Bug#908942: marked as done (libio-socket-ssl-perl: FTBFS: Connection refused at t/verify_fingerprint.t line 49 and tests hang)

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 06:49:08 +
with message-id 
and subject line Bug#908942: fixed in libio-socket-ssl-perl 2.060-1
has caused the Debian Bug report #908942,
regarding libio-socket-ssl-perl: FTBFS: Connection refused at 
t/verify_fingerprint.t line 49 and tests hang
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.)


-- 
908942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libio-socket-ssl-perl
Version: 2.059-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libio-socket-ssl-perl&arch=all&ver=2.059-3&stamp=1537087640&raw=0

I am able to reproduce this if I run `prove -lb t/verify_fingerprint.t` several 
hundred times in a row, but I can't figure out what could be wrong.

Some times the test hangs, with parent calling wait(-1) and child doing 
accept(). Some times the test fails without hanging.

The test spawns two child processes, each one listening on a random port 
(chosen by the OS). The listen() call happens before the fork(), so it seems to 
me that a later connection attempt from the parent cannot fail.

The listen queue is set to 10, and each of the children is being connected less 
than 10 times.

The child processes are designed to exit when they are connected and 
disconnected without any data being sent. Perhaps this causes one of them to 
exit before the parent does its tests, but what other process makes that 
connection is a mistery.

I'll try adding some debugging output to the children and see if this "foreigh" 
connection attempt is the reason.


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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: clean
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libio-socket-ssl-perl
Source-Version: 2.060-1

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated libio-socket-ssl-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Sep 2018 06:41:12 +
Source: libio-socket-ssl-perl
Binary: libio-socket-ssl-perl
Architecture: source
Version: 2.060-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 908942
Description: 
 libio-socket-ssl-perl - Perl module implementing object oriented interface to 
SSL sockets
Changes:
 libio-socket-ssl-perl (2.060-1) unstable; urgency=medium
 .
   * New upstream version 2.060
 + drop all the patches (merged upstream)
 + Fixes test failures with openssl 1.1.1 (Closes: #908942)
Checksums-Sha1: 
 859e2e348f179d099426a48b53ec6e9ac009816c 2530 libio-socket-ssl-perl_2.060-1.dsc
 d00985ca87425ab5860bc38e59bcb9d39b372508 233169 
libio-socket-ssl-perl_2.060.orig.tar.gz
 25ed200b7858e780db62c70cc5b1aacb1503e033 10084 
libio-socket-ssl-perl_2.060-1.debian.tar.xz
Checksums-Sha256: 
 bfda6f19d817ca4ab174235d5d5e61637ac2d9e8a8b44490d22b1913d54a354d 2530 
libio-socket-ssl-perl_2.060-1.dsc
 fb5b2877ac5b686a5d7b8dd71cf5464ffe75d10c32047b5570674870e46b1b8c 233169 
libio-socket-ssl-perl_2.060.orig.tar.gz
 09fa3b75f9e908920dc04c952f739d5d1b3ec58d77c913febb0d344db42ecc46 10084 
libio-socket-ssl-perl_2.060-1.debian.tar.xz
Files: 
 083e4e524933eda0c6b64c68a879c253 2530 perl optional 
libio-socket-ssl-perl_2.060-1.dsc
 97fa6cd64f15db60f810cd8ab02d57fc 233169 perl optional 
libio-socket-ssl-perl_2.060.orig.tar.gz
 972599e08d30c349ca84549c5c2ac43c 10084 perl optional 
libio-socket-ssl-perl_2.060-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAlufTaUACgkQ276dTZnS
oASizw//dffqATAY+A4OXgono/A5Sso0964sqlw+deTMY3g2B8WTfy8kofCo3l

Processed: litecoin: FTBFS on mips64el in binNMU against qrencode - test failure

[Debian Bug Tracking System]

Processing control commands:

> block 908980 by -1
Bug #908980 [release.debian.org] transition: qrencode (ongoing, apparently 
uncoordinated)
908980 was blocked by: 908929
908980 was not blocking any bugs.
Added blocking bug(s) of 908980: 908987

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

Bug#908987: litecoin: FTBFS on mips64el in binNMU against qrencode - test failure

[Niels Thykier]

Source: litecoin
Version: 0.16.0-2
Severity: serious
Control: block 908980 by -1

Hi,

During the qrencode transition, we noticed that litecoin FTBFS on
mips64el.  It is not entirely clear that the FTBFS is related to
qrencode (from my PoV the failures looks related to cryptography and
I would assume qrencode was not used for that).

Anyhow, the last bit of the log is:

"""
FAIL: tests
===

src/tests.c:200: test condition failed: secp256k1_ecdsa_verify(vrfy, &sig, 
ctmp, &pubkey) == 1
FAIL tests (exit status: 134)


Testsuite summary for libsecp256k1 0.1

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

See ./test-suite.log

make[8]: *** [Makefile:1229: test-suite.log] Error 1
make[8]: Leaving directory '/<>/src/secp256k1'
make[7]: *** [Makefile:1337: check-TESTS] Error 2
make[7]: Leaving directory '/<>/src/secp256k1'
make[6]: *** [Makefile:1550: check-am] Error 2
make[6]: Leaving directory '/<>/src/secp256k1'
make[5]: *** [Makefile:10233: check-local] Error 2
make[5]: Leaving directory '/<>/src'
make[4]: *** [Makefile:9333: check-am] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:9011: check-recursive] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:748: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:37: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2018-09-17T02:09:46Z
"""

Note it might be relevant to see the entire log as it appears to list more 
failures
https://buildd.debian.org/status/fetch.php?pkg=litecoin&arch=mips64el&ver=0.16.0-2%2Bb1&stamp=1537150206&raw=0

Thanks,
~Niels

Bug#907162: marked as done (step: FTBFS in buster/sid (invalid use of incomplete type 'class QItemSelectionModel'))

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 05:34:19 +
with message-id 
and subject line Bug#907162: fixed in step 4:18.08.1-1
has caused the Debian Bug report #907162,
regarding step: FTBFS in buster/sid (invalid use of incomplete type 'class 
QItemSelectionModel')
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.)


-- 
907162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:step
Version: 4:17.08.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/<>'
dh_testdir  # [-a]
dh_auto_configure '--buildsystem=kf5' --parallel  # [-a]
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

In file included from /usr/include/KF5/KDELibs4Support/KDE/KStandardDirs:1,
 from /<>/step/mainwindow.cc:43:
/usr/include/KF5/KDELibs4Support/kstandarddirs.h:641:44: note: declared here
 KDELIBS4SUPPORT_DEPRECATED static bool makeDir(const QString &dir, int 
mode = 0755);
^~~
/<>/step/mainwindow.cc:466:31: warning: 'static bool 
KStandardDirs::makeDir(const QString&, int)' is deprecated 
[-Wdeprecated-declarations]
 KStandardDirs::makeDir(dir);
   ^
In file included from /usr/include/KF5/KDELibs4Support/KDE/KStandardDirs:1,
 from /<>/step/mainwindow.cc:43:
/usr/include/KF5/KDELibs4Support/kstandarddirs.h:641:44: note: declared here
 KDELIBS4SUPPORT_DEPRECATED static bool makeDir(const QString &dir, int 
mode = 0755);
^~~
/<>/step/mainwindow.cc:466:31: warning: 'static bool 
KStandardDirs::makeDir(const QString&, int)' is deprecated 
[-Wdeprecated-declarations]
 KStandardDirs::makeDir(dir);
   ^
In file included from /usr/include/KF5/KDELibs4Support/KDE/KStandardDirs:1,
 from /<>/step/mainwindow.cc:43:
/usr/include/KF5/KDELibs4Support/kstandarddirs.h:641:44: note: declared here
 KDELIBS4SUPPORT_DEPRECATED static bool makeDir(const QString &dir, int 
mode = 0755);
^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic.h:41,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qbytearray.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QUrl:1,
 from /<>/step/mainwindow.h:22,
 from /<>/step/mainwindow.cc:19:
/<>/step/mainwindow.cc: In member function 'void 
MainWindow::worldSelectionChanged()':
/<>/step/mainwindow.cc:578:46: error: invalid use of incomplete 
type 'class QItemSelectionModel'
  worldModel->selectionModel()->selection().indexes()) {
  ^~
In file included from /<>/step/mainwindow.cc:24:
/<>/step/worldmodel.h:41:7: note: forward declaration of 'class 
QItemSelectionModel'
 class QItemSelectionModel;
   ^~~
make[4]: *** [step/CMakeFiles/step.dir/build.make:124: 
step/CMakeFiles/step.dir/mainwindow.cc.o] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:3538: step/CMakeFiles/step.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:144: all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:

Processed: Regression in a stable update

[Debian Bug Tracking System]

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

> severity 908112 serious
Bug #908112 [ganeti] ganeti: Unable to move an instance to an other node
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[Roger Shimizu]

On Sat, Sep 15, 2018 at 2:11 PM, intrigeri  wrote:
> Roger Shimizu:
>> On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann  wrote:
>>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>>> After upgrading to 0.2.9-4, adequate complains:
>>>
>>> torbrowser-launcher: obsolete-conffile 
>>> /etc/apparmor.d/local/torbrowser.Tor.tor
>>> torbrowser-launcher: obsolete-conffile 
>>> /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>>> torbrowser-launcher: obsolete-conffile 
>>> /etc/apparmor.d/local/torbrowser.Browser.firefox
>
>> Sorry, I don't have these errors when upgrading package.
>
> To reproduce, I think you need 1. adequate installed;
> 2. upgrading from a specific version of the package.

I confirmed I already had adequate installed previously.

$ dpkg -l adequate
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
+++--=-=-==
ii  adequate 0.15.1all
Debian package quality testing tool

On Sun, Sep 16, 2018 at 2:35 AM, gregor herrmann  wrote:
>> > After getting rid of them, I have a starting torbrowser again.
>> >
>> > Looks like some dpkg-maintscript-helper(1) magic is needed here ...
>>
>> Could you provide an example, or even patch?
>> Thanks!
>
> After looking at the package/repo:
>
> The files under /etc/apparmor.d/local were created in 0.2.9-1 (with
> the upstream import) and were removed in 0.2.9-2, probably with
> 0016-Remove-apparmor-local-path-from-setup.py.patch. Or maybe with
> debian/patches/0015-AppArmor-remove-boilerplate-from-local-override-file.patch.
> Or with both :)
>
> This is somewhat confusing but 0.2.9-1 seems to be the only release
> with
>
> drwxr-xr-x root/root 0 2018-01-29 15:17 ./etc/apparmor.d/local/
> -rw-r--r-- root/root   134 2018-01-28 19:33 
> ./etc/apparmor.d/local/torbrowser.Browser.firefox
> -rw-r--r-- root/root   133 2018-01-28 19:33 
> ./etc/apparmor.d/local/torbrowser.Browser.plugin-container
> -rw-r--r-- root/root   133 2018-01-28 19:33 
> ./etc/apparmor.d/local/torbrowser.Tor.tor
>
> (That also means that adequate must have warned me earlier?)
>
> Anyway, these conffiles are not shipped any more; either that's a
> mistake or they need to be properly removed.

I tried to install 0.2.9-1 and upgrade to 0.2.9-4, but still didn't reproduced.
I tested it again after enabling adequate by set 'Adequate::Enabled
"true";' in /etc/apt/apt.conf.d/20adequate
But same result.

BTW. Old packages can be found on snapshot.d.o [1].

[1] http://snapshot.debian.org/package/torbrowser-launcher/


# dpkg -i torbrowser-launcher_0.2.9-1_amd64.deb
(Reading database ... 272854 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-1_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-1) over (0.2.9-1) ...
Setting up torbrowser-launcher (0.2.9-1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272854 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-1) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.plugin-container ...
Installing new version of config file /etc/apparmor.d/torbrowser.Tor.tor ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...


> There is already debian/torbrowser-launcher.maintscript which IMO
> needs three new lines:
>
> rm_conffile /etc/apparmor.d/local/torbrowser.Tor.tor 0.2.9-2~ 
> torbrowser-launcher
> rm_conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container 
> 0.2.9-2~ torbrowser-launcher
> rm_conffile /etc/apparmor.d/local/torbrowser.Browser.firefox 0.2.9-2~ 
> torbrowser-launcher
>
> Or maybe s/0.2.9-2~/0.2.9-5~/ , if I'm reading dpkg-maintscript-helper(1)
> correctly.

Thanks for the hint!
I'll try this snippet.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Re: Bug#908124: libh2o-evloop-dev: Depends on libwslay to link but doesn't say so in pkg-config file

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libh2o-evloop0.13 2.2.5+dfsg1-6
Bug #908124 [libh2o-evloop-dev] libh2o-evloop-dev: Depends on libwslay to link 
but doesn't say so in pkg-config file
Bug reassigned from package 'libh2o-evloop-dev' to 'libh2o-evloop0.13'.
No longer marked as found in versions h2o/2.2.5+dfsg1-6.
Ignoring request to alter fixed versions of bug #908124 to the same values 
previously set
Bug #908124 [libh2o-evloop0.13] libh2o-evloop-dev: Depends on libwslay to link 
but doesn't say so in pkg-config file
Marked as found in versions h2o/2.2.5+dfsg1-6.
> retitle -1 libh2o-evloop.so must be linked with libwslay
Bug #908124 [libh2o-evloop0.13] libh2o-evloop-dev: Depends on libwslay to link 
but doesn't say so in pkg-config file
Changed Bug title to 'libh2o-evloop.so must be linked with libwslay' from 
'libh2o-evloop-dev: Depends on libwslay to link but doesn't say so in 
pkg-config file'.
> severity -1 serious
Bug #908124 [libh2o-evloop0.13] libh2o-evloop.so must be linked with libwslay
Severity set to 'serious' from 'important'

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

Bug#908942: libio-socket-ssl-perl: FTBFS: Connection refused at t/verify_fingerprint.t line 49 and tests hang

[Damyan Ivanov]

-=| gregor herrmann, 17.09.2018 00:18:35 +0200 |=-
> On Sun, 16 Sep 2018 14:42:05 +, Damyan Ivanov wrote:
> 
> > The test passes a thousand runs if the server child ignores SIGPIPE, 
> > so this looks like the TLSv1.3 shutdown problem when the client makes 
> > a fast SSL shutdown without waiting for the confirmation from the 
> > server, then exits, then exits and the server sending its confirmation 
> > gets SIGPIPEd.
> 
> 
> https://rt.cpan.org/Ticket/Display.html?id=126899 also talks about
> issues around SIGPIPE.
> And there's a new 2.060, maybe we should try and check from there.

Oh, nice. Thanks for that notification. I was delving in internals 
trying to avoid ignoring SIGPIPE.

Upstream seems to have gone the other way, ignoring SIGPIPE and 
documenting the situation. It it suits them, I think it is alright :)

I'll run the test suite a hundred times and upload the new upstream 
release.

-- dam

Processed: severity of 908134 is serious

[Debian Bug Tracking System]

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

> severity 908134 serious
Bug #908134 [libpodofo-dev] libpodofo-dev: Wrong linker flag -lpodofo-0 
returned from pkg-config
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#907432: marked as done (golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to activation.Listeners))

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 03:34:09 +
with message-id 
and subject line Bug#907432: fixed in golang-github-cloudflare-redoctober 
0.0~git20161017.0.78e9720-3
has caused the Debian Bug report #907432,
regarding golang-github-cloudflare-redoctober: FTBFS (too many arguments in 
call to activation.Listeners)
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.)


-- 
907432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-cloudflare-redoctober
Version: 0.0~git20161017.0.78e9720-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang --with systemd
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-cloudflare-redoctober-0.0\~git20161017.0.78e9720/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-cloudflare-redoctober-0.0\~git20161017.0.78e9720/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/cloudflare/redoctober 
github.com/cloudflare/redoctober/client github.com/cloudflare/redoctober/cmd/ro 
github.com/cloudflare/redoctober/cmd/ro/gopass 
github.com/cloudflare/redoctober/config github.com/cloudflare/redoctober/core 
github.com/cloudflare/redoctober/cryptor github.com/cloudflare/redoctober/ecdh 
github.com/cloudflare/redoctober/hipchat 
github.com/cloudflare/redoctober/keycache github.com/cloudflare/redoctober/msp 
github.com/cloudflare/redoctober/order github.com/cloudflare/redoctober/padding 
github.com/cloudflare/redoctober/passvault 
github.com/cloudflare/redoctober/persist 
github.com/cloudflare/redoctober/symcrypt
github.com/cloudflare/redoctober/config
github.com/cloudflare/redoctober/padding
github.com/cloudflare/redoctober/symcrypt
github.com/cloudflare/redoctober/ecdh
golang.org/x/crypto/pbkdf2
golang.org/x/crypto/scrypt
github.com/cloudflare/redoctober/passvault
github.com/cloudflare/redoctober/keycache
github.com/cloudflare/redoctober/msp
github.com/cloudflare/redoctober/persist
github.com/cloudflare/redoctober/cryptor
github.com/cloudflare/redoctober/hipchat
github.com/cloudflare/redoctober/order
github.com/cloudflare/redoctober/core
github.com/coreos/go-systemd/activation
github.com/beorn7/perks/quantile
github.com/golang/protobuf/proto
github.com/prometheus/client_model/go
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
github.com/prometheus/common/model
github.com/prometheus/common/expfmt
github.com/prometheus/procfs/internal/util
github.com/prometheus/procfs/nfs
github.com/prometheus/procfs/xfs
github.com/prometheus/procfs
github.com/prometheus/client_golang/prometheus
github.com/cloudflare/redoctober
# github.com/cloudflare/redoctober
src/github.com/cloudflare/redoctober/redoctober.go:141:41: too many arguments 
in call to activation.Listeners
have (bool)
want ()
github.com/cloudflare/redoctober/client
github.com/cloudflare/redoctober/cmd/ro/gopass
github.com/cloudflare/redoctober/cmd/ro
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-cloudflare-redoctober-0.0\~git20161017.0.78e9720/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-cloudflare-redoctober-0.0\~git20161017.0.78e9720/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/cloudflare/redoctober 
github.com/cloudflare/redoctober/client github.com/cloudflare/redoctober/cmd/ro 
github.com/cloudflare/redoctober/cmd/ro/gopass 
github.com/cloudflare/redoctober/config github.com/cloudflare/redoctober/core 
github.com/cloudflare/redoctober/cryptor github.com/cloudflare/redoctober/ecdh 
github.com/cloudflare/redoctober/hipchat 
github.com/cloudflare/redoctober/keycache github.com/cloudflare/redoctober/msp 
github.com/cloudflare/redoctober/order github.com/cloudflare/redoctober/padding 
github.com/cloudflare/redoctober/passvault 
github.com/cloudflare/redoctober/persist 
github.com/cloudflare/redoctober/symcrypt returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpk

Bug#897504: marked as done (golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/hashicorp/go-plugin returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 03:19:07 +
with message-id 
and subject line Bug#897504: fixed in golang-github-hashicorp-go-plugin 
0.0~git20170621.5ee1a665-2
has caused the Debian Bug report #897504,
regarding golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/hashicorp/go-plugin 
returned exit code 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.)


-- 
897504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-hashicorp-go-plugin
Version: 0.0~git20160212.0.cccb4a1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install 
> -gcflags=\"-trimpath=/<>/golang-github-hashicorp-go-plugin-0.0\~git20160212.0.cccb4a1/obj-x86_64-linux-gnu/src\"
>  
> -asmflags=\"-trimpath=/<>/golang-github-hashicorp-go-plugin-0.0\~git20160212.0.cccb4a1/obj-x86_64-linux-gnu/src\"
>  -v -p 1 github.com/hashicorp/go-plugin
> github.com/hashicorp/yamux
> github.com/hashicorp/go-plugin
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/hashicorp/go-plugin
> === RUN   TestClient_testInterfaceReattach
> 2018/05/02 19:21:27 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "test-interface-daemon"}
> 2018/05/02 19:21:27 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:27 [DEBUG] plugin: go-plugin.test: 2018/05/02 19:21:27 
> [DEBUG] plugin: plugin address: unix /tmp/plugin359815028
> 2018/05/02 19:21:28 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> 2018/05/02 19:21:29 [DEBUG] plugin: reattached plugin process exited
> --- PASS: TestClient_testInterfaceReattach (2.00s)
> === RUN   TestClient
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "mock"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClient (0.00s)
> === RUN   TestClient_testInterface
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "test-interface"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: go-plugin.test: 2018/05/02 19:21:29 
> [DEBUG] plugin: plugin address: unix /tmp/plugin030403425
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClient_testInterface (0.01s)
> === RUN   TestClient_cmdAndReattach
> --- PASS: TestClient_cmdAndReattach (0.00s)
> === RUN   TestClient_reattachNotFound
> --- PASS: TestClient_reattachNotFound (0.01s)
> === RUN   TestClientStart_badVersion
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "bad-version"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClientStart_badVersion (0.00s)
> === RUN   TestClient_Start_Timeout
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "start-timeout"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEB

Processed: Re: dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small key

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small key and 
> unknown ca
Bug #898969 [dnssec-trigger] dnssec-trigger: fails with OpenSSL in experimental 
due to too-small key
Changed Bug title to 'dnssec-trigger: fails with OpenSSL 1.1.1 due to too-small 
key and unknown ca' from 'dnssec-trigger: fails with OpenSSL in experimental 
due to too-small key'.
> severity -1 serious
Bug #898969 [dnssec-trigger] dnssec-trigger: fails with OpenSSL 1.1.1 due to 
too-small key and unknown ca
Severity set to 'serious' from 'important'

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

Bug#903388: marked as done (Failure to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 00:19:15 +
with message-id 
and subject line Bug#903388: fixed in libcloud 2.3.0-2
has caused the Debian Bug report #903388,
regarding Failure to install with Python 3.7
to be marked as done.

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

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


-- 
903388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-libcloud
Version: 2.3.0-1
Severity: serious

Setting up python3-libcloud (2.3.0-1) ...
File "/usr/lib/python3/dist-packages/libcloud/compute/drivers/azure.py",
line 1438
  def _perform_post(self, path, body, response_type=None, async=False):
^
SyntaxError: invalid syntax

'async' is a reserved keyword in Python 3.7. This issue has been
previously reported upstream, and was fixed in version 4.3 of
pexpect.[1] The current upstream version is 4.6.

[1] https://github.com/pexpect/pexpect/issues/453
--- End Message ---
--- Begin Message ---
Source: libcloud
Source-Version: 2.3.0-2

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated libcloud 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, 16 Sep 2018 19:46:23 -0400
Source: libcloud
Binary: python-libcloud python3-libcloud
Architecture: source all
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Starr-Bochicchio 
Description:
 python-libcloud - unified Python interface into the cloud
 python3-libcloud - unified Python interface into the cloud (Python3 version)
Closes: 900999 903388
Changes:
 libcloud (2.3.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
 .
   [ Andrew Starr-Bochicchio ]
   * d/tests: Run autopkg tests on all supported Python
 versions (Closes: #900999).
   * d/patches/0001-Backport-Python-3.7-support-from-upstream-master.patch:
 Backport Python 3.7 support from upstream master (Closes: #903388).
   * d/patches/0002-Unset-the-http_proxy-environment-variable-before-run.patch:
 Backport upstream patch fixing issues w/ disabled tests.
   * d/rules: Re-enable tests that conflict with pybuild's proxy settings.
Checksums-Sha1:
 7413ffa28db99a828e021343a2fcc8f67fc399d6 2700 libcloud_2.3.0-2.dsc
 ddb54c76a5bb8e056449534384c58168e3900816 8324 libcloud_2.3.0-2.debian.tar.xz
 6e5c33d28ce6cab14fe9bcdb1954729e6b63774b 9362 libcloud_2.3.0-2_amd64.buildinfo
 02b4d3dd801c24639d9aac971a1b9f468620e30b 1306812 
python-libcloud_2.3.0-2_all.deb
 548bf280913ed72bbcdd45da69b4c668f2e4e1f7 1290272 
python3-libcloud_2.3.0-2_all.deb
Checksums-Sha256:
 0680a31924660ad073ce4d98c2b8af2b25d3aefe887cee4987af2ab9afb50f61 2700 
libcloud_2.3.0-2.dsc
 3c769f39a1670f7a7c7692d63dea84a55c04509c7b0116710b7176f6a5624661 8324 
libcloud_2.3.0-2.debian.tar.xz
 ff580b139d0f2b1f8b816ca570129abc9eb2ade85378d7fa56b9b686ac030780 9362 
libcloud_2.3.0-2_amd64.buildinfo
 f155d6298b181c8819e0d99f50eaee2e42fee738cea5eb549860629a8cfd7b00 1306812 
python-libcloud_2.3.0-2_all.deb
 deedbe843d4c19680f8d70ae2fcecc3a05da861fd6a610fbc4d5402e6e7d8ae1 1290272 
python3-libcloud_2.3.0-2_all.deb
Files:
 172ba03073520847fe85d9c7037b2af9 2700 python optional libcloud_2.3.0-2.dsc
 bcc6a1d51038e9218ef485b18e27de8e 8324 python optional 
libcloud_2.3.0-2.debian.tar.xz
 8c12f4eb3e600e8785d1cc6e3da16f1c 9362 python optional 
libcloud_2.3.0-2_amd64.buildinfo
 6b14386aa5535c6437c4d497fafa2b89 1306812 python optional 
python-libcloud_2.3.0-2_all.deb
 45e142063591160dd6b938b56b039d1a 1290272 python optional 
python3-libcloud_2.3.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbrIj19ceZ6U8k6faO1biu9U/3LEFAlue7YUACgkQO1biu9U/
3LH17BAAtAZv2ExPbUpwwjCZhBR5vYkhmbtcWVTBtJjrFSEKbYSh3oaGvCdD4SQ5
Q

Bug#906888: marked as done (fdroidserver fails it's autopkg tests)

[Debian Bug Tracking System]

Your message dated Mon, 17 Sep 2018 00:19:15 +
with message-id 
and subject line Bug#903388: fixed in libcloud 2.3.0-2
has caused the Debian Bug report #903388,
regarding fdroidserver fails it's autopkg tests
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.)


-- 
903388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fdroidserver
Version: 1.0.9-1
Severity: serious
Tags: sid buster

see
https://ci.debian.net/data/packages/unstable/amd64/f/fdroidserver/latest-autopkgtest/log.gz

autopkgtest: WARNING: package fdroidserver is not installed though it should be
command2 FAIL badpkg
blame: fdroidserver
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
autopkgtest [10:10:07]:  summary
command1 PASS
command2 FAIL badpkg
blame: fdroidserver
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
--- End Message ---
--- Begin Message ---
Source: libcloud
Source-Version: 2.3.0-2

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated libcloud 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, 16 Sep 2018 19:46:23 -0400
Source: libcloud
Binary: python-libcloud python3-libcloud
Architecture: source all
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Starr-Bochicchio 
Description:
 python-libcloud - unified Python interface into the cloud
 python3-libcloud - unified Python interface into the cloud (Python3 version)
Closes: 900999 903388
Changes:
 libcloud (2.3.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
 .
   [ Andrew Starr-Bochicchio ]
   * d/tests: Run autopkg tests on all supported Python
 versions (Closes: #900999).
   * d/patches/0001-Backport-Python-3.7-support-from-upstream-master.patch:
 Backport Python 3.7 support from upstream master (Closes: #903388).
   * d/patches/0002-Unset-the-http_proxy-environment-variable-before-run.patch:
 Backport upstream patch fixing issues w/ disabled tests.
   * d/rules: Re-enable tests that conflict with pybuild's proxy settings.
Checksums-Sha1:
 7413ffa28db99a828e021343a2fcc8f67fc399d6 2700 libcloud_2.3.0-2.dsc
 ddb54c76a5bb8e056449534384c58168e3900816 8324 libcloud_2.3.0-2.debian.tar.xz
 6e5c33d28ce6cab14fe9bcdb1954729e6b63774b 9362 libcloud_2.3.0-2_amd64.buildinfo
 02b4d3dd801c24639d9aac971a1b9f468620e30b 1306812 
python-libcloud_2.3.0-2_all.deb
 548bf280913ed72bbcdd45da69b4c668f2e4e1f7 1290272 
python3-libcloud_2.3.0-2_all.deb
Checksums-Sha256:
 0680a31924660ad073ce4d98c2b8af2b25d3aefe887cee4987af2ab9afb50f61 2700 
libcloud_2.3.0-2.dsc
 3c769f39a1670f7a7c7692d63dea84a55c04509c7b0116710b7176f6a5624661 8324 
libcloud_2.3.0-2.debian.tar.xz
 ff580b139d0f2b1f8b816ca570129abc9eb2ade85378d7fa56b9b686ac030780 9362 
libcloud_2.3.0-2_amd64.buildinfo
 f155d6298b181c8819e0d99f50eaee2e42fee738cea5eb549860629a8cfd7b00 1306812 
python-libcloud_2.3.0-2_all.deb
 deedbe843d4c19680f8d70ae2fcecc3a05da861fd6a610fbc4d5402e6e7d8ae1 1290272 
python3-libcloud_2.3.0-2_all.deb
Files:
 172ba03073520847fe85d9c7037b2af9 2700 python optional libcloud_2.3.0-2.dsc
 bcc6a1d51038e9218ef485b18e27de8e 8324 python optional 
libcloud_2.3.0-2.debian.tar.xz
 8c12f4eb3e600e8785d1cc6e3da16f1c 9362 python optional 
libcloud_2.3.0-2_amd64.buildinfo
 6b14386aa5535c6437c4d497fafa2b89 1306812 python optional 
python-libcloud_2.3.0-2_all.de

Processed (with 1 error): fix version info for 907687

[Debian Bug Tracking System]

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

> # version tracking doesn't accept the fixed version, adjusting
> notfixed 907687 src:buildbot/1.4.0-1
Unknown command or malformed arguments to command.
> fixed 907687 1.4.0-1
Bug #907687 {Done: Robin Jarry } [src:buildbot] buildbot: FTBFS 
(buildbot_worker.test.unit.test_runprocess.TestRunProcess.testPipeString fails)
Marked as fixed in versions buildbot/1.4.0-1.
> thanks
Stopping processing here.

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

Processed (with 1 error): transition: qrencode (ongoing, apparently uncoordinated)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1https://release.debian.org/transitions/html/auto-qrencode.html
Unknown command or malformed arguments to command.

> block -1 by 908929
Bug #908980 [release.debian.org] transition: qrencode (ongoing, apparently 
uncoordinated)
908980 was not blocked by any bugs.
908980 was not blocking any bugs.
Added blocking bug(s) of 908980: 908929

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

Bug#908979: jayway-jsonpath: FTBFS on all

[Ivo De Decker]

package: jayway-jsonpath
version: 2.0.0-4
severity: serious

Hi,

The latest version of jayway-jsonpath in unstable fails on all:

https://buildd.debian.org/status/package.php?p=jayway-jsonpath

Cheers,

Ivo

Bug#908978: openvswitch: FTBFS on armel, mips, mips64el, mipsel

[Ivo De Decker]

package: openvswitch
version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-3
severity: serious

Hi,

The latest version of openvswitch in unstable fails on armel, mips, mips64el,
mipsel:

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

Cheers,

Ivo

Bug#897755: fixed in fswatch 1.12.0+repack-3

[Alf Gaida]

Not still, again is the better word for. will fix it in the next days again.

Cheers Alf

Bug#908966: marked as done (libiptcdata0-dev: ships libiptcdata.pc in literally /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 22:34:15 +
with message-id 
and subject line Bug#908966: fixed in libiptcdata 1.0.5-2
has caused the Debian Bug report #908966,
regarding libiptcdata0-dev: ships libiptcdata.pc in literally 
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
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.)


-- 
908966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libiptcdata0-dev
Version: 1.0.5-1
Severity: serious
Justification: makes tracker-miners ftbfs
Tags: ftbfs
Control: affects -1 + src:tracker-miners

libiptcdata.pc is now shipped in literally
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig. That is semantically
equivalent to it being absent. Consequently, the autopkgtest for
tracker-miners fails. tracker-miners also fails to build from source.

If you want to use such an expansion in libiptcdata0-dev.install, you
must Build-Depends: dh-exec, add a #! line and make the file executable.

It might be easiert to just add
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) to
DEB_CONFIGURE_EXTRA_FLAGS though.

Helmut
--- End Message ---
--- Begin Message ---
Source: libiptcdata
Source-Version: 1.0.5-2

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

Debian distribution maintenance software
pp.
Ian Wienand  (supplier of updated libiptcdata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 17 Sep 2018 08:02:52 +1000
Source: libiptcdata
Binary: libiptcdata0-dev libiptcdata0-dbg libiptcdata-doc libiptcdata-bin 
libiptcdata0 python-iptcdata
Architecture: source amd64 all
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Ian Wienand 
Description:
 libiptcdata-bin - Library to parse IPTC metadata (programs)
 libiptcdata-doc - Library to parse IPTC metadata (documentation)
 libiptcdata0 - Library to parse IPTC metadata
 libiptcdata0-dbg - Library to parse IPTC metadata (debug files)
 libiptcdata0-dev - Library to parse IPTC metadata (development files)
 python-iptcdata - Python bindings for the iptcdata library
Closes: 908966
Changes:
 libiptcdata (1.0.5-2) unstable; urgency=medium
 .
   * Fix multi-arch configuration & libiptcdata.pc location by using
 configure argument; update paths in .install files (Closes: #908966).
 Thanks Helmut!
Checksums-Sha1:
 38b85bb0ea29963c713ad7c3536a72ce6e00d5ca 2336 libiptcdata_1.0.5-2.dsc
 c4c4baa9f7894386d9a69eeac82d1f853dc3d961 6584 libiptcdata_1.0.5-2.debian.tar.xz
 d8d7f1ad472378b72c09d6d5fd68a541b837ff6a 24000 
libiptcdata-bin_1.0.5-2_amd64.deb
 d8d8223383b136896e27304904edb5e4782d35a9 28184 libiptcdata-doc_1.0.5-2_all.deb
 4d81d99946229ddbe35b485c13c5c8b250895a4d 99148 
libiptcdata0-dbg_1.0.5-2_amd64.deb
 b511c9d50c5f3031a122794b13531dadcc2579b3 18436 
libiptcdata0-dev_1.0.5-2_amd64.deb
 02c257cd2c4558e4df4d0ecbcf14bdfecdfc21e6 29488 libiptcdata0_1.0.5-2_amd64.deb
 669f0a56de5d64e0f889f684f7309488219bb117 10933 
libiptcdata_1.0.5-2_amd64.buildinfo
 ab95c0868bfc7c414c776e8ac62586308550ce90 23012 
python-iptcdata_1.0.5-2_amd64.deb
Checksums-Sha256:
 e0ed0c33c74ac2f0a6924834a40f0d7c90057989097416a98874daf091c35e75 2336 
libiptcdata_1.0.5-2.dsc
 87bd269a8a95a05d998ed5d35971cf765a64be5d828046a315b5e7f8a9d4b6e3 6584 
libiptcdata_1.0.5-2.debian.tar.xz
 75bba1233fa424b61e74496f31487cb67ec8e71eb92cf3345fb3a373083290a3 24000 
libiptcdata-bin_1.0.5-2_amd64.deb
 c2d9dfb823357c2dc308cf2fb074d2ec5fdbb9d51cc6fe545bf4f968b51656ef 28184 
libiptcdata-doc_1.0.5-2_all.deb
 245d286efa0ef35b2e17ef7a0f603398b7b7fdeb9329f38c2c89d205d75bd071 99148 
libiptcdata0-dbg_1.0.5-2_amd64.deb
 afe2f4a00780e53ed0bf62a2fd2b9635ed02507c412e144459e03dc1e252a3db 18436 
libiptcdata0-dev_1.0.5-2_amd64.deb
 62ec4f8beca05bf5786201668f78171fa69df3c37285adb7012b80994898f4be 29488 
libiptcdata0_1.0.5-2_amd64.deb
 74fad598e34679e5daa34cd00b697c6b1fb35f43364552633d8724b5c7eee2aa 10933 
libiptcdata_1.0.5-2_amd64.buildinfo
 075f637e42a99ed1635dd28e83a52b98d8d91b37d54b104dde7eec33eb1914e3 23012 
pyth

Processed: severity of 907518 is serious

[Debian Bug Tracking System]

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

> severity 907518 serious
Bug #907518 [wpasupplicant] New libssl1.1 1.1.1~~pre9-1 in unstable breaks 
connecting to some wifi networks
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#908942: libio-socket-ssl-perl: FTBFS: Connection refused at t/verify_fingerprint.t line 49 and tests hang

[gregor herrmann]

On Sun, 16 Sep 2018 14:42:05 +, Damyan Ivanov wrote:

> The test passes a thousand runs if the server child ignores SIGPIPE, 
> so this looks like the TLSv1.3 shutdown problem when the client makes 
> a fast SSL shutdown without waiting for the confirmation from the 
> server, then exits, then exits and the server sending its confirmation 
> gets SIGPIPEd.


https://rt.cpan.org/Ticket/Display.html?id=126899 also talks about
issues around SIGPIPE.
And there's a new 2.060, maybe we should try and check from there.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Sonny Terry: Playing With The Thing


signature.asc
Description: Digital Signature

Processed: Re: Bug#908705: g_icon_to_string output includes some garbage prefix

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream confirmed
Bug #908705 [libglib2.0-0] g_icon_to_string output includes some garbage prefix
Added tag(s) upstream and confirmed.

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

Bug#908705: g_icon_to_string output includes some garbage prefix

[Simon McVittie]

Control: tags -1 + upstream confirmed

On Fri, 14 Sep 2018 at 16:04:41 -0300, Damián Barberón wrote:
> The patches pushed recently from the upstream fixes this.

They have not been merged yet, so tagging this upstream rather than
fixed-upstream.

The merge request is:
https://gitlab.gnome.org/GNOME/glib/merge_requests/305

smcv

Bug#897755: fixed in fswatch 1.12.0+repack-3

[Santiago Vila]

found 897755 1.12.0+repack-5
thanks

This is still happening in buster/sid, please see:

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

for details.

Thanks.

Processed: Re: Bug#897755: fixed in fswatch 1.12.0+repack-3

[Debian Bug Tracking System]

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

> found 897755 1.12.0+repack-5
Bug #897755 {Done: Alf Gaida } [src:fswatch] fswatch: 
ftbfs with GCC-8
Marked as found in versions fswatch/1.12.0+repack-5 and reopened.
> thanks
Stopping processing here.

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

Processed: affects 908966

[Debian Bug Tracking System]

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

> affects 908966 src:rawtherapee
Bug #908966 [libiptcdata0-dev] libiptcdata0-dev: ships libiptcdata.pc in 
literally /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
Added indication that 908966 affects src:rawtherapee
> thanks
Stopping processing here.

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

Processed: notfixed 859795 in 1.6.0-1

[Debian Bug Tracking System]

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

> # unconfuse
> notfixed 859795 1.6.0-1
Bug #859795 {Done: Hans Joachim Desserud } 
[src:python-cgcloud] python-cgcloud: dependency python-bd2k is not yet in the 
archive
No longer marked as fixed in versions 1.6.0-1.
> thanks
Stopping processing here.

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

Bug#908681: libsane1: pointless package rename

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Julien,


Am Mittwoch, den 12.09.2018, 16:14 +0200 schrieb Julien Cristau:
> Package: libsane1
> Severity: serious
> 
> Hi,
> 
> libsane was renamed to libsane1 for apparently no good
> reason.  Renames
> for library packages should be tied to ABI breakage (and associated
> SONAME changes).
> 

According to Debian Policy 8.6.2, renaming of the SONAME and the
library package name is possible for non-backwards compatible ABI
changes.

The SONAME is for a longer time 1: 

$ objdump -p ./libsane.so.1.0.27 | grep SONAME
  SONAME   libsane.so.1

$ objdump -p ./libsane.so.1.0.25 | grep SONAME
  SONAME   libsane.so.1

Between libsane.so.1.0.25 and libsane.so.1.0.27 are some symbols
removed. Therefore the change the library from libsane to libsane1
are possible.

> Either there was ABI breakage and the SONAME should be bumped (and
> Provides: libsane would be wrong), or there wasn't and the package
> name
> change ought to be reverted.
> 

The changes 

- -Breaks: libsane (<<1.0.27-1)
- -Replaces: libsane (<<1.0.27-1)
- -Pre-Depends: ${misc:Pre-Depends}
+Conflicts: libsane (<< 1.0.27-1~)
+Replaces: libsane (<< 1.0.27-1~)
+Provides: libsane (= ${binary:Version})

were requested by Jeremy Bicha and taken over after consultation with
my mentor.

> I don't know which it is, and when I asked I didn't get a clear
> answer,
> so I'll ask again here.
> 
> Cheers,
> Julien


CU
Jörg
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAluewxkACgkQCfifPIyh
0l2hrxAAukOnYhcZIW8DUY3k/3f3l+7OcWrZs2fS3nvg3NvxGAVIATksbFXswCAm
o0G+LFRUOrZWwgnIMxTL85acnszIZ3u8RglmWbKjlmK5wJ/d8xeefU4ZizrWHVJY
g7HBI7tgkXk2H2eVmVIMT3B+hiVSBSShpTi1x3Mhq0IYs/1j8dlDNQ7tvU3iPkoU
75UoZQC55JS15CZLE6LAqESqgP9FPtSlAvHdLUqF9hS5jITdUpLr+Fbxg0fYszQq
rw+8+yw6BYumkfGhru4wC9BisxpfL8wjsmNQkeat2H02+X/93NaZvl6TNApe6Any
gCPVRHlAyyEUbfgfONLsGkP2aKV07izc+RSg9jwW5qDat+tM1qjT4MfXxWNnGz22
dKSjcOhudut8807R6M2e/6yJpOPAumXMOLjY7UPmfmgxKsbFsDgCH2+IWL0xFnkG
yGj6zHrjCOzO2zIBmtcxG6CdeYTCp+k95QKKTTQEPG9x9POy9wBjN+HC95r7L7Bh
Ne9yueBoKgSYxXhfuENXvwHJvKfVPAcH6jKlhYUegS0XGTkKliGhCdC4K0clxMA7
Vfph57wuU535j3rZCRI/l1s8vvUxeh4THT597xNMS3U2jz2ksLM9h+PEJy+Lx9hB
yJOdWv0dTvG7C7acflepG1yL3FuDMKauYPVvhz9BADKGcahpCBM=
=C/cV
-END PGP SIGNATURE-

Bug#908970: spamassassin: CVE-2018-11780: potential remote code execution bug with the PDFInfo plugin

[Salvatore Bonaccorso]

Source: spamassassin
Version: 3.4.1-1
Severity: grave
Tags: security

Hi,

The following vulnerability was published for spamassassin.

CVE-2018-11780[0]:
potential remote code execution bug with the PDFInfo plugin

It is fixed in new upstream version 3.4.2.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11780
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11780
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#908971: spamassassin: CVE-2018-11781: local user code injection in the meta rule syntax

[Salvatore Bonaccorso]

Source: spamassassin
Version: 3.4.1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for spamassassin.

CVE-2018-11781[0]:
local user code injection in the meta rule syntax

It is fixed in new upstream version 3.4.2.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11781
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11781
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#908969: spamassassin: CVE-2017-15705: denial of service vulnerability

[Salvatore Bonaccorso]

Source: spamassassin
Version: 3.4.1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for spamassassin.

CVE-2017-15705[0]:
denial of service vulnerability

It is fixed upstream in new 3.4.2 release.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15705
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15705
[1] https://www.openwall.com/lists/oss-security/2018/09/16/1

Please adjust the affected versions in the BTS as needed.



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

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

Processed: tagging 906003

[Debian Bug Tracking System]

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

> tags 906003 + buster sid
Bug #906003 [plowshare-modules] Keep plowshare-modules out of Debian releases
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: found 896204 in 3.4.0-1

[Debian Bug Tracking System]

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

> found 896204 3.4.0-1
Bug #896204 {Done: Federico Ceratto } [python3-gridfs] 
python3-gridfs: gridfs fails to import
Marked as found in versions pymongo/3.4.0-1.
> thanks
Stopping processing here.

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

Bug#908966: libiptcdata0-dev: ships libiptcdata.pc in literally /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig

[Helmut Grohne]

Package: libiptcdata0-dev
Version: 1.0.5-1
Severity: serious
Justification: makes tracker-miners ftbfs
Tags: ftbfs
Control: affects -1 + src:tracker-miners

libiptcdata.pc is now shipped in literally
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig. That is semantically
equivalent to it being absent. Consequently, the autopkgtest for
tracker-miners fails. tracker-miners also fails to build from source.

If you want to use such an expansion in libiptcdata0-dev.install, you
must Build-Depends: dh-exec, add a #! line and make the file executable.

It might be easiert to just add
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) to
DEB_CONFIGURE_EXTRA_FLAGS though.

Helmut

Processed: libiptcdata0-dev: ships libiptcdata.pc in literally /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:tracker-miners
Bug #908966 [libiptcdata0-dev] libiptcdata0-dev: ships libiptcdata.pc in 
literally /usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig
Added indication that 908966 affects src:tracker-miners

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

Bug#861549: marked as done (systemd-docker: FTBFS with latest golang-go.crypto)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 21:28:08 +0200
with message-id <43bbba8f-8c05-486b-04d5-17b4c8527...@debian.org>
and subject line systemd-docker was removed from unstable
has caused the Debian Bug report #861549,
regarding systemd-docker: FTBFS with latest golang-go.crypto
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.)


-- 
861549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Bug #859655 [3] has been fixed in unstable. This addresses a CVE bug, but also
requires all reverse build dependencies be rebuilt. After this package has
migrated to testing, there will be 62-64 packages that need rebuilding as well.

I have run build tests in both unstable and testing for this update using an
amd64 sbuild environment. For reference, the results:

testing:
  success: 62,  failed: 2 (being addressed)
unstable
  success: 107, failed: 7 (unchecked)


For the moment, I need the 107 packages in this list [1] to rebuilt in unstable.
... wanna build? :)

[1]

nmu mtail_0.0+git20161231.ae129e9-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu tendermint-ed25519_0.0~git20160723.0.1f52c6f-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-rsc-letsencrypt_0.0~git20160929.0.76104d2-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-docker-leadership_0.1.0-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu sia_1.0.4-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-samalba-dockerclient_0.0~git20160531.0.a303626-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-golang-x-net-dev_1:0.0+git20160110.4fd4a9f-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu gocryptfs_1.2-2 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-blevesearch-bleve_0.5.0+git20170324.202.4702785f-1 . ANY all 
. unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-endophage-gotuf_0.0~git20151020.0.2df1c8e-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu cadvisor_0.25.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu dnss_0.0~git20161126.0.162090e-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu golang-gopkg-dancannon-gorethink.v2_2.0.4-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu mongo-tools_3.2.11-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-docker-go-connections_0.2.1+git20161115.12.4ccf312-1 . ANY 
all . unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-fsouza-go-dockerclient_0.0+git20160622-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-go-macaron-macaron_1.2.1+git20170219.2.8be5635-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu rkt_1.21.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-coreos-go-systemd_14-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu chasquid_0.01+git20161124.6479138-2 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu minica_1.0-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-pkg-sftp_0.0~git20160930.0.4d0e916-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-spf13-afero_0.0~git20161226.0.90dd71e-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-azure-go-ntlmssp_0.0~git20160412.e0b63eb-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-opencontainers-image-spec_1.0.0~rc2+dfsg-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-couchbase-moss_0.0~git20170330.0.d2258a2-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu tendermint-go-p2p_0.0~git20170113.0.3d98f67-1 . ANY all . unstab

Bug#893792: marked as done (balsa: Unable to send mail since the latest upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 14:58:45 -0400
with message-id 

and subject line Re: Re : Bug#893792: balsa: Unable to send mail since the 
latest upgrade
has caused the Debian Bug report #893792,
regarding balsa: Unable to send mail since the latest upgrade
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.)


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

Dear Maintainer,

Till the latest upgrade, Balsa can’t send mail anymore.
The remote server complains that:
* It doesn’t support STARTTLS when I try with TLS,
* the password is wrong when I try with SSL.
But the password is OK and TLS used to work until yesterday.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages balsa depends on:
ii  libc6   2.27-2
ii  libcairo2   1.15.10-2
ii  libcanberra-gtk3-0  0.30-6
ii  libcanberra00.30-6
ii  libcompfaceg1   1:1.5.2-5+b2
ii  libgdk-pixbuf2.0-0  2.36.11-2
ii  libglib2.0-02.56.0-2
ii  libgmime-2.6-0  2.6.23+dfsg1-2
ii  libgnutls30 3.5.18-1
ii  libgpgme11  1.10.0-2
ii  libgspell-1-1   1.6.1-1
ii  libgssapi-krb5-21.16-2
ii  libgtk-3-0  3.22.29-1
ii  libgtksourceview-3.0-1  3.24.7-1
ii  libldap-2.4-2   2.4.45+dfsg-1
ii  libnotify4  0.7.7-3
ii  libpango-1.0-0  1.40.14-1
ii  libpangocairo-1.0-0 1.40.14-1
ii  libsecret-1-0   0.18.5-6
ii  libsqlite3-03.22.0-2
ii  libssl1.1   1.1.0g-2
ii  libwebkit2gtk-4.0-372.20.0-2
ii  libxml2 2.9.4+dfsg1-6.1
ii  pinentry-gnome3 [pinentry-x11]  1.1.0-1
ii  pinentry-gtk2 [pinentry-x11]1.1.0-1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages balsa recommends:
ii  ca-certificates20170717
ii  gpgsm  2.2.5-1
ii  python3-html2text  2018.1.9-1
ii  yelp   3.26.0-2

balsa suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Sep 16, 2018 at 2:54 PM  wrote:
> Le 16/09/2018 17:23:14, Jeremy Bicha a écrit :
> > Since you reported this bug, there has been a bugfix release (2.5.6)
> > for balsa and many other changes in Debian Unstable. Are you still
> > able to reproduce this issue?
>
> > If so, does 2.5.3-4 from Debian Testing still work?
>
> You can close the bug.--- End Message ---

Bug#893792: Re : Bug#893792: balsa: Unable to send mail since the latest upgrade

[nicolas . patrois]

Le 16/09/2018 17:23:14, Jeremy Bicha a écrit :

> I suspect that no one on the Debian GNOME team uses balsa.

> Since you reported this bug, there has been a bugfix release (2.5.6)
> for balsa and many other changes in Debian Unstable. Are you still
> able to reproduce this issue?

> If so, does 2.5.3-4 from Debian Testing still work?

You can close the bug.

Thank you,
nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Processed: more affects for surefire

[Debian Bug Tracking System]

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

> affects 908535 src:avro-java
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } [libsurefire-java] 
libsurefire-java: Maven pom contains unwanted rules
Added indication that 908535 affects src:avro-java
Added indication that 908536 affects src:avro-java
Added indication that 908537 affects src:avro-java
Added indication that 908542 affects src:avro-java
> affects 908535 src:commons-jcs
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } [libsurefire-java] 
libsurefire-java: Maven pom contains unwanted rules
Added indication that 908535 affects src:commons-jcs
Added indication that 908536 affects src:commons-jcs
Added indication that 908537 affects src:commons-jcs
Added indication that 908542 affects src:commons-jcs
> affects 908535 src:gmbal-pfl
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } [libsurefire-java] 
libsurefire-java: Maven pom contains unwanted rules
Added indication that 908535 affects src:gmbal-pfl
Added indication that 908536 affects src:gmbal-pfl
Added indication that 908537 affects src:gmbal-pfl
Added indication that 908542 affects src:gmbal-pfl
> affects 908535 src:guava-libraries
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } [libsurefire-java] 
libsurefire-java: Maven pom contains unwanted rules
Added indication that 908535 affects src:guava-libraries
Added indication that 908536 affects src:guava-libraries
Added indication that 908537 affects src:guava-libraries
Added indication that 908542 affects src:guava-libraries
> affects 908535 src:guice
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } [libsurefire-java] 
libsurefire-java: Maven pom contains unwanted rules
Added indication that 908535 affects src:guice
Added indication that 908536 affects src:guice
Added indication that 908537 affects src:guice
Added indication that 908542 affects src:guice
> affects 908535 src:jackson-core
Bug #908535 {Done: Emmanuel Bourg } [libsurefire-java] 
aether-ant-tasks: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.9 could not be resolved)
Bug #908536 {Done: Emmanuel Bourg } [libsurefire-java] 
jnr-posix: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1 could not be resolved)
Bug #908537 {Done: Emmanuel Bourg } [libsurefire-java] 
jruby-joni: FTBFS in buster/sid (Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1 could not be resolved)
Bug #908542 {Done: Emmanuel Bourg } 

Processed: tagging 908929

[Debian Bug Tracking System]

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

> tags 908929 + buster sid
Bug #908929 [libpam-google-authenticator] libpam-google-authenticator: 
hardcoded dependency on libqrencode3
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#874526: Keyboard grab doesn't work under Wayland

[Jeremy Bicha]

Control: severity -1 important

On Wed, Sep 6, 2017 at 6:03 PM Josh Triplett  wrote:
> [I don't know whether this bug lies in gnome-boxes or gnome-shell or
> some combination of both. Release-critical because this completely
> breaks the ability to log into many Windows VMs with gnome-boxes under
> the default GNOME Wayland session.]

I am downgrading the severity since there is a workaround in the
keyboard menu in the headerbar.

> The mechanism gnome-boxes uses to grab the keyboard doesn't work under
> the default GNOME Wayland session. This makes it impossible to send
> Ctrl-Alt-Delete; it always goes to gnome-shell instead.

I can't reproduce this bug. Boxes does correctly grab the keyboard and
tells me that it has in its headerbar.

If you look in the Boxes app menu, there is an item called Shortcuts.
If you click it, it tells you that the shortcut for keyboard grab is
Ctrl + L Alt.

I mean have you tried Ctrl + R Alt + Delete ?

If you can still reproduce, please provide a more detailed test case.
What guest OS are you using? How can you tell that Ctrl+Alt+Delete
isn't being sent to the guest?

Thanks,
Jeremy Bicha

Processed: Re: Bug#874526: Keyboard grab doesn't work under Wayland

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #874526 [gnome-boxes] Keyboard grab doesn't (always?) work under Wayland
Severity set to 'important' from 'serious'

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

Bug#895732: marked as done (cogl FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 17:34:24 +
with message-id 
and subject line Bug#895732: fixed in cogl 1.22.2-4
has caused the Debian Bug report #895732,
regarding cogl FTBFS: symbol differences
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.)


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

Some recent change in unstable makes cogl FTBFS:

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/cogl-1.22.2'
dh_makeshlibs -- -c4
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libcogl20/DEBIAN/symbols doesn't match 
completely debian/libcogl20.symbols
--- debian/libcogl20.symbols (libcogl20_1.22.2-3_amd64)
+++ dpkg-gensymbolsWTxDRA   2018-04-14 20:35:38.272738785 -1200
@@ -174,6 +174,7 @@
  cogl_feature_flags_get_type@Base 1.17.4
  cogl_features_available@Base 1.17.4
  cogl_fence_closure_get_user_data@Base 1.17.4
+ cogl_filter_return_get_type@Base 1.22.2-3
  cogl_fixed_atan2@Base 1.17.4
  cogl_fixed_atan@Base 1.17.4
  cogl_fixed_cos@Base 1.17.4
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:43: override_dh_makeshlibs] Error 2
--- End Message ---
--- Begin Message ---
Source: cogl
Source-Version: 1.22.2-4

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated cogl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 13:04:26 -0400
Source: cogl
Binary: libcogl20 libcogl-common libcogl-dev libcogl-doc gir1.2-cogl-1.0 
libcogl-path20 libcogl-path-dev libcogl-pango20 libcogl-pango-dev 
gir1.2-coglpango-1.0 libcogl-gles2-20 libcogl-gles2-dev libcogl-gst20 
libcogl-gst-dev gir1.2-coglgst-2.0
Architecture: source
Version: 1.22.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-cogl-1.0 - GObject introspection data for the Cogl 1.0 library
 gir1.2-coglgst-2.0 - GObject introspection data for the CoglGst 2.0 library
 gir1.2-coglpango-1.0 - GObject introspection data for the CoglPango 1.0 library
 libcogl-common - Object oriented GL/GLES Abstraction/Utility Layer (common 
files)
 libcogl-dev - Object oriented GL/GLES Abstraction/Utility Layer (development fi
 libcogl-doc - Object oriented GL/GLES Abstraction/Utility Layer (documentation)
 libcogl-gles2-20 - Object oriented GL/GLES Abstraction/Utility Layer
 libcogl-gles2-dev - Object oriented GL/GLES Abstraction/Utility Layer 
(development fi
 libcogl-gst-dev - Object oriented GL/GLES Abstraction/Utility Layer 
(development fi
 libcogl-gst20 - Object oriented GL/GLES Abstraction/Utility Layer
 libcogl-pango-dev - Object oriented GL/GLES Abstraction/Utility Layer 
(development fi
 libcogl-pango20 - Object oriented GL/GLES Abstraction/Utility Layer
 libcogl-path-dev - Object oriented GL/GLES Abstraction/Utility Layer 
(development fi
 libcogl-path20 - Object oriented GL/GLES Abstraction/Utility Layer
 libcogl20  - Object oriented GL/GLES Abstraction/Utility Layer
Closes: 895732 905974
Changes:
 cogl (1.22.2-4) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * Update Vcs fields for migration to https://salsa.debian.org/
   * debian/libcogl20.symbols: Add symbol exposed by compiler changes
 (Closes: #895732)
   * Bump Standards-Version to 4.2.1
 .
   [ Simon McVittie ]
   * Remove obsolete Breaks on pre-jessie versions of cogl
   * Add versioned Provides for gir1.2-cogl-2.0 and gir1.2-coglpango-2.0,
 the canonical names for the packages containing Cogl-2.0.typelib and
 CoglPango-2.0.typelib. Note that despite the packages' names, there
 is no Cogl-1.0.typelib or CoglPango-1.0.typelib.
   * Depend on li

Bug#893792: balsa: Unable to send mail since the latest upgrade

[Jeremy Bicha]

On Thu, Mar 22, 2018 at 9:09 AM Nicolas Patrois
 wrote:
> Till the latest upgrade, Balsa can’t send mail anymore.
> The remote server complains that:
> * It doesn’t support STARTTLS when I try with TLS,
> * the password is wrong when I try with SSL.
> But the password is OK and TLS used to work until yesterday.

I suspect that no one on the Debian GNOME team uses balsa.

Since you reported this bug, there has been a bugfix release (2.5.6)
for balsa and many other changes in Debian Unstable. Are you still
able to reproduce this issue?

If so, does 2.5.3-4 from Debian Testing still work?

Thanks,
Jeremy Bicha

Bug#908955: /usr/lib/libglide3.so.3: undefined symbol: __LINE__

[Gianluigi Tiesi]

Package: libglide3
Version: 2002.04.10ds1-12
Severity: grave


I known no one has such a card to test it, but I've just got one
compiling xdraw3.o with -fdollars-in-identifiers causes __LINE__ to became
an undefined symbol even if specifying -x assembler-with-cpp
because is used as $__LINE__


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

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages libglide3 depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-6
ii  libx11-6   2:1.6.6-1
ii  libxext6   2:1.3.3-1+b2
ii  libxxf86dga1   2:1.1.4-1+b3
ii  libxxf86vm11:1.1.4-1+b2
pn  pciutils   

libglide3 recommends no packages.

libglide3 suggests no packages.

Bug#908784: marked as done (nethack: license incompatibility results in non-distributable binaries)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 17:04:23 +
with message-id 
and subject line Bug#908784: fixed in nethack 3.6.1-1
has caused the Debian Bug report #908784,
regarding nethack: license incompatibility results in non-distributable binaries
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.)


-- 
908784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nethack
Version: 3.4.3-14
Severity: serious
X-Debbugs-CC: vch...@debian.org

Hi,

While reviewing the copyright file for the NetHack 3.6.1 upload, I
noticed that the debian directory (and its patches) are marked as under
the GPL-2.0. Unfortunately NetHack's special NGPL license is not
compatible with the GPL (both are copyleft with some conflicting terms),
so I have come to the conclusion that Debian's version of NetHack is not
distributable in binary form at all.

Thankfully I think this can be resolved fairly smoothly. If I look at
the package history, I see that before 3.4.3-14 everything was licensed
under the NGPL (except for the lisp patches). In this version, the
copyright file was changed to relicense(?!) the debian/ directory under
the GPL. Vincent and I are the only people who have claimed copyright
since that point, and I am fine with licensing my stuff under the NGPL,
so Vincent is the only person who needs asking.

Vincent, can all your changes to the nethack package be licensed under
the NGPL instead of the GPL-2.0?

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nethack
Source-Version: 3.6.1-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated nethack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 17:35:42 +0100
Source: nethack
Binary: nethack-common nethack-console nethack-lisp nethack-x11
Architecture: source
Version: 3.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: James Cowgill 
Description:
 nethack-common - dungeon crawl game - common files
 nethack-console - dungeon crawl game - text-based interface
 nethack-lisp - dungeon crawl game - Lisp interface
 nethack-x11 - dungeon crawl game - X11 interface
Closes: 900318 908784
Changes:
 nethack (3.6.1-1) unstable; urgency=medium
 .
   [ James Cowgill ]
   * New upstream release. (Closes: #900318)
 .
   * d/changelog: Remove trailing whitespace.
   * d/clean: Clean dat/gitinfo.txt.
   * d/copyright:
 - Update and list all copyright holders.
 - "Relicense" debian directory under the NGPL. (Closes: #908784)
   * d/compat: Use debhelper 11.
   * d/control:
 - Switch Vcs URLs to salsa.debian.org.
 - Bump standards to 4.2.1.
 - Use secure Homepage URL.
   * d/*.desktop: Add Comment fields to desktop files.
   * d/patches:
 - Refresh patches.
 - Drop u1-avoid-crash-for-long-lines-in-nethackrc.patch - applied upstream.
 - Drop 0005-Simple-mail.patch - no longer applies.
 - Drop 0010-Enables-color-HP-monitor-for-textmode-NetHack - obsolete.
 - Drop 0019-stay-in-array-bounds.patch - fixed upstream.
 - Drop 0023-gcc-warning-fixes.patch - alternative applied upstream.
 - Drop 0025-reproducible-build.patch and enable upstream reproducibility.
 - Add upstream patch to fix sys/unix/setup.sh behavior.
 - Disable SIMPLE_MAIL which now has a slightly different meaning.
 - Fix undefined reference to "terminate" in lisp patch.
 - Fix spelling mistake in 0026-fix-permanently-identify.
   * d/rules:
 - Enable verbose build.
 - Add set -e to for loop.
   * nethackrc: disable hpmon now that the patch has been dropped.
 .
   [ Niels Thykier ]
   * Declare the explicit requirement for (fake)root.
Checksums-Sha1:
 799365a9674d35d985d38fd0f3ac4131b899a984 2417 nethack_3.6.1-1.dsc
 006fc177206f68375a87e17371de5d86555c329f 4640769 nethack_3.6.1.orig.tar.gz
 e1a85dc9e3518a50f44c6f468d8

Bug#906461: florence: diff for NMU version 0.6.3-1.1

[Adrian Bunk]

On Fri, Sep 14, 2018 at 04:48:03PM +0200, Jérémy Bobbio wrote:
> Hi!
> 
> On 14/09/2018 15:51, Adrian Bunk wrote:
> > I've prepared an NMU for florence (versioned as 0.6.3-1.1) and uploaded 
> > it to DELAYED/14. Please feel free to tell me if I should cancel it.
> 
> Thanks!
> 
> Feel free to upload it right away or even take over the package.
> I sadly still haven't found enough time and energy to adjust packages to
> my current (non-)involvement in Debian.

Unfortunately I do not have a personal interest in this package,
I was just fixing some release critical bugs.

But if you want to orphan this package (and other packages?),
I can do the WNPP bug sending so that other people have the
opportunity to adopt.

> Lunar

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#908953: pinball FTBFS with automake 1.16

[Adrian Bunk]

Source: pinball
Version: 0.3.1-14
Severity: serious
Tags: patch ftbfs

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

...
Making all in src
make[3]: Entering directory '/build/1st/pinball-0.3.1/src'
g++ -DHAVE_CONFIG_H -I. -I.. -I../base -I../addon   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  -g -O2 
-ffile-prefix-map=/build/1st/pinball-0.3.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o Pinball.o Pinball.cpp
In file included from /usr/include/c++/8/backward/strstream:50,
 from Pinball.cpp:13:
/usr/include/c++/8/backward/backward_warning.h:32:2: warning: #warning This 
file includes at least one deprecated or antiquated header which may be removed 
without further notice at a future date. Please use a non-deprecated interface 
with equivalent functionality instead. For a listing of replacement headers and 
interfaces, consult the file backward_warning.h. To disable this warning use 
-Wno-deprecated. [-Wcpp]
 #warning \
  ^~~
Pinball.cpp: In function 'MenuItem* createMenus(Engine*)':
Pinball.cpp:566:10: warning: ignoring return value of 'int chdir(const char*)', 
declared with attribute warn_unused_result [-Wunused-result]
 chdir(Config::getInstance()->getDataDir());
 ~^
Pinball.cpp:579:10: warning: ignoring return value of 'int chdir(const char*)', 
declared with attribute warn_unused_result [-Wunused-result]
 chdir(cwd);
 ~^
make[3]: *** No rule to make target '../src/libemilia_pin.a', needed by 
'pinball'.  Stop.
make[3]: Leaving directory '/build/1st/pinball-0.3.1/src'
make[2]: *** [Makefile:535: all-recursive] Error 1


This is likely an old latent bug that would always have caused
problems with parallel building.

Fix is attached.
Description: Fix the src/Makefile.am dependencies
Author: Adrian Bunk 

--- pinball-0.3.1.orig/src/Makefile.am
+++ pinball-0.3.1/src/Makefile.am
@@ -9,7 +9,7 @@ pinlib_LIBRARIES = libemilia_pin.a
 
 INCLUDES = -I../base -I../addon @INCLTDL@
 
-pinball_LDADD = ../src/libemilia_pin.a ../addon/libemilia_addon.a 
../base/libemilia_base.a @LIBLTDL@
+pinball_LDADD = libemilia_pin.a ../addon/libemilia_addon.a 
../base/libemilia_base.a @LIBLTDL@
 pinball_LDFLAGS = -export-dynamic
 
 pinball_SOURCES = Pinball.cpp

Processed: tagging 908290

[Debian Bug Tracking System]

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

> tags 908290 + buster sid
Bug #908290 [zfs-linux] Please package 0.7.11
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: twinkle: diff for NMU version 1:1.10.1+dfsg-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906657 + patch
Bug #906657 [src:twinkle] twinkle: FTBFS in buster/sid (expected type-specifier 
before 'QRegExpValidator')
Added tag(s) patch.
> tags 906657 + pending
Bug #906657 [src:twinkle] twinkle: FTBFS in buster/sid (expected type-specifier 
before 'QRegExpValidator')
Added tag(s) pending.

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

Bug#906657: twinkle: diff for NMU version 1:1.10.1+dfsg-3.1

[Adrian Bunk]

Control: tags 906657 + patch
Control: tags 906657 + pending

Dear maintainer,

I've prepared an NMU for twinkle (versioned as 1:1.10.1+dfsg-3.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru twinkle-1.10.1+dfsg/debian/changelog twinkle-1.10.1+dfsg/debian/changelog
--- twinkle-1.10.1+dfsg/debian/changelog	2018-03-28 04:25:58.0 +0300
+++ twinkle-1.10.1+dfsg/debian/changelog	2018-09-16 19:21:15.0 +0300
@@ -1,3 +1,13 @@
+twinkle (1:1.10.1+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with Qt 5.11,
+thanks to Juhani Numminen. (Closes: #906657)
+  * Remove alternative dependency on the no longer existing
+qtdeclarative5-qtquick2-plugin. (Closes: #904029)
+
+ -- Adrian Bunk   Sun, 16 Sep 2018 19:21:15 +0300
+
 twinkle (1:1.10.1+dfsg-3) unstable; urgency=medium
 
   * Drop unneeded build-deps on qtscript5-dev and qttools5-dev-tools.
diff -Nru twinkle-1.10.1+dfsg/debian/control twinkle-1.10.1+dfsg/debian/control
--- twinkle-1.10.1+dfsg/debian/control	2018-03-28 04:25:58.0 +0300
+++ twinkle-1.10.1+dfsg/debian/control	2018-09-16 19:21:15.0 +0300
@@ -28,7 +28,7 @@
 
 Package: twinkle
 Architecture: any
-Depends: qml-module-qtquick2 | qtdeclarative5-qtquick2-plugin,
+Depends: qml-module-qtquick2,
  twinkle-common (= ${source:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
diff -Nru twinkle-1.10.1+dfsg/debian/patches/0001-Include-QRegExpValidator-explicitly.patch twinkle-1.10.1+dfsg/debian/patches/0001-Include-QRegExpValidator-explicitly.patch
--- twinkle-1.10.1+dfsg/debian/patches/0001-Include-QRegExpValidator-explicitly.patch	1970-01-01 02:00:00.0 +0200
+++ twinkle-1.10.1+dfsg/debian/patches/0001-Include-QRegExpValidator-explicitly.patch	2018-09-16 13:42:02.0 +0300
@@ -0,0 +1,119 @@
+From 4b42755619011c117a76bdf98e417ebedc47e319 Mon Sep 17 00:00:00 2001
+From: Michal Kubecek 
+Date: Wed, 6 Jun 2018 10:07:21 +0200
+Subject: Include  explicitly
+
+Since Qt 5.11, generated ui_getprofilename.h no longer includes QHeaderView
+which breaks the chain that included qvalidator.h in getprofilename.cpp.
+As it feels rather fragile to rely on such indirect includes, let's include
+ explicitly in each file using QRegExpValidator class.
+---
+ src/gui/diamondcardprofileform.cpp | 1 +
+ src/gui/getprofilenameform.cpp | 2 +-
+ src/gui/inviteform.cpp | 1 +
+ src/gui/mphoneform.cpp | 1 +
+ src/gui/numberconversionform.cpp   | 1 +
+ src/gui/syssettingsform.cpp| 1 +
+ src/gui/userprofileform.cpp| 1 +
+ src/gui/wizardform.cpp | 1 +
+ 8 files changed, 8 insertions(+), 1 deletion(-)
+
+diff --git a/src/gui/diamondcardprofileform.cpp b/src/gui/diamondcardprofileform.cpp
+index 6656909..517180b 100644
+--- a/src/gui/diamondcardprofileform.cpp
 b/src/gui/diamondcardprofileform.cpp
+@@ -21,6 +21,7 @@
+ 
+ #include 
+ #include 
++#include 
+ #include "gui.h"
+ #include "diamondcard.h"
+ #include "getprofilenameform.h"
+diff --git a/src/gui/getprofilenameform.cpp b/src/gui/getprofilenameform.cpp
+index 1319e1d..89c715e 100644
+--- a/src/gui/getprofilenameform.cpp
 b/src/gui/getprofilenameform.cpp
+@@ -1,7 +1,7 @@
+ #include "getprofilenameform.h"
+-
+ #include 
+ #include 
++#include 
+ #include "user.h"
+ #include "protocol.h"
+ 
+diff --git a/src/gui/inviteform.cpp b/src/gui/inviteform.cpp
+index 433fb22..2a5b68d 100644
+--- a/src/gui/inviteform.cpp
 b/src/gui/inviteform.cpp
+@@ -7,6 +7,7 @@
+ #include "sys_settings.h"
+ #include 
+ #include 
++#include 
+ 
+ /*
+ Copyright (C) 2005-2009  Michel de Boer 
+diff --git a/src/gui/mphoneform.cpp b/src/gui/mphoneform.cpp
+index 260fda7..c4e3c1d 100644
+--- a/src/gui/mphoneform.cpp
 b/src/gui/mphoneform.cpp
+@@ -54,6 +54,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "buddyform.h"
+ #include "diamondcardprofileform.h"
+ #include "osd.h"
+diff --git a/src/gui/numberconversionform.cpp b/src/gui/numberconversionform.cpp
+index f8ae64c..8481a9b 100644
+--- a/src/gui/numberconversionform.cpp
 b/src/gui/numberconversionform.cpp
+@@ -1,5 +1,6 @@
+ #include "numberconversionform.h"
+ 
++#include 
+ #include "gui.h"
+ 
+ /*
+diff --git a/src/gui/syssettingsform.cpp b/src/gui/syssettingsform.cpp
+index 216af54..355df59 100644
+--- a/src/gui/syssettingsform.cpp
 b/src/gui/syssettingsform.cpp
+@@ -28,6 +28,7 @@
+ #include "twinkle_config.h"
+ #include 
+ #include 
++#include 
+ #include "syssettingsform.h"
+ /*
+  *  Constructs a SysSettingsForm as a child of 'parent', with the
+diff --git a/src/gui/userprofileform.cpp b/src/gui/userprofileform.cpp
+index 28700a6..9ed9209 100644
+---

Processed: block 908903 with 908952

[Debian Bug Tracking System]

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

> block 908903 with 908952
Bug #908903 [zonecheck] zonecheck unusable in buster/sid
908903 was not blocked by any bugs.
908903 was not blocking any bugs.
Added blocking bug(s) of 908903: 908952
> thanks
Stopping processing here.

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

Bug#908784: nethack: license incompatibility results in non-distributable binaries

[James Cowgill]

On 14/09/2018 17:50, Vincent Cheng wrote:
> On Thu, Sep 13, 2018 at 2:51 PM James Cowgill  wrote:
>> Vincent, can all your changes to the nethack package be licensed under
>> the NGPL instead of the GPL-2.0?
> 
> Yes, I'm fine with licensing my changes to nethack under the NGPL as well.

Thanks!
James




signature.asc
Description: OpenPGP digital signature

Bug#906412: marked as done (svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found))

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 14:45:11 +
with message-id 
and subject line Bug#906412: fixed in svn-buildpackage 0.8.7
has caused the Debian Bug report #906412,
regarding svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found)
to be marked as done.

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

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


-- 
906412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:svn-buildpackage
Version: 0.8.6
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_auto_build -i
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1
make[1]: Entering directory '/<>'
po4a-build 
make[1]: po4a-build: Command not found
make[1]: *** [Makefile:10: docbuild] Error 127
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: svn-buildpackage
Source-Version: 0.8.7

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated svn-buildpackage 
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, 16 Sep 2018 15:37:01 +0200
Source: svn-buildpackage
Binary: svn-buildpackage
Architecture: source
Version: 0.8.7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 svn-buildpackage - helper programs to maintain Debian packages with Subversion
Closes: 906412
Changes:
 svn-buildpackage (0.8.7) unstable; urgency=medium
 .
   * QA upload.
   * Include and use a copy of the ancient po4a-build script. (Closes: #906412)
Checksums-Sha1:
 db4cdfcb530f72dd54c81c98934c307bf8a93933 1763 svn-buildpackage_0.8.7.dsc
 31293ee9ed38960f030cb7b44ab05c9b81d93c05 292818 svn-buildpackage_0.8.7.tar.gz
 1576178b93af011ad299ffbaf7167a3421c28e69 5645 
svn-buildpackage_0.8.7_source.buildinfo
Checksums-Sha256:
 6873bc292c4488df9eab4982f5073e6fd054e6cf11791b141f49aa74cffb6443 1763 
svn-buildpackage_0.8.7.dsc
 9e56d7a0da9bbb3f4aa1a33812d8a4d4cbe2397db857a24203e2ed54c3813ff0 292818 
svn-buildpackage_0.8.7.tar.gz
 c02fb62a7da776843be8d21c848ddbb602ab6163bd953d120e284c633ef9a90d 5645 
svn-buildpackage_0.8.7_source.buildinfo
Files:
 e14fb2a9ec5daedd96208d20ff904b56 1763 vcs extra svn-buildpackage_0.8.7.dsc
 6bae0dc437a2e08bb02c66ae9445f964 292818 vcs extra svn-buildpackage_0.8.7.tar.gz
 0a29df10879e0b796e46fbdb8bfb9bfa 5645 vcs extra 
svn-buildpackage_0.8.7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlueYFUQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCFapD/oDe3dk0ZhrsC55XU2XhnIexZqdWRi6Mb7R
lbPcTTcAiAJisNSuC9AXuI1MXMQlEy8k/JQwA12uchRszGxks76sA6JG/hHCHSo6
dTl1fkCiHInryE38HNMvZ0/S/0czQm9gXVISg7P4QfD2jHsiuv636rucvMWD0/ym
YRjhqTGbaz/JOMbN4eCjO8zn8HqJDYQVysxYghtFNDrEy9iY54ktajdNBa/eVqTV
KSzdlj1hCFE5ymjWN1gtcUH3RN/AUjWBgKnXLyc+4/EgWEsuT0q9XRv3rO11MOL5
tBKwdOkXalke5wybZp+dnvix9CzNy3K4tYjqFcXO8ZA7m7a3pewKiFlm+Ao0+Cxs
1

Bug#908942: libio-socket-ssl-perl: FTBFS: Connection refused at t/verify_fingerprint.t line 49 and tests hang

[Damyan Ivanov]

-=| Damyan Ivanov, 16.09.2018 11:44:59 + |=-
> Package: src:libio-socket-ssl-perl
> Version: 2.059-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> https://buildd.debian.org/status/fetch.php?pkg=libio-socket-ssl-perl&arch=all&ver=2.059-3&stamp=1537087640&raw=0
> 
> I am able to reproduce this if I run `prove -lb 
> t/verify_fingerprint.t` several 

The test passes a thousand runs if the server child ignores SIGPIPE, 
so this looks like the TLSv1.3 shutdown problem when the client makes 
a fast SSL shutdown without waiting for the confirmation from the 
server, then exits, then exits and the server sending its confirmation 
gets SIGPIPEd.

Similar problem exhibits in t/public_suffix_ssl.t and if I add there 
an explicit ->close(SSL_fast_shutdown=>0) the test survives a thousand 
runs.

I think that when using TLS 1.3, there should be no "fast" shutdown 
and the client should always wait for the server response. Either 
that, or all the server code should ignore SIGPIPE during shutdown, 
which seems like a hard goal.


-- dam

Processed: tagging 908945

[Debian Bug Tracking System]

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

> tags 908945 + buster sid
Bug #908945 [lxqt-common] lxqt-common is deprecated and should be removed from 
archive after the buster release
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#906412: svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found)

[Andreas Beckmann]

On Sat, 25 Aug 2018 14:21:54 +0200 Johannes Schauer 
wrote:
> Upstream version 0.54 of po4a removed po4a-build:

> Since it is unclear to me what the correct replacement for po4a-build is, I
> contacted upstream about it:
> 
> https://github.com/mquinson/po4a/issues/144
> 
> Since this bug is also still unfixed, I thought that this information might be
> helpful for you as well. :)

For svn-buildpackage I'll just include a copy of po4a-build ... without
trying to understand it. Should be sufficient to keep the ancient
package alive for another release.


Andreas

Bug#908396: firefox-esr: stopped working after upgrade from 59 to 60

[Gianluigi Tiesi]

Package: firefox-esr
Version: 60.2.0esr-1
Followup-For: Bug #908396

I get illegal instruction on AMD Duron 900 mhz

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow 3dnowprefetch vmmcall


crashes here:

0xb354526f  movsd  -0x18(%ebp),%xmm0

looks like an sse/sse2 instruction

if it's not possible to fix, I would suggest at least a note in the readme

Regards


-- Package-specific info:

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.27-6
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-6
ii  libgdk-pixbuf2.0-02.38.0+dfsg-5
ii  libglib2.0-0  2.58.0-3
ii  libgtk-3-03.24.0-3
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.39-1
ii  libpango-1.0-01.42.4-3
ii  libsqlite3-0  3.25.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-6
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.0.2-1+b1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-5
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
ii  libgtk2.0-02.24.32-3

-- no debconf information

Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch

[Thierry]

Package: youtube-dl
Version: 2017.05.18.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the version of youtube-dl that is shipped with stretch does not work
anymore for the youtube website, making the package unusable for some
videos. It should be updated to a more recent version. If this is not
possible by Debian policy, stretch-backport should provide a recent
version.

Best regards,
Thierry


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

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

Versions of packages youtube-dl depends on:
ii  dpkg   1.18.25
ii  python33.5.3-1
ii  python3-pkg-resources  33.1.1-1

Versions of packages youtube-dl recommends:
ii  ca-certificates  20161130+nmu1+deb9u1
ii  curl 7.52.1-5+deb9u7
ii  ffmpeg   7:3.2.12-1~deb9u1
ii  mplayer  2:1.3.0-6
ii  rtmpdump 2.4+20151223.gitfa8646d.1-1+b1
ii  wget 1.18-5+deb9u2

youtube-dl suggests no packages.

-- no debconf information

Bug#898075: marked as done (jack: segfaults at start)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 12:34:53 +
with message-id 
and subject line Bug#898075: fixed in jack 3.1.1+cvs20050801-30
has caused the Debian Bug report #898075,
regarding jack: segfaults at start
to be marked as done.

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

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


-- 
898075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jack
Version: 3.1.1+cvs20050801-29.2+b1
Severity: grave
Justification: renders package unusable

Hello!

I have just found out that jack stopped working in Debian testing.
Last time I used it (around last December, on an up-to-date Debian
testing box), it worked without any glitch.

Now, when I try to encode one audio CD (*any* audio CD, including
one that was successfully encoded in the past), I just get a
segfault, immediately after selecting which FreeDB entry I want to use
(when there is a multiple choice):

  $ jack -Q
  [...]
  Segmentation fault

My /var/log/kern.log says:

  May  6 19:44:10 HOSTNAME kernel: [36919.353320] jack[10063]: segfault at 
7f89 ip 7f89ed5665c1 sp 7ffee93b2398 error 4 in 
libc-2.27.so[7f89ed40d000+1b1000]

My configuration file is:

  $ cat ~/.jack3rc 
  # jackrc-version:31
  ripper:cdparanoia
  base_dir:~/music/CDs
  unusable_chars:[' ', '/', ':', '?', '|', '>', '<']
  replacement_chars:['_', '_', '_', '_', '_', '_', '_']

in case it makes any difference.


Could you please try to reproduce the bug and fix it and/or
forward my bug report upstream, as appropriate?

Thanks for your time!
Bye.



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

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

Versions of packages jack depends on:
ii  cdparanoia   3.10.2+debian-13
ii  libc62.27-3
ii  libncursesw6 6.1+20180210-2
ii  libtinfo66.1+20180210-2
ii  python   2.7.15~rc1-1
ii  python-cddb  1.4-5.3
ii  python-eyed3 0.8.4-2
ii  python-pyvorbis  1.5-4
ii  vorbis-tools 1.4.0-10.1

jack recommends no packages.

jack suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jack
Source-Version: 3.1.1+cvs20050801-30

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

Debian distribution maintenance software
pp.
Francois Mazen  (supplier of updated jack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Aug 2018 22:24:35 +0200
Source: jack
Binary: jack
Architecture: source amd64
Version: 3.1.1+cvs20050801-30
Distribution: unstable
Urgency: medium
Maintainer: Michael Banck 
Changed-By: Francois Mazen 
Description:
 jack   - Rip and encode CDs with one command
Closes: 898075
Changes:
 jack (3.1.1+cvs20050801-30) unstable; urgency=medium
 .
   * Set Francois Mazen as Uploader.
   * Acknowledge NMUs.
   * Remove obsolete cursesmodule python binding (Closes: #898075).
   * Fix trailing whitespace in changelog.
   * Update patches to quilt (3.0).
   * Update debian/copyright to dep5 format.
   * Clean debian/rules.
Checksums-Sha1:
 565a71393c319d14802027bdcc59edda03aaac0a 1870 jack_3.1.1+cvs20050801-30.dsc
 795a0ebbaaa6c9c7b1f84d746e3b83f9ce4716ae 55308 
jack_3.1.1+cvs20050801-30.debian.tar.xz
 3af03b7b45fc65c531cf513c52ba364945d1f7d0 6610 
jack_3.1.1+cvs20050801-30_amd64.buildinfo
 c49fb5e4bc92cd366a94250d92d00181814f559d 89072 
jack_3.1.1+cvs20050801-30_amd64.deb
Checksums-Sha256:
 4ee4b4edfaf02d4db7736e7d7dc0eabfdbc3f98049dffac88474e07939ca258b 1870 
jack_3.1.1+cvs20050801-30.dsc
 bd8dfecfc758922b47220b81fc584425955be7f08718fdd73bc3805308b779ff 55308 
jack_3.1.1+cvs20050801-30.debian.tar.xz
 8acc9f35f3d52b16031fd6f0b32153b3de304408b51ff16d0723f67900b3f58c 6610 
jack_3.1.1+cvs20050801-30_amd64.buildinfo
 ba381e495b2687edaad

Bug#908945: lxqt-common is deprecated and should be removed from archive after the buster release

[Alf Gaida]

Package: lxqt-common
Severity: serious

Note to myself,

set the bug to serious to prevent inclusion in buster.
Normally the package should be removed from testing before the release without
further actions.

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

Kernel: Linux 4.19.0-rc3-siduction-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxqt-common depends on:
ii  libfile-mimeinfo-perl  0.29-1
ii  x11-utils  7.7+4

Versions of packages lxqt-common recommends:
ii  breeze-cursor-theme 4:5.13.4-1
ii  breeze-icon-theme   4:5.49.0-1
ii  chameleon-cursor-theme  0.5-7
ii  faenza-icon-theme   1.3.1-2
ii  fonts-hack-ttf  3.003-1
ii  fonts-noto  20171026-2
ii  oxygen-icon-theme   5:5.49.0-1
ii  xfwm4-theme-breeze  1.0.0-1

lxqt-common suggests no packages.

Bug#905155: libtss-dev: missing Depends: libtss0 (= ${binary:Version})

[Luca Boccassi]

On Wed, 01 Aug 2018 02:00:14 +0200 Andreas Beckmann 
wrote:
> Package: libtss-dev
> Version: 1045-1.1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> From the attached log (scroll to the bottom...):
> 
> 0m25.8s ERROR: FAIL: Broken symlinks:
>   /usr/lib/i386-linux-gnu/libtss.so -> libtss.so.0
> 
> 
> cheers,
> 
> Andreas

Dear Maintainer (and Sponsor),

I have uploaded to DELAYED/10 an NMU fixing #905155 and #871705. The
debdiff is inlined below.

Please let me know if you would like me to cancel it.

Thank you.

-- 
Kind regards,
Luca Boccassi


diff -Nru tss2-1045/debian/changelog tss2-1045/debian/changelog
--- tss2-1045/debian/changelog  2018-03-24 13:42:22.0 +
+++ tss2-1045/debian/changelog  2018-09-16 13:01:30.0 +0100
@@ -1,3 +1,11 @@
+tss2 (1045-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing dependency libtss-dev -> libtss0. (Closes: #905155)
+  * Add patch max_path.patch to fix FTBFS on hurd-i386. (Closes: #871705)
+
+ -- Luca Boccassi   Sun, 16 Sep 2018 13:01:30 +0100
+
 tss2 (1045-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tss2-1045/debian/control tss2-1045/debian/control
--- tss2-1045/debian/control2017-07-24 23:02:43.0 +0100
+++ tss2-1045/debian/control2018-09-16 12:43:52.0 +0100
@@ -36,7 +36,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: no
-Depends: ${misc:Depends}
+Depends: ${misc:Depends}, libtss0 (= ${binary:Version})
 Description: Development headers for IBM's TSS 2.0
  Development headers for IBM's TSS 2.0.  You will need this in order
  to build TSS 2.0 applications. In addition, it contains documentation
diff -Nru tss2-1045/debian/patches/max_path.patch 
tss2-1045/debian/patches/max_path.patch
--- tss2-1045/debian/patches/max_path.patch 1970-01-01 01:00:00.0 
+0100
+++ tss2-1045/debian/patches/max_path.patch 2018-09-16 13:00:59.0 
+0100
@@ -0,0 +1,34 @@
+Author: Luca Boccassi 
+Description: fix FTBFS on hurd-i386
+ Hurd does not define PATH_MAX/MAXPATHLEN, so define 4096 as a fallback.
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871705
+Forwarded: https://sourceforge.net/p/ibmtpm20tss/mailman/message/36416364/
+--- a/utils/imalib.h
 b/utils/imalib.h
+@@ -49,6 +49,11 @@
+ 
+ #include 
+ 
++/* Debian/Hurd does not define MAXPATHLEN */
++#ifndef MAXPATHLEN
++#define MAXPATHLEN 4096
++#endif
++
+ #define IMA_PCR   10
+ 
+ /* FIXME need better error codes */
+--- a/utils/ekutils.c
 b/utils/ekutils.c
+@@ -67,7 +67,12 @@
+ 
+ /* windows apparently uses _MAX_PATH in stdlib.h */
+ #ifndef PATH_MAX
++#ifdef _MAX_PATH
+ #define PATH_MAX _MAX_PATH
++#else
++/* Debian/Hurd does not define MAX_PATH */
++#define PATH_MAX 4096
++#endif
+ #endif
+ 
+ /* The print flag is set by the caller, depending on whether it wants 
information displayed.
diff -Nru tss2-1045/debian/patches/series tss2-1045/debian/patches/series
--- tss2-1045/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ tss2-1045/debian/patches/series 2018-09-16 12:20:50.0 +0100
@@ -0,0 +1 @@
+max_path.patch

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

Bug#908942: libio-socket-ssl-perl: FTBFS: Connection refused at t/verify_fingerprint.t line 49 and tests hang

[Damyan Ivanov]

Package: src:libio-socket-ssl-perl
Version: 2.059-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libio-socket-ssl-perl&arch=all&ver=2.059-3&stamp=1537087640&raw=0

I am able to reproduce this if I run `prove -lb t/verify_fingerprint.t` several 
hundred times in a row, but I can't figure out what could be wrong.

Some times the test hangs, with parent calling wait(-1) and child doing 
accept(). Some times the test fails without hanging.

The test spawns two child processes, each one listening on a random port 
(chosen by the OS). The listen() call happens before the fork(), so it seems to 
me that a later connection attempt from the parent cannot fail.

The listen queue is set to 10, and each of the children is being connected less 
than 10 times.

The child processes are designed to exit when they are connected and 
disconnected without any data being sent. Perhaps this causes one of them to 
exit before the parent does its tests, but what other process makes that 
connection is a mistery.

I'll try adding some debugging output to the children and see if this "foreigh" 
connection attempt is the reason.


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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: clean
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#908678: security-tracker - Breaks salsa.d.o

[Bastian Blank]

Hi Salvatore

On Thu, Sep 13, 2018 at 01:37:35PM +0200, Salvatore Bonaccorso wrote:
> Do you have any hints at us on what we could look at to faciliate/help
> more salsa maintainers?

Please try to fork that repo.  Git will take a long time to resolve
deltas.  This is due to Git not handling very well the one file appended
in every revision.  To fix it for all times this file needs to be split
up.  With that change in place the repo needs to be rewritten.

We have even one fork of this repo where blobs are missing.

> What is actually this old diff formater problem you mentioned which
> going to be solved? Would it in the meantime help to make the access
> only for logged in users/restricted?

For some requests the diff formatter blocks and runs into the one minute
hard timeout.  This should be fixed with the 11.3 release next week, so
we can ignore that.

Regards,
Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown

Bug#880497: pytimechart: missing dependencies

[Hans Joachim Desserud]

Since this bug was filed initially, kiwisolver has been packaged in
Debian [1]. So a dependency on python-kiwisolver should resolve that
part.

Also, pytimechart seems to have an indirect dependency on
python-fonttools now, I am at least not able to remove fonttools
without apt also removing pytimechart.

[1] https://tracker.debian.org/pkg/kiwisolver

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#908941: rpyc FTBFS: test_registry.TestUdpRegistry failures

[Adrian Bunk]

Source: rpyc
Version: 4.0.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=rpyc&arch=all&ver=4.0.2-2&stamp=1536269574&raw=0

...
I: pybuild pybuild:269: mkdir 
/<>/.pybuild/cpython3_3.7_rpyc/build/bin; cp bin/rpyc_classic.py 
bin/rpyc_registry.py /<>/.pybuild/cpython3_3.7_rpyc/build/bin
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_rpyc/build; 
python3.7 -m nose tests
SS...FFS.S.SSSS
==
FAIL: test_api (test_registry.TestUdpRegistry)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.7_rpyc/build/tests/test_registry.py", 
line 35, in test_api
self.assertEqual(set(p for _, p in res), set(expected))
AssertionError: Items in the second set but not the first:
12345
45678
 >> begin captured logging << 
REGSRV/UDP/18811: DEBUG: server started on 0.0.0.0:18811
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGSRV/UDP/18811: DEBUG: stopping server...
REGSRV/UDP/18811: DEBUG: server closed
- >> end captured logging << -

==
FAIL: test_pruning (test_registry.TestUdpRegistry)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.7_rpyc/build/tests/test_registry.py", 
line 48, in test_pruning
self.assertEqual(set(p for _, p in res), set((17171,)))
AssertionError: Items in the second set but not the first:
17171
 >> begin captured logging << 
REGSRV/UDP/18811: DEBUG: server started on 0.0.0.0:18811
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGSRV/UDP/18811: DEBUG: stopping server...
REGSRV/UDP/18811: DEBUG: server closed
- >> end captured logging << -

--
Ran 47 tests in 54.010s

FAILED (SKIP=12, failures=2)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_rpyc/build; python3.7 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.7 3.6" 
returned exit code 13


Looking at the changelog, I'd suspect this might be caused by
  * Remove TestUdpRegistry patch rejected upstream

Bug#897223: kmodpy: diff for NMU version 0.1.10-2.1

[Adrian Bunk]

Control: tags 897223 + patch
Control: tags 897223 + pending

Dear maintainer,

I've prepared an NMU for kmodpy (versioned as 0.1.10-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru kmodpy-0.1.10/debian/changelog kmodpy-0.1.10/debian/changelog
--- kmodpy-0.1.10/debian/changelog	2015-07-03 11:57:57.0 +0300
+++ kmodpy-0.1.10/debian/changelog	2018-09-16 13:26:10.0 +0300
@@ -1,3 +1,10 @@
+kmodpy (0.1.10-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Remove the incorrect Multi-Arch: same. (Closes: #897223)
+
+ -- Adrian Bunk   Sun, 16 Sep 2018 13:26:10 +0300
+
 kmodpy (0.1.10-2) unstable; urgency=medium
 
   * Bump S-V to 3.9.6.
diff -Nru kmodpy-0.1.10/debian/control kmodpy-0.1.10/debian/control
--- kmodpy-0.1.10/debian/control	2015-07-06 13:39:14.0 +0300
+++ kmodpy-0.1.10/debian/control	2018-09-16 13:26:03.0 +0300
@@ -11,7 +11,6 @@
 
 Package: python-kmodpy
 Architecture: linux-any
-Multi-Arch: same
 Depends: ${misc:Depends}, ${python:Depends}, libkmod2 (>=18-1)
 Description: Python binding for kmod
  The libkmod2 is a library that provides an API for insertion, removal,

Processed: block 904615 with 907716

[Debian Bug Tracking System]

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

> block 904615 with 907716
Bug #904615 {Done: Carl Suster } [python3-rpyc] 
python3-rpyc: fails to install with Python 3.7
904615 was blocked by: 906719
904615 was blocking: 902788
Added blocking bug(s) of 904615: 907716
> thanks
Stopping processing here.

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

Processed: kmodpy: diff for NMU version 0.1.10-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 897223 + patch
Bug #897223 [python-kmodpy] python-kmodpy breaks package system in multiarch 
setting
Added tag(s) patch.
> tags 897223 + pending
Bug #897223 [python-kmodpy] python-kmodpy breaks package system in multiarch 
setting
Added tag(s) pending.

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

Bug#902506: marked as done (node-husl: FTBFS in buster/sid (uglifyjs: not found))

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 10:07:30 +
with message-id 
and subject line Bug#902506: fixed in node-husl 6.0.1+dfsg-2
has caused the Debian Bug report #902506,
regarding node-husl: FTBFS in buster/sid (uglifyjs: not found)
to be marked as done.

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

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


-- 
902506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-husl
Version: 6.0.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-husl-6.0.1+dfsg'
dh_auto_build
make -j1
make[2]: Entering directory '/<>/node-husl-6.0.1+dfsg'
coffee --compile husl.coffee
make[2]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
make husl.min.js
make[2]: Entering directory '/<>/node-husl-6.0.1+dfsg'
uglifyjs husl.js > husl.min.js
/bin/sh: 1: uglifyjs: not found
Makefile:5: recipe for target 'husl.min.js' failed
make[2]: *** [husl.min.js] Error 127
make[2]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/node-husl-6.0.1+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-husl
Source-Version: 6.0.1+dfsg-2

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-husl 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, 16 Sep 2018 15:15:57 +0530
Source: node-husl
Binary: node-husl libjs-husl
Architecture: source
Version: 6.0.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 libjs-husl - Human-friendly HSL - Javascript
 node-husl  - Human-friendly HSL - NodeJS
Closes: 902506
Changes:
 node-husl (6.0.1+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Add uglifyjs to build deps (Closes: #902506)
 (Thanks to Hans Joachim Desserud)
   * Bump debhelper compatibility level to 11
   * Bump Standards-Version to 4.2.1 (no changes needed)
   * Change section to javascript
   * Enable nocheck build profile
   * Use salsa.debian.org in Vcs-* fields
Checksums-Sha1:
 d3e79eeb1938199d051359f76a996c2af42d1f88 2098 node-husl_6.0.1+dfsg-2.dsc
 354cbf13a2a836c67348590cc0acbd6d4647b318 2736 
node-husl_6.0.1+dfsg-2.debian.tar.xz
 265205401c08044ef517aec8a79be1045d9ab66f 9015 
node-husl_6.0.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 5a67a76609da57ffd6aaaebb335a754f0bda616ffee0bd30e15147bd9d560087 2098 
node-husl_6.0.1+dfsg-2.dsc
 e0b5f4e488005a80db7d5229244adebed87cf0d76682afb7c0ec349eccaed043 2736 
node-husl_6.0.1+dfsg-2.debian.tar.xz
 5a3060f97649d3f0ac372c987372b966488918ebe527b7cc0b1c34f7330054fb 9015 
node-husl_6.0.1+dfsg-2_source.buildinfo
Files:
 97b09a32d4a93d02b6a543323439f85c 2098 javascript optional 
node-husl_6.0.1+dfsg-2.dsc
 0bf40944ea6f1a9cdaa8d2b8e2979175 2736 javascript optional 
node-husl_6.0.1+dfsg-2.debian.tar.xz
 29efba24c

Processed: Re: [zfs-linux] Please package 0.7.10

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #908290 [zfs-linux] Please package 0.7.11
Severity set to 'serious' from 'important'

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

Processed: Re: node-husl: FTBFS in buster/sid (uglifyjs: not found)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #902506 [src:node-husl] node-husl: FTBFS in buster/sid (uglifyjs: not found)
Added tag(s) patch.

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

Bug#902506: node-husl: FTBFS in buster/sid (uglifyjs: not found)

[Hans Joachim Desserud]

Control: tags -1 patch

Looks like it needs uglifyjs added to build dependencies.
(See attached patch)

--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index 68a92dd..f390863 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,8 @@ Build-Depends: debhelper (>= 9),
nodejs,
mocha,
coffeescript,
-   node-underscore
+   node-underscore,
+   uglifyjs
 Standards-Version: 3.9.8
 Homepage: http://www.husl-colors.org
 Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-husl.git

Bug#871343: dummydroid: FTBFS

[Hans Joachim Desserud]

Control: tags -1 patch

I am unable to reproduce the original FTBFS issue and error message 
here.

The current version of maven-assembly-plugin in Unstable has since been
updated to 3.1.0 so that might have changed something. There's also the
fact that a new version of dummydroid has been uploaded to Unstable, so
either (or both) of these might have resolved it.

However, dummydroid currently fails to build due to a different issue.
It seems to be missing a build dependency on junit (see attached patch)
With this in place, I was able to successfully build dummydroid in a
pbuilder environment.

So while the original issue is no longer reproducible, the package
still suffers from FTBFS without the attached patch. Presumably
this issue could be closed when the patch is added and the package
builds successfully again? :)

--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index a89aff6..5c5c06a 100644
--- a/debian/control
+++ b/debian/control
@@ -7,6 +7,7 @@ Build-Depends: cdbs,
debhelper (>= 9),
default-jdk,
javahelper,
+   junit,
libmaven-assembly-plugin-java,
libprotobuf-java,
maven-debian-helper (>= 1.5~)

Processed: Re: dummydroid: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #871343 [src:dummydroid] dummydroid: FTBFS: [ERROR] Failed to 
execute goal 
org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single 
(make-assembly) on project dummydroid: Execution 
make-assembly of goal 
org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single failed: A required 
class was missing while executing 
org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single: 
org/codehaus/plexus/util/MatchPatterns
Added tag(s) patch.

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

Processed: bug 897658 is forwarded to https://gitlab.com/m2crypto/m2crypto/issues/234

[Debian Bug Tracking System]

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

> forwarded 897658 https://gitlab.com/m2crypto/m2crypto/issues/234
Bug #897658 [src:m2crypto] m2crypto: FTBFS against openssl 1.1.1
Set Bug forwarded-to-address to 
'https://gitlab.com/m2crypto/m2crypto/issues/234'.
> thanks
Stopping processing here.

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

Processed: affects 908884

[Debian Bug Tracking System]

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

> affects 908884 src:i2p
Bug #908884 [libtomcat8-java] i2p: FTBFS (autobuilder hangs)
Added indication that 908884 affects src:i2p
> thanks
Stopping processing here.

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

Bug#859795: marked as done (python-cgcloud: dependency python-bd2k is not yet in the archive)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 10:43:14 +0200
with message-id <762eae5604591728a5401eaf35440...@webmail.domeneshop.no>
and subject line Re: python-cgcloud: dependency python-bd2k is not yet in the 
archive
has caused the Debian Bug report #859795,
regarding python-cgcloud: dependency python-bd2k is not yet in the archive
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.)


-- 
859795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cgcloud
Version: 1.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-cgcloud-lib python-cgcloud-core

python-cgcloud-core/amd64 unsatisfiable Depends: python-bd2k
python-cgcloud-lib/amd64 unsatisfiable Depends: python-bd2k
python-cgcloud-core/i386 unsatisfiable Depends: python-bd2k
python-cgcloud-lib/i386 unsatisfiable Depends: python-bd2k
--- End Message ---
--- Begin Message ---

Version: 1.6.0-1

While looking through the list of RC-bugs, I found that this issue is
resolved. https://tracker.debian.org/pkg/python-bd2k is now available
in Debian, and I was successfully able to build python-cgcloud in a
pbuilder environment. :)

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org--- End Message ---

Bug#891988: marked as done (missing entry in debian/copyright)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 08:34:32 +
with message-id 
and subject line Bug#891988: fixed in gtimelog 0.11-5
has caused the Debian Bug report #891988,
regarding missing entry in debian/copyright
to be marked as done.

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

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


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

Package: gtimelog
Version: 0.11-4
Severity: serious
thanks

Dear Maintainer,

please add the missing licenses of:
 gtimelog-0.11/src/gtimelog/help/C/*
to debian/copyright.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: gtimelog
Source-Version: 0.11-5

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated gtimelog 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, 16 Sep 2018 10:28:45 +0200
Source: gtimelog
Binary: gtimelog
Architecture: source
Version: 0.11-5
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Andrej Shadura 
Description:
 gtimelog   - time logging application
Closes: 891988
Changes:
 gtimelog (0.11-5) unstable; urgency=medium
 .
   * Update debian/copyright (Closes: #891988).
Checksums-Sha1:
 313b3045dfa1835a7a09a64552b48a231a2cabf4 1773 gtimelog_0.11-5.dsc
 be9329841d71c4f99778aadade8f6a2aeda956c8 13188 gtimelog_0.11-5.debian.tar.xz
Checksums-Sha256:
 91ab5a71db35584cda9207033eba7212da81970a6f58aa9d4ee5ca4b4c1bb66a 1773 
gtimelog_0.11-5.dsc
 39475e53556d9adb0954f1d2b584e1208147109ecd348b5dd3b7f7fdac1c2057 13188 
gtimelog_0.11-5.debian.tar.xz
Files:
 4afeec02c66ada5f55cf82bfa6588980 1773 admin optional gtimelog_0.11-5.dsc
 c55674a46388f678d5a5db0583fd3622 13188 admin optional 
gtimelog_0.11-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlueFLkACgkQXkCM2RzY
OdKpnAf+NLh218lJxh7ePPczHfioBHM4mnjvIJGpSuRBDtIplqOXqxh0pep4WyD1
A2ATXSHY6Z2uso5xW8uF6ziVyr80c/3WE9y4GP/HurWzB4N4aoE+KuEhgExRqoyY
akAOt+LvcSyNFYLnqxXArbXXd3JDmBVgik2TvXrOrr1kUDGiBxXi9/ZKLXV+BlXU
E693wWsoa8XkVl3gGjlXVqxH+FhAcqmUrL6VQ5NZ8KLueGiJSz+hVpyZaMV9hgUO
nILMVJpZxqTqmgrqZ1CeVJf10/ov2oD8ZPyjS4HzNC3WZNDNVeI/++uXlirwnMg8
B5xmZzYNCZM+zMbZ2bK7wwXWanRs4A==
=LkDF
-END PGP SIGNATURE End Message ---

Bug#908910: marked as done (libdumbnet FTBFS with debhelper 11.4: dh_prep: Unknown option: k)

[Debian Bug Tracking System]

Your message dated Sun, 16 Sep 2018 07:49:15 +
with message-id 
and subject line Bug#908910: fixed in libdumbnet 1.12-8
has caused the Debian Bug report #908910,
regarding libdumbnet FTBFS with debhelper 11.4: dh_prep: Unknown option: k
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.)


-- 
908910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdumbnet
Version: 1.12-7
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/libdumbnet.html

...
dh_testdir
dh_prep -k
Unknown option: k
dh_prep: unknown option or error during option parsing; aborting
make: *** [debian/rules:20: configure-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: libdumbnet
Source-Version: 1.12-8

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated libdumbnet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 07:24:55 +
Source: libdumbnet
Binary: libdumbnet1 libdumbnet-dev python-dumbnet
Architecture: source
Version: 1.12-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Niels Thykier 
Description:
 libdumbnet-dev - dumb, portable networking library -- development files
 libdumbnet1 - dumb, portable networking library -- shared library
 python-dumbnet - dumb, portable networking library -- python bindings
Closes: 908910
Changes:
 libdumbnet (1.12-8) unstable; urgency=medium
 .
   * QA upload.
   * Correct the placement and the call to dh_prep.  (Closes: #908910)
   * Use dh_auto_{configure,build,install} as they know how to pass
 cross-building information to the upstream build system.
   * Set Rules-Requires-Root to "no".
   * Remove duplicated Build-Depends on autoconf.
Checksums-Sha1:
 389d08987c680b369b66554e08bf74ddf5a1a700 1965 libdumbnet_1.12-8.dsc
 076cc30cd59f04105bd9947e6356d43f1d1aa8dd 11207 libdumbnet_1.12-8.diff.gz
 fe36a61f31828a3363d1e76e8458773b1ec96736 5206 
libdumbnet_1.12-8_source.buildinfo
Checksums-Sha256:
 7123cb06ad81be88ca27c3065ea25b65bc83ca98b5fba2c4c06f35608fa0f520 1965 
libdumbnet_1.12-8.dsc
 c7a65a4427adf188661159bb0162452b5fea6e6ff387b086247fb1940689646d 11207 
libdumbnet_1.12-8.diff.gz
 75b3eb4f55582e9f2bd1960b1ee95bfbb9594e89cc41bf055bff4cdade5e2b27 5206 
libdumbnet_1.12-8_source.buildinfo
Files:
 d5b35a8c81328a4e6f81977b8c78d9e4 1965 libs optional libdumbnet_1.12-8.dsc
 6540af9a6e7ad0f4156c9c764c556888 11207 libs optional libdumbnet_1.12-8.diff.gz
 3fecda3363044ba6a3ebee3db60d3ee1 5206 libs optional 
libdumbnet_1.12-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAlueBewSHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqsAC8P/iXDUgQeKzT3kRUeygte1yS2i+GkEaJT
Bq1ZoOkrv91McSDWlR4p8p0vKsLJCYFAmFBtOKTnoptH0ngZ1pMt7DY7T9+GNMrd
a75S3UJ5i/wf9R3fafkUoOScxwXVZ9KMZOILy6j0nB37KWqS6DVgu8UNr6TUSGNH
OXFzlBzrZ/E0LNyQi0zFvK4J4Nn8e+muaIAwq5CQ0Xr5t90IHqtW/R67UsfsnQ29
dM49IiAcMmRr3z34WrsJVG/r1HnoaX/PWbaNX+Xh/yr+QP8+lgAuIdgW4uBTsqGX
MOtGC76DAyExy9bkjhyID0Y2ez8t5suYw5eZBoYmMh20Ky0hkfLDtMZ1BE/4fAF/
bWXSJtpCwWw4+7HhCRS50FZiQ/7Feb03SNJYkZUr0M5F2TDeujY9T4vj+LdT/k9j
N1hFdlVuZoX8kF5fycjskmKxp7nv2vWoP2Z2Ku06CjeA9ZoDKfDo6xLcPu1c26H1
mfFpgcYzVmOSzoppvq6r/nyD+CLuj0J35NHgeo2HHj05OvsiAVfMyJQd5Dmp+B8y
Ibpj3eYdiD8Dwa7OAe9p1gFKZoltIshOEMkl5tdgIYvBpG/BR8NA1qnydH1mCPb1
LeFR0FCA/kkPdcNLcbHmb0V0d60XmBD2coHEW+ZP+VFrtz08ZWDQ6tT6rqOmQirx
RUV3sjXHGM9S
=6G6A
-END PGP SIGNATURE End Message ---

Bug#908670: libundead: ftbfs on armhf

[peter green]

On 13/09/18 21:49, Andreas Tille wrote:

Hi Peter,

thanks a lot for your analysis.

On Thu, Sep 13, 2018 at 01:27:58PM +0100, peter green wrote:

4. Simply get libundead removed on armhf/raspbian. libundead seems to only have 
two reverse build-dependencies neither of which has ever successfully built on 
armhf. libbiod previously failed with a testsuite failure (probablly related to 
the miscompilation discussed above) and now fails with the same error that 
libundead does. sambamba is blocked by a dependency on libbiod

I think this solution makes the least effort for all involved parties
and is in line with the practical use of this package on armhf.

I went ahead and filed the removal request 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908920

Bug#908929: libpam-google-authenticator: hardcoded dependency on libqrencode3

[peter green]

Package: libpam-google-authenticator
Severity: serious
Tags: patch

libpam-google-authenticator depends on libqrencode3, which has no longer built 
from the qrencode source package. It has been replaced by libqrencode4. This 
dependency is hard coded and does not change after a re-build. Looking at the 
code it seems that libqrencode is used via dlopen/dlsym.

The two functions used don't seem to have changed in ABI, so afaict it should 
be ok to add the new .4 version to the list of sonames to try in the upstream 
code and change debian/control

I have attached a debdiff that makes the aforementioned changes, I have tested 
the package builds with the debdiff but I have not tested it beyond that.

diff -Nru google-authenticator-20170702/debian/changelog 
google-authenticator-20170702/debian/changelog
--- google-authenticator-20170702/debian/changelog  2017-07-02 
10:02:29.0 +
+++ google-authenticator-20170702/debian/changelog  2018-09-16 
07:31:09.0 +
@@ -1,3 +1,10 @@
+google-authenticator (20170702-1.1) UNRELEASED; urgency=medium
+
+  * Patch proposed to BTS, no intent to NMU
+  * update for libqrcode4.
+
+ -- Peter Michal Green   Sun, 16 Sep 2018 07:31:09 +
+
 google-authenticator (20170702-1) unstable; urgency=medium
 
   * Upstream update (00065df) (Closes: #864187).
diff -Nru google-authenticator-20170702/debian/control 
google-authenticator-20170702/debian/control
--- google-authenticator-20170702/debian/control2016-06-07 
17:49:06.0 +
+++ google-authenticator-20170702/debian/control2018-09-16 
07:31:01.0 +
@@ -8,7 +8,7 @@
 
 Package: libpam-google-authenticator
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libqrencode3
+Depends: ${shlibs:Depends}, ${misc:Depends}, libqrencode4
 Description: Two-step verification
  The Google Authenticator project includes implementations of one-time
  passcode generators for several mobile platforms, as well as a
diff -Nru google-authenticator-20170702/debian/patches/libqrencode4.patch 
google-authenticator-20170702/debian/patches/libqrencode4.patch
--- google-authenticator-20170702/debian/patches/libqrencode4.patch 
1970-01-01 00:00:00.0 +
+++ google-authenticator-20170702/debian/patches/libqrencode4.patch 
2018-09-16 07:31:09.0 +
@@ -0,0 +1,18 @@
+Description: Add support for libqrencode4 and make it the first choice.
+Author: Peter Michal Green 
+Last-Update: 2018-09-16
+
+--- google-authenticator-20170702.orig/libpam/src/google-authenticator.c
 google-authenticator-20170702/libpam/src/google-authenticator.c
+@@ -203,7 +203,10 @@ static const char *getURL(const char *se
+ 
+ // Display QR code visually. If not possible, return 0.
+ static int displayQRCode(const char* url) {
+-  void *qrencode = dlopen("libqrencode.so.2", RTLD_NOW | RTLD_LOCAL);
++  void *qrencode = dlopen("libqrencode.so.4", RTLD_NOW | RTLD_LOCAL);
++  if (!qrencode) {
++qrencode = dlopen("libqrencode.so.2", RTLD_NOW | RTLD_LOCAL);
++  }
+   if (!qrencode) {
+ qrencode = dlopen("libqrencode.so.3", RTLD_NOW | RTLD_LOCAL);
+   }
diff -Nru google-authenticator-20170702/debian/patches/series 
google-authenticator-20170702/debian/patches/series
--- google-authenticator-20170702/debian/patches/series 2016-06-07 
16:17:33.0 +
+++ google-authenticator-20170702/debian/patches/series 2018-09-16 
07:31:09.0 +
@@ -0,0 +1 @@
+libqrencode4.patch

Bug#895320: re: ps2pdf crashes

[Andrej Shadura]

On Sat, 15 Sep 2018 12:51:40 +0200 Jonas Smedegaard  wrote:
> Quoting Jonas Smedegaard (2018-09-14 22:33:14)
> > A new release of ghostscript is now in experimental.
> > 
> > Could you please help test if that succeeds?
> 
> Didn't help.  But neither do downgrading to 9.22~dfsg-2.1 in unstable 
> since 2018-04-20.  Seems the cause of this is somewhere else than 
> ghostscript.
> 
> texlive, perhaps?

Ha, I haven’t seen this. Hmm, interesting.

-- 
Cheers,
  Andrej

Processed: tagging 908910

[Debian Bug Tracking System]

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

> tags 908910 + sid buster
Bug #908910 [src:libdumbnet] libdumbnet FTBFS with debhelper 11.4: dh_prep: 
Unknown option: k
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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