Hans-Christoph Steiner <hans@eds.org> (2014-11-25): > The package android-permissions integrates the Android permissions into a > Debian chroot running on Android. Android permissions are implemented in > Android's Linux kernel using UIDs and GIDs. Therefore, this package should > only ever run on a Debian chroot running with an Android kernel. It adds all > of the hard-coded users and groups to Debian. > > It should modify things like GID_MAX or LAST_GID in /etc/login.defs and > /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs, but it is a > policy violation for a package to modify those files. Any suggestions as how > to best tackle this issue? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770330 > > One idea was to make a debootstrap variant, but I'm not sure that cdebootstrap > supports that. The idea is rather than having the package do these changes > directly, it provides a script that does the changes to a specified root > directory. Then this script is run as part of the variant. I suppose this could be done, even if probably not for jessie. You can't depend on this behaviour anyway from your package, since you don't know what type of environment you're getting installed within. > Another idea is to create /etc/login.defs.d and /etc/adduser.conf.d so that > packages can add definitions there. Adding respective maintainers to the loop. > (please keep me CCed since I'm not subscribed) (done) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature