Bug#867418: marked as pending

[Scott Kitterman]

tag 867418 pending
thanks

Hello,

Bug #867418 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:


https://anonscm.debian.org/cgit/python-modules/packages/python-arpy.git/commit/?id=f813608

---
commit f813608c5df290d5e107e21eb261cd42cc34f8d3
Author: Scott Kitterman 
Date:   Sun Jul 9 01:20:16 2017 -0400

Correct substitution variable for python3 interpreter depends (Closes: 
#867418)

diff --git a/debian/changelog b/debian/changelog
index 34b70ef..9668fa9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,7 +8,11 @@ python-arpy (1.1.1-3) UNRELEASED; urgency=low
   * Fixed homepage (https)
   * Fixed VCS URL (https)
 
- -- Christoph Egger   Sat, 06 Jul 2013 15:02:46 +0200
+  [ Scott Kitterman ]
+  * Correct substitution variable for python3 interpreter depends (Closes:
+#867418)
+
+ -- Scott Kitterman   Sun, 09 Jul 2017 01:18:49 -0400
 
 python-arpy (1.1.1-2) unstable; urgency=low
 

Processed: Bug#867418 marked as pending

[Debian Bug Tracking System]

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

> tag 867418 pending
Bug #867418 [python3-arpy] python3-arpy: missing python3 dependency
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867738: devscripts: debpatch.1.gz conflicts with debdelta's debpatch.1.gz

[Nelson A. de Oliveira]

Source: devscripts
Version: 2.17.7
Severity: serious
Justification: Policy 7.4

Hi!

While upgrading devscripts from 2.17.6 to 2.17.7:

=
Unpacking devscripts (2.17.7) over (2.17.6) ...
dpkg: error processing archive 
/var/cache/apt/archives/devscripts_2.17.7_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/debpatch.1.gz', which is also in 
package debdelta 0.59
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/devscripts_2.17.7_amd64.deb
=

Thank you!

Best regards,
Nelson

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

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

-- debconf-show failed

Bug#867737: Do not use this package. It will lock your screen.

[積丹尼 Dan Jacobson]

Package: arora
Version: 0.11.0+qt5+git2014-04-06-1
Severity: grave

All I did was
$ arora
then after it finished rendering its initial screen,
I hit CTRL+Q and CTRL+W or maybe the other way around.

Next thing you know my entire screen was locked up.
The clock in the corner of icewm stopped.
I couldn't even do ALT+CTRL+F1 to leave X-windows.

I had to hit the power button on the front of my computer.
My disks needed to be fscked. My bash history got lost.
Who knows what else I lost.

Bug#867736: [fbpanel] fbpanel crashes with default config

[Will Brokenbourgh]

Package: fbpanel
Version: 7.0-3
Severity: serious

When fbpanel is run with the default config file 
(/usr/share/fbpanel/default) it crashes without displaying any GUI.


The crash output from the terminal follows:
- - -
*** Error in `fbpanel': double free or corruption (out): 
0x558a947cda10 ***

=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f4d4469bbcb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f4d446a1f96]
/lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7f4d446a27de]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7f4d44f38699]
fbpanel(get_utf8_property_list+0x141)[0x558a94308e71]
/usr/lib/fbpanel/libtaskbar.so(+0x453c)[0x7f4d3da7f53c]
/usr/lib/fbpanel/libtaskbar.so(taskbar_constructor+0x4c0)[0x7f4d3da812f0]
fbpanel(plugin_start+0xd8)[0x558a9430aee8]
fbpanel(main+0xdbe)[0x558a943041ce]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f4d4464b2b1]
fbpanel(_start+0x2a)[0x558a9430468a]
=== Memory map: 
558a942fb000-558a9431 r-xp  08:24 1194991
/usr/bin/fbpanel
558a9450f000-558a9451 r--p 00014000 08:24 1194991
/usr/bin/fbpanel
558a9451-558a94511000 rw-p 00015000 08:24 1194991
/usr/bin/fbpanel
558a94726000-558a9488d000 rw-p  00:00 0  
[heap]

7f4d3000-7f4d30022000 rw-p  00:00 0
7f4d30022000-7f4d3400 ---p  00:00 0
7f4d3400-7f4d34021000 rw-p  00:00 0
7f4d34021000-7f4d3800 ---p  00:00 0
7f4d3800-7f4d38021000 rw-p  00:00 0
7f4d38021000-7f4d3c00 ---p  00:00 0
7f4d3d643000-7f4d3d659000 r-xp  08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d659000-7f4d3d858000 ---p 00016000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d858000-7f4d3d859000 r--p 00015000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d859000-7f4d3d85a000 rw-p 00016000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d873000-7f4d3d879000 r-xp  08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3d879000-7f4d3da78000 ---p 6000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da78000-7f4d3da79000 r--p 5000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da79000-7f4d3da7a000 rw-p 6000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da7b000-7f4d3da83000 r-xp  08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3da83000-7f4d3dc82000 ---p 8000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc82000-7f4d3dc83000 r--p 7000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc83000-7f4d3dc84000 rw-p 8000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc8b000-7f4d3dc8d000 r-xp  08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3dc8d000-7f4d3de8c000 ---p 2000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3de8c000-7f4d3de8d000 r--p 1000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3de8d000-7f4d3de8e000 rw-p 2000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so

7f4d3de91000-7f4d3de92000 ---p  00:00 0
7f4d3de92000-7f4d3e692000 rw-p  00:00 0
7f4d3e692000-7f4d3e693000 ---p  00:00 0
7f4d3e693000-7f4d3ee93000 rw-p  00:00 0
7f4d3ee93000-7f4d3ee95000 r-xp  08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3ee95000-7f4d3f094000 ---p 2000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f094000-7f4d3f095000 r--p 1000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f095000-7f4d3f096000 rw-p 2000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f0b3000-7f4d3f0e9000 r-xp  08:24 1317789 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
7f4d3f0e9000-7f4d3f2e9000 ---p 00036000 08:24 1317789 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
7f4d3f2e9000-7f4d3f2ef000 r--p 00036000 08:24 1317789 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
7f4d3f2ef000-7f4d3f2f rw-p 0003c000 08:24 1317789 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
7f4d3f2f3000-7f4d3f322000 r-xp  08:24 1317798 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
7f4d3f322000-7f4d3f522000 ---p 0002f000 08:24 1317798 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
7f4d3f522000-7f4d3f524000 r--p 0002f000 08:24 1317798 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
7f4d3f524000-7f4d3f525000 rw-p 00031000 08:24 1317798 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
7f4d3f52b000-7f4d3f547000 r--p  08:24 1316774

Bug#867730: dummydroid: unusable due to authentication failure

[Phil Morrell]

Package: dummydroid
Version: 1.1-1
Severity: grave
Justification: renders package unusable

I am attempting to use gplaycli on stretch, for which I need a google play
device id.

After the Credentials step, no matter how I setup the google account, I always
get an error displayed on the Profile Upload step:

com.akdeniz.googleplaycrawler.GooglePlayException: Error=BadAuthentication

Google Auth methods tried:
* custom domain, two-factor
* custom domain, password only
* registered dummydro...@gmail.com

Steps to reproduce:
1) register account at https://accounts.google.com/SignUp
2) sign in at https://play.google.com/store
3) launch dummydroid
4) open Google_Nexus_6.prop (or Azpen_A727.prop)
5) click next through to Credentials
6) enter details registered and click next

I can't find a manpage or guess any flags to enter debug mode, so there is no
extra detail on stdout - please let me know if there's a way to test this, or
if you're unable to reproduce the error.

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

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

Versions of packages dummydroid depends on:
ii  default-jre [java8-runtime]2:1.8-58
ii  jarwrapper 0.59
ii  libhttpclient-java 4.5.2-2
ii  libhttpcore-java   4.4.6-1
ii  openjdk-8-jre [java8-runtime]  8u131-b11-2

dummydroid recommends no packages.

dummydroid suggests no packages.

-- no debconf information

Processed: 859155 is pending, fixed-upstream

[Debian Bug Tracking System]

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

> tags 859155 pending fixed-upstream
Bug #859155 [openafs-modules-dkms] openafs-modules-dkms: Please support kernel 
4.11
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867670: marked as done (libpng1.6 FTBFS on arm* building arm/filter_neon.S)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 23:19:15 +
with message-id 
and subject line Bug#867670: fixed in libpng1.6 1.6.30-2
has caused the Debian Bug report #867670,
regarding libpng1.6 FTBFS on arm* building arm/filter_neon.S
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.)


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

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

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c arm/filter_neon.S  
-fPIC -DPIC -o arm/.libs/filter_neon.o
arm/../pngpriv.h: Assembler messages:
arm/../pngpriv.h:476: Error: unknown mnemonic `typedef' -- `typedef unsigned 
long png_ptruint'
Makefile:1156: recipe for target 'arm/filter_neon.lo' failed
make[2]: *** [arm/filter_neon.lo] Error 1
...

None of our ARM ports includes NEON in the architecture baseline.
--- End Message ---
--- Begin Message ---
Source: libpng1.6
Source-Version: 1.6.30-2

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated libpng1.6 
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, 09 Jul 2017 01:02:17 +0200
Source: libpng1.6
Binary: libpng16-16 libpng-dev libpng-tools libpng16-16-udeb
Architecture: source
Version: 1.6.30-2
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Gianfranco Costamagna 
Description:
 libpng-dev - PNG library - development (version 1.6)
 libpng-tools - PNG library - tools (version 1.6)
 libpng16-16 - PNG library - runtime (version 1.6)
 libpng16-16-udeb - PNG library - minimal runtime library (version 1.6) (udeb)
Closes: 867670
Changes:
 libpng1.6 (1.6.30-2) unstable; urgency=medium
 .
   * Fix arm* build failures with upstream patch
 (Closes: #867670)
Checksums-Sha1:
 9e6010980d1b64f3c22fcbbbd7b5d13a28856574 2188 libpng1.6_1.6.30-2.dsc
 0bbe61e858c47e38cb331d743acf8dbd68dae1f5 22844 libpng1.6_1.6.30-2.debian.tar.xz
Checksums-Sha256:
 6f778d2e59fc66aaca420c2b68b49267c79255fc3c701ff527e3f3ce98526b5d 2188 
libpng1.6_1.6.30-2.dsc
 8daa2a3bcd3cc5300d0afe86ca95feffd266dc80c41d252f2c651973198e319f 22844 
libpng1.6_1.6.30-2.debian.tar.xz
Files:
 bbcb30c820bc3aaf6720d5e280d1ce35 2188 libs optional libpng1.6_1.6.30-2.dsc
 0d21e4eb5f9d61b4d53a51e109021bbd 22844 libs optional 
libpng1.6_1.6.30-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZYWV8AAoJEPNPCXROn13ZAeYP/jlW5vvwpaJWqe4evTCy7+24
SnO0HDYZCmiTyNsmbJAyvRaKYIOLnYhfKy6Oo1STlSLoeHgbjv3eVXYn8Wkfgh5d
k23RO0qSiQ6PJgCJqfapsSZg9/UYJVHdwup9yi4D+F3wBPnJ0pI9CyWTG63EN5cY
HVr5f9wVbhprQSon4HrkeK9FzeoTZbXfU4lqSLMt5jmHiBaYJoXFKXwmkrQMAR/o
5aXWM9E9SdTvqWNcqhVp7KSRuFr08wm53uzsOCxOIKEKKd1pShwTsD9Im/76N+XZ
UnVpAAOaaTDfiuTNWkfyvv/ZPCkZWbPCmWL9/czWC5OOF4IFjZCI2E75UAkWcTUD
hlMkOyaWtaorndXhIW8OFuz56FsdKootNL8fwB/2FzLx/KYPLbTNkexWYbXUAzZ+
uAthk6YkSOHnbVwuxbmseBWB4qRGDN6ivP//gWZaABC44pqALehkCRoiIbZUDOkm
PY0jSM8UQat24m3VCtSHHzgvfT3VE64rq9ml6TwiHevun+HNlGpYZMxnUwy32cZ5
T12G5TykCyGOI8ohE0o0pbDy0JPZbinHROTqX4YpDpPPzwxkSPIGdgrgUxs4jYQc
JVs4sH7ap/8bYssOYEN/AOT51BG7vZysMIBMEshARwbq1NOiLEpjxzYlwVRE3eVA
LzGHSDaGiD0vBjs7T08+
=P4eS
-END PGP SIGNATURE End Message ---

Bug#867725: CVE-2017-9869 CVE-2017-9870 CVE-2017-9871 CVE-2017-9872

[Moritz Muehlenhoff]

Source: lame
Severity: grave
Tags: security

Hi,
please see:

CVE-2017-9869:
https://blogs.gentoo.org/ago/2017/06/17/lame-global-buffer-overflow-in-ii_step_one-layer2-c/

CVE-2017-9870:
https://blogs.gentoo.org/ago/2017/06/17/lame-global-buffer-overflow-in-iii_i_stereo-layer3-c/
  
CVE-2017-9871:
https://blogs.gentoo.org/ago/2017/06/17/lame-stack-based-buffer-overflow-in-iii_i_stereo-layer3-c/

CVE-2017-9872:
https://blogs.gentoo.org/ago/2017/06/17/lame-stack-based-buffer-overflow-in-iii_dequantize_sample-layer3-c/

Cheers,
Moritz

 

Bug#865863: marked as done (dgit 3.10 and earlier not compatible with git 2.12-ish)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#865863: fixed in dgit 3.11
has caused the Debian Bug report #865863,
regarding dgit 3.10 and earlier not compatible with git 2.12-ish
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.)


-- 
865863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: dgit
version: 3.10

dgit problem:

% dgit -D clone network-manager-strongswan sid
fatal: BUG: setup_git_env called without repository
dgit: failed command: git config -z --get-regexp --local '.*'
dgit: subprocess failed with error exit status 128

Output of "printenv | sort" is attached.


Regards
Harri
CCACHE_DIR=/var/tmp/.ccache
CCACHE_HARDLINKS=1
CCACHE_TEMPDIR=/var/tmp/.ccache
CCACHE_UMASK=0
CHROMIUM_FLAGS=--ssl-version-min=tls1 
--cipher-suite-blacklist=0xc007,0xc011,0x0005,0x0004
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-6D94iG3gEN,guid=04875397619c644082d8d560594f375b
DEBEMAIL=ha...@afaics.de
DEBFULLNAME=Harald Dunkel
DEBKEY=1F657AD782DB47FBB53BE6B50A9E2A9E66D381CB
DEBSIGN_KEYID=1F657AD782DB47FBB53BE6B50A9E2A9E66D381CB
DEB_SIGN_KEYID=1F657AD782DB47FBB53BE6B50A9E2A9E66D381CB
DISPLAY=:4
DOMAINNAME=afaics.de
EDITOR=/usr/bin/emacs
EMACS=/usr/bin/emacs
EMAIL=ha...@afaics.de
FVWM_DATADIR=/usr/share/fvwm
FVWM_MODULEDIR=/usr/lib/fvwm/2.6.7
FVWM_USERDIR=/home/harri/.fvwm
GDK_CORE_DEVICE_EVENTS=1
GPGKEY=1F657AD782DB47FBB53BE6B50A9E2A9E66D381CB
GPG_TTY=/dev/pts/5
HOME=/home/harri
HOSTDISPLAY=cecil.afaics.de:4
HUSHLOGIN=TRUE
INITRD_OK=true
KEMAIL=ha...@afaics.de
LANG=C
LC_ALL=C
LESS=-iMXRS
LESSCHARSET=iso8859
LESSCLOSE=/usr/bin/lesspipe %s %s
LESSOPEN=| /usr/bin/lesspipe %s
LOGNAME=harri
MAIL=/var/mail/harri
MAILHOST=tweety
MANPATH=/home/harri/man:/usr/share/man
OLDPWD=/home/harri
ORIGPATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PAGER=/usr/bin/less
PATH=/home/harri/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PILOTPORT=usb:
PRINTER=lp
PWD=/tmp
QUILT_PATCHES=debian/patches
QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
QUOTING_STYLE=literal
RSYNC_RSH=ssh -S none -x
SHELL=/bin/bash
SHLVL=4
SIGNCHANGES=true
SSH_AGENT_PID=2135
SSH_AUTH_SOCK=/tmp/ssh-LT5dDN4iFldX/agent.2133
S_COLORS=auto
TAPE=/dev/null
TERM=xterm
USER=harri
VIRSH_DEFAULT_CONNECT_URI=qemu:///system
VISUAL=/usr/bin/emacs
WINDOWID=41943076
WINDOWPATH=2
WINEDITOR=/usr/bin/emacs
XAUTHORITY=/home/harri/.Xauthority
XDG_CACHE_HOME=/tmp/harri/.cache
XDG_CURRENT_DESKTOP=GNOME
XRSH_RSH=ssh
XTERM_LOCALE=C
XTERM_SHELL=/bin/bash
XTERM_VERSION=XTerm(330)
_=/usr/bin/printenv


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.11

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 08 Jul 2017 22:40:15 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: source all
Version: 3.11
Distribution: unstable
Urgency: high
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Closes: 857694 858054 865863 867185 867189 867309 867434 867603 867693
Changes:
 dgit (3.11) unstable; urgency=high
 .
   Important bugfixes to dgit:
   * Fix rpush+buildinfo: Transfer buildinfos for signing.  Closes:#867693.
   * Cope if the archive server sends an HTTP redirect,
 by passing -L to curl.  Closes:#867185,#867309.
   * Cope with newer git which hates --local outside a tree.  Closes:#865863.
   * rpush: Honour local git config from build host working tree.
   * Tolerate compressor terminating with SIGPIPE.  

Bug#867185: marked as done (dgit: Perl error trying to clone Gtk+)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#867309: fixed in dgit 3.11
has caused the Debian Bug report #867309,
regarding dgit: Perl error trying to clone Gtk+
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.)


-- 
867309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 3.10
Severity: normal

The transcript below demonstrates the problem.  I get the same failure on
chiark (jessie), with a clean environment and bogus $HOME (to eliminate my
dotfiles).

[stratocaster /tmp/mdw]dgit clone gtk+3.0
canonical suite name for unstable is sid
starting new git history
downloading 
http://ftp.debian.org/debian//pool/main/g/gtk+3.0/gtk+3.0_3.22.16-1.dsc...
last upload to archive: NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   386  100   3860 0   8327  0 --:--:-- --:--:-- --:--:--  8391
Use of uninitialized value $got in concatenation (.) or string at /usr/bin/dgit 
line 2545.
[stratocaster /tmp/mdw rc=255]

This appears to mean that $checkhash->() failed and it was trying to report
this; I don't know what might have caused that or what I might be able to do
about it.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)
Foreign Architectures: amd64

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput  0.12.1
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.12.2
ii  git-core  1:2.11.0-3
ii  libdigest-sha-perl5.96-1+b1
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3
ii  realpath  8.26-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
pn  sbuild  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.11

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 08 Jul 2017 22:40:15 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: source all
Version: 3.11
Distribution: unstable
Urgency: high
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Closes: 857694 858054 865863 867185 867189 867309 867434 867603 867693
Changes:
 dgit (3.11) unstable; urgency=high
 .
   Important bugfixes to dgit:
   * Fix rpush+buildinfo: Transfer buildinfos for signing.  Closes:#867693.
   * Cope if the archive server sends an HTTP redirect,
 by passing -L to curl.  Closes:#867185,#867309.
   * Cope with newer git which hates --local outside a tree.  Closes:#865863.
   * 

Bug#867309: marked as done (dgit: Use of uninitialized value $got in concatenation)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#867309: fixed in dgit 3.11
has caused the Debian Bug report #867309,
regarding dgit: Use of uninitialized value $got in concatenation
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.)


-- 
867309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 4.0
Severity: normal

Steps to reproduce:

$ dgit clone janus
canonical suite name for unstable is sid
starting new git history
downloading http://ftp.debian.org/debian//pool/main/j/janus/janus_0.2.3-1.dsc...
last upload to archive: NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   380  100   3800 0   2085  0 --:--:-- --:--:-- --:--:--  2087
Use of uninitialized value $got in concatenation (.) or string at /usr/bin/dgit 
line 2545.


Thanks!

cheers, josch


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

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput  0.12.1
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.12.2
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
ii  sbuild  0.73.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.11

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 08 Jul 2017 22:40:15 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: source all
Version: 3.11
Distribution: unstable
Urgency: high
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Closes: 857694 858054 865863 867185 867189 867309 867434 867603 867693
Changes:
 dgit (3.11) unstable; urgency=high
 .
   Important bugfixes to dgit:
   * Fix rpush+buildinfo: Transfer buildinfos for signing.  Closes:#867693.
   * Cope if the archive server sends an HTTP redirect,
 by passing -L to curl.  Closes:#867185,#867309.
   * Cope with newer git which hates --local outside a tree.  Closes:#865863.
   * rpush: Honour local git config from build host working tree.
   * Tolerate compressor terminating with SIGPIPE.  Closes:#857694.
   * Honour more pre-tree git config options in our private trees sharing
 the user's object store.  In particular, core.sharedRepository.
 Prompted by #867603.
   * Clone multisuite works even without --no-rm-on-error.  Closes:#867434.
   

Bug#867723: ejabberd: `dpkg-reconfigure ejabberd` fails with `Can't register admin user`

[Soren Stoutner]

Package: ejabberd
Version: 17.04-1~exp2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After performing a new ejabberd install on Debian testing, running 
`dpkg-reconfigure ejabberd` produces the folling error:


root@mail:/home/soren# dpkg-reconfigure ejabberd

The ejabberd database has been backed up to 
/var/backups/ejabberd-2017-07-08T14:08:25.vzaIOQ/ejabberd-database.

Replacing config file /etc/ejabberd/ejabberd.yml with new version
Waiting for ejabberd to register admin user
Can't register admin user "so...@ejabberd.stoutner.com".


A 1.5 MB `erl_crash.dump` file is created in `/var/log/ejabberd`.  I can upload 
the file to a webserver and link to it if it is valuable for troubleshooting.

I initially enountered this error with the 16.09-4 package in testing.  
Upgrading to the 17.04-1~exp2 package in experimental produces the same result.

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

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

Versions of packages ejabberd depends on:
ii  adduser3.115
ii  debconf1.5.62
ii  erlang-asn11:20.0+dfsg-2
ii  erlang-base [erlang-abi-17.0]  1:20.0+dfsg-2
ii  erlang-crypto  1:20.0+dfsg-2
ii  erlang-inets   1:20.0+dfsg-2
ii  erlang-jiffy   0.14.8+dfsg-1
ii  erlang-lager   3.2.4-1
ii  erlang-mnesia  1:20.0+dfsg-2
ii  erlang-odbc1:20.0+dfsg-2
ii  erlang-p1-cache-tab1.0.7-1~exp1
ii  erlang-p1-iconv1.0.4-1~exp1
ii  erlang-p1-stringprep   1.0.8-1~exp1
ii  erlang-p1-tls  1.0.11-1~exp1
ii  erlang-p1-utils1.0.8-1~exp2
ii  erlang-p1-xml  1.1.22-1~exp1
ii  erlang-p1-xmpp 1.1.9-1~exp1
ii  erlang-p1-yaml 1.0.9-1~exp1
ii  erlang-p1-zlib 1.0.2-1~exp1
ii  erlang-ssl 1:20.0+dfsg-2
ii  erlang-syntax-tools1:20.0+dfsg-2
ii  erlang-xmerl   1:20.0+dfsg-2
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  openssl1.1.0f-3
ii  ucf3.0036

ejabberd recommends no packages.

Versions of packages ejabberd suggests:
pn  apparmor 
pn  apparmor-utils   
pn  ejabberd-contrib 
pn  erlang-luerl 
ii  erlang-p1-mysql  1.0.1-4
pn  erlang-p1-oauth2 
pn  erlang-p1-pam
pn  erlang-p1-pgsql  
pn  erlang-p1-sip
pn  erlang-p1-sqlite3
pn  erlang-p1-stun   
pn  erlang-redis-client  
ii  imagemagick  8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11
pn  libunix-syslog-perl  
pn  yamllint 

-- Configuration Files:
/etc/ejabberd/inetrc [Errno 13] Permission denied: '/etc/ejabberd/inetrc'
/etc/ejabberd/modules.d/README.modules [Errno 13] Permission denied: 
'/etc/ejabberd/modules.d/README.modules'

-- debconf information:
* ejabberd/hostname: ejabberd.stoutner.com
* ejabberd/user: soren
  ejabberd/nomatch:
  ejabberd/invaliduser:

Bug#867309: marked as done (dgit: Use of uninitialized value $got in concatenation)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#867185: fixed in dgit 3.11
has caused the Debian Bug report #867185,
regarding dgit: Use of uninitialized value $got in concatenation
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.)


-- 
867185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 4.0
Severity: normal

Steps to reproduce:

$ dgit clone janus
canonical suite name for unstable is sid
starting new git history
downloading http://ftp.debian.org/debian//pool/main/j/janus/janus_0.2.3-1.dsc...
last upload to archive: NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   380  100   3800 0   2085  0 --:--:-- --:--:-- --:--:--  2087
Use of uninitialized value $got in concatenation (.) or string at /usr/bin/dgit 
line 2545.


Thanks!

cheers, josch


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

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput  0.12.1
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.12.2
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
ii  sbuild  0.73.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.11

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 08 Jul 2017 22:40:15 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: source all
Version: 3.11
Distribution: unstable
Urgency: high
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Closes: 857694 858054 865863 867185 867189 867309 867434 867603 867693
Changes:
 dgit (3.11) unstable; urgency=high
 .
   Important bugfixes to dgit:
   * Fix rpush+buildinfo: Transfer buildinfos for signing.  Closes:#867693.
   * Cope if the archive server sends an HTTP redirect,
 by passing -L to curl.  Closes:#867185,#867309.
   * Cope with newer git which hates --local outside a tree.  Closes:#865863.
   * rpush: Honour local git config from build host working tree.
   * Tolerate compressor terminating with SIGPIPE.  Closes:#857694.
   * Honour more pre-tree git config options in our private trees sharing
 the user's object store.  In particular, core.sharedRepository.
 Prompted by #867603.
   * Clone multisuite works even without --no-rm-on-error.  Closes:#867434.
   

Bug#857694: marked as done (dgit: Died at /usr/bin/dgit line 2196.)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#857694: fixed in dgit 3.11
has caused the Debian Bug report #857694,
regarding dgit: Died at /usr/bin/dgit line 2196.
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.)


-- 
857694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 3.10
Severity: important

this dgit clone fails (the .tar.xz were there from a previously failed
call of the same dgit clone command):

mattia@warren ~/devel/debian/NMU/qt4-perl % dgit -D clone qt4-perl 
clone main body
| curl -sS https://api.ftp-master.debian.org/suites -w '%{http_code}'
=> `[{"name": "backports-new", "dakname": "backports-new", "architectures": 
["all", "source"], "components": ["main", "contrib", "non-free"], "codename": 
null, "archive": "backports-new"}, {"name": "backports-policy", "dakname": 
"backports-policy", "architectures": ["all", "amd64", "armel", "i386", "ia64", 
"kfreebsd-amd64", "kfreebsd-i386", "mips", "mipsel", "powerpc", "s390", 
"source", "sparc"], "components": ["main", "contrib", "non-free"], "codename": 
null, "archive": "backports-policy"}, {"name": "buildd-experimental", 
"dakname": "buildd-experimental", "architectures": ["all", "amd64", "arm64", 
"armel", "armhf", "hurd-i386", "i386", "kfreebsd-amd64", "kfreebsd-i386", 
"mips", "mips64el", "mipsel", "powerpc", "ppc64el", "s390x", "source"], 
"components": ["main", "contrib", "non-free"], "codename": 
"buildd-experimental", "archive": "build-queues"}, {"name": 
"buildd-jessie-backports", "dakname": "buildd-jessie-backports", 
"architectures": ["all", "amd64", "arm64", "armel", "armhf", "i386", 
"kfreebsd-amd64", "kfreebsd-i386", "mips", "mipsel", "powerpc", "ppc64el", 
"s390x"], "components": ["main", "contrib", "non-free"], "codename": null, 
"archive": "build-queues"}, {"name": "buildd-oldstable-proposed-updates", 
"dakname": "buildd-oldstable-proposed-updates", "architectures": ["all", 
"amd64", "armel", "armhf", "i386", "ia64", "kfreebsd-amd64", "kfreebsd-i386", 
"mips", "mipsel", "powerpc", "s390", "s390x", "source", "sparc"], "components": 
["main", "contrib", "non-free"], "codename": "buildd-wheezy-proposed-updates", 
"archive": "build-queues"}, {"name": "buildd-proposed-updates", "dakname": 
"buildd-proposed-updates", "architectures": ["all", "amd64", "arm64", "armel", 
"armhf", "i386", "mips", "mipsel", "powerpc", "ppc64el", "s390x", "source"], 
"components": ["main", "contrib", "non-free"], "codename": 
"buildd-jessie-proposed-updates", "archive": "build-queues"}, {"name": 
"buildd-squeeze-backports", "dakname": "buildd-squeeze-backports", 
"architectures": ["all", "amd64", "armel", "i386", "ia64", "kfreebsd-amd64", 
"kfreebsd-i386", "mips", "mipsel", "powerpc", "s390", "source", "sparc"], 
"components": ["main", "contrib", "non-free"], "codename": null, "archive": 
"build-queues"}, {"name": "buildd-squeeze-backports-sloppy", "dakname": 
"buildd-squeeze-backports-sloppy", "architectures": ["all", "amd64", "armel", 
"i386", "ia64", "kfreebsd-amd64", "kfreebsd-i386", "mips", "mipsel", "powerpc", 
"s390", "source", "sparc"], "components": ["main", "contrib", "non-free"], 
"codename": null, "archive": "build-queues"}, {"name": "buildd-squeeze-lts", 
"dakname": "buildd-squeeze-lts", "architectures": ["all", "amd64", "i386", 
"source"], "components": ["main", "contrib", "non-free"], "codename": 
"buildd-squeeze-lts", "archive": "build-queues"}, {"name": 
"buildd-stable-kfreebsd-proposed-updates", "dakname": 
"buildd-stable-kfreebsd-proposed-updates", "architectures": ["all", 
"kfreebsd-amd64", "kfreebsd-i386", "source"], "components": ["main", "contrib", 
"non-free"], "codename": "buildd-jessie-kfreebsd-proposed-updates", "archive": 
"build-queues"}, {"name": "buildd-testing-proposed-updates", "dakname": 
"buildd-testing-proposed-updates", "architectures": ["amd64", "arm64", "armel", 
"armhf", "i386", "mips", "mips64el", "mipsel", "ppc64el", "s390x"], 
"components": ["main", "contrib", "non-free"], "codename": 
"buildd-stretch-proposed-updates", "archive": "build-queues"}, {"name": 
"buildd-unstable", "dakname": "buildd-unstable", "architectures": ["all", 
"amd64", "arm64", "armel", "armhf", "hurd-i386", "i386", "kfreebsd-amd64", 
"kfreebsd-i386", "mips", "mips64el", "mipsel", "powerpc", "ppc64el", "s390x", 
"source"], "components": ["main", "contrib", "non-free"], "codename": 
"buildd-sid", "archive": "build-queues"}, {"name": "buildd-wheezy-backports", 
"dakname": 

Bug#867185: marked as done (dgit: Perl error trying to clone Gtk+)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 22:03:50 +
with message-id 
and subject line Bug#867185: fixed in dgit 3.11
has caused the Debian Bug report #867185,
regarding dgit: Perl error trying to clone Gtk+
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.)


-- 
867185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 3.10
Severity: normal

The transcript below demonstrates the problem.  I get the same failure on
chiark (jessie), with a clean environment and bogus $HOME (to eliminate my
dotfiles).

[stratocaster /tmp/mdw]dgit clone gtk+3.0
canonical suite name for unstable is sid
starting new git history
downloading 
http://ftp.debian.org/debian//pool/main/g/gtk+3.0/gtk+3.0_3.22.16-1.dsc...
last upload to archive: NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   386  100   3860 0   8327  0 --:--:-- --:--:-- --:--:--  8391
Use of uninitialized value $got in concatenation (.) or string at /usr/bin/dgit 
line 2545.
[stratocaster /tmp/mdw rc=255]

This appears to mean that $checkhash->() failed and it was trying to report
this; I don't know what might have caused that or what I might be able to do
about it.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)
Foreign Architectures: amd64

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

Versions of packages dgit depends on:
ii  apt   1.4.6
ii  ca-certificates   20161130+nmu1
ii  coreutils 8.26-3
ii  curl  7.52.1-5
ii  devscripts2.17.6
ii  dpkg-dev  1.18.24
ii  dput  0.12.1
ii  git [git-core]1:2.11.0-3
ii  git-buildpackage  0.8.12.2
ii  git-core  1:2.11.0-3
ii  libdigest-sha-perl5.96-1+b1
ii  libdpkg-perl  1.18.24
ii  libjson-perl  2.90-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-glob-perl 0.10-1
ii  libtext-iconv-perl1.7-5+b4
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3
ii  realpath  8.26-3

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.4p1-10

Versions of packages dgit suggests:
pn  sbuild  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.11

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit 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, 08 Jul 2017 22:40:15 +0100
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: source all
Version: 3.11
Distribution: unstable
Urgency: high
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Description:
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
Closes: 857694 858054 865863 867185 867189 867309 867434 867603 867693
Changes:
 dgit (3.11) unstable; urgency=high
 .
   Important bugfixes to dgit:
   * Fix rpush+buildinfo: Transfer buildinfos for signing.  Closes:#867693.
   * Cope if the archive server sends an HTTP redirect,
 by passing -L to curl.  Closes:#867185,#867309.
   * Cope with newer git which hates --local outside a tree.  Closes:#865863.
   * 

Bug#807317: again: future of Moodle in Debian: ship with Debian 10 Buster in 2019?

[Moritz Muehlenhoff]

On Fri, Mar 10, 2017 at 11:50:45AM +0100, Joost van Baal-Ilić wrote:
> Hi,
> 
> Is any DD interested in working on shipping Moodle with upcoming upcoming
> Debian 10 Buster release?

Did anyone step up? If not, should we proceed with removal at this point?

Cheers,
Moritz

Bug#866175: marked as done (golang-github-d4l3k-messagediff FTBFS: FAIL: TestPrettyDiff)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 21:34:42 +
with message-id 
and subject line Bug#866175: fixed in golang-github-d4l3k-messagediff 
1.1.0+git20170428.10.080993f-1
has caused the Debian Bug report #866175,
regarding golang-github-d4l3k-messagediff FTBFS: FAIL: TestPrettyDiff
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.)


-- 
866175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-d4l3k-messagediff
Version: 1.1.0-1
Severity: serious

Some recent change in unstable makes golang-github-d4l3k-messagediff FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-d4l3k-messagediff.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-d4l3k-messagediff.html

...
   dh_auto_test -O--buildsystem=golang
go test -v -p 1 github.com/d4l3k/messagediff 
github.com/d4l3k/messagediff/example
=== RUN   TestPrettyDiff
--- FAIL: TestPrettyDiff (0.00s)
messagediff_test.go:41: 12. PrettyDiff(time.Time{sec:62135596800, 
nsec:0, loc:(*time.Location)(nil)}, time.Time{sec:0, nsec:0, 
loc:(*time.Location)(nil)}) diff = "modified: .sec = 0\n"; not "modified: .loc 
= (*time.Location)(nil)\nmodified: .sec = 0\n"
=== RUN   TestPrettyDiffRecursive
--- PASS: TestPrettyDiffRecursive (0.00s)
=== RUN   TestPathString
--- PASS: TestPathString (0.00s)
FAIL
exit status 1
FAILgithub.com/d4l3k/messagediff0.007s
=== RUN   ExampleAtom
--- PASS: ExampleAtom (0.00s)
PASS
ok  github.com/d4l3k/messagediff/example0.010s
dh_auto_test: go test -v -p 1 github.com/d4l3k/messagediff 
github.com/d4l3k/messagediff/example returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-github-d4l3k-messagediff
Source-Version: 1.1.0+git20170428.10.080993f-1

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated 
golang-github-d4l3k-messagediff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 17:06:13 -0400
Source: golang-github-d4l3k-messagediff
Binary: golang-github-d4l3k-messagediff-dev
Architecture: source all
Version: 1.1.0+git20170428.10.080993f-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-d4l3k-messagediff-dev - library for doing diffs of arbitrary 
Golang structs
Closes: 866175
Changes:
 golang-github-d4l3k-messagediff (1.1.0+git20170428.10.080993f-1) unstable; 
urgency=medium
 .
   * New upstream version. (Closes: #866175)
   * Bump Standards-Version to 4.0.0.
Checksums-Sha1:
 bd7f54394f1c681f58b6b44851c42c7229888dd3 2464 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f-1.dsc
 cb3478aaa78b7df104c0cd6735bda8efb826 7048 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f.orig.tar.xz
 a55d612811e1f6127535abe0aa70904b91303633 2036 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f-1.debian.tar.xz
 e54648fca7a70f7b95a93e65bd34f180e72c1a4f 7950 
golang-github-d4l3k-messagediff-dev_1.1.0+git20170428.10.080993f-1_all.deb
 497e050920f4103120f89158775ad8799a76bb00 6174 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f-1_amd64.buildinfo
Checksums-Sha256:
 1a9b01d9d7fa32f5048d88f197632d730fe06099285c0ffb759b5ca66181de77 2464 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f-1.dsc
 136ac11a4aee1fde0ef50b126ba0600a9d6ba315e77e6af74a4e5e433d716264 7048 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f.orig.tar.xz
 9d0b046160b27e37bf280a34ffa01a1a9f1a830b7ad3a3c996ca66b6fcf68e6d 2036 
golang-github-d4l3k-messagediff_1.1.0+git20170428.10.080993f-1.debian.tar.xz
 576f4dd3595de4d7f68c54ca31fe95afe0112562f70a6077ef501ea18bce80f4 

Processed: found 867717 in 1:0.95-2

[Debian Bug Tracking System]

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

> found 867717 1:0.95-2
Bug #867717 [catdoc] CVE-2017-0
Marked as found in versions catdoc/1:0.95-2.
> thanks
Stopping processing here.

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

Processed: tagging 867717

[Debian Bug Tracking System]

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

> tags 867717 + upstream
Bug #867717 [catdoc] CVE-2017-0
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#867717: CVE-2017-11110

[Moritz Muehlenhoff]

Package: catdoc
Severity: grave
Tags: security

This was assigned CVE-2017-0:
https://bugzilla.redhat.com/show_bug.cgi?id=1468471

Cheers,
Moritz

Bug#867711: marked as done (emacspeak: incompatible with emacs23)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 21:03:53 +
with message-id 
and subject line Bug#867711: fixed in emacspeak 46.0+dfsg-3
has caused the Debian Bug report #867711,
regarding emacspeak: incompatible with emacs23
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.)


-- 
867711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacspeak
Version: 46.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze' to 'wheezy' to 'jessie' to stretch to buster..
It installed fine in 'squeeze', and upgraded to 'wheezy', 'jessie', and
'stretch' successfully,
but then the upgrade to 'buster' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

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

  Setting up emacspeak (46.0+dfsg-2) ...
  Install emacspeak for emacs23
  /usr/lib/emacsen-common/packages/install/emacspeak running in /
  Latest installed version: 46.0+dfsg-2
  install/emacspeak: Handling update for emacsen flavor emacs23
Temporary log file is /tmp/fileXOEKwZ
Byte-compiling  (~0.5 min) ...
  ERROR: install script from emacspeak package failed
  dpkg: error processing package emacspeak (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


emacspeak_46.0+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: emacspeak
Source-Version: 46.0+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated emacspeak 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, 08 Jul 2017 22:34:58 +0200
Source: emacspeak
Binary: emacspeak emacspeak-espeak-server
Architecture: source
Version: 46.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Paul Gevers 
Description:
 emacspeak  - speech output interface to Emacs
 emacspeak-espeak-server - espeak syntesis server for emacspeak
Closes: 866157 867711
Changes:
 emacspeak (46.0+dfsg-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * control: Update maintainer mailing list.
   * emacspeak.links: Drop DTK link, not shipped any more (Closes: #866157).
 .
   [ Paul Gevers ]
   * Add Breaks for emacs20 - emacs23 (Closes: #867711)
Checksums-Sha1:
 12fe09c4d653f220cdc89d5e47c9a0b390d88505 1830 emacspeak_46.0+dfsg-3.dsc
 0689a0548ff247d81729aad721597ef2f93dcf55 49284 
emacspeak_46.0+dfsg-3.debian.tar.xz
Checksums-Sha256:
 edac4e520cd8dccb6ce1e902e3aa2dae980a25599381ddaac479bc5c52aeeb29 1830 
emacspeak_46.0+dfsg-3.dsc
 2abfaca276d4c4141f1af73b0443e3ee4f54051bddc715eadb073f3ae22f797a 49284 
emacspeak_46.0+dfsg-3.debian.tar.xz
Files:
 db57eadad8d0801708665723a31f857f 1830 editors optional 
emacspeak_46.0+dfsg-3.dsc
 72024f8013ec85c8c6141c7d1103d762 49284 editors optional 
emacspeak_46.0+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAllhQkgACgkQnFyZ6wW9
dQoxVQf8DIUh4cgRsHbSXhqS6Fu1q7tuOupzj7qmcrYu3wPme4oU4OyBbsz9i1Mp
6v2xla9YNag9m4PItnimIRik6TybXKW5mg+fJk/76XFg5m20TUzINmD4+hi5Cd+r
X7I8i3eIjq4Huw/Rr9waNqtAgolHqXYi2khyOkKNG1B1w5y7EdvAl/r2SZAVDFaX
+tFEQmh79cHQ6BoMu+FsTGaKgmiDNTq6S+b1h/2bIpn+SpGH3TlTL+0Ofx2UmzDf
zLES7TVpCWNVfhrLEGzupddhPdbvGRvuUt6kyC2iWtzmmgSmM8U2arKC1dMrXH8u
shqb06/dH7OH8lzxfW5DPyxw+GpzNg==
=2iaW
-END PGP SIGNATURE End Message ---

Bug#866556: marked as done (d-feet FTBFS: E722 do not use bare except')

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 21:03:44 +
with message-id 
and subject line Bug#866556: fixed in d-feet 0.3.12-1
has caused the Debian Bug report #866556,
regarding d-feet FTBFS: E722 do not use bare except'
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.)


-- 
866556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: d-feet
Version: 0.3.11-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes d-feet FTBFS:

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

...
/usr/bin/make  check-TESTS check-local
make[5]: Entering directory '/build/1st/d-feet-0.3.11/src/tests'
make[6]: Entering directory '/build/1st/d-feet-0.3.11/src/tests'
PASS: tests.py

Testsuite summary for d-feet 0.3.11

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

make[6]: Leaving directory '/build/1st/d-feet-0.3.11/src/tests'
pep8 --max-line-length=99 --ignore=E123,E402 
--exclude='.svn,CVS,.bzr,.hg,.git,__pycache__,.#*' ../../src/
../../src/dfeet/bus_watch.py:109:9: E722 do not use bare except'
../../src/dfeet/bus_watch.py:193:9: E722 do not use bare except'
../../src/dfeet/dbus_utils.py:14:5: E722 do not use bare except'
../../src/dfeet/dbus_utils.py:148:13: E722 do not use bare except'
../../src/dfeet/introspection.py:25:9: E722 do not use bare except'
../../src/dfeet/settings.py:10:1: E722 do not use bare except'
../../src/dfeet/wnck_utils.py:11:1: E722 do not use bare except'
Makefile:820: recipe for target 'check-local' failed
make[5]: *** [check-local] Error 1
--- End Message ---
--- Begin Message ---
Source: d-feet
Source-Version: 0.3.12-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated d-feet 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, 08 Jul 2017 21:27:29 +0100
Source: d-feet
Binary: d-feet
Architecture: source
Version: 0.3.12-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 866556
Description: 
 d-feet - D-Bus object browser, viewer and debugger
Changes:
 d-feet (0.3.12-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/patches/: Instead of patching minor formatting errors, ignore
 the result of the PEP8 check. (Closes: #866556)
   * d/p/ExecuteMethodDialog-Pretty-print-multiple-results.patch:
 Add patch to display multiple results from one method call correctly
 (upstream bug GNOME#784387)
   * d/p/Show-values-that-have-a-logical-False-representation.patch:
 Add patch from upstream Bugzilla to display zero/empty/false
 property values (upstream bug GNOME#783006)
   * Standards-Version: 4.0.0 (no further changes)
   * Upgrade to debhelper 10 compatibility level
 - Do not explicitly run dh-autoreconf, it is now the default
   * Add myself to Uploaders
Checksums-Sha1: 
 2ed3ecc6d3f6174dfcff21dbf93521c16b45e1bf 2210 d-feet_0.3.12-1.dsc
 8099545a32db847de69e3c1eae6f898bcc7133f4 184308 d-feet_0.3.12.orig.tar.xz
 93f928d2e1ff4b92264532ff52143a04c5b5cc77 7304 d-feet_0.3.12-1.debian.tar.xz
Checksums-Sha256: 
 461991fbec49425741ea1287d086cafad97570f3e9887cb9eab056fbef09 2210 
d-feet_0.3.12-1.dsc
 c868c350ea4bb0101d9aeb344661ed4b723f523a5010faf3712ec5984da19014 184308 
d-feet_0.3.12.orig.tar.xz
 dbc3483b736020486036bd37d221ab2086ba58e8c83d1d8c21a9b08eac9555a3 7304 
d-feet_0.3.12-1.debian.tar.xz
Files: 
 9b2ac50ff8d7f0179c923636e7fd80cb 2210 devel extra d-feet_0.3.12-1.dsc
 

Bug#791548: marked as done (gtk-theme-config: clicking on Revert silently removes the user's .gtkrc-2.0 file)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 20:49:05 +
with message-id 
and subject line Bug#791548: fixed in gtk-theme-config 1.2.2-1
has caused the Debian Bug report #791548,
regarding gtk-theme-config: clicking on Revert silently removes the user's 
.gtkrc-2.0 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.)


-- 
791548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk-theme-config
Version: 1.0-1
Severity: critical
Justification: causes serious data loss

I was wondering why Iceweasel was no longer working as expected...
I finally found the cause: my ~/.gtkrc-2.0 file had been removed.
Then I remembered that I used gtk-theme-config recently. After
some tests, clicking on the "Revert" button has this effect of
removing the ~/.gtkrc-2.0 file, without even leaving a backup!

When changing some settings, gtk-theme-config modifies this file.
But when the user clicks on "Revert", gtk-theme-config should just
remove the settings it added, e.g. by using begin/end markers, not
the whole file! Or if is this too difficult, it should warn the
user before doing a destructive operation.

Note also that it isn't documented at all that gtk-theme-config
uses the ~/.gtkrc-2.0 file. This is even more surprising as
gtk-theme-config depends on libgtk-3-0 (thus GTK+ 3, not GTK+ 2).

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

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

Versions of packages gtk-theme-config depends on:
ii  gconf2 3.2.6-3
ii  gsettings-desktop-schemas  3.16.1-1
ii  libatk1.0-02.16.0-2
ii  libc6  2.19-18
ii  libcairo-gobject2  1.14.2-2
ii  libcairo2  1.14.2-2
ii  libgdk-pixbuf2.0-0 2.31.4-2
ii  libglib2.0-0   2.44.1-1.1
ii  libgtk-3-0 3.16.4-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libx11-6   2:1.6.3-1

Versions of packages gtk-theme-config recommends:
ii  xfconf  4.12.0-2+b1

gtk-theme-config suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk-theme-config
Source-Version: 1.2.2-1

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

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

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated gtk-theme-config package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 07 Jul 2017 09:07:13 -0400
Source: gtk-theme-config
Binary: gtk-theme-config
Architecture: source
Version: 1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Xubuntu Developers 
Changed-By: Unit 193 
Description:
 gtk-theme-config - simple interface to change GTK+ themes
Closes: 791548
Changes:
 gtk-theme-config (1.2.2-1) unstable; urgency=medium
 .
   [ Sean Davis ]
   * New upstream bugfix and translations release.
 - Fixes destructive config file editing (Closes: #791548, LP: #1473821)
   * debian/control:
 - Update to Standards-Version 3.9.6
 - Update Homepage to Launchpad
 - Add libnotify-dev and intltool to BuildDepends
 - Add self to Uploaders
   * debian/rules:
 - Fix building with translations.
   * debian/patches/include-system-flags.patch:
 - Dropped, included upstream.
   * debian/watch:
 - Update to point to current upstream releases
 .
   [ Unit 193 ]
   * New upstream release.
 - Fixes theming in Unity 7 (LP: #1315262)
 - Fixes gtk.css generation (LP: #1500210)
   * Update to Standards-Version 4.0.0.
   * d/control, d/compat: Update to use debhelper compat 10.
   * d/control:
 

Processed: Re: Bug#867711: emacspeak: incompatible with emacs23

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #867711 [emacspeak] emacspeak: incompatible with emacs23
Removed tag(s) moreinfo.

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

Bug#867711: emacspeak: incompatible with emacs23

[Andreas Beckmann]

Control: tag -1 - moreinfo

On 2017-07-08 21:58, Paul Gevers wrote:
> On 07/08/17 21:40, Andreas Beckmann wrote:
>> In case the package was not part of an intermediate stable release,
>> the version from the preceding stable release was kept installed.

> Can you clarify what you mean by this?

That doesn't apply in your case. It's for packages like compiz that were
last seen in squeeze (or something) and reappeared in stretch (with
sightly different package layout), having upgrade problems if some old
bits were still installed.

> Emacs23 hasn't been in Debian stable since wheezy. I removed the checks
> for < emacs24 from my latest upload because of that. Do you think I
> really should keep on checking these old versions? And is so, how far do
> I need to go back? emacs22? emacs21? And until when?

Unlike many other packages, the old emacsXX packages seem to stay
(co-)installable forever ... there is nothing on the upgrade path that
makes them go away. But having them installed, triggers stuff to be run
with them at installation time of other packages.

I would probably add
  Breaks: emacs23
(and maybe more old versions previously covered by the removed checks)
for one stable release and thereafter you can be sure that these old
cruft versions can't do harm to your package in the future.

> For what it is worth, in Depends emacspeak has emacs25 | emacs (>=47.0~)
> because emacspeak is also incompatible with emacs24 (but doesn't fail on
> it).

Andreas

Processed: limit source to dgit, tagging 867434, tagging 867693, tagging 857694, tagging 867309, tagging 867185 ...

[Debian Bug Tracking System]

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

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

> tags 867434 + pending
Bug #867434 [dgit] dgit: cloning a combined suite deletes the working directory
Added tag(s) pending.
> tags 867693 + pending
Bug #867693 [dgit] rpush does not work with buildinfos
Added tag(s) pending.
> tags 857694 + pending
Bug #857694 [dgit] dgit: Died at /usr/bin/dgit line 2196.
Added tag(s) pending.
> tags 867309 + pending
Bug #867309 [dgit] dgit: Use of uninitialized value $got in concatenation
Bug #867185 [dgit] dgit: Perl error trying to clone Gtk+
Added tag(s) pending.
Added tag(s) pending.
> tags 867185 + pending
Bug #867185 [dgit] dgit: Perl error trying to clone Gtk+
Bug #867309 [dgit] dgit: Use of uninitialized value $got in concatenation
Ignoring request to alter tags of bug #867185 to the same tags previously set
Ignoring request to alter tags of bug #867309 to the same tags previously set
> tags 867603 + pending
Bug #867603 [dgit] /usr/bin/dgit-badcommit-fixup: does not respect 
core.sharedrepository
Added tag(s) pending.
> tags 865863 + pending
Bug #865863 [dgit] dgit 3.10 and earlier not compatible with git 2.12-ish
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857694
865863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865863
867185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867185
867309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867309
867434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867434
867603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867603
867693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867711: emacspeak: incompatible with emacs23

[Paul Gevers]

Control: tags -1 moreinfo

On 07/08/17 21:40, Andreas Beckmann wrote:
> In case the package was not part of an intermediate stable release,
> the version from the preceding stable release was kept installed.

Can you clarify what you mean by this?

Emacs23 hasn't been in Debian stable since wheezy. I removed the checks
for < emacs24 from my latest upload because of that. Do you think I
really should keep on checking these old versions? And is so, how far do
I need to go back? emacs22? emacs21? And until when?

For what it is worth, in Depends emacspeak has emacs25 | emacs (>=47.0~)
because emacspeak is also incompatible with emacs24 (but doesn't fail on
it).

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#867711: emacspeak: incompatible with emacs23

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #867711 [emacspeak] emacspeak: incompatible with emacs23
Added tag(s) moreinfo.

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

Bug#867711: emacspeak: incompatible with emacs23

[Andreas Beckmann]

Package: emacspeak
Version: 46.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze' to 'wheezy' to 'jessie' to stretch to buster..
It installed fine in 'squeeze', and upgraded to 'wheezy', 'jessie', and
'stretch' successfully,
but then the upgrade to 'buster' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

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

  Setting up emacspeak (46.0+dfsg-2) ...
  Install emacspeak for emacs23
  /usr/lib/emacsen-common/packages/install/emacspeak running in /
  Latest installed version: 46.0+dfsg-2
  install/emacspeak: Handling update for emacsen flavor emacs23
Temporary log file is /tmp/fileXOEKwZ
Byte-compiling  (~0.5 min) ...
  ERROR: install script from emacspeak package failed
  dpkg: error processing package emacspeak (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


emacspeak_46.0+dfsg-2.log.gz
Description: application/gzip

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Ryan Tandy]

On Sat, Jul 08, 2017 at 11:15:48AM -0700, Ryan Tandy wrote:
The bug reproduces consistently when building with stretch's toolchain 
and running stretch's kernel, but I have not seen it at all with 
jessie's kernel *nor* in a jessie chroot on stretch's kernel. I have 
also reproduced it with clang as well as gcc.


The newer compilers generate POWER8 vector instructions e.g. 
mtvsrd/mfvsrd while the older ones do not. A kernel bug related to (or 
triggered by) these instructions would meet the conditions I described. 
Howard suggested we could be looking at a kernel bug around FP/VSR 
save/restore.

Bug#867647: marked as done (ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: return http.request(req, body, ))

[Debian Bug Tracking System]

Your message dated Sat, 8 Jul 2017 21:34:01 +0200
with message-id <20170708193401.om6iklu6vqlib...@xanadu.blop.info>
and subject line 
has caused the Debian Bug report #867647,
regarding ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: 
return http.request(req, body, )
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.)


-- 
867647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rest-client
Version: 1.8.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: return http.request(req, body, )
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: GET 
> http://some/resource with headers {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip, deflate', 'Authorization'=>'Basic Zm9vOmJhcg==', 
> 'User-Agent'=>'Ruby'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:get, "http://some/resource;).
>  with(headers: {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip, deflate', 'Authorization'=>'Basic Zm9vOmJhcg==', 
> 'User-Agent'=>'Ruby'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:get, "http://foo:bar@new/resource;).
>  with(headers: {'Accept'=>'application/json'})
>stub_request(:get, "http://foo:bar@some/resource;).
>  with(headers: {'Accept'=>'application/json'})
> 
>
>  # ./lib/restclient/request.rb:270:in `net_http_do_request'
>  # ./lib/restclient/request.rb:418:in `block in transmit'
>  # ./lib/restclient/request.rb:413:in `transmit'
>  # ./lib/restclient/request.rb:176:in `execute'
>  # ./lib/restclient/request.rb:41:in `execute'
>  # ./spec/unit/response_spec.rb:90:in `block (3 levels) in  (required)>'
> 
> Finished in 0.26307 seconds (files took 0.67677 seconds to load)
> 217 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/unit/response_spec.rb:87 # RestClient::Response redirection 
> follows a redirection and keep the parameters
> 
> Randomized with seed 14583
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/ruby-rest-client_1.8.0-3_unstable.log

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

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

this is fixed in that new version--- End Message ---

Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

[Lucas Nussbaum]

On 08/07/17 at 19:37 +0200, Georg Faerber wrote:
> Hi,
> 
> Unfortunately, I can't reproduce this locally. Besides the sbuild
> options used which are shown in the log file, is there a .sbuildrc in
> place, with non-default options? If so, could you share it?

Have you tried diffing your log with mine?

> Additionally, I've got a question regarding the network configuration of
> the VM on which the build was run: At the moment of the build, were the
> only configured network interfaces localhost and / or loopback?

no.

Also, I've just tried on another machine (that has Internet access). In
that case the test suite hangs at:

user sends a plain text message
  from thunderbird

  Schleuder::ListBuilder


Lucas

Processed: Fix the bug title

[Debian Bug Tracking System]

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

> retitle 867670 libpng1.6 FTBFS on arm* building arm/filter_neon.S
Bug #867670 [src:libpng1.6] libpng1.6 FTBFS on arm*:
Changed Bug title to 'libpng1.6 FTBFS on arm* building arm/filter_neon.S' from 
'libpng1.6 FTBFS on arm*:'.
> thanks
Stopping processing here.

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

Processed: dgit fails with some .xz packages

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #857694 [dgit] dgit: Died at /usr/bin/dgit line 2196.
Severity set to 'serious' from 'important'

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

Processed: tagging 859155, severity of 859155 is serious ..., found 859155 in 1.8.0~pre1-5

[Debian Bug Tracking System]

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

> tags 859155 + sid buster
Bug #859155 [openafs-modules-dkms] openafs-modules-dkms: Please support kernel 
4.10
Added tag(s) buster and sid.
> severity 859155 serious
Bug #859155 [openafs-modules-dkms] openafs-modules-dkms: Please support kernel 
4.10
Severity set to 'serious' from 'wishlist'
> retitle 859155 openafs-modules-dkms: Please support kernel 4.11
Bug #859155 [openafs-modules-dkms] openafs-modules-dkms: Please support kernel 
4.10
Changed Bug title to 'openafs-modules-dkms: Please support kernel 4.11' from 
'openafs-modules-dkms: Please support kernel 4.10'.
> found 859155 1.8.0~pre1-5
Bug #859155 [openafs-modules-dkms] openafs-modules-dkms: Please support kernel 
4.11
Marked as found in versions openafs/1.8.0~pre1-5.
> thanks
Stopping processing here.

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

Bug#867706: backfire-dkms: module FTBFS for Linux 4.11

[Andreas Beckmann]

Package: backfire-dkms
Version: 1.0-1
Severity: serious
Tags: sid buster

backfire-dkms fails to build a module for Linux 4.11:

DKMS make.log for backfire-0.84-2 for kernel 4.11.0-1-amd64 (x86_64)
Sat Jul  8 18:35:33 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.11.0-1-amd64'
  LD  /var/lib/dkms/backfire/0.84-2/build/built-in.o
  CC [M]  /var/lib/dkms/backfire/0.84-2/build/backfire.o
/var/lib/dkms/backfire/0.84-2/build/backfire.c: In function 'backfire_write':
/var/lib/dkms/backfire/0.84-2/build/backfire.c:64:4: error: implicit 
declaration of function 'kill_pid' [-Werror=implicit-function-declaration]
kill_pid(pid, signo, 1);
^~~~
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:305: recipe for 
target '/var/lib/dkms/backfire/0.84-2/build/backfire.o' failed
make[3]: *** [/var/lib/dkms/backfire/0.84-2/build/backfire.o] Error 1
/usr/src/linux-headers-4.11.0-1-common/Makefile:1509: recipe for target 
'_module_/var/lib/dkms/backfire/0.84-2/build' failed
make[2]: *** [_module_/var/lib/dkms/backfire/0.84-2/build] Error 2
Makefile:152: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.11.0-1-amd64'


Andreas

Bug#867703: blktap-dkms: module FTBFS for Linux 4.11

[Andreas Beckmann]

Package: blktap-dkms
Version: 2.0.93-0.8
Severity: serious
Tags: sid buster

Hi,

blktap-dkms fails to build a module for Linux 4.11:

  CC [M]  /var/lib/dkms/blktap/2.0.93/build/device.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/ring.c:38:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.11.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^~
/usr/src/linux-headers-4.11.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.11.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.11.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^~
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro '__RD32'
  ((int)__RD32((BLKTAP_PAGE_SIZE -\
^~
/var/lib/dkms/blktap/2.0.93/build/blktap.h:77:41: note: in expansion of macro 
'BLKTAP_RING_SIZE'
  struct blktap_request *pending[BLKTAP_RING_SIZE];
 ^~~~
/var/lib/dkms/blktap/2.0.93/build/ring.c:187:14: error: initialization from 
incompatible pointer type [-Werror=incompatible-pointer-types]
  .fault= blktap_ring_fault,
  ^
/var/lib/dkms/blktap/2.0.93/build/ring.c:187:14: note: (near initialization for 
'blktap_ring_vm_operations.fault')

Andreas


blktap.make.log.gz
Description: application/gzip

Bug#867691: marked as done (libvirt-python FTBFS with libvirt 3.5.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 18:19:37 +
with message-id 
and subject line Bug#867691: fixed in libvirt-python 3.5.0-1
has caused the Debian Bug report #867691,
regarding libvirt-python FTBFS with libvirt 3.5.0-1
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libvirt-python.html

...
I: pybuild base:184: /usr/bin/python setup.py build 
running build
/usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
/usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
Found 425 functions in /usr/share/libvirt/api/libvirt-api.xml
Found 0 functions in libvirt-override-api.xml
Generated 348 wrapper functions
Missing type converters: 
virStreamSinkFunc:1 
long long *:1 
virStreamSourceFunc:1 
ERROR: failed virStreamRecvHole
ERROR: failed virStreamSparseRecvAll
ERROR: failed virStreamSparseSendAll
error: command '/usr/bin/python' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: libvirt-python
Source-Version: 3.5.0-1

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt-python 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, 08 Jul 2017 19:58:21 +0200
Source: libvirt-python
Binary: python-libvirt python3-libvirt
Architecture: source
Version: 3.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Description:
 python-libvirt - libvirt Python bindings
 python3-libvirt - libvirt Python 3 bindings
Closes: 867691
Changes:
 libvirt-python (3.5.0-1) unstable; urgency=medium
 .
   * [52a4687] Update upstream pgp key
   * [a42ff89] New upstream version 3.5.0 (Closes: #867691)
Checksums-Sha1:
 635bc677acafb4f12c852672c2c57786e62bd916 2138 libvirt-python_3.5.0-1.dsc
 7dceca6ea9e97ab302da6f54b52be40e81f8f9ff 181733 
libvirt-python_3.5.0.orig.tar.gz
 fecc8af13350e9041ba60e152934e6265703dd6e 9088 
libvirt-python_3.5.0-1.debian.tar.xz
 94bdcfd0c5cdaa55c180c2c45595eba02bcd8bd1 8615 
libvirt-python_3.5.0-1_amd64.buildinfo
Checksums-Sha256:
 4cc33565572cd91945b3c64b96d7150570e17cf2379967eaf2f5a38a38b23117 2138 
libvirt-python_3.5.0-1.dsc
 5c5fee90bebf39d318ef55545077431c3da9ae8b6352adfa461fa4492a03ac1a 181733 
libvirt-python_3.5.0.orig.tar.gz
 d458442682b15687940bd1e49e8c07bf948f220dae5bb4d13c338e9d33920386 9088 
libvirt-python_3.5.0-1.debian.tar.xz
 ae6f412a18f3b7cd6d02c9a7cce9f1e3dcba8fa7690bf766cc346c3f7f0c82bc 8615 
libvirt-python_3.5.0-1_amd64.buildinfo
Files:
 d705c366e25fded737464024390f5f55 2138 python optional 
libvirt-python_3.5.0-1.dsc
 0e4a9366c545ef1426730da77ffba1b9 181733 python optional 
libvirt-python_3.5.0.orig.tar.gz
 00b90b330df2aaf72c7933b0315bc6b2 9088 python optional 
libvirt-python_3.5.0-1.debian.tar.xz
 d737abfe82972e878dcd81b9969b9bba 8615 python optional 
libvirt-python_3.5.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAllhHc8ACgkQB7i3sOqY
EgsJpQ//YMhFd6M7y597Zd1o78c/kQMgR2o/4FDfgc7f47SUiKKbdh0t/umEU0KJ
mDgxS5wAwW0WDndj/DkpBAPctb0s/12Vz4niyshXiAihI4h4hzxNpK2VyWLyE2fa
Fnuj4hG88Fu+A+3LJtqSq+m7zIbQYyxvjJzS0hlxwvlSLuyu4tuacqDVJg/+XMKz
u4Gp3sIlY8K1ooBGlHL+vyjaFkIgRB/y+CIuOCLhbLgio2EbIP2+PazHshdZUGOQ
2gSD772HwQ9DlwcXF+55zDQMg5QeUqR2GRnQ1++iD1fotx5yMU46sEpZfKm6lUhv
Y+RlxcS9Ktfo+BZexFuO8J77uWMohS6V0nUOt3P8O4kV7XdgWXC/HpxLxz9oHH8Y

Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

[Ryan Tandy]

I spent some more time on this issue and I believe I isolated the 
problem to the following line:


int r = ((double)nvalues)*rand()/(RAND_MAX + 1.0);

http://sources.debian.net/src/openldap/2.4.44%2Bdfsg-7/tests/progs/slapd-mtread.c/#L682

Specifically, during the multi-threaded tests, casting 'nvalues' from 
int to double occasionally comes up with the wrong result.


e.g.:
(double)19 -> 61.00

Note that 'nvalues' is a local variable in the same function. There 
should be zero chance of it being shared with another thread or anything 
like that.


The bug reproduces consistently when building with stretch's toolchain 
and running stretch's kernel, but I have not seen it at all with 
jessie's kernel *nor* in a jessie chroot on stretch's kernel. I have 
also reproduced it with clang as well as gcc.

Bug#867701: Radeon HD 6450, black screen, cursor, no console

[Ivan Sergio Borgonovo]

Package: xserver-xorg-video-radeon
Version: 1:7.9.0-1
Severity: grave

Upgrading from 1:7.8.0-1+b1 to 1:7.9.0-1, PC boot but I get a black 
screen with cursor on the top left, I can't switch to console, xorg log 
just say


[28.383] (II) glamor: OpenGL accelerated X.org driver based.
[28.441] (EE)
[28.441] (EE) Backtrace:

downgrading solve the problem.

I've a very very similar PC, same motherboard and slightly different 
video card (Turks PRO [Radeon HD 6570) that works.


--
Ivan Sergio Borgonovo
http://www.webthatworks.it http://www.borgonovo.net

Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

[Georg Faerber]

Hi,

Unfortunately, I can't reproduce this locally. Besides the sbuild
options used which are shown in the log file, is there a .sbuildrc in
place, with non-default options? If so, could you share it?

Additionally, I've got a question regarding the network configuration of
the VM on which the build was run: At the moment of the build, were the
only configured network interfaces localhost and / or loopback?

Thanks,
Georg


signature.asc
Description: Digital signature

Bug#866575: [Python-modules-team] Bug#866575: libapache2-mod-wsgi-py3: Impossible depends when built with more then one supported python3 version

[Scott Kitterman]

On Saturday, July 08, 2017 12:52:39 PM Bas Couwenberg wrote:
> Package: libapache2-mod-wsgi-py3
> Version: 4.5.11-1
> Followup-For: Bug #866575
> 
> Dear Maintainer,
> 
> The attached patch fixes this issue, but there are several other issues
> with the package that should be fixed in the next upload too.

Thanks for the patch.  I have committed it to the DPMT git repository for the 
next upload.  Since I'm not the package maintainer, I am going to leave it to 
them to decide what else needs to be addressed.

In particular, I suspect this package will need to be rebuilt again when the 
default python3 version changes to update the symlink:

 ./usr/lib/apache2/modules/mod_wsgi.so -> mod_wsgi.so-3.5

Given that, it might make more sense to only build it for the default version.

Thanks again,

Scott K

Bug#866575: marked as pending

[Scott Kitterman]

tag 866575 pending
thanks

Hello,

Bug #866575 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:


https://anonscm.debian.org/cgit/python-modules/packages/mod-wsgi.git/commit/?id=8a3cee5

---
commit 8a3cee53c0c544d0789ed4d44fcb714380ffdc9e
Author: Scott Kitterman 
Date:   Sat Jul 8 13:20:02 2017 -0400

* Fix min/max Python 3 version determination for multiple versions.
  (closes: #866575)

diff --git a/debian/changelog b/debian/changelog
index b398340..8569b0f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+mod-wsgi (4.5.11-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+
+  [ Bas Couwenberg ]
+  * Fix min/max Python 3 version determination for multiple versions.
+(closes: #866575)
+
+  [ Felix Geyer ]
+  * Remove myself from Uploaders.
+
+ -- Scott Kitterman   Sat, 08 Jul 2017 13:04:06 -0400
+
 mod-wsgi (4.5.11-1) unstable; urgency=medium
 
   * [8d515a5] Merge tag 'upstream/4.5.11'

Processed: Bug#866575 marked as pending

[Debian Bug Tracking System]

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

> tag 866575 pending
Bug #866575 [libapache2-mod-wsgi-py3] libapache2-mod-wsgi-py3: Impossible 
depends when built with more then one supported python3 version
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: dgit invokes curl in a way that fails on redirects

[Debian Bug Tracking System]

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

> severity 867185 serious
Bug #867185 [dgit] dgit: Perl error trying to clone Gtk+
Severity set to 'serious' from 'normal'
> forcemerge 867185 867309
Bug #867185 [dgit] dgit: Perl error trying to clone Gtk+
Bug #867309 [dgit] dgit: Use of uninitialized value $got in concatenation
Severity set to 'serious' from 'normal'
Marked as found in versions dgit/3.10.
Bug #867185 [dgit] dgit: Perl error trying to clone Gtk+
Marked as found in versions dgit/4.0.
Merged 867185 867309
> thanks
Stopping processing here.

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

Bug#867695: debian-design FTBFS with shellcheck 0.4.6-1

[Adrian Bunk]

Source: debian-design
Version: 3.0.7
Severity: serious
Tags: buster sid

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

...
# check that all package lists are populated
test -n "task-xfce-desktop, task-laptop, abiword, alsa-utils, apt-listchanges, 
aptitude, buku, bzip2, dfc, evince, firefox-esr, git, gnome-system-tools, 
gnumeric, gtk2-engines-xfce, gvfs, info, less, libgl1-mesa-dri, 
libreoffice-calc, libreoffice-gtk2, libreoffice-impress, libreoffice-ogltrans, 
libreoffice-style-tango, libreoffice-writer, lightdm, lightning, links, man-db, 
manpages, mc, mpv, mtr-tiny, myrepos, ncdu, needrestart, network-manager-gnome, 
pasystray, pavucontrol, popularity-contest, pulseaudio, pulseaudio-utils, 
rsync, tango-icon-theme, thunar, thunderbird, unicode-screensaver, v4l-utils, 
volti, wget, xfce4-notifyd, xfce4-power-manager, xfce4-power-manager-plugins, 
xfce4-session, xserver-xorg, xul-ext-sieve,"
set -e; test -n "diffpdf, font-manager, gcolor2, gimp, gimp-lensfun, 
gimp-plugin-registry, gpick, gtk-vector-screenshot, gucharmap, inkscape, 
jpeginfo, jpegoptim, lcdf-typetools, libpdf-reuse-perl, libpodofo-utils, 
librsvg2-bin, libtiff-tools, mypaint, mypaint-data-extras, origami-pdf, 
pdfposter, pdfshuffler, pngcrush, poppler-utils, python-cairosvg, python-scour, 
qpdf, scribus, scrot, shotwell, typecatcher,";  test -n "blender, 
synfigstudio,";  test -n "chromium, chromium-l10n, compass-blueprint-plugin, 
compass-color-schemer-plugin, compass-fancy-buttons-plugin, 
compass-h5bp-plugin, compass-layoutgala-plugin, compass-normalize-plugin, 
compass-singularitygs-plugin, compass-slickmap-plugin, compass-susy-plugin, 
compass-toolkit-plugin, compass-yui-plugin, surf,"; 
perl -0777 -n \
-e 's,.*d-i preseed/late_command string ,#!/bin/sh\n,ms' \
-e ' and print $_' \
content/desktop/preseed.cfg > design-desktop-tidy
shellcheck -e SC1003 -e SC2016 -e SC2034 -e SC2046 -e SC2048 -e SC2086 
design-desktop-tidy

In design-desktop-tidy line 38:
  if [ -e "$1" ] && egrep -q "^#?$2\$" "$1"; then \
^-- SC2196: egrep is non-standard and deprecated. Use grep 
-E instead.


In design-desktop-tidy line 49:
  if [ -e "$1" ] && egrep -q "^#?$2=" "$1"; then \
^-- SC2196: egrep is non-standard and deprecated. Use grep 
-E instead.

debian/blends.mk:87: recipe for target 'design-desktop-tidy' failed
make: *** [design-desktop-tidy] Error 1

Bug#867694: netsurf-fb: Completely unusable

[Salvo Tomaselli]

Package: netsurf-fb
Version: 3.6-3.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

netsurf-fb comes without any documentation on how to get it working.

I had to figure out by myself that I was supposed to add my user to the input
group.

After this, it was complaining about fb initialisation. Searching, I found this
page:

https://askubuntu.com/questions/817937/how-to-run-netsurf-fb-fails-with-unable-to-set-video-could-not-set-console-s

But the 3rd solution did not work and my screen just gets completely black and
I need to hard reset the machine.

Fix these issues, or at least document how to make this thing work, add the
necessary dependencies, or remove this package.

Best

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

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

Versions of packages netsurf-fb depends on:
ii  libc62.24-12
ii  libcurl3 7.52.1-5
ii  libexpat12.2.1-2
ii  libfreetype6 2.8-0.2
ii  libjpeg62-turbo  1:1.5.1-2
ii  libpng16-16  1.6.29-3
ii  libsdl1.2debian  1.2.15+dfsg1-4
ii  libssl1.0.2  1.0.2l-2
ii  libvncserver10.9.11+dfsg-1
ii  libxcb-icccm40.4.1-1
ii  libxcb-image00.4.0-1+b2
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-shm0  1.12-1
ii  libxcb-util0 0.3.8-3+b2
ii  libxcb1  1.12-1
ii  netsurf-common   3.6-3.1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages netsurf-fb recommends:
ii  mime-support  3.60

netsurf-fb suggests no packages.

-- no debconf information

Processed: Re: Bug#867115: smplayer crashes with "Error parsing option noquiet (option not found)"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #867115 [smplayer] smplayer crashes with "Error parsing option noquiet 
(option not found)"
Severity set to 'important' from 'grave'
> tags -1 moreinfo
Bug #867115 [smplayer] smplayer crashes with "Error parsing option noquiet 
(option not found)"
Added tag(s) moreinfo.

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

Bug#867115: smplayer crashes with "Error parsing option noquiet (option not found)"

[Reinhard Tartler]

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

Thank you for your bugreport. I had a look at the issue and have some
questions for you.

On Mon, Jul 3, 2017 at 6:09 PM Daniel 'DaB.' Baur 
wrote:

> Package: smplayer
> Version: 16.11.0~ds0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> after the update to Debian Stretch, which makes smplayer using mpv instead
> of mplayer, the smplayer does not work anymore.
>
> Any file I try to open, smplayer crashes with "Error parsing option noquiet
> (option not found)". The problems seems to be, that mpv doesn’t have the
> same options that mplayer had, but smplayer does not respect this.
>

I can't reproduce that here. I've tested with these package versions:
siretart@debian:~$ dpkg -l mpv mplayer2 smplayer
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version
 Architecture Description
+++-==---=
un  mplayer2  
  (no description available)
ii  mpv0.23.0-2+b2  amd64
 video player based on MPlayer/mplayer2
ii  smplayer   16.11.0~ds0-1amd64
 Complete front-end for MPlayer and mpv


Invoking smplayer like this plays the video just fine:

siretart@debian:~$ smplayer
/tmp/20060131_dropping-pre-i686_jbailey-doko.ogg
This is SMPlayer v. 16.11.0 (revision 8242) running on Linux
siretart@debian:~$ echo $?
0

Please be more specific how to reproduce this issue. Do you have any local
versions of mpv in /usr/lo


Could this please be fixed or reverted back? Currently smplayer is pretty
useless in Debian.


Sincerely,
DaB.


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'oldstable-updates'), (300,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to de_DE.UTF-8), LANGUAGE=de (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages smplayer depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5network55.7.1+dfsg-3+b1
ii  libqt5script5 5.7.1~20161021+dfsg-2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  mpv   0.23.0-2+b2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages smplayer recommends:
ii  smplayer-l10n16.11.0~ds0-1
ii  smplayer-themes  1:16.8.0-1

smplayer suggests no packages.

-- no debconf information
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainerscal
or something?

Also, there is a new upstream version of smplayer in
experimental 17.3.0~ds0-1. Do you experience this issue also with that
version? If not, I'd propose to upload it to unstable.


>
> AFAIS you were told in #783401 that this would happen, but somehow this
> was ignored.
>

I don't know. That bug was marked fixed on Fri, 15 Jan 2016  and didn't see
any updates since then. I'd assume that the package worked fine for the
uploader back then, just like the current package works fine with mpv for
me.

It is certainly possible that I'm missing something here. In that case, any
clarifications would be much appreciated.

Best,
Reinhard

Bug#867691: libvirt-python FTBFS with libvirt 3.5.0-1

[Adrian Bunk]

Source: libvirt-python
Version: 3.0.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libvirt-python.html

...
I: pybuild base:184: /usr/bin/python setup.py build 
running build
/usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
/usr/bin/python generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
Found 425 functions in /usr/share/libvirt/api/libvirt-api.xml
Found 0 functions in libvirt-override-api.xml
Generated 348 wrapper functions
Missing type converters: 
virStreamSinkFunc:1 
long long *:1 
virStreamSourceFunc:1 
ERROR: failed virStreamRecvHole
ERROR: failed virStreamSparseRecvAll
ERROR: failed virStreamSparseSendAll
error: command '/usr/bin/python' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25

Bug#866988: marked as done (lordsawar FTBFS: bigmap.cpp:70:16: error: no match for 'operator==' (operand types are 'Cairo::RefPtr' and 'bool'))

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 15:51:11 +
with message-id 
and subject line Bug#866988: fixed in lordsawar 0.3.1-2
has caused the Debian Bug report #866988,
regarding lordsawar FTBFS: bigmap.cpp:70:16: error: no match for 'operator==' 
(operand types are 'Cairo::RefPtr' and 'bool')
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.)


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

Some recent change in unstable makes lordsawar FTBFS:

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

...
bigmap.cpp: In destructor 'virtual BigMap::~BigMap()':
bigmap.cpp:70:16: error: no match for 'operator==' (operand types are 
'Cairo::RefPtr' and 'bool')
 if (buffer == true)
 ~~~^~~
bigmap.cpp:70:16: note: candidate: operator==(int, int) 
bigmap.cpp:70:16: note:   no known conversion for argument 1 from 
'Cairo::RefPtr' to 'int'
In file included from /usr/include/cairomm-1.0/cairomm/device.h:24:0,
 from /usr/include/cairomm-1.0/cairomm/surface.h:39,
 from /usr/include/gdkmm-3.0/gdkmm/pixbuf.h:39,
 from /usr/include/gdkmm-3.0/gdkmm/dragcontext.h:30,
 from /usr/include/gtkmm-3.0/gtkmm.h:90,
 from bigmap.h:29,
 from bigmap.cpp:27:
/usr/include/cairomm-1.0/cairomm/refptr.h:397:6: note: candidate: bool 
Cairo::RefPtr::operator==(const Cairo::RefPtr&) const 
[with T_CppObject = Cairo::Surface]
 bool RefPtr::operator==(const RefPtr& src) const 
noexcept
  ^~~
...
--- End Message ---
--- Begin Message ---
Source: lordsawar
Source-Version: 0.3.1-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lordsawar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 16:55:44 +0200
Source: lordsawar
Binary: lordsawar lordsawar-data
Architecture: source
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 lordsawar  - Clone of the popular SSG game Warlords II
 lordsawar-data - Clone of the popular SSG game Warlords II - data files
Closes: 866988
Changes:
 lordsawar (0.3.1-2) unstable; urgency=medium
 .
   * Declare compliance with Debian Policy 4.0.0.
   * Drop deprecated menu file and xpm icon.
   * Use https for Format field.
   * Add bigmap-cairomm.patch and fix FTBFS with cairomm 1.12.2.
 (Closes: #866988)
Checksums-Sha1:
 85b4f8861bfa39f1f76fb99b434dbb673ccc1a5f 2297 lordsawar_0.3.1-2.dsc
 24175639695deb8d96950956f35ff9f5ef535034 5756 lordsawar_0.3.1-2.debian.tar.xz
 f9a846b622ea8923be99c8929b89372d628ea937 14757 
lordsawar_0.3.1-2_amd64.buildinfo
Checksums-Sha256:
 1f00124eaf05df2e49f5c47a771bf2bfb142d52551cc5d6b30b9bece54acaf32 2297 
lordsawar_0.3.1-2.dsc
 6bcbb3041a37d4ae5f2f32fb61eb5f31c18d42c85fcb7c24c3c32c2f199f7205 5756 
lordsawar_0.3.1-2.debian.tar.xz
 778450f5cd93161b19f1873b6e20821ec8442b66fdef97590de0b307c878c7d0 14757 
lordsawar_0.3.1-2_amd64.buildinfo
Files:
 2610155a2ceb2799b1ce3d7e702ef402 2297 games optional lordsawar_0.3.1-2.dsc
 b09517ee740d204b989fab88e31a460c 5756 games optional 
lordsawar_0.3.1-2.debian.tar.xz
 46f29242bed6aad931c836e9be545c4f 14757 games optional 
lordsawar_0.3.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAllg+kVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkakIQAMpfrBEVsC1fDzTm3ylUyfVLGnsRXRDuO/OY
KVgsBUhpdisbenGu/v4A/FQF1R5C4L9VVlzlYwjiEYcX4sDFPfoOsBwoqjGF87jy

Bug#846314: alot: Migrate from pygpgme to python-gpg

[Jonathan Wiltshire]

On Sat, Jul 08, 2017 at 12:03:30AM -0700, Jordan Justen wrote:
> On 2017-06-27 11:08:09, Jonathan Wiltshire wrote:
> > Control: severity -1 serious
> > 
> > Hi,
> > 
> > Bumping severity, because in ~1 month I will request removal of pygpgme
> > from unstable.
> 
> According to:
> 
> https://udd.debian.org/cgi-bin/autoremovals.cgi
> 
> the 'alot' package is 'flagged for removal in 5.1 days', but your
> update says pygpgme will be removed in ~1 month.

You're confusing suites. It will be automatically removed from testing in 5
days. I will be requesting removal of pygpgme from unstable at the end of
this month (but it's up to ftp masters if they do so immediately and break
things, or wait for dependencies to be resolved).

Thanks,

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

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

Processed: astroquery FTBFS with python 3.6 as supported version

[Debian Bug Tracking System]

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

> reassign 867502 src:pytest
Bug #867502 [src:astroquery] astroquery FTBFS with python 3.6 as supported 
version
Bug reassigned from package 'src:astroquery' to 'src:pytest'.
No longer marked as found in versions astroquery/0.3.5+dfsg-2.
Ignoring request to alter fixed versions of bug #867502 to the same values 
previously set
> affects 867502 src:astroquery
Bug #867502 [src:pytest] astroquery FTBFS with python 3.6 as supported version
Added indication that 867502 affects src:astroquery
>
End of message, stopping processing here.

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

Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

[Lucas Nussbaum]

On 08/07/17 at 12:16 +0200, Georg Faerber wrote:
> Hi Lucas,
> 
> Thanks for the report:
> 
> On 17-07-08 08:28:30, Lucas Nussbaum wrote:
> >
> > [...] 
> >
> > 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.
> 
> Was a wrapper used, like pbuilder or sbuild?

Yes, sbuild

Lucas

Bug#867106: marked as done (wine-development: build-depends unicode-data (< 10.0) but 10.0.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 15:12:14 +
with message-id 
and subject line Bug#867106: fixed in wine-development 2.11-2
has caused the Debian Bug report #867106,
regarding wine-development: build-depends unicode-data (< 10.0) but 10.0.0-1 is 
to be installed
to be marked as done.

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

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


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

# apt-get build-dep wine-development
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:wine-development : Depends: unicode-data (< 10.0) but 10.0.0-1 is to 
be installed
E: Unable to correct problems, you have held broken packages.
#
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 2.11-2

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

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

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

Debian distribution maintenance software
pp.
Jens Reyer  (supplier of updated wine-development 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 13:37:04 +0200
Source: wine-development
Binary: wine-development wine32-development wine64-development 
wine32-development-preloader wine64-development-preloader 
wine32-development-tools wine64-development-tools libwine-development 
libwine-development-dev
Architecture: source
Version: 2.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Jens Reyer 
Description:
 libwine-development - Windows API implementation - library
 libwine-development-dev - Windows API implementation - development files
 wine-development - Windows API implementation - standard suite
 wine32-development - Windows API implementation - 32-bit binary loader
 wine32-development-preloader - Windows API implementation - prelinked 32-bit 
binary loader
 wine32-development-tools - Windows API implementation - 32-bit developer tools
 wine64-development - Windows API implementation - 64-bit binary loader
 wine64-development-preloader - Windows API implementation - prelinked 64-bit 
binary loader
 wine64-development-tools - Windows API implementation - 64-bit developer tools
Closes: 867106
Changes:
 wine-development (2.11-2) unstable; urgency=medium
 .
   * Update to using Unicode 10 (closes: #867106).
Checksums-Sha1:
 ab9789620abc5ef44f7f24204a4df44dfe457922 3863 wine-development_2.11-2.dsc
 9ff87d163212d1d9c325fbc85c2b5e69cc1ce5a9 177748 
wine-development_2.11-2.debian.tar.xz
 1233e10a6faa32e5c59818c8f8b842659138759b 15933 
wine-development_2.11-2_all.buildinfo
Checksums-Sha256:
 441682382e01def7fb5c5a19a302898fb81e8aa07f0716c031fcfb37b5d7ddba 3863 
wine-development_2.11-2.dsc
 cf98ea0cff22b0d1da89f5d4ee3fa98ae9ec24ccbf67e144a8502ea741f37791 177748 
wine-development_2.11-2.debian.tar.xz
 24e9cafa16af199826ca2b573c7b676873d121436c001742125be40e48716fa2 15933 
wine-development_2.11-2_all.buildinfo
Files:
 589e75a30d93a67a492ddf00665aa7d8 3863 otherosfs optional 
wine-development_2.11-2.dsc
 abadaf26f41669850e99e20d8e4452d0 177748 otherosfs optional 
wine-development_2.11-2.debian.tar.xz
 622f2bd2d420ea2c2b248693ae9f30ec 15933 otherosfs optional 
wine-development_2.11-2_all.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEo+4EaAPA6D5jhqo9YIQSAytXMHYFAllg6m8ACgkQYIQSAytX
MHbnIQ/9EbsGC/umL/f7uULgwpoB//AcevOBP+slXXPDlV78aIm5ayuyopXw6kgZ
ZutUsRXH2zrjDfKNPMJt8ZydMWmgETxHHfRpfSkvEe75fYoeylK6JtKKJihTpKWQ

Bug#837387: xul-ext-compactheader: uninstallable in jessie and wheezy

[Andreas Beckmann]

On Sat, 21 Jan 2017 21:47:55 +0100 Andreas Beckmann  wrote:
> Hi David,
> 
> could you take a look at updating xul-ext-compactheader in jessie (and
> wheezy)? These have become uninstallable after switching to newer
> icedove versions in stable/oldstable.

in the mean time: s/icedove/thunderbird/

Ping?

Should xul-ext-compactheader be removed from jessie instead?


Andreas

Processed: unarchiving 858509, found 858509 in 20170403-1, found 857226 in 3.4.1+dfsg-1

[Debian Bug Tracking System]

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

> unarchive 858509
Bug #858509 {Done: Christoph Berg } 
[cl-csv-data-table] cl-csv-data-table: broken symlink: 
/usr/share/common-lisp/systems/cl-csv-data-table.asd -> 
../source/cl-csv-data-table/cl-csv-data-table.asd
Unarchived Bug 858509
> found 858509 20170403-1
Bug #858509 {Done: Christoph Berg } 
[cl-csv-data-table] cl-csv-data-table: broken symlink: 
/usr/share/common-lisp/systems/cl-csv-data-table.asd -> 
../source/cl-csv-data-table/cl-csv-data-table.asd
Marked as found in versions cl-csv/20170403-1 and reopened.
> found 857226 3.4.1+dfsg-1
Bug #857226 [cl-pgloader] cl-pgloader: broken symlink: 
/usr/share/common-lisp/systems/pgloader.asd -> ../source/pgloader/pgloader.asd
Marked as found in versions pgloader/3.4.1+dfsg-1.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 865572, found 865572 in 0.3.3-1, found 865572 in 0.7.3-2 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 865572 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 865572 0.3.3-1
Bug #865572 [ruby-autoparse,ruby-signet] ruby-signet and ruby-autoparse: error 
when trying to install together
There is no source info for the package 'ruby-signet' at version '0.3.3-1' with 
architecture ''
Marked as found in versions ruby-autoparse/0.3.3-1.
> found 865572 0.7.3-2
Bug #865572 [ruby-autoparse,ruby-signet] ruby-signet and ruby-autoparse: error 
when trying to install together
There is no source info for the package 'ruby-autoparse' at version '0.7.3-2' 
with architecture ''
Marked as found in versions ruby-signet/0.7.3-2.
> found 859579 1.1.9+dfsg-1
Bug #859579 [python-cvxopt-doc] python-cvxopt-doc: fails to upgrade from 'sid' 
- trying to overwrite /usr/share/doc-base/cvxopt
Marked as found in versions cvxopt/1.1.9+dfsg-1.
> severity 865614 serious
Bug #865614 [aufs-dkms] aufs-dkms: aufs-dkms does not support Linux 4.11
Severity set to 'serious' from 'important'
> usertags 865614 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 782155 2.02-2
Bug #782155 [grub-pc] grub-pc: unowned files after purge (policy 6.8, 10.8): 
/boot/grub/unicode.pf2
Marked as found in versions grub2/2.02-2.
> found 782156 2.02-2
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8): 
/boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02-2.
> found 863960 8.13.11+dfsg1-8
Bug #863960 [gitlab] gitlab: unowned files after purge (policy 6.8, 10.8)
Marked as found in versions gitlab/8.13.11+dfsg1-8.
> usertags 849987 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
782155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782155
782156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
849987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849987
859579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859579
863960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863960
865572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865572
865614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867671: libratbag-tools: removal of libratbag-tools/sid makes files disappear from liblur3/testing

[Stephen Kitt]

Hi Andreas,

Thanks for taking the time to file this bug.

On Sat, 08 Jul 2017 14:02:29 +0200, Andreas Beckmann  wrote:
> during a test with piuparts and DOSE tools I noticed your package causes
> removal of files that also belong to another package.
> This is caused by using Replaces without corresponding Breaks.
> 
[...]
> 
> The list of installed files at points (1) and (2) should be identical,
> but the following files have disappeared:
> 
>   /usr/share/man/man1/lur-command.1.gz
> 
> This is a serious bug violating policy 7.6, see
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> and also see the footnote that describes this incorrect behavior
> https://www.debian.org/doc/debian-policy/footnotes.html#f53

As I understand Policy in this case, I’m not convinced this is a violation.
lur-command.1.gz should never have been in liblur3; it should always have
been in libratbag-tools. I moved the file from liblur3 to libratbag-tools, and
added the appropriate Replaces relationship; but as I understand it, Breaks
isn’t needed because the upgrade doesn’t actually break liblur3. Considering
the behaviour described in footnote 54 (53 doesn’t apply here AFAICT), I don’t
think there’s a problem: the old liblur3 does end up missing a file, but it’s
a file it doesn’t need and should never have had, so its disappearance
doesn’t cause any problems.

The only problematic scenario is
* install liblur3 0.5-2
* install libratbag-tools 0.9-2
* remove libratbag-tools
* install libratbag-tools 0.5-2
which results in lur-command.1.gz not being installed, but that’s really an
unsupported scenario anyway, akin to downgrading libratbag-tools.

Regards,

Stephen


pgpl3ovPnolgE.pgp
Description: OpenPGP digital signature

Processed: This has been fixed for stretch in a DSA

[Debian Bug Tracking System]

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

> fixed 867032 2.4.0-3+deb9u1
Bug #867032 [jabberd2] jabberd2: CVE-2017-10807: allows anyone to authenticate 
using SASL ANONYMOUS, even when the option is not enabled
Marked as fixed in versions jabberd2/2.4.0-3+deb9u1.
> thanks
Stopping processing here.

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

Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and system upgraded to stretch

[Andreas Beckmann]

Package: squid-deb-proxy-client
Version: 0.8.9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package can cause problems
after upgrading from 'jessie' to 'stretch'.

If squid-deb-proxy-client is removed (but not purged) from jessie,
/etc/apt/apt.conf.d/30autoproxy is left behind. This causes a warning in
jessie, but no failure:

  Failed to exec method /usr/share/squid-deb-proxy-client/apt-avahi-discover

But this is a failure in stretch. The 'apt-get dist-upgrade' from jessie
to stretch works fine, but any further apt opertion will fail, e.g.
installing a package (like squid-deb-proxy-client):

  Err:1 http://ftp.de.debian.org/debian stretch/main amd64 
squid-deb-proxy-client all 0.8.14
Sub-process ProxyAutoDetect returned an error code (100)
  E: Failed to fetch 
http://ftp.de.debian.org/debian/pool/main/s/squid-deb-proxy/squid-deb-proxy-client_0.8.14_all.deb
  Sub-process ProxyAutoDetect returned an error code (100)


cheers,

Andreas


squid-deb-proxy-client_0.8.14.log.gz
Description: application/gzip

Bug#867681: software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get update'

[peacerebel]

Package: software-properties-gtk
Version: 0.96.20.2-1
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

>> Adding other repos and keys via gui.

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

>> Deleted /etc/apt/trusted.gpg file and all
contents of /var/lib/apt/lists directory.

   * What was the outcome of this action?

>>'app-get update' didn't give any errors.

   * What outcome did you expect instead?

>> Same as the above mentioned.

Note: Got the temporary fix from
https://readlist.com/lists/lists.debian.org/debian-user/77/388466.html

*** End of the template - remove these template lines ***



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

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

Versions of packages software-properties-gtk depends on:
ii  gir1.2-gtk-3.0   3.22.11-1
ii  python3  3.5.3-1
ii  python3-gi   3.22.0-2
ii  python3-software-properties  0.96.20.2-1
ii  software-properties-common   0.96.20.2-1

software-properties-gtk recommends no packages.

Versions of packages software-properties-gtk suggests:
ii  gnome-software  3.22.5-1

Bug#867679: libglib2.0-dev-bin: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gdbus-codegen

[Andreas Beckmann]

Package: libglib2.0-dev-bin
Version: 2.53.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libglib2.0-dev-bin.
  Preparing to unpack .../libglib2.0-dev-bin_2.53.3-1_amd64.deb ...
  Unpacking libglib2.0-dev-bin (2.53.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-dev-bin_2.53.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/gdbus-codegen', which is also in package 
libglib2.0-dev 2.52.3-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libglib2.0-dev-bin_2.53.3-1_amd64.deb


cheers,

Andreas


libglib2.0-dev=2.52.3-1_libglib2.0-dev-bin=2.53.3-1.log.gz
Description: application/gzip

Bug#867678: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua

[Andreas Beckmann]

Package: prosody
Version: 0.10~hg745e0a783055-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Preparing to unpack .../prosody_0.10~hg745e0a783055-2_amd64.deb ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of stop.
  Unpacking prosody (0.10~hg745e0a783055-2) over (0.9.12-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/prosody_0.10~hg745e0a783055-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is also in 
package prosody-modules 0.0~hg20170123.3ed504b944e5+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Errors were encountered while processing:
   /var/cache/apt/archives/prosody_0.10~hg745e0a783055-2_amd64.deb


cheers,

Andreas


prosody-modules=0.0~hg20170123.3ed504b944e5+dfsg-1_prosody=0.10~hg745e0a783055-2.log.gz
Description: application/gzip

Bug#867676: libengine-pkcs11-openssl: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/engines-1.1/pkcs11.la

[Andreas Beckmann]

Package: libengine-pkcs11-openssl
Version: 0.4.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libengine-pkcs11-openssl:amd64.
  Preparing to unpack .../libengine-pkcs11-openssl_0.4.4-2_amd64.deb ...
  Unpacking libengine-pkcs11-openssl:amd64 (0.4.4-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libengine-pkcs11-openssl_0.4.4-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/engines-1.1/pkcs11.la', which 
is also in package libengine-pkcs11-openssl1.1:amd64 0.4.4-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libengine-pkcs11-openssl_0.4.4-2_amd64.deb


cheers,

Andreas


libengine-pkcs11-openssl1.1=0.4.4-4_libengine-pkcs11-openssl=0.4.4-2.log.gz
Description: application/gzip

Bug#867675: texlive-binaries: typo in Breaks: texiive-lang-japanese (<< 2017)

[Andreas Beckmann]

Package: texlive-binaries
Version: 2017.20170613.44572-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

makes files disappear on partial upgrades ...


Andreas

Bug#865678: knot: Improper TSIG validity period check can allow TSIG forgery

[Salvatore Bonaccorso]

Control: retitle -1 knot: CVE-2017-11104: Improper TSIG validity period check 
can allow TSIG forgery

On Fri, Jun 23, 2017 at 07:01:49PM +0200, Salvatore Bonaccorso wrote:
> Source: knot
> Version: 2.4.3-1
> Severity: grave
> Tags: security upstream patch
> Control: found -1 2.5.1-1
> 
> Hi
> 
> See
> https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
> and
> http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
> and filling a bug in BTS to have a reference, afaik there is no CVE
> yet assigned.
> 
> [16:19] < KGB-1> Yves-Alexis Perez 52846  /data/CVE/list add temporary entry 
> for knot
> [16:21] < Corsac> ondrej: I guess you know about it?
> 
> Please adjust the affected versions in the BTS as needed.

This now was assigned CVE-2017-11104.

Regards,
Salvatore

Processed: Re: Bug#865678: knot: Improper TSIG validity period check can allow TSIG forgery

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 knot: CVE-2017-11104: Improper TSIG validity period check can 
> allow TSIG forgery
Bug #865678 [src:knot] knot: Improper TSIG validity period check can allow TSIG 
forgery
Changed Bug title to 'knot: CVE-2017-11104: Improper TSIG validity period check 
can allow TSIG forgery' from 'knot: Improper TSIG validity period check can 
allow TSIG forgery'.

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

Processed: Bug#867633 marked as pending

[Debian Bug Tracking System]

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

> tag 867633 pending
Bug #867633 {Done: Christos Trochalakis } 
[src:python-confluent-kafka] python-confluent-kafka: missing build dependency 
on python3-all-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867633: marked as pending

[Christos Trochalakis]

tag 867633 pending
thanks

Hello,

Bug #867633 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:


https://anonscm.debian.org/cgit/python-modules/packages/python-confluent-kafka.git/commit/?id=bb02365

---
commit bb02365c7f998eeb3cb5fae373aa3132836d3a8a
Author: Christos Trochalakis 
Date:   Sat Jul 8 14:37:42 2017 +0300

Release 0.9.4-3

diff --git a/debian/changelog b/debian/changelog
index fa8e27b..2f670fb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-confluent-kafka (0.9.4-3) unstable; urgency=medium
+
+  * Properly Build-Depend on python*-all-dev (Closes: #867633)
+
+ -- Christos Trochalakis   Sat, 08 Jul 2017 14:37:20 
+0300
+
 python-confluent-kafka (0.9.4-2) unstable; urgency=medium
 
   * Switch to debhelper 10.

Bug#867672: starpy: missing build dependency on python-setuptools

[Adrian Bunk]

Source: starpy
Version: 1.0.1.0.git.20151124-1.1
Severity: serious
Tags: buster sid

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

...
   dh_auto_clean
python setup.py clean -a
Traceback (most recent call last):
  File "setup.py", line 18, in 
from setuptools import setup, find_packages
ImportError: No module named setuptools
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:11: recipe for target 'clean' failed
make: *** [clean] Error 1

Bug#867633: marked as done (python-confluent-kafka: missing build dependency on python3-all-dev)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 12:05:42 +
with message-id 
and subject line Bug#867633: fixed in python-confluent-kafka 0.9.4-3
has caused the Debian Bug report #867633,
regarding python-confluent-kafka: missing build dependency on python3-all-dev
to be marked as done.

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

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


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-confluent-kafka.html

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.6m -c confluent_kafka/src/confluent_kafka.c -o 
build/temp.linux-amd64-3.6/confluent_kafka/src/confluent_kafka.o
In file included from confluent_kafka/src/confluent_kafka.c:17:0:
confluent_kafka/src/confluent_kafka.h:17:20: fatal error: Python.h: No such 
file or directory
 #include 
^
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.6 setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 3.6 3.5 returned exit code 
13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: python-confluent-kafka
Source-Version: 0.9.4-3

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

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

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

Debian distribution maintenance software
pp.
Christos Trochalakis  (supplier of updated 
python-confluent-kafka 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, 08 Jul 2017 14:37:20 +0300
Source: python-confluent-kafka
Binary: python-confluent-kafka python3-confluent-kafka
Architecture: source
Version: 0.9.4-3
Distribution: unstable
Urgency: medium
Maintainer: Christos Trochalakis 
Changed-By: Christos Trochalakis 
Description:
 python-confluent-kafka - Python client to interact with Kafka - Python 2.7
 python3-confluent-kafka - Python client to interact with Kafka - Python 3.x
Closes: 867633
Changes:
 python-confluent-kafka (0.9.4-3) unstable; urgency=medium
 .
   * Properly Build-Depend on python*-all-dev (Closes: #867633)
Checksums-Sha1:
 6b6bf7f5c53e4bb8d9c954d11fd1f669e001694d 2302 
python-confluent-kafka_0.9.4-3.dsc
 31a385f7728e4fad06d5e1c08bce94034eed0610 2580 
python-confluent-kafka_0.9.4-3.debian.tar.xz
 1605af6878ce191b051dfe7bc1ff06806caa1ae8 8977 
python-confluent-kafka_0.9.4-3_amd64.buildinfo
Checksums-Sha256:
 65ace98b6f0c49a9fa2c4308cc90ac6f621afafd423e798be2006fb43c42cb58 2302 
python-confluent-kafka_0.9.4-3.dsc
 5da68192c0ef745b8567277d447c5d7926a1aad05df47c838e06818575e3fe69 2580 
python-confluent-kafka_0.9.4-3.debian.tar.xz
 5af135dce2aef2f47eb7cb1f012a251f5834e5f9374140c07f7696ceeb547dbb 8977 
python-confluent-kafka_0.9.4-3_amd64.buildinfo
Files:
 c301490e47d7f19d597b4f492d661637 2302 python optional 
python-confluent-kafka_0.9.4-3.dsc
 4636f3451d7f22368410675d2397ca11 2580 python optional 
python-confluent-kafka_0.9.4-3.debian.tar.xz
 6eaec65b494af12801ffc51b5b11dabb 8977 python optional 
python-confluent-kafka_0.9.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEf2SPbCEjyY+zKcgrETYmAKdH7NkFAllgxIIACgkQETYmAKdH
7NnZ4RAArV7eiFNjX6DpgIPyEH1NoLIg8pPpEMIXyGBDC3okuysofs9srWNy2+KA
/vXTkjSwtZkjyVbkG6zb4qL4UKbaZ7H0asd3PnQqZgCg8F2LsGWxuTIo+Ub+iHTh
v5rK0zl4PnDk/+SZdNoY3QQIl++8M6cUunJ8nua6sF6U+r7ajkVCkC/LB/09hXOm
KbVNf7onBRGv8A6LRQY33cZWOlOF7XYBVmibkiJZ5k8GIlZwpmbtgvl5ZjtuE5/E
wsQwT6j7aYsScCy0no16kf17BkRa+p075yDC6dpCB6jb68wFgtCdRyqP+LmDc6+8
uesxJrD78UbJ6qRqmTVyqabmkUDGyXhvygQZx5GHyoMA1o8B1tg+yeKgO7L1x+tz

Bug#867671: libratbag-tools: removal of libratbag-tools/sid makes files disappear from liblur3/testing

[Andreas Beckmann]

Package: libratbag-tools
Version: 0.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install liblur3/testing
  # (1)
  apt-get install libratbag-tools/sid
  apt-get remove libratbag-tools
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/man/man1/lur-command.1.gz

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The libratbag-tools package has the following relationships with liblur3:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  liblur3 (<< 0.9-1)
  Depends:   liblur3 (>= 0.4)

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

 ERROR: FAIL: After purging files have disappeared:
  /usr/share/man/man1/lur-command.1.gz   owned by: libratbag-tools

0m15.7s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/liblur3:amd64.list  not owned


cheers,

Andreas


liblur3=0.5-2_libratbag-tools=0.9-2.log.gz
Description: application/gzip

Bug#867670: libpng1.6 FTBFS on arm*:

[Adrian Bunk]

Source: libpng1.6
Version: 1.6.30-1
Severity: serious

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

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c arm/filter_neon.S  
-fPIC -DPIC -o arm/.libs/filter_neon.o
arm/../pngpriv.h: Assembler messages:
arm/../pngpriv.h:476: Error: unknown mnemonic `typedef' -- `typedef unsigned 
long png_ptruint'
Makefile:1156: recipe for target 'arm/filter_neon.lo' failed
make[2]: *** [arm/filter_neon.lo] Error 1
...

None of our ARM ports includes NEON in the architecture baseline.

Processed: astroquery FTBFS with python 3.6 as supported version

[Debian Bug Tracking System]

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

> forwarded 867502 https://github.com/astropy/astroquery/issues/952
Bug #867502 [src:astroquery] astroquery FTBFS with python 3.6 as supported 
version
Set Bug forwarded-to-address to 
'https://github.com/astropy/astroquery/issues/952'.
>
End of message, stopping processing here.

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

Bug#845497: marked as done (liblasi-dev: has packaging issues with dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 11:49:18 +
with message-id 
and subject line Bug#845497: fixed in lasi 1.1.0-2
has caused the Debian Bug report #845497,
regarding liblasi-dev: has packaging issues with dependencies
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.)


-- 
845497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblasi-dev
Version: 1.1.0-1.1
Severity: normal

Dear Maintainer,

The Depends: line for liblasi-dev is incomplete, i.e., only the
corresponding library package is mentioned now.  Although, I only have
the Debian stable version installed, I notice this bad situation
persists in the unstable version of this package (see
).

This package is linked to the pango/cairo subset of the GTK+ suite of
libraries so at minimum you should add the appropriate libpango
development package (libpango1.0-dev in sid) to the dependencies of this 
package.
That package in turn depends on libcairo2-dev (amongst many others)
which in turn depends on libfreetype6-dev (amongst many others).

As a result of this liblasi-dev dependency bug, one well-known PLplot
developer (Hazen Babcock) has recently reported a PLplot build bug on
Ubuntu due to this situation.  He had liblasi-dev installed, but not
libfreetype6-dev and the result was the following build error for the
psttf device driver (which depends on liblasi):

> Scanning dependencies of target psttf
> [ 20%] Building CXX object drivers/CMakeFiles/psttf.dir/psttf.cc.o
> In file included from
> /home/travis/build/HazenBabcock/PLplot/drivers/psttf.cc:44:0:
> /usr/include/LASi.h:14:30: fatal error: freetype/ftglyph.h: No such file or 
> directory
> compilation terminated.
> make[2]: *** [drivers/CMakeFiles/psttf.dir/psttf.cc.o] Error 1
> make[1]: *** [drivers/CMakeFiles/psttf.dir/all] Error 2
> make: *** [all] Error 2

Addressing this dependency issue for the liblasi-dev package should
solve this build bug (which of course can be worked around for now by
installing libfreetype6-dev and any other missing liblasi-dev direct
or indirect development package dependencies).

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

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

Versions of packages liblasi-dev depends on:
ii  liblasi0  1.1.0-1.1

liblasi-dev recommends no packages.

liblasi-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lasi
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated lasi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 14:19:16 +0300
Source: lasi
Binary: liblasi0 liblasi-dev
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 liblasi-dev - development files and documentation for the LASi library
 liblasi0   - creation of PostScript documents containing Unicode symbols
Closes: 845497
Changes:
 lasi (1.1.0-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #867050)
   * Add the missing libpango1.0-dev and libfreetype6-dev
 dependencies to liblasi-dev. (Closes: #845497)
   * Add ${misc:Depends} to the package dependencies.
Checksums-Sha1:
 792eec287642a59a08b87210d669793ee75099da 1966 lasi_1.1.0-2.dsc
 67213fe6b4469fd4e772101c651cbc4ffbf16f8d 4784 lasi_1.1.0-2.debian.tar.xz
Checksums-Sha256:
 226ba7aa8894478fb48cd7472be8e8dd0a51b5826d4ed628ef0bfd68481606ba 1966 
lasi_1.1.0-2.dsc
 

Bug#867581: libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report)

[Andreas Metzler]

On 2017-07-07 Andreas Metzler  wrote:
[...]
> Thanks for the bugreport. I will try to get this fixed via a stable
> update.

See https://bugs.debian.org/867659

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: Missing dependencies are RC

[Debian Bug Tracking System]

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

> severity 845497 serious
Bug #845497 [liblasi-dev] liblasi-dev: has packaging issues with dependencies
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 867031 confirmed
Bug #867031 [schleuder] schleuder: fails to upgrade wheezy -> jessie -> stretch 
-> buster
Added tag(s) confirmed.
>
End of message, stopping processing here.

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

Bug#866575: libapache2-mod-wsgi-py3: Impossible depends when built with more then one supported python3 version

[Bas Couwenberg]

Package: libapache2-mod-wsgi-py3
Version: 4.5.11-1
Followup-For: Bug #866575

Dear Maintainer,

The attached patch fixes this issue, but there are several other issues
with the package that should be fixed in the next upload too.

Kind Regards,

Bas
>From 4534ad18aaff225f87e7b3a33ec4ab3806e0f48b Mon Sep 17 00:00:00 2001
From: Bas Couwenberg 
Date: Sat, 8 Jul 2017 12:34:58 +0200
Subject: Fix min/max Python 3 version determination for multiple versions.
 (closes: #866575)

---
 debian/changelog | 8 
 debian/rules | 4 ++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index b398340..90e6bcc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+mod-wsgi (4.5.11-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix min/max Python 3 version determination for multiple versions.
+(closes: #866575)
+
+ -- Bas Couwenberg   Sat, 08 Jul 2017 12:33:46 +0200
+
 mod-wsgi (4.5.11-1) unstable; urgency=medium
 
   * [8d515a5] Merge tag 'upstream/4.5.11'
diff --git a/debian/rules b/debian/rules
index d39b22d..d536d9e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,8 +9,8 @@ PYMIN=$(shell echo $(PYVERS) | awk '{print $$1}')
 PYMAX=$(shell echo $(PYVERS) | LANG=C awk '{print $$NF+0.1}')
 PY3VERS=$(shell py3versions -vs)
 PY3DEFAULT=$(shell py3versions -dv)
-PY3MIN=$(shell echo $(PY3VERS) | awk '{print $$1}')
-PY3MAX=$(shell echo $(PY3VERS) | LANG=C awk '{print $$NF+0.1}')
+PY3MIN=$(shell for VERSION in $(PY3VERS); do echo $$VERSION; done | sort | 
head -1)
+PY3MAX=$(shell for VERSION in $(PY3VERS); do echo $$VERSION; done | sort | 
tail -1 | LANG=C awk '{print $$NF+0.1}')
 pkgdir = $(CURDIR)/debian/$(PACKAGE)$(if $(patsubst 3.%,,$(1)),,-py3)
 
 %:
-- 
2.11.0

Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

[Georg Faerber]

Hi Lucas,

Thanks for the report:

On 17-07-08 08:28:30, Lucas Nussbaum wrote:
>
> [...] 
>
> 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.

Was a wrapper used, like pbuilder or sbuild?

Thanks,
Georg


signature.asc
Description: Digital signature

Bug#867105: marked as done (utf8proc: build-depends unicode-data (< 9.1) but 10.0.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 09:30:41 +
with message-id 
and subject line Bug#867105: fixed in utf8proc 2.1.0-1
has caused the Debian Bug report #867105,
regarding utf8proc: build-depends unicode-data (< 9.1) but 10.0.0-1 is to be 
installed
to be marked as done.

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

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


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

# apt-get build-dep utf8proc
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:utf8proc : Depends: unicode-data (< 9.1) but 10.0.0-1 is to be 
installed
E: Unable to correct problems, you have held broken packages.
# 
--- End Message ---
--- Begin Message ---
Source: utf8proc
Source-Version: 2.1.0-1

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

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

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated utf8proc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 10:47:15 +0200
Source: utf8proc
Binary: libutf8proc2 libutf8proc-dev
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Julia Team 
Changed-By: Graham Inggs 
Description:
 libutf8proc-dev - C library for processing UTF-8 Unicode data (development 
files)
 libutf8proc2 - C library for processing UTF-8 Unicode data (shared library)
Closes: 867105
Changes:
 utf8proc (2.1.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch to unicode-data 10 (Closes: #867105)
   * Regenerate utf8proc_data.c from unicode-data 10
   * Update debian/libutf8proc2.symbols
   * Switch to debhelper 10
   * Enable all hardening flags
   * Bump Standards-Version to 4.0.0
   * Update copyright, use https
Checksums-Sha1:
 516c319dc9398295baa97fa922d575b55f7c58f7 2065 utf8proc_2.1.0-1.dsc
 2c4e949490820f53841dfc951c12b0a36dfbfa40 151842 utf8proc_2.1.0.orig.tar.gz
 d94fc78438359712ef052c1d85538abce8cd7323 15600 utf8proc_2.1.0-1.debian.tar.xz
Checksums-Sha256:
 def0db58c2ff73293a87eeb828ef1e3bd8a8c182799e76dc1750d99b29f0b528 2065 
utf8proc_2.1.0-1.dsc
 25ccc5619ac400f9eaf24aafaae5b625afa1961e140b8dd6072b393267833260 151842 
utf8proc_2.1.0.orig.tar.gz
 7e2268f6a39ae9a302c5cd915459c1a2d411b38e9e786d21e790c152f0dfa265 15600 
utf8proc_2.1.0-1.debian.tar.xz
Files:
 05e9e0b144593e9560ef7070ab4a600f 2065 libs optional utf8proc_2.1.0-1.dsc
 8ec2f58a12b3cec857881360b2b99952 151842 libs optional 
utf8proc_2.1.0.orig.tar.gz
 25c9d4041ee571f82ae7a3f929a775f5 15600 libs optional 
utf8proc_2.1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIvBAEBCgAZBQJZYJ1EEhxnaW5nZ3NAZGViaWFuLm9yZwAKCRCvz+yOZpzhwriX
EACEVU4UH+5+Wb8o70GP5JeLX7IDm1LAKLer9jCio+iGn591jonn+IWP8c5pEOP2
0XC2dKEsW75gvoomN2phKNhIwmPDNzE/LNwio8lBqcSQt7SE++Hvimc4rLD542ST
tptJzLQOIrce2kVdmW1MItlAKo1pU0bNQE+bltsTiSSUlH0C2306kwa6sacZclYj
DmDqisJZzJ+hXnNfR6/jx3VZb0u2noSz4l2kmdqyNfJJydJV8T5/4csrvXZPJGeZ
6lT8Gmdx9o2HDxGeOjLDNIz423w+qNHXAJ2/EGUXHw/mjGkWGCquokWiYHi3VPoC
Xr7a20nd5q7i/SZYF+uj665noTu51It4HnE3JG8Lw7pSmuebkgkJDRziVCvaQ8Pf
TM1sxMI5yaTesGQtUtpKcyU9YHpAdKPzT3HvpPtniO5KRp8aT2ew8+W4uf4GzhKv
qS6qagp/VBYyfx2kPM8FpLa6nJrH1Stfjkdya2wnN2OeOWfYJD+Oro2Lhk1ue652
dp38XIShLy55bXNwNXSdA9EVmEVJSFOGyuKArB+Yf/JWRJKUIY8PPUT9+eYhC7k4
tsZSditfwOgWuVR4vxXalNXo6WS8i0DIyxUQn8IPOC1JurWLWoz9KXht5tzQedTd
SLQCItW2FKOIrPmwxrgdJYr1nvwYLYei9aA5tDVwpZEyeQ==
=LU8q
-END PGP SIGNATURE End Message ---

Processed: The BTS gets confused since mdp is not built from src: mdp

[Debian Bug Tracking System]

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

> reassign 867515 python3-mdp
Bug #867515 [src:mdp] mdp FTBFS with python 3.6 as supported version
Bug reassigned from package 'src:mdp' to 'python3-mdp'.
No longer marked as found in versions mdp/3.5-1.
Ignoring request to alter fixed versions of bug #867515 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#867658: debian-parl FTBFS with shellcheck 0.4.6-1

[Adrian Bunk]

Source: debian-parl
Version: 1.9.10
Severity: serious

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

...
perl -0777 -n \
-e 's,.*d-i preseed/late_command string ,#!/bin/sh\n,ms' \
-e ' and print $_' \
content/desktop/preseed.cfg > parl-desktop-tidy
shellcheck -e SC1003 -e SC2016 -e SC2034 -e SC2046 -e SC2048 -e SC2086 
parl-desktop-tidy

In parl-desktop-tidy line 38:
  if [ -e "$1" ] && egrep -q "^#?$2\$" "$1"; then \
^-- SC2196: egrep is non-standard and deprecated. Use grep 
-E instead.


In parl-desktop-tidy line 49:
  if [ -e "$1" ] && egrep -q "^#?$2=" "$1"; then \
^-- SC2196: egrep is non-standard and deprecated. Use grep 
-E instead.

debian/blends.mk:87: recipe for target 'parl-desktop-tidy' failed
make: *** [parl-desktop-tidy] Error 1

Bug#865133: marked as done (ruby-redcarpet FTBFS on 32bit: Failure: test_utf8_only_header_anchors(HTMLRenderTest))

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 07:50:37 +
with message-id 
and subject line Bug#865133: fixed in ruby-redcarpet 3.4.0-2
has caused the Debian Bug report #865133,
regarding ruby-redcarpet FTBFS on 32bit: Failure: 
test_utf8_only_header_anchors(HTMLRenderTest)
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.)


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

https://buildd.debian.org/status/package.php?p=ruby-redcarpet=sid

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/«PKGBUILDDIR»/debian/ruby-redcarpet/usr/lib/i386-linux-gnu/ruby/vendor_ruby/2.3.0:/«PKGBUILDDIR»/debian/ruby-redcarpet/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-redcarpet/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/i386-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -I"lib:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/*_test.rb" 
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
...F
===
Failure: test_utf8_only_header_anchors(HTMLRenderTest)
/«PKGBUILDDIR»/test/html_render_test.rb:259:in `test_utf8_only_header_anchors'
 256: markdown = "# 見出し"
 257: html = "見出し"
 258: 
  => 259: assert_equal html, render(markdown, with: [:with_toc_data])
 260:   end
 261: 
 262:   def test_escape_entities_removal_from_anchor
<"見出し"> expected but was
<"見出し">

diff:
? 見出し
===
.F
===
Failure:
   expected to be =~
  <"\n\nA title\n\n\nA nice subtitle\n\n\nAnother one\n\n\nA sub-sub-title\n\n\n見出し\n\n\n\n\n\n">.
test_toc_heading_id(HTMLTOCRenderTest)
/«PKGBUILDDIR»/test/html_toc_render_test.rb:43:in `test_toc_heading_id'
 40: assert_match /a-nice-subtitle/, output
 41: assert_match /another-one/, output
 42: assert_match /a-sub-sub-title/, output
  => 43: assert_match /part-37870bfa194139f/, output
 44:   end
 45: 
 46:   def test_toc_heading_with_hyphen_and_equal
===
...
.

Finished in 0.643828262 seconds.
--
126 tests, 178 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
98.4127% passed
--
195.70 tests/s, 276.47 assertions/s
rake aborted!
Command failed with status (1): [ruby -I"lib:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/*_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-redcarpet 
returned exit code 1
debian/rules:6: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-redcarpet
Source-Version: 3.4.0-2

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated ruby-redcarpet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jul 2017 09:25:10 +0200
Source: ruby-redcarpet
Binary: ruby-redcarpet
Architecture: source
Version: 3.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Processed: Bug#865133 marked as pending

[Debian Bug Tracking System]

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

> tag 865133 pending
Bug #865133 [src:ruby-redcarpet] ruby-redcarpet FTBFS on 32bit: Failure: 
test_utf8_only_header_anchors(HTMLRenderTest)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865133: marked as pending

[Lucas Nussbaum]

tag 865133 pending
thanks

Hello,

Bug #865133 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:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-redcarpet.git/commit/?id=5a08455

---
commit 5a084558d059bf6882b8cdf8f1f06eb6160d8f77
Author: Lucas Nussbaum 
Date:   Sat Jul 8 09:27:03 2017 +0200

Prepare changelog

diff --git a/debian/changelog b/debian/changelog
index 6d087ad..3e26f7a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ruby-redcarpet (3.4.0-2) unstable; urgency=medium
+
+  * Team upload.
+  * Add patch fix-test-suite-on-32b-arch.patch. Closes: #865133
+
+ -- Lucas Nussbaum   Sat, 08 Jul 2017 09:25:10 +0200
+
 ruby-redcarpet (3.4.0-1) unstable; urgency=medium
 
   * Team upload.
@@ -5,7 +12,7 @@ ruby-redcarpet (3.4.0-1) unstable; urgency=medium
   * Bump Standard-Version:3.9.8
   * Remove patch call-the-right-ruby.patch (incorporated upstream)
   * Remove patch fix_test_no_rewind_into_previous_inline.patch
-(incorporated upstream)   
+(incorporated upstream)
 
  -- Abhijith PA   Sat, 17 Jun 2017 10:09:36 +0530
 

Bug#866629: debian-installer: Installer showes Debootstrap Error debian stretch live installation

[Pirate Praveen]

On Thu, 6 Jul 2017 00:35:21 +0530 Prahlad Yeri 
wrote:
> Can confirm this bug on the live installer - tried both XFCE and LXDE
> versions.
> 
> Never expected such goof up on a debian stable version!

I agree it was a let down and frustrating.

> Granted that its just released, but we do go through ages of testing
> before reaching stable, don't we? The reason a user comes to debian in
> the first place is stability. If you don't even get that, then what is
> the rationale for using debian stable against something like Ubuntu LTS
> where you get both stability and newer packages?

The reason why debian is stable is because of the extensive testing.
Unfortunately the live installer did not receive the extensive testing
as the regular installer or the rest of debian. Only live installer had
this problem and if more people volunteer to test pre-releases of live
installer, we can avoid the situation in future.



signature.asc
Description: OpenPGP digital signature

Processed: Makes planet not work at all

[Debian Bug Tracking System]

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

> severity 845987 serious
Bug #845987 [planet-venus] planet-venus: Fails with html5lib 0.9-1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#867651: ruby-rubymail: FTBFS: ERROR: Test "ruby2.3" failed.

[Lucas Nussbaum]

Source: ruby-rubymail
Version: 1.1.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-rubymail/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"rmail\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-rubymail/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -w -I"."  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/testaddress.rb" 
> "test/testbase.rb" "test/testheader.rb" "test/testmailbox.rb" 
> "test/testmboxreader.rb" "test/testmessage.rb" "test/testparser.rb" 
> "test/testparsermultipart.rb" "test/testpushbackreader.rb" 
> "test/testserialize.rb" "test/testtestbase.rb" "test/testtranspparency.rb" -v
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:664:
>  warning: character class has duplicated range: 
> /\A[\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:706:
>  warning: character class has duplicated range: 
> /\A[\x80-\xff\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:474:
>  warning: shadowing outer local variable - name
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:474:
>  warning: shadowing outer local variable - value
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:507:
>  warning: shadowing outer local variable - name
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:507:
>  warning: shadowing outer local variable - value
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:509:
>  warning: assigned but unused variable - found
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/header.rb:892:
>  warning: optional boolean argument is obsoleted
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/message.rb:133:
>  warning: optional boolean argument is obsoleted
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/message.rb:140:
>  warning: optional boolean argument is obsoleted
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/parser.rb:205:
>  warning: assigned but unused variable - pushback
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/serialize.rb:77:
>  warning: assigned but unused variable - delimiters_boundary
> Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
> Started
> TestBase: 
>   test_nothing:   .: (0.000482)
>   TestRMailAddress: 
> test_bug_23043:   
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:664:
>  warning: character class has duplicated range: 
> /\A[\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> .: (0.001371)
> test_comments:.: (0.000349)
> test_domain_literal:  .: (0.002962)
> test_exhaustive:  .: (0.227276)
> test_initialize:  .: (0.000842)
> test_invalid_addresses:   
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:664:
>  warning: character class has duplicated range: 
> /\A[\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> .: (0.001094)
> test_mailtools_suite: 
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:664:
>  warning: character class has duplicated range: 
> /\A[\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> .: (0.012168)
> test_majordomoII: .: (0.005281)
> test_misc_addresses:  .: (0.006986)
> test_out_of_spec: .: (0.002300)
> test_random_strings:  
> /<>/debian/ruby-rubymail/usr/lib/ruby/vendor_ruby/rmail/address.rb:664:
>  warning: character class has duplicated range: 
> /\A[\w!$%&\'*+\/=?^_\`{\}|~#-]+/
> .: (0.115439)
>   

Bug#867653: ruby-license-finder: FTBFS: ERROR: Test "ruby2.3" failed: /etc/ssl/certs/T?RKTRUST_Elektronik_Sertifika_Hizmet_Sa?lay?c?s?_H5.pem (No such file or directory)

[Lucas Nussbaum]

Source: ruby-license-finder
Version: 2.1.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   /etc/ssl/certs/T?RKTRUST_Elektronik_Sertifika_Hizmet_Sa?lay?c?s?_H5.pem (No 
> such file or directory)
> Adding debian:QuoVadis_Root_CA_2.pem
> Adding debian:AffirmTrust_Networking.pem
> Adding debian:Izenpe.com.pem
> Adding debian:AddTrust_Low-Value_Services_Root.pem
> Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
> Adding debian:DigiCert_Assured_ID_Root_CA.pem
> Adding debian:Equifax_Secure_eBusiness_CA_1.pem
> Adding debian:Starfield_Class_2_CA.pem
> Adding debian:Taiwan_GRCA.pem
> Adding debian:GeoTrust_Global_CA_2.pem
> Adding debian:DST_ACES_CA_X6.pem
> Adding debian:OpenTrust_Root_CA_G2.pem
> Adding debian:Trustis_FPS_Root_CA.pem
> Adding debian:GlobalSign_Root_CA_-_R3.pem
> Adding debian:Comodo_Secure_Services_root.pem
> Adding debian:COMODO_Certification_Authority.pem
> Adding debian:ComSign_CA.pem
> Adding debian:S-TRUST_Universal_Root_CA.pem
> Adding 
> debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
> done.
> Setting up dh-autoreconf (14) ...
> Setting up python3 (3.5.3-3) ...
> Setting up ruby-test-unit (3.2.5-1) ...
> Setting up rake (12.0.0-1) ...
> Setting up antlr (2.7.7+dfsg-7) ...
> Setting up devscripts (2.17.6) ...
> Setting up dh-strip-nondeterminism (0.035-2) ...
> Setting up ant (1.9.9-4) ...
> Setting up bnd (2.4.1-6) ...
> Setting up junit4 (4.12-4) ...
> Setting up ivy (2.4.0-3) ...
> Setting up libruby2.3:amd64 (2.3.3-1) ...
> Setting up default-jre-headless (2:1.8-59) ...
> Setting up debhelper (10.6.2) ...
> Setting up groovy (2.4.8-1) ...
> update-alternatives: using /usr/share/groovy/bin/groovy to provide 
> /usr/bin/groovy (groovy) in auto mode
> update-alternatives: using /usr/share/groovy/bin/groovyc to provide 
> /usr/bin/groovyc (groovyc) in auto mode
> update-alternatives: using /usr/share/groovy/bin/grape to provide 
> /usr/bin/grape (grape) in auto mode
> update-alternatives: using /usr/share/groovy/bin/startGroovy to provide 
> /usr/bin/startGroovy (startGroovy) in auto mode
> update-alternatives: using /usr/share/groovy/bin/groovysh to provide 
> /usr/bin/groovysh (groovysh) in auto mode
> update-alternatives: using /usr/share/groovy/bin/java2groovy to provide 
> /usr/bin/java2groovy (java2groovy) in auto mode
> update-alternatives: using /usr/share/groovy/bin/groovyConsole to provide 
> /usr/bin/groovyConsole (groovyConsole) in auto mode
> update-alternatives: using /usr/share/groovy/bin/groovydoc to provide 
> /usr/bin/groovydoc (groovydoc) in auto mode
> Setting up ant-optional (1.9.9-4) ...
> Setting up ruby2.3 (2.3.3-1) ...
> Setting up libmsv-java (2009.1+dfsg1-5) ...
> Setting up ruby2.3-dev:amd64 (2.3.3-1) ...
> Setting up libxbean-java (4.5-4) ...
> Setting up libgradle-core-java (3.2.1-1) ...
> Setting up ruby (1:2.3.3) ...
> Setting up ruby-erubis (2.7.0-3) ...
> Setting up ruby-progressbar (1.4.2-1) ...
> Setting up ruby-xml-simple (1.1.5-1) ...
> Setting up ruby-diff-lcs (1.3-1) ...
> Setting up ruby-escape-utils (1.1.0-1+b2) ...
> Setting up ruby-http-parser.rb (0.6.0-3+b3) ...
> Setting up gem2deb-test-runner (0.34) ...
> Setting up libplexus-containers-java (1.0~beta3.0.7-8) ...
> Setting up ruby-fakefs (0.6.7-1) ...
> Setting up ruby-zip (1.2.1-1) ...
> Setting up libdom4j-java (1.6.1+dfsg.3-2) ...
> Setting up ruby-thor (0.19.4-1) ...
> Setting up ruby-safe-yaml (1.0.4-1) ...
> Setting up libplexus-io-java (1.0~alpha5-2) ...
> Setting up ruby-rack (1.6.4-4) ...
> Setting up ruby-crack (0.4.3-1) ...
> Setting up libplexus-interactivity-api-java (1.0-alpha-6-7) ...
> Setting up ruby-unf-ext (0.0.7.2-3) ...
> Setting up ruby-all-dev:amd64 (1:2.3.3) ...
> Setting up ruby-addressable (2.4.0-1) ...
> Setting up ruby-net-http-persistent (2.9.4-1) ...
> Setting up libplexus-container-default1.5-java (1.7.1-3) ...
> Setting up ruby-multi-json (1.12.1-1) ...
> Setting up ruby-method-source (0.8.2-2) ...
> Setting up ruby-pkg-config (1.1.7-1) ...
> Setting up ruby-rack-test (0.6.3-1) ...
> Setting up ruby-thread-order (1.1.0-1) ...
> Setting up ruby-rspec-support (3.5.0c3e0m0s0-1) ...
> Setting up ruby-hashdiff (0.2.3-1) ...
> Setting up ruby-coderay (1.1.1-1) ...
> Setting up libwagon-java (1.0.0-9) ...
> Setting up ruby-eventmachine (1.0.7-4) ...
> Setting up ruby-setup (3.4.1-9) ...
> Setting up libplexus-cli-java (1.2-5) ...
> Setting up ruby-ffi (1.9.10debian-1+b2) ...
> Setting up libmaven-resolver-java (1.0.3-1) ...
> Setting up ruby-multi-xml (0.5.5-2) ...
> Setting up libplexus-archiver-java (2.2-1) ...
> Setting up ruby-launchy-shim (2.3.0.1) ...
> Setting up ruby-cookiejar (0.3.3-1) ...
> Setting up ruby-unf (0.1.4-2) ...
> Setting up libmaven2-core-java (2.2.1-27) ...
> Setting up pry (0.10.3-2) ...
> Setting up 

Bug#867655: ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request)

[Lucas Nussbaum]

Source: ruby-gemnasium-gitlab-service
Version: 0.2.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: @connection.request(request)
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: POST 
> https://api.gemnasium.com/v1/test_path with body '{"foo":"bar"}' with headers 
> {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:post, "https://api.gemnasium.com/v1/test_path;).
>  with(body: "{\"foo\":\"bar\"}",
>   headers: {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:post, 
> "https://X:secret_api_...@api.gemnasium.com/v1/test_path;).
>  with(body: {"foo"=>"bar"},
>   headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
>stub_request(:get, 
> "https://X:secret_api_...@api.gemnasium.com/v1/test_path;).
>  with(headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
>stub_request(:post, 
> "https://X:secret_api_...@api.gemnasium.com/v1/projects/project_slug/dependency_files;).
>  with(headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
> 
>
>  # ./lib/gemnasium/gitlab_service/connection.rb:28:in `post'
>  # ./spec/gemnasium/gitlab_service/connection_spec.rb:25:in `block (3 
> levels) in '
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/gemnasium/gitlab_service/client_spec.rb:11:in `block (3 
> levels) in '.
> 
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly 
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
> enable `:should` instead. Called from 
> /<>/spec/gemnasium/gitlab_service/pusher_spec.rb:8:in `block (2 
> levels) in '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 2 deprecation warnings total
> 
> Finished in 0.02929 seconds (files took 0.65037 seconds to load)
> 8 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/gemnasium/gitlab_service/client_spec.rb:30 # 
> Gemnasium::GitlabService::Client upload_files issues a POST request
> rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:18 # 
> Gemnasium::GitlabService::Connection get issues a GET request
> rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:27 # 
> Gemnasium::GitlabService::Connection post issues a POST request
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/2017/07/07/ruby-gemnasium-gitlab-service_0.2.6-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#867656: ruby-mixlib-install: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: res = http.request(request)

[Lucas Nussbaum]

Source: ruby-mixlib-install
Version: 1.1.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   Failure/Error: res = http.request(request)
> 
>   WebMock::NetConnectNotAllowedError:
> Real HTTP connections are disabled. Unregistered request: GET 
> https://bintray.com/api/v1/packages/chef/stable/chefdk/versions/0.7.0/files 
> with headers {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic 
> bWl4bGliLWluc3RhbGxAY2hlZjphODNkM2EyZmZhZDUwZWI5YTIyMzBmMjgxYTJlMTliNzBmZTBkYjJk',
>  'User-Agent'=>'Ruby'}
> 
> You can stub this request with the following snippet:
> 
> stub_request(:get, 
> "https://bintray.com/api/v1/packages/chef/stable/chefdk/versions/0.7.0/files;).
>   with(headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic 
> bWl4bGliLWluc3RhbGxAY2hlZjphODNkM2EyZmZhZDUwZWI5YTIyMzBmMjgxYTJlMTliNzBmZTBkYjJk',
>  'User-Agent'=>'Ruby'}).
>   to_return(status: 200, body: "", headers: {})
> 
> registered request stubs:
> 
> stub_request(:get, 
> "https://mixlib-install%40chef:a83d3a2ffad50eb9a2230f281a2e19b70fe0d...@bintray.com/api/v1/packages/chef/stable/chefdk/versions/0.7.0/files;).
>   with(headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'User-Agent'=>'Ruby'})
> stub_request(:get, 
> "https://mixlib-install%40chef:a83d3a2ffad50eb9a2230f281a2e19b70fe0d...@bintray.com/api/v1/packages/chef/stable/chefdk/versions/0.3.0/files;).
>   with(headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'User-Agent'=>'Ruby'})
> stub_request(:get, 
> "https://mixlib-install%40chef:a83d3a2ffad50eb9a2230f281a2e19b70fe0d...@bintray.com/api/v1/packages/chef/stable/chefdk/versions/0.16.28/files;).
>   with(headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'User-Agent'=>'Ruby'})
> stub_request(:get, 
> "https://mixlib-install%40chef:a83d3a2ffad50eb9a2230f281a2e19b70fe0d...@bintray.com/api/v1/packages/chef/stable/chefdk/versions/_latest;).
>   with(headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'User-Agent'=>'Ruby'})
> 
> 
>   # ./lib/mixlib/install/backend/bintray.rb:71:in `bintray_get'
>   # ./lib/mixlib/install/backend/bintray.rb:96:in `available_artifacts'
>   # ./lib/mixlib/install/backend/base.rb:44:in `info'
>   # ./lib/mixlib/install/backend.rb:31:in `info'
>   # ./lib/mixlib/install.rb:46:in `artifact_info'
>   # ./lib/mixlib/install.rb:100:in `upgrade_available?'
>   # ./spec/mixlib/install_spec.rb:137:in `block (4 levels) in  (required)>'
> 
> Finished in 0.18617 seconds (files took 0.65727 seconds to load)
> 106 examples, 10 failures, 24 pending
> 
> Failed examples:
> 
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:82 # 
> Mixlib::Install::Backend::Bintray for chef/stable with :latest version 
> returns all artifacts
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:91 # 
> Mixlib::Install::Backend::Bintray for chef/stable with :latest version with 
> platform info returns a single artifact with correct info
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:111 # 
> Mixlib::Install::Backend::Bintray for a product without native 64-bit builds 
> returns 32 bit package for 64 bit
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:125 # 
> Mixlib::Install::Backend::Bintray for a product with native 64-bit builds 
> returns 64 bit package for 64 bit
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:185 # 
> Mixlib::Install::Backend::Bintray for a version with unique solaris 
> publishing values finds an artifact
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:254 # 
> Mixlib::Install::Backend::Bintray for a missing version of a product raises 
> an error
> rspec ./spec/mixlib/install/backend/bintray_spec.rb:267 # 
> Mixlib::Install::Backend::Bintray for compliance uses product package name
> rspec ./spec/mixlib/install_spec.rb:114 # Mixlib::Install checking for 
> upgrades with :latest, upgrade exists, :stable channel should report upgrade 
> available
> rspec ./spec/mixlib/install_spec.rb:125 # Mixlib::Install checking for 
> upgrades with specific version lower than current, :stable channel should 
> report upgrade available
> rspec ./spec/mixlib/install_spec.rb:136 # Mixlib::Install checking for 
> upgrades with specific version higher than current, :stable channel should 
> report upgrade available
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> 

Bug#867650: berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean? Berkshelf::NullFormatter (NameError)

[Lucas Nussbaum]

Source: berkshelf
Version: 4.3.5-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> Did you mean?  Berkshelf::NullFormatter (NameError)
> ./lib/berkshelf.rb:164:in `const_get'
> ./lib/berkshelf.rb:164:in `set_format'
> ./lib/berkshelf/cli.rb:78:in `initialize'
> ./lib/berkshelf/cli.rb:49:in `dispatch'
> ./lib/berkshelf/cli.rb:27:in `execute!'
> ./features/step_definitions/utility_steps.rb:6:in `/the output from 
> ./features/step_definitions/utility_steps.rb:6:in 
> (.+)./features/step_definitions/utility_steps.rb:6:in  should be the same as 
> ./features/step_definitions/utility_steps.rb:6:in 
> (.+)./features/step_definitions/utility_steps.rb:6:in /'
> features/help.feature:9:in `Then the output from `berks cookbook -h` should 
> be the same as `berks help cookbook`'
> features/help.feature:3:in `Then the output from `` should be the 
> same as ``'
> 
> Failing Scenarios:
> cucumber features/help.feature:6 # Scenario Outline: Using various help 
> switches, Examples (#1)
> cucumber features/help.feature:7 # Scenario Outline: Using various help 
> switches, Examples (#2)
> cucumber features/help.feature:8 # Scenario Outline: Using various help 
> switches, Examples (#3)
> cucumber features/help.feature:9 # Scenario Outline: Using various help 
> switches, Examples (#4)
> 
> 146 scenarios (4 failed, 142 passed)
> 823 steps (4 failed, 819 passed)
> 0m9.671s
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/berkshelf_4.3.5-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#867654: ruby-omniauth-crowd: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req)

[Lucas Nussbaum]

Source: ruby-omniauth-crowd
Version: 2.2.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: http.request(req)
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: POST 
> https://crowd.example.org/rest/usermanagement/latest/authentication?username=foo
>  with body '
>  ba
>' with headers {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic Ym9ndXNfYXBwOmJvZ3VzX2FwcF9wYXNzd29yZA==', 
> 'Content-Type'=>'application/xml', 'User-Agent'=>'Ruby'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:post, 
> "https://crowd.example.org/rest/usermanagement/latest/authentication?username=foo;).
>  with(body: "\n  ba\n",
>   headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic Ym9ndXNfYXBwOmJvZ3VzX2FwcF9wYXNzd29yZA==', 
> 'Content-Type'=>'application/xml', 'User-Agent'=>'Ruby'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:post, 
> "https://bogus_app:bogus_app_passw...@crowd.example.org/rest/usermanagement/latest/authentication?username=foo;)
> 
>
>  # ./lib/omniauth/strategies/crowd/crowd_validator.rb:90:in `block in 
> make_request'
>  # ./lib/omniauth/strategies/crowd/crowd_validator.rb:83:in `make_request'
>  # ./lib/omniauth/strategies/crowd/crowd_validator.rb:99:in 
> `make_authorization_request'
>  # ./lib/omniauth/strategies/crowd/crowd_validator.rb:61:in 
> `retrieve_user_info!'
>  # ./lib/omniauth/strategies/crowd/crowd_validator.rb:24:in `user_info'
>  # ./lib/omniauth/strategies/crowd.rb:41:in `callback_phase'
>  # ./spec/omniauth/strategies/crowd_spec.rb:154:in `block (3 levels) in 
> '
> 
> Finished in 0.09906 seconds (files took 0.71987 seconds to load)
> 14 examples, 7 failures
> 
> Failed examples:
> 
> rspec ./spec/omniauth/strategies/crowd_spec.rb:99 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using authentication endpoint should call through to the 
> master app
> rspec ./spec/omniauth/strategies/crowd_spec.rb:102 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using authentication endpoint should have an auth hash
> rspec ./spec/omniauth/strategies/crowd_spec.rb:106 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using authentication endpoint should have good data
> rspec ./spec/omniauth/strategies/crowd_spec.rb:128 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using session endpoint should call through to the master app
> rspec ./spec/omniauth/strategies/crowd_spec.rb:133 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using session endpoint should have an auth hash
> rspec ./spec/omniauth/strategies/crowd_spec.rb:138 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials can be 
> successful when using session endpoint should have good data
> rspec ./spec/omniauth/strategies/crowd_spec.rb:156 # 
> OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials will 
> fail should fail
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/2017/07/07/ruby-omniauth-crowd_2.2.3-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#867649: ruby-flowdock: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: resp = self.class.delete(api_url(path), :basic_auth => {:username => @api_token, :password => ''}, :headers => headers)

[Lucas Nussbaum]

Source: ruby-flowdock
Version: 0.7.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: resp = self.class.delete(api_url(path), :basic_auth => 
> {:username => @api_token, :password => ''}, :headers => headers)
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: DELETE 
> https://api.flowdock.com/v1/some_path with headers 
> {'Accept'=>'application/json', 'Authorization'=>'Basic 
> NWJmYmJmZjk1ODEzMWFjNzo=', 'Content-Type'=>'application/json'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:delete, "https://api.flowdock.com/v1/some_path;).
>  with(headers: {'Accept'=>'application/json', 'Authorization'=>'Basic 
> NWJmYmJmZjk1ODEzMWFjNzo=', 'Content-Type'=>'application/json'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:delete, 
> "https://5bfbbff958131ac7:@api.flowdock.com/v1/some_path;).
>  with(headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json'})
> 
>
>  # ./lib/flowdock.rb:188:in `delete'
>  # ./spec/flowdock_spec.rb:460:in `block (4 levels) in '
> 
> Deprecation Warnings:
> 
> Using `should_not` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from /<>/spec/flowdock_spec.rb:6:in 
> `block (3 levels) in '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 0.06967 seconds (files took 0.66419 seconds to load)
> 39 examples, 8 failures
> 
> Failed examples:
> 
> rspec ./spec/flowdock_spec.rb:379 # Flowdock::Client with api_token posting 
> to chat posts to /messages
> rspec ./spec/flowdock_spec.rb:388 # Flowdock::Client with api_token posting 
> to chat posts to /comments
> rspec ./spec/flowdock_spec.rb:397 # Flowdock::Client with api_token posting 
> to chat posts to /private/:user_id/messages
> rspec ./spec/flowdock_spec.rb:417 # Flowdock::Client with api_token posting 
> to chat handles error responses
> rspec ./spec/flowdock_spec.rb:428 # Flowdock::Client with api_token GET does 
> abstract get with params
> rspec ./spec/flowdock_spec.rb:437 # Flowdock::Client with api_token POST does 
> abstract post with body
> rspec ./spec/flowdock_spec.rb:447 # Flowdock::Client with api_token PUT does 
> abstract put with body
> rspec ./spec/flowdock_spec.rb:456 # Flowdock::Client with api_token DELETE 
> does abstract delete with params
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/ruby-flowdock_0.7.0-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#867648: jruby-maven-plugins: FTBFS: RailsService.java:[26,20] variable session might not have been initialized

[Lucas Nussbaum]

Source: jruby-maven-plugins
Version: 1.1.5+ds1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/jruby-maven-plugins-1.1.5+ds1'
> dh_auto_build -- install
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/jruby-maven-plugins-1.1.5\+ds1
>  -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/jruby-maven-plugins-1.1.5\+ds1/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/jruby-maven-plugins-1.1.5\+ds1/debian 
> -Dmaven.repo.local=/<>/jruby-maven-plugins-1.1.5\+ds1/debian/maven-repo
>  install -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] JRuby Maven Mojos
> [INFO] Mojo Parent
> [INFO] Ruby Tools
> [INFO] JRuby Maven Mojo
> [INFO] Gem Maven Mojo
> [INFO] 
> [INFO] 
> 
> [INFO] Building JRuby Maven Mojos 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install 
> (default-install) @ jruby-maven-plugins ---
> [INFO] Installing 
> /<>/jruby-maven-plugins-1.1.5+ds1/pom.xml to 
> /<>/jruby-maven-plugins-1.1.5+ds1/debian/maven-repo/de/saumya/mojo/jruby-maven-plugins/1.1.5/jruby-maven-plugins-1.1.5.pom
> [INFO] 
> [INFO] 
> 
> [INFO] Building Mojo Parent 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-plugin-plugin:3.5:helpmojo 
> (default) @ parent-mojo ---
> [WARNING] Unsupported packaging type pom, execution skipped
> [INFO] 
> [INFO] >>> maven-source-plugin:2.4:jar 
> (default) > generate-sources @ parent-mojo 
> >>>
> [INFO] 
> [INFO] <<< maven-source-plugin:2.4:jar 
> (default) < generate-sources @ parent-mojo 
> <<<
> [INFO] 
> [INFO] 
> [INFO] --- maven-source-plugin:2.4:jar 
> (default) @ parent-mojo ---
> [INFO] Skipping source per configuration.
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install 
> (default-install) @ parent-mojo ---
> [INFO] Installing 
> /<>/jruby-maven-plugins-1.1.5+ds1/parent-mojo/pom.xml to 
> /<>/jruby-maven-plugins-1.1.5+ds1/debian/maven-repo/de/saumya/mojo/parent-mojo/1.1.5/parent-mojo-1.1.5.pom
> [INFO] 
> [INFO] 
> 
> [INFO] Building Ruby Tools 1.1.5
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-dependency-plugin:2.8:copy (copy 
> jruby) @ ruby-tools ---
> [INFO] Configured Artifact: org.jruby:jruby-complete:debian:jar
> [INFO] Copying jruby-complete-debian.jar to 
> /<>/jruby-maven-plugins-1.1.5+ds1/ruby-tools/target/jruby-complete-debian.jar
> [INFO] 
> [INFO] --- 
> maven-dependency-plugin:2.8:copy-dependencies (copy gems) @ 
> ruby-tools ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.6:resources 
> (default-resources) @ ruby-tools ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 18 resources
> [INFO] 
> [INFO] --- exec-maven-plugin:1.1.1:exec (install 
> gems) @ ruby-tools ---
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:compile 
> (default-compile) @ ruby-tools ---
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, 

Bug#867647: ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: return http.request(req, body, )

[Lucas Nussbaum]

Source: ruby-rest-client
Version: 1.8.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: return http.request(req, body, )
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: GET 
> http://some/resource with headers {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip, deflate', 'Authorization'=>'Basic Zm9vOmJhcg==', 
> 'User-Agent'=>'Ruby'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:get, "http://some/resource;).
>  with(headers: {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip, deflate', 'Authorization'=>'Basic Zm9vOmJhcg==', 
> 'User-Agent'=>'Ruby'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:get, "http://foo:bar@new/resource;).
>  with(headers: {'Accept'=>'application/json'})
>stub_request(:get, "http://foo:bar@some/resource;).
>  with(headers: {'Accept'=>'application/json'})
> 
>
>  # ./lib/restclient/request.rb:270:in `net_http_do_request'
>  # ./lib/restclient/request.rb:418:in `block in transmit'
>  # ./lib/restclient/request.rb:413:in `transmit'
>  # ./lib/restclient/request.rb:176:in `execute'
>  # ./lib/restclient/request.rb:41:in `execute'
>  # ./spec/unit/response_spec.rb:90:in `block (3 levels) in  (required)>'
> 
> Finished in 0.26307 seconds (files took 0.67677 seconds to load)
> 217 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/unit/response_spec.rb:87 # RestClient::Response redirection 
> follows a redirection and keep the parameters
> 
> Randomized with seed 14583
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/ruby-rest-client_1.8.0-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#867644: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output[2]).to match('Found 2 errors. Giving up')

[Lucas Nussbaum]

Source: ruby-puppet-syntax
Version: 2.2.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: expect(output[2]).to match('Found 2 errors. Giving up')
>expected "Language validation logged 2 errors. Giving up" to match 
> "Found 2 errors. Giving up"
>  # ./spec/puppet-syntax/manifests_spec.rb:79:in `block (2 levels) in  (required)>'
> 
> Finished in 0.15262 seconds (files took 0.95446 seconds to load)
> 34 examples, 2 failures, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/puppet-syntax/manifests_spec.rb:27 # PuppetSyntax::Manifests 
> should return an error from an invalid file
> rspec ./spec/puppet-syntax/manifests_spec.rb:70 # PuppetSyntax::Manifests 
> should continue after finding an error in the first file
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/ruby-puppet-syntax_2.2.0-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.