Processed: src:directfb: fails to migrate to testing for too long: FTBFS on armel and armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.7.7-10
Bug #1012383 [src:directfb] src:directfb: fails to migrate to testing for too 
long: FTBFS on armel and armhf
Marked as fixed in versions directfb/1.7.7-10.
Bug #1012383 [src:directfb] src:directfb: fails to migrate to testing for too 
long: FTBFS on armel and armhf
Marked Bug as done

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

Bug#1012383: src:directfb: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Source: directfb
Version: 1.7.7-9
Severity: serious
X-Debbugs-CC: Andreas Beckmann 
Control: close -1 1.7.7-10
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s), Andreas,

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:directfb has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The package fails to build from 
source on armel and armhf where it successfully built in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4

[Paul Gevers]

Source: pktanon
Version: 2~git20160407.0.2bde4f2+dfsg-9
Severity: serious

Hi,

Your package has an autopkgtest, great. However, it fails on s390x. I
have attached the relevant piece of the log [1]. I'd like to note that
s390x is big-endian. Maybe the check for the version fails somehow?

Paul

[1] 
https://ci.debian.net/data/autopkgtest/testing/s390x/p/pktanon/22395337/log.gz

autopkgtest [23:55:15]: test run-example: [---
---
pktanon --- profile-based traffic anonymization
---
initializing PktAnon,  configuration = 
/usr/share/doc/pktanon/examples/profiles/profile.xml
istream: opened file 
/tmp/autopkgtest-lxc.1djzl_hk/downtmp/build.oQb/src/profiles/sample.pcap
ostream: opened output file ./out.pcap
initialized
error: wrong pcap file version: should be 2.4
error: unsupported link type: 16777216
autopkgtest [23:55:16]: test run-example: ---]

Bug#1012279: php-horde-turba: CVE-2022-30287

[Juri Grabowski]

Hello together,

On 2022-06-05 14:35 7, Salvatore Bonaccorso wrote:

it looks that the force pushed commit two days ago adjusted two
further create() -> createTrusted() stances in lib/Application.php,
can you double check?

functions backup and _restoreContact are only available on turba/master
for future release.

Best Regards,
Juri Grabowski

Bug#1011420: marked as done (opencu: missing Breaks+Replaces: cu)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 02:34:10 +
with message-id 
and subject line Bug#1011420: fixed in opencu 3-3
has caused the Debian Bug report #1011420,
regarding opencu: missing Breaks+Replaces: cu
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package opencu.
  Preparing to unpack .../archives/opencu_3-2_amd64.deb ...
  Unpacking opencu (3-2) ...
  dpkg: error processing archive /var/cache/apt/archives/opencu_3-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/cu', which is also in package cu 1.07-27+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/opencu_3-2_amd64.deb


How are cu and opencu supposed to co-exist?
Is cu supposed to be removed from the archive?


cheers,

Andreas


cu=1.07-27+b1_opencu=3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: opencu
Source-Version: 3-3
Done: Tobias Heider 

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

Debian distribution maintenance software
pp.
Tobias Heider  (supplier of updated opencu 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: Mon, 23 May 2022 21:37:14 +0200
Source: opencu
Architecture: source
Version: 3-3
Distribution: unstable
Urgency: medium
Maintainer: Tobias Heider 
Changed-By: Tobias Heider 
Closes: 1011420
Changes:
 opencu (3-3) unstable; urgency=medium
 .
   * Add Breaks + Replaces cu (Closes: #1011420).
Checksums-Sha1:
 cbc063ef9d9843dda9675b80e4a99bef25489cca 1799 opencu_3-3.dsc
 fdf8130b68ba1f15600df5a123dc85bfa6dcda98 2428 opencu_3-3.debian.tar.xz
 e93d25b9611a209d8ea38fa7047dd49fffd70f96 7062 opencu_3-3_amd64.buildinfo
Checksums-Sha256:
 55d8f06d59837dfdfb619a99f206917ca883211abd7fb3d2710faacd4315a186 1799 
opencu_3-3.dsc
 cbbb99ea783f7d8db5073fb3f00848f655853b35df080e38dc638a4b2e2fcc07 2428 
opencu_3-3.debian.tar.xz
 e3c5b556849c83377feeb584df54754f885e20980fcadb50a690e6b6fd2eaf91 7062 
opencu_3-3_amd64.buildinfo
Files:
 f4007cb7d30d94acc213fe167b1527dc 1799 misc optional opencu_3-3.dsc
 6f9e746afbed948f47f4ee8c13a9ac6c 2428 misc optional opencu_3-3.debian.tar.xz
 1bbd28b9c888a2e3b9f85e4846a14024 7062 misc optional opencu_3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEP7FHOW9as2zJ9q6CWXuniu1D+jAFAmKdZEAACgkQWXuniu1D
+jDbqw//e6EpiILfb5RWCZ0494ruS2OQiiYFD+o/MinceVE3OXPyQug3iFJsybFY
nGpeGTmRTbD5f8A+ueNoDaxhN7eFOmzp0vkuXZh9i0DN6ojaXkL0DK8xBfAbdGpa
ffKHhIxb6l+FncUCtyXwJriS2dA5B0yUHqFPNW0Mf/Yx4wqegilqJsspgNVAJ3B3
aiZrvZjwkxvGNFn3c7pLtwRCziICdJb2M5cBq7Pn5CQp7odIY2uux5gd/vGxWC6A
wHW/J1dIzOFRYRuPtk1SybbPEsLY58wPh2TEOgHsNa8XyUqBZJEx18PLhIng98KT
s+tU6bxroqkWfTOBZReMfSvfOysXzRp0wJ/s391m8LX+w8pd9Q69HwZLDgj48+jh
l1kj9WVzr9RoMl3EhjITzbPaO2rNAB2JVXyiqB044hMEUreCCykhy6aS2OZI6dTr
gap8F7c32DpLZIe0+v5QHEom1fXgeQ0QcrHNe44sv/27Nw+mqG6E5AABwfTZC2+I
0/3oNyEgtvrK84IuerPzj6JZu+/TvUGisJcuugeF7zqGMlDd+ast+JrB8MFMKW4I
h3+XJ2CgHqZJVVR2TjiqHO3f8vzKeOExlu4cJAKYFrrumh+JjK8M/aBQNQqae5fg
bFAaBqDBiBQaVA5UZ7BVXiJxg1k/J3inl+gG8WVoKx/KznKLc0w=
=SAGZ
-END PGP SIGNATURE End Message ---

Bug#996273: marked as done (dovecot: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 00:03:57 +
with message-id 
and subject line Bug#996273: fixed in dovecot 1:2.3.19+dfsg1-1
has caused the Debian Bug report #996273,
regarding dovecot: FTBFS with OpenSSL 3.0
to be marked as done.

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

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


-- 
996273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dovecot
Version: 2.3.16+dfsg1-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Hi,

Your package is failing to build using OpenSSL 3.0 with the
following error:
test_get_info_pw_encrypted ... : ok
test-crypto.c:827: Assert failed: ret == TRUE
Panic: file dcrypt-openssl.c: line 2642 (dcrypt_openssl_private_to_public_key): 
assertion failed: (priv_key != NULL && pub_key_r != NULL)
Error: Raw backtrace: ./test-crypto(+0x53775) [0x55cb6b24d775] -> 
./test-crypto(backtrace_get+0x1c) [0x55cb6b24d8ec] -> ./test-crypto(+0x2b23b) 
[0x55cb6b22523b] -> ./test-crypto(+0x2b271) [0x55cb6b225271] -> 
./test-crypto(+0x14d1a) [0x55cb6b20ed1a] -> .libs/libdcrypt_openssl.so(+0x618d) 
[0x7f5058c9018d] -> ./test-crypto(+0x253fa) [0x55cb6b21f3fa] -> 
./test-crypto(+0x2a63d) [0x55cb6b22463d] -> ./test-crypto(test_run+0x5f) 
[0x55cb6b2246df] -> ./test-crypto(main+0x4c) [0x55cb6b2136dc] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f5058cc9e4a] -> 
./test-crypto(_start+0x2a) [0x55cb6b21381a]
/bin/bash: line 1: 161575 Aborted ./$bin


Kurt
--- End Message ---
--- Begin Message ---
Source: dovecot
Source-Version: 1:2.3.19+dfsg1-1
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated dovecot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jun 2022 18:29:18 +
Source: dovecot
Architecture: source
Version: 1:2.3.19+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Dovecot Maintainers 
Changed-By: Noah Meyerhans 
Closes: 996273 1009872
Changes:
 dovecot (1:2.3.19+dfsg1-1) unstable; urgency=medium
 .
   [ Christian Göttsche ]
   * [0d29e45] d/rules: enable LTO via DEB_BUILD_MAINT_OPTIONS instead of 
custom flags
   * [560cceb] d/source/lintian-overrides: update 
very-long-line-length-in-source-file overrides
   * [b99d09e] d/copyright: update years
   * [9ee8271] d/dovecot-core.prerm: drop as superseded by debhelper
   * [907f85c] d/maintscripts: update
   * [2b38240] d/dovecot-core.postinst: drop support for version skips
   * [dcb76d1] d/dovecot-core.postinst: only link certs if existent (Closes: 
#1009872)
   * [d223bbd] d/patches: add patch to support openssl 3.0 (Closes: #996273)
 .
   [ Noah Meyerhans ]
   * [9f3175e] New upstream version 2.3.19+dfsg1
Checksums-Sha1:
 f29eb6b7bea0969162f27c07c32949a1d9e155ef 4140 dovecot_2.3.19+dfsg1-1.dsc
 194a094ed258253b18952fa14f32719857ed80a6 1685254 
dovecot_2.3.19+dfsg1.orig-pigeonhole.tar.gz
 378d81c23718ac85bb0286af93f22df4ead60ee6 7790661 
dovecot_2.3.19+dfsg1.orig.tar.gz
 d21652d798d88c0f624c66e2cbacaef9c564d0b4 866 
dovecot_2.3.19+dfsg1.orig.tar.gz.asc
 3bf4ff6a4194f369a17b35c6876b5a10e3fa6c44 64032 
dovecot_2.3.19+dfsg1-1.debian.tar.xz
 a6d86175b29ddf174c4d480ef87375246c0966a5 7848 
dovecot_2.3.19+dfsg1-1_source.buildinfo
Checksums-Sha256:
 4b8ee228476662a1b1c97172e96e55a149f945facaa53c4cf3745922e04107f7 4140 
dovecot_2.3.19+dfsg1-1.dsc
 eb8efca6aa938d9cfe04e7d2d82438e381bacd935c03dd2c608884119336e253 1685254 
dovecot_2.3.19+dfsg1.orig-pigeonhole.tar.gz
 0173f693d441b6248b8a62aa5fd690021a1f04a12902653e0bf2e5b012fe437b 7790661 
dovecot_2.3.19+dfsg1.orig.tar.gz
 6fccc8472419988c01a75955181f414f9b13abff2e636cfb9959f847d1c5146b 866 
dovecot_2.3.19+dfsg1.orig.tar.gz.asc
 e5e5fc6883021013f6c5d1b3aecfbd564e8d7e7cf88f25e02618af7cc0fabbe2 64032 
dovecot_2.3.19+dfsg1-1.debian.tar.xz
 0291732893d30fe245cc500296bf0adb7d9b70196fc2a08bf34ea141f0091ea8 7848 

Bug#1009872: marked as done (dovecot-core: postinst fails when snakeoil cert is removed)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jun 2022 00:03:57 +
with message-id 
and subject line Bug#1009872: fixed in dovecot 1:2.3.19+dfsg1-1
has caused the Debian Bug report #1009872,
regarding dovecot-core: postinst fails when snakeoil cert is removed
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.)


-- 
1009872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dovecot-core
Version: 1:2.3.13+dfsg1-2
Severity: serious
X-Debbugs-Cc: jcris...@debian.org

This bit of dovecot-core.postinst breaks (at least on the second invocation) if
the snakeoil cert or key don't exist: test -e returns false, but ln -s fails
because the symlink is already there:

  # SSL configuration
  # Use the ssl-cert-snakeoil certificate in the following cases:
  # - On new installations
  # - On upgrades from versions that did not enable SSL by default
  if [ -z "$2" ] || dpkg --compare-versions "$2" lt "1:2.2.31-1~"; then
if [ ! -e /etc/dovecot/private/dovecot.key ] && \
   [ ! -e /etc/dovecot/private/dovecot.pem ]; then
  ln -s /etc/ssl/certs/ssl-cert-snakeoil.pem 
/etc/dovecot/private/dovecot.pem
  ln -s /etc/ssl/private/ssl-cert-snakeoil.key 
/etc/dovecot/private/dovecot.key
fi
  fi


Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: dovecot
Source-Version: 1:2.3.19+dfsg1-1
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated dovecot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jun 2022 18:29:18 +
Source: dovecot
Architecture: source
Version: 1:2.3.19+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Dovecot Maintainers 
Changed-By: Noah Meyerhans 
Closes: 996273 1009872
Changes:
 dovecot (1:2.3.19+dfsg1-1) unstable; urgency=medium
 .
   [ Christian Göttsche ]
   * [0d29e45] d/rules: enable LTO via DEB_BUILD_MAINT_OPTIONS instead of 
custom flags
   * [560cceb] d/source/lintian-overrides: update 
very-long-line-length-in-source-file overrides
   * [b99d09e] d/copyright: update years
   * [9ee8271] d/dovecot-core.prerm: drop as superseded by debhelper
   * [907f85c] d/maintscripts: update
   * [2b38240] d/dovecot-core.postinst: drop support for version skips
   * [dcb76d1] d/dovecot-core.postinst: only link certs if existent (Closes: 
#1009872)
   * [d223bbd] d/patches: add patch to support openssl 3.0 (Closes: #996273)
 .
   [ Noah Meyerhans ]
   * [9f3175e] New upstream version 2.3.19+dfsg1
Checksums-Sha1:
 f29eb6b7bea0969162f27c07c32949a1d9e155ef 4140 dovecot_2.3.19+dfsg1-1.dsc
 194a094ed258253b18952fa14f32719857ed80a6 1685254 
dovecot_2.3.19+dfsg1.orig-pigeonhole.tar.gz
 378d81c23718ac85bb0286af93f22df4ead60ee6 7790661 
dovecot_2.3.19+dfsg1.orig.tar.gz
 d21652d798d88c0f624c66e2cbacaef9c564d0b4 866 
dovecot_2.3.19+dfsg1.orig.tar.gz.asc
 3bf4ff6a4194f369a17b35c6876b5a10e3fa6c44 64032 
dovecot_2.3.19+dfsg1-1.debian.tar.xz
 a6d86175b29ddf174c4d480ef87375246c0966a5 7848 
dovecot_2.3.19+dfsg1-1_source.buildinfo
Checksums-Sha256:
 4b8ee228476662a1b1c97172e96e55a149f945facaa53c4cf3745922e04107f7 4140 
dovecot_2.3.19+dfsg1-1.dsc
 eb8efca6aa938d9cfe04e7d2d82438e381bacd935c03dd2c608884119336e253 1685254 
dovecot_2.3.19+dfsg1.orig-pigeonhole.tar.gz
 0173f693d441b6248b8a62aa5fd690021a1f04a12902653e0bf2e5b012fe437b 7790661 
dovecot_2.3.19+dfsg1.orig.tar.gz
 6fccc8472419988c01a75955181f414f9b13abff2e636cfb9959f847d1c5146b 866 
dovecot_2.3.19+dfsg1.orig.tar.gz.asc
 e5e5fc6883021013f6c5d1b3aecfbd564e8d7e7cf88f25e02618af7cc0fabbe2 64032 
dovecot_2.3.19+dfsg1-1.debian.tar.xz
 0291732893d30fe245cc500296bf0adb7d9b70196fc2a08bf34ea141f0091ea8 7848 
dovecot_2.3.19+dfsg1-1_source.buildinfo
Files:
 e9d709d303a6ebb0f44216a83ec31767 4140 mail optional dovecot_2.3.19+dfsg1-1.dsc
 c4705f71136704a07bd4acc6bd46e26c 1685254 mail optional 
dovecot_2.3.19+dfsg1.orig-pigeonhole.tar.gz
 5d9e43266c489a0c503cf227e7491094 7790661 mail optional 

Bug#999620: marked as done (pktanon: autopkgtest regression on armhf)

[Debian Bug Tracking System]

Your message dated Mon, 6 Jun 2022 01:43:55 +0200
with message-id <0decacca-5d17-88b6-7185-00ca8e1c8...@debian.org>
and subject line Re: Bug#999620: pktanon: autopkgtest regression on armhf
has caused the Debian Bug report #999620,
regarding pktanon: autopkgtest regression on armhf
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.)


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

Source: pktanon
Version: 2~git20160407.0.2bde4f2+dfsg-8
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pktanonfrom testing2~git20160407.0.2bde4f2+dfsg-8
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/p/pktanon/16640926/log.gz

---
pktanon --- profile-based traffic anonymization
---
initializing PktAnon,  configuration = 
/usr/share/doc/pktanon/examples/profiles/profile.xml

unknown element: pktanon-config: 37
unknown element: anonymizations: 102
istream: opened file 
/tmp/autopkgtest-lxc.tgw0nfyu/downtmp/build.ybV/src/profiles/sample.pcap

ostream: opened output file ./out.pcap
initialized
Bus error
autopkgtest [23:49:21]: test run-example




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Closing this since armel and armhf builds have been disabled and RMs 
have been addressed, removing old builds for these archs. Closing this 
bug should now unlock testing migration again.


Thanks
Sascha


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1011763: marked as done (apt-listdifferences: FTBFS: patching file colordiff-git (read from /usr/bin/colordiff))

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 23:03:49 +
with message-id 
and subject line Bug#1011763: fixed in apt-listdifferences 1.20220605
has caused the Debian Bug report #1011763,
regarding apt-listdifferences: FTBFS: patching file colordiff-git (read from 
/usr/bin/colordiff)
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.)


-- 
1011763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-listdifferences
Version: 1.20190206
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3
>dh_update_autotools_config
>dh_autoreconf
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> gunzip < /usr/share/man/man1/colordiff.1.gz > colordiff-git.1
> patch /usr/bin/colordiff colordiff-git.patch -o colordiff-git
> File /usr/bin/colordiff is read-only; trying to patch anyway
> patching file colordiff-git (read from /usr/bin/colordiff)
> Hunk #1 FAILED at 66.
> 1 out of 1 hunk FAILED -- saving rejects to file colordiff-git.rej
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/apt-listdifferences_1.20190206_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: apt-listdifferences
Source-Version: 1.20220605
Done: Michael Gilbert 

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated apt-listdifferences 
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, 05 Jun 2022 21:37:55 +
Source: apt-listdifferences
Architecture: source
Version: 1.20220605
Distribution: unstable
Urgency: medium
Maintainer: Michael Gilbert 
Changed-By: Michael Gilbert 
Closes: 1011763
Changes:
 apt-listdifferences (1.20220605) unstable; urgency=medium
 .
   * Update to debhelper 13.
   * Update standards version.
   * Support colordiff 1.0.20 (closes: #1011763).
Checksums-Sha1:
 bf5964539f1cc9a1beabf9b89437e41c138d 2247 
apt-listdifferences_1.20220605.dsc
 dc3bd8b171cbe079baa600d09b6567608b9c1a1d 13040 
apt-listdifferences_1.20220605.tar.xz
 080a9bb925c6ff164f38167bf77e204e27b231bb 6835 
apt-listdifferences_1.20220605_source.buildinfo
Checksums-Sha256:
 2693d31c35ff46231cb3127e07ab9fd79c00bdae581f58c4eb62026be6e4ec86 2247 
apt-listdifferences_1.20220605.dsc
 19fabe0829046d3895cff6b5803518d4a093282af0b60ee16296684d9345a4c5 13040 
apt-listdifferences_1.20220605.tar.xz
 edc336a3bcf08a52d887cd161f26c2286164f939846996bee960c62e88c9459b 6835 
apt-listdifferences_1.20220605_source.buildinfo
Files:
 ac1e8e649d3f772f70de1fb4f3a8f406 2247 utils optional 
apt-listdifferences_1.20220605.dsc
 2481e2d82396f2f21548d64b7c158122 13040 utils optional 
apt-listdifferences_1.20220605.tar.xz
 9ee4e87268a5fd6479c912982d12dd8f 6835 utils optional 
apt-listdifferences_1.20220605_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmKdMUgACgkQmD40ZYkU
ayh5oR/9GfBGF4UyBWuM+aoMMoGEPoxFY7gdei9HJubn3iJUmxLUWGeLQpakKefi

Bug#1012275: closing 1012275

[Christoph Anton Mitterer]

On Sat, 2022-06-04 at 14:42 +0200, Vincent Bernat wrote:
> Unfortunately, Firefox is not buildable due to depending on a version
> of
> Cargo not available in unstable.

Shouldn't that be reopened then?

I wouldn't be surprised if quite a number of people use the non ESR FF,
probably also DDs/DMs.

And because of rust deps, it seems to happen more often now, that
security critical upgrades cannot enter unstable. (And yes I'm well
aware, that unstable has no official security support, but still).


Cheers,
Chris.

Bug#1011042: marked as done (libica FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 21:33:52 +
with message-id 
and subject line Bug#1011042: fixed in libica 3.9.0-1
has caused the Debian Bug report #1011042,
regarding libica FTBFS with OpenSSL 3.0
to be marked as done.

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

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


-- 
1011042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libica
Version: 3.2.0-4
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/fetch.php?pkg=libica=s390x=3.2.0-4%2Bb1=1652517971=0

...
libica_keygen_test.c: In function ‘main’:
libica_keygen_test.c:228:21: warning: implicit declaration of function 
‘FIPS_mode’ [-Wimplicit-function-declaration]
  228 | if (FIPS_mode())
  | ^
gcc -O0 -g -Wall -D_LINUX_S390_ -D_GNU_SOURCE -pthread  -o 
libica_aes_gcm_kma_test libica_aes_gcm_kma_test.c -L../.libs -I. -I../include 
-I../../include -lica -lcrypto
/usr/bin/ld: /tmp/ccXlAKmW.o: in function `main':
/<>/src/tests/libica_keygen_test.c:228: undefined reference to 
`FIPS_mode'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:483: libica_keygen_test] Error 1
--- End Message ---
--- Begin Message ---
Source: libica
Source-Version: 3.9.0-1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libica 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, 05 Jun 2022 20:58:13 +
Source: libica
Architecture: source
Version: 3.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1011042
Changes:
 libica (3.9.0-1) unstable; urgency=medium
 .
   * QA upload.
   * Import OpenSSL 3 compatible version from Ubuntu (Closes: #1011042).
   * Keep Homepage
   * Update to debhelper-compat level 12
Checksums-Sha1:
 5c6b0bd37f94da135bed60ca5f5b1a8aa3abbd00 1726 libica_3.9.0-1.dsc
 98f9f376a8db6f58deab1e08987653170159fe41 553295 libica_3.9.0.orig.tar.gz
 dd093be68e996997c9d055d7182676f0ed435815 7616 libica_3.9.0-1.debian.tar.xz
 571cb02b5d32d9c77ca8d10c5d89949cb58e8e46 5159 libica_3.9.0-1_source.buildinfo
Checksums-Sha256:
 802ac03f4530cbd122dd10bb79fa6ebd1db4ff2aad7aa326c715b33fe02cf112 1726 
libica_3.9.0-1.dsc
 4969f9d30dbd0e81fe328161dfcbb313d6aebd79224077eaf99779e9ad895d03 553295 
libica_3.9.0.orig.tar.gz
 f78f3a21ab1137687acaa2c426e7a17845a45b15d60217ab805872c986091992 7616 
libica_3.9.0-1.debian.tar.xz
 4a0b6c9303192c8e4d33ef5e56ce6e08c0ddd9eb4441c18f3c726bac5f771905 5159 
libica_3.9.0-1_source.buildinfo
Files:
 5c6bd809f9ff2e522e9716bcc20b4ecc 1726 libs optional libica_3.9.0-1.dsc
 0b0ff67ec705f3b85ec1a1251318444d 553295 libs optional libica_3.9.0.orig.tar.gz
 ab67e427a35845ccf6757f50a7a19390 7616 libs optional 
libica_3.9.0-1.debian.tar.xz
 7ac8af6c1fb8b882f37c30d20f7cfa08 5159 libs optional 
libica_3.9.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmKdHkQQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFGAtC/9vjMiAfh2sd7OgUF1/XzOvQaQqMMYzVmAA
mP4729MblvtAJae/Lu2Q8kxeWti8H7GoAeoyYI8ZMatRcFb8Jp2tIbQrVMgWi+C3
VYvonxdfm47fc6u7aB6XsHG95W7Ci26/yNlsq0WzoqNthcvimjHrUuHI6HvHbIGI
p/yUEQhS4QtWJDnH65oxf+5rfjYDdCvqBFMcS0Jv+rloLhjdQZ02EVdyOjR0SlCY
oXyvOLHmEkdd+PH+17s6U31bRGkURbF+jwaT51/RQyJ/TAZOLkECM2nxq2w8GPkg
7CM+9UF4q/7U+Orh85oIVpx9Si7eNzC0/xPY6LPrh8tAiHT+uwvvufj+kYe7l+HT
QlFRg6EWQwAH6Dc4l0+94zTwMmIwpd0zDBBTTzvmk21ObPL/Db1YWLoItFECb+CD
Dc+x/5jbNvB1VFHhNW67DaZssztvzO57SmwbDz5qp1CWqiPwXnDvsdxMG9Q1y4Jd
wiTc5lIPyVjtONnFQt+lwAL8CeeCPY8=
=16ZP
-END PGP SIGNATURE End Message ---

Bug#1010331: marked as done (src:vkd3d: fails to migrate to testing for too long: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 21:19:21 +
with message-id 
and subject line Bug#1010331: fixed in vkd3d 1.2-12
has caused the Debian Bug report #1010331,
regarding src:vkd3d: fails to migrate to testing for too long: FTBFS on s390x
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.)


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

Source: vkd3d
Version: 1.1-5
Severity: serious
Control: close -1 1.2-11
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:vkd3d has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on s390x while it built successfully there in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.2-12
Done: Michael Gilbert 

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated vkd3d 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, 05 Jun 2022 20:43:40 +
Source: vkd3d
Architecture: source
Version: 1.2-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 1010331
Changes:
 vkd3d (1.2-12) unstable; urgency=medium
 .
   * Update standards version.
   * Drop s390x from the supported architectures (closes: #1010331).
Checksums-Sha1:
 190b43ad644806bd5a01be6be0f1ded1f36d43a9 3978 vkd3d_1.2-12.dsc
 bdc1ba960b918af2609351e2c85532b43cd30d25 12052 vkd3d_1.2-12.debian.tar.xz
 d9d53f6985576094c00cb5bb63dca7e743ac1a38 7300 vkd3d_1.2-12_source.buildinfo
Checksums-Sha256:
 bceaeae51df7bd54ce816e78e1ab7e38832b2a88087d16167ec74dd7ce1fdb10 3978 
vkd3d_1.2-12.dsc
 7f4ac1616b4ece3e2d61e370556b99437af00859893e67417f29b902e3a14084 12052 
vkd3d_1.2-12.debian.tar.xz
 3a26575f374c0ca90aa2f75754b0bad4f2605d259e8daca85349bb9438a5bdd0 7300 
vkd3d_1.2-12_source.buildinfo
Files:
 9c17515743cc4d56efb9cc4e903d64be 3978 libs optional vkd3d_1.2-12.dsc
 4bb870d5a234da84d2410f6e4d7ff8db 12052 libs optional vkd3d_1.2-12.debian.tar.xz
 3cc119e756b35f1132b93e31bb4648c2 7300 libs optional 
vkd3d_1.2-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmKdGnMACgkQmD40ZYkU
aygVWB//WTzF1fT1UulAjS9Oy6ACF6SJw9wGNhtxXLUwLWAmBGCHEZjN9BA58kNP
X1tLGVqpWO7KXKq4Vl60yyHBgoVSM3CBfPsnT+Kx7NlYIMat/JaPFi9IDOEbkekK
rC0Fa/3ywI/EE7dlzs2MoS0kZnViLtl9X5yer7qP09h0pQUprwCVyHhbM8kwWiis
Tx4ehDGyz/lP7LmDbCxKtcOFYnhXD3JjvGodturOV+ZDiH8D/ub5C8VV5DA65tYS

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 1010331
Bug #1010331 {Done: Paul Gevers } [src:vkd3d] src:vkd3d: 
fails to migrate to testing for too long: FTBFS on s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vkd3d/1.2-11.
> notfixed 1010331 1.2-11
Bug #1010331 [src:vkd3d] src:vkd3d: fails to migrate to testing for too long: 
FTBFS on s390x
Ignoring request to alter fixed versions of bug #1010331 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1012373: dulwich breaks breezy autopkgtest: command loaded forbidden modules ['shutil', 'ssl', 'tempfile']

[Paul Gevers]

Source: dulwich, breezy
Control: found -1 dulwich/0.20.42-1
Control: found -1 breezy/3.2.2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
dulwichfrom testing0.20.42-1
breezy from testing3.2.2-2
all others from testingfrom testing

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

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

https://ci.debian.net/data/autopkgtest/testing/amd64/b/breezy/22354009/log.gz

FAIL: 
breezy.tests.test_import_tariff.TestImportTariffs.test_simple_local_git

--
testtools.testresult.real._StringException: log: {{{95.793  Setting env 
for bzr subprocess: {'PYTHONVERBOSE': '1', 'BRZ_PLUGIN_PATH': 
'-site:-user', 'BRZ_DISABLE_PLUGINS': None, 'BRZ_PLUGINS_AT': None

start_brz_subprocess-log-0: {{{
this is a debug log for diagnosing/reporting problems in brz
you can delete or truncate this file, or include sections in
bug reports to https://bugs.launchpad.net/brz/+filebug

Sat 2022-06-04 20:12:21 +
0.055  encoding stdout as sys.stdout encoding 'utf-8'
0.056  encoding stdout as sys.stdout encoding 'utf-8'
0.056  encoding stdout as sys.stdout encoding 'utf-8'
0.077  breezy version: 3.2.2
0.077  brz arguments: ['--no-plugins', 'st']
0.079  encoding stdout as sys.stdout encoding 'utf-8'
0.146  check paths: None
0.147  shelving not supported by tree, not displaying shelves.
0.147  return code 0
}}}

subprocess_stderr: {{{
import _frozen_importlib # frozen
import _imp # builtin
import '_thread' # 
import '_warnings' # 
import '_weakref' # 
import '_io' # 
import 'marshal' # 
import 'posix' # 
import '_frozen_importlib_external' # '_frozen_importlib.FrozenImporter'>

# installing zipimport hook
import 'time' # 
import 'zipimport' # 
# installed zipimport hook
# /usr/lib/python3.10/encodings/__pycache__/__init__.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/__init__.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/__init__.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/codecs.cpython-310.pyc matches 
/usr/lib/python3.10/codecs.py

# code object from '/usr/lib/python3.10/__pycache__/codecs.cpython-310.pyc'
import '_codecs' # 
import 'codecs' # <_frozen_importlib_external.SourceFileLoader object at 
0x7f556e9a3520>
# /usr/lib/python3.10/encodings/__pycache__/aliases.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/aliases.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/aliases.cpython-310.pyc'
import 'encodings.aliases' # 
<_frozen_importlib_external.SourceFileLoader object at 0x7f556e7fcb80>
import 'encodings' # <_frozen_importlib_external.SourceFileLoader object 
at 0x7f556e9a3190>
# /usr/lib/python3.10/encodings/__pycache__/utf_8.cpython-310.pyc 
matches /usr/lib/python3.10/encodings/utf_8.py
# code object from 
'/usr/lib/python3.10/encodings/__pycache__/utf_8.cpython-310.pyc'
import 'encodings.utf_8' # <_frozen_importlib_external.SourceFileLoader 
object at 0x7f556e9a3370>

import '_signal' # 
# /usr/lib/python3.10/__pycache__/io.cpython-310.pyc matches 
/usr/lib/python3.10/io.py

# code object from '/usr/lib/python3.10/__pycache__/io.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/abc.cpython-310.pyc matches 
/usr/lib/python3.10/abc.py

# code object from '/usr/lib/python3.10/__pycache__/abc.cpython-310.pyc'
import '_abc' # 
import 'abc' # <_frozen_importlib_external.SourceFileLoader object at 
0x7f556e7fce50>
import 'io' # <_frozen_importlib_external.SourceFileLoader object at 
0x7f556e7fcc40>
# /usr/lib/python3.10/__pycache__/site.cpython-310.pyc matches 
/usr/lib/python3.10/site.py

# code object from '/usr/lib/python3.10/__pycache__/site.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/os.cpython-310.pyc matches 
/usr/lib/python3.10/os.py

# code object from '/usr/lib/python3.10/__pycache__/os.cpython-310.pyc'
# /usr/lib/python3.10/__pycache__/stat.cpython-310.pyc matches 
/usr/lib/python3.10/stat.py

# code object from '/usr/lib/python3.10/__pycache__/stat.cpython-310.pyc'
import '_stat' # 
import 'stat' # <_frozen_importlib_external.SourceFileLoader object at 
0x7f556e7ff0d0>
# /usr/lib/python3.10/__pycache__/_collections_abc.cpython-310.pyc 

Processed: dulwich breaks breezy autopkgtest: command loaded forbidden modules ['shutil', 'ssl', 'tempfile']

[Debian Bug Tracking System]

Processing control commands:

> found -1 dulwich/0.20.42-1
Bug #1012373 [src:dulwich, src:breezy] dulwich breaks breezy autopkgtest: 
command loaded forbidden modules ['shutil', 'ssl', 'tempfile']
Marked as found in versions dulwich/0.20.42-1.
> found -1 breezy/3.2.2-2
Bug #1012373 [src:dulwich, src:breezy] dulwich breaks breezy autopkgtest: 
command loaded forbidden modules ['shutil', 'ssl', 'tempfile']
Marked as found in versions breezy/3.2.2-2.

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

Bug#942737: libapache2-mod-gnutls: mod_gnutls consumes 100% cpu

[Félix Arreola Rodríguez]

Finally managed to write a patch. This patch applies ok on mod-gnutls
0.9.0 and not sure if it will work for buster.

-- 
Atte. Félix Arreola
Firmado con GPG 0x1e249ee4
Author: Félix Arreola Rodríguez 
Date: Thu, 5 Jun 2022 10:42:46 -0500
Subject: Fix a loop caused by timeout if mod_reqtimeout is enabled
Bug-Debian: https://bugs.debian.org/942737

When mod_reqtimeout is enabled, when mod_gnutls tries to read from
the previous apr_bucket, it returns a timeout. Mod_gnutls handles
incorrectly this timeout as a EAGAIN, causing to forever loop
and consumes 100% CPU on the current apache process.
---
diff --git a/src/gnutls_io.c b/src/gnutls_io.c
===
--- a/src/gnutls_io.c
+++ b/src/gnutls_io.c
@@ -269,6 +269,17 @@ static apr_status_t gnutls_io_input_read
 ap_log_cerror(APLOG_MARK, APLOG_TRACE2, ctxt->input_rc, ctxt->c,
   "%s: looping recv after '%s' (%d)",
   __func__, gnutls_strerror(rc), rc);
+if (APR_STATUS_IS_TIMEUP (ctxt->input_rc)) {
+	/* Timeout by mod_reqtimeout, bye bye */
+	ap_log_cerror(APLOG_MARK,
+APLOG_INFO,
+ctxt->input_rc,
+ctxt->c,
+"GnuTLS: Timeout reading data. (%d) '%s'",
+rc,
+gnutls_strerror(rc));
+break;
+}
 /* For a blocking read, loop and try again
  * immediately. Otherwise just notify the caller. */
 if (ctxt->input_block != APR_NONBLOCK_READ)


pgp29x61ProPo.pgp
Description: Firma digital OpenPGP

Bug#1012279: php-horde-turba: CVE-2022-30287

[Mike Gabriel]

Hi Salvatore,

On  So 05 Jun 2022 14:35:03 CEST, Salvatore Bonaccorso wrote:


Hi,

On Sun, Jun 05, 2022 at 12:02:54PM +, Mike Gabriel wrote:

Hi Juri,

On  Sa 04 Jun 2022 00:13:11 CEST, debian wrote:

> Hello,
>
> here is draft for MR:
> https://salsa.debian.org/horde-team/php-horde-turba/-/merge_requests/1
> I would look after it next time on sunday evening.
>
> @Mike: Can you please review it?


it looks that the force pushed commit two days ago adjusted two
further create() -> createTrusted() stances in lib/Application.php,
can you double check?


I actually did double check already, applied 9f242132 and saw that it  
did not apply properly (and thus reverted). See Git history at [1]. It  
seems that the backup/restore API calls (where these two spots of  
create -> createTrusted had been added) were not part of the 4.2.25  
upstream release of turba.



https://github.com/horde/turba/commit/9f2521328aa7d0dbd905591eca138c8e7580d673
(which is not yet merged, but compare to the used
https://github.com/horde/turba/commit/784da95e0190321b08ceeb27e2cb6c7505f2057c).

p.s.: the upload did contain a non valid bug closer, which in case the
above is correct cha be simply closed in a 4.2.25-7 upload.


If you agree, we have to close the bug manually as Juri's approach  
already contained the right patch.


Mike

[1] https://salsa.debian.org/horde-team/php-horde-turba/-/commits/debian-sid

--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpHjZpZu5AsP.pgp
Description: Digitale PGP-Signatur

Bug#1006581: marked as done (xmltooling: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 19:05:05 +
with message-id 
and subject line Bug#1006581: fixed in xmltooling 3.2.1-2
has caused the Debian Bug report #1006581,
regarding xmltooling: FTBFS with OpenSSL 3.0
to be marked as done.

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

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


-- 
1006581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmltooling
Version: 3.2.1-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Your package is failing to build using OpenSSL 3.0 with the
following error:

| make[5]: Entering directory '/<>/xmltoolingtest'
| ../build-aux/test-driver: line 112: 1662259 Segmentation fault  "$@" >> 
"$log_file" 2>&1
| FAIL: xmltoolingtest
| =
|xmltooling 3.2.1: xmltoolingtest/test-suite.log
| =
| 
| # TOTAL: 1
| # PASS:  0
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| .. contents:: :depth: 2
| 
| FAIL: xmltoolingtest
| 
| 
| Running cxxtest tests (125 tests)..1644903586 WARN XMLTooling.XMLHelper : 
DEPRECATED: attribute "ignoreCase" encountered in configuration. Use 
"caseSensitive".
| 1644903586 WARN XMLTooling.XMLHelper : DEPRECATED: attribute "ignoreCase" 
encountered in configuration. Use "caseSensitive".
| 1644903586 WARN XMLTooling.XMLHelper : DEPRECATED: attribute "ignoreCase" 
encountered in configuration. Use "caseSensitive".
| 1644903586 WARN XMLTooling.XMLHelper : Attribute "ignoreCase" and 
"caseSensitive" should not be used in the same element.
| .1644903586 WARN DirectoryWalkerTest : Unable to open directory (invalid)
| ...1644903586 ERROR XMLTooling.ParserPool : fatal error on line 2, 
column 10, message: invalid document structure
| .1644903586 ERROR XMLTooling.XMLObject : no default builder installed, 
found unknown child element (test:UnknownElement)
| ..FAIL xmltoolingtest (exit status: 139)
| 
| 
| Testsuite summary for xmltooling 3.2.1
| 
| # TOTAL: 1
| # PASS:  0
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| See xmltoolingtest/test-suite.log
| Please report to https://shibboleth.atlassian.net/jira
| 
| make[5]: *** [Makefile:1172: test-suite.log] Error 1

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html

Sebastian
--- End Message ---
--- Begin Message ---
Source: xmltooling
Source-Version: 3.2.1-2
Done: Ferenc Wágner 

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated xmltooling 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, 05 Jun 2022 20:43:32 +0200
Source: xmltooling
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Closes: 1006581
Changes:
 xmltooling (3.2.1-2) unstable; urgency=medium
 .
   * [357c2a5] xmltoolingtest: enable legacy PKCS#12 algorithms.
 OpenSSL 3 requires this for decoding data.pfx. (Closes: #1006581)
   * [a6c620f] Update Standards-Version to 4.6.1 (no changes required)
   * [8831817] Switch to Debhelper compatibility level 13
   * [bb23e99] Replace override_dh_{install,missing} with debian/not-installed
   * [77dfd2c] Suppress GCC deprecation warnings, they probably won't be heeded
Checksums-Sha1:
 a81f78389ecdaff3ed5234f6d697dcdd2f04e91b 2770 xmltooling_3.2.1-2.dsc
 d31178616eae0ead037df51378a38637f20da880 21096 xmltooling_3.2.1-2.debian.tar.xz
 f44d3a2bfa02368fa555cc629b63cf8e56d5d20c 10134 
xmltooling_3.2.1-2_amd64.buildinfo

Processed (with 1 error): unarchiving 972084, forcibly merging 972084 1012352, archiving 972084

[Debian Bug Tracking System]

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

> unarchive 972084
> forcemerge 972084 1012352
Bug #972084 {Done: Stephen Kitt } [gweled] gweled: Display is 
glitching
Bug #1012352 {Done: Stephen Kitt } [gweled] 
Glitches/artifacts in the window of Gweled
Severity set to 'grave' from 'normal'
Marked as fixed in versions gweled/0.9.1-8; no longer marked as fixed in 
versions 0.9.1-8.
Added tag(s) bullseye, sid, and bookworm.
Merged 972084 1012352
> archive 972084
Bug #972084 {Done: Stephen Kitt } [gweled] gweled: Display is 
glitching
Bug #1012352 {Done: Stephen Kitt } [gweled] 
Glitches/artifacts in the window of Gweled
archived 972084 to archive/84 (from 972084)
archived 1012352 to archive/52 (from 972084)
> thanks
Stopping processing here.

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

Bug#981224: Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Andrej Shadura]

Hi,

On Sun, 5 Jun 2022, at 12:58, Pirate Praveen wrote:
> On ബു, ജൂൺ 1 2022 at 07:32:00 വൈകു +05:30:00 
> +05:30:00, Pirate Praveen  wrote:
>> Looks like upstreams moved already
>> https://github.com/rails/sprockets/pull/713
>> https://github.com/rails/rails/blob/main/Gemfile#L33
>
> $ reverse-depends -b ruby-uglifier
> Reverse-Build-Depends
> * open-build-service
>
> $ reverse-depends ruby-uglifier
> Reverse-Depends
> * diaspora
> * gitlab
> * obs-api

> Last unstable upload of open-build-service/obs-api is 2020-04-13 and 
> already has two unfixed rc bugs and a request for help 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984462

We (Collabora) stopped using OBS from Debian packages and switched to our own 
Docker images completely, which use Rubygems.org instead. Since we were 
effectively the maintainers of the Debian packages, and nobody else volunteered 
to maintain OBS in Debian, I’m going to remove most of it except the worker 
code, which is really tiny and needs virtually no maintenance. (There’s also a 
related package, obs-build, unaffected by this.)

I’m preparing an upload to the OBS package to implement this.

[0]: https://gitlab.collabora.com/obs/open-build-service

-- 
Cheers,
  Andrej

Processed (with 2 errors): unarchiving 972084, merging 972084 1012352, archiving 972084

[Debian Bug Tracking System]

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

> unarchive 972084
Bug #972084 {Done: Stephen Kitt } [gweled] gweled: Display is 
glitching
Unarchived Bug 972084
> merge 972084 1012352
Bug #972084 {Done: Stephen Kitt } [gweled] gweled: Display is 
glitching
Unable to merge bugs because:
severity of #1012352 is 'normal' not 'grave'
Failed to merge 972084: Did not alter merged bugs.

> archive 972084
> thanks
Stopping processing here.

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

Bug#1012361: New upstream version 4.2.2

[Guido Günther]

Package: electrum
Version: 4.0.9-1
Severity: critical

Hi,
there's a new upstream version 4.2.2 available:

  https://electrum.org/#download

Would be great to have that in Debian.
Cheers,
 -- Guido

Processed (with 2 errors): Re: Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

[Debian Bug Tracking System]

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

> severity 1011914 minor
Bug #1011914 [src:lsof] lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1
Severity set to 'minor' from 'serious'
> tags 1011914 = wontfix
Bug #1011914 [src:lsof] lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1
Added tag(s) wontfix; removed tag(s) bookworm, ftbfs, and sid.
> retitle 1011914 lsof: FTBFS during unit tests when hostname cannot be
Bug #1011914 [src:lsof] lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1
Changed Bug title to 'lsof: FTBFS during unit tests when hostname cannot be' 
from 'lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1'.
> resolved
Unknown command or malformed arguments to command.
> forward 1011914 https://github.com/lsof-org/lsof/issues/61
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

[Andres Salomon]

severity 1011914 minor
tags 1011914 = wontfix
retitle 1011914 lsof: FTBFS during unit tests when hostname cannot be 
resolved

forward 1011914 https://github.com/lsof-org/lsof/issues/61
thanks

On Sun, Jun 5, 2022 at 11:13, Lucas Nussbaum  wrote:

Hi Andres,

[...]

This is not related to the build attempting network access (I don't
check against this, so even if it did require network access, the 
build

would work just fine).

What happens in AWS is:
- the hostname is ip-10-84-234-245 (for example)
- /etc/hosts contains (on the host)
   127.0.1.1 ip-10-84-234-245.eu-central-1.compute.internal 
ip-10-84-234-245
- schroot does not copy the host's /etc/hosts to the chroot, because 
the
  chroot is configured (using sbuild-create-chroot) to use the 
'sbuild'

  schroot profile, which does not include 'hosts' in
  /etc/schroot/sbuild/nssdatabases

As a result, if the hostname cannot be resolved using DNS but only 
using

NSS (/etc/hosts), then it cannot be resolved inside the chroot.

I fixed my chroot setup script so that 'hosts' get copied from host, 
and

confirmed that lsof now builds fine.

I let you decide whether you want to close this bug, or turn it into a
severity:minor "FTBFS when hostname cannot be resolved".

I am not aware of other packages failing to build in the AWS 
environment
because of this issue, so it might be worth keeping track of with a 
bug.


Luca



Thanks, I'll keep it open. We have an upstream bug[0] discussing what to
do about the unit tests, which may result in the tests not being run at
all. If that ends up being the case, I will of course close this.

[0] https://github.com/lsof-org/lsof/issues/61#issuecomment-1120611271

Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Hi,

On Sun, Jun 05, 2022 at 12:02:54PM +, Mike Gabriel wrote:
> Hi Juri,
> 
> On  Sa 04 Jun 2022 00:13:11 CEST, debian wrote:
> 
> > Hello,
> > 
> > here is draft for MR:
> > https://salsa.debian.org/horde-team/php-horde-turba/-/merge_requests/1
> > I would look after it next time on sunday evening.
> > 
> > @Mike: Can you please review it?

it looks that the force pushed commit two days ago adjusted two
further create() -> createTrusted() stances in lib/Application.php,
can you double check?

https://github.com/horde/turba/commit/9f2521328aa7d0dbd905591eca138c8e7580d673
(which is not yet merged, but compare to the used
https://github.com/horde/turba/commit/784da95e0190321b08ceeb27e2cb6c7505f2057c).

p.s.: the upload did contain a non valid bug closer, which in case the
above is correct cha be simply closed in a 4.2.25-7 upload.

Regards,
Salvtore

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

[Reinhard Tartler]

Just a hunch, is it possible that your build environment did not have the
package 'ca-certificates' present whereas mine does?

I wonder whether I need to add 'ca-certificates' to "Build-Depends". What
do you think?

On Sun, Jun 5, 2022 at 7:10 AM Reinhard Tartler  wrote:

> Please find the buildlog of my attempt attached to this email
>
> As far as I can tell, the tests are executing in the same way as in your
> logs, but I may be missing something.
>


-- 
regards,
Reinhard

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

[Reinhard Tartler]

Please find the buildlog of my attempt attached to this email

As far as I can tell, the tests are executing in the same way as in your
logs, but I may be missing something.


golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-1_amd64-2022-06-05T02:02:05Z.build
Description: Binary data

Bug#1009369: marked as done (frescobaldi: fails to start)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 11:03:58 +
with message-id 
and subject line Bug#1009369: fixed in frescobaldi 3.2+ds1-1
has caused the Debian Bug report #1009369,
regarding frescobaldi: fails to start
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.)


-- 
1009369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: frescobaldi
Version: 3.1.3+ds1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: f2c...@gmail.com

Dear Maintainer,

Frescobaldi fails to start since the last dist-upgrade for sid (today) with :

~$ frescobaldi
Traceback (most recent call last):
  File "/usr/share/frescobaldi/frescobaldi_app/panel.py", line 64, in sizeHint
self.widget()
  File "/usr/share/frescobaldi/frescobaldi_app/panel.py", line 71, in widget
w = self.createWidget()
  File "/usr/share/frescobaldi/frescobaldi_app/docbrowser/__init__.py", line
56, in createWidget
return browser.Browser(self)
  File "/usr/share/frescobaldi/frescobaldi_app/docbrowser/browser.py", line 86,
in __init__
self.readSettings()
  File "/usr/share/frescobaldi/frescobaldi_app/docbrowser/browser.py", line
102, in readSettings
ws.setFontSize(QWebEngineSettings.DefaultFixedFontSize, fixed.pointSizeF()
* 96 / 72)
TypeError: setFontSize(self, QWebEngineSettings.FontSize, int): argument 2 has
unexpected type 'float'
Abandon

Beside ;
~$ frescobaldi -V
Frescobaldi: 3.1.3
Extension API: 0.9.0
Python: 3.10.4
python-ly: 0.9.6
Qt: 5.15.2
PyQt: 5.15.6
sip: 6.5.1
poppler: 20.9.0
python-poppler-qt: 0.75.0
OS: Linux-5.16.0-6-amd64-x86_64-with-glibc2.33


Thanks in advance,
Frédéric Moinard


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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages frescobaldi depends on:
ii  python33.10.4-1
ii  python3-ly 0.9.6-2
ii  python3-poppler-qt50.75.0-3+b1
ii  python3-pygame 2.1.2+dfsg-3
ii  python3-pyqt5  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtsvg5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebengine  5.15.5-1+b1
ii  python3-pyqt5.qtwebkit 5.15.6+dfsg-1+b2
ii  tango-icon-theme   0.8.90-10

Versions of packages frescobaldi recommends:
ii  lilypond  2.22.2-1

Versions of packages frescobaldi suggests:
ii  hyphen-en-us [hyphen-hyphenation-patterns]  2.8.8-7
ii  hyphen-fr [hyphen-hyphenation-patterns] 1:7.2.0-2
ii  lilypond-doc2.22.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: frescobaldi
Source-Version: 3.2+ds1-1
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated frescobaldi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jun 2022 04:33:35 -0600
Source: frescobaldi
Architecture: source
Version: 3.2+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Anthony Fok 
Closes: 1009369
Changes:
 frescobaldi (3.2+ds1-1) unstable; urgency=medium
 .
   * New upstream version 3.2+ds1
 Thanks to Frédéric Moinard for the bug report about "frescobaldi:
 fails to start" due to Python 3.10 changes (Closes: #1009369)
   * Reorder fields in debian/control and debian/copyright
   * Bump Standards-Version to 4.6.1 (no change)
   * Refresh debian/patches/private-module-directory.patch
   * Add dependency on python3-qpageview.
 Thanks to Jean Baptiste Favre for packaging it! (See #1012051)
   * Add "Recommends: fluidsynth" in 

Bug#1012345: marked as done (librust-bytecount-dev: depends on missing package librust-packed-simd-2-0.3+default-dev)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 10:49:08 +
with message-id 
and subject line Bug#1012345: fixed in rust-bytecount 0.6.3-2
has caused the Debian Bug report #1012345,
regarding librust-bytecount-dev: depends on missing package 
librust-packed-simd-2-0.3+default-dev
to be marked as done.

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

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


-- 
1012345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-bytecount-dev
Version: 0.6.3-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKcUsEACgkQLHwxRsGg
ASHxeA//VWukx86Dd5gchqYzYYuWwP2Z1nW/qQbJFOu5uXtmmQilwqkG7USbvKcx
5VeC5uq+lQvXVeWZEI1Mmug+iS23VDqel74CtJ77CFOfuhcce4JvV5QlKMssFv7A
2Xj7vguLei1yYMFrNVLZAka861tOY3xQJ3Y1OYSS2ZYlS7JzBI+dLel2YHaHKzMm
gP0X5eRfdx+w12FRSZMZqSC7KtUWsjWcEBGpiP0pOruNNrI5x+2pHYHcK8szEitW
xiv6BQcXbvIzrPc3XHB017CSq96fdb4WWrvciWAn10w1eJsZNDmj57g5TGj4DWAf
aQETcRzFXml4SKsn1U5spgX1v5khiLe6Q9DQiIjKhwIdzCRCQKSwVrMGee4P6nhO
tgT4TNguwEvUjpHA89qiShjl3K/gsVlPRELAHBmNn32nLUAN9Utx+uASjuqrKI0N
jWxHENFVBFQYJa4lX4eniKx+jfEG1EwEs8AO0JWn0ewwy2IfwftRbgeSN25r9Pcd
6gGIYDzwJ6SnP/YqNOQtUJSPxS/tK+ehWfENks6xIcSqfuamYXoJL3HKFHaQP+6u
UYPig49JglcoO1fMGr5F4Pc3Z2PiGe5tvnSN5aaZdmgOyr1QqpWEwxUc75pn0k3u
LkGZz7EcTZJHXhiQYyYBQe3w3BWfenvSAMEIGY60OTzAqbPQ4E4=
=iX3c
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-bytecount
Source-Version: 0.6.3-2
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-bytecount 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Jun 2022 10:25:37 +
Source: rust-bytecount
Architecture: source
Version: 0.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1012345
Changes:
 rust-bytecount (0.6.3-2) unstable; urgency=medium
 .
   * Package bytecount 0.6.3 from crates.io using debcargo 2.5.0
   * Drop packed-simd feature (Closes: 1012345)
   * Drop dev-depends on criteion and disable bench that uses it so the rest
 of the testsuite can run.
Checksums-Sha1:
 4e48e32bfcb225f41f8b38f541de91c58791f149 2216 rust-bytecount_0.6.3-2.dsc
 869c80aa51e77516b743d04ca53b45163ff9cea4 3388 
rust-bytecount_0.6.3-2.debian.tar.xz
 f1851f0a34a79c55cb8533c8bb88a5f64763e56d 6836 
rust-bytecount_0.6.3-2_source.buildinfo
Checksums-Sha256:
 afbefc17df935dae74920c6a15fa0b3aab26fdad17f0d8edee6fec804ccb9ff0 2216 
rust-bytecount_0.6.3-2.dsc
 c74d5fe0a9b0747e20221b3bd5f8e3842037e9f9bb1bffb23b1c2c16e604b790 3388 
rust-bytecount_0.6.3-2.debian.tar.xz
 405457caec9800bd8ceffd3a38981b6537387be50c5d8bac96153c55d915 6836 
rust-bytecount_0.6.3-2_source.buildinfo
Files:
 daaac7b9099c4583b9debf91d12e305d 2216 rust optional rust-bytecount_0.6.3-2.dsc
 00f110fbfd5ad66f72d442dc94033e17 3388 rust optional 
rust-bytecount_0.6.3-2.debian.tar.xz
 7ca6c2c4b7908bac7fb06738e8889b22 6836 rust optional 
rust-bytecount_0.6.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmKchL0UHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtcTw/9HmlpgPFD7LiZDBhomgSsxgxnqZZH
3Ari9EnrNaZx3f/u1N0+01G7BwaKYto9qDNle8vVm9aGlPDJ1WF1BzXd3jKJyc47
ZyzHVfY/j6V+LQMW2bGQQwiR/F4X6MfjC6iG/YqvWMzOBE+1XwtRcZRZQtGaqs/9
M+dFdF99yxBbeMPEHQPTP10r9BYc4qTRKR/sfguVg5dcj9HilN+e8qckoxqrNjkk
Sagr38s/5Mw5jQaGUL5aIYlgcneX3m5uPqYUZl40LKqSKIt9jeWHRUzXELY9tUXL
IniJ3H2JKiEl6NIsSHYJezYaHxUPloQJHW4NreMIyWiIJHpmz9QUdEjpCCvGn8iA
Z7Z+f6JNyTpKFA+M9+uw1yM18zRStKCVltaCeAaVmDe/Lq2utfbbMbfrYPi49z0q
n+B6gpo96+WikxdzQGDjqSxsgeeM/79+iw7jFb47lv0obnOwk93DCVZGIAs7OK0X
MuoBk8KA3iZes0z012Fb/yLJWZcUIxfPmSltXP+p0yfF6SpLB7dDe6F56HBOTeOk
taYG2Wvxw7CfF7W7DvBxmcdOzxAsdF+ELpVRHfQgEsca9kW+r6lj4KSqljqFVBML
z07K7CMqUF0cDauJpQoTRyBoWM/wu/mkNI3oJDCBfx50+ogtOBEzkqXEAOrJXOT/
ph045LgOqeABZdY=
=IAn0
-END 

Processed: Re: [Pkg-rust-maintainers] Bug#1012221: rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.

[Debian Bug Tracking System]

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

> reopen 1012221
Bug #1012221 {Done: Sylvestre Ledru } 
[rust-stdweb-internal-macros] rust-stdweb-internal-macros (build-)depends on 
old version of rust-sha1.
Bug reopened
Ignoring request to alter fixed versions of bug #1012221 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1012221: [Pkg-rust-maintainers] Bug#1012221: rust-stdweb-internal-macros (build-)depends on old version of rust-sha1.

[Peter Michael Green]

reopen 1012221
thanks

On 02/06/2022 13:29, Sylvestre Ledru wrote:
4. Remove the stdweb features in instant and parking-lot and allow 
stdweb to be removed from testing.


I think I implemented this solution.


Thanks,

That solves the issue for instant, parking-lot and their reverse 
dependencies, but stdweb-internal-macros remains rc buggy, hence this 
bug should stay open until it is removed.




I opened #1012261 for the removal of the packages.
It appears the ftpmasters responded to that bug by only removing stdweb, 
not the other stdweb related packages.

Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

[Lucas Nussbaum]

Hi Andres,

On 04/06/22 at 15:13 -0400, Andres Salomon wrote:
> Thanks for the report. I can't reproduce this, though.
> 
> The code in question is this:
> 
> 
> /*
> * Get the host name and its IP address.  Convert the IP address to dotted
> * ASCII form.
> */
>if (gethostname(hnm, sizeof(hnm) - 1)) {
>cem = "ERROR!!!  can't get this host's name";
>goto print_errno;
>}
>hnm[sizeof(hnm) - 1] = '\0';
>if (!(hp = gethostbyname(hnm))) {
>(void) snprintf(buf, bufl - 1, "ERROR!!!  can't get IP address for
> %s",
>hnm);
>buf[bufl - 1] = '\0';
> 
> 
> It seems like gethostbyname() is failing, which presumably is a
> misconfiguration on the part of the build host (probably something in
> /etc/hosts?). I'm pretty sure local hostname forward and reverse lookups
> don't violate policy 4.9 "required targets must not attempt network access,
> except, via the loopback interface", but correct me if I'm wrong.
> 
> I've attached the build log and the diff between our build logs, just in
> case that's helpful (although you're using sbuild and I'm not, so the diff
> isn't very readable).

This is not related to the build attempting network access (I don't
check against this, so even if it did require network access, the build
would work just fine).

What happens in AWS is:
- the hostname is ip-10-84-234-245 (for example)
- /etc/hosts contains (on the host)
   127.0.1.1 ip-10-84-234-245.eu-central-1.compute.internal ip-10-84-234-245
- schroot does not copy the host's /etc/hosts to the chroot, because the
  chroot is configured (using sbuild-create-chroot) to use the 'sbuild'
  schroot profile, which does not include 'hosts' in
  /etc/schroot/sbuild/nssdatabases

As a result, if the hostname cannot be resolved using DNS but only using
NSS (/etc/hosts), then it cannot be resolved inside the chroot.

I fixed my chroot setup script so that 'hosts' get copied from host, and
confirmed that lsof now builds fine.

I let you decide whether you want to close this bug, or turn it into a
severity:minor "FTBFS when hostname cannot be resolved".

I am not aware of other packages failing to build in the AWS environment
because of this issue, so it might be worth keeping track of with a bug.

Lucas

Bug#1009528: marked as done (node-temporary: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 09:05:47 +
with message-id 
and subject line Bug#1010006: Removed package(s) from unstable
has caused the Debian Bug report #1009528,
regarding node-temporary: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 2
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.)


-- 
1009528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-temporary
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/temporary
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -R spec --timeout 1 test/
> 
> 
>   Base
> rename
>   undefined should rename the directory
> renameSync
>   undefined should rename the directory
> prepareArgs
>   undefined should convert object to array and append path as first 
> element
> 
>   detector
> tmp
>   undefined should return the tmp dir of the system
>   undefined should normalize windows paths correctly
> 
>   Tempdir
> undefined should create file
> undefined should use the directory name as the path when generator option 
> equals false
> undefined should use the custom generator if supplied
> rmdir
>   undefined should remove the directory
> rmdirSync
>   undefined should remove the directory
> 
>   Tempfile
> undefined should create file
> readFile
>   undefined should call fs.readfile
> readFileSync
>   undefined should call fs.readfileSync
> writeFile
>   1) should call fs.readfile
> writeFileSync
>   2) should call fs.writeFileSync
> open
>   undefined should call fs.open
> openSync
>   undefined should call fs.openSync
> close
>   undefined should call fs.close
> closeSync
>   undefined should call fs.closeSync
> unlink
>   undefined should call fs.unlink
> unlinkSync
>   undefined should call fs.readfileSync
> 
>   generator
> name
>   undefined should unique generate name
> build
>   undefined should build full names
> 
> 
>   21 passing (46ms)
>   2 failing
> 
>   1) Tempfile
>writeFile
>  should call fs.readfile:
>  TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type 
> string or an instance of Buffer, TypedArray, or DataView. Received an 
> instance of Object
>   at Object.writeFile (fs.js:1491:5)
>   at Function.invoke 
> (/usr/share/nodejs/sinon/lib/sinon/proxy-invoke.js:50:47)
>   at Object.writeFile (/usr/share/nodejs/sinon/lib/sinon/proxy.js:285:26)
>   at File.writeFile (lib/file.js:58:16)
>   at Context. (test/file.test.js:49:11)
>   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (internal/timers.js:464:21)
> 
>   2) Tempfile
>writeFileSync
>  should call fs.writeFileSync:
>  TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type 
> string or an instance of Buffer, TypedArray, or DataView. Received undefined
>   at Object.writeFileSync (fs.js:1521:5)
>   at Function.invoke 
> (/usr/share/nodejs/sinon/lib/sinon/proxy-invoke.js:50:47)
>   at Object.writeFileSync 
> (/usr/share/nodejs/sinon/lib/sinon/proxy.js:280:26)
>   at File.writeFileSync (lib/file.js:65:27)
>   at Context. (test/file.test.js:59:11)
>   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at 

Bug#1009536: marked as done (node-connect-timeout: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 09:05:05 +
with message-id 
and subject line Bug#1010009: Removed package(s) from unstable
has caused the Debian Bug report #1009536,
regarding node-connect-timeout: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 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.)


-- 
1009536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-connect-timeout
Version: 1.9.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../debian/tests/test_modules/supertest node_modules/supertest
>   ln -s ../. node_modules/connect-timeout
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_PATH=debian/tests/test_modules mocha --exit --reporter spec --bail 
> --check-leaks test/
> 
> 
>   timeout()
> undefined should have a default timeout (5045ms)
> undefined should accept millisecond timeout (130ms)
> undefined should accept string timeout (49ms)
> when below the timeout
>   undefined should do nothing
> when above the timeout
>   with no response made
> undefined should respond with 503 Request timeout (103ms)
> 1) should pass the error to next()
> 
> 
>   5 passing (5s)
>   1 failing
> 
>   1) timeout()
>when above the timeout
>  with no response made
>should pass the error to next():
>  Uncaught Error [ERR_STREAM_WRITE_AFTER_END]: write after end
>   at new NodeError (internal/errors.js:322:7)
>   at writeAfterEnd (_http_outgoing.js:694:15)
>   at ServerResponse.end (_http_outgoing.js:815:7)
>   at /<>/test/test.js:46:15
>   at Timeout._onTimeout (test/test.js:205:11)
>   at listOnTimeout (internal/timers.js:557:17)
>   at processTimers (internal/timers.js:500:7)
> 
> 
> 
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-connect-timeout_1.9.0-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.9.0-5+rm

Dear submitter,

as the package node-connect-timeout 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/1010009

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1010513: marked as done (node-lolex: FTBFS, deprecated, replaced by @sinonjs/fake-timers)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 09:01:28 +
with message-id 
and subject line Bug#1010512: Removed package(s) from unstable
has caused the Debian Bug report #1010513,
regarding node-lolex: FTBFS, deprecated, replaced by @sinonjs/fake-timers
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.)


-- 
1010513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-lolex
Version: 5.1.2+ds-3
Severity: serious
Justification: FTBFS

* node-lolex test fails with nodejs 16
* lolex has been renamed @sinonsj/fake-timers, included in node-sinon
* no more (build) reverse dependencies

I just ask ROM-RM
--- End Message ---
--- Begin Message ---
Version: 5.1.2+ds-3+rm

Dear submitter,

as the package node-lolex 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/1010512

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1010505: marked as done (golang-gopkg-libgit2-git2go.v31 autopkgtest failure with libgit2 1.3)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 09:00:22 +
with message-id 
and subject line Bug#1010960: Removed package(s) from unstable
has caused the Debian Bug report #1010505,
regarding golang-gopkg-libgit2-git2go.v31 autopkgtest failure with libgit2 1.3
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.)


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

Package: golang-gopkg-libgit2-git2go.v31
Version: 31.4.3-4
Severity: serious

The autopkgtest for golang-gopkg-libgit2-git2go.v31 is failing with 
libgit2 1.3

and hence blocking the transition.

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-gopkg-libgit2-git2go.v31/21329197/log.gz




github.com/libgit2/git2go/v31
# github.com/libgit2/git2go/v31
src/github.com/libgit2/git2go/v31/git_system_dynamic.go:11:3: error: #error "Invalid 
libgit2 version; this git2go supports libgit2 between v1.1.0 and v1.1.0"
11 | # error "Invalid libgit2 version; this git2go supports libgit2 between 
v1.1.0 and v1.1.0"
   |   ^





--- End Message ---
--- Begin Message ---
Version: 31.4.3-4+rm

Dear submitter,

as the package golang-gopkg-libgit2-git2go.v31 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/1010960

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#993355: marked as done (haskell-hgettext: autopkgtest regressed in August 2020)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:59:37 +
with message-id 
and subject line Bug#1011208: Removed package(s) from unstable
has caused the Debian Bug report #993355,
regarding haskell-hgettext: autopkgtest regressed in August 2020
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.)


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

Hi Maintainer

Some time in August 2020, haskell-hgettext's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/h/haskell-hgettext/testing/amd64/


autopkgtest [20:40:01]: test cabal-install-compatibility:
[---
Warning: No remote package servers have been specified. Usually you would have
one specified in the config file.
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: example-0.1.0 (user goal)
[__1] next goal: example:setup.Cabal (dependency of example)
[__1] rejecting: example:setup.Cabal-3.0.1.0/installed-3.0... (conflict:
example => example:setup.Cabal>=1.8 && <1.25)
[__1] fail (backjumping, conflict set: example, example:setup.Cabal)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: example, example:setup.Cabal

autopkgtest [20:40:03]: test cabal-install-compatibility:
---]
autopkgtest [20:40:03]: test cabal-install-compatibility:  - - - - - -
- - - - results - - - - - - - - - -
cabal-install-compatibility FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Version: 0.1.31.0-8+rm

Dear submitter,

as the package haskell-hgettext 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/1011208

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#964826: marked as done (haskell-chell-quickcheck2: BD-Uninstallable)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:58:42 +
with message-id 
and subject line Bug#1011211: Removed package(s) from unstable
has caused the Debian Bug report #964826,
regarding haskell-chell-quickcheck2: BD-Uninstallable
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.)


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

haskell-chell-quickcheck2 build-depends on missing:
- libghc-quickcheck2-dev:amd64 (< 2.13)

libghc-quickcheck2-dev is at version 2.13.2-1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.2.5.2-1+rm

Dear submitter,

as the package haskell-chell-quickcheck2 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/1011211

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#964825: marked as done (haskell-chell: BD-Uninstallable)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:59:10 +
with message-id 
and subject line Bug#1011214: Removed package(s) from unstable
has caused the Debian Bug report #964825,
regarding haskell-chell: BD-Uninstallable
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.)


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

haskell-chell build-depends on missing:
- libghc-ansi-terminal-dev:amd64 (< 0.9)

libghc-ansi-terminal-dev is at version 0.10.3-1 now

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package haskell-chell 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/1011214

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#963748: marked as done (haskell-gitlib: FTBFS with ghc-8.8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:57:51 +
with message-id 
and subject line Bug#1011213: Removed package(s) from unstable
has caused the Debian Bug report #963748,
regarding haskell-gitlib: FTBFS with ghc-8.8
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.)


-- 
963748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gitlib
Version: 3.1.2-3
Severity: grave
Justification: renders package unusable

This package FTBFS with ghc-8.8.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 3.1.2-3+rm

Dear submitter,

as the package haskell-gitlib 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/1011213

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#963072: marked as done (haskell-easytest: Does not build with hedgehog 1.x)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:58:17 +
with message-id 
and subject line Bug#1011212: Removed package(s) from unstable
has caused the Debian Bug report #963072,
regarding haskell-easytest: Does not build with hedgehog 1.x
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.)


-- 
963072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-easytest
Version: 0.2.1-2
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/joelburget/easytest/issues/26

easytest does not work with hedgehog 1.x (available on unstable).
Luckily, hledger (the only rev dep of easytest) replaced it with tasty:

  https://github.com/simonmichael/hledger/commit/13a3542464de479e8

If easytest continues to be unmaintained, we may want to consider
removing it from Debian.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.2.1-2+rm

Dear submitter,

as the package haskell-easytest 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/1011212

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#914353: marked as done (hdbc-odbc: Missing build-dependency on concurrent-extra)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:57:04 +
with message-id 
and subject line Bug#1011216: Removed package(s) from unstable
has caused the Debian Bug report #914353,
regarding hdbc-odbc: Missing build-dependency on concurrent-extra
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.)


-- 
914353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdbc-odbc
Version: 2.3.1.1-9
Severity: serious
Justification: fails to build from source

This package has no reverse dependencies and is not on LTS.
Do we want to continue maintaining it? If so, we will have to package
concurrent-extra.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 2.5.0.1-2+rm

Dear submitter,

as the package hdbc-odbc 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/1011216

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#964824: marked as done (hdevtools: FTBFS with GHC 8.8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:56:38 +
with message-id 
and subject line Bug#1011217: Removed package(s) from unstable
has caused the Debian Bug report #964824,
regarding hdevtools: FTBFS with GHC 8.8
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.)


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

hdevtools currently fails to build:
| [ 4 of 14] Compiling Info ( src/Info.hs, 
dist-ghc/build/hdevtools/hdevtools-tmp/Info.o )
|
| src/Info.hs:89:14: error:
| • Couldn't match type ‘GHC.GenLocated GHC.SrcSpan a0’
|  with ‘GHC.Pat TypecheckI’
|   Expected type: [GHC.LPat TypecheckI]
| Actual type: [GHC.Located a0]
| • In the expression:
|   listifySpans tcs (line, col) :: [GHC.LPat TypecheckI]
|   In an equation for ‘ps’:
|   ps = listifySpans tcs (line, col) :: [GHC.LPat TypecheckI]
|   In the expression:
| do let tcs = GHC.tm_typechecked_source tcm
|bs = ...
|
|bts <- mapM (getTypeLHsBind tcm) bs
|ets <- mapM (getTypeLHsExpr tcm) es
|pts <- mapM (getTypeLPat tcm) ps
|
||
| 89 | ps = listifySpans tcs (line, col) :: [GHC.LPat TypecheckI]
||  
|
| src/Info.hs:158:16: error:
| • Couldn't match type ‘GHC.GenLocated
|  GHC.SrcSpan (GHC.Pat GHC.GhcTc)’
|  with ‘GHC.Pat TypecheckI’
|   Expected type: GHC.LPat TypecheckI
| Actual type: GHC.GenLocated GHC.SrcSpan (GHC.Pat GHC.GhcTc)
| • In the pattern: GHC.L spn pat
|   In an equation for ‘getTypeLPat’:
|   getTypeLPat _ (GHC.L spn pat)
| = return $ Just (spn, TcHsSyn.hsPatType pat)
| |
| 158 | getTypeLPat _ (GHC.L spn pat) = return $ Just (spn, TcHsSyn.hsPatType 
pat)
| |^
| make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.1.8.0-1+rm

Dear submitter,

as the package hdevtools 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/1011217

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#970453: marked as done (coq-float: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:54:02 +
with message-id 
and subject line Bug#1011347: Removed package(s) from unstable
has caused the Debian Bug report #970453,
regarding coq-float: FTBFS in sid
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.)


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

Hello, this is the build log (attached)

make[1]: Leaving directory '/<>'
   dh_clean
 dpkg-source -Zxz -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building coq-float using existing 
./coq-float_8.10.0.orig.tar.gz
dpkg-source: info: building coq-float in coq-float_8.10.0-1.debian.tar.xz
dpkg-source: info: building coq-float in coq-float_8.10.0-1.dsc
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make all
make[2]: Entering directory '/<>'
coq_makefile -f Make -o Makefile.coq
make -f Makefile.coq Makefile
make[3]: Entering directory '/<>'
COQDEP VFILES
make[3]: Nothing to be done for 'Makefile'.
make[3]: Leaving directory '/<>'
make -f Makefile.coq all
make[3]: Entering directory '/<>'
COQC sTactic.v
COQC Faux.v
File "./Faux.v", line 640, characters 0-63:
Error: No such goal.

make[4]: *** [Makefile.coq:716: Faux.vo] Error 1
make[3]: *** [Makefile.coq:339: all] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:2: all] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: binary] Error 2
dpkg-buildpackage-debomatic-original: error: debian/rules binary subprocess 
returned exit status 2



G.

sbuild (Debian sbuild) 0.78.1 (09 February 2019) on misc-debomatic1

+==+
| coq-float 1:8.10.0-1 (amd64) Wed, 16 Sep 2020 09:46:45 + |
+==+

Package: coq-float
Version: 1:8.10.0-1
Source Version: 1:8.10.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-debomatic-0194c9e2-9684-4720-b99d-4f9e1b12cdfe'
 with '<>'

+--+
| Chroot Setup Commands|
+--+


/home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/apt-speedup 
coq-float_8.10.0-1 unstable amd64



I: Finished running 
'/home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/apt-speedup 
coq-float_8.10.0-1 unstable amd64'.

Finished processing commands.

I: NOTICE: Log filtering will replace 'build/coq-float-RLWwzM/resolver-lS5yzA' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://ftp.debian.org/debian unstable InRelease [146 kB]
Get:2 http://ftp.debian.org/debian unstable/main amd64 Packages [11.4 MB]
Fetched 11.5 MB in 1s (10.9 MB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  cpp-10 dmidecode gcc-10-base libelf1 libgcc-s1 libgnutls30 libstdc++6
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.2 MB of archives.
After this operation, 7168 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian unstable/main amd64 cpp-10 amd64 10.2.0-8 
[8003 kB]
Get:2 http://ftp.debian.org/debian unstable/main amd64 gcc-10-base amd64 
10.2.0-8 [199 kB]
Get:3 http://ftp.debian.org/debian unstable/main amd64 libstdc++6 amd64 
10.2.0-8 [492 kB]
Get:4 http://ftp.debian.org/debian unstable/main amd64 libgcc-s1 amd64 10.2.0-8 
[41.4 kB]
Get:5 http://ftp.debian.org/debian 

Bug#975464: marked as done (haskell-werewolf: Removal notice: broken and unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:55:18 +
with message-id 
and subject line Bug#1011223: Removed package(s) from unstable
has caused the Debian Bug report #975464,
regarding haskell-werewolf: Removal notice: broken and unmaintained
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.)


-- 
975464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-werewolf
Version: 1.5.2.0-4
Severity: grave
Justification: renders package unusable

This package seems to be unmaintained (last upload in 2017).
Does not build with GHC 8.8, is not part of Stackage and has no rev
dependencies.

I intend to remove this package.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 1.5.2.0-4+rm

Dear submitter,

as the package haskell-werewolf 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/1011223

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#967102: marked as done (rss2irc: FTBFS: unsatisfiable build-dependencies: Depends: libghc-feed-dev (< 1.1) but 1.3.0.1-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:55:50 +
with message-id 
and subject line Bug#1011221: Removed package(s) from unstable
has caused the Debian Bug report #967102,
regarding rss2irc: FTBFS: unsatisfiable build-dependencies: Depends: 
libghc-feed-dev (< 1.1) but 1.3.0.1-1 is to be installed
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.)


-- 
967102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rss2irc
Version: 1.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200803 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), cdbs, 
> ghc (>= 8.4.3), libghc-safesemaphore-dev (>= 0.10), libghc-safesemaphore-dev 
> (<< 1.1), libghc-cmdargs-dev, libghc-feed-dev (>= 1), libghc-feed-dev (<< 
> 1.1), libghc-http-client-dev (>= 0.2.1), libghc-http-client-dev (<< 0.6), 
> libghc-http-conduit-dev (>= 1.9), libghc-http-conduit-dev (<< 2.4), 
> libghc-http-types-dev (>= 0.6.4), libghc-http-types-dev (<< 1.0), 
> libghc-io-storage-dev (>= 0.3), libghc-io-storage-dev (<< 0.4), 
> libghc-irc-dev (>= 0.6), libghc-irc-dev (<< 0.7), libghc-network-dev (>= 
> 2.6), libghc-network-dev (<< 2.9), libghc-network-uri-dev (>= 2.6), 
> libghc-network-uri-dev (<< 2.7), libghc-old-locale-dev, libghc-regexpr-dev 
> (>= 0.5), libghc-regexpr-dev (<< 0.6), libghc-resourcet-dev (>= 0.4.4), 
> libghc-resourcet-dev (<< 1.3), libghc-safe-dev (>= 0.2), libghc-safe-dev (<< 
> 0.4), libghc-split-dev (>= 0.2), libghc-split-dev (<< 0.3), 
> libghc-utf8-string-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), 
> cdbs, ghc (>= 8.4.3), libghc-safesemaphore-dev (>= 0.10), 
> libghc-safesemaphore-dev (<< 1.1), libghc-cmdargs-dev, libghc-feed-dev (>= 
> 1), libghc-feed-dev (<< 1.1), libghc-http-client-dev (>= 0.2.1), 
> libghc-http-client-dev (<< 0.6), libghc-http-conduit-dev (>= 1.9), 
> libghc-http-conduit-dev (<< 2.4), libghc-http-types-dev (>= 0.6.4), 
> libghc-http-types-dev (<< 1.0), libghc-io-storage-dev (>= 0.3), 
> libghc-io-storage-dev (<< 0.4), libghc-irc-dev (>= 0.6), libghc-irc-dev (<< 
> 0.7), libghc-network-dev (>= 2.6), libghc-network-dev (<< 2.9), 
> libghc-network-uri-dev (>= 2.6), libghc-network-uri-dev (<< 2.7), 
> libghc-old-locale-dev, libghc-regexpr-dev (>= 0.5), libghc-regexpr-dev (<< 
> 0.6), libghc-resourcet-dev (>= 0.4.4), libghc-resourcet-dev (<< 1.3), 
> libghc-safe-dev (>= 0.2), libghc-safe-dev (<< 0.4), libghc-split-dev (>= 
> 0.2), libghc-split-dev (<< 0.3), libghc-utf8-string-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [609 B]
> Get:5 copy:/<>/apt_archive ./ Packages [696 B]
> Fetched 2268 B in 0s (225 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libghc-feed-dev (< 1.1) but 
> 1.3.0.1-1 is to be installed
>Depends: libghc-http-client-dev (< 0.6) 
> but 0.6.4.1-2+b1 is to be installed
>Depends: libghc-network-dev (< 2.9) but 
> 3.1.1.1-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   

Bug#964842: marked as done (haskell-yesod-auth-oauth2: BD-Uninstallable)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:54:53 +
with message-id 
and subject line Bug#1011224: Removed package(s) from unstable
has caused the Debian Bug report #964842,
regarding haskell-yesod-auth-oauth2: BD-Uninstallable
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.)


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

haskell-yesod-auth-oauth2 build-depends on missing:
- libghc-hoauth2-dev:amd64 (< 1.9)

libghc-hoauth2-dev is at version 1.11.0-2.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.6.1.2-1+rm

Dear submitter,

as the package haskell-yesod-auth-oauth2 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/1011224

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#964830: marked as done (haskell-icalendar: BD-Uninstallable)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:56:13 +
with message-id 
and subject line Bug#1011219: Removed package(s) from unstable
has caused the Debian Bug report #964830,
regarding haskell-icalendar: BD-Uninstallable
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.)


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

haskell-icalendar build-depends on missing:
- libghc-network-dev:amd64 (< 2.9)

libghc-network-dev is at version 3.1.1.1-1.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.4.0.5-2+rm

Dear submitter,

as the package haskell-icalendar 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/1011219

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#943479: marked as done (FTBFS with ghc-8.6.5)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:55:18 +
with message-id 
and subject line Bug#1011223: Removed package(s) from unstable
has caused the Debian Bug report #943479,
regarding FTBFS with ghc-8.6.5
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.)


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

This package FTBFS with newer versions of GHC (ghc-8.6.5) with the
following error:

Building executable 'werewolf' for werewolf-1.5.2.0..
[ 1 of 53] Compiling Game.Werewolf.Message ( app/Game/Werewolf/Message.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Message.o )
[ 2 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledge.Command ( 
app/Game/Werewolf/Variant/NoRoleKnowledge/Command.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledge/Command.o
 )
[ 3 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledge.Engine ( 
app/Game/Werewolf/Variant/NoRoleKnowledge/Engine.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledge/Engine.o
 )
[ 4 of 53] Compiling Game.Werewolf.Variant.NoRoleKnowledgeOrReveal.Command ( 
app/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.hs, 
dist-ghc/build/werewolf/werewolf-tmp/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.o
 )

app/Game/Werewolf/Variant/NoRoleKnowledgeOrReveal/Command.hs:56:31: error:
• Parse error in expression!
• In the quasi-quotation:

[iFile|variant/no-role-knowledge-or-reveal/command/status/dead-players.txt|]
   |
56 | deadPlayersText game = 
[iFile|variant/no-role-knowledge-or-reveal/command/status/dead-players.txt|]
   |   
^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 1.5.2.0-4+rm

Dear submitter,

as the package haskell-werewolf 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/1011223

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#880879: marked as done (haskell-dpkg FTBFS: hlibrary.setup: parsing output of pkg-config --modversion failed)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:54:27 +
with message-id 
and subject line Bug#1011277: Removed package(s) from unstable
has caused the Debian Bug report #880879,
regarding haskell-dpkg FTBFS: hlibrary.setup: parsing output of pkg-config 
--modversion failed
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.)


-- 
880879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-dpkg
Version: 0.0.3-10
Severity: serious
Tags: buster sid

Some recent change in unstable makes haskell-dpkg FTBFS:

https://tests.reproducible-builds.org/debian/history/haskell-dpkg.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-dpkg.html

...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
make_setup_recipe
Running ghc --make Setup.hs -o debian/hlibrary.setup
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/dpkg-0.0.3/ --datasubdir=dpkg 
--htmldir=/usr/share/doc/libghc-dpkg-doc/html/ --enable-library-profiling 
--disable-shared
Configuring dpkg-0.0.3...
Dependency base ==4.*: using base-4.9.1.0
Dependency bindings-DSL >=1.0.7 && <1.1: using bindings-DSL-1.0.23
Dependency bytestring -any: using bytestring-0.10.8.1
Dependency monad-loops -any: using monad-loops-0.4.3
hlibrary.setup: parsing output of pkg-config --modversion failed
/usr/share/cdbs/1/class/hlibrary.mk:142: recipe for target 
'configure-ghc-stamp' failed
make: *** [configure-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.0.3-12+rm

Dear submitter,

as the package haskell-dpkg 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/1011277

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#998351: marked as done (Should libdbd-sqlite2-perl be shipped in bookworm?)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:51:38 +
with message-id 
and subject line Bug#1011981: Removed package(s) from unstable
has caused the Debian Bug report #998351,
regarding Should libdbd-sqlite2-perl be shipped in bookworm?
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.)


-- 
998351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbd-sqlite2-perl
Severity: serious
Tags: bookworm sid

libdbd-sqlite2-perl uses a vendored copy of SQLite 2.

SQLite 3 was released in 2004, and the the regular
SQLite 2 package is no longer shipped since bullseye (see #607969).
--- End Message ---
--- Begin Message ---
Version: 2:0.38-2+rm

Dear submitter,

as the package libdbd-sqlite2-perl 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/1011981

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#959193: marked as done (libperl5i-perl: Test failures with Devel::Declare 0.006022-1)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:52:11 +
with message-id 
and subject line Bug#1011980: Removed package(s) from unstable
has caused the Debian Bug report #959193,
regarding libperl5i-perl: Test failures with Devel::Declare 0.006022-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.)


-- 
959193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libperl5i-perl
Version: 2.13.2-1
Severity: serious
Tags: upstream ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=131226

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As noted on ci.d.n and in CPAN RT, libperl5i-perl is broken by the
recent updagrade of libdevel-declare-perl.

Couldn't find declarator 'func' at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Devel/Declare/Context/Simple.pm line 47.

Devel::Declare::Context::Simple::skip_declarator(perl5i::2::Signatures=HASH(0x55bdfacdc748))
 called at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Devel/Declare/MethodInstaller/Simple.pm 
line 62

Devel::Declare::MethodInstaller::Simple::parser(perl5i::2::Signatures=HASH(0x55bdfacdc748),
 "func", 4, 1) called at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Devel/Declare/MethodInstaller/Simple.pm 
line 25
Devel::Declare::MethodInstaller::Simple::__ANON__("func", 4) called at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Devel/Declare.pm line 277
Devel::Declare::linestr_callback("const", "func", 4) called at 
t/Meta/methods.t line 115
t/Meta/methods.t . 
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run 

etc.


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl6q98ZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaKThAAoaPibfxHkbZDHE8qNwRhy9BxzqDyApOxQizwPlKcpimPKpv4kbbC+9K9
nvTNUCDM5i3IlHTQG9V0/VwRzlX+sdpo8iGQj6UtDdGRt+BP85sewQU+HjFvpVBR
X3nD2jZmt0S/EWGiUVG65ld/6dBsaPZA63CkVtGzLHJ3h5ybsrDF1+9dQgARXRfM
/Mpdg0GMnCRZXNcAaXvddXHDYdJ//X2IW1cJwxnHzldmrSRAx5dHB0Nvdk+Inwne
IwO8VEgJOvMycKhtiyxQ13T/+4EB+R7qiwRBhV4/9eGTBQ4rfzT1AtQeez98gO1i
0warPeNN+Jxw2Htsg0O5qWG0KayTJSR2xzvBUvHEsc5gg096SHNcujbu6MN+CC8J
/jdOop5ioUIAZDyMJlufPEtvUK4pX6uPDCU9S3DeujuZdiLWl7wWn18P0cr7uGql
72wCGgsfREIhqe8KiN16dGbF14H6hucI2J7pDI1BjK4877whV3/WxZNgP9FF/8T4
/tUxZEOucvD/Hd9g+A/1Hnm4cvdZSPC2wpzWDXYos4ihMXsMwORC8j3nXlaaj5AS
OOwbzmBNQDwhXy3wa5hHII5q+7A55mSiKFWhtWmPYj20IK66/qEvup/N8UakwYl0
Pmqlqw1GETSx6858NsW0S3N7F9jfIgaSFbCYQXu+IgwBE3Qf8Is=
=ieDu
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 2.13.2-1+rm

Dear submitter,

as the package libperl5i-perl 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/1011980

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#936869: marked as done (libgnatcoll-bindings: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:50:54 +
with message-id 
and subject line Bug#1011991: Removed package(s) from unstable
has caused the Debian Bug report #936869,
regarding libgnatcoll-bindings: 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.)


-- 
936869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgnatcoll-bindings
Version: 18-2.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:libgnatcoll-bindings

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: 21.0.0-2+rm

Dear submitter,

as the package libgnatcoll-python 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/1011991

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1002863: marked as done (node-react-audio-player: FTBFS with webpack5: Error: Invalid webpack options)

[Debian Bug Tracking System]

Your message dated Sun, 05 Jun 2022 08:49:47 +
with message-id 
and subject line Bug#1012304: Removed package(s) from unstable
has caused the Debian Bug report #1002863,
regarding node-react-audio-player: FTBFS with webpack5: Error: Invalid webpack 
options
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.)


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

Source: node-react-audio-player
Version: 0.17.0-1
Severity: important
Justification: ftbfs
Tags: ftbfs
User: pkg-javascript-de...@alioth-lists.debian.net
Usertags: webpack5


Hi,

We are starting to build against webpack5 in experimental and the 
package needed for local build is webpack and node-webpack-source from 
experimental.
During a test rebuild, node-react-audio-player was found to fail to 
build in that situation.


Relevant part (hopefully):

   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
webpack -p
[webpack-cli] Error: Unknown option '-p'
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2


The full log is attached to this mail
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on Ayoyimika-PC.localdomain

+==+
| node-react-audio-player 0.17.0-1 (amd64) Thu, 30 Dec 2021 10:03:44 + |
+==+

Package: node-react-audio-player
Version: 0.17.0-1
Source Version: 0.17.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-edd8bfd5-56d2-4cf6-830c-30a8e27dfc11'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/node-react-audio-player-5xBmM0/resolver-AQ2HwR' with '<>'

+--+
| Update chroot|
+--+

Get:1 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
InRelease
Ign:1 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
InRelease
Get:2 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Release [951 B]
Get:2 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Release [951 B]
Get:3 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Release.gpg
Ign:3 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Release.gpg
Get:4 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Packages [798 B]
Err:4 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Packages
  Could not open file 
/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive/./Packages - 
open (13: Permission denied)
Get:4 file:/build/node-react-audio-player-5xBmM0/resolver-T2XFCG/apt_archive ./ 
Packages [1381 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB]
Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Get:9 http://deb.debian.org/debian unstable/main all Contents (deb).diff/Index 
[63.8 kB]
Get:10 http://deb.debian.org/debian unstable/main amd64 Contents 
(deb).diff/Index [63.8 kB]
Get:11 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 
kB]
Get:12 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index 
[63.3 kB]
Get:13 http://deb.debian.org/debian experimental/main amd64 Contents 
(deb).diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian experimental/main all Contents 
(deb).diff/Index [63.6 kB]
Get:15 http://deb.debian.org/debian unstable/main Sources 
T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff [266 kB]
Get:16 http://deb.debian.org/debian unstable/main amd64 Packages 
T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff [277 kB]
Get:15 http://deb.debian.org/debian unstable/main Sources 
T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff [266 kB]
Get:17 http://deb.debian.org/debian unstable/main all Contents (deb) 
T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff 

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

[Lucas Nussbaum]

Hi Reinhard,

On 04/06/22 at 22:05 -0400, Reinhard Tartler wrote:
> Control: tags -1 = moreinfo unreproducible
> Hi Lucas,
> 
> Thank you for reaching out. I've been looking into this report and am a
> bit confused. I'm trying to reproduce it on my laptop, but it builds just
> fine for me. Can you please help me understand why it would fail on your
> end?

I just confirmed that it still fails (and that was in a different
environment, not on AWS, but still using sbuild). Maybe you can provide
your build log?

Lucas

Bug#1012345: librust-bytecount-dev: depends on missing package librust-packed-simd-2-0.3+default-dev

[Jonas Smedegaard]

Package: librust-bytecount-dev
Version: 0.6.3-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKcUsEACgkQLHwxRsGg
ASHxeA//VWukx86Dd5gchqYzYYuWwP2Z1nW/qQbJFOu5uXtmmQilwqkG7USbvKcx
5VeC5uq+lQvXVeWZEI1Mmug+iS23VDqel74CtJ77CFOfuhcce4JvV5QlKMssFv7A
2Xj7vguLei1yYMFrNVLZAka861tOY3xQJ3Y1OYSS2ZYlS7JzBI+dLel2YHaHKzMm
gP0X5eRfdx+w12FRSZMZqSC7KtUWsjWcEBGpiP0pOruNNrI5x+2pHYHcK8szEitW
xiv6BQcXbvIzrPc3XHB017CSq96fdb4WWrvciWAn10w1eJsZNDmj57g5TGj4DWAf
aQETcRzFXml4SKsn1U5spgX1v5khiLe6Q9DQiIjKhwIdzCRCQKSwVrMGee4P6nhO
tgT4TNguwEvUjpHA89qiShjl3K/gsVlPRELAHBmNn32nLUAN9Utx+uASjuqrKI0N
jWxHENFVBFQYJa4lX4eniKx+jfEG1EwEs8AO0JWn0ewwy2IfwftRbgeSN25r9Pcd
6gGIYDzwJ6SnP/YqNOQtUJSPxS/tK+ehWfENks6xIcSqfuamYXoJL3HKFHaQP+6u
UYPig49JglcoO1fMGr5F4Pc3Z2PiGe5tvnSN5aaZdmgOyr1QqpWEwxUc75pn0k3u
LkGZz7EcTZJHXhiQYyYBQe3w3BWfenvSAMEIGY60OTzAqbPQ4E4=
=iX3c
-END PGP SIGNATURE-