I built a tweak using dragon, and the resulting .deb installs files under UID 1000 (which is the user I'm running dragon as). That UID doesn't even exist in iOS. It should install them as root:wheel (0:0) instead.
Dragon runs as a normal user, so the directory structure in .dragon/_/ will be owned by my user too. When the package is built, tar copies the UID/GID and permissions into the data.tar, and when installing the package, dpkg applies them to the installed files.
The way Debian handles this nowadays is by passing --root-owner-group to dpkg-deb when building the binary package. This sets all files to root:root ownership. However this would need dpkg 1.19.0; I'm not sure what is used on macOS or on-device iOS?
I built a tweak using dragon, and the resulting .deb installs files under UID 1000 (which is the user I'm running dragon as). That UID doesn't even exist in iOS. It should install them as root:wheel (0:0) instead.
Dragon runs as a normal user, so the directory structure in
.dragon/_/
will be owned by my user too. When the package is built,tar
copies the UID/GID and permissions into the data.tar, and when installing the package, dpkg applies them to the installed files.The way Debian handles this nowadays is by passing
--root-owner-group
to dpkg-deb when building the binary package. This sets all files to root:root ownership. However this would need dpkg 1.19.0; I'm not sure what is used on macOS or on-device iOS?