Bug#755347: marked as done (shinken: FTBFS: Error: pyversions: error parsing Python-Version attribute)
Your message dated Fri, 29 Aug 2014 06:00:09 + with message-id e1xnfeh-00074c...@franck.debian.org and subject line Bug#755347: fixed in shinken 2.0.3-1 has caused the Debian Bug report #755347, regarding shinken: FTBFS: Error: pyversions: error parsing Python-Version attribute 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.) -- 755347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: shinken Version: 1.4.2-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean --with python2 --install-layout=deb,quilt dh_testdir -O--install-layout=deb,quilt dh_auto_clean -O--install-layout=deb,quilt pyversions: error parsing Python-Version attribute dh_auto_clean: pyversions -r failed [4] make: *** [clean] Error 4 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/07/18/shinken_1.4.2-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: shinken Source-Version: 2.0.3-1 We believe that the bug you reported is fixed in the latest version of shinken, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Parent sath...@debian.org (supplier of updated shinken 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: SHA256 Format: 1.8 Date: Thu, 28 Aug 2014 22:26:37 +0200 Source: shinken Binary: shinken shinken-common shinken-doc Architecture: source all Version: 2.0.3-1 Distribution: experimental Urgency: medium Maintainer: Shinken Debian packages maintainers pkg-shinken-ma...@lists.alioth.debian.org Changed-By: Mathieu Parent sath...@debian.org Description: shinken- Flexible monitoring tool - Meta-package shinken-common - Flexible monitoring tool - Common files shinken-doc - Flexible monitoring tool - Documentation Closes: 745458 755347 Changes: shinken (2.0.3-1) experimental; urgency=medium . [ Mathieu Parent ] * Init script are already installed by setup.py, remove from shinken-common.install * Install files from setup.py * Removing all patches (integrated upstream, except 11_shinken_init.patch * Remove modules, they are now in separate git repos * Remove in d/rules things done by setup.py * Move doc to a separate package * Compile doc (html, txt) and install it * Move to dh compat 9 * Lintian: W: shinken source: debhelper-but-no-misc-depends shinken-doc * Set pkg-shinken-maint as Maintainer, and add me as Uploader * Don't require any module * Everything is arch:all * update copyright format URL * Lintian: I: shinken: capitalization-error-in-description meta-package metapackage * Add shinken-doc.doc-base * Remove shinken-common.default (not needed anymore) * Replace embedded JS libraries in -doc by symlinks * init script patches * Suggests shinken-mod and shinken-pack virtual packages * Install the shinken bin * Remove debconf question as shinken/instructions doesn't exist * Start the receiver on boot too (as stated in LSB headers) * Clean up maintscripts * Fix dpkg-statoverride usage * Purge directories on purge (and not on remove) * useradd/adduser is usually done in postinst * Use adduser/addgroup instead of useradd usermod * More refactoring * Remove duplicate call update-rc.d * Don't manage the shinken init script * Install webui * Create the /var/lib/shinken/modules dir * Create an empty /etc/shinken/modules dir * Install egg-info * Stop lintian from complaining
Bug#743806: marked as done (gnome-keyring: Build-Depends on transitional libtasn1-3-* packages)
Your message dated Fri, 29 Aug 2014 06:03:34 + with message-id e1xnfha-0007mc...@franck.debian.org and subject line Bug#743806: fixed in gnome-keyring 3.12.2-1 has caused the Debian Bug report #743806, regarding gnome-keyring: Build-Depends on transitional libtasn1-3-* packages 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.) -- 743806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-keyring Version: 3.8.2-2 Severity: normal gnome-keyring build-depends on libtasn1-3-dev and libtasn1-3-bin, which are both empty transitional packages. Please change build-dependencies to libtasn1-6-dev and libtasn1-bin instead. This also applies to gnome-keyring 3.10.1-1 in experimental. 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' ---End Message--- ---BeginMessage--- Source: gnome-keyring Source-Version: 3.12.2-1 We believe that the bug you reported is fixed in the latest version of gnome-keyring, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson andr...@fatal.se (supplier of updated gnome-keyring 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: SHA1 Format: 1.8 Date: Thu, 28 Aug 2014 22:47:23 -0700 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring Architecture: source amd64 Version: 3.12.2-1 Distribution: unstable Urgency: medium Maintainer: Josselin Mouette j...@debian.org Changed-By: Andreas Henriksson andr...@fatal.se Description: gnome-keyring - GNOME keyring services (daemon and tools) libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login Closes: 558553 743806 Changes: gnome-keyring (3.12.2-1) unstable; urgency=medium . [ Andreas Henriksson ] * New upstream release. * Bump Standards-Version to 3.9.5 . [ Dmitry Shachnev ] * Build with dh-autoreconf to support new archs (closes: #558553). . [ Andreas Metzler ] * Build-depend on libtasn1-6-dev/libtasn1-bin instead of libtasn1-3-dev/libtasn1-3-bin transitional packages. Closes: #743806 . [ Andreas Henriksson ] * Disable tests on kfreebsd for now. - see corresponding change in libgnome-keyring (need kfreebsd-10). Checksums-Sha1: 0c121fb68f4ccc720ab9d1d31eb239387fa92e3e 1984 gnome-keyring_3.12.2-1.dsc 0bdcbeadfef9fee15cf70b6070ab347b0584816a 1170560 gnome-keyring_3.12.2.orig.tar.xz 2bf548e770c7563778d6649ab7f46c196400aa50 14956 gnome-keyring_3.12.2-1.debian.tar.xz a595863db00c7f1660c51cd6a8b2dc0741a1a3ca 959486 gnome-keyring_3.12.2-1_amd64.deb a0ea43e71e0db4a0f079c2ab44b259be86c9347c 284982 libpam-gnome-keyring_3.12.2-1_amd64.deb Checksums-Sha256: 338909c86f68edc4a1453d5e28825ae24adb9bfd266616b745e768b09116d779 1984 gnome-keyring_3.12.2-1.dsc 3bc39a42d445b82d24247a8c39eeb0eef7ecb1c8ebb8e6ec62671868be93fd4c 1170560 gnome-keyring_3.12.2.orig.tar.xz eda9523f2be3ec4d1ad7afd7048c36f3f5d5edcd1a9709ea88116f14aea1e371 14956 gnome-keyring_3.12.2-1.debian.tar.xz fbdd4498be52a786c8dafb08a5eb201793717c4098c15be6040906ecd93a1fee 959486 gnome-keyring_3.12.2-1_amd64.deb 00ae827a61e179ef21bacf7875fba6507cd73ec26b421e418f3626201067beac 284982 libpam-gnome-keyring_3.12.2-1_amd64.deb Files: 79d2c8bff21573081794b5cdc48afd38 959486 gnome optional gnome-keyring_3.12.2-1_amd64.deb 9b3533ae37d9056c3f1971f9bb88bf20 284982 admin optional libpam-gnome-keyring_3.12.2-1_amd64.deb d7fd0e2187095f8fecab553107ff7bf5 1984 gnome optional gnome-keyring_3.12.2-1.dsc 63db70619f58e9cbd70c0b7d2285f26f 1170560 gnome optional gnome-keyring_3.12.2.orig.tar.xz 009d6fdd5bb71154893e90860b9ed3fa 14956 gnome optional gnome-keyring_3.12.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQAFhYACgkQcgQ2cL3l8e7ypwCfbfs+YAY0ZNBjbyaXKmPXQ1bF KwgAnR/j3t61aBH2nAl7GnMDStMtSP7W =IoAG -END PGP SIGNATUREEnd Message---
Bug#755910: marked as done (collides with python-bzrlib)
Your message dated Fri, 29 Aug 2014 06:35:18 + with message-id e1xnfmi-0004gm...@franck.debian.org and subject line Bug#755910: fixed in paramiko 1.14.1-1 has caused the Debian Bug report #755910, regarding collides with python-bzrlib 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.) -- 755910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-paramiko Version: 1.14.0-2 Severity: serious python-paramiko is no longer installable once bzr is installed, since the latest python-bzrlib has a Conflicts against python-paramiko = 1.12. The python-bzrlib changelog suggests that python-paramiko needs an update: * Conflict and build-conflict with newer versions of paramiko that no longer accept 'buffer' objects. This is a stop-gap until paramiko is fixed. Closes: #750347 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 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 python-paramiko depends on: ii python 2.7.8-1 ii python-crypto 2.6.1-5+b1 ii python-ecdsa 0.11-1 python-paramiko recommends no packages. python-paramiko suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: paramiko Source-Version: 1.14.1-1 We believe that the bug you reported is fixed in the latest version of paramiko, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy T. Bouse jbo...@debian.org (supplier of updated paramiko 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: Thu, 28 Aug 2014 22:23:51 -0700 Source: paramiko Binary: paramiko-doc python-paramiko python3-paramiko Architecture: source all Version: 1.14.1-1 Distribution: unstable Urgency: medium Maintainer: Jeremy T. Bouse jbo...@debian.org Changed-By: Jeremy T. Bouse jbo...@debian.org Description: paramiko-doc - Make ssh v2 connections with Python (Documentation) python-paramiko - Make ssh v2 connections with Python (Python 2) python3-paramiko - Make ssh v2 connections with Python (Python 3) Closes: 750517 755910 Changes: paramiko (1.14.1-1) unstable; urgency=medium . [ Thomas Kluyver ] * Add autopkgtest information . [ Jeremy T. Bouse ] * Include upstream GitHub Pull Request #352 to fix RC bug. Thanks to Jelmer Vernooij jelmer (Closes: #750517, #755910) * Imported Upstream version 1.14.1 * Revert Include upstream GitHub Pull Request #352 to fix RC bug as it was included in upstream bug fix release 1.14.1 to remove the regression introduced into 1.14.0. Checksums-Sha1: 3808ed0c046fc58ae3f1e8e47aa0af7a36da26ef 2140 paramiko_1.14.1-1.dsc 921ba11dfbf7fb7a3ac1a3c3440d64f89b65af2c 235333 paramiko_1.14.1.orig.tar.gz f1e8977dd7d993ba9f7345a858338b22f40b4293 5136 paramiko_1.14.1-1.debian.tar.xz 7661eca09bfd9428aa7306e9be79ec7fac35d2e3 370844 paramiko-doc_1.14.1-1_all.deb a7721dea682bcd432a49d4d5510906916406c9f9 97756 python-paramiko_1.14.1-1_all.deb bfb4dcadf3820ebe3e1b98e640a02a9a8a9fe726 97296 python3-paramiko_1.14.1-1_all.deb Checksums-Sha256: 851945af12df917f3c60ed5a7bd245bdc01da5be1cd6b84f747718f030775b8f 2140 paramiko_1.14.1-1.dsc c3387c67c9abbe82c81ae589e324fd9dc8e33be3ead0c396b9ed4987eb86a2b1 235333 paramiko_1.14.1.orig.tar.gz d51ab03697c3766c34f475f0ffa6d52824dd27dc35fed22bc4d17c0de44bc538 5136 paramiko_1.14.1-1.debian.tar.xz 6b5fcd77542034b8590b462dbbd138e03c918db1ddd7a94c5c4b5967a2ba2e18 370844 paramiko-doc_1.14.1-1_all.deb aa5b830a2f846bb869aee3e37f3115e809f6af4b77ef13f5f5dcc644841fa659 97756 python-paramiko_1.14.1-1_all.deb 4cfac7fc6fabba5bb817e159129b1de0a0d9af517f441fd5ce22e437e7745b8c 97296 python3-paramiko_1.14.1-1_all.deb Files: c4c7823f95e00bf48eec678e4b7e0bb4 370844 doc optional paramiko-doc_1.14.1-1_all.deb c98b61944f937c9ef52cfa4031a9787b 97756 python optional
Bug#734599: native library loading failure
The following patch modifies the native library loading to use debian
native /usr/lib/libsnappy.so file if no specific system property is used.
This fixes the native loading, however, using latest code there are
pending issues. Using previous example, it seems that Java library does
not match native library:
osallou@debiansid:~$ java -cp
/home/osallou/snappy-java-1.0.4.1~dfsg/target/snappy-java-1.0.4.1.jar:.
SnappyTests Exception in thread main java.lang.UnsatisfiedLinkError:
org.xerial.snappy.SnappyNative.maxCompressedLength(I)I
at org.xerial.snappy.SnappyNative.maxCompressedLength(Native Method)
at org.xerial.snappy.Snappy.maxCompressedLength(Snappy.java:316)
at org.xerial.snappy.Snappy.rawCompress(Snappy.java:329)
at org.xerial.snappy.Snappy.compress(Snappy.java:88)
at SnappyTests.main(SnappyTests.java:12)
Olivier
gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4
6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
--- a/src/main/java/org/xerial/snappy/SnappyLoader.java
+++ b/src/main/java/org/xerial/snappy/SnappyLoader.java
@@ -433,21 +433,8 @@
return nativeLib;
}
-{
-// Load an OS-dependent native library inside a jar file
-snappyNativeLibraryPath = /org/xerial/snappy/native/ +
OSInfo.getNativeLibFolderPathForCurrentOS();
+return new File(/usr/lib/libsnappy.so);
-if (SnappyLoader.class.getResource(snappyNativeLibraryPath + / +
snappyNativeLibraryName) != null) {
-// Temporary library folder. Use the value of
org.xerial.snappy.tempdir or java.io.tmpdir
-String tempFolder = new
File(System.getProperty(KEY_SNAPPY_TEMPDIR,
-System.getProperty(java.io.tmpdir))).getAbsolutePath();
-
-// Extract and load a native library inside the jar file
-return extractLibraryFile(snappyNativeLibraryPath,
snappyNativeLibraryName, tempFolder);
-}
-}
-
-return null; // Use a pre-installed libsnappyjava
}
/**
Bug#741075: user-mode-linux: Occasional memory corruption on startup under high load
On 09/03/14 21:35, Mattia Dongili wrote: On Sat, Mar 08, 2014 at 07:04:56AM +, Anton Ivanov wrote: Package: user-mode-linux Version: 3.2-2um-1+deb7u2+b1 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, This bug is perennial. If we go through old bugs with cannot reproduce tag 50% of them are this one, the other 50% are the you should not use pipe for interprocess IPC which we will submit shortly. Manifestation of the problem - UML dies on startup for no reason with a memory corruption message. Occurs only on heavily loaded systems and usually when running a lot of UMLs. Thanks for the patch. I have noticed that you submitted these patch-set (together with the other two you sent here and more) upstream and they will be in the stable branch. The easiest path here is also to go through the stable release of linux-source where uml is built from. I'll keep an eye on the stable tree but it'd be very helpful if you could add the stable tree commit ids once the patches get included. Same story for the other two bugs. All 3 bugs have now patches submitted upstream. I have submitted our other improvements as well. While they do not make a speed daemon of uml userspace they get it reasonably close to kvm. Kernel itself is now faster than qemu-kvm for most networking stuff. A. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741075: user-mode-linux: Occasional memory corruption on startup under high load
This is great news. Thank you. s3nt fr0m a $martph0ne, excuse typ0s On Aug 29, 2014 1:24 PM, Anton Ivanov anton.iva...@kot-begemot.co.uk wrote: On 09/03/14 21:35, Mattia Dongili wrote: On Sat, Mar 08, 2014 at 07:04:56AM +, Anton Ivanov wrote: Package: user-mode-linux Version: 3.2-2um-1+deb7u2+b1 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, This bug is perennial. If we go through old bugs with cannot reproduce tag 50% of them are this one, the other 50% are the you should not use pipe for interprocess IPC which we will submit shortly. Manifestation of the problem - UML dies on startup for no reason with a memory corruption message. Occurs only on heavily loaded systems and usually when running a lot of UMLs. Thanks for the patch. I have noticed that you submitted these patch-set (together with the other two you sent here and more) upstream and they will be in the stable branch. The easiest path here is also to go through the stable release of linux-source where uml is built from. I'll keep an eye on the stable tree but it'd be very helpful if you could add the stable tree commit ids once the patches get included. Same story for the other two bugs. All 3 bugs have now patches submitted upstream. I have submitted our other improvements as well. While they do not make a speed daemon of uml userspace they get it reasonably close to kvm. Kernel itself is now faster than qemu-kvm for most networking stuff. A. Thanks!
Processed: your mail
Processing commands for cont...@bugs.debian.org: notforwarded 750867 Bug #750867 [src:kde-runtime] kde-runtime: openssl license exception needed Unset Bug forwarded-to-address End of message, stopping processing here. Please contact me if you need assistance. -- 750867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750867 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#750867:
Here you can see kio-sftp is under LGPL http://quickgit.kde.org/?p=kde-runtime.gita=blobf=kioslave%2Fsftp%2Fkio_sftp.cpp
Bug#757670: cadabra: maintainer address bounces
Sorry about that. My gmail account should work fine: iulian.ud...@gmail.com. Cheers, Iulian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759663: octave: FTBFS on mips - Please add mips to NO_JDK_ARCHS
Source: octave Version: 3.6.4-4 Severity: serious Justification: FTBFS on mips (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, As you already know octave has been binNMUed for the ongoing hdf5 transition. Unfortunately it FTBFS on mips [1] with: libinterp/octave-value/ov-java.cc-tst ..panic: Bus error -- stopping myself... [1] https://buildd.debian.org/status/fetch.php?pkg=octavearch=mipsver=3.8.2-1%2Bb1stamp=1409282746 This error was seen before and discussed in January 2014 on the pkg-octave-devel list [2]. [2] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2014-January/010510.html How about adding mips to the disable-java list? Thanks in advance, _g. - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUAD8MAAoJEO/obGx//s+DtqAIAKtODQTLSHExQbIzQ+/cpRrV ykjYEdG9AMn57NCow/Qtfito1V3i5DB3qd00vWMay4CKo4+UkLsDJDj/Qiffgzhf tgEgNuk2MR/jUFIeZflca2L+5Ic4KwVabODK39BwuBA2C+TRrYkD17xzrglFSF/P tQZuxhSe9QQneB+WdG+Y5BIhIJe1EPX5tv8Bgech8Qz52V9xeFVK8TiSmFr1lts8 PjAip2gXqyBbEur/nb9p5M3U5c0Bv/Jqs5L+GYGGQaPcGckKEpVkXDxmG/l/XX47 cExFVwyxRfcCGFwPOLc0+R6Rv+8lIhpOqCjNHKWOoRJZ097SHYpqfGWEpMLN5/I= =T82V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749500: rakudo: not installable in sid
rakudo =2014.07-1 depends on nqp =2014.07-1, but only nqp =2014.07-2 is available. root@qmqm:~# apt-cache policy rakudo rakudo: Zainstalowana: 2014.03.01-1+b1 Kandydująca: 2014.07-1 Tabela wersji: 2014.07-1 0 700 http://ftp.pl.debian.org/debian/ sid/main amd64 Packages *** 2014.03.01-1+b1 0 100 /var/lib/dpkg/status 0.1~2012.01-1 0 800 http://ftp.pl.debian.org/debian/ wheezy/main amd64 Packages root@qmqm:~# apt-cache policy nqp nqp: Zainstalowana: 2014.04-3 Kandydująca: 2014.04-3 Tabela wersji: 2014.07-2 0 700 http://ftp.pl.debian.org/debian/ sid/main amd64 Packages *** 2014.04-3 0 900 http://ftp.pl.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status 0.1~2012.01-5 0 800 http://ftp.pl.debian.org/debian/ wheezy/main amd64 Packages -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749659: build on other distro
btw. I was testing your patches on other distro than Debian and unfortunately it fails to build here. Probably due to some differences between distros. Not sure if that matters in efforts of upstreaming wxwidgets 3.0 support. http://sprunge.us/TDBI -- Arkadiusz Miśkiewicz, arekm / maven.pl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749500: rakudo: not installable in sid
Ack. I'm going to relax the vesrioned dependency on nqp. I don't think that a strict dependency is necessary. -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759666: [xsdcxx] Generates uncompilable code (FTBFS in other packages)
Package: xsdcxx Version: 4.0.0-1 Severity: serious This problem was introduced with 4.0.0-1 and it worked perfectly fine in 3.3.0.2-3. This problem can for example be seen in bug #756866 (see the build logs there for more information) If you think that the problem is in the other package than please give detailed instructions how they can be fixed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754644: marked as done (golang-go.tools: FTBFS on armel/armhf/i386: test failures)
Your message dated Fri, 29 Aug 2014 09:22:55 + with message-id e1xniov-sw...@franck.debian.org and subject line Bug#754644: fixed in golang-go.tools 0.0~hg20140703-3 has caused the Debian Bug report #754644, regarding golang-go.tools: FTBFS on armel/armhf/i386: test failures 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.) -- 754644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: golang-go.tools Version: 0.0~hg20140703-1 Severity: serious Justification: FTBFS Hi, your package FTBFS on all buildds it was tried on (armel/armhf/i386), in the test suite. Direct links: https://buildd.debian.org/status/fetch.php?pkg=golang-go.toolsarch=armelver=0.0~hg20140703-1stamp=1404410530 https://buildd.debian.org/status/fetch.php?pkg=golang-go.toolsarch=armhfver=0.0~hg20140703-1stamp=1404410491 https://buildd.debian.org/status/fetch.php?pkg=golang-go.toolsarch=i386ver=0.0~hg20140703-1stamp=1404410059 Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: golang-go.tools Source-Version: 0.0~hg20140703-3 We believe that the bug you reported is fixed in the latest version of golang-go.tools, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg stapelb...@debian.org (supplier of updated golang-go.tools 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, 29 Aug 2014 09:50:11 +0200 Source: golang-go.tools Binary: golang-go.tools golang-go.tools-dev Architecture: source amd64 all Version: 0.0~hg20140703-3 Distribution: unstable Urgency: medium Maintainer: Michael Stapelberg stapelb...@debian.org Changed-By: Michael Stapelberg stapelb...@debian.org Description: golang-go.tools - supplementary Go tools golang-go.tools-dev - supplementary Go tools (development files) Closes: 754644 Changes: golang-go.tools (0.0~hg20140703-3) unstable; urgency=medium . * Add debian/patches/0003-fix-tests.patch (Closes: #754644) Checksums-Sha1: 36f1576d8ba173064e3baac75a6efa20aa5b54cd 2127 golang-go.tools_0.0~hg20140703-3.dsc 1e2522064f72707ab5a47574ec5add7f6329b9c6 9308 golang-go.tools_0.0~hg20140703-3.debian.tar.xz 3531c1aeff8d0593880f649e11836ab21d9e2e52 8870650 golang-go.tools_0.0~hg20140703-3_amd64.deb 215ddc1d31320f57f279abd526001b7fe90c72a8 1242616 golang-go.tools-dev_0.0~hg20140703-3_all.deb Checksums-Sha256: eff753e879d6b87ab21b2ad946e279e40563cfdc055ff6e9a3eae671e8225bab 2127 golang-go.tools_0.0~hg20140703-3.dsc c6d2398678f61a18b1b517056ae1fd3986161e16f629fed77d795f4666917d3a 9308 golang-go.tools_0.0~hg20140703-3.debian.tar.xz 6b245b6f26bc9240bd64b26800ed1c98759680d83f46688a77141bb080768d8b 8870650 golang-go.tools_0.0~hg20140703-3_amd64.deb b8adf39740b8c76a421f1e08d92b42c1823b30e672a69825ae5aafd26595bc00 1242616 golang-go.tools-dev_0.0~hg20140703-3_all.deb Files: b1ee62cb4e2866181afe2734f4c99887 8870650 devel extra golang-go.tools_0.0~hg20140703-3_amd64.deb 9a9a5601f33fd658d6ff91f4c5ed4740 1242616 devel extra golang-go.tools-dev_0.0~hg20140703-3_all.deb 31dc57d511d2848414d49fb76f0f4870 2127 devel extra golang-go.tools_0.0~hg20140703-3.dsc c07cf67b670938a9c859558250322488 9308 devel extra golang-go.tools_0.0~hg20140703-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUADHxAAoJEE5xYO1KyO4dnT4P/3iv2wNDYZ3quUa/mfsOa2ps khB8WRr+fGP1D4VV5Xe7Lwe/lZ/u96USz7l5ggAvBGMz3qyMRzNaR7XrOvz3wDIv BxQjO7liZkLHBsN2Urqafg8QX7z5/9IlPlQpRCznFdLR9hkoBULOdJFD/llIK/CM Kpi+I7lmUlYysdIaVSIYjwGVvQPlOKdPhowbdXqkn0qCCgYlHIL9VBlKn9ZiFUx3 jQ4ASOQ15VFm4IrS9KNCJ+sAbuYN/DkYVWvf7BCIDHxomCqwFkWnh4QrAzDOqKSE 8qE2rAGFTaAEmoO8zizYt50jbDmu8gyhWLtvD+xmgM5xi6nd7zV2m0oEEntCJ2NI fi0PGWde96WWRMurHymYsNLloqFrmjYIFpgHFwsZNoYs5hYwRy3HyaYqzB7pguhl E+BZ4RGm5cpX6I9ec9fhzrKHsjfxqLkJuT2ngLuKhTiKgD8neMPH8wS09HJi2GMr H2wHxLRcDP5WQiLIVeA/E2iUDnxaL95C9hw89PrKIPJZjlkjAjc5/ChQ623vwU6N 15FIiE47zsS7/llCvjfNNp/mZ21W8JoWXoT8RZw+aSKhom75t9IKn8HG/TQpe/Ir oQSci/RFUgY0nw1kbR21smbAYXB3ERWHGtXWdhiD2v+jyL4eTptwwNr+ozMlEsmp Wk7xkj80pM/BksXBZgXO =lNbF -END PGP SIGNATUREEnd
Bug#759182: marked as done (dolfin: FTBFS on mips(el) and sparc: MPI inconsistency)
Your message dated Fri, 29 Aug 2014 09:21:27 +
with message-id e1xnin5-qe...@franck.debian.org
and subject line Bug#759182: fixed in dolfin 1.4.0+dfsg-3
has caused the Debian Bug report #759182,
regarding dolfin: FTBFS on mips(el) and sparc: MPI inconsistency
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.)
--
759182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dolfin
Version: 1.4.0+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of dolfin on mips, mipsel, and sparc have all been failing:
In file included from /usr/lib/petscdir/3.4.2/include/petscsys.h:96:0,
from /«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/common/types.h:29,
from
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/function/Function.h:34,
from
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/ale/MeshDisplacement.h:28,
from /«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/mesh/Mesh.h:38,
from /«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/mesh/Cell.h:33,
from
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/mesh/MeshColoring.cpp:32:
/usr/lib/openmpi/include/mpi.h:319:37: error: conflicting declaration
'typedef struct ompi_communicator_t* MPI_Comm'
typedef struct ompi_communicator_t *MPI_Comm;
^
In file included from
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/common/utils.h:33:0,
from
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/mesh/MeshColoring.cpp:27:
/«BUILDDIR»/dolfin-1.4.0+dfsg/dolfin/common/MPI.h:42:13: note: previous
declaration as 'typedef int MPI_Comm'
typedef int MPI_Comm;
^
In all three cases, debian/rules tries to disable MPI because these
architectures historically used the LAM implementation, but PETSc
proceeds to include real OpenMPI headers, leading to those errors.
Could you please take alook?
Thanks!
---End Message---
---BeginMessage---
Source: dolfin
Source-Version: 1.4.0+dfsg-3
We believe that the bug you reported is fixed in the latest version of
dolfin, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johannes Ring joha...@simula.no (supplier of updated dolfin 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: SHA1
Format: 1.8
Date: Fri, 29 Aug 2014 08:28:19 +0200
Source: dolfin
Binary: libdolfin-dev libdolfin1.4 libdolfin1.4-dbg python-dolfin
python-dolfin-dbg dolfin-doc dolfin-bin
Architecture: source amd64 all
Version: 1.4.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Johannes Ring joha...@simula.no
Description:
dolfin-bin - Executable scripts for DOLFIN
dolfin-doc - Documentation and demo programs for DOLFIN
libdolfin-dev - Shared links and header files for DOLFIN
libdolfin1.4 - Shared libraries for DOLFIN
libdolfin1.4-dbg - Shared libraries with debugging symbols for DOLFIN
python-dolfin - Python interface for DOLFIN
python-dolfin-dbg - Python extension modules for DOLFIN with debugging symbols
Closes: 759182 759183
Changes:
dolfin (1.4.0+dfsg-3) unstable; urgency=medium
.
* debian/rules: Enable MPI on mips(el) and sparc (closes: #759182).
* debian/control:
- Disable libcgal-dev on {hurd, kfreebsd}-i386 since it requires
unreasonable amounts of memory (closes: #759183).
- Disable libpetsc3.4.2-dev and libslepc3.4.2-dev on amr64 since
they are not available on this architecture.
Checksums-Sha1:
400466126bd30301ac8b8323afa3c9902d3f34be 2989 dolfin_1.4.0+dfsg-3.dsc
057c273e696e4abc2d2e731a00174b6a8d0d9b6a 115200
dolfin_1.4.0+dfsg-3.debian.tar.xz
d56c70ca8a73e1cfe5e8a703e8701870e22f56b0 242662
libdolfin-dev_1.4.0+dfsg-3_amd64.deb
012e57a12a1398d2a745d348c62102af39acd936 3417326
libdolfin1.4_1.4.0+dfsg-3_amd64.deb
07964492f98ee795a47d5d21abba6657d5c7527f 51326732
libdolfin1.4-dbg_1.4.0+dfsg-3_amd64.deb
30723ba3af34f6e8f92e4e1ac788b808df47c129 1245030
Bug#759183: marked as done (dolfin: FTBFS on {hurd,kfreebsd}-i386: virtual memory exhausted)
Your message dated Fri, 29 Aug 2014 09:21:28 +
with message-id e1xnin6-qk...@franck.debian.org
and subject line Bug#759183: fixed in dolfin 1.4.0+dfsg-3
has caused the Debian Bug report #759183,
regarding dolfin: FTBFS on {hurd,kfreebsd}-i386: virtual memory exhausted
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.)
--
759183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dolfin
Version: 1.4.0+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of dolfin for hurd-i386 and kfreebsd-i386 both run out of
memory when trying to compile ImplicitDomainMeshGenerator.cpp:
virtual memory exhausted: Cannot allocate memory
make[4]: ***
[dolfin/CMakeFiles/dolfin.dir/generation/ImplicitDomainMeshGenerator.cpp.o]
Error 1
Could you please take a look?
Thanks!
---End Message---
---BeginMessage---
Source: dolfin
Source-Version: 1.4.0+dfsg-3
We believe that the bug you reported is fixed in the latest version of
dolfin, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johannes Ring joha...@simula.no (supplier of updated dolfin 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: SHA1
Format: 1.8
Date: Fri, 29 Aug 2014 08:28:19 +0200
Source: dolfin
Binary: libdolfin-dev libdolfin1.4 libdolfin1.4-dbg python-dolfin
python-dolfin-dbg dolfin-doc dolfin-bin
Architecture: source amd64 all
Version: 1.4.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Johannes Ring joha...@simula.no
Description:
dolfin-bin - Executable scripts for DOLFIN
dolfin-doc - Documentation and demo programs for DOLFIN
libdolfin-dev - Shared links and header files for DOLFIN
libdolfin1.4 - Shared libraries for DOLFIN
libdolfin1.4-dbg - Shared libraries with debugging symbols for DOLFIN
python-dolfin - Python interface for DOLFIN
python-dolfin-dbg - Python extension modules for DOLFIN with debugging symbols
Closes: 759182 759183
Changes:
dolfin (1.4.0+dfsg-3) unstable; urgency=medium
.
* debian/rules: Enable MPI on mips(el) and sparc (closes: #759182).
* debian/control:
- Disable libcgal-dev on {hurd, kfreebsd}-i386 since it requires
unreasonable amounts of memory (closes: #759183).
- Disable libpetsc3.4.2-dev and libslepc3.4.2-dev on amr64 since
they are not available on this architecture.
Checksums-Sha1:
400466126bd30301ac8b8323afa3c9902d3f34be 2989 dolfin_1.4.0+dfsg-3.dsc
057c273e696e4abc2d2e731a00174b6a8d0d9b6a 115200
dolfin_1.4.0+dfsg-3.debian.tar.xz
d56c70ca8a73e1cfe5e8a703e8701870e22f56b0 242662
libdolfin-dev_1.4.0+dfsg-3_amd64.deb
012e57a12a1398d2a745d348c62102af39acd936 3417326
libdolfin1.4_1.4.0+dfsg-3_amd64.deb
07964492f98ee795a47d5d21abba6657d5c7527f 51326732
libdolfin1.4-dbg_1.4.0+dfsg-3_amd64.deb
30723ba3af34f6e8f92e4e1ac788b808df47c129 1245030
python-dolfin_1.4.0+dfsg-3_amd64.deb
90a98dd9adf6ad4782569e2fd2b72cb2e0f42311 8671578
python-dolfin-dbg_1.4.0+dfsg-3_amd64.deb
2361f8c518a699a9eb1b3a4c1ed02e4905ddd462 2262016
dolfin-doc_1.4.0+dfsg-3_all.deb
d3d56626808b8fd41f0aa08fc56bd6d10cd71bc4 43896 dolfin-bin_1.4.0+dfsg-3_all.deb
Checksums-Sha256:
e43f7fda14fd10c2fb00d9802257f6b016398f325526c2bb0fa5376284e2b735 2989
dolfin_1.4.0+dfsg-3.dsc
584555a2d1c90405d5e561b2e3f3260512914b1db429b0e2049557669df90b29 115200
dolfin_1.4.0+dfsg-3.debian.tar.xz
b6e65b15b03daed964e8e58a38de6fbc6f339251e7c4ae7265fd1575ef43e91e 242662
libdolfin-dev_1.4.0+dfsg-3_amd64.deb
f16c41994c888a68651c7989a55938faebb4fa3de770ab76a4877e445ff31e78 3417326
libdolfin1.4_1.4.0+dfsg-3_amd64.deb
98cb2dfaac0223aca5487722ac87a976ef32cea66d04248e0e1f64b0065efcc1 51326732
libdolfin1.4-dbg_1.4.0+dfsg-3_amd64.deb
99edb7edaec60de8c5b1f639a21621353a082c89e51ef6b3f13870980cb4b29c 1245030
python-dolfin_1.4.0+dfsg-3_amd64.deb
b74a38ca24ba0cf1efd9dd95c50dd4d5b793d6c9db7dd6305aff020268a37f8f 8671578
python-dolfin-dbg_1.4.0+dfsg-3_amd64.deb
Bug#759666: marked as done ([xsdcxx] Generates uncompilable code (FTBFS in other packages))
Your message dated Fri, 29 Aug 2014 10:46:20 +0100 with message-id 1409305580.79736.yahoomail...@web133202.mail.ir2.yahoo.com and subject line already fixed in other package has caused the Debian Bug report #759666, regarding [xsdcxx] Generates uncompilable code (FTBFS in other packages) 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.) -- 759666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xsdcxx Version: 4.0.0-1 Severity: serious This problem was introduced with 4.0.0-1 and it worked perfectly fine in 3.3.0.2-3. This problem can for example be seen in bug #756866 (see the build logs there for more information) If you think that the problem is in the other package than please give detailed instructions how they can be fixed. ---End Message--- ---BeginMessage--- already fixed in other package---End Message---
Bug#756910: marked as done (libapache2-mod-auth-openidc: FTBFS on mips, powerpc, s390x (and sparc): test failure)
Your message dated Fri, 29 Aug 2014 12:28:54 +0200 with message-id 540055e6.2090...@pingidentity.com and subject line Re: Bug#756910: libapache2-mod-auth-openidc: FTBFS on mips, powerpc, s390x (and sparc): test failure has caused the Debian Bug report #756910, regarding libapache2-mod-auth-openidc: FTBFS on mips, powerpc, s390x (and sparc): test failure 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.) -- 756910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libapache2-mod-auth-openidc Version: 1.5.3-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on the aforementioned archs due to this test failure: | `/usr/bin/apxs2 -q CC` -DLINUX -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/apr-1.0 -Isrc -o test/test test/*.c src/jose/apr_jwt.c src/jose/apr_jwk.c src/jose/apr_jws.c src/jose/apr_jwe.c -lapr-1 -laprutil-1 -lldap -llber -lssl -lcrypto -ljansson | test/test | Failed: # test_jwt_decryption: error in apr_jwe_decrypt_jwt: result 0 != expected 1 | make[1]: *** [test] Error 1 Build summary with links to full build logs: https://buildd.debian.org/status/package.php?p=libapache2-mod-auth-openidcsuite=sid Mraw, KiBi. ---End Message--- ---BeginMessage--- This is fixed in release 1.5.5 with the patch provided by Dejan Latinovic: The reason for this failure is the fact that p does not get info about Additional Authentication Data length (al) in src/jose/apr_jwe.c for big endian. Patch that fixes this issue is attached. This patch should enable build of libapache2-mod-auth-openidc on big endian architectures. I successfully built it on mips (BE). Could you please consider including this patch? I had already forwarded it upstream: https://github.com/pingidentity/mod_auth_openidc/pull/21 Hans. On 8/3/14, 2:07 PM, Cyril Brulebois wrote: Source: libapache2-mod-auth-openidc Version: 1.5.3-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on the aforementioned archs due to this test failure: | `/usr/bin/apxs2 -q CC` -DLINUX -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/apr-1.0 -Isrc -o test/test test/*.c src/jose/apr_jwt.c src/jose/apr_jwk.c src/jose/apr_jws.c src/jose/apr_jwe.c -lapr-1 -laprutil-1 -lldap -llber -lssl -lcrypto -ljansson | test/test | Failed: # test_jwt_decryption: error in apr_jwe_decrypt_jwt: result 0 != expected 1 | make[1]: *** [test] Error 1 Build summary with links to full build logs: https://buildd.debian.org/status/package.php?p=libapache2-mod-auth-openidcsuite=sid Mraw, KiBi. -- Hans Zandbelt | Sr. Technical Architect hzandb...@pingidentity.com | Ping Identity---End Message---
Bug#758009: marked as done (shogun: FTBFS: depends on non-existing package as first alternative)
Your message dated Fri, 29 Aug 2014 10:50:49 + with message-id e1xnjlz-0003gz...@franck.debian.org and subject line Bug#758009: fixed in shogun 3.2.0-7.1 has caused the Debian Bug report #758009, regarding shogun: FTBFS: depends on non-existing package as first alternative 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.) -- 758009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: shogun Version: 3.2.0-7 Severity: serious Justification: fails to build from source (but built successfully in the past) Latest upload of shogun has this changelog entry: | shogun (3.2.0-7) unstable; urgency=low | | * Build depend on libjson-c2-dev instead of libjson-c-dev. | | -- Soeren Sonnenburg so...@debian.org Fri, 11 Jul 2014 22:13:43 +0200 In practice the build-depends is libjson-c2-dev | libjson0-dev. The libjson-c2-dev package doesn't exist in the archive, and sbuild doesn't consider alternatives. As a consequence, your package fail to build from source on all architectures: https://buildd.debian.org/status/package.php?p=shogunsuite=sid -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: shogun Source-Version: 3.2.0-7.1 We believe that the bug you reported is fixed in the latest version of shogun, 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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini p...@debian.org (supplier of updated shogun 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: SHA256 Format: 1.8 Date: Wed, 27 Aug 2014 10:33:25 +0200 Source: shogun Binary: libshogun16 libshogun-dev shogun-doc-en shogun-doc-cn libshogun-dbg shogun-cmdline-static Architecture: source i386 all Version: 3.2.0-7.1 Distribution: unstable Urgency: medium Maintainer: Soeren Sonnenburg so...@debian.org Changed-By: Gilles Filippini p...@debian.org Description: libshogun-dbg - Large Scale Machine Learning Toolbox libshogun-dev - Large Scale Machine Learning Toolbox libshogun16 - Large Scale Machine Learning Toolbox shogun-cmdline-static - Large Scale Machine Learning Toolbox shogun-doc-cn - Large Scale Machine Learning Toolbox shogun-doc-en - Large Scale Machine Learning Toolbox Closes: 758009 Changes: shogun (3.2.0-7.1) unstable; urgency=medium . * Non-maintainer upload. * Build-Depends: libjson-c-dev instead of libjson-c2-dev | libjson0-dev (closes: #758009). Checksums-Sha1: 5eb4693c1c7cf8a1d7d833f2314c09d9270d52fc 2316 shogun_3.2.0-7.1.dsc ba31ede2687df611e59d5c7acb6728c8d3cca3e6 14116 shogun_3.2.0-7.1.debian.tar.xz 9dc2e06c256a73f9521c6f7e94d2c12cfa979fbb 3716374 libshogun16_3.2.0-7.1_i386.deb d700b29eba6f7e6497a3a962882642750c052dea 1537672 libshogun-dev_3.2.0-7.1_i386.deb 1a83aeef135a32239a71c31e129d9fa32e647014 29094534 shogun-doc-en_3.2.0-7.1_all.deb bd077b5eab6925ed523c5eafd7c984ac34ff5e4a 29062112 shogun-doc-cn_3.2.0-7.1_all.deb ce4defe400dc67279b0e7b35d9bb32c69c63612a 42609894 libshogun-dbg_3.2.0-7.1_i386.deb 2e69a2def9f9c9c175b755b05463070e342555f7 959392 shogun-cmdline-static_3.2.0-7.1_i386.deb Checksums-Sha256: 0cd5cc9f4a2cd2f1c9ea1ccf8fb55735a2da40fe9d5703f3e6700513f4e7a431 2316 shogun_3.2.0-7.1.dsc 4729ccfba15d3980a30283db8931fba8454dff1afcd98f1de1d9b27611f65650 14116 shogun_3.2.0-7.1.debian.tar.xz 5be118149376fa13dd490887d1482b0526967c6413235fde82b50e2037089ce1 3716374 libshogun16_3.2.0-7.1_i386.deb b9e8ef5bee41d1c0ac8fcf123f261d0cf38d687f718686ae6d2421c7cebb1259 1537672 libshogun-dev_3.2.0-7.1_i386.deb a59bc35a1a57e2ba5999e79760aaad257b55c2b3e87fbac5806cf9677fa0891b 29094534 shogun-doc-en_3.2.0-7.1_all.deb 875ee56aaa2388a71f28af178f813cfdfbcfdd71bbeab82b29f7c0b6c33d8e72 29062112 shogun-doc-cn_3.2.0-7.1_all.deb e747011d4569d7f9adba6dc0b0e39f0756f1ba6b8a8e7045e2bf5e8eab933d7f 42609894
Bug#755728: marked as done (fenics: not installable in sid)
Your message dated Fri, 29 Aug 2014 11:03:59 + with message-id e1xnjyj-0007ee...@franck.debian.org and subject line Bug#755728: fixed in fenics 1:1.4.0.1 has caused the Debian Bug report #755728, regarding fenics: not installable in sid 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.) -- 755728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fenics Version: 1:1.3.0.1 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Hi, fenics is not installable in sid on any architecture. This is the case since 2014-05-12. The reason is that fenics depends both on python-ffc and python-ufc, which are in conflict. -Ralf. ---End Message--- ---BeginMessage--- Source: fenics Source-Version: 1:1.4.0.1 We believe that the bug you reported is fixed in the latest version of fenics, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Ring joha...@simula.no (supplier of updated fenics 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: SHA1 Format: 1.8 Date: Fri, 29 Aug 2014 12:48:12 +0200 Source: fenics Binary: fenics Architecture: source all Version: 1:1.4.0.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Johannes Ring joha...@simula.no Description: fenics - Automated Solution of Differential Equations Closes: 755728 Changes: fenics (1:1.4.0.1) unstable; urgency=medium . * debian/control: - Update Depends field to DOLFIN 1.4.0, FFC 1.4.0, FIAT 1.4.0, Instant 1.4.0 and UFL 1.4.0. - Remove ufc, python-ufc and python-ferari from Depends field (closes: #755728, LP: #1353018). - Remove libsyfi1.0-dev, python-syfi, syfi-doc and sfc from Suggest. Checksums-Sha1: 984e181ed95e32ffd9529a0ace0fa124e873dba8 1719 fenics_1.4.0.1.dsc e105ab679e04a7dfbf17aab88d7832897dd46563 2680 fenics_1.4.0.1.tar.xz fb3a455b786ec63bcf8cb40994f74140525f92fa 3194 fenics_1.4.0.1_all.deb Checksums-Sha256: ced627a0fad3db95db6d4234fb3c3f29c8d331b8900788369f17d02decd37323 1719 fenics_1.4.0.1.dsc 27564f7deff77952f253f26dd928447134c9e531c8e26abf562718312a0629de 2680 fenics_1.4.0.1.tar.xz 934b06224aa1e11e31dbfd403d9cb8a49cf0b69b0dd7152d954a12a4fa40a137 3194 fenics_1.4.0.1_all.deb Files: 59f8443ed4e07bf0e33cbdba3648b3ab 3194 math extra fenics_1.4.0.1_all.deb 0fd3c704bf6308651c6fc8dc2486799e 1719 math extra fenics_1.4.0.1.dsc 59f4b831c44673a0e09ad8401dfa5384 2680 math extra fenics_1.4.0.1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUAFrOAAoJEIsTRN6fgH8U4pIQAK+/yihNnYzGJV64JQtZhSFR rRfjji1jSL/3525c2VKESC7ipy9vgdmCUZHJ6S1tTvWU6DjFQXFKq96Xma9/aOE9 0wCn2Xr4fLP3A4QPPQ4dchq9mffnvudIpCVMLre1A5O9tvAz47mcJta/GQoyH/yF /knOnZeZXaTawj86p+/6pvz/rFgoBKwY29b/vYe1eEWpUxlQcIMz4GPclUCMpC0U kYs3XaPW3o+CXb8Y1YChcEutHelkpNJ+greKoiPEf/ZaF6/gJl348PZtcM1DOcZs /EbZYhSLxp+UPFcGcnptSYhgk2p+HxFohV68p2bMt3Vaok6+M05A4RgGyErsIgLq wb2DEM0OL9menRmdDyOQ0/A1ObCBhzutaaTeBKsz1R01Do8AwShi5at03nV02LUB IUAioDtBbPAQWfjmC8KZ7SQYlSzX564K9S5f2N5T3ojjl5LjvfDlSLfhJMPRH70C 7IKdX8+ux3VcWjcepik1PjpVttYXxgGNUGDW2D5loHcE0xprccHa0jwvIUjBcENI AhCtmnChJVEF1/UceiMTboL6hPTmuwwCNjiQx7xUEOAC9A/y4nHaDccliB//Qvaq FIFWhRWh2iW8EOSWCOq9Vv06cxogQjMF5njDl3RdfADpOuI7V7hqAKyYk9UaoEth H2QqiBVIBFv0tqol/CG9 =6DOk -END PGP SIGNATUREEnd Message---
Bug#711799: PXE error: no server is specified
Hi, Just to let hurd folks know, this bug affects their netboot images too. So I'll submit a patch that fixes both hurd and kfreebsd: $ wget http://d-i.debian.org/daily-images/hurd-i386/daily/netboot/grub2pxe $ qemu-system-i386 -net nic -net user,bootfile=grub2pxe,tftp=. qemu: fatal: Trying to execute code outside RAM or ROM at 0x656e0065 EAX=07ff158f EBX=07ff158f ECX=0001 EDX=656e0065 ESI=07f3c7d0 EDI=0007ff80 EBP=0007ff3c ESP=0007ff00 EIP=656e0065 EFL=0022 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 etc... 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
Bug#758999: marked as done (gjiten: FTBFS due to conflicting (transitive) b-d libgnutls-dev - libgnomevfs2-dev)
Your message dated Fri, 29 Aug 2014 12:33:29 + with message-id e1xnlmv-ns...@franck.debian.org and subject line Bug#758999: fixed in gjiten 2.6-2.3 has caused the Debian Bug report #758999, regarding gjiten: FTBFS due to conflicting (transitive) b-d libgnutls-dev - libgnomevfs2-dev 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.) -- 758999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gjiten Version: 2.6-2.2 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Hello, gjiten build-depends on libgnutls-dev and libgnomeui-dev, the latter depends on libgnomevfs2-dev which depends on libgnutls28-dev. The two gnutls development packages conflict with each other. gjiten also has a unused b-d on libgcrypt-dev. - Please drop it. Find attached a straightforward patch to fix these issues. 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' diff -u gjiten-2.6/debian/control gjiten-2.6/debian/control --- gjiten-2.6/debian/control +++ gjiten-2.6/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Botond Botyanszki b...@users.sourceforge.net Uploaders: Ludovic Drolez ldro...@debian.org -Build-Depends: cdbs, debhelper ( 4.2.0), libgnomeui-dev, scrollkeeper, libxml-parser-perl, libgnutls-dev, libgcrypt-dev, docbook-utils, xmlto, libglade2-dev +Build-Depends: cdbs, debhelper ( 4.2.0), libgnomeui-dev, scrollkeeper, libxml-parser-perl, libgnutls28-dev, docbook-utils, xmlto, libglade2-dev Standards-Version: 3.8.0 Package: gjiten diff -u gjiten-2.6/debian/changelog gjiten-2.6/debian/changelog --- gjiten-2.6/debian/changelog +++ gjiten-2.6/debian/changelog @@ -1,3 +1,10 @@ +gjiten (2.6-2.3) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build against libgnutls28-dev, drop b-d on libgcrypt-dev. + + -- Andreas Metzler ametz...@debian.org Sat, 23 Aug 2014 18:14:24 +0200 + gjiten (2.6-2.2) unstable; urgency=low * Non-maintainer upload. ---End Message--- ---BeginMessage--- Source: gjiten Source-Version: 2.6-2.3 We believe that the bug you reported is fixed in the latest version of gjiten, 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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler ametz...@debian.org (supplier of updated gjiten 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: Sun, 24 Aug 2014 13:51:10 +0200 Source: gjiten Binary: gjiten Architecture: source Version: 2.6-2.3 Distribution: unstable Urgency: medium Maintainer: Botond Botyanszki b...@users.sourceforge.net Changed-By: Andreas Metzler ametz...@debian.org Description: gjiten - Japanese dictionary for GNOME Closes: 758999 Changes: gjiten (2.6-2.3) unstable; urgency=medium . * Non-maintainer upload. * Build against libgnutls28-dev, drop b-d on libgcrypt-dev, fixing FTBFS. Closes: #758999 Checksums-Sha1: 015bcaffdc96ccdd50cc188f7b2364abec72d3c5 1772 gjiten_2.6-2.3.dsc 5b57fb858b6a41aead52cd7d7d4f35fa6934984d 1889 gjiten_2.6-2.3.diff.gz Checksums-Sha256: 246044bcdea57ebea8952e6743e7dcbe15732259593b152b7072a8766b8c673f 1772 gjiten_2.6-2.3.dsc ea87cf162be02f1803b7793a0c5463bdf162b35044648579d58e0c8a0af2cdad 1889 gjiten_2.6-2.3.diff.gz Files: 58b0b3267c3364b58b978441a454f2d2 1772 gnome optional gjiten_2.6-2.3.dsc d20dd6e3eccd6d9b2742e2e619b21589 1889 gnome optional gjiten_2.6-2.3.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT+dTDAAoJEKVPAYVDghSE9y4P/2uXk5IvFUXGgD/V4oZ6Xend wD93FQ5HWhP7pT0d+OcRM7Zjhygiu/OR6qU6ZfZRyIjVtOWUeFHlvjBVQajMvucv D86NDFwGLjYi/O/eXcX32MzgXCM/+x+LjF+5lpginCiuZhhqza/yhGJAS7QQeAWK LnRgMG0QYGRir1/EyyugAHIVDeHvf/XdolTw9FoKAAxVL/JNetAysVT4hmVJvrTN DR3/MgKKejxbTgWMhmt/TKipiHTSXV+lgBeV91UeIR6XI8o3qWrP//NsmbWI4VQj 8/Qu+pQScZBlWtzOa0q434kX/eL/oaYy6qCgcx6Hh/OpdMGAa2nv2pJGg82Y0mDP ll9oAGzziouQS7cNweTqQB4AbdqF+zbOmX+r/iDU0gSEx+e9qBgWikyEKHjtvFQg 9HNHQfyGKs0P00H87PCi64ZzkgNs3zf+e4HJBFOrPOfV33ve55vqwxZnbZLx424p
Bug#754759: openwalnut: FTBFS on kfreebsd-*: wrong linking flags
Hi Thank you for this bug report. I will fix this after my holidays. It looks like we missed an explicit link to the X libs. Expect an update at the end of September. Cheers, Sebastian On Mon, 14 Jul 2014, Cyril Brulebois wrote: Source: openwalnut Version: 1.4.0~rc1+hg3a3147463ee2-1 Severity: serious Justification: FTBFS Hi, openwalnut now fails to link on kfreebsd-*: | Linking CXX executable ../bin/openwalnut-qt4 | cd /«BUILDDIR»/openwalnut-1.4.0~rc1+hg3a3147463ee2/build/qt4gui /usr/bin/cmake -E cmake_link_script CMakeFiles/openwalnut-qt4.dir/link.txt --verbose=1 | /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -frtti -pedantic -std=c++98 -Wall -Wno-long-long -Wextra -O3 -Wl,-z,relro -Wl,--as-needed CMakeFiles/openwalnut-qt4.dir/WQtGLScreenCapture.cpp.o CMakeFiles/openwalnut-qt4.dir/OpenWalnut.cpp.o CMakeFiles/openwalnut-qt4.dir/WApplication.cpp.o CMakeFiles/openwalnut-qt4.dir/WSettingMenu.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtMessageDialog.cpp.o CMakeFiles/openwalnut-qt4.dir/WQt4Gui.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtGLDockWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtToolBarBase.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtMessagePopup.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkItemActivator.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkInputPort.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkOutputPort.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkScene.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkItemGrid.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkArrow.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkEditorView.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkPort.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkColors.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkEditorProjectFileIO.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkItem.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkSceneLayout.cpp.o CMakeFiles/openwalnut-qt4.dir/networkEditor/WQtNetworkEditor.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtGLWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/WQtNavGLWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleConnectEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WRoiAssocEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleAssocEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WRenderedFrameEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WLogEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WLoadFinishedEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleRemovedEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleCrashEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleDisconnectEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WPropertyChangedEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WCloseCustomDockWidgetEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WRoiSortEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WRoiRemoveEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleReadyEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleConnectorEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WOpenCustomDockWidgetEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WModuleDeleteEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/events/WUpdateTextureSorterEvent.cpp.o CMakeFiles/openwalnut-qt4.dir/WSettingAction.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertySelectionWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertyDoubleWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertyColorWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertyBoolWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WQtControlPanel.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertyWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WQtRoiTreeItem.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WQtTreeWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionLine.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionHistogram.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionPoint.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionColorPoint.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionWidget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionScene.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/transferFunction/WTransferFunctionBackground.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WQtModuleHeaderTreeItem.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WPropertyMatrix4X4Widget.cpp.o CMakeFiles/openwalnut-qt4.dir/controlPanel/WQtModuleTreeItem.cpp.o
Processed: Add blocking bug for FreeOrion
Processing commands for cont...@bugs.debian.org: block 759368 by 759682 Bug #759368 [freeorion] freeorion: ftbfs on mips(el) 759368 was not blocked by any bugs. 759368 was not blocking any bugs. Added blocking bug(s) of 759368: 759682 thanks Stopping processing here. Please contact me if you need assistance. -- 759368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759368 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
Processed: debian-installer: non-grub PXE boot images crash (was: Re: Bug#711799: PXE error: no server is specified)
Processing commands for cont...@bugs.debian.org: clone 711799 -1 Bug #711799 [grub-pc-bin] PXE error: no server is specified Bug 711799 cloned as bug 759686 759686 was not blocked by any bugs. 759686 was blocking: 695500 Added blocking bug(s) of 759686: 695500 retitle -1 debian-installer: non-grub PXE boot images crash Bug #759686 [grub-pc-bin] PXE error: no server is specified Changed Bug title to 'debian-installer: non-grub PXE boot images crash' from 'PXE error: no server is specified' severity -1 important Bug #759686 [grub-pc-bin] debian-installer: non-grub PXE boot images crash Severity set to 'important' from 'grave' reassign -1 debian-installer Bug #759686 [grub-pc-bin] debian-installer: non-grub PXE boot images crash Bug reassigned from package 'grub-pc-bin' to 'debian-installer'. No longer marked as found in versions grub2/2.00-22, grub2/2.00-14, and grub2/2.02~beta2-11. Ignoring request to alter fixed versions of bug #759686 to the same values previously set found -1 debian-installer/20140802 Bug #759686 [debian-installer] debian-installer: non-grub PXE boot images crash Marked as found in versions debian-installer/20140802. thanks Stopping processing here. Please contact me if you need assistance. -- 711799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711799 759686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759686 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#711799: debian-installer: non-grub PXE boot images crash (was: Re: Bug#711799: PXE error: no server is specified)
clone 711799 -1 retitle -1 debian-installer: non-grub PXE boot images crash severity -1 important reassign -1 debian-installer found -1 debian-installer/20140802 thanks On 29/08/14 03:16, Steven Chamberlain wrote: terminal and gettext [...], adding those two additional modules to the grub-mkimage line. And now it works! I'm still working on this. I've realised it will be better to track it separately from the original PXE issue, which seems fixed. 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
Bug#711799: marked as done (PXE error: no server is specified)
Your message dated Fri, 29 Aug 2014 14:16:04 +0100 with message-id 54007d14.2030...@pyro.eu.org and subject line Re: Bug#711799: PXE error: no server is specified has caused the Debian Bug report #711799, regarding PXE error: no server is specified 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.) -- 711799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: grub-pc-bin Version: 2.00-14 File: /usr/lib/grub/i386-pc/pxe.mod Severity: important Tags: d-i Control: affects -1 debian-installer Hi, Since upstream version 2.00, a GRUB2 PXE image fails to set grub_net_default_server and so is unable to proceed with booting. I built the image with: grub-mkimage -O i386-pc-pxe --prefix=(pxe) -o grub2pxe pxe tftp The image is not given a multiboot signature. I'm testing under Qemu with iPXE firmware (but with Etherboot it shows the same issue). $ qemu-system-x86_64 -m 128 -enable-kvm -net nic -net user,bootfile=grub2pxe,tftp=. -boot n It fails like this: iPXE 1.0.0+git-20120202.f6840ba-3 -- Open Source Network Boot Firmware -- http:/ /ipxe.org Features: HTTP iSCSI DNS TFTP AoE bzImage COMBOOT ELF MBOOT PXE PXEXT net0: 52:54:00:12:34:56 using E1000_DEV_ID_82540EM on PCI00:03.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] DHCP (net0 52:54:00:12:34:56).. ok net0: 10.0.2.15/255.255.255.0 gw 10.0.2.2 Next server: 10.0.2.2 Filename: grub2pxe tftp://10.0.2.2/grub2pxe... ok Welcome to GRUB! error: no server is specified. Entering rescue mode... net_ls_addr shows no output. If I run net_bootp manually, it gets an IP address and sets net_pxe_dhcp_*, but still does not set net_default_server or pxe_default_server. If I set net_default_server manually (to 10.0.2.2) I can then fetch files via TFTP through the (pxe) device. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-pc-bin depends on: ii grub-common 2.00-14 ii libc0.1 2.17-5 ii libgeom1 9.0+ds1-4 grub-pc-bin recommends no packages. Versions of packages grub-pc-bin suggests: pn desktop-base none -- no debconf information ---End Message--- ---BeginMessage--- Source-Version: 2.02~beta2-11 On 29/08/14 03:16, Steven Chamberlain wrote: [...] it looks like the PXE issue has been fixed in this version. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org---End Message---
Processed: Re: Bug#711799: PXE error: no server is specified
Processing commands for cont...@bugs.debian.org:
notfound 711799 grub2/2.02~beta2-11
Bug #711799 {Done: Steven Chamberlain ste...@pyro.eu.org} [grub-pc-bin] PXE
error: no server is specified
No longer marked as found in versions grub2/2.02~beta2-11.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
711799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711799
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
Processed: Re: Bug#756469: libfuntools-dev and libbsd-dev: error when trying to install together
Processing control commands: clone -1 -2 Bug #756469 [libbsd-dev,libfuntools-dev] libfuntools-dev and libbsd-dev: error when trying to install together Bug 756469 cloned as bug 759687 reassign -1 libbsd-dev Bug #756469 [libbsd-dev,libfuntools-dev] libfuntools-dev and libbsd-dev: error when trying to install together Bug reassigned from package 'libbsd-dev,libfuntools-dev' to 'libbsd-dev'. Ignoring request to alter found versions of bug #756469 to the same values previously set Ignoring request to alter fixed versions of bug #756469 to the same values previously set found -1 libbsd-dev/0.7.0-1 Bug #756469 [libbsd-dev] libfuntools-dev and libbsd-dev: error when trying to install together The source libbsd-dev and version 0.7.0-1 do not appear to match any binary packages Marked as found in versions libbsd-dev/0.7.0-1. reassign -2 libfuntools-dev Bug #759687 [libbsd-dev,libfuntools-dev] libfuntools-dev and libbsd-dev: error when trying to install together Bug reassigned from package 'libbsd-dev,libfuntools-dev' to 'libfuntools-dev'. Ignoring request to alter found versions of bug #759687 to the same values previously set Ignoring request to alter fixed versions of bug #759687 to the same values previously set retitle -2 libfuntools-dev: Please rename (at least) the funopen.3 man page Bug #759687 [libfuntools-dev] libfuntools-dev and libbsd-dev: error when trying to install together Changed Bug title to 'libfuntools-dev: Please rename (at least) the funopen.3 man page' from 'libfuntools-dev and libbsd-dev: error when trying to install together' severity -2 wishlist Bug #759687 [libfuntools-dev] libfuntools-dev: Please rename (at least) the funopen.3 man page Severity set to 'wishlist' from 'serious' -- 756469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756469 759687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759687 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#756469: libfuntools-dev and libbsd-dev: error when trying to install together
Control: clone -1 -2 Control: reassign -1 libbsd-dev Control: found -1 libbsd-dev/0.7.0-1 Control: reassign -2 libfuntools-dev Control: retitle -2 libfuntools-dev: Please rename (at least) the funopen.3 man page Control: severity -2 wishlist On Wed, 2014-07-30 at 08:57:06 +0200, Ralf Treinen wrote: Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man3/funopen.3.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. I'm fixing libbsd-dev as it's the one that introduced this while libfuntools-dev had already been using that pathname in Debian. But I think libfuntools-dev should ideally also rename at least its man page upstream, by at least suffixing the section number with something, for example funopen.3funtools or similar. Because otherwise this conflicts with the existing man page on BSD systems: http://www.freebsd.org/cgi/man.cgi?query=funopen http://www.openbsd.org/cgi-bin/man.cgi?query=funopen http://netbsd.gw.com/cgi-bin/man-cgi?funopen … But it might be worth considering eventually renaming the function altogether, as it can be very confusing on those systems. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754637: marked as done (ck: FTBFS on kfreebsd-i386: PIC register clobbered by '%ebx' in 'asm')
Your message dated Fri, 29 Aug 2014 13:57:37 + with message-id 104adedc18ae5e45870c06cf0304e344a28...@lemail01.le.imgtec.org and subject line Fixed in ck 0.4.3-1 has caused the Debian Bug report #754637, regarding ck: FTBFS on kfreebsd-i386: PIC register clobbered by '%ebx' in 'asm' 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.) -- 754637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ck Version: 0.4.2-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-i386: | make[3]: Entering directory `/«PKGBUILDDIR»/regressions/ck_cohort/benchmark' | /usr/bin/cc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -std=gnu99 -pedantic -Wall -W -Wundef -Wendif-labels -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wdisabled-optimization -fstrict-aliasing -O2 -pipe -Wno-parentheses -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -march=i586 -fPIC -I../../../include -DCORES=2 -m32 -D__x86__ -msse -msse2 -pthread -D_GNU_SOURCE -lm -o ck_cohort.THROUGHPUT throughput.c -lm | /usr/bin/cc -DLATENCY -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -std=gnu99 -pedantic -Wall -W -Wundef -Wendif-labels -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wdisabled-optimization -fstrict-aliasing -O2 -pipe -Wno-parentheses -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -march=i586 -fPIC -I../../../include -DCORES=2 -m32 -D__x86__ -msse -msse2 -pthread -D_GNU_SOURCE -lm -o ck_cohort.LATENCY ck_cohort.c | In file included from ../../ck_spinlock/benchmark/latency.h:34:0, | from ck_cohort.c:7: | ../../ck_spinlock/benchmark/../../common.h: In function 'main': | ../../ck_spinlock/benchmark/../../common.h:381:9: error: PIC register clobbered by '%ebx' in 'asm' | __asm__ __volatile__(cpuid; | ^ | ../../ck_spinlock/benchmark/../../common.h:387:9: error: PIC register clobbered by '%ebx' in 'asm' | __asm__ __volatile__(xorl %%eax, %%eax; | ^ | ../../ck_spinlock/benchmark/../../common.h:381:9: error: PIC register clobbered by '%ebx' in 'asm' | __asm__ __volatile__(cpuid; | ^ | ../../ck_spinlock/benchmark/../../common.h:387:9: error: PIC register clobbered by '%ebx' in 'asm' | __asm__ __volatile__(xorl %%eax, %%eax; | ^ | make[3]: *** [ck_cohort.LATENCY] Error 1 Full build log: https://buildd.debian.org/status/fetch.php?pkg=ckarch=kfreebsd-i386ver=0.4.2-1stamp=1399019497 Mraw, KiBi. ---End Message--- ---BeginMessage--- Version: 0.4.3-1 ck now builds on i386 and kfreebsd-i386 ---End Message---
Bug#759691: ck: file ck_hclh is not cleaned by debian/rules clean
Source: ck Version: 0.4.3-1 Justification: Policy 4.9 Severity: serious Tags: patch Hi, The file regressions/ck_spinlock/validate/ck_hclh is not removed after running cleaning the build tree. I've attached a patch to fix this. Also I closed a few bugs that were previously fixed, I hope you don't mind that. Thanks James -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 mipsel Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/regressions/ck_spinlock/validate/Makefile 2014-08-29 14:58:40.396839432 +0100 +++ b/regressions/ck_spinlock/validate/Makefile 2014-08-29 15:02:45.156728019 +0100 @@ -50,7 +50,7 @@ clean: rm -rf ck_ticket ck_mcs ck_dec ck_cas ck_fas ck_clh linux_spinlock ck_ticket_pb \ - ck_anderson ck_spinlock *.dSYM *.exe + ck_anderson ck_spinlock ck_hclh *.dSYM *.exe include ../../../build/regressions.build CFLAGS+=$(PTHREAD_CFLAGS) -D_GNU_SOURCE -lm
Bug#749500: rakudo: not installable in sid
On ven, ago 29, 2014 at 11:17:18 +0200, Dominique Dumont wrote: Ack. I'm going to relax the vesrioned dependency on nqp. I don't think that a strict dependency is necessary. Actually, it is. rakudo needs to use at runtime the specific nqp build used to build rakudo itself. If you update the nqp package (or just rebuilt it without any change) without rebuilding rakudo too, rakudo stops working and spews a bunch of Missing or wrong version of dependency ... errors. Hence the = dependency to make sure nqp and rakudo migrated to testing at the same time. You can actually test this by forcibly installing rakudo 2014.07-1 with nqp 2014.07-2 (dpkg -i rakudo_2014.07-1_amd64.deb --force-depends) and then run perl6. I don't know if anything changed, but IIRC the upstream developers had no plan on fixing this (in fact they didn't really consider it a bug at all, although they agreed it was annoying). One of the many joys of maintaining rakudo :/ I should have probably left a note about this somewhere but I didn't think about it at the time, sorry about that. Cheers signature.asc Description: Digital signature
Bug#759696: 3dldf: FTBFS on non-*amd64: invalid free in arc_1 test
Source: 3dldf Version: 2.0.3+dfsg-1 Severity: serious Justification: fails to build from source Builds of 3dldf for all architectures but (linux-)amd64 and kfreebsd-amd64 have been failing with errors along the lines of make[4]: Entering directory '/«BUILDDIR»/3dldf-2.0.3+dfsg/examples' ../src/3dldf arc_1.ldf *** Error in `../src/3dldf': free(): invalid pointer: 0x093c8840 *** make[4]: *** [arc_1.mp] Aborted Makefile_sub:21: recipe for target 'arc_1.mp' failed Could you please take a look? FWIW, I've generally had good results with GCC's new -fsanitize=address flag. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759558: gcj-4.9-jdk: broken symlinks for j{awt,ni}{,_md}.h
On Fri, 29 Aug 2014 00:30:56 +0200 Matthias Klose d...@debian.org wrote: Am 28.08.2014 um 18:08 schrieb Steven Chamberlain: reassign 759558 gcj-4.9-jdk found 759558 gcc-4.9/4.9.1-9 thanks gcj-4.9-jdk isn't a source package, so the BTS seems a little confused about who to mail about this bug; I don't think the maintainers were notified. The original bug report is here: https://bugs.debian.org/759558#5 fixed in the VCS. Any chance to have it uploaded soonish? It is blocking the hdf5 transition. Thanks in advance, _g. signature.asc Description: OpenPGP digital signature
Bug#750287: marked as done (php-db: FTBFS: Tests failures)
Your message dated Fri, 29 Aug 2014 15:20:00 + with message-id e1xnny4-00056n...@franck.debian.org and subject line Bug#750287: fixed in php-db 1.7.14-3 has caused the Debian Bug report #750287, regarding php-db: FTBFS: Tests failures 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.) -- 750287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: php-db Version: 1.7.14-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' dh_link -O--buildsystem=phppear chmod +x ./debian/tests_run ./debian/tests_run Testing with db_error.phpt PHPUnit 3.7.28 by Sebastian Bergmann. F Time: 126 ms, Memory: 2.50Mb There was 1 failure: 1) db_error.phpt --- Expected +++ Actual @@ @@ testing different error codes... + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX [db_error: message=db error: unknown error code=-1 mode=return level=notice prefix= info=] [db_error: message=db error: test error code=-1 mode=return level=notice prefix= info=] + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX [db_error: message=db error: no error code=1 mode=return level=notice prefix= info=] + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX [db_error: message=db error: unknown error code=-1 mode=return level=notice prefix= info=] + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX [db_error: message=db error: syntax error code=-2 mode=return level=notice prefix= info=] + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX [db_error: message=db error: division by zero code=-13 mode=return level=notice prefix= info=] testing different error modes... + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX DB Error: unknown error[db_error: message=db error: unknown error code=-1 mode=print level=notice prefix= info=] +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX + User Notice: DB Error: syntax error in PEAR.php on line XXX testing different error serverities... +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX + User Notice: DB Error: syntax error in PEAR.php on line XXX +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX + User Warning: DB Error: syntax error in PEAR.php on line XXX + +Notice: Undefined offset: 8192 in /«PKGBUILDDIR»/DB-1.7.14/tests/db_error.php on line 29 + +: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in DB.php on line XXX User Error: DB Error: syntax error in PEAR.php on line XXX FAILURES! Tests: 1, Assertions: 1, Failures: 1. make[1]: *** [override_dh_link] Error 1 The full build log is available from:
Bug#759700: gtkextra: FTBFS: `debian/libgtkextra-3.0-doc/': No such file or directory
Source: gtkextra
Version: 3.1.0-1
Severity: serious
Justification: fails to build from source
Builds of gtkextra covering only its architecture-dependent binary
packages (as on the autobuilders) have been failing:
debian/rules override_dh_install
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_install
find debian/libgtkextra-3.0-doc/ -type f -executable -exec chmod 644 {} \;
find: `debian/libgtkextra-3.0-doc/': No such file or directory
make[1]: *** [override_dh_install] Error 1
debian/rules:21: recipe for target 'override_dh_install' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2
debian/rules:14: recipe for target 'binary-arch' failed
Could you please arrange to make changes in the -doc tree only when it
actually exists?
Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759702: apq-postgresql: needs update for new apq packages
Package: apt-postgresql Version: 3.2.0-2.1 Severity: serious apq got upgraded and its packages renamed. That means apq-postgresql needs to be updated for them. Since the -dev package got renamed too, a sourceful upload is needed. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759701: libstxxl: FTBFS on 32-bit architectures
Source: libstxxl Version: 1.4.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of libstxxl 1.4.0 for 32-bit architectures have been failing with a cascade of errors, which you can find in full at https://buildd.debian.org/status/logs.php?pkg=libstxxlver=1.4.0-2suite=sid: In file included from /«PKGBUILDDIR»/include/stxxl/priority_queue:14:0, from /«PKGBUILDDIR»/tools/benchmark_pqueue.cpp:26: /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:870:47: error: template instantiation depth exceeds maximum of 1024 (use -ftemplate-depth= to increase the maximum) instantiating 'stxxl::priority_queue_local::find_B_m8u, 134217728u, 2097152ull, 8388608u, 1019u, true::c' static const external_size_type fits = (c 10) ^ /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:870:47: required from 'const external_size_type stxxl::priority_queue_local::find_B_m8u, 134217728u, 2097152ull, 8388608u, 1019u, true::fits' /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:875:109: recursively required from 'struct stxxl::priority_queue_local::find_B_m8u, 134217728u, 2097152ull, 8388608u, 2u, false' /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:875:109: required from 'struct stxxl::priority_queue_local::find_B_m8u, 134217728u, 2097152ull, 8388608u, 1u, false' /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:901:81: required from 'struct stxxl::priority_queue_local::find_settings8u, 134217728u, 2097152u' /«PKGBUILDDIR»/include/stxxl/bits/containers/priority_queue.h:965:106: required from 'class stxxl::PRIORITY_QUEUE_GENERATORstxxl::tupleunsigned int, unsigned int, my_cmpstxxl::tupleunsigned int, unsigned int , 134217728u, 2097152ull, 6u' /«PKGBUILDDIR»/tools/benchmark_pqueue.cpp:216:34: required from 'int do_benchmark_pqueue(stxxl::uint64, int) [with ValueType = stxxl::tupleunsigned int, unsigned int; long long unsigned int mib_for_queue = 128ull; long long unsigned int mib_for_pools = 128ull; long long unsigned int maxvolume = 16ull; stxxl::uint64 = long long unsigned int]' /«PKGBUILDDIR»/tools/benchmark_pqueue.cpp:265:72: required from 'int do_benchmark_pqueue_config(unsigned int, stxxl::uint64, unsigned int) [with ValueType = stxxl::tupleunsigned int, unsigned int; stxxl::uint64 = long long unsigned int]' /«PKGBUILDDIR»/tools/benchmark_pqueue.cpp:284:82: required from here ... Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759705: openjdk-7-jre-dcevm: FTBFS on i386: the stabs debug format cannot be used with pre-compiled headers
Source: openjdk-7-jre-dcevm Version: 7u55-1 Severity: serious Justification: fails to build from source The i386 build of openjdk-7-jre-dcevm failed: g++ -DLINUX -D_GNU_SOURCE -DIA32 -DPRODUCT -I. -I/«PKGBUILDDIR»/src/share/vm/prims -I/«PKGBUILDDIR»/src/share/vm -I/«PKGBUILDDIR»/src/share/vm/precompiled -I/«PKGBUILDDIR»/src/cpu/x86/vm -I/«PKGBUILDDIR»/src/os_cpu/linux_x86/vm -I/«PKGBUILDDIR»/src/os/linux/vm -I/«PKGBUILDDIR»/src/os/posix/vm -I../generated -DHOTSPOT_RELEASE_VERSION=\24.55-b03-dcevm-full\ -DHOTSPOT_BUILD_TARGET=\product\ -DHOTSPOT_BUILD_USER=\buildd\ -DHOTSPOT_LIB_ARCH=\i386\ -DHOTSPOT_VM_DISTRO=\Dynamic Code Evolution\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DTARGET_OS_FAMILY_linux -DTARGET_ARCH_x86 -DTARGET_ARCH_MODEL_x86_32 -DTARGET_OS_ARCH_linux_x86 -DTARGET_OS_ARCH_MODEL_linux_x86_32 -DTARGET_COMPILER_gcc -DCOMPILER2 -DCOMPILER1 -fno-rtti -fno-exceptions -D_REENTRANT -fcheck-new -fvisibility=hidden -m32 -march=i586 -pipe -DTARGET_OS_FAMILY_linux -DTARGET_ARCH_x86 -DTARGET_ARCH_MODEL_x86_32 -DTARGET_OS_ARCH_linux_x86 -DTARGET_OS_ARCH_MODEL_linux_x86_32 -DTARGET_COMPILER_gcc -DCOMPILER2 -DCOMPILER1 -fPIC -fno-rtti -fno-exceptions -D_REENTRANT -fcheck-new -fvisibility=hidden -m32 -march=i586 -pipe -O3 -fno-strict-aliasing -gstabs -DVM_LITTLE_ENDIAN -DINCLUDE_TRACE=1 -Werror -Wpointer-arith -Wsign-compare-c -fpch-deps -MMD -MP -MF ../generated/dependencies/precompiled.hpp.gch.d -x c++-header /«PKGBUILDDIR»/src/share/vm/precompiled/precompiled.hpp -o precompiled.hpp.gch cc1plus: error: the stabs debug format cannot be used with pre-compiled headers [-Werror=deprecated] cc1plus: all warnings being treated as errors /«PKGBUILDDIR»/make/linux/makefiles/vm.make:291: recipe for target 'precompiled.hpp.gch' failed make[6]: *** [precompiled.hpp.gch] Error 1 Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759696: 3dldf: FTBFS on non-*amd64: invalid free in arc_1 test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I will have a look ASAP. Thanks, Jerome On 29/08/14 16:49, Aaron M. Ucko wrote: Source: 3dldf Version: 2.0.3+dfsg-1 Severity: serious Justification: fails to build from source Builds of 3dldf for all architectures but (linux-)amd64 and kfreebsd-amd64 have been failing with errors along the lines of make[4]: Entering directory '/«BUILDDIR»/3dldf-2.0.3+dfsg/examples' ../src/3dldf arc_1.ldf *** Error in `../src/3dldf': free(): invalid pointer: 0x093c8840 *** make[4]: *** [arc_1.mp] Aborted Makefile_sub:21: recipe for target 'arc_1.mp' failed Could you please take a look? FWIW, I've generally had good results with GCC's new -fsanitize=address flag. Thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJUAJ54AAoJEIC/w4IMSybj+zgIAKNOM42dMDe6XA+aRvuoC4DV jnuNhF/dgBQI9m6nLzBYWYmWCqP5lbio0xwmd96kgTGJkjNoi5DXBHnLfwshx1UI 5dMDrdzvSwcLL3fIu1SbxcG8ybkqp43Slx6yjJaVBOgQ7VI55qQbCtgLzCk6Eixg MdqRIGW7tdsQiMCY3AcxfffPYaAhP12VfWUKLjnWlXJdgBErbwIRBpnRfT9aCAG3 ESg24nmKbdy80V3SGhzytUPxVEMvtbLQMcSwA+ExjWzdr95ajF9e0tyibBliSUNK QSa4RzkBjCf1Q+FzUiQDzdER+45XOkiUjI78qHKgSaHU4INyzB+lYYQ8hqviDFY= =/Y7h -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759702: apq-postgresql: needs update for new apq packages
Control: reassign -1 src:apq-postgresql On 29/08/14 17:36, Emilio Pozuelo Monfort wrote: Package: apt-postgresql Version: 3.2.0-2.1 Severity: serious apq got upgraded and its packages renamed. That means apq-postgresql needs to be updated for them. Since the -dev package got renamed too, a sourceful upload is needed. Stupid typo, reassigning to the right package. -- 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#759702: apq-postgresql: needs update for new apq packages
Processing control commands: reassign -1 src:apq-postgresql Bug #759702 [apt-postgresql] apq-postgresql: needs update for new apq packages Warning: Unknown package 'apt-postgresql' Bug reassigned from package 'apt-postgresql' to 'src:apq-postgresql'. No longer marked as found in versions 3.2.0-2.1. Ignoring request to alter fixed versions of bug #759702 to the same values previously set -- 759702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759702 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#759708: imms: FTBFS against new audacious
Source: imms Version: 3.1.0~svn301-3 Severity: serious Your package FTBFS against new libaudcore from the new audacious, see https://buildd.debian.org/status/fetch.php?pkg=immsarch=amd64ver=3.1.0~svn301-3%2Bb1stamp=1409239333 Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 759573 is grave, tagging 759573, found 759573 in 2.4-5, severity of 759574 is grave ...
Processing commands for cont...@bugs.debian.org: severity 759573 grave Bug #759573 [torrentflux] Information Disclosure in TorrentFlux Severity set to 'grave' from 'normal' tags 759573 + security upstream Bug #759573 [torrentflux] Information Disclosure in TorrentFlux Added tag(s) upstream and security. found 759573 2.4-5 Bug #759573 [torrentflux] Information Disclosure in TorrentFlux Marked as found in versions torrentflux/2.4-5. severity 759574 grave Bug #759574 [torrentflux] XSS in TorrentFlux Severity set to 'grave' from 'normal' tags 759574 + security upstream Bug #759574 [torrentflux] XSS in TorrentFlux Added tag(s) upstream and security. found 759574 2.4-5 Bug #759574 [torrentflux] XSS in TorrentFlux Marked as found in versions torrentflux/2.4-5. thanks Stopping processing here. Please contact me if you need assistance. -- 759573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759573 759574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759574 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#759702: Package update is in the works
tags 759702 + pending thanks I am currently working on updating the apq-postgresql package. Will upload it as soon as it is ready. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Package update is in the works
Processing commands for cont...@bugs.debian.org: tags 759702 + pending Bug #759702 [src:apq-postgresql] apq-postgresql: needs update for new apq packages Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 759702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759702 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#749500: rakudo: not installable in sid
On Fri, Aug 29, 2014 at 04:15:44PM +0200, Alessandro Ghedini wrote: On ven, ago 29, 2014 at 11:17:18 +0200, Dominique Dumont wrote: Ack. I'm going to relax the vesrioned dependency on nqp. I don't think that a strict dependency is necessary. Actually, it is. rakudo needs to use at runtime the specific nqp build used to build rakudo itself. [...] I don't know if anything changed, but IIRC the upstream developers had no plan on fixing this (in fact they didn't really consider it a bug at all, although they agreed it was annoying). One of the many joys of maintaining rakudo :/ The Rakudo and NQP developers do consider this a bug... it's just one that we cannot easily fix at the moment. For example, Parrot's underlying design requires the strong version linkages in its downstream components. Pm -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718699: marked as done (Changelog is not in UTF8)
Your message dated Fri, 29 Aug 2014 17:04:55 + with message-id e1xnpbb-0002fk...@franck.debian.org and subject line Bug#718699: fixed in python-mysqldb 1.2.3-2.1 has caused the Debian Bug report #718699, regarding Changelog is not in UTF8 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.) -- 718699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-mysqldb Version: 1.2.3-2 Severity: serious Hello, the package declares Standards-Version: 3.9.2 but the changelog is encoded in latin1. Since policy version 3.8.1.0, debian/changelog files must be encoded in UTF-8. This is currently breaking nm.debian.org in a way which cannot be worked around by me. See bug #717851. Ciao, Enrico -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-mysqldb depends on: ii libc6 2.17-7 ii libmysqlclient18 5.5.31+dfsg-1 ii python2.7.5-2 ii zlib1g1:1.2.8.dfsg-1 python-mysqldb recommends no packages. Versions of packages python-mysqldb suggests: ii mysql-server 5.5.31+dfsg-1 ii python-egenix-mxdatetime 3.2.5-1 pn python-mysqldb-dbgnone -- no debconf information ---End Message--- ---BeginMessage--- Source: python-mysqldb Source-Version: 1.2.3-2.1 We believe that the bug you reported is fixed in the latest version of python-mysqldb, 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 718...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Roeckx k...@roeckx.be (supplier of updated python-mysqldb 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, 29 Aug 2014 18:51:42 +0200 Source: python-mysqldb Binary: python-mysqldb python-mysqldb-dbg Architecture: source amd64 Version: 1.2.3-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Kurt Roeckx k...@roeckx.be Description: python-mysqldb - Python interface to MySQL python-mysqldb-dbg - Python interface to MySQL (debug extension) Closes: 718699 Changes: python-mysqldb (1.2.3-2.1) unstable; urgency=medium . * Non-maintainer upload. * Convert changelog to UTF-8 (Closes: #718699) Checksums-Sha1: a2c048ae74e126c9927532f8e38bc131326d00aa 2202 python-mysqldb_1.2.3-2.1.dsc da636c4f05505c683e02f35b8fd99570a2e9b6e7 9332 python-mysqldb_1.2.3-2.1.debian.tar.xz 2a9fd3c02873a2f35057ac11f8f874d97a594619 62172 python-mysqldb_1.2.3-2.1_amd64.deb 1be1955f6b1cd88b4f47a71a00b9a9f66d5ca2b7 58924 python-mysqldb-dbg_1.2.3-2.1_amd64.deb Checksums-Sha256: 73d629239b350edad1b39ed39a362570eb61dc687ab6396258fc38d8208a93b9 2202 python-mysqldb_1.2.3-2.1.dsc dc2115205ff6b7b1061627f56974a2f9f686b2f3b95700307dd22d10db0644bc 9332 python-mysqldb_1.2.3-2.1.debian.tar.xz d0546b26344a28e5c4f6ae59eb2b422945179c468440e32bec6d579fda316614 62172 python-mysqldb_1.2.3-2.1_amd64.deb 4b108c4123fee77abf157c8f07333eecdc2e3a58bd8dcc6f51efb1f3cb09b743 58924 python-mysqldb-dbg_1.2.3-2.1_amd64.deb Files: 2efeaf0781952aba2183ca87be99535e 62172 python optional python-mysqldb_1.2.3-2.1_amd64.deb bc79e1dbb296e2e3d5a77b2d6218e7cc 58924 debug extra python-mysqldb-dbg_1.2.3-2.1_amd64.deb 65ae9a77c3793df5c778598a48411cb9 2202 python optional python-mysqldb_1.2.3-2.1.dsc a5a61e3842adb1cd8850246f5edad13f 9332 python optional python-mysqldb_1.2.3-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUALDAAAoJEKGfLDAaVSLd2koP/AtJq/+zW4MYPTdSDLknuvhh JD59MHyRWWhr67Mh29Ls/PSqowNwFqKqE1tjSzZwDCP3iKTTeUvcLG9lnHp1LMnc S96XQjoH/gKVxBqlUrAmv1viqOI0pWBrNE4pnbIGDZ8PSLejQkf0KiAG1ncTha5s AyWme0m6rimIF0STKrZ9Q84nfPchiuPef+PgHDOH/r/TKBjP7kxWgJjtJjvoArf5 une4rmBKrYtJrOPB/hzLolo4zxxKX/TTDSYrrFy5c+XastFFCM9cJwVSYu+PbCpW SxLzVOIYIKRInzSUEz8gIuS/DtHFlTdxBoSfphy4yssMHTfq9AesPS1L2lihiqti
Bug#756469: marked as done (libfuntools-dev and libbsd-dev: error when trying to install together)
Your message dated Fri, 29 Aug 2014 17:04:31 + with message-id e1xnpbd-00029p...@franck.debian.org and subject line Bug#756469: fixed in libbsd 0.7.0-2 has caused the Debian Bug report #756469, regarding libfuntools-dev and libbsd-dev: error when trying to install together 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.) -- 756469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libbsd-dev,libfuntools-dev Version: libbsd-dev/0.7.0-1 Version: libfuntools-dev/1.4.4+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-07-30 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libbsd0:amd64. (Reading database ... 10858 files and directories currently installed.) Preparing to unpack .../libbsd0_0.7.0-1_amd64.deb ... Unpacking libbsd0:amd64 (0.7.0-1) ... Selecting previously unselected package libwcstools0:amd64. Preparing to unpack .../libwcstools0_3.8.7-2_amd64.deb ... Unpacking libwcstools0:amd64 (3.8.7-2) ... Selecting previously unselected package libfuntools1:amd64. Preparing to unpack .../libfuntools1_1.4.4+dfsg-1_amd64.deb ... Unpacking libfuntools1:amd64 (1.4.4+dfsg-1) ... Selecting previously unselected package libbsd-dev:amd64. Preparing to unpack .../libbsd-dev_0.7.0-1_amd64.deb ... Unpacking libbsd-dev:amd64 (0.7.0-1) ... Selecting previously unselected package libwcstools-dev. Preparing to unpack .../libwcstools-dev_3.8.7-2_amd64.deb ... Unpacking libwcstools-dev (3.8.7-2) ... Selecting previously unselected package libfuntools-dev. Preparing to unpack .../libfuntools-dev_1.4.4+dfsg-1_amd64.deb ... Unpacking libfuntools-dev (1.4.4+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libfuntools-dev_1.4.4+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/funopen.3.gz', which is also in package libbsd-dev:amd64 0.7.0-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/libfuntools-dev_1.4.4+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man3/funopen.3.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: libbsd Source-Version: 0.7.0-2 We believe that the bug you reported is fixed in the latest version of libbsd, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover guil...@debian.org (supplier of updated libbsd 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: SHA256 Format: 1.8 Date: Fri, 29 Aug 2014 14:42:03 +0200 Source: libbsd Binary: libbsd-dev libbsd0
Bug#756485: [Pkg-acpi-devel] Bug#756485: acpid: Unable to upgrade/downgrade
severity 756485 normal thanks On Mon, Aug 04, 2014 at 12:57:20PM +0200, Michael Meskes wrote: Please, pretty please, give us at least some output to see what may be happening on your system. My cystal ball is currently not working. :) ... I have no idea what /etc/sysctl.d has to do with acpid, sorry. Please run stop script with set -x and send the output. This bug report lacks important information and thus does not warrant its release critical status IMO. Therefore I cast it down to normal. Please send the missing information. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- 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#756485: [Pkg-acpi-devel] Bug#756485: acpid: Unable to upgrade/downgrade
Processing commands for cont...@bugs.debian.org: severity 756485 normal Bug #756485 [acpid] acpid: Unable to upgrade/downgrade Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 756485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756485 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
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 750867 important Bug #750867 [src:kde-runtime] kde-runtime: openssl license exception needed Severity set to 'important' from 'serious' End of message, stopping processing here. Please contact me if you need assistance. -- 750867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750867 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#759718: php-cas needs to urlencode all tickets (CVE-2014-4172)
Package: php-cas Severity: serious Tags: fixed-upstream Hi Olivier, php-cas 1.3.3 fixes security issue CVE-2014-4172: urlencode all tickets. Can you please upgrade php-cas in Debian to this version? thanks, Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759720: initramfs boot fails after unlocking encrypted root lv
Package: cryptsetup
Version: 2:1.4.3-4
Severity: serious
Tags: patch
[Rationale for severity serious: renders system unbootable]
I recently upgraded a Thecus n2100 from squeeze to wheezy [better late
than never!]. It's a headless system; the root filesystem is a logical
volume on LVM over an encrypted physical volume. I use dropbear to ssh
into the system at initramfs stage and unlock the encrypted PV, as
described in /usr/share/doc/cryptsetup/README.remote.gz.
After completing the upgrade and installing a new kernel version, I
rebooted the system. Although it was possible to log in remotely to
initramfs via ssh and successfully unlock encrypted root filesystem,
the system did not proceed to mount the root FS and boot.
Judging by the output of ps, a rescue shell is started after I unlock
the encrypted volume. There is no terminal connected to the system, so
I couldn't actually interact with the rescue shell, but grepping
through the rescue shell's environment gives:
REASON=ALERT! /dev/ram0 does not exist. Dropping to a shell!
Before unlocking encrypted device, /conf/param.conf contains
ROOT=/dev/mapper/name-of-root-lv line pointing to the correct root
device; after unlocking it contains *two* ROOT lines, the original,
correct line and a second, incorrect line (ROOT=/dev/ram0). I think
this second line is causing the subsequent boot process to fail.
It seems that the second line is put there by this part of
/usr/share/initramfs-tools/scripts/local-top/cryptroot after unlocking
the encrypted volume:
,[ /usr/share/initramfs-tools/scripts/local-top/cryptroot ]
| NEWROOT=${cmdline_root:-/dev/mapper/$cryptlvm}
| if [ $cryptrootdev = yes ]; then
| # required for lilo to find the root device
| echo ROOT=$NEWROOT /conf/param.conf
| fi
| eval $(fstype $NEWROOT)
`
The first, correct ROOT line is put there by flash-kernel: The n2100
uses redboot as a bootloader; redboot loads a kernel image and an
initramfs image from flash; in Debian, the flash-kernel package
automates the process of writing the kernel and the initramfs image to
flash; flash-kernel has explicit support for the n2100.
Because redboot passes the kernel bogus root parameter
[root=/dev/ram0], flash-kernel includes an initramfs-tools hook to
write the correct root device to /conf/param.conf when building the
initramfs image:
,[ /usr/share/initramfs-tools/hooks/flash_kernel_set_root ]
| # Should we override the root device or merely provide a default root
| # device?
| blsr=$(get_machine_field $machine Bootloader-sets-root)
|
| if [ $blsr = no ]; then
| # The boot loader doesn't pass root= on the command line, so
| # provide a default.
| install -d $DESTDIR/conf/conf.d
| echo ROOT=\$rootdev\ $DESTDIR/conf/conf.d/default_root
| else
| # The boot loader passes a bogus root= (e.g. root=/dev/ram), so
| # override the command line parameter.
| install -d $DESTDIR/conf
| echo ROOT=\$rootdev\ $DESTDIR/conf/param.conf
| fi
`
The quoted section of local-top/cryptoroot causes a bogus second
ROOT= entry (the bogus root=/dev/ram0 from the command line) to be
written to /conf/param.conf. This prevents boot process from
continuing correctly.
This problem is present both in the version of cryptsetup in wheezy,
and in the version in wheezy-backports (2:1.6.4-4~bpo70+1). I haven't
tested it, but I'm guessing the version in jessie is also affected.
I imagine that other system which use flash-kernel, with
Bootloader-sets-root=yes, would also be affected if they use root on a
LV over an encrypted device.
I attach a patch which fixes the issue for me, it could probably do
with further testing. The patch is against the version of cryptsetup in
wheezy-backports.
--- debian/initramfs/cryptroot-script.orig
+++ debian/initramfs/cryptroot-script
@@ -297,10 +297,15 @@
return 1
fi
- NEWROOT=${cmdline_root:-/dev/mapper/$cryptlvm}
- if [ $cryptrootdev = yes ]; then
-# required for lilo to find the root device
-echo ROOT=$NEWROOT /conf/param.conf
+ if [ -f /conf/param.conf ] grep -q '^ROOT=' /conf/param.conf
+ then
+eval $(sed -n 's/^ROOT=/NEWROOT=/p' /conf/param.conf)
+ else
+NEWROOT=${cmdline_root:-/dev/mapper/$cryptlvm}
+if [ $cryptrootdev = yes ]; then
+ # required for lilo to find the root device
+ echo ROOT=$NEWROOT /conf/param.conf
+fi
fi
eval $(fstype $NEWROOT)
fi
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tag 751731 + sid jessie
Bug #751731 [debian-installer] please use syslinux-utils instead of isolinux
for isohybird
Added tag(s) sid and jessie.
tag 759232 + sid jessie
Bug #759232 [gtktrain] gtktrain: FTBFS - Makefile:206: *** missing separator
Added tag(s) sid and jessie.
tag 759237 + sid jessie
Bug #759237 [pdfmod] pdfmod: FTBFS - The label `SkipChar:' could not be found
within the scope of the goto statement
Added tag(s) sid and jessie.
tag 759242 + sid jessie
Bug #759242 [pidgin-audacious] pidgin-audacious: FTBFS - audacious/audctrl.h:
No such file or directory
Added tag(s) sid and jessie.
tag 759252 + sid jessie
Bug #759252 [gjay] gjay: FTBFS - audacious/dbus.h: No such file or directory
Added tag(s) sid and jessie.
tag 758999 + sid jessie
Bug #758999 {Done: Andreas Metzler ametz...@debian.org} [gjiten] gjiten:
FTBFS due to conflicting (transitive) b-d libgnutls-dev - libgnomevfs2-dev
Added tag(s) sid and jessie.
tag 759200 + sid jessie
Bug #759200 [libevolution,libgtkhtml-4.0-0] evolution: uninstallable in
sid/amd64: needs libgtkhtml-4.0-0 4.8
Added tag(s) sid and jessie.
tag 758836 + sid jessie
Bug #758836 {Done: Dimitri Fontaine d...@tapoueh.org}
[cl-alexandria,cl-chunga] cl-chunga and cl-alexandria: error when trying to
install together
Added tag(s) sid and jessie.
tag 758897 + sid jessie
Bug #758897 [fckeditor] Should not be shipped in jessie
Added tag(s) sid and jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
751731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751731
758836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758836
758897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758897
758999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758999
759200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759200
759232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759232
759237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759237
759242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759242
759252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759252
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#759736: elasticsearch: CVE-2014-3120
Source: elasticsearch Severity: grave Tags: security upstream fixed-upstream Hi Hilko, I see elasticsearch entered unstable now. Some time ago the following vulnerability was published for elasticsearch. CVE-2014-3120[0]: | The default configuration in Elasticsearch before 1.2 enables dynamic | scripting, which allows remote attackers to execute arbitrary MVEL | expressions and Java code via the source parameter to _search. NOTE: | this only violates the vendor's intended security policy if the user | does not run Elasticsearch in its own independent virtual machine. If I understand it correctly, the value or this defaults to false, more references are in Red Hat's Bugzilla[1]. Could you check elasticsearch for this? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3120 https://security-tracker.debian.org/tracker/CVE-2014-3120 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1124252 [2] https://github.com/elasticsearch/elasticsearch/issues/5853 [3] https://github.com/elasticsearch/elasticsearch/commit/81e83cca Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711799: debian-installer: non-grub PXE boot images crash
tags 711799 + patch thanks Hi KiBi, Please may I commit this patch directly to debian-installer Git? Hopefully it is self-explanatory from the changelog. Earlier I thought it was modules terminal+gettext that were missing to cause the hang/crash, but it turned out to be only tftp. (I'd been testing dozens of permutations of different GRUB version [Debian- packaged and vanilla upstream], different builds [official Debian and my own], different selection of GRUB modules, and different versions of grub-image; so I made a few mistakes along the way that led me to wrong conclusions initially.) The xorriso incompatiblity refers to this scary warning seen with an outdated xorriso package but newer grub-common: grub-mkrescue: warning: Your xorriso doesn't support `--grub2-boot-info'. Some features are disabled. Please use xorriso 1.2.9 or later.. grub-mkrescue: warning: Your xorriso doesn't support `--grub2-boot-info'. Your core image is too big. Boot as disk is disabled. Please use xorriso 1.2.9 or later.. I don't know if it caused actual breakage, but since 1.3.2-1 is already in sid/jessie I felt it safer to raise Build-Depends to that version. Thanks. --- a/debian/changelog +++ b/debian/changelog @@ -13,6 +13,18 @@ debian-installer (2014) UNRELEASED; urgency=low adding a syslinux-utils build-dep (Closes: #751731), no thanks to its maintainer as far as cooperation is concerned (See: #751724, #759189). + [ Steven Chamberlain ] + * On kfreebsd and hurd, which use GRUB for PXE booting, request two +additional modules in the grub-mkimage step: (Closes: #711799) +- tftp: required since GRUB 2.02 otherwise PXE boot will crash/hang +- gfxterm_background: required since GRUB 2.02 for the boot splash + image functionality to be available +- raise the grub-pc (and indirectly grub-common) build dependency to + = 2.02~beta2~ on these architectures, because module + gfxterm_background did not exist in GRUB 2.00 +- raise the xorriso build dependency to = 1.3.2-1~ on these + architectures, for compatibility with grub-mkrescue in GRUB 2.02 + -- Cyril Brulebois k...@debian.org Sat, 02 Aug 2014 02:59:35 +0200 debian-installer (20140802) unstable; urgency=low --- a/debian/control +++ b/debian/control @@ -157,9 +157,9 @@ Build-Depends: # Alternative boot method for win32 platforms. makefs [kfreebsd-any], # Used to create an UFS1 filesystem from a directory tree. - grub-pc (= 1.99-1~) [kfreebsd-i386 kfreebsd-amd64 hurd-i386], + grub-pc (= 2.02~beta2~) [kfreebsd-i386 kfreebsd-amd64 hurd-i386], # Used as the CD-ROM's bootloader - xorriso [kfreebsd-i386 kfreebsd-amd64 hurd-i386], + xorriso (= 1.3.2-1~) [kfreebsd-i386 kfreebsd-amd64 hurd-i386], # Used by grub-pc to create the CD-ROM images debian-ports-archive-keyring [sh4 sparc64], # Used for architectures hosted on debian-ports.org --- a/build/config/hurd.cfg +++ b/build/config/hurd.cfg @@ -33,7 +33,7 @@ GRUB_CFG_PXE=boot/hurd/grub-hurd-pxe.cfg # GRUB modules GRUB_PLATFORM=i386-pc GRUB_MODDIR=/usr/lib/grub/$(GRUB_PLATFORM) -GRUB_MODULES_PXE=pxe multiboot cpuid echo gfxterm gzio minicmd normal png vbe +GRUB_MODULES_PXE=pxe tftp multiboot cpuid echo gfxterm gfxterm_background gzio minicmd normal png vbe # Location for Xen example configuration. XENCFG = $(SOME_DEST)/$(EXTRANAME)debian.cfg --- a/build/config/kfreebsd.cfg +++ b/build/config/kfreebsd.cfg @@ -15,7 +15,7 @@ GRUB_CFG_PXE=boot/kfreebsd/grub-kfreebsd-pxe.cfg # GRUB modules GRUB_PLATFORM=i386-pc GRUB_MODDIR=/usr/lib/grub/$(GRUB_PLATFORM) -GRUB_MODULES_PXE=pxe bsd cpuid echo gfxterm gzio minicmd normal png vbe +GRUB_MODULES_PXE=pxe tftp bsd cpuid echo gfxterm gfxterm_background gzio minicmd normal png vbe # Location for Xen example configuration. XENCFG = $(SOME_DEST)/$(EXTRANAME)debian.cfg -- 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#711799: debian-installer: non-grub PXE boot images crash
Processing commands for cont...@bugs.debian.org:
tags 711799 + patch
Bug #711799 {Done: Steven Chamberlain ste...@pyro.eu.org} [grub-pc-bin] PXE
error: no server is specified
Added tag(s) patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
711799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711799
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
Processed: Re: Bug#759686: debian-installer: non-grub PXE boot images crash
Processing commands for cont...@bugs.debian.org:
tags 711799 - patch
Bug #711799 {Done: Steven Chamberlain ste...@pyro.eu.org} [grub-pc-bin] PXE
error: no server is specified
Removed tag(s) patch.
tags 759686 + patch
Bug #759686 [debian-installer] debian-installer: non-grub PXE boot images crash
Added tag(s) patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
711799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711799
759686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759686
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#759741: FTBFS: -O2: command not found
Package: octave-odepkg Version: 0.8.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) I'm afraid that your package fails to build on current unstable (tested on armhf and amd64). The interesting part of the log is: FFLAGS=-g -O2 -fstack-protector-strong /usr/bin/mkoctfile -DHAVE_OCTAVE_38 -v -c cash/mebdfdae.f -o cash/mebdfdae.o /bin/bash: -O2: command not found make[1]: *** [cash/mebdfdae.o] Error 127 Makefile:49: recipe for target 'cash/mebdfdae.o' failed make[1]: Leaving directory '/tmp/oct-yhIrtK/src' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759663: [pkg-octave/master] Disable java on mips.
tag 759663 pending thanks Date: Fri Aug 29 22:38:31 2014 +0200 Author: Sébastien Villemot sebast...@debian.org Commit ID: 4f87d1af82a202c3b142fa50fdb756bf65fa7b3b Commit URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b Patch URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff_plain;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b Disable java on mips. Closes: #759663 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [pkg-octave/master] Disable java on mips.
Processing commands for cont...@bugs.debian.org: tag 759663 pending Bug #759663 [src:octave] octave: FTBFS on mips - Please add mips to NO_JDK_ARCHS Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 759663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759663 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
Processed: Help needed on #747993
Processing commands for cont...@bugs.debian.org: tag 747993 - pending Bug #747993 [xorp] xorp: non-standard gcc/g++ used for build (gcc-4.6) Removed tag(s) pending. tag 747993 + help Bug #747993 [xorp] xorp: non-standard gcc/g++ used for build (gcc-4.6) Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 747993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747993 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#757447: marked as done ([src:tcpdf] Non free icc profile)
Your message dated Fri, 29 Aug 2014 21:07:42 + with message-id e1xntoy-0008ru...@franck.debian.org and subject line Bug#757447: fixed in tcpdf 6.0.091+dfsg-1 has caused the Debian Bug report #757447, regarding [src:tcpdf] Non free icc profile 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.) -- 757447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:tcpdf Version: 6.0.048+dfsg-2 Severity: serious Hi, Your package include a non free file: include/sRGB.icc usual name is sRGB_IEC61966-2-1_black_scaled.icc. Does not allow modification. See also https://packages.debian.org/sid/icc-profiles. Thanks Bastien ---End Message--- ---BeginMessage--- Source: tcpdf Source-Version: 6.0.091+dfsg-1 We believe that the bug you reported is fixed in the latest version of tcpdf, 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 757...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog hert...@debian.org (supplier of updated tcpdf 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: SHA256 Format: 1.8 Date: Fri, 29 Aug 2014 22:06:12 +0200 Source: tcpdf Binary: php-tcpdf Architecture: source all Version: 6.0.091+dfsg-1 Distribution: unstable Urgency: low Maintainer: Laurent Destailleur (eldy) e...@users.sourceforge.net Changed-By: Raphaël Hertzog hert...@debian.org Description: php-tcpdf - PHP class for generating PDF files on-the-fly Closes: 757447 Changes: tcpdf (6.0.091+dfsg-1) unstable; urgency=low . [ Laurent Destailleur (eldy) ] * New upstream release 6.0.091+dfsg * Fix: Removed file include/sRGB.icc. This remove support for PDF/A-1b but solve any license troubles (Closes: #757447) . [ Raphaël Hertzog ] * Restore sRGB.icc as a symlink to icc-profiles-free's /usr/share/color/icc/sRGB.icc * Add “Files-Excluded: include/sRGB.icc” to debian/copyright so that uscan automatically repacks new upstream tarballs. Checksums-Sha1: c05e65ed9cf5db472c22f3cb03ac5355a62d74d8 1600 tcpdf_6.0.091+dfsg-1.dsc 0255522913d12ca438a38242ad539f4520b04903 7954784 tcpdf_6.0.091+dfsg.orig.tar.xz a93211ec4c8e1e158599070f848e832ba23b6b28 5216 tcpdf_6.0.091+dfsg-1.debian.tar.xz da12c74c7095dfd5958a51a31bc508ca5358ef81 7874728 php-tcpdf_6.0.091+dfsg-1_all.deb Checksums-Sha256: 5bbea7f49c6547c47f9579a717aca815c45d4ca12448824a9cabd423ad1df164 1600 tcpdf_6.0.091+dfsg-1.dsc d34732af1a8d587d4b022b34921559e8e99b18c675353ee38b4b82aa6b981491 7954784 tcpdf_6.0.091+dfsg.orig.tar.xz 424ba0f9abdaf25c316b2fe3291a5ea418720c082484fd6fc3d7708799f78a09 5216 tcpdf_6.0.091+dfsg-1.debian.tar.xz 4eb89b82e5a42d7b6c94c279bb58701294c578576c7cf569334faacd49a5a920 7874728 php-tcpdf_6.0.091+dfsg-1_all.deb Files: 4a36a642a0413f385b98f35cc7e6d094 7874728 php optional php-tcpdf_6.0.091+dfsg-1_all.deb 3d9d3fd3110b987c86be9ad77d3a10fa 1600 php optional tcpdf_6.0.091+dfsg-1.dsc 2bb058e9c6120e6e02e8fb48b44d3fb2 7954784 php optional tcpdf_6.0.091+dfsg.orig.tar.xz 0015997bcbeeb1aeab6a6900c6b75d15 5216 php optional tcpdf_6.0.091+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Signed by Raphael Hertzog iQEcBAEBCAAGBQJUAN2uAAoJEAOIHavrwpq5JwgH/0iJLlYL8W4YSGWiiqun8KTx phw1hODFnPc5SR0qLrhERpeR7Chw/lRtrtWZTt0w2hMThKzZdAnXBii5SYnWrFRR JtKyGpWNW8X0ydXpvXRmUv+PfG+cU8gRPsawSXOudhxUN2BgDtGGn9DPJ8MZHahc BkEFXwb26yrTfFiyOotSAPCGFInZFw5Cpuac7+/DOEWxfh95jTFhzHgCsNEW31Ar 1URKmvFKrVugvTg/i/V5zUvi3gIHz6DiyUrlMvsEZeNR6o+shDBBmJYuLHBItXju VOE5XwGAwAdtMvO9SPKjDULfOt44OPCLUqHi9Myvr9zeADIULZmTyBtspvGeR/w= =dNw7 -END PGP SIGNATUREEnd Message---
Bug#759700: marked as done (gtkextra: FTBFS: `debian/libgtkextra-3.0-doc/': No such file or directory)
Your message dated Fri, 29 Aug 2014 21:04:47 +
with message-id e1xntlj-0007n2...@franck.debian.org
and subject line Bug#759700: fixed in gtkextra 3.1.0-2
has caused the Debian Bug report #759700,
regarding gtkextra: FTBFS: `debian/libgtkextra-3.0-doc/': No such file or
directory
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.)
--
759700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gtkextra
Version: 3.1.0-1
Severity: serious
Justification: fails to build from source
Builds of gtkextra covering only its architecture-dependent binary
packages (as on the autobuilders) have been failing:
debian/rules override_dh_install
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_install
find debian/libgtkextra-3.0-doc/ -type f -executable -exec chmod 644 {} \;
find: `debian/libgtkextra-3.0-doc/': No such file or directory
make[1]: *** [override_dh_install] Error 1
debian/rules:21: recipe for target 'override_dh_install' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2
debian/rules:14: recipe for target 'binary-arch' failed
Could you please arrange to make changes in the -doc tree only when it
actually exists?
Thanks!
---End Message---
---BeginMessage---
Source: gtkextra
Source-Version: 3.1.0-2
We believe that the bug you reported is fixed in the latest version of
gtkextra, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
georg...@debian.org (supplier of updated gtkextra 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: SHA1
Format: 1.8
Date: Fri, 29 Aug 2014 18:17:56 +0200
Source: gtkextra
Binary: libgtkextra-3.0 libgtkextra-dev libgtkextra-3.0-doc
Architecture: source amd64 all
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar georg...@debian.org
Changed-By: georg...@debian.org
Description:
libgtkextra-3.0 - useful set of widgets for creating GUI's for GTK+
libgtkextra-3.0-doc - documentation for libgtkextra-x11-3.0
libgtkextra-dev - development files for libgtkextra-x11-3.0
Closes: 759700
Changes:
gtkextra (3.1.0-2) unstable; urgency=medium
.
* fixed a FTBFS bug for architectures which run only the binary build:
the script modifying file permissions in the architecture-independent
subdirectory must be allowed to fail nicely when this subderectory
is not there. Closes: #759700
* removed the build-dependency on obseleted package hardening-wrapper
Checksums-Sha1:
30bb630ebd233b43ecfc38d41bc131ec83501cb1 1445 gtkextra_3.1.0-2.dsc
260fc073a41454a45b87f833fd086e7d353c9e26 9528 gtkextra_3.1.0-2.debian.tar.xz
c2f4f4437f390ddb5dc95f8ba96d0373cb2a644a 319552
libgtkextra-3.0_3.1.0-2_amd64.deb
a22691f48d58bf17f3258333b515ffb400d0495c 68412
libgtkextra-dev_3.1.0-2_amd64.deb
15e3c9e439b6db50d7e9bef339ee795765a3fb3f 279096
libgtkextra-3.0-doc_3.1.0-2_all.deb
Checksums-Sha256:
212e36cc17194c6927ac244ef979141de006aba5bbe6e5bada60bcca031e1db0 1445
gtkextra_3.1.0-2.dsc
5a40856075dab0545bb49c23960bffefcc1413522d039a1756555ef03e5398ef 9528
gtkextra_3.1.0-2.debian.tar.xz
413271d3d19d43cf23259c644d7cdb8a4cdf20eff2c1c04b88f410e2c29a4654 319552
libgtkextra-3.0_3.1.0-2_amd64.deb
2669c14f5ac3cc7554b7c4244654fb0e8a8ba93054b06663ba5e490717e7b705 68412
libgtkextra-dev_3.1.0-2_amd64.deb
3957a56b20ec671daa14c63ce3923faf11a30ec59bfffb765b8fb959828b1e7d 279096
libgtkextra-3.0-doc_3.1.0-2_all.deb
Files:
163cd0c1a3658b91febf25686dff1dfd 319552 devel optional
libgtkextra-3.0_3.1.0-2_amd64.deb
cca5a65614db27f71ae8a6eacede678d 68412 libdevel optional
libgtkextra-dev_3.1.0-2_amd64.deb
a7b24aef5c14fa87b1f65759c577754f 279096 doc optional
libgtkextra-3.0-doc_3.1.0-2_all.deb
2ae38ec01026409b83d31f9a023c643e 1445 devel optional gtkextra_3.1.0-2.dsc
ec1d6270c8e5e099a6fc4148a1104255 9528 devel optional
gtkextra_3.1.0-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iD8DBQFUAOSUnfmb2hFpETARAr+xAJoCL796Vk2Hwc7E4+/2+wY44+G+9ACaArMg
FRRy6P19+8DlaBny3Pose4M=
=55QH
-END PGP SIGNATUREEnd
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
Hi, Please may I commit this to d-i/netcfg (assuming my d-i Git privileges include that repository). As well as kfreebsd, I expect hurd is currently affected by this bug, so this patch would also fix it there. Thanks. --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +netcfg (1.120) UNRELEASED; urgency=medium + + [ Steven Chamberlain ] + * Do not kill_dhcp_client after setting the hostname and domain, +otherwise Linux udhcpc will stop renewing its lease, and on other +platforms dhclient will de-configure the network interface +(Closes: #757711, #757988) + + -- Debian Install System Team debian-b...@lists.debian.org Fri, 29 Aug 2014 22:05:47 +0100 + netcfg (1.119) unstable; urgency=medium [ Colin Watson ] diff --git a/dhcp.c b/dhcp.c index aa37bd0..5ef0dbc 100644 --- a/dhcp.c +++ b/dhcp.c @@ -614,7 +614,6 @@ int netcfg_activate_dhcp (struct debconfclient *client, struct netcfg_interface netcfg_write_loopback(); netcfg_write_interface(interface); netcfg_write_resolv(domain, interface); -kill_dhcp_client(); stop_rdnssd(); return 0; -- 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
Bug#759573: Information Disclosure in TorrentFlux
FTR in the bug: Given that it is also possible to delete or modify cookies. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
Steven Chamberlain ste...@pyro.eu.org (2014-08-29): Please may I commit this to d-i/netcfg (assuming my d-i Git privileges include that repository). (Yes, we have no per-repository settings that I'm aware of.) As well as kfreebsd, I expect hurd is currently affected by this bug, so this patch would also fix it there. Thanks. --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +netcfg (1.120) UNRELEASED; urgency=medium + + [ Steven Chamberlain ] + * Do not kill_dhcp_client after setting the hostname and domain, +otherwise Linux udhcpc will stop renewing its lease, and on other +platforms dhclient will de-configure the network interface +(Closes: #757711, #757988) + + -- Debian Install System Team debian-b...@lists.debian.org Fri, 29 Aug 2014 22:05:47 +0100 + netcfg (1.119) unstable; urgency=medium [ Colin Watson ] diff --git a/dhcp.c b/dhcp.c index aa37bd0..5ef0dbc 100644 --- a/dhcp.c +++ b/dhcp.c @@ -614,7 +614,6 @@ int netcfg_activate_dhcp (struct debconfclient *client, struct netcfg_interface netcfg_write_loopback(); netcfg_write_interface(interface); netcfg_write_resolv(domain, interface); -kill_dhcp_client(); stop_rdnssd(); return 0; I'd be slightly happier if Philipp would comment on this since he seems to be the one having committed this change. See: | commit 8802ca520d9e91542d92bbfa5b2fc412a31cf2e2 | Author: Matt Palmer mpal...@hezmatt.org | Date: Sun Jan 30 22:29:42 2011 +1100 | | IPv6 support for using rDNS to preseed hostnames | | A lot of refactoring to make the code cleaner and simpler, but the | IPv6-specific changes were actually relatively small. | | Rebased-and-modified-by: Philipp Kern pk...@debian.org http://anonscm.debian.org/cgit/d-i/netcfg.git/commit/?id=8802ca520d9e91542d92bbfa5b2fc412a31cf2e2 Mraw, KiBi. signature.asc Description: Digital signature
Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed
Package: gdm3 Version: 3.12.2-2.1 Severity: grave Justification: renders package unusable Performed routine aptitude upgrade and had new version of gdm installed. Shutdown laptop and upon restart was no longer presented with the login greeter. Gnome environment would work by getting to shell and running startx but was presented with a systemd-login error on the console shell when logging in. Installed systemd-sysv which purged sysinit-core, rebooted and the system was once again usable. Suggest that there is a dependency not properly resolving in there to ensure that systemd is running as PID 1. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3 ii adduser 3.113+nmu3 ii dconf-cli0.20.0-2 ii dconf-gsettings-backend 0.20.0-2 ii debconf [debconf-2.0]1.5.53 ii gir1.2-gdm3 3.12.2-2.1 ii gnome-session [x-session-manager]3.12.1-3 ii gnome-session-bin3.12.1-3 ii gnome-session-flashback [x-session-manager] 3.8.1-1 ii gnome-settings-daemon3.12.2-1 ii gnome-shell 3.12.2-3 ii gnome-terminal [x-terminal-emulator] 3.12.3-2 ii gsettings-desktop-schemas3.12.2-1 ii libaccountsservice0 0.6.37-3 ii libatk1.0-0 2.12.0-1 ii libaudit11:2.3.7-1 ii libc62.19-9 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgdm1 3.12.2-2.1 ii libglib2.0-0 2.40.0-4 ii libglib2.0-bin 2.40.0-4 ii libgtk-3-0 3.12.2-3 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 208-8 ii libpam0g 1.1.8-3.1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-0 1.36.6-1 ii librsvg2-common 2.40.3-1 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-8 ii libsystemd-id128-0 208-8 ii libsystemd-journal0 208-8 ii libsystemd-login0208-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii metacity [x-window-manager] 1:3.12.0-2 ii policykit-1 0.105-6.1 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils7.7+3 ii xterm [x-terminal-emulator] 308-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.12.0-2 ii desktop-base 7.0.3 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.0-1 ii xserver-xorg 1:7.7+7 ii zenity 3.12.1-1.1 Versions of packages gdm3 suggests: ii gnome-orca3.12.2-1 ii libpam-gnome-keyring 3.8.2-2+b1 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754310: netgen: meshing a STEP file makes X crash
On Sun, 10 Aug 2014 14:03:34 -0400 Caitlin Matos wrote: [...] I cannot reproduce this error on my machine, with all the latest versions of the dependencies from testing. Hello Caitlin! First of all, thanks for your response and sorry for my late reply. Also, many of the x11-related packages underwent a significant update since then (e.g., xserver-xorg-core in testing went from 1.15.1-1 to 1.16.0-1). Can you try on your machine with the updated packages and see if the problem still occurs? I tried again with the system up-to-date with respect to current Debian testing. Unfortunately I am still able to reproduce the bug exactly as originally reported. If so, perhaps you should include some specs about the machine itself (RAM, GPU, etc), as maybe your hardware is too old? The memory capacity is 8 GiB, the graphics chipset is Intel G45/G43. Please see the attached output of glxinfo, dmesg, and the X log. Also, what WM or DE are you using? I am using the Fluxbox window manager. Also, what kind of output do you get to STDOUT before it crashes? I realise you can't copy + paste this, so I have attached my own output for you to look at. How far along do you get before it freezes? It seems to freeze as soon as I maximize the window (after minimizing it) or as soon as I switch workspace and then come back, and possibly after other GUI actions. So it depends on when I perform those actions... I hope this helps to pinpoint the bug... Please let me know, in case you need further information, but please take into account that the machine where I experience the bug is a production box: hence, I cannot afford to power-cycle it too often... :-( Thanks for your time. -- http://www.inventati.org/frx/ fsck is a four letter word... . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE dmesg.out.gz Description: application/gzip glxinfo.out.gz Description: application/gzip Xorg.0.log.gz Description: application/gzip pgpll0MwZ69S4.pgp Description: PGP signature
Bug#756838: marked as done (acpica-unix: FTBFS on big-endian architectures)
Your message dated Fri, 29 Aug 2014 21:48:40 + with message-id e1xnu2c-0005il...@franck.debian.org and subject line Bug#756838: fixed in acpica-unix 20140828-1 has caused the Debian Bug report #756838, regarding acpica-unix: FTBFS on big-endian architectures 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.) -- 756838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: acpica-unix Version: 20140724-1 Severity: serious Justification: fails to build from source (but built successfully in the past) acpica-unix failed to build on big endian architectures with: | # misc tests | /«PKGBUILDDIR»/debian/run-misc-tests.sh /«PKGBUILDDIR» 20140724 | + CURDIR=/«PKGBUILDDIR» | + BINDIR=/«PKGBUILDDIR»/generate/unix/bin | + DEBDIR=/«PKGBUILDDIR»/debian | + VERSION=20140724 | + cd /«PKGBUILDDIR»/tests/misc | + /«PKGBUILDDIR»/generate/unix/bin/iasl -h | iASL is not currently supported on big-endian machines. | ++ dpkg-architecture -qDEB_HOST_ARCH_BITS | + BITS=32 | ++ stat --format=%Y /«PKGBUILDDIR»/generate/unix/bin/iasl | ++ cut '-d ' -f1 | + FDATE=1406598005 | ++ date --date=@1406598005 '+%b %_d %Y' | + WHEN='Jul 29 2014' | + sed -e 's/XXX/Jul 29 2014/' -e s//32/ -e s//20140724/ /«PKGBUILDDIR»/debian/badcode.asl.result | + sed -e 's/XXX/Jul 29 2014/' -e s//32/ -e s//20140724/ /«PKGBUILDDIR»/debian/grammar.asl.result | + /«PKGBUILDDIR»/generate/unix/bin/iasl -f badcode.asl | + tee badcode | iASL is not currently supported on big-endian machines. | + diff badcode badcode.asl.result | + '[' 1 -eq 0 ']' | + exit 1 | make[2]: *** [check] Error 1 Full build logs are available from https://buildd.debian.org/status/package.php?p=acpica-unix. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: acpica-unix Source-Version: 20140828-1 We believe that the bug you reported is fixed in the latest version of acpica-unix, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Al Stone a...@debian.org (supplier of updated acpica-unix 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: SHA1 Format: 1.8 Date: Fri, 29 Aug 2014 14:42:27 -0600 Source: acpica-unix Binary: acpica-tools iasl acpidump Architecture: source amd64 all Version: 20140828-1 Distribution: unstable Urgency: medium Maintainer: Mattia Dongili malat...@debian.org Changed-By: Al Stone a...@debian.org Description: acpica-tools - ACPICA tools for the development and debug of ACPI tables acpidump - transitional dummy package iasl - transitional dummy package Closes: 756838 Changes: acpica-unix (20140828-1) unstable; urgency=medium . * Upgrade to latest upstream. * Refresh patches as needed. * Closes: #756838 -- re-enable build on big-endian systems (needed to add a patch to do so) Checksums-Sha1: 3dee9d3f49677c9f90f5f955fe18c807af04d7a5 1332 acpica-unix_20140828-1.dsc ef0618aebbaa0012f711ff5f7a6d32fc39f8d237 3316427 acpica-unix_20140828.orig.tar.gz 636c4097cb3dab8edd78226f4772fea7a261c8a3 29896 acpica-unix_20140828-1.debian.tar.xz 84f7c999feb83ddca6328a13cec367f23c6a34c8 659414 acpica-tools_20140828-1_amd64.deb f2fd57dc010eaefdf031be503bcc23a2ebb5570f 166772 iasl_20140828-1_all.deb 3a0b4e1054661fa84d4fd8ceef5603981ed524f5 166780 acpidump_20140828-1_all.deb Checksums-Sha256: 738cb33c6360f8285431b8083120f15e83cce8530d6d082db8f43276f2528c75 1332 acpica-unix_20140828-1.dsc f2343f4137b40ed9f1233d8a229a9b2503042e189272f25a52462bd81423636b 3316427 acpica-unix_20140828.orig.tar.gz af4d43989659f4be8e9e5cc2c312c88841ed47e8febe697dbf73df4019884042 29896 acpica-unix_20140828-1.debian.tar.xz c715d84e1e49bbd2c8806e0b8941aa2d08c3d54a6c885a1c1d8cfacabd866a83 659414 acpica-tools_20140828-1_amd64.deb 72f342b872da9248da8226ec7a8286a4f3aa0503e8eae559f8190879c091cde7 166772 iasl_20140828-1_all.deb 046364ec8b105c22f6e0613369fd319f0d5e498f22f2cc5c57cecec85ec6 166780 acpidump_20140828-1_all.deb Files:
Bug#754310: netgen: meshing a STEP file makes X crash
On Wed, Jul 9, 2014 at 21:51:33 +0200, Francesco Poli (wintermute) wrote: Package: netgen Version: 4.9.13.dfsg-8+b1 Severity: grave Justification: renders package unusable Hello, I cannot generate a mesh on a geometry described in a STEP file without experiencing X crashes that force me to reboot the machine. X crashes are X bugs, not client bugs. Cheers, Julien signature.asc Description: Digital signature
Bug#759663: marked as done (octave: FTBFS on mips - Please add mips to NO_JDK_ARCHS)
Your message dated Fri, 29 Aug 2014 21:49:36 + with message-id e1xnu36-0005sy...@franck.debian.org and subject line Bug#759663: fixed in octave 3.8.2-2 has caused the Debian Bug report #759663, regarding octave: FTBFS on mips - Please add mips to NO_JDK_ARCHS 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.) -- 759663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: octave Version: 3.6.4-4 Severity: serious Justification: FTBFS on mips (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, As you already know octave has been binNMUed for the ongoing hdf5 transition. Unfortunately it FTBFS on mips [1] with: libinterp/octave-value/ov-java.cc-tst ..panic: Bus error -- stopping myself... [1] https://buildd.debian.org/status/fetch.php?pkg=octavearch=mipsver=3.8.2-1%2Bb1stamp=1409282746 This error was seen before and discussed in January 2014 on the pkg-octave-devel list [2]. [2] http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2014-January/010510.html How about adding mips to the disable-java list? Thanks in advance, _g. - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUAD8MAAoJEO/obGx//s+DtqAIAKtODQTLSHExQbIzQ+/cpRrV ykjYEdG9AMn57NCow/Qtfito1V3i5DB3qd00vWMay4CKo4+UkLsDJDj/Qiffgzhf tgEgNuk2MR/jUFIeZflca2L+5Ic4KwVabODK39BwuBA2C+TRrYkD17xzrglFSF/P tQZuxhSe9QQneB+WdG+Y5BIhIJe1EPX5tv8Bgech8Qz52V9xeFVK8TiSmFr1lts8 PjAip2gXqyBbEur/nb9p5M3U5c0Bv/Jqs5L+GYGGQaPcGckKEpVkXDxmG/l/XX47 cExFVwyxRfcCGFwPOLc0+R6Rv+8lIhpOqCjNHKWOoRJZ097SHYpqfGWEpMLN5/I= =T82V -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: octave Source-Version: 3.8.2-2 We believe that the bug you reported is fixed in the latest version of octave, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot sebast...@debian.org (supplier of updated octave 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: SHA256 Format: 1.8 Date: Fri, 29 Aug 2014 22:39:52 +0200 Source: octave Binary: octave octave-dbg octave-common octave-doc octave-htmldoc octave-info liboctave2 liboctave-dev Architecture: source all Version: 3.8.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: liboctave-dev - Development files for the GNU Octave language liboctave2 - Shared libraries of the GNU Octave language octave - GNU Octave language for numerical computations octave-common - architecture-independent files for octave octave-dbg - Debug symbols for octave octave-doc - PDF documentation on the GNU Octave language octave-htmldoc - HTML documentation on the GNU Octave language octave-info - GNU Info documentation on the GNU Octave language Closes: 759663 Changes: octave (3.8.2-2) unstable; urgency=medium . * Disable java on mips. (Closes: #759663) Checksums-Sha1: 550bb12b3fd3e28d37118b903a59ee505d072275 2952 octave_3.8.2-2.dsc 9e1ce7076aa917c2ca8b33b8088a37b006da585e 58696 octave_3.8.2-2.debian.tar.xz 76afd81e2e396543d62c47b926a6416fc2a90395 1379738 octave-common_3.8.2-2_all.deb d475634587b8dc16e46fe41d068232c4bd7f9d84 3897948 octave-doc_3.8.2-2_all.deb 31a6d75b0d91965d0a21d8f71c885f349759161a 1749360 octave-htmldoc_3.8.2-2_all.deb 6a78ec14f2b7f2d1d8d5697411718e74b53567fe 1070236 octave-info_3.8.2-2_all.deb Checksums-Sha256: a9ec9e999ead729649bceb85c6f1ca2c7d16d6ad1b1d8168cc843f81ceae8369 2952 octave_3.8.2-2.dsc 411e45ab0f6821a23bc6dd5e8c4d631d9e76b2facf03109132112416902ea78f 58696 octave_3.8.2-2.debian.tar.xz 25db527a3707702d6f1dbd311e96b688fa430c9cf56b11425509cadc60bf4a35 1379738 octave-common_3.8.2-2_all.deb
Bug#759663: [pkg-octave/master] Disable java on mips.
On Fri, 29 Aug 2014 20:40:34 + =?utf-8?q?S=C3=A9bastien_Villemot?=
sebast...@debian.org wrote:
tag 759663 pending
thanks
Date: Fri Aug 29 22:38:31 2014 +0200
Author: Sébastien Villemot sebast...@debian.org
Commit ID: 4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Commit URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Patch URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff_plain;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Disable java on mips.
Closes: #759663
Looking at the patch - IIUIC - it misses the change below in debian/control.
Thanks,
_g.
diff -Nru octave-3.8.2/debian/control octave-3.8.2/debian/control
--- octave-3.8.2/debian/control 2014-08-13 20:14:38.0 +
+++ octave-3.8.2/debian/control 2014-08-29 18:20:42.0 +
@@ -24,7 +24,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, texinfo, octave-common (=
${source:Version}),
liboctave2 (= ${binary:Version}),
- default-jre-headless [!armhf !hurd-i386 !kfreebsd-amd64
!kfreebsd-i386 !mipsel !sparc]
+ default-jre-headless [!armhf !hurd-i386 !kfreebsd-amd64
!kfreebsd-i386 !mips !mipsel !sparc]
Recommends: gnuplot-x11 | gnuplot-qt, libopenblas-base | libatlas3-base,
pstoedit
Suggests: octave-info,
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759748: ogmrip: Depends on mencoder which is not available
Source: ogmrip Version: 1.0.1-1 Severity: serious Justification: Policy 2.2.1 Hello, ogmrip depends on mencoder which is not currently available in Debian unstable which makes the package uninstallable. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: Digital signature
Bug#759745: gdm3: Unable to login post-upgrade without systemd-sysv installed
Am 29.08.2014 23:34, schrieb Jeremy T. Bouse: Package: gdm3 Version: 3.12.2-2.1 Severity: grave Justification: renders package unusable Performed routine aptitude upgrade and had new version of gdm installed. Shutdown laptop and upon restart was no longer presented with the login greeter. Gnome environment would work by getting to shell and running startx but was presented with a systemd-login error on the console shell when logging in. Installed systemd-sysv which purged sysinit-core, rebooted and the system was once again usable. Suggest that there is a dependency not properly resolving in there to ensure that systemd is running as PID 1. Might be a bug in systemd-shim. systemd-logind is supposed to work stand-alone (under sysvinit/upstart). Could you poke the systemd-shim maintainers please about this issue. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#759696: 3dldf: FTBFS on non-*amd64: invalid free in arc_1 test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. Unfortunately I cannot reproduce the issue on my box. So I will first try to get access to an i386 box. Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJUAPa+AAoJEIC/w4IMSybjpLsIALH4Gt3rs3nKA8SI5MGeKDES nV/LNQ15I5qWfJn4FgmvRy/Y1HtWw2TI0C+Ab/bMHeOhAsBjowGa6ftf45dde1XD PjVrp9QNQX/h9fZahEfgz2BHk4zuBs1WvEFT/jyPn91UxHwXeidhT8l4pMmkMt1X vEcDcYvqCB/NWGIFjjKs3Zn+m+O5PJEbqkWwITOCyOZuj0OD72NT2ihNR6MFjw0K 9LKISK8VeVvm5+QbDRjrPFEGPe7olF3WGNOXdV2eu9D3ukeSHtOOJA3mny2A7ghb ldks/+2Jve8+jXgqKavdCBsTtQas8NS9Bp5p40lGIZlToMXxhh2+wYBpKRcfTug= =5Nzp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759663: [pkg-octave/master] Disable java on mips.
Le vendredi 29 août 2014 à 23:56 +0200, pini a écrit :
On Fri, 29 Aug 2014 20:40:34 + =?utf-8?q?S=C3=A9bastien_Villemot?=
sebast...@debian.org wrote:
Date: Fri Aug 29 22:38:31 2014 +0200
Author: Sébastien Villemot sebast...@debian.org
Commit ID: 4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Commit URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Patch URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff_plain;h=4f87d1af82a202c3b142fa50fdb756bf65fa7b3b
Disable java on mips.
Closes: #759663
Looking at the patch - IIUIC - it misses the change below in debian/control.
Thanks,
_g.
diff -Nru octave-3.8.2/debian/control octave-3.8.2/debian/control
--- octave-3.8.2/debian/control 2014-08-13 20:14:38.0 +
+++ octave-3.8.2/debian/control 2014-08-29 18:20:42.0 +
@@ -24,7 +24,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, texinfo, octave-common (=
${source:Version}),
liboctave2 (= ${binary:Version}),
- default-jre-headless [!armhf !hurd-i386 !kfreebsd-amd64
!kfreebsd-i386 !mipsel !sparc]
+ default-jre-headless [!armhf !hurd-i386 !kfreebsd-amd64
!kfreebsd-i386 !mips !mipsel !sparc]
Recommends: gnuplot-x11 | gnuplot-qt, libopenblas-base | libatlas3-base,
pstoedit
Suggests: octave-info,
Thanks for noticing. I have committed the fix to our git. I think this
is not a critical issue, since it is just a spurious dependency, without
any other side effect.
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
Processed: tagging 730742, severity of 730742 is serious
Processing commands for cont...@bugs.debian.org: tags 730742 + patch Bug #730742 [libfreetype6] Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1 Added tag(s) patch. severity 730742 serious Bug #730742 [libfreetype6] Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 730742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730742 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#752582: qemubuilder hangs after extracting the packages
Control: severity -1 important Hi, On Tue, Jun 24, 2014 at 10:51:43PM +0100, Alberto Bertogli wrote: I'm trying to use qemubootstrap in Debian testing, but it hangs after extracting the packages and doing some filesystem work, apparently before running qemu/kvm. I'm using simple command lines, and reproduced this in two different systems with different kernels (one using Debian's kernel, the other hand-built), where I've verified that kvm works just fine. Because of that, I've put this as grave severity, but please let me know if it's not appropriate. I tried to reproduce this bug, and it seems that qemubuilder doesn't handle the fact that the kernel image and the initrd are not set. This is caused by code in qemubuilder.c on line 316: http://sources.debian.net/src/cowdancer/0.73/qemubuilder.c/#L316 When these options are not set, the values are NULL, and the child that's supposed to start qemu segfaults when adding all the command line arguments. As this only happens when the configuration is wrong, this doesn't make the package completely unusable, so I downgraded this bug. This is still a bug that should be fixed, however. The user should get a clear message that some settings are missing. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: qemubuilder hangs after extracting the packages
Processing control commands: severity -1 important Bug #752582 [qemubuilder] qemubuilder hangs after extracting the packages Severity set to 'important' from 'grave' -- 752582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752582 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#759757: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main
Package: pavucontrol Version: 2.0-2 Severity: grave $ pavucontrol pavucontrol: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759757: downgrade helps
OK this works: Downgrade the following packages: 1) libpulse-mainloop-glib0 [5.0-10 (experimental, now) - 5.0-6 (unstable)] 2) libpulse0 [5.0-10 (now) - 5.0-6 (unstable)] 3) libpulsedsp [5.0-10 (experimental, now) - 5.0-6 (unstable)] 4) pulseaudio [5.0-10 (experimental, now) - 5.0-6 (unstable)] 5) pulseaudio-utils [5.0-10 (experimental, now) - 5.0-6 (unstable)] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759757: marked as done (symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main)
Your message dated Fri, 29 Aug 2014 21:23:32 -0400 with message-id caafdzj96gtusf9vbidf8tg55rfqah9p4+9_trgihdfy9pf6...@mail.gmail.com and subject line Re: Bug#759757: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main has caused the Debian Bug report #759757, regarding symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main 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.) -- 759757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pavucontrol Version: 2.0-2 Severity: grave $ pavucontrol pavucontrol: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main ---End Message--- ---BeginMessage--- On Fri, Aug 29, 2014 at 9:02 PM, 積丹尼 Dan Jacobson jida...@jidanni.org wrote: Package: pavucontrol Version: 2.0-2 Severity: grave $ pavucontrol pavucontrol: symbol lookup error: /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-5.0.so: undefined symbol: main Please be a little bit more verbose. Reportbug exists for a reason, as it provides information that we need. In this case, the information that we need is the version of libpulse0. I'm willing to bet it is 5.0-10, because this should be bug #758531 or #758556, which I already fixed. Please downgrade libpulse0 to the version in unstable until the new one is fixed in unstable (the i386 build failed). I'm closing the bug because it is already reported and not a bug in pavucontrol -- Saludos, Felipe Sateler---End Message---
Bug#759765: gcj-4.9-jdk: Invalid symlinks prevent building against the jdk
Package: gcj-4.9-jdk Version: 4.9.1-9 Severity: serious Packages which use the JNI will FTBFS due to invalid symlinks in gcj-4.9-jdk: $ dpkg-deb -c gcj-4.9-jdk_4.9.1-9_amd64.deb | grep /build lrwxrwxrwx root/root 0 2014-08-24 22:16 ./usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/include/jawt.h - /build/x86_64-linux-gnu/libjava/include/jawt.h lrwxrwxrwx root/root 0 2014-08-24 22:16 ./usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/include/jni.h - /build/x86_64-linux-gnu/libjava/include/jni.h lrwxrwxrwx root/root 0 2014-08-24 22:16 ./usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/include/linux/jawt_md.h - /build/x86_64-linux-gnu/libjava/include/jawt_md.h lrwxrwxrwx root/root 0 2014-08-24 22:16 ./usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/include/linux/jni_md.h - /build/x86_64-linux-gnu/libjava/include/jni_md.h -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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#759765: gcj-4.9-jdk: Invalid symlinks prevent building against the jdk
Am 30.08.2014 um 04:14 schrieb James McCoy: Package: gcj-4.9-jdk Version: 4.9.1-9 Severity: serious Packages which use the JNI will FTBFS due to invalid symlinks in gcj-4.9-jdk Is there anything which prevents you to check the BTS for existing bug reports before filing duplicates? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 759558 759765
Processing commands for cont...@bugs.debian.org:
forcemerge 759558 759765
Bug #759558 [gcj-4.9-jdk] gcj-4.9-jdk: broken symlinks for j{awt,ni}{,_md}.h
Bug #759765 [gcj-4.9-jdk] gcj-4.9-jdk: Invalid symlinks prevent building
against the jdk
Merged 759558 759765
thanks
Stopping processing here.
Please contact me if you need assistance.
--
759558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759558
759765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759765
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
Processed: reassign 746493 to glugen2
Processing commands for cont...@bugs.debian.org: # the com.jogamp.common.os.Platform class is in gluegen2 reassign 746493 glugen2 Bug #746493 [libjogl2-java] Wrong guess on the endianness of powerpc Bug reassigned from package 'libjogl2-java' to 'glugen2'. Warning: Unknown package 'glugen2' Warning: Unknown package 'glugen2' Ignoring request to alter found versions of bug #746493 to the same values previously set Warning: Unknown package 'glugen2' Warning: Unknown package 'glugen2' Ignoring request to alter fixed versions of bug #746493 to the same values previously set Warning: Unknown package 'glugen2' thanks Stopping processing here. Please contact me if you need assistance. -- 746493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746493 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#759765: gcj-4.9-jdk: Invalid symlinks prevent building against the jdk
On Sat, Aug 30, 2014 at 04:20:12AM +0200, Matthias Klose wrote: Am 30.08.2014 um 04:14 schrieb James McCoy: Package: gcj-4.9-jdk Version: 4.9.1-9 Severity: serious Packages which use the JNI will FTBFS due to invalid symlinks in gcj-4.9-jdk Is there anything which prevents you to check the BTS for existing bug reports before filing duplicates? Is there anything which prevents you from performing sanity checks on packages you upload? People make mistakes. It hadn't been reassigned when I looked yesterday and reportbug's bug listing is broken. -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 746493 to gluegen2
Processing commands for cont...@bugs.debian.org: # the com.jogamp.common.os.Platform class is in gluegen2 reassign 746493 gluegen2 Bug #746493 [glugen2] Wrong guess on the endianness of powerpc Warning: Unknown package 'glugen2' Bug reassigned from package 'glugen2' to 'gluegen2'. Ignoring request to alter found versions of bug #746493 to the same values previously set Ignoring request to alter fixed versions of bug #746493 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 746493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746493 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
Processed: bug 746493 is forwarded to https://jogamp.org/bugzilla/show_bug.cgi?id=1056
Processing commands for cont...@bugs.debian.org: forwarded 746493 https://jogamp.org/bugzilla/show_bug.cgi?id=1056 Bug #746493 [gluegen2] Wrong guess on the endianness of powerpc Set Bug forwarded-to-address to 'https://jogamp.org/bugzilla/show_bug.cgi?id=1056'. thanks Stopping processing here. Please contact me if you need assistance. -- 746493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746493 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#759766: libnkf-perl: cannot load module on i386 arch
Package: libnkf-perl Version: 2.13-3+b1 Severity: grave Dear Maintainer, NKF module for perl doesn't work on i386 arch: % perl -e 'use NKF' Can't use an undefined value as a subroutine reference at /usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210. END failed--call queue aborted at /usr/lib/i386-linux-gnu/perl5/5.20/NKF.pm line 210. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. It works on amd64 arch. Regards, Nobuhiro Versions of packages libnkf-perl depends on: ii libc6 2.19-10 ii perl5.20.0-4 ii perl-base [perlapi-5.20.0] 5.20.0-4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751277: python-biopython: FTBFS on mips* powerpc s390x
Dear all, With Dave kindly offering access to a PowerPC, I was able to fix this bug. I have uploaded a fixed version of Bio/Cluster/clustermodule.c to the Biopython github repository; see https://github.com/biopython/biopython/blob/master/Bio/Cluster/clustermodule.c Can you try this version? This should solve the test failures. Best, -Michiel. On Mon, 8/18/14, Andreas Tille andr...@an3as.eu wrote: Subject: Re: Bug#751277: python-biopython: FTBFS on mips* powerpc s390x To: Michiel de Hoon mjldeh...@yahoo.com, debian-powe...@lists.debian.org, debian-m...@lists.debian.org, debian-s...@lists.debian.org Cc: Peter Cock p.j.a.c...@googlemail.com, Dejan Latinovic dejan.latino...@imgtec.com, Biopython discussion list biopyt...@lists.open-bio.org, 751...@bugs.debian.org 751...@bugs.debian.org, biopython-...@biopython.org biopython-...@biopython.org Date: Monday, August 18, 2014, 5:01 PM Hi porters, could you please be so kind to check this issue? It would be great to find out why the test suite of biopython fails on these architectures. Thanks a lot Andreas. On Mon, Aug 18, 2014 at 12:35:53AM -0700, Michiel de Hoon wrote: Hi Andreas, Without access to powerpc, I have no way to test the code. Can you try recompiling Biopython and checking what exactly happens inside the distance_converter function in Bio/Cluster/clustermodule.c ? For example, I am really wondering what strlen(data) inside this function returns on powerpc. Best, -Michiel. On Sat, 8/16/14, Andreas Tille andr...@an3as.eu wrote: Subject: Re: Bug#751277: python-biopython: FTBFS on mips* powerpc s390x To: Peter Cock p.j.a.c...@googlemail.com Cc: Dejan Latinovic dejan.latino...@imgtec.com, Michiel de Hoon mjldeh...@yahoo.com, Biopython discussion list biopyt...@lists.open-bio.org, 751...@bugs.debian.org 751...@bugs.debian.org, biopython-...@biopython.org biopython-...@biopython.org Date: Saturday, August 16, 2014, 5:37 AM Hi Peter, On Thu, Aug 14, 2014 at 09:52:40AM +0100, Peter Cock wrote: 1. waiting for your confirmation / patch 2. deactivating the specific test 3. exclude mips for biopython 4. ? any better idea ? In the current state all the work we spent in biopython over the last monthes will not migrate to testing for the simple reason that the current package in testing just does not run the test suite at build time and moreover python3 is not supported. Kind regards Andreas. I would suggest (2), deactivate this test (at least for for mips) as the most practical short term solution for the Debian packages. Or if you prefer (3), don't target mips for the Biopython package (yet). Medium term, I hope we can fix the C code to handle either Endian platform - option (1). It seems after having fixed the issue caused by wise we have one remaining problem: On powerpc[1] and s390x[2] test_Cluster fails even with Python 2.7 with: == ERROR: test_clusterdistance (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 212, in test_clusterdistance method='a', transpose=0) ValueError: method should be a single character == ERROR: test_kcluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 141, in test_kcluster method='a', dist='e') ValueError: method should be a single character == ERROR: test_somcluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 557, in test_somcluster inittau=0.02, niter=100, dist='e') ValueError: distance should be a single character == ERROR: test_treecluster (test_Cluster.TestCluster) -- Traceback (most recent call last): File
Bug#759129: marked as done (nanomsg ftbfs in current unstable (i386, and other architectures))
Your message dated Sat, 30 Aug 2014 04:00:07 + with message-id e1xnzpf-0006st...@franck.debian.org and subject line Bug#759129: fixed in nanomsg 0.4~beta+dfsg-3 has caused the Debian Bug report #759129, regarding nanomsg ftbfs in current unstable (i386, and other architectures) 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.) -- 759129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:nanomsg Version: 0.4~beta+dfsg-1 Severity: serious Tags: sid jessie reproduced with current unstable on i386: [...] PASS: tests/iovec ./test-driver: line 107: 14170 Aborted $@ $log_file 21 FAIL: tests/msg PASS: tests/inproc_shutdown [...] make[4]: Entering directory '/scratch/packages/tmp/nanomsg-0.4~beta+dfsg' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/scratch/packages/tmp/nanomsg-0.4~beta+dfsg' Testsuite summary for nanomsg Unknown # TOTAL: 28 # PASS: 27 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to nano...@freelists.org Makefile:2955: recipe for target 'test-suite.log' failed make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory '/scratch/packages/tmp/nanomsg-0.4~beta+dfsg' Makefile:3061: recipe for target 'check-TESTS' failed make[2]: *** [check-TESTS] Error 2 ---End Message--- ---BeginMessage--- Source: nanomsg Source-Version: 0.4~beta+dfsg-3 We believe that the bug you reported is fixed in the latest version of nanomsg, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Harlan Lieberman-Berg h.liebermanb...@gmail.com (supplier of updated nanomsg 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: SHA256 Format: 1.8 Date: Tue, 26 Aug 2014 14:15:20 -0700 Source: nanomsg Binary: libnanomsg-dev libnanomsg0 libnanomsg0-dbg Architecture: source amd64 Version: 0.4~beta+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Harlan Lieberman-Berg h.liebermanb...@gmail.com Changed-By: Harlan Lieberman-Berg h.liebermanb...@gmail.com Description: libnanomsg-dev - nanomsg development files libnanomsg0 - high-performance implementation of scalability libraries libnanomsg0-dbg - high-performance implementation of scalability libraries - debug Closes: 759129 Changes: nanomsg (0.4~beta+dfsg-3) unstable; urgency=medium . * Add the debug package. . nanomsg (0.4~beta+dfsg-2) unstable; urgency=medium . * Disable test due to transient failure (Closes: #759129) Checksums-Sha1: 175ed28c1949edf7a024212a6b0a44eaf01720f0 2016 nanomsg_0.4~beta+dfsg-3.dsc 9e4943455a52431c58ba7a4815bfa7217ab0a3dd 4980 nanomsg_0.4~beta+dfsg-3.debian.tar.xz 0fa93d35330d4e0ec5642d80c9f99cfb77c6aff1 113560 libnanomsg-dev_0.4~beta+dfsg-3_amd64.deb 2e56ecd7a852a643e78fb288be6d17242b98c1fb 77088 libnanomsg0_0.4~beta+dfsg-3_amd64.deb 8c2289940740c80aa0fa9431f8d559b76053f643 259216 libnanomsg0-dbg_0.4~beta+dfsg-3_amd64.deb Checksums-Sha256: 44b553cbe506b6dd90d395c45e9d36522e68b445d17e7ecccd5e0ce43f610f0e 2016 nanomsg_0.4~beta+dfsg-3.dsc efdbb2de26f820af8a564baa4c1990c156a2d23a8e81361176a222dd0143824a 4980 nanomsg_0.4~beta+dfsg-3.debian.tar.xz 2defd2f5318a43d93c2a27806e4e78df72bf4e216b2336466f39e0b5051eb5e5 113560 libnanomsg-dev_0.4~beta+dfsg-3_amd64.deb b2c576e5cf8a4c9dee305848c01de236316f64891fbbc242b476812b9211a1c9 77088 libnanomsg0_0.4~beta+dfsg-3_amd64.deb a4f522a6c3f3ab7e5bc2f90b903b9499d1c1ad295ab455d0ff231202af07a492 259216 libnanomsg0-dbg_0.4~beta+dfsg-3_amd64.deb Files: 934a5a1526c0d4916fd6f562a69c2290 113560 libdevel extra libnanomsg-dev_0.4~beta+dfsg-3_amd64.deb 416bb9f8b6c76feb647e05db42641b24 77088 libs extra libnanomsg0_0.4~beta+dfsg-3_amd64.deb ec36efdec5152e4bdcd54a77413b8281 259216 debug extra
Bug#759766: libnkf-perl: cannot load module on i386 arch
tag 759766 patch
thanks
On Sat, Aug 30, 2014 at 12:20:02PM +0900, Nobuhiro Ban wrote:
Package: libnkf-perl
Version: 2.13-3+b1
Severity: grave
Dear Maintainer,
NKF module for perl doesn't work on i386 arch:
% perl -e 'use NKF'
Can't use an undefined value as a subroutine reference at
/usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.
END failed--call queue aborted at /usr/lib/i386-linux-gnu/perl5/5.20/NKF.pm
line 210.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
It works on amd64 arch.
This is a binary compatibility issue caused by not compiling the module
with flags from $Config{ccflags}, particularly -D_FILE_OFFSET_BITS=64.
I'm attaching a patchset that improves the dpkg-buildflags handling
and doesn't override $Config{ccflags}.
--
Niko Tyni nt...@debian.org
From 2e8b8850c8a3eb5bab045eddb30f5d255193a6dd Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Fri, 29 Aug 2014 21:52:50 -0700
Subject: [PATCH 1/4] Remove redundant use of buildflags.mk
buildflags.mk and dpkg-buildflags are alternative approaches.
It is useless for the first one to export CFLAGS and LDFLAGS, when
the latter overrides them.
---
debian/rules | 3 ---
1 file changed, 3 deletions(-)
diff --git a/debian/rules b/debian/rules
index 0590fb7..9e7b52d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,9 +7,6 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
-DPKG_EXPORT_BUILDFLAGS = 1
-include /usr/share/dpkg/buildflags.mk
-
CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
CFLAGS+=$(HARDENING_CFLAGS)
--
2.1.0
From 74b2ba0d22a3cf302e5ac79b1931f131db7f28e7 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Fri, 29 Aug 2014 22:02:38 -0700
Subject: [PATCH 2/4] Use CPPFLAGS from dpkg-buildflags in the build
These currently include -D_FORTIFY_SOURCE=2
---
debian/rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/rules b/debian/rules
index 9e7b52d..63ab1f9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,7 @@
# This has to be exported to make some magic below work.
export DH_OPTIONS
-CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
+CFLAGS=$(shell dpkg-buildflags --get CFLAGS) $(shell dpkg-buildflags --get CPPFLAGS)
LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
CFLAGS+=$(HARDENING_CFLAGS)
LDFLAGS+=$(HARDENING_LDFLAGS)
--
2.1.0
From 129955540dee54a970209152beb191e4f30c2f31 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Fri, 29 Aug 2014 22:04:51 -0700
Subject: [PATCH 3/4] Pass build flags to the NKF Perl module in OPTIMIZE and
LD
This mirrors what debhelper currently does at compatibility level 9,
and doesn't override $Config{ccflags} from Perl, fixing binary
compatibility issues on 32-bit architectures.
Bug-Debian: https://bugs.debian.org/759766
---
debian/rules | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/debian/rules b/debian/rules
index 63ab1f9..a482f3c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -40,11 +40,11 @@ override_dh_auto_clean:
override_dh_auto_configure:
(cd NKF.mod \
- /usr/bin/perl Makefile.PL INSTALLDIRS=vendor)
+ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE=$(CFLAGS) LD=cc $(LDFLAGS))
override_dh_auto_build:
make nkf CC=cc CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)
- (cd NKF.mod make CCFLAGS=$(CFLAGS) LDDFLAGS=$(LDFLAGS))
+ (cd NKF.mod make)
override_dh_auto_install:
install -s -m 755 nkf debian/nkf/usr/bin
--
2.1.0
From 09435ea0c61b08837e16628a470f402906d72794 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Fri, 29 Aug 2014 22:18:04 -0700
Subject: [PATCH 4/4] Run the NKF.mod test suite too
This would have caught the binary compatibility issues
in #759766.
---
debian/rules | 4
1 file changed, 4 insertions(+)
diff --git a/debian/rules b/debian/rules
index a482f3c..b0b6b55 100755
--- a/debian/rules
+++ b/debian/rules
@@ -46,6 +46,10 @@ override_dh_auto_build:
make nkf CC=cc CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)
(cd NKF.mod make)
+override_dh_auto_test:
+ make test
+ make -C NKF.mod test
+
override_dh_auto_install:
install -s -m 755 nkf debian/nkf/usr/bin
./debian/nkf/usr/bin/nkf -e nkf.1j debian/nkf.1j.tmp
--
2.1.0
Processed: Re: Bug#759766: libnkf-perl: cannot load module on i386 arch
Processing commands for cont...@bugs.debian.org: tag 759766 patch Bug #759766 [libnkf-perl] libnkf-perl: cannot load module on i386 arch Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 759766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759766 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
