Processed: tagging 961699

[Debian Bug Tracking System]

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

> tags 961699 + bullseye sid
Bug #961699 [src:dokujclient] dokujclient build depends on the removed 
libguava-java-doc
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#961700: picard-tools build depends on the removed libguava-java-doc

[Adrian Bunk]

Source: picard-tools
Version: 2.18.25+dfsg-2
Severity: serious
Tags: ftbfs bullseye sid

picard-tools build depends on libguava-java-doc,
which is no longer built by src:guava-libraries.

Bug#961699: dokujclient build depends on the removed libguava-java-doc

[Adrian Bunk]

Source: dokujclient
Version: 3.9.0-1
Severity: serious
Tags: ftbfs

dokujclient build depends on libguava-java-doc,
which is no longer built by src:guava-libraries.

Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel

[Paul Gevers]

Hi Dirk,

On 28-05-2020 01:14, Dirk Eddelbuettel wrote:
> Shall I close this one 'by hand'?  Or will it get closed by migrating
> quantlib-swig?  I just close the other one (#956830) that was at the start of
> this by hand.

I closed the bug the moment I filed it. Albeit that's a bit weird, I
have multiple reasons to do that (I use a template for these bugs):

- The Release Team considers the version in TESTING from having an RC
issue. So, the version in unstable is fine, and if it migrates, the
Release Team's concern is addressed.

- If the package migrates without a new upload, it's easy for the
maintainer to forget to close the issue. Then we need manual actions to
close it, or QA needs to find these unclosed bugs later. The BTS doesn't
archive unclosed bugs.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: severity of 960773 is important

[Debian Bug Tracking System]

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

> severity 960773 important
Bug #960773 [src:gr-gsm] gr-gsm FTBFS on big endian
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#961367: marked as done (tome FTBFS on 32bit: invalid conversion from ‘uint32_t*’ {aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’})

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 06:03:38 +
with message-id 
and subject line Bug#961367: fixed in tome 2.41-ah~0.git.20200131-1
has caused the Debian Bug report #961367,
regarding tome FTBFS on 32bit: invalid conversion from ‘uint32_t*’ {aka 
‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’}
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.)


-- 
961367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tome
Version: 2.4.0-ah-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=tome&suite=sid

...
/<>/src/loadsave.cc: In instantiation of ‘void 
{anonymous}::do_flag_set(flag_set*, ls_flag_t) [with unsigned int Tiers 
= 6]’:
/<>/src/loadsave.cc:391:34:   required from here
/<>/src/loadsave.cc:280:10: error: invalid conversion from 
‘uint32_t*’ {aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’} 
[-fpermissive]
  280 |   do_u32b(&(*flags)[i], flag);
  |   ~~~^~~~
  |  |
  |  uint32_t* {aka unsigned int*}
/<>/src/loadsave.cc:190:27: note:   initializing argument 1 of 
‘void do_u32b(u32b*, ls_flag_t)’
  190 | static void do_u32b(u32b *ip, ls_flag_t flag)
  | ~~^~
/<>/src/loadsave.cc: In instantiation of ‘void 
{anonymous}::do_flag_set(flag_set*, ls_flag_t) [with unsigned int Tiers 
= 1]’:
/<>/src/loadsave.cc:430:34:   required from here
/<>/src/loadsave.cc:280:10: error: invalid conversion from 
‘uint32_t*’ {aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’} 
[-fpermissive]
  280 |   do_u32b(&(*flags)[i], flag);
  |   ~~~^~~~
  |  |
  |  uint32_t* {aka unsigned int*}
/<>/src/loadsave.cc:190:27: note:   initializing argument 1 of 
‘void do_u32b(u32b*, ls_flag_t)’
  190 | static void do_u32b(u32b *ip, ls_flag_t flag)
  | ~~^~
/<>/src/loadsave.cc: In instantiation of ‘void 
{anonymous}::do_flag_set(flag_set*, ls_flag_t) [with unsigned int Tiers 
= 2]’:
/<>/src/loadsave.cc:1366:34:   required from here
/<>/src/loadsave.cc:280:10: error: invalid conversion from 
‘uint32_t*’ {aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’} 
[-fpermissive]
  280 |   do_u32b(&(*flags)[i], flag);
  |   ~~~^~~~
  |  |
  |  uint32_t* {aka unsigned int*}
/<>/src/loadsave.cc:190:27: note:   initializing argument 1 of 
‘void do_u32b(u32b*, ls_flag_t)’
  190 | static void do_u32b(u32b *ip, ls_flag_t flag)
  | ~~^~
...
--- End Message ---
--- Begin Message ---
Source: tome
Source-Version: 2.41-ah~0.git.20200131-1
Done: Manoj Srivastava 

We believe that the bug you reported is fixed in the latest version of
tome, 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 tome 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, 27 May 2020 16:50:33 -0700
Source: tome
Architecture: source
Version: 2.41-ah~0.git.20200131-1
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Closes: 961367
Changes:
 tome (2.41-ah~0.git.20200131-1) unstable; urgency=medium
 .
   * New ipstream git snapshot (sync to head)
   * Bug fix: "tome FTBFS on 32bit: invalid conversion from ‘uint32_t*’
 {aka ‘unsigned int*’} to ‘u32b*’ {aka ‘long unsigned int*’}", thanks
 to Adrian Bunk (Closes: #961367).
Checksums-Sha1:
 6d3cb388ea80bc4a35574ddeac9a679f3a92790f 1964 tome_2.41-ah~0.git.20200131-1.dsc
 15474facc647c91d2fe8746fe71ecb5ad1be6a65 2553302 
tome_2.41-ah~0.git.20200131.orig.tar.gz
 91ce0a126a709f376f037246bcc81c512594a533 30566 
tome_2.41-ah~0.git.20200131-1.diff.gz
Checksums-Sha256:
 7f75d61c7b00e28a3d07568d265ba9d24e2c6e2140cd0fb62c46b30f998666dc 1964 
tome_2.41-ah~0.git.20200131-1.dsc
 d031a3a89cce0f379d92ddaf9d53b4aae6ee0c47b81aaf3b0d700b2ab0375385 2553302 
tome_2.41-ah~0.git.20200131.orig.tar.gz
 8ca6fe8dacb803d90f1342796ec96de3985252d13324eb90d508abd3c1504cfa 30566 
t

Processed: retitle 961116 to gnome-shell-extension-suspend-button: Not suitable for next release: Does not work with gnome 3.36

[Debian Bug Tracking System]

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

> retitle 961116 gnome-shell-extension-suspend-button: Not suitable for next 
> release: Does not work with gnome 3.36
Bug #961116 [gnome-shell-extension-suspend-button] 
gnome-shell-extension-suspend-button: Does not work with gnome 3.36
Changed Bug title to 'gnome-shell-extension-suspend-button: Not suitable for 
next release: Does not work with gnome 3.36' from 
'gnome-shell-extension-suspend-button: Does not work with gnome 3.36'.
> thanks
Stopping processing here.

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

Bug#960752: marked as done (FTBFS on IPv6-only hosts)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 05:18:50 +
with message-id 
and subject line Bug#960752: fixed in cockpit 220-1
has caused the Debian Bug report #960752,
regarding FTBFS on IPv6-only hosts
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.)


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

Hi Martin,

looks like the latest release reliably triggers a FTBFS on arch-all:

https://buildd.debian.org/status/logs.php?pkg=cockpit&ver=219-1&arch=all

The relevant part from the build log
**
cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request: 
assertion failed (error == NULL): Error resolving 
?2a02:16a8:dc41:100::238:46259?: Name or service not known 
(g-resolver-error-quark, 0)
SKIP: test-webserver Bail out! 
cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request: 
assertion failed (error == NULL): Error resolving 
?2a02:16a8:dc41:100::238:46259?: Name or service not known 
(g-resolver-error-quark, 0)
Aborted
ERROR: test-webserver process failed: 134


Regards,
Michael



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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cockpit
Source-Version: 220-1
Done: Martin Pitt 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 May 2020 07:04:14 +0200
Source: cockpit
Architecture: source
Version: 220-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Martin Pitt 
Closes: 960752
Changes:
 cockpit (220-1) unstable; urgency=medium
 .
   * New upstream release:
 - New navigation with integrated switching of hosts
 - Logs: Inline help for filtering
 - Storage: Improve side panel on details page
 - Fix unit tests on IPv6-only build hosts (Closes: #960752)
Checksums-Sha1:
 2736c7076495b3e869bd614efb7821329bd22af6 3102 cockpit_220-1.dsc
 602cf4d82e837cf2d3b45041befecd6e4e22d40d 13324848 cockpit_220.orig.tar.xz
 18ff40faddfa43489468cfbcd3503716a694fec0 16876 cockpit_220-1.debian.tar.xz
 962b93a4a06f84cbf3b5b002e6c619061d0d788e 9303 cockpit_220-1_source.buildinfo
Checksums-Sha256:
 bcf9d146897a38c45107b07dd560fa98b179aa5b2d4ff2e0017817c0e9213dd7 3102 
cockpit_220-1.dsc
 afc82acc8ef9d51e0f34265a07a2f059f5b71a1df721b299e657a40a098cbb7f 13324848 
cockpit_220.orig.tar.xz
 3dd3c10edc4dae0bfc087b9f68e9e5d3715d192fc40de424a61ba0083bcd5789 16876 
cockpit_220-1.debian.tar.xz
 51c8606c858e99f961cd07b8ec7ed66d472336be0d5efc559b27880ad0e5dcff 9303 
cockpit_220-1_source.buildinfo
Files:
 84a30594aabe6e9c555e84cd01ce8fd2 3102 admin optional cockpit_220-1.dsc
 beb88d8e70ee1da6ebd917c956217803 13324848 admin optional 
cockpit_220.orig.tar.xz
 9f4ef1f3f99d0846fe7b4a14fc3941d7 16876 admin optional 
cockpit_220-1.debian.tar.xz
 98f00c9a9f99b05cd8730799f606db54 9303 admin optional 
cockpit_220-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPbRrVe+lnUDmIyFI0U7xXa/hE0cFAl7PRpwACgkQ0U7xXa/h
E0c68hAAhIPcOu3/fNHQ6Td/P5qetes3vo01rvf3aRRp463SjaFNjg7jAf1dX0cY
yNu4PaePvVG8FZI3U/sqKTq0X5j7r+XGDOyJ/+fX7HcjIt33zBlB6ct54V9oqsBl
27OpxA9bBQWZqvwbZTWROSHAGwoRMmyW836O4hZWB+N4e5tBeYFyalVT5ploZeVf
A3EOSZOQWawQBxlatl6Bx67fk+TcT6GV0xKgRfpKnnBX/cyeGSVZVet8Wr02z9mG
AvI5JP5hAsuyJ/8we8njoQLtzb8Qq5TB+UhWxPc/EL7/e7ppnKw11BtbA26yi8iS
RFPMYlsSrC8HLS5QzZ7wrGSqpXG9kbin5jf3a1RhQk6peu2uow1FRpM6zZ0K44Rh
HJqFAkGkyKixIZJrP1i9T1GCfUow2zgsnusXbRgFX2aoVGrBOsOkOR4nTGPjgfpR
j/t3

Bug#961415: marked as done (symfony: CVE-2020-5275 CVE-2020-5274 CVE-2020-5255)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 04:33:44 +
with message-id 
and subject line Bug#961415: fixed in symfony 4.4.8-1
has caused the Debian Bug report #961415,
regarding symfony: CVE-2020-5275 CVE-2020-5274 CVE-2020-5255
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.)


-- 
961415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symfony
Version: 4.4.4-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for symfony.

CVE-2020-5275[0]:
| In symfony/security-http before versions 4.4.7 and 5.0.7, when a
| `Firewall` checks access control rule, it iterate overs each rule's
| attributes and stops as soon as the accessDecisionManager decides to
| grant access on the attribute, preventing the check of next attributes
| that should have been take into account in an unanimous strategy. The
| accessDecisionManager is now called with all attributes at once,
| allowing the unanimous strategy being applied on each attribute. This
| issue is patched in versions 4.4.7 and 5.0.7.


CVE-2020-5274[1]:
| In Symfony before versions 5.0.5 and 4.4.5, some properties of the
| Exception were not properly escaped when the `ErrorHandler` rendered
| it stacktrace. In addition, the stacktrace were displayed even in a
| non-debug configuration. The ErrorHandler now escape alls properties
| of the exception, and the stacktrace is only display in debug
| configuration. This issue is patched in symfony/http-foundation
| versions 4.4.5 and 5.0.5


CVE-2020-5255[2]:
| In Symfony before versions 4.4.7 and 5.0.7, when a `Response` does not
| contain a `Content-Type` header, affected versions of Symfony can
| fallback to the format defined in the `Accept` header of the request,
| leading to a possible mismatch between the response's content
| and `Content-Type` header. When the response is cached, this can
| prevent the use of the website by other users. This has been patched
| in versions 4.4.7 and 5.0.7.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-5275
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5275
[1] https://security-tracker.debian.org/tracker/CVE-2020-5274
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5274
[2] https://security-tracker.debian.org/tracker/CVE-2020-5255
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5255

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: symfony
Source-Version: 4.4.8-1
Done: =?utf-8?q?David_Pr=C3=A9vot?= 

We believe that the bug you reported is fixed in the latest version of
symfony, 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.
David Prévot  (supplier of updated symfony 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, 27 May 2020 14:34:35 -1000
Source: symfony
Architecture: source
Version: 4.4.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 952431 961415
Changes:
 symfony (4.4.8-1) unstable; urgency=medium
 .
   [ Fabien Potencier ]
   * updated VERSION for 4.4.8, fixes security issues (Closes: #961415)
 .
   [ Robin Chalas ]
   * [Security] Fix access_control behavior with unanimous decision strategy
 [CVE-2020-5275]
 .
   [ Yonel Ceruto ]
   * [HttpFoundation] Do not set the default Content-Type based on the Accept
 header [CVE-2020-5255]
 .
   [ Jérémy Derussé ]
   * Escape variable in Exception Template [CVE-2020-5274]
 .
   [ David Prévot ]
   * Use debhelper-compat 13
   * Simplify override_dh_auto_test
   * Workaround failing tests with php7.4 (Closes: #952431)
Checksums-Sha1:
 053594561c0cd0fe9c53dffaa32cddeaa4d6d74a 7745 symfony_4.4.8-1.dsc
 aed8a6e1814a7df97acf5b1fc211e3d9734ac29f 4124496 symfony_4.4.8.orig.tar.xz
 5ff84e625f8b05965ca3a43e091ced5381bf3f04 47316 symfony_4.4.8-1.debian.tar.xz
 a619f

Bug#943135: marked as done (numba: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 04:18:56 +
with message-id 
and subject line Bug#943135: fixed in numba 0.48.0-2
has caused the Debian Bug report #943135,
regarding numba: 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.)


-- 
943135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numba
Version: 0.42.0-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_take2.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: numba
Source-Version: 0.48.0-2
Done: Drew Parsons 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 May 2020 12:01:21 +0800
Source: numba
Architecture: source
Version: 0.48.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 943135
Changes:
 numba (0.48.0-2) unstable; urgency=medium
 .
   * Team upload.
   * drop Recommends: python-numba from numba-doc, remove python-numba
 tests from debian/tests. Closes: #943135.
   * run debian/tests over all supported python versions
Checksums-Sha1:
 52f8a26ee90bde6f1c75c9f6b47fb6e224800a1f 2219 numba_0.48.0-2.dsc
 53c6b5dcd33e1130d9919cba5261ae79725e45de 7560 numba_0.48.0-2.debian.tar.xz
 4c8ee35d07dcf489b1fbc3d907aa3e092385a5bd 8174 numba_0.48.0-2_source.buildinfo
Checksums-Sha256:
 f1dea1b20830e262eec9f027871dcb5fb2c3afedf945e13180d0bd91b08f1e3a 2219 
numba_0.48.0-2.dsc
 5db8340fc5cb0cca37ebf149a30def2ef8d6f51ab3da5c3563a79699db4247c8 7560 
numba_0.48.0-2.debian.tar.xz
 3b5b9e8e52ceb95394dea8e1bcdd1446cc8c52add62fa8afc895e741bbe6dcc1 8174 
numba_0.48.0-2_source.buildinfo
Files:
 62dea2663e6a92c85437d5b523e75636 2219 science optional numba_0.48.0-2.dsc
 0c420efe5a8ba3eaf761a2000d0d9409 7560 science op

Bug#961691: linux-image-5.6.0-1-amd64: System hangs all the time

[Igor Liferenko]

Package: src:linux
Version: 5.6.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since upgrade of 2020-05-18 system started to hang all the time without any 
reason,
forcing me to reboot computer each time loosing my work.

-- Package-specific info:
** Version:
Linux version 5.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-11)) #1 SMP Debian 5.6.7-1 (2020-04-29)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.6.0-1-amd64 
root=UUID=284f2b06-aeb5-4d51-bffe-ddb426f4c63f ro

** Not tainted

** Kernel log:
[   10.387864] systemd[1]: Mounted Huge Pages File System.
[   10.390388] systemd[1]: Mounted POSIX Message Queue File System.
[   10.394777] systemd[1]: Mounted Kernel Debug File System.
[   10.399670] systemd[1]: Mounted Kernel Trace File System.
[   10.404568] systemd[1]: Finished Create list of static device nodes for the 
current kernel.
[   10.427001] RPC: Registered named UNIX socket transport module.
[   10.429045] RPC: Registered udp transport module.
[   10.431114] RPC: Registered tcp transport module.
[   10.433100] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   10.437145] systemd[1]: Mounted RPC Pipe File System.
[   10.440980] systemd[1]: Starting pNFS block layout mapping daemon...
[   10.487925] systemd[1]: Finished Load Kernel Modules.
[   10.490130] systemd[1]: Condition check resulted in FUSE Control File System 
being skipped.
[   10.490243] systemd[1]: Condition check resulted in Kernel Configuration 
File System being skipped.
[   10.493417] systemd[1]: Starting Apply Kernel Variables...
[   10.516173] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   10.522665] systemd[1]: Finished Remount Root and Kernel File Systems.
[   10.525011] systemd[1]: Started pNFS block layout mapping daemon.
[   10.646829] systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
[   10.648586] systemd[1]: Condition check resulted in Platform Persistent 
Storage Archival being skipped.
[   10.651696] systemd[1]: Starting Load/Save Random Seed...
[   10.655199] systemd[1]: Starting Create System Users...
[   10.779957] systemd[1]: Finished udev Coldplug all Devices.
[   10.816807] systemd[1]: Starting Helper to synchronize boot up for 
ifupdown...
[   10.828057] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[   10.831924] systemd[1]: Mounted NFSD configuration filesystem.
[   10.860106] systemd[1]: Finished Apply Kernel Variables.
[   10.930500] systemd[1]: Finished Load/Save Random Seed.
[   11.041107] systemd[1]: Finished Set the console keyboard layout.
[   11.050969] systemd[1]: Finished Create System Users.
[   11.056564] systemd[1]: Starting Create Static Device Nodes in /dev...
[   11.090135] systemd[1]: Started Journal Service.
[   11.119693] systemd-journald[258]: Received client request to flush runtime 
journal.
[   11.379257] systemd-journald[258]: File 
/var/log/journal/a7cfea2033ec4c4182a6354cbc46c69c/system.journal corrupted or 
uncleanly shut down, renaming and replacing.
[   13.136231] parport_pc 00:03: reported by Plug and Play ACPI
[   13.137946] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[   13.377785] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   13.516053] ppdev: user-space parallel port driver
[   13.556030] iTCO_vendor_support: vendor-support=0
[   13.645501] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   13.647259] iTCO_wdt: Found a ICH10 TCO device (Version=2, TCOBASE=0x0860)
[   13.649190] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   14.563063] intel_powerclamp: No package C-state available
[   14.605586] intel_powerclamp: No package C-state available
[   14.641855] intel_powerclamp: No package C-state available
[   14.680160] intel_powerclamp: No package C-state available
[   15.115708] snd_hda_codec_via hdaudioC0D0: autoconfig for VT1708S: 
line_outs=4 (0x1c/0x19/0x22/0x23/0x0) type:line
[   15.117461] snd_hda_codec_via hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   15.119133] snd_hda_codec_via hdaudioC0D0:hp_outs=1 
(0x1d/0x0/0x0/0x0/0x0)
[   15.120838] snd_hda_codec_via hdaudioC0D0:mono: mono_out=0x0
[   15.122623] snd_hda_codec_via hdaudioC0D0:dig-out=0x20/0x0
[   15.124284] snd_hda_codec_via hdaudioC0D0:inputs:
[   15.125939] snd_hda_codec_via hdaudioC0D0:  Rear Mic=0x1a
[   15.127550] snd_hda_codec_via hdaudioC0D0:  Front Mic=0x1e
[   15.129180] snd_hda_codec_via hdaudioC0D0:  Line=0x1b
[   15.130763] snd_hda_codec_via hdaudioC0D0:  CD=0x1f
[   15.132384] Adding 2539516k swap on /dev/sda2.  Priority:-2 extents:1 
across:2539516k FS
[   15.148279] input: HDA Intel Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[   15.150830] input: HDA Intel Front Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   15.153555] input: HDA Intel Line as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   15.156024] input: HDA Intel Line Out Front as 
/devices/pci000

Bug#921926: marked as done (pki-base: Does not work with Java 11)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 23:33:36 +
with message-id 
and subject line Bug#921926: fixed in dogtag-pki 10.9.0~a1-1
has caused the Debian Bug report #921926,
regarding pki-base: Does not work with Java 11
to be marked as done.

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

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


-- 
921926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pki-base
Severity: grave
Tags: upstream
Justification: renders package unusable

Upstream needs to port Dogtag to TLS1.3 & Java11 before pkispawn is able to 
configure the instance. Upstream ticket at:

https://pagure.io/dogtagpki/issue/3088

It's unlikely that this will be fixed before Fedora has switched to Java11, 
which might happen in Fedora 31 but not before.
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.9.0~a1-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated dogtag-pki package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 May 2020 02:16:42 +0300
Source: dogtag-pki
Architecture: source
Version: 10.9.0~a1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 920725 921926
Changes:
 dogtag-pki (10.9.0~a1-1) experimental; urgency=medium
 .
   * New upstream prerelease.
   * watch: Updated.
   * patches: Refreshed.
   * control, rules: Build with default-jdk, bump jss, tomcatjss
 dependencies. (Closes: #920725, #921926)
   * control: Add libcommons-net-java to depends.
   * fix-javadoc-build.diff: Fix building the javadoc.
   * install: Updated, nsutil got folded in cmsutil.
   * copyright: Don't exclude the fonts.
Checksums-Sha1:
 aa94b0fb98e16996732b75815d54c3f6fa20c600 3823 dogtag-pki_10.9.0~a1-1.dsc
 c8b1d47713f145ce3e3446b5a5c1cba6d1b99ae1 5671832 
dogtag-pki_10.9.0~a1.orig.tar.xz
 82ac55d5d37f5d54913229f9f4665c053ffdd4c5 31192 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 de66edcd71be6fa03fe46ef5bfcd71a5e67baea6 14677 
dogtag-pki_10.9.0~a1-1_source.buildinfo
Checksums-Sha256:
 f86e0544bfb49be8dcb94de83245e485f82f643340f10d3b00452f3da1bed4f7 3823 
dogtag-pki_10.9.0~a1-1.dsc
 bfb7c2d243844ccfce2e98633fa8659b5033e5046fedd1ec34c24755b22bc18d 5671832 
dogtag-pki_10.9.0~a1.orig.tar.xz
 aaae87de3a14eda70f370b9d74c9fd2f56eba2338eb9b5e9608c871a63a9d48f 31192 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 4c230c426a4a0cac1d5abfd06b3d62ded0bb149baf28b519b85f25a3d976727e 14677 
dogtag-pki_10.9.0~a1-1_source.buildinfo
Files:
 6f053471a65a320d327dd3e7b4431569 3823 java optional dogtag-pki_10.9.0~a1-1.dsc
 8fa625a301b3d2ce9bd9973c903c9e9d 5671832 java optional 
dogtag-pki_10.9.0~a1.orig.tar.xz
 f49b480bd54359fe3c090a7b43f5276d 31192 java optional 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 f6049589714054238edec8b3e695f7e7 14677 java optional 
dogtag-pki_10.9.0~a1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl7O9Q0ACgkQy3AxZaiJ
hNwCbw//UaiV+n+fa40XuWFisgr5u0cKas4ACDsTvSaUZOe92Dfznam+Nm7SyT4o
/fCVKew+14wlU6x3q+14lke6jaF+E5g6Lskqk0EsA4FQKWRYHvyNvj8Oo0evvvDn
6jpZ21nar8JwlbLJNevDAjFooahHTwjvg66XhvZfOTkPJ5Yeq4CHU8vdhyG8zGvT
c48EBK4nHe12NZreAFYDnKzhNzduUQ+Wbsk0rQJJnNOT0IohOgZpgZvB/ztqV9iW
Js8V3qkY9chnMETMlBTkA+WOAFH/MUuflV4Tm1qa+CrJfQupdZbHHJM1NJhNokox
RhYNJtUlI+Jc0bdLdF4nMQvn0n76rPvZEeX9cMIgE6LPqWOa8ViY7aVMKsbeS0mN
FjDCcN1PbgD2W6ZyRTtT800+4FLZc6AGB4t8uTmVfPI9+sCGrVuGDvPN32hdOG+R
w+GnoimuodvQtrmOL94FEht3zD1/EJKbpOPw6Dx4c41KCo2uZj/ATsY+FlAZRr4h
I8Fe4N6mj/qMVZ0w1Ismc1rdUIxVLgkWvTcKS/IB/mxza5tO8CRzgJzXRzCJvheY
M2QqBbr/ZLtgBq11vojw6eDOXPecz6ZH0YJIQg+lgCJCKuDlAYsob3nzebC9r3Uk
KfW8wni7Vumyvyt+Njg6ToREow2uEAgzTCeyMuwvvHOY6esd0HM=
=Pz8Y
-END PGP SIGNATURE End Message ---

Bug#920725: marked as done (pki-base-java: Depends on openjdk-8-jre-headless which will not be in buster)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 23:33:36 +
with message-id 
and subject line Bug#920725: fixed in dogtag-pki 10.9.0~a1-1
has caused the Debian Bug report #920725,
regarding pki-base-java: Depends on openjdk-8-jre-headless which will not be in 
buster
to be marked as done.

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

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


-- 
920725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pki-base-java
Version: 10.6.8-2
Severity: serious
Control: block 920037 with -1

Hi,

buster will ship with openjdk-11 only.


Andreas
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.9.0~a1-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated dogtag-pki package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 May 2020 02:16:42 +0300
Source: dogtag-pki
Architecture: source
Version: 10.9.0~a1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 920725 921926
Changes:
 dogtag-pki (10.9.0~a1-1) experimental; urgency=medium
 .
   * New upstream prerelease.
   * watch: Updated.
   * patches: Refreshed.
   * control, rules: Build with default-jdk, bump jss, tomcatjss
 dependencies. (Closes: #920725, #921926)
   * control: Add libcommons-net-java to depends.
   * fix-javadoc-build.diff: Fix building the javadoc.
   * install: Updated, nsutil got folded in cmsutil.
   * copyright: Don't exclude the fonts.
Checksums-Sha1:
 aa94b0fb98e16996732b75815d54c3f6fa20c600 3823 dogtag-pki_10.9.0~a1-1.dsc
 c8b1d47713f145ce3e3446b5a5c1cba6d1b99ae1 5671832 
dogtag-pki_10.9.0~a1.orig.tar.xz
 82ac55d5d37f5d54913229f9f4665c053ffdd4c5 31192 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 de66edcd71be6fa03fe46ef5bfcd71a5e67baea6 14677 
dogtag-pki_10.9.0~a1-1_source.buildinfo
Checksums-Sha256:
 f86e0544bfb49be8dcb94de83245e485f82f643340f10d3b00452f3da1bed4f7 3823 
dogtag-pki_10.9.0~a1-1.dsc
 bfb7c2d243844ccfce2e98633fa8659b5033e5046fedd1ec34c24755b22bc18d 5671832 
dogtag-pki_10.9.0~a1.orig.tar.xz
 aaae87de3a14eda70f370b9d74c9fd2f56eba2338eb9b5e9608c871a63a9d48f 31192 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 4c230c426a4a0cac1d5abfd06b3d62ded0bb149baf28b519b85f25a3d976727e 14677 
dogtag-pki_10.9.0~a1-1_source.buildinfo
Files:
 6f053471a65a320d327dd3e7b4431569 3823 java optional dogtag-pki_10.9.0~a1-1.dsc
 8fa625a301b3d2ce9bd9973c903c9e9d 5671832 java optional 
dogtag-pki_10.9.0~a1.orig.tar.xz
 f49b480bd54359fe3c090a7b43f5276d 31192 java optional 
dogtag-pki_10.9.0~a1-1.debian.tar.xz
 f6049589714054238edec8b3e695f7e7 14677 java optional 
dogtag-pki_10.9.0~a1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl7O9Q0ACgkQy3AxZaiJ
hNwCbw//UaiV+n+fa40XuWFisgr5u0cKas4ACDsTvSaUZOe92Dfznam+Nm7SyT4o
/fCVKew+14wlU6x3q+14lke6jaF+E5g6Lskqk0EsA4FQKWRYHvyNvj8Oo0evvvDn
6jpZ21nar8JwlbLJNevDAjFooahHTwjvg66XhvZfOTkPJ5Yeq4CHU8vdhyG8zGvT
c48EBK4nHe12NZreAFYDnKzhNzduUQ+Wbsk0rQJJnNOT0IohOgZpgZvB/ztqV9iW
Js8V3qkY9chnMETMlBTkA+WOAFH/MUuflV4Tm1qa+CrJfQupdZbHHJM1NJhNokox
RhYNJtUlI+Jc0bdLdF4nMQvn0n76rPvZEeX9cMIgE6LPqWOa8ViY7aVMKsbeS0mN
FjDCcN1PbgD2W6ZyRTtT800+4FLZc6AGB4t8uTmVfPI9+sCGrVuGDvPN32hdOG+R
w+GnoimuodvQtrmOL94FEht3zD1/EJKbpOPw6Dx4c41KCo2uZj/ATsY+FlAZRr4h
I8Fe4N6mj/qMVZ0w1Ismc1rdUIxVLgkWvTcKS/IB/mxza5tO8CRzgJzXRzCJvheY
M2QqBbr/ZLtgBq11vojw6eDOXPecz6ZH0YJIQg+lgCJCKuDlAYsob3nzebC9r3Uk
KfW8wni7Vumyvyt+Njg6ToREow2uEAgzTCeyMuwvvHOY6esd0HM=
=Pz8Y
-END PGP SIGNATURE End Message ---

Bug#961398: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on mipsel

[Dirk Eddelbuettel]

Paul,

Shall I close this one 'by hand'?  Or will it get closed by migrating
quantlib-swig?  I just close the other one (#956830) that was at the start of
this by hand.

Best,  Dirk

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

Bug#956830: marked as done (quantlib-swig: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 18:12:41 -0500
with message-id <24270.62441.723302.256...@rob.eddelbuettel.com>
and subject line Re: Bug#956830: quantlib-swig: FTBFS on mipsel
has caused the Debian Bug report #956830,
regarding quantlib-swig: FTBFS on mipsel
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.)


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

The last upload of quantlib-swig failed to build on mipsel:
https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig&arch=mipsel&ver=1.18-1&stamp=1586885285&raw=0

Cheers
-- 
Sebastian Ramacher


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

On 15 April 2020 at 14:13, Dirk Eddelbuettel wrote:
| 
| On 15 April 2020 at 20:44, Sebastian Ramacher wrote:
| | Source: quantlib-swig
| | Version: 1.18-1
| | Severity: serious
| | Tags: ftbfs sid bullseye
| | Justification: fails to build from source (but built successfully in the 
past)
| 
| Yes ... but it also failed before. See e.g. #909725 (per a quick scan in my
| debian-bugs folder).
| 
| Can you possibly try a fix (in dialing down down compiler greedyness, and/or
| give the builder a bigger allocation) as the error is
| 
|virtual memory exhausted: Cannot allocate memory

That has been taken care of via #961555:

  From: Debian FTP Masters 
  To: 961555-cl...@bugs.debian.org
  Cc: quantlib-s...@packages.debian.org 
  Subject: Bug#961555: Removed package(s) from unstable
  Date: Tue, 26 May 2020 17:22:25 +

  We believe that the bug you reported is now fixed; the following
  package(s) have been removed from unstable:

  quantlib-python | 1.17-1 | mipsel

  --- Reason ---
  ROM; old now unbuildable binaries
  --

Dirk


| 
| Dirk
| 
| | 
| | The last upload of quantlib-swig failed to build on mipsel:
| | 
https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig&arch=mipsel&ver=1.18-1&stamp=1586885285&raw=0
| | 
| | Cheers
| | -- 
| | Sebastian Ramacher
| | [DELETED ATTACHMENT signature.asc, application/pgp-signature]
| 
| -- 
| http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

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

Bug#948087: future of aufs in Debian.

[Tianon Gravi]

On Wed, 27 May 2020 at 14:33, Noah Meyerhans  wrote:
> Docker no longer users aufs by default, though, having switched to
> overlayfs some time ago.  I'm sure we could get them to drop the
> Recommends if we're considering getting rid of it.

This is something I'd been considering for quite a while now and
hadn't gotten around to, so thanks for the push!  I've filed [1] now.
:)

[1]: https://github.com/docker/docker-ce-packaging/pull/472

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#961684: marked as done (lintian: exits with error: Can't use an undefined value as a HASH reference)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 22:18:49 +
with message-id 
and subject line Bug#961684: fixed in lintian 2.77.1
has caused the Debian Bug report #961684,
regarding lintian: exits with error: Can't use an undefined value as a HASH 
reference
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.)


-- 
961684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.77.0
Severity: grave
Justification: renders package unusable

Hello,
while attempting to check a just built package within my sid
pbuilder-managed chroot enviroment, I see that lintian is no
longer working.
Please note that lintian/2.76.0 was working fine in the same
environment.

Attempting to check the package with the following command:

  # su -p pbuser -c "lintian -viF $PACKAGE.changes"
  Can't use an undefined value as a HASH reference at 
/usr/share/lintian/commands/lintian.pm line 831.

exits immediately with the above shown error message.
Same exact misbehavior with:

  # su -p pbuser -c "lintian -EviIL +pedantic $PACKAGE.changes"

I would say that this renders lintian unusable, hence the
'grave' severity of the bug report.

Please fix this issue.
Thanks for your time and dedication!


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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=en_US:en (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages lintian depends on:
ii  binutils 2.34-8
ii  bzip21.0.8-3
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-5
ii  gettext  0.19.8.1-10
ii  gpg  2.2.20-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b3
ii  libarchive-zip-perl  1.68-1
ii  libcapture-tiny-perl 0.48-1
ii  libclass-xsaccessor-perl 1.19-3+b4
ii  libclone-perl0.45-1
ii  libconfig-tiny-perl  2.24-1
ii  libcpanel-json-xs-perl   4.19-1
ii  libdevel-size-perl   0.83-1+b1
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libhtml-parser-perl  3.72-5
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libjson-maybexs-perl 1.004002-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmoo-perl  2.004000-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.112-1
ii  libsereal-decoder-perl   4.011+ds-1
ii  libsereal-encoder-perl   4.011+ds-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3300-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.010001-1
ii  libunicode-utf8-perl 0.62-1+b1
ii  liburi-perl  1.76-2
ii  libxml-libxml-perl   2.0134+dfsg-2
ii  libxml-writer-perl   0.625-1
ii  libyaml-libyaml-perl 0.82+repack-1
ii  man-db   2.9.1-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.2-1
ii  t1utils  1.41-4
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
pn  libtext-template-perl  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.77.1
Done: Chris Lamb 

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

(This message was generated automatically at their request; if you
bel

Processed: Bug#961684 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #961684 [lintian] lintian: exits with error: Can't use an undefined value 
as a HASH reference
Added tag(s) pending.

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

Bug#961684: marked as pending in lintian

[Felix Lechner]

Control: tag -1 pending

Hello,

Bug #961684 in lintian 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/lintian/lintian/-/commit/db5e8f83357f4a6588f16be46c959f44345c375f


Deal gracefully with empty configuration files. (Closes: #961684)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961684

Bug#961684: lintian: exits with error: Can't use an undefined value as a HASH reference

[Francesco Poli (wintermute)]

Package: lintian
Version: 2.77.0
Severity: grave
Justification: renders package unusable

Hello,
while attempting to check a just built package within my sid
pbuilder-managed chroot enviroment, I see that lintian is no
longer working.
Please note that lintian/2.76.0 was working fine in the same
environment.

Attempting to check the package with the following command:

  # su -p pbuser -c "lintian -viF $PACKAGE.changes"
  Can't use an undefined value as a HASH reference at 
/usr/share/lintian/commands/lintian.pm line 831.

exits immediately with the above shown error message.
Same exact misbehavior with:

  # su -p pbuser -c "lintian -EviIL +pedantic $PACKAGE.changes"

I would say that this renders lintian unusable, hence the
'grave' severity of the bug report.

Please fix this issue.
Thanks for your time and dedication!


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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=en_US:en (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages lintian depends on:
ii  binutils 2.34-8
ii  bzip21.0.8-3
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-5
ii  gettext  0.19.8.1-10
ii  gpg  2.2.20-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b3
ii  libarchive-zip-perl  1.68-1
ii  libcapture-tiny-perl 0.48-1
ii  libclass-xsaccessor-perl 1.19-3+b4
ii  libclone-perl0.45-1
ii  libconfig-tiny-perl  2.24-1
ii  libcpanel-json-xs-perl   4.19-1
ii  libdevel-size-perl   0.83-1+b1
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libhtml-parser-perl  3.72-5
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libjson-maybexs-perl 1.004002-1
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmoo-perl  2.004000-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.112-1
ii  libsereal-decoder-perl   4.011+ds-1
ii  libsereal-encoder-perl   4.011+ds-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3300-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.010001-1
ii  libunicode-utf8-perl 0.62-1+b1
ii  liburi-perl  1.76-2
ii  libxml-libxml-perl   2.0134+dfsg-2
ii  libxml-writer-perl   0.625-1
ii  libyaml-libyaml-perl 0.82+repack-1
ii  man-db   2.9.1-1
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.2-1
ii  t1utils  1.41-4
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
pn  libtext-template-perl  

-- no debconf information

Bug#948087: future of aufs in Debian.

[Noah Meyerhans]

On Tue, May 26, 2020 at 05:10:10PM +0300, Adrian Bunk wrote:
> > Adrian filed a rc bug in November 2019 which received no maintainer 
> > response, however the package was not autoremoved from testing due to aufs 
> > and aufs-tools being considered a "key packages" due to high popcon. This 
> > popcon actually seems to be growing in both absolute and percentage terms. 
> > I presume the high popcon is due to some deriviative (hence 
> > debian-derivatives and debian-live in cc) using aufs in their live image 
> > builds (as far as I can tell debian's own live images seem to use overlayfs 
> > instead nowadays).
> >...
> 
> It doesn't have to be a derivative, one webhoster who installs popcon by 
> default is enough.

It's very possible that it is the upstream Docker packaging that
accounts for the upward trend.  The docker.io packages in the Debian
archive list aufs-tools as "Suggests", so they won't be pulled in by
default, but the upstream docker-ce packages distributed directly by
Docker still have them at Recommends.

Docker no longer users aufs by default, though, having switched to
overlayfs some time ago.  I'm sure we could get them to drop the
Recommends if we're considering getting rid of it.

noah

Bug#867775: marked as done (golang-github-optiopay-kafka FTBFS: FAIL: TestProduceRequest)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 21:03:35 +
with message-id 
and subject line Bug#867775: fixed in golang-github-optiopay-kafka 2.1.1-1
has caused the Debian Bug report #867775,
regarding golang-github-optiopay-kafka FTBFS: FAIL: TestProduceRequest
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.)


-- 
867775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-optiopay-kafka
Version: 0.0~git20150921.0.bc8e095-1
Severity: serious

Some recent change in unstable makes golang-github-optiopay-kafka FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-optiopay-kafka.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-optiopay-kafka.html

...
--- FAIL: TestProduceRequest (0.00s)
messages_test.go:174: expected different bytes representation: 
[]byte{0x0, 0x0, 0x0, 0x6d, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xf1, 0x0, 0x4, 
0x74, 0x65, 0x73, 0x74, 0xff, 0xff, 0x0, 0x0, 0x3, 0xe8, 0x0, 0x0, 0x0, 0x1, 
0x0, 0x3, 0x66, 0x6f, 0x6f, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x44, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x38, 0x8a, 
0xa7, 0x46, 0xe2, 0x0, 0x1, 0xff, 0xff, 0xff, 0xff, 0x0, 0x0, 0x0, 0x2a, 0x1f, 
0x8b, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xff, 0x62, 0x40, 0x0, 0x91, 0x1d, 
0xbb, 0xe2, 0xc3, 0xc1, 0x2c, 0xe6, 0xb4, 0xfc, 0x7c, 0x10, 0x95, 0x94, 0x58, 
0x4, 0x8, 0x0, 0x0, 0xff, 0xff, 0xa0, 0xbc, 0x10, 0xc2, 0x20, 0x0, 0x0, 0x0}
...
FAIL
FAILgithub.com/optiopay/kafka/proto 0.010s
dh_auto_test: go test -v -p 15 github.com/optiopay/kafka 
github.com/optiopay/kafka/integration github.com/optiopay/kafka/kafkatest 
github.com/optiopay/kafka/proto returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-github-optiopay-kafka
Source-Version: 2.1.1-1
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-optiopay-kafka package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 24 May 2020 18:04:05 +0530
Source: golang-github-optiopay-kafka
Architecture: source
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Nilesh Patra 
Closes: 867775
Changes:
 golang-github-optiopay-kafka (2.1.1-1) unstable; urgency=medium
 .
   * Team Upload.
 .
   [Alexandre Viau]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [Nilesh Patra]
   * Fix watch as per github tags
   * New upstream version 2.1.1 (Closes: #867775)
   * Update Build-Deps
   * Skip tests needing TLS connection
   * Add upstream/metadata
   * Fix with cme
   * Add "Rules-Requires-Root:no"
Checksums-Sha1:
 c423910ef03807c7ffb3c6a92ddc5e13679ebd7d 2334 
golang-github-optiopay-kafka_2.1.1-1.dsc
 edacca0b9bcfa7cd96d904fc5a15607c8e8ba81a 90978 
golang-github-optiopay-kafka_2.1.1.orig.tar.gz
 ae944f89f750f56d9a0d49ebaaad569138ba209c 3040 
golang-github-optiopay-kafka_2.1.1-1.debian.tar.xz
 310e9ff34ef38dd336a3c1bab255110d3f08685b 19301 
golang-github-optiopay-kafka_2.1.1-1_amd64.buildinfo
Checksums-Sha256:
 5c4dbf844775a2da54185ef645bea026d4d66491b8e8cc65b69c63803c4d7531 2334 
golang-github-optiopay-kafka_2.1.1-1.dsc
 f623374e1041329c99ae99d9902d554418239e983198b8b418a73b193e9ec069 90978 
golang-github-optiopay-kafka_2.1.1.orig.tar.gz
 f8bb13da6994c970a376fa3f53751197997730df2aa273c12587bba3559216fd 3040 
golang-github-optiopay-kafka_2.1.1-1.debian.tar.xz
 135b6ad174ba3b58cef008f3654bf0161f797594e0fcf808fb7431d1ff1d75c6 19301 
golang-github-optiopay-kafka_2.1.1-1_amd64.buildinfo
Files:
 f93d68b6a2323d612d9898a4bf6ca150 2334 devel optional 
golang-github-optiopay-kafka_2.1.1-1.dsc
 61f393b225498d50ea36d33aba0340db 90978 devel optional 
golang-github-optiopay-kafka_2.1.1.orig.tar.gz
 7231a5c07ffa7c0d161854547f7e11d5 3040 devel optiona

Bug#961591: marked as done (r-bioc-graph: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 20:37:16 +
with message-id 
and subject line Bug#961591: fixed in r-bioc-graph 1.66.0-2
has caused the Debian Bug report #961591,
regarding r-bioc-graph: autopkgtest regression
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.)


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

Hi Maintainer

Since the upload of 1.66.0-1, r-bioc-graph has been failing its own
autopkgtests [1].   This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-graph/unstable/amd64/


> BiocGenerics:::testPackage("graph", pattern="_test.R")

Attaching package: ‘BiocGenerics’

The following objects are masked from ‘package:parallel’:

clusterApply, clusterApplyLB, clusterCall, clusterEvalQ,
clusterExport, clusterMap, parApply, parCapply, parLapply,
parLapplyLB, parRapply, parSapply, parSapplyLB

The following objects are masked from ‘package:stats’:

IQR, mad, sd, var, xtabs

The following objects are masked from ‘package:base’:

anyDuplicated, append, as.data.frame, basename, cbind, colnames,
dirname, do.call, duplicated, eval, evalq, Filter, Find, get, grep,
grepl, intersect, is.unsorted, lapply, Map, mapply, match, mget,
order, paste, pmax, pmax.int, pmin, pmin.int, Position, rank,
rbind, Reduce, rownames, sapply, setdiff, sort, table, tapply,
union, unique, unsplit, which, which.max, which.min

Timing stopped at: 0.002 0 0.002
Error in checkEquals("not a node: 'not-a-node'", conditionMessage(ans)) :
  1 string mismatch



RUNIT TEST PROTOCOL -- Tue May 26 07:01:18 2020
***
Number of test functions: 206
Number of errors: 0
Number of failures: 1


1 Test Suite :
graph RUnit Tests - 206 test functions, 0 errors, 1 failure
FAILURE in testInEdges: Error in checkEquals("not a node:
'not-a-node'", conditionMessage(ans)) :
  1 string mismatch


Test files with failing tests

   graphNEL_test.R
 testInEdges


Error in BiocGenerics:::testPackage("graph", pattern = "_test.R") :
  unit tests failed for package graph
Execution halted
autopkgtest [07:01:18]: test pkg-r-autopkgtest: ---]
autopkgtest [07:01:18]: test pkg-r-autopkgtest:  - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-bioc-graph
Source-Version: 1.66.0-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
r-bioc-graph, 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.
Nilesh Patra  (supplier of updated r-bioc-graph 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, 27 May 2020 21:45:43 +0200
Source: r-bioc-graph
Architecture: source
Version: 1.66.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 961591
Changes:
 r-bioc-graph (1.66.0-2) unstable; urgency=medium
 .
   * Team Upload.
 .
   [ Dylan Aïssi ]
   * Fix tab-in-license-text
 .
   [ Nilesh Patra ]
   * Fix incompatible unicode (Closes: #961591)
   * Bump compat version to 13
Checksums-Sha1:
 ded1330286dc937e56c0810ae8e8a151c263b011 2103 r-bioc-graph_1.66.0-2.dsc
 ad723728d52cc14cdda46c98093300e20313e7f5 4960 
r-bioc-graph_1.66.0-2.debian.tar.xz
 bb3c2ffd729b4ae935f2fa7f552b1a2f6e57be45 8747 
r-bioc-graph_1.66.0-2_amd64.buildinfo
Checksums-Sha256:
 0d52e578ac5407a5151bedac7c2ba23ddd9c7a6698113562952c5ee95e87a222 2103 
r-bioc-graph_1.66.0-2.dsc
 4ed176c16d160e5563b07331648c6ea417f6dadfc18476ace36b099477f63801 4960 
r-bioc-graph_1.66.0-2.debian.tar.xz
 c9d1335a90c49740c8b91248fadf604693aaafcab2107296a9852061e17bd723 8747 
r-bioc-graph_1.66.0-2_amd64.buildinfo
Files:
 083b2bd6c9a1781acc614502

Bug#961591: [RFS] r-bioc-graph

[Nilesh Patra]

On Thu, 28 May 2020, 01:43 Dylan Aïssi,  wrote:

> Hi,
>
> Le mer. 27 mai 2020 à 20:04, Nilesh Patra  a écrit :
> >
> > The second test (needing the library) failed on gitlab-ci, w/o adding
> r-cran-xml and r-cran-runit, possible because this doesn't pick up depends
> from test-depends.
> > This passed on my local machine though. Since I wanted to be sure, I
> moved this there.
>
> There is probably a bug on the salsa-ci side, because both tests
> passed on my computer. Let's skip salsa-ci for now.
>

Ahh, alrighty.


> I have moved back these dependencies to test-deps and I have updated
> your patch (str_replace_all --> gsub) to not add a new dependency.
>

That's good, and makes sense. I didn't know about this, possibly because I
don't speak R :P


> You probably already noticed, the debian/test/control files for R
> packages require a lot of manual work to keep the list of test-deps
> up-to-date. Because I don't want to do this manually, I moved the code
> to tests these packages into pkg-r-autopkgtest. The list of test-deps
> is automatically generated at run time from the DESCRIPTION file
>

That's nice!

Currently, it is enabled only for bioconductor packages, if there is
> no big bug with this transition, we will be able to remove the
> debian/test/control files and to enable this for other R packages.
>

Got it, thanks for the explanation.


> Thanks again for #961591.
>

:)
And thanks a lot for letting me have this upload (i.e. my name on d/ch for
this upload)

Kind regards,
Nilesh

>

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

[Markus Koschany]

Am 27.05.20 um 21:54 schrieb Thorsten Glaser:
[...]
> Thank you. Please also take care of buster.

I will take care of Buster eventually.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#961591: [RFS] r-bioc-graph

[Dylan Aïssi]

Hi,

Le mer. 27 mai 2020 à 20:04, Nilesh Patra  a écrit :
>
> The second test (needing the library) failed on gitlab-ci, w/o adding 
> r-cran-xml and r-cran-runit, possible because this doesn't pick up depends 
> from test-depends.
> This passed on my local machine though. Since I wanted to be sure, I moved 
> this there.

There is probably a bug on the salsa-ci side, because both tests
passed on my computer. Let's skip salsa-ci for now.

I have moved back these dependencies to test-deps and I have updated
your patch (str_replace_all --> gsub) to not add a new dependency.

You probably already noticed, the debian/test/control files for R
packages require a lot of manual work to keep the list of test-deps
up-to-date. Because I don't want to do this manually, I moved the code
to tests these packages into pkg-r-autopkgtest. The list of test-deps
is automatically generated at run time from the DESCRIPTION file.
Currently, it is enabled only for bioconductor packages, if there is
no big bug with this transition, we will be able to remove the
debian/test/control files and to enable this for other R packages.

Thanks again for #961591.

Best,
Dylan

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

[Thorsten Glaser]

Markus Koschany dixit:

>The mods-available directory is correct. Both conf and load file have to
>be installed into it but the file naming is wrong. httpd-jk.conf should
>be jk.conf.

OK, so the way it is in stretch is correct.

>Just renaming the file should be sufficient.

That plus renaming and retargetting the symlink.

Given that stretch has the same upstream version, just with a
different Debian revision, I think it makes sense to diff these
two and make the one in sid equivalent to the one in stretch
modulo changelog entries, and then upload that to buster as well.

>I will upload a new revision.

Thank you. Please also take care of buster.

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

Bug#931654: marked as done (node-json3: json3 is no more maintained)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 19:16:57 +
with message-id 
and subject line Bug#931653: Removed package(s) from unstable
has caused the Debian Bug report #931654,
regarding node-json3: json3 is no more maintained
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.)


-- 
931654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-json3
Severity: normal
Tags: security upstream

According to https://github.com/bestiejs/json3, node-json3 is no more
maintained and easy to replace by native JSON.parse/JSON.stringify
functions.

A ROM-RM issue is opened (#931653). This one will avoid testing
migration.
--- End Message ---
--- Begin Message ---
Version: 3.3.2-1+rm

Dear submitter,

as the package node-json3 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/931653

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#938860: marked as done (yagtd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 19:15:11 +
with message-id 
and subject line Bug#961626: Removed package(s) from unstable
has caused the Debian Bug report #938860,
regarding yagtd: 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.)


-- 
938860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yagtd
Version: 0.3.4-1.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.  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 the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:yagtd

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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 ---
Version: 0.3.4-1.1+rm

Dear submitter,

as the package yagtd 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/961626

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#902255: marked as done (llvm-toolchain-6.0: unicode non free license)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 19:16:27 +
with message-id 
and subject line Bug#916837: Removed package(s) from unstable
has caused the Debian Bug report #902255,
regarding llvm-toolchain-6.0: unicode non free license
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.)


-- 
902255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:llvm-toolchain-6.0
version: 1:6.0-3
severity: serious
control: affects -1 src:chromium-browser

LLVM includes ConvertUTF, which has a non free license.  See #823100,
#900596, etc.  Files affected are:

lib/Support/ConvertUTF.cpp
include/llvm/Support/ConvertUTF.h

Best wishes,
Mike
--- End Message ---
--- Begin Message ---
Version: 1:6.0.1-14.1+rm

Dear submitter,

as the package llvm-toolchain-6.0 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/916837

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#936928: marked as done (libtuxcap: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 19:14:43 +
with message-id 
and subject line Bug#961625: Removed package(s) from unstable
has caused the Debian Bug report #936928,
regarding libtuxcap: 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.)


-- 
936928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libtuxcap
Version: 1.4.0.dfsg2-2.3
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.  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 the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:libtuxcap

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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 ---
Version: 1.4.0.dfsg2-2.3+rm

Dear submitter,

as the package libtuxcap 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/961625

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#928813: marked as done (libapache2-mod-jk: Jk can not find any configured worker)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 18:49:47 +
with message-id 
and subject line Bug#928813: fixed in libapache-mod-jk 1:1.2.46-2
has caused the Debian Bug report #928813,
regarding libapache2-mod-jk: Jk can not find any configured worker
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.)


-- 
928813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: libapache2-mod-jk: Jk can not find any configured worker
Package: libapache2-mod-jk
Version: 1:1.2.46-1
Severity: important

Dear Maintainer,

any configured worker does not get found, following error messages appearing:

Could not find worker with name ajp13_worker

I found out that the config file for Jk module is not named correctly in 
/etc/apache2/mods-available. Name is httpd-jk.conf where it should have been 
jk.conf. Consequence is, that it does not get linked to mods-enabled directory 
on enabling Jk module. Also the link /etc/libapache2-mod-jk/httpd-jk.conf 
should point to the renamed file /etc/apache2/mods-availabl
e/jk.conf.



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

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

Versions of packages libapache2-mod-jk depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  libc6   2.28-10

libapache2-mod-jk recommends no packages.

Versions of packages libapache2-mod-jk suggests:
pn  libapache-mod-jk-doc  
ii  tomcat9   9.0.16-3

-- Configuration Files:
/etc/apache2/mods-available/httpd-jk.conf [Errno 2] Datei oder Verzeichnis 
nicht gefunden: '/etc/apache2/mods-available/httpd-jk.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libapache-mod-jk
Source-Version: 1:1.2.46-2
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libapache-mod-jk 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, 27 May 2020 19:19:20 +0200
Source: libapache-mod-jk
Architecture: source
Version: 1:1.2.46-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 928813
Changes:
 libapache-mod-jk (1:1.2.46-2) unstable; urgency=medium
 .
   * Rename httpd-jk.conf to jk.conf to restore compatibility with Debian's
 Apache helpers a2enmod and a2dismod. (Closes: #928813)
Checksums-Sha1:
 a194015d5623146080199cda4f30b6c50def8b7a 2297 libapache-mod-jk_1.2.46-2.dsc
 db92c6689a58be2f54d7a478a4dfb20526f7a5ba 60672 
libapache-mod-jk_1.2.46-2.debian.tar.xz
 2d038c9fa6d8ee5f489f088348024a386e0abe43 6950 
libapache-mod-jk_1.2.46-2_amd64.buildinfo
Checksums-Sha256:
 84472b6feeff1474c3aade826a41aebe13589f71417d676f830c8639c6f9b1ce 2297 
libapache-mod-jk_1.2.46-2.dsc
 3fd3a904033f1bb0dd798722349efc52a983b24862bc623a31559f38ad45c5aa 60672 
libapache-mod-jk_1.2.46-2.debian.tar.xz
 17515a895f5afb8e28e4e8cf80c16f27e924236dca7c4ed65bc27a8f6c1f6c63 6950 
libapache-mod-jk_1.2.46-2_amd64.buildinfo
Files:
 610c57262f733ba7a932d4a40c3f6f0d 2297 httpd optional 
libapache-mod-jk_1.2.46-2.dsc
 c3b933708be5e591a8622410857ffe69 60672 httpd optional 
libapache-mod-jk_1.2.46-2.debian.tar.xz
 da78b69fda07f2881eae2934433df42d 6950 httpd optional 
libapache-mod-jk_1.2.46-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl7OsPlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkXQkQAKRn7voqWy5AyX+xHmKa/85FjUjEPMAPrqdc
mZDihNk0TzPbZahxCxt15df7VPlriO28ZJRjdf7JwlVELn8E3SIL+ovgtjPTpf3N
q2gNu6X+U8Ys40mj1OqrD0L4WRTwVb7EN55UWM052h+HaM+ywGkKE

Bug#928813: marked as pending in libapache-mod-jk

[Markus Koschany]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/libapache-mod-jk/-/commit/f8d4df2710889793f7f1a0d862ad76bec1302d25


Rename httpd-jk.conf to jk.conf to restore compatibility with Debian's Apache

helpers a2enmod and a2dismod.

Closes: #928813


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/928813

Processed: Bug#928813 marked as pending in libapache-mod-jk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any 
configured worker
Added tag(s) pending.

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

Processed: tagging 936244

[Debian Bug Tracking System]

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

> tags 936244 + pending
Bug #936244 [src:bsdmainutils] bsdmainutils: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#961320 marked as pending in npm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #961320 [npm] backported version needs newer node-dot-prop to work
Added tag(s) pending.

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

Bug#961320: marked as pending in npm

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #961320 in npm 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/js-team/npm/-/commit/38be7079d06ec8b1624acdfc0176ad779883aee7


Require node-dot-prop ≥ 5.2.0

Closes: #961320


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961320

Bug#961591: [RFS] r-bioc-graph

[Nilesh Patra]

On Wed, 27 May 2020, 23:28 Dylan Aïssi,  wrote:

> Hi Nilesh,
>
> Le mer. 27 mai 2020 à 19:36, Nilesh Patra  a écrit :
> >
> > Hi,
> > Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed
> against this.
> > I have fixed this and pushed my changes to the team repo here[1].
> > Need review and sponsorship.
> >
>
> Thanks for #961591 !!!
>
> I don't understand why you moved some test-deps to deps ?


The second test (needing the library) failed on gitlab-ci, w/o adding
r-cran-xml and r-cran-runit, possible because this doesn't pick up depends
from test-depends.
This passed on my local machine though. Since I wanted to be sure, I moved
this there.

Was this incorrect to do?
Please do let me know.

Regards,
Nilesh

Bug#961591: [RFS] r-bioc-graph

[Dylan Aïssi]

Hi Nilesh,

Le mer. 27 mai 2020 à 19:36, Nilesh Patra  a écrit :
>
> Hi,
> Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed 
> against this.
> I have fixed this and pushed my changes to the team repo here[1].
> Need review and sponsorship.
>

Thanks for #961591 !!!

I don't understand why you moved some test-deps to deps ?

Best,
Dylan

Bug#961591: [RFS] r-bioc-graph

[Nilesh Patra]

Hi,
Currently r-bioc-graph has failing tests, and has RC bug - #961591 filed
against this.
I have fixed this and pushed my changes to the team repo here[1].
Need review and sponsorship.

[1]: https://salsa.debian.org/r-pkg-team/r-bioc-graph


Thanks and regards
Nilesh

Bug#928813: libapache2-mod-jk: Jk can not find any configured worker

[Markus Koschany]

Am 27.05.20 um 17:28 schrieb Thorsten Glaser:
[...]
> In stretch, an “a2enmod jk” will enable mods-available/jk.conf
> and make things work.
> 
> From reading the changelog, you wanted to “Install new httpd-jk.conf
> file which follows Apache 2.4 syntax”, but the directory is wrong;
> these files belong into conf-available, not mods-available.
> That being said, that would require both “a2enmod jk” *and*
> “a2enconf httpd-jk”, which is a UI regression against earlier,
> so I’d prefer for the file to be renamed back to what it was
> in stretch over moving it to another directory.
> 
> 
> ⚠ I intend to team-upload the fix if not done within the week. ⚠
> 

The mods-available directory is correct. Both conf and load file have to
be installed into it but the file naming is wrong. httpd-jk.conf should
be jk.conf. Just renaming the file should be sufficient. I will upload a
new revision.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#960571: marked as done (Missing dependency on fontconfig)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 16:21:24 +
with message-id 
and subject line Bug#960571: fixed in rst2pdf 0.97-2
has caused the Debian Bug report #960571,
regarding Missing dependency on fontconfig
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.)


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

Hi,

rst2pdf calls fc-match in findfonts.py, but does not list a dependency
on fontconfig. If you don't have it installed, building the document
will succeed but the document itself is empty.


Cheers,
Thijs
--- End Message ---
--- Begin Message ---
Source: rst2pdf
Source-Version: 0.97-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
rst2pdf, 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.
Sandro Tosi  (supplier of updated rst2pdf 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, 27 May 2020 11:52:20 -0400
Source: rst2pdf
Architecture: source
Version: 0.97-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 960571
Changes:
 rst2pdf (0.97-2) unstable; urgency=medium
 .
   * properly spell 'fontconfig' in Depends; Closes: #960571
Checksums-Sha1:
 336f9e031040beed678c8f4c7561a444a4009337 2227 rst2pdf_0.97-2.dsc
 6d0806571073adb7a90a49dcdcef65e8955129f6 5068 rst2pdf_0.97-2.debian.tar.xz
 0966f1e037f7bba34accf3e0c78a2f373ea8f0c6 5768 rst2pdf_0.97-2_source.buildinfo
Checksums-Sha256:
 9c1fbffd056622fa2cbc0f9706d5a94ff504e13ee4e41391f1b0eee77a001f27 2227 
rst2pdf_0.97-2.dsc
 f5181df5be8145df05cfcaab4f6d5ffe9140033dbea26d0050565e4be20fcf4e 5068 
rst2pdf_0.97-2.debian.tar.xz
 cfd7f8583b4bf68f0f56b10c0c10a70f0546d69ec1c47147164d9b70a51e3039 5768 
rst2pdf_0.97-2_source.buildinfo
Files:
 318e9096efd9c00c9ed38f8253905f28 2227 utils optional rst2pdf_0.97-2.dsc
 ef34b4213d17e0e6993d0930a4cba29c 5068 utils optional 
rst2pdf_0.97-2.debian.tar.xz
 b9e5503efefbecd13b6c4a0251e4d4a1 5768 utils optional 
rst2pdf_0.97-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl7OjNwACgkQh588mTgB
qU/VKA/+L7dqALc2biX+UdD7MrXpse8gPpgcpPA94RSUsWXaFZYfh+/QK3NfiZAA
qUKR9zgeEwDsWwzxNCjFXlAw7Hp1KQo7lmprUkvUgWN8THtN/bPDwrW4Dc9xvGXJ
pUUZTUWEaFOTiyrxMjA2syxnGPrh64ImiqM/rf4S5Cg94apY1PCCLd1P/OrCvVjF
s3aTqE4E++ljlbI+davTjc5EvRMe9nuRIkWPELCtS459ZU1hr6CWUyJvG/CpZBzK
FN6V/AQ2XimTX8dnOI2IvQZaqF0i/bmeu5hBlcZsbBv+dRZzZDvukRjxiaa2LQaY
1VGxTQMlvOCWn6xhz78NrwCnDcbRU7Wjr/P4M9S7+O1QGOgLy8XuExdrCBpDHJ36
2WTXS08RgQGKi9rTLsy15yebGgUHKuJFQEg4OZdjcmjd/FRwICfanKTSNXP2gzNb
/5wHmpryMLgEAPxtkFG5mVkSq+koNJxiKZGXBqq5wzlCc+9+0kxWElcJWIvptUxw
LsfRwfx6729rJLGRibqcYRQW7wrI6guuAm47O3rzHITNsxeWECKsG7EcE2dRjCIc
LTrSI6bGEQfBYO7SAMKKgrqZMWQBeEiJxMnO4hB7Ejkak/WAiyjPqScDkeutrv/5
N1mBFcQqgKl/ls5wjqmTt4jUNizvK2fQObhlQ0uT1QznmXbcIbE=
=vkr1
-END PGP SIGNATURE End Message ---

Processed: Bug#960571 marked as pending in pdfposter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #960571 [rst2pdf] Missing dependency on fontconfig
Added tag(s) pending.

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

Bug#960571: marked as pending in pdfposter

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/applications/rst2pdf/-/commit/e222db5bfcc68f8b2178bf56e06350fbb25c747e


properly spell 'fontconfig' in Depends; Closes: #960571


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/960571

Bug#960402: marked as done (mwrap FTBFS with bison 3.6.1)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 15:48:57 +
with message-id 
and subject line Bug#960402: fixed in mwrap 0.33-10
has caused the Debian Bug report #960402,
regarding mwrap FTBFS with bison 3.6.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.)


-- 
960402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mwrap
Version: 0.33-9
Severity: serious
Tags: ftbfs bullseye sid

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

...
   dh_auto_test
make -j15 test
make[1]: Entering directory '/build/1st/mwrap-0.33'
(cd testing; make)
make[2]: Entering directory '/build/1st/mwrap-0.33/testing'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
../mwrap -mex test_transfersmex \
-c test_transfersmex.cc \
-m test_transfers.m test_transfers.mw
mkoctfile --mex test_transfersmex.cc
../mwrap -cppcomplex \
-mex test_cpp_complexmex \
-c test_cpp_complexmex.cc \
-m test_cpp_complex.m test_cpp_complex.mw
mkoctfile --mex test_cpp_complexmex.cc
../mwrap -c99complex \
-mex test_c99_complexmex \
-c test_c99_complexmex.c \
-m test_c99_complex.m test_c99_complex.mw
mkoctfile --mex test_c99_complexmex.c
../mwrap -cppcomplex test_syntax.mw 2> test_syntax.log
make[2]: [Makefile:30: test_syntax] Error 1 (ignored)
diff test_syntax.log test_syntax.ref
2c2
< Parse error (test_syntax.mw:8): syntax error, unexpected end of file, 
expecting ';'
---
> Parse error (test_syntax.mw:8): syntax error, unexpected $end, expecting ';'
make[2]: *** [Makefile:31: test_syntax] Error 1
--- End Message ---
--- Begin Message ---
Source: mwrap
Source-Version: 0.33-10
Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= 

We believe that the bug you reported is fixed in the latest version of
mwrap, 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.
Rafael Laboissière  (supplier of updated mwrap 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, 27 May 2020 09:23:45 -0300
Source: mwrap
Architecture: source
Version: 0.33-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissière 
Closes: 960402
Changes:
 mwrap (0.33-10) unstable; urgency=medium
 .
   * Team upload
 .
   * d/u/metadata: New file
   * d/control:
 + Bump the Debhelper compatibility level to 13
 + Bump Standards-Version to 4.5.0 (no changes needed)
   * d/p/compile-with-bison-3.6.1.patch: New patch (Closes: #960402)
Checksums-Sha1:
 d4cbe87741fdc80da3b45d9cc80a98ac32c4dcc6 1992 mwrap_0.33-10.dsc
 3d1efe198804b24561aa3f6d8bdc4118e4d446bc 7456 mwrap_0.33-10.debian.tar.xz
 54753a4bd6770b65ba246e10ca25819f2b4e6dbc 13448 mwrap_0.33-10_amd64.buildinfo
Checksums-Sha256:
 c8df5f4a8e555f0907410225d3e13b9ca22b78f839f7e07daadc96be55e5ff30 1992 
mwrap_0.33-10.dsc
 1b10a2b7887834e100b033c152a26fc3cc52453894bc7c9c4b3ade38ffb2fd40 7456 
mwrap_0.33-10.debian.tar.xz
 4afcbc5d5e6181934fb1686b81cd40c1f32d4541460c5b994bae34ee48e33883 13448 
mwrap_0.33-10_amd64.buildinfo
Files:
 d541bfbcaa5f955f435fcf593ea21882 1992 devel optional mwrap_0.33-10.dsc
 ef752752f74c86d6381510196136ed4b 7456 devel optional 
mwrap_0.33-10.debian.tar.xz
 a65005f6a7ffe848ae0234f9fec83c82 13448 devel optional 
mwrap_0.33-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl7OhnQACgkQISSqGYN4
XJBlaA/9HK6YCNPrzN9yW3+d2qNDR3z0MB27pOxBPCcdXDXKxmacBpMwpsl0CjkF
5IjGY96s5cT8b1HAY00QBj1zOO8dLMiK++kpeGxbzV93XkBjNHTBxWv8pwNWRg4O
Iy9I1TXhnc+vQaY96KFQH1jOfCKu22+jCMJC7uwtoErDJSmzkz5Qzhe2bwxxYgXX
Pg5y4Kd79vWg0OgeBrIvGU5mgXKV/yKWeHwh9EDUsfN0P+sBhS5Eyw/ui3wJKYB2
8R/r17a9Ap17Aq4SIltNod9mouezotawbd7eq7eKbNmAEZnJxEOZwlPPM+QPc1MH
zCvOldRoR057YC+XK1EgsU6/NiOD9eEuvpHcn6gFPy3KXdGivO2fsv8osdnnFzo+
j/y9RxDgdh7m1TPIlGjbsM+k34NY/Tq5ycdIxK5o6wPHiCGJByu3S7vnn7nfEizG
mwOnHcgMoYZQVZci0JSsdllwlu0QveXrUCJv8QPDsKoAKaz3eidMzoI7/s+aC7oV
KpwVfVYkLLuSmjBTxhMJ5jVp7wZE97t9seO4HeoOXzJ2AvzlVh5JZ8GxZZmPlpwu
b+PmyC6ThMn/iaD3VSKzznUXgAUUwdfEm/uJ

Bug#955316: marked as done (r-cran-svglite autopkgtest fails: Error: symbol font)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 15:49:45 +
with message-id 
and subject line Bug#955316: fixed in r-cran-svglite 1.2.3-3
has caused the Debian Bug report #955316,
regarding r-cran-svglite autopkgtest fails: Error: symbol font
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.)


-- 
955316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-svglite
Version: 1.2.3-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: always-fail

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails.

I copied a piece from the log below.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-svglite/4737512/log.gz

autopkgtest [13:47:37]: test run-unit-test: [---
BEGIN TEST testthat.R

R version 3.6.3 (2020-02-29) -- "Holding the Windsock"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(svglite)
>
> test_check("svglite")
-- 1. Error: (unknown) (@test-colour.R#2)
-
there is no package called 'xml2'
Backtrace:
 1. base::library(xml2)

-- 2. Error: (unknown) (@test-devSVG.R#2)
-
there is no package called 'xml2'
Backtrace:
 1. base::library(xml2)

-- 3. Error: (unknown) (@test-lines.R#2)
--
there is no package called 'xml2'
Backtrace:
 1. base::library(xml2)

-- 4. Failure: intermediate outputs are always valid svg
(@test-output.R#30)  --
`xml2::read_xml(path)` threw an error.
Message: there is no package called 'xml2'
Class:   packageNotFoundError/error/condition
Backtrace:
  1. svglite:::expect_valid_svg()
  7. xml2::read_xml
  8. base::getExportedValue(pkg, name)
  9. base::asNamespace(ns)
 10. base::getNamespace(ns)
 11. base::loadNamespace(name)
 12. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
 13. base:::withOneRestart(expr, restarts[[1L]])
 14. base:::doWithOneRestart(return(expr), restart)

-- 5. Failure: intermediate outputs are always valid svg
(@test-output.R#33)  --
`xml2::read_xml(path)` threw an error.
Message: there is no package called 'xml2'
Class:   packageNotFoundError/error/condition
Backtrace:
  1. svglite:::expect_valid_svg()
  7. xml2::read_xml
  8. base::getExportedValue(pkg, name)
  9. base::asNamespace(ns)
 10. base::getNamespace(ns)
 11. base::loadNamespace(name)
 12. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
 13. base:::withOneRestart(expr, restarts[[1L]])
 14. base:::doWithOneRestart(return(expr), restart)

-- 6. Failure: intermediate outputs are always valid svg
(@test-output.R#36)  --
`xml2::read_xml(path)` threw an error.
Message: there is no package called 'xml2'
Class:   packageNotFoundError/error/condition
Backtrace:
  1. svglite:::expect_valid_svg()
  7. xml2::read_xml
  8. base::getExportedValue(pkg, name)
  9. base::asNamespace(ns)
 10. base::getNamespace(ns)
 11. base::loadNamespace(name)
 12. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
 13. base:::withOneRestart(expr, restarts[[1L]])
 14. base:::doWithOneRestart(return(expr), restart)

-- 7. Failure: intermediate outputs are always valid svg
(@test-output.R#39)  --
`xml2::read_xml(path)` threw an error.
Message: there is no package called 'xml2'
Class:   packageNotFoundError/error/condition
Backtrace:
  1. svglite:::expect_valid_svg()
  7. xml2::read_xml
  8. base::getExportedValue(pkg, name)
  9. base::asNamespace(ns)
 10. base::getNamespace(ns)
 11. base::loadNamespace(name)
 12. base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
 13. base:::withOneRestart(expr, restarts[[1L]])
 14. base:::doWithOneRestart(return(expr), restart)

-- 8. Error: (unknown) (@test-path.R#2)
---
there is no package called 'xml2'
Backtrace:
 1. base::library(xml2)

-- 9. Error: (unknown) (@test-points.R#2)
-
there is no package called 'xml2'

Processed: Reopen

[Debian Bug Tracking System]

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

> reopen 960571
Bug #960571 {Done: Sandro Tosi } [rst2pdf] Missing dependency 
on fontconfig
Bug reopened
Ignoring request to alter fixed versions of bug #960571 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#960571: rst2pdf: Bad dependency on "fontconfing"

[Daniel Serpell]

Package: rst2pdf
Version: 0.97-1
Followup-For: Bug #960571

The last upload clearly was not tested, as it now depends on the
misspelled package "fontconfing".

New package is uninstallable.

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

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

Versions of packages rst2pdf depends on:
ii  python33.8.2-3
ii  python3-docutils   0.16+dfsg-2
ii  python3-jinja2 2.11.1-1
ii  python3-pdfrw  0.4-2.1
ii  python3-pkg-resources  46.1.3-1
ii  python3-pygments   2.3.1+dfsg-3
ii  python3-reportlab  3.5.34-1
ii  python3-setuptools 46.1.3-1
ii  python3-simplejson 3.17.0-1
ii  python3-six1.15.0-1
ii  python3-smartypants2.0.0-2

rst2pdf recommends no packages.

Versions of packages rst2pdf suggests:
pn  python3-aafigure  
ii  python3-matplotlib3.2.1-1+b1
ii  python3-pil   7.0.0-4+b1
pn  python3-sphinx
pn  python3-uniconvertor  

-- no debconf information

Processed: Re: libapache2-mod-jk: Jk can not find any configured worker

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any 
configured worker
Severity set to 'serious' from 'important'
> notfound -1 1:1.2.46-0+deb9u1
Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any 
configured worker
Ignoring request to alter found versions of bug #928813 to the same values 
previously set
> found -1 1:1.2.46-1
Bug #928813 [libapache2-mod-jk] libapache2-mod-jk: Jk can not find any 
configured worker
Ignoring request to alter found versions of bug #928813 to the same values 
previously set

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

Bug#960402: marked as pending in mwrap

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #960402 in mwrap 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/pkg-octave-team/mwrap/-/commit/60d8f18ba09b242be7c6953f166683807907a03b


d/p/compile-with-bison-3.6.1.patch: New patch

Closes: #960402


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/960402

Processed: Bug#960402 marked as pending in mwrap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #960402 [src:mwrap] mwrap FTBFS with bison 3.6.1
Added tag(s) pending.

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

Processed: Re: Bug#959675: libgrpc++1: endless looping with default settings

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #959675 [libgrpc++1] libgrpc++1: endless looping with default settings
Added tag(s) pending.

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

Bug#959675: libgrpc++1: endless looping with default settings

[GCS]

Control: tags -1 +pending

On Wed, May 27, 2020 at 4:42 PM Thomas Goirand  wrote:
> Any progress on this? I've been watching this bug activity, and
> nothing's happening. I'm worried for my packages removal in Bullseye
> (ie: most of OpenStack...).
Quoting the package tracker: "grpc is marked for autoremoval from
testing on 2020-06-23" which is almost a month away.
Then Benjamin uploaded Abseil and it's in NEW [1] and I've updated
gRPC and it's also in NEW [2] waiting for Abseil at first. Hope FTP
Masters will clear both packages soon to the archives.
In short, don't worry for the time being.

Regards,
Laszlo/GCS
[1] https://ftp-master.debian.org/new/abseil_0~20200225.2-1.html
[2] https://ftp-master.debian.org/new/grpc_1.29.1-1.html

Bug#959675: libgrpc++1: endless looping with default settings

[Thomas Goirand]

Hi Benjamin,

Any progress on this? I've been watching this bug activity, and
nothing's happening. I'm worried for my packages removal in Bullseye
(ie: most of OpenStack...).

Cheers,

Thomas Goirand (zigo)

Bug#959818: marked as done (libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 14:35:06 +
with message-id 
and subject line Bug#959818: fixed in libcatmandu-perl 1.2012-1
has caused the Debian Bug report #959818,
regarding libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-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.)


-- 
959818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcatmandu-perl
Version: 1.2011-1
Severity: serious
Control: block -1 with 955689

1.2011-1 in unstable dropped its dependency on libdata-uuid-perl,
unmasking a missing dependency in libcatmandu-filestore-perl (#955689).
This was noticed by autopkgtest checks, currently preventing testing
migration of libcatmandu-perl.

libcatmandu-filestore-perl should be fixed first, and libcatmandu-perl
should then declare a Breaks relation on the earlier versions
of libcatmandu-filestore-perl to prevent partial upgrades where
libcatmandu-perl is updated before libcatmandu-filestore-perl.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libcatmandu-perl
Source-Version: 1.2012-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libcatmandu-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: Tue, 26 May 2020 21:21:19 +0200
Source: libcatmandu-perl
Architecture: source
Version: 1.2012-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Closes: 959818
Changes:
 libcatmandu-perl (1.2012-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
   * set upstream metadata fields:
 Bug-Database, Bug-Submit, Repository, Repository-Browse.
 .
   [ upstream ]
   * new release
 .
   [ Jonas Smedegaard ]
   * break older libcatmandu-filestore-perl;
 closes: bug#959818, thanks to Niko Tyni
   * copyright: update coverage
Checksums-Sha1:
 7b1dfabe3c7fe70ef861e65645104844bcb43c6b 3204 libcatmandu-perl_1.2012-1.dsc
 3fc48252c1cccb8a882141091e6e962de9569f79 83 
libcatmandu-perl_1.2012.orig.tar.gz
 c645e660a0d541dd79b664567f3a0bc114ea69f6 18428 
libcatmandu-perl_1.2012-1.debian.tar.xz
 607850568b667a4654dcb7fc3119d4f8f71fc58a 9037 
libcatmandu-perl_1.2012-1_amd64.buildinfo
Checksums-Sha256:
 5fe15dadf1e128f64998529bedcbbdeffe94a0a71dbc07257339cbac5fe91223 3204 
libcatmandu-perl_1.2012-1.dsc
 a08d0cfbc503deaed64ec8f57fa352b9708ef1bbe55ceff41c5ec5b6 83 
libcatmandu-perl_1.2012.orig.tar.gz
 b8c4f69fe540ec3170b218335538933c8420a2ac61cd97e0459e482e276f3d1d 18428 
libcatmandu-perl_1.2012-1.debian.tar.xz
 cb6590dba31a4e1e2365ff9f3d0839cca3687b2f18edacf80dd28e373676ce35 9037 
libcatmandu-perl_1.2012-1_amd64.buildinfo
Files:
 047b4f253c04bbc54a07c380bc435ee3 3204 perl optional 
libcatmandu-perl_1.2012-1.dsc
 ec400c7c1cb7adc1fd80550a3b0b8e07 83 perl optional 
libcatmandu-perl_1.2012.orig.tar.gz
 8d4a290cafd1aef9ac1bbd34c0f17cee 18428 perl optional 
libcatmandu-perl_1.2012-1.debian.tar.xz
 52f412ccbb9aafa83a99fa3411a1ae8e 9037 perl optional 
libcatmandu-perl_1.2012-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7OdGcACgkQLHwxRsGg
ASHUDxAAqJUYoFWP8wmmg5abKgoK1pyyO58ZsNjSX+rsrwow/55wZzJdu4QzDj8d
rXJuAmmHjZDC+B1ax+myjCTjrduD0csGgQb+SYINDeywRjoCIpZgsng9w3aHliNx
Uu6LWLuWk3eNuV0J+96AzmIelW+3iB66CfBmLfEeygynyfCvu7O/EYqCU5Nl1j9E
wBKs91mgf7pCwWOco9jUI15sclR4Jzt5kHKsmt7kQ0b8kCWKM7ccShewsU9aXd+j
ICIko9/k0eFTwyoAOJo63TBTt/vLeL81sqV1spR8+tQVpdvmzWpnN5TNFOM+FqoA
+TcqXIA0PqMlzCFLxtMbd1s9wdlkWOfNrT6uJYEU8Rw/TX7WMC/iOtkPsfvd4fYV
Kp10+1yOZbis4CpJFsBMkDjWJ17RttJxeLLg08qR48pycoi+Dc8HGE3CC+EtUCw4
dMnN+paIPyT3GYqCvGsVnuAX1mAac/tIIUYQarK3fdlp7L8amLX9K5AVnP35RGem
RSG2NBkP1yrQARdboqUtDXPiQTogjjfBvAl16O9OoJrT7zlDtM5CVfvcgRxyLKbI
O2UFQrmtdAOFnAGTMQDpr+PM+bIhMGK0Ytg2pX/c2HspuZPmkWxHcxDiL1cs+ukl
1NhYiPFtV3CwSoNN1d4EYSWLd7adT/oLaqlvD/0wVhQSwE2ZD6w=
=9PsX
-END

Processed: Bug#959818 marked as pending in libcatmandu-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #959818 [libcatmandu-perl] libcatmandu-perl: 1.2011-1 breaks 
libcatmandu-filestore-perl
Added tag(s) pending.

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

Bug#959818: marked as pending in libcatmandu-perl

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #959818 in libcatmandu-perl 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/perl-team/modules/packages/libcatmandu-perl/-/commit/531666483bff923121cd274111281b8c1c97da02


break older libcatmandu-filestore-perl; closes: bug#959818, thanks to Niko Tyni


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959818

Bug#961584: lxc-stop fails with exit code 1

[Inaki Malerba]

El 26/5/20 a las 23:35, Antonio Terceiro escribió:
> is there an easy/documented way of reproducing the salsa ci environment
> (i.e. lxc working under docker) locally? 

Attached is a Dockerfile. It should be sufficient to reproduce the problem.

Changing the FROM statement from debian:unstable to debian:testing is
enough to make it work. It needs to be run as privileged.

$ docker build -t autopkgtest - < Dockerfile
$ docker run --rm --privileged autopkgtest

-- 
- ina
FROM debian:unstable

ENV SALSA_CI_AUTOPKGTEST_LXC 
https://salsa.debian.org/salsa-ci-team/autopkgtest-lxc
ENV LXC_PATH /lxc

# Download and configure container.
RUN apt-get update && apt-get install -y wget
RUN wget --progress=dot:giga 
${SALSA_CI_AUTOPKGTEST_LXC}/-/jobs/artifacts/master/raw/artifacts/lxc.tar?job=stable
 -O lxc.tar
RUN mkdir ${LXC_PATH} && tar xf lxc.tar -C ${LXC_PATH}
RUN sed -i "/lxc.rootfs.path/ s@dir:.*/lxc/@dir:${LXC_PATH}/@" 
${LXC_PATH}/autopkgtest-stable-amd64/config

# Install lxc.
RUN apt-get update && apt-get install -y eatmydata
RUN eatmydata apt-get install -y lxc iptables

RUN echo "lxc.lxcpath=${LXC_PATH}" | tee -a /etc/lxc/lxc.conf
RUN echo 'USE_LXC_BRIDGE="true"' | tee /etc/default/lxc-net

RUN echo 'tmpfs /sys/fs/cgroup tmpfs rw,relatime,seclabel' | tee /etc/fstab
RUN echo 'cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset,x-mount.mkdir' 
| tee -a /etc/fstab
RUN echo 'cgroup /sys/fs/cgroup/devices cgroup 
rw,relatime,devices,x-mount.mkdir' | tee -a /etc/fstab

# This steps need to be run as privileged.
CMD umount -R /sys/fs/cgroup && mount -a && \
/etc/init.d/lxc-net start && \
/etc/init.d/lxc start && \
lxc-start autopkgtest-stable-amd64 && \
lxc-stop autopkgtest-stable-amd64 && \
echo "ok"


signature.asc
Description: OpenPGP digital signature

Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

[Thorsten Glaser]

Hi Gunnar,

>VERY GOOD CATCH! Thanks a lot for this. I'm pushing it to Git right

you’re welcome.

>
> https://salsa.debian.org/debian/raspi-firmware/-/commit/2bf38f62de0514c2759f2c33d147c935e4d044bf

Note this caused unbootable RPi 3B+ systems, so it was actually a
severe regression wrt. the previous upload, not just the 0/2 ones.

bye,
//mirabilos
-- 
  "Using Lynx is like wearing a really good pair of shades: cuts out
   the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
 -- Henry Nelson, March 1999

Bug#961505: marked as done (failed mips64el build of flint 2.5.2-22)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 13:18:45 +
with message-id 
and subject line Bug#961505: fixed in flint 2.5.2-23
has caused the Debian Bug report #961505,
regarding failed mips64el build of flint 2.5.2-22
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.)


-- 
961505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flint
Version: 2.5.2-22
Severity: serious
Tags: ftbfs
Thanks

Hi,

I wanted to check whether the recent upload actually fixed
953437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953437

I realized that it failed to build.

Regards, Thibaut.


 Message transféré 
Sujet : failed mips64el build of flint 2.5.2-22
Date : Tue, 19 May 2020 20:45:33 -
De : Debian buildds 
Pour : dispa...@tracker.debian.org

 * Source package: flint
 * Version: 2.5.2-22
 * Architecture: mips64el
 * State: failed
 * Suite: sid
 * Builder: mipsel-aql-02.debian.org
 * Build log:
https://buildd.debian.org/status/fetch.php?pkg=flint&arch=mips64el&ver=2.5.2-22&stamp=1589921133&file=log

Please note that these notifications do not necessarily mean bug reports
in your package but could also be caused by other packages, temporary
uninstallabilities and arch-specific breakages.  A look at the build log
despite this disclaimer would be appreciated however.





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: flint
Source-Version: 2.5.2-23
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
flint, 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.
Julien Puydt  (supplier of updated flint 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, 27 May 2020 13:47:49 +0200
Source: flint
Architecture: source
Version: 2.5.2-23
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Julien Puydt 
Closes: 961505
Changes:
 flint (2.5.2-23) unstable; urgency=medium
 .
   * Update bug_953437.patch, following a new
 upstream change (Closes: #961505).
Checksums-Sha1:
 70828a39221b8bd0e98c865dae235feae2f27d41 2143 flint_2.5.2-23.dsc
 2c71f45918568ed6f6c8d2926255b28d768b7b72 8972 flint_2.5.2-23.debian.tar.xz
 f2cb3312b45b8a35185ec1327dbe363ea568f526 7770 flint_2.5.2-23_source.buildinfo
Checksums-Sha256:
 87086dad11679ba6ae502f6dc4efca6d1d1f500767897f1770f9c4964b0ff941 2143 
flint_2.5.2-23.dsc
 606dfd8110d3e4f685b7eb73ae49e66a0e242a857ac4959773496f2c40ba5f46 8972 
flint_2.5.2-23.debian.tar.xz
 59be1f574cabef445ed3811673490a977eecee175b99c8b226934b14e14b535b 7770 
flint_2.5.2-23_source.buildinfo
Files:
 9ba5ddc6c6248d4074844d4d6daabbe6 2143 math optional flint_2.5.2-23.dsc
 215efee5e66cf5023c263c307d8a0128 8972 math optional 
flint_2.5.2-23.debian.tar.xz
 3153dcba24e53c5021c51b9560d0dce5 7770 math optional 
flint_2.5.2-23_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl7OWrkSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRfWIP/A35LQKL6tcTeoSkvuzpXftDE6qVrBVt
kWs1bPX0nmeD6ZyQDiPAWQE+nO4tTn545U3DGrRJW4ne3dHmDmWe5tzYtskMwAp9
apCZXGdBp6+8NsuFwnatupe1QDLrhFydpb8GVxvG9ZLvlbRSa5sK8iTo7gw7BrXp
CNcsHZkr8iWAL9ryIGIxixlPk8U6jVub7C/6uGvUc2ggLqA2bOzSTdARVEYm33pA
mrx+a5Dt5RIn6S7TcH/Eir+tESkK0t91KQDLaYgHvDMSn+QRfGhCjgfDKrSWjfaP
c3EBLhXQ/Zx9YJdxT/+685qRFQVNKAATY5bsWxQQst2mGz5iczAVar/8WwGk29Bz
CJTFSbYSzDtlF2JjzxACXTCs3LK/UhYGPTmUrW/W8YH00nRs5L7GviArkZmtCEQm
4ye1eyJe+F0WLUUath82HWebdu0WrmNndUZNLhD3L/g3ccW2fF5yq2BcnPJpS0hf
yqZEMP8mOsfr9Z5TSNv8rzzrwf+WiyiBZsbTwk0R8Yx+HywfzK2999VeN/s2QXKk
CoIVV0jDFhJnAEJZORdPDCnGz44OWI3mqYWisy+CWKBAlMDFsytfVHsd1f9B/yVy
Dxwu6vfIfBPlVWX2yjJDAMfEak/4RDcyh3oeAcWKEDjafPfCYMzZ/oxS+esDJCY+
8ERJDWO202Qa
=TzpA
-END PGP SIGNATURE End Message ---

Bug#961501: remmina is calling home for update notifications

[Antenore Gatta]

Hi all,

patch is on its way.

Progress can be tracked on our gitlab [0]

Any feedback is much appreciated as it'll easy the resolution of the bug.

Thanks!

Kind regards
Antenore

- [0] https://gitlab.com/Remmina/Remmina/-/merge_requests/2066

Processed (with 5 errors): Raise severity

[Debian Bug Tracking System]

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

> severity 960558 grave
Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with 
optimisation and FORTIFY_SOURCE flags
Severity set to 'grave' from 'important'
> tags 960558 patch
Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with 
optimisation and FORTIFY_SOURCE flags
Added tag(s) patch.
> found 960558 3.2.0-5
Bug #960558 [cyrus-common] cyrus-common: lmtpd aborts when compiled with 
optimisation and FORTIFY_SOURCE flags
Marked as found in versions cyrus-imapd/3.2.0-5.
> Hi,
Unknown command or malformed arguments to command.
> I will argue this bug is grave, since LMTP is likely used in most setups for 
> local delivery to the IMAP server (from either SMTP or procmail). Therefore 
> it "makes the package in question unusable or mostly so". In addition it can 
> causes a possibly large number of failed delivery notifications to be sent, 
> which is called "spamming". This renders the package in most setups unusable.
Unknown command or malformed arguments to command.
> Is it possible to incorporate the upstream patch please?
Unknown command or malformed arguments to command.
> Regards,
Unknown command or malformed arguments to command.
> Keith
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#961647: marked as done (akonadi: FTBFS on armel: missing -latomic)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:18:32 +
with message-id 
and subject line Bug#961647: fixed in akonadi 4:20.04.1-2
has caused the Debian Bug report #961647,
regarding akonadi: FTBFS on armel: missing -latomic
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.)


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

akonadi failed to build on armel:
| cd /<>/obj-arm-linux-gnueabi/src/server && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/akonadiserver.dir/link.txt --verbose=1
| /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra 
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith 
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla 
-Wdate-time -Wsuggest-override -Wlogical-op -pedantic 
-Wzero-as-null-pointer-constant -Wnon-virtual-dtor -Wundef -Wcast-align 
-Wchar-subscripts -Wall -Wextra -Wpointer-arith -Wformat-security -fno-common 
-pedantic -fexceptions  -Wl,--enable-new-dtags -Wl,-z,relro -Wl,-z,now 
CMakeFiles/akonadiserver.dir/akonadiserver_autogen/mocs_compilation.cpp.o 
CMakeFiles/akonadiserver.dir/main.cpp.o 
CMakeFiles/akonadiserver.dir/akonadiserver_debug.cpp.o 
CMakeFiles/akonadiserver.dir/akonadiserver_search_debug.cpp.o  -o 
../../bin/akonadiserver  -Wl,-rpath,/<>/obj-arm-linux-gnueabi/bin: 
../../lib/libakonadiserver.a ../../lib/libakonadi_shared.a 
/usr/lib/arm-linux-gnueabi/libKF5Crash.so.5.70.0 
/usr/lib/arm-linux-gnueabi/libKF5CoreAddons.so.5.70.0 
../../bin/libKF5AkonadiPrivate.so.5.14.1.abi2 
/usr/lib/arm-linux-gnueabi/libQt5Network.so.5.12.5 
/usr/lib/arm-linux-gnueabi/libQt5Sql.so.5.12.5 
/usr/lib/arm-linux-gnueabi/libQt5DBus.so.5.12.5 
/usr/lib/arm-linux-gnueabi/libQt5Xml.so.5.12.5 
/usr/lib/arm-linux-gnueabi/libQt5Core.so.5.12.5 
| /usr/bin/ld: ../../lib/libakonadiserver.a(querybuilder.cpp.o): undefined 
reference to symbol '__atomic_fetch_add_8@@LIBATOMIC_1.0'
| /usr/bin/ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: 
DSO missing from command line
| collect2: error: ld returned 1 exit status

This is caused by a missing -latmoic. See also
https://buildd.debian.org/status/fetch.php?pkg=akonadi&arch=armel&ver=4%3A20.04.1-1&stamp=1590553675&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: akonadi
Source-Version: 4:20.04.1-2
Done: =?utf-8?q?Sandro_Knau=C3=9F?= 

We believe that the bug you reported is fixed in the latest version of
akonadi, 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.
Sandro Knauß  (supplier of updated akonadi 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, 27 May 2020 11:52:12 +0200
Source: akonadi
Architecture: source
Version: 4:20.04.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Closes: 961647
Changes:
 akonadi (4:20.04.1-2) unstable; urgency=medium
 .
   [ Sandro Knauß ]
   * Add linkage against atomic, where needed. (Closes: #961647)
 Thanks to Adrian Bunk 
Checksums-Sha1:
 92a3169265308caa30ed79f11b3b152471386914 4014 akonadi_20.04.1-2.dsc
 7d7ed7610aa39490773e1022ca7092e38cdac2c9 32696 akonadi_20.04.1-2.debian.tar.xz
 3b94bc4946b3058de1794f2000b7f52936a3b015 18598 
akonadi_20.04.1-2_source.buildinfo
Checksums-Sha256:
 394a5e79c7aa1a546babc8baac6895104ec6b39b75459b2169dc424e191f669e 4014 
akonadi_20.04.1-2.dsc
 84760862b7755a56e74f99440d96ea6bbcd96e60771480057f695619155fb81a 32696 
akonadi_20.04.1-2.debian.tar.xz
 362b6af7439b451beb2e3e7370941c9260e43c2b77d73c75b5d5644918489089 18598 
akonadi_20.04.1-2_source.buildinfo
Files:
 9e90dde684b2d53e2b39f92bcfeed547 4014 libs optional akonadi_20.04.1-2.dsc
 32790bdb3a332642af

Bug#961646: marked as done (node-deep-for-each breaks node-grunt-webpack)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:19:22 +
with message-id 
and subject line Bug#961646: fixed in node-deep-for-each 3.0.0-2
has caused the Debian Bug report #961646,
regarding node-deep-for-each breaks node-grunt-webpack
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.)


-- 
961646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-deep-for-each
Version: 3.0.0-1
Severity: serious
Control: affects -1 node-grunt-webpack

Version 3.0.0 breaks node-grunt-webpack. Probably due to this change:

> This library is no longer built with Babel, you must compile it
> yourself within your app

Revert to a version 2.x may solve this issue
--- End Message ---
--- Begin Message ---
Source: node-deep-for-each
Source-Version: 3.0.0-2
Done: Xavier Guimard 

We believe that the bug you reported is fixed in the latest version of
node-deep-for-each, 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.
Xavier Guimard  (supplier of updated node-deep-for-each 
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, 27 May 2020 11:51:55 +0200
Source: node-deep-for-each
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 961646
Changes:
 node-deep-for-each (3.0.0-2) unstable; urgency=medium
 .
   * Team upload
   * Build with babel-plugin-add-module-exports (Closes: #961646)
Checksums-Sha1: 
 70a6160c9d7c02735e512c87255cd82c3a11fb34 2184 node-deep-for-each_3.0.0-2.dsc
 87ba9e26ed4ae449528db38a12a3186883effcb4 13044 
node-deep-for-each_3.0.0-2.debian.tar.xz
Checksums-Sha256: 
 5fc4c53691dd1537bab3e48e7fc07efe2bf4d9a9657f39e8ce5628d2f52dd969 2184 
node-deep-for-each_3.0.0-2.dsc
 462f32a1e521e155981ff80d83d2916de8c175e50eba23e1636a1b75af311149 13044 
node-deep-for-each_3.0.0-2.debian.tar.xz
Files: 
 fea4ab34c61431086d568d8619bb5eb8 2184 javascript optional 
node-deep-for-each_3.0.0-2.dsc
 9c8464a68e29d9370b26474cb5e16ebe 13044 javascript optional 
node-deep-for-each_3.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl7OOHQACgkQ9tdMp8mZ
7unquQ//Y7E3/QVGxoJTO2oVfKC4k9AD915aei7KaKsd5PJj2MqYisnCx/cM9kyB
oodg7BwPgocT1rArIDG4Lhd0YzO8KO/tFNjnCv1h/tIvnx8VBRKTwXVmi3Mjj+WN
KCFYSSjJcbcxe3YZYhAE7WqE+ApbcL8ax2qFlpBfGN7iK57g7Yh1XQjNYI1ztjBK
CHBbFY/CyFdCipVuD+fofRrJTq426LrCrlXLXQSWbeOd9giDNNjlmPb+oLOmOjVg
kBGUjRNNKGkE6OJQNktBWljdDcMdr5ec8GICDzvkRcncvV2iiOM/KGm91H2TEmzY
3uLiat8ztPqE/zQcE4FXVCGCAgN06MprwsBM6KR6VwOatuT3WD1jm8YPklwND3wH
h8DGcH2kMexgex7KnvusS3KhgjGuh7pcMZHy5Hx2NyVNbcHh9hMtv1cOXvRyUyJo
AhM0omOG8DEVvDs7/smi35WWzQ4HbdIG89gjuuSSMHTwRDmL/ENcu7SgSQZbiKoM
SCY9Ev0dMaHHnipWo46uFDNmppfq7ndzf69/BNvYTyi9cicerISZ8tjnK4KjMkF9
hlbSB9CzVXUmRP9eXdOSRL1YrPAPRvbf7twctulnTU8X3Nez0c+HcpkN7+hAL1Bd
tpbC5YnNSLQ5Vf5ao+QuxYU2YB3v1CjhjkZra9WEwlbpVdgiTp0=
=ISK4
-END PGP SIGNATURE End Message ---

Bug#961591: Bug#961592: r-bioc-gviz: autopkgtest regression

[Andreas Tille]

On Wed, May 27, 2020 at 11:22:34AM +0200, Dylan Aïssi wrote:
> 
> But, regarding https://bugs.debian.org/961591 , I have no idea how to fix it.

I have no idea either.  What about seeking help at upstream?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#961592: marked as done (r-bioc-gviz: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:04:09 +
with message-id 
and subject line Bug#961592: fixed in r-bioc-gviz 1.32.0+dfsg-2
has caused the Debian Bug report #961592,
regarding r-bioc-gviz: autopkgtest regression
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.)


-- 
961592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-gviz
Version: 1.32.0+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since the upload of 1.32.0+dfsg-1, r-bioc-gviz has been failing its
own autopkgtests [1].   This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-gviz/unstable/amd64/


> test_check("Gviz")
Error in library(BSgenome.Hsapiens.UCSC.hg19) :
  there is no package called 'BSgenome.Hsapiens.UCSC.hg19'
Calls: test_check ... source_dir -> lapply -> FUN -> eval -> eval -> library
Execution halted
autopkgtest [15:02:19]: test pkg-r-autopkgtest: ---]
autopkgtest [15:02:19]: test pkg-r-autopkgtest:  - - - - - - - - - -
results - - - - - - - - - -
pkg-r-autopkgtestFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-bioc-gviz
Source-Version: 1.32.0+dfsg-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-bioc-gviz, 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.
Dylan Aïssi  (supplier of updated r-bioc-gviz 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, 27 May 2020 11:39:34 +0200
Source: r-bioc-gviz
Architecture: source
Version: 1.32.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 961592
Changes:
 r-bioc-gviz (1.32.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to skip tests requiring package not available in Debian.
  (Closes: #961592)
Checksums-Sha1:
 8563e4c47956f4d854bc6a14ffe645e2a54f0b17 2642 r-bioc-gviz_1.32.0+dfsg-2.dsc
 890d3d828509a720456f13bc0f0d97bd5cc4377b 7380 
r-bioc-gviz_1.32.0+dfsg-2.debian.tar.xz
 d9ead668f4756ed8d38dcbae8ecd5bfec878ae38 13344 
r-bioc-gviz_1.32.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 0db20d24844baa6534562cdec6e81e44e1ba52f3cdaff45a942c650ab1b04088 2642 
r-bioc-gviz_1.32.0+dfsg-2.dsc
 f930f5a6bb2622771ac9b6bc94d5b6e70293d8f6b7657290492f8b574a183a14 7380 
r-bioc-gviz_1.32.0+dfsg-2.debian.tar.xz
 98dd01d70e363776a6357d58da809d4a19632af42179a3caea2abe1059d2b755 13344 
r-bioc-gviz_1.32.0+dfsg-2_amd64.buildinfo
Files:
 84322eb508fb33e5688e161025111f81 2642 gnu-r optional 
r-bioc-gviz_1.32.0+dfsg-2.dsc
 a22322b6980edb805a3b963145d56ee0 7380 gnu-r optional 
r-bioc-gviz_1.32.0+dfsg-2.debian.tar.xz
 085346d7131c34b654d4091599bfaac8 13344 gnu-r optional 
r-bioc-gviz_1.32.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl7ON68ACgkQYS7xYT4F
D1SmbRAAggycHhviirGUwPaP5lqtmylPyXaSs14COg+wGm93r5AyKAOg1CgNjOM7
653sXPhL8rerv1hzEq0/suVMlocIyrrh2Pem4ZDnVok1f74C/zijtEpGSREANdsk
zPG/h0T6Q95Lu55YO5WmMmzckKjgI0PpjVwDKxV1g0MisUHGiz3tzqpdFWbLVbKr
ld7gzCXh6aMToVR+WNTk8gXHveUr/OQdQ+9Rmopv/CxNDLiDqTZbA4AaGJSzpTxK
JrGxdzAzfXakh6g/yC7KZZyNYjoKZKTocMBjkpkfR2Jo+QbP5dyw7uX65VW1xrjk
xaVAup35Nu05QwYpQn0578gP8gnRV+mTwnJv4dTSyaRzTnFboBPQhDyjf8fhDFDv
yTIz4hIGL/wsgoLzbn/BwzCD/GddDIpqe8/7k9C6ielUJWcI2mUiwOMW0S9Kb1cy
QagXXJzqi1Xh1Uqzy+sd5qaFs87a8nA2UGX5e1vbSmOjfsD+ev3SKAyuuqo71wBV
X1r+duYHNynlrRj6tguPk3Le60bdjzg4ir4jUB+JKMoK+DFIJ8qplt3aGNla92m8
D4CMTtb3o/5OaPszB+YDHCTc6eILt2tKUYOK1f0hEV0bIvShCeGKcO+mYI36nC86
C7keytrYbMJ2OKMKgApKriVXDUNOiJE2hkf2jyLslYtnhQ4HwfU=
=X89z
-END PGP SIGNATURE End Message ---

Bug#961581: marked as done (pbcopper: ftbfs on ppc64el)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:00:10 +
with message-id 
and subject line Bug#961581: fixed in pbcopper 1.6.0+dfsg-2
has caused the Debian Bug report #961581,
regarding pbcopper: ftbfs on ppc64el
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.)


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

Dear Maintainer,

As can be seen on 

https://buildd.debian.org/status/logs.php?pkg=pbcopper&arch=ppc64el

pbcopper currently ftbfs on pcp64el. I think this is a bug in simde:

https://github.com/nemequ/simde/issues/325

but anyway, I'm attaching the workaround I just uploaded to Ubuntu.

Cheers,
mwh


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

Kernel: Linux 5.4.0-31-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
--- a/src/align/cssw/ssw.c
+++ b/src/align/cssw/ssw.c
@@ -35,6 +35,9 @@
  *
  */
 
+#ifdef __powerpc64__
+#define SIMDE_NO_NATIVE
+#endif
 #define SIMDE_ENABLE_NATIVE_ALIASES
 #include "simde/x86/sse2.h"
 #include 
--- a/src/align/cssw/ssw.h
+++ b/src/align/cssw/ssw.h
@@ -11,6 +11,9 @@
 #ifndef SSW_H
 #define SSW_H
 
+#ifdef __powerpc64__
+#define SIMDE_NO_NATIVE
+#endif
 #define SIMDE_ENABLE_NATIVE_ALIASES
 #include "simde/x86/sse2.h"
 #include 
--- End Message ---
--- Begin Message ---
Source: pbcopper
Source-Version: 1.6.0+dfsg-2
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 May 2020 13:28:10 +0200
Source: pbcopper
Binary: libpbcopper-dev libpbcopper1.6.0 libpbcopper1.6.0-dbgsym
Architecture: source amd64
Version: 1.6.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libpbcopper-dev - data structures, algorithms, and utilities for C++ 
applications -
 libpbcopper1.6.0 - data structures, algorithms, and utilities for C++ 
applications
Closes: 959409 960219 961581
Changes:
 pbcopper (1.6.0+dfsg-2) unstable; urgency=medium
 .
   * Use d-shlibs to make sure SOVERSION is correct
 Closes: #959409
   * d-shlibs requires explicitly Section: libs
   * Restrict architectures to 64bit
 Closes: #960219
   * Fix simde build for ppc64el (thanks to Michael Hudson-Doyle for the patch)
 Closes: #961581
Checksums-Sha1:
 37494938d6ef434f2a89e3ef336b85531245d03a 2349 pbcopper_1.6.0+dfsg-2.dsc
 1cced55276ec3f0d2facd8388ef8e707076f1c32 5800 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 1db0280bbdcbb63f0e5050225eff2782c95bdf81 579124 
libpbcopper-dev_1.6.0+dfsg-2_amd64.deb
 fbbcdbc816bfa600f759ecebca24d260ec77f554 6661996 
libpbcopper1.6.0-dbgsym_1.6.0+dfsg-2_amd64.deb
 32b6118e3e5324d367218476c86cb9a3dd567a16 340360 
libpbcopper1.6.0_1.6.0+dfsg-2_amd64.deb
 f03c5c331c558930e2ff55663f4931b71cf545d9 7776 
pbcopper_1.6.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 4a6f16e941f9c20fd7094022681aad5a0fb6a398fd3a3aa5036a22ab79a5ff3c 2349 
pbcopper_1.6.0+dfsg-2.dsc
 7721b8f92c0b9b90cf9a9f6c4363bfaee3354075b913b112970e33cb6c2befb8 5800 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 dd8fda2f86a06c8d31452498baaad30d6f46cb1526935942e78fa10e2f3d382e 579124 
libpbcopper-dev_1.6.0+dfsg-2_amd64.deb
 d264405f26e5da290c024495f01da934dbc8fd4271ea85cb176ca9fcca454606 6661996 
libpbcopper1.6.0-dbgsym_1.6.0+dfsg-2

Bug#960219: marked as done (pbcopper FTBFS on 32bit: int128 not available)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:00:10 +
with message-id 
and subject line Bug#960219: fixed in pbcopper 1.6.0+dfsg-2
has caused the Debian Bug report #960219,
regarding pbcopper FTBFS on 32bit: int128 not available
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.)


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

https://buildd.debian.org/status/package.php?p=pbcopper&suite=sid

...
../include/pbcopper/pbmer/DnaBit.h:16:26: error: expected type-specifier before 
‘__int128’
   16 | __extension__ using BI = __int128;
  |  ^~~~
...


int128 is not available on 32bit systems,
I don't know whether upstream cares about that.
--- End Message ---
--- Begin Message ---
Source: pbcopper
Source-Version: 1.6.0+dfsg-2
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 May 2020 13:28:10 +0200
Source: pbcopper
Binary: libpbcopper-dev libpbcopper1.6.0 libpbcopper1.6.0-dbgsym
Architecture: source amd64
Version: 1.6.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libpbcopper-dev - data structures, algorithms, and utilities for C++ 
applications -
 libpbcopper1.6.0 - data structures, algorithms, and utilities for C++ 
applications
Closes: 959409 960219 961581
Changes:
 pbcopper (1.6.0+dfsg-2) unstable; urgency=medium
 .
   * Use d-shlibs to make sure SOVERSION is correct
 Closes: #959409
   * d-shlibs requires explicitly Section: libs
   * Restrict architectures to 64bit
 Closes: #960219
   * Fix simde build for ppc64el (thanks to Michael Hudson-Doyle for the patch)
 Closes: #961581
Checksums-Sha1:
 37494938d6ef434f2a89e3ef336b85531245d03a 2349 pbcopper_1.6.0+dfsg-2.dsc
 1cced55276ec3f0d2facd8388ef8e707076f1c32 5800 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 1db0280bbdcbb63f0e5050225eff2782c95bdf81 579124 
libpbcopper-dev_1.6.0+dfsg-2_amd64.deb
 fbbcdbc816bfa600f759ecebca24d260ec77f554 6661996 
libpbcopper1.6.0-dbgsym_1.6.0+dfsg-2_amd64.deb
 32b6118e3e5324d367218476c86cb9a3dd567a16 340360 
libpbcopper1.6.0_1.6.0+dfsg-2_amd64.deb
 f03c5c331c558930e2ff55663f4931b71cf545d9 7776 
pbcopper_1.6.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 4a6f16e941f9c20fd7094022681aad5a0fb6a398fd3a3aa5036a22ab79a5ff3c 2349 
pbcopper_1.6.0+dfsg-2.dsc
 7721b8f92c0b9b90cf9a9f6c4363bfaee3354075b913b112970e33cb6c2befb8 5800 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 dd8fda2f86a06c8d31452498baaad30d6f46cb1526935942e78fa10e2f3d382e 579124 
libpbcopper-dev_1.6.0+dfsg-2_amd64.deb
 d264405f26e5da290c024495f01da934dbc8fd4271ea85cb176ca9fcca454606 6661996 
libpbcopper1.6.0-dbgsym_1.6.0+dfsg-2_amd64.deb
 d87e8d3217979396056271fb3b03aa168d369eddead3d00d047213259f321f39 340360 
libpbcopper1.6.0_1.6.0+dfsg-2_amd64.deb
 7835d82de8d1efea615219f6291061fccc80a11f220a367ca2997473b52036c7 7776 
pbcopper_1.6.0+dfsg-2_amd64.buildinfo
Files:
 67adf91e0729cc61b86cc965e326d8f2 2349 science optional 
pbcopper_1.6.0+dfsg-2.dsc
 cc636c8a9e9e17e0b807f99952a6234a 5800 science optional 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 ee790a5178061b2a0571b46f33ab8072 579124 libdevel optional 
libpbcopper-dev_1.6.0+dfsg-2_amd64.deb
 8e803dc79e36cc0176c5c8565c84d384 6661996 debug optional 
libpbcopper1.6.0-dbgsym_1.6.0+dfsg-2_amd64.deb
 964e4e6fc3101df4abdfaac3f5cb6ccf 340360 libs optional 
libpbcopper1.6.0_1.6.0+dfsg-2_amd64.deb
 1d89d71370eededd3719358ab5fc1c1c 7776 science optional 
pbcopper_1.6.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7NiQ8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGbsg//WfAI4dfete1eiMGCCpcn2JsQPwJQtjBG
iEgFvyOpL9Dy2NLl9HLvfzAzYbCEBg7bJBYpU92aINecm+iXYjDh/RKQ7idPWLMK
0fKWGLR6dRj/2KIhabw6xEaP79NkoS2

Bug#959409: marked as done (pbcopper breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 10:00:10 +
with message-id 
and subject line Bug#959409: fixed in pbcopper 1.6.0+dfsg-2
has caused the Debian Bug report #959409,
regarding pbcopper breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot 
open shared object file: No such file or directory
to be marked as done.

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

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


-- 
959409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbcopper, pbbam
Control: found -1 pbcopper/1.4.0+dfsg-1
Control: found -1 pbbam/1.0.6+dfsg-2
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 pbcopper the autopkgtest of pbbam fails in
testing when that autopkgtest is run with the binary packages of
pbcopper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
pbcopper   from testing1.4.0+dfsg-1
pbbam  from testing1.0.6+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. To be honest,
this looks a bit messy. 1) libpbcopper.so.1.4.0 is shipped by a package
called libpbcopper1.3.0 (this may be correct, but very confusing; didn't
investigate further). 2) pbmerge is opening libpbcopper.so.1.3.0 instead
of something like libpbcopper.so.1 (and following symlinks). This may be
correct (again, I didn't investigate), but it makes updates to pbcopper
very fragile (as in this case) and isn't what normally happens with
libraries, where the symlinks make it possible to update the package
without rebuilding if SONAME compatibility is maintained, and otherwise
trigger a transition that can be handled by the release team.

Currently this regression is blocking the migration of pbcopper 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=pbcopper

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pbbam/5248083/log.gz

   $ $PBMERGE $HQREGION_BAM $SCRAPS_BAM > $MERGED_BAM
+  pbmerge: error while loading shared libraries: libpbcopper.so.1.3.0:
cannot open shared object file: No such file or directory
+  [127]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pbcopper
Source-Version: 1.6.0+dfsg-2
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 May 2020 13:28:10 +0200
Source: pbcopper
Binary: libpbcopper-dev libpbcopper1.6.0 libpbcopper1.6.0-dbgsym
Architecture: source amd64
Version: 1.6.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libpbcopper-dev - data structures, algorithms, and utilities for C++ 
applications -
 libpbcopper1.6.0 - data structures, algorithms, and utilities for C++ 
applications
Closes: 959409 960219 961581
Changes:
 pbcopper (1.6.0+dfsg-2) unstable; urgency=medium
 .
   * Use d-shlibs to make sure SOVERSION is correct
 Closes: #959409
   * d-shlibs requires explicitly Section: libs
   * Restrict architectures to 64bit
 Closes: #960219
   * Fix simde build for ppc64el (thanks to Michael Hudson-Doyle for the patch)
 Closes: #961581
Checksums-Sha1:
 37494938d6ef434f2a89e3ef336b85531245d03a 2349 pbcopper_1.6.0+dfsg-2.dsc
 1cced55276ec3f0d2facd8388ef8e707076f1c32 5800 
pbcopper_1.6.0+dfsg-2.debian.tar.xz
 1db0280bbdcbb63f0e5050225eff2782c95bdf81 

Bug#961647: akonadi: FTBFS on armel: missing -latomic

[Sandro Knauß]

Hey,

Whoo I'm quite impressed to have two different solutions that fast! Thank you 
both for proposing me solutions. You made my day!

> The easy workaround is in debian/rules:
> 
> ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc sh4))
>   export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic
> -Wl,--as-needed endif

thanks for this easy workaround! I implemented that one for now.

> It might, but due to gcc defaulting to -Wl,--as-needed it wouldn't be an 
issue. There is also https://phabricator.kde.org/D16184 that only links 
libatomic if necessary.

I will propose a proper patch upstream based on the patch you proposed. Maybe 
we integrate CheckAtomic into extra-cmake-modules.

hefee

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

Processed: Bug#961646 marked as pending in node-deep-for-each

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #961646 [node-deep-for-each] node-deep-for-each breaks node-grunt-webpack
Added tag(s) pending.

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

Bug#961646: marked as pending in node-deep-for-each

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #961646 in node-deep-for-each 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/js-team/node-deep-for-each/-/commit/49821500526523ff148398291d6306ccf71e9b3a


Build with babel-plugin-add-module-exports

Closes: #961646


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/961646

Bug#961647: akonadi: FTBFS on armel: missing -latomic

[Adrian Bunk]

On Wed, May 27, 2020 at 11:02:50AM +0200, Sandro Knauß wrote:
> Hey,
> 
> > This is caused by a missing -latmoic. See also
> > https://buildd.debian.org/status/fetch.php?pkg=akonadi&arch=armel&ver=4%3A20
> > .04.1-1&stamp=1590553675&raw=0
> 
> thanks for this fast scan and also proposing a solution. But I have no 
> example 
> of how I need to modify cmake to end up having -latomic for armel being 
> added. 
> Do you know anything?
> I found one solution to add atomic everywhere, but this may be an overkill: 
> https://github.com/mavlink/mavros/pull/790/files
>...

The easy workaround is in debian/rules:

ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc sh4))
  export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic -Wl,--as-needed
endif


> hefee

cu
Adrian

Processed: Bug#959558 marked as pending in sphinx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #959558 [python3-sphinx] case: FTBFS: AttributeError: 'tuple' object has no 
attribute 'lstrip'
Added tag(s) pending.

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

Bug#959558: marked as pending in sphinx

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/sphinx/-/commit/13fd7ebf72c60df553efe3a7e7dc75e619cb


Make autodoc skip mocked objects.

Closes: #959558.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959558

Bug#961647: akonadi: FTBFS on armel: missing -latomic

[Sebastian Ramacher]

Hi

On 2020-05-27 11:02:50 +0200, Sandro Knauß wrote:
> > This is caused by a missing -latmoic. See also
> > https://buildd.debian.org/status/fetch.php?pkg=akonadi&arch=armel&ver=4%3A20
> > .04.1-1&stamp=1590553675&raw=0
> 
> thanks for this fast scan and also proposing a solution. But I have no 
> example 
> of how I need to modify cmake to end up having -latomic for armel being 
> added. 
> Do you know anything?
> I found one solution to add atomic everywhere, but this may be an overkill: 
> https://github.com/mavlink/mavros/pull/790/files

It might, but due to gcc defaulting to -Wl,--as-needed it wouldn't be an
issue. There is also https://phabricator.kde.org/D16184 that only links
libatomic if necessary.

> So far I see the libboost-atomic1.67-dev is already installed, that means I 
> don't have to install anything additionally. So at least I don't have to 
> modify build-depends.

Note that's a different atomic. akonadi needs to link GCC's libatomic.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#959558: case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-sphinx 2.4.3-2
Bug #959558 [src:case] case: FTBFS: AttributeError: 'tuple' object has no 
attribute 'lstrip'
Bug reassigned from package 'src:case' to 'python3-sphinx'.
No longer marked as found in versions case/1.5.3+dfsg-3.
Ignoring request to alter fixed versions of bug #959558 to the same values 
previously set
Bug #959558 [python3-sphinx] case: FTBFS: AttributeError: 'tuple' object has no 
attribute 'lstrip'
Marked as found in versions sphinx/2.4.3-2.

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

Bug#959558: case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip'

[Dmitry Shachnev]

Control: reassign -1 python3-sphinx 2.4.3-2

On Sun, May 03, 2020 at 02:47:46PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> [...]
> > AttributeError: 'tuple' object has no attribute 'lstrip'

I will fix this in the next sphinx upload.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#961592: r-bioc-gviz: autopkgtest regression

[Dylan Aïssi]

Hi,

Le mer. 27 mai 2020 à 11:12, Andreas Tille  a écrit :
>
> Ahhh, its new to me that pkg-r-autopkgtest does more than just
> loading the library.  Hmmm, Dylan, do you have any idea besides
> patching the test suite?
>

I am testing my patch that skip the test if
"BSgenome.Hsapiens.UCSC.hg19" is not available, so this bug should be
fixed soon.

But, regarding https://bugs.debian.org/961591 , I have no idea how to fix it.

Best,
Dylan

Bug#961592: r-bioc-gviz: autopkgtest regression

[Andreas Tille]

Hi Graham,

On Wed, May 27, 2020 at 11:13:07AM +0200, Graham Inggs wrote:
> 
> Note this is not run-unit-test, this is pkg-r-autopkgtest.

Ahhh, its new to me that pkg-r-autopkgtest does more than just
loading the library.  Hmmm, Dylan, do you have any idea besides
patching the test suite?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#961592: r-bioc-gviz: autopkgtest regression

[Graham Inggs]

Hi Andreas

On Wed, 27 May 2020 at 10:55, Andreas Tille  wrote:
> That's strange.  The autopkgtest should not run.  r-bioc-gviz source
> has
>
> debian/tests/control_unused
>
> to deactivate its test.  Has anything changed in debci that fetches
> anything that looks like a test script?

Note this is not run-unit-test, this is pkg-r-autopkgtest.

Regards
Graham

Bug#961647: akonadi: FTBFS on armel: missing -latomic

[Sandro Knauß]

Hey,

> This is caused by a missing -latmoic. See also
> https://buildd.debian.org/status/fetch.php?pkg=akonadi&arch=armel&ver=4%3A20
> .04.1-1&stamp=1590553675&raw=0

thanks for this fast scan and also proposing a solution. But I have no example 
of how I need to modify cmake to end up having -latomic for armel being added. 
Do you know anything?
I found one solution to add atomic everywhere, but this may be an overkill: 
https://github.com/mavlink/mavros/pull/790/files

So far I see the libboost-atomic1.67-dev is already installed, that means I 
don't have to install anything additionally. So at least I don't have to 
modify build-depends.

hefee


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

Bug#961592: r-bioc-gviz: autopkgtest regression

[Andreas Tille]

Hi Graham,

On Tue, May 26, 2020 at 02:37:04PM +0200, Graham Inggs wrote:
> Since the upload of 1.32.0+dfsg-1, r-bioc-gviz has been failing its
> own autopkgtests [1].   This now prevents the migration of r-base.
> I've copied what I hope is the relevant part of the log below.

That's strange.  The autopkgtest should not run.  r-bioc-gviz source
has

debian/tests/control_unused

to deactivate its test.  Has anything changed in debci that fetches
anything that looks like a test script?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#961357: marked as done (r-cran-etm: autopktest failure)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 08:36:24 +
with message-id 
and subject line Bug#961357: fixed in r-cran-etm 1.1-2
has caused the Debian Bug report #961357,
regarding r-cran-etm: autopktest failure
to be marked as done.

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

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


-- 
961357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-etm
Version: 1.1-1
Severity: serious

r-cran-etm's autopktest currently fails with
| --- tests.etm.Rout.save_  2020-05-19 15:07:33.895363332 +
| +++ tests.etm.Rout_   2020-05-19 15:07:33.899363322 +
| @@ -554,16 +554,21 @@
|  +   cens.name = "cens", keep = "cova")
|  > 
|  > newdat
| -  id entry exit from   to cova
| -1  1 03011
| -2  1 36121
| -3  2 04010
| -4  2 49120
| -5  3 03011
| -6  3 38121
| -7  4 06020
| -8  5 08021
| -9  6 090 cens1
| +   id entry exit from   to cova
| +1   1 03011
| +2   1 36121
| +3   1 662 cens1
| +4   2 04010
| +5   2 49120
| +6   2 992 cens0
| +7   3 03011
| +8   3 38121
| +9   3 882 cens1
| +10  4 06020
| +11  4 662 cens0
| +12  5 08021
| +13  5 882 cens1
| +14  6 090 cens1
|  > 
|  > ref <- data.frame(id = c(1, 1, 2, 2, 3, 3, 4, 5, 6),
|  +   entry = c(0, 3, 0, 4, 0, 3, 0, 0, 0),
| @@ -575,7 +580,13 @@
|  > ref$to <- factor(as.character(ref$to), levels = c("0", "1", "2", "cens"))
|  > 
|  > all.equal(ref, newdat)
| -[1] TRUE
| +[1] "Attributes: < Component \"row.names\": Numeric: lengths (9, 14) differ 
>"
| +[2] "Component \"id\": Numeric: lengths (9, 14) differ"  
 
| +[3] "Component \"entry\": Numeric: lengths (9, 14) differ"   
 
| +[4] "Component \"exit\": Numeric: lengths (9, 14) differ"
 
| +[5] "Component \"from\": 'current' is not a factor"  
 
| +[6] "Component \"to\": 'current' is not a factor"
 
| +[7] "Component \"cova\": Numeric: lengths (9, 14) differ"
 
|  > 
|  > 
|  > ##
| autopkgtest [15:07:34]: test run-unit-test: ---]
| autopkgtest [15:07:34]: test run-unit-test:  - - - - - - - - - - results - - 
- - - - - - - -
| run-unit-testFAIL non-zero exit status 1

See
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-etm/5565165/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-cran-etm
Source-Version: 1.1-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-etm, 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.
Dylan Aïssi  (supplier of updated r-cran-etm 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, 27 May 2020 09:51:44 +0200
Source: r-cran-etm
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 961357
Changes:
 r-cran-etm (1.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Re-write DEP-8 tests to avoid to compare "expected" outputs (*.Rout.save)
  with our outputs. They are not expected to be identical, the
  "CRAN Package Check Results" show differences.
  Comparing theses outputs produce a lot of false positive.
  (Closes: #961357)
Checksums-Sha1:
 82b2606b14bf8ae54c9f7aacdacd723690ea48ea 2109 r-cran-etm_1.1-2.dsc
 402b5b18b91cba5d06e948240d7147f91fc26bc5 3540 r-cran-etm_1.1-2.debian.tar.xz
 bf0b6976027ea0a66283f34c488619d46063c172 8956 r-cran-etm_1.1-2_amd64.buildinfo
Checksum

Bug#961490: fwupd: version in stable too old, no updates possible

[Luca Boccassi]

On Wed, 2020-05-27 at 02:58 +0200, Matthias Klumpp wrote:
> Am Di., 26. Mai 2020 um 20:24 Uhr schrieb :
> > > -Original Message-
> > > From: Ansgar 
> > > Sent: Tuesday, May 26, 2020 8:01 AM
> > > To: Steffen Schreiber; 961...@bugs.debian.org
> > > Subject: Bug#961490: fwupd: version in stable too old, no updates possible
> > > 
> > > 
> > > [EXTERNAL EMAIL]
> > > 
> > > Hi,
> > > 
> > > On Tue, 2020-05-26 at 13:56 +0200, Steffen Schreiber wrote:
> > > > So I see you marked this bug as fixed/resolved.
> > > 
> > > Someone (not the maintainer) did so, but please note that the bug
> > > remains open even when marked as fixed in a newer version.  Debian's
> > > stable release team prefers bugs to be fixed in unstable/testing before
> > > they get fixed in (old)stable, so this is good.
> > 
> > The particular circumstances of this issue are that the update in question 
> > requires
> > a newer version of fwupd than is in stable.  This is not a matter of just 
> > backporting
> > a change or two and it works.  There are daemon and plugin level changes 
> > that have to
> > go together to guarantee a proper update.
> > 
> > This seems incompatible with the documentation around uploading to stable.
> > https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
> > > > What's the way going forward for users of stable? Installing packages
> > > > from testing? Are you recommending to just forget about running Debian
> > > > stable as is?
> > > 
> > > The maintainer hasn't yet commented on how he wants to proceed.
> > > Reasonable options seem to be to either update stable to the version
> > > currently in testing (1.3.9) or to update to a later version of 1.2.X.
> > > 
> > > Ansgar
> > 
> > If a particular update requires a newer fwupd version I don't think it's 
> > reasonable
> > to push that version to all Debian users who may not need the newer fwupd 
> > version
> > and might not be willing to accept the risk of regressions in a newer 
> > version.
> > 
> > "Fixes must be minimal and relevant"
> > 
> > So in this circumstance if your device needs the newer version you should 
> > probably
> > take the package from testing instead.
> 
> Maybe talk to the release-team - they will probably not like adding a
> change this big, but exceptions are always possible (e.g. firefox-esr
> is exempt from this rule).
> In any case though, you could provide a backport of the latest version
> for easy installation by stable users as the next-best option :-)
> 
> Cheers,
> Matthias

Hi,

IMHO this qualifies for proposed-updates - not being able to update
firmwares in this day and age exposes users to huge risks from the
security point of view.
Especially if, as it seems, upstream maintains stable branches. We
already have a number of packages that get new LTS versions via
proposed-updates - firefox being one, but not the only one.

-- 
Kind regards,
Luca Boccassi


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

Bug#961636: [debian-mysql] Bug#961636: src:galera-3: fails to migrate to testing for too long: ftbfs on armel

[Otto Kekäläinen]

Thanks for the report!

There are new upstream releases of both Galera 3 and Galera 4, and I
intend to upload them and work with any remaining FTBFS issues in
coming weeks.

Bug#961485: marked as done (r-cran-sp: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 27 May 2020 07:49:50 +
with message-id 
and subject line Bug#961485: fixed in r-cran-sp 1:1.4-2-2
has caused the Debian Bug report #961485,
regarding r-cran-sp: autopkgtest regression
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.)


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

Hi Maintainer

Since the upload of 1:1.4-2-1, r-cran-sp has been failing its own
autopkgtests [1].  This now prevents the migration of r-base.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-sp/unstable/amd64/


autopkgtest [09:03:38]: test run-unit-test: [---
Test base passed
--- fail1.Rout.save_ 2020-05-24 09:03:40.508583188 +
+++ fail1.Rout_ 2020-05-24 09:03:40.512583197 +
@@ -208,10 +208,8 @@
 Error in CRS("+proj=latlon +ellps=WGS84") :
   northings must follow eastings: +proj=latlon +ellps=WGS84
 > try(CRS("+proj=lonlat +ellps=WGS84"))
-CRS arguments: +proj=longlat +ellps=WGS84 +no_defs
-Warning messages:
-1: In CRS("+proj=lonlat +ellps=WGS84") :
+CRS arguments: +proj=longlat +ellps=WGS84
+Warning message:
+In CRS("+proj=lonlat +ellps=WGS84") :
   'lonlat' changed to 'longlat': +proj=longlat +ellps=WGS84
-2: In showSRID(uprojargs, format = "PROJ", multiline = "NO") :
-  Discarded datum Unknown based on WGS84 ellipsoid in CRS definition
 >
autopkgtest [09:03:40]: test run-unit-test: ---]
autopkgtest [09:03:40]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
run-unit-testFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: r-cran-sp
Source-Version: 1:1.4-2-2
Done: =?utf-8?q?Dylan_A=C3=AFssi?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-sp, 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.
Dylan Aïssi  (supplier of updated r-cran-sp 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, 27 May 2020 09:31:48 +0200
Source: r-cran-sp
Architecture: source
Version: 1:1.4-2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Dylan Aïssi 
Closes: 961485
Changes:
 r-cran-sp (1:1.4-2-2) unstable; urgency=medium
 .
   * Team upload.
   * Re-write DEP-8 tests to avoid to compare "expected" outputs (*.Rout.save)
  with our outputs. They are not expected to be identical, the
  "CRAN Package Check Results" show differences.
  Comparing theses outputs produce a lot of false positive.
  (Closes: #961485)
Checksums-Sha1:
 45670bf2964d93d962e75060c364aeaec03df0ce 2035 r-cran-sp_1.4-2-2.dsc
 942caa1b7870a8cb762e6259d034114ac6a0b1d1 4416 r-cran-sp_1.4-2-2.debian.tar.xz
 aca0be3e80202698694fbd83f3e36bafc5217788 8701 r-cran-sp_1.4-2-2_amd64.buildinfo
Checksums-Sha256:
 ea9ef9c139754491a6ec7e3e46952e1f614079bbbe06f3adb50817aa224d3d89 2035 
r-cran-sp_1.4-2-2.dsc
 cf98faaaeb1b31b760f45fb0639127b38b88de34874ca925409af579ab2b2263 4416 
r-cran-sp_1.4-2-2.debian.tar.xz
 a42dd0cdd2efe764ca3904caa8cdab9cb812e9f424980c0af9c02fe2a2b27389 8701 
r-cran-sp_1.4-2-2_amd64.buildinfo
Files:
 8b50a744f5066ea65fa866efa509af94 2035 gnu-r optional r-cran-sp_1.4-2-2.dsc
 ff558602234682284bde8ee0a4a492a9 4416 gnu-r optional 
r-cran-sp_1.4-2-2.debian.tar.xz
 0ad1546ad8f0e59c2fd9f20f365ce802 8701 gnu-r optional 
r-cran-sp_1.4-2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl7OGNgACgkQYS7xYT4F
D1RM7g//cEm7m4PcPhJYvkz6bfmkcv41bf1jKwbFRjv7TZfRySQrdK2bgt7urxbs
aRctauDmgV2M+Ti8yZANUr+2xXoQ8yS9/lVOiIXYJh9nE9VFG7jYze/XG80Ozxvz
zIRbnK14STIdejtFdxfloB2ZWPUylUG4Esp3U4ybbQMMj7vSBzq271MSCWi+QckN
HpVqIySbybdQA7YJWE/hMFoq1wptnbIXG8e51HPiZ7ZJq0fQvs8xKO3Zrm8JPVzg
yLVYii9xEUravHz2TQdq18P4RgVaR+WB4PKplVyDGq7OlqXUVsHBUCsl6ewA+u4y
RUZggp3ewTon+IaXO9KfxRysLuKeo25384wVxXwj8KJ3

Bug#961649: php-horde-gollem: CVE-2020-8034

[Salvatore Bonaccorso]

Source: php-horde-gollem
Version: 3.0.12-5
Severity: grave
Tags: security upstream
Control: found -1 3.0.12-3

Hi,

The following vulnerability was published for php-horde-gollem.

CVE-2020-8034[0]:
| Gollem before 3.0.13, as used in Horde Groupware Webmail Edition
| 5.2.22 and other products, is affected by a reflected Cross-Site
| Scripting (XSS) vulnerability via the HTTP GET dir parameter in the
| browser functionality, affecting breadcrumb output. An attacker can
| obtain access to a victim's webmail account by making them visit a
| malicious URL.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-8034
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8034
[1] https://lists.horde.org/archives/announce/2020/001289.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: php-horde-gollem: CVE-2020-8034

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.0.12-3
Bug #961649 [src:php-horde-gollem] php-horde-gollem: CVE-2020-8034
Marked as found in versions php-horde-gollem/3.0.12-3.

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

Bug#954148: doit: diff for NMU version 0.31.1-3.3

[Adrian Bunk]

Control: tags 954148 + patch
Control: tags 954148 + pending

Dear maintainer,

I've prepared an NMU for doit (versioned as 0.31.1-3.3) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru doit-0.31.1/debian/changelog doit-0.31.1/debian/changelog
--- doit-0.31.1/debian/changelog	2020-02-02 14:23:58.0 +0200
+++ doit-0.31.1/debian/changelog	2020-05-27 10:06:51.0 +0300
@@ -1,3 +1,11 @@
+doit (0.31.1-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't run an autopkgtest that downloads code from the internet.
+(Closes: #954148)
+
+ -- Adrian Bunk   Wed, 27 May 2020 10:06:51 +0300
+
 doit (0.31.1-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru doit-0.31.1/debian/tests/control doit-0.31.1/debian/tests/control
--- doit-0.31.1/debian/tests/control	2019-11-15 20:59:07.0 +0200
+++ doit-0.31.1/debian/tests/control	2020-05-27 10:01:35.0 +0300
@@ -1,7 +1,6 @@
-Tests: version, unittests
+Tests: version
 Depends: @,
  python3-pytest,
- python3-pip,
  python3-wheel,
  python3-pyflakes,
  python3-pytest,
diff -Nru doit-0.31.1/debian/tests/unittests doit-0.31.1/debian/tests/unittests
--- doit-0.31.1/debian/tests/unittests	2019-11-15 21:02:13.0 +0200
+++ doit-0.31.1/debian/tests/unittests	2020-05-27 10:03:10.0 +0300
@@ -1,2 +1,4 @@
-pip3 install --no-warn-script-location -r dev_requirements.txt
+# not allowed, see #954148
+#pip3 install --no-warn-script-location -r dev_requirements.txt
+
 doit ut

Processed: doit: diff for NMU version 0.31.1-3.3

[Debian Bug Tracking System]

Processing control commands:

> tags 954148 + patch
Bug #954148 [src:doit] src:doit: autopkgtest requires packages outside the 
Debian archive
Added tag(s) patch.
> tags 954148 + pending
Bug #954148 [src:doit] src:doit: autopkgtest requires packages outside the 
Debian archive
Added tag(s) pending.

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