Bug#879579: offlineimap: crashes on startup: getfolder() got an unexpected keyword argument 'decode'

2017-10-22 Thread Paul Wise
Package: offlineimap
Version: 7.1.3+dfsg1-1
Severity: serious
Justification: crash
Usertags: crash

Since the recent upgrade from 7.1.2+dfsg1-2 to 7.1.3+dfsg1-1,
offlineimap crashes on startup with an error in the getfolder()
function and is thus unusable.

$ offlineimap 
OfflineIMAP 7.1.3
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v2.57 (system), Python v2.7.13, OpenSSL 1.1.0f  25 May 2017
Account sync :
 *** Processing account 
 Establishing connection to :993 (Remote-)
 ERROR: While attempting to sync account ''
  getfolder() got an unexpected keyword argument 'decode'
 *** Finished account '' in 0:04
ERROR: Exceptions occurred during the run!
ERROR: While attempting to sync account ''
  getfolder() got an unexpected keyword argument 'decode'

Traceback:
  File "/usr/share/offlineimap/offlineimap/accounts.py", line 283, in syncrunner
self.__sync()
  File "/usr/share/offlineimap/offlineimap/accounts.py", line 362, in __sync
remoterepos.sync_folder_structure(localrepos, statusrepos)
  File "/usr/share/offlineimap/offlineimap/repository/Base.py", line 245, in 
sync_folder_structure
tmp_remotefolder = remote_repo.getfolder(remote_name, decode=False)

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages offlineimap depends on:
ii  python   2.7.13-2
ii  python-imaplib2  2.57-1
ii  python-six   1.11.0-1

Versions of packages offlineimap recommends:
ii  python-socks  1.6.5-1

Versions of packages offlineimap suggests:
pn  python-kerberos  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Processed: Re: cjs: Please don't use mozjs24

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 879575 https://github.com/linuxmint/cjs/issues/52
Bug #879575 [src:cjs] cjs: Please don't use mozjs24
Set Bug forwarded-to-address to 'https://github.com/linuxmint/cjs/issues/52'.
>
End of message, stopping processing here.

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



Bug#879576: mozjs24: Please keep out of testing/buster

2017-10-22 Thread Jeremy Bicha
Source: mozjs24
Version: 24.2.0-6
Severity: serious
Tags: buster sid

mozjs24 is the SpiderMonkey JavaScript engine from Firefox ESR 24.
Firefox ESR 24 has not been supported by Mozilla for 3 years. We
should not ship Debian 10 "Buster" with mozjs24.

There are only 2 rdepends for mozjs24 left in Debian unstable: cjs and edbrowse.
https://bugs.debian.org/875706
https://bugs.debian.org/879575

mozjs52, a replacement for mozjs24, is now in Debian.

Thanks,
Jeremy Bicha



Processed: Re: duktape: please ship a duktape library

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #875706 [edbrowse] edbrowse: please package new upstream version
Severity set to 'serious' from 'wishlist'

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



Processed: Re: duktape: please ship a duktape library

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #872040 [src:duktape] duktape: please ship a duktape library
Severity set to 'serious' from 'wishlist'

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



Bug#879575: cjs: Please don't use mozjs24

2017-10-22 Thread Jeremy Bicha
Source: cjs
Version: 3.2.0-3
Severity: serious
Tags: sid buster

mozjs24 is the SpiderMonkey JavaScript engine from Firefox ESR 24.
Firefox ESR 24 has not been supported by Mozilla for 3 years. We
should not ship Debian 10 "Buster" with mozjs24.

There are only 2 rdepends for mozjs24 in Debian: cjs and edbrowse.
edbrowse is already ported upstream but there is a packaging issue.
See https://bugs.debian.org/875706 That means that cjs is basically
the only reason mozjs24 is still in Debian.

A replacement for mozjs24, mozjs52 is now in Debian. cjs upstream has
not been ported to mozjs52 yet, but it has been ported to mozjs38.
mozjs38 is not in Debian but perhaps you could apply the
debian/copyright from mozjs52 to the WIP mozjs38 branch to get it
through the Debian NEW queue.

https://anonscm.debian.org/git/pkg-gnome/mozjs38.git
https://anonscm.debian.org/git/pkg-gnome/mozjs52.git

However, mozjs38 hasn't been supported by Mozilla since June 2016 so
that's not ideal either.

Thanks,
Jeremy Bicha



Bug#877225: jblas FTBFS with multiarch libatlas-base-dev

2017-10-22 Thread Markus Koschany
Control: owner -1 !

I am working on this bug and jblas and I intend to package the latest
upstream release.



signature.asc
Description: OpenPGP digital signature


Processed: Re: jblas FTBFS with multiarch libatlas-base-dev

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> owner -1 !
Bug #877225 [src:jblas] jblas FTBFS with multiarch libatlas-base-dev
Owner recorded as Markus Koschany .

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



Bug#867376: Processed: Re: Bug#867376 closed by Alexander GQ Gerasiov <g...@debian.org> (Bug#867376: fixed in uncrustify 0.65+git20170831+dfsg1-1)

2017-10-22 Thread Julien Cristau
On Sun, Oct 22, 2017 at 12:54:14 +0300, Alexander Gerasiov wrote:

> In generally I agree with you, that changelog should be meaningful.
> But in this case you're wrong (from my point of view).
> 
> We have sigfault in the app.
> User reports "%appname segfault when %something"
> I look through the code and see pointer dereference, so I create commit
> not with "Fix sigfault", but with "Do some checks on pointer
> dereference when ... This should fix #issuenumber".
> 
> Or may be you mean, that I should write
> "New upstream release. Fixes disk overflow on some archs. (Closes:
> #number)" There is some good point in this, I agree, but still no
> reason to reopen the bug, I think. =)
> 
Yes, that's what I meant.  Thanks.

Cheers,
Julien



Bug#879478: [debhelper-devel] Bug#879478: debhelper: dh_testroot regression: relies on debian/control

2017-10-22 Thread Cyril Brulebois
Hi,

Niels Thykier  (2017-10-22):
> Unfortunately, I cannot even fix this by guarding it with a compat bump
> (because that will die as it cannot find debian/compat).  For now, I
> will have it issue a warning and continue (plus make some assumptions
> about what the d/control file would have contained).  But eventually, I
> will remove that fallback and that *cannot* happen with a compat bump.
> 
> For you, an easy fix appears be to re-arrange the lines:
> 
>   dh_testroot
>   @[ -d ../debian ] || { echo "directory '../debian' [...] }
> 
> Into:
> 
>   @[ -d ../debian ] || { echo "directory '../debian' [...] }
>   cd .. && dh_testroot
> 
> (Only occurs two places AFAICT in the Makefile).  This change would also
> be backwards compatible for you.

FYI (debian-boot@): I've checked after filing this bug report that daily
builds are broken… and that release builds are broken as well, so fixing
the issue by taking this proposed change should work for all use cases.

I've filed #879554 to make sure we don't forget about updating d-i
before debhelper gets updated again. I'll probably double check this
for the next buster alpha release.

> The scope of dh_testroot has changed and I have committed an update of
> the documentation of dh_testroot targeting 10.10.1.  Furthermore, I
> have added a note in debhelper.7 that all debhelper tools must be run
> from the unpacked source root (except where otherwise noted).

ACK.

Also: Thanks for the quick reply.


KiBi.


signature.asc
Description: PGP signature


Bug#879221: marked as done (dropbear-bin: hardcodes dependencies on shared libs)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 19:36:01 +
with message-id 
and subject line Bug#879221: fixed in dropbear 2017.75-3
has caused the Debian Bug report #879221,
regarding dropbear-bin: hardcodes dependencies on shared libs
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.)


-- 
879221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dropbear-bin
Version: 2017.75-2
Severity: serious

dropbear-bin has:

Depends: libtomcrypt0, libtommath1, ${misc:Depends}, ${shlibs:Depends}

A rebuild of dropbear against libtopcrypt1 (which bumped the SONAME)
causes it to have:

Depends: libtomcrypt0, libtommath1, libc6 (>= 2.15), libtomcrypt1, zlib1g (>= 
1:1.1.4)

Which is wrong. Please let shlibs do its job and drop the libtomcrypt
and libtommath hardcoded dependencies.

Emilio
--- End Message ---
--- Begin Message ---
Source: dropbear
Source-Version: 2017.75-3

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated dropbear 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, 22 Oct 2017 14:30:10 +0200
Source: dropbear
Binary: dropbear-bin dropbear-run dropbear-initramfs dropbear
Architecture: source amd64 all
Version: 2017.75-3
Distribution: unstable
Urgency: low
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Description:
 dropbear   - transitional dummy package for dropbear-{run,initramfs}
 dropbear-bin - lightweight SSH2 server and client - command line tools
 dropbear-initramfs - lightweight SSH2 server and client - initramfs integration
 dropbear-run - lightweight SSH2 server and client - startup scripts
Closes: 879221
Changes:
 dropbear (2017.75-3) unstable; urgency=low
 .
   * debian/control:
 + Remove hardcoding of libtomcryptX/libtommathY in dropbear-bin's Depends.
   (Closes: #879221.)
 + Bump Standards-Version to 4.1.1.  Changes:
   - Replace dropbear's Priority from extra to optional (inherited from
 source package paragraph).
Checksums-Sha1:
 8a88e33b864a9368ac66d72321f1b2620f4f436c 2170 dropbear_2017.75-3.dsc
 5d50124906574d05e83b04daae4f67ce1369443c 22324 dropbear_2017.75-3.debian.tar.xz
 3c968e5d97659c5a0fd6b27ba63bdd16436ebe1a 992140 
dropbear-bin-dbgsym_2017.75-3_amd64.deb
 438a3b37cdd4cb0c35544b2cdaa7e14465b12411 136020 
dropbear-bin_2017.75-3_amd64.deb
 2b198b740919037c969e792c335712cca030fc19 38164 
dropbear-initramfs_2017.75-3_all.deb
 12dfa71067d189504739b5be4301a5d82c1de275 35288 dropbear-run_2017.75-3_all.deb
 37be1f50278791157e7512fc4b8d2c55c8b098ee 33084 dropbear_2017.75-3_all.deb
 9a099505147ca0f6c05618143b6f8038e10841e5 6564 
dropbear_2017.75-3_amd64.buildinfo
Checksums-Sha256:
 70dd52041dc27e82c0ffec19fe31ec74061222f861a69c841c46ccb924ac3d5d 2170 
dropbear_2017.75-3.dsc
 56517d3d5535e34f4b120856800c84ec7ad51a4eb954ac8150637698d2bbd83b 22324 
dropbear_2017.75-3.debian.tar.xz
 b83680451b5184b879992f56cd054c6b810273076f07032b7e5eb9896584c003 992140 
dropbear-bin-dbgsym_2017.75-3_amd64.deb
 7178a4dda1ab70dbd1153ec55aa87fa0fcf0792d86b80d7743ac5b78588b9650 136020 
dropbear-bin_2017.75-3_amd64.deb
 968bf65c74002ec22c4728f2eae5c40f83a903dba7bcf64ba9bd8d6e68d63982 38164 
dropbear-initramfs_2017.75-3_all.deb
 6ce8f9d6bbcecf720071c46d16f38413a092a3b11158a3791889beac73f28c5d 35288 
dropbear-run_2017.75-3_all.deb
 6eeabab672069d19b3b0c371392137d34d9da7fbdd8215e7375ac1b634b252d2 33084 
dropbear_2017.75-3_all.deb
 5d7cb34b430d53fd5b8eaf0d3f8736b92f55de0617ea2ab5824261ff7068fe6f 6564 
dropbear_2017.75-3_amd64.buildinfo
Files:
 3ffd57eda684101663787a2e073dca63 2170 net optional dropbear_2017.75-3.dsc
 76ccebee4385457ce76793df874d9baa 22324 net optional 
dropbear_2017.75-3.debian.tar.xz
 270c993af4be6b382cf938fb4d178a78 992140 debug optional 
dropbear-bin-dbgsym_2017.75-3_amd64.deb
 1c8f83ea99f053cca7a750abf947dfc8 136020 net optional 

Processed: Re: Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 879518 normal
Bug #879518 [ifupdown] ifupdown: fail to start with bridge_stp on and recursion 
detected in parent-lock with vlan after jessie upgrade
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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



Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Guus Sliepen
severity 879518 normal
thanks

On Sun, Oct 22, 2017 at 04:35:58PM +0200, Daniel wrote:

> Severity: critical
> Justification: breaks the whole system

Downgrading to normal since this bug doesn't fit the definition of
critical:

“Makes unrelated software on the system (or the whole system) break, or
causes serious data loss, or introduces a security hole on systems where
you install the package.”

> This setup was perfectly running on Jessie. After upgrading to Stretch, all 
> the network stuff was down, doesn't matter if local, VMs or Internet.
> In the interfaces file below we changed the bridge-stp to off to get rid from 
> the "set forward delay failed: Numerical result out of range" error.
> After this, interface bone was going up as well as eth0 but then we had the 
> parent-lock error. We commented the pre-up bone[.1|.2] on each interface who 
> call them
> and the system started with all interfaces up.

I see. Locking interfaces indeed prevents a VLAN interface from calling ifup on
its parent interface. It's actually with good reason; while it may have
worked on your bridge interface, it's not guaranteed to work correctly,
and it will break in situations where interface are created on demand
(like with tun/tap interfaces).

That said, it's of course necessary for the parent interface to be up
before you can bring up a VLAN interface. So I'll probably change
ifupdown to do that for you. That way, you won't need pre-up ifup
statements anymore.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Bug#878564: marked as done (postgresql-filedump FTBFS with PostgreSQL 10)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 18:49:14 +
with message-id 
and subject line Bug#878564: fixed in postgresql-filedump 10.0-1
has caused the Debian Bug report #878564,
regarding postgresql-filedump FTBFS with PostgreSQL 10
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.)


-- 
878564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-filedump
Version: 9.6.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-filedump.html

...
   dh_auto_build
make -j1
make[1]: Entering directory '/build/1st/postgresql-filedump-9.6.0'
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/postgresql/10/server pg_filedump.c -c
pg_filedump.c: In function 'FormatItem':
pg_filedump.c:994:18: error: 'SizeOfIptrData' undeclared (first use in this 
function)
   if (numBytes < SizeOfIptrData)
  ^~
pg_filedump.c:994:18: note: each undeclared identifier is reported only once 
for each function it appears in
pg_filedump.c: In function 'FormatControl':
pg_filedump.c:1613:19: error: 'ControlFileData {aka struct ControlFileData}' 
has no member named 'enableIntTimes'
   (controlData->enableIntTimes ?
   ^~
Makefile:26: recipe for target 'pg_filedump.o' failed
make[1]: *** [pg_filedump.o] Error 1
--- End Message ---
--- Begin Message ---
Source: postgresql-filedump
Source-Version: 10.0-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated postgresql-filedump 
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, 22 Oct 2017 20:12:17 +0200
Source: postgresql-filedump
Binary: postgresql-filedump
Architecture: source
Version: 10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 postgresql-filedump - Utility to format PostgreSQL files
Closes: 878564
Changes:
 postgresql-filedump (10.0-1) unstable; urgency=medium
 .
   * New upstream release supporting PG10. (Closes: #878564)
   * Update Standards-Version and package URLs.
   * Re-enable PIE on 32bit archs.
Checksums-Sha1:
 e5d9fed0f4283320cd45549e070efe4eafac4ec1 2158 postgresql-filedump_10.0-1.dsc
 0858429de2c42f0bb095f4af185a91cec1f99e95 31544 
postgresql-filedump_10.0.orig.tar.gz
 2f112df94cec4184b0f7ea36d4abab648ac163c5 3016 
postgresql-filedump_10.0-1.debian.tar.xz
 c7f17808528451438aa415468401f1af3eb97e1c 6778 
postgresql-filedump_10.0-1_source.buildinfo
Checksums-Sha256:
 bb9458f095a6cb9f6dc03797abdcfa34521be675d7dc979a799bdbb1fc21461c 2158 
postgresql-filedump_10.0-1.dsc
 5adddeeed5ca97408b94333c5baf5deb6732c7b3fbbd192d7d2c639f5c1be409 31544 
postgresql-filedump_10.0.orig.tar.gz
 fa4a814128799458ed3d9cadde0e21eac3c274e86189da0c62e8c4417e095810 3016 
postgresql-filedump_10.0-1.debian.tar.xz
 961f78fa4d105c2940a811574cedaaa611f95be350d69acdad96ffa2a1d3bc2f 6778 
postgresql-filedump_10.0-1_source.buildinfo
Files:
 34ed4128a00fa15388208c257662f6a8 2158 database optional 
postgresql-filedump_10.0-1.dsc
 1299b533be564819c03d92567e31e497 31544 database optional 
postgresql-filedump_10.0.orig.tar.gz
 3833fb9fa7dd6f292f1e1a8ee0e2f16c 3016 database optional 
postgresql-filedump_10.0-1.debian.tar.xz
 2d168e5ff738c54bad68049439d0 6778 database optional 
postgresql-filedump_10.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlns5KkACgkQTFprqxLS
p67ISw/6Albu5KXK6xLHIAbKH13f9ngOfKiV6Q5ji0w7mWmln/1vA960GWYiDL+O
R+YZE2Hh2CkYg2hyHvsRdgP7+jZj7ITklC8hcj0YSsVDcAN9hyb0GnVmL/PeXDGl
4/SLeoJpzxkZzjNfW1PuLacwbMAIrkyVhtYb8noPs0JC96kypoBceNiqSgsB1Nc7
4rUd6ej5aWwolPysWr9G5WPY4LDzvy/gDH7ldv2SLwMMlM+jXiW76yDFX9+Sss0s

Bug#855218: marked as done (kubernetes-master: Unable to install due to failing kubernetes-master.service)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 18:48:58 +
with message-id 
and subject line Bug#855218: fixed in kubernetes 1.7.7+dfsg-3
has caused the Debian Bug report #855218,
regarding kubernetes-master: Unable to install due to failing 
kubernetes-master.service
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.)


-- 
855218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kubernetes-master
Version: 1.2.5+dfsg-1
Severity: serious
Justification: renders package unusable

Hi!

Trying to install the kubernetes-master package on Debian unstable fails with:

root@test-janluca2:~# apt install kubernetes-master
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.3.0-1-amd64 linux-image-4.5.0-2-amd64 linux-image-4.6.0-1-amd64
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  kubernetes-client
The following NEW packages will be installed:
  kubernetes-client kubernetes-master
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.2 MB of archives.
After this operation, 198 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.de.debian.org/debian experimental/main amd64 kubernetes-client 
amd64 1.2.5+dfsg-1 [4,647 kB]
Get:2 http://ftp.de.debian.org/debian experimental/main amd64 kubernetes-master 
amd64 1.2.5+dfsg-1 [26.6 MB]
Fetched 31.2 MB in 1s (30.3 MB/s)
Selecting previously unselected package kubernetes-client.
(Reading database ... 205878 files and directories currently installed.)
Preparing to unpack .../kubernetes-client_1.2.5+dfsg-1_amd64.deb ...
Unpacking kubernetes-client (1.2.5+dfsg-1) ...
Selecting previously unselected package kubernetes-master.
Preparing to unpack .../kubernetes-master_1.2.5+dfsg-1_amd64.deb ...
Unpacking kubernetes-master (1.2.5+dfsg-1) ...
Setting up kubernetes-master (1.2.5+dfsg-1) ...
Job for kube-apiserver.service failed because the control process exited with 
error code.
See "systemctl status kube-apiserver.service" and "journalctl -xe" for details.
invoke-rc.d: initscript kube-apiserver, action "start" failed.
● kube-apiserver.service - Kubernetes API Server
   Loaded: loaded (/lib/systemd/system/kube-apiserver.service; disabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2017-02-15 
16:26:38 CET; 9ms ago
 Docs: https://github.com/kubernetes/kubernetes
   man:kube-apiserver
  Process: 29675 ExecStart=/usr/bin/kube-apiserver $KUBE_LOGTOSTDERR 
$KUBE_LOG_LEVEL $KUBE_ALLOW_PRIV $KUBE_API_ADDRESS $KUBE_API_PORT $KUBELET_PORT 
$KUBE_ETCD_SERVERS $KUBE_SERVICE_ADDRESSES $KUBE_ADMISSION_CONTROL $DAEMON_ARGS 
(code=exited, status=255)
 Main PID: 29675 (code=exited, status=255)
  CPU: 174ms

Feb 15 16:26:38 test-janluca2 systemd[1]: kube-apiserver.service: Unit entered 
failed state.
Feb 15 16:26:38 test-janluca2 systemd[1]: kube-apiserver.service: Failed with 
result 'exit-code'.
dpkg: error processing package kubernetes-master (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up kubernetes-client (1.2.5+dfsg-1) ...
Processing triggers for systemd (232-15) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 kubernetes-master
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@test-janluca2:~#

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: kubernetes
Source-Version: 1.7.7+dfsg-3

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

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated kubernetes package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#879513: lame will not run at all

2017-10-22 Thread Sebastian Ramacher
On 2017-10-22 19:46:28, Fabian Greffrath wrote:
> Hi Klaumi,
> 
> Am Sonntag, den 22.10.2017, 15:24 +0200 schrieb Klaumi Klingsporn:
> > Maybe it helps to upgrade libmp3lame0 to 3.100-2 as well?
> > In this case lame should depend on this version (or above)
> > of course!
> 
> the point is that in the lame 3.100-2 upload the library got a symbols
> file that maps all symbols to a dependency on libmp3lame0 (>= 3.100).
> 
> So, lame 3.100-2 should have pulled in the 3.100-2 library package.
> Alex, can you confirn that?

Alex is using libmp3lame0 from dmo with version 1:3.99-0.1 which trivially
satisfies >= 3.100 due to the epoch.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Processed: transition: netcdf

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 878818
Bug #879544 [release.debian.org] transition: netcdf
879544 was not blocked by any bugs.
879544 was not blocking any bugs.
Added blocking bug(s) of 879544: 878818
> forwarded -1 https://release.debian.org/transitions/html/auto-netcdf.html
Bug #879544 [release.debian.org] transition: netcdf
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-netcdf.html'.

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



Bug#800891: marked as done (r-cran-afex violates the GPL2)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 18:06:09 +
with message-id 
and subject line Bug#800891: fixed in r-cran-afex 0.18-0-1
has caused the Debian Bug report #800891,
regarding r-cran-afex violates the GPL2
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.)


-- 
800891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org,r-cran-afex
Version: 0.14-2-1
Severity: serious
Tags: upstream
Justification: Policy 2.3

Dear Maintainer,

I believe the r-cran-afex package violates the GPL. It is released under GPL3+, 
however it has GPL2-only dependencies (r-cran-stringr, r-cran-coin, 
r-crain-lsmeans), and it calls functions from these packages directly.

The nature of the interaction (function calls) means that r-cran-afex and its 
dependencies constitute a single work, and not two separate programs, as per 
the GPL faq:

https://www.gnu.org/licenses/gpl-faq.en.html#MereAggregation
https://www.gnu.org/licenses/gpl-faq.en.html#IfInterpreterIsGPL


Versions of packages r-cran-afex depends on:
ii  r-base 3.2.2-1
ii  r-base-core [r-api-3]  3.2.2-1
ii  r-cran-car 2.1-0-1
ii  r-cran-coin1.1-0-1
ii  r-cran-lme41.1-9-1
ii  r-cran-lsmeans 2.20-1
ii  r-cran-matrix  1.2-2-1
ii  r-cran-pbkrtest0.4-2-1
ii  r-cran-reshape21.4-1
ii  r-cran-stringr 0.6.2-2

r-cran-afex recommends no packages.

r-cran-afex suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-cran-afex
Source-Version: 0.18-0-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-afex 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, 22 Oct 2017 19:37:24 +0200
Source: r-cran-afex
Binary: r-cran-afex
Architecture: source
Version: 0.18-0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas Tille 
Description:
 r-cran-afex - GNU R package for analyzing factorial experiments using ANOVA or
Closes: 800891
Changes:
 r-cran-afex (0.18-0-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version
 Closes: #800891
   * Use dh-r
   * Add r-cran-dplyr, r-cran-mlmrev to test dependencies
   * debhelper 10
   * Canonical CRAN homepage
   * Standards-Version: 4.1.1 (no changes needed)
   * d/watch: version=4
   * Build-Depends: r-cran-lmertest, r-cran-foreign
   * Secure URI in watch file
Checksums-Sha1:
 704f18af8e474bcf2f890b82784b3804102af5ae 2290 r-cran-afex_0.18-0-1.dsc
 b6bba0e01de1b5507a38ac8bd2714e23b056f5b9 2430582 r-cran-afex_0.18-0.orig.tar.gz
 5560beda2bce272beca3e95e0d80501989ddd408 4376 
r-cran-afex_0.18-0-1.debian.tar.xz
 c216226ad63c5bf214625ddc72db6f1538001e55 14407 
r-cran-afex_0.18-0-1_source.buildinfo
Checksums-Sha256:
 a666f9f82777a76143985cff8dcdc6c8d620536502c68dc9d3c1401a80cb750c 2290 
r-cran-afex_0.18-0-1.dsc
 65bf137d1cffa97ac0bd79923612d29738d8dea3d1efa572875c0b570eab4453 2430582 
r-cran-afex_0.18-0.orig.tar.gz
 66f7536b55a3e12327db0e514a0e06f20931ec75ec749a574aafb654e20a29c3 4376 
r-cran-afex_0.18-0-1.debian.tar.xz
 656ec4d41cc8cded9b14c27cb0621f148568d5cb1b1800e66de4b28226ab3ef6 14407 
r-cran-afex_0.18-0-1_source.buildinfo
Files:
 029ce58a27c0a2a40b44374cd97c80c3 2290 gnu-r optional r-cran-afex_0.18-0-1.dsc
 76192b329626fde749d6bd72f5ae7bb5 2430582 gnu-r optional 
r-cran-afex_0.18-0.orig.tar.gz
 ef3c37bc42de0a506b9490c6db04dbbb 4376 gnu-r optional 
r-cran-afex_0.18-0-1.debian.tar.xz
 2b0230e49db6b9543cb147139dcffd3d 14407 gnu-r optional 
r-cran-afex_0.18-0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlns2c4OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtF3HhAAiWpIEdUSFEp9hlSQSY9E1YLgOglG4a4ACAVD

Bug#870217: glm: diff for NMU version 0.9.8.4-1.1

2017-10-22 Thread Guus Sliepen
On Sun, Oct 22, 2017 at 03:34:53PM +0200, Tobias Frost wrote:

> I've prepared an NMU for glm (versioned as 0.9.8.4-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

I was actually waiting for 0.9.8.6 or 0.9.9 to be released, but I won't
mind this NMU :)

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Bug#879513: lame will not run at all

2017-10-22 Thread Fabian Greffrath
Hi Klaumi,

Am Sonntag, den 22.10.2017, 15:24 +0200 schrieb Klaumi Klingsporn:
> Maybe it helps to upgrade libmp3lame0 to 3.100-2 as well?
> In this case lame should depend on this version (or above)
> of course!

the point is that in the lame 3.100-2 upload the library got a symbols
file that maps all symbols to a dependency on libmp3lame0 (>= 3.100).

So, lame 3.100-2 should have pulled in the 3.100-2 library package.
Alex, can you confirn that?

 - Fabian


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


Bug#878751: marked as done (expeyes FTBFS: recipe for target 'microhope.pdf' failed)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 17:19:23 +
with message-id 
and subject line Bug#878751: fixed in expeyes 4.3.2+dfsg-1
has caused the Debian Bug report #878751,
regarding expeyes FTBFS: recipe for target 'microhope.pdf' failed
to be marked as done.

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

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


-- 
878751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: expeyes
Version: 4.3.1+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=expeyes=sid

...
make[3]: Entering directory 
'/<>/expeyes-4.3.1+dfsg/microhope/microhope-doc'
Exporting microhope.lyx to a LaTeX file ... Makefile:35: recipe for target 
'microhope.pdf' failed
make[3]: *** [microhope.pdf] Error 127
--- End Message ---
--- Begin Message ---
Source: expeyes
Source-Version: 4.3.2+dfsg-1

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated expeyes 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, 08 Oct 2017 19:56:07 +0200
Source: expeyes
Binary: expeyes eyes17 libej0 libej-dev expeyes-clib expeyes-firmware-dev 
python-expeyes expeyes-web microhope
Architecture: source amd64 all
Version: 4.3.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 expeyes- hardware & software framework for developing science experiments
 expeyes-clib - hardware & software framework for developing science experiments
 expeyes-firmware-dev - hardware & software framework for developing science 
experiments
 expeyes-web - Web interface for expEYES-Junior
 eyes17 - hardware & software framework for developing science experiments
 libej-dev  - hardware & software framework for developing science experiments
 libej0 - hardware & software framework for developing science experiments
 microhope  - hardware & software framework to learn microcontrollers
 python-expeyes - Python library for expeyes
Closes: 773202 877323 878751
Changes:
 expeyes (4.3.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream release, which adds more translations
   * removed unused dependencies on python*-usb: Closes: #773202
   * Keep pdf precompiled file in the source package (the PDF comes
 with its source in LyX format). Closes: #878751
   * added the German translation: Closes: #877323
Checksums-Sha1:
 3369b95ea1d33779d2b0fd9db5b50819dbf76d33 2462 expeyes_4.3.2+dfsg-1.dsc
 9f6f5d933f9209458d2f0a52a9fac6f080e68613 17586954 
expeyes_4.3.2+dfsg.orig.tar.gz
 ad83fabd00e2ef86c66dae2f431beb163e9074dd 3236940 
expeyes_4.3.2+dfsg-1.debian.tar.xz
 3ed9fd6096ddba009923050bdfe6c5ed038b4e0c 24860 
expeyes-clib-dbgsym_4.3.2+dfsg-1_amd64.deb
 db9034cdd1e60c5ec90f8575392aff430f12ae9e 16188 
expeyes-clib_4.3.2+dfsg-1_amd64.deb
 e030373a8ae9fee0416eb6aebf48b1383f8423e7 25972 
expeyes-firmware-dev_4.3.2+dfsg-1_all.deb
 ba0688a3dc95cd048be97574dd839c94c8fff73a 605556 
expeyes-web_4.3.2+dfsg-1_all.deb
 0adf2fbfb5f8be623e52f358131b6f119f1ab491 588448 expeyes_4.3.2+dfsg-1_all.deb
 5a73e28c6a92bf0535e40b08dd14da2a76ad3630 18105 
expeyes_4.3.2+dfsg-1_amd64.buildinfo
 4511f93b3d8f1abb75ee69bf476bfbada3930c95 613248 eyes17_4.3.2+dfsg-1_all.deb
 53c0884614e2b527aca08b002ef7cb2aebe647e1 19756 libej-dev_4.3.2+dfsg-1_amd64.deb
 ecbb99404b73c1090f6bce750d4fafc1e12e6740 17964 
libej0-dbgsym_4.3.2+dfsg-1_amd64.deb
 2825f932818524a263cee42dba29909fa50626ed 18716 libej0_4.3.2+dfsg-1_amd64.deb
 09853066f7169243c3480eec1026c1ec8acf078e 41444 
microhope-dbgsym_4.3.2+dfsg-1_amd64.deb
 14525d2191b9932e06a8c91914b4f4d568876db4 3360180 
microhope_4.3.2+dfsg-1_amd64.deb
 491b0716bd67876b01f555ec6832752fac55e217 87640 
python-expeyes_4.3.2+dfsg-1_all.deb
Checksums-Sha256:
 d0478e826d8c2f0230966ac541959ae0e044b7c9045d255142c038632cfbc28b 2462 
expeyes_4.3.2+dfsg-1.dsc
 

Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Daniel Huhardeaux
I investigate further and discover that the the message "recursion 
detected in parent-lock" appears in *ALL* vlan interfaces (.1 .2 .100 
.1001 .1002), not only the 2 first one as I reported.
After having removed all pre-up bone and pre-up bone.vlan in interfaces 
file, I was able to again set bridge_stp on without getting the "set 
forward delay failed: Numerical result out of range" message.
This means that bridge_stp on error is a result from the pre-up bone and 
bone.vlan behavior.


Regards

--
Daniel



Processed: severity of 859262 is important

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 859262 important
Bug #859262 [gnome-orca] gnome-orca: Gets stuck if target app is busy
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#871117: closing 871117

2017-10-22 Thread Samuel Thibault
close 871117 
thanks

fixed by 871089 as Andreas Bombe noticed, thanks!
Samuel



Processed: closing 871117

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 871117
Bug #871117 [src:festival] festival: FTBFS: /bin/sh: 1: g++-6: not found
Marked Bug as done
> thanks
Stopping processing here.

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



Processed: bug 878972 is forwarded to https://github.com/donnemartin/gitsome/issues/105, tagging 878972

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 878972 https://github.com/donnemartin/gitsome/issues/105
Bug #878972 [src:gitsome] gitsome build depends on python3 (< 3.6) but 3.6.3-1 
is to be installed
Set Bug forwarded-to-address to 
'https://github.com/donnemartin/gitsome/issues/105'.
> tags 878972 + upstream
Bug #878972 [src:gitsome] gitsome build depends on python3 (< 3.6) but 3.6.3-1 
is to be installed
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Bug#871089: marked as done (speech-tools: FTBFS: /bin/sh: 1: g++-6: not found)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 16:06:58 +
with message-id 
and subject line Bug#871089: fixed in speech-tools 1:2.4~release-6
has caused the Debian Bug report #871089,
regarding speech-tools: FTBFS: /bin/sh: 1: g++-6: not found
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.)


-- 
871089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: speech-tools
Version: 1:2.4~release-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Check system type
> Remake modincludes.inc
>   NATIVE_AUDIO
>   ok
>   EDITLINE
>   config/modules/editline.mak
>   SIOD
>   siod/siod.mak
>   WAGON
>   stats/wagon/wagon.mak
>   SCFG
>   grammar/scfg/scfg.mak
>   WFST
>   grammar/wfst/wfst.mak
>   OLS
>   stats/ols.mak
>   RXP
>   rxp/rxp.mak
>   LINUX16_AUDIO
>   config/modules/linux16_audio.mak
> Making in directory ./siod ...
> making dependencies -- siodeditline.c el_complete.c editline.c el_sys_unix.c 
> slib.cc slib_core.cc slib_doc.cc slib_file.cc slib_format.cc slib_list.cc 
> slib_math.cc slib_sys.cc slib_server.cc slib_str.cc slib_xtr.cc slib_repl.cc 
> slib_python.cc io.cc trace.cc siod.cc siod_est.cc 
> g++-6 -fno-delete-null-pointer-checks -c -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -fPIC -Wall 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -fPIC -Wall -DSUPPORT_EDITLINE 
> -I../include -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security slib.cc
> /bin/sh: 1: g++-6: not found
> ../config/rules/c.mak:59: recipe for target 'slib.o' failed
> make[3]: *** [slib.o] Error 127

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/speech-tools_2.4~release-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: speech-tools
Source-Version: 1:2.4~release-6

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

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

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated speech-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Oct 2017 17:34:44 +0200
Source: speech-tools
Binary: libestools2.4 libestools-dev speech-tools speech-tools-doc
Architecture: source
Version: 1:2.4~release-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 libestools-dev - Edinburgh Speech Tools Library - developer's libraries
 libestools2.4 - Edinburgh Speech Tools Library
 speech-tools - Edinburgh Speech Tools - user binaries
 speech-tools-doc - Documentation for the Edinburgh Speech Tools
Closes: 857667 871089
Changes:
 speech-tools (1:2.4~release-6) unstable; urgency=medium
 .
   * Use canonical anonscm vcs URL.
   * control: Update maintainer mailing list.
   * control: Remove libaudiofile-dev build-dependency, now
 unused. Closes: Bug#857667
   * patches/gcc-6: Do not hardcode gcc version. Closes: Bug#871089
   * control: Bump Standards-Version to 4.1.1 (no change)
   * rules: Remove reference to former -dbg packages.
Checksums-Sha1:
 f2819ce886e4229e8f1f02c5708734a9ebeb03be 

Bug#879521: irssi: multiple vulnerabilities fixed in irssi 1.0.5

2017-10-22 Thread Yves-Alexis Perez
On Sun, 2017-10-22 at 17:22 +0200, Yves-Alexis Perez wrote:
> Can you prepare updates for sid, stretch and jessie (please coordinate with
> security team at t...@security.debian.org for the latter two)? Please add
> CVE numbers to the changelog so we can track them easily.

By the way, fixes against master are here:

https://github.com/irssi/irssi/commit/43e44d553d44e313003cee87e6ea5e24d68b84a1

Regards,
-- 
Yves-Alexis Perez - Debian Security



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


Bug#871117: festival: FTBFS: /bin/sh: 1: g++-6: not found

2017-10-22 Thread Andreas Bombe
block 871117 by 871089
thanks

This problem is caused by #871089 because it is using the same
configuration files for building. Changing the hardcoded g++-6 to plain
g++ (in the gcc-6 patch to speech-tools) fixes the build issue.

This bug should be fixed when the other bug is fixed.



Processed: Re: festival: FTBFS: /bin/sh: 1: g++-6: not found

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 871117 by 871089
Bug #871117 [src:festival] festival: FTBFS: /bin/sh: 1: g++-6: not found
871117 was not blocked by any bugs.
871117 was not blocking any bugs.
Added blocking bug(s) of 871117: 871089
> thanks
Stopping processing here.

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



Bug#879521: irssi: multiple vulnerabilities fixed in irssi 1.0.5

2017-10-22 Thread Yves-Alexis Perez
Source: irssi
Severity: grave
Tags: security
Justification: user security hole

Hi,

irssi 1.0.5 has been released, fixing multiple vulnerabilities

(a) When installing themes with unterminated colour formatting
sequences, Irssi may access data beyond the end of the
string. (CWE-126) Found by Hanno Böck.

CVE-2017-15228 was assigned to this issue.

(b) While waiting for the channel synchronisation, Irssi may
incorrectly fail to remove destroyed channels from the query list,
resulting in use after free conditions when updating the state
later on. Found by Joseph Bisch. (CWE-416 caused by CWE-672)

CVE-2017-15227 was assigned to this issue.

(c) Certain incorrectly formatted DCC CTCP messages could cause NULL
pointer dereference. Found by Joseph Bisch. This is a separate,
but similar issue to CVE-2017-9468. (CWE-690)

CVE-2017-15721 was assigned to this issue.

(d) Overlong nicks or targets may result in a NULL pointer dereference
while splitting the message. Found by Joseph Bisch. (CWE-690)

CVE-2017-15723 was assigned to this issue.

(e) In certain cases Irssi may fail to verify that a Safe channel ID
is long enough, causing reads beyond the end of the string. Found
by Joseph Bisch. (CWE-126)

CVE-2017-15722 was assigned to this issue.

Can you prepare updates for sid, stretch and jessie (please coordinate with 
security team at t...@security.debian.org for the latter two)? Please add CVE 
numbers to the changelog so we can track them easily.

Regards,
-- 
Yves-Alexis
Debian security team

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

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


Bug#879175: androidsdk-tools: Duplicate of android-platform-tools-swt

2017-10-22 Thread 殷啟聰 | Kai-Chung Yan
(I am one maintainer of android-platform-tools-swt)

To be honest, both should be removed since Google has abandoned 
android-platform-tools-swt. That's why it remains unbuildable as of today.



signature.asc
Description: OpenPGP digital signature


Bug#878746: marked as done (praat FTBFS on !amd64: num/fisherQ.praat fails)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 15:08:40 +
with message-id 
and subject line Bug#878746: fixed in praat 6.0.35-2
has caused the Debian Bug report #878746,
regarding praat FTBFS on !amd64: num/fisherQ.praat fails
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.)


-- 
878746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: praat
Version: 6.0.34-1
Severity: serious

https://buildd.debian.org/status/package.php?p=praat=sid

...
= num/fisherQ.praat
Error: Script assertion fails in line 13 (false):
   fisherQ (randomUniform (3, 4), 1, 10) <> undefined
Script “/<>/test/num/fisherQ.praat” not completed.
Praat: script command <> not completed.

fisherQ test: 5.932714539946133e-11 0.005932714540
...
116 tests passed, 115 ok
Failed test(s):

num/fisherQ.praat
debian/rules:84: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: praat
Source-Version: 6.0.35-2

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated praat 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, 22 Oct 2017 06:57:27 -0200
Source: praat
Binary: praat
Architecture: source amd64
Version: 6.0.35-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Rafael Laboissiere 
Description:
 praat  - program for speech analysis and synthesis
Closes: 878746
Changes:
 praat (6.0.35-2) unstable; urgency=medium
 .
   * d/t/run-tests: Skip unit test fisherQ.praat (Closes: #878746)
Checksums-Sha1:
 4114f19109aab98940de9e0fcfd04c8a093fd0ca 2273 praat_6.0.35-2.dsc
 21fcb7965819838d33162ad9166031761321d1cd 24536 praat_6.0.35-2.debian.tar.xz
 0fb9e69180b5fa4e87444cf6fd6fbb19b119941b 31311488 
praat-dbgsym_6.0.35-2_amd64.deb
 59d3a8b622f196598540ecdd6b8bbed25d7f4cb0 11263 praat_6.0.35-2_amd64.buildinfo
 328a84a28d058425c936f6880d712cc754c8c557 9171700 praat_6.0.35-2_amd64.deb
Checksums-Sha256:
 727561fc166e54e9a43c836ee1a3fc33d637e3f90058d2b8730f20215fb27132 2273 
praat_6.0.35-2.dsc
 8d573d5595358d294aebcd9772b5e92b983c404162eabfd95c4b0b8b9bafea92 24536 
praat_6.0.35-2.debian.tar.xz
 515dad053c2af7f381783d779eb83fcccf2304e10123339892c3729746ad7db3 31311488 
praat-dbgsym_6.0.35-2_amd64.deb
 e7f6bc934703591873785d9215a67cebd95f3d4514ccbf125eafb73909eef75c 11263 
praat_6.0.35-2_amd64.buildinfo
 38b771eac69feb4b219e98af3ca55a822a4e4203fee27d836ce03e9fff4b382d 9171700 
praat_6.0.35-2_amd64.deb
Files:
 d46ebc76703adfa9a6f9a210df999e7c 2273 science optional praat_6.0.35-2.dsc
 d0c734029efd15d49b24c183420cace5 24536 science optional 
praat_6.0.35-2.debian.tar.xz
 eda18e48c30abc31ca0af86791dad953 31311488 debug optional 
praat-dbgsym_6.0.35-2_amd64.deb
 ff1865cfa1cc5f67542b181984ab79e6 11263 science optional 
praat_6.0.35-2_amd64.buildinfo
 3ade8b7e629eb6f2b850594ac5ffed11 9171700 science optional 
praat_6.0.35-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlnsqKEACgkQISSqGYN4
XJDE4g//eZYZ8PwAZ3TWopHiwBrBXHTyAuYH9a5lgQIkAgCyFrVcWDZp55fM4Xod
EnIZH5oWaRrpfbarIo8np6nTHFyGPlrN0kynLLrPY3848EEZRKeSCYGDeMf1/bii
KpfPkaczcPGkoEaczpN1hZy0n3XIQ5/dHUBcY7/jCwuPzrVs3wJMDCZeftYBmmsh
JRMKJvL0CSS+MIBStHIFFmxQM9Ub7FyqLqkDC5iCwo3W9Wrdp9voKbUYcHCFjLCp
vV1VMpFnalSobOT8H2uX3xPgFL0hvHdwlrqGyIlTe8tNrZGBvGKzFWkiun3oskav
eu5KIJBKwNPWXcwnj+2uBBJ3hpFVgiZO3trsDMObQPcV2QjnGSXhxgy5rwiwGt+X
VkScn3oZuJw77iInwgW9ePzwkj6B5iscNOyAE5S0WL6//hKZRBiKZjCjvrQ0vXZt
9fEWlNpIjXi1WnkTv/zVjQ6uGASwBammA1yTF8jnsKWRKVIyPxoq7lpfa+vP+wog
L26CQn2iOiW5kDtSxSSHHOMiI1+BsdorsWXWPhEzz2W8/aLcpq+ljaa8fHUuFKbo
2UcNXw/52WwSMDO8qBHZJMRFoBdtOz7pHDQdfhzY+jM+OVwd/FHG1Akx7SBzOLbp
7mMzpj/nAGWCaPNhfKynUeD1EJbtPmVHdlJY4wSPtbu7Ejf9s9w=
=nDkg
-END PGP SIGNATURE End Message ---


Bug#878046: marked as done (amanda-server: Fails all backups if one or more hosts are down)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 15:04:11 +
with message-id 
and subject line Bug#878046: fixed in amanda 1:3.5-1
has caused the Debian Bug report #878046,
regarding amanda-server: Fails all backups if one or more hosts are down
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.)


-- 
878046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amanda-server
Version: 1:3.3.9-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

If one or more backup host is unreachable, the backup of all hosts fails.

Example - backing up two hosts - smaug and TerriblTerror:

If the latter is unreachable

  TerribleTerror1 /etc lev 0  FAILED [Request to TerribleTerror1 failed: 
Connection timed out]

The former (and all other hosts in the backup sequence) fail with:

  smaug /exports/md0/home/aivanov lev 0  FAILED [Request to smaug failed: error 
sending REQ: write error to: Broken pipe]

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

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

Versions of packages amanda-server depends on:
ii  amanda-common  1:3.3.9-5
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
ii  libc6  2.24-11+deb9u1
ii  libcurl3   7.52.1-5
ii  libglib2.0-0   2.50.3-2
ii  libssl1.1  1.1.0f-3
ii  perl   5.24.1-3

amanda-server recommends no packages.

Versions of packages amanda-server suggests:
ii  amanda-client  1:3.3.9-5
ii  cpio   2.11+dfsg-6
ii  gnuplot5.0.5+dfsg1-6
ii  mt-st  1.3-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: amanda
Source-Version: 1:3.5-1

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

Debian distribution maintenance software
pp.
Jose M Calhariz  (supplier of updated amanda 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, 22 Oct 2017 13:10:08 +0100
Source: amanda
Binary: amanda-common amanda-server amanda-client
Architecture: source amd64
Version: 1:3.5-1
Distribution: experimental
Urgency: medium
Maintainer: Jose M Calhariz 
Changed-By: Jose M Calhariz 
Description:
 amanda-client - Advanced Maryland Automatic Network Disk Archiver (Client)
 amanda-common - Advanced Maryland Automatic Network Disk Archiver (Libs)
 amanda-server - Advanced Maryland Automatic Network Disk Archiver (Server)
Closes: 878045 878046
Changes:
 amanda (1:3.5-1) experimental; urgency=medium
 .
   * Add gawk as Build-Depends.
   * New upstream version 3.5
   * Use different thread to connect to different client
   * amservice, amcheck, planner, dumper are no longer suid root
   * ambind
  - new suid program to bind to a privileged port
   * amanda-security.conf
  - new tcp_port_range, range of privileged tcp port
  - new udp_port_range, range of privileged udp port
   * S3 device
  - openstack keystone v3 support
* device-property STORAGE-API must be set to SWIFT-3
* new PROJECT-NAME device-property
* new DOMAIN-NAME device-property
   * amfetchdump
  - rename --directory argument to --target
   * ampgsql
  - new --incremental property
  - new --remove-full-wal property
  - new --remove-incremental-wal property
 .
   * New upstream version 3.4.6
  * fix planner looping
  * fix overflow in S3 device
  * fix compilation on OpenBSD
  * fix race in amarchive reader
  * fix amflush (flush date selected by user)
  * fix local auth, use getaddrinfo to find if the host is local
  * fix dumper cancelling the shm_ring with a STRANGE result
   

Processed: kalzium: diff for NMU version 4:17.08.0-1.1

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> tags 869869 + pending
Bug #869869 [src:kalzium] kalzium FTBFS with OCaml 4.05.0: Options -c and -o 
are incompatible when compiling C files
Added tag(s) pending.

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



Bug#869869: kalzium: diff for NMU version 4:17.08.0-1.1

2017-10-22 Thread Tobias Frost
Control: tags 869869 + pending

Dear maintainer,

I've prepared an NMU for kalzium (versioned as 4:17.08.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru kalzium-17.08.0/debian/changelog kalzium-17.08.0/debian/changelog
--- kalzium-17.08.0/debian/changelog	2017-09-18 15:06:16.0 +0200
+++ kalzium-17.08.0/debian/changelog	2017-10-22 16:29:30.0 +0200
@@ -1,3 +1,12 @@
+kalzium (4:17.08.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "kalzium FTBFS with OCaml 4.05.0: Options -c and -o are
+incompatible when compiling C files" by applying patch from
+Stéphane Glondu, via the BTS (Closes: #869869)
+
+ -- Tobias Frost   Sun, 22 Oct 2017 16:29:30 +0200
+
 kalzium (4:17.08.0-1) experimental; urgency=medium
 
   * New upstream release (17.08.0)
diff -Nru kalzium-17.08.0/debian/patches/869869.patch kalzium-17.08.0/debian/patches/869869.patch
--- kalzium-17.08.0/debian/patches/869869.patch	1970-01-01 01:00:00.0 +0100
+++ kalzium-17.08.0/debian/patches/869869.patch	2017-10-22 16:29:30.0 +0200
@@ -0,0 +1,17 @@
+Description: Fix compilation with OCaml 4.05.0
+Author: Stéphane Glondu 
+Bug-Debian: https://bugs.debian.org/869869
+Forwarded: no
+Last-Update: 2017-07-28
+
+--- a/src/CMakeOCamlInstructions.cmake
 b/src/CMakeOCamlInstructions.cmake
+@@ -58,7 +58,7 @@
+ # object files
+ 
+ add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o
+-   COMMAND ${OCAML_OCAMLOPT_EXECUTABLE} -I ${LIBFACILE_INCLUDE_DIR} -c ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c
++   COMMAND ${OCAML_OCAMLOPT_EXECUTABLE} -I ${LIBFACILE_INCLUDE_DIR} -c ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c -ccopt -o -ccopt ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o
+DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c ${CMAKE_CURRENT_BINARY_DIR}/solver.o
+WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR})
+ set_directory_properties(PROPERTIES ADDITIONAL_MAKE_CLEAN_FILES ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o)
diff -Nru kalzium-17.08.0/debian/patches/series kalzium-17.08.0/debian/patches/series
--- kalzium-17.08.0/debian/patches/series	2017-09-18 15:06:16.0 +0200
+++ kalzium-17.08.0/debian/patches/series	2017-10-22 16:29:30.0 +0200
@@ -1,3 +1,4 @@
 no_install_rpath_use_link_path.diff
 avoid_nameclash.patch
 add_missing_include.patch
+869869.patch


signature.asc
Description: PGP signature


Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Daniel
Package: ifupdown
Version: 0.8.19
Severity: critical
Justification: breaks the whole system

This setup was perfectly running on Jessie. After upgrading to Stretch, all the 
network stuff was down, doesn't matter if local, VMs or Internet.
In the interfaces file below we changed the bridge-stp to off to get rid from 
the "set forward delay failed: Numerical result out of range" error.
After this, interface bone was going up as well as eth0 but then we had the 
parent-lock error. We commented the pre-up bone[.1|.2] on each interface who 
call them
and the system started with all interfaces up.


-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto bone lan isp1 isp2

# The bone interface
iface bone inet manual
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
pre-up ifup eth0

iface eth0 inet manual

iface lan inet static
address 192.168.10.250
netmask 255.255.255.0
dns-nameservers 192.168.10.254 xxx.yyy.zzz.179
dns-search domain.tld
gateway 192.168.10.1
bridge_ports bone.1 eth1
bridge_stp off
bridge_maxwait 0
bridge_fd 0
#pre-up ifup bone.1
pre-up ifup voice
pre-up ifup eth1
post-down ifdown bone.1
post-down ifdown voice

iface eth1 inet manual

iface bone.1 inet manual
vlan_raw_device bone
#pre-up ifup bone
#pre-up ifup bone.2
pre-up ifup bone.100
pre-up vconfig add bone 1
post-down vconfig rem bone.1

iface voice inet manual
bridge_ports bone.2
bridge_stp off
bridge_maxwait 0
bridge_fd 0
#pre-up ifup bone.2
post-down ifdown bone.2

iface bone.2 inet manual
vlan_raw_device bone
pre-up vconfig add bone 2
post-down vconfig rem bone.2

iface isp1 inet manual
bridge_ports bone.1001
bridge_stp off
bridge_maxwait 0
bridge_fd 0
pre-up ifup bone.1001
post-down ifdown bone.1001

iface bone.1001 inet manual
vlan_raw_device bone
#pre-up ifup bone
pre-up vconfig add bone 1001
post-up ifup fbx-tv
post-down vconfig rem bone.1001

iface fbx-tv inet manual
bridge_ports bone.100
bridge_stp off
bridge_maxwait 0
bridge_fd 0
#pre-up ifup bone.100
post-down ifdown bone.100

iface bone.100 inet manual
vlan_raw_device bone
#pre-up ifup bone
pre-up vconfig add bone 100
post-down vconfig rem bone.100

iface isp2 inet manual
bridge_ports bone.1002
bridge_stp off
bridge_maxwait 0
bridge_fd 0
pre-up ifup bone.1002
post-down ifdown bone.1002

iface bone.1002 inet manual
vlan_raw_device bone
#pre-up ifup bone
pre-up vconfig add bone 1002
post-down vconfig rem bone.1002

--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory

--- up and down scripts installed:
/etc/network/if-down.d:
total 8
-rwxr-xr-x 1 root root 800 Sep 27 06:56 postfix
-rwxr-xr-x 1 root root 332 Jan  6  2013 upstart

/etc/network/if-post-down.d:
total 4
lrwxrwxrwx 1 root root   29 Jul  2 23:20 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root 1207 Apr  1  2014 vlan

/etc/network/if-pre-up.d:
total 12
lrwxrwxrwx 1 root root   29 Jul  2 23:20 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root  344 Sep 22  2014 ethtool
-rwxr-xr-x 1 root root  137 Aug 16  2016 uml-utilities
-rwxr-xr-x 1 root root 2416 Apr  1  2014 vlan

/etc/network/if-up.d:
total 32
-rwxr-xr-x 1 root root 1685 Sep 22  2014 ethtool
-rwxr-xr-x 1 root root  578 Apr  1  2014 ip
-rwxr-xr-x 1 root root 4958 Apr  6  2015 mountnfs
-rwxr-xr-x 1 root root  972 Jun 18 02:08 openssh-server
-rwxr-xr-x 1 root root 1117 Sep 27 06:56 postfix
-rwxr-xr-x 1 root root  261 Nov 14  2014 uml-utilities
-rwxr-xr-x 1 root root 1483 Jan  6  2013 upstart


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

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

Versions of packages ifupdown depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  iproute2 4.9.0-1
ii  libc62.24-11+deb9u1
ii  lsb-base 9.20161125

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.5-3

Versions of packages ifupdown suggests:
pn  ppp 
pn  rdnssd  

-- no debconf information



Bug#878462: Patch

2017-10-22 Thread Andreas Stührk
tags 878462 + patch fixed-upstream
thanks

This issue is fixed upstream since release 2.48.4
(commit 4473822b5aa6de3e849ca6c958b365a71edbca4f fixed it).

Attached is a patch that fixes the FTBFS.
Index: unison-2.48.3/system/system_generic.ml
===
--- unison-2.48.3.orig/system/system_generic.ml
+++ unison-2.48.3/system/system_generic.ml
@@ -57,7 +57,7 @@ let opendir f =
 let readdir = Unix.readdir
 let closedir = Unix.closedir
 let readlink = Unix.readlink
-let symlink = Unix.symlink
+let symlink s1 s2 = Unix.symlink s1 s2
 let chdir = Sys.chdir
 let getcwd = Sys.getcwd
 


Processed: Patch

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 878462 + patch fixed-upstream
Bug #878462 [src:unison] unison FTBFS: Error: The implementation 
/build/1st/unison-2.48.3/system.ml does not match the interface system.cmi
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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



Bug#878820:

2017-10-22 Thread Andreas Stührk
Changing the
PYTHONPATH=$(shell echo .pybuild/pythonX.Y_3.5*/build/)
to
PYTHONPATH=$(shell echo .pybuild/pythonX.Y_3.6*/build/)
does indeed fix the FTBFS.


Processed: Patch

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 878453 + patch
Bug #878453 [src:altos] altos FTBFS: misleading-indentation
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#878453: Patch

2017-10-22 Thread Andreas Stührk
tags 878453 + patch
thanks

Attached is a patch that fixes the FTBFS.
Index: altos-1.8.2/src/math/kf_rem_pio2.c
===
--- altos-1.8.2.orig/src/math/kf_rem_pio2.c
+++ altos-1.8.2/src/math/kf_rem_pio2.c
@@ -77,7 +77,8 @@ twon8  =  3.906250e-03; /* 0x3b8
 
 /* compute q[0],q[1],...q[jk] */
 	for (i=0;i<=jk;i++) {
-	for(j=0,fw=0.0;j<=jx;j++) fw += x[j]*f[jx+i-j]; q[i] = fw;
+	for(j=0,fw=0.0;j<=jx;j++) fw += x[j]*f[jx+i-j];
+	q[i] = fw;
 	}
 
 	jz = jk;
Index: altos-1.8.2/src/math/sf_cos.c
===
--- altos-1.8.2.orig/src/math/sf_cos.c
+++ altos-1.8.2/src/math/sf_cos.c
@@ -16,12 +16,6 @@
 #include "fdlibm.h"
 
 #ifdef __STDC__
-static const float one=1.0;
-#else
-static float one=1.0;
-#endif
-
-#ifdef __STDC__
 	float cosf(float x)
 #else
 	float cosf(x)


Processed: Re: Bug#879513: lame will not run at all

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +unreproducible
Bug #879513 {Done: James Cowgill } [lame] lame will not 
run at all
Added tag(s) unreproducible.

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



Bug#879513: lame will not run at all

2017-10-22 Thread Fabian Greffrath
control: tags -1 +unreproducible

Am Sonntag, den 22.10.2017, 14:01 +0100 schrieb Alex Dekker:
> Package: lame
> Version: 3.100-2

Hi Alex,

I cannot reproduce your issue.

> ii  libmp3lame0  1:3.99.5-0.1

Ahem, please update the library package as well.

Thanks,

 - Fabian


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


Bug#879513: marked as done (lame will not run at all)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 14:32:25 +0100
with message-id 
and subject line Re: Bug#879513: lame will not run at all
has caused the Debian Bug report #879513,
regarding lame will not run at all
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.)


-- 
879513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lame
Version: 3.100-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since upgrading to lame 3.100-1 yesterday it fails to execute with:

$ lame
lame: symbol lookup error: lame: undefined symbol: 
lame_get_maximum_number_of_samples

Tried upgrading to 3.100-2 today and it is the same.


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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1), 
LANGUAGE=en_GB:en_US:en_GB:en (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lame depends on:
ii  libc62.24-17
ii  libmp3lame0  1:3.99.5-0.1
ii  libsndfile1  1.0.28-4
ii  libtinfo56.0+20170902-1

lame recommends no packages.

Versions of packages lame suggests:
pn  lame-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

On 22/10/17 14:01, Alex Dekker wrote:
> Package: lame
> Version: 3.100-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Since upgrading to lame 3.100-1 yesterday it fails to execute with:
> 
> $ lame
> lame: symbol lookup error: lame: undefined symbol: 
> lame_get_maximum_number_of_samples
> 
> Tried upgrading to 3.100-2 today and it is the same.
[...]
> ii  libmp3lame0  1:3.99.5-0.1

This version of lame is from deb-multimedia.org which Debian itself does
not support. If you install Debian's copy it should work:

apt-get install libmp3lame0=3.100-2

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---


Bug#870217: glm: diff for NMU version 0.9.8.4-1.1

2017-10-22 Thread Tobias Frost
Control: tags 870217 + patch
Control: tags 870217 + pending

Dear maintainer,

I've prepared an NMU for glm (versioned as 0.9.8.4-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru glm-0.9.8.4/debian/changelog glm-0.9.8.4/debian/changelog
--- glm-0.9.8.4/debian/changelog	2017-06-24 17:27:12.0 +0200
+++ glm-0.9.8.4/debian/changelog	2017-10-22 15:21:32.0 +0200
@@ -1,3 +1,14 @@
+glm (0.9.8.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherrypick patch from upstream for FTBFS for GCC-7 (Closes: #870217)
+  * Replace priority extra with optional. Fixes linitian:
+priority-extra-is-replaced-by-priority-optional
+  * Remove Testsuite: autopkgtest from d/control as it is no longer
+needed. Fixes lintian unnecessary-testsuite-autopkgtest-header
+
+ -- Tobias Frost   Sun, 22 Oct 2017 15:21:32 +0200
+
 glm (0.9.8.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru glm-0.9.8.4/debian/control glm-0.9.8.4/debian/control
--- glm-0.9.8.4/debian/control	2017-06-24 17:08:14.0 +0200
+++ glm-0.9.8.4/debian/control	2017-10-22 15:19:20.0 +0200
@@ -3,7 +3,7 @@
 Uploaders: Guus Sliepen 
 Section: libs
 Testsuite: autopkgtest
-Priority: extra
+Priority: optional
 Build-Depends: debhelper (>= 10),
cmake
 Standards-Version: 4.0.0
diff -Nru glm-0.9.8.4/debian/patches/870217.patch glm-0.9.8.4/debian/patches/870217.patch
--- glm-0.9.8.4/debian/patches/870217.patch	1970-01-01 01:00:00.0 +0100
+++ glm-0.9.8.4/debian/patches/870217.patch	2017-10-22 15:10:34.0 +0200
@@ -0,0 +1,54 @@
+Description: Patch fixing the  FTBFS with gcc-7: Test failures
+Author: Christophe Riccio 
+Origin: https://github.com/g-truc/glm/commit/e37cf6e47fa4305c82845103b17af58f6cfe23db.patch
+
+--- a/test/core/core_type_mat2x4.cpp
 b/test/core/core_type_mat2x4.cpp
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include 
+ #include 
+ #include 
+@@ -83,7 +85,7 @@
+ 		glm::mat2x4 Identity(1.0f);
+ 
+ 		for(glm::length_t i = 0, length = B.length(); i < length; ++i)
+-			Error += glm::all(glm::equal(B[i], Identity[i])) ? 0 : 1;
++			Error += glm::all(glm::epsilonEqual(B[i], Identity[i], glm::epsilon())) ? 0 : 1;
+ 
+ 		return Error;
+ 	}
+--- a/test/core/core_type_mat3x4.cpp
 b/test/core/core_type_mat3x4.cpp
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include 
+ #include 
+ #include 
+@@ -87,7 +89,7 @@
+ 		glm::mat3x4 Identity(1.0f);
+ 
+ 		for(glm::length_t i = 0, length = B.length(); i < length; ++i)
+-			Error += glm::all(glm::equal(B[i], Identity[i])) ? 0 : 1;
++			Error += glm::all(glm::epsilonEqual(B[i], Identity[i], glm::epsilon())) ? 0 : 1;
+ 
+ 		return Error;
+ 	}
+--- a/test/core/core_type_mat4x4.cpp
 b/test/core/core_type_mat4x4.cpp
+@@ -1,3 +1,4 @@
++#include 
+ #include 
+ #include 
+ #include 
+@@ -263,7 +264,7 @@
+ 		glm::mat4x4 Identity(1.0f);
+ 
+ 		for(glm::length_t i = 0, length = B.length(); i < length; ++i)
+-			Error += glm::all(glm::equal(B[i], Identity[i])) ? 0 : 1;
++			Error += glm::all(glm::epsilonEqual(B[i], Identity[i], glm::epsilon())) ? 0 : 1;
+ 
+ 		return Error;
+ 	}
diff -Nru glm-0.9.8.4/debian/patches/series glm-0.9.8.4/debian/patches/series
--- glm-0.9.8.4/debian/patches/series	2017-06-24 17:05:01.0 +0200
+++ glm-0.9.8.4/debian/patches/series	2017-10-22 15:07:26.0 +0200
@@ -1,2 +1,3 @@
 Fix-CMake-package-version-file.patch
 fix-infiloop
+870217.patch


Processed: glm: diff for NMU version 0.9.8.4-1.1

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> tags 870217 + patch
Bug #870217 [src:glm] glm: FTBFS with gcc-7: Test failures
Added tag(s) patch.
> tags 870217 + pending
Bug #870217 [src:glm] glm: FTBFS with gcc-7: Test failures
Added tag(s) pending.

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



Bug#879516: [Fwd: Bug#879511: Updating the rrdtool Uploaders list]

2017-10-22 Thread Tobias Frost
Package: rrdtool
Severity: serious
Justification: Policy 3.3 

As per policy:
The email address given in the Maintainer control field must accept
mail from those role accounts in Debian used to send automated mails
regarding the package. 

See attached original email. It seems so that the signing a email with
the GPG key does cause the rejection, but I did not check if this was
the cause. It happened when reporting bug #879511.

--
tobi--- Begin Message ---
The message's content type was not explicitly allowed

--- Begin Message ---
Source: rrdtool
Version: 1.6.0-1
Severity: minor

Sebastian Harl  wishes no longer to be uploader of rrdtool.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.


signature.asc
Description: PGP signature
--- End Message ---
--- End Message ---


Bug#879513: lame will not run at all

2017-10-22 Thread Klaumi Klingsporn
Am / On Sun, 22 Oct 2017 14:01:53 +0100
schrieb / wrote Alex Dekker :

> Since upgrading to lame 3.100-1 yesterday it fails to
> execute with:
> 
> $ lame
> lame: symbol lookup error: lame: undefined symbol:
> lame_get_maximum_number_of_samples
> 
> Tried upgrading to 3.100-2 today and it is the same.
> ...
> Versions of packages lame depends on:
> 
> ii  libmp3lame0  1:3.99.5-0.1
>

Maybe it helps to upgrade libmp3lame0 to 3.100-2 as well?
In this case lame should depend on this version (or above)
of course!

Klaumi


---
Klaus-Michael Klingsporn 
mail: klaumi...@gmx.de
web: www.klaumikli.de



Bug#871094: Patch to fix GCC 7 build failures

2017-10-22 Thread Johannes Brandstätter
tags 871094 + patch
thanks

The attached patch fixes the implicit fallthrough warnings and an
uninitialized variable.--- a/src/bloc.c
+++ b/src/bloc.c
@@ -1249,6 +1249,7 @@
 case MEM_SET_SIZE:
 u32 = args;
 bd->trks = (*u32 + bd->seclen - 1) / bd->seclen + 1;
+__attribute__((fallthrough));
 default:
 ret = -1;
 break;
--- a/src/char.c
+++ b/src/char.c
@@ -154,6 +154,7 @@
 CHARDEV_DPRINTF("one serial port\n");
 register_outd = 1;
 /* No break here */
+__attribute__((fallthrough));
 case CHARDEV_KBD:
 CHARDEV_DPRINTF("one input port %d %d\n", n, i);
 if (i < 16 && chardev_open(cur) == 0) {
@@ -162,6 +163,7 @@
 if (!register_outd)
 break;
 /* No break here */
+__attribute__((fallthrough));
 case CHARDEV_DISPLAY:
 CHARDEV_DPRINTF("one output port %d %d\n", n, j);
 if (j < 16 && chardev_open(cur) == 0) {
@@ -587,6 +589,7 @@
 case ADB_LISTEN:
 memcpy(adb_send + 1, buf, len);
 /* No break here */
+__attribute__((fallthrough));
 case ADB_TALK:
 adb_send[0] = (dev->addr << 4) | cmd | reg;
 break;
--- a/src/libc/src/format.c
+++ b/src/libc/src/format.c
@@ -281,6 +281,7 @@
 goto next;
 }
 /* No break here */
+__attribute__((fallthrough));
 case '1' ... '9':
 switch (maxfill) {
 case -2:
@@ -350,6 +351,7 @@
 goto invalid;
 } else {
 tmp = outc(outf, private, '%', maxlen - totlen);
+__attribute__((fallthrough));
 }
 default:
 invalid:
--- a/src/of.c
+++ b/src/of.c
@@ -3000,7 +3000,7 @@
 {
 OF_env_t *OF_env = OF_env_main;
 OF_node_t *pci_ata = dev;
-OF_node_t *ata, *atas[2];
+OF_node_t *ata, *atas[2] = { NULL };
 int i;
 
 OF_prop_int_new(OF_env, pci_ata, "#address-cells", 1);


Processed: Patch to fix GCC 7 build failures

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 871094 + patch
Bug #871094 [src:openhackware] openhackware: FTBFS: src/bloc.c:1251:18: error: 
this statement may fall through [-Werror=implicit-fallthrough=]
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#879127: marked as done (lwresd is now a dangling symlink when bind9 isn't installed)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 13:04:00 +
with message-id 
and subject line Bug#879127: fixed in bind9 1:9.10.6+dfsg-3
has caused the Debian Bug report #879127,
regarding lwresd is now a dangling symlink when bind9 isn't installed
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.)


-- 
879127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lwresd
Version: 1:9.10.6+dfsg-2
Severity: serious

bind9 (1:9.10.6+dfsg-2) unstable; urgency=medium
...
  * Replace lwresd with symlink instead of hard copy (Closes: #868538)


Unfortunately this created an even bigger problem:
lwresd is now a dangling symlink when bind9 isn't installed.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.6+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Oct 2017 11:08:20 +
Source: bind9
Binary: bind9 bind9utils bind9-doc bind9-host libbind-dev libbind9-141 
libdns190 libirs141 libisc189 liblwres141 libisccc140 libisccfg144 dnsutils 
lwresd libbind-export-dev libdns-export190 libdns-export190-udeb 
libirs-export141 libirs-export141-udeb libisc-export189 libisc-export189-udeb 
libisccc-export140 libisccc-export140-udeb libisccfg-export144 
libisccfg-export144-udeb
Architecture: source
Version: 1:9.10.6+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-141 - BIND9 Shared Library used by BIND
 libdns-export190 - Exported DNS Shared Library
 libdns-export190-udeb - Exported DNS library for debian-installer (udeb)
 libdns190  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export189 - Exported ISC Shared Library
 libisc-export189-udeb - Exported ISC library for debian-installer (udeb)
 libisc189  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export144 - Exported ISC CFG Shared Library
 libisccfg-export144-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg144 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 879127
Changes:
 bind9 (1:9.10.6+dfsg-3) unstable; urgency=medium
 .
   * Make lwresd hard depend on bind9 package (Closes: #879127)
Checksums-Sha1:
 a597bb052b2c498372ccaeb934e540bf51a52e31 3884 bind9_9.10.6+dfsg-3.dsc
 16c0cbfcc019c424414fe6b2ef2ad3b3e0b96a35 84784 
bind9_9.10.6+dfsg-3.debian.tar.xz
 a08962bad8beffdfd6f223a3c01e548be437b60a 18907 
bind9_9.10.6+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 7886b8ec8c5ca5149a6bd52dcae7d2eb393e9ca87f55d332782a8fa82211b13a 3884 
bind9_9.10.6+dfsg-3.dsc
 911bc4809506656173630d25b4f5586c190581d9072f26303c7aaa431efd2c9b 84784 
bind9_9.10.6+dfsg-3.debian.tar.xz
 ff097ad60524718126d0498027ea0546f89e0b0b7e9e8b4f7af9611e70b14162 18907 
bind9_9.10.6+dfsg-3_amd64.buildinfo
Files:
 d9b53c8d56a900d99343c3a78fd9 3884 net optional bind9_9.10.6+dfsg-3.dsc
 18d95750103aa896e2b988db2fb6e382 84784 net optional 
bind9_9.10.6+dfsg-3.debian.tar.xz
 1cc8f5c552ec074023fdb6e24d6fa2c5 18907 net 

Bug#879513: lame will not run at all

2017-10-22 Thread Alex Dekker
Package: lame
Version: 3.100-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since upgrading to lame 3.100-1 yesterday it fails to execute with:

$ lame
lame: symbol lookup error: lame: undefined symbol: 
lame_get_maximum_number_of_samples

Tried upgrading to 3.100-2 today and it is the same.


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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1), 
LANGUAGE=en_GB:en_US:en_GB:en (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lame depends on:
ii  libc62.24-17
ii  libmp3lame0  1:3.99.5-0.1
ii  libsndfile1  1.0.28-4
ii  libtinfo56.0+20170902-1

lame recommends no packages.

Versions of packages lame suggests:
pn  lame-doc  

-- no debconf information



Processed: Merge duplicate FTBFS reports

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 877706 879260
Bug #877706 [src:jakarta-jmeter] FTBFS: error: cannot find symbol 
.autoConnectRetry(getAutoConnectRetry())
Bug #877706 [src:jakarta-jmeter] FTBFS: error: cannot find symbol 
.autoConnectRetry(getAutoConnectRetry())
Marked as found in versions jakarta-jmeter/2.13-3.
Bug #879260 [src:jakarta-jmeter] jakarta-jmeter FTBFS: error: cannot find 
symbol .autoConnectRetry(getAutoConnectRetry())
Merged 877706 879260
> thanks
Stopping processing here.

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



Bug#878896: Patch

2017-10-22 Thread Andreas Stührk
tags 878896 + patch fixed-upstream
thanks

This issue is already fixed upstream. Attached is a patch that fixes the
FTBFS (it's basically upstream
commit bf0640779b2e7095e01755d3660c7e3f0865171d).
Index: liquidsoap-1.1.1/src/decoder/decoder.ml
===
--- liquidsoap-1.1.1.orig/src/decoder/decoder.ml
+++ liquidsoap-1.1.1/src/decoder/decoder.ml
@@ -277,7 +277,7 @@ let get_image_file_decoder filename =
   with
   | Pervasives.Exit -> !ans
 
-exception Exit of stream_decoder
+exception Exit_decoder of stream_decoder
 
 let get_stream_decoder mime kind =
   try
@@ -287,13 +287,13 @@ let get_stream_decoder mime kind =
  match try decoder mime kind with _ -> None with
| Some f ->
log#f 3 "Method %S accepted %S." name mime ;
-   raise (Exit f)
+   raise (Exit_decoder f)
| None -> ()) (get_decoders conf_stream_decoders
stream_decoders);
 log#f 3 "Unable to decode stream of type %S!" mime ;
 None
   with
-| Exit f -> Some f
+| Exit_decoder f -> Some f
 
 (** {1 Helpers for defining decoders} *)
 


Processed: Patch

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 878896 + patch fixed-upstream
Bug #878896 [src:liquidsoap] liquidsoap with OCaml 4.05.0
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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



Bug#878288: marked as done (Stays in synchronising mode after start)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 12:18:54 +
with message-id 
and subject line Bug#878288: fixed in electrum 2.9.3-1
has caused the Debian Bug report #878288,
regarding Stays in synchronising mode after 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.)


-- 
878288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: electrum
Version: 2.7.9-1~bpo8+1
Severity: grave


When I start Electrum, it says “Synchronizing...” and it stays like
that many hours and never finishes that synchronising.

I asked at a channel IRC-called #electrum at freenode. They thought
problem is because this version of Electrum is so old that it probably
can not do segwit serialisation.

Please update this package to the latest upstream version. And create
backport-package, too.


-- System Information:
Debian Release: 8.9
  APT prefers oldstable
  APT policy: (990, 'oldstable'), (500, 'oldstable-updates'), (500, 
'oldstable-proposed-updates')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-0.bpo.3-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages electrum depends on:
ii  python   2.7.9-1
ii  python-electrum  2.7.9-1~bpo8+1
pn  python:any   

Versions of packages electrum recommends:
ii  python-qt4  4.11.2+dfsg-1

Versions of packages electrum suggests:
pn  python-btchip  
pn  python-trezor  
pn  python-zbar

-- no debconf information

-- 
Juhapekka ”naula” Tolvanen ** http colon slash slash iki dot fi slash juhtolv
”Joo, mä vihaan rakkauslauluja. Ilman niitä tää ois iisii. Mä olin ihan
tarpeeks hajalla ennen tätäkin biisii. Mä voisin olla niitä juttuja,
jotka ei jää nimimuistiin. Ehkä me ei koskaan tunneta, ooh, mut silti.” SANNI
--- End Message ---
--- Begin Message ---
Source: electrum
Source-Version: 2.9.3-1

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated electrum package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Nov 2016 14:32:35 +0200
Source: electrum
Binary: python-electrum electrum
Architecture: source
Version: 2.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bitcoin Packaging Team 

Changed-By: Tristan Seligmann 
Description:
 electrum   - Easy to use Bitcoin client
 python-electrum - Easy to use Bitcoin client - Python module
Closes: 870081 875828 878288
Changes:
 electrum (2.9.3-1) unstable; urgency=medium
 .
   * New upstream release (closes: #870081, #875828, #878288).
 - Cold storage signing issue fixed (closes: #870081).
 - Drop slowaes dependency, add pycryptodome + pyaes.
   * Add some other missing dependencies.
   * Fixed a typo ("defaut") in the man page.
   * Update copyright file to properly cover "packages".
Checksums-Sha1:
 f3ca3e522a26b8567910c799deaec5ea181c4544 2044 electrum_2.9.3-1.dsc
 dc4953beb632b34dfedae896c63a67477db9f0f6 2389367 electrum_2.9.3.orig.tar.gz
 7c6053e318863ca5319c1a1fd57b4df9278db12c 13008 electrum_2.9.3-1.debian.tar.xz
 e286180e378d6ca538e5c813c4fcdb86cd23ed26 8526 electrum_2.9.3-1_source.buildinfo
Checksums-Sha256:
 8a9dfb363c64d6ad1b36fc1535f04329ec20e1639ed200d7b9f9ff412d3e891c 2044 
electrum_2.9.3-1.dsc
 c2192d4df6490fdc6e6f9f85b05db0e3915683a016a43ed444ebbc51ccfa0e34 2389367 
electrum_2.9.3.orig.tar.gz
 9f73cab31ca5f4ae57c5ab5905d5db42914ef72f723a802013465d53a7f8ffb9 13008 
electrum_2.9.3-1.debian.tar.xz
 aaae49b7ff0352fade03923c11d8fb43cc53f79a198a42be76bf8e2e382e9c6e 8526 
electrum_2.9.3-1_source.buildinfo
Files:
 578cb29c6d556f31ba4e87198d4a1608 2044 utils optional electrum_2.9.3-1.dsc
 17257d2ee01454283a3324392b85eef5 2389367 utils optional 
electrum_2.9.3.orig.tar.gz
 8e3e7d19d20c3fcf6877b76570e3e653 13008 utils optional 

Processed: softhsm2: diff for NMU version 2.2.0-3.1

2017-10-22 Thread Debian Bug Tracking System
Processing control commands:

> tags 868855 + pending
Bug #868855 [src:softhsm2] softhsm2: FTBFS with cppunit 1.14 (cppunit-config 
removed)
Added tag(s) pending.

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



Processed: tagging 858057, tagging 870266, tagging 851278, tagging 834845

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 858057 + pending
Bug #858057 [src:chicken] chicken: CVE-2017-6949
Added tag(s) pending.
> tags 870266 + pending
Bug #870266 [src:chicken] chicken: CVE-2017-11343
Added tag(s) pending.
> tags 851278 + pending
Bug #851278 [src:chicken] CVE-2016-9954
Added tag(s) pending.
> tags 834845 + pending
Bug #834845 [src:chicken] chicken: CVE-2016-6830 CVE-2016-6831
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#868855: softhsm2: diff for NMU version 2.2.0-3.1

2017-10-22 Thread Tobias Frost
Control: tags 868855 + pending

Dear maintainer,

I've prepared an NMU for softhsm2 (versioned as 2.2.0-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru softhsm2-2.2.0/debian/changelog softhsm2-2.2.0/debian/changelog
--- softhsm2-2.2.0/debian/changelog	2017-02-12 15:12:33.0 +0100
+++ softhsm2-2.2.0/debian/changelog	2017-10-22 13:41:11.0 +0200
@@ -1,3 +1,19 @@
+softhsm2 (2.2.0-3.1) unstable; urgency=medium
+
+  [Tobias Frost ]
+  * Non-maintainer upload.
+  * Import patch from Rene from the BTS.
+  * Lintian warning fixed:
+- Fix VCS-* links in d/control ("right" URL and using https)
+- As package priority extra is obsolete, change it to optional.
+  This fixed transitional-package-should-be-oldlibs-optional and
+  priority-extra-is-replaced-by-priority-optional.
+
+  [ Rene Engelhard ]
+  * use pkg-config instead of cppunit-config for cppunit (Closes: #868855)
+
+ -- Tobias Frost   Sun, 22 Oct 2017 13:41:11 +0200
+
 softhsm2 (2.2.0-3) unstable; urgency=medium
 
   * Replace doc symlink with directory in transitional softhsm package
diff -Nru softhsm2-2.2.0/debian/control softhsm2-2.2.0/debian/control
--- softhsm2-2.2.0/debian/control	2017-02-12 15:12:33.0 +0100
+++ softhsm2-2.2.0/debian/control	2017-10-22 13:41:11.0 +0200
@@ -1,6 +1,6 @@
 Source: softhsm2
 Section: admin
-Priority: extra
+Priority: optional
 Maintainer: Debian DNS Packaging 
 Uploaders: Ondřej Surý 
 Build-Depends: autotools-dev,
@@ -15,8 +15,8 @@
sqlite3
 Standards-Version: 3.9.8
 Homepage: https://www.opendnssec.org/softhsm/
-Vcs-Browser: http://anonscm.debian.org/?p=pkg-dns/softhsm2.git
-Vcs-Git: git://anonscm.debian.org/pkg-dns/softhsm2.git
+Vcs-Browser: https://anonscm.debian.org/cgit/pkg-dns/softhsm2.git
+Vcs-Git: https://anonscm.debian.org/git/pkg-dns/softhsm2.git
 
 Package: softhsm2-common
 Architecture: any
diff -Nru softhsm2-2.2.0/debian/patches/cppunit-pkg-config.diff softhsm2-2.2.0/debian/patches/cppunit-pkg-config.diff
--- softhsm2-2.2.0/debian/patches/cppunit-pkg-config.diff	1970-01-01 01:00:00.0 +0100
+++ softhsm2-2.2.0/debian/patches/cppunit-pkg-config.diff	2017-10-22 13:41:11.0 +0200
@@ -0,0 +1,278 @@
+Description: Fix to detect cppuinits ising pkg-config
+Author: Rene Engelhard 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868855
+Forwarded: no, already applied upstream
+
+--- a/src/lib/crypto/test/Makefile.am
 b/src/lib/crypto/test/Makefile.am
+@@ -9,7 +9,7 @@
+ -I$(srcdir)/../../session_mgr \
+ -I$(srcdir)/../../slot_mgr \
+ @CRYPTO_INCLUDES@ \
+-`cppunit-config --cflags`
++`pkg-config --cflags cppunit`
+ 
+ check_PROGRAMS =		cryptotest
+ 
+@@ -32,7 +32,7 @@
+ 
+ cryptotest_LDADD =		../../libsofthsm_convarch.la
+ 
+-cryptotest_LDFLAGS = 		@CRYPTO_LIBS@ -no-install `cppunit-config --libs`
++cryptotest_LDFLAGS = 		@CRYPTO_LIBS@ -no-install `pkg-config --libs cppunit`
+ 
+ TESTS = 			cryptotest
+ 
+--- a/src/lib/crypto/test/Makefile.in
 b/src/lib/crypto/test/Makefile.in
+@@ -558,7 +558,7 @@
+ -I$(srcdir)/../../session_mgr \
+ -I$(srcdir)/../../slot_mgr \
+ @CRYPTO_INCLUDES@ \
+-`cppunit-config --cflags`
++`pkg-config --cflags cppunit`
+ 
+ cryptotest_SOURCES = cryptotest.cpp \
+ AESTests.cpp \
+@@ -578,7 +578,7 @@
+ randtest.c
+ 
+ cryptotest_LDADD = ../../libsofthsm_convarch.la
+-cryptotest_LDFLAGS = @CRYPTO_LIBS@ -no-install `cppunit-config --libs`
++cryptotest_LDFLAGS = @CRYPTO_LIBS@ -no-install `pkg-config --libs cppunit`
+ EXTRA_DIST = $(srcdir)/*.h
+ all: all-am
+ 
+--- a/src/lib/data_mgr/test/Makefile.am
 b/src/lib/data_mgr/test/Makefile.am
+@@ -9,7 +9,7 @@
+ -I$(srcdir)/../../session_mgr \
+ -I$(srcdir)/../../slot_mgr \
+ @CRYPTO_INCLUDES@ \
+-`cppunit-config --cflags`
++`pkg-config --cflags cppunit`
+ 
+ check_PROGRAMS =		datamgrtest
+ 
+@@ -20,7 +20,7 @@
+ 
+ datamgrtest_LDADD =		../../libsofthsm_convarch.la 
+ 
+-datamgrtest_LDFLAGS = 		@CRYPTO_LIBS@ -no-install `cppunit-config --libs`
++datamgrtest_LDFLAGS = 		@CRYPTO_LIBS@ -no-install `pkg-config --libs cppunit`
+ 
+ TESTS = 			datamgrtest
+ 
+--- a/src/lib/data_mgr/test/Makefile.in
 b/src/lib/data_mgr/test/Makefile.in
+@@ -537,7 +537,7 @@
+ -I$(srcdir)/../../session_mgr \
+ -I$(srcdir)/../../slot_mgr \
+ @CRYPTO_INCLUDES@ \
+-`cppunit-config --cflags`
++`pkg-config --cflags cppunit`
+ 
+ datamgrtest_SOURCES = datamgrtest.cpp \
+ ByteStringTests.cpp \
+@@ -545,7 +545,7 @@
+ SecureDataMgrTests.cpp
+ 
+ datamgrtest_LDADD = ../../libsofthsm_convarch.la 
+-datamgrtest_LDFLAGS = @CRYPTO_LIBS@ -no-install `cppunit-config --libs`
++datamgrtest_LDFLAGS = @CRYPTO_LIBS@ -no-install `pkg-config --libs cppunit`
+ EXTRA_DIST = $(srcdir)/*.h
+ all: all-am
+ 
+--- a/src/lib/handle_mgr/test/Makefile.am
 

Processed: tagging 863884

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 863884 + pending
Bug #863884 [chicken] CVE-2017-9334
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#879488: unzip: contains files licensed only for non-commercial use

2017-10-22 Thread Jonas Smedegaard
Quoting Santiago Vila (2017-10-22 11:41:46)
> On Sun, Oct 22, 2017 at 09:29:16AM +0200, Jonas Smedegaard wrote:
>> unzip.c contains the following notice:
>> 
>>   Copyright on recmatch() from Zip's util.c (although recmatch() was almost
>>   certainly written by Mark Adler...ask me how I can tell :-) ):
>
> Note: This is match.c, not unzip.c.
> 
> The current copyright and license for unzip.c is at the top:
> 
>   Copyright (c) 1990-2005 Info-ZIP.  All rights reserved.
>   
>   See the accompanying file LICENSE, version 2000-Apr-09 or later
>   (the contents of which are also included in unzip.h) for terms of use.
>   If, for some reason, all these files are missing, the Info-ZIP license
>   also may be found at: ftp://ftp.info-zip.org/pub/infozip/license.html
> 
> which of course is DFSG-free.
> 
> What you quoted is the old copyright recmatch() had before it was taken
> from the old util.c and before it was relicensed.
> 
> The copy of recmtach in the unzip package is under Info-Zip license.
> 
> This has been reported before. Please read my reply to the old bug report:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834195#10

Oh. Sorry for not investigating better before reporting.


> So, unless you guys can show that the relicense did not take place,
> or that it was made without the original author's permission,
> this is again a non-bug.

No, I agree there is no bug here.

You might consider explicitly mention above clarification in 
debian/copyright, since evidently I am not alone in (wrongly!) stumbling 
on that confusing really-a-license-but-obsolete.  But I fully understand 
if you feel that is superfluous (especially since I notice that you did 
not find it relevant to use machine-readable copyright file format).

Regards, and sorry again for the hassle.

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



Bug#878348: marked as done (collectd FTBFS with libsigrok 0.5.0)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 11:48:49 +
with message-id 
and subject line Bug#878348: fixed in collectd 5.7.2-2
has caused the Debian Bug report #878348,
regarding collectd FTBFS with libsigrok 0.5.0
to be marked as done.

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

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


-- 
878348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.7.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/collectd.html

...
checking for LIBSIGROK... no
...
configure:40804: checking for LIBSIGROK
configure:40811: $PKG_CONFIG --exists --print-errors "libsigrok < 0.4"
Requested 'libsigrok < 0.4' but version of libsigrok is 0.5.0
--- End Message ---
--- Begin Message ---
Source: collectd
Source-Version: 5.7.2-2

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

Debian distribution maintenance software
pp.
Sebastian Harl  (supplier of updated collectd 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, 22 Oct 2017 00:37:19 +0200
Source: collectd
Binary: collectd-core collectd collectd-utils collectd-dbg collectd-dev 
libcollectdclient-dev libcollectdclient1
Architecture: source
Version: 5.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Harl 
Changed-By: Sebastian Harl 
Description:
 collectd   - statistics collection and monitoring daemon
 collectd-core - statistics collection and monitoring daemon (core system)
 collectd-dbg - statistics collection and monitoring daemon (debugging symbols)
 collectd-dev - statistics collection and monitoring daemon (development files)
 collectd-utils - statistics collection and monitoring daemon (utilities)
 libcollectdclient-dev - client library for collectd's control interface 
(development file
 libcollectdclient1 - client library for collectd's control interface
Closes: 858315 872482 878348
Changes:
 collectd (5.7.2-2) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * debian/patches:
 - Add dpdk-pkg-config.patch: Backport upstream patch to build DPDK with
   pkg-config. This allows DPDK in Debian to fix an upstream multi-arch
   issue, where arch-dependents headers are installed in /usr/include
   breaking multi-arch co-installability of libdpdk-dev. (Closes: #872482)
 .
   [ Sebastian Harl ]
   * Disable the sigrok plugin for now; it's not compatible with libsigrok4;
 thanks to Adrian Bunk for reporting this (Closes: #878348).
   * Enable the write_mongodb plugin, libmongoc is now available. Thanks to
 Saikrishna Arcot for reporting this (Closes: #858315).
 - Add write_mongodb.patch to update the plugin to the most recent upstream
   version to bring it up to date with Debian's libmongoc and fix some
   other issues.
   * Update to standards-version 4.1.1:
 - Build depend on debhelper (>= 9.20160709~) instead of dh-systemd.
 - Use priority "optional" instead of deprecated priority "extra".
   * Disable the varnish plugin for now. collectd FTBFS against varnish 5.2.
 Cf. https://github.com/collectd/collectd/issues/2498 and #879471.
Checksums-Sha1:
 b31676174e5968eab023c5a1830d4563f1270989 3923 collectd_5.7.2-2.dsc
 e98badcb6034b622b4e733f29e74afbe93cb0036 84504 collectd_5.7.2-2.debian.tar.xz
 fa2d6fc556cff3d18ae6fb21224ce0e9332a0cf4 19360 
collectd_5.7.2-2_source.buildinfo
Checksums-Sha256:
 cf4bbcb5be759fd63ed411dda4723a8498c73876dd02781c9d6d89770b06f645 3923 
collectd_5.7.2-2.dsc
 69c53e28cac5baf74e1b8b195331e2bc2b23c57f665efb67f07a64a5ac026dd6 84504 
collectd_5.7.2-2.debian.tar.xz
 de3470b90429d970ea643dfedafdbd9a89856e5c172c2686b863053997fba822 19360 
collectd_5.7.2-2_source.buildinfo
Files:
 2714834e6735436a68797ba9ff3d6896 3923 utils optional collectd_5.7.2-2.dsc
 55df52c18c484068e9c0fce5dfaceab2 84504 utils optional 
collectd_5.7.2-2.debian.tar.xz
 47f0806ce4295579dc3d49ad66003816 19360 utils optional 

Bug#878046: amanda-server: Fails all backups if one or more hosts are down

2017-10-22 Thread Anton Ivanov
I am OK to wait for the upload 

On 22 October 2017 13:26:56 EEST, Jose M Calhariz  wrote:
>That is an old problem of amanda that is solved on v3.5.  But the error
>messages are usually different from what you see.
>
>I have been working on a new package that I should upload very shortly,
>to sid and backports.  If you are dead on water I
>can provide my working in progress packages for stretch on amd64.
>
>Kind regards
>Jose M Calhariz
>
>On 09/10/17 06:55, Anton Ivanov wrote:
>> Package: amanda-server
>> Version: 1:3.3.9-5
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> If one or more backup host is unreachable, the backup of all hosts
>fails.
>>
>> Example - backing up two hosts - smaug and TerriblTerror:
>>
>> If the latter is unreachable
>>
>>   TerribleTerror1 /etc lev 0  FAILED [Request to TerribleTerror1
>failed: Connection timed out]
>>
>> The former (and all other hosts in the backup sequence) fail with:
>>
>>   smaug /exports/md0/home/aivanov lev 0  FAILED [Request to smaug
>failed: error sending REQ: write error to: Broken pipe]
>>
>> -- System Information:
>> Debian Release: 9.0
>>   APT prefers stable
>>   APT policy: (500, 'stable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8),
>LANGUAGE=en_GB:en (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages amanda-server depends on:
>> ii  amanda-common  1:3.3.9-5
>> ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
>> ii  libc6  2.24-11+deb9u1
>> ii  libcurl3   7.52.1-5
>> ii  libglib2.0-0   2.50.3-2
>> ii  libssl1.1  1.1.0f-3
>> ii  perl   5.24.1-3
>>
>> amanda-server recommends no packages.
>>
>> Versions of packages amanda-server suggests:
>> ii  amanda-client  1:3.3.9-5
>> ii  cpio   2.11+dfsg-6
>> ii  gnuplot5.0.5+dfsg1-6
>> ii  mt-st  1.3-1
>>
>> -- no debconf information

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Processed: Re: Bug#875708: [mytop] missing libconfig-inifiles-perl

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 875708 important
Bug #875708 [mariadb-client-10.1] [mytop] missing libconfig-inifiles-perl
Severity set to 'important' from 'serious'
> thank you
Stopping processing here.

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



Bug#875708: [mytop] missing libconfig-inifiles-perl

2017-10-22 Thread Ondřej Surý
severity 875708 important
thank you

mytop is a minor script and there's easy workaround, so I am setting this
as important. And I will fix this in next mariadb-10.1 update in unstable
and stable.

Also please not that it's the maintainer of the package who makes the
ultimate decision on the package severity.

Ondrej.

On Sun, 22 Oct 2017 at 15:03 Jörg Frings-Fürst 
wrote:

> severity 875708 serious
> thanks
>
> Hallo Daniel,
>
>
> Am Donnerstag, den 12.10.2017, 21:17 +0200 schrieb Daniel Baumann:
> > severity 875708 normal
> > thanks
> >
> > Hi,
> >
> > this hardly qualifies as a serious - not everybody is using mytop and
> > mytop is not a core functionality of the mariadb-client-10.1 package.
> > pulling in libconfig-inifiles-perl unconditionally on all systems is
> > thus unecessary bloat.
> >
> [...]
>
> its not hardly, its real. Mytop can't work without libconfig-inifiles-
> perl. So it must by declare as with Depends. From [1]:
>
> [qoute]
> The Depends field should be used if the depended-on package is required
> for the depending package to provide a significant amount of
> functionality.
> [/quote]
>
>
> And a missing dependency is an RC-Bug. From[2]:
>
> [quote]
> serious
> is a severe violation of Debian policy (roughly, it violates a "must"
> or "required" directive), or, in the package maintainer's or release
> manager's opinion, makes the package unsuitable for release.
> [/quote]
>
> > if at all, libconfig-inifiles-perl should rather be in recommends, not
> > depends. imho better suited in suggests only though.
> >
> > Regards,
> > Daniel
> >
>
> CU
> Jörg
>
> [1]
> https://www.debian.org/doc/debian-policy/#binary-dependencies-depends-recommends-suggests-enhances-pre-depends
> [2] https://www.debian.org/Bugs/Developer.en.html#severities
>
> --
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
>
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
>
> Jörg Frings-Fürst
> D-54470 Lieser
>
> Threema: SYR8SJXB
> Wire:  @joergfringsfuerst
> Skype: joergpenguin
> Ring:  jff
>
> IRC: j_...@freenode.net
>  j_...@oftc.net
>
> My wish list:
>  - Please send me a picture from the nature at your home.
>
-- 
Ondřej Surý 


Bug#849832: No longer affects FF55/56

2017-10-22 Thread Carsten Schoenert
Hello Gregor,

On Fri, Oct 13, 2017 at 08:52:32AM +0200, Gregor Riepl wrote:
> According to https://bugzilla.mozilla.org/show_bug.cgi?id=1357323 ,
> this bug should no longer affect Firefox 55 and 56, as the gonk code was
> removed from the tree.
> 
> Please confirm.

the problem is not that the related files are removed by Mozilla in the
between times. The real issue is now we have tarballs in the archive
which contains that non DFSG compatible files. That's why this report
is still open.

Feel free to take action here and contact the ftp team to request the
removal of the related tarballs.

Regrads
Carsten



Processed: notfound 849832 in thunderbird/1:52.4.0-1

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 849832 thunderbird/1:52.4.0-1
Bug #849832 [icedove] firefox: contains JSHint work under non-free licence
Ignoring request to alter found versions of bug #849832 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: notfound 855344 in thunderbird/1:52.4.0-1

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 855344 thunderbird/1:52.4.0-1
Bug #855344 {Done: Carsten Schoenert } [icedove] 
thunderbird: retains mails from removed IMAP accounts
Ignoring request to alter found versions of bug #855344 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: notfound 861840 in thunderbird/1:52.4.0-1

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 861840 thunderbird/1:52.4.0-1
Bug #861840 {Done: Carsten Schoenert } 
[calendar-google-provider] thunderbird: gmail authentication broken
Ignoring request to alter found versions of bug #861840 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: Re: Bug#875708: [mytop] missing libconfig-inifiles-perl

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 875708 serious
Bug #875708 [mariadb-client-10.1] [mytop] missing libconfig-inifiles-perl
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#878426: marked as done (odil FTBFS with Python 3.6 as default)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 10:49:24 +
with message-id 
and subject line Bug#878426: fixed in odil 0.8.0-4
has caused the Debian Bug report #878426,
regarding odil FTBFS with Python 3.6 as 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.)


-- 
878426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odil
Version: 0.8.0-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/odil.html

...
   debian/rules override_dh_install-arch
make[1]: Entering directory '/build/1st/odil-0.8.0'
dh_install
dh_install: Cannot find (any matches for) "build-py3.5/wrappers/odil.so" (tried 
in ., debian/tmp)

dh_install: python3-odil missing files: build-py3.5/wrappers/odil.so
dh_install: missing files, aborting
debian/rules:68: recipe for target 'override_dh_install-arch' failed
make[1]: *** [override_dh_install-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: odil
Source-Version: 0.8.0-4

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

Debian distribution maintenance software
pp.
Julien Lamy  (supplier of updated odil 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, 22 Oct 2017 11:30:35 +0200
Source: odil
Binary: libodil0 libodil-dev libodil-doc python-odil python3-odil odil
Architecture: source
Version: 0.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Lamy 
Description:
 libodil-dev - C++11 library for the DICOM standard (development files)
 libodil-doc - C++11 library for the DICOM standard (documentation)
 libodil0   - C++11 library for the DICOM standard
 odil   - C++11 library for the DICOM standard (application)
 python-odil - C++11 library for the DICOM standard (Python wrappers)
 python3-odil - C++11 library for the DICOM standard (Python 3 wrappers)
Closes: 878426
Changes:
 odil (0.8.0-4) unstable; urgency=medium
 .
   * Fix install of Python files (Closes: #878426)
   * Update standards version
Checksums-Sha1:
 f843003bb6477db0d90cbd9bd6a0bb6c4ffedf13 2581 odil_0.8.0-4.dsc
 2ffd13ced1004d89a0a6175d806e1ab5e5d164c9 15916 odil_0.8.0-4.debian.tar.xz
 79608ddab0056a9a31acf5e10b0bd83960e3517f 8183 odil_0.8.0-4_source.buildinfo
Checksums-Sha256:
 5c2aeccfc92f1ea0b47f0f1e0b66c7687cbe7e0a6e399fe81b485d4b1acea996 2581 
odil_0.8.0-4.dsc
 034c918bac9344308dde553371607526e531df0cb74bd05aebc79ae870d4e472 15916 
odil_0.8.0-4.debian.tar.xz
 5312e19e27752ee779c19047489f6d1e5fc31343937a7271ad48c015f4a2365f 8183 
odil_0.8.0-4_source.buildinfo
Files:
 5368208e08020940775565070397711e 2581 science optional odil_0.8.0-4.dsc
 31f6d966c7bb4b66eb5648cb8048fba0 15916 science optional 
odil_0.8.0-4.debian.tar.xz
 04bcf3e0e991cd9de5af20d596cce63e 8183 science optional 
odil_0.8.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6rcjomb2J+aAVWFfWbIwbzr53cEFAlnsc5QQHGFmaWZAZGVi
aWFuLm9yZwAKCRBZsjBvOvndwXLfEAC3+wo7USBiO8PBwc/j0xWtdlQonWdCFAkX
3nQhEkoDRRxJVpZpKOlOXwI6LTa4mEItnHttDbu1VJYBt3DHHcH6fSgEbhsqck9M
p6v/YR6X+bfR2bozfX632tRGuoB2H8wndjITn/va5ssABf/NBzU17EHHxpV6brWT
N4pgiDanozGrRDZ6YixPUICTKMd+huqQDj9H27WpY4FjZeXQSajBQ0pe8H9R3vhb
K/CZe58wR4CbeYnaYocaOagsUmsA2v5dwFVJmDJ07T4mrPCwuwwSqcO+VsVZA//i
8eNWTVr/0NOcuEVPbQ33Aa18LGKOcM7Y59uCy+OCmhNO4hXEr0ZuRTPOs/gxNCG2
Ar2YkD8KUklLviB8GEtEGpfhl1B3/EViersd0873CEFTwlDa5s3A5mD0ZPRnV8tR
TsfVZ1Tg4b/PzqPaOxrNDghSTLFWtNuve3VVA0jYhTfwwEzMA99Bn6/18oOTlVv/
+K9IQ92ZxbToWHTSx1RGZ6pVLmNQZJ2zMQVlE7LQ/E8PpMrVpLzip9Obc9U5xLr8
zXRPdq/P8kMHLlDkCIXVlMyefpeWeazbbl7PNQSLOh+bOxr5IfmcWP2jBt/aiJCO
D0hsW6LZgWOxMUwYeCE5QguHuMz9YaI3RMaG+DEU6TqinZBJVlI+9TilIRTOvzFf
piRq537YUA==
=m8Jv
-END PGP SIGNATURE End Message ---


Bug#878046: amanda-server: Fails all backups if one or more hosts are down

2017-10-22 Thread Jose M Calhariz
That is an old problem of amanda that is solved on v3.5.  But the error
messages are usually different from what you see.

I have been working on a new package that I should upload very shortly,
to sid and backports.  If you are dead on water I
can provide my working in progress packages for stretch on amd64.

Kind regards
Jose M Calhariz

On 09/10/17 06:55, Anton Ivanov wrote:
> Package: amanda-server
> Version: 1:3.3.9-5
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> If one or more backup host is unreachable, the backup of all hosts fails.
>
> Example - backing up two hosts - smaug and TerriblTerror:
>
> If the latter is unreachable
>
>   TerribleTerror1 /etc lev 0  FAILED [Request to TerribleTerror1 failed: 
> Connection timed out]
>
> The former (and all other hosts in the backup sequence) fail with:
>
>   smaug /exports/md0/home/aivanov lev 0  FAILED [Request to smaug failed: 
> error sending REQ: write error to: Broken pipe]
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages amanda-server depends on:
> ii  amanda-common  1:3.3.9-5
> ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
> ii  libc6  2.24-11+deb9u1
> ii  libcurl3   7.52.1-5
> ii  libglib2.0-0   2.50.3-2
> ii  libssl1.1  1.1.0f-3
> ii  perl   5.24.1-3
>
> amanda-server recommends no packages.
>
> Versions of packages amanda-server suggests:
> ii  amanda-client  1:3.3.9-5
> ii  cpio   2.11+dfsg-6
> ii  gnuplot5.0.5+dfsg1-6
> ii  mt-st  1.3-1
>
> -- no debconf information





signature.asc
Description: OpenPGP digital signature


Bug#878348: collectd FTBFS with libsigrok 0.5.0

2017-10-22 Thread Sebastian Harl
Hi,

On Sun, Oct 22, 2017 at 09:49:43AM +0200, Michael Stapelberg wrote:
> Adrian Bunk  writes:
> > Source: collectd
> > Version: 5.7.2-1
> > Severity: serious
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/collectd.html
> >
> > ...
> > checking for LIBSIGROK... no
> > ...
> > configure:40804: checking for LIBSIGROK
> > configure:40811: $PKG_CONFIG --exists --print-errors "libsigrok < 0.4"
> > Requested 'libsigrok < 0.4' but version of libsigrok is 0.5.0
> 
> tokkee, are you on top of this? This bug marks freeradius for
> auto-removal from testing. If you need help with a fix, please let me
> know.

Yes, I have a pending upload to fix it. Thanks for the ping.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature


Bug#879488: unzip: contains files licensed only for non-commercial use

2017-10-22 Thread Santiago Vila
I forgot to answer to the second part of your report:

> The file COPYING.OLD similarly contains this notice:
>
> The following copyright applied to the Windows DLL code (windll/*),
> distributed with UnZip version 5.2 and later:

The file COPYING.OLD says this at the top:

 This file contains some details about the copyright history of
 contributions to the UnZip project.

So, as before, this is included for historical purposes only
(note the usage of "applied" which means *past* in English).

Those are clearly not the current license terms.

Thanks.



Bug#867376: Processed: Re: Bug#867376 closed by Alexander GQ Gerasiov <g...@debian.org> (Bug#867376: fixed in uncrustify 0.65+git20170831+dfsg1-1)

2017-10-22 Thread Alexander Gerasiov
Hello Julien,

On Fri, 1 Sep 2017 17:53:03 +0200
Julien Cristau  wrote:

> On 09/01/2017 12:57 AM, Alexander Gerasiov wrote:
> > Hello Julien,
> > 
> > On Thu, 31 Aug 2017 22:15:04 +
> > ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> >   
> >> This bug was not a request for packaging a new upstream version, so
> >> this changelog entry isn't appropriate.  
> > Could you please explain your point?
> > 
> > There was several bugs in upstream code which leads to incorrect
> > behavior on some architectures.
> > We have fixed them in current upstream code, and current upstream
> > version was uploaded into archive. This really fixes #867376, you
> > can see this on
> > https://buildd.debian.org/status/package.php?p=uncrustify 
> What I mean is that when closing bugs in your changelog entry, it
> should actually describe what fixes the bug.  So "New upstream
> release (closes: #nnn)" implies that #nnn was about packaging a new
> upstream release. "Fix vanilla flavor to not taste like chocolate
> (closes: #mmm)" implies that #mmm is about something being wrong with
> the vanilla flavor of ice cream.
Ah, totally lost this mail, so reply just now.

In generally I agree with you, that changelog should be meaningful.
But in this case you're wrong (from my point of view).

We have sigfault in the app.
User reports "%appname segfault when %something"
I look through the code and see pointer dereference, so I create commit
not with "Fix sigfault", but with "Do some checks on pointer
dereference when ... This should fix #issuenumber".

Or may be you mean, that I should write
"New upstream release. Fixes disk overflow on some archs. (Closes:
#number)" There is some good point in this, I agree, but still no
reason to reopen the bug, I think. =)

-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: g...@cs.msu.su  Homepage: http://gerasiov.net  Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1



Bug#879488: marked as done (unzip: contains files licensed only for non-commercial use)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 11:41:46 +0200
with message-id <20171022094146.qanxxkowgvtpnoqk@nuc>
and subject line Re: Bug#879488: unzip: contains files licensed only for 
non-commercial use
has caused the Debian Bug report #879488,
regarding unzip: contains files licensed only for non-commercial use
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.)


-- 
879488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unzip
Version: 6.0-21
Severity: serious
Tags: upstream
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

unzip.c contains the following notice:

  Copyright on recmatch() from Zip's util.c (although recmatch() was almost
  certainly written by Mark Adler...ask me how I can tell :-) ):

 Copyright (C) 1990-1992 Mark Adler, Richard B. Wales, Jean-loup Gailly,
 Kai Uwe Rommel and Igor Mandrichenko.

 Permission is granted to any individual or institution to use, copy,
 or redistribute this software so long as all of the original files are
 included unmodified, that it is not sold for profit, and that this copy-
 right notice is retained.

The file COPYING.OLD similarly contains this notice:

   The following copyright applied to the Windows DLL code (windll/*),
   distributed with UnZip version 5.2 and later:

 * Copyright (c) 1996 Mike White.
 * Permission is granted to any individual or institution to use,
 * copy, or redistribute this software so long as all of the original
 * files are included, that it is not sold for profit, and that this
 * copyright notice is retained.

In both cases the phrase "not sold for profit" makes the license non-DFSG-free.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlnsSMkACgkQLHwxRsGg
ASFPRQ/+LCfq1MayfP8Oq50b6Ud+mPlQ3ZtV/YW7a5Uoi7QOQ1fBAyYMSWsZAfVY
UjSU6AgJRiACgkBty8KRSL1uuQIYZLPc3npgKyywsAtPUlpUYwh0MGj9GEgkqkCS
DVtXiR2L6NhK70+bYrFzzQzelRApgFRWnwCI7+n79ZWj8ZraAMYLLIwQ1EI62fuy
wgV2jdQWh4Cyb+ntckoGCFMiRzH2ABBMtPN8AMBGulZWePAHxT2f91L54KB1DVvr
XUCMHUPZt8VzG4qsyF25uMxqpaGDEL5FIiY7fqTfza+UswPhqLFC1WFHPU+fl3vf
cOl8A2YK1FFjIC2qCiCNVixwk38IUhyL9NVj0ntN4MjaB+L8TYr2GaxCeEut58v2
36F9IXZODj3941d7v2B9UZ7qpalKKMpiVW+jO+I16BlzDNy57LN8Gqjo07thaB9B
Ga6YUKabNiUh6IzQ54s2i5JfLsi6k+Oqh8v93mlm+uoiptaxO7dXl3etQD/R6IwN
ZDiXWbgPB2TqfmXecNvgthPgfXItE7NMaIXSQPWv2FrkGVRyLGppqQmyHCxG3p9v
l+YCiKHoBrCzfISCTpl1By6UMTgbQq1IEa25O7l6KwsDV7Y4NSinavlp8265ER59
rTZDQITU7y/vXoG1WrSq3O7IHEXgMh2OcW1MYYcl/w/kHUcXBwk=
=XkK+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Sun, Oct 22, 2017 at 09:29:16AM +0200, Jonas Smedegaard wrote:
> Package: unzip
> Version: 6.0-21
> Severity: serious
> Tags: upstream
> Justification: Policy 2.1
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> unzip.c contains the following notice:
> 
>   Copyright on recmatch() from Zip's util.c (although recmatch() was almost
>   certainly written by Mark Adler...ask me how I can tell :-) ):

Note: This is match.c, not unzip.c.

The current copyright and license for unzip.c is at the top:

  Copyright (c) 1990-2005 Info-ZIP.  All rights reserved.
  
  See the accompanying file LICENSE, version 2000-Apr-09 or later
  (the contents of which are also included in unzip.h) for terms of use.
  If, for some reason, all these files are missing, the Info-ZIP license
  also may be found at: ftp://ftp.info-zip.org/pub/infozip/license.html

which of course is DFSG-free.

What you quoted is the old copyright recmatch() had before it was taken
from the old util.c and before it was relicensed.

The copy of recmtach in the unzip package is under Info-Zip license.

This has been reported before. Please read my reply to the old bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834195#10

So, unless you guys can show that the relicense did not take place,
or that it was made without the original author's permission,
this is again a non-bug.

Thanks.--- End Message ---


Bug#853372: marked as done (desmume: ftbfs with GCC-7)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 09:48:45 +
with message-id 
and subject line Bug#853372: fixed in desmume 0.9.11-3
has caused the Debian Bug report #853372,
regarding desmume: ftbfs with GCC-7
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.)


-- 
853372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:desmume
Version: 0.9.11-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/desmume_0.9.11-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 ^
utils/xstring.cpp:346:25: warning: narrowing conversion of 
'int)converted[1]) << 4) | (((int)converted[2]) >> 2))' from 'int' to 
'unsigned char' inside { } [-Wnarrowing]
 (converted[1] << 4) | (converted[2] >> 2),
 ^
utils/xstring.cpp:347:25: warning: narrowing conversion of 
'int)converted[2]) << 6) | ((int)converted[3]))' from 'int' to 'unsigned 
char' inside { } [-Wnarrowing]
 (converted[2] << 6) | (converted[3])
 ^~~~
g++ -DPACKAGE_NAME=\"desmume\" -DPACKAGE_TARNAME=\"desmume\" 
-DPACKAGE_VERSION=\"svn\" -DPACKAGE_STRING=\"desmume\ svn\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"desmume\" 
-DVERSION=\"svn\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSVN_REV=0 
-DSVN_REV_STR=\"0\" -DHAVE_LIBZ=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1 
-DHAVE_LIBDL=1 -DHAVE_LIBGL=1 -DHAVE_LIBOSMESA=1 
-DGLADEUI_UNINSTALLED_DIR=\"/<>/src/gtk-glade/glade/\" 
-DGTKGLEXT_AVAILABLE=1 -DHAVE_LIBSOUNDTOUCH=1 -DGETTEXT_PACKAGE=\"desmume\" 
-DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 
-DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_JIT=1 -DHOST_LINUX=1 
-DHOST_64=1 -DGDB_STUB=1 -I.  -I../src -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/
 alsa -I/usr/include/agg2 -I/usr/include/soundtouch  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
utils/decrypt/crc.o utils/decrypt/crc.cpp
g++ -DPACKAGE_NAME=\"desmume\" -DPACKAGE_TARNAME=\"desmume\" 
-DPACKAGE_VERSION=\"svn\" -DPACKAGE_STRING=\"desmume\ svn\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"desmume\" 
-DVERSION=\"svn\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSVN_REV=0 
-DSVN_REV_STR=\"0\" -DHAVE_LIBZ=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1 
-DHAVE_LIBDL=1 -DHAVE_LIBGL=1 -DHAVE_LIBOSMESA=1 
-DGLADEUI_UNINSTALLED_DIR=\"/<>/src/gtk-glade/glade/\" 
-DGTKGLEXT_AVAILABLE=1 -DHAVE_LIBSOUNDTOUCH=1 -DGETTEXT_PACKAGE=\"desmume\" 
-DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 
-DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_JIT=1 -DHOST_LINUX=1 
-DHOST_64=1 -DGDB_STUB=1 -I.  -I../src -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/
 alsa -I/usr/include/agg2 -I/usr/include/soundtouch  -Wdate-time 

Bug#879488: unzip: contains files licensed only for non-commercial use

2017-10-22 Thread Francesco Poli
On Sun, 22 Oct 2017 10:57:41 +0200 Francesco Poli wrote:

> On Sun, 22 Oct 2017 09:29:16 +0200 Jonas Smedegaard wrote:
> 
> [...]
> >  Permission is granted to any individual or institution to use, copy,
>  ^^
> >  or redistribute this software so long as all of the original files are
>^^^
> >  included unmodified, that it is not sold for profit, and that this 
> > copy-
>^^^
> >  right notice is retained.
> [...]
> > In both cases the phrase "not sold for profit" makes the license 
> > non-DFSG-free.
> 
> Agreed.
> 
> Moreover, the first case seems to also lack any permission to modify
> (thus failing DFSG#3)...

Well, on a second glance, the second case also seems to lack permission
to modify:

[...]
> >* Permission is granted to any individual or institution to use,
   
> >* copy, or redistribute this software so long as all of the original
 ^  ^^^
> >* files are included, that it is not sold for profit, and that this
 ^^
> >* copyright notice is retained.
[...]




-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp_JMbimO_Jo.pgp
Description: PGP signature


Bug#867003: marked as done (libgd2 FTBFS: test failures)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 09:33:43 +
with message-id 
and subject line Bug#867003: fixed in libgd2 2.2.5-4
has caused the Debian Bug report #867003,
regarding libgd2 FTBFS: test failures
to be marked as done.

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

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


-- 
867003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.2.4-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes libgd2 FTBFS:

https://tests.reproducible-builds.org/debian/history/libgd2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgd2.html

...

   GD 2.2.4: tests/test-suite.log


# TOTAL: 153
# PASS:  151
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: freetype/bug00132
===

freetype/bug00132.c:31: Total pixels changed: 9 with a maximum channel 
difference of 255.
freetype/bug00132.c:33: Reference image and destination differ
FAIL freetype/bug00132 (exit status: 1)

FAIL: gdimagestringft/gdimagestringft_bbox
==

gdimagestringft/gdimagestringft_bbox.c:60: (491, 364) (613, 313) (602, 288) 
(481, 338) expected, but (491, 364) (613, 313) (602, 288) (480, 339)
FAIL gdimagestringft/gdimagestringft_bbox (exit status: 1)


Testsuite summary for GD 2.2.4

# TOTAL: 153
# PASS:  151
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to https://github.com/libgd/libgd/issues

Makefile:3782: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.5-4

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libgd2 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, 22 Oct 2017 11:14:32 +0200
Source: libgd2
Binary: libgd-tools libgd-dev libgd3
Architecture: source
Version: 2.2.5-4
Distribution: unstable
Urgency: medium
Maintainer: GD team 
Changed-By: Ondřej Surý 
Description:
 libgd-dev  - GD Graphics Library (development version)
 libgd-tools - GD command line tools and example code
 libgd3 - GD Graphics Library
Closes: 867003 879254
Changes:
 libgd2 (2.2.5-4) unstable; urgency=medium
 .
   [ Jiří Paleček ]
   * Disable the test during build and run the testsuite through autopkgtest
 (Closes: #867003)
   * Make --as-needed work again
 .
   [ Ondřej Surý ]
   * Get rid of libgd2*-dev traces (Closes: #879254)
Checksums-Sha1:
 628258c9d6e8130edd51181a0ab7e197cf5b1297 2364 libgd2_2.2.5-4.dsc
 00e07adec1eb2b7e453261323063dbae2e39e809 31848 libgd2_2.2.5-4.debian.tar.xz
 0446df0f10a5b735c9caa56d24ee760e0dce6291 8033 libgd2_2.2.5-4_amd64.buildinfo
Checksums-Sha256:
 b76b58ce9eb596198a36eed9538d421ae7828c2f9f9bb063307f945e8c2ba40b 2364 
libgd2_2.2.5-4.dsc
 7bccfea19f47ecfb095f3f11343e3f607e60c0731fd28d4cc23d63c177e06119 31848 
libgd2_2.2.5-4.debian.tar.xz
 7db6b0a6b03f50c67c695dbe9f3127ccf8d4f33f9f1be0603aec0a4b2a8bf640 8033 
libgd2_2.2.5-4_amd64.buildinfo
Files:
 92fd692f9dec2ee85b24cde90411f04c 2364 graphics optional libgd2_2.2.5-4.dsc
 27daae06c62e20ca09936e971b4f022e 31848 graphics optional 
libgd2_2.2.5-4.debian.tar.xz
 5421f788e22aa2c3add542c706acc9cb 8033 graphics optional 
libgd2_2.2.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlnsYyZfFIAALgAo

Bug#879254: marked as done (libgd2: FTBFS: Requested unknown package libgd2-xpm-dev via -p/--package)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 09:33:43 +
with message-id 
and subject line Bug#879254: fixed in libgd2 2.2.5-4
has caused the Debian Bug report #879254,
regarding libgd2: FTBFS: Requested unknown package libgd2-xpm-dev via 
-p/--package
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.)


-- 
879254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.2.5-3
Severity: serious

>From my pbuilder log log:

...
   debian/rules override_dh_install
make[1]: Entering directory '/build/libgd2-2.2.5'
dh_install --fail-missing -Xlibgd.la -Xgdlib-config
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
make[1]: Leaving directory '/build/libgd2-2.2.5'
  debian/rules override_dh_installdocs
make[1]: Entering directory '/build/libgd2-2.2.5'
dh_installdocs -plibgd2-xpm-dev -plibgd2-noxpm-dev --link-doc=libgd-dev
dh_installdocs: Requested unknown package libgd2-xpm-dev via
-p/--package, expected one of: libgd-tools libgd-dev libgd3
dh_installdocs: Requested unknown package libgd2-noxpm-dev via
-p/--package, expected one of: libgd-tools libgd-dev libgd3
dh_installdocs: unknown option or error during option parsing; aborting
debian/rules:32: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 25
make[1]: Leaving directory '/build/libgd2-2.2.5'
debian/rules:23: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.5-4

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libgd2 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, 22 Oct 2017 11:14:32 +0200
Source: libgd2
Binary: libgd-tools libgd-dev libgd3
Architecture: source
Version: 2.2.5-4
Distribution: unstable
Urgency: medium
Maintainer: GD team 
Changed-By: Ondřej Surý 
Description:
 libgd-dev  - GD Graphics Library (development version)
 libgd-tools - GD command line tools and example code
 libgd3 - GD Graphics Library
Closes: 867003 879254
Changes:
 libgd2 (2.2.5-4) unstable; urgency=medium
 .
   [ Jiří Paleček ]
   * Disable the test during build and run the testsuite through autopkgtest
 (Closes: #867003)
   * Make --as-needed work again
 .
   [ Ondřej Surý ]
   * Get rid of libgd2*-dev traces (Closes: #879254)
Checksums-Sha1:
 628258c9d6e8130edd51181a0ab7e197cf5b1297 2364 libgd2_2.2.5-4.dsc
 00e07adec1eb2b7e453261323063dbae2e39e809 31848 libgd2_2.2.5-4.debian.tar.xz
 0446df0f10a5b735c9caa56d24ee760e0dce6291 8033 libgd2_2.2.5-4_amd64.buildinfo
Checksums-Sha256:
 b76b58ce9eb596198a36eed9538d421ae7828c2f9f9bb063307f945e8c2ba40b 2364 
libgd2_2.2.5-4.dsc
 7bccfea19f47ecfb095f3f11343e3f607e60c0731fd28d4cc23d63c177e06119 31848 
libgd2_2.2.5-4.debian.tar.xz
 7db6b0a6b03f50c67c695dbe9f3127ccf8d4f33f9f1be0603aec0a4b2a8bf640 8033 
libgd2_2.2.5-4_amd64.buildinfo
Files:
 92fd692f9dec2ee85b24cde90411f04c 2364 graphics optional libgd2_2.2.5-4.dsc
 27daae06c62e20ca09936e971b4f022e 31848 graphics optional 
libgd2_2.2.5-4.debian.tar.xz
 5421f788e22aa2c3add542c706acc9cb 8033 graphics optional 
libgd2_2.2.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlnsYyZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDMw
QjkzM0Q4MEZDRTNEOTgxQTJEMzhGQjBDOTlCNzBFRjRGQ0JCMDcACgkQDJm3DvT8
uwcCPxAAqiGFbt9AKM69vm1BI9j+4kBUZVtV08qiI2k5Y3R8hlCSRlYX4MtOnyPr
qoIvYT/i+Jqj0Fo97py9pkJ2wKQjMM60C6ghk0TgXPY5lu+Mt7XLfy0Irbd5O5J+
WDJhXK77guZFVYCfgXZFMZtXdab97xftVAxELWv0BOc9TRDr/GkiwZwwz6bicpFd
dWAvTrcf1xUSh6kl9Y01EZSDLicoE3ZFeo5a0Hr/yrQUObEywJL56AxYZz1RyoeX

Bug#879478: marked as done (debhelper: dh_testroot regression: relies on debian/control)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 09:18:41 +
with message-id 
and subject line Bug#879478: fixed in debhelper 10.10.1
has caused the Debian Bug report #879478,
regarding debhelper: dh_testroot regression: relies on debian/control
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.)


-- 
879478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 10.10
Severity: serious
Tags: d-i
Justification: triggers FTBFS

[ Please keep both debian-boot@ and myself in the loop, thanks. ]

Hi,

debian-installer uses compat 7, a build/ directory, and its daily-build
script is started from this directory. Makefiles use dh_testroot from
that directory, and starting with 10.10, the build is broken because of:
| dh_testroot: "debian/control" not found. Are you sure you are in the correct 
directory?

The changes were obvious since 10.9.2 (known good), but I've confirmed
anyway (through bisection) that it's caused by:
| commit 087be1a300581b989aa38227693a8a6f112408f9 (refs/bisect/bad)
| Author: Niels Thykier 
| Date:   Sat Sep 16 14:51:53 2017 +
| 
| Add minimal R³ support for debhelper
| 
| Signed-off-by: Niels Thykier 

It seems to me that's due to the getpackages call addition, but I don't
think it's reasonable for debhelper to break compat 7 this way. Also,
even if one might object d-i is abusing dh_testroot (or using it
incorrectly), its documented purpose is:
| dh_testroot simply checks to see if you are root. If not, it exits
| with an error. Debian packages must be built as root, though you can
| use fakeroot(1)


KiBi.
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 10.10.1

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 22 Oct 2017 09:00:12 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 10.10.1
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 879478
Changes:
 debhelper (10.10.1) unstable; urgency=medium
 .
   * debhelper.pod: Document that all tools by default must be run
 in the root of an unpacked source.
   * dh: Clarify that --list can be run anywhere.
   * dh_testroot: Temporarily cope with being run outside a source
 root.  (Closes: #879478)
   * dh_testroot: Update manpage to mention its new scope.
   * d/control: Bump (build-)dependency on dpkg to 1.19.0.3~.  That
 was technically necessary already in the previous upload.
Checksums-Sha1:
 8308af126c9f3a7215a1a33ce01fe1040f2ad956 1795 debhelper_10.10.1.dsc
 55fa0f20f7752d6235ef42ec35297322fd4239c4 427780 debhelper_10.10.1.tar.xz
 8550deb017b68a01b61c5ee183b539c2edafcdc1 4506 
debhelper_10.10.1_source.buildinfo
Checksums-Sha256:
 d61ff70119c56aa1a45ddb53af8e153e60a30f35e15000b30a0290c867a0db90 1795 
debhelper_10.10.1.dsc
 3de4d8824c80b63ec35bf1f5d3f5c3e09699fc77587ea34338f2903d0ccc 427780 
debhelper_10.10.1.tar.xz
 c3d5976dd9e5600f8f655f0e7e60d28d8ba9eb0438ca04e97d46f404bc954cbf 4506 
debhelper_10.10.1_source.buildinfo
Files:
 0636cb917e9a6ca6d6a4a86722d88f58 1795 devel optional debhelper_10.10.1.dsc
 596b38a6c21f4419a632d090d5e99a00 427780 devel optional debhelper_10.10.1.tar.xz
 8028a328540c198c7175c55887043494 4506 devel optional 
debhelper_10.10.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlnsXosACgkQBUu7n32A
ZEK+2g/+J3GfkWsRMEhGdcGq801fzzwxtV8emPhOJ6Ut8+NJleMWyV3i4Jo68mN/
LW/OkCXKjMr8x8T61mKk87SKgvl/FZ0Gk0KeEAXWRjx5wF6YId/QUCjH3zTjhI30

Bug#879488: unzip: contains files licensed only for non-commercial use

2017-10-22 Thread Francesco Poli
On Sun, 22 Oct 2017 09:29:16 +0200 Jonas Smedegaard wrote:

[...]
>  Permission is granted to any individual or institution to use, copy,
 ^^
>  or redistribute this software so long as all of the original files are
   ^^^
>  included unmodified, that it is not sold for profit, and that this copy-
   ^^^
>  right notice is retained.
[...]
> In both cases the phrase "not sold for profit" makes the license 
> non-DFSG-free.

Agreed.

Moreover, the first case seems to also lack any permission to modify
(thus failing DFSG#3)...


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpxJGUSXbTTf.pgp
Description: PGP signature


Bug#879478: [debhelper-devel] Bug#879478: debhelper: dh_testroot regression: relies on debian/control

2017-10-22 Thread Niels Thykier
Cyril Brulebois:
> Package: debhelper
> Version: 10.10
> Severity: serious
> Tags: d-i
> Justification: triggers FTBFS
> 
> [ Please keep both debian-boot@ and myself in the loop, thanks. ]
> 
> Hi,
> 
> debian-installer uses compat 7, a build/ directory, and its daily-build
> script is started from this directory. Makefiles use dh_testroot from
> that directory, and starting with 10.10, the build is broken because of:

Hi Cyril

I am sorry to hear that this broke a build for you.

> [...]
> It seems to me that's due to the getpackages call addition, but I don't
> think it's reasonable for debhelper to break compat 7 this way.

Unfortunately, I cannot even fix this by guarding it with a compat bump
(because that will die as it cannot find debian/compat).  For now, I
will have it issue a warning and continue (plus make some assumptions
about what the d/control file would have contained).  But eventually, I
will remove that fallback and that *cannot* happen with a compat bump.

For you, an easy fix appears be to re-arrange the lines:

dh_testroot
@[ -d ../debian ] || { echo "directory '../debian' [...] }

Into:

@[ -d ../debian ] || { echo "directory '../debian' [...] }
cd .. && dh_testroot

(Only occurs two places AFAICT in the Makefile).  This change would also
be backwards compatible for you.

> Also,
> even if one might object d-i is abusing dh_testroot (or using it
> incorrectly), its documented purpose is:
> | dh_testroot simply checks to see if you are root. If not, it exits
> | with an error. Debian packages must be built as root, though you can
> | use fakeroot(1)
> 
> 
> KiBi.
> [...]

The scope of dh_testroot has changed and I have committed an update of
the documentation of dh_testroot targeting 10.10.1.  Furthermore, I have
added a note in debhelper.7 that all debhelper tools must be run from
the unpacked source root (except where otherwise noted).

Thanks,
~Niels



Processed: limit source to debhelper, tagging 879478

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> limit source debhelper
Limiting to bugs with field 'source' containing at least one of 'debhelper'
Limit currently set to 'source':'debhelper'

> tags 879478 + pending
Bug #879478 [debhelper] debhelper: dh_testroot regression: relies on 
debian/control
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#878348: collectd FTBFS with libsigrok 0.5.0

2017-10-22 Thread Michael Stapelberg
Hi,

Adrian Bunk  writes:
> Source: collectd
> Version: 5.7.2-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/collectd.html
>
> ...
> checking for LIBSIGROK... no
> ...
> configure:40804: checking for LIBSIGROK
> configure:40811: $PKG_CONFIG --exists --print-errors "libsigrok < 0.4"
> Requested 'libsigrok < 0.4' but version of libsigrok is 0.5.0

tokkee, are you on top of this? This bug marks freeradius for
auto-removal from testing. If you need help with a fix, please let me
know.

-- 
Best regards,
Michael



Bug#879489: cadvisor FTBFS on amd64

2017-10-22 Thread Adrian Bunk
Source: cadvisor
Version: 0.27.1+dfsg-1
Severity: serious

Some recent change in unstable makes cadvisor FTBFS on amd64:

https://tests.reproducible-builds.org/debian/history/cadvisor.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cadvisor.html

...
github.com/google/cadvisor/storage/test
github.com/google/cadvisor/utils/cpuload/netlink/example
github.com/google/cadvisor/utils/oomparser/oomexample
github.com/google/cadvisor/utils/procfs
github.com/google/cadvisor/utils/sysfs/fakesysfs
github.com/google/cadvisor/utils/tail
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/build/1st/cadvisor-0.27.1\+dfsg/_build/src\" 
-asmflags=\"-trimpath=/build/1st/cadvisor-0.27.1\+dfsg/_build/src\" -v -p 1 
github.com/google/cadvisor github.com/google/cadvisor/api 
github.com/google/cadvisor/cache github.com/google/cadvisor/cache/memory 
github.com/google/cadvisor/client 
github.com/google/cadvisor/client/clientexample 
github.com/google/cadvisor/client/v2 github.com/google/cadvisor/collector 
github.com/google/cadvisor/container 
github.com/google/cadvisor/container/common 
github.com/google/cadvisor/container/crio 
github.com/google/cadvisor/container/docker 
github.com/google/cadvisor/container/libcontainer 
github.com/google/cadvisor/container/raw 
github.com/google/cadvisor/container/rkt 
github.com/google/cadvisor/container/systemd 
github.com/google/cadvisor/container/testing 
github.com/google/cadvisor/devicemapper 
github.com/google/cadvisor/devicemapper/fake github.com/google/cadvisor/events 
github.com/google/cad
 visor/fs github.com/google/cadvisor/healthz github.com/google/cadvisor/http 
github.com/google/cadvisor/http/mux github.com/google/cadvisor/info/v1 
github.com/google/cadvisor/info/v1/test github.com/google/cadvisor/info/v2 
github.com/google/cadvisor/integration/framework 
github.com/google/cadvisor/integration/runner 
github.com/google/cadvisor/integration/tests/api 
github.com/google/cadvisor/integration/tests/healthz 
github.com/google/cadvisor/machine github.com/google/cadvisor/manager 
github.com/google/cadvisor/manager/watcher 
github.com/google/cadvisor/manager/watcher/raw 
github.com/google/cadvisor/manager/watcher/rkt 
github.com/google/cadvisor/metrics github.com/google/cadvisor/pages 
github.com/google/cadvisor/pages/static github.com/google/cadvisor/storage 
github.com/google/cadvisor/storage/bigquery 
github.com/google/cadvisor/storage/bigquery/client 
github.com/google/cadvisor/storage/bigquery/client/example 
github.com/google/cadvisor/storage/elasticsearch github.com/google/cadviso
 r/storage/influxdb github.com/google/cadvisor/storage/kafka 
github.com/google/cadvisor/storage/redis 
github.com/google/cadvisor/storage/statsd 
github.com/google/cadvisor/storage/statsd/client 
github.com/google/cadvisor/storage/stdout 
github.com/google/cadvisor/storage/test github.com/google/cadvisor/summary 
github.com/google/cadvisor/utils github.com/google/cadvisor/utils/cloudinfo 
github.com/google/cadvisor/utils/container 
github.com/google/cadvisor/utils/cpuload 
github.com/google/cadvisor/utils/cpuload/netlink 
github.com/google/cadvisor/utils/cpuload/netlink/example 
github.com/google/cadvisor/utils/docker 
github.com/google/cadvisor/utils/oomparser 
github.com/google/cadvisor/utils/oomparser/oomexample 
github.com/google/cadvisor/utils/procfs github.com/google/cadvisor/utils/sysfs 
github.com/google/cadvisor/utils/sysfs/fakesysfs 
github.com/google/cadvisor/utils/sysinfo github.com/google/cadvisor/utils/tail 
github.com/google/cadvisor/validate github.com/google/cadvisor/version github.
 com/google/cadvisor/zfs returned exit code 2
debian/rules:32: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2



Bug#879487: cgview FTBFS with libbatik-java 1.9-3

2017-10-22 Thread Adrian Bunk
Source: cgview
Version: 0.0.20100111-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cgview.html

...
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/cgview-0.0.20100111'
cd src && \
cp -a ca/ualberta/stothard/cgview/includes . && \
javac -classpath 
/usr/share/java/batik-awt-util.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-svggen.jar:/usr/share/java/batik-util.jar:/usr/share/java/batik-xml.jar:/usr/share/java/commons-lang.jar:/usr/share/java/jargs.jar:/usr/share/java/xercesImpl.jar
 ca/ualberta/stothard/cgview/*.java && \
jar -cmf ../manifestinfo cgview.jar ca/ualberta/stothard/cgview/*.class 
includes && \
rm -rf includes
ca/ualberta/stothard/cgview/CgviewIO.java:156: error: cannot access Localizable
DOMImplementation domImpl = 
GenericDOMImplementation.getDOMImplementation();
^
  class file for org.apache.batik.i18n.Localizable not found
ca/ualberta/stothard/cgview/CgviewIO.java:184: error: cannot access XMLConstants
Element root = graphics2D.getRoot();
 ^
  class file for org.apache.batik.util.XMLConstants not found
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
debian/rules:21: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1



Bug#879488: unzip: contains files licensed only for non-commercial use

2017-10-22 Thread Jonas Smedegaard
Package: unzip
Version: 6.0-21
Severity: serious
Tags: upstream
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

unzip.c contains the following notice:

  Copyright on recmatch() from Zip's util.c (although recmatch() was almost
  certainly written by Mark Adler...ask me how I can tell :-) ):

 Copyright (C) 1990-1992 Mark Adler, Richard B. Wales, Jean-loup Gailly,
 Kai Uwe Rommel and Igor Mandrichenko.

 Permission is granted to any individual or institution to use, copy,
 or redistribute this software so long as all of the original files are
 included unmodified, that it is not sold for profit, and that this copy-
 right notice is retained.

The file COPYING.OLD similarly contains this notice:

   The following copyright applied to the Windows DLL code (windll/*),
   distributed with UnZip version 5.2 and later:

 * Copyright (c) 1996 Mike White.
 * Permission is granted to any individual or institution to use,
 * copy, or redistribute this software so long as all of the original
 * files are included, that it is not sold for profit, and that this
 * copyright notice is retained.

In both cases the phrase "not sold for profit" makes the license non-DFSG-free.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlnsSMkACgkQLHwxRsGg
ASFPRQ/+LCfq1MayfP8Oq50b6Ud+mPlQ3ZtV/YW7a5Uoi7QOQ1fBAyYMSWsZAfVY
UjSU6AgJRiACgkBty8KRSL1uuQIYZLPc3npgKyywsAtPUlpUYwh0MGj9GEgkqkCS
DVtXiR2L6NhK70+bYrFzzQzelRApgFRWnwCI7+n79ZWj8ZraAMYLLIwQ1EI62fuy
wgV2jdQWh4Cyb+ntckoGCFMiRzH2ABBMtPN8AMBGulZWePAHxT2f91L54KB1DVvr
XUCMHUPZt8VzG4qsyF25uMxqpaGDEL5FIiY7fqTfza+UswPhqLFC1WFHPU+fl3vf
cOl8A2YK1FFjIC2qCiCNVixwk38IUhyL9NVj0ntN4MjaB+L8TYr2GaxCeEut58v2
36F9IXZODj3941d7v2B9UZ7qpalKKMpiVW+jO+I16BlzDNy57LN8Gqjo07thaB9B
Ga6YUKabNiUh6IzQ54s2i5JfLsi6k+Oqh8v93mlm+uoiptaxO7dXl3etQD/R6IwN
ZDiXWbgPB2TqfmXecNvgthPgfXItE7NMaIXSQPWv2FrkGVRyLGppqQmyHCxG3p9v
l+YCiKHoBrCzfISCTpl1By6UMTgbQq1IEa25O7l6KwsDV7Y4NSinavlp8265ER59
rTZDQITU7y/vXoG1WrSq3O7IHEXgMh2OcW1MYYcl/w/kHUcXBwk=
=XkK+
-END PGP SIGNATURE-



Bug#878503: marked as done (macsyfinder: FTBFS: Needs build-dep on graphviz)

2017-10-22 Thread Debian Bug Tracking System
Your message dated Sun, 22 Oct 2017 07:19:06 +
with message-id 
and subject line Bug#878503: fixed in macsyfinder 1.0.2-5
has caused the Debian Bug report #878503,
regarding macsyfinder: FTBFS: Needs build-dep on graphviz
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.)


-- 
878503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macsyfinder
Version: 1.0.2-4
Severity: serious
Justification: fails to build from source

Dear maintainer,

macsyfinder currently fails to build with the following error:

  ! LaTeX Error: File `None' not found.

  See the LaTeX manual or LaTeX Companion for explanation.
  Type  H   for immediate help.
   ...

  l.1218 \includegraphics{None}

That line is a result of .. digraph:: directive in implementation.rst. This
directive requires graphviz package to work properly. Without that package,
the HTML output is also broken.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: macsyfinder
Source-Version: 1.0.2-5

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated macsyfinder 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, 22 Oct 2017 09:01:54 +0200
Source: macsyfinder
Binary: macsyfinder
Architecture: source
Version: 1.0.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 macsyfinder - detection of macromolecular systems in protein datasets
Closes: 878503
Changes:
 macsyfinder (1.0.2-5) unstable; urgency=medium
 .
   * Team upload.
   * Add graphviz to Build-Depends
 Closes: #878503
   * Standards-Version: 4.1.1
Checksums-Sha1:
 bc035ef79e6ed9d57a013cb80252796f9b167b4b 2170 macsyfinder_1.0.2-5.dsc
 dccea0734acdce86928371267bea0054f7355de5 6220 macsyfinder_1.0.2-5.debian.tar.xz
 a1c02944f984d6aef3622e34a7bcac1912da1633 15162 
macsyfinder_1.0.2-5_source.buildinfo
Checksums-Sha256:
 2519a90a4bcb954ca14b5f1d339ba54995360230398dba044bdddf939d3ded6e 2170 
macsyfinder_1.0.2-5.dsc
 67c9a2e82848c521f33ea9ae55efc1603293b91d8a8b68b120e4f89cbfc485ac 6220 
macsyfinder_1.0.2-5.debian.tar.xz
 b405591bebefae3174b0d11f10eaac8c12e1c382a77df23b17e0ca53f5bd7eb7 15162 
macsyfinder_1.0.2-5_source.buildinfo
Files:
 6aafda05c90affcb6bd3147ac7592ec9 2170 science optional macsyfinder_1.0.2-5.dsc
 1d56b10d8269be7bbba5fd43b6a19399 6220 science optional 
macsyfinder_1.0.2-5.debian.tar.xz
 9a15cd0059d6138b096754993bf11ee6 15162 science optional 
macsyfinder_1.0.2-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlnsQ+AOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGvrQ//SL2v7FJlSlPVAKsoZ4xAQxcI07QhNvdkxakt
4LEz2oRT9M51kchPRuTjvmzOOLkR8Uu9cpy8VWr9VDj2H9EYibZ6hrLbkmmFsoj5
0YePMyinuqo4q80zLeVyKHjkUxRqCHOPui+dKvr/v7YeouCGJ8diKUHZtTP9MdMB
+PhlfDEK+tIWccOxEaudSyDd1/a3jCUkEFRmqcG2GtbDWLL+KEV57vnaIFagU0SI
nl2Z0f7QhHYf+QDou7h5fYUjJohtBvIBEw4fqvXnYl09nuDFklPGGNQgFHjz5r9y
50aHBpL93p/uvwJv0MCZ4GXi+3AxobuJfo958i2h4Ooakm0bY3ENWfmQeUipvcd8
F9YHTvlbKgbVc2bDPAYBCDTXRePWgf0cr2Ap8r6katLzAbAll1DT0+sFSgCjNmUa
y1DXVjtJ4Ep5OjQvjbswPE4nDyjlrp2PZ/IC7y9hcglbeI6UMHfQRrW/YXfPn98u
GruRL2SdtE/0lyPPNiW+f1Q85hPcrqUVALWGOgulVvaxLKtF1O8sptOElf9599vz
ZCgOuorxhSunLKVyQPbsv2XRylFzxBg8dS6+3TDklpIlKQd0wJ01oubJSTcfJvCg
WVuFZmQ2C5wTM1oNWtoW+x4Sg9qxLt+Ni1ADPhrzTY8rAvM5/mfaObGmzRX8QGVS
4SpGkm0=
=pqWB
-END PGP SIGNATURE End Message ---