Hi, On Wed, 10 Apr 2013, Jonathan Nieder wrote: > > It might look harmless, but we do *NOT* want to release Debian > > with a dpkg that is broken with respect to all the descriptions > > floating around how to clone a system. > > I agree that this is a problem, but I cannot convince myself it breaks > the entire system. Therefore I'm lowering the severity. > > Presumably this is due to > > 1.16.2~15 dpkg: Only allow setting selections for known packages, > 2012-03-17 > > It is a shame the impact of that commit on existing workflows was not > noticed until a year later. Guillem, can you say a little about the > motivation behind the change? Would it be safe to revert it?
The impact was perfectly known. I was also concerned by the change but Guillem did not want to change his mind. See https://lists.debian.org/debian-dpkg/2012/03/msg00065.html and Guillem's reply in https://lists.debian.org/debian-dpkg/2012/03/msg00067.html Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
