Bug#959236: Bonding doesn't work

[Roberto Ibáñez]

Bonding doesn't work. Same behavior here.

Debian bullseye/sid 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64
GNU/Linux

 /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth
(1000) reached

Bug#961191: src:python-traceback2: fails to migrate to testing for too long: makes python-unittest2 non-installable

[Paul Gevers]

Source: python-traceback2
Version: 1.4.0-5
Severity: serious
Control: close -1 1.4.0-6
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-traceback2 in its current version in unstable has been trying
to migrate for 60 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-traceback2




signature.asc
Description: OpenPGP digital signature

Processed: src:python-traceback2: fails to migrate to testing for too long: makes python-unittest2 non-installable

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.4.0-6
Bug #961191 [src:python-traceback2] src:python-traceback2: fails to migrate to 
testing for too long: makes python-unittest2 non-installable
Marked as fixed in versions python-traceback2/1.4.0-6.
Bug #961191 [src:python-traceback2] src:python-traceback2: fails to migrate to 
testing for too long: makes python-unittest2 non-installable
Marked Bug as done

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

Bug#961148: marked as done (libgraphics-colorobject-perl: broken by new libgraphics-colornames-perl)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 03:04:22 +
with message-id 
and subject line Bug#961148: fixed in libgraphics-colorobject-perl 0.5.0-9
has caused the Debian Bug report #961148,
regarding libgraphics-colorobject-perl: broken by new 
libgraphics-colornames-perl
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.)


-- 
961148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgraphics-colorobject-perl
Version: 0.5.0-7.1
Severity: grave
Tags: bullseye sid
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=127300

Graphics::ColorObject needs Graphics::ColorNames::HTML, which was recently
dropped from the libgraphics-colornames-perl package in Debian.

 % perl -e 'use Graphics::ColorObject'
 Cannot load color naming scheme module Graphics::ColorNames::HTML at 
/usr/share/perl5/Graphics/ColorObject.pm line 1902.
 Compilation failed in require at -e line 1.

Graphics::ColorNames::HTML is now available separately on CPAN, with a
deprecation notice pointing users to Graphics::ColorNames::WWW (packaged
in Debian as libgraphics-colornames-www-perl) instead.

So Graphics::ColorObject needs to adapt, or Graphics::ColorNames::HTML
needs to be packaged separately despite the deprecation.

Also, libgraphics-colornames-perl should add a Breaks entry for the
versions of libgraphics-colorobject-perl it broke.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libgraphics-colorobject-perl
Source-Version: 0.5.0-9
Done: Manoj Srivastava 

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

Debian distribution maintenance software
pp.
Manoj Srivastava  (supplier of updated 
libgraphics-colorobject-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: Wed, 20 May 2020 19:32:47 -0700
Source: libgraphics-colorobject-perl
Architecture: source
Version: 0.5.0-9
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Closes: 961148
Changes:
 libgraphics-colorobject-perl (0.5.0-9) unstable; urgency=medium
 .
   * The new libgraphics-colornames-perl has split out the HTML colors into
 a separate module, and the Windows and netscape colors went
 away. Adjusted accordingly.
   * Bug fix: "broken by new libgraphics-colornames-perl", thanks to Niko
 Tyni (Closes: #961148).
Checksums-Sha1:
 b357dede620aa4f7136cfdbcd2249a322cf42583 2127 
libgraphics-colorobject-perl_0.5.0-9.dsc
 55c717051470d96e566b37f3852e7978897c2b24 25275 
libgraphics-colorobject-perl_0.5.0-9.diff.gz
Checksums-Sha256:
 00eb3c1487c4fb72c1924610f5e38ca3cefaa5d45d87e72948536aab82ee3afe 2127 
libgraphics-colorobject-perl_0.5.0-9.dsc
 d45ae38ed718efb565b951b210830f2adcebe2eaa659cebe459e90fa2d58122d 25275 
libgraphics-colorobject-perl_0.5.0-9.diff.gz
Files:
 d168f9675a0170b16ae04920e6a8b906 2127 perl optional 
libgraphics-colorobject-perl_0.5.0-9.dsc
 b5b7ee7cf7af15be587795713b08f1c7 25275 perl optional 
libgraphics-colorobject-perl_0.5.0-9.diff.gz

-BEGIN PGP SIGNATURE-

iQGZBAEBCgCDFiEEq6cQJaG1qIpOX2jCNr1yD29XZHIFAl7F7F9QFIAAGwAs
c3JpdmFzdGFAZ29sZGVuLWdyeXBob24uY29tQUJBNzEwMjVBMUI1QTg4QTRFNUY2
OEMyMzZCRDcyMEY2RjU3NjQ3Ml8yMDYUHHNyaXZhc3RhQGRlYmlhbi5vcmcACgkQ
Nr1yD29XZHLlXggA0PaRzeK3y24ahkHbaN5B9EDtkwNVvmZ+9185rud4guQefZB1
4Azn2pC6p/yM1ega1+OhzJvlNVEw+A5Jakoj+qr5j77xI1w8XC2I5vle481dfjak
5sz+I7R5OD2998C2m95ZA5dFC3QFHD+AW2UUcC2w3Lg/yWww7XuLTiu+LxZf1tkF
u/VOAJozDl2NgrqMVpcquMFiDa4zo2XRWdrwnincL2zKqpIoQesDjKqIRJ5c5NE1
bTwJBMEF60GdVd3Vl3XlMQdE8JscUE2Fv9j4kiLkY9GUxSWb+LURpeAdNI6vJRxy
4viqAx4x3zv1L9Askk+Eif3UpmJYEYcLs5EVdg==
=2wTR
-END PGP SIGNATURE End Message ---

Bug#961049: marked as done (sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-1)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:39 +
with message-id 
and subject line Bug#961049: fixed in sra-sdk 2.10.6+dfsg-1
has caused the Debian Bug report #961049,
regarding sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-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.)


-- 
961049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sra-sdk
Version: 2.9.3+dfsg-1
Severity: serious
Tags: ftbfs bullseye sid

https://buildd.debian.org/status/fetch.php?pkg=sra-sdk=amd64=2.9.3%2Bdfsg-1%2Bb2=1589906040=0

...
/<>/tools/util/test-sra.c:2373:14: error: too many arguments to 
function ‘KClientHttpRequestFormatMsg’
 2373 | rc = KClientHttpRequestFormatMsg
  |  ^~~
In file included from /<>/tools/util/test-sra.c:42:
/usr/include/ncbi-vdb/kns/http-priv.h:53:20: note: declared here
   53 | KNS_EXTERN rc_t CC KClientHttpRequestFormatMsg (
  |^~~
...
--- End Message ---
--- Begin Message ---
Source: sra-sdk
Source-Version: 2.10.6+dfsg-1
Done: u...@debian.org (Aaron M. Ucko)

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated sra-sdk 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, 20 May 2020 22:15:19 -0400
Source: sra-sdk
Architecture: source
Version: 2.10.6+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 943231 961049
Changes:
 sra-sdk (2.10.6+dfsg-1) unstable; urgency=medium
 .
   [ Steffen Moeller ]
   * New upstream version
   * debhelper-compat 12
   * Standards-Version: 4.4.1
 .
   * ncbi-vdb needs to appear as 2.10.2 in Debian with its mbedtls wrapper
 fixed to avoid a link error in this package.
 .
   [ Michael R. Crusoe ]
   * Convert to Python3. Closes: #943231
   * Standards-Version: 4.5.0 (routine-update)
 .
   [ Aaron M. Ucko ]
   * Correct accidental cutover to ncbi-vdb 2.10.5(+dfsg); further update to
 2.10.6.
   * Revert patch updates contingent on spurious cutover to ncbi-vdb.
   * Refresh patches for real.
 - Generally standardize on -pab format.
 - hardening.patch: Rebase C(P)FLAGS, which no longer request extensions.
 - python3: Drop makefile tweaks obsoleted by new PYTHON abstraction.
   * Help validate-names4.c find ncbi-vdb headers that are normally internal.
 To wit, build-depend on libncbi-vdb-dev (>= 2.10.6+dfsg-2~) to ensure
 these headers are installed sanely, and patch validate-names4.c
 accordingly in a new patch use_exposed_headers.patch.  In conjunction
 with taking the latest upstream, closes: #961049.
   * Specify configuration location by passing KONFIG_DIR.  (The makefile
 patch previously in use relied on [fake]root.)
   * Fix usage of default Debian build flags: Use buildflags.mk with
 appropriate _APPEND settings, and tweak hardening.patch to add
 DEB_*FLAGS to the front rather than the end (so as to keep upstream's
 preferred optimization level).
   * Preclean more fully to allow for consecutive builds.
   * List (wildcard) currently uninstalled files in debian/not-installed.
   * Correct logic for identifying all failing tests when there are any.
   * Secure URI in copyright format (routine-update)
   * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target (routine-
 update)
   * Remove trailing whitespace in debian/changelog (routine-update)
   * Remove trailing whitespace in debian/rules (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Add myself to uploaders.
Checksums-Sha1:
 110682d2fabda5ef8210b582fe52265ed0287cfe 2203 sra-sdk_2.10.6+dfsg-1.dsc
 624addec15af7bca572e0350cdfe9eafb34f8a4f 5724360 
sra-sdk_2.10.6+dfsg.orig.tar.xz
 76a17f91b61af4d368c72964e93363aed4ab0eca 3843368 
sra-sdk_2.10.6+dfsg-1.debian.tar.xz
 

Bug#953897: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952627,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
952627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-vdb, sra-sdk
Control: found -1 ncbi-vdb/2.10.3+dfsg-1
Control: found -1 sra-sdk/2.9.3+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ncbi-vdb the autopkgtest of sra-sdk fails in
testing when that autopkgtest is run with the binary packages of
ncbi-vdb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ncbi-vdb   from testing2.10.3+dfsg-1
sra-sdkfrom testing2.9.3+dfsg-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 ncbi-vdb 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=ncbi-vdb

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sra-sdk/4556611/log.gz

autopkgtest [21:40:51]: test run-unit-test: [---
>Decompressing test-data archive...
dbGaP-0/
dbGaP-0/SRR2042184.fasta
meta/
meta/SRR6650398_experiment.xml
meta/SRR6650398_illumina_run.xml
meta/SRR2042184_run.xml
meta/SRR6650398_fastq_run.xml
meta/SRR6650398.bam
meta/SRR7032226_run.xml
meta/reference.fna
meta/SRR7032226_experiment.xml
meta/dbGaP-0.enc_key
meta/SRR2042184_experiment.xml
public/
public/wgs/
public/refseq/
public/refseq/NC_000962.3
public/files/
public/nannot/
public/sra/
public/sra/SRR2042184.sra
public/sra/SRR7032226.sra
public/sra/SRR6650398.sra
>Running test-sra...
test-sra: symbol lookup error: /lib/x86_64-linux-gnu/libncbi-vdb.so.2:
undefined symbol: vdb_mbedtls_md_setup
autopkgtest [21:40:51]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ncbi-vdb
Source-Version: 2.10.6+dfsg-2
Done: u...@debian.org (Aaron M. Ucko)

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-vdb 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, 20 May 2020 22:13:24 -0400
Source: ncbi-vdb
Architecture: source
Version: 2.10.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 952623 952627 953897
Changes:
 ncbi-vdb (2.10.6+dfsg-2) unstable; urgency=medium
 .
   * Install libs/vfs/services-priv.h as .../services-priv-internal.h to
 distinguish it from interfaces/vfs/services-priv.h.  (Neither can
 stand in for the other.)
   * Formally refresh patches that developed offsets.
   * Factor out a new DSLMFLAGS macro for common d-shlibmove flags; include
 the libmbedx509-0 quirk there since it will soon be needed everywhere.
   * Address remaining underlinkage of system libraries (mbed*, z, bz2).
 At this point, the only remaining unresolved references are of libkdf5
 against symbols that could come from either libncbi-vdb or libncbi-wvdb.
 (Closes: #952623, #952627, #953897.)
   * Copy headers rather than moving them to allow for consecutive builds.
   * Fix typo in override_dh_missing name; supply debian/not-installed.
   * Add myself to Uploaders.
Checksums-Sha1:
 

Bug#953897: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:32 +
with message-id 
and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #953897,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
953897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-vdb, sra-sdk
Control: found -1 ncbi-vdb/2.10.3+dfsg-1
Control: found -1 sra-sdk/2.9.3+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ncbi-vdb the autopkgtest of sra-sdk fails in
testing when that autopkgtest is run with the binary packages of
ncbi-vdb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ncbi-vdb   from testing2.10.3+dfsg-1
sra-sdkfrom testing2.9.3+dfsg-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 ncbi-vdb 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=ncbi-vdb

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sra-sdk/4556611/log.gz

autopkgtest [21:40:51]: test run-unit-test: [---
>Decompressing test-data archive...
dbGaP-0/
dbGaP-0/SRR2042184.fasta
meta/
meta/SRR6650398_experiment.xml
meta/SRR6650398_illumina_run.xml
meta/SRR2042184_run.xml
meta/SRR6650398_fastq_run.xml
meta/SRR6650398.bam
meta/SRR7032226_run.xml
meta/reference.fna
meta/SRR7032226_experiment.xml
meta/dbGaP-0.enc_key
meta/SRR2042184_experiment.xml
public/
public/wgs/
public/refseq/
public/refseq/NC_000962.3
public/files/
public/nannot/
public/sra/
public/sra/SRR2042184.sra
public/sra/SRR7032226.sra
public/sra/SRR6650398.sra
>Running test-sra...
test-sra: symbol lookup error: /lib/x86_64-linux-gnu/libncbi-vdb.so.2:
undefined symbol: vdb_mbedtls_md_setup
autopkgtest [21:40:51]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ncbi-vdb
Source-Version: 2.10.6+dfsg-2
Done: u...@debian.org (Aaron M. Ucko)

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-vdb 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, 20 May 2020 22:13:24 -0400
Source: ncbi-vdb
Architecture: source
Version: 2.10.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 952623 952627 953897
Changes:
 ncbi-vdb (2.10.6+dfsg-2) unstable; urgency=medium
 .
   * Install libs/vfs/services-priv.h as .../services-priv-internal.h to
 distinguish it from interfaces/vfs/services-priv.h.  (Neither can
 stand in for the other.)
   * Formally refresh patches that developed offsets.
   * Factor out a new DSLMFLAGS macro for common d-shlibmove flags; include
 the libmbedx509-0 quirk there since it will soon be needed everywhere.
   * Address remaining underlinkage of system libraries (mbed*, z, bz2).
 At this point, the only remaining unresolved references are of libkdf5
 against symbols that could come from either libncbi-vdb or libncbi-wvdb.
 (Closes: #952623, #952627, #953897.)
   * Copy headers rather than moving them to allow for consecutive builds.
   * Fix typo in override_dh_missing name; supply debian/not-installed.
   * Add myself to Uploaders.
Checksums-Sha1:
 

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:32 +
with message-id 
and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #953897,
regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: 
undefined reference to `vdb_mbedtls_entropy_init'
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.)


-- 
953897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sra-sdk
Version: 2.9.3+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> gcc -static-libgcc -o 
> /<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/bin/rcexplain.2.9.3
>  -DNDEBUG -m64 -Wl,-z,relro -Wl,-z,now rcexplain.o 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/lib 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/ilib 
> -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu 
> -L/usr/lib/x86_64-linux-gnu -lkapp -ltk-version -lncbi-vdb -Wl,-Bdynamic -ldl 
> -lpthread -lxml2 -Wl,-Bdynamic -lm -lz -lbz2 -lsz -lmbedx509 -lmbedtls 
> -lmbedcrypto
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_entropy_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_base64_encode'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_setup'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_rsa'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_file'
> /usr/bin/ld: 

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952623,
regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: 
undefined reference to `vdb_mbedtls_entropy_init'
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.)


-- 
952623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sra-sdk
Version: 2.9.3+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> gcc -static-libgcc -o 
> /<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/bin/rcexplain.2.9.3
>  -DNDEBUG -m64 -Wl,-z,relro -Wl,-z,now rcexplain.o 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/lib 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/ilib 
> -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu 
> -L/usr/lib/x86_64-linux-gnu -lkapp -ltk-version -lncbi-vdb -Wl,-Bdynamic -ldl 
> -lpthread -lxml2 -Wl,-Bdynamic -lm -lz -lbz2 -lsz -lmbedx509 -lmbedtls 
> -lmbedcrypto
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_entropy_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_base64_encode'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_setup'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_rsa'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_file'
> /usr/bin/ld: 

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:32 +
with message-id 
and subject line Bug#953897: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #953897,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
953897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skesa
Version: 2.3.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> c++ -std=c++11 -o skesa skesa.o glb_align.o -L 
> /<>/NGS/vdb_out/lib64 -lncbi-ngs-c++ -lncbi-vdb -L 
> /<>/NGS/ngs_out/lib64 -lngs-c++-static -Wl,-Bstatic  
> -lboost_program_options -lboost_iostreams -lboost_regex -lboost_timer 
> -lboost_chrono -lboost_system -Wl,-Bdynamic -lrt -ldl -lm  -lpthread -lz 
> -Wl,-z,relro
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_entropy_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_base64_encode'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_setup'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: 
> 

Bug#953897: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952623,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
952623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-vdb, sra-sdk
Control: found -1 ncbi-vdb/2.10.3+dfsg-1
Control: found -1 sra-sdk/2.9.3+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ncbi-vdb the autopkgtest of sra-sdk fails in
testing when that autopkgtest is run with the binary packages of
ncbi-vdb from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ncbi-vdb   from testing2.10.3+dfsg-1
sra-sdkfrom testing2.9.3+dfsg-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 ncbi-vdb 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=ncbi-vdb

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sra-sdk/4556611/log.gz

autopkgtest [21:40:51]: test run-unit-test: [---
>Decompressing test-data archive...
dbGaP-0/
dbGaP-0/SRR2042184.fasta
meta/
meta/SRR6650398_experiment.xml
meta/SRR6650398_illumina_run.xml
meta/SRR2042184_run.xml
meta/SRR6650398_fastq_run.xml
meta/SRR6650398.bam
meta/SRR7032226_run.xml
meta/reference.fna
meta/SRR7032226_experiment.xml
meta/dbGaP-0.enc_key
meta/SRR2042184_experiment.xml
public/
public/wgs/
public/refseq/
public/refseq/NC_000962.3
public/files/
public/nannot/
public/sra/
public/sra/SRR2042184.sra
public/sra/SRR7032226.sra
public/sra/SRR6650398.sra
>Running test-sra...
test-sra: symbol lookup error: /lib/x86_64-linux-gnu/libncbi-vdb.so.2:
undefined symbol: vdb_mbedtls_md_setup
autopkgtest [21:40:51]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ncbi-vdb
Source-Version: 2.10.6+dfsg-2
Done: u...@debian.org (Aaron M. Ucko)

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-vdb 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, 20 May 2020 22:13:24 -0400
Source: ncbi-vdb
Architecture: source
Version: 2.10.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 952623 952627 953897
Changes:
 ncbi-vdb (2.10.6+dfsg-2) unstable; urgency=medium
 .
   * Install libs/vfs/services-priv.h as .../services-priv-internal.h to
 distinguish it from interfaces/vfs/services-priv.h.  (Neither can
 stand in for the other.)
   * Formally refresh patches that developed offsets.
   * Factor out a new DSLMFLAGS macro for common d-shlibmove flags; include
 the libmbedx509-0 quirk there since it will soon be needed everywhere.
   * Address remaining underlinkage of system libraries (mbed*, z, bz2).
 At this point, the only remaining unresolved references are of libkdf5
 against symbols that could come from either libncbi-vdb or libncbi-wvdb.
 (Closes: #952623, #952627, #953897.)
   * Copy headers rather than moving them to allow for consecutive builds.
   * Fix typo in override_dh_missing name; supply debian/not-installed.
   * Add myself to Uploaders.
Checksums-Sha1:
 

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952623: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952623,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
952623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skesa
Version: 2.3.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> c++ -std=c++11 -o skesa skesa.o glb_align.o -L 
> /<>/NGS/vdb_out/lib64 -lncbi-ngs-c++ -lncbi-vdb -L 
> /<>/NGS/ngs_out/lib64 -lngs-c++-static -Wl,-Bstatic  
> -lboost_program_options -lboost_iostreams -lboost_regex -lboost_timer 
> -lboost_chrono -lboost_system -Wl,-Bdynamic -lrt -ldl -lm  -lpthread -lz 
> -Wl,-z,relro
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_entropy_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_base64_encode'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_setup'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: 
> 

Bug#952627: marked as done (libncbi-vdb2 uses undefined symbols)

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952627,
regarding libncbi-vdb2 uses undefined symbols
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.)


-- 
952627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skesa
Version: 2.3.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> c++ -std=c++11 -o skesa skesa.o glb_align.o -L 
> /<>/NGS/vdb_out/lib64 -lncbi-ngs-c++ -lncbi-vdb -L 
> /<>/NGS/ngs_out/lib64 -lngs-c++-static -Wl,-Bstatic  
> -lboost_program_options -lboost_iostreams -lboost_regex -lboost_timer 
> -lboost_chrono -lboost_system -Wl,-Bdynamic -lrt -ldl -lm  -lpthread -lz 
> -Wl,-z,relro
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_entropy_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_base64_encode'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_setup'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_md_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: 
> 

Bug#952623: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `vdb_mbedtls_entropy_init')

[Debian Bug Tracking System]

Your message dated Thu, 21 May 2020 02:36:31 +
with message-id 
and subject line Bug#952627: fixed in ncbi-vdb 2.10.6+dfsg-2
has caused the Debian Bug report #952627,
regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: 
undefined reference to `vdb_mbedtls_entropy_init'
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.)


-- 
952627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sra-sdk
Version: 2.9.3+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye

Hi,

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

This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).

Relevant part (hopefully):
> gcc -static-libgcc -o 
> /<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/bin/rcexplain.2.9.3
>  -DNDEBUG -m64 -Wl,-z,relro -Wl,-z,now rcexplain.o 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/lib 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/ilib 
> -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu 
> -L/usr/lib/x86_64-linux-gnu -lkapp -ltk-version -lncbi-vdb -Wl,-Bdynamic -ldl 
> -lpthread -lxml2 -Wl,-Bdynamic -lm -lz -lbz2 -lsz -lmbedx509 -lmbedtls 
> -lmbedcrypto
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_entropy_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_decrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_base64_encode'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_random'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_setup'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_parse_public_key'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_encrypt'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_setkey_dec'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_get_len'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_hmac_update'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_init'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_ctr_drbg_seed'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_path'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_md_free'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_aes_crypt_cbc'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_pk_rsa'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `vdb_mbedtls_x509_crt_parse_file'
> /usr/bin/ld: 

Processed: Bug#961049 marked as pending in sra-sdk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #961049 [src:sra-sdk] sra-sdk FTBFS with libncbi-vdb-dev 2.10.6+dfsg-1
Added tag(s) pending.

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

Bug#961049: marked as pending in sra-sdk

[Aaron M. Ucko]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/sra-sdk/-/commit/8ef4c86e26989677717f8bbabf617f5fab302f52


Help validate-names4.c find internal ncbi-vdb headers (#961049).

Build-depend on libncbi-vdb-dev (>= 2.10.6+dfsg-2~) to ensure these
headers are installed sanely, and patch validate-names4.c accordingly
in a new patch use_exposed_headers.patch.  In conjunction with taking
the latest upstream, closes: #961049.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961049

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

[Manoj Srivastava]

The usage of ucf in debian/bacula-director.postinst seems fine.

Manoj
--
Nothing ever becomes real till it is experienced -- even a proverb is no
proverb to you till your life has illustrated it.  -- John Keats
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

[Manoj Srivastava]

Hi,

There is very little actionable in the bug report. We can’t see
 the ucf invocation, nor do we see any error messages that might point
 us to the root cause.

The last lines in the logs:
--8<---cut here---start->8---
service bacula-director restart
Job for bacula-director.service failed because the control process
exited with error code.
See "systemctl status bacula-director.service" and "journalctl -xe" for
details.
--8<---cut here---end--->8---

Point to bacula-director failing to start, which has probably
 little to do with ucf. The package install part of the logs seems to go
 wiothout an error.

--8<---cut here---start->8---
 apt-get -y install bacula bacula-director-pgsql
Reading package lists...
Building dependency tree...
Reading state information...
bacula is already the newest version (9.6.3-1).
bacula-director-pgsql is already the newest version (9.6.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
--8<---cut here---end--->8---

Indeed, this does not seem ucf at all.

Can you show me what I am missing?

Manoj
--
Numeric stability is probably not all that important when you're
guessing.
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#961088: Acknowledgement (libsane-hpaio fails to detect HP MFDs)

[Jan Nordholz]

Hi,

my issue is plain and simple: libsane.hpaio.1.0.0 is no longer dlopen()able
due to an unresolved symbol '_DBG', used in scan/sane/orblite.c:198.
You can check this easily by running scanimage with envvar SANE_DEBUG_DLL=1:

=
] jan@p53:~$ SANE_DEBUG_DLL=1 scanimage -d 
"hpaio:/net/envy_5000_series?ip=192.168.178.41=false" -T
] [sanei_debug] Setting debug level of dll to 1.
] [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.27
] [dll] add_backend: `hpaio' is already there
] [dll] load: dlopen() failed 
(/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1: undefined symbol: _DBG)
] scanimage: open of device 
hpaio:/net/envy_5000_series?ip=192.168.178.41=false failed: Invalid 
argument
=

A few other files in scan/sane/ include a header that defines the _DBG()
macro to call syslog(), but orblite.c doesn't.

What puzzles me is that the call is flagged as undefined in both build
logs (3.20.3+dfsg0-2 and 3.20.5+dfsg0-2) - however, in the old version
the call in the final shared library *has* been replaced by a call to
__syslog_chk(). (Don't want to figure out how that's happening.)

Anyway, resolving that _DBG() invocation in orblite.c should trivially
fix this bug.

Thanks for considering

Jan

Bug#959455: marked as done (fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 22:03:42 +
with message-id 
and subject line Bug#959455: fixed in fakeroot-ng 0.18-4.1
has caused the Debian Bug report #959455,
regarding fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers
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.)


-- 
959455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fakeroot-ng
Version: 0.18-4
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: fakeroot-ng
Source-Version: 0.18-4.1
Done: Sudip Mukherjee 

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

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

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated fakeroot-ng 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 May 2020 21:10:17 +0100
Source: fakeroot-ng
Architecture: source
Version: 0.18-4.1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh 
Changed-By: Sudip Mukherjee 
Closes: 959455
Changes:
 fakeroot-ng (0.18-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove dependency on linux-kernel-headers. (Closes: #959455)
Checksums-Sha1:
 92255f097bf62d63cdb9d5aaf4667b975c0b699e 1809 fakeroot-ng_0.18-4.1.dsc
 ef8b9b390fa6a3fcbbd7caa1ce42fa504d87215c 4576 
fakeroot-ng_0.18-4.1.debian.tar.xz
 d24acff7015db2d26fe4b326848579f383da61f1 5648 
fakeroot-ng_0.18-4.1_amd64.buildinfo
Checksums-Sha256:
 7c320fc331b7dbd01880d7f5ec30bd2ef69bb492717c819c4dfe1c9af696 1809 
fakeroot-ng_0.18-4.1.dsc
 9905ba1c1fd30b6ed311b59add8009d93cd8d81db8084664f866dd8d553c5ec9 4576 
fakeroot-ng_0.18-4.1.debian.tar.xz
 504917ed8b8b34749e446db1eff3a72a01c7fe52500eb85254073882644a56b5 5648 
fakeroot-ng_0.18-4.1_amd64.buildinfo
Files:
 8c3a5261c7a5786b7783c5b1e11daad3 1809 utils extra fakeroot-ng_0.18-4.1.dsc
 73c8c027fcf822fb0f28ede3137a2bd6 4576 utils extra 
fakeroot-ng_0.18-4.1.debian.tar.xz
 dc2f21f55958a1de8beea00730bce7f7 5648 utils extra 
fakeroot-ng_0.18-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAl68ZKUACgkQZR7vsCUn
3xN3NxAAs4aNVXilrBG3cHM2f4ZVpaAJQ2BrEVBh4Bwj7guIpNsb/6pO+xeKILfx
IC4RbdSIjtkA8AO+5MQy9ZThr/R392nNQaTQcebJMVSe8JC/ujqy16BRzWxuunB+
iHkS/OWf0aPg3baHcB6BXNLVZ+nKq8EKn1qtYwwz/HDdwFPF5tzL8UdEZIx1Ty2P
/igptVC21NEK53YYaOsrsLSpf9bJk6NyY05FOR4MfTvSujH+l7eiAuji62UWgaXs
sPGeQvLdMYjwTw9xTREiqfVgO/DlVnpghYV/nJ1QKn+mFeu8Ds86HL2kMzmEgim9
QbnbYicup+g4ItCDBthoqr6AV4Y1ZvkvrX5ZPxfeMXZS1vlzyBkIp01Oq42yd/uC
VnmC1W21eIBvHiakdef4AeMEZfoanQvLnNPOMwlwd2Aq45nqcEfP8Lgt20gZqIqo
3RcGLTl+rt5uofSduT60Ynpb1b3fMtAIxumqs8tpF2DK317afNzUSlVuxYgnSMMM
39C9we6AlABGfQVSi9GuPbWh84GCdNpjWZ0OHC30tN5EX4OGkS3kGQ851KI7bZnW
SxZXemtKOffjEroeA907uYaTst+tp4yoSVVlaZfWUpuM4zcU5emcOLB/tQMpR9Dr
7pf71tiBQiJP3E/voz7Jr2a84n5GuBhXjzJ/fnQ1e/jiLpBPHWA=
=Wphf
-END PGP SIGNATURE End Message ---

Bug#961060: qmail-verify: CVE-2020-3811 CVE-2020-3812

[Salvatore Bonaccorso]

Control: tags -1 + patch

On Tue, May 19, 2020 at 07:30:53PM +0200, Salvatore Bonaccorso wrote:
> Source: netqmail
> Version: 1.06-6.1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 1.06-6
> Control: found -1 1.06-5
> 
> Hi
> 
> See https://www.openwall.com/lists/oss-security/2020/05/19/8 for the
> Qualys advisory covering CVE-2020-3811 and CVE-2020-3812.

debdiff based on the above attached.

Salvatore
diff -u netqmail-1.06/debian/changelog netqmail-1.06/debian/changelog
--- netqmail-1.06/debian/changelog
+++ netqmail-1.06/debian/changelog
@@ -1,3 +1,10 @@
+netqmail (1.06-6.2) unstable; urgency=high
+
+  * Address CVE-2005-1513, CVE-2005-1514, CVE-2005-1515, CVE-2020-3811 and
+CVE-2020-3812 (Closes: #961060)
+
+ -- Salvatore Bonaccorso   Wed, 20 May 2020 22:23:21 +0200
+
 netqmail (1.06-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- netqmail-1.06.orig/debian/diff/0004-Remote-Code-Execution-in-qmail.diff
+++ netqmail-1.06/debian/diff/0004-Remote-Code-Execution-in-qmail.diff
@@ -0,0 +1,515 @@
+From e80dc4ad2b0ee51315e336253606c0effdd0f117 Mon Sep 17 00:00:00 2001
+From: Qualys Security Advisory 
+Date: Tue, 19 May 2020 10:05:06 -0700
+Subject: [PATCH] Remote Code Execution in qmail (CVE-2005-1513)
+
+Qualys Security Advisory
+
+15 years later: Remote Code Execution in qmail (CVE-2005-1513)
+
+
+Contents
+
+
+Summary
+Analysis
+Exploitation
+qmail-verify
+- CVE-2020-3811
+- CVE-2020-3812
+Mitigations
+Acknowledgments
+Patches
+
+
+Summary
+
+
+TLDR: In 2005, three vulnerabilities were discovered in qmail but were
+never fixed because they were believed to be unexploitable in a default
+installation. We recently re-discovered these vulnerabilities and were
+able to exploit one of them remotely in a default installation.
+
+
+
+In May 2005, Georgi Guninski published "64 bit qmail fun", three
+vulnerabilities in qmail (CVE-2005-1513, CVE-2005-1514, CVE-2005-1515):
+
+http://www.guninski.com/where_do_you_want_billg_to_go_today_4.html
+
+Surprisingly, we re-discovered these vulnerabilities during a recent
+qmail audit; they have never been fixed because, as stated by qmail's
+author Daniel J. Bernstein (in https://cr.yp.to/qmail/guarantee.html):
+
+"This claim is denied. Nobody gives gigabytes of memory to each
+qmail-smtpd process, so there is no problem with qmail's assumption
+that allocated array lengths fit comfortably into 32 bits."
+
+Indeed, the memory consumption of each qmail-smtpd process is severely
+limited by default (by qmail-smtpd's startup script); for example, on
+Debian 10 (the latest stable release), it is limited to roughly 7MB.
+
+Unfortunately, we discovered that these vulnerabilities also affect
+qmail-local, which is reachable remotely and is not memory-limited by
+default (we investigated many qmail packages, and *all* of them limit
+qmail-smtpd's memory, but *none* of them limits qmail-local's memory).
+
+As a proof of concept, we developed a reliable, local and remote exploit
+against Debian's qmail package in its default configuration. This proof
+of concept requires 4GB of disk space and 8GB of memory, and allows an
+attacker to execute arbitrary shell commands as any user, except root
+(and a few system users who do not own their home directory). We will
+publish our proof-of-concept exploit in the near future.
+
+About our new discovery, Daniel J. Bernstein issues the following
+statement:
+
+"https://cr.yp.to/qmail/guarantee.html has for many years mentioned
+qmail's assumption that allocated array lengths fit comfortably into
+32 bits. I run each qmail service under softlimit -m12345678, and I
+recommend the same for other installations."
+
+Finally, we also discovered two minor vulnerabilities in qmail-verify (a
+third-party qmail patch that is included in, for example, Debian's qmail
+package): CVE-2020-3811 (a mail-address verification bypass), and
+CVE-2020-3812 (a local information disclosure).
+
+
+Analysis
+
+
+We decided to exploit Georgi Guninski's vulnerability "1. integer
+overflow in stralloc_readyplus" (CVE-2005-1513). There are, in fact,
+four potential integer overflows in stralloc_readyplus; three in the
+GEN_ALLOC_readyplus() macro (which generates the stralloc_readyplus()
+function), at line 21 (n += x->len), line 23 (x->a = base + n + ...),
+and line 24 (x->a * sizeof(type)):
+

Processed: Re: Bug#961060: qmail-verify: CVE-2020-3811 CVE-2020-3812

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #961060 [src:netqmail] qmail-verify: CVE-2020-3811 CVE-2020-3812
Added tag(s) patch.

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

Processed: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

[Debian Bug Tracking System]

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

> tags 961144 +moreinfo
Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for 
bacula-director.service failed
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#960892 closed by Debian FTP Masters (reply to to...@debian.org (Dr. Tobias Quathamer)) (Bug#960892: fixed in po4a 0.59-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #960892 {Done: to...@debian.org (Dr. Tobias Quathamer)} [po4a] po4a: 
--srcdir ignored by [po_directory]
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions po4a/0.59-1.
> notfixed -1 0.59-1
Bug #960892 [po4a] po4a: --srcdir ignored by [po_directory]
Ignoring request to alter fixed versions of bug #960892 to the same values 
previously set

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

Bug#960892: closed by Debian FTP Masters (reply to to...@debian.org (Dr. Tobias Quathamer)) (Bug#960892: fixed in po4a 0.59-1)

[Axel Beckert]

Control: reopen -1
Control: notfixed -1 0.59-1

Hi,

Debian Bug Tracking System wrote:
>  - po4a tool: Fix --srcdir handling. This bug was breaking the build
>of several packages, including dpkg. (Closes: #960892)

I'm sorry to report, but this is not fixed for aptitude.

> previously when building aptitude's documentation, it sufficed to
> declare
> 
>   [po_directory] po4a/po
> 
> in doc/po4a/po4a.cfg and then calling from the out-of-tree build
> directory in e.g. "build/doc/de/"
> 
>   /usr/bin/po4a --translate-only=de/manpage.xml --srcdir=../../../doc 
> --destdir=../../doc ../../../doc/po4a/po4a.cfg
> 
> but since recently, this fails with the IMHO not very helpful error
> message:
> 
>   ../../../doc/po4a/po4a.cfg:1: no PO files found in po4a/po

The error now looks slightly different, though:

  ../../../doc/po4a/po4a.cfg:1: no PO files found in ../../doc/po4a/po


So for me it looks as this "../../doc/po4a/po" is now prefixed with
what I gave as --destdir, but it should have been what I gave as
--srcdir.

Here's the requested run with more verbose settings:

[…]ptitude/build/doc/de → /usr/bin/po4a -d -v --translate-only=de/manpage.xml 
--srcdir=../../../doc --destdir=../../doc ../../../doc/po4a/po4a.cfg
cmd=[po_directory]; po4a/po /
../../../doc/po4a/po4a.cfg:1: no PO files found in ../../doc/po4a/po
cmd=[po4a_alias:docbook]; docbook / opt:"-M utf-8 -o 
untranslated="
cmd=[po4a_alias:svg]; xml / opt:"-M utf-8 -k 0"
cmd=[type: docbook]; en/aptitude.xml / $lang:$lang/aptitude.xml opt:"-k 0"
cmd=[type: docbook]; en/manpage.xml / $lang:$lang/manpage.xml opt:"-k 0"
cmd=[type: svg]; en/images/safety-cost-level-diagram.svg / 
$lang:$lang/images/safety-cost-level-diagram.svg
'po4a_paths' is not defined in the configuration file. Where are the POT and PO 
files?

HTH!

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#959138: nipy: resolve nipy autopkgtest failure due to numpy testing decorators

[Matthieu Clemenceau]

Source: nipy
Followup-For: Bug #959138
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

Dear Maintainer,

While working on numpy proposed-migration for groovy, I realize nipy
autopkgtest was failing. It appears that numpy changed the pass to the
module decorators from numpy.testing.decorators to
numpy.testing._private.decorators.

In Ubuntu, the attached patch was applied allowing nipy to pass autopkg
test and migrate from groovy-proposed to groovy.

The Changelog below was added to nipy-0.4.2-3ubuntu1
  * Resolved test failure due to numpy 1:1.18.4-1. (Closes: #959138)


Thanks for considering the patch.


-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-29-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Description: Fix Autopkgtest failure caused by the new numpy 1:1.18.4-1
Author: Matthieu Clemenceau 
Origin: vendor
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959138#5
Forwarded: yes
Last-Update: 2020-05-15
--- a/nipy/algorithms/clustering/tests/test_vmm.py
+++ b/nipy/algorithms/clustering/tests/test_vmm.py
@@ -13,7 +13,7 @@
 select_vmm_cv)
 
 from nose.tools import assert_true, assert_equal
-from numpy.testing import decorators
+from numpy.testing._private import decorators
 
 from nibabel.optpkg import optional_package
 
--- a/nipy/algorithms/diagnostics/tests/test_screen.py
+++ b/nipy/algorithms/diagnostics/tests/test_screen.py
@@ -23,7 +23,8 @@
 from nose.tools import (assert_true, assert_false, assert_equal, assert_raises)
 
 from numpy.testing import (assert_array_equal, assert_array_almost_equal,
-   assert_almost_equal, decorators)
+   assert_almost_equal)
+from numpy.testing._private import decorators
 
 from nipy.testing import funcfile
 from nipy.testing.decorators import needs_mpl_agg
--- a/nipy/fixes/numpy/testing/nosetester.py
+++ b/nipy/fixes/numpy/testing/nosetester.py
@@ -21,7 +21,7 @@
 
 Examples
 
->>> from numpy.testing import nosetester
+>>> from numpy.testing._private import nosetester
 >>> nosetester.get_package_name('nonsense')
 'numpy'
 
--- a/nipy/testing/decorators.py
+++ b/nipy/testing/decorators.py
@@ -8,7 +8,7 @@
 from __future__ import print_function
 from __future__ import absolute_import
 
-from numpy.testing.decorators import *
+from numpy.testing._private.decorators import *
 
 from nipy.utils import templates, example_data, DataError
 
--- a/nipy/tests/test_scripts.py
+++ b/nipy/tests/test_scripts.py
@@ -19,7 +19,9 @@
 from nose.tools import assert_true, assert_false, assert_equal, assert_raises
 
 from ..testing import funcfile
-from numpy.testing import decorators, assert_almost_equal
+
+from numpy.testing._private import decorators
+from numpy.testing import assert_almost_equal
 
 from nipy.testing.decorators import make_label_dec
 

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

[Ross Vandegrift]

On Thu, May 07, 2020 at 07:52:31PM +0200, Julien Cristau wrote:
> On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote:
> > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote:
> > > This use of Provides is not acceptable.  The systemctl package does not
> > > in any way provide the same functionality / interfaces as the systemd
> > > package, and as such it does not get to pretend that it does and cause
> > > problems to other packages.
> > 
> > I have to challenge that. "systemctl" provides enough functionality to 
> > replace "systemd" inside application containers. Therefore there are 
> > situations where "Provides: systemd" is justified.
> > 
> That's not what "Provides" means though.  What you're saying is
> "systemctl provides a subset of the systemd package's functionality".
> That's not good enough.  Provides is much stronger than "there are cases
> where this might be enough", and there's more to systemd than systemctl.

Indeed- packages that Build-Depend on systemd need a way to express that
fact.  experimental builds use apt-cudf, which now sees systemctl as a
more attractive solution:
https://buildd.debian.org/status/package.php?p=e17=experimental

Ross

Processed: Partially solved

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian
Bug #960660 [src:cyrus-imapd] cyrus-imapd: Test failure on armhf (at least on 
armv8)
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'

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

Bug#960658: Partially solved

[Xavier]

Control: severity -1 important

This bug is partially  fixed in version 3.2.0-5. Keeping it opened due to:
 * some unimportant tests still fail (disabled in 3.2.0-5)
 * build still fail for hppa and sparc64 [1]

[1]: https://buildd.debian.org/status/logs.php?pkg=cyrus-imapd=3.2.0-5

Bug#961148: libgraphics-colorobject-perl: broken by new libgraphics-colornames-perl

[Niko Tyni]

Package: libgraphics-colorobject-perl
Version: 0.5.0-7.1
Severity: grave
Tags: bullseye sid
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=127300

Graphics::ColorObject needs Graphics::ColorNames::HTML, which was recently
dropped from the libgraphics-colornames-perl package in Debian.

 % perl -e 'use Graphics::ColorObject'
 Cannot load color naming scheme module Graphics::ColorNames::HTML at 
/usr/share/perl5/Graphics/ColorObject.pm line 1902.
 Compilation failed in require at -e line 1.

Graphics::ColorNames::HTML is now available separately on CPAN, with a
deprecation notice pointing users to Graphics::ColorNames::WWW (packaged
in Debian as libgraphics-colornames-www-perl) instead.

So Graphics::ColorObject needs to adapt, or Graphics::ColorNames::HTML
needs to be packaged separately despite the deprecation.

Also, libgraphics-colornames-perl should add a Breaks entry for the
versions of libgraphics-colorobject-perl it broke.
-- 
Niko Tyni   nt...@debian.org

Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl

[Niko Tyni]

Package: libcolor-calc-perl
Version: 1.074-2
Severity: grave
Tags: bullseye sid
X-Debbugs-Cc: libgraphics-colornames-p...@packages.debian.org

Color::Calc uses Graphics::ColorNames::HTML, which was recently dropped
from the libgraphics-colornames-perl package in Debian.

Graphics::ColorNames::HTML is now available separately on CPAN, with a
deprecation notice pointing users to Graphics::ColorNames::WWW (packaged
in Debian as libgraphics-colornames-www-perl) instead.

So Color::Calc needs to adapt, or Graphics::ColorNames::HTML needs to be
packaged separately despite the deprecation.

Also, libgraphics-colornames-perl should add a Breaks entry for the
versions of libcolor-calc-perl it broke.
-- 
Niko Tyni   nt...@debian.org

Bug#961144: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

[Paul Gevers]

Source: ucf, bacula
Control: found -1 ucf/3.0039
Control: found -1 bacula/9.6.3-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ucf the autopkgtest of bacula fails in testing
when that autopkgtest is run with the binary packages of ucf from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
ucffrom testing3.0040
bacula from testing9.6.3-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 ucf 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=ucf

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bacula/555/log.gz
autopkgtest [10:36:26]: test backup-test-pgsql: [---
+ apt-get -y install debconf-utils
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  debconf-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 57.1 kB of archives.
After this operation, 108 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main amd64 debconf-utils all
1.5.74 [57.1 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 57.1 kB in 0s (745 kB/s)
Selecting previously unselected package debconf-utils.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 15551 files and directories currently installed.)
Preparing to unpack .../debconf-utils_1.5.74_all.deb ...
Unpacking debconf-utils (1.5.74) ...
Setting up debconf-utils (1.5.74) ...
+ awk '$3=="password"{print}'
+ debconf-set-selections
+ debconf-get-selections
+ for pkg in bacula-director-mysql bacula-director-pgsql
++ dpkg-query --showformat '${db:Status-Status}' -W bacula-director-mysql
+ pkg_status=not-installed
+ '[' not-installed = installed ']'
+ for pkg in bacula-director-mysql bacula-director-pgsql
++ dpkg-query --showformat '${db:Status-Status}' -W bacula-director-pgsql
+ pkg_status=installed
+ '[' installed = installed ']'
+ echo 'bacula-director-pgsql bacula-director-pgsql/dbconfig-reinstall
boolean true'
+ debconf-set-selections
+ DEBIAN_FRONTEND=noninteractive
+ dpkg-reconfigure bacula-director-pgsql
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-pgsql.conf
creating postgres user bacula:  already exists.
resetting password:  success.
dbconfig-common: dumping pgsql database bacula to
/var/tmp/bacula-director-pgsql.bacula.2020-05-20-10.36.pgsql.e6nhYl.
dbconfig-common: dropping old pgsql database bacula.
dropping database bacula: success.
verifying database bacula was dropped: success.
creating database bacula: success.
verifying database bacula exists: success.
populating database via administrative sql...  done.
populating database via sql...  done.
dbconfig-common: flushing administrative password
+ echo 'start testing ... '
start testing ...
+ echo 'USER: root'
USER: root
+ DBTYPE=pgsql
+ echo 'DBTYPE: pgsql'
DBTYPE: pgsql
+ '[' pgsql = pgsql ']'
+ echo '- installing packages ---'
- installing packages ---
+ apt-get -y install bacula bacula-director-pgsql
Reading package lists...
Building dependency tree...
Reading state information...
bacula is already the newest version (9.6.3-1).
bacula-director-pgsql is already the newest version (9.6.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo '- configuring Bacula daemons ---'
- configuring Bacula daemons ---
+
FILECHGRDIR=/tmp/autopkgtest-lxc.zc_04wyr/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+
RESTOREDIR=/tmp/autopkgtest-lxc.zc_04wyr/downtmp/autopkgtest_tmp/bacula-restores
+ mkdir -p
/tmp/autopkgtest-lxc.zc_04wyr/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+ chown -R bacula:tape
/tmp/autopkgtest-lxc.zc_04wyr/downtmp/autopkgtest_tmp/bacula-sd/filechgr
+ sed -i

Processed: ucf breaks bacula autopkgtest: Job for bacula-director.service failed

[Debian Bug Tracking System]

Processing control commands:

> found -1 ucf/3.0039
Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for 
bacula-director.service failed
Marked as found in versions ucf/3.0039.
> found -1 bacula/9.6.3-1
Bug #961144 [src:ucf, src:bacula] ucf breaks bacula autopkgtest: Job for 
bacula-director.service failed
Marked as found in versions bacula/9.6.3-1.

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

Bug#961088: bug confirmed

[Hans-Georg Rist]

Hi,

I have the same problem with an HP Officejet 7310 AIO:

sane-find-scanner reports:
"found USB scanner (vendor=0x03f0 [HP], product=0x4211 [Officejet 7300
series]) at libusb:002:012"

but "scanimage -L" fails:
"No scanners were identified."

Unfortunately, I wasn't able to downgrade to 3.20.3+dfsg0-2. There are
(too) many dependencies, and I couldn't find the 3.20.3 packages on the
Debian servers).

A fix or a workaround would be very much appreciated.

Regards and thanks for your efforts,
HG

Bug#961126: marked as done (fig2dev fails autopkg test with stderr output on 32bit archs)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 16:49:03 +
with message-id 
and subject line Bug#961126: fixed in fig2dev 1:3.2.7b-4
has caused the Debian Bug report #961126,
regarding fig2dev fails autopkg test with stderr output on 32bit archs
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.)


-- 
961126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fig2dev
Version: 1:3.2.7b-3
Severity: serious
Tags: sid bullseye patch

fig2dev fails autopkg test with stderr output on 32bit archs

make  test1
make[1]: Entering directory 
'/tmp/autopkgtest.No5cFl/build.GqQ/src/fig2dev/tests'
gcc -DHAVE_CONFIG_H -I. -I../..  -DI18N_DATADIR="\"/usr/share/fig2dev/i18n\""
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/tmp/autopkgtest.No5cFl/build.GqQ/src=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o test1.o test1.c
test1.c: In function ‘main’:
test1.c:60:33: warning: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘size_t’ {aka ‘unsigned int’} [-Wformat=]
   60 |   printf("File path too long, %ld > %d.\n", n + 10, BUFSIZ);
  |   ~~^   ~~
  | | |
  | long int  size_t {aka unsigned int}
  |   %d
gcc  -g -O2 -fdebug-prefix-map=/tmp/autopkgtest.No5cFl/build.GqQ/src=. 
-fstack-prote

patch at
http://launchpadlibrarian.net/480599135/fig2dev_1%3A3.2.7b-3_1%3A3.2.7b-3ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: fig2dev
Source-Version: 1:3.2.7b-4
Done: Roland Rosenfeld 

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

Debian distribution maintenance software
pp.
Roland Rosenfeld  (supplier of updated fig2dev 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, 20 May 2020 18:26:07 +0200
Source: fig2dev
Architecture: source
Version: 1:3.2.7b-4
Distribution: unstable
Urgency: medium
Maintainer: Roland Rosenfeld 
Changed-By: Roland Rosenfeld 
Closes: 961126
Changes:
 fig2dev (1:3.2.7b-4) unstable; urgency=medium
 .
   * debian/tests/fig2dev-testsuite: Avoid suppressing output, but do not
 handle build warnings as test fails.
   * Update standards version to 4.5.0, no changes needed.
   * Rename gitlab-ci.yml to salsa-ci.yml.
   * Update debian/watch to version=4 and optimize regex.
   * 33_test1_32bit: Fix autopkg test warning on 32bit architectures.
 Thanks to Matthias Klose (Closes: #961126).
   * Update to debhelper 13.
Checksums-Sha1:
 968d1c75368be2c5d4c3d2cad801f405691bb1f1 2232 fig2dev_3.2.7b-4.dsc
 067cb37b0dde5367455a61e9f6549b3151003f16 229088 fig2dev_3.2.7b-4.debian.tar.xz
 7cdd4f500e0bd2772d772420fbad75b8e70b6a1e 9031 fig2dev_3.2.7b-4_source.buildinfo
Checksums-Sha256:
 4fa2820241ba88381121936743e75d8301e6a17dc9fa13fab3f359bc3b6b0e41 2232 
fig2dev_3.2.7b-4.dsc
 0d41366d7831692371c9e8bc1f298efb7e5c27b14e596a52a8fc4715078a2bda 229088 
fig2dev_3.2.7b-4.debian.tar.xz
 181eb1bd5bc7339ceebc90a1b2ae5ad0b6210cfc876025a60dca5528fdd3a79e 9031 
fig2dev_3.2.7b-4_source.buildinfo
Files:
 71f3a56eaf571b62ed3a6b36824380d1 2232 graphics optional fig2dev_3.2.7b-4.dsc
 ef030063f85972b3f9ef9de2fe389881 229088 graphics optional 
fig2dev_3.2.7b-4.debian.tar.xz
 e7c903115f81303a6c1957ec916f28ad 9031 graphics optional 
fig2dev_3.2.7b-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAl7FWtQACgkQAnE7z8pU
ELK+sA//XQlkOHpqTxxOaZ5OiiEqZCrrB1ZhZk84pbyBkRltiIgt/LEo64EjocH0
7Gl3rc65g1cFbXkpfVZejgrutzhKxVc+VDs59/TZuFxg7gur7a2PuWESbUm93yTm
6hc0bvtwsxDTS/8+zz2o+s2YeuBhpt48/qMR+yZWUXkeQsDAndvANEDszWbw9ToZ
xArJQqfKl/r9ox91awZRjNHoXwCGXnEvi7NZQw6zh4Rw7aUkb5bSWJzf8ypc2tp4
PExnqBb7MYL6uO5tO/7jS17ezhvRdBLzKCiDr9ju1JTbXjQyDt1+/lSdxPb5AU+4
q9PCkNGsHFJzZTQduUoh3DC3W4qPRlghPZg0wkGXb9qGGx4y3n8TuhsHA4i4+K27
iWfeYa6yDTmbKHF7CZGwz25kZ50KGCW7b9I+3/Upq7rNL0DPJU7qxhU7YoE8C2Dq

Processed: bug 961126 is forwarded to https://sourceforge.net/p/mcj/tickets/94/

[Debian Bug Tracking System]

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

> forwarded 961126 https://sourceforge.net/p/mcj/tickets/94/
Bug #961126 [src:fig2dev] fig2dev fails autopkg test with stderr output on 
32bit archs
Set Bug forwarded-to-address to 'https://sourceforge.net/p/mcj/tickets/94/'.
> thanks
Stopping processing here.

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

Bug#960876: marked as done (bcalm: autopkgtest regression: python: command not found)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 16:18:47 +
with message-id 
and subject line Bug#960876: fixed in bcalm 2.2.2-1.1
has caused the Debian Bug report #960876,
regarding bcalm: autopkgtest regression: python: command not found
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.)


-- 
960876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bcalm
Version: 2.2.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of bcalm the autopkgtest of bcalm fails in testing
when that autopkgtest is run with the binary packages of bcalm from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
bcalm  from testing2.2.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Seems like you
missed that python now needs to be called with a version: python2.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bcalm/5517318/log.gz

Finding links between unitigs   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 0   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 1   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 2   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 3   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 4   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (2kmers/2extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 5   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 6   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 1 pass 7   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
step 2 (0kmers/0extremities)19:07:17 memory
[current, maxRSS]: [  80,   80] MB
gathering links from disk   19:07:17 memory
[current, maxRSS]: [  80,   80] MB
Done finding links between unitigs  19:07:17 memory
[current, maxRSS]: [  80,   80] MB
simple_test.sh: line 9: python: command not found
test KO



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bcalm
Source-Version: 2.2.2-1.1
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated bcalm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 May 2020 08:51:35 -0700
Source: bcalm
Architecture: source
Version: 2.2.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian 

Bug#961120: marked as done (nulib2 ftbfs on s390x (failing tests), built before)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 16:04:24 +
with message-id 
and subject line Bug#961120: fixed in nulib2 3.1.0-4
has caused the Debian Bug report #961120,
regarding nulib2 ftbfs on s390x (failing tests), built before
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.)


-- 
961120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nulib2
Version: 3.1.0-3
Severity: serious
Tags: sid bullseye

nulib2 ftbfs on s390x (failing tests), built before:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nufxlib/samples/test-basic
ERROR: kNuAttrNumRecords 12884901888 vs 3
Using NuFX library v3.1.0, built on or after
  May 19 2020 with [Debian]

... starting tests
... open zero-byte existing
... add 'bytes' record
... add 'English' record
... add 'long' record
... checking contents
... reopening archive read-only
... checking contents
... verifying CRCs
... extracting files
... reopening archive read-write
... checking contents
... deleting first and last
... tests ended, FAILURE
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: nulib2
Source-Version: 3.1.0-4
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated nulib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 May 2020 17:41:18 +0200
Source: nulib2
Architecture: source
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 961120
Changes:
 nulib2 (3.1.0-4) unstable; urgency=medium
 .
   * Fix the tests on 64-bit big-endian platforms. Closes: #961120.
Checksums-Sha1:
 e6bfdb260858f59020e478612834006285d98691 1808 nulib2_3.1.0-4.dsc
 f65463cf8aaef75127dbcfb4de245cba5a9c4fb8 5112 nulib2_3.1.0-4.debian.tar.xz
 6dac71ce5256c04a322013f19c9db230abbd8345 6028 nulib2_3.1.0-4_source.buildinfo
Checksums-Sha256:
 84f6499b51f519e1659e990c13676307a0bc983a872ca9e144aa90f8b870021c 1808 
nulib2_3.1.0-4.dsc
 752fc41dc6513062a6efd6f8726fd1b62b94c8d51c43fee4f78319833152b73c 5112 
nulib2_3.1.0-4.debian.tar.xz
 3c2d9ec8cf38ea08c5004336484abccfdb6ce4f50f8e733d62fef03de98f6fbc 6028 
nulib2_3.1.0-4_source.buildinfo
Files:
 f82e83affa39a78d23677d3086ce0c51 1808 otherosfs optional nulib2_3.1.0-4.dsc
 be693242224d1a27019098de1b0a8574 5112 otherosfs optional 
nulib2_3.1.0-4.debian.tar.xz
 f65b84954fc97394c0cd260c51918ea1 6028 otherosfs optional 
nulib2_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl7FT7EACgkQgNMC9Yht
g5wvYA/+I0r4nILmWLboXZzX7votWCokTvjFLL4lqCFRmfw5POxkcjwjXulHZ7NJ
RTyJYsUFGMQeedVe5ZmfmRFJfgTBnDb9yRfrcnb19r3CYs70SQEk5MrI0nhG2KJi
TOw57LG2NtB1hy1gXcpdzgC+T1uaP6slSDHXhWlLkYmknaB2xqeFW4pmt4AW4GMh
J87Cv1n8BJ1ZfH5SduJuUnEejMu2YYjydH86qJvkw6r9OTt0h0jcgGZC854c21gf
a47mugWC/O4J29uJw2Zf/EGzP0HYBFBcMf105t/wnFJyyVcG6g4RglQkWYIZefuE
3NfNH8kf+KvGUo+0K4IIodZuYdrOXF5ZnvKzninxv/fZZqyLiyoNPCKbPIhkVXuh
UgEQdTcP4AGGtCcg61cxmBEUfrx2JPvMZC8lwgg1vci/JS0FPsv8fWV+cSD+lP1q
mJftCPw2gHbbFb4RbFulidb/QbodL+Wch43v5rmr5ce5bLjRq+uqLjdAE74H/qZq
NOHCnucBMN5xJzWBPhsRBLFo+Wc/hpT+ludbHH9c9/UP/E3yQqrVYhjEFwV1czQ1
iBPphFYMfXaL9HAF0yWyc4jF3aeOGM+wcLAAMWDPx7NkK27j83LpF54fIgnwuHsh
WZ5v/aFPvVKmYa9fhxFWXSKdEhKn6YbLhbQSjcEoairspJtTs7g=
=9mZx
-END PGP SIGNATURE End Message ---

Processed: bcalm: diff for NMU version 2.2.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 960876 + patch
Bug #960876 [src:bcalm] bcalm: autopkgtest regression: python: command not found
Added tag(s) patch.

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

Bug#960876: bcalm: diff for NMU version 2.2.2-1.1

[Stefano Rivera]

Control: tags 960876 + patch

Dear maintainer,

I've prepared an NMU for bcalm (versioned as 2.2.2-1.1). The diff
is attached to this message.

Regards.

SR
diff -Nru bcalm-2.2.2/debian/bcalm.install bcalm-2.2.2/debian/bcalm.install
--- bcalm-2.2.2/debian/bcalm.install	2020-05-05 12:21:17.0 -0700
+++ bcalm-2.2.2/debian/bcalm.install	2020-05-20 08:51:23.0 -0700
@@ -1,6 +1,5 @@
-debian/missing-sources/compare_fasta.py usr/share/doc/bcalm/test
-debian/missing-sources/reference.fasta usr/share/doc/bcalm/test
-debian/missing-sources/simple_test.sh usr/share/doc/bcalm/test
 example/* usr/share/doc/bcalm/test
 test/* usr/share/doc/bcalm/test
 debian/missing-sources/compare_fasta.py usr/share/doc/bcalm/test
+debian/missing-sources/reference.fasta usr/share/doc/bcalm/test
+debian/missing-sources/simple_test.sh usr/share/doc/bcalm/test
diff -Nru bcalm-2.2.2/debian/changelog bcalm-2.2.2/debian/changelog
--- bcalm-2.2.2/debian/changelog	2020-05-05 12:21:17.0 -0700
+++ bcalm-2.2.2/debian/changelog	2020-05-20 08:51:35.0 -0700
@@ -1,3 +1,11 @@
+bcalm (2.2.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Overwrite upstream's simple_test with our fixed version, so we test with
+Python 3, again. And depend on it for the test. (Closes: #960876)
+
+ -- Stefano Rivera   Wed, 20 May 2020 08:51:35 -0700
+
 bcalm (2.2.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru bcalm-2.2.2/debian/tests/control bcalm-2.2.2/debian/tests/control
--- bcalm-2.2.2/debian/tests/control	2020-05-05 12:21:03.0 -0700
+++ bcalm-2.2.2/debian/tests/control	2020-05-20 08:51:33.0 -0700
@@ -1,3 +1,3 @@
 Tests: run-unit-test
-Depends: @
+Depends: @, python3
 Restrictions: allow-stderr

Bug#960773: gr-gsm: FTBFS on s390x

[Adrian Bunk]

Control: retitle -1 gr-gsm FTBFS on big endian

On Sat, May 16, 2020 at 03:09:07PM +0200, Sebastian Ramacher wrote:
> Source: gr-gsm
> Version: 0.42.2.20200214-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> gr-gsm failed to build on s390x:
> https://buildd.debian.org/status/fetch.php?pkg=gr-gsm=s390x=0.42.2.20200214-1=1589387991=0

It also FTBFS on hppa/powerpc/ppc64, this is FTBFS on big endian.

The options forward are:
1. try to fix it for big endian with likely 0 users, or
2. submit a bug against ftp.debian.org asking for removal of the
   stale s390x binary, with lowering of the severity of this bug

> Cheers

cu
Adrian

Processed: Re: Bug#960773: gr-gsm: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gr-gsm FTBFS on big endian
Bug #960773 [src:gr-gsm] gr-gsm: FTBFS on s390x
Changed Bug title to 'gr-gsm FTBFS on big endian' from 'gr-gsm: FTBFS on s390x'.

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

Bug#947827: marked as done (Missing symbols in -lblas ?)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 15:18:48 +
with message-id 
and subject line Bug#947827: fixed in atlas 3.10.3-10
has caused the Debian Bug report #947827,
regarding Missing symbols in -lblas ?
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.)


-- 
947827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatlas3-base
Version: 3.10.3-9

I tried to work on the scilab package, but couldn't get very far : for
some reason, the configure script was failing to detect the umfpack
library. But looking in config.log, I found out the reason was that the
BLAS used is atlas, and linking to it gives many undefined references :


configure:30844: gcc -o conftest -g -O2 -fdebug-prefix-
map=/home/jpuydt/Debian/build/scilab-6.0.2=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-
z,relro -Wl,-z,now -Wl,--no-as-needed conftest.c -lumfpack  -lamd
-lblas -lpthread -ldl -lcurses  -lm -lm >&5
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dgeset'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dgemoveT'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sger'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cgeset'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dtrscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cgemaxnrm'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zgeru'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cgemoveT'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dgemaxnrm'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zcplxdivide'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sgemaxnrm'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_csqtrans'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zGetNB'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dGetNB'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dger'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_ztrscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_ssqtrans'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_ccplxdivide'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dgezero'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cgeru'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sgeset'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sgezero'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_xerbla'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_ctrscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zgemaxnrm'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cgezero'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zgezero'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dgescal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_ccplxinvert'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zgemoveT'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_dsqtrans'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zgeset'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_cGetNB'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_sGetNB'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_strscal'
/usr/bin/ld: /lib/x86_64-linux-gnu/liblapack.so.3: undefined reference
to `ATL_zcplxinvert'
/usr/bin/ld: 

Bug#959619: urwid: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13

[Matthias Klose]

I see this on the Launchpad buildds, building the package. Adding a build
dependency on locales-all fixes this.  I assume that the same dependency needs
to be added for the autopkg test.

Processed: Re: Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)

[Debian Bug Tracking System]

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

> reopen 960327
Bug #960327 {Done: Luigi Gangitano } [src:squid] squid: 
autopkgtest regression: test_daemons (__main__.BasicTest)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions squid/4.11-5.
> thanks
Stopping processing here.

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

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

[Mauro Dionisi]

When I upgraded to buster I disabled deb-multimedia and I forgot to enable
it again.

After enabling deb-multimedia repository for buster and upgrading the
packages, mkvtoolnix-gui worked again.

Thanks for the advice.

Regards

--
Mauro

On Wed, May 20, 2020, 04:35 Phil Wyett  wrote:

> On Wed, 2020-05-20 at 09:28 +0200, Bernhard Übelacker wrote:
> > > On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote:
> > > > Versions of packages mkvtoolnix-gui depends on:
> > > > ii  libebml4v5 1:1.3.9-dmo0+deb9u1
> > > > ii  libmatroska6v5 1:1.4.5-dmo1
> >
> > Hello,
> > might this be related to the above packages being
> > from the debian multimedia repository?
> >
> > Could the issue resolve if these packages get installed
> > in the buster version?
> >
> > Kind regards,
> > Bernhard
> >
>
> I did not spot the presence of the dmo packages.
>
> This app works correctly with Debian buster versions of the packages.
>
> Regards
>
> Phil
>
> --
>
> *** Playing the game for the games sake. ***
>
> WWW: https://kathenas.org
>
> Twitter: @kathenasorg
>
> IRC: kathenas
>
> GPG: 724AA9B52F024C8B
>
>

Bug#961131: freecad: autopkgtest regression with opencascade 7.4

[Graham Inggs]

Source: freecad
Version: 0.18.4+dfsg2-2
Tags: patch
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Freecad fails its autopkgtests with opencascade 7.4 [1]:

testTaperedHole (PartDesignTests.TestHole.TestHole) ... FAIL

The attached patch is applied in Ubuntu.

Regards
Graham


[1] https://ci.debian.net/packages/f/freecad/
Description: partdesign: fix failing tapered hole test
 The given parameters return an invalid shape. This fails with occt7.4 but
 doesn't with occt7.3. If the angle is 45 degree the cone is
 self-intersecting as Hole.Depth > Hole.Diameter/2. Changing the 
 Hole.TaperedAngle to 60 degree solves this issue.
Author: lorenz 
Last-Update: 2020-05-03

--- a/src/Mod/PartDesign/PartDesignTests/TestHole.py
+++ b/src/Mod/PartDesign/PartDesignTests/TestHole.py
@@ -67,7 +67,7 @@
 def testTaperedHole(self):
 self.Hole.Diameter = 6
 self.Hole.Depth = 5
-self.Hole.TaperedAngle = 45
+self.Hole.TaperedAngle = 60
 self.Hole.ThreadType = 0
 self.Hole.HoleCutType = 0
 self.Hole.DepthType = 0

Bug#906870: marked as done (xul-ext-certificatepatrol no longer works with firefox-esr 60)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 13:39:05 +
with message-id 
and subject line Bug#960959: Removed package(s) from unstable
has caused the Debian Bug report #906870,
regarding xul-ext-certificatepatrol no longer works with firefox-esr 60
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.)


-- 
906870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-certificatepatrol
Version: 2.0.14-5
Severity: serious

XUL addons are no longer supported.

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.
--- End Message ---
--- Begin Message ---
Version: 2.0.16-1+rm

Dear submitter,

as the package certificatepatrol has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/960959

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)

[Sergio Durigan Junior]

reopen 960327
thanks

On Saturday, May 16 2020, Luigi Gangitano wrote:

> Hi Sergio,
>
>> On 14 May 2020, at 05:42, Sergio Durigan Junior  wrote:
>> 
>> Here's a patch that fixes the issue above.
>> 
>> Please note that even after fixing this specific issue, I still see
>> another failure with test_zz_apparmor.  I've posted a merge request to
>> also fix this problem here:
>> 
>>  https://salsa.debian.org/squid-team/squid/-/merge_requests/12 
>> 
>
>
> Thanks for looking into it. I’ve merged your patches and will upload shortly.

Hi Luigi,

I think there's been a confusion here :-).  The MR on salsa does *not*
fix this bug: it was meant to fix another apparmor bug I had found while
testing the package.  I attached the fix to this specific bug here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960327;msg=10

I can submit it as an MR as well, if you want.  Currently, the
autopkgtest is still failing.

Thanks, and sorry if this wasn't clear in my initial message.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#961120: nulib2 ftbfs on s390x (failing tests), built before

[Stephen Kitt]

Le 20/05/2020 13:02, Matthias Klose a écrit :

nulib2 ftbfs on s390x (failing tests), built before:


Thanks, the tests fail on all 64-bit big-endian platforms:

ERROR: kNuAttrNumRecords 12884901888 vs 3

12884901888 is 0x3 ;-).

I’ll look into it...

Regards,

Stephen

Bug#961126: fig2dev fails autopkg test with stderr output on 32bit archs

[Matthias Klose]

Package: src:fig2dev
Version: 1:3.2.7b-3
Severity: serious
Tags: sid bullseye patch

fig2dev fails autopkg test with stderr output on 32bit archs

make  test1
make[1]: Entering directory 
'/tmp/autopkgtest.No5cFl/build.GqQ/src/fig2dev/tests'
gcc -DHAVE_CONFIG_H -I. -I../..  -DI18N_DATADIR="\"/usr/share/fig2dev/i18n\""
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2
-fdebug-prefix-map=/tmp/autopkgtest.No5cFl/build.GqQ/src=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o test1.o test1.c
test1.c: In function ‘main’:
test1.c:60:33: warning: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘size_t’ {aka ‘unsigned int’} [-Wformat=]
   60 |   printf("File path too long, %ld > %d.\n", n + 10, BUFSIZ);
  |   ~~^   ~~
  | | |
  | long int  size_t {aka unsigned int}
  |   %d
gcc  -g -O2 -fdebug-prefix-map=/tmp/autopkgtest.No5cFl/build.GqQ/src=. 
-fstack-prote

patch at
http://launchpadlibrarian.net/480599135/fig2dev_1%3A3.2.7b-3_1%3A3.2.7b-3ubuntu1.diff.gz

Bug#960963: status?

[Tomas Pospisek]

What's the status of this problem? Is anybody working on dovecot to have 
this fixed in Debian stable?

*t

Bug#926539: rootskel: steal-ctty no longer works on s390x

[John Paul Adrian Glaubitz]

On 5/20/20 1:18 PM, Philipp Kern wrote:
> But then I keep wondering how representative qemu is. Is VT220 SCLP even
> something you get on a real z machine? Not that we shouldn't fix qemu,
> of course. But Hercules might be closer to the real thing in this regard.

Hercules shows the exact same behavior. I also don't think the emulation
is relevant as the underlying issue is a naming inconsistency in the kernel
which is only present on s390x and used to be present on sparc64.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#961122: giac: FTBFS on armhf

[Graham Inggs]

Source: giac
Version: 1.5.0.87+dfsg1-1
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

d-workaround-armhf-hang.patch was recently dropped [1], however, as
can be seen on buildds [2] and reproducibles builds [3], that giac
still FTBFS on armhf with:

E: Build killed with signal TERM after 300 minutes of inactivity

Regards
Graham


[1] 
https://salsa.debian.org/science-team/giac/-/commit/67485addcc95870c3f4a5756cbba21a4d8889900
[2] https://buildd.debian.org/status/logs.php?pkg=giac=armhf
[3] https://tests.reproducible-builds.org/debian/history/armhf/giac.html

Bug#926539: rootskel: steal-ctty no longer works on s390x

[Philipp Kern]

On 20.05.20 12:42, Valentin Vidić wrote:
> On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
>> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
>>
>> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
>> that it would potentially break existing setups but eventually I could
>> convince him that the change was right.
>>
>> Not sure which distributions he has in mind.
> 
> It is hard to tell, but it seems the current state is hardcoded
> in different places:
> 
> https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html
> https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lhdd/lhdd_r_console_sum.html
> 
> I think it would be better to make debian-installer smarter about
> this since we will probably run into the same problem again with
> a different architecture/driver.

qemu-system-s390x is probably the least representative here. I recall
that the consoles for z/VM and LPAR were actually different. As alluded
to by the thread LPAR uses SCLP while you get 3215 on z/VM.

I'm all for making d-i smarter. But I think we should start by trying to
back merge all the improvements Canonical made on Ubuntu instead of
Debian as part of their s390x contract. Maybe trying ubuntu-installer
and seeing if that works correctly would be a good start.

But then I keep wondering how representative qemu is. Is VT220 SCLP even
something you get on a real z machine? Not that we shouldn't fix qemu,
of course. But Hercules might be closer to the real thing in this regard.

Kind regards
Philipp Kern

Processed: merge

[Debian Bug Tracking System]

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

> reassign 961056 src:linux,rootskel
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails 
due to incorrect serial device
Bug reassigned from package 'rootskel' to 'src:linux,rootskel'.
Ignoring request to alter found versions of bug #961056 to the same values 
previously set
Ignoring request to alter fixed versions of bug #961056 to the same values 
previously set
> severity 961056 serious
Bug #961056 [src:linux,rootskel] debian-installer: qemu-system-s390x 
installation fails due to incorrect serial device
Severity set to 'serious' from 'important'
> merge 961056 926539
Bug #961056 [src:linux,rootskel] debian-installer: qemu-system-s390x 
installation fails due to incorrect serial device
Bug #961056 [src:linux,rootskel] debian-installer: qemu-system-s390x 
installation fails due to incorrect serial device
Added tag(s) patch.
Bug #926539 [src:linux,rootskel] rootskel: steal-ctty no longer works on at 
least sparc64
Merged 926539 961056
> thanks
Stopping processing here.

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

Processed: bug 960658 is forwarded to https://github.com/cyrusimap/cyrus-imapd/issues/3040

[Debian Bug Tracking System]

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

> forwarded 960658 https://github.com/cyrusimap/cyrus-imapd/issues/3040
Bug #960658 [src:cyrus-imapd] src:cyrus-imapd: test fails on all big endian arch
Bug #960659 [src:cyrus-imapd] cyrus-imapd: Test failure on big endian
Bug #960660 [src:cyrus-imapd] cyrus-imapd: Test failure on armhf (at least on 
armv8)
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-imapd/issues/3040'.
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-imapd/issues/3040'.
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-imapd/issues/3040'.
> thanks
Stopping processing here.

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

Bug#961120: nulib2 ftbfs on s390x (failing tests), built before

[Matthias Klose]

Package: src:nulib2
Version: 3.1.0-3
Severity: serious
Tags: sid bullseye

nulib2 ftbfs on s390x (failing tests), built before:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nufxlib/samples/test-basic
ERROR: kNuAttrNumRecords 12884901888 vs 3
Using NuFX library v3.1.0, built on or after
  May 19 2020 with [Debian]

... starting tests
... open zero-byte existing
... add 'bytes' record
... add 'English' record
... add 'long' record
... checking contents
... reopening archive read-only
... checking contents
... verifying CRCs
... extracting files
... reopening archive read-write
... checking contents
... deleting first and last
... tests ended, FAILURE
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Processed (with 1 error): merge bugs

[Debian Bug Tracking System]

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

> merge 961056 926539
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails 
due to incorrect serial device
Unable to merge bugs because:
severity of #926539 is 'serious' not 'important'
package of #926539 is 'src:linux,rootskel' not 'rootskel'
Failed to merge 961056: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#926539: rootskel: steal-ctty no longer works on s390x

[John Paul Adrian Glaubitz]

On 5/20/20 12:42 PM, Valentin Vidić wrote:
> It is hard to tell, but it seems the current state is hardcoded
> in different places:
> 
> https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html

This wouldn't cause breakage as with your change, the console name
would actually be ttysclp0.

> https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lhdd/lhdd_r_console_sum.html

Well, IBM could just update their documentation.

> I think it would be better to make debian-installer smarter about
> this since we will probably run into the same problem again with
> a different architecture/driver.

It was only SPARC which had this issue as well and where it was fixed. For
all the other architectures, the console and driver names already match.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#961103: marked as done (headache FTBFS: Error: Unbound module UTF8)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 10:48:51 +
with message-id 
and subject line Bug#961103: fixed in headache 1.04-1
has caused the Debian Bug report #961103,
regarding headache FTBFS: Error: Unbound module UTF8
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.)


-- 
961103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: headache
Version: 1.03-30
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=headache=sid

...
/usr/bin/make all
make[2]: Entering directory '/<>'
/usr/bin/ocamlc -I +extlib extLib.cma -c info.ml
/usr/bin/ocamlc -I +extlib extLib.cma -c skip.ml
/usr/bin/ocamlc -I +extlib extLib.cma -c model.ml
File "model.ml", line 63, characters 12-27:
63 | Failure "int_of_string" -> 
 ^^^
Warning 52: Code should not depend on the actual values of
this constructor's arguments. They are only for information
and may change in future versions. (See manual section 9.5)
File "model.ml", line 68, characters 5-16:
68 |   if UTF8.length s = 1 then s.[0]
  ^^^
Error: Unbound module UTF8
make[2]: *** [Makefile:74: model.cmo] Error 2
--- End Message ---
--- Begin Message ---
Source: headache
Source-Version: 1.04-1
Done: Andy Li 

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

Debian distribution maintenance software
pp.
Andy Li  (supplier of updated headache package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 May 2020 18:24:07 +0800
Source: headache
Architecture: source
Version: 1.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Andy Li 
Closes: 961103
Changes:
 headache (1.04-1) unstable; urgency=medium
 .
   [ Andy Li ]
   * Team upload
   * New upstream version
 This version builds on camomile instead of extlib (closes: #961103)
   * Remove patches and README.Debian, all patches applied in this release
   * Update d/rules to use dune
   * Update d/control for dependency changes
   * Update Homepage, Source, and d/watch to reflect repository migration
 to GitHub according to http://forge.ocamlcore.org/projects/headache/
   * Bump Standards-Version to 4.5.0
 .
   [ Ralf Treinen ]
   * d/control: added missing ${shlibs:Depends}
Checksums-Sha1:
 ae8913aac7ed6a4da90597cc6211d20f5178f35a 2088 headache_1.04-1.dsc
 089a8235ce0f09443c25cc1fd0931cdcebd16859 176900 headache_1.04.orig.tar.gz
 2cb32ce698b50646a283160d7970a9490e904d6e 8456 headache_1.04-1.debian.tar.xz
 7b68fe76fa28b89e94acb96f5fbdad02b8ca8886 5730 headache_1.04-1_source.buildinfo
Checksums-Sha256:
 f7bb410fb7e4da30c0dde5eaf0a39a1d02bb2a15d62979492debe332e98e9132 2088 
headache_1.04-1.dsc
 af9d7d07fb9f66d4426d6d288cb285e69e2d47be38d3f5763f4e5f5504749721 176900 
headache_1.04.orig.tar.gz
 a7e5fbfc5c9b7f34a612fd87757d4e149d4c86248aa92667e434e8a916fd17bc 8456 
headache_1.04-1.debian.tar.xz
 10928750823f15fa57e733952ffba2f4464aa0a2549ff972b34a2fc24684e57c 5730 
headache_1.04-1_source.buildinfo
Files:
 8d336337ff7574db71961c993b89ccb0 2088 devel optional headache_1.04-1.dsc
 d551319dcb2616d660f2cb04021602aa 176900 devel optional 
headache_1.04.orig.tar.gz
 07f12434464f9a64c08f79d270b0908a 8456 devel optional 
headache_1.04-1.debian.tar.xz
 a169b3389e71a7243218fa500264fea6 5730 devel optional 
headache_1.04-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3wGpIpcm0PpC91cGbaw8RIdzOBoFAl7FBeMACgkQbaw8RIdz
OBp9NhAArF7kN2znbhTbyBed6oS6GLz7V7fyZ+wT1HnU/OddIpUqsIiQBzfghfmw
QNEVS4JCOTIwx25T/Tmo2DCOS1Dtag3ETKxPKQNKOeLCEJEvTGTtzQDcGp3NFP6s
VxTaMYmyBF7MNlk07AriuWQT64lDLvZulRgHyTu2y06DEZRie+/3+MUML0RmEXOC
bDac7gn8hwJNFVDaXL8c4NLIdGnWZkYEeZuemA7Unw4EJOfJbWku0E4C2T63y4BG
I7q4laJ87KpWInE7PspuPgsCZReJY+0yZr0Fsp4li30klxp/a5Bww0DW8FgCrUsR
PzwvaRtiPDwuPErQVtrxeSEPo/lmm/hvF6tOgnOS9y+ogzuDIdfxjRrNvDpvo3BA
C563pj5evR7oawc1nV3C4lL26SnOi+RMzIg4HQfG0XVwOzIr6Hulz8dY4zQs0gO6
dt6nGpQJjPmpoOg1brmI3LhJjSo6aqv5hLbQouM4uwpWLhCNLOZrmNe6P47v5fFu

Bug#926539: rootskel: steal-ctty no longer works on s390x

[Valentin Vidić]

On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
> 
> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
> that it would potentially break existing setups but eventually I could
> convince him that the change was right.
> 
> Not sure which distributions he has in mind.

It is hard to tell, but it seems the current state is hardcoded
in different places:

https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html
https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lhdd/lhdd_r_console_sum.html

I think it would be better to make debian-installer smarter about
this since we will probably run into the same problem again with
a different architecture/driver.

-- 
Valentin

Bug#952868: marked as done (OpenSSL linking without license exception)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 10:23:02 +
with message-id 
and subject line Bug#952868: fixed in wesnoth-1.14 1:1.14.12-1
has caused the Debian Bug report #952868,
regarding OpenSSL linking without license exception
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.)


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

This GPL2 package links with OpenSSL. The OpenSSL license is
incompatible with the GPL (see
https://ftp-master.debian.org/REJECT-FAQ.html). This can be solved by
asking upstream to add a license exception or by linking with wolfSSL
instead. You can find a patch enclosed (untested).
From f15f10434ef5fbdc9cf2eeea15e7ca057c0f6e63 Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Sun, 1 Mar 2020 11:19:53 +0100
Subject: [PATCH] Replace OpenSSL with wolfSSL

---
 debian/control  |  2 +-
 debian/patches/01wolfssl-crypto | 14 ++
 debian/patches/series   |  1 +
 debian/rules|  2 +-
 4 files changed, 17 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/01wolfssl-crypto

diff --git a/debian/control b/debian/control
index 5e35ef9b..1d650a07 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~), libsdl2-image-dev (>= 2.0.0),
   libboost-iostreams-dev, libboost-test-dev, libboost-regex-dev,
   libboost-serialization-dev, libboost-system-dev, libboost-thread-dev,
   libboost-program-options-dev, libboost-filesystem-dev, libboost-locale-dev,
-  libboost-random-dev, libpng-dev, libreadline-dev, libssl-dev,
+  libboost-random-dev, libpng-dev, libreadline-dev, libwolfssl-dev,
   libpango1.0-dev, libvorbis-dev, cmake (>= 2.6)
 Standards-Version: 4.1.4
 Uploaders: Rhonda D'Vine ,
diff --git a/debian/patches/01wolfssl-crypto b/debian/patches/01wolfssl-crypto
new file mode 100644
index ..ad55d158
--- /dev/null
+++ b/debian/patches/01wolfssl-crypto
@@ -0,0 +1,14 @@
+Author: Bastian Germann   vim:ft=diff:
+Description: Link with wolfssl instead of libcrypto.
+
+--- a/cmake/FindCrypto.cmake
 b/cmake/FindCrypto.cmake
+@@ -2,7 +2,7 @@
+ 
+ find_path(CRYPTO_INCLUDE_DIR openssl/md5.h)
+ 
+-find_library(CRYPTO_LIBRARY crypto)
++find_library(CRYPTO_LIBRARY wolfssl)
+ 
+ # handle the QUIETLY and REQUIRED arguments and set XXX_FOUND to TRUE if all listed variables are TRUE
+ INCLUDE(FindPackageHandleStandardArgs)
diff --git a/debian/patches/series b/debian/patches/series
index 57b6465e..8014e9fd 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
+01wolfssl-crypto
 02wesnoth-nolog-desktop-file
 03wesnothd-name
diff --git a/debian/rules b/debian/rules
index 02ad4071..cbec12c1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
 CXXFLAGSDBG = -g1
 endif
 
-export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS)
+export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) -I/usr/include/wolfssl -DOPENSSL_ALL
 export CFLAGS   := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp
 export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp  $(CXXFLAGSDBG)
 export LDFLAGS  := $(shell dpkg-buildflags --get LDFLAGS)
-- 
2.25.1

--- End Message ---
--- Begin Message ---
Source: wesnoth-1.14
Source-Version: 1:1.14.12-1
Done: Rhonda D'Vine 

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

Debian distribution maintenance software
pp.
Rhonda D'Vine  (supplier of updated wesnoth-1.14 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, 01 Apr 2020 09:46:00 +0200
Source: wesnoth-1.14
Binary: wesnoth wesnoth-1.14 wesnoth-1.14-aoi wesnoth-1.14-core 
wesnoth-1.14-core-dbgsym wesnoth-1.14-data wesnoth-1.14-did wesnoth-1.14-dm 
wesnoth-1.14-dw wesnoth-1.14-ei wesnoth-1.14-httt wesnoth-1.14-l 
wesnoth-1.14-low wesnoth-1.14-music wesnoth-1.14-nr wesnoth-1.14-server 

Bug#901382: node-katex is now split into katex (which include katex command and provides node-katex), libjs-katex and fonts-katex

[Pirate Praveen]

Control: block -1 by 961005

This is fixed in git along with update to 0.10.2 but blocked by 
node-less (need new upstream version).

Bug#945744: marked as done (wesnoth-1.14: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 10:23:02 +
with message-id 
and subject line Bug#945744: fixed in wesnoth-1.14 1:1.14.12-1
has caused the Debian Bug report #945744,
regarding wesnoth-1.14: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
945744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wesnoth-1.14
Version: 1:1.14.9-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: wesnoth-1.14
Source-Version: 1:1.14.12-1
Done: Rhonda D'Vine 

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

Debian distribution maintenance software
pp.
Rhonda D'Vine  (supplier of updated wesnoth-1.14 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, 01 Apr 2020 09:46:00 +0200
Source: wesnoth-1.14
Binary: wesnoth wesnoth-1.14 wesnoth-1.14-aoi wesnoth-1.14-core 
wesnoth-1.14-core-dbgsym wesnoth-1.14-data wesnoth-1.14-did wesnoth-1.14-dm 
wesnoth-1.14-dw wesnoth-1.14-ei wesnoth-1.14-httt wesnoth-1.14-l 
wesnoth-1.14-low wesnoth-1.14-music wesnoth-1.14-nr wesnoth-1.14-server 
wesnoth-1.14-server-dbgsym wesnoth-1.14-sof wesnoth-1.14-sota 
wesnoth-1.14-sotbe wesnoth-1.14-thot wesnoth-1.14-tools wesnoth-1.14-trow 
wesnoth-1.14-tsg wesnoth-1.14-ttb wesnoth-1.14-utbs wesnoth-core wesnoth-music
Architecture: source all amd64
Version: 1:1.14.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Rhonda D'Vine 
Description:
 wesnoth- fantasy turn-based strategy game - complete suite (metapackage)
 wesnoth-1.14 - fantasy turn-based strategy game - complete suite (branch 1.14)
 wesnoth-1.14-aoi - "An Orcish Incursion" official campaign for Wesnoth (branch 
1.14)
 wesnoth-1.14-core - fantasy turn-based strategy game (branch 1.14)
 wesnoth-1.14-data - data files for Wesnoth (branch 1.14)

Processed: node-katex is now split into katex (which include katex command and provides node-katex), libjs-katex and fonts-katex

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 961005
Bug #901382 [node-katex] node-katex: must build binary packages fonts-katex and 
libjs-katex
901382 was not blocked by any bugs.
901382 was not blocking any bugs.
Added blocking bug(s) of 901382: 961005

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

Bug#961116: gnome-shell-extension-suspend-button: Does not work with gnome 3.36

[Tobias Frost]

Package: gnome-shell-extension-suspend-button
Version: 0~git20191005-1
Severity: serious
Control: tags -1 upstream
Control: forwarded -1 
https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53

This extension is currently not compatible with gnome 3.36 and it is unclear if 
it will be
adapted to he new interface as upstream seems a bit inactive. 

Filing this bug to keep this extension out of testing and to see if this gets 
resolved

Note: gnome 3.36 has built-in facilities like this plugin, but requires 
additional click.

-- 
tobi

Processed: gnome-shell-extension-suspend-button: Does not work with gnome 3.36

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #961116 [gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: Does not work with gnome 3.36
Added tag(s) upstream.
> forwarded -1 
> https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53
Bug #961116 [gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: Does not work with gnome 3.36
Set Bug forwarded-to-address to 
'https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53'.

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

Bug#959225: libcap-ng: diff for NMU version 0.7.9-2.2

[Håvard Flaget Aasen]

Package: libcap-ng
Version: 0.7.9-2.1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for libcap-ng (versioned as 0.7.9-2.2) and
uploaded it to mentors. Please feel free to tell me if I
should remove it.

Regards,
Håvard
diff -Nru libcap-ng-0.7.9/debian/changelog libcap-ng-0.7.9/debian/changelog
--- libcap-ng-0.7.9/debian/changelog	2019-10-17 23:30:59.0 +0200
+++ libcap-ng-0.7.9/debian/changelog	2020-05-19 14:54:57.0 +0200
@@ -1,3 +1,13 @@
+libcap-ng (0.7.9-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/control
+- Remove dependency on linux-kernel-headers closes: #959225
+- Remove libattr1-dev as build dependency closes: #953925
+- Build for default python3 version closes: #943627
+
+ -- Håvard Flaget Aasen   Tue, 19 May 2020 14:54:57 +0200
+
 libcap-ng (0.7.9-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libcap-ng-0.7.9/debian/control libcap-ng-0.7.9/debian/control
--- libcap-ng-0.7.9/debian/control	2019-10-17 23:30:14.0 +0200
+++ libcap-ng-0.7.9/debian/control	2020-05-19 14:53:03.0 +0200
@@ -5,11 +5,10 @@
 dh-autoreconf,
 dh-python ,
 autotools-dev,
-libattr1-dev,
-linux-kernel-headers,
+linux-libc-dev,
 swig ,
-libpython3-all-dev ,
-python3-all-dev:any 
+libpython3-dev ,
+python3-dev:any 
 Standards-Version: 3.9.8
 Section: libs
 Homepage: http://people.redhat.com/sgrubb/libcap-ng

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

[Xavier]

Le 20/05/2020 à 11:26, Xavier a écrit :
> Hi,
> 
> with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this
> issue.
> @Adrian, could you test this on your armv8 ?
> 
> Cheers,
> Xavier

Note that there are still 4 tests that fail [1] (failed already at least
with i386). I'm waiting for [buildd] results.

[1]:
https://github.com/cyrusimap/cyrus-imapd/issues/3040#issuecomment-631367737
[buildd]:
https://buildd.debian.org/status/logs.php?pkg=cyrus-imapd=3.2.0-4

Bug#960660: cyrus-imapd: Test failure on armhf (at least on armv8)

[Xavier]

Hi,

with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this
issue.
@Adrian, could you test this on your armv8 ?

Cheers,
Xavier

Bug#926539: rootskel: steal-ctty no longer works on s390x

[John Paul Adrian Glaubitz]

On 5/20/20 11:17 AM, John Paul Adrian Glaubitz wrote:
> I don't see any discussion in this thread. I would like to know the reasoning
> why kernel upstream thinks that this naming inconsistency is correct. It
> makes no sense, in my opinion and it can potentially trigger more problems.

Ah, sorry. I was seeing the cached version of the thread, refreshing helped.

In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
that it would potentially break existing setups but eventually I could
convince him that the change was right.

Not sure which distributions he has in mind.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#926539: rootskel: steal-ctty no longer works on s390x

[John Paul Adrian Glaubitz]

Hi!

On 5/20/20 11:00 AM, Valentin Vidić wrote:
> Similar change for console name on s390x was not accepted:
> 
>   https://lkml.org/lkml/2020/5/19/854
> 
> so please fix in rootskel.

I don't see any discussion in this thread. I would like to know the reasoning
why kernel upstream thinks that this naming inconsistency is correct. It
makes no sense, in my opinion and it can potentially trigger more problems.

Also, this bug report should be merged with the other one that I referenced
yesterday.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#926539: rootskel: steal-ctty no longer works on s390x

[Valentin Vidić]

Similar change for console name on s390x was not accepted:

  https://lkml.org/lkml/2020/5/19/854

so please fix in rootskel.

-- 
Valentin

Bug#960892: marked as done (po4a: --srcdir ignored by [po_directory])

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 09:04:00 +
with message-id 
and subject line Bug#960892: fixed in po4a 0.59-1
has caused the Debian Bug report #960892,
regarding po4a: --srcdir ignored by [po_directory]
to be marked as done.

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

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


-- 
960892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: po4a
Version: 0.58.1-1
Severity: important
Control: affects -1 src:aptitude
Control: block 960865 by -1

Dear Martin,

previously when building aptitude's documentation, it sufficed to
declare

  [po_directory] po4a/po

in doc/po4a/po4a.cfg and then calling from the out-of-tree build
directory in e.g. "build/doc/de/"

  /usr/bin/po4a --translate-only=de/manpage.xml --srcdir=../../../doc 
--destdir=../../doc ../../../doc/po4a/po4a.cfg

but since recently, this fails with the IMHO not very helpful error
message:

  ../../../doc/po4a/po4a.cfg:1: no PO files found in po4a/po

See https://bugs.debian.org/960865.

The following change to doc/po4a/po4a.cfg fixes this:

  -[po_directory] po4a/po
  +[po_directory] ../../../doc/po4a/po

But this hardcoding of the relative path to the directory given with
--srcdir IMHO contradicts what is written in the man page:

   --srcdir SRCDIR
   Set the base directory for all input documents specified in
   the po4a configuration file.

   If both destdir and srcdir are specified, input files are
   searched in the following directories, in order: destdir,
   srcdir and the current directory. Output files are written to
   destdir if specified, or to the current directory.

Is there a chance that it has been forgotten to also check for the
po_directory under the directory given by --srcdir?

-- 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 5.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_UNSIGNED_MODULE
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 po4a depends on:
ii  gettext0.19.8.1-10
ii  libsgmls-perl  1.03ii-36
ii  libyaml-tiny-perl  1.73-1
ii  opensp 1.5.2-13+b1
ii  perl   5.30.0-10

Versions of packages po4a recommends:
ii  liblocale-gettext-perl 1.07-4
ii  libterm-readkey-perl   2.38-1+b1
ii  libtext-wrapi18n-perl  0.06-9
ii  libunicode-linebreak-perl  0.0.20190101-1+b2

po4a suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: po4a
Source-Version: 0.59-1
Done: to...@debian.org (Dr. Tobias Quathamer)

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated po4a 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, 20 May 2020 10:23:43 +0200
Source: po4a
Architecture: source
Version: 0.59-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Dr. Tobias Quathamer 
Closes: 960892 960949
Changes:
 po4a (0.59-1) unstable; urgency=medium
 .
   [ Niko Tyni ]
   * Add dependencies on libpod-parser-perl.
 This anticipates changes in Perl 5.32: Pod::Parser has been removed
 from the core distribution in the 5.31 series and is being packaged
 separately for Debian.
 The Perl 5.30 package in Debian already Provides libpod-parser-perl,
 so the dependencies don't need to wait for the separate package.
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 0.59
 - po4a tool: Fix --srcdir handling. This bug was breaking the build
   of several packages, including 

Bug#961104: marked as done (t4kcommon FTBFS on !amd64)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 08:48:55 +
with message-id 
and subject line Bug#961104: fixed in t4kcommon 0.1.1-9
has caused the Debian Bug report #961104,
regarding t4kcommon FTBFS on !amd64
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.)


-- 
961104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: t4kcommon
Version: 0.1.1-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=t4kcommon=sid

...
   dh_missing -a
dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.a exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.a")
dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.la exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.la")
dh_missing: error: missing files, aborting
...
--- End Message ---
--- Begin Message ---
Source: t4kcommon
Source-Version: 0.1.1-9
Done: Holger Levsen 

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated t4kcommon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 May 2020 10:30:44 +0200
Source: t4kcommon
Architecture: source
Version: 0.1.1-9
Distribution: unstable
Urgency: medium
Maintainer: Holger Levsen 
Changed-By: Holger Levsen 
Closes: 961104
Changes:
 t4kcommon (0.1.1-9) unstable; urgency=medium
 .
   * d/not-installed: use wildcards to ignore usr/lib/*/libt4k_common.(a|la)
 for all architectures. Closes: #961104. Thanks to Adrian Bunk.
Checksums-Sha1:
 a2a7b8d22794447b754064a7d4a43a78d450afed 2132 t4kcommon_0.1.1-9.dsc
 982e676c4a01bb3fefb8380e5ee97796192ef6aa 5960 t4kcommon_0.1.1-9.debian.tar.xz
 c8a2a1ae3bc099d3b7872958c5432c62919b7010 12451 
t4kcommon_0.1.1-9_source.buildinfo
Checksums-Sha256:
 b04afcba9f19051d1edc7283d5b52ee9b85de3dc927ce0b28b7b94310ba7bd5e 2132 
t4kcommon_0.1.1-9.dsc
 3cc72f436fe390cd46a00016c3479d2f5231a522aed48b23ed8ac6a47cb7f2e1 5960 
t4kcommon_0.1.1-9.debian.tar.xz
 1e6f0d7a987c1262b3fb2ee8a1e29c0887575824afb93be21892224cbf7a1189 12451 
t4kcommon_0.1.1-9_source.buildinfo
Files:
 295c8b7bc4e56347761a3d2b29bb2915 2132 libs optional t4kcommon_0.1.1-9.dsc
 5eb97905ebb8eb49410014f6dc75cc63 5960 libs optional 
t4kcommon_0.1.1-9.debian.tar.xz
 abcf096579ee7c16bf037b7d62fcb942 12451 libs optional 
t4kcommon_0.1.1-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl7E65oACgkQCRq4Vgaa
qhzGoA//auXqe6dgOlOUpvpz25FCoW5KQDtuDjIcG6bsCDtxIfI7Ovm5gANUjyPS
csiiFujkWYXzli3RBS0cxtCMnaWfSIUNcfFuFJrO0IWd2EtrXuQnh/W5yw9FXE2u
YT+hFCmcb4vCmm2F2/jhL5Yg7Hrl11Qo82Yh1tJ9WODLUo1eGv9N+93RApA1sFFu
KLvdAYthPIX0oYhI0DFpDZu5wDhWhJpRSHgYvFW4xRbHU+h07kSKvs5wKKLEcmCc
LIyjpqxocoEFrn68suziSFtFJoBrPFWdTDVbQQfDS9MIOG7hUBoTn3XyMl2IYOfc
ALt9LWw0UFSxmtIa4oEsSX3CPpwuK6x9OhLl2i8Pm7ToliqUQrOieDxzwQ11IOBm
V20J/f8t/XVikK4icMVmv2uhaxV4mWGhVpPuHd0AJkTVjxyn0z5pAVo/xk8gQEtT
QzDXs+rHRzOdCzOGlXyfEe/aSt5ezozd7mS6mCtVezuUxzKvKtNfNtGITCObCVa/
MGwKzAqnC9TUlHz88DV1D3bNJq0dLEQPJXbHZua7cxOT5iSEyANJXPQS1Sv6aDTV
Tpvf0/FF5/u60KzZGr7cPwY5EWTDOtu9aaOmdcNNASn5enr1N40xaXZFLQXZ0CKn
uP5gAwy1NhXT0QJbqLGdCXANMsq/LURFFWUD0400OtXowiEwoLM=
=vlvD
-END PGP SIGNATURE End Message ---

Bug#960998: marked as done (r-cran-av: broken symlink /usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 08:37:17 +
with message-id 
and subject line Bug#960998: fixed in r-cran-av 0.5.0+dfsg-3
has caused the Debian Bug report #960998,
regarding r-cran-av: broken symlink 
/usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3
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.)


-- 
960998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-av
Version: 0.5.0+dfsg-2
Severity: serious
Control: affects -1 src:r-cran-av

The autopkgtest fails:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-av/4902405/log.gz

This is due to:
/usr/lib/R/site-library/av/samples/Synapsis-Wonderland.mp3: broken symbolic 
link to ../../../../../share/doc/libmp3-tag-perl/examples/empty_10sec.mp3

The test passes after installing libmp3-tag-perl, but shipping
a broken link created in debian/rules is wrong in any case.

And depending on libmp3-tag-perl does not make sense for that.

I would suggest to remove the override_dh_link, add test
dependency on libmp3-tag-perl and then copy the file from
libmp3-tag-perl at the start of the test.
--- End Message ---
--- Begin Message ---
Source: r-cran-av
Source-Version: 0.5.0+dfsg-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-av 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, 20 May 2020 09:34:42 +0200
Source: r-cran-av
Architecture: source
Version: 0.5.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 960998
Changes:
 r-cran-av (0.5.0+dfsg-3) unstable; urgency=medium
 .
   * Provide mp3 example properly
 Closes: #960998
Checksums-Sha1:
 7258adf87665ceb35a057ad39d3195c6c3735178 2108 r-cran-av_0.5.0+dfsg-3.dsc
 f580fc81824abd609c32dbc30efb7968669046a3 4080 
r-cran-av_0.5.0+dfsg-3.debian.tar.xz
 2423740ad5fd669c05d3ff3f91912fa4324bb95e 10972 
r-cran-av_0.5.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9271887b634ee5efa27b8e9c07856d94449e8c4b0cec09881c68519ad076a0de 2108 
r-cran-av_0.5.0+dfsg-3.dsc
 c69fed024f9febcb4f0a768e43f118e30981e65c66e4d2c9aadbcb0cb3dbc5de 4080 
r-cran-av_0.5.0+dfsg-3.debian.tar.xz
 5e2c3fc66e18db14e9a07c70ab6fc9651318537b83cf9113a3aa2f0ef229cf72 10972 
r-cran-av_0.5.0+dfsg-3_amd64.buildinfo
Files:
 774bbc549ebb570e0d75f508ad12f5c6 2108 gnu-r optional r-cran-av_0.5.0+dfsg-3.dsc
 d5512a73b1042a5e7793b533e01bb70f 4080 gnu-r optional 
r-cran-av_0.5.0+dfsg-3.debian.tar.xz
 5ebe3bd8539e62349ea9af917802ceb3 10972 gnu-r optional 
r-cran-av_0.5.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7E31QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFWgQ//RVmDrPayJVbUFb0v4JVNxde+PanXgnx5
Fmn/SjZdOQVJD93b5UBtqiBOuTEVzTb88qsWpt86TfQ+YQ9X8fLOdKfLa8bqBmTR
cYGu3gjAsWVvmsRWDjE0DAM6u2NutueURKpEVc+1hlf9zoJgQq8nQSfCOLJsuaf0
z22BZKkbwi8PLBG8tq7pRuO9wTsCs32f7fwTEq2zWLWhihuVo5nSwQxCTbeQUN6R
ROBQkmG1xLqngSH7gUfFuykpLK+n4rl7IO6+ir3k6OO5aaJxbYGP5ripyzsE223P
ylYloFKXJ6SQieSCkJCF0zKXD6PqsdOINAEze7MlodELQ+XvOREJu0v3nbA4CJD5
FhjfiV9gPoWgokmadyxs4B21lfNtAvzZW61bNk7vwvkYL/ND+c7sYUleowy0DCeX
cgUddoTZ0r64uf0Dyhd/CiXzvleJfJbF9zC71lJNUXnm7Y9lwD4JbjlMBk/Tp8Wi
2U5UMCc6JprDjocYYvqXV20oRTpE9ICmoYuDj6NOZEiqVX9N5ne3doe1IIobp0Vg
Leh/xMVsgPxa4o0ASvA/ohhFVNrdYwOTGu4T939u8FSXuxQFo8Yr0WPTgQfyB4v7
h3XcwhqkDT3xIC8HC2O54sq0HvCNzz2//kv+RGyyOYhkHnU0UdlEN20jKUTXu4TD
PulLx6QJnUs=
=0ygm
-END PGP SIGNATURE End Message ---

Bug#961104: t4kcommon FTBFS on !amd64

[Holger Levsen]

On Wed, May 20, 2020 at 11:17:49AM +0300, Adrian Bunk wrote:
> the paths do not include "x86_64-linux-gnu" on other architectures,

I was aware of this...

> you should write these as
>   usr/lib/*/libt4k_common.a
>   usr/lib/*/libt4k_common.la

but not that I could use wildcards here. Thank you!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.


signature.asc
Description: PGP signature

Bug#961104: t4kcommon FTBFS on !amd64

[Adrian Bunk]

On Wed, May 20, 2020 at 08:12:35AM +, Holger Levsen wrote:
> Hi Adrian,

Hi Holger,

>...
> I was surprised when I added these lines to debian/not-installed for
> the 0.1.1-8 upload:
> 
> usr/lib/x86_64-linux-gnu/libt4k_common.a
> usr/lib/x86_64-linux-gnu/libt4k_common.la
> 
> however as I could confirm with diffoscope that these files were not shipped
> previously I thought this was ok. Now I can clearly see the problem this
> causes and will look for a better solution...
> 
> Help/hints welcome!

the paths do not include "x86_64-linux-gnu" on other architectures,
you should write these as

  usr/lib/*/libt4k_common.a
  usr/lib/*/libt4k_common.la

> cheers,
>   Holger

cu
Adrian

Bug#959236: ifenslave bonding doesn't work. Same here

[Miguel A. Novo]

  
  
After the last dist-upgrade bonding stopped
  working. I am using bullseye/sid and 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29)
x86_64 GNU/Linux
  
  The "dist-upgrade" warned about not using ifenslave anymore but
  iproute2, so I tried to see how this would affect the server
  implied, and:
  
  This is my /etc/network/interfaces
  
  auto eth0
  auto eth1
  iface eth0 inet manual
  iface eth1 inet manual
  
  auto bond10
  iface bond10 inet static
      address 192.168.10.205
      netmask 255.255.255.0
      network 192.168.10.0
      broadcast 192.168.10.255
      gateway 192.168.10.254
      bond-slaves eth0 eth1
      bond-miimon 100
      bond-mode balance-rr
      bond-downdelay 200
      bond-updelay 200
  
  This is what it happens on every reboot:
  
  may 18 14:58:06 hermes systemd-udevd[374]: Using default interface
  naming scheme 'v245'.
  may 18 14:58:06 hermes systemd-udevd[374]: ethtool:
  autonegotiation is unset or enabled, the speed and duplex are not
  writable.
  may 18 14:58:06 hermes kernel: Ethernet Channel Bonding Driver:
  v3.7.1 (April 27, 2011)
  may 18 14:58:06 hermes ifup[611]:
  /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion
  depth (1000) reached
  may 18 14:58:06 hermes ifup[610]: run-parts:
  /etc/network/if-pre-up.d/ifenslave exited with return code 2
  may 18 14:58:06 hermes ifup[584]: ifup: failed to bring up bond10
  may 18 14:58:06 hermes systemd[1]: networking.service: Main
  process exited, code=exited, status=1/FAILURE
  may 18 14:58:06 hermes systemd[1]: networking.service: Failed with
  result 'exit-code'.
  may 18 14:58:06 hermes systemd[1]: Failed to start Raise network
  interfaces.
  
  I have to say that the alternative systemd method to setup
  bonding, bridging, etc. is far to be a simple, clean and clear
  method as it should be, in my humble opinion.
  
  Also, but less important, I am using the traditional NIC naming
  scheme, using "biosdevname=0, net.ifnames=0" with GRUB, and I get
  these messages. I don't understand why (my /etc/udev/rules.d is
  empty):
  
  may 18 14:58:02 hermes systemd-udevd[365]: Using default interface
  naming scheme 'v245'.
  may 18 14:58:02 hermes systemd-udevd[365]: ethtool:
  autonegotiation is unset or enabled, the speed and duplex are not
  writable.
  may 18 14:58:02 hermes systemd-udevd[365]: Could not set
  AlternativeName= or apply AlternativeNamesPolicy= on eth0: File
  exists
  may 18 14:58:02 hermes systemd-udevd[365]: eth0: Could not apply
  link config, ignoring: File exists
  may 18 14:58:02 hermes systemd-udevd[365]: ethtool:
  autonegotiation is unset or enabled, the speed and duplex are not
  writable.
  may 18 14:58:02 hermes systemd-udevd[365]: Could not set
  AlternativeName= or apply AlternativeNamesPolicy= on eth1: File
  exists
  may 18 14:58:02 hermes systemd-udevd[365]: eth1: Could not apply
  link config, ignoring: File exists
  
  Why is systemd trying to do some NIC renaming is a mistery to me.
  
  Regards,

-- 

Miguel A. Novo

  

Bug#961104: t4kcommon FTBFS on !amd64

[Holger Levsen]

Hi Adrian,

On Wed, May 20, 2020 at 09:41:16AM +0300, Adrian Bunk wrote:
> Source: t4kcommon
> Version: 0.1.1-8
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=t4kcommon=sid
> 
> ...
>dh_missing -a
> dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.a exists in 
> debian/tmp but is not installed to anywhere (related file: 
> "debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.a")
> dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.la exists in 
> debian/tmp but is not installed to anywhere (related file: 
> "debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.la")
> dh_missing: error: missing files, aborting
> ...

thanks for this bug report, I'll fix it ASAP, which could be some days...

I was surprised when I added these lines to debian/not-installed for
the 0.1.1-8 upload:

usr/lib/x86_64-linux-gnu/libt4k_common.a
usr/lib/x86_64-linux-gnu/libt4k_common.la

however as I could confirm with diffoscope that these files were not shipped
previously I thought this was ok. Now I can clearly see the problem this
causes and will look for a better solution...

Help/hints welcome!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#960892: po4a: --srcdir ignored by [po_directory]

[Martin Quinson]

Hello,

your patch was included in an upstream release. The debian package
should be updated shortly.

Thanks for your patience,
Mt.

-- 
You have a problem and decide to use floats. 
Now you have 2.0001 problems.


signature.asc
Description: PGP signature

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

[Phil Wyett]

On Wed, 2020-05-20 at 09:28 +0200, Bernhard Übelacker wrote:
> > On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote:
> > > Versions of packages mkvtoolnix-gui depends on:
> > > ii  libebml4v5 1:1.3.9-dmo0+deb9u1
> > > ii  libmatroska6v5 1:1.4.5-dmo1
> 
> Hello,
> might this be related to the above packages being
> from the debian multimedia repository?
> 
> Could the issue resolve if these packages get installed
> in the buster version?
> 
> Kind regards,
> Bernhard
> 

I did not spot the presence of the dmo packages.

This app works correctly with Debian buster versions of the packages.

Regards

Phil

-- 

*** Playing the game for the games sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B



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

Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE

[Bernhard Übelacker]

> On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote:
> > Versions of packages mkvtoolnix-gui depends on:
> > ii  libebml4v5 1:1.3.9-dmo0+deb9u1
> > ii  libmatroska6v5 1:1.4.5-dmo1

Hello,
might this be related to the above packages being
from the debian multimedia repository?

Could the issue resolve if these packages get installed
in the buster version?

Kind regards,
Bernhard

Processed: bug 956083 is forwarded to https://github.com/k0lter/autopostgresqlbackup/issues/2

[Debian Bug Tracking System]

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

> forwarded 956083 https://github.com/k0lter/autopostgresqlbackup/issues/2
Bug #956083 [autopostgresqlbackup] autopostgresqlbackup: Fails to detect when 
DB dumps fail, and saves useless backups
Set Bug forwarded-to-address to 
'https://github.com/k0lter/autopostgresqlbackup/issues/2'.
> thanks
Stopping processing here.

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

Processed: limit source to headache, tagging 961103

[Debian Bug Tracking System]

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

> limit source headache
Limiting to bugs with field 'source' containing at least one of 'headache'
Limit currently set to 'source':'headache'

> tags 961103 + pending
Bug #961103 [src:headache] headache FTBFS: Error: Unbound module UTF8
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#961095: marked as done (mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE)

[Debian Bug Tracking System]

Your message dated Wed, 20 May 2020 09:05:37 +0200
with message-id <20200520070537.ga489...@ramacher.at>
and subject line Re: Bug#961095: mkvtoolnix-gui: mkvtoolnix does not start 
undefined symbol: _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE
has caused the Debian Bug report #961095,
regarding mkvtoolnix-gui: mkvtoolnix does not start undefined symbol: 
_ZN11libmatroska22KaxVideoProjectionType10ClassInfosE
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.)


-- 
961095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mkvtoolnix-gui
Version: 31.0.0-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

$ mkvtoolnix-gui
mkvtoolnix-gui: symbol lookup error: mkvtoolnix-gui: undefined symbol:
_ZN11libmatroska22KaxVideoProjectionType10ClassInfosE



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

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

Versions of packages mkvtoolnix-gui depends on:
ii  libboost-filesystem1.67.0  1.67.0-13+deb10u1
ii  libboost-regex1.67.0   1.67.0-13+deb10u1
ii  libboost-system1.67.0  1.67.0-13+deb10u1
ii  libc6  2.28-10
ii  libcmark0  0.28.3-1
ii  libebml4v5 1:1.3.9-dmo0+deb9u1
ii  libgcc11:8.3.0-6
ii  libmagic1  1:5.35-4+deb10u1
ii  libmatroska6v5 1:1.4.5-dmo1
ii  libpugixml1v5  1.9-3
ii  libqt5core5a   5.11.3+dfsg1-1+deb10u3
ii  libqt5dbus55.11.3+dfsg1-1+deb10u3
ii  libqt5gui5 5.11.3+dfsg1-1+deb10u3
ii  libqt5multimedia5  5.11.3-2
ii  libqt5network5 5.11.3+dfsg1-1+deb10u3
ii  libqt5widgets5 5.11.3+dfsg1-1+deb10u3
ii  libstdc++6 8.3.0-6
ii  mkvtoolnix 31.0.0-1+b1
ii  zlib1g 1:1.2.11.dfsg-1

mkvtoolnix-gui recommends no packages.

mkvtoolnix-gui suggests no packages.

-- no debconf information

RioTel - Barracuda Email Security Gateway
--- End Message ---
--- Begin Message ---
On 2020-05-20 02:49:18 +0100, Phil Wyett wrote:
> Control: tags -1 + moreinfo
> 
> On Tue, 2020-05-19 at 22:05 -0300, Mauro Dionisi wrote:
> > Package: mkvtoolnix-gui
> > Version: 31.0.0-1+b1
> > Severity: grave
> > Tags: upstream
> > Justification: renders package unusable
> > 
> > $ mkvtoolnix-gui
> > mkvtoolnix-gui: symbol lookup error: mkvtoolnix-gui: undefined symbol:
> > _ZN11libmatroska22KaxVideoProjectionType10ClassInfosE
> > 
> > 
> > 
> > -- System Information:
> > Debian Release: 10.4
> >   APT prefers stable
> >   APT policy: (990, 'stable')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> > 
> > Kernel: Linux 4.19.0-9-amd64 (SMP w/6 CPU cores)
> > Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
> > LANGUAGE=es_AR:es (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> > 
> > Versions of packages mkvtoolnix-gui depends on:
> > ii  libboost-filesystem1.67.0  1.67.0-13+deb10u1
> > ii  libboost-regex1.67.0   1.67.0-13+deb10u1
> > ii  libboost-system1.67.0  1.67.0-13+deb10u1
> > ii  libc6  2.28-10
> > ii  libcmark0  0.28.3-1
> > ii  libebml4v5 1:1.3.9-dmo0+deb9u1
> > ii  libgcc11:8.3.0-6
> > ii  libmagic1  1:5.35-4+deb10u1
> > ii  libmatroska6v5 1:1.4.5-dmo1
> > ii  libpugixml1v5  1.9-3
> > ii  libqt5core5a   5.11.3+dfsg1-1+deb10u3
> > ii  libqt5dbus55.11.3+dfsg1-1+deb10u3
> > ii  libqt5gui5 5.11.3+dfsg1-1+deb10u3
> > ii  libqt5multimedia5  5.11.3-2
> > ii  libqt5network5 5.11.3+dfsg1-1+deb10u3
> > ii  libqt5widgets5 5.11.3+dfsg1-1+deb10u3
> > ii  libstdc++6 8.3.0-6
> > ii  mkvtoolnix 31.0.0-1+b1
> > ii  zlib1g 1:1.2.11.dfsg-1
> > 
> > mkvtoolnix-gui recommends no packages.
> > 
> > mkvtoolnix-gui suggests no packages.
> > 
> > -- no debconf information
> > 
> > RioTel - Barracuda Email Security Gateway
> > 
> 
> I am unable to reproduce under vanilla 10.4 installation. Could you
> provide more information 

Bug#961107: slic3r-prusa FTBFS on mipsel and i386

[Adrian Bunk]

Source: slic3r-prusa
Version: 2.2.0+dfsg1-1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=mipsel=2.2.0%2Bdfsg1-1=1586422709=0

...
virtual memory exhausted: Cannot allocate memory
make[3]: *** [src/libslic3r/CMakeFiles/libslic3r_cgal.dir/build.make:66: 
src/libslic3r/CMakeFiles/libslic3r_cgal.dir/MeshBoolean.cpp.o] Error 1


https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=i386=2.2.0%2Bdfsg1-1=1586426190=0

...
test cases:  28 |  27 passed | 1 failed
assertions: 519 | 517 passed | 2 failed


E: Build killed with signal TERM after 150 minutes of inactivity


Fix/workaround:

--- debian/rules.old2020-04-07 15:08:57.0 +
+++ debian/rules2020-05-20 06:43:06.593960217 +
@@ -4,7 +4,11 @@
 
 # less debug info to avoid running out of address space
 ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
-   export DEB_CXXFLAGS_MAINT_APPEND += -g1
+   export DEB_CXXFLAGS_MAINT_APPEND += --param ggc-min-expand=5 -g0
+endif
+
+ifneq (,$(filter $(DEB_HOST_ARCH), i386))
+export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store
 endif
 
 %:

Bug#961104: t4kcommon FTBFS on !amd64

[Adrian Bunk]

Source: t4kcommon
Version: 0.1.1-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=t4kcommon=sid

...
   dh_missing -a
dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.a exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.a")
dh_missing: warning: usr/lib/aarch64-linux-gnu/libt4k_common.la exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libt4k_common.la")
dh_missing: error: missing files, aborting
...

Bug#961103: headache FTBFS: Error: Unbound module UTF8

[Adrian Bunk]

Source: headache
Version: 1.03-30
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=headache=sid

...
/usr/bin/make all
make[2]: Entering directory '/<>'
/usr/bin/ocamlc -I +extlib extLib.cma -c info.ml
/usr/bin/ocamlc -I +extlib extLib.cma -c skip.ml
/usr/bin/ocamlc -I +extlib extLib.cma -c model.ml
File "model.ml", line 63, characters 12-27:
63 | Failure "int_of_string" -> 
 ^^^
Warning 52: Code should not depend on the actual values of
this constructor's arguments. They are only for information
and may change in future versions. (See manual section 9.5)
File "model.ml", line 68, characters 5-16:
68 |   if UTF8.length s = 1 then s.[0]
  ^^^
Error: Unbound module UTF8
make[2]: *** [Makefile:74: model.cmo] Error 2