Control: reassign -1 ruby-gettext 3.3.3-2 Control: affects -1 apt-listbugs
On Tue, 07 Nov 2023 20:49:03 +0100 Jochen Spieker wrote: > Package: apt-listbugs > Version: 0.1.41 > Severity: minor > > Dear Maintainer, Hello Jochen, thanks for your bug report. > > on my laptop running sid I am often using an NFS mount that is only available > when I am at home. > > Today I had the NFS filesystem mounted when I suspended my laptop, moved it > somewhere else and woke it up again. My shell still had the NFS (unavailable) > mount as the current working directory. Then I ran 'apt upgrade'. An unusual use case, although an interesting one... > The upgrade failed like this: [...] > <internal:dir>:220:in `glob': Input/output error - ./locale (Errno::EIO) > from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:64:in `block in > default_path_rules' > from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:63:in `select' > from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:63:in > `default_path_rules' > from /usr/lib/ruby/vendor_ruby/gettext/locale_path.rb:80:in > `initialize' > from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:52:in `new' > from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:52:in > `initialize' > from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:226:in > `new' > from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:226:in > `create_or_find_text_domain' > from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:71:in > `bind_to' > from /usr/lib/ruby/vendor_ruby/gettext.rb:73:in `bindtextdomain_to' > from /usr/lib/ruby/vendor_ruby/gettext.rb:54:in `bindtextdomain' > from /usr/bin/apt-listbugs:428:in `<main>' > E: Sub-process /usr/bin/apt-listbugs apt returned an error code (1) > E: Failure running script /usr/bin/apt-listbugs apt It seems that a simple call to GetText::bindtextdomain() caused a search inside a ./locale directory, from within the ruby-gettext library, but ./ was not accessible, since it belonged to a non-responding NFS mount. Hence the I/O error. > > > It would be great if a problem with the current working directory could be > handled more gracefully. It took me a few minutes to find out what the > problem was. I agree that this kind of problems could be handled better, even though we are talking about a quite unusual situation. However, apt-listbugs is just making ruby-gettext library calls in the correct manner (or in what I believe is the correct manner). I think it is the responsibility of the library to make sure that unforeseen filesystem accessibility issues are handled gracefully. I am therefore reassigning your bug report to package 'ruby-gettext': I hope it will be handled there, possibly by forwarding it upstream. Actually, I see that there's already another bug report about the same issue: [#943714] [#943714]: <https://bugs.debian.org/943714> It's probably reasonable to merge these two bug reports... > > Thanks, > Jochen Thanks to you, bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpd7_3gPP8s6.pgp
Description: PGP signature
