Processed: Bug#864733

[Debian Bug Tracking System]

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

> fixed 864733 torbrowser-launcher/0.2.8-1
Bug #864733 [torbrowser-launcher] Error: "Download error: Download Error: 404 
Not Found", Debian stable
Marked as fixed in versions torbrowser-launcher/0.2.8-1.
>
End of message, stopping processing here.

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

Processed: Re: [Pkg-privacy-maintainers] Bug#864733: Error: "Download error: Download Error: 404 Not Found", Debian stable

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 0.2.8-1
Bug #864733 [torbrowser-launcher] Error: "Download error: Download Error: 404 
Not Found", Debian stable
Ignoring request to alter found versions of bug #864733 to the same values 
previously set

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

Bug#864733: [Pkg-privacy-maintainers] Bug#864733: Error: "Download error: Download Error: 404 Not Found", Debian stable

[Roger Shimizu]

Control: notfound -1 0.2.8-1

On Sun, Sep 10, 2017 at 5:15 AM, Nikolas Nyby  wrote:
>
> Hi,
> I received this error in version 0.2.7-3 of this package. I'm using
> Debian testing. Here's the output of torbrowser-launcher:
>
> $ torbrowser-launcher
> Tor Browser Launcher
> By Micah Lee, licensed under MIT
> version 0.2.7
> https://github.com/micahflee/torbrowser-launcher
> Downloading and installing Tor Browser for the first time.
> Downloading
> https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US
> Download Error: Download Error: 404 Not Found  'torbrowser_launcher.launcher.DownloadErrorException'>

Could you try the latest version 0.2.8-1, which was just migrated to buster?
Thanks!

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

Bug#853655: marked as done (setools: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 10 Sep 2017 01:23:43 +
with message-id 
and subject line Bug#853655: fixed in setools 4.1.1-1
has caused the Debian Bug report #853655,
regarding setools: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.5m -c 
libqpol/genfscon_query.c -o build/temp.linux-amd64-3.5/libqpol/genfscon_query.o 
-Werror -Wextra -Waggregate-return -Wcast-align -Wfloat-equal -Wformat 
-Wformat=2 -Winit-self -Winline -Wmissing-format-attribute 
-Wmissing-include-dirs -Wnested-externs -Wold-style-definition -Wpointer-arith 
-Wredundant-decls -Wstrict-prototypes -Wunknown-pragmas -Wwrite-strings 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-cast-qual 
-Wno-shadow -Wno-unreachable-code -fno-exceptions
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.5m -c libqpol/isid_query.c 
-o build/temp.linux-amd64-3.5/libqpol/isid_query.o -Werror -Wextra 
-Waggregate-return -Wcast-align -Wfloat-equal -Wformat -Wformat=2 -Winit-self 
-Winline -Wmissing-format-attribute -Wmissing-include-dirs -Wnested-externs 
-Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes 
-Wunknown-pragmas -Wwrite-strings -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-cast-qual -Wno-shadow -Wno-unreachable-code 
-fno-exceptions
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.5m -c libqpol/iterator.c -o 
build/temp.linux-amd64-3.5/libqpol/iterator.o -Werror -Wextra 
-Waggregate-return -Wcast-align -Wfloat-equal -Wformat -Wformat=2 -Winit-self 
-Winline -Wmissing-format-attribute -Wmissing-include-dirs -Wnested-externs 
-Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes 
-Wunknown-pragmas -Wwrite-strings -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-cast-qual -Wno-shadow -Wno-unreachable-code 
-fno-exceptions
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.5m -c libqpol/mls_query.c -o 
build/temp.linux-amd64-3.5/libqpol/mls_query.o -Werror -Wextra 
-Waggregate-return -Wcast-align -Wfloat-equal -Wformat -Wformat=2 -Winit-self 
-Winline -Wmissing-format-attribute -Wmissing-include-dirs -Wnested-externs 
-Wold-style-definition -Wpointer-arith 

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Luc Van Oostenryck]

On Sat, Sep 9, 2017 at 11:02 PM, Uwe Kleine-König  
wrote:
>
> I tried this on ppc64le and it fixes 2 tests, so were at
>
> Out of 287 tests, 273 passed, 14 failed (10 of them are known to fail)
>
> The repaired tests are:
>
> backend/hello.c
> backend/sum.c
>
> unexpected failures are:
>
> backend/arithmetic-ops.c
> backend/cmp-ops.c
> backend/int-cond.c
> backend/logical-ops.c
>
> These are not about missing preprocessor tokens as there are no system
> includes used, but the error there is
>
> Error: unrecognized opcode: `...`
>
> . I didn't look into what the problem is there, but attached the test
> log.

It clearly looks as the code generated by LLVM  (the machine code/assembly
not LLVM's bytecode) is not understood by the assembler (or at least some
instructions). Probably a mismatch with the architecture version or something
like that.

> I did a build test on a few other Debian machines, arm64 was fine, mips
> and mipx64el had 15 failures, ppc64 (i.e. big endian) had 12. I didn't
> look in more detail and suggest to tackle one after the other :-)

I fully test on x86, x86-64, arm & ARM64 (with LLVM 3.9 or 4.0).
I also test on ppc64 but not the LLVM part because the machines I have
access to have not LLVM installed and I never bothered to install it myself.

Would it be possible to have access to a machine with the architectures
you care about?

Meanwhile, is it possible to have the build logs but with 'make V=1 ...' ?
It would also be useful to have:
- the output of 'uname -a'
- the details about the version of LLVM you're using

On the other hand, you/us should disable the sparse-llvm part since:
- it's something that is bundled and build by default but absolutely not
  needed (or even useful) to use sparse.
- it hasn't been written for anything else than x86/x86-64 (no 'layout'
  for anything else than those architectures.

Best regards,
-- Luc Van Ooostenryck

Bug#871168: marked as done (caneda: FTBFS: chartsdialog.h:23:10: fatal error: ui_chartsdialog.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 10 Sep 2017 00:34:12 +
with message-id 
and subject line Bug#871168: fixed in caneda 0.3.1-1
has caused the Debian Bug report #871168,
regarding caneda: FTBFS: chartsdialog.h:23:10: fatal error: ui_chartsdialog.h: 
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.)


-- 
871168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caneda
Version: 0.3.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DQT_CORE_LIB 
> -DQT_GUI_LIB -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB 
> -I/<>/obj-x86_64-linux-gnu/src -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src/caneda_autogen/include 
> -I/<>/obj-x86_64-linux-gnu -I/<>/src/dialogs 
> -I/<>/src/paintings -I/<>/src/tools 
> -I/<>/obj-x86_64-linux-gnu/src/dialogs 
> -I/<>/obj-x86_64-linux-gnu/src/paintings 
> -I/<>/obj-x86_64-linux-gnu/src/tools -I/usr/include/qwt -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g   -fPIC 
> -std=gnu++11 -o CMakeFiles/caneda.dir/global.cpp.o -c 
> /<>/src/global.cpp
> In file included from /<>/src/chartview.cpp:23:0:
> /<>/src/dialogs/chartsdialog.h:23:10: fatal error: 
> ui_chartsdialog.h: No such file or directory
>  #include "ui_chartsdialog.h"
>   ^~~
> compilation terminated.
> src/CMakeFiles/caneda.dir/build.make:137: recipe for target 
> 'src/CMakeFiles/caneda.dir/chartview.cpp.o' failed
> make[3]: *** [src/CMakeFiles/caneda.dir/chartview.cpp.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/caneda_0.3.0-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
caneda package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Sep 2017 21:05:33 -0300
Source: caneda
Binary: caneda
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Lisandro Damián Nicanor Pérez Meyer 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 caneda - Electronic Design Automation software focused on easy of use and
Closes: 871168
Changes:
 caneda (0.3.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #871168).
Checksums-Sha1:
 9258626174e1bcc647cd0c383b33aa8032b6fa91 1834 caneda_0.3.1-1.dsc
 3d5fdd2f6ea8fd2fc5c04ab6449c819fe020d6bf 595356 caneda_0.3.1.orig.tar.xz
 523996fe72f17098c75f3d3f7972e14c845b282e 2412 caneda_0.3.1-1.debian.tar.xz
 aba3e213aa0c495b918b7ae888d6a1f8e8e09639 6779 caneda_0.3.1-1_source.buildinfo
Checksums-Sha256:
 1ba5824b19213af5e620524d95f2dd9c566752aa0a40e24f902fdda66fa8d35f 1834 
caneda_0.3.1-1.dsc
 

Bug#874138: marked as done (octave-msh FTBFS with octave-pkg-dev 1.5.0)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 23:50:28 +
with message-id 
and subject line Bug#874138: fixed in octave-msh 1.0.10-3
has caused the Debian Bug report #874138,
regarding octave-msh FTBFS with octave-pkg-dev 1.5.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.)


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

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

...
Summary: 32 tests, 29 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-msh
Source-Version: 1.0.10-3

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated octave-msh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Sep 2017 14:31:41 -0300
Source: octave-msh
Binary: octave-msh
Architecture: source amd64
Version: 1.0.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Description:
 octave-msh - create and manage meshes for FE or FV solvers in Octave
Closes: 874138
Changes:
 octave-msh (1.0.10-3) unstable; urgency=medium
 .
   [ Sébastien Villemot ]
   * d/copyright: use secure URL for format.
 .
   [ Rafael Laboissiere ]
   * d/p/continuation-lines.patch: New patch
   * d/p/skip-dolfin-tests.patch: New patch.
 Skip the unit tests related to the dolfin library, avoiding the
 package to FTBFS. (Closes: #874138)
   * d/control:
 + Use cgit instead of gitweb in Vcs-Browser URL
 + Bump Standards-Version to 4.1.0 (no changes needed)
Checksums-Sha1:
 2d4d9c541b08af242fa9002db5a7944a0b1dd9d6 2195 octave-msh_1.0.10-3.dsc
 9eb185880e846501eafcb02cc5b5b875299124cf 6292 octave-msh_1.0.10-3.debian.tar.xz
 ee32e22d7f6dee2c4e6521c7bd4bcf48a7e04bd1 901730 
octave-msh-dbgsym_1.0.10-3_amd64.deb
 8f3d3e682c4b87c53131ee548d072e536e923dd1 12337 
octave-msh_1.0.10-3_amd64.buildinfo
 583f79789b0b7a174bb04c2ee439d03c366d1de4 31934 octave-msh_1.0.10-3_amd64.deb
Checksums-Sha256:
 56e39e4964ceefd051fe2567de5be5c9223fe8bf611e0422e6e84054ad0f304e 2195 
octave-msh_1.0.10-3.dsc
 e9b4ab645552deedfcb024c11cf2af6a3490a6c49313decfbe511b9c343d642e 6292 
octave-msh_1.0.10-3.debian.tar.xz
 0ee73d05b4aaef41746fa1eec713d3dbfe6e5ca5374971322f128b3010cb2bf2 901730 
octave-msh-dbgsym_1.0.10-3_amd64.deb
 380c8cc38fc8adbce14d54297c13c3d92555612efe396692636905e899e7b02f 12337 
octave-msh_1.0.10-3_amd64.buildinfo
 e74ec7facc1b48a28a116f1bb57a86a22564d67d9e7f50ad8ed750a866479dd4 31934 
octave-msh_1.0.10-3_amd64.deb
Files:
 487ea0800412bb09831be2f171d76101 2195 math optional octave-msh_1.0.10-3.dsc
 3264f638bab5478803fa54b133e0ba55 6292 math optional 
octave-msh_1.0.10-3.debian.tar.xz
 d46875dc5b7f4bd4c3e091f9336c5522 901730 debug extra 
octave-msh-dbgsym_1.0.10-3_amd64.deb
 707f3698fabd03ee3316b8df7063e3ed 12337 math optional 
octave-msh_1.0.10-3_amd64.buildinfo
 e9e836307649c1068170cbf7a67308d0 31934 math optional 
octave-msh_1.0.10-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlm0d5MACgkQISSqGYN4
XJBdvg//TkdaRBHrDtD/CZ7TnjAaolOmndaSnmrptH57iypewYlynraUp0PULET5
ulICYQYvPquF9mjn39z8Ss0RbWHLtj9s25zWi/aAhU+cJpM9WxCog42WrqP65jdz
ib/OKeDgRYuneoT2ZBrQhbv8g9aWGUR/D0RJh7ciU81SNg/Yo2g/zuGP9HMGpKmf
omX/oGU6140dniZtydNDcqiTt32aysDTULVgQdq5M6Kj4fqDnMuFjDzJTGBOt8h5
7nSnuDxGZSlNgEk/KGAPYnuru5MalyYxmphGhLciTXQ1VBsFRz0u05pqp7r0LzOm
c0NabFwALWI5doN6xiFZ94+WVjSvMQ5+7P56oZ3aqF1Crgvs7gvC5Dc9Oc+TSDt7
aXT87XROWz0J6leR32Grps8gM3szjtsnjH4t+dg7/KZzABHMghiXxBAdmZwJkbXd
QaB3hSzM1ldSHhYAhRGl+pGHwv9mQTJ74FBjmvg3mfbnwM6FRTp4MIbsS04jzLET

Bug#874805: marked as done (haskell-vector: FTBFS due to ambiguous occurrences)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 23:35:04 +
with message-id 
and subject line Bug#874805: fixed in haskell-vector 0.12.0.1-1
has caused the Debian Bug report #874805,
regarding haskell-vector: FTBFS due to ambiguous occurrences
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.)


-- 
874805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-vector
Version: 0.11.0.0-8
Severity: serious

Hi,
haskell-vector now FTBFS in unstable[0]; the relevant tail of the log is
given below:

> Data/Vector.hs:223:14: error:
> Ambiguous occurrence `fromList'
> It could refer to either `Exts.fromList',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromList', defined at 
> Data/Vector.hs:1528:1
>
> Data/Vector.hs:224:15: error:
> Ambiguous occurrence `fromListN'
> It could refer to either `Exts.fromListN',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromListN', defined at 
> Data/Vector.hs:1537:1
>
> Data/Vector.hs:344:19: error:
> Ambiguous occurrence `fromList'
> It could refer to either `Exts.fromList',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromList', defined at 
> Data/Vector.hs:1528:1
> /usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
> failed

Regards,
James

[0] 
https://buildd.debian.org/status/fetch.php?pkg=haskell-vector=sparc64=0.11.0.0-8%2Bb1=1504966021=0
--- End Message ---
--- Begin Message ---
Source: haskell-vector
Source-Version: 0.12.0.1-1

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated haskell-vector 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Sep 2017 16:14:29 -0700
Source: haskell-vector
Binary: libghc-vector-dev libghc-vector-prof libghc-vector-doc
Architecture: source
Version: 0.12.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Sean Whitton 
Description:
 libghc-vector-dev - Efficient Arrays for Haskell${haskell:ShortBlurb}
 libghc-vector-doc - Efficient Arrays for Haskell${haskell:ShortBlurb}
 libghc-vector-prof - Efficient Arrays for Haskell${haskell:ShortBlurb}
Closes: 874805
Changes:
 haskell-vector (0.12.0.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #874805)
   * Drop patches newer-base-and-ghc-prim, newer-quickcheck
 Obsoleted by upstream changes.
Checksums-Sha1:
 7ce6716c741a0ade7061104ed6eb0df0d1d6ed15 2570 haskell-vector_0.12.0.1-1.dsc
 6d048ea1fac4c8958545e42312bbd2082f847c7b 121798 
haskell-vector_0.12.0.1.orig.tar.gz
 43b6a89fd67ea352dfb7df399e9e6b4d806e643c 3852 
haskell-vector_0.12.0.1-1.debian.tar.xz
 f10d157526b03f6a9106a276e80fab78ffdd81bb 5744 
haskell-vector_0.12.0.1-1_source.buildinfo
Checksums-Sha256:
 3012444e848bdb76d48571951a4026f6d67f2577585f59314819a88b662f1827 2570 
haskell-vector_0.12.0.1-1.dsc
 b100ee79b9da2651276278cd3e0f08a3c152505cc52982beda507515af173d7b 121798 
haskell-vector_0.12.0.1.orig.tar.gz
 106d64b28eff7537f2903d051c62edb332c92f684d99f23052817434668ae6ed 3852 
haskell-vector_0.12.0.1-1.debian.tar.xz
 42bd2ad7ff6d69721305cafe97f9509ba4365930db772be87fa9b4dfebcd5cf0 5744 
haskell-vector_0.12.0.1-1_source.buildinfo
Files:
 cfa0d07e7ece1914527d7f9bde781981 2570 haskell extra 
haskell-vector_0.12.0.1-1.dsc
 82b3e15adf88250d76d91240e3c21159 

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Emmanuel Bourg]

Control: reassign -1 libsejda-io-java
Control: affects -1 libsambox-java
Control: tags -1 + patch

Le 9/09/2017 à 19:53, Markus Koschany a écrit :

> thanks for the patch. However we can just remove the
> --has-package-version option in libsambox-java.poms which will have the
> same effect. This issue was caused by a recent change in
> maven-debian-helper and affects multiple packages.

The --has-package-version flag in libsambox-java is fine. It's the one
in libsejda-io-java that isn't consistent with the pom version, sorry if
this wasn't clear. The patch proposed is a good solution.

Processed: Re: Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libsejda-io-java
Bug #874494 [src:libsambox-java] rebuilding libsambox-java generates unmet 
dependency on libsejda-io-java (>= 1.1.3.RELEASE)
Bug reassigned from package 'src:libsambox-java' to 'libsejda-io-java'.
No longer marked as found in versions libsambox-java/1.0.34-1.
Ignoring request to alter fixed versions of bug #874494 to the same values 
previously set
> affects -1 libsambox-java
Bug #874494 [libsejda-io-java] rebuilding libsambox-java generates unmet 
dependency on libsejda-io-java (>= 1.1.3.RELEASE)
Added indication that 874494 affects libsambox-java
> tags -1 + patch
Bug #874494 [libsejda-io-java] rebuilding libsambox-java generates unmet 
dependency on libsejda-io-java (>= 1.1.3.RELEASE)
Added tag(s) patch.

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

Bug#871171: marked as done (aplus-fsf: FTBFS: configure: error: C compiler cannot create executables)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 22:19:47 +
with message-id 
and subject line Bug#871171: fixed in aplus-fsf 4.22.1-10
has caused the Debian Bug report #871171,
regarding aplus-fsf: FTBFS: configure: error: C compiler cannot create 
executables
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.)


-- 
871171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aplus-fsf
Version: 4.22.1-9
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc-6
> checking whether the C compiler works... no
> configure: error: in `/<>'
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> debian/rules:48: recipe for target 'configure-stamp' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/aplus-fsf_4.22.1-9_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Neil Roeth  (supplier of updated aplus-fsf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Sep 2017 22:09:18 -0400
Source: aplus-fsf
Binary: aplus-fsf-doc xfonts-kapl aplus-fsf-el aplus-fsf aplus-fsf-dev
Architecture: source amd64 all
Version: 4.22.1-10
Distribution: unstable
Urgency: medium
Maintainer: Neil Roeth 
Changed-By: Neil Roeth 
Description:
 aplus-fsf  - A+ programming language run-time environment
 aplus-fsf-dev - A+ programming language development environment
 aplus-fsf-doc - A+ programming language documentation
 aplus-fsf-el - XEmacs lisp for A+ development
 xfonts-kapl - APL fonts for A+ development
Closes: 871171
Changes:
 aplus-fsf (4.22.1-10) unstable; urgency=medium
 .
   * Removed implicit build dependency on g++-6 (Closes: #871171).
Checksums-Sha1:
 cbedceef4c729d9a7a2415e7e0d6ba5ac2e1b3e2 1950 aplus-fsf_4.22.1-10.dsc
 ec772dcb52ca3e282f99632cdf6061bcc2094904 587506 aplus-fsf_4.22.1-10.diff.gz
 db0a6aaac5a45107f927b112e6d9f9533db06e27 9038314 
aplus-fsf-dbgsym_4.22.1-10_amd64.deb
 da67c6d082424a288302a23515025e6ea880112b 6980 aplus-fsf-dev_4.22.1-10_amd64.deb
 f40172c2de20e17b6f7abf442c6280a7b7999afd 2531988 
aplus-fsf-doc_4.22.1-10_all.deb
 f65a9eb32cbbff1fac1456da9ca52f49cddf677b 9092 aplus-fsf-el_4.22.1-10_all.deb
 6d42f75c5aeb8e2e42063e09f1c5c2e246957e20 7411 
aplus-fsf_4.22.1-10_amd64.buildinfo
 1229f3311cdc7b43ceed5458fb205470ba2b35d5 1921642 aplus-fsf_4.22.1-10_amd64.deb
 70b607a84f17f5c3895d3772d38d6a2d324a7c87 49486 xfonts-kapl_4.22.1-10_all.deb
Checksums-Sha256:
 f8cd6f5777444add03db34f68c48238b5f1c4e3552f9a3db155d9ee7da654eda 1950 
aplus-fsf_4.22.1-10.dsc
 b129ddf69d00a1392c1ea3f3b5d59884773658b3b55dd18148f6a8f3782a27aa 587506 
aplus-fsf_4.22.1-10.diff.gz
 c8cdf5724ad39b2e28ccff3c1aff43929f10a0cce8401ab405711a7f3a5d2ca4 9038314 
aplus-fsf-dbgsym_4.22.1-10_amd64.deb
 5ee3be207d7b7ba944ddac0875b847d30750ff7b38a5ddbc85a6393abd16c3f8 6980 
aplus-fsf-dev_4.22.1-10_amd64.deb
 6975a082c90bcdf6e4eb97954d91fae94fbd052161d9aa7746ddde8d6b2a4c9e 2531988 
aplus-fsf-doc_4.22.1-10_all.deb
 

Bug#875248: gnome: severe graphical glitches

[Ramiro Lopes]

Package: gnome
Version: 1:3.22+3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm experiencing severe graphical glitches on Gnome and Gdm3 that render
the environment unusable. Borders of windows remain on screen, blinking, after
moving, and typing on terminals is a mess, full of glitches that make it
impossible to see the characters. Menus show highliting and blinking of
several items when hovering over them. Chromium works fine though.

Videos show this better than pictures, here are a couple:
https://photos.app.goo.gl/lgTsHKLZhBa3SaF83
https://photos.app.goo.gl/m2Dj4XYP79q0fSTJ2

I'm using Fluxbox for now which works perfectly, showing no glitches,
whatsoever.

I updated my system from Jessie to Stretch and I believe this started after
 an upgrade, but not the dist-upgrade though. I tried reverting all packages
but that did not help.

System running on current Stretch versions of all packages.
Xorg with no custom configurations.

Hardware: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, 
Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758]
Driver: xserver-xorg-video-radeon 1:7.8.0-1+b1

I'm not sure if this is a Gnome, Xorg, Radeon bug...

Any help is appreciated.


PS.: I just would like to let you know that I'm an experienced Linux user, and
I have been using it for 20 years on several computers, servers, laptop etc.
I can provide you with any information you need and perform any tests you
suggest. I googled for similar problems but I haven't found any.



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

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

Versions of packages gnome depends on:
ii  avahi-daemon 0.6.32-2
ii  cheese   3.22.1-1+b1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 9.0.2
ii  evolution3.22.6-1
ii  evolution-plugins3.22.6-1
ii  file-roller  3.22.3-1
ii  gedit-plugins3.22.0-1
ii  gimp 2.8.18-1
ii  gnome-calendar   3.22.4-2
ii  gnome-clocks 3.22.1-1
ii  gnome-color-manager  3.22.2-1
ii  gnome-core   1:3.22+3
ii  gnome-dictionary 3.20.0-3+b1
ii  gnome-documents  3.22.1-1
ii  gnome-getting-started-docs   3.22.0-1
ii  gnome-maps   3.22.2-1
ii  gnome-music  3.22.2-1
ii  gnome-orca   3.22.2-3
ii  gnome-photos 3.22.5-1
ii  gnome-screenshot 3.22.0-1+b1
ii  gnome-sound-recorder 3.21.92-2
ii  gnome-tweak-tool 3.22.0-1
ii  gnome-weather3.20.2-1
ii  gstreamer1.0-libav   1.10.4-1
ii  gstreamer1.0-plugins-ugly1.10.4-1
ii  inkscape 0.92.1-1
ii  libgsf-bin   1.14.41-1
ii  libgtk2-perl 2:1.2499-1
ii  libproxy1-plugin-networkmanager  0.4.14-2
ii  libreoffice-calc 1:5.2.7-1
ii  libreoffice-evolution1:5.2.7-1
ii  libreoffice-gnome1:5.2.7-1
ii  libreoffice-impress  1:5.2.7-1
ii  libreoffice-writer   1:5.2.7-1
ii  nautilus-sendto  3.8.4-2+b1
ii  network-manager-gnome1.4.4-1
ii  rhythmbox3.4.1-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.1-2+b1
ii  rhythmbox-plugins3.4.1-2+b1
ii  rygel-playbin0.32.1-3
ii  rygel-tracker0.32.1-3
ii  seahorse 3.20.0-3.1
ii  simple-scan  3.23.2-1
ii  totem-plugins3.22.1-1
ii  vinagre  3.22.0-1+b1
ii  xdg-user-dirs-gtk0.10-1+b1

Versions of packages gnome recommends:
ii  brasero   3.12.1-4
ii  gnome-games   1:3.22+3
ii  polari3.22.2-1
ii  transmission-gtk  2.92-2

Versions of packages gnome suggests:
ii  alacarte 3.11.91-2
ii  empathy  3.12.12-4
pn  firefox-esr-l10n-all | firefox-l10n-all  
ii  goobox   3.4.2-3
pn  xul-ext-gnome-keyring
pn  xul-ext-ublock-origin

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.22.0-1+deb9u1
ii  at-spi2-core  2.22.0-6
ii  baobab3.22.1-1
ii  caribou   0.4.21-1+b1
ii  chrome-gnome-shell8-4
ii  chromium  60.0.3112.78-1~deb9u1
ii  dconf-cli   

Bug#852572: marked as done (s390-tools: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 21:13:19 +
with message-id 
and subject line Bug#852572: fixed in s390-tools 1.37.1-1
has caused the Debian Bug report #852572,
regarding s390-tools: Update udevadm path
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.)


-- 
852572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s390-tools
Version: 1.36.1-1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package s390-tools does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Source: s390-tools
Source-Version: 1.37.1-1

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated s390-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 09 Jul 2017 10:07:15 +0200
Source: s390-tools
Binary: s390-tools s390-tools-udeb
Architecture: source
Version: 1.37.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian S/390 Team 
Changed-By: Philipp Kern 
Description:
 s390-tools - Set of fundamental utilities for Linux on S/390
 s390-tools-udeb - Set of utilities for Linux on S/390 (udeb)
Closes: 852572 856062 857190
Changes:
 s390-tools (1.37.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Pass in the default CPPFLAGS/LDFLAGS from debian/rules.
   * Drop the libsysfs-dev build-dependency; it is no longer used.
 (Closes: #856062)
   * Check for udevadm in /bin, not /sbin. (Closes: #852572)
   * Replace BindTo with BindsTo in systemd unit file. (Closes: #857190)
Checksums-Sha1:
 8cbd1f43a79ebfacc09c4c06a91135678cfe934e 1708 s390-tools_1.37.1-1.dsc
 98c594c077f0dde13e346a726e1f95bb0b2e3042 867980 s390-tools_1.37.1.orig.tar.bz2
 c7bb5edf3abe09ff1249c61f9bb801db47da4f4a 10788 
s390-tools_1.37.1-1.debian.tar.xz
 7b1c51fab190714035769bc71882a4728dc1f070 6586 
s390-tools_1.37.1-1_source.buildinfo
Checksums-Sha256:
 f26442098cc04ffef0c5f25234dc986d53c172f0124e7758e8cc96afe7316033 1708 
s390-tools_1.37.1-1.dsc
 778ff067eb76b3d0f24e19844ad9f3ecac9584d13ce3fc1573598d310816ffda 867980 
s390-tools_1.37.1.orig.tar.bz2
 840c93bcdb1dc3505659ad29dbef1ae0ac268f124f6396603e8acba89e3bcdcd 10788 
s390-tools_1.37.1-1.debian.tar.xz
 0f6b0df9cd866dc657f334f01fb3e39e46e4e6184bcc63f9d8993f8cc2187ea8 6586 
s390-tools_1.37.1-1_source.buildinfo
Files:
 32b9f1e9cd4f861abef78645bb0c1445 1708 admin important s390-tools_1.37.1-1.dsc
 6ae1671c2712875c8e0a12df059851a6 867980 admin important 
s390-tools_1.37.1.orig.tar.bz2
 5e926c19e49adfe18553649f40b64b21 10788 admin important 
s390-tools_1.37.1-1.debian.tar.xz
 3ba5f6f607af636f229619e411f44bb6 6586 admin important 
s390-tools_1.37.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlm0RuQRHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuzatAf/QRLETcbX9AqYJIAhgBm9wXGtao95r93a
ITYcgr4/c/Sm+kzZLbaZBdhEzmLFA2NvwkDafaVV0cmkEhHrLuJIba2r+s9k/kgs
iIOVvS//HCsgnrsQxhmEFRB7S+ON+htxmhslljWdCvR7xp0Z5H0NV015hYGI+1hV
gRcaakrJNnHIg/TztvPIEjBSQlZD+hrR6O4gh1F9gStKezR1CejQ2kiin6ek7Bcw
z4LsJSxD3JRglhX2dYDpxwvoqFPPL5YXRpZOS7iG6KX7Wvb1Bf3QdBbZtMepvmO4
XFs6b7fL46FdfrQF8NlGZxZsCM2tdu3M11o34gRRj3LuyvPKuS09Sw==
=yBIe
-END PGP SIGNATURE End Message ---

Bug#873465: marked as done (apt: wrongly reports failure on 'update' on mips64el, triggers d-i FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 22:59:21 +0200
with message-id <20170909225854.ga32...@debian.org>
and subject line Re: Bug#873465: apt: wrongly reports failure on 'update' on 
mips64el, triggers d-i FTBFS
has caused the Debian Bug report #873465,
regarding apt: wrongly reports failure on 'update' on mips64el, triggers d-i 
FTBFS
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.)


-- 
873465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.5~beta2
Severity: serious
Tags: d-i
Justification: triggers FTBFS

(Please keep debian-boot@ in the loop.)

Hi,

Daily builds of the Debian Installer on mips64el have started erroring
out on 2017-08-19 with what I believed was some kind of network issue;
but we've just hit the very same issue on the buildd when trying to
build the actual debian-installer release:
  
https://buildd.debian.org/status/fetch.php?pkg=debian-installer=mips64el=20170828=1503891562=0

Excerpt:
| Using generated sources.list.udeb:
|deb [trusted=yes] copy:/<>/build/ localudebs/
|deb http://ftp.at.debian.org/debian buster main/debian-installer
|deb http://ftp.debian.org/debian buster main/debian-installer
| make[7]: 'sources.list.udeb' is up to date.
| Ign:1 copy:/<>/build localudebs/ InRelease
| Ign:2 copy:/<>/build localudebs/ Release
| Get:3 http://ftp.at.debian.org/debian buster InRelease [124 kB]
| Ign:4 copy:/<>/build localudebs/ Packages
| Ign:4 copy:/<>/build localudebs/ Packages
| Ign:4 copy:/<>/build localudebs/ Packages
| Get:4 copy:/<>/build localudebs/ Packages [20 B]
| Get:5 http://ftp.debian.org/debian buster InRelease [124 kB]
| Get:6 http://ftp.at.debian.org/debian buster/main/debian-installer mips64el 
Packages [55.7 kB]
| Get:7 http://ftp.debian.org/debian buster/main/debian-installer mips64el 
Packages [55.7 kB]
| Fetched 358 kB in 1s (280 kB/s)
| Reading package lists...
| E: Some index files failed to download. They have been ignored, or old ones 
used instead.

AFAICT, everything looks good and matches what happens on e.g. amd64:
| Using generated sources.list.udeb:
|deb [trusted=yes] copy:/<>/build/ localudebs/
|deb http://mirror.bm.debian.org/debian buster main/debian-installer
|deb http://ftp.debian.org/debian buster main/debian-installer
| make[9]: 'sources.list.udeb' is up to date.
| Ign:1 copy:/<>/build localudebs/ InRelease
| Ign:2 copy:/<>/build localudebs/ Release
| Ign:3 copy:/<>/build localudebs/ Packages
| Ign:3 copy:/<>/build localudebs/ Packages
| Ign:3 copy:/<>/build localudebs/ Packages
| Get:3 copy:/<>/build localudebs/ Packages [20 B]
| Get:4 http://mirror.bm.debian.org/debian buster InRelease [124 kB]
| Get:5 http://ftp.debian.org/debian buster InRelease [124 kB]
| Get:6 http://mirror.bm.debian.org/debian buster/main/debian-installer amd64 
Packages [50.5 kB]
| Get:7 http://ftp.debian.org/debian buster/main/debian-installer amd64 
Packages [50.5 kB]
| Fetched 348 kB in 0s (563 kB/s)
| Reading package lists...
| Reading package lists...

Given apt 1.5~beta2 was uploaded on the evening of the 17th, it probably
reached the archive on the 18th, and was first used in the build chroot
for the 0030Z build on the 19th. I'm filing this against apt since it
seems clear to me there were no actual download errors, but it also
seems likely that apt might be encountering gcc-7 related
miscompilations, see #871514.

In any case, a speedy fix would be much appreciated, as this is a
blocker for the D-I Buster Alpha 1 release (which has already been
delayed way too much for other reasons).

Thanks for your time.


KiBi.
--- End Message ---
--- Begin Message ---

On Mon, Aug 28, 2017 at 06:24:50AM +0200, Cyril Brulebois wrote:
> Package: apt
> Version: 1.5~beta2
> Severity: serious
> Tags: d-i
> Justification: triggers FTBFS
> 
> (Please keep debian-boot@ in the loop.)
> 
> Hi,
> 
> Daily builds of the Debian Installer on mips64el have started erroring
> out on 2017-08-19 with what I believed was some kind of network issue;
> but we've just hit the very same issue on the buildd when trying to
> build the actual debian-installer release:
>   
> https://buildd.debian.org/status/fetch.php?pkg=debian-installer=mips64el=20170828=1503891562=0

Is fixed with a new gcc version


-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.--- End Message ---

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
> On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
> that works. So to address the Debian bug I can do:
> >
> >  - move sparse to /usr/lib
> >  - teach cgcc about the move of sparse
> >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> 
> I don't like that. It means the user can't invoke sparse directly.
> 
> >
> > or is it easier to teach sparse about the architecture stuff?
> 
> First of all. It is not very trivial to teach sparse about the architecture
> stuff. To my mind, we need to move all the cgcc logic into sparse.
> 
> For this case, I think it is easier to teach the sparse validation
> code to use cgcc on those back end testing. Most validation don't
> need to include system header file at all so it does not have
> this problem.
> 
> How about this patch?
> I know my patch is white space damaged in email.
> Git branch is at:
> https://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git/log/?h=llvm-cgcc
> 
> Please let me know if that fix your problem. It pass check
> on my local machine running x86_64. I don't have ppc64 to
> test with.
> 
> Chris
> 
> diff --git a/sparsec b/sparsec
> index 9dc96c9..2990d26 100755
> --- a/sparsec
> +++ b/sparsec
> @@ -32,7 +32,8 @@ done
>  TMPLLVM=`mktemp -t tmp.XX`".llvm"
>  TMPFILE=`mktemp -t tmp.XX`".o"
> 
> -$DIRNAME/sparse-llvm $SPARSEOPTS > $TMPLLVM
> +env CHECK=$DIRNAME/sparse-llvm $DIRNAME/cgcc -no-compile \
> +   $SPARSEOPTS > $TMPLLVM
> 
>  LLC=`"${LLVM_CONFIG:-llvm-config}" --bindir`/llc
> 
> diff --git a/sparsei b/sparsei
> index 3431a9f..3abd00f 100755
> --- a/sparsei
> +++ b/sparsei
> @@ -10,4 +10,4 @@ if [ $# -eq 0 ]; then
>exit 1
>  fi
> 
> -$DIRNAME/sparse-llvm $@ | $LLI
> +env CHECK=$DIRNAME/sparse-llvm $DIRNAME/cgcc -no-compile $@ | $LLI

I tried this on ppc64le and it fixes 2 tests, so were at

Out of 287 tests, 273 passed, 14 failed (10 of them are known to fail)

The repaired tests are:

backend/hello.c
backend/sum.c

unexpected failures are:

backend/arithmetic-ops.c
backend/cmp-ops.c
backend/int-cond.c
backend/logical-ops.c

These are not about missing preprocessor tokens as there are no system
includes used, but the error there is

Error: unrecognized opcode: `...`

. I didn't look into what the problem is there, but attached the test
log.

I did a build test on a few other Debian machines, arm64 was fine, mips
and mipx64el had 15 failures, ppc64 (i.e. big endian) had 12. I didn't
look in more detail and suggest to tackle one after the other :-)

Best regards
Uwe
I: Started sh -c make && make check
O: make: Nothing to be done for 'all'.
O:  TESTWoverride-init-def (Woverride-init-def.c)
O:  TESTWoverride-init-no (Woverride-init-no.c)
O:  TESTWoverride-init-yes (Woverride-init-yes.c)
O:  TESTwarn-unknown-attribute (Wunknown-attribute-def.c)
O:  TESTwarn-unknown-attribute-no (Wunknown-attribute-no.c)
O:  TESTwarn-unknown-attribute-yes (Wunknown-attribute-yes.c)
O:  TEST__func__ (__func__.c)
O:  TESTabstract array declarator static 
(abstract-array-declarator-static.c)
O:  TESTaddress_space attribute (address_space.c)
O:  TESTalias distinct symbols (alias-distinct.c)
O:  TESTalias symbol/pointer (alias-mixed.c)
O:  TESTalias same symbols (alias-same.c)
O:  TESTattribute __alloc_align__ (alloc-align.c)
O:  TESTalternate keywords (alternate-keywords.c)
O:  TESTtest anonymous union initializer (anon-union.c)
O:  TESTAsm with goto labels. (asm-empty-clobber.c)
O:  TESTAsm with goto labels. (asm-goto-lables.c)
O:  TESTasm-toplevel.c (asm-toplevel.c)
O:  TESTinline attributes (attr-inline.c)
O:  TESTattribute no_sanitize_address (attr-no_sanitize_address.c)
O:  TESTattribute noclone (attr-noclone.c)
O:  TESToptimize attributes (attr-optimize.c)
O:  TESTattribute warning (attr-warning.c)
O:  TESTattribute assume_aligned (attr_aligned.c)
O:  TESTattribute after ( in direct-declarator (attr_in_parameter.c)
O:  TESTattribute vector_size (attr_vector_size.c)
O:  TESTArithmetic operator code generation (backend/arithmetic-ops.c)
O: error: actual error text does not match expected error text.
O: error: see backend/arithmetic-ops.c.error.* for further investigation.
O: --- backend/arithmetic-ops.c.error.expected  2017-09-09 20:44:47.964306005 
+
O: +++ backend/arithmetic-ops.c.error.got   2017-09-09 20:44:47.960305943 
+
O: @@ -0,0 +1,10 @@
O: +{standard input}: Assembler messages:
O: +{standard input}:38: Error: unrecognized opcode: `xsaddsp'
O: +{standard input}:52: Error: unrecognized opcode: `xsadddp'
O: +{standard input}:94: Error: unrecognized opcode: `xssubsp'
O: +{standard input}:108: Error: unrecognized opcode: `xssubdp'
O: +{standard input}:150: Error: 

Bug#784453: [brewtarget] Qt4 removal, please package latest upstream version

[Simon Quigley]

Control: -1 retitle [brewtarget] Qt4 removal, please package latest upstream 
version

This bug can be fixed by packaging the latest upstream version, or at
minimum, 2.2.0, which features a Qt 5 port.

-- 
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4

Bug#875125: comptext: Incomplete debian/copyright?

[Chris Lamb]

Source: comptext
Version: 1.0.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ana Custura 

Hi,

I just ACCEPTed comptext from NEW but noticed it was missing 
attribution in debian/copyright for at least Stelios Bounanos
in the win32 dir.

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


Regards,

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

Bug#875126: comptext: Incomplete debian/copyright?

[Chris Lamb]

Source: comptext
Version: 1.0.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ana Custura 

Hi,

I just ACCEPTed comptext from NEW but noticed it was missing 
attribution in debian/copyright for at least Stelios Bounano
in the win32 bit.

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

Processed: severity of 875107 is normal

[Debian Bug Tracking System]

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

> severity 875107 normal
Bug #875107 [kdesudo] RM: kdesudo -- ROM; Deprecated upstream and superseded by 
kdesu
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#875106: python-oslo.concurrency: Incomplete debian/copyright?

[Chris Lamb]

Source: python-oslo.concurrency
Version: 3.21.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Thomas Goirand 

Hi,

I just ACCEPTed python-oslo.concurrency from NEW but noticed it was 
missing attribution in debian/copyright for at least Piston.

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


Regards,

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

Bug#875107: RM: kdesudo -- ROM; Deprecated upstream and superseded by kdesu

[Simon Quigley]

Package: ftp.debian.org
Package: kdesudo
Severity: serious

kdesudo still uses Qt 3 libraries (with the Qt 4 compatibility layer)
and has not seen upstream commits since 2011. It's superseded by kdesu,
which is Qt 5 and works fine.

kdesu has seen several CVEs, and in my opinion, it's more of a liability
to keep kdesudo than to keep it. It should also be removed because of
the Qt 4 removal in Buster.

-- 
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4



signature.asc
Description: OpenPGP digital signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Timo Aaltonen]

On 09.09.2017 02:31, Salvo Tomaselli wrote:
> Well I had to downgrade to testing since it was making my machine crash.

Doesn't crash my KBL now that I tested it. Try an older kernel maybe.



-- 
t

Bug#864733: Error: "Download error: Download Error: 404 Not Found", Debian stable

[Nikolas Nyby]

Package: torbrowser-launcher
Version: 0.2.7-3
Followup-For: Bug #864733

Dear Maintainer,

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

Hi,
I received this error in version 0.2.7-3 of this package. I'm using
Debian testing. Here's the output of torbrowser-launcher:

$ torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.7
https://github.com/micahflee/torbrowser-launcher
Downloading and installing Tor Browser for the first time.
Downloading
https://dist.torproject.org/torbrowser/update_2/release/Linux_x86_64-gcc3/x/en-US
Download Error: Download Error: 404 Not Found 

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


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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates  20170717
ii  gnupg2.1.23-2
ii  python   2.7.13-2
ii  python-gtk2  2.24.0-5.1
ii  python-lzma  0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil5.0.1-1+b1
ii  python-twisted   17.5.0-2
ii  python-txsocksx  1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.0.10-1

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
pn  python-pygame  

-- no debconf information

Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.

[Anton Gladky]

tags 874727 +moreinfo
severity 874727 important
thanks

Hi,

thank you for the bugreport. Please provide some more information,
what packages in Debian are affected.

Thanks

Anton


2017-09-09 11:33 GMT+02:00 markus :
> Package: libcoin80v5
> Version: 3.1.4~abc9f50+dfsg1-2
> Severity: critical
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) the included 
> copy of it in libcoin results in segfaults of any program that uses 
> libexpat1. Specifically any program that uses xml from python and links 
> against libcoin will segfault.
>
> The stacktrace looks like it is a problem with libexpat1 leading to a 
> segfault in XML_SetHashSalt - however looking at that function there is no 
> way it could possibly segfault - unless of course the provided XMLParser 
> pointer does not actually point to what expat expects to be an XMLParser - 
> which is indeed the case because the XMLParser instance was created by a call 
> into lobcoin which is still on libexpat 2.2.0.

Processed: Re: Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.

[Debian Bug Tracking System]

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

> tags 874727 +moreinfo
Bug #874727 [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other 
library that uses lebexpat1 segfaults.
Added tag(s) moreinfo.
> severity 874727 important
Bug #874727 [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other 
library that uses lebexpat1 segfaults.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#874802: libcblas3 and libatlas3-base: error when trying to install together

[Sébastien Villemot]

On Sat, Sep 09, 2017 at 09:11:46PM +0200, Sébastien Villemot wrote:

> - completely dropping libcblas3 (and libcblas-dev). These two packages are
>   actually useless, because they provide the same C interface to BLAS than the
>   other BLAS implementations (libblas3, libatlas3-base, libopenblas-base), but
>   in a less optimized way;

I made a mistake here. Paradoxically libcblas-dev does not provide the
standardized C API for BLAS, which is called… “CBLAS”; it only provides the
Fortran API. See the discussion in
https://lists.debian.org/debian-science/2017/09/msg00038.html

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#874802: libcblas3 and libatlas3-base: error when trying to install together

[Sébastien Villemot]

On Sat, Sep 09, 2017 at 08:22:08PM +0200, Ralf Treinen wrote:
> Package: libatlas3-base,libcblas3
> Version: libatlas3-base/3.10.3-4
> Version: libcblas3/3.2.1+dfsg-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
> 
> Date: 2017-09-09
> Architecture: amd64
> Distribution: sid

> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:

> dpkg: error processing archive 
> /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.so.3', which is also 
> in package libatlas3-base:amd64 3.10.3-4
> Processing triggers for libc-bin (2.24-17) ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

First, note that the problem has appeared because I have multiarchified atlas,
and therefore the libcblas.so.3 that it provides has moved from /usr/lib to
/usr/lib/. But in a sense the situation was already problematic
before that change , because two libraries with the same SONAME were in the
dynamic linker search path.

Same reasoning for #874803.

Now, I think there are two options for fixing this issue:

- completely dropping libcblas3 (and libcblas-dev). These two packages are
  actually useless, because they provide the same C interface to BLAS than the
  other BLAS implementations (libblas3, libatlas3-base, libopenblas-base), but
  in a less optimized way;

- or making the two packages conflict.

Andreas (and others), what do you think?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#874805: haskell-vector: FTBFS due to ambiguous occurrences

[James Clarke]

Source: haskell-vector
Version: 0.11.0.0-8
Severity: serious

Hi,
haskell-vector now FTBFS in unstable[0]; the relevant tail of the log is
given below:

> Data/Vector.hs:223:14: error:
> Ambiguous occurrence `fromList'
> It could refer to either `Exts.fromList',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromList', defined at 
> Data/Vector.hs:1528:1
>
> Data/Vector.hs:224:15: error:
> Ambiguous occurrence `fromListN'
> It could refer to either `Exts.fromListN',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromListN', defined at 
> Data/Vector.hs:1537:1
>
> Data/Vector.hs:344:19: error:
> Ambiguous occurrence `fromList'
> It could refer to either `Exts.fromList',
>  imported from `Data.Primitive.Array' at 
> Data/Vector.hs:164:1-37
>  (and originally defined in `GHC.Exts')
>   or `Data.Vector.fromList', defined at 
> Data/Vector.hs:1528:1
> /usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
> failed

Regards,
James

[0] 
https://buildd.debian.org/status/fetch.php?pkg=haskell-vector=sparc64=0.11.0.0-8%2Bb1=1504966021=0

Bug#874803: libcblas-dev and libatlas-base-dev: error when trying to install together

[Ralf Treinen]

Package: libatlas-base-dev,libcblas-dev
Version: libatlas-base-dev/3.10.3-4
Version: libcblas-dev/3.2.1+dfsg-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-09-09
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package gcc-7-base:amd64.
(Reading database ... 10979 files and directories currently installed.)
Preparing to unpack .../gcc-7-base_7.2.0-4_amd64.deb ...
Unpacking gcc-7-base:amd64 (7.2.0-4) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_7.2.0-4_amd64.deb ...
Unpacking libquadmath0:amd64 (7.2.0-4) ...
Selecting previously unselected package libgfortran4:amd64.
Preparing to unpack .../libgfortran4_7.2.0-4_amd64.deb ...
Unpacking libgfortran4:amd64 (7.2.0-4) ...
Selecting previously unselected package libatlas3-base:amd64.
Preparing to unpack .../libatlas3-base_3.10.3-4_amd64.deb ...
Unpacking libatlas3-base:amd64 (3.10.3-4) ...
Selecting previously unselected package libatlas-base-dev:amd64.
Preparing to unpack .../libatlas-base-dev_3.10.3-4_amd64.deb ...
Unpacking libatlas-base-dev:amd64 (3.10.3-4) ...
Selecting previously unselected package libblas-common.
Preparing to unpack .../libblas-common_3.7.1-1+b1_amd64.deb ...
Unpacking libblas-common (3.7.1-1+b1) ...
Selecting previously unselected package libf2c2:amd64.
Preparing to unpack .../libf2c2_20130926-2_amd64.deb ...
Unpacking libf2c2:amd64 (20130926-2) ...
Selecting previously unselected package libcblas3.
Preparing to unpack .../libcblas3_3.2.1+dfsg-1_amd64.deb ...
Unpacking libcblas3 (3.2.1+dfsg-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.so.3', which is also 
in package libatlas3-base:amd64 3.10.3-4
Selecting previously unselected package libcblas-dev.
Preparing to unpack .../libcblas-dev_3.2.1+dfsg-1_amd64.deb ...
Unpacking libcblas-dev (3.2.1+dfsg-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcblas-dev_3.2.1+dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.a', which is also in 
package libatlas-base-dev:amd64 3.10.3-4
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.24-17) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb
 /var/cache/apt/archives/libcblas-dev_3.2.1+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Error calling setupterm: 0
E: cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/x86_64-linux-gnu/libcblas.a
  /usr/lib/x86_64-linux-gnu/libcblas.so

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#874802: libcblas3 and libatlas3-base: error when trying to install together

[Ralf Treinen]

Package: libatlas3-base,libcblas3
Version: libatlas3-base/3.10.3-4
Version: libcblas3/3.2.1+dfsg-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-09-09
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package gcc-7-base:amd64.
(Reading database ... 10979 files and directories currently installed.)
Preparing to unpack .../gcc-7-base_7.2.0-4_amd64.deb ...
Unpacking gcc-7-base:amd64 (7.2.0-4) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_7.2.0-4_amd64.deb ...
Unpacking libquadmath0:amd64 (7.2.0-4) ...
Selecting previously unselected package libgfortran4:amd64.
Preparing to unpack .../libgfortran4_7.2.0-4_amd64.deb ...
Unpacking libgfortran4:amd64 (7.2.0-4) ...
Selecting previously unselected package libatlas3-base:amd64.
Preparing to unpack .../libatlas3-base_3.10.3-4_amd64.deb ...
Unpacking libatlas3-base:amd64 (3.10.3-4) ...
Selecting previously unselected package libblas-common.
Preparing to unpack .../libblas-common_3.7.1-1+b1_amd64.deb ...
Unpacking libblas-common (3.7.1-1+b1) ...
Selecting previously unselected package libf2c2:amd64.
Preparing to unpack .../libf2c2_20130926-2_amd64.deb ...
Unpacking libf2c2:amd64 (20130926-2) ...
Selecting previously unselected package libcblas3.
Preparing to unpack .../libcblas3_3.2.1+dfsg-1_amd64.deb ...
Unpacking libcblas3 (3.2.1+dfsg-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcblas.so.3', which is also 
in package libatlas3-base:amd64 3.10.3-4
Processing triggers for libc-bin (2.24-17) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libcblas3_3.2.1+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/x86_64-linux-gnu/libcblas.so.3

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#854228: marked as done (Libraries not linked with their deps)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 18:06:55 +
with message-id 
and subject line Bug#854228: fixed in scalapack 2.0.2-2
has caused the Debian Bug report #854228,
regarding Libraries not linked with their deps
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.)


-- 
854228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libblacs-openmpi1
Version: 1.1-37+b1
Severity: serious

All three shared libs in the package are linked only with libc, while using
various MPI_*, BI_* etc symbols.

Interesting that rebuilding a package (with the patch for #848813) links these
libraries with various libmpi_* libs, partially fixing the problem. These are
the remaining symbols:

undefined symbol: Cblacs_pinfo  (/usr/lib/libblacs-openmpi.so.1.1)

undefined symbol: BI_Iam(/usr/lib/libblacsCinit-openmpi.so.1.1)
undefined symbol: BI_F77_MPI_COMM_WORLD (/usr/lib/libblacsCinit-openmpi.so.1.1)
undefined symbol: BI_Np (/usr/lib/libblacsCinit-openmpi.so.1.1)
undefined symbol: bi_f77_get_constants_ (/usr/lib/libblacsCinit-openmpi.so.1.1)
undefined symbol: BI_BlacsErr   (/usr/lib/libblacsCinit-openmpi.so.1.1)

undefined symbol: BI_Iam(/usr/lib/libblacsF77init-openmpi.so.1.1)
undefined symbol: BI_F77_MPI_COMM_WORLD (/usr/lib/libblacsF77init-
openmpi.so.1.1)
undefined symbol: BI_Np (/usr/lib/libblacsF77init-openmpi.so.1.1)
undefined symbol: bi_f77_get_constants_ (/usr/lib/libblacsF77init-
openmpi.so.1.1)
undefined symbol: bi_f77_init_  (/usr/lib/libblacsF77init-openmpi.so.1.1)



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

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

Versions of packages libblacs-openmpi1 depends on:
ii  libc62.24-9
ii  mpi-default-bin  1.8

libblacs-openmpi1 recommends no packages.

libblacs-openmpi1 suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: scalapack
Source-Version: 2.0.2-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated scalapack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Sep 2017 01:30:35 +0800
Source: scalapack
Binary: libscalapack-openmpi2.0 libscalapack-mpich2.0 libscalapack-mpi-dev 
libscalapack-mpich-dev libscalapack-openmpi-dev scalapack-mpi-test 
scalapack-test-common
Architecture: source
Version: 2.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 libscalapack-mpi-dev - Scalable Linear Algebra Package - Dev. files for MPICH
 libscalapack-mpich-dev - Scalable Linear Algebra Package - Dev. files for MPICH
 libscalapack-mpich2.0 - Scalable Linear Algebra Package - Shared libs. for 
MPICH
 libscalapack-openmpi-dev - Scalable Linear Algebra Package - Dev. files for 
OPENMPI
 libscalapack-openmpi2.0 - Scalable Linear Algebra Package - Shared libs. for 
OpenMPI
 scalapack-mpi-test - Scalable Linear Algebra Package - Test files for MPI
 scalapack-test-common - Test data for ScaLAPACK testers
Closes: 854228
Changes:
 scalapack (2.0.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Standards-Version: 4.1.0
   * blacs is now included in scalapack. blacs initialisation is now
 independent of whether it is called from C or Fortran.
 Closes: #854228.
Checksums-Sha1:
 bc12ea0e8f9f6bb56231ab99271aee9294ada5a0 2634 scalapack_2.0.2-2.dsc
 74913c8c88999bcaa77de9d90e5c690f835889df 15224 scalapack_2.0.2-2.debian.tar.xz
Checksums-Sha256:
 

Processed: Re: Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -patch
Bug #874494 [src:libsambox-java] rebuilding libsambox-java generates unmet 
dependency on libsejda-io-java (>= 1.1.3.RELEASE)
Removed tag(s) patch.

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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Markus Koschany]

Control: tags -1 -patch

Hi,

thanks for the patch. However we can just remove the
--has-package-version option in libsambox-java.poms which will have the
same effect. This issue was caused by a recent change in
maven-debian-helper and affects multiple packages.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#849122: Please adjust the BTS version tracking info

[Francesco Poli]

On Sat, 1 Jul 2017 23:32:28 +0200 Francesco Poli wrote:

> Dear Debian wpasupplicant Maintainers,
> I noticed that these 3 RC bugs (#849122, #849077, #849875) are marked
> as found in wpa/2.6-2, which is now superseded by versions with epoch 2.
> What seems to have happened (please correct me, if I am wrong) is that
> the upstream version 2.4 was reintroduced into unstable (with epoch 2)
> and then migrated to stretch (before the stretch release as stable).
> 
> Hence, I would say that those three bugs only affect experimental and
> are not in stretch, buster or sid.
> 
> Could you please confirm that these 3 bugs should be marked as fixed in
> wpa/2:2.4-1 and found in wpa/2:2.6-4 ?
> 
> Thanks for your time!
> Bye.

Hello again,
could you please reply to my question?

Again, thanks for your time.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp8ZLuZnEijF.pgp
Description: PGP signature

Processed: [pkg-octave/master] d/p/skip-dolfin-tests.patch: New patch

[Debian Bug Tracking System]

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

> tag 874138 pending
Bug #874138 [src:octave-msh] octave-msh FTBFS with octave-pkg-dev 1.5.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: blacs is in scalapack 2

[Debian Bug Tracking System]

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

> reassign 854228 libscalapack-openmpi2.0
Bug #854228 [libblacs-openmpi1] Libraries not linked with their deps
Bug reassigned from package 'libblacs-openmpi1' to 'libscalapack-openmpi2.0'.
No longer marked as found in versions blacs-mpi/1.1-37.
Ignoring request to alter fixed versions of bug #854228 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#874138: [pkg-octave/master] d/p/skip-dolfin-tests.patch: New patch

[Rafael Laboissiere]

tag 874138 pending
thanks

Date: Sat Sep 9 14:28:21 2017 -0300
Author: Rafael Laboissiere 
Commit ID: a9988b3b911a35b08b045e6b38923a7fefcfa3f2
Commit URL: 
https://anonscm.debian.org/cgit/pkg-octave/octave-msh.git;a=commitdiff;h=a9988b3b911a35b08b045e6b38923a7fefcfa3f2
Patch URL: 
https://anonscm.debian.org/cgit/pkg-octave/octave-msh.git;a=commitdiff_plain;h=a9988b3b911a35b08b045e6b38923a7fefcfa3f2

d/p/skip-dolfin-tests.patch: New patch

Skip the unit tests related to the dolfin library, avoiding the
package to FTBFS.

Git-Dch: Full
Closes: #874138
  

Processed: Tagging #874787 as pending

[Debian Bug Tracking System]

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

> tags 874787 + pending
Bug #874787 [doris] doris: fails to install: IndentationError in 
create_image.py, line 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #874494 [src:libsambox-java] rebuilding libsambox-java generates unmet 
dependency on libsejda-io-java (>= 1.1.3.RELEASE)
Added tag(s) patch.

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

Bug#874494: rebuilding libsambox-java generates unmet dependency on libsejda-io-java (>= 1.1.3.RELEASE)

[Gianfranco Costamagna]

control: tags -1 patch

> >>> - remove the suffix from the version in the pom
> >>
> >> doesn't work

it worked to me, and the bootstrap in Ubuntu is now complete.

This is the patch:
--- libsejda-io-java-1.1.3/debian/patches/fix-broken-version.patch  
1970-01-01 00:00:00.0 +
+++ libsejda-io-java-1.1.3/debian/patches/fix-broken-version.patch  
2017-09-09 13:33:44.0 +
@@ -0,0 +1,15 @@
+Description: This breaks reverse-dependencies, fix version up
+Author: Gianfranco Costamagna 
+Last-Update: 2017-09-09
+
+--- libsejda-io-java-1.1.3.orig/pom.xml
 libsejda-io-java-1.1.3/pom.xml
+@@ -5,7 +5,7 @@
+   sejda-io
+   jar
+   sejda-io
+-  1.1.3.RELEASE
++  1.1.3
+ 
+   An Input/Output layer built on top of Java standard io and 
nio packages
+   http://www.sejda.org

G.



signature.asc
Description: OpenPGP digital signature

Bug#874787: doris: fails to install: IndentationError in create_image.py, line 13

[Andreas Beckmann]

Package: doris
Version: 5.0.3~beta+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package doris.
  (Reading database ... 
(Reading database ... 10562 files and directories currently installed.)
  Preparing to unpack .../doris_5.0.3~beta+dfsg-1_amd64.deb ...
  Unpacking doris (5.0.3~beta+dfsg-1) ...
  Setting up doris (5.0.3~beta+dfsg-1) ...
  Sorry: IndentationError: expected an indented block (create_image.py, line 13)
  dpkg: error processing package doris (--configure):
   subprocess installed post-installation script returned error exit status 101
  Errors were encountered while processing:
   doris


cheers,

Andreas


doris_5.0.3~beta+dfsg-1.log.gz
Description: application/gzip

Bug#862969: marked as done (r-cran-sp needs recompilation for R 3.4.0 ?)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 10:22:25 -0500
with message-id <22964.1841.475173.600...@bud.eddelbuettel.com>
and subject line All affected packages are manually uploaded
has caused the Debian Bug report #861333,
regarding r-cran-sp needs recompilation for R 3.4.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.)


-- 
861333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-sp
Version: 1:1.2-4-1

Using latest debian testing, function spDistsN1() of package sp throws an 
error:

> library(sp)
> ll <- matrix(c(5, 6, 60, 60), ncol=2)
> km <- spDistsN1(ll, ll[1,], longlat=TRUE)
Error in .C("sp_dists", x, y, xx, yy, n, dists, lonlat, PACKAGE = "sp") : 
  "sp_dists" not available for .C() for package "sp"

It was working until recently, i.e. before the upgrade from R 3.3 to 3.4. 

If I uninstall the debian package and compile the R source package from CRAN, 
it works. So probably the debian package needs recompilation.
--- End Message ---
--- Begin Message ---

Per the email thread in #868558, this bug can also be closed as all packages
needing a rebuild under R 3.4.* have now gotten a rebuild, thanks an
energetic push by Andreas.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---

Bug#861333: marked as done (r-base: R packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail to find objects)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 10:22:25 -0500
with message-id <22964.1841.475173.600...@bud.eddelbuettel.com>
and subject line All affected packages are manually uploaded
has caused the Debian Bug report #861333,
regarding r-base: R packages uploaded to Debian before 14 April 2017 that use 
.C or .Fortran fail to find objects
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.)


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

With current R, R packages built for Debian before the upload of R 
3.3.3.20170413-1 
on 14 April that use .C or .Fortran do no work properly, because the functions 
calling .C or .Fortran do not find the compiled objects.

Example packages are r-cran-spatial and r-cran-kernsmooth. 

An example session in a fresh Debian sid chroot:

> library(spatial)
> example(surf.gls)

srf.gl> library(MASS)  # for eqscplot

srf.gl> data(topo, package="MASS")

srf.gl> topo.kr <- surf.gls(2, expcov, topo, d=0.7)
Error in surf.gls(2, expcov, topo, d = 0.7) : object 'VR_frset' not found


The relevant NEWS entry from R is

* Packages which register native routines for .C or .Fortran need
  to be re-installed for this version (unless installed with
  R-devel SVN revision r72375 or later).

Packages compiled locally can simply be rebuilt using

  update.packages(lib.loc="/usr/local/lib/R/site-library", checkBuilt=TRUE)

However the packages provided by Debian packages are installed in a directory
only writable by privileged users.

Cheers,

Johannes

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

Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages r-base depends on:
ii  r-base-core3.4.0-1
ii  r-recommended  3.4.0-1

Versions of packages r-base recommends:
ii  r-base-html  3.4.0-1
ii  r-doc-html   3.4.0-1

Versions of packages r-base suggests:
pn  ess 
pn  r-doc-info | r-doc-pdf  

-- no debconf information
--- End Message ---
--- Begin Message ---

Per the email thread in #868558, this bug can also be closed as all packages
needing a rebuild under R 3.4.* have now gotten a rebuild, thanks an
energetic push by Andreas.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---

Bug#861684: marked as done (r-cran-randomfields: FTBFS against r-base 3.4.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 10:22:25 -0500
with message-id <22964.1841.475173.600...@bud.eddelbuettel.com>
and subject line All affected packages are manually uploaded
has caused the Debian Bug report #861333,
regarding r-cran-randomfields: FTBFS against r-base 3.4.0-1
to be marked as done.

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

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


-- 
861333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-randomfields
Version: 3.1.36-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

This package FTBFS against r-base 3.4.0-1 which was uploaded to unstable
recently.

[..]
make[1]: Leaving directory '/<>/src'
make[1]: Entering directory '/<>/src'
make[1]: Leaving directory '/<>/src'
installing to 
/<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields/libs
** R
** data
** inst
** preparing package for lazy loading
Error: package or namespace load failed for 'RandomFieldsUtils' in 
dyn.load(file, DLLpath = DLLpath, ...):
 allocation failure in R_setPrimitiveArgTypes
Error : package 'RandomFieldsUtils' could not be loaded
ERROR: lazy loading failed for package 'RandomFields'
* removing 
'/<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields'
dh_auto_install: R CMD INSTALL -l 
/<>/debian/r-cran-randomfields/usr/lib/R/site-library --clean . 
--built-timestamp='Sun, 08 Jan 2017 17:05:46 +0100' returned exit code 1
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

Build finished at 2017-05-02T17:28:29Z

Ximin


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

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

Per the email thread in #868558, this bug can also be closed as all packages
needing a rebuild under R 3.4.* have now gotten a rebuild, thanks an
energetic push by Andreas.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---

Bug#874786: qt3d5-dev: broken symlinks: /usr/lib/i386-linux-gnu/libQt53D{QuickScene2D, QuickAnimation, Animation}.so -> libQt53D*.so.5.9.1

[Andreas Beckmann]

Package: qt3d5-dev
Version: 5.9.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m50.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/i386-linux-gnu/libQt53DQuickScene2D.so -> 
libQt53DQuickScene2D.so.5.9.1
  /usr/lib/i386-linux-gnu/libQt53DQuickAnimation.so -> 
libQt53DQuickAnimation.so.5.9.1
  /usr/lib/i386-linux-gnu/libQt53DAnimation.so -> libQt53DAnimation.so.5.9.1

Looks like missing dependencies on libqt53dquickscene2d5,
libqt53dquickanimation5, libqt53danimation5.


cheers,

Andreas


qt3d5-dev_5.9.1+dfsg-2+b1.log.gz
Description: application/gzip

Processed: user debian...@lists.debian.org, found 867275 in 2:4.5.1-1, found 857151 in 1:20170829 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> found 867275 2:4.5.1-1
Bug #867275 [libemos-data] libemos-data: broken symlinks: 
/usr/share/emos/bufrtables/?.TXT -> ?_.distinct
Marked as found in versions emoslib/2:4.5.1-1.
> found 857151 1:20170829
Bug #857151 [live-build] live-build: broken symlinks: 
/usr/share/live/build/bootloaders/*/*.c32
Marked as found in versions live-build/1:20170829.
> found 857393 7.8.1+dfsg-1
Bug #857393 [gazebo7-common] gazebo7-common: broken symlink: 
/usr/share/gazebo-7/media/fonts/arial.ttf -> 
../../../fonts/truetype/ttf-liberation/LiberationSans-Regular.ttf
Marked as found in versions gazebo/7.8.1+dfsg-1.
> affects 87 + python3-biopython
Bug #87 [python-biopython] python-biopython: broken symlinks: 
/usr/share/doc/python-biopython/{NEWS, DEPRECATED, CONTRIB} -> *.rst
Added indication that 87 affects python3-biopython
> found 857222 0.2-7
Bug #857222 [python3-flask-silk] python3-flask-silk: broken symlink: 
/usr/lib/python3/dist-packages/flask_silk/icons/arrow_turn_up.png -> 
../../../../../share/icons/python3-flask-silk/16x16/arrow_turn_up.png
Marked as found in versions flask-silk/0.2-7.
> found 857820 1.14.15-1
Bug #857820 [simplesamlphp] simplesamlphp: broken symlink: 
/usr/share/simplesamlphp/vendor/openid/php-openid/Auth -> ../../../../php/Auth
Marked as found in versions simplesamlphp/1.14.15-1.
> affects 874418 + libdislocker0.6 dislocker libdislocker0-dev
Bug #874418 [libdislocker0.7] libdislocker0.7: fails to upgrade from 'stretch' 
- trying to overwrite /usr/lib/libdislocker.so
Added indication that 874418 affects libdislocker0.6, dislocker, and 
libdislocker0-dev
> found 864927 live-task-kde/0.1
Bug #864927 {Done: Maximiliano Curia } [kde-l10n-sr] 
kde-l10n-sr and plasma-desktop-data: error when trying to install together
The source live-task-kde and version 0.1 do not appear to match any binary 
packages
Marked as found in versions live-task-kde/0.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857151
857222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857222
857393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857393
857820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857820
864927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864927
867275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867275
87: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
874418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#873918: marked as done (charmtimetracker: Missing binary dependency on libqt5sql5-sqlite)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 15:19:07 +
with message-id 
and subject line Bug#873918: fixed in charmtimetracker 1.11.4-2
has caused the Debian Bug report #873918,
regarding charmtimetracker: Missing binary dependency on libqt5sql5-sqlite
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.)


-- 
873918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: charmtimetracker
Version: 1.11.4-1
Severity: grave
Tags: patch
Justification: Renders package unusable

Hi,

charmtimetracker appears to be missing a binary dependency on
libqt5sql5-sqlite. Installing libqt5sql5-sqlite manually moves
past this.

  $ charmtimetracker
  QSqlDatabase: QSQLITE driver not loaded
  QSqlDatabase: available drivers: 

Screenshot of UI error:

  https://i.imgur.com/1RLOZ4L.jpg


Patch attached.



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

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

Versions of packages charmtimetracker depends on:
ii  libc62.24-17
ii  libgcc1  1:7.2.0-1
ii  libqt5core5a 5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5gui5   5.9.1+dfsg-9
ii  libqt5keychain1  0.7.0-3
ii  libqt5network5   5.9.1+dfsg-9
ii  libqt5printsupport5  5.9.1+dfsg-9
ii  libqt5script55.9.1+dfsg-2
ii  libqt5sql5   5.9.1+dfsg-9
ii  libqt5widgets5   5.9.1+dfsg-9
ii  libqt5xml5   5.9.1+dfsg-9
ii  libstdc++6   7.2.0-1
ii  libxcb-screensaver0  1.12-1
ii  libxcb1  1.12-1

charmtimetracker recommends no packages.

charmtimetracker suggests no packages.

-- no debconf information


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/control b/debian/control
index 32ff76f..ebdba87 100644
--- a/debian/control
+++ b/debian/control
@@ -20,7 +20,7 @@ Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-kde/kde-extras/charmtimetracker
 
 Package: charmtimetracker
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, libqt5sql5-sqlite
 Description: Cross-Platform Time Tracker
  It is built around two major ideas - tasks and events.
  Tasks are the things time is spend on, repeatedly. Tasks
--- End Message ---
--- Begin Message ---
Source: charmtimetracker
Source-Version: 1.11.4-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Sep 2017 16:59:35 +0200
Source: charmtimetracker
Binary: charmtimetracker
Architecture: source
Version: 1.11.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Description:
 charmtimetracker - Cross-Platform Time Tracker
Closes: 873918
Changes:
 charmtimetracker (1.11.4-2) unstable; urgency=medium
 .
   * Fix "Missing binary dependency on libqt5sql5-sqlite" (Closes: #873918)
 - Adding libqt5sql5-sqlite to depends list of charmtimetracker.
   * Bump Standards-Version to 4.1.0 (no change needed).
Checksums-Sha1:
 f18ca708880c856963f80f81958c884c70665f56 2170 charmtimetracker_1.11.4-2.dsc
 262c6168ca154bd69eefa15314c32ec52ff6a9b3 3500 
charmtimetracker_1.11.4-2.debian.tar.xz
 59e2d81295433d45af145aa654898d546aa5b104 11590 
charmtimetracker_1.11.4-2_source.buildinfo
Checksums-Sha256:
 8fff7155c7137f65465ccd19ad9cd47d2520cc371582177aaad5b6a2a9cd2f73 2170 
charmtimetracker_1.11.4-2.dsc
 

Bug#872007: marked as done (dh_strip fails randomly "No such file or directory" during parallel builds)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 15:19:13 +
with message-id 
and subject line Bug#872007: fixed in debhelper 10.8
has caused the Debian Bug report #872007,
regarding dh_strip fails randomly "No such file or directory" during parallel 
builds
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.)


-- 
872007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 10.7.2
Severity: serious
File: /usr/bin/dh_strip
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:fuse

Hi Niels,

I noticed that cross building fuse failed. Once. The issue isn't
reproducible, at least not easily. It also FTBFSed on the jenkins
reproducible builds:

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

| dh_strip --dbg-package=fuse-dbg
| chmod: cannot access 
'debian/fuse-dbg/usr/lib/debug/.build-id/2b/bbc8403aec6a1ea2abd3cf6467439e0c4ae1ed.debug':
 No such file or directory
| dh_strip: chmod 0644 -- 
debian/fuse-dbg/usr/lib/debug/.build-id/2b/bbc8403aec6a1ea2abd3cf6467439e0c4ae1ed.debug
 returned exit code 1

I attempted to natively build fuse 13 times now (with parallel=100) and
it failed twice like that. Without parallel, I couldn't reproduce it at
all.

Whatever is broken over here, it likely resides in debhelper and makes
fuse FTBFS randomly. I wish I could provide more details.

Helmut
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 10.8

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Sep 2017 15:07:38 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 10.8
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 824221 866619 870892 870905 872007 872274 872510 873043
Changes:
 debhelper (10.8) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * Dh_Lib: Introduce a qx_cmd sub to behave like a mix of qx
 and doit (i.e. avoid the shell while capturing stdout).
   * dh_makeshlibs: Avoid forking a shell when calling objdump in
 compat 11.
   * dh_shlibdeps: Avoid forking a shell when calling file.
   * dh_shlibdeps: Avoid passing files with "newline" to
 subprocesses.
   * dh_installdocs: Ignore missing files in compat 11 for packages
 that are not processed (e.g. arch:all packages during a -B build).
 Thanks to Jens Reyer for reporting the issue.  (Closes: #870892)
   * dh_installexamples: Ditto.
   * dh_installinfo: Ditto.
   * dh_installman: Ditto.
   * dh_compress: Avoid forking a shell for a find command.
   * dh_gconf: Ditto.
   * dh_installgsettings: Ditto.
   * dh_perl: Avoid forking a shell for a dpkg call.
   * dh_gencontrol: Set the priority of all dbgsym packages to
 optional to be compliant with Standards-Version 4.0.1.
 Thanks to Mattia Rizzolo for the report.  (Closes: #870905)
   * dh_installdocs: Accept "nodoc" via DEB_BUILD_OPTIONS as well.
 Thanks to Sébastien Villemot for the suggestion.
 (Closes: #866619)
   * dh_installexamples: Ditto.
   * dh_installinfo: Ditto.
   * dh_installman: Ditto.
   * dh_installwm: Ditto.
   * debhelper.pod: Tweak text for some compat 11 changes.
   * dh_installdeb: Stop emitting versioned Pre-Depends on dpkg for
 symlink_to_dir and dir_to_symlink maintscripts.  The version
 requirements are satisfied in oldoldstable.
   * dh_installdocs: Merge two chmod calls to save a fork+exec.
   * dh_strip: Disable parallelism when --dbg-package is used as it
 causes non-deterministic failures in some cases.  

Bug#874220: marked as pending

[Jochen Sprickerhof]

tag 874220 pending
thanks

Hello,

Bug #874220 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/openni2.git/commit/?id=e76b051

---
commit e76b0517fc61886eb461dd393fc2c3ffb8d39f31
Author: Jochen Sprickerhof 
Date:   Sat Sep 9 16:17:52 2017 +0200

Update changelog for 2.2.0.33+dfsg-10 release

diff --git a/debian/changelog b/debian/changelog
index a2650a7..db8d2ed 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+openni2 (2.2.0.33+dfsg-10) unstable; urgency=medium
+
+  * Add patch for arm.
+Thanks to Adrian Bunk (Closes: #874220)
+  * Remove flags, not needed anymore
+
+ -- Jochen Sprickerhof   Sat, 09 Sep 2017 16:17:46 +0200
+
 openni2 (2.2.0.33+dfsg-9) unstable; urgency=medium
 
   * Add patch for GCC7 (Closes: #871157)

Processed: Bug#874220 marked as pending

[Debian Bug Tracking System]

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

> tag 874220 pending
Bug #874220 [src:openni2] openni2 mustn't build with NEON on armel/armhf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#874764: 389-ds-base-dev: broken symlinks: /usr/lib//dirsrv/lib{sds, nunc-stans, ns-dshttpd}.so

[Andreas Beckmann]

Package: 389-ds-base-dev
Version: 1.3.6.7-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m21.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/dirsrv/libsds.so -> libsds.so.0.0.0
  /usr/lib/x86_64-linux-gnu/dirsrv/libnunc-stans.so -> libnunc-stans.so.0.1.0
  /usr/lib/x86_64-linux-gnu/dirsrv/libns-dshttpd.so -> libns-dshttpd-1.3.6.7.so

Either these libs should have been in 389-ds-base-libs,
or 389-ds-base-dev needs to depend on 389-ds-base which currently
ships the targets.


cheers,

Andreas


389-ds-base-dev_1.3.6.7-4.log.gz
Description: application/gzip

Processed: Re: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.4.1-12
Bug #872233 {Done: Matthias Klose } 
[lib32objc-5-dev,libx32objc-5-dev] lib{, x}32objc-5-dev: broken symlink: 
/usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> 
../../../../../lib32/libobjc_gc.so.4
Marked as found in versions gcc-5/5.4.1-12; no longer marked as fixed in 
versions gcc-5/5.4.1-12 and reopened.

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

Bug#872233: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Andreas Beckmann]

Followup-For: Bug #872233
Control: found -1 5.4.1-12

Hi,

the broken symlinks are still here:

0m46.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc/x86_64-linux-gnu/5/32/libobjc_gc.so -> 
../../../../../lib32/libobjc_gc.so.4

0m57.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc/x86_64-linux-gnu/5/x32/libobjc_gc.so -> 
../../../../../libx32/libobjc_gc.so.4


Andreas

Bug#874752: ndiswrapper-dkms: module FTBFS for Linux 4.12

[Andreas Beckmann]

Package: ndiswrapper-dkms
Version: 1.60-3
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

ndiswrapper-dkms fails to build a module for Linux 4.12:

Selecting previously unselected package ndiswrapper-dkms.
(Reading database ... 34989 files and directories currently installed.)
Preparing to unpack .../ndiswrapper-dkms_1.60-3_all.deb ...
Unpacking ndiswrapper-dkms (1.60-3) ...
Setting up ndiswrapper-dkms (1.60-3) ...
Loading new ndiswrapper-1.60 DKMS files...
It is likely that 4.6.0-1-amd64 belongs to a chroot's host
Building for 4.12.0-1-amd64
Building initial module for 4.12.0-1-amd64
Error! Bad return status for module build on kernel: 4.12.0-1-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.


DKMS make.log for ndiswrapper-1.60 for kernel 4.12.0-1-amd64 (x86_64)
Sat Sep  9 13:09:26 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.12.0-1-amd64'
  LD  /var/lib/dkms/ndiswrapper/1.60/build/built-in.o
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
  MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0,
 from /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.c:20:
/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.c: In function 'mp_reset':
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:163:7: error: implicit 
declaration of function 'signal_pending' [-Werror=implicit-function-declaration]
   if (signal_pending(current)) {   \
   ^
/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.c:67:7: note: in expansion of 
macro 'wait_condition'
   if (wait_condition((wnd->ndis_req_done > 0), 0,
   ^~
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/lin2win.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.12.0-1-common/scripts/Makefile.build:307: recipe for 
target '/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o' failed
make[3]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o] Error 1
make[3]: *** Waiting for unfinished jobs
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
'NdisMIndicateReceivePacket':
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: 'struct net_device' 
has no member named 'last_rx'
   wnd->net_dev->last_rx = jiffies;
   ^~
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 'EthRxIndicateHandler':
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: 'struct net_device' 
has no member named 'last_rx'
  wnd->net_dev->last_rx = jiffies;
  ^~
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
'NdisMTransferDataComplete':
/var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: 'struct net_device' 
has no member named 'last_rx'
  wnd->net_dev->last_rx = jiffies;
  ^~
/usr/src/linux-headers-4.12.0-1-common/scripts/Makefile.build:307: recipe for 
target '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' failed
make[3]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] Error 1
In file included from /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.c:16:0:
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.c: In function 
'KeWaitForMultipleObjects':
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:163:7: error: implicit 
declaration of function 'signal_pending' [-Werror=implicit-function-declaration]
   if (signal_pending(current)) {   \
   ^
/var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.c:1127:9: note: in expansion of 
macro 'wait_condition'
   res = wait_condition(wait_done, wait_hz, TASK_INTERRUPTIBLE);
 ^~
cc1: some warnings being treated as errors

Bug#874751: blktap-dkms: module FTBFS for Linux 4.12

[Andreas Beckmann]

Package: blktap-dkms
Version: 2.0.93-0.10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

Selecting previously unselected package blktap-dkms.
(Reading database ... 34976 files and directories currently installed.)
Preparing to unpack .../blktap-dkms_2.0.93-0.10_amd64.deb ...
Unpacking blktap-dkms (2.0.93-0.10) ...
Setting up blktap-dkms (2.0.93-0.10) ...
Loading new blktap-2.0.93 DKMS files...
It is likely that 4.6.0-1-amd64 belongs to a chroot's host
Building for 4.12.0-1-amd64
Building initial module for 4.12.0-1-amd64
Error! Bad return status for module build on kernel: 4.12.0-1-amd64 (x86_64)
Consult /var/lib/dkms/blktap/2.0.93/build/make.log for more information.


DKMS make.log for blktap-2.0.93 for kernel 4.12.0-1-amd64 (x86_64)
Sat Sep  9 13:04:28 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.12.0-1-amd64'
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/control.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/ring.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/device.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/request.o
  CC [M]  /var/lib/dkms/blktap/2.0.93/build/sysfs.o
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/request.c:31:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^~
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^~
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro '__RD32'
  ((int)__RD32((BLKTAP_PAGE_SIZE -\
^~
/var/lib/dkms/blktap/2.0.93/build/blktap.h:77:41: note: in expansion of macro 
'BLKTAP_RING_SIZE'
  struct blktap_request *pending[BLKTAP_RING_SIZE];
 ^~~~
/var/lib/dkms/blktap/2.0.93/build/request.c: In function 'blktap_request_alloc':
/var/lib/dkms/blktap/2.0.93/build/request.c:138:2: warning: this 'if' clause 
does not guard... [-Wmisleading-indentation]
  if (request)
  ^~
/var/lib/dkms/blktap/2.0.93/build/request.c:140:6: note: ...this statement, but 
the latter is misleadingly indented as if it is guarded by the 'if'
  sg_init_table(request->sg_table, ARRAY_SIZE(request->sg_table));
  ^
In file included from /var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:66:0,
 from /var/lib/dkms/blktap/2.0.93/build/blktap.h:33,
 from /var/lib/dkms/blktap/2.0.93/build/control.c:30:
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:119:24: warning: variably 
modified 'pending' at file scope
sizeof(((struct blktap_sring *)0)->ring[0])))
^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:15:59: 
note: in definition of macro '__RD2'
 #define __RD2(_x)  (((_x) & 0x0002) ? 0x2 : ((_x) & 0x1))
   ^~
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:17:66: 
note: in expansion of macro '__RD4'
 #define __RD8(_x)  (((_x) & 0x00f0) ? __RD4((_x)>>4)<<4: __RD4(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:18:66: 
note: in expansion of macro '__RD8'
 #define __RD16(_x) (((_x) & 0xff00) ? __RD8((_x)>>8)<<8: __RD8(_x))
  ^
/usr/src/linux-headers-4.12.0-1-common/include/xen/interface/io/ring.h:19:66: 
note: in expansion of macro '__RD16'
 #define __RD32(_x) (((_x) & 0x) ? __RD16((_x)>>16)<<16 : __RD16(_x))
  ^~
/var/lib/dkms/blktap/2.0.93/build/linux-blktap.h:117:8: note: in expansion of 
macro 

Bug#874750: langford-dkms: module FTBFS against Linux 4.12: implicit declaration of function 'copy_to_user'

[Andreas Beckmann]

Package: langford-dkms
Version: 0.0.20130228-5
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

langford-dkms fails to build a module for Linux 4.12:

Selecting previously unselected package langford-dkms.
(Reading database ... 34967 files and directories currently installed.)
Preparing to unpack .../langford-dkms_0.0.20130228-5_all.deb ...
Unpacking langford-dkms (0.0.20130228-5) ...
Setting up langford-dkms (0.0.20130228-5) ...
Loading new langford-0.0.20130108 DKMS files...
It is likely that 4.6.0-1-amd64 belongs to a chroot's host
Building for 4.12.0-1-amd64
Building initial module for 4.12.0-1-amd64
Error! Bad return status for module build on kernel: 4.12.0-1-amd64 (x86_64)
Consult /var/lib/dkms/langford/0.0.20130108/build/make.log for more information.


DKMS make.log for langford-0.0.20130108 for kernel 4.12.0-1-amd64 (x86_64)
Sat Sep  9 12:59:30 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.12.0-1-amd64'
  LD  /var/lib/dkms/langford/0.0.20130108/build/built-in.o
  CC [M]  /var/lib/dkms/langford/0.0.20130108/build/langford.o
/var/lib/dkms/langford/0.0.20130108/build/langford.c: In function 'cdev_read':
/var/lib/dkms/langford/0.0.20130108/build/langford.c:383:3: error: implicit 
declaration of function 'copy_to_user' [-Werror=implicit-function-declaration]
   copy_to_user(buf, cdev_read_buff + cdev_read_buff_start, MIN(len, 
CDEVBUFFSIZE - cdev_read_buff_start));
   ^~~~
/var/lib/dkms/langford/0.0.20130108/build/langford.c: In function 'cdev_write':
/var/lib/dkms/langford/0.0.20130108/build/langford.c:428:3: error: implicit 
declaration of function 'copy_from_user' [-Werror=implicit-function-declaration]
   copy_from_user(cdev_write_buff + cdev_write_buff_end, buf, MIN(len, 
CDEVBUFFSIZE - cdev_write_buff_end));
   ^~
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.12.0-1-common/scripts/Makefile.build:313: recipe for 
target '/var/lib/dkms/langford/0.0.20130108/build/langford.o' failed
make[3]: *** [/var/lib/dkms/langford/0.0.20130108/build/langford.o] Error 1
/usr/src/linux-headers-4.12.0-1-common/Makefile:1532: recipe for target 
'_module_/var/lib/dkms/langford/0.0.20130108/build' failed
make[2]: *** [_module_/var/lib/dkms/langford/0.0.20130108/build] Error 2
Makefile:152: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.12.0-1-amd64'


Andreas

Processed: user debian...@lists.debian.org, usertagging 868637, affects 868637, usertagging 867475 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 868637 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 868637 + libghc-yi-dev libghc-yi-prof
Bug #868637 [src:yi] yi build-depends on libghc-yi-rope-dev (< 0.8) but 0.8-1 
is to be installed
Added indication that 868637 affects libghc-yi-dev and libghc-yi-prof
> usertags 867475 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 867475 + libghc-test-framework-th-prime-dev 
> libghc-test-framework-th-prime-prof
Bug #867475 [src:haskell-test-framework-th-prime] 
haskell-test-framework-th-prime FTBFS: Expecting one more argument to `Module'
Added indication that 867475 affects libghc-test-framework-th-prime-dev and 
libghc-test-framework-th-prime-prof
> usertags 810284 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 870664 serious
Bug #870664 [src:hkl] hkl: build-depends on obsolete emacs24
Severity set to 'serious' from 'important'
> tags 870664 + sid buster
Bug #870664 [src:hkl] hkl: build-depends on obsolete emacs24
Added tag(s) buster and sid.
> usertags 868481 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 868481 + libhkl-dev
Bug #868481 [src:hkl] hkl FTBFS with Bullet 2.86.1
Added indication that 868481 affects libhkl-dev
> found 855578 1.4.0-1
Bug #855578 [python-scrapy,python3-scrapy] python{,3}-scrapy: leaves 
alternatives after purge: /usr/bin/scrapy
Marked as found in versions python-scrapy/1.4.0-1.
> found 872198 9.6.5-1
Bug #872198 [postgresql-9.6] postgresql-9.6: unowned directory after purge: 
/etc/postgresql/9.6/main/conf.d/
Marked as found in versions postgresql-9.6/9.6.5-1.
> found 852116 6.0.10-4
Bug #852116 [zorp] zorp: unowned files after purge (policy 6.8, 10.8): 
/etc/zorp/dh.pem
Marked as found in versions zorp/6.0.10-4.
> found 771085 3.25.90.1-2
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): 
/etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.25.90.1-2.
> found 668393 0.5.17-1.1
Bug #668393 [dtc-xen] dtc-xen: unowned files after purge (policy 6.8, 10.8)
Marked as found in versions dtc-xen/0.5.17-1.1.
> retitle 668393 dtc-xen: unowned directory after purge: /etc/xen/auto/
Bug #668393 [dtc-xen] dtc-xen: unowned files after purge (policy 6.8, 10.8)
Changed Bug title to 'dtc-xen: unowned directory after purge: /etc/xen/auto/' 
from 'dtc-xen: unowned files after purge (policy 6.8, 10.8)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
668393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668393
771085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085
852116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852116
855578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855578
867475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867475
868481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868481
868637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868637
870664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870664
872198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: courier-mta, courier-imap, courier-pop: fails to install: install: target '' is not a directory: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.18.0+0.77.0-3
Bug #874736 [courier-mta,courier-imap,courier-pop] courier-mta, courier-imap, 
courier-pop: fails to install: install: target '' is not a directory: No such 
file or directory
There is no source info for the package 'courier-mta' at version 
'4.18.0+0.77.0-3' with architecture ''
There is no source info for the package 'courier-pop' at version 
'4.18.0+0.77.0-3' with architecture ''
Marked as found in versions courier/0.77.0-3.

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

Bug#874736: courier-mta, courier-imap, courier-pop: fails to install: install: target '' is not a directory: No such file or directory

[Andreas Beckmann]

Package: courier-mta,courier-imap,courier-pop
Version: 0.77.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.18.0+0.77.0-3

Hi,

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

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

  Selecting previously unselected package courier-mta.
  (Reading database ... 
(Reading database ... 6578 files and directories currently installed.)
  Preparing to unpack .../courier-mta_0.77.0-3_amd64.deb ...
  Adding 'diversion of /usr/bin/addcr to /usr/bin/addcr.ucspi-tcp by 
courier-mta'
  Adding 'diversion of /usr/share/man/man1/addcr.1.gz to 
/usr/share/man/man1/addcr.ucspi-tcp.1.gz by courier-mta'
  Unpacking courier-mta (0.77.0-3) ...
  Setting up courier-mta (0.77.0-3) ...
  update-alternatives: using /usr/bin/lockmail.courier to provide 
/usr/bin/lockmail (lockmail) in auto mode
  update-alternatives: using /usr/bin/preline.courier to provide 
/usr/bin/preline (preline) in auto mode
  /run/courier/esmtpd.pid.lock: No such file or directory
  install: target '' is not a directory: No such file or directory
  dpkg: error processing package courier-mta (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   courier-mta


cheers,

Andreas


courier-mta_0.77.0-3.log.gz
Description: application/gzip

Bug#874734: python-ecflow: fails to install: syntax error in ecflow/sms2ecf.py

[Andreas Beckmann]

Package: python-ecflow
Version: 4.6.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python-ecflow.
  (Reading database ... 
(Reading database ... 5424 files and directories currently installed.)
  Preparing to unpack .../python-ecflow_4.6.1-1_amd64.deb ...
  Unpacking python-ecflow (4.6.1-1) ...
  Setting up python-ecflow (4.6.1-1) ...
File "/usr/lib/python2.7/dist-packages/ecflow/sms2ecf.py", line 164
  print (line, file=fop)
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python-ecflow (--configure):
   subprocess installed post-installation script returned error exit status 101
  Errors were encountered while processing:
   python-ecflow


cheers,

Andreas


python-ecflow_4.6.1-1.log.gz
Description: application/gzip

Processed: retitle 810284 to yubico-piv-tool: newer upstream release 1.4.3, needed by yubikey-piv-manager ...

[Debian Bug Tracking System]

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

> retitle 810284 yubico-piv-tool: newer upstream release 1.4.3, needed by 
> yubikey-piv-manager
Bug #810284 [src:yubico-piv-tool] yubico-piv-tool: newer upstream release
Changed Bug title to 'yubico-piv-tool: newer upstream release 1.4.3, needed by 
yubikey-piv-manager' from 'yubico-piv-tool: newer upstream release'.
> affects 810284 + yubikey-piv-manager
Bug #810284 [src:yubico-piv-tool] yubico-piv-tool: newer upstream release 
1.4.3, needed by yubikey-piv-manager
Added indication that 810284 affects yubikey-piv-manager
> severity 810284 serious
Bug #810284 [src:yubico-piv-tool] yubico-piv-tool: newer upstream release 
1.4.3, needed by yubikey-piv-manager
Severity set to 'serious' from 'wishlist'
> tags 810284 + sid buster
Bug #810284 [src:yubico-piv-tool] yubico-piv-tool: newer upstream release 
1.4.3, needed by yubikey-piv-manager
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#874562: marked as done (python-bloom: python-rosdep was renamed to python-rosdep2)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 10:34:42 +
with message-id 
and subject line Bug#874562: fixed in ros-bloom 0.5.26-6
has caused the Debian Bug report #874562,
regarding python-bloom: python-rosdep was renamed to python-rosdep2
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.)


-- 
874562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-bloom
Version: 0.5.26-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

python-bloom still depends on python-rosdep, but that was renamed to
python-rosdep2.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: ros-bloom
Source-Version: 0.5.26-6

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-bloom package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Sep 2017 11:33:23 +0200
Source: ros-bloom
Binary: python-bloom python3-bloom
Architecture: source
Version: 0.5.26-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-bloom - Bloom is a release automation tool from Robot OS (Python 2)
 python3-bloom - Bloom is a release automation tool from Robot OS (Python 3)
Closes: 874562
Changes:
 ros-bloom (0.5.26-6) unstable; urgency=medium
 .
   * Add overrides for rosdep2 rename (Closes: #874562)
Checksums-Sha1:
 06ab167485b88dc626599af8a474fddf9a5902b7 2411 ros-bloom_0.5.26-6.dsc
 5aaf3b8ec4d639a0191be8a1587bb9c2f57e7b61 2900 ros-bloom_0.5.26-6.debian.tar.xz
 a9f5066ba8f94b2308672d02432508d9fd03e665 7445 
ros-bloom_0.5.26-6_source.buildinfo
Checksums-Sha256:
 e9b35de76d95a28b4b195fe7d6de8bc3ff75cf5dd52b3da815c89271c38b1a41 2411 
ros-bloom_0.5.26-6.dsc
 70095ce303ef197748c80aaff80246f264f0799da5e592f73d3b6848f5137918 2900 
ros-bloom_0.5.26-6.debian.tar.xz
 dff943acc6059cd7a4b7e8495ac5c69946f08651a2f2a3b5174614f5c745aa97 7445 
ros-bloom_0.5.26-6_source.buildinfo
Files:
 7c1f9acdd1f0b36739853bd1203f0b74 2411 python optional ros-bloom_0.5.26-6.dsc
 1577001a48e8557155ee7574e82b690a 2900 python optional 
ros-bloom_0.5.26-6.debian.tar.xz
 c460090d041d0449bf2b9854649dc086 7445 python optional 
ros-bloom_0.5.26-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlmzvjEUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDNeaw//SuUHcp2aRIm8fFPXtWYITuTWDAoV
j29ak0sbBZd/SZl72nkWvwRKmbm8qm979tPUJObcrvtILbkdJhOVtmNiikR5fsp7
lyLf15jN2NrILJV4iqZtTUJ7VjqvUXu43hCDWdG5fc+pG2c5JMW9NUjBl8T7XaA5
NXckS0XC8JAlIXXaqUkHqy1PPzIo+bshLFDaNyZj82rkpHetBV0Ho+WNfQAF6m99
r8jxO7nBckAhG0xdbCMHKa+Na6q7WEZfW99hp/eiO0f/dE4ZmdVYxt4bTA+W6UG4
+VEZXq0fpLwHQfXmUZGdkFHPpd8CcYDAA4LZWom8IWmBI4bAKl+IjOVqbKDiK/ph
EmPRtHZPJufeAWy3KjuU6H4UEF18kWVZEgeYPvKIsgVbHqF64gmAKytc0wI8lXdF
X5jFFwPpvUzzSU6GXhEwYGLQhtbz5vYYjHAiX/79T6p1MWUdh9Cb90swhKkyJ11s
19Puwgrtd+tcQL3PZHlNUFdfqsbFC5kFlI289iyshdpYeVnYwN+94VyS9ip4Zrve
9iQjaIA7jOSZgL76ZbWB/SAumZAoUJ5Ibx9CZMEClE9hTsc7FK1SpxHfTMPnFcaT
xwlSV/dqWOwgtNCETeM3mv0jnjBBmgE5COJjFkcZfEOsIXCWuK5l3HHWXeJJQkuX
Q86TTDydcL0z8wc=
=EB0z
-END PGP SIGNATURE End Message ---

Processed: Found in version h5py/2.7.1-1

[Debian Bug Tracking System]

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

> notfound 874712 2.7.0-1
Bug #874712 [python-h5py] python-h5py: all arches FTBFS
No longer marked as found in versions h5py/2.7.0-1.
> found 874712 2.7.1-1
Bug #874712 [python-h5py] python-h5py: all arches FTBFS
There is no source info for the package 'python-h5py' at version '2.7.1-1' with 
architecture ''
Unable to make a source version for version '2.7.1-1'
Marked as found in versions 2.7.1-1.
> thanks
Stopping processing here.

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

Bug#874191: gdm3 started users start in wrong context

[Laurent Bigonville]

On Sun, 03 Sep 2017 18:02:30 -0400 Harlan Lieberman-Berg 
 wrote:


> Hello maintainers,

Hello,

>
> It seems that shells started via Gnome start with the wrong context.
> Logging in from a console shell gives me an id of
> unconfined_u:unconfined_r:unconfined_t:s0-s0, whereas terminals opened
> inside Gnome give me a context of system_u:system_r:initrc_t:s0.

How are you checking the context? With gnome-terminal? Could you please 
test with xterm (or an other terminal emulator?) as well?


If I'm correct, the problem only exists for processes started by 
dbus/systemd user session.


In /etc/selinux/default/contexts/users/unconfined_u, could you please 
add the following line and try again?


system_r:init_t:s0  unconfined_r:unconfined_t:s0

Regards,

Laurent Bigonville

Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.

[markus]

Package: libcoin80v5
Version: 3.1.4~abc9f50+dfsg1-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) the included 
copy of it in libcoin results in segfaults of any program that uses libexpat1. 
Specifically any program that uses xml from python and links against libcoin 
will segfault.

The stacktrace looks like it is a problem with libexpat1 leading to a segfault 
in XML_SetHashSalt - however looking at that function there is no way it could 
possibly segfault - unless of course the provided XMLParser pointer does not 
actually point to what expat expects to be an XMLParser - which is indeed the 
case because the XMLParser instance was created by a call into lobcoin which is 
still on libexpat 2.2.0.

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

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

Versions of packages libcoin80v5 depends on:
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-3
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libstdc++67.2.0-3
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2

libcoin80v5 recommends no packages.

Versions of packages libcoin80v5 suggests:
ii  libbz2-1.0 1.0.6-8.1
ii  libfreetype6   2.8-0.2
pn  libopenal0a
ii  libsimage-dev  1.7.1~2c958a6.dfsg-4
ii  zlib1g 1:1.2.8.dfsg-5

-- no debconf information

Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXQt

[Manuel A. Fernandez Montecelo]

Control: severity -1 serious


Hi,

2017-09-09 5:33 GMT+02:00 Simon Quigley :
> Control: retitle -1 razorqt: Razor-Qt dead upstream, superseded by LXQt
> Control: severity -1 grave
>
> Hello,
>
> Bump on this. razorqt has been dead upstream for several years now
> (several LXQt releases have made it in Debian, even making it into
> Stretch), and popcon statistics have dropped. I would like to get this
> removed as part of the effort to remove Qt 4 from the archive for Buster
> as announced[1].
>
>> so I would just feel bad removing it from the archive at this
>> point.
> I don't see a reason to keep this in the archive, but I'm not the
> maintainer... I don't see an upload since 2014, and since it's not
> maintained upstream, there could be severe bugs or security issues in
> the packaged version that have not been discovered. In my opinion this
> is a compelling reason to finally drop it, and it might just be better
> than keeping it in the archive.
>
> Thoughts?

I already explained this in the bug report multiple times in different
messages of this bug report.

Yes, the package will have to be removed beause Qt4 is going to be
removed, I already said that in the original submission.  It turns out
that Qt4 was not removed in 6 months time, as I expected then, and 2.5
years later is still here.

Since there are no upstream releases and haven't been important bugs
reported, coupled with the pending removal, there have been no strong
reasons for new uploads.  However, I use it on a daily basis on
several computers and it works fine.

There are many packages, including similar desktops/windows managers,
in the same situation, and they were even shipped in the last stable
(unlike razorqt).  Razorqt is still more popular than other WMs, even
not being in the last stable, and contrary to my expectations users
didn't migrate en-masse to LXQt, popcon reports 70% of the users at
the peak time in 2015.


So: If Qt4 is going to be removed within a month, by all means, let's
go ahead and remove razorqt now.  But if the news are that it's going
to be removed "in buster release cycle", which might mean even 2 years
time, and perhaps even it ends up not being removed (as the
announcement says) please lets this package be until it actually
blocks the removal of Qt4.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Processed: Re: Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXQt

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784181 [src:razorqt] razorqt: Razor-Qt dead upstream, superseded by LXQt
Severity set to 'serious' from 'grave'

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

Bug#873694: marked as done (python-greenlet FTBFS on ppc64el: error: PIC register clobbered by 'r2' in 'asm')

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 07:19:46 +
with message-id 
and subject line Bug#873694: fixed in python-greenlet 0.4.12-2
has caused the Debian Bug report #873694,
regarding python-greenlet FTBFS on ppc64el: error: PIC register clobbered by 
'r2' in 'asm'
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=python-greenlet=ppc64el=0.4.12-1=1504055313=0

...
running build_ext
building 'greenlet' extension
creating build
creating build/temp.linux-ppc64le-3.6
powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c greenlet.c -o 
build/temp.linux-ppc64le-3.6/greenlet.o -fno-tree-dominator-opts
In file included from slp_platformselect.h:16:0,
 from greenlet.c:328:
platform/switch_ppc64_linux.h: In function 'slp_switch':
platform/switch_ppc64_linux.h:72:5: error: PIC register clobbered by 'r2' in 
'asm'
 __asm__ volatile ("" : : : REGS_TO_SAVE);
 ^~~
platform/switch_ppc64_linux.h:85:5: error: PIC register clobbered by 'r2' in 
'asm'
 __asm__ volatile ("" : : : REGS_TO_SAVE);
 ^~~
error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1
debian/rules:25: recipe for target 'build-python3.6' failed
make[1]: *** [build-python3.6] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2



http://gcc.gnu.org/gcc-7/changes.html
- GCC now diagnoses inline assembly that clobbers register r2. This has always 
been invalid code, and is no longer quietly tolerated.
--- End Message ---
--- Begin Message ---
Source: python-greenlet
Source-Version: 0.4.12-2

We believe that the bug you reported is fixed in the latest version of
python-greenlet, 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.
Laszlo Boszormenyi (GCS)  (supplier of updated python-greenlet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Sep 2017 06:40:06 +
Source: python-greenlet
Binary: python-greenlet-dbg python3-greenlet-dbg python-greenlet-doc 
python-greenlet-dev python-greenlet python3-greenlet
Architecture: source amd64 all
Version: 0.4.12-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-greenlet - Lightweight in-process concurrent programming
 python-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
 python-greenlet-dev - Lightweight in-process concurrent programming - 
development files
 python-greenlet-doc - Lightweight in-process concurrent programming - 
documentation
 python3-greenlet - Lightweight in-process concurrent programming (python3)
 python3-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
Closes: 873694
Changes:
 python-greenlet (0.4.12-2) unstable; urgency=medium
 .
   * Don't clobber 'r2' register on ppc64el (closes: #873694).
Checksums-Sha1:
 ee372bda51e780701f7ef517512427de2eeeae4b 2320 python-greenlet_0.4.12-2.dsc
 e3bd5ac2710d099c07fa68071c96ca63bc8ebf19 7176 
python-greenlet_0.4.12-2.debian.tar.xz
 d32955782932077667cb79e1204f948878cd1762 59690 
python-greenlet-dbg_0.4.12-2_amd64.deb
 3f4bee82ebce4f4cbe42ed9816fee1551dbba4f3 6904 
python-greenlet-dev_0.4.12-2_amd64.deb
 b201f1308724f838bb04be82ed2a0e1d292857d3 42888 
python-greenlet-doc_0.4.12-2_all.deb
 4dfbcca7a7754e49edefd1de4e6778846d62eee2 10922 
python-greenlet_0.4.12-2_amd64.buildinfo
 0155ab8504c5585162ab33fbc23dacefea76bf00 18706 
python-greenlet_0.4.12-2_amd64.deb
 dc8f34674093d897f96efa970f9094cdc3a7c317 91700 

Processed: Re: open-infrastructure-system-boot: Update udevadm path

[Debian Bug Tracking System]

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

> tag 852571 pending
Bug #852571 [open-infrastructure-system-boot] open-infrastructure-system-boot: 
Update udevadm path
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852571: open-infrastructure-system-boot: Update udevadm path

[Daniel Baumann]

tag 852571 pending
thanks

got a few other changes to test, will upload new release tomorrow.

Regards,
Daniel

Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Dominik Kupschke]

Hi,

i attach some additional information.

These are all installed mesa packages on my system:

~$ dpkg -l | grep mesa
ii  libegl-mesa0:amd6417.2.0-2  
amd64free implementation of the EGL API -- Mesa vendor library
ii  libegl-mesa0:i386 17.2.0-2  
i386 free implementation of the EGL API -- Mesa vendor library
ii  libegl1-mesa:amd6417.2.0-2  
amd64transitional dummy package
ii  libegl1-mesa:i386 17.2.0-2  
i386 transitional dummy package
ii  libgl1-mesa-dev:amd64 17.2.0-2  
amd64free implementation of the OpenGL API -- GLX development files
ii  libgl1-mesa-dri:amd64 17.2.0-2  
amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i386  17.2.0-2  
i386 free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64 17.2.0-2  
amd64transitional dummy package
ii  libgl1-mesa-glx:i386  17.2.0-2  
i386 transitional dummy package
ii  libglapi-mesa:amd64   17.2.0-2  
amd64free implementation of the GL API -- shared library
ii  libglapi-mesa:i38617.2.0-2  
i386 free implementation of the GL API -- shared library
ii  libgles2-mesa:amd64   17.2.0-2  
amd64transitional dummy package
ii  libglu1-mesa:amd649.0.0-2.1 
amd64Mesa OpenGL utility library (GLU)
ii  libglu1-mesa:i386 9.0.0-2.1 
i386 Mesa OpenGL utility library (GLU)
ii  libglx-mesa0:amd6417.2.0-2  
amd64free implementation of the OpenGL API -- GLX vendor library
ii  libglx-mesa0:i386 17.2.0-2  
i386 free implementation of the OpenGL API -- GLX vendor library
ii  libosmesa6:amd64  17.2.0-2  
amd64Mesa Off-screen rendering extension
ii  libosmesa6:i386   17.2.0-2  
i386 Mesa Off-screen rendering extension
ii  libwayland-egl1-mesa:amd6417.2.0-2  
amd64implementation of the Wayland EGL platform -- runtime
ii  mesa-common-dev:amd64 17.2.0-2  
amd64Developer documentation for Mesa
ii  mesa-common-dev:i386  17.2.0-2  
i386 Developer documentation for Mesa
ii  mesa-opencl-icd:amd64 17.2.0-2  
amd64free implementation of the OpenCL API -- ICD runtime
ii  mesa-utils8.3.0-5   
amd64Miscellaneous Mesa GL utilities
ii  mesa-va-drivers:amd64 17.2.0-2  
amd64Mesa VA-API video acceleration drivers
ii  mesa-va-drivers:i386  17.2.0-2  
i386 Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:amd64  17.2.0-2  
amd64Mesa VDPAU video acceleration drivers  

  
ii  mesa-vdpau-drivers:i386   17.2.0-2  
i386 Mesa VDPAU video acceleration drivers  

  
ii  mesa-vulkan-drivers:amd64 17.2.0-2  
amd64Mesa Vulkan graphics drivers   

This is my Xorg.0.log:

[ 11371.708] (--) Log file renamed from "/var/log/Xorg.pid-23713.log" to 
"/var/log/Xorg.0.log" 


Regards
Dominik




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

Bug#852589: marked as done (ovirt-guest-agent: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 06:49:15 +
with message-id 
and subject line Bug#852589: fixed in ovirt-guest-agent 1.0.13.dfsg-2
has caused the Debian Bug report #852589,
regarding ovirt-guest-agent: Update udevadm path
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.)


-- 
852589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ovirt-guest-agent
Version: 1.0.12.2.dfsg-2
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package ovirt-guest-agent does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Source: ovirt-guest-agent
Source-Version: 1.0.13.dfsg-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated 
ovirt-guest-agent package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Sep 2017 06:02:22 +
Source: ovirt-guest-agent
Binary: ovirt-guest-agent
Architecture: source all
Version: 1.0.13.dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 ovirt-guest-agent - daemon that resides within guest virtual machines
Closes: 852589
Changes:
 ovirt-guest-agent (1.0.13.dfsg-2) unstable; urgency=medium
 .
   * Update udevadm path in RPM build scripts to prevent false positive matches
 (closes: #852589).
   * Remove autotools-dev and dh-autoreconf build dependencies.
Checksums-Sha1:
 6a98a47484a87862139c3add9259e00e37770bbe 1953 
ovirt-guest-agent_1.0.13.dfsg-2.dsc
 29c11644ba8f65ea05643efc87676807ff6e2143 9044 
ovirt-guest-agent_1.0.13.dfsg-2.debian.tar.xz
 0fcb117b3c5bfd814b6abf3b444781bacf833591 54638 
ovirt-guest-agent_1.0.13.dfsg-2_all.deb
 b8455a3d6b868a007ac6f0d7b9ab53a0258319bf 7696 
ovirt-guest-agent_1.0.13.dfsg-2_amd64.buildinfo
Checksums-Sha256:
 9feb2a3f450531bb3efe00be745558e9bffbf9ad6960b4a97e76e8655e24d7f2 1953 
ovirt-guest-agent_1.0.13.dfsg-2.dsc
 d857a9f7665e81c5c5cb8a9ebf6b27c1bb4c954199ce443b372ec0cd958c6cf4 9044 
ovirt-guest-agent_1.0.13.dfsg-2.debian.tar.xz
 79129e8ca84cedc35336d16d2753ee637d862590ab5a405683a6546f57cd222c 54638 
ovirt-guest-agent_1.0.13.dfsg-2_all.deb
 0f9c594925dd98f62df92c2a9dd169e2a4752e2e536841c6cc55c87e43d41998 7696 
ovirt-guest-agent_1.0.13.dfsg-2_amd64.buildinfo
Files:
 af4a42314594c36ce5e4ee4263b35ec0 1953 utils extra 
ovirt-guest-agent_1.0.13.dfsg-2.dsc
 cba647d22a300c1f273c3d70a4e8cc71 9044 utils extra 
ovirt-guest-agent_1.0.13.dfsg-2.debian.tar.xz
 63dfba47d1c83b9cbc3db4db751229eb 54638 utils extra 
ovirt-guest-agent_1.0.13.dfsg-2_all.deb
 b3c58c5c8da505488f2b472270b40d18 7696 utils extra 
ovirt-guest-agent_1.0.13.dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlmziXsACgkQ3OMQ54ZM
yL/CnBAAsW0m/GdVdyz2D6EEGTxLFD+AFAI6qVTgtbVh3IQ1eqSZvctJeqmoydTB
/JSzIRxS6dwjab5aIGNRAw8EPilTh2L/rx/iq2HVsBEVJ3QDOegGYoicXP3MXfKl
V8XwcOkGczo0Zud8RRGsd/q7tUDqr40ReSeYBCO/N1F3nMGxlCxMTQGGnUXESJIo
4Xdg0ChJfuvwhH8HhjmeV8lMYbEB9ZH3us4O0fKbRDn5KpC8XY6HCApbVLMjSkQo
jfT6nybZjVRO1tDM3LLGByESdawjLJzYBUo5r+HvFw2zHNZnhpb/3rv16XtnCYZI
jvdF2gZMywoARM8GlkMexsHXA0G7oM9jFjUYfdkZ2G80xk8urK7eTMl0ZJWbbJfr
HIs12AXLfbPGKRyyWPxb2WSI17ZNBgO66ShvuMgvHkc+cDwnunTX8b2oDbZ9W3o/
T0JazQsYJ+YfJUXqYCQF28l++vmcfGrttcQ2H08r3FImcixPbUlDMayDBZkvtCDe
xpgy6V5JidKTv7rpaD2fWTkQmOUx/G86M4mgqKnNnkSWvVMWMbq0Zh3cjj6PKZgD

Processed: retitle 874429 to bzr: CVE-2017-14176: bzr+ssh URLs don't strip SSH options

[Debian Bug Tracking System]

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

> retitle 874429 bzr: CVE-2017-14176: bzr+ssh URLs don't strip SSH options
Bug #874429 [src:bzr] bzr: bzr+ssh URLs don't strip SSH options
Changed Bug title to 'bzr: CVE-2017-14176: bzr+ssh URLs don't strip SSH 
options' from 'bzr: bzr+ssh URLs don't strip SSH options'.
> thanks
Stopping processing here.

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

Bug#873362: marked as done (coinor-libcoinutils3v5: unannounced ABI change without SONAME change?)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 08:33:15 +0200
with message-id 

and subject line Re: Bug#873362: coinor-libcoinutils3v5: unannounced ABI change 
without SONAME change?
has caused the Debian Bug report #873362,
regarding coinor-libcoinutils3v5: unannounced ABI change without SONAME change?
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.)


-- 
873362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coinor-libcoinutils3v5
Version: 2.10.14+repack1-1
Severity: serious

Hi,

LOs unit tests fail (don't get confused by the name, also tests the CoinMP
based solver) since the last updates in sid:

build CUT] sccomp_lpsolver
S=/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2 && 
I=$S/instdir && W=$S/workdir &&mkdir -p $W/CppunitTest/ && rm -fr 
$W/CppunitTest/sccomp_lpsolver.test.user && mkdir 
$W/CppunitTest/sccomp_lpsolver.test.user &&rm -fr 
$W/CppunitTest/sccomp_lpsolver.test.core && mkdir 
$W/CppunitTest/sccomp_lpsolver.test.core && cd 
$W/CppunitTest/sccomp_lpsolver.test.core && (   
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program":$W/UnpackedTarball/cppunit/src/cppunit/.libs
   MALLOC_CHECK_=2 MALLOC_PERTURB_=153  
$W/LinkTarget/Executable/cppunittester 
$W/LinkTarget/CppunitTest/libtest_sccomp_lpsolver.so --headless 
"-env:BRAND_BASE_DIR=file://$S/instdir" "-env:BRAND_SHARE_SUBDIR=share" 
"-env:UserInstallation=file://$W/CppunitTest/sccomp_lpsolver.test.user"   
"-env:CONFIGURATION_LAYERS=xcsxcu:file://$I/share/registry 
xcsxcu:file://$W/unittest/registry"  
"-env:UNO_TYPES=file://$I/program/types.rdb file://$I/program/types/offapi.rdb" 
 "-env:UNO_SERVICES=file://$W/Rdb/ure/services.rdb file://$W/Rdb/services.rdb"  
-env:URE_INTERNAL_LIB_DIR=file://$I/program -env:LO_LIB_DIR=file://$I/program 
-env:LO_JAVA_DIR=file://$I/program/classes --protector 
$W/LinkTarget/Library/unoexceptionprotector.so unoexceptionprotector 
--protector $W/LinkTarget/Library/unobootstrapprotector.so 
unobootstrapprotector   --protector 
$W/LinkTarget/Library/libvclbootstrapprotector.so vclbootstrapprotector   
"-env:CPPUNITTESTTARGET=$W/CppunitTest/sccomp_lpsolver.test"   )  > 
$W/CppunitTest/sccomp_lpsolver.test.log 2>&1 || ( RET=$?; 
$S/solenv/bin/gdb-core-bt.sh $W/LinkTarget/Executable/cppunittester 
$W/CppunitTest/sccomp_lpsolver.test.core $RET >> 
$W/CppunitTest/sccomp_lpsolver.test.log 2>&1; cat 
$W/CppunitTest/sccomp_lpsolver.test.log; 
$S/solenv/gbuild/platform/unittest-failed-default.sh Cppunit sccomp_lpsolver)
Segmentation fault (core dumped)
(anonymous namespace)::LpSolverTest::testLpSolver finished in: 579ms

It looks like 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/LinkTarget/Executable/cppunittester
 generated a core file at 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/CppunitTest/sccomp_lpsolver.test.core/core
Backtraces:
[New LWP 11917]
[New LWP 11918]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by 
`/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/Li'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f6dca552b9e in CoinMessageHandler::internalPrint() () from 
/usr/lib/x86_64-linux-gnu/libCoinUtils.so.3
[Current thread is 1 (Thread 0x7f6de7e2e740 (LWP 11917))]
warning: File 
"/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_sal.so.3-gdb.py"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_sal.so.3-gdb.py
line to your configuration file "/tmp/tmp.Aw8SthVoRj/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/tmp/tmp.Aw8SthVoRj/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
warning: File 
"/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_cppu.so.3-gdb.py"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
warning: File 

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Anton Gladky]

Libreoffice migrated to testing. I am closing the bug.
Next time the symbols of the new version will be checked
precisely. Thanks all for discussion.

Regards

Anton


2017-09-08 23:17 GMT+02:00 Rene Engelhard :
> On Fri, Sep 08, 2017 at 07:37:03PM +0200, Francesco Poli wrote:
>> Will libreoffice/1:5.4.1-1 (currently in unstable and testing) break,
>> if I upgrade coinor-libcoinutils3v5 from version 2.9.15-4 to version
>> 2.10.14+repack1-1 ?
>
> The fix for LO is: rebuild coinmp. It works without rebuilding LO.
>
> That said, you probably didn't even check libreoffice/1:5.4.1-1s dependencies
> sincce to go very very sure for partial upgrades it depends on the new,
> rebuilt coinmp (and because coinutils didn't bump soname or so) on the 
> matching
> coinutils.
>
> So LO will work.
>
> Regards,
>
> Rene

Bug#853598: marked as done (opensaml2: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 09 Sep 2017 07:51:27 +0200
with message-id <87a824mnc0@lant.ki.iif.hu>
and subject line Re: Bug#853598: opensaml2: ftbfs with GCC-7
has caused the Debian Bug report #853598,
regarding opensaml2: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
 from /usr/include/xmltooling/XMLObjectBuilder.h:35,
 from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
 from ../saml/saml2/core/Assertions.h:33,
 from ../saml/saml2/metadata/Metadata.h:30,
 from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
samlsign.cpp:316:21: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
 auto_ptr metadata(buildPlugin(m_param, 
conf.MetadataProviderManager));
 ^~~~
In file included from /usr/include/c++/7/memory:80:0,
 from /usr/include/xmltooling/XMLObjectBuilder.h:35,
 from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
 from ../saml/saml2/core/Assertions.h:33,
 from ../saml/saml2/metadata/Metadata.h:30,
 from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
samlsign.cpp:354:13: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
 auto_ptr cr(
 ^~~~
In file included from /usr/include/c++/7/memory:80:0,
 from /usr/include/xmltooling/XMLObjectBuilder.h:35,
 from /usr/include/xmltooling/ConcreteXMLObjectBuilder.h:30,
 from ../saml/saml2/core/Assertions.h:33,
 from ../saml/saml2/metadata/Metadata.h:30,
 from samlsign.cpp:39:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -O2 -DNDEBUG  -Wl,-z,relro -Wl,-z,now -o samlsign 
samlsign-samlsign.o ../saml/libsaml.la -lxerces-c -lxmltooling -llog4shib  
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -O2 -DNDEBUG 
-Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/samlsign samlsign-samlsign.o  
../saml/.libs/libsaml.so -lxerces-c -lxmltooling -llog4shib
../saml/.libs/libsaml.so: undefined reference to `virtual thunk to 
xmltooling::AbstractComplexElement::getOrderedChildren[abi:cxx11]() const'
../saml/.libs/libsaml.so: undefined reference to `virtual thunk to 
xmltooling::AbstractSimpleElement::getOrderedChildren[abi:cxx11]() const'
collect2: error: ld returned 1 exit status
Makefile:453: recipe for target 'samlsign' failed
make[3]: *** [samlsign] Error 1
make[3]: Leaving directory '/<>/samlsign'
Makefile:586: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: 

Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Dominik Kupschke]

Source: mesa
Version: 17.0.2-2
Severity: grave
Justification: renders package unusable

Hi,

after upgrading mesa from 17.1.5 to 17.2.0-2 none of my games are able
to start.
At least Counter-Strike Global Offensive reports this failure back to
me:
Failed to create GL context: Could not make GL context current:
GLXBadContextTag

Regards
Dominik

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

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