On Sun, Apr 21, 2013 at 07:30:48PM +0200, Guillem Jover wrote: > > What I'm planning to do to try to improve the situation is: > > * Document the change in the man page in master targetting 1.17.x > (perhaps 1.16.x too). > * Probably add a single warning at the end of the --set-selections > processing if any unknown package has been found, prompting the > user to consider updating the available database in master > targetting 1.17.x. > * Add an entry in <http://wiki.debian.org/Teams/Dpkg/FAQ>. > * Clone this to the release-notes so that this gets documented there > too. > * Possibly, ask nicely the release-team if they'd consider accepting > any kind of documentation update for this (doubtful), even if only > for r1.
Hi, Anything that documents this dpkg feature and suggests alternatives is OK, I leave the exact way to your choice, but the above seems to me very reasonable. This bug report should also be helpful in web searches. I noticed this problem when trying to carry out a i386-amd64 migration with all required packages previously downloaded-only in the amd64 chroot, before the actual migration-upgrade, so this was not harmful. What surprised me was that I did not find easy references in first web searches, just after refining the search I could find info about both the message and the clone process together in the same thread. Surprisingly, I even remember somebody complaining that there was no filed bugreport about this, but did not actually file one. A pity, you could have had more time to deal with the documentation changes if that bug was filed in time. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
