Your message dated Sun, 06 Apr 2014 18:03:26 +0000 with message-id <[email protected]> and subject line Bug#740564: fixed in apt-listbugs 0.1.13 has caused the Debian Bug report #740564, regarding apt-listbugs: auxiliary script send-hook-info.rb fails to work with Ruby 2.0 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 740564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740564 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apt-listbugs Version: 0.1.12 Severity: normal Tags: help I am filing this bug report against my own package, since I noticed something awkward that I am unable to understand. Hence this is intended as both a reminder of the issue and a call for help. The issue is that the send-hook-info.rb auxiliary script seems to break with Ruby 2.0. Please take a look at the following transcript (the input file is attached): $ ruby1.9.1 /usr/share/doc/apt-listbugs/examples/send-hook-info.rb v3-hookinfo_install_1lib_upgrade_1lib.txt 'ruby1.9.1 /usr/sbin/apt-listbugs apt' APT_HOOK_INFO_FD set to 5 Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of libnss-ldap (264-2.2 → 264-2.5) <Resolved in some Version> #706182 - libnss-ldap: purging deletes shared config file /etc/libnss-ldap.conf still in use by other architectures (Fixed: libnss-ldap/265-3) serious bugs of libnss-ldap:i386 (→ 264-2.5) <Resolved in some Version> #706182 - libnss-ldap: purging deletes shared config file /etc/libnss-ldap.conf still in use by other architectures (Fixed: libnss-ldap/265-3) #661628 - libnss-ldap: fails to configure: tries to run /etc/init.d/nscd but /etc/init.d/unscd is the one that actually exists (Fixed: libnss-ldap/265-1) Summary: libnss-ldap(1 bug), libnss-ldap:i386(2 bugs) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Y $ ruby1.9.1 /usr/share/doc/apt-listbugs/examples/send-hook-info.rb v3-hookinfo_install_1lib_upgrade_1lib.txt 'ruby2.0 /usr/sbin/apt-listbugs apt' APT_HOOK_INFO_FD set to 5 Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of libnss-ldap (264-2.2 → 264-2.5) <Resolved in some Version> #706182 - libnss-ldap: purging deletes shared config file /etc/libnss-ldap.conf still in use by other architectures (Fixed: libnss-ldap/265-3) serious bugs of libnss-ldap:i386 (→ 264-2.5) <Resolved in some Version> #706182 - libnss-ldap: purging deletes shared config file /etc/libnss-ldap.conf still in use by other architectures (Fixed: libnss-ldap/265-3) #661628 - libnss-ldap: fails to configure: tries to run /etc/init.d/nscd but /etc/init.d/unscd is the one that actually exists (Fixed: libnss-ldap/265-1) Summary: libnss-ldap(1 bug), libnss-ldap:i386(2 bugs) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Y $ ruby2.0 /usr/share/doc/apt-listbugs/examples/send-hook-info.rb v3-hookinfo_install_1lib_upgrade_1lib.txt 'ruby2.0 /usr/sbin/apt-listbugs apt' APT_HOOK_INFO_FD set to 7 $ ruby2.0 /usr/share/doc/apt-listbugs/examples/send-hook-info.rb v3-hookinfo_install_1lib_upgrade_1lib.txt 'ruby1.9.1 /usr/sbin/apt-listbugs apt' APT_HOOK_INFO_FD set to 7 /usr/sbin/apt-listbugs:344:in `initialize': Bad file descriptor (Errno::EBADF) from /usr/sbin/apt-listbugs:344:in `open' from /usr/sbin/apt-listbugs:344:in `<main>' In summary, apt-listbugs works with both Ruby 1.9 and Ruby 2.0, but send-hook-info.rb seems to fail to work correctly with Ruby 2.0 ! I cannot understand where the problem lies. http://www.ruby-doc.org/core-2.0.0/IO.html#method-c-pipe http://www.ruby-doc.org/core-2.0.0/Process.html#method-c-fork http://www.ruby-doc.org/core-2.0.0/Kernel.html#method-i-exec seem to confirm that the code is correct... Do anyone have any idea of what's wrong and how it may be fixed?VERSION 3 APT::Architecture=amd64 libnss-ldap 264-2.2 amd64 same < 264-2.5 amd64 same /var/cache/apt/archives/libnss-ldap_264-2.5_amd64.deb libnss-ldap - - none < 264-2.5 i386 same /var/cache/apt/archives/libnss-ldap_264-2.5_i386.deb libnss-ldap 264-2.2 amd64 same < 264-2.5 amd64 same **CONFIGURE** libnss-ldap - - none < 264-2.5 i386 same **CONFIGURE**
--- End Message ---
--- Begin Message ---Source: apt-listbugs Source-Version: 0.1.13 We believe that the bug you reported is fixed in the latest version of apt-listbugs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Poli (wintermute) <[email protected]> (supplier of updated apt-listbugs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 02 Apr 2014 22:56:47 +0200 Source: apt-listbugs Binary: apt-listbugs Architecture: source all Version: 0.1.13 Distribution: unstable Urgency: medium Maintainer: Francesco Poli (wintermute) <[email protected]> Changed-By: Francesco Poli (wintermute) <[email protected]> Description: apt-listbugs - tool which lists critical bugs before each APT installation Closes: 441689 493632 524768 562499 740564 Changes: apt-listbugs (0.1.13) unstable; urgency=medium . * improved README.Debian formatting * documented how to temporarily disable the invocation of apt-listbugs in README.Debian * added some further considerations to the section about the "affects" field in README.Debian * fixed a bug in the handling of the user's answer to the question on how to proceed (continue or stop the installation, or pin packages, and so forth...): a "y" answer is now ignored, when some packages have just been pinned * improved the man page: - clarified what happens with the force options when in apt mode - enhanced the explanation of the exit status - improved style and clarity of the explanation for IgnoreRegexp - enhanced the explanation of APT_HOOK_INFO_FD - clarified the explanation of the severity filter option * updated gitweb URL in man page and in debian/copyright file * fixed another bug in the handling of the user's answer to the question on how to proceed: an answer containing the letter "h" or "p" is no longer misinterpreted as an "h" or "p" answer * refreshed the .pot file for internationalization - switched to rxgettext for the .pot file generation * enhanced reading of ignore_bugs files: each line is considered a comment, if its first nonwhitespace character is '#'; otherwise, the first word is considered a package name or bug number to be ignored. * downgraded the dependencies on ruby-xmlparser and ruby-httpclient to recommendations * fixed "auxiliary script send-hook-info.rb fails to work with Ruby 2.0": added an explicit file descriptor redirection to the exec call in order to adapt to Ruby 2.0 stricter behavior; thanks a lot to Christian Hofstaedtler for explaining what was wrong and for pointing me to the appropriate documentation! (Closes: #740564) * fixed "New feature to automatically pin packages (implementation patch supplied)": implemented the --force-pin option, thanks to Famelis George for the initial patch, updated by Serafeim Zanikolas (thanks!) and further modified by me (Closes: #441689) * fixed "make ParseStep configurable": created an APT configuration option (Closes: #562499) * fixed "should try and be more informative on "invalid date" SOAP parsing error" (Closes: #493632) and "Proposed Workaround for Apt-listbugs SOAP Failures" (Closes: #524768): on network errors, apt-listbugs now proposes to the user to retry one bug report at a time and begins showing the bug number currently being parsed. Checksums-Sha1: 5807f845ae58493d588e6b3fe16dc247a6f90ea7 1751 apt-listbugs_0.1.13.dsc 068c5f8329bf94775312a35f71f9210a22eb5093 98192 apt-listbugs_0.1.13.tar.xz e7cfafb793cbc6c6fff63a4f1bff1a13ab9e32d1 68044 apt-listbugs_0.1.13_all.deb Checksums-Sha256: adbcb08babf2040cb0c940c0779f535dc78000cf5675a34c779989dd6362b996 1751 apt-listbugs_0.1.13.dsc 45182d23b2f35825d3336962fad92850628675af09840f701d3ff24e7ab804a0 98192 apt-listbugs_0.1.13.tar.xz e39828e77ec0ab9e031d18624122db1b76cca7e199b445b03f42245002d46f51 68044 apt-listbugs_0.1.13_all.deb Files: 67b4c3d057c3cdb478f18ed5b37d3c90 1751 admin optional apt-listbugs_0.1.13.dsc d4539c92122a28d288daef05b090d051 98192 admin optional apt-listbugs_0.1.13.tar.xz 83b300b170772c2e17043d09e2327561 68044 admin optional apt-listbugs_0.1.13_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJTQZIjAAoJEE+fbVUO1hIqLdYP+wYhecFxDGOQpXo2xPkVhx2c 2QvwUR+AVhWmhy7hZhFLo0mFYQRSBqmVmZqkgMnHPETUxFPw9vIyxtJdTZ09H9lp v3tTBMjTgIxIWE7Ah88K8fA0aGXnLyg68AirBdp0qL1cJLgbcz15Emi/cBUExyzX usdzQeSi2C37jeDmfF2LZjyn6OSuC1N6CTyrAT4Mw49nYNNb3ZDN5ZiWzAiyMHRt REh5QA70EPZY5cpll5Sya3oDgbW5g2xF6ZT3k6PPzbs25XxYsp8CIeEPyaAN4TQr VJNGcjE0pPRtyrxRRiHzQ24+QCfI/0THNuFAeFj4BiDmx0xTHrvHHuKeCybQI5l0 GXQt7ad6SrT4EDq1ncXjn7W4e6jyoeURP/ZO4OypsB8mQks0ntNEfgpjgCTN0/9C eAnIWKwMWfQTe+hKUGU7pN7dZZDqsjbU4A8L+PLebE09E9N0E3YmIXdTiYyr5Z4U jg5l3mcS1LeVhgN5uX696lWsnB4xBJMgzi41tWwxN5TXc/PlPhaTa3RwJeYgHpB9 XDYo0Q5Ac+A1B43pWMkgAiT0UBDCyhdWAj1CbyMXoGxXfkCF7SAxJUxYK33Hqrhd grzJ/WCuQiGu9T7Y+h4+mNigPv6aF5StM83hfcXVRKtSsscc7jgSeCCuebBZtVR4 THExktyGWTpSiwYe/lY0 =fSXt -----END PGP SIGNATURE-----
--- End Message ---
