Hi Guillem, On Fri, 30 Jul 2010, Guillem Jover wrote: > I'll consider whether to do something about these bug reports for > tomorrow's upload, mostly because this is a regression from the point > of view of the user, that had a working dpkg before the upgrade and > it suddenly stopped working. But I'm tending to think about this as > wontfix.
Would it be doable to add a pre-inst snippet that sed/awks the available/status file? Or is that not going to work because dpkg has already loaded the file and won't take into account those changes? I guess so. Ideal would be to fix it by replacing invalid characters by "+invalid+char+removed+by+dpkg+". sed -i -e '/^Version:/ s/[^-a-zA-Z0-9:.+~ ]/+invalid+char+removed+by+dpkg+/g' /var/lib/dpkg/available Alternatively it should abort the upgrade and ask the user to cleanup before-hand. It could give out the requireds commands. We could also fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397121 so that the cruft in the available file really affects only dselect users. This would make dpkg more robust in general BTW. Cheers, -- Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693] 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
