Bug#762755: marked as done (bind 9.9.5-4.1: assertion failure)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding bind 9.9.5-4.1: assertion failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.9.5.dfsg-4.1
Severity: important

After upgrading from 1:9.9.5.dfsg-4 bind9 fails to start. It logs after 
loading the zones:

Sep 24 23:44:19 name named[10932]: mem.c:1321: REQUIRE(ptr != ((void *)0)) 
failed, back trace
Sep 24 23:44:19 name named[10932]: #0 0x7f74d0b4922d in ??
Sep 24 23:44:19 name named[10932]: #1 0x7f74ced367ba in ??
Sep 24 23:44:19 name named[10932]: #2 0x7f74ced4702c in ??
Sep 24 23:44:19 name named[10932]: #3 0x7f74d03f8694 in ??
Sep 24 23:44:19 name named[10932]: #4 0x7f74d03a416a in ??
Sep 24 23:44:19 name named[10932]: #5 0x7f74d038bc29 in ??
Sep 24 23:44:19 name named[10932]: #6 0x7f74d038bd99 in ??
Sep 24 23:44:19 name named[10932]: #7 0x7f74d03ff7fd in ??
Sep 24 23:44:19 name named[10932]: #8 0x7f74d040dbf0 in ??
Sep 24 23:44:19 name named[10932]: #9 0x7f74ced57eeb in ??
Sep 24 23:44:19 name named[10932]: #10 0x7f74ce7090a4 in ??
Sep 24 23:44:19 name named[10932]: #11 0x7f74ce0d9c2d in ??
Sep 24 23:44:19 name named[10932]: exiting (due to assertion failure)


Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bind9_9.9.5.dfsg-4.2.dsc
 f9c3204ee4c5691a3

Bug#762800: marked as done (bind9 crashes)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding bind9 crashes
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.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: bind9
Version: 1:9.9.5.dfsg-4.1

After updating Debian Jessie DNS  today resolver on bind startup (or, 
perhaps, on several first queries) I receive


Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
114.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
115.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
116.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
117.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
118.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
119.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
120.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
121.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
122.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
123.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
124.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
125.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
126.100.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
127.100.IN-ADDR.ARPA

Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 0.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 127.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
254.169.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
2.0.192.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
100.51.198.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
113.0.203.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
255.255.255.255.IN-ADDR.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA

Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: D.F.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 8.E.F.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 9.E.F.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: A.E.F.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: B.E.F.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: automatic empty zone: 
8.B.D.0.1.0.0.2.IP6.ARPA
Sep 25 13:33:29 resolv2 named[1381]: command channel listening on 
127.0.0.1#953

Sep 25 13:33:29 resolv2 named[1381]: general: notice: all zones loaded
Sep 25 13:33:29 resolv2 named[1381]: general: notice: running

Sep 25 13:27:52 resolv1 named[1389]: general: critical: mem.c:1321: 
REQUIRE(ptr != ((void *)0)) failed, back trace
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #0 
0x7f3c7c3a622d in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #1 
0x7f3c7a5a47ba in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #2 
0x7f3c7a5b502c in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #3 
0x7f3c7bc55694 in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #4 
0x7f3c7bc0116a in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #5 
0x7f3c7bbe8c29 in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #6 
0x7f3c7bbe8d99 in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #7 
0x7f3c7bc5c7fd in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #8 
0x7f3c7bc6abf0 in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #9 
0x7f3c7a5c5eeb in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #10 
0x7f3c79f780a4 in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: #11 
0x7f3c7994dc2d in ??
Sep 25 13:27:52 resolv1 named[1389]: general: critical: exiting (due to 
assertion failure)


Rolling back to 1:9.9.5.dfsg-4 helps.

--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, which is due to be installed in the Debian FTP archive.

Bug#762766: marked as done (bind9: ftbfs no rule for unix/socket.lo on some archs)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#762766: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #762766,
regarding bind9: ftbfs no rule for unix/socket.lo on some archs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
762766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: bind9
severity: serious
version: 1:9.9.5.dfsg-4.1

See buildd output.  It looks like this is a dependency that's not
actually needed, but more testing needed.  Since I broke it, I'll fix
it, but no time tonight.

Best wishes,
Mike
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bind9_9.9.5.dfsg-4.2.dsc
 f9c3204ee4c5691a3b1270538d05721114c1eb76 99717 bind9_9.9.5.dfsg-4.2.diff.gz
 68a02f1187417b1db0440273008dbbf870bc2825 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 415b09de04ae5e4f8a06d3bb4355f74e112cf163 8 host_9.9.5.dfsg-4.2_all.deb
Checksums-Sha256:
 30f999bf4027b5684aa8eb9da9539b6dc1b151d011edce15038a14bb68b47160 4109 
bind9_9.9.5.dfsg-4.2.dsc
 31d8988674b476b08a835af36977047c64b4dcf903b3b2a7268382be6540c902 99717 
bind9_9.9.5.dfsg-4.2.diff.gz
 e1391cea57fbeb36bba54fa68c1fd9bc9adc8837fe3de731d041ffedd4798580 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 af1caa79328713d12bf580efa83a0a733110b40d673be13a9a6170601e825def 8 
host_9.9.5.dfsg-4.2_all.deb
Files:
 1f35c43ee8fb2083ff9cc15e00671f4c 338348 doc optional 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 2c5dc2db94de410621fe3d57ac06f7e6 8 net standard host_9.9.5.dfsg-4.2_all.deb
 8724cc3f8b6d5ec386ab39e7c81da729 41

Bug#750760: marked as done (bind9: requires -fno-delete-null-pointer-checks on gcc >= 4.9)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding bind9: requires -fno-delete-null-pointer-checks on 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.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Severity: normal

According to [0], bind9 should be compiled with
"-fno-delete-null-pointer-checks" added to CFLAGS, in order to avoid
certain optimizations that occur when compiled with gcc 4.9 that can
cause the server process to crash.  I've also written an article [1] on
the topic with a little more background info.

It might be prudent to have this workaround in bind9 active before the
switch to gcc-4.9 to minimize the possibility of bad binaries reaching
the archive.

[0] https://kb.isc.org/article/AA-01167

[1] http://blog.mycre.ws/articles/bind-and-gcc-49/

Thanks!

-- 
Robert Edmonds
edmo...@debian.org


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bind9_9.9.5.dfsg-4.2.dsc
 f9c3204ee4c5691a3b1270538d05721114c1eb76 99717 bind9_9.9.5.dfsg-4.2.diff.gz
 68a02f1187417b1db0440273008dbbf870bc2825 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 415b09de04ae5e4f8a06d3bb4355f74e112cf163 8 host_9.9.5.dfsg-4.2_all.deb
Checksums-Sha256:
 30f999bf4027b5684aa8eb9da9539b6dc1b151d011edce15038a14bb68b47160 4109 
bind9_9.9.5.dfsg-4.2.dsc
 31d8988674b476b08a835af36977047c64b4dcf903b3b2a7268382be6540c902 99717 

Bug#762762: marked as done (libbind-export-udeb: not installable: depends on libdns-export100, libisc-export95, libisccfg-export90)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#762762: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #762762,
regarding libbind-export-udeb: not installable: depends on libdns-export100, 
libisc-export95, libisccfg-export90
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.)


-- 
762762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbind-export-udeb
Version: 1:9.9.5.dfsg-4.1
Severity: grave
Justification: renders package unusable

Hi,

your NMU added a libbind-export-udeb udeb in the last bind9 upload but
it's nowhere installable.
| Depends: libc6-udeb (>= 2.19), libdns-export100, libisc-export95, 
libisccfg-export90

I don't see it mentioned explicitly in the changelog, it doesn't appear
to be the topic of #656150, and I don't think there were any discussions
about it on debian-boot@ (X-d-cc'd, please keep the list in the loop).

Maybe it would be a good idea to talk to the installer team at some
point?

KiBi.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bind9_9.9.5.dfsg-4.2.dsc
 f9c3204ee4c5691a3b1270538d05721114c1eb76 99717 bind9_9.9.5.dfsg-4.2.diff.gz
 68a02f1187417b1db0440273008dbbf870bc2825 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 415b09de04ae5e4f8a06d3bb4355f74e112cf163 8 host_9.9.5.dfsg-4.2_all.deb
Checksums-Sha256:
 30f999bf4027b5684aa8eb9da9539b6dc1b151d011edce15038a14bb68b47160 4109 
bind9_9.9.5.dfsg-4.2.dsc
 31d8988674b476b08a835af36977047c64b4dcf903b3b2a7268382be6540c902 99717 
bind9_9.9.5.dfsg-4.2.diff.gz
 e1391ce

Bug#762805: marked as done (bind9 process crashes within a few minutes of restarting)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding bind9 process crashes within a few minutes of restarting
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.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.9.5.dfsg-4.1
Severity: important

Dear Maintainer,

With the update 1:9.9.5.dfsg-4 1:9.9.5.dfsg-4.1 bind9 now crashes with:

Sep 25 06:30:40 dimen named[6358]: mem.c:1321: REQUIRE(ptr != ((void *)0)) 
failed, back trace
Sep 25 06:30:40 dimen named[6358]: #0 0x7feaed9c922d in ??
Sep 25 06:30:40 dimen named[6358]: #1 0x7feaebbb67ba in ??
Sep 25 06:30:40 dimen named[6358]: #2 0x7feaebbc702c in ??
Sep 25 06:30:40 dimen named[6358]: #3 0x7feaed278694 in ??
Sep 25 06:30:40 dimen named[6358]: #4 0x7feaed22416a in ??
Sep 25 06:30:40 dimen named[6358]: #5 0x7feaed20bc29 in ??
Sep 25 06:30:40 dimen named[6358]: #6 0x7feaed20bd99 in ??
Sep 25 06:30:40 dimen named[6358]: #7 0x7feaed27f7fd in ??
Sep 25 06:30:40 dimen named[6358]: #8 0x7feaed28b26b in ??
Sep 25 06:30:40 dimen named[6358]: #9 0x7feaebbd7eeb in ??
Sep 25 06:30:40 dimen named[6358]: #10 0x7feaeb5890a4 in ??
Sep 25 06:30:40 dimen named[6358]: #11 0x7feaeaf59c2d in ??
Sep 25 06:30:40 dimen named[6358]: exiting (due to assertion failure)

within a few minutes of being restarted. Although I have a local configuration, 
I checked with a brand new
install and the same behaviour obtains.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bind9 depends on:
ii  adduser3.113+nmu3
ii  bind9utils 1:9.9.5.dfsg-4.1
ii  debconf [debconf-2.0]  1.5.53
ii  init-system-helpers1.21
ii  libbind9-901:9.9.5.dfsg-4.1
ii  libc6  2.19-11
ii  libcap21:2.24-5
ii  libcomerr2 1.42.12-1
ii  libdns100  1:9.9.5.dfsg-4.1
ii  libgssapi-krb5-2   1.12.1+dfsg-10
ii  libisc95   1:9.9.5.dfsg-4.1
ii  libisccc90 1:9.9.5.dfsg-4.1
ii  libisccfg901:9.9.5.dfsg-4.1
ii  libk5crypto3   1.12.1+dfsg-10
ii  libkrb5-3  1.12.1+dfsg-10
ii  liblwres90 1:9.9.5.dfsg-4.1
ii  libssl1.0.01.0.1i-2
ii  libxml22.9.1+dfsg1-4
ii  lsb-base   4.1+Debian13
ii  net-tools  1.60-26
ii  netbase5.2

bind9 recommends no packages.

Versions of packages bind9 suggests:
ii  bind9-doc   1:9.9.5.dfsg-4.1
ii  dnsutils1:9.9.5.dfsg-4.1
pn  resolvconf  
pn  ufw 

-- Configuration Files:
/etc/bind/named.conf changed [not included]
/etc/bind/named.conf.local changed [not included]

-- debconf information:
  bind9/different-configuration-file:
  bind9/start-as-user: bind
  bind9/run-resolvconf: false
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 

Bug#762948: marked as done (bind9: /usr/etc)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#762948: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #762948,
regarding bind9: /usr/etc
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.)


-- 
762948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: bind9
Version: 1:9.9.5.dfsg-4.1
Severity: serious
Justification: Policy §9.1.1, §10.7.2

$ dpkg -L bind9 | grep /usr/etc
/usr/etc
/usr/etc/bind.keys

Configuration files must reside in /etc.

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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 762...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bind9_9.9.5.dfsg-4.2.dsc
 f9c3204ee4c5691a3b1270538d05721114c1eb76 99717 bind9_9.9.5.dfsg-4.2.diff.gz
 68a02f1187417b1db0440273008dbbf870bc2825 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 415b09de04ae5e4f8a06d3bb4355f74e112cf163 8 host_9.9.5.dfsg-4.2_all.deb
Checksums-Sha256:
 30f999bf4027b5684aa8eb9da9539b6dc1b151d011edce15038a14bb68b47160 4109 
bind9_9.9.5.dfsg-4.2.dsc
 31d8988674b476b08a835af36977047c64b4dcf903b3b2a7268382be6540c902 99717 
bind9_9.9.5.dfsg-4.2.diff.gz
 e1391cea57fbeb36bba54fa68c1fd9bc9adc8837fe3de731d041ffedd4798580 338348 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 af1caa79328713d12bf580efa83a0a733110b40d673be13a9a6170601e825def 8 
host_9.9.5.dfsg-4.2_all.deb
Files:
 1f35c43ee8fb2083ff9cc15e00671f4c 338348 doc optional 
bind9-doc_9.9.5.dfsg-4.2_all.deb
 2c5dc2db94de410621fe3d57ac06f7e6 8 net standard host_9.9.5.dfsg-4.2_all.deb
 8724cc3f8b6d5ec386ab39e7c81da729 4109 net optional bind9_9.9.5.dfsg-4.2.dsc
 b6e579a61426fc92b44b

Bug#762876: marked as done (named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c
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.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: bind9
Version: 1:9.9.5.dfsg-4.1

From syslog:
Sep 25 15:16:21 odeon named[12685]: mem.c:1321: REQUIRE(ptr != ((void *)0)) 
failed, back trace
Sep 25 15:16:21 odeon named[12685]: #0 0x7fd64356522d in ??
Sep 25 15:16:21 odeon named[12685]: #1 0x7fd6417527ba in ??
Sep 25 15:16:21 odeon named[12685]: #2 0x7fd64176302c in ??
Sep 25 15:16:21 odeon named[12685]: #3 0x7fd642e14694 in ??
Sep 25 15:16:21 odeon named[12685]: #4 0x7fd642dc016a in ??
Sep 25 15:16:21 odeon named[12685]: #5 0x7fd642da7c29 in ??
Sep 25 15:16:21 odeon named[12685]: #6 0x7fd642da7d99 in ??
Sep 25 15:16:21 odeon named[12685]: #7 0x7fd642e1b7fd in ??
Sep 25 15:16:21 odeon named[12685]: #8 0x7fd642e29bf0 in ??
Sep 25 15:16:21 odeon named[12685]: #9 0x7fd641773eeb in ??
Sep 25 15:16:21 odeon named[12685]: #10 0x7fd6411250a4 in ??
Sep 25 15:16:21 odeon named[12685]: #11 0x7fd640af5c2d in ??

Kernel:

uname -r

3.16.3

Essentially, after an upgrade of bind9, bind9-host, and bind9utils,  named 
restarted and crashed very soon
afterwards.  Doing a service restart on bind9 would get it working again,  but 
it would crash again relatively
quickly.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 750760 762762 762766 762948
Changes:
 bind9 (1:9.9.5.dfsg-4.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix intermittent parallel build failure.  Closes: #762766
   * Set -fno-delete-null-pointer-checks.  Closes: #750760
   * Use separate packages for the udebs.  Closes: #762762
   * Don't install configuration files to /usr.  Closes: #762948
Checksums-Sha1:
 29107f7ae1e37066c6b4b7c87d2ac2b7f189fe04 4109 bi

Bug#762838: marked as done ([bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace”)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 07:00:06 +
with message-id 
and subject line Bug#750760: fixed in bind9 1:9.9.5.dfsg-4.2
has caused the Debian Bug report #750760,
regarding [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) 
failed, back trace”
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.)


-- 
750760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.9.5.dfsg-4.1
Severity: grave

--- Please enter the report below this line. ---

Hello,

Since last update, my bind server crashes after a few requests (maybe
when it gets too many at the same time), for instance when I start
Firefox (with some tabs)
Downgrading to the version in testing fixes the issue ( 1:9.9.5.dfsg-4).

The error log I get is:

25-Sep-2014 14:41:51.464 general: critical: mem.c:1321: REQUIRE(ptr != ((void 
*)0)) failed, back trace
25-Sep-2014 14:41:51.464 general: critical: #0 0x7fd288a3b22d in ??
25-Sep-2014 14:41:51.464 general: critical: #1 0x7fd286c287ba in ??
25-Sep-2014 14:41:51.464 general: critical: #2 0x7fd286c3902c in ??
25-Sep-2014 14:41:51.465 general: critical: #3 0x7fd2882ea694 in ??
25-Sep-2014 14:41:51.465 general: critical: #4 0x7fd28829616a in ??
25-Sep-2014 14:41:51.465 general: critical: #5 0x7fd28827dc29 in ??
25-Sep-2014 14:41:51.465 general: critical: #6 0x7fd28827dd99 in ??
25-Sep-2014 14:41:51.465 general: critical: #7 0x7fd2882f17fd in ??
25-Sep-2014 14:41:51.465 general: critical: #8 0x7fd2882ffbf0 in ??
25-Sep-2014 14:41:51.465 general: critical: #9 0x7fd286c49eeb in ??
25-Sep-2014 14:41:51.465 general: critical: #10 0x7fd2865fb0a4 in ??
25-Sep-2014 14:41:51.465 general: critical: #11 0x7fd285fcbc2d in ??
25-Sep-2014 14:41:51.465 general: critical: exiting (due to assertion failure)

I do not know how to install debugging symbols for bind, could you tell
me how if you need them?

Regards,
Valentin

--- System information. ---
Architecture: amd64
Kernel: Linux 3.13-1-amd64



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-4.2

We believe that the bug you reported is fixed in the latest version of
bind9, 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.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Oct 2014 01:23:57 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all
Version: 1:9.9.5.dfsg-4.2
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblw

Bug#764444: libalog: build-depends on cruft package libaws2.10.2-dev

[Ralf Treinen]

Source: libalog
Version: 0.4.1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable
Affects: libaws2.10.2

Hello,

libalog build-depends on libaws2.10.2-dev. However, this package is no
longer build from source libaws.

-Ralf.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764446: gir1.2-gweather-3.0: Typelib not found because it is in wrong location

[Bart Libert]

Package: gir1.2-gweather-3.0
Version: 3.14.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I recently noticed the gnome-shell extension 'panel world clock' stopped 
working suddenly. Logs indicated the following:

"Error: Requiring GWeather, version none: Typelib file for namespace 'GWeather' 
(any version) not found"

However, the correct package was installed. Also, just doing 
'imports.gi.GWeather' in a gjs console gives the same
problem.

Some investigation shows that the file 'GWeather-3.0.typelib' is installed in 
the following directory on my system:

/usr/lib/girepository-1.0/girepository-1.0

Other typelibs are installed in:

/usr/lib/girepository-1.0

After creating a symlink to GWeather-3.0.typelib in that directory, everything 
works fine.

Package content also contains the /usr/lib/girepository-1.0/girepository-1.0 
path. Wheezy package contains
/usr/lib/girepository-1.0 instead.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 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#763228: Processed: g++ producing overlapping exception frames [was: Re: Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value]

[Michael Tautschnig]

Hi Matthias,

[...]
> afaics not a GCC issue. please recheck with binutils 2.24.51.20141001-3
> 

This *is* binutils 2.24.51.20141001-3:

# zcat /usr/share/doc/binutils/changelog.Debian.gz | head -n 1
binutils (2.24.51.20141001-3) unstable; urgency=medium

And indeed only this version would yield the more detailed list of overlapping
.eh_frame_hdr, rather than merely saying that there were some as was the case in
2.24.51.20141001-1. Though this doesn't seem to be an issue of zero-sized
exception handling frames, as was discussed in the context of Mesa and Clang.

So if it isn't a GCC issue, should I reassign to binutils instead? (I have no
intention of playing a bug-assigning ping-pong, but I do fail to see what might
be wrong in CBMC. But I'm happy to assist by providing any input that would be
deemed useful.)

Best,
Michael



pgp8dqGJ0ahjb.pgp
Description: PGP signature

Processed: NMU debdiff for mod-gnutls_0.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch + pending
Bug #750857 [src:mod-gnutls] FTBFS on many architectures, test suite errors
Added tag(s) patch.
Bug #750857 [src:mod-gnutls] FTBFS on many architectures, test suite errors
Added tag(s) pending.

-- 
750857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750857
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#750857: NMU debdiff for mod-gnutls_0.6-1.1

[Aníbal Monsalve Salazar]

Control: tags -1 + patch + pending

Hello Daniel,

At Imagination Technologies (http://imgtec.com/) Jurica Stanojkovic has
found a solution to Debian bug #750857.

https://bugs.debian.org/750857

My NMU debdiff for mod-gnutls_0.6-1.1 is below, at the end of this
message.

With the changes in the NMU debdiff, mod-gnutls builds successfully on
mips, mipsel and amd64.

Regards,

Aníbal
--
Aníbal Monsalve Salazar 

debdiff mod-gnutls_0.6-1.dsc mod-gnutls_0.6-1.1.dsc
diff -Nru mod-gnutls-0.6/debian/changelog mod-gnutls-0.6/debian/changelog
--- mod-gnutls-0.6/debian/changelog 2014-02-21 06:10:16.0 +
+++ mod-gnutls-0.6/debian/changelog 2014-10-08 08:16:49.0 +0100
@@ -1,3 +1,13 @@
+mod-gnutls (0.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use 127.0.0.1 for TEST_IP.
+Add test-ip.patch.
+Patch by Jurica Stanojkovic .
+Closes: #750857.
+
+ -- Anibal Monsalve Salazar   Wed, 08 Oct 2014 08:16:43 
+0100
+
 mod-gnutls (0.6-1) unstable; urgency=low
 
   * New upstream version
diff -Nru mod-gnutls-0.6/debian/patches/series 
mod-gnutls-0.6/debian/patches/series
--- mod-gnutls-0.6/debian/patches/series1970-01-01 01:00:00.0 
+0100
+++ mod-gnutls-0.6/debian/patches/series2014-10-08 08:10:50.0 
+0100
@@ -0,0 +1 @@
+test-ip.patch
diff -Nru mod-gnutls-0.6/debian/patches/test-ip.patch 
mod-gnutls-0.6/debian/patches/test-ip.patch
--- mod-gnutls-0.6/debian/patches/test-ip.patch 1970-01-01 01:00:00.0 
+0100
+++ mod-gnutls-0.6/debian/patches/test-ip.patch 2014-10-08 08:12:26.0 
+0100
@@ -0,0 +1,34 @@
+From: Jurica Stanojkovic 
+Subject: Re: FTBFS on many architectures, test suite errors
+Date: Mon, 29 Sep 2014 15:14:48 +
+
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750857
+
+I have found while testing package on local build machine that package is
+failing due to configuration in /etc/hosts
+
+ip6-loopback was configured with
+127.0.0.1   localhost ip6-localhost ip6-loopback
+after replacing that with following
+::1   localhost ip6-localhost ip6-loopback
+package was built successfully without changes to source.
+
+I do not know how is this configured in /etc/hosts on official buildd for
+architectures that fail to build.
+
+Also if following patch is added to a source there is no need for changes in
+/etc/hosts:
+
+Index: mod-gnutls-0.6/t/Makefile
+===
+--- mod-gnutls-0.6.orig/t/Makefile
 mod-gnutls-0.6/t/Makefile
+@@ -6,7 +6,7 @@
+ # simple configuration choices.
+ 
+ export TEST_HOST ?= localhost
+-export TEST_IP ?= ::1
++export TEST_IP ?= 127.0.0.1
+ # chosen at random:
+ export TEST_PORT ?= 9932
+ export MSVA_PORT ?= 9933


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#718315: Please reduce severity of bug

[Vincent Lefevre]

Control: severity -1 important

Reducing the severity because XSLT can be regarded as a general
programming language, and not all programming language implementations
are protected against infinite recursion anyway.

On 2014-10-07 08:55:46 -0700, Andrew Ayer wrote:
> Dear Maintainer,
> 
> I do not believe that this bug constitutes a security vulnerability or
> that it deserves grave severity.

Well, I agree that this isn't a security vulnerability, but it still
*easily* freezes the whole system for several minutes, and can
possibly make random process crash / be killed by the OOM killer.

> As for exploiting locally, there are already a plethora of ways for a
> local user to DoS the system, such as by running a fork bomb in bash.

Note however that this must be done on purpose (or because of a
specific bug). That's not common.

> In these ways, Xalan is similar to an interpreter like bash or perl.

Yes, that's true at least with perl:

#!/usr/bin/env perl

sub f { &f }

&f;

(BTW, that might explain why some buggy Perl script was freezing my
system some time ago, though I didn't have the time to find what was
the cause exactly.)

In C, one would be protected because the memory for the recursize
function calls is taken from the stack, which is limited by default.

> The fact that malicious programs can do great harm to a system if
> interpreted by bash or perl does not constitute a security
> vulnerability in bash or perl, and nor should it in Xalan.

The main problem is not malicious programs, but bugs, e.g. in user
code. It's very easy to introduce a bug that yields an infinite
recursion. Users should be protected against system freeze due to
infinite recursion (or with a large number of recursion calls) by
default, just like what can be observed in C.

> I therefore propose that the severity of this bug be reduced to
> important or normal so that Xalan can migrate to Testing.  It would
> be a shame for Xalan to not make it into Jessie because of this.

I've reduced it to important.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
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#718315: Please reduce severity of bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #718315 [xalan] xalan: With recursive xsl:call-template, xalan makes the 
whole system freeze
Severity set to 'important' from 'grave'

-- 
718315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718315
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#741557: libapache2-mod-gnutls: apache will not start if mod_authnz_ldap is loaded before mod_gnutls

[Aníbal Monsalve Salazar]

Control: severity -1 important

On Thu, 2014-05-29 16:51:22 +0200, Andreas Metzler wrote:
> On 2014-04-02 Nikolai Lusan  wrote:
> [...]
>> Short of me compiling a local package linked against an earlier
>> version to libgnutls is there a solution? I note that the
>> libcurl4-gnutls-dev that is supposedly blocking this fix is set at
>> "wishlist" can we get that bumped to "critical"?
> [...]
> 
> Hello,
> 
> do you still see this? (curl has since switched to gnutls28) And if
> you still see the problem could you check whether building mod_gnutls
> against libgnutls28-dev from experimental (which has corrected symbol
> versioning) fixes the issue for you?
> 
> Thanks, cu Andreas

No response in 4+ months. I'm changing the severity of this bug to
important. If someone thinks this is stll a bug, please let me know and
I'll put it back as it was before.


-- 
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#741557: libapache2-mod-gnutls: apache will not start if mod_authnz_ldap is loaded before mod_gnutls

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #741557 [libapache2-mod-gnutls] libapache2-mod-gnutls: apache will not 
start if mod_authnz_ldap is loaded before mod_gnutls
Severity set to 'important' from 'critical'

-- 
741557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741557
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: Alog package update is in the works

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 755077 + pending
Bug #755077 [src:libalog] libalog: increase gnat version in dependencies
Added tag(s) pending.
> tags 746082 + pending
Bug #746082 [src:libalog] libalog: FTBFS: error: "aws-net-std__gnat.adb" must 
be compiled
Added tag(s) pending.
> tags 76 + pending
Bug #76 [src:libalog] libalog: build-depends on cruft package 
libaws2.10.2-dev
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
746082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746082
755077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755077
76: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
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#764441: sinfo and slurm-client: error when trying to install together

[Gaudenz Steinlin]

Ralf Treinen  writes:

> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
>
>   /usr/bin/sinfo
>   /usr/share/man/man1/sinfo.1.gz

This happends because the sinfo binary in slurm moved from slurm-llnl to
slurm-client and now the conflict specified in sinfo is wrong. To
restore the previous state, sinfo should update it's conflict to
slurm-client with appropriate versioning.

A better solution would be if one of the binaries would be renamed. I
don't know what the sinfo command in slurm does, so I can't judge if
it's easy to rename or not. Renameing the sinfo command in the sinfo
package would be suboptimal at best because it's the main command of
this package.

Gaudenz


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#746082: Alog package update is in the works

[Adrian-Ken Rueegsegger]

tags 755077 + pending
tags 746082 + pending
tags 76 + pending
thanks

Changes to address the effects of Debian bug #763286 [1] on Alog are
currently being integrated upstream. As soon as the new Alog release is
ready, I will update the Debian package and submit it for upload.

[1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763286


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763780: apt-get: Insecure temporary changelog handling

[Michael Vogt]

On Thu, Oct 02, 2014 at 06:29:45PM +0200, Guillem Jover wrote:
> Package: apt
> Version: 0.8.7
> Severity: serious
> Tags: security patch

Thanks for your bugreport and your patch!
 
> I've found an instance of insecure temporary filenames handling. The
> problem is that the code correctly creates a temporary directory, but
> then uses that name as just a prefix for the created changelog
> filename, thus creating it alongside the tamporary directory (instead
> of inside of it), and making it very much predictable. This is worsened
> due to the time it takes apt-get to download the changelog from the net,
> which gives a very huge window to use that pathname.
> 
> Attached a patch fixing this. This affects all versions starting from
> the one in squeeze.
> 
> I'm not sure if this deserves a CVE or perhaps a lower severity?
[..]

I uploaded a fix for wheezy now, squeeze is not affected, this feature
got added in 0.8.11 in debian so we should be safe here.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#616689: The bug now reaches the "separate /usr on lvm" case

[Raphael Plasson]

Few more informations,

I also met this bug on another computer, where both separate / and /usr
partitions were on lvm. I didn't have problem beforehand, but the
upgrade of initramfs-tools indeed lead to the same problem.
Interestingly, it is clear during the boot time that the lvm root
partition is correctly mounted, then initramfs waits for /usr, cannot
find it and fall back to initramfs prompt. "vgchange -ay" command and
exiting this prompt leads to a correct boot process. This time, I only
put a "lvm vgchange -ay" line on the lvm2 script, didn't specify any
kernel option to grub, and this solved the problem.

So as far as I can observe the problem on my computers:
- the problem only occurs for a separate /usr partition on lvm volumes
(no problem with / ): initramfs cannot find it
- a "lvm vgchange -ay" line on the
/usr/share/initramfs-tools/scripts/local-top/lvm2 added before the
"activate_vg" commands solves the problem (i.e. both / and /usr are
correctly found and mounted by initramfs)

-- Raphaël


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: jessie

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 764268 + sid jessie
Bug #764268 {Done: Ludovic Brenta } [src:libaws] 
libaws: build-dependency not satisfiable in sid
Added tag(s) sid and jessie.
> tag 764440 + sid jessie
Bug #764440 [ruby-activemodel-3.2,ruby-protected-attributes] 
ruby-protected-attributes and ruby-activemodel-3.2: error when trying to 
install together
Added tag(s) sid and jessie.
> tag 76 + sid jessie
Bug #76 [src:libalog] libalog: build-depends on cruft package 
libaws2.10.2-dev
Added tag(s) sid and jessie.
> tag 764441 + sid jessie
Bug #764441 [slurm-client,sinfo] sinfo and slurm-client: error when trying to 
install together
Added tag(s) sid and jessie.
> tag 764357 + sid jessie
Bug #764357 [ssdeep] non-free file in package
Added tag(s) sid and jessie.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
764357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764357
764440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764440
764441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764441
76: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
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: NOT jessie

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 764268 -sid -jessie
Bug #764268 {Done: Ludovic Brenta } [src:libaws] 
libaws: build-dependency not satisfiable in sid
Removed tag(s) sid.
Bug #764268 {Done: Ludovic Brenta } [src:libaws] 
libaws: build-dependency not satisfiable in sid
Removed tag(s) jessie.
> tags 76 -jessie
Bug #76 [src:libalog] libalog: build-depends on cruft package 
libaws2.10.2-dev
Removed tag(s) jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
76: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
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#763625: keepnote fails with Attempt to unlock mutex that was not locked

[Vlad Orlov]

 Hi,

Guys, thanks for spotting this. Indeed, I haven't tested keepnote with
creating a new notebook (my bad).

Unfortunately, as I've tried to dig deeper into the issue, I found out that
keepnote now simply segfaults on start:

keepnote[3028]: segfault at 0 ip   (null) sp 7fff4794a738 error 14 
in python2.7[40+31c000]

This is probably due to some recent updates in Debian Testing, because
some other Python apps crash with segfault as well.
If I'll manage to find a fix or a workaround, I'll continue the investigation.

Bug#754623: NMU defdiff for percona-xtradb-cluster-galera-2.x_175-2.1 archs

[Aníbal Monsalve Salazar]

debdiff percona-xtradb-cluster-galera-2.x_175-2.dsc 
percona-xtradb-cluster-galera-2.x_175-2.1.dsc
diff -Nru percona-xtradb-cluster-galera-2.x-175/debian/changelog 
percona-xtradb-cluster-galera-2.x-175/debian/changelog
--- percona-xtradb-cluster-galera-2.x-175/debian/changelog  2014-06-18 
17:41:42.0 +0100
+++ percona-xtradb-cluster-galera-2.x-175/debian/changelog  2014-08-15 
11:18:08.0 +0100
@@ -1,3 +1,14 @@
+percona-xtradb-cluster-galera-2.x (175-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix difference in alignment of long long for MIPS ISA and IA32.
+Use corresponding __atomic_* from libatomic library.
+Add fix-mips.patch.
+Patch by Dejan Latinovic .
+Closes: #754623.
+
+ -- Anibal Monsalve Salazar   Fri, 15 Aug 2014 11:18:03 
+0100
+
 percona-xtradb-cluster-galera-2.x (175-2) unstable; urgency=medium
 
   * d/p/detect-atomic.patch: Add check to determine whether -latomic is 
required
diff -Nru percona-xtradb-cluster-galera-2.x-175/debian/patches/fix-mips.patch 
percona-xtradb-cluster-galera-2.x-175/debian/patches/fix-mips.patch
--- percona-xtradb-cluster-galera-2.x-175/debian/patches/fix-mips.patch 
1970-01-01 01:00:00.0 +0100
+++ percona-xtradb-cluster-galera-2.x-175/debian/patches/fix-mips.patch 
2014-08-15 11:11:22.0 +0100
@@ -0,0 +1,129 @@
+Date: Wed, 13 Aug 2014 16:30:32 +0100
+From: Dejan Latinovic 
+Subject: fix for percona-xtradb-cluster-galera-2.x
+
+package percona-xtradb-cluster-galera-2.x FTBFS for mips/mipsel with an error:
+
+> galerautils/src/gu_rand.c: In function 'gu_rand_seed_long':
+> galerautils/src/gu_mmh3.h:195:21: error: '*((void *)&rse+23)' is used 
uninitialized in this function [-Werror=uninitialized]
+>  case  8: k1 ^= ((uint64_t)tail[ 7]) << 56;
+
+https://buildd.debian.org/status/fetch.php?pkg=percona-xtradb-cluster-galera-2.x&arch=mipsel&ver=175-2&stamp=1403112913
+
+This problem is reported here:
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754623
+
+The reason for this failure is a difference in alignment of long long for MIPS
+ISA and IA32.  This results that size of gu_rse structure on mips is 24,
+instead of expected 20 (on ia32).
+
+As long long is first attribute in structure, so it is safe to use pack(4). 
+
+> struct gu_rse
+> {
+> long long   time;
+> const void* heap_ptr;
+> const void* stack_ptr;
+> longpid;
+> };
+
+I assume that this fix could be used for other architectures like: armel,
+armhf, powerpc, sparc.  I did not have a chance to test it on those
+architectures, so my changes affects only mips and mipsel.
+
+Solving this issue, fallowing error appears:
+
+> gcs/src/gcs.c:1161: undefined reference to `__sync_fetch_and_add_8'
+
+Mips platform does not have 64-bit __sync_* operations.  To avoid this
+behaviuor it is needed to use corresponding __atomic_* from libatomic library.
+
+Patch that solves both issues for mips/mipsel is attached.
+
+Index: percona-xtradb-cluster-galera-2.x-175/SConstruct
+===
+--- percona-xtradb-cluster-galera-2.x-175.orig/SConstruct
 percona-xtradb-cluster-galera-2.x-175/SConstruct
+@@ -368,7 +368,7 @@ else:
+ print 'Not using boost'
+ 
+ # Check to see if -latomic is need for GCC atomic built-ins.
+-if conf.CheckLib(library='atomic', symbol='__sync_fetch_and_add_8'):
++if conf.CheckLib(library='atomic', symbol='__sync_fetch_and_add_8') or 
conf.CheckLib(library='atomic', symbol='__atomic_fetch_add_8'):
+ conf.env.Append(LIBS=['atomic'])
+ 
+ # asio
+Index: percona-xtradb-cluster-galera-2.x-175/galerautils/src/gu_atomic.h
+===
+--- percona-xtradb-cluster-galera-2.x-175.orig/galerautils/src/gu_atomic.h
 percona-xtradb-cluster-galera-2.x-175/galerautils/src/gu_atomic.h
+@@ -11,6 +11,8 @@
+ 
+ #ifdef __GNUC__
+ 
++#if !defined(__mips__) || defined(__mips64)
++
+ #define gu_sync_fetch_and_add  __sync_fetch_and_add
+ #define gu_sync_fetch_and_sub  __sync_fetch_and_sub
+ #define gu_sync_fetch_and_or   __sync_fetch_and_or
+@@ -26,6 +28,28 @@
+ #define gu_sync_xor_and_fetch  __sync_xor_and_fetch
+ #define gu_sync_nand_and_fetch __gu_sync_nand_and_fetch
+ 
++#else  /* __mips__ */
++
++/* Mips platform does not have 64-bit __sync_* operations.
++ * so it is needed to use corresponding __atomic_* operations from libatomic 
library. */
++
++#define gu_sync_fetch_and_add(value_, x)  __atomic_fetch_add(value_, x, 
__ATOMIC_SEQ_CST)
++#define gu_sync_fetch_and_sub(value_, x)  __atomic_fetch_sub(value_, x, 
__ATOMIC_SEQ_CST)
++#define gu_sync_fetch_and_or(value_, x)   __atomic_fetch_or(value_, x, 
__ATOMIC_SEQ_CST)
++#define gu_sync_fetch_and_and(value_, x)  __atomic_fetch_and(value_, x, 
__ATOMIC_SEQ_CST)
++#define gu_sync_fetch_and_xor(value_, x)  __atomic_fetch_xor(value_, x, 
__ATOMIC_SEQ_CST)
++#define gu_sync_fetch_and_nand(value_, x) __atomic_fetch_nand(value_, x, 
__ATOMIC_SEQ_CST

Bug#763228: Processed: g++ producing overlapping exception frames [was: Re: Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value]

[Matthias Klose]

Am 08.10.2014 um 09:34 schrieb Michael Tautschnig:
> Hi Matthias,
> 
> [...]
>> afaics not a GCC issue. please recheck with binutils 2.24.51.20141001-3
>>
> 
> This *is* binutils 2.24.51.20141001-3:
> 
> # zcat /usr/share/doc/binutils/changelog.Debian.gz | head -n 1
> binutils (2.24.51.20141001-3) unstable; urgency=medium
> 
> And indeed only this version would yield the more detailed list of overlapping
> .eh_frame_hdr, rather than merely saying that there were some as was the case 
> in
> 2.24.51.20141001-1. Though this doesn't seem to be an issue of zero-sized
> exception handling frames, as was discussed in the context of Mesa and Clang.
> 
> So if it isn't a GCC issue, should I reassign to binutils instead? (I have no
> intention of playing a bug-assigning ping-pong, but I do fail to see what 
> might
> be wrong in CBMC. But I'm happy to assist by providing any input that would be
> deemed useful.)

Both the abr and the cbmc package builds link the .a files using ld -r, not with
ar rcf. at least I can workaround this link failure for now when building the
package this way.

Filed upstream https://sourceware.org/bugzilla/show_bug.cgi?id=17467


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764196: marked as done (maildir-utils: FTBFS on arm*)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 09:23:26 +
with message-id 
and subject line Bug#764196: fixed in maildir-utils 0.9.9.6-5
has caused the Debian Bug report #764196,
regarding maildir-utils: FTBFS on arm*
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.)


-- 
764196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maildir-utils
Version: 0.9.9.6-4
Severity: serious
Justification: FTBFS



Hello,

  Your package fails to build from source on Debian autobuilder network.

  Please check your package build logs at:
  

make[3]: Entering directory '/«PKGBUILDDIR»/guile'
/usr/bin/guile-snarf -o mu-guile.x mu-guile.c -DHAVE_CONFIG_H -I. -I.. -I../lib 
-pthread -I/usr/include/guile/2.0  -pthread -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include   -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall -I. -I.. 
-I../lib -pthread -I/usr/include/guile/2.0  -pthread -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
/usr/bin/guile-snarf: 54: /usr/bin/guile-snarf: gcc-4.8: not found
make[3]: *** [mu-guile.x] Error 1
Makefile:1155: recipe for target 'mu-guile.x' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/guile'



  Full log:

https://buildd.debian.org/status/fetch.php?pkg=maildir-utils&arch=armhf&ver=0.9.9.6-4&stamp=1412581604

Best regards


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Foreign Architectures: armhf

Kernel: Linux 3.14-2-686-pae (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
--- End Message ---
--- Begin Message ---
Source: maildir-utils
Source-Version: 0.9.9.6-5

We believe that the bug you reported is fixed in the latest version of
maildir-utils, 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 764...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated maildir-utils 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Oct 2014 08:57:14 +0900
Source: maildir-utils
Binary: maildir-utils mu4e maildir-utils-extra
Architecture: source all amd64
Version: 0.9.9.6-5
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining 
Changed-By: Norbert Preining 
Description:
 maildir-utils - Set of utilities to deal with Maildirs (upstream name mu)
 maildir-utils-extra - Extra utilities for maildir-utils
 mu4e   - e-mail client for Emacs based on mu (maildir-utils)
Closes: 764196
Changes:
 maildir-utils (0.9.9.6-5) unstable; urgency=medium
 .
   * bump build-dep version for guile-2.0-dev another time, arm build
 failures (Closes: #764196)
Checksums-Sha1:
 4a451da494b02da7174839bb2a6a2495a6f045f0 2227 maildir-utils_0.9.9.6-5.dsc
 c6640e433d7fa213fe3cb5d74ab6bb19ac478bcc 8692 
maildir-utils_0.9.9.6-5.debian.tar.xz
 93b9c8c9011f4dc17de3b9c04920c2050878e968 178484 mu4e_0.9.9.6-5_all.deb
 993d098e32c5e9c1aa6cbcd287154826d729677d 268866 
maildir-utils_0.9.9.6-5_amd64.deb
 1a977a91271b7149071289a2974c270cec4ffb93 107348 
maildir-utils-extra_0.9.9.6-5_amd64.deb
Checksums-Sha256:
 abb83475733eb4af288c689ab7b90b326c0ab7de90370bb097b3e4c82cdf54ca 2227 
maildir-utils_0.9.9.6-5.dsc
 0cfd1469f54e5e516f843496fd3002a3db08654173dda1f865a4ede39d2a29ae 8692 
maildir-utils_0.9.9.6-5.debian.tar.xz
 a8b77411229625f92806e94b655e94fad229234dce114be5c7c83f701a672993 178484 
mu4e_0.9.9.6-5_all.deb
 1fad3302063c6e5ddebbbc820e801e7d288a82f17ed344e013de17547871eaac 268866 
maildir-utils_0.9.9.6-5_amd64.deb
 9903c9d1a290e6e2badb320f6c93b2817f01c3c9885446fd699bd879f20e10ee 107348 
maildir-utils-extra_0.9.9.6-5_amd64.deb
Files:
 096bbeae8f306ab27cfda7b5177beae5 2227 mail optional maildir-utils_0.9.9.6-5.dsc
 a8c7dab72955b42e1e7a4e27ab67d27c 8692 mail optional 
maildir-utils_0.9.9.6-5.debian.tar.xz
 ca78136c3b118227f0382196c7737a3b 178484 lisp optional mu4e_0.9.9.6-5_all.deb
 bc477c4fa3a0bb94ad8ad470

Bug#750857: marked as done (FTBFS on many architectures, test suite errors)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 09:23:33 +
with message-id 
and subject line Bug#750857: fixed in mod-gnutls 0.6-1.1
has caused the Debian Bug report #750857,
regarding FTBFS on many architectures, test suite errors
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.)


-- 
750857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mod-gnutls
Version: 0.6-1
Severity: serious

Hi,

Your package failed to build on many architectures where it built before,
thus preventing testing migration. See:

https://buildd.debian.org/status/package.php?p=mod-gnutls

Emilio

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: mod-gnutls
Source-Version: 0.6-1.1

We believe that the bug you reported is fixed in the latest version of
mod-gnutls, 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.
Anibal Monsalve Salazar  (supplier of updated mod-gnutls 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Oct 2014 08:16:43 +0100
Source: mod-gnutls
Binary: libapache2-mod-gnutls
Architecture: source mips
Version: 0.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Anibal Monsalve Salazar 
Description:
 libapache2-mod-gnutls - Apache module for SSL and TLS encryption with GnuTLS
Closes: 750857
Changes:
 mod-gnutls (0.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use 127.0.0.1 for TEST_IP.
 Add test-ip.patch.
 Patch by Jurica Stanojkovic .
 Closes: #750857.
Checksums-Sha1:
 2a9f5df1120adca48eb83210fd98432d97f0a887 1985 mod-gnutls_0.6-1.1.dsc
 731733210b2742ee18322494fb7b140a39ff49bf 18220 mod-gnutls_0.6-1.1.debian.tar.xz
 c783ab75edbebadc36eba3252fdf51a9566a7662 43238 
libapache2-mod-gnutls_0.6-1.1_mips.deb
Checksums-Sha256:
 9f242474bb7a405cbcc34bb878598542f7e5bd5b849ec237aca67f87133eb5f4 1985 
mod-gnutls_0.6-1.1.dsc
 5f1570b468698cc241d272f61f83a6c40a840d066353e9cbfff0923123533cb4 18220 
mod-gnutls_0.6-1.1.debian.tar.xz
 a1c68984c4936596abf2c3896f2d958000394b0e8e7470dd45045df38311589e 43238 
libapache2-mod-gnutls_0.6-1.1_mips.deb
Files:
 a884b6c5ee3b4f162290e5c2ee91b09d 1985 httpd extra mod-gnutls_0.6-1.1.dsc
 06df64c9ab9f7ae78e0c8551f467287d 18220 httpd extra 
mod-gnutls_0.6-1.1.debian.tar.xz
 276f5619ab0b3673aa789fb30b243602 43238 httpd extra 
libapache2-mod-gnutls_0.6-1.1_mips.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJUNO6PAAoJEHxWrP6UeJfYniAQAMWCJ+16UALzAKgARAd6ff1q
ng3+fChyTyFF6ZhPxiEaWW0ZA3J44YamX7I2zWmPadhGYH8/xWwsTR8TAnjFEUFt
dSdOhfpC0wcfoGDVr5WotfyYrfaSYh2n2nZ0037zbjapd42MVQWQPT8caxOwT3NY
o44zAKUaoPvjMOLoWdOG2qQ9eFDS/MW/WVCcdIGGXvXFYHUhYp18UKMheRnVLRKX
qhz89149jGsq80GNDRhZGWQI7ipmsrG91Sv/ARzdFSl5A3EOFS8E8LHrQS8Iauxq
HLr+3yrb5ZZL3XNCO656RnZP/95elSdqqy9/FXnFXUka1PGQsr1dNfA/DcU+nfn3
DVKB3ojOdzzusOp1kjHfz7aJVdtxPBBptRbL/Je2wlWGOZx4nPQVLE4Y7Tk8GJAm
Ys+bGrwM0wJyDyf/S39Zy8vpEybaz98GOUW2StV8xO79Sivvh1BuZxo7ch9WJ0/Q
IkfN8U84A6wDZiGznaA5rHYwHWFi9WfCHgP5EcPr4hFk7usJQ4RC/LBosNPk26+e
/WWi9hPEI59RqvQZz87lG6y01zC7lHlLlmQ5XrO1geNJTuUvu77LhzYyofrOrlg7
dg/Ozbnip4DXwIp4v+uuUNPEf6BC9dealBnuPmYPGni+/b5CmS0ZAOa5GD0W0tAp
oeEZxPF81RRomZEn30TB
=tAtX
-END PGP SIGNATURE End Message ---

Bug#754623: marked as done (percona-xtradb-cluster-galera-2.x: FTBFS on many archs)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 09:23:54 +
with message-id 
and subject line Bug#754623: fixed in percona-xtradb-cluster-galera-2.x 175-2.1
has caused the Debian Bug report #754623,
regarding percona-xtradb-cluster-galera-2.x: FTBFS on many archs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: percona-xtradb-cluster-galera-2.x
Version: 175-2
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on many archs. Build excerpt from powerpc:
| gcc -o galerautils/src/gu_rand.o -c -std=c99 -fno-strict-aliasing -pipe -g 
-O3 -DNDEBUG -Wall -Wextra -Wno-unused-parameter -pedantic -pthread 
-D_XOPEN_SOURCE=600 -DHAVE_COMMON_H -DGALERA_USE_GU_NETWORK -DHAVE_BYTESWAP_H 
-DHAVE_ENDIAN_H -DHAVE_BOOST_SHARED_PTR_HPP -DHAVE_TR1_UNORDERED_MAP 
-DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG=1 -DHAVE_ASIO_HPP -DHAVE_ASIO_SSL_HPP 
-Werror -Icommon -Iasio -Igalerautils/src -Igcomm/src -Igcomm/src/gcomm 
-Igcache/src -Igcs/src -Iwsdb/src -Igalera/src galerautils/src/gu_rand.c
| In file included from galerautils/src/gu_hash.h:30:0,
|  from galerautils/src/gu_rand.c:15:
| galerautils/src/gu_rand.c: In function 'gu_rand_seed_long':
| galerautils/src/gu_mmh3.h:195:21: error: '*((void *)&rse+23)' is used 
uninitialized in this function [-Werror=uninitialized]
|  case  8: k1 ^= ((uint64_t)tail[ 7]) << 56;
|  ^
| galerautils/src/gu_rand.c:32:14: note: '*((void *)&rse+23)' was declared here
|  gu_rse_t rse = { time, heap_ptr, &time, pid };
|   ^
| In file included from galerautils/src/gu_hash.h:30:0,
|  from galerautils/src/gu_rand.c:15:
| galerautils/src/gu_mmh3.h:196:21: error: '*((void *)&rse+22)' is used 
uninitialized in this function [-Werror=uninitialized]
|  case  7: k1 ^= ((uint64_t)tail[ 6]) << 48;
|  ^
| galerautils/src/gu_rand.c:32:14: note: '*((void *)&rse+22)' was declared here
|  gu_rse_t rse = { time, heap_ptr, &time, pid };
|   ^
| In file included from galerautils/src/gu_hash.h:30:0,
|  from galerautils/src/gu_rand.c:15:
| galerautils/src/gu_mmh3.h:197:21: error: '*((void *)&rse+21)' is used 
uninitialized in this function [-Werror=uninitialized]
|  case  6: k1 ^= ((uint64_t)tail[ 5]) << 40;
|  ^
| galerautils/src/gu_rand.c:32:14: note: '*((void *)&rse+21)' was declared here
|  gu_rse_t rse = { time, heap_ptr, &time, pid };
|   ^
| In file included from galerautils/src/gu_hash.h:30:0,
|  from galerautils/src/gu_rand.c:15:
| galerautils/src/gu_mmh3.h:198:21: error: '*((void *)&rse+20)' is used 
uninitialized in this function [-Werror=uninitialized]
|  case  5: k1 ^= ((uint64_t)tail[ 4]) << 32;
|  ^
| galerautils/src/gu_rand.c:32:14: note: '*((void *)&rse+20)' was declared here
|  gu_rse_t rse = { time, heap_ptr, &time, pid };
|   ^
| cc1: all warnings being treated as errors
| scons: *** [galerautils/src/gu_rand.o] Error 1

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=percona-xtradb-cluster-galera-2.x&arch=powerpc&ver=175-2&stamp=1404609797

Build log summary:
  
https://buildd.debian.org/status/package.php?p=percona-xtradb-cluster-galera-2.x&suite=sid

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: percona-xtradb-cluster-galera-2.x
Source-Version: 175-2.1

We believe that the bug you reported is fixed in the latest version of
percona-xtradb-cluster-galera-2.x, 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.
Anibal Monsalve Salazar  (supplier of updated 
percona-xtradb-cluster-galera-2.x package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Aug 2014 11:18:03 +0100
Source: percona-xtradb-cluster-galera-2.x
Binary: percona-xtradb-cluster-galera-2.x
Architecture: source mips
Version: 175-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Ma

Bug#758499: marked as done (presage: Please update to use wxpython3.0)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 09:24:11 +
with message-id 
and subject line Bug#758499: fixed in presage 0.9-1
has caused the Debian Bug report #758499,
regarding presage: Please update to use wxpython3.0
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.)


-- 
758499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: presage
Version: 0.8.9-1
Severity: important
Tags: patch sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1

We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.

I've rebuilt presage with the attached patch.  The required change
suppresses WXDEBUG assertions, which happened by default with wx2.8.
I've also updated a couple of constant names - wxPython 3.0 still
provides the old names, but they're gone in the C++ API, so they're
likely to disappear from wxPython in the next release.

Both changes should be compatible with wxPython 2.8.

I've tested the pyprompter app with these changes, and it seems to
work correctly.

I'm happy to NMU these changes.

Cheers,
Olly
diff -Nru presage-0.8.9/debian/changelog presage-0.8.9/debian/changelog
--- presage-0.8.9/debian/changelog	2013-10-03 10:28:47.0 +1300
+++ presage-0.8.9/debian/changelog	2014-08-18 19:09:09.0 +1200
@@ -1,3 +1,10 @@
+presage (0.8.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update to depend on python-wxgtk3.0.
+
+ -- Olly Betts   Mon, 18 Aug 2014 18:54:57 +1200
+
 presage (0.8.9-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru presage-0.8.9/debian/control presage-0.8.9/debian/control
--- presage-0.8.9/debian/control	2013-10-03 10:28:47.0 +1300
+++ presage-0.8.9/debian/control	2014-08-18 18:54:41.0 +1200
@@ -14,7 +14,7 @@
  swig2.0 (>= 2.0.4),
  libgtk2.0-dev (>= 2.12),
  python-dbus,
- python-wxgtk2.8
+ python-wxgtk3.0
 Build-Depends-Indep: doxygen, graphviz
 Standards-Version: 3.9.4
 Homepage: http://presage.sourceforge.net/
@@ -178,7 +178,7 @@
 Depends: ${python:Depends},
  ${misc:Depends},
  python-presage (>= ${source:Version}),
- python-wxgtk2.8 (>= 2.8.7)
+ python-wxgtk3.0
 Description: intelligent predictive wxPython text editor
  This package contains the wxPython predictive text editor pyprompter.
  .
--- End Message ---
--- Begin Message ---
Source: presage
Source-Version: 0.9-1

We believe that the bug you reported is fixed in the latest version of
presage, 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.
Matteo Vescovi  (supplier of updated presage 
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, 28 Sep 2014 14:20:39 +0100
Source: presage
Binary: presage presage-dbg libpresage-doc libpresage1 libpresage1-dbg 
libpresage-data libpresage-dev python-presage python-presage-dbg gprompter 
gprompter-dbg pyprompter presage-dbus
Architecture: source all
Version: 0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Matteo Vescovi 
Changed-By: Matteo Vescovi 
Description:
 gprompter  - intelligent predictive GTK+ text editor
 gprompter-dbg - intelligent predictive GTK+ text editor (debugging symbols)
 libpresage-data - intelligent predictive text entry platform (data files)
 libpresage-dev - intelligent predictive text entry platform (development files)
 libpresage-doc - intelligent predictive text entry platform (documentation)
 libpresage1 - intelligent predictive text entry platform (shared library)
 libpresage1-dbg - intelligent predictive text entry platform (shared library 
debugg
 presage- intelligent predictive text entry platform (tools and demos)
 presage-dbg - intelligent predictive text entry platform (tools debugging symbo
 presage-dbus - intelligent predictive text entry platform (D-Bus service)
 pyprompter - intelligent predictive wxPython text editor
 python-presage - intelligent predictive text entry platform (Python binding)
 python-presage-dbg - intelligent predictive t

Processed: notfound 763780 in apt/0.8.7, found 763780 in apt/0.8.11

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 763780 apt/0.8.7
Bug #763780 {Done: Michael Vogt } [apt] apt-get: 
CVE-2014-7206: Insecure temporary changelog handling
No longer marked as found in versions apt/0.8.7.
> found 763780 apt/0.8.11
Bug #763780 {Done: Michael Vogt } [apt] apt-get: 
CVE-2014-7206: Insecure temporary changelog handling
Marked as found in versions apt/0.8.11.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763780
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#763228: Processed: g++ producing overlapping exception frames [was: Re: Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value]

[Michael Tautschnig]

Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=17467

Hi again,

[...]
> > So if it isn't a GCC issue, should I reassign to binutils instead? (I have 
> > no
> > intention of playing a bug-assigning ping-pong, but I do fail to see what 
> > might
> > be wrong in CBMC. But I'm happy to assist by providing any input that would 
> > be
> > deemed useful.)
> 
> Both the abr and the cbmc package builds link the .a files using ld -r, not 
> with
> ar rcf. at least I can workaround this link failure for now when building the
> package this way.
> 

This appears consistent with my report that passing all the object files makes
things work. So surely I can use this as workaround, but really using ld -r
should be fine - or am I wrong here?

> Filed upstream https://sourceware.org/bugzilla/show_bug.cgi?id=17467
> 

Thanks a lot!

Do you want to take this one under the binutils umbrella, possibly with non-RC
severity as a workaround exists?

Best,
Michael



pgp_HfEWC49Mq.pgp
Description: PGP signature

Processed: Re: Processed: g++ producing overlapping exception frames [was: Re: Bug#763228: cbmc: FTBFS: ld: final link failed: Bad value]

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=17467
Bug #763228 [src:cbmc] cbmc: FTBFS: ld: final link failed: Bad value
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=17467'.

-- 
763228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763228
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#763855: xchat: FTBFS on linux-any

[Svante Signell]

Hi,

I just tried to compile xchat on a Linux amd64 box, and the linking
problem is present also there. The attached patch configure.in.patch
solves the build problem, at least for linux, kfreebsd and hurd.
Attached is a patch for debian/rules too. autoconf works (with
warnings), putting dh_autoreconf there (or running auotreconf manually)
does not work. Some work is needed to make autoreconf working if needed.

Thanks!
--- a/configure.in	2010-05-30 08:01:16.0 +0200
+++ b/configure.in	2014-10-08 12:07:44.097529411 +0200
@@ -445,8 +445,7 @@
 	if test "$have_dl" = yes; then
 		AC_DEFINE(USE_PLUGIN)
 		AC_PATH_PROG(pkgconfigpath, pkg-config)
-		dnl we just need the -Wl,--export-dynamic, but not -lgmodule-2.0
-		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs | $sedpath 's/ -lgmodule-2.0//'`"
+		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs`"
 		LIBS="$LIBS $RDYNAMIC_FLAGS"
 		if test "$LD" = ""; then
 			VS="`ld --help | grep version-script 2> /dev/null`"
--- a/debian/rules	2012-04-01 18:31:46.0 +0200
+++ b/debian/rules	2014-10-08 12:07:06.157529416 +0200
@@ -10,6 +10,7 @@
 
 configure: configure-stamp
 configure-stamp:
+	autoconf
 	[ -f config.sub.d-r-orig ] || cp -p config.sub config.sub.d-r-orig
 	[ -f config.guess.d-r-orig ] || cp -p config.guess config.guess.d-r-orig
 	cp -f /usr/share/misc/config.sub .

Bug#763855: xchat: FTBFS on linux-any

[Svante Signell]

Hi,

I just tried to compile xchat on a Linux amd64 box, and the linking
problem is present also there. The attached patch configure.in.patch
solves the build problem, at least for linux, kfreebsd and hurd.
Attached is a patch for debian/rules too. autoconf works (with
warnings), putting dh_autoreconf there (or running autoreconf manually)
does not work. Some work is needed to make autoreconf working if needed.

Thanks!
--- a/configure.in	2010-05-30 08:01:16.0 +0200
+++ b/configure.in	2014-10-08 12:07:44.097529411 +0200
@@ -445,8 +445,7 @@
 	if test "$have_dl" = yes; then
 		AC_DEFINE(USE_PLUGIN)
 		AC_PATH_PROG(pkgconfigpath, pkg-config)
-		dnl we just need the -Wl,--export-dynamic, but not -lgmodule-2.0
-		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs | $sedpath 's/ -lgmodule-2.0//'`"
+		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs`"
 		LIBS="$LIBS $RDYNAMIC_FLAGS"
 		if test "$LD" = ""; then
 			VS="`ld --help | grep version-script 2> /dev/null`"
--- a/debian/rules	2012-04-01 18:31:46.0 +0200
+++ b/debian/rules	2014-10-08 12:07:06.157529416 +0200
@@ -10,6 +10,7 @@
 
 configure: configure-stamp
 configure-stamp:
+	autoconf
 	[ -f config.sub.d-r-orig ] || cp -p config.sub config.sub.d-r-orig
 	[ -f config.guess.d-r-orig ] || cp -p config.guess config.guess.d-r-orig
 	cp -f /usr/share/misc/config.sub .

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

[Vlad Orlov]

Follow-up:

Ok, I've found out that the segfaults were caused by GTK+3 hack [1] which
I've been testing yesterday and haven't turned off afterwards.
Now keepnote and other Python apps run fine, so I'll continue investigating
the mutex issue.

Don't ask me how a GTK+3 hack could possibly affect Python apps that are
using GTK+2 - I have no idea :)


[1] https://bugs.debian.org/744249#127

Bug#763780: apt-get: Insecure temporary changelog handling

[Guillem Jover]

Hi!

On Wed, 2014-10-08 at 10:42:07 +0200, Michael Vogt wrote:
> On Thu, Oct 02, 2014 at 06:29:45PM +0200, Guillem Jover wrote:
> > Package: apt
> > Version: 0.8.7
> > Severity: serious
> > Tags: security patch

> > Attached a patch fixing this. This affects all versions starting from
> > the one in squeeze.

> > I'm not sure if this deserves a CVE or perhaps a lower severity?
> [..]
> 
> I uploaded a fix for wheezy now, squeeze is not affected, this feature
> got added in 0.8.11 in debian so we should be safe here.

Oh, indeed, sorry about the wrong version. I was confused by the git
history:

  $ git show a4c404301df135bea81f23b944dc6e1967f9ca85
  $ git describe --tags a4c404301df135bea81f23b944dc6e1967f9ca85
  0.8.6-22-ga4c4043

Thanks,
Guillem


-- 
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#750857: marked as done (FTBFS on many architectures, test suite errors)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #750857 {Done: Anibal Monsalve Salazar } 
[src:mod-gnutls] FTBFS on many architectures, test suite errors
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mod-gnutls/0.6-1.1.
> found -1 0.6-1.1
Bug #750857 [src:mod-gnutls] FTBFS on many architectures, test suite errors
Marked as found in versions mod-gnutls/0.6-1.1.

-- 
750857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750857
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#750857: marked as done (FTBFS on many architectures, test suite errors)

[Jonathan Wiltshire]

Control: reopen -1
Control: found -1 0.6-1.1

Hi,

On 2014-10-08 10:27, ow...@bugs.debian.org wrote:

 mod-gnutls (0.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use 127.0.0.1 for TEST_IP.
 Add test-ip.patch.
 Patch by Jurica Stanojkovic .
 Closes: #750857.


This change now causes test suite failures on amd64 and powerpc instead, 
where they previously built.


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 763625 http://code.google.com/p/keepnote/issues/detail?id=709
Bug #763625 [keepnote] keepnote fails with Attempt to unlock mutex that was not 
locked
Set Bug forwarded-to-address to 
'http://code.google.com/p/keepnote/issues/detail?id=709'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
763625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763625
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: fixed 763780 in 1.1~exp4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 763780 1.1~exp4
Bug #763780 {Done: Michael Vogt } [apt] apt-get: 
CVE-2014-7206: Insecure temporary changelog handling
Marked as fixed in versions apt/1.1~exp4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763780
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#749844: marked as done (xaralx: wxwidgets3.0 transition)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 11:14:37 +
with message-id 
and subject line Bug#764456: Removed package(s) from unstable
has caused the Debian Bug report #749844,
regarding xaralx: wxwidgets3.0 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.)


-- 
749844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xaralx
Version: 0.7r1785-7
Severity: serious
Justification: Blocks an on-going transition
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Control: block 748169 by -1

Dear maintainer,

We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.

When I spoke to you about this at the Cambridge minidebconf last year,
you said you were OK to remove xaralx.  The transition is starting to
progress rapidly, so I just wanted to check that nothing had changed
which might affect that plan.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Version: 0.7r1785-7+rm

Dear submitter,

as the package xaralx has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/764456

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#763255: marked as done (Rebuild with libjpeg-dev)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 11:34:26 +
with message-id 
and subject line Bug#763255: fixed in freeimage 3.15.4-4.1
has caused the Debian Bug report #763255,
regarding Rebuild with libjpeg-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.)


-- 
763255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
Version: 3.15.4-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> g++ -shared -Wl,-soname,libfreeimage.so.3 -Wl,-z,defs -Wl,-z,relro -o 
> libfreeimage-3.15.4.so ./Source/FreeImage/BitmapAccess.o 
> ./Source/FreeImage/ColorLookup.o ./Source/FreeImage/FreeImage.o 
> ./Source/FreeImage/FreeImageC.o ./Source/FreeImage/FreeImageIO.o 
> ./Source/FreeImage/GetType.o ./Source/FreeImage/MemoryIO.o 
> ./Source/FreeImage/PixelAccess.o ./Source/FreeImage/J2KHelper.o 
> ././Source/FreeImage/MNGHelper.o ./Source/FreeImage/Plugin.o 
> ./Source/FreeImage/PluginBMP.o ./Source/FreeImage/PluginCUT.o 
> ./Source/FreeImage/PluginDDS.o ./Source/FreeImage/PluginEXR.o 
> ./Source/FreeImage/PluginG3.o ./Source/FreeImage/PluginGIF.o 
> ./Source/FreeImage/PluginHDR.o ./Source/FreeImage/PluginICO.o 
> ./Source/FreeImage/PluginIFF.o ./Source/FreeImage/PluginJ2K.o 
> ././Source/FreeImage/PluginJNG.o ./Source/FreeImage/PluginJP2.o 
> ./Source/FreeImage/PluginJPEG.o ./Source/FreeImage/PluginKOALA.o 
> ./Source/FreeImage/PluginMNG.o ./Source/FreeImage/PluginPCD.o 
> ./Source/FreeImage/PluginPCX.o ./Source/FreeImage/PluginPFM.o 
> ./Source/FreeImage/PluginPICT.o ./Source/FreeImage/PluginPNG.o 
> ./Source/FreeImage/PluginPNM.o ./Source/FreeImage/PluginPSD.o 
> ./Source/FreeImage/PluginRAS.o ./Source/FreeImage/PluginRAW.o 
> ./Source/FreeImage/PluginSGI.o ./Source/FreeImage/PluginTARGA.o 
> ./Source/FreeImage/PluginTIFF.o ./Source/FreeImage/PluginWBMP.o 
> ./Source/FreeImage/PluginXBM.o ./Source/FreeImage/PluginXPM.o 
> ./Source/FreeImage/PSDParser.o ./Source/FreeImage/TIFFLogLuv.o 
> ./Source/FreeImage/Conversion.o ./Source/FreeImage/Conversion16_555.o 
> ./Source/FreeImage/Conversion16_565.o ./Source/FreeImage/Conversion24.o 
> ./Source/FreeImage/Conversion32.o ./Source/FreeImage/Conversion4.o 
> ./Source/FreeImage/Conversion8.o ./Source/FreeImage/ConversionFloat.o 
> ./Source/FreeImage/ConversionRGB16.o ./Source/FreeImage/ConversionRGBF.o 
> ./Source/FreeImage/ConversionType.o ./Source/FreeImage/ConversionUINT16.o 
> ./Source/FreeImage/Halftoning.o ./Source/FreeImage/tmoColorConvert.o 
> ./Source/FreeImage/tmoDrago03.o ./Source/FreeImage/tmoFattal02.o 
> ./Source/FreeImage/tmoReinhard05.o ./Source/FreeImage/ToneMapping.o 
> ./Source/FreeImage/NNQuantizer.o ./Source/FreeImage/WuQuantizer.o 
> ./Source/DeprecationManager/Deprecated.o 
> ./Source/DeprecationManager/DeprecationMgr.o ./Source/FreeImage/CacheFile.o 
> ./Source/FreeImage/MultiPage.o ./Source/FreeImage/ZLibInterface.o 
> ./Source/Metadata/Exif.o ./Source/Metadata/FIRational.o 
> ./Source/Metadata/FreeImageTag.o ./Source/Metadata/IPTC.o 
> ./Source/Metadata/TagConversion.o ./Source/Metadata/TagLib.o 
> ./Source/Metadata/XTIFF.o ./Source/FreeImageToolkit/Background.o 
> ./Source/FreeImageToolkit/BSplineRotate.o 
> ./Source/FreeImageToolkit/Channels.o 
> ./Source/FreeImageToolkit/ClassicRotate.o ./Source/FreeImageToolkit/Colors.o 
> ./Source/FreeImageToolkit/CopyPaste.o ./Source/FreeImageToolkit/Display.o 
> ./Source/FreeImageToolkit/Flip.o ./Source/FreeImageToolkit/JPEGTransform.o 
> ./Source/FreeImageToolkit/MultigridPoissonSolver.o 
> ./Source/FreeImageToolkit/Rescale.o ./Source/FreeImageToolkit/Resize.o 
> Source/LibJPEG/transupp.o -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fexceptions -fvisibility=hidden 
> -Wno-ctor-dtor-privacy -I. -ISource -ISource/Metadata 
> -ISource/FreeImageToolkit -pthread -I/usr/include/OpenEXR 
> -I/usr/include/libraw -I/usr/include/libpng12 -I/usr/include/x86_64-linux-gnu 
>  -lstdc++ -ljpeg -lmng -lopenjpeg -L/usr/lib/x86_64-linux-gnu -L/usr/lib -lz 
> -lIlmImf -lz -pthread -lImath -lHalf -lIex -lIlmThread -lraw -lstdc++ 
> -fopenmp -llcms2 -lpng12 -ltiff  -lm
> Source/LibJPEG/transupp.o: In function `jtransform_request_workspace':
> /«PKGBUILDDIR»/Source/LibJPEG/transupp.c:900: undefined reference to 
> `jpeg_core_output_dimensions'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
ht

Processed: gweather gir fix pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 764446 + pending
Bug #764446 [gir1.2-gweather-3.0] gir1.2-gweather-3.0: Typelib not found 
because it is in wrong location
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764446
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#720517: configuration files, ownership and dpkg-statoverride

[Ian Jackson]

Paul Gevers writes ("Re: Bug#720517: configuration files, ownership and 
dpkg-statoverride"):
> On 07-10-14 15:40, Ian Jackson wrote:
> > Also I don't see in your references an explanation from anyone as to
> > why dbconfig-common does this.
> 
> I you mean with "why": "why is it implemented this way" than that is
> exactly the question that I am asking myself looking at the code, if you
> mean "why does dbconfig-common change the ownership of cactis
> configuration file" than the answer is that you can tell dbconfig-common
> in your maintainer scripts what the (I expected initial) ownership
> should be.

Why does dbconfig-common have this feature ?

Why does cactis use it ?

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764472: cups creates millions of temporary files when printing

[Antonio Sartori]

Package: cups
Version: 1.7.5-4
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

When trying to print (tried twice from evince, not tested from other software), 
cups creates millions of symbolic links in /tmp to the ppd driver in 
/etc/cups/ppd. The names of the symbolic links are similar to 54351da228fae.

This causes the system to hang on the next reboot while systemd tries to empty 
the tmp folder, making the system unbootable.

Notice that deleting the files by hand is tricky, since they are too many (rm 
does not work, it is not even possible to list the files with ls), I don't know 
how to do this. For now, I rebooted the system using a live dist and I typed mv 
/tmp /tmp2. This enables the system to boot again. Help on how I can delete the 
folder tmp2 would also be appreciated.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-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 cups depends on:
ii  cups-client1.7.5-4
ii  cups-common1.7.5-4
ii  cups-core-drivers  1.7.5-4
ii  cups-daemon1.7.5-4
ii  cups-filters   1.0.59-1
ii  cups-ppdc  1.7.5-4
ii  cups-server-common 1.7.5-4
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.06~dfsg-1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.19-11
ii  libc6  2.19-11
ii  libcups2   1.7.5-4
ii  libcupscgi11.7.5-4
ii  libcupsimage2  1.7.5-4
ii  libcupsmime1   1.7.5-4
ii  libcupsppdc1   1.7.5-4
ii  libgcc11:4.9.1-16
ii  libstdc++6 4.9.1-16
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13
ii  poppler-utils  0.26.5-1
ii  procps 2:3.3.9-8

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.2.1-1+b1
ii  cups-filters [ghostscript-cups]  1.0.59-1
ii  printer-driver-gutenprint5.2.10-3

Versions of packages cups suggests:
ii  cups-bsd   1.7.5-4
pn  cups-pdf   
ii  foomatic-db-compressed-ppds [foomatic-db]  20140730-1
ii  hplip  3.14.6-1
ii  printer-driver-hpcups  3.14.6-1
ii  smbclient  2:4.1.11+dfsg-2
ii  udev   215-5+b1

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#760038: minor problem subsists

[Sébastien NOBILI]

Hi,

I just ran how-can-i-help and noticed e17 is planned to be dropped from Jessie
because of this bug.

I'm working everyday with Jessie version of e17 and never noticed any
black-screen problem.

Crashes happen from time to time, but are really occasional and always followed
by an automatic restart. This point is just a matter of clicking a button to
restart the environment.

These two issues don't seem grave enough to legitimate e17 being dropped.

Is there anything I've missed in this decision ?

Sébastien


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#737440: marked as done ([src:mono-tools] Sourceless file (minified) (jquery))

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 12:04:47 +
with message-id 
and subject line Bug#737440: fixed in mono-tools 3.10-1
has caused the Debian Bug report #737440,
regarding [src:mono-tools] Sourceless file (minified) (jquery)
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.)


-- 
737440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mono-tools 
Version: 2.11+git20131009.5b1ef35-1
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org


I could not find the source of:
mono-tools 2.11+git20131009.5b1ef35-1 (source)

webdoc/plugins/iframe-plugin/jquery.iframe-auto-height-plugin.1.9.0.min.js





Bastien
--- End Message ---
--- Begin Message ---
Source: mono-tools
Source-Version: 3.10-1

We believe that the bug you reported is fixed in the latest version of
mono-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 737...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated mono-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: SHA1

Format: 1.8
Date: Wed, 08 Oct 2014 12:45:51 +0100
Source: mono-tools
Binary: monodoc-browser mono-tools-gui mono-tools-devel gendarme mono-profiler 
monodoc-http
Architecture: source all
Version: 3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mono Group 
Changed-By: Jo Shields 
Description:
 gendarme   - extensible rule-based checker for CLI assemblies
 mono-profiler - Mono profiler
 mono-tools-devel - Various development tools for mono
 mono-tools-gui - Various GUI tools for mono
 monodoc-browser - MonoDoc GTK+ based viewer
 monodoc-http - MonoDoc http based viewer
Closes: 737440
Changes:
 mono-tools (3.10-1) unstable; urgency=medium
 .
   * [25b8caf] Imported Upstream version 3.10
   * [1771e9d] Add missing source for minified Javascript (Closes: #737440)
Checksums-Sha1:
 90702f81f150b1ce2fd3fd4b3deb5cf61dcd2af8 2211 mono-tools_3.10-1.dsc
 eb042b5c8fcd4a128ed654ad6ed6b917699b99e2 2511632 mono-tools_3.10.orig.tar.gz
 57b558f5165cab6e11832db78a6af8755cf420fe 16664 mono-tools_3.10-1.debian.tar.xz
 a9525f30b630ee5dad979dc6461a940389a50d94 85146 monodoc-browser_3.10-1_all.deb
 a760e9186394dfd01ff5113103d820c8c06e0fda 134710 mono-tools-gui_3.10-1_all.deb
 7d6e681771353e78c9430936351aca5558390329 37382 mono-tools-devel_3.10-1_all.deb
 2edaac26530cd1519b37f8f983a2d53dc217652a 269788 gendarme_3.10-1_all.deb
 a1720de7e96f728eb49d3db81d05d917683e7bb6 89086 mono-profiler_3.10-1_all.deb
 a39c7dacb35d5161a3b268b52251692a33aed2ef 75878 monodoc-http_3.10-1_all.deb
Checksums-Sha256:
 1c62aeee2f8465e50f64ca7c3da85ef98abfe58e29ec7abe256c6d78d0659521 2211 
mono-tools_3.10-1.dsc
 6af9fa153f2411efb22f16ed49d5682295a55f075fa30a4cbd25a7bc8ffb8268 2511632 
mono-tools_3.10.orig.tar.gz
 83db9b9d5b240c98d8f6a37f8dff7e15bbb6acf45c695788dd0aad9f027810fd 16664 
mono-tools_3.10-1.debian.tar.xz
 d5cbe20a8e503b385ec03e5ef3aea72345e106ae7a218aca74165e1e105a7e13 85146 
monodoc-browser_3.10-1_all.deb
 d5f0d7a5266cfe1b828f9a60690a1cea039d0c030b97ab3cdc6161c19cb258cd 134710 
mono-tools-gui_3.10-1_all.deb
 19f4e9d02246887c92c293d3169711b63c0d88f9373c4f07bf77e27ffde13893 37382 
mono-tools-devel_3.10-1_all.deb
 12e76658e08bf3cbc71f2486646bf7c2d4e2147979ab160f6dea7b4b76e0d7a7 269788 
gendarme_3.10-1_all.deb
 d594ee5ea4020aa8c4e2eb895b4e17c2257773665a8dbb70613e449247d2d774 89086 
mono-profiler_3.10-1_all.deb
 4b6521e24a2233f360b214381aa16b9d40f3c6e7e2a771be944560a2c89a14c3 75878 
monodoc-http_3.10-1_all.deb
Files:
 a817c168bd185a9600b871c3575d9acc 2211 devel optional mono-tools_3.10-1.dsc
 a34d5f1b0897243bb7a9d97a41aeabbf 2511632 devel optional 
mono-tools_3.10.orig.tar.gz
 ffa7b645d76b35ca0ae72a7a419a77fb 16664 devel optional 
mono-tools_3.10-1.debian.tar.xz
 1ff4586bc7fb099aadadef119618528d 85146 devel optional 
monodoc-browser_3.10-1_all.deb
 cffdea3156d2ba5091d9c50120bdc16b 134710 devel optional 
mono-tools-gui_3.10-1_all.deb
 517cf64550687cc864f64094d2ddbd2c 37382 devel optional 
mono-tools-devel_3.10-1_all.deb
 1c1795cdd86f6c

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 735237 + pending
Bug #735237 [src:python-weberror] [python-weberror] non sourced minified 
javascript
Bug #735893 [src:python-weberror] Sourceless file
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
735237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735237
735893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735893
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#735237: marked as done ([python-weberror] non sourced minified javascript)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 13:20:20 +
with message-id 
and subject line Bug#735237: fixed in python-weberror 0.10.3+dfsg-1
has caused the Debian Bug report #735237,
regarding [python-weberror] non sourced minified javascript
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.)


-- 
735237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-weberror
Severity: serious
x-cc-debug: ftpmas...@debian.org

I could not find the source for:
weberror/eval-media/jquery-1.2.1.min.js

Bastien
--- End Message ---
--- Begin Message ---
Source: python-weberror
Source-Version: 0.10.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
python-weberror, 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 735...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated python-weberror 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Oct 2014 14:33:11 +0200
Source: python-weberror
Binary: python-weberror
Architecture: source all
Version: 0.10.3+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Shadura 
Description:
 python-weberror - Python web error handling and exception catching module
Closes: 735237
Changes:
 python-weberror (0.10.3+dfsg-1) unstable; urgency=low
 .
   [ Jakub Wilk ]
   * Use canonical URIs for Vcs-* fields.
 .
   [ Jackson Doak ]
   * Bump debhelper version to 9
   * debian/rules: Use dh
 .
   [ Federico Ceratto ]
   * Add patch to remove embedded minified JS (Closes: #735237)
   * Bump Standards-Version to 3.9.5 (no changes needed)
   * Add Pybuild dependencies
   * Install evaldemo.py example
 .
   [ Andrew Shadura ]
   * Repack the tarball to remove jQuery object files.
Checksums-Sha1:
 45d67c43927740ffe60967d72820bb01f168333a 2306 python-weberror_0.10.3+dfsg-1.dsc
 bb8a1f0ea507181c814ce619e9778117c24b2fa9 50680 
python-weberror_0.10.3+dfsg.orig.tar.gz
 efbf3170eb465cac4976713afdcd200ce900daf8 3780 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 48a9a228a928be9fa501b3db130b201aaec4558d 45098 
python-weberror_0.10.3+dfsg-1_all.deb
Checksums-Sha256:
 6de098534812a2a91c40ea00cc5bd7e5f2536f5c8102099dfc8b6478ecd93a33 2306 
python-weberror_0.10.3+dfsg-1.dsc
 c23cf11f412744272516929c04aee076a125eefd1fa03967ee8f02c60b88dc74 50680 
python-weberror_0.10.3+dfsg.orig.tar.gz
 ee73f1816f028d942215e68548dcdefb462d71b46929428b61aa2d047405f2f4 3780 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 862a3065bb70e313cbf0e352939cdff50708121f5bf586e8c04e87813e71fc00 45098 
python-weberror_0.10.3+dfsg-1_all.deb
Files:
 ec2409944612626dee329a93df0e082a 2306 python optional 
python-weberror_0.10.3+dfsg-1.dsc
 722eadecc892e2bcfe73a0dfe392108c 50680 python optional 
python-weberror_0.10.3+dfsg.orig.tar.gz
 89fb2711c5ac2ad3c395c7b60243caf1 3780 python optional 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 73cb09e2a700278ed6f6f3085dc57c1c 45098 python optional 
python-weberror_0.10.3+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJUNTJZAAoJEG6k0jEaLSaNJIQQALYWE4uvbixPBEdZd6frJOTz
4llXgQ4PUScvTpc3k3L93Is613fvSIOupmXbwMb01QrKURftWt+l3Qc8o+gaYE4Q
Ej+ZJBvNm2TmozLDZSAkidxke4oEbEN6Zv1HT7kWTHsdMDuuPCPbcSspTUjh3eyl
CB+SgRx9yocQXpZMXXdlQapdnK59wbucv8LNBM1VH1UltHN6EUUkmymGzl8xSQxN
9P4E4mpKsYViICazsLfT0Uwn7vGSmXzzQVsVbaE/at2+HeieIMyfgMZu3gCFiPUi
8I/cD4wHe3vKLT9GpEKllCbBuNX4EX6ZJMhPvIoNRTMeZE47fy4Q0PQltvkg9w7z
eAlsBeM1m4ipVL9BGj4k6I31x2qF9jvFpXoLnhHMPg5FCY2DNyD0JJDht3FiKpuj
dr7ob2+kTSH+1ldI+yUQHVynsYxv08NPfHkjoHwqS4OiSiOANJO+QMprLreZ7Mvm
tJ6lKiMGj7aCBeLPw4TmwJ//hOAPnyECBKd2bOwcY9XXCBy5sJ4M8SShHxHGN7qR
jBeoREY1L095JOT410hxKu4nt8BtFNsMPFlonc6AxE3UNPJ0fyHhvf+j0GRrWE1r
wXtZ4ApN91KjRtmWSBHGTRz2hBBl9YZrPs8vLYJDsSuca7salz2OkcAFZwhYL/vk
hyfKiy7pp5oZE/nFfXZA
=905N
-END PGP SIGNATURE End Message ---

Bug#735893: marked as done (Sourceless file)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 13:20:20 +
with message-id 
and subject line Bug#735237: fixed in python-weberror 0.10.3+dfsg-1
has caused the Debian Bug report #735237,
regarding Sourceless file
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.)


-- 
735237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-weberror
Version:0.10.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org

I could not find the source of:
python-weberror 0.10.3-1 (source)

weberror/eval-media/jquery-1.2.1.min.js
  weberror/eval-media/jquery-1.2.3.pack.js
 

Bastien
--- End Message ---
--- Begin Message ---
Source: python-weberror
Source-Version: 0.10.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
python-weberror, 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 735...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated python-weberror 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Oct 2014 14:33:11 +0200
Source: python-weberror
Binary: python-weberror
Architecture: source all
Version: 0.10.3+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Shadura 
Description:
 python-weberror - Python web error handling and exception catching module
Closes: 735237
Changes:
 python-weberror (0.10.3+dfsg-1) unstable; urgency=low
 .
   [ Jakub Wilk ]
   * Use canonical URIs for Vcs-* fields.
 .
   [ Jackson Doak ]
   * Bump debhelper version to 9
   * debian/rules: Use dh
 .
   [ Federico Ceratto ]
   * Add patch to remove embedded minified JS (Closes: #735237)
   * Bump Standards-Version to 3.9.5 (no changes needed)
   * Add Pybuild dependencies
   * Install evaldemo.py example
 .
   [ Andrew Shadura ]
   * Repack the tarball to remove jQuery object files.
Checksums-Sha1:
 45d67c43927740ffe60967d72820bb01f168333a 2306 python-weberror_0.10.3+dfsg-1.dsc
 bb8a1f0ea507181c814ce619e9778117c24b2fa9 50680 
python-weberror_0.10.3+dfsg.orig.tar.gz
 efbf3170eb465cac4976713afdcd200ce900daf8 3780 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 48a9a228a928be9fa501b3db130b201aaec4558d 45098 
python-weberror_0.10.3+dfsg-1_all.deb
Checksums-Sha256:
 6de098534812a2a91c40ea00cc5bd7e5f2536f5c8102099dfc8b6478ecd93a33 2306 
python-weberror_0.10.3+dfsg-1.dsc
 c23cf11f412744272516929c04aee076a125eefd1fa03967ee8f02c60b88dc74 50680 
python-weberror_0.10.3+dfsg.orig.tar.gz
 ee73f1816f028d942215e68548dcdefb462d71b46929428b61aa2d047405f2f4 3780 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 862a3065bb70e313cbf0e352939cdff50708121f5bf586e8c04e87813e71fc00 45098 
python-weberror_0.10.3+dfsg-1_all.deb
Files:
 ec2409944612626dee329a93df0e082a 2306 python optional 
python-weberror_0.10.3+dfsg-1.dsc
 722eadecc892e2bcfe73a0dfe392108c 50680 python optional 
python-weberror_0.10.3+dfsg.orig.tar.gz
 89fb2711c5ac2ad3c395c7b60243caf1 3780 python optional 
python-weberror_0.10.3+dfsg-1.debian.tar.xz
 73cb09e2a700278ed6f6f3085dc57c1c 45098 python optional 
python-weberror_0.10.3+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJUNTJZAAoJEG6k0jEaLSaNJIQQALYWE4uvbixPBEdZd6frJOTz
4llXgQ4PUScvTpc3k3L93Is613fvSIOupmXbwMb01QrKURftWt+l3Qc8o+gaYE4Q
Ej+ZJBvNm2TmozLDZSAkidxke4oEbEN6Zv1HT7kWTHsdMDuuPCPbcSspTUjh3eyl
CB+SgRx9yocQXpZMXXdlQapdnK59wbucv8LNBM1VH1UltHN6EUUkmymGzl8xSQxN
9P4E4mpKsYViICazsLfT0Uwn7vGSmXzzQVsVbaE/at2+HeieIMyfgMZu3gCFiPUi
8I/cD4wHe3vKLT9GpEKllCbBuNX4EX6ZJMhPvIoNRTMeZE47fy4Q0PQltvkg9w7z
eAlsBeM1m4ipVL9BGj4k6I31x2qF9jvFpXoLnhHMPg5FCY2DNyD0JJDht3FiKpuj
dr7ob2+kTSH+1ldI+yUQHVynsYxv08NPfHkjoHwqS4OiSiOANJO+QMprLreZ7Mvm
tJ6lKiMGj7aCBeLPw4TmwJ//hOAPnyECBKd2bOwcY9XXCBy5sJ4M8SShHxHGN7qR
jBeoREY1L095JOT410hxKu4nt8BtFNsMPFlonc6AxE3UNPJ0fyHhvf+j0GRrWE1r
wXtZ4ApN91KjRtmWSBHGTRz2hBBl9YZrPs8vLYJDsSuca7salz2OkcAFZwhYL/vk
hyfKiy7pp5oZE/nFfXZA
=905N
-END PGP SIGNATURE End Message ---

Bug#764440: marked as done (ruby-protected-attributes and ruby-activemodel-3.2: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 13:33:49 +
with message-id 
and subject line Bug#764440: fixed in ruby-protected-attributes 1.0.8-2
has caused the Debian Bug report #764440,
regarding ruby-protected-attributes and ruby-activemodel-3.2: error when trying 
to install together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
764440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-activemodel-3.2,ruby-protected-attributes
Version: ruby-activemodel-3.2/3.2.19-1
Version: ruby-protected-attributes/1.0.8-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2014-10-08
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package libffi6:amd64.
(Reading database ... 10872 files and directories currently installed.)
Preparing to unpack .../libffi6_3.1-2_amd64.deb ...
Unpacking libffi6:amd64 (3.1-2) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ...
Selecting previously unselected package libyaml-0-2:amd64.
Preparing to unpack .../libyaml-0-2_0.1.6-2_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-2) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.1i-2_amd64.deb ...
Unpacking openssl (1.0.1i-2) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20140927_all.deb ...
Unpacking ca-certificates (20140927) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.8_all.deb ...
Unpacking rubygems-integration (1.8) ...
Selecting previously unselected package libruby2.1:amd64.
Preparing to unpack .../libruby2.1_2.1.3-1_amd64.deb ...
Unpacking libruby2.1:amd64 (2.1.3-1) ...
Selecting previously unselected package ruby2.1.
Preparing to unpack .../ruby2.1_2.1.3-1_amd64.deb ...
Unpacking ruby2.1 (2.1.3-1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.1.0.4_all.deb ...
Unpacking ruby (1:2.1.0.4) ...
Selecting previously unselected package ruby-i18n.
Preparing to unpack .../ruby-i18n_0.6.9-2_all.deb ...
Unpacking ruby-i18n (0.6.9-2) ...
Selecting previously unselected package ruby-json.
Preparing to unpack .../ruby-json_1.8.1-1+b2_amd64.deb ...
Unpacking ruby-json (1.8.1-1+b2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.4.2-1_all.deb ...
Unpacking ruby-minitest (5.4.2-1) ...
Selecting previously unselected package ruby-atomic.
Preparing to unpack .../ruby-atomic_1.1.16-2+b2_amd64.deb ...
Unpacking ruby-atomic (1.1.16-2+b2) ...
Selecting previously unselected package ruby-thread-safe.
Preparing to unpack .../ruby-thread-safe_0.3.3-1_all.deb ...
Unpacking ruby-thread-safe (0.3.3-1) ...
Selecting previously unselected package ruby-tzinfo.
Preparing to unpack .../ruby-tzinfo_1.1.0-2_all.deb ...
Unpacking ruby-tzinfo (1.1.0-2) ...
Selecting previously unselected package ruby-activesupport.
Preparing to unpack .../ruby-activesupport_2%3a4.1.6-2_all.deb ...
Unpacking ruby-activesupport (2:4.1.6-2) ...
Selecting previously unselected package ruby-blankslate.
Preparing to unpack .../ruby-blankslate_2.1.2.4-4_all.deb ...
Unpacking ruby-blankslate (2.1.2.4-4) ...
Selecting previously unselected package ruby-builder.
Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ...
Unpacking ruby-builder (3.2.2-4) ...
Selecting previously unselected package ruby-activemodel.
Preparing to unpack .../ruby-activemodel_2%3a4.1.6-2_all.deb ...
Unpacking ruby-activemodel (2:4.1.6-2) ...
Selecting previously unselected package ruby-bcrypt.
Preparing to unpack .../ruby-bcrypt_3.1.7-2+b3_amd64.deb ...
Unpacking ruby-bcrypt (3.1.7-2+b3) ...
Selecting previously unselected package ruby-multi-json.
Preparing to unpack .../ruby-multi-json_1.10.0-1_all.deb ...
Unpacking ruby-multi-json (1.10.0-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.0.1-1_all.deb ...
Unpacking ruby-test-unit (3.0.1-1) ...
Selecting previously unselected package ruby-activesupport-3.2.
Preparing to unpack .../ruby-activesupport-3.2_3.2.19-1_all.deb ...
Unpacking ruby-activesupport-3.2 (3.2.19-1) ...
Replaced by files in installed package 

Bug#761040: [libqtwebkit4] Browsers based on Webkit crash on loading pages

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 08 October 2014 12:16:52 Michel Dänzer wrote:
> On 07.10.2014 21:44, Lisandro =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?=
> 
> Meyer wrote:
> > In powerpc: do you get a SIGBUS or SIGSERV for unaligned access?
> 
> No, neither.
> 
> > Can anyone check is arora suffers from the same bug on ppc?
> 
> arora crashes in libQt5WebKit.so.5 for me on startup, not sure it's the
> same bug though.

Can you get a backtrace of that? Better after installing libqt5webkit5-dbg 
(which might be big). If this happens to be the same bug it will make things 
easier.

Porters: is there any ppc virtual machine I can link upstream too?

Once again, thanks a lot!

-- 
You know it's love when you memorize her IP number to skip DNS overhead.
  Anonymous

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#750857: NMU debdiff for mod-gnutls_0.6-1.1

[Daniel Kahn Gillmor]

On 10/08/2014 03:54 AM, Aníbal Monsalve Salazar wrote:
> Control: tags -1 + patch + pending
> 
> Hello Daniel,
> 
> At Imagination Technologies (http://imgtec.com/) Jurica Stanojkovic has
> found a solution to Debian bug #750857.
> 
> https://bugs.debian.org/750857
> 
> My NMU debdiff for mod-gnutls_0.6-1.1 is below, at the end of this
> message.
> 
> With the changes in the NMU debdiff, mod-gnutls builds successfully on
> mips, mipsel and amd64.

This suggests that those buildd's do not have a reasonable ipv6 loopback
configuration.

Wouldn't it be better to update the buildd to have such a thing?

Alternately, we could adjust the test suite to scan for available IP
addresses, but it sounds like it's starting to get rather complex.

--dkg



signature.asc
Description: OpenPGP digital signature

Bug#764480: cdbs: fails to build from source

[Holger Levsen]

package: cdbs
version: 0.4.126
severity: serious

Hi,

cdbs fails to build from source in an up2date sid today. Full log attached 
too.

make[5]: Leaving directory '/tmp/buildd/cdbs-0.4.126/test/cdbs.build'
mv cdbs.build/autotools-test-0.1.tar.gz tarballs
rm -rf cdbs.build
mkdir tarballs
mkdir: cannot create directory 'tarballs': File exists
Makefile:929: recipe for target 'tarballs/distutils-test-0.1.tar.gz' failed
make[4]: [tarballs/distutils-test-0.1.tar.gz] Error 1 (ignored)
cd distutils && ./setup.py sdist
running sdist
running check
reading manifest file 'MANIFEST'
creating distutils-test-0.1
creating distutils-test-0.1/src
making hard links in distutils-test-0.1...
hard linking ./setup.py -> distutils-test-0.1/.
hard linking src/__init__.py -> distutils-test-0.1/src
hard linking src/foo.py -> distutils-test-0.1/src
creating dist
Creating tar archive
removing 'distutils-test-0.1' (and everything under it)
mv distutils/dist/distutils-test-0.1.tar.gz tarballs
rm -rf distutils/dist
FAIL: autotools-1.sh
FAIL: autotools-2.sh
FAIL: autotools-3.sh
FAIL: autotools-4.sh
FAIL: autotools-5.sh
FAIL: autotools-lzma.sh
FAIL: recursive.sh
FAIL: udeb-1.sh
FAIL: hdparm.sh
FAIL: debhelper-1.sh
FAIL: debhelper-2.sh
FAIL: debhelper-3.sh
FAIL: debhelper-4.sh
FAIL: debhelper-5.sh
FAIL: debhelper-6.sh
FAIL: debhelper-7.sh
FAIL: patchsys-1.sh
FAIL: list-missing-1.sh
FAIL: distutils-9.sh
FAIL: distutils-10.sh
FAIL: distutils-11.sh
PASS: ant-1.sh
make[6]: Entering directory '/tmp/buildd/cdbs-0.4.126/test'
make[6]: Nothing to be done for 'all'.
make[6]: Leaving directory '/tmp/buildd/cdbs-0.4.126/test'

Testsuite summary for cdbs something

# TOTAL: 22
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  21
# XPASS: 0
# ERROR: 0

See test/test-suite.log

Makefile:472: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/tmp/buildd/cdbs-0.4.126/test'
Makefile:578: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/tmp/buildd/cdbs-0.4.126/test'
Makefile:791: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/tmp/buildd/cdbs-0.4.126/test'
Makefile:526: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/tmp/buildd/cdbs-0.4.126'
Makefile:626: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/tmp/buildd/cdbs-0.4.126'
1/class/makefile.mk.in:65: recipe for target 'debian/stamp-makefile-check' 
failed
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


cheers,
Holger
DIST=unstable
ARCH=amd64

W: /root/.pbuilderrc does not exist
I: using fakeroot in build.
I: Current time: Wed Oct  8 15:55:02 CEST 2014
I: pbuilder-time-stamp: 1412776502
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-amd64-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: devscripts (>= 2.10.7), debhelper, dh-buildinfo, realpath, fakeroot, python-dev, python-all-dev, python3-all-dev, ant, default-jdk, sharutils, lzma
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11926 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested:
 pbuilder-satisfydepends-dummy depends on devscripts (>= 2.10.7); however:
  Package devscripts is not installed.
 pbuilder-satisfydepends-dummy depends on debhelper; however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on dh-buildinfo; however:
  Package dh-buildinfo is not installed.
 pbuilder-satisfydepends-dummy depends on realpath; however:
  Package realpath is not installed.
 

Bug#755575: anjuta-extras: uninstallable with anjuta 3.14

[Christoph Anton Mitterer]

reopen 755575
retitle 755575 anjuta-extras: uninstallable with anjuta 3.14
stop


Same issue, now with 3.14

Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Processed: Re: anjuta-extras: uninstallable with anjuta 3.14

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 755575
Bug #755575 {Done: Laurent Bigonville } [anjuta-extras] 
anjuta-extras: uninstallable with anjuta 3.12
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions anjuta-extras/3.10.0-2.
> retitle 755575 anjuta-extras: uninstallable with anjuta 3.14
Bug #755575 [anjuta-extras] anjuta-extras: uninstallable with anjuta 3.12
Changed Bug title to 'anjuta-extras: uninstallable with anjuta 3.14' from 
'anjuta-extras: uninstallable with anjuta 3.12'
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
755575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755575
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: josm-plugins: not installable in sid

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 764176 grave
Bug #764176 [josm-plugins] josm-plugins: not installable in sid
Severity set to 'grave' from 'normal'
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
764176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764176
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#760038: minor problem subsists

[Curtis Dean Smith]

Well, I've given up on e17 for the short term, although I went from stable
to testing specifically for e17.  I try once a week to see if something
changed, but no luck.  I certainly hope it is fixed and not dropped,
though!  My vote is to keep e17 in Jessie!

On Wed, Oct 8, 2014 at 5:04 AM, Sébastien NOBILI 
wrote:

> Hi,
>
> I just ran how-can-i-help and noticed e17 is planned to be dropped from
> Jessie
> because of this bug.
>
> I'm working everyday with Jessie version of e17 and never noticed any
> black-screen problem.
>
> Crashes happen from time to time, but are really occasional and always
> followed
> by an automatic restart. This point is just a matter of clicking a button
> to
> restart the environment.
>
> These two issues don't seem grave enough to legitimate e17 being dropped.
>
> Is there anything I've missed in this decision ?
>
> Sébastien
>
> --
> To unsubscribe, send mail to 760038-unsubscr...@bugs.debian.org.
>



--

Processed: fixed 759241 in 0.8-3.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 759241 0.8-3.1
Bug #759241 [wmauda] wmauda: FTBFS - audacious/dbus.h: No such file or directory
Marked as fixed in versions wmauda/0.8-3.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759241
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#758121: bibletime: Bibletime is unusable in testing and unstable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 758121 bibletime: New upstream release fixes display problem in jessie
Bug #758121 [bibletime] bibletime: Texts doesn't display properly
Changed Bug title to 'bibletime: New upstream release fixes display problem in 
jessie' from 'bibletime: Texts doesn't display properly'
> severity 758121 grave
Bug #758121 [bibletime] bibletime: New upstream release fixes display problem 
in jessie
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
758121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758121
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#759241: marked as done (wmauda: FTBFS - audacious/dbus.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 8 Oct 2014 16:55:06 +0200
with message-id 

and subject line Fixed in 0.8-3.1
has caused the Debian Bug report #759241,
regarding wmauda: FTBFS - audacious/dbus.h: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
759241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wmauda
Version: 0.8-3
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
Package audclient was not found in the pkg-config search path.
Perhaps you should add the directory containing `audclient.pc'
to the PKG_CONFIG_PATH environment variable
No package 'audclient' found
rm -f *.o wmauda
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-wmauda/wmauda-0.8'
   dh_clean
 dpkg-source --auto-commit -b wmauda-0.8
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building wmauda using existing ./wmauda_0.8.orig.tar.gz
dpkg-source: info: building wmauda in wmauda_0.8-3.debian.tar.xz
dpkg-source: info: building wmauda in wmauda_0.8-3.dsc
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-wmauda/wmauda-0.8'
CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-z,relro -Wl,--as-needed" /usr/bin/make
make[2]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-wmauda/wmauda-0.8'
Package audclient was not found in the pkg-config search path.
Perhaps you should add the directory containing `audclient.pc'
to the PKG_CONFIG_PATH environment variable
No package 'audclient' found
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-z,relro -Wl,--as-needed  -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm 
-I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/freetype2  -D_FORTIFY_SOURCE=2  -c -o wmauda.o wmauda.c
wmauda.c:29:28: fatal error: audacious/dbus.h: No such file or directory
 #include 
^
compilation terminated.
: recipe for target 'wmauda.o' failed
make[2]: *** [wmauda.o] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


wmauda-build-log.txt.gz
Description: application/gunzip


pgps6zrKoOmcu.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
wmauda (0.8-3.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Change the build-dependency to libaudclient, as it's been moved
to a separate package.
  * Update the Makefile to not link against audacious.

 -- Andrew Shadura   Sun, 07 Sep 2014 23:47:58 +0200



-- 
Cheers,
  Andrew--- End Message ---

Bug#764493: python-eventlet tests failures

[Matthias Klose]

Package: src:python-eventlet
Version: 0.13.0
Severity: serious
Tags: sid jessie patch

Two python-eventlet tests fail with the recent python2.7. Proposed patch at
http://launchpadlibrarian.net/186832595/python-eventlet_0.13.0-1ubuntu2_0.13.0-1ubuntu3.diff.gz

I didn't check with 0.15. Is this version stable enough for unstable?


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764499: Fix build failure with python2.7 and PEP 466

[Matthias Klose]

Package: src:python-gevent
Version: 1.0-2
Severity: serious
Tags: sid jessie patch

Fix build failure with python2.7 and PEP 466
patch at
http://launchpadlibrarian.net/186834363/python-gevent_1.0-2_1.0-2ubuntu1.diff.gz


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764499: Acknowledgement (Fix build failure with python2.7 and PEP 466)

[Matthias Klose]

there's also a new upstream version 1.0.1


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: python-pygraphviz: avoid deprecated build target python-build-stamp-%

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 759709
Bug #759709 {Done: Jonas Smedegaard } [python-pygraphviz] 
python-pygraphviz: avoid deprecated build target python-build-stamp-%
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.8.2-5.
> notfixed 759709 1.8.2-5
Bug #759709 [python-pygraphviz] python-pygraphviz: avoid deprecated build 
target python-build-stamp-%
There is no source info for the package 'python-pygraphviz' at version 
'1.8.2-5' with architecture ''
Unable to make a source version for version '1.8.2-5'
Ignoring request to alter fixed versions of bug #759709 to the same values 
previously set
> tags 759709 pending
Bug #759709 [python-pygraphviz] python-pygraphviz: avoid deprecated build 
target python-build-stamp-%
Added tag(s) pending.
> severity 759709 serious
Bug #759709 [python-pygraphviz] python-pygraphviz: avoid deprecated build 
target python-build-stamp-%
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
759709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759709
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#754686: marked as done (concordance: FTBFS on kfreebsd-*: configure: error: lib is missing!)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 16:19:13 +
with message-id 
and subject line Bug#754686: fixed in concordance 1.1-2
has caused the Debian Bug report #754686,
regarding concordance: FTBFS on kfreebsd-*: configure: error: lib is missing!
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.)


-- 
754686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: concordance
Version: 1.1-1
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on kfreebsd-*:
| checking dynamic linker characteristics... (cached) GNU/Linux ld.so
| checking how to hardcode library paths into programs... immediate
| checking for update-mime-database... no
| checking hidapi/hidapi.h usability... no
| checking hidapi/hidapi.h presence... no
| checking for hidapi/hidapi.h... no
| checking for hid_init in -l... no
| configure: error: lib is missing!
|   Note that while we are deprecating the use of libusb on Linux in favor
|   of libhidapi, this release still supports it via
|   --enable-force-libusb-on-linux
| make[1]: *** [override_dh_auto_configure] Error 1
| make[1]: Leaving directory `/«PKGBUILDDIR»'
| make: *** [build-arch] Error 2

Full build logs:
  
https://buildd.debian.org/status/fetch.php?pkg=concordance&arch=kfreebsd-amd64&ver=1.1-1&stamp=1399055931
  
https://buildd.debian.org/status/fetch.php?pkg=concordance&arch=kfreebsd-i386&ver=1.1-1&stamp=1399055594

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: concordance
Source-Version: 1.1-2

We believe that the bug you reported is fixed in the latest version of
concordance, 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.
Mathieu Trudel-Lapierre  (supplier of updated concordance 
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: Tue, 07 Oct 2014 22:56:47 -0400
Source: concordance
Binary: concordance libconcord3 libconcord-dev python-libconcord 
concordance-common
Architecture: all amd64 i386 source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Mathieu Trudel-Lapierre 
Closes: 754686
Description: 
 concordance-common - Harmony remote configuration tool - common files
 concordance - configuration tool for Harmony remotes
 libconcord3 - configuration tool for Harmony remotes - runtime libraries
 libconcord-dev - configuration tool for Harmony remotes - development files
 python-libconcord - Harmony remote configuration tool - Python bindings
Changes:
 concordance (1.1-2) unstable; urgency=medium
 .
   [ Scott Talbert ]
   * Fix kFreeBSD build - use hidapi which is now available (Closes: #754686)
Checksums-Sha1: 
 a0ac13106c36c1d943b3dc56fa92ddeef16b6d24 1481 concordance_1.1-2.dsc
 b96e5b5f69ff29bcc2837378b4d4f605e1320f2a 6676 concordance_1.1-2.debian.tar.xz
 513c32fcffb84deab2b294f3769e16d726c5dea9 23172 concordance_1.1-2_amd64.deb
 0b4b0d0cc57bd1683f864470f1c15a1a68d714ba 56120 libconcord3_1.1-2_amd64.deb
 49757b63e256d8d95211d102207c46b53dbc5be3 15100 libconcord-dev_1.1-2_amd64.deb
 fbf9edcae53258630d6ef146e165c3e9e4ea8ddf 14866 python-libconcord_1.1-2_all.deb
 61778a777abf94b0e885982746c2d42b7001e3f5 11264 concordance-common_1.1-2_all.deb
 2556ea2d9f5933c5095f64ef63521f7c3ed6bf7c 22892 concordance_1.1-2_i386.deb
 197471855a33927d024a132d471899942ce2f348 57676 libconcord3_1.1-2_i386.deb
 d3a3f2be63899da239a6ccbb78f0137c232b2f4a 15094 libconcord-dev_1.1-2_i386.deb
Checksums-Sha256: 
 2ba1f697731804ac83354b74cd9347fcfba405080b9cfae990392d9aedb21790 1481 
concordance_1.1-2.dsc
 7636afea93dde59cbd3bd2d0f91e8f2013e9e929a5dfbd496b5687b168cda862 6676 
concordance_1.1-2.debian.tar.xz
 8227dc01a54622282c649980fdc166a3d0852978bb9d36018f9bd548fd830bf0 23172 
concordance_1.1-2_amd64.deb
 9701faac07c58e776aef1cd63393864dda9560a24fbe31a26ddb146c16dee6e8 56120 
libconcord3_1.1-2_amd64.deb
 107669cc9d18ecc0fb376b70b8b9a2fe173c3f29d0107e9f87e67641180c4e37 15100 
libconcord-dev_1.1-2_amd64.deb
 327bbf509fce7e5447a5480e7fc776309bd2899e75be144cd74a1ec2eb639f9e 14866 
python-libconcor

Processed: fixed 763780 in 0.9.7.9+deb7u6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 763780 0.9.7.9+deb7u6
Bug #763780 {Done: Michael Vogt } [apt] apt-get: 
CVE-2014-7206: Insecure temporary changelog handling
There is no source info for the package 'apt' at version '0.9.7.9+deb7u6' with 
architecture ''
Unable to make a source version for version '0.9.7.9+deb7u6'
Marked as fixed in versions 0.9.7.9+deb7u6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763780
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#763470: marked as done (flightgear: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 17:18:44 +
with message-id 
and subject line Bug#763470: fixed in flightgear 3.0.0-3
has caused the Debian Bug report #763470,
regarding flightgear: Please change build dependency to libjpeg-dev 
(libjpeg-turbo 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.)


-- 
763470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flightgear
Version: 3.0.0-2
Severity: important
Tags: patch
User: ond...@debian.org
Usertags: libjpeg-turbo-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

Debian is transitioning from IJG JPEG library (src:libjpeg8) to
libjpeg-turbo implementation (src:libjpeg-turbo)[1] of libjpeg62 API
with "decode from memory buffer" interface (jpeg_mem_{src,dest}).

Your package cannot be transitioned automatically as it explicitly
build depends on specific API/ABI (libjpeg8-dev) and this build
dependency needs to be changed to libjpeg-dev.  In most if not all
cases this should be sufficient to build against libjpeg-turbo.

I am in process of testing each package in question to compile against
libjpeg-turbo and I will provide a suitable patch for each package
when I will succeed.

On the other hand please note that the winter^Wfreeze is coming and
if your package is not updated in due time it might be NMUed by the
release team (or by me with the full ack of release team).

That also means that if you are OK with NMU then please respond to
this bug report and I will prepare and upload the recompiled packages
for you.

Cheers,
Ondrej

1. The full Technical Committee decision can be found here:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076#235

- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJUKqrHXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHxv4P/3ydlTq8EF0gs75qJ/eG13pR
SK8Svi+ELwK4osvEmnYNoD8sw7aAKNSLk/YvSKtklRP6PfdvT/4/8LOHzPBkrDb2
SIqatn5+FUs6DoIFvgCrOtCsm+FEUupXu48LVKkQ7IZzjIpGbj21XK64NXwnOJl4
Me9k5D/8ZCcB5qmdcZEDOA0Zqf6ZqEhNHsBtDzbez5EB+QtLIa3XkxF1HbTdAAOj
Kb0dt/elWKhEJfk1pzRX09vIptQox0uj5IGMbonAa1jzi3OkebxvIIgB5dYZFcLc
A+hNuL0luVyPp4X2bL+ILb7O3L8qigamMIIPLoybtMk5Bjfchtrc1H8JBGdHm6ix
8b++3k7RLR2O1yDQk7AF4gq/l7LMzsWAfeDZY3VJDCbbAEW1MwNj3PI4itFJa/X1
NLzATsLHzVjuDWsHidqmy/LFTEfnE04d3gdyqb9qc7hk0+xWk02j1n85050EpCMT
CQOlSIUyes4kf/eBEJWvT+NeA8g0z/ROqy8F5sDSdoun1jG6SR12iD+cPIuarKCx
Sp0k+EmjekHcGZhs/pFMkzPGO4bKPR3RMDsgWFFDDdox88NP2Y7oAD2tLIPkt+Su
HieEUI/5b9McstUgqNMJdu3BYmOIXELCcUQVg2DwSjYiAiURsNqrTiqsQPqi9SUP
qSUIDXMecdu/geShLRkP
=zcgj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: flightgear
Source-Version: 3.0.0-3

We believe that the bug you reported is fixed in the latest version of
flightgear, 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 763...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Wanner  (supplier of updated flightgear package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Oct 2014 08:26:10 +0200
Source: flightgear
Binary: flightgear
Architecture: source
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew 
Changed-By: Markus Wanner 
Description:
 flightgear - Flight Gear Flight Simulator
Closes: 763470
Changes:
 flightgear (3.0.0-3) unstable; urgency=medium
 .
   * Change B-D to libjpeg-dev to finish the transition to
 libjpeg-turbo. Closes: #763470.
   * Increment simgear dependency due to incompatible patch.
   * Correct, update and simplify copyright file.
   * Bump S-V: no changes required.
Checksums-Sha1:
 f6e0f40af8fc4a3994842ff52cc92679bdc0a419 3212 flightgear_3.0.0-3.dsc
 a803ca84028594330768707f7fec045fd82977bd 25504 fligh

Bug#764509: libaio ftbfs at least on i386 and powerpc

[Matthias Klose]

Package: src:libaio
Version: 0.3.109-4
Severity: serious
Tags: sid jessie

reproduced on i386 with today's sid:

cc -shared -nostdlib -nostartfiles -fomit-frame-pointer -fPIC -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wl,--version-script=libaio.map -Wl,-soname=libaio.so.1 -o libaio.so.1.0.1
io_queue_init.os io_queue_release.os io_queue_wait.os io_queue_run.os
io_getevents.os io_submit.os io_cancel.os io_setup.os io_destroy.os
raw_syscall.os compat-0_1.os -lgcc -Wl,-z,relro
io_queue_run.os: In function `io_queue_run':
/scratch/packages/tmp/libaio-0.3.109/src/io_queue_run.c:39: undefined reference
to `__stack_chk_fail_local'
io_getevents.os: In function `__io_getevents_0_4':
/scratch/packages/tmp/libaio-0.3.109/src/io_getevents.c:25: undefined reference
to `__stack_chk_fail_local'
compat-0_1.os: In function `compat0_1_io_cancel':
/scratch/packages/tmp/libaio-0.3.109/src/compat-0_1.c:38: undefined reference to
`__stack_chk_fail_local'
compat-0_1.os: In function `compat0_1_io_queue_wait':
/scratch/packages/tmp/libaio-0.3.109/src/compat-0_1.c:47: undefined reference to
`__stack_chk_fail_local'
compat-0_1.os: In function `compat0_1_io_getevents':
/scratch/packages/tmp/libaio-0.3.109/src/compat-0_1.c:61: undefined reference to
`__stack_chk_fail_local'
collect2: error: ld returned 1 exit status
Makefile:55: recipe for target 'libaio.so.1.0.1' failed
make[2]: *** [libaio.so.1.0.1] Error 1
make[2]: Leaving directory '/scratch/packages/tmp/libaio-0.3.109/src'
Makefile:25: recipe for target 'all' failed
make[1]: *** [all] Error 2


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: python-greenlet: FTBFS on arm* due to test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + sid jessie
Bug #751498 [src:python-greenlet] python-greenlet: FTBFS on arm* due to test 
failures
Added tag(s) sid and jessie.

-- 
751498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751498
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#751498: python-greenlet: FTBFS on arm* due to test failures

[Matthias Klose]

Control: tags -1 + sid jessie

reproducible, no difference when building with -O0 or with gcc-4.8. The tests
succeed for python3.4.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#751498: python-greenlet: FTBFS on arm* due to test failures

[GCS]

On Wed, Oct 8, 2014 at 7:33 PM, Matthias Klose  wrote:
> reproducible, no difference when building with -O0 or with gcc-4.8. The tests
> succeed for python3.4.
 Do you mean that I should tighten the python3 build dependency to
3.4? May you give more pointers why the build fails with other python3
versions?

Thanks,
Laszlo/GCS


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#762417: [Pkg-libvirt-maintainers] Bug#762417: vinagre: cannot connect - libgrypt error?

[Guido Günther]

On Tue, Oct 07, 2014 at 12:16:51PM +0900, Norbert Preining wrote:
> Hi,
> 
> On Tue, 30 Sep 2014, Andreas Henriksson wrote:
> > > > and suggest you try to downgrade all binary packages built from gtk-vnc
> > > > you have installed on your system to 0.5.3-1 and see if this has any 
> > > > affect.
> > > 
> > > Yes, it has. Installing the packages you mentioned I can easily connect
> > > without any problem or crashes.
> > 
> > Ok, reassigning to the affected version of gtk-vnc then
> > 
> > Andreas Metzler, hopefully you can shine some light on what the difference
> > is for the new gnutls/gcrypt version?
> > 
> > A backtrace is available as an attachment in the bug report backlog, see:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=vinagre.gdb.log;att=1;bug=762417
> 
> Is there any progress with respect to this introduced bug?
> Especially introducing such a grave bug in an NMU was a bit
> a surprise for me.

I did see this but didn't have time to look into it yet but maybe
Andreas can shed some light on this?
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#762860: [dfc] strace information

[Thomas Kreft]

Hi Matteo,

I did:

$ mkdir /run/user/1000/gvfs

After which dfc seems to work again, but prints this warning ahead:

$ strace -o ~/20141008_bug#762860_as_user dfc
WARNING: /run/user/1001/gvfs was skipped because it cannot be stated : 
Permission denied
(...expected output of dfc skipped...)

See strace report attached. I've also attached the output of

$ sudo strace -o ~/20141008_bug#762860_per_sudo dfc

which only gives the following error:

Error while stating /run/user/1001/gvfs : No such file or directory

Hope that helps. 
(Probably unrelated hint: I have systemd installed.)

Cheers,
Thomasexecve("/usr/bin/dfc", ["dfc"], [/* 47 vars */]) = 0
brk(0)  = 0x218f000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1a00dfe000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=141536, ...}) = 0
mmap(NULL, 141536, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f1a00ddb000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1725888, ...}) = 0
mmap(NULL, 3832352, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f1a00838000
mprotect(0x7f1a009d7000, 2093056, PROT_NONE) = 0
mmap(0x7f1a00bd6000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19e000) = 0x7f1a00bd6000
mmap(0x7f1a00bdc000, 14880, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f1a00bdc000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1a00dda000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1a00dd9000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1a00dd8000
arch_prctl(ARCH_SET_FS, 0x7f1a00dd9700) = 0
mprotect(0x7f1a00bd6000, 16384, PROT_READ) = 0
mprotect(0x603000, 4096, PROT_READ) = 0
mprotect(0x7f1a00e0, 4096, PROT_READ) = 0
munmap(0x7f1a00ddb000, 141536)  = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, 
{B38400 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=42, ws_col=152, ws_xpixel=0, ws_ypixel=0}) = 0
brk(0)  = 0x218f000
brk(0x21b)  = 0x21b
open("/etc/mtab", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1a00dfd000
read(3, "rootfs / rootfs rw 0 0\nsysfs /sy"..., 1024) = 1024
statfs("/", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=2370105, 
f_bfree=507082, f_bavail=385022, f_files=610800, f_ffree=392389, 
f_fsid={973349808, 2075321154}, f_namelen=255, f_frsize=4096}) = 0
stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
statfs("/sys", {f_type="SYSFS_MAGIC", f_bsize=4096, f_blocks=0, f_bfree=0, 
f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, f_frsize=4096}) 
= 0
stat("/sys", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
statfs("/proc", {f_type="PROC_SUPER_MAGIC", f_bsize=4096, f_blocks=0, 
f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, 
f_frsize=4096}) = 0
stat("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
statfs("/dev", {f_type=0x1021994, f_bsize=4096, f_blocks=2560, f_bfree=2560, 
f_bavail=2560, f_files=981478, f_ffree=980908, f_fsid={0, 0}, f_namelen=255, 
f_frsize=4096}) = 0
stat("/dev", {st_mode=S_IFDIR|0755, st_size=4020, ...}) = 0
statfs("/dev/pts", {f_type="DEVPTS_SUPER_MAGIC", f_bsize=4096, f_blocks=0, 
f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, 
f_frsize=4096}) = 0
stat("/dev/pts", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
statfs("/run", {f_type=0x1021994, f_bsize=4096, f_blocks=396835, 
f_bfree=390423, f_bavail=390423, f_files=992086, f_ffree=991155, f_fsid={0, 0}, 
f_namelen=255, f_frsize=4096}) = 0
stat("/run", {st_mode=S_IFDIR|0755, st_size=1220, ...}) = 0
statfs("/", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=2370105, 
f_bfree=507082, f_bavail=385022, f_files=610800, f_ffree=392389, 
f_fsid={973349808, 2075321154}, f_namelen=255, f_frsize=4096}) = 0
stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
statfs("/sys/kernel/security", {f_type=0x73636673, f_bsize=4096, f_blocks=0, 
f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, 
f_frsize=4096}) = 0
stat("/sys/kernel/security", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
statfs("/dev/shm", {f_type=0x1021994, f_bsize=4096, f_blocks=992086, 
f_bfree=992086, f_bavail=992086, f_files=992086, f_ffree=992085, f_fsid={0, 0

Bug#751498: python-greenlet: FTBFS on arm* due to test failures

[Matthias Klose]

Am 08.10.2014 um 19:39 schrieb László Böszörményi (GCS):
> On Wed, Oct 8, 2014 at 7:33 PM, Matthias Klose  wrote:
>> reproducible, no difference when building with -O0 or with gcc-4.8. The tests
>> succeed for python3.4.
>  Do you mean that I should tighten the python3 build dependency to
> 3.4? May you give more pointers why the build fails with other python3
> versions?

no, it fails with 2.7.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#763855: xchat: FTBFS on linux-any

[Sebastian Schmidt]

Hi,

On Wed, Oct 08, 2014 at 12:22:11PM +0200, Svante Signell wrote:
> The attached patch configure.in.patch
> solves the build problem, at least for linux, kfreebsd and hurd.
> Attached is a patch for debian/rules too. autoconf works (with
> warnings), putting dh_autoreconf there (or running autoreconf manually)
> does not work. Some work is needed to make autoreconf working if needed.

I can confirm Svante's patch is working; as far as I can tell from
http://sourceforge.net/p/xchat/svn/189/ this doesn't seem relevant on
GNU/*. The attached patch incorporates Svante's into quilt and calls
autoconf from debian/rules.

HTH,
  Sebastian
diff -urN xchat-2.8.8.old/debian/control xchat-2.8.8/debian/control
--- xchat-2.8.8.old/debian/control	2014-10-08 20:22:21.609183656 +0200
+++ xchat-2.8.8/debian/control	2014-10-08 20:35:45.460998064 +0200
@@ -4,7 +4,7 @@
 Maintainer: Davide Puricelli (evo) 
 Uploaders: Bart Martens 
 Standards-Version: 3.8.4.0
-Build-Depends: debhelper (>= 5), bison, libssl-dev, libglib2.0-dev, libgtk2.0-dev (>= 2.0.6), libperl-dev, gettext (>= 0.10.37), libtool, zlib1g-dev, perl (>= 5.8), python-dev, tcl-dev, autotools-dev, libdbus-glib-1-dev, libgtkspell-dev, gconf2, dpkg-dev (>= 1.13.19), libsexy-dev, chrpath, imagemagick
+Build-Depends: debhelper (>= 5), bison, libssl-dev, libglib2.0-dev, libgtk2.0-dev (>= 2.0.6), libperl-dev, gettext (>= 0.10.37), libtool, zlib1g-dev, perl (>= 5.8), python-dev, tcl-dev, autotools-dev, libdbus-glib-1-dev, libgtkspell-dev, gconf2, dpkg-dev (>= 1.13.19), libsexy-dev, chrpath, imagemagick, autoconf
 Homepage: http://www.xchat.org/
 
 Package: xchat
diff -urN xchat-2.8.8.old/debian/patches/67_configure_with_gmodule.patch xchat-2.8.8/debian/patches/67_configure_with_gmodule.patch
--- xchat-2.8.8.old/debian/patches/67_configure_with_gmodule.patch	1970-01-01 01:00:00.0 +0100
+++ xchat-2.8.8/debian/patches/67_configure_with_gmodule.patch	2014-10-08 20:28:02.961012570 +0200
@@ -0,0 +1,17 @@
+Description: Don't strip -lgmodule-2.0 from RDYNAMIC_LIBS
+Author: Svante Signell 
+Bug: 763855
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/configure.in
 b/configure.in
+@@ -445,8 +445,7 @@
+ 	if test "$have_dl" = yes; then
+ 		AC_DEFINE(USE_PLUGIN)
+ 		AC_PATH_PROG(pkgconfigpath, pkg-config)
+-		dnl we just need the -Wl,--export-dynamic, but not -lgmodule-2.0
+-		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs | $sedpath 's/ -lgmodule-2.0//'`"
++		RDYNAMIC_FLAGS="`$pkgconfigpath gmodule-2.0 --libs`"
+ 		LIBS="$LIBS $RDYNAMIC_FLAGS"
+ 		if test "$LD" = ""; then
+ 			VS="`ld --help | grep version-script 2> /dev/null`"
diff -urN xchat-2.8.8.old/debian/patches/series xchat-2.8.8/debian/patches/series
--- xchat-2.8.8.old/debian/patches/series	2014-10-08 20:22:21.609183656 +0200
+++ xchat-2.8.8/debian/patches/series	2014-10-08 20:23:17.914135890 +0200
@@ -24,3 +24,4 @@
 64_save_pevents.patch
 65_save_sound.patch
 66_load_libnotify4.patch
+67_configure_with_gmodule.patch
diff -urN xchat-2.8.8.old/debian/rules xchat-2.8.8/debian/rules
--- xchat-2.8.8.old/debian/rules	2014-10-08 20:22:21.609183656 +0200
+++ xchat-2.8.8/debian/rules	2014-10-08 20:30:42.249007574 +0200
@@ -12,8 +12,10 @@
 configure-stamp:
 	[ -f config.sub.d-r-orig ] || cp -p config.sub config.sub.d-r-orig
 	[ -f config.guess.d-r-orig ] || cp -p config.guess config.guess.d-r-orig
+	[ -f configure.d-r-orig ] || cp -p configure configure.d-r-orig
 	cp -f /usr/share/misc/config.sub .
 	cp -f /usr/share/misc/config.guess .
+	autoconf
 	[ -f xchat.xpm ] || convert -resize 32x32 xchat.png xchat.xpm
 	CFLAGS="$(CFLAGS)" ./configure --prefix=/usr --datadir=/usr/share --sysconfdir=/etc --enable-python --enable-ipv6  \
 	--disable-mmx --enable-openssl --enable-tcl=/usr/lib \
@@ -36,6 +38,7 @@
 	[ ! -f Makefile ] || $(MAKE) distclean
 	[ ! -f config.sub.d-r-orig ] || mv config.sub.d-r-orig config.sub
 	[ ! -f config.guess.d-r-orig ] || mv config.guess.d-r-orig config.guess
+	[ ! -f configure.d-r-orig ] || mv configure.d-r-orig configure
 	rm -f xchat.xpm
 	rm -f config.log
 	rm -f xchat xchat-gnome


signature.asc
Description: Digital signature

Bug#758165: gcc-4.9 devirtualisation bug affecting wxwidgets3.0 now fixed

[Niko Tyni]

On Tue, Oct 07, 2014 at 12:40:46PM +1300, Olly Betts wrote:
> On Mon, Sep 01, 2014 at 09:51:37PM -0300, Olly Betts wrote:
> > There's an issue with devirtualisation in GCC 4.9 which wx3 triggers,
> > which may be connected:
> > 
> > https://bugs.debian.org/752733
> 
> This was fixed in gcc-4.9 4.9.1-14, so it would be useful to check if
> libwx-perl and sage now work OK on armel and armhf, or if there's
> something else going on here.

I tried building libwx-perl on armel / abel.debian.org in a jessie chroot
(the build dependencies are uninstallable in sid right now), with gcc-4.9
4.9.1-16, and still got

t/01_load.t ... 1/6 Can't load 
'/home/ntyni/libwx-perl-0.9923/blib/arch/auto/Wx/PropertyGrid/PropertyGrid.so' 
for module Wx::PropertyGrid:  at 
/home/ntyni/libwx-perl-0.9923/blib/lib/Wx/Mini.pm line 74.

which looks like the problem is still present.

But we probably need the wxwidgets3.0 packages built with a fixed
gcc-4.9 first?  This was jessie's 3.0.1-3, and buildd logs say it was
built in August with 4.9.0-10.

I've filed #764525 to fix the uninstallability in sid and can re-test
when the binNMUs are built. The porter box setup doesn't really allow for
manually built binaries or mixing distributions AFAICS.
-- 
Niko Tyni   nt...@debian.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#720517: configuration files, ownership and dpkg-statoverride

[Paul Gevers]

On 08-10-14 13:58, Ian Jackson wrote:
> Paul Gevers writes ("Re: Bug#720517: configuration files, ownership and 
> dpkg-statoverride"):
>> On 07-10-14 15:40, Ian Jackson wrote:
>>> Also I don't see in your references an explanation from anyone as to
>>> why dbconfig-common does this.
>>
>> I you mean with "why": "why is it implemented this way" than that is
>> exactly the question that I am asking myself looking at the code, if you
>> mean "why does dbconfig-common change the ownership of cactis
>> configuration file" than the answer is that you can tell dbconfig-common
>> in your maintainer scripts what the (I expected initial) ownership
>> should be.
> 
> Why does dbconfig-common have this feature ?

Because some packages need the configuration file to be owned (or
grouped) by the user under which a package is running.

> Why does cactis use it ?

The cacti configuration file contains a password to the database, so it
must be readable by the httpd, but not readable by all other users of
the system. Therefore the ownership is root:www-data.

Paul




signature.asc
Description: OpenPGP digital signature

Processed: fixed 763849 in ruby-carrierwave/0.8.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 763849 ruby-carrierwave/0.8.0-2
Bug #763849 {Done: Ralf Treinen } 
[ruby-carrierwave] ruby-carrierwave: not installable in sid
Marked as fixed in versions ruby-carrierwave/0.8.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763849
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: notfound 763849 in ruby-carrierwave/0.8.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 763849 ruby-carrierwave/0.8.0-2
Bug #763849 {Done: Ralf Treinen } 
[ruby-carrierwave] ruby-carrierwave: not installable in sid
No longer marked as found in versions ruby-carrierwave/0.8.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763849
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#752514: marked as done (ruby-fftw3: FTBFS on armhf)

[Debian Bug Tracking System]

Your message dated Wed, 8 Oct 2014 23:06:50 +0200
with message-id <20141008210650.GA30572@spin>
and subject line builds now fine on armhf
has caused the Debian Bug report #752514,
regarding ruby-fftw3: FTBFS on armhf
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.)


-- 
752514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fftw3
Version: 0.4-6
Severity: serious

Your package failed to build on armhf:

/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:86:in `exit': no implicit 
conversion from nil to integer (TypeError)
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:86:in `run_ruby'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:130:in `run_tests'
from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:189:in `'
..ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 
1
make: *** [binary-arch] Error 1
debian/rules:4: recipe for target 'binary-arch' failed

For the full build log see 
https://buildd.debian.org/status/logs.php?pkg=ruby-fftw3&ver=0.4-6%2Bb2&arch=armhf

Emilio
--- End Message ---
--- Begin Message ---
Hi,

I am able to reliably build ruby-fftw3 on armhf in a schroot on
harris.debian.org. I am therefore closing this bug.

Attached the build log.

Cheers,

Cédric
dpkg-buildpackage: source package ruby-fftw3
dpkg-buildpackage: source version 0.4-6
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Youhei SASAKI 
dpkg-buildpackage: host architecture armhf
dh clean --buildsystem ruby --with ruby
   dh_testdir -O--buildsystem=ruby
   dh_auto_clean -O--buildsystem=ruby
  Entering dh_ruby --clean
Running 'make distclean || make clean' in /home/boutil/ruby-fftw3-0.4...
make[1]: Entering directory '/home/boutil/ruby-fftw3-0.4'
make[1]: Leaving directory '/home/boutil/ruby-fftw3-0.4'
  Leaving dh_ruby --clean
   dh_clean -O--buildsystem=ruby
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building ruby-fftw3 using existing 
./ruby-fftw3_0.4.orig.tar.gz
dpkg-source: info: building ruby-fftw3 in ruby-fftw3_0.4-6.debian.tar.xz
dpkg-source: info: building ruby-fftw3 in ruby-fftw3_0.4-6.dsc
dh build --buildsystem ruby --with ruby
   dh_testdir -O--buildsystem=ruby
   dh_auto_configure -O--buildsystem=ruby
   dh_auto_build -O--buildsystem=ruby
   dh_auto_test -O--buildsystem=ruby
dh binary --buildsystem ruby --with ruby
   dh_testroot -O--buildsystem=ruby
   dh_prep -O--buildsystem=ruby
   dh_installdirs -O--buildsystem=ruby
   dh_auto_install -O--buildsystem=ruby
  Entering dh_ruby --install
Building extension for ruby2.1 ...
/usr/bin/ruby2.1 extconf.rb
checking for narray.h... yes
checking for narray_config.h... yes
checking for fftw3.h... yes
checking for main() in -lfftw3... yes
checking for main() in -lfftw3f... yes
creating Makefile
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/home/boutil/ruby-fftw3-0.4'
rm -f 
rm -f fftw3.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/home/boutil/ruby-fftw3-0.4'
make V=1 "DESTDIR="
make[1]: Entering directory '/home/boutil/ruby-fftw3-0.4'
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 
-I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. 
-DHAVE_NARRAY_H -DHAVE_NARRAY_CONFIG_H -DHAVE_FFTW3_H -I/usr/include 
-I/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0 -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64  -fPIC -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -DFFTW3_HAS_SINGLE_SUPPORT  -o na_fftw3.o -c 
na_fftw3.c
rm -f fftw3.so
gcc -shared -o fftw3.so na_fftw3.o -L. -L/usr/lib/arm-linux-gnueabihf 
-L/usr/lib -L/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0 -L. 
-Wl,-z,relro -L/build/ruby2.1-xqAFpt/ruby2.1-2.1.3/debian/lib -fstack-protector 
-rdynamic -Wl,-export-dynamic-lruby-2.1 -lfftw3f -lfftw3  -lpthread -lgmp 
-ldl -lcrypt -lm   -lc
make[1]: Leaving directory '/home/boutil/ruby-fftw3-0.4'
make V=1 "DESTDIR=" install
make[1]: Entering directory '/home/boutil/ruby-fftw3-0.4'
/bin/mkdir -p . ./.gem.20141008-10612-3t65e4/numru
exit > .RUBYARCHDIR.-.numru.time
/usr/bin/install -c -m 0755 fftw3.so ./.gem.20141008-10612-3t65e4/numru
make[1]: Leaving directory '/home/boutil/ruby-fftw3-0.4'
Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml 
...
Lo

Bug#754609: marked as done (kexec-tools: FTBFS on powerpc: kexec-elf-ppc.c:456:3: error: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 21:20:19 +
with message-id 
and subject line Bug#754609: fixed in kexec-tools 1:2.0.7-2
has caused the Debian Bug report #754609,
regarding kexec-tools: FTBFS on powerpc: kexec-elf-ppc.c:456:3: error: format 
not a string literal and no format arguments
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.)


-- 
754609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kexec-tools
Version: 1:2.0.7-1
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on powerpc:
| gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -fno-strict-aliasing -Wall -Wstrict-prototypes 
-D_FORTIFY_SOURCE=2 -I./include -I./util_lib/include -Iinclude/ 
-I./kexec/libfdt -I./kexec/arch/ppc/include  -c -MD -o 
kexec/arch/ppc/kexec-elf-ppc.o kexec/arch/ppc/kexec-elf-ppc.c
| kexec/arch/ppc/kexec-elf-ppc.c: In function 'elf_ppc_load':
| kexec/arch/ppc/kexec-elf-ppc.c:456:3: error: format not a string literal and 
no format arguments [-Werror=format-security]
|die(error_msg);
|^
| kexec/arch/ppc/kexec-elf-ppc.c:182:6: warning: variable 'target_is_gamecube' 
set but not used [-Wunused-but-set-variable]
|   int target_is_gamecube = 0;
|   ^
| kexec/arch/ppc/kexec-elf-ppc.c:452:2: warning: 'crash_cmdline' may be used 
uninitialized in this function [-Wmaybe-uninitialized]
|   free(crash_cmdline);
|   ^
| cc1: some warnings being treated as errors

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=kexec-tools&arch=powerpc&ver=1%3A2.0.7-1&stamp=1404934775

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: kexec-tools
Source-Version: 1:2.0.7-2

We believe that the bug you reported is fixed in the latest version of
kexec-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Khalid Aziz  (supplier of updated kexec-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: SHA1

Format: 1.8
Date: Wed, 08 Oct 2014 11:01:58 -0600
Source: kexec-tools
Binary: kexec-tools kexec-tools-udeb
Architecture: source amd64
Version: 1:2.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Khalid Aziz 
Changed-By: Khalid Aziz 
Description:
 kexec-tools - tools to support fast kexec reboots
 kexec-tools-udeb - tools to support fast kexec reboots (udeb) (udeb)
Closes: 699008 729451 734697 747119 754609 756127 757510 764360
Changes:
 kexec-tools (1:2.0.7-2) unstable; urgency=medium
 .
   * Fix build failure on ppc (closes: Bug#754609)
   * Replaced s390 arch with s390x (closes: Bug#729451)
   * Added patch from Roland to support powerpcspe (closes: Bug#734697)
   * Added support for systemd (closes: Bug#764360, closes: Bug#699008)
   * Enhanced kexec init scripts to work with systemd as well and now
 "sudo reboot" from an X11 terminal works (closes: Bug#747119)
   * Includes upstream fix to align initrd_base address to pagesize
 (closes: Bug#756127)
   * Added Turkish translation (closes: Bug#757510)
Checksums-Sha1:
 c089457998a0fc6948ab6920b96e6c087d940c92 1468 kexec-tools_2.0.7-2.dsc
 f3143c33a1446eaa4c6c9143243a23ffd539ee8f 19740 
kexec-tools_2.0.7-2.debian.tar.xz
 cc8ee228fbe9611b380374dfc7c319c3ac4c41c8 80002 kexec-tools_2.0.7-2_amd64.deb
 2a89652d20cfa776856d8cd7c6058da64636ca44 52002 
kexec-tools-udeb_2.0.7-2_amd64.udeb
Checksums-Sha256:
 dce81d5f2988b444894edd332406bebaa1ebaea85780188b12d2161cd2651d8b 1468 
kexec-tools_2.0.7-2.dsc
 8ac249575288e2575b508ad640ee05c40d5898e2ff7e8ee0b57ffb1523a6bbbd 19740 
kexec-tools_2.0.7-2.debian.tar.xz
 e0dcb95401acc65945b6024c575eb4a8e4d3305a28cb98e6753a9a0ab19447a4 80002 
kexec-tools_2.0.7-2_amd64.deb
 f3d0a5344e580ef6755e2338d75004628ccd4dce1514d79a2ed8398508afe3fc 52002 
kexec-tools-udeb_2.0.7-2_amd64.udeb
Files:
 99392378a10e6fe1804483ed559dd3ae 1468 admin optional kexec-tools_2.0.7-2.dsc
 986ad08eea6ffa88d98a8eb85114be72 19740 admin optional 
kexec-tools_2.0.7-2.debian.tar.xz
 993ac34aad596ad4ed328ccdad9bc1df 80002 admin optional 
kexec-tools_2.0.7-2_amd64.deb
 1802d6bf3955bbc89c34a

Bug#764360: marked as done (kexec doesn't work with systemd)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 21:20:19 +
with message-id 
and subject line Bug#764360: fixed in kexec-tools 1:2.0.7-2
has caused the Debian Bug report #764360,
regarding kexec doesn't work with systemd
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.)


-- 
764360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kexec-tools
Version: 1:2.0.4-1
Severity: serious

Hi,

the purpose of kexec is that it works 'out-of-the-box', this doesn't
work anymore with a default jessie system (kexec 1:2.0.4-1, systemd
215-5+b1), a 'normal' reboot with kexec now behaves like a coldreboot,
so kexec-tools is basically useless with systemd now.

Regards,
Daniel

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/
--- End Message ---
--- Begin Message ---
Source: kexec-tools
Source-Version: 1:2.0.7-2

We believe that the bug you reported is fixed in the latest version of
kexec-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 764...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Khalid Aziz  (supplier of updated kexec-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: SHA1

Format: 1.8
Date: Wed, 08 Oct 2014 11:01:58 -0600
Source: kexec-tools
Binary: kexec-tools kexec-tools-udeb
Architecture: source amd64
Version: 1:2.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Khalid Aziz 
Changed-By: Khalid Aziz 
Description:
 kexec-tools - tools to support fast kexec reboots
 kexec-tools-udeb - tools to support fast kexec reboots (udeb) (udeb)
Closes: 699008 729451 734697 747119 754609 756127 757510 764360
Changes:
 kexec-tools (1:2.0.7-2) unstable; urgency=medium
 .
   * Fix build failure on ppc (closes: Bug#754609)
   * Replaced s390 arch with s390x (closes: Bug#729451)
   * Added patch from Roland to support powerpcspe (closes: Bug#734697)
   * Added support for systemd (closes: Bug#764360, closes: Bug#699008)
   * Enhanced kexec init scripts to work with systemd as well and now
 "sudo reboot" from an X11 terminal works (closes: Bug#747119)
   * Includes upstream fix to align initrd_base address to pagesize
 (closes: Bug#756127)
   * Added Turkish translation (closes: Bug#757510)
Checksums-Sha1:
 c089457998a0fc6948ab6920b96e6c087d940c92 1468 kexec-tools_2.0.7-2.dsc
 f3143c33a1446eaa4c6c9143243a23ffd539ee8f 19740 
kexec-tools_2.0.7-2.debian.tar.xz
 cc8ee228fbe9611b380374dfc7c319c3ac4c41c8 80002 kexec-tools_2.0.7-2_amd64.deb
 2a89652d20cfa776856d8cd7c6058da64636ca44 52002 
kexec-tools-udeb_2.0.7-2_amd64.udeb
Checksums-Sha256:
 dce81d5f2988b444894edd332406bebaa1ebaea85780188b12d2161cd2651d8b 1468 
kexec-tools_2.0.7-2.dsc
 8ac249575288e2575b508ad640ee05c40d5898e2ff7e8ee0b57ffb1523a6bbbd 19740 
kexec-tools_2.0.7-2.debian.tar.xz
 e0dcb95401acc65945b6024c575eb4a8e4d3305a28cb98e6753a9a0ab19447a4 80002 
kexec-tools_2.0.7-2_amd64.deb
 f3d0a5344e580ef6755e2338d75004628ccd4dce1514d79a2ed8398508afe3fc 52002 
kexec-tools-udeb_2.0.7-2_amd64.udeb
Files:
 99392378a10e6fe1804483ed559dd3ae 1468 admin optional kexec-tools_2.0.7-2.dsc
 986ad08eea6ffa88d98a8eb85114be72 19740 admin optional 
kexec-tools_2.0.7-2.debian.tar.xz
 993ac34aad596ad4ed328ccdad9bc1df 80002 admin optional 
kexec-tools_2.0.7-2_amd64.deb
 1802d6bf3955bbc89c34a84fed6697f0 52002 debian-installer optional 
kexec-tools-udeb_2.0.7-2_amd64.udeb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQ1lC4ACgkQlQEY26iVtiGBCwCfcHaCnem5RXw6KYrVl23zioiO
g0UAn1TwPkPYBES346ee26vHryXfbOEQ
=f4Jx
-END PGP SIGNATURE End Message ---

Bug#758165: gcc-4.9 devirtualisation bug affecting wxwidgets3.0 now fixed

[Johan Van de Wauw]

On Wed, Oct 8, 2014 at 10:22 PM, Niko Tyni  wrote:
> On Tue, Oct 07, 2014 at 12:40:46PM +1300, Olly Betts wrote:
>> On Mon, Sep 01, 2014 at 09:51:37PM -0300, Olly Betts wrote:
>> > There's an issue with devirtualisation in GCC 4.9 which wx3 triggers,
>> > which may be connected:
>> >
>> > https://bugs.debian.org/752733
>>
>> This was fixed in gcc-4.9 4.9.1-14, so it would be useful to check if
>> libwx-perl and sage now work OK on armel and armhf, or if there's
>> something else going on here.
>
> I tried building libwx-perl on armel / abel.debian.org in a jessie chroot
> (the build dependencies are uninstallable in sid right now), with gcc-4.9
> 4.9.1-16, and still got
>
> t/01_load.t ... 1/6 Can't load 
> '/home/ntyni/libwx-perl-0.9923/blib/arch/auto/Wx/PropertyGrid/PropertyGrid.so'
>  for module Wx::PropertyGrid:  at 
> /home/ntyni/libwx-perl-0.9923/blib/lib/Wx/Mini.pm line 74.
>
> which looks like the problem is still present.
On armhf, I managed to get saga gui linking again.

Johan


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#758165: gcc-4.9 devirtualisation bug affecting wxwidgets3.0 now fixed

[Olly Betts]

On Wed, Oct 08, 2014 at 11:22:20PM +0300, Niko Tyni wrote:
> But we probably need the wxwidgets3.0 packages built with a fixed
> gcc-4.9 first?

The problematic code is inlined from a wx API header, so I suspect not,
but maybe there's something in the rebuilt library too.

> This was jessie's 3.0.1-3, and buildd logs say it was built in August
> with 4.9.0-10.

Yes, that sounds about right.

> I've filed #764525 to fix the uninstallability in sid and can re-test
> when the binNMUs are built. The porter box setup doesn't really allow for
> manually built binaries or mixing distributions AFAICS.

Even if the issue is header-only, it would definitely be good to retest
with 3.0.2-1 (in unstable only currently) in case there are changes in
the new upstream version which have solved this issue, especially as
Johan reports sage now builds OK.

Cheers,
Olly


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#733013: marked as done (red5: FTBFS: error: method populate in class BeanUtils cannot be applied to given types)

[Debian Bug Tracking System]

Your message dated Wed, 08 Oct 2014 22:49:28 +
with message-id 
and subject line Bug#733013: fixed in red5 1.0~svn4374-4
has caused the Debian Bug report #733013,
regarding red5: FTBFS: error: method populate in class BeanUtils cannot be 
applied to given types
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.)


-- 
733013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:red5
Version: 1.0~svn4374-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Failed build complete log file is attached.

Relevant error messages:

[...]
retrieve:
[javac] Compiling 492 source files to /tmp/buildd/red5-1.0~svn4374/bin
[javac] Since fork is false, ignoring memoryInitialSize setting.
[javac] Since fork is false, ignoring memoryMaximumSize setting.
[javac] 
/tmp/buildd/red5-1.0~svn4374/src/org/red5/server/util/ConversionUtils.java:392: 
error: method populate in class BeanUtils cannot be applied to given types;
[javac] BeanUtils.populate(bean, source);
[javac]  ^
[javac]   required: Object,Map
[javac]   found: Object,Map
[javac]   reason: actual argument Map cannot be converted to 
Map by method invocation conversion
[javac]   where CAP#1,CAP#2 are fresh type-variables:
[javac] CAP#1 extends Object from capture of ?
[javac] CAP#2 extends Object from capture of ?
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error

BUILD FAILED
/tmp/buildd/red5-1.0~svn4374/debian/build.xml:11: The following error occurred 
while executing this line:
/tmp/buildd/red5-1.0~svn4374/build.xml:206: The following error occurred while 
executing this line:
/tmp/buildd/red5-1.0~svn4374/build.xml:223: Compile failed; see the compiler 
error output for details.

Total time: 20 seconds
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
 -> Cleaning COW directory
  forking: rm -rf /var/cache/pbuilder/build//cow.7046 

-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at
http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9
"Faith means not wanting to know what is true." -- Nietzsche


red5_1.0~svn4374-3_amd64.build.gz
Description: Binary data


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: red5
Source-Version: 1.0~svn4374-4

We believe that the bug you reported is fixed in the latest version of
red5, 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 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated red5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Oct 2014 13:04:23 +0200
Source: red5
Binary: libred5-java red5-server red5-doc
Architecture: source all
Version: 1.0~svn4374-4
Distribution: unstable
Urgency: medium
Maintainer: Damien Raude-Morvan 
Changed-By: Emmanuel Bourg 
Description:
 libred5-java - remote API for Red5 flash streaming server
 red5-doc   - flash streaming server - documentation
 red5-server - flash streaming server
Closes: 686880 733013
Changes:
 red5 (1.0~svn4374-4) unstable; urgency=medium
 .
   [ Emmanuel Bourg ]
   * Team upload.
   * Fixed the build failure with BeanUtils 1.9 (Closes: 

Bug#764547: bsdutils: script(1) is broken, hangs or crashes

[Thorsten Glaser]

Package: bsdutils
Version: 1:2.25.1-3
Severity: serious
Tags: upstream
Justification: crashes
Forwarded: http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/1

Hi,

as I reported upstream in
http://article.gmane.org/gmane.linux.utilities.util-linux-ng/1
the script(1) in util-linux 2.25.1 is broken, whereas the one
in util-linux 2.20.1 as currently in jessie works fine. This applies
to both my x32 regular machine as well as a clean, minimal amd64 and
i386 cowbuilder sid chroot, as well as the OpenSuSE Buildservice setup.

This bug opened in Debian to prevent a crashing script(1) from
migrating to testing, and to track progress.

-- System Information:
Debian Release: jessie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh

Versions of packages bsdutils depends on:
ii  libc62.19-11
ii  libsystemd0  215-5+b1

Versions of packages bsdutils recommends:
ii  bsdmainutils  9.0.5

bsdutils 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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 764547 src:mksh
Bug #764547 [bsdutils] bsdutils: script(1) is broken, hangs or crashes
Added indication that 764547 affects src:mksh
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764547
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#764472: cups creates millions of temporary files when printing

[Brian Potkin]

Hello Antonio,

Thank you for your report. The first thing to say is that this is very
likely not to be a bug in cups. Please see

  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/890705

and

  https://bugzilla.redhat.com/show_bug.cgi?id=581748

So - do you have acroread installed?


On Wed 08 Oct 2014 at 14:04:46 +0200, Antonio Sartori wrote:

> When trying to print (tried twice from evince, not tested from other
> software), cups creates millions of symbolic links in /tmp to the ppd
> driver in /etc/cups/ppd. The names of the symbolic links are similar
> to 54351da228fae.

Millions of links would imply lots of printing taking place and not just
twice. Is that the case? Also, does it occur with other applications? We
really need to track down under what circumstances the files are created
and why they are not deleted by the application.
 
> This causes the system to hang on the next reboot while systemd tries
> to empty the tmp folder, making the system unbootable.

Do you mean it hangs indefinitely and the machine has to powered off to
be restarted?

> Notice that deleting the files by hand is tricky, since they are too
> many (rm does not work, it is not even possible to list the files with
> ls), I don't know how to do this. For now, I rebooted the system using
> a live dist and I typed mv /tmp /tmp2. This enables the system to boot
> again. Help on how I can delete the folder tmp2 would also be
> appreciated.

I'm surprised 'ls -l' doesn't work. Is there any error message? What
about 'ls -l | head'.

'rm -r /tmp2' should delete /tmp2.

Regards,

Brian.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#764548: chromium: fails to build due to missing libgnome-keyring-dev build-dependency

[Andreas Cadhalpun]

Source: chromium-browser
Version: 37.0.2062.120-4
Severity: serious
Justification: fails to build from source

Dear Maintainer,

chromium failed to build on amd64 [1]:
Package gnome-keyring-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gnome-keyring-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gnome-keyring-1' found

This is due to a missing build-dependency on libgnome-keyring-dev.

Even with that installed the binary package misses a dependency on 
libgnome-keyring0, because 'linux_link_gnome_keyring=1' is not added to 
the defines.


Additionally h264 support got disabled, because 'proprietary_codecs=1' 
is not used anymore.


Attached patch fixes these issues, please consider applying it.

Best regards,
Andreas

PS: Please keep the git repository up to date. (Currently the last known 
upload there is 37.0.2062.120-2.) This would help with figuring out what 
changelog entries like 'Merge changes from the experimental branch' mean.

E.g. what happened with the disable/google-api-warning.patch?

1: 
https://buildd.debian.org/status/fetch.php?pkg=chromium-browser&arch=amd64&ver=37.0.2062.120-4&stamp=1412576129
diff --git a/debian/control b/debian/control
index 488ad96..e647d86 100644
--- a/debian/control
+++ b/debian/control
@@ -81,6 +81,7 @@ Build-Depends:
  libgcrypt11-dev | libgcrypt20-dev,
  fonts-ipafont-gothic,
  fonts-ipafont-mincho,
+ libgnome-keyring-dev,
 Built-Using:
  libjs-jquery,
  libjs-jquery-flot,
diff --git a/debian/rules b/debian/rules
index b0e5a15..797ee58 100755
--- a/debian/rules
+++ b/debian/rules
@@ -40,6 +40,8 @@ defines+=enable_hidpi=1 \
  linux_link_libpci=1 \
  linux_link_gsettings=1 \
  linux_link_libspeechd=1 \
+ linux_link_gnome_keyring=1 \
+ proprietary_codecs=1 \
 
 # system libraries to use
 defines+=use_system_re2=1 \

Bug#749659: audacity: Systematic check for Printf/Format mismatches

[Benjamin Drung]

Hi all,

sorry for reacting too lazy.

Am Montag, den 06.10.2014, 02:33 +0100 schrieb Olly Betts:
> On Thu, Oct 02, 2014 at 10:42:07PM +0200, Martin Steghöfer wrote:
> > Find attached the (hopefully) final debdiff from my side. It's big,
> > but relatively easy to review because most of the changes can be
> > interpreted independently.
> 
> Thanks for all your work on this, Martin.
> 
> Is someone looking at this with an eye to getting an updated version of
> audacity actually uploaded?
> 
> This is now the last package waiting for an upload in the wxwidgets3.0
> transition, and the latest upload date to make it to testing before the
> release freeze is now less than 3 weeks away (the freeze is November
> 5th, but an upload would need to age for 10 days).
> 
> I can NMU with this patch if need be, but if the package maintainers are
> already on the case there's no point me duplicating their efforts.

I finally found time to import the upstream release 2.0.6, backport the
preliminary upstream changes for wxWidgets 3.0.1 from r13403, and pushed
everything to our git repository. Your patch needs to be forward ported,
which I will try to do when I have some spare time (knowing that it
should be done ASAP due to the nearing freeze). I would be happy to get
help forward porting the patch.

PS: I was reluctant to upload the debdiff because I liked to see the
patch for 2.0.6 (which has autoreconf fixed). Upstream want to get wx3.0
support in for 2.0.7 and is actively working on getting it in the svn
repository. So you could provide the missing bits and we will get
upstream to test your proposed changes (when I commit them to the
upstream repository).

-- 
Benjamin Drung
Debian & Ubuntu Developer


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#758619: pyrenamer: Attempt to unlock mutex that was not locked

[sp113438]

pyrenamer also gives:

Attempt to unlock mutex that was not locked
Aborted

Thanks!


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#758619: Attempt to unlock mutex that was not locked

[sp113438]

It happens on Sid as well as Jessie (amd64).

Thanks


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#754625: marked as done (cutesdr: FTBFS on i386: interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm')

[Debian Bug Tracking System]

Your message dated Wed, 8 Oct 2014 19:36:26 -0400
with message-id <21557.51834.158675.657...@airborne.nrl.navy.mil>
and subject line cutesdr: FTBFS on i386: interface/perform.cpp:70:59: error: 
PIC register clobbered by 'bx' in 'asm'
has caused the Debian Bug report #754625,
regarding cutesdr: FTBFS on i386: interface/perform.cpp:70:59: error: PIC 
register clobbered by 'bx' in 'asm'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cutesdr
Version: 1.13.42-1
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on i386:
| g++ -c -pipe -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 
-Wformat -Werror=format-security -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-Wall -W -D_REENTRANT -fPIE -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB 
-DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
-I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -I. -I/usr/include/qt5 
-I/usr/include/qt5/QtMultimedia -I/usr/include/qt5/QtWidgets 
-I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtCore 
-I. -I. -o perform.o interface/perform.cpp
| interface/perform.cpp: In function 'void StartPerformance()':
| interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm'
|   __asm__ __volatile__("cpuid": : : "ax", "bx", "cx", "dx");
|^
| interface/perform.cpp: In function 'void StopPerformance(int)':
| interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm'
|   __asm__ __volatile__("cpuid": : : "ax", "bx", "cx", "dx");
|^
| interface/perform.cpp: In function 'void SamplePerformance()':
| interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm'
|   __asm__ __volatile__("cpuid": : : "ax", "bx", "cx", "dx");
|^
| interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm'
|   __asm__ __volatile__("cpuid": : : "ax", "bx", "cx", "dx");
|^
| interface/perform.cpp:70:59: error: PIC register clobbered by 'bx' in 'asm'
|   __asm__ __volatile__("cpuid": : : "ax", "bx", "cx", "dx");
|^
| make[1]: *** [perform.o] Error 1
| make[1]: Leaving directory `/«PKGBUILDDIR»'

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=cutesdr&arch=i386&ver=1.13.42-1&stamp=1399152943

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Version: 1.13.42-2

As cutesdr 1.13.42-2 is built and installed on all linux-any
architectures, this bug can be closed.

-Maitland--- End Message ---

Processed: Re: Bug#747983: kfreebsd-9: non-standard gcc/g++ used for build (gcc-4.6)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 747983 + pending
Bug #747983 [kfreebsd-9] kfreebsd-9: non-standard gcc/g++ used for build 
(gcc-4.6)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747983
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#751238: Reopen bug report for switching hwclock-set to use hctosys

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.25.1-4
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
There is no source info for the package 'util-linux' at version '2.25.1-4' with 
architecture ''
There is no source info for the package 'linux' at version '2.25.1-4' with 
architecture ''
Unable to make a source version for version '2.25.1-4'
No longer marked as found in versions 2.25.1-4.
> clone -1 -2
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
Bug 751238 cloned as bug 764552
> retitle -2 hwclock-set misconfigures kernel for NTP when RTC holds local time
Bug #764552 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
Changed Bug title to 'hwclock-set misconfigures kernel for NTP when RTC holds 
local time' from 'util-linux/linux: ignores RTC when the RTC driver is a module'
> notfound -1 2.20.1-5
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
There is no source info for the package 'linux' at version '2.20.1-5' with 
architecture ''
No longer marked as found in versions util-linux/2.20.1-5.
> close -1 2.25-2
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
There is no source info for the package 'linux' at version '2.25-2' with 
architecture ''
Marked as fixed in versions util-linux/2.25-2.
Bug #751238 [util-linux,linux] util-linux/linux: ignores RTC when the RTC 
driver is a module
Marked Bug as done
> found -2 2.25-2
Bug #764552 [util-linux,linux] hwclock-set misconfigures kernel for NTP when 
RTC holds local time
There is no source info for the package 'linux' at version '2.25-2' with 
architecture ''
Marked as found in versions util-linux/2.25-2.
> found -2 2.25.1-3
Bug #764552 [util-linux,linux] hwclock-set misconfigures kernel for NTP when 
RTC holds local time
There is no source info for the package 'linux' at version '2.25.1-3' with 
architecture ''
Marked as found in versions util-linux/2.25.1-3.
> severity -2 serious
Bug #764552 [util-linux,linux] hwclock-set misconfigures kernel for NTP when 
RTC holds local time
Severity set to 'serious' from 'important'

-- 
751238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751238
764552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764552
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 764552 to util-linux, submitter 764552

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 764552 util-linux
Bug #764552 [util-linux,linux] hwclock-set misconfigures kernel for NTP when 
RTC holds local time
Bug reassigned from package 'util-linux,linux' to 'util-linux'.
No longer marked as found in versions util-linux/2.25.1-3, util-linux/2.25-2, 
and util-linux/2.20.1-5.
Ignoring request to alter fixed versions of bug #764552 to the same values 
previously set
> submitter 764552 Michael Biebl 
Bug #764552 [util-linux] hwclock-set misconfigures kernel for NTP when RTC 
holds local time
Changed Bug submitter to 'Michael Biebl ' from 'Aurelien 
Jarno '
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764552
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