On Mon, Oct 07, 2013 at 10:10:55PM +0200, Francesco Poli wrote: > Control: tags -1 + moreinfo > > > On Mon, 7 Oct 2013 11:20:26 +0200 Cyril Brulebois wrote: > > [...] > > Gilles Crevecoeur <gilles.creveco...@gmail.com> (2013-10-07): > > > Package: apt-listbugs > > > Version: 0.1.9 > > > Severity: normal > > > > > > Dear Maintainer, > > Hello Gilles, > thanks for your bug report!
Hello Francesco, Thanks for your response! > > > > > > > While the version 0.1.9 works correctly, the last version > > > fails with this message : > > > W: uninitialized constant XML::SaxParser > > Awkward! > I have never seen any error resembling this, during the development > cycle of apt-listbugs/0.1.10 ... > > > > > > > > > > I've downgraded to previous version to be able > > > to update my system more safely. > > > > So you should have edited the Version pseudoheader. Fixing with the > > above commands. Hello Cyril, This is because, I use reportbug stupidly. Thanks for your correction and your reply. I'll try to think to that the next time i'll fill a bug report ;) > > Hello Cyril, > many thanks for fixing the version tracking info and for sending a > first reply to Gilles! It's really appreciated. > > > > > I can't seem able to reproduce this issue, taking a testing chroot and > > upgrading only apt-listbugs. > > I cannot reproduce the bug, either. > > > Anything special with your setup? I don't think there is something special... But I'll think about that. I'll try again apt-listbugs/0.1.10 to see the results. > > This is an important question: Gilles, please describe any special > configuration that may be related to the bug. > > BTW, Gilles, what's the output of "ruby -v" on your system? I use the ruby interpreter provide by official debian packages. ruby -v output : ruby 1.9.3p448 (2013-06-27 revision 41675) [i486-linux] I've left the default configuration in /etc/apt/listbugs/ > > > > (It appears I have the same set of ruby packages installed, besides > > ruby-gettext. Getting to the same version as yours didn't make a > > difference.) > > > > Trying to install ruby1.9 doesn't seem to lead to any issues either > > (tried that since the changelog suggested bits of 1.9 support got > > merged in that release). > > I confirm that apt-listbugs/0.1.10 is the release where support for > Ruby 1.9 has just debuted (generating a few new bug reports...!). > But I tested the package several times with both Ruby 1.8 and Ruby 1.9: > everything worked fine and I have never seen the error experienced by > Gilles, as I said. > I am really puzzled. > > I suspect that the problem lies in package ruby-soap4r, but I still > have to figure out why Cyril and I do not experience it. I've had the same idea about ruby-soap4r. > Gilles, please provide the requested additional information, thanks. I apologize, I'm not comfortable at all with english, and this is the reason why my message is so tight ;) Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
