On Wed, 06 Apr 2011, Jonathan Nieder wrote: > I am not Guillem :) but I think the ideal thing would be a way for the > user to (perhaps explicitly) update the status db by inserting an > architecture.
Why ? 1/ It concerns packages which have not been touched since 2004 or packages which were installed before 2004 and got removed but not purged since then 2/ We can't invent the value to put in Architecture > Available seems less of a problem given the workaround > "dpkg --clear-avail"; in an ideal world "apt-get update" and "dselect > update" would be taught[1] to remove stale entries, though. dselect update sometimes does depending on the "method" configured. Right now, it serves no purpose for apt-get to update the available file. > Especially for the sake of cross-upgrade support, the architecture > field seems kind of important. Which is why we're requiring it now and why we're more verbose. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
