[buildd-tools-devel] Bug#865541: Bug#865541: sbuild --apt-distupgrade should not remove build-essential

[Johannes Schauer]

Hi,

Quoting Raphael Hertzog (2017-06-26 15:00:28)
> On Mon, 26 Jun 2017, Johannes Schauer wrote:
> > > It would because actually I pass "--apt-update --apt-upgrade" but not
> > > "--apt-distupgrade" and I have no ~/.sbuildrc.
> > then why not pass --no-apt-distupgrade?
> Because when I wrote that script, I was probably not aware that
> --apt-distupgrade was the default.

so does the existence of that option help your use-case somehow?

> > > If I call sbuild-update --dist-upgrade, I might understand that you would
> > > like the command to fail.
> > Unfortunately, currently sbuild makes no distinction between how a
> > configuration variable was set, whether it was via the sbuildrc, a
> > commandline switch, an environment variable or whether the user changed
> > nothing and it was just the default.
> > 
> > Adding provisions that would let sbuild know who set a variable and then
> > letting sbuild behave differently depending on how the variable was set would
> > be a big effort.
> 
> I understand this. But you can react differently to the failure in the
> various places where you are calling "$resolver->distupgrade".

What do you mean exactly here?

> > > For a build chroot, we want the opposite... as long as it doesn't break
> > > the build chroot. If the new perl causes the removal of dpkg-dev, then it
> > > should not be dist-upgraded. If it causes the removal of
> > > liblocale-gettext-perl only, then it's fine.
> > 
> > Unfortunately, "apt-mark hold" has the nasty side effect that it not only stops
> > a package from being removed but it also stops a package from being upgraded.
> Hence we start with "apt-get install build-essential" which does upgrade it
> before we mark it back on hold.

Ah right, you indeed said this in your first mail.

So how do you want to solve the issue now for kali? By just passing
--no-apt-distupgrade and upgrading the chroots manually from time to time like
the Debian and Ubuntu buildds do it?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20170626/3e2d928c/attachment.sig>