Bug#798237: isc-dhcp-server: after upgrading to 4.3.3-3 the server doesn't start

[Elimar Riesebieter]

Package: isc-dhcp-server
Version: 4.3.2-1
Severity: grave
Justification: renders package unusable

Setting up isc-dhcp-server (4.3.3-3) ...
Installing new version of config file /etc/init.d/isc-dhcp-server ...
dhcpd self-test failed. Please fix /etc/dhcp/dhcpd.conf.
The error was:
Internet Systems Consortium DHCP Server 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Support for ddns-update-style not compiled in

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

The error was: 
Is not that much expressive

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.1.6-baumbart-lxtec-i686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.57
ii  debianutils4.5.1
ii  isc-dhcp-common4.3.2-1
ii  libc6  2.19-19
ii  libdns-export100   1:9.9.5.dfsg-12
ii  libirs-export911:9.9.5.dfsg-12
ii  libisc-export951:9.9.5.dfsg-12
ii  lsb-base   4.1+Debian14

isc-dhcp-server recommends no packages.

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed:
authoritative;
ddns-update-style interim;
ddns-updates on;
ddns-domainname "home.lxtec.de";
ddns-rev-domainname "in-addr.arpa.";
option domain-name "home.lxtec.de";
option domain-name-servers 192.168.200.1;
default-lease-time 28800;
max-lease-time 86400;
ignore client-updates;
log-facility local7;
update-static-leases true;
include "/etc/bind/rndc.key";
 zone home.lxtec.de. {
 primary 192.168.200.1;
 key "lxtec-dhcp";
 }
 zone 200.168.192.in-addr.arpa. {
 primary 192.168.200.1;
 key "lxtec-dhcp";
 }
   # Ein paar feste IP-Adressen werden vergeben
# INTEL 2400 Linux
host gandalf {
option dhcp-client-identifier 1:0:1b:21:70:ec:ca;
fixed-address 192.168.200.201;
ddns-hostname "gandalf";
option host-name "gandalf";
max-lease-time 28800;
}
 ..
 
   subnet 192.168.200.0 netmask 255.255.255.0 {
   option domain-name-servers 192.168.200.1;
   option broadcast-address 192.168.200.255;
   option routers 192.168.200.254;
   range 192.168.200.100 192.168.200.199;
 }

/etc/logcheck/ignore.d.server/isc-dhcp-server 71f490713ed345ec955be8e2a5bc6cf4 
[Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/isc-dhcp-server 
71f490713ed345ec955be8e2a5bc6cf4'

-- debconf information:
  isc-dhcp-server/config_warn:
  isc-dhcp-server/interfaces:

Bug#787533: [debian-mysql] Bug#787533: Bug#787533: Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

[Otto Kekäläinen]

2015-08-14 11:18 GMT+03:00 Otto Kekäläinen :
> For the record: mariadb-10.0 with these changes was uploaded to
> unstable weeks ago, but it cannot enter testing, as it now has a
> versioned dependency on mysql-5.6, which due to other problems in that
> package does not enter testing.
>
> For the time beeing, new versions of mariadb-10.0 entering testing is
> tied to mysql-5.6 entering testing, which is a bit suboptimal. For
> example testing still has only 10.0.19 and is missing the security
> fixes included in 10.0.20.

This is still the status. Over 40 days has already passed of waiting
for mysql-5.6.

Andreas: are you still into making mysql-common a separate source
package as you suggested in the summer? I think it would be a good
time now.

Processed: bug 796197 is forwarded to http://www.sogo.nu/bugs/view.php?id=3246

[Debian Bug Tracking System]

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

> forwarded 796197 http://www.sogo.nu/bugs/view.php?id=3246
Bug #796197 [src:sogo] CVE-2015-5395
Set Bug forwarded-to-address to 'http://www.sogo.nu/bugs/view.php?id=3246'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#791732: marked as done (FTBFS with GCC 5: new symbols appeared in the symbols file)

[Debian Bug Tracking System]

Your message dated Mon, 07 Sep 2015 01:34:48 -0400
with message-id <1929516.VaJREE3UXL@kitterma-e6430>
and subject line Already marked fixed
has caused the Debian Bug report #791732,
regarding FTBFS with GCC 5: new symbols appeared in the symbols 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.)


-- 
791732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: modemmanager-qt
Version: 5.11.0-1
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

This package fails to build with GCC 5:

> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
> dh_strip  --dbg-package=libkf5modemmanagerqt6-dbg
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkf5modemmanagerqt6/DEBIAN/symbols doesn't 
> match completely debian/libkf5modemmanagerqt6.symbols
> --- debian/libkf5modemmanagerqt6.symbols 
> (libkf5modemmanagerqt6_5.11.0-1_amd64)
> +++ dpkg-gensymbolseWZ62M 2015-07-07 21:37:56.547869390 +
> @@ -269,9 +269,9 @@
>   _ZN12ModemManager8Notifier15serviceAppearedEv@Base 5.8.50
>   _ZN12ModemManager8Notifier16staticMetaObjectE@Base 5.8.50
>   _ZN12ModemManager8Notifier18serviceDisappearedEv@Base 5.8.50
> - _ZN12ModemManager8NotifierD0Ev@Base 5.8.50
> - _ZN12ModemManager8NotifierD1Ev@Base 5.8.50
> - _ZN12ModemManager8NotifierD2Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD0Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD1Ev@Base 5.8.50
> +#MISSING: 5.11.0-1# _ZN12ModemManager8NotifierD2Ev@Base 5.8.50
>   _ZN12ModemManager8notifierEv@Base 5.8.50
>   _ZN12ModemManager9Interface11qt_metacallEN11QMetaObject4CallEiPPv@Base 
> 5.8.50
>   _ZN12ModemManager9Interface11qt_metacastEPKc@Base 5.8.50
> dh_makeshlibs: failing due to earlier errors
> make[1]: *** [pre_binary_dh_makeshlibs] Error 2
> /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
> 'pre_binary_dh_makeshlibs' failed
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> make: *** [debian/dhmk_binary] Error 2
> /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
> 'debian/dhmk_binary' failed
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2

-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 53530--- End Message ---

Bug#798172: marked as done (python-casmoothing: depends on vtk 5)

[Debian Bug Tracking System]

Your message dated Mon, 07 Sep 2015 07:53:36 +0200
with message-id <55ed2660.3050...@thykier.net>
and subject line Re: python-casmoothing: depends on vtk 5
has caused the Debian Bug report #798172,
regarding python-casmoothing: depends on vtk 5
to be marked as done.

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

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


-- 
798172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-casmoothing
Version: 0.1-2
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.2-1

On Sun, 6 Sep 2015 13:17:47 +0200 Julien Cristau 
wrote:
> Source: python-casmoothing
> Version: 0.1-2
> Severity: serious
> Tags: sid stretch
> Control: block 798164 with -1
> 
> Hi,
> 
> your package depends on vtk 5.x, which should not be in stretch.  Please
> switch to vtk 6.x or drop the dependency.
> 
> Thanks,
> Julien

Fixed in unstable, just needs to migrate.

Thanks,
~Niels--- End Message ---

Bug#795940: vcr.py: FTBFS: Build requires internet access ("gaierror: [Errno -2] Name or service not known")

[Daniel Stender]

Upstream plans to run the tests completely on pytest-httpbin, which provides a 
locally running
instance of httpbin [1]. There are already some steps towards this in the 
pytest-httpbin branch [2].

I'm working on pytest-httpbin [3] and httpbin [4] to make them available. When 
they are becoming, either upstream
made this feature available or maybe some patch work would be necessary.

I'm on it.

DS

[1] https://github.com/kevin1024/vcrpy/issues/142
Use pytest-httpbin

[2] https://github.com/kevin1024/vcrpy/compare/pytest-httpbin

[3] http://bugs.debian.org/787114
ITP: pytest-httpbin -- Test an HTTP library against a local copy of 
httpbin.org

[4] http://bugs.debian.org/787113
ITP: httpbin -- HTTP Request and Response Service

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Bug#798190: reads nonexistant dir, segfaults Kodi on startup

[Bálint Réczey]

Hi Steinar,

2015-09-06 19:51 GMT+02:00 Steinar H. Gunderson :
> On Sun, Sep 06, 2015 at 07:48:24PM +0200, Bálint Réczey wrote:
>> Thank you for the detailed bug report.
>> Could you please test the fix built here?:
>> http://debomatic-amd64.debian.net/distribution#unstable/libcec/3.0.1+dfsg2-5
>
> Uhm, I must understand I couldn't figure that UI out at all. Do you have a
> patch?
>
> FWIW, I tried just returning immediately if the pointer from opendir is NULL,
> and that seems to have worked correctly. If your fix is anything like that,
> it should be fine.
OK, I tried that, too.
Could you please confirm if the latest upload fixed the bug?
I would forward the fix to upstream then.

Cheers,
Balint

Bug#794555: marked as done (qpdf: License/copyright holder information for multiple files not documented in debian/copyright)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 23:22:22 +
with message-id 
and subject line Bug#794555: fixed in qpdf 5.1.3-3
has caused the Debian Bug report #794555,
regarding qpdf: License/copyright holder information for multiple files not 
documented in debian/copyright
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.)


-- 
794555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qpdf
Version: 5.1.3-2
Severity: serious
Justification: Policy 4.5

Information about license and copyright holder for the following files is
missing from debian/copyright:

libqpdf/sph/sph_sha2.h
libqpdf/sph/sph_types.h
libqpdf/sph/md_helper.c
libqpdf/sha2big.c
libqpdf/sha2.c
libqpdf/MD5.cc

Since this is not a new problem for this upload, I'm going to go ahead and
accept the current upload, but please fix this in your next upload.
--- End Message ---
--- Begin Message ---
Source: qpdf
Source-Version: 5.1.3-3

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

Debian distribution maintenance software
pp.
Jay Berkenbilt  (supplier of updated qpdf 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, 06 Sep 2015 18:37:40 -0400
Source: qpdf
Binary: libqpdf13v5 libqpdf-dev qpdf
Architecture: source amd64
Version: 5.1.3-3
Distribution: unstable
Urgency: high
Maintainer: Jay Berkenbilt 
Changed-By: Jay Berkenbilt 
Description:
 libqpdf-dev - development files for PDF transformation/inspection library
 libqpdf13v5 - runtime library for PDF transformation/inspection software
 qpdf   - tools for transforming and inspecting PDF files
Closes: 794555
Changes:
 qpdf (5.1.3-3) unstable; urgency=high
 .
   * Update copyright to include a few files that had separate copyrights
 from the rest of the software. (Closes: #794555)
Checksums-Sha1:
 67aa92bc1fc84682aea8f3b67bc9001b0b05678f 1842 qpdf_5.1.3-3.dsc
 23dd57881611f012ed5d5e3145b221fabef98f27 8504 qpdf_5.1.3-3.debian.tar.xz
 b51ac29f385489a05097999f85626758e242f5c1 386760 libqpdf-dev_5.1.3-3_amd64.deb
 f7ba3d7e10a10f08dfc23215de0429c670631e2b 318960 libqpdf13v5_5.1.3-3_amd64.deb
 b497cef16c97242c072edc199c4c8e65ff598ffe 238724 qpdf_5.1.3-3_amd64.deb
Checksums-Sha256:
 91aea5bdd1d9a30d6ccda6ea40b160472a59c983ae6cd5d75a8583496789d57a 1842 
qpdf_5.1.3-3.dsc
 8acaa252911ece45820c07bfde70f006edc8207b740ff43e137db4407f8e3162 8504 
qpdf_5.1.3-3.debian.tar.xz
 93468e960cb30c8781dc090191c5b4f9357d74963a747298627f11cbf820fc2b 386760 
libqpdf-dev_5.1.3-3_amd64.deb
 3106c6fa10b209331898a7ec50bbf1ee678a36f165f63e3183764b6cdaee408b 318960 
libqpdf13v5_5.1.3-3_amd64.deb
 68f8b6cf09c255215d874af00b04299d9a1d382de3727266779c60857bd492ad 238724 
qpdf_5.1.3-3_amd64.deb
Files:
 2b95670b29eaccaec8336ad9dba092b6 1842 libs optional qpdf_5.1.3-3.dsc
 d70a286f3b166aaeed4346fa3170cc96 8504 libs optional qpdf_5.1.3-3.debian.tar.xz
 eb915943aec5518d878a73681d347bc7 386760 libdevel optional 
libqpdf-dev_5.1.3-3_amd64.deb
 3610452b88ff73a71f93f7029cab8b62 318960 libs optional 
libqpdf13v5_5.1.3-3_amd64.deb
 563f691bd874cdb74b649b23a71e5f3c 238724 text optional qpdf_5.1.3-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJV7MM7AAoJEIp10QmYASx+UY8P/2diyy2Yx55opNhP+XJ61/TI
dn1K1xDMmR8sJK5KYaBYg0GyVsOg/tQh0T5n4dJeQ/nPygTfcYbn7EVI/JWYu51B
geFyRxRnKAlignE5mTgbJR+WVgmfYslyMu2fFCb568Ed1zoOLEGxTmiifDRgmx9P
Lb6bp6/27U0orEnaCVB3Nl+xo7Uqi+vo9CS5+3h5e9NwV27BMaEWt8jHTXcvNXDr
KY7bgEysrq1O7Ua1KWMU0a0Tk22NEHv5GGMp22mTJhXPH+xFxNgyqzUMEvZDIV7i
lAI0YcM1CLH+hyqh1BZizbufcn1Xj5Z+ZlWAMSmGk0iynk6gIXkypETVaddc7N4W
D4WudVsbScCZqqrHzsDvWGCD+JivF6EIlYyOSeAN9+cB+m2Gma7MvmEQBL9poi7r
4c8fqslZIDedf60qIBgVskDe+XCcy9ViuVLK14LLGubyTKIuSt4OjikMfC6tvcgu
5fa63wIVXpVrZ96btPuEAw7BG1LEyqaWzUEBo4KeBP3lEYIB9Hy5Aa1+PchqZvNg
Sf5Aud9LD02coHylhlwynCMMLcEveI203lNRVWeDGJXjjCS4DvRTkf6Bu5k/Uhfi
GYTRGk0UpauhxBzkGQa7FyFhN1ZlMO3hFPOzPXAXnt33San7szsK+WO2np2w90uK
WEa4kBJXmzx5Mazl9tkp
=uH2r
-END PGP 

Processed: tagging 796052

[Debian Bug Tracking System]

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

> tags 796052 + stretch
Bug #796052 [src:gwenview] gwenview: FTBFS: No rule to make target 
'/usr/lib/libsoprano.so'
Added tag(s) stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#787398: Stable update? Bug#787398 (evolution-data-server: SMTP connection lost while reading message data)

[Fabian Greffrath]

Am Dienstag, den 18.08.2015, 09:58 +0200 schrieb Fabian Greffrath:
> unfortunately, I had no luck convincing the SRM to accept my proposed e
> -d-s update in Jessie in #789429. I didn't even receive a singly reply
> after ~2 months. Maybe one of you wants to try his luck with it?

So, 8.2 has been released without even a single comment to this
request. I am done with it. Feel free to reopen and try your luck. :/

 - Fabian



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

Processed: Re: Bug#794555: qpdf: License/copyright holder information for multiple files not documented in debian/copyright

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.1.3-1
Bug #794555 [qpdf] qpdf: License/copyright holder information for multiple 
files not documented in debian/copyright
Marked as found in versions qpdf/5.1.3-1.

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

Bug#794555: qpdf: License/copyright holder information for multiple files not documented in debian/copyright

[Julien Cristau]

Control: found -1 5.1.3-1

On Tue, Aug  4, 2015 at 07:36:03 -0400, Scott Kitterman wrote:

> Package: qpdf
> Version: 5.1.3-2
> Severity: serious
> Justification: Policy 4.5
> 
> Information about license and copyright holder for the following files is
> missing from debian/copyright:
> 
> libqpdf/sph/sph_sha2.h
> libqpdf/sph/sph_types.h
> libqpdf/sph/md_helper.c
> libqpdf/sha2big.c
> libqpdf/sha2.c
> libqpdf/MD5.cc
> 
> Since this is not a new problem for this upload, I'm going to go ahead and
> accept the current upload, but please fix this in your next upload.

Since this is not a new problem for this upload, it shouldn't be marked
as found in that version.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#793866: marked as done (samba: purging deletes directories (co-)owned by samba-common: /var/{cache, lib, log}/samba)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 23:38:04 +
with message-id 
and subject line Bug#793866: fixed in samba 2:4.2.1+dfsg-1
has caused the Debian Bug report #793866,
regarding samba: purging deletes directories (co-)owned by samba-common: 
/var/{cache, lib, log}/samba
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.)


-- 
793866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.17+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.

This could be a violation of policy 10.7.4 ("Sharing configuration
files"), see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.4
or policy chapter 6 ("Package maintainer scripts..."), see
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
or policy 7.6 ("Overwriting files..."), see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

If a directory is used by several packages, all should ship it as part
of the package (possibly empty, using $package.dirs to create it), and
no package should mkdir/rmdir it in the maintainer scripts as dpkg will
take care of this.

>From the attached log (scroll to the bottom...):

3m19.7s ERROR: FAIL: After purging files have disappeared:
  /var/cache/samba/  owned by: samba-common-bin, samba-common
  /var/lib/samba/owned by: samba, samba-common
  /var/log/samba/owned by: samba-common


Cheers,

Andreas


samba.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.2.1+dfsg-1

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Dec 2014 15:34:36 +
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev samba-doc 
python-samba samba-dsdb-modules samba-vfs-modules libpam-smbpass libsmbclient 
libsmbclient-dev winbind libpam-winbind libnss-winbind samba-dbg libwbclient0 
libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.2.1+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Jelmer Vernooij 
Description:
 ctdb   - clustered database to store temporary data
 libnss-winbind - Samba nameservice integration plugins
 libpam-smbpass - pluggable authentication module for Samba
 libpam-winbind - Windows domain authentication integration plugin
 libparse-pidl-perl - IDL compiler written in Perl
 libsmbclient - shared library for communication with SMB/CIFS servers
 libsmbclient-dev - development files for libsmbclient
 libwbclient-dev - Samba winbind client library - development files
 libwbclient0 - Samba winbind client library
 python-samba - Python bindings for Samba
 registry-tools - tools for viewing and manipulating the Windows registry
 samba  - SMB/CIFS file, print, and login server for Unix
 samba-common - common files used by both the Samba server and client
 samba-common-bin - Samba common files used by both the server and the client
 samba-dbg  - Samba debugging symbols
 samba-dev  - tools for extending Samba
 samba-doc  - Samba documentation
 samba-dsdb-modules - Samba Directory Services Database
 samba-libs - Samba core libraries
 samba-testsuite - test suite from Samba
 samba-vfs-modules - Samba Virtual FileSystem plugins
 smbclient  - command-line SMB/CIFS clients for Unix
 winbind- service to resolve user and group information from Windows NT ser
Closes: 793866

Bug#735255: marked as done (samba-common-bin: net ads join needs /var/lib/samba/private)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 23:38:04 +
with message-id 
and subject line Bug#793866: fixed in samba 2:4.2.1+dfsg-1
has caused the Debian Bug report #793866,
regarding samba-common-bin: net ads join needs /var/lib/samba/private
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.)


-- 
793866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-common-bin
Version: 2:4.0.13+dfsg-1
Severity: wishlist

After I patched samba to fix #732604 (winbind dep on samba) I found out
that net ads join no longer works because it operates secrets.tdb
from /var/lib/samba/private which is only in the samba, samba4 packages.
I propose to add /var/lib/samba/private to samba-common-bin too so that
'net ads join' can create secrets.tdb in /var/lib/samba/private.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.2.1+dfsg-1

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Dec 2014 15:34:36 +
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev samba-doc 
python-samba samba-dsdb-modules samba-vfs-modules libpam-smbpass libsmbclient 
libsmbclient-dev winbind libpam-winbind libnss-winbind samba-dbg libwbclient0 
libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.2.1+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Jelmer Vernooij 
Description:
 ctdb   - clustered database to store temporary data
 libnss-winbind - Samba nameservice integration plugins
 libpam-smbpass - pluggable authentication module for Samba
 libpam-winbind - Windows domain authentication integration plugin
 libparse-pidl-perl - IDL compiler written in Perl
 libsmbclient - shared library for communication with SMB/CIFS servers
 libsmbclient-dev - development files for libsmbclient
 libwbclient-dev - Samba winbind client library - development files
 libwbclient0 - Samba winbind client library
 python-samba - Python bindings for Samba
 registry-tools - tools for viewing and manipulating the Windows registry
 samba  - SMB/CIFS file, print, and login server for Unix
 samba-common - common files used by both the Samba server and client
 samba-common-bin - Samba common files used by both the server and the client
 samba-dbg  - Samba debugging symbols
 samba-dev  - tools for extending Samba
 samba-doc  - Samba documentation
 samba-dsdb-modules - Samba Directory Services Database
 samba-libs - Samba core libraries
 samba-testsuite - test suite from Samba
 samba-vfs-modules - Samba Virtual FileSystem plugins
 smbclient  - command-line SMB/CIFS clients for Unix
 winbind- service to resolve user and group information from Windows NT ser
Closes: 793866
Changes:
 samba (2:4.2.1+dfsg-1) experimental; urgency=medium
 .
   [ Jelmer Vernooij ]
   * New upstream release.
+ Drop patch do-not-install-smbclient4-and-nmbclient4: applied upstream.
+ Drop patch
  bug_598313_upstream_7499-nss_wins-dont-clobber-daemons-logs.patch:
  present upstream.
+ Refresh patch 26_heimdal_compat.26_heimdal_compat.
+ Add build-dependency on libarchive-dev.
   * Drop samba_bug_11077_torturetest.patch: applied upstream.
   * Drop dependency on ctdb - now bundled with Samba.
   * Use bundled Heimdal as the system Heimdal doesn't contain the
 changes required for Samba.
   * Add patch heimdal-rfc3454.txt: patch in truncated rfc3454.txt for
 building bundled heimdal.
   * Drop patches 25_heimdal_api_changes and 26_heimdal_compat.
   * Disable 

Bug#787892: marked as done (realmd: Suffers from bug #735255 - missing /var/lib/samba/private)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 23:38:04 +
with message-id 
and subject line Bug#793866: fixed in samba 2:4.2.1+dfsg-1
has caused the Debian Bug report #793866,
regarding realmd: Suffers from bug #735255 - missing /var/lib/samba/private
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.)


-- 
793866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: realmd
Version: 0.15.1-1+b2
Severity: important

Dear Maintainer,

Hi, fresh install of jessie.  Installed realmd and get:

root@debian8:~# realm join --verbose --user=someone the.domain
 * Resolving: _ldap._tcp.the.domain
 * Performing LDAP DSE lookup on: 1.1.1.1
 * Performing LDAP DSE lookup on: 1.1.1.2
 * Successfully discovered: the.domain
Password for someone:
 * Unconditionally checking packages
 * Resolving required packages
 * Installing necessary packages: sssd-tools, libpam-sss, libnss-sss, sssd, 
samba-common-bin
 * LANG=C LOGNAME=root /usr/bin/net -s /var/cache/realmd/realmd-smb-conf.Z2P0ZX 
-U someone ads join the.domain
Enter someone's password:Failed to open /var/lib/samba/private/secrets.tdb

Failed to join domain: Unable to open secrets database
 ! Joining the domain the.domain failed
realm: Couldn't join realm: Joining the domain the.domain failed

This is resolved by mkdir'ing the above before doing the above.

This bug also leaves sssd in a strange state, whereby I had to leave the domain
and rejoin before things worked.

Versions of packages that realmd installed:

ii  libnss-sss:amd64  1.11.7-3
ii  libpam-sss:amd64  1.11.7-3
ii  samba-common-bin  2:4.1.17+dfsg-2
ii  sssd  1.11.7-3
ii  sssd-ad   1.11.7-3
ii  sssd-ad-common1.11.7-3
ii  sssd-common   1.11.7-3
ii  sssd-ipa  1.11.7-3
ii  sssd-krb5 1.11.7-3
ii  sssd-krb5-common  1.11.7-3
ii  sssd-ldap 1.11.7-3
ii  sssd-proxy1.11.7-3
ii  sssd-tools1.11.7-3


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages realmd depends on:
ii  libc6   2.19-18
ii  libcomerr2  1.42.12-1.1
ii  libglib2.0-02.42.1-1
ii  libk5crypto31.12.1+dfsg-19
ii  libkrb5-3   1.12.1+dfsg-19
ii  libldap-2.4-2   2.4.40+dfsg-1
ii  libpackagekit-glib2-18  1.0.1-2
ii  libpolkit-gobject-1-0   0.105-8
ii  libsqlite3-03.8.7.1-1+deb8u1
ii  libsystemd0 215-17

realmd recommends no packages.

realmd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.2.1+dfsg-1

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Dec 2014 15:34:36 +
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev samba-doc 
python-samba samba-dsdb-modules samba-vfs-modules libpam-smbpass libsmbclient 
libsmbclient-dev winbind libpam-winbind libnss-winbind samba-dbg libwbclient0 
libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.2.1+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Jelmer Vernooij 

Processed: found 796052 in 4:4.14.2-1

[Debian Bug Tracking System]

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

> found 796052 4:4.14.2-1
Bug #796052 [src:gwenview] gwenview: FTBFS: No rule to make target 
'/usr/lib/libsoprano.so'
Ignoring request to alter found versions of bug #796052 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#789400: marked as done (gucharmap: needs update for unicode-data 8.0-1 and Built-Using field)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:27:37 +
with message-id 
and subject line Bug#789400: fixed in gucharmap 1:3.17.90-1
has caused the Debian Bug report #789400,
regarding gucharmap: needs update for unicode-data 8.0-1 and Built-Using field
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.)


-- 
789400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gucharmap
Severity: serious
Usertags: static built-using

According to the Build-Depends and build logs, gucharmap takes files
from unicode-data, converts them to C headers using a Perl script and
statically compiles them into the library.

A new version of unicode-data was just uploaded (8.0-1), so gucharmap
needs an update from upstream to build with the new version.

Since files from unicode-data therefore form part of the source of
gucharmap, unicode-data should be present in the Built-Using field,
which is documented in this section of policy:

https://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using

The package currently FTBFS due to this issue:

unicode-versions.h:182:21: error: 'GUCHARMAP_UNICODE_VERSION_8_0' undeclared 
here (not in a function)
   { 0x08B3, 0x08B4, GUCHARMAP_UNICODE_VERSION_8_0 },
 ^

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: gucharmap
Source-Version: 1:3.17.90-1

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated gucharmap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Sep 2015 21:42:35 +0200
Source: gucharmap
Binary: gucharmap libgucharmap-2-90-dev libgucharmap-2-90-7 
gir1.2-gucharmap-2.90
Architecture: source amd64
Version: 1:3.17.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-gucharmap-2.90 - GObject introspection data for the Unicode browser 
widget library
 gucharmap  - Unicode character picker and font browser
 libgucharmap-2-90-7 - Unicode browser widget library (shared library)
 libgucharmap-2-90-dev - Unicode browser widget library (development headers)
Closes: 789400
Changes:
 gucharmap (1:3.17.90-1) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * Generate Built-Using control field for libgucharmap package
 from unicode-data version used during build. (See #789400)
   * New upstream release including unicode 8.0 support. (Closes: #789400)
   * Tighten unicode-data versions to also say << 8.1 in build-dependency
 to match what is supported upstream in GucharmapUnicodeVersion enum
 of gucharmap/gucharmap-unicode-info.h
 .
   [ Josselin Mouette ]
   * Remove Debian menu entry.
Checksums-Sha1:
 12c12305a4f141e05e9607ded7a0aa0240a05603 2653 gucharmap_3.17.90-1.dsc
 a28c8105a46cb79f8009640d27f5efb935053393 2026612 gucharmap_3.17.90.orig.tar.xz
 19627e88da6d5e82971f871ccfc2184bd6b3138c 11256 
gucharmap_3.17.90-1.debian.tar.xz
 285580ab61ca921e61a298adc26f2d89ab43969b 252688 
gir1.2-gucharmap-2.90_3.17.90-1_amd64.deb
 8365508ea5e37aa16e1f1e8435842419e7105b93 682198 gucharmap_3.17.90-1_amd64.deb
 b07658b9dd2fb14c650a671fe7f7034f09dded71 1227902 
libgucharmap-2-90-7_3.17.90-1_amd64.deb
 c2092e131b125f3497fd8dd299ab741cd669a503 278076 
libgucharmap-2-90-dev_3.17.90-1_amd64.deb
Checksums-Sha256:
 a1a5ff786fda040523356e5437560ac41ecc9e3c8f13f03d4cbf84f47cd21b2e 2653 
gucharmap_3.17.90-1.dsc
 fb921b5fb533253f62b5848ffbbd6ec75c6cc6cb8c4b4d7d3504c0364d17accc 2026612 
gucharmap_3.17.90.orig.tar.xz
 d969242046fce0a86e325f3496c25e78a399e9ef493dfe6741c132d769dad93d 11256 
gucharmap_3.17.90-1.debian.tar.xz
 bb1e0a5c75d0f14d06af6243f861c06e339b3520c251c07c88eddadadbb6be02 252688 

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 798115 src:wmail
Bug #798115 [wmail] wmail: FTBFS with libdockapp v0.7.0
Bug reassigned from package 'wmail' to 'src:wmail'.
No longer marked as found in versions wmail/2.0-3.
Ignoring request to alter fixed versions of bug #798115 to the same values 
previously set
> merge 798112 798115
Bug #798112 [src:wmail] wmail ftbfs with the new libdockapp
Bug #798112 [src:wmail] wmail ftbfs with the new libdockapp
Added tag(s) patch.
Bug #798115 [src:wmail] wmail: FTBFS with libdockapp v0.7.0
Marked as found in versions wmail/2.0-3.
Added tag(s) stretch and sid.
Merged 798112 798115
> reassign 798113 wmdate
Bug #798113 [src:wmail] wmdate ftbfs with the new libdockapp
Bug reassigned from package 'src:wmail' to 'wmdate'.
No longer marked as found in versions wmail/0.7-4.
Ignoring request to alter fixed versions of bug #798113 to the same values 
previously set
> merge 798113 798118
Bug #798113 [wmdate] wmdate ftbfs with the new libdockapp
Bug #798118 [wmdate] wmdate: FTBFS with libdockapp v0.7.0
Added tag(s) sid and stretch.
Bug #798113 [wmdate] wmdate ftbfs with the new libdockapp
Marked as found in versions wmdate/0.7-4.
Added tag(s) patch.
Merged 798113 798118
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
798112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798112
798113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798113
798115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798115
798118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#795767: marked as done (netty-tcnative: FTBFS: missing org.apache.felix:maven-bundle-plugin)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:33:32 +
with message-id 
and subject line Bug#795767: fixed in netty-tcnative 1.1.33.Fork6-1
has caused the Debian Bug report #795767,
regarding netty-tcnative: FTBFS: missing org.apache.felix:maven-bundle-plugin
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.)


-- 
795767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netty-tcnative
Version: 1.1.33.Fork4-1
Severity: serious
Justification: fails to build from source

Builds of netty-tcnative in minimal environments geared for covering
only its architecture-dependent binary package have been failing:

  [ERROR] BUILD ERROR
  [INFO] 

  [INFO] The plugin 'org.apache.felix:maven-bundle-plugin' does not exist or no 
valid version could be found

Could you please take a look?  I presume you'll want to move
libmaven-bundle-plugin-java from Build-Depends-Indep to Build-Depends;
I'm not sure about libmaven-antrun-plugin-java offhand.

Thanks!
--- End Message ---
--- Begin Message ---
Source: netty-tcnative
Source-Version: 1.1.33.Fork6-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated netty-tcnative package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Sep 2015 22:45:45 +0200
Source: netty-tcnative
Binary: libnetty-tcnative-java libnetty-tcnative-jni
Architecture: source all amd64
Version: 1.1.33.Fork6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libnetty-tcnative-java - Tomcat native fork for Netty
 libnetty-tcnative-jni - Tomcat native fork for Netty (JNI library)
Closes: 795767
Changes:
 netty-tcnative (1.1.33.Fork6-1) unstable; urgency=medium
 .
   * New upstream release
   * Fixed the failure when building only the binary package (Closes: #795767)
Checksums-Sha1:
 9a02ebdb91f7d6376d48b61f6b0f954522fd7204 2282 netty-tcnative_1.1.33.Fork6-1.dsc
 c310da9399a6593a3dc13500ea398fd8c71b7f37 171582 
netty-tcnative_1.1.33.Fork6.orig.tar.gz
 f05dc1470ea9a3e7a9ab9748ab2033510942a66f 5280 
netty-tcnative_1.1.33.Fork6-1.debian.tar.xz
 28f85513c4ca3993ed4bec57b1a98c5eff875975 64194 
libnetty-tcnative-java_1.1.33.Fork6-1_all.deb
 2a294a53c75bb556bbdfd22454f79f3728873c70 50900 
libnetty-tcnative-jni_1.1.33.Fork6-1_amd64.deb
Checksums-Sha256:
 f8191b04421160c8f22d323670cf3bb7338963de690a31535683c0eb4477f56f 2282 
netty-tcnative_1.1.33.Fork6-1.dsc
 3d895ae09089f73ad255c916bf5fc51268c6fc8d541f736cb6b91882015a5c25 171582 
netty-tcnative_1.1.33.Fork6.orig.tar.gz
 7feab5ea67a5ab153d235f5e12487726feeceee060d5e022b49b1c8499d9bfd1 5280 
netty-tcnative_1.1.33.Fork6-1.debian.tar.xz
 1ec220231d4fdba0584f4135f76fec96b738a05056e6ea6409dd2799f5b128ee 64194 
libnetty-tcnative-java_1.1.33.Fork6-1_all.deb
 3ba03055ef4bcfdf6c665624be4ff981e42b6ca6842dfec98c938e142b1d4826 50900 
libnetty-tcnative-jni_1.1.33.Fork6-1_amd64.deb
Files:
 fe2a7ce9d9225b1147b0be29045d68f9 2282 java optional 
netty-tcnative_1.1.33.Fork6-1.dsc
 16ee9d0a146027f8002d7a10fd8c76fe 171582 java optional 
netty-tcnative_1.1.33.Fork6.orig.tar.gz
 48c239e8ffd8aad2fd855457e79570fc 5280 java optional 
netty-tcnative_1.1.33.Fork6-1.debian.tar.xz
 1828e1ca8b00a8855445df5d99b5113e 64194 java optional 
libnetty-tcnative-java_1.1.33.Fork6-1_all.deb
 b3a2cec647876982d44d5cc343262009 50900 java optional 
libnetty-tcnative-jni_1.1.33.Fork6-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJV7KrTAAoJEPUTxBnkudCsqSQP/iZkrl6uLiKavMbNfZbwGS/A
CGceklGHOUJNjdCPe/LJ18Y68a/PXaIEQSduy5ASKEwJXoKm6WLQli3sFXmpTzWg
NMuF9OEgpFLWwIcG2+5k9JQcL0OwI5p01FGMEmRMOts0NvDC2lhn/fC9sa8+l8t9
UtceXmj7kvl9SE7hMPx6AMUXmu4F/TaVkJ0VB2RlyxCWe87XHRFL7NHN/u6OO7Bw

Bug#797224: marked as done (lyx ftbfs with boost1.58)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:33:08 +
with message-id 
and subject line Bug#797224: fixed in lyx 2.1.4-1
has caused the Debian Bug report #797224,
regarding lyx ftbfs with boost1.58
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.)


-- 
797224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lyx
Version: 2.1.3-1
Severity: serious
Tags: sid stretch patch

see
https://launchpad.net/ubuntu/+source/lyx/2.1.3-1build1/+build/7845469

the new upstream 2.1.4 builds fine. See
https://launchpad.net/ubuntu/+source/lyx/2.1.4-0ubuntu1
--- End Message ---
--- Begin Message ---
Source: lyx
Source-Version: 2.1.4-1

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

Debian distribution maintenance software
pp.
Per Olofsson  (supplier of updated lyx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Sep 2015 21:25:59 +0200
Source: lyx
Binary: lyx lyx-common lyx-dbg fonts-lyx ttf-lyx
Architecture: source all amd64
Version: 2.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LyX Maintainers 
Changed-By: Per Olofsson 
Description:
 fonts-lyx  - TrueType versions of some TeX fonts used by LyX
 lyx- document processor
 lyx-common - architecture-independent files for LyX
 lyx-dbg- debugging symbols for LyX
 ttf-lyx- transitional package
Closes: 797224
Changes:
 lyx (2.1.4-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes FTBFS with boost 1.58. Closes: #797224.
 - Drop patch add-desktop-keywords; applied upstream.
Checksums-Sha1:
 62bdc71b7c088077920602a0127d137587c2f076 2353 lyx_2.1.4-1.dsc
 956662191437685789a2ffc2eec3048a21d3e37b 10928716 lyx_2.1.4.orig.tar.xz
 ba5d0ec990d16d7990e6ea5584f579ab6866658f 28008 lyx_2.1.4-1.debian.tar.xz
 49b5a9047f48b7edda98e950807fcb9cb91acc78 201524 fonts-lyx_2.1.4-1_all.deb
 8e0bbf7ebfa8834fb7be5b5440cd7fdc6261108f 6253352 lyx-common_2.1.4-1_all.deb
 d70cd57ac6ccefef82a89435277cc18ad1c6fa03 57100990 lyx-dbg_2.1.4-1_amd64.deb
 0531f71ec37aa0e80db0039c323b548213d38df1 3674784 lyx_2.1.4-1_amd64.deb
 173e4e5ce32f0cd9710c1950581d462420de5506 48908 ttf-lyx_2.1.4-1_all.deb
Checksums-Sha256:
 f070f6761393a7dd900267f9af22425871f6be1f62864700d560c6b7f555903f 2353 
lyx_2.1.4-1.dsc
 d13548cf183f2fc241df8121420933702491a7460c78a0ef6dba0e9e438ef32a 10928716 
lyx_2.1.4.orig.tar.xz
 e9cf03f638cce9348d42a0d844f9a35232b6aa70a76b68841cdeba0b98144307 28008 
lyx_2.1.4-1.debian.tar.xz
 9b0437695cf1a168c7fb3a46178997a2b013f96185668ef0cb5e5273f41e81c2 201524 
fonts-lyx_2.1.4-1_all.deb
 bf2ac8ff1c3d4bfda63e2d28fa2641a31b2799818ed7cfcf6ca176dd877bb178 6253352 
lyx-common_2.1.4-1_all.deb
 36d96f6face031e85ed3c890b5c914a8ee9dc5213df6ccd9eab6e1fa6e53a6e9 57100990 
lyx-dbg_2.1.4-1_amd64.deb
 8450bad379ea594515f9c473fd5d16a38728b4ab8bf895bdc63e01ff6a77c372 3674784 
lyx_2.1.4-1_amd64.deb
 9b93800b8d930fc69cafe6479fe25b805dab7da130e2d88161870140d7a3e1f5 48908 
ttf-lyx_2.1.4-1_all.deb
Files:
 d1e32f6901e05e2cde733bced2b1dc62 2353 editors optional lyx_2.1.4-1.dsc
 33f6906e5447a193b27c7231986e9f46 10928716 editors optional 
lyx_2.1.4.orig.tar.xz
 26abff7b97c2a9ccd0a679b86fae1493 28008 editors optional 
lyx_2.1.4-1.debian.tar.xz
 9f8090301526a08d6b703a4baba0f878 201524 fonts optional 
fonts-lyx_2.1.4-1_all.deb
 3f08e3c006c6db5df57008ee80361f60 6253352 editors optional 
lyx-common_2.1.4-1_all.deb
 e68b69df187ad5f4ebd41f00ec814672 57100990 debug extra lyx-dbg_2.1.4-1_amd64.deb
 9c767e81cc5e7f91b7aed0ac7b9046df 3674784 editors optional lyx_2.1.4-1_amd64.deb
 2fdc0fee9204ccd9b6f39a2c604bb99c 48908 oldlibs extra ttf-lyx_2.1.4-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV7JiTAAoJEMQ1cPgMwpXmwNwQAMBt9lI2Spm1d2K0kfWRWDvg
eZWPzLeuSejVVPmSBYfhoU19mlC4nxAYsCB9aDKzTfHRRcA5vJpUL7B1PBKh5fic
8RFO2RzzPwBStJHC5IVcuOTBhwG/W4Ko4az/zXibAmVTk99V5Rn4tgzvanTofbIn

Bug#798190: marked as done (reads nonexistant dir, segfaults Kodi on startup)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:32:17 +
with message-id 
and subject line Bug#798190: fixed in libcec 3.0.1+dfsg2-5
has caused the Debian Bug report #798190,
regarding reads nonexistant dir, segfaults Kodi on startup
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.)


-- 
798190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcec3
Version: 3.0.1+dfsg2-4
Severity: grave

Hi,

Recently, Kodi has started segfaulting on startup, pointing to libcec3.
A backtrace reads:

#0  0x7fffecf55789 in __readdir (dirp=dirp@entry=0x0) at 
../sysdeps/posix/readdir.c:44
#1  0x7fffc81d8b74 in PLATFORM::CDRMEdidParser::GetPhysicalAddress 
(this=this@entry=0x7fffc29e8550)
at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/platform/drm/drm-edid.cpp:54
#2  0x7fffc81e4c0e in CEC::CUSBCECAdapterCommunication::GetPhysicalAddress 
(this=0x7fffb4000f50)
at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/adapter/Pulse-Eight/USBCECAdapterCommunication.cpp:697
#3  0x7fffc81baaec in CEC::CCECClient::AutodetectPhysicalAddress 
(this=0x1a7cab0)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:1224
#4  0x7fffc81b884c in CEC::CCECClient::SetPhysicalAddress (this=0x1a7cab0, 
configuration=...)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:236
#5  0x7fffc81bcdcb in CEC::CCECClient::OnRegister (this=0x1a7cab0) at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:138
#6  0x7fffc81cd4d2 in CEC::CCECProcessor::RegisterClient (this=0x1a76840, 
client=std::shared_ptr (count 4, weak 0) 0x1a7cab0)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECProcessor.cpp:899
#7  0x7fffc81d3e7a in CEC::CLibCEC::Open (this=0x1a78d10, 
strPort=, iTimeoutMs=)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/LibCEC.cpp:91
#8  0x010cdd39 in PERIPHERALS::CPeripheralCecAdapter::OpenConnection() 
()
#9  0x010d0434 in PERIPHERALS::CPeripheralCecAdapter::Process() ()
#10 0x0113f56f in CThread::Action() ()
#11 0x0113f832 in CThread::staticThread(void*) ()
#12 0x755ad0a4 in start_thread (arg=0x7fffc29e9700) at 
pthread_create.c:309
#13 0x7fffecf8807d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

It would seem libcec3 unconditionally assumes /sys/class/drm exists
(it does not on my system using the proprietary NVIDIA driver, since
that driver doesn't use drm), and then segfaults when it doesn't.

Could you please add a check for the NULL value?
--- End Message ---
--- Begin Message ---
Source: libcec
Source-Version: 3.0.1+dfsg2-5

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated libcec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Sep 2015 19:11:37 +0200
Source: libcec
Binary: libcec-dev libcec3 cec-utils python-libcec
Architecture: source
Version: 3.0.1+dfsg2-5
Distribution: unstable
Urgency: medium
Maintainer: Sjoerd Simons 
Changed-By: Balint Reczey 
Description:
 cec-utils  - USB CEC Adaptor communication Library (utility programs)
 libcec-dev - USB CEC Adaptor communication Library (development files)
 libcec3- USB CEC Adaptor communication Library (shared library)
 python-libcec - Python bindings for USB CEC Adaptor
Closes: 798190
Changes:
 libcec (3.0.1+dfsg2-5) unstable; urgency=medium
 .
   * Fix crash on systems lacking /sys/class/drm (Closes: #798190)
Checksums-Sha1:
 96df242753ed03711f6a610ee124ccf58d7e2335 2271 libcec_3.0.1+dfsg2-5.dsc
 6a19f43fa80073751d73e70c286bda7818c1a9ae 15780 
libcec_3.0.1+dfsg2-5.debian.tar.xz
Checksums-Sha256:
 1e86cc829e88ed9cd6b4fd4215d223c5c574dae660700f8e56c1b2cddc3ae6ea 2271 
libcec_3.0.1+dfsg2-5.dsc
 97698a4df2a31c669a4208730a268b145c7a0a980d700c9ea37e5f1981a46f05 15780 
libcec_3.0.1+dfsg2-5.debian.tar.xz

Bug#797235: marked as done (ssh-agent-filter ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:36:27 +
with message-id 
and subject line Bug#797235: fixed in ssh-agent-filter 0.4.1-1
has caused the Debian Bug report #797235,
regarding ssh-agent-filter ftbfs in unstable
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.)


-- 
797235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ssh-agent-filter
Version: 0.4-2
Severity: serious
Tags: sid stretch

g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++11
-D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64  -c -o ssh-agent-filter.o
ssh-agent-filter.C
ssh-agent-filter.C: In function 'void setup_filters()':
ssh-agent-filter.C:276:46: error: call of overloaded 'move(rfc4251string&)' is
ambiguous
   if (allow) allowed_pubkeys.emplace(move(key));
  ^
In file included from /usr/include/c++/5/bits/stl_pair.h:59:0,
 from /usr/include/c++/5/bits/stl_algobase.h:64,
 from /usr/include/c++/5/bits/char_traits.h:39,
 from /usr/include/c++/5/string:40,
 from /usr/include/boost/program_options/errors.hpp:12,
 from 
/usr/include/boost/program_options/options_description.hpp:12,
 from /usr/include/boost/program_options.hpp:15,
 from ssh-agent-filter.C:22:
/usr/include/c++/5/bits/move.h:101:5: note: candidate: constexpr typename
std::remove_reference<  >::type&& std::move(_Tp&&) [with
_Tp = rfc4251string&; typename std::remove_reference< 
>::type = rfc4251string]
 move(_Tp&& __t) noexcept
 ^
In file included from /usr/include/boost/function/function_template.hpp:32:0,
 from /usr/include/boost/function/detail/maybe_include.hpp:18,
 from /usr/include/boost/function/function1.hpp:11,
 from /usr/include/boost/program_options/value_semantic.hpp:13,
 from 
/usr/include/boost/program_options/options_description.hpp:13,
 from /usr/include/boost/program_options.hpp:15,
 from ssh-agent-filter.C:22:
/usr/include/boost/move/utility_core.hpp:191:77: note: candidate: typename
boost::move_detail::remove_reference::type&& boost::move(T&&) [with T =
rfc4251string&; typename boost::move_detail::remove_reference::type =
rfc4251string]
  inline typename ::boost::move_detail::remove_reference::type &&
move(T&& t) BOOST_NOEXCEPT
 ^
ssh-agent-filter.C:297:51: error: call of overloaded 'move(rfc4251string&)' is
ambiguous
if (confirm) confirmed_pubkeys.emplace(move(key), move(comm));
   ^
In file included from /usr/include/c++/5/bits/stl_pair.h:59:0,
 from /usr/include/c++/5/bits/stl_algobase.h:64,
 from /usr/include/c++/5/bits/char_traits.h:39,
 from /usr/include/c++/5/string:40,
 from /usr/include/boost/program_options/errors.hpp:12,
 from 
/usr/include/boost/program_options/options_description.hpp:12,
 from /usr/include/boost/program_options.hpp:15,
 from ssh-agent-filter.C:22:
/usr/include/c++/5/bits/move.h:101:5: note: candidate: constexpr typename
std::remove_reference<  >::type&& std::move(_Tp&&) [with
_Tp = rfc4251string&; typename std::remove_reference< 
>::type = rfc4251string]
 move(_Tp&& __t) noexcept
 ^
In file included from /usr/include/boost/function/function_template.hpp:32:0,
 from /usr/include/boost/function/detail/maybe_include.hpp:18,
 from /usr/include/boost/function/function1.hpp:11,
 from /usr/include/boost/program_options/value_semantic.hpp:13,
 from 
/usr/include/boost/program_options/options_description.hpp:13,
 from /usr/include/boost/program_options.hpp:15,
 from ssh-agent-filter.C:22:
/usr/include/boost/move/utility_core.hpp:191:77: note: candidate: typename
boost::move_detail::remove_reference::type&& boost::move(T&&) [with T =
rfc4251string&; typename boost::move_detail::remove_reference::type =
rfc4251string]
  inline typename ::boost::move_detail::remove_reference::type &&
move(T&& t) BOOST_NOEXCEPT
 ^
ssh-agent-filter.C: In function 'rfc4251string handle_request(const
rfc4251string&)':

Processed (with 3 errors): your mail

[Debian Bug Tracking System]

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

> merge 798112 798115
Bug #798112 [src:wmail] wmail ftbfs with the new libdockapp
Unable to merge bugs because:
package of #798115 is 'wmail' not 'src:wmail'
Failed to merge 798112: Did not alter merged bugs.

> merge 798113 798118
Bug #798113 [src:wmail] wmdate ftbfs with the new libdockapp
Unable to merge bugs because:
package of #798118 is 'wmdate' not 'src:wmail'
Failed to merge 798113: Did not alter merged bugs.

> reassign 798113 wmdate 0.7-4
Failed to clear fixed versions and reopen on 798113: failed to get lock on 
/org/bugs.debian.org/spool/lock/798113 -- Unable to lock 
/org/bugs.debian.org/spool/lock/798113 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/798113 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
798112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798112
798113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798113
798115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798115
798118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#782614: marked as done (Python 2.7.9 poplib._MAXLINE problem)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:18:51 +
with message-id 
and subject line Bug#782614: fixed in getmail4 4.46.0-1+deb8u1
has caused the Debian Bug report #782614,
regarding Python 2.7.9 poplib._MAXLINE problem
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.)


-- 
782614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: getmail4
Version: 4.46.0-1
Severity: important

Dear Maintainer,

apparently since I upgraded to Jessie a few weeks ago, some
mails in my POP3 mailbox prevent fetching the mails. It
produces the following errors:

getmail version 4.46.0
Copyright (C) 1998-2012 Charles Cazabon.  Licensed under the GNU GPL version 2.
SimplePOP3SSLRetriever:a...@..aa:995:
Retrieval error: server for 
SimplePOP3SSLRetriever:a...@..aa:995 is broken; offered message 
b56b54610e7b but failed to provide it.  Please notify the administrator of 
the server.  Skipping message...
  0 messages (0 bytes) retrieved, 0 skipped


When I delete the first mail from the mailbox on the server,
it usually can fetch the rest, so the first mail seems to be
the offending one. Other POP3 retrievers don't have this
problem, so it must be a problem in getmail4.

The config hasn't changed and looks like this:

[retriever]
type = SimplePOP3SSLRetriever
server = ..aa
username = 
password = b

[destination]
type = MDA_external
path = /usr/bin/procmail


I can provide an example of a mail that prevents fetching,
it always seems to be a mail with HTML or mixed content,
produced unter Windows.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages getmail4 depends on:
ii  python  2.7.9-1

getmail4 recommends no packages.

getmail4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: getmail4
Source-Version: 4.46.0-1+deb8u1

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

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated getmail4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 03 Sep 2015 21:00:36 +0900
Source: getmail4
Binary: getmail4
Architecture: source all
Version: 4.46.0-1+deb8u1
Distribution: jessie
Urgency: low
Maintainer: Osamu Aoki 
Changed-By: Osamu Aoki 
Description:
 getmail4   - mail retriever with support for POP3, IMAP4 and SDPS
Closes: 782614
Changes:
 getmail4 (4.46.0-1+deb8u1) jessie; urgency=low
 .
   * The Python 2.7.9 introduced a regression while addressing
 CVE-2013-1752 with poplib._MAXLINE=2048 which causes problem
 for some HTML mails etc..  This fix sets poplib._MAXLINE=1MB
 as in the getmail 4.48.0.  Closes: #782614
Checksums-Sha1:
 8bb72677cdc1b9690f6d54fd24b6ee0f0b97bce9 1883 getmail4_4.46.0-1+deb8u1.dsc
 68685fc54f0bcdaa9e626099504987c1f3bac865 7680 
getmail4_4.46.0-1+deb8u1.debian.tar.xz
 96448e3550fe3851b333ae824b6e99da4dbff9a9 170248 
getmail4_4.46.0-1+deb8u1_all.deb
Checksums-Sha256:
 d876460ce19a5ffe6ac8afc91259693ca0bb2ad346305a6b5caebdd50a7f17a8 1883 
getmail4_4.46.0-1+deb8u1.dsc
 f2acbc71f140110f84d52fe890b12bf66b97a1750b6fa6f0529edcb9bde70eff 7680 
getmail4_4.46.0-1+deb8u1.debian.tar.xz
 8004d5d6e248d93755306056963bac1ad790459825899a63c5f0dca24acd65b3 170248 
getmail4_4.46.0-1+deb8u1_all.deb
Files:
 553e8591e799c2872ec6056410c879ff 1883 mail optional 
getmail4_4.46.0-1+deb8u1.dsc
 d112a31e6cd454c28f392b07c3ec340b 7680 mail optional 
getmail4_4.46.0-1+deb8u1.debian.tar.xz
 066d23cd2546b70a32a192edede5b9ee 170248 mail optional 
getmail4_4.46.0-1+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#793811: marked as done (qemu: CVE-2015-5154: ide: atapi: heap overflow during I/O buffer memory access)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:19:24 +
with message-id 
and subject line Bug#793811: fixed in qemu 1:2.1+dfsg-12+deb8u2
has caused the Debian Bug report #793811,
regarding qemu: CVE-2015-5154: ide: atapi: heap overflow during I/O buffer 
memory access
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.)


-- 
793811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1.5.0+dfsg-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

CVE-2015-5154[0]:
QEMU heap overflow flaw while processing certain ATAPI commands

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5154
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1243563

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.1+dfsg-12+deb8u2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated qemu 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: Sat, 29 Aug 2015 16:12:31 +0200
Source: qemu
Binary: qemu qemu-system qemu-system-common qemu-system-misc qemu-system-arm 
qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user 
qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.1+dfsg-12+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Debian QEMU Team 
Changed-By: Salvatore Bonaccorso 
Closes: 793811 794610 795087 795461 796465
Description: 
 qemu   - fast processor emulator
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscelaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Changes:
 qemu (1:2.1+dfsg-12+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add 0001-i8254-fix-out-of-bounds-memory-access-in-pit_ioport_.patch patch.
 CVE-2015-3214: i8254: out-of-bounds memory access in pit_ioport_read
 function. (Closes: #795461)
   * Add patches to address heap overflow when processing ATAPI commands.
 CVE-2015-5154: heap overflow during I/O buffer memory access.
 (Closes: #793811)
   * Add CVE-2015-5225.patch patch.
 CVE-2015-5225: vnc: heap memory corruption in
 vnc_refresh_server_surface. (Closes: #796465)
   * Add 0001-virtio-serial-fix-ANY_LAYOUT.patch patch.
 CVE-2015-5745: buffer overflow in virtio-serial. (Closes: #795087)
   * Add patches for CVE-2015-5165.
 CVE-2015-5165: rtl8139 uninitialized heap memory information leakage to
 guest. (Closes: #794610)
Checksums-Sha1: 
 ac15c1363023106bbf9f73d7f9a7d5a8b212b78d 5520 qemu_2.1+dfsg-12+deb8u2.dsc
 a11f28854b972f71bb5e5eebe0da55bc82f23cfd 112728 
qemu_2.1+dfsg-12+deb8u2.debian.tar.xz
Checksums-Sha256: 
 254db070d83650461ae37dc470346304209d0065fea6852479378344bac92e7f 5520 
qemu_2.1+dfsg-12+deb8u2.dsc
 96f8859ab1e020b92e48000a90d06ee1e7d8f044acfad715250100b417bc 112728 

Bug#796465: marked as done (qemu: CVE-2015-5225: ui: vnc: heap memory corruption in vnc_refresh_server_surface)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:19:25 +
with message-id 
and subject line Bug#796465: fixed in qemu 1:2.1+dfsg-12+deb8u2
has caused the Debian Bug report #796465,
regarding qemu: CVE-2015-5225: ui: vnc: heap memory corruption in 
vnc_refresh_server_surface
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.)


-- 
796465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.1+dfsg-1
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for qemu.

CVE-2015-5225[0]:
ui: vnc: heap memory corruption in vnc_refresh_server_surface

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5225
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1255896

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.1+dfsg-12+deb8u2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated qemu 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: Sat, 29 Aug 2015 16:12:31 +0200
Source: qemu
Binary: qemu qemu-system qemu-system-common qemu-system-misc qemu-system-arm 
qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user 
qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.1+dfsg-12+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Debian QEMU Team 
Changed-By: Salvatore Bonaccorso 
Closes: 793811 794610 795087 795461 796465
Description: 
 qemu   - fast processor emulator
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscelaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Changes:
 qemu (1:2.1+dfsg-12+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add 0001-i8254-fix-out-of-bounds-memory-access-in-pit_ioport_.patch patch.
 CVE-2015-3214: i8254: out-of-bounds memory access in pit_ioport_read
 function. (Closes: #795461)
   * Add patches to address heap overflow when processing ATAPI commands.
 CVE-2015-5154: heap overflow during I/O buffer memory access.
 (Closes: #793811)
   * Add CVE-2015-5225.patch patch.
 CVE-2015-5225: vnc: heap memory corruption in
 vnc_refresh_server_surface. (Closes: #796465)
   * Add 0001-virtio-serial-fix-ANY_LAYOUT.patch patch.
 CVE-2015-5745: buffer overflow in virtio-serial. (Closes: #795087)
   * Add patches for CVE-2015-5165.
 CVE-2015-5165: rtl8139 uninitialized heap memory information leakage to
 guest. (Closes: #794610)
Checksums-Sha1: 
 ac15c1363023106bbf9f73d7f9a7d5a8b212b78d 5520 qemu_2.1+dfsg-12+deb8u2.dsc
 a11f28854b972f71bb5e5eebe0da55bc82f23cfd 112728 
qemu_2.1+dfsg-12+deb8u2.debian.tar.xz
Checksums-Sha256: 
 254db070d83650461ae37dc470346304209d0065fea6852479378344bac92e7f 5520 
qemu_2.1+dfsg-12+deb8u2.dsc
 96f8859ab1e020b92e48000a90d06ee1e7d8f044acfad715250100b417bc 112728 

Bug#795910: marked as done (python3-yaql: yaql not working: ImportError: No module named 'context')

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 22:19:24 +
with message-id 
and subject line Bug#795910: fixed in python-yaql 0.2.3-2+deb8u1
has caused the Debian Bug report #795910,
regarding python3-yaql: yaql not working: ImportError: No module named 'context'
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.)


-- 
795910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-yaql
Version: 0.2.3-2
Severity: grave
Tags: patch
Justification: renders package unusable

yaql (python 3 package) fails to launch or import because uses python 2 syntax.

2to3 seams to fix the issue.


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

Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-yaql depends on:
ii  dpkg 1.18.2
ii  python3-ply  3.4-5
ii  python3.43.4.3-7
pn  python3:any  

python3-yaql recommends no packages.

python3-yaql suggests no packages.
--- yaql/__init__.py	(original)
+++ yaql/__init__.py	(refactored)
@@ -12,8 +12,8 @@
 #License for the specific language governing permissions and limitations
 #under the License.
 
-import parser
-import context
+from . import parser
+from . import context
 from yaql.functions import builtin, extended
 
 __versioninfo__ = (0, 2, 3)
--- yaql/context.py	(original)
+++ yaql/context.py	(refactored)
@@ -14,7 +14,7 @@
 
 from functools import wraps
 import inspect
-from exceptions import NoArgumentFound
+from .exceptions import NoArgumentFound
 
 
 class Context():
--- yaql/exceptions.py	(original)
+++ yaql/exceptions.py	(refactored)
@@ -20,9 +20,9 @@
 
 class NoFunctionRegisteredException(YaqlException):
 def __init__(self, func_name, arg_num=None):
-self.func_name = func_name
+self.__name__ = func_name
 self.arg_num = arg_num
-msg = "No function called '{0}' is registered".format(self.func_name)
+msg = "No function called '{0}' is registered".format(self.__name__)
 if self.arg_num:
 msg += " which has {0} arguments".format(self.arg_num)
 super(NoFunctionRegisteredException, self).__init__(msg)
--- yaql/expressions.py	(original)
+++ yaql/expressions.py	(refactored)
@@ -13,8 +13,8 @@
 #under the License.
 
 import types
-from context import *
-from exceptions import YaqlExecutionException, NoFunctionRegisteredException
+from .context import *
+from .exceptions import YaqlExecutionException, NoFunctionRegisteredException
 import yaql
 
 
@@ -87,7 +87,7 @@
 fs = self._try_invoke(
 resolvers,
 [self.function_name, this], context) or []
-if not isinstance(fs, types.ListType):
+if not isinstance(fs, list):
 fs = [fs]
 except YaqlExecutionException:
 fs = []
@@ -223,7 +223,7 @@
 ok = True
 if arg_type:
 ok = ok and isinstance(arg_val, arg_type)
-if type(arg_val) == types.BooleanType:
+if type(arg_val) == bool:
 ok = ok and type(arg_val) == arg_type
 if custom_validator:
 ok = ok and custom_validator(arg_val)
--- yaql/parser.py	(original)
+++ yaql/parser.py	(refactored)
@@ -14,9 +14,9 @@
 
 import types
 import ply.yacc as yacc
-import expressions
-import exceptions
-import lexer
+from . import expressions
+from . import exceptions
+from . import lexer
 import tempfile
 
 
@@ -96,7 +96,7 @@
 """
 func : value '.' FUNC arg ')'
 """
-if isinstance(p[4], types.ListType):
+if isinstance(p[4], list):
 arg = p[4]
 else:
 arg = [p[4]]
@@ -114,7 +114,7 @@
 """
 func : FUNC arg ')'
 """
-if isinstance(p[2], types.ListType):
+if isinstance(p[2], list):
 arg = p[2]
 else:
 arg = [p[2]]
@@ -126,11 +126,11 @@
 arg : arg ',' arg
 """
 val_list = []
-if isinstance(p[1], types.ListType):
+if isinstance(p[1], list):
 val_list += p[1]
 else:
 val_list.append(p[1])
-if 

Bug#797284: pytango ftbfs in unstable

[PICCA Frederic-Emmanuel]

ok, so the missing symbols comes from 

attribute.o and wattribute.o

Bug#798143: packagesearch: FTBFS against libxapian22v5

[Niels Thykier]

Package: packagesearch
Version: 2.7.4
Severity: serious

Hi,

We cannot rebuild packagesearch.  The error is included below:

"""
/usr/lib/x86_64-linux-gnu/qt4/bin/uic tagchooserwidget.ui -o 
.ui/ui_tagchooserwidget.h
g++ -c -m64 -pipe -O2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -D_REENTRANT -Wall -W -fPIC -DQT_NO_DEBUG 
-DQT_PLUGIN -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED 
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore 
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 -I. 
-I../.. -I/usr/include/tagcoll-2.0.14 -I.moc -I.ui -o .obj/relatedplugin.o 
relatedplugin.cpp
relatedplugin.cpp:238:35: fatal error: ept/debtags/debtags.tcc: No such file or 
directory
"""

~Niels

Bug#796721: tntnet patch for GCC 5 transition

[Kari Pahula]

tags 796721 patch
thanks

Attached is a tntnet patch for the GCC 5 transition, with a library
package rename.  Tested to work with cxxtools which had made the
transition.
diff -Nru tntnet-2.2.1/debian/changelog tntnet-2.2.1/debian/changelog
--- tntnet-2.2.1/debian/changelog	2014-01-22 19:31:26.0 +0200
+++ tntnet-2.2.1/debian/changelog	2015-09-05 18:57:54.0 +0300
@@ -1,3 +1,11 @@
+tntnet (2.2.1-2) unstable; urgency=medium
+
+  * Bump library package name to 12v5 for C++ ABI transition.  (Closes:
+#796721)
+  * Bump Standards-Version to 3.9.6 (No changes necessary)
+
+ -- Kari Pahula   Sat, 05 Sep 2015 18:57:54 +0300
+
 tntnet (2.2.1-1) unstable; urgency=high
 
   * New upstream release (SONAME 12)
diff -Nru tntnet-2.2.1/debian/control tntnet-2.2.1/debian/control
--- tntnet-2.2.1/debian/control	2014-01-22 18:14:31.0 +0200
+++ tntnet-2.2.1/debian/control	2015-09-06 11:56:31.0 +0300
@@ -2,8 +2,8 @@
 Section: httpd
 Priority: extra
 Maintainer: Kari Pahula 
-Build-Depends: cdbs, debhelper (>= 9), libcxxtools-dev (>= 2.2.1), libltdl-dev, zip, pkg-config, dh-autoreconf, libtool, libssl-dev
-Standards-Version: 3.9.5
+Build-Depends: cdbs, debhelper (>= 9), libcxxtools-dev (>= 2.2.1-2), libltdl-dev, zip, pkg-config, dh-autoreconf, libtool, libssl-dev
+Standards-Version: 3.9.6
 Homepage: http://www.tntnet.org/
 
 Package: tntnet
@@ -120,11 +120,13 @@
  it scalable. It uses a dynamic pool of worker threads, which answer
  requests from HTTP clients.
 
-Package: libtntnet12
+Package: libtntnet12v5
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: tntnet-runtime
+Breaks: libtntnet12
+Replaces: libtntnet12
 Description: Tntnet libraries
  Tntnet has a template-language called ecpp similar to PHP, JSP or
  Mason, where you can embed c++ code inside a HTML page to generate
@@ -161,7 +163,7 @@
 Package: libtntnet-dev
 Architecture: any
 Section: libdevel
-Depends: ${shlibs:Depends}, ${misc:Depends}, libcxxtools-dev, libtntnet12 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libcxxtools-dev, libtntnet12v5 (= ${binary:Version})
 Conflicts: tntnet-dev (<< 1.6.3-3)
 Replaces: tntnet-dev (<< 1.6.3-3)
 Description: Tntnet library development headers
diff -Nru tntnet-2.2.1/debian/libtntnet12.install tntnet-2.2.1/debian/libtntnet12.install
--- tntnet-2.2.1/debian/libtntnet12.install	2011-08-24 20:06:43.0 +0300
+++ tntnet-2.2.1/debian/libtntnet12.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-debian/tmp/usr/lib/lib*.so.*		usr/lib
diff -Nru tntnet-2.2.1/debian/libtntnet12v5.install tntnet-2.2.1/debian/libtntnet12v5.install
--- tntnet-2.2.1/debian/libtntnet12v5.install	1970-01-01 02:00:00.0 +0200
+++ tntnet-2.2.1/debian/libtntnet12v5.install	2011-08-24 20:06:43.0 +0300
@@ -0,0 +1 @@
+debian/tmp/usr/lib/lib*.so.*		usr/lib

Processed: tntnet patch for GCC 5 transition

[Debian Bug Tracking System]

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

> tags 796721 patch
Bug #796721 [src:tntnet] tntnet: library transition needed with GCC 5 as default
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#791243: marked as done (poco: library transition may be needed when GCC 5 is the default)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 06:00:18 +
with message-id 
and subject line Bug#791243: fixed in poco 1.3.6p1-5.1
has caused the Debian Bug report #791243,
regarding poco: library transition may be needed when GCC 5 is the default
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.)


-- 
791243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:poco
Version: 1.3.6p1-5
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
--- End Message ---
--- Begin Message ---
Source: poco
Source-Version: 1.3.6p1-5.1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated poco 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, 02 Sep 2015 07:49:04 +0100
Source: poco
Binary: libpoco-dev libpococrypto9v5-dbg libpococrypto9v5 libpocodata9v5-dbg 
libpocodata9v5 libpocofoundation9v5-dbg libpocofoundation9v5 
libpocomysql9v5-dbg libpocomysql9v5 libpoconet9v5-dbg libpoconet9v5 
libpoconetssl9v5-dbg libpoconetssl9v5 libpocoodbc9v5-dbg libpocoodbc9v5 
libpocosqlite9v5-dbg libpocosqlite9v5 libpocoutil9v5-dbg libpocoutil9v5 
libpocoxml9v5-dbg libpocoxml9v5 libpocozip9v5-dbg libpocozip9v5
Architecture: amd64 source
Version: 1.3.6p1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Simon McVittie 
Closes: 791243
Description: 
 

Bug#797984: marked as done (nordugrid-arc: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 06:00:15 +
with message-id 
and subject line Bug#797984: fixed in nordugrid-arc 5.0.2-2
has caused the Debian Bug report #797984,
regarding nordugrid-arc: ABI transition needed for libstdc++ v5
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.)


-- 
797984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nordugrid-arc
Version: 5.0.2-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of nordugrid-arc, std::string appears in functions in
installed headers, so it seems very likely that a transition is needed.
The transition normally consists of renaming the affected library
packages, adding a v5 suffix.  The SONAME should not be changed when
doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, please avoid doing this unless the new upstream version
is extremely low-risk: this transition has been going on for 1 month
already, and anything that drags it out further is bad for Debian.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the C++ library build-dependencies of nordugrid-arc:

* glibmm, cppunit and canl-c++ have already been renamed
* libdb++ is not believed to need a transition

so I think nordugrid-arc is ready to start its transition now.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: nordugrid-arc
Source-Version: 5.0.2-2

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated nordugrid-arc 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 04 Sep 2015 11:35:01 +0200
Source: nordugrid-arc
Binary: libarccommon3v5 nordugrid-arc-client nordugrid-arc-arcproxyalt 
nordugrid-arc-hed nordugrid-arc-gridftpd nordugrid-arc-cache-service 
nordugrid-arc-datadelivery-service nordugrid-arc-ldap-infosys 
nordugrid-arc-aris nordugrid-arc-egiis nordugrid-arc-ldap-monitor 
nordugrid-arc-ws-monitor nordugrid-arc-arex nordugrid-arc-plugins-needed 
nordugrid-arc-plugins-globus nordugrid-arc-acix-core nordugrid-arc-acix-cache 
nordugrid-arc-acix-index nordugrid-arc-dev nordugrid-arc-python 
nordugrid-arc-java nordugrid-arc-gridmap-utils nordugrid-arc-ca-utils 
nordugrid-arc-misc-utils nordugrid-arc-dbg
Architecture: source amd64 all
Version: 5.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 

Bug#797284: Info received (Bug#797284: pytango ftbfs in unstable)

[PICCA Frederic-Emmanuel]

:/usr/lib/i386-linux-gnu$ nm -D libtango.so.8.1.2  | grep ranges_type | c++filt 
0045f258 D Tango::ranges_type2const::enu
00460dfc B Tango::ranges_type2const::str[abi:cxx11]
0045f280 D Tango::ranges_type2const::enu
00460fdc B Tango::ranges_type2const::str[abi:cxx11]
0045f27c D Tango::ranges_type2const::enu
00460fac B Tango::ranges_type2const::str[abi:cxx11]
0045f26c D Tango::ranges_type2const::enu
00460eec B Tango::ranges_type2const::str[abi:cxx11]
0045f278 D Tango::ranges_type2const::enu
00460f7c B Tango::ranges_type2const::str[abi:cxx11]
0045f268 D Tango::ranges_type2const::enu
00460ebc B Tango::ranges_type2const::str[abi:cxx11]
0045f25c D Tango::ranges_type2const::enu
00460e2c B Tango::ranges_type2const::str[abi:cxx11]
0045f250 D Tango::ranges_type2const::enu
00460d9c B Tango::ranges_type2const::str[abi:cxx11]
0045f254 D Tango::ranges_type2const::enu
00460dcc B Tango::ranges_type2const::str[abi:cxx11]
0045f270 D Tango::ranges_type2const::enu
00460f1c B Tango::ranges_type2const::str[abi:cxx11]
0045f260 D Tango::ranges_type2const::enu
00460e5c B Tango::ranges_type2const::str[abi:cxx11]
0045f274 D Tango::ranges_type2const::enu
00460f4c B Tango::ranges_type2const::str[abi:cxx11]
0045f264 D Tango::ranges_type2const::enu
00460e8c B Tango::ranges_type2const::str[abi:cxx11]

so it seems that tango does not contain the symbol.

Tango::ranges_type2const::str

ok this symbol is not from the abi:cxx11.

We need to understand why pytango was built with the old abi.

Bug#796719: tntdb patch for GCC 5 transition

[Kari Pahula]

tags 796719 patch
thanks

Attached is a tntdb patch for the GCC 5 transition, with a library
package rename.  Tested to work with cxxtools which had made the
transition.
diff -Nru tntdb-1.3/debian/changelog tntdb-1.3/debian/changelog
--- tntdb-1.3/debian/changelog	2013-07-12 19:35:32.0 +0300
+++ tntdb-1.3/debian/changelog	2015-09-05 20:44:44.0 +0300
@@ -1,3 +1,11 @@
+tntdb (1.3-3) unstable; urgency=medium
+
+  * Bump library package names to 4v5 for C++ ABI transition.  (Closes:
+#796719)
+  * Bump Standards-Version to 3.9.6 (No changes necessary)
+
+ -- Kari Pahula   Sat, 05 Sep 2015 20:44:44 +0300
+
 tntdb (1.3-2) unstable; urgency=low
 
   * Build-Conflicts: libtntdb3, libtntdb-dev (Closes: #716749)
diff -Nru tntdb-1.3/debian/control tntdb-1.3/debian/control
--- tntdb-1.3/debian/control	2013-07-12 19:36:05.0 +0300
+++ tntdb-1.3/debian/control	2015-09-05 22:51:55.0 +0300
@@ -4,14 +4,16 @@
 Maintainer: Kari Pahula 
 Build-Depends: cdbs, debhelper (>= 9), libcxxtools-dev (>= 2.2), libsqlite3-dev, libmysqlclient-dev, libpq-dev, libltdl-dev, doxygen, dh-autoreconf, sqlite3
 Build-Conflicts: libtntdb-dev, libtntdb3
-Standards-Version: 3.9.4
+Standards-Version: 3.9.6
 Homepage: http://www.tntnet.org/tntdb.html
 
-Package: libtntdb4
+Package: libtntdb4v5
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: tntdb-mysql4|tntdb-postgresql4|tntdb-sqlite4
-Suggests: tntdb-mysql4, tntdb-postgresql4, tntdb-sqlite4, libtntdb-dev
+Recommends: tntdb-mysql4v5|tntdb-postgresql4v5|tntdb-sqlite4v5
+Suggests: tntdb-mysql4v5, tntdb-postgresql4v5, tntdb-sqlite4v5, libtntdb-dev
+Breaks: libtntdb4
+Replaces: libtntdb4
 Description: C++ class library for easy database access
  This library provides a thin, database independent layer over an SQL
  database.  It lacks complex features like schema queries or wrapper
@@ -22,9 +24,11 @@
  .
  Currently has support for MySQL, PostgreSQL and SQLite.
 
-Package: tntdb-mysql4
+Package: tntdb-mysql4v5
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libtntdb-mysql4
+Replaces: libtntdb-mysql4
 Description: MySQL backend for tntdb database access library
  This library provides a thin, database independent layer over an SQL
  database.  It lacks complex features like schema queries or wrapper
@@ -35,9 +39,11 @@
  .
  This file has the necessary files for MySQL support.
 
-Package: tntdb-postgresql4
+Package: tntdb-postgresql4v5
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libtntdb-postgresql4
+Replaces: libtntdb-postgresql4
 Description: PostgreSQL backend for tntdb database access library
  This library provides a thin, database independent layer over an SQL
  database.  It lacks complex features like schema queries or wrapper
@@ -48,9 +54,11 @@
  .
  This file has the necessary files for PostgreSQL support.
 
-Package: tntdb-sqlite4
+Package: tntdb-sqlite4v5
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libtntdb-sqlite4
+Replaces: libtntdb-sqlite4
 Description: SQLite backend for tntdb database access library
  This library provides a thin, database independent layer over an SQL
  database.  It lacks complex features like schema queries or wrapper
@@ -64,7 +72,7 @@
 Package: libtntdb-dev
 Architecture: any
 Section: libdevel
-Depends: libtntdb4 (= ${binary:Version}), libcxxtools-dev, ${shlibs:Depends}, ${misc:Depends}, libjs-jquery
+Depends: libtntdb4v5 (= ${binary:Version}), libcxxtools-dev, ${shlibs:Depends}, ${misc:Depends}, libjs-jquery
 Description: Development headers for tntdb
  This library provides a thin, database independent layer over an SQL
  database.  It lacks complex features like schema queries or wrapper
diff -Nru tntdb-1.3/debian/libtntdb4.install tntdb-1.3/debian/libtntdb4.install
--- tntdb-1.3/debian/libtntdb4.install	2012-04-24 19:32:13.0 +0300
+++ tntdb-1.3/debian/libtntdb4.install	1970-01-01 02:00:00.0 +0200
@@ -1,2 +0,0 @@
-debian/tmp/usr/lib/lib*.so.*	usr/lib
-debian/tmp/usr/lib/tntdb/tntdb*-replicate.so*
diff -Nru tntdb-1.3/debian/libtntdb4v5.install tntdb-1.3/debian/libtntdb4v5.install
--- tntdb-1.3/debian/libtntdb4v5.install	1970-01-01 02:00:00.0 +0200
+++ tntdb-1.3/debian/libtntdb4v5.install	2012-04-24 19:32:13.0 +0300
@@ -0,0 +1,2 @@
+debian/tmp/usr/lib/lib*.so.*	usr/lib
+debian/tmp/usr/lib/tntdb/tntdb*-replicate.so*
diff -Nru tntdb-1.3/debian/tntdb-mysql4.install tntdb-1.3/debian/tntdb-mysql4.install
--- tntdb-1.3/debian/tntdb-mysql4.install	2012-04-24 19:32:21.0 +0300
+++ tntdb-1.3/debian/tntdb-mysql4.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-debian/tmp/usr/lib/tntdb/tntdb*-mysql.so*
diff -Nru tntdb-1.3/debian/tntdb-mysql4v5.install tntdb-1.3/debian/tntdb-mysql4v5.install
--- tntdb-1.3/debian/tntdb-mysql4v5.install	1970-01-01 02:00:00.0 +0200
+++ tntdb-1.3/debian/tntdb-mysql4v5.install	2012-04-24 19:32:21.0 +0300
@@ 

Processed: tntdb patch for GCC 5 transition

[Debian Bug Tracking System]

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

> tags 796719 patch
Bug #796719 [src:tntdb] tntdb: library transition needed with GCC 5 as default
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
796719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#797865: marked as done (libpqxx: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 13:00:18 +
with message-id 
and subject line Bug#797865: fixed in libpqxx 4.0.1+dfsg-4
has caused the Debian Bug report #797865,
regarding libpqxx: ABI transition needed for libstdc++ v5
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.)


-- 
797865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpqxx
Version: 4.0.1+dfsg-3
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of libpqxx, std::string appears in the installed headers
in many places, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libpqxx-4.0v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of libpqxx, there do not seem to be
any C++ libraries, so it seems ready to go.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: libpqxx
Source-Version: 4.0.1+dfsg-4

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

Debian distribution maintenance software
pp.
Marcin Kulisz (kuLa)  (supplier of updated libpqxx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Sep 2015 07:52:13 +0100
Source: libpqxx
Binary: libpqxx-dev libpqxx3-dev libpqxx-doc libpqxx-4.0v5 libpqxx-dbg
Architecture: source amd64 all
Version: 4.0.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Marcin Kulisz (kuLa) 
Changed-By: Marcin Kulisz (kuLa) 
Description:
 libpqxx-4.0v5 - C++ library to connect to PostgreSQL
 libpqxx-dbg - C++ library to connect to PostgreSQL (debugging symbols)
 libpqxx-dev - C++ library to connect to PostgreSQL (development files)
 libpqxx-doc - C++ library to connect to PostgreSQL (documentation)
 libpqxx3-dev - Transitional dummy package for libpqxx-dev
Closes: 795866 797865
Changes:
 libpqxx (4.0.1+dfsg-4) unstable; urgency=medium
 .
   * Bumping up standars version to 3.9.6
   * Conforming with Short Name for License specification in d/copyright
   * Fixed source-contains-prebuilt-doxygen-documentation by removing all of
 the doxygen generated docs and recreating it at build time
   * Changing package name for gcc-5 

Bug#797983: marked as done (mathic: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 13:00:19 +
with message-id 
and subject line Bug#797983: fixed in mathic 1.0~git20130827-3
has caused the Debian Bug report #797983,
regarding mathic: ABI transition needed for libstdc++ v5
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.)


-- 
797983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mathic
Version: 1.0~git20130827-2
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of mathic, std::string appears in functions in public
headers, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libmathic0v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of mathic, the C++ libraries
are gtest, which is header-only, and memtailor, which does not appear
to need a transition. So this sub-transition is ready to start.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: mathic
Source-Version: 1.0~git20130827-3

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated mathic 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, 06 Sep 2015 02:31:53 -0400
Source: mathic
Binary: libmathic-dev libmathic0v5 libmathic-dbg
Architecture: source amd64
Version: 1.0~git20130827-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 libmathic-dbg - C++ library for Groebner basis computation (debugging symbols)
 libmathic-dev - C++ library for Groebner basis computation (developer tools)
 libmathic0v5 - C++ library for Groebner basis computation (runtime library)
Closes: 797983
Changes:
 mathic (1.0~git20130827-3) unstable; urgency=medium
 .
   * debian/{control,libmathic0.install}
 - Rename libmathic0 to libmathic0v5 for libstdc++ transition
   (Closes: #797983).
   * debian/control
 - Add libmathic0 to Breaks/Replaces.
Checksums-Sha1:
 d79fca301ec891e4c91a6f270edfefaaf479c348 2197 mathic_1.0~git20130827-3.dsc
 

Bug#797386: monotone: FTBFS on ppc64el (test suite failure)

[Julien Cristau]

Control: severity -1 important

Seems to have built on the third try.  Downgrading for now.

Cheers,
Julien

On Sun, Aug 30, 2015 at 12:06:50 +0200, Julien Cristau wrote:

> Source: monotone
> Version: 1.1-4.1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> from the build log:
> 
> > Check failed (return value): wanted -13 got 0
> > stack traceback:
> > [string "testlib.lua"]:114: in function 'err'
> > [string "testlib.lua"]:659: in function 'post_cmd'
> > [string "testlib.lua"]:759: in function 'finish'
> > ...notone-1.1/test/func/log_quits_on_SIGPIPE/__driver__.lua:102: in 
> > main chunk
> > [C]: in function 'xpcall'
> > [string "testlib.lua"]:1158: in function <[string 
> > "testlib.lua"]:1126>
> > [C]: in function 'run_tests_in_children'
> > [string "testlib.lua"]:1087: in function <[string 
> > "testlib.lua"]:882>
> > Of 612 tests run:
> > 515 succeeded
> > 1 failed
> > 35 had expected failures
> > 0 succeeded unexpectedly
> > 61 were skipped
> > debian/rules:85: recipe for target 'override_dh_auto_test' failed
> > make[1]: Leaving directory '/«PKGBUILDDIR»'
> > debian/rules:56: recipe for target 'build-arch' failed
> 
> See the full log at
> https://buildd.debian.org/status/fetch.php?pkg=monotone=ppc64el=1.1-4.1=1440783122
> 
> Cheers,
> Julien




signature.asc
Description: Digital signature

Processed: Re: Bug#797386: monotone: FTBFS on ppc64el (test suite failure)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797386 [src:monotone] monotone: FTBFS on ppc64el (test suite failure)
Severity set to 'important' from 'serious'

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

Bug#798187: re2: ftbfs on mips{,el} (test failure)

[Julien Cristau]

Source: re2
Version: 20150701+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

See logs at
https://buildd.debian.org/status/logs.php?pkg=re2=20150701%2Bdfsg-2=sid

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#798188: wmacpi: FTBFS when rebuild against libdockapp3

[Niels Thykier]

Package: wmacpi
Version: 2.3.1
Severity: serious

Hi,

The wmacpi package FTBFS when rebuild against libdockapp3.

"""
gcc -MM -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -O2 
-Wall -W -g -ansi wmacpi.c > wmacpi.d
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -O2 -Wall 
-W -g -ansi -D_FORTIFY_SOURCE=2  -c -o wmacpi.o wmacpi.c
wmacpi.c:22:21: fatal error: dockapp.h: No such file or directory
compilation terminated.
make[1]: *** [wmacpi.o] Error 1
"""

This issue is also blocking the GCC-5 transition.

~Niels

Bug#795056: SOURCE_DATE_EPOCH

[Camm Maguire]

Greetings!  Following the link you reference, it appears that I do not
need to export this variable, right?  Debhelper is at a later version in
unstable.

=
The package would not become immediately reproducible with this
solution though because it does not use dh in debian/rules but
instead classic debhelper. Because of that $SOURCE_DATE_EPOCH has
to be exported in debian/rules [3]
=
Setting the variable

Debhelper (as of 9.20150628.0~reproducible3, see commit and bug) exports this 
variable during its build, so if you are using debhelper you don't
(in theory) need to do anything extra.

CDBS (as of 0.4.130.0~reproducible3, see commit and bug) exports this variable 
during its build.

As a last resort to be avoided where possible, package maintainers may set and 
export this variable manually in debian/rules:

export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog -SDate)" +%s)
=

Take care,
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#798190: reads nonexistant dir, segfaults Kodi on startup

[Steinar H. Gunderson]

Package: libcec3
Version: 3.0.1+dfsg2-4
Severity: grave

Hi,

Recently, Kodi has started segfaulting on startup, pointing to libcec3.
A backtrace reads:

#0  0x7fffecf55789 in __readdir (dirp=dirp@entry=0x0) at 
../sysdeps/posix/readdir.c:44
#1  0x7fffc81d8b74 in PLATFORM::CDRMEdidParser::GetPhysicalAddress 
(this=this@entry=0x7fffc29e8550)
at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/platform/drm/drm-edid.cpp:54
#2  0x7fffc81e4c0e in CEC::CUSBCECAdapterCommunication::GetPhysicalAddress 
(this=0x7fffb4000f50)
at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/adapter/Pulse-Eight/USBCECAdapterCommunication.cpp:697
#3  0x7fffc81baaec in CEC::CCECClient::AutodetectPhysicalAddress 
(this=0x1a7cab0)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:1224
#4  0x7fffc81b884c in CEC::CCECClient::SetPhysicalAddress (this=0x1a7cab0, 
configuration=...)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:236
#5  0x7fffc81bcdcb in CEC::CCECClient::OnRegister (this=0x1a7cab0) at 
/home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:138
#6  0x7fffc81cd4d2 in CEC::CCECProcessor::RegisterClient (this=0x1a76840, 
client=std::shared_ptr (count 4, weak 0) 0x1a7cab0)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECProcessor.cpp:899
#7  0x7fffc81d3e7a in CEC::CLibCEC::Open (this=0x1a78d10, 
strPort=, iTimeoutMs=)
at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/LibCEC.cpp:91
#8  0x010cdd39 in PERIPHERALS::CPeripheralCecAdapter::OpenConnection() 
()
#9  0x010d0434 in PERIPHERALS::CPeripheralCecAdapter::Process() ()
#10 0x0113f56f in CThread::Action() ()
#11 0x0113f832 in CThread::staticThread(void*) ()
#12 0x755ad0a4 in start_thread (arg=0x7fffc29e9700) at 
pthread_create.c:309
#13 0x7fffecf8807d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

It would seem libcec3 unconditionally assumes /sys/class/drm exists
(it does not on my system using the proprietary NVIDIA driver, since
that driver doesn't use drm), and then segfaults when it doesn't.

Could you please add a check for the NULL value?

Processed: tagging 791289, tagging 791302, tagging 791305, tagging 791307, tagging 791311, tagging 791312 ...

[Debian Bug Tracking System]

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

> tags 791289 + pending
Bug #791289 [release.debian.org] snappy: library transition may be needed when 
GCC 5 is the default
Added tag(s) pending.
> tags 791302 + pending
Bug #791302 [release.debian.org] tinyxml: library transition may be needed when 
GCC 5 is the default
Added tag(s) pending.
> tags 791305 + pending
Bug #791305 [release.debian.org] transition: ucommon (libucommon7v5)
Added tag(s) pending.
> tags 791307 + pending
Bug #791307 [release.debian.org] transition: vamp-plugin-sdk (GCC 5)
Added tag(s) pending.
> tags 791311 + pending
Bug #791311 [release.debian.org] wxwidgets3.0: library transition is needed 
when GCC 5 is the default
Added tag(s) pending.
> tags 791312 + pending
Bug #791312 [release.debian.org] xapian-core: library transition may be needed 
when GCC 5 is the default
Added tag(s) pending.
> tags 791314 + pending
Bug #791314 [release.debian.org] transition: xqilla (libxqilla6v5)
Added tag(s) pending.
> tags 791327 + pending
Bug #791327 [release.debian.org] transition: voms (libvomsapi1v5)
Added tag(s) pending.
> tags 791746 + pending
Bug #791746 [release.debian.org] transition: libindi
Added tag(s) pending.
> block 791746 with 795818
Bug #791746 [release.debian.org] transition: libindi
791746 was blocked by: 790756
791746 was not blocking any bugs.
Added blocking bug(s) of 791746: 795818
> tags 792619 + pending
Bug #792619 [release.debian.org] transition: ffmpeg
Added tag(s) pending.
> tags 793909 + pending
Bug #793909 [release.debian.org] transition: libgig (GCC 5)
Added tag(s) pending.
> tags 794402 + pending
Bug #794402 [release.debian.org] libproxy: library transition is needed when 
GCC 5 is the default
Added tag(s) pending.
> tags 794626 + pending
Bug #794626 [release.debian.org] transition: libconfig (libconfig++9v5)
Added tag(s) pending.
> tags 794734 + pending
Bug #794734 [release.debian.org] openexr: library transition is needed when GCC 
5 is the default
Added tag(s) pending.
> tags 794753 + pending
Bug #794753 [release.debian.org] libxml++2.6: Transistion required for GCC-5
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
791289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791289
791302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791302
791305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791305
791307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791307
791311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791311
791312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791312
791314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791314
791327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791327
791746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791746
792619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792619
793909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793909
794402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794402
794626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794626
794734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794734
794753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#781232: Bug#766884: libxml2 broken in sid for months already

[Guido Günther]

Hi Aron,
On Sat, Sep 05, 2015 at 02:35:49PM +0200, Guido Günther wrote:
> tags 781232 +patch
> thanks
> 
> Hi Salvatore, Hi Aron,
> On Mon, Aug 31, 2015 at 11:02:48AM +0200, Salvatore Bonaccorso wrote:
> > Hi Aron,
> > 
> > Specific for the issue now seen for #781232: Looked shortly at
> > https://bugzilla.gnome.org/show_bug.cgi?id=731063#c1 According to that
> > comment the original patch lead to more issues (e.g.  the one which we
> > see now) and more patches were applied. I have though not tried to
> > skim trough to check which are required.
> 
> Attached patch resolves the libvirt related regression for me. It's a
> straight cherry pick from upstream commit
> 
> beb7281055dbf0ed4d041022a67c6c5cfd126f25
> 
> Can we have this in sid please? It would also be great to have this
> backported to Jessie since libvirt is there affected as well. (And yes,
> I do think the severity is correct).

I've uploaded a NMU to delayed 7days so in case nobody has time to take
care of it it will get fixed eventually. We can always dcut it.

Let me know if I should take care of stable as well?

Cheers,
 -- Guido

Bug#796676: marked as done (amarok: Amarok won't start)

[Debian Bug Tracking System]

Your message dated Sun, 6 Sep 2015 10:26:00 + (UTC)
with message-id <1941812508.2953606.1441535160444.javamail.ya...@mail.yahoo.com>
and subject line FIXED: Crash using mixed GCC4.9/GCC5 amarok installation
has caused the Debian Bug report #796676,
regarding amarok: Amarok won't start
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.)


-- 
796676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok
Version: 2.8.0-2.1+b2
Severity: grave
Justification: renders package unusable

Dear maintainer

As soon as I open amarok I get:

QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
unnamed app(8305): Communication problem with  "amarok" , it probably crashed.
Error message was:  " org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

KCrash: Application 'amarok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/user/.kde/socket-PC/kdeinit4__0


I have tried reinstalling, removing and deleting ~/.kde/share/apps/amarok
folder with no success



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages amarok depends on:
ii  amarok-common 2.8.0-2.1
ii  amarok-utils  2.8.0-2.1+b2
ii  kde-runtime   4:4.14.2-2
ii  libaio1   0.3.110-1
ii  libavcodec-ffmpeg56   7:2.7.2-1
ii  libavformat-ffmpeg56  7:2.7.2-1
ii  libavutil-ffmpeg547:2.7.2-1
ii  libc6 2.19-19
ii  libcurl3-gnutls   7.44.0-1
ii  libgcrypt20   1.6.3-2
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libgl1-mesa-glx [libgl1]  10.6.4-1
ii  libglib2.0-0  2.44.1-1.1
ii  libgpod4  0.8.3-1.1+b3
ii  libkcmutils4  4:4.14.2-5
ii  libkdecore5   4:4.14.2-5
ii  libkdeui5 4:4.14.2-5
ii  libkdewebkit5 4:4.14.2-5
ii  libkdnssd44:4.14.2-5
ii  libkfile4 4:4.14.2-5
ii  libkio5   4:4.14.2-5
ii  libknewstuff3-4   4:4.14.2-5
ii  liblastfm11.0.8-3
ii  libloudmouth1-0   1.4.3-12.1
ii  libmtp9   1.1.9-3
ii  libmysqlclient18  5.6.25-3
ii  libnepomukcore4   4:4.14.0-1+b3
ii  libofa0   0.9.3-7
ii  libphonon44:4.8.3-1
ii  libplasma34:4.14.2-5
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.7+dfsg-1
ii  libqt4-network4:4.8.7+dfsg-1
ii  libqt4-opengl 4:4.8.7+dfsg-1
ii  libqt4-script 4:4.8.7+dfsg-1
ii  libqt4-sql4:4.8.7+dfsg-1
ii  libqt4-svg4:4.8.7+dfsg-1
ii  libqt4-xml4:4.8.7+dfsg-1
ii  libqtcore44:4.8.7+dfsg-1
ii  libqtgui4 4:4.8.7+dfsg-1
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.3.4.dfsg-3
ii  libsolid4 4:4.14.2-5
ii  libsoprano4   2.9.4+dfsg-3
ii  libstdc++65.1.1-14
ii  libthreadweaver4  4:4.14.2-5
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.2+dfsg1-3
ii  phonon4:4.8.3-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages amarok recommends:
ii  clamz0.5-2+b1
ii  kio-audiocd  4:4.14.2-1

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.7+dfsg-1
pn  libqt4-sql-psql
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-1
pn  moodbar

Versions of packages amarok-common depends on:
ii  perl  5.20.2-6

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-vlc [phonon-backend]  0.8.0-2

-- no debconf information
--- End Message ---
--- Begin Message ---
It is fixed when you update amarok and all of its dependencies (just update all 
your packages) to the version in sid.

Processed: Re: Bug#797804: pgadmin3 segfaults after rightclick

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797804 [pgadmin3] pgadmin3 segfaults after rightclick
Severity set to 'important' from 'grave'

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

Bug#797823: marked as done (amarok: Amarok crashes at startup with Qt5/Qt5 libs in stack)

[Debian Bug Tracking System]

Your message dated Sun, 6 Sep 2015 10:26:00 + (UTC)
with message-id <1941812508.2953606.1441535160444.javamail.ya...@mail.yahoo.com>
and subject line FIXED: Crash using mixed GCC4.9/GCC5 amarok installation
has caused the Debian Bug report #797823,
regarding amarok: Amarok crashes at startup with Qt5/Qt5 libs in stack
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.)


-- 
797823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok
Version: 2.8.0-2.1+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Amarok crashes at startup with a stack containing both Qt4 and Qt5 libs. The 
system is a mix of Testing and Unstable, but Amarok from Unstable is not 
instalable due to dependencies.

The stack:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __strcmp_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29
#7  0x7fb099536c9f in QMetaType::registerNormalizedType(QByteArray const&, 
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void 
const*), int, QFlags, QMetaObject const*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb09982f060 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x7fb0c64ae9fa in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7ffdab1821b8, env=env@entry=0x7ffdab1821c8) at dl-init.c:78
#10 0x7fb0c64aeae3 in call_init (env=0x7ffdab1821c8, argv=0x7ffdab1821b8, 
argc=1, l=) at dl-init.c:36
#11 _dl_init (main_map=main_map@entry=0x2375aa0, argc=1, argv=0x7ffdab1821b8, 
env=0x7ffdab1821c8) at dl-init.c:126
#12 0x7fb0c64b2c48 in dl_open_worker (a=a@entry=0x7ffdab180658) at 
dl-open.c:577
#13 0x7fb0c64ae8b4 in _dl_catch_error 
(objname=objname@entry=0x7ffdab180648, 
errstring=errstring@entry=0x7ffdab180650, 
mallocedp=mallocedp@entry=0x7ffdab180647, operate=operate@entry=0x7fb0c64b2970 
, args=args@entry=0x7ffdab180658) at dl-error.c:187
#14 0x7fb0c64b243b in _dl_open (file=0x2369b50 
"/usr/lib/vlc/plugins/gui/libqt4_plugin.so", mode=-2147483647, 
caller_dlopen=, nsid=-2, argc=1, argv=0x7ffdab1821b8, 
env=0x7ffdab1821c8) at dl-open.c:661
#15 0x7fb0bd74202b in dlopen_doit (a=a@entry=0x7ffdab180870) at dlopen.c:66
#16 0x7fb0c64ae8b4 in _dl_catch_error (objname=0x20b9000, 
errstring=0x20b9008, mallocedp=0x20b8ff8, operate=0x7fb0bd741fd0 , 
args=0x7ffdab180870) at dl-error.c:187
#17 0x7fb0bd7425dd in _dlerror_run (operate=operate@entry=0x7fb0bd741fd0 
, args=args@entry=0x7ffdab180870) at dlerror.c:163
#18 0x7fb0bd7420c1 in __dlopen (file=, mode=) 
at dlopen.c:87
#19 0x7fb09fa4373f in ?? () from /usr/lib/libvlccore.so.8
#20 0x7fb09fa2787b in ?? () from /usr/lib/libvlccore.so.8
#21 0x7fb09fa27ba8 in ?? () from /usr/lib/libvlccore.so.8
#22 0x7fb09fa27b04 in ?? () from /usr/lib/libvlccore.so.8
#23 0x7fb09fa28084 in ?? () from /usr/lib/libvlccore.so.8
#24 0x7fb09fa2867a in ?? () from /usr/lib/libvlccore.so.8
#25 0x7fb09f9ae6fd in libvlc_InternalInit () from /usr/lib/libvlccore.so.8
#26 0x7fb09f77fa8b in libvlc_new () from /usr/lib/libvlc.so.5
#27 0x7fb09fcd1f6b in ?? () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#28 0x7fb09fcb34d3 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#29 0x7fb09fcb4193 in qt_plugin_instance () from 
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so
#30 0x7fb0c39cd6d3 in QPluginLoader::instance (this=0x7ffdab1812c0) at 
plugin/qpluginloader.cpp:204
#31 0x7fb0a0348c1b in ?? () from 
/usr/lib/kde4/plugins/phonon_platform/kde.so
#32 0x7fb0a03493b7 in ?? () from 
/usr/lib/kde4/plugins/phonon_platform/kde.so
#33 0x7fb0c2cb2e06 in Phonon::FactoryPrivate::createBackend 
(this=this@entry=0x2207b50) at ../../phonon/factory.cpp:252
#34 0x7fb0c2cb4258 in Phonon::Factory::backend 
(createWhenNull=createWhenNull@entry=true) at ../../phonon/factory.cpp:576
#35 0x7fb0c2cb49a2 in Phonon::Factory::createAudioOutput (parent=0x20ebf00) 
at ../../phonon/factory.cpp:470
#36 0x7fb0c2ca803f in Phonon::AudioOutputPrivate::createBackendObject 
(this=0x21eb430) at ../../phonon/audiooutput.cpp:136
#37 0x7fb0c2ca552f in Phonon::AudioOutputPrivate::init (this=0x21eb430, 
c=Phonon::MusicCategory) at ../../phonon/audiooutput.cpp:103
#38 0x7fb0c6022af3 in EngineController::initializePhonon (this=0x2206120) 
at 

Bug#797804: pgadmin3 segfaults after rightclick

[Christoph Berg]

Control: severity -1 important

Re: Marc Neininger 2015-09-02 
<20150902171723.27655.99593.report...@touchlette.fritz.box>
> Package: pgadmin3
> Version: 1.20.0-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
> I tried to manage a local postgres installation but when trying to add a new
> server pgadmin3 closes after segfaulting.
> Message: $> Debug: Adding duplicate image handler for 'PNG file'
> 
> I found nearly the same bug description last year but it seems that the bug
> returned.
> 
> I use a fully upgraded debian testing environment but when the bug appeared I
> even upgraded pgadmin3 to experimental. This didn't help either.

Hi Marc,

the package works for me in my sid chroot, so I still have no idea
what the problem is. I'm downgrading the severity because the problem
doesn't make the package unusable for everyone.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#798162: node-leveldown: FTBFS when rebuilt against libleveldb1v5 (GCC-5 transition)

[Niels Thykier]

Package: node-leveldown
Version: 1.0.0+dfsg-1
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

The node-leveldown package FTBFS when we attempted to rebuild it
against libleveldb1v5 for the GCC-5 transition:

"""
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[2]: Entering directory '/«BUILDDIR»/node-leveldown-1.0.0+dfsg/build'
  CXX(target) Release/obj.target/leveldown/src/batch.o
[... more issues here ...]
In file included from ../src/database.h:18:0,
 from ../src/batch.cc:5:
../src/leveldown.h:78:28: error: 'NanGetCurrentContext' was not declared in 
this scope
   NanGetCurrentContext()->Global(), callback, argc, argv);
^
../src/batch.cc:146:5: note: in expansion of macro 'LD_RUN_CALLBACK'
 LD_RUN_CALLBACK(v8::Local::Cast(args[0]), 0, NULL);
 ^
../src/leveldown.h:78:61: error: 'NanMakeCallback' was not declared in this 
scope
   NanGetCurrentContext()->Global(), callback, argc, argv);
 ^
../src/batch.cc:146:5: note: in expansion of macro 'LD_RUN_CALLBACK'
 LD_RUN_CALLBACK(v8::Local::Cast(args[0]), 0, NULL);
 ^
../src/batch.cc:149:22: error: 'NanReturnUndefined' was not declared in this 
scope
   NanReturnUndefined();
  ^
make[2]: *** [Release/obj.target/leveldown/src/batch.o] Error 1
leveldown.target.mk:88: recipe for target 
'Release/obj.target/leveldown/src/batch.o' failed
"""

Thanks,
~Niels

Processed: ants: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798165
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798166

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

Bug#798166: ants: depends on vtk 5

[Julien Cristau]

Source: ants
Version: 2.1.0~rc2+git3-g9103999-4
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#798167: camitk: depends on vtk 5

[Julien Cristau]

Source: camitk
Version: 3.4.0-1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#798165: activiz.net: depends on vtk 5

[Julien Cristau]

Source: activiz.net
Version: 1:1.0~git20111214-2
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Processed: activiz.net: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was not blocked by any bugs.
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798165

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

Bug#798172: python-casmoothing: depends on vtk 5

[Julien Cristau]

Source: python-casmoothing
Version: 0.1-2
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Processed: python-casmoothing: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798169 798167 798170 798165 798168 798171 798166
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798172

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

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Niels Thykier]

On Wed, 26 Aug 2015 07:11:14 +1000 Riley Baird
 wrote:
> On Tue, 25 Aug 2015 11:54:00 -0400
> Eric Dorland  wrote:
> 
> > * Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
> > > This is listed in the FTP master's cruft report, so if I'm correct, it
> > > shouldn't be necessary to request a removal from unstable.
> > 
> > Yeah and you have the right conflicts/replaces. I'm surprised it's
> > complaining about this.
> 
> No, at the moment, it is possible to simultaneously install these
> conflicting packages because someone made a NMU just before or after you
> uploaded my package, but they didn't add the hyphen between "libassa"
> and "3", so now we have libassa3.5-5v5 and libassa-3.5-5v5.

Hi,

What is the status on adding these Conflicts/Replaces?  This bug will
soon be the only thing blocking libassa's transition to testing.

Thanks,
~Niels




signature.asc
Description: OpenPGP digital signature

Bug#798178: warzone2100: Major regressions compared to squeeze

[Anton Ivanov]

Package: warzone2100
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The new version is unplayable. 

1. Units produced during a remote mission instead of being delivered to 
the factory delivery area of the factory producing them are locked in a 
rock somewhere off-map rendering them unusable as well as rendering most 
preparation strategies unusable. This is an obvious bug and it worked
correctly in the squeeze version.

2. The "nudge your neigbour" in the unit obstacle avoidance algorithm 
does not work. The result is unit deadlock, because units that need to
"give you way" for you to get past them just sit and wait unless moved
manually.

This can be resolved only by picking every unit separately, and moving
them "by hand". They definitely cannot be moved in a formation any more. 
This renders commanders, sensors, etc mostly unusable. You now cannot
retreat a group under command because the "subordinates" will not move 
out of the way for the commander to pass. They will also not move out 
of the way for any damaged units to go for repair. 

Again - this worked in squeeze.

Frankly, can we have the squeeze version recompiled and released as an 
"update", this "improvement" is unplayable.

I am definitely recompiling it locally from squeeze sources as the main 
users (the kids) are revolting that this is unusable.

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

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

Versions of packages warzone2100 depends on:
ii  libc6 2.19-18
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libfribidi0   0.19.6-3
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglc0   0.7.2-5+b2
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libminiupnpc101.9.20140610-2
ii  libogg0   1.3.2-1
ii  libopenal11:1.15.1-5
ii  libphysfs12.0.3-2
ii  libpng12-01.2.50-2+b2
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libsdl1.2debian   1.2.15-10+b1
ii  libstdc++64.9.2-10
ii  libtheora01.1.1+dfsg.1-6
ii  libvorbis0a   1.3.4-2
ii  libvorbisfile31.3.4-2
ii  libx11-6  2:1.6.2-3
ii  libxrandr22:1.4.2-1+b1
ii  warzone2100-data  3.1.1-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages warzone2100 recommends:
ii  warzone2100-music  3.1.1-1

warzone2100 suggests no packages.

-- no debconf information

Bug#798164: vtk: do not ship in stretch

[Julien Cristau]

Source: vtk
Version: 5.8.0-17.5
Severity: serious
Tags: stretch sid

The mix of vtk 5.x and vtk 6.x in the archive was bad enough in jessie,
we shouldn't ship that again for stretch.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#798168: caret: depends on vtk 5

[Julien Cristau]

Source: caret
Version: 5.6.4~dfsg.1-3
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Processed: caret: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798166 798167 798165
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798168

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

Processed: camitk: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798165 798166
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798167

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

Processed: viper: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798170 798165 798172 798166 798169 798171 798167 798168
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798174

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

Bug#798174: viper: depends on vtk 5

[Julien Cristau]

Source: viper
Version: 1.0.0-1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Processed: Re: Bug#791520: libmojomojo-perl: FTBFS: Recursive inheritance detected in package 'Types::Serialiser::BooleanBase'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #791520 [libmojomojo-perl] libmojomojo-perl: FTBFS: test failures
Added tag(s) patch.

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

Bug#791520: libmojomojo-perl: FTBFS: Recursive inheritance detected in package 'Types::Serialiser::BooleanBase'

[Niko Tyni]

Control: tag -1 patch

On Sat, Sep 05, 2015 at 09:14:15PM +0200, gregor herrmann wrote:
> Control: tag -1 - fixed-upstream
> # (sorry)

Sorry for not checking this properly. Here's some penance for that.

The formatter_file.t thing broke with liburi-find-perl 20140709-1.
Upstream 1.11 changed the test so it now works again (but is broken
with older versions of URI::Find, which is probably not a problem.)

The unicode.t failure began with libcatalyst-perl 5.90097-1,
which has this in NEWS.Debian:

libcatalyst-perl (5.90097-1) unstable; urgency=medium

  From upstream Changes, 5.90079_001:  

  UTF-8 is now the default encoding (there used to be none...).  You can
  disable this if you need to with MyApp->config(encoding => undef) if it
  causes you trouble.

 -- gregor herrmann   Wed, 12 Aug 2015 11:42:15 +0200

and it can be fixed/worked around with the attached patch.

1.11 builds for me with this, will forward & upload shortly.
-- 
Niko Tyni   nt...@debian.org
>From 12ce7bb7b3dfb3b6e4caab40bb9d850f1e97735b Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 6 Sep 2015 12:52:53 +0300
Subject: [PATCH] Unbreak unicode.t with newer Catalyst versions

>From Catalyst-5.90079_001 Changes:

- !!! UTF-8 is now the default encoding (there used to be none...).
  You can disable this if you need to with MyApp->config(encoding =>
  undef) if it causes you trouble.

This breaks unicode.t tests 7-8. Explicitly unset the encoding
as a fix/workaround.

Bug-Debian: https://bugs.debian.org/791520
---
 t/lib/MojoMojoTestSchema.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/t/lib/MojoMojoTestSchema.pm b/t/lib/MojoMojoTestSchema.pm
index 785061f..b0b53a4 100644
--- a/t/lib/MojoMojoTestSchema.pm
+++ b/t/lib/MojoMojoTestSchema.pm
@@ -124,6 +124,7 @@ sub init_schema {
 view_allowed => 1,
 attachment_allowed   => 0,
 },
+'encoding' => undef,
 'View::Email' => { sender => { mailer => 'Test' } },
 'system_mail' => 'admin@localhost',
 };
-- 
2.1.4

Processed: mayavi2: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798166 798168 798167 798165
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798169

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

Processed: odin: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798167 798169 798168 798166 798165
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798170

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

Processed: pcl: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798167 798169 798170 798168 798166 798165
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 798171

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

Bug#798169: mayavi2: depends on vtk 5

[Julien Cristau]

Source: mayavi2
Version: 4.3.1-4.1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#798170: odin: depends on vtk 5

[Julien Cristau]

Source: odin
Version: 1.8.8-1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#798171: pcl: depends on vtk 5

[Julien Cristau]

Source: pcl
Version: 1.7.2-7
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Riley Baird]

On Sun, 06 Sep 2015 13:37:44 +0200
Niels Thykier  wrote:

> On Wed, 26 Aug 2015 07:11:14 +1000 Riley Baird
>  wrote:
> > On Tue, 25 Aug 2015 11:54:00 -0400
> > Eric Dorland  wrote:
> > 
> > > * Riley Baird (bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch) wrote:
> > > > This is listed in the FTP master's cruft report, so if I'm correct, it
> > > > shouldn't be necessary to request a removal from unstable.
> > > 
> > > Yeah and you have the right conflicts/replaces. I'm surprised it's
> > > complaining about this.
> > 
> > No, at the moment, it is possible to simultaneously install these
> > conflicting packages because someone made a NMU just before or after you
> > uploaded my package, but they didn't add the hyphen between "libassa"
> > and "3", so now we have libassa3.5-5v5 and libassa-3.5-5v5.
> What is the status on adding these Conflicts/Replaces?  This bug will
> soon be the only thing blocking libassa's transition to testing.

We don't need to add any more Conflicts/Replaces.

libassa3.5-5v5 and libassa-3.5-5v5 both only exist in unstable at the
moment. They come from different versions of the same source package.
Only libassa-3.5-5v5 will make it into testing. For a person running
testing, it will be impossible to have the problem which Ralf described.


pgpVHi1Vc_vpd.pgp
Description: PGP signature

Processed: Re: Bug#794932: missing license in debian/copyright

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.1.0-6.1
Bug #794932 [libcoyotl] missing license in debian/copyright
There is no source info for the package 'libcoyotl' at version '3.1.0-6.1' with 
architecture ''
Unable to make a source version for version '3.1.0-6.1'
Ignoring request to alter found versions of bug #794932 to the same values 
previously set

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

Bug#794932: missing license in debian/copyright

[Julien Cristau]

Control: found -1 3.1.0-6.1

On Sat, Aug  8, 2015 at 10:27:34 +0200, Thorsten Alteholz wrote:

> Package: libcoyotl
> Version: 3.1.0-6.1
> Severity: serious
> User: alteh...@debian.org
> Usertags: ftp
> X-Debbugs-CC: ftpmas...@ftp-master.debian.org
> thanks
> 
> Dear Maintainer,
> 
> please add the missing licenses of:
>  libcoyotl-3.1.0/libcoyotl/mwc1038.h
>  libcoyotl-3.1.0/test/test_maze.cpp
> to debian/copyright.
> According to the file headers you can also add ", or (at your option) any
> later version." again to your GPL-2 license block
> 
This is not a change introduced in 3.1.0-6.1.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#798177: marked as done ("Use default paths for lease files" breaks dhcpd)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 17:34:13 +
with message-id 
and subject line Bug#798177: fixed in isc-dhcp 4.3.3-3
has caused the Debian Bug report #798177,
regarding "Use default paths for lease files" breaks dhcpd
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.)


-- 
798177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: isc-dhcp-server
Version: 4.3.3-2
Severity: important

Hi,

The changelog for "isc-dhcp (4.3.3-2) unstable" says:

"* Use default paths for lease files."

I don't know what the actual change was here, but the result is that dhcpd
expects the lease file to live in /var/db/dhcpd.leases, which is not where the
lease file was before and is not policy compliant. Policy aside, it breaks the
startup, since the init script still touches /var/lib/dhcp/dhcpd.leases.

Note:

# grep leases /etc/init.d/isc-dhcp-server 
touch /var/lib/dhcp/dhcpd.leases

# strings $(which dhcpd)|grep -F .leases
/var/db/dhcpd6.leases
/var/db/dhcpd.leases

The change in git simply removes the configure options for --with-srv and
--with-cli lease, noting that it fixes bug 758882. I don't see how that will
fix r/w files in /var, since the default lease files are still in /var.

Please investigate and update the change. The server lease file was in the
right place, the client one might need to be put somewhere else, but right now
the fix breaks more than it solves.

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

Kernel: Linux 4.1.6-ruru0 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.57
ii  debianutils4.5.1
ii  libc6  2.19-19
ii  libdns-export100   1:9.9.5.dfsg-12
ii  libisc-export951:9.9.5.dfsg-12
ii  lsb-base   4.1+Debian14
ii  policycoreutils2.3-1

Versions of packages isc-dhcp-server recommends:
ii  isc-dhcp-common  4.3.3-2

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed [not included]
/etc/logcheck/ignore.d.server/isc-dhcp-server [Errno 13] Permission denied: 
u'/etc/logcheck/ignore.d.server/isc-dhcp-server'

-- debconf information:
* isc-dhcp-server/interfaces:
  isc-dhcp-server/config_warn:


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: isc-dhcp
Source-Version: 4.3.3-3

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated isc-dhcp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Sep 2015 16:47:39 +
Source: isc-dhcp
Binary: isc-dhcp-server isc-dhcp-dbg isc-dhcp-server-ldap isc-dhcp-common 
isc-dhcp-dev isc-dhcp-client isc-dhcp-client-udeb isc-dhcp-relay
Architecture: source
Version: 4.3.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian ISC DHCP maintainers 
Changed-By: Michael Gilbert 
Description:
 isc-dhcp-client - DHCP client for automatically obtaining an IP address
 isc-dhcp-client-udeb - ISC DHCP Client for debian-installer (udeb)
 isc-dhcp-common - common files used by all of the isc-dhcp packages
 isc-dhcp-dbg - ISC DHCP server for automatic IP address assignment (debuging 
sym
 isc-dhcp-dev - API for accessing and modifying the DHCP server and client state
 isc-dhcp-relay - ISC DHCP relay daemon
 isc-dhcp-server - ISC DHCP server for automatic IP address assignment
 isc-dhcp-server-ldap - DHCP server that uses LDAP as its backend
Closes: 798177
Changes:
 isc-dhcp (4.3.3-3) unstable; 

Bug#797095: amd64: netboot 2015-04-22, 2015-06-04, 2015-08-13 fail, wheezy succeeds

[Douglas Guptill]

Dear Maintainer,

On Thu, 27 Aug 2015 15:57:03 -0300 Douglas Guptill  
wrote:
> Package: debian-installer
> Version: 20150422+deb8u1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> summary
> ---
> amd64 netboot wheezy  2015-01-05 works
> amd64 netboot jessie  2015-04-22 fails
> amd64 netboot jessie  2015-06-04 fails
> amd64 netboot stretch 2015-08-13 fails

Wrong.  my bad.  no bug.

Details
---

Wanting an automatic, unattended install, it has been my practice
(through squeeze and wheezy) to _replace_ the 'default' file after
installing netboot.tar.gz

  srv/tftp/debian-installer/amd64/pxelinux.cfg/default

When looking for reasons for the boot failure, I forgot to consider
that replacement.

Using a 'default' file written according to the specs for syslinux
version 6.03, I get an automated, unattended, preseeded install.

Sorry for the noise.

Regards,
Douglas.

Bug#798190: reads nonexistant dir, segfaults Kodi on startup

[Bálint Réczey]

Hi Steinar,

2015-09-06 16:35 GMT+02:00 Steinar H. Gunderson :
> Package: libcec3
> Version: 3.0.1+dfsg2-4
> Severity: grave
>
> Hi,
>
> Recently, Kodi has started segfaulting on startup, pointing to libcec3.
> A backtrace reads:
>
> #0  0x7fffecf55789 in __readdir (dirp=dirp@entry=0x0) at 
> ../sysdeps/posix/readdir.c:44
> #1  0x7fffc81d8b74 in PLATFORM::CDRMEdidParser::GetPhysicalAddress 
> (this=this@entry=0x7fffc29e8550)
> at 
> /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/platform/drm/drm-edid.cpp:54
> #2  0x7fffc81e4c0e in 
> CEC::CUSBCECAdapterCommunication::GetPhysicalAddress (this=0x7fffb4000f50)
> at 
> /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/adapter/Pulse-Eight/USBCECAdapterCommunication.cpp:697
> #3  0x7fffc81baaec in CEC::CCECClient::AutodetectPhysicalAddress 
> (this=0x1a7cab0)
> at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:1224
> #4  0x7fffc81b884c in CEC::CCECClient::SetPhysicalAddress 
> (this=0x1a7cab0, configuration=...)
> at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:236
> #5  0x7fffc81bcdcb in CEC::CCECClient::OnRegister (this=0x1a7cab0) at 
> /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECClient.cpp:138
> #6  0x7fffc81cd4d2 in CEC::CCECProcessor::RegisterClient (this=0x1a76840, 
> client=std::shared_ptr (count 4, weak 0) 0x1a7cab0)
> at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/CECProcessor.cpp:899
> #7  0x7fffc81d3e7a in CEC::CLibCEC::Open (this=0x1a78d10, 
> strPort=, iTimeoutMs=)
> at /home/sesse/nmu/libcec-3.0.1+dfsg2/src/libcec/LibCEC.cpp:91
> #8  0x010cdd39 in 
> PERIPHERALS::CPeripheralCecAdapter::OpenConnection() ()
> #9  0x010d0434 in PERIPHERALS::CPeripheralCecAdapter::Process() ()
> #10 0x0113f56f in CThread::Action() ()
> #11 0x0113f832 in CThread::staticThread(void*) ()
> #12 0x755ad0a4 in start_thread (arg=0x7fffc29e9700) at 
> pthread_create.c:309
> #13 0x7fffecf8807d in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
>
> It would seem libcec3 unconditionally assumes /sys/class/drm exists
> (it does not on my system using the proprietary NVIDIA driver, since
> that driver doesn't use drm), and then segfaults when it doesn't.
>
> Could you please add a check for the NULL value?
Thank you for the detailed bug report.
Could you please test the fix built here?:
http://debomatic-amd64.debian.net/distribution#unstable/libcec/3.0.1+dfsg2-5

Thanks,
Balint

Processed: Move boost1.54 bugs to boost-defaults

[Debian Bug Tracking System]

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

> reassign 735353 boost-defaults
Bug #735353 [src:boost1.54] Sourceless file
Bug reassigned from package 'src:boost1.54' to 'boost-defaults'.
Ignoring request to alter found versions of bug #735353 to the same values 
previously set
Ignoring request to alter fixed versions of bug #735353 to the same values 
previously set
> reassign 631079 boost-defaults
Bug #631079 [boost1.54] Please build boost.python for pythonX-dbg too
Bug reassigned from package 'boost1.54' to 'boost-defaults'.
No longer marked as found in versions 1.54.0-2, 1.54.0, and 1.54.0.1.
Ignoring request to alter fixed versions of bug #631079 to the same values 
previously set
> reassign 722758 boost-defaults
Bug #722758 [boost1.54] boost1.54 link with -L/usr/lib
Bug reassigned from package 'boost1.54' to 'boost-defaults'.
No longer marked as found in versions 1.54.0-2.
Ignoring request to alter fixed versions of bug #722758 to the same values 
previously set
> reassign 734504 boost-defaults
Bug #734504 [libboost-python1.54-dev] libboost-python1.54-dev: shared library 
not linked against python
Bug reassigned from package 'libboost-python1.54-dev' to 'boost-defaults'.
No longer marked as found in versions boost1.54/1.54.0-4.
Ignoring request to alter fixed versions of bug #734504 to the same values 
previously set
> reassign 751880 boost-defaults
Bug #751880 [src:boost1.54] boost1.54: outdated embedded data copy: unicode-data
Bug reassigned from package 'src:boost1.54' to 'boost-defaults'.
Ignoring request to alter found versions of bug #751880 to the same values 
previously set
Ignoring request to alter fixed versions of bug #751880 to the same values 
previously set
> reassign 719484 boost-defaults
Bug #719484 [src:boost1.54] boost1.54: FTBFS: assertion fail in bjam, possibly 
invalid/unportable alignment assumptions
Bug reassigned from package 'src:boost1.54' to 'boost-defaults'.
No longer marked as found in versions boost1.54/1.54.0-2.
Ignoring request to alter fixed versions of bug #719484 to the same values 
previously set
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
631079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631079
719484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719484
722758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722758
734504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734504
735353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735353
751880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#798190: reads nonexistant dir, segfaults Kodi on startup

[Steinar H. Gunderson]

On Sun, Sep 06, 2015 at 07:48:24PM +0200, Bálint Réczey wrote:
> Thank you for the detailed bug report.
> Could you please test the fix built here?:
> http://debomatic-amd64.debian.net/distribution#unstable/libcec/3.0.1+dfsg2-5

Uhm, I must understand I couldn't figure that UI out at all. Do you have a
patch?

FWIW, I tried just returning immediately if the pointer from opendir is NULL,
and that seems to have worked correctly. If your fix is anything like that,
it should be fine.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

Bug#795590: postgresql-multicorn: FTBFS: TypeError: an integer is required

[Christoph Berg]

Control: severity -1 important
Control: tag -1 upstream

Re: Chris Lamb 2015-08-15 
<1439646814.2190529.356965353.0608b...@webmail.messagingengine.com>
> postgresql-multicorn fails to build from source on unstable/amd64:
> 
>   [..]
> 
>   self = 
>   fd = 'lipsum/a_foo/1'
>   
>   def write(self, fd=None):
>   if fd is None:
>   fd = self.open(False)
>   >   os.ftruncate(fd, 0)
>   E   TypeError: an integer is required

This is actually a failure in the testsuite, thanks for spotting.
Until this is resolved upstream, we are ignoring the test results. A
"fixed" package was just uploaded to unstable, hence downgrading the
severity.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/

Processed: Re: Bug#795590: postgresql-multicorn: FTBFS: TypeError: an integer is required

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #795590 [src:postgresql-multicorn] postgresql-multicorn: FTBFS: TypeError: 
an integer is required
Severity set to 'important' from 'serious'
> tag -1 upstream
Bug #795590 [src:postgresql-multicorn] postgresql-multicorn: FTBFS: TypeError: 
an integer is required
Added tag(s) upstream.

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

Bug#791232: openvrml: library transition may be needed when GCC 5 is the default

[tony mancill]

On Wed, 12 Aug 2015 21:02:55 +0200 Mehdi Dogguy  wrote:
> Control: tags -1 + confirmed
> Control: severity -1 serious
> 
> On Fri, Jul 03, 2015 at 01:13:22PM +, Matthias Klose  
> wrote:
> >  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
> >library API, and are used by the reverse dependencies of the
> >library.
> > 
> 
> There are some std::string exposed in the public API.
> 
> >  - If there are no reverse dependencies, it should be the package
> >maintainers decision if a transition is needed.  However this might
> >break software which is not in the Debian archive, and built
> >against these packages.
> > 
> 
> It seems that there are no reverse dependencies.

Dear openvrml maintainers:

I have started on an NMU to address the Java8 FTBFS bugs, but haven't
yet uploaded it because of the ABI transition bug.  These are the
changes so far for the NMU:

> openvrml (0.18.9-7.1) UNRELEASED; urgency=medium
> 
>   * Non-maintainer upload.
>   * Package is listed as LowNMU.
>   * Address FTBFS with OpenJDK 8. (Closes: #748045, #760928)
> Thanks to Emmanuel Bourg for the patches.
> - Updates cflags and cxxflags to include JAVA_HOME/include/linux
> - Adds 0004-java8-compatibility.patch.
> 
>  -- tony mancill   Fri, 31 Jul 2015 20:32:24 -0700

Do you have an opinion about whether there are 3rd party packages using
libopenvrml9 as a dependency, and thus whether a 'v5' transitional
library package is needed?

Thank you,
tony



signature.asc
Description: OpenPGP digital signature

Processed: Fixes Pending

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #793885 [minc] minc: FTBFS with netcdf in experimental due to test failure
Added tag(s) pending.

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

Bug#793885: Fixes Pending

[Steve M. Robbins]

Control: tags -1 + pending

To update my progress: the packaging vcs [1] (slightly reorganized) has new 
upstream development branch code that builds properly with the new NetCDF.  I 
am awaiting a new upstream release (in the coming week) to set the proper 
version for minc-tools.


[1] http://anonscm.debian.org/viewvc/debian-med/trunk/packages/minc/


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

Bug#798197: sdformat build-depends on libignition-math2-dev which is not available on armel and mips.

[Peter Green]

Package: sdformat
Severity: serious
x-debbugs-cc: ignition-ma...@packages.debian.org

sdformat build-depends on libignition-math2-dev. This is provided by the 
source package ignition-math2 which has never built succesfully on armel 
or mips (it is failing with a test failure, I wonder if it is a race 
condition triggered by slow systems)


sdformat however has built on armel and mips in the past and hence has 
out of date binaries for those architectures and will not migrate to 
testing until that is sorted out. There are three possible soloutions to 
this (in decreasing order of preference). There are thee potential 
soloutions for this (in descending order of preference).


1: fix ignition-math2 so it builds on armel and mips.
2: make your package build without libignition-math2-dev on armel and mips.
3: declare that it is not reasonable to support your package on armel 
and mips and file a removal request with the ftpmasters.

Processed: severity of 798178 is important

[Debian Bug Tracking System]

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

> severity 798178 important
Bug #798178 [warzone2100] warzone2100: Major regressions compared to squeeze
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
798178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#792137: [einstein] No Longer Runs with Latest Qt/KDE5 Upgrades

[Felix Geyer]

Hi,

On Sun, 12 Jul 2015 00:38:28 +0300 David Baron  wrote:
> Package: einstein
> Version: 2.0.dfsg.2-9
> Severity: grave
> 
> --- Please enter the report below this line. ---
> Get the following when run from a terminal: 
> ~$ einstein
> terminate called after throwing an instance of 'std::logic_error'
>   what():  basic_string::_S_construct null not valid
> Aborted
> 
> Worked fine yesterday.
> Many KDE-desktop packages have been upgraded

Was this maybe an issue related to the GCC 5 transition?
Does it still crash with an up-to-date unstable?
It works fine for me.

Cheers,
Felix

Bug#797992: marked as done (octave: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 16:00:23 +
with message-id 
and subject line Bug#797992: fixed in octave 4.0.0-4
has caused the Debian Bug report #797992,
regarding octave: ABI transition needed for libstdc++ v5
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.)


-- 
797992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave
Version: 4.0.0-3
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
Control: block -1 by 791067

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of octave, std::string appears in functions in
installed headers, so it seems very likely that a transition is needed.
The transition normally consists of renaming the affected library
packages, adding a v5 suffix (liboctave3v5). The actual SONAME should
not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, please avoid doing this unless the new upstream version
is extremely low-risk: this transition has been going on for 1 month
already, and anything that drags it out further is bad for Debian.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the C++ library build-dependencies of octave, it is
waiting for hdf5 (#791067) but everything else seems to be ready.
When hdf5 starts its transition, please give octave a versioned
build-dependency on the version of libhdf5-dev corresponding to
the rename.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 4.0.0-4

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

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

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated octave package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Sep 2015 00:03:52 +0200
Source: octave
Binary: octave octave-dbg octave-common octave-doc octave-htmldoc octave-info 
liboctave3v5 liboctave-dev
Architecture: source amd64 all
Version: 4.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Description:
 liboctave-dev - Development files for the GNU Octave language
 liboctave3v5 - Shared libraries of the GNU Octave language
 octave - GNU Octave language for numerical computations
 octave-common - architecture-independent files for octave
 octave-dbg - Debug symbols for octave
 octave-doc - PDF documentation on the GNU Octave language
 octave-htmldoc - 

Bug#797917: Actually this bug makes clang not so useful

[Danny Edel]

On 04/09/15 11:23, Gianfranco Costamagna wrote:
> 
> I guess clang is not useful for cxx11 projects until llvm folks finds
> a way to make it use the new ABI.
> 

Hi everyone,

I just want to make clear that this is *not* specific to c++11 projects.
Even if you don't use any c++11 features, clang can't link against the
library.

Try compiling my example code (which is valid c++98) with

$ g++ -std=c++98 -o options options.cpp -lboost_program_options
$ clang++ -std=c++98 -o options options.cpp -lboost_program_options

The results are the same - works on gcc, fails to link on clang on sid,
while both commands used to work on stable.

If I understand the consequences of this failure right, this will
severely impact the usefulness of clang++, since it will start failing
to link against *any* c++ library compiled by recent g++, breaking
unchanged and valid user code - be it c++11, c++03 or c++98.

I don't think this is that much of an issue on sid - after all, it's
called "unstable" for a reason - but it might be a showstopper for
stable, if clang++ is to be an alternative for g++.

- Danny

Processed: Re: wmbattery does not update display after launching

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #798136 [wmbattery] wmbattery does not update display after launching
Added tag(s) unreproducible and moreinfo.
> severity -1 important
Bug #798136 [wmbattery] wmbattery does not update display after launching
Severity set to 'important' from 'grave'

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

Bug#798136: wmbattery does not update display after launching

[Doug Torrance]

Control: tags -1 unreproducible moreinfo
Control: severity -1 important

On Sat, 05 Sep 2015 23:35:22 -0400 Norman Ramsey  wrote:
> After a recent upgrade from wheezy to jessie, wmbattery no longer
> tracks battery information in real time. The time remaining and
> charge percentage are accurate when launched, but they don't change.
>
> wmbattery *does* notice a power-loss or power-acquisition event,
> and when it responds to these, it also updates percentage charge and
> time remaining. But otherwise they do not track.
>
> On the command line, acpi reports good information, and gkrellm's
> battery monitor tracks changes to charge percentage in real time.
>
> I marked the bug 'grave' since the only purpose of the package is to
> monitor battery status in real time, and if the status is not updated,
> the package is not fulfilling its intended purpose.
>
> I mostly run a standard jessie installation, but just in case I did
> install the latest wmbattery from stretch. Still not updating.

Thanks for your report!

I'm not able to reproduce this problem, so I'm downgrading the bug to
important.  Could you provide some more information?

In particular, could you run "upower --monitor-detail" from the command
line?  It should periodically print out a status report with information
about your battery.  If it doesn't, then this is likely an issue with
upower.  (Note that wmbattery switched to using upower in 2.42, right
after the version that was in wheezy.)

Thanks!
Doug Torrance

Processed: Re: [pkg-dhcp-devel] Bug#798177: Temporary workaround

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #798177 [isc-dhcp-server] "Use default paths for lease files" breaks dhcpd
Severity set to 'serious' from 'important'

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

Bug#567418: marked as done (dict-jargon: Use w3m instead of elinks to build jargon.txt)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 15:34:55 +
with message-id 
and subject line Bug#567418: fixed in dict-jargon 4.4.7-3
has caused the Debian Bug report #567418,
regarding dict-jargon: Use w3m instead of elinks to build jargon.txt
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.)


-- 
567418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dict-jargon
Version: 4.4.7-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lucid ubuntu-patch



*** /tmp/tmpehp15g
In Ubuntu, we've applied the attached patch to achieve the following:

  * Replace elinks with w3m.

We thought you might be interested in doing the same. 

We're trying to replace elinks with w3m wherever possible.

-- System Information:
Debian Release: squeeze/sid
  APT prefers lucid-updates
  APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-25-server (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/control'
--- debian/control  2009-06-20 19:03:13 +
+++ debian/control  2010-01-28 23:15:59 +
@@ -1,9 +1,10 @@
 Section: text
 Priority: optional
 Build-Depends: quilt, debhelper (>= 7)
-Build-Depends-Indep: xmlto, elinks-lite, dictfmt, dictzip
+Build-Depends-Indep: xmlto, w3m, dictfmt, dictzip
 Standards-Version: 3.8.2
 Homepage: http://catb.org/jargon/
 

=== modified file 'debian/jargon2dict.sh'
--- debian/jargon2dict.sh   2009-01-29 21:47:29 +
+++ debian/jargon2dict.sh   2010-01-28 23:00:33 +
@@ -42,8 +42,8 @@
   sed -i "s/\o264/'/" jargon-web.html
 
 echo " [+] dumping plain-text version"
-  ELINKSOPTS="-dump -dump-width 79 -no-numbering 1 -no-references 1"
-  elinks $ELINKSOPTS jargon-web.html > jargon.txt
+  W3MOPTS="-dump"
+  w3m $W3MOPTS jargon-web.html > jargon.txt
 
 
 extract() { # usage: extract 'first string' 'second string'

--- End Message ---
--- Begin Message ---
Source: dict-jargon
Source-Version: 4.4.7-3

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

Debian distribution maintenance software
pp.
Ruben Molina  (supplier of updated dict-jargon 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 Sep 2015 22:38:38 -0400
Source: dict-jargon
Binary: dict-jargon
Architecture: source all
Version: 4.4.7-3
Distribution: unstable
Urgency: medium
Maintainer: Ruben Molina 
Changed-By: Ruben Molina 
Description:
 dict-jargon - dict package for The Jargon Lexicon
Closes: 567418 581692 587744 587745 792709
Changes:
 dict-jargon (4.4.7-3) unstable; urgency=medium
 .
   * Switch to source format "3.0 (quilt)" and dh7 tiny rules
   * Remove quilt from Build-Depends.
   * Switch to machine-readable format for debian/copyright
   * Bump Standards-Version to 3.9.6 (no changes)
   * Bump compat level to 9 and update debhelper version on Build-Depends.
   * Replace elinks with w3m (Closes: #567418).
 Patch provided by: Mathias Gug 
   * Replace timestamps with the last debian/changelog entry timestamp
 before calling dictzip and remove timestamps in call to dictfmt to
 make the package build reproducibly (Closes: #792709).
 Patch provided by: Dhole 
   * Add a new patch fixing typos and a missing sense number in a
 reference (Closes: #581692, #587744, #587745).
 Patches provided by: Oohara Yuuma 
   * Fix command-with-path-in-maintainer-script in debian/post*
   * Add debian/README.source
   * Update maintainer email
Checksums-Sha1:
 a033c560d4c85a088765efb006d3a10e860ea077 1764 dict-jargon_4.4.7-3.dsc
 e8033166b50eb33d8df1bd9fb8973911b99ce9c6 9800 dict-jargon_4.4.7-3.debian.tar.xz
 7edb1da2391f2008c7af79346480e60eaefc2709 613086 

Bug#798188: wmacpi: FTBFS when rebuild against libdockapp3

[Doug Torrance]

Control: tags -1 pending

On Sun, 06 Sep 2015 16:14:17 +0200 Niels Thykier  wrote:
> The wmacpi package FTBFS when rebuild against libdockapp3.
>
> """
> gcc -MM -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -W -g -ansi wmacpi.c > wmacpi.d
> gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-O2 -Wall -W -g -ansi -D_FORTIFY_SOURCE=2 -c -o wmacpi.o wmacpi.c
> wmacpi.c:22:21: fatal error: dockapp.h: No such file or directory
> compilation terminated.
> make[1]: *** [wmacpi.o] Error 1
> """

Thanks for your report!

I've prepared a new version of the wmacpi package which fixes this
issue.  It should be uploaded soon, once my sponsor takes a look at it.

Processed: Re: wmacpi: FTBFS when rebuild against libdockapp3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #798188 [wmacpi] wmacpi: FTBFS when rebuild against libdockapp3
Added tag(s) pending.

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

Bug#796950: marked as done (NameError: global name 're' is not defined)

[Debian Bug Tracking System]

Your message dated Sun, 06 Sep 2015 15:38:44 +
with message-id 
and subject line Bug#796950: fixed in obnam 1.16-1
has caused the Debian Bug report #796950,
regarding NameError: global name 're' is not defined
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.)


-- 
796950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obnam
Version: 1.15-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I was attempting to run obnam backup and received the following python stack
trace.

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 189, in _run
self.process_args(args)
  File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 206, in
process_args
self.hooks.call('config-loaded')
  File "/usr/lib/python2.7/dist-packages/obnamlib/hooks.py", line 188, in call
self.hooks[name].call_callbacks(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/obnamlib/hooks.py", line 65, in
call_callbacks
callback(*args, **kwargs)
  File "/usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py", line 57, in
config_loaded
self.compile_exclusion_patterns()
  File "/usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py", line 81, in
compile_exclusion_patterns
self.compile_regexps(regexps, self.pathname_excluder.exclude_regexp)
  File "/usr/lib/python2.7/dist-
packages/obnamlib/plugins/exclude_pathnames_plugin.py", line 97, in
compile_regexps
except re.error as e:
NameError: global name 're' is not defined

Looking at exclude_pathnames_plugin.py it does call "except re.error" and I
couldn't find a corresponding import re. So something seems wrong.

Attached are the modifications I made to exclude_pathnames_plugin in order to
get it to work.
--- /tmp/exclude_pathnames_plugin.py	2015-08-25 22:27:42.290914865 -0700
+++ /usr/lib/python2.7/dist-packages/obnamlib/plugins/exclude_pathnames_plugin.py	2015-08-25 22:27:13.923549566 -0700
@@ -18,8 +18,9 @@
 import logging
 import os
 import stat
 import time
+import re
 
 import obnamlib
 
 
@@ -93,11 +94,11 @@
 logging.debug('Regular expression: %s', regexp)
 try:
 compiler(regexp)
 except re.error as e:
-msg = ('error compiling regular expression "%s": %s' % (x, e))
+msg = ('error compiling regular expression "%s": %s' % (regexp, e))
 logging.error(msg)
-self.progress.error(msg)
+#self.progress.error(msg)
 
 def read_patterns_from_files(self, filenames):
 patterns = []
 for filename in filenames:
--- End Message ---
--- Begin Message ---
Source: obnam
Source-Version: 1.16-1

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

Debian distribution maintenance software
pp.
Lars Wirzenius  (supplier of updated obnam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 Sep 2015 16:25:28 +0300
Source: obnam
Binary: obnam
Architecture: amd64 i386 source
Version: 1.16-1
Distribution: unstable
Urgency: medium
Maintainer: Lars Wirzenius 
Changed-By: Lars Wirzenius 
Closes: 796139 796950
Description: 
 obnam  - online and disk-based backup application
Changes:
 obnam (1.16-1) unstable; urgency=medium
 .
   * New upstream release.
 * Fix "NameError: global name 're' is not defined" (Closes: #796950)
 * Fix "NameError: global name 'netloc' is not defined" (Closes: #796139)
Checksums-Sha1: 
 bf8a2e7aae4f40b518c82c81c8e577757abdec49 169066 obnam_1.16-1_amd64.deb
 b68aa311e62cb2c8e5d52e644f0d15fcae610ebf 169246 obnam_1.16-1_i386.deb
 75a1dfb0c7d3a36487d8e33d96796a7cf4290487 2020 obnam_1.16-1.dsc
 aeadc82d346c7d39fbc1b1b7555eabafac84b674 276120 obnam_1.16.orig.tar.xz
 11c645d941b1ad1ae034560c71957478e79f4be8 6264 obnam_1.16-1.debian.tar.xz
Checksums-Sha256: 
 

Processed: crtmpserver: Please drop hard-coded dependency on libtinyxml2.6.2

[Debian Bug Tracking System]

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

> Severity 794724 grave
Bug #794724 [crtmpserver] crtmpserver: Please drop hard-coded dependency on 
libtinyxml2.6.2
Severity set to 'grave' from 'important'
> tags 794724 +stretch sid
Bug #794724 [crtmpserver] crtmpserver: Please drop hard-coded dependency on 
libtinyxml2.6.2
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems