date:20191031

On Sat, Sep 09, 2017 at 11:06:18PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: qjoypad
> Version: 4.1.0-2.1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

qjoypad seems dead upstream, but there's a fork at 
https://github.com/panzi/qjoypad
which supports Qt5. Does anyone plan to switch the package to the port? 
Otherwise
let's remove it as we're moving forward with the Qt4 removal.

Cheers,
Moritz

Bug#874853: [cmtk] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 09:03:16PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: cmtk
> Version: 3.3.1-1.2
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

There hasn't been any followup on this bug since two years and we're now moving
forward with the Qt4 removal, are the immediate plans to port cmtk to Qt5 or
should we remove it from the archive?

Cheers,
Moritz

Bug#874878: [freemat] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 09:04:55PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: freemat
> Version: 4.2+dfsg1-1
> 4.2+dfsg1-5
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

There hasn't been any followup on this bug since two years and we're now moving
forward with the Qt4 removal, are the immediate plans to port freemat to Qt5 or
should we remove it from the archive?

Cheers,
Moritz

Bug#943920: llvm-toolchain-8: FTBFS since migration of gcc-defaults to gcc-9

2019-10-31 Thread Sylvestre Ledru




Le 31/10/2019 à 22:51, Samuel Thibault a écrit :

Source: llvm-toolchain-8
Version: 1:8.0.1-3
Severity: serious
Justification: FTBFS

Hello,

Since the migration of gcc-defaults to gcc-9, llvm-toolchain-8 FTBFS,
with



CMake Error at tools/polly/lib/External/CMakeLists.txt:91 (message):
   No ffs implementation found


looking at CMakeError.log, one actually see:


Source file was:

   int main() { (void)__builtin_ffs(0); return 0; }
   
Performing C SOURCE FILE Test HAVE_DECL__BITSCANFORWARD failed with the following output:

Change Dir: /build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_11f2c/fast"
make[2]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_11f2c.dir/build.make 
CMakeFiles/cmTC_11f2c.dir/build
make[3]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_11f2c.dir/src.c.o
/usr/bin/gcc-9 -D_GNU_SOURCE  -g -O2 
-fdebug-prefix-map=/build/llvm-toolchain-8-8.0.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -Werror=date-time -Wall -Wextra 
-Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers -pedantic 
-Wno-long-long -Wimplicit-fallthrough -Wno-comment -ffunction-sections 
-fdata-sections -flto=thin -DHAVE_DECL__BITSCANFORWARD   -o 
CMakeFiles/cmTC_11f2c.dir/src.c.o   -c 
/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp/src.c
cc1: error: unrecognized argument to '-flto=' option: 'thin'


i.e. llvm passed -flto=thin to gcc-9, which does not understand it.
gcc-8 used to understand it, but not gcc-9 any more. I had to comment in
debian/rules CMAKE_EXTRA += -DLLVM_ENABLE_LTO="Thin" to get it built.

Samuel


Indeed, this is why I am forcing the build of -9 with gcc-8 for now :)

See https://bugs.llvm.org/show_bug.cgi?id=43193 for more info!

S

Bug#943920: llvm-toolchain-8: FTBFS since migration of gcc-defaults to gcc-9

2019-10-31 Thread Samuel Thibault

Source: llvm-toolchain-8
Version: 1:8.0.1-3
Severity: serious
Justification: FTBFS

Hello,

Since the migration of gcc-defaults to gcc-9, llvm-toolchain-8 FTBFS,
with 



CMake Error at tools/polly/lib/External/CMakeLists.txt:91 (message):
  No ffs implementation found


looking at CMakeError.log, one actually see:


Source file was:

  int main() { (void)__builtin_ffs(0); return 0; }
  
Performing C SOURCE FILE Test HAVE_DECL__BITSCANFORWARD failed with the 
following output:
Change Dir: /build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_11f2c/fast"
make[2]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_11f2c.dir/build.make 
CMakeFiles/cmTC_11f2c.dir/build
make[3]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_11f2c.dir/src.c.o
/usr/bin/gcc-9 -D_GNU_SOURCE  -g -O2 
-fdebug-prefix-map=/build/llvm-toolchain-8-8.0.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -Werror=date-time -Wall -Wextra 
-Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers -pedantic 
-Wno-long-long -Wimplicit-fallthrough -Wno-comment -ffunction-sections 
-fdata-sections -flto=thin -DHAVE_DECL__BITSCANFORWARD   -o 
CMakeFiles/cmTC_11f2c.dir/src.c.o   -c 
/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp/src.c
cc1: error: unrecognized argument to '-flto=' option: 'thin'


i.e. llvm passed -flto=thin to gcc-9, which does not understand it.
gcc-8 used to understand it, but not gcc-9 any more. I had to comment in
debian/rules CMAKE_EXTRA += -DLLVM_ENABLE_LTO="Thin" to get it built.

Samuel

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

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

-- 
Samuel
 t1 faich
 les programmes ils segfaultent jamais quand on veut
 -+- #ens-mim en plein débogage -+-

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-31 Thread Rene Engelhard

reassign 935902 g++-9
affects 935902 libcppunit-dev
found 935902 9.2.1-12
close 935902 9.2.1-16
thanks

Hi,

On Thu, Oct 31, 2019 at 03:15:10PM +0100, Matthias Klose wrote:
> The comment about cppunit made me look at the cppunit package to find
> #935902, and yes, the test case is reproducible. So looking at the test

Ah, that one...

Reassigning to gcc (and marking as fixed)

> failure would have been revealed that the test frame work is broken, not a
> single test. This turned out to be https://gcc.gnu.org/PR92267, causing an
> ABI breakage in cppunit.

OK.

> The fix is now in -16.

Good. Can confirm. You can close the bug.

Regards,

Rene

Bug#943447: the autopkg test calls python instead of python2

2019-10-31 Thread Jason Crain

On Thu, Oct 24, 2019 at 10:39:33PM +0200, Matthias Klose wrote:
> the autopkg test calls python instead of python2. This will make the package
> fail the next binNMU when adding python3.8 support.

I think I will instead have the test run python3, since python2 is
possibly being removed soon.

Processed: Re: Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.

Processing control commands:

> notfound -1 twolame/0.4.0-2
Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest: 
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
No longer marked as found in versions twolame/0.4.0-2.

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

Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.

2019-10-31 Thread Sebastian Ramacher

Control: notfound -1 twolame/0.4.0-2

Hi

On 2019-10-31 16:37:11, Paul Gevers wrote:
> Source: twolame, ffmpeg
> Control: found -1 twolame/0.4.0-2
> Control: found -1 ffmpeg/7:4.2.1-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
> 
> Dear maintainers,
> 
> With a recent upload of twolame the autopkgtest of ffmpeg fails in
> testing when that autopkgtest is run with the binary packages of twolame
> from unstable. It passes when run with only packages from testing. In
> tabular form:
>passfail
> twolamefrom testing0.4.0-2
> ffmpeg from testing7:4.2.1-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of twolame to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the right package?

This is an issue in ffmpeg. The change in twolame is deliberate:
https://github.com/njh/twolame/pull/32. The defaults in ffmpeg produce
invalid files.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#941376: Should monotone be removed?

On Sun, Sep 29, 2019 at 10:23:44PM +0200, Moritz Muehlenhoff wrote:
> Source: monotone
> Severity: serious
> 
> Should monotone be removed? Dead upstream, last upload three years ago
> and removed from testing since 1.5 years.

I've now filed a removal bug.

Cheers,
Moritz

Bug#943868: [Pkg-rust-maintainers] Bug#943868: rust-chrono: issues in d/copyright

2019-10-31 Thread Sean Whitton

Hello,

On Thu 31 Oct 2019 at 04:30PM +00, kpcyrd wrote:

> This has been fixed in our git repo, but we're still waiting for the
> previous upload to go through the NEW queue before we can upload the fix
> for this.

Thanks for the fix!  You can make another upload to NEW and it will
(effectively) replace the old one.  Indeed, that would be recommended.

-- 
Sean Whitton

signature.asc
Description: PGP signature

Bug#943623: marked as done (objects in libclangIndex.a are llvm ir bitcode)

Your message dated Thu, 31 Oct 2019 20:53:52 +
with message-id 
and subject line Bug#943623: fixed in llvm-toolchain-9 1:9.0.0-3
has caused the Debian Bug report #943623,
regarding objects in libclangIndex.a are llvm ir bitcode
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.)


-- 
943623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-9-dev
Version: 1:9.0.0-1
Severity: serious
Control: affects -1 ccls

As for 1:9.0.0-1

ar x /usr/lib/llvm-9/lib/libclangIndex.a
file *.o

CodegenNameGenerator.cpp.o: LLVM IR bitcode
CommentToXML.cpp.o: LLVM IR bitcode
FileIndexRecord.cpp.o:  LLVM IR bitcode
IndexBody.cpp.o:LLVM IR bitcode
IndexDecl.cpp.o:LLVM IR bitcode
IndexingAction.cpp.o:   LLVM IR bitcode
IndexingContext.cpp.o:  LLVM IR bitcode
IndexSymbol.cpp.o:  LLVM IR bitcode
IndexTypeSourceInfo.cpp.o:  LLVM IR bitcode
USRGeneration.cpp.o:LLVM IR bitcode

While version 1:9-1 shows

CodegenNameGenerator.cpp.o: ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
CommentToXML.cpp.o: ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
FileIndexRecord.cpp.o:  ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexBody.cpp.o:ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexDecl.cpp.o:ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexingAction.cpp.o:   ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexingContext.cpp.o:  ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexSymbol.cpp.o:  ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
IndexTypeSourceInfo.cpp.o:  ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped
USRGeneration.cpp.o:ELF 64-bit LSB relocatable, x86-64, version 1 
(SYSV), not stripped

This causes GNU ld fails to link, errors are:

  /usr/lib/llvm-9/lib/libclangIndex.a error adding symbols: archive has no 
index; run ranlib to add one

I checked the upstream prebuild tarball, the objects in libclangIndex.a are ELF.

So I think this is bug in the Debian package, and is a regression from the 
version in testing.

Thanks
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-9
Source-Version: 1:9.0.0-3

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-9 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Oct 2019 20:36:09 +0100
Source: llvm-toolchain-9
Architecture: source
Version: 1:9.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 942864 943623
Changes:
 llvm-toolchain-9 (1:9.0.0-3) unstable; urgency=medium
 .
   * Seems to be ok, uploading to unstable
 (Closes: #942864) fuzzer issues
 (Closes: #943623) libclangIndex.a are llvm ir bitcode
Checksums-Sha1:
 86c6f5907d2e30b9787ddbeb03bfe68c378dc856 6032 llvm-toolchain-9_9.0.0-3.dsc
 0678f492595bb6d805493ab8852e8a11be7400f4 40 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 bcef045f0fd471387542b5e390b0f4fbe8b7ef22 11993 
llvm-toolchain-9_9.0.0-3_source.buildinfo
Checksums-Sha256:
 8d5c7d5d97c2cc413360d3febd681d33c8b13973520a1c7889e279c6079f6928 6032 
llvm-toolchain-9_9.0.0-3.dsc
 771096e3960efacfcbb2abe1b7ef273957444f6ced5745c4dc614acedd22c859 40 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 5a7f36ac1faa9c67855cff3ed8b669898b34bbaab56408ce2866ba29451b5c6e 11993 
llvm-toolchain-9_9.0.0-3_source.buildinfo
Files:
 f3f609165224d41c254ccbac8f87f764 6032 devel optional 
llvm-toolchain-9_9.0.0-3.dsc
 4e064d4debacde08a089b4a8f877f47b 40 devel optional 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 003713efd17652108578798045909dd0 11993 devel optional 
llvm-toolchain-9_9.0.0-3_source.buildinfo

-BEGIN PGP

Bug#942864: marked as done (llvm-toolchain-9: FTBFS on i386: tries to ld -r amd64 code)

Your message dated Thu, 31 Oct 2019 20:53:52 +
with message-id 
and subject line Bug#942864: fixed in llvm-toolchain-9 1:9.0.0-3
has caused the Debian Bug report #942864,
regarding llvm-toolchain-9: FTBFS on i386: tries to ld -r amd64 code
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.)


-- 
942864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-9
Version: 1:9.0.0-1
Severity: serious
Justification: FTBFS on release arch, built before
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-9=i386=1%3A9.0.0-1=1571581925=0

Disentangling the parallel build, we get:

[…]
cd 
/<>/build-llvm/tools/clang/stage2-bins/projects/compiler-rt/lib/fuzzer/cxx_x86_64_merge.dir
 && /usr/bin/ld --whole-archive 
/<>/build-llvm/tools/clang/stage2-bins/lib/clang/9.0.0/lib/linux/libclang_rt.fuzzer-x86_64.a
 --no-whole-archive 
/<>/build-llvm/tools/clang/stage2-bins/projects/compiler-rt/lib/fuzzer/libcxx_fuzzer_x86_64/lib/libc++.a
 -r -o fuzzer.o
/usr/bin/ld: relocatable linking with relocations from format elf64-x86-64 
(/<>/build-llvm/tools/clang/stage2-bins/lib/clang/9.0.0/lib/linux/libclang_rt.fuzzer-x86_64.a(FuzzerCrossOver.cpp.o))
 to format elf32-i386 (fuzzer.o) is not supported
make[8]: *** 
[projects/compiler-rt/lib/fuzzer/CMakeFiles/clang_rt.fuzzer-x86_64.dir/build.make:120:
 lib/clang/9.0.0/lib/linux/libclang_rt.fuzzer-x86_64.a] Error 1

Basically, it’s trying to create one single fuzzer.o relocatable object file
from the contents of the amd64 library but uses ld -r without -m64.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-9
Source-Version: 1:9.0.0-3

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-9 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Oct 2019 20:36:09 +0100
Source: llvm-toolchain-9
Architecture: source
Version: 1:9.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 942864 943623
Changes:
 llvm-toolchain-9 (1:9.0.0-3) unstable; urgency=medium
 .
   * Seems to be ok, uploading to unstable
 (Closes: #942864) fuzzer issues
 (Closes: #943623) libclangIndex.a are llvm ir bitcode
Checksums-Sha1:
 86c6f5907d2e30b9787ddbeb03bfe68c378dc856 6032 llvm-toolchain-9_9.0.0-3.dsc
 0678f492595bb6d805493ab8852e8a11be7400f4 40 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 bcef045f0fd471387542b5e390b0f4fbe8b7ef22 11993 
llvm-toolchain-9_9.0.0-3_source.buildinfo
Checksums-Sha256:
 8d5c7d5d97c2cc413360d3febd681d33c8b13973520a1c7889e279c6079f6928 6032 
llvm-toolchain-9_9.0.0-3.dsc
 771096e3960efacfcbb2abe1b7ef273957444f6ced5745c4dc614acedd22c859 40 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 5a7f36ac1faa9c67855cff3ed8b669898b34bbaab56408ce2866ba29451b5c6e 11993 
llvm-toolchain-9_9.0.0-3_source.buildinfo
Files:
 f3f609165224d41c254ccbac8f87f764 6032 devel optional 
llvm-toolchain-9_9.0.0-3.dsc
 4e064d4debacde08a089b4a8f877f47b 40 devel optional 
llvm-toolchain-9_9.0.0-3.debian.tar.xz
 003713efd17652108578798045909dd0 11993 devel optional 
llvm-toolchain-9_9.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl27ONsACgkQfmUo2nUv
G+FRWRAAkmEWoQ1Sd/KLGrL88ckiL4vzDsR+PiCkpxzBp1w7wyeewtsuAbxxOcCB
q5czA9Wk5A08rBLmp/1rFjiRkhBcpWuVQgOg6/4xcqxWteeDaa3QOlmcaeCyugV8
Gs32TnE4PHw6HbgGRVk2GZuJX0rReT3APpT7oId15RWKkC2luHk96NAfncjNagYa
NNMSFZ2vU/xqdP11U0ABJhUP3UKPe/QA31AGPp+VrDSsCIWOF8s3tYXSGnHTrxa2
nMM1hN1c76kASFpR13mGVK9QwJ3eJDs6fpm8xc8u79Y1/MxUWkUe8m4NcprXeusA

Processed: py2removal blocks updates - 2019-10-31 20:35:37.097140+00:00

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 942966 936214
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 938604 936789 938799 937339 943123 939114 943146 936221 
936981 943117 943291 943178 936758 943300 936632 942916 938593 938583 937628 
938584 938803 938789 943129 943076 936813 938464 938293 943108 938329 936833 
936841 938837 938511 936265 938327 939104 938361 943151 938614 937803 936624 
938582 943093 937454 936619 939115 939109 939112 943186 943103 938637 936531 
936721 937956 936748 938623 942988 937457 936266 937405 936398 938591 937419 
943230 935358 883161 942966 943270 942919 938586 937114 938884 943294 938596 
936214 943245 938665 942941 938160 936670 938084 936601 93 943023 943131 
937099 943252 936173 938780 936539 938590 936995 937703 937688 936900 937181 
936371 936718 939106 937388 936225 936166 937422 943110 942956 926244 937115 
943216 936717 942904 938885
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-distutils-extra
> block 937703 by 936641 937114 943270
Bug #937703 [src:python-distutils-extra] python-distutils-extra: Python2 
removal in sid/bullseye
937703 was blocked by: 939107 937114 943270 937457 939111 939109 939106 939104 
939115 936641 936107 939105 936813 939114 939112 939113 936225 938885 849087 
936119 939103 939110 926244 938623 939108 938450
937703 was blocking: 937448 937695 937817 938168 943104
Ignoring request to alter blocking bugs of bug #937703 to the same blocks 
previously set
>
End of message, stopping processing here.

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

Bug#936207: biosig4c++: Python2 removal in sid/bullseye


Severity 936207 serious
thanks

biosig4c++ build-depends on the python-pkgconfig binary package which is no 
longer built by the python-pkgconfig source package.

Processed: re: biosig4c++: Python2 removal in sid/bullseye

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

> Severity 936207 serious
Bug #936207 [src:biosig4c++] biosig4c++: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#943765: marked as done (libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev)

Your message dated Thu, 31 Oct 2019 20:10:58 +
with message-id 
and subject line Bug#943765: fixed in gdcm 3.0.3-1~exp2
has caused the Debian Bug report #943765,
regarding libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev
to be marked as done.

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

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


-- 
943765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtkgdcm3-dev
Version: 3.0.3-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb ...
  Unpacking libvtkgdcm3-dev (3.0.3-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libvtkgdcm.so', which is also 
in package libvtkgdcm2-dev 2.8.8-9+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libvtkgdcm3-dev_3.0.3-1~exp1_amd64.deb


cheers,

Andreas


libvtkgdcm2-dev=2.8.8-9+b1_libvtkgdcm3-dev=3.0.3-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 3.0.3-1~exp2

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated gdcm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Oct 2019 12:35:25 +0100
Source: gdcm
Binary: gdcm-doc libgdcm-cil libgdcm-cil-dbgsym libgdcm-dev libgdcm-java 
libgdcm-java-dbgsym libgdcm-tools libgdcm-tools-dbgsym libgdcm3.0 
libgdcm3.0-dbgsym libvtkgdcm-cil libvtkgdcm-cil-dbgsym libvtkgdcm-dev 
libvtkgdcm-java libvtkgdcm-java-dbgsym libvtkgdcm-tools libvtkgdcm-tools-dbgsym 
libvtkgdcm3.0 libvtkgdcm3.0-dbgsym python3-gdcm python3-gdcm-dbgsym 
python3-vtkgdcm python3-vtkgdcm-dbgsym
Architecture: source all amd64
Version: 3.0.3-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 gdcm-doc   - Grassroots DICOM documentation
 libgdcm-cil - Grassroots DICOM CLI bindings
 libgdcm-dev - Grassroots DICOM development libraries and headers
 libgdcm-java - Grassroots DICOM Java bindings
 libgdcm-tools - Grassroots DICOM tools and utilities
 libgdcm3.0 - Grassroots DICOM runtime libraries
 libvtkgdcm-cil - Grassroots DICOM VTK CLI bindings
 libvtkgdcm-dev - Grassroots DICOM VTK development libraries and headers
 libvtkgdcm-java - Grassroots DICOM VTK Java bindings
 libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities
 libvtkgdcm3.0 - Grassroots DICOM VTK runtime libraries
 python3-gdcm - Grassroots DICOM Python bindings
 python3-vtkgdcm - Grassroots DICOM VTK/Python bindings
Closes: 943765
Changes:
 gdcm (3.0.3-1~exp2) experimental; urgency=medium
 .
   * d/control: Add Breaks/Replaces for *gdcm2-dev Closes: #943765
   * d/* rename lib*gdcm3-dev to lib*gdcm-dev
Checksums-Sha1:
 bf6570484d39397e2bb8f89dcd1be495cb63edb4 3594 gdcm_3.0.3-1~exp2.dsc
 933e10a6411edbef6b15c220563001bf5f00c695 21912 gdcm_3.0.3-1~exp2.debian.tar.xz
 a19ec256e2041806625189a679303872a34cce99 13821068 gdcm-doc_3.0.3-1~exp2_all.deb
 ea185f06e06f5608e83b97c440aa2447e7c7e668 42915 
gdcm_3.0.3-1~exp2_amd64.buildinfo
 0a7794cae83f46c7748a775ea71869810c700c5d 2550472 
libgdcm-cil-dbgsym_3.0.3-1~exp2_amd64.deb
 8dd1f3b2ede267cb51364328c6d81b8ec4d74d29 340884 
libgdcm-cil_3.0.3-1~exp2_amd64.deb
 36682d1b4910fa59bd82363083c674a581bbea3d 267136 
libgdcm-dev_3.0.3-1~exp2_amd64.deb
 69288d384b40d81559e7d898ecc51b69c1c97eea 2453980

Bug#943509: libsqlite3 (Re: Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4)

2019-10-31 Thread ISHIKAWA,chiaki




Hi,

I vouch that there seems to be a serious issue in libsqlite3 3.30.1-1.

I came here because it seems that I have an issue with sqlite3 on my 
linux installation.
The problem manifested as database operation failures during thunderbird 
mail client regression testing (called mach xcpshell-tests|)


I looks someone on Ubuntu did not see it this month and mozilla's 
compilation and testing farm machines do not seem to see it. They run 
CentOs if I am not mistaken.


https://bugzilla.mozilla.org/show_bug.cgi?id=1589779

So I thought maybe the current installation of libsqlite3 on my linux PC 
was to blame.


Well, it looks that is the case if I read the exchanges here correctly.
My libsqlite3 seems to be affected: the version is 3.30.1-1
(The problem was not observed in August. I am not sure if the upgrade of 
libsqlite3 happened during then and now.)


What do people suggest that best course of action under the circumstances?

Downgrade (to which version and how) or install newer libsqlite3 (where)?

Your guidance is appreciated.

TIA

Chiaki

PS: if necessary, I can file a separate bug report to escalate this 
issue, but it would be weeks until I can come up with a very simplified 
test case since the problems occur inside the complex test harness: I 
don't understand the innards very well.


All I can say is that the same tests that deal with database that worked 
for years suddenly broke in the last several weeks. So my bug report 
would not be that useful :-(

Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41

2019-10-31 Thread Michel Dänzer

On 2019-10-31 8:36 p.m., Petra R.-P. wrote:
> Am Do., 31. Okt. 2019, um 18:01 +0100 schrieb Michel Dänzer 
> :
>> On 2019-10-30 2:15 p.m., Petra R.-P. wrote:
> 
>> This happens when HW acceleration is disabled. If you can't or don't
>> want to enable HW acceleration,
>  I can't because I don't know how to do this.
>> I recommend using the Xorg modesetting
>> driver for the time being, by either uninstalling
>> xserver-xorg-video-radeon or explicitly setting the driver in
>> /etc/X11/xorg.conf, see below. Without HW acceleration, the radeon
>> driver doesn't really provide much if any benefit over modesetting.
>>
>>
>> Section "Device"
>>
>> Identifier "whateveryoulike"
>>
>> Driver  "modesetting"
>>
>> EndSection
> 
>  I tried both variants without success.
> 
>  Both resulted in something like
> 
>  Server terminated with error (1).
>  xinit: giving up
>  xinit: unable to connect to X server: Conncection refused
>  xinit: server error

We'd again need to see the corresponding Xorg log file.


-- 
Earthling Michel Dänzer   |   https://redhat.com
Libre software enthusiast | Mesa and X developer

Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41

2019-10-31 Thread Petra R.-P.

Am Do., 31. Okt. 2019, um 18:01 +0100 schrieb Michel Dänzer 
:
> On 2019-10-30 2:15 p.m., Petra R.-P. wrote:

> This happens when HW acceleration is disabled. If you can't or don't
> want to enable HW acceleration,
 I can't because I don't know how to do this.
> I recommend using the Xorg modesetting
> driver for the time being, by either uninstalling
> xserver-xorg-video-radeon or explicitly setting the driver in
> /etc/X11/xorg.conf, see below. Without HW acceleration, the radeon
> driver doesn't really provide much if any benefit over modesetting.
> 
> 
> Section "Device"
> 
> Identifier "whateveryoulike"
> 
> Driver  "modesetting"
> 
> EndSection

 I tried both variants without success.

 Both resulted in something like

 Server terminated with error (1).
 xinit: giving up
 xinit: unable to connect to X server: Conncection refused
 xinit: server error


 Old xserver-xorg-video-radeon 19.0.1-1 still works fine  :-)


 Petra

Processed: py2removal blocks updates - 2019-10-31 18:35:33.414531+00:00

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 942966 936214
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 938604 936789 938799 937339 943123 939114 943146 936221 
936981 943117 943291 943178 936758 943300 936632 942916 938593 938583 937628 
938584 938803 938789 943129 943076 936813 938464 938293 943108 938329 936833 
936841 938837 938511 936265 938327 939104 938361 943151 938614 937803 936624 
938582 943093 937454 936619 939115 939109 939112 943186 943103 938637 936531 
936721 937956 936748 938623 942988 937457 936266 937405 936398 938591 937419 
943230 935358 883161 942966 943270 942919 938586 937114 938884 943294 938596 
936214 943245 938665 942941 938160 936670 938084 936601 93 943023 943131 
937099 943252 936173 938780 936539 938590 936995 937703 937688 936900 937181 
936371 936718 939106 937388 936225 936166 937422 943110 942956 926244 937115 
943216 936717 942904 938885
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-distutils-extra
> block 937703 by 936641 937114 943270
Bug #937703 [src:python-distutils-extra] python-distutils-extra: Python2 
removal in sid/bullseye
937703 was blocked by: 939107 937114 943270 937457 939111 939109 939106 939104 
939115 936641 936107 939105 936813 939114 939112 939113 936225 938885 849087 
936119 939103 939110 926244 938623 939108 938450
937703 was blocking: 937448 937695 937817 938168 943104
Ignoring request to alter blocking bugs of bug #937703 to the same blocks 
previously set
>
End of message, stopping processing here.

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

Processed: re: python-colormap: Python2 removal in sid/bullseye

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

> Severity 937657 serious
Bug #937657 [src:python-colormap] python-colormap: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#941641: marked as done (acl2: Build-Depends on emacs25 which has been removed from unstable/bullseye)

Your message dated Thu, 31 Oct 2019 18:04:58 +
with message-id 
and subject line Bug#941641: fixed in acl2 8.1dfsg-4
has caused the Debian Bug report #941641,
regarding acl2: Build-Depends on emacs25 which has been removed from 
unstable/bullseye
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.)


-- 
941641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acl2
Version: 8.0dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

You package Build-Depends on "emacs25 | emacsen". For reproducibility reasons,
the Debian buildds only consider the first alternative. The emacs25 has been a
transitional package in buster, and src:emacs has recently stopped building
that package. Please update your Build-Depends.

This all came about because your package is part of the readline transition,
but it FTBFS on mipsel now.

Paul

PS: your package isn't migrating because you uploaded an arch:all
binary. Please do a source-only upload when you fix this issue.

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2VuEkACgkQnFyZ6wW9
dQoXcwf/RrWQfP6v0BeScTnd3LU6dznMK1p0ldlHrnRrOgLg8SjKrDVe9SaQm6JX
vvZXzUnhW/Vjdvk2BKqSlbUBCMo75ZY93cTNQDK9y6ht41dAfn3er/QDc5V44yA0
exW3rHJWUo4guTUeufvvWg3SZf4ooGkemjyHbppedPioNc9N7T7NyL8Qwt29L2l3
lHLVHrIK4dRuw3EMYaVI8fyrGkBHHU4oCi3Ljhck6hhjtt3ibITMkDt6yBFCmaih
Wg0qTCu1M5qmRlLTxE+IPkb3bOw8Kv3rc58tPbR6ktcl5KYJvvlZdg3uzA58isuZ
OPGqctPFxOElSxJcie43cSN3Dwafxg==
=3F00
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: acl2
Source-Version: 8.1dfsg-4

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated acl2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Oct 2019 17:17:49 +
Source: acl2
Architecture: source
Version: 8.1dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 941641
Changes:
 acl2 (8.1dfsg-4) unstable; urgency=medium
 .
   * source-only upload
   * Bug fix: "Build-Depends on emacs25 which has been removed from
 unstable/bullseye", thanks to Paul Gevers (Closes: #941641).
Checksums-Sha1:
 4f38bae51376a9d2c9a74050725545944940b855 2247 acl2_8.1dfsg-4.dsc
 689c6feba87b806832168665e120de26a82789f9 205348 acl2_8.1dfsg-4.debian.tar.xz
 0889f90ba27f3e4ef241f80807a48d37f77d0be7 8337 acl2_8.1dfsg-4_source.buildinfo
Checksums-Sha256:
 b189350548fab88aa8a2cf0318b76d60d626a1fbc65e38e0613b2202fc55332f 2247 
acl2_8.1dfsg-4.dsc
 63d8c700489c76347aa855f07d0f59db209dfb7d1604c4f95c3222e063793adf 205348 
acl2_8.1dfsg-4.debian.tar.xz
 29fb2ab4712c5c6ecbd29dd57eee718b369622db774c9a6bae2dfd87d1d60b27 8337 
acl2_8.1dfsg-4_source.buildinfo
Files:
 29f4bfe94194d75d152d700a350523f6 2247 math optional acl2_8.1dfsg-4.dsc
 18d9e864658af90a3ab3c10245d76541 205348 math optional 
acl2_8.1dfsg-4.debian.tar.xz
 b73ea2d7391e3938192e82b8cbd6b63c 8337 math optional 
acl2_8.1dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAl27G3YACgkQuEXOUQ+b
cU1Uaw//Yt5CQ9TUPZKTOdr+xfBwRswUOZd6VgpCZ1gxBkgVzZLr2Bbsg9gZge36
jbnjadDgJ+O1U7d/RVBbArDigipl4sIrffKdCgJzHpiKOzyBY2J3pgUSl6nCsORi
hxtoYKSwn1zSAglkBNA27p1QlhqxZnftrMR1piy5vo62StvEVdqBnCLJpKa+BJyk
j2LBsvWZLE4+Wn8h7D7x6QgxEKIvBnAu4WyMCZj952Db/F3FS9Lu0bOXOEi1oj4X

Bug#943912: python-easydev: needs a source-only upload


Package: python-easydev
Version: 0.9.38-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing. Please Make a source-only upload so your package can migrate.

Bug#943761: python3-nototools: fails to install: Sorry: IndentationError: unexpected indent (lint_cmap_reqs.py, line 56)

2019-10-31 Thread Andreas Beckmann

Followup-For: Bug #943761

Furthermore, python3-nototools is missing Breaks+Replaces: python-nototools

  Preparing to unpack .../python3-nototools_0.2.0-1_all.deb ...
  Unpacking python3-nototools (0.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-nototools_0.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/add_vs_cmap', which is also in package 
python-nototools 0~20170925-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-nototools_0.2.0-1_all.deb


Andreas

Bug#943911: squid: needs a source-only upload.


Package: squid
Version: 4.8-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing. Please make a source-only upload so your package can migrate.

Bug#941101: rdup: Uses functions deprecated in Nettle 3.5


I notice that in addition to the complaints about nettle deprecation there is 
also a complaint about the use of memmove, unfortunately the compiler doesn't 
say what exactly it doesn't like about the use of memmove.

In raspbian I decided to go ahead and remove -Werror, a debdiff doing that 
should appear soon at https://debdiffs.raspbian.org/main/r/rdup . No intent to 
NMU in Debian.

Bug#943566: FTBFS with nettle 3.5.1


tags 943566 +patch
thanks


Currently the nettle 3.5.1 transition is going on. I tried to binNMU
your package but it fails to build from source on all architectures.


I had a fiddle around with the order of includes and this led me to some 
different error messages which led me to the real problem.

Utils.h includes  inside the pktannon namespace. This causes the 
sockaddr definition to be incorrectly placed in the pktannon namespace which causes 
problems later.

The fix is to move the include of  outside the namespace.

I then ran into a testsuite failure, it seems the testsuite needs ncat and 
tshark, initially I thought this may be extra tests activated by building as 
root, but it also seemed to happen when building as nobody. So I went ahead and 
added the build-dependencies, but I still had a bunch of test failures.

Looking back at the last succesful Debian build I noticed the testsuite was not 
being run on the autobuilders because runtest was not installed. However the 
chroot I was testing in did have runtest installed. I decided to go ahead and 
disable the testsuite and remove the extra build-depends I added.

I also extended the clean target to clean up some files that were left behind 
after said failed testsuite run. I have not checked if the same files are left 
behind by a successful testsuite run.

I have uploaded my fix to Raspbian, A debdiff should appear soon at 
https://debdiffs.raspbian.org/main/p/pktanon , no intent to NMU in Debian.

Processed: Re: FTBFS with nettle 3.5.1

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

> tags 943566 +patch
Bug #943566 [src:pktanon] FTBFS with nettle 3.5.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41

2019-10-31 Thread Michel Dänzer

On 2019-10-30 2:15 p.m., Petra R.-P. wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:19.1.0-1
> Followup-For: Bug #943664
> 
> Dear Maintainer,
> 
> I can confirm every detail of the original report,
> except that this happens here on an old IBM Thinkpad T 41.

This happens when HW acceleration is disabled. If you can't or don't
want to enable HW acceleration, I recommend using the Xorg modesetting
driver for the time being, by either uninstalling
xserver-xorg-video-radeon or explicitly setting the driver in
/etc/X11/xorg.conf, see below. Without HW acceleration, the radeon
driver doesn't really provide much if any benefit over modesetting.

Section "Device"

Identifier "whateveryoulike"

Driver  "modesetting"

EndSection

-- 
Earthling Michel Dänzer   |   https://redhat.com
Libre software enthusiast | Mesa and X developer

Processed: severity 935156 important

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

> severity 935156 important
Bug #935156 [ceph] ceph: Multiple mon deployment failure on arm64: 
ms_verfity_authorizer bad authorizer and crc check failure
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

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

Processed: py2removal blocks updates - 2019-10-31 16:35:41.051588+00:00

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 942966 936214
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 938604 936789 938799 937339 943123 939114 943146 936221 
936981 943117 943291 943178 936758 943300 936632 942916 938593 938583 937628 
938584 938803 938789 943129 943076 936813 938464 938293 943108 938329 936833 
936841 938837 938511 936265 938327 939104 938361 943151 938614 937803 936624 
938582 943093 937454 936619 939115 939109 939112 943186 943103 938637 936531 
936721 937956 936748 938623 942988 937457 936266 937405 936398 938591 937419 
943230 935358 883161 942966 943270 942919 938586 937114 938884 943294 938596 
936214 943245 938665 942941 938160 936670 938084 936601 93 943023 943131 
937099 943252 936173 938780 936539 938590 936995 937703 937688 936900 937181 
936371 936718 939106 937388 936225 936166 937422 943110 942956 926244 937115 
943216 936717 942904 938885
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Ignoring request to alter blocking bugs of bug #937448 to the same blocks 
previously set
> # python-distutils-extra
> block 937703 by 936641 937114 943270
Bug #937703 [src:python-distutils-extra] python-distutils-extra: Python2 
removal in sid/bullseye
937703 was blocked by: 939107 937114 943270 937457 939111 939109 939106 939104 
939115 936641 936107 939105 936813 939114 939112 939113 936225 938885 849087 
936119 939103 939110 926244 938623 939108 938450
937703 was blocking: 937448 937695 937817 938168 943104
Ignoring request to alter blocking bugs of bug #937703 to the same blocks 
previously set
>
End of message, stopping processing here.

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

Bug#943868: [Pkg-rust-maintainers] Bug#943868: rust-chrono: issues in d/copyright

2019-10-31 Thread kpcyrd

On Wed, Oct 30, 2019 at 06:11:47PM -0700, Sean Whitton wrote:
> There are some inaccuracies in d/copyright.  I'm filing this bug at RC
> severity because the MIT license requires all copyright claims to be
> collated in d/copyright.
> 
> (The package is dual-licensed under Apache-2.0, which the FTP team
> considers a license which does not require that all claims of copyright
> be collated in d/copyright, but it seems easier to just fix d/copyright
> rather than try to rely on the dual-licensing...)
> 
> - `Files: *` stanza has incorrect copyright information.  It should be
>   "Kang Seonghoon and contributors" not just "Kang Seonghoon".
> 
> - `Files: ./src/div.rc` stanza looks to be copyright both Kang
>   Seonghoon and contributors, and also the Rust Project Developers.
> 
> - Similarly `Files: ./src/format/parse.rs` is only /portions/
>   copyrighted by John Nagle, so Kang Seonghoon and contributors would
>   appear to hold copyright too.

This has been fixed in our git repo, but we're still waiting for the
previous upload to go through the NEW queue before we can upload the fix
for this.

You can find our copyright file at:

https://salsa.debian.org/rust-team/debcargo-conf/blob/master/src/chrono/debian/copyright

Feel free to submit a merge request if there are remaining issues.

Thanks!

Bug#942269: marked as done (ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call))

Your message dated Thu, 31 Oct 2019 15:51:21 +
with message-id 
and subject line Bug#942269: fixed in ossim 2.9.1-2
has caused the Debian Bug report #942269,
regarding ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call)
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.)


-- 
942269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ossim
Version: 2.9.1-1
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so
Control: forwarded -1 https://github.com/ossimlabs/ossim/issues/243

Dear Maintainer,

Your package FTBFS with GEOS 3.8.0:

 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'void 
OssimPolyArea2dPrivate::setGeometry(const ossimPolygon&, const 
std::vector&)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:152:64: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createPolygon(geos::geom::LinearRing*&, 
std::vector*&)'
   152 |  m_geometry = geomFactory()->createPolygon(shell, holes);
   |^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:778:109: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createMultiPolygon(std::vector&)
 const'
   778 |
m_privateData->setGeometry(m_privateData->m_geometry->getFactory()->createMultiPolygon(values));
   |
 ^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'bool 
ossimPolyArea2d::loadState(const ossimKeywordlist&, const char*)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:848:64: error: no matching 
function for call to 
'OssimPolyArea2dPrivate::setGeometry(std::unique_ptr)'
   848 | m_privateData->setGeometry(reader.read(wkt.c_str()));
   |^

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: ossim
Source-Version: 2.9.1-2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated ossim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Oct 2019 15:56:16 +0100
Source: ossim
Architecture: source
Version: 2.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 942269
Changes:
 ossim (2.9.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.4.1, no changes.
   * Add upstream patches to fix FTBFS with GEOS 3.8.0.
 (closes: #942269)
   * Drop unused override for file-references-package-build-path.
Checksums-Sha1:
 740c513b53c4f224bd79fcff17bad050d59a5713 2187 ossim_2.9.1-2.dsc
 15bf2ba0cb044e45dc8c1f85b9333e91b593e8ee 48796 ossim_2.9.1-2.debian.tar.xz
 7775fe6c27d4861fad1c21e91a4c457c9c844f59 9196 ossim_2.9.1-2_amd64.buildinfo
Checksums-Sha256:
 63ea8fad59cbe4a1543f5ae2173f1518adba521b1601460f0a60dede39c26183 2187 
ossim_2.9.1-2.dsc
 6e979f23b0c522a44ee7ab267a1aee0a3291022a767e5eea0ec473032fa35b60 48796 
ossim_2.9.1-2.debian.tar.xz
 b78c4e750f3aad435b0d715d21c6ea84c0b1aaf945a9afec1a9f689744cc1f6a 9196 
ossim_2.9.1-2_amd64.buildinfo
Files:
 087317e991053f3287edc934497450d5 2187 science optional ossim_2.9.1-2.dsc
 4b891ad66572785309094927c0389915 48796 science optional 
ossim_2.9.1-2.debian.tar.xz
 49a96e61ef8ea883eea8927317eadcaf 9196 science optional 
ossim_2.9.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl26/ioACgkQZ1DxCuiN
SvGoLw//VNakRx3K8C/WxXell+4fC0EjOpXZCW8PDdCyLboB9sFvpBUinexoL7io
A94qx5kZROyCXetYXKT+MEPf0DWUMHz1Pl1NgF8s4rbp67Y/g+PcMaXqvd3ICpcb
DmDyBKHxrXaJ1OHoLxA+0zcpc7zf0NCZ5elwageeSfK98U+hyB+/az/Mlax6kjNW
tFflQgv1psnxAOZqTkWvQRAkuP3GZTaXsy/WX9sDswGt4IzCh3fL8ObG99yWn1ye

Processed: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.

Processing control commands:

> found -1 twolame/0.4.0-2
Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest: 
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Marked as found in versions twolame/0.4.0-2.
> found -1 ffmpeg/7:4.2.1-1
Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest: 
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Marked as found in versions ffmpeg/7:4.2.1-1.

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

Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.

2019-10-31 Thread Paul Gevers

Source: twolame, ffmpeg
Control: found -1 twolame/0.4.0-2
Control: found -1 ffmpeg/7:4.2.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of twolame the autopkgtest of ffmpeg fails in
testing when that autopkgtest is run with the binary packages of twolame
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
twolamefrom testing0.4.0-2
ffmpeg from testing7:4.2.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of twolame to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=twolame

https://ci.debian.net/data/autopkgtest/testing/amd64/f/ffmpeg/3300508/log.gz

Test 95:
trying muxer 'asf' with 'a' encoder 'libtwolame' for codec 'mp2'

ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a libtwolame -f asf
/tmp/autopkgtest-lxc.m3tk853a/downtmp/autopkgtest_tmp/test/libtwolame.asf
-y -hide_banner -nostdin
Input #0, lavfi, from 'sine=d=0.1':
  Duration: N/A, start: 0.00, bitrate: 705 kb/s
Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (pcm_s16le (native) -> mp2 (libtwolame))
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Error initializing output stream 0:0 -- Error while opening encoder for
output stream #0:0 - maybe incorrect parameters such as bit_rate, rate,
width or height
Conversion failed!



FAILED: asf;a=mp2:libtwolame; encoding return code: 1



signature.asc
Description: OpenPGP digital signature

Bug#943623: I got this too with libclang-9-dev 9.0.0-2 for libclangTooling.a

2019-10-31 Thread Sylvestre Ledru


Le 31/10/2019 à 16:11, Paolo Greppi a écrit :

See:
https://salsa.debian.org/debian/doxygen/-/jobs/393296

ar x /usr/lib/llvm-9/lib/libclangTooling.a
file *.o

yeah, I am aware ;)

The version in experimental should be ok

S

Bug#943899: Should ndisgtk be removed?

2019-10-31 Thread Moritz Muehlenhoff

Package: ndisgtk
Severity: serious

Should ndisgtk be removed?

It's dead upstream (no release for 10 years) and depends on outdated stacks 
scheduled for removal
(python 2, pygtk).

Cheers,
Moritz

Bug#943623: I got this too with libclang-9-dev 9.0.0-2 for libclangTooling.a

2019-10-31 Thread Paolo Greppi

See:
https://salsa.debian.org/debian/doxygen/-/jobs/393296

ar x /usr/lib/llvm-9/lib/libclangTooling.a
file *.o

AllTUsExecution.cpp.o:   LLVM IR bitcode
ArgumentsAdjusters.cpp.o:LLVM IR bitcode
CommonOptionsParser.cpp.o:   LLVM IR bitcode
CompilationDatabase.cpp.o:   LLVM IR bitcode
Execution.cpp.o: LLVM IR bitcode
FileMatchTrie.cpp.o: LLVM IR bitcode
FixIt.cpp.o: LLVM IR bitcode
GuessTargetAndModeCompilationDatabase.cpp.o: LLVM IR bitcode
InterpolatingCompilationDatabase.cpp.o:  LLVM IR bitcode
JSONCompilationDatabase.cpp.o:   LLVM IR bitcode
RefactoringCallbacks.cpp.o:  LLVM IR bitcode
Refactoring.cpp.o:   LLVM IR bitcode
StandaloneExecution.cpp.o:   LLVM IR bitcode
Tooling.cpp.o:   LLVM IR bitcode

Thanks for all your work !

Paolo

Bug#821795: marked as done (lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag')

Your message dated Thu, 31 Oct 2019 11:08:05 -0400
with message-id 
and subject line Re: Bug#821795: lttng-modules-dkms: module FTBFS in jessie 
against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'
has caused the Debian Bug report #821795,
regarding lttng-modules-dkms: module FTBFS in jessie against Linux 3.16: error: 
conflicting types for 'trace_mm_page_alloc_extfrag'
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.)


-- 
821795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lttng-modules-dkms
Version: 2.5.1-1
Severity: serious
Tags: jessie
Control: fixed -1 2.7.2-1

Hi,

while test-building all dkms kernel modules, I noticed that
lttng-modules-dkms/jessie does not (no longer?) build for Linux 3.16 in
jessie:

  CC [M]  /var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-kmem.o
In file included from 
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/../../../probes/define_trace.h:139:0,
 from 
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/kmem.h:380,
 from 
/var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-kmem.c:42:
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:151:6:
 error: conflicting types for 'trace_mm_page_alloc_extfrag'
 void trace_##_name(_proto);
  ^
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:47:2:
 note: in expansion of macro 'DEFINE_EVENT_MAP'
  DEFINE_EVENT_MAP(map, name, map, PARAMS(proto), PARAMS(args))
  ^
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:89:2:
 note: in expansion of macro 'TRACE_EVENT_MAP'
  TRACE_EVENT_MAP(name, name,\
  ^
/var/lib/dkms/lttng-modules/2.5.1/build/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/kmem.h:291:1:
 note: in expansion of macro 'TRACE_EVENT'
 TRACE_EVENT(mm_page_alloc_extfrag,
 ^
In file included from 
/usr/src/linux-headers-3.16.0-4-common/include/trace/events/kmem.h:8:0,
 from 
/var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-kmem.c:31:
/usr/src/linux-headers-3.16.0-4-common/include/linux/tracepoint.h:163:21: note: 
previous definition of 'trace_mm_page_alloc_extfrag' was here
  static inline void trace_##name(proto)\
 ^
/usr/src/linux-headers-3.16.0-4-common/include/linux/tracepoint.h:270:3: note: 
in expansion of macro '__DECLARE_TRACE'
   __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), 1, \
   ^
/usr/src/linux-headers-3.16.0-4-common/include/linux/tracepoint.h:404:2: note: 
in expansion of macro 'DECLARE_TRACE'
  DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
  ^
/usr/src/linux-headers-3.16.0-4-common/include/trace/events/kmem.h:267:1: note: 
in expansion of macro 'TRACE_EVENT'
 TRACE_EVENT(mm_page_alloc_extfrag,
 ^
/usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for 
target '/var/lib/dkms/lttng-modules/2.5.1/build/probes/lttng-probe-kmem.o' 
failed


Andreas


make.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
This bug is not present in oldstable or newer releases.--- End Message ---

Bug#943840: marked as done (python3-rrdtool-dbg: missing Breaks+Replaces: rrdtool-dbg)

Your message dated Thu, 31 Oct 2019 14:49:30 +
with message-id 
and subject line Bug#943840: fixed in rrdtool 1.7.2-3
has caused the Debian Bug report #943840,
regarding python3-rrdtool-dbg: missing Breaks+Replaces: rrdtool-dbg
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.)


-- 
943840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rrdtool-dbg
Version: 1.7.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python3-rrdtool-dbg_1.7.2-2_amd64.deb ...
  Unpacking python3-rrdtool-dbg:amd64 (1.7.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-rrdtool-dbg_1.7.2-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/rrdtool.cpython-37dm-x86_64-linux-gnu.so', 
which is also in package rrdtool-dbg:amd64 1.7.2-1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-rrdtool-dbg_1.7.2-2_amd64.deb


cheers,

Andreas


rrdtool-dbg=1.7.2-1+b1_python3-rrdtool-dbg=1.7.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: rrdtool
Source-Version: 1.7.2-3

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

Debian distribution maintenance software
pp.
Jean-Michel Vourgère  (supplier of updated rrdtool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Oct 2019 09:51:05 +0100
Source: rrdtool
Binary: librrd-dev librrd8 librrd8-dbgsym librrdp-perl librrds-perl 
librrds-perl-dbgsym lua-rrd lua-rrd-dbgsym lua-rrd-dev python3-rrdtool 
python3-rrdtool-dbg rrdcached rrdcached-dbgsym rrdtool rrdtool-dbgsym 
rrdtool-tcl rrdtool-tcl-dbgsym ruby-rrd ruby-rrd-dbgsym
Architecture: source
Version: 1.7.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian RRDtool Team 
Changed-By: Jean-Michel Vourgère 
Description:
 librrd-dev - time-series data storage and display system (development)
 librrd8- time-series data storage and display system (runtime library)
 librrdp-perl - time-series data storage and display system (Perl interface, 
pipe
 librrds-perl - time-series data storage and display system (Perl interface, 
shar
 lua-rrd- time-series data storage and display system (Lua interfaces)
 lua-rrd-dev - time-series data storage and display system (Lua development)
 python3-rrdtool - time-series data storage and display system (Python3 
interface)
 python3-rrdtool-dbg - time-series data storage and display system (Python3 
debug interf
 rrdcached  - data caching daemon for RRDtool
 rrdtool- time-series data storage and display system (programs)
 rrdtool-tcl - time-series data storage and display system (Tcl interface)
 ruby-rrd   - time-series data storage and display system (Ruby interfaces)
Closes: 943840
Changes:
 rrdtool (1.7.2-3) unstable; urgency=medium
 .
   * Added Breaks+Replaces for debug symbols migration. (Closes: #943840)
Checksums-Sha1:
 770a933e366908afc0d6c0fa298c0eeb754fb9bc 2825 rrdtool_1.7.2-3.dsc
 b7ead72c0336e9311fb2e4613b097222449652c9 28036 rrdtool_1.7.2-3.debian.tar.xz
Checksums-Sha256:
 cd190d5fccadea2a25bcabe2f0db7c3b9122c1b559985c9449e8285bfba72a0b 2825 
rrdtool_1.7.2-3.dsc
 b27a4c82caed6f8317625fcddd8e1664cc44b569022c8a4130f563ee6c3c8c3c 28036 
rrdtool_1.7.2-3.debian.tar.xz
Files:
 998ac9517f821bafe21ea4c51908c4b3 2825 utils optional rrdtool_1.7.2-3.dsc
 e1d1c77c82883a4c46f2d9cfea1177cd 28036 utils optional 
rrdtool_1.7.2-3.debian.tar.xz

-BEGIN PGP

Bug#943838: marked as done (grml2usb: check_for_fat() always fails)

Your message dated Thu, 31 Oct 2019 14:47:34 +
with message-id 
and subject line Bug#943838: fixed in grml2usb 0.17.0
has caused the Debian Bug report #943838,
regarding grml2usb: check_for_fat() always fails
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.)


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

The check_for_fat() function always fails, no matter what:

,
| # file -s /dev/sdc2
| /dev/sdc2: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "mkfs.fat", 
sectors/cluster 64, reserved sectors 64, root entries 1024, Media descriptor 
0xf8, sectors/FAT 256, sectors/track 32, heads 64, hidden sectors 27265024, 
sectors 3512319 (volumes > 32 MB), serial number 0xadbb, unlabeled, FAT (16 
bit)
| # sudo grml2usb grml96-full_2018.12.iso /dev/sdc2
| Executing grml2usb version 0.16.7
| Execution failed: Partition /dev/sdc2 does not contain a FAT16 filesystem. 
(Use --fat16 or run mkfs.vfat /dev/sdc2)
| # grml2usb --fat16 grml96-full_2018.12.iso /dev/sdc2
| Executing grml2usb version 0.16.7
| Are you sure you want to format the specified partition with fat16? y/N y
| Note: you can skip this question using the option --force
| Formating partition with fat16 filesystem
| mkfs.fat 4.1 (2017-01-24)
| Execution failed: Partition /dev/sdc2 does not contain a FAT16 filesystem. 
(Use --fat16 or run mkfs.vfat /dev/sdc2)
`

I am not really a Python expert, but AFAICS the problem is that by
default Subprocess.open() opens file objects in binary mode, so the
"filesystem" variable is an array of bytes, and comparing it to a string
always yields false.


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

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

Versions of packages grml2usb depends on:
ii  grub-pc-bin 2.04-3
ii  grub2-common2.04-3
ii  kmod26-3
ii  mtools  4.0.23-1+b1
ii  python3 3.7.5-1
ii  python3-parted  3.11.2-11
ii  rsync   3.1.3-8
ii  syslinux3:6.04~git20190206.bf6db5b4+dfsg1-1

Versions of packages grml2usb recommends:
ii  genisoimage 9:1.1.11-3+b2
ii  syslinux3:6.04~git20190206.bf6db5b4+dfsg1-1
pn  syslinux-utils  

grml2usb suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grml2usb
Source-Version: 0.17.0

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

Debian distribution maintenance software
pp.
Michael Prokop  (supplier of updated grml2usb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Oct 2019 12:00:01 +0100
Source: grml2usb
Binary: grml2usb
Architecture: source
Version: 0.17.0
Distribution: unstable
Urgency: medium
Maintainer: Grml Team 
Changed-By: Michael Prokop 
Description:
 grml2usb   - install Grml system / ISO to usb device
Closes: 943838 943845
Changes:
 grml2usb (0.17.0) unstable; urgency=medium
 .
   [ Sven Joachim ]
   * [5b2ffe4] check_for_fat: Avoid comparing strings and bytes (Closes: 
#943838)
   * [c2e742a] check_boot_flag(): Open device in binary mode
   * [fd89485] Fix path to syslinux *.c32 files (Closes: #943845)
 .
 .
   [ Michael Prokop ]
   * [4d800e5] Provide git-describe based version information when running
 from within git. Thanks to Florian Apolloner for review and feedback
   * [9586781] No longer explicitly list addon files, instead copy all
 files from /boot/addons/
   * [ea3de89] check_for_fat(): use subprocess.check_output to avoid
 dependency on Python 3.7. Thanks to Florian Apolloner for review and
 feedback
Checksums-Sha1:
 987ed3f07546da6ce0357f55eb9e5f472b8e5f0e 1846 grml2usb_0.17.0.dsc

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-31 Thread Matthias Klose

>> And afaik there was no test rebuild for bullseye
>> either.
>
> It does not help to blame people for not doing a rebuild when there is no 
rebuild necessary.

Please could you turn off your mode feeling attacked by any email, before you 
understood these?

On 31.10.19 15:33, rene.engelh...@mailbox.org wrote:

Hi,

Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :

And afaik there was no test rebuild for
bullseye
either.

Accepted cppunit 1.14.0-4 (source) into unstable
On July 26:
https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into-unstable/

Buster release was 3 weeks before that. So this "no test rebuild for bullseye" 
is not true.

bullseye didn't see any test rebuild of the archive, and filing of FTBFS bugs 
yet.

Processed: py2removal blocks updates - 2019-10-31 14:35:31.386543+00:00

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # chardet
> block 936289 by 936214
Bug #936289 [src:chardet] chardet: Python2 removal in sid/bullseye
936289 was blocked by: 936196 937446 936297 937339 943240 93 938355 936511 
936661 938718 936270 937300 936710 937425 936709 937691
936289 was blocking: 937558 937695 937823 938168
Added blocking bug(s) of 936289: 936214
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools: Python2 removal in sid/bullseye
936813 was blocked by: 939106 936812
936813 was blocking: 936371 936485 936757 936812 937448 937695 937703 938305 
939106 943104
Ignoring request to alter blocking bugs of bug #936813 to the same blocks 
previously set
> # pygobject
> block 937448 by 942966 936214
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 943093 936221 943103 938885 938596 943252 936900 943245 
936981 939109 936173 936619 936166 943300 942941 939104 942919 938583 938614 
937181 936813 938623 943117 938837 938327 936371 936748 943178 937688 936601 
937956 937422 936758 937114 937454 938665 942966 936841 942988 938084 939112 
938584 942956 926244 936632 938799 938511 936539 937339 936398 939115 938591 
938160 943023 938780 943294 938464 943110 936225 943230 938590 936624 935358 
938637 938604 936265 936670 943186 936721 936717 943076 937099 943146 938586 
936833 937419 943108 943129 883161 938361 936718 942904 936266 937388 938803 
938582 938593 938293 939114 943216 938329 942916 938789 939106 943123 93 
937628 936531 943151 937703 937457 937115 936995 938884 943291 937405 943270 
936789 937803 943131
937448 was blocking: 936371 937397 937439 937447 937558 937579 937695 938168 
942941 943104
Added blocking bug(s) of 937448: 936214
> # pyhamcrest
> block 937456 by 938731
Bug #937456 [src:pyhamcrest] pyhamcrest: Python2 removal in sid/bullseye
937456 was not blocked by any bugs.
937456 was not blocking any bugs.
Added blocking bug(s) of 937456: 938731
> # python-defaults
> block 937695 by 943048 937456
Bug #937695 [src:python-defaults] python-defaults: Python2 removal in 
sid/bullseye
937695 was blocked by: 936954 938050 936169 938779 936657 938055 937851 938714 
936442 938702 937492 938885 936159 937792 938402 937081 937867 937317 936742 
938432 936667 937087 938065 938479 938322 937956 936661 943223 938305 937657 
936982 942960 936857 937255 938420 937169 936966 938300 938425 937250 938330 
938416 938716 937667 936340 937742 938685 936317 942950 937265 936867 936792 
938589 937159 938680 938720 936311 936345 943173 936956 937260 942955 936660 
938444 936712 943105 943049 937085 936704 937860 943135 936261 937406 938796 
943100 936665 937326 938887 936267 937080 936569 938061 937850 936251 938057 
938373 938744 936559 938051 936434 938280 937261 942957 937397 936310 938746 
937660 937712 937267 936865 937391 942951 938285 937378 937665 936326 936341 
938727 938427 937251 937324 938331 936850 938301 937412 936855 938421 937257 
938337 938189 937559 936736 937404 938794 938307 943122 936706 937262 943043 
943194 938854 938682 937711 936790 937286 943008 937392 938558 937740 943038 
937717 938666 937417 937252 938314 937440 942986 936284 936985 938864 943203 
937445 937411 938568 936495 938084 938379 938656 939259 943121 936745 938654 
943144 936262 936717 936188 936740 938866 938400 937563 937490 938700 943277 
936440 938730 937495 938705 943298 938856 943196 937553 938735 938052 938183 
936445 943120 937588 937064 936981 937447 938256 937410 937336 943116 937884 
943125 943218 936724 936852 937415 937441 937426 937726 938168 937054 936424 
937715 936886 936153 936778 937710 943229 936312 938473 936862 936797 936304 
936336 936447 938737 938394 937497 938707 936426 937852 937684 937724 938731 
936652 936884 943275 938701 937491 937153 937082 937791 938583 937778 943114 
938431 938327 936741 943102 936726 936686 937304 938407 937066 938437 937334 
937312 936710 938346 938243 936520 942977 937144 938613 936629 936789 938592 
936525 942998 942971 937196 937532 937514 936146 937271 936870 938003 936489 
937675 936999 937579 936875 936127 937038 938909 938293 943286 942933 936358 
937516 938542 937525 937194 936829 938363 943262 937489 937870 936298 936271 
936670 936532 936514 936196 937203 937618 937875 938098 938353 937233 939482 
936949 936818 938388 936877 937275 937803 936125 937677 937544 943056 938192 
936898 936120 937270 937848 937671 943163 942970 936527 937179 938608 938638 
939109 937102 936521 938029 942975 936546 937132 938643 937114 943153 937596 
936544 936833 938759 937218 937125 936803 938070 936974 936275 937116 938923 
936848 936919 942929 943064 937648 938469 937898 938808 938769 937383 936179 
938838 937229 937527 942918 936596 936132 936114 943054 938843 938459 936928 
938693 937013 937521 936535 936609 936505 937768 938141

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-31 Thread rene . engelhard

Hi,

Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :
>And afaik there was no test rebuild for
>bullseye 
>either.

Accepted cppunit 1.14.0-4 (source) into unstable 
On July 26: 
https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into-unstable/

Buster release was 3 weeks before that. So this "no test rebuild for bullseye" 
is not true.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-31 Thread rene . engelhard

Hi,

Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :
>On 29.10.19 15:09, Vincent Lefevre wrote:
>> On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
>>> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre
>:
 In case makefile magic triggers some rebuild, you can also run the
 generated executable directly (with the right environment
>variables,
 in case this matters). If the programs honors the system ABI, this
 is allowed, and you'll effectively test the new libstdc++6.
>>>
>>> No, if the rebuild rebuilds cppunittester or one of the
>>> exceptionprotectors or the smoketest so or similar we are at the
>>> same situation as with the autopkgtest (that's what it builds) and
>>> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
>>> test are an executable it's a executable with gazillions of .sos.
>> 
>> I meant running the generated program (smoketest) without rebuilding
>> it:
>> 
>> 1. Build smoketest with the old g++-9 / libstdc++6.
>> 2. Upgrade g++-9 / libstdc++6.
>> 3. Run smoketest directly.
>> 
>> (I assume that the smoketest executable does not invoke g++-9 to
>> rebuild things on the fly.)
>
>I'm not sure if Rene wants to help tracking this down, he just disabled
>running 
>the test in
>https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/99764f8d0df2f40aba9a220a8a4858d3f6d05494

*temporarily*

>and introducing a typo in
>https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/998c3b1c63bbedf8d886227749279d7ccb26a30b
>So maybe don't commit if you are angry.
>

Maybe, yes, but I needed to get it builds le got the upload. Will fix, thanks.

><_rene_> how supported is clang on the various (release) archs?
><_rene_> completely?
><_rene_> (clang++ if it matters)
><_rene_> (actually probably only matters for amd64/arm64 for now,
>but...)
>
>so I assume we cannot expect Rene's help for that issue anymore.

Unfortunately the tests fail when LO is built with clang. So yes, we need to 
track it down.

>The comment about cppunit made me look at the cppunit package to find
>#935902, 
>and yes, the test case is reproducible. So looking at the test failure
>would 
>have been revealed that the test frame work is broken, not a single
>test. 

I said in some comment that "the first" test failed: basic_scanner.

I didn't say smoketest was the only one. It's the only one done in autopkgtest 
though.

This 
>turned out to be https://gcc.gnu.org/PR92267, causing an ABI breakage
>in 
>cppunit. The fix is now in -16.

Ok. Will try. Then I can add build-conflcts or so and reenable the tests.

>So a symbols file and a test rebuild should have at least flagged
>something, however cppunit doesn't have symbols files, because the
>package 
>maintainer doesn't like them.

For C++ and the mangling and handling it in all arxgs, yes.

> And afaik there was no test rebuild for
bullseye 
>l either.

It does not help to blame people for not doing a rebuild when there is no 
rebuild necessary.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#943895: Please migrate to PostgreSQL 12

2019-10-31 Thread Christoph Berg

Source: glom
Version: 1.30.4-3
Severity: serious

Hi,

postgresql-11 is being replaced by postgresql-12. Please upgrade glom
accordingly.

Thanks,
Christoph


signature.asc
Description: PGP signature

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-31 Thread Matthias Klose

On 29.10.19 15:09, Vincent Lefevre wrote:

On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:

Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :

In case makefile magic triggers some rebuild, you can also run the
generated executable directly (with the right environment variables,
in case this matters). If the programs honors the system ABI, this
is allowed, and you'll effectively test the new libstdc++6.

No, if the rebuild rebuilds cppunittester or one of the
exceptionprotectors or the smoketest so or similar we are at the
same situation as with the autopkgtest (that's what it builds) and
are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
test are an executable it's a executable with gazillions of .sos.

I meant running the generated program (smoketest) without rebuilding
it:

1. Build smoketest with the old g++-9 / libstdc++6.
2. Upgrade g++-9 / libstdc++6.
3. Run smoketest directly.

(I assume that the smoketest executable does not invoke g++-9 to
rebuild things on the fly.)

I'm not sure if Rene wants to help tracking this down, he just disabled running
the test in

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/99764f8d0df2f40aba9a220a8a4858d3f6d05494
and introducing a typo in
https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/998c3b1c63bbedf8d886227749279d7ccb26a30b
So maybe don't commit if you are angry.

<_rene_> how supported is clang on the various (release) archs?
<_rene_> completely?
<_rene_> (clang++ if it matters)
<_rene_> (actually probably only matters for amd64/arm64 for now, but...)

so I assume we cannot expect Rene's help for that issue anymore.

The comment about cppunit made me look at the cppunit package to find #935902,
and yes, the test case is reproducible. So looking at the test failure would
have been revealed that the test frame work is broken, not a single test. This
turned out to be https://gcc.gnu.org/PR92267, causing an ABI breakage in
cppunit. The fix is now in -16.

So a symbols file and a test rebuild should have at least flagged
something, however cppunit doesn't have symbols files, because the package
maintainer doesn't like them. And afaik there was no test rebuild for bullseye
either.

The upstream issue was introduced in May, I don't know why it's only seen now.

Processed: notfound 937986 in 3.40.3-2, found 937986 in 3.36.4-2, notfound 937979 in 1:6.8.1-2 ...

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

> # fix bug metadata to allow archival
> notfound 937986 3.40.3-2
Bug #937986 {Done: Sandro Tosi } [src:python-oslo.utils] 
python-oslo.utils: Python2 removal in sid/bullseye
No longer marked as found in versions python-oslo.utils/3.40.3-2.
> found 937986 3.36.4-2
Bug #937986 {Done: Sandro Tosi } [src:python-oslo.utils] 
python-oslo.utils: Python2 removal in sid/bullseye
Marked as found in versions python-oslo.utils/3.36.4-2.
> notfound 937979 1:6.8.1-2
Bug #937979 {Done: Sandro Tosi } [src:python-oslo.config] 
python-oslo.config: Python2 removal in sid/bullseye
No longer marked as found in versions python-oslo.config/1:6.8.1-2.
> found 937979 1:6.4.1-1
Bug #937979 {Done: Sandro Tosi } [src:python-oslo.config] 
python-oslo.config: Python2 removal in sid/bullseye
Marked as found in versions python-oslo.config/1:6.4.1-1.
> reassign 935911 src:rust-md5 0.3.8-1
Bug #935911 {Done: kpcyrd } [src:rust-uuid] 
librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev
Bug reassigned from package 'src:rust-uuid' to 'src:rust-md5'.
No longer marked as found in versions rust-uuid/0.7.2-2.
No longer marked as fixed in versions rust-md5/0.6.1-1.
Bug #935911 {Done: kpcyrd } [src:rust-md5] 
librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev
Marked as found in versions rust-md5/0.3.8-1.
> fixed 935911 0.6.1-1
Bug #935911 {Done: kpcyrd } [src:rust-md5] 
librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev
Marked as fixed in versions rust-md5/0.6.1-1.
> affects 935911 + src:rust-uuid
Bug #935911 {Done: kpcyrd } [src:rust-md5] 
librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev
Added indication that 935911 affects src:rust-uuid
> tags 935911 + sid bullseye
Bug #935911 {Done: kpcyrd } [src:rust-md5] 
librust-uuid+md5-dev/amd64 unsatisfiable Depends: librust-md5-0.6+default-dev
Added tag(s) sid and bullseye.
> notfound 693986 3.14.0-3
Bug #693986 {Done: Christian Göttsche } [logrotate] 
logrotate: create option does not support acls
No longer marked as found in versions logrotate/3.14.0-3.
> fixed 742099 2.13.2-2
Bug #742099 {Done: Matthias Klose } [zc.buildout] Please 
provide Python3 support
There is no source info for the package 'zc.buildout' at version '2.13.2-2' 
with architecture ''
Unable to make a source version for version '2.13.2-2'
Marked as fixed in versions 2.13.2-2.
> fixed 869446 2.13.2-2
Bug #869446 {Done: Matthias Klose } [src:zc.buildout] Updating 
the zc.buildout Uploaders list
The source 'zc.buildout' and version '2.13.2-2' do not appear to match any 
binary packages
Marked as fixed in versions zc.buildout/2.13.2-2.
> tags 937327 + experimental
Bug #937327 {Done: Laszlo Boszormenyi (GCS) } [src:protobuf] 
protobuf: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 940524 - buster
Bug #940524 {Done: Georg Faerber } [schleuder] schleuder: 
fails to recognize keywords in mails with protected headers and empty subject
Removed tag(s) buster.
> tags 940526 - buster
Bug #940526 {Done: Georg Faerber } [schleuder] schleuder: 
vulnerable to signature-flooded keys
Removed tag(s) buster.
> tags 940527 - buster
Bug #940527 {Done: Georg Faerber } [schleuder] schleuder: 
should error out if argument provided to 'refresh_keys' is no list
Removed tag(s) buster.
> reassign 890734 src:texlive-bin
Bug #890734 {Done: Norbert Preining } [texlive-metapost] 
texlive-metapost: mpost does not honour SOURCE_DATE_EPOCH
Bug reassigned from package 'texlive-metapost' to 'src:texlive-bin'.
No longer marked as found in versions texlive-base/2016.20170123-5.
No longer marked as fixed in versions texlive-bin/2019.20190605.51237-3.
> fixed 890734 2019.20190605.51237-3
Bug #890734 {Done: Norbert Preining } [src:texlive-bin] 
texlive-metapost: mpost does not honour SOURCE_DATE_EPOCH
Marked as fixed in versions texlive-bin/2019.20190605.51237-3.
> notfixed 852170 3.4
Bug #852170 {Done: Norbert Preining } 
[cinnamon-control-center] cinnamon-control-center: Inconsistency in settings 
for Trackpad (edge-scrolling vs two-finger-scrolling)
There is no source info for the package 'cinnamon-control-center' at version 
'3.4' with architecture ''
Unable to make a source version for version '3.4'
No longer marked as fixed in versions 3.4.
> fixed 852170 3.4.0-1
Bug #852170 {Done: Norbert Preining } 
[cinnamon-control-center] cinnamon-control-center: Inconsistency in settings 
for Trackpad (edge-scrolling vs two-finger-scrolling)
Marked as fixed in versions cinnamon-control-center/3.4.0-1.
> reassign 929654 src:node-unicode-data 0~20190414+gitbf518e99-2
Bug #929654 {Done: Xavier } [node-unicode-12.0.0] Outdated 
node-unicode-property-value-aliases results in incomplete package rebuild
Bug reassigned from package 'node-unicode-12.0.0' to 'src:node-unicode-data'.
No longer marked as found in versions 
node-unicode-data/0~20190414+gitbf518e99-2.
No longer marked as fixed in versions

Processed: Bug#943765 marked as pending in gdcm

Processing control commands:

> tag -1 pending
Bug #943765 [libvtkgdcm3-dev] libvtkgdcm3-dev: missing Breaks+Replaces: 
libvtkgdcm2-dev
Added tag(s) pending.

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

Bug#943765: marked as pending in gdcm

2019-10-31 Thread Gert Wollny

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/gdcm/commit/3b564e917769f50aae98c33043870e6887b6d9de


d/control: Add Breaks/Replaces for *gdcm2-dev Closes: #943765

Also rename the dev package from *gdcm3-dev to plain gdcm-dev.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943765

Processed: fixed 936307 in claws-mail/3.17.4-2

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

> fixed 936307 claws-mail/3.17.4-2
Bug #936307 [src:claws-mail] claws-mail: Python2 removal in sid/bullseye
Marked as fixed in versions claws-mail/3.17.4-2.
> thanks
Stopping processing here.

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

Bug#943876: marked as done (linux breaks systemtap autopkgtest: error: this statement may fall through [-Werror=implicit-fallthrough=])

Your message dated Thu, 31 Oct 2019 11:49:15 +
with message-id 
and subject line Bug#943876: fixed in systemtap 4.1-11
has caused the Debian Bug report #943876,
regarding linux breaks systemtap autopkgtest: error: this statement may fall 
through [-Werror=implicit-fallthrough=]
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.)


-- 
943876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux, systemtap
Control: found -1 linux/5.3.7-1
Control: found -1 systemtap/4.1-10
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of linux the autopkgtest of systemtap fails in
testing when that autopkgtest is run with the binary packages of linux
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
linux  from testing5.3.7-1
systemtap  from testing4.1-10
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of linux to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package? If needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
linux/5.3.7-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=linux

https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/3297749/log.gz

autopkgtest [17:24:37]: test build-hello: [---
WARNING: Kernel function symbol table missing [man warning::symbols]
Pass 1: parsed user script and 476 library scripts using
95952virt/82936res/7544shr/75500data kb, in 230usr/50sys/280real ms.
Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using
97536virt/84640res/7672shr/77084data kb, in 10usr/0sys/9real ms.
Pass 3: translated to C into "/tmp/stapKkW4rr/hello_src.c" using
97536virt/84640res/7672shr/77084data kb, in 0usr/0sys/0real ms.
In file included from /usr/share/systemtap/runtime/linux/print.c:18,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from /tmp/stapKkW4rr/hello_src.c:56:
/usr/share/systemtap/runtime/vsprintf.c: In function ‘_stp_vsnprintf’:
/usr/share/systemtap/runtime/vsprintf.c:641:35: error: this statement
may fall through [-Werror=implicit-fallthrough=]
  641 | flags |= STP_LARGE;
  | ~~^~~~
/usr/share/systemtap/runtime/vsprintf.c:642:21: note: here
  642 | case 'x':
  | ^~~~
/usr/share/systemtap/runtime/vsprintf.c:828:10: error: this statement
may fall through [-Werror=implicit-fallthrough=]
  828 |flags |= STP_LARGE;
  |~~^~~~
/usr/share/systemtap/runtime/vsprintf.c:829:3: note: here
  829 |   case 'x':
  |   ^~~~
cc1: all warnings being treated as errors
make[2]: ***
[/usr/src/linux-headers-5.3.0-1-common/scripts/Makefile.build:285:
/tmp/stapKkW4rr/hello_src.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:1639:
_module_/tmp/stapKkW4rr] Error 2
make: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make]
Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "hello.ko" in 11380usr/1860sys/13245real ms.
Pass 4: compilation failed.  [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
autopkgtest [17:24:51]: test build-hello: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: systemtap
Source-Version: 4.1-11

We believe that the bug you reported is fixed in the latest version of
systemtap, 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

Bug#943445: marked as done (the autopkg test calls python instead of python2)

Your message dated Thu, 31 Oct 2019 09:37:44 +0100
with message-id <53b5ceb3-4826-d87a-05d4-d846d0e1e...@debian.org>
and subject line Python 2 modules have been removed
has caused the Debian Bug report #943445,
regarding the autopkg test calls python instead of python2
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.)


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

Package: src:python-fann2
Version: 1:1.1.2+ds-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448288137/python-fann2_1%3A1.1.2+ds-1build1_1%3A1.1.2+ds-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Version: 1:1.1.2+ds-2

Module python-pyfann and python-fann2 had no reverse dependencies, and
have been removed. The package builds only the Python 3 module now.--- End Message ---

Bug#943843: marked as done (mailutils-doc: missing Breaks+Replaces: mailutils (<< 1:3.7))

Your message dated Thu, 31 Oct 2019 09:23:45 +
with message-id 
and subject line Bug#943843: fixed in mailutils 1:3.7-2
has caused the Debian Bug report #943843,
regarding mailutils-doc: missing Breaks+Replaces: mailutils (<< 1:3.7)
to be marked as done.

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

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


-- 
943843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailutils-doc
Version: 1:3.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../mailutils-doc_1%3a3.7-1_all.deb ...
  Unpacking mailutils-doc (1:3.7-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/mailutils-doc_1%3a3.7-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/mailutils/AUTHORS', which is also in 
package mailutils 1:3.5-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/mailutils-doc_1%3a3.7-1_all.deb


cheers,

Andreas


mailutils=1:3.5-3_mailutils-doc=1:3.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mailutils
Source-Version: 1:3.7-2

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated mailutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Oct 2019 09:44:14 +0100
Source: mailutils
Architecture: source
Version: 1:3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Jordi Mallach 
Closes: 943787 943843
Changes:
 mailutils (1:3.7-2) unstable; urgency=medium
 .
   * Add missing Break+Replaces to handle the new location of files
 from mailutils-doc with the switch to the dh sequencer and v12.
 Thanks, Andreas Beckmann (closes: #943843).
   * Source-only upload, after going through NEW (closes: #943787).
Checksums-Sha1:
 7c418ab9cc13dd6fb346d158676cd644fa1700a0 3055 mailutils_3.7-2.dsc
 92e55b995d7d3ff213e88264dae75e6b77fbb4cf 28568 mailutils_3.7-2.debian.tar.xz
 dc1411af015a745edb30a1a7a83500624a3e0e99 13574 mailutils_3.7-2_amd64.buildinfo
Checksums-Sha256:
 1febcac6231c778ddf86dd49b23ac572b8a65586875c93321bcda4d55fe7a239 3055 
mailutils_3.7-2.dsc
 39d9c0b4899f31205b004e7bb4fb24ab8028349249240930e3c675dc3d6f3304 28568 
mailutils_3.7-2.debian.tar.xz
 5ba27da588892106a91c8c4b113443f2295e460d835ed21f2b2aa7e06b5244bc 13574 
mailutils_3.7-2_amd64.buildinfo
Files:
 3e8dc61ee158aef841be870861bcc39e 3055 mail optional mailutils_3.7-2.dsc
 cf422fd3eb54e0b46504aec18ed283bc 28568 mail optional 
mailutils_3.7-2.debian.tar.xz
 6d04e931c4424d3bfa3b979d3020c0fd 13574 mail optional 
mailutils_3.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAl26n9kACgkQJVAvb8vj
ywR+1hAAiD1G/9ntRwXVy2XIqJ23aSSHKQ8cbVN7Bhr8GObyxOgSu4MyvzqzacVM
VLucfF1gOlg3zlKh78l/+xMeoDFBtFQ8XWjsjzDRDf3Xp0s+xY/D6Lu4MvNsV2CX
tV8UQ83RKhk5npynlrQZJfLEmny8SQEwQ74nJsxyjeyPgHgFVjKtfw1v2t6SgGtq
7yRUPAAbC+K3QMDbQMzVC5uWF//Zvy+xL8BMDpivpIr3nAXTaU/d6HJJja9myuvN
dxSB8S7mbq7mWgk7FoTTfPNoXoXMldUzfCDeCe2hhlJDviyDmB4BwGx5eSVDOyGX
8tPTSMRneeYtZVkK+d35n+GHaAKvp4kc6rLtXa9e6yVB6oJbHgH2Qy4ftdjpqyYi
3Yv4J3z7hf/VwQGveto61nnu8J42Ka8oBdwfq8tyiLhnl2RLXbYyt+pA5tbDCaNm
hfkk1ycz4FS9GUfNaNyXcu1HylqY5UmPuOE/0uNICpY4mK31gwDl9Qp5miRMYENe
2REngrW5LxR6/23TqTb5EmmGZA0LqRp+8Cme+QEm+F3zWXdi8jHQWhpNt3stoOPu
lmthDWQMHudMh70cbpxoU1aDpZU36vYPuv0RAGd4f1RlnKgntNjFrp1RqoyK+rO1
NLJ/ho3xnR9Jx20dUhUugReuv8W7T+Plwp5zROynjvh8QNNXj/c=
=Ywqa
-END PGP SIGNATURE End Message ---

Processed: Bug#943840 marked as pending in rrdtool

Processing control commands:

> tag -1 pending
Bug #943840 [python3-rrdtool-dbg] python3-rrdtool-dbg: missing Breaks+Replaces: 
rrdtool-dbg
Added tag(s) pending.

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

Bug#943840: marked as pending in rrdtool

2019-10-31 Thread Jean-Michel Vourgère

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/rrdtool-team/rrdtool/commit/42ed9fd3b24ce895d3565aebb897bac734453083


Added Breaks+Replaces for debug symbols migration

Closes: #943840


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943840

Bug#915708: eviacam FTBFS against opencv 3.4.4 in experimental

2019-10-31 Thread Cesar Mauri

Fixed (hopefully) in upstream.

Source code is here: https://github.com/cmauri/eviacam

And also uploaded to mentors here: https://mentors.debian.net/package/eviacam

Bug#922578: FTBFS against opencv 4.0.1 (exp)

2019-10-31 Thread Cesar Mauri

Fixed opencv4 compatibility for eviacam in upstream.

Source code is here: https://github.com/cmauri/eviacam

And also uploaded to mentors here: https://mentors.debian.net/package/eviacam

Bug#943877: libayatana-indicator FTBFS: libayatana-indicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror]

2019-10-31 Thread Helmut Grohne

Source: libayatana-indicator
Version: 0.6.2-3
Severity: serious
Tags: ftbfs

libayatana-indicator fails to build from source in unstable on amd64.

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libayatana-indicator_0.6.2-3.rbuild.log.gz
| ../../../libayatana-indicator/indicator-object.c: In function 
'indicator_object_init':
| ../../../libayatana-indicator/indicator-object.c:307:13: error: G_ADD_PRIVATE 
[-Werror]
|   307 |  IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, 
INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate);
|   | ^~~
| cc1: all warnings being treated as errors
| make[5]: *** [Makefile:696: 
libayatana_indicator_la-indicator-desktop-shortcuts.lo] Error 1

Also affects cross building to ppc64el.
http://crossqa.debian.net/build/libayatana-indicator_0.6.2-3_ppc64el_20191018185417.log

Helmut

Processed: linux breaks systemtap autopkgtest: error: this statement may fall through [-Werror=implicit-fallthrough=]

Processing control commands:

> found -1 linux/5.3.7-1
Bug #943876 [src:linux, src:systemtap] linux breaks systemtap autopkgtest: 
error: this statement may fall through [-Werror=implicit-fallthrough=]
Marked as found in versions linux/5.3.7-1.
> found -1 systemtap/4.1-10
Bug #943876 [src:linux, src:systemtap] linux breaks systemtap autopkgtest: 
error: this statement may fall through [-Werror=implicit-fallthrough=]
Marked as found in versions systemtap/4.1-10.

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

Bug#943876: linux breaks systemtap autopkgtest: error: this statement may fall through [-Werror=implicit-fallthrough=]

2019-10-31 Thread Paul Gevers

Source: linux, systemtap
Control: found -1 linux/5.3.7-1
Control: found -1 systemtap/4.1-10
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of linux the autopkgtest of systemtap fails in
testing when that autopkgtest is run with the binary packages of linux
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
linux  from testing5.3.7-1
systemtap  from testing4.1-10
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of linux to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package? If needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
linux/5.3.7-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=linux

https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/3297749/log.gz

autopkgtest [17:24:37]: test build-hello: [---
WARNING: Kernel function symbol table missing [man warning::symbols]
Pass 1: parsed user script and 476 library scripts using
95952virt/82936res/7544shr/75500data kb, in 230usr/50sys/280real ms.
Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using
97536virt/84640res/7672shr/77084data kb, in 10usr/0sys/9real ms.
Pass 3: translated to C into "/tmp/stapKkW4rr/hello_src.c" using
97536virt/84640res/7672shr/77084data kb, in 0usr/0sys/0real ms.
In file included from /usr/share/systemtap/runtime/linux/print.c:18,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from /tmp/stapKkW4rr/hello_src.c:56:
/usr/share/systemtap/runtime/vsprintf.c: In function ‘_stp_vsnprintf’:
/usr/share/systemtap/runtime/vsprintf.c:641:35: error: this statement
may fall through [-Werror=implicit-fallthrough=]
  641 | flags |= STP_LARGE;
  | ~~^~~~
/usr/share/systemtap/runtime/vsprintf.c:642:21: note: here
  642 | case 'x':
  | ^~~~
/usr/share/systemtap/runtime/vsprintf.c:828:10: error: this statement
may fall through [-Werror=implicit-fallthrough=]
  828 |flags |= STP_LARGE;
  |~~^~~~
/usr/share/systemtap/runtime/vsprintf.c:829:3: note: here
  829 |   case 'x':
  |   ^~~~
cc1: all warnings being treated as errors
make[2]: ***
[/usr/src/linux-headers-5.3.0-1-common/scripts/Makefile.build:285:
/tmp/stapKkW4rr/hello_src.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:1639:
_module_/tmp/stapKkW4rr] Error 2
make: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make]
Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "hello.ko" in 11380usr/1860sys/13245real ms.
Pass 4: compilation failed.  [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
autopkgtest [17:24:51]: test build-hello: ---]



signature.asc
Description: OpenPGP digital signature

Bug#943850: marked as done (python3-python-qt-binding: missing Breaks+Replaces: python-qt-binding)

Your message dated Thu, 31 Oct 2019 07:34:26 +
with message-id 
and subject line Bug#943850: fixed in ros-python-qt-binding 0.3.6-3
has caused the Debian Bug report #943850,
regarding python3-python-qt-binding: missing Breaks+Replaces: python-qt-binding
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.)


-- 
943850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-python-qt-binding
Version: 0.3.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../python3-python-qt-binding_0.3.6-2_all.deb ...
  Unpacking python3-python-qt-binding (0.3.6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-python-qt-binding_0.3.6-2_all.deb (--unpack):
   trying to overwrite '/usr/share/pkgconfig/python_qt_binding.pc', which is 
also in package python-qt-binding 0.3.4-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-python-qt-binding_0.3.6-2_all.deb


cheers,

Andreas


python-qt-binding=0.3.4-2_python3-python-qt-binding=0.3.6-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ros-python-qt-binding
Source-Version: 0.3.6-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Oct 2019 08:18:16 +0100
Source: ros-python-qt-binding
Architecture: source
Version: 0.3.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 943850
Changes:
 ros-python-qt-binding (0.3.6-3) unstable; urgency=medium
 .
   * Add breaks/replaces for python-qt-binding.
 Thanks to Andreas Beckmann (Closes: #943850)
Checksums-Sha1:
 5323094d86858d5f5c94085c3af5b3704839d256 2206 ros-python-qt-binding_0.3.6-3.dsc
 425e0bb2f047685abc0f2e40c5a910336fd62aa3 3176 
ros-python-qt-binding_0.3.6-3.debian.tar.xz
 b0ee4b52e06c5265e06f0db00cdb6379470da586 7489 
ros-python-qt-binding_0.3.6-3_source.buildinfo
Checksums-Sha256:
 f4088359b590b62d3d4a09f4421dd677925093d9eb0de1774d0ce83c0f2e5f74 2206 
ros-python-qt-binding_0.3.6-3.dsc
 99eb65145d47e08419e44d450837d3b002c29354eb944f7e65c7dd7a80c2b05b 3176 
ros-python-qt-binding_0.3.6-3.debian.tar.xz
 b193379c7549a277940488c181b5cefdd6743838e60f88a52491ef73508e5744 7489 
ros-python-qt-binding_0.3.6-3_source.buildinfo
Files:
 d1169d5581ef4a1342ac4b548ef6bee9 2206 python optional 
ros-python-qt-binding_0.3.6-3.dsc
 577200c0846487bf6dcbd2da7607d4e4 3176 python optional 
ros-python-qt-binding_0.3.6-3.debian.tar.xz
 9de72750b40fd9a2f46d41816f5bf7d4 7489 python optional 
ros-python-qt-binding_0.3.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl26isUACgkQW//cwljm
lDNW6Q//WRTPIhK6EhSr6iWLkAMGC9ZJfgr7cp0k6n9sNjO9w88UZ+1rAamvDgV+
vjpqRpRPiSD0PQTix1ferE2OdNeKd7MazcaurHbzki7Tcb0NUq543VkP23lC3MQZ
+bhIxMxna2hLTJOhM+Tn9YwPWm/rJLRFrWbdYRTS5TUsQf5lxLEDEEQpCbQqjnCw
oPG54wuOOsbmGHp0z+eJEZxnZ1bn83MF2CUYRHk9AJUSeYzOng6tEO+Gy5xcNfAi
/96/eZD269Srv43Qi07HNB8oMqzBHcPqrOv6bMxyQkoqBEu3cq2Vl0JBBaKvMznF
HoQf2ceAINEVCU85ziMTQ9PfZij2LvtTe3+dG6AxAwh9h1siEAItgZyMg7p2izk5
NYSPBAMoWwDf3r+a63x6X2sLCwyqOcIFtfbzuL/qE/BsgzUgI1kgsVpTO/gh1438
clQfKAnYhEBO0lLkLJtBmpSaw5XdR9ZN2zwEBRD8R6xYZRirZ3x/0pi0KWzgiLkg

Bug#941984: marked as done (backintime: files under the GFDL)

Your message dated Thu, 31 Oct 2019 07:33:55 +
with message-id 
and subject line Bug#941984: fixed in backintime 1.2.1-2
has caused the Debian Bug report #941984,
regarding backintime: files under the GFDL
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.)


-- 
941984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: backintime
Version: 1.1.24-0.1
Severity: serious

Dear maintainer,

Files in the source package matching qt4/docbook/en/* look to be under
the GFDL, not the GPL, as implied by d/copyright.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: backintime
Source-Version: 1.2.1-2

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated backintime 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: Wed, 30 Oct 2019 22:35:50 +0100
Source: backintime
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Wiltshire 
Changed-By: Fabian Wolff 
Closes: 941686 941984 942155
Changes:
 backintime (1.2.1-2) unstable; urgency=medium
 .
   * Source-only reupload after the package has been in the NEW queue
 (due to backintime-qt).
   * Change incorrect dependency on python3-dbus.mainloop.qt to the Qt 5
 python3-dbus.mainloop.pyqt5 (thanks to Michael Weghorn for pointing
 this out to me!) (Closes: #941686).
   * Audit and update debian/copyright (Closes: #941984, #942155).
   * Upgrade to Standards-Version 4.4.1 (no changes).
   * Add additional backintime-qt_polkit.1.gz symlink to backintime.1.gz
 to silence the binary-without-manpage Lintian warning.
Checksums-Sha1:
 191f317e6e8189736435fb28d8e39d40740b7e91 2081 backintime_1.2.1-2.dsc
 89c2f6a92cf5332e3f6ca7367773a97a0d439132 6708 backintime_1.2.1-2.debian.tar.xz
 4675f76b4875d2cce2faa3aef0391f4ac43cf64b 6437 
backintime_1.2.1-2_source.buildinfo
Checksums-Sha256:
 b4a1e06eb1c080d0804e8fa04002954ac760e0a07bfb1b74dd1660bad14089c0 2081 
backintime_1.2.1-2.dsc
 f230a5be85022657ae45d82e14ce7e87cf2ec13deb9c37d10d5e5e41d981ef35 6708 
backintime_1.2.1-2.debian.tar.xz
 9c35c3fdd34450124838d291ea35f5ab6aafaa4ed94f3844ec8851911dae8733 6437 
backintime_1.2.1-2_source.buildinfo
Files:
 4ed84f97cf930af6470aa22dcef0e478 2081 utils optional backintime_1.2.1-2.dsc
 a59133485d24267153edaea48aebfae7 6708 utils optional 
backintime_1.2.1-2.debian.tar.xz
 8416ce35667c2d235fb60c28844836de 6437 utils optional 
backintime_1.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl26inYTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy2m9D/9dIgcgf07oSXu0lcwR7it3A4TTOrE7
Kv6AMLr4pWMZw2ZIZTzR8VBORnKp4/afWrAkGGA+vi3u1k9PqtJdyXgnprqMQcvJ
lfgU5Vh+9IeU5qsRVv74Bxl1R6dN7PhDpdPtoV63K2NiqQztzOJP4nQpyYL/QVNh
O6nqZHpcORydbi23284E/xA5/2oNdVb9RpIie7v6lfvgZCV8toOAj9IPGhQt0iFC
whwQBjt0RSic1tdiXMUR/vzZW9xP8KY//NPWLbmz3L+/ZeDrcM8GWy2Iaam1tiWv
fqXiR/QIUSVe4eVguOhZ+9hKWXuSb6DB9FGJCKSxrAv/fLIPXorBmTGKx6hHqJvI
TAKKdDkHQMoHm4p0OVhYEJTNgm34G9Yw6G2T1zskLn9sPkx5/fzL4cFEumLy0pC2
9dDD0dXb1psgFSkG5Vqg44sjHCdpNGUMFuq/uzyXfscIEJsmT1Q+GBStRmdTmYkk
wGdD3P6Af0xBfYkI27yABasuKC+gV+yhEGAqmfIsbUd6h6MfkfZf9q8JIdF71sLq
JKAje7Po+YXuzOOdDQB+8hO25rPJMKSUbpA+wFKDYrx1SYozB1ay0MIgdnL6eE8a
b0Oq7z/03S9/W80MnMqYB0fvwyLIdOwz802ygUwjqOE/NTGrVXWqu8hRA8uIDHOC
uqOcOb4PPIzEDQ==
=WZ3k
-END PGP SIGNATURE End Message ---

Bug#941686: marked as done (backintime-qt: Version 1.2.1-1 has wrong dependency on qt4 python3-dbus.mainloop)

Your message dated Thu, 31 Oct 2019 07:33:55 +
with message-id 
and subject line Bug#941686: fixed in backintime 1.2.1-2
has caused the Debian Bug report #941686,
regarding backintime-qt: Version 1.2.1-1 has wrong dependency on qt4 
python3-dbus.mainloop
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.)


-- 
941686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: backintime-qt
Version: 1.2.1-1
Severity: normal
Tags: patch

Dear Maintainer,

backintime 1.2.1-1, which is currently in the NEW queue, switched from
Qt 4 to Qt 5.

However, the package still declares a (wrong) dependency on the qt4-based 
package
'python3-dbus.mainloop.qt', which should be replaced by the qt5 version,
'python3-dbus.mainloop.pyqt5' that is now being used.

Best regards,
Michael

PS: Thanks for packaging the new version!


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

Kernel: Linux 5.2.0-2-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages backintime-qt depends on:
ii  backintime-common1.2.1-1
ii  libnotify-bin0.7.8-1
ii  policykit-1  0.105-26
ii  python3  3.7.3-1
ii  python3-dbus.mainloop.pyqt5  5.12.3+dfsg-2
ii  python3-pyqt55.12.3+dfsg-2
ii  x11-utils7.7+4

Versions of packages backintime-qt recommends:
ii  python3-secretstorage  2.3.1-2

Versions of packages backintime-qt suggests:
ii  meld  3.20.0-2

-- no debconf information
>From 4d9751c7d215ebdd56f14239d6edfd0e1db78b19 Mon Sep 17 00:00:00 2001
From: Michael Weghorn 
Date: Thu, 3 Oct 2019 21:26:56 +0200
Subject: [PATCH] d/control: Update python3-dbus.mainloop dep for qt5

Package 'python3-dbus.mainloop.qt' is the qt4 version,
while backintime now uses qt5.

To demonstrate the issue:

$ python3 /usr/share/backintime/qt/serviceHelper.py
Traceback (most recent call last):
  File "/usr/share/backintime/qt/serviceHelper.py", line 74, in 
import dbus.mainloop.pyqt5
ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5'
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 9a19da2..6ea3eee 100644
--- a/debian/control
+++ b/debian/control
@@ -35,7 +35,7 @@ Architecture: all
 Breaks: backintime-kde (<< 1.1.6-1~), backintime-gnome (<< 1.1.6-1~), 
backintime-qt4 (<< 1.2.1-0.1~)
 Replaces: backintime-kde (<< 1.1.6-1~), backintime-gnome (<< 1.1.6-1~), 
backintime-kde4, backintime-qt4 (<< 1.2.1-0.1~)
 Conflicts: backintime-kde4
-Depends: x11-utils, libnotify-bin, python3-pyqt5, python3-dbus.mainloop.qt, 
policykit-1,
+Depends: x11-utils, libnotify-bin, python3-pyqt5, python3-dbus.mainloop.pyqt5, 
policykit-1,
  backintime-common (= ${source:Version}), ${python3:Depends}, ${misc:Depends}
 Recommends: python3-secretstorage
 Suggests: meld | kompare
-- 
2.23.0

--- End Message ---
--- Begin Message ---
Source: backintime
Source-Version: 1.2.1-2

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated backintime 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: Wed, 30 Oct 2019 22:35:50 +0100
Source: backintime
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Wiltshire 
Changed-By: Fabian Wolff 
Closes: 941686 941984 942155
Changes:
 backintime (1.2.1-2) unstable; urgency=medium
 .
   * Source-only reupload after the package has been in the NEW queue
 (due to backintime-qt).
   * Change incorrect dependency on python3-dbus.mainloop.qt to the Qt 5
 python3-dbus.mainloop.pyqt5 (thanks to Michael Weghorn for pointing

Bug#942155: marked as done (backintime: Incomplete debian/copyright, etc.)