Bug#826175: xargs: Segfaults on hurd
On 2016-06-03 James Clarkewrote: > Package: findutils > Version: 4.6.0+git+20160126-2 > User: debian-hurd@lists.debian.org > Usertags: hurd > X-Debbugs-CC: debian-hurd@lists.debian.org > The latest version of findutils segfaults on hurd: > debian-hurd:git-src james% echo '' | xargs > xargs: echo: terminated by signal 11 > This seems to happen whatever input and arguments are given to xargs > (except for things like --version which cause it not to execute anything > else). Downgrading to the previous built version (4.4.2-10) works, so > this is a regression. I suspect a broken build. Only single build of findutils > 4.4 succeeded on hurd (4.6.0+git+20160126-2) and afaict for this build the testsuite run was manually disabled (probably DEB_BUILD_OPTIONS nocheck). A rebuild with testsuite half a day later failed. This should not have ended up in the archive. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Still Failing: g-i-installation_debian_sid_daily_hurd_lxde/172
See https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/172/ and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/172//console and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/172//artifact/results/ if there are any.
Failure: g-i-installation_debian_sid_daily_hurd_lxde/171
See https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/171/ and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/171//console and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/171//artifact/results/ if there are any.
crosshurd_1.7.51_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jun 2016 13:17:51 +0200 Source: crosshurd Binary: crosshurd Architecture: source all Version: 1.7.51 Distribution: unstable Urgency: medium Maintainer: GNU Hurd MaintainersChanged-By: Samuel Thibault Description: crosshurd - Install a Debian system Closes: 825229 Changes: crosshurd (1.7.51) unstable; urgency=medium . [ Rodrigo Valiña Gutiérrez ] * Add gnumach.gz symlink for dumb update-grub scripts (Closes: Bug#825229). . [ Samuel Thibault ] * Bump gnumach version to 1.7. Checksums-Sha1: c289dec0d576723f2b038274bcb3bc8dbc0998f3 1479 crosshurd_1.7.51.dsc 4981426a74f27599cdeabdb4d70141e05b973365 21290 crosshurd_1.7.51.tar.gz cadc8967c5683e174e0cefe9732452d705b325ae 20584 crosshurd_1.7.51_all.deb Checksums-Sha256: 98331ca76021af04ebf4052fc8f9b766068ee4d3d55dd88c40903e77f35dbc3c 1479 crosshurd_1.7.51.dsc 1a505fcc1b8c543be141853b0c26b3f3d7bc9d7fe138e512e681ca07ad06db14 21290 crosshurd_1.7.51.tar.gz ae3135c700b87c6d8ef58f953deff37063c94e24ffe32e0423df31a904d78b29 20584 crosshurd_1.7.51_all.deb Files: 8ae78a5b3908b117b8a1b99af079209b 1479 misc extra crosshurd_1.7.51.dsc 3fcbe5efb884de44a883aacdb6daa456 21290 misc extra crosshurd_1.7.51.tar.gz 392dea34e199de59f00eaa3def8a9a2a 20584 misc extra crosshurd_1.7.51_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXUWfhAAoJEPs9hU7TiF8YcbAQALD+fWiZ/AZyJDgTAIY3OzFu Y1aVqNjXsFGAVQUA3e392yHTFBgJsSFzr3jH+RmGCmSTRq1qfXBwpRgjSzkUShjY c+ojZ4nDsxvi7qglFW6GOhi5b1Tzp59w0U/xXmg6zGJKPp+hDhTCK5Ji/oLnQDTs nb3Lj3y2LAn1BYQwfRsH9Y9iyiEibJ3l0I95dvx3sL6SUr/su+yZufhfM7ijLyDj WqzSQktS/gBxYWKf+1jPmGI6+yxpAm66nPoUojARxb0mxZxJ6i65eOsOZCs2CFrf YkBWCVEvXLi4zP7s7McOqkhkdCcWk4YQRfvFM1uAybJQG2flrSYLT3bA62+33bS0 fkRBCS24aBpctLrdHwQowuTzfumd85XGAO2pOrwHqjnsYjmU7rlW/CcHMHaG//hK 5FS7+JTX6g6KEpDLPyzPxW07w9d39oKp5tyrp+8zDaiQh5TkmooiIhppw75ZG/Xm eELYax3d0NQVFyJlBIcTvraPQ+7kTLD5yIaU83yXWsCaWf7R8RPPQX4WfoQ0NaGU 8HvNEa1wWX5stNT/iSlvhPZNyMnBK1mfNftegPp1XiM8o0JxMacFYJwo1+kuh/a+ Sirvb0kQ91iwhQS/E6rhNmTpBpJk6egTt1U32W6iVET5Yi0ZQ9UQc+xa5ME6k7Ui aiCoQs8sYCY86CQmBygx =Yw9N -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#825229: marked as done (crosshurd: Incompatibility with update-grub. Fails to boot.)
Your message dated Fri, 03 Jun 2016 11:49:51 + with message-idand subject line Bug#825229: fixed in crosshurd 1.7.51 has caused the Debian Bug report #825229, regarding crosshurd: Incompatibility with update-grub. Fails to boot. 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 ow...@bugs.debian.org immediately.) -- 825229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: crosshurd Version: 1.7.50 Severity: normal Tags: patch Running crosshurd to install in a disk partition and then running update-grub, rebooting and selecting the Hurd entry, fails to boot because the Grub does not find /boot/gnumach.gz (there is /boot/gnumach-1.6-486.gz). The following patch solves the problem in my case: - --- makehurddir.sh 2016-05-22 16:28:32.0 +0200 +++ makehurddir2.sh 2016-05-24 21:25:48.678706572 +0200 @@ -43,6 +43,8 @@ if [ -e $TARGET/var/cache/apt/archives/gnumach-image-1.6-486_* ] ; then extract gnumach-image-1.6-486 +# place symlink for compatibility with update-grub (/etc/grub.d/30_os-prober) +ln -s gnumach-1.6-486.gz "$TARGET/boot/gnumach.gz" fi if [ -e $TARGET/var/cache/apt/archives/libbz2-1.0_* ] ; then - Afterwards, the Hurd starts to boot but fails (hangs) with the following error (maybe an issue with partition names): start ext2fs: ext2fs: device:(hostdisk//dev/sda,msdos2): No such device or address Also I have observed that, running "grep TARGET /usr/share/crosshurd/*" yields some results with "$TARGET/..." quoted and some others not, so if we run crosshurd with a path with spaces, it may fail. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=gl_ES.utf8, LC_CTYPE=gl_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages crosshurd depends on: ii dialog1.2-20140911-1 ii dpkg-dev 1.17.26 Versions of packages crosshurd recommends: pn attr crosshurd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: crosshurd Source-Version: 1.7.51 We believe that the bug you reported is fixed in the latest version of crosshurd, 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 825...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated crosshurd 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jun 2016 13:17:51 +0200 Source: crosshurd Binary: crosshurd Architecture: source all Version: 1.7.51 Distribution: unstable Urgency: medium Maintainer: GNU Hurd Maintainers Changed-By: Samuel Thibault Description: crosshurd - Install a Debian system Closes: 825229 Changes: crosshurd (1.7.51) unstable; urgency=medium . [ Rodrigo Valiña Gutiérrez ] * Add gnumach.gz symlink for dumb update-grub scripts (Closes: Bug#825229). . [ Samuel Thibault ] * Bump gnumach version to 1.7. Checksums-Sha1: c289dec0d576723f2b038274bcb3bc8dbc0998f3 1479 crosshurd_1.7.51.dsc 4981426a74f27599cdeabdb4d70141e05b973365 21290 crosshurd_1.7.51.tar.gz cadc8967c5683e174e0cefe9732452d705b325ae 20584 crosshurd_1.7.51_all.deb Checksums-Sha256: 98331ca76021af04ebf4052fc8f9b766068ee4d3d55dd88c40903e77f35dbc3c 1479 crosshurd_1.7.51.dsc 1a505fcc1b8c543be141853b0c26b3f3d7bc9d7fe138e512e681ca07ad06db14 21290 crosshurd_1.7.51.tar.gz ae3135c700b87c6d8ef58f953deff37063c94e24ffe32e0423df31a904d78b29 20584 crosshurd_1.7.51_all.deb Files: 8ae78a5b3908b117b8a1b99af079209b 1479 misc extra crosshurd_1.7.51.dsc 3fcbe5efb884de44a883aacdb6daa456 21290 misc extra crosshurd_1.7.51.tar.gz 392dea34e199de59f00eaa3def8a9a2a 20584 misc extra crosshurd_1.7.51_all.deb
Processing of crosshurd_1.7.51_amd64.changes
crosshurd_1.7.51_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: crosshurd_1.7.51.dsc crosshurd_1.7.51.tar.gz crosshurd_1.7.51_all.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Re: Bug#826043: apt: gpg validation fails on hurd
Hi, (purely optional mail follows) On Fri, Jun 03, 2016 at 11:21:41AM +0200, Adam Borowski wrote: > On Fri, Jun 03, 2016 at 02:25:45PM +0530, Ritesh Raj Sarraf wrote: > > On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote: > > From what you've explained, this bug should be reassigned to APT then ? > > It has been filed on apt and never been assigned elsewhere. > And, David already fixed it in git, tagging the bug +pending. > He responded[1] only to 826043-submitter (ie, me and the bug docket) > without CC:ing debian-hurd@l.d.o. Which I'm hereby doing. [Not sure I would have included d-hurd@ even if I had manually replied (but I thought buglog & commit message [1] will be enough text already and hadn't really anything to add) mainly as this isn't really hurd specific, just easier to 'see' as a problem as on hurd it actually fails while on linux it 'just' generates a warning which is hidden in the 'apt update' case, but manual usage of apt-key should have made them visible (sometimes at least). That also means I haven't actually tested it on hurd, so if anyone wants to… testers are always welcome!] btw: I just checked: I introduced the first of the two finds (which is the more obvious problem as that codepath is used more) on 7 Jul 2015 (25f27319) [the other is 6 Dec 2015], so that problem isn't recent but lingers there since 1.1 and I have to wonder if something changed in regards to this on hurd (or d-i) or if that really is some huge Baader-Meinhof bias… [2] (and I am bit surprised we had nobody on non-hurd complain about 'strange' messages being emitted while using apt-key – but perhaps that just means nobody is using apt-key anymore… if only that were true…) Best regards David Kalnischkies [1] The mail isn't even sent by me via a tool, but by a git hook: https://wiki.debian.org/Alioth/Git#Marking_closed_bugs_as_pending_in_BTS [2] I have these "how on earth could we miss that for so long?!?" moments quite often recently… which is another instance itself… signature.asc Description: PGP signature
Re: Bug#826043: apt: gpg validation fails on hurd
On Fri, Jun 03, 2016 at 02:25:45PM +0530, Ritesh Raj Sarraf wrote: > On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote: > > So, to summarize, the issue is that since apt-get update runs find as a > > non-root user, running it from a 700 directory breaks find. > > Thank you for the root cause. I am hitting the same problem on my Hurd box. > > From what you've explained, this bug should be reassigned to APT then ? It has been filed on apt and never been assigned elsewhere. And, David already fixed it in git, tagging the bug +pending. He responded[1] only to 826043-submitter (ie, me and the bug docket) without CC:ing debian-hurd@l.d.o. Which I'm hereby doing. I'm not sure whether the choose-mirror failure in d-i is a symptom of this bug, but because of the timing I assume so, and we'll soon know if this is the case. Thanks Samuel and David! [1]. Via an automated tool, so it's hard to blame him, especially that the debian-hurd CC was included only in a single later message. -- An imaginary friend squared is a real enemy.
Re: Bug#826043: apt: gpg validation fails on hurd
On Thu, 2016-06-02 at 01:13 +0200, Samuel Thibault wrote: > On Hurd, getting $PWD from the 700 directory fails, and find thus aborts > immediately, without emitting any output, and thus no keyring is found. > > So, to summarize, the issue is that since apt-get update runs find as a > non-root user, running it from a 700 directory breaks find. > > I guess it may make sense for apt to chdir to e.g. / before running the > find command, so that we are sure that find doesn't get any issue? > > Actually it's pure luck that the script doesn't completely fail on Linux > when find fails due to not being able to restore the cwd: since the find > command is only used as parameter of a for loop, the returned value > is ignored by sh. Had the find command output been first stored in a > variable, the script would have aborted... Thank you for the root cause. I am hitting the same problem on my Hurd box. From what you've explained, this bug should be reassigned to APT then ? -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response signature.asc Description: This is a digitally signed message part