On 9 November 2016 at 21:21, Johannes Schauer <[email protected]> wrote: > > Hi, > > On Tue, 8 Nov 2016 16:44:53 -0300 Felipe Sateler <[email protected]> wrote: > > On 8 November 2016 at 16:39, Felipe Sateler <[email protected]> wrote: > > > Package: sbuild > > > Version: 0.72.0-2 > > > Severity: wishlist > > > > > > Hi, > > > > > > I have been trying to run some builds with a modified dpkg, but this > > > currently isn't working. sbuild appears to copy the debs to the chroot > > > after the initial apt-get update/upgrade, so it will not be > > > automatically upgraded. > > > > > > --chroot-setup-commands= doesn't help because it is also run before > > > setting up the apt repository, and --starting-build-commands= is run as > > > non-root. > > > > > > Upon further reading of the manpage, it is explicitly stated that > > > --extra-packages is only available for build-dependency resolution, and > > > that there is no --$something-command that will run as root but after > > > all chroot setup. It would be great to have such a command. > > > > I forgot to add that it is currently possible to --add-depends to > > achieve installation, but in the general case where one needs a root command > > after injecting the debs (eg, to run some command from the package) this > > would not be possible. > > now I'm confused. What's the bug here? As you already pointed out, > --add-depends allows you to force installation of your custom .deb. What is > missing? Why do you still need root after packages are installed? > > Your bug report might also have similarities to #792037.
Hmm, it appears I was confused as well. I started drafting this report before discovering --add-depends, and thus the title. I guess what I want is equivalent to #792037 but for --extra-packages instead of --extra-repository. I do not currently need root after packages are installed, but it is indeed impossible to have root after build-deps (and the extra repos) have been installed. -- Saludos, Felipe Sateler
