[buildd-tools-devel] [PATCH] Remove debfoster from things automatically installed by sbuild-createchroot

[Philipp Kern]

On Mon, Jan 16, 2012 at 10:37:27AM +0000, Roger Leigh wrote:
> Out of interest, how commonly is this needed now that we have
> snapshots?
> 
> I would have thought that nowadays there is little reason to do any
> manual package install/remove in a buildd chroot after the initial
> debootstrap.  It would be useful to know what situations require
> this.

For odd reasons I still catch stray libs when I upgrade the chroot (which is
the situation we're talking about).  Also not all buildds use snapshots.

(I think debootstrap installs the initial set and then the libs are marked as
manually installed.  And when the core libs get their ABI bumped, you'll get
the new and the old one wouldn't go away.  It wouldn't cause any trouble but I
still think that one should get rid of them.  debfoster, due to how it works,
catches them.)

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern                        Debian Developer
: :' :  http://philkern.de                         Stable Release Manager
`. `'   xmpp:phil at 0x539.de                         Wanna-Build Admin
  `-    finger pkern/key at db.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20120116/28e7fd37/attachment.pgp>