Bug#849334: marked as done ([dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 06:18:28 +
with message-id 
and subject line Bug#849334: fixed in dnscrypt-proxy 1.8.1-4
has caused the Debian Bug report #849334,
regarding [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect 
configuration path on systemd service file
to be marked as done.

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

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


-- 
849334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnscrypt-proxy
Version: 1.8.1-3
Severity: serious

--- Please enter the report below this line. ---
Since last upgrade, Dnscrypt fails to start due search configuration file at 
path that does 
not exist.

Service file (/lib/systemd/system/dnscrypt-proxy.service) has incorrect path on 
Exec line:
ExecStart=/usr/sbin/dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf

and, on my system, since last update dnscrypt-proxy.conf is located at 
/etc/dnscrypt-proxy/dnscrypt-proxy.conf/dnscrypt-proxy.conf


Service file after update:

[Unit]
Description=DNSCrypt client proxy Documentation=man:dnscrypt-proxy(8) 
Requires=dnscrypt-proxy.socket After=network.target Before=nss-lookup.target 

[Install] Also=dnscrypt-proxy.socket WantedBy=multi-user.target 

[Service] Type=notify NonBlocking=true User=_dnscrypt-proxy ExecStart=/usr/sbin/
dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf Restart=always 
ProtectSystem=strict ProtectHome=true ProtectKernelModules=true 
ProtectKernelTunables=true ProtectControlGroups=true 
MemoryDenyWriteExecute=true 
RestrictRealtime=true




Directory structure on disk:

~$ tree /etc/dnscrypt-proxy/
/etc/dnscrypt-proxy/└── dnscrypt-proxy.conf   └── dnscrypt-proxy.conf



Modifying incorrect path on systemd service file or moving config file to path 
in systemd 
service file makes dnscrypt work correctly again.

--- System information. ---
Architecture: 
Kernel:   Linux 4.8.0-2-amd64

Debian Release: stretch/sid
  950 unstablewww.deb-multimedia.org 
  900 unstable-debug  deb.debian.org 
  900 unstableftp.debian.org 
  800 experimentalftp.debian.org 
  500 stable  people.debian.org 
 
--- Package information. ---
Depends   (Version) | Installed
===-+-
adduser | 3.115
lsb-base (>= 3.0-6) | 9.20161125
init-system-helpers  (>= 1.18~) | 1.46
libc6 (>= 2.17) | 
libltdl7 (>= 2.4.6) | 
libsodium18 (>= 1.0.10) | 
libsystemd0 | 


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
resolvconf| 




signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: dnscrypt-proxy
Source-Version: 1.8.1-4

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

Debian distribution maintenance software
pp.
Eric Dorland  (supplier of updated dnscrypt-proxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Dec 2016 00:52:25 -0500
Source: dnscrypt-proxy
Binary: dnscrypt-proxy dnscrypt-proxy-plugins
Architecture: source amd64
Version: 1.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Eric Dorland 
Changed-By: Eric Dorland 
Description:
 dnscrypt-proxy - Tool for securing communications between a client and a DNS 
resol
 dnscrypt-proxy-plugins - Plugins for dnscrypt-proxy
Closes: 849334
Changes:
 dnscrypt-proxy (1.8.1-4) unstable; urgency=medium
 .
   * debian/dnscrypt-proxy.install, debian/dnscrypt-proxy.maintscript: Fix
 erroneously install location of config file. (Closes: #849334)
Checksums-Sha1:
 8952088a6558fc0a6f58df7c991935f0ebc5d2ed 2062 dnscrypt-proxy_1.8.1-4.dsc
 3a306d225645887e485c9bec65a424b9e9a950e1 9316 
dnscrypt-proxy_1.8.1-4.debian.tar.xz
 94826a2a2be7acc6048cf5440d97d0d8bb16fc05 537198 

Bug#848029: chromium: sound broken after update

[Nicolai Clemmensen]

Hi all!

Sort of good news. I just upgraded after coming back to my desktop and was then 
having the exact same issue.
I tried to track down the offending code, but the diff was enormous, so I 
couldn't really find anything.
I did however, manage to find a temporary solution to the issue, which might 
point us in the right direction:
Launch with: chromium --audio-buffer-size=8192 (I just tried a random number, a 
lower value might be fine).

When doing this here, the audio is fine again.
So yes, it's basically the same age-old issue with PulseAudio and Chromium. 
Something must have changed that triggered this though, but without knowing the 
code, it's pretty much impossible for me to say what.

Just to clarify, this is definitely not the same bug as Christopher Mark 
describes, as Ubuntu.
Videos works fine for me. Only audio is affected.
YouTube's HTML5 test shows that everything is okay here.

chromium: 55.0.2883.75-1~deb8u1
pulseaudio: 5.0-13
also-base: 1.0.27+1

Bug#845117: marked as done (ifmail: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo error))

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 04:04:11 +
with message-id 
and subject line Bug#845117: fixed in ifmail 2.14tx8.10-23
has caused the Debian Bug report #845117,
regarding ifmail: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo 
error)
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.)


-- 
845117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ifmail
Version: 2.14tx8.10-22
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_testdir
/usr/bin/make EXTRA_CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" EXTRA_LDFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now"
make[1]: Entering directory '/<>'
for d in iflib ifgate ifcico po; do (cd $d && echo $d && /usr/bin/make all) || 
exit; done;
iflib
make[2]: Entering directory '/<>/iflib'
(for f in  ;do BASE=`basename $f .o`; BASE=\"${BASE}.h\" ; \
echo "#include ${BASE}"; done) > needed.h
cc -Wall -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote . -iquote . -I/usr/include 
-DDEBUGFILE=\""/var/log/ifmail/ifdebug"\" -DLOGFILE=\""/var/log/ifmail/iflog"\" 
-DCONFIGFILE=\""/etc/ifmail/config"\" -DMAPTABDIR=\""/usr/lib/ifmail/maptabs"\" 
-DLOCKDIR=\""/var/lock"\" -DPUBDIR=\""/home/ftp/pub"\" 
-DFAKEDIR=\""/tmp/ifmail/"\" -DMAILLOG=LOG_LOCAL0 -DNEWSLOG=LOG_LOCAL0 
-DCICOLOG=LOG_LOCAL0 -DTERMAIL_HACK -DTPUT_STATUS_HACK -DADD_PID -DLEVEL=0 
-DDONT_REGATE -DSLAVE_SENDS_NAK_TOO -DRNEWSB -DJE -DRESTAMP_OLD_POSTINGS=14 
-DBELEIVE_ZFIN=1 -DHAS_TCP -DAREAS_HACKING -DRESTAMP_FUTURE_POSTINGS -DFSCHTML 
-DMACHIGAI -DALLOW_RETURNPATH -DGATEBAU_MSGID -DDIRTY_CHRS -DHIDDEN 
-DAREAS_NUMERAL_COMMENTS -DHAS_STATFS -DSTATFS_IN_VFS_H -DHAS_SETSID 
-DHAS_NDBM_H -DDONT_HAVE_TM_GMTOFF -DHAS_TERMIOS_H -DASCII_LOCKFILES 
-DHAS_FSYNC -DHAS_IOCTL_H -DHAS_REGEX_H -DNEED_BSY -DNO_IO_AFTER_HANGUP -DDO
 _NEED_TIME -DNEED_FORK -DHAS_BSD_SIGNALS -DHAS_SELECT -DUSE_SETPROCTITLE 
-DINT32=long -DINT16=short -D_GNU_SOURCE -DHAVE_LOCALE_H 
-DNLS_CAT_NAME=\"ifmail\" -DNLS_LOCALE_PATH=\"/usr/share/locale\" -c lutil.c
cc -Wall -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote . -iquote . -I/usr/include 
-DDEBUGFILE=\""/var/log/ifmail/ifdebug"\" -DLOGFILE=\""/var/log/ifmail/iflog"\" 
-DCONFIGFILE=\""/etc/ifmail/config"\" -DMAPTABDIR=\""/usr/lib/ifmail/maptabs"\" 
-DLOCKDIR=\""/var/lock"\" -DPUBDIR=\""/home/ftp/pub"\" 
-DFAKEDIR=\""/tmp/ifmail/"\" -DMAILLOG=LOG_LOCAL0 -DNEWSLOG=LOG_LOCAL0 
-DCICOLOG=LOG_LOCAL0 -DTERMAIL_HACK -DTPUT_STATUS_HACK -DADD_PID -DLEVEL=0 
-DDONT_REGATE -DSLAVE_SENDS_NAK_TOO -DRNEWSB -DJE -DRESTAMP_OLD_POSTINGS=14 
-DBELEIVE_ZFIN=1 -DHAS_TCP -DAREAS_HACKING -DRESTAMP_FUTURE_POSTINGS -DFSCHTML 
-DMACHIGAI -DALLOW_RETURNPATH -DGATEBAU_MSGID -DDIRTY_CHRS -DHIDDEN 
-DAREAS_NUMERAL_COMMENTS -DHAS_STATFS -DSTATFS_IN_VFS_H -DHAS_SETSID 
-DHAS_NDBM_H -DDONT_HAVE_TM_GMTOFF -DHAS_TERMIOS_H -DASCII_LOCKFILES 
-DHAS_FSYNC -DHAS_IOCTL_H -DHAS_REGEX_H -DNEED_BSY -DNO_IO_AFTER_HANGUP -DDO
 _NEED_TIME -DNEED_FORK -DHAS_BSD_SIGNALS -DHAS_SELECT -DUSE_SETPROCTITLE 
-DINT32=long -DINT16=short -D_GNU_SOURCE -DHAVE_LOCALE_H 
-DNLS_CAT_NAME=\"ifmail\" -DNLS_LOCALE_PATH=\"/usr/share/locale\" -c xutil.c
cc -Wall -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -iquote . -iquote . -I/usr/include 
-DDEBUGFILE=\""/var/log/ifmail/ifdebug"\" -DLOGFILE=\""/var/log/ifmail/iflog"\" 
-DCONFIGFILE=\""/etc/ifmail/config"\" -DMAPTABDIR=\""/usr/lib/ifmail/maptabs"\" 
-DLOCKDIR=\""/var/lock"\" -DPUBDIR=\""/home/ftp/pub"\" 
-DFAKEDIR=\""/tmp/ifmail/"\" -DMAILLOG=LOG_LOCAL0 -DNEWSLOG=LOG_LOCAL0 
-DCICOLOG=LOG_LOCAL0 -DTERMAIL_HACK -DTPUT_STATUS_HACK -DADD_PID -DLEVEL=0 
-DDONT_REGATE -DSLAVE_SENDS_NAK_TOO -DRNEWSB -DJE -DRESTAMP_OLD_POSTINGS=14 
-DBELEIVE_ZFIN=1 -DHAS_TCP -DAREAS_HACKING -DRESTAMP_FUTURE_POSTINGS -DFSCHTML 
-DMACHIGAI -DALLOW_RETURNPATH -DGATEBAU_MSGID -DDIRTY_CHRS 

Bug#846429: marked as done (ifmail: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 04:04:11 +
with message-id 
and subject line Bug#846429: fixed in ifmail 2.14tx8.10-23
has caused the Debian Bug report #846429,
regarding ifmail: add libfl-dev to Build-Depends
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.)


-- 
846429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifmail
Severity: important
User: helm...@debian.org
Usertags: libfldep

ifmail will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since ifmail uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: ifmail
Source-Version: 2.14tx8.10-23

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

Debian distribution maintenance software
pp.
Marco d'Itri  (supplier of updated ifmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Dec 2016 04:40:59 +0100
Source: ifmail
Binary: ifmail ifgate ifcico
Architecture: source i386 all
Version: 2.14tx8.10-23
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Description:
 ifcico - Fidonet Technology transport package
 ifgate - Internet to Fidonet gateway
 ifmail - Internet to Fidonet gateway
Closes: 831629 845117 846429
Changes:
 ifmail (2.14tx8.10-23) unstable; urgency=medium
 .
   * Made the builds reproducible, thanks to Chris Lamb. (Closes: #831629)
   * Fixed a FTBFS when built with dpkg-buildpackage -A, thanks to
 Santiago Vila. (Closes: #845117)
   * Depend on libfl-dev. (Closes: #846429)
   * Implemented FTS-5005, thanks to Markus Reschke.
   * Updated patch portability_headers to fix a FTBFS on x32.
Checksums-Sha1:
 32b9a865d9968a0a127fea8d5f94c8ba0942e277 1756 ifmail_2.14tx8.10-23.dsc
 8f2c2ceb77210d8067b8de7a893ff812a68d6c61 39900 
ifmail_2.14tx8.10-23.debian.tar.xz
 ffcaf606193bc8bf457a50151d55a923796cb5e5 198360 ifcico_2.14tx8.10-23_i386.deb
 1f1e80557d50770e05c7ebacca9a4732dc50f9f6 162138 ifgate_2.14tx8.10-23_i386.deb
 21256d8e27124779d7a0028d801225de7640ad2e 48510 ifmail_2.14tx8.10-23_all.deb
 c69dd1c7ee5d6eb49fe006ab4e9694c8c5f1bad8 5090 
ifmail_2.14tx8.10-23_i386.buildinfo
Checksums-Sha256:
 dd79ec19aae438eae6b12b260ecae5e55d9880cf7b2c0d3e6ad89f3dd25491f5 1756 
ifmail_2.14tx8.10-23.dsc
 f9fdee052d2dd74bc9df9a68edde33f634f654a984e7a383f80b3428b39a649f 39900 
ifmail_2.14tx8.10-23.debian.tar.xz
 c61e3c6765ec4af1ec1db25d05eb801fd0e55b0ed4a725815732dca6396c0466 198360 
ifcico_2.14tx8.10-23_i386.deb
 56460fae9fbab6f44cad68ad265b1b337f1be1ba13d9b4a014eeeaafc6d54355 162138 
ifgate_2.14tx8.10-23_i386.deb
 13e327607920cbf9ddf750b5aef1a699ef2f36f12b882954ca11ebe2834e9f19 48510 
ifmail_2.14tx8.10-23_all.deb
 4ea01127a3d5cbc3a94980616345a76de5f50286f5419b6704cc8cd0ec119d14 5090 
ifmail_2.14tx8.10-23_i386.buildinfo
Files:
 ba0ad769fc4eb1c9a3bc4919b6033907 1756 comm extra ifmail_2.14tx8.10-23.dsc
 488585e29a13680020351a1dd2ad0aec 39900 comm extra 
ifmail_2.14tx8.10-23.debian.tar.xz
 07bd60e28215ee68d571d84fa1ef931e 198360 comm extra 
ifcico_2.14tx8.10-23_i386.deb
 5a04a3a7a5b775f2b41188d99126c376 162138 comm extra 
ifgate_2.14tx8.10-23_i386.deb
 e9cef891ab9bd27da3493c9462eafac8 48510 comm extra ifmail_2.14tx8.10-23_all.deb
 333f17ac2ac4d34e3ffaaeda60150db4 5090 comm extra 
ifmail_2.14tx8.10-23_i386.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEGBsIcS5ipP0URKfyK/WlwSLE96QFAlhgkm8ACgkQK/WlwSLE
96Q79Qv+P4PJXcMDOn3aNeQjPDhbo/wl/uHTWX5Lko48+b8fT5D41Wzeah9XX7gI
h0HZL08BaXL7sD5+0ZuvyMaY5DMG7gekM1zonoJg5ukeg9PsZroew5QHTHzKPjjE
3vVsFY0E1NsM05/n92uDflq3xu3z3K0EHR8ZVJvNYwscFW+4LurnFsTX32qYGuQM

Bug#812137: FTBFS with GCC 6: statement is indented as if

[Legimet]

This patch fixes the issue.Index: mailavenger-0.8.4/libasync/maketables.c
===
--- mailavenger-0.8.4.orig/libasync/maketables.c
+++ mailavenger-0.8.4/libasync/maketables.c
@@ -132,7 +132,9 @@ for (i = 0; i < 256; i++)
   meta-character, which in this sense is any character that terminates a run
   of data characters. */
 
-  if (strchr("*+?{^.$|()[", i) != 0) x += ctype_meta; *p++ = x; }
+  if (strchr("*+?{^.$|()[", i) != 0) x += ctype_meta;
+  *p++ = x;
+  }
 
 return yield;
 }

Bug#849162: marked as done (snapd: Drop unversioned 'Conflicts: snap')

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 03:08:57 +
with message-id 
and subject line Bug#849162: fixed in snapd 2.20-2
has caused the Debian Bug report #849162,
regarding snapd: Drop unversioned 'Conflicts: snap'
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.)


-- 
849162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snap
Version: 2013-11-29-4
Severity: serious
Justification: Policy 10.1

Both snap (general purpose gene finding program) and snapd (part of
the app packaging system developed by Canonical) ship the binary
/usr/bin/snap

This is a violation of Debian Policy 10.1
https://www.debian.org/doc/debian-policy/ch-files.html

This was handled in Ubuntu by renaming snap's /usr/bin/snap to
/usr/bin/snap-dna and allowing snapd to keep the /usr/bin/snap binary.

https://launchpad.net/ubuntu/+source/snap/2013-11-29-1ubuntu1

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: snapd
Source-Version: 2.20-2

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

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated snapd 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, 25 Dec 2016 17:50:25 -0600
Source: snapd
Binary: golang-github-ubuntu-core-snappy-dev golang-github-snapcore-snapd-dev 
snapd snap-confine ubuntu-core-launcher
Architecture: source all amd64
Version: 2.20-2
Distribution: unstable
Urgency: medium
Maintainer: Steve Langasek 
Changed-By: Steve Langasek 
Description:
 golang-github-snapcore-snapd-dev - snappy development go packages.
 golang-github-ubuntu-core-snappy-dev - transitional dummy package
 snap-confine - Support executable to apply confinement for snappy apps
 snapd  - Tool to interact with Ubuntu Core Snappy.
 ubuntu-core-launcher - Launcher for ubuntu-core (snappy) apps
Closes: 849162
Changes:
 snapd (2.20-2) unstable; urgency=medium
 .
   * Replace unversioned Conflicts on snap package with versioned
 Breaks/Replaces, now that snap has dropped /usr/bin/snap.
 Closes: #849162.
Checksums-Sha1:
 c2eda1b94d750695c759a7241ecb9c13092c316f 3267 snapd_2.20-2.dsc
 d74e7f11c809334dd0b589d31308a3708e5824fc 36344 snapd_2.20-2.debian.tar.xz
 047e12493ea544209936d13c901ba669ae894011 539412 
golang-github-snapcore-snapd-dev_2.20-2_all.deb
 253a8be5b5a1f8724e436fbb14dcf81b51377f19 33200 
golang-github-ubuntu-core-snappy-dev_2.20-2_all.deb
 2ac841eabb29ddf4928657ea16704dcd7437ad1a 68994 
snap-confine-dbgsym_2.20-2_amd64.deb
 6d70950901ce8c88ae794660983d29e755bff55e 63824 snap-confine_2.20-2_amd64.deb
 3747d16c9237775a4954b3aac2d1c94434327b12 3197190 snapd-dbgsym_2.20-2_amd64.deb
 025b640155f313455de0a8cfcc29d28cda9ccf31 9349 snapd_2.20-2_amd64.buildinfo
 f62368effa03db1527b0762e3eb7ac603a5c666f 5345826 snapd_2.20-2_amd64.deb
 d763cc6ff0f9dc1106e320ce9a1eb5f24bfa6106 34046 
ubuntu-core-launcher_2.20-2_amd64.deb
Checksums-Sha256:
 45b98649311cccb1d59562dd316e5ceb44933604c42e963aa962065ef5af53c0 3267 
snapd_2.20-2.dsc
 c9beb69e26bf9aff3c155f05026e765e39105829a5744f12e823fc39fb2949b1 36344 
snapd_2.20-2.debian.tar.xz
 5b15f9272ddce1a6e8eb4683d721750f02d40869bdc04dd3b211fa3e5d06f380 539412 
golang-github-snapcore-snapd-dev_2.20-2_all.deb
 6ed2560c950c49f0ab5308b0f0e1e31ba9842e8c3f7702946535396946772571 33200 
golang-github-ubuntu-core-snappy-dev_2.20-2_all.deb
 347c64fc389c544488f60ca0de160ab3c84598db160f225b980eaef87e55dd8e 68994 
snap-confine-dbgsym_2.20-2_amd64.deb
 3b26749acebdca30812cb504cd74fe8ae72aa6aa977353494256456c6caf7446 63824 
snap-confine_2.20-2_amd64.deb
 ef4dfbf69b4efeed588b40806c923f1eab2ef7d718c7616e9a990f3f14c16ae5 3197190 
snapd-dbgsym_2.20-2_amd64.deb
 66b9cb6a5fd474f1ff6fb9201198dbe764ade36eeea669bf8a4b993aa34aad2b 9349 
snapd_2.20-2_amd64.buildinfo
 e9d48aa8b8de08620d36dde7a34f4bab67e115852a614e36c444690908654bc0 5345826 
snapd_2.20-2_amd64.deb
 

Processed: tag 812137

[Debian Bug Tracking System]

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

> tags 812137 patch
Bug #812137 [mailavenger] FTBFS with GCC 6: statement is indented as if
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#794438: marked as done (Partition manager does not launch)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 03:08:05 +
with message-id 
and subject line Bug#794438: fixed in partitionmanager 3.0.0-1
has caused the Debian Bug report #794438,
regarding Partition manager does not launch
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.)


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

Package: partitionmanager
Version: 1.0.3-2.1
Severity: grave

Dear Maintainer,

* What led up to the situation?

I recently updated my KDE desktop to plasma5 which entails a lot of 
changes, lots of things not working yet, including this one.

partitionmanager errors out saying that root password incorrect.
This is a false positive, root password is correct.
I tested it on other programs that depend on it, like Synaptic Package 
Manager.


* What exactly did you do (or not do) that was effective (or
ineffective)?

I just launched partition manager from an icon in my desktop

 * What was the outcome of this action?

http://i.imgur.com/79Qrvl7.png

  * What outcome did you expect instead?

A normal launch like in plasma4



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

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

Versions of packages partitionmanager depends on:
ii  kde-runtime   4:4.14.2-2
ii  libblkid1 2.26.2-6
ii  libc6 2.19-19
ii  libgcc1   1:5.1.1-14
ii  libkdecore5   4:4.14.2-5
ii  libkdeui5 4:4.14.2-5
ii  libkio5   4:4.14.2-5
ii  libparted-fs-resize0  3.2-7
ii  libparted23.2-7
ii  libqtcore44:4.8.7+dfsg-1
ii  libqtgui4 4:4.8.7+dfsg-1
ii  libstdc++65.1.1-14
ii  libuuid1  2.26.2-6

partitionmanager recommends no packages.

--
*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

--- End Message ---
--- Begin Message ---
Source: partitionmanager
Source-Version: 3.0.0-1

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

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

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

Debian distribution maintenance software
pp.
Debian KDE Extras Team  (supplier of 
updated partitionmanager 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, 25 Dec 2016 21:19:48 -0500
Source: partitionmanager
Binary: partitionmanager
Architecture: source amd64
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Debian KDE Extras Team 
Description:
 partitionmanager - file, disk and partition management for KDE
Closes: 709474 731957 745290 788701 794438
Changes:
 partitionmanager (3.0.0-1) unstable; urgency=medium
 .
   [ Jonathan Carter ]
   * Update to new upstream version (Closes: #794438, #709474, LP: #1635756)
   * Update standards version to 3.9.8
   * Remove patches (no longer needed)
   * Update compat to level 10
   * Fix watch file (Closes: #788701)
   * Replace ntfsprogs dependency with ntfs-3g (Closes: #731957)
   * Replace partion typo with partition in control (Closes: 745290)
   * New build-deps: extra-cmake-modules, qtbase5-dev, libkf5widgetsaddons-dev,
 libkf5xmlgui-dev, libkf5kiocore5, libkf5config-dev,
 libkf5crash-dev, libkf5doctools-dev, libkf5jobwidgets-dev,
 libkf5kio-dev, libkpmcore4-dev, libatasmart-dev
   * wrap-and-sort
   * Update homepage to new location on kde.org
   * Update copyright file to machine readable format
   * Add hardening export to debian/rules
   * Remove 3 lintian-overrides (no longer needed)
   

Processed: tag 830399

[Debian Bug Tracking System]

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

> tags 830399 patch
Bug #830399 [src:python-jedi] python-jedi: FTBFS: dh_auto_test: pybuild --test 
-i python{version} -p 2.7 returned exit code 13
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#830399: python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Legimet]

These two patches fix the errors. Also, python-pytest and python3-pytest must 
be added as build dependencies.>From de7273e04b3c8e4ca3f8ba32298a5d3d763b3ab3 Mon Sep 17 00:00:00 2001
From: Sid Shanker 
Date: Sun, 17 May 2015 23:11:02 -0700
Subject: [PATCH] Fixed utf-8 decoding error in build.

---
 test/run.py | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/test/run.py b/test/run.py
index a48e1fb..d730914 100755
--- a/test/run.py
+++ b/test/run.py
@@ -290,9 +290,12 @@ def collect_dir_tests(base_dir, test_files, check_thirdparty=False):
 skip = 'Thirdparty-Library %s not found.' % lib
 
 path = os.path.join(base_dir, f_name)
-source = open(path).read()
-if not is_py3:
-source = unicode(source, 'UTF-8')
+
+if is_py3:
+source = open(path, encoding='utf-8').read()
+else:
+source = unicode(open(path).read(), 'UTF-8')
+
 for case in collect_file_tests(StringIO(source),
lines_to_execute):
 case.path = path
Description: 
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 python-jedi (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/watch: use pypi.debian.net redirector
Author: Piotr Ożarowski 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2016-11-16

--- python-jedi-0.9.0.orig/test/test_integration_import.py
+++ python-jedi-0.9.0/test/test_integration_import.py
@@ -18,22 +18,22 @@ def test_goto_definition_on_import():
 def test_complete_on_empty_import():
 assert Script("from datetime import").completions()[0].name == 'import'
 # should just list the files in the directory
-assert 10 < len(Script("from .", path='').completions()) < 30
+assert 10 < len(Script("from .", path='whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import", 1, 5, '').completions()) > 30
+assert len(Script("from . import", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import", 1, 6, 'whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import classes", 1, 5, '').completions()) > 30
+assert len(Script("from . import classes", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import classes", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import classes", 1, 6, 'whatever.py').completions()) < 30
 
 wanted = set(['ImportError', 'import', 'ImportWarning'])
 assert set([c.name for c in Script("import").completions()]) == wanted
 if not is_py26:  # python 2.6 doesn't always come with a library `import*`.
-assert len(Script("import import", path='').completions()) > 0
+assert len(Script("import import", path='whatever.py').completions()) > 0
 
 # 111
 assert Script("from datetime import").completions()[0].name == 'import'

Bug#849345: marked as done (The connman.postrm is plain wrong. It must remove the state dir only on purging)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 01:48:47 +
with message-id 
and subject line Bug#849345: fixed in connman 1.33-3
has caused the Debian Bug report #849345,
regarding The connman.postrm is plain wrong. It must remove the state dir only 
on purging
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.)


-- 
849345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: connman
Version: 1.33-2
Severity: serious

Dear Maintainer,
that goes in per incident - reverting this would fix the situation.

Cheers Alf


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

Kernel: Linux 4.9.0-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages connman depends on:
ii  dbus 1.10.14-1
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libdbus-1-3  1.10.14-1
ii  libglib2.0-0 2.50.2-2
ii  libgnutls30  3.5.7-3
ii  libreadline7 7.0-1
ii  libxtables12 1.6.0+snapshot20161117-4
ii  lsb-base 9.20161125

Versions of packages connman recommends:
pn  bluez  
pn  ofono  
ii  wpasupplicant  2.6-2

Versions of packages connman suggests:
pn  connman-vpn  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: connman
Source-Version: 1.33-3

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

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated connman package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2016 02:12:30 +0100
Source: connman
Binary: connman connman-vpn connman-dev connman-doc
Architecture: source
Version: 1.33-3
Distribution: unstable
Urgency: high
Maintainer: Alexander Sack 
Changed-By: Alf Gaida 
Description:
 connman- Intel Connection Manager daemon
 connman-dev - Development files for connman
 connman-doc - ConnMan documentation
 connman-vpn - Intel Connection Manager daemon - VPN daemon
Closes: 849345
Changes:
 connman (1.33-3) unstable; urgency=high
 .
   * Fix connman.postrm (Closes: #849345)
 - don't remove state-dir unless when purge
 - make removing the resolv.conf symlink more sophisticated
   * Suggests: connman-vpn
Checksums-Sha1:
 54f6bdf14d6040c86b852e9815acef16238dae0a 2359 connman_1.33-3.dsc
 fd216608f1eb8daa9f4688b89bb78f771c30df40 11684 connman_1.33-3.debian.tar.xz
Checksums-Sha256:
 28cfc74e29942d35cf9980e1b0f0d5b0de4c5cc5c73d86bbb26ef822d8725201 2359 
connman_1.33-3.dsc
 090d25bd80fa769fbc34b385040dcfee820cf5b78421f1df41b6fe9949db17b4 11684 
connman_1.33-3.debian.tar.xz
Files:
 5b93cb3c90869d80205c0621239ab1dd 2359 net optional connman_1.33-3.dsc
 df6f4a9874ec121e5b60e613f410be92 11684 net optional 
connman_1.33-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAlhgcTYRHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjbWkg/8DP6y3nBrnQyn6eqDa5d9noVErMUMPLEm
dXdEFT/6BxuzUmIvjI1JYtz1NfGaNhkMh6/3NTDW/JiiGMuRDtLTYvcm4ZdUSilU
A43CzOY8OlMOxMHeFnCBCnTe2uW9cQJGCmQL0C/YpqkeHwew6whEpoHY0bTocAzp
5iSsgIODAsajouOaIu+PsnwWlHrFzOE0QLxPseD+IPfwKFTTJksk8hvXb16Mf5zW
NAxMbY5PVdBUax6BHtHPoUlozy8atN4aM2RtotleHqtjRzntCvL9fDebS1nhLIb8
Dd2DA9EJRLoMYud1WA/Qjn7XzUObFtwSQpifmhfXfKZ7aJBCYw9U37tx6bFVBYFp
PFasa46ps4C2kCvxmVaOaK45iIuJ0meicdrEaIcdufmY/hyrSgMqtErNaV0cnnR+
eCHM3itU29LKfGSEwuAOXLQMa8EQ9GY9PPvBx2Oqday7i9iSYTNdSH86f03WUBqs
NVSI/LS7TkqtR/HZAQupSj89FBVyrj1ErDEmPL38O7/gjs1VV8w3qqvzXTVETCsJ
m5Kp/uhW2+v7Zj9hJDpsM1eE1w0KyOC7F+dz2ovwXJ5VNIQqbIBbsksPUrJPJ4qg
EF5hwqJIJwAkPiI7LIwCrC6TR8pAjrr5SqrGHbwt6dYJKIIZR/F+PGpVZFt3a5Ah
brNrv7npKZo=
=dk2/
-END PGP 

Bug#806092: marked as done (pcb: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 00:34:16 +
with message-id 
and subject line Bug#806092: fixed in pcb 20140316-3.1
has caused the Debian Bug report #806092,
regarding pcb: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

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

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


-- 
806092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pcb
Version: 20140316-3
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --with=autotools_dev
   dh_testroot -i
   dh_prep -i
   dh_installdirs -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install --builddirectory build_gtk
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>/build_gtk'
Making install in w32
make[3]: Entering directory '/<>/build_gtk/w32'
make[4]: Entering directory '/<>/build_gtk/w32'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/build_gtk/w32'
make[3]: Leaving directory '/<>/build_gtk/w32'
Making install in intl
make[3]: Entering directory '/<>/build_gtk/intl'
if { test "pcb" = "gettext-runtime" || test "pcb" = "gettext-tools"; } \
   && test 'no' = yes; then \
  /bin/sh ../../mkinstalldirs 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
/<>/debian/tmp/usr/include; \

[... snipped ...]

# installing common files:
rm -rf /<>/debian/tmp/usr/lib
rm -rf /<>/debian/tmp/usr/include
dh_install -Xusr/bin -Xusr/share/pcb- -Xusr/share/doc -Xexamples -Xtutorial 
-Xusr/share/info
# Install pcb-gtk binary:
install build_gtk/src/pcb debian/pcb-gtk/usr/bin/pcb-gtk
install: cannot create regular file 'debian/pcb-gtk/usr/bin/pcb-gtk': No such 
file or directory
debian/rules:33: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:11: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: pcb
Source-Version: 20140316-3.1

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

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated pcb 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, 25 Dec 2016 14:56:02 -0800
Source: pcb
Binary: pcb pcb-common pcb-gtk pcb-lesstif
Architecture: source
Version: 20140316-3.1
Distribution: unstable
Urgency: medium

Bug#734688: Logs are not rotated for a month

[Christoph Biedl]

Hello everybody,

looking at this old but nasty bug that must be fixed for stretch:

* Trying to understand what goes wrong I wrote a small script that
  creates a few scenarios and executes logrotate then. Run it in
  an arbitrary directory like /tmp/ as regular user, with a single
  parameter in the range 0 to 4. Expect a lot of failures.

* In my understanding logrotate never compresses older logfiles even
  if they are not compressed yet, this will lead to the observed
  clashes. So I was about to write a patch that similar for Bolesław's
  proposal detects if the target file already exists, but would
  compress it then. However:

* github[1] contains a link[2] to a patch gentoo created. At least
  for all scenario my test script above creates, it solves the problems.
  I'd suggest you all test it as well and report back.

Cheers,

Christoph

[1] https://github.com/logrotate/logrotate/pull/23
[2] 
https://gitweb.gentoo.org/repo/gentoo.git/plain/app-admin/logrotate/files/logrotate-3.10.0-atomic-create.patch?id=3aae9fbc
#!/bin/sh

set -e

mkdir -p logs
rm logs/* 2>/dev/null || true

create () {
touch logs/logfile
while [ "$1" ] ; do
echo "$1" >logs/logfile$1
shift
done
}

compress () {
while [ "$1" ] ; do
gzip logs/logfile$1
shift
done
}


case "$1" in
0)
# vanilla: some older logfiles
create  '.1' '.2' '.3'
compress'.1' '.2' '.3'
;;
1)
# first generation exists both plain and compressed
create  '.1' '.2' '.3'
compress'.1' '.2' '.3'
create  '.1'
;;
2)
# first generation is not compressed - ERROR
create  '.1' '.2' '.3' '.4'
compress '.2' '.3' '.4'
;;
3)
# gen.1 not compressed, gen.2 missing
create  '.1'  '.3' '.4'
compress  '.3' '.4'
;;
4)
# gen.1 not compressed, gen.[23] missing
create  '.1'   '.4'
compress   '.4'
;;
'')
echo "Usage: $0 "
exit 1
;;
*)
echo "BUG: Undefined scenario '$1'"
exit 2
;;
esac

CONF="$PWD/logrotate.conf"

cat <<__EOS__ >"$CONF"
$PWD/logs/logfile {
daily
missingok
rotate 3
compress
copytruncate
create 640 $(getent passwd $(id -u) | cut -d: -f1) $(getent group $(id -g) 
| cut -d: -f1)
}
__EOS__

STATE="$PWD/state"
rm "$STATE" >/dev/null || true

echo 'Files in logs/ [PRE]:'
ls -1 logs/

/usr/sbin/logrotate --force --state "$STATE" --verbose "$CONF" || true

echo 'Files in logs/ [POST]:'
ls -1 logs/
echo 'State file:'
cat "$STATE"


signature.asc
Description: Digital signature

Bug#776193: unshield: CVE-2015-1386: directory traversal

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> A fix for this release critical security issue is now available as a
> pull request upstream.

I had a look at the upstream patch, and it do not apply cleanly to the
code in unstable, as the code has been restructured quite a bit upstream.

As unshield is currently missing from testing, and today is the last day
to upload packages missing in testing, I suspect unshield will be missing
from Stretch.  At least I lack the capacity to fix the problem in time.

-- 
Happy hacking
Petter Reinholdtsen

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[James Cameron]

Thanks to Paul Wise for the heads-up.

OLPC still has a software and hardware organisation (me), and is
using a Debian derivative (Ubuntu) on our latest hardware (NL3), using
the Debian packages of Sugar desktop.

Debian should drop olpc-xo1, olpc-powerd, and olpc-kbdshim.

OLPC models are XO-1, XO-1.5, XO-1.75, XO-4, and now NL3.

Right now, OLPC has manufacturing capability for XO-4 and NL3.

Debian only really worked well on the XO-1 and XO-1.5 models; these
are no longer manufactured, units in the field are past end of life,
and are failing at an expected high rate.

Anybody relying on an XO-1 or XO-1.5 should buy a new laptop.  ;-)

Disclosure: I'm paid by OLPC.

-- 
James Cameron
http://quozl.netrek.org/

Bug#849350: marked as done (jimfs: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 26 Dec 2016 00:05:48 +
with message-id 
and subject line Bug#849350: fixed in jimfs 1.1-2
has caused the Debian Bug report #849350,
regarding jimfs: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
849350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jimfs
Version: 1.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Hans-Christoph Steiner 

Hi,

I just ACCEPTed jimfs from NEW but noticed it was missing attribution 
in debian/copyright for the embedded murmurhash implementation.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: jimfs
Source-Version: 1.1-2

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated jimfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Dec 2016 00:44:03 +0100
Source: jimfs
Binary: libjimfs-java libjimfs-java-doc
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Hans-Christoph Steiner 
Description:
 libjimfs-java - In-memory file system implementing the java.nio.file APIs
 libjimfs-java-doc - Documentation for libjimfs-java
Closes: 849350
Changes:
 jimfs (1.1-2) unstable; urgency=medium
 .
   * add missing copyright statement (Closes: #849350)
   * remove unused junit dependency from POM
Checksums-Sha1:
 20b678496a449cf87b8524032a912e046e21cf74 1914 jimfs_1.1-2.dsc
 3fd2fe6f3c78803e26c032e9d4456be4df47b541 3892 jimfs_1.1-2.debian.tar.xz
Checksums-Sha256:
 3d1bc9ef9c26e49dc4e668d78505522a2b9c8afcefb88264c197a35390e7a292 1914 
jimfs_1.1-2.dsc
 cb71057d8e96ebb980ea746a4bd79a9af26e083a50d4cff86aa62b12ebfa0b26 3892 
jimfs_1.1-2.debian.tar.xz
Files:
 070d6405fa0fbd2cc1925317ad3f1fdd 1914 java extra jimfs_1.1-2.dsc
 b7e330cbbdc585aa4112de3881740969 3892 java extra jimfs_1.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQEcBAEBCAAGBQJYYFpaAAoJED4XeBe6G5v6xRoIAKlHTaQ8o0jE4Ir0+IybIh3d
qDZzt1x2j0Yslj+u6KDZCjWfyjU4bD6qqytFGeZdpmzF/094wczSSTJPY95WQbga
vRiW8Zf2Njhsr4liEUj6yUWoGvI9+9EkkkbhLDuQcl2GcBYPbbHWte4GttFMYShO
BsQUt6nLn5j0vT4LquyvflX+pr7atLy0vez9VUqbJTeAmVvv0HJ85hxANa7TAPV9
Yn5YXRireT8RUtF+BPm+P52GYL8NPDGISbZcZTwR8+u/mkR20BYoleGJhoFvLQXx
HdXZGUVeRra2Br544/YisANcsvkvLCZakzJGKWS7uAqgAV2JhyXmTUqJMVBSKgs=
=Sq6m
-END PGP SIGNATURE End Message ---

Bug#846799: Pending fixes for bugs in the golang-google-cloud package

[Martín Ferrari]

Dmitry,

On 16/12/16 19:30, Dmitry Smirnov wrote:

>> Ensure the transition from symlink to directory is handled correctly.
>> Closes: #846799
> 
> Thanks for fixing this problem. FYI there is a better way to do that.
> Instead of duplicated section in preinst/postinst/postrm you can use one 
> "{PKGNAME}.maintscript" file with "symlink_to_dir" line.
> See dpkg-maintscript-helper(1) for details.

Thanks for the tip, I did not know this!


-- 
Martín Ferrari (Tincho)

Processed: Pending fixes for bugs in the jimfs package

[Debian Bug Tracking System]

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

> tag 849350 + pending
Bug #849350 [src:jimfs] jimfs: Incomplete debian/copyright?
Warning: Unknown package 'src:jimfs'
Added tag(s) pending.
Warning: Unknown package 'src:jimfs'
> thanks
Stopping processing here.

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

Bug#849350: Pending fixes for bugs in the jimfs package

[pkg-java-maintainers]

tag 849350 + pending
thanks

Some bugs in the jimfs package are closed in revision
d3c825ff34ffbd7db24302e5cbf82b735e7d2494 in branch 'master' by
Hans-Christoph Steiner

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jimfs.git/commit/?id=d3c825f

Commit message:

add missing copyright statement (Closes: #849350)

Processed: python3-django-macaddress: Compatibility of django-macaddress with django 1.10 in stretch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #848073 [python3-django-macaddress] python3-django-macaddress: 
Compatibility of django-macaddress with django 1.10 in stretch
Severity set to 'grave' from 'important'

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

Bug#849346: marked as done (CVE-2015-3239)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 23:33:51 +
with message-id 
and subject line Bug#849346: fixed in android-platform-external-libunwind 
7.0.0+r1-4
has caused the Debian Bug report #849346,
regarding CVE-2015-3239
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.)


-- 
849346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-external-libunwind
Severity: grave
Tags: security

Hi,
https://security-tracker.debian.org/tracker/CVE-2015-3239 has been fixed in
src:unwind, but is still needed in android-platform-external-libunwind

Cheers,
Moritz
 
--- End Message ---
--- Begin Message ---
Source: android-platform-external-libunwind
Source-Version: 7.0.0+r1-4

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated 
android-platform-external-libunwind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Dec 2016 00:09:38 +0100
Source: android-platform-external-libunwind
Binary: android-libunwind android-libunwind-dev
Architecture: source
Version: 7.0.0+r1-4
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Hans-Christoph Steiner 
Description:
 android-libunwind - libunwind for Android
 android-libunwind-dev - libunwind for Android - Development files
Closes: 849346
Changes:
 android-platform-external-libunwind (7.0.0+r1-4) unstable; urgency=medium
 .
   [ Hans-Christoph Steiner]
   * Team upload
 .
   [ Daigo Moriwaki ]
   * Fix off-by-one in dwarf_to_unw_regnum(), applying an upstream patch
 396b6c7ab737e2bff244d640601c436a26260ca1.
 (Closes: #849346) (CVE-2015-3239)
Checksums-Sha1:
 74c86c5e4e1d95a41e1d1ccca8d23530785520fb 2224 
android-platform-external-libunwind_7.0.0+r1-4.dsc
 22185430c1c245acdf8713f380b42866f53dd2ae 11264 
android-platform-external-libunwind_7.0.0+r1-4.debian.tar.xz
Checksums-Sha256:
 b22ec16b153d4eefdfa725977e08f497e9a143e1adac45f346cd9bd38bf12b4a 2224 
android-platform-external-libunwind_7.0.0+r1-4.dsc
 0513e708b26a23328eaf28d6d62b294e3a5da5764597c021e0edc6a5aa8a0f68 11264 
android-platform-external-libunwind_7.0.0+r1-4.debian.tar.xz
Files:
 b7b50c73caf695cc04a300ef41a7af8d 2224 libs optional 
android-platform-external-libunwind_7.0.0+r1-4.dsc
 ec3d125a27c12aa97e26c6966dfa4195 11264 libs optional 
android-platform-external-libunwind_7.0.0+r1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQEcBAEBCAAGBQJYYFLjAAoJED4XeBe6G5v6pwcH/0VwrF7B4HwFY4kuEe7OcBmp
a2R1zQHFv77Ll6DQhJkBEhkN1olknVRUarnhKF4peHxVOTSXCTUvnyykUNiHI+9j
Whg3/Ff7oc7GXXYWIFRM6RPGjORNaiqtkATEbFlxBwOhwxMDjCRiQuh4R/A77AqF
+lZ9rlXoAc1tCpvC36uoa3w8S1/h5CSiDkzpMhblpi7iUSLVyq+9/wX/zE7/8+1B
A0yoH0da4104ItO15I8gGFKnAGH/1Or2AnZ67DbEAydj5nTxbTQy5x8NMU2h6Tc9
bEfGfL6/Ts1y45EyXglqtAaOvPT3pmUu0zhsE5EVWK3Sj60I3uZ2i9TcLaLfQDQ=
=rPqb
-END PGP SIGNATURE End Message ---

Bug#849350: jimfs: Incomplete debian/copyright?

[Chris Lamb]

Source: jimfs
Version: 1.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Hans-Christoph Steiner 

Hi,

I just ACCEPTed jimfs from NEW but noticed it was missing attribution 
in debian/copyright for the embedded murmurhash implementation.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#806092: proposed fix

[Dima Kogan]

I'm attaching two patches to fix this. Please review soon if
possible. If I don't hear back by Dec 26, I'll NMU this. That's the
latest possible day to meet the cutoff for stretch.


>From 65bd793529cc6aae5f6f1946396cde03e55a2620 Mon Sep 17 00:00:00 2001
From: Dima Kogan 
Date: Sun, 25 Dec 2016 14:55:05 -0800
Subject: [PATCH 1/2] We can now build arch-dependent and arch-independent
 packages only

I.e. "dpkg-buildpackage -A" and "dpkg-buildpackage -B" works. Closes: #806092
---
 debian/rules | 32 ++--
 1 file changed, 22 insertions(+), 10 deletions(-)

diff --git a/debian/rules b/debian/rules
index 759ed3d..e7df4c7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,26 +10,31 @@ CONFIGURE_OPTS=--disable-rpath --enable-dbus --disable-update-desktop-database -
 %:
 	dh $@ --with=autotools_dev
 
+# I configure build-gtk unconditionally (arch-dependent and arch-independent)
+# because I need a single configure invocation in both cases
 override_dh_auto_configure:
-	dh_auto_configure --builddirectory build_gtk -- $(CONFIGURE_OPTS) --with-gui=gtk
-	dh_auto_configure --builddirectory build_lesstif -- $(CONFIGURE_OPTS) --with-gui=lesstif
+	dh_auto_configure--builddirectory build_gtk -- $(CONFIGURE_OPTS) --with-gui=gtk
+	dh_auto_configure -a --builddirectory build_lesstif -- $(CONFIGURE_OPTS) --with-gui=lesstif
 
 override_dh_auto_build:
-	dh_auto_build --builddirectory build_gtk
-	dh_auto_build --builddirectory build_lesstif
+	dh_auto_build -a --builddirectory build_gtk
+	dh_auto_build -a --builddirectory build_lesstif
 
 override_dh_auto_test:
-	dh_auto_test --builddirectory build_gtk
-	dh_auto_test --builddirectory build_lesstif
+	dh_auto_test -a --builddirectory build_gtk
+	dh_auto_test -a --builddirectory build_lesstif
 
-override_dh_auto_install:
-	dh_auto_install --builddirectory build_gtk
+override_dh_auto_install-arch:
+	make -C build_gtk install-exec DESTDIR=$$PWD/debian/tmp AM_UPDATE_INFO_DIR=no
+
+override_dh_auto_install-indep:
+	make -C build_gtk install-data DESTDIR=$$PWD/debian/tmp AM_UPDATE_INFO_DIR=no
 
 override_dh_auto_clean:
 	dh_auto_clean --builddirectory build_gtk
 	dh_auto_clean --builddirectory build_lesstif
 
-override_dh_install:
+override_dh_install-arch:
 	# Remove needlessly installed static library and header file before
 	# installing common files:
 	rm -rf $(CURDIR)/debian/tmp/usr/lib
@@ -42,6 +47,13 @@ override_dh_install:
 	# Install pcb-lesstif binary:
 	install build_lesstif/src/pcb debian/$(package)-lesstif/usr/bin/pcb-lesstif
 
+override_dh_install-indep:
+	# Remove needlessly installed static library and header file before
+	# installing common files:
+	rm -rf $(CURDIR)/debian/tmp/usr/lib
+	rm -rf $(CURDIR)/debian/tmp/usr/include
+	dh_install -Xusr/bin -Xusr/share/pcb- -Xusr/share/doc -Xexamples -Xtutorial -Xusr/share/info
+
 	# Set executable bit for pcb tools:
 	[ ! -d debian/$(package)-common ] || chmod a+x debian/$(package)-common/usr/share/pcb/tools/MergePCBPS
 	[ ! -d debian/$(package)-common ] || chmod a+x debian/$(package)-common/usr/share/pcb/tools/Merge_dimPCBPS
@@ -52,7 +64,7 @@ override_dh_install:
 	# Remove empty dirs:
 	[ ! -d debian/$(package)-common ] || find debian/$(package)-common -type d -empty -delete
 
-override_dh_fixperms:
+override_dh_fixperms-indep:
 	dh_fixperms
 	# Fix permissions of a couple of example files:
 	[ ! -d debian/$(package)-common ] || chmod -x debian/$(package)-common/usr/share/doc/$(package)-common/examples/LED.pcb
-- 
2.10.1

>From 77ee5069c455bd3458a20875c328c9642ded0fdf Mon Sep 17 00:00:00 2001
From: Dima Kogan 
Date: Sun, 25 Dec 2016 14:56:11 -0800
Subject: [PATCH 2/2] changelog bump

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 1fa754f..62c65c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pcb (20140316-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Closes: #806092
+
+ -- Dima Kogan   Sun, 25 Dec 2016 14:56:02 -0800
+
 pcb (20140316-3) unstable; urgency=medium
 
   * (Build-)Depend on unversioned tcl/tk
-- 
2.10.1

Processed: fix version for 842347

[Debian Bug Tracking System]

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

> # identical found and fixed versions confuse version tracking
> # removing the fixed version
> notfixed 842347 3.2-7
Bug #842347 {Done: Santiago Vila } [src:mpich] mpich: FTBFS 
randomly (cannot find -l-L/usr/lib/gcc/x86_64-linux-gnu/6)
No longer marked as fixed in versions 3.2-7.
> thanks
Stopping processing here.

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

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Jonas Smedegaard]

Quoting Adam Borowski (2016-12-25 23:23:32)
> On Sun, Dec 25, 2016 at 06:06:12PM +0100, Jonas Smedegaard wrote:
> > > I'm pretty sure they haven't produced XO-1s in close to a decade, and 
> > > that us what my packages are for.  XO-1.5 and XO-4 were never 
> > > supported without additional hacks.
> > > 
> > > That said, I can orphan the packages; I just don't see much point with 
> > > such old hardware and the lack of package users.
> > 
> > I agree it makes sense to drop this package: Despite the hardware vendor 
> > still issueing software, we can no longer do so, because the XO-1 uses 
> > an X86 chipset is incompatible with our i686 libc and kernel, I believe 
> > (I haven't tested for quite some time, though - please correct me if 
> > wrong).
> 
> XO-1 uses Geode LX which lacks just NOPL for full 686 ISA, and our version
> of gas doesn't issue NOPL for this reason.
> 
> It's possible there are other show stoppers, but I have no idea here.

Ah, interesting.  Then there might be hope still.  thanks!

@Andres: Please don't drop the OLPC packages.  I can adopt them and 
maintain them in the Sugar team (and will dust off my XO-1 laptops 
collecting dust in a shelf).

 - Jonas

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

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

Bug#829452: marked as done (axel: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 22:33:30 +
with message-id 
and subject line Bug#829452: fixed in axel 2.12-1
has caused the Debian Bug report #829452,
regarding axel: FTBFS with openssl 1.1.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.)


-- 
829452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alex
Version: 2.11-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-07-02/attempted/axel_2.11-1_amd64-20160702-2205

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: axel
Source-Version: 2.12-1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated axel 
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, 25 Dec 2016 19:48:14 -0200
Source: axel
Binary: axel
Architecture: source
Version: 2.12-1
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Description:
 axel   - light command line download accelerator
Closes: 829452
Changes:
 axel (2.12-1) unstable; urgency=medium
 .
   * New upstream release.
   * Ack for NMU. Thanks to Raphaël Hertzog .
 (Closes: #829452)
   * Bumped DH level to 10.
   * debian/copyright: added the right for a new upstream.
   * debian/patches/Fix-a-build-failure-when-using-OpenSSL-1.1.0.patch: dropped.
 The upstream already fixed the source code.
Checksums-Sha1:
 1611e7f8f2aeaed150bdbe3ee6a4ec0da9048d09 1839 axel_2.12-1.dsc
 50b2cc7ae66afe058fa9591c7e6acfee2adb8467 82995 axel_2.12.orig.tar.gz
 a28dc0bf5e86ee5d18ae7d9f735c44cb70d83f87 7488 axel_2.12-1.debian.tar.xz
Checksums-Sha256:
 958c8e8481aa227a654c82c79617f949595e4be71aa8027e20e66909a2a25d3f 1839 
axel_2.12-1.dsc
 28e7bb26b7be3f56a61b60ef07e15e05ea9a41850b0ed45a0c56d6d2202f4a8b 82995 
axel_2.12.orig.tar.gz
 fdac978d2830c98ae48f9066b7d105d06d36aa3d37fde1a3242aba8f278f9cc8 7488 
axel_2.12-1.debian.tar.xz
Files:
 0bab7d363e2af8fe2084deb817b3472e 1839 web optional axel_2.12-1.dsc
 30484a8ea524329e84e794b7888a426b 82995 web optional axel_2.12.orig.tar.gz
 cb6549f55ccfe26544b07ba324f47f5c 7488 web optional axel_2.12-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhgRqUACgkQ3mO5xwTr
6e/WgxAAk1Dvvz4wsp1qUbPaDCfKjC6SbWnv75AcapgAiA1hr5xxvHw2k/WnuuLR
aTWbnOwWAQFC/Nc6fjwRIMPi2qfOL7B9vwjSogwiqrQs1yhrCsrRgdjd8qI9LEPl
0eyT7H1PSd2zEvE9kI4t6tQW1U071BLHk8Z4bndq/FLv/W92a/1W+LDUBYSLBvZC
hFRJSz5+gaD9zfeaYVu2VZ1F2T65eB79D2mB9Z8Te4AoIhh973eW45+vkV2TNcta
zirJzYZtDnlUSOAmlPLqkypbEGx/v9Qg9xeX98PZpVusvNleXqIKHL3hsTq1agdt
XPtuTH5Ee7JA/j229v0QrgZBePXRARsEaccsWbZz4tmg+GpHFiRePuHKxkuzfI2X
3ZrNRcHK78neqcaajgv661cYU+amJGeHZHIrCzIM1cBH0LJLe8cLwP4BvTNWULzX
vyAPeP0PpLJv9i+GHXx44d3pql/9R1VnFdsPDFZEWgI2NBeFJjcHVgRiT56UwmGw
yHTShWFScX3TlH1IdM/NXHUayPC3nxLjnxQtg8eOQhN7PcdQYq6nSJ9iodvgj6WL
Q/Wra/OsEJp6IOrDvbvOHE60s8OrJCHv1X3sbKD7vgfWcqHq/ivxmdWqOa2zpBf/
Ox1AT/tBlWmQdLjgCL6e6FTKs1LItM7YF8Z2XqHmQ5xfpyyUgvQ=
=PPsm
-END PGP SIGNATURE End Message ---

Bug#835456: FTBFS: t/refhang.t test fail on s390x

[Ivo De Decker]

Control: found -1 1.4.28-1
Control: retitle -1 FTBFS: t/refhang.t test fail

Hi,

On Thu, Aug 25, 2016 at 10:27:33PM +0200, g...@iroqwa.org wrote:
> Just for the record, the upstream test suite fail on s390x
> 
> https://buildd.debian.org/status/fetch.php?pkg=memcached=s390x=1.4.31-1=1471823136
> 
> I'll open a issue to upstream to definitively fix it.

The issue also happens with version 1.4.28-1 (currently in testing) and on the
buildd on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=memcached=ppc64el=1.4.33-1=1478289801

I was able to reproduce it on amd64 by running the build in a loop (it failed
in less than 10 tries).

This probably is the same issue as #831253.

Cheers,

Ivo

Processed: Re: FTBFS: t/refhang.t test fail on s390x

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.4.28-1
Bug #835456 [src:memcached] FTBFS: t/refhang.t test fail on s390x
Marked as found in versions memcached/1.4.28-1.
> retitle -1 FTBFS: t/refhang.t test fail
Bug #835456 [src:memcached] FTBFS: t/refhang.t test fail on s390x
Changed Bug title to 'FTBFS: t/refhang.t test fail' from 'FTBFS: t/refhang.t 
test fail on s390x'.

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

Bug#831930: marked as done (spkproxy: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 22:23:07 +
with message-id 
and subject line Bug#831930: fixed in spkproxy 1.4.8-4.4
has caused the Debian Bug report #831930,
regarding spkproxy: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spkproxy
Version: 1.4.8-4.3
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for file in allwords bottomright.html CA.cert CA.pkey FileTemplate.xml 
> help.html index.html left.html notes.html passchecklist requestcache.html 
> scan_database.db server.cert server.pkey shortwords testpickle.pickle 
> titleframe.html topright.html words  ; do \
>   install -m644 $file 
> /<>/debian/spikeproxy//usr/share/spikeproxy/ ; \
> done
> for file in daveutil.py requestandresponse.py spikeProxyUI.py spkproxy.py 
> testform.py testfunc.py testpickle.py versioncheck.py VulnXML.py 
> whiskerdbtovulnxml.py read_query.py timeoutsocket.py ; do \
>   install -m755 $file 
> /<>/debian/spikeproxy//usr/share/spikeproxy/ ; \
> done
> for dir in testVulnXml VulnXML ntlm  ; do \
>   cp -a $dir /<>/debian/spikeproxy///usr/share/spikeproxy/ ; 
> \
> done
> make[1]: Leaving directory '/<>'
> install -m755 debian/spikeproxy-wrapper 
> `pwd`/debian/spikeproxy/usr/bin/spikeproxy
> cd debian/spikeproxy/usr/share/spikeproxy/ && ln -s 
> ../../../var/cache/spikeproxy/ cache
>  dpkg-genchanges --build=all >../spkproxy_1.4.8-4.3_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/spkproxy_1.4.8-4.3_unstable_archallonly.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: spkproxy
Source-Version: 1.4.8-4.4

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated spkproxy 
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, 25 Dec 2016 19:10:13 -0200
Source: spkproxy
Binary: spikeproxy
Architecture: source
Version: 1.4.8-4.4
Distribution: unstable
Urgency: medium
Maintainer: Javier 

Bug#836885: Re-add heimdal-multidev?

[Jelmer Vernooij]

On Sun, Dec 25, 2016 at 01:03:15PM -0800, Ryan Tandy wrote:
> On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote:
> > Now that heimdal has some upstream activity again and 7.1.0 has been
> > uploaded to unstable, is there a chance that openldap will reenable
> > support for "krb5" in "olcSmbK5PwdEnable"?
> 
> I really hope we can, but right now I'm reluctant to change anything until
> heimdal actually migrates to testing.
> 
> My understanding is since heimdal was removed it will be subject to the
> freeze on new packages entering testing (Jan 5th); and given the mips*
> builds currently appear to be blocked by #844357 or something resembling it,
> that doesn't look guaranteed. :/
> 
> If the new version of heimdal does enter testing I will for sure do my best
> to enable support for it in smbk5pwd again promptly.

FWIW Heimdal wasn't actually removed from testing - the new upstream version
happened before all the packages that depended on it were removed from testing
- but we can't really release with what's currently in testing.

Jelmer

Bug#846854: nagios2mantis: Don't depend on nagios3 which has been removed from unstable

[Moritz Mühlenhoff]

On Sat, Dec 03, 2016 at 06:54:26PM +0100, Bas Couwenberg wrote:
> Source: nagios2mantis
> Version: 3.1-1.1
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> Please update your package to deal with the nagios3 removal from Debian
> (#845765).

Or let's simply remove nagios2mantis, after all mantis has been removed
from Debian as well.

Cheers,
Moritz

Processed: severity of 849243 is important, severity of 848655 is important, forcibly merging 848655 849243

[Debian Bug Tracking System]

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

> severity 849243 important
Bug #849243 [reportbug] reportbug: TypeError: * wants int
Severity set to 'important' from 'grave'
> severity 848655 important
Bug #848655 [reportbug] reportbug crashes with error "TypeError: * wants int"
Severity set to 'important' from 'normal'
> forcemerge 848655 849243
Bug #848655 [reportbug] reportbug crashes with error "TypeError: * wants int"
Bug #849243 [reportbug] reportbug: TypeError: * wants int
Added tag(s) unreproducible and moreinfo.
Merged 848655 849243
> thanks
Stopping processing here.

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

Bug#849346: CVE-2015-3239

[Moritz Muehlenhoff]

Source: android-platform-external-libunwind
Severity: grave
Tags: security

Hi,
https://security-tracker.debian.org/tracker/CVE-2015-3239 has been fixed in
src:unwind, but is still needed in android-platform-external-libunwind

Cheers,
Moritz
 

Bug#831920: marked as done (newbiedoc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 21:33:52 +
with message-id 
and subject line Bug#831920: fixed in newbiedoc 0.8.0-2.1
has caused the Debian Bug report #831920,
regarding newbiedoc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: newbiedoc
Version: 0.8.0-2
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -d 
> /<>/debian/newbiedoc/usr/share/doc/newbiedoc/newbiedoc.berlios.de
> install -d 
> /<>/debian/newbiedoc/usr/share/doc/newbiedoc/newbiedoc.berlios.de/images
> install -d 
> /<>/debian/newbiedoc/usr/share/doc/newbiedoc/newbiedoc.berlios.de/wiki
> cp -aR newbiedoc.berlios.de/* 
> /<>/debian/newbiedoc/usr/share/doc/newbiedoc/newbiedoc.berlios.de
> cp newbiedoc /<>/debian/newbiedoc/usr/bin
> cp newbiedoc-icon.png 
> /<>/debian/newbiedoc/usr/share/doc/newbiedoc/newbiedoc.berlios.de/images
> make[1]: Leaving directory '/<>'
> dh_install debian/newbiedoc-icon.xpm usr/share/pixmaps
>  dpkg-genchanges --build=all >../newbiedoc_0.8.0-2_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/newbiedoc_0.8.0-2_unstable_archallonly.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: newbiedoc
Source-Version: 0.8.0-2.1

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated newbiedoc 
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, 25 Dec 2016 18:32:04 -0200
Source: newbiedoc
Binary: newbiedoc
Architecture: source
Version: 0.8.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Vanessa Gutierrez 
Changed-By: Giovani Augusto Ferreira 
Description:
 newbiedoc  - Debian documentation FOR newbies BY newbies
Closes: 831920
Changes:
 newbiedoc (0.8.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 10.
   * debian/compat: updated to 10.
   * debian/control:
   - Bumped Standards-Version to 3.9.8.
   * 

Bug#849345: The connman.postrm is plain wrong. It must remove the state dir only on purging

[Alf Gaida]

Package: connman
Version: 1.33-2
Severity: serious

Dear Maintainer,
that goes in per incident - reverting this would fix the situation.

Cheers Alf


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

Kernel: Linux 4.9.0-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages connman depends on:
ii  dbus 1.10.14-1
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libdbus-1-3  1.10.14-1
ii  libglib2.0-0 2.50.2-2
ii  libgnutls30  3.5.7-3
ii  libreadline7 7.0-1
ii  libxtables12 1.6.0+snapshot20161117-4
ii  lsb-base 9.20161125

Versions of packages connman recommends:
pn  bluez  
pn  ofono  
ii  wpasupplicant  2.6-2

Versions of packages connman suggests:
pn  connman-vpn  

-- no debconf information

Bug#842007: marked as done (python-pyftpdlib: FTBFS (test_on_incomplete_file_received fails))

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 21:12:07 +
with message-id 
and subject line Bug#842007: fixed in python-pyftpdlib 1.5.1-3
has caused the Debian Bug report #842007,
regarding python-pyftpdlib: FTBFS (test_on_incomplete_file_received 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.)


-- 
842007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pyftpdlib
Version: 1.5.1-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

conn.unwrap()
  File "/usr/lib/python2.7/ssl.py", line 813, in unwrap
s = self._sslobj.shutdown()
error: [Errno 0] Error

==
FAIL: test_on_incomplete_file_received 
(pyftpdlib.test.test_functional.TestCallbacks)
--
Traceback (most recent call last):
  File "/<>/pyftpdlib/test/__init__.py", line 178, in wrapper
raise err
AssertionError: error_temp not raised

==
FAIL: test_on_incomplete_file_received 
(pyftpdlib.test.test_functional.TestCallbacks)
--
Traceback (most recent call last):
  File "/<>/pyftpdlib/test/__init__.py", line 178, in wrapper
raise err
AssertionError: error_temp not raised

==
FAIL: test_on_incomplete_file_received (test_servers.TestCallbacksThreadMixin)
--
Traceback (most recent call last):
  File "/<>/pyftpdlib/test/__init__.py", line 178, in wrapper
raise err
AssertionError: error_temp not raised

==
FAIL: test_on_incomplete_file_received (test_functional.TestCallbacks)
--
Traceback (most recent call last):
  File "/<>/pyftpdlib/test/__init__.py", line 178, in wrapper
raise err
AssertionError: error_temp not raised

--
Ran 783 tests in 8.326s

FAILED (failures=4, errors=1, skipped=47)
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is very similar to Bug #790274 but here the test which fails is different.

The relevant part of the build log is included above, but I'm attaching
four different build logs as well.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the page for
this package.

If you could not reproduce this using sbuild on a single CPU virtual
machine (as I did), please do not downgrade or mark as unreproducible,
I would then consider giving you access to a virtual machine on which
I can reproduce it so that you can as well. (In such case, please
contact me off-list for details).

Also, even if it's Arch:all, it would be worth to upload this package
in source only form next time, so that we get pretty official build
logs here:

https://buildd.debian.org/status/package.php?p=python-pyftpdlib

and also avoid bugs like this one to propagate to testing.

Thanks.

python-pyftpdlib_1.5.1-2_amd64-20161024T093918Z.gz
Description: application/gzip


python-pyftpdlib_1.5.1-2_amd64-20161024T094525Z.gz
Description: application/gzip


python-pyftpdlib_1.5.1-2_amd64-20161024T104003Z.gz

Bug#836885: Re-add heimdal-multidev?

[Ryan Tandy]

On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote:

Now that heimdal has some upstream activity again and 7.1.0 has been
uploaded to unstable, is there a chance that openldap will reenable
support for "krb5" in "olcSmbK5PwdEnable"?


I really hope we can, but right now I'm reluctant to change anything 
until heimdal actually migrates to testing.


My understanding is since heimdal was removed it will be subject to the 
freeze on new packages entering testing (Jan 5th); and given the mips* 
builds currently appear to be blocked by #844357 or something resembling 
it, that doesn't look guaranteed. :/


If the new version of heimdal does enter testing I will for sure do my 
best to enable support for it in smbk5pwd again promptly.

Bug#848419: trac-announcer: FTBFS in stretch (failing tests)

[W. Martin Borgert]

It seems, that trac-announcer is not yet compatible with current
trac. The package will therefore not be in stretch. If a fixed
version is released, we can deliver it via backports.

Bug#842007: marked as pending

[W . Martin Borgert]

tag 842007 pending
thanks

Hello,

Bug #842007 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/python-pyftpdlib.git;a=commitdiff;h=095d22b

---
commit 095d22b07b57da77fdd2f7df6ddffba69b53ef9e
Author: W. Martin Borgert 
Date:   Sun Dec 25 20:44:21 2016 +

prepare 1.5.1-3

diff --git a/debian/changelog b/debian/changelog
index d694fda..a068dcf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-pyftpdlib (1.5.1-3) unstable; urgency=medium
+
+  * Set TRAVIS=1 to skip one unit test, marked by upstream as
+"failing on Travis" (Closes: #842007)
+
+ -- W. Martin Borgert   Sun, 25 Dec 2016 20:40:48 +
+
 python-pyftpdlib (1.5.1-2) unstable; urgency=medium
 
   * Build-Depend on python{,3}-openssl/python3-openssl and python{,3}-mock.

Processed: Bug#842007 marked as pending

[Debian Bug Tracking System]

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

> tag 842007 pending
Bug #842007 [src:python-pyftpdlib] python-pyftpdlib: FTBFS 
(test_on_incomplete_file_received fails)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Jonas Smedegaard]

Quoting Andres Salomon (2016-12-25 06:26:43)
> On December 24, 2016 7:24:00 PM PST, Paul Wise  wrote:
>>On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:
>>
>>> Thanks for the patch.  Given that OLPC isn't really alive any more,
>>> I'm thinking the OLPC packages should probably just be removed from
>>the
>>> archive for Stretch.  Popcon shows exactly 1 installation of this
>>> package.. https://qa.debian.org/popcon.php?package=olpc-xo1
>>
>>I think you will find that OLPC is still active and recently made a
>>release:
>>
>>http://lists.laptop.org/pipermail/devel/2016-December/thread.html
>>
>>They also have a Debian derivative:
>>
>>https://wiki.debian.org/Derivatives/Census/OLPC
>>
>>I've asked James to respond to your mail.
>>
> 
> 
> I meant OLPC the hardware organization.
>
> I'm glad to see James is still producing Fedora-based images for 
> legacy hardware.

For the record, OLPC is still alive, and still (pay James Cameron to 
help prepare, and) release (Fedora-derived) system images for the (no 
longer sold) XO-1 laptop.


> I'm pretty sure they haven't produced XO-1s in close to a decade, and 
> that us what my packages are for.  XO-1.5 and XO-4 were never 
> supported without additional hacks.
> 
> That said, I can orphan the packages; I just don't see much point with 
> such old hardware and the lack of package users.

I agree it makes sense to drop this package: Despite the hardware vendor 
still issueing software, we can no longer do so, because the XO-1 uses 
an X86 chipset is incompatible with our i686 libc and kernel, I believe 
(I haven't tested for quite some time, though - please correct me if 
wrong).


 - Jonas

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

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

Bug#836885: Re-add heimdal-multidev?

[Michael Fladischer]

Now that heimdal has some upstream activity again and 7.1.0 has been
uploaded to unstable, is there a chance that openldap will reenable
support for "krb5" in "olcSmbK5PwdEnable"?

Cheers,
Michael

Bug#817490: marked as done (hashcash: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 19:33:55 +
with message-id 
and subject line Bug#817490: fixed in hashcash 1.21-2
has caused the Debian Bug report #817490,
regarding hashcash: Removal of debhelper compat 4
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.)


-- 
817490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hashcash
Severity: important
Usertags: compat-4-removal

Hi,

The package hashcash uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: hashcash
Source-Version: 1.21-2

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated hashcash 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Dec 2016 10:48:59 -0200
Source: hashcash
Binary: hashcash
Architecture: source amd64
Version: 1.21-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Giovani Augusto Ferreira 
Description:
 hashcash   - postage payment scheme for email based on hash calculations
Closes: 817490
Changes:
 hashcash (1.21-2) unstable; urgency=medium
 .
   * QA upload.
   * Set Debian QA Group as maintainer (See: #831803)
   * Update DH level to 10. (Closes: #817490)
   * debian/compat: updated to 10.
   * debian/control:
  - Bumped Standards-Version to 3.9.8.
Checksums-Sha1:
 42a03ee9535e8d5869dfc1b292b47388a39c90db 1636 hashcash_1.21-2.dsc
 b060e8f25c1ddd13d41b9d1a1fdf15a9076f9381 6103 hashcash_1.21-2.diff.gz
 a35066f54de9aa6a8bd42943b3d4b3b5cf34170e 89212 hashcash-dbgsym_1.21-2_amd64.deb
 86f33ba31e123aa47b3205cf124ce641b833ac6b 4988 hashcash_1.21-2_amd64.buildinfo
 67bb1c946de1d704ff83df0b7262e7bae71ae757 134194 hashcash_1.21-2_amd64.deb
Checksums-Sha256:
 39a0b5def5762412a53439632ff2ecc5b1af7baff65a79fa7fd3bc1c3eee13ea 1636 
hashcash_1.21-2.dsc
 abcddff04153b0e665de2538fccde8c745d2bb0f6b06ce2df888af88b811013d 6103 
hashcash_1.21-2.diff.gz
 a5ce3bb83188fd69cef8c5651073cc6f8973844682bc1c0590286413b58000ae 89212 
hashcash-dbgsym_1.21-2_amd64.deb
 5a3a9650c1b95a2c1ef1569cdd6ccb721b9d694fe8453573c9799b85b50de144 4988 
hashcash_1.21-2_amd64.buildinfo
 9e6737633ed78c15695a6387f569458af7225a8ed947a9d1bba6f1a955825bcc 134194 
hashcash_1.21-2_amd64.deb
Files:
 cefe2f0647feb3107b7188533146ae13 1636 mail optional hashcash_1.21-2.dsc
 2ec0a8dcda630a4b3dec8207371e97f2 6103 mail optional hashcash_1.21-2.diff.gz
 dfa3a39fb3d878066c0cee08be5b62ef 89212 debug extra 
hashcash-dbgsym_1.21-2_amd64.deb
 1819f7f4891e4056767515413eb4ad34 4988 mail optional 
hashcash_1.21-2_amd64.buildinfo
 eb58f70b494a24dde971ea9259fedb51 134194 mail optional hashcash_1.21-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAlhgGS0ACgkQeElO9yN1
pmyDDxAAoQJ39LfY41ovbY8iNfByHqJv/9lZGLpCLcbFj5PQUBNZ99Deus4pvzOw
7CIBYb7aulv8LAbL/aoDKz2BNR9teVaztusW1eeLP2807BjYcrh4PqtfGmOinjvG
KeZ4NTslb+YMfUQ8uQQSOBeNIChIjgq+muDtI5gSfgPeppvOZO80c53YOoHUWXX4
djtQKbIi4vMz1LWKoCZ0jPW2K9teezQtjp59AskGRnj3VP+OPBtLEfMsMt5kUlmH
BX+PQyVnYxPY7UaKfPuxqLsLL9QrJziHm9IGqAd1Mqs2Q+mY11Y0Ddt91Euf8vKY
tOymB8G25Z/WteVcTonlVBk3PkocdZa1krui4v641cxPJ9pJ1rHF9PHNznD1VByC
loJkaBv0FKgHf4MkL+HDyJtolPcVMWZInplCxWa7gLA7VpQsBn7dh1fZKySVqBzD
x38PxxGuIY9OE4XBRxB/bU/jOhz662RDwwVlZ6yPj3vqyXyzycFoHHlbSmvPWg1P

Processed: severity of 849136 is important

[Debian Bug Tracking System]

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

> severity 849136 important
Bug #849136 [src:gdk-pixbuf] gdk-pixbuf FTBFS on mips64el: 
pixbuf-randomly-modified test failures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#817376: marked as done (bicyclerepair: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 19:18:54 +
with message-id 
and subject line Bug#817376: fixed in redet 8.26-1.2
has caused the Debian Bug report #817376,
regarding bicyclerepair: Removal of debhelper compat 4
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.)


-- 
817376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bicyclerepair
Severity: important
Usertags: compat-4-removal

Hi,

The package bicyclerepair uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: redet
Source-Version: 8.26-1.2

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated redet 
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, 25 Dec 2016 16:47:52 -0200
Source: redet
Binary: redet redet-doc
Architecture: source
Version: 8.26-1.2
Distribution: unstable
Urgency: medium
Maintainer: Bartosz Fenski 
Changed-By: Joao Eriberto Mota Filho 
Description:
 redet  - regular expression development and execution tool
 redet-doc  - regular expression development and execution tool (documentation)
Closes: 817376
Changes:
 redet (8.26-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817376)
   * debian/control:
   - Added the ${misc:Depends} variable to Depends field.
   - Bumped Standards-Version to 3.9.8.
   * debian/rules: added targets binary-arch (mandatory) and
 build-arch (recommended).
   * debian/watch: created.
Checksums-Sha1:
 3c621ef97599a4a299d4c889f7ea9ad666e9d78d 1723 redet_8.26-1.2.dsc
 b07ec2c8555f7889bc0a0f09b1fa091e33edca2a 4024 redet_8.26-1.2.diff.gz
Checksums-Sha256:
 9621bbf7364df3d70796cf16e7b66e8f990e9ec42b89ca4566d6e0cc78d22fea 1723 
redet_8.26-1.2.dsc
 f4b537211453892c08f86e7ea0cce68841a3a7543989e718b999c82fefcd4654 4024 
redet_8.26-1.2.diff.gz
Files:
 f8e5aff18c1f98fbd5dafab97fc19e3f 1723 x11 optional redet_8.26-1.2.dsc
 adcb7ebcf0dbf850f96f3a26f3c9cff9 4024 x11 optional redet_8.26-1.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlhgFikACgkQ3mO5xwTr
6e/ZoQ/+LXtG/ZFDtb1jLuBlvb4dKQWqcAMD6Cj9b35KPJcAr1oh95l4g+ZNfUty
rmtk4K9zIVBAVJKLtIPJGFCkS+f1mLdQuA5SS9v/bAoOXam37kVxaKTWoQaWiVy5
w6yZdCc2HfxGj24DmFdGSljkJfiuvSyH1aaUtmxidovOv27hhZ0+dCoOGJsUAO1O
JLoXMBp0KqrlX7kDknelxLknMtDkZhPJdJWVAe1ec0/s8ybJWrmvZfO8VDVJ3hn6
Kskt+BFREzscFWsd3XIE+d+IGXe47rK7Cif4r8D6eLWhBXVrn/4W6tLGhIEeL+pI
eA8JKTNp3Gcddn2FZG4qAwvr8PdGmpMGyFEwSUdIWVlzzdiuPMIQy0gB+WubTMcV
mmwuyel2s1Zc95faPf1sIvwvldZQP624rsQIzbEnFCCaEMtF9zWhLVu9aSzT/DWd
cD+sZvp2zooowadbjVNQVRhAwMThZzj+S4klJg1YQ/rYoBrwkbDsfqnUnfg1w/pC
RCS9duvbkRdfQn69ye0+UVxeb6/nOZcU5+3aRQi2WfidTQV+B30jfztjpk2CDeqn
k8VYQkNPdHIAS6mdXxJvSUFGrapezmDqn+aze8IXfVoRwvezi3/8en6KVgMSLPuC
KbLfYaT4jwGcCaTA4iR+/qQvj5d9WxqAErjoAjJMKzQO6OUThKg=
=N2b5
-END PGP SIGNATURE End Message ---

Bug#828287: marked as done (dsniff: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 16:51:36 -0200
with message-id 

Bug#828525: qupzilla: diff for NMU version 1.8.9~dfsg1-3.1

[Georges Khaznadar]

Thank you very much, Andrey!

Andrey Rahmatullin a écrit :
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for qupzilla (versioned as 1.8.9~dfsg1-3.1). The diff
> is attached to this message.
> 
> Regards.
> 
> -- 
> WBR, wRAR

> diff -Nru qupzilla-1.8.9~dfsg1/debian/changelog 
> qupzilla-1.8.9~dfsg1/debian/changelog
> --- qupzilla-1.8.9~dfsg1/debian/changelog 2016-01-23 20:42:31.0 
> +0500
> +++ qupzilla-1.8.9~dfsg1/debian/changelog 2016-12-18 20:22:33.0 
> +0500
> @@ -1,3 +1,10 @@
> +qupzilla (1.8.9~dfsg1-3.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Build with OpenSSL 1.0 (Closes: #828525).
> +
> + -- Andrey Rahmatullin   Sun, 18 Dec 2016 20:22:33 +0500
> +
>  qupzilla (1.8.9~dfsg1-3) unstable; urgency=medium
>  
>* removed the dependency on libqt5xcbqpa5. Closes: #812233
> diff -Nru qupzilla-1.8.9~dfsg1/debian/control 
> qupzilla-1.8.9~dfsg1/debian/control
> --- qupzilla-1.8.9~dfsg1/debian/control   2016-01-23 20:42:16.0 
> +0500
> +++ qupzilla-1.8.9~dfsg1/debian/control   2016-12-18 20:22:33.0 
> +0500
> @@ -7,7 +7,7 @@
>   qtbase5-private-dev, qtscript5-dev,
>   libqt5x11extras5-dev,
>   libx11-dev,
> - libssl-dev, kdelibs5-dev, libgnome-keyring-dev,
> + libssl1.0-dev | libssl-dev (<< 1.1.0~), kdelibs5-dev, libgnome-keyring-dev,
>   libjs-jquery, libjs-jquery-ui
>  Standards-Version: 3.9.7
>  Homepage: http://www.qupzilla.com/





signature.asc
Description: PGP signature

Bug#849334: [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file

[Ximo Baldó i Soriano]

Package: dnscrypt-proxy
Version: 1.8.1-3
Severity: serious

--- Please enter the report below this line. ---
Since last upgrade, Dnscrypt fails to start due search configuration file at 
path that does 
not exist.

Service file (/lib/systemd/system/dnscrypt-proxy.service) has incorrect path on 
Exec line:
ExecStart=/usr/sbin/dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf

and, on my system, since last update dnscrypt-proxy.conf is located at 
/etc/dnscrypt-proxy/dnscrypt-proxy.conf/dnscrypt-proxy.conf


Service file after update:

[Unit]
Description=DNSCrypt client proxy Documentation=man:dnscrypt-proxy(8) 
Requires=dnscrypt-proxy.socket After=network.target Before=nss-lookup.target 

[Install] Also=dnscrypt-proxy.socket WantedBy=multi-user.target 

[Service] Type=notify NonBlocking=true User=_dnscrypt-proxy ExecStart=/usr/sbin/
dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf Restart=always 
ProtectSystem=strict ProtectHome=true ProtectKernelModules=true 
ProtectKernelTunables=true ProtectControlGroups=true 
MemoryDenyWriteExecute=true 
RestrictRealtime=true




Directory structure on disk:

~$ tree /etc/dnscrypt-proxy/
/etc/dnscrypt-proxy/└── dnscrypt-proxy.conf   └── dnscrypt-proxy.conf



Modifying incorrect path on systemd service file or moving config file to path 
in systemd 
service file makes dnscrypt work correctly again.

--- System information. ---
Architecture: 
Kernel:   Linux 4.8.0-2-amd64

Debian Release: stretch/sid
  950 unstablewww.deb-multimedia.org 
  900 unstable-debug  deb.debian.org 
  900 unstableftp.debian.org 
  800 experimentalftp.debian.org 
  500 stable  people.debian.org 
 
--- Package information. ---
Depends   (Version) | Installed
===-+-
adduser | 3.115
lsb-base (>= 3.0-6) | 9.20161125
init-system-helpers  (>= 1.18~) | 1.46
libc6 (>= 2.17) | 
libltdl7 (>= 2.4.6) | 
libsodium18 (>= 1.0.10) | 
libsystemd0 | 


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
resolvconf| 




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

Processed: Re: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Debian Bug Tracking System]

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

> tags 849333 + patch
Bug #849333 [src:faker] faker: Non-determistically FTBFS due to tests sometimes 
exposing UnboundLocalError
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

forwarded 849333 https://github.com/joke2k/faker/pull/441
thanks

I've forwarded this upstream here:

   https://github.com/joke2k/faker/pull/441


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

tags 849333 + patch
thanks

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/faker/providers/ssn/fi_FI/__init__.py 
b/faker/providers/ssn/fi_FI/__init__.py
index 44d9ff3..bba2c0b 100644
--- a/faker/providers/ssn/fi_FI/__init__.py
+++ b/faker/providers/ssn/fi_FI/__init__.py
@@ -39,7 +39,7 @@ class Provider(SsnProvider):
 if birthday.year < 2000:
 separator = '-'
 else:
-separator += 'A'
+separator = 'A'
 suffix = str(random.randrange(2, 899)).zfill(3)
 checksum = _checksum(hetu_date + suffix)
 hetu = "".join([hetu_date, separator, suffix, checksum])

Processed: Re: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Debian Bug Tracking System]

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

> forwarded 849333 https://github.com/joke2k/faker/pull/441
Bug #849333 [src:faker] faker: Non-determistically FTBFS due to tests sometimes 
exposing UnboundLocalError
Set Bug forwarded-to-address to 'https://github.com/joke2k/faker/pull/441'.
> thanks
Stopping processing here.

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

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

[Chris Lamb]

Source: faker
Version: 0.7.7-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

faker's testsuite appears to non-deterministically vary in behaviour,
causing a FTBFS when it exposes a programming error:

  […]

  ==
  ERROR: test_documentor (faker.tests.FactoryTestCase)
  --
  Traceback (most recent call last):
File "faker/tests/__init__.py", line 207, in test_documentor
  print_doc(output=output)
File "faker/cli.py", line 110, in print_doc
  excludes=base_provider_formatters):
File "faker/documentor.py", line 32, in get_formatters
  (provider, self.get_provider_formatters(provider, **kwargs))
File "faker/documentor.py", line 87, in get_provider_formatters
  example = self.generator.format(name)
File "faker/generator.py", line 66, in format
  return self.get_formatter(formatter)(*args, **kwargs)
File "faker/providers/profile/__init__.py", line 47, in profile
  "ssn": self.generator.ssn(),
File "faker/providers/ssn/fi_FI/__init__.py", line 42, in ssn
  separator += 'A'
  UnboundLocalError: local variable 'separator' referenced before assignment
  
  --
  Ran 45 tests in 2.150s
  
  FAILED (errors=1)
  debian/rules:27: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


faker.0.7.7-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#848266: marked as done (libparanoid-perl: FTBFS: tests timeout)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 17:48:28 +
with message-id 
and subject line Bug#848266: fixed in libparanoid-perl 2.04-2
has caused the Debian Bug report #848266,
regarding libparanoid-perl: FTBFS: tests timeout
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.)


-- 
848266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libparanoid-perl
Version: 2.04-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

libparanoid-perl fails to build from source in unstable/amd64:

  […]

  ok 23 - test/2/1 == "-P"
  ok 24 - parseArgs 8
  ok 25 - error string matches
  ok 26 - parseArgs 9
  ok 27 - error string matches
  ok 28 - parseArgs 10
  ok 29 - error string matches
  ok 30 - parseArgs 10
  ok 31 - error string matches
  ok 32 - parseArgs 10
  ok 33 - error string matches
  ok
  t/12_lockfile.t . 
  1..6
  ok 1 - plock excluse 1
  ok 2 - plock exclusive 2
  ok 3 - plock share 1
  ok 4 - pexclock 1
  ok 5 - pshclock 1
  ok 6 - punlock 1
  ok
  t/20_filesystem_pmkdir.t  
  1..9
  ok 1 - pmkdir 1
  ok 2 - pmkdir 2
  ok 3 - pmkdir 3
  ok 4 - pmkdir perms 1
  ok 5 - pmkdir 4
  ok 6 - pmkdir 5
  ok 7 - pmkdir 6
  ok 8 - pmkdir 7
  ok 9 - pmkdir 8
  ok
  t/21_filesystem_preadDir.t .. 
  1..18
  ok 1 - preadDir 1
  ok 2 - preadDir 2
  ok 3 - preadDir 3
  ok 4 - preadDir 4
  ok 5 - preadDir 5
  ok 6 - preadDir 6
  ok 7 - psubdirs 1
  ok 8 - psubdirs 2
  ok 9 - psubdirs 3
  ok 10 - psubdirs 4
  ok 11 - psubdirs 5
  ok 12 - psubdirs 6
  ok 13 - pfiles 1
  ok 14 - pfiles 2
  ok 15 - pfiles 3
  ok 16 - pfiles 4
  ok 17 - pfiles 5
  ok 18 - pfiles 6
  ok
  t/22_filesystem_prm.t ... 
  1..9
  ok 1 - prm single 1
  ok 2 - prm glob 1
  ok 3 - prm glob 2
  ok 4 - prmR 1
  ok 5 - prmR 2
  ok 6 - prmR 3
  ok 7 - prmR 4
  ok 8 # skip Running as root -- skipping permissions test
  ok 9 - prmR 6
  ok
  t/23_filesystem_ptouch.t  
  1..14
  ok 1 - ptouch missing 1
  ok 2 - ptouch single 1
  ok 3 - ptouch single 2
  ok 4 - ptouch checking atime 1
  ok 5 - ptouch checking mtime 1
  ok 6 - ptouch single 4
  ok 7 - ptouchR nofollow 1
  ok 8 - ptouchR checking atime 1
  ok 9 - ptouchR checking atime 1
  ok 10 - ptouchR follow 1
  ok 11 - ptouchR checking atime 2
  ok 12 - ptouchR checking mtime 2
  ok 13 - ptouchR glob 1
  ok 14 - error message
  ok
  t/24_filesystem_misc.t .. 
  1..12
  ok 1 - pcleanPath 1
  ok 2 - pcleanPath 2
  ok 3 - pcleanPath 3
  ok 4 - pcleanPath 4
  ok 5 - pcleanPath 5
  ok 6 - pcleanPath 6
  ok 7 - pcleanPath 7
  ok 8 - ptranslateLink 1
  ok 9 - ptranslateLink 2
  ok 10 - pwhich 1
  ok 11 - pwhich 2
  ok 12 - pwhich 3
  ok
  t/25_filesystem_pchmod.t  
  1..19
  ok 1 - perms match (ugo+rwxt)
  ok 2 - perms match (u+rwxs)
  ok 3 - perms match (ug+rwx)
  ok 4 - perms undef ()
  ok 5 - perms undef (0990)
  ok 6 - perms undef (xr+uG)
  ok 7 - pchmod 1
  ok 8 - pchmod 2
  ok 9 - pchmod 3
  ok 10 - pchmod 4
  ok 11 - pchmod 5
  ok 12 - pchmodR 1
  ok 13 - pchmodR 2
  ok 14 - pchmodR 3
  ok 15 - pchmodR 4
  ok 16 - pchmodR 5
  ok 17 - pchmodR 6
  ok 18 - pchmodR 7
  ok 19 - pchmodR 7
  ok
  t/26_filesystem_pchown.t  
  1..15
  ok 1 # skip Non-root user running tests
  ok 2 # skip Non-root user running tests
  ok 3 # skip Non-root user running tests
  ok 4 # skip Non-root user running tests
  ok 5 # skip Non-root user running tests
  ok 6 # skip Non-root user running tests
  ok 7 # skip Non-root user running tests
  ok 8 # skip Non-root user running tests
  ok 9 # skip Non-root user running tests
  ok 10 # skip Non-root user running tests
  ok 11 # skip Non-root user running tests
  ok 12 # skip Non-root user running tests
  ok 13 # skip Non-root user running tests
  ok 14 # skip Non-root user running tests
  ok 15 # skip Non-root user running tests
  ok
  t/30_log.t .. 
  1..9
  ok 1 - startLogger 1
  ok 2 - startLogger 2
  ok 3 - plog 1a
  ok 4 - plog 1b
  ok 5 - stopLogger 1
  ok 6 - plog 2
  ok 7 - plog 3
  ok 8 - plog 4
  ok 9 - plog 5
  ok
  t/31_log_buffer.t ... 
  1..20
  ok 1 - startLogger 1
  ok 2 - plog 1
  ok 3 - dumpBuffer 1
  ok 4 - check message 1
  ok 5 - plog 2
  ok 6 - dumpBuffer 2
  ok 7 - startLogger 2
  ok 8 - plog 3
  ok 9 - dumpBuffer 3
  ok 10 - plog 4
  ok 11 - dumpBuffer 4
  ok 12 - plog 5
  ok 13 - dumpBuffer 5
  ok 14 - dumpBuffer 6
  ok 15 - check message 2
  ok 16 - 

Processed: bug 848266 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=119462

[Debian Bug Tracking System]

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

> forwarded 848266 https://rt.cpan.org/Ticket/Display.html?id=119462
Bug #848266 [src:libparanoid-perl] libparanoid-perl: FTBFS: tests timeout
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=119462'.
> thanks
Stopping processing here.

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

Processed: found 849264 in 53.0.2785.143-1

[Debian Bug Tracking System]

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

> found 849264 53.0.2785.143-1
Bug #849264 [src:chromium-browser] chromium-browser: copyright file is 
incomplete
Marked as found in versions chromium-browser/53.0.2785.143-1.
> thanks
Stopping processing here.

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

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Chris Lamb]

Jérémy Bobbio wrote:

> > I deliberately used python3 to match the behaviour of what the
> > /usr/bin/enjarify script does.
> 
> Guess it's worth adding a comment about it for future readers. :)

Excellent point; added in 53c649cef48de11e1584a09795ad890dcdb95eb4.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#849126: marked as done (FTBFS: several errors when building)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 15:18:59 +
with message-id 
and subject line Bug#849126: fixed in logtools 0.13e
has caused the Debian Bug report #849126,
regarding FTBFS: several errors when building
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.)


-- 
849126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: logtools
Version: 0.13d
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

When trying build logtools in Sid over GCC-6, I got these error messages:

clfmerge.cpp:22:63: error: template argument 3 is invalid
 hash_map, eqstr> months;
   ^
clfmerge.cpp: In member function ‘int LogFile::setDate()’:
clfmerge.cpp:86:29: error: invalid conversion from ‘char’ to ‘const char*’ 
[-fpermissive]
   const char *m = months[mon];
   ~~^
clfmerge.cpp: In function ‘int main(int, char**)’:
clfmerge.cpp:229:19: error: assignment of read-only location ‘"Jan"[months]’
   months["Jan"] = "01";
   ^~~~
clfmerge.cpp:229:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:230:19: error: assignment of read-only location ‘"Feb"[months]’
   months["Feb"] = "02";
   ^~~~
clfmerge.cpp:230:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:231:19: error: assignment of read-only location ‘"Mar"[months]’
   months["Mar"] = "03";
   ^~~~
clfmerge.cpp:231:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:232:19: error: assignment of read-only location ‘"Apr"[months]’
   months["Apr"] = "04";
   ^~~~
clfmerge.cpp:232:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:233:19: error: assignment of read-only location ‘"May"[months]’
   months["May"] = "05";
   ^~~~
clfmerge.cpp:233:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:234:19: error: assignment of read-only location ‘"Jun"[months]’
   months["Jun"] = "06";
   ^~~~
clfmerge.cpp:234:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:235:19: error: assignment of read-only location ‘"Jul"[months]’
   months["Jul"] = "07";
   ^~~~
clfmerge.cpp:235:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:236:19: error: assignment of read-only location ‘"Aug"[months]’
   months["Aug"] = "08";
   ^~~~
clfmerge.cpp:236:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:237:19: error: assignment of read-only location ‘"Sep"[months]’
   months["Sep"] = "09";
   ^~~~
clfmerge.cpp:237:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:238:19: error: assignment of read-only location ‘"Oct"[months]’
   months["Oct"] = "10";
   ^~~~
clfmerge.cpp:238:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:239:19: error: assignment of read-only location ‘"Nov"[months]’
   months["Nov"] = "11";
   ^~~~
clfmerge.cpp:239:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
clfmerge.cpp:240:19: error: assignment of read-only location ‘"Dec"[months]’
   months["Dec"] = "12";
   ^~~~
clfmerge.cpp:240:19: error: invalid conversion from ‘const char*’ to ‘char’ 
[-fpermissive]
Makefile:17: recipe for target 'clfmerge' failed
make[1]: *** [clfmerge] Error 1


Regards,

Eriberto

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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: logtools
Source-Version: 0.13e

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

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Ole Streicher]

OK, I will re-upload directly to ftp-master.

Andreas, since you already moved and cleaned up skimage: would you do
the same for pandas and statsmodels? For statsmodels, I will already put
the new VCS into d/control and do a team upload (pushing the changes as
soon as the git is there).

Cheers

Ole

On 25.12.2016 14:42, Yaroslav Halchenko wrote:
> On December 25, 2016 7:29:09 AM EST, Ole Streicher  wrote:
>> Hi Yaroslav, Michael,Andreas,
>>
>> I uploaded the NMU as release 1.1 to DELAYED/2 now. I preferred NMU
>> since I am not a NeuroDebian team member.
>>
>> And I would (again) propose to move the package to debian-science. It
>> would also be useful to have it with the default structure (with
>> upstream and pristine-tar branches).
>>
>> Best regards
>>
>> Ole
>>
>> On 25.12.2016 10:43, Ole Streicher wrote:
>>> I'll upload to DELAYED ASAP (need to learn how to do this anyway);
>>> however the unresolved problem is still the pandas FTBFS. Without
>> that,
>>> statsmodels will not migrate.
>>>
>>> Cheers
>>>
>>> Ole
>>>
>>> On 25.12.2016 08:34, Andreas Tille wrote:
 Hi Ole,

> the attached patch fixes the FTBFS. What is the schedule to fix the
> other problems with statsimage -- especially pandas?

 I learned that NeuroDebian is happy about team uploads / NMUs - so
 I think its fine if you upload your patch.

 Kind regards

 Andreas.

 PS: If you are not convinced and there is no response from Yaroslav
>> or
 Michael in the next 24 hours - well, people are occupied by real
>> life
 these days, yust tell me and I'd upload.

> 
> You can go ahead and upload without delays. 
> If you see somehow that moving under another bigger team would make package 
> better, you have my blessing for pandas and statsmodels
> 
> Cheers
> 

Processed: Re: Bug#849261: webcamd: FTBFS in testing (no binary artifacts)

[Debian Bug Tracking System]

Processing control commands:

> tags 849261 pending
Bug #849261 [src:webcamd] webcamd: FTBFS in testing (no binary artifacts)
Added tag(s) pending.

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

Bug#849260: gav-themes: FTBFS in testing (no binary artifacts)

[Christoph Biedl]

Control: tags 849260 pending

Santiago Vila wrote...

> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Only the NMUer is to blame for this. So in a last-minute attempt to
fix this for stretch:

Find below the debdiff for a NMU I've prepared for gav-themes (versioned
as 0.7.3-2.2), upload will follow shortly. Please object ASAP if
you disagree -  but keep in mind then this is the last chance to get
this package into stretch, if at all.

Christoph

diff -u gav-themes-0.7.3/debian/changelog gav-themes-0.7.3/debian/changelog
--- gav-themes-0.7.3/debian/changelog
+++ gav-themes-0.7.3/debian/changelog
@@ -1,3 +1,10 @@
+gav-themes (0.7.3-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix another FTBFS, patch by Santiago Vila. Closes: #849260
+
+ -- Christoph Biedl   Sun, 25 Dec 2016 
13:50:40 +0100
+
 gav-themes (0.7.3-2.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -u gav-themes-0.7.3/debian/rules gav-themes-0.7.3/debian/rules
--- gav-themes-0.7.3/debian/rules
+++ gav-themes-0.7.3/debian/rules
@@ -58,12 +58,12 @@
#$(MAKE) install DESTDIR=$(CURDIR)/debian/gav-themes
dh_install
 
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
 # Build architecture-dependent files here.
 binary-arch: build install
+# We have nothing to do by default.
+
+# Build architecture-independent files here.
+binary-indep: build install
dh_testdir
dh_testroot
 #  dh_installdebconf   


signature.asc
Description: Digital signature

Bug#849261: webcamd: FTBFS in testing (no binary artifacts)

[Christoph Biedl]

Control: tags 849261 pending

Santiago Vila wrote...

> Dear maintainer:
>·
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Only the NMUer is to blame for this. So in a last-minute attempt to
fix this for stretch:

Find below the debdiff for a NMU I've prepared for webcamd (versioned
as 0.7.6-5.2), upload will follow shortly. Please object ASAP if
you disagree - but keep in mind then this is the last chance to get
this package into stretch, if at all.

Christoph

diff -Nru webcamd-0.7.6/debian/changelog webcamd-0.7.6/debian/changelog
--- webcamd-0.7.6/debian/changelog  2016-12-18 23:29:31.0 +0100
+++ webcamd-0.7.6/debian/changelog  2016-12-25 13:55:37.0 +0100
@@ -1,3 +1,10 @@
+webcamd (0.7.6-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix another FTBFS, patch by Santiago Vila. Closes: #849261
+
+ -- Christoph Biedl   Sun, 25 Dec 2016 
13:55:37 +0100
+
 webcamd (0.7.6-5.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru webcamd-0.7.6/debian/rules webcamd-0.7.6/debian/rules
--- webcamd-0.7.6/debian/rules  2016-12-18 23:29:31.0 +0100
+++ webcamd-0.7.6/debian/rules  2016-12-25 13:55:37.0 +0100
@@ -45,12 +45,12 @@
$(MAKE) install DESTDIR=$(CURDIR)/debian/webcamd
 
 
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
 # Build architecture-dependent files here.
 binary-arch: build install
+# We have nothing to do by default.
+
+# Build architecture-independent files here.
+binary-indep: build install
dh_testdir
dh_testroot
dh_installdocs


signature.asc
Description: Digital signature

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Yaroslav Halchenko]

On December 25, 2016 7:29:09 AM EST, Ole Streicher  wrote:
>Hi Yaroslav, Michael,Andreas,
>
>I uploaded the NMU as release 1.1 to DELAYED/2 now. I preferred NMU
>since I am not a NeuroDebian team member.
>
>And I would (again) propose to move the package to debian-science. It
>would also be useful to have it with the default structure (with
>upstream and pristine-tar branches).
>
>Best regards
>
>Ole
>
>On 25.12.2016 10:43, Ole Streicher wrote:
>> I'll upload to DELAYED ASAP (need to learn how to do this anyway);
>> however the unresolved problem is still the pandas FTBFS. Without
>that,
>> statsmodels will not migrate.
>> 
>> Cheers
>> 
>> Ole
>> 
>> On 25.12.2016 08:34, Andreas Tille wrote:
>>> Hi Ole,
>>>
 the attached patch fixes the FTBFS. What is the schedule to fix the
 other problems with statsimage -- especially pandas?
>>>
>>> I learned that NeuroDebian is happy about team uploads / NMUs - so
>>> I think its fine if you upload your patch.
>>>
>>> Kind regards
>>>
>>> Andreas.
>>>
>>> PS: If you are not convinced and there is no response from Yaroslav
>or
>>> Michael in the next 24 hours - well, people are occupied by real
>life
>>> these days, yust tell me and I'd upload.
>>>

You can go ahead and upload without delays. 
If you see somehow that moving under another bigger team would make package 
better, you have my blessing for pandas and statsmodels

Cheers
-- 
Sent from a phone which beats iPhone.

Processed: Re: Bug#849260: gav-themes: FTBFS in testing (no binary artifacts)

[Debian Bug Tracking System]

Processing control commands:

> tags 849260 pending
Bug #849260 [src:gav-themes] gav-themes: FTBFS in testing (no binary artifacts)
Added tag(s) pending.

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

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Ole Streicher]

Hi Yaroslav, Michael,Andreas,

I uploaded the NMU as release 1.1 to DELAYED/2 now. I preferred NMU
since I am not a NeuroDebian team member.

And I would (again) propose to move the package to debian-science. It
would also be useful to have it with the default structure (with
upstream and pristine-tar branches).

Best regards

Ole

On 25.12.2016 10:43, Ole Streicher wrote:
> I'll upload to DELAYED ASAP (need to learn how to do this anyway);
> however the unresolved problem is still the pandas FTBFS. Without that,
> statsmodels will not migrate.
> 
> Cheers
> 
> Ole
> 
> On 25.12.2016 08:34, Andreas Tille wrote:
>> Hi Ole,
>>
>>> the attached patch fixes the FTBFS. What is the schedule to fix the
>>> other problems with statsimage -- especially pandas?
>>
>> I learned that NeuroDebian is happy about team uploads / NMUs - so
>> I think its fine if you upload your patch.
>>
>> Kind regards
>>
>> Andreas.
>>
>> PS: If you are not convinced and there is no response from Yaroslav or
>> Michael in the next 24 hours - well, people are occupied by real life
>> these days, yust tell me and I'd upload.
>>

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Jérémy Bobbio]

Chris Lamb:
> Daniel Shahaf wrote:
> 
> > > +if subprocess.call(
> > > +('python3', '-c', 'import enjarify.typeinference'),
> > 
> > Use sys.executable instead of hardcoding 'python3', to handle the case
> > that there's more than one python3 binary on the system?
> 
> I deliberately used python3 to match the behaviour of what the
> /usr/bin/enjarify script does.

Guess it's worth adding a comment about it for future readers. :)

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#845050: marked as done (python-hpilo FTBFS in stretch due to missing python-cloud-sptheme)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 12:51:34 +0100
with message-id <20161225115134.GA13457@sx>
and subject line Re: #845050: python-hpilo FTBFS in stretch due to missing 
python-cloud-sptheme
has caused the Debian Bug report #845050,
regarding python-hpilo FTBFS in stretch due to missing python-cloud-sptheme
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.)


-- 
845050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-hpilo
Version: 3.8-1
Severity: serious
Tags: stretch
Control: block -1 by 829230

python-hpilo build-depends on python-cloud-sptheme,
which is not in stretch due to #829230
--- End Message ---
--- Begin Message ---
cloud-sptheme has reentered testing.--- End Message ---

Processed: tag 806037

[Debian Bug Tracking System]

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

> tags 806037 + pending
Bug #806037 [src:gnumail] gnumail: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: block 845050 with 829230

[Debian Bug Tracking System]

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

> block 845050 with 829230
Bug #845050 [src:python-hpilo] python-hpilo FTBFS in stretch due to missing 
python-cloud-sptheme
845050 was blocked by: 829230
845050 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #845050 to the same blocks 
previously set
> thanks
Stopping processing here.

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

Bug#849164: severity is critical

[Adam Borowski]

On Sun, Dec 25, 2016 at 11:08:58AM +, Pedro Ribeiro wrote:
> severity 849164 critical

To issue a command, you need to either CC control@b.d.o or prefix the
pseudoheader with "Control: ".

> critical as the package cannot be installed

Nope, "critical" applies if the bug:
* breaks the whole system the package is installed on
* introduces a severe security hole
* breaks _unrelated_ software

A plugin such as -ext-pack is definitely not unrelated.

The proper severity for "the package is not installable" is merely "grave". 
Not that this matters, all RC severities bring the same practical
consequences.

> after upgrading virtualbox I cannot start previously suspended VM's

Just discard the saved state.  This is identical to pulling the power plug
on a physical machine.

Yeah, a hard power cycle is not nice but virtualbox fails this way for most
unexpected configuration changes, even blase ones like a disk being
inaccessible (RAID testing anyone?).

Alternatively, you can use dpkg --force-depends and pray the dependency
mismatch is just a mistake (which, judging from upstream versions being the
same, it's quite likely).


Gianfranco can give you a real answer, but AFAIK he's off to the family
(such a surprise during Xmas!) thus might not respond immediately -- that's
why I'm telling you about the "pull the plug" workaround.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#849063: marked as done (src:haskell-mode: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 11:33:36 +
with message-id 
and subject line Bug#849063: fixed in haskell-mode 16.1-2
has caused the Debian Bug report #849063,
regarding src:haskell-mode: maintainer address bounces
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.)


-- 
849063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-mode
Source-Version: 16.1-1
Severity: serious

The maintainer address for haskell-mode bounces, see below.

Ansgar

Mail Delivery System writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   mornf...@debian.org
> Unrouteable address
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> Subject: haskell-mode_16.1-1_amd64.changes ACCEPTED into unstable
[...]
> Date: Mon, 19 Dec 2016 15:06:08 +
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Mon, 19 Dec 2016 14:57:00 +0100
> Source: haskell-mode
> Binary: haskell-mode
> Architecture: source all
> Version: 16.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Petr Rockai 
> Changed-By: Barak A. Pearlmutter 
> Description:
>  haskell-mode - major mode for editing Haskell in Emacs
> Changes:
>  haskell-mode (16.1-1) unstable; urgency=medium
>  .
>* New upstream release
>* dh10 is --parallel by default
>* Simplify build scripts for simpler (more rational) upstream build process
> Checksums-Sha1:
>  05b91d7084b714b9be01a8b3c68cb3e23963d9f5 2068 haskell-mode_16.1-1.dsc
>  58a961f5f4c0875872e00955a1c4b30c2b4125ae 1192866 
> haskell-mode_16.1.orig.tar.gz
>  b9b882d7a264e26486d3f5822f075a6f41cce344 7068 
> haskell-mode_16.1-1.debian.tar.xz
>  09c911faa3e41fcb70b261c68f15c1d3fa3a1d43 186822 haskell-mode_16.1-1_all.deb
>  b6a4a9ca50e6a33c4fdd775dbec59c0cc00ca12a 8726 
> haskell-mode_16.1-1_amd64.buildinfo
> Checksums-Sha256:
>  80dd211625990d5caca065db86221b924a54f5cffed2dadd5537983fc69b9954 2068 
> haskell-mode_16.1-1.dsc
>  109d9a0070825745c20f590c7fd0a1d2bb873d931db5ecc7deea317ab864d43c 1192866 
> haskell-mode_16.1.orig.tar.gz
>  35156763f487ecb606bab0bbbf8856816b327b2696a9d677810002a0d5577c7a 7068 
> haskell-mode_16.1-1.debian.tar.xz
>  cc26fac3d18be32235f099edf67820aa346819dbcc07e2023261e85fd6b0df55 186822 
> haskell-mode_16.1-1_all.deb
>  60fcabdec9da4b769a1124c1aae5eafc801109f0246bcfcd38d35e064db12c34 8726 
> haskell-mode_16.1-1_amd64.buildinfo
> Files:
>  d48155b79c893e1540961c2981e8c6be 2068 haskell optional 
> haskell-mode_16.1-1.dsc
>  2ad24b91681a6eda4e3384f4851bd3ad 1192866 haskell optional 
> haskell-mode_16.1.orig.tar.gz
>  800f1f6ecefe4cd24f73e68787e8e980 7068 haskell optional 
> haskell-mode_16.1-1.debian.tar.xz
>  3664c12ab0882ef4337dcfa1d05f3e0f 186822 haskell optional 
> haskell-mode_16.1-1_all.deb
>  3d5e9c5d43233f0e571e66b26efe2c59 8726 haskell optional 
> haskell-mode_16.1-1_amd64.buildinfo
>
>
>
> Thank you for your contribution to Debian.
--- End Message ---
--- Begin Message ---
Source: haskell-mode
Source-Version: 16.1-2

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated haskell-mode 
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, 25 Dec 2016 11:04:07 +
Source: haskell-mode
Binary: haskell-mode
Architecture: source all
Version: 16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Barak A. Pearlmutter 
Description:
 haskell-mode - major mode for editing Haskell in Emacs
Closes: 825485 838127 849063
Changes:
 haskell-mode (16.1-2) unstable; urgency=medium
 .
   * Remove old uploaders, add pkg-emacen team (closes: #838127, #849063)
 

Bug#849164: severity is critical

[Pedro Ribeiro]

severity 849164 critical

critical as the package cannot be installed, and after upgrading
virtualbox I cannot start previously suspended VM's

Bug#824738: marked as done (simpleparse: FTBFS: ImportError: No module named simpleparse.stt.TextTools)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 10:35:05 +
with message-id 
and subject line Bug#824738: fixed in simpleparse 2.2.0-1
has caused the Debian Bug report #824738,
regarding simpleparse: FTBFS: ImportError: No module named 
simpleparse.stt.TextTools
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.)


-- 
824738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simpleparse
Version: 2.1.0a1-7
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

simpleparse fails to build from source in unstable/amd64:

  [..]

 static void *mxDebugPrintf_used;
  ^
  stt/TextTools/mxTextTools/mxTextTools.c: In function 
'mxTextSearch_SearchBuffer':
  stt/TextTools/mxTextTools/mxTextTools.c:483:56: warning: passing argument 3 
of 'PyObject_AsCharBuffer' from incompatible pointer type 
[-Wincompatible-pointer-types]
else if (PyObject_AsCharBuffer(so->match, , _len))
  ^
  In file included from /usr/include/python2.7/Python.h:133:0,
   from stt/TextTools/mxTextTools/mx.h:60,
   from stt/TextTools/mxTextTools/mxTextTools.c:16:
  /usr/include/python2.7/abstract.h:476:22: note: expected 'Py_ssize_t * {aka 
long int *}' but argument is of type 'int *'
PyAPI_FUNC(int) PyObject_AsCharBuffer(PyObject *obj,
^
  stt/TextTools/mxTextTools/mxTextTools.c: At top level:
  stt/TextTools/mxTextTools/mxTextTools.c:2045:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (inquiry)0,/*sq_length*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2045:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_length')
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: warning: 'intargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intargfunc)0,   /*sq_repeat*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2047:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_repeat')
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: warning: 'intargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intargfunc)0,   /*sq_item*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2048:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_item')
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: warning: 'intintargfunc' is 
deprecated [-Wdeprecated-declarations]
   (intintargfunc)0,   /*sq_slice*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
  stt/TextTools/mxTextTools/mxTextTools.c:2049:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_slice')
  stt/TextTools/mxTextTools/mxTextTools.c:2050:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (intobjargproc)0,   /*sq_ass_item*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2050:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_ass_item')
  stt/TextTools/mxTextTools/mxTextTools.c:2051:5: warning: initialization from 
incompatible pointer type [-Wincompatible-pointer-types]
   (intintobjargproc)0,  /*sq_ass_slice*/
   ^
  stt/TextTools/mxTextTools/mxTextTools.c:2051:5: note: (near initialization 
for 'mxCharSet_TypeAsSequence.sq_ass_slice')
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-Istt/TextTools/mxTextTools -I/usr/include/python2.7 -c 
stt/TextTools/mxTextTools/mxte.c -o 
/home/lamby/temp/cdt.20160519114504.pfnZ1hQqMU.simpleparse/simpleparse-2.1.0a1/./build/temp.linux-x86_64-2.7/stt/TextTools/mxTextTools/mxte.o
  In file included from stt/TextTools/mxTextTools/mx.h:63:0,
   from stt/TextTools/mxTextTools/mxte.c:17:
  stt/TextTools/mxTextTools/mxstdlib.h: In function 'mxDebugPrintf':
  stt/TextTools/mxTextTools/mxstdlib.h:177:16: warning: variable 
'mxDebugPrintf_used' set but not used 

Bug#849082: marked as done (libapache2-mod-perl2: FTBFS: test failures with Apache 2.4.25)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 10:33:46 +
with message-id 
and subject line Bug#849082: fixed in libapache2-mod-perl2 2.0.10-2
has caused the Debian Bug report #849082,
regarding libapache2-mod-perl2: FTBFS: test failures with Apache 2.4.25
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.)


-- 
849082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-perl2
Version: 2.0.10-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net, this package fails its test suite
on current sid, making the package fail to build from source.

 http://ci.debian.net/packages/liba/libapache2-mod-perl2/unstable/amd64/

Reading debci.log there, the most likely candidate for triggering the
regression seems to be

  -apache2 2.4.23-8
  -apache2-bin 2.4.23-8
  -apache2-data 2.4.23-8
  -apache2-utils 2.4.23-8
  +apache2 2.4.25-1
  +apache2-bin 2.4.25-1
  +apache2-data 2.4.25-1
  +apache2-utils 2.4.25-1

but I haven't verified that.

>From my build log:

  # Failed test 1 in t/apache/read.t at line 52
  t/apache/read.t . 
  1..1
  # Running under perl version 5.024001 for linux
  # Current time local: Thu Dec 22 09:33:49 2016
  # Current time GMT:   Thu Dec 22 09:33:49 2016
  # Using Test.pm version 1.28_01
  # Using Apache/Test.pm version 1.40
  not ok 1
  Failed 1/1 subtests 
[...]
  request has failed (the response code was: 400)
  see t/logs/error_log for more details
  t/filter/in_bbs_inject_header.t . 
  # connecting to localhost:8555
  1..36
  # Running under perl version 5.024001 for linux
  # Current time local: Thu Dec 22 09:35:22 2016
  # Current time GMT:   Thu Dec 22 09:35:22 2016
  # Using Test.pm version 1.28_01
  # Using Apache/Test.pm version 1.40
  Dubious, test returned 2 (wstat 512, 0x200)
  Failed 36/36 subtests 
[...] 
  Test Summary Report
  ---
  t/apache/read.t   (Wstat: 0 Tests: 1 Failed: 1)
Failed test:  1
  t/filter/in_bbs_inject_header.t   (Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 36 tests but ran 0.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-perl2
Source-Version: 2.0.10-2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libapache2-mod-perl2 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, 25 Dec 2016 11:51:10 +0200
Source: libapache2-mod-perl2
Binary: libapache2-mod-perl2 libapache2-mod-perl2-dev libapache2-mod-perl2-doc
Architecture: source
Version: 2.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Description:
 libapache2-mod-perl2 - Integration of perl with the Apache2 web server
 libapache2-mod-perl2-dev - Integration of perl with the Apache2 web server - 
development fil
 libapache2-mod-perl2-doc - Integration of perl with the Apache2 web server - 
documentation
Closes: 849082
Changes:
 libapache2-mod-perl2 (2.0.10-2) unstable; urgency=medium
 .
   * Patch the test suite for Apache 2.4.24 compatibility.
 Thanks to Stefan Fritsch. (Closes: #849082)
Checksums-Sha1:
 d5084b2f35d7308e2227a30473f17c2ddc64b255 2668 libapache2-mod-perl2_2.0.10-2.dsc
 049c7139800c956c3fe24e92d5727bd8e4a6a42f 27024 
libapache2-mod-perl2_2.0.10-2.debian.tar.xz
Checksums-Sha256:
 504fbd0482022129f52e34a58bbd4f20215ce297a9a40650c37b77dd39502f30 2668 
libapache2-mod-perl2_2.0.10-2.dsc
 1d6cd137fe7ba16ccf7ebdb09a4f0f852463ea83e794f27dabe8bd6e9fe0a776 27024 
libapache2-mod-perl2_2.0.10-2.debian.tar.xz
Files:
 356c9b59365458cde507a7273ca150cc 2668 httpd optional 
libapache2-mod-perl2_2.0.10-2.dsc
 de902cf824474620714643e8e8b383e6 27024 httpd optional 

Bug#849315: ruby-rabl: FTBFS: Rabl::Engine without bson root #attribute asserts that it can add attribute under a different key name

[Chris Lamb]

Source: ruby-rabl
Version: 0.13.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

ruby-rabl fails to build from source in unstable/amd64:

  […]

  at «BUILDDIR»/lib/rabl/template.rb:15:in `evaluate'
  at «BUILDDIR»/lib/rabl/engine.rb:47:in `render'
  at «BUILDDIR»/lib/rabl/engine.rb:380:in `cache_results'
  at «BUILDDIR»/lib/rabl/engine.rb:48:in `block in render'
  at «BUILDDIR»/lib/rabl/engine.rb:154:in `to_bson'
  
  ERROR
   Rabl::Engine without bson root #collection asserts that it sets root node 
for objects => undefined method `serialize' for BSON:Module occured
   at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
  at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block in run'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `each'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block (2 levels) in run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in 
run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in 
run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:97:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `local_run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:109:in `block in local_run'
  at /usr/lib/ruby/vendor_ruby/riot/rr.rb:33:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/assertion.rb:51:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `evaluate'
  at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `instance_eval'
  at «BUILDDIR»/test/bson_engine_test.rb:216:in `block (4 levels) in '
  at /usr/lib/ruby/vendor_ruby/tilt/template.rb:96:in `render'
  at «BUILDDIR»/lib/rabl/template.rb:15:in `evaluate'
  at «BUILDDIR»/lib/rabl/engine.rb:47:in `render'
  at «BUILDDIR»/lib/rabl/engine.rb:380:in `cache_results'
  at «BUILDDIR»/lib/rabl/engine.rb:48:in `block in render'
  at «BUILDDIR»/lib/rabl/engine.rb:154:in `to_bson'
  
  ERROR
   Rabl::Engine without bson root #attribute asserts that it adds an attribute 
or method to be included in output => undefined method `serialize' for 
BSON:Module occured
   at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
  at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block in run'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `each'
  at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block (2 levels) in run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in 
run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in 
run_sub_contexts'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:97:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `local_run'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `each'
  at /usr/lib/ruby/vendor_ruby/riot/context.rb:109:in `block in local_run'
  at /usr/lib/ruby/vendor_ruby/riot/rr.rb:33:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/assertion.rb:51:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `evaluate'
  at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `instance_eval'
  at «BUILDDIR»/test/bson_engine_test.rb:228:in `block (4 levels) in '
  at /usr/lib/ruby/vendor_ruby/tilt/template.rb:96:in `render'
  at «BUILDDIR»/lib/rabl/template.rb:15:in `evaluate'
  at «BUILDDIR»/lib/rabl/engine.rb:47:in `render'
  at «BUILDDIR»/lib/rabl/engine.rb:380:in `cache_results'
  at «BUILDDIR»/lib/rabl/engine.rb:48:in `block in render'
  at «BUILDDIR»/lib/rabl/engine.rb:154:in `to_bson'
  
  ERROR
   Rabl::Engine without bson root #attribute asserts that it can add attribute 
under a different key name through :as => undefined method `serialize' for 
BSON:Module occured
   at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
  at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
  at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
  at 

Processed: Bug#824738 marked as pending

[Debian Bug Tracking System]

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

> tag 824738 pending
Bug #824738 [src:simpleparse] simpleparse: FTBFS: ImportError: No module named 
simpleparse.stt.TextTools
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824738: marked as pending

[Vincent Bernat]

tag 824738 pending
thanks

Hello,

Bug #824738 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/simpleparse.git;a=commitdiff;h=087e956

---
commit 087e956bbdb6bda9de89037998bcbca3bfc7e238
Author: Vincent Bernat 
Date:   Sun Dec 25 10:49:00 2016 +0100

Switch to pybuild

diff --git a/debian/changelog b/debian/changelog
index 459e56d..5299080 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,6 +6,8 @@ simpleparse (2.2.0-1) unstable; urgency=medium
   [ Vincent Bernat ]
   * New upstream release.
 - drop "with"-keyword patch
+- fix FTBFS (Closes: #824738)
+  * Switch to pybuild.
 
  -- Vincent Bernat   Sun, 25 Dec 2016 10:39:11 +0100
 

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Ole Streicher]

I'll upload to DELAYED ASAP (need to learn how to do this anyway);
however the unresolved problem is still the pandas FTBFS. Without that,
statsmodels will not migrate.

Cheers

Ole

On 25.12.2016 08:34, Andreas Tille wrote:
> Hi Ole,
> 
>> the attached patch fixes the FTBFS. What is the schedule to fix the
>> other problems with statsimage -- especially pandas?
> 
> I learned that NeuroDebian is happy about team uploads / NMUs - so
> I think its fine if you upload your patch.
> 
> Kind regards
> 
> Andreas.
> 
> PS: If you are not convinced and there is no response from Yaroslav or
> Michael in the next 24 hours - well, people are occupied by real life
> these days, yust tell me and I'd upload.
> 

Bug#811986: marked as done (qwtplot3d: FTBFS with GCC 6: symbol changes)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 09:34:51 +
with message-id 
and subject line Bug#811986: fixed in qwtplot3d 0.2.7+svn191-10.1
has caused the Debian Bug report #811986,
regarding qwtplot3d: FTBFS with GCC 6: symbol changes
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.)


-- 
811986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qwtplot3d
Version: 0.2.7+svn191-9
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-symbols

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libqwtplot3d-qt4-0v5/DEBIAN/symbols doesn't 
> match completely debian/libqwtplot3d-qt4-0v5.symbols
> --- debian/libqwtplot3d-qt4-0v5.symbols 
> (libqwtplot3d-qt4-0v5_0.2.7+svn191-9_amd64)
> +++ dpkg-gensymbolsFodDeO 2016-01-19 23:39:20.896195539 +
> @@ -242,10 +242,10 @@
>   _ZN5Qwt3D4Axis9setMajorsEi@Base 0.2.7
>   _ZN5Qwt3D4Axis9setMinorsEi@Base 0.2.7
>   _ZN5Qwt3D4AxisC1ENS_6TripleES1_@Base 0.2.7
> - _ZN5Qwt3D4AxisC1ERKS0_@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# _ZN5Qwt3D4AxisC1ERKS0_@Base 0.2.7
>   _ZN5Qwt3D4AxisC1Ev@Base 0.2.7
>   _ZN5Qwt3D4AxisC2ENS_6TripleES1_@Base 0.2.7
> - _ZN5Qwt3D4AxisC2ERKS0_@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# _ZN5Qwt3D4AxisC2ERKS0_@Base 0.2.7
>   _ZN5Qwt3D4AxisC2Ev@Base 0.2.7
>   _ZN5Qwt3D4AxisD0Ev@Base 0.2.7
>   _ZN5Qwt3D4AxisD1Ev@Base 0.2.7
> @@ -267,7 +267,7 @@
>   _ZN5Qwt3D5ArrowD0Ev@Base 0.2.7
>   _ZN5Qwt3D5ArrowD1Ev@Base 0.2.7
>   _ZN5Qwt3D5ArrowD2Ev@Base 0.2.7
> - _ZN5Qwt3D5Color12createVectorERSt6vectorINS_4RGBAESaIS2_EE@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> _ZN5Qwt3D5Color12createVectorERSt6vectorINS_4RGBAESaIS2_EE@Base 0.2.7
>   _ZN5Qwt3D5GL2QtEddd@Base 0.2.7
>   _ZN5Qwt3D5Label11setPositionENS_6TripleENS_6ANCHORE@Base 0.2.7
>   _ZN5Qwt3D5Label12devicefonts_E@Base 0.2.7
> @@ -379,9 +379,9 @@
>   _ZN5Qwt3D6Plot3DD0Ev@Base 0.2.7
>   _ZN5Qwt3D6Plot3DD1Ev@Base 0.2.7
>   _ZN5Qwt3D6Plot3DD2Ev@Base 0.2.7
> - _ZN5Qwt3D7MappingD0Ev@Base 0.2.7
> - _ZN5Qwt3D7MappingD1Ev@Base 0.2.7
> - _ZN5Qwt3D7MappingD2Ev@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# _ZN5Qwt3D7MappingD0Ev@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# _ZN5Qwt3D7MappingD1Ev@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# _ZN5Qwt3D7MappingD2Ev@Base 0.2.7
>   _ZN5Qwt3D8CellData5clearEv@Base 0.2.7
>   _ZN5Qwt3D8CellDataD0Ev@Base 0.2.7
>   _ZN5Qwt3D8CellDataD1Ev@Base 0.2.7
> @@ -473,33 +473,40 @@
>   _ZNK5Qwt3D8LogScale5cloneEv@Base 0.2.7
>   _ZNK5Qwt3D8LogScale8ticLabelEj@Base 0.2.7
>   _ZNK5Qwt3D9CrossHair5cloneEv@Base 0.2.7
> - 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base
>  0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS2_S4_EERKS2_@Base
>  0.2.7
> + 
> _ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EE19_M_emplace_back_auxIJRKS2_EEEvDpOT_@Base
>  0.2.7+svn191-9
>   (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EED1Ev@Base 0.2.7
>   (optional=templinst)_ZNSt6vectorIN5Qwt3D2IO5EntryESaIS2_EED2Ev@Base 0.2.7
> - (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED1Ev@Base 0.2.7
> - (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED2Ev@Base 0.2.7
> - (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EEaSERKS3_@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED1Ev@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EED2Ev@Base 0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D4AxisESaIS1_EEaSERKS3_@Base 0.2.7
>   (optional=templinst)_ZNSt6vectorIN5Qwt3D4RGBAESaIS1_EEaSERKS3_@Base 0.2.7
> - 
> (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS1_S3_EEmRKS1_@Base
>  0.2.7
> +#MISSING: 0.2.7+svn191-9# 
> 

Bug#811986: qwtplot3d: diff for NMU version 0.2.7+svn191-10.1

[Arto Jantunen]

Graham Inggs  writes:

> Hi Arto
>
> On 23 December 2016 at 14:59, Arto Jantunen  wrote:
>> I've prepared an NMU for qwtplot3d (versioned as 0.2.7+svn191-10.1) and
>> uploaded it to DELAYED/5. Please feel free to tell me if I
>> should delay it longer.
>
> Thanks for the upload.  I'm not the maintainer, but I suggest you
> remove the delay otherwise qwtplot3d won't migrate to testing before
> the freeze.
>
> BTW, the bug was RC and there had been no maintainer activity for more
> than 7 days, so I think a DELAYED/0 would have been appropriate.

Indeed you are right, I misjudged my timing. I have rescheduled this
upload to go through now.

The point of course was to get this package (and goldencheetah) into
stretch. Thanks for the heads up.

-- 
Arto Jantunen

Bug#849277: marked as done (A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading)

[Debian Bug Tracking System]

Your message dated Sun, 25 Dec 2016 09:03:26 +
with message-id 
and subject line Bug#849277: fixed in bbdb3 3.1.2-7
has caused the Debian Bug report #849277,
regarding A typo, "flavor", which evaluates to nothing, prevents bbdb3 from 
loading
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.)


-- 
849277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-Cc: wink...@gnu.org
Package: bbdb3
Version: 3.1.2-6
Severity: grave
File: /etc/emacs/site-start.d/50bbdb3.el

A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading.

--- 50bbdb3.el  2016-07-21 15:21:11.0 +0800
+++ 50bbdb3.NEW.el  2016-12-24 21:07:24.969515584 +0800
@@ -14,7 +14,7 @@
 ;; installed in a subdirectory of the respective site-lisp directory.
 ;; We have to add this to the load-path:
 (let ((package-dir (concat "/usr/share/"
-  (symbol-name flavor)
+  "emacs"
   "/site-lisp/bbdb3")))
   ;; If package-dir does not exist the bbdb3 package must have been
   ;; removed but not purged, and we should skip the setup.
--- End Message ---
--- Begin Message ---
Source: bbdb3
Source-Version: 3.1.2-7

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated bbdb3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Dec 2016 18:54:45 +
Source: bbdb3
Binary: bbdb3
Architecture: source all
Version: 3.1.2-7
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 bbdb3  - Reboot of the BBDB Insidious Big Brother Database for Emacs
Closes: 849277
Changes:
 bbdb3 (3.1.2-7) unstable; urgency=medium
 .
   * switch from flavor to debian-emacs-flavor (closes: #849277)
Checksums-Sha1:
 7d599ae8553cf6e0d4a014651f415e0bee87fdb8 1933 bbdb3_3.1.2-7.dsc
 c8bb4d7552346fb0ec7b079c6f3c06a1c3c6c699 41472 bbdb3_3.1.2-7.debian.tar.xz
 8dcad51e2ad45508015288e06905df7dc72c77db 135224 bbdb3_3.1.2-7_all.deb
 c56d3518eeb3f766c737990180cbea41cb01a02a 9588 bbdb3_3.1.2-7_amd64.buildinfo
Checksums-Sha256:
 6f8eb65a9c12b9831c7974c196c222b907c1e793e9ed9491e71cd00dd95ae474 1933 
bbdb3_3.1.2-7.dsc
 cba902f9d8fa3a9f13a16aa58a927a325010a1d3098ee19e6d4fe0a68b4ef06b 41472 
bbdb3_3.1.2-7.debian.tar.xz
 5f7376f7e6003118d68e90c0c31c1a6c004c071ebc05ce8da77be59f3b37 135224 
bbdb3_3.1.2-7_all.deb
 60b57d0c0f0209e981eac52d2ad40e662d5ee7a4bc3e7e303f83c9d9cfc5552d 9588 
bbdb3_3.1.2-7_amd64.buildinfo
Files:
 df9bf0aee5424148646cd68ab06667d3 1933 mail optional bbdb3_3.1.2-7.dsc
 4514cce96bee2b551ec28f91a4e56ce5 41472 mail optional 
bbdb3_3.1.2-7.debian.tar.xz
 81e2c0be47a9bc191892671d6e2a1a12 135224 mail optional bbdb3_3.1.2-7_all.deb
 d7fcdc1918d24a28f7e36ddb42c6f773 9588 mail optional 
bbdb3_3.1.2-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAlhfdsMACgkQEltXR14Z
DRgVZg//X50LLfFkp1kAlURxNUg49gqy0NFxdV0u9VBsqpwPycpcv9GDWT+X7kyZ
5kRR+SfYWLvaArfF7d7rgHupe6HXuqhhQ68Ixh51ij3ft8ayk7Q93FNSPtI7Kxfq
mi9YZeFpLITJBcl/uLGzbjFB8shslFFwAxOAShfLa9+dYMuTK27FfAs0qsWTwTSK
HJLW9j+TBT0Ks1kx1qAkZZHqN9PcrMvim/yZrvNQjhn93inxDnABOeAZox2RM6Iv
U2iV8tTQ3iDdhpgb45MxDN7WnI33y3X694bl2z9Eq04olk0pZgIv8M0ubQU6HLVE
Ed7S4A5GdNzJ5YwRu3kF8h9wdNCKDS813w1TrveSTJoNwRTvknuUComp2vr0UMnE
DhegbplK6opJl5NLznsUAFcNLCx60LW5Wl2zIQykCLkSu9OTpxnlXf9CeeSdri3X
wtqYAG5JEfZ6yR+1LyY0MKjK8KpFP0KizzrIcVDKK93bx6SqMIDnp+odtzDCVC7G
i3dIZCI9k/LQAHi/GXpBVeacq2P3LUTQU4rB3YdfF34qXj3FOJqaz4wWtFLrmWf+
jBjS3EpBa6OdgIWK4Y+dIbjyJ+l8DYzDb11tFUI8iTDM88g40ca4uurd+epqOY43
WLenLpqlyMdwBtOGK93xuaSEUEknvLxFB4DnOVc0AraP+xIUW8A=
=3ZbQ
-END PGP SIGNATURE End Message ---

Bug#811986: qwtplot3d: diff for NMU version 0.2.7+svn191-10.1

[Graham Inggs]

Hi Arto

On 23 December 2016 at 14:59, Arto Jantunen  wrote:
> I've prepared an NMU for qwtplot3d (versioned as 0.2.7+svn191-10.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Thanks for the upload.  I'm not the maintainer, but I suggest you
remove the delay otherwise qwtplot3d won't migrate to testing before
the freeze.

BTW, the bug was RC and there had been no maintainer activity for more
than 7 days, so I think a DELAYED/0 would have been appropriate.

Regards
Graham