Bug#939303: marked as done (matplotlib2: FTBFS unsatisfied b-d on python-pyshp)

[Debian Bug Tracking System]

Your message dated Fri, 13 Sep 2019 01:18:55 +
with message-id 
and subject line Bug#939303: fixed in matplotlib2 2.2.4-1
has caused the Debian Bug report #939303,
regarding matplotlib2: FTBFS unsatisfied b-d on python-pyshp
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.)


-- 
939303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib2
Version: 2.2.3-6
Severity: serious
Justification: fails to build from source

Hi,

src:matplotlib2 currently FTBFS because its build dependencies cannot be
satisfied in Debian unstable. It follows some evidence:

$ dose-builddebcheck --explain --failures --deb-native-arch amd64 
--checkonly=matplotlib2 Packages_main_amd64 Sources
output-version: 1.2
native-architecture: amd64
report:
 -
  package: matplotlib2
  version: 2.2.3-6
  architecture: any,all
  type: src
  status: broken
  reasons:
   -
missing:
 pkg:
  package: python-mpltoolkits.basemap
  version: 1.2.0+dfsg-1
  architecture: amd64
  unsat-dependency: python-pyshp:amd64
 depchains:
  -
   depchain:
-
 package: matplotlib2
 version: 2.2.3-6
 architecture: any,all
 type: src
 depends: python-mpltoolkits.basemap:amd64
 
binary-packages: 90294
source-packages: 30649
broken-packages: 1

Or the debcheck results:

https://qa.debian.org/dose/debcheck/src_unstable_main/1567400407/packages/matplotlib2.html

This failure is also important, because matplotlib2 is necessary to
compile build-essential. See the dependency graph here:

http://paste.debian.net/1098490/

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: matplotlib2
Source-Version: 2.2.4-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 20:34:06 -0400
Source: matplotlib2
Architecture: source
Version: 2.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 923768 939303
Changes:
 matplotlib2 (2.2.4-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release; Closes: #923768
   * debian/control
 - remove basemap from b-d, no longer needed; Closes: #939303
   * debian/patches/*
 - refresh/remove patches merged upstream
   * debian/patches/dont-download-jquery.patch
 - dont try to download jquery during build
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.0.
Checksums-Sha1:
 8c32bdc8ea262f92840b4d648af644d4a4644558 3549 matplotlib2_2.2.4-1.dsc
 13434643ced067f1d5fc757419670f53911a8c79 29090192 matplotlib2_2.2.4.orig.tar.xz
 08f2ddea150c26417596cb0fe76b6b0c464e5e9f 31920 
matplotlib2_2.2.4-1.debian.tar.xz
 191db1808187ddf12466979550c4adf175b5ad05 23681 
matplotlib2_2.2.4-1_source.buildinfo
Checksums-Sha256:
 10880112ed985527daf43a4ac4241838893dd71ada5eabba6dfa840538f0b5ce 3549 
matplotlib2_2.2.4-1.dsc
 079e1b622c7e2ff204b2808ad7f881f7b8bafeee697906e47d325f44a394ee85 29090192 
matplotlib2_2.2.4.orig.tar.xz
 ed2fef36563416dc0f91936ef1fed12ffb3c487cc11272daf006349f61e5373e 31920 
matplotlib2_2.2.4-1.debian.tar.xz
 1d9fbd7e21d82c74bcb0cff88589d06c7a24a4e855662780e82897987987a0c0 23681 
matplotlib2_2.2.4-1_source.buildinfo
Files:
 8f3475b50022d8313a33f7fedbbed122 3549 python optional matplotlib2_2.2.4-1.dsc
 533f58695d251c187053ffd69f1ff62a 29090192 python optional 
matplotlib2_2.2.4.orig.tar.xz
 6eabc4beb30907639494289a456381a9 31920 python optional 
matplotlib2_2.2.4-1.debian.tar.xz
 fd81e95fcf1ce9d707b06d545e895584 23681 python optional 
matplotlib2_2.2.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl165I0ACgkQh588mTgB

Processed: retitle 939529 to RM: gtg -- RoM; python2-only; dead upstream; low popcon; no rdeps ...

[Debian Bug Tracking System]

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

> retitle 939529 RM: gtg -- RoM; python2-only; dead upstream; low popcon; no 
> rdeps
Bug #939529 [src:gtg] gtg: should this package be removed?
Changed Bug title to 'RM: gtg -- RoM; python2-only; dead upstream; low popcon; 
no rdeps' from 'gtg: should this package be removed?'.
> reassign 939529 ftp.debian.org
Bug #939529 [src:gtg] RM: gtg -- RoM; python2-only; dead upstream; low popcon; 
no rdeps
Bug reassigned from package 'src:gtg' to 'ftp.debian.org'.
No longer marked as found in versions gtg/0.3.1-4.
Ignoring request to alter fixed versions of bug #939529 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: retitle 939531 to RM: medit -- RoQA; python2-only; dead upstream; low popcon; no rdeps ...

[Debian Bug Tracking System]

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

> retitle 939531 RM: medit -- RoQA; python2-only; dead upstream; low popcon; no 
> rdeps
Bug #939531 [src:medit] medit: should this package be removed?
Changed Bug title to 'RM: medit -- RoQA; python2-only; dead upstream; low 
popcon; no rdeps' from 'medit: should this package be removed?'.
> reassign 939531 ftp.debian.org
Bug #939531 [src:medit] RM: medit -- RoQA; python2-only; dead upstream; low 
popcon; no rdeps
Bug reassigned from package 'src:medit' to 'ftp.debian.org'.
No longer marked as found in versions medit/1.2.0-3.
Ignoring request to alter fixed versions of bug #939531 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#940130: marked as done (pymca: testsuite failure (segfault))

[Debian Bug Tracking System]

Your message dated Fri, 13 Sep 2019 07:45:42 +0800
with message-id 
and subject line RE:Bug#940130: pymca: testsuite failure (segfault)
has caused the Debian Bug report #940130,
regarding pymca: testsuite failure (segfault)
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.)


-- 
940130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymca
Version: 5.5.1+dfsg-1
Severity: serious

Hello, looks like the package autopkgtest is failing...
testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Segmentation fault

https://ci.debian.net/packages/p/pymca/testing/amd64

can you please have a look?
--- End Message ---
--- Begin Message ---
oh, come on--- End Message ---

Bug#940138: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Thu, 2019-09-12 at 23:36 +0200, Kendy Kutzner wrote:
[...]
> ** PCI devices:
> 
[...]

Since the panic occurs during PCI initialisation, this is likely to be
very relevant.  However more detail than the default list may be
needed.  Can you please send:

* The output of "lspci -vvnn" when running 4.19.
* The kernel log messages that relate to PCI initialisation when
  running 4.19.  You should be able to get these by running
  "sudo dmesg | grep -E -i '\bpci'" shortly after booting.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.



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

Processed: Re: Bug#940138: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #940138 [src:linux] linux-image-5.2.0-2-amd64: panic in 
pci_assign_unassigned_root_bus_resources
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #940138 [src:linux] linux-image-5.2.0-2-amd64: panic in 
pci_assign_unassigned_root_bus_resources
Added tag(s) moreinfo.

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

Bug#939939: marked as done (libterm-choose-perl: testsuite failures)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 23:08:11 +
with message-id 
and subject line Bug#939939: fixed in libterm-choose-perl 1.701-1
has caused the Debian Bug report #939939,
regarding libterm-choose-perl: testsuite failures
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.)


-- 
939939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libterm-choose-perl
Version: 1.700-1
Severity: serious

Hello, since your last upload the testsuite is now failing.
https://ci.debian.net/packages/libt/libterm-choose-perl/testing/amd64

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libterm-choose-perl/2922560/log.gz

thanks for having a look

Gianfranco
--- End Message ---
--- Begin Message ---
Source: libterm-choose-perl
Source-Version: 1.701-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libterm-choose-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Sep 2019 00:40:48 +0200
Source: libterm-choose-perl
Architecture: source
Version: 1.701-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 939939
Changes:
 libterm-choose-perl (1.701-1) unstable; urgency=medium
 .
   * debian/upstream/metadata: add Bug-Database, remove deprecated Name and
 Contact.
   * Import upstream version 1.701.
 Updates `tput' handling (closes: #939939).
   * Drop redirect patch, fixed in this release.
Checksums-Sha1:
 9df982f9f4bea850d110a25f178b76ba8618e13e 2440 libterm-choose-perl_1.701-1.dsc
 deb4240b007135412f41a8fc7e2bbb9f3f9d063d 56442 
libterm-choose-perl_1.701.orig.tar.gz
 3fbfcb61627a0d18f947da3ba8e9e4e4137aa36f 2384 
libterm-choose-perl_1.701-1.debian.tar.xz
Checksums-Sha256:
 2570ca6f477ccbb24c207e825030b3a9b1134e9dbf00aa14d32defe760ca592a 2440 
libterm-choose-perl_1.701-1.dsc
 3fdfa4768d494a1e896b91f7ab01a6006264aa3a3bed23094d337b72766099e8 56442 
libterm-choose-perl_1.701.orig.tar.gz
 db6b7fdc6c8c5e7fc59f67ad2d022443bac437f82229fdc45282d1fb8f56ea18 2384 
libterm-choose-perl_1.701-1.debian.tar.xz
Files:
 0306431ac790df061d1692666f50d809 2440 perl optional 
libterm-choose-perl_1.701-1.dsc
 350b4b53437f3609aaf8188ddc45e1e2 56442 perl optional 
libterm-choose-perl_1.701.orig.tar.gz
 a3850858e43bcb6e4f4823888c6237e4 2384 perl optional 
libterm-choose-perl_1.701-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl16yhtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgafIA//Xx5Sq9JYWOsGvm6JMukzA3sUceQfoRBZ8/mH32lqfbJuJ5+6XbCBMwnI
jpjsxLTY5Awk3JXqcPqaI/sAU78n1NhJeNTElJCBzUfs6Sb5ZyAz7RFApbv5Hq/K
5w4IoMuRflR9Il2q6B6QtUQ8P7UDzB/iGiNgydS6d+ziIYw3qBI1JsoiM1Za3OkF
yO4x+V2IB+MFG3FJaIwtjCsBoGC2lfn4tlmn7+G/sYGHftcDybUrnUTJDUTI77TX
ZE7YKJu4QItIPF8eCWTJfDcyfWLt6KH3EbShrFdhjt9Mo1g0YH1rMDedOvBCwMYJ
qKu0ic+04YtetT1aTehDT5FMdr/Fjsv8GoZWOv6ylXeT9HqwvInRlLKNRkq1LcwN
gpoMrgjKmIoUZ0x6LRpvtZzV9uIkCVmD65pn2rPX0TwAOLptNfsEiL21Yylvw8pK
Jtiz2ITm6UVLPt2sl9CjAxjdYajlUglw28tE3Qw0lTc42gTNsFwsZiEOjsN09/eP
Tj7Yzc/YOATiT6tKSMppfkHlAzTU5MSGMSpxiyuPFUdepslWoMie+wj87PMBoQ0Q
EcocvcypVNkwjli6Bvb1PALpHvsO4hpbDl/nE2kyStsoxjHVYuRZ4pi/XZMFg1JN
956+jlqoRETaXR/EPtMLaBOp/laNAzFfDA4Z4vNBcnoJrZL0C40=
=pipt
-END PGP SIGNATURE End Message ---

Bug#853594: marked as done (openmama: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 22:49:02 +
with message-id 
and subject line Bug#853594: fixed in openmama 2.2.2.1-12
has caused the Debian Bug report #853594,
regarding openmama: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -I/opt/openmama/include -I./.. 
-I./../../../../mama/c_cpp/src/cpp/mama -I./../../../../mama/c_cpp/src/cpp 
-I./../../../../mama/c_cpp/src/c -I./../../../../common/c_cpp/src/c 
-pedantic-errors -Wall -Wno-long-long -Wno-non-virtual-dtor -D_GNU_SOURCE  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o MamdaLock.lo MamdaLock.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/opt/openmama/include -I./.. 
-I./../../../../mama/c_cpp/src/cpp/mama -I./../../../../mama/c_cpp/src/cpp 
-I./../../../../mama/c_cpp/src/c -I./../../../../common/c_cpp/src/c 
-pedantic-errors -Wall -Wno-long-long -Wno-non-virtual-dtor -D_GNU_SOURCE -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c MamdaLock.cpp  -fPIC -DPIC -o .libs/MamdaLock.o
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -I/opt/openmama/include -I./.. 
-I./../../../../mama/c_cpp/src/cpp/mama -I./../../../../mama/c_cpp/src/cpp 
-I./../../../../mama/c_cpp/src/c -I./../../../../common/c_cpp/src/c 
-pedantic-errors -Wall -Wno-long-long -Wno-non-virtual-dtor -D_GNU_SOURCE  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o MamdaBasicSubscription.lo 
MamdaBasicSubscription.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/opt/openmama/include -I./.. 
-I./../../../../mama/c_cpp/src/cpp/mama -I./../../../../mama/c_cpp/src/cpp 
-I./../../../../mama/c_cpp/src/c -I./../../../../common/c_cpp/src/c 
-pedantic-errors -Wall -Wno-long-long -Wno-non-virtual-dtor -D_GNU_SOURCE -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c MamdaBasicSubscription.cpp  -fPIC -DPIC -o 
.libs/MamdaBasicSubscription.o
MamdaBasicSubscription.cpp: In member function 'virtual void 
Wombat::MamdaBasicSubscription::MamdaBasicSubscriptionImpl::onError(Wombat::MamaBasicSubscription*,
 const Wombat::MamaStatus&, const char*)':
MamdaBasicSubscription.cpp:251:16: warning: enumeration value 
'MAMA_STATUS_NOT_MODIFIABLE' not handled in switch [-Wswitch]
 switch (status.getStatus())
^
MamdaBasicSubscription.cpp:251:16: warning: enumeration value 
'MAMA_STATUS_DELETE' not handled in switch [-Wswitch]
MamdaBasicSubscription.cpp:251:16: warning: enumeration value 
'MAMA_STATUS_SUBSCRIPTION_GAP' not handled in switch [-Wswitch]
MamdaBasicSubscription.cpp:251:16: warning: enumeration value 
'MAMA_STATUS_NOT_INITIALISED' not handled in switch [-Wswitch]
MamdaBasicSubscription.cpp:251:16: warning: enumeration value 
'MAMA_STATUS_NO_SUBSCRIBERS' not handled in switch [-Wswitch]

Bug#940137: marked as done (openmama: FTBFS with Java 10 due to javah removal)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 22:49:02 +
with message-id 
and subject line Bug#940137: fixed in openmama 2.2.2.1-12
has caused the Debian Bug report #940137,
regarding openmama: FTBFS with Java 10 due to javah removal
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.)


-- 
940137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmama
Version: 2.2.2.1-11.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-j...@lists.debian.org
Usertags: default-java10

openmama fails to build with Java 10 due to the removal of javah:

  headers:
   [echo] Generating C header files. Putting in: 
/build/openmama-2.2.2.1/mama/jni/src/c/mamajni
  
  BUILD FAILED
  /build/openmama-2.2.2.1/mama/jni/build.xml:94: Execute failed: 
java.io.IOException: Cannot run program "javah" (in directory 
"/build/openmama-2.2.2.1/mama/jni"): error=2, No such file or directory
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
  at java.base/java.lang.Runtime.exec(Runtime.java:591)
  at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
  at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:424)
  at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:438)
  at 
org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:630)
  at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669)
  at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:497)
  at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
  at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown 
Source)
  at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
  at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
  at org.apache.tools.ant.Task.perform(Task.java:350)
  at org.apache.tools.ant.Target.execute(Target.java:449)
  at org.apache.tools.ant.Target.performTasks(Target.java:470)
  at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1391)
  at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
  at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
  at org.apache.tools.ant.Project.executeTargets(Project.java:1254)
  at org.apache.tools.ant.Main.runBuild(Main.java:830)
  at org.apache.tools.ant.Main.startAnt(Main.java:223)
  at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
  at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
  Caused by: java.io.IOException: error=2, No such file or directory
  at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
  at java.base/java.lang.ProcessImpl.(ProcessImpl.java:340)
  at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:271)
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
  ... 24 more
--- End Message ---
--- Begin Message ---
Source: openmama
Source-Version: 2.2.2.1-12

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated openmama package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Sep 2019 00:09:10 +0200
Source: openmama
Architecture: source
Version: 2.2.2.1-12
Distribution: unstable
Urgency: medium
Maintainer: Daniel Pocock 
Changed-By: Emmanuel Bourg 
Closes: 853594 940137
Changes:
 openmama (2.2.2.1-12) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol 

Bug#939561: marked as done (soapybladerf ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 22:35:50 +
with message-id 
and subject line Bug#939561: fixed in soapybladerf 0.3.5-2
has caused the Debian Bug report #939561,
regarding soapybladerf ftbfs in unstable
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.)


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

Package: src:soapybladerf
Version: 0.3.5-1
Severity: serious
Tags: sid bullseye

soapybladerf ftbfs in unstable:

/usr/bin/c++  -DHAS_BLADERF_GAIN_MODE -DbladeRFSupport_EXPORTS 
-I/<>  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -std=c++11 -fPIC 
-Wno-unused-parameter -Wall -Wextra -fvisibility=hidden -std=gnu++11 -o 
CMakeFiles/bladeRFSupport.dir/bladeRF_Streaming.cpp.o -c 
/<>/bladeRF_Streaming.cpp
/<>/bladeRF_Streaming.cpp: In member function ‘virtual 
SoapySDR::Stream* bladeRF_SoapySDR::setupStream(int, const string&, const 
std::vector&, const Kwargs&)’:
/<>/bladeRF_Streaming.cpp:125:17: error: invalid conversion from 
‘bladerf_module’ {aka ‘int’} to ‘bladerf_channel_layout’ [-fpermissive]

  125 | _dir2mod(direction),
  | ^~~
  | |
  | bladerf_module {aka int}
In file included from /<>/bladeRF_SoapySDR.hpp:26,
 from /<>/bladeRF_Streaming.cpp:22:
/usr/include/libbladeRF.h:2555:58: note:   initializing argument 2 of ‘int 
bladerf_sync_config(bladerf*, bladerf_channel_layout, bladerf_format, unsigned 
int, unsigned int, unsigned int, unsigned int)’

 2555 |   bladerf_channel_layout layout,
  |   ~~~^~
/<>/bladeRF_Streaming.cpp: In member function ‘virtual int 
bladeRF_SoapySDR::writeStream(SoapySDR::Stream*, const void* const*, size_t, 
int&, long long int, long int)’:
/<>/bladeRF_Streaming.cpp:387:41: error: invalid conversion from 
‘bladerf_channel’ {aka ‘int’} to ‘bladerf_direction’ [-fpermissive]

  387 | bladerf_get_timestamp(_dev, BLADERF_MODULE_TX, 
);
  | ^
  | |
  | bladerf_channel {aka int}
/usr/include/libbladeRF.h:2481:55: note:   initializing argument 2 of ‘int 
bladerf_get_timestamp(bladerf*, bladerf_direction, bladerf_timestamp*)’

 2481 | bladerf_direction dir,
  | ~~^~~
/<>/bladeRF_Settings.cpp: In member function ‘virtual double 
bladeRF_SoapySDR::getFrequency(int, size_t, const string&) const’:
/<>/bladeRF_Settings.cpp:411:64: error: cannot convert ‘unsigned 
int*’ to ‘bladerf_frequency*’ {aka ‘long unsigned int*’}

  411 | int ret = bladerf_get_frequency(_dev, _dir2mod(direction), );
  |^
  ||
  |unsigned 
int*

In file included from /<>/bladeRF_SoapySDR.hpp:26,
 from /<>/bladeRF_Settings.cpp:22:
/usr/include/libbladeRF.h:1277:56: note:   initializing argument 3 of ‘int 
bladerf_get_frequency(bladerf*, bladerf_channel, bladerf_frequency*)’

 1277 | bladerf_frequency *frequency);
  | ~~~^
/<>/bladeRF_Settings.cpp: In member function ‘virtual long long int 
bladeRF_SoapySDR::getHardwareTime(const string&) const’:
/<>/bladeRF_Settings.cpp:570:49: error: invalid conversion from 
‘bladerf_channel’ {aka ‘int’} to ‘bladerf_direction’ [-fpermissive]
  570 | const int ret = bladerf_get_timestamp(_dev, BLADERF_MODULE_RX, 
);

  | ^
  | |
  | bladerf_channel {aka 
int}
/usr/include/libbladeRF.h:2481:55: note:   initializing argument 2 of ‘int 
bladerf_get_timestamp(bladerf*, bladerf_direction, bladerf_timestamp*)’

 2481 | bladerf_direction dir,
  | ~~^~~
/<>/bladeRF_Settings.cpp: In member function ‘virtual void 
bladeRF_SoapySDR::writeSetting(const string&, const string&)’:

Bug#866122: kernel resolution

[Barry Arndt]

For reference:
 
While debugging this very tricky problem, our kernel team found 2 separate 
but related bugs whose resolutions fix the problem outlined in this 
report.
 
The bug fixes both resulted in CVEs and have already been added to Linus' 
tree.  They are:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a8318c13e79badb92bc6640704a64cc022a6eb97
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=8205d5d98ef7f155de211f5e2eb6ca03d95a5a60
 
The CVEs are:
https://security-tracker.debian.org/tracker/CVE-2019-15030
https://security-tracker.debian.org/tracker/CVE-2019-15031
 
One of the problems was introduced in 4.12, and the other in 4.15.
 
Barry

Bug#939561: soapybladerf ftbfs in unstable

[Andreas Bombe]

On Thu, Sep 12, 2019 at 04:42:53PM +0100, peter green wrote:
> tags 939561 +fixed-upstream
> tags 939561 +patch
> thanks
> 
> Some googling revealed that upstream had fixed this issue 
> https://github.com/pothosware/SoapyBladeRF/pull/19 . I was able to take the 
> upstream pull request, turn it into a patch series and apply it to the Debian 
> package.
> 
> I have uploaded my fix to raspbian, a debdiff can be found at 
> http://debdiffs.raspbian.org/main/s/soapybladerf/soapybladerf_0.3.5-1+rpi1.debdiff
>  , no intent to NMU in Debian.

Thanks for this, I'm going to use it to upload a fixed revision of the
current version to Debian. I am working on updating all soapysdr modules
now, but with the ABI version change all the transitioning will take a
while so this is a welcome help to cover for the time until that
completes.

Bug#874907: [hydrogen] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann  wrote:
> > Control: tags -1 + fixed-upstream
> >
> > The current upstream beta release supports Qt5.
> > https://github.com/hydrogen-music/hydrogen/releases/tag/1.0.0-beta1
>
> I'll see if I can tackle it during the weekend.

Uuups, it uses cdbs. I'll prepare the NMU switching to dh. If this is
not wanted please say so as soon as possible :-)

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#874812: [amora-server] Future Qt4 removal from Buster

[Axel Beckert]

Hi Moritz

Moritz Mühlenhoff wrote:
> there's been no movement on https://github.com/amora/amora/issues/86 for the
> last 11 months

Yes, IIRC it was like compiling but not yet really working again. Will
have to check.

I'm though currently busy with the Python 2 to 3 migration in WICD
(which really gained speed due to a new upstream maintainer) at the
moment. And WICD clearly has higher priority for me, not only because
of about 100 times more popcon, but also because people are relying on
it daily.

> or we're moving forward with the Qt4 removal.

Just move forward. IIRC amora already has been removed from testing,
so it really shouldn't be an issue for the Qt4 removal.

> How about dropping the amora-applet binary package for now and
> retaining the CLI package?

If I (or upstream) doesn't get it working with Qt5, it's either that
or complete removal. Haven't decided yet as I first want to check how
far the porting is.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#875066: [ofono-phonesim] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Thu, Sep 12, 2019 at 11:12:18PM +0200, Héctor Orón Martínez wrote:
> Hello,
> 
> Missatge de Moritz Mühlenhoff  del dia dj., 12 de set.
> 2019 a les 22:30:
> 
> > Are you planning to port it to Qt5 yourself or shall we remove it from
> > the archive?
> 
> Let's remove it from the archive.

Ack, I've just filed an RM bug.

Cheers,
Moritz

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

[Bob Weber]

I tried upgrading gegl, libgegl-0.4-0, and libgegl-common to :

gegl (0.4.14-1+b2)
libspiro1 (1:20190731-1+b1)<== brought in by upgrading gegl
libgegl-0.4-0 (0.4.12-2 => 0.4.14-1+b2)
libgegl-common (0.4.12-2 => 0.4.14-1)

I run testing but also have unstable pined to a lower priorty than testing so 
apt policy shows the unstable versions also.


Now gimp-v shows :

GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu

Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6)

using GEGL version 0.4.14 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)


So all seems OK with GEGL version 0.4.14 (compiled against version 0.4.14)!

Tried working on a simple jpg image and exported to png without a crash.

Hope this helps.

--
...Bob

Bug#940139: nautilus: open files by double clicking or right click "open"

[Christian Danneberg]

Package: nautilus
Version: 3.30.5-2
Severity: serious
Justification: must

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Since one of the most recently apt upgrades nautilus does not open any files
associated with applications by double click or right click "open". This
happens to all file types! I can browse through the file system as before etc.
no other issue, except the described one. Other users on my system are not
affected, just me (as usual  ).
I found nothing with journalctl.


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



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

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

Versions of packages nautilus depends on:
ii  bubblewrap 0.3.1-4
ii  desktop-file-utils 0.23-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  gvfs   1.38.1-5
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libgexiv2-20.10.9-1
ii  libglib2.0-0   2.58.3-2+deb10u1
ii  libglib2.0-data2.58.3-2+deb10u1
ii  libgnome-autoar-0-00.2.3-2
ii  libgtk-3-0 3.24.5-1
ii  libnautilus-extension1a3.30.5-2
ii  libpango-1.0-0 1.42.4-7~deb10u1
ii  libpangocairo-1.0-01.42.4-7~deb10u1
ii  libseccomp22.3.3-4
ii  libselinux12.8-1+b1
ii  libtracker-sparql-2.0-02.1.8-2
ii  nautilus-data  3.30.5-2
ii  shared-mime-info   1.10-1
ii  tracker2.1.8-2

Versions of packages nautilus recommends:
ii  gnome-sushi  3.30.0-2
ii  gvfs-backends1.38.1-5
ii  librsvg2-common  2.44.10-2.1

Versions of packages nautilus suggests:
ii  atril [pdf-viewer]  1.20.3-1
ii  eog 3.28.4-2+b1
ii  evince [pdf-viewer] 3.30.2-3
ii  gv [pdf-viewer] 1:3.7.4-2
ii  mpg321 [mp3-decoder]0.3.2-3
pn  nautilus-extension-brasero  
ii  nautilus-sendto 3.8.6-3
ii  okular [pdf-viewer] 4:17.12.2-2.2
ii  totem   3.30.0-4
ii  vlc [mp3-decoder]   3.0.8-0+deb10u1
ii  xdg-user-dirs   0.17-2

-- no debconf information

Bug#940137: openmama: FTBFS with Java 10 due to javah removal

[Emmanuel Bourg]

Source: openmama
Version: 2.2.2.1-11.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-j...@lists.debian.org
Usertags: default-java10

openmama fails to build with Java 10 due to the removal of javah:

  headers:
   [echo] Generating C header files. Putting in: 
/build/openmama-2.2.2.1/mama/jni/src/c/mamajni
  
  BUILD FAILED
  /build/openmama-2.2.2.1/mama/jni/build.xml:94: Execute failed: 
java.io.IOException: Cannot run program "javah" (in directory 
"/build/openmama-2.2.2.1/mama/jni"): error=2, No such file or directory
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
  at java.base/java.lang.Runtime.exec(Runtime.java:591)
  at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
  at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:424)
  at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:438)
  at 
org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:630)
  at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669)
  at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:497)
  at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
  at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown 
Source)
  at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
  at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
  at org.apache.tools.ant.Task.perform(Task.java:350)
  at org.apache.tools.ant.Target.execute(Target.java:449)
  at org.apache.tools.ant.Target.performTasks(Target.java:470)
  at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1391)
  at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
  at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
  at org.apache.tools.ant.Project.executeTargets(Project.java:1254)
  at org.apache.tools.ant.Main.runBuild(Main.java:830)
  at org.apache.tools.ant.Main.startAnt(Main.java:223)
  at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
  at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
  Caused by: java.io.IOException: error=2, No such file or directory
  at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
  at java.base/java.lang.ProcessImpl.(ProcessImpl.java:340)
  at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:271)
  at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
  ... 24 more

Bug#940138: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources

[Kendy Kutzner]

Package: src:linux
Version: 5.2.9-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

aptitude upgrade && aptitude update && reboot

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

booting into resuce mode for 5.2.0-2  leads to the same kernel panic
booting into 4.19.0-5 works just fine


Screenshots of the panic and the boot menu: 
https://photos.app.goo.gl/299ykmDM77NBJeDo6

For reference and searchability, the screenshot says

"
RIP ... pci_assign_unassigned_root_bus_resources
...
Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b
"


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1604   
board_vendor: ASUSTeK Computer INC.
board_name: P7H55D-M EVO
board_version: Rev 1.xx

** PCI devices:



** USB devices:


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

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

Versions of packages linux-image-5.2.0-2-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.135
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-5.2.0-2-amd64 recommends:
ii  apparmor 2.13.3-5
ii  firmware-linux-free  3.4

Versions of packages linux-image-5.2.0-2-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.04-3
pn  linux-doc-5.2   

Versions of packages linux-image-5.2.0-2-amd64 is related to:
ii  firmware-amd-graphics 20190717-2
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
ii  firmware-linux-nonfree20190717-2
ii  firmware-misc-nonfree 20190717-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#939662: 回复: Bug#939662 closed by Stephen Kitt (Re: Bug#939662: sys/mman.h not found)

[Stephen Kitt]

On Sun, 8 Sep 2019 01:53:54 +, Zhang Hao  wrote:
> Even though I use the parameter "--host=x86_64-w64-32", the gperftools
> makefile dos not passed. And The gperftools support "mingw-w64" to cross
> compile on linux. You can find it on
> "https://github.com/gperftools/gperftools/issues/878;.

Indeed, I stand corrected!

> And I have report this issue in
> "https://github.com/gperftools/gperftools/issues/1108;. The developer told
> me this is a "#include ." issue, not gperftools' problem.

And it’s not mingw-w64’s problem either: you need to install mman yourself.
See
https://github.com/gperftools/gperftools/issues/1108#issuecomment-519070972

Regards,

Stephen


pgpA_rdFn82WO.pgp
Description: OpenPGP digital signature

Bug#875066: [ofono-phonesim] Future Qt4 removal from Buster

[Héctor Orón Martínez]

Hello,

Missatge de Moritz Mühlenhoff  del dia dj., 12 de set.
2019 a les 22:30:

> Are you planning to port it to Qt5 yourself or shall we remove it from
> the archive?

Let's remove it from the archive.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#874812: [amora-server] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 08:57:09PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: amora-server
> Version: 1.2~svn+git2015.04.25-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

Hi Axel,
there's been no movement on https://github.com/amora/amora/issues/86 for the
last 11 months or we're moving forward with the Qt4 removal. How about
dropping the amora-applet binary package for now and retaining the CLI
package?

Cheers,
Moritz

Bug#939596: marked as done (python3-ndg-httpsclient: trying to overwrite '/usr/bin/ndg_httpclient', which is also in package python-ndg-httpsclient 0.5.1-1)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 20:40:08 +
with message-id 
and subject line Bug#939596: fixed in ndg-httpsclient 0.5.1-3
has caused the Debian Bug report #939596,
regarding python3-ndg-httpsclient: trying to overwrite 
'/usr/bin/ndg_httpclient', which is also in package python-ndg-httpsclient 
0.5.1-1
to be marked as done.

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

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


-- 
939596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ndg-httpsclient
Version: 0.5.1-2
Severity: serious

Dear Maintainer,

your upload seems to have moved /usr/bin/ndg_httpclient (and
potentially further files) from python-ndg-httpsclient to
python3-ndg-httpsclient without the according Breaks and Replaces
headers.

This resulted in the following file conflict when upgrading
python3-ndg-httpsclient from 0.5.1-1 to 0.5.1-2 with
python-ndg-httpsclient being installed, too:

Preparing to unpack .../29-python3-ndg-httpsclient_0.5.1-2_all.deb ...
Unpacking python3-ndg-httpsclient (0.5.1-2) over (0.5.1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-idI8Ph/29-python3-ndg-httpsclient_0.5.1-2_all.deb 
(--unpack):
 trying to overwrite '/usr/bin/ndg_httpclient', which is also in package 
python-ndg-httpsclient 0.5.1-1

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

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

Versions of packages python3-ndg-httpsclient depends on:
ii  python3  3.7.3-1
ii  python3-openssl  19.0.0-1
ii  python3-pyasn1   0.4.2-3

python3-ndg-httpsclient recommends no packages.

python3-ndg-httpsclient suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ndg-httpsclient
Source-Version: 0.5.1-3

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
ndg-httpsclient package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 22:23:05 +0200
Source: ndg-httpsclient
Binary: python3-ndg-httpsclient
Architecture: source
Version: 0.5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Gianfranco Costamagna 
Changed-By: Gianfranco Costamagna 
Description:
 python3-ndg-httpsclient - enhanced HTTPS support for httplib and urllib2 using 
PyOpenSSL fo
Closes: 939596
Changes:
 ndg-httpsclient (0.5.1-3) unstable; urgency=medium
 .
   * Fix typo in breaks/replaces relationship that prevented smooth upgrades
 Closes: #939596.
 - thanks a lot to Axel Beckert  for the report!
Checksums-Sha1:
 9376fb45d56212f7e698efd75e718ecdaaeb9ea8 2090 ndg-httpsclient_0.5.1-3.dsc
 a98263c57ae16d5de38c9e5c8f5ac406ae62cd31 3676 
ndg-httpsclient_0.5.1-3.debian.tar.xz
 86426a3654b983c7c6fffc1a3b1d18d64d8e0de9 8585 
ndg-httpsclient_0.5.1-3_source.buildinfo
Checksums-Sha256:
 76800446793610ace959d5703ad3e85723e81a7aaf370a53277d36172f76d221 2090 
ndg-httpsclient_0.5.1-3.dsc
 e325eaf3f4ebf0052f6343f8d7f88fe7719b3b0ff72f579c383af34c16214a53 3676 
ndg-httpsclient_0.5.1-3.debian.tar.xz
 a5d3e53374b9a13f02c5c058155f1a1fca8fe6b67ff8a241b33b08946951ee6d 8585 
ndg-httpsclient_0.5.1-3_source.buildinfo
Files:
 1244d833857a31d7080423dbb3456cee 2090 python optional 
ndg-httpsclient_0.5.1-3.dsc
 292e2978ce9f1e43e1ee968ecd80ed4e 3676 python optional 
ndg-httpsclient_0.5.1-3.debian.tar.xz
 99b5c8ba1231cd3877695528c2fe11d1 8585 python optional 
ndg-httpsclient_0.5.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl16qWMACgkQ808JdE6f

Bug#874931: [karlyriceditor] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Fri, Aug 23, 2019 at 11:20:58PM +0200, Moritz Mühlenhoff wrote:
> Lisandro Damián Nicanor Pérez Meyer wrote:
> > Source: karlyriceditor
> > 
> > 
> > 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
> 
> Hi Martin,
> current upstream releases (after 2.2) should support Qt5. The last upload by 
> you
> was in March 2016, if you're no longer interested in karlyriceditor, we can
> also remove it.

I've now filed a removal bug.

Cheers,
Moritz

Bug#874907: [hydrogen] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann 
wrote:
> Control: tags -1 + fixed-upstream
>
> The current upstream beta release supports Qt5.
> https://github.com/hydrogen-music/hydrogen/releases/tag/1.0.0-beta1

I'll see if I can tackle it during the weekend.

Bug#874911: [hamfax] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Aug 25, 2019 at 09:33:12PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 09:05:57PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: hamfax
> > 
> > 
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as [announced] in:
> > 
> > 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
> 
> We're now moving forward with the QT4 removal.
> 
> hamfax wasn't changed since 2011 and is dead upstream (last commit is from
> 2012). Does anyone of the Debian Hamradio Maintainers intend to port it to
> Qt5 or should it be removed?

I now filed a removal bug.

Cheers,
Moritz

Bug#875066: [ofono-phonesim] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 10:13:00PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: ofono-phonesim
> Version: 1.20-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

Hi Héctor,
ofono-phonesim seems dead upstream, the last commit is from six years ago.

Are you planning to port it to Qt5 yourself or shall we remove it from
the archive?

Cheers,
Moritz

Bug#940130: pymca: testsuite failure (segfault)

[PICCA Frederic-Emmanuel]

Hello, this is a probleme due to a bug in python-numpy which is already solved 
in python-numpy 1.6.5

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933056

Cheers



De : debian-science-maintainers 
[debian-science-maintainers-bounces+picca=synchrotron-soleil...@alioth-lists.debian.net]
 de la part de Gianfranco Costamagna [locutusofb...@debian.org]
Envoyé : jeudi 12 septembre 2019 21:37
À : sub...@bugs.debian.org
Objet : Bug#940130: pymca: testsuite failure (segfault)

Source: pymca
Version: 5.5.1+dfsg-1
Severity: serious

Hello, looks like the package autopkgtest is failing...
testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Segmentation fault

https://ci.debian.net/packages/p/pymca/testing/amd64

can you please have a look?

--
debian-science-maintainers mailing list
debian-science-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#940131: srslte FTBFS with libbladerf2 and uhd 3.14

[peter green]

Package: srslte
Version: 3.14.1.0-2
Severity: serious

srslte FTBFS in bullseye and sid due to the new versions of bladerf and uhd 
changing some data types. I patched the errors and was able to get a successful 
build in raspbian bullseye which I uploaded to the raspbian archive, I have not 
tested it beyond that.

A debdiff can be found at 
http://debdiffs.raspbian.org/main/s/srslte/srslte_18.06.1-8+rpi1.debdiff no 
intent to NMU in Debian.

P.S. while watching the build scroll by I noticed warnings about incorrect 
printf format specifiers which are likely to cause crashes on some platforms if 
those printf statements are ever executed.

Processed: severity of 939866 is serious

[Debian Bug Tracking System]

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

> severity 939866 serious
Bug #939866 [mariadb-server-10.1] mariadb-server-10.1: replication hangs in 
state "Slave_IO_Running: Preparing" after upgrade from 10.1.38 to 10.1.41
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 939819, affects 939819

[Debian Bug Tracking System]

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

> tags 939819 + upstream
Bug #939819 [src:mariadb-10.3] mariadb-10.3: Replication hangs with "preparing" 
and never starts
Added tag(s) upstream.
> affects 939819 + release.debian.org
Bug #939819 [src:mariadb-10.3] mariadb-10.3: Replication hangs with "preparing" 
and never starts
Added indication that 939819 affects release.debian.org
> thanks
Stopping processing here.

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

Bug#940130: pymca: testsuite failure (segfault)

[Gianfranco Costamagna]

Source: pymca
Version: 5.5.1+dfsg-1
Severity: serious

Hello, looks like the package autopkgtest is failing...
testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Segmentation fault

https://ci.debian.net/packages/p/pymca/testing/amd64

can you please have a look?

Processed: [bts-link] source package src:mariadb-10.3

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:mariadb-10.3
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #939819 (http://bugs.debian.org/939819)
> # Bug title: mariadb-10.3: Replication hangs with "preparing" and never starts
> #  * https://jira.mariadb.org/browse/MDEV-20247
> #  * remote status changed: (?) -> Closed
> #  * remote resolution changed: (?) -> Fixed
> #  * closed upstream
> tags 939819 + fixed-upstream
Bug #939819 [src:mariadb-10.3] mariadb-10.3: Replication hangs with "preparing" 
and never starts
Added tag(s) fixed-upstream.
> usertags 939819 + status-Closed resolution-Fixed
There were no usertags set.
Usertags are now: status-Closed resolution-Fixed.
> thanks
Stopping processing here.

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

Processed: Re: hdup: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #925711 [src:hdup] hdup: ftbfs with GCC-9
Added tag(s) pending and patch.

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

Bug#925711: hdup: ftbfs with GCC-9

[Gianfranco Costamagna]

control: tags -1 patch pending

On Thu, 5 Sep 2019 16:00:29 +0200 Gianfranco Costamagna 
 wrote:
> Hello, please try again, looks like you need a quilt format if you want to 
> add a patch
> 
> attached an updated diff
> 
> G.

in deferred/2
diff -u hdup-2.0.14/debian/changelog hdup-2.0.14/debian/changelog
--- hdup-2.0.14/debian/changelog
+++ hdup-2.0.14/debian/changelog
@@ -1,3 +1,11 @@
+hdup (2.0.14-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply the patch on source-tree since this is not a quilt format package
+(Closes: #641645)
+
+ -- Gianfranco Costamagna   Thu, 12 Sep 2019 
21:16:58 +0200
+
 hdup (2.0.14-5) unstable; urgency=medium
 
   * New patch: gcc-4.6 to fix for GCC 4.6.
reverted:
--- hdup-2.0.14/debian/patches/gcc-4.6
+++ hdup-2.0.14.orig/debian/patches/gcc-4.6
@@ -1,11 +0,0 @@
 hdup-2.0.14.orig/src/Makefile.in
-+++ hdup-2.0.14/src/Makefile.in
-@@ -28,7 +28,7 @@
- all:  hdup Makefile.in
- 
- hdup: ${OBJ} ${HDR} Makefile.in
--  ${GCC} ${GLIB_LIBS} ${OBJ} -o hdup
-+  ${GCC} ${OBJ} ${GLIB_LIBS} -o hdup
- # ${STRIP}
- 
- hdup.h:   hdup.h.in Makefile.in
reverted:
--- hdup-2.0.14/debian/patches/series
+++ hdup-2.0.14.orig/debian/patches/series
@@ -1 +0,0 @@
-gcc-4.6
diff -u hdup-2.0.14/src/Makefile.in hdup-2.0.14/src/Makefile.in
--- hdup-2.0.14/src/Makefile.in
+++ hdup-2.0.14/src/Makefile.in
@@ -28,7 +28,7 @@
 all:   hdup Makefile.in
 
 hdup:  ${OBJ} ${HDR} Makefile.in
-   ${GCC} ${GLIB_LIBS} ${OBJ} -o hdup
+   ${GCC} ${OBJ} ${GLIB_LIBS} -o hdup
 #  ${STRIP}
 
 hdup.h:hdup.h.in Makefile.in

Bug#939620: marked as done (python3-zope.testrunner: missing Breaks+Replaces: python-zope.testrunner)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 18:49:45 +
with message-id 
and subject line Bug#939620: fixed in zope.testrunner 4.4.9-3
has caused the Debian Bug report #939620,
regarding python3-zope.testrunner: missing Breaks+Replaces: 
python-zope.testrunner
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.)


-- 
939620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zope.testrunner
Version: 4.4.9-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-zope.testrunner_4.4.9-2_all.deb ...
  Unpacking python3-zope.testrunner (4.4.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/zope-testrunner', which is also in package 
python-zope.testrunner 4.4.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb


cheers,

Andreas


python-zope.testrunner=4.4.9-1_python3-zope.testrunner=4.4.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zope.testrunner
Source-Version: 4.4.9-3

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated zope.testrunner 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 18:19:28 +
Source: zope.testrunner
Architecture: source
Version: 4.4.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Peter Michael Green 
Closes: 939620
Changes:
 zope.testrunner (4.4.9-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix error in breaks/replaces relationship, change python3-zope.testrunner 
to
 python-zope.testrunner (Closes: 939620)
Checksums-Sha1:
 515931750dae0fa134dd8ae5bf4bfc45f06f7c18 1897 zope.testrunner_4.4.9-3.dsc
 9643be4586f6f95564a56bf82ad80f61351d9be8 6088 
zope.testrunner_4.4.9-3.debian.tar.xz
 4ef6192c5b24dd8380041cfe78a6ea39d2bd8d93 5899 
zope.testrunner_4.4.9-3_source.buildinfo
Checksums-Sha256:
 e5c4e28a63b4f69c844432230195965448a363baeb5a47dce94889ba166fe22e 1897 
zope.testrunner_4.4.9-3.dsc
 3f7b00f2f9a8e78bff6294b895708d3aca5431e88c1d4a01dff04f7ad05a4b2d 6088 
zope.testrunner_4.4.9-3.debian.tar.xz
 651c8bfb79a8d32435923a7ac6efaac6c32e297e18f4348964e853d3f2ae0a3d 5899 
zope.testrunner_4.4.9-3_source.buildinfo
Files:
 dd80481d9dc258697376dd8e0693a9d8 1897 zope optional zope.testrunner_4.4.9-3.dsc
 a24ff03b96fb6891c193d0dbfd238a36 6088 zope optional 
zope.testrunner_4.4.9-3.debian.tar.xz
 b2e1a43a0a794bb51b9fbe76e44828cf 5899 zope optional 
zope.testrunner_4.4.9-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl16jUUUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xss1Q/+JN2emKNbpwBsOdt7Gdb0dAPRGwmF
SkB7xk6scnSi5xdHk04FDi+DsYMi6X0t1IXXC1TnVY1EOYfGUiUMiKwUeCnovCLV
7CR975MdERfBDnVDGP5NfAkOsQGXGJm1MXCB3XhMpEvpMJIWEPYQlcpReP7kfQNR
8b+dgpIl67/VC3mvgv8T6LQoPdSc6VwcQz0wCf3AhJMDfIeax60AQALdZlcnYZAi
UHLZXMuLpW5JV58QDMt2bZrmN8yDqk7z2bnvH4GEplU3OC0bUOyfPlR7gj6y3h3N
bIqzf8fePvVRzsAvlxXThQ7GbFQSpiZnH4r50/nvmn2woBKOzSho7WFDM4yNd3RY
X6l0r1Ps9YPN5BF20Hi4/tcXi2VJ7n3clQg442CEmbZVvPhKSR0GkbbOvzaf0UcU
0WluaMVVuwBYdoRnw2atrXN1bWHQiaUrGsS3b/Usa0tnK//Cka5qAKST2ICvILSO
QbS5QBYREkZJHzTl1bBHQkNOhC19DJJQBoO8/fM1aRF8w7czol0n6kZ2ILxD7nW7
+vLwthNWOQk+tAK6oJ01s3wT+Im4HarA9IrrqvF4JV2yHQAe9uLXtUxv0kqg0fMd

Bug#932865: python-qrtools: not installable: depends on python2 version of zbar

[Ying-Chun Liu (PaulLiu)]

Hi all,


Unfortunately, I'm still using this app. Or not me cause I can use
command line,

but I must keep this app running otherwise I'll be in trouble.

So I propose a merge request to the upstream that ports this app to python3.


https://code.launchpad.net/~paulliu/qr-tools/python3/+merge/372711

Will do NMU for a patch maintained inside Debian if the upstream is
really dead and don't want to accept or discuss my patch.

If the upstream accepts my patch then we can upgrade to latest upstream.


Yours,
Paul




signature.asc
Description: OpenPGP digital signature

Bug#938919: zope.testrunner: Python2 removal in sid/bullseye

[Matthias Klose]

On 12.09.19 19:34, peter green wrote:

severity 938919 serious
thanks

python-zope.testrunner in testing depends on python-zope.exceptions which has 
already been dropped by the zope.exceptions source package.


This has been addressed in unstable by dropping the python-zope.testrunner 
binary package, however that fix cannot currently migrate to testing because 
/usr/bin/zope-testrunner was moved to the python3-zope.testrunner binary package 
but no breaks/replaces relationships were put in place.


feel free to fix. the package is orphaned.

Bug#939620: zope.testrunner: Python2 removal in sid/bullseye

[peter green]

severity 938919 serious
thanks

python-zope.testrunner in testing depends on python-zope.exceptions which has 
already been dropped by the zope.exceptions source package.

This has been addressed in unstable by dropping the python-zope.testrunner 
binary package, however that fix cannot currently migrate to testing because 
/usr/bin/zope-testrunner was moved to the python3-zope.testrunner binary 
package but no breaks/replaces relationships were put in place.

Processed: zope.testrunner: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> severity 938919 serious
Bug #938919 {Done: Matthias Klose } [src:zope.testrunner] 
zope.testrunner: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: ghostscript makes c2esp autopkgtest timeout

[Debian Bug Tracking System]

Processing control commands:

> found -1 ghostscript/9.28~~rc2~dfsg-1
Bug #940127 [src:ghostscript, src:c2esp] ghostscript makes c2esp autopkgtest 
timeout
Marked as found in versions ghostscript/9.28~~rc2~dfsg-1.
> found -1 c2esp/27-4
Bug #940127 [src:ghostscript, src:c2esp] ghostscript makes c2esp autopkgtest 
timeout
Marked as found in versions c2esp/27-4.

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

Bug#940127: ghostscript makes c2esp autopkgtest timeout

[Paul Gevers]

Source: ghostscript, c2esp
Control: found -1 ghostscript/9.28~~rc2~dfsg-1
Control: found -1 c2esp/27-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update timeout

Dear maintainers,

With a recent upload of ghostscript the autopkgtest of c2esp timeouts
[1] in testing when that autopkgtest is run with the binary packages of
ghostscript from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ghostscriptfrom testing9.28~~rc2~dfsg-1
c2esp  from testing27-4
all others from testingfrom testing

The autopkgtest of c2esp also times out in unstable since the upload of
ghostscript.

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?

Paul

[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/c/c2esp/2944626/log.gz



signature.asc
Description: OpenPGP digital signature

Processed: re: pyramid-jinja2: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> severity 937518 serious
Bug #937518 [src:pyramid-jinja2] pyramid-jinja2: Python2 removal in sid/bullseye
Bug #935380 [src:pyramid-jinja2] Please drop the Python 2 subpackage
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

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

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

Processed: re: python-aws-xray-sdk: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> severity 937593 serious
Bug #937593 [src:python-aws-xray-sdk] python-aws-xray-sdk: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: re: python-repoze.tm2: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

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

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

Processed: re: Please replace with a python3 module or remove the package

[Debian Bug Tracking System]

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

> severity 782951 serious
Bug #782951 [python-pyramid-tm] Please replace with a python3 module or remove 
the package
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: re: gnumed-client: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> severity 936630 serious
Bug #936630 [src:gnumed-client] gnumed-client: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#940085: marked as done (plplot breaks gnudatalanguage autopkgtest: PLplot installation lacks the requested driver: xwin)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 17:48:19 +0200
with message-id 
and subject line Re: plplot breaks gnudatalanguage autopkgtest: PLplot 
installation lacks the requested driver: xwin
has caused the Debian Bug report #940085,
regarding plplot breaks gnudatalanguage autopkgtest: PLplot installation lacks 
the requested driver: xwin
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.)


-- 
940085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plplot, gnudatalanguage
Control: found -1 plplot/5.15.0+dfsg-3
Control: found -1 gnudatalanguage/0.9.9-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 plplot the autopkgtest of gnudatalanguage fails
in testing when that autopkgtest is run with the binary packages of
plplot from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
plplot from testing5.15.0+dfsg-3
gnudatalanguagefrom testing0.9.9-10
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 plplot 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=plplot

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnudatalanguage/2942807/log.gz

% TEST_BUG_2974380: PLplot installation lacks the requested driver: xwin
% Execution halted at: TEST_BUG_2974380 3
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_bug_2974380.pro
%  $MAIN$

[...]

% TEST_BUG_3275334: PLplot installation lacks the requested driver: xwin
% Execution halted at: TEST_BUG_327533449
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_bug_3275334.pro
%  $MAIN$

[...]

% TEST_CONGRID_ON_IMAGES: PLplot installation lacks the requested
driver: xwin
% Execution halted at: TEST_CONGRID_ON_IMAGES   150
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_congrid.pro
%  TEST_CONGRID   150
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_congrid.pro
%  $MAIN$
% WARNING: your version of the GraphicsMagick library will truncate
images to 16 bits per pixel
% Compiled module: TEST_CONSTANTS.
% WARNING: your version of the GraphicsMagick library will truncate
images to 16 bits per pixel
% Compiled module: TEST_CONTAINER.
gdl:
/build/gnudatalanguage-jfDpIi/gnudatalanguage-0.9.9/src/envt.cpp:1368:
void EnvBaseT::SetNextParUnchecked(BaseGDL*): Assertion
`static_cast(parIx - pro->key.size()) < pro->nPar' failed.
Magick: abort due to signal 6 (SIGABRT) "Abort"...
Aborted

[... ] but there is more

=
14 Error(s) found
=
test_bug_2974380
test_bug_3275334
test_congrid
test_contour
test_device
test_execute
test_extra_keywords
test_moment
test_plot_oo
test_plot_usersym
test_pmulti_basic
test_qhull
test_tv
test_window_background



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi Paul,

this is a transitional problem only -- for some reason,
plplot-driver-xwin was taken in the old version, while libplplot17 was
taken in the new version. The new version of libplplot17 could not find
the old version of xwin, which was however required to run the gdl tests.

This part should work now; however in parallel GDL was binNMUed and
rebuilt with gcc-9 (instead of gcc-8) and then shows a different problem.

Cheers

Ole--- End Message ---

Bug#939974: osmo-trx FTBFS: undefined reference to symbol '_ZN5boost6system16generic_categoryEv'

[Pau Espin Pedrol]

Hi,

sorry for late response regarding this topic in here.

Related osmocom ticket can be found here: https://osmocom.org/issues/4182

As I mentioned in last comments of that ticket, I think the build 
failure in testing and unstable (building fine in stable) comes from the 
fact that this patch was applied in debian's UHD package: 
https://sources.debian.org/patches/uhd/3.14.1.0-2/fix-pkg-config


I'm not sure why this patch was applied (I don't see a similar patch 
applied in UHD master in upstream). Could it be that libboost-system 
doesn't exist on some system architectures but it was unconditionally 
dropped with that patch?



--
- Pau Espin Pedrol  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte

Bug#939561: soapybladerf ftbfs in unstable

[peter green]

tags 939561 +fixed-upstream
tags 939561 +patch
thanks

Some googling revealed that upstream had fixed this issue 
https://github.com/pothosware/SoapyBladeRF/pull/19 . I was able to take the 
upstream pull request, turn it into a patch series and apply it to the Debian 
package.

I have uploaded my fix to raspbian, a debdiff can be found at 
http://debdiffs.raspbian.org/main/s/soapybladerf/soapybladerf_0.3.5-1+rpi1.debdiff
 , no intent to NMU in Debian.

Processed: spyder: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> Severity 938550 serious
Bug #938550 [src:spyder] spyder: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.

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

Processed: re: soapybladerf ftbfs in unstable

[Debian Bug Tracking System]

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

> tags 939561 +fixed-upstream
Bug #939561 [src:soapybladerf] soapybladerf ftbfs in unstable
Added tag(s) fixed-upstream.
> tags 939561 +patch
Bug #939561 [src:soapybladerf] soapybladerf ftbfs in unstable
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: spyder-kernels: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> Severity 938551 serious
Bug #938551 [src:spyder-kernels] spyder-kernels: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.

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

Processed: skimage: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> Severity 938494 serious
Bug #938494 [src:skimage] skimage: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.

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

Bug#938962: user-mode-linux needs update for new linux

[Anton Ivanov]

On 12/09/2019 13:14, Ritesh Raj Sarraf wrote:

Hi,

I am not sure if this has been reported upstream but with libpcap 1.9,
user mode linux fails to build. The build failure happens with both,
5.2 and 4.19 LTS kernels.

A much detailed report is available at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938962

libpcap 1.9 introduces `pcap_open` which is also declared in linux
headers in arch/um/drivers/pcap_user.c





I think the best way forward here is to kill the old libpcap driver 
altogether.


You get the same functionality from vector raw including the ability to 
load a bpf filter.


The only thing that needs is a wrapper to compile the filter before 
handing it to UML.


A side effect is that it is ~ 10+ time faster - in the multigigabit range.

Alternatively, I can wrap it so it looks like pcap to any existing 
scripts and is actually vector underneath, but that will lose some of 
the tunables, like offloads, vector depth, etc.




Thanks,
Ritesh

On Sat, 2019-09-07 at 17:18 +0200, Romain Francoise wrote:

Hi,

On Tue, Sep 3, 2019 at 3:21 PM Ritesh Raj Sarraf 
wrote:
[...]

In file included from /usr/include/pcap.h:43,
  from arch/um/drivers/pcap_user.c:7:
/usr/include/pcap/pcap.h:835:18: note: previous declaration of
‘pcap_open’ was here
  PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int
flags,
   ^
make[2]: *** [scripts/Makefile.build:309:
arch/um/drivers/pcap_user.o] Error 1


libpcap 1.9 includes support for remote capture, which was originally
a part of WinPcap extensions. The `pcap_open()' symbol is part of
that
API and that's why it's defined in the header file even though remote
support is not enabled in Debian. I suggest you rename the function
defined in your program so that it doesn't conflict with libpcap.

___
linux-um mailing list
linux...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


--
Anton R. Ivanov
https://www.kot-begemot.co.uk/

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Lisandro Damián Nicanor Pérez Meyer]

On 19/09/07 08:58, Paul Gevers wrote:
> Source: clazy
> Version: 1.5-1
> Severity: serious
> Tags: ftbfs
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Dear maintainer,
> 
> During a binNMU of clazy during the llvm-defaults transition, you package 
> FTBFS
> on armel. Can you please check and fix the situation?

This seems more a bug in the toolchain than anything else. I'm currently trying 
it on a porterbox. 

Bug#940026: marked as done (gvfs: unbuildable in unstable: requires experimental gsettings-desktop-schemas)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 14:57:18 +
with message-id 
and subject line Bug#940026: fixed in gvfs 1.42.0+really1.42.0-1
has caused the Debian Bug report #940026,
regarding gvfs: unbuildable in unstable: requires experimental 
gsettings-desktop-schemas
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.)


-- 
940026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gvfs
Version: 1.42.0-1
Severity: grave
Justification: renders package unusable

> gvfs unsatisfiable Build-Depends(-Arch) on amd64: 
> gsettings-desktop-schemas-dev (>= 3.33.0)

We cannot upload the new gsettings-desktop-schemas-dev to unstable yet,
because it Breaks the current version of mutter, which cannot go to
unstable until we are ready for the libmutter and evolution-data-server
ABI transitions to take place.

This probably needs to be reverted via a 1.42.0+really1.38.1 or
1.42.0+really1.40.1 upload to unstable, and 1.42.0+really1.42.0 to
experimental.

Unfortunately this has also knocked gvfs 1.41.x out of experimental,
because that happens automatically whenever the source version in unstable
is higher.

smcv
--- End Message ---
--- Begin Message ---
Source: gvfs
Source-Version: 1.42.0+really1.42.0-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gvfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 12:05:16 +0100
Source: gvfs
Architecture: source
Version: 1.42.0+really1.42.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 940026
Changes:
 gvfs (1.42.0+really1.42.0-1) experimental; urgency=medium
 .
   * Team upload
   * Re-upload 1.42.x to experimental, with a higher version number than
 the revert to 1.38.x in unstable. It isn't ready for unstable just yet.
 (Closes: #940026)
Checksums-Sha1:
 44bdc8f6f46b07033c79cd0457bbb3ee708051a5 3487 gvfs_1.42.0+really1.42.0-1.dsc
 231acfdf17f466c0bc70aea3fcf610d1a7280e25 1204864 
gvfs_1.42.0+really1.42.0.orig.tar.xz
 6cc5747b9a15429d5370cc1bd59dd1ac1307 23848 
gvfs_1.42.0+really1.42.0-1.debian.tar.xz
 974802ccc0adf233b8b01b606ef626472bb3f604 18533 
gvfs_1.42.0+really1.42.0-1_source.buildinfo
Checksums-Sha256:
 e3ef4333ff05ebf176659398545180cb60280f0fbf2829f99ab211a9e076da4b 3487 
gvfs_1.42.0+really1.42.0-1.dsc
 d0958d9ceefb54bb8ddda74ef51e10fe03dff93f74634784bd309ea434066cf1 1204864 
gvfs_1.42.0+really1.42.0.orig.tar.xz
 d3b6fda6a0f1392e507e8abb8145ad7dcba1ab58432825cad0f2ffe26b3daf76 23848 
gvfs_1.42.0+really1.42.0-1.debian.tar.xz
 1bf23010b35b4061ecbff9d44a09ebe1d384bb344026a29ceb3003f07e173e74 18533 
gvfs_1.42.0+really1.42.0-1_source.buildinfo
Files:
 faae547b0a50c705d22ec590be552cf5 3487 gnome optional 
gvfs_1.42.0+really1.42.0-1.dsc
 61377a86babe41cdf6c5dfd1fef53b21 1204864 gnome optional 
gvfs_1.42.0+really1.42.0.orig.tar.xz
 b6afc6bf937c450037e21f238ab09e8e 23848 gnome optional 
gvfs_1.42.0+really1.42.0-1.debian.tar.xz
 9bdd4a7466a90484d90ba4e9de93cf07 18533 gnome optional 
gvfs_1.42.0+really1.42.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl16R38ACgkQ4FrhR4+B
TE91FRAAmjYTEPv3zTV76b8/zw9BDah58S6+DQoi7kMMT6w71NM7shDy43CB34AI
1bE+Q94o4Qg5ovzk4pEcLiemk5QuVQk4lHWB3OYND2jve8a/OF7pMmTQoeG+QcMg
muntFBjEaw9Uyxrqs1jX/dW8aqb25YDRLi3It2LAlMB8fTz0nNxU3U6QUm0D96nf
y5F31O//VDuWHQCg99zTHazmoD7hr8aenBhq6Q95svrzVx0zWhZHYuF0MDzqAwFM
gICLBx6JAESD4dSfC4Jv7BAt3Yck0RKOs9cUWimzB658I5ref07zK2XdbfjnGZtn
W/nIPvzcoHxr/l/0EbNzhgs2O0dzY5GPlTelPHHnSzW+BNj06iER7yOiRZ36gAD5
FJNeXafYY4k+oL/9zg6HMqD307YoAveCnGDBLNZFqARkNUmpsLnz+FbaDSo5YddH
hwuFNvIBGysIA8dZ4Ntvx4Q1VCM7Wfk6xx6mkWIT8x/ZYxwYZGLBMkebXyztwa+Z
U3RYJOr7RuI2V7wdSGFyHeTICaLk7O7QZStC4bJzUZo2fm7WF+fY12JtzZLb6B54
AiKN7bicK82diFWqa4JJvPZlhh2TP95YyuZQ51Pzwiut6beH5eDCv3MwOdSrIx6h
6ypcjGnX5WVt26gqvnW+nA/QEdneE+VbijbUd5sAmSvAGd2oiT8=
=uWD0
-END PGP SIGNATURE 

Bug#940119: sdaps build-depends on package that is cruft in unstable and gone in testing.

[peter green]

Package: sdaps
Version: 1.9.7-0.1
Severity: serious

sdaps build-depends on texlive-generic-recommended which is no longer built by 
texlive-base. The old texlive-generic-recommended is still present in unstable 
as a cruft package, but is completely gone from testing.

Please update your build-dependency to texlive-plain-generic.

Bug#940107: python3-webpy: Does not work with static content

[Martin]

Control: severity -1 normal

Robin, thanks for your bug report!

I'm using web.py myself, behind an nginx frontend.  In my case,
static content is served by nginx, which is probably the most
common case. For special cases, I use custom code for serving
static files. Therefore, I never realized, that there is a bug
in web.py regarding static files. I suggest, to look into the
possibility of using one of the two approaches for your web
application.

Processed: Re: Bug#940107: python3-webpy: Does not work with static content

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #940107 [python3-webpy] python3-webpy: Does not work with static content
Severity set to 'normal' from 'grave'

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

Processed: Re: blockdiag: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936219 [src:blockdiag] blockdiag: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#893301: marked as done (logisim FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 13:48:38 +
with message-id 
and subject line Bug#893301: fixed in logisim 2.7.1~dfsg-2
has caused the Debian Bug report #893301,
regarding logisim FTBFS with openjdk-9
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.)


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

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

...
   debian/rules override_jh_build
make[1]: Entering directory '/build/1st/logisim-2.7.1~dfsg'
jh_build
find src/com -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jhall.jar:/usr/share/java/ColorPicker.jar:/usr/share/java/FontChooser.jar:debian/_jh_build.logisim
 -d debian/_jh_build.logisim -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 1.7
src/com/cburch/logisim/gui/main/SimulationTreeNode.java:18: error: children() 
in SimulationTreeNode cannot implement children() in TreeNode
public abstract Enumeration children();
   ^
  return type Enumeration is not compatible with Enumeration
src/com/cburch/logisim/gui/log/ComponentSelector.java:244: error: 
ComponentSelector.OptionNode is not abstract and does not override abstract 
method children() in TreeNode
private class OptionNode implements TreeNode {
^
src/com/cburch/logisim/gui/log/ComponentSelector.java:282: error: children() in 
ComponentSelector.OptionNode cannot implement children() in TreeNode
public Enumeration children() {
  ^
  return type Enumeration is not compatible with Enumeration
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
3 errors
1 warning
make[1]: *** [debian/rules:10: override_jh_build] Error 123
--- End Message ---
--- Begin Message ---
Source: logisim
Source-Version: 2.7.1~dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated logisim 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, 12 Sep 2019 14:50:52 +0200
Source: logisim
Architecture: source
Version: 2.7.1~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Cheng 
Changed-By: Emmanuel Bourg 
Closes: 893301
Changes:
 logisim (2.7.1~dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893301)
   * Moved the packaging repository to Salsa
   * Standards-Version updated to 4.4.0
   * Switch to debhelper level 11
Checksums-Sha1:
 83e6616340ac5eafa966963dbe250c5066daf8d3 1986 logisim_2.7.1~dfsg-2.dsc
 cdef74c0f3cc34e1b96251f045b6dc3bf1961962 6488 
logisim_2.7.1~dfsg-2.debian.tar.xz
 52bb28c01b5cda93f013b6da4016602f09f2da80 8660 
logisim_2.7.1~dfsg-2_source.buildinfo
Checksums-Sha256:
 8d5e7df0a3bbd2c280b98fd9f7df096ca5f00d2afa2a244a0d6e72a543c161df 1986 
logisim_2.7.1~dfsg-2.dsc
 8c4294104ff1afdb1ca0cade0c3c8711e61ae8bae63220af7475bc19457b7278 6488 
logisim_2.7.1~dfsg-2.debian.tar.xz
 03afcd9abe3eda8ef45fa6019863eea0afc8af8f5459bffd9d6fa299bd51ddf9 8660 
logisim_2.7.1~dfsg-2_source.buildinfo
Files:
 bdff7869909bd438ff1a9ba0b7e68931 1986 java optional logisim_2.7.1~dfsg-2.dsc
 5b20cf4ad4e00a13a86f474cf02242d2 6488 java optional 
logisim_2.7.1~dfsg-2.debian.tar.xz
 cfe2256261805224832005af25a2ace8 8660 java optional 
logisim_2.7.1~dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl16P6gSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsVIkQAJjMn4YtgRPkqj+F6F9w8MqSPxU6hIYl
4zbyE0uWGuoPcg3IBcLVlAT4UwL/vGvmXqlFbvFKhhyDeuIWa/hhlsLafAMPt7Rc

Bug#940026: marked as done (gvfs: unbuildable in unstable: requires experimental gsettings-desktop-schemas)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 13:47:47 +
with message-id 
and subject line Bug#940026: fixed in gvfs 1.42.0+really1.38.1-1
has caused the Debian Bug report #940026,
regarding gvfs: unbuildable in unstable: requires experimental 
gsettings-desktop-schemas
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.)


-- 
940026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gvfs
Version: 1.42.0-1
Severity: grave
Justification: renders package unusable

> gvfs unsatisfiable Build-Depends(-Arch) on amd64: 
> gsettings-desktop-schemas-dev (>= 3.33.0)

We cannot upload the new gsettings-desktop-schemas-dev to unstable yet,
because it Breaks the current version of mutter, which cannot go to
unstable until we are ready for the libmutter and evolution-data-server
ABI transitions to take place.

This probably needs to be reverted via a 1.42.0+really1.38.1 or
1.42.0+really1.40.1 upload to unstable, and 1.42.0+really1.42.0 to
experimental.

Unfortunately this has also knocked gvfs 1.41.x out of experimental,
because that happens automatically whenever the source version in unstable
is higher.

smcv
--- End Message ---
--- Begin Message ---
Source: gvfs
Source-Version: 1.42.0+really1.38.1-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gvfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 11:56:17 +0100
Source: gvfs
Architecture: source
Version: 1.42.0+really1.38.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 940026
Changes:
 gvfs (1.42.0+really1.38.1-1) unstable; urgency=medium
 .
   * Team upload
   * Re-release 1.38.1-5 to unstable to overwrite premature upload of
 1.42.x. Versions 1.42.x depend on a gsettings-desktop-schemas version
 from experimental that cannot go to unstable until the mutter and
 evolution-data-server transitions for GNOME 3.34 are ready.
 (Closes: #940026)
 - d/gbp.conf: Set packaging branch to debian/unstable
Checksums-Sha1:
 b2c6de51d99a4419134f506bd4c62ef34d90a66f 3483 gvfs_1.42.0+really1.38.1-1.dsc
 e1f340a1500e0c56491e3d2146d157c3ca46b521 1203224 
gvfs_1.42.0+really1.38.1.orig.tar.xz
 b3ff0f0fd794abd8b9f7cf5dad8b2edb2e04cf33 63384 
gvfs_1.42.0+really1.38.1-1.debian.tar.xz
 965716200ec4e5402a283302e6996d4d94b857c3 18978 
gvfs_1.42.0+really1.38.1-1_source.buildinfo
Checksums-Sha256:
 d7bf2d9d24aa0907695efb9f4e122bad0a84839f03b8cf3730b9400628b0514b 3483 
gvfs_1.42.0+really1.38.1-1.dsc
 ed136a842c996d25c835da405c4775c77106b46470e75bdc242bdd59ec0d61a0 1203224 
gvfs_1.42.0+really1.38.1.orig.tar.xz
 1fd9bf0a6cd844c65e22611a3b54405ba86ec535038cf09fbcbfc9a4ca02f7eb 63384 
gvfs_1.42.0+really1.38.1-1.debian.tar.xz
 241c4bc637664936e3a28d40fcef2a78ab607fbfcd9ce6f68a9f97f80717c6dd 18978 
gvfs_1.42.0+really1.38.1-1_source.buildinfo
Files:
 a7f3607522b1b581d09c9307a32de44b 3483 gnome optional 
gvfs_1.42.0+really1.38.1-1.dsc
 510afd56f11579023d9a331f72fe5a8b 1203224 gnome optional 
gvfs_1.42.0+really1.38.1.orig.tar.xz
 921a1cc3f638319b72520265034bdb3b 63384 gnome optional 
gvfs_1.42.0+really1.38.1-1.debian.tar.xz
 d22c9c04a54080135a9fd7367f85ba6b 18978 gnome optional 
gvfs_1.42.0+really1.38.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl16QwsACgkQ4FrhR4+B
TE/HAhAAkOW9sbxnDoonJnQhmWz8Z3LEqsg2ZLNvEgSpUUFzlqQQO9Cx+xB2/rGb
ZC7ogpAcJAbV0aDNYo54QoLEp+JCdyERShcwqCn3yMBvg5iTHrucouKaIvYtbUjN
OV1gvKQrp5gW3cpw2OLtUkHB7JNsszJM4UeRo3aAjYT6BJoZyxYpvbOpCsDry+bB
bxrF0y4kiq5QgsqJFEPksp4jPlG29P+N6ippTVrulHOMHADy2OSs61zhURNCZuUW
pvCRyWY2pUdN9ic6qIrgca63nv1ARAD+w79CMhcy0Tt6CBuajPysEoNfKAcoyK3j
wFoRWxyZnPwi8Udw8vGfvdFZoi0s3eSEHYDbQPzTg0uAtxNUNdFWe9xQvCFxSM1c
8zs1O8ELGjTry4qN9BBXJrIivDWhmhgt1l7V5EOqtHaUNDae7ghZaGCiSoGbaw1R
IQCCvzfxAWBo7CCChLLyVpRSeG8SxjIQk9dx6Fuw2TPrOZ1g6jshV3s1+84ElR2Y

Bug#934841: marked as done (sshpubkeys: (build-)depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 13:50:40 +
with message-id 
and subject line Bug#934841: fixed in sshpubkeys 3.1.0-2
has caused the Debian Bug report #934841,
regarding sshpubkeys: (build-)depends on cruft package.
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.)


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

Package: sshpubkeys
Severity: serious
Version: 3.1.0-1
Tags: bullseye, sid

The python-sshpubkeys package depends on and the sshpubkeys source package 
build-depends on the python-ecdsa binary package which is no longer built by 
the corresponding source package.

It's probablly time to drop python 2 support from your Package.
--- End Message ---
--- Begin Message ---
Source: sshpubkeys
Source-Version: 3.1.0-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated sshpubkeys 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, 12 Sep 2019 14:20:37 +0200
Source: sshpubkeys
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Ondřej Nový 
Closes: 934841 938563
Changes:
 sshpubkeys (3.1.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Use debhelper-compat instead of debian/compat.
   * Drop Python 2 support (Closes: #934841, #938563).
Checksums-Sha1:
 b44121200e44fa86bad3d07f4f11f43d3d7daace 2095 sshpubkeys_3.1.0-2.dsc
 1f44ebe173fc8b9dd0ad2ca79d931660fd683d3d 2428 sshpubkeys_3.1.0-2.debian.tar.xz
 493905c7f3196843df703a41edf4f77d4dce3c45 6143 
sshpubkeys_3.1.0-2_amd64.buildinfo
Checksums-Sha256:
 507520728acaeb8f1beb0619578bfbcb07f9bb8d0e88d8cd9ccf315e49684d97 2095 
sshpubkeys_3.1.0-2.dsc
 7e3dad7652fb1d850321c2aa715078e072b23138616546bb1dfdbb85d4639797 2428 
sshpubkeys_3.1.0-2.debian.tar.xz
 b96165a00d23a8d40c18cc41fc798380ad432fd96cd99fee13b9b8ca4b7f4768 6143 
sshpubkeys_3.1.0-2_amd64.buildinfo
Files:
 ed21b839c6ac65f3473695c7888ab52e 2095 python optional sshpubkeys_3.1.0-2.dsc
 9c04b9f6bfbb55480b301fccec917754 2428 python optional 
sshpubkeys_3.1.0-2.debian.tar.xz
 5599e9594a6467901980c47fa57cc868 6143 python optional 
sshpubkeys_3.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl16OHUACgkQNXMSVZ0e
Bkuj2g//Xu4Kxb//Eh1/Qmja1kVCLjKV+e/69wk2+sz9qKaQ9BLdai/9VQxkPYMX
BB0yOvhJKV6IOFmWQr7odny9LaDGYYRe+zeLoqn4vfJ03uTtIVT1g9DkzLug1vc5
Lll+1HVEhSfLKqJ8DwzHExqO+BT7fduL1F6Vm1jhkmqPxDPuaJ/lYBB0nZg/8ilV
Do8N0og4aCtVsH5GzNh/DjHrn6pau/mkOb5X/LLWpgtXCTw2mBgGS8Z3A1+Q/Lnr
YsBnQqSaAjNMx0HeDWM2++Rrin/tyLtETmVJSYSXeEumACCWnWe8Pc4BsdOCXAV0
eFYxxaMbM/TnYgwi8u9az7//DqZ4oqNEhmSIT529UXZSdjUbysLiZubSsEjRD/u7
mrEAAqviHJaLxJWPsRPxpM55wSDjvEYUg/q33GyPTZaQUIdVI5/gqKiMiAmN92yU
3faBLjonU6k7uguRv1U1nneZsSFAVH8QrHx3jaSqZEOG4uQBvsbxaMnxulurSEg8
xnWH/nXHgvZQ5R9+nID7wRjmHwnoIeHc8qdH09Y2SOG+vOS11mcmcEsQrsUCrZ2m
AQfb45RwzHFkZTrtHtL3TFx7wZTUp4bba+zM9clSlVxMTptRdwPz+2+CTfxQsTKD
9+LEOVpEvlF3lCrLyewYnljlAKM1dB8b0BaZZ55lvyor2X492fQ=
=CB0i
-END PGP SIGNATURE End Message ---

Bug#940108: nexus: FTBFS with GCC 9: dereferencing pointer to incomplete type 'mxml_node_t' error

[Emmanuel Bourg]

Source: nexus
Version: 4.3.2-svn1921-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source

With the Java 9 fix applied (#893383) nexus still fails to build,
I assume due to more strict checks by GCC 9:

  /bin/bash ../libtool  --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I../include  -I../include -I/usr/include/hdf -DHDF4 
-I/usr/lib/x86_64-linux-gnu/hdf5/serial/include -DHDF5 
-DH5_NO_DEPRECATED_SYMBOLS -DH5Acreate_vers=2 -DH5Aiterate_vers=2 
-DH5Dcreate_vers=2 -DH5Dopen_vers=2 -DH5Eclear_vers=2 -DH5Eprint_vers=2 
-DH5Epush_vers=2 -DH5Eset_auto_vers=2 -DH5Eget_auto_vers=2 -DH5Ewalk_vers=2 
-DH5Gcreate_vers=2 -DH5Gopen_vers=2 -DH5Pget_filter_vers=2 
-DH5Pget_filter_by_id_vers=2 -DH5Pinsert_vers=2 -DH5Pregister_vers=2 
-DH5Rget_obj_type_vers=2 -DH5Tarray_create_vers=2 -DH5Tcommit_vers=2 
-DH5Tget_array_dims_vers=2 -DH5Topen_vers=2 -I/usr/include -DNXXML 
-DIN_NEXUS_LIBRARY=1 -Wdate-time -D_FORTIFY_SOURCE=2 -fno-common 
-DHAVE_NAPICONFIG_H -prefer-pic -g -O2 
-fdebug-prefix-map=/build/nexus-4.3.2-svn1921=. -fstack-protector-strong 
-Wformat -Werror=format-security -fno-strict-aliasing -MT nxxml.lo -MD -MP -MF 
.deps/nxxml.Tpo -c -o nxxml.lo nxxml.c
  libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../include 
-I../include -I/usr/include/hdf -DHDF4 
-I/usr/lib/x86_64-linux-gnu/hdf5/serial/include -DHDF5 
-DH5_NO_DEPRECATED_SYMBOLS -DH5Acreate_vers=2 -DH5Aiterate_vers=2 
-DH5Dcreate_vers=2 -DH5Dopen_vers=2 -DH5Eclear_vers=2 -DH5Eprint_vers=2 
-DH5Epush_vers=2 -DH5Eset_auto_vers=2 -DH5Eget_auto_vers=2 -DH5Ewalk_vers=2 
-DH5Gcreate_vers=2 -DH5Gopen_vers=2 -DH5Pget_filter_vers=2 
-DH5Pget_filter_by_id_vers=2 -DH5Pinsert_vers=2 -DH5Pregister_vers=2 
-DH5Rget_obj_type_vers=2 -DH5Tarray_create_vers=2 -DH5Tcommit_vers=2 
-DH5Tget_array_dims_vers=2 -DH5Topen_vers=2 -I/usr/include -DNXXML 
-DIN_NEXUS_LIBRARY=1 -Wdate-time -D_FORTIFY_SOURCE=2 -fno-common 
-DHAVE_NAPICONFIG_H -g -O2 -fdebug-prefix-map=/build/nexus-4.3.2-svn1921=. 
-fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing 
-MT nxxml.lo -MD -MP -MF .deps/nxxml.Tpo -c nxxml.c  -fPIC -DPIC -o 
.libs/nxxml.o
  nxxml.c: In function 'searchGroupLinks':
  nxxml.c:305:21: error: dereferencing pointer to incomplete type 'mxml_node_t' 
{aka 'struct _mxml_node_s'}
305 |   if(strcmp(test->value.element.name,nxclass) == 0){
| ^~
  nxxml.c: In function 'NXXmakedatatable64':
  nxxml.c:486:46: error: invalid application of 'sizeof' to incomplete type 
'mxml_node_t' {aka 'struct _mxml_node_s'}
486 |   newData = (mxml_node_t *)malloc(sizeof(mxml_node_t));
|  ^~~
  nxxml.c:491:31: error: invalid application of 'sizeof' to incomplete type 
'mxml_node_t' {aka 'struct _mxml_node_s'}
491 |   memset(newData,0,sizeof(mxml_node_t));
|   ^~~
  nxxml.c: In function 'NXXmakedata64':
  nxxml.c:555:44: error: invalid application of 'sizeof' to incomplete type 
'mxml_node_t' {aka 'struct _mxml_node_s'}
555 | newData = (mxml_node_t *)malloc(sizeof(mxml_node_t));
|^~~
  nxxml.c:560:29: error: invalid application of 'sizeof' to incomplete type 
'mxml_node_t' {aka 'struct _mxml_node_s'}
560 | memset(newData,0,sizeof(mxml_node_t));
| ^~~
  make[2]: *** [Makefile:606: nxxml.lo] Error 1

Processed: Bug#940026 marked as pending in gvfs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940026 [src:gvfs] gvfs: unbuildable in unstable: requires experimental 
gsettings-desktop-schemas
Ignoring request to alter tags of bug #940026 to the same tags previously set

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

Bug#940026: marked as pending in gvfs

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #940026 in gvfs 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/gnome-team/gvfs/commit/59d62f91e48dd8e168c0fdc7f4da87aa28fb1221


Re-upload 1.42.x to experimental

Give it a higher version number than the revert to 1.38.x in unstable. It
isn't ready for unstable just yet.

Closes: #940026


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/940026

Bug#940106: python3-webpy: Does not work with static content

[Robin Rawson-Tetley]

Package: python3-webpy
Version: 1:0.39+20181101-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

python3-webpy cannot serve static content due to upstream bugs that have since 
been fixed.

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages python3-webpy depends on:
ii  python3  3.7.3-1
ii  python3-cheroot  6.5.4+ds-2

Versions of packages python3-webpy recommends:
ii  python3-mysqldb   1.3.10-2
ii  python3-psycopg2  2.7.7-1

python3-webpy suggests no packages.

-- no debconf information

Bug#940105: linux: serious corruption issue with btrfs

[Christoph Anton Mitterer]

Source: linux
Version: 5.2.9-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss


Hi.

There were some reports over the last weeks from users on linux-btrfs which
suffered from catastrophic btrfs corruption.
The bug which is apparently a regression introduced in 5.2 has now been found[0]
an a patch is available[1].

Since it's unclear how long it will take to be part of a stable release and when
Debian will pick this up in unstable, please consider to cherry-pick the patch.

Thanks,
Chris.

[0] 
https://lore.kernel.org/linux-btrfs/9731b0e7-81f3-4ee5-6f89-b4fd8d981...@petaramesh.org/T/#m38d726b09e784f1ffbd26edf13f723f71045723e
[1] https://patchwork.kernel.org/patch/11141559/


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

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

Bug#940026: marked as pending in gvfs

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #940026 in gvfs 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/gnome-team/gvfs/commit/58ac46091c3c47de3bae9cf6b2349ed19aa68a70


Re-release 1.38.1-5 to unstable to overwrite premature upload of 1.42.x

Versions 1.42.x depend on a gsettings-desktop-schemas version
from experimental that cannot go to unstable until the mutter and
evolution-data-server transitions for GNOME 3.34 are ready.

Closes: #940026


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/940026

Processed: Bug#940026 marked as pending in gvfs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940026 [src:gvfs] gvfs: unbuildable in unstable: requires experimental 
gsettings-desktop-schemas
Added tag(s) pending.

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

Processed: limit source to ubuntu-dev-tools, tagging 940040

[Debian Bug Tracking System]

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

> limit source ubuntu-dev-tools
Limiting to bugs with field 'source' containing at least one of 
'ubuntu-dev-tools'
Limit currently set to 'source':'ubuntu-dev-tools'

> tags 940040 + pending
Bug #940040 [src:ubuntu-dev-tools] ubuntu-dev-tools: pbuilder-dist broken in 
unstable
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#939899: [ftpmas...@ftp-master.debian.org: apitrace_8.0+repack-1_amd64.changes REJECTED]

[Aurelien Jarno]

- Forwarded message from Debian FTP Masters 
 -

From: Debian FTP Masters 
To: amd64 Build Daemon 
Date: Thu, 12 Sep 2019 12:04:04 +
Subject: apitrace_8.0+repack-1_amd64.changes REJECTED


apitrace-tracers_8.0+repack-1_amd64.deb: Built-Using refers to non-existing 
source package snappy (= 1.1.7-1+b1)


Mapping sid to unstable.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.




- End forwarded message -

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

Processed: Bug#934841 marked as pending in sshpubkeys

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #934841 [sshpubkeys] sshpubkeys: (build-)depends on cruft package.
Added tag(s) pending.

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

Bug#934841: marked as pending in sshpubkeys

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #934841 in sshpubkeys 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/python-team/modules/sshpubkeys/commit/d50e2433d5a18c1e952fe5de8ee72e24dac97a99


Drop Python 2 support (Closes: #934841, #938563).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/934841

Bug#938962: user-mode-linux needs update for new linux

[Ritesh Raj Sarraf]

Hi,

I am not sure if this has been reported upstream but with libpcap 1.9,
user mode linux fails to build. The build failure happens with both,
5.2 and 4.19 LTS kernels.

A much detailed report is available at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938962

libpcap 1.9 introduces `pcap_open` which is also declared in linux
headers in arch/um/drivers/pcap_user.c


Thanks,
Ritesh

On Sat, 2019-09-07 at 17:18 +0200, Romain Francoise wrote:
> Hi,
> 
> On Tue, Sep 3, 2019 at 3:21 PM Ritesh Raj Sarraf 
> wrote:
> [...]
> > In file included from /usr/include/pcap.h:43,
> >  from arch/um/drivers/pcap_user.c:7:
> > /usr/include/pcap/pcap.h:835:18: note: previous declaration of
> > ‘pcap_open’ was here
> >  PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int
> > flags,
> >   ^
> > make[2]: *** [scripts/Makefile.build:309:
> > arch/um/drivers/pcap_user.o] Error 1
> 
> libpcap 1.9 includes support for remote capture, which was originally
> a part of WinPcap extensions. The `pcap_open()' symbol is part of
> that
> API and that's why it's defined in the header file even though remote
> support is not enabled in Debian. I suggest you rename the function
> defined in your program so that it doesn't conflict with libpcap.
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#940092: flowblade does start

[Gürkan Myczko]

Hi Theodore

What does which flowblade say for you?

Mine says /usr/bin/flowblade and starts pretty much normal.

Best,

Bug#940087: marked as done (FTBFS: test-prompt: Method "Prompt" with signature "s" on interface "org.freedesktop.Secret.Prompt" doesn't exist)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 10:49:13 +
with message-id 
and subject line Bug#940087: fixed in dbus-python 1.2.12-1
has caused the Debian Bug report #940087,
regarding FTBFS: test-prompt: Method "Prompt" with signature "s" on interface 
"org.freedesktop.Secret.Prompt" doesn't exist
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.)


-- 
940087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsecret
Version: 0.18.7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

During build-time tests, for example in

and
:

> **
> ERROR:libsecret/test-prompt.c:239:test_perform_vanish: assertion failed 
> (error == NULL): Method "Prompt" with signature "s" on interface 
> "org.freedesktop.Secret.Prompt" doesn't exist
>  (g-dbus-error-quark, 19)

I can reproduce this locally and am looking into it. I think it's just
a race condition in the tests.

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: dbus-python
Source-Version: 1.2.12-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated dbus-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Sep 2019 10:58:27 +0100
Source: dbus-python
Architecture: source
Version: 1.2.12-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 940087
Changes:
 dbus-python (1.2.12-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes a build regression in libsecret by restoring the ability to
   raise SystemExit from a dbus-python method (Closes: #940087)
Checksums-Sha1:
 d7ff18cded36d367766aebdd1c2282c8be681d47 3802 dbus-python_1.2.12-1.dsc
 d42b76863d89890a335425f5fe796052e3cc3712 574727 dbus-python_1.2.12.orig.tar.gz
 9d1fc96b9b25adfe1b3d196a7bd7288b89d0d7d5 833 dbus-python_1.2.12.orig.tar.gz.asc
 d7053aee947c5068e5af85e8893da6dbc6a7b74f 34088 
dbus-python_1.2.12-1.debian.tar.xz
 ea23c472958c610fe37c15796b62d93ba1958020 8106 
dbus-python_1.2.12-1_source.buildinfo
Checksums-Sha256:
 1febae81596ef245993e04f5cc70d80f777b7b75d7ecfdec595ff6bbe47fb0b6 3802 
dbus-python_1.2.12-1.dsc
 cdd4de2c4f5e58f287b12013ed7b41dee81d503c8d0d2397c5bd2fb01badf260 574727 
dbus-python_1.2.12.orig.tar.gz
 0f7a4ebd0bce1fd3ae379eec3ab316b423b7c001c5dbc43abc3aea3e7ad52056 833 
dbus-python_1.2.12.orig.tar.gz.asc
 fa43d31caef5513b9d583c9f89958c0dcc1eb04c032c23bd6579327e3d9e7639 34088 
dbus-python_1.2.12-1.debian.tar.xz
 3f1587431a053d61d84c24d64752e74ac6e22ead5bad324abf989f5911538c47 8106 
dbus-python_1.2.12-1_source.buildinfo
Files:
 2e9f6039320dec9ff7ff4cdbb8df5eb1 3802 devel optional dbus-python_1.2.12-1.dsc
 428b7a9e7e2d154a7ceb3e13536283e4 574727 devel optional 
dbus-python_1.2.12.orig.tar.gz
 87dcc4d727f28a07d2308a7a4200fa22 833 devel optional 
dbus-python_1.2.12.orig.tar.gz.asc
 d0cc145a51558731963dbb824de76d49 34088 devel optional 
dbus-python_1.2.12-1.debian.tar.xz
 a0ed506df972ab16cc5331aae449f262 8106 devel optional 
dbus-python_1.2.12-1_source.buildinfo

Bug#912391: marked as done (segment: FTBFS with Java 11 due to JAXB removal)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 10:21:05 +
with message-id 
and subject line Bug#912391: fixed in segment 1.4.2-1
has caused the Debian Bug report #912391,
regarding segment: FTBFS with Java 11 due to JAXB removal
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.)


-- 
912391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: segment
Version: 1.3.5~svn57+dfsg-1.1
Severity: serious
Tags: ftbfs buter sid

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

...
compile:
[mkdir] Created dir: /build/1st/segment-1.3.5~svn57+dfsg/build/classes
[javac] /build/1st/segment-1.3.5~svn57+dfsg/build.xml:44: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 68 source files to 
/build/1st/segment-1.3.5~svn57+dfsg/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:23:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBContext;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:24:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:290:
 error: cannot find symbol
[javac] public static JAXBContext getContext(String context) {
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:305:
 error: cannot find symbol
[javac] public static JAXBContext getContext(String context, 
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Util.java:321:
 error: cannot find symbol
[javac] public static JAXBContext getContext(Class... 
classesToBeBound) {
[javac]   ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Util
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:13:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBContext;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:14:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.JAXBException;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:15:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Marshaller;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:16:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.Unmarshaller;
[javac]  ^
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:30:
 error: cannot find symbol
[javac] private Marshaller marshaller;
[javac] ^
[javac]   symbol:   class Marshaller
[javac]   location: class Bind
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:32:
 error: cannot find symbol
[javac] private Unmarshaller unmarshaller;
[javac] ^
[javac]   symbol:   class Unmarshaller
[javac]   location: class Bind
[javac] 
/build/1st/segment-1.3.5~svn57+dfsg/src/net/sourceforge/segment/util/Bind.java:39:
 error: cannot find symbol
[javac] public Bind(JAXBContext context, Schema schema) {
[javac] ^
[javac]   symbol:   class JAXBContext
[javac]   location: class Bind
   

Bug#940087: FTBFS: test-prompt: Method "Prompt" with signature "s" on interface "org.freedesktop.Secret.Prompt" doesn't exist

[Simon McVittie]

Control: reassign -1 python3-dbus 1.2.10-1
Control: affects -1 + src:libsecret
Control: tags -1 + pending

On Thu, 12 Sep 2019 at 09:34:21 +0100, Simon McVittie wrote:
> > **
> > ERROR:libsecret/test-prompt.c:239:test_perform_vanish: assertion failed 
> > (error == NULL): Method "Prompt" with signature "s" on interface 
> > "org.freedesktop.Secret.Prompt" doesn't exist
> >  (g-dbus-error-quark, 19)
> 
> I can reproduce this locally and am looking into it. I think it's just
> a race condition in the tests.

This was a regression in dbus-python. libsecret was doing something
somewhat suspect (calling sys.exit from a dbus-python method, which
relies on being able to propagate a Python exception all the way through
libdbus and GLib) and recent error-handling fixes in dbus-python broke
the ability to do this.

Since dbus-python's most important feature is compatibility with old
versions of itself, I'm going to revert those fixes.

smcv

Processed: Re: Bug#940087: FTBFS: test-prompt: Method "Prompt" with signature "s" on interface "org.freedesktop.Secret.Prompt" doesn't exist

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-dbus 1.2.10-1
Bug #940087 [src:libsecret] FTBFS: test-prompt: Method "Prompt" with signature 
"s" on interface "org.freedesktop.Secret.Prompt" doesn't exist
Bug reassigned from package 'src:libsecret' to 'python3-dbus'.
No longer marked as found in versions libsecret/0.18.7-1.
Ignoring request to alter fixed versions of bug #940087 to the same values 
previously set
Bug #940087 [python3-dbus] FTBFS: test-prompt: Method "Prompt" with signature 
"s" on interface "org.freedesktop.Secret.Prompt" doesn't exist
Marked as found in versions dbus-python/1.2.10-1.
> affects -1 + src:libsecret
Bug #940087 [python3-dbus] FTBFS: test-prompt: Method "Prompt" with signature 
"s" on interface "org.freedesktop.Secret.Prompt" doesn't exist
Added indication that 940087 affects src:libsecret
> tags -1 + pending
Bug #940087 [python3-dbus] FTBFS: test-prompt: Method "Prompt" with signature 
"s" on interface "org.freedesktop.Secret.Prompt" doesn't exist
Added tag(s) pending.

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

Bug#912391: marked as pending in segment

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912391 in segment 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/java-team/segment/commit/2f8053904fd448b36686543c623e6a075494


Fixed the build failure with Java 11 (Closes: #912391)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912391

Processed: Bug#912391 marked as pending in segment

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912391 [src:segment] segment: FTBFS with Java 11 due to JAXB removal
Added tag(s) pending.

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

Bug#940092: flowblade doesn't start

[Theodore Y. Ts'o]

Package: flowblade
Version: 2.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed flowblade, and then tried to start it.  It failed to start;
I expected it to start and be usable.  :-)

% flowblade
FLOWBLADE MOVIE EDITOR 2.2
--
Launch script dir: /bin
Running from filesystem...
MLT found, version: 6.16.0
Failed to import module app.py to launch Flowblade!
ERROR: No module named processutils
Installation was assumed to be at: /bin/Flowblade


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

Kernel: Linux 5.3.0-rc4-15023-g572feee69df4 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flowblade depends on:
ii  frei0r-plugins1.6.1-3
ii  gir1.2-gdkpixbuf-2.0  2.38.1+dfsg-1
ii  gir1.2-glib-2.0   1.58.3-2
ii  gir1.2-gtk-3.03.24.10-1
ii  gir1.2-pango-1.0  1.42.4-7
ii  gmic  2.4.5-1+b1
ii  libmlt-data   6.16.0-3
ii  librsvg2-common   2.44.14-1
ii  python2.7.16-1
ii  python-cairo  1.16.2-1+b1
ii  python-dbus   1.2.8-3
ii  python-gi 3.32.2-1
ii  python-gi-cairo   3.32.2-1
ii  python-mlt6.16.0-3
ii  python-numpy  1:1.16.2-1
ii  python-pil6.1.0-1
ii  swh-plugins   0.4.17-2

flowblade recommends no packages.

flowblade suggests no packages.

-- no debconf information

Bug#939937: Acknowledgement (Remotely exploitable null pointer dereference bug)

[Steinar H. Gunderson]

On Wed, Sep 11, 2019 at 12:36:03PM +0200, Max Kellermann wrote:
> I committed my patch to libapreq's Subversion repository:
> 
>  http://svn.apache.org/viewvc?view=revision=1866760

Thanks! I'll make an upload to unstable when I get the time, but I guess the
security team should do one for stable. TBH I don't know how this process
works currently; perhaps security-team@ should be involved?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#912230: marked as done (drmips FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 08:41:06 +
with message-id 
and subject line Bug#912230: fixed in drmips 2.0.1-2.1
has caused the Debian Bug report #912230,
regarding drmips FTBFS with OpenJDK 11
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.)


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

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

...
[  2%] Building Java objects for DrMIPS.jar
cd /build/1st/drmips-2.0.1/src/pc/DrMIPS/src && /usr/bin/javac -encoding UTF-8 
-source 1.7 -target 1.7 -classpath 
:/build/1st/drmips-2.0.1/src/pc/DrMIPS/src:/build/1st/drmips-2.0.1/obj-x86_64-linux-gnu/src/pc/DrMIPS/src:../lib/DrMIPSSimulator.jar
 -d 
/build/1st/drmips-2.0.1/obj-x86_64-linux-gnu/src/pc/DrMIPS/src/CMakeFiles/DrMIPS.dir
 
@/build/1st/drmips-2.0.1/obj-x86_64-linux-gnu/src/pc/DrMIPS/src/CMakeFiles/DrMIPS.dir/java_sources
warning: [options] bootstrap class path not set in conjunction with -source 7
org/fife/ui/rsyntaxtextarea/RSyntaxTextArea.java:613: error: cannot find symbol
sm.checkSystemClipboardAccess();
  ^
  symbol:   method checkSystemClipboardAccess()
  location: variable sm of type SecurityManager
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
1 warning
make[3]: *** [src/pc/DrMIPS/src/CMakeFiles/DrMIPS.dir/build.make:2625: 
src/pc/DrMIPS/src/CMakeFiles/DrMIPS.dir/java_compiled_DrMIPS] Error 1
--- End Message ---
--- Begin Message ---
Source: drmips
Source-Version: 2.0.1-2.1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated drmips 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, 12 Sep 2019 10:01:49 +0200
Source: drmips
Architecture: source
Version: 2.0.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bruno Nova 
Changed-By: Emmanuel Bourg 
Closes: 912230
Changes:
 drmips (2.0.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed the build failure with Java 11 (Closes: #912230)
Checksums-Sha1:
 b216aa1d5b291bbcfa885f7ba81e1ca61a89126d 1886 drmips_2.0.1-2.1.dsc
 337afd82e03513cbef38167b75c63a69a590cc83 7912 drmips_2.0.1-2.1.debian.tar.xz
 185cb5d82f6b2b5a757ead6609c5fcf6f31d704e 8908 drmips_2.0.1-2.1_source.buildinfo
Checksums-Sha256:
 f716a705a52e82046d4bc3d7330c14521a67acfcd93d757691447177c058774c 1886 
drmips_2.0.1-2.1.dsc
 d86f0826fa04b78758e68a1e2c96c8df002bfad47dc67c5000684a7d4ecf5df7 7912 
drmips_2.0.1-2.1.debian.tar.xz
 42c526df8d6ef4d7610ecc9d6c8fee7db7f6f4009fd2dd75d7a5abf9f50b9491 8908 
drmips_2.0.1-2.1_source.buildinfo
Files:
 0f50b14be225e3d6716ed97535fe0d6a 1886 electronics optional drmips_2.0.1-2.1.dsc
 4241c726d1d68eb273e823242a40b7b3 7912 electronics optional 
drmips_2.0.1-2.1.debian.tar.xz
 6b4de2389ae065e8a5c4e148b8a1e400 8908 electronics optional 
drmips_2.0.1-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl15/EoSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsB5wQAKVC1QJM05lCVomOKUperzntYPVGrdtg
Z9MDvixMXUVKfvfgAjxyJQlo6jJNXKGGYHAEyInVxYSYhpH5msn6f9XPqnar1O4E
K030cze0WfqT6xNuNEKAYJmUXJTk3YMj52Jp7gk++V+qgcyqusKrj1/t7LPKk1w3
6eXJYMQu2+zd/h2SSA75JU9TiDmA0hF5rt0fq5SETYEpKaXlYLFyAj+6V9hn7clQ
KEhWrmsUPjpWhBd9y6L+is20kawRZbf4YHrL6s5W/CbzTcTTX6Cf0InNN0B7vDZ9
0gFPoHOYnDlAalHwX+IDRPYPOOvF8NJwChG6M4gmrhyoUg4JqT1fpv9edw73HmNM
Lqgv/2vLS6qTw76D0l7I9sduHysOA2GrGbNRyR5oPD67ScDBe7jC0ywb+VZvoM3s
rG3aZtZXqjy2FYfC+ANY4fIjXwEBhMW09zVsCup9U/El+oDVr9ZgnibkTCg7+tCl
XvL3ornuYPCZ8O/9LVmOBSblNSegTz3MowrWo/W/uC62bM9N+lEzADUhvEcwcH2+
ODpU3jXEYKaPgfUTidmDYwCefJJRIPCbBkuuLyzxQqN3rFXB/PRPgu3VkDSz9aX4

Bug#940088: gimp: crashes on opening exsisting or creating new image

[Michael Monschau]

Package: gimp
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?
Starting GIMP and opening a jpg,png or xcf File.
Alternatively creating a new File via File -> New ... -> OK
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
removing config files, purging and reinstalling GIMP (multiple times) 
   * What was the outcome of this action?
The "GIMP Crash Debug" dialog opens with the following fatal error (jpg case): 
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6) 

using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 22161 - Thread 22161 #

[New LWP 22162]
[New LWP 22163]
[New LWP 22166]
[New LWP 22167]
[New LWP 22168]
[New LWP 22169]
[New LWP 22170]
[New LWP 22183]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd93495010, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7f21590e1e00 (LWP 22161) "gimp-2.10"  __libc_read 
(nbytes=256, buf=0x7ffd93495010, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f2157e90700 (LWP 22162) "gmain"  0x7f215ae3c819 in 
__GI___poll (fds=0x5598c5db2160, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7f215768f700 (LWP 22163) "gdbus"  0x7f215ae3c819 in 
__GI___poll (fds=0x5598c5dca6b0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f214990d700 (LWP 22166) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f214910c700 (LWP 22167) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f214890b700 (LWP 22168) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f213bfff700 (LWP 22169) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f213b7fe700 (LWP 22170) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f213aaa3700 (LWP 22183) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 9 (Thread 0x7f213aaa3700 (LWP 22183)):
#0  0x7f215ae41f59 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f215b15395f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f215b5fe0cd in  () at /lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3  0x7f215b13189d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f215af18fa3 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139780694882048, 
1035657979091779756, 140727074507534, 140727074507535, 139780694882048, 
94114679608800, -1144740976228532052, -1144529400536858452}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#5  

Bug#940087: FTBFS: test-prompt: Method "Prompt" with signature "s" on interface "org.freedesktop.Secret.Prompt" doesn't exist

[Simon McVittie]

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

During build-time tests, for example in

and
:

> **
> ERROR:libsecret/test-prompt.c:239:test_perform_vanish: assertion failed 
> (error == NULL): Method "Prompt" with signature "s" on interface 
> "org.freedesktop.Secret.Prompt" doesn't exist
>  (g-dbus-error-quark, 19)

I can reproduce this locally and am looking into it. I think it's just
a race condition in the tests.

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

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

Processed: plplot breaks gnudatalanguage autopkgtest: PLplot installation lacks the requested driver: xwin

[Debian Bug Tracking System]

Processing control commands:

> found -1 plplot/5.15.0+dfsg-3
Bug #940085 [src:plplot, src:gnudatalanguage] plplot breaks gnudatalanguage 
autopkgtest: PLplot installation lacks the requested driver: xwin
Marked as found in versions plplot/5.15.0+dfsg-3.
> found -1 gnudatalanguage/0.9.9-10
Bug #940085 [src:plplot, src:gnudatalanguage] plplot breaks gnudatalanguage 
autopkgtest: PLplot installation lacks the requested driver: xwin
Marked as found in versions gnudatalanguage/0.9.9-10.

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

Bug#940085: plplot breaks gnudatalanguage autopkgtest: PLplot installation lacks the requested driver: xwin

[Paul Gevers]

Source: plplot, gnudatalanguage
Control: found -1 plplot/5.15.0+dfsg-3
Control: found -1 gnudatalanguage/0.9.9-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 plplot the autopkgtest of gnudatalanguage fails
in testing when that autopkgtest is run with the binary packages of
plplot from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
plplot from testing5.15.0+dfsg-3
gnudatalanguagefrom testing0.9.9-10
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 plplot 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=plplot

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnudatalanguage/2942807/log.gz

% TEST_BUG_2974380: PLplot installation lacks the requested driver: xwin
% Execution halted at: TEST_BUG_2974380 3
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_bug_2974380.pro
%  $MAIN$

[...]

% TEST_BUG_3275334: PLplot installation lacks the requested driver: xwin
% Execution halted at: TEST_BUG_327533449
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_bug_3275334.pro
%  $MAIN$

[...]

% TEST_CONGRID_ON_IMAGES: PLplot installation lacks the requested
driver: xwin
% Execution halted at: TEST_CONGRID_ON_IMAGES   150
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_congrid.pro
%  TEST_CONGRID   150
/tmp/autopkgtest-lxc.9dcat9i9/downtmp/build.9Uq/src/testsuite/test_congrid.pro
%  $MAIN$
% WARNING: your version of the GraphicsMagick library will truncate
images to 16 bits per pixel
% Compiled module: TEST_CONSTANTS.
% WARNING: your version of the GraphicsMagick library will truncate
images to 16 bits per pixel
% Compiled module: TEST_CONTAINER.
gdl:
/build/gnudatalanguage-jfDpIi/gnudatalanguage-0.9.9/src/envt.cpp:1368:
void EnvBaseT::SetNextParUnchecked(BaseGDL*): Assertion
`static_cast(parIx - pro->key.size()) < pro->nPar' failed.
Magick: abort due to signal 6 (SIGABRT) "Abort"...
Aborted

[... ] but there is more

=
14 Error(s) found
=
test_bug_2974380
test_bug_3275334
test_congrid
test_contour
test_device
test_execute
test_extra_keywords
test_moment
test_plot_oo
test_plot_usersym
test_pmulti_basic
test_qhull
test_tv
test_window_background



signature.asc
Description: OpenPGP digital signature

Bug#934961: marked as done (insserv breaks startpar autopkgtest)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 07:51:40 +
with message-id 
and subject line Bug#934961: fixed in startpar 0.64-1
has caused the Debian Bug report #934961,
regarding insserv breaks startpar autopkgtest
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.)


-- 
934961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: insserv, startpar
Control: found -1 insserv/1.20.0-2
Control: found -1 startpar/0.63-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent (one month old) upload of insserv the autopkgtest of
startpar fails in testing when that autopkgtest is run with the binary
packages of insserv from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
insservfrom testing1.20.0-2
startpar   from testing0.63-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 insserv 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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/startpar/2751621/log.gz

Setting up insserv (1.20.0-2) ...
insserv: FATAL: service mountkernfs has to exist for service networking
insserv: FATAL: service urandom has to exist for service networking
insserv: FATAL: service mountdevsubfs has to exist for service hwclock
insserv: exiting now!
Setting up autopkgtest-satdep (0) ...
(Reading database ... 12357 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [02:13:15]: test testsuite: [---
make: Entering directory
'/tmp/autopkgtest-lxc.gu4ek7wq/downtmp/build.cYi/src/testsuite'
STARTPAR=/lib/startpar/startpar ./runtests
insserv: fopen(/etc/init.d/.depend.boot): Permission denied
error: the test init.d was not running
error: the ls command was not running
make: Leaving directory
'/tmp/autopkgtest-lxc.gu4ek7wq/downtmp/build.cYi/src/testsuite'
autopkgtest [02:13:15]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: startpar
Source-Version: 0.64-1

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated startpar 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, 12 Sep 2019 07:08:43 +
Source: startpar
Architecture: source
Version: 0.64-1
Distribution: unstable
Urgency: medium
Maintainer: Debian sysvinit maintainers 

Changed-By: Dmitry Bogatov 
Closes: 588666 934961
Changes:
 startpar (0.64-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #588666)
   * Prevent warnings on stderr from breaking autopkgtests (Closes: #934961)
Checksums-Sha1:
 d363bccb09d32fe393ca0f469f8da5193190918f 2305 startpar_0.64-1.dsc
 620e593823c617f742ddaa316dd9e6eaae243cfc 24464 startpar_0.64.orig.tar.xz
 424624866600a7384aaddb635c4cfa5c53c9a28f 313 startpar_0.64.orig.tar.xz.asc
 032621ba645f1b530678ae08b1553cd2d1a60f80 6732 startpar_0.64-1.debian.tar.xz
 7c538433a7c2cf3b411d0f354ad947c1737c83e2 5639 startpar_0.64-1_source.buildinfo
Checksums-Sha256:
 e7a2f3df023dc14ade832b2d1c4bdcf751b2a91d28c9fa84ed9df23a11c18939 2305 
startpar_0.64-1.dsc
 482a6869a5a5413d305f3073a0d831cca14bf7634554194419ca7015d5dd5731 24464 
startpar_0.64.orig.tar.xz
 478993e12a10ae7ed326542677c793dec74b32a46e0a114df010eed68a3d6328 313 

Bug#915291: marked as done (java3ds-fileloader: FTBFS with Java 11 due to Applet API removal)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 07:48:51 +
with message-id 
and subject line Bug#915291: fixed in java3ds-fileloader 1.2+dfsg-4
has caused the Debian Bug report #915291,
regarding java3ds-fileloader: FTBFS with Java 11 due to Applet API removal
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.)


-- 
915291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java3ds-fileloader
Version: 1.2+dfsg-3
Severity: serious
Tags: ftbfs

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

...
build:
[mkdir] Created dir: 
/build/1st/java3ds-fileloader-1.2+dfsg/debian/build/classes
[javac] /build/1st/java3ds-fileloader-1.2+dfsg/debian/build.xml:13: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 38 source files to 
/build/1st/java3ds-fileloader-1.2+dfsg/debian/build/classes
[javac] 
/build/1st/java3ds-fileloader-1.2+dfsg/com/microcrowd/loader/java3d/max3ds/Main.java:59:
 error: package com.sun.j3d.utils.applet does not exist
[javac] import com.sun.j3d.utils.applet.MainFrame;
[javac]^
[javac] 
/build/1st/java3ds-fileloader-1.2+dfsg/com/microcrowd/loader/java3d/max3ds/Main.java:91:
 error: cannot find symbol
[javac] MainFrame mainFrame = new MainFrame(self, 750, 550);
[javac] ^
[javac]   symbol:   class MainFrame
[javac]   location: class Main
[javac] 
/build/1st/java3ds-fileloader-1.2+dfsg/com/microcrowd/loader/java3d/max3ds/Main.java:91:
 error: cannot find symbol
[javac] MainFrame mainFrame = new MainFrame(self, 750, 550);
[javac]   ^
[javac]   symbol:   class MainFrame
[javac]   location: class Main
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 errors

BUILD FAILED
/build/1st/java3ds-fileloader-1.2+dfsg/debian/build.xml:13: Compile failed; see 
the compiler error output for details.

Total time: 10 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1
--- End Message ---
--- Begin Message ---
Source: java3ds-fileloader
Source-Version: 1.2+dfsg-4

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated java3ds-fileloader 
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, 12 Sep 2019 09:24:49 +0200
Source: java3ds-fileloader
Architecture: source
Version: 1.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 915291
Changes:
 java3ds-fileloader (1.2+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * No longer build the applet to fix the build failure with Java 11
 (Closes: #915291)
   * Build with the DH sequencer instead of CDBS
   * Standards-Version updated to 4.4.0
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 a6ffe52c80d372125edfff3e6d8c1a30bdb13659 2123 java3ds-fileloader_1.2+dfsg-4.dsc
 1a761018f062642712759e9f53a5d013a3980548 2804 
java3ds-fileloader_1.2+dfsg-4.debian.tar.xz
 5ce3537b2849305091391773d655be3bddd6ec65 8580 
java3ds-fileloader_1.2+dfsg-4_source.buildinfo
Checksums-Sha256:
 988ab0158ab393dd77d5ce19d81ba40c65e3e04ea032ddb92092be8f66d8c238 2123 
java3ds-fileloader_1.2+dfsg-4.dsc
 49826d2c8bb1364f668c71c793cc9a173f831055a4d40a5a7e2591273a0108ca 2804 
java3ds-fileloader_1.2+dfsg-4.debian.tar.xz
 12a3f021a3c268d4ce9e447475ac149e11d3e0b919af43720c61a91dbacfdd6a 8580 
java3ds-fileloader_1.2+dfsg-4_source.buildinfo
Files:
 1f51d8f2fe80432fa918439c6e91b7fe 2123 java optional 

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

[Andreas Tille]

Control: tags -1 help

On Sun, Sep 08, 2019 at 11:00:34PM +0200, Moritz Mühlenhoff wrote:
> On Sun, Sep 08, 2019 at 08:41:40AM +0200, Andreas Tille wrote:
> > On Sat, Sep 07, 2019 at 10:43:53PM +0200, Moritz Mühlenhoff wrote:
> > > 
> > > The current releases on https://github.com/sofa-framework claim to be Qt5
> > > compatible. Is anyone working on updating the package or should it be 
> > > removed?
> > > 
> > > sofa-framework is one of the three remaining reverse dependencies of
> > > libqwt5-qt4-dev at this point.
> > 
> > I tried to upgrade sofa-framework but had severe issues with new cmake
> > configuration.  I'll have a look next week.
> 
> If you're stuck, feel free to ping #debian-qt-kde.

I need to admit I'm totally stuck with this package.  Yes, there is a
new upstream version since a long time and I tried several times to
update it in Git[1].  However, its basically a new packaging of a large
package with the need for excluding several code copies of libraries.
I took over the maintenance from a former uploader which left the team
but I need to admit my time resources and interest in this package are
quite sparse.

To have a chance to keep sofa-framework we need an expert in cmake who
has some experience how to replace Debian packaged libraries.  I'd
happily add any volunteer to the Debian Med team to give full commit
permissions.  If nobody volunteers I do not see a realistic chance to
keep that package.

Kind regards,

Andreas.


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

-- 
http://fam-tille.de

Processed: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #875184 [src:sofa-framework] [sofa-framework] Future Qt4 removal from Buster
Added tag(s) help.

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

Bug#915291: marked as pending in java3ds-fileloader

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #915291 in java3ds-fileloader 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/java-team/java3ds-fileloader/commit/d2c7e9e14fd31924b0f26238830a0cd160d18d5d


No longer build the applet to fix the build failure with Java 11 (Closes: 
#915291)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/915291

Processed: Bug#915291 marked as pending in java3ds-fileloader

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #915291 [src:java3ds-fileloader] java3ds-fileloader: FTBFS with Java 11 due 
to Applet API removal
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> user debian-j...@lists.debian.org
Setting user to debian-j...@lists.debian.org (was ebo...@apache.org).
> usertag 915291 + default-java11
There were no usertags set.
Usertags are now: default-java11.
> retitle 915291 java3ds-fileloader: FTBFS with Java 11 due to Applet API 
> removal
Bug #915291 [src:java3ds-fileloader] java3ds-fileloader FTBFS: error: package 
com.sun.j3d.utils.applet does not exist
Changed Bug title to 'java3ds-fileloader: FTBFS with Java 11 due to Applet API 
removal' from 'java3ds-fileloader FTBFS: error: package 
com.sun.j3d.utils.applet does not exist'.
>
End of message, stopping processing here.

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

Bug#935290: moar digging

[Niels Thykier]

On Wed, 11 Sep 2019 07:21:24 +0200 Robert Lemmen
 wrote:
> ...and it's fakeroot! it does ld_preload to map file user ids, and doing
> that it fakes stat calls, but not statx!
> 
> regards  robert
> 
> -- 
> Robert Lemmen   http://www.semistable.com 


Does rakudo build with "Rules-Requires-Root: no"[1]?  If it does, then
you can work around the bug / issue in fakeroot for sid, testing and
stable for now by using it.

Thanks,
~Niels


[1] Assumes you do not need static ownerships or any chown calls during
package build/installation.

Bug#940007: marked as done (gitlab: CVE-2019-16170: Project Template Functionality Could Be Used to Access Restricted Project Data)

[Debian Bug Tracking System]

Your message dated Thu, 12 Sep 2019 06:49:20 +
with message-id 
and subject line Bug#940007: fixed in gitlab 12.0.9-1
has caused the Debian Bug report #940007,
regarding gitlab: CVE-2019-16170: Project Template Functionality Could Be Used 
to Access Restricted Project Data
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.)


-- 
940007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 11.8.10+dfsg-1
Severity: grave
Tags: security upstream
Control: found -1 12.0.8-2
Control: found -1 12.0.8-1

Hi,

The following vulnerability was published for gitlab.

CVE-2019-16170[0]:
|Project Template Functionality Could Be Used to Access Restricted
|Project Data

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-16170
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16170
[1] 
https://about.gitlab.com/2019/09/10/critical-security-release-gitlab-12-dot-2-dot-5-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 12.0.9-1

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

Debian distribution maintenance software
pp.
Nilesh  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 Sep 2019 10:12:18 -0400
Source: gitlab
Architecture: source
Version: 12.0.9-1
Distribution: experimental
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Nilesh 
Closes: 940007
Changes:
 gitlab (12.0.9-1) experimental; urgency=high
 .
   * Team Upload
   * New upstream version 12.0.9 (Closes: #940007)
 (Fixes: CVE-2019-16170)
Checksums-Sha1:
 77c99bd953f4a7e262f087abd42bb65aa40eb466 2314 gitlab_12.0.9-1.dsc
 5b101fa06aa6aad6ac7e68997a33415b16bfa72c 72973516 gitlab_12.0.9.orig.tar.bz2
 f94fb2edf341b6c09043a1cb9ce3a5aedde3594a 1161420 gitlab_12.0.9-1.debian.tar.xz
 cbdc3511354e5b38671761936841d965877bdfcf 12920 gitlab_12.0.9-1_amd64.buildinfo
Checksums-Sha256:
 78d7f9f2c4e67bb0310f7cc946d1e49d15af30c16f24c2922877f281b4b6c194 2314 
gitlab_12.0.9-1.dsc
 a0dd0c4b8bee1421cb3c1c677e449e0c9755b8320f6a96e8fdd0792e980af0c1 72973516 
gitlab_12.0.9.orig.tar.bz2
 b089a2729bf600b3d1c61f803f947f686d026522754c3a3e674c79016f10d43d 1161420 
gitlab_12.0.9-1.debian.tar.xz
 5756288ca4a5ca524655db922f58fe597abab803c18d5f34f63fbb9de7d1cd1e 12920 
gitlab_12.0.9-1_amd64.buildinfo
Files:
 23ced619a7f05eb99bfd759766c5d97a 2314 net optional gitlab_12.0.9-1.dsc
 9907d968982f960ce3012adad8683081 72973516 net optional 
gitlab_12.0.9.orig.tar.bz2
 5cc6c0ae823821a1e3dc497a6c30e7dd 1161420 net optional 
gitlab_12.0.9-1.debian.tar.xz
 3f9d0bcb7d37bc83ee5ff361bee66ab5 12920 net optional 
gitlab_12.0.9-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl154soACgkQgj6WdgbD
S5Z3txAAvTp2vQDxatTc6XQGFvIyktRU+5WQvdhQ9h0cBoRhvBtIHAC38rN9A4FK
8cdsW8QrGa/LL779m+Rl6C+xF3S94TsLkEOpSVz6z5jyhh3v/ssJxzEu4m5CoKEo
EU+9cyG6I0a3szpoQY5YjAWFzdnPwqFG5rMrIEpUA/tbCKBOOmmLYqE6nRBOZR1C
Usm/CCoC8M/xIKa7aZuO9A+5/htkJz6YdiD+SG2S2lZ5e+NYpIqNij+1s2HC8r41
/9KGmnR/3FD0OoatCYNt3WQeoOe1m+nE51/7mO2Szdo7NidoP86M/Ehlt869NA4l
y5UE6tNwyeVab7LnHqS31tD/YmlX8FDj/Ip3w1jd/tEUuTCqFtkhcXRC/ekrqRuc
pF3sRfigI6KwsN8VFVmuBqw3BfqcFmiZqQ4Cw0IY1MB7tEZDUcRXDtm7xR8XxSnV
JMczrvFewwXPMvSpbyxJAiVE0Jck9j+vnYN1DojgReQmjP2E3huftPh08bdcrJBJ
6Oh2dGfwj5HUsLsBQR/Ex62cQES4zhtzU4SuDa8NlmsmPBeAOFi3U7Vd1iJeT/hA
Oltr0u4V+Ug1sK1cWn44NVR2z/UWqsvnPCBZDoN+rl0JB4f0xyNcu2Jknh+Y0P4N
vJ8xgBAkW10BaWatILn5TfJ11yn40oK83Ki6UD2/6qb+CInVdI0=
=LrKt
-END PGP SIGNATURE End Message ---