Bug#691793: FTBFS on kfreebsd-*
Package: ruby1.8 Version: 1.8.7.358-5 Severity: serious Hi, ruby1.8 FTBFSes on kfreebsd-*, see https://buildd.debian.org/status/package.php?p=ruby1.8 Cheers, Moritz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby1.8 depends on: ii libc6 2.13-35 ii libruby1.8 1.8.7.358-4 ruby1.8 recommends no packages. Versions of packages ruby1.8 suggests: pn ri1.8 none pn ruby1.8-examples none -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691793: FTBFS on kfreebsd-*
tags 691793 + patch fixed 691793 1.8.7.358-4 thanks Hi, Explanation for the ruby1.8 FTBFS is here: http://lists.debian.org/508050a1.6000...@pyro.eu.org It is necessary to restore the timeout on the testsuite (unless we can figure out the reason for the thread-related hangs, in several places). diff --git a/debian/rules b/debian/rules index bc261ab..5f5df9c 100755 --- a/debian/rules +++ b/debian/rules @@ -65,7 +65,7 @@ common-post-build-arch:: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) # avoid running drb tests -- they make buildds hang forever mv test/drb _test_drb - -make test-all + -timeout 1h make test-all mv _test_drb test/drb endif Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#691793: FTBFS on kfreebsd-*
Processing commands for cont...@bugs.debian.org: tags 691793 + patch Bug #691793 [ruby1.8] FTBFS on kfreebsd-* Added tag(s) patch. fixed 691793 1.8.7.358-4 Bug #691793 [ruby1.8] FTBFS on kfreebsd-* Marked as fixed in versions ruby1.8/1.8.7.358-4. thanks Stopping processing here. Please contact me if you need assistance. -- 691793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691793: FTBFS on kfreebsd-*
Hi Steven, Steven Chamberlain escreveu: tags 691793 + patch fixed 691793 1.8.7.358-4 Are you sure of that? the difference between -4 and -5 does not look like causing this at all. I am testing on a kfreebsd-amd64 porterbox. That said, I am not against re-adding the timeout to the tests, but I will probably make it specific to kfreebsd-*. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#691793: FTBFS on kfreebsd-*
notfixed 691793 1.8.7.358-4 found 691793 1.8.7.358-4 fixed 691793 1.8.7.358-3 done On 29/10/12 21:29, Antonio Terceiro wrote: Are you sure of that? the difference between -4 and -5 does not look like causing this at all. I am testing on a kfreebsd-amd64 porterbox. Sorry Antonio, I meant that the change from -3 to -4 introduced it, by removing the timeout. I agree the remaining problems during the testsuite seem specific to GNU/kFreeBSD and GNU/Hurd, so maybe the timeout can be applied only to those non-Linux platforms. Thank you, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: Bug#691793: FTBFS on kfreebsd-*
Processing commands for cont...@bugs.debian.org: notfixed 691793 1.8.7.358-4 Bug #691793 [ruby1.8] FTBFS on kfreebsd-* No longer marked as fixed in versions ruby1.8/1.8.7.358-4. found 691793 1.8.7.358-4 Bug #691793 [ruby1.8] FTBFS on kfreebsd-* Marked as found in versions ruby1.8/1.8.7.358-4. fixed 691793 1.8.7.358-3 Bug #691793 [ruby1.8] FTBFS on kfreebsd-* Marked as fixed in versions ruby1.8/1.8.7.358-3. done Unknown command or malformed arguments to command. On 29/10/12 21:29, Antonio Terceiro wrote: Unknown command or malformed arguments to command. Are you sure of that? the difference between -4 and -5 does not look Unknown command or malformed arguments to command. like causing this at all. I am testing on a kfreebsd-amd64 porterbox. Unknown command or malformed arguments to command. Sorry Antonio, I meant that the change from -3 to -4 introduced it, by Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 691793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
