Hi, On Sun, 18 Mar 2012, Guillem Jover wrote: > With multiarch, non-installed selections w/o an architecture, do not > make sense, in addition there's no guarantee they match any entry > from the available file and the db could end up with a selection that > could not be addressed from the command line when other more specific > selections were present. As such the new dpkg will silently drop any > such selections, which look like (with possible Section and Priority > fields): [...] > In addition selections for packages unknown to dpkg will not be > accepted anymore.
I'm not sure I understand this correctly but I'm afraid that this is a serious regression. It has always been possible to sort-of "duplicate" a system by doing "dpkg --get-selections >file" on one computer and running "dpkg --set-selections <file" on another computer followed by an "apt-get dselect-upgrade". This requires that dpkg accepts the selection for packages that it doesn't know about (but that apt knows). Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
