Bug#905472: libtextwrap FTBFS: cannot find -ltextwrap

[Helmut Grohne]

On Sun, Aug 05, 2018 at 07:31:55AM +0200, Helmut Grohne wrote:
> libtextwrap fails to build from source on amd64 in unstable. A build log
> ends with:
> 
> | touch configure-stamp
> | dh_testdir
> | /usr/bin/make
> | make[1]: Entering directory '/<>'
> | /usr/bin/make  all-am
> | make[2]: Entering directory '/<>'
> | gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -MT dotextwrap.o -MD -MP -MF .deps/dotextwrap.Tpo -c 
> -o dotextwrap.o dotextwrap.c
> | mv -f .deps/dotextwrap.Tpo .deps/dotextwrap.Po
> | /bin/bash ./libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wl,-z,relro -o dotextwrap dotextwrap.o -ltextwrap 
> | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -o 
> dotextwrap dotextwrap.o  -ltextwrap
> | /usr/bin/ld: cannot find -ltextwrap
> | collect2: error: ld returned 1 exit status
> | make[2]: *** [Makefile:515: dotextwrap] Error 1
> | make[2]: Leaving directory '/<>'
> | make[1]: *** [Makefile:373: all] Error 2
> | make[1]: Leaving directory '/<>'
> | make: *** [debian/rules:56: build-stamp] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
> 
> This looks very strange and more of a breakage of makefile dependencies.
> It didn't even try building -ltextwrap and links it already. The issue
> is reproducible without parallelism. I haven't seen it until "recently"
> though since meson and then pcre3 have fucked up bootstrap qa lately,
> "recently" means like two weeks here though reproducible builds didn't
> encounter the issue (yet?). The make-dfsg upload looks a bit suspicious,
> so I'm Ccing Ben here.

make seems to be a wrong guess here. After downgrading make, it fails
the same way. Sorry, Ben, for the noise. Also thank you for having taken
care of it.

Scanning the recent upload history, automake-1.16 looks suspicious now.

I also rescheduled libtextwrap on reproducible.d.n and it fails there as
well. Another data point for a fairly recent regression.

Helmut

Bug#905471: marked as done (fwupd-amd64-signed-template: conflicting source package name)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 05:34:20 +
with message-id 
and subject line Bug#905471: fixed in fwupd 1.1.0-6
has caused the Debian Bug report #905471,
regarding fwupd-amd64-signed-template: conflicting source package name
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.)


-- 
905471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd-amd64-signed-template
Version: 1.1.0-5
Severity: serious

>From the code signing service:

+---
| dpkg-source: error: source package has two conflicting values - 
fwupd-amd64-signed and fwupd-signed-amd64
+---

d/changelog and d/control use different source package names.

This should be reproducible by just invoking `dpkg-source -b` in the
template directory (or a copy of it).

Ansgar
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.1.0-6

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
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, 05 Aug 2018 00:06:30 -0500
Source: fwupd
Binary: libfwupd2 fwupd fwupd-tests fwupd-doc libfwupd-dev gir1.2-fwupd-2.0 
fwupd-amd64-signed-template fwupd-i386-signed-template 
fwupd-armhf-signed-template fwupd-arm64-signed-template
Architecture: source amd64 all
Version: 1.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-amd64-signed-template - Template for signed fwupd package
 fwupd-arm64-signed-template - Template for signed fwupd package
 fwupd-armhf-signed-template - Template for signed fwupd package
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 fwupd-i386-signed-template - Template for signed fwupd package
 fwupd-tests - Test suite for firmware update daemon
 gir1.2-fwupd-2.0 - GObject introspection data for libfwupd
 libfwupd-dev - development files for libfwupd
 libfwupd2  - Firmware update daemon library
Closes: 905471
Changes:
 fwupd (1.1.0-6) unstable; urgency=medium
 .
   * correct secure boot signing template name (Closes: #905471)
Checksums-Sha1:
 46c0ab43481c150abffe200374252e8a17399184 3590 fwupd_1.1.0-6.dsc
 ba2af7ecdc9c2148d275fe8d0dd654e7cf8b89f9 17648 fwupd_1.1.0-6.debian.tar.xz
 1629d0fb4122359ece8a0184c57f36d14f8b4ccd 13946 
fwupd-amd64-signed-template_1.1.0-6_amd64.deb
 b511779b2be887947c1f6d4dbdc447ae1da39291 1999342 fwupd-dbgsym_1.1.0-6_amd64.deb
 12bca7657d9655aa3ccf4b4579dabf74389906fa 63668 fwupd-doc_1.1.0-6_all.deb
 95526f86e4445bc96299495b9dea669dae8da827 9804 
fwupd-tests-dbgsym_1.1.0-6_amd64.deb
 c7017e237f8a7282e6a6e710475fd9b7c60a165b 22092 fwupd-tests_1.1.0-6_amd64.deb
 195d9853b42e8cfde50989bcfb7c63fba0ff3210 16800 fwupd_1.1.0-6_amd64.buildinfo
 e5b6e0481a76ed5258684374334c9994b23c6f26 1708950 fwupd_1.1.0-6_amd64.deb
 952ca63d5e75e88c023ff909895f613cea9235e8 17814 
gir1.2-fwupd-2.0_1.1.0-6_amd64.deb
 5016cf3dfcfe075596bdda1f4e939596d8a03585 30028 libfwupd-dev_1.1.0-6_amd64.deb
 401fff734269f7a0b6a989393595ea4e05e64cdd 114654 
libfwupd2-dbgsym_1.1.0-6_amd64.deb
 3886182c20b6e5d8f0f3e95ae7562707eb04c95f 55986 libfwupd2_1.1.0-6_amd64.deb
Checksums-Sha256:
 b4a6e0b98889a00f088e8ada960c0e29f9ba49f403be692f51cc5426e510bde5 3590 
fwupd_1.1.0-6.dsc
 079c5635fe76c45c45a6b3cef5a8fe74351fb1e86d5475311de540b6e73ce278 17648 
fwupd_1.1.0-6.debian.tar.xz
 9979d27dd3051f249d38c70c131704fdd9d6e3894fc55eafd2e59e1011b5ee26 13946 
fwupd-amd64-signed-template_1.1.0-6_amd64.deb
 8a5c851155ceec455c6f4f27fd8d64f9dc99ff7bd6ec81444285cb469f636b9c 1999342 
fwupd-dbgsym_1.1.0-6_amd64.deb
 82c3cdc41a6de54227bbaf098277be7c6a7459301f0aef054b2dfd97762c6ae4 63668 
fwupd-doc_1.1.0-6_all.deb
 7eeaff02d75f3ae87111bd2accf0ce8f0c204d7f4b0760a6bfc01b6bcf71d153 9804 
fwupd-tests-dbgsym_1.1.0-6_amd64.deb
 e979e69f5117c4140ac5f74d5312c8c9c6d3458717eb18b13031a4daca537fba 22092 
fwupd-tests_1.1.0-6_amd64.deb
 0439b5505f0f3f5ea884770f01f09e

Bug#905472: libtextwrap FTBFS: cannot find -ltextwrap

[Helmut Grohne]

Source: libtextwrap
Version: 0.1-14.1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

libtextwrap fails to build from source on amd64 in unstable. A build log
ends with:

| touch configure-stamp
| dh_testdir
| /usr/bin/make
| make[1]: Entering directory '/<>'
| /usr/bin/make  all-am
| make[2]: Entering directory '/<>'
| gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -MT dotextwrap.o -MD -MP -MF .deps/dotextwrap.Tpo -c -o 
dotextwrap.o dotextwrap.c
| mv -f .deps/dotextwrap.Tpo .deps/dotextwrap.Po
| /bin/bash ./libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -o dotextwrap dotextwrap.o -ltextwrap 
| libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -o 
dotextwrap dotextwrap.o  -ltextwrap
| /usr/bin/ld: cannot find -ltextwrap
| collect2: error: ld returned 1 exit status
| make[2]: *** [Makefile:515: dotextwrap] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:373: all] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:56: build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This looks very strange and more of a breakage of makefile dependencies.
It didn't even try building -ltextwrap and links it already. The issue
is reproducible without parallelism. I haven't seen it until "recently"
though since meson and then pcre3 have fucked up bootstrap qa lately,
"recently" means like two weeks here though reproducible builds didn't
encounter the issue (yet?). The make-dfsg upload looks a bit suspicious,
so I'm Ccing Ben here.

I hope that someone can make sense of this, or at least reproduce it.

Helmut

Processed: closing because h5py 2.8.0 has been uploaded

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #904781 [src:h5py] new upstream needed for Python 3.7 compatibility
Marked Bug as done

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

Bug#904781: closing because h5py 2.8.0 has been uploaded

[Lumin]

control: close -1

closing because 0.2.8 has been uploaded.
I forgot to close this bug.

Bug#905439: su from util-linux breaks autopkgtest

[Lumin]

control: close -1

Hi Antonio,

The log is available here and the autopkgtest version used is 5.4.1~bpo9+2
http://debomatic-amd64.debian.net/distribution#unstable/h5py/2.8.0-1/autopkgtest

So I think it would be fixed when the backported backage is updated.
Sorry for the noise.

On Sat, Aug 04, 2018 at 01:31:27PM -0300, Antonio Terceiro wrote:
> Control: tag -1 + moreinfo unreproducible
> 
> On Sat, Aug 04, 2018 at 03:11:17PM +, Lumin wrote:
> > Package: autopkgtest
> > Version: 5.4.2
> > Severity: serious
> > 
> > the "su" command from util-linux breaks autopkgtest. The previous
> > working one comes from shadow.
> > 
> > python-h5py-dbg is already the newest version (2.8.0-1).
> > python-h5py-dbg set to manually installed.
> > python-h5py is already the newest version (2.8.0-1).
> > python-h5py set to manually installed.
> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > (Reading database ... 13709 files and directories currently installed.)
> > Removing autopkgtest-satdep (0) ...
> > autopkgtest [16:38:33]: test command1: set -e ; for py in $(pyversions -r 
> > 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
> > "import h5py; h5py.run_tests()" ; echo "Testing with $py-dbg:" ; $py-dbg -c 
> > "import h5py; h5py.run_tests()" ; done
> > autopkgtest [16:38:33]: test command1: [---
> > su: user  does not exist
> > autopkgtest [16:38:33]: test command1: ---]
> > Unexpected error:
> > Traceback (most recent call last):
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
> > command()
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
> > r = f(c, ce)
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
> > copyupdown(c, ce, True)
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
> > copyupdown_internal(ce[0], c[1:], upp)
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
> > copyupdown_internal
> > copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
> >   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
> > copyup_shareddir
> > shutil.copy(tb, host)
> >   File "/usr/lib/python3.5/shutil.py", line 241, in copy
> > copyfile(src, dst, follow_symlinks=follow_symlinks)
> >   File "/usr/lib/python3.5/shutil.py", line 120, in copyfile
> > with open(src, 'rb') as fsrc:
> > FileNotFoundError: [Errno 2] No such file or directory: 
> > '/var/run/schroot/mount/unstable-amd64-debomatic-98e10886-4014-46ea-a35e-37ffe71bdcf3/tmp/autopkgtest.mZ5fp7/command1-stdout'
> > autopkgtest [16:38:34]: ERROR: testbed failure: unexpected eof from the 
> > testbed
> 
> Are you sure you saw this with autopkgtest 5.4.2? This bug was present
> 5.4.1, but explicitly fixed in 5.4.2.
> 
> See the attached log for an attempt I just made at reproducing this. The
> tests fail but autopkgtest itself works as expected.

> autopkgtest [13:26:52]: version 5.4.2
> autopkgtest [13:26:52]: host lemur; command line: /usr/bin/autopkgtest 
> --apt-upgrade --log-file /tmp/log -B h5py -- lxc --sudo 
> autopkgtest-unstable-amd64
> autopkgtest: WARNING: running as root in testbed, because no normal user 
> could be determined
> autopkgtest [13:27:04]:  test bed setup
> Get:1 http://deb.debian.org/debian unstable InRelease [233 kB]
> Get:2 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [27.8 
> kB]
> Get:3 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB]
> Get:4 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
> [27.9 kB]
> Get:5 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index 
> [27.8 kB]
> Get:6 http://deb.debian.org/debian unstable/non-free Sources 
> 2018-08-03-2013.11.pdiff [1,306 B]
> Get:7 http://deb.debian.org/debian unstable/non-free Sources 
> 2018-08-04-0814.44.pdiff [665 B]
> Get:8 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-02-1416.04.pdiff [5,521 B]
> Get:7 http://deb.debian.org/debian unstable/non-free Sources 
> 2018-08-04-0814.44.pdiff [665 B]
> Get:9 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-02-2015.39.pdiff [10.3 kB]
> Get:10 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-03-0208.52.pdiff [3,145 B]
> Get:11 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-03-0811.08.pdiff [15.6 kB]
> Get:12 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-03-1408.50.pdiff [39.5 kB]
> Get:13 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-03-2013.11.pdiff [8,876 B]
> Get:14 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-04-0211.02.pdiff [5,928 B]
> Get:15 http://deb.debian.org/debian unstable/main Sources 
> 2018-08-04-0814.44.pdiff [11.7 kB]
> Get:16 http://incoming.debian.org/debian-buildd buildd-unstable InRelease 
> [55.3 kB]
> Get:17 http://deb.debian.org/debian unstable/main Source

Processed: Re: Bug#905439: su from util-linux breaks autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #905439 [autopkgtest] su from util-linux breaks autopkgtest
Marked Bug as done

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

Bug#905471: fwupd-amd64-signed-template: conflicting source package name

[Ansgar Burchardt]

Package: fwupd-amd64-signed-template
Version: 1.1.0-5
Severity: serious

>From the code signing service:

+---
| dpkg-source: error: source package has two conflicting values - 
fwupd-amd64-signed and fwupd-signed-amd64
+---

d/changelog and d/control use different source package names.

This should be reproducible by just invoking `dpkg-source -b` in the
template directory (or a copy of it).

Ansgar

Bug#905468: marked as done (fwupd-amd64-signed-template: invalid Build-Depends (syntax error))

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 04:04:10 +
with message-id 
and subject line Bug#905468: fixed in fwupd 1.1.0-5
has caused the Debian Bug report #905468,
regarding fwupd-amd64-signed-template: invalid Build-Depends (syntax error)
to be marked as done.

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

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


-- 
905468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd-amd64-signed-template
Version: 1.1.0-4
Severity: serious

The source template for code signing contains invalid Build-Depends:

Build-Depends: ... fwupd (= ) [amd64]

The version is missing.  The same problem occurs in `Depends` too:

Depends: ... fwupd (= })

Ansgar
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.1.0-5

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 22:37:36 -0500
Source: fwupd
Binary: libfwupd2 fwupd fwupd-tests fwupd-doc libfwupd-dev gir1.2-fwupd-2.0 
fwupd-amd64-signed-template fwupd-i386-signed-template 
fwupd-armhf-signed-template fwupd-arm64-signed-template
Architecture: source amd64 all
Version: 1.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-amd64-signed-template - Template for signed fwupd package
 fwupd-arm64-signed-template - Template for signed fwupd package
 fwupd-armhf-signed-template - Template for signed fwupd package
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 fwupd-i386-signed-template - Template for signed fwupd package
 fwupd-tests - Test suite for firmware update daemon
 gir1.2-fwupd-2.0 - GObject introspection data for libfwupd
 libfwupd-dev - development files for libfwupd
 libfwupd2  - Firmware update daemon library
Closes: 904671 905468
Changes:
 fwupd (1.1.0-5) unstable; urgency=medium
 .
   * Fix secure boot signing template version string (Closes: #905468)
   * Refresh debian/copyright (Closes: #904671)
Checksums-Sha1:
 9432fe97e375356c79e4674f888384354d28a774 3590 fwupd_1.1.0-5.dsc
 a8d0800693cec0e6b766ff829a66bcf2bab59835 17620 fwupd_1.1.0-5.debian.tar.xz
 ad69e6b5f7ecca43d174151e12e8eec9533099c4 13900 
fwupd-amd64-signed-template_1.1.0-5_amd64.deb
 ddbf1a8d9cda1ca8afbe4a47f1b71db0bd1bb02c 1999150 fwupd-dbgsym_1.1.0-5_amd64.deb
 1b04aaf318ab374597a4332aa9226ddc9c12eb2f 63626 fwupd-doc_1.1.0-5_all.deb
 f5416e8aa4203efdafae6667ec026a2cd6ec2187 9806 
fwupd-tests-dbgsym_1.1.0-5_amd64.deb
 3423cfee22e6000ef4e9bce4c8b24002b50aef82 22046 fwupd-tests_1.1.0-5_amd64.deb
 9ea5b3d4f1309bff42dd997f9527b341205f077b 16800 fwupd_1.1.0-5_amd64.buildinfo
 7ee0282413cf16055094a2b8c2d3e6ff54276f82 1708632 fwupd_1.1.0-5_amd64.deb
 687bd15d0254ce4b2a7e2e4b3aafa5b7d69f25a1 17790 
gir1.2-fwupd-2.0_1.1.0-5_amd64.deb
 c39954d498c87253334a24cf21027832cda732f7 29984 libfwupd-dev_1.1.0-5_amd64.deb
 2d81479c5584bebb34623491f1495c1d34cf9341 114662 
libfwupd2-dbgsym_1.1.0-5_amd64.deb
 1cc29078d2486fdc25c155b74f3a2e7d3f324e6f 55952 libfwupd2_1.1.0-5_amd64.deb
Checksums-Sha256:
 7f0f770cff1cb2376d5e028247669f6b423d4263c507a08ae267e85f06f4716d 3590 
fwupd_1.1.0-5.dsc
 ccdcaf63c44e8f94d63bfa81220e2bdbb9982877a493915adc289724a5ad1b0f 17620 
fwupd_1.1.0-5.debian.tar.xz
 250c4b1400ee0f6f4568737b623aa1e9aa712f8ea66256a09d452bf14682fb83 13900 
fwupd-amd64-signed-template_1.1.0-5_amd64.deb
 0bc2a1808914b005a23ddedc34ea934314297219ce9f6f666ab7fb252abfc0a7 1999150 
fwupd-dbgsym_1.1.0-5_amd64.deb
 e4fa8a04d5633b192cdbca41fdfe5f5e9a2dd0d2e8d876813329897c54691191 63626 
fwupd-doc_1.1.0-5_all.deb
 8a060f9e3b9e5329f3eaa6ea94d8ac3a754467ece60f4db5e571642d86a66114 9806 
fwupd-tests-dbgsym_1.1.0-5_amd64.deb
 64cee7d72f4336731684bb5ec7732104e2e5c853903cee48cf656b2ed91d8a89 22046 
fwupd-tests_1.1.0-5_amd64.deb
 d79e66683c5960510fe3934f779e22daade0ea27de4746ca2677e5fee0e6644e 16800 
fwupd

Bug#904671: marked as done (fwupd: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 04:04:10 +
with message-id 
and subject line Bug#904671: fixed in fwupd 1.1.0-5
has caused the Debian Bug report #904671,
regarding fwupd: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
904671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwupd
Version: 1.1.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Mario Limonciello 

Hi,

I just ACCEPTed fwupd from NEW but noticed it was missing attribution 
in debian/copyright for at least a bunch of code copies (or similar)
under "plugins/".

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.1.0-5

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 22:37:36 -0500
Source: fwupd
Binary: libfwupd2 fwupd fwupd-tests fwupd-doc libfwupd-dev gir1.2-fwupd-2.0 
fwupd-amd64-signed-template fwupd-i386-signed-template 
fwupd-armhf-signed-template fwupd-arm64-signed-template
Architecture: source amd64 all
Version: 1.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-amd64-signed-template - Template for signed fwupd package
 fwupd-arm64-signed-template - Template for signed fwupd package
 fwupd-armhf-signed-template - Template for signed fwupd package
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 fwupd-i386-signed-template - Template for signed fwupd package
 fwupd-tests - Test suite for firmware update daemon
 gir1.2-fwupd-2.0 - GObject introspection data for libfwupd
 libfwupd-dev - development files for libfwupd
 libfwupd2  - Firmware update daemon library
Closes: 904671 905468
Changes:
 fwupd (1.1.0-5) unstable; urgency=medium
 .
   * Fix secure boot signing template version string (Closes: #905468)
   * Refresh debian/copyright (Closes: #904671)
Checksums-Sha1:
 9432fe97e375356c79e4674f888384354d28a774 3590 fwupd_1.1.0-5.dsc
 a8d0800693cec0e6b766ff829a66bcf2bab59835 17620 fwupd_1.1.0-5.debian.tar.xz
 ad69e6b5f7ecca43d174151e12e8eec9533099c4 13900 
fwupd-amd64-signed-template_1.1.0-5_amd64.deb
 ddbf1a8d9cda1ca8afbe4a47f1b71db0bd1bb02c 1999150 fwupd-dbgsym_1.1.0-5_amd64.deb
 1b04aaf318ab374597a4332aa9226ddc9c12eb2f 63626 fwupd-doc_1.1.0-5_all.deb
 f5416e8aa4203efdafae6667ec026a2cd6ec2187 9806 
fwupd-tests-dbgsym_1.1.0-5_amd64.deb
 3423cfee22e6000ef4e9bce4c8b24002b50aef82 22046 fwupd-tests_1.1.0-5_amd64.deb
 9ea5b3d4f1309bff42dd997f9527b341205f077b 16800 fwupd_1.1.0-5_amd64.buildinfo
 7ee0282413cf16055094a2b8c2d3e6ff54276f82 1708632 fwupd_1.1.0-5_amd64.deb
 687bd15d0254ce4b2a7e2e4b3aafa5b7d69f25a1 17790 
gir1.2-fwupd-2.0_1.1.0-5_amd64.deb
 c39954d498c87253334a24cf21027832cda732f7 29984 libfwupd-dev_1.1.0-5_amd64.deb
 2d81479c5584bebb34623491f1495c1d34cf9341 114662 
libfwupd2-dbgsym_1.1.0-5_amd64.deb
 1cc29078d2486fdc25c155b74f3a2e7d3f324e6f 55952 libfwupd2_1.1.0-5_amd64.deb
Checksums-Sha256:
 7f0f770cff1cb2376d5e028247669f6b423d4263c507a08ae267e85f06f4716d 3590 
fwupd_1.1.0-5.dsc
 ccdcaf63c44e8f94d63bfa81220e2bdbb9982877a493915adc289724a5ad1b0f 17620 
fwupd_1.1.0-5.debian.tar.xz
 250c4b1400ee0f6f4568737b623aa1e9aa712f8ea66256a09d452bf14682fb83 13900 
fwupd-amd64-signed-template_1.1.0-5_amd64.deb
 0bc2a1808914b005a23ddedc34ea934314297219ce9f6f666ab7fb252abfc0a7 1999150 
fwupd-dbgsym_1.1.0-5_amd64.deb
 e4fa8a04d5633b192cdbca41fdfe5f5e9a2dd0d2e8d876813329897c54691191 63626 
fwupd-doc_1.1.0-5_all.deb
 8a060f9e3b9e5329f3eaa6ea94d8ac3a754467ece60f4db5e571642d86a66114 9806 
fwupd-tests-dbgsym_1.1.0-5

Bug#893542: marked as done (ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 04:04:28 +
with message-id 
and subject line Bug#893542: fixed in ntpsec 1.1.1+dfsg1-1
has caused the Debian Bug report #893542,
regarding ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped 
when ntp is purged
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.)


-- 
893542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntpsec-ntpviz
Version: 1.0.0+dfsg1-5
Severity: serious

I installed the ntpsec suite, then purged the ntp packages.
Unfortunately, this zapped the /var/log/ntpstats directory, which is
needed by ntpsec-ntpviz.  There needs to either been some agreement
between ntp and ntpsec about the use of this directory, or ntpsec
needs to use a different log directory.

Best wishes,

   ulian

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

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

Versions of packages ntpsec-ntpviz depends on:
ii  adduser   3.117
ii  cron [cron-daemon]3.0pl1-130
ii  fonts-liberation  1:1.07.4-5
ii  gnuplot   5.2.2+dfsg1-2
ii  gnuplot-qt [gnuplot]  5.2.2+dfsg1-2
ii  python3   3.6.4-1
ii  python3-ntp   1.0.0+dfsg1-5
ii  systemd   238-2

Versions of packages ntpsec-ntpviz recommends:
ii  apache2 [httpd]  2.4.29-2
ii  ntpsec   1.0.0+dfsg1-5
ii  python3-psutil   5.4.2-1
ii  systemd  238-2

Versions of packages ntpsec-ntpviz suggests:
ii  python  2.7.14-4
pn  python-gps  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ntpsec
Source-Version: 1.1.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated ntpsec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Aug 2018 22:04:20 -0500
Source: ntpsec
Binary: ntpsec ntpsec-ntpdate ntpsec-ntpviz ntpsec-doc python3-ntp
Architecture: source
Version: 1.1.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Description:
 ntpsec - Network Time Protocol daemon and utility programs
 ntpsec-doc - Network Time Protocol documentation
 ntpsec-ntpdate - client for setting system time from NTP servers
 ntpsec-ntpviz - NTP statistics graphing utility
 python3-ntp - Python 3 NTP Helper Classes
Closes: 893542 898402
Changes:
 ntpsec (1.1.1+dfsg1-1) unstable; urgency=medium
 .
   * Changes as of ntp_4.2.8p11+dfsg-1 have been merged as appropriate:
 - Drop old versioned build-deps.
   Thanks to Bernhard Schmidt 
 - Sync AppArmor profile changes from Ubuntu.
   Thanks to Bernhard Schmidt 
   * Update apparmor for new drift temp file
   * Drop preempt from Ubuntu ntp.conf
   * Use ntp.conf.dhcp if it exists, rather than only if it is newer than
 ntp.conf
   * Add an option to ignore DHCP-provided servers (Closes: 898402)
   * Update upstream GPG key
   * New upstream version
 - Log timestamps now include the year.  This is useful when
   investigating bugs involving time-setting and -g.
 - Many internal cleanups to clear the way for upcoming major features.
   They should generally not be user visible.  Refer to the git-log if
   you are interested.
 - Restore support for peer (MODE_ACTIVE) packets
   * Drop autorevision-related code
   * Refresh Debian patches
   * README.Debian: Update bit about dhclient.conf
   * README.Debian: Fix broken link to NTP servers
   * debian/copyright: Use HTTPS for Format URL
   * Update URLs in debian

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Andreas Henriksson]

Hello Davide Prina,

Thanks for your bug report. (Reply inline below.)

On Sat, Aug 04, 2018 at 08:59:29AM +0200, Davide Prina wrote:
> Package: util-linux
> Version: 2.32-0.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> upgrading
> * util-linux:amd64 (2.32-0.1, 2.32-0.3)
> * login:amd64 (1:4.5-1, 1:4.5-1.1)
> 
> do not let work anymore something like this:
> 
> $ xhost +si:localuser:temp
> $ su - temp

You are right that the old su would copy over DISPLAY and XAUTHORITY
environment variables, even when you tell it to give you a new
clean environment.

The util-linux implementation does what you tell it to do.

> $ firefox &
> Error: GDK_BACKEND does not match available displays

The error message is a bit misleading. Please just try running this
instead:

DISPLAY=:0 firefox &

> 
> downgrade this two packages (as I have done now before writing this bug
> report) solve the problem
> 
> If I mistake and this is a login package problem please reassign the bug.

Please feel free to submit a merge request with a util-linux.NEWS entry
addition mentioning the difference if you can come up with a nice
user-understandable description.

You might also want to file a minor bug report against firefox
(upstream?) to give a less misleading error message.

Regards,
Andreas Henriksson

Bug#897797: Help to build libsmithwaterman with gcc-8 needed

[Andreas Tille]

Hi,

I thinks I've fixed the issue for bug #897797 in Git[1] for
libsmithwaterman but somehow it fails to build for a different
reason now.  Any idea why this might happen:

...
make  all-am
make[2]: Entering directory '/build/libsmithwaterman-0.0+git20160702.2610e25'
g++ -DHAVE_CONFIG_H -I.   -I. -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/build/libsmithwaterman-0.0+git20160702.2610e25=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o smithwaterman.o 
smithwaterman.cpp
/bin/bash ./libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/build/libsmithwaterman-0.0+git20160702.2610e25=. 
-fstack-protector-strong -Wformat -Werror=format-security  -  Wl,-z,relro 
-Wl,-z,now -o smithwaterman smithwaterman.o -lsmithwaterman -ldisorder
libtool: link: g++ -g -O2 
-fdebug-prefix-map=/build/libsmithwaterman-0.0+git20160702.2610e25=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o smithwaterman smithwaterman.o  -lsmithwaterman -ldisorder
/usr/bin/ld: cannot find -lsmithwaterman
collect2: error: ld returned 1 exit status
...


Any hints?

Kind regards

 Andreas.


[1] https://salsa.debian.org/med-team/libsmithwaterman

-- 
http://fam-tille.de

Bug#905468: fwupd-amd64-signed-template: invalid Build-Depends (syntax error)

[Ansgar Burchardt]

Package: fwupd-amd64-signed-template
Version: 1.1.0-4
Severity: serious

The source template for code signing contains invalid Build-Depends:

Build-Depends: ... fwupd (= ) [amd64]

The version is missing.  The same problem occurs in `Depends` too:

Depends: ... fwupd (= })

Ansgar

Bug#905195: e2fslibs-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Theodore Y. Ts'o]

Thanks for the report.  I've checked in a fix for this into the
e2fsprogs git repository, and it will be in the next release of e2fsprogs.

  - Ted

Processed: tagging 905195

[Debian Bug Tracking System]

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

> tags 905195 + pending
Bug #905195 [e2fslibs-dev] e2fslibs-dev: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#904444: marked as done (trnascan-se: FTBFS during arch-indep build)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 00:48:59 +
with message-id 
and subject line Bug#90: fixed in trnascan-se 2.0.0-2
has caused the Debian Bug report #90,
regarding trnascan-se: FTBFS during arch-indep build
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.)


-- 
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trnascan-se
Version: 2.0.0-1
Severity: serious
Justification: fails to build from source

Hi,

trnascan-se FTBFS when built with dpkg-buildpackage -A:

   dh_auto_build -i
make -j4
make[1]: Entering directory '/build/trnascan-se-2.0.0'
make  all-am
make[2]: Entering directory '/build/trnascan-se-2.0.0'
sed -e 's,\@bindir\@,/usr/bin,g' -e 's,\@pkgdatadir\@,/usr/share/trnascan-se,g' 
-e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,\@INFERNAL\@,,g' -e 
's,\@sysconfdir\@,/etc,g' < ./src/sstofa.in > bin/sstofa
sed -e 's,\@bindir\@,/usr/bin,g' -e 's,\@pkgdatadir\@,/usr/share/trnascan-se,g' 
-e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,\@INFERNAL\@,,g' -e 
's,\@sysconfdir\@,/etc,g' < ./src/fasta2gsi.in > bin/fasta2gsi
/bin/bash: bin/sstofa: No such file or directory
make[2]: *** [Makefile:1102: bin/sstofa] Error 1


Andreas


trnascan-se_2.0.0-1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: trnascan-se
Source-Version: 2.0.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated trnascan-se 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, 05 Aug 2018 02:22:58 +0200
Source: trnascan-se
Binary: trnascan-se trnascan-se-common
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 trnascan-se - detection of transfer RNA genes in genomic sequence
 trnascan-se-common - detection of transfer RNA genes in genomic sequence 
(common files
Closes: 90
Changes:
 trnascan-se (2.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Check existence of files before calling chmod on them to fix arch indep
 builds
 Closes: #90
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.5
   * Clean up properly
   * Fix paths in d/copyright
   * hardening=+all
Checksums-Sha1:
 81a1a7c5e1fe679a3ea42f6e1efaf6b5f1ce2e21 2096 trnascan-se_2.0.0-2.dsc
 3cf95c2df82a10dde60efd2a954485a14581ba93 6216 trnascan-se_2.0.0-2.debian.tar.xz
Checksums-Sha256:
 515fa57691a8913b29096f1c8ab9cd825e253b4e08cae085d7b11abe32417052 2096 
trnascan-se_2.0.0-2.dsc
 1eecb88f2d63539509be1b03d276dcfb9fcd59f69a37883004f262cbe284a400 6216 
trnascan-se_2.0.0-2.debian.tar.xz
Files:
 a7b9404d0f3ec1ee56f0260eac53c53a 2096 non-free/science optional 
trnascan-se_2.0.0-2.dsc
 d1d3ba9d3736275e1875089e8696f5aa 6216 non-free/science optional 
trnascan-se_2.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltmRKgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHmJg/+LRLXNvOXEZaEZRnpXiY8hT/kgDqXKms5
wK4Q+kZOTFNAKfL5jHy5s/1Z/77a4R+D4ae6URY5onsRffPdckigbcQwtzUJITOc
cJyR/Mxk0NoAzOPnC0Rk8opyFmMiDXkrL5SmZXrfAxdfvpQuc/V7qnu5Iys+paRQ
+QDWVHpCAHnZ7cXUgrkyZ78f2x09jUUapG+HwRish3zVoBNVD/TYJwAoGzNJdM/Y
UDm2psot21bRbYae6Dpf+7C3E88jYp3moBzrzSkNPWcRZ63lFr116XZpETv1IP6M
rU8msrVmHuJmiLXl4Y0DNBaAtAsZUcmYIoV1ucqRNI7Q/z8PY1MtvooEUB6TLWt2
a1mjDoRlIrNNux5/TOOIkIZAYr/dbnU64R9U0UQHWYwmxRsj8PjraTi8P8IRB/rl
reMc+wC/5IHlRCrDyGtTD9IivlC6iiXuWrZSbfIOJbh2CJK8KK0ENmJeI7W7MXTL
boe+UFNPjKMM27kC/Ibo4V1vu0eKib+hLTNzs2JiSVQMePlU5gaxcS5405VA4AEw
er9Qn+EbLF2foFgfEXE1EosLiB8XIghIgCJvQ2z0In5Ub4s53kWcn6DS+5UthvgY
RSjkdy0MSDOlVWEFhBiajq8CozX4IPk2f4qvk5k9YkCZEjiu8pw/28IrZA/mR95U
QrczvsjW04w=
=KQ23
-END PGP SIGNATURE End Message ---

Bug#905463: leatherman: FTBFS - test hangs

[Andreas Beckmann]

Source: leatherman
Version: 1.4.2+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

leatherman FTBFS in the buildd environent on all architectures:
https://buildd.debian.org/status/package.php?p=leatherman

The testsuite seems to hang or take forever:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/leatherman-1.4.2+dfsg'
# Tests are locale-dependent
LC_ALL=C LC_CTYPE=C dh_auto_test
cd obj-i686-linux-gnu && make -j4 test ARGS\+=-j4
make[2]: Entering directory 
'/<>/leatherman-1.4.2+dfsg/obj-i686-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/leatherman-1.4.2+dfsg/obj-i686-linux-gnu
Start 1: leatherman tests
E: Build killed with signal TERM after 150 minutes of inactivity


Andreas

Bug#904514: marked as done (python3-expeyes: fails to install: Exception: cannot get content of python-expeyes)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 23:49:12 +
with message-id 
and subject line Bug#904514: fixed in expeyes 4.4.3+dfsg-3
has caused the Debian Bug report #904514,
regarding python3-expeyes: fails to install: Exception: cannot get content of 
python-expeyes
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package python3-expeyes.
  (Reading database ... 
(Reading database ... 7418 files and directories currently installed.)
  Preparing to unpack .../python3-expeyes_4.4.3+dfsg-2_all.deb ...
  Unpacking python3-expeyes (4.4.3+dfsg-2) ...
  Setting up python3-expeyes (4.4.3+dfsg-2) ...
  udev: unrecognized service
  dpkg-query: package 'python-expeyes' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in 
  main()
File "/usr/bin/py3compile", line 270, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 106, in filter_files
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python-expeyes
  dpkg: error processing package python3-expeyes (--configure):
   installed python3-expeyes package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-expeyes


cheers,

Andreas


python3-expeyes_4.4.3+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: expeyes
Source-Version: 4.4.3+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated expeyes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Jul 2018 05:03:44 +0200
Source: expeyes
Binary: expeyes eyes17 libej0 libej-dev expeyes-clib expeyes-firmware-dev 
python3-expeyes expeyes-web microhope
Architecture: source amd64 all
Version: 4.4.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 expeyes- hardware & software framework for developing science experiments
 expeyes-clib - hardware & software framework for developing science experiments
 expeyes-firmware-dev - hardware & software framework for developing science 
experiments
 expeyes-web - Web interface for expEYES-Junior
 eyes17 - hardware & software framework for developing science experiments
 libej-dev  - hardware & software framework for developing science experiments
 libej0 - hardware & software framework for developing science experiments
 microhope  - hardware & software framework to learn microcontrollers
 python3-expeyes - Python3 library for expeyes
Closes: 904514
Changes:
 expeyes (4.4.3+dfsg-3) unstable; urgency=medium
 .
   * promoted the recommendation python3-expeyes <- udev to a dependency.
 Closes: #904514
Checksums-Sha1:
 b59c610d0e729acec6bf85fad4d89540ae46b8bf 2491 expeyes_4.4.3+dfsg-3.dsc
 d2219f894e53fc2c58c9a2546b10304e55a8e73a 3241864 
expeyes_4.4.3+dfsg-3.debian.tar.xz
 dd9eb5686979010ee6ae160c31ac0be06681b173 25668 

Processed: fixed 905188 in 2:2.0.4-1

[Debian Bug Tracking System]

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

> fixed 905188 2:2.0.4-1
Bug #905188 {Done: Guilhem Moulin } [cryptsetup-initramfs] 
cryptsetup-initramfs: fails to install, remove, distupgrade, and install again
Marked as fixed in versions cryptsetup/2:2.0.4-1.
> thanks
Stopping processing here.

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

Bug#759410: Different approach for safe-rm

[Dimitri John Ledkov]

I agree that's the generic way forward for safe-rm in light of usrmerge but
did not feel it was right to make up such a path in Ubuntu. I'm happy with
such a solution for Debian, and for Ubuntu. I'm off for two weeks, but will
migrate Ubuntu over to that if and when available for merging/syncing into
Ubuntu.

Sorry for top post. Writing from phone.

On Sun, 5 Aug 2018, 00:21 Francois Marier,  wrote:

> I took a look at the details of the diversion that the latest version of
> dash sets up and it's really quite complicated. It's not clear that I could
> easily get it right, even copying that code, and the consequences of
> getting
> it wrong could be disastrous.
>
> So instead I went for an easier approach: install the rm symlink in
> /usr/share/safe-rm/bin/ and then add that to the front of the PATH in
> /etc/profile.d/safe-rm.sh.
>
> That seems to work both for login shells (on a virtual terminal) and for
> interactive shells (e.g. gnome-terminal) after logging out and logging back
> in.
>
> The downside is that it may not for shells which are not Bourne-compatible.
> I believe it works in bash, dash, ksh and zsh, but I could be wrong. I'm
> happy to accept patches to make it work on other shells of course.
>
> Francois
>
> --
> https://fmarier.org/
>

Bug#759410: Different approach for safe-rm

[Francois Marier]

I took a look at the details of the diversion that the latest version of
dash sets up and it's really quite complicated. It's not clear that I could
easily get it right, even copying that code, and the consequences of getting
it wrong could be disastrous.

So instead I went for an easier approach: install the rm symlink in
/usr/share/safe-rm/bin/ and then add that to the front of the PATH in
/etc/profile.d/safe-rm.sh.

That seems to work both for login shells (on a virtual terminal) and for
interactive shells (e.g. gnome-terminal) after logging out and logging back
in.

The downside is that it may not for shells which are not Bourne-compatible.
I believe it works in bash, dash, ksh and zsh, but I could be wrong. I'm
happy to accept patches to make it work on other shells of course.

Francois

-- 
https://fmarier.org/

Bug#759410: marked as done (Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin))

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 22:05:26 +
with message-id 
and subject line Bug#759410: fixed in safe-rm 0.12-6
has caused the Debian Bug report #759410,
regarding Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin 
-> /usr/bin)
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.)


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

[As discussed at DebConf 14.]

I'm working on making it possible to merge /bin and /sbin into /usr/bin
and /usr/sbin respectively.  As a first step towards that, I'm planning
to propose a Debian Policy change to prohibit conflicts between
/bin/$foo and /usr/bin/$foo, and likewise for sbin.  safe-rm is one of
only two packages that contains such a conflict: it installs
/usr/bin/rm, which would conflict with /bin/rm.

In order to fix this while preserving safe-rm's default of automatic
protection on installation, safe-rm will need to divert and replace
/bin/rm.  This will require quite a bit of care to do safely; see dash's
maintainer scripts for a safe procedure.

Since safe-rm currently uses Perl, this change will also require one of
two approaches: either provide a small wrapper C program that attempts
to run /usr/bin/safe-rm and falls back to /bin/rm if that fails, or
rewrite safe-rm in C.

- Josh Triplett

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

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: safe-rm
Source-Version: 0.12-6

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

Debian distribution maintenance software
pp.
Francois Marier  (supplier of updated safe-rm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 13:25:52 -0700
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-6
Distribution: unstable
Urgency: high
Maintainer: Francois Marier 
Changed-By: Francois Marier 
Description:
 safe-rm- wrapper around the rm command to prevent accidental deletions
Closes: 759410
Changes:
 safe-rm (0.12-6) unstable; urgency=high
 .
   * Replace /usr/bin/ symlink with /etc/profile.d/ config file for
 Bourne-compatible shells. Patches for other shells are welcome.
 (closes: #759410)
   * Update desktop action to use new user config file
   * Bump Standards-Version up to 4.2.0
Checksums-Sha1:
 9fee0062514261c0dad6cc50465f8ed583e86da7 1959 safe-rm_0.12-6.dsc
 f56eeabe2cf2d79fc98dc6628bc9733ead611ae5 237156 safe-rm_0.12-6.debian.tar.xz
 56a7813ff03c7fe87a60e18c12651e641c0c1bf2 12088 safe-rm_0.12-6_all.deb
 6b379c7653fa9ec2b0adba51619d466cc351a677 5736 safe-rm_0.12-6_amd64.buildinfo
Checksums-Sha256:
 757b577a2e0693e15a6941fa59407b0c34d4dc18e4d9cf1d8a498f83b989ac6d 1959 
safe-rm_0.12-6.dsc
 d5c9d7be0d98a92a650a875d1c7185efce1a6a9f8008c664b34448dde08db840 237156 
safe-rm_0.12-6.debian.tar.xz
 089938fbc09af3acad6a4aa37125b4330456986c3c1844875426e22a63bbfd94 12088 
safe-rm_0.12-6_all.deb
 f8c6c83ec2a334d26ffa9d357a32e68ec839cef2ac50cbbe571b35f3a8b0753e 5736 
safe-rm_0.12-6_amd64.buildinfo
Files:
 2819603c0d957f7fb3d8ead8d45100a3 1959 utils optional safe-rm_0.12-6.dsc
 f2aaed5715b5b04cd940f1ba676eec0c 237156 utils optional 
safe-rm_0.12-6.debian.tar.xz
 88d140c58a457351d3b628ec8596f70d 12088 utils optional safe-rm_0.12-6_all.deb
 71e9428ccbb1e80af7bef6a58865453e 5736 utils optional 
safe-rm_0.12-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAltmFFBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEUHGZyYW5jb2lz
QGRlYmlhbi5vcmcACgkQFigfLgB8mNEC6Q//TpGOV90o12FDpn2Uzstky6Jj3WQO
Ce/mDccLIw05nd0gNAO0FPTUj6edSA0hwO3zUz5HEYZ62WBy+IOOqB+DNB5okhAR
cBbiNDHN441ezRKpf0FkB

Bug#905188: marked as done (cryptsetup-initramfs: fails to install, remove, distupgrade, and install again)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 05:28:40 +0800
with message-id <20180804212840.GA2201@localhost.localdomain>
and subject line Re: [pkg-cryptsetup-devel] Bug#905188: cryptsetup-initramfs: 
fails to install, remove, distupgrade, and install again
has caused the Debian Bug report #905188,
regarding cryptsetup-initramfs: fails to install, remove, distupgrade, and 
install again
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.)


-- 
905188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.0.3-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + cryptsetup

Hi,

during a test with piuparts I noticed your package cryptsetup failed to
install (in 'stretch'), remove (but not purge), distupgrade to 'buster',
and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is from the previous release.

The problem shows up in cryptsetup-initramfs, which prompts about a
deleted conffile, which was not deleted by the user, but probably by a
buggy script in the old package.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

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

  Setting up initramfs-tools-core (0.131) ...
  Setting up initramfs-tools (0.131) ...
  update-initramfs: deferring update (trigger activated)
  Setting up cryptsetup-initramfs (2:2.0.3-6) ...
  
  Configuration file '/etc/cryptsetup-initramfs/conf-hook'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** conf-hook (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
cryptsetup-initramfs (--configure):
   end of file on stdin at conffile prompt
  dpkg: dependency problems prevent configuration of cryptsetup:
   cryptsetup depends on cryptsetup-initramfs (>= 2:2.0.3-1); however:
Package cryptsetup-initramfs is not configured yet.
  
  dpkg: error processing package cryptsetup (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.27-5) ...
  Processing triggers for initramfs-tools (0.131) ...
  Errors were encountered while processing:
   cryptsetup-initramfs
   cryptsetup


cheers,

Andreas


cryptsetup_2:2.0.3-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Control: fixed -1 2:2.0.4-1

On Thu, 02 Aug 2018 at 23:37:20 +0800, Guilhem Moulin wrote:
> I see, thanks for the pointers.  Fixed at
> https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/b7abb5d06e46f3704c4edeb55d033b6283ae8777
>  .

Uploaded, but I managed to get the bug number wrong…

-- 
Guilhem.


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

Bug#904926: marked as done (`cryptroot-unlock` assumes non usrmerge layout and doesn't work with initramfs-tools 0.132)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 21:19:41 +
with message-id 
and subject line Bug#904926: fixed in cryptsetup 2:2.0.4-1
has caused the Debian Bug report #904926,
regarding `cryptroot-unlock` assumes non usrmerge layout and doesn't work with 
initramfs-tools 0.132
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.)


-- 
904926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-initramfs
Version: 2:2.0.3-6
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

after installing updates today, I cannot unlock the cryptroot anymore.
After sshing to the dropbear instance of the machine and starting
cryptroot-unlock, the command responds with the error message:

timeout waiting for askpass.

askpass is installed in the initrd under /lib/cryptsetup (iirc).

Logging into the machines remote console (done via spice) also fails,
as I always get the error message that the password is wrong.
I tried entering the password using US-keyboard layout, to no avail.

I've had to boot into an older kernel, that kernels initramfs still
works. The kernel where the cryptroot-unlock is not working is 4.17.0-1.

The machine has a single disk with 2 partitions, vda1 being the
unencrypted boot partition having the boot loader, kernel and initramfs.

The second partition is the luks volume, having a single LVM volume
group with two logical volumes (see fstab below, hostname redacted)

I have booted into the older kernel and updated the 4.17.0-1 initramfs
with update-initramfs -u
That did not help, either.

Regards,
C. Dominik Bódi

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/x-root ro elevator=noop 
ip=aaa.bbb.ccc.ddd::aaa.bbb.ccc.xxx:255.255.255.zzz::eth0:none quiet

-- /etc/crypttab
vda2_crypt UUID=aecd1a7c-efe5-44e5-a14a-74f1c8c3d046 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
proc/proc   procdefaults0   0
/dev/mapper/x-root / xfs defaults0   1
/dev/mapper/x-data /data xfs defaults0   2
# /boot was on /dev/vda1 during installation
/dev/vda1   /boot   ext2defaults0   2
#/dev/mapper/odysseus-swap_1 noneswapsw  0   0
/dev/scd0   /media/cdrom0   udf,iso9660 user,noauto 0   0

-- lsmod
Module  Size  Used by
ip6t_REJECT16384  4
nf_reject_ipv6 16384  1 ip6t_REJECT
ip6table_nat   16384  1
nf_nat_ipv616384  1 ip6table_nat
ip6table_mangle16384  1
ip6table_raw   16384  1
nf_conntrack_ipv6  16384  21
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
nf_log_ipv616384  5
ip6table_filter16384  1
ip6_tables 32768  4 
ip6table_mangle,ip6table_filter,ip6table_raw,ip6table_nat
ipt_MASQUERADE 16384  1
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
xt_nat 16384  2
xt_recent  20480  2
xt_comment 16384  54
xt_set 16384  2
ip_set_hash_ip 36864  1
ip_set 45056  2 xt_set,ip_set_hash_ip
xt_AUDIT   16384  0
ipt_REJECT 16384  4
nf_reject_ipv4 16384  1 ipt_REJECT
xt_addrtype16384  7
iptable_nat16384  1
nf_nat_ipv416384  1 iptable_nat
xt_mark16384  2
iptable_mangle 16384  1
xt_tcpudp  16384  78
xt_CT  16384  36
iptable_raw16384  1
xt_multiport   16384  10
nf_conntrack_ipv4  16384  35
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
xt_conntrack   16384  15
xt_NFLOG   16384  0
nfnetlink_log  20480  1 xt_NFLOG
nf_log_ipv416384  6
nf_log_common  16384  2 nf_log_ipv6,nf_log_ipv4
xt_LOG 16384  11
nf_conntrack_sane  16384  4
nf_conntrack_netlink49152  0
nfnetlink  16384  3 nfnetlink_log,ip_set,nf_conntrack_netlink
nf_nat_tftp16384  0
nf_nat_snmp_basic  16384  0
nf_conntrack_snmp  16384  3 nf_nat_snmp_basic
nf_nat_sip 20480  0
nf_nat_pptp16384  0
nf_nat_proto_gre   16384  1 nf_nat_pptp
nf_nat_irc 16384  0
nf_nat_h323   

Bug#902445: marked as done (libclojure-java: Upgrading fails in preinst)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 21:04:01 +
with message-id 
and subject line Bug#902445: fixed in clojure 1.9.0-5
has caused the Debian Bug report #902445,
regarding libclojure-java: Upgrading fails in preinst
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.)


-- 
902445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclojure-java
Version: 1.9.0-4
Severity: serious

On 1.9.0-2 -> 1.9.0-4 upgrade:

Preparing to unpack .../00-libclojure-java_1.9.0-4_all.deb ...
update-alternatives: error: no alternatives for clojure
dpkg: error processing archive 
/tmp/apt-dpkg-install-Z53q9V/00-libclojure-java_1.9.0-4_all.deb (--unpack):
 new libclojure-java package pre-installation script subprocess returned error 
exit status 2
--- End Message ---
--- Begin Message ---
Source: clojure
Source-Version: 1.9.0-5

We believe that the bug you reported is fixed in the latest version of
clojure, 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.
Elana Hashman  (supplier of updated clojure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 16:21:54 -0400
Source: clojure
Binary: clojure libclojure-java
Architecture: source
Version: 1.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers 

Changed-By: Elana Hashman 
Description:
 clojure- Lisp dialect for the JVM
 libclojure-java - Lisp dialect for the JVM (library)
Closes: 902445
Changes:
 clojure (1.9.0-5) unstable; urgency=medium
 .
   * Fix alternatives management when clojure alternatives group doesn't
 exist. (Closes: #902445)
   * Assert compliance with the new Standards-Version. Obey.
   * Update team email to the Clojure team's, matching the Salsa link.
Checksums-Sha1:
 67a8442e0f545752db39b9f879d2bf8769b399e7 2203 clojure_1.9.0-5.dsc
 25e459a83f1f9824d799e1c2affcfb8c8529e8b4 13328 clojure_1.9.0-5.debian.tar.xz
 a52a601fdfca09910400413b9b742ff8169d7e4e 10863 clojure_1.9.0-5_source.buildinfo
Checksums-Sha256:
 4bc07a2672fdb9d78c97e98788ac640e9b65f5c83de946359c84f03640c05621 2203 
clojure_1.9.0-5.dsc
 13acf09b963937dea0f6a9803cbbc873541029a770371154e8c8c498cb3a7215 13328 
clojure_1.9.0-5.debian.tar.xz
 a8c7839de8acac75071296d9c0513aff9b6e67dd183ec11500f9fbc24abb00ed 10863 
clojure_1.9.0-5_source.buildinfo
Files:
 ce791f620940a28232ecdf9049ce29d7 2203 devel optional clojure_1.9.0-5.dsc
 6fd88f67d195c8e933a0b5406efdc0e5 13328 devel optional 
clojure_1.9.0-5.debian.tar.xz
 2e53bb2b75e9b9c1e0ef4d968b892c5b 10863 devel optional 
clojure_1.9.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJbZg88XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3RDBCMTc3NUUyNjI2REQ4OTlEMjBCRURE
RUNBMEM5RDMwRUQ5RkUzAAoJEN7KDJ0w7Z/jyvEP/iBJ2YjeorO8ZyMYyqUfLhQg
rfIJBR0Gt5RRjnUE6VJuBtSOpfvEvduXBbX9zxptRdpVNnuOLqvN6UlWe5p2m+ra
sykZ09H/rOe+XOk8+nAM+BmzxlWWnI0uW2ss8idFPTcQGnNsiTeWcKgV4faN7WXL
lDPrgAKraruGdYGPN6gyxS8kNOC+ch41hujkhwLFnVA18psG2tCRCIjsWt4Soa5H
z1n6CotHPCBOa4Xnhpwl1kWWcXhegGO30gwBM0IE+G0a9P0Xa5i5ZCY4p9eTRmQm
ZebQzhZSCgXQjUjUhbWVXCJdEBfByNXi77/Ep3OdiviHGLtrWb0e6OUFPkEm+1MA
dLnMqEfecKUJMvZYfkMtzrXOvyfErLEL/XS0a41A1tnTMBFHQp5MZEfLCa2YsZL1
ihKuh6s3q+kopuapfRQKGPtODbI+rU4p3fv0A+LdymvLUlZctr/AHnIXXaMtgj17
3LD8RfZr4jVPteumRktQctDbv7PVRy9eV5LI/6dwDcPI2FETRAkyBqFHqgasnUKv
7izMwbKNnrL4E4psVrSMI3VxUEJ9Jxod6tTNMkPEvxqRHmPc3JS1g4Gst44aGMFO
Gxfkz1HIfPKq6DYYT0asYzTnbxyoGB1zYZw/rNV4KauLSqfF4fwcmMEWfjhsIt/Y
fhJoLnc5KZLImj4tISJb
=ZiOp
-END PGP SIGNATURE End Message ---

Bug#904772: marked as done (tcpwatch-httpproxy: missing dependency on python-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 20:42:01 +
with message-id 
and subject line Bug#904772: fixed in tcpwatch-httpproxy 1.3.1-3
has caused the Debian Bug report #904772,
regarding tcpwatch-httpproxy: missing dependency on python-pkg-resources
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.)


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

$ tcpwatch-httpproxy
Traceback (most recent call last):
  File "/usr/bin/tcpwatch-httpproxy", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources


Andreas
--- End Message ---
--- Begin Message ---
Source: tcpwatch-httpproxy
Source-Version: 1.3.1-3

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

Debian distribution maintenance software
pp.
Toni Mueller  (supplier of updated tcpwatch-httpproxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 21:31:50 +0200
Source: tcpwatch-httpproxy
Binary: tcpwatch-httpproxy
Architecture: source all
Version: 1.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Toni Mueller 
Changed-By: Toni Mueller 
Description:
 tcpwatch-httpproxy - TCP monitoring and logging tool with support for HTTP 1.1
Closes: 904772
Changes:
 tcpwatch-httpproxy (1.3.1-3) unstable; urgency=medium
 .
   * add dependency (closes: #904772)
Checksums-Sha1:
 d6c1dcffc9f60a98bcae49644a664984664b9c6d 1848 tcpwatch-httpproxy_1.3.1-3.dsc
 d1eb31f6285dcbe8cc64696a2d3216237e52caf6 5284 
tcpwatch-httpproxy_1.3.1-3.debian.tar.xz
 5e2746444157e6931fb374dbfb16c3748440448a 17020 
tcpwatch-httpproxy_1.3.1-3_all.deb
 421f35ee20eb78b3c7266480312c5ef1f559cf81 6581 
tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo
Checksums-Sha256:
 d01c352786376a80590b7b00b13764cc3682d02b0ae58d25a66bc6dde29360d2 1848 
tcpwatch-httpproxy_1.3.1-3.dsc
 f52c4b7406501efa3b2c5c058b6e7d91bdebf51fc220563250125ba2c0b64bfb 5284 
tcpwatch-httpproxy_1.3.1-3.debian.tar.xz
 76f0feff4fe55213331d1b99bdec4461299b11837050fc26e4ce8302adf7b9a4 17020 
tcpwatch-httpproxy_1.3.1-3_all.deb
 98357195fd0e4b9644d10a2d0d889eefc90eb4400924d479c6ee554474458637 6581 
tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo
Files:
 29cd6447996bad9903705c28ea2e0fc1 1848 net optional 
tcpwatch-httpproxy_1.3.1-3.dsc
 b226fdda2b74c4d46f278623aff87e85 5284 net optional 
tcpwatch-httpproxy_1.3.1-3.debian.tar.xz
 13ffb9ac2d63983134707743a1c03dd2 17020 net optional 
tcpwatch-httpproxy_1.3.1-3_all.deb
 f82ffd0de69cb0ddb97620bee9c62a81 6581 net optional 
tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEHfahn8pT+XNT8/NdigpIh0aHr08FAltmBWgQHHRvbmlAZGVi
aWFuLm9yZwAKCRCKCkiHRoevTxbzD/9WYN1Qj/7mMANvQ2i3AAGLEH5R+jCQe6s4
GUu9edaENcJc4qS/Cx+1o4YwsmRM+oB6e5b/Q8sdAGq892/Rd8tV4sNXPBj+gPDN
vE612JyAqDzJGuSkwq8RHy/+MWibILPz52H3wVP7fcOU3TCzq7OtFx+BDBmalu2L
NyNhhyq7v+UuQzLy61ItAkmBRGhviGSM4Mst4PT0TgZhsUSnVy9Dxk885cm1gQhM
wuEUu4ISvWLMIIni2+FUd7G+4xiM468SW4KDuUpSFnRb/sgXyge3K1FJdr56AS6F
yrUqh2jnpLu5tGeI4sXiA74T3hxZbeW0VVenLcfr/MKQK94KlQtcejYV4gxMJuMN
8AhHwZYna82gTvXCdJhU7kCMz/4Mk092bJNyW7kGoggKzJOyHOpsOo5BCj4Qhzcs
pY1r+J97qQatN0m22MpPaHsQoji7ifWmqOi2U8qq0PA0Gm5YsqwvLaYfAEYJzdZF
mWMPqaOzs5YdrbD5VK29v3pTulHWkos1iQDbZUEnaSMtsujZVrN1C7dRTCXTBpsc
XO3CTV48XWDFcWxGxfdMmNKZqsY3sfCnhZqEZxi1F6+Wzo1J9snCj00+p9GQq7Hn
PkkrN+Qlfu91sKKWj2ownzwDoHXfwVMbqbGnPj4t1CGPZP+60xF1w9HecRZH2S12
NdPeRfopVg==
=qLJR
-END PGP SIGNATURE End Message ---

Bug#905382: marked as done (cgit: CVE-2018-14912: directory traversal vulnerability)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 20:36:20 +
with message-id 
and subject line Bug#905382: fixed in cgit 1.1+git2.10.2-3+deb9u1
has caused the Debian Bug report #905382,
regarding cgit: CVE-2018-14912: directory traversal vulnerability
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.)


-- 
905382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cgit
Version: 1.1+git2.10.2-3
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for cgit.

CVE-2018-14912[0]:
| cgit_clone_objects in CGit before 1.2.1 has a directory traversal
| vulnerability when `enable-http-clone=1` is not turned off, as
| demonstrated by a cgit/cgit.cgi/git/objects/?path=../ request.

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-14912
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14912
[1] https://bugs.chromium.org/p/project-zero/issues/detail?id=1627
[2] https://lists.zx2c4.com/pipermail/cgit/2018-August/004176.html
[3] 
https://git.zx2c4.com/cgit/commit/?id=53efaf30b50f095cad8c160488c74bba3e3b2680

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: cgit
Source-Version: 1.1+git2.10.2-3+deb9u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated cgit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 12:27:48 +0200
Source: cgit
Binary: cgit
Architecture: source
Version: 1.1+git2.10.2-3+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Cgit Packaging Team 
Changed-By: Salvatore Bonaccorso 
Description:
 cgit   - hyperfast web frontend for git repositories written in C
Closes: 905382
Changes:
 cgit (1.1+git2.10.2-3+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * clone: fix directory traversal (CVE-2018-14912) (Closes: #905382)
Checksums-Sha1:
 4203d69518c3134d9ec001c04d894a8fad3a190f 2309 cgit_1.1+git2.10.2-3+deb9u1.dsc
 37d74a9266a995c4fc53bd78a5affdf8d214e174 6118627 cgit_1.1+git2.10.2.orig.tar.gz
 2c5292295fcc0f1e081e7812d569fa271e1bc8d2 11508 
cgit_1.1+git2.10.2-3+deb9u1.debian.tar.xz
 abfe9a68f32f856ef369c5cb0d684fc57a471e1f 6336 
cgit_1.1+git2.10.2-3+deb9u1_source.buildinfo
Checksums-Sha256:
 12b6b10a306ba9e624187527d58ec89ea4e05f890f6baa5dde76facd7a617686 2309 
cgit_1.1+git2.10.2-3+deb9u1.dsc
 ca271d2cd188bd8a1d9a103c3d5e889ac67169bd2b9b554fbdaa98cf76e8a2bb 6118627 
cgit_1.1+git2.10.2.orig.tar.gz
 2768eec1f9bc23d762276ce45732bd844ee7835893d898be06094606506cd8c0 11508 
cgit_1.1+git2.10.2-3+deb9u1.debian.tar.xz
 d8ae5a5a7f8a5906e6c0c284746c38cde48bd192a5fa03db165c99b98dd085b9 6336 
cgit_1.1+git2.10.2-3+deb9u1_source.buildinfo
Files:
 6f4fff92c5c61c461e0517fcf970c174 2309 net extra cgit_1.1+git2.10.2-3+deb9u1.dsc
 ed3b45ecf5b8bc4afe92ace523548b26 6118627 net extra 
cgit_1.1+git2.10.2.orig.tar.gz
 a422ce22211961179d0efabafad6d3d4 11508 net extra 
cgit_1.1+git2.10.2-3+deb9u1.debian.tar.xz
 33bee95b83bdef0fd324458ed715b09b 6336 net extra 
cgit_1.1+git2.10.2-3+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAltlgdVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EBj0P/2leun7OtMItU3pJ6fjLERudAwCapM4C
gvMqMc7W0HF9TXZucK9MIn8m8rmiK+Nt7vETk7r9jfkmpgKAAjF8yErh1D/7jD62
ctOOWQQ2+brq5T0RaQ4F6gajeuBSVdmgg8CPiwR7tETQNpLsyMxqJOUBghugiSE3
0ywA2zeS8Mlhc92FsnCJ+A52Ryp/MxgZQFB1c4djaoNGVGlBA4EScX6m39TbnVzD
VPFlk7B2ZliWANT5eMO+GXMk0wjR3+f/GGGRFzIuoPbBuGLJvJE+oxjxuenmmKm/
0u6/mnhlguqBuvSUUyLE3hVblRF3FHFOpiv3eQbIWUota5b5bvdOX9mRtX1/9/Br
xrVtXm9xUag7VF0dM0VXt568IsGXO0EHyePUclknorM1yH9xiJuXBL+mjy5SFaaZ
Nfzj9Z1n6rBZiN

Bug#905441: Bug #905441 in libreoffice-dictionaries marked as pending

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #905441 in libreoffice-dictionaries reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice-dictionaries/commit/4acc4c895e48dd60d0605882e5c1181a1251cba4


Turn the Conflicts on myspell-bg into a versioned Breaks+Replaces

Closes: #905441
Signed-off-by: Mattia Rizzolo 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905441

Processed: Bug #905441 in libreoffice-dictionaries marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905441 [hunspell-bg] hunspell-bg: make conflicts versioned to allow 
installation of transitional myspell-bg package
Added tag(s) pending.

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

Processed: Fixed upstream

[Debian Bug Tracking System]

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

> tags 902458 fixed-upstream
Bug #902458 [src:django-countries] django-countries: FTBFS in buster/sid ("BAD" 
is not a valid choice)
Added tag(s) fixed-upstream.
> forwarded 902458 
> https://github.com/SmileyChris/django-countries/commit/4c57fcecc65862259b997be3fe1f176d310ad2c5
Bug #902458 [src:django-countries] django-countries: FTBFS in buster/sid ("BAD" 
is not a valid choice)
Set Bug forwarded-to-address to 
'https://github.com/SmileyChris/django-countries/commit/4c57fcecc65862259b997be3fe1f176d310ad2c5'.
> thanks
Stopping processing here.

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

Bug#902729: marked as done (Missing Conflicts with libmariadb2)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 19:04:43 +
with message-id 
and subject line Bug#902729: fixed in mariadb-connector-c 1:3.0.6-1
has caused the Debian Bug report #902729,
regarding Missing Conflicts with libmariadb2
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.)


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

Hi,
Trying to install libmariadb3 on a system which already has libmariadb2
installed fails with:

> Unpacking libmariadb3:amd64 (1:3.0.3-2) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libmariadb3_1%3a3.0.3-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/mariadb/plugin/dialog.so', 
> which is also in package libmariadb2:amd64 2.3.3-1

The plugins are in an unversioned directory, present in both packages,
and so the two packages cannot be co-installed. Please add suitable
dependency relationships to the new libmariadb3 package to allow
upgrades to work.

Regards,
James
--- End Message ---
--- Begin Message ---
Source: mariadb-connector-c
Source-Version: 1:3.0.6-1

We believe that the bug you reported is fixed in the latest version of
mariadb-connector-c, 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.
Otto Kekäläinen  (supplier of updated mariadb-connector-c 
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, 05 Aug 2018 00:02:45 +0800
Source: mariadb-connector-c
Binary: libmariadb-dev libmariadb3 libmariadb-dev-compat
Architecture: source
Version: 1:3.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadb-dev - MariaDB Connector/C, development files
 libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
 libmariadb3 - MariaDB Connector/C
Closes: 877622 902729
Changes:
 mariadb-connector-c (1:3.0.6-1) unstable; urgency=low
 .
   * New upstream version 3.0.6 (Closes: #877622)
   * Use versioned in installation path to avoid conflicts (Closes: #902729)
   * Change upstream signing key format to armored ASCII
   * Add rudimentary autopkgtest
Checksums-Sha1:
 1f209e9d03ebb705dcdf75dbc0fe453f92b0cfca 2527 mariadb-connector-c_3.0.6-1.dsc
 2cd90593ece987e3367b42d22acd4756478f8614 666819 
mariadb-connector-c_3.0.6.orig.tar.gz
 15d472acc163cbb00811705362bef7340acb9662 181 
mariadb-connector-c_3.0.6.orig.tar.gz.asc
 2b4070205be4b955195efec8e103c485220f934e 24508 
mariadb-connector-c_3.0.6-1.debian.tar.xz
 3dbd7dcbf8a3d8b850352fd5edb53fe29657 7674 
mariadb-connector-c_3.0.6-1_source.buildinfo
Checksums-Sha256:
 4392198fd92a7776ee9cfe0b0e037f4a177df5e9efd40f72400b58ecc7fc3aef 2527 
mariadb-connector-c_3.0.6-1.dsc
 2b2d18dc969dc385f7f740e4db112300e11bc626c9ba9aa05c284704095b9e48 666819 
mariadb-connector-c_3.0.6.orig.tar.gz
 35848a10cb6d407820dc4ee83fb4ddb6f6ffeeebdae22fc8d56f3d9fd32b66e9 181 
mariadb-connector-c_3.0.6.orig.tar.gz.asc
 022b17732efa859f84cc2f8f319e8eb41b0cf6c8cda73ff2732b2e265b6b5152 24508 
mariadb-connector-c_3.0.6-1.debian.tar.xz
 71ae616d11c5d6044d530bc48c322791824ded47bbb2f3c24a1f22fa5d77444e 7674 
mariadb-connector-c_3.0.6-1_source.buildinfo
Files:
 36f79fa1ffda11f815f9f94714d04c93 2527 libs optional 
mariadb-connector-c_3.0.6-1.dsc
 81c85d8fc696ee65046c0d29b67201be 666819 libs optional 
mariadb-connector-c_3.0.6.orig.tar.gz
 c7a7ec7ed8de14c3c627ede6522e8e74 181 libs optional 
mariadb-connector-c_3.0.6.orig.tar.gz.asc
 39de17847388694ada977cc63580b2d7 24508 libs optional 
mariadb-connector-c_3.0.6-1.debian.tar.xz
 2ce4b860d57ebc8f345ee015313e20de 7674 libs optional 
mariadb-connector-c_3.0.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAltl74EACgkQvthEn87o
2oj/rQ//SzqUujz9HKQMki9AilrKrbrxvfGD54LrOLCecfFSdEPepn89o3bkJaLo
55WEX1GQg5A2cwdNNvM8A1lmiPKOtAxoSgYnaKyQbo2vkJcJGLD2xWWzmfhU7Z8V
9QAsZZnqMQLwgg43Fms15CgCm5ZBXqvc6zYGOx28oXh6KiTgfV/9h+YML7vZ0nIF
PyHbjhI96aMviP5+5ei8zL956gtd0mgax1nrFESqIOgcqKYjqFYGirzkNhH

Processed: laditools: diff for NMU version 1.1.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896305 + patch
Bug #896305 [python-laditools] python-laditools: laditools fails to import
Added tag(s) patch.
> tags 896305 + pending
Bug #896305 [python-laditools] python-laditools: laditools fails to import
Added tag(s) pending.

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

Bug#896305: laditools: diff for NMU version 1.1.0-3.1

[Adrian Bunk]

Control: tags 896305 + patch
Control: tags 896305 + pending

Dear maintainer,

I've prepared an NMU for laditools (versioned as 1.1.0-3.1) and uploaded 
it to DELAYED/15. 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 laditools-1.1.0/debian/changelog laditools-1.1.0/debian/changelog
--- laditools-1.1.0/debian/changelog	2018-05-06 21:28:15.0 +0300
+++ laditools-1.1.0/debian/changelog	2018-08-04 22:02:00.0 +0300
@@ -1,3 +1,11 @@
+laditools (1.1.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move the python-xdg dependency from laditools to python-laditools.
+(Closes: #896305)
+
+ -- Adrian Bunk   Sat, 04 Aug 2018 22:02:00 +0300
+
 laditools (1.1.0-3) unstable; urgency=medium
 
   [ Ross Gammon ]
diff -Nru laditools-1.1.0/debian/control laditools-1.1.0/debian/control
--- laditools-1.1.0/debian/control	2018-05-06 21:28:15.0 +0300
+++ laditools-1.1.0/debian/control	2018-08-04 22:02:00.0 +0300
@@ -25,7 +25,6 @@
  python-gi,
  python-gi-cairo,
  python-laditools,
- python-xdg,
  ${misc:Depends},
  ${python:Depends}
 Recommends: gladish
@@ -59,6 +58,7 @@
  python-dbus,
  python-enum34,
  python-gi,
+ python-xdg,
  ${misc:Depends},
  ${python:Depends}
 Breaks: laditools (<< 1.0)

Bug#899620: marked as done (ns2: Invalid maintainer address pkg-netsim-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 18:04:46 +
with message-id 
and subject line Bug#899620: fixed in ns2 2.35+dfsg-3
has caused the Debian Bug report #899620,
regarding ns2: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
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.)


-- 
899620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ns2
Version: 2.35+dfsg-2.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ns2,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ns2 since the list address
pkg-netsim-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-netsim-de...@lists.alioth.debian.org is 5.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ns2
Source-Version: 2.35+dfsg-3

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated ns2 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, 05 Aug 2018 00:58:43 +0800
Source: ns2
Binary: ns2 ns2-dbg ns2-doc ns2-examples
Architecture: source amd64 all
Version: 2.35+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team 
Changed-By: Aron Xu 
Description:
 ns2- Discrete event simulator targeted at networking research
 ns2-dbg- debug symbols of ns2
 ns2-doc- docs of ns2
 ns2-examples - examples of ns2
Closes: 899620
Changes:
 ns2 (2.35+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Use tracker.d.o address (Closes: #899620)
Checksums-Sha1:
 46e2194133d0b79c2ce6f79de0aef6e630aaa22d 1829 ns2_2.35+dfsg-3.dsc
 b4b888724cf07648114ec6ab280074e716de5591 15744 ns2_2.35+dfsg-3.debian.tar.xz
 96e1eb87c4cf84e4adb7da80a25aaf472e073525 49067684 ns2-dbg_2.35+dfsg-3_amd64.deb
 fb92c46232283182646d49bc2aa40280b230ceb4 1955896 ns2-doc_2.35+dfsg-3_all.deb
 056f5d0549bf973e1fc9743e614b853b4e18c8e7 40277648 
ns2-examples_2.35+dfsg-3_all.deb
 bff7e15320a09ea008559336b2768d01af484235 8672 ns2_2.35+dfsg-3_amd64.buildinfo
 c07fdcb9cf7dc5a75293187075bec8c741c17c13 2436864 ns2_2.35+dfsg-3_amd64.deb
Checksums-Sha256:
 9c7fdc075a60f1f6dd536221a19705157f7f3db57605d52da3052e9a05b7bcb7 1829 
ns2_2.35+dfsg-3.dsc
 5a97d8042de53037391d416d07042b52df7c455df2d00979af3ea8400eaf3139 15744 
ns2_

Bug#880726: marked as done (libmariadb-dev: fails to install - missing replace)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 01:24:33 +0800
with message-id 

and subject line Re: Already fixed
has caused the Debian Bug report #880726,
regarding libmariadb-dev: fails to install - missing replace
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.)


-- 
880726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmariadb-dev
Version: 2.3.3-1
Severity: serious
Justification: fails to install

Preconfiguring packages ...
(Reading database ... 871801 files and directories currently installed.)
Preparing to unpack .../libmariadb-dev_10.2.7-1_amd64.deb ...
Unpacking libmariadb-dev:amd64 (10.2.7-1) over (2.3.3-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev_10.2.7-1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/mysql_config', which is also in package 
libmariadbclient-dev 10.1.28-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Missing replace?

Best

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

Kernel: Linux 4.14.0-rc5+ (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)

Versions of packages libmariadb-dev depends on:
ii  libc62.24-17
pn  libmariadb2  

libmariadb-dev recommends no packages.

libmariadb-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.0.3-1

To restate, this is already fixed both in 2.3 and 3.0 series of
MariaDB Connector C--- End Message ---

Bug#904957: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3

[Rob Browning]

Rob Browning  writes:

> Sounds like I need to (at least) change the replaces line to:
>
>   Replaces: emacs-gtk, emacs-lucid, emacs25-gtk (<<1:25), emacs25-lucid 
> (<<1:25)

...rather:

  Replaces: emacs-gtk, emacs-lucid,
emacs25-nox (<< 1:25) emacs25-gtk (<< 1:25), emacs25-lucid (<< 1:25)

i.e. it perhaps needs to be all three.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#904957: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3

[Rob Browning]

Adrian Bunk  writes:

> But during the upgrade the Replaces is additionally required, for 
> telling dpkg that emacs-lucid contains files that are during the
> upgrade still present from the not yet fully removed emacs25-lucid
> package.

Sven Joachim  writes:

> I think emacs-lucid needs a "Replaces: emacs25-lucid (<< 1:25)" here,
> and similarly for the other flavors.

Ahh, ok.  So I can't use an indirect dependency for that -- in which
case, given the current deps:

  Package: emacs-nox
  Architecture: any
  ...
  Conflicts: emacs-gtk, emacs-lucid
  Replaces: emacs-gtk, emacs-lucid

Sounds like I need to (at least) change the replaces line to:

  Replaces: emacs-gtk, emacs-lucid, emacs25-gtk (<<1:25), emacs25-lucid (<<1:25)

and do something similar to the emacs-lucid and emacs-gtk replaces lines.

Plausible?

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#899707: marked as done (tclcl: Invalid maintainer address pkg-netsim-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 17:20:00 +
with message-id 
and subject line Bug#899707: fixed in tclcl 1.20-9
has caused the Debian Bug report #899707,
regarding tclcl: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
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.)


-- 
899707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tclcl
Version: 1.20-8
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of tclcl,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package tclcl since the list address
pkg-netsim-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-netsim-de...@lists.alioth.debian.org is 5.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tclcl
Source-Version: 1.20-9

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated tclcl 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, 05 Aug 2018 00:56:01 +0800
Source: tclcl
Binary: tclcl libtclcl1 libtclcl1-dev tclcl-dev tclcl-dbg
Architecture: source amd64 all
Version: 1.20-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team 
Changed-By: Aron Xu 
Description:
 libtclcl1  - shared library of TclCL
 libtclcl1-dev - development files of TclCL
 tclcl  - tcl2c++ and otcldoc program from tclcl
 tclcl-dbg  - debug symbols of TclCL: both tclcl and libtclcl1
 tclcl-dev  - transitional dummy package to libtclcl-dev
Closes: 899707
Changes:
 tclcl (1.20-9) unstable; urgency=medium
 .
   * Team upload.
   * Use tracker.d.o address (Closes: #899707)
Checksums-Sha1:
 56b4ee7c7fac4ba53422d779140f34830203afa5 1846 tclcl_1.20-9.dsc
 75f26cb8756c7be06cfa3ef2126e956b2063b9f4 9016 tclcl_1.20-9.debian.tar.xz
 3a4267841fd031468016d676efbdae1e962e4f1f 82912 libtclcl1-dev_1.20-9_amd64.deb
 0dbe6606b9fd5c17de5af2b8b90e9613c2bd010c 76908 libtclcl1_1.20-9_amd64.deb
 7cef55138a1a1bebdf2c7967f721ec750c6e650d 238196 tclcl-dbg_1.20-9_amd64.deb
 dbd99a05fec0f4feafaf643b39e9a25355269c80 18176 tclcl-dev_1.20-9_all.deb
 14a581c33761b92088ffb883e48f406f4fadaa18 8730 tclcl_1.20-9_amd64.buildinfo
 6a180bd7096b50c7d17334ddf5fc8b2032421a73 30376 tclcl_1.20-9_amd64.deb
Checksums-Sha256:
 913f93e604d1744c9d73d43

Bug#898526: marked as done (h5py: FTBFS - FAIL: test_out_of_order_offsets)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 17:19:21 +
with message-id 
and subject line Bug#898526: fixed in h5py 2.8.0-1
has caused the Debian Bug report #898526,
regarding h5py: FTBFS - FAIL: test_out_of_order_offsets
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.)


-- 
898526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h5py
Version: 2.7.1-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

h5py FTBFS with HDF5 1.10.2 currently in experimental. The failure occurs
during the tests where two of them fail:

==
FAIL: test_out_of_order_offsets (h5py.tests.hl.test_datatype.TestOffsets)
- --
Traceback (most recent call last):
  File "h5py/tests/hl/test_datatype.py", line 198, in test_out_of_order_offsets
self.assertArrayEqual(fd['data'], data)
  File "h5py/tests/common.py", line 124, in assertArrayEqual
"Dtype mismatch (%s vs %s)%s" % (dset.dtype, arr.dtype, message)
AssertionError: Dtype mismatch ({'names':['f1','f3','f2'], 
'formats':['--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 2.8.0-1

We believe that the bug you reported is fixed in the latest version of
h5py, 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.
Mo Zhou  (supplier of updated h5py package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 16:54:06 +
Source: h5py
Binary: python-h5py python-h5py-dbg python3-h5py python3-h5py-dbg 
python-h5py-doc
Architecture: source
Version: 2.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 python-h5py - general-purpose Python interface to hdf5 (Python 2)
 python-h5py-dbg - debug extensions for h5py (Python 2)
 python-h5py-doc - documentation for h5py
 python3-h5py - general-purpose Python interface to hdf5 (Python 3)
 python3-h5py-dbg - debug extensions for h5py (Python 3)
Closes: 898526 900419 902553
Changes:
 h5py (2.8.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * New upstream version (Closes: #902553, #898526, #900419)
   * Bump debhelper compat level to 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.4
 .
   [ Mo Zhou ]
   * Remove the ancient X-Python*-Version fields.
   * Bump Standards-Version to 4.2.0 .
 - Remove Priority: extra from control since it had been deprecated.
   * Add the missing B-D python-unittest2 for python2 tests.
Checksums-Sha1:
 de2de2313e98e817285f20f084ad5f8527a0f157 2672 h5py_2.8.0-1.dsc
 b0c57e6bc84adfd0e77eaa9f2ad127cce84e4d81 274576 h5py_2.8.0.orig.tar.gz
 2ed55adcd06c6321995b508c90c370f646ab9ce5 7588 h5py_2.8.0-1.debian.tar.xz
Checksums-Sha256:
 7051e9b77305465e856d34a13d6f54b352bdbc47898802e44d3171cef14574c9 2672 
h5py_2.8.0-1.dsc
 e626c65a8587921ebc7fb8d31a49addfdd0b9a9aa96315ea484c09803337b955 274576 
h5py_2.8.0.orig.tar.gz
 2f6136a855ab521daf3e176b15548e41120464a8b59add48478e3acc0ed4fc63 7588 
h5py_2.8.0-1.debian.tar.xz
Files:
 6cb0f9f17f9c49e9be3a6f511dfc1693 2672 python optional h5py_2.8.0-1.dsc
 ece4f358e69fc8a416f95953b91bc373 274576 python optional h5py_2.8.0.orig.tar.gz
 9969b5d4f5a0c667748560815ded293c 7588 python optional 
h5py_2.8.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAltl2vsACgkQr8/sjmac
4cJ4lRAAkxRTDTW2FCy8SckulrbEdpstE1zNAK8SBlnARHlE82N5lIu6EpuNAMsF
NdSkZP8/gh13Git+Yv8mv7XffPgk/allqhHefUPjixQvYSSP4Mf8BuX3B+uj00Py
82cQFD34w0BbmwtEu1s7ngHPGrKRAcq+T42RpBc/J4gy0AGtbPplsGVg/UL+7Efd
aUzvPD2MMe1zMU2qQSCTzIQ8ezG3/QoHId8M0twiQ6OHJWc3jR3yZ/xeX6znOReg
n4va7GKZw9Ba6Cs9unb3eDz/cYWI9pHDQ0owPQ43T/JelzDwBfdIbtlcK1EX1Iai
7zPUCiBN6EZP1JE4MearciugCPM7sU4/SD4lKSujHPoLhOjPcBvNIyFB7WjSpY+1
bnU6ik3sxZCxP5B0wjoPLUc2f35oEzFdFQhlVri7sm/gMBaVNr+aDK4Vr39Y0TlC
30HIVvik/JyB2I4Z3haD9Zo2TfwkK+ph9L4VdJ/DPAolyK1g9DMqelnWMsyDVbSq
Nprv5odb5rWw8Q4rNrAeuTAxaSVnfsO1Hn+bvClQCNQjgfWBChtdD

Bug#900419: marked as done (h5py: Now emitting warnings, breaking pbgenomicconsensus tests)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 17:19:21 +
with message-id 
and subject line Bug#900419: fixed in h5py 2.8.0-1
has caused the Debian Bug report #900419,
regarding h5py: Now emitting warnings, breaking pbgenomicconsensus 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.)


-- 
900419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h5py
Version: 2.7.1-2
Severity: normal

The pbgenomicconsensus tests are now failing because a warning is being
emitted from h5py with numpy 1.14:

/usr/lib/python2.7/dist-packages/h5py/__init__.py:36: FutureWarning: Conversion 
of the second argument of issubdtype from `float` to `np.floating` is 
deprecated. In future, it will be treated as `np.float64 == 
np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 2.8.0-1

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated h5py package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 16:54:06 +
Source: h5py
Binary: python-h5py python-h5py-dbg python3-h5py python3-h5py-dbg 
python-h5py-doc
Architecture: source
Version: 2.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 python-h5py - general-purpose Python interface to hdf5 (Python 2)
 python-h5py-dbg - debug extensions for h5py (Python 2)
 python-h5py-doc - documentation for h5py
 python3-h5py - general-purpose Python interface to hdf5 (Python 3)
 python3-h5py-dbg - debug extensions for h5py (Python 3)
Closes: 898526 900419 902553
Changes:
 h5py (2.8.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * New upstream version (Closes: #902553, #898526, #900419)
   * Bump debhelper compat level to 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.4
 .
   [ Mo Zhou ]
   * Remove the ancient X-Python*-Version fields.
   * Bump Standards-Version to 4.2.0 .
 - Remove Priority: extra from control since it had been deprecated.
   * Add the missing B-D python-unittest2 for python2 tests.
Checksums-Sha1:
 de2de2313e98e817285f20f084ad5f8527a0f157 2672 h5py_2.8.0-1.dsc
 b0c57e6bc84adfd0e77eaa9f2ad127cce84e4d81 274576 h5py_2.8.0.orig.tar.gz
 2ed55adcd06c6321995b508c90c370f646ab9ce5 7588 h5py_2.8.0-1.debian.tar.xz
Checksums-Sha256:
 7051e9b77305465e856d34a13d6f54b352bdbc47898802e44d3171cef14574c9 2672 
h5py_2.8.0-1.dsc
 e626c65a8587921ebc7fb8d31a49addfdd0b9a9aa96315ea484c09803337b955 274576 
h5py_2.8.0.orig.tar.gz
 2f6136a855ab521daf3e176b15548e41120464a8b59add48478e3acc0ed4fc63 7588 
h5py_2.8.0-1.debian.tar.xz
Files:
 6cb0f9f17f9c49e9be3a6f511dfc1693 2672 python optional h5py_2.8.0-1.dsc
 ece4f358e69fc8a416f95953b91bc373 274576 python optional h5py_2.8.0.orig.tar.gz
 9969b5d4f5a0c667748560815ded293c 7588 python optional 
h5py_2.8.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAltl2vsACgkQr8/sjmac
4cJ4lRAAkxRTDTW2FCy8SckulrbEdpstE1zNAK8SBlnARHlE82N5lIu6EpuNAMsF
NdSkZP8/gh13Git+Yv8mv7XffPgk/allqhHefUPjixQvYSSP4Mf8BuX3B+uj00Py
82cQFD34w0BbmwtEu1s7ngHPGrKRAcq+T42RpBc/J4gy0AGtbPplsGVg/UL+7Efd
aUzvPD2MMe1zMU2qQSCTzIQ8ezG3/QoHId8M0twiQ6OHJWc3jR3yZ/xeX6znOReg
n4va7GKZw9Ba6Cs9unb3eDz/cYWI9pHDQ0owPQ43T/JelzDwBfdIbtlcK1EX1Iai
7zPUCiBN6EZP1JE4MearciugCPM7sU4/SD4lKSujHPoLhOjPcBvNIyFB7WjSpY+1
bnU6ik3sxZCxP5B0wjoPLUc2f35oEzFdFQhlVri7sm/gMBaVNr+aDK4Vr39Y0TlC
30HIVvik/JyB2I4Z3haD9Zo2TfwkK+ph9L4VdJ/DPAolyK1g9DMqelnWMsyDVbSq
Nprv5odb5rWw8Q4rNrAeuTAxaSVnfsO1Hn+bvClQCNQjgfWBChtdDS+2zfsgIoJl
n79BmhIOyXF80lWmQWsQCC5c4uLeVhQWupWktju6e/kjWN52CwwTwGwvtdKIdDo+
WmMLDGlcfa8EdjKrfVH0/+JQwRR+j3itOG5OUXFF9WTZ3o6+uUg=
=NWnh
-END PGP SIGNATURE End Message ---

Bug#899633: marked as done (otcl: Invalid maintainer address pkg-netsim-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 17:19:40 +
with message-id 
and subject line Bug#899633: fixed in otcl 1.14+dfsg-4
has caused the Debian Bug report #899633,
regarding otcl: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
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.)


-- 
899633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:otcl
Version: 1.14+dfsg-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of otcl,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package otcl since the list address
pkg-netsim-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-netsim-de...@lists.alioth.debian.org is 5.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: otcl
Source-Version: 1.14+dfsg-4

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated otcl 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, 05 Aug 2018 00:53:14 +0800
Source: otcl
Binary: libotcl1 otcl-shells libotcl1-dev otcl-dbg
Architecture: source amd64
Version: 1.14+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team 
Changed-By: Aron Xu 
Description:
 libotcl1   - shared library of OTcl
 libotcl1-dev - static library of OTcl
 otcl-dbg   - debug symbol of OTcl (libotcl1 and otcl-shells)
 otcl-shells - OTcl shells
Closes: 899633
Changes:
 otcl (1.14+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Use tracker.d.o address (Closes: #899633)
Checksums-Sha1:
 6e75dcdce87ad70848e01d562353bfe482aafbd8 1779 otcl_1.14+dfsg-4.dsc
 1eef1424653786de510ea79d44409336bced7963 5272 otcl_1.14+dfsg-4.debian.tar.xz
 6e9ccd57d5c21e8e11ce918693de168f83186af8 42472 
libotcl1-dev_1.14+dfsg-4_amd64.deb
 b25915b45f588f8ff20cd3c1ab5ad308c55b3094 29296 libotcl1_1.14+dfsg-4_amd64.deb
 bf572546a9d2f9c54d2cdc18e4c74a7f2ea84a78 154108 otcl-dbg_1.14+dfsg-4_amd64.deb
 8f450963cf35f8f42dab2600dfaef4cb1f074c73 14004 
otcl-shells_1.14+dfsg-4_amd64.deb
 9dba97adca823c470b0ac6d19538a1e89d89551a 8465 otcl_1.14+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 c34c89914852415e4e0a582093ba9c76299b756272699653e5ac40e377a5e6bc 1779 
otcl_1.14+dfsg-4.dsc
 444d412a0625ccdde6c19d8d364f1d5f879ba2b8e24ee83592be

Bug#881073: marked as done (libmariadb-dev: mariadb_config always returns the help text)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 00:44:15 +0800
with message-id 

and subject line Re: [debian-mysql] Bug#881073: libmariadb-dev: mariadb_config 
always returns the help text
has caused the Debian Bug report #881073,
regarding libmariadb-dev: mariadb_config always returns the help text
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.)


-- 
881073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmariadb-dev
Version: 10.2.7-1
Severity: serious
Control: affects -1 src:rmysql

$ mariadb_config --cflags
Copyright 2011-2015 MariaDB Corporation AB
Get compiler flags for using the MariaDB Connector/C.
Usage: /usr/lib/x86_64-linux-gnu/mariadb_config [OPTIONS]
  --cflags[-I/usr/include/mysql -I/usr/include/mysql/mysql]
  --include   [-I/usr/include/mysql -I/usr/include/mysql/mysql]
  --libs  [-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
-lgnutls]
  --libs_r[-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
-lgnutls]
  --libs_sys  [-lpthread -ldl -lm -lgnutls]
  --version   [10.2.7]
  --socket[/var/run/mysqld/mysqld.sock]
  --port  [3306]
  --plugindir [/usr/lib/x86_64-linux-gnu/mariadb3/plugin]
  --tlsinfo   [GnuTLS ]
$ 
--- End Message ---
--- Begin Message ---
ti 7. marrask. 2017 klo 23.09 Adrian Bunk (b...@debian.org) kirjoitti:
>
> Package: libmariadb-dev
> Version: 10.2.7-1
> Severity: serious
> Control: affects -1 src:rmysql
>
> $ mariadb_config --cflags
> Copyright 2011-2015 MariaDB Corporation AB
> Get compiler flags for using the MariaDB Connector/C.
> Usage: /usr/lib/x86_64-linux-gnu/mariadb_config [OPTIONS]
>   --cflags[-I/usr/include/mysql -I/usr/include/mysql/mysql]
>   --include   [-I/usr/include/mysql -I/usr/include/mysql/mysql]
>   --libs  [-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
> -lgnutls]
>   --libs_r[-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
> -lgnutls]
>   --libs_sys  [-lpthread -ldl -lm -lgnutls]
>   --version   [10.2.7]
>   --socket[/var/run/mysqld/mysqld.sock]
>   --port  [3306]
>   --plugindir [/usr/lib/x86_64-linux-gnu/mariadb3/plugin]
>   --tlsinfo   [GnuTLS ]
> $

This seems to have been fixed already.

$ mariadb_config --cflags
-I/usr/include/mariadb -I/usr/include/mariadb/mysql--- End Message ---

Processed: Bug #902729 in mariadb-connector-c marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902729 [libmariadb3] Missing Conflicts with libmariadb2
Added tag(s) pending.

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

Bug#902729: Bug #902729 in mariadb-connector-c marked as pending

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #902729 in mariadb-connector-c reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/mariadb-connector-c/commit/f7845f6a0a7462c07fc53614af3a9713fb94234c


Use versioned in installation path to avoid conflicts (Closes: #902729)

This fixes the error
 Unpacking libmariadb3:amd64 (1:3.0.3-2) ...
 dpkg: error processing archive /var/cache/apt/archives/libmariadb3_\
 1%3a3.0.3-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/mariadb/plugin/dialog.so',
 which is also in package libmariadb2:amd64 2.3.3-1



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902729

Bug#904957: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3

[Sven Joachim]

On 2018-08-04 11:24 -0500, Rob Browning wrote:

> Axel Beckert  writes:
>
>> upgrading emacs25-lucid on armhf pulls in emacs-lucid, but that fails
>> to install as follows:
>>
>> Preparing to unpack .../emacs-lucid_1%3a25.2+1-8_armhf.deb ...
>> Unpacking emacs-lucid (1:25.2+1-8) ...
>> dpkg: error processing archive 
>> /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb (--unpack):
>>  trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in 
>> package emacs25-lucid 25.2+1-6+b3
>> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>> Errors were encountered while processing:
>>  /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb
>>
>> The Replaces header only contains emacs-gtk and emacs-nox, but likely
>> also needs emacs25-lucid. And probably also needs a "Breaks:
>> emacs25-lucid".
>
> I suspect I'm just misunderstanding the dependency system, but this
> confuses me because:
>
>   emacs25-lucid 25.2+1-6+b3
> Depends: emacs25-bin-common
>
> and
>
>   emacs25-bin-common
> Depends: emacs25-common
>
> and on the newer side
>
>   emacs-lucid 1:25.2+1-8
> Depends: emacs-common (= 1:25.2+1-8)
>
> and 
>
>   emacs-common 1:25.2+1-8
> Depends: emacsen-common (>= 3.0.0)
>
> and
>
>   emacsen-common (>= 3.0.0)
> Conflicts: emacs25-common

AFAICS this does not prevent emacs-lucid to be unpacked before
emacs-common and the new emacsen-common and emacs25-lucid versions, in
which case you hit the file conflict.

> So I'd expected the indirect dependency of emacs-lucid on the newer
> emacsen-common to have indirectly forced emacs25-lucid out (via the
> emacsen-common conflicts), so that there wouldn't be a file conflict,
> but obviously I'm missing something (and agree that it's a somewhat
> tortuous route).

I think emacs-lucid needs a "Replaces: emacs25-lucid (<< 1:25)" here,
and similarly for the other flavors.

Cheers,
   Sven

Bug#904957: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3

[Adrian Bunk]

On Sat, Aug 04, 2018 at 11:24:27AM -0500, Rob Browning wrote:
> Axel Beckert  writes:
> 
> > upgrading emacs25-lucid on armhf pulls in emacs-lucid, but that fails
> > to install as follows:
> >
> > Preparing to unpack .../emacs-lucid_1%3a25.2+1-8_armhf.deb ...
> > Unpacking emacs-lucid (1:25.2+1-8) ...
> > dpkg: error processing archive 
> > /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb (--unpack):
> >  trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in 
> > package emacs25-lucid 25.2+1-6+b3
> > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb
> >
> > The Replaces header only contains emacs-gtk and emacs-nox, but likely
> > also needs emacs25-lucid. And probably also needs a "Breaks:
> > emacs25-lucid".
> 
> I suspect I'm just misunderstanding the dependency system, but this
> confuses me because:
> 
>   emacs25-lucid 25.2+1-6+b3
> Depends: emacs25-bin-common
> 
> and
> 
>   emacs25-bin-common
> Depends: emacs25-common
> 
> and on the newer side
> 
>   emacs-lucid 1:25.2+1-8
> Depends: emacs-common (= 1:25.2+1-8)
> 
> and 
> 
>   emacs-common 1:25.2+1-8
> Depends: emacsen-common (>= 3.0.0)
> 
> and
> 
>   emacsen-common (>= 3.0.0)
> Conflicts: emacs25-common
> 
> So I'd expected the indirect dependency of emacs-lucid on the newer
> emacsen-common to have indirectly forced emacs25-lucid out (via the
> emacsen-common conflicts), so that there wouldn't be a file conflict,
> but obviously I'm missing something (and agree that it's a somewhat
> tortuous route).

This needs Breaks+Replaces:
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-in-other-packages

The Breaks part might be covered by the Conflicts relationship you showed.

But during the upgrade the Replaces is additionally required, for 
telling dpkg that emacs-lucid contains files that are during the
upgrade still present from the not yet fully removed emacs25-lucid
package.

> Thanks

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#905446: haskell-hackage-mirror: FTBFS: Module `Control.Monad.Trans.Resource' does not export `monadThrow'

[Andreas Beckmann]

Source: haskell-hackage-mirror
Version: 0.1.1.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: affects -1 + libghc-hackage-mirror-dev libghc-hackage-mirror-doc 
libghc-hackage-mirror-prof

Hi,

haskell-hackage-mirror FTBFS everywhere:
https://buildd.debian.org/status/package.php?p=haskell-hackage-mirror&suite=unstable


[...]
build_recipe
Running debian/hlibrary.setup build --builddir=dist-ghc
Preprocessing library for hackage-mirror-0.1.1.1..
Building library for hackage-mirror-0.1.1.1..
[1 of 1] Compiling Hackage.Mirror   ( src/Hackage/Mirror.hs, 
dist-ghc/build/Hackage/Mirror.o )

src/Hackage/Mirror.hs:75:7: error:
Module `Control.Monad.Trans.Resource' does not export `monadThrow'
   |
75 |   monadThrow,
   |   ^^

src/Hackage/Mirror.hs:82:38: error:
Module `Data.Conduit' does not export `unwrapResumable'
   |
82 | import Data.Conduit ( Source, yield, unwrapResumable, ($=), ($$) )
   |  ^^^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Andreas

Processed: haskell-hackage-mirror: FTBFS: Module `Control.Monad.Trans.Resource' does not export `monadThrow'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libghc-hackage-mirror-dev libghc-hackage-mirror-doc 
> libghc-hackage-mirror-prof
Bug #905446 [src:haskell-hackage-mirror] haskell-hackage-mirror: FTBFS: Module 
`Control.Monad.Trans.Resource' does not export `monadThrow'
Warning: Unknown package 'src:haskell-hackage-mirror'
Added indication that 905446 affects libghc-hackage-mirror-dev, 
libghc-hackage-mirror-doc, and libghc-hackage-mirror-prof
Warning: Unknown package 'src:haskell-hackage-mirror'

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

Processed: Re: Bug#905439: su from util-linux breaks autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #905439 [autopkgtest] su from util-linux breaks autopkgtest
Added tag(s) unreproducible and moreinfo.

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

Bug#905439: su from util-linux breaks autopkgtest

[Antonio Terceiro]

Control: tag -1 + moreinfo unreproducible

On Sat, Aug 04, 2018 at 03:11:17PM +, Lumin wrote:
> Package: autopkgtest
> Version: 5.4.2
> Severity: serious
> 
> the "su" command from util-linux breaks autopkgtest. The previous
> working one comes from shadow.
> 
> python-h5py-dbg is already the newest version (2.8.0-1).
> python-h5py-dbg set to manually installed.
> python-h5py is already the newest version (2.8.0-1).
> python-h5py set to manually installed.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> (Reading database ... 13709 files and directories currently installed.)
> Removing autopkgtest-satdep (0) ...
> autopkgtest [16:38:33]: test command1: set -e ; for py in $(pyversions -r 
> 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
> "import h5py; h5py.run_tests()" ; echo "Testing with $py-dbg:" ; $py-dbg -c 
> "import h5py; h5py.run_tests()" ; done
> autopkgtest [16:38:33]: test command1: [---
> su: user  does not exist
> autopkgtest [16:38:33]: test command1: ---]
> Unexpected error:
> Traceback (most recent call last):
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
> command()
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
> r = f(c, ce)
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
> copyupdown(c, ce, True)
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
> copyupdown_internal(ce[0], c[1:], upp)
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
> copyupdown_internal
> copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
>   File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
> copyup_shareddir
> shutil.copy(tb, host)
>   File "/usr/lib/python3.5/shutil.py", line 241, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.5/shutil.py", line 120, in copyfile
> with open(src, 'rb') as fsrc:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/var/run/schroot/mount/unstable-amd64-debomatic-98e10886-4014-46ea-a35e-37ffe71bdcf3/tmp/autopkgtest.mZ5fp7/command1-stdout'
> autopkgtest [16:38:34]: ERROR: testbed failure: unexpected eof from the 
> testbed

Are you sure you saw this with autopkgtest 5.4.2? This bug was present
5.4.1, but explicitly fixed in 5.4.2.

See the attached log for an attempt I just made at reproducing this. The
tests fail but autopkgtest itself works as expected.
autopkgtest [13:26:52]: version 5.4.2
autopkgtest [13:26:52]: host lemur; command line: /usr/bin/autopkgtest 
--apt-upgrade --log-file /tmp/log -B h5py -- lxc --sudo 
autopkgtest-unstable-amd64
autopkgtest: WARNING: running as root in testbed, because no normal user could 
be determined
autopkgtest [13:27:04]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [233 kB]
Get:2 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [27.8 
kB]
Get:3 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB]
Get:4 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[27.9 kB]
Get:5 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index 
[27.8 kB]
Get:6 http://deb.debian.org/debian unstable/non-free Sources 
2018-08-03-2013.11.pdiff [1,306 B]
Get:7 http://deb.debian.org/debian unstable/non-free Sources 
2018-08-04-0814.44.pdiff [665 B]
Get:8 http://deb.debian.org/debian unstable/main Sources 
2018-08-02-1416.04.pdiff [5,521 B]
Get:7 http://deb.debian.org/debian unstable/non-free Sources 
2018-08-04-0814.44.pdiff [665 B]
Get:9 http://deb.debian.org/debian unstable/main Sources 
2018-08-02-2015.39.pdiff [10.3 kB]
Get:10 http://deb.debian.org/debian unstable/main Sources 
2018-08-03-0208.52.pdiff [3,145 B]
Get:11 http://deb.debian.org/debian unstable/main Sources 
2018-08-03-0811.08.pdiff [15.6 kB]
Get:12 http://deb.debian.org/debian unstable/main Sources 
2018-08-03-1408.50.pdiff [39.5 kB]
Get:13 http://deb.debian.org/debian unstable/main Sources 
2018-08-03-2013.11.pdiff [8,876 B]
Get:14 http://deb.debian.org/debian unstable/main Sources 
2018-08-04-0211.02.pdiff [5,928 B]
Get:15 http://deb.debian.org/debian unstable/main Sources 
2018-08-04-0814.44.pdiff [11.7 kB]
Get:16 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [55.3 
kB]
Get:17 http://deb.debian.org/debian unstable/main Sources 
2018-08-04-1411.17.pdiff [12.2 kB]
Get:18 http://deb.debian.org/debian unstable/main amd64 Packages 
2018-08-02-1416.04.pdiff [27.6 kB]
Get:19 http://deb.debian.org/debian unstable/main amd64 Packages 
2018-08-02-2015.39.pdiff [16.0 kB]
Get:17 http://deb.debian.org/debian unstable/main Sources 
2018-08-04-1411.17.pdiff [12.2 kB]
Get:20 http://deb.debian.org/debian unstable/main amd64 Packages 
2018-08-03-0208.52.pdiff [2,583 B]
Get:21 http://deb.debian.org/debian unstable/main amd64 Packages 
2018-08-03-0811.08.pdiff [13.7 kB]

Bug#905444: libcipux-rpc-client-perl: uninstallable in sid: libcipux-perl is gone

[Andreas Beckmann]

Package: libcipux-rpc-client-perl
Version: 3.4.0.7-2.1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 libcipux-rpc-client-perl : Depends: libcipux-perl (>= 3.4.0.0) but it is not 
installable


Cheers,

Andreas

Bug#904957: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3

[Rob Browning]

Axel Beckert  writes:

> upgrading emacs25-lucid on armhf pulls in emacs-lucid, but that fails
> to install as follows:
>
> Preparing to unpack .../emacs-lucid_1%3a25.2+1-8_armhf.deb ...
> Unpacking emacs-lucid (1:25.2+1-8) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb (--unpack):
>  trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in 
> package emacs25-lucid 25.2+1-6+b3
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb
>
> The Replaces header only contains emacs-gtk and emacs-nox, but likely
> also needs emacs25-lucid. And probably also needs a "Breaks:
> emacs25-lucid".

I suspect I'm just misunderstanding the dependency system, but this
confuses me because:

  emacs25-lucid 25.2+1-6+b3
Depends: emacs25-bin-common

and

  emacs25-bin-common
Depends: emacs25-common

and on the newer side

  emacs-lucid 1:25.2+1-8
Depends: emacs-common (= 1:25.2+1-8)

and 

  emacs-common 1:25.2+1-8
Depends: emacsen-common (>= 3.0.0)

and

  emacsen-common (>= 3.0.0)
Conflicts: emacs25-common

So I'd expected the indirect dependency of emacs-lucid on the newer
emacsen-common to have indirectly forced emacs25-lucid out (via the
emacsen-common conflicts), so that there wouldn't be a file conflict,
but obviously I'm missing something (and agree that it's a somewhat
tortuous route).

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#904854: gemma ftbfs in unstable (test failures and libquadmath not available on all architectures)

[Adrian Bunk]

On Sun, Jul 29, 2018 at 01:50:56AM +0200, Matthias Klose wrote:
> Package: src:gemma
> Version: 0.97+dfsg-3
> Severity: serious
> Tags: sid buster
> 
> gemma ftbfs in unstable (test failures and libquadmath not available on all
> architectures).  Please check the availability of libquadmath before 
> explicitly
> linking with libquadmath.

This is already covered (with patch) in #902153.

> on amd64:
> 
> Ran 12 tests.
> 
> FAILED (failures=11)
> tail -n 1 test.log | grep -q OK
> make[1]: *** [Makefile:175: slow-check] Error 1
> make[1]: Leaving directory '/<>/gemma-0.97+dfsg'
> dh_auto_test: make -j4 check returned exit code 2
> make: *** [debian/rules:18: build-arch] Error 2

This one is new (seems it got broken in June) and should be tracked with 
this bug here.

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#897826: marked as done (openfoam: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 16:04:40 +
with message-id 
and subject line Bug#897826: fixed in openfoam 4.1+dfsg1-2.1
has caused the Debian Bug report #897826,
regarding openfoam: ftbfs with GCC-8
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.)


-- 
897826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openfoam
Version: 4.1+dfsg1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/openfoam_4.1+dfsg1-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
 "minor", you should undefine it after including .
 stat[8] = label(minor(fStat.status_.st_rdev));
 ^~ 



 
g++ -std=c++0x -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -g -O2 
-fdebug-prefix-map=/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3  -DNoRepository 
-ftemplate-depth-100  -IlnInclude -I. 
-I/<>/openfoam-4.1+dfsg1/src/OpenFOAM/lnInclude 
-I/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX/lnInclude   -fPIC -c 
cpuTime/cpuTime.C -o 
/<>/openfoam-4.1+dfsg1/platforms/linux64Gcc51/src/OSspecific/POSIX/cpuTime/cpuTime.o
g++ -std=c++0x -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -g -O2 
-fdebug-prefix-map=/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3  -DNoRepository 
-ftemplate-depth-100  -IlnInclude -I. 
-I/<>/openfoam-4.1+dfsg1/src/OpenFOAM/lnInclude 
-I/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX/lnInclude   -fPIC -c 
clockTime/clockTime.C -o 
/<>/openfoam-4.1+dfsg1/platforms/linux64Gcc51/src/OSspecific/POSIX/clockTime/clockTime.o
g++ -std=c++0x -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -g -O2 
-fdebug-prefix-map=/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3  -DNoRepository 
-ftemplate-depth-100  -IlnInclude -I. 
-I/<>/openfoam-4.1+dfsg1/src/OpenFOAM/lnInclude 
-I/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX/lnInclude   -fPIC -c 
memInfo/memInfo.C -o 
/<>/openfoam-4.1+dfsg1/platforms/linux64Gcc51/src/OSspecific/POSIX/memInfo/memInfo.o
g++ -std=c++0x -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -g -O2 
-fdebug-prefix-map=/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3  -DNoRepository 
-ftemplate-depth-100  -IlnInclude -I. 
-I/<>/openfoam-4.1+dfsg1/src/OpenFOAM/lnInclude 
-I/<>/openfoam-4.1+dfsg1/src/OSspecific/POSIX/lnInclude   -fPIC -c 
fileMonitor.C -o 
/<>/openfoam-4.1+dfsg1/platforms/linux64Gcc51/src/OSspecific/POSIX/fileMonitor.o
g++ -std=c++0x -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-inva

Bug#904888: marked as done (python3-django-q fails to install (Python 3.7 compatibility))

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 16:03:53 +
with message-id 
and subject line Bug#903522: fixed in django-q 0.9.4-2
has caused the Debian Bug report #903522,
regarding python3-django-q fails to install (Python 3.7 compatibility)
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.)


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

python3-django-q fails to install. Proposed patch at
https://github.com/Koed00/django-q/pull/306

Thanks to Michael Hudson for the pointer.


Setting up python3-django-q (0.9.4-1) ...
  File "/usr/lib/python3/dist-packages/django_q/__init__.py", line 15
from .tasks import async, schedule, result, result_group, fetch,
fetch_group, count_group, delete_group, queue_size
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/admin.py", line 5
from django_q.tasks import async
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 539
s.task = tasks.async(s.func, *args, **kwargs)
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tasks.py", line 20
def async(func, *args, **kwargs):
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_cached.py", line 8
from django_q.tasks import async, result, fetch, count_group, result_group,
fetch_group, delete_group, delete_cached, \
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_cluster.py", line 16
from django_q.tasks import fetch, fetch_group, async, result, result_group,
count_group, delete_group, queue_size
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_monitor.py", line 3
from django_q.tasks import async
   ^
SyntaxError: invalid syntax

dpkg: error processing package python3-django-q (--configure):
 installed python3-django-q package post-installation script subprocess returned
error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: django-q
Source-Version: 0.9.4-2

We believe that the bug you reported is fixed in the latest version of
django-q, 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.
Pierre-Elliott Bécue  (supplier of updated django-q 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: Fri, 03 Aug 2018 18:12:34 +0200
Source: django-q
Binary: python-django-q python3-django-q python-django-q-doc
Architecture: source
Version: 0.9.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Pierre-Elliott Bécue 
Description:
 python-django-q - Django multiprocessing distributed task queue (Python 2 
version)
 python-django-q-doc - Django multiprocessing distributed task queue 
(Documentation)
 python3-django-q - Django multiprocessing distributed task queue (Python 3 
version)
Closes: 903522
Changes:
 django-q (0.9.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
 .
   [ Pierre-Elliott Bécue ]
   * d/patches:
 - Add patch 0003, validated by upstream, to fix the python3.7 issues.
   (Closes: #903522)
   * d/control:
 - Bump Standards-Version to 4.1.5. Implements R3 and get-orig-source
 removal.
   * d/rules:
 - Drop get-orig-source rule
   * d/NEWS:
 - Add the breaking changes for this release.
Checksums-Sha1:
 728146380157a601f56457db2f30f307d71dfd8b 2538 django-q_0.9.4-2.dsc
 13c62e07d4ce036ba0f093c5ae5fd1290e87f26a 14536 django-q_0.9.4-2.debian.tar.xz
 a63fb3488c9e1f6e8cb4dcb435204a6d10b522df 9443 django-q_0.9.4-2_amd64.buildinfo
Checksums-Sha256:
 9bd3b65de2be58007a1fc3e6360aafa80f34600ee5f555e79f

Bug#903522: marked as done (python3-django-q fails to install with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 16:03:53 +
with message-id 
and subject line Bug#903522: fixed in django-q 0.9.4-2
has caused the Debian Bug report #903522,
regarding python3-django-q fails to install with Python 3.7 as supported version
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.)


-- 
903522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-q
Version: 0.9.4-1
Severity: grave
Control: block 902788 by -1

Setting up python3-django-q (0.9.4-1) ...
  File "/usr/lib/python3/dist-packages/django_q/__init__.py", line 15
from .tasks import async, schedule, result, result_group, fetch, 
fetch_group, count_group, delete_group, queue_size
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/admin.py", line 5
from django_q.tasks import async
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 539
s.task = tasks.async(s.func, *args, **kwargs)
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tasks.py", line 20
def async(func, *args, **kwargs):
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_cached.py", line 8
from django_q.tasks import async, result, fetch, count_group, result_group, 
fetch_group, delete_group, delete_cached, \
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_cluster.py", line 16
from django_q.tasks import fetch, fetch_group, async, result, result_group, 
count_group, delete_group, queue_size
   ^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/django_q/tests/test_monitor.py", line 3
from django_q.tasks import async
   ^
SyntaxError: invalid syntax

dpkg: error processing package python3-django-q (--configure):
 installed python3-django-q package post-installation script subprocess 
returned error exit status 1
--- End Message ---
--- Begin Message ---
Source: django-q
Source-Version: 0.9.4-2

We believe that the bug you reported is fixed in the latest version of
django-q, 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.
Pierre-Elliott Bécue  (supplier of updated django-q 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: Fri, 03 Aug 2018 18:12:34 +0200
Source: django-q
Binary: python-django-q python3-django-q python-django-q-doc
Architecture: source
Version: 0.9.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Pierre-Elliott Bécue 
Description:
 python-django-q - Django multiprocessing distributed task queue (Python 2 
version)
 python-django-q-doc - Django multiprocessing distributed task queue 
(Documentation)
 python3-django-q - Django multiprocessing distributed task queue (Python 3 
version)
Closes: 903522
Changes:
 django-q (0.9.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
 .
   [ Pierre-Elliott Bécue ]
   * d/patches:
 - Add patch 0003, validated by upstream, to fix the python3.7 issues.
   (Closes: #903522)
   * d/control:
 - Bump Standards-Version to 4.1.5. Implements R3 and get-orig-source
 removal.
   * d/rules:
 - Drop get-orig-source rule
   * d/NEWS:
 - Add the breaking changes for this release.
Checksums-Sha1:
 728146380157a601f56457db2f30f307d71dfd8b 2538 django-q_0.9.4-2.dsc
 13c62e07d4ce036ba0f093c5ae5fd1290e87f26a 14536 django-q_0.9.4-2.debian.tar.xz
 a63fb3488c9e1f6e8cb4dcb435204a6d10b522df 9443 django-q_0.9.4-2_amd64.buildinfo
Checksums-Sha256:
 9bd3b65de2be58007a1fc3e6360aafa80f34600ee5f555e79f2b9689b50dd8eb 2538 
django-q_0.9.4-2.dsc
 46bc3a6e4d2c9cde6b112ea8a73df6eda515768a866cc534a0d56b55c6c43457 14536 
django-q_0.9.4-2.debian.tar.xz
 8114d1fa3e9de644edb2ff55

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> severity 898473 serious
Bug #898473 [fio] Build fio for generic CPU
Severity set to 'serious' from 'normal'
> forcemerge 898473 904830
Bug #898473 [fio] Build fio for generic CPU
Bug #898473 [fio] Build fio for generic CPU
Marked as found in versions fio/3.6-4.
Added tag(s) a11y.
Bug #904830 [fio] fio not started
Severity set to 'serious' from 'critical'
Marked as found in versions fio/3.6-1.
Merged 898473 904830
> thanks
Stopping processing here.

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

Bug#903587: marked as done (src:linux: FTBFS on arm64: of_mdio module in two packages)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 16:00:10 +
with message-id 
and subject line Bug#903587: fixed in linux-signed-amd64 4.18~rc4+1~exp1
has caused the Debian Bug report #903587,
regarding src:linux: FTBFS on arm64: of_mdio module in two packages
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.)


-- 
903587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.18~rc3-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

of_mdio module in two packages on amd64

Hi,

buildlogs for experimental¹ hints that amd64 package failed to build:

> some modules are in more than one package
> debian/nic-usb-modules-4.18.0-rc3-arm64-di 
> lib/modules/4.18.0-rc3-arm64/kernel/drivers/of/of_mdio.ko
> debian/nic-modules-4.18.0-rc3-arm64-di 
> lib/modules/4.18.0-rc3-arm64/kernel/drivers/of/of_mdio.ko



https://buildd.debian.org/status/package.php?p=linux&suite=experimental



 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAltGHeEACgkQLHwxRsGg
ASEi4hAAmSyghQBrvT1OM08YR91h1YQitcBuQj4uOX8CW0lEwkYvrcjU5zYfzDja
e5TUAxfilyrjaaUFLS63xbKZC9hCU+y8/hW7unxqlJpLd2DkENzUGi/H/e/nG1PY
cdpGnayOhWErQqiiuvdBAMPM3HhrJZhheAvI9SkDDyPFDjXwKFnT8faB8Cldr7Al
i0yHTmkaZphjNvhb+OOLkesfntctPMDMk8chZVCpRrDGRWeQvri1vEuDo36rWl5r
/S1eoKq/6mwEwwtGQmDjga2rmo+4f5i2M9v+eBJwN1irYyh8sa3GFeEMnV2Ka4KB
ubFtfHXiChjra5vGEG7fO+YokugPs8gIjPBKK7m0YlJY4EMiPZGQpMh0Kq5S50bg
+Pz4V8fkv6zL5kDS9NeEIJJ+2NA4jaTR7/NZd0bJHPjR/QmQABaetSKKt9BWHskI
tc8dinjIXifnEVG09cHxyrSp9LHfinzS17wXK3Ujq5P3oo1LaI8TfzvFqrUIyW4b
U1fDH96AyzjyUghITn3eUoeVI6Ra7PKexqmIYTVH+sMQEMCViHOut2cnLycBlpT5
uhRygYl3RdgtnIFtiU0kVtAYp3kbkeLzZXGZFBvt5btrC8p1VITsamo/K4UB9XhG
kno5N65tqeCyGg6MnRUZ4IqOaVsXZQXIN/ac7oF1PRcI6J5Ou7c=
=E0Ql
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: linux-signed-amd64
Source-Version: 4.18~rc4+1~exp1

We believe that the bug you reported is fixed in the latest version of
linux-signed-amd64, 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.
Ben Hutchings  (supplier of updated linux-signed-amd64 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Jul 2018 05:12:50 +0100
Source: linux-signed-amd64
Binary: kernel-image-4.18.0-rc4-amd64-di nic-modules-4.18.0-rc4-amd64-di 
nic-wireless-modules-4.18.0-rc4-amd64-di nic-shared-modules-4.18.0-rc4-amd64-di 
serial-modules-4.18.0-rc4-amd64-di usb-serial-modules-4.18.0-rc4-amd64-di 
ppp-modules-4.18.0-rc4-amd64-di pata-modules-4.18.0-rc4-amd64-di 
cdrom-core-modules-4.18.0-rc4-amd64-di 
firewire-core-modules-4.18.0-rc4-amd64-di scsi-core-modules-4.18.0-rc4-amd64-di 
scsi-modules-4.18.0-rc4-amd64-di loop-modules-4.18.0-rc4-amd64-di 
btrfs-modules-4.18.0-rc4-amd64-di ext4-modules-4.18.0-rc4-amd64-di 
isofs-modules-4.18.0-rc4-amd64-di jfs-modules-4.18.0-rc4-amd64-di 
ntfs-modules-4.18.0-rc4-amd64-di xfs-modules-4.18.0-rc4-amd64-di 
fat-modules-4.18.0-rc4-amd64-di md-modules-4.18.0-rc4-amd64-di 
multipath-modules-4.18.0-rc4-amd64-di usb-modules-4.18.0-rc4-amd64-di 
usb-storage-modules-4.18.0-rc4-amd64-di 
pcmcia-storage-modules-4.18.0-rc4-amd64-di fb-modules-4.18.0-rc4-amd64-di 
input-modules-4.18.0-rc4-amd64-di
 event-modules-4.18.0-rc4-amd64-di mouse-modules-4.18.0-rc4-amd64-di 
nic-pcmcia-modules-4.18.0-rc4-amd64-di pcmcia-modules-4.18.0-rc4-amd64-di 
nic-usb-modules-4.18.0-rc4-amd64-di sata-modules-4.18.0-rc4-amd64-di 
acpi-modules-4.18.0-rc4-amd64-di i2c-modules-4.18.0-rc4-amd64-di 
crc-modules-4.18.0-rc4-amd64-di crypto-modules-4.18.0-rc4-amd64-di 
crypto-dm-modules-4.18.0-rc4-amd64-di efi-modules-4.18.0-rc4-amd64-di 
ata-modules-4.18.0-rc4-amd64-di mmc-core-modules-4.18.0-rc4-amd64-di 
mmc-modules-4.18.0-rc4-amd64-di nbd-modules-4.18.0-rc4-amd64-di 
squashfs-modules-4.18.0-rc4-amd64-di speakup-modules-4.18.0-rc4-amd64-di 
virtio-modules-4.18.0-rc4-amd64-di uinput-modules-4.18.0-rc4-amd64-di 
sound-modules-4.18.0-rc4-amd64-di compres

Bug#904825: aces3 ftbfs in unstable

[Adrian Bunk]

Control: reassign -1 src:openmpi 3.1.1.real-3
Control: affects -1 src:aces3

On Sat, Jul 28, 2018 at 01:01:04PM +0200, Matthias Klose wrote:
> Package: src:aces3
> Version: 3.0.8-5.1
> Tags: sid buster
> Severity: serious
>...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> (cd tests; OMPI_MCA_orte_rsh_agent=/bin/false csh ./runscript-quick)
> Running 1.1.1.1
> --
> MPI_ABORT was invoked on rank 1 in communicator MPI_COMM_WORLD
> with errorcode 1.
> 
> NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
> You may or may not see output from other processes, depending on
> exactly when Open MPI kills them.
> --
> E: Build killed with signal TERM after 150 minutes of inactivity
> 

The timing when it started [1] strongly hints at openmpi as root cause.

#904779 is also for an openmpi hang, not sure whether or not this is related.

cu
Adrian

[1] https://tests.reproducible-builds.org/debian/history/aces3.html

-- 

   "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

Processed: Re: Bug#904825: aces3 ftbfs in unstable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:openmpi 3.1.1.real-3
Bug #904825 [src:aces3] aces3 ftbfs in unstable
Bug reassigned from package 'src:aces3' to 'src:openmpi'.
No longer marked as found in versions aces3/3.0.8-5.1.
Ignoring request to alter fixed versions of bug #904825 to the same values 
previously set
Bug #904825 [src:openmpi] aces3 ftbfs in unstable
Marked as found in versions openmpi/3.1.1.real-3.
> affects -1 src:aces3
Bug #904825 [src:openmpi] aces3 ftbfs in unstable
Added indication that 904825 affects src:aces3

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

Processed: ball: FTBFS - test failures

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python-ball
Bug #905443 [src:ball] ball: FTBFS - test failures
Added indication that 905443 affects python-ball

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

Bug#905443: ball: FTBFS - test failures

[Andreas Beckmann]

Source: ball
Version: 1.4.3~beta1-4
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-ball

Hi,

ball FTBFS on most architectures:
https://buildd.debian.org/status/package.php?p=ball&suite=unstable
keeping uninstallable packages in the archive that depend on the no
longer available sip-api-11.3.


Andreas

Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.1

[Adrian Bunk]

On Sat, Aug 04, 2018 at 01:09:49PM +0200, Anton Gladky wrote:
> Dear Adrian,

Hi Anton,

> thank you for the patch! I actually also started to fix
> the issue, but still not finished. Please feel free to move
> the upload to DELAYED/0.

thanks, done.

> Also it would be good if you push
> your changes into the git-repo.

That's permission denied since I'm not a member.

> Thanks
> 
> Anton

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

Processed: hunspell-bg: make conflicts versioned to allow installation of transitional myspell-bg package

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + myspell-bg
Bug #905441 [hunspell-bg] hunspell-bg: make conflicts versioned to allow 
installation of transitional myspell-bg package
Added indication that 905441 affects myspell-bg

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

Bug#905441: hunspell-bg: make conflicts versioned to allow installation of transitional myspell-bg package

[Andreas Beckmann]

Package: hunspell-bg
Version: 1:6.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + myspell-bg

Hi,

during a test with piuparts I noticed your package prevents installation
of the transitional myspell-bg package (which in turn depends on
hunspell-bg) because of the unversioned conflict with it.

Please make the conflict versioned: 
  Conflicts: myspell-bg (<< 4.1-5)
or better switch to Breaks:
  Breaks: myspell-bg (<< 4.1-5)
to avoid a lintian warning on versioned Conflicts.
In case the old myspell-bg and the current hunspell-bg have file
conflicts, add a matching Replaces:
  Replaces: myspell-bg (<< 4.1-5)


cheers,

Andreas

Bug#905439: su from util-linux breaks autopkgtest

[Lumin]

Package: autopkgtest
Version: 5.4.2
Severity: serious

the "su" command from util-linux breaks autopkgtest. The previous
working one comes from shadow.

python-h5py-dbg is already the newest version (2.8.0-1).
python-h5py-dbg set to manually installed.
python-h5py is already the newest version (2.8.0-1).
python-h5py set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
(Reading database ... 13709 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [16:38:33]: test command1: set -e ; for py in $(pyversions -r 
2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
"import h5py; h5py.run_tests()" ; echo "Testing with $py-dbg:" ; $py-dbg -c 
"import h5py; h5py.run_tests()" ; done
autopkgtest [16:38:33]: test command1: [---
su: user  does not exist
autopkgtest [16:38:33]: test command1: ---]
Unexpected error:
Traceback (most recent call last):
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
command()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
r = f(c, ce)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
copyupdown(c, ce, True)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
copyupdown_internal(ce[0], c[1:], upp)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
copyupdown_internal
copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
copyup_shareddir
shutil.copy(tb, host)
  File "/usr/lib/python3.5/shutil.py", line 241, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.5/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/run/schroot/mount/unstable-amd64-debomatic-98e10886-4014-46ea-a35e-37ffe71bdcf3/tmp/autopkgtest.mZ5fp7/command1-stdout'
autopkgtest [16:38:34]: ERROR: testbed failure: unexpected eof from the testbed

Processed: fixed 894736 in 3.7.0-1+deb9u2

[Debian Bug Tracking System]

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

> fixed 894736 3.7.0-1+deb9u2
Bug #894736 {Done: Andrea Capriotti } [vim-syntastic] 
vim-syntastic: CVE-2018-11319: Checker config files allow arbitrary code 
execution scenarios
Marked as fixed in versions vim-syntastic/3.7.0-1+deb9u2.
> thanks
Stopping processing here.

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

Bug#905438: htslib: FTBFS on i386: 2 tests fail

[Andreas Beckmann]

Source: htslib
Version: 1.9-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

htslib/experimental FTBFS on i386:
https://buildd.debian.org/status/fetch.php?pkg=htslib&arch=i386&ver=1.9-1&stamp=1532825380&raw=0


  ./test_view -@4 -i reference=ce.fa range.cram CHROMOSOME_II:2980-2980 
CHROMOSOME_IV:1500-1500 CHROMOSOME_II:2980-2980 CHROMOSOME_I:1000-1100 > 
range.tmp
  ./compare_sam.pl range.tmp range.out
  ./test_view -@4 range.bam CHROMOSOME_II:2980-2980 CHROMOSOME_IV:1500-1500 
CHROMOSOME_II:2980-2980 CHROMOSOME_I:1000-1100 > range.tmp
  ./compare_sam.pl range.tmp range.out
test_vcf_api:
/<>/test/test-vcf-api /tmp/JMIB5wVvT_/test-vcf-api.bcf
bcf_get_format_float didn't produce the expected output.

.. failed ...

test_vcf_sweep:
/<>/test/test-vcf-sweep /tmp/JMIB5wVvT_/test-vcf-api.bcf

The outputs differ:
/<>/test/test-vcf-sweep.out
/<>/test/test-vcf-sweep.out.new
.. failed ...


Andreas

Bug#905434: fpylll: FTBFS: error: 'class fplll::MatrixRow<...>' has no member named 'dot_product'

[Andreas Beckmann]

Source: fpylll
Version: 0.4.1+ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

fpylll/experimental recently started to FTBFS, maybe related to the
switch of the default gcc to gcc-8.

[...]
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/fpylll-0.4.1+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security -W
date-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/cysignals -I/usr/include 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c build/src/fpylll/fplll/integer_matr
ix.cpp -o build/temp.linux-amd64-2.7/build/src/fpylll/fplll/integer_matrix.o 
-std=c++11 -g -O2 -fdebug-prefix-map=/build/fpylll-0.4.1+ds1=. 
-fstack-protector-strong -Wformat -Werror=format-security
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC 
but not for C++
build/src/fpylll/fplll/integer_matrix.cpp: In function 'PyObject* 
__pyx_pf_6fpylll_5fplll_14integer_matrix_16IntegerMatrixRow_10__abs__(__pyx_obj_6fpylll_5fplll_14integer_matrix_IntegerMatrixRow*)':
build/src/fpylll/fplll/integer_matrix.cpp:3285:58: error: 'class 
fplll::MatrixRow >' has no member named 
'dot_product'
 
((__pyx_v_self->m->_core.mpz[0])[__pyx_v_self->row]).dot_product(__pyx_v_t_mpz, 
((__pyx_v_self->m->_core.mpz[0])[__pyx_v_self->row]));
  ^~~
build/src/fpylll/fplll/integer_matrix.cpp:3374:65: error: 'class 
fplll::MatrixRow >' has no member named 'dot_product'
 
((__pyx_v_self->m->_core.__pyx_long[0])[__pyx_v_self->row]).dot_product(__pyx_v_t_l,
 ((__pyx_v_self->m->_core.__pyx_long[0])[__pyx_v_self->row]));
 ^~~
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build] Error 25


Andreas


fpylll_0.4.1+ds1-1.log.gz
Description: application/gzip

Bug#902467: [pkg-go] Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

[Shengjing Zhu]

On Sat, Aug 4, 2018 at 7:35 AM Anthony Fok  wrote:
> For some reasons, however, I have been unable to reproduce this test
> FAIL on my own machine.
>

It always fails on my cpu-busy server(same in upstream issue report)

> So, yes, skipping TestExecutableDelete is the entirely pragmatic thing
> to do, but there is this little voice in my gut urging me to learn to
> diagnose what exactly triggers this intermittent test failure, and if
> it is indeed a race condition, how to fix it?  :-)

The race is when os.Remove and os.Executable are called. I don't see
there's a fix instead of rewriting the logic...


-- 
Best regards,
Shengjing Zhu

Bug#904775: marked as done (Broken dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 4 Aug 2018 17:26:11 +0300
with message-id <20180804142611.GC7454@localhost>
and subject line Recent enough util-linux is now in unstable
has caused the Debian Bug report #904775,
regarding Broken dependencies
to be marked as done.

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

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


-- 
904775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: login
Version: 1:4.5-1
Severity: grave

Dear Maintainer,
please don't break util-linux that is not even released. At least _one_ valid 
util-linux
should be available. Thanks.

W: See /var/cache/pyfll/fll_lxCa2q/amd64/debootstrap/debootstrap.log for 
details (possibly the package util-linux is at fault)
2018-07-27 21:30:20,668 CRITICAL - command failed with return value: 1
2018-07-27 21:30:20,669 INFO  - cleaning up...

Cheers Alf

-- 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.17.9-towo.1-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 login depends on:
ii  libaudit1   1:2.8.3-1+b1
ii  libc6   2.27-5
ii  libpam-modules  1.1.8-3.7
ii  libpam-runtime  1.1.8-3.7
ii  libpam0g1.1.8-3.7

login recommends no packages.

login suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Recent enough util-linux is now in unstable.

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--- End Message ---

Processed: found 904755 in 0.22.0-1

[Debian Bug Tracking System]

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

> found 904755 0.22.0-1
Bug #904755 [yapf] yapf: missing dependency on python-pkg-resources
Marked as found in versions yapf/0.22.0-1.
> thanks
Stopping processing here.

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

Processed: tagging 904740

[Debian Bug Tracking System]

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

> tags 904740 + buster sid
Bug #904740 {Done: gregor herrmann } [src:libtext-bidi-perl] 
libtext-bidi-perl: FTBFS: 'fribidi_uint32' undeclared
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#903069: marked as done (qiime FTBFS: update Build-Depends: ruby-ronn -> ronn)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 13:49:51 +
with message-id 
and subject line Bug#903069: fixed in qiime 1.9.1+dfsg-3
has caused the Debian Bug report #903069,
regarding qiime FTBFS: update Build-Depends: ruby-ronn -> ronn
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.)


-- 
903069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qiime
Version: 1.9.1+dfsg-2
Severity: serious

Since ronn got split out of ruby-ronn, qiime fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn as qiime uses the command
line tool.

Helmut
--- End Message ---
--- Begin Message ---
Source: qiime
Source-Version: 1.9.1+dfsg-3

We believe that the bug you reported is fixed in the latest version of
qiime, 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.
Andreas Tille  (supplier of updated qiime package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Aug 2018 15:14:39 +0200
Source: qiime
Binary: qiime qiime-doc qiime-data
Architecture: source
Version: 1.9.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 qiime  - Quantitative Insights Into Microbial Ecology
 qiime-data - Quantitative Insights Into Microbial Ecology (supporting data)
 qiime-doc  - Quantitative Insights Into Microbial Ecology (tutorial)
Closes: 903069
Changes:
 qiime (1.9.1+dfsg-3) unstable; urgency=medium
 .
   * Build-Depends: ruby-ronn -> ronn
 Closes: #903069
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.5
Checksums-Sha1:
 22a5b7570f799022e17939f4b0af3bb426e302d7 2316 qiime_1.9.1+dfsg-3.dsc
 c8ab934ba35c03b24802299d36a99db0d53fdf4d 25140 qiime_1.9.1+dfsg-3.debian.tar.xz
Checksums-Sha256:
 4955c80a517fd71cd778123e0f7424ab231d5c93904bdc6329145c6a3d8f8c16 2316 
qiime_1.9.1+dfsg-3.dsc
 cad29929679e81b1da2c04a508de8ce8879eee47a349902a55827c0387c24f96 25140 
qiime_1.9.1+dfsg-3.debian.tar.xz
Files:
 f20aeea0b9d24c44c29dbf77831efcd9 2316 science optional qiime_1.9.1+dfsg-3.dsc
 1791bdd29fd44cd6d8a28a85e15d8c29 25140 science optional 
qiime_1.9.1+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltlrJIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGtuA//ZLyZsHU9XG7JNLcg3O4ZxvM9xXbutPXV
6v0v/UZp9r3DVjwD4xiuvNM13oJHeiUhPEniIb0xwj8gZCYJEksK1BayzKM7LkZG
5qHH9tHI0OiijE/pbPtpE6nfkokbvU2XjGCOI6efi969rrqFUXJ9zoOty+S0eZId
qOsFJGRxi+Qa2yhyXA03yTmW9pCBNguhIjAaTCRc1fs9R/+ymRAkEkxEWqCNQziS
jFr6Q+Dcm5kNBR4IgpdO1/5GtvUfC8opJDPwzqudiqGIBkJzNAG4vUDEaz4/db8g
0tSVYkoe2SD0VZtvjAHdRwQLmb67WxezbZdvnvTSI3FFDC4kt7ymPKcwKFiqRTtb
vOWAQnN3UJ5JwTkNWhISxkBidjJ615DxRe+aQYQIgsiyP54vQnyL8tMA50dLcnrV
Cx4rx4n+j02rjkgi9cJTfyyGgOorrfjWvxOz0wXSmpiuF9R2+WguBQwrr5ysfXfV
i7tcIy5oTNKECywk2HyDhSJoBv4sHwagyyKBGdmhJwAFeczAASaWLNwMzq92aHYM
bEklHY0dENKcOCBvWR2bb+lzieYRx1ASNCdvrJM2Jk77mq+bcBiEYNtBqyVD4zWe
G/bjLY6Rm7geTXHkilWQVADqcwBkkDV7nNIWWLWRl6kP5t0fg/sBVrlyRxjESxwR
nXuBLbS6KaA=
=pCRh
-END PGP SIGNATURE End Message ---

Bug#904133: in telegram-destkop marked as pending

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #904133 in telegram-destkop reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian/telegram-desktop/commit/53e93da1bb352eb25457afe9dc16336587cdacd7


Disable LTO at all

 * Unfortunately, this mode results to many FTBFS on 32-bit machines.
 * Nevertheless, on amd64 it reduces size of resulting binary by 22%.
 * Now less debug info is generated only for Release builds.

Closes: #904133



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904133

Bug#904133: marked as done (telegram-desktop: FTBFS with memory exhaustion on many targets)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 12:49:15 +
with message-id 
and subject line Bug#904133: fixed in telegram-desktop 1.3.10-2
has caused the Debian Bug report #904133,
regarding telegram-desktop: FTBFS with memory exhaustion on many targets
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.)


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

the package ftbfs at least on armel, and mips* in Debian, it fails on Ubuntu
almost everywhere due to more memory limited buildds.

  https://launchpad.net/ubuntu/+source/telegram-desktop/1.3.10-1

Did you make any measurements how much better the code is with -flto?  I'm
unsure if it's worth the trouble for a desktop application.
--- End Message ---
--- Begin Message ---
Source: telegram-desktop
Source-Version: 1.3.10-2

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

Debian distribution maintenance software
pp.
Nicholas Guriev  (supplier of updated telegram-desktop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Aug 2018 22:10:59 +0300
Source: telegram-desktop
Binary: telegram-desktop
Architecture: source
Version: 1.3.10-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev 
Changed-By: Nicholas Guriev 
Description:
 telegram-desktop - official telegram messaging app
Closes: 904133
Changes:
 telegram-desktop (1.3.10-2) unstable; urgency=medium
 .
   * Fix FTBFS on mips, mipsel, armel with libatomic.
   * Disable LTO at all (closes: #904133).
   * Bump standards version, no needed changes.
Checksums-Sha1:
 39a62b93496fa2f8959a62f235581a92aa3ce74e 2423 telegram-desktop_1.3.10-2.dsc
 b3ae957dcc0ba5224716aa36c36ab288b51f19bc 31948 
telegram-desktop_1.3.10-2.debian.tar.xz
 02876789658a622b7e1fa720186b67cd5d701587 18382 
telegram-desktop_1.3.10-2_amd64.buildinfo
Checksums-Sha256:
 dd336f99662f8c98d69efb08d88534424b8af39e9c5d8948377bfce8f703cc0e 2423 
telegram-desktop_1.3.10-2.dsc
 14b769391f9724520c18709109a9f9daeb29fd0c5b6d4f535d46577b806446eb 31948 
telegram-desktop_1.3.10-2.debian.tar.xz
 4318937d55e19235d1725bce9d3d5900a400887068f06f0b9d5a1c676ba09d81 18382 
telegram-desktop_1.3.10-2_amd64.buildinfo
Files:
 35f130b99a4920dd166c566481e96741 2423 net optional 
telegram-desktop_1.3.10-2.dsc
 0999e91738cfdb203afa598a7919a5b9 31948 net optional 
telegram-desktop_1.3.10-2.debian.tar.xz
 f86cbaded63dec1915137a25d0c5a9ae 18382 net optional 
telegram-desktop_1.3.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAltlnpkACgkQCBa54Yx2
K62/1Q/+Omv0PCBOwmsOyRcDJGIiGu++etdzucRYxM7LdS2SJ2axISMqus6gKvTK
i1ah0mGstOZg2+lDwKCXfkmUQD9t+RT1nwU4pVK4pYYfx8WMW6itjQwBn4nsAttY
zQoaBQHyZo6QRpFIlFibSZjpN25ELYsySxNBEVuwIZxP/+E6XBU+4RfMIsyAP6Xn
6Yh8e5GkXDvelYxFA+wVutqxc6XsigrzJjB0Hp8BP6q7goA20KO/Ti4o9jWKasAP
EIzIaANinozLL/T7ls7nKnT7HrjYAIQXbYA+hb4rwJU1YYvaF+fuyg7QlgLl3cng
rfBHPeh45o7vibB0xf8iz3A51iNCGi/mvpZTywLMXxNQmJvF+bO6v6r3gUJYfhjL
WZdGbOnIO+WXZzJ1xKfCugBbMrjRAmN8fabJkOD4W5Wd1u+2CjobEB8JCmvtZfKb
ixVtqV5Z3dB7mP+ZLqt9uBmeSvcxw/aVbWZ3Ulbt+PuLvjoa/8T9sJmZ+HBMLGga
mCBkN1mldgyO/ycziZkQAIyX/219ZzDGC4y8g53244fM5Et7UmcPjVNx6Sqax0to
f9ZcYy/1dmgNgecKEIDMu4jWKE99BKDhPJrpFqRNMKoEVBasFlKSW9yh3cSfUH2M
wCPMMYwTZWPNuG1GfHGIh850JIlqJe34Y+I/k0I00+YXc8oGo0w=
=R1aQ
-END PGP SIGNATURE End Message ---

Processed: Bug#904133 in telegram-destkop marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904133 {Done: Nicholas Guriev } [src:telegram-desktop] 
telegram-desktop: FTBFS with memory exhaustion on many targets
Added tag(s) pending.

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

Bug#905283: marked as done (r-cran-crosstalk: broken symlink: /usr/lib/R/site-library/crosstalk/lib/strftime/strftime-min.js -> ../../../shiny/www/shared/strftime/strftime-min.js)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 12:35:42 +
with message-id 
and subject line Bug#905283: fixed in r-cran-crosstalk 1.0.0+dfsg-3
has caused the Debian Bug report #905283,
regarding r-cran-crosstalk: broken symlink: 
/usr/lib/R/site-library/crosstalk/lib/strftime/strftime-min.js -> 
../../../shiny/www/shared/strftime/strftime-min.js
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.)


-- 
905283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-crosstalk
Version: 1.0.0+dfsg-2
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...):

1m18.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/R/site-library/crosstalk/lib/strftime/strftime-min.js -> 
../../../shiny/www/shared/strftime/strftime-min.js

   ^

r-cran-shiny now ships
/usr/lib/R/site-library/shiny/www/shared/strftime/strftime.min.js
  ^


cheers,

Andreas


r-cran-crosstalk_1.0.0+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: r-cran-crosstalk
Source-Version: 1.0.0+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-crosstalk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Aug 2018 12:15:22 +0200
Source: r-cran-crosstalk
Binary: r-cran-crosstalk
Architecture: source
Version: 1.0.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Description:
 r-cran-crosstalk - GNU R inter-widget interactivity for HTML widgets
Closes: 905283
Changes:
 r-cran-crosstalk (1.0.0+dfsg-3) unstable; urgency=medium
 .
   * Fix symlink
 Closes: #905283
   * Standards-Version: 4.2.0
Checksums-Sha1:
 a321c95f9a5257a49a8bfc38a775f323b254179b 2197 r-cran-crosstalk_1.0.0+dfsg-3.dsc
 32a75241793650e8a98caf99330c78056d9c95d4 2620 
r-cran-crosstalk_1.0.0+dfsg-3.debian.tar.xz
Checksums-Sha256:
 41075cede0e50933b2bc073b8d9742aaba79b40dd4b1df3b17fb8180c4e341b3 2197 
r-cran-crosstalk_1.0.0+dfsg-3.dsc
 23f1321157b1c5f648f243b0d6c92bc7314a18c3d4badf27b23c7a70bcc6c652 2620 
r-cran-crosstalk_1.0.0+dfsg-3.debian.tar.xz
Files:
 387e48c055c053702e77bb5919bdcc5e 2197 gnu-r optional 
r-cran-crosstalk_1.0.0+dfsg-3.dsc
 7d39b4e5851658d223a017adec5f58ae 2620 gnu-r optional 
r-cran-crosstalk_1.0.0+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltlmEURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG9Rw//dF5JX8oBF3e08XZ223P0HfMA5AoP2wUr
ZMivooAtD6l+f4wah7TX7vuQ8wkiq/YiYHQ+SgIh2vqkOR2yHBxv6o7vG52ZWWU0
IgtxUFs8bAzg7ycFTI4EAd1J+HNCHFfm1yfXSVifgXIAyTOseDBAIWb5+S6MNgL0
SfoPfxI/xTA3JDoaI5+lhSVJGoEYwQbPdPdIkMOtOBIhOucX0OqpsV27PW88gaj2
8C7sRdHxzXu2xQivfrT6IgXsJ1g4kumsByHg0B7x8yDgWJqu8qxWeIsjIVwAgZ6Q
Cqyy6iQjPGvoQ4LKYrBn8B703pJ68K5KHDs//rQn9XuA5/EM3Mnu3j9C3YKZa1Qz
b+jMxw88gpwzH8Tc9Ess9wkNiIhfqjU1i5+iwXlm4e/ZPy1yANSu33zTTSGSNDmA
AXpD4qjHgDAmgQL0hzAx03wyuSWGdOGnHUQOjzr5ZoXPDrgPbWr0ARsSoYbLAUQU
MLe8TPR+h+eKesiWwebUobSDLdDH6Mga9vaTt1F+AilS2ks0bkMDwKctMzDCxqe+
mXv9GMYaTG2RXf0SB8+9xILN/pR4EW47qgCez18ANZrN+IlDOkdZmbK3F8I/x/UK
7B7q4ivCQcPxGiMLyMGyRhV6pOJAWKRLdFlpwy14f9jofhLupDvmkK7ExmkIfqnw
fJR909+0muk=
=xY4F
-END PGP SIGNATURE End Message ---

Processed: pulseaudio broken by timidity

[Debian Bug Tracking System]

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

> reassign 904652 timidity 2.14.0-2
Bug #904652 [pulseaudio] pulseaudio: looses device and replace it with dummy 
package so no sound possible
Bug reassigned from package 'pulseaudio' to 'timidity'.
No longer marked as found in versions pulseaudio/11.1-5 and pulseaudio/12.0-1.
Ignoring request to alter fixed versions of bug #904652 to the same values 
previously set
Bug #904652 [timidity] pulseaudio: looses device and replace it with dummy 
package so no sound possible
Marked as found in versions timidity/2.14.0-2.
> forcemerge 901148 904652
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Added tag(s) upstream.
Added tag(s) upstream.
Bug #904652 [timidity] pulseaudio: looses device and replace it with dummy 
package so no sound possible
Severity set to 'critical' from 'grave'
Marked as found in versions timidity/2.14.0-3 and timidity/2.14.0-8.
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Merged 901148 902330 904652
> affects 904652 + pulseaudio
Bug #904652 [timidity] pulseaudio: looses device and replace it with dummy 
package so no sound possible
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Added indication that 904652 affects pulseaudio
Added indication that 901148 affects pulseaudio
Added indication that 902330 affects pulseaudio
> thanks
Stopping processing here.

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

Processed: tagging 896582

[Debian Bug Tracking System]

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

> # Noise change to reset auto-rm counter
> tags 896582 + pending
Bug #896582 {Done: Rob Browning } [src:guile-2.2] 
guile-2.2 FTBFS with glibc 2.27
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 891593 in 0.4.1+ds1-1, severity of 905413 is serious, user debian...@lists.debian.org ...

[Debian Bug Tracking System]

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

> found 891593 0.4.1+ds1-1
Bug #891593 [python-fpylll-doc] python-fpylll-doc: broken symlink: 
/usr/share/doc/python-fpylll-doc/tests -> examples/tests
Marked as found in versions fpylll/0.4.1+ds1-1.
> severity 905413 serious
Bug #905413 [libgamemode0-dev] libgamemode0-dev: missing Depends: libgamemode0 
(= ${binary:Version})
Severity set to 'serious' from 'normal'
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 887344 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> thanks
Stopping processing here.

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

Bug#905421: kea-common: fails to remove: dpkg-statoverride: error: unknown option --remote

[Andreas Beckmann]

Package: kea-common
Version: 1.4.0.P1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Purging configuration files for kea-common (1.4.0.P1-3) ...
  dpkg-statoverride: error: unknown option --remote
  
  Use --help for help about overriding file stat information.
  dpkg: error processing package kea-common (--purge):
   installed kea-common package post-removal script subprocess returned error 
exit status 2
  Errors were encountered while processing:
   kea-common


cheers,

Andreas


kea-common_1.4.0.P1-3.log.gz
Description: application/gzip

Bug#905418: elpa ftbfs on at least armel, mips64el, ppc64el

[Matthias Klose]

Package: src:elpa
Version: 2016.05.001-6
Severity: serious
Tags: sid buster

elpa ftbfs on at least armel, mips64el, ppc64el, where it built before:

[...]
echo 'mpiexec -n 2 --oversubscribe ./elpa2_test_complex_choose_kernel_with_api
$TEST_FLAGS' > elpa2_test_complex_choose_kernel_with_api.sh
chmod +x elpa2_test_complex_choose_kernel_with_api.sh
make[4]: 'elpa2_print_kernels' is up to date.
echo 'mpiexec -n 2 --oversubscribe ./elpa1_test_real_c_version $TEST_FLAGS' >
elpa1_test_real_c_version.sh
chmod +x elpa1_test_real_c_version.sh
echo 'mpiexec -n 2 --oversubscribe ./elpa1_test_complex_c_version $TEST_FLAGS' >
elpa1_test_complex_c_version.sh
chmod +x elpa1_test_complex_c_version.sh
echo 'mpiexec -n 2 --oversubscribe ./elpa2_test_real_c_version $TEST_FLAGS' >
elpa2_test_real_c_version.sh
chmod +x elpa2_test_real_c_version.sh
echo 'mpiexec -n 2 --oversubscribe ./elpa2_test_complex_c_version $TEST_FLAGS' >
elpa2_test_complex_c_version.sh
chmod +x elpa2_test_complex_c_version.sh
make[4]: Leaving directory '/<>'
/usr/bin/make  check-TESTS
make[4]: Entering directory '/<>'
make[5]: Entering directory '/<>'

Bug#899606: marked as done (madplay: Invalid maintainer address pkg-mad-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 11:19:14 +
with message-id 
and subject line Bug#899606: fixed in madplay 0.15.2b-8.3
has caused the Debian Bug report #899606,
regarding madplay: Invalid maintainer address 
pkg-mad-maintain...@lists.alioth.debian.org
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.)


-- 
899606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:madplay
Version: 0.15.2b-8.2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of madplay,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package madplay since the list address
pkg-mad-maintain...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-mad-maintain...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: madplay
Source-Version: 0.15.2b-8.3

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated madplay 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: Fri, 03 Aug 2018 20:42:59 +0200
Source: madplay
Binary: madplay
Architecture: source
Version: 0.15.2b-8.3
Distribution: unstable
Urgency: medium
Maintainer: Mad Maintainers 
Changed-By: Paul Gevers 
Description:
 madplay- MPEG audio player in fixed point
Closes: 899606
Changes:
 madplay (0.15.2b-8.3) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Set maintainer field to madp...@packages.debian.org to have a valid
 address (Closes: #899606)
Checksums-Sha1:
 c894f4e91c96c11afaf38db8f2e20c5264c6a203 1695 madplay_0.15.2b-8.3.dsc
 be1b7d1c65ae3162725667723f5cf579f08ae76a 6885 madplay_0.15.2b-8.3.diff.gz
Checksums-Sha256:
 ceadb1bfedac860b81a2a67c86b8255d65445572646171474c248cc9889d1c9c 1695 
madplay_0.15.2b-8.3.dsc
 51f7ac817cf8800e7b024c68b043e63de01f7810777bb4ac44b21cc331a1dae3 6885 
madplay_0.15.2b-8.3.diff.gz
Files:
 0a1fd39849466ce49ce5be224297bf66 1695 sound optional madplay_0.15.2b-8.3.dsc
 4fd97729b88ef467f4b359b8de25759d 6885 sound optional 
madplay_0.15.2b-8.3.diff.gz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAltlh3QACgkQnFyZ6wW9
dQp9igf/TNEcLHblaie+Sge/xCDOnOz5iPVqQ5v1lcz+meiqObD3CBPfqIeymU3O
fv8sGKKlmrB7od1EmsMCellPcHVaESnU7FmoEoACX1a4eJDxQyorCr7YVnk5u6i2
Jzm9MnIrJILNltLP2Jmo+m

Bug#905382: cgit: diff for NMU version 1.1+git2.10.2-3.1

[Salvatore Bonaccorso]

Control: tags 905382 + pending


Dear maintainer, hi Peter, hi Alexander

I've prepared an NMU for cgit (versioned as 1.1+git2.10.2-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

I choosed delayed/10 since I'm not strictly follwoing the advice and
good practice on NMUs, as the bug was just from yesterday, and
defintively not enough time for maintainer to react. I have repared an
update for stretch-security for the issue and wanted to avoid the
discrepancy to buster/sid. I will cancel the NMU if you diagree with
my approach on straight doing a NMU.

Regards
Salvatore
diff -Nru cgit-1.1+git2.10.2/debian/changelog cgit-1.1+git2.10.2/debian/changelog
--- cgit-1.1+git2.10.2/debian/changelog	2017-01-06 06:08:21.0 +0100
+++ cgit-1.1+git2.10.2/debian/changelog	2018-08-04 12:27:48.0 +0200
@@ -1,3 +1,10 @@
+cgit (1.1+git2.10.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * clone: fix directory traversal (CVE-2018-14912) (Closes: #905382)
+
+ -- Salvatore Bonaccorso   Sat, 04 Aug 2018 12:27:48 +0200
+
 cgit (1.1+git2.10.2-3) unstable; urgency=medium
 
   * Build-depend on asciidoc-base | asciidoc.
diff -Nru cgit-1.1+git2.10.2/debian/patches/clone-fix-directory-traversal.patch cgit-1.1+git2.10.2/debian/patches/clone-fix-directory-traversal.patch
--- cgit-1.1+git2.10.2/debian/patches/clone-fix-directory-traversal.patch	1970-01-01 01:00:00.0 +0100
+++ cgit-1.1+git2.10.2/debian/patches/clone-fix-directory-traversal.patch	2018-08-04 12:26:43.0 +0200
@@ -0,0 +1,65 @@
+From: "Jason A. Donenfeld" 
+Date: Fri, 3 Aug 2018 15:46:11 +0200
+Subject: clone: fix directory traversal
+Origin: https://git.zx2c4.com/cgit/commit/?id=53efaf30b50f095cad8c160488c74bba3e3b2680
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-14912
+Bug-Debian: https://bugs.debian.org/905382
+Bug: https://bugs.chromium.org/p/project-zero/issues/detail?id=1627
+
+This was introduced in the initial version of this code, way back when
+in 2008.
+
+$ curl http://127.0.0.1/cgit/repo/objects/?path=../../../../../../../../../etc/passwd
+root:x:0:0:root:/root:/bin/sh
+...
+
+Signed-off-by: Jason A. Donenfeld 
+Reported-by: Jann Horn 
+---
+ ui-clone.c | 23 +++
+ 1 file changed, 19 insertions(+), 4 deletions(-)
+
+diff --git a/ui-clone.c b/ui-clone.c
+index 2c1ac3d..6ba8f36 100644
+--- a/ui-clone.c
 b/ui-clone.c
+@@ -92,17 +92,32 @@ void cgit_clone_info(void)
+ 
+ void cgit_clone_objects(void)
+ {
+-	if (!ctx.qry.path) {
+-		cgit_print_error_page(400, "Bad request", "Bad request");
+-		return;
+-	}
++	char *p;
++
++	if (!ctx.qry.path)
++		goto err;
+ 
+ 	if (!strcmp(ctx.qry.path, "info/packs")) {
+ 		print_pack_info();
+ 		return;
+ 	}
+ 
++	/* Avoid directory traversal by forbidding "..", but also work around
++	 * other funny business by just specifying a fairly strict format. For
++	 * example, now we don't have to stress out about the Cygwin port.
++	 */
++	for (p = ctx.qry.path; *p; ++p) {
++		if (*p == '.' && *(p + 1) == '.')
++			goto err;
++		if (!isalnum(*p) && *p != '/' && *p != '.' && *p != '-')
++			goto err;
++	}
++
+ 	send_file(git_path("objects/%s", ctx.qry.path));
++	return;
++
++err:
++	cgit_print_error_page(400, "Bad request", "Bad request");
+ }
+ 
+ void cgit_clone_head(void)
+-- 
+2.18.0
+
diff -Nru cgit-1.1+git2.10.2/debian/patches/series cgit-1.1+git2.10.2/debian/patches/series
--- cgit-1.1+git2.10.2/debian/patches/series	2016-11-25 22:02:50.0 +0100
+++ cgit-1.1+git2.10.2/debian/patches/series	2018-08-04 12:26:56.0 +0200
@@ -10,3 +10,4 @@
 syntax-highlighting.patch
 fix-crash-when-using-path-limit.patch
 link-with-ldl-on-gnu-hurd.patch
+clone-fix-directory-traversal.patch

Processed: cgit: diff for NMU version 1.1+git2.10.2-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 905382 + pending
Bug #905382 [src:cgit] cgit: CVE-2018-14912: directory traversal vulnerability
Added tag(s) pending.

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

Bug#905417: ants: broken symlink: /usr/bin/jointfusion -> ../lib/ants/jointfusion

[Andreas Beckmann]

Package: ants
Version: 2.2.0-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...):

0m46.5s ERROR: FAIL: Broken symlinks:
  /usr/bin/jointfusion -> ../lib/ants/jointfusion


ants/experimental does no longer ship /usr/lib/ants/jointfusion


cheers,

Andreas


ants_2.2.0-1+b2.log.gz
Description: application/gzip

Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.1

[Anton Gladky]

Dear Adrian,

thank you for the patch! I actually also started to fix
the issue, but still not finished. Please feel free to move
the upload to DELAYED/0. Also it would be good if you push
your changes into the git-repo.

Thanks

Anton


2018-08-04 10:26 GMT+02:00 Adrian Bunk :
> Control: tags 897826 + patch
> Control: tags 897826 + pending
> Control: tags 897826 + ftbfs
>
> Dear maintainer,
>
> I've prepared an NMU for openfoam (versioned as 4.1+dfsg1-2.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
>
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#905415: libnode64-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/uv*.h -> ../../../../uv*.h

[Andreas Beckmann]

Package: libnode64-dev
Version: 10.4.0~dfsg-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...):

0m32.4s ERROR: FAIL: Broken symlinks:
  /usr/include/nodejs/deps/uv/include/uv.h -> ../../../../uv.h
  /usr/include/nodejs/deps/uv/include/uv-version.h -> ../../../../uv-version.h
  /usr/include/nodejs/deps/uv/include/uv-unix.h -> ../../../../uv-unix.h
  /usr/include/nodejs/deps/uv/include/uv-threadpool.h -> 
../../../../uv-threadpool.h
  /usr/include/nodejs/deps/uv/include/uv-linux.h -> ../../../../uv-linux.h
  /usr/include/nodejs/deps/uv/include/uv-errno.h -> ../../../../uv-errno.h


Is libnode64-dev missing a Depends: libuv1-dev ?


cheers,

Andreas


libnode64-dev_10.4.0~dfsg-1.log.gz
Description: application/gzip

Bug#905414: libosmo-sccp-dev: missing Depends: libosmomtp0 (= ${binary:Version})

[Andreas Beckmann]

Package: libosmo-sccp-dev
Version: 0.9.0-2
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...):

0m31.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libosmomtp.so -> libosmomtp.so.0.0.0


cheers,

Andreas


libosmo-sccp-dev_0.9.0-2.log.gz
Description: application/gzip

Bug#889878: marked as done (hkl FTBFS on amd64/arm64/ppc64el/s390x: sirius segfaults)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 10:33:55 +
with message-id 
and subject line Bug#889878: fixed in hkl 5.0.0.2449-2
has caused the Debian Bug report #889878,
regarding hkl FTBFS on amd64/arm64/ppc64el/s390x: sirius segfaults
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.)


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

https://buildd.debian.org/status/package.php?p=hkl&suite=sid

...
make[4]: Entering directory '/<>/Documentation/figures'
gcc -DHAVE_CONFIG_H -I. -I../..  -Wextra -D_DEFAULT_SOURCE -I../.. -I../../hkl 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o sirius.o sirius.c
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security 
-Wl,--whole-archive,../../hkl/.libs/libhkl.a,--no-whole-archive -Wl,-z,relro 
-Wl,--as-needed -o sirius sirius.o ../../hkl/libhkl.la 
../../hkl/api2/libhkl2.la -lglib-2.0 -lgobject-2.0 -lglib-2.0 
-L/usr/lib/x86_64-linux-gnu -lgsl -lgslcblas -lm -lyaml 
libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,--whole-archive 
-Wl,../../hkl/.libs/libhkl.a -Wl,--no-whole-archive -Wl,-z -Wl,relro 
-Wl,--as-needed -o .libs/sirius sirius.o  ../../hkl/.libs/libhkl.so 
../../hkl/api2/.libs/libhkl2.a -lgobject-2.0 -lglib-2.0 
-L/usr/lib/x86_64-linux-gnu -lgsl -lgslcblas -lm -lyaml
cd . && ./sirius
Makefile:728: recipe for target 'sirius-stamp' failed
make[4]: *** [sirius-stamp] Segmentation fault


Backtrace:

#0  generator_argp_ (ret=0xcdaab730) at ../../hkl/ccan/generator/generator.h:44
#1  trajectory_gen_generator__ (ret=0xcdaab730) at hkl2.c:246
#2  0x7f3078908d70 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x in ?? ()
--- End Message ---
--- Begin Message ---
Source: hkl
Source-Version: 5.0.0.2449-2

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated hkl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 10:42:33 +0200
Source: hkl
Binary: ghkl libhkl5 libhkl-dev libhkl-dbg libhkl-doc gir1.2-hkl-5.0
Architecture: source
Version: 5.0.0.2449-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 ghkl   - diffractometer computation control application
 gir1.2-hkl-5.0 - diffractometer computation control library - gir binding
 libhkl-dbg - diffractometer computation control library - debug symbols
 libhkl-dev - diffractometer computation control library - development files
 libhkl-doc - diffractometer computation control library - documentation
 libhkl5- diffractometer computation control library
Closes: 889878
Changes:
 hkl (5.0.0.2449-2) unstable; urgency=medium
 .
   * fix for real (Closes: #889878) and a big thanks to
 Bernhard Übelacker for his investigations
   * d/patches
 - make-test-for-pointer-safe-makecontext-succeed (added)
Checksums-Sha1:
 05391e9d0b8f962f2281bbfa8df0dd3d08cd1bcd 2709 hkl_5.0.0.2449-2.dsc
 3048764bad2a92a1cc5ece21b196c1c00236f20e 9632 hkl_5.0.0.2449-2.debian.tar.xz
Checksums-Sha256:
 37fe08e3c8286fdc8d5c915274fb7d8abefff7e1868300c73654cfc171499e11 2709 
hkl_5.0.0.2449-2.dsc
 85453b53f09a099b66787dbd98b0c258b80caa70f259c4deabe33a3c9a627541 9632 
hkl_5.0.0.2449-2.debian.tar.xz
Files:
 6d2d74f59abd391bda6a1d56ed8d7d26 2709 science optional hkl_5.0.0.2449-2.dsc
 1a9930e0fe57cc54b049437840f7d20c 9632 science optional 
hkl_5.0.0.2449-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAltlfBMRHHBpY2NhQG

Processed (with 1 error): Re: Bug#848603: Enable innodb_large_prefix

[Debian Bug Tracking System]

Processing control commands:

> merge -1 886756
Bug #848603 [mariadb-server] Enable innodb_large_prefix
Unable to merge bugs because:
forwarded of #886756 is 'https://jira.mariadb.org/browse/MDEV-14904' not ''
severity of #886756 is 'serious' not 'normal'
blocks of #886756 is '891691' not ''
package of #886756 is 'mariadb-server-10.1' not 'mariadb-server'
Failed to merge 848603: Did not alter merged bugs.


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

Bug#871563: manpages-fr-extra: French translation of diff(1) is outdated

[Colomban Wendling]

Package: manpages-fr-extra
Version: 20151231
Followup-For: Bug #871563

I agree, I just wanted to check a diff(1) option, and it wasn't listed
in the manpage, leading me to assume diff(1) didn't have it.  Next, a
search on the Internet showed that diff(1) did indeed have this option,
making me wonder whether Debian's diff(1) was different.  `diff --help`
showed it was just the manpage, so did a subsequent `man -LC diff`.

This is confusing and counter-productive for the user.  Please either
update this package to provide accurate translations, or drop it to
force accurate English on users instead of allowing inaccurate French.

Regards,
Colomban


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

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

manpages-fr-extra depends on no packages.

Versions of packages manpages-fr-extra recommends:
ii  manpages-fr  3.65d1p1-1

Versions of packages manpages-fr-extra suggests:
ii  man-db [man-browser]  2.7.6.1-2
pn  manpages-fr-dev   

-- no debconf information

Processed: [r...@debian.org: Bug#905408: libreoffice: missed radiobuttons and checkbox in forms]

[Debian Bug Tracking System]

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

> notfound 905408 3a6.1.0~rc2-3
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms with gen VCLplug
The source 'libreoffice' and version '3a6.1.0~rc2-3' do not appear to match any 
binary packages
No longer marked as found in versions libreoffice/3a6.1.0~rc2-3.
> thanks
Stopping processing here.

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

Processed: [r...@debian.org: Re: Bug#905408: libreoffice: missed radiobuttons and checkbox in forms]

[Debian Bug Tracking System]

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

> retitle 905408 libreoffice: missed radiobuttons and checkbox in forms with 
> gen VCLplug
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms
Changed Bug title to 'libreoffice: missed radiobuttons and checkbox in forms 
with gen VCLplug' from 'libreoffice: missed radiobuttons and checkbox in forms'.
> thanks
Stopping processing here.

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

Bug#905408: libreoffice: missed radiobuttons and checkbox in forms

[Rene Engelhard]

found 905408 1:6.1.0~rc2-3
retitle 905408 libreoffice: missed radiobuttons and checkbox in forms
with gen VCLplug
thanks

On Sat, Aug 04, 2018 at 08:46:12AM +0200, Kamil Jonca wrote:
> Source: libreoffice
> Version: 3a6.1.0~rc2-3

Please a bit more care, this isn't a valid version.

> I found that in my database forms, at version 6.1 libreoffice, all checkboxes 
> and radiobuttons are missing. 
> Only their labels exist, but no field to enter/check value. 
> Simplest way to observe it is to run: 
> soffice -base
> and try to choose 'open existing database file'

Confirmed. :-(

Only happens on "gen" VCLplug.. - aka without any gtk(2/3) or kde
integration.

Regards,

Rene

Bug#853336: marked as done (bomberclone: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 09:03:53 +
with message-id 
and subject line Bug#853336: fixed in bomberclone 0.11.9-7.1
has caused the Debian Bug report #853336,
regarding bomberclone: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
Making all in tricked
make[6]: Entering directory '/<>/data/tileset/tricked'
make[6]: Nothing to be done for 'all'.
make[6]: Leaving directory '/<>/data/tileset/tricked'
Making all in zbb_frog
make[6]: Entering directory '/<>/data/tileset/zbb_frog'
make[6]: Nothing to be done for 'all'.
make[6]: Leaving directory '/<>/data/tileset/zbb_frog'
make[6]: Entering directory '/<>/data/tileset'
make[6]: Nothing to be done for 'all-am'.
make[6]: Leaving directory '/<>/data/tileset'
make[5]: Leaving directory '/<>/data/tileset'
make[5]: Entering directory '/<>/data'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/<>/data'
make[4]: Leaving directory '/<>/data'
Making all in include
make[4]: Entering directory '/<>/include'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/include'
Making all in src
make[4]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I.. -I../include  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -ggdb -O0 -Wall -Werror -c -o main.o main.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -ggdb -O0 -Wall -Werror -c -o bomb.o bomb.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -ggdb -O0 -Wall -Werror -c -o debug.o debug.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -ggdb -O0 -Wall -Werror -c -o packets.o packets.c
packets.c: In function 'send_mapinfo':
packets.c:1603:44: error: writing a terminating nul past the end of the 
destination [-Werror=format-overflow=]
 sprintf (map_pkg.bomb_tickingtime, "%4f", bman.bomb_tickingtime);
 ~~~^
packets.c:1603:5: note: format output between 9 and 318 bytes into a 
destination of size 8
 sprintf (map_pkg.bomb_tickingtime, "%4f", bman.bomb_tickingtime);
 ^~~~
cc1: all warnings being treated as errors
Makefile:473: recipe for target 'packets.o' failed
make[4]: *** [packets.o] Error 1
make[4]: Leaving directory '/<>/src'
Makefile:448: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:368: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:15: recip

Processed (with 1 error): Re: Bug#905408: libreoffice: missed radiobuttons and checkbox in forms

[Debian Bug Tracking System]

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

> found 905408 1:6.1.0~rc2-3
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms
Marked as found in versions libreoffice/1:6.1.0~rc2-3.
> retitle 905408 libreoffice: missed radiobuttons and checkbox in forms
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms
Ignoring request to change the title of bug#905408 to the same title
> with gen VCLplug
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: Enough broken systems to justify RC

[Debian Bug Tracking System]

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

> severity 900550 serious
Bug #900550 [xserver-xorg-core] xserver-xorg-core: X server segfaults for 
xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Bug #903708 [xserver-xorg-core] xfce4: xfce fails to start with all methods
Bug #904715 [xserver-xorg-core] startxfce4 fails
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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