Bug#708675: openjdk-6-doc empty when built on many architectures
Source: openjdk-6 Version: 6b27-1.12.5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) When building openjdk-6 on many architectures, the documentation package ends up empty with no error indicating you shouldn't have tried. It seems the problem is that debian/rules contians: # assume we don't build binary indep packages on these architectures ifeq ($(with_docs),yes) ifeq (,$(filter $(DEB_HOST_ARCH), amd64 i386 lpia)) CONFIGURE_ARGS += --disable-docs endif else CONFIGURE_ARGS += --disable-docs endif This means you you do dpkg-buildpackage -b on say a powerpc, you end up with all the .deb files generated, but openjdk-6-doc doesn't actually contain anything useful and hence causes other things to fail to build. There has got to be a better way to disable building docs when only binary-arch is being built, and to let everyone actually be able to generate the all packages if they want to. I know Debian's buildd's don't generate the all packages, but I don't think that excuses a package that builds incorrectly just because it isn't on x86/amd64 (or whatever lpia is. That one is new to me). I think it should be changed to: ifneq ($(with_docs),yes) CONFIGURE_ARGS += --disable-docs endif It is not the package's job to second guess the user, so the assumption is wrong. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 powerpc Kernel: Linux 3.8-trunk-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: The missing files
On Thu, May 16, 2013 at 01:38:47AM -0400, tony mancill wrote: On 05/15/2013 01:05 PM, Len Sorensen wrote: So the missing files in geronimo-jta-1.1-spec-java are: wheezy/usr/share/java: lrwxrwxrwx 1 root root 99 May 15 15:31 geronimo-jta_1.1_spec-1.1.1.jar - ../maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar lrwxrwxrwx 1 root root 99 May 15 15:31 geronimo-jta_1.1_spec.jar - ../maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar I don't know if a change in maven or something else is responsible for this not working correctly anymore. This sounds familiar - based on when geronimo-jta-1.1-spec_1.1.1-2 entered unstable, it would have been built with a version of maven-debian-helper *prior* to 1.5, which is before a behavior change than necessitated a number of rebuilds/uploads to ensure that jars were installed in /usr/share/java and not only in the debian maven repo. (And actually, I just ran into the same issue when trying to rebuild libgetopt-java to transition it from experimental to unstable. I'm not sure yet if that means that the version of m-d-h in experimental reverts the default such that the --java-lib option is assumed if not provided.) In any event, I believe the attached patch should address the problem with the build for you. Would you mind retying your local build and reporting back? Thank you, tony diff -Nru geronimo-jta-1.1-spec-1.1.1/debian/changelog geronimo-jta-1.1-spec-1.1.1/debian/changelog --- geronimo-jta-1.1-spec-1.1.1/debian/changelog 2011-09-24 13:23:00.0 -0700 +++ geronimo-jta-1.1-spec-1.1.1/debian/changelog 2013-05-15 22:30:35.0 -0700 @@ -1,3 +1,11 @@ +geronimo-jta-1.1-spec (1.1.1-3) unstable; urgency=low + + * Team upload. + * Update pom to install jars in /usj for maven-debian-helper +behavior change. + + -- tony mancill tmanc...@debian.org Wed, 15 May 2013 22:28:00 -0700 + geronimo-jta-1.1-spec (1.1.1-2) unstable; urgency=low * Fix compatibility symlink. (Closes: #642684) diff -Nru geronimo-jta-1.1-spec-1.1.1/debian/libgeronimo-jta-1.1-spec-java.poms geronimo-jta-1.1-spec-1.1.1/debian/libgeronimo-jta-1.1-spec-java.poms --- geronimo-jta-1.1-spec-1.1.1/debian/libgeronimo-jta-1.1-spec-java.poms 2011-09-24 13:23:00.0 -0700 +++ geronimo-jta-1.1-spec-1.1.1/debian/libgeronimo-jta-1.1-spec-java.poms 2013-05-15 22:30:35.0 -0700 @@ -23,4 +23,4 @@ # --ignore-pom: don't install the POM with mh_install or mh_installpoms. To use with POM files that are created # temporarily for certain artifacts such as Javadoc jars. # -pom.xml --no-parent --has-package-version +pom.xml --no-parent --has-package-version --java-lib That would appear to fix the problem. I will try and see if that then solves the jetty compile problem (I suspect it will). -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: The missing files
On Thu, May 16, 2013 at 11:01:20AM -0400, Len Sorensen wrote: That would appear to fix the problem. I will try and see if that then solves the jetty compile problem (I suspect it will). And it did. I have now patched maven-debian-helper with the patch from 688043 which is already included in the version in experimental, and this has solved the problem without having to apply the patch to geronimo-jta-1.1-spec. So really this is probably simply something bug 688043 solves, although of course that doesn't solve the problem in wheezy. Maybe that will fix a couple of other FTBFS I am looking at. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: jetty: Fails to build from source on wheezy
Package: jetty Version: 6.1.26-1 Severity: serious Justification: fails to build from source (but built successfully in the past) I am trying to create a small subset of wheezy that is self contained, and as part of building things, jetty failed to build. Strangely it looks a lot like an old bug #642783, although that was supposedly fixed by an update to geronimo, and the fixed version of that is what is in wheezy. I can provide the build log if that would help, but the error seen is: [javadoc] Constructing Javadoc information... [javadoc] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:19: cannot find symbol [javadoc] symbol : class UserTransaction [javadoc] location: package javax.transaction [javadoc] import javax.transaction.UserTransaction; [javadoc] ^ [javadoc] Standard Doclet version 1.6.0_27 [javadoc] Building tree for all the packages and classes... [javadoc] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:58: cannot find symbol [javadoc] symbol : class UserTransaction [javadoc] location: class org.mortbay.jetty.plus.naming.Transaction [javadoc] public Transaction (UserTransaction userTransaction) [javadoc] ^ and [javac] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:19: cannot find symbol [javac] symbol : class UserTransaction [javac] location: package javax.transaction [javac] import javax.transaction.UserTransaction; [javac] ^ [javac] /build/www-data-jetty_6.1.26-1-i386-njNJoQ/jetty-6.1.26/modules/plus/src/main/java/org/mortbay/jetty/plus/naming/Transaction.java:58: cannot find symbol [javac] symbol : class UserTransaction [javac] location: class org.mortbay.jetty.plus.naming.Transaction [javac] public Transaction (UserTransaction userTransaction) [javac] ^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors Any idea what the problem is and how to fix it? -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: jetty: Fails to build from source on wheezy
On Wed, May 15, 2013 at 11:17:30AM -0400, tony mancill wrote: I am able to build the package in a clean wheezy chroot, so I'm not sure yet what's going on here yet. Any chance you're trying to build with a different JDK than the default-jdk? I am using sbuild, pointing at wheezy, so I would hope it picks the right one based on what the control file asks for. If you could provide a build log, that would be helpful. If you'd prefer, you can send it to me directly. Will do. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: jetty: Fails to build from source on wheezy
On Wed, May 15, 2013 at 11:36:47AM -0400, Cyril Brulebois wrote: (Random #-changes reader.) Len Sorensen lennartsoren...@ruggedcom.com (15/05/2013): On Wed, May 15, 2013 at 11:17:30AM -0400, tony mancill wrote: I am able to build the package in a clean wheezy chroot, so I'm not sure yet what's going on here yet. Any chance you're trying to build with a different JDK than the default-jdk? I am using sbuild, pointing at wheezy, so I would hope it picks the right one based on what the control file asks for. I've just created a brand new sbuild chroot for wheezy and run that: sbuild -As -d wheezy jetty_6.1.26-1.dsc and everything went fine. I can confirm that is true. On the other hand it seems if you recompile some of the dependancies it uses then it breaks. Now which dependancy could be breaking if you recompile it in wheezy to cause this problem I wonder. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: jetty: Fails to build from source on wheezy
On Wed, May 15, 2013 at 12:12:51PM -0400, Len Sorensen wrote: I can confirm that is true. On the other hand it seems if you recompile some of the dependancies it uses then it breaks. Now which dependancy could be breaking if you recompile it in wheezy to cause this problem I wonder. And first guess got it: If I build using wheezy official packages as build-deps, then jetty builds fine. If I replace just libgeronimo-jta-1.1-spec-java_1.1.1-2_all.deb with the one I rebuilt myself (in wheezy), then jetty fails to build. So it would seem rebuilding libgeronimo-jta-1.1-spec, results in something that doesn't work the same as what is in wheezy. I guess the bug has to be punted to libgeronimo-jta-1.1-spec then. Trying another rebuild of that package to see if it happens every time. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: jetty: Fails to build from source on wheezy
On Wed, May 15, 2013 at 02:55:58PM -0400, Len Sorensen wrote: And first guess got it: If I build using wheezy official packages as build-deps, then jetty builds fine. If I replace just libgeronimo-jta-1.1-spec-java_1.1.1-2_all.deb with the one I rebuilt myself (in wheezy), then jetty fails to build. So it would seem rebuilding libgeronimo-jta-1.1-spec, results in something that doesn't work the same as what is in wheezy. I guess the bug has to be punted to libgeronimo-jta-1.1-spec then. Trying another rebuild of that package to see if it happens every time. So if you rebuild under wheezy, you end up with some files missing: wheezy wheezy/usr wheezy/usr/share wheezy/usr/share/maven-repo wheezy/usr/share/maven-repo/org wheezy/usr/share/maven-repo/org/apache wheezy/usr/share/maven-repo/org/apache/geronimo wheezy/usr/share/maven-repo/org/apache/geronimo/specs wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian/geronimo-jta_1.1_spec-debian.jar wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian/geronimo-jta_1.1_spec-debian.pom wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1 wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar wheezy/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.pom wheezy/usr/share/java wheezy/usr/share/java/geronimo-jta_1.1_spec.jar wheezy/usr/share/java/geronimo-jta_1.1_spec-1.1.1.jar wheezy/usr/share/java/geronimo-jta-1.0.1b-spec.jar wheezy/usr/share/doc wheezy/usr/share/doc/libgeronimo-jta-1.1-spec-java wheezy/usr/share/doc/libgeronimo-jta-1.1-spec-java/changelog.Debian.gz wheezy/usr/share/doc/libgeronimo-jta-1.1-spec-java/copyright rebuild rebuild/usr rebuild/usr/share rebuild/usr/share/maven-repo rebuild/usr/share/maven-repo/org rebuild/usr/share/maven-repo/org/apache rebuild/usr/share/maven-repo/org/apache/geronimo rebuild/usr/share/maven-repo/org/apache/geronimo/specs rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian/geronimo-jta_1.1_spec-debian.jar rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/debian/geronimo-jta_1.1_spec-debian.pom rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1 rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.pom rebuild/usr/share/java rebuild/usr/share/java/geronimo-jta-1.0.1b-spec.jar rebuild/usr/share/doc rebuild/usr/share/doc/libgeronimo-jta-1.1-spec-java rebuild/usr/share/doc/libgeronimo-jta-1.1-spec-java/changelog.Debian.gz rebuild/usr/share/doc/libgeronimo-jta-1.1-spec-java/copyright No idea why wheezy/usr/share/java/geronimo-jta_1.1_spec.jar and wheezy/usr/share/java/geronimo-jta_1.1_spec-1.1.1.jar are gone when you rebuild libgeronimo-jta-1.1-spec. I suspect that's the problem though. The contents of the rebuild/usr/share/maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar file appears to be the same other than the manifest being a few bytes off in size. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708405: The missing files
So the missing files in geronimo-jta-1.1-spec-java are: wheezy/usr/share/java: lrwxrwxrwx 1 root root 99 May 15 15:31 geronimo-jta_1.1_spec-1.1.1.jar - ../maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar lrwxrwxrwx 1 root root 99 May 15 15:31 geronimo-jta_1.1_spec.jar - ../maven-repo/org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1/geronimo-jta_1.1_spec-1.1.1.jar I don't know if a change in maven or something else is responsible for this not working correctly anymore. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705306: quagga package should not contain header files and static libraries
Package: quagga Version: 0.99.22-1 Severity: serious Justification: Policy 8.4 As far as I understand packaging policy, header files and static libraries must go in a -dev package, and not be included in the main package. After all most people running a program are not going to be compiling add ons for it. Certainly the static library really doesn't make sense to include. It seems to me, quagga really should have a quagga package for the daemons, a libquagga for the shared libraries, and a libquagga-dev for the headers and static libraries. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 powerpc Kernel: Linux 3.8-trunk-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quagga depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii iproute20120521-3+b4 ii libc6 2.16-0experimental1 ii libcap21:2.22-1.2 ii libpam0g 1.1.3-9 ii libreadline6 6.2+dfsg-0.1 ii libtinfo5 5.9-10 ii logrotate 3.8.3-3 quagga recommends no packages. Versions of packages quagga suggests: pn snmpd none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657254: libnl-3-200: Fails to build from source due to missing build-dep on source-highlight
Package: libnl-3-200 Version: 3.2.3-2 Severity: serious Justification: fails to build from source (but built successfully in the past) libnl3 fails to build since it uses asciidoc and hence needs source-highlight. However asciidoc only recommends source-highlight which means buildd's won't have it installed and others might not have it installed. So either libnl3 needs an explicit build-dep on source-hightlight, or asciidoc needs to be made to require source-highlight. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnl-3-200 depends on: ii libc6 2.13-24 libnl-3-200 recommends no packages. libnl-3-200 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638589: libcaca: Missing build dependancies for documentation building.
Package: libcaca Version: 0.99.beta17-1 Severity: serious Tags: patch Justification: fails to build from source libcaca fails to build due to not finding xcolor.sty and sectsty.sty which are provided by latex-xcolor and texlive-latex-extra respectively. As a result the package fails to build. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613475: elinks fails to build from source.
On Mon, Feb 14, 2011 at 10:27:33PM -0500, Kumar Appaiah wrote: Could you please let me know if autoconf/automake are installed in the build environment? In other words, what is the output of dpkg -l | grep autoconf dpkg -l | grep automake If you do, this is a known bug (see URL:http://bugs.debian.org/592466). Please then try to remove those packages and rebuild. I am able to build in a clean sid chroot. I can confirm that. This is in fact a duplicate of bug 592466. Strange, since I thought I had started with a clean chroot, so not sure how automake and autoconf got in there. Well something for me to investigate. Given some of the buildd's have hit it too, perhaps something in build-essentials or something else at some point caused automake and autoconf to be added for some reason. Maybe sbuild is related. No idea yet. Thanks for the help though. This was the first FTBFS package I encountered in squeeze so far, and the fact it really isn't one is great. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613475: elinks fails to build from source.
Package: elinks Version: 0.12~pre5-2 Severity: serious Justification: fails to build from source Trying to compile elinks fails. This unfortunately happens both in unstable, testing and stable (ouch). This is the error: [MAKE all] src/ecmascript/spidermonkey make[4]: Entering directory `/tmp/elinks-0.12~pre5/build-main/src/ecmascript/spidermonkey' [CC] src/ecmascript/spidermonkey/document.o [CC] src/ecmascript/spidermonkey/form.o echo Did [CC] src/ecmascript/spidermonkey/heartbeat.o e/tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:61:68: error: macro get_opt_int passed 2 arguments, but takes just 1 /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c: In function ‘check_heartbeats’: /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:61: error: ‘get_opt_int’ undeclared (first use in this function) /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:61: error: (Each undeclared identifier is reported only once /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:61: error: for each function it appears in.) /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:88:62: error: macro get_opt_int passed 2 arguments, but takes just 1 /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c: In function ‘add_heartbeat’: /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:88: error: ‘get_opt_int’ undeclared (first use in this function) /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c: In function ‘done_heartbeat’: /tmp/elinks-0.12~pre5/src/ecmascript/spidermonkey/heartbeat.c:111: error: expected declaration or statement at end of input make[4]: *** [heartbeat.o] Error 1 make[4]: Leaving directory `/tmp/elinks-0.12~pre5/build-main/src/ecmascript/spidermonkey' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/elinks-0.12~pre5/build-main/src/ecmascript' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/elinks-0.12~pre5/build-main/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/elinks-0.12~pre5/build-main' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build command 'cd elinks-0.12~pre5 dpkg-buildpackage -b -uc' failed. E: Child process failed -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages elinks depends on: ii elinks-data 0.12~pre5-2 advanced text-mode WWW browser - d ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-2common error description library ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libfsplib0 0.11-1 FSP v2 protocol stack library - sh ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgpm2 1.20.4-3.3 General Purpose Mouse - shared lib ii libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k ii libidn111.18-1 GNU Libidn library, implementation ii libk5crypto31.8.3+dfsg-4 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries ii liblua505.0.3-4 Main interpreter library for the L ii liblualib50 5.0.3-4 Extension library for the Lua 5.0 ii libmozjs2d 1.9.1.16-4 The Mozilla SpiderMonkey JavaScrip ii libperl5.10 5.10.1-17shared Perl library ii libruby1.8 1.8.7.302-2 Libraries necessary to run Ruby 1. ii libtre5 0.8.0-2 regexp matching library with appro ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime elinks recommends no packages. Versions of packages elinks suggests: pn elinks-docnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: closed by David Bremner brem...@debian.org (Bug#594178: fixed in clisp 1:2.48-3.1)
6a769867d8b7e1885203b4ca5652aab6c5d38901945f0f92f56810d23f9fd5a4 9434445 clisp_2.48.orig.tar.gz 13979c5f77eaa0b3b58398148add13ad35cdf5e5c1222c49a0df0e886a0de765 24223 clisp_2.48-3.1.diff.gz 5b66abcd98a2481415cd9f22624d27a9b38c9ba89addbf9e58ddbbe0fe982fcc 1172692 clisp-doc_2.48-3.1_all.deb adfa950f3ad08931b0fdac7e9623d2ddec6024d0f1a99eca24a514bf34f6b61a 4721774 clisp_2.48-3.1_amd64.deb 5112b4f66bc09b63ff9f1954935dca02cbefc2930ce94f4eb3da92206caf803f 4038148 clisp-dev_2.48-3.1_amd64.deb Files: 70f97ac4697d75299970c1763de292e3 1693 lisp optional clisp_2.48-3.1.dsc 82275297d00ff10e481f8f244fa1d37f 9434445 lisp optional clisp_2.48.orig.tar.gz 24dfdd14fae2a64ca9a3384c661d4a1e 24223 lisp optional clisp_2.48-3.1.diff.gz 172a1d4475fd3844819482e105498e0b 1172692 doc optional clisp-doc_2.48-3.1_all.deb a77a607d710fc2dc1c345e2ba73b65b9 4721774 lisp optional clisp_2.48-3.1_amd64.deb 702883c58fd8bc56f35a7f4519463b59 4038148 lisp optional clisp-dev_2.48-3.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iJwEAQECAAYFAk0uas8ACgkQTiiN/0Um85mtpgQAnaiE1uV0oyfVOrL0zgTitwxU IjsapxNDgaYPmwc9LJABUB5qHfcBjkWIRgneKG7PtoC9TGINkoQIp0LhcgYh7XQw fg//ureAqvJubUVqef5ZOnve18qGnuUtJeAWvpx+Xv9QLFAln8sqYv55C7F+3+uJ usHa9KSPf+UmfKlW9LI= =c7XG -END PGP SIGNATURE- Received: (at submit) by bugs.debian.org; 12 Aug 2010 17:20:42 + Received: from mail2.ruggedcom.com ([204.50.148.11]) by busoni.debian.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from lennartsoren...@ruggedcom.com) id 1OjbSM-0004uP-4F for sub...@bugs.debian.org; Thu, 12 Aug 2010 17:20:42 + Received: from rceng01.eng.lan (10.200.2.11) by RCexchangesvr1 (10.200.2.21) with Microsoft SMTP Server id 8.2.176.0; Thu, 12 Aug 2010 13:15:09 -0400 Received: from rceng03.eng.lan (rceng03.eng.lan [10.200.17.13]) by rceng01.eng.lan (Postfix) with ESMTP id 3099214E30C; Thu, 12 Aug 2010 13:14:56 -0400 (EDT) Received: from root by rceng03.eng.lan with local (Exim 4.72) (envelope-from lennartsoren...@ruggedcom.com) id 1OjbMb-0005kH-QC; Thu, 12 Aug 2010 13:14:45 -0400 From: Len Sorensen lennartsoren...@ruggedcom.com To: Debian Bug Tracking System sub...@bugs.debian.org Date: Thu, 12 Aug 2010 13:14:45 -0400 Subject: clisp segfaults on install on powerpc system. Thread-Topic: clisp segfaults on install on powerpc system. Thread-Index: Acuy0PnvqY0vUMpcRkO/uou/CvsTqg== Message-ID: 20100812171445.22066.27218.report...@rceng03.eng.lan Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: delivered-to: sub...@bugs.debian.org x-spam-level: x-spam-status: No, score=-10.0 required=4.0 tests=AWL,BAYES_00,FOURLA, HAS_PACKAGE,IMPRONONCABLE_2,XMAILER_REPORTBUG autolearn=ham version=3.2.5-bugs.debian.org_2005_01_02 x-spam-checker-version: SpamAssassin 3.2.5-bugs.debian.org_2005_01_02 (2008-06-10) on busoni.debian.org x-greylist: delayed 341 seconds by postgrey-1.31 at busoni; Thu, 12 Aug 2010 17:20:42 UTC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Package: clisp Version: 1:2.48-3 Severity: grave Justification: renders package unusable In trying to dist-upgrade today, I got a segfault in clisp. Setting up clisp (1:2.48-3) ... Installing clc... ;; Loading file /usr/lib/clisp-2.48/install-clc.lisp ... ;; Loading file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp ... ;; Loaded file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp *** - handle_fault error2 ! address = 0x77946b98 not in [0x69a5a0d8,0x69b37000) ! SIGSEGV cannot be cured
Bug#601043: [buildd-tools-devel] Bug#605939: Bug#605939: Regression: Chroots with periods in the name no longer work.
On Sun, Dec 05, 2010 at 06:05:51PM -0500, Roger Leigh wrote:
This is hopefully fixed in git. This is the logic we're using:
bool
sbuild::is_valid_sessionname (std::string const name)
{
bool match = false;
static regex file_namespace(^[^:/,.][^:/,]*$);
static regex editor_backup(~$);
static regex debian_dpkg_conffile_cruft(dpkg-(old|dist|new|tmp)$);
if (regex_search(name, file_namespace)
!regex_search(name, editor_backup)
!regex_search(name, debian_dpkg_conffile_cruft)) {
match = true;
}
return match;
}
If there are no objections and we're correctly picking out all editor
and dpkg backup files, I think this is fixed.
From the updated documentation:
CHROOT NAMES
A number of characters or words are not permitted in a chroot name,
session
name or configuration filename. The name may not contain a leading
period
(‘.’). The characters ‘:’ (colon), ‘,’ (comma) and ‘/’ (forward
slash) are
not permitted anywhere in the name. The name may also not contain a
trail‐
ing tilde (‘~’). The rationale for these restrictions is given below.
‘.’A leading period could be used to create a name with a
relative path
in it, in combination with ‘/’, and this could allow
overwriting of
files on the host filesystem. Not allowing this character also
means
hidden files cannot be created. It also means some editor
backups
are automatically ignored. Periods are allowed anywhere else
in the
name.
‘:’A colon is used as a namespace delimiter, and so is not
permitted as
part of a chroot or session name. LVM snapshot names may
also not
contain this character due to a naming restriction by
lvcreate(8).
‘/’Names containing this character are not valid filenames. A
forward
slash would potentially allow creation of files in
subdirectories.
‘,’Commas are used to separate items in lists. Aliases are
separated by
commas and hence can't contain commas in their name.
‘~’Filenames containing trailing tildes are used for editor
backup
files, which are ignored. Tildes are allowed anywhere else
in the
name.
‘dpkg-old’
‘dpkg-dist’
‘dpkg-new’
‘dpkg-tmp’
These names may not appear at the end of a name. These are
saved
copies of conffiles used by the dpkg package manager, and
will be
ignored.
I am entirely satisfied with those rules. I wanted periods allowed in
the name but certainly have no need for a leading period and it does
make it simpler to avoid relative paths when you avoid the leading period.
Looks great to me. Thanks.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: closed by Peter Van Eynde pvane...@debian.org (Bug#592768: fixed in clisp 1:2.49-1)
On Thu, Oct 28, 2010 at 07:51:39AM -0400, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the clisp package: #592768: clisp segfaults on install on powerpc system. It has been closed by Peter Van Eynde pvane...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Peter Van Eynde pvane...@debian.org by replying to this email. I didn't think the bug could be closed until the fixed package entered the archives, which it certainly hasn't yet, especially since it depends on a package (libsigsegv) that isn't even in incoming yet. I wanted to test that it fixed the problem, but since there is no powerpc build of it yet and the build dependancies are missing, I can't. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597778: schroot: Stupid name restrictions is breaking existing setups for no good reason.
Package: schroot Version: 1.4.12-1 Severity: grave I just upgraded schroot to the current version in testing, and now I can't use it anymore because someone got the bright (not) idea that only alphanumeric, dashes and underscores should be allowed in chroot names. It was annoying enough when a while ago the config files started having that (undocumented unless you read the source code and without useful error message) restriction. Put it back to sanity please. If I want to name a chroot rr2.1.0 because that's what is in it, then that's my choice. While you are at it, let me choose the names of my config files too. Breaking existing users is NOT acceptable so stop doing that. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc64) Kernel: Linux 2.6.32-5-powerpc64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages schroot depends on: ii libboost-filesystem1.42.0 1.42.0-4 filesystem operations (portable pa ii libboost-program-options1.42. 1.42.0-4 program options library for C++ ii libboost-regex1.42.0 1.42.0-4 regular expression library for C++ ii libboost-system1.42.0 1.42.0-4 Operating system (e.g. diagnostics ii libc6 2.11.2-5 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-8 GCC support library ii liblockdev1 1.0.3-1.4 Run-time shared library for lockin ii libpam0g 1.1.1-6Pluggable Authentication Modules l ii libstdc++64.4.4-8The GNU Standard C++ Library v3 ii libuuid1 2.17.2-3.1 Universally Unique ID library ii schroot-common1.4.12-1 common files for schroot schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-module none (no description available) pn btrfs-tools none (no description available) ii debootstrap 1.0.23 Bootstrap a basic Debian system pn lvm2 none (no description available) ii unzip 6.0-4 De-archiver for .zip files -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: clisp segfaults on install on powerpc system.
Package: clisp Version: 1:2.48-3 Severity: grave Justification: renders package unusable In trying to dist-upgrade today, I got a segfault in clisp. Setting up clisp (1:2.48-3) ... Installing clc... ;; Loading file /usr/lib/clisp-2.48/install-clc.lisp ... ;; Loading file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp ... ;; Loaded file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp *** - handle_fault error2 ! address = 0x77946b98 not in [0x69a5a0d8,0x69b37000) ! SIGSEGV cannot be cured. Fault address = 0x77946b98. GC count: 0 Space collected by GC: 0 0 Run time: 0 34497 Real time: 0 610829 GC time: 0 0 Permanently allocated: 108736 bytes. Currently in use: 3721192 bytes. Free space: 198 bytes. Segmentation fault Building of new image failed! dpkg: error processing clisp (--configure):
Bug#521472: Missing file /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu
Package: linux-headers-2.6.29-1-common Version: 2.6.29-1 Severity: grave Justification: renders package unusable Trying to build anything against 2.6.29 headers on i386 fails due to a missing file. /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.29-1-common/arch/x86/Makefile_32.cpu: No such file or directory On i386, the x86 Makefile includes Makefile_32.cpu which is not included in the headers package. The 2.6.26 package did include this file and hence worked fine. I so far tried compiling alsa-source 1.0.19 and nvidia-kernel-source 180.29, and both failed with the same error. -- System Information: Debian Release: 5.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502219: closed by Giuseppe Iuculano [EMAIL PROTECTED] (Re: Bug#502219: procinfo: Segfaults with large number of interrupts.)
On Wed, Oct 15, 2008 at 10:13:06AM +0200, Giuseppe Iuculano wrote: I prepared an upload for tpu, and I'm waiting an ack from release-team [0] Excellent. You can find a preliminary package for lenny [1], let me know if it fixes this issue. [0] http://lists.debian.org/debian-release/2008/10/msg00662.html [1] http://ctu.iuculano.it/procinfo-lenny/ I downloaded it, built it for i386, and ran it, and it didn't segfault, and seems to work. I like that you seem to have adjusted the printout to have room for 4 digit irqs now. Looks nicer that way. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502219: closed by Giuseppe Iuculano [EMAIL PROTECTED] (Re: Bug#502219: procinfo: Segfaults with large number of interrupts.)
On Tue, Oct 14, 2008 at 04:51:35PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the procinfo package: #502219: procinfo: Segfaults with large number of interrupts. It has been closed by Giuseppe Iuculano [EMAIL PROTECTED]. I do not consider this closed. You are wrong. Please reopen until it is fixed. I was actually considering marking it RC for Lenny. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502219: closed by Giuseppe Iuculano [EMAIL PROTECTED] (Re: Bug#502219: procinfo: Segfaults with large number of interrupts.)
On Tue, Oct 14, 2008 at 07:57:40PM +0200, Giuseppe Iuculano wrote: I understand your point of view, but this bug is marked as Fixed in version procinfo/1:2.0.208-1. This is correct and this remain an RC for Lenny. Well if it isn't being accepted into Lenny, then that doesn't help and most likely Lenny will end up with no procinfo at all. Wouldn't it be better to make a procinfo 18-3 with the simple fix which is much more likely to be accepted into Lenny and then get the new procinfo-ng into the next major release? A fixed package for etch would be nice too given it is a rather serious bug. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330159: Fix for 1.0-1 build on arm so nvu can enter testing
Package: nvu Version: 1.0-1 Severity: serious Tags: patch Justification: no longer builds from source nvu 1.0-1 currently fails to build on arm. Bug #325532 contains the patch required to make the mozilla source compile correctly on arm (as well as a number of other architectures). make sure to get the typo fix a bit further down for the arm patch. Of course the security team would prefer if everything using mozilla could use the mozilla package for those libraries and such so that there are less packages to go fix the same bugs in, but I don't know if that is currently possible with nvu's build setup. If it did use the externally available mozilla then this bug would have been solved long ago since it was fixed in the mozilla upstream a few months ago. Len Sorensen -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tel) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-5-armcoregx-nano-nor-exp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages nvu depends on: ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libfontconfig12.3.2-1generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.1-8 GCC support library ii libgconf2-4 2.10.1-5 GNOME configuration database syste ii libglib2.0-0 2.8.0-1The GLib library of C routines ii libgnome2-0 2.10.1-1 The GNOME 2 library - runtime file ii libgnomevfs2-02.10.1-5 The GNOME virtual file-system libr ii libgtk2.0-0 2.6.9-1The GTK+ graphical user interface ii libidl0 0.8.5-1library for parsing CORBA IDL file ii liborbit2 1:2.12.2-3 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.8.2-2Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libstdc++64.0.1-8The GNU Standard C++ Library v3 ii libx11-6 6.8.2.dfsg.1-7 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-7 X Window System miscellaneous exte ii libxft2 2.1.7-1FreeType-based font drawing librar ii libxp66.8.2.dfsg.1-7 X Window System printing extension ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii libxt66.8.2.dfsg.1-7 X Toolkit Intrinsics ii xlibs 6.8.2.dfsg.1-7 X Window System client libraries m ii zlib1g1:1.2.3-4 compression library - runtime Versions of packages nvu recommends: pn myspell-dictionarynone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
