Bug#1058374: marked as done (python-parsley: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 07:19:18 +
with message-id 
and subject line Bug#1058374: fixed in python-parsley 1.3-3
has caused the Debian Bug report #1058374,
regarding python-parsley: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-parsley
Version: 1.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> I: pybuild base:310: python3.11 setup.py config 
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> I: pybuild base:310: /usr/bin/python3 setup.py build 
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_parsley/build; python3.12 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 309 items
> 
> ometa/test/test_builder.py F [  
> 6%]
> ometa/test/test_protocol.py .F.FFF...[ 
> 11%]
> ometa/test/test_pymeta.py .. [ 
> 25%]
> ...F [ 
> 49%]
> s...s...sss...s..s.. [ 
> 72%]
> ..s...   [ 
> 80%]
> ometa/test/test_runtime.py F [ 
> 87%]
> ometa/test/test_tube.py  [ 
> 88%]
> ometa/test/test_vm_builder.py .  [ 
> 95%]
> terml/test/test_quasiterm.py ... [ 
> 96%]
> terml/test/test_terml.py ..  
> [100%]
> 
> === FAILURES 
> ===
> __ PythonWriterTests.test_markAsTree 
> ___
> 
> self = 
> 
> def test_markAsTree(self):
> """
> Grammars containing list patterns are marked as taking
> tree-shaped input rather than character streams.
> """
> x = t.Rule("foo", t.List(
> t.Exactly("x")))
> g = t.Grammar("TestGrammar", True, [x])
> >   self.assert_("\ntree = True\n" in writePython(g, ""))
> E   AttributeError: 'PythonWriterTests' object has no attribute 
> 'assert_'. Did you mean: 'assertIn'?
> 
> ometa/test/test_builder.py:328: AttributeError
> __ ParserProtocolTestCase.test_connectionEstablishes 
> ___
> 
> self =  testMethod=test_connectionEstablishes>
> 
> def test_connectionEstablishes(self):
> """prepareParsing is called on the receiver after connection 
> establishment."""
> self.protocol.makeConnection(None)
> >   self.assert_(self.protocol.receiver.connected)
> E   AttributeError: 'ParserProtocolTestCase' object has no attribute 
> 'assert_'. Did you mean: 'assertIn'?
> 
> ometa/test/test_protocol.py:93: AttributeError
> __ ParserProtocolTestCase.test_dataIgnoredAfterDisconnection 
> ___
> 
> self =  testMethod=test_dataIgnoredAfterDisconnection>
> 
> def test_dataIgnoredAfterDisconnection(self):
> """After connectionLost is called, all incoming data is ignored."""
> transport = FakeTransport()
> self.protocol.makeConnection(transport)
> reason = object()
> self.protocol.connectionLost(reason)
> self.protocol.dataReceived('d')
> self.assertEqual(self.protocol.receiver.lossReason, reason)
> >   self.assert_(not transport.aborted)
> E   AttributeError: 'ParserProtocolTestCase' object has no attribute 
> 'assert_'. Did you mean: 'assertIn'?
> 
> ometa/test/test_protocol.py:190: AttributeError
> ___ 

Processed: fixed 1021153 in 4.0.0~ds-2

[Debian Bug Tracking System]

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

> fixed 1021153 4.0.0~ds-2
Bug #1021153 {Done: Yadd } [node-schema-utils] 
node-schema-utils: ftbfs due to changed output formatting/escaping
Marked as fixed in versions node-schema-utils/4.0.0~ds-2.
> thanks
Stopping processing here.

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

Bug#1057683: marked as done (libpdfbox-java: ftbfs due to bouncycastle 1.77 API changes)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 06:19:12 +
with message-id 
and subject line Bug#1057683: fixed in libpdfbox-java 1:1.8.16-5
has caused the Debian Bug report #1057683,
regarding libpdfbox-java: ftbfs due to bouncycastle 1.77 API changes
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.)


-- 
1057683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdfbox-java
Version: 1:1.8.16-4
Severity: important
Tags: ftbfs

Dear Maintainer,

The package fails to build due to bouncycastle 1.77 API changes.
The relevant part of the build log:

[INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ pdfbox ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 546 source files to /<>/pdfbox/target/classes
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/encryption/DocumentEncryption.java:
Some input files use or override a deprecated API.
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/encryption/DocumentEncryption.java:
Recompile with -Xlint:deprecation for details.
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/cos/COSDictionary.java:
Some input files use or override a deprecated API that is marked for removal.
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/cos/COSDictionary.java:
Recompile with -Xlint:removal for details.
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/common/PDStream.java:
Some input files use unchecked or unsafe operations.
[INFO]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/common/PDStream.java:
Recompile with -Xlint:unchecked for details.
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[45,29]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[316,17]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[316,41]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
cannot find symbol
  symbol:   method getObjectId()
  location: variable algorithmidentifier of type
org.bouncycastle.asn1.x509.AlgorithmIdentifier
[INFO] 4 errors
[INFO] -
[INFO] 
[INFO] Reactor Summary for PDFBox reactor 1.8.16:
[INFO]
[INFO] Apache FontBox . SUCCESS [  0.792 s]
[INFO] Apache JempBox . SUCCESS [  0.082 s]
[INFO] Apache PDFBox .. FAILURE [  1.940 s]
[INFO] PDFBox reactor . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  2.849 s
[INFO] Finished at: 2023-12-07T16:45:43+13:00
[INFO] 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-
plugin:3.10.1:compile (default-compile) on project pdfbox: Compilation failure:
Compilation failure:
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[45,29]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[316,17]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[316,41]
org.bouncycastle.asn1.DEROutputStream is not public in org.bouncycastle.asn1;
cannot be accessed from outside package
[ERROR]
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
cannot find symbol
[ERROR]   symbol:   

Bug#1058508: marked as done (libpdfbox-java: FTBFS: [ERROR] /<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63] cannot find symbol)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 06:19:12 +
with message-id 
and subject line Bug#1057683: fixed in libpdfbox-java 1:1.8.16-5
has caused the Debian Bug report #1057683,
regarding libpdfbox-java: FTBFS: [ERROR] 
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
 cannot find symbol
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.)


-- 
1057683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdfbox-java
Version: 1:1.8.16-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # work around downloading adobe file
> mkdir -p pdfbox/target/classes/org/apache/pdfbox/resources/cmap
> cp pdfbox/src/main/resources/org/apache/pdfbox/resources/cmap/* 
> pdfbox/target/classes/org/apache/pdfbox/resources/cmap/
> mkdir -p pdfbox/target/classes/org/apache/pdfbox/resources/afm
> cp /usr/share/htmldoc/fonts/*.afm 
> pdfbox/target/classes/org/apache/pdfbox/resources/afm/
> cp /usr/share/aglfn/glyphlist.txt 
> pdfbox/target/classes/org/apache/pdfbox/resources
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache FontBox 
> [jar]
> [INFO] Apache JempBox 
> [jar]
> [INFO] Apache PDFBox  
> [jar]
> [INFO] PDFBox reactor 
> [pom]
> [INFO] 
> [INFO] -< org.apache.pdfbox:fontbox 
> >--
> [INFO] Building Apache FontBox 1.8.16 
> [1/4]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.1 
> has been relocated to 
> org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated 
> to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3
> [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has 
> been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
> fontbox ---
> [INFO] skip non existing resourceDirectory 
> /<>/fontbox/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ fontbox 
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 80 source files to /<>/fontbox/target/classes
> [INFO] 
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java:
>  
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java
>  uses or overrides a deprecated API that is marked for removal.
> [INFO] 
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java:
>  Recompile with -Xlint:removal for details.
> [INFO] 
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java:
>  
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java
>  uses unchecked or unsafe operations.
> [INFO] 
> /<>/fontbox/src/main/java/org/apache/fontbox/cmap/CMapParser.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:testResources (default-testResources) 
> @ fontbox ---
> [INFO] 

Processed: Bug#1057683 marked as pending in libpdfbox-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Bug #1058508 [src:libpdfbox-java] libpdfbox-java: FTBFS: [ERROR] 
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
 cannot find symbol
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1057683: marked as pending in libpdfbox-java

[Tony Mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/libpdfbox-java/-/commit/c45215e7bfc5931129180b0303a5b6d6a3d0fce5


Update BouncyCastle patch for BC 1.77 (Closes: #1057683)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057683

Processed: owner 1058508, merging 1057683 1058508

[Debian Bug Tracking System]

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

> owner 1058508 !
Bug #1058508 [src:libpdfbox-java] libpdfbox-java: FTBFS: [ERROR] 
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
 cannot find symbol
Owner recorded as tony mancill .
> merge 1057683 1058508
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Added tag(s) sid and trixie.
Bug #1058508 [src:libpdfbox-java] libpdfbox-java: FTBFS: [ERROR] 
/<>/pdfbox/src/main/java/org/apache/pdfbox/pdmodel/encryption/PublicKeySecurityHandler.java:[431,63]
 cannot find symbol
Merged 1057683 1058508
> thanks
Stopping processing here.

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

Processed (with 1 error): severity of 1057683 is serious, owner 1057683, merging 1057683 1058508

[Debian Bug Tracking System]

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

> severity 1057683 serious
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Severity set to 'serious' from 'important'
> owner 1057683 !
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Owner recorded as tony mancill .
> merge 1057683 1058508
Bug #1057683 [src:libpdfbox-java] libpdfbox-java: ftbfs due to bouncycastle 
1.77 API changes
Unable to merge bugs because:
owner of #1058508 is '' not 'tony mancill '
Failed to merge 1057683: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1058721: squid: CVE-2023-50269: SQUID-2023:10: Denial of Service in HTTP Request parsing

[Salvatore Bonaccorso]

Source: squid
Version: 6.5-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for squid.

CVE-2023-50269[0]:
| Squid is a caching proxy for the Web. Due to an Uncontrolled
| Recursion bug in versions 2.6 through 2.7.STABLE9, versions 3.1
| through 5.9, and versions 6.0.1 through 6.5, Squid may be vulnerable
| to a Denial of Service attack against HTTP Request parsing. This
| problem allows a remote client to perform Denial of Service attack
| by sending a large X-Forwarded-For header when the
| follow_x_forwarded_for feature is configured. This bug is fixed by
| Squid version 6.6. In addition, patches addressing this problem for
| the stable releases can be found in Squid's patch archives.


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-50269
https://www.cve.org/CVERecord?id=CVE-2023-50269
[1] https://github.com/squid-cache/squid/security/advisories/GHSA-wgq4-4cfg-c4x3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

Kernel: Linux 6.6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1058720: slurm-wlm: CVE-2023-49933 CVE-2023-49935 CVE-2023-49936 CVE-2023-49937 CVE-2023-49938

[Salvatore Bonaccorso]

Source: slurm-wlm
Version: 23.02.6-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi Gennaro,

The following vulnerabilities were published for slurm-wlm.

CVE-2023-49933[0]:
| An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and
| 23.11.x. There is Improper Enforcement of Message Integrity During
| Transmission in a Communication Channel. This allows attackers to
| modify RPC traffic in a way that bypasses message hash checks. The
| fixed versions are 22.05.11, 23.02.7, and 23.11.1.


CVE-2023-49935[1]:
| An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x. There
| is Incorrect Access Control because of a slurmd Message Integrity
| Bypass. An attacker can reuse root-level authentication tokens
| during interaction with the slurmd process. This bypasses the RPC
| message hashes that protect against undesired MUNGE credential
| reuse. The fixed versions are 23.02.7 and 23.11.1.


CVE-2023-49936[2]:
| An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and
| 23.11.x. A NULL pointer dereference leads to denial of service. The
| fixed versions are 22.05.11, 23.02.7, and 23.11.1.


CVE-2023-49937[3]:
| An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and
| 23.11.x. Because of a double free, attackers can cause a denial of
| service or possibly execute arbitrary code. The fixed versions are
| 22.05.11, 23.02.7, and 23.11.1.


CVE-2023-49938[4]:
| An issue was discovered in SchedMD Slurm 22.05.x and 23.02.x. There
| is Incorrect Access Control: an attacker can modified their extended
| group list that is used with the sbcast subsystem, and open files
| with an unauthorized set of extended groups. The fixed versions are
| 22.05.11 and 23.02.7.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-49933
https://www.cve.org/CVERecord?id=CVE-2023-49933
[1] https://security-tracker.debian.org/tracker/CVE-2023-49935
https://www.cve.org/CVERecord?id=CVE-2023-49935
[2] https://security-tracker.debian.org/tracker/CVE-2023-49936
https://www.cve.org/CVERecord?id=CVE-2023-49936
[3] https://security-tracker.debian.org/tracker/CVE-2023-49937
https://www.cve.org/CVERecord?id=CVE-2023-49937
[4] https://security-tracker.debian.org/tracker/CVE-2023-49938
https://www.cve.org/CVERecord?id=CVE-2023-49938

Regards,
Salvatore

Bug#1052983: marked as done (bluez FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 04:49:01 +
with message-id 
and subject line Bug#1052983: fixed in bluez 5.70-1.1~exp0
has caused the Debian Bug report #1052983,
regarding bluez FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bluez
Version: 5.69-1
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. bluez' upstream build system consumes this variable
while the packaging hard codes its current value. As we change it, bluez
will FTBFS. Consider applying the attached patch to avoid this failure.

Helmut
diff -Nru bluez-5.69/debian/bluez-meshd.install 
bluez-5.69/debian/bluez-meshd.install
--- bluez-5.69/debian/bluez-meshd.install   2023-08-28 02:38:44.0 
+0200
+++ bluez-5.69/debian/bluez-meshd.install   2023-09-26 16:23:44.0 
+0200
@@ -1,5 +1,5 @@
 usr/share/dbus-1/system.d/bluetooth-mesh.conf
-lib/systemd/system/bluetooth-mesh.service
+${env:deb_systemdsystemunitdir}/bluetooth-mesh.service
 usr/bin/mesh-cfgclient
 usr/bin/mesh-cfgtest
 usr/bin/meshctl
diff -Nru bluez-5.69/debian/bluez.install bluez-5.69/debian/bluez.install
--- bluez-5.69/debian/bluez.install 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/bluez.install 2023-09-26 16:24:10.0 +0200
@@ -24,7 +24,7 @@
 lib/udev/rules.d/97-hid2hci.rules
 attrib/gatttool usr/bin
 #-- for systemd
-lib/systemd/system/bluetooth.service
+${env:deb_systemdsystemunitdir}/bluetooth.service
 usr/share/dbus-1/system.d/bluetooth.conf
 usr/share/dbus-1/system-services/org.bluez.service
 usr/share/zsh/site-functions/_bluetoothctl
diff -Nru bluez-5.69/debian/changelog bluez-5.69/debian/changelog
--- bluez-5.69/debian/changelog 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/changelog 2023-09-26 16:49:20.0 +0200
@@ -1,3 +1,10 @@
+bluez (5.69-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 16:49:20 +0200
+
 bluez (5.69-1) unstable; urgency=medium
 
   * Update to 5.69.
diff -Nru bluez-5.69/debian/control bluez-5.69/debian/control
--- bluez-5.69/debian/control   2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/control   2023-09-26 16:22:48.0 +0200
@@ -18,7 +18,8 @@
python3-docutils,
udev,
check ,
-   systemd
+   systemd,
+   systemd-dev,
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/bluetooth-team/bluez
diff -Nru bluez-5.69/debian/rules bluez-5.69/debian/rules
--- bluez-5.69/debian/rules 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/rules 2023-09-26 16:29:04.0 +0200
@@ -41,6 +41,8 @@
skip_packages = -Nbluez-cups
 endif
 
+export deb_systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
dh $@ --exclude=.la
 
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.70-1.1~exp0
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated bluez 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, 14 Dec 2023 22:32:44 +0100
Source: bluez
Architecture: source
Version: 5.70-1.1~exp0
Distribution: experimental
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 1052983 1056996 1057914
Changes:
 bluez (5.70-1.1~exp0) experimental; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir (Closes: #1052983)
 .
   [ Chris Hofstaedtler ]
   * Defer udev 

Bug#1057914: marked as done (bluez: CVE-2023-45866)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 04:49:02 +
with message-id 
and subject line Bug#1057914: fixed in bluez 5.70-1.1~exp0
has caused the Debian Bug report #1057914,
regarding bluez: CVE-2023-45866
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.)


-- 
1057914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bluez
Version: 5.70-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for bluez.

CVE-2023-45866[0]:
| Bluetooth HID Hosts in BlueZ may permit an unauthenticated
| Peripheral role HID Device to initiate and establish an encrypted
| connection, and accept HID keyboard reports, potentially permitting
| injection of HID messages when no user interaction has occurred in
| the Central role to authorize such access. An example affected
| package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some
| cases, a CVE-2020-0556 mitigation would have already addressed this
| Bluetooth HID Hosts issue.


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-45866
https://www.cve.org/CVERecord?id=CVE-2023-45866
[1] 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=25a471a83e02e1effb15d5a488b3f0085eaeb675

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.70-1.1~exp0
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
bluez, 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.
Salvatore Bonaccorso  (supplier of updated bluez 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, 14 Dec 2023 22:32:44 +0100
Source: bluez
Architecture: source
Version: 5.70-1.1~exp0
Distribution: experimental
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 1052983 1056996 1057914
Changes:
 bluez (5.70-1.1~exp0) experimental; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir (Closes: #1052983)
 .
   [ Chris Hofstaedtler ]
   * Defer udev file placement to udev's pkg-config data (Closes: #1056996)
   * Install hciconfig into /usr/bin instead of /bin
 .
   [ Salvatore Bonaccorso ]
   * input.conf: Change default of ClassicBondedOnly (CVE-2023-45866)
 (Closes: #1057914)
Checksums-Sha1: 
 aa2b13114d9afcae3969887114c8c27280953ab0 2931 bluez_5.70-1.1~exp0.dsc
 d862a26517a90102f34a1fd55f03cb1ccd3ddcec 40952 
bluez_5.70-1.1~exp0.debian.tar.xz
Checksums-Sha256: 
 b574b5de53f5e30678d7739c0faebff711f4594a9ead0d65d31c23573d497300 2931 
bluez_5.70-1.1~exp0.dsc
 47137265c3495c7975a5e690b040a3d18a6bf0e1b5f3034dd3476690d095ec96 40952 
bluez_5.70-1.1~exp0.debian.tar.xz
Files: 
 0b4ee2d33087aecaadbe68a8e4ad6389 2931 admin optional bluez_5.70-1.1~exp0.dsc
 ea761a012caff825d8ebb0fdffaa278f 40952 admin optional 
bluez_5.70-1.1~exp0.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmV7daRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EwBUP/io4r7cBDKrsZmbUA0HaA1L2pnayWBjY
hL/7D95FvgdmqNonlobmV2F53WLBrlpZ7HDUgRl7QD83+/8y9a6U0BvzS9FYOPPo
B+5brqNg9IoLTBIQHsNX8g7OXWvWTr3XDHNabLpqH+jwG1RIbBzlK4XF8yHAYv5E
nf8ylVp87ANxL/bYO3PpPo+FEYrLWZKS1OMmMw8HtIWk7FNnsA6Vwu9/uUSL1d6J
e59VtLt2Jv7hOySDvagGxR18T5zoFaLV/dvznQ/bAhXa0OwhgIaEKNRC47qmQ+oT
N51iNMWYhaNMEHBmN5BYgWtRd4FZdcgGe4upsVBr6y42GSZvSpR+ttnEHlf5gCeq
nsSiaNWbLSnw62+TxsQTlw+98rOTc/DcAZZvAB1mN8NUZwrCCkc+wgjDyTpxWztI
fQW7G6UgRoLly8udA5j9gUjAhrWuUZ1MYZgwhpHQH4abJu4JuNlh87xRKeRwiCUZ
DtuctBhzflo1klhVc1yuLOT9cxBX8Wd3hoARjarY7T/iCMmod4srQThzGlwANhTn

Bug#1052983: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

[Salvatore Bonaccorso]

Hi Nobuhiro

On Fri, Dec 15, 2023 at 08:37:13AM +0900, Nobuhiro Iwamatsu wrote:
> Hi Salvatore,
> 
> Thanks for your work.
> This patch looks good to me.
> Please upload without DELAYED/2 to unstable.

Thanks for the confirmation, so I rescheduled it *but* note due to the
UsrMerge changes it goes first to experimental, so it can be tested by
the dumat tool from Helmut (Cc'ed).

Thank you!

Regards,
Salvatore

Processed: Re: libmpfr6: major formatted output function bugs with %c and the value 0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #1057355 [libmpfr6] libmpfr6: major formatted output function bugs with %c 
and the value 0
Added tag(s) fixed-upstream.

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

Bug#1057355: libmpfr6: major formatted output function bugs with %c and the value 0

[Vincent Lefevre]

Control: tags -1 fixed-upstream

On 2023-12-03 22:13:03 +0100, Vincent Lefevre wrote:
> I've reported the following bug in the MPFR mailing-list. I think
> I've fixed the issues on the MPFR side in master, but MPFR is still
> affected by the bug on the GMP side (gmp_vasprintf):
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057344

The gmp_vasprintf function is actually correct (but its documentation
is not; and it is gmp_sprintf that is incorrect, which is not a
problem for MPFR). I've fixed the remaining bugs in MPFR.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: libgmp10: major formatted output function bug with %c and the value 0

[Debian Bug Tracking System]

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

> severity 1057344 normal
Bug #1057344 [libgmp10] libgmp10: major formatted output function bug with %c 
and the value 0
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#1057344: libgmp10: major formatted output function bug with %c and the value 0

[Steven Robbins]

severity 1057344 normal
thanks


On Sun, 3 Dec 2023 21:10:39 +0100 Vincent Lefevre  wrote:
> Package: libgmp10
> Version: 2:6.2.1+dfsg1-1.1
> Severity: grave
> Tags: security upstream
> Justification: user security hole

I understand the bug may have severe consequences but it doesn't appear to 
rise to the level of grave in my opinion.  

-Steve





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

Bug#1058391: marked as done (heapdict: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 01:49:19 +
with message-id 
and subject line Bug#1058391: fixed in heapdict 1.0.1-3
has caused the Debian Bug report #1058391,
regarding heapdict: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heapdict
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> copying heapdict.py -> /<>/.pybuild/cpython3_3.12_heapdict/build
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying heapdict.py -> /<>/.pybuild/cpython3_3.11_heapdict/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_heapdict/build; python3.12 -m pytest 
> /<>/test_heap.py
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 10 items
> 
> ../../../test_heap.py .F 
> [100%]
> 
> === FAILURES 
> ===
> __ test_main 
> ___
> 
> verbose = None
> 
> def test_main(verbose=None):
> test_classes = [TestHeap]
> >   test_support.run_unittest(*test_classes)
> E   AttributeError: module 'test.support' has no attribute 'run_unittest'
> 
> ../../../test_heap.py:107: AttributeError
> === short test summary info 
> 
> FAILED ../../../test_heap.py::test_main - AttributeError: module 
> 'test.suppor...
> = 1 failed, 9 passed in 0.05s 
> ==
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12_heapdict/build; python3.12 -m pytest 
> /<>/test_heap.py
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.11_heapdict/build; python3.11 -m pytest 
> /<>/test_heap.py
> = test session starts 
> ==
> platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 10 items
> 
> ../../../test_heap.py .F 
> [100%]
> 
> === FAILURES 
> ===
> __ test_main 
> ___
> 
> verbose = None
> 
> def test_main(verbose=None):
> test_classes = [TestHeap]
> >   test_support.run_unittest(*test_classes)
> E   AttributeError: module 'test.support' has no attribute 'run_unittest'
> 
> ../../../test_heap.py:107: AttributeError
> === short test summary info 
> 
> FAILED ../../../test_heap.py::test_main - AttributeError: module 
> 'test.suppor...
> = 1 failed, 9 passed in 0.04s 
> ==
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.11_heapdict/build; python3.11 -m pytest 
> /<>/test_heap.py
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
> 3.11" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/heapdict_1.0.1-2_unstable.log

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

A list of current common problems and possible solutions is available at

Bug#1058391: marked as pending in heapdict

[Diane Trout]

Control: tag -1 pending

Hello,

Bug #1058391 in heapdict 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/heapdict/-/commit/4d8e903cc4263c3ee03ba2e1ff27f949dbc3ed6a


Indicate use-unittest-api.patch Closes: #1058391


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058391

Processed: Bug#1058391 marked as pending in heapdict

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058391 [src:heapdict] heapdict: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.

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

Bug#1052639: marked as done (hfd-service FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 00:49:09 +
with message-id 
and subject line Bug#1052639: fixed in hfd-service 0.2.1-1
has caused the Debian Bug report #1052639,
regarding hfd-service FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hfd-service
Version: 0.2.0-1
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. hfd-service's upstream build system consumes this
variable, but its packaging hard codes the current value. Therefore
hfd-service will FTBFS when we change the value. Consider applying the
attached patch to avoid that failure.

Helmut
diff -Nru hfd-service-0.2.0/debian/changelog hfd-service-0.2.0/debian/changelog
--- hfd-service-0.2.0/debian/changelog  2023-02-05 01:08:28.0 +0100
+++ hfd-service-0.2.0/debian/changelog  2023-09-25 15:31:05.0 +0200
@@ -1,3 +1,10 @@
+hfd-service (0.2.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Sep 2023 15:31:05 +0200
+
 hfd-service (0.2.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru hfd-service-0.2.0/debian/hfd-service.install 
hfd-service-0.2.0/debian/hfd-service.install
--- hfd-service-0.2.0/debian/hfd-service.install2023-02-05 
01:08:28.0 +0100
+++ hfd-service-0.2.0/debian/hfd-service.install2023-09-25 
15:30:49.0 +0200
@@ -1,6 +1,6 @@
 #! /usr/bin/dh-exec
 
 usr/libexec/hfd-service
-[linux-any] lib/systemd/system/hfd-service.service
+[linux-any] ${env:systemdsystemunitdir}/hfd-service.service
 etc/dbus-1/system.d/com.lomiri.hfd.conf
 usr/share/dbus-1/system-services/com.lomiri.hfd.service
diff -Nru hfd-service-0.2.0/debian/rules hfd-service-0.2.0/debian/rules
--- hfd-service-0.2.0/debian/rules  2022-07-20 00:01:10.0 +0200
+++ hfd-service-0.2.0/debian/rules  2023-09-25 15:30:55.0 +0200
@@ -4,6 +4,8 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
+export systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd)
+
 %:
dh $@ --buildsystem cmake
 
--- End Message ---
--- Begin Message ---
Source: hfd-service
Source-Version: 0.2.1-1
Done: Marius Gripsgard 

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

Debian distribution maintenance software
pp.
Marius Gripsgard  (supplier of updated hfd-service 
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: Fri, 15 Dec 2023 00:52:46 +0100
Source: hfd-service
Architecture: source
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Marius Gripsgard 
Closes: 1052639
Changes:
 hfd-service (0.2.1-1) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #1052639)
 .
   [ Marius Gripsgard ]
   * New upstream release
   * Add myself as uploader
   * Correct git/upstream url
Checksums-Sha1:
 66058e80a51e14bb1ff0d2cfd4f5289ba9072766 1850 hfd-service_0.2.1-1.dsc
 b8151d3d1d923f007958f18755359f6f4816c1d2 30911 hfd-service_0.2.1.orig.tar.gz
 63d2e513d142c92ea1b9ad092f55085da662d660 3560 hfd-service_0.2.1-1.debian.tar.xz
 0ef778bc5bd561cb1d96d2ce633712db076da5d2 12763 
hfd-service_0.2.1-1_source.buildinfo
Checksums-Sha256:
 05c41e9d5098f3de4d37fed7d14744869d1da8ab4bf1aed4d9a6d6bde360611a 1850 
hfd-service_0.2.1-1.dsc
 e1b313e2bb22a556703410952856df722203a2f778de0ec0c47e5d56c61788e2 30911 
hfd-service_0.2.1.orig.tar.gz
 d6db4d1359d455eba7ecf8593db8d4f27d7038bd0469f2b1405ac4e63fddaf21 3560 
hfd-service_0.2.1-1.debian.tar.xz
 0cec7f9b19c79791efd781755a721e1fabb338bcaaca84c168ec00b831a94b9f 12763 
hfd-service_0.2.1-1_source.buildinfo
Files:
 

Bug#1055726: marked as done (scikit-misc ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 00:22:26 +
with message-id 
and subject line Bug#1055726: fixed in scikit-misc 0.3.1+dfsg-1
has caused the Debian Bug report #1055726,
regarding scikit-misc 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.)


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

Package: src:scikit-misc
Version: 0.1.4+dfsg-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

scikit-misc ftbfs with Python 3.12:

[...]
creating build
creating build/src.linux-x86_64-3.12
creating build/src.linux-x86_64-3.12/skmisc
INFO: building library "floess" sources
INFO: building extension "skmisc.loess._loess" sources
INFO: building data_files sources
INFO: build_src: building npy-pkg config files
/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
SetuptoolsDeprecationWarning: setup.py install is deprecated.

!!



Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.

See 
https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for 
details.




!!
  self.initialize_options()
running build_py
Traceback (most recent call last):
  File "/<>/setup.py", line 180, in 
setup_package()
  File "/<>/setup.py", line 174, in setup_package
setup(**metadata)
  File "/usr/lib/python3/dist-packages/numpy/distutils/core.py", line 
169, in setup

return old_setup(**new_attr)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 
107, in setup

return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", 
line 185, in setup

return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", 
line 201, in run_commands

dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", 
line 969, in run_commands

self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, 
in run_command

super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", 
line 988, in run_command

cmd_obj.run()
  File 
"/usr/lib/python3/dist-packages/numpy/distutils/command/build.py", line 
62, in run

old_build.run(self)
  File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 131, in run

self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", 
line 318, in run_command

self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, 
in run_command

super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", 
line 988, in run_command

cmd_obj.run()
  File "/<>/versioneer.py", line 1558, in run
cfg = get_config_from_root(root)
  ^^
  File "/<>/versioneer.py", line 342, in get_config_from_root
parser = configparser.SafeConfigParser()
 ^
AttributeError: module 'configparser' has no attribute 
'SafeConfigParser'. Did you mean: 'RawConfigParser'?
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build
--- End Message ---
--- Begin Message ---
Source: scikit-misc
Source-Version: 0.3.1+dfsg-1
Done: Diane Trout 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Jul 2023 

Bug#1057421: sysstat: diff for NMU version 12.6.1-1.1

[Chris Hofstaedtler]

Control: tags 1057421 + pending


Dear maintainer,

I've prepared an NMU for sysstat (versioned as 12.6.1-1.1) and
uploaded it to DELAYED/7. Please feel free to upload yourself in the
meantime.

I'll also push a branch to salsa for the changelog entry.

Chris

diff -Nru sysstat-12.6.1/debian/changelog sysstat-12.6.1/debian/changelog
--- sysstat-12.6.1/debian/changelog	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/changelog	2023-12-15 01:23:13.0 +0100
@@ -1,3 +1,11 @@
+sysstat (12.6.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS after systemdsystemunitdir changed in systemd.pc
+(Closes: #1057421)
+
+ -- Chris Hofstaedtler   Fri, 15 Dec 2023 01:23:13 +0100
+
 sysstat (12.6.1-1) unstable; urgency=medium
 
   * New upstream stable version: fixes size_t overflow in sa_common.c
diff -Nru sysstat-12.6.1/debian/control sysstat-12.6.1/debian/control
--- sysstat-12.6.1/debian/control	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/control	2023-12-15 01:23:13.0 +0100
@@ -6,7 +6,8 @@
gettext,
libsensors-dev,
pkg-config,
-   systemd
+   systemd,
+   systemd-dev
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Homepage: http://sebastien.godard.pagesperso-orange.fr/
diff -Nru sysstat-12.6.1/debian/rules sysstat-12.6.1/debian/rules
--- sysstat-12.6.1/debian/rules	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/rules	2023-12-15 01:23:13.0 +0100
@@ -19,6 +19,8 @@
 
 DFLAGS :=
 
+export deb_systemdsystemunitdir=$(shell pkgconf --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
 	dh ${@}
 
diff -Nru sysstat-12.6.1/debian/sysstat.install sysstat-12.6.1/debian/sysstat.install
--- sysstat-12.6.1/debian/sysstat.install	2022-12-04 22:23:25.0 +0100
+++ sysstat-12.6.1/debian/sysstat.install	2023-12-15 01:23:13.0 +0100
@@ -1,5 +1,5 @@
 debian/debian-sa1 usr/lib/sysstat
 debian/tmp/etc/
-debian/tmp/lib/systemd/
+debian/tmp/${env:deb_systemdsystemunitdir}
 debian/tmp/usr/
 debian/tmp/var/

Processed: sysstat: diff for NMU version 12.6.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1057421 + pending
Bug #1057421 [src:sysstat] sysstat: FTBFS: dh_install: warning: Cannot find 
(any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp)
Added tag(s) pending.

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

Bug#1055723: rocketcea ftbfs with Python 3.12

[Bdale Garbee]

You have my permission.

Bdale 

On December 14, 2023 11:54:24 AM MST, Alexandre Detiste 
 wrote:
>Hi,
>
>I ll try to fix this one if you permit.
>
>
>Greetings

Bug#1052984: marked as done (deviceinfo FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 00:04:01 +
with message-id 
and subject line Bug#1052984: fixed in deviceinfo 0.2.1-1
has caused the Debian Bug report #1052984,
regarding deviceinfo FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deviceinfo
Version: 0.2.0-1
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. deviceinfo's upstream build system consumes this
variable while the packaging hard codes its current value. As we change
it, deviceinfo will FTBFS. Consider applying the attached patch to avoid
this failure.

Helmut
diff -Nru deviceinfo-0.2.0/debian/changelog deviceinfo-0.2.0/debian/changelog
--- deviceinfo-0.2.0/debian/changelog   2023-06-11 14:19:45.0 +0200
+++ deviceinfo-0.2.0/debian/changelog   2023-09-26 14:53:41.0 +0200
@@ -1,3 +1,10 @@
+deviceinfo (0.2.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 14:53:41 +0200
+
 deviceinfo (0.2.0-1) unstable; urgency=medium
 
   [ Mike Gabriel ]
diff -Nru deviceinfo-0.2.0/debian/control deviceinfo-0.2.0/debian/control
--- deviceinfo-0.2.0/debian/control 2023-06-11 14:19:38.0 +0200
+++ deviceinfo-0.2.0/debian/control 2023-09-26 14:52:31.0 +0200
@@ -12,6 +12,7 @@
libyaml-cpp-dev,
pkg-config,
systemd,
+   systemd-dev,
 Maintainer: Debian UBports Team 
 Uploaders: Mike Gabriel ,
 Standards-Version: 4.6.2
diff -Nru deviceinfo-0.2.0/debian/deviceinfo-extras.install 
deviceinfo-0.2.0/debian/deviceinfo-extras.install
--- deviceinfo-0.2.0/debian/deviceinfo-extras.install   2023-06-11 
14:19:31.0 +0200
+++ deviceinfo-0.2.0/debian/deviceinfo-extras.install   2023-09-26 
14:53:33.0 +0200
@@ -1,2 +1,2 @@
 usr/libexec/update-machine-info-from-deviceinfo
-lib/systemd/system/update-machine-info-from-deviceinfo.service
+${env:deb_systemdsystemunitdir}/update-machine-info-from-deviceinfo.service
diff -Nru deviceinfo-0.2.0/debian/rules deviceinfo-0.2.0/debian/rules
--- deviceinfo-0.2.0/debian/rules   2023-06-11 14:19:31.0 +0200
+++ deviceinfo-0.2.0/debian/rules   2023-09-26 14:53:14.0 +0200
@@ -5,6 +5,7 @@
 include /usr/share/dpkg/buildflags.mk
 
 export DPKG_GENSYMBOLS_CHECK_LEVEL=1
+export deb_systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
 
 %:
dh $@ --buildsystem cmake
--- End Message ---
--- Begin Message ---
Source: deviceinfo
Source-Version: 0.2.1-1
Done: Marius Gripsgard 

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

Debian distribution maintenance software
pp.
Marius Gripsgard  (supplier of updated deviceinfo 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: Fri, 15 Dec 2023 00:43:58 +0100
Source: deviceinfo
Architecture: source
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Marius Gripsgard 
Closes: 1052984
Changes:
 deviceinfo (0.2.1-1) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #1052984)
 .
   [ Marius Gripsgard ]
   * New upstream release
   * Add myself as uploader
Checksums-Sha1:
 e5736a06d49ed13cd2692d7a0fe0b381f42c7263 1734 deviceinfo_0.2.1-1.dsc
 a23fb73b7e37082ddf47fba56a2ff3598b304ec0 36764 deviceinfo_0.2.1.orig.tar.gz
 aaafdf3c529b0fe5c2677015823ed46194cd015a 4320 deviceinfo_0.2.1-1.debian.tar.xz
 5e642a1bedb69e5b017491e41ac34c1ca2b35bf5 8712 
deviceinfo_0.2.1-1_source.buildinfo
Checksums-Sha256:
 7f26708d4e7d8e0ba46d5223f65fce3b96837030d9b52930d22d311b802949be 1734 
deviceinfo_0.2.1-1.dsc
 

Bug#1052983: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

[Nobuhiro Iwamatsu]

Hi Salvatore,

Thanks for your work.
This patch looks good to me.
Please upload without DELAYED/2 to unstable.

Best regards,
  Nobuhiro

2023年12月15日(金) 6:45 Salvatore Bonaccorso :
>
> Control: tags 1052983 + pending
> Control: tags 1056996 + pending
> Control: tags 1057914 + patch
> Control: tags 1057914 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for bluez (versioned as 5.70-1.1~exp0) and
> uploaded it to DELAYED/2 (targetting experimental to expose the
> UsrMerge parts first by the dumat tool). Please feel free to tell me
> if I should delay it longer.
>
> Regards,
> Salvatore



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org / kernel.org}
   GPG ID: 32247FBB40AD1FA6

Bug#1056036: marked as done (python-aiohttp ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 23:20:19 +
with message-id 
and subject line Bug#1056036: fixed in python-aiohttp 3.9.1-1
has caused the Debian Bug report #1056036,
regarding python-aiohttp 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.)


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

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

python-aiohttp ftbfs with Python 3.12:

[...]
building 'aiohttp._websocket' extension
creating build
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/aiohttp
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection 
-fdebug-prefix-map=/<>=/usr/src/python-aiohttp-3.8.6-1build1 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -c 
aiohttp/_websocket.c -o 
build/temp.linux-x86_64-cpython-312/aiohttp/_websocket.o
aiohttp/_websocket.c: In function 
‘__pyx_pf_7aiohttp_10_websocket__websocket_mask_cython’:
aiohttp/_websocket.c:1475:3: warning: ‘Py_OptimizeFlag’ is deprecated 
[-Wdeprecated-declarations]

 1475 |   if (unlikely(!Py_OptimizeFlag)) {
  |   ^~
In file included from /usr/include/python3.12/Python.h:48,
 from aiohttp/_websocket.c:6:
/usr/include/python3.12/cpython/pydebug.h:13:37: note: declared here
   13 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_OptimizeFlag;
  | ^~~
aiohttp/_websocket.c: In function ‘__Pyx_get_tp_dict_version’:
aiohttp/_websocket.c:2680:5: warning: ‘ma_version_tag’ is deprecated 
[-Wdeprecated-declarations]

 2680 | return likely(dict) ? __PYX_GET_DICT_VERSION(dict) : 0;
  | ^~
In file included from /usr/include/python3.12/dictobject.h:90,
 from /usr/include/python3.12/Python.h:61:
/usr/include/python3.12/cpython/dictobject.h:22:34: note: declared here
   22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
  |  ^~
aiohttp/_websocket.c: In function ‘__Pyx_get_object_dict_version’:
aiohttp/_websocket.c:2692:5: warning: ‘ma_version_tag’ is deprecated 
[-Wdeprecated-declarations]
 2692 | return (dictptr && *dictptr) ? 
__PYX_GET_DICT_VERSION(*dictptr) : 0;

  | ^~
/usr/include/python3.12/cpython/dictobject.h:22:34: note: declared here
   22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
  |  ^~
aiohttp/_websocket.c: In function ‘__Pyx_object_dict_version_matches’:
aiohttp/_websocket.c:2696:5: warning: ‘ma_version_tag’ is deprecated 
[-Wdeprecated-declarations]
 2696 | if (unlikely(!dict) || unlikely(tp_dict_version != 
__PYX_GET_DICT_VERSION(dict)))

  | ^~
/usr/include/python3.12/cpython/dictobject.h:22:34: note: declared here
   22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
  |  ^~
aiohttp/_websocket.c: In function ‘__Pyx_CLineForTraceback’:
aiohttp/_websocket.c:2741:9: warning: ‘ma_version_tag’ is deprecated 
[-Wdeprecated-declarations]

 2741 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
  | ^~~~
/usr/include/python3.12/cpython/dictobject.h:22:34: note: declared here
   22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
  |  ^~
aiohttp/_websocket.c:2741:9: warning: ‘ma_version_tag’ is deprecated 
[-Wdeprecated-declarations]

 2741 | __PYX_PY_DICT_LOOKUP_IF_MODIFIED(
  | ^~~~
/usr/include/python3.12/cpython/dictobject.h:22:34: note: declared here
   22 | Py_DEPRECATED(3.12) uint64_t ma_version_tag;
  |  ^~
aiohttp/_websocket.c: In function ‘__Pyx_PyInt_As_long’:
aiohttp/_websocket.c:3042:53: error: ‘PyLongObject’ {aka ‘struct 
_longobject’} has no member named ‘ob_digit’

 3042 | const digit* digits = ((PyLongObject*)x)->ob_digit;
  | ^~
aiohttp/_websocket.c:3097:53: error: ‘PyLongObject’ {aka ‘struct 
_longobject’} has no member named ‘ob_digit’

 3097 | 

Bug#1058442: marked as done (ledger-autosync: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 23:05:42 +
with message-id 
and subject line Bug#1058442: fixed in ledger-autosync 1.0.3.28.gcbfa04d-1
has caused the Debian Bug report #1058442,
regarding ledger-autosync: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ledger-autosync
Version: 1.0.3.22.g4edbb5b-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.12_ledger-autosync 
> * Building wheel...
> Successfully built ledger_autosync-1.0.3-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with 
> "installer" module
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_ledger-autosync 
> * Building wheel...
> Successfully built ledger_autosync-1.0.3-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_ledger-autosync/build; python3.12 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.12_ledger-autosync/build
> configfile: pyproject.toml
> collected 78 items / 2 errors
> 
>  ERRORS 
> 
> __ ERROR collecting tests/test_cli.py 
> __
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.12_ledger-autosync/build/tests/test_cli.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_cli.py:29: in 
> from ledgerautosync.cli import find_ledger_file, run
> ledgerautosync/cli.py:24: in 
> import imp
> E   ModuleNotFoundError: No module named 'imp'
> ___ ERROR collecting tests/test_weird_ofx.py 
> ___
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.12_ledger-autosync/build/tests/test_weird_ofx.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_weird_ofx.py:27: in 
> from ledgerautosync.cli import run
> ledgerautosync/cli.py:24: in 
> import imp
> E   ModuleNotFoundError: No module named 'imp'
> === short test summary info 
> 
> ERROR tests/test_cli.py
> ERROR tests/test_weird_ofx.py
> !!! Interrupted: 2 errors during collection 
> 
> == 2 errors in 0.20s 
> ===
> E: pybuild pybuild:395: test: plugin pyproject failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.12_ledger-autosync/build; python3.12 -m 
> pytest tests
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.11_ledger-autosync/build; python3.11 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.11_ledger-autosync/build
> configfile: pyproject.toml
> collected 101 items
> 
> tests/test_cli.py ...[  
> 6%]
> tests/test_converter.py .   

Bug#1055566: marked as done (mod-wsgi ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 23:06:23 +
with message-id 
and subject line Bug#1055566: fixed in mod-wsgi 5.0.0-1
has caused the Debian Bug report #1055566,
regarding mod-wsgi 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.)


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

Package: src:mod-wsgi
Version: 4.9.4-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

mod-wsgi ftbfs with Python 3.12

[...]
/usr/share/apr-1.0/build/libtool  --mode=link --tag=disable-static 
x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-Bsymbolic-functions -flto=auto 
-ffat-lto-objects -Wl,-z,relro -Wl,-z,now -lpcre2-8 
-L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0-o src/server/mod_wsgi.la 
 -rpath /usr/lib/apache2/modules -module -avoid-version 
src/server/wsgi_validate.lo src/server/wsgi_thread.lo 
src/server/wsgi_stream.lo src/server/wsgi_server.lo 
src/server/wsgi_restrict.lo src/server/wsgi_metrics.lo 
src/server/wsgi_memory.lo src/server/wsgi_logger.lo 
src/server/wsgi_interp.lo src/server/wsgi_daemon.lo 
src/server/wsgi_convert.lo src/server/wsgi_buckets.lo 
src/server/wsgi_apache.lo src/server/mod_wsgi.lo 
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro 
-L/usr/lib/x86_64-linux-gnu -L -lpython3.12 -ldl -lm

libtool:   error: require no space between '-L' and '-lpython3.12'
apxs:Error: Command failed with rc=65536
.
make[2]: *** [Makefile:31: src/server/mod_wsgi.la] Error 1
make[2]: Leaving directory '/<>/build-3.12'
--- End Message ---
--- Begin Message ---
Source: mod-wsgi
Source-Version: 5.0.0-1
Done: Bo YU 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 Dec 2023 15:09:03 +0800
Source: mod-wsgi
Architecture: source
Version: 5.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bo YU 
Closes: 1055566
Changes:
 mod-wsgi (5.0.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 5.0.0. (Closes: #1055566)
   * Add metadata file.
Checksums-Sha1:
 0b785f9ce1f41b460a0e00f432040782fbc43ca4 1884 mod-wsgi_5.0.0-1.dsc
 5dacd734ef568a20c20cdd7952074ac4601de8e6 707590 mod-wsgi_5.0.0.orig.tar.gz
 54519b6e673d97654c33bf2f2c052683afe2fe64 11080 mod-wsgi_5.0.0-1.debian.tar.xz
 4deec11c5005c74f1c6500baaa3500d3b77ebe9b 7351 mod-wsgi_5.0.0-1_source.buildinfo
Checksums-Sha256:
 d61bbb711cec4789796b078fb8e5d22b1c4b07abb43e4ed1ec2109a39ef60402 1884 
mod-wsgi_5.0.0-1.dsc
 013e788e26c27eeda99e235fc3ed94dc7ff8b62a0ad2fb5a1cb46aaa92f8f9cc 707590 
mod-wsgi_5.0.0.orig.tar.gz
 31fed78a17cec65a1b6a4f59138c79ee0dfc9b2f877f364e35cfacce8938dcb9 11080 
mod-wsgi_5.0.0-1.debian.tar.xz
 ff45b37fd2af8fd11ea4ac2d4dd7a83aae2ba4e98dc842d715d1e6a00ee26dc9 7351 
mod-wsgi_5.0.0-1_source.buildinfo
Files:
 82b63c55df1f13ff5d7644dca35bdac5 1884 httpd optional mod-wsgi_5.0.0-1.dsc
 df853606c97d39936d41654e3f2f15a9 707590 httpd optional 
mod-wsgi_5.0.0.orig.tar.gz
 02ad75676b878eb5ca7050040ab74529 11080 httpd optional 
mod-wsgi_5.0.0-1.debian.tar.xz
 761fd1fcedbfc4b845e0ff9368aebdad 7351 httpd optional 
mod-wsgi_5.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmV7h3YQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFLPFC/0UqOsQuThHq5YvgW9wvn92uIvQP0bDmIHk
ckqH8CLPeVqdY7wbZfxqnVjIqY4OFQWPN2KwkNdd4RlAZLWNT9xcr10rpHqTfiY3
1UhpGrisr+u2ymK532HSd/fb82lUTDvNenTv0gt0GvI6DKcjmLxiyGAgjmeRvyQe
KRf/iPKb9Vx1hlTod9t3e3rbytN+v/Xi5lF8qSo4T/l5+9yaOba9nJP1XGFPeA7L
o8U+A6IV/4Qb8vz/Ax+Xh6sdiJRLeeBufE8iod1UKgGujGPUUZC7naSpBI7VuPhi
Z07zSnNa4V+Th/opWq1nlAxBJBafP1JCkYGbjvBlFe2URn0ppaOfx3wEjs4TiI2H
BejEzTNwA0SccVy8iHl+OlZaM1Mo8G+UTXCokwEA6UtMmhehpC59OgFsmSy7FA93
E7zvHu6mXnBlwLfUwmXzVPo+AzOc52xstyjI8kEEhJK1gd4zAFlH2VomHE7gHWMl
njc7v4ObTUnXxYs5aVEbhMOyKBQaUe4=
=ao3x
-END PGP SIGNATURE 

Processed: Re: burp: FTBFS with zlib 1.3 due to 'make check' failure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1057880 [src:burp] burp: FTBFS with zlib 1.3 due to 'make check' failure
Added tag(s) patch.

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

Bug#1057880: burp: FTBFS with zlib 1.3 due to 'make check' failure

[James Addison]

Source: burp
Followup-For: Bug #1057880
X-Debbugs-Cc: z...@debian.org, broo...@debian.org

Dear Maintainer,

Attached is a patch that includes the changes applied by Ubuntu[1] to remove
the problematic unit test version check from their source package.

For visibility, on cc are Shengjing Zhu (as the patch author) and Broonie (as
zlib maintainer in Debian).

Regards,
James

[1] - https://bugs.launchpad.net/ubuntu/+source/burp/+bug/2046149
diff --git a/debian/changelog b/debian/changelog
index 1974a93..c18448e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+burp (3.1.4-3ubuntu1) noble; urgency=medium
+
+  * Add patch to remove unnecessary but broken zlib version check in fzp test
+(Closes: #1057880, LP: #2046149)
+
+ -- Shengjing Zhu   Mon, 11 Dec 2023 18:59:33 
+0800
+
 burp (3.1.4-3) unstable; urgency=medium
 
   * fix cleanup target (Closes: #1044122)
diff --git 
a/debian/patches/remove-unnecessary-but-broken-zlib-version-check-in-fzp-t.patch
 
b/debian/patches/remove-unnecessary-but-broken-zlib-version-check-in-fzp-t.patch
new file mode 100644
index 000..a86d269
--- /dev/null
+++ 
b/debian/patches/remove-unnecessary-but-broken-zlib-version-check-in-fzp-t.patch
@@ -0,0 +1,23 @@
+From: Shengjing Zhu 
+Date: Mon, 11 Dec 2023 18:56:13 +0800
+Subject: remove unnecessary but broken zlib version check in fzp test
+
+Debian-Bug: http://bugs.debian.org/1057880
+Ubuntu-Bug: https://launchpad.net/bugs/2046149
+---
+ utest/test_fzp.c | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/utest/test_fzp.c b/utest/test_fzp.c
+index 856eae1..cac280c 100644
+--- a/utest/test_fzp.c
 b/utest/test_fzp.c
+@@ -179,8 +179,6 @@ END_TEST
+ 
+ START_TEST(test_fzp_gzseek)
+ {
+-  if(version_to_long(ZLIB_VERSION) <= version_to_long("1.2.3"))
+-  fzp_gzopen_old_zlib_seek_hack=1;
+   do_seek_tests(fzp_gzopen);
+ }
+ END_TEST
diff --git a/debian/patches/series b/debian/patches/series
index 8e3360f..a81b657 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ CVE-2017-16516.patch
 CVE-2022-24795.patch
 CVE-2023-33460-part1.patch
 CVE-2023-33460-part2.patch
+remove-unnecessary-but-broken-zlib-version-check-in-fzp-t.patch

Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

[Chris Hofstaedtler]

Hi everyone!

On Tue, Dec 12, 2023 at 03:08:49PM +0100, Helmut Grohne wrote:
[..
> Almost two weeks later, I'm back with what I hope is a solution.
[..]
> At the time of this writing, my preferred solution is restoring the lost
> files in postinst. Fortunately, they are all symlinks in the case of
> systemd-sysv, so restoring them is a rather simple matter. And this is
> what the attached systemd patch does.
[..]
> This is not the option I'm going for now. Rather, given that systemd can
> paper over the loss we can make the loss very unlikely by having
> molly-guard not declare Breaks against systemd-sysv. As a result, apt no
> longer sees a mutual conflict and no longer schedules temporary removal.
> Thus, the loss scenario (usually) does not happen (though systemd-sysv
> still mitigates it).

I think this is a good plan, even though this means quite a few
packages will have to do this in their maintainer scripts. I'll note
that all affected packages will have to cooperate.

[..]
> /usr/sbin/halt -> /usr/sbin/halt.no-molly-guard

I think this is a bit of a problem. My understanding of
molly-guard's primary feature is to hide dangerous programs from
$PATH, to avoid execution by overworked (or otherwise unattentive)
operators.

Keeping the dangerous programs in $PATH, under a similar-enough name
that TAB-completion works, might be a serious downgrade in
functionality to molly-guard's audience.

I would suspect for other packages, like progress-linux-container,
it might be worse, if they expect to completely disable these
programs.

As said above, this is all speculation, but I want to point this
out, and maybe Francois can comment if this is acceptable for
molly-guard?

[..]
> So now I am attaching the result of my work. I invite people to review
> it (even though I understand that this is a complex matter). In
> particular, I am also interested in what kind of tests I should be
> performing in addition.

I've asked you before on IRC about the test cases I thought to be
the "interesting" ones and you pointed out they are already
covered by the attached testcases and they have a success outcome.

Chris

Bug#1058416: marked as done (nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 22:21:38 +
with message-id 
and subject line Bug#1058416: fixed in nitime 0.10.2-1
has caused the Debian Bug report #1058416,
regarding nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/utils.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/version.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/_mpl_units.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/viz.py -> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/lazy.py -> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/lazyimports.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/index_utils.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/descriptors.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> copying nitime/timeseries.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime
> creating /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_algorithms.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_lazy.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_timeseries.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_analysis.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_utils.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_viz.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> copying nitime/tests/test_descriptors.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/tests
> creating /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/event_related.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/spectral.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/granger.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/correlation.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/snr.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/base.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/coherence.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> copying nitime/analysis/normalization.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/analysis
> creating /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/entropy.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/event_related.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/spectral.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/autoregressive.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/correlation.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/wavelet.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying nitime/algorithms/cohere.py -> 
> /<>/.pybuild/cpython3_3.12/build/nitime/algorithms
> copying 

Processed: bluez: diff for NMU version 5.70-1.1~exp0

[Debian Bug Tracking System]

Processing control commands:

> tags 1052983 + pending
Bug #1052983 [src:bluez] bluez FTBFS when systemd.pc changes 
systemdsystemunitdir
Ignoring request to alter tags of bug #1052983 to the same tags previously set
> tags 1056996 + pending
Bug #1056996 [src:bluez] bluez FTBFS when udev.pc changes udevdir
Ignoring request to alter tags of bug #1056996 to the same tags previously set
> tags 1057914 + patch
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Ignoring request to alter tags of bug #1057914 to the same tags previously set
> tags 1057914 + pending
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Ignoring request to alter tags of bug #1057914 to the same tags previously set

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

Processed: bluez: diff for NMU version 5.70-1.1~exp0

[Debian Bug Tracking System]

Processing control commands:

> tags 1052983 + pending
Bug #1052983 [src:bluez] bluez FTBFS when systemd.pc changes 
systemdsystemunitdir
Ignoring request to alter tags of bug #1052983 to the same tags previously set
> tags 1056996 + pending
Bug #1056996 [src:bluez] bluez FTBFS when udev.pc changes udevdir
Ignoring request to alter tags of bug #1056996 to the same tags previously set
> tags 1057914 + patch
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Ignoring request to alter tags of bug #1057914 to the same tags previously set
> tags 1057914 + pending
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Ignoring request to alter tags of bug #1057914 to the same tags previously set

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

Bug#1052983: bluez: diff for NMU version 5.70-1.1~exp0

[Salvatore Bonaccorso]

Control: tags 1052983 + pending
Control: tags 1056996 + pending
Control: tags 1057914 + patch
Control: tags 1057914 + pending


Dear maintainer,

I've prepared an NMU for bluez (versioned as 5.70-1.1~exp0) and
uploaded it to DELAYED/2 (targetting experimental to expose the
UsrMerge parts first by the dumat tool). Please feel free to tell me
if I should delay it longer.

Regards,
Salvatore
diff -Nru bluez-5.70/debian/bluez-meshd.install bluez-5.70/debian/bluez-meshd.install
--- bluez-5.70/debian/bluez-meshd.install	2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/bluez-meshd.install	2023-12-14 22:32:44.0 +0100
@@ -1,5 +1,5 @@
 usr/share/dbus-1/system.d/bluetooth-mesh.conf
-lib/systemd/system/bluetooth-mesh.service
+${env:deb_systemdsystemunitdir}/bluetooth-mesh.service
 usr/bin/mesh-cfgclient
 usr/bin/mesh-cfgtest
 usr/bin/meshctl
diff -Nru bluez-5.70/debian/bluez.install bluez-5.70/debian/bluez.install
--- bluez-5.70/debian/bluez.install	2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/bluez.install	2023-12-14 22:32:44.0 +0100
@@ -7,7 +7,7 @@
 usr/bin/btattach
 usr/bin/btmon
 usr/bin/hciattach
-usr/bin/hciconfig bin/
+usr/bin/hciconfig
 usr/bin/hcitool
 usr/bin/sdptool
 usr/bin/rctest
@@ -20,11 +20,11 @@
 usr/bin/mpris-proxy
 tools/btmgmt usr/bin
 tools/obexctl usr/bin
-lib/udev/hid2hci
-lib/udev/rules.d/97-hid2hci.rules
+${env:deb_udevdir}/hid2hci
+${env:deb_udevdir}/rules.d/97-hid2hci.rules
 attrib/gatttool usr/bin
 #-- for systemd
-lib/systemd/system/bluetooth.service
+${env:deb_systemdsystemunitdir}/bluetooth.service
 usr/share/dbus-1/system.d/bluetooth.conf
 usr/share/dbus-1/system-services/org.bluez.service
 usr/share/zsh/site-functions/_bluetoothctl
diff -Nru bluez-5.70/debian/changelog bluez-5.70/debian/changelog
--- bluez-5.70/debian/changelog	2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/changelog	2023-12-14 22:32:44.0 +0100
@@ -1,3 +1,20 @@
+bluez (5.70-1.1~exp0) experimental; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir (Closes: #1052983)
+
+  [ Chris Hofstaedtler ]
+  * Defer udev file placement to udev's pkg-config data (Closes: #1056996)
+  * Install hciconfig into /usr/bin instead of /bin
+
+  [ Salvatore Bonaccorso ]
+  * input.conf: Change default of ClassicBondedOnly (CVE-2023-45866)
+(Closes: #1057914)
+
+ -- Salvatore Bonaccorso   Thu, 14 Dec 2023 22:32:44 +0100
+
 bluez (5.70-1) unstable; urgency=medium
 
   * Update to 5.70.
diff -Nru bluez-5.70/debian/control bluez-5.70/debian/control
--- bluez-5.70/debian/control	2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/control	2023-12-14 22:32:44.0 +0100
@@ -18,7 +18,8 @@
python3-docutils,
udev,
check ,
-   systemd
+   systemd,
+   systemd-dev,
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/bluetooth-team/bluez
diff -Nru bluez-5.70/debian/patches/input.conf-Change-default-of-ClassicBondedOnly.patch bluez-5.70/debian/patches/input.conf-Change-default-of-ClassicBondedOnly.patch
--- bluez-5.70/debian/patches/input.conf-Change-default-of-ClassicBondedOnly.patch	1970-01-01 01:00:00.0 +0100
+++ bluez-5.70/debian/patches/input.conf-Change-default-of-ClassicBondedOnly.patch	2023-12-14 22:32:44.0 +0100
@@ -0,0 +1,52 @@
+From: Luiz Augusto von Dentz 
+Date: Tue, 10 Oct 2023 13:03:12 -0700
+Subject: input.conf: Change default of ClassicBondedOnly
+Origin: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit?id=25a471a83e02e1effb15d5a488b3f0085eaeb675
+Bug-Debian: https://bugs.debian.org/1057914
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-45866
+
+This changes the default of ClassicBondedOnly since defaulting to false
+is not inline with HID specification which mandates the of Security Mode
+4:
+
+BLUETOOTH SPECIFICATION Page 84 of 123
+Human Interface Device (HID) Profile:
+
+  5.4.3.4.2 Security Modes
+  Bluetooth HID Hosts shall use Security Mode 4 when interoperating with
+  Bluetooth HID devices that are compliant to the Bluetooth Core
+  Specification v2.1+EDR[6].
+---
+ profiles/input/device.c   | 2 +-
+ profiles/input/input.conf | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/profiles/input/device.c b/profiles/input/device.c
+index 4a50ea9921a9..4310dd192e11 100644
+--- a/profiles/input/device.c
 b/profiles/input/device.c
+@@ -81,7 +81,7 @@ struct input_device {
+ 
+ static int idle_timeout = 0;
+ static bool uhid_enabled = false;
+-static bool classic_bonded_only = false;
++static bool classic_bonded_only = true;
+ 
+ void input_set_idle_timeout(int timeout)
+ {
+diff --git a/profiles/input/input.conf b/profiles/input/input.conf
+index 4c70bc561f05..d8645f3dd664 100644
+--- a/profiles/input/input.conf
 b/profiles/input/input.conf
+@@ -17,7 +17,7 @@
+ # platforms may want to 

Processed: bluez: diff for NMU version 5.70-1.1~exp0

[Debian Bug Tracking System]

Processing control commands:

> tags 1052983 + pending
Bug #1052983 [src:bluez] bluez FTBFS when systemd.pc changes 
systemdsystemunitdir
Added tag(s) pending.
> tags 1056996 + pending
Bug #1056996 [src:bluez] bluez FTBFS when udev.pc changes udevdir
Added tag(s) pending.
> tags 1057914 + patch
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Added tag(s) patch.
> tags 1057914 + pending
Bug #1057914 [src:bluez] bluez: CVE-2023-45866
Added tag(s) pending.

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

Bug#1057934: marked as done (libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 22:22:43 +0100
with message-id <853523f5-4b93-4f41-8666-2e0f9d1af...@thykier.net>
and subject line Re: Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: 
error: debputy internal-command dh-integration-generate-debs -p 
libjs-jquery-jstree .. returned exit code 1
has caused the Debian Bug report #1057934,
regarding libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy 
internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. 
returned exit code 1
to be marked as done.

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

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


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

Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-1
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
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js

Tracing dependencies for: jstree

/<>/dist/jstree.js

/<>/src/jstree.js
/<>/src/jstree.changed.js
/<>/src/jstree.checkbox.js
/<>/src/jstree.conditionalselect.js
/<>/src/jstree.contextmenu.js
/<>/src/jstree.dnd.js
/<>/src/jstree.massload.js
/<>/src/jstree.search.js
/<>/src/jstree.sort.js
/<>/src/jstree.state.js
/<>/src/jstree.types.js
/<>/src/jstree.unique.js
/<>/src/jstree.wholerow.js
/<>/src/vakata-jstree.js

sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/libjs-jquery-jstree/
   dh_debputy
Internal error in debputy
  - 8<  BEGIN STACK TRACE  8< -
Traceback (most recent call last):
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 2082, in 
main
command.handler(cmd_context)
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 1133, in 
_dh_integration_generate_debs
intermediate_manifest = manifest.finalize_data_tar_contents(

  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 1177, in 
finalize_data_tar_contents
intermediate_manifest = list(
^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180, in 
_generate_intermediate_manifest
tar_member = _path_to_tar_member(path, clamp_mtime_to)
 ^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159, in 
_path_to_tar_member
return TarMember.from_file(
   
  File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line 147, in 
from_file
"debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
  - 8<  END STACK TRACE  8< -
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs -p 
libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: 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: debputy
Source-Version: 

Bug#1058097: python-openstackclient: FTBFS: AttributeError: module 'sys' has no attribute 'builtin_module_names'

[Thomas Goirand]

I'm not getting what's been reported, but this now:

  File "", line 1360, in _find_and_load
  File "", line 1331, in 
_find_and_load_unlocked

  File "", line 935, in _load_unlocked
  File "", line 1176, in exec_module
  File "", line 58, in 
AttributeError: module 'sys' has no attribute 'byteorder'

Working on it... Though is it possible that this is a bug in the 
interpreter itself?


Cheers,

Thomas Goirand (zigo)

Bug#1057928: marked as done (boinctui: FTBFS: invalid use of incomplete type ‘ITEM’ {aka ‘struct tagITEM’})

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 20:34:04 +
with message-id 
and subject line Bug#1057928: fixed in boinctui 2.7.1-1
has caused the Debian Bug report #1057928,
regarding boinctui: FTBFS: invalid use of incomplete type ‘ITEM’ {aka ‘struct 
tagITEM’}
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.)


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

Package: src:boinctui
Version: 2.7.0-1
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
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.in
autoreconf -f -i
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoconf
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 gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for main in -lncursesw... yes
checking for main in -lformw... yes
checking for main in -lpanelw... yes
checking for main in -lmenuw... yes
checking for main in -lexpat... yes
checking for main in -lpthread... yes
checking for MD5_Init in -lgnutls-openssl ... yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for pthread.h... yes
checking for string.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for stdio.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdarg.h... yes
checking for sys/ioctl.h... yes
checking for arpa/inet.h... yes
checking for locale.h... yes
checking for malloc.h... yes
checking for sys/socket.h... yes
checking for netdb.h... yes
checking for signal.h... yes
checking for ctype.h... yes
checking for algorithm... yes
checking for string... yes
checking for list... yes
checking for vector... yes
checking for queue... yes
checking for stack... yes
checking for sstream... yes
checking for expat.h... yes
checking for gnutls/openssl.h... yes
checking for ncursesw/curses.h... yes
checking for ncursesw/form.h... yes
checking for ncursesw/panel.h... yes
checking for ncursesw/menu.h... yes
checking for _Bool... yes
checking for stdbool.h that conforms to C99... yes
checking for size_t... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether lstat correctly handles trailing slash... yes
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for mblen... yes
checking for memset... yes
checking for setlocale... yes
checking 

Bug#1058030: marked as done (pyferret: b-d on python3-all-dev, but not built for all supported Python3 versions)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 20:36:18 +
with message-id 
and subject line Bug#1058030: fixed in pyferret 7.6.5-5
has caused the Debian Bug report #1058030,
regarding pyferret: b-d on python3-all-dev, but not built for all supported 
Python3 versions
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.)


-- 
1058030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyferret
Version: 7.6.5-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.12 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.12-add.html
--- End Message ---
--- Begin Message ---
Source: pyferret
Source-Version: 7.6.5-5
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pyferret package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Dec 2023 19:22:01 +
Source: pyferret
Architecture: source
Version: 7.6.5-5
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1058030
Changes:
 pyferret (7.6.5-5) unstable; urgency=medium
 .
   * Ensure all python3 types are shipped. Closes: #1058030
   * Add fortran-support.mk makefile, start simplifcation
   * Drop patching files that were missing in 7.6.3
   * Include bash_completion file
Checksums-Sha1:
 7fb65748c265318da2a71f230f205e6af8a35d44 2301 pyferret_7.6.5-5.dsc
 78e1cea70eca105b5c25722d4eb872a5ac912a89 17860 pyferret_7.6.5-5.debian.tar.xz
Checksums-Sha256:
 b1ddb685b607f2e160dc42b82dcaa9d3576103fc740b371794b4850e0cecc51a 2301 
pyferret_7.6.5-5.dsc
 dbda42fbc05dfc9962ea4b5c531e12354c8dfb63536ca0b19fe8a6dd97ba34b1 17860 
pyferret_7.6.5-5.debian.tar.xz
Files:
 aef3b0bc927c45c073c57eba67758ae4 2301 science optional pyferret_7.6.5-5.dsc
 d4595145969a21859ae4e8c983a99706 17860 science optional 
pyferret_7.6.5-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmV7XBQACgkQy+a7Tl2a
06VfGw//R0IhDqI0OG2lpQcfGFZUt8f1dz90OI9hKm9R/8uY+OACNBjeQBvw9bPG
EJ7Xx+cMf4YeCokevSzA84hNk0QczQkuAMsti4RmhHyrms1qkIK6rXlMhbcKEJ7G
TcggEaUAIODN/Y8vWzd/N6Db3HQx5tKpR0ct1yQFrTYC9NwA9gUlCtYzMnU5VSPS
GRhonkEFRUkSOvhXy/QGoWX0sSYUwrJ3bpkTbzZYzqrTF3qcOpObPPELQXx/+31c
3JzUr9h/TTz8ZHRu800zEXioyK+6UqDsfiCG33HCH4P7W3p4afT0DIp5XyQ+MxST
Z/wphGJiWUFZMiIOT4S5TLnB/3mem0pYp/1lONflVpbcPa+8WFSF7IIFWQGJ//XM
n/vw2moKCEzSk60oyIQAUG2zG/9z2Ig6nS69p8cpMYcjiRDooCAtEfYEk+ufjJJp
H5XVxJWKLzQD8HdmZAZsm2pzPrQe3TNVtx1ZEQmH8zBuuyw617FiA1b/DvSYdPhU
fwJQXDETZYWI7PHAiFyk8i35ybfA+n3DGFHCw9a8Q38XpRfqEsPUj97uaBIFJeeN
uktAtdmXwh62OilZopGdzsgx9F3GaJ+5LFJK1GFiir38zFaKO29k7B+DyGQ46wVC
gkwlwk07J3HF07X3R71W8o1rCSJVBNHz4hqZTyMsBbENT6WzEUo=
=l92k
-END PGP SIGNATURE End Message ---

Processed: FTBFS: FAIL: TestCheckoutGit

[Debian Bug Tracking System]

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

> # Currently happening on bullseye
> found 1024506 20.10.5+dfsg1-1+deb11u2
Bug #1024506 {Done: Felix Geyer } [src:docker.io] docker.io: 
FTBFS: FAIL: builder/remotecontext/git TestCheckoutGit
Bug #1040141 {Done: Felix Geyer } [src:docker.io] FTBFS: 
FAIL: TestCheckoutGit
Marked as found in versions docker.io/20.10.5+dfsg1-1+deb11u2.
Marked as found in versions docker.io/20.10.5+dfsg1-1+deb11u2.
> thanks
Stopping processing here.

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

Bug#1024506: FTBFS: FAIL: TestCheckoutGit

[Santiago Vila]

# Currently happening on bullseye
found 1024506 20.10.5+dfsg1-1+deb11u2
thanks

Hi. This is happening on bullseye:

https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/docker.io.html

Thanks.

Bug#1058702: pius fails completely on bookworm and up

[Jérôme Charaoui]

On Thu, 14 Dec 2023 14:32:45 -0500 Antoine Beaupre  
wrote:> pius: error: GnuPG binary not found at /usr/bin/gpg2.


gpg2 hasn't been around for a long time. but maybe we can work around
this with:


Yeah I would also like like to see this patched.


pius: error: Keyring /home/anarcat/.gnupg/pubring.gpg doesn't exist

Nope! That doesn't work either! I have not dared to use the --keyring
argument to correct `.gnupg/pubring.kbx` keyring, for fear of
corruption, but clearly something is wrong here.


FWIW I've used --keyring and it didn't seem to corrupt the keyring or do 
anything bad, but you can also test it yourself on a copy of your 
keyring, the signatures thus produces will be just as valid.


Another thing that would be nice to fix upstream, or in the package at 
least.


-- Jérôme

Processed: unarchive for bullseye

[Debian Bug Tracking System]

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

> # This is happening in bullseye, a supported distribution (i.e. still not LTS)
> unarchive 1024506
Bug #1024506 {Done: Felix Geyer } [src:docker.io] docker.io: 
FTBFS: FAIL: builder/remotecontext/git TestCheckoutGit
Bug #1040141 {Done: Felix Geyer } [src:docker.io] FTBFS: 
FAIL: TestCheckoutGit
Unarchived Bug 1024506
Unarchived Bug 1040141
> tags 1024506 bullseye
Bug #1024506 {Done: Felix Geyer } [src:docker.io] docker.io: 
FTBFS: FAIL: builder/remotecontext/git TestCheckoutGit
Bug #1040141 {Done: Felix Geyer } [src:docker.io] FTBFS: 
FAIL: TestCheckoutGit
Added tag(s) bullseye.
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Bug#1058702: pius fails completely on bookworm and up

[Antoine Beaupre]

Package: pius
Version: 3.0.0-5
Severity: grave

I've been trying to use pius to sign things, and it's completely
failing me:

anarcat@angela:~$ pius -s BBB6CD4C98D74E1358A752A602293A6FA4E53473  
D477040C70C2156A5C298549BB7E9101495E6BF7
Welcome to PIUS, the PGP Individual UID Signer.

Usage: pius [options] -s   [ ...]
   pius [options] -A -r  -s 

pius: error: GnuPG binary not found at /usr/bin/gpg2.

gpg2 hasn't been around for a long time. but maybe we can work around
this with:

anarcat@angela:~[2]$ pius -b /usr/bin/gpg -s 
BBB6CD4C98D74E1358A752A602293A6FA4E53473  
D477040C70C2156A5C298549BB7E9101495E6BF7
Welcome to PIUS, the PGP Individual UID Signer.

Usage: pius [options] -s   [ ...]
   pius [options] -A -r  -s 

pius: error: Keyring /home/anarcat/.gnupg/pubring.gpg doesn't exist

Nope! That doesn't work either! I have not dared to use the --keyring
argument to correct `.gnupg/pubring.kbx` keyring, for fear of
corruption, but clearly something is wrong here.

-- System Information:
Debian Release: 12.4
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(1, 'experimental'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pius depends on:
ii  gnupg2.2.40-1.1
ii  python3  3.11.2-1+b1

pius recommends no packages.

pius suggests no packages.

-- no debconf information

Processed: Re: Bug#1057760: settle - upcoming rust-rusqlite update.

[Debian Bug Tracking System]

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

> severity 1057760 serious
Bug #1057760 [settle] settle - upcoming rust-rusqlite update.
Severity set to 'serious' from 'normal'
> tags 1057760 +ftbfs
Bug #1057760 [settle] settle - upcoming rust-rusqlite update.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: block bug

[Debian Bug Tracking System]

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

> block 1042746 by 1057451
Bug #1042746 [src:rust-hashbrown] rust-hashbrown: Please upgrade to v0.13
1042746 was blocked by: 1050086
1042746 was not blocking any bugs.
Added blocking bug(s) of 1042746: 1057451
> thanks
Stopping processing here.

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

Bug#1058690: marked as done (liblatex-tounicode-perl: trying to overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 2023.20231207-1)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 19:05:56 +
with message-id 
and subject line Bug#1058690: fixed in liblatex-tounicode-perl 0.54-2
has caused the Debian Bug report #1058690,
regarding liblatex-tounicode-perl: trying to overwrite .../ltx2unitxt.1.gz, 
which is also in package texlive-bibtex-extra 2023.20231207-1
to be marked as done.

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

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


-- 
1058690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblatex-tounicode-perl
Version: 0.54-1
Severity: serious

As a consequence of the upgrade of texlive-bibtex-extra to
2023.20231207-3:

[...]
Selecting previously unselected package liblatex-tounicode-perl.
(Reading database ... 711147 files and directories currently installed.)
Preparing to unpack .../00-liblatex-tounicode-perl_0.54-1_all.deb ...
Unpacking liblatex-tounicode-perl (0.54-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-seikpl/00-liblatex-tounicode-perl_0.54-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man1/ltx2unitxt.1.gz', which is also in 
package texlive-bibtex-extra 2023.20231207-1
[...]

It seems that the fix in bug 1058462 is incorrect or incomplete.

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

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

Versions of packages liblatex-tounicode-perl depends on:
ii  perl  5.36.0-10

liblatex-tounicode-perl recommends no packages.

liblatex-tounicode-perl suggests no packages.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: liblatex-tounicode-perl
Source-Version: 0.54-2
Done: Damyan Ivanov 

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

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated liblatex-tounicode-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Dec 2023 18:45:34 +
Source: liblatex-tounicode-perl
Architecture: source
Version: 0.54-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 1058690
Changes:
 liblatex-tounicode-perl (0.54-2) unstable; urgency=medium
 .
   * Team upload
 .
   * add Breaks/Replaces texlive-bibtex-extra (<< 2023.20231207-2)
 (Closes: #1058690)
Checksums-Sha1: 
 3109d68c26fa0d3432c214dea28a4ae14d9d8f21 2173 
liblatex-tounicode-perl_0.54-2.dsc
 9210b51115b899b8057e4b7677462499e4e75a1c 2116 
liblatex-tounicode-perl_0.54-2.debian.tar.xz
Checksums-Sha256: 
 10596fed6ef3ac2ed3298234111ac037733fb12041c6634daa4be84c91cde352 2173 
liblatex-tounicode-perl_0.54-2.dsc
 dcbd5926bdaabc5535930fbbe81288abb379c5bdb09c2c6d0ab7d796813ebdb5 2116 
liblatex-tounicode-perl_0.54-2.debian.tar.xz
Files: 
 af5d696dd82e9625466574b7fd090749 2173 perl optional 
liblatex-tounicode-perl_0.54-2.dsc
 dd89233acde208eebf67d697ac1467d8 2116 perl optional 
liblatex-tounicode-perl_0.54-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmV7TcUACgkQ276dTZnS
oAR1cA//W0rWnbDpB9WExGZHyYsIJqBZ2bHU60tE2aXSAk70ljdskDvBlCAaewsj
cXdmYiPMrGWkP71NTisXbHUr+jbk7qBmRTh/TVE2+oropv72L70LbfA3GHNRlKxs
68PihInUbzKPG2wtKtQn6gA3STaPwBXrraO2HXavi3xloyV511NUJXE9V6Nm8dyd
/ULJqQgiByv3yi1YIfEu4xw4voEYMpitmILpuxgKg+yZYVg8+NkoPnywB6ZQeXOn

Bug#1055723: rocketcea ftbfs with Python 3.12

[Alexandre Detiste]

Hi,

I ll try to fix this one if you permit.


Greetings

Bug#1058690: marked as pending in liblatex-tounicode-perl

[Damyan Ivanov]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/liblatex-tounicode-perl/-/commit/808faa5812566085b701bf764752e08177ebe4c1


add Breaks/Replaces texlive-bibtex-extra (<< 2023.20231207-2)

Closes: #1058690


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058690

Processed: Bug#1058690 marked as pending in liblatex-tounicode-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058690 [liblatex-tounicode-perl] liblatex-tounicode-perl: trying to 
overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 
2023.20231207-1
Added tag(s) pending.

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

Bug#1058698: mozilla-devscripts should be removed from testing/unstable

[Mechtilde]

Hello Mathias,

thanks for the hint,

At this time mozilla-devscript is needed when you want to build 
Mozilla-AddOns from the *.xpi.


So we need to elaborate another way to do it.

Some of my packages are affected


Kind regards


--
Mechtilde Stehmann

## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

Bug#1058698: mozilla-devscripts should be removed from testing/unstable

[Mechtilde]

Hello Mathias,

thanks for the hint,

At this time mozilla-devscript is needed when you want to build 
Mozilla-AddOns from the *.xpi.


So we need to elaborate another way to do it.

Some of my packages are affected


Kind regards


--
Mechtilde Stehmann

## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

Bug#1058220: marked as done (q2-sample-classifier: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 18:36:23 +
with message-id 
and subject line Bug#1058220: fixed in q2-sample-classifier 2023.7.0-2
has caused the Debian Bug report #1058220,
regarding q2-sample-classifier: FTBFS: AttributeError: module 'configparser' 
has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


-- 
1058220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: q2-sample-classifier
Version: 2023.7.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:310: python3.12 setup.py clean 
> /<>/versioneer.py:422: SyntaxWarning: invalid escape sequence 
> '\s'
>   LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
>   File "/<>/setup.py", line 16, in 
> version=versioneer.get_version(),
> 
>   File "/<>/versioneer.py", line 1481, in get_version
> return get_versions()["version"]
>^^
>   File "/<>/versioneer.py", line 1413, in get_versions
> cfg = get_config_from_root(root)
>   ^^
>   File "/<>/versioneer.py", line 343, in get_config_from_root
> parser = configparser.SafeConfigParser()
>  ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. 
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make[1]: *** [debian/rules:23: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/q2-sample-classifier_2023.7.0-1_unstable.log

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

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

If you reassign this bug to another package, please 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: q2-sample-classifier
Source-Version: 2023.7.0-2
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated q2-sample-classifier 
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, 14 Dec 2023 19:06:53 +0100
Source: q2-sample-classifier
Architecture: source
Version: 2023.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1058220
Changes:
 q2-sample-classifier (2023.7.0-2) unstable; urgency=medium
 .
   * python3.12.patch: new: port versioneer.py. (Closes: #1058220)
Checksums-Sha1:
 ad039de1c6623e413c2b93cae4c554968271a176 2449 
q2-sample-classifier_2023.7.0-2.dsc
 6d06ca32c1780c3a7a9741cc6b8ac3532d307283 7360 
q2-sample-classifier_2023.7.0-2.debian.tar.xz
Checksums-Sha256:
 ac6901cdb5ff612cb5407ee4c86083400578fa7d107c2842b9fc47df442dcf72 2449 
q2-sample-classifier_2023.7.0-2.dsc
 42db75c338a084bdcc987a196d624bbb264611bd77be6d389b7351f61daa7948 7360 
q2-sample-classifier_2023.7.0-2.debian.tar.xz
Files:
 4a24de6634017fc31ee04245afed6aa1 2449 science optional 

Processed: closing 1058405

[Debian Bug Tracking System]

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

> close 1058405 23.3.1-1
Bug #1058405 [src:mesa] mesa: FTBFS: 
../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp:127:16: error: 
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENDED_QVBR1_SUPPORT’ was not 
declared in this scope; did you mean 
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENSION1_SUPPORT’?
Marked as fixed in versions mesa/23.3.1-1.
Bug #1058405 [src:mesa] mesa: FTBFS: 
../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp:127:16: error: 
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENDED_QVBR1_SUPPORT’ was not 
declared in this scope; did you mean 
‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENSION1_SUPPORT’?
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1058334: marked as done (python-ete3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 18:05:20 +
with message-id 
and subject line Bug#1058334: fixed in python-ete3 3.1.3+dfsg-2
has caused the Debian Bug report #1058334,
regarding python-ete3: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ete3
Version: 3.1.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # link to examples
> find .pybuild -name build -type d -exec ln -s /<>/examples \{\} 
> \;
> dh_auto_test
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_ete3/build; 
> python3.12 -m pytest -k "not test_ncbiquery and not test_ncbi_compare and not 
> test_get_topology and not test_01tree_annotation and not 
> test_00_update_database and not test_merged_id and not test_renderer" 
> ete3/test/test_api.py
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 53 items / 7 deselected / 46 selected
> 
> ete3/test/test_api.py ..FFF. 
> [100%]
> 
> === FAILURES 
> ===
> ___ Test_Coretype_ArrayTable.test_arraytable_parser 
> 
> 
> self =  testMethod=test_arraytable_parser>
> 
> def test_arraytable_parser(self):
> """ Tests reading numneric tables"""
> A = ArrayTable(expression)
> self.assertEqual(A.get_row_vector("A").tolist(), \
>  [-1.23, -0.81, 1.79, 0.78,-0.42,-0.69, 0.58])
> self.assertEqual(A.get_several_row_vectors(["A","C"]).tolist(), \
>  [[-1.23, -0.81, 1.79, 0.78, -0.42, -0.69, 0.58],
>  [-2.19, 0.13, 0.65, -0.51, 0.52, 1.04, 0.36]])
> 
> self.assertEqual(A.get_several_column_vectors(["col2", 
> "col7"]).tolist(), \
>  [[-0.81005, -0.93995,\
> 0.13, -0.97998, 
> -0.82996,\
> -1.1101, -1.1699,\
> -1.25],
>   [0.57996, 1.1201, \
>0.35999, 0.93005, \
>0.65002, 0.47998, \
>0.26001, 0.77002]])
> 
> 
> self.assertEqual(A.get_column_vector("col4").tolist(), \
>  [0.78003, 0.35999, \
>   -0.51001, -0.76001, 
> \
>   0.070007, -0.14001, 
> \
>   0.23001, -0.2])
> 
> A.remove_column("col4")
> >   self.assert_(A.get_column_vector("col4") is None )
> E   AttributeError: 'Test_Coretype_ArrayTable' object has no attribute 
> 'assert_'. Did you mean: 'assertIn'?
> 
> ete3/test/test_arraytable.py:36: AttributeError
> _ TestEvolEvolTree.test_labelling_tree 
> _
> 
> self = 
> 
> def test_labelling_tree(self):
> tree = EvolTree (WRKDIR + 'tree.nw')
> tree.workdir = 'protamine/PRM1/paml/'
> random_swap(tree)
> tree.link_to_evol_model (WRKDIR + 'paml/fb/fb.out', 'fb')
> >   self.assert_(check_annotation (tree))
> E   AttributeError: 'TestEvolEvolTree' object has no attribute 'assert_'. 
> Did you mean: 'assertIn'?
> 
> ete3/test/test_evol.py:132: AttributeError
> ___ TestEvolEvolTree.test_load_model 
> ___
> 
> self = 
> 
> def test_load_model(self):
> tree = EvolTree (WRKDIR + 'tree.nw')
> tree.workdir = 'protamine/PRM1/paml/'
> tree.link_to_evol_model (WRKDIR + 'paml/fb/fb.out', 'fb')
> tree.link_to_evol_model (WRKDIR + 'paml/M1/M1.out', 'M1')
> tree.link_to_evol_model (WRKDIR + 'paml/M2/M2.out', 'M2')
> 

Processed: Bug#1058220 marked as pending in q2-sample-classifier

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058220 [src:q2-sample-classifier] q2-sample-classifier: FTBFS: 
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did 
you mean: 'RawConfigParser'?
Added tag(s) pending.

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

Bug#1058220: marked as pending in q2-sample-classifier

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/q2-sample-classifier/-/commit/446dfe546dd9004b38f4dd9fa9c6ad126240f666


python3.12.patch: new: port versioneer.py.

Closes: #1058220


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058220

Bug#1058657: python3-apt: undefined symbol: PyAptWarning, breaks nala

[Hendrik Lehmbruch]

Package: python3-apt
Version: 2.7.2
Followup-For: Bug #1058657
X-Debbugs-Cc: hlehmbr...@gmx.net

Dear Maintainer,

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

   * What led up to the situation?

Running nala upgrade

   * What was the outcome of this action?

--- snipp ---

Traceback (most recent call last):
File "/usr/bin/nala", line 5, in 
 from nala.__main__ import main
File "/usr/lib/python3/dist-packages/nala/__main__.py", line 31, in 
 import nala.fetch as _fetch  # pylint: disable=unused-import
 ^^^
File "/usr/lib/python3/dist-packages/nala/fetch.py", line 60, in 
 from nala.downloader import print_error
File "/usr/lib/python3/dist-packages/nala/downloader.py", line 70, in 
 from nala.error import ExitCode, FileDownloadError
File "/usr/lib/python3/dist-packages/nala/error.py", line 38, in 
 from nala.debfile import NalaBaseDep, NalaDebPackage, NalaDep
File "/usr/lib/python3/dist-packages/nala/debfile.py", line 32, in 
 from apt.debfile import DebPackage
File "/usr/lib/python3/dist-packages/apt/debfile.py", line 28, in 
 import apt_inst ImportError: /usr/lib/python3/dist-
packages/apt_inst.cpython-311-x86_64-linux-gnu.so: undefined symbol:
PyAptWarning

- snapp ---

apt policy nala
nala:
  Installed: 0.14.0
  Candidate: 0.14.0


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

Kernel: Linux 6.6.7-1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-apt depends on:
ii  distro-info-data   0.60
ii  libapt-pkg6.0  2.7.7
ii  libc6  2.37-13
ii  libgcc-s1  13.2.0-8
ii  libstdc++6 13.2.0-8
ii  python-apt-common  2.7.2
ii  python33.11.6-1

Versions of packages python3-apt recommends:
ii  iso-codes4.15.0-1
ii  lsb-release  12.0-2

Versions of packages python3-apt suggests:
ii  apt 2.7.7
pn  python-apt-doc  

-- no debconf information

Bug#1055719: marked as done (python-pomegranate ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 16:42:19 -0100
with message-id 

and subject line python-pomegranate ftbfs with Python 3.12
has caused the Debian Bug report #1055719,
regarding python-pomegranate 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.)


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

Package: src:python-pomegranate
Version: 0.14.8-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Error compiling Cython file:

...

cpdef disable_gpu():
global GPU
GPU = False

cdef ndarray_wrap_cpointer(void* data, numpy.npy_intp n):
 ^


pomegranate/utils.pyx:120:5: Function signature does not match previous 
declaration
performance hint: pomegranate/utils.pyx:157:5: Exception check on 'mdot' 
will always require the GIL to be acquired.

Possible solutions:
	1. Declare the function as 'noexcept' if you control the definition and 
you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on the function to allow an error code to 
be returned.

Compiling pomegranate/BayesClassifier.pyx because it changed.
Compiling pomegranate/BayesianNetwork.pyx because it changed.
Compiling pomegranate/FactorGraph.pyx because it changed.
Compiling pomegranate/MarkovChain.pyx because it changed.
Compiling pomegranate/MarkovNetwork.pyx because it changed.
Compiling pomegranate/NaiveBayes.pyx because it changed.
Compiling pomegranate/base.pyx because it changed.
Compiling pomegranate/bayes.pyx because it changed.
Compiling pomegranate/gmm.pyx because it changed.
Compiling pomegranate/hmm.pyx because it changed.
Compiling pomegranate/kmeans.pyx because it changed.
Compiling pomegranate/parallel.pyx because it changed.
Compiling pomegranate/utils.pyx because it changed.
Compiling pomegranate/distributions/BernoulliDistribution.pyx because it 
changed.

Compiling pomegranate/distributions/BetaDistribution.pyx because it changed.
Compiling pomegranate/distributions/ConditionalProbabilityTable.pyx 
because it changed.
Compiling pomegranate/distributions/DirichletDistribution.pyx because it 
changed.
Compiling pomegranate/distributions/DiscreteDistribution.pyx because it 
changed.
Compiling pomegranate/distributions/ExponentialDistribution.pyx because 
it changed.
Compiling pomegranate/distributions/GammaDistribution.pyx because it 
changed.
Compiling 
pomegranate/distributions/IndependentComponentsDistribution.pyx because 
it changed.
Compiling pomegranate/distributions/JointProbabilityTable.pyx because it 
changed.

Compiling pomegranate/distributions/KernelDensities.pyx because it changed.
Compiling pomegranate/distributions/LogNormalDistribution.pyx because it 
changed.
Compiling pomegranate/distributions/MultivariateGaussianDistribution.pyx 
because it changed.
Compiling pomegranate/distributions/NormalDistribution.pyx because it 
changed.
Compiling pomegranate/distributions/PoissonDistribution.pyx because it 
changed.
Compiling pomegranate/distributions/UniformDistribution.pyx because it 
changed.

Compiling pomegranate/distributions/distributions.pyx because it changed.
[ 1/29] Cythonizing pomegranate/BayesClassifier.pyx
[ 2/29] Cythonizing pomegranate/BayesianNetwork.pyx
[ 3/29] Cythonizing pomegranate/FactorGraph.pyx
[ 4/29] Cythonizing pomegranate/MarkovChain.pyx
[ 5/29] Cythonizing pomegranate/MarkovNetwork.pyx
[ 6/29] Cythonizing pomegranate/NaiveBayes.pyx
[ 7/29] Cythonizing pomegranate/base.pyx
[ 8/29] Cythonizing pomegranate/bayes.pyx
[ 9/29] Cythonizing pomegranate/distributions/BernoulliDistribution.pyx
[10/29] Cythonizing pomegranate/distributions/BetaDistribution.pyx
[11/29] Cythonizing 
pomegranate/distributions/ConditionalProbabilityTable.pyx

[12/29] Cythonizing pomegranate/distributions/DirichletDistribution.pyx
[13/29] Cythonizing pomegranate/distributions/DiscreteDistribution.pyx
[14/29] Cythonizing pomegranate/distributions/ExponentialDistribution.pyx
[15/29] Cythonizing pomegranate/distributions/GammaDistribution.pyx
[16/29] Cythonizing 
pomegranate/distributions/IndependentComponentsDistribution.pyx

[17/29] Cythonizing pomegranate/distributions/JointProbabilityTable.pyx
[18/29] Cythonizing pomegranate/distributions/KernelDensities.pyx
[19/29] Cythonizing pomegranate/distributions/LogNormalDistribution.pyx
[20/29] Cythonizing 

Bug#1055705: marked as done (pyreadstat ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 16:37:28 -0100
with message-id 

and subject line pyreadstat ftbfs with Python 3.12
has caused the Debian Bug report #1055705,
regarding pyreadstat 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.)


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

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

pyreadstat ftbfs with Python 3.12:

[...]
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
Traceback (most recent call last):
  File "/<>/setup.py", line 32, in 
raise Exception(msg)
Exception: Cython version 0.28 or newer required
E: pybuild pybuild:395: configure: plugin distutils failed with: exit 
code=1: python3.12 setup.py config
dh_auto_configure: error: pybuild --configure -i python{version} -p 
"3.12 3.11" returned exit code 13
--- End Message ---
--- Begin Message ---
pyreadstat 1.2.2-1+b1 built successfully with cython 0.29.36-3.
The failure with cython 3.0.x is #1056847.--- End Message ---

Processed: Bug#1058334 marked as pending in python-ete3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058334 [src:python-ete3] python-ete3: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.

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

Bug#1058334: marked as pending in python-ete3

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/python-ete3/-/commit/11f450737651b73905a5eed6ac1e36824e9a4cc9


python3.12.patch: new: fix test failures.

Closes: #1058334


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058334

Bug#1058698: mozilla-devscripts should be removed from testing/unstable

[Matthias Klose]

Package: src:mozilla-devscripts
Version: 0.54.2+nmu1
Severity: serious
Tags: sid trixie

mozilla-devscripts should be removed from testing/unstable. devscripts 
already dropped the dependency, and python3-librdf isn't built anymore.

Bug#1057139: Update

[Sarisky, Dan]

Is anyone monitoring these bug reports?  Any suggestions on next steps?

Bug#1050187: mvdsv: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find attached a patch (build-tested only).
>From e7127e5a2fa57f84dc12cc6d63671c872c48d28b Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Thu, 14 Dec 2023 18:31:41 +0200
Subject: [PATCH] Port to PCRE2 (#1050187)

---
 debian/changelog   |   7 +
 debian/control |   2 +-
 debian/patches/pcre2.patch | 316 +
 debian/patches/series  |   1 +
 4 files changed, 325 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/pcre2.patch

diff --git a/debian/changelog b/debian/changelog
index 0f44607..9874ff2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mvdsv (0.35-7) UNRELEASED; urgency=medium
+
+  * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #1050187).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov   Thu, 14 Dec 2023 18:30:40 +0200
+
 mvdsv (0.35-6) unstable; urgency=high
 
   * Fix build failure on big endian systems
diff --git a/debian/control b/debian/control
index d53102d..f69173d 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
libcurl4-openssl-dev,
-   libpcre3-dev,
+   libpcre2-dev,
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/games-team/mvdsv
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..efad8d1
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,316 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/1050187
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-14
+---
+
+--- mvdsv.orig/CMakeLists.txt
 mvdsv/CMakeLists.txt
+@@ -90,18 +90,14 @@
+ 
##
+  
+ # Check for PCRE. if found, include it; if not found, use bundled PCRE.
+-find_library(PCRE_LIBRARIES pcre)
++find_library(PCRE_LIBRARIES pcre2-8)
+ if(PCRE_LIBRARIES)
+   set(PCRE_FOUND 1)
+-  find_path(PCRE_INCLUDE_DIR pcre.h)
++  find_path(PCRE_INCLUDE_DIR pcre2.h)
+ endif(PCRE_LIBRARIES)
+ 
+ if(NOT PCRE_FOUND)
+-  message(STATUS "PCRE library not found. Using bundled PCRE instead.")
+-  list(APPEND SRC_COMMON
+-  "${DIR_SRC}/pcre/get.c"
+-  "${DIR_SRC}/pcre/pcre.c"
+-  )
++  message(FATAL_ERROR "PCRE library not found.")
+ else()
+   message(STATUS "Found PCRE: ${PCRE_LIBRARIES}")
+ endif()
+--- mvdsv.orig/src/sv_demo_misc.c
 mvdsv/src/sv_demo_misc.c
+@@ -22,7 +22,8 @@
+ #ifndef CLIENTONLY
+ #include "qwsvdef.h"
+ #ifndef SERVERONLY
+-#include "pcre.h"
++#define PCRE2_CODE_UNIT_WIDTH 8
++#include 
+ #endif
+ 
+ #define MAX_DEMOINFO_SIZE (1024 * 200)
+@@ -342,8 +343,10 @@
+   int files[MAX_DIRFILES + 1];
+ 
+   int r;
+-  pcre*preg;
+-  const char  *errbuf;
++  size_t erroffset;
++  pcre2_code *preg;
++  pcre2_match_data *md;
++  PCRE2_UCHAR errbuf[120];
+ 
+   memset(files, 0, sizeof(files));
+ 
+@@ -361,26 +364,29 @@
+   {
+   if (use_regex)
+   {
+-  if (!(preg = 
pcre_compile(Q_normalizetext(Cmd_Argv(j)), PCRE_CASELESS, , , NULL)))
++  if (!(preg = 
pcre2_compile((PCRE2_SPTR)Q_normalizetext(Cmd_Argv(j)), PCRE2_ZERO_TERMINATED, 
PCRE2_CASELESS, , , NULL)))
+   {
+-  Con_Printf("Sys_listdir: 
pcre_compile(%s) error: %s at offset %d\n",
+- Cmd_Argv(j), errbuf, r);
+-  pcre_free(preg);
++  pcre2_get_error_message(r, errbuf, 
sizeof(errbuf));
++  Con_Printf("Sys_listdir: 
pcre2_compile(%s) error: %s at offset %lu\n",
++ Cmd_Argv(j), errbuf, 
erroffset);
+   break;
+   }
+-  switch (r = pcre_exec(preg, NULL, list->name,
+-strlen(list->name), 0, 0, 
NULL, 0))
++  md = pcre2_match_data_create_from_pattern(preg, 
NULL);
++  switch (r = pcre2_match(preg, 
(PCRE2_SPTR)list->name,
++  strlen(list->name), 0, 
0, md, NULL))
+   {
+   case 0:
+-  pcre_free(preg);
++  pcre2_match_data_free(md);
++  pcre2_code_free(preg);
+   continue;
+-  case 

Processed: Re: Bug#1050187: mvdsv: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1050187 [src:mvdsv] mvdsv: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#1058241: marked as done (python-dracclient: FTBFS: AttributeError: 'UtilsTestCase' object has no attribute 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 16:04:33 +
with message-id 
and subject line Bug#1058241: fixed in python-dracclient 3.1.0-5
has caused the Debian Bug report #1058241,
regarding python-dracclient: FTBFS: AttributeError: 'UtilsTestCase' object has 
no attribute 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?
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.)


-- 
1058241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dracclient
Version: 3.1.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> ERROR: test_change_physical_disk_state_raise_drac_operation_other 
> (dracclient.tests.test_raid.ClientRAIDManagementTestCase.test_change_physical_disk_state_raise_drac_operation_other)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/requests_mock/mocker.py", line 317, in 
> inner
> return func(*args, **kwargs)
>^
>   File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
> return func(*newargs, **newkeywargs)
>^
>   File "/<>/dracclient/tests/test_raid.py", line 1214, in 
> test_change_physical_disk_state_raise_drac_operation_other
> self.assertRaisesRegexp(
> ^^^
> AttributeError: 'ClientRAIDManagementTestCase' object has no attribute 
> 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?
> 
> ==
> ERROR: test_change_physical_disk_state_raise_other 
> (dracclient.tests.test_raid.ClientRAIDManagementTestCase.test_change_physical_disk_state_raise_other)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/requests_mock/mocker.py", line 317, in 
> inner
> return func(*args, **kwargs)
>^
>   File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
> return func(*newargs, **newkeywargs)
>^
>   File "/<>/dracclient/tests/test_raid.py", line 1238, in 
> test_change_physical_disk_state_raise_other
> self.assertRaisesRegexp(
> ^^^
> AttributeError: 'ClientRAIDManagementTestCase' object has no attribute 
> 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?
> 
> ==
> ERROR: test_get_all_wsman_resource_attrs_missing_text 
> (dracclient.tests.test_utils.UtilsTestCase.test_get_all_wsman_resource_attrs_missing_text)
> --
> Traceback (most recent call last):
>   File "/<>/dracclient/tests/test_utils.py", line 153, in 
> test_get_all_wsman_resource_attrs_missing_text
> self.assertRaisesRegexp(
> ^^^
> AttributeError: 'UtilsTestCase' object has no attribute 'assertRaisesRegexp'. 
> Did you mean: 'assertRaisesRegex'?
> 
> ==
> ERROR: test_get_wsman_resource_attr_missing_attr 
> (dracclient.tests.test_utils.UtilsTestCase.test_get_wsman_resource_attr_missing_attr)
> --
> Traceback (most recent call last):
>   File "/<>/dracclient/tests/test_utils.py", line 73, in 
> test_get_wsman_resource_attr_missing_attr
> self.assertRaisesRegexp(
> ^^^
> AttributeError: 'UtilsTestCase' object has no attribute 'assertRaisesRegexp'. 
> Did you mean: 'assertRaisesRegex'?
> 
> ==
> ERROR: test_get_wsman_resource_attr_missing_text 
> (dracclient.tests.test_utils.UtilsTestCase.test_get_wsman_resource_attr_missing_text)
> --
> Traceback (most recent call last):
>   File "/<>/dracclient/tests/test_utils.py", line 100, in 
> test_get_wsman_resource_attr_missing_text
> self.assertRaisesRegexp(
> ^^^
> AttributeError: 'UtilsTestCase' object has no attribute 'assertRaisesRegexp'. 
> Did you 

Bug#1056422: marked as done (masakari's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 16:58:26 +0100
with message-id 
and subject line Already fixed
has caused the Debian Bug report #1056422,
regarding masakari's autopkg tests fail 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.)


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

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


masakari's autopkg tests fail with Python 3.12:

[...]
648s autopkgtest [18:34:06]: test autodep8-python3: [---
648s Testing with python3.12:
648s Traceback (most recent call last):
648s   File "", line 1, in 
648s   File "/usr/lib/python3/dist-packages/masakari/__init__.py", line 
34, in 

648s import eventlet  # noqa
648s ^^^
648s   File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 
17, in 

648s from eventlet import convenience
648s   File "/usr/lib/python3/dist-packages/eventlet/convenience.py", 
line 161, in 

648s from eventlet.green import ssl
648s   File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 
25, in 

648s _original_wrap_socket = __ssl.wrap_socket
648s ^
648s AttributeError: module 'ssl' has no attribute 'wrap_socket'
648s autopkgtest [18:34:06]: test autodep8-python3: ---]
--- End Message ---
--- Begin Message ---

Hi,

The reported issue here was in eventlet. The remaining problems were 
fixed in the upload of masakari 16.0.0-2 (closing bug #1058212).


Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#1058241: marked as pending in python-dracclient

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058241 in python-dracclient 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/openstack-team/clients/python-dracclient/-/commit/4becfa2b99c1a47f89ffb9d5c3b324411b5ed026


* Add py3.12-assertRaisesRegexp-becomes-assertRaisesRegex.patch
(Closes: #1058241).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058241

Processed: Bug#1058241 marked as pending in python-dracclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058241 [src:python-dracclient] python-dracclient: FTBFS: AttributeError: 
'UtilsTestCase' object has no attribute 'assertRaisesRegexp'. Did you mean: 
'assertRaisesRegex'?
Added tag(s) pending.

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

Processed: severity of 1058678 is serious

[Debian Bug Tracking System]

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

> severity 1058678 serious
Bug #1058678 [src:blt] blt: disable jpeg support
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1058315: python3-nose: from nose.tools import assert_equals, assert_raises FAILS

[Thomas Goirand]

Hi,

As you may see by the reassigned bug, doing this:
from nose.tools import assert_equals, assert_raises

fails under Python 3.12, when it works under 3.11.

Cheers,

Thomas Goirand (zigo)

Bug#1057809: marked as done (python-pysam ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 14:12:37 -0100
with message-id 

and subject line python-pysam ftbfs with Python 3.12
has caused the Debian Bug report #1057809,
regarding python-pysam 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.)


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

Package: src:python-pysam
Version: 0.22.0+ds-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-pysam ftbfs with Python 3.12, didn't check for any follow-up errors:

[...]
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/pysam -I/usr/include -I/<>/samtools 
-I/<>/samtools/lz4 -I/<>/bcftools 
-I/<> -I/usr/include/python3.12 -c pysam/libchtslib.c -o 
build/temp.linux-x86_64-cpython-312/pysam/libchtslib.o -Wno-unused 
-Wno-strict-prototypes -Wno-sign-compare 
-Wno-error=declaration-after-statement

pysam/libchtslib.c: In function ‘__pyx_f_5pysam_10libchtslib_set_verbosity’:
pysam/libchtslib.c:1387:32: error: ‘_PyCFrame’ has no member named 
‘use_tracing’

 1387 |  (unlikely((tstate)->cframe->use_tracing) &&\
  |^~
pysam/libchtslib.c:958:43: note: in definition of macro ‘unlikely’
  958 |   #define unlikely(x) __builtin_expect(!!(x), 0)
  |   ^
pysam/libchtslib.c:1426:15: note: in expansion of macro ‘__Pyx_IsTracing’
 1426 |   if (__Pyx_IsTracing(tstate, 1, 1)) {\
  |   ^~~
--- End Message ---
--- Begin Message ---
As noted above, python-pysam 0.22.0+ds-1+b1 built successfully with
cython3 0.29.36-3.1.--- End Message ---

Processed: reassign 1058315 python3-nose

[Debian Bug Tracking System]

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

> reassign 1058315 python3-nose
Bug #1058315 [src:python-sure] python-sure: FTBFS: ERROR: Failure: ImportError 
(cannot import name 'assert_equals' from 'nose.tools' 
(/usr/lib/python3/dist-packages/nose/tools/__init__.py))
Bug reassigned from package 'src:python-sure' to 'python3-nose'.
No longer marked as found in versions python-sure/2.0.0-3.
Ignoring request to alter fixed versions of bug #1058315 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#1058690: liblatex-tounicode-perl: trying to overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 2023.20231207-1

[Andrius Merkys]

Control: tags -1 + patch

Hello,

On 2023-12-14 16:07, Vincent Lefevre wrote:

Package: liblatex-tounicode-perl
Version: 0.54-1
Severity: serious

As a consequence of the upgrade of texlive-bibtex-extra to
2023.20231207-3:

[...]
Selecting previously unselected package liblatex-tounicode-perl.
(Reading database ... 711147 files and directories currently installed.)
Preparing to unpack .../00-liblatex-tounicode-perl_0.54-1_all.deb ...
Unpacking liblatex-tounicode-perl (0.54-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-seikpl/00-liblatex-tounicode-perl_0.54-1_all.deb 
(--unpack):
  trying to overwrite '/usr/share/man/man1/ltx2unitxt.1.gz', which is also in 
package texlive-bibtex-extra 2023.20231207-1
[...]

It seems that the fix in bug 1058462 is incorrect or incomplete.


I agree that this bug is due to the incomplete fix for #1058462. The 
offending files were removed from texlive-bibtex-extra, but 
Breaks+Replaces were not added to liblatex-tounicode-perl. Thus to 
complete the fix one should add the following to liblatex-tounicode-perl:


Breaks: texlive-bibtex-extra (<< 2023.20231207-2)
Replaces: texlive-bibtex-extra (<< 2023.20231207-2)

Thanks,
Andrius

Processed: Re: Bug#1058690: liblatex-tounicode-perl: trying to overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 2023.20231207-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1058690 [liblatex-tounicode-perl] liblatex-tounicode-perl: trying to 
overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 
2023.20231207-1
Added tag(s) patch.

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

Bug#1056045: marked as done (healpy ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 13:59:00 -0100
with message-id 

and subject line healpy ftbfs with Python 3.12
has caused the Debian Bug report #1056045,
regarding healpy 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.)


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

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

healpy ftbfs with Python 3.12, although it also fails the same way with 
3.11.  Probably you need to wait until we have built all the depending 
modules when adding 3.12.



[...]
= test session starts 
==
platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 -- 
/usr/bin/python3.11

cachedir: .pytest_cache
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase(PosixPath('/<>/.pybuild/cpython3_3.11_healpy/build/.hypothesis/examples'))

rootdir: /<>
configfile: setup.cfg
plugins: cov-4.1.0, doctestplus-1.0.0, arraydiff-0.5.0, 
hypothesis-6.88.1, cython-0.1.1, mock-3.11.1, astropy-header-0.2.2, 
filter-subpackage-0.1.2, remotedata-0.4.1, astropy-0.11.0

collecting ... collected 0 items / 1 error

 ERRORS 

 ERROR collecting test session 
_
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:641: in 
_importconftest

mod = import_path(conftestpath, mode=importmode, root=rootpath)
/usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path
importlib.import_module(module_name)
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1204: in _gcd_import
???
:1176: in _find_and_load
???
:1126: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1204: in _gcd_import
???
:1176: in _find_and_load
???
:1126: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1204: in _gcd_import
???
:1176: in _find_and_load
???
:1147: in _find_and_load_unlocked
???
:690: in _load_unlocked
???
:940: in exec_module
???
:241: in _call_with_frames_removed
???
healpy/__init__.py:90: in 
from ._query_disc import query_disc, query_strip, query_polygon, 
boundaries

healpy/src/_query_disc.pyx:10: in init healpy._query_disc
???
E   ModuleNotFoundError: No module named '_pixelfunc'
=== short test summary info 


ERROR ../../.. - ModuleNotFoundError: No module named '_pixelfunc'
 Interrupted: 1 error during collection 

=== 1 error in 0.28s 
===
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=2: 
cd /<>/.pybuild/cpython3_3.11_healpy/build; python3.11 -m 
pytest --doctest-modules
--- End Message ---
--- Begin Message ---
healpy 1.16.1-1+b3 built successfully with cython3 0.29.36-3.
The failure with cython 3.0.1 is #1056805.--- End Message ---

Bug#1058439: marked as done (python-os-api-ref: FTBFS: AttributeError: 'TestMicroversions' object has no attribute 'assertRegexpMatches')

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 14:49:39 +
with message-id 
and subject line Bug#1058439: fixed in python-os-api-ref 2.3.0+ds1-3
has caused the Debian Bug report #1058439,
regarding python-os-api-ref: FTBFS: AttributeError: 'TestMicroversions' object 
has no attribute 'assertRegexpMatches'
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.)


-- 
1058439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-os-api-ref
Version: 2.3.0+ds1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2 
> 'os_api_ref.tests.(?!.*test_basic_example\.TestBasicExample\.test_parameters|.*test_basic_example\.TestBasicExample\.test_rest_response.*)'
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.12 = disabled ]
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -x /usr/bin/python3-stestr ]
> + STESTR=stestr
> + rm -rf .stestr
> + PYTHON=python3.12 stestr run --parallel --subunit 
> os_api_ref.tests.(?!.*test_basic_example\.TestBasicExample\.test_parameters|.*test_basic_example\.TestBasicExample\.test_rest_response.*)
> + subunit2pyunit
> os_api_ref.tests.test_os_api_ref.TestOs_api_ref.test_something
> os_api_ref.tests.test_os_api_ref.TestOs_api_ref.test_something ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_empty_parameter_file
> os_api_ref.tests.test_warnings.TestWarnings.test_empty_parameter_file ... ok
> os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all
> os_api_ref.tests.test_basic_example.TestBasicExample.test_expand_all ... ok
> os_api_ref.tests.test_microversions.TestMicroversions.test_js_declares
> os_api_ref.tests.test_microversions.TestMicroversions.test_js_declares ... ok
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_method
> os_api_ref.tests.test_basic_example.TestBasicExample.test_rest_method ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_invalid_parameter_definition
> os_api_ref.tests.test_warnings.TestWarnings.test_invalid_parameter_definition 
> ... ok
> os_api_ref.tests.test_microversions.TestMicroversions.test_mv_selector
> os_api_ref.tests.test_microversions.TestMicroversions.test_mv_selector ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_field
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_field ... FAIL
> os_api_ref.tests.test_microversions.TestMicroversions.test_rest_method
> os_api_ref.tests.test_microversions.TestMicroversions.test_rest_method ... 
> FAIL
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_lookup_name
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_lookup_name ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_path_parameter_in_stanza
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_path_parameter_in_stanza
>  ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_no_parameters_set
> os_api_ref.tests.test_warnings.TestWarnings.test_no_parameters_set ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_out_of_order
> os_api_ref.tests.test_warnings.TestWarnings.test_out_of_order ... ok
> os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist
> os_api_ref.tests.test_warnings.TestWarnings.test_parameter_file_not_exist ... 
> ok
> 
> ==
> FAIL: os_api_ref.tests.test_warnings.TestWarnings.test_missing_field
> os_api_ref.tests.test_warnings.TestWarnings.test_missing_field
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File "/<>/os_api_ref/tests/test_warnings.py", line 60, in 
> test_missing_field
> self.assertIn(
>   File 

Bug#1056046: marked as done (pyregion ftbfs with Python 3.12 (and cython 3.0.5))

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 13:46:42 -0100
with message-id 

and subject line pyregion ftbfs with Python 3.12 (and cython 3.0.5)
has caused the Debian Bug report #1056046,
regarding pyregion ftbfs with Python 3.12 (and cython 3.0.5)
to be marked as done.

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

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


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

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

pyregion ftbfs with Python 3.12 (and cython 3.0.5):

[...]
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:381: 
FutureWarning: Cython directive 'language_level' not set, using '3str' 
for now (Py3). This has changed from earlier releases! File: 
/<>/pyregion/_region_filter.pyx

  tree = Parsing.p_module(s, pxd, full_module_name)

Error compiling Cython file:

...

cdef extern from "stdlib.h":
pass


cimport  c_numpy
 ^


pyregion/_region_filter.pyx:9:9: 'c_numpy.pxd' not found

Error compiling Cython file:

...
cdef extern from "stdlib.h":
pass


cimport  c_numpy
from c_numpy cimport npy_bool
^


pyregion/_region_filter.pyx:10:0: 'c_numpy/npy_bool.pxd' not found

Error compiling Cython file:

...
pass


cimport  c_numpy
from c_numpy cimport npy_bool
cimport c_python
^


pyregion/_region_filter.pyx:11:8: 'c_python.pxd' not found

Error compiling Cython file:

...
return RegionAnd(self, o)

def __or__(self, RegionBase o):
return RegionOr(self, o)

cdef npy_bool _inside(self, double x, double y):
 ^


pyregion/_region_filter.pyx:103:9: 'npy_bool' is not a type identifier

Error compiling Cython file:

...
ny = c_python.PySequence_GetItem(shape, 0)
nx = c_python.PySequence_GetItem(shape, 1)

return self._mask(nx, ny)

cdef c_numpy.ndarray _mask(self, c_numpy.npy_intp nx, 
c_numpy.npy_intp ny):

 ^


pyregion/_region_filter.pyx:134:9: 'ndarray' is not a type identifier

Error compiling Cython file:

...
ny = c_python.PySequence_GetItem(shape, 0)
nx = c_python.PySequence_GetItem(shape, 1)

return self._mask(nx, ny)

cdef c_numpy.ndarray _mask(self, c_numpy.npy_intp nx, 
c_numpy.npy_intp ny):

 ^


pyregion/_region_filter.pyx:134:37: 'npy_intp' is not a type identifier

Error compiling Cython file:

...
ny = c_python.PySequence_GetItem(shape, 0)
nx = c_python.PySequence_GetItem(shape, 1)

return self._mask(nx, ny)

cdef c_numpy.ndarray _mask(self, c_numpy.npy_intp nx, 
c_numpy.npy_intp ny):

  ^


pyregion/_region_filter.pyx:134:58: 'npy_intp' is not a type identifier

Error compiling Cython file:

...
cdef RegionBase child_region

def __init__(self, RegionBase child_region):
self.child_region = child_region

cdef npy_bool _inside(self, double x, double y):
 ^


pyregion/_region_filter.pyx:246:9: 'npy_bool' is not a type identifier

Error compiling Cython file:

...

cdef class RegionOrList(RegionList):
"""
>>> r = RegionOrList(r1, r2, r3, r4, ...)
"""
cdef npy_bool _inside(self, double x, double y):
 ^


pyregion/_region_filter.pyx:286:9: 'npy_bool' is not a type identifier

Error compiling Cython file:

...
cdef class RegionAndList(RegionList):

Bug#1056038: marked as done (python-thinc ftbfs with Python 3.12 (and cython 3.0.5))

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 13:40:54 -0100
with message-id 

and subject line python-thinc ftbfs with Python 3.12 (and cython 3.0.5)
has caused the Debian Bug report #1056038,
regarding python-thinc ftbfs with Python 3.12 (and cython 3.0.5)
to be marked as done.

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

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


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

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

python-thinc ftbfs with Python 3.12 (and cython 3.0.5):

[...]
Error compiling Cython file:

...
dims = table.shape[1]

cdef np.ndarray output
if reals2d_ft is float2d_t:
output = self.xp.zeros((rows, dims), dtype="float32")
cpu_gather_add(saxpy(cblas), output.data, 
[0, 0], [0, 0],

^


thinc/backends/numpy_ops.pyx:448:32: Cannot assign type 'saxpy_ptr' to 
'ptr'. Exception values are incompatible. Suggest adding 'noexcept' to 
type 'void (int, float, const float *, int, float *, int) except * nogil'.


Error compiling Cython file:

...
dims = table.shape[1]

cdef np.ndarray output
if reals2d_ft is float2d_t:
output = self.xp.zeros((rows, dims), dtype="float32")
cpu_gather_add(saxpy(cblas), output.data, 
[0, 0], [0, 0],

^


thinc/backends/numpy_ops.pyx:448:32: Cannot assign type 'saxpy_ptr' to 
'ptr'. Exception values are incompatible. Suggest adding 'noexcept' to 
type 'void (int, float, const float *, int, float *, int) except * nogil'.


Error compiling Cython file:

...
output = self.xp.zeros((rows, dims), dtype="float32")
cpu_gather_add(saxpy(cblas), output.data, 
[0, 0], [0, 0],

table.shape[0], dims, rows, indices.shape[1])
else:
output = self.xp.zeros((rows, dims), dtype="float64")
cpu_gather_add(daxpy(cblas), output.data, 
[0, 0], [0, 0],

^


thinc/backends/numpy_ops.pyx:452:32: Cannot assign type 'daxpy_ptr' to 
'ptr'. Exception values are incompatible. Suggest adding 'noexcept' to 
type 'void (int, double, const double *, int, double *, int) except * 
nogil'.


Error compiling Cython file:

...
output = self.xp.zeros((rows, dims), dtype="float32")
cpu_gather_add(saxpy(cblas), output.data, 
[0, 0], [0, 0],

table.shape[0], dims, rows, indices.shape[1])
else:
output = self.xp.zeros((rows, dims), dtype="float64")
cpu_gather_add(daxpy(cblas), output.data, 
[0, 0], [0, 0],

^


thinc/backends/numpy_ops.pyx:452:32: Cannot assign type 'daxpy_ptr' to 
'ptr'. Exception values are incompatible. Suggest adding 'noexcept' to 
type 'void (int, double, const double *, int, double *, int) except * 
nogil'.




complete build log at
https://launchpadlibrarian.net/697893737/buildlog_ubuntu-noble-amd64.python-thinc_8.1.7-1build1_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
python-thinc 8.1.7-1+b1 built successfully with cython3 0.29.36-3.1.
The failure with cython 3.0.x is #1056875.--- End Message ---

Processed: bug 1057717 is forwarded to https://gitlab.kitware.com/cmake/cmake/-/issues/25500

[Debian Bug Tracking System]

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

> forwarded 1057717 https://gitlab.kitware.com/cmake/cmake/-/issues/25500
Bug #1057717 [src:cmake] cmake ftbfs on ppc64el (and ppc64)
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/cmake/cmake/-/issues/25500'.
> thanks
Stopping processing here.

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

Bug#1055712: marked as done (python-feather-format ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 13:33:56 -0100
with message-id 

and subject line python-feather-format ftbfs with Python 3.12
has caused the Debian Bug report #1055712,
regarding python-feather-format 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.)


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

Package: src:python-feather-format
Version: 0.3.1+dfsg1-6
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-feather-format ftbfs with Python 3.12:

[...]
Compiling feather/ext.pyx because it changed.
[1/1] Cythonizing feather/ext.pyx
Traceback (most recent call last):
  File "/<>/setup.py", line 136, in 
extensions = cythonize(extensions)
 ^
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1154, in cythonize

cythonize_one(*args)
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1321, in cythonize_one

raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: feather/ext.pyx
E: pybuild pybuild:395: clean: plugin distutils failed with: exit 
code=1: python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
returned exit code 13

make: *** [debian/rules:10: clean] Error 25

complete build log at
https://launchpadlibrarian.net/696984575/buildlog_ubuntu-noble-amd64.python-feather-format_0.3.1+dfsg1-6build2_BUILDING.txt.gz
--- End Message ---
--- Begin Message ---
python-feather-format 0.3.1+dfsg1-6+b3 built successfully with cython3
0.29.36-3 after pandas had built.--- End Message ---

Processed: Bug#1058439 marked as pending in python-os-api-ref

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058439 [src:python-os-api-ref] python-os-api-ref: FTBFS: AttributeError: 
'TestMicroversions' object has no attribute 'assertRegexpMatches'
Added tag(s) pending.

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

Bug#1058439: marked as pending in python-os-api-ref

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058439 in python-os-api-ref 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/openstack-team/libs/python-os-api-ref/-/commit/6005e4d73fbf0436b961810927b3df45c56097a6


* Add python 3.12 patches (Closes: #1058439):
- py3.12-use-assertRegex-not-assertRegexpMatches.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058439

Processed: flake8 is completely broken

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1057968 [python3-flake8] python3-flake8: cannot import name 
'missing_whitespace_around_operator' from 'pycodestyle'
Severity set to 'serious' from 'normal'
> fixed -1 6.1.0-1
Bug #1057968 [python3-flake8] python3-flake8: cannot import name 
'missing_whitespace_around_operator' from 'pycodestyle'
Marked as fixed in versions python-flake8/6.1.0-1.

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

Bug#1058690: liblatex-tounicode-perl: trying to overwrite .../ltx2unitxt.1.gz, which is also in package texlive-bibtex-extra 2023.20231207-1

[Vincent Lefevre]

Package: liblatex-tounicode-perl
Version: 0.54-1
Severity: serious

As a consequence of the upgrade of texlive-bibtex-extra to
2023.20231207-3:

[...]
Selecting previously unselected package liblatex-tounicode-perl.
(Reading database ... 711147 files and directories currently installed.)
Preparing to unpack .../00-liblatex-tounicode-perl_0.54-1_all.deb ...
Unpacking liblatex-tounicode-perl (0.54-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-seikpl/00-liblatex-tounicode-perl_0.54-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man1/ltx2unitxt.1.gz', which is also in 
package texlive-bibtex-extra 2023.20231207-1
[...]

It seems that the fix in bug 1058462 is incorrect or incomplete.

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

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

Versions of packages liblatex-tounicode-perl depends on:
ii  perl  5.36.0-10

liblatex-tounicode-perl recommends no packages.

liblatex-tounicode-perl suggests no packages.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1058683: marked as done (FTBFS against htsjdk/4.0.2+dfsg-1 now in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 13:34:56 +
with message-id 
and subject line Bug#1058683: fixed in igv 2.16.2+dfsg-2
has caused the Debian Bug report #1058683,
regarding FTBFS against htsjdk/4.0.2+dfsg-1 now in unstable
to be marked as done.

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

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


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

Hello,

igv fails to build against new htsjdk/4.0.2+dfsg-1:

/<>/src/main/java/org/broad/igv/track/TribbleFeatureSource.java:352:
 error: reference to NamedFeature is ambiguous
if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
 ^
  both interface org.broad.igv.feature.NamedFeature in org.broad.igv.feature 
and interface htsjdk.tribble.NamedFeature in htsjdk.tribble match
/<>/src/main/java/org/broad/igv/track/TribbleFeatureSource.java:352:
 error: reference to NamedFeature is ambiguous
if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
 ^
  both interface org.broad.igv.feature.NamedFeature in org.broad.igv.feature 
and interface htsjdk.tribble.NamedFeature in htsjdk.tribble match

There is some ambiguity to be removed, which is solved by the enclosed patch.

Best,

-- 
Pierre
Description: solving an ambiguity in the tests due to a new class in
 htsjdk/4.0.2+dfsg
Author: Pierre Gruet 
Forwarded: no
Last-Update: 2023-12-14

--- a/src/main/java/org/broad/igv/track/TribbleFeatureSource.java
+++ b/src/main/java/org/broad/igv/track/TribbleFeatureSource.java
@@ -349,7 +349,7 @@
 featureMap.put(igvChr, featureList);
 }
 featureList.add(f);
-if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
+if (f instanceof org.broad.igv.feature.NamedFeature) 
FeatureDB.addFeature((org.broad.igv.feature.NamedFeature) f, genome);
 
 if (this.isVCF && f instanceof Variant) {
 Variant v = (Variant) f;
--- End Message ---
--- Begin Message ---
Source: igv
Source-Version: 2.16.2+dfsg-2
Done: Pierre Gruet 

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

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated igv 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, 14 Dec 2023 14:09:05 +0100
Source: igv
Architecture: source
Version: 2.16.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pierre Gruet 
Closes: 1058683
Changes:
 igv (2.16.2+dfsg-2) unstable; urgency=medium
 .
   * Solving ambiguity to build against htsjdk/4.0.2+dfsg (Closes: #1058683)
Checksums-Sha1:
 0d0fab13758b4434268de8c3cb96ec48627774b2 2544 igv_2.16.2+dfsg-2.dsc
 d2f30730793ac44c770ae5d91713dcd435b3fc28 31036 igv_2.16.2+dfsg-2.debian.tar.xz
 30307534606afa213d566ae468cfc7b0fcdee89d 17257 
igv_2.16.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 76bafe701ef897da0f87c5f5d64f5081d8468647896f23d93703927c17bd7d38 2544 
igv_2.16.2+dfsg-2.dsc
 3dc6143dd9c2925de4b3e11a0b99a7a92b8793e23b075ee0ae18bf2f786d99a4 31036 
igv_2.16.2+dfsg-2.debian.tar.xz
 1f10df17c35041b4d7cc54a3050027e025a60ad99a27bf7451880be3da5cb219 17257 
igv_2.16.2+dfsg-2_source.buildinfo
Files:
 170223ab614c88c611838600a44dd396 2544 science optional igv_2.16.2+dfsg-2.dsc
 663c08465b93348ca2c1dfe047e9f63f 31036 science optional 
igv_2.16.2+dfsg-2.debian.tar.xz
 74d5f5326fc833e6fffa58a46adfe6b7 17257 science optional 
igv_2.16.2+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmV6/o8ACgkQYAMWptwn
dHbuxA//duLfPJRkKoobUh59cUxSeIlXEuQrfkAGFfITKZ8iNK69+4K3SE9iyhzB
HvdZfxVktCcGXeOewt4G2DA6zibK/5O0DnSxQqKIntkiRBcbp7XkkHnE76Nc23vo

Bug#1058683: FTBFS against htsjdk/4.0.2+dfsg-1 now in unstable

[Pierre Gruet]

Source: igv
Version: 2.16.2+dfsg-1
Severity: serious
Tags: patch

Hello,

igv fails to build against new htsjdk/4.0.2+dfsg-1:

/<>/src/main/java/org/broad/igv/track/TribbleFeatureSource.java:352:
 error: reference to NamedFeature is ambiguous
if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
 ^
  both interface org.broad.igv.feature.NamedFeature in org.broad.igv.feature 
and interface htsjdk.tribble.NamedFeature in htsjdk.tribble match
/<>/src/main/java/org/broad/igv/track/TribbleFeatureSource.java:352:
 error: reference to NamedFeature is ambiguous
if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
 ^
  both interface org.broad.igv.feature.NamedFeature in org.broad.igv.feature 
and interface htsjdk.tribble.NamedFeature in htsjdk.tribble match

There is some ambiguity to be removed, which is solved by the enclosed patch.

Best,

-- 
Pierre
Description: solving an ambiguity in the tests due to a new class in
 htsjdk/4.0.2+dfsg
Author: Pierre Gruet 
Forwarded: no
Last-Update: 2023-12-14

--- a/src/main/java/org/broad/igv/track/TribbleFeatureSource.java
+++ b/src/main/java/org/broad/igv/track/TribbleFeatureSource.java
@@ -349,7 +349,7 @@
 featureMap.put(igvChr, featureList);
 }
 featureList.add(f);
-if (f instanceof NamedFeature) 
FeatureDB.addFeature((NamedFeature) f, genome);
+if (f instanceof org.broad.igv.feature.NamedFeature) 
FeatureDB.addFeature((org.broad.igv.feature.NamedFeature) f, genome);
 
 if (this.isVCF && f instanceof Variant) {
 Variant v = (Variant) f;

Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Alex Sisson]

 New release
https://master.dl.sourceforge.net/project/shed/shed/shed%201.16/shed-1.16.tar.gz
I've spun up a unstable vm and tested myself.
Also I've manually applied the two debian patches related to CFLAGS and man 
page.
ThanksAlex




On Tuesday, 5 December 2023 at 22:39:57 GMT, Santiago Vila 
 wrote:  
 
 Package: src:shed
Version: 1.15-5
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
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:429: AM_INIT_AUTOMAKE is expanded from...
configure.in:2: the top level
configure.in:48: warning: AC_OUTPUT should be used without arguments.
configure.in:48: You should run autoupdate.
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.in:2: 
https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:3: installing './compile'
automake: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
    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 --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 for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
large file support: yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for ncurses.h... yes
checking for getopt.h... yes
checking for initscr in -lncurses... yes
checking for pow in -lm... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
    dh_auto_build
    make -j2
make[1]: Entering directory '/<>'
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"shed\" -DVERSION=\"1.15\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
-DHAVE_LIBNCURSES=1 -DHAVE_LIBM=1 -I.  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSHED_LFS=1 -D_FILE_OFFSET_BITS=64 -DSHED_CYGFIX=0 -DSHED_NOFOLLOW=0 -c -o 
util.o util.c
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"shed\" -DVERSION=\"1.15\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
-DHAVE_LIBNCURSES=1 -DHAVE_LIBM=1 -I.  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSHED_LFS=1 -D_FILE_OFFSET_BITS=64 -DSHED_CYGFIX=0 -DSHED_NOFOLLOW=0 -c -o 
shed.o shed.c
In file included from shed.c:35:
shed.c: In function ‘mainloop’:
shed.c:410:29: error: invalid use of incomplete 

Bug#1058581: marked as done (rust-rusqlite: autopkgtest regression on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 12:04:22 +
with message-id 
and subject line Bug#1058581: fixed in rust-rusqlite 0.29.0-3
has caused the Debian Bug report #1058581,
regarding rust-rusqlite: autopkgtest regression on architectures where char is 
unsigned
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.)


-- 
1058581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rusqlite
Version: 0.29.0-2
Severity: serious

https://tracker.debian.org/pkg/rust-rusqlite

Issues preventing migration:
∙ ∙ autopkgtest for rust-rusqlite/0.29.0-2: amd64: Pass, arm64: Regression or 
new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: 
Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Reference test in 
progress, but real test failed already, s390x: Regression or new test ♻ 
(reference ♻)

...
146s error[E0308]: mismatched types
146s --> src/lib.rs:1782:44
146s  |
146s 1782 | let r = unsafe { ffi::sqlite3_open(":memory:\0".as_ptr() as 
*const i8,  handle) };
146s  |  - 
^^ expected `*const u8`, found `*const i8`
146s  |  |
146s  |  arguments to this function are incorrect
146s  |
146s  = note: expected raw pointer `*const u8`
146s found raw pointer `*const i8`
146s note: function defined here
146s --> 
/tmp/tmp.3mduH0HVbW/target/aarch64-unknown-linux-gnu/debug/build/libsqlite3-sys-aef3de5783c0ae0e/out/bindgen.rs:3:39519
146s  |
146s 3| ...* mut :: std :: os :: raw :: c_void) ; } extern "C" { pub fn 
sqlite3_open (filename : * const :: std :: os :: raw :: c_char , ppDb : *...
146s  | 

146s 
146s For more information about this error, try `rustc --explain E0308`.
146s error: could not compile `rusqlite` due to previous error
--- End Message ---
--- Begin Message ---
Source: rust-rusqlite
Source-Version: 0.29.0-3
Done: Peter Michael Green 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Dec 2023 11:53:33 +
Source: rust-rusqlite
Architecture: source
Version: 0.29.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1058581
Changes:
 rust-rusqlite (0.29.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Package rusqlite 0.29.0 from crates.io using debcargo 2.6.1
   * Fix build of test_from_handle on architectures with unsigned char. 
(Closes: #1058581)
Checksums-Sha1:
 fc55018f66d0e9c16e316dc31cc85216f322168d 2772 rust-rusqlite_0.29.0-3.dsc
 194a565dd215ee99637de432fa67e3299dfb526c 5616 
rust-rusqlite_0.29.0-3.debian.tar.xz
 dc8e86f8fc4fae9609f8281cc2cb66e31be9100f 8318 
rust-rusqlite_0.29.0-3_source.buildinfo
Checksums-Sha256:
 0a4622fdde578f38b4ca87267c79cbc5fce339bcb70ff1b2016ebb2156d71c58 2772 
rust-rusqlite_0.29.0-3.dsc
 6337f09a7fea084a41bc5682327f6b5a71ec2746cadd6a5b6d92fc7de82bbc4e 5616 
rust-rusqlite_0.29.0-3.debian.tar.xz
 409cb719e72fff7808cfcfe678197e15f981a0453d150b71eae263ca1cb06cbe 8318 
rust-rusqlite_0.29.0-3_source.buildinfo
Files:
 bc150306910dc783c290528c0b3c6735 2772 rust optional rust-rusqlite_0.29.0-3.dsc
 d460f5b9c262ac52d004de1f09846b48 5616 rust optional 
rust-rusqlite_0.29.0-3.debian.tar.xz
 e64b50479db759fab1d14647da26 8318 rust optional 
rust-rusqlite_0.29.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmV67PIUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtzFg/+OGsulMS09k11ZaamEdMHJSp8lCR5
0lix/uYFe4yRhDd2ZGDrfW3UVr4wZ4RHVv9l/SoBucanyyamt5ADfk4nWw0iHy1Y
vbXchT959YEtghvyi2lGcg9+rvFuv21eUQzxxRvopZUGs1bOcqE66UYPMqZkQjp/

Bug#1057967: linux-image-6.1.0-15-amd64: Fixed in 6.1.67-1

[reporter]

I can confirm that this issue is fixed in my Macbook Pro after upgrading to
6.1.67-1 from bookworm-proposed-updates.

---

$ apt-cache policy linux-image-amd64
linux-image-amd64:
  Installed: 6.1.67-1
  Candidate: 6.1.67-1
  Version table:
 *** 6.1.67-1 500
500 http://httpredir.debian.org/debian
bookworm-proposed-updates/main amd64 Packages
100 /var/lib/dpkg/status
 6.1.66-1 500
500 http://httpredir.debian.org/debian bookworm/main amd64 Packages
 6.1.52-1 500
500 http://security.debian.org/debian-security
bookworm-security/main amd64 Packages

---

# lspci -vvv

02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4331
802.11a/b/g/n (rev 02)
...
Kernel driver in use: wl
Kernel modules: bcma, wl


---

# modinfo wl
filename:   /lib/modules/6.1.0-16-amd64/updates/dkms/wl.ko
license:MIXED/Proprietary
alias:  pci:v*d*sv*sd*bc02sc80i*
depends:cfg80211
retpoline:  Y
name:   wl
vermagic:   6.1.0-16-amd64 SMP preempt mod_unload modversions
sig_id: PKCS#7
...

#

Thanks.

Processed: forcibly merging 1054737 1054749

[Debian Bug Tracking System]

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

> forcemerge 1054737 1054749
Bug #1054737 [src:ruby-pry-byebug] ruby-pry-byebug: FTBFS: ERROR: Test 
"ruby3.1" failed: 
:86:in 
`require': cannot load such file -- pry-byebug (LoadError)
Bug #1054749 [src:ruby-pry-byebug] ruby-android-key-attestation: FTBFS: ERROR: 
Test "ruby3.1" failed: Failure/Error: require "pry-byebug"
Severity set to 'serious' from 'normal'
1056995 was blocked by: 1054737
1056995 was blocking: 1057333
Added blocking bug(s) of 1056995: 1054749
Removed indication that 1054749 affects ruby-android-key-attestation
Marked as fixed in versions ruby-pry-byebug/3.10.1-1.
Marked as found in versions ruby-pry-byebug/3.9.0-1.
Merged 1054737 1054749
> thanks
Stopping processing here.

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

Bug#1058161: marked as done (metaconfig: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'?)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 11:50:58 +
with message-id 
and subject line Bug#1058161: fixed in metaconfig 0.1.4a1-8
has caused the Debian Bug report #1058161,
regarding metaconfig: FTBFS: AttributeError: 'ConfigParser' object has no 
attribute 'readfp'. Did you mean: 'read'?
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.)


-- 
1058161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metaconfig
Version: 0.1.4a1-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.12 setup.py build
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/metaconfig
> copying metaconfig/__init__.py -> build/lib/metaconfig
> copying metaconfig/mconf.py -> build/lib/metaconfig
> running egg_info
> creating metaconfig.egg-info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> python3.11 setup.py build
> running build
> running build_py
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> dh_auto_build
>   pybuild --build -i python{version} -p "3.12 3.11"
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/metaconfig
> copying metaconfig/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/metaconfig
> copying metaconfig/mconf.py -> 
> /<>/.pybuild/cpython3_3.12/build/metaconfig
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/metaconfig
> copying metaconfig/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/metaconfig
> copying metaconfig/mconf.py -> 
> /<>/.pybuild/cpython3_3.11/build/metaconfig
> running egg_info
> writing metaconfig.egg-info/PKG-INFO
> writing dependency_links to metaconfig.egg-info/dependency_links.txt
> writing top-level names to metaconfig.egg-info/top_level.txt
> reading manifest file 'metaconfig.egg-info/SOURCES.txt'
> writing manifest file 'metaconfig.egg-info/SOURCES.txt'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test --test-nose2 -i python{version} -p "3.12 3.11"
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m nose2 -v 
> test_1 (test_metaconfig.Test1.test_1) ... ok
> test_2 (test_metaconfig.Test1.test_2) ... ok
> test_3 (test_metaconfig.Test1.test_3) ... ok
> test_4 (test_metaconfig.Test1.test_4) ... ok
> test_1 (test_metaconfig.Test2.test_1) ... ERROR
> test_2 (test_metaconfig.Test2.test_2) ... ok
> test_1 (test_metaconfig.Test3.test_1) ... ERROR
> 
> ==
> ERROR: test_1 (test_metaconfig.Test2.test_1)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.12/build/test/test_metaconfig.py", line 
> 112, in test_1
> self.mf.add_config_fh('p1', open(self.config_file))
>   File "/<>/.pybuild/cpython3_3.12/build/metaconfig/mconf.py", 
> line 71, in add_config_fh
> conf.readfp(fileobj)
> ^^^
> AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you 
> mean: 'read'?
> 
> ==
> ERROR: test_1 (test_metaconfig.Test3.test_1)
> 

Processed (with 1 error): Re: Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:octave-netcdf
Bug #1058281 [src:octave-ncarray] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Bug reassigned from package 'src:octave-ncarray' to 'src:octave-netcdf'.
No longer marked as found in versions octave-ncarray/1.0.5-3.
Ignoring request to alter fixed versions of bug #1058281 to the same values 
previously set
> forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?64999'.
> merge -1 1057590
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Unable to merge bugs because:
blockedby of #1057589 is '1058621' not ''
blockedby of #1057590 is '1058621' not ''
Failed to merge 1058281: Did not alter merged bugs.


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

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Rafael Laboissière]

Control: reassign -1 src:octave-netcdf
Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?64999
Control: merge -1 1057590

* Lucas Nussbaum  [2023-12-12 09:39]:


Source: octave-ncarray
Version: 1.0.5-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

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


Thanks for this bug report, but the issue has been already reported. I 
am hereby reassigning and merging this bug report.


Best,

Rafael Laboissière

Bug#1058345: marked as done (fdb: FTBFS: SingleGribMungePartFileHandle.h:69:10: error: ‘void fdb5::SingleGribMungePartFileHandle::cost(std::map, eckit::Length>&, bool)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2023 11:34:25 +
with message-id 
and subject line Bug#1058345: fixed in fdb 5.11.94-1
has caused the Debian Bug report #1058345,
regarding fdb: FTBFS: SingleGribMungePartFileHandle.h:69:10: error: ‘void 
fdb5::SingleGribMungePartFileHandle::cost(std::map,
 eckit::Length>&, bool) const’ marked ‘override’, but does not override
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.)


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

Hi,

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


Relevant part (hopefully):
> cd /<>/debian/build/src/fdb5 && /usr/bin/c++ -Dfdb5_EXPORTS 
> -I/<>/src -I/<>/debian/build/src 
> -I/usr/include/x86_64-linux-gnu/metkit -I/usr/include/x86_64-linux-gnu/eckit 
> -I/usr/include/x86_64-linux-gnu/eckit/option -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall -Wextra -Wno-unused-parameter 
> -Wno-unused-variable -Wno-sign-compare -O3 -DNDEBUG -std=gnu++17 -fPIC -MD 
> -MT src/fdb5/CMakeFiles/fdb5.dir/io/SingleGribMungePartFileHandle.cc.o -MF 
> CMakeFiles/fdb5.dir/io/SingleGribMungePartFileHandle.cc.o.d -o 
> CMakeFiles/fdb5.dir/io/SingleGribMungePartFileHandle.cc.o -c 
> /<>/src/fdb5/io/SingleGribMungePartFileHandle.cc
> In file included from 
> /<>/src/fdb5/io/SingleGribMungePartFileHandle.cc:12:
> /<>/src/fdb5/io/SingleGribMungePartFileHandle.h:69:10: error: 
> ‘void 
> fdb5::SingleGribMungePartFileHandle::cost(std::map,
>  eckit::Length>&, bool) const’ marked ‘override’, but does not override
>69 | void cost(std::map&, bool) const 
> override { NOTIMP; }
>   |  ^~~~
> [ 52%] Building CXX object src/fdb5/CMakeFiles/fdb5.dir/toc/AdoptVisitor.cc.o
> cd /<>/debian/build/src/fdb5 && /usr/bin/c++ -Dfdb5_EXPORTS 
> -I/<>/src -I/<>/debian/build/src 
> -I/usr/include/x86_64-linux-gnu/metkit -I/usr/include/x86_64-linux-gnu/eckit 
> -I/usr/include/x86_64-linux-gnu/eckit/option -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall -Wextra -Wno-unused-parameter 
> -Wno-unused-variable -Wno-sign-compare -O3 -DNDEBUG -std=gnu++17 -fPIC -MD 
> -MT src/fdb5/CMakeFiles/fdb5.dir/toc/AdoptVisitor.cc.o -MF 
> CMakeFiles/fdb5.dir/toc/AdoptVisitor.cc.o.d -o 
> CMakeFiles/fdb5.dir/toc/AdoptVisitor.cc.o -c 
> /<>/src/fdb5/toc/AdoptVisitor.cc
> make[3]: *** [src/fdb5/CMakeFiles/fdb5.dir/build.make:1423: 
> src/fdb5/CMakeFiles/fdb5.dir/io/SingleGribMungePartFileHandle.cc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/fdb_5.11.25-1_unstable.log

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

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

If you reassign this bug to another package, please 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: fdb
Source-Version: 5.11.94-1
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated fdb 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: 

Processed (with 1 error): forcibly merging 1054737 1054749

[Debian Bug Tracking System]

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

> forcemerge 1054737 1054749
Bug #1054737 [src:ruby-pry-byebug] ruby-pry-byebug: FTBFS: ERROR: Test 
"ruby3.1" failed: 
:86:in 
`require': cannot load such file -- pry-byebug (LoadError)
Unable to merge bugs because:
package of #1054749 is 'ruby-pry-byebug' not 'src:ruby-pry-byebug'
Failed to forcibly merge 1054737: Did not alter merged bugs.

> thanks
Stopping processing here.

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