Bug#881483: marked as done (libsavitar: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2017 03:11:45 +
with message-id 
and subject line Bug#881483: fixed in libsavitar 3.0.3-3
has caused the Debian Bug report #881483,
regarding libsavitar: 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.)


-- 
881483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsavitar
Version: 3.0.3-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Petter Reinholdtsen 

Hi,

I just ACCEPTed libsavitar from NEW but noticed it was missing 
attribution in debian/copyright for at least Kristen Wegner
for pugixml.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: libsavitar
Source-Version: 3.0.3-3

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated libsavitar 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: Tue, 21 Nov 2017 02:25:24 +
Source: libsavitar
Binary: libsavitar0 libsavitar-dev python3-savitar
Architecture: source
Version: 3.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Petter Reinholdtsen 
Description:
 libsavitar-dev - 3MF file handling library (development files)
 libsavitar0 - 3MF file handling library (shared library)
 python3-savitar - 3MF file handling library (Python bindings)
Closes: 881483 881493
Changes:
 libsavitar (3.0.3-3) unstable; urgency=medium
 .
   [ Gregor Riepl ]
   * Fixed incorrect quoting in symbols file (Closes: #881493).
   * Some copyright file corrections (Closes: #881483).
Checksums-Sha1:
 4421fda6811f1ebf930a83d6618d5363672980e0 2181 libsavitar_3.0.3-3.dsc
 5f9632489dd656c6d31bcc6320986c8ce7ac32d8 9064 libsavitar_3.0.3-3.debian.tar.xz
 58541876450241d29e06e55d005099845fbc4c94 7867 
libsavitar_3.0.3-3_source.buildinfo
Checksums-Sha256:
 8d9fc725f58cea7d539332ea8eb93b08bbd17a7b63fdb7fe7618b260e349fddc 2181 
libsavitar_3.0.3-3.dsc
 d0fb3f62f904d0c3a73656d1b55f14f95245da252032647117593f68e7d11e4e 9064 
libsavitar_3.0.3-3.debian.tar.xz
 8f50792f06267e41a48bcb7b654337be902d0468ed2edf1869f9605a9bd881a7 7867 
libsavitar_3.0.3-3_source.buildinfo
Files:
 e83c1e6dccceeaa2873d46b59107301f 2181 libs optional libsavitar_3.0.3-3.dsc
 063bf9ff63659e714549246ca72a9216 9064 libs optional 
libsavitar_3.0.3-3.debian.tar.xz
 75cbe3404b534b04d102599b55dbba33 7867 libs optional 
libsavitar_3.0.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAloTj7UACgkQgSgKoIe6
+w7iBhAAvx8c7zqaw+gwWWXqbel8+wdRJTPjmz+BdSjAMRY6pfIhun5aiXS+x/J8
zxEqlspHxX143ImD3ICYIuxuZoZ7uQ/1mSvuPI/m/kdeQb4CCAJKEkirrzMsAMNX
d7aeQh/Tj+E4c4oCGJO8zhfcOtnlOCJ1JCkaWQDUWwxnxjkyLb4IZXIvJ9Iy62lO
CHLAipIm0kw3EtThDUa4UBcDHHeICyHyAMmnwSsClcvuxMviFAZ0P18bBswpeNye
ZXI4kwDOhPK8DQthMsIOq+E2w/prVbWP1YinmR09JYqvJC9CdLmKUbY1EEOHY872
Bz/Yek/rnAYt2J24cn/hx6bCzyxWUf/nrtaH2FAMKwXUO8G0h7JdHA/omD4FBp3Y
s1LrjxJ+z4FhoFbGIWYwH7Dkb4x0uUA6a8ERBQeleYRU+asVMueEw8ASjqm6zAfn
u7u0CINWcEDrWGMH+cJz3fQgwdlhGipI1cw0Cv4z06rr6lgYna2SZ0fKVVH1WG73
jZjXAo9gRqhMlpQwvYwCWowbj+i82/FPUPoksVyCj3RUkVfkkjiTnGh//ogXsbFG
6qKLYjPnE3mLm3IAUyoDgg1HOKlOrFnAeoWrxVibx++jjODc0TLiWGWVQPFC6Nw3
EiMgcv2OH0Sg76wYE4NmNqR+p6YC0Ei4TLhXOAHs5NXVlz6/0dc=
=wo3i
-END PGP SIGNATURE End Message ---

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Tue, 21 Nov 2017, Aurelien Jarno wrote:

> On 2017-11-21 01:01, Mikulas Patocka wrote:
> > 
> > 
> > On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> > 
> > > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > > > 
> > > > 
> > > > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > > > 
> > > > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > > > Package: libc6-amd64
> > > > > > Version: 2.25-1
> > > > > > Severity: critical
> > > > > > Justification: breaks the whole system
> > > > > > 
> > > > > > Dear Maintainer,
> > > > > > 
> > > > > > *** Reporter, please consider answering these questions, where 
> > > > > > appropriate ***
> > > > > > 
> > > > > >* What led up to the situation?
> > > > > > 
> > > > > > I have a x86-64 system with i386 and x32 foreign architectures 
> > > > > > (because I
> > > > > > need to develop software for i386 and x32 architectures).
> > > > > > 
> > > > > >* What exactly did you do (or not do) that was effective (or
> > > > > >  ineffective)?
> > > > > > 
> > > > > > I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> > > > > > 
> > > > > >* What was the outcome of this action?
> > > > > > 
> > > > > > Halfway through apt upgrade it failed and I ended up with unusable 
> > > > > > system where
> > > > > > large number of binaries were segfauting on startup without doign 
> > > > > > anything.
> > > > > > 
> > > > > >* What outcome did you expect instead?
> > > > > > 
> > > > > > The upgrade to libc-2.25 should work.
> > > > > > 
> > > > > > 
> > > > > > The reason for the catastrophic failure is this:
> > > > > > 
> > > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > > 
> > > > > I guess you mean you have installed one of the two, not both.
> > > > > 
> > > > > > x86-64 libc in /lib64/). This package is not technically needed 
> > > > > > (because
> > > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it 
> > > > > > is
> > > > > > installed nonetheless because of some dependencies.
> > > > > 
> > > > > Just to be clear, as said in my other email, this *is* technically
> > > > > needed as gcc-multilib is not able to make use of the libc in
> > > > > /lib/x86_64-linux-gnu.
> > > > > 
> > > > > > apt makes sure that all libc packages are upgraded at once to the 
> > > > > > same
> > > > > > version. However, during the upgrade process, the package
> > > > > > libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, 
> > > > > > we
> > > > > > temporarily have two libcs with different versions on the system, 
> > > > > > and this
> > > > > > mismatch makes most of the x86-64 binaries crash. Due to the 
> > > > > > crashes, the
> > > > > > upgrade doesn't proceed and it doesn't install the correct libc 
> > > > > > version in
> > > > > > /lib/x86_64-linux-gnu/.
> > > > > > 
> > > > > > The result is unusable system.
> > > > > 
> > > > > I have done some tests, and while I confirm that libc6-i386:amd64 is
> > > > 
> > > > The problem is with libc6-amd64:i386 or libc6-amd64:x32.
> > > > Not libc6-i386:amd64.
> > > 
> > > Yes, sorry about that, I really did the test with libc6-amd64:i386, but
> > > mixed it when typing the mail.
> > > 
> > > > I.e. use amd64 Debian Sid base installation, add foreign architectures 
> > > > i386 and x32 and use this /etc/apt/sources.list:
> > > > 
> > > > deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main 
> > > > contrib non-free
> > > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased main
> > > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main
> > > > 
> > > > > unpacked much before libc6:amd64, it doesn't cause any issue here.
> > > > > Indeed the search path in ld.so is to give higher priority to
> > > > > /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> > > > > libc6:amd64 in version 2.24 (using force-all), while keeping
> > > > > libc6-amd64:i386 in version 2.25.
> > > > > 
> > > > > The only way to change the priority of the two path is using a
> > > > > non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf 
> > > > > or
> > > > > /etc/ld.so.conf.d/*? Maybe you can share the content of this file and
> > > > > this directory.
> > > > 
> > > > On my system, there's a file 
> > > > /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
> > > > containing:
> > > > 
> > > > # Legacy biarch compatibility support
> > > > /lib64
> > > > /usr/lib64
> > > > 
> > > > and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:
> > > > 
> > > > # Legacy biarch compatibility support
> > > > /lib32
> > > > /usr/lib32
> > > > 
> > > > These files are created by the packages libc6-i386:x32 and 
> > > > libc6-amd64:x32. They cause that /lib64 is preferred to 
> > > > /lib/x86_64-linux-gnu/. If I delete these files and run ldconfig, the 
> > > > linker will prefer /lib/x86_64-linux-gnu/.
> > > 
> > > Those files are installed with the zz_ prefix to make sure they are
> > > 

Bug#879071: marked as done (0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2017 00:33:59 +
with message-id 
and subject line Bug#879071: fixed in 0ad 0.0.22-3.1
has caused the Debian Bug report #879071,
regarding 0ad FTBFS with on armhf with gcc 7: error: call of overloaded 
'abs(unsigned int)' is ambiguous
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/0ad.html
https://buildd.debian.org/status/fetch.php?pkg=0ad=armhf=0.0.22-1=1508365643=0

...
../../../source/gui/CDropDown.cpp: In member function 'virtual InReaction 
CDropDown::ManuallyHandleEvent(const SDL_Event_*)':
../../../source/gui/CDropDown.cpp:355:94: error: call of overloaded 
'abs(unsigned int)' is ambiguous
   diff = std::abs(pList->m_Items[i].GetRawString().LowerCase()[j] - 
(int)m_InputBuffer[j]);

  ^
In file included from /usr/include/c++/7/cmath:47:0,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
In file included from /usr/include/c++/7/bits/std_abs.h:38:0,
 from /usr/include/c++/7/cmath:47,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
gui.make:198: recipe for target 'obj/gui_Release/CDropDown.o' failed
make[3]: *** [obj/gui_Release/CDropDown.o] Error 1
--- End Message ---
--- Begin Message ---
Source: 0ad
Source-Version: 0.0.22-3.1

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

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

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 0ad 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: Tue, 21 Nov 2017 00:15:10 +
Source: 0ad
Binary: 0ad
Architecture: source
Version: 0.0.22-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Peter Michael Green 
Description:
 0ad- Real-time strategy game of ancient warfare
Closes: 879071
Changes:
 0ad (0.0.22-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload with maintainers permission.
   * Add armhf back to architecture list.
   * Fix "0ad FTBFS with on armhf with gcc 7: error: call of overloaded
 'abs(unsigned int)' is ambiguous" (Closes: #879071)
Checksums-Sha1:
 9b81fdb82832872fc900f0f473e1449d512006c6 2402 0ad_0.0.22-3.1.dsc
 fe1b79c2a504a0b2fbda1af1c6c6320fde55d363 72012 0ad_0.0.22-3.1.debian.tar.xz
 42c600e565dec9e0971087d79a8311c5b7bf3f44 12619 0ad_0.0.22-3.1_source.buildinfo
Checksums-Sha256:
 59ea3438740d1d3c980a8e9b634285a2910676b434222e40e9e5b793d63dab37 2402 
0ad_0.0.22-3.1.dsc
 

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-21 01:01, Mikulas Patocka wrote:
> 
> 
> On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> 
> > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > > 
> > > 
> > > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > > 
> > > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > > Package: libc6-amd64
> > > > > Version: 2.25-1
> > > > > Severity: critical
> > > > > Justification: breaks the whole system
> > > > > 
> > > > > Dear Maintainer,
> > > > > 
> > > > > *** Reporter, please consider answering these questions, where 
> > > > > appropriate ***
> > > > > 
> > > > >* What led up to the situation?
> > > > > 
> > > > > I have a x86-64 system with i386 and x32 foreign architectures 
> > > > > (because I
> > > > > need to develop software for i386 and x32 architectures).
> > > > > 
> > > > >* What exactly did you do (or not do) that was effective (or
> > > > >  ineffective)?
> > > > > 
> > > > > I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> > > > > 
> > > > >* What was the outcome of this action?
> > > > > 
> > > > > Halfway through apt upgrade it failed and I ended up with unusable 
> > > > > system where
> > > > > large number of binaries were segfauting on startup without doign 
> > > > > anything.
> > > > > 
> > > > >* What outcome did you expect instead?
> > > > > 
> > > > > The upgrade to libc-2.25 should work.
> > > > > 
> > > > > 
> > > > > The reason for the catastrophic failure is this:
> > > > > 
> > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > 
> > > > I guess you mean you have installed one of the two, not both.
> > > > 
> > > > > x86-64 libc in /lib64/). This package is not technically needed 
> > > > > (because
> > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > > > installed nonetheless because of some dependencies.
> > > > 
> > > > Just to be clear, as said in my other email, this *is* technically
> > > > needed as gcc-multilib is not able to make use of the libc in
> > > > /lib/x86_64-linux-gnu.
> > > > 
> > > > > apt makes sure that all libc packages are upgraded at once to the same
> > > > > version. However, during the upgrade process, the package
> > > > > libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
> > > > > temporarily have two libcs with different versions on the system, and 
> > > > > this
> > > > > mismatch makes most of the x86-64 binaries crash. Due to the crashes, 
> > > > > the
> > > > > upgrade doesn't proceed and it doesn't install the correct libc 
> > > > > version in
> > > > > /lib/x86_64-linux-gnu/.
> > > > > 
> > > > > The result is unusable system.
> > > > 
> > > > I have done some tests, and while I confirm that libc6-i386:amd64 is
> > > 
> > > The problem is with libc6-amd64:i386 or libc6-amd64:x32.
> > > Not libc6-i386:amd64.
> > 
> > Yes, sorry about that, I really did the test with libc6-amd64:i386, but
> > mixed it when typing the mail.
> > 
> > > I.e. use amd64 Debian Sid base installation, add foreign architectures 
> > > i386 and x32 and use this /etc/apt/sources.list:
> > > 
> > > deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main contrib 
> > > non-free
> > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased main
> > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main
> > > 
> > > > unpacked much before libc6:amd64, it doesn't cause any issue here.
> > > > Indeed the search path in ld.so is to give higher priority to
> > > > /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> > > > libc6:amd64 in version 2.24 (using force-all), while keeping
> > > > libc6-amd64:i386 in version 2.25.
> > > > 
> > > > The only way to change the priority of the two path is using a
> > > > non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf or
> > > > /etc/ld.so.conf.d/*? Maybe you can share the content of this file and
> > > > this directory.
> > > 
> > > On my system, there's a file 
> > > /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
> > > containing:
> > > 
> > > # Legacy biarch compatibility support
> > > /lib64
> > > /usr/lib64
> > > 
> > > and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:
> > > 
> > > # Legacy biarch compatibility support
> > > /lib32
> > > /usr/lib32
> > > 
> > > These files are created by the packages libc6-i386:x32 and 
> > > libc6-amd64:x32. They cause that /lib64 is preferred to 
> > > /lib/x86_64-linux-gnu/. If I delete these files and run ldconfig, the 
> > > linker will prefer /lib/x86_64-linux-gnu/.
> > 
> > Those files are installed with the zz_ prefix to make sure they are
> > included last, and therefore after x86_64-linux-gnu.conf. It seems to
> > be missing on your system and is probably the root of your problem. This
> > file is installed by libc6:amd64.
> > 
> > Aurelien
> 
> I have /etc/ld.so.conf.d/x86_64-linux-gnu.conf, it contains 
> # Multiarch support
> /lib/x86_64-linux-gnu
> 

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Tue, 21 Nov 2017, Aurelien Jarno wrote:

> On 2017-11-21 00:15, Mikulas Patocka wrote:
> > 
> > 
> > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > 
> > > On 2017-11-20 21:58, Mikulas Patocka wrote:
> > > > 
> > > > 
> > > > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > > > 
> > > > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > > > x86-64 libc in /lib64/). This package is not technically needed 
> > > > > > (because
> > > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it 
> > > > > > is
> > > > > > installed nonetheless because of some dependencies.
> > > > > 
> > > > > The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not 
> > > > > new, I
> > > > > tried to do it in the past, just to see, with the same kind of effect 
> > > > > as
> > > > > you had.
> > > > > 
> > > > > The question is rather how that got pulled at all. What package thinks
> > > > > it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> > > > > (which should normally not get pulled either), I can see uc-echo which
> > > > > should rather use foreign dependencies, and :i386 multilib packages
> > > > > which don't really make sense to install either.
> > > > > 
> > > > > I don't remember whether it was tried to make libc6-amd64:i386 
> > > > > conflict
> > > > > with libc6:amd64 (and vice-versa for i386) to make sure that this
> > > > > doesn't happen by misfortune?
> > > > > 
> > > > > Samuel
> > > > 
> > > > libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, 
> > > > lib64asan3, 
> > > > lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, 
> > > > lib64itm1, 
> > > > lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.
> > > > 
> > > > If you install gcc-7-multilib for non-default architecture (i386 or 
> > > > x32), 
> > > > it will inevitably pull libc6-amd64.
> > > 
> > > What's the point of doing that, as opposed for example building with
> > > -m32 or mx32?
> > 
> > The native x32 gcc binary is about 10% faster than the amd64 binary.
> 
> In that case you can install only gcc-7:x32 instead of gcc-7-multilib:x32,
> which won't pull libc6-amd64:x32.

But then, it won't be able to build i386 and amd64 binaries.

Mikulas

> -- 
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
> 

Bug#877353: marked as done (acpica-unix FTBFS on mips64el: error: cast from pointer to integer of different size)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2017 00:03:58 +
with message-id 
and subject line Bug#877353: fixed in acpica-unix 20171110-1
has caused the Debian Bug report #877353,
regarding acpica-unix FTBFS on mips64el: error: cast from pointer to integer of 
different size
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.)


-- 
877353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acpica-unix
Version: 20170831-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=acpica-unix=mips64el=20170831-1=1506550333=0

...
-  Intermediate obj/aslcompilerparse.c
/<>/generate/unix/iasl/obj/aslcompiler.y: In function 
'AslCompilerparse':
/<>/generate/unix/iasl/obj/aslcompiler.y:1089:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_NAMESTRING{$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) $1);}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1090:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_IO{$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "IO");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1091:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_DMA   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "DMA");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1092:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_IRQ   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "IRQ");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1093:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_FOR   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "FOR");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1104:41: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 (ACPI_NATIVE_INT) AslCompilerlval.s);}
 ^
/<>/generate/unix/iasl/obj/aslcompiler.y:1474:41: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 (ACPI_NATIVE_INT) AslCompilerlval.s);}
 ^
cc1: all warnings being treated as errors
Makefile:344: recipe for target 'obj/aslcompilerparse.o' failed
make[3]: *** [obj/aslcompilerparse.o] Error 1



The fix is attached.
Description: Stop listing all 64bit architectures
 Check __LP64__ instead of maintaining a list of all
 64bit architectures.
Author: Adrian Bunk 

--- acpica-unix-20170831.orig/source/include/platform/aclinux.h
+++ acpica-unix-20170831/source/include/platform/aclinux.h
@@ -208,9 +208,7 @@
 #define ACPI_FLUSH_CPU_CACHE()
 #define ACPI_CAST_PTHREAD_T(Pthread) ((ACPI_THREAD_ID) (Pthread))
 
-#if defined(__ia64__)|| defined(__x86_64__) ||\
-defined(__aarch64__) || defined(__PPC64__) ||\
-defined(__s390x__)
+#if defined(__LP64__)
 #define ACPI_MACHINE_WIDTH  64
 #define COMPILER_DEPENDENT_INT64long
 #define COMPILER_DEPENDENT_UINT64   unsigned long
--- End Message ---
--- Begin Message ---
Source: acpica-unix
Source-Version: 20171110-1

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

Debian distribution maintenance software
pp.
Al Stone  (supplier of updated acpica-unix 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: 

Bug#863568: marked as done (cfengine3: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Tue, 21 Nov 2017 00:04:20 +
with message-id 
and subject line Bug#863568: fixed in cfengine3 3.10.2-1
has caused the Debian Bug report #863568,
regarding cfengine3: Please migrate to openssl1.1 in Buster
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.)


-- 
863568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cfengine3
Version: 3.9.1-4.2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: cfengine3
Source-Version: 3.10.2-1

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

Debian distribution maintenance software
pp.
Antonio Radici  (supplier of updated cfengine3 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, 20 Nov 2017 23:01:12 +
Source: cfengine3
Binary: cfengine3 cfengine3-dbg libpromises3
Architecture: source
Version: 3.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Antonio Radici 
Changed-By: Antonio Radici 
Description:
 cfengine3  - tool for configuring and maintaining network machines
 cfengine3-dbg - debugging symbols for cfengine3
 libpromises3 - libpromises library for cfengine3 binaries
Closes: 863568
Changes:
 cfengine3 (3.10.2-1) unstable; urgency=medium
 .
   * Uploading the official LTS for cfengine3
 + it builds with openssl 1.1 (Closes: 863568)
   * debian/patches:
 + Removed the following patches, already upstream:
   * 0003-remove_man_errors.patch
   * 0009_disable_spelling_errors.patch
   * 0011_build_with_openssl_1.1.patch
 + refreshed the remaining patches.
 + created 0001-CFE-2629-Fix-source-to-build-with-before-and-after-1.patch
   from upstream commit e95dcc083c022, to build wiht openssl 1.1
   * added debian/source/include-binaries with some unrepresentable content
 from the masterfiles.
   * debian/compat: set it to 9, compatibility <= 7 is deprecated.
Checksums-Sha1:
 9a2837fa9bdd60d694b5851b6a79c4a51a5bf9ac 2461 cfengine3_3.10.2-1.dsc
 8b980f381ea50ae012c660259157c25616d8a30e 472049 
cfengine3_3.10.2.orig-masterfiles.tar.gz
 c40adf04c7ef9a6d115957484a901a48f1dcf6a1 2366237 cfengine3_3.10.2.orig.tar.gz
 d503450f4d61b08538889e0162aad1d93bff3f8f 27184 cfengine3_3.10.2-1.debian.tar.xz
 cdf9556c829a88a137d1dbdf317f95ff8aa7b5ac 7859 
cfengine3_3.10.2-1_amd64.buildinfo
Checksums-Sha256:
 7613d23e250acf3c6ce7ff23188e313e448c4c8bef4ea1d2da71be16fa7b9db1 2461 
cfengine3_3.10.2-1.dsc
 5d18a8d71f451d0b5dd1f5e579452b29b99b664f2bb0827dbba9a615f2764df6 472049 
cfengine3_3.10.2.orig-masterfiles.tar.gz
 d4fa9ac7276dba7b85d6757aab2f0929ab8d3b115cb0e7b0cf984760347429d7 2366237 
cfengine3_3.10.2.orig.tar.gz
 ab625887f8e2976b8c6a2ea378bdcf481ca28a87d1f60ee014501d2d46871ddd 27184 
cfengine3_3.10.2-1.debian.tar.xz
 ace83f1bf744f0dde7af4bbd87247179322104907975968db36cd16387df898b 7859 
cfengine3_3.10.2-1_amd64.buildinfo
Files:
 ce7c0c8d19d13c95779041dc72d16c13 2461 admin optional cfengine3_3.10.2-1.dsc
 1247ef4e8f3cee5efa98da50c326e5a4 472049 admin optional 
cfengine3_3.10.2.orig-masterfiles.tar.gz
 c16baf08189a1af6fcf2e2ff61102992 2366237 admin optional 
cfengine3_3.10.2.orig.tar.gz
 dfde9c344c37d2d4f7dc809192d482ad 27184 admin optional 
cfengine3_3.10.2-1.debian.tar.xz
 1113764ee8564d5a45e6efc80c141451 7859 admin optional 
cfengine3_3.10.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEQObYrBkA1SRrfOa1NcjIiHLLHu0FAloTaMgTHGFudG9uaW9A
ZGViaWFuLm9yZwAKCRA1yMiIcsse7RokD/9qoILMk9OFlQC3tTXjMK56lioDoHpM
d0ESb8yshazVCM5fSwZHN9jPW4Ro6t2laZoM9N8P9q4t/ZBESquXc7NoQ2caF+ve
l16+LkXVggC4IOEZKxblYlaPmc5g2Id1C+GJPQY6TQL857xBhQ+HlGjohr8Gu7+O
NbiTjcP+0e+rOc3VA6tMI48FVAMh49o0AIZ/9sskkLKx52Bad7P9HP4LfnIWIIcM
98LjEB7nMqWEZBHk1G8tXuyuD66f+TLJzIPYG3Vh6rJpnXMN7cn5wJFpmoDVPxB9

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Tue, 21 Nov 2017, Aurelien Jarno wrote:

> On 2017-11-21 00:12, Mikulas Patocka wrote:
> > 
> > 
> > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > 
> > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > Package: libc6-amd64
> > > > Version: 2.25-1
> > > > Severity: critical
> > > > Justification: breaks the whole system
> > > > 
> > > > Dear Maintainer,
> > > > 
> > > > *** Reporter, please consider answering these questions, where 
> > > > appropriate ***
> > > > 
> > > >* What led up to the situation?
> > > > 
> > > > I have a x86-64 system with i386 and x32 foreign architectures (because 
> > > > I
> > > > need to develop software for i386 and x32 architectures).
> > > > 
> > > >* What exactly did you do (or not do) that was effective (or
> > > >  ineffective)?
> > > > 
> > > > I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> > > > 
> > > >* What was the outcome of this action?
> > > > 
> > > > Halfway through apt upgrade it failed and I ended up with unusable 
> > > > system where
> > > > large number of binaries were segfauting on startup without doign 
> > > > anything.
> > > > 
> > > >* What outcome did you expect instead?
> > > > 
> > > > The upgrade to libc-2.25 should work.
> > > > 
> > > > 
> > > > The reason for the catastrophic failure is this:
> > > > 
> > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > 
> > > I guess you mean you have installed one of the two, not both.
> > > 
> > > > x86-64 libc in /lib64/). This package is not technically needed (because
> > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > > installed nonetheless because of some dependencies.
> > > 
> > > Just to be clear, as said in my other email, this *is* technically
> > > needed as gcc-multilib is not able to make use of the libc in
> > > /lib/x86_64-linux-gnu.
> > > 
> > > > apt makes sure that all libc packages are upgraded at once to the same
> > > > version. However, during the upgrade process, the package
> > > > libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
> > > > temporarily have two libcs with different versions on the system, and 
> > > > this
> > > > mismatch makes most of the x86-64 binaries crash. Due to the crashes, 
> > > > the
> > > > upgrade doesn't proceed and it doesn't install the correct libc version 
> > > > in
> > > > /lib/x86_64-linux-gnu/.
> > > > 
> > > > The result is unusable system.
> > > 
> > > I have done some tests, and while I confirm that libc6-i386:amd64 is
> > 
> > The problem is with libc6-amd64:i386 or libc6-amd64:x32.
> > Not libc6-i386:amd64.
> 
> Yes, sorry about that, I really did the test with libc6-amd64:i386, but
> mixed it when typing the mail.
> 
> > I.e. use amd64 Debian Sid base installation, add foreign architectures 
> > i386 and x32 and use this /etc/apt/sources.list:
> > 
> > deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main contrib 
> > non-free
> > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased main
> > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main
> > 
> > > unpacked much before libc6:amd64, it doesn't cause any issue here.
> > > Indeed the search path in ld.so is to give higher priority to
> > > /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> > > libc6:amd64 in version 2.24 (using force-all), while keeping
> > > libc6-amd64:i386 in version 2.25.
> > > 
> > > The only way to change the priority of the two path is using a
> > > non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf or
> > > /etc/ld.so.conf.d/*? Maybe you can share the content of this file and
> > > this directory.
> > 
> > On my system, there's a file /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
> > containing:
> > 
> > # Legacy biarch compatibility support
> > /lib64
> > /usr/lib64
> > 
> > and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:
> > 
> > # Legacy biarch compatibility support
> > /lib32
> > /usr/lib32
> > 
> > These files are created by the packages libc6-i386:x32 and 
> > libc6-amd64:x32. They cause that /lib64 is preferred to 
> > /lib/x86_64-linux-gnu/. If I delete these files and run ldconfig, the 
> > linker will prefer /lib/x86_64-linux-gnu/.
> 
> Those files are installed with the zz_ prefix to make sure they are
> included last, and therefore after x86_64-linux-gnu.conf. It seems to
> be missing on your system and is probably the root of your problem. This
> file is installed by libc6:amd64.
> 
> Aurelien

I have /etc/ld.so.conf.d/x86_64-linux-gnu.conf, it contains 
# Multiarch support
/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu

But nonetheless, the linker prefers libc from /lib64.

I have these files in /etc/ld.so.conf.d:

i386-linux-gnu.conf:# Multiarch support
i386-linux-gnu.conf:/lib/i386-linux-gnu
i386-linux-gnu.conf:/usr/lib/i386-linux-gnu
i386-linux-gnu.conf:/lib/i686-linux-gnu
i386-linux-gnu.conf:/usr/lib/i686-linux-gnu

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-21 00:12, Mikulas Patocka wrote:
> 
> 
> On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> 
> > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > Package: libc6-amd64
> > > Version: 2.25-1
> > > Severity: critical
> > > Justification: breaks the whole system
> > > 
> > > Dear Maintainer,
> > > 
> > > *** Reporter, please consider answering these questions, where 
> > > appropriate ***
> > > 
> > >* What led up to the situation?
> > > 
> > > I have a x86-64 system with i386 and x32 foreign architectures (because I
> > > need to develop software for i386 and x32 architectures).
> > > 
> > >* What exactly did you do (or not do) that was effective (or
> > >  ineffective)?
> > > 
> > > I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> > > 
> > >* What was the outcome of this action?
> > > 
> > > Halfway through apt upgrade it failed and I ended up with unusable system 
> > > where
> > > large number of binaries were segfauting on startup without doign 
> > > anything.
> > > 
> > >* What outcome did you expect instead?
> > > 
> > > The upgrade to libc-2.25 should work.
> > > 
> > > 
> > > The reason for the catastrophic failure is this:
> > > 
> > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > 
> > I guess you mean you have installed one of the two, not both.
> > 
> > > x86-64 libc in /lib64/). This package is not technically needed (because
> > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > installed nonetheless because of some dependencies.
> > 
> > Just to be clear, as said in my other email, this *is* technically
> > needed as gcc-multilib is not able to make use of the libc in
> > /lib/x86_64-linux-gnu.
> > 
> > > apt makes sure that all libc packages are upgraded at once to the same
> > > version. However, during the upgrade process, the package
> > > libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
> > > temporarily have two libcs with different versions on the system, and this
> > > mismatch makes most of the x86-64 binaries crash. Due to the crashes, the
> > > upgrade doesn't proceed and it doesn't install the correct libc version in
> > > /lib/x86_64-linux-gnu/.
> > > 
> > > The result is unusable system.
> > 
> > I have done some tests, and while I confirm that libc6-i386:amd64 is
> 
> The problem is with libc6-amd64:i386 or libc6-amd64:x32.
> Not libc6-i386:amd64.

Yes, sorry about that, I really did the test with libc6-amd64:i386, but
mixed it when typing the mail.

> I.e. use amd64 Debian Sid base installation, add foreign architectures 
> i386 and x32 and use this /etc/apt/sources.list:
> 
> deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main contrib 
> non-free
> deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased main
> deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main
> 
> > unpacked much before libc6:amd64, it doesn't cause any issue here.
> > Indeed the search path in ld.so is to give higher priority to
> > /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> > libc6:amd64 in version 2.24 (using force-all), while keeping
> > libc6-amd64:i386 in version 2.25.
> > 
> > The only way to change the priority of the two path is using a
> > non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf or
> > /etc/ld.so.conf.d/*? Maybe you can share the content of this file and
> > this directory.
> 
> On my system, there's a file /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
> containing:
> 
> # Legacy biarch compatibility support
> /lib64
> /usr/lib64
> 
> and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:
> 
> # Legacy biarch compatibility support
> /lib32
> /usr/lib32
> 
> These files are created by the packages libc6-i386:x32 and 
> libc6-amd64:x32. They cause that /lib64 is preferred to 
> /lib/x86_64-linux-gnu/. If I delete these files and run ldconfig, the 
> linker will prefer /lib/x86_64-linux-gnu/.

Those files are installed with the zz_ prefix to make sure they are
included last, and therefore after x86_64-linux-gnu.conf. It seems to
be missing on your system and is probably the root of your problem. This
file is installed by libc6:amd64.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-21 00:15, Mikulas Patocka wrote:
> 
> 
> On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> 
> > On 2017-11-20 21:58, Mikulas Patocka wrote:
> > > 
> > > 
> > > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > > 
> > > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > > x86-64 libc in /lib64/). This package is not technically needed 
> > > > > (because
> > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > > > installed nonetheless because of some dependencies.
> > > > 
> > > > The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> > > > tried to do it in the past, just to see, with the same kind of effect as
> > > > you had.
> > > > 
> > > > The question is rather how that got pulled at all. What package thinks
> > > > it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> > > > (which should normally not get pulled either), I can see uc-echo which
> > > > should rather use foreign dependencies, and :i386 multilib packages
> > > > which don't really make sense to install either.
> > > > 
> > > > I don't remember whether it was tried to make libc6-amd64:i386 conflict
> > > > with libc6:amd64 (and vice-versa for i386) to make sure that this
> > > > doesn't happen by misfortune?
> > > > 
> > > > Samuel
> > > 
> > > libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, lib64asan3, 
> > > lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, 
> > > lib64itm1, 
> > > lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.
> > > 
> > > If you install gcc-7-multilib for non-default architecture (i386 or x32), 
> > > it will inevitably pull libc6-amd64.
> > 
> > What's the point of doing that, as opposed for example building with
> > -m32 or mx32?
> 
> The native x32 gcc binary is about 10% faster than the amd64 binary.

In that case you can install only gcc-7:x32 instead of gcc-7-multilib:x32,
which won't pull libc6-amd64:x32.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Mon, 20 Nov 2017, Aurelien Jarno wrote:

> On 2017-11-20 21:58, Mikulas Patocka wrote:
> > 
> > 
> > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > 
> > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > x86-64 libc in /lib64/). This package is not technically needed (because
> > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > > installed nonetheless because of some dependencies.
> > > 
> > > The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> > > tried to do it in the past, just to see, with the same kind of effect as
> > > you had.
> > > 
> > > The question is rather how that got pulled at all. What package thinks
> > > it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> > > (which should normally not get pulled either), I can see uc-echo which
> > > should rather use foreign dependencies, and :i386 multilib packages
> > > which don't really make sense to install either.
> > > 
> > > I don't remember whether it was tried to make libc6-amd64:i386 conflict
> > > with libc6:amd64 (and vice-versa for i386) to make sure that this
> > > doesn't happen by misfortune?
> > > 
> > > Samuel
> > 
> > libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, lib64asan3, 
> > lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, lib64itm1, 
> > lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.
> > 
> > If you install gcc-7-multilib for non-default architecture (i386 or x32), 
> > it will inevitably pull libc6-amd64.
> 
> What's the point of doing that, as opposed for example building with
> -m32 or mx32?

The native x32 gcc binary is about 10% faster than the amd64 binary.

> > If we removed libc6-amd64 at all, it would cause problems building amd64 
> > packages on i386 system. We could make those lib64* packages dependent on 
> > libc6:amd64 instead, but that would break if the user has i386 
> > installation and he doesn't have amd64 foreign architecture set up.
> > 
> > It would be best to set it up so that libc6-amd64 doesn't install any 
> > files only if libc6:amd64 is present. Could it be done with the deb 
> > format?
> 
> It's not something possible, and it's even more complicated than that.
> The current ugly way the multiarch + multilib is done, uses a different
> libc for linking and executing. So you definitely need to install both
> if you want to be able to build and execute code.
> 
> -- 
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net

Mikulas

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Mon, 20 Nov 2017, Aurelien Jarno wrote:

> On 2017-11-20 19:13, Mikulas Patocka wrote:
> > Package: libc6-amd64
> > Version: 2.25-1
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > Dear Maintainer,
> > 
> > *** Reporter, please consider answering these questions, where appropriate 
> > ***
> > 
> >* What led up to the situation?
> > 
> > I have a x86-64 system with i386 and x32 foreign architectures (because I
> > need to develop software for i386 and x32 architectures).
> > 
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > 
> > I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> > 
> >* What was the outcome of this action?
> > 
> > Halfway through apt upgrade it failed and I ended up with unusable system 
> > where
> > large number of binaries were segfauting on startup without doign anything.
> > 
> >* What outcome did you expect instead?
> > 
> > The upgrade to libc-2.25 should work.
> > 
> > 
> > The reason for the catastrophic failure is this:
> > 
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> 
> I guess you mean you have installed one of the two, not both.
> 
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > installed nonetheless because of some dependencies.
> 
> Just to be clear, as said in my other email, this *is* technically
> needed as gcc-multilib is not able to make use of the libc in
> /lib/x86_64-linux-gnu.
> 
> > apt makes sure that all libc packages are upgraded at once to the same
> > version. However, during the upgrade process, the package
> > libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
> > temporarily have two libcs with different versions on the system, and this
> > mismatch makes most of the x86-64 binaries crash. Due to the crashes, the
> > upgrade doesn't proceed and it doesn't install the correct libc version in
> > /lib/x86_64-linux-gnu/.
> > 
> > The result is unusable system.
> 
> I have done some tests, and while I confirm that libc6-i386:amd64 is

The problem is with libc6-amd64:i386 or libc6-amd64:x32.
Not libc6-i386:amd64.

I.e. use amd64 Debian Sid base installation, add foreign architectures 
i386 and x32 and use this /etc/apt/sources.list:

deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main contrib 
non-free
deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased main
deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main

> unpacked much before libc6:amd64, it doesn't cause any issue here.
> Indeed the search path in ld.so is to give higher priority to
> /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> libc6:amd64 in version 2.24 (using force-all), while keeping
> libc6-amd64:i386 in version 2.25.
> 
> The only way to change the priority of the two path is using a
> non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf or
> /etc/ld.so.conf.d/*? Maybe you can share the content of this file and
> this directory.
> 
> -- 
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net

On my system, there's a file /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
containing:

# Legacy biarch compatibility support
/lib64
/usr/lib64

and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:

# Legacy biarch compatibility support
/lib32
/usr/lib32

These files are created by the packages libc6-i386:x32 and 
libc6-amd64:x32. They cause that /lib64 is preferred to 
/lib/x86_64-linux-gnu/. If I delete these files and run ldconfig, the 
linker will prefer /lib/x86_64-linux-gnu/.

Mikulas

Bug#882264: Pending fixes for bugs in the libtemplate-declare-perl package

[pkg-perl-maintainers]

tag 882264 + pending
thanks

Some bugs in the libtemplate-declare-perl package are closed in
revision f51e1dfdbcf6e6bcd57e6aaddc6e0b7467779445 in branch 'master'
by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtemplate-declare-perl.git/commit/?id=f51e1df

Commit message:

Add a patch to fix test failures with HTML::Lint 2.26.

Closes: #882264

Processed: Pending fixes for bugs in the libtemplate-declare-perl package

[Debian Bug Tracking System]

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

> tag 882264 + pending
Bug #882264 [src:libtemplate-declare-perl] libtemplate-declare-perl FTBFS with 
libhtml-lint-perl 2.26+dfsg-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 882264

[Debian Bug Tracking System]

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

> tags 882264 + patch
Bug #882264 [src:libtemplate-declare-perl] libtemplate-declare-perl FTBFS with 
libhtml-lint-perl 2.26+dfsg-1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#873401: marked as done (clamav FTBFS with LLVM 4.0 as default)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 22:49:09 +
with message-id 
and subject line Bug#873401: fixed in clamav 0.99.3~beta1+dfsg-3
has caused the Debian Bug report #873401,
regarding clamav FTBFS with LLVM 4.0 as default
to be marked as done.

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

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


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

Hello,

Currently, we have 6 versions of the llvm toolchain in the archive.
I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)

Could you please update your package to use 4.0 (or, better, 5.0 which will be 
released very 
soon)?

I will update the severity of this bug at the end of September

Thanks
Sylvestre



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 0.99.3~beta1+dfsg-3

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated clamav 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 21:52:34 +0100
Source: clamav
Binary: clamav-base clamav-docs clamav libclamav-dev libclamav7 clamav-daemon 
clamdscan clamav-testfiles clamav-freshclam clamav-milter
Architecture: source
Version: 0.99.3~beta1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Description:
 clamav - anti-virus utility for Unix - command-line interface
 clamav-base - anti-virus utility for Unix - base package
 clamav-daemon - anti-virus utility for Unix - scanner daemon
 clamav-docs - anti-virus utility for Unix - documentation
 clamav-freshclam - anti-virus utility for Unix - virus database update utility
 clamav-milter - anti-virus utility for Unix - sendmail integration
 clamav-testfiles - anti-virus utility for Unix - test files
 clamdscan  - anti-virus utility for Unix - scanner client
 libclamav-dev - anti-virus utility for Unix - development files
 libclamav7 - anti-virus utility for Unix - library
Closes: 873401 881634 881780
Changes:
 clamav (0.99.3~beta1+dfsg-3) unstable; urgency=medium
 .
   * Drop "demime = *" from Debian.README for clamav, this option is gone from
 exim (Closes: #881634).
   * Use "ucf" instead "ucp" in clamav-milter's postinst.
   * Disable LLVM support due to 3.8 removal (Closes: #873401).
   * Disable the freshclam service if changed to `manual' mode so it does start
 again after system reboot with systemd (Closes: #881780).
   * Bump standards version to 4.1.1 without further change.
   * Allow to build as non root user.
   * Update dh compat level 10
Checksums-Sha1:
 a9c77721d344f59167aab38df0ac19019681b966 3041 clamav_0.99.3~beta1+dfsg-3.dsc
 bf598d822e10991c0bc254ee463a516f41d17c4b 216080 
clamav_0.99.3~beta1+dfsg-3.debian.tar.xz
 4ddff99047d737e0cdf99ec9ff506a549bda3ee6 7399 
clamav_0.99.3~beta1+dfsg-3_source.buildinfo
Checksums-Sha256:
 3099f4d5b5c6c2bb16bcaab1d93d04c97c9c602a0b85ed5368770b5c9f6981a7 3041 
clamav_0.99.3~beta1+dfsg-3.dsc
 69d72066d8835aa8e254cf63fc0eb1d567b9d075e684e3dc1f9a618714d53e97 216080 
clamav_0.99.3~beta1+dfsg-3.debian.tar.xz
 89df81be648b753ce5e27b937395e1d2de564111f75338948a9e085140427b30 7399 
clamav_0.99.3~beta1+dfsg-3_source.buildinfo
Files:
 33e645a5e6433a78afdc054a63738f26 3041 utils optional 
clamav_0.99.3~beta1+dfsg-3.dsc
 dfb1d6f8a4be3e03f653bbba505ecc7a 216080 utils optional 
clamav_0.99.3~beta1+dfsg-3.debian.tar.xz
 

Bug#855876: marked as done (golang-etcd-server-dev: ships md5sums but no files: /usr/share/gocode/src/github.com/coreos/etcd/integration/*)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 22:49:16 +
with message-id 
and subject line Bug#855876: fixed in etcd 3.2.9+dfsg-3
has caused the Debian Bug report #855876,
regarding golang-etcd-server-dev: ships md5sums but no files: 
/usr/share/gocode/src/github.com/coreos/etcd/integration/*
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.)


-- 
855876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-etcd-server-dev
Version: 3.1.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed debsums reports some missing
files in your package.
Looks like these are present in the md5sums file, but not in the
package itself.

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

2m18.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2100901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2102901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105501396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105601396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142501396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142601396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142701396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142801396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143701396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143801396 
(from 

Bug#855876: Pending fixes for bugs in the etcd package

[pkg-go-maintainers]

tag 855876 + pending
thanks

Some bugs in the etcd package are closed in revision
0afc17c8a5f3ebbc6387a7223ae8192f8e3bd626 in branch 'master' by Dr.
Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/etcd.git/commit/?id=0afc17c

Commit message:

Exclude the sockets from the MD5 sum generation.

Closes: #855876

Bug#859957: marked as done (natbraille: ftbfs without networking)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 22:34:39 +
with message-id 
and subject line Bug#859957: fixed in natbraille 2.0rc3-6
has caused the Debian Bug report #859957,
regarding natbraille: ftbfs without networking
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.)


-- 
859957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: natbraille
Version: 2.0rc3-4
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs


natbraille fails to build from source on machines without an internet
connection. This is generally accepted to be a policy violation:

** Utilisation du dictionnaire de coupure existant

D?but de la conversion du document ... 

java.net.UnknownHostException: www.w3.org
...
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown 
Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
...

This happens on the reproducible-builds builder:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/natbraille.html
--- End Message ---
--- Begin Message ---
Source: natbraille
Source-Version: 2.0rc3-6

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated natbraille package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 23:19:28 +0100
Source: natbraille
Binary: natbraille natbraille-doc
Architecture: source
Version: 2.0rc3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 natbraille - French braille typesetting program
 natbraille-doc - Documentation for natbraille
Closes: 859957
Changes:
 natbraille (2.0rc3-6) unstable; urgency=medium
 .
   * rules: While checking output, use diff -u output. Support nocheck build
 option.
   * patches/nonetwork: Use sed to replace network DTD link with on-disk link
 (Closes: #859957)
   * debian/testresults/documents/testMathOpenOffice.odt.txt: Update accordingly
 (natbrailles' DTD are a bit different)
Checksums-Sha1:
 697b98e7029e093725587a8e586c934b9c872cc9 2364 natbraille_2.0rc3-6.dsc
 7d1648f4a2de94403b14578cc815cac22c5d942b 21136 
natbraille_2.0rc3-6.debian.tar.xz
Checksums-Sha256:
 9d8c4ec1bd039fefaec306d20b45c54ff39ddac6754f6baa86eaa0391d3a97ef 2364 
natbraille_2.0rc3-6.dsc
 d51dc3486e6cbf9bc994c3fa511b28ff3189e7339a8e545dfb70507725665203 21136 
natbraille_2.0rc3-6.debian.tar.xz
Files:
 31acdd26eda742036a4ab14edae9f904 2364 text optional natbraille_2.0rc3-6.dsc
 9374c9f96cb99cfad04dc55a0b3fbfaf 21136 text optional 
natbraille_2.0rc3-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErr90SPq5RTpFUjkOsKUb9YyRecUFAloTVigACgkQsKUb9YyR
ecVcyhAAl0KGDE7rJC8aA0HDKuFw7ADFVugow/mz4UIxJnrxTEb2bgMtZZAvkdIc
8qt3QyUS71td1E53kepAsYiua5BEf2EVFScgpLbBzV6gNWMxcq82VaDhWX3Glg9j
W2/vD/cuPnuxxYCvmskZTtmm6pFa2r0wFnp7RIOIZG1AY+jhVrnaidoUR+p4TYPF
srw6kQWm4qskgOKd3yqExQXDSu3FpamdSJVwPAEBJBrSAHa809Aas6ddkA0uvzBf
7mfp2Nr+RzytK8gL4DSpPCGMUmcrEDviNc5w4EhZKmPPgiCd1YRMy6thENZnJ/KZ
v8rlWtrKbcovUmbRENxPEguCcfe8CdLTWHi7jJlyI/wO1ad8eeBnO/ixwUNaVY5k
79FZjVAqdE47nrgoCyU1trvgl924eHjexOTEDyxs3C6Peg6AerjixeukrgXbDdt4
Xz+3UJTXBcSo0XekgttbP55i8+grd34mk/5/IQoihfza+MSDlqB2E54D854Mh6Lu
GkKBIY1eXc6qLq1okhn47spnt9kgg63NdHfOhjUNc3Wu7oR3XS68vkS1VhL1hXoE
eO3CefD0SojMPkkITP1fYRL06VnwMIbMNKgWORax9tPTPxXRus3vRdt0TrvUoG1o
NKPTW8j39EgugTQOVFEh75T2W37ruzMEKKgk3Lf+j6bHIaGo8io=
=lDKg
-END PGP SIGNATURE End Message ---

Processed: Bug#855876 tagged as pending

[Debian Bug Tracking System]

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

> tag 855876 pending
Bug #855876 [golang-etcd-server-dev] golang-etcd-server-dev: ships md5sums but 
no files: /usr/share/gocode/src/github.com/coreos/etcd/integration/*
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#855876: tagged as pending

[Dr . Tobias Quathamer]

tag 855876 pending
--

We believe that the bug #855876 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/pkg-go/packages/etcd.git/diff/?id=0afc17c

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 0afc17c8a5f3ebbc6387a7223ae8192f8e3bd626
Author: Dr. Tobias Quathamer 
Date:   Mon Nov 20 23:06:26 2017 +0100

Exclude the sockets from the MD5 sum generation.

Closes: #855876

Processed: Pending fixes for bugs in the etcd package

[Debian Bug Tracking System]

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

> tag 855876 + pending
Bug #855876 [golang-etcd-server-dev] golang-etcd-server-dev: ships md5sums but 
no files: /usr/share/gocode/src/github.com/coreos/etcd/integration/*
Ignoring request to alter tags of bug #855876 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 859957

[Debian Bug Tracking System]

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

> tags 859957 + pending
Bug #859957 [src:natbraille] natbraille: ftbfs without networking
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#878107: src:pcre3: stack frame size detection is broken

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Severity set to 'serious' from 'important'
> tags -1 -moreinfo
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Removed tag(s) moreinfo.
> found -1 2:8.35-3.3
Bug #878107 [src:pcre3] src:pcre3: stack frame size detection is broken
Marked as found in versions pcre3/2:8.35-3.3.

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

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-20 19:13, Mikulas Patocka wrote:
> Package: libc6-amd64
> Version: 2.25-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> I have a x86-64 system with i386 and x32 foreign architectures (because I
> need to develop software for i386 and x32 architectures).
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.
> 
>* What was the outcome of this action?
> 
> Halfway through apt upgrade it failed and I ended up with unusable system 
> where
> large number of binaries were segfauting on startup without doign anything.
> 
>* What outcome did you expect instead?
> 
> The upgrade to libc-2.25 should work.
> 
> 
> The reason for the catastrophic failure is this:
> 
> There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide

I guess you mean you have installed one of the two, not both.

> x86-64 libc in /lib64/). This package is not technically needed (because
> x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> installed nonetheless because of some dependencies.

Just to be clear, as said in my other email, this *is* technically
needed as gcc-multilib is not able to make use of the libc in
/lib/x86_64-linux-gnu.

> apt makes sure that all libc packages are upgraded at once to the same
> version. However, during the upgrade process, the package
> libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
> temporarily have two libcs with different versions on the system, and this
> mismatch makes most of the x86-64 binaries crash. Due to the crashes, the
> upgrade doesn't proceed and it doesn't install the correct libc version in
> /lib/x86_64-linux-gnu/.
> 
> The result is unusable system.

I have done some tests, and while I confirm that libc6-i386:amd64 is
unpacked much before libc6:amd64, it doesn't cause any issue here.
Indeed the search path in ld.so is to give higher priority to
/lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
libc6:amd64 in version 2.24 (using force-all), while keeping
libc6-amd64:i386 in version 2.25.

The only way to change the priority of the two path is using a
non-standard ld.so.conf. Have you made any change to /etc/ld.so.conf or
/etc/ld.so.conf.d/*? Maybe you can share the content of this file and
this directory.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#880941: pink-pony: diff for NMU version 1.4.1-2.1

[Adrian Bunk]

On Mon, Nov 20, 2017 at 11:45:27PM +0200, Adrian Bunk wrote:
> Control: tags 880941 + patch
> Control: tags 880941 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for pink-pony (versioned as 1.4.1-2.1) and uploaded 
> it to DELAYED/5. Please feel free to tell me if I should cancel it.

Apologies, I messed up and forgot to add the DELAYED parameter
when uploading.  :-(

> cu
> Adrian

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#880941: marked as done (pink-pony: Build-depends on glee-dev, but doesn't need it)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 22:06:09 +
with message-id 
and subject line Bug#880941: fixed in pink-pony 1.4.1-2.1
has caused the Debian Bug report #880941,
regarding pink-pony: Build-depends on glee-dev, but doesn't need it
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.)


-- 
880941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pink-pony
Version: 1.4.1-2
Severity: serious
Justification: glee is marked for auto-removal from testing

Dear Games Team,

Pink-pony build-depends on glee-dev, but 1.4.1-2 doesn't seem to need
this dependency, it builds and runs fine without it.

Because of this dependency, it's affected by Glee's auto-removal
from testing.  For Glee's #879905 I'm analysing how much effort
it would take to remove the glee package without losing any of
the rdeps.

Steve

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pink-pony
Source-Version: 1.4.1-2.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pink-pony package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 23:39:25 +0200
Source: pink-pony
Binary: pink-pony pink-pony-data pink-pony-dbg
Architecture: source
Version: 1.4.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Adrian Bunk 
Description:
 pink-pony  - 3D racing game with ponies
 pink-pony-data - 3D racing game with ponies - game data
 pink-pony-dbg - 3D racing game with ponies - debug
Closes: 880941
Changes:
 pink-pony (1.4.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove no longer required build dependency on glee-dev.
 (Closes: #880941)
   * Stop using a non-default compressor
 (xz is now default, and it compresses better than bzip2).
Checksums-Sha1:
 d74f4b4b0ddffbb65d97c7296dfe6a8df92063ad 2342 pink-pony_1.4.1-2.1.dsc
 0e144e0286a3d133d09dcb1f621fd55c2fb24ba0 64304 
pink-pony_1.4.1-2.1.debian.tar.xz
Checksums-Sha256:
 a2327b00759832d432e1d89ae15dd61568e88bb0e3d9a6c063417786e8d9088e 2342 
pink-pony_1.4.1-2.1.dsc
 d64ef4f9fc87a644dc18ad498dd90044f7956adb27892871350771da983c50e2 64304 
pink-pony_1.4.1-2.1.debian.tar.xz
Files:
 4446dfedde851d4897a483f806547e13 2342 games optional pink-pony_1.4.1-2.1.dsc
 d695695135f89c4a5248641f9a551133 64304 games optional 
pink-pony_1.4.1-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAloTTMgACgkQiNJCh6LY
mLG7cg/9Hr495/voHbL7yiw9yvdJ7lAhnG4XCg+7pudP566D1WKgkOUKyBEXBd52
k2WjeBQYlhGK52qiZbXpzdsZw5WvduD5WOIfxV2AMVFTzdpjkupd5H2eTDbTOGGA
I4u0McdIUx0sWvKr48UrPC2mjOA/dtmTs9aORA+ICFMvH2Hu9t6BbBGG7Nm910Yv
8yckTjd/+xjv/m5R+LBKFhJ/wMMgdFONG6F3ONvC+U5OhSLThq6fCqICRTgbctHm
NXMVdOGMyBAZ6EL9rqCok4qtH9xBklhjS5jtlMiAUMxph4a+hUKoWJYeIXb8rSvW
djy8HDfS7ajLxBFTeUr/F9E/ZjA/TNfXQd/V6PaTsJHTEcHqYoQMfN9+97ldw4ZL
H7U5AA66CkJ0XMuHKJ/I5rPd7iorl4v5hZ7pPdIrcAlKkIMajMgUUr7H9YHle+kK
HTlt75jb6pwViMUS0SAWtfoUbxvjKvngWjQw0QxbQtZN/Et/4wlTS6SUlJ02bkZn
dM51R1HNzTMPYDzpraG2Sk7M6YRpzTyG19sQI63QdgHtYTFj/G3kc1oXKa+p3zM8
csIZHPkxVghbEEq/K2nSG62h6jUPuBlAS3SzkCFGdvrRU3DBQrmlBJ0JkT6u5q3V
rH0xGuTQKVCiquBROCTIOugUAK5QD6n8omjdHx7Awc1ATfgX7e4=
=5ChJ
-END PGP SIGNATURE End Message ---

Bug#881149: marked as done (htslib FTBFS: test failures on i386)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 22:04:59 +
with message-id 
and subject line Bug#881149: fixed in htslib 1.5-4
has caused the Debian Bug report #881149,
regarding htslib FTBFS: test failures on i386
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.)


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

As per logs from reproducible builds [1], htslib 1.5-1 recently
(around 2017-09-25) started to FTBFS on i386 with the following test
failures:

test_vcf_api:
/build/1st/htslib-1.5/test/test-vcf-api /tmp/o6gEIzeYrS/test-vcf-api.bcf
bcf_get_format_float didn't produce the expected output.

.. failed ...

test_vcf_sweep:
/build/1st/htslib-1.5/test/test-vcf-sweep /tmp/o6gEIzeYrS/test-vcf-api.bcf

The outputs differ:
/build/1st/htslib-1.5/test/test-vcf-sweep.out
/build/1st/htslib-1.5/test/test-vcf-sweep.out.new
.. failed ...


[1] https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/htslib.html
--- End Message ---
--- Begin Message ---
Source: htslib
Source-Version: 1.5-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated htslib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 22:42:09 +0100
Source: htslib
Binary: libhts2 libhts-dev htslib-test tabix
Architecture: source
Version: 1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 htslib-test - Test data for HTSlib
 libhts-dev - Development files for the HTSlib
 libhts2- C library for high-throughput sequencing data formats
 tabix  - generic indexer for TAB-delimited genome position files
Closes: 881149
Changes:
 htslib (1.5-4) unstable; urgency=medium
 .
   * Fix build on i386 (Thanks to Graham Inggs )
 Closes: #881149
Checksums-Sha1:
 991542707caa494ab05a411f106923b1ff31930d 2272 htslib_1.5-4.dsc
 6775bb8aa5c4036430f18433e0a95f55d981bdd9 13832 htslib_1.5-4.debian.tar.xz
 86fd5558fb6b5df1d46d41d04465d7f37fde6f9e 7312 htslib_1.5-4_amd64.buildinfo
Checksums-Sha256:
 120a375f2b77b0a79833ff78b2880b69bc8474d948b887182f0f296ac2e00ae7 2272 
htslib_1.5-4.dsc
 e0a482530543679d16154987589122ba0b61978e146aac9a6dc0c9ae489b0119 13832 
htslib_1.5-4.debian.tar.xz
 2339bc2b8fb873aaba97c387c5098c62f0c143fda20b0d452cdbc5292ff7df1f 7312 
htslib_1.5-4_amd64.buildinfo
Files:
 736cab3470325c8f12989f65b5ccb254 2272 science optional htslib_1.5-4.dsc
 6a7fe425b093c577b85f00675a8acdb1 13832 science optional 
htslib_1.5-4.debian.tar.xz
 f743687a0c3bd13a550d330f41418964 7312 science optional 
htslib_1.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloTTOYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHXvA/+MwRHZYJOqoKlrvfbb6aGQWqd9OA2iG4n
G3LDE0z2D3kiFcSzVHJRap/XKUudP+IA024xj4YlKVwupSpXCj9eQ7SEVXY7MkaN
01NtCDCRPt/4SRqHxlu6vTPSTqOvYC5NgDWgbRsyBUZG3jgwpgaDgm8h6TTlvBJz
bRjo961b1tT2/WnVcEW23pEDw6tdtpHUhbpbSrZAMw3dEN42rlGNZr6qkNg7cP60
puuiMZLKxduqgKb0DaXg896d/Vy09S39hMrBiapSXN0CN6mHuj7RUD6LTjL9pLD9
IVG1/aOZprdRUj/MeK6stLCqmevMKm1j3Clxhf3WAhZ5nK8XmJag8/VHEWDIkLn9
914AM+z8B2STK2nxDsUb+RVMAosrueY2MS5zVTz5OB4IrtNyFGwjAejQ0tr3Wb0N
RDg1ylPdks5TpAIsjdCX0zmo29rqV2JpkOdq1cwOgoPrVZlQDk+kmdxd4tM4fqWH
hAHIOPyN8cYlTfSBN9MpGOxlPKpK4VgyXYBzN4CazhrYqTJR5+nJkIeEqupkLodC
WGmRAfsCfI00+gSGs1rbfWkX0RQhVePn13qCORw4U24mkRJ+AaWvX5IdaffTJ3c4
rMvImbOEGhYu85QfM/ctoFzk9uHJi9ov/+Yz9eimN6vcalZbWKfMafz1Z5JVuYO2
GKGYEsD+h4M=
=w99q
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#882261: Acknowledgement (rsyslog: imjournal doesn't work)

[Debian Bug Tracking System]

Processing control commands:

> found -1 8.30.0-1
Bug #882261 [rsyslog] rsyslog: imjournal doesn't work
There is no source info for the package 'rsyslog' at version '8.30.0-1' with 
architecture ''
Unable to make a source version for version '8.30.0-1'
Marked as found in versions 8.30.0-1.
> severity -1 serious
Bug #882261 [rsyslog] rsyslog: imjournal doesn't work
Severity set to 'serious' from 'important'
> tags -1 + patch
Bug #882261 [rsyslog] rsyslog: imjournal doesn't work
Added tag(s) patch.
> forwarded -1 https://github.com/rsyslog/rsyslog/issues/1897
Bug #882261 [rsyslog] rsyslog: imjournal doesn't work
Set Bug forwarded-to-address to 
'https://github.com/rsyslog/rsyslog/issues/1897'.

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

Bug#881368: fis-gtm: please switch build-dep from libconfig8-dev to libconfig-dev

[Andreas Tille]

Hi Mattia,

On Fri, Nov 10, 2017 at 09:09:16PM +0100, Mattia Rizzolo wrote:
> Version: 6.3-002-3
> Severity: serious
> 
> I'm about to upload a libconfig dropping this transitional package,
> please update fis-gtm.

Fis-gtm Build-Depends: libconfig-dev | libconfig8-dev.

In how far is it serious to drop the second alternative?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#880941: pink-pony: diff for NMU version 1.4.1-2.1

[Adrian Bunk]

Control: tags 880941 + patch
Control: tags 880941 + pending

Dear maintainer,

I've prepared an NMU for pink-pony (versioned as 1.4.1-2.1) and uploaded 
it to DELAYED/5. 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 pink-pony-1.4.1/debian/changelog pink-pony-1.4.1/debian/changelog
--- pink-pony-1.4.1/debian/changelog	2016-06-27 00:55:50.0 +0300
+++ pink-pony-1.4.1/debian/changelog	2017-11-20 23:39:25.0 +0200
@@ -1,3 +1,13 @@
+pink-pony (1.4.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove no longer required build dependency on glee-dev.
+(Closes: #880941)
+  * Stop using a non-default compressor
+(xz is now default, and it compresses better than bzip2).
+
+ -- Adrian Bunk   Mon, 20 Nov 2017 23:39:25 +0200
+
 pink-pony (1.4.1-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru pink-pony-1.4.1/debian/control pink-pony-1.4.1/debian/control
--- pink-pony-1.4.1/debian/control	2016-06-27 00:55:50.0 +0300
+++ pink-pony-1.4.1/debian/control	2017-11-20 23:39:20.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Debian Games Team 
 Uploaders: Miriam Ruiz 
 Build-Depends: debhelper (>= 9), quilt, scons, pkg-config, dh-buildinfo,
- mesa-common-dev, libglu1-mesa-dev, libglfw3-dev, libxrandr-dev, glee-dev,
+ mesa-common-dev, libglu1-mesa-dev, libglfw3-dev, libxrandr-dev,
  libilmbase-dev, libdevil-dev, libftgl-dev, libsigc++-2.0-dev,
  libprotobuf-dev (>= 2), protobuf-compiler (>= 2), libtinyxml-dev,
  libsdl1.2-dev, libsdl-mixer1.2-dev
diff -Nru pink-pony-1.4.1/debian/source/options pink-pony-1.4.1/debian/source/options
--- pink-pony-1.4.1/debian/source/options	2016-06-24 12:28:46.0 +0300
+++ pink-pony-1.4.1/debian/source/options	2017-11-20 23:39:25.0 +0200
@@ -1,5 +1,2 @@
-# Bzip2 compression for debian.tar
-compression = "bzip2"
-compression-level = 7
 # Do not generate diff for changes in config.(sub|guess)
 extend-diff-ignore = "(^|/)config.(sub|guess)$"

Processed: pink-pony: diff for NMU version 1.4.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 880941 + patch
Bug #880941 [src:pink-pony] pink-pony: Build-depends on glee-dev, but doesn't 
need it
Added tag(s) patch.
> tags 880941 + pending
Bug #880941 [src:pink-pony] pink-pony: Build-depends on glee-dev, but doesn't 
need it
Added tag(s) pending.

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

Bug#859826: marked as done (xca: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 21:44:10 +
with message-id 
and subject line Bug#859826: fixed in xca 1.4~pre1-1
has caused the Debian Bug report #859826,
regarding xca: Please migrate to openssl1.1 in Buster
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.)


-- 
859826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xca
Version: 1.3.2-2
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828604. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xca_1.3.2-1_amd64-20160529-1554

Sebastian
--- End Message ---
--- Begin Message ---
Source: xca
Source-Version: 1.4~pre1-1

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

Debian distribution maintenance software
pp.
Tino Mettler  (supplier of updated xca package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 21:28:27 +0100
Source: xca
Binary: xca
Architecture: source amd64
Version: 1.4~pre1-1
Distribution: unstable
Urgency: medium
Maintainer: Tino Mettler 
Changed-By: Tino Mettler 
Description:
 xca- x509 Certification Authority management tool based on QT4
Closes: 859826
Changes:
 xca (1.4~pre1-1) unstable; urgency=medium
 .
   * Switch to OpenSSL 1.1 (Closes: #859826)
   * Add 0001-Fix-further-spelling-errors-found-by-lintian-packge-.patch
 to fix new spelling errors found by lintian
   * Bump standards version, no changes needed
Checksums-Sha1:
 88adf684e7320ced26a09e0bcd48be886687cf12 1885 xca_1.4~pre1-1.dsc
 882f2fc35061d6fbd88682fc6ac81d4ec6fbe34a 902695 xca_1.4~pre1.orig.tar.gz
 8fb2be5fb34985059a9ade3fc23e6246f757b19e 6616 xca_1.4~pre1-1.debian.tar.xz
 443f25df99fc940fe660a0f623efb70e21b12e01 15445932 
xca-dbgsym_1.4~pre1-1_amd64.deb
 5b6a605dd659743b094981d318d070f1e6210652 11193 xca_1.4~pre1-1_amd64.buildinfo
 f705bd67528afb4c6734daa64cafc07e64e79c76 742268 xca_1.4~pre1-1_amd64.deb
Checksums-Sha256:
 38c05cd63c39713d5bdc1747ca91e9923cf112fd1cadce4b9cb7a426043cd6a2 1885 
xca_1.4~pre1-1.dsc
 10f91e032c4671479a93ae19f6b892700c17b92bf989a92ff444e5bcc95b070c 902695 
xca_1.4~pre1.orig.tar.gz
 7b32aa7fe47127bc406ba8f85ec69e3abbc47ecad02e0a34b380816c5122f4d6 6616 
xca_1.4~pre1-1.debian.tar.xz
 68b1dc8fdcc982bd9899ac0fb3f3ffb3e498a20597807d566d9bdc9ec4bc74a8 15445932 
xca-dbgsym_1.4~pre1-1_amd64.deb
 9dbff55ef0a6c70a3f4ffb623f6960edcafeb8edcb0c9ea2ddfb2af0d1ecda47 11193 
xca_1.4~pre1-1_amd64.buildinfo
 c3cb38e14257fd6c5f87caf6fb039ddb5007ab943b794211823780b9e6fe9fa2 742268 
xca_1.4~pre1-1_amd64.deb
Files:
 9813319b04e0ae5c3e55511f4fd99f91 1885 x11 optional xca_1.4~pre1-1.dsc
 dbaf00910f48f128fbf93c46dafc4999 902695 x11 optional xca_1.4~pre1.orig.tar.gz
 ba536a040a78fcc9f2ae85580e8faab8 6616 x11 optional xca_1.4~pre1-1.debian.tar.xz
 32dc1c1fb24ca73c7b337f9c33275d2a 15445932 debug optional 
xca-dbgsym_1.4~pre1-1_amd64.deb
 d5729bcd86be716458a0557d9f4d2c28 11193 x11 optional 
xca_1.4~pre1-1_amd64.buildinfo
 e9cd79bdd5b230673b42db7c2f215760 742268 x11 optional xca_1.4~pre1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEraWhGyuAVZbHjpBn6Abnf/ghVbwFAloTQTsVHHRpbm8rZGVi
aWFuQHRpa2VpLmRlAAoJEOgG53/4IVW8aOoP+gNau42OaYEWC1DXO5bGoYDwvhJA
LoDm90c8L7CSdBHAW/5Mm0FNah29tUdKP8r/T7LeqtpOw9D+NT1NjBHaxrU3Ud95
5+h4/WrxomibWTKU9brpCX8d/Cxmk2kZSm03JqmQrxQeEg5AJ4ajx3rXaG3UJ0pB
B0Ne0ANot+a+sGsTEu5/JGP786klNK68PmTRrBAFxgYgf3fNbsQf6q4Xj7VgqNCi
33RolhYbm4iviriRmceCG8NjkVCafaGZSyXaJLriM9z53LNLCn8LzTSKQCpnfPO+
SuFK7g9cmfvdk6KscRhdSGApO87U8YZgYltfm7trnEz29PB2OU4rZvdoHASfvt9D
Dib9PH8Rv7Q2UGp35l3uThGm7q/t2U5MGmYV6oTLCC+zFvfnGZctiBv32C3SzHWu
ABpj3OtPVIY7QDHRQrvx6ZnA8jzdw+mAWQgU01Fj5G+Xo9W24abz9whGqmobfUaO
iFvcrpE4UFk/4XXOGqB+7kAWa2DRIwvnRhVTaoamrVJbh7bj5gzJFFrKlKSSSrHu

Bug#882191: marked as done (ktuberling: file conflict with kde-l10n-ptbr: /usr/share/doc/HTML/pt_BR/ktuberling/index.cache.bz2)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 21:39:21 +
with message-id 
and subject line Bug#882191: fixed in kde-l10n 4:16.04.3-4
has caused the Debian Bug report #882191,
regarding ktuberling: file conflict with kde-l10n-ptbr: 
/usr/share/doc/HTML/pt_BR/ktuberling/index.cache.bz2
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.)


-- 
882191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ktuberling
Version: 4:17.08.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package ktuberling.
  Preparing to unpack .../329-ktuberling_4%3a17.08.3-2_amd64.deb ...
  Unpacking ktuberling (4:17.08.3-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-EIyn9C/329-ktuberling_4%3a17.08.3-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc/HTML/pt_BR/ktuberling/index.cache.bz2', 
which is also in package kde-l10n-ptbr 4:16.04.3-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-EIyn9C/329-ktuberling_4%3a17.08.3-2_amd64.deb

I'm filing only this one bug (because ktuberling is the only
package with a -2 revision and a changelog entry pointing
into the Breaks+Replaces direction),
but the problem affects many packages uploaded yesterday:

ark=4:17.08.3-1 kde-l10n-ptbr=4:16.04.3-3
blinken=4:17.08.3-1 kde-l10n-ptbr=4:16.04.3-3
bomber=4:17.08.3-1  kde-l10n-ptbr=4:16.04.3-3
bovo=4:17.08.3-1kde-l10n-ptbr=4:16.04.3-3
filelight=4:17.08.3-1   kde-l10n-ptbr=4:16.04.3-3
granatier=4:17.08.3-1   kde-l10n-ptbr=4:16.04.3-3
kapman=4:17.08.3-1  kde-l10n-ptbr=4:16.04.3-3
katomic=4:17.08.3-1 kde-l10n-ptbr=4:16.04.3-3
kblackbox=4:17.08.3-1   kde-l10n-ptbr=4:16.04.3-3
kblocks=4:17.08.3-1 kde-l10n-ptbr=4:16.04.3-3
kbounce=4:17.08.3-1 kde-l10n-ptbr=4:16.04.3-3
kbreakout=4:17.08.3-1   kde-l10n-ptbr=4:16.04.3-3

kde-l10n-ptbr=4:16.04.3-3   kdiamond=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kfourinline=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   khangman=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   killbots=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kiriki=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kjumpingcube=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   klettres-data=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   klickety=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   klines=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kmahjongg=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kmines=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   knavalbattle=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   knetwalk=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kollision=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kpat=4:17.08.3-2
kde-l10n-ptbr=4:16.04.3-3   kshisen=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   ksquares=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   ksystemlog=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   kteatime=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   ktuberling=4:17.08.3-2
kde-l10n-ptbr=4:16.04.3-3   lokalize=4:17.08.3-1
kde-l10n-ptbr=4:16.04.3-3   picmi=4:17.08.3-1

kde-l10n-sr=4:16.04.3-3 lokalize=4:17.08.3-1


cheers,

Andreas


kde-l10n-ptbr=4%16.04.3-3_ktuberling=4%17.08.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kde-l10n
Source-Version: 4:16.04.3-4

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kde-l10n 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)

Bug#882181: mockito: FTBFS - java.lang.UnsupportedOperationException: Cannot nest operations in the same thread

[Gilles Filippini]

Hi Markus,

Markus Koschany a écrit le 20/11/2017 à 21:17 :
> Control: tags -1 confirmed
> 
> Am 20.11.2017 um 00:27 schrieb Gilles Filippini:
>> Source: mockito
>> Version: 1.10.19-2
>> Severity: serious
>> Justification: FTBFS
>>
>> Hi,
>>
>> While testing a build of mockito against a new json-simple releae I've
>> experienced a FTBFS which is reproducible when building into a clean sid
>> chroot:
>>
>> Task :test class loader hash: 83f3637f6805a7b149525a93c5faad58
>> Task :test actions class loader hash: d883a18cf154fc57e90f4d3fa9e5588f
>> Executing task ':test' (up-to-date check took 0.041 secs) due to:
>>   No history is available.
>> Cannot nest operations in the same thread. Each nested operation must run in 
>> its own thread.
> 
> [...]
> 
> Hi,
> 
> thanks for reporting. This appears to be the same issue Olivier Sallou
> has mentioned on debian-java a few weeks ago. [1] This is a Gradle bug.
> I'm not exactly sure why it is surfacing now. I am in the process of
> updating Gradle to a newer version but it will take more time to finish
> the work.

I've just submitted another bug [1] against libgradle-core-java related
to the way it handles maven relocations.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882271

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-20 21:58, Mikulas Patocka wrote:
> 
> 
> On Mon, 20 Nov 2017, Samuel Thibault wrote:
> 
> > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > x86-64 libc in /lib64/). This package is not technically needed (because
> > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > installed nonetheless because of some dependencies.
> > 
> > The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> > tried to do it in the past, just to see, with the same kind of effect as
> > you had.
> > 
> > The question is rather how that got pulled at all. What package thinks
> > it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> > (which should normally not get pulled either), I can see uc-echo which
> > should rather use foreign dependencies, and :i386 multilib packages
> > which don't really make sense to install either.
> > 
> > I don't remember whether it was tried to make libc6-amd64:i386 conflict
> > with libc6:amd64 (and vice-versa for i386) to make sure that this
> > doesn't happen by misfortune?
> > 
> > Samuel
> 
> libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, lib64asan3, 
> lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, lib64itm1, 
> lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.
> 
> If you install gcc-7-multilib for non-default architecture (i386 or x32), 
> it will inevitably pull libc6-amd64.

What's the point of doing that, as opposed for example building with
-m32 or mx32?

> If we removed libc6-amd64 at all, it would cause problems building amd64 
> packages on i386 system. We could make those lib64* packages dependent on 
> libc6:amd64 instead, but that would break if the user has i386 
> installation and he doesn't have amd64 foreign architecture set up.
> 
> It would be best to set it up so that libc6-amd64 doesn't install any 
> files only if libc6:amd64 is present. Could it be done with the deb 
> format?

It's not something possible, and it's even more complicated than that.
The current ugly way the multiarch + multilib is done, uses a different
libc for linking and executing. So you definitely need to install both
if you want to be able to build and execute code.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: bug 882264 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=119731, tagging 882264

[Debian Bug Tracking System]

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

> forwarded 882264 https://rt.cpan.org/Ticket/Display.html?id=119731
Bug #882264 [src:libtemplate-declare-perl] libtemplate-declare-perl FTBFS with 
libhtml-lint-perl 2.26+dfsg-1
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=119731'.
> tags 882264 + confirmed
Bug #882264 [src:libtemplate-declare-perl] libtemplate-declare-perl FTBFS with 
libhtml-lint-perl 2.26+dfsg-1
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#882272: libc6:amd64: upgrade of libc6:amd64 + libc6:i386 + libc6-i686 breaks system

[Stepan Golosunov]

Package: libc6
Version: 2.24-11+deb9u1
Severity: critical
Justification: breaks the whole system


Upgrade of glibc packages from jessie to stretch versions failed
resulting in most programs (presumably all non-static 32-bit ones) to
segfault on start. I believe the following happend:
1. libc6:i386 and libc6:amd64 2.24-11+deb9u1 were unpacked,
/etc/ld.so.nohwcap was created by preinst scripts.
2. postinst of libc6:amd64 started running and removed
/etc/ld.so.nohwcap (as $hwcappkgs is empty for amd64).
3. As libc6-i686 2.19-18+deb8u10 was still installed most applications
started segfaulting (including most essential ones).

Unfortunately, I did not have any root shell open, and while
export LD_HWCAP_MASK=0
workaround worked on many applications, it had no effect on setuid
programs (like su and sudo). I had to resolve the problem by rebooting
system with break=init argument and running
touch /root/etc/ld.so.nohwcap
from initramfs shell (and later calling
dpkg --purge libc6-i686
before finishing upgrade of libc6:amd64).

This probably should be fixed by replacing

case ${DPKG_MAINTSCRIPT_ARCH} in
alpha)
hwcappkgs="libc6-alphaev67"
;;
i386)
hwcappkgs="libc6-i686 libc6-xen"
;;
kfreebsd-i386)
hwcappkgs="libc0.1-i686"
;;
esac

with something like

hwcappkgs="libc6-alphaev67 libc6-i686 libc6-xen libc0.1-i686"

or

hwcappkgs="libc6.1-alphaev67:alpha libc6-i686:i386 libc6-xen:i386 
libc0.1-i686:kfreebsd-i386"

in debian/script.in/nohwcap.sh.


sghpc% sudo apt upgrade
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Расчёт обновлений…Следующие пакеты устанавливались автоматически и больше не 
требуются:
  aumix aumix-common bzip2-doc gdb-doc libc6-i686 
linux-image-3.16.0-4-amd64:amd64 linux-image-4.9.0-3-amd64-dbg:amd64
  python-networkx python-pygraphviz python-skimage python-skimage-lib
Для их удаления используйте «apt-get autoremove».
Готово
НОВЫЕ пакеты, которые будут установлены:
  libc-l10n
Пакеты, которые будут оставлены в неизменном виде:
  geeqie geeqie-common geeqie-dbg
Пакеты, которые будут обновлены:
  glibc-doc libc-bin libc-dev-bin libc6 libc6:amd64 libc6-dbg libc6-dbg:amd64 
libc6-dev libc6-i686 locales locales-all
  multiarch-support
обновлено 12, установлено 1 новых пакетов, для удаления отмечено 0 пакетов, и 3 
пакетов не обновлено.
Необходимо скачать 0 B/44,6 MB архивов.
После данной операции, объём занятого дискового пространства уменьшится на 9 
642 kB.
Хотите продолжить? [Д/н] 
Чтение журнала изменений... Выполнено 
apt-listchanges: Хотите продолжить? [Y/n] 
apt-listchanges: Отправка почты root: apt-listchanges: журнал изменений sghpc
apt-listchanges: Отправка почты root: apt-listchanges: новости о sghpc
Предварительная настройка пакетов ...
(Чтение базы данных … на данный момент установлено 803482 файла и каталога.)
Подготовка к распаковке …/locales_2.24-11+deb9u1_all.deb …
Распаковывается locales (2.24-11+deb9u1) на замену (2.19-18+deb8u10) …
Выбор ранее не выбранного пакета libc-l10n.
Подготовка к распаковке …/libc-l10n_2.24-11+deb9u1_all.deb …
Распаковывается libc-l10n (2.24-11+deb9u1) …
Подготовка к распаковке …/locales-all_2.24-11+deb9u1_i386.deb …
Распаковывается locales-all (2.24-11+deb9u1) на замену (2.19-18+deb8u10) …
Подготовка к распаковке …/libc6_2.24-11+deb9u1_i386.deb …
Деконфигурируется libc6:amd64 (2.19-18+deb8u10) …
Checking for services that may need to be restarted...
Checking init 
scripts...##.]
 
Распаковывается libc6:i386 (2.24-11+deb9u1) на замену (2.19-18+deb8u10) …
Подготовка к распаковке …/libc6_2.24-11+deb9u1_amd64.deb 
….] 
Checking for services that may need to be 
restarted]
 
Checking init scripts...
Распаковывается libc6:amd64 (2.24-11+deb9u1) на замену (2.19-18+deb8u10) …
Настраивается пакет libc6:amd64 (2.24-11+deb9u1) 
….] 
dpkg: ошибка при обработке пакета libc6:amd64 
(--configure):...] 
 подпроцесс установлен сценарий post-installation уничтожен по сигналу (Ошибка 
сегментирования)
Настраивается пакет libc6:i386 (2.24-11+deb9u1) …
Устанавливается новая версия файла настройки 
/etc/ld.so.conf.d/i386-linux-gnu.conf …
dpkg: ошибка при обработке пакета libc6:i386 
(--configure):] 
 подпроцесс установлен сценарий post-installation уничтожен по сигналу (Ошибка 
сегментирования)
При обработке следующих пакетов произошли ошибки:
 libc6:amd64
 libc6:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Problem executing scripts DPkg::Post-Invoke 

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

On Mon, 20 Nov 2017, Samuel Thibault wrote:

> Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > installed nonetheless because of some dependencies.
> 
> The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> tried to do it in the past, just to see, with the same kind of effect as
> you had.
> 
> The question is rather how that got pulled at all. What package thinks
> it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> (which should normally not get pulled either), I can see uc-echo which
> should rather use foreign dependencies, and :i386 multilib packages
> which don't really make sense to install either.
> 
> I don't remember whether it was tried to make libc6-amd64:i386 conflict
> with libc6:amd64 (and vice-versa for i386) to make sure that this
> doesn't happen by misfortune?
> 
> Samuel

libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, lib64asan3, 
lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, lib64itm1, 
lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.

If you install gcc-7-multilib for non-default architecture (i386 or x32), 
it will inevitably pull libc6-amd64.

If we removed libc6-amd64 at all, it would cause problems building amd64 
packages on i386 system. We could make those lib64* packages dependent on 
libc6:amd64 instead, but that would break if the user has i386 
installation and he doesn't have amd64 foreign architecture set up.

It would be best to set it up so that libc6-amd64 doesn't install any 
files only if libc6:amd64 is present. Could it be done with the deb 
format?

Mikulas

Processed: unmerging 882269, reassign 882269 to src:kde-l10n

[Debian Bug Tracking System]

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

> unmerge 882269
Bug #882269 [src:kde-l10n] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Bug #882191 [src:kde-l10n] ktuberling: file conflict with kde-l10n-ptbr: 
/usr/share/doc/HTML/pt_BR/ktuberling/index.cache.bz2
Disconnected #882269 from all other report(s).
> reassign 882269 src:kde-l10n kde-l10n/4:17.08.3-1
Bug #882269 [src:kde-l10n] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Ignoring request to reassign bug #882269 to the same package
Bug #882269 [src:kde-l10n] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Marked as found in versions kde-l10n/4:17.08.3-1; no longer marked as found in 
versions kde-l10n/4:16.04.3-3.
> thanks
Stopping processing here.

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

Bug#874295: clementine: installs non-free plugin at runtime

[Jonas Smedegaard]

Quoting Anthony DeRobertis (2017-11-20 21:08:18)
> [resending just to -submitter, sorry I messed up the address the first
> time.]
>
> (from Jonas Smedegaard  via the bug):
>
>> One of several functions of Clementine is to stream audio from cloud 
>> service Spotify.  Initially selecting that function triggers a 
>> routine where Clementine (asks for concent and then) downloads and 
>> installs a non-free binary driver.
>>
>> Policy 2.2.1 states that "None of the packages in the main archive 
>> area require software outside of that area to function."
>>
>> Clementine should either be moved to contrib, or the Spotify function 
>> be removed.
>
> I suggest this isn't a Policy violation. Clementine functions without 
> the Spotify plugin; e.g., it'll happily play local music files, or 
> from any of the non-Spotify streaming sources.

Yes, and this bugreport is only about the Spotify option: As I wrote 
just above this bug is resolved if the Spotify function is removed.


> Compare to, for example, all web browsers except lynx (and similar). 
> They all happily and automatically download and execute non-free code 
> (JavaScript), without any warning whatsoever. And if you turn off 
> JavaScript, they lose quite a bit more functionality than Clementine 
> does (I'd go so far as to say they become fairly useless — quite a bit 
> of the web doesn't work w/o JavaScript).

None of our geeral-purpose web browsers "require software outside of 
[the main archive] to function" as general-purpose web browsers.


> Many of them have their own plugin services (at least both Firefox and 
> Chromium do) that happily install and execute non-free code, again 
> without any warning (the only warnings they give are about access to 
> data, browsing history, etc., nothing about freedom).

I agree that some web browser addons are problematic too.  But the 
mechanism in the browsers is not specific to non-free code and therefore 
do not "_require_ software outside [the main archive] to function".


> Further, Debian understands software broadly (including, e.g., 
> data—basically, "not hardware"), not just executables. If this bug 
> report's reading of policy were correct, Clementine would need to 
> disable most of streaming music services as the music they provide 
> doesn't follow DFSG. (And even lynx would have to be removed.)

Protocols only able to access non-free services would indeed need to be 
removed, I believe.  But protocols able to access either free or 
non-free resources are fine.

Existence of additional DFSG violations is not an argument that this is 
not a DFSG violation.


> I think it'd be reasonable to make the confirmation dialog explicitly 
> say that the plugin is not free software. But other than that, which 
> does not warrant severity: serious, I think this bug should be closed 
> as not a bug.

I disagree.


 - Jonas

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

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

Processed: reassign 882269 to src:kde-l10n, forcibly merging 882191 882269

[Debian Bug Tracking System]

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

> reassign 882269 src:kde-l10n kde-l10n/4:16.04.3-3
Bug #882269 [kde-l10n-de] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Bug reassigned from package 'kde-l10n-de' to 'src:kde-l10n'.
No longer marked as found in versions kde-l10n/4:17.08.3-1.
Ignoring request to alter fixed versions of bug #882269 to the same values 
previously set
Bug #882269 [src:kde-l10n] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Marked as found in versions kde-l10n/4:16.04.3-3.
> forcemerge 882191 882269
Bug #882191 [src:kde-l10n] ktuberling: file conflict with kde-l10n-ptbr: 
/usr/share/doc/HTML/pt_BR/ktuberling/index.cache.bz2
Bug #882269 [src:kde-l10n] kde-l10n-de: Ohter application cause conflict with 
version old than 4:17.08.3-1
Severity set to 'serious' from 'normal'
Added tag(s) pending.
Merged 882191 882269
> thanks
Stopping processing here.

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

Bug#881764: marked as done (openjdk-7: several vulnerabilities)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 21:10:54 +
with message-id 
and subject line Bug#881764: fixed in openjdk-7 7u151-2.6.11-2
has caused the Debian Bug report #881764,
regarding openjdk-7: several vulnerabilities
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.)


-- 
881764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-7
Version: 7u151-2.6.11-1
Severity: serious

Hi,

The last round of vulnerabilities for OpenJDK hasn't been fixed in openjdk-7
yet. It'd be good to get an updated package in experimental so it can be
pushed to jessie and wheezy.

Thanks,
Emilio

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: openjdk-7
Source-Version: 7u151-2.6.11-2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-7 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, 20 Nov 2017 21:24:32 +0100
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib 
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-jamvm 
openjdk-7-jre-zero
Architecture: source
Version: 7u151-2.6.11-2
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
 openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-7-jdk - OpenJDK Development Kit (JDK)
 openjdk-7-jre - OpenJDK Java runtime, using
 openjdk-7-jre-headless - OpenJDK Java runtime, using  (headless)
 openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
 openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 881764
Changes:
 openjdk-7 (7u151-2.6.11-2) experimental; urgency=medium
 .
   [ Tiago Stürmer Daitx ]
   * Backport of 8u151 security fixes. Closes: #881764.
   * Security patches:
 - CVE-2017-10274, S8169026: Handle smartcard clean up better. If a
   CardImpl can be recovered via finalization, then separate instances
   pointing to the same device can be created.
 - CVE-2017-10281, S8174109: Better queuing priorities. PriorityQueue's
   readObject allocates an array based on data in the stream which could
   cause an OOM.
 - CVE-2017-10285, S8174966: Unreferenced references. RMI's Unreferenced
   thread can be used as the root of a Trusted Method Chain.
 - CVE-2017-10295, S8176751: Better URL connections. On Ubuntu (and
   possibly other Linux flavors) CR-NL in the host field are ignored and
   can be used to inject headers in an HTTP request stream.
 - CVE-2017-10388, S8178794: Correct Kerberos ticket grants. Kerberos
   implementations can incorrectly take information from the unencrypted
   portion of the ticket from the KDC. This can lead to an MITM attack
   impersonating Kerberos services.
 - CVE-2017-10346, S8180711: Better alignment of special invocations. A
   missing load constraint for some invokespecial cases can allow invoking
   a method from an unrelated class.
 - CVE-2017-10350, S8181100: Better Base Exceptions. An array is allocated

Bug#877206: marked as done (foolscap FTBFS with twisted 17.9.0)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 21:04:56 +
with message-id 
and subject line Bug#877206: fixed in foolscap 0.13.0-1
has caused the Debian Bug report #877206,
regarding foolscap FTBFS with twisted 17.9.0
to be marked as done.

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

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


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

https://ci.debian.net/packages/f/foolscap/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/foolscap.html

...
===
[FAIL]
Traceback (most recent call last):
  File 
"/build/1st/foolscap-0.12.6/debian/python-foolscap/usr/lib/python2.7/dist-packages/foolscap/test/test_logging.py",
 line 1319, in _check_gatherer
self.failUnlessEqual(len(events), 4)
  File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 432, 
in assertEqual
super(_Assertions, self).assertEqual(first, second, msg)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
twisted.trial.unittest.FailTest: 2 != 4

foolscap.test.test_logging.Gatherer.test_log_gatherer
foolscap.test.test_logging.Gatherer.test_log_gatherer2
foolscap.test.test_logging.Gatherer.test_log_gatherer_furlfile
foolscap.test.test_logging.Gatherer.test_log_gatherer_furlfile2
foolscap.test.test_logging.Gatherer.test_log_gatherer_furlfile_multiple
foolscap.test.test_logging.Gatherer.test_log_gatherer_multiple
===
[FAIL]
Traceback (most recent call last):
  File 
"/build/1st/foolscap-0.12.6/debian/python-foolscap/usr/lib/python2.7/dist-packages/foolscap/test/test_logging.py",
 line 460, in _check
self.failUnlessEqual(len(files), 1)
  File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 432, 
in assertEqual
super(_Assertions, self).assertEqual(first, second, msg)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
twisted.trial.unittest.FailTest: 0 != 1

foolscap.test.test_logging.Incidents.test_classify
===
[FAIL]
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1386, 
in _inlineCallbacks
result = g.send(result)
  File 
"/build/1st/foolscap-0.12.6/debian/python-foolscap/usr/lib/python2.7/dist-packages/foolscap/test/test_logging.py",
 line 2193, in test_basic
self.failUnless("4 events covering" in page)
  File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 395, 
in assertTrue
super(_Assertions, self).assertTrue(condition, msg)
  File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
raise self.failureException(msg)
twisted.trial.unittest.FailTest: False is not true

foolscap.test.test_logging.Web.test_basic
===
[ERROR]
Traceback (most recent call last):
  File 
"/build/1st/foolscap-0.12.6/debian/python-foolscap/usr/lib/python2.7/dist-packages/foolscap/test/test_copyable.py",
 line 138, in _testFailure1_1
p = pickle.dumps(f)
  File "/usr/lib/python2.7/pickle.py", line 1380, in dumps
Pickler(file, protocol).dump(obj)
  File "/usr/lib/python2.7/pickle.py", line 224, in dump
self.save(obj)
  File "/usr/lib/python2.7/pickle.py", line 331, in save
self.save_reduce(obj=obj, *rv)
  File "/usr/lib/python2.7/pickle.py", line 425, in save_reduce
save(state)
  File "/usr/lib/python2.7/pickle.py", line 286, in save
f(self, obj) # Call unbound method with explicit self
  File "/usr/lib/python2.7/pickle.py", line 655, in save_dict
self._batch_setitems(obj.iteritems())
  File "/usr/lib/python2.7/pickle.py", line 669, in _batch_setitems
save(v)
  File "/usr/lib/python2.7/pickle.py", line 286, in save
f(self, obj) # Call unbound method with explicit self
  File "/usr/lib/python2.7/pickle.py", line 759, in save_global
(obj, module, name))
pickle.PicklingError: Can't pickle : it's not the same object as exceptions.RuntimeError

Bug#882268: networking-ovs-dpdk FTBFS: AttributeError: 'module' object has no attribute 'VIF_TYPE_VHOST_USER'

[Adrian Bunk]

Source: networking-ovs-dpdk
Version: 2015.1.1+git20151118.35ac4c7-1
Severity: serious

Some recent change in unstable makes networking-ovs-dpdk FTBFS:

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

...
==
FAIL: 
unittest2.loader._FailedTest.networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
unittest2.loader._FailedTest.networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovs_dpdk/tests/unit/driver/test_mech_dpdk_ovs.py", line 27, 
in 
class OVSDPDKMechanismBaseTestCase(base.AgentMechanismBaseTestCase):
  File "networking_ovs_dpdk/tests/unit/driver/test_mech_dpdk_ovs.py", line 28, 
in OVSDPDKMechanismBaseTestCase
VIF_TYPE = portbindings.VIF_TYPE_VHOST_USER
AttributeError: 'module' object has no attribute 'VIF_TYPE_VHOST_USER'


--
Ran 1 test in 3.646s

FAILED (failures=1)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#882267: php-mockery FTBFS: Class 'DOMDocument' not found

[Adrian Bunk]

Source: php-mockery
Version: 0.9.5-1
Severity: serious
Tags: buster sid

Some recent change in unstable (PHP 7.1?) makes php-mockery FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-mockery-0.9.5'
phpunit --include-path library --bootstrap debian/bootstrap.php
Class 'DOMDocument' not found
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#882266: horizon accesses the internet during the build

[Adrian Bunk]

Source: horizon
Version: 3:12.0.0-4
Severity: serious

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

...
==
ERROR: Failure: ConnectionError 
(HTTPSConnectionPool(host='translate.openstack.org', port=443): Max retries 
exceeded with url: /rest/project/horizon/version/master/locales (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary 
failure in name resolution',)))
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/build/1st/horizon-12.0.0/horizon/management/commands/pull_catalog.py", 
line 21, in 
ZANATA_LOCALES = requests.get("https://translate.openstack.org/rest/project;
  File "/usr/lib/python2.7/dist-packages/requests/api.py", line 72, in get
return request('get', url, params=params, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/api.py", line 58, in request
return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 502, in 
request
resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 612, in 
send
r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 504, in 
send
raise ConnectionError(e, request=request)
ConnectionError: HTTPSConnectionPool(host='translate.openstack.org', port=443): 
Max retries exceeded with url: /rest/project/horizon/version/master/locales 
(Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] 
Temporary failure in name resolution',))

--
Ran 209 tests in 66.346s

FAILED (SKIP=7, errors=1)
...

Processed: reassign 882223 to glibc-doc

[Debian Bug Tracking System]

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

> # match possible intention of reporter
> reassign 882223 glibc-doc
Bug #882223 [manpages-dev] Document security problems with system.3 and popen.3 
(argument injection)
Bug reassigned from package 'manpages-dev' to 'glibc-doc'.
No longer marked as found in versions manpages/4.13-3.
Ignoring request to alter fixed versions of bug #882223 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#874295: clementine: installs non-free plugin at runtime

[Anthony DeRobertis]

(from Jonas Smedegaard  via the bug):

> One of several functions of Clementine is to stream audio from cloud
> service Spotify.  Initially selecting that function triggers a routine
> where Clementine (asks for concent and then) downloads and installs a
> non-free binary driver.
> 
> Policy 2.2.1 states that "None of the packages in the main archive area
> require software outside of that area to function."
> 
> Clementine should either be moved to contrib, or the Spotify function be
> removed.

I suggest this isn't a Policy violation. Clementine functions without
the Spotify plugin; e.g., it'll happily play local music files, or from
any of the non-Spotify streaming sources.

Compare to, for example, all web browsers except lynx (and similar).
They all happily and automatically download and execute non-free code
(JavaScript), without any warning whatsoever. And if you turn off
JavaScript, they lose quite a bit more functionality than Clementine
does (I'd go so far as to say they become fairly useless — quite a bit
of the web doesn't work w/o JavaScript).

Many of them have their own plugin services (at least both Firefox and
Chromium do) that happily install and execute non-free code, again
without any warning (the only warnings they give are about access to
data, browsing history, etc., nothing about freedom).

Further, Debian understands software broadly (including, e.g.,
data—basically, "not hardware"), not just executables. If this bug
report's reading of policy were correct, Clementine would need to
disable most of streaming music services as the music they provide
doesn't follow DFSG. (And even lynx would have to be removed.)

I think it'd be reasonable to make the confirmation dialog explicitly
say that the plugin is not free software. But other than that, which
does not warrant severity: serious, I think this bug should be closed as
not a bug.

Bug#874295: clementine: installs non-free plugin at runtime

[Anthony DeRobertis]

[resending just to -submitter, sorry I messed up the address the first
time.]

(from Jonas Smedegaard  via the bug):

> One of several functions of Clementine is to stream audio from cloud
> service Spotify.  Initially selecting that function triggers a routine
> where Clementine (asks for concent and then) downloads and installs a
> non-free binary driver.
> 
> Policy 2.2.1 states that "None of the packages in the main archive area
> require software outside of that area to function."
> 
> Clementine should either be moved to contrib, or the Spotify function be
> removed.

I suggest this isn't a Policy violation. Clementine functions without
the Spotify plugin; e.g., it'll happily play local music files, or from
any of the non-Spotify streaming sources.

Compare to, for example, all web browsers except lynx (and similar).
They all happily and automatically download and execute non-free code
(JavaScript), without any warning whatsoever. And if you turn off
JavaScript, they lose quite a bit more functionality than Clementine
does (I'd go so far as to say they become fairly useless — quite a bit
of the web doesn't work w/o JavaScript).

Many of them have their own plugin services (at least both Firefox and
Chromium do) that happily install and execute non-free code, again
without any warning (the only warnings they give are about access to
data, browsing history, etc., nothing about freedom).

Further, Debian understands software broadly (including, e.g.,
data—basically, "not hardware"), not just executables. If this bug
report's reading of policy were correct, Clementine would need to
disable most of streaming music services as the music they provide
doesn't follow DFSG. (And even lynx would have to be removed.)

I think it'd be reasonable to make the confirmation dialog explicitly
say that the plugin is not free software. But other than that, which
does not warrant severity: serious, I think this bug should be closed as
not a bug.

Bug#882264: libtemplate-declare-perl FTBFS with libhtml-lint-perl 2.26+dfsg-1

[Adrian Bunk]

Source: libtemplate-declare-perl
Version: 0.47-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libtemplate-declare-perl.html

...
Test Summary Report
---
t/aliasing.t  (Wstat: 1280 Tests: 30 Failed: 5)
  Failed tests:  11, 16, 21, 26, 30
  Non-zero exit status: 5
t/arg-declaration-styles.t (Wstat: 2048 Tests: 39 Failed: 8)
  Failed tests:  3, 6, 9, 15, 21, 27, 33, 39
  Non-zero exit status: 8
t/attributes.t(Wstat: 1280 Tests: 10 Failed: 5)
  Failed tests:  2, 4, 6, 8, 10
  Non-zero exit status: 5
t/closures.t  (Wstat: 2048 Tests: 16 Failed: 8)
  Failed tests:  2, 4, 6, 8, 10, 12, 14, 16
  Non-zero exit status: 8
t/forms.t (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/importing.t (Wstat: 512 Tests: 18 Failed: 2)
  Failed tests:  14, 18
  Non-zero exit status: 2
t/indexhtml.t (Wstat: 512 Tests: 4 Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
t/mixing.t(Wstat: 1280 Tests: 30 Failed: 5)
  Failed tests:  11, 16, 21, 26, 30
  Non-zero exit status: 5
t/private.t   (Wstat: 1024 Tests: 14 Failed: 4)
  Failed tests:  3, 6, 9, 12
  Non-zero exit status: 4
t/self.t  (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  3
  Non-zero exit status: 1
t/siblings.t  (Wstat: 768 Tests: 7 Failed: 3)
  Failed tests:  2, 4, 7
  Non-zero exit status: 3
t/subclassing.t   (Wstat: 768 Tests: 11 Failed: 3)
  Failed tests:  3, 5, 11
  Non-zero exit status: 3
t/subtemplates.t  (Wstat: 1024 Tests: 9 Failed: 4)
  Failed tests:  2, 4, 6, 9
  Non-zero exit status: 4
t/trivial.t   (Wstat: 1024 Tests: 9 Failed: 4)
  Failed tests:  2, 4, 6, 9
  Non-zero exit status: 4
t/utf8.t  (Wstat: 1536 Tests: 12 Failed: 6)
  Failed tests:  2, 4, 6, 8, 10, 12
  Non-zero exit status: 6
t/xss.t   (Wstat: 1024 Tests: 8 Failed: 4)
  Failed tests:  2, 4, 6, 8
  Non-zero exit status: 4
Files=51, Tests=478, 12 wallclock secs ( 0.23 usr  0.15 sys +  6.65 cusr  0.71 
csys =  7.74 CPU)
Result: FAIL
Failed 16/51 test programs. 65/478 subtests failed.
Makefile:786: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 4

Bug#882263: libc6-dev-mips64el-cross breaks linking executables

[Helmut Grohne]

Package: libc6-dev-mips64el-cross
Version: 20
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I was trying to use gcc-mips64el-linux-gnuabi64 to link a trivial
executable:

$ echo 'int main(){return 0;}' | mips64el-linux-gnuabi64-gcc -x c - -o /dev/null

With libc6-dev:mips64el installed, this just works. As soon as I install
libc6-dev-mips64el-cross, it fails though:

/usr/lib/gcc-cross/mips64el-linux-gnuabi64/7/../../../../mips64el-linux-gnuabi64/bin/ld:
 cannot find /usr/mips64el-linux-gnuabi64/lib/ld.so.1
collect2: error: ld returned 1 exit status

This renders libc6-dev-mips64el-cross pretty much useless.

Helmut

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-20 20:47, Samuel Thibault wrote:
> Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > x86-64 libc in /lib64/). This package is not technically needed (because
> > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > installed nonetheless because of some dependencies.
> 
> The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> tried to do it in the past, just to see, with the same kind of effect as
> you had.
> 
> The question is rather how that got pulled at all. What package thinks
> it's a good idea to pull libc6-amd64?  Apart from libc64* packages
> (which should normally not get pulled either), I can see uc-echo which
> should rather use foreign dependencies, and :i386 multilib packages
> which don't really make sense to install either.
> 
> I don't remember whether it was tried to make libc6-amd64:i386 conflict
> with libc6:amd64 (and vice-versa for i386) to make sure that this
> doesn't happen by misfortune?

Arch-qualified conflicts are not supported. What you can do is make
libc6-amd64 and libc6:amd64 not coinstallable (by changing the Replaces
into a Conflicts). Maybe it's time to do it and let GCC enjoy multiarch
+ multilib pain.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> found 873414 4.3.1-1
Bug #873414 [src:qtcreator] qtcreator: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Marked as found in versions qtcreator/4.3.1-1.
> found 873417 0.13-9
Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
Marked as found in versions pocl/0.13-9.
> found 873408 0.4.7-7
Bug #873408 [src:julia] julia: Please update to llvm-toolchain 4.0 or, better, 
5.0
Marked as found in versions julia/0.4.7-7.
> thanks
Stopping processing here.

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

Processed: tagging 790204

[Debian Bug Tracking System]

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

> tags 790204 + pending
Bug #790204 [src:gnucash] gnucash: depends on libwebkitgtk-1.0-0 which is 
deprecated
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882181: mockito: FTBFS - java.lang.UnsupportedOperationException: Cannot nest operations in the same thread

[Markus Koschany]

Control: tags -1 confirmed

Am 20.11.2017 um 00:27 schrieb Gilles Filippini:
> Source: mockito
> Version: 1.10.19-2
> Severity: serious
> Justification: FTBFS
> 
> Hi,
> 
> While testing a build of mockito against a new json-simple releae I've
> experienced a FTBFS which is reproducible when building into a clean sid
> chroot:
> 
> Task :test class loader hash: 83f3637f6805a7b149525a93c5faad58
> Task :test actions class loader hash: d883a18cf154fc57e90f4d3fa9e5588f
> Executing task ':test' (up-to-date check took 0.041 secs) due to:
>   No history is available.
> Cannot nest operations in the same thread. Each nested operation must run in 
> its own thread.

[...]

Hi,

thanks for reporting. This appears to be the same issue Olivier Sallou
has mentioned on debian-java a few weeks ago. [1] This is a Gradle bug.
I'm not exactly sure why it is surfacing now. I am in the process of
updating Gradle to a newer version but it will take more time to finish
the work.

Regards,

Markus

[1] https://lists.debian.org/debian-java/2017/10/msg00078.html



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#882181: mockito: FTBFS - java.lang.UnsupportedOperationException: Cannot nest operations in the same thread

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #882181 [src:mockito] mockito: FTBFS - 
java.lang.UnsupportedOperationException: Cannot nest operations in the same 
thread
Added tag(s) confirmed.

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

Processed: Bug#882173 marked as pending

[Debian Bug Tracking System]

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

> tag 882173 pending
Bug #882173 [src:audacity] audacity: FTBFS on !x86 and baseline violation on 
i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882173: marked as pending

[Jaromír Mikeš]

tag 882173 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/audacity.git/commit/?id=9464548

---
commit 9464548bfc7fd10c10198d5bdfd007bc743f122e
Author: Jaromír Mikeš 
Date:   Mon Nov 20 21:08:35 2017 +0100

Start new upload.

diff --git a/debian/changelog b/debian/changelog
index d6bcb89..84ceb5e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+audacity (2.2.0-2) UNRELEASED; urgency=medium
+
+  * Build without sbsms to fix FTBFS on non-x86 archs. (Closes: #882173)
+
+ -- Jaromír Mikeš   Mon, 20 Nov 2017 21:08:16 +0100
+
 audacity (2.2.0-1) unstable; urgency=medium
 
   [ Sebastian Ramacher ]

Processed: found 882255 in 2.24-1

[Debian Bug Tracking System]

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

> found 882255 2.24-1
Bug #882255 [libc6-amd64] libc6-amd64: Multilib causes catastrophic system 
failure during upgrade to libc 2.25
Marked as found in versions glibc/2.24-1.
> thanks
Stopping processing here.

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

Bug#881149: htslib FTBFS: test failures on i386

[Graham Inggs]

Control: tags -1 + patch

I found the documentation of the optimization flags for GCC 7.2.0 [1].
I was then able to bisect the list of flags enabled for -O2 and
determine which ones needed to be disabled in order to build htslib on
i386.  Patch follows.

--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,9 @@

 include /usr/share/dpkg/default.mk

-export DEB_CFLAGS_MAINT_APPEND = -fno-strict-aliasing
+ifneq (,$(filter $(DEB_HOST_ARCH),i386))
+  export DEB_CFLAGS_MAINT_APPEND=-fno-strict-aliasing -fno-code-hoisting
+endif

 %:


[1] https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Optimize-Options.html

Processed: Re: Bug#881149: htslib FTBFS: test failures on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #881149 [src:htslib] htslib FTBFS: test failures on i386
Added tag(s) patch.

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

Bug#882260: neutron-lbaas FTBFS: testtools.matchers._impl.MismatchError: 'www.hostfromdnsname1.com' != u'www.hostFromDNSName1.com'

[Adrian Bunk]

Source: neutron-lbaas
Version: 1:11.0.1-1
Severity: serious

Some recent change in unstable makes neutron-lbaas FTBFS:

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

...
==
FAIL: 
neutron_lbaas.tests.unit.common.tls_utils.test_cert_parser.TestTLSParseUtils.test_alt_subject_name_parses
neutron_lbaas.tests.unit.common.tls_utils.test_cert_parser.TestTLSParseUtils.test_alt_subject_name_parses
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutron/tests/base.py", line 118, in 
func
return f(self, *args, **kwargs)
  File "neutron_lbaas/tests/unit/common/tls_utils/test_cert_parser.py", line 
243, in test_alt_subject_name_parses
self.assertEqual('www.hostfromdnsname1.com', hosts['dns_names'][0])
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 'www.hostfromdnsname1.com' != 
u'www.hostFromDNSName1.com'


--
Ran 544 tests in 264.046s

FAILED (failures=1)
debian/rules:41: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: severity of 882258 is important, tagging 882258

[Debian Bug Tracking System]

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

> severity 882258 important
Bug #882258 [src:busybox] busybox: CVE-2017-16544: lineedit: do not 
tab-complete any strings which have control characters
Severity set to 'important' from 'grave'
> tags 882258 + upstream fixed-upstream
Bug #882258 [src:busybox] busybox: CVE-2017-16544: lineedit: do not 
tab-complete any strings which have control characters
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Samuel Thibault]

Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> x86-64 libc in /lib64/). This package is not technically needed (because
> x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> installed nonetheless because of some dependencies.

The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
tried to do it in the past, just to see, with the same kind of effect as
you had.

The question is rather how that got pulled at all. What package thinks
it's a good idea to pull libc6-amd64?  Apart from libc64* packages
(which should normally not get pulled either), I can see uc-echo which
should rather use foreign dependencies, and :i386 multilib packages
which don't really make sense to install either.

I don't remember whether it was tried to make libc6-amd64:i386 conflict
with libc6:amd64 (and vice-versa for i386) to make sure that this
doesn't happen by misfortune?

Samuel

Bug#882258: busybox: CVE-2017-16544: lineedit: do not tab-complete any strings which have control characters

[Salvatore Bonaccorso]

Source: busybox
Version: 1:1.27.2-1
Severity: grave
Tags: security

Hi,

the following vulnerability was published for busybox. I realize you
know of the issue already but just filling to have a tracking bug as
well in the BTS.

CVE-2017-16544[0]:
| In the add_match function in libbb/lineedit.c in BusyBox through
| 1.27.2, the tab autocomplete feature of the shell, used to get a list
| of filenames in a directory, does not sanitize filenames and results in
| executing any escape sequence in the terminal. This could potentially
| result in code execution, arbitrary file writes, or other attacks.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16544
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16544
[1] 
https://git.busybox.net/busybox/commit/?id=c3797d40a1c57352192c6106cc0f435e7d9c11e8

Please adjust the affected versions in the BTS as needed, only
unstable checked so far.

Regards,
Salvatore

Processed: Re: Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #873411 [src:kdevelop] kdevelop: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'important' from 'serious'

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

Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Pino Toscano]

Control: severity -1 important

(see below why...)

In data lunedì 20 novembre 2017 20:05:20 CET, Emilio Pozuelo Monfort ha scritto:
> Control: severity -1 serious
> 
> On Wed, 06 Sep 2017 21:34:47 +0200 Pino Toscano  wrote:
> > Hi,
> > 
> > In data domenica 27 agosto 2017 16:01:25 CEST, Sylvestre Ledru ha scritto:
> > > Source: kdevelop
> > > Severity: normal
> > > 
> > > Hello,
> > > 
> > > Currently, we have 6 versions of the llvm toolchain in the archive.
> > > I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)
> > > 
> > > Could you please update your package to use 4.0 (or, better, 5.0 which 
> > > will be released very 
> > > soon)?
> > 
> > Sure, but only after the versions available build and work at least on
> > all the release architectures.  So far, llvm 3.9 is still affected by
> > #866354, since it did not build fine again since then -- this is
> > holding kdevelop in unstable for more than 2 months, and I really would
> > like to get it into testing.
> > 
> > I see that each of the llvm sources has various bugs, FTBFSes, cmake
> > issues, and so forth... as a suggestion from a bystander, what about
> > focusing on at most 3 versions of llvm in the archive, instead of
> > upload every version available (and then have to cleanup llvm users
> > periodically, like with bugs like this)?
> > 
> > > I will update the severity of this bug at the end of September
> > 
> > Doing that with the current state of llvm versions would be a bad idea.
> 
> It should be fine now with 4.0. Would be good if this could move to either
> unversioned llvm/clang (which defaults to 4.0 now) or to versioned 4.0. 
> Bumping
> to serious as we want to remove 3.8 soon to reduce the high number of llvm
> versions that we currently ship.

IMHO, if the goal would really be getting rid of old llvm versions in
the archive, then (as I wrote above) the llvm maintainers ought to
a) fix the latest stable (= 5.0)
b) switch llvm-defaults to the above

llvm got versioned symbols, so loading two llvm versions in the same
process (hello, mesa), although it is ugly. This should allow kdevelop
to switch back to llvm-defaults, even if llvm maintainers should care
a bit more about it, instead of almost letting it rot...

Anyway, I just lowered the severity of this bug to important, so
kdevelop 5.2 can migrate to testing.  Yes, it is an important update
(merged kdevplatform, so the separate source can be dropped), so I
really it to reach testing.
Because of another issue in the past, related to llvm (#866354),
kdevelop 5.1.x was stuck in unstable for basically 2 months. I don't
want llvm to get in the way of kdevelop, once again.

-- 
Pino Toscano

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

Bug#881643: marked as done (spacefm not updated after libavfilter update, broken link.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 20:08:19 +0100
with message-id <98e7f6a9-2b21-bd87-820e-29278a276...@linuxmint.pl>
and subject line Re: Bug#881643: spacefm not updated after libavfilter update, 
broken link.
has caused the Debian Bug report #881643,
regarding spacefm not updated after libavfilter update, broken link.
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.)


-- 
881643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spacefm-gtk3
Version: 1.0.5-2
Severity: grave
Source: spacefm
Tags: sid

$ spacefm
spacefm: relocation error: /usr/lib/x86_64-linux-gnu/libavfilter.so.6: symbol
av_hwframe_map, version LIBAVUTIL_55 not defined in file libavutil.so.55 with 
link time
reference
$

Looks like the spacefm shoul dbe re-built using the new version of libavfilter
(libavfilter6 is in version 7:3.4-2) and libavutil (libavutil55 in version 
10:3.2.2-dmo1),
or that libavutil is missing some symbols.


$ ls /usr/lib/x86_64-linux-gnu/libavutil.so*
/usr/lib/x86_64-linux-gnu/libavutil.so.55
/usr/lib/x86_64-linux-gnu/libavutil.so.55.34.100

$ls /usr/lib/x86_64-linux-gnu/libavfilter.so.6*
/usr/lib/x86_64-linux-gnu/libavfilter.so.6
/usr/lib/x86_64-linux-gnu/libavfilter.so.6.107.100


libc6 : Version: 2.24-17


-- 
Nathaël PAJANI - ED3L - Techno-Innov
Internet : http://www.ed3l.fr - http://www.techno-innov.fr
--- End Message ---
--- Begin Message ---

Bug was invalid. Error was related to the configuration of user system.


--
 .''`.  Mateusz Łukasik
: :' :  https://l0calh0st.pl
`. `'   Debian Member - mat...@linuxmint.pl
  `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851--- End Message ---

Processed: Re: qtcreator: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873414 [src:qtcreator] qtcreator: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: pocl: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873417 [src:pocl] pocl: Please update to llvm-toolchain 4.0 or, better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#873411: kdevelop: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873411 [src:kdevelop] kdevelop: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: ycmd: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873412 [src:ycmd] ycmd: Please update to llvm-toolchain 4.0 or, better, 5.0
Severity set to 'serious' from 'normal'

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

Processed: Re: julia: Please update to llvm-toolchain 4.0 or, better, 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873408 [src:julia] julia: Please update to llvm-toolchain 4.0 or, better, 
5.0
Severity set to 'serious' from 'normal'

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

Bug#858828: marked as done (golang-github-google-certificate-transparency: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 18:49:29 +
with message-id 
and subject line Bug#858828: fixed in 
golang-github-google-certificate-transparency 0.0~git20160709.0.0f6e3d1~ds1-3
has caused the Debian Bug report #858828,
regarding golang-github-google-certificate-transparency: Please migrate to 
openssl1.1 in Buster
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.)


-- 
858828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-google-certificate-transparency
Version: 0.0~git20160709.0.0f6e3d1~ds1-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertag: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: golang-github-google-certificate-transparency
Source-Version: 0.0~git20160709.0.0f6e3d1~ds1-3

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-google-certificate-transparency 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, 20 Nov 2017 19:32:14 +0100
Source: golang-github-google-certificate-transparency
Binary: golang-github-google-certificate-transparency-dev
Architecture: source
Version: 0.0~git20160709.0.0f6e3d1~ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-google-certificate-transparency-dev - Framework for monitoring 
and auditing SSL certificates
Closes: 858828
Changes:
 golang-github-google-certificate-transparency 
(0.0~git20160709.0.0f6e3d1~ds1-3) unstable; urgency=medium
 .
   * Team upload.
   * Use debhelper v10
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Build-Depend on libssl-dev. (Closes: #858828)
Checksums-Sha1:
 3b9510c64cb29f6d8f763dae116c3d748bc1fed9 2824 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 b47575e2226431d0dd3b755257f2780b1cdc1a20 4628 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 6fa42fa93bf131f8358166c900c9a449304456b6 6913 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo
Checksums-Sha256:
 2879921007038c988fe8d817ecace36f4ed08ec0020bc1ababa28be57c265b1c 2824 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 5f1bfb85df22d2037f7774775f20fa0ec19cf9aa8d1347807648dcccbb9f9024 4628 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 03aad6797a23a1245685c47fe8d6cd785fd4c729d5b0be3a942f503aa394f1bb 6913 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo
Files:
 2652c83c2deca11cd0d2854ff9d4f474 2824 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.dsc
 1fc5bc1c025b06932608bf8399417a06 4628 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3.debian.tar.xz
 5ea59b33df32452c0320c7192948191c 6913 devel optional 
golang-github-google-certificate-transparency_0.0~git20160709.0.0f6e3d1~ds1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloTIGQACgkQEwLx8Dbr
6xlsIw/9FLAfOuO/jNJ9DfsClU3KXsSyaT218yAs4JI0kIjG/IZfjd8cy9g+OYX6
V3TxXeDkQG8tYHh83J+tEpltvmqtASqEp8tJiVIqMr7hEzdmNSxy+bY82xZqUNTr
liP0lFgIqdlW4gT21TRZICAwFveiH/jM4VuutQTejMQu6A2YxaEuMd84MnOejiOt
nwvCosOtYI4aSYvxIznGGO2pS87SeAWmIp0s6FzWYvpbIwVcB2OnJBZPJbr0rP8e
F3uhS7gB27s3ZFGcreX5H8QU0kd21UMkngVuAiI5/L4asG+JgT0k4cxYGekF0bNe
zqbTNNpIvuDQ0ucPjYnbV8jR/oW4cLgOKglilJAiASVNLSAIzzio9sFvqx/Dhn/7

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Mikulas Patocka]

Package: libc6-amd64
Version: 2.25-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?

I have a x86-64 system with i386 and x32 foreign architectures (because I
need to develop software for i386 and x32 architectures).

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

I ran apt update and apt upgrade. Apt tried to upgrade to libc-2.25.

   * What was the outcome of this action?

Halfway through apt upgrade it failed and I ended up with unusable system where
large number of binaries were segfauting on startup without doign anything.

   * What outcome did you expect instead?

The upgrade to libc-2.25 should work.


The reason for the catastrophic failure is this:

There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
x86-64 libc in /lib64/). This package is not technically needed (because
x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
installed nonetheless because of some dependencies.

apt makes sure that all libc packages are upgraded at once to the same
version. However, during the upgrade process, the package
libc6-amd64 is upgraded before libc6:amd64. So, during the upgrade, we
temporarily have two libcs with different versions on the system, and this
mismatch makes most of the x86-64 binaries crash. Due to the crashes, the
upgrade doesn't proceed and it doesn't install the correct libc version in
/lib/x86_64-linux-gnu/.

The result is unusable system.

The system can be fixed if we mount it from another machine and remove the
libc files from /lib64 directory - the upgrade can then proceed and
install correct libc in /lib/x86_64-linux-gnu/.

The libc package should be fixed, so that if we have mismatching libc
version in /lib64 and in /lib/x86_64-linux-gnu/, it shouldn't crash,
because such mismatch happens temporarily during upgrade.


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

Kernel: Linux 4.14.0 (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libc6-amd64 depends on:
ii  libc6  2.25-1

libc6-amd64 recommends no packages.

libc6-amd64 suggests no packages.

-- no debconf information

Processed: Pending fixes for bugs in the golang-github-google-certificate-transparency package

[Debian Bug Tracking System]

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

> tag 858828 + pending
Bug #858828 [golang-github-google-certificate-transparency] 
golang-github-google-certificate-transparency: Please migrate to openssl1.1 in 
Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#858828: Pending fixes for bugs in the golang-github-google-certificate-transparency package

[pkg-go-maintainers]

tag 858828 + pending
thanks

Some bugs in the golang-github-google-certificate-transparency
package are closed in revision
6105e2a0ad302a6d7cdfda8cfb64dee1cb910e30 in branch 'master' by Dr.
Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-google-certificate-transparency.git/commit/?id=6105e2a

Commit message:

Build-Depend on libssl-dev.

Closes: #858828

Bug#881496: [Pkg-privacy-maintainers] Bug#881496: onioncircuits: python3/testing and apparmor/testing breaks onioncircuits

[Sascha Steinbiss]

Hi all,

ah, this sheds some light on the situation. However:

> audit[3722]: AVC apparmor="DENIED" operation="file_mmap" 
> profile="/usr/bin/onioncircuits" 
> name="/usr/lib/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so" 
> pid=3722 comm="onioncircuits" requested_mask="m" denied_mask="m" fsuid=1000 
> ouid=0

This is interesting, since the corresponding line in the python AppArmor
abstractions [1] (which are imported by the onioncircuits profile [2]) is:

  /usr/lib{,32,64}/python3.[0-6]/lib-dynload/*.somr,

which indeed already has the mmap flag set. It's been in testing for
some while now (since bzr revision #1671, which was the initial update
to upstream's 2.11.1).
I also can't see it being overridden anywhere. So I am not sure why this
permission should be denied...

Any ideas? (AppArmor-savvy team members?)

Cheers
Sascha


[1]
https://alioth.debian.org/scm/loggerhead/collab-maint/apparmor/view/head:/profiles/apparmor.d/abstractions/python
[2]
https://anonscm.debian.org/cgit/pkg-privacy/packages/onioncircuits.git/tree/apparmor/usr.bin.onioncircuits#n8

> So, python3/testing + apparmor/testing is a breaking
> combination. Downgrading to apparmor/stable fixes the problem.
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers stable
>   APT policy: (500, 'stable'), (70, 'unstable'), (60, 'testing'), (50, 
> 'experimental')
> Architecture: amd64
>  (x86_64)
> 
> Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages onioncircuits depends on:
> ii  gir1.2-glib-2.01.54.1-3
> ii  gir1.2-gtk-3.0 3.22.26-1
> ii  python3-gi 3.22.0-2
> ii  python3-pycountry  17.5.14+ds1-0.1
> ii  python3-stem   1.6.0-1
> pn  python3:any
> 
> onioncircuits recommends no packages.
> 
> Versions of packages onioncircuits suggests:
> ii  tor-geoipdb  0.3.1.8-2
> 
> -- no debconf information
> 
> ___
> Pkg-privacy-maintainers mailing list
> pkg-privacy-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-privacy-maintainers
> 



signature.asc
Description: OpenPGP digital signature

Bug#881876: marked as done (astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing files: astromenace_64.png)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 19:10:43 +0100
with message-id 
and subject line Re: Bug#881876: astromenace: FTBFS on 32-bit arches: 
dh_install: astromenace missing files: astromenace_64.png
has caused the Debian Bug report #881876,
regarding astromenace: FTBFS on 32-bit arches: dh_install: astromenace missing 
files: astromenace_64.png
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.)


-- 
881876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astromenace
Version: 1.3.2+repack-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

astromenace FTBFS on 32-bit architectures (tried i386 and armhf) while
it builds fine on amd64.

   debian/rules override_dh_install
make[1]: Entering directory '/build/astromenace-1.3.2+repack'
dh_install --exclude=astromenace_64.png
dh_install: astromenace missing files: astromenace_64.png
dh_install: missing files, aborting
debian/rules:28: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25

This could be caused by a change in debhelper.


Andreas


astromenace_1.3.2+repack-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On 2017-11-20 14:08, James Cowgill wrote:
> I can't reproduce this with debhelper 10.10.9. Could you try building it
> again?

It was reproducible a few days ago (and even hit amd64 shortly after
after I filed the bug), but today it built cleanly on both sid and
buster for amd64, i386 and armhf. So something else was fixed inbetween. :-)


Andreas--- End Message ---

Bug#882247:

[Jos van Wolput]

Package: firefox
Version: 58.0~b4-1
Severity: grave

After upgrading firefox to version 58.0~b4-1 I get the same issue.

Bug#881577: marked as done (libmagics++-dev: cmake files require libraries without package dependency)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 17:20:15 +
with message-id 
and subject line Bug#881577: fixed in magics++ 2.34.3-6
has caused the Debian Bug report #881577,
regarding libmagics++-dev: cmake files require libraries without package 
dependency
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.)


-- 
881577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmagics++-dev
Version: 2.34.3-4
Severity: serious
Control: affects -1 src:metview

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

...
/usr/bin/ld: cannot find -lOdb_fortran
/usr/bin/ld: cannot find -lOdb
/usr/bin/ld: cannot find -leckit
/usr/bin/ld: cannot find -leckit_geometry
/usr/bin/ld: cannot find -leckit_linalg
/usr/bin/ld: cannot find -leckit_maths
/usr/bin/ld: cannot find -leckit_web
/usr/bin/ld: cannot find -leckit_cmd
/usr/bin/ld: cannot find -lmetkit
collect2: error: ld returned 1 exit status
src/uPlot/CMakeFiles/uPlot.dir/build.make:3405: recipe for target 'bin/uPlot' 
failed
make[3]: *** [bin/uPlot] Error 1


The libraries at the commandline seem to come from
/usr/lib/x86_64-linux-gnu/cmake/magics/magics-*
--- End Message ---
--- Begin Message ---
Source: magics++
Source-Version: 2.34.3-6

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated magics++ 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, 20 Nov 2017 15:29:03 +
Source: magics++
Binary: libmagplus3v5 libmagics++-dev magics++ python-magics++ python3-magics++ 
libmagics++-data libmagics++-metview-dev
Architecture: source all amd64
Version: 2.34.3-6
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libmagics++-data - Data files needed for magics++ library
 libmagics++-dev - Development files for ECMWF  plotting software MAGICS++
 libmagics++-metview-dev - Libraries needed for building MetView
 libmagplus3v5 - ECMWF meteorological plotting software library
 magics++   - Executables for the magics++ library
 python-magics++ - python support for Magics++
 python3-magics++ - Python3 support for Magics++
Closes: 881577
Changes:
 magics++ (2.34.3-6) unstable; urgency=medium
 .
   * Fix typo in control file. Closes: #881577
Checksums-Sha1:
 227e5a457a4386735018efe65f5b81a605a5f67e 2833 magics++_2.34.3-6.dsc
 e619d8efe7fb3d31dc8be5c59af5265c0d9f3b8b 35732 magics++_2.34.3-6.debian.tar.xz
 0d3c85811273eb6ddeabaeffecf6525681770423 36646324 
libmagics++-data_2.34.3-6_all.deb
 edb8fce11d8f8f85d137b6c43b50f0aa3ebb8929 109176 
libmagics++-dev_2.34.3-6_amd64.deb
 eb2e400ec4be0df97a957eb93b5a209b40a95a05 761720 
libmagics++-metview-dev_2.34.3-6_amd64.deb
 f200b34c89a9d9a43de4115242d1ffe8164904e8 72856780 
libmagplus3v5-dbgsym_2.34.3-6_amd64.deb
 27a60ba1947d0a7bcfda9c90ffd8630f002cc9a7 3052832 
libmagplus3v5_2.34.3-6_amd64.deb
 3f0dda1e477290edb22d5c3bc340e2d6f985edae 321280 
magics++-dbgsym_2.34.3-6_amd64.deb
 4585059df2673b0829ae4bb85d265f8166e15510 18950 
magics++_2.34.3-6_amd64.buildinfo
 fe11de3ec5b682ca49786f2b4ff29b1ab1e98e4d 62408 magics++_2.34.3-6_amd64.deb
 7c6d5b0f3beaf2ce3429ef429bc4e8f102065f68 61896 
python-magics++-dbgsym_2.34.3-6_amd64.deb
 0df23a87053c30864282e3aaff0b3c65195bfdb5 62824 
python-magics++_2.34.3-6_amd64.deb
 749e8041fc118a2a3fd6a94d6f709529d560c58e 62496 
python3-magics++-dbgsym_2.34.3-6_amd64.deb
 cccf6f8e36c37df39348b10ab1de19759e05921d 62460 
python3-magics++_2.34.3-6_amd64.deb
Checksums-Sha256:
 52f1d0d9ac768a204bdfddc2a69aac2dda53cd3067760ce1ef5726bb6257fb51 2833 
magics++_2.34.3-6.dsc
 dc28351ec8adfcdce7b281da2d5fe41edafe7b9ecfe3dca301d810e77072 35732 
magics++_2.34.3-6.debian.tar.xz
 03c1968e7907138f5766cb22a3442e2267c2c1cbfb0674eaf66e81256f0386c3 36646324 
libmagics++-data_2.34.3-6_all.deb
 

Bug#882248: sympathy FTBFS with glibc 2.25

[Adrian Bunk]

Source: sympathy
Version: 1.2.1+woking+cvs+git20161222
Severity: serious
Tags: buster sid

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

...
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -g -Werror -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libsympathy_a-lockfile.o `test -f 'lockfile.c' || echo './'`lockfile.c
lockfile.c: In function 'lockfile_add_name_from_dev':
lockfile.c:317:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
lockfile.c:317:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
   sprintf (buf, "LCK.%03d.%03d", major (dev), minor (dev));
 ^~~



 
cc1: all warnings being treated as errors
Makefile:988: recipe for target 'libsympathy_a-lockfile.o' failed
make[3]: *** [libsympathy_a-lockfile.o] Error 1

Bug#882247:

[積丹尼 Dan Jacobson]

Package: firefox
Version: 58.0~b4-1
Severity: grave

Firefox just starts in the corner of the screen with a . Unusable.

Processed: [bts-link] source package src:collectd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:collectd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #881757 (http://bugs.debian.org/881757)
> # Bug title: collectd: CVE-2017-16820: snmp plugin: double free or heap 
> corruption
> #  * https://github.com/collectd/collectd/issues/2291
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 881757 + fixed-upstream
Bug #881757 [src:collectd] collectd: CVE-2017-16820: snmp plugin: double free 
or heap corruption
Added tag(s) fixed-upstream.
> usertags 881757 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#882243: dfvfs FTBFS with construct 2.8.16

[Adrian Bunk]

Source: dfvfs
Version: 20171022-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfvfs-20171022'
python run_tests.py
Checking availability and versions of dependencies.
[OK]Crypto version: 2.6.1
[FAILURE]   construct version: 2.8.16 is too recent, 2.5.3 or earlier 
required.
[OK]dfdatetime version: 20171109
[OPTIONAL]  lzma.
[OK]pybde version: 20170902
[OK]pyewf version: 20140608
[OK]pyfsntfs version: 20170315
[OK]pyfvde version: 20170930
[OK]pyfwnt version: 20170115
[OK]pyqcow version: 20170222
[OK]pysigscan version: 20170124
[OK]pysmdev version: 20171112
[OK]pysmraw version: 20171105
[OK]pytsk3 version: 20171108
[OK]pyvhdi version: 20170223
[OK]pyvmdk version: 20170226
[OK]pyvshadow version: 20170902
[OK]pyvslvm version: 20160110
[OK]six version: 1.11.0
[OK]sqlite3 version: 3.21.0

debian/rules:23: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#882099: marked as done (libnih1: Dependency from libc6<2.25 breaks dist-upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 18:49:07 +0200
with message-id <20171120164907.wgizgxpyh3zbscwu@localhost>
and subject line After the second binNMU libnih1 has the correct dependency
has caused the Debian Bug report #882099,
regarding libnih1: Dependency from libc6<2.25 breaks dist-upgrade
to be marked as done.

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

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


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

Dear Maintainer,

Apt dist-upgrade wants to delete the following packages:
  cgmanager kde-plasma-desktop kdeconnect libcgmanager0 libnih-dbus1 libnih1 
libpam-systemd libvirt-daemon-system plasma-desktop plasma-widgets-addons 
plasma-workspace policykit-1 polkit-kde-1
  polkit-kde-agent-1 systemd-shim sysvinit-core udisks2


Seems the culprit is in libnih1 package:

root@hpsiddie:/home/manul# apt-get dist-upgrade -d libnih1+
Reading package lists... Done
Building dependency tree   
Reading state information... Done
libnih1 is already the newest version (1.0.3-8).
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libnih1 : Depends: libc6 (< 2.25) but 2.25-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


root@hpsiddie:/home/manul# apt-cache policy libc6
libc6:
  Installed: 2.24-17
  Candidate: 2.25-1
  Version table:
 2.25-1 500
500 http://ftp.us.debian.org/debian sid/main amd64 Packages
 *** 2.24-17 100
100 /var/lib/dpkg/status




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

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

Versions of packages libnih1 depends on:
ii  libc6  2.24-17

libnih1 recommends no packages.

libnih1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
After the second binNMU libnih1 has the correct dependency.

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

Bug#881107: marked as done (gb (build) depends on the obsolete golang-1.8-go)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:49:23 +
with message-id 
and subject line Bug#881107: fixed in gb 0.4.4-2
has caused the Debian Bug report #881107,
regarding gb (build) depends on the obsolete golang-1.8-go
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.)


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

gb depends and build depends on the obsolete golang-1.8-go.
--- End Message ---
--- Begin Message ---
Source: gb
Source-Version: 0.4.4-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated gb 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, 20 Nov 2017 17:18:26 +0100
Source: gb
Binary: gb golang-github-constabulary-gb-dev
Architecture: source
Version: 0.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 gb - project based build tool for Go
 golang-github-constabulary-gb-dev - project based build tool for Go (source)
Closes: 881107
Changes:
 gb (0.4.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depend on golang 1.9. (Closes: #881107)
   * Use debhelper v10
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Remove empty d/patches directory
Checksums-Sha1:
 bb28b3b9ef3f2233691edc5d16ed0ec815e735d2 2228 gb_0.4.4-2.dsc
 55595c3f1d2993466bbe6efb81d87bfcf445d179 4180 gb_0.4.4-2.debian.tar.xz
 01243e2e84a0fd0078a5d39122541658ea859245 5884 gb_0.4.4-2_amd64.buildinfo
Checksums-Sha256:
 97a4f025582b0de59b24e62dc39a53364596c60dfd02a456618433188c4cc6f0 2228 
gb_0.4.4-2.dsc
 73297c67f6636b4225e07f2aa545d9a270d7432c73622b4d4ae9f36e57adf9bb 4180 
gb_0.4.4-2.debian.tar.xz
 7d65090276fa1b45ac9ba47526f82ae53dd8fcc6769ac37da714f4257595d859 5884 
gb_0.4.4-2_amd64.buildinfo
Files:
 948de29f47376e9c7fd45dec5c1b4d25 2228 devel optional gb_0.4.4-2.dsc
 ad47125029bc1ca27ebadaa18bf53075 4180 devel optional gb_0.4.4-2.debian.tar.xz
 dfd71687ee61b486aa885bb31f6612ff 5884 devel optional gb_0.4.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloTAdgACgkQEwLx8Dbr
6xmTNg//dswzcZbrJMJDdqb5TLfEIJ6WrXb0zEZ95Oi+5ZXaJRVsZFO+nowdNzyK
AoUJh/b026tP4rbjh0XjsO67s5UMe715tGGzGoy6P8i5zeMUT2LsxV1GYH+xzCa3
OXBhl4lzUjp19Xa2lzMrrRFHc35bhecuhVNyMJwvCMuKPQ3/UE8AsgDWPA285YHB
Y3stYqs0uH66Hx3HIv5HJxKdDSnzSocW87iG/bdSzYNTdYvQ89rdFcmxzCaCAAMY
erfqyetERl4qZiytHQyC7+aBJN8x4n5AaACTE5smtN1Ho6cW8GzVG+Lql+unzp0b
Z5kNMDreTYjFWvcAN4hlLdulYJ/kqJS4UCftaCaEBYiQ6nFlb3YxL2dHYtAZhud7
zJtMoq3P1i1sBkHUK8QowZVvb5c/bdUlcfr1ayNDQkTnfa2T3GGlLgJSXpgLErj/
6rCtB40m3K1aKBSff3Sc8aUJ98PJUMcGuw63FUlRpyrDikX0Umed+SV3IsofcV6R
Xx1CSPuBP85aUL7RlTV+UZ00bZqnC6ZXOrDTWKBj2/jJVzPIR54k06bcVibyr5gt
BAD74V7SGLS8tP4EP/rwTZnHwoejczpJRraJqITafd5LcAJijyrBpibo43X5i0pE
4z5k5fi50EHuTJ0Y1m3XHOFmTkvJk9v18/wP8As1LPD6j9Ymd/A=
=IvQX
-END PGP SIGNATURE End Message ---

Processed: severity of 881756 is normal

[Debian Bug Tracking System]

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

> severity 881756 normal
Bug #881756 [swi-prolog] swi-prolog: FTBFS on mips: Build killed with signal 
TERM
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 881756

[Debian Bug Tracking System]

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

> tags 881756 = confirmed moreinfo
Bug #881756 [swi-prolog] swi-prolog: FTBFS on mips: Build killed with signal 
TERM
Removed tag(s) help.
> thanks
Stopping processing here.

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

Bug#882239: dfwinreg FTBFS with construct 2.8.16

[Adrian Bunk]

Source: dfwinreg
Version: 20170706-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfwinreg-20170706'
python run_tests.py
Checking availability and versions of dependencies.
[FAILURE]   construct version: 2.8.16 is too recent, 2.5.3 or earlier 
required.
[OK]dfdatetime version: 20171109
[OK]pyregf version: 20170130
[OK]six version: 1.11.0

debian/rules:22: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Processed: Pending fixes for bugs in the gb package

[Debian Bug Tracking System]

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

> tag 881107 + pending
Bug #881107 [src:gb] gb (build) depends on the obsolete golang-1.8-go
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881107: Pending fixes for bugs in the gb package

[pkg-go-maintainers]

tag 881107 + pending
thanks

Some bugs in the gb package are closed in revision
9afede07d1d81a512b989566f61e1944b994e53e in branch 'master' by Dr.
Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/gb.git/commit/?id=9afede0

Commit message:

Build-Depend on golang 1.9.

Closes: #881107

Bug#881105: marked as done (golang-github-nebulouslabs-fastrand build depends on the obsolete golang-1.8-go)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:19:28 +
with message-id 
and subject line Bug#881105: fixed in golang-github-nebulouslabs-fastrand 
0.0~git20170512.60b6156-1
has caused the Debian Bug report #881105,
regarding golang-github-nebulouslabs-fastrand build depends on the obsolete 
golang-1.8-go
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.)


-- 
881105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-nebulouslabs-fastrand
Version: 0.0~git20170420.0.5a1a312-1
Severity: serious

golang-github-nebulouslabs-fastrand build depends on the
obsolete golang-1.8-go.
--- End Message ---
--- Begin Message ---
Source: golang-github-nebulouslabs-fastrand
Source-Version: 0.0~git20170512.60b6156-1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-nebulouslabs-fastrand 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, 20 Nov 2017 17:04:38 +0100
Source: golang-github-nebulouslabs-fastrand
Binary: golang-github-nebulouslabs-fastrand-dev
Architecture: source
Version: 0.0~git20170512.60b6156-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-nebulouslabs-fastrand-dev - 10x faster than crypto/rand
Closes: 881105
Changes:
 golang-github-nebulouslabs-fastrand (0.0~git20170512.60b6156-1) unstable; 
urgency=medium
 .
   [ Bjorn Dolk ]
   * Team upload.
   * Use gbp pq for patches
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 0.0~git20170512.60b6156
   * Use golang-any instead of the obsolete golang-1.8-go. (Closes: #881105)
   * Update to Standards-Version 4.1.1
 - Use HTTPS URL for d/copyright
 - Use Priority: optional
   * Add missing golang-github-dchest-blake2b-dev to dependencies
Checksums-Sha1:
 895756d2fdf7f51de4688fd50e9440218fbf0a5f 2497 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 f8750291bd98f441a73de75ecb769908d8d486ef 6480 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 03878272be255e6687effdc7282e3de29a5f162e 2872 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 e4d2e19468d7a6f4868d478665cb21c0b7f13e3b 6159 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo
Checksums-Sha256:
 e6781a5dff3518f5a29ecc36082813634cc8ada12e1b9d3d59b764507b6d79d7 2497 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 f2b8076fcdcfdbf4b398e26a17fe2105f2e72613ffc1aa199b1cf6d8ec39eac5 6480 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 617eb1bcecdf1b1d00235cd7d30351193ca39aea1b5d6aea8d7f703b4191e472 2872 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 87b63ba050196e75a407ec04525b5818e2c9cb28025efac27ad19235499c882f 6159 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo
Files:
 240072007915557d763b05afd6263db0 2497 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.dsc
 012b6813e74a523c50e1401d4d285cfe 6480 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156.orig.tar.xz
 e141df2d550c8af459d3a0a078e4e8ba 2872 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1.debian.tar.xz
 68135dc23c13fa0e19b3b8b4a6eac0df 6159 devel optional 
golang-github-nebulouslabs-fastrand_0.0~git20170512.60b6156-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAloS/h0ACgkQEwLx8Dbr
6xnDXhAAiS6rYZMm4imUUVnmzOyCw0fWDTqfQ/K4M1kdgdXyP1HOKt7B4DIUWvoK
4+82mGCdRLRZGZe826btiEtFxZnBy3t34EqvlHW67K2ZsHFVZcEf/SHwU9apAEFt
3W1yx3Pc+0uO4GRcDvWP49gPbIg0bcXumV8LyxXShefkgcnrKLcjKaFD0uZ4Nyu+

Bug#881105: Pending fixes for bugs in the golang-github-nebulouslabs-fastrand package

[pkg-go-maintainers]

tag 881105 + pending
thanks

Some bugs in the golang-github-nebulouslabs-fastrand package are
closed in revision bbb620584bd893a88f665ae7f7144f31880f1684 in branch
'master' by Dr. Tobias Quathamer

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-nebulouslabs-fastrand.git/commit/?id=bbb6205

Commit message:

Use golang-any instead of the obsolete golang-1.8-go.

Closes: #881105

Processed: Pending fixes for bugs in the golang-github-nebulouslabs-fastrand package

[Debian Bug Tracking System]

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

> tag 881105 + pending
Bug #881105 [src:golang-github-nebulouslabs-fastrand] 
golang-github-nebulouslabs-fastrand build depends on the obsolete golang-1.8-go
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841133: marked as done (ruby-gruff: FTBFS: Tests hang after segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 16:42:11 +0100
with message-id <20171120154211.3wog23nnnildvkx4@shiraz>
and subject line transitive bug
has caused the Debian Bug report #841133,
regarding ruby-gruff: FTBFS: Tests hang after segmentation fault
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.)


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

Dear Maintainer,

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

  […]

  /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:65:in `run_suite'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `catch'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:468:in `block in run'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:283:in `run_setup'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:248:in `run_fixture'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:470:in `block (2 levels) in 
run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:744:in `run_test'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `test_bezier'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:230:in
 `initialize'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `reset_themes'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `initialize'
  
  -- Machine register context 
   RIP: 0x7f59938d0249 RBP: 0x RSP: 0x7ffd0ad90bd0
   RAX: 0x RBX: 0x01ee7510 RCX: 0x0021
   RDX: 0x RDI: 0x7f5993bf1b00 RSI: 0x
R8: 0x01ee7520  R9: 0x41a0 R10: 0x
   R11: 0x R12: 0x7f5993bf1b58 R13: 0x7f5993bf1b18
   R14: 0x01ee7510 R15: 0x7f5993bf1b00 EFL: 0x00010246
  

  […]

The full build log is attached.


Regards,

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


ruby-gruff.0.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---

Hi,

according to ci.debian.org, the package has been usable since Jan 1,
2017 after a long period of failure, matching the date of the bug
report.

I could build it here locally without problem and the problem mentioned
by Gunnar isn't showing up.

It was probably a bug triggered by a dependency, updated in the mean
time.

I am therefore closing this bug.

Cheers,

Cédric


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

Bug#881997: marked as done (vboot-utils FTBFS on 32bit: test failure)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 15:34:20 +
with message-id 
and subject line Bug#881997: fixed in vboot-utils 0~R63-10032.B-2
has caused the Debian Bug report #881997,
regarding vboot-utils FTBFS on 32bit: test failure
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.)


-- 
881997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vboot-utils
Version: 0~R63-10032.B-1
Severity: serious

https://buildd.debian.org/status/package.php?p=vboot-utils=sid

...
Testing prog... /<>/build/utility/bmpblk_utility
tests/futility/run_test_scripts.sh /<>/build/install_for_test/bin
-- builtin --
test_bdb.sh ... FAILED. Stdout is recorded in 
/<>/build/tests/futility_test_results/test_bdb.sh.stdout
+ me=test_bdb.sh
+ TMP=test_bdb.sh.tmp
+ cd /<>/build/tests/futility_test_results
+ BDB_FILE=bdb.bin
+ TESTKEY_DIR=/<>/tests/testkeys
+ TESTDATA_DIR=/<>/tests/testdata
+ BDBKEY_PUB=/<>/tests/testkeys/bdbkey.keyb
+ BDBKEY_PRI=/<>/tests/testkeys/bdbkey.pem
+ DATAKEY_PUB=/<>/tests/testkeys/datakey.keyb
+ DATAKEY_PRI=/<>/tests/testkeys/datakey.pem
+ BDBKEY_DIGEST=/<>/tests/testdata/bdbkey_digest.bin
+ DATAKEY_DIGEST=/<>/tests/testdata/datakey_digest.bin
+ DATA_FILE=/<>/tests/testdata/sp-rw.bin
+ declare -i num_hash
+ load_address=0x60061ec0de
+ /<>/build/install_for_test/bin/futility bdb --create bdb.bin 
--bdbkey_pri /<>/tests/testkeys/bdbkey.pem --bdbkey_pub 
/<>/tests/testkeys/bdbkey.keyb --datakey_pub 
/<>/tests/testkeys/datakey.keyb --datakey_pri 
/<>/tests/testkeys/datakey.pem --load_address 0x60061ec0de
BDB is created successfully
+ verify
+ local key_digest=/<>/tests/testdata/bdbkey_digest.bin
+ local extra_option=
+ /<>/build/install_for_test/bin/futility bdb --verify bdb.bin 
--key_digest /<>/tests/testdata/bdbkey_digest.bin
BDB is successfully verified.
+ check_field 'Load Address:' 0x60061ec0de
++ /<>/build/install_for_test/bin/futility show bdb.bin
++ grep 'Load Address:'
+ x='  Load Address:   0x'
+ '[' '  Load Address:   0x' ']'
+ x='   0x'
+ '[' '   0x' ']'
+ x=0x
+ '[' 0x == 0x60061ec0de ']'
+ return 1
test_create.sh ... PASSED
test_dump_fmap.sh ... PASSED
test_gbb_utility.sh ... PASSED
test_load_fmap.sh ... PASSED
test_main.sh ... PASSED
test_rwsig.sh ... 1024 2048 2048_exp3 3072_exp3 4096 8192 PASSED
test_show_contents.sh ... PASSED
test_show_kernel.sh ... PASSED
test_show_vs_verify.sh ... PASSED
test_show_usbpd1.sh ... 1024 2048 4096 8192 PASSED
test_sign_firmware.sh ... 1 2 3 4 5 6 PASSED
test_sign_fw_main.sh ... PASSED
test_sign_kernel.sh ... amd64: 1 2 3 4 5 6 arm: 1 2 3 4 5 6 PASSED
test_sign_keyblocks.sh ... PASSED
test_sign_usbpd1.sh ... 1 2 3 4 PASSED
test_file_types.sh ... PASSED
FAIL: 16 / 17 passed
Makefile:1490: recipe for target 'runfutiltests' failed
make[2]: *** [runfutiltests] Error 1
make[2]: Leaving directory '/<>'
debian/rules:23: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: vboot-utils
Source-Version: 0~R63-10032.B-2

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated vboot-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 14:19:32 +0100
Source: vboot-utils
Binary: vboot-utils cgpt vboot-kernel-utils
Architecture: source
Version: 0~R63-10032.B-2
Distribution: unstable
Urgency: medium
Maintainer: Sophie Brun 
Changed-By: Sophie Brun 
Description:
 cgpt   - GPT manipulation tool with support for Chromium OS extensions
 vboot-kernel-utils - Chrome OS verified boot utils 

Processed: clamav FTBFS with LLVM 4.0 as default

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 clamav FTBFS with LLVM 4.0 as default
Bug #873401 [src:clamav] clamav: Please update to llvm-toolchain 4.0 or, 
better, 5.0
Changed Bug title to 'clamav FTBFS with LLVM 4.0 as default' from 'clamav: 
Please update to llvm-toolchain 4.0 or, better, 5.0'.
> severity -1 serious
Bug #873401 [src:clamav] clamav FTBFS with LLVM 4.0 as default
Severity set to 'serious' from 'normal'

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

Bug#882172: marked as done (aircrack-ng FTBFS: chmod: cannot access dump-join: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 20 Nov 2017 15:18:56 +
with message-id 
and subject line Bug#882172: fixed in aircrack-ng 1:1.2-0~rc4-4
has caused the Debian Bug report #882172,
regarding aircrack-ng FTBFS: chmod: cannot access dump-join: No such file or 
directory
to be marked as done.

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

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


-- 
882172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aircrack-ng
Version: 1:1.2-0~rc4-3
Severity: serious

https://buildd.debian.org/status/package.php?p=aircrack-ng=sid

...
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod 755 /<>/debian/airgraph-ng/usr/share/airgraph-ng/dump-join
chmod: cannot access 
'/<>/debian/airgraph-ng/usr/share/airgraph-ng/dump-join': No such 
file or directory
debian/rules:25: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
--- End Message ---
--- Begin Message ---
Source: aircrack-ng
Source-Version: 1:1.2-0~rc4-4

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

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated aircrack-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Nov 2017 14:29:58 +0100
Source: aircrack-ng
Binary: aircrack-ng airgraph-ng
Architecture: source
Version: 1:1.2-0~rc4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Sophie Brun 
Description:
 aircrack-ng - wireless WEP/WPA cracking utilities
 airgraph-ng - Tool to graph txt files created by aircrack-ng
Closes: 882172
Changes:
 aircrack-ng (1:1.2-0~rc4-4) unstable; urgency=medium
 .
   [ Sophie Brun ]
   * Team upload.
   * debian/rules: override dh_fixperms only for arch-indep packages.
 Closes: #882172
 .
   [ Raphaël Hertzog ]
   * Add dh-python to Build-Depends.
Checksums-Sha1:
 635aa6ea0e20b2fe3a061220f3ffd48d007890dc 1987 aircrack-ng_1.2-0~rc4-4.dsc
 7788d8378507ce91b8629110f0221241aad80c7b 16424 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 0cdebd86084cbac7e85855a95dc5ef4a9a5428af 5982 
aircrack-ng_1.2-0~rc4-4_source.buildinfo
Checksums-Sha256:
 3c093b2ab647c86f788d8784261186f8ecbd49920e5ad33fdd3096aeb8469e84 1987 
aircrack-ng_1.2-0~rc4-4.dsc
 896907cc4b24699fff2131cd03b787d30f600f98a5c876ae1e8d451624d907a5 16424 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 416f817212852980007bedd14055116863e41e2bd86558cd35b6c22ac4213d6b 5982 
aircrack-ng_1.2-0~rc4-4_source.buildinfo
Files:
 e385010010d7248587db30c36202efdb 1987 net optional aircrack-ng_1.2-0~rc4-4.dsc
 ef223c4cc046fb480a2f0af72fd7fd04 16424 net optional 
aircrack-ng_1.2-0~rc4-4.debian.tar.xz
 4800d5b2efb1f8ac0292e545a05011c8 5982 net optional 
aircrack-ng_1.2-0~rc4-4_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAloS6MEACgkQA4gdq+vC
mrk1JwgAmgR1/PHWkfXJ2ahqSxCUHIred0DMHU1wnT1RO6if8mFjISmGiRAXszKf
jLE/PGJ7cjR5LmeQ2rX0dG2vwTSjroLtRsWUjfvSGgiwxucs5WUKuRBGpfabJ4Np
PmtnLdmd4sVgnjzBNrdWKzXLm3tiI1V+LCWAtcqy8gMjcQsSjNu+TQjHaekR8w34
7Nk8io6cRbCeoi2H8y++v4IbtJoTS0/zK9hWWNk3pHunCDlS52z9UnZiqI3Fg2NK
Kdydj0/3Q+cLoFbqXgLW8UK9ZsuLcI5Wq1ns9WLpF89h1PaY8wvhf46VDU5GRT3e
X1tA2yHqrVXtU1sLrFOIUm2Nf8FK7w==
=PCAN
-END PGP SIGNATURE End Message ---