Bug#351693: status of #351693?
On Sat, May 20, 2006 at 10:57:20AM -0700, Rob Browning wrote: At this point, my best guess is that this may be a bug in 1.6.7 that has been fixed in 1.6.8. I believe a number of GC and syntax related bugs have been fixed since 1.6.7, and I wouldn't be surprised if one of those is the culprit. Unfortunately, the only way I know of to reproduce this problem is to upload a new package for the autobuilders, which isn't a particularly friendly debugging process. guile-1.6 has pleasantly trivial build-dependencies, so you ought to be able to do a test build of 1.6.8 in merulo's unstable chroot without even needing to contact debian-admin. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Bug#351693: status of #351693?
Steve Langasek [EMAIL PROTECTED] writes: On Sat, May 20, 2006 at 10:57:20AM -0700, Rob Browning wrote: At this point, my best guess is that this may be a bug in 1.6.7 that has been fixed in 1.6.8. I believe a number of GC and syntax related bugs have been fixed since 1.6.7, and I wouldn't be surprised if one of those is the culprit. Unfortunately, the only way I know of to reproduce this problem is to upload a new package for the autobuilders, which isn't a particularly friendly debugging process. guile-1.6 has pleasantly trivial build-dependencies, so you ought to be able to do a test build of 1.6.8 in merulo's unstable chroot without even needing to contact debian-admin. As is mentioned in the bug log, test builds in merulo's unstable chroot work fine. The bug does not manifest itself under such conditions, and is seen only in the buildd environment. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
At this point, my best guess is that this may be a bug in 1.6.7 that has been fixed in 1.6.8. I believe a number of GC and syntax related bugs have been fixed since 1.6.7, and I wouldn't be surprised if one of those is the culprit. Unfortunately, the only way I know of to reproduce this problem is to upload a new package for the autobuilders, which isn't a particularly friendly debugging process. However, I'm in the process of releasing 1.6.8 upstream (cleaning up copyright, etc.), and then I'll upgrade Debian's package. I suspect I'll be able to finish within a week or so. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Rob Browning [EMAIL PROTECTED] writes: At this point, my best guess is that this may be a bug in 1.6.7 that has been fixed in 1.6.8. I believe a number of GC and syntax related bugs have been fixed since 1.6.7, and I wouldn't be surprised if one of those is the culprit. Unfortunately, the only way I know of to reproduce this problem is to upload a new package for the autobuilders, which isn't a particularly friendly debugging process. It's perfectly reasonable to upload 1.6.8 without knowing whether it fixes this particular bug. So I would go ahead and do that once it's ready. However, I'm in the process of releasing 1.6.8 upstream (cleaning up copyright, etc.), and then I'll upgrade Debian's package. I suspect I'll be able to finish within a week or so. Rock on! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Thomas Bushnell BSG [EMAIL PROTECTED] writes: Can you please work on #351693? Perhaps simply following the suggestion in the bug report would solve the problem; I don't know. But regardless, it's silly that such a small thing should be causing problems for three months now. At least when I looked here http://people.debian.org/~igloo/package-status.php?package=guile-1.6 ia64 appeared (and still appears) to be building. Of course it's been over a week, so I would imagine something's wrong. Where did you see the log describing the failure? -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Rob Browning [EMAIL PROTECTED] writes: Thomas Bushnell BSG [EMAIL PROTECTED] writes: Can you please work on #351693? Perhaps simply following the suggestion in the bug report would solve the problem; I don't know. But regardless, it's silly that such a small thing should be causing problems for three months now. At least when I looked here http://people.debian.org/~igloo/package-status.php?package=guile-1.6 ia64 appeared (and still appears) to be building. Of course it's been over a week, so I would imagine something's wrong. Where did you see the log describing the failure? http://buildd.debian.org/build.php?arch=pkg=guile-1.6 The ia64 buildd admin clearly has just not processed the failing log. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Thomas Bushnell BSG [EMAIL PROTECTED] writes: http://buildd.debian.org/build.php?arch=pkg=guile-1.6 The ia64 buildd admin clearly has just not processed the failing log. Ahh. This isn't (or may not be) the same problem. It's not failing in the test suite, but rather when trying to build the docs. Based on a recent discussion on guile-devel, I have a suspicion about what might be causing the trouble. I'll try to look in to it this evening. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Rob Browning [EMAIL PROTECTED] writes: Thomas Bushnell BSG [EMAIL PROTECTED] writes: http://buildd.debian.org/build.php?arch=pkg=guile-1.6 The ia64 buildd admin clearly has just not processed the failing log. Ahh. This isn't (or may not be) the same problem. It's not failing in the test suite, but rather when trying to build the docs. I don't know what you're talking about. At the end of that page is the link to the ia64 build of version 1.6.7-3. Clicking on that link brings you to the failing build from April 29, 2006, at the following URL: http://buildd.debian.org/fetch.php?pkg=guile-1.6ver=1.6.7-3arch=ia64stamp=1146285308file=logas=raw At the end of that log, is the following error, which generates the failure exit status: make[3]: Entering directory `/build/buildd/guile-1.6-1.6.7' Testing /build/buildd/guile-1.6-1.6.7/pre-inst-guile ... with GUILE_LOAD_PATH=/build/buildd/guile-1.6-1.6.7/test-suite ERROR: In procedure variable-set-name-hint!: ERROR: Wrong type argument in position ~A (expecting ~A): ~S FAIL: check-guile === 1 of 1 tests failed === make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/build/buildd/guile-1.6-1.6.7' This looks for all the world like a failure in the test suite, and the identical one in the original bug report. I see no indication of a failure in building docs. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Thomas Bushnell BSG [EMAIL PROTECTED] writes: I don't know what you're talking about. Actually, I just clicked on the wrong link. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Rob Browning [EMAIL PROTECTED] writes: Thomas Bushnell BSG [EMAIL PROTECTED] writes: I don't know what you're talking about. Actually, I just clicked on the wrong link. Oh good, it seemed like we were surely looking at different files entirely. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351693: status of #351693?
Can you please work on #351693? Perhaps simply following the suggestion in the bug report would solve the problem; I don't know. But regardless, it's silly that such a small thing should be causing problems for three months now. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
