Bug#496287: Me too!

2009-01-03 Thread Francesco Poli
On Sat, 3 Jan 2009 15:49:09 +0100 Marc Haber wrote: > On Wed, Sep 10, 2008 at 12:15:30AM +0200, Francesco Poli wrote: > > Those messages are definitely noisy and suspicious during the libsane > > package upgrade. > > They also appear when upgrading an etch system to lenny, which makes > it worth

Bug#496287: Me too!

2009-01-03 Thread Marc Haber
On Wed, Sep 10, 2008 at 12:15:30AM +0200, Francesco Poli wrote: > Those messages are definitely noisy and suspicious during the libsane > package upgrade. They also appear when upgrading an etch system to lenny, which makes it worthwhile to either actually fix in lenny or to document in the relea

Bug#496287: Me too!

2008-09-12 Thread Bdale Garbee
On Fri, 2008-09-12 at 19:49 +0200, Francesco Poli wrote: > On Fri, 12 Sep 2008 12:51:49 +0300 Martin Michlmayr wrote: > > > * Francesco Poli <[EMAIL PROTECTED]> [2008-09-11 19:35]: > > > # mount | grep static > > > # /var/lib/dpkg/info/libsane.postinst configure > > > # echo $? > > > > > >

Bug#496287: Me too!

2008-09-12 Thread Francesco Poli
On Fri, 12 Sep 2008 12:51:49 +0300 Martin Michlmayr wrote: > * Francesco Poli <[EMAIL PROTECTED]> [2008-09-11 19:35]: > > # mount | grep static > > # /var/lib/dpkg/info/libsane.postinst configure > > # echo $? > > > > You should not see any error messages now... > > Yeah, it's fine now. P

Bug#496287: Me too!

2008-09-12 Thread Martin Michlmayr
* Francesco Poli <[EMAIL PROTECTED]> [2008-09-11 19:35]: > # mount | grep static > # /var/lib/dpkg/info/libsane.postinst configure > # echo $? > > You should not see any error messages now... Yeah, it's fine now. 15709:[EMAIL PROTECTED]: ~] sudo /var/lib/dpkg/info/libsane.postinst configur

Bug#496287: Me too!

2008-09-11 Thread Francesco Poli
On Thu, 11 Sep 2008 07:45:01 +0300 Martin Michlmayr wrote: > * Francesco Poli <[EMAIL PROTECTED]> [2008-09-10 23:15]: > > > > P.S.: I am Cc:ing the bug submitter, maybe he also had udev <= 0.114-2 > > > > installed at the time of his latest reboot, when he submitted this bug > > > > report... Mar

Bug#496287: Me too!

2008-09-10 Thread Martin Michlmayr
* Francesco Poli <[EMAIL PROTECTED]> [2008-09-10 23:15]: > > > P.S.: I am Cc:ing the bug submitter, maybe he also had udev <= 0.114-2 > > > installed at the time of his latest reboot, when he submitted this bug > > > report... Martin, can you check? > > > > I'm afraid I cannot remember. I don't

Bug#496287: Me too!

2008-09-10 Thread Francesco Poli
On Wed, 10 Sep 2008 08:55:46 +0300 Martin Michlmayr wrote: > * Francesco Poli <[EMAIL PROTECTED]> [2008-09-10 00:15]: > > P.S.: I am Cc:ing the bug submitter, maybe he also had udev <= 0.114-2 > > installed at the time of his latest reboot, when he submitted this bug > > report... Martin, can you

Bug#496287: Me too!

2008-09-09 Thread Martin Michlmayr
* Francesco Poli <[EMAIL PROTECTED]> [2008-09-10 00:15]: > P.S.: I am Cc:ing the bug submitter, maybe he also had udev <= 0.114-2 > installed at the time of his latest reboot, when he submitted this bug > report... Martin, can you check? I'm afraid I cannot remember. I don't think it was that ol

Bug#496287: Me too!

2008-09-09 Thread Francesco Poli
On Tue, 09 Sep 2008 13:48:49 -0600 Bdale Garbee wrote: > On Tue, 2008-09-09 at 20:07 +0200, Francesco Poli wrote: > > found 496287 2.3.1-88 > > thanks > > > > Hi! > > I've just seen the same issue while upgrading from libsane/1.0.19-17 to > > libsane/1.0.19-19. > > Does this actually cause an op

Bug#496287: Me too!

2008-09-09 Thread Bdale Garbee
On Tue, 2008-09-09 at 20:07 +0200, Francesco Poli wrote: > found 496287 2.3.1-88 > thanks > > Hi! > I've just seen the same issue while upgrading from libsane/1.0.19-17 to > libsane/1.0.19-19. Does this actually cause an operational problem, or is it just noisy on install? Bdale -- To UNSUB

Bug#496287: Me too!

2008-09-09 Thread Francesco Poli
found 496287 2.3.1-88 thanks Hi! I've just seen the same issue while upgrading from libsane/1.0.19-17 to libsane/1.0.19-19. I thought I should report this, so that I could add a "found" version for this bug... -- http://frx.netsons.org/doc/index.html#nanodocs The nano-document series is here!