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: > > 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: > 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 I did say "ideally". I can understand if you're not motivated to work on it. (That said, iiuc the above is not so

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 inst

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 ins

Bug#604241: missing architecture warnings

2011-04-06 Thread jidanni
> "RH" == Raphael Hertzog writes: RH> On Mon, 04 Apr 2011, jida...@jidanni.org wrote: RH> (Or edit /var/lib/dpkg/status to add the missing field if you really want a RH> dirty hack to shut up dpkg.) >> OK, I'll do that. What should I put where? RH> Put a line "Architecture: all" in the set of

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

2011-04-06 Thread Raphael Hertzog
Hello, On Tue, 05 Apr 2011, Sven-Haegar Koch wrote: > Package: libmimelib1 > Status: deinstall ok config-files I did some code archeology to try to find out an explanation of why dpkg would have dropped that field. And I found it: http://bugs.debian.org/228253 It got "fixed" by this commit: c

Bug#621066: dpkg-query manpage doesn't explain -S well

2011-04-06 Thread Raphael Hertzog
On Wed, 06 Apr 2011, Lars Buitinck wrote: > dpkg-query(1) explains -S as: > Search for a filename from installed packages. > while it really searches for packages given a filename pattern. It also > doesn't > include the word "own" which I've frequently tried to use to find this option.

Bug#621066: marked as pending

2011-04-06 Thread Raphaƫl Hertzog
tag 621066 pending thanks Hello, Bug #621066 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=9dc6ea2 --- commit 9dc6ea29b59050af1fd06c6c348afacc428de8f4 Aut

Processed: Bug#621066 marked as pending

2011-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 621066 pending Bug #621066 [dpkg] dpkg-query manpage doesn't explain -S well Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 621066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62106

Bug#621066: dpkg-query manpage doesn't explain -S well

2011-04-06 Thread Lars Buitinck
Package: dpkg Version: 1.15.8.10 Severity: minor Tags: patch dpkg-query(1) explains -S as: Search for a filename from installed packages. while it really searches for packages given a filename pattern. It also doesn't include the word "own" which I've frequently tried to use to find this