Processed: Bug#1057588 marked as pending in octave-nan

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057588 [src:octave-nan] octave-nan: FTBFS: error: 'fid' undefined near 
line 333, column 14
Added tag(s) pending.

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

Bug#1057588: marked as pending in octave-nan

[Rafael Laboissière]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-octave-team/octave-nan/-/commit/6e1b193838a252d42bcce201fd19df284c727599


d/check.m: Redefine clear function

This is necessary because some test scripts test/*.m issue the clear
command and this interferes with the way dh_octave-check works.

Gbp-Dch: Full
Closes: #1057588


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057588

Bug#1055555: marked as done (python-jellyfish fails tests with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 07:49:11 +
with message-id 
and subject line Bug#105: fixed in python-jellyfish 0.10.0-1
has caused the Debian Bug report #105,
regarding python-jellyfish fails tests with Python 3.12
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.)


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

Package: src:python-jellyfish
Version: 0.8.9-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-jellyfish fails tests with Python 3.12

[...]
=== short test summary info 

FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-dixon-dicksonx-0.813]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-martha-marhta-0.961]

FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-dwayne-duane-0.84]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-William-Williams-0.975]
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c--foo-0] - 
TypeError:...
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-a-a-1] - 
TypeError: ...
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-abc-xyz-0] - 
TypeErr...
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c--a-0.96] - T...
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-orangutan-kumquat-orangutan 
kumquat-0.976]
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-jaz-jal-0.822] 
- Typ...
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-@-@@-0.85] - 
TypeErr...
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-0-0@-0.85] - 
TypeErr...
FAILED jellyfish/test.py::test_jaro_winkler_similarity[c-a-ab-0.85] - 
TypeErr...
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-012345-0123456-0.971]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-012abc-012abcd-0.971]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-012abc-013abcd-0.879]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity[c-a1bc-a1be-0.883] - T...
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-dixon-dicksonx-0.830]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-martha-marhta-0.971]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-dwayne-duane-0.869]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-William-Williams-0.980]
FAILED jellyfish/test.py::test_jaro_winkler_similarity_longtol[c--foo-0] 
- Ty...
FAILED jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-a-a-1] 
- Typ...

FAILED jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-abc-xyz-0]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c--a-0.96]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-orangutan-kumquat-orangutan 
kumquat-0.986]
FAILED 
jellyfish/test.py::test_jaro_winkler_similarity_longtol[c-1abcdefg-1abcdefh-0.96]
FAILED jellyfish/test.py::test_jaro_winkler_deprecation[python] - 
TypeError: ...
FAILED jellyfish/test.py::test_jaro_winkler_deprecation[c] - TypeError: 
str a...
FAILED jellyfish/test.py::test_jaro_distance_deprecation - TypeError: 
str arg...
FAILED jellyfish/test.py::test_jaro_similarity[c-dixon-dicksonx-0.767] - 
Type...
FAILED jellyfish/test.py::test_jaro_similarity[c-martha-marhta-0.944] - 
TypeE...
FAILED jellyfish/test.py::test_jaro_similarity[c-dwayne-duane-0.822] - 
TypeEr...
FAILED jellyfish/test.py::test_jaro_similarity[c-0\xf000-0\xf000-1] - 
TypeErr...
FAILED jellyfish/test.py::test_jaro_similarity[c-Sint-Pietersplein 6, 
9000 Gent-Test 10, 1010 Brussel-0.518]
FAILED jellyfish/test.py::test_hamming_distance[c---0] - TypeError: str 
argum...
FAILED jellyfish/test.py::test_hamming_distance[c--abc-3] - TypeError: 
str ar...
FAILED jellyfish/test.py::test_hamming_distance[c-abc-abc-0] - 
TypeError: str...
FAILED jellyfish/test.py::test_hamming_distance[c-acc-abc-1] - 
TypeError: str...
FAILED jellyfish/test.py::test_hamming_distance[c-abcd-abc-1] - 
TypeError: st...
FAILED jellyfish/test.py::test_hamming_distance[c-abc-abcd-1] - 
TypeError: st...

FAILED jellyfish/test.py::test_hamming_distance[c-testing-this is a test-13]
FAILED jellyfish/test.py::test_hamming_distance[c-Saturday-Sunday-7] - 
TypeEr...
FAILED jellyfish/test.py::test_levenshtein_distance[c---0] - TypeError: 
str a...
FAILED jellyfish/test.py::test_levenshtein_distance[c-abc--3] - 
TypeError: st...
FAILED jellyfish/test.py::test_levenshtein_distance[c--abc-3] - 
TypeError: st...
FAILED jellyfish/test.py::test_levenshtei

Processed: Bug#1055555 marked as pending in python-jellyfish

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #105 [src:python-jellyfish] python-jellyfish fails tests with Python 
3.12
Added tag(s) pending.

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

Bug#1055555: marked as pending in python-jellyfish

[Julian Gilbey]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-jellyfish/-/commit/62b719f11470df24c47c768def1fb600dcb78827


Mark new version as working with Python 3.12 (closes: #105)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/105

Bug#1057692: rust-serde-with-macros: fails autopkgtests

[Jonas Smedegaard]

Source: rust-serde-with-macros
Version: 3.3.0-1
Severity: grave
Tags: ftbfs
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package fails its autopkgtests on all tested architectures, and
therefore is blocked from migrating to testing.

See e.g.
https://ci.debian.net/packages/r/rust-serde-with-macros/testing/amd64/39958360/
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVxcJMACgkQLHwxRsGg
ASEBlA/+JxMQ93DkpnCDK76H2A25OJ4AwdpWRDG5rLieGNGWpCBr5qodW9QtnwrD
cZT/Qi1uv1/C7/g7jVZWM2bVmONU9XMwNBT7GofTcOW/3x4qsEHXnovJb2M3/wZo
nWo563HCUUd8JB/S6ONw0mNWPhzkBlmUcHLhKC5iRORTjYGtiquFc7vCXPwEj331
ANg9NGP2GWwmbBpAxq8NMs6HHAsIZ1YVBaREhkF4JwegO6jOS6ib2yuumtOaWvgn
G7oFVVfNv5pcAXHOnEyNXSB7sJGCvuQpQwIvRXgMhq3EEmtEqrYnZtDbOXwSo3En
K2mNu/DLi9xILiXe4WBDndczi246U+BHN64HXeRUz8lUZcMMMoBeagjocjOayf7H
mDHFFMzvh+AD6FGBcGh7IxUPbq672iP79i0U98Nxh8hFzpQNbAMdsm9e3ZyOCtmN
CJxMWFIW/M9bU1eomeBLod0WEllbIztDu3eW0Rw/O91TM1vqQ0Xtf1AYWXBTIapV
HZuA/caTeGptAvUiX/rur80k+Y1j+KL1fq7vHtO/+eUq80PQkiPSUp6IWqUhJCAZ
mS/pBl8ro2Tu7+Pd3FimyzfUiZqV4tcIpahnwqkDEFv4/9R6y9mKJmO0/40J+m1b
09i0kl7BtTZgVLM1lKczvWK2Pu+uqP2NElMZh4NzJmcnlTvYhmM=
=akWP
-END PGP SIGNATURE-

Processed: severity of 1057665 is important

[Debian Bug Tracking System]

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

> severity 1057665 important
Bug #1057665 [src:python-mapnik] python-mapnik: Segfault when importing with 
python3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: arpwatch: diff for NMU version 2.1a15-8.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1054193 + pending
Bug #1054193 [src:arpwatch] arpwatch: installs arpwatch@.service twice once 
dh_installsystemd installs to /usr
Added tag(s) pending.

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

Bug#1055253: marked as done (amanda: CVE-2023-30577)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 06:19:05 +
with message-id 
and subject line Bug#1055253: fixed in amanda 1:3.5.1-11.1
has caused the Debian Bug report #1055253,
regarding amanda: CVE-2023-30577
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.)


-- 
1055253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amanda
Version: 1:3.5.1-11
Severity: grave
Tags: security upstream
Forwarded: https://github.com/zmanda/amanda/pull/228
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:3.5.1-7

Hi,

The following vulnerability was published for amanda.

CVE-2023-30577[0]:
| AMANDA (Advanced Maryland Automatic Network Disk Archiver) before
| tag-community-3.5.4 mishandles argument checking for runtar.c, a
| different vulnerability than CVE-2022-37705.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-30577
https://www.cve.org/CVERecord?id=CVE-2023-30577
[1] https://github.com/zmanda/amanda/security/advisories/GHSA-crrw-v393-h5q3
[2] https://github.com/zmanda/amanda/pull/228

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: amanda
Source-Version: 1:3.5.1-11.1
Done: Tobias Frost 

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated amanda 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, 03 Dec 2023 14:09:23 +0100
Source: amanda
Architecture: source
Version: 1:3.5.1-11.1
Distribution: unstable
Urgency: medium
Maintainer: Jose M Calhariz 
Changed-By: Tobias Frost 
Closes: 1055253
Changes:
 amanda (1:3.5.1-11.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply upstream fix for CVE-2023-30577 (Closes: #1055253)
Checksums-Sha1:
 267ab58fd85b157e1c8bb481eda0f8a30716d600 2224 amanda_3.5.1-11.1.dsc
 92fe801d1e27e1638cac8d58fe779bb126b7210f 59608 amanda_3.5.1-11.1.debian.tar.xz
 bf2769d2f8c8cf3f3edc421fdaa2c36c0f3b7f31 15376 
amanda_3.5.1-11.1_amd64.buildinfo
Checksums-Sha256:
 d9a287d391d6e73fa27f40b850ece8034c2cdb53d4a373b59931a09c9d261ed6 2224 
amanda_3.5.1-11.1.dsc
 54b0a8d7a8e073cb3cc0fa5658d6aa87ed4a2584c17de71bcbd0c39f05c32df5 59608 
amanda_3.5.1-11.1.debian.tar.xz
 de2a61f40d26eceb30ae46ee929c8127eb9b86b9eac30475d0294320e851a5a7 15376 
amanda_3.5.1-11.1_amd64.buildinfo
Files:
 97716853fef88f3d0bba7211c3ae12e5 2224 utils optional amanda_3.5.1-11.1.dsc
 80e786513f4f11f7ca60cce32572c581 59608 utils optional 
amanda_3.5.1-11.1.debian.tar.xz
 13f41f3f28f231cc98bcd4961bb26f96 15376 utils optional 
amanda_3.5.1-11.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmVsfxIACgkQkWT6HRe9
XTbSYxAA2vbw+TyUMz1G/wrfK1WVMTevsjqM6Zt/j0iDc3CYqATwFeEn6liwfOnt
T0eHYxz5yMVQcQOWaUDwK8HKbVQ32mwdfSFRcVgRurV8qbLoLv4O8lMROnYBq1FD
WUZHt52RbmEkw06lz9omsf1906bs2rbovXTKD1V4rNoHm4GrqhxMcfihG1jhgUn7
g4UCrdZI2N1RORkf3rJc7KlXCh0WYnX2fzkp2N2C4Poj0RS29aGSSs8RuGkwk2cp
bHV37Eop7D0LnMRnF2AbS1epAYDEpvwIdqYtdjCb1+rF50vlQAhr8CQfCGew5ZiK
6dwoz5z1MFoL8EIvrrEFLbtWbonx5XusXP9P3Y7UuaxkYQWellC+Lh9ijxHWZdUK
h7vobc9za3VpXLphtiy+IzCkfqsw/dZ5/kGAhFKkJK31+tc1r/jct969MZV3R3rY
WwV9n2VJB4LzZWkTxRRCdAm6gSmms4m/F5lMN++3m41TiKMSTPWTMbHCa9lJTC4U
BnntTLxBgo8AMS+gezI+VE2LO1+wNSpxrJvXM8ONk+oO+rj1sFlAtgUKZqX2TBB8
VSbpQRR5vJ/3Kf72LMo7N4XtBRJDKYF53u5BoA6mxqsW4c8crQxNM8s3y9uKZl3E
dK4IIS6z9hyPWL/ZqgVm4qVXBifPEoSXxfSHLG9kVEXDRbk+K+w=
=UK+8
-END PGP SIGNATURE End Message ---

Bug#1054193: arpwatch: diff for NMU version 2.1a15-8.1

[Salvatore Bonaccorso]

Control: tags 1054193 + pending


Dear maintainer,

arpwatch has been removed from testing now.

I've prepared an NMU for arpwatch (versioned as 2.1a15-8.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru arpwatch-2.1a15/debian/arpwatch.install arpwatch-2.1a15/debian/arpwatch.install
--- arpwatch-2.1a15/debian/arpwatch.install	2021-01-31 17:44:03.0 +0100
+++ arpwatch-2.1a15/debian/arpwatch.install	2023-12-07 07:12:41.0 +0100
@@ -1,7 +1,6 @@
 arp2ethers   usr/sbin/
 arpfetch usr/sbin/
 *.awkusr/lib/arpwatch/
-debian/arpwatch@.service lib/systemd/system
 debian/etc/READMEetc/arpwatch/
 debian/ieee-data-update/arpwatch var/lib/ieee-data/update.d/
 debian/sbin/*usr/sbin/
diff -Nru arpwatch-2.1a15/debian/changelog arpwatch-2.1a15/debian/changelog
--- arpwatch-2.1a15/debian/changelog	2021-01-31 17:44:03.0 +0100
+++ arpwatch-2.1a15/debian/changelog	2023-12-07 07:12:41.0 +0100
@@ -1,3 +1,12 @@
+arpwatch (2.1a15-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Install arpwatch@.service only once. (Closes: #1054193)
+
+ -- Salvatore Bonaccorso   Thu, 07 Dec 2023 07:12:41 +0100
+
 arpwatch (2.1a15-8) unstable; urgency=medium
 
   * Team Upload

Bug#1057583: marked as done (node-gulp-changed: FTBFS: not ok 3 TypeError: getStream.array is not a function)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 05:49:29 +
with message-id 
and subject line Bug#1057583: fixed in node-gulp-changed 4.0.3-3
has caused the Debian Bug report #1057583,
regarding node-gulp-changed: FTBFS: not ok 3 TypeError: getStream.array is not 
a function
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.)


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

Package: src:node-gulp-changed
Version: 4.0.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 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/figures node_modules/figures
ln -s ../debian/tests/test_modules/touch node_modules/touch
ln -s ../. node_modules/gulp-changed
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# compareLastModifiedTime › using relative dest
# compareLastModifiedTime › using relative dest
# compareContents › should not pass any files through in identical directories
not ok 1 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:94:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using file extension
not ok 2 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:102:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using transformPath
not ok 3 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:117:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# compareContents › should only pass through changed files using extension 
.coffee
not ok 4 TypeError: getStream.array is not a function
  ---
operator: error
stack: |-
  TypeError: getStream.array is not a function
  at Test. (/<>/test.js:129:32)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...

1..4
# tests 4
# pass  0
# fail  4

dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not

Bug#1057584: marked as done (node-qs: FTBFS: Error: module has-proto in /<>/node_modules/get-intrinsic not found)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 05:49:38 +
with message-id 
and subject line Bug#1057584: fixed in node-qs 6.11.0+ds+~6.9.7-4
has caused the Debian Bug report #1057584,
regarding node-qs: FTBFS: Error: module has-proto in 
/<>/node_modules/get-intrinsic not found
to be marked as done.

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

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


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

Package: src:node-qs
Version: 6.11.0+ds+~6.9.7-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link ./node_modules/available-typed-arrays -> 
/usr/share/nodejs/available-typed-arrays
Link ./node_modules/call-bind -> /usr/share/nodejs/call-bind
Link ./node_modules/es-abstract -> /usr/share/nodejs/es-abstract
Link ./node_modules/for-each -> /usr/share/nodejs/for-each
Link ./node_modules/function-bind -> /usr/share/nodejs/function-bind
Link ./node_modules/get-intrinsic -> /usr/share/nodejs/get-intrinsic
Link ./node_modules/gopd -> /usr/share/nodejs/gopd
Link ./node_modules/has-symbols -> /usr/share/nodejs/has-symbols
Link ./node_modules/has -> /usr/share/nodejs/has
Link ./node_modules/has-tostringtag -> /usr/share/nodejs/has-tostringtag
Link ./node_modules/inherits -> /usr/share/nodejs/inherits
Link ./node_modules/is-arguments -> /usr/share/nodejs/is-arguments
Link ./node_modules/is-callable -> /usr/share/nodejs/is-callable
Link ./node_modules/is-generator-function -> 
/usr/share/nodejs/is-generator-function
Link ./node_modules/is-typed-array -> /usr/share/nodejs/is-typed-array
Link ./node_modules/object-inspect -> /usr/share/nodejs/object-inspect
Link ./node_modules/side-channel -> /usr/share/nodejs/side-channel
Link ./node_modules/util -> /usr/share/nodejs/util
Link ./node_modules/which-typed-array -> /usr/share/nodejs/which-typed-array
Link node_modules/@types/qs -> ../../types-qs
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
mkdir dist
browserify-lite ./lib/index.js --outfile dist/qs.js
/usr/share/nodejs/browserify-lite/cli.js:29
  if (err) throw err;
   ^

Error: module has-proto in /<>/node_modules/get-intrinsic not found
at trySearchPath (/usr/share/nodejs/browserify-lite/index.js:269:32)
at /usr/share/nodejs/browserify-lite/index.js:274:7
at /usr/share/nodejs/browserify-lite/index.js:294:21
at FSReqCallback.oncomplete (node:fs:202:21)

Node.js v18.19.0
make[1]: *** [debian/rules:13: 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 above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-qs
Source-Version: 6.11.0+ds+~6.9.7-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-qs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu

Bug#1057582: marked as done (Bad commonjs build)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 05:49:23 +
with message-id 
and subject line Bug#1057582: fixed in node-get-stream 8.0.1-10
has caused the Debian Bug report #1057582,
regarding Bad commonjs build
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.)


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

Package: src:node-decompress-response
Version: 6.0.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 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/decompress-response
/bin/sh -ex debian/tests/pkg-js/test
+ tape test/test.js
TAP version 13
# decompress gzipped content
ok 1 should be truthy
ok 2 should be truthy
ok 3 should be truthy
ok 4 should be truthy
ok 5 should be truthy
ok 6 should be truthy
ok 7 should be truthy
ok 8 should be truthy
ok 9 should be truthy
ok 10 should be truthy
ok 11 should be truthy
ok 12 should be truthy
not ok 13 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test/test.js:72:13)
  at process.processTicksAndRejections 
(node:internal/process/task_queues:95:5)
  ...
# decompress deflated content
node:events:495
  throw er; // Unhandled 'error' event
  ^

Error: listen EADDRINUSE: address already in use :::59060
at Server.setupListenHandle [as _listen2] (node:net:1811:16)
at listenInCluster (node:net:1859:12)
at Server.listen (node:net:1947:7)
at /usr/share/nodejs/pify/index.js:33:11
at new Promise ()
at Server. (/usr/share/nodejs/pify/index.js:6:9)
at Object.apply (/usr/share/nodejs/pify/index.js:85:19)
at before (/<>/test/test.js:46:15)
at Test. (/<>/test/test.js:80:5)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1838:8)
at process.processTicksAndRejections 
(node:internal/process/task_queues:82:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 59060
}

Node.js v18.19.0
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-get-stream
Source-Version: 8.0.1-10
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-get-stream package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2023 07:19:05 +0400
Source: node-get-stream
Architecture: source
Version: 8.0.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintai

Bug#1057585: marked as done (node-strip-bom-stream: FTBFS: not ok 2 TypeError: getStream is not a function)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 05:49:23 +
with message-id 
and subject line Bug#1057582: fixed in node-get-stream 8.0.1-10
has caused the Debian Bug report #1057582,
regarding node-strip-bom-stream: FTBFS: not ok 2 TypeError: getStream is not a 
function
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.)


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

Package: src:node-strip-bom-stream
Version: 4.0.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/is-utf8 -> ../is-utf8
Link node_modules/strip-bom-buf -> ../strip-bom-buf
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/strip-bom-stream
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# main
not ok 1 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test.js:7:23)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...
# low `highWaterMark`
not ok 2 TypeError: getStream is not a function
  ---
operator: error
stack: |-
  TypeError: getStream is not a function
  at Test. (/<>/test.js:13:23)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:476:21)
  ...

1..2
# tests 2
# pass  0
# fail  2

dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-get-stream
Source-Version: 8.0.1-10
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-get-stream package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2023 07:19:05 +0400
Source: node-get-stream
Architecture: source
Version: 8.0.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1057582
Changes:
 node-get-stream (8.0.1-10) unstable; urgency=medium
 .
   * Team upload
   * D

Processed: Bug#1057583 marked as pending in node-gulp-changed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057583 [src:node-gulp-changed] node-gulp-changed: FTBFS: not ok 3 
TypeError: getStream.array is not a function
Added tag(s) pending.

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

Bug#1057583: marked as pending in node-gulp-changed

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-gulp-changed/-/commit/5fb85e2fbd0efee84f5bb931298eecda4b26fd0e


Add patch for node-get-stream >= 8

Closes: #1057583


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057583

Processed: reassign #1057546 to calamares

[Debian Bug Tracking System]

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

> reassign 1057546 calamares
Bug #1057546 [src:calamares-extensions] calamares-extensions: FTBFS: Unknown 
CMake command "set_package_properties".
Bug reassigned from package 'src:calamares-extensions' to 'calamares'.
No longer marked as found in versions calamares-extensions/1.3.2-1.
Ignoring request to alter fixed versions of bug #1057546 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Xiyue Deng]

Nicholas D Steeves  writes:

> Xiyue Deng  writes:
>
>> Control: tags -1 pending
>>
>> Hi,
>>
>> I have prepared a patch[1] that fixes this issue and also forwarded it
>> upstream[2].  I have also prepared the package on mentors[3].  Please
>> consider reviewing and sponsoring it.  TIA!
>>
>> [1] 
>> https://salsa.debian.org/emacsen-team/emacs-wgrep/-/commit/62bc99d768bcb290612b834c668f131e9f5b53f0
>> [2] https://github.com/mhayashi1120/Emacs-wgrep/pull/93
>> [3] https://mentors.debian.net/package/emacs-wgrep/
>> -- 
>> Xiyue Deng
>
> Looks good.  Go ahead and finalise the package, and delete changelog:L4
> whitespace at that time.
>
> --N
>

Done.  Also reuploaded to mentors just in case.

-- 
Xiyue Deng


signature.asc
Description: PGP signature

Processed: affects 1052763, user debian...@lists.debian.org, usertagging 1052763

[Debian Bug Tracking System]

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

> affects 1052763 + gnuastro libgnuastro-dev
Bug #1052763 [libgnuastro18] libgnuastro18 has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/libgnuastro_make.so
Added indication that 1052763 affects gnuastro and libgnuastro-dev
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1052763 piuparts
Usertags were: fileconflict.
Usertags are now: fileconflict piuparts.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1057675: urlview: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/urlview/examples/sample.urlview

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1057675 [urlview] urlview: postinst uses /usr/share/doc content (Policy 
12.3): /usr/share/doc/urlview/examples/sample.urlview
Added tag(s) pending.

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

Bug#1057675: urlview: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/urlview/examples/sample.urlview

[наб]

Control: tags -1 + pending

On Thu, Dec 07, 2023 at 02:28:39AM +0100, Andreas Beckmann wrote:
> Package: urlview
> Version: 1b-1
> 
> a test with piuparts revealed that your package uses files from
> /usr/share/doc in its maintainer scripts which is a violation of
> Policy 12.3: "Packages must not require the existence of any files in
> /usr/share/doc/ in order to function."
> https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation
> 
> These files must be moved to /usr/share/$PACKAGE and may be symlinked
> from /usr/share/doc/$PACKAGE.
Comparing 0.9-24 and 1b-1, I see that I started to use ucf with a
  /usr/share/urlview/examples/sample.urlview /etc/urlview/system.urlview
stanza. I'm gonna be frank: I don't know why, since this file is already
covered by the conffile mechanism. And, re-reading the conffile sexion,
  https://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
> Note that a package should not modify a dpkg-handled conffile in its
> maintainer scripts. Doing this will lead to dpkg giving the user
> confusing and possibly dangerous options for conffile update when the
> package is upgraded.
which is precisely what ucf does.

Thankfully, we're in a fortunate situation of there having only been one
urlview with ucf, and /e/u/s.u is installed (and conffile-tagged)
in both versions, so an upgrade-test shows we can drop it
with the normal conffile mechanism correctly handling the situation.

Fixed in
  
https://git.sr.ht/~nabijaczleweli/urlview.deb/commit/13cd0e45d02da500ff0b8ed32701bd9ac9131454

Thank you for your report!
This would be a lot uglier if we ended up with multiple versions
with double conffile+ucf handling, I think.

Best,
наб


signature.asc
Description: PGP signature

Processed: affects 1057582

[Debian Bug Tracking System]

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

> affects 1057582 node-decompress-response
Bug #1057582 [node-get-stream] Bad commonjs build
Bug #1057585 [node-get-stream] node-strip-bom-stream: FTBFS: not ok 2 
TypeError: getStream is not a function
Added indication that 1057582 affects node-decompress-response
Added indication that 1057585 affects node-decompress-response
> thanks
Stopping processing here.

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

Processed: reassign 1057585 to node-get-stream, affects 1057585, forcibly merging 1057585 1057582

[Debian Bug Tracking System]

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

> reassign 1057585 node-get-stream
Bug #1057585 [src:node-strip-bom-stream] node-strip-bom-stream: FTBFS: not ok 2 
TypeError: getStream is not a function
Bug reassigned from package 'src:node-strip-bom-stream' to 'node-get-stream'.
No longer marked as found in versions node-strip-bom-stream/4.0.0-2.
Ignoring request to alter fixed versions of bug #1057585 to the same values 
previously set
> affects 1057585 node-strip-bom-stream
Bug #1057585 [node-get-stream] node-strip-bom-stream: FTBFS: not ok 2 
TypeError: getStream is not a function
Added indication that 1057585 affects node-strip-bom-stream
> forcemerge 1057585 1057582
Bug #1057585 [node-get-stream] node-strip-bom-stream: FTBFS: not ok 2 
TypeError: getStream is not a function
Bug #1057585 [node-get-stream] node-strip-bom-stream: FTBFS: not ok 2 
TypeError: getStream is not a function
Added tag(s) pending.
Bug #1057582 [node-get-stream] Bad commonjs build
Removed indication that 1057582 affects node-decompress-response
Added indication that 1057582 affects node-strip-bom-stream
Merged 1057582 1057585
> thanks
Stopping processing here.

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

Bug#1057584: marked as pending in node-qs

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-qs/-/commit/d674e719bd69897cf78c19323183e6a597a7cd36


Fix build links

Closes: #1057584


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057584

Processed: Bug#1057584 marked as pending in node-qs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057584 [src:node-qs] node-qs: FTBFS: Error: module has-proto in 
/<>/node_modules/get-intrinsic not found
Added tag(s) pending.

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

Processed: reassign 1057582 to node-get-stream, affects 1057582, retitle 1057582 to Bad commonjs build

[Debian Bug Tracking System]

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

> reassign 1057582 node-get-stream
Bug #1057582 [src:node-decompress-response] node-decompress-response: FTBFS: 
not ok 13 TypeError: getStream is not a function
Bug reassigned from package 'src:node-decompress-response' to 'node-get-stream'.
No longer marked as found in versions node-decompress-response/6.0.0-2.
Ignoring request to alter fixed versions of bug #1057582 to the same values 
previously set
> affects 1057582 node-decompress-response
Bug #1057582 [node-get-stream] node-decompress-response: FTBFS: not ok 13 
TypeError: getStream is not a function
Added indication that 1057582 affects node-decompress-response
> retitle 1057582 Bad commonjs build
Bug #1057582 [node-get-stream] node-decompress-response: FTBFS: not ok 13 
TypeError: getStream is not a function
Changed Bug title to 'Bad commonjs build' from 'node-decompress-response: 
FTBFS: not ok 13 TypeError: getStream is not a function'.
> thanks
Stopping processing here.

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

Processed: Bug#1057582 marked as pending in node-get-stream

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057582 [node-get-stream] Bad commonjs build
Added tag(s) pending.

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

Bug#1057582: marked as pending in node-get-stream

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-get-stream/-/commit/83dc26f3021df4a4cadd1ed18e041059090b6f1b


Fix commonjs build

Closes: #1057582


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057582

Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Nicholas D Steeves]

Xiyue Deng  writes:

> Control: tags -1 pending
>
> Hi,
>
> I have prepared a patch[1] that fixes this issue and also forwarded it
> upstream[2].  I have also prepared the package on mentors[3].  Please
> consider reviewing and sponsoring it.  TIA!
>
> [1] 
> https://salsa.debian.org/emacsen-team/emacs-wgrep/-/commit/62bc99d768bcb290612b834c668f131e9f5b53f0
> [2] https://github.com/mhayashi1120/Emacs-wgrep/pull/93
> [3] https://mentors.debian.net/package/emacs-wgrep/
> -- 
> Xiyue Deng

Looks good.  Go ahead and finalise the package, and delete changelog:L4
whitespace at that time.

--N


signature.asc
Description: PGP signature

Bug#1057388: marked as done (unrardll: needs binary upload to add Python 3.12 as supported)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 02:42:07 +
with message-id 
and subject line Bug#1057388: fixed in unrardll 0.1.7-2
has caused the Debian Bug report #1057388,
regarding unrardll: needs binary upload to add Python 3.12 as supported
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.)


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

Hi Maintainer

The package unrardll requires a binary upload since it is in contrib
and cannot be built on the buildds [1].

Please upload the binary package python3-unrardll_0.1.7-1+b1_amd64.deb to
the archive.  There is no need for another source upload and no need
to bump the version.

However, as suggested in #977170, a source+binary upload may just be easier.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=unrardll
--- End Message ---
--- Begin Message ---
Source: unrardll
Source-Version: 0.1.7-2
Done: YOKOTA Hiroshi 

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

Debian distribution maintenance software
pp.
YOKOTA Hiroshi  (supplier of updated unrardll package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2023 10:49:16 +0900
Source: unrardll
Binary: python3-unrardll python3-unrardll-dbgsym
Architecture: source amd64
Version: 0.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Unrardll maintainer team 
Changed-By: YOKOTA Hiroshi 
Description:
 python3-unrardll - Python wrapper for the unrar shared library
Closes: 1057388
Changes:
 unrardll (0.1.7-2) unstable; urgency=medium
 .
   * Rebuild to Python 3.12 support (Closes: #1057388)
Checksums-Sha1:
 97d8f957253a4c3752c7e0ab1eac855afacf19c4 2336 unrardll_0.1.7-2.dsc
 00bb00b89ac403f7f244e4f2c852280f93d8c16e 6144 unrardll_0.1.7-2.debian.tar.xz
 8b2650af9b113f68e246cfebebe1845696a0f4f4 39164 
python3-unrardll-dbgsym_0.1.7-2_amd64.deb
 a41a50157b06a7e659324384e6531036c1536f11 15408 
python3-unrardll_0.1.7-2_amd64.deb
 01f1adc460db5f759b4a824da49a7d31b1bde950 7640 unrardll_0.1.7-2_amd64.buildinfo
Checksums-Sha256:
 765bcf89dbbe8f0d809d757749ef327029e175c45bb9424b0267683caac591f2 2336 
unrardll_0.1.7-2.dsc
 b333e983412cbb1a504fbb283c11ce4f69d233f5d0584305db43062a469c66e4 6144 
unrardll_0.1.7-2.debian.tar.xz
 5ea8ad1e4f2cf98a61ff790c5263563cf75630e3013735ca448c17e49de498a4 39164 
python3-unrardll-dbgsym_0.1.7-2_amd64.deb
 b257d72514d9752ccefe864374036b223e9e98330dc7df345dee7de7cd6812e1 15408 
python3-unrardll_0.1.7-2_amd64.deb
 b2487a0e92db7bd4e5f642ff802283989f327428f9c6c6691d4bd381a069f1be 7640 
unrardll_0.1.7-2_amd64.buildinfo
Files:
 9a598f39efc79156beb9bd0e49948be8 2336 contrib/python optional 
unrardll_0.1.7-2.dsc
 22bf43f0bd9f6f47f750517e094cffe6 6144 contrib/python optional 
unrardll_0.1.7-2.debian.tar.xz
 3947380ef360fecc3f3d01aeb0979874 39164 contrib/debug optional 
python3-unrardll-dbgsym_0.1.7-2_amd64.deb
 446216fabc20567950feb1235977a9ff 15408 contrib/python optional 
python3-unrardll_0.1.7-2_amd64.deb
 92d96194fa4c6bceb6ca0d1e05d0ff08 7640 contrib/python optional 
unrardll_0.1.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEErjlfKHqxT11VFyPEqem2T5LebcoFAmVxJgsWHHlva290YS5o
Z21sQGdtYWlsLmNvbQAKCRCp6bZPkt5tyrwID/9U260MAR91TopFDqfQqNUTgSi9
tEtUnLuo8bfaqwgUDZ9AsINksMHW9x5vhVNgyJMV9qOY9bdluQ44I8OLn6TPwR0R
ewMjq03NPmB6DNCkX9LZpXFnBvTrepJGzKnvLd4sf//IrmVd/QMARxQyNEezzGvp
G9CZ0UR4wJBiicO4w5OMmI5/xoKqFgx/38i4qz2v0hj1yeC5FW9Iqy6FoqHUdgf/
tkuuz4dkzINqO37wHyDoH5PDImg1zwwcG2JbjG/tELNVtf/Lg5we+sWMmu8HJws5
mpIB7N0RDCxaPOCXdLBhujR1MjF62aIVSpJ9/4+H1kQhcfMklPywIMIjK43tdhrF
aypo2EOFyN1zFSWI0+oddzZDzg4gQoxGQ8R7boT/sHQau+Aj5fQyBHluG5671bdb
GZdF7q2kye5eqitae4EFwNEMR3YrueswhJayGEX/DpT5dhmWodi81Y/ONNbZSdzI
s10wSyUCMEVTfA4y/SRqhCv3w+5OxjLnmaNzqJ9O/BeFyJL+IDV0cJzutIeIMHI5
x5lMGQE8qXwusdsYyL/gvDs1LMmyu8nqMGMnRMjEHIrbCX5XguMSR0HKFuVXI91g
NkLyCY5eFWciNs+dScu3TXTEDiBhduEu958XKRj7TdMGkQuqK8Oy4xwTdkGmk3OG
ZTqubnkgMUeiTb3RFw==
=XeHI
-END PGP SIGNATURE

Bug#1051155: marked as done (FTBFS with doxygen 1.9.8)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 01:37:34 +
with message-id 
and subject line Bug#1051155: fixed in wxpython4.0 4.2.1+dfsg-2
has caused the Debian Bug report #1051155,
regarding FTBFS with doxygen 1.9.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.)


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

Package: wxpython-tools
Version: 4.2.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the 
past)

X-Debbugs-Cc: paolo.gre...@libpf.com

While preparing to upload doxygen 1.9.8, I did a partial rebuild of 
packages that build-depend on it.
More info here: 
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial


Of 510 packages I tried, 5 failed and one is wxpython-tools.

The build error was:

  Running command: etg
  "/usr/bin/python3.11" etg/_core.py --sip --nodoc
  "/usr/bin/python3.11" etg/_html2.py --sip --nodoc
  "/usr/bin/python3.11" etg/_xml.py --sip --nodoc
  "/usr/bin/python3.11" etg/_xrc.py --sip --nodoc
  "/usr/bin/python3.11" etg/_richtext.py --sip --nodoc
  "/usr/bin/python3.11" etg/_stc.py --sip --nodoc
  "/usr/bin/python3.11" etg/_grid.py --sip --nodoc
  "/usr/bin/python3.11" etg/_msw.py --sip --nodoc 


  "/usr/bin/python3.11" etg/_propgrid.py --sip --nodoc
  "/usr/bin/python3.11" etg/_dataview.py --sip --nodoc
  "/usr/bin/python3.11" etg/_glcanvas.py --sip --nodoc
  Traceback (most recent call last):
File "/<>/etg/_glcanvas.py", line 137, in 
  run()
File "/<>/etg/_glcanvas.py", line 49, in run
  etgtools.parseDoxyXML(module, ITEMS) 


File "/<>/etgtools/__init__.py", line 91, in parseDoxyXML
  item = module.addElement(element)
^^
File "/<>/etgtools/extractors.py", line 1576, in 
addElement

  self.addElement(node)
File "/<>/etgtools/extractors.py", line 1547, in 
addElement

  item = EnumDef(element, inClass)
^
File "/<>/etgtools/extractors.py", line 1185, in __init__
  self.extract(element) 


File "/<>/etgtools/extractors.py", line 1189, in extract
  super(EnumDef, self).extract(element)
File "/<>/etgtools/extractors.py", line 65, in extract
  if '::' in self.name:
^
  TypeError: argument of type 'NoneType' is not iterable

I attach the full build log.

Paolo

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wxpython-tools depends on:
ii  python3   3.11.4-5+b1
ii  python3-wxgtk4.0  4.2.1+dfsg-1

wxpython-tools recommends no packages.

wxpython-tools suggests no packages.

-- no debconf information

wxpython4.0_4.2.1+dfsg-1.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: wxpython4.0
Source-Version: 4.2.1+dfsg-2
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated wxpython4.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Dec 2023 18:27:20 -0500
Source: wxpython4.0
Architecture: source
Version: 4.2.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Scott Talbert 
Closes: 1051155
Changes:
 wxpython4.0 (4.2.1+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS with doxygen 1.9.7+ (Closes: #1051155)
Checksums-Sha1:
 0baa9a63791f0455b4dfd8fb2ed6c6b4059fa184 2569 wxpython4.0_4.2.1+dfsg-2.dsc
 2e502a88fe1735279a064de5bc87583391efb421 30892 
wxpython4.0_4.2.1+dfsg-2.debian.tar.xz
 b7698f2790dea77548079fc586f4b90300a5bd59 21734 
wxpython4.0_4.

Processed: Re: Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1057559 [src:emacs-wgrep] emacs-wgrep: FTBFS: Error: error ("Test 
‘wgrep-normal’ redefined")
Added tag(s) pending.

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

Bug#1057559: emacs-wgrep: FTBFS: Error: error ("Test ‘wgrep-normal’ redefined")

[Xiyue Deng]

Control: tags -1 pending

Hi,

I have prepared a patch[1] that fixes this issue and also forwarded it
upstream[2].  I have also prepared the package on mentors[3].  Please
consider reviewing and sponsoring it.  TIA!

[1] 
https://salsa.debian.org/emacsen-team/emacs-wgrep/-/commit/62bc99d768bcb290612b834c668f131e9f5b53f0
[2] https://github.com/mhayashi1120/Emacs-wgrep/pull/93
[3] https://mentors.debian.net/package/emacs-wgrep/
-- 
Xiyue Deng

Bug#1057675: urlview: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/urlview/examples/sample.urlview

[Andreas Beckmann]

Package: urlview
Version: 1b-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Setting up urlview (1b-1) ...
  Error: The new file /usr/share/doc/urlview/examples/sample.urlview does not 
exist!
  dpkg: error processing package urlview (--configure):
   installed urlview package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.37-12) ...
  Errors were encountered while processing:
   urlview


Cheers,

Andreas


urlview_1b-1.log.gz
Description: application/gzip

Bug#1057674: pyqt6-examples: rtupdate hook uses /usr/share/doc content (Policy 12.3): /usr/share/doc/pyqt6-examples/examples/designer/calculatorform/calculatorform.py

[Andreas Beckmann]

Package: pyqt6-examples
Version: 6.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

Or in this case, probably just exclude the examples from the rtupdate
hook.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Setting up python3 (3.11.4-5+b1) ...
  [Errno 2] No such file or directory: 
'/usr/share/doc/pyqt6-examples/examples/designer/calculatorform/calculatorform.py'error
 running python rtupdate hook pyqt6-examples
  dpkg: error processing package python3 (--configure):
   installed python3 package post-installation script subprocess returned error 
exit status 4
 

Cheers,

Andreas


pyqt6-examples_6.6.0-1.log.gz
Description: application/gzip

Bug#1057464: marked as done (libsolv depends on python3-all-dev, but only builds for the default Python3)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2023 01:20:15 +
with message-id 
and subject line Bug#1057464: fixed in libsolv 0.7.27-2
has caused the Debian Bug report #1057464,
regarding libsolv depends on python3-all-dev, but only builds for the default 
Python3
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.)


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

Package: libsolv
Version: 0.7.27-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libsolv build-depends on:

 python3-all,
 python3-all-dev,
 libpython3-dev,

However it only builds for the default python3 version, not every 
supported python3 version.  Now it doesn't build for 3.12 as an extra 
version.  The build-depends can be simplified to:


 python3-dev,

or you change your packaging to build for all supported Python3 versions.

Also please check that the package builds with Python 3.12.
--- End Message ---
--- Begin Message ---
Source: libsolv
Source-Version: 0.7.27-2
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated libsolv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2023 00:43:04 +
Source: libsolv
Architecture: source
Version: 0.7.27-2
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Luca Boccassi 
Closes: 1057464
Changes:
 libsolv (0.7.27-2) unstable; urgency=medium
 .
   * Simplify dependencies on Python (Closes: #1057464)
Checksums-Sha1:
 a111e575ec4c42db3ba93d6f33e38ee6f86db96f 2449 libsolv_0.7.27-2.dsc
 75e875012f9f82468dfff87cae4bef20562ca362 19020 libsolv_0.7.27-2.debian.tar.xz
 e17164cc317cd84111fd1127863ca860c8e7 9278 libsolv_0.7.27-2_source.buildinfo
Checksums-Sha256:
 a0f7914e3f3642f17cffdebfbb23dbdfd5a795c6e0e06cf68e9c2fcec86718ac 2449 
libsolv_0.7.27-2.dsc
 eeccdb05eb1264b787fb5ef132f43080210315d6f8742264bbfa77701246ffb3 19020 
libsolv_0.7.27-2.debian.tar.xz
 9377e3525c6dfa5df1fc7cd8ef0d47e771b37f1eeefbd48d193e804786dca4de 9278 
libsolv_0.7.27-2_source.buildinfo
Files:
 7e7019d6f59762f403e1c756740b6d0a 2449 admin optional libsolv_0.7.27-2.dsc
 9e4c38f71af07ea608edaaa9e71eac88 19020 admin optional 
libsolv_0.7.27-2.debian.tar.xz
 388147a9e896eb400ffeba3be81fda93 9278 admin optional 
libsolv_0.7.27-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmVxGIsRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB67tg//aVSDApp48rFhTxvHrRDdymGTBI89nSEA
CRnEtxe2M+JU7iuX4KH6PBjDAqouMVByU2sDGVjiKiVXhiq78vYGg1UMPtL4sib4
QP6otFI/fE+O+xq39YffMyVSog8ZBsvbHMXBdd3mnfm3PRYdpYgu/9cUyUhyaA6E
3Ge7MDBzpSVqZOHt62kc6Z4HBDgxOVdoOt7+qKNZKSS/G0HGtsSzKvAH8rBvFU6d
3PoEvtFC8Wj1T6H3KchzsesNnUcW2BvrBk9phXpMiol1obkD3KzLkIRP0xPKqXRE
FWs2pwkp7xPW2fm0P3J8cBNwNcBWbO2wi7KFtVIPrOV3kORRAjt2iJ/4VmnAGD4F
pU+NyKT4xPg3WyqczrYK0GQqb2xfBdVu6kk09lp0vH4ogWtCc5nMXJEaui9Uctb3
0obfNw2o8h6VXB4QECQefG32iqiiSRz5rInU6UaZNgrOouH+zdufQ6ehvIRUZcVj
k3xqYBJMQ7Q0/MVJoukgboqqY75ndXaE2rEzpxFmWd3wM62Z/wQqqozNQ9FFg2b8
8QFg5GwydR6VzLlYZ6YHZWE61j4JnH2FYQlXldx28j2bLJLljmTrNRp/Vsw6PW21
uO/fVG751iRYElKjzm5k3BxiDFCq8z+731V2rqLf5/0wCPLGut2tB9B5BTWS0ppf
bT29i8HHoI0=
=PuOu
-END PGP SIGNATURE End Message ---

Bug#1054156: librust-env-logger-0.7+default-dev shouldn't provide librust-env-logger+default-dev

[Peter Green]

On the one hand I'm not at all convinced this bug is rc, on the other
hand I don't think shipping a four year old version of env-logger
in the next release of Debian is a great idea.

So I decided to look at the reverse dependencies, I found three

safe-vdash - this is a Jonas package, the dependency on rust-env-logger-0.7 
seems bogus, I filed a bug.
rust-tracing-log - the new version no longer depends on env-logger, I updated 
it along with it's reverse dependency tracing-subscriber.
rspotify - this package is long term broken, noctis expressed an interest in 
fixing it back in January but I don't know what if-any progress he has made 
since then.

Bug#1011492: Additional information

[Vladimir Petko]

The relevant part of the build log
---
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/MetadataExtractor.java:[37,72]
package org.openxmlformats.schemas.officeDocument.x2006.customProperties
does not exist
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/MetadataExtractor.java:[38,74]
cannot find symbol
  symbol:   class CTProperties
  location: package
org.openxmlformats.schemas.officeDocument.x2006.extendedProperties
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[26,62]
cannot find symbol
  symbol:   class CTAbstractNum
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[27,62]
cannot find symbol
  symbol:   class CTDecimalNumber
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[28,62]
cannot find symbol
  symbol:   class CTLvl
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[29,62]
cannot find symbol
  symbol:   class CTNum
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[30,62]
cannot find symbol
  symbol:   class CTNumLvl
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[105,45]
cannot find symbol
  symbol:   class CTNum
  location: class org.apache.tika.parser.microsoft.ooxml.XWPFListManager
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[129,51]
cannot find symbol
  symbol:   class CTDecimalNumber
  location: class org.apache.tika.parser.microsoft.ooxml.XWPFListManager
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFListManager.java:[143,46]
cannot find symbol
  symbol:   class CTLvl
  location: class org.apache.tika.parser.microsoft.ooxml.XWPFListManager
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/RunProperties.java:[21,62]
cannot find symbol
  symbol:   class CTUnderline
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSSFExcelExtractorDecorator.java:[68,55]
cannot find symbol
  symbol:   class CTHyperlink
  location: package org.openxmlformats.schemas.drawingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSSFExcelExtractorDecorator.java:[69,55]
cannot find symbol
  symbol:   class CTNonVisualDrawingProps
  location: package org.openxmlformats.schemas.drawingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSSFExcelExtractorDecorator.java:[70,69]
cannot find symbol
  symbol:   class CTShape
  location: package
org.openxmlformats.schemas.drawingml.x2006.spreadsheetDrawing
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSSFExcelExtractorDecorator.java:[71,69]
cannot find symbol
  symbol:   class CTShapeNonVisual
  location: package
org.openxmlformats.schemas.drawingml.x2006.spreadsheetDrawing
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSSFExcelExtractorDecorator.java:[303,45]
cannot find symbol
  symbol:   class CTShape
  location: class
org.apache.tika.parser.microsoft.ooxml.XSSFExcelExtractorDecorator
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSLFPowerPointExtractorDecorator.java:[64,60]
cannot find symbol
  symbol:   class CTPicture
  location: package org.openxmlformats.schemas.presentationml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSLFPowerPointExtractorDecorator.java:[65,60]
cannot find symbol
  symbol:   class CTSlideIdList
  location: package org.openxmlformats.schemas.presentationml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XSLFPowerPointExtractorDecorator.java:[66,60]
cannot find symbol
  symbol:   class CTSlideIdListEntry
  location: package org.openxmlformats.schemas.presentationml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/microsoft/ooxml/XWPFWordExtractorDecorator.java:[65,62]
cannot find symbol
  symbol:   class CTBookmark
  location: package org.openxmlformats.schemas.wordprocessingml.x2006.main
[ERROR]
/<>/tika-parsers/src/main/java/org/apache/tika/parser/mic

Bug#1057438: raft: FTBFS: Reason: UndefinedError("'style' is undefined")

[Mathias Gibbens]

  Sphinx 7.0.0 dropped the `style` key
(https://github.com/sphinx-doc/sphinx/pull/11381). Version 7.2.6 was
uploaded to unstable early last month, causing this FTBFS.


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

Bug#832116: edgar: Source missing for some GPL licensed assets

[Alexandre Detiste]

Hi Matt,

It looks like Zorian is rightfully disgusted forever:
   https://contributors.debian.org/contributor/misterhat-guest@alioth/

I'm not scared of a handful .ogg files without the matching .wav files,
that's life, if these .ogg file were freely licensed as-is that's good enough.

I will give a new attempt at updating this game under
the Games Teams where bugs will get more visibility

Greetings,

Bug#1057671: cytadela: game include non free graphical assets

[Alexandre Detiste]

Package: cytadela
Version: 1.1.0-4+b1
Severity: serious
Justification: Policy 2.2.2.

Hi,

I'm currently reviewing all the games in contrib & non-free to see
wether game-data-packager can help to make them easier to install.


I'm surprised that cytadela is in contrib but doesn't try
to download anything and works from the go.

It should be either in "main" or in "non-free",
that just does not makes sense.


After digging out, I see that the graphical sprites
included upstream are a rip of from the original Amiga rom.

https://www.myabandonware.com/game/citadel-7ki
https://sourceforge.net/projects/cytadela/
https://sources.debian.org/src/cytadela/1.1.0-4/data/obj/

If this data-extraction were scriptable,
this engine would have to be stripped of the files
in data/obj/ and would then indeed perfectly fit in "contrib".

The game being mostly unmaintained I have little hope.

In the current state I think this package is
unfit for inclusion in Debian and should be removed.


Greetings,


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cytadela depends on:
ii  cytadela-data   1.1.0-4
ii  libc6   2.37-12
ii  libgcc-s1   13.2.0-7
ii  libgl1  1.7.0-1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libsdl-mixer1.2 1.2.12-17+b3
ii  libsdl1.2debian 1.2.68-1
ii  libstdc++6  13.2.0-7
ii  libvlc5 3.0.20-1+b1
ii  vlc-plugin-base 3.0.20-1+b1

cytadela recommends no packages.

cytadela suggests no packages.

-- no debconf information

Processed (with 1 error): raise severity of python3.12 issues

[Debian Bug Tracking System]

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

> severity 1055683 serious
Bug #1055683 [src:gtsam] gtsam b-d's on python3-all-dev, but only builds for 
the default python version
Severity set to 'serious' from 'important'
> severity 1055691 serious
Bug #1055691 [src:logbook] logbook ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> severity 1055693 serious
Bug #1055693 [src:mlpy] mlpy ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> version 1055686 0.1.8-2
Unknown command or malformed arguments to command.
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was d...@debian.org).
> usertag 1055686 python3.12
There were no usertags set.
Usertags are now: python3.12.
> thanks
Stopping processing here.

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

Bug#1057561: marked as done (gccintro: FTBFS: dh_installdocs: error: Cannot find (any matches for) "gccintro" (tried in ., debian/tmp))

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 22:35:02 +
with message-id 
and subject line Bug#1057561: fixed in gccintro 1.0-5
has caused the Debian Bug report #1057561,
regarding gccintro: FTBFS: dh_installdocs: error: Cannot find (any matches for) 
"gccintro" (tried in ., debian/tmp)
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.)


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

Package: src:gccintro
Version: 1.0-4
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
configure.ac:4: warning: AC_OUTPUT should be used without arguments.
configure.ac:4: You should run autoupdate.
Makefile.am: installing './COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your 
project uses
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
makeinfo gccintro.texi
makeinfo --html gccintro.texi
# next always return with ERROR, ths needs to use -
texi2pdf -b gccintro.texi
This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) 
(preloaded format=pdfetex)
 restricted \write18 enabled.
entering extended mode
(./gccintro.texi (/<>/texinfo.tex
Loading texinfo [version 2021-04-25.21]: pdf, fonts, glyphs, page headings,
tables, conditionals, indexing, sectioning, toc, environments, defuns, macros,
cross references, insertions, localization, formatting,
and turning on texinfo input format.) [1{/var/lib/texmf/fonts/map/pdftex/updmap
/pdftex.map}] [2] [-1] (/<>/rms.texi
(Foreword)) Chapter 1 [1]
Cross reference values unknown; you must run TeX again.
Writing index file gccintro.cp
[2] [3] Chapter 2 [4] (/<>/hello.c) [5]
(/<>/bad.c) [6]
(/<>/main.c)
(/<>/hello1.h)
(/<>/hello_fn.c) [7] [8]
(/<>/main2.c) [9]
(/<>/c1makefile2) [10] [11]
(/<>/calc.c) [12]
(/<>/badpow.c [13]) Chapter 3 [14]
(/<>/dbmain.c [15]) [16] [17] [18] [19]
[20] (/<>/ansi.c)
(/<>/pi.c) [21]
(/<>/gnuarray.c) [22] [23]
(/<>/main4.c) [24]
(/<>/w.c)
(/<>/wabs.c [25])
(/<>/shadow.c) [26]
(/<>/shadow2.c)
(/<>/castqual.c) [27] Chapter 4 [28]
(/<>/dtest.c) [29]
(/<>/dtestval.c)
(/<>/dtestval2.c [30])
(/<>/dtestval3.c)
(/<>/test.c [31])
(/<>/hello.c) [32] Chapter 5 [33]
(/<>/null.c) [34] [35] [36] [37] Chapter 6
[38] [39] [40] [41] [42] (/<>/optim.c [43])
[44] [45] (/<>/uninit.c) Chapter 7 [46]
(/<>/hello.cc) [47] [48]
(/<>/hellostr.cc)
(/<>/string.cc [49])
(/<>/buffer.h [50])
(/<>/tprog.cc [51])
(/<>/templates.cc) [52]
(/<>/templates2.cc) Chapter 8 [53]
(/<>/format.c) [54]
Overfull \hbox (20.69044pt too wide) in paragraph at lines 3944--3944
 []@texttt format.c:9:7: warning: format not a string literal and no format arg
uments[]
(/<>/bof.c
Overfull \hbox (26.43913pt too wide) in paragraph at lines 18--18
 [][]
) [55] [56] Chapter 9 [57] [58] (/<>/alpha.c
[59]) [60] [61] (/<>/setfpu.c)
(/<>/fptest2.c [62]) [63]
(/<>/signed.c)
(/<>/testgetc.c [64])
(/<>/testgetc2.c) Chapter 10 [65] [66]
(/<>/loop.c [67]) [68] Chapter 11 [69]
(/<>/hello_fn.c)
(/<>/bye_fn.c)
(/<>/hello.h) [70]
(/<>/main3.c) [71]
(/<>/collatz.c [72]) [73]
(/<>/cov.c) [74]
(/<>/cov_c_gcov) Chapter 12 [75]
(/<>/hello.c) [76] [77] Chapter 13 [78]
[79] [80] Chapter 14 [81] (/<>/msg-file.c)
(/<>/msg-nest1.h)
(/<>/msg-nest2.h)
(/<>/msg-invalidpp.c [82])
(/<>/msg-cppheader.c)
(/<>/msg-undeclared.c [83])
(/<>/msg-parse.c)
(/<>/msg-eoi.c)
(/<>/msg-implicitdecl.c [84])
(

Processed: Re: Bug#1057606: shim: FTBFS: ./debian/generate_dbx_list: 23: efisiglist: not found

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057606 [src:shim] shim: FTBFS: ./debian/generate_dbx_list: 23: 
efisiglist: not found
Added tag(s) pending.

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

Bug#1054747: marked as done (ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require 'pry-byebug')

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 22:22:36 +
with message-id 
and subject line Bug#1054747: fixed in ruby-pry-byebug 3.10.1-1
has caused the Debian Bug report #1054747,
regarding ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: 
require 'pry-byebug'
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.)


-- 
1054747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-octokit
Version: 4.20.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> Failure/Error: require 'pry-byebug'
> 
> Gem::MissingSpecError:
>   Could not find 'pry' (~> 0.13.0) among 122 total gem(s)
>   Checked in 
> 'GEM_PATH=/<>/debian/ruby-octokit/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /usr/share/rubygems-integration/all/specifications/pry-byebug-3.9.0.gemspec, 
> execute `gem env` for more information
> # ./spec/helper.rb:12:in `'
> # ./spec/octokit_spec.rb:1:in `'
> # --
> # --- Caused by: ---
> # LoadError:
> #   cannot load such file -- pry-byebug
> #   ./spec/helper.rb:12:in `'
> No examples found.
> 
> Finished in 0.6 seconds (files took 2.89 seconds to load)
> 0 examples, 0 failures, 66 errors occurred outside of examples
> 
> Coverage report generated for RSpec to /<>/coverage. 1360 / 7524 
> LOC (18.08%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has 
> been detected
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/ruby-octokit_4.20.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: ruby-pry-byebug
Source-Version: 3.10.1-1
Done: Vinay Keshava 

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

Debian distribution maintenance software
pp.
Vinay Keshava  (supplier of updated ruby-pry-byebug 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 24 Nov 2023 09:34:04 +0530
Source: ruby-pry-byebug
Architecture: source
Version: 3.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Vinay Keshava 
Closes: 1054747
Changes:
 ruby-pry-byebug (3.10.1-1) unstable; urgency=medium
 .
   [ Vinay Keshava ]
   * QA upload.
   * New upstream release. (Closes: #1054747)
   * use {ruby:Depends} & update versioned deps
   * update d/watch
   * Bump Standards-Version to 4.6.2 (no changes needed)
 .
   [ Miguel Landaeta ]
   *

Bug#1057606: shim: FTBFS: ./debian/generate_dbx_list: 23: efisiglist: not found

[Steve McIntyre]

Control: tag -1 pending

On Tue, Dec 05, 2023 at 11:11:17PM +0100, Santiago Vila wrote:
>Package: src:shim
>Version: 15.7-1
>Severity: serious
>Tags: ftbfs
>
>Dear maintainer:
>
>During a rebuild of all packages in unstable, your package failed to build:
>
>
>[...]
> debian/rules build
>dh build
>   dh_update_autotools_config
>   dh_autoreconf
>   dh_auto_configure
>   debian/rules override_dh_auto_build
>make[1]: Entering directory '/<>'
>./debian/generate_dbx_list x64 debian/debian-dbx.hashes dbx.esl
>  Adding 000f1547bb113601d65df9cb74ac62dd6d2ca85a0c2bb375c2f0ecedb59c84a4 to 
> dbx list
>./debian/generate_dbx_list: 23: efisiglist: not found
>make[1]: *** [debian/rules:52: dbx.esl] Error 127
>make[1]: Leaving directory '/<>'
>make: *** [debian/rules:64: build] Error 2
>dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
>
>
>The above is just how the build ends and not necessarily the most relevant 
>part.
>If required, the full build log is available here:

ACK, this is already known about. The pesign package no longer
provides efisiglist in unstable. I already have the necessary changes
made in shim in git, and we're due a new upload soon-ish.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
'There is some grim amusement in watching Pence try to run the typical
 "politician in the middle of a natural disaster" playbook, however
 incompetently, while Trump scribbles all over it in crayon and eats some
 of the pages.'   -- Russ Allbery

Bug#1031842: marked as done (xdg-desktop-portal-gnome: 44 appears incompatible with GNOME Shell 43)

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 21:40:00 +
with message-id 
and subject line Bug#1031842: fixed in xdg-desktop-portal-gnome 45.1-2
has caused the Debian Bug report #1031842,
regarding xdg-desktop-portal-gnome: 44 appears incompatible with GNOME Shell 43
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.)


-- 
1031842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Version: 44~beta-1
Severity: serious
Tags: trixie

It appears that xdg-desktop-portal-gnome 44 is incompatible with
mutter/gnome-shell 43.

https://launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/44~beta-1ubuntu1

GNOME Shell 43 uses libmutter-11-0 ; GNOME Shell 44 uses libmutter-12-0

Therefore, would it be correct to set an unversioned
Breaks: libmutter-11-0

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Source-Version: 45.1-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated xdg-desktop-portal-gnome 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Dec 2023 15:55:56 -0500
Source: xdg-desktop-portal-gnome
Built-For-Profiles: noudeb
Architecture: source
Version: 45.1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1031842
Launchpad-Bugs-Fixed: 1971168
Changes:
 xdg-desktop-portal-gnome (45.1-2) experimental; urgency=medium
 .
   [ Simon McVittie ]
   * Merge packaging changes from unstable
 - Require a version of GNOME Shell or Budgie based on libmutter-12
 .
 xdg-desktop-portal-gnome (45.1-1) experimental; urgency=medium
 .
   * New upstream release
   * Drop LP: #1971168 patch: applied in new release
 .
 xdg-desktop-portal-gnome (45.0-2) experimental; urgency=medium
 .
   * Stop using debian/control.in and dh_gnome_clean
   * Update remote file URIs patch with latest version accepted upstream
 .
 xdg-desktop-portal-gnome (44.2-3) unstable; urgency=medium
 .
   * Require a version of GNOME Shell or Budgie based on libmutter-12.
 This version of x-d-p-gnome does not work with GNOME 43 in bookworm.
 (Closes: #1031842)
 - Increase Recommends to gnome-shell 44~ or budgie-desktop 10.7.2-0.1~
 - Add Breaks on older versions
   * d/control.in, d/gbp.conf: Use debian/trixie packaging branch.
 The debian/latest branch is now in use for GNOME 45.
Checksums-Sha1:
 b80006a0d3a7131af8302b471afe6d5e94c3fee2 2482 
xdg-desktop-portal-gnome_45.1-2.dsc
 08966f84d4debab6fb635a7fcd63326b8394b133 140996 
xdg-desktop-portal-gnome_45.1.orig.tar.xz
 83c41c4f6d8f1e530b371be4b74f666a90fd81e6 4644 
xdg-desktop-portal-gnome_45.1-2.debian.tar.xz
 536e22c91172b33858f57e7b9c639d53163e3415 12657 
xdg-desktop-portal-gnome_45.1-2_source.buildinfo
Checksums-Sha256:
 d36b92834c9b654f53ee83496c61daafe5e1e1cfbf070e5d0d0b2c15912ece2a 2482 
xdg-desktop-portal-gnome_45.1-2.dsc
 3e9ca821044005fb37bd68ebe4ad196fc3d072835581467a22a4879dac7b5fdd 140996 
xdg-desktop-portal-gnome_45.1.orig.tar.xz
 aad2410e1dfa081ce531cf25226de37884af4c334697e6837466bfe0e3e4027d 4644 
xdg-desktop-portal-gnome_45.1-2.debian.tar.xz
 397c3d5236c68d9b9f5d2ccca495410d16abb49c2039f3dd149edd4c34ddc872 12657 
xdg-desktop-portal-gnome_45.1-2_source.buildinfo
Files:
 7d9ce4f13d8703e57109dc8701383df1 2482 gnome optional 
xdg-desktop-portal-gnome_45.1-2.dsc
 390b42a8a671ee20e280d69b1e2ae1c6 140996 gnome optional 
xdg-desktop-portal-gnome_45.1.orig.tar.xz
 19530d3a2e23d07982e54ec4ef1aac20 4644 gnome optional 
xdg-desktop-portal-gnome_45.1-2.debian.tar.xz
 64e04294031e54723f9fe451e6f3422f 12657 gnome optional 
xdg-desktop-portal-gnome_45.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmVw4C8ACgkQ5mx3Wuv+
bH0ybRAAwUEcUZyjRfhL9R0r5Gw3n+Yy1Rm4rj4MRInNnvfeYU6EFlHkxfBjAsOE
oahI7tJbpcWSfCIL6xSGGFMa4BCQ1uCboTDIfxsBT

Bug#1057665: python-mapnik: Segfault when importing with python3.12

[Bas Couwenberg]

Source: python-mapnik
Version: 1:0.0~20200224-7da019cf9-5
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

Importing the module with python3.12 results in a segfault:

 $ python3.12 -c 'import mapnik'
 Segmentation fault
 $ 

This does not happen with python3.11:

 $ python3.11 -c 'import mapnik'
 $ 

Backtrace:

 # gdb -args python3.12 -c 'import mapnik'
 GNU gdb (Debian 13.2-1) 13.2
 Copyright (C) 2023 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later 
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.
 Type "show copying" and "show warranty" for details.
 This GDB was configured as "x86_64-linux-gnu".
 Type "show configuration" for configuration details.
 For bug reporting instructions, please see:
 .
 Find the GDB manual and other documentation resources online at:
 .
 
 For help, type "help".
 Type "apropos word" to search for commands related to "word"...
 Reading symbols from python3.12...
 Reading symbols from 
/usr/lib/debug/.build-id/f0/4aa612852535800fe6d4b638c0e386059e2267.debug...
 (gdb) run
 Starting program: /usr/bin/python3.12 -c import\ mapnik
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
 
 Program received signal SIGSEGV, Segmentation fault.
 type_new_get_bases (type=, ctx=) at 
../Objects/typeobject.c:3834
 3834../Objects/typeobject.c: No such file or directory.
 (gdb) backtrace
 #0  type_new_get_bases (type=, ctx=) at 
../Objects/typeobject.c:3834
 #1  type_new (metatype=0x779f1300 , 
args=('Query', (0x0,), {'__module__': 'mapnik._mapnik', '__doc__': 'a spatial 
query data object'}), kwds=0x0) at ../Objects/typeobject.c:3914
 #2  0x0052cc35 in type_call (kwds=0x0, args=('Query', (0x0,), 
{'__module__': 'mapnik._mapnik', '__doc__': 'a spatial query data object'}), 
type=0x779f1300 )
 at ../Objects/typeobject.c:1661
 #3  _PyObject_MakeTpCall (tstate=0xbaf188 <_PyRuntime+459656>, callable=, args=, nargs=3, keywords=0x0) at 
../Objects/call.c:240
 #4  0x00501dc9 in _PyObject_CallFunctionVa (is_size_t=0, 
va=0x7fffcb00, format=, callable=, tstate=0xbaf188 <_PyRuntime+459656>) at ../Objects/call.c:556
 #5  PyEval_CallFunction (callable=, 
format=) at ../Objects/call.c:602
 #6  0x779ce503 in boost::python::call, boost::python::dict> 
(a0=@0x7fffcc40: 0x778d11aa "Query", a1=..., a2=..., 
 callable=) at ./boost/python/cast.hpp:87
 #7  
boost::python::api::object_operators::operator(), boost::python::dict> (a2=..., 
a1=..., a0=@0x7fffcc40: 0x778d11aa "Query", 
 this=0x7fffcc90) at ./boost/python/object_call.hpp:19
 #8  boost::python::objects::(anonymous namespace)::new_class 
(doc=0x778d118e "a spatial query data object", types=0x7fffce60, 
num_types=, name=0x778d11aa "Query") at 
libs/python/src/object/class.cpp:570
 #9  boost::python::objects::class_base::class_base (this=0x7fffcd40, 
name=0x778d11aa "Query", num_types=, types=0x7fffce60, 
doc=0x778d118e "a spatial query data object")
 at libs/python/src/object/class.cpp:586
 #10 0x77815512 in export_query() () from 
/usr/lib/python3/dist-packages/mapnik/_mapnik.cpython-312-x86_64-linux-gnu.so
 #11 0x77806e05 in init_module__mapnik() () from 
/usr/lib/python3/dist-packages/mapnik/_mapnik.cpython-312-x86_64-linux-gnu.so
 #12 0x779d78a3 in boost::function0::operator() 
(this=0x7fffd360) at ./boost/function/function_template.hpp:763
 #13 boost::python::handle_exception_impl (f=...) at 
libs/python/src/errors.cpp:25
 #14 0x779d80fc in boost::python::handle_exception 
(f=) at ./boost/python/errors.hpp:29
 #15 boost::python::detail::(anonymous namespace)::init_module_in_scope 
(init_function=0x77806cd0 , m=) at libs/python/src/module.cpp:24
 #16 boost::python::detail::init_module (moduledef=..., 
init_function=0x77806cd0 ) at 
libs/python/src/module.cpp:43
 #17 0x0066909f in _PyImport_LoadDynamicModuleWithSpec (fp=, 
 spec=, 
origin='/usr/lib/python3/dist-packages/mapnik/_mapnik.cpython-312-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, 
_uninitialized_submodules=[], _set_fileattr=True, _cached=None) at remote 
0x77ae4140>) at ../Python/importdl.c:169
 #18 _imp_create_dynamic_impl (module=, file=, 
 spec=, 
origin='/usr/lib/python3/dist-packages/mapnik/_mapnik.cpython-312-x86_64-linux-gnu.so',
 loader_state=None, submodule_search_locations=None, 
_uninitialized_submodules=[], _set_fileattr=True, _cached=None) at remote 
0x77ae4140>) at ../Python/import.c:3775
 #19 _imp_create_dynamic (module=, args=, 
nargs=) at ../Python/clinic/import.c.h:506
 #20 0x0056887e in cfunction_vectorcall

Processed: src:k3b: fails to migrate to testing for too long: new Build-Depends not available everywhere

[Debian Bug Tracking System]

Processing control commands:

> close -1 23.08.2-1
Bug #1057662 [src:k3b] src:k3b: fails to migrate to testing for too long: new 
Build-Depends not available everywhere
Marked as fixed in versions k3b/23.08.2-1.
Bug #1057662 [src:k3b] src:k3b: fails to migrate to testing for too long: new 
Build-Depends not available everywhere
Marked Bug as done

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

Bug#1057662: src:k3b: fails to migrate to testing for too long: new Build-Depends not available everywhere

[Paul Gevers]

Source: k3b
Version: 22.12.3-1
Severity: serious
Control: close -1 23.08.2-1
Tags: sid trixie
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 30 days as having a Release Critical bug in 
testing [1]. Your package src:k3b has been trying to migrate for 31 days 
[2]. Hence, I am filing this bug. The version in unstable has a new 
Build-Depends that's not available on armel, ppc64el and s390x. Please 
help the maintainer of qtwebengine5-dev to get that package available on 
those architectures, drop the Build-Depends or request the removal of 
your package on those architectures.


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 trixie, 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/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=k3b


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

[Paul Gevers]

Control: tags -1 - moreinfo

Hi Ben and the rest,

On 04-12-2023 15:10, Ben Hutchings wrote:

CPU: 6 PID: 15039 Comm: lxc-start Tainted: G  D WL 
6.5.0-0.deb12.1-arm64 #1  Debian 6.5.3-1~bpo12+1


The D and W flags mean there were prior BUG and WARN errors logged.
Please send those as well.


Please find attached the content of the journal since the reboot. I 
filtered out "debci".


Paul


kernel-bug-part0.log.xz
Description: application/xz


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #1057282 [src:linux] linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel 
upgrade makes systems unresponsive
Removed tag(s) moreinfo.

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

Bug#1057660: fastdtw: autopkgtest failure

[Adrian Bunk]

Source: fastdtw
Version: 0.3.4-2
Severity: serious

https://tracker.debian.org/pkg/fastdtw

Issues preventing migration:
∙ ∙ autopkgtest for fastdtw/0.3.4-2: amd64: Regression ♻ , arm64: Regression ♻ 
, armel: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: 
Regression ♻ , s390x: Regression ♻

...
48s autopkgtest [15:11:13]: test pybuild-autopkgtest: pybuild-autopkgtest
 48s autopkgtest [15:11:13]: test pybuild-autopkgtest: [---
 48s pybuild-autopkgtest
 49s I: pybuild base:310: python3.11 setup.py test 
 49s /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
Cython directive 'language_level' not set, using 2 for now (Py2). This will 
change in a later release! File: 
/tmp/autopkgtest-lxc.nv65t9ym/downtmp/build.LqL/src/fastdtw/_fastdtw.pyx
 49s   tree = Parsing.p_module(s, pxd, full_module_name)
 49s Compiling fastdtw/_fastdtw.pyx because it depends on 
/usr/lib/python3/dist-packages/Cython/Includes/numpy/math.pxd.
 49s [1/1] Cythonizing fastdtw/_fastdtw.pyx
 49s /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
_DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
 49s !!
 49s 
 49s 

 49s Requirements should be satisfied by a PEP 517 installer.
 49s If you are using pip, you can try `pip install --use-pep517`.
 49s 

 49s 
 49s !!
 49s   dist.fetch_build_eggs(dist.setup_requires)
 50s WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 50s WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 51s WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 53s WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 57s WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 'ProxyError('Cannot connect to 
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused'))': /simple/pytest-runner/
 57s ERROR: Could not find a version that satisfies the requirement 
pytest-runner (from versions: none)
 57s ERROR: No matching distribution found for pytest-runner
 57s Traceback (most recent call last):
 57s   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 101, 
in _fetch_build_egg_no_warn
 57s subprocess.check_call(cmd)
 57s   File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
 57s raise CalledProcessError(retcode, cmd)
 57s subprocess.CalledProcessError: Command '['/usr/bin/python3.11', '-m', 
'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
'/tmp/tmpx6wpjq2f', '--quiet', 'pytest-runner']' returned non-zero exit status 
1.
 57s 
 57s The above exception was the direct cause of the following exception:
 57s 
 57s Traceback (most recent call last):
 57s   File "/tmp/autopkgtest-lxc.nv65t9ym/downtmp/build.LqL/src/setup.py", 
line 81, in 
 57s setup(**kwargs)
 57s   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 106, 
in setup
 57s _install_setup_requires(attrs)
 57s   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 79, 
in _install_setup_requires
 57s _fetch_build_eggs(dist)
 57s   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 84, 
in _fetch_build_eggs
 57s dist.fetch_build_eggs(dist.setup_requires)
 57s   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 908, in 
fetch_build_eggs
 57s return _fetch_build_eggs(self, requires)
 57s^
 57s   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 38, 
in _fetch_build_eggs
 57s resolved_dists = pkg_resources.working_set.resolve(
 57s  ^^
 57s   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
829, in resolve
 57s dist = self._resolve_dist(
 57s^^^
 57s   File "/usr/lib/python3/dist-packages/pkg_res

Bug#1000006: parser: depends on obsolete pcre3 library

[Boyuan Yang]

X-Debbugs-CC: ya...@gnu.org

On Thu, 18 Nov 2021 11:49:06 + Matthew Vernon  wrote:
> Source: parser
> Severity: important
> User: matthew-pcre...@debian.org
> Usertags: obsolete-pcre3
> 
> Dear maintainer,
> 
> Your package still depends on the old, obsolete PCRE3[0] libraries
> (i.e. libpcre3-dev). This has been end of life for a while now, and
> upstream do not intend to fix any further bugs in it. Accordingly, I
> would like to remove the pcre3 libraries from Debian, preferably in
> time for the release of Bookworm.
> 
> The newer PCRE2 library was first released in 2015, and has been in
> Debian since stretch. Upstream's documentation for PCRE2 is available
> here: https://pcre.org/current/doc/html/
> 
> Many large projects that use PCRE have made the switch now (e.g. git,
> php); it does involve some work, but we are now at the stage where
> PCRE3 should not be used, particularly if it might ever be exposed to
> untrusted input.
> 
> This mass bug filing was discussed on debian-devel@ in
> https://lists.debian.org/debian-devel/2021/11/msg00176.html
> 
> Regards,
> 
> Matthew [0] Historical reasons mean that old PCRE is packaged as
> pcre3 in Debian 

I am aware of the work at https://bugs.debian.org/1057281 , but
unfortunately I am unable to review the patch at the moment. In order
to prevent the loss of the proposed patch, I am including it as an email
attachment here.

Thanks,
Boyuan Yang
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/106
Author: Yavor Doganov 
Forwarded: mailto:mail...@parser.ru
Last-Update: 2023-11-29
---

--- parser-3.4.6.orig/configure.ac
+++ parser-3.4.6/configure.ac
@@ -184,20 +184,20 @@
 	PCRE_INCLUDES="-I$PCRE/include"
 	PCRE_LIBS="$PCRE/lib/libpcre.la"
 
-	if test -f $PCRE/include/pcre.h -a -f $PCRE_LIBS; then
+	if test -f $PCRE/include/pcre2.h -a -f $PCRE_LIBS; then
 		PCRE_OK="yes"
 	else
-		PCRE_LIBS="-L$PCRE/lib -lpcre"
+		PCRE_LIBS="-L$PCRE/lib -lpcre2-8"
 	fi
 
 	if test "$PCRE" = "yes"; then
 		PCRE=""
-		PCRE_LIBS="-lpcre"
+		PCRE_LIBS="-lpcre2-8"
 		PCRE_INCLUDES=""
 		AC_MSG_WARN([--with-pcre value was not specified, hoping linker would find it])
 	fi
 ],[
-	PCRE_LIBS="-lpcre"
+	PCRE_LIBS="-lpcre2-8"
 	PCRE_INCLUDES=""
 	AC_MSG_WARN([--with-pcre was not specified, hoping linker would find it])
 ])
@@ -206,16 +206,21 @@
 	AC_MSG_CHECKING(for prce)
 	SAVE_LIBS=$LIBS
 	LIBS="$LIBS $PCRE_LIBS $PCRE_INCLUDES"
-	AC_TRY_LINK([ #include  ],[ const char *v=pcre_version(); ],
-		AC_MSG_RESULT(yes)
+	AC_LINK_IFELSE(
+  [AC_LANG_PROGRAM([[#define PCRE2_CODE_UNIT_WIDTH 8
+ #include ]],
+ [[uint32_t ov=16;
+   pcre2_match_data *md;
+   md=pcre2_match_data_create(ov, NULL);]])],
+	  [AC_MSG_RESULT([yes])]
 	,
-		AC_MSG_RESULT(no)
+	  [AC_MSG_RESULT([no])
 		if test -z "$PCRE"; then
 			AC_MSG_ERROR(please specify path to PCRE: --with-pcre=DIR)
 		else
 			AC_MSG_ERROR($PCRE does not seem to be valid PCRE installation directory)
 		fi
-	)
+	])
 	LIBS=$SAVE_LIBS
 fi
 
--- parser-3.4.6.orig/src/include/pa_charset.h
+++ parser-3.4.6/src/include/pa_charset.h
@@ -16,7 +16,8 @@
 #include "pa_hash.h"
 #include "pa_array.h"
 
-#include "pcre.h"
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 // we are using some pcre_internal.h stuff as well
 #include "../lib/pcre/pa_pcre_internal.h"
 
--- parser-3.4.6.orig/src/lib/pcre/pa_pcre_valid_utf8.c
+++ parser-3.4.6/src/lib/pcre/pa_pcre_valid_utf8.c
@@ -6,7 +6,8 @@
 and semantics are as close as possible to those of the Perl 5 language.
 
Written by Philip Hazel
-   Copyright (c) 1997-2012 University of Cambridge
+ Original API code Copyright (c) 1997-2012 University of Cambridge
+  New API code Copyright (c) 2016-2020 University of Cambridge
 
 -
 Redistribution and use in source and binary forms, with or without
@@ -38,112 +39,134 @@
 */
 
 
-/* This module contains an internal function for validating UTF-8 character
-strings. */
-
-#include "pcre.h"
+/* This module contains an internal function for validating UTF character
+strings. This file is also #included by the pcre2test program, which uses
+macros to change names from _pcre2_xxx to , thereby avoiding name clashes
+with the library. In this case, PCRE2_PCRE2TEST is defined. */
+
+#define SUPPORT_UNICODE
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #include "pa_pcre_internal.h"
 
+static const uint8_t utf8_table4[] = {
+  1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
+  1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,
+  2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,
+  3,3,3,3,3,3,3,3,4,4,4,4,5,5,5,5 };
+
+#ifndef SUPPORT_UNICODE
+/*
+*  Dummy function when Unicode is not supported  *
+*/
+
+/* This function should never be called when Unicode is not supported. */
+
+int
+PRIV(valid_utf)(PCRE2_SPTR string, PCRE2_SIZE leng

Bug#1055716: marked as done (python-mapnik ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 18:21:54 +
with message-id 
and subject line Bug#1055716: fixed in python-mapnik 1:0.0~20200224-7da019cf9-5
has caused the Debian Bug report #1055716,
regarding python-mapnik ftbfs with Python 3.12
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.)


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

Package: src:python-mapnik
Version: 1:0.0~20200224-7da019cf9-4
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-mapnik ftbfs with Python 3.12:

[...]
src/python_grid_utils.cpp: In function ‘void mapnik::grid2utf(const T&, 
boost::python::list&, std::vector&)’:
src/python_grid_utils.cpp:108:26: error: there are no arguments to 
‘PyUnicode_FromUnicode’ that depend on a template parameter, so a 
declaration of ‘PyUnicode_FromUnicode’ must be available [-fpermissive]
  108 |  PyUnicode_FromUnicode(line.get(), 
array_size;

  |  ^
src/python_grid_utils.cpp:108:26: note: (if you use ‘-fpermissive’, G++ 
will accept your code, but allowing the use of an undeclared name is 
deprecated)
src/python_grid_utils.cpp: In function ‘void mapnik::grid2utf(const T&, 
boost::python::list&, std::vector&, unsigned int)’:
src/python_grid_utils.cpp:171:26: error: there are no arguments to 
‘PyUnicode_FromUnicode’ that depend on a template parameter, so a 
declaration of ‘PyUnicode_FromUnicode’ must be available [-fpermissive]
  171 |  PyUnicode_FromUnicode(line.get(), 
array_size;

  |  ^
src/python_grid_utils.cpp: In function ‘void 
mapnik::write_features(const T&, boost::python::dict&, const 
std::vector&)’:
src/python_grid_utils.cpp:186:34: warning: declaration of ‘attributes’ 
shadows a global declaration [-Wshadow]
  186 | std::set const& attributes = 
grid_type.get_fields();

  |  ^~
In file included from /usr/include/mapnik/symbolizer_base.hpp:34,
 from /usr/include/mapnik/rule.hpp:28,
 from /usr/include/mapnik/grid/grid_renderer.hpp:31,
 from src/python_grid_utils.cpp:36:
/usr/include/mapnik/attribute.hpp:73:7: note: shadowed declaration is here
   73 | using attributes = std::unordered_map;
  |   ^~
src/python_grid_utils.cpp: In function ‘boost::python::dict 
mapnik::grid_encode(const T&, const std::string&, bool, unsigned int)’:
src/python_grid_utils.cpp:263:43: warning: declaration of ‘grid’ shadows 
a global declaration [-Wshadow]
  263 | boost::python::dict grid_encode( T const& grid, std::string 
const& format, bool add_features, unsigned int resolution)

  |  ~^~~~
In file included from /usr/include/mapnik/grid/grid_renderer.hpp:29:
/usr/include/mapnik/grid/grid.hpp:220:7: note: shadowed declaration is here
  220 | using grid = hit_grid;
  |   ^~~~
src/python_grid_utils.cpp: In function ‘void 
mapnik::render_layer_for_grid(const Map&, grid&, unsigned int, const 
boost::python::list&, double, unsigned int, unsigned int)’:
src/python_grid_utils.cpp:282:50: warning: declaration of ‘grid’ shadows 
a global declaration [-Wshadow]

  282 |   mapnik::grid & grid,
  |   ~~~^~~~
/usr/include/mapnik/grid/grid.hpp:220:7: note: shadowed declaration is here
  220 | using grid = hit_grid;
  |   ^~~~
src/python_grid_utils.cpp:315:27: warning: declaration of ‘attributes’ 
shadows a global declaration [-Wshadow]

  315 | std::set attributes = grid.get_fields();
  |   ^~
/usr/include/mapnik/attribute.hpp:73:7: note: shadowed declaration is here
   73 | using attributes = std::unordered_map;
  |   ^~
src/python_grid_utils.cpp: In instantiation of ‘void 
mapnik::grid2utf(const T&, boost::python::list&, std::vectorT::lookup_type>&, unsigned int) [with T = hit_grid; typename 
T::lookup_type = std::__cxx11::basic_string]’:
src/python_grid_utils.cpp:236:28:   required from ‘void 
mapnik::grid_encode_utf(const T&, boost::python::dict&, bool, unsigned 
int) [with T = hit_grid]’
src/python_grid_utils.cpp:267:27:   required from ‘boost::python::dict 
mapnik::grid_encode(const T&, const std::string&, bool, unsigned int) 
[with T = hit_grid; std::string = 
std::__cxx11::basic_string]’

src/python_grid_utils.cpp:278:138:   re

Processed: severity of 1055726 is serious

[Debian Bug Tracking System]

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

> severity 1055726 serious
Bug #1055726 [src:scikit-misc] scikit-misc ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1057575: marked as done (mailfromd: FTBFS: makeinfo: error parsing ./webdoc.init: Undefined subroutine &Texinfo::Config::set_from_init_file called at ./webdoc.init line 3.)

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 18:20:17 +
with message-id 
and subject line Bug#1057575: fixed in mailfromd 8.17.1-3
has caused the Debian Bug report #1057575,
regarding mailfromd: FTBFS: makeinfo: error parsing ./webdoc.init: Undefined 
subroutine &Texinfo::Config::set_from_init_file called at ./webdoc.init line 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.)


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

Package: src:mailfromd
Version: 8.17.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
tar cf debian/autoreconf.tar INSTALL Makefile.in aclocal.m4 \
build-aux/compile \
build-aux/depcomp build-aux/install-sh build-aux/mdate-sh \
build-aux/missing build-aux/texinfo.tex \
configure doc/Makefile.in elisp/Makefile.in etc/Makefile.in \
gacopyz/Makefile.in imprimatur/Makefile.in lib/Makefile.in \
mflib/Makefile.in mtasim/Makefile.in pmult/Makefile.in \
src/Makefile.in src/builtin/Makefile.in tests/Makefile.in \
doc/mailfromd.info doc/mailfromd.info-1 doc/mailfromd.info-2 \

[... snipped ...]


Underfull \hbox (badness 1) in paragraph at lines 472--484
@texttt org.  ua/  historic/  6/  html_node/  old_002dstyle-function-declaratio
ns.  html[]@textrm )[][]),

Underfull \hbox (badness 1) in paragraph at lines 472--484
@texttt mailfromd.  man.  gnu.  org.  ua/  historic/  6/  html_node/  implicit-
concatenation.  html[]@textrm )[][]),

Underfull \hbox (badness 1) in paragraph at lines 472--484
@textrm (@texttt http://  mailfromd.  man.  gnu.  org.  ua/  historic/  6/  htm
l_node/  Deprecated-Features.

Underfull \hbox (badness 1) in paragraph at lines 494--495
 @textrm See [][]$@textsy h$@textrm un-de-fined$@textsy i$ @textrm [scope of vi
s-i-bil-ity],
[291]
Overfull \hbox (204.64845pt too wide) in paragraph at lines 550--550
 []@texttt mailfromd: /etc/mailfromd.mf:7: warning: including a module file is
unreliable and may cause subtle errors[] |
[292] [293] [294] [295] [296] [297]) Appendix D [298]
(/<>/doc/fdl.texi [299] [300] [301]
[302] [303] [304]
Overfull \hbox (14.94176pt too wide) in paragraph at lines 421--421
 []  @texttt Texts.  A copy of the license is included in the section entitled
``GNU[] |
) (Concept Index) [305] [306]
No file mailfromd.cps.
[307] )
(see the transcript file for additional information)
Output written on mailfromd.pdf (315 pages, 1076921 bytes).
Transcript written on mailfromd.log.
This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) 
(preloaded format=pdfetex)
 restricted \write18 enabled.
entering extended mode
(/tmp/6zK6fRcSyc/manual!mailfromd.t2d/pdf/xtr/mailfromd.texi
(/<>/build-aux/texinfo.tex
Loading texinfo [version 2021-04-25.21]: pdf, fonts, glyphs, page headings,
tables, conditionals, indexing, sectioning, toc, environments, defuns, macros,
cross references, insertions, localization, formatting,
and turning on texinfo input format.)
Writing index file mailfromd.cp
(/<>/doc/version.texi)
(/<>/imprimatur/rendition.texi)
(/<>/doc/macros.texi)
(/<>/global.texi) [1{/var/lib/texmf/fonts/
map/pdftex/updmap/pdftex.map}] [2] [1] [2] (./mailfromd.toc) [-1] [-2]
(./mailfromd.toc [-3] [-4] [-5] [-6] [-7]) [-8] (./mailfromd.toc)
(./mailfromd.toc) (Preface) (./mailfromd.aux) [1] [2] Chapter 1 [3] [4]
[5] [6] [7] Chapter 2 [8] [9] [10] [11] [12] Chapter 3 [13] [14] [15] [16]
[17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31]
[32] [33] [34] [35]
Overfull \hbox (14.94176pt too wide) in paragraph at lines 3001--3001
 []@texttt gltime   num-ber 13  /etc/mailfromd.mfl:37,219,220,2
22,223[] |
[36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48]
Underfull \hbox (badness 1) in paragraph at lines 3964--3967
 @textrm trace0List calls to `@texttt spf_eval_record[]@textrm '[], `@texttt sp
f_test_record[]@textrm '[],
[49] [50] [51] [52] [53] Chapter 4 [54] [55] [56] [57] [58] [59] [60] [61]
[62] [63] [64]
Underfull \hbox (badness 1) in paragraph at lines 5275--5277
 []@textrm The fol-low-ing ex-am-ple uses @texttt __major__[] @textrm con-stant
 to de-ter-mine if some
[65] [66] [67] [68] [69] [70]
Overfull \hbox (6.3953pt too wide) in paragraph at lin

Processed: severity of 1055720 is serious

[Debian Bug Tracking System]

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

> severity 1055720 serious
Bug #1055720 [src:python-wheezy.template] python-wheezy.template ftbfs with 
Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055728 is serious

[Debian Bug Tracking System]

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

> severity 1055728 serious
Bug #1055728 [src:segyio] segyio ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055723 is serious

[Debian Bug Tracking System]

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

> severity 1055723 serious
Bug #1055723 [src:rocketcea] rocketcea ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055724 is serious

[Debian Bug Tracking System]

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

> severity 1055724 serious
Bug #1055724 [src:ruamel.yaml.clib] ruamel.yaml.clib ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055717 is serious

[Debian Bug Tracking System]

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

> severity 1055717 serious
Bug #1055717 [src:python-multidict] python-multidict ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055721 is serious

[Debian Bug Tracking System]

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

> severity 1055721 serious
Bug #1055721 [src:python-wordcloud] python-wordcloud ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055703 is serious

[Debian Bug Tracking System]

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

> severity 1055703 serious
Bug #1055703 [src:pyfftw] pyfftw ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055697 is serious

[Debian Bug Tracking System]

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

> severity 1055697 serious
Bug #1055697 [src:pivy] pivy ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1057654: zope.testrunner fails tests with Python 3.12

[Matthias Klose]

Package: src:zope.testrunner
Version: 6.2-1
Severity: serious
Tags: sid trixie
Forwarded: https://github.com/zopefoundation/zope.testrunner/issues/157
User: debian-pyt...@lists.debian.org
Usertags: python3.12

zope.testrunner fails tests with Python 3.12:

[...]
Failure in test 
/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-colors.rst

Failed doctest test for testrunner-colors.rst
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-colors.rst", 
line 0


--
File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-colors.rst", 
line 165, in testrunner-colors.rst

Failed example:
_ = testrunner.run_internal(defaults_skip)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.12/doctest.py", line 1359, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
_ = testrunner.run_internal(defaults_skip)
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/__init__.py", 
line 55, in run_internal

runner.run()
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 191, in run

self.run_tests()
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 292, in run_tests

self.ran += run_layer(self.options, layer_name, layer, tests,
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 473, in run_layer
return run_tests(options, tests, layer_name, failures, errors, 
skipped,
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 399, in run_tests

test(result)
  File "/usr/lib/python3.12/unittest/case.py", line 692, in __call__
return self.run(*args, **kwds)
  File "/usr/lib/python3.12/unittest/case.py", line 662, in run
result.stopTest(self)
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 1023, in stopTest

test.__dict__.update(self._test_state)
AttributeError: 'TestResult' object has no attribute '_test_state'



/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-simple.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-nestedcode.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-test-selection.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-verbose.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-repeat.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-knit.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-shuffle.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-stops-when-stop-on-error.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-new-threads.rst
 TestTrace (zope.testrunner.coverage)
 normalize_package (zope.testrunner.options)
 StartUpFailure (zope.testrunner.find)

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-gc.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-wo-source.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-profiling.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-profiling-cprofiler.rst

/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-report-skipped.rst

Failure in test 
/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-report-skipped.rst

Failed doctest test for testrunner-report-skipped.rst
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-report-skipped.rst", 
line 0


--
File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/tests/testrunner-report-skipped.rst", 
line 26, in testrunner-report-skipped.rst

Failed example:
testrunner.run_internal(defaults + ["-t", "TestSkipppedNoLayer"])
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.12/doctest.py", line 1359, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 


testrunner.run_internal(defaults + ["-t", "TestSkipppedNoLayer"])
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/__init__.py", 
line 55, in run_internal

runner.run()
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 191, in run

self.run_tests()
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 292, in run_tests

self.ran += run_layer(self.options, layer_name, layer, tests,
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 473, in run_layer
return run_tests(options, tests, layer_name, failures, errors, 
skipped,
  File 
"/<>/.pybuild/cpython3_3.12/build/zope/testrunner/runner.py", 
line 399, in run_tests

test(result)
  File "/usr/lib

Processed: severity of 1055713 is serious

[Debian Bug Tracking System]

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

> severity 1055713 serious
Bug #1055713 [src:python-http-parser] python-http-parser ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055714 is serious

[Debian Bug Tracking System]

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

> severity 1055714 serious
Bug #1055714 [src:python-jpype] python-jpype ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055710 is serious

[Debian Bug Tracking System]

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

> severity 1055710 serious
Bug #1055710 [src:python-cassandra-driver] python-cassandra-driver ftbfs with 
Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 1055716

[Debian Bug Tracking System]

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

> tags 1055716 + ftbfs
Bug #1055716 [src:python-mapnik] python-mapnik ftbfs with Python 3.12
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1055716 is serious

[Debian Bug Tracking System]

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

> severity 1055716 serious
Bug #1055716 [src:python-mapnik] python-mapnik ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055715 is serious

[Debian Bug Tracking System]

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

> severity 1055715 serious
Bug #1055715 [src:python-line-profiler] python-line-profiler ftbfs with Python 
3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#1057553: dosbox: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + trixie sid patch
Bug #1057553 [src:dosbox] dosbox: FTBFS: error: invalid use of incomplete type 
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch, sid, and trixie.

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

Bug#1057553: dosbox: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

[Sven Joachim]

Control: tags -1 + trixie sid patch

On 2023-12-05 23:04 +0100, Santiago Vila wrote:

> Package: src:dosbox
> Version: 0.74-3-4
> Severity: serious
> Tags: ftbfs
>
> During a rebuild of all packages in unstable, your package failed to build:
> In file included from ../../../src/debug/debug_gui.cpp:28:
> ../../../src/debug/debug_gui.cpp: In function ‘void DrawBars()’:
> ../../../src/debug/debug_gui.cpp:149:29: error: invalid use of incomplete 
> type ‘WINDOW’ {aka ‘struct _win_st’}
>   149 | mvaddstr(dbg.win_reg->_begy-1,0, "---(Register Overview   
> )---");
>   | ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> ../../../src/debug/debug_gui.cpp:151:30: error: invalid use of incomplete 
> type ‘WINDOW’ {aka ‘struct _win_st’}
>   151 | mvaddstr(dbg.win_data->_begy-1,0,"---(Data Overview   Scroll: 
> page up/down)---");
>   |  ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> ../../../src/debug/debug_gui.cpp:153:30: error: invalid use of incomplete 
> type ‘WINDOW’ {aka ‘struct _win_st’}
>   153 | mvaddstr(dbg.win_code->_begy-1,0,"---(Code Overview   Scroll: 
> up/down )---");
>   |  ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> ../../../src/debug/debug_gui.cpp:155:29: error: invalid use of incomplete 
> type ‘WINDOW’ {aka ‘struct _win_st’}
>   155 | mvaddstr(dbg.win_var->_begy-1,0, "---(Variable Overview   
> )---");
>   | ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> ../../../src/debug/debug_gui.cpp:157:29: error: invalid use of incomplete 
> type ‘WINDOW’ {aka ‘struct _win_st’}
>   157 | mvaddstr(dbg.win_out->_begy-1,0, "---(OutPut/InputScroll: 
> home/end)---");
>   | ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   442 | typedef struct _win_st WINDOW;
>   |^~~
> make[5]: *** [Makefile:358: debug_gui.o] Error 1

I have left out the gazillion of string format warnings, the above
messages are the only actual errors making the build fail.

They have been caused by a recent change in ncurses which makes the
WINDOW structure opaque.  Accessing its members directly is no longer
possible, you need to use library functions to obtain window dimensions
and positions.  In the current case, this would be getbegy(), see the
attached patch.  I have only tested that it builds, though,

See the ncurses INSTALL file:

,
| --enable-opaque-curses
| --enable-opaque-form
| --enable-opaque-menu
| --enable-opaque-panel
|   Define symbol in curses.h controlling whether some library structures
|   are opaque, meaning that their members are accessible only via the
|   documented API.  The --enable-opaque-curses option may be overridden
|   by the --enable-reentrant option.
| 
|   Enabling opaque-curses enables opaque for the form, menu, and panel
|   libraries.  Use their corresponding options to disable the feature
|   individually.
| 
|   NOTE: beginning with ncurses 6.5 this option is enabled by default;
|   older versions disable it by default.
`

While ncurses 6.5 has not been released yet, the change has already been
made in the patchlevel Debian is shipping.  From the NEWS file:

,
| 20231021
|   + change defaults for configure opaque and widec options (prompted by
| discussion with Branden Robinson).
`

Cheers,
   Sven (ncurses maintainer in Debian)

From ab9fe80d94d35d10109ee4899de7b37eeab474eb Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 6 Dec 2023 17:49:05 +0100
Subject: [PATCH] Use getbegy() rather than accessing window structures
 directly

---
 src/debug/debug_gui.cpp | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/debug/debug_gui.cpp b/src/debug/debug_gui.cpp
index fc9f1ca..53743e3 100644
--- a/src/debug/debug_gui.cpp
+++ b/src/debug/debug_gui.cpp
@@ -146,15 +146,15 @@ static void DrawBars(void) {
 		attrset(COLOR_PAIR(PAIR_BLACK_BLUE));
 	}
 	/* Show the Register bar */
-	mvaddstr(dbg.win_reg->_begy-1,0, "---(Register Overview   )---");
+	mvaddstr(getbegy(dbg.win_reg)-1,0, "---(Register Overview   )---");
 	/* Show the Data Overview bar perhaps with more special stuff in the end */
-	mvaddstr(dbg.win_data->_begy-1,0,"---(Data Overview   Scro

Bug#1057652: libghc-base64-dev: Segfaults on 32-bit architectures

[Ilias Tsitsimpis]

Package: libghc-base64-dev
Version: 0.4.2.4-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Forwarded: https://github.com/emilypi/base64/issues/56

This library segfaults on 32-bit architectures. The testsuite fails as
well, but unfortunately is not enabled in Debian because of a missing
build-dependency.

For more information, see the upstream bug report
https://github.com/emilypi/base64/issues/56.

-- 
Ilias

Bug#1057162: marked as done (jglobus: FTBFS with bouncycastle 1.77)

[Debian Bug Tracking System]

Your message dated Wed, 06 Dec 2023 16:34:32 +
with message-id 
and subject line Bug#1057162: fixed in jglobus 2.1.0-9
has caused the Debian Bug report #1057162,
regarding jglobus: FTBFS with bouncycastle 1.77
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.)


-- 
1057162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jglobus
Version: 2.1.0-8.1
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

jglobus fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.

[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/<>/ssl-proxies/src/main/java/org/globus/gsi/proxy/ext/ProxyPolicy.java:[63,46]
 cannot find symbol
  symbol:   method getObject()
  location: class org.bouncycastle.asn1.DERTaggedObject
[INFO] 1 error
--- End Message ---
--- Begin Message ---
Source: jglobus
Source-Version: 2.1.0-9
Done: Mattias Ellert 

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated jglobus 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Dec 2023 13:45:57 +0100
Source: jglobus
Architecture: source
Version: 2.1.0-9
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Closes: 1057162
Changes:
 jglobus (2.1.0-9) unstable; urgency=medium
 .
   * Adapt to changes in bouncycastle 1.77 (Closes: #1057162)
Checksums-Sha1:
 4c3339db69a3b57f462a054bf88e1e6a45cb7cba 2792 jglobus_2.1.0-9.dsc
 bd7df429c4f38d20464d414471c3fab18c9ee6a4 23496 jglobus_2.1.0-9.debian.tar.xz
 3ee5e8a440c991bb95f9baa294c8b9b9065b8b0c 14339 jglobus_2.1.0-9_amd64.buildinfo
Checksums-Sha256:
 42326fa8898d6c13dba23e9eb151172b538121df7518b60b0c92a3328f514a25 2792 
jglobus_2.1.0-9.dsc
 ad9228839ab5f8e2e400173497da0198d2ccce6bcddabe2f215a5c218d005525 23496 
jglobus_2.1.0-9.debian.tar.xz
 0a7e0e5efa8a412982ea9348003314dc3c4be5636e59c5f1fe3441e1ac4cd84b 14339 
jglobus_2.1.0-9_amd64.buildinfo
Files:
 2a4a5f1a297bf4723a274f76eca8a159 2792 java optional jglobus_2.1.0-9.dsc
 2689857141787c35ab5568954be560a5 23496 java optional 
jglobus_2.1.0-9.debian.tar.xz
 307523d13590d4e348129e93adda3a59 14339 java optional 
jglobus_2.1.0-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6hgwr99NQxrZ4RRS6K7C/zvhqUsFAmVwnpkACgkQ6K7C/zvh
qUucgQ//apZ5H2rcoPdDVEhafui2n1+hwJNQTNSUBpbCvt8B99VDUh+c1qPiIQmc
aqIX6VineB5fqliECHh0Jb0xjQ+JVUDbDOcAGQE4lRCXJT9oipvfzyvwNVtwK8KH
KHQAj+BSvj2BUiWMEpNZj0TdkK4Wv3udFGW272t6zB//EoAgvR0Y/15bLnITE/bZ
QzKHjNVFscfJbWQLm20kXPLschWdGhF9hSh2MeqnVk+S/ImAeebSfytP6sELNUuF
vK4oBMqxpNY93pjULlP4IjEzQ8jiEsbRPprzO+ozQRdYUUOCdIG+h+3r+6fuH18X
vn2XtFT4UDxyupWeFjuVVdwJUbrb3zZui4W5uJKWf3IengK148ADefx/7VOjvy/7
uiTee4EQMSfGsdnC2xIx5VM0AIrQZ5XnqvZ3L8otsGH4NShDfXv4asJ/DeRWnNxE
T7mzvQROHqmSYFMdw7q6gtjf2k07WwN+1e1UQWV+Uh3VkD/WPS3vpn4PRZmk3mFY
mJtcqlSZ4Qt4MjCRbB88pgi3lWysc6mHV29IjZiv0ja9X5oXxuWfUmmoShIFk3cv
6RzGXqx1eC0QZXwwybR1RxMa8EGQM8jMcp/0jLz4k9xR5hzj5AJpl4AFphTnb8A4
NsZNy4B7xtOppufz7tO7IVyYAaxkbs1rjF1tD7aZ+R2pe1QPtQo=
=rVb6
-END PGP SIGNATURE End Message ---

Processed: severity of 1055690 is serious

[Debian Bug Tracking System]

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

> severity 1055690 serious
Bug #1055690 [src:libgpuarray] libgpuarray ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055707 is serious

[Debian Bug Tracking System]

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

> severity 1055707 serious
Bug #1055707 [src:python-acora] python-acora fbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055701 is serious

[Debian Bug Tracking System]

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

> severity 1055701 serious
Bug #1055701 [src:pycifrw] pycifrw ftbfs with Python 3.12 (test failures)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 1055698

[Debian Bug Tracking System]

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

> tags 1055698 + ftbfs
Bug #1055698 [src:py-ubjson] py-ubjson ftbfs with Python 3.12 (test failures)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1031465: marked as done (snippy: FTBFS: make[2]: *** [Makefile:32: S1/snps.tab] Error 2)

[Debian Bug Tracking System]

Your message dated Wed, 6 Dec 2023 21:29:42 +0530
with message-id <20231206155942.eonflqgtdtpnv...@office.mailbox.org>
and subject line [FIXED] snippy: FTBFS: make[2]: *** [Makefile:32: S1/snps.tab] 
Error 2
has caused the Debian Bug report #1031465,
regarding snippy: FTBFS: make[2]: *** [Makefile:32: S1/snps.tab] Error 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.)


-- 
1031465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snippy
Version: 4.6.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/test'
> mkdir -p S1
> wgsim -S 1 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S1/R2.fq S1/R1.fq > S1/dwgsim.tab
> [wgsim] seed = 1
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S2
> wgsim -S 2 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S2/R2.fq S2/R1.fq > S2/dwgsim.tab
> [wgsim] seed = 2
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S3
> wgsim -S 3 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S3/R2.fq S3/R1.fq > S3/dwgsim.tab
> [wgsim] seed = 3
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S4
> wgsim -S 4 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S4/R2.fq S4/R1.fq > S4/dwgsim.tab
> [wgsim] seed = 4
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> ../bin/snippy --cpus 2 --ram 2 --force --ref example.fna --outdir S1 --R1 
> S1/R1.fq --R2 S1/R2.fq
> [01:21:32] This is snippy 4.6.0
> [01:21:32] Written by Torsten Seemann
> [01:21:32] Obtained from https://github.com/tseemann/snippy
> [01:21:32] Detected operating system: linux
> [01:21:32] Enabling bundled linux tools.
> [01:21:32] Found bwa - /usr/bin/bwa
> [01:21:32] Found bcftools - /usr/bin/bcftools
> [01:21:32] Found samtools - /usr/bin/samtools
> [01:21:32] Found java - /usr/bin/java
> [01:21:32] Found snpEff - /usr/bin/snpEff
> [01:21:32] Found samclip - /usr/bin/samclip
> [01:21:32] Found seqtk - /usr/bin/seqtk
> [01:21:32] Found parallel - /usr/bin/parallel
> [01:21:32] Found freebayes - /usr/bin/freebayes
> [01:21:32] Found freebayes-parallel - 
> /usr/share/freebayes/scripts/freebayes-parallel
> [01:21:32] Found fasta_generate_regions.py - 
> /usr/share/freebayes/scripts/fasta_generate_regions.py
> [01:21:32] Found vcfstreamsort - /usr/bin/vcfstreamsort
> [01:21:32] Found vcfuniq - /usr/bin/vcfuniq
> [01:21:32] Found vcffirstheader - /usr/share/freebayes/scripts/vcffirstheader
> [01:21:32] Found gzip - /bin/gzip
> [01:21:32] Found vt - /usr/bin/vt
> [01:21:32] Found snippy-vcf_to_tab - /<>/bin/snippy-vcf_to_tab
> [01:21:32] Found snippy-vcf_report - /<>/bin/snippy-vcf_report
> [01:21:32] Checking version: samtools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Checking version: bcftools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Need freebayes --version >= 1.1 but you have 0 - please upgrade it.
> make[2]: *** [Makefile:32: S1/snps.tab] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/snippy_4.6.0+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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 ---
This seems fixed and is not reproducible anymore. Closing.

Best,
Nilesh


signature.asc
Description: PGP 

Processed: forcibly merging 1055688 1055544

[Debian Bug Tracking System]

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

> forcemerge 1055688 1055544
Bug #1055688 [src:libgetdata] libgetdata ftbfs with Python 3.12 as supported 
Python version
Bug #1055544 [src:libgetdata] libgetdata hardcodes specific python versions in 
the packaging
Severity set to 'serious' from 'important'
The source libgetdata and version 0.11-0-7 do not appear to match any binary 
packages
Marked as found in versions libgetdata/0.11.0-7.
Added tag(s) ftbfs.
Bug #1055688 [src:libgetdata] libgetdata ftbfs with Python 3.12 as supported 
Python version
The source libgetdata and version 0.11-0-7 do not appear to match any binary 
packages
Marked as found in versions libgetdata/0.11-0-7.
Merged 1055544 1055688
> thanks
Stopping processing here.

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

Bug#1057567: libconfig-model-lcdproc-perl: FTBFS: Cannot determine local time zone

[gregor herrmann]

On Wed, 06 Dec 2023 13:17:09 +0100, gregor herrmann wrote:

> On Wed, 06 Dec 2023 12:52:15 +0100, Dominique Dumont wrote:
> > On Tuesday, 5 December 2023 23:06:12 CET you wrote:
> > > Wrote documentation in lib/Config/Model/models/LCDd/yard2LCD.pod
> > > Cannot determine local time zone
> > > [DZ] beginning to build Config-Model-LcdProc
> > I've seen this error from time to time. I don't know the exact algorithm 
> > used 
> > to determine the time zone, but usually, setting TZ to an appropriate value 
> > fixed this issue.

> My suspicion/idea was that it might be useful to have
> libdatetime-timezone-perl depend on tzdata (now that tzdata is not
> essential (or whatever it was) any more), as
> libdatetime-timezone-perl seems to be involved in alle of the bug
> reports …

"Cannot determine local time zone" is an exception thrown by
DateTime::TimeZone::Local which uses DateTime::TimeZone::Local::Unix
which checks the TZ env variable and /etc/localtime /etc/timezone
/etc/TIMEZONE /etc/sysconfig/clock /etc/default/init.

(Cf. the docs for DateTime::TimeZone, DateTime::TimeZone::Local, and
DateTime::TimeZone::Local::Unix.)

So it seems that DateTime::TimeZone will fail for the "local
timezone" when neither TZ is set nor any of the files is present. In
our case I looks like both /etc/localtime and /etc/timezone are
related to tzdata('s .postinst and/or .config), so I think the point
for making libdatetime-timezone-perl depend on tzdata by itself gets
stronger, which would en passant fix the test failures in the other
packages.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: tagging 1055705

[Debian Bug Tracking System]

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

> tags 1055705 - ftbfs
Bug #1055705 [src:pyreadstat] pyreadstat ftbfs with Python 3.12
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 1055705

[Debian Bug Tracking System]

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

> tags 1055705 + ftbfs
Bug #1055705 [src:pyreadstat] pyreadstat ftbfs with Python 3.12
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1055705 is serious

[Debian Bug Tracking System]

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

> severity 1055705 serious
Bug #1055705 [src:pyreadstat] pyreadstat ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1055692 is serious

[Debian Bug Tracking System]

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

> severity 1055692 serious
Bug #1055692 [src:macs] macs ftbfs with Python 3.12
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1055692

[Debian Bug Tracking System]

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

> tags 1055692 + ftbfs trixie sid
Bug #1055692 [src:macs] macs ftbfs with Python 3.12
Added tag(s) trixie, sid, and ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 1055688

[Debian Bug Tracking System]

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

> tags 1055688 + ftbfs
Bug #1055688 [src:libgetdata] libgetdata ftbfs with Python 3.12 as supported 
Python version
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1055688 is serious

[Debian Bug Tracking System]

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

> severity 1055688 serious
Bug #1055688 [src:libgetdata] libgetdata ftbfs with Python 3.12 as supported 
Python version
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1000044: ccze: depends on obsolete pcre3 library

[Yavor Doganov]

On Mon, 04 Dec 2023 15:46:29 +0200,
Yavor Doganov wrote:
> I guess I need to revisit my patch and find some way to fix this.

Here it is -- no memory leaks and I could not obtain crash or abort
with the logs I've tested.  Note that while my original patch
introduced some leaks, it also fixes some in the original code.

Tested the following plugins: dpkg, exim, httpd, procmail, sulog and
syslog (yours and mine).  Also compared the output between version -7
and git master + this new patch.

Please test extensively and let me know if something is wrong.

You may wish to apply (or not) two additional patches: 1 memory leak
that I discovered with aptitude/Xorg logs and 1 uninitialized value
(reported by valgrind as error).
>From 475cbc072cb08bd6a57befa6c3856f8458355b1b Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Wed, 6 Dec 2023 15:07:25 +0200
Subject: [PATCH] pcre2.patch: Fix some memory leaks

---
 debian/patches/pcre2.patch | 181 +
 1 file changed, 125 insertions(+), 56 deletions(-)

diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 6b60dc8..4014fc3 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -2,7 +2,7 @@ Description: Port to PCRE2.
 Bug-Debian: https://bugs.debian.org/144
 Author: Yavor Doganov 
 Forwarded: no
-Last-Update: 2023-12-03
+Last-Update: 2023-12-06
 ---
 
 --- ccze.orig/configure.ac
@@ -39,7 +39,7 @@ Last-Update: 2023-12-03
  
  static char *words_bad[] = {
"warn", "restart", "exit", "stop", "end", "shutting", "down", "close",
-@@ -71,33 +71,31 @@
+@@ -71,34 +71,35 @@
  void
  ccze_wordcolor_process_one (char *word, int slookup)
  {
@@ -48,8 +48,9 @@ Last-Update: 2023-12-03
 +  size_t wlen, l;
ccze_color_t col;
 -  int match, printed = 0;
+-  char *pre = NULL, *post = NULL, *tmp, *lword;
 +  int printed = 0;
-   char *pre = NULL, *post = NULL, *tmp, *lword;
++  char *pre = NULL, *post = NULL, *tmp = NULL, *lword;
 +  pcre2_match_data *offsets;
  
col = CCZE_COLOR_DEFAULT;
@@ -63,10 +64,11 @@ Last-Update: 2023-12-03
  {
 -  pcre_get_substring (word, offsets, match, 1, (const char **)&pre);
 -  pcre_get_substring (word, offsets, match, 2, (const char **)&tmp);
--  free (word);
 +  pcre2_substring_get_bynumber (offsets, 1, (unsigned char **)&pre, &l);
 +  pcre2_substring_get_bynumber (offsets, 2, (unsigned char **)&tmp, &l);
-   word = tmp;
+   free (word);
+-  word = tmp;
++  word = strdup (tmp);
  }
else
  pre = NULL;
@@ -78,13 +80,16 @@ Last-Update: 2023-12-03
  {
 -  pcre_get_substring (word, offsets, match, 1, (const char **)&tmp);
 -  pcre_get_substring (word, offsets, match, 2, (const char **)&post);
--  free (word);
++  pcre2_substring_free (tmp);
 +  pcre2_substring_get_bynumber (offsets, 1, (unsigned char **)&tmp, &l);
 +  pcre2_substring_get_bynumber (offsets, 2, (unsigned char **)&post, &l);
-   word = tmp;
+   free (word);
+-  word = tmp;
++  word = strdup (tmp);
  }
else
-@@ -107,45 +105,45 @@
+ post = NULL;
+@@ -107,45 +108,45 @@
lword = _stolower (word);

/** Host **/
@@ -144,20 +149,20 @@ Last-Update: 2023-12-03
  {
char *host, *ip;
size_t hostlen, iplen;
-@@ -206,9 +204,9 @@
- }
+@@ -207,8 +208,10 @@

free (lword);
--  free (word);
+   free (word);
 -  free (post);
 -  free (pre);
++  pcre2_substring_free (tmp);
 +  pcre2_substring_free (post);
 +  pcre2_substring_free (pre);
 +  pcre2_match_data_free (offsets);
  }
  
  void
-@@ -260,64 +258,67 @@
+@@ -260,64 +263,67 @@
  void
  ccze_wordcolor_setup (void)
  {
@@ -305,7 +310,8 @@ Last-Update: 2023-12-03
 +ccze_apm_process (pcre2_match_data *offsets)
  {
char *battery, *charge, *rate, *stuff1, *elapsed, *remain;
-   char *stuff2;
+-  char *stuff2;
++  char *stuff2, *ret;
 +  size_t l;

 -  pcre_get_substring (str, offsets, match, 1, (const char **)&battery);
@@ -325,7 +331,7 @@ Last-Update: 2023-12-03
  
ccze_addstr (CCZE_COLOR_DEFAULT, "Battery:");
ccze_space ();
-@@ -62,12 +63,12 @@
+@@ -62,48 +63,54 @@
ccze_addstr (CCZE_COLOR_DATE, remain);
ccze_space ();
  
@@ -335,16 +341,19 @@ Last-Update: 2023-12-03
 -  free (stuff1);
 -  free (elapsed);
 -  free (remain);
++  ret = strdup (stuff2);
 +  pcre2_substring_free (battery);
 +  pcre2_substring_free (charge);
 +  pcre2_substring_free (rate);
 +  pcre2_substring_free (stuff1);
 +  pcre2_substring_free (elapsed);
 +  pcre2_substring_free (remain);
++  pcre2_substring_free (stuff2);

-   return stuff2;
+-  return stuff2;
++  return ret;
  }
-@@ -75,35 +76,39 @@
+ 
  static void
  ccze_apm_setup (void)
  {
@@ -408,7 +417,8 @@ Last-Update: 2023-12-03
 -ccze_distcc_process (const char *str, int *offsets, int match)
 +ccze_distcc_process (pcre2_match_data *offsets)
  {
-   char *pid, *func, *rest;
+-  char *pid, *func, *rest;
++  char *pid, *func, *rest, *ret;
 +  size_t l;
  
 -  p

Processed: closing 1055685

[Debian Bug Tracking System]

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

> close 1055685 0.5.5-1~exp1
Bug #1055685 [src:compreffor] compreffor ftbfs with Python 3.12
Marked as fixed in versions compreffor/0.5.5-1~exp1.
Bug #1055685 [src:compreffor] compreffor ftbfs with Python 3.12
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: severity of 1055685 is serious

[Debian Bug Tracking System]

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

> severity 1055685 serious
Bug #1055685 [src:compreffor] compreffor ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: closing 1055718

[Debian Bug Tracking System]

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

> close 1055718 0.3.1-1~exp1
Bug #1055718 [src:python-openstep-plist] python-openstep-plist ftbfs with 
Python 3.12
Marked as fixed in versions python-openstep-plist/0.3.1-1~exp1.
Bug #1055718 [src:python-openstep-plist] python-openstep-plist ftbfs with 
Python 3.12
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: severity of 1055718 is serious

[Debian Bug Tracking System]

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

> severity 1055718 serious
Bug #1055718 [src:python-openstep-plist] python-openstep-plist ftbfs with 
Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 1055686

[Debian Bug Tracking System]

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

> tags 1055686 + ftbfs trixie sid
Bug #1055686 [src:dm-tree] dm-tree ftbfs with Python 3.12
Added tag(s) sid, ftbfs, and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1055686 is serious

[Debian Bug Tracking System]

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

> severity 1055686 serious
Bug #1055686 [src:dm-tree] dm-tree ftbfs with Python 3.12
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1055684 is serious

[Debian Bug Tracking System]

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

> severity 1055684 serious
Bug #1055684 [src:beancount] beancount fails tests with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1057567: libconfig-model-lcdproc-perl: FTBFS: Cannot determine local time zone

[Santiago Vila]

El 6/12/23 a las 12:52, Dominique Dumont escribió:

On Tuesday, 5 December 2023 23:06:12 CET you wrote:

Wrote documentation in lib/Config/Model/models/LCDd/yard2LCD.pod Cannot
determine local time zone
[DZ] beginning to build Config-Model-LcdProc


I've seen this error from time to time. I don't know the exact algorithm used
to determine the time zone, but usually, setting TZ to an appropriate value
fixed this issue.

Could you check the config of your build deamon and add such a variable ?


Hi. Before that: This one, most probably, happens because of a missing
Build-Depends on tzdata.

So, to reproduce, please make sure your chroot has been created with debootstrap
in trixie/sid, since tzdata is not build-essential. Previously, debootstrap
installed all required packages (no matter what), which made bugs like this
one to be hidden (see #837060 for details).

However, as Gregor points out, the missing build-dependency (if that's really
the reason for the build failure) may be added either directly or indirectly
by making libdatetime-timezone-perl to binary-depend on tzdata. Given
the package name, it makes sense.

Thanks.

Bug#1057567: libconfig-model-lcdproc-perl: FTBFS: Cannot determine local time zone

[gregor herrmann]

On Wed, 06 Dec 2023 12:52:15 +0100, Dominique Dumont wrote:

> On Tuesday, 5 December 2023 23:06:12 CET you wrote:
> > Wrote documentation in lib/Config/Model/models/LCDd/yard2LCD.pod Cannot
> > determine local time zone
> > [DZ] beginning to build Config-Model-LcdProc
> I've seen this error from time to time. I don't know the exact algorithm used 
> to determine the time zone, but usually, setting TZ to an appropriate value 
> fixed this issue.

I had a brief look on some of the bugs yesterday; I could reproduce
them once I (re)moved /etc/timezone in my chroot (tzdata is not
installed but the old /etc/timezone is apparently left around). Fixes
included either setting TZ for the tests or installing tzdata which
recreated /etc/timezone.

My suspicion/idea was that it might be useful to have
libdatetime-timezone-perl depend on tzdata (now that tzdata is not
essential (or whatever it was) any more), as
libdatetime-timezone-perl seems to be involved in alle of the bug
reports …


Thoughts?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   BOFH excuse #64:  CPU needs recalibration