Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2012-01-06 Thread Jonathan Nieder
Raphael Manfredi wrote: I wrote a little perl script to do the conversion. God bless you for using a text file for the database and not some binary format: --- #!/usr/bin/perl use strict; my @lines; my $seen_arch = 0; while () { push (@lines, $_);

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-09 Thread Guillem Jover
Hi! On Thu, 2011-04-07 at 08:04:58 +0200, Raphael Hertzog wrote: On Wed, 06 Apr 2011, Jonathan Nieder wrote: Would it be possible in the long term for dpkg to stop caring about available altogether (leaving it to dselect)? Yes, it's more or less the plan. We've just changed dpkg to not

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-07 Thread Raphael Hertzog
On Wed, 06 Apr 2011, Jonathan Nieder wrote: 2/ We can't invent the value to put in Architecture It seems likely this has been covered before, but just in case: why not put in the native architecture for already-installed, ancient packages? It could be Architecture: all instead of the

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-06 Thread Jonathan Nieder
Hi, Raphael Hertzog wrote: The change is very old, not many users will be affected by this. Guillem, what do you think? Should we silence the warning due to this? 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

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-06 Thread Raphael Hertzog
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

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-05 Thread Sven-Haegar Koch
Package: dpkg Version: 1.16.0.1 Severity: normal Since the 1.16.0 update dpkg outputs a ton of new warning messages for each run (multiple times for one apt-get dist-upgrade). Example: aurora:~# dpkg -l dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 301 package

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-05 Thread Raphael Hertzog
Hello, On Tue, 05 Apr 2011, Sven-Haegar Koch wrote: aurora:~# dpkg -l dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 301 package 'libmimelib1': missing architecture [...] These seem all to only affect packages long removed, but not purged. Can you show us the entry in

Bug#620958: dpkg outputs tons of new warning messages with no obvious way to fix them

2011-04-05 Thread Sven-Haegar Koch
On Tue, 5 Apr 2011, Raphael Hertzog wrote: Hello, On Tue, 05 Apr 2011, Sven-Haegar Koch wrote: aurora:~# dpkg -l dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 301 package 'libmimelib1': missing architecture [...] These seem all to only affect packages long