buildd failures for amd64?
Hi, I from time-to-time notice that amd64 doesn't have a package in unstable/testing, while most (all) other archs do. At the moment for example natios-plugins is compiled for most archs, but the amd64 arch reports maybe-failed: http://buildd.debian.org/fetch.php?pkg=nagios-pluginsver=1.4.3.0cvs.20060707-2arch=amd64stamp=1152532502file=logas=raw http://buildd.debian.org/build.php?arch=pkg=nagios-plugins When trying myself apt-get source nagios-plugins; cd n*; fakeroot ./debian/rules binary on my amd64 box, I get the proper nagios-plugins*.deb's in 136 seconds, so it looks like there was something wrong with the build box for amd64. So, I wonder, could my box help with the compiling (I have hd and bandwidth to burn)? (If so, does anyone know where to apply?) Thanks! (I used to be a debian developer, [EMAIL PROTECTED]) -- Groetjes, joostje 005608398914893a14f10ab33944162d - 1d8aab438cd59e35b101349479f50ad69c4f52b10945c66db1527492859d1172 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: buildd failures for amd64?
Je 2006/07/20(4)/13:07, Goswin von Brederlow skribis: checking for ICMP ping syntax... Terminated make: *** [config.status] Error 1 Build killed with signal 15 after 150 minutes of inactivity Yes, I've seen it in the webpage. But it doesn't appear when I run fakeroot debian/rules binary manually. So either something strange is going on on the buildd amd64 machine, or the package has an unreproducing bug. In the past we had a few packages just hang in sbuild during build for no concernable reasons. This might be a new one with the same effect. Yes. Although most packages are available for amd64, whenever I noticed an unavailable package, I could manually build it without any changes. So maybe it would be useful to send a STOP instead of TERM signal to the process (and an email to the owner), go on with the next package, and let the owner of the machine find out later what went wrong with the build (connecting to the stopped process with gdb and friends). (with a max number of STOPped builds of cource) To run a buildd you would also need to be a DD. Well, I still get my [EMAIL PROTECTED] email:). Maybe I still am a DD? But you can do what you do now. OK, that's what I'll do then. -- Groetjes, joostje 005608398914893a14f10ab33944162d - 1d8aab438cd59e35b101349479f50ad69c4f52b10945c66db1527492859d1172 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broken applications: Openoffice on AMD64
Je 2006/07/20(4)/14:07, Joost Witteveen skribis: I've been using a 64 bit OOo for a couple weeks now, and have been quite pleased with it. There's a working AMD64 port here: http://people.debian.org/~rene/openoffice.org/2.0.3/amd64/ That's the 2.0.3-1 version, released 2006-07-01, right? That must be the same version announced here: http://openoffice.debian.net/ where it's described as: Note that they sttill are not usable; for example saving doesn't work... Now, my uses of OO usually don't include saving anything, but I do imagine that to be important for some people. (I run debian-amd64 on a server, where I have no need for OO, so I haven't tried it myself). Or does saving generally work, except for some exotic file formats like .doc? -- Groetjes, joostje 005608398914893a14f10ab33944162d - 1d8aab438cd59e35b101349479f50ad69c4f52b10945c66db1527492859d1172 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
