Re: bug #350639

2009-05-20 Thread Osamu Aoki
Hi, On Mon, May 18, 2009 at 01:32:01PM -0300, Tiago Saboga wrote: > Freddy Freeloader writes: > > Thorny wrote: > >> On Sun, 17 May 2009 12:31:05 -0700, Freddy Freeloader posted: > >>> In my mind there is no good reason for this fix to go into Sid > >>> and then sit there until the dependencies

Re: bug #350639

2009-05-18 Thread Tiago Saboga
Freddy Freeloader writes: > Thorny wrote: >> On Sun, 17 May 2009 12:31:05 -0700, Freddy Freeloader posted: >>> In my mind there is no good reason for this fix to go into Sid >>> and then sit there until the dependencies are satisfied for that version >>> number. >>> >> >> Well, that is the s

Re: bug #350639

2009-05-18 Thread Eduardo M KALINOWSKI
On Seg, 18 Mai 2009, Freddy Freeloader wrote: It is also standard flow to fix bugs that are found in testing, not to always wait until a new version comes down from Sid. No, that's not the Debian flow. That's the purpose for which testing exists. Those bugs not found while a package is in

Re: bug #350639

2009-05-18 Thread Freddy Freeloader
Thorny wrote: On Sun, 17 May 2009 12:31:05 -0700, Freddy Freeloader posted: [...] I have to ask why. Why is this left up every user of testing to fix this problem themselves when the fix is so simple? [...] One possible answer to this question would be that users of "testing" are sup

Re: bug #350639

2009-05-18 Thread Thorny
On Sun, 17 May 2009 12:31:05 -0700, Freddy Freeloader posted: [...] > > I have to ask why. Why is this left up every user of testing to fix > this problem themselves when the fix is so simple? >[...] One possible answer to this question would be that users of "testing" are supposed to be able t

Re: bug #350639

2009-05-18 Thread Andrei Popescu
On Mon,18.May.09, 00:48:44, Matteo Riva wrote: > On Sun, May 17, 2009 at 9:58 PM, Javier Barroso wrote: > > > It seems resolved in unstable, > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525183 > > I have rebuilt the package from source as suggested by a user in that > bug report, but now

Re: bug #350639

2009-05-17 Thread Freddy Freeloader
Matteo Riva wrote: On Sun, May 17, 2009 at 9:58 PM, Javier Barroso wrote: It seems resolved in unstable, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525183 I have rebuilt the package from source as suggested by a user in that bug report, but now the update manager flags gnome-vo

Re: bug #350639

2009-05-17 Thread Freddy Freeloader
Javier Barroso wrote: Hi, On Sun, May 17, 2009 at 9:31 PM, Freddy Freeloader wrote: I'd like to point this bug out as it has been around now for 3 1/2 months with no official resolution. What's worse is that this bug was caused by the Debian gnome-volume-manager maintainer. Nobody else is

Re: bug #350639

2009-05-17 Thread Matteo Riva
On Sun, May 17, 2009 at 9:58 PM, Javier Barroso wrote: > It seems resolved in unstable, > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525183 I have rebuilt the package from source as suggested by a user in that bug report, but now the update manager flags gnome-volume-manager as needing an

Re: bug #350639

2009-05-17 Thread Javier Barroso
Hi, On Sun, May 17, 2009 at 9:31 PM, Freddy Freeloader wrote: > I'd like to point this bug out as it has been around now for 3 1/2 months > with no official resolution.  What's worse is that this bug was caused by > the Debian gnome-volume-manager maintainer.  Nobody else is responsible for > it.

bug #350639

2009-05-17 Thread Freddy Freeloader
I'd like to point this bug out as it has been around now for 3 1/2 months with no official resolution. What's worse is that this bug was caused by the Debian gnome-volume-manager maintainer. Nobody else is responsible for it. He disabled automount when he compiled the gnome-volume-manager pa