Bug#759096: guile-snarf: hardcodes compiler at build-time instead of using cc or gcc
Source: guile-2.0-dev Version: 2.0.11+1-1 Severity: grave Justification: makes the package in question unusable Hello, On ix86 Debian has recently switched from i486 to i586 (dpkg 1.17.11), therefore i486-linux-gnu-gcc is not available in current default gcc. However since guile-snarf hardcodes the compiler available at build-time it currently fails unless CPP is set, breaking e.g. gnutls28: /usr/bin/guile-snarf -o core.x core.c -DHAVE_CONFIG_H -I../../lib/includes -I.. /../lib/includes -I../../extra/includes -I../.. -I. -D_FORTIFY_SOURCE=2 -g -O2 - fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-strict-proto types -I../../gl -I../../gl -pthread -I/usr/include/guile/2.0 /usr/bin/guile-snarf: 54: /usr/bin/guile-snarf: i486-linux-gnu-gcc: not found Makefile:1709: recipe for target 'core.x' failed make[5]: *** [core.x] Error 1 make[5]: Leaving directory '/tmp/GNUTLS/gnutls-3.3.6/guile/src' 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' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756780: Status bowtie + tophat (Was: [Help] Need help for architecture specific code)
Le Sat, Aug 23, 2014 at 07:30:21PM +0200, Andreas Tille a écrit : What can we do to get tophat and bowtie into testing? tophat: 1. tophat only Recommends: bowtie2 | bowtie or 2. tophat Architecture: amd64 kfreebsd-amd64 I think 1. is the better option Hi Andreas, In my understanding, it is not possible to run TopHat without Bowtie (version 1 or 2). Therefore, the “Depends” relationship is the most appropriate. Regarding the migration to Testing, it looks like both bowtie2 and bowtie must be installable to satisfy “bowtie2 | bowtie”, so we need to adapt ourselves to this constraint. Here are two possible solutions to the problem : 1. bowtie2 and bowtie provide a virtual “bowtie-aligner”, and tophat depends on “bowtie2 | bowtie-aligner”. 2. tophat depends on bowtie2 only. Given that bowtie and bowtie2 can be co-installed, and given that most users will want to use Bowtie 2 with TopHat, how about solution 2 ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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
Hi Michiel, thanks for testing this. Just to let you know: I personally need to admit that I do not feel capable to verify your test for the next couple of weeks. Just from my gut feling I'd say: If you find a workaround here that's probably helpful to run the test suite successfully. Thanks again Andreas. On Sat, Aug 23, 2014 at 06:47:00PM -0700, Michiel de Hoon wrote: Hi Andreas, I was able to replicate this bug on a PowerPC with Python 2.7, but only if I replace the single character into a single unicode character (e.g. in line 212 of test_Cluster.py, if I replace method='a' by method=u'a'). Can you confirm that you get this bug with Python 2.7 even with simple strings rather than unicode? Thanks, -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 /«BUILDDIR»/python-biopython-1.64+dfsg/.pybuild/pythonX.Y_3.4/build/Tests/test_Cluster.py, line 290, in test_treecluster transpose=0, method='a', dist='e') ValueError: method should be a single character -- Ran 210 tests in 293.712 seconds FAILED (failures = 1) On sparc[3] there is a problem with dialign but sparc is no release architecture and wie might ignore this. It might be a helpful hint anyway. Any hint for the test_Cluster problem? If not I would also consider to hide it cowardly under the carpet for the moment. The new package is so much better tested than the one in the testing distribution which does not even dare about any unit tests and only for this reason reached the testing distribution. What do you think? Kind regards Andreas. scrool these links to the end to see the problem: [1]
Processed: reassign 759096 to guile-2.0-dev
Processing commands for cont...@bugs.debian.org: # Package, not Source reassign 759096 guile-2.0-dev 2.0.11+1-1 Bug #759096 [src:guile-2.0-dev] guile-snarf: hardcodes compiler at build-time instead of using cc or gcc Warning: Unknown package 'src:guile-2.0-dev' Bug reassigned from package 'src:guile-2.0-dev' to 'guile-2.0-dev'. No longer marked as found in versions guile-2.0-dev/2.0.11+1-1. Ignoring request to alter fixed versions of bug #759096 to the same values previously set Bug #759096 [guile-2.0-dev] guile-snarf: hardcodes compiler at build-time instead of using cc or gcc Marked as found in versions guile-2.0/2.0.11+1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 759096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759096 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 759096 to guile-2.0-dev
Processing commands for cont...@bugs.debian.org: # Package, not Source reassign 759096 guile-2.0-dev 2.0.11+1-1 Bug #759096 [guile-2.0-dev] guile-snarf: hardcodes compiler at build-time instead of using cc or gcc Ignoring request to reassign bug #759096 to the same package Bug #759096 [guile-2.0-dev] guile-snarf: hardcodes compiler at build-time instead of using cc or gcc Ignoring request to alter found versions of bug #759096 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 759096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759096 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#758688: [Pkg-libvirt-maintainers] Bug#758688: Bug#758688: Bug#758688: libvirt-daemon-system (1.2.7-9) dist-upgrade failed
On Sun, Aug 24, 2014 at 12:21:29AM +0700, Neutron Soutmun wrote: On Sat, Aug 23, 2014 at 10:56 PM, Guido Günther a...@sigxcpu.org wrote: On Sat, Aug 23, 2014 at 10:22:46PM +0700, Neutron Soutmun wrote: To reproduce this, make the virtlockd.service inactive (it's already inactive on my laptop on upgrade, not by this command) # systemctl stop virtlockd.service Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket That's exactly what I did (see my other reply) and with systemctl stop virtlockd.service systemctl reload virtlockd.service ; echo $? it returns 0 with systemd 204. Can you confirm it behaves differently with another version? If so we should report this to the systemd maintainers since it's a important behviour change. # systemctl stop virtlockd.service systemctl reload virtlockd.service ; echo $? Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. 1 It returns 1 with systemd 208-8 Thanks for verifying. I've filed for that 759098. Nevertheless a libvirt that works around this is on it's way into the archive too. Thanks for reporting back! Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758994: marked as done (Can't install package because Unit virtlockd.service cannot be reloaded because it is inactive)
Your message dated Sun, 24 Aug 2014 09:38:55 + with message-id e1xlugf-0007yj...@franck.debian.org and subject line Bug#758688: fixed in libvirt 1.2.7-11 has caused the Debian Bug report #758688, regarding Can't install package because Unit virtlockd.service cannot be reloaded because it is inactive 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.) -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvirt-daemon-system Version: 1.2.7-10+b1 Severity: important Today I updated my Jessie machine and got this error: giuseppe@blatta:~$ sudo env LANG=C apt-get -f install [...] Setting up libvirt-daemon-system (1.2.7-10+b1) ... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-10+b1); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin E: Sub-process /usr/bin/dpkg returned an error code (1) As you may see, package cannot be configured and stopped the machine upgrade. More information, as suggested by the error message, are: giuseppe@blatta:~$ env LANG=C systemctl status virtlockd.service virtlockd.service - Virtual machine lock manager Loaded: loaded (/lib/systemd/system/virtlockd.service; static) Active: inactive (dead) Docs: man:virtlockd(8) http://libvirt.org Aug 23 17:32:14 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:32:42 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:32:48 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:35:03 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. giuseppe@blatta:~$ env LANG=C journalctl -xn -- Logs begin at Sat 2014-08-23 17:00:42 CEST, end at Sat 2014-08-23 17:35:11 CEST. -- Aug 23 17:33:42 blatta pcscd[12247]: 0008 readerfactory.c:1046:RFInitializeReader() Open Port 0x20 Failed (usb:0a5c/5802:libudev:0:/dev/bus/usb/ Aug 23 17:33:42 blatta pcscd[12247]: 0003 readerfactory.c:338:RFAddReader() Broadcom Corp 5880 [Broadcom USH w/touch sensor] (0123456789ABCD) init f Aug 23 17:35:01 blatta CRON[12354]: pam_unix(cron:session): session opened for user root by (uid=0) Aug 23 17:35:01 blatta /USR/SBIN/CRON[12355]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) Aug 23 17:35:01 blatta CRON[12354]: pam_unix(cron:session): session closed for user root Aug 23 17:35:02 blatta sudo[12357]: giuseppe : TTY=pts/0 ; PWD=/home/giuseppe ; USER=root ; COMMAND=/usr/bin/env LANG=C apt-get -f install Aug 23 17:35:02 blatta sudo[12357]: pam_unix(sudo:session): session opened for user root by giuseppe(uid=0) Aug 23 17:35:03 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:35:03 blatta sudo[12357]: pam_unix(sudo:session): session closed for user root Aug 23 17:35:11 blatta pcscd[12247]: 88578856 commands.c:1068:CmdPowerOff Card absent or mute Bye, Giuseppe ---End Message--- ---BeginMessage--- Source: libvirt Source-Version: 1.2.7-11 We believe that the bug you reported is fixed in the latest version of libvirt, 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. Guido Günther a...@sigxcpu.org (supplier of updated libvirt 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: Sun, 24 Aug 2014 10:54:26 +0200 Source: libvirt Binary: libvirt-bin libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0 libvirt0-dbg libvirt-doc libvirt-dev libvirt-sanlock Architecture: source amd64 all
Bug#758688: marked as done (libvirt-daemon-system (1.2.7-9) dist-upgrade failed)
Your message dated Sun, 24 Aug 2014 09:38:55 + with message-id e1xlugf-0007yj...@franck.debian.org and subject line Bug#758688: fixed in libvirt 1.2.7-11 has caused the Debian Bug report #758688, regarding libvirt-daemon-system (1.2.7-9) dist-upgrade failed 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.) -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvirt-daemon-system Version: 1.2.7-9 Severity: grave Dear Maintainer, aptitude dist-upgrade failed at libvirt-daemon-system 1.2.7-9. # aptitude dist-upgrade [cut] Setting up libvirt0 (1.2.7-9) ... Setting up libvirt-clients (1.2.7-9) ... Setting up libvirt-daemon (1.2.7-9) ... Setting up libvirt-daemon-system (1.2.7-9) ... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-9); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Setting up openntpd (20080406p-9) ... Setting up ruby-ffi (1.9.3debian-2) ... Setting up udisks2 (2.1.3-3) ... Processing triggers for libc-bin (2.19-9) ... Errors were encountered while processing: libvirt-daemon-system libvirt-bin localepurge: Disk space freed in /usr/share/locale: 8660 KiB localepurge: Disk space freed in /usr/share/man: 1196 KiB localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed in /usr/share/omf: 0 KiB localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB Total disk space freed by localepurge: 9856 KiB E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up libvirt-daemon-system (1.2.7-9) ... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-9); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin Current status: 6 updates [-35]. # # systemctl status virtlockd.service -l virtlockd.service - Virtual machine lock manager Loaded: loaded (/lib/systemd/system/virtlockd.service; static) Active: inactive (dead) Docs: man:virtlockd(8) http://libvirt.org Aug 20 12:48:10 lilith systemd[1]: Stopped Virtual machine lock manager. Aug 20 12:48:18 lilith systemd[1]: Stopped Virtual machine lock manager. Aug 20 12:48:27 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 12:48:30 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 12:49:22 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 12:49:25 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:06:44 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:06:47 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:12:54 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:12:57 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. # # journalctl -xn -- Logs begin at Wed 2014-08-20 09:26:12 JST, end at Wed 2014-08-20 13:15:43 JST. -- Aug 20 13:10:01 lilith CRON[8386]: pam_unix(cron:session): session opened for user root by (uid=0) Aug 20 13:10:01 lilith CRON[8385]: pam_unix(cron:session): session closed for user root Aug 20 13:10:09 lilith CRON[8386]: pam_unix(cron:session): session closed for user root Aug 20 13:12:54 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:12:57 lilith systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 20 13:15:01
Bug#758759: marked as done (postinst fails if virtlockd.service is masked)
Your message dated Sun, 24 Aug 2014 09:38:55 + with message-id e1xlugf-0007yj...@franck.debian.org and subject line Bug#758688: fixed in libvirt 1.2.7-11 has caused the Debian Bug report #758688, regarding postinst fails if virtlockd.service is masked 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.) -- 758688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvirt-daemon-system Version: 1.2.7-9 Severity: important After the first failure: root@bongo:/home/md# dpkg --configure --pending Configurazione di libvirt-daemon-system (1.2.7-9)... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: errore nell'elaborare il pacchetto libvirt-daemon-system (--configure): il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: libvirt-daemon-system [Exit 1] md@bongo:~$ systemctl status virtlockd.service -l virtlockd.service - Virtual machine lock manager Loaded: loaded (/lib/systemd/system/virtlockd.service; static) Active: inactive (dead) Docs: man:virtlockd(8) http://libvirt.org Aug 21 01:54:10 bongo.bofh.it systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. [Exit 3] root@bongo:/home/md# ls -l /etc/systemd/system/virtlockd.socket lrwxrwxrwx 1 root root 9 Feb 12 2014 /etc/systemd/system/virtlockd.socket - /dev/null root@bongo:/home/md# -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libvirt-daemon-system depends on: ii adduser 3.113+nmu3 ii gettext-base 0.19.2-1 ii init-system-helpers 1.20 ii libapparmor1 2.8.0-5.1 ii libaudit11:2.3.7-1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libblkid12.25-3 ii libc62.19-9 ii libcap-ng0 0.7.3-1.1 ii libdbus-1-3 1.8.6-2 ii libdevmapper1.02.1 2:1.02.88-1 ii libgnutls-deb0-283.2.16-1 ii libnl-3-200 3.2.24-2 ii libnl-route-3-2003.2.24-2 ii libnuma1 2.0.9~rc5-1 ii librados20.80.1-1+b1 ii librbd1 0.80.1-1+b1 ii libsasl2-2 2.1.26.dfsg1-11 ii libselinux1 2.3-1 ii libssh2-11.4.3-3 ii libsystemd-daemon0 208-7 ii libvirt-clients 1.2.7-9 ii libvirt-daemon 1.2.7-9 ii libvirt0 1.2.7-9 ii libxml2 2.9.1+dfsg1-4 ii libyajl2 2.0.4-2 ii logrotate3.8.7-1 Versions of packages libvirt-daemon-system recommends: ii bridge-utils 1.5-9 ii dmidecode 2.12-3 ii dnsmasq-base 2.71-1 pn ebtables none ii iproute2 3.16.0-1 ii iptables 1.4.21-2 ii parted3.2-2 ii pm-utils 1.4.1-15 Versions of packages libvirt-daemon-system suggests: pn apparmor none pn auditd none ii policykit-1 0.105-6.1 pn radvdnone ii systemd 208-7 pn systemtapnone -- Configuration Files: /etc/default/libvirtd changed [not included] /etc/libvirt/qemu.conf [Errno 13] Permesso negato: u'/etc/libvirt/qemu.conf' -- no debconf information -- ciao, Marco signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libvirt Source-Version: 1.2.7-11 We believe that the bug you reported is fixed in the latest version of libvirt, 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. Guido Günther a...@sigxcpu.org (supplier of updated libvirt 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: Sun, 24 Aug 2014 10:54:26 +0200 Source: libvirt Binary: libvirt-bin libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0 libvirt0-dbg libvirt-doc libvirt-dev
Bug#743596: gimp still built with lcms1
On Sat, Aug 23, 2014 at 05:33:48PM -0400, Ari Pollak wrote: Is this something that can be taken care of with a binNMU after liblcms1 is removed? That's chicken and egg; FTP masters won't remove lcms until the reverse deps have been cleared. I'm not sure there's much I can do at this point beyond patching upstream. A Build-Conflicts might help? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759100: openjade FTBFS now
Package: openjade Version: 1.4devel1-21 Severity: serious Hi, while bootstrapping on ppc64el I found that openjade FTBFS now. I retried on the amd64 porterbox, and the result is as follows. Andi g++ -g --pipe -fpermissive -O2 -o .libs/openjade jade.o SgmlFOTBuilder.o RtfFOTBuilder.o HtmlFOTBuilder.o TeXFOTBuilder.o TransformFOTBuilder.o MifFOTBuilder.o MessageModule.o ../style/.libs/libostyle.so ../spgrove/.libs/libospgrove.so ../grove/.libs/libogrove.so -losp -lpthread creating openjade make[4]: Leaving directory '/home/aba/openjade-1.4devel1/jade' make[3]: Leaving directory '/home/aba/openjade-1.4devel1/jade' Making all in intl make[3]: Entering directory '/home/aba/openjade-1.4devel1/intl' Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. make[3]: Leaving directory '/home/aba/openjade-1.4devel1/intl' Makefile:308: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/aba/openjade-1.4devel1' Makefile:212: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/aba/openjade-1.4devel1' debian/rules:116: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 -- 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 759107 is serious
Processing commands for cont...@bugs.debian.org: severity 759107 serious Bug #759107 [libudf-dev] Unknown Multi-Arch type 'no' for package 'libudf-dev' Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 759107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759107 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 759107 to src:libcdio, severity of 759105 is serious, merging 759105 759107
Processing commands for cont...@bugs.debian.org: reassign 759107 src:libcdio Bug #759107 [libudf-dev] Unknown Multi-Arch type 'no' for package 'libudf-dev' Bug reassigned from package 'libudf-dev' to 'src:libcdio'. No longer marked as found in versions libcdio/0.92-1. Ignoring request to alter fixed versions of bug #759107 to the same values previously set severity 759105 serious Bug #759105 [src:libcdio] libcdio: Breaks apt-get update - Unknown Multi-Arch type 'no' for package 'libcdio-dev' Severity set to 'serious' from 'normal' merge 759105 759107 Bug #759105 [src:libcdio] libcdio: Breaks apt-get update - Unknown Multi-Arch type 'no' for package 'libcdio-dev' Bug #759107 [src:libcdio] Unknown Multi-Arch type 'no' for package 'libudf-dev' Marked as found in versions libcdio/0.92-1. Merged 759105 759107 thanks Stopping processing here. Please contact me if you need assistance. -- 759105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759105 759107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759107 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#755705: cyrus-imapd-2.4: still not binNMU safe
Hi, On Sun, Aug 24, 2014 at 01:57:51AM +0200, Ivo De Decker wrote: The problem isn't solved yet: the transitional packages cyrus-admin-2.4, cyrus-dev-2.4 and libcyrus-imap-perl24 are arch all, but they have a strict versioned depend on cyrus-common, which is arch: any, and has a different version after a binnmu. I guess the misc::depends is not necessary for the transitional packages. This is also the case for the other transitional packages. 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: forcibly merging 759105 759109
Processing commands for cont...@bugs.debian.org: forcemerge 759105 759109 Bug #759105 [src:libcdio] libcdio: Breaks apt-get update - Unknown Multi-Arch type 'no' for package 'libcdio-dev' Bug #759107 [src:libcdio] Unknown Multi-Arch type 'no' for package 'libudf-dev' Bug #759109 [src:libcdio] libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type Severity set to 'serious' from 'minor' Marked as found in versions libcdio/0.92-1. Bug #759107 [src:libcdio] Unknown Multi-Arch type 'no' for package 'libudf-dev' Merged 759105 759107 759109 thanks Stopping processing here. Please contact me if you need assistance. -- 759105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759105 759107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759107 759109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759109 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: gjiten: diff for NMU version 2.6-2.3
Processing control commands: tags 758999 + pending Bug #758999 [gjiten] gjiten: FTBFS due to conflicting (transitive) b-d libgnutls-dev - libgnomevfs2-dev Added tag(s) pending. -- 758999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758999 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#758999: gjiten: diff for NMU version 2.6-2.3
Control: tags 758999 + pending Dear maintainer, I've prepared an NMU for gjiten (versioned as 2.6-2.3) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. 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,11 @@ +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 + + -- Andreas Metzler ametz...@debian.org Sun, 24 Aug 2014 13:51:10 +0200 + gjiten (2.6-2.2) unstable; urgency=low * Non-maintainer upload. signature.asc Description: Digital signature
Processed: Remove FreeSCI from Debian
Processing commands for cont...@bugs.debian.org: severity 730057 serious Bug #730057 [freesci] Should this package be removed? Severity set to 'serious' from 'important' retitle 730057 This package shoudl be removed Bug #730057 [freesci] Should this package be removed? Changed Bug title to 'This package shoudl be removed' from 'Should this package be removed?' thanks Stopping processing here. Please contact me if you need assistance. -- 730057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730057 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#754631: marked as done (icedove: FTBFS on kfreebsd-i386: error: inlining failed in call to always_inline […])
Your message dated Sun, 24 Aug 2014 14:42:22 +0200 with message-id 20140824124222.ga28...@x201s.cruise.homelinux.net and subject line Re: Bug#754631: icedove: FTBFS on kfreebsd-i386: error: inlining failed in call to always_inline […] has caused the Debian Bug report #754631, regarding icedove: FTBFS on kfreebsd-i386: error: inlining failed in call to always_inline […] 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.) -- 754631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: icedove Version: 31.0~b1-2 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-i386: | c++ -o nsDependentString.o -c -I../../../dist/stl_wrappers -I../../../dist/system_wrappers -include /«PKGBUILDDIR»/mozilla/config/gcc_hidden.h -DMOZ_GLUE_IN_PROGRAM -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL -DSTATIC_EXPORTABLE_JS_API -DNO_NSPR_10_SUPPORT -I/«PKGBUILDDIR»/mozilla/xpcom/string/src -I. -I/«PKGBUILDDIR»/mozilla/mfbt/double-conversion -I../../../dist/include -I/usr/include/nspr -I/usr/include/nss -I/«PKGBUILDDIR»/obj-icedove/mozilla/dist/include -I/usr/include -I/usr/include/pixman-1-fPIC -D_FORTIFY_SOURCE=2 -DMOZILLA_CLIENT -include ../../../mozilla-config.h -MD -MP -MF .deps/nsDependentString.o.pp -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Werror=int-to-pointer-cast -Wtype-limits -Wempty-body -Wsign-compare -Wno-invalid-offsetof -Wcast-align -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-except ions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -O -fomit-frame-pointer /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsDependentString.cpp | nsDependentSubstring.o | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp: In member function 'void LossyConvertEncoding16to8::write_sse2(const char16_t*, uint32_t)': | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:25:43: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi] |__m128i vectmask = _mm_set1_epi16(0x00ff); |^ | In file included from /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:7:0: | /usr/lib/gcc/i486-kfreebsd-gnu/4.9/include/emmintrin.h:639:1: error: inlining failed in call to always_inline '__m128i _mm_set1_epi16(short int)': target specific option mismatch | _mm_set1_epi16 (short __A) | ^ | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:25:43: error: called from here |__m128i vectmask = _mm_set1_epi16(0x00ff); |^ | In file included from /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:7:0: | /usr/lib/gcc/i486-kfreebsd-gnu/4.9/include/emmintrin.h:686:1: error: inlining failed in call to always_inline '__m128i _mm_load_si128(const __m128i*)': target specific option mismatch | _mm_load_si128 (__m128i const *__P) | ^ | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:27:83: error: called from here | __m128i source1 = _mm_load_si128(reinterpret_castconst __m128i*(aSource + i)); | ^ | In file included from /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:7:0: | /usr/lib/gcc/i486-kfreebsd-gnu/4.9/include/emmintrin.h:1248:1: error: inlining failed in call to always_inline '__m128i _mm_and_si128(__m128i, __m128i)': target specific option mismatch | _mm_and_si128 (__m128i __A, __m128i __B) | ^ | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:28:47: error: called from here | source1 = _mm_and_si128(source1, vectmask); |^ | In file included from /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:7:0: | /usr/lib/gcc/i486-kfreebsd-gnu/4.9/include/emmintrin.h:686:1: error: inlining failed in call to always_inline '__m128i _mm_load_si128(const __m128i*)': target specific option mismatch | _mm_load_si128 (__m128i const *__P) | ^ | /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:30:87: error: called from here | __m128i source2 = _mm_load_si128(reinterpret_castconst __m128i*(aSource + i + 8)); | ^ | In file included from /«PKGBUILDDIR»/mozilla/xpcom/string/src/nsUTF8UtilsSSE2.cpp:7:0: |
Processed: retitle 730057 to This package should be removed
Processing commands for cont...@bugs.debian.org: retitle 730057 This package should be removed Bug #730057 [freesci] This package shoudl be removed Changed Bug title to 'This package should be removed' from 'This package shoudl be removed' thanks Stopping processing here. Please contact me if you need assistance. -- 730057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730057 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#754632: marked as done (icedove: FTBFS on kfreebsd-amd64: error: could not convert '0' from 'int' to 'mozilla::CrossProcessMutexHandle)
Your message dated Sun, 24 Aug 2014 14:42:57 +0200
with message-id 20140824124257.ga28...@x201s.cruise.homelinux.net
and subject line Re: Bug#754632: icedove: FTBFS on kfreebsd-amd64: error: could
not convert '0' from 'int' to 'mozilla::CrossProcessMutexHandle
has caused the Debian Bug report #754632,
regarding icedove: FTBFS on kfreebsd-amd64: error: could not convert '0' from
'int' to 'mozilla::CrossProcessMutexHandle
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.)
--
754632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: icedove
Version: 31.0~b1-2
Severity: serious
Justification: FTBFS
Hi,
your package no longer builds on kfreebsd-amd64:
| c++ -o CrossProcessMutex_unimplemented.o -c -I../../dist/stl_wrappers
-I../../dist/system_wrappers -include
/«PKGBUILDDIR»/mozilla/config/gcc_hidden.h -DOS_POSIX=1 -DOS_FREEBSD=1
-DOS_BSD=1 -DMOZ_CHILD_PROCESS_NAME='plugin-container'
-DMOZ_CHILD_PROCESS_BUNDLE='plugin-container.app/Contents/MacOS/'
-DMOZ_GLUE_IN_PROGRAM -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL
-DSTATIC_EXPORTABLE_JS_API -DNO_NSPR_10_SUPPORT
-I/«PKGBUILDDIR»/mozilla/ipc/glue -I. -I/«PKGBUILDDIR»/mozilla/xpcom/build
-I/«PKGBUILDDIR»/mozilla/xpcom/threads
-I/«PKGBUILDDIR»/mozilla/ipc/chromium/src -I/«PKGBUILDDIR»/mozilla/ipc/glue
-I/«PKGBUILDDIR»/mozilla/toolkit/crashreporter
-I/«PKGBUILDDIR»/obj-icedove/mozilla/ipc/ipdl/_ipdlheaders -I../../dist/include
-I/usr/include/nspr -I/usr/include/nss
-I/«PKGBUILDDIR»/obj-icedove/mozilla/dist/include -I/usr/include
-I/usr/include/pixman-1-fPIC -D_FORTIFY_SOURCE=2 -DMOZILLA_CLIENT -include
../../mozilla-config.h -MD -MP -MF .deps/CrossProcessMutex_unim
plemented.o.pp -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Woverloaded-virtual
-Werror=return-type -Werror=int-to-pointer-cast -Wtype-limits -Wempty-body
-Wsign-compare -Wno-invalid-offsetof -Wcast-align -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -fno-exceptions
-fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections
-fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED
-g -O -fomit-frame-pointer
/«PKGBUILDDIR»/mozilla/ipc/glue/CrossProcessMutex_unimplemented.cpp
| FileDescriptor.o
| /«PKGBUILDDIR»/mozilla/ipc/glue/CrossProcessMutex_unimplemented.cpp: In
member function 'mozilla::CrossProcessMutexHandle
mozilla::CrossProcessMutex::ShareToProcess(base::ProcessHandle)':
| /«PKGBUILDDIR»/mozilla/ipc/glue/CrossProcessMutex_unimplemented.cpp:43:10:
error: could not convert '0' from 'int' to 'mozilla::CrossProcessMutexHandle
{aka base::FileDescriptor}'
|return 0;
| ^
| /«PKGBUILDDIR»/mozilla/ipc/glue/CrossProcessMutex_unimplemented.cpp:44:1:
error: control reaches end of non-void function [-Werror=return-type]
| }
| ^
| cc1plus: some warnings being treated as errors
| /«PKGBUILDDIR»/mozilla/config/rules.mk:1001: recipe for target
'CrossProcessMutex_unimplemented.o' failed
| make[7]: *** [CrossProcessMutex_unimplemented.o] Error 1
| make[7]: *** Waiting for unfinished jobs
| /«PKGBUILDDIR»/mozilla/ipc/glue/BackgroundImpl.cpp:75:1: warning: 'bool
{anonymous}::IsChildProcess()' defined but not used [-Wunused-function]
| IsChildProcess()
| ^
| make[7]: Leaving directory '/«PKGBUILDDIR»/obj-icedove/mozilla/ipc/glue'
| make[6]: *** [libs] Error 2
| /«PKGBUILDDIR»/mozilla/config/recurse.mk:179: recipe for target 'libs' failed
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=icedovearch=kfreebsd-amd64ver=31.0~b1-2stamp=1403486892
Mraw,
KiBi.
---End Message---
---BeginMessage---
Version: 31.0-2
Hello Cyril,
On Sun, Jul 13, 2014 at 04:06:07AM +0200, Cyril Brulebois wrote:
Source: icedove
Version: 31.0~b1-2
Severity: serious
Justification: FTBFS
Hi,
your package no longer builds on kfreebsd-amd64:
...
the FTBFS on kfreebsd-amd64 is fixed by the last upload of version
31.0-2.
https://buildd.debian.org/status/fetch.php?pkg=icedovearch=kfreebsd-amd64ver=31.0-2stamp=1408864056
I will close this bug report by this mail.
Regards
Carsten---End Message---
Processed: Re: Bug#757199: [icedove] [32bit] getdents() = EOVERFLOW - Mail Extensions inaccessible when profile folder resides on large XFS or BTRFS volume with 64bit inodes
Processing commands for cont...@bugs.debian.org: severity 757199 important Bug #757199 [icedove] [icedove] [32bit] getdents() = EOVERFLOW - Mail Extensions inaccessible when profile folder resides on large XFS or BTRFS volume with 64bit inodes Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 757199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757199 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#757199: [icedove] [32bit] getdents() = EOVERFLOW - Mail Extensions inaccessible when profile folder resides on large XFS or BTRFS volume with 64bit inodes
severity 757199 important thanks Hello Marcel, On Tue, Aug 05, 2014 at 11:05:13PM +0200, Marcel Partap wrote: Package: icedove Version: 31.0-1 Severity: serious --- Please enter the report below this line. --- After migrating my home directory to a 1.8TiB XFS partition, I could not access my emails anymore. Icedove would open, but all extensions from the profile folder were missing. The accounts were listed with the name crossed out in the folder pane - yet the INBOX of my POP3 account (and a single subfolder) would show up (including the mail contained therein)... Rsyncing the profile folder from my backup one time after another and trying various things kept me busy for most of the day... with an AUFS union set up merging the backup root partition (ro) and /tmp (rw), the same profile folder did work! Digging deeper I finally found the right clues to identify the problem cause: xfs uses 64-bit inodes by default for volumes 1TiB (and I think BTRFS does now, too).. Icedove chokes on those. due your not typical partition layout with the big XFS usage I set the severity to important. We have to investigate this issue deeper. Propably we have to set up a similar system to readjust this issue. Any help is appreciated. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758999: gjiten: diff for NMU version 2.6-2.3
Hi Andreas, Unfortunately I don't have upload rights, so feel free to do so. Thanks for taking care of this! Regards, Botond On Sun, 24 Aug 2014 14:04:51 +0200 Andreas Metzler ametz...@bebt.de wrote: Control: tags 758999 + pending Dear maintainer, I've prepared an NMU for gjiten (versioned as 2.6-2.3) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. 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' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758999: gjiten: diff for NMU version 2.6-2.3
On 2014-08-24 Botond Botyanszki debian-b...@siliconium.net wrote: Hi Andreas, Unfortunately I don't have upload rights, so feel free to do so. Thanks for taking care of this! [...] Hi Botond, Thanks for the heads-up. If you want to do a maintainer upload instead and need a sponsor feel free to contact me. 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' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748626: openjade FTBFS Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?).
* Wookey (woo...@wookware.org) [140824 13:34]: or just use dh_autoreconf which I think does exactly the same thing. So with the attached patch the configure goes OK and the build proceeds but eventually stops with: make[3]: Entering directory '/home/buildd/packages/modified/openjade-1.4devel1/po' make[3]: *** No rule to make target 'Makevars', needed by 'Makefile'. Stop. One could create a Makevars from Makevars.template (or rather, I copied the template to Makevars and ran sed -e 's,COPYRIGHT_HOLDER.*,COPYRIGHT_HOLDER = see po-files,' -i po/Makevars ). After doing so, the build fails at a later stage, because the PACKAGE-variable is now used as openjade but should be OpenJade (as also seen in configure.in). (One could adjust the installation paths of course or move files around, but that doesn't seem to be the right solution.) Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748626: openjade FTBFS Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?).
* Andreas Barth (a...@ayous.org) [140824 15:37]: * Wookey (woo...@wookware.org) [140824 13:34]: or just use dh_autoreconf which I think does exactly the same thing. So with the attached patch the configure goes OK and the build proceeds but eventually stops with: make[3]: Entering directory '/home/buildd/packages/modified/openjade-1.4devel1/po' make[3]: *** No rule to make target 'Makevars', needed by 'Makefile'. Stop. One could create a Makevars from Makevars.template (or rather, I copied the template to Makevars and ran sed -e 's,COPYRIGHT_HOLDER.*,COPYRIGHT_HOLDER = see po-files,' -i po/Makevars ). After doing so, the build fails at a later stage, because the PACKAGE-variable is now used as openjade but should be OpenJade (as also seen in configure.in). (One could adjust the installation paths of course or move files around, but that doesn't seem to be the right solution.) With these changes everything builds as it should: --- configure.in~ 2014-08-24 12:52:22.667482046 + +++ configure.in2014-08-24 13:55:47.737475362 + @@ -11,7 +11,7 @@ dnl dnl Initialization -AC_INIT([OpenJade], [1.4devel], []) +AC_INIT([OpenJade], [1.4devel], [], [OpenJade]) AC_CONFIG_SRCDIR(dsssl) AM_INIT_AUTOMAKE([foreign]) AM_CONFIG_HEADER([config.h]) --- po/Makevars.template2014-08-24 13:52:30.699437001 + +++ po/Makevars 2014-08-24 13:08:04.215437344 + @@ -18,7 +18,7 @@ # or entity, or to disclaim their copyright. The empty string stands for # the public domain; in this case the translators are expected to disclaim # their copyright. -COPYRIGHT_HOLDER = Free Software Foundation, Inc. +COPYRIGHT_HOLDER = see po-files # This tells whether or not to prepend GNU prefix to the package # name that gets inserted into the header of the $(DOMAIN).pot file. The libos*-packages are as they should. However, the programm misses the jade.mo-files, so something still needs to be done. Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748626: openjade FTBFS Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?).
* Andreas Barth (a...@ayous.org) [140824 16:07]: The libos*-packages are as they should. However, the programm misses the jade.mo-files, so something still needs to be done. This is fixed by setting the domain in Makevars. I intend to upload the NMU as below later today (generated files removed from the diff). (I'll probably also add some more rm to debian/rules clean target to remove generated files which are not there currently.) Andi diff -Nru openjade-1.4devel1/configure.in openjade-1.4devel1/configure.in --- openjade-1.4devel1/configure.in 2014-08-24 14:17:28.0 + +++ openjade-1.4devel1/configure.in 2014-08-24 14:17:28.0 + @@ -11,11 +11,13 @@ dnl dnl Initialization -AC_INIT(dsssl) -AM_INIT_AUTOMAKE(OpenJade, 1.4devel, no-define) -AM_CONFIG_HEADER(config.h) +AC_INIT([OpenJade], [1.4devel], [], [OpenJade]) +AC_CONFIG_SRCDIR(dsssl) +AM_INIT_AUTOMAKE([foreign]) +AM_CONFIG_HEADER([config.h]) AM_SANITY_CHECK AM_MAINTAINER_MODE +AC_USE_SYSTEM_EXTENSIONS dnl Use different names than usually to avoid conflicts. AC_DEFINE_UNQUOTED(OPENJADE_PACKAGE, $PACKAGE, [Package name]) @@ -36,8 +38,8 @@ dnl Checks for libraries. AC_CHECK_LIB(pthread,pthread_create,,AC_CHECK_LIB(threads,cthread_fork)) AM_GNU_GETTEXT -AM_GNU_GETTEXT_VERSION -AC_CHECK_HEADERS(locale.h) +AM_GNU_GETTEXT_VERSION([0.19.2]) +AC_CHECK_HEADERS([locale.h]) AC_DEFINE_DIR(OPENJADE_LOCALE_DIR, datadir/locale, [location of message catalogs]) OPENJADE_MESSAGE_DOMAIN=jade AC_DEFINE_UNQUOTED(OPENJADE_MESSAGE_DOMAIN, $OPENJADE_MESSAGE_DOMAIN, [message domain]) @@ -46,13 +48,13 @@ dnl Checks for header files. AC_HEADER_STDC -AC_CHECK_HEADERS(limits.h) -AC_LANG_CPLUSPLUS +AC_CHECK_HEADERS([limits.h]) +AC_LANG([C++]) AC_CHECK_HEADERS(new cassert) dnl Checks for typedefs, structures and compiler characteristics. AC_TYPE_SIZE_T -AC_STRUCT_ST_BLKSIZE +AC_CHECK_MEMBERS([struct stat.st_blksize]) AC_CACHE_CHECK(for sig_atomic_t in signal.h, ac_cv_have_sig_atomic_t, AC_TRY_LINK([#include signal.h],sig_atomic_t x;, diff -Nru openjade-1.4devel1/debian/changelog openjade-1.4devel1/debian/changelog --- openjade-1.4devel1/debian/changelog 2014-08-24 14:17:28.0 + +++ openjade-1.4devel1/debian/changelog 2014-08-24 14:17:28.0 + @@ -1,3 +1,19 @@ +openjade (1.4devel1-21.1) unstable; urgency=medium + + [ Wookey ] + * Add acinclude.m4 macro to find correct intlh header whether or +not gettext is present (Closes: #748626, ##759100) + * Update rules file to use dh-autoreconf rather than manual commands +and update configure.in enough for autoreconf to work + + [ Andreas Barth ] + * Non-maintainer upload. + * Update configure.in to set PACKAGE_TARNAME to mixed case. + * Create po/Makevars with copyright hint to individual pot files +and DOMAIN=jade + + -- Andreas Barth a...@ayous.org Sun, 24 Aug 2014 12:47:55 + + openjade (1.4devel1-21) unstable; urgency=low * Added dependency on libperl4-corelibs-perl for getopts.pl. (Closes: diff -Nru openjade-1.4devel1/debian/control openjade-1.4devel1/debian/control --- openjade-1.4devel1/debian/control 2014-08-24 14:17:28.0 + +++ openjade-1.4devel1/debian/control 2014-08-24 14:17:28.0 + @@ -4,7 +4,7 @@ Maintainer: Neil Roeth n...@debian.org Homepage: http://openjade.sourceforge.net/ Standards-Version: 3.9.2.0 -Build-Depends: libosp-dev (= 1.5.1.0-2.1), debhelper (= 4.1.75), autotools-dev, gettext, dh-buildinfo, libperl4-corelibs-perl +Build-Depends: libosp-dev (= 1.5.1.0-2.1), debhelper (= 4.1.75), dh-autoreconf, gettext, dh-buildinfo, libperl4-corelibs-perl Package: openjade Architecture: any diff -Nru openjade-1.4devel1/debian/rules openjade-1.4devel1/debian/rules --- openjade-1.4devel1/debian/rules 2014-08-24 14:17:28.0 + +++ openjade-1.4devel1/debian/rules 2014-08-24 14:17:28.0 + @@ -77,13 +77,6 @@ mv OpenJade-1.4devel/ChangeLog . rm -r OpenJade-1.4devel -autoinit: - aclocal - autoheader - libtoolize --force --copy - automake --add-missing --force-missing --copy - autoconf - clean: dh_testdir rm -f debian/buildinfo @@ -96,14 +89,11 @@ style/DssslAppMessages.h jade/JadeMessages.h \ jade/RtfMessages.h jade/HtmlMessages.h jade/TeXMessages.h \ jade/MifMessages.h - # See /usr/share/doc/autotools-dev/README.Debian.gz - -test -r /usr/share/misc/config.sub \ - cp -f /usr/share/misc/config.sub config.sub - -test -r /usr/share/misc/config.guess \ - cp -f /usr/share/misc/config.guess config.guess + dh_autoreconf_clean configure: configure-stamp configure-stamp: + dh_autoreconf dh_buildinfo generate cat ./configure --prefix=/usr --enable-http --enable-shared --enable-static touch $@ diff -Nru openjade-1.4devel1/po/Makevars openjade-1.4devel1/po/Makevars ---
Bug#748626: openjade FTBFS Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?).
* Andreas Barth (a...@ayous.org) [140824 16:31]: I intend to upload the NMU as below later today (generated files removed from the diff). (I'll probably also add some more rm to debian/rules clean target to remove generated files which are not there currently.) Final diff, upload will happen in ~2 hours if nobody yells at me. Andi diff -u openjade-1.4devel1/debian/changelog openjade-1.4devel1/debian/changelog --- openjade-1.4devel1/debian/changelog +++ openjade-1.4devel1/debian/changelog @@ -1,3 +1,19 @@ +openjade (1.4devel1-21.1) unstable; urgency=medium + + [ Wookey ] + * Add acinclude.m4 macro to find correct intlh header whether or +not gettext is present (Closes: #748626, ##759100) + * Update rules file to use dh-autoreconf rather than manual commands +and update configure.in enough for autoreconf to work + + [ Andreas Barth ] + * Non-maintainer upload. + * Update configure.in to set PACKAGE_TARNAME to mixed case. + * Create po/Makevars with copyright hint to individual pot files. +and DOMAIN=jade + + -- Andreas Barth a...@ayous.org Sun, 24 Aug 2014 12:47:55 + + openjade (1.4devel1-21) unstable; urgency=low * Added dependency on libperl4-corelibs-perl for getopts.pl. (Closes: diff -u openjade-1.4devel1/debian/control openjade-1.4devel1/debian/control --- openjade-1.4devel1/debian/control +++ openjade-1.4devel1/debian/control @@ -4,7 +4,7 @@ Maintainer: Neil Roeth n...@debian.org Homepage: http://openjade.sourceforge.net/ Standards-Version: 3.9.2.0 -Build-Depends: libosp-dev (= 1.5.1.0-2.1), debhelper (= 4.1.75), autotools-dev, gettext, dh-buildinfo, libperl4-corelibs-perl +Build-Depends: libosp-dev (= 1.5.1.0-2.1), debhelper (= 4.1.75), dh-autoreconf, gettext, dh-buildinfo, libperl4-corelibs-perl Package: openjade Architecture: any diff -u openjade-1.4devel1/debian/rules openjade-1.4devel1/debian/rules --- openjade-1.4devel1/debian/rules +++ openjade-1.4devel1/debian/rules @@ -77,13 +77,6 @@ mv OpenJade-1.4devel/ChangeLog . rm -r OpenJade-1.4devel -autoinit: - aclocal - autoheader - libtoolize --force --copy - automake --add-missing --force-missing --copy - autoconf - clean: dh_testdir rm -f debian/buildinfo @@ -96,14 +89,12 @@ style/DssslAppMessages.h jade/JadeMessages.h \ jade/RtfMessages.h jade/HtmlMessages.h jade/TeXMessages.h \ jade/MifMessages.h - # See /usr/share/doc/autotools-dev/README.Debian.gz - -test -r /usr/share/misc/config.sub \ - cp -f /usr/share/misc/config.sub config.sub - -test -r /usr/share/misc/config.guess \ - cp -f /usr/share/misc/config.guess config.guess + dh_autoreconf_clean + rm -f debian/*.debhelper.log configure: configure-stamp configure-stamp: + dh_autoreconf dh_buildinfo generate cat ./configure --prefix=/usr --enable-http --enable-shared --enable-static touch $@ --- openjade-1.4devel1.orig/po/Makevars +++ openjade-1.4devel1/po/Makevars @@ -0,0 +1,72 @@ +# Makefile variables for PO directory in any package using GNU gettext. + +# Usually the message domain is the same as the package name. +DOMAIN = jade + +# These two variables depend on the location of this directory. +subdir = po +top_builddir = .. + +# These options get passed to xgettext. +XGETTEXT_OPTIONS = --keyword=_ --keyword=N_ + +# This is the copyright holder that gets inserted into the header of the +# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding +# package. (Note that the msgstr strings, extracted from the package's +# sources, belong to the copyright holder of the package.) Translators are +# expected to transfer the copyright for their translations to this person +# or entity, or to disclaim their copyright. The empty string stands for +# the public domain; in this case the translators are expected to disclaim +# their copyright. +COPYRIGHT_HOLDER = see po-files + +# This tells whether or not to prepend GNU prefix to the package +# name that gets inserted into the header of the $(DOMAIN).pot file. +# Possible values are yes, no, or empty. If it is empty, try to +# detect it automatically by scanning the files in $(top_srcdir) for +# GNU packagename string. +PACKAGE_GNU = + +# This is the email address or URL to which the translators shall report +# bugs in the untranslated strings: +# - Strings which are not entire sentences, see the maintainer guidelines +# in the GNU gettext documentation, section 'Preparing Strings'. +# - Strings which use unclear terms or require additional context to be +# understood. +# - Strings which make invalid assumptions about notation of date, time or +# money. +# - Pluralisation problems. +# - Incorrect English spelling. +# - Incorrect formatting. +# It can be your email address, or a mailing list address where translators +# can write to without being subscribed, or the URL of a web page through
Bug#746851: marked as done (gdb-msp430: ftbfs with GCC-4.9)
Your message dated Sun, 24 Aug 2014 15:20:17 + with message-id e1xlzab-0004u4...@franck.debian.org and subject line Bug#746851: fixed in gdb-msp430 7.2a~mspgcc-20111205-3 has caused the Debian Bug report #746851, regarding gdb-msp430: ftbfs with GCC-4.9 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.) -- 746851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gdb-msp430 Version: 7.2a~mspgcc-20111205-2 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.9 The package fails to build in a test rebuild on at least amd64 with gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The severity of this report may be raised before the jessie release. The full build log can be found at: http://people.debian.org/~doko/logs/failed-gcc49/gdb-msp430_7.2a~mspgcc-20111205-2_unstable_gcc49.log The last lines of the build log are at the end of this report. To build with GCC 4.9, either set CC=gcc-4.9 CXX=g++-4.9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-4.9/porting_to.html [...] /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR='/usr/bin' -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfd.lo -MD -MP -MF .deps/bfd.Tpo -c -o bfd.lo bfd.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\/usr/bin\ -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfd.lo -MD -MP -MF .deps/bfd.Tpo -c bfd.c -o bfd.o mv -f .deps/bfd.Tpo .deps/bfd.Plo /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR='/usr/bin' -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfdio.lo -MD -MP -MF .deps/bfdio.Tpo -c -o bfdio.lo bfdio.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\/usr/bin\ -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfdio.lo -MD -MP -MF .deps/bfdio.Tpo -c bfdio.c -o bfdio.o mv -f .deps/bfdio.Tpo .deps/bfdio.Plo /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR='/usr/bin' -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfdwin.lo -MD -MP -MF .deps/bfdwin.Tpo -c -o bfdwin.lo bfdwin.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\/usr/bin\ -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT bfdwin.lo -MD -MP -MF .deps/bfdwin.Tpo -c bfdwin.c -o bfdwin.o mv -f .deps/bfdwin.Tpo .deps/bfdwin.Plo /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR='/usr/bin' -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT cache.lo -MD -MP -MF .deps/cache.Tpo -c -o cache.lo cache.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec -DBINDIR=\/usr/bin\ -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT cache.lo -MD -MP -MF .deps/cache.Tpo -c cache.c -o cache.o mv -f .deps/cache.Tpo .deps/cache.Plo /bin/bash ./libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include -DHAVE_bfd_elf32_msp430_vec
Bug#759107: marked as done (Unknown Multi-Arch type 'no' for package 'libudf-dev')
Your message dated Sun, 24 Aug 2014 15:21:23 + with message-id e1xlzbf-0004jn...@franck.debian.org and subject line Bug#759109: fixed in libcdio 0.92-2 has caused the Debian Bug report #759109, regarding Unknown Multi-Arch type 'no' for package 'libudf-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.) -- 759109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libudf-dev Version: 0.92-1 Unknown Multi-Arch type 'no' for package 'libcdio-dev' Unknown Multi-Arch type 'no' for package 'libiso9660-dev' Unknown Multi-Arch type 'no' for package 'libudf-dev' ---End Message--- ---BeginMessage--- Source: libcdio Source-Version: 0.92-2 We believe that the bug you reported is fixed in the latest version of libcdio, 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. Nicolas Boullis nboul...@debian.org (supplier of updated libcdio 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: Sun, 24 Aug 2014 15:58:03 +0200 Source: libcdio Binary: libcdio-dev libcdio15 libiso9660-dev libiso9660-9 libudf-dev libudf0 libcdio-utils Architecture: source i386 Version: 0.92-2 Distribution: experimental Urgency: low Maintainer: Nicolas Boullis nboul...@debian.org Changed-By: Nicolas Boullis nboul...@debian.org Description: libcdio-dev - library to read and control CD-ROM (development files) libcdio-utils - sample applications based on the CDIO libraries libcdio15 - library to read and control CD-ROM libiso9660-9 - library to work with ISO9660 filesystems libiso9660-dev - library to work with ISO9660 filesystems (development files) libudf-dev - library to work with UDF filesystems (development files) libudf0- library to work with UDF filesystems Closes: 759109 Changes: libcdio (0.92-2) experimental; urgency=low . * debian/control: Remove the Multi-Arch: no field from the -dev packages: although this value is supposed to be correct according to deb_control(5), apt complains about it. As this value matches the default behaviour without a Muti-Arch: field, it can safely be removed. Thanks to Axel Beckert, Andreas Metzler and Dan Jacobson for pointing this. (Closes: #759109) Checksums-Sha1: d7caa027115d9372778e0617e81f187ffe957573 1667 libcdio_0.92-2.dsc 31e060a99c1306875c01a28fa602b19a3755a1ea 9568 libcdio_0.92-2.debian.tar.xz d1bf7a2fde950d84e73435bb1f61c9ed2ba719b7 294640 libcdio-dev_0.92-2_i386.deb 2bcc7f9990179bda34c41e38333e0ea58dff8d74 193538 libcdio15_0.92-2_i386.deb a30c5782008b5d72956107d2107451940f2c2ca8 166736 libiso9660-dev_0.92-2_i386.deb ce224194b2a46e7e6863e7dc8e2cc38296ba7e29 154594 libiso9660-9_0.92-2_i386.deb 304a3304e0fcae92c3a5b388f7c445f2425204a9 149918 libudf-dev_0.92-2_i386.deb e34adcced409a7cad8fef3fcdaae29f8ee53 141708 libudf0_0.92-2_i386.deb 622a0f6f3fdfd10d3d07fd90d294c8d88b6b2a3c 183090 libcdio-utils_0.92-2_i386.deb Checksums-Sha256: d6c6eb845dd9ecfed9114dede9a549dd8e46d232f3b8bb0fc18e2d0f3d094b0c 1667 libcdio_0.92-2.dsc 3f49bcab6cbbbe07dd054f817bad915710f6c93bc916f21a8044c693c616f0aa 9568 libcdio_0.92-2.debian.tar.xz 21316fa2b021657f128063a2bcab082055012834a01e2704a70f0928c1bcbda5 294640 libcdio-dev_0.92-2_i386.deb a9878ba18fbeec41268d072f05bef95f916c3cefcabf9f3eac24532715e27b7e 193538 libcdio15_0.92-2_i386.deb 40729a1579eb3fa83a3015f51a1d861f9fb017c7b695117e16bcca528ffe79c6 166736 libiso9660-dev_0.92-2_i386.deb 249286e864dbf62c2af2231b2c4b995da804dee656ac40b61f563bdf8ddae666 154594 libiso9660-9_0.92-2_i386.deb d0861e4bc88ba10efde55870d674c09157d760736e3f49d12b119e6df14423a0 149918 libudf-dev_0.92-2_i386.deb be3f865bf3ce70a23fb1560378c2323ca430c8d3e3e144c395958c9866d990cc 141708 libudf0_0.92-2_i386.deb 2760b19303dc4011366ab94d4d0006a6158ffc0804f90375b3f86be6de555f49 183090 libcdio-utils_0.92-2_i386.deb Files: 1885ffd160fa77d387dffb8eb97a7dd3 294640 libdevel optional libcdio-dev_0.92-2_i386.deb fc7259448d766141212cdd71bfeea597 193538 libs optional libcdio15_0.92-2_i386.deb
Bug#759109: marked as done (libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type)
Your message dated Sun, 24 Aug 2014 15:21:23 + with message-id e1xlzbf-0004jn...@franck.debian.org and subject line Bug#759109: fixed in libcdio 0.92-2 has caused the Debian Bug report #759109, regarding libcdio-dev: Causes every apt command to argue about unknown Multi-Arch type 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.) -- 759109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libcdio Version: 0.92-1 Severity: important Dear Maintainer, your recent upload to experimental causes the following APT warnings with nearly every APT-based command, at least apt-get update, apt-cache policy $packagename, and aptitude: $ apt-cache policy foobar W: Unknown Multi-Arch type 'no' for package 'libcdio-dev' W: Unknown Multi-Arch type 'no' for package 'libiso9660-dev' W: Unknown Multi-Arch type 'no' for package 'libudf-dev' W: You may want to run apt-get update to correct these problems N: Unable to locate package foobar $ While this seem to cause no actual harm, it's _very_ annoying to have these warnings with every apt command. (Cc'ing the APT maintainers for their information.) I'm sure, I'm not the only one who would be _very_ happy if you could fix this issue quickly. :-) I will also file a lintian feature request as lintian does not show _any_ warning about this in e.g. the libcdio-dev package yet. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental'), (109, 'buildd-unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: libcdio Source-Version: 0.92-2 We believe that the bug you reported is fixed in the latest version of libcdio, 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. Nicolas Boullis nboul...@debian.org (supplier of updated libcdio 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: Sun, 24 Aug 2014 15:58:03 +0200 Source: libcdio Binary: libcdio-dev libcdio15 libiso9660-dev libiso9660-9 libudf-dev libudf0 libcdio-utils Architecture: source i386 Version: 0.92-2 Distribution: experimental Urgency: low Maintainer: Nicolas Boullis nboul...@debian.org Changed-By: Nicolas Boullis nboul...@debian.org Description: libcdio-dev - library to read and control CD-ROM (development files) libcdio-utils - sample applications based on the CDIO libraries libcdio15 - library to read and control CD-ROM libiso9660-9 - library to work with ISO9660 filesystems libiso9660-dev - library to work with ISO9660 filesystems (development files) libudf-dev - library to work with UDF filesystems (development files) libudf0- library to work with UDF filesystems Closes: 759109 Changes: libcdio (0.92-2) experimental; urgency=low . * debian/control: Remove the Multi-Arch: no field from the -dev packages: although this value is supposed to be correct according to deb_control(5), apt complains about it. As this value matches the default behaviour without a Muti-Arch: field, it can safely be removed. Thanks to Axel Beckert, Andreas Metzler and Dan Jacobson for pointing this. (Closes: #759109) Checksums-Sha1: d7caa027115d9372778e0617e81f187ffe957573 1667 libcdio_0.92-2.dsc 31e060a99c1306875c01a28fa602b19a3755a1ea 9568 libcdio_0.92-2.debian.tar.xz d1bf7a2fde950d84e73435bb1f61c9ed2ba719b7 294640 libcdio-dev_0.92-2_i386.deb 2bcc7f9990179bda34c41e38333e0ea58dff8d74 193538 libcdio15_0.92-2_i386.deb a30c5782008b5d72956107d2107451940f2c2ca8 166736 libiso9660-dev_0.92-2_i386.deb ce224194b2a46e7e6863e7dc8e2cc38296ba7e29 154594 libiso9660-9_0.92-2_i386.deb 304a3304e0fcae92c3a5b388f7c445f2425204a9 149918 libudf-dev_0.92-2_i386.deb e34adcced409a7cad8fef3fcdaae29f8ee53 141708 libudf0_0.92-2_i386.deb 622a0f6f3fdfd10d3d07fd90d294c8d88b6b2a3c 183090 libcdio-utils_0.92-2_i386.deb
Bug#759105: marked as done (libcdio: Breaks apt-get update - Unknown Multi-Arch type 'no' for package 'libcdio-dev')
Your message dated Sun, 24 Aug 2014 15:21:23 + with message-id e1xlzbf-0004jn...@franck.debian.org and subject line Bug#759109: fixed in libcdio 0.92-2 has caused the Debian Bug report #759109, regarding libcdio: Breaks apt-get update - Unknown Multi-Arch type 'no' for package 'libcdio-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.) -- 759109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libcdio Version: 0.92-1 Severity: normal The latest libcdio triggers this error on any system with experimental in sources.lists: - Reading package lists... Done W: Unknown Multi-Arch type 'no' for package 'libcdio-dev' W: Unknown Multi-Arch type 'no' for package 'libiso9660-dev' W: Unknown Multi-Arch type 'no' for package 'libudf-dev' W: You may want to run apt-get update to correct these problems - According to https://wiki.ubuntu.com/MultiarchSpec no is not a valid value for the Multi-Arch field. 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: libcdio Source-Version: 0.92-2 We believe that the bug you reported is fixed in the latest version of libcdio, 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. Nicolas Boullis nboul...@debian.org (supplier of updated libcdio 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: Sun, 24 Aug 2014 15:58:03 +0200 Source: libcdio Binary: libcdio-dev libcdio15 libiso9660-dev libiso9660-9 libudf-dev libudf0 libcdio-utils Architecture: source i386 Version: 0.92-2 Distribution: experimental Urgency: low Maintainer: Nicolas Boullis nboul...@debian.org Changed-By: Nicolas Boullis nboul...@debian.org Description: libcdio-dev - library to read and control CD-ROM (development files) libcdio-utils - sample applications based on the CDIO libraries libcdio15 - library to read and control CD-ROM libiso9660-9 - library to work with ISO9660 filesystems libiso9660-dev - library to work with ISO9660 filesystems (development files) libudf-dev - library to work with UDF filesystems (development files) libudf0- library to work with UDF filesystems Closes: 759109 Changes: libcdio (0.92-2) experimental; urgency=low . * debian/control: Remove the Multi-Arch: no field from the -dev packages: although this value is supposed to be correct according to deb_control(5), apt complains about it. As this value matches the default behaviour without a Muti-Arch: field, it can safely be removed. Thanks to Axel Beckert, Andreas Metzler and Dan Jacobson for pointing this. (Closes: #759109) Checksums-Sha1: d7caa027115d9372778e0617e81f187ffe957573 1667 libcdio_0.92-2.dsc 31e060a99c1306875c01a28fa602b19a3755a1ea 9568 libcdio_0.92-2.debian.tar.xz d1bf7a2fde950d84e73435bb1f61c9ed2ba719b7 294640 libcdio-dev_0.92-2_i386.deb 2bcc7f9990179bda34c41e38333e0ea58dff8d74 193538 libcdio15_0.92-2_i386.deb a30c5782008b5d72956107d2107451940f2c2ca8 166736 libiso9660-dev_0.92-2_i386.deb ce224194b2a46e7e6863e7dc8e2cc38296ba7e29 154594 libiso9660-9_0.92-2_i386.deb 304a3304e0fcae92c3a5b388f7c445f2425204a9 149918 libudf-dev_0.92-2_i386.deb e34adcced409a7cad8fef3fcdaae29f8ee53 141708 libudf0_0.92-2_i386.deb 622a0f6f3fdfd10d3d07fd90d294c8d88b6b2a3c 183090 libcdio-utils_0.92-2_i386.deb Checksums-Sha256: d6c6eb845dd9ecfed9114dede9a549dd8e46d232f3b8bb0fc18e2d0f3d094b0c 1667 libcdio_0.92-2.dsc 3f49bcab6cbbbe07dd054f817bad915710f6c93bc916f21a8044c693c616f0aa 9568 libcdio_0.92-2.debian.tar.xz 21316fa2b021657f128063a2bcab082055012834a01e2704a70f0928c1bcbda5 294640 libcdio-dev_0.92-2_i386.deb a9878ba18fbeec41268d072f05bef95f916c3cefcabf9f3eac24532715e27b7e 193538 libcdio15_0.92-2_i386.deb 40729a1579eb3fa83a3015f51a1d861f9fb017c7b695117e16bcca528ffe79c6 166736 libiso9660-dev_0.92-2_i386.deb
Bug#735227: activemq is marked for autoremoval from testing
On 08/20/2014 09:39 PM, Debian testing autoremoval watch wrote: activemq 5.6.0+dfsg-1 is marked for autoremoval from testing on 2014-08-29 It is affected by these RC bugs: 735227: activemq: [activemq] Non sourced jquery Hi Emmanuel and Eugene, I see updates to the packaging in the pkg-java repo - thanks! Any concerns with me building and uploading the new dfsg version? Thank you, tony signature.asc Description: OpenPGP digital signature
Bug#736039: marked as done (please build-depend on libtiff-dev, not libtiff4-dev)
Your message dated Sun, 24 Aug 2014 15:49:53 + with message-id e1xla3f-0001bb...@franck.debian.org and subject line Bug#736039: fixed in pinball 0.3.1-13.2 has caused the Debian Bug report #736039, regarding please build-depend on libtiff-dev, not libtiff4-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.) -- 736039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pinball Version: 0.3.1-13.1 User: q...@debian.org Usertags: libtiff4-dev The libtiff4-dev package is a transitional package that is going to disappear soon. Please update your build dependency from libtiff4-dev to libtiff-dev. ---End Message--- ---BeginMessage--- Source: pinball Source-Version: 0.3.1-13.2 We believe that the bug you reported is fixed in the latest version of pinball, 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 736...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated pinball 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: Sat, 23 Aug 2014 14:16:37 +0200 Source: pinball Binary: pinball pinball-dev pinball-data Architecture: source amd64 all Version: 0.3.1-13.2 Distribution: unstable Urgency: medium Maintainer: Jochen Friedrich joc...@scram.de Changed-By: Markus Koschany a...@gambaru.de Description: pinball- Emilia Pinball Emulator pinball-data - Data files for the Emilia Pinball Emulator pinball-dev - Development files for the Emilia Pinball Emulator Closes: 736039 750082 Changes: pinball (0.3.1-13.2) unstable; urgency=medium . * Non-maintainer upload. * Build-depend on libtiff-dev instead of libtiff4-dev because the latter is going to disappear soon. (Closes: #736039) * Add missing-separators.patch. - Replace spaces with TABS in Makefiles and thus fix a FTBFS with newer versions of GNU Make which are less fault tolerant. Thanks to Michael Tautschnig for the report. (Closes: #750082) Checksums-Sha1: b477a50b72d7fbe501f899f69ef3540b77ce6a41 2079 pinball_0.3.1-13.2.dsc 7daf63a7b7e586ede2a6ffae3e53abd0e23fff22 6082982 pinball_0.3.1.orig.tar.gz 6311da7763241c1975f13b038cf8f4e3cfb89456 9508 pinball_0.3.1-13.2.debian.tar.xz 09559563aa27e7db829d71090d87df5e77a2a056 176494 pinball_0.3.1-13.2_amd64.deb bec52425010d9627bf4ae30064c6eb68d733ae28 255792 pinball-dev_0.3.1-13.2_amd64.deb 8caae597982fa9742fe95f6be36ade3de519b972 4368748 pinball-data_0.3.1-13.2_all.deb Checksums-Sha256: 39973599fa8474ae08cb464dd195c2c81a16cf94c045d4ab44f862dde87804a8 2079 pinball_0.3.1-13.2.dsc ba47989f7fb6e294faa95285563220c8b01c3dbb9aa1bc29828eb7e832855cb8 6082982 pinball_0.3.1.orig.tar.gz 3155b2a0e3bca9ec820f21cd96070e34f5f83c9ca7c7ced3a0da447e55b54465 9508 pinball_0.3.1-13.2.debian.tar.xz c31a9afd4d08f22f27415dca3127a741d0432f3c1be491622a093394e822b47b 176494 pinball_0.3.1-13.2_amd64.deb bbb5e5bd4e22d36a55652a9e9cfc42094c44bec1e78d180c87b114f2c499465e 255792 pinball-dev_0.3.1-13.2_amd64.deb de6951b95c4bef180754d5567d8f86de6e9ed6dea6c73acdb3ae7a274eeaa5cc 4368748 pinball-data_0.3.1-13.2_all.deb Files: b883219886e053ec25396b9e2a2cffdf 176494 games optional pinball_0.3.1-13.2_amd64.deb b610da6b47d52411760ae0cf7ffda42e 255792 games optional pinball-dev_0.3.1-13.2_amd64.deb 8f9308eb9bae327c8f40dbd3cea2150e 4368748 games optional pinball-data_0.3.1-13.2_all.deb 5b5caea74fa8c2048120928afe44c161 2079 games optional pinball_0.3.1-13.2.dsc f28e8f49e0db8e9491e4d9f0c13c36c6 6082982 games optional pinball_0.3.1.orig.tar.gz bf319d2e42f25127f79e7f84e2a4e316 9508 games optional pinball_0.3.1-13.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT+gg0AAoJEHQmOzf1tfkTUM4P/2xVOAewaHUMABidm6l/uZz+ xqg+d2pdL1YhmFsN24yIsAGvypmnBNl3Jsv+WTTAZaG0XtlXofR+4NH0iMFPeXAn bcclrkM+yWZhw9jfyx6ws16WUNacA+b2Qv2hiAjK3z6mFu35P9Ts22zXK04RENgF OGf6ar9iTiUsR1Wt9g+jMSdpQtF3RbMZk6TcvOWf7FtXL87iNG6wN7bKDv5msLf1 MmbPUjYheysRWFWqIs9mFxwF/C/bra6EXakJIcJrfF32vTcbjpjTCXUWB6645EBT B+M3e3vHW2NKxL9Rtqm1sYWy9XewldS1j18sTCBzjf69czaEDzH15vKydYMrDC7Z
Bug#750082: marked as done (pinball: FTBFS - Makefile:820: *** missing separator (did you mean TAB instead of 8 spaces?).)
Your message dated Sun, 24 Aug 2014 15:49:53 + with message-id e1xla3f-0001bh...@franck.debian.org and subject line Bug#750082: fixed in pinball 0.3.1-13.2 has caused the Debian Bug report #750082, regarding pinball: FTBFS - Makefile:820: *** missing separator (did you mean TAB instead of 8 spaces?). 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.) -- 750082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pinball Version: 0.3.1-13.1 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. [...] Making all in src make[3]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-pinball/pinball-0.3.1/src' Makefile:820: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. make[3]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-pinball/pinball-0.3.1/src' Makefile:525: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-pinball/pinball-0.3.1' Makefile:398: recipe for target 'all' failed make[1]: *** [all] Error 2 The full build log is attached. Best, Michael pinball-build-log.txt.gz Description: application/gunzip pgpeVRiHtf1yQ.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: pinball Source-Version: 0.3.1-13.2 We believe that the bug you reported is fixed in the latest version of pinball, 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 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated pinball 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: Sat, 23 Aug 2014 14:16:37 +0200 Source: pinball Binary: pinball pinball-dev pinball-data Architecture: source amd64 all Version: 0.3.1-13.2 Distribution: unstable Urgency: medium Maintainer: Jochen Friedrich joc...@scram.de Changed-By: Markus Koschany a...@gambaru.de Description: pinball- Emilia Pinball Emulator pinball-data - Data files for the Emilia Pinball Emulator pinball-dev - Development files for the Emilia Pinball Emulator Closes: 736039 750082 Changes: pinball (0.3.1-13.2) unstable; urgency=medium . * Non-maintainer upload. * Build-depend on libtiff-dev instead of libtiff4-dev because the latter is going to disappear soon. (Closes: #736039) * Add missing-separators.patch. - Replace spaces with TABS in Makefiles and thus fix a FTBFS with newer versions of GNU Make which are less fault tolerant. Thanks to Michael Tautschnig for the report. (Closes: #750082) Checksums-Sha1: b477a50b72d7fbe501f899f69ef3540b77ce6a41 2079 pinball_0.3.1-13.2.dsc 7daf63a7b7e586ede2a6ffae3e53abd0e23fff22 6082982 pinball_0.3.1.orig.tar.gz 6311da7763241c1975f13b038cf8f4e3cfb89456 9508 pinball_0.3.1-13.2.debian.tar.xz 09559563aa27e7db829d71090d87df5e77a2a056 176494 pinball_0.3.1-13.2_amd64.deb bec52425010d9627bf4ae30064c6eb68d733ae28 255792 pinball-dev_0.3.1-13.2_amd64.deb 8caae597982fa9742fe95f6be36ade3de519b972 4368748 pinball-data_0.3.1-13.2_all.deb Checksums-Sha256: 39973599fa8474ae08cb464dd195c2c81a16cf94c045d4ab44f862dde87804a8 2079 pinball_0.3.1-13.2.dsc ba47989f7fb6e294faa95285563220c8b01c3dbb9aa1bc29828eb7e832855cb8 6082982 pinball_0.3.1.orig.tar.gz 3155b2a0e3bca9ec820f21cd96070e34f5f83c9ca7c7ced3a0da447e55b54465 9508 pinball_0.3.1-13.2.debian.tar.xz c31a9afd4d08f22f27415dca3127a741d0432f3c1be491622a093394e822b47b 176494 pinball_0.3.1-13.2_amd64.deb bbb5e5bd4e22d36a55652a9e9cfc42094c44bec1e78d180c87b114f2c499465e 255792 pinball-dev_0.3.1-13.2_amd64.deb de6951b95c4bef180754d5567d8f86de6e9ed6dea6c73acdb3ae7a274eeaa5cc 4368748 pinball-data_0.3.1-13.2_all.deb Files: b883219886e053ec25396b9e2a2cffdf 176494 games optional pinball_0.3.1-13.2_amd64.deb b610da6b47d52411760ae0cf7ffda42e 255792 games optional pinball-dev_0.3.1-13.2_amd64.deb 8f9308eb9bae327c8f40dbd3cea2150e 4368748 games optional pinball-data_0.3.1-13.2_all.deb
Bug#754761: marked as done (ruby-oj: FTBFS on many archs: armel armhf i386 kfreebsd-i386 powerpc)
Your message dated Sun, 24 Aug 2014 16:19:53 + with message-id e1xlawh-0007ax...@franck.debian.org and subject line Bug#754761: fixed in ruby-oj 2.10.1-1 has caused the Debian Bug report #754761, regarding ruby-oj: FTBFS on many archs: armel armhf i386 kfreebsd-i386 powerpc 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.) -- 754761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-oj Version: 2.9.6-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on various archs where it built successfully in the past. You'll find a summary page available here: https://buildd.debian.org/status/package.php?p=ruby-ojsuite=sid Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: ruby-oj Source-Version: 2.10.1-1 We believe that the bug you reported is fixed in the latest version of ruby-oj, 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. Caitlin Matos caitlin.ma...@zoho.com (supplier of updated ruby-oj 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: Mon, 18 Aug 2014 17:53:34 -0400 Source: ruby-oj Binary: ruby-oj Architecture: source amd64 Version: 2.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Caitlin Matos caitlin.ma...@zoho.com Description: ruby-oj- fast JSON parser and serializer for Ruby Closes: 754761 Changes: ruby-oj (2.10.1-1) unstable; urgency=medium . [ Caitlin Matos ] * Team upload * New upstream release * Versioned build dependency for ruby-minitest . [ Cédric Boutillier ] * Add 03_deactivate_test_io_string.patch to deactivate tests causing others to fail on some architectures (Closes: #754761) Checksums-Sha1: 77c9a6276376d57910c18cf442cf9906605a30a6 1651 ruby-oj_2.10.1-1.dsc 8d98c5997e627eddcc152b72afa6eca1627ece87 104656 ruby-oj_2.10.1.orig.tar.gz 2a599fc13f7816f723309a341e2d35273a32e574 3676 ruby-oj_2.10.1-1.debian.tar.xz 51e77fc5eb6c78b178df9d39b359f02f913f1508 76448 ruby-oj_2.10.1-1_amd64.deb Checksums-Sha256: e0f01109a512d9e2b26280dd0908d66104ac2508a4bb550599142e00bdd7632d 1651 ruby-oj_2.10.1-1.dsc 7903713c825fd4a1e9f510a1adee8017cc84a28d55257fc090f2c35fca2b1307 104656 ruby-oj_2.10.1.orig.tar.gz 2802d92ef50625086fd1a940579376809ccc482757f79cebe67ed9a167a330b1 3676 ruby-oj_2.10.1-1.debian.tar.xz 23b28416be5b1f84a6ff045e831e5c3a28b59cdbe52bc6e490d9a8c3d880f321 76448 ruby-oj_2.10.1-1_amd64.deb Files: 36f4047dc14b88ca43b606e55fec73d6 76448 ruby optional ruby-oj_2.10.1-1_amd64.deb ab42b52ddb3c43d4e26f40b9abb4e37d 1651 ruby optional ruby-oj_2.10.1-1.dsc 020cf6f1268f992a10b5c8657f1d84e7 104656 ruby optional ruby-oj_2.10.1.orig.tar.gz b4f91f0d062789832a808f27440ad13e 3676 ruby optional ruby-oj_2.10.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJT+g1ZAAoJEImvgrc5zSF64Q8H/ApPGJVzXd+FiLTkdJxvZeVo 6aUQpYRONknK5UxhIiut4ftlxGt4KYvwjSjfMhIwgrE40rXVKcggV+kJsmrJRtwA fotruDi0b1ERV3xsHLrXdCRhMuOlBN0hWvipOY1U2+bbTp/yUHeDxv0KDRCYzI3o 9WvsrghigJAeqCa5GizGqRAI3rm1WVTdiu7OT4uS0XNyFKkzZf286Y16X8RpvqzK 5pvCIeMlwUFZpPnSEh7DN2A9le7quAolTNrAWNSDG5Wsff62KyEpJnCd5amYYqHR 4ccFXy5BsaqCLcddUsWZr2oFHQCfd9D5inB6AdACky/OHlKKyvUCDak4x9e5SoI= =QbRW -END PGP SIGNATUREEnd Message---
Bug#759129: nanomsg ftbfs in current unstable (i386, and other architectures)
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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758972: Mojarra update 2.2.8
On Sat, Aug 23, 2014 at 07:22:37PM +0200, Markus Koschany wrote: I will investigate whether an update to 2.2.8 can resolve the issues with mojarra. I'll report back as soon as it's done. I'm pretty sure 2.2.8 would resolve almost all the outstaing issues. However, after inspecting 2.2.8 I found it B-D on Java EE 6 APIs (e.g. javax.enterprise.context) and AFAICT they are not available in Debian yet. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#759100: marked as done (openjade FTBFS now)
Your message dated Sun, 24 Aug 2014 17:34:25 + with message-id e1xlbgp-se...@franck.debian.org and subject line Bug#759100: fixed in openjade 1.4devel1-21.1 has caused the Debian Bug report #759100, regarding openjade FTBFS now 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.) -- 759100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: openjade Version: 1.4devel1-21 Severity: serious Hi, while bootstrapping on ppc64el I found that openjade FTBFS now. I retried on the amd64 porterbox, and the result is as follows. Andi g++ -g --pipe -fpermissive -O2 -o .libs/openjade jade.o SgmlFOTBuilder.o RtfFOTBuilder.o HtmlFOTBuilder.o TeXFOTBuilder.o TransformFOTBuilder.o MifFOTBuilder.o MessageModule.o ../style/.libs/libostyle.so ../spgrove/.libs/libospgrove.so ../grove/.libs/libogrove.so -losp -lpthread creating openjade make[4]: Leaving directory '/home/aba/openjade-1.4devel1/jade' make[3]: Leaving directory '/home/aba/openjade-1.4devel1/jade' Making all in intl make[3]: Entering directory '/home/aba/openjade-1.4devel1/intl' Makefile:210: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. make[3]: Leaving directory '/home/aba/openjade-1.4devel1/intl' Makefile:308: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/aba/openjade-1.4devel1' Makefile:212: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/aba/openjade-1.4devel1' debian/rules:116: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: openjade Source-Version: 1.4devel1-21.1 We believe that the bug you reported is fixed in the latest version of openjade, 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. Andreas Barth a...@ayous.org (supplier of updated openjade 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: Sun, 24 Aug 2014 12:47:55 + Source: openjade Binary: openjade libostyle1c2 libostyle-dev Architecture: source ppc64el Version: 1.4devel1-21.1 Distribution: unstable Urgency: medium Maintainer: Neil Roeth n...@debian.org Changed-By: Andreas Barth a...@ayous.org Description: libostyle-dev - OpenJade libraries, developer support libostyle1c2 - Runtime libraries for OpenJade openjade - Implementation of the DSSSL language Closes: 748626 759100 Changes: openjade (1.4devel1-21.1) unstable; urgency=medium . [ Wookey ] * Add acinclude.m4 macro to find correct intlh header whether or not gettext is present (Closes: #748626, #759100) * Update rules file to use dh-autoreconf rather than manual commands and update configure.in enough for autoreconf to work . [ Andreas Barth ] * Non-maintainer upload. * Update configure.in to set PACKAGE_TARNAME to mixed case. * Create po/Makevars with copyright hint to individual pot files and DOMAIN=jade. Checksums-Sha1: 77eddada67d366b56525f921f4681fb7c3421793 1295 openjade_1.4devel1-21.1.dsc 4abba80afa206fb6e60c3ce14f17733c5905e266 253102 openjade_1.4devel1-21.1.diff.gz 890df73aa88b5a68197e7fe18ed676ba41ca438b 263280 openjade_1.4devel1-21.1_ppc64el.deb 6adf7e18acc96ac0787584460008a19b5d1eda17 620992 libostyle1c2_1.4devel1-21.1_ppc64el.deb 805093327f52bfe6e849c5250901edaef061da8f 660306 libostyle-dev_1.4devel1-21.1_ppc64el.deb Checksums-Sha256: deed8acce8e6cbb2ef09526b51f671320024eab82036a879af6083e49d869cf7 1295 openjade_1.4devel1-21.1.dsc 99370fd9def91a3ab6c69d18f6f225965716928bf271aed732048690c86c7618 253102 openjade_1.4devel1-21.1.diff.gz 83ca86679d19c060f157c27c5f7917dc91941d23e996aa21c45511d054b70262 263280 openjade_1.4devel1-21.1_ppc64el.deb ed99a3d805e467c10c8500390c928a9148a3f222509e3e2dfc5b097ad5d7db4f 620992 libostyle1c2_1.4devel1-21.1_ppc64el.deb bf659fa625a8a4dc37afbf15988e9a14a19d55323bb7d21afa18c237182849ec 660306 libostyle-dev_1.4devel1-21.1_ppc64el.deb
Processed: tagging 753921
Processing commands for cont...@bugs.debian.org: # Don't need suite tags where version-tracking dtrt tags 753921 - wheezy Bug #753921 [src:getfem++] getfem++: Bogus patch disallows dpkg-source unpack Removed tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 753921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753921 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#758687: uninstallable: xorg-server 1.16 transition
Steven Chamberlain ste...@pyro.eu.org writes: On 20/08/14 03:59, Cyril Brulebois wrote: your package needs an update for the transition to xorg-server 1.16 which happened in July. This is something any uploading DD can help with. Please could someone build and upload xserver-xorg-video-nv 1:2.1.20-3 on kfreebsd-amd64 and kfreebsd-i386, from our packaging SVN r5427: svn://anonscm.debian.org/glibc-bsd/trunk/xserver-xorg-video-nv/ Done just now! I build-tested it myself, and Petr was able to test it on real hardware: http://lists.debian.org/alpine.lnx.2.00.1407172103500.15...@contest.felk.cvut.cz Alright I don't have any nvidia but as Petr has tested it :-) It also adds the XS-Autobuild flag, which allows binNMUs to be automatic in future. Jep seen. Guess it still also needs to mail [0] but I'm following up on that. Christoph [0] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd pgpFZOdGcI9tS.pgp Description: PGP signature
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Sun, Aug 24, 2014 at 08:05:45PM +0200, Bastian Blank wrote:
On Fri, Aug 22, 2014 at 07:21:31PM -0400, Stephen Powell wrote:
32ea: a7 f4 00 01 j 32ec
sclp_wait_for_int+0x84
32ee: 07 07 nopr%r7
gcc 4.9 decides that this must never happen and adds a trap in this
location, so this a is deliberate way to stop the process.
I found the culprit: The tree-isolate-paths pass in gcc 4.9. If I
disable this pass I get:
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
32d6: e3 20 d0 00 00 04 lg %r2,0(%r13)
32dc: a7 39 01 b0 lghi%r3,432
32e0: c0 e5 ff ff fb b8 brasl %r14,2a50 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004U)
32e6: 48 10 00 86 lh %r1,134
32ea: bd 13 d0 0a clm %r1,3,10(%r13)
32ee: a7 84 00 0c je 3306 sclp_wait_for_int+0x9e
return ETIMEOUT;
} while (S390_lowcore.ext_int_code != 0x2401U);
32f2: 48 10 00 86 lh %r1,134
32f6: bd 13 d0 08 clm %r1,3,8(%r13)
32fa: a7 74 ff ee jne 32d6 sclp_wait_for_int+0x6e
return 0;
32fe: a7 28 00 00 lhi %r2,0
3302: a7 f4 00 04 j 330a sclp_wait_for_int+0xa2
This pass seems to declare the null-pointer-access as invalid.
Bastian
--
In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, Wolf in the Fold, stardate 3615.4
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Sun, Aug 24, 2014 at 08:34:45PM +0200, Bastian Blank wrote: On Sun, Aug 24, 2014 at 08:05:45PM +0200, Bastian Blank wrote: On Fri, Aug 22, 2014 at 07:21:31PM -0400, Stephen Powell wrote: 32ea: a7 f4 00 01 j 32ec sclp_wait_for_int+0x84 32ee: 07 07 nopr%r7 gcc 4.9 decides that this must never happen and adds a trap in this location, so this a is deliberate way to stop the process. I found the culprit: The tree-isolate-paths pass in gcc 4.9. If I disable this pass I get: And -fno-delete-null-pointer-checks seems to be the correct option. Bastian -- There are some things worth dying for. -- Kirk, Errand of Mercy, stardate 3201.7 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748425: marked as done (needs update for new iptables-persistent)
Your message dated Sun, 24 Aug 2014 18:49:33 + with message-id e1xlcr7-0001sb...@franck.debian.org and subject line Bug#748425: fixed in puppet-module-puppetlabs-firewall 1.1.3-1 has caused the Debian Bug report #748425, regarding needs update for new iptables-persistent 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.) -- 748425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: puppet-module-puppetlabs-firewall Version: 1.0.2-1 Severity: grave With version 1.0.1 of iptables-persistent, this module fails with the error: Error: /Stage[main]/Firewall::Linux::Debian/Service[iptables-persistent]: Could not evaluate: Could not find init script for 'iptables-persistent' It looks like the latest version converts iptables-persistent to a set of modules for netfilter-persistent, and has renamed the init configuration to netfilters-persistent. The Puppet module will need a corresponding update. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/1 CPU core) 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 puppet-module-puppetlabs-firewall depends on: ii puppet-common 3.5.1-1 puppet-module-puppetlabs-firewall recommends no packages. Versions of packages puppet-module-puppetlabs-firewall suggests: pn ebtables none ii iptables 1.4.21-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: puppet-module-puppetlabs-firewall Source-Version: 1.1.3-1 We believe that the bug you reported is fixed in the latest version of puppet-module-puppetlabs-firewall, 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 748...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Russ Allbery r...@debian.org (supplier of updated puppet-module-puppetlabs-firewall 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: Sat, 23 Aug 2014 23:36:53 -0700 Source: puppet-module-puppetlabs-firewall Binary: puppet-module-puppetlabs-firewall Architecture: source all Version: 1.1.3-1 Distribution: unstable Urgency: medium Maintainer: Puppet Package Maintainers pkg-puppet-de...@lists.alioth.debian.org Changed-By: Russ Allbery r...@debian.org Description: puppet-module-puppetlabs-firewall - Puppet module for Firewall management Closes: 748425 Changes: puppet-module-puppetlabs-firewall (1.1.3-1) unstable; urgency=medium . * New upstream release. - Add support for connlimit and connmark. - Add mask as a parameter. - Add systemd support for RHEL7. * Add a Debian patch to support the change of init script name to netfilter-persistent introduced in iptables-persistent 1.0. (Closes: #748425) * No longer install Modulefile, since this has been dropped upstream. * Canonicalize the Vcs-Git URL. * Add myself to Uploaders. Checksums-Sha1: fbbba596a7630ee780366a48feac33e2d74c1665 1891 puppet-module-puppetlabs-firewall_1.1.3-1.dsc fb6917a96d5b4f56f13d10250ced1b20b423d296 63315 puppet-module-puppetlabs-firewall_1.1.3.orig.tar.gz dfc22956dab98eb5d95659a6a7fbb039d7aa3e8f 3344 puppet-module-puppetlabs-firewall_1.1.3-1.debian.tar.xz 7c7ba44cd79f8660d3571d714ddff600910f252e 34734 puppet-module-puppetlabs-firewall_1.1.3-1_all.deb Checksums-Sha256: 57f21533286d909008a8333cf42efb6f201b0e7f505c915ca5e2cf5c7959cda9 1891 puppet-module-puppetlabs-firewall_1.1.3-1.dsc 8e23ef433458d231918dc9e70a1197d09bbeedcd9ec1c5b308c240de41b2c55a 63315 puppet-module-puppetlabs-firewall_1.1.3.orig.tar.gz 07144b742bff39f07caeddbcbd923baee4e035547127a409a53f511d30396a0f 3344 puppet-module-puppetlabs-firewall_1.1.3-1.debian.tar.xz 117efcb6a3ae4542b13616943e036e74301bcf5b3f0c96278d0b251636a462ed 34734 puppet-module-puppetlabs-firewall_1.1.3-1_all.deb Files: 0b95a8cb764bec46fa7cee4aea1de0ad 34734 admin optional puppet-module-puppetlabs-firewall_1.1.3-1_all.deb 80f8974d924691c8aa9fac0a409c3c8d 1891 admin optional
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Fri, Aug 22, 2014 at 07:21:31PM -0400, Stephen Powell wrote:
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
33d0: e3 20 d0 00 00 04 lg %r2,0(%r13)
33d6: a7 39 01 b0 lghi%r3,432
33da: c0 e5 ff ff fc f7 brasl %r14,2dc8 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
33e0: e3 10 00 86 00 91 llgh%r1,134
33e6: a7 1e 10 04 chi %r1,4100
33ea: a7 74 00 06 jne 33f6
sclp_wait_for_int+0x9a
33ee: a7 28 00 02 lhi %r2,2
33f2: a7 f4 00 08 j 3402
sclp_wait_for_int+0xa6
return ETIMEOUT;
} while (S390_lowcore.ext_int_code != 0x2401);
33f6: a7 1e 24 01 chi %r1,9217
33fa: a7 74 ff eb jne 33d0
sclp_wait_for_int+0x74
33fe: a7 28 00 00 lhi %r2,0
Would be interesting how the disassembly looks on your system.
Indeed. Here is what I got:
-
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
32d6: a7 39 01 b0 lghi%r3,432
32da: e3 20 d0 00 00 04 lg %r2,0(%r13)
32e0: c0 e5 ff ff fb b8 brasl %r14,2a50 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
32e6: 48 10 00 86 lh %r1,134
32ea: a7 f4 00 01 j 32ec sclp_wait_for_int+0x84
32ee: 07 07 nopr%r7
-
With gcc-4.8:
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
331e: e3 20 d0 00 00 04 lg %r2,0(%r13)
3324: a7 39 01 b0 lghi%r3,432
3328: c0 e5 ff ff fb ac brasl %r14,2a80 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
332e: e3 10 00 86 00 91 llgh%r1,134
3334: a7 1e 10 04 chi %r1,4100
3338: a7 84 00 0a je 334c sclp_wait_for_int+0x9c
return ETIMEOUT;
} while (S390_lowcore.ext_int_code != 0x2401);
333c: a7 1e 24 01 chi %r1,9217
3340: a7 74 ff ef jne 331e sclp_wait_for_int+0x6e
return 0;
3344: a7 28 00 00 lhi %r2,0
3348: a7 f4 00 04 j 3350 sclp_wait_for_int+0xa0
That does look much better for 3338, 3340, not really for 3348 (to 3350). It
does fix the issue at hand, but it's a band-aid at most. I installed the
package on wheezy (compiled on sid) and it booted...
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758115: marked as done (Disabled wait state X'32EE' on IPL of zIPL)
Your message dated Sun, 24 Aug 2014 19:04:57 + with message-id e1xld61-0004ep...@franck.debian.org and subject line Bug#758115: fixed in s390-tools 1.25.0-1 has caused the Debian Bug report #758115, regarding Disabled wait state X'32EE' on IPL of zIPL 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.) -- 758115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: s390-tools Version: 1.24.1-1 Severity: critical Justification: The entire system is unbootable After installing s390-tools version 1.24.1-1 and re-running zipl, a reboot of the system causes a disabled wait PSW to be loaded during boot, with a wait state code of X'32EE', prior to the zipl menu being written out. The system is unbootable. This may be related to the general brokenness of C on s390x in jessie/sid. -- .''`. Stephen Powell : :' : `. `'` `- ---End Message--- ---BeginMessage--- Source: s390-tools Source-Version: 1.25.0-1 We believe that the bug you reported is fixed in the latest version of s390-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 758...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern pk...@debian.org (supplier of updated s390-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: SHA256 Format: 1.8 Date: Sun, 24 Aug 2014 19:41:12 +0200 Source: s390-tools Binary: s390-tools s390-tools-udeb Architecture: source s390x Version: 1.25.0-1 Distribution: unstable Urgency: medium Maintainer: Debian S/390 Team debian-s...@lists.debian.org Changed-By: Philipp Kern pk...@debian.org Description: s390-tools - A set of fundamental utilities for Linux on S/390 s390-tools-udeb - A set of utilities for Linux on S/390 (udeb) Closes: 758115 Changes: s390-tools (1.25.0-1) unstable; urgency=medium . * New upstream release - Refreshed patches. - Dropped the backported zipl fix. - Build zipl's bootloader part with gcc-4.8 to sidestep miscompilation. (Closes: #758115) Checksums-Sha1: 2cf63859c2884dd448d67d308acf4cd104d60dd8 1679 s390-tools_1.25.0-1.dsc 02ead626175a5232f9b861f3586331e6415346da 641041 s390-tools_1.25.0.orig.tar.bz2 9e1bbd783b4508d8f18e8ecc0ed769d292d89231 12740 s390-tools_1.25.0-1.debian.tar.xz 71bf85d9473fa73a504292dd22f8a7a490abc48c 346542 s390-tools_1.25.0-1_s390x.deb 663e7877051dd766ae1e5e7fe1e5283e099151de 31304 s390-tools-udeb_1.25.0-1_s390x.udeb Checksums-Sha256: 9006e339cc43ea42500663fb5f4fe127585e3539671631ed6a87b05a9dad82eb 1679 s390-tools_1.25.0-1.dsc 3e17f10afa3d98ccee73abddb6f173ae6f87ea2ef622a86c09074db92416f357 641041 s390-tools_1.25.0.orig.tar.bz2 a2003898c9e247cf13e55f37cf2b37c1ba38d311a9c0186a450d9a357fb43bf8 12740 s390-tools_1.25.0-1.debian.tar.xz fe004d1735c268bbfe3cfb96ff5855cc19ed8fb3ee95d38c306d352ce30e2ab6 346542 s390-tools_1.25.0-1_s390x.deb ce64869f86ae4a42532a5dc62909657d5661a79e7b4d1b8eb90b7a1c55350f34 31304 s390-tools-udeb_1.25.0-1_s390x.udeb Files: 15426e02555f930fa815973446b51fc4 346542 admin important s390-tools_1.25.0-1_s390x.deb 3b21bdff45d4367a631e01833a295226 31304 debian-installer optional s390-tools-udeb_1.25.0-1_s390x.udeb 797d10a74233adb6040fba349a4dfe34 1679 admin important s390-tools_1.25.0-1.dsc 9a97bae58971d0c79fba49e1b4447f12 641041 admin important s390-tools_1.25.0.orig.tar.bz2 efd1e161215f77d57349f069ec3764b9 12740 admin important s390-tools_1.25.0-1.debian.tar.xz Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJT+jQnAAoJEERuJUU10Fbsf3oH/jbzIaPrMtxtDLYq32CUHoqn WgGjgV18z532Acv/8BKetFWZoOIHKcfkpzeg9wl2RvP7l7k1YhFpnCZw+j5AYgGM 03NICztezlk68qqk61XfwGfmoWwp9aNR4P3LgZfuWC7n8on79c4NYiMH5ETcGvnx aNb7UvkLaOIPADL3h3BRAUhlC8ErNs+9crcBc10FXmFu/aL8JPBf9Cy833mlm5ZD HmgojkjIwhyHeemON0srKDockaTyjllh91R0hNvQD59keU3jIPIwFaHSuB0goTje rjEx2sy4P31f84sn3EW32c3MvRBKcQtVDuOUDKEIKVu0lTBukBENJ+kOb5vbTtQ= =ndHC -END PGP SIGNATUREEnd Message---
Bug#756794: vsftpd: FTBFS on kfreebsd-*
Hello Steven, Am Donnerstag, den 21.08.2014, 14:56 +0100 schrieb Steven Chamberlain: [...] Hi, On 20/08/14 16:38, Jörg Frings-Fürst wrote: There are no changes at sysdeputil.c between vsftpd/3.0.2-14 and vsftpd/3.0.2-15. I see what happened: kfreebsd-kernel-headers introduced a new sys/capability.h which we did not have before. vsftpd will use it in preference to a dummyinc/sys/capability.h You can see in dummyinc/sys/capability.h that it would otherwise #undef VSF_SYSDEP_HAVE_LIBCAP. vsftpd expects sys/capability.h will define cap_t, but only libcap has that, our header does not. I'm not sure what's right/wrong here. libcap is a linux-any package currently but would conflict with this FreeBSD kernel header otherwise. (Why does libpcap put it in sys/?) Either way, we don't seem to have libcap on GNU/kFreeBSD, and quoting Ben Kaduk: It seems [libpcap] is the provider of the cap_t; there is no such concept in the base freebsd system. I think it is appropriate to add the attached, along with the other platform-specific configuration atop sysdeputil.c Regards, Many thanks for your work and the patch. I've added them into 3.0.2-16. CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#759146: [phatch] Phatch doesn't work with python-imaging and python-pil 2.5.1-x or 2.5.3-x
Package: phatch Version: 0.2.7.1-3 Severity: grave --- Please enter the report below this line. --- After upgrading to python-imaging 2.5.1-x or or 2.5.3-x and python-pil 2.5.1-x or or 2.5.3-x I got this message from Phatch when I try to process pictures: 'NoneType' object has no attribute 'mode' Traceback (most recent call last): File /usr/share/phatch/phatch/core/api.py, line 493, in get_photo photo = pil.Photo(info_file, info_not_file) File /usr/share/phatch/phatch/core/pil.py, line 471, in __init__ layer.image) File /usr/share/phatch/phatch/core/pil.py, line 175, in __init__ if image == None: File /usr/lib/python2.7/dist-packages/PIL/Image.py, line 576, in __eq__ a = (self.mode == other.mode) AttributeError: 'NoneType' object has no attribute 'mode' Downgrade to python-imaging 2.4.0-2 and python-pil 2.4.0-2 make Phatch work again. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstablehttp.debian.net --- Package information. --- Depends (Version) | Installed ==-+-== python:any (= 2.7.5-5~) | phatch-cli (= 0.2.7.1-3) | 0.2.7.1-3 xdg-utils | 1.1.0~rc1+git20111210-7.1 python-wxgtk2.8| 2.8.12.1+dfsg2-2 python-wxversion | 3.0.0.0+dfsg-4 Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== blender | inkscape| -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0
On Fri, 2014-08-22 at 05:26 +0200, Cyril Brulebois wrote: Ian Campbell i...@hellion.org.uk (2014-08-22): The Internet(tm) seems to think that __aeabi_unwind_cpp_pr0 comes from libunwind, but the wifi in this hotel is making it a rather slow job to figure out what might be depending on that and/or whether there is/should be a udeb for it, I'll try and investigate further though. Interesting that only the network-console flavour is affected Comparing netboot and network-console builds before the library reduction phase leads to an interesting diff, which I'm not attaching because I think that's not really needed, see below. (BTW: There's a similar symbol in the kernel but I'm going to assume the *.ko diff is totally irrelevant to the problem in mklibs…) Yes, I'm sure it is irrelevant. Letting netboot go through, and grepping for that symbol, there's no match in the resulting tree; on the contrary, network-console still gets some: | Binary file tmp/network-console/tree/lib/libcrypt.so.1-so-stripped matches | Binary file tmp/network-console/tree/lib/libcrypt.so.1-so matches | Binary file tmp/network-console/tree/lib/libc.so.6-so matches Interestingly, grepping for libcrypt.so in netboot shows no match, while network-console has: | Binary file tmp/network-console/tree/bin/gen-crypt matches | Binary file tmp/network-console/tree/lib/libcrypt.so.1-so-stripped matches | Binary file tmp/network-console/tree/lib/libcrypt.so.1-so matches | Binary file tmp/network-console/tree/usr/sbin/sshd matches See? Both gen-crypt and sshd are only in the network-console image, and apparently pulling libcrypt.so.1, which comes from libc: | libc6:armhf: /lib/arm-linux-gnueabihf/libcrypt.so.1 Also in the tree, nm -D shows that this libcrypt.so.1-so* have: | U __aeabi_unwind_cpp_pr0 which is likely what mklibs barfs about. Bottom line: FTBFS vs. non-FTBFS depending on image type is likely explained by the differences in binaries included in each image; Agreed. and that FTBFS was likely introduced by a toolchain update which mklibs doesn't exactly cope nicely with, yet. Possibly. One thing I'm confused about is that the symbol is apparently provided by libgcc_s.so.1 but that doesn't appears under tmp/network-console/ anywhere. But surely some other symbols from libgcc_s must be being used already. Running mklibs by hand in verbose mode AFAICT it is never even considering libgcc_s.so.1. Copying /lib/arm-linux-gnueabihf/libgcc_s.so.1 to tmp/network-console/tree/lib/ (which I'm sure is quite wrong...) doesn't work but it does cause mklibs to spit out some interesting debug: needed_symbols adding __aeabi_unwind_cpp_pr0, weak: False [...] present_symbols adding __aeabi_unwind_cpp_pr0@GCC_3.5@libgcc_s.so.1 [...] Exception: No library provides non-weak __aeabi_unwind_cpp_pr0 (the middle line is from calling mklibs-readelf --print-symbols-provided ./tmp/network-console/tree/lib/libgcc_s.so.1) Which made me wonder if the issue might be to do with symbol versioning somehow? For the record, I'm listing below where the symbol is referenced (T in libgcc_s.so.1, U elsewhere). Was it deliberate that this referenced the host (/lib etc) rather than the build tree? I've timed out for now, but I'll continue prodding as I have the chance... Ian. -- 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#690282: Status of bug #690282
Processing commands for cont...@bugs.debian.org: reassign 690282 ruby-pgplot Bug #690282 [buildd.debian.org] building of contrib package with non-free build-dependencies not supported Bug reassigned from package 'buildd.debian.org' to 'ruby-pgplot'. Ignoring request to alter found versions of bug #690282 to the same values previously set Ignoring request to alter fixed versions of bug #690282 to the same values previously set severity 690282 serious Bug #690282 [ruby-pgplot] building of contrib package with non-free build-dependencies not supported Severity set to 'serious' from 'important' retitle 690282 ruby-pgplot fails to build within Debian (build-depends on non-free) Bug #690282 [ruby-pgplot] building of contrib package with non-free build-dependencies not supported Changed Bug title to 'ruby-pgplot fails to build within Debian (build-depends on non-free)' from 'building of contrib package with non-free build-dependencies not supported' thanks Stopping processing here. Please contact me if you need assistance. -- 690282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690282 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#748614: [libkolab0] looses information about birthdays
Processing commands for cont...@bugs.debian.org: reassign 748614 libkolab0 0.5.2-1 Bug #748614 [libkolabxml1] [libkolabxml0] looses information about birthdays Bug reassigned from package 'libkolabxml1' to 'libkolab0'. No longer marked as found in versions 0.8.4-5.1. Ignoring request to alter fixed versions of bug #748614 to the same values previously set Bug #748614 [libkolab0] [libkolabxml0] looses information about birthdays Marked as found in versions libkolab/0.5.2-1. reassign 732213 libkolab0 0.5.2-1 Bug #732213 [kdepim-runtime] [kdepim-runtime] Kolab agent looses information about birthdays Bug reassigned from package 'kdepim-runtime' to 'libkolab0'. No longer marked as found in versions kdepim-runtime/4:4.11.3-1. Ignoring request to alter fixed versions of bug #732213 to the same values previously set Bug #732213 [libkolab0] [kdepim-runtime] Kolab agent looses information about birthdays Marked as found in versions libkolab/0.5.2-1. forcemerge 748614 732213 Bug #748614 [libkolab0] [libkolabxml0] looses information about birthdays Bug #732213 [libkolab0] [kdepim-runtime] Kolab agent looses information about birthdays Unset Bug forwarded-to-address Bug #748614 [libkolab0] [libkolabxml0] looses information about birthdays Added tag(s) upstream. Merged 732213 748614 retitle 748614 [libkolab0] looses information about birthdays Bug #748614 [libkolab0] [libkolabxml0] looses information about birthdays Bug #732213 [libkolab0] [kdepim-runtime] Kolab agent looses information about birthdays Changed Bug title to '[libkolab0] looses information about birthdays' from '[libkolabxml0] looses information about birthdays' Changed Bug title to '[libkolab0] looses information about birthdays' from '[kdepim-runtime] Kolab agent looses information about birthdays' tags 748614 + patch upstream Bug #748614 [libkolab0] [libkolab0] looses information about birthdays Bug #732213 [libkolab0] [libkolab0] looses information about birthdays Added tag(s) patch. Added tag(s) patch. forwarded 748614 https://issues.kolab.org/show_bug.cgi?id=2739 Bug #748614 [libkolab0] [libkolab0] looses information about birthdays Bug #732213 [libkolab0] [libkolab0] looses information about birthdays Set Bug forwarded-to-address to 'https://issues.kolab.org/show_bug.cgi?id=2739'. Set Bug forwarded-to-address to 'https://issues.kolab.org/show_bug.cgi?id=2739'. thanks Stopping processing here. Please contact me if you need assistance. -- 732213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732213 748614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748614 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#732213: Bug#748614: [libkolab0] looses information about birthdays
reassign 748614 libkolab0 0.5.2-1
reassign 732213 libkolab0 0.5.2-1
forcemerge 748614 732213
retitle 748614 [libkolab0] looses information about birthdays
tags 748614 + patch upstream
forwarded 748614 https://issues.kolab.org/show_bug.cgi?id=2739
thanks
Hi,
the problem of the unsaved kaddressbook date-values doesn't seem to be in
libkolabxml1 or kdepim-runtime but in libkolab0. I've just created a patch to
fix it for me. Maybe this patch or a variation of it could be included as part
of the next libkolab upload. Please also include it in the upstream bug #2739.
Kind regards,
SvenFrom a90b7696d6e21d17d4dbe1225a2671704db92014 Mon Sep 17 00:00:00 2001
From: Sven Eckelmann s...@narfation.org
Date: Sun, 24 Aug 2014 22:14:20 +0200
Subject: [PATCH] Allow KDateTime with only valid date
The cDateTime class of libkolab returns true on .isValid() for an object with
only a valid date. But KDateTime and QDateTime only return true when both date
and time are valid. Still the conversion code relies on the fact that
KDateTime::isValid() would return true when date or date+time is true.
The code handling the conversion from/to KDateTime has to handle this
difference. Otherwise the conversion of Date-only value like KABC birthday or
anniversary would fail and therefore cause data loss.
---
conversion/commonconversion.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/conversion/commonconversion.cpp b/conversion/commonconversion.cpp
index 7accd22..09fc04a 100644
--- a/conversion/commonconversion.cpp
+++ b/conversion/commonconversion.cpp
@@ -67,13 +67,13 @@ KDateTime toDate(const Kolab::cDateTime dt)
date.setTimeSpec(getTimeSpec(dt.isUTC(), dt.timezone()));
}
Q_ASSERT(date.timeSpec().isValid());
-Q_ASSERT(date.isValid());
+Q_ASSERT(date.isValid() || date.date().isValid());
return date;
}
cDateTime fromDate(const KDateTime dt)
{
-if (!dt.isValid()) {
+if (!dt.isValid() !dt.date().isValid()) {
// qDebug() invalid datetime converted;
return cDateTime();
}
--
2.1.0
Bug#724837: marked as done (apt-xapian-index: unsafe polkit usage)
Your message dated Sun, 24 Aug 2014 21:19:25 +
with message-id e1xlfc9-0004wk...@franck.debian.org
and subject line Bug#724837: fixed in apt-xapian-index 0.47
has caused the Debian Bug report #724837,
regarding apt-xapian-index: unsafe polkit usage
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.)
--
724837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: apt-xapian-index
Severity: grave
Tags: security patch
Hi,
the following vulnerability was published for apt-xapian-index.
CVE-2013-1064[0]: (from Ubuntu USN)
| It was discovered that apt-xapian-index was using polkit in an unsafe
| manner. A local attacker could possibly use this issue to bypass intended
| polkit authorizations.
The patch from Ubuntu is attached.
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-2013-1064
http://security-tracker.debian.org/tracker/CVE-2013-1064
Please adjust the affected versions in the BTS as needed.
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
Description: fix possible privilege escalation via policykit UID lookup race.
Author: Marc Deslauriers marc.deslauri...@canonical.com
Index: apt-xapian-index-0.45ubuntu2/update-apt-xapian-index-dbus
===
--- apt-xapian-index-0.45ubuntu2.orig/update-apt-xapian-index-dbus 2012-10-31 09:07:53.0 -0400
+++ apt-xapian-index-0.45ubuntu2/update-apt-xapian-index-dbus 2013-09-13 14:41:36.564345788 -0400
@@ -34,15 +34,8 @@
/org/freedesktop/PolicyKit1/Authority,
org.freedesktop.PolicyKit1.Authority)
policykit = dbus.Interface(obj, org.freedesktop.PolicyKit1.Authority)
-info = dbus.Interface(connection.get_object('org.freedesktop.DBus',
- '/org/freedesktop/DBus/Bus',
- False),
- 'org.freedesktop.DBus')
-pid = info.GetConnectionUnixProcessID(sender)
-subject = ('unix-process',
- { 'pid' : dbus.UInt32(pid, variant_level=1),
- 'start-time' : dbus.UInt64(0, variant_level=1),
- }
+subject = ('system-bus-name',
+ { 'name': dbus.String(sender, variant_level = 1) }
)
details = { '' : '' }
flags = dbus.UInt32(1) # AllowUserInteraction = 0x0001
pgpBJWT7cCCSC.pgp
Description: PGP signature
---End Message---
---BeginMessage---
Source: apt-xapian-index
Source-Version: 0.47
We believe that the bug you reported is fixed in the latest version of
apt-xapian-index, 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 724...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Enrico Zini enr...@debian.org (supplier of updated apt-xapian-index 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: Sun, 24 Aug 2014 10:44:58 -0700
Source: apt-xapian-index
Binary: apt-xapian-index
Architecture: source all
Version: 0.47
Distribution: unstable
Urgency: low
Maintainer: Enrico Zini enr...@debian.org
Changed-By: Enrico Zini enr...@debian.org
Description:
apt-xapian-index - maintenance and search tools for a Xapian index of Debian
package
Closes: 719940 724837 736500
Changes:
apt-xapian-index (0.47) unstable; urgency=low
.
[ Enrico Zini ]
* s/UNRELEASED/unstable/ in 0.46 changelog. Closes: #719940
* Removed dbus support files, not needed anymore since software-center has
been removed from sid and testing. Closes: #724837
* Ported to dh-python2
* Updated Standards-Version, no changes required.
.
[ Elena Grandi ]
* Use defaults when values file is broken. Closes: #736500
Checksums-Sha1:
09a22df29a4c04bfc0865950f7a60e099082aa8e 1847 apt-xapian-index_0.47.dsc
f3a2dae68258626b1d936f76a6da5a75fd6b70e2 55515
Bug#736500: marked as done ([apt-xapian-index] fails on update)
Your message dated Sun, 24 Aug 2014 21:19:25 + with message-id e1xlfc9-0004wq...@franck.debian.org and subject line Bug#736500: fixed in apt-xapian-index 0.47 has caused the Debian Bug report #736500, regarding [apt-xapian-index] fails on update 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.) -- 736500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt-xapian-index Version: 0.46 Severity: serious --- Please enter the report below this line. --- Hi, it's my first Debian bugreport! I've just installed fresh Debian Testing. After normal installation I've just installed apt-xapian-index for fast search in Synaptic and it's recommends, but it fails instead of working. Here is log: dima@kali:~$ uname -a Linux kali 3.12-1-686-pae #1 SMP Debian 3.12.6-2 (2013-12-29) i686 GNU/Linux dima@kali:~$ sudo update-apt-xapian-index [sudo] password for dima: Traceback (most recent call last): File /usr/sbin/update-apt-xapian-index, line 97, in module if not indexer.setupIndexing(force=opts.force, system=opts.pkgfile is None): File /usr/lib/pymodules/python2.7/axi/indexer.py, line 507, in setupIndexing values_seq = max(self.values.values()) + 1 ValueError: max() arg is an empty sequence dima@kali:~$ I didn't modify any system's file or something like this, so this must be very reproducible. Thanks in advance ^_^ --- System information. --- Architecture: i386 Kernel: Linux 3.12-1-686-pae Debian Release: jessie/sid 500 testing-updates ftp.debian.chuvsu.ru 500 testing security.debian.org 500 testing ftp.debian.chuvsu.ru 100 jessie-backports ftp.debian.chuvsu.ru --- Package information. --- Depends(Version) | Installed -+-== python (= 2.4) | 2.7.5-5 python-xapian (= 1.0.2) | 1.2.16-2 python-apt (= 0.7.93.2) | 0.9.1 python-debian(= 0.1.14) | 0.1.21+nmu2 python-support (= 0.90.0) | 1.0.15 Package's Recommends field is empty. Suggests (Version) | Installed ===-+-=== app-install-data| 2012.06.16.1 python-xdg | 0.25-3 ---End Message--- ---BeginMessage--- Source: apt-xapian-index Source-Version: 0.47 We believe that the bug you reported is fixed in the latest version of apt-xapian-index, 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 736...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini enr...@debian.org (supplier of updated apt-xapian-index 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: Sun, 24 Aug 2014 10:44:58 -0700 Source: apt-xapian-index Binary: apt-xapian-index Architecture: source all Version: 0.47 Distribution: unstable Urgency: low Maintainer: Enrico Zini enr...@debian.org Changed-By: Enrico Zini enr...@debian.org Description: apt-xapian-index - maintenance and search tools for a Xapian index of Debian package Closes: 719940 724837 736500 Changes: apt-xapian-index (0.47) unstable; urgency=low . [ Enrico Zini ] * s/UNRELEASED/unstable/ in 0.46 changelog. Closes: #719940 * Removed dbus support files, not needed anymore since software-center has been removed from sid and testing. Closes: #724837 * Ported to dh-python2 * Updated Standards-Version, no changes required. . [ Elena Grandi ] * Use defaults when values file is broken. Closes: #736500 Checksums-Sha1: 09a22df29a4c04bfc0865950f7a60e099082aa8e 1847 apt-xapian-index_0.47.dsc f3a2dae68258626b1d936f76a6da5a75fd6b70e2 55515 apt-xapian-index_0.47.tar.gz fdaad69820231206c1d5d27694f9288b1c362f27 58528 apt-xapian-index_0.47_all.deb Checksums-Sha256: b5057a482275df69272f66ec5e580ad25914ebf5c1e505a69485e3b9b848bb91 1847 apt-xapian-index_0.47.dsc 382c5910c3ce5b0c1f7de913263cd0197471c1d0387b091b1ab671f6a78d5de5 55515 apt-xapian-index_0.47.tar.gz 0019be55259cb9226beeb313e71bae379e2bb206c4b2041724c23b9388493518 58528 apt-xapian-index_0.47_all.deb Files: 823dc58302f4c83001159ba017affb36 58528 admin
Processed: severity of 758506 is grave, tagging 758506, fixed 758506 in 2013.09.15-1
Processing commands for cont...@bugs.debian.org: severity 758506 grave Bug #758506 [pianobar] Fix for TLS read/handshake error Severity set to 'grave' from 'normal' tags 758506 + confirmed Bug #758506 [pianobar] Fix for TLS read/handshake error Added tag(s) confirmed. fixed 758506 2013.09.15-1 Bug #758506 [pianobar] Fix for TLS read/handshake error Marked as fixed in versions pianobar/2013.09.15-1. thanks Stopping processing here. Please contact me if you need assistance. -- 758506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758506 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#759129: nanomsg ftbfs in current unstable (i386, and other architectures)
On Sun, 24 Aug 2014 18:34:17 +0200 Matthias Klose d...@debian.org wrote: PASS: tests/iovec ./test-driver: line 107: 14170 Aborted $@ $log_file 21 FAIL: tests/msg PASS: tests/inproc_shutdown Yeah, unfortunately, upstream's test suite is really buggy. I've already had to disable one of the tests because it has a really severe race condition in it that causes it to FTBFS about 50% of the time. It doesn't surprise me that there are transient failures in some of the other tests. That one I haven't seen, but. As a temporary solution, I'll disable this problematic test. If we still see problems in other places, we'll have to disable the tests altogether. It's not something that I particularly like doing, but if the problems with the test suite run that deep, I don't see much of a choice. Sincerely, -- Harlan Lieberman-Berg ~hlieberman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 758506 in 2012.05.06-2, found 758506 in 2010.11.06-1+squeeze2
Processing commands for cont...@bugs.debian.org: found 758506 2012.05.06-2 Bug #758506 [pianobar] Fix for TLS read/handshake error Marked as found in versions pianobar/2012.05.06-2. found 758506 2010.11.06-1+squeeze2 Bug #758506 [pianobar] Fix for TLS read/handshake error Marked as found in versions pianobar/2010.11.06-1+squeeze2. thanks Stopping processing here. Please contact me if you need assistance. -- 758506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758506 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#755705: cyrus-imapd-2.4: still not binNMU safe
Control: tags -1 patch On Sun, Aug 24, 2014 at 13:39:13 +0200, Ivo De Decker wrote: Hi, On Sun, Aug 24, 2014 at 01:57:51AM +0200, Ivo De Decker wrote: The problem isn't solved yet: the transitional packages cyrus-admin-2.4, cyrus-dev-2.4 and libcyrus-imap-perl24 are arch all, but they have a strict versioned depend on cyrus-common, which is arch: any, and has a different version after a binnmu. I guess the misc::depends is not necessary for the transitional packages. This is also the case for the other transitional packages. How about this: diff --git a/debian/changelog b/debian/changelog index aaef857..900d8fc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +cyrus-imapd-2.4 (2.4.17+caldav~beta10-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Link arch:all packages doc directories to cyrus-common-2.4 instead of +cyrus-common, because the latter is arch:any and that breaks binNMUs +(closes: #755705) + + -- Julien Cristau jcris...@debian.org Sun, 24 Aug 2014 15:11:46 -0700 + cyrus-imapd-2.4 (2.4.17+caldav~beta10-4) unstable; urgency=high * Remove obsolete cyrus-admin, cyrus-clients and libcyrus-imap-perl diff --git a/debian/rules b/debian/rules index 253d19f..128ff61 100755 --- a/debian/rules +++ b/debian/rules @@ -229,7 +229,7 @@ override_dh_installdocs: dh_installdocs \ -p cyrus-common -p cyrus-doc -p cyrus-clients \ -p cyrus-admin -p libcyrus-imap-perl - dh_installdocs --remaining-packages --link-doc=cyrus-common + dh_installdocs --remaining-packages --link-doc=cyrus-common-2.4 override_dh_installinit: dh_installinit -p cyrus-common --name=cyrus-imapd I'll upload to delayed/2 in a little bit, feel free to reschedule or cancel it. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#755705: cyrus-imapd-2.4: still not binNMU safe
Processing control commands: tags -1 patch Bug #755705 [src:cyrus-imapd-2.4] cyrus-imapd-2.4: not binNMU safe Added tag(s) patch. -- 755705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755705 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: marked as done (kde-runtime: openssl license exception needed)
Your message dated Sun, 24 Aug 2014 22:19:21 + with message-id e1xlg89-0005n3...@franck.debian.org and subject line Bug#750867: fixed in kde-runtime 4:4.14.0-1 has caused the Debian Bug report #750867, regarding kde-runtime: openssl license exception needed 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.) -- 750867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kde-runtime Version: 4:4.13.1-1 Severity: serious Tags: sid jessie Hi, The file /usr/lib/kde4/kio_sftp.so links against libssh which in turn links against openssl. Since the sftp code whichs links to libssh is licensed under the GPL, it needs a license exception to allow the linking. Alternatively you could prod bug #676650 which would provide an alternate libssh built against gnutls. See https://lists.debian.org/debian-legal/2004/05/msg00595.html James -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-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 ---End Message--- ---BeginMessage--- Source: kde-runtime Source-Version: 4:4.14.0-1 We believe that the bug you reported is fixed in the latest version of kde-runtime, 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 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated kde-runtime 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: Sun, 24 Aug 2014 23:26:40 +0200 Source: kde-runtime Binary: kde-runtime kdebase-runtime kde-runtime-data khelpcenter4 plasma-scriptengine-javascript kde-runtime-dbg kdebase-runtime-dbg Architecture: source amd64 all Version: 4:4.14.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Maximiliano Curia m...@debian.org Description: kde-runtime - runtime components from the official KDE release kde-runtime-data - shared data files for the KDE base runtime module kde-runtime-dbg - debugging symbols for KDE base runtime module kdebase-runtime - Transitional package for the KDE runtime components kdebase-runtime-dbg - transitional package for kde-runtime-dbg khelpcenter4 - help center plasma-scriptengine-javascript - JavaScript script engine for Plasma Closes: 750867 Changes: kde-runtime (4:4.14.0-1) unstable; urgency=medium . * Disable libssh build-dep, due to openssl license incompatibility. (Closes: #750867) * Update install files. * New upstream release. Checksums-Sha1: f45c40f2bb5e5e401ab297553868be49bff939e3 3293 kde-runtime_4.14.0-1.dsc 3847a9e6a66e4e724cff9230ff564c900243d4cd 7864060 kde-runtime_4.14.0.orig.tar.xz 75d8a380cba52c69a94febd92237815a0eb2aa59 29488 kde-runtime_4.14.0-1.debian.tar.xz 96f671859613b10f01c03341360cecb3d9326003 1847692 kde-runtime_4.14.0-1_amd64.deb 6e4ae32fbd6a0ed7e6c7656b6404907f84e8b652 19454 kdebase-runtime_4.14.0-1_all.deb 054007e84dce22a0c33da11d3cf7ac31239fe53d 6939314 kde-runtime-data_4.14.0-1_all.deb 27ae5651337f6ce7737b469629e7f284a3dbdb35 339340 khelpcenter4_4.14.0-1_amd64.deb 17b2965df49793505fdc04f75acc138de78179fa 404202 plasma-scriptengine-javascript_4.14.0-1_amd64.deb 035af1193ea890ebd66e7de99a60ad5d71a36d95 35595628 kde-runtime-dbg_4.14.0-1_amd64.deb 25c57f52a44e2e8930afc3a0329687cad0af4c16 19198 kdebase-runtime-dbg_4.14.0-1_all.deb Checksums-Sha256: 26e8e1c00d2358329982893456957a55476e033d88f097fbd2d3a5e41c5a0afa 3293 kde-runtime_4.14.0-1.dsc 3c3c20525b7be7b5d7babc1c8bf75e51217b1b7a7312bbf3a8b7a78800858763 7864060 kde-runtime_4.14.0.orig.tar.xz 9ed6fb59c6e6c25b85fb88aa063ef8e790748b27eb4073d2e1e245939474b484 29488 kde-runtime_4.14.0-1.debian.tar.xz dbf65af813693459b281da1d5ceb6e8247927208a8b94eef0dfdfd1b176540c3 1847692 kde-runtime_4.14.0-1_amd64.deb 53b262f349e21f9dc8269251a35b6c025f3c587d92c62c1a04a0958db7db8745 19454
Bug#725686: marked as done (dirdiff: calls /usr/bin/wish and depends on tk8.5)
Your message dated Sun, 24 Aug 2014 22:18:43 + with message-id e1xlg7x-0005e9...@franck.debian.org and subject line Bug#725686: fixed in dirdiff 2.1-6 has caused the Debian Bug report #725686, regarding dirdiff: calls /usr/bin/wish and depends on tk8.5 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.) -- 725686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dirdiff Version: 2.1-5 Severity: normal Dear Maintainer, We plan to drop alternatives for /usr/bin/wish from tk8.5 (only the tk package will provide symlink /usr/bin/wish) before jessie release. In your dirdiff package the /usr/bin/dirdiff script calls /usr/bin/wish, so it will stop working after the change in tk8.5. I see two ways of fixing this: either replace /usr/bin/wish by /usr/bin/wish8.5 and use tk8.5 in dependencies, or retain /usr/bin/wish and use simple tk in tependencies. In the latter case, please, test you script using tk package from experimental, as it pulls tk8.6 package as a default (8.6 as a default is planned for jessie too). -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: dirdiff Source-Version: 2.1-6 We believe that the bug you reported is fixed in the latest version of dirdiff, 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 725...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luciano Bello luci...@debian.org (supplier of updated dirdiff 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: Sun, 24 Aug 2014 19:16:04 +0200 Source: dirdiff Binary: dirdiff Architecture: source amd64 Version: 2.1-6 Distribution: unstable Urgency: high Maintainer: Santiago Sánchez Paz sanchez...@gmail.com Changed-By: Luciano Bello luci...@debian.org Description: dirdiff- Display and merge changes between two directory trees Closes: 725686 Changes: dirdiff (2.1-6) unstable; urgency=high . * Using tk8.5. Closes: #725686 (RC bug). * Standards-Version: 3.9.5 * Hardening flags added. Checksums-Sha1: a1fd68608f32349b26aa2191776b69ad818e88f3 1727 dirdiff_2.1-6.dsc cd67ddb38c53807ccc27f76b646f78dadfad1085 6842 dirdiff_2.1-6.diff.gz ffecca6bb97bf8faa304c7294ffc33f106c8b988 38230 dirdiff_2.1-6_amd64.deb Checksums-Sha256: d52ddc9e18053372295883fa9f370fdf203e1422d393b225d5d4e1c933fe551a 1727 dirdiff_2.1-6.dsc f9755e5a88c827e6bf3113ae2c33239c932179f7d6cd9ca9f571bb4a8cc3733b 6842 dirdiff_2.1-6.diff.gz 6be207dbc9338421cdb324b80264fde846232e7aaaba1a53d3dc281b80f61f11 38230 dirdiff_2.1-6_amd64.deb Files: f1f444f3721b3dfa61b54f9586dd08b3 38230 utils optional dirdiff_2.1-6_amd64.deb eb72932047ffd4e9a48dba6418eff27a 1727 utils optional dirdiff_2.1-6.dsc 6e3f99887a2df2a012573823cbdd6ffe 6842 utils optional dirdiff_2.1-6.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJT+mO4AAoJEG7C3vaP/jd08NYP/A6jWkMlrnrlD73nPi8lOdaR zt+C1gKQdteDwBC+ANTBtus0IdnQSe5wfkaqQMTJlZbZ/ra7G2E0YMwJ9kgk7GX9 9fMa78nhqUI8p1b8zGBB8GO9K6vuRkUBd3fRn1bGMBDt95nFM+gRYYTlgHX/udgl C+IArVMI2ibK1tTVfu+4aDzZhUHD9Z0kZs7xwIYeOsq5FtUgewD9zFbk73SQOrcT LagVuDeDRjGFUWyDNWO/Sr043x4qRRnGplCN0wK1b9KOvRbQxFZaIEU0/fDVKAVP zVSjDMjRZ4tevOGOXZgtm4ur5Xhqr2FgJR88ltE2LHEHimsCJUSRE7IU5EAfcvTh S779zanb2LuvQ6KZ0O/zokymXnVPkK+jG1XS71EkhdEZdgwINQu4anIP/C6cLCAM LY9e1z+yC+RB5rDgbMQhFYmnUY6URB9wPSK3miTwEx0/2GWIRBQSvQrd3BLY7VsL S3TRNkGlO1yp/spEZxLSlVqKMEDFcEyiqvUAKCxzMSP1HxXkLECo72l6YhXJ09AK URM0/SI1TuMY5hVVI/BxwRrVQaN5vJOaKE6iWwlfu4UPZKXoKMFu5lh4Sx59Ma5m FQCzREVTA4BX1zI4nmFuWKN+/SA+1bzyRYsmIlrQvcp5nXCWE0e24Aktz1YWyw1X 3TWx7mlRSAF28J9vxWGl =R1ah -END PGP SIGNATUREEnd Message---
Bug#758687: marked as done (uninstallable: xorg-server 1.16 transition)
Your message dated Sun, 24 Aug 2014 23:24:41 +0100 with message-id 53fa6629.30...@pyro.eu.org and subject line Re: Bug#758687: uninstallable: xorg-server 1.16 transition has caused the Debian Bug report #758687, regarding uninstallable: xorg-server 1.16 transition 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.) -- 758687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-nv Version: 1:2.1.20-2 Severity: grave Justification: renders package unusable Hi, your package needs an update for the transition to xorg-server 1.16 which happened in July. https://packages.qa.debian.org/x/xserver-xorg-video-nv/news/20140715T163918Z.html Your package is currently in unstable only, and uninstallable. Mraw, KiBi. ---End Message--- ---BeginMessage--- Source-Version: 1:2.1.20-3 Thanks Christoph! On 24/08/14 18:38, Christoph Egger wrote: Guess it still also needs to mail [0] but I'm following up on that. [0] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd Maybe it is done already: http://lists.debian.org/09f6de1446cdb3fb7c8261bfc86b0...@hub.kern.lc Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature ---End Message---
Bug#758687: uninstallable: xorg-server 1.16 transition
Steven Chamberlain ste...@pyro.eu.org writes: [0] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd Maybe it is done already: http://lists.debian.org/09f6de1446cdb3fb7c8261bfc86b0...@hub.kern.lc At least it's built on buildds now! Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752178: [unetbootin] The resulting usb pendrive looping with menu.c32 error
Hello, it seems to be a bit funny: I experienced the same bug. According to the Ubuntu bug report I tried to look for the mentioned files and found that on my box there were the two folders usr/lib/syslinux and usr/lib/SYSLINUX, the latter did not contain the files I was looking for. I renamed that folder and from that time on unetbootin seemed to find the right path and worked like it should without having to copy any files. Could you have a look and verify if this is the same on your box , maybe the SYSLINUX folder comes from a former installation? Regards Ingo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759129: nanomsg ftbfs in current unstable (i386, and other architectures)
Am 24.08.2014 um 23:43 schrieb Harlan Lieberman-Berg: If we still see problems in other places, we'll have to disable the tests altogether. then it's better to run these but ignore the test results (or just ignore the test failures of these which don't succeed). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759129: nanomsg ftbfs in current unstable (i386, and other architectures)
On Mon, 2014-08-25 at 01:09 +0200, Matthias Klose wrote: then it's better to run these but ignore the test results (or just ignore the test failures of these which don't succeed). Definitely. I'll set that up if we still have more problems. I just submitted -2 to solve this issue and pushed the new code up to collab-maint, if you want to take a try at rebuilding. Sincerely, -- Harlan Lieberman-Berg ~hlieberman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754237: RFC: disable SCTP in Debian's kFreeBSD?
On 06/08/14 22:18, Moritz Mühlenhoff wrote: On Wed, Jul 09, 2014 at 01:26:22AM +0100, Steven Chamberlain wrote: So I'm obviously asking here - could we just drop SCTP from the default kernel config? In jessie/sid? Even in wheezy-security? We can certainly do this for wheezy-security if the kfreebsd maintainers think it's the best course of action. Okay then, thanks. I propose we drop SCTP support from wheezy kernels, via wheezy-security, to address CVE-2014-3953 and other concerns. In kfreebsd-10 however, there's been a lot of work on SCTP recently, suggesting there's some renewed interest in the protocol. I'm inclined to keep it in the 10.1 kernel config for now. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: These bugs are not RC
Processing commands for cont...@bugs.debian.org: severity 755093 important Bug #755093 [src:cjs] cjd: FTBFS on sparc Severity set to 'important' from 'serious' severity 759023 important Bug #759023 [src:cjs] cjs: FTBFS on kFreeBSD Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 755093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755093 759023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759023 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#757711: netcfg: promptly kills dhclient, deconfigures interface
Processing commands for cont...@bugs.debian.org: tags 757711 + patch Bug #757711 [src:netcfg] netcfg: promptly kills dhclient, deconfigures interface Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 757711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757711 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#758688: cannot be installed
You guys noticed that it cannot be installed in sid any longer since libxen-4.3 is no more?! Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0
On Sun, 2014-08-24 at 21:24 +0100, Ian Campbell wrote: I've timed out for now, but I'll continue prodding as I have the chance... I caught up with Adam Conrad a debconf and he pointed out that __aeabi_* are some weird internal ABI thing which doesn't actually indicate an unresolved symbol. IOW they should be ignored, dpkg-shlibs does this too (search for __aeabi_ in /usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm) Rebuilding the installer with mklibs patches as below seems to work, in that I can chroot tmp/network-console/tree/ /bin/sh and then in the chroot /usb/sbin/sshd --help runs and produces output. If the symbol were actually required at runtime then this would have failed with some sort of dynamic linker error. This: # LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-armhf.so.3 /usr/sbin/sshd libcrypto.so.1.0.0 = /usr/lib/libcrypto.so.1.0.0 (0xb6ddd000) libutil.so.1 = /lib/libutil.so.1 (0xb6dcb000) libz.so.1 = /usr/lib/libz.so.1 (0xb6da9000) libcrypt.so.1 = /lib/libcrypt.so.1 (0xb6d6c000) libc.so.6 = /lib/libc.so.6 (0xb6cc1000) /lib/ld-linux-armhf.so.3 (0xb6f7c000) libdl.so.2 = /lib/libdl.so.2 (0xb6cb) indicates that the ssh binary is indeed using those libraries which appear to depend on the problematic symbol. What's not clear is why this is just occurring now. I suppose changes to gcc/glibc or something have caused it to be exposed. I don't propose to dig much deeper into that aspect (mostly on the basis that if dpkg-shlibs does it mklibs should too). So I think we should upload a new mklibs and have a new debian-installer upload which buidld-deps on it. Ian. From cf0887e69d4d150e240fa3770e03464ed79aa442 Mon Sep 17 00:00:00 2001 From: Ian Campbell i...@hellion.org.uk Date: Mon, 25 Aug 2014 02:22:15 +0100 Subject: [PATCH] Ignore all ARM EABI symbols (__aeabi_*) --- debian/changelog | 7 +++ src/mklibs | 11 +++ 2 files changed, 18 insertions(+) diff --git a/debian/changelog b/debian/changelog index e9afd36..303e1c1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +mklibs (0.1.40) UNRELEASED; urgency=medium + + * Ignore all ARM EABI symbols (__aeabi_*). These are artefacts of the ABI and +not real symbols which need to be present. + + -- Ian Campbell i...@hellion.org.uk Mon, 25 Aug 2014 02:08:09 +0100 + mklibs (0.1.39) unstable; urgency=medium * Sort objects and libraries to reduce entropy in the output, which diff --git a/src/mklibs b/src/mklibs index d9b784b..1f3d60f 100755 --- a/src/mklibs +++ b/src/mklibs @@ -137,6 +137,14 @@ class UndefinedSymbol(Symbol): super(UndefinedSymbol, self).__init__(name, version, library) self.weak, self.library = weak, library +def symbol_is_blacklisted(name): +# The ARM Embedded ABI spec states symbols under this namespace as +# possibly appearing in output objects. +if name.startswith(__aeabi_): +return True + +return False + # Return undefined symbols in an object as a set of tuples (name, weakness) def undefined_symbols(obj): if not os.access(obj, os.F_OK): @@ -148,6 +156,9 @@ def undefined_symbols(obj): for line in output: name, weak_string, version_string, library_string = line.split()[:4] +if symbol_is_blacklisted(name): +continue + weak = False if weak_string.lower() == 'true': weak = True -- 2.0.1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0
Ian Campbell i...@hellion.org.uk (2014-08-25): On Sun, 2014-08-24 at 21:24 +0100, Ian Campbell wrote: I've timed out for now, but I'll continue prodding as I have the chance... I caught up with Adam Conrad a debconf and he pointed out that __aeabi_* are some weird internal ABI thing which doesn't actually indicate an unresolved symbol. IOW they should be ignored, dpkg-shlibs does this too (search for __aeabi_ in /usr/share/perl5/Dpkg/Shlibs/SymbolFile.pm) Rebuilding the installer with mklibs patches as below seems to work, in that I can chroot tmp/network-console/tree/ /bin/sh and then in the chroot /usb/sbin/sshd --help runs and produces output. If the symbol were actually required at runtime then this would have failed with some sort of dynamic linker error. This: # LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-armhf.so.3 /usr/sbin/sshd libcrypto.so.1.0.0 = /usr/lib/libcrypto.so.1.0.0 (0xb6ddd000) libutil.so.1 = /lib/libutil.so.1 (0xb6dcb000) libz.so.1 = /usr/lib/libz.so.1 (0xb6da9000) libcrypt.so.1 = /lib/libcrypt.so.1 (0xb6d6c000) libc.so.6 = /lib/libc.so.6 (0xb6cc1000) /lib/ld-linux-armhf.so.3 (0xb6f7c000) libdl.so.2 = /lib/libdl.so.2 (0xb6cb) indicates that the ssh binary is indeed using those libraries which appear to depend on the problematic symbol. What's not clear is why this is just occurring now. I suppose changes to gcc/glibc or something have caused it to be exposed. I don't propose to dig much deeper into that aspect (mostly on the basis that if dpkg-shlibs does it mklibs should too). So I think we should upload a new mklibs and have a new debian-installer upload which buidld-deps on it. Hi, and many thanks to both of you. Feel free to upload an updated mklibs and bump the build-dep in debian-installer's git. No need to upload it right away IMHO. Mraw, KiBi. signature.asc Description: Digital signature
Bug#754982: NMU of transmission?
Hi, The new version of Transmission, (ie: version 2.84) solves the issue with miniupnpc. Can you upload that one? If not, would you agree that I do an NMU of it? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704206: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package teem fails to build as reported in bug #704206 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=teemarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755009: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package adasockets fails to build as reported in bug #755009 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=adasocketsarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723964: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package devtodo fails to build as reported in bug #723964 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=devtodoarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735832: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package wyrd fails to build as reported in bug #735832 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=wyrdarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758501: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package gsmlib fails to build as reported in bug #758501 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=gsmlibarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759182: dolfin: FTBFS on mips(el) and sparc: MPI inconsistency
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! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759183: dolfin: FTBFS on {hurd,kfreebsd}-i386: virtual memory exhausted
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! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759185: oasis3: FTBFS: dvipdf: not found
Source: oasis3 Version: 3.mct+dfsg.121022-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of oasis3 in minimal environments (as on the autobuilders) have been failing: cd lib/mct/doc dvipdf mct_APIs.dvi /bin/sh: 1: dvipdf: not found make[1]: *** [override_dh_auto_build] Error 127 The package containing dvipdf is ghostscript, which isn't even in Build-Depends-Indep, though the documentation build is currently unconditional anyway. 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#759188: bluetoothd: Creates FIFO at /tmp/hogsuspend, not in /run
Package: bluez Version: 5.21-2 Severity: serious There is a FIFO at /tmp/hogsuspend on my system. It is opened by bluetoothd, though this doesn't seem to be documented anywhere. It is apparently a debug feature added this patch (or actually a later version): http://www.spinics.net/lists/linux-bluetooth/msg29802.html This feature should either be disabled by default or changed to put the FIFO somewhere under /run. This bug was previously reported against Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=998133 where it was pointed out that this upsets SELinux. Ben. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.14-2-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 bluez depends on: ii dbus 1.8.6-1 ii init-system-helpers 1.20 ii kmod 18-1 ii libc62.19-7 ii libdbus-1-3 1.8.6-1 ii libglib2.0-0 2.40.0-3 ii libreadline6 6.3-8 ii libudev1 208-7 ii lsb-base 4.1+Debian13 ii udev 208-7 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
Package: isolinux Version: 3:6.03~pre19+dfsg-3 Severity: serious Justification: breaks rdepends Hi, once again syslinux is breaking its reverse dependencies. We're now getting this in d-i daily builds: | geniso_hybrid_plus_firmware_partition ./tmp/netboot/mini.iso | util/geniso_hybrid_plus_firmware_partition: 26: util/geniso_hybrid_plus_firmware_partition: isohybrid: not found | config/x86.cfg:248: recipe for target 'arch_miniiso' failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
Cyril Brulebois k...@debian.org (2014-08-25): Package: isolinux Version: 3:6.03~pre19+dfsg-3 Severity: serious Justification: breaks rdepends Hi, once again syslinux is breaking its reverse dependencies. We're now getting this in d-i daily builds: | geniso_hybrid_plus_firmware_partition ./tmp/netboot/mini.iso | util/geniso_hybrid_plus_firmware_partition: 26: util/geniso_hybrid_plus_firmware_partition: isohybrid: not found | config/x86.cfg:248: recipe for target 'arch_miniiso' failed Or that was syslinux-common. I lost track of files/packages getting renamed/moved around. Please keep debian-boot@ in copy of your replies. signature.asc Description: Digital signature
Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
reassign 759189 debian-installer forcemerge 759189 751731 thanks On 08/25/2014 06:27 AM, Cyril Brulebois wrote: once again syslinux is breaking its reverse dependencies. We're now getting this in d-i daily builds: please update your package as i've communicated in #751731, thanks. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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#759189: isolinux: isohybrid dropped, breaking debian-installer builds
Processing commands for cont...@bugs.debian.org: reassign 759189 debian-installer Bug #759189 [isolinux] isolinux: isohybrid dropped, breaking debian-installer builds Bug reassigned from package 'isolinux' to 'debian-installer'. No longer marked as found in versions syslinux/3:6.03~pre19+dfsg-3. Ignoring request to alter fixed versions of bug #759189 to the same values previously set forcemerge 759189 751731 Bug #759189 [debian-installer] isolinux: isohybrid dropped, breaking debian-installer builds Bug #751731 [debian-installer] please use syslinux-utils instead of isolinux for isohybird Severity set to 'serious' from 'important' Merged 751731 759189 thanks Stopping processing here. Please contact me if you need assistance. -- 751731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751731 759189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759189 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#759189: isolinux: isohybrid dropped, breaking debian-installer builds
Daniel Baumann daniel.baum...@progress-technologies.net (2014-08-25): reassign 759189 debian-installer forcemerge 759189 751731 thanks On 08/25/2014 06:27 AM, Cyril Brulebois wrote: once again syslinux is breaking its reverse dependencies. We're now getting this in d-i daily builds: please update your package as i've communicated in #751731, thanks. Please stop breaking packages gratuitously, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Processed: unmerging 759189, reassign 759189 to isolinux, severity of 759189 is serious
Processing commands for cont...@bugs.debian.org: unmerge 759189 Bug #759189 [debian-installer] isolinux: isohybrid dropped, breaking debian-installer builds Bug #751731 [debian-installer] please use syslinux-utils instead of isolinux for isohybird Disconnected #759189 from all other report(s). reassign 759189 isolinux Bug #759189 [debian-installer] isolinux: isohybrid dropped, breaking debian-installer builds Bug reassigned from package 'debian-installer' to 'isolinux'. Ignoring request to alter found versions of bug #759189 to the same values previously set Ignoring request to alter fixed versions of bug #759189 to the same values previously set severity 759189 serious Bug #759189 [isolinux] isolinux: isohybrid dropped, breaking debian-installer builds Ignoring request to change severity of Bug 759189 to the same value. thanks Stopping processing here. Please contact me if you need assistance. -- 751731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751731 759189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759189 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#759189: isolinux: isohybrid dropped, breaking debian-installer builds
why did you reassign #759189 back to syslinux? do you require a patch for #751731? are there any problems adding syslinux-utils to debian-installer build-depends? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
[ Again, please keep debian-boot@ in the loop. ] Daniel Baumann daniel.baum...@progress-technologies.net (2014-08-25): why did you reassign #759189 back to syslinux? do you require a patch for #751731? are there any problems adding syslinux-utils to debian-installer build-depends? Because your package is actively dropping features your reverse dependencies are using. So please avoid doing so until packages have been adapted, uploaded, and possibly migrated to testing. Patches are always appreciated. About using syslinux-utils in build-depends, I don't know yet. It'd be nice if someone could take some time to investigate that. Until that has happened, we're back to: please don't actively break your reverse dependencies. That's why #759189 belongs to src:syslinux, and why I reassigned it back. signature.asc Description: Digital signature
Processed: severity of 758199 is important
Processing commands for cont...@bugs.debian.org:
# Non-release arch FTBFS are not RC
severity 758199 important
Bug #758199 {Done: Guillem Jover guil...@debian.org} [src:dpkg] dpkg:
libcompat fails to build on GNU/Hurd
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
758199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758199
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#733517: bug 733517 is forwarded to https://bitbucket.org/cffi/cffi/issue/162/bus-error-on-sparc
❦ 23 août 2014 22:08 +0200, Vincent Bernat ber...@debian.org : forwarded 733517 https://bitbucket.org/cffi/cffi/issue/162/bus-error-on-sparc Hi! A patch is available here: https://bitbucket.org/cffi/cffi/pull-request/45/use-memcpy-instead-of-unaligned-accesses/diff It has been merged upstream. Also, I can prepare and do the upload if you wish. -- panic(floppy: Port bolixed.); 2.2.16 /usr/src/linux/include/asm-sparc/floppy.h signature.asc Description: PGP signature
Bug#759189: isolinux: isohybrid dropped, breaking debian-installer builds
On 08/25/2014 07:35 AM, Cyril Brulebois wrote: [ Again, please keep debian-boot@ in the loop. ] [ clicking on reply-all in icedove only adds CCs for addresses that were CCed in the original message. ] Because your package is actively dropping features your reverse dependencies are using. there were two (suspected) reverse dependencies: debian-cd and debian-installer. i filled bugs against both beginning of june. turns out, debian-cd is not using isohybrid. debian-installer is the only package using it. So please avoid doing so until packages have been adapted, uploaded, and possibly migrated to testing. 10 weeks should be enough, even for debian-installer, to add a simple additional build-depends. Patches are always appreciated. patch attached. About using syslinux-utils in build-depends, I don't know yet. It'd be nice if someone could take some time to investigate that. no need to overcomplicate things: debian-installer calls the 'isohybrid' command which is in bin:syslinux-utils instead of bin:isolinux. adding syslinux-utils to build-depends as you do for any other packages you are using during the build is enough. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ diff -Naurp debian-installer.orig/debian/control debian-installer/debian/control --- debian-installer.orig/debian/control 2014-08-02 00:09:06.0 + +++ debian-installer/debian/control 2014-08-25 05:43:42.460472053 + @@ -93,6 +93,7 @@ Build-Depends: # still called debian-boot.. syslinux [i386 amd64], isolinux [i386 amd64], + syslinux-utils [i386 amd64], pxelinux [i386 amd64], syslinux-common (= 3:6) [i386 amd64], # With isohybrid.
Bug#754237: RFC: disable SCTP in Debian's kFreeBSD?
On Mon, Aug 25, 2014 at 01:27:43AM +0100, Steven Chamberlain wrote: On 06/08/14 22:18, Moritz Mühlenhoff wrote: On Wed, Jul 09, 2014 at 01:26:22AM +0100, Steven Chamberlain wrote: So I'm obviously asking here - could we just drop SCTP from the default kernel config? In jessie/sid? Even in wheezy-security? We can certainly do this for wheezy-security if the kfreebsd maintainers think it's the best course of action. Okay then, thanks. I propose we drop SCTP support from wheezy kernels, via wheezy-security, to address CVE-2014-3953 and other concerns. Ok, please note that kfreebsd-9 also needs http://www.freebsd.org/security/advisories/FreeBSD-SA-14:17.kmem.asc In kfreebsd-10 however, there's been a lot of work on SCTP recently, suggesting there's some renewed interest in the protocol. I'm inclined to keep it in the 10.1 kernel config for now. Ok. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
