[buildd-tools-devel] Bug#792037: Doesn't upgrade to the newest versions of packages in extra repositories

[Iain Lane]

Package: libsbuild-perl
Version: 0.65.2-1
Severity: normal
Tags: patch

Hi, thanks for sbuild!

I noticed that packages in a repository given via --extra-repository
that are preinstalled into the base chroot aren't upgraded to. For
example I was trying to test building with GCC5 from a PPA of doko's and
yet it wasn't being used during the build. It seems like these repos are
added quite late on, just before installing the actual build-deps and
*after* the initial upgrade/dist-upgrade. This means that build-deps are
satisfied from this repo but things already in the chroot are left as
they were.

Attached is a patch to simply dist-upgrade after doing the later update.
Do you think this makes sense? Note that (AFAICT) sbuild has carefully
only updated its indices for the extra repository and its internal one,
so this should avoid accidentally dist-upgrading from the main archive
again if we get a race condition with a mirror pulse or similar. Note
that I only tested the apt resolver and just assume the aptitude one is
the same, sorry...

Cheers,

-- 
Iain Lane                                  [ iain at orangesquash.org.uk ]
Debian Developer                                   [ laney at debian.org ]
Ubuntu Developer                                   [ laney at ubuntu.com ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-lib-Sbuild-Apt-itude-Resolver.pm-dist-upgrade-after-.patch
Type: text/x-diff
Size: 1994 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20150710/dd44a0d8/attachment.patch>