On Fri, Mar 24, 2017 at 07:30:55PM +0500, Andrey Rahmatullin wrote: > On Fri, Mar 24, 2017 at 03:25:59PM +0100, Adam Borowski wrote: > > autoremove will still usually catch this. > I'm not sure about this. Looks like it keeps Recommends or something. Or > it's a bug.
I'd say that apt autoremove keeping Recommends even when called with --no-install-recommends is a reasonable behaviour. Same for Priority:important or Important:yes packages. The sbuild case is quite special. The functionality to keep a system squeaky clean would probably be better in debfoster, but alas, it's effectively unmaintained. > > you do refresh your chroots from time to time (don't you?); > No, I didn't even think it's ever needed until I saw FTBFS bugs about > tzdata not installed with the base system anymore. Do we have guidelines > on keeping our chroots healthy apart from running sbuild-update -udr from > time to time? The man page recommends -udcar, which includes autoclean, and, important here, autoremove. No idea about official buildds, but I remember hearing somewhere that the Reproducible Builds project recreates them from scratch once a month. -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!