Bug#1073417: marked as done (trapperkeeper-status-clojure: FTBFS: make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jun 2024 05:19:25 +
with message-id 
and subject line Bug#1073417: fixed in trapperkeeper-status-clojure 1.1.1-5
has caused the Debian Bug report #1073417,
regarding trapperkeeper-status-clojure: FTBFS: make[1]: *** [debian/rules:25: 
override_dh_auto_test] Error 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.)


-- 
1073417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trapperkeeper-status-clojure
Version: 1.1.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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 '/<>'
> lein test
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/usr/share/java/logback-classic.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/usr/share/java/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type 
> [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 
> lein test puppetlabs.trapperkeeper.services.status.check-test
> 
> lein test puppetlabs.trapperkeeper.services.status.status-core-test
> 
> lein test puppetlabs.trapperkeeper.services.status.status-proxy-service-test
> 
> lein test :only 
> puppetlabs.trapperkeeper.services.status.status-proxy-service-test/proxy-only-proxies-what-it-should-test
> 
> ERROR in (proxy-only-proxies-what-it-should-test) (Alert.java:131)
> Uncaught exception, not in assertion.
> expected: nil
>   actual: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed
>  at sun.security.ssl.Alert.createSSLException (Alert.java:131)
> sun.security.ssl.TransportContext.fatal (TransportContext.java:378)
> sun.security.ssl.TransportContext.fatal (TransportContext.java:321)
> sun.security.ssl.TransportContext.fatal (TransportContext.java:316)
> 
> sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts 
> (CertificateMessage.java:1351)
> 
> sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate
>  (CertificateMessage.java:1226)
> sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume 
> (CertificateMessage.java:1169)
> sun.security.ssl.SSLHandshake.consume (SSLHandshake.java:396)
> sun.security.ssl.HandshakeContext.dispatch (HandshakeContext.java:480)
> sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run 
> (SSLEngineImpl.java:1277)
> sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run 
> (SSLEngineImpl.java:1264)
> java.security.AccessController.doPrivileged (AccessController.java:712)
> sun.security.ssl.SSLEngineImpl$DelegatedTask.run (SSLEngineImpl.java:1209)
> org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask 
> (SSLIOSession.java:289)
> org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake 
> (SSLIOSession.java:357)
> org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady 
> (SSLIOSession.java:545)
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady 
> (AbstractIODispatch.java:120)
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable 
> (BaseIOReactor.java:162)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent 
> (AbstractIOReactor.java:337)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents 
> (AbstractIOReactor.java:315)
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute 
> (AbstractIOReactor.java:276)
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute 
> (BaseIOReactor.java:104)
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run 
> (AbstractMultiworkerIOReactor.java:591)
> java.lang.Thread.run (Thread.java:840)
> Caused by: sun.security.validator.ValidatorException: PKIX path validation 
> failed: java.security.cert.CertPathValidatorException: validity check failed
>  at sun.security.validator.PKIXValidator.doValidate (PKIXValidator.java:369)
> sun.security.validator.PKIXValidator.engineValidate 
> (PKIXValidator.java:275)
> sun.security.validator.Validator.validate (Validator.java:264)
> sun.security.ssl.X509TrustManagerImpl.checkTrusted 
> (X509TrustManagerImpl.java:285)
> 

Bug#1073097: marked as done (lazymap-clojure: replace to-be-removed markdown build-dependency)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jun 2024 04:08:36 +
with message-id 
and subject line Bug#1073097: fixed in lazymap-clojure 3.1.1-3
has caused the Debian Bug report #1073097,
regarding lazymap-clojure: replace to-be-removed markdown build-dependency
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.)


-- 
1073097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lazymap-clojure
Version: 3.1.1-2
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.
--- End Message ---
--- Begin Message ---
Source: lazymap-clojure
Source-Version: 3.1.1-3
Done: Louis-Philippe Véronneau 

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated 
lazymap-clojure 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: Sat, 29 Jun 2024 23:41:14 -0400
Source: lazymap-clojure
Architecture: source
Version: 3.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers 
Changed-By: Louis-Philippe Véronneau 
Closes: 1073097
Changes:
 lazymap-clojure (3.1.1-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Louis-Philippe Véronneau ]
   * d/control: New email for the Clojure Team.
   * remove dependency on deprecated markdown package. (Closes: 1073097)
Checksums-Sha1:
 70cf8a48caa6f157751cfb7740a4136997d1ef9e 1494 lazymap-clojure_3.1.1-3.dsc
 292a20506418975b89ed561f15b173eef5406c74 2980 
lazymap-clojure_3.1.1-3.debian.tar.xz
 3fb3b0ef4c46041671f6e740cf5fa02d5d028a78 11979 
lazymap-clojure_3.1.1-3_amd64.buildinfo
Checksums-Sha256:
 337fa209c8912dd3405eef5c6cb49dbab20cad874ec95968ef8bbaeab8f0855f 1494 
lazymap-clojure_3.1.1-3.dsc
 0ef9147ce33a842aaeff370aacb420edec7831c4ab4cb06b1ac12b79d1ec3878 2980 
lazymap-clojure_3.1.1-3.debian.tar.xz
 dae17472c51ee88a8a09121761412f5e1c124145ee8f3f1ade204dc239d091a2 11979 
lazymap-clojure_3.1.1-3_amd64.buildinfo
Files:
 d741a2ec55b4e02b06cd2eeba786f9ca 1494 java optional lazymap-clojure_3.1.1-3.dsc
 089e947f57b67371b7e52993a63ddd90 2980 java optional 
lazymap-clojure_3.1.1-3.debian.tar.xz
 be5420d8d5cb23d274775a18b2dd6fa9 11979 java optional 
lazymap-clojure_3.1.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCZoDUgQAKCRD0JXpQshz6
haccAP93tttfNhJQ55RmPKU+66ou/V/3ISF2U6D9BcrTpRx6qAD/ZAqwlgI4POXY
PV3inb2QXqD0ldfPrxvCGq9z9IXzRgo=
=yycc
-END PGP SIGNATURE-



pgp4qIDE7HvRU.pgp
Description: PGP signature
--- End Message ---

Processed: Re: cura: Cura fails to start

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1074239 [cura] cura: Cura fails to start
Severity set to 'grave' from 'normal'

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

Bug#1071268: marked as done (nat-rtsp-dkms: fails to build on kernel 6.8.9)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jun 2024 00:34:27 +
with message-id 
and subject line Bug#1071268: fixed in nat-rtsp 0.7+5.3-0.3
has caused the Debian Bug report #1071268,
regarding nat-rtsp-dkms: fails to build on kernel 6.8.9
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.)


-- 
1071268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nat-rtsp-dkms
Version: 0.7+5.3-0.2
Severity: normal

Dear Maintainer,

the kernel modules in nat-rtsp-dkms fail to build in the newly released 6.8.9 
kernel. If feasible/useful to fix it, please do so, otherwise modify the 
package so that it does not even try compiling for them.

Thanks in advance, best regards
Giacomo Mulas


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

Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 nat-rtsp-dkms depends on:
ii  dkms  3.0.13-1

nat-rtsp-dkms recommends no packages.

nat-rtsp-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nat-rtsp
Source-Version: 0.7+5.3-0.3
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nat-rtsp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Jun 2024 02:11:00 +0200
Source: nat-rtsp
Architecture: source
Version: 0.7+5.3-0.3
Distribution: unstable
Urgency: medium
Maintainer: Julien Muchembled 
Changed-By: Andreas Beckmann 
Closes: 1071268
Changes:
 nat-rtsp (0.7+5.3-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Adrien CLERC ]
   * Fix module build for Linux 6.8+.  (Closes: #1071268)
Checksums-Sha1:
 4dfcd7e0e818531746ec10e58e3afb464fcf9316 1820 nat-rtsp_0.7+5.3-0.3.dsc
 a8bd24123458b304fb023117d74c1688a62a1bb7 3744 
nat-rtsp_0.7+5.3-0.3.debian.tar.xz
 a98e0618ed4e2a09f6ac7efbf06cb0a29bbe021e 5476 
nat-rtsp_0.7+5.3-0.3_source.buildinfo
Checksums-Sha256:
 5ea67c0da74a179ae584e6fc5a4ad843e4e2b3a9e479b3ad64a45fe3ec756d2b 1820 
nat-rtsp_0.7+5.3-0.3.dsc
 c1e44ffc58748c42ad0920ef925932d052579d3264cf51c2bd860d695c70c484 3744 
nat-rtsp_0.7+5.3-0.3.debian.tar.xz
 da35dd95d744fb134f0d08018cc0efc6bb5ec287ddbb7ac03924a4eb76fdaaa1 5476 
nat-rtsp_0.7+5.3-0.3_source.buildinfo
Files:
 f2352de4eaf904941671bcf503f6e510 1820 kernel optional nat-rtsp_0.7+5.3-0.3.dsc
 a1b7eb774346ad92daf231b03a8daff0 3744 kernel optional 
nat-rtsp_0.7+5.3-0.3.debian.tar.xz
 5241185e2a58085bc2456b57549e2e99 5476 kernel optional 
nat-rtsp_0.7+5.3-0.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmaAousQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCCdkD/9Bfxr/M7mJxgyFl0lNDrigYLUq3icWlAWp
GBBttJlJJebtlAUBLcTOeNMfa+M5WybD4J5NNro+F/lS8q6qF6vA6aWDADHApnsj
gRwZWKbj5ST7kWylyEyrJhBiwq4I/qjCoVENyqPTN2LYbIicFLaJuV/cdMu5y1KC
XiohpEOZ6ZTSsWWECF55b1HFIC8EF4hFpgrAp9RErhTlGxuHIYqheIDRlHZXgL9K
T/WypFiVvKxNcF+YVIZk2O8Ts7j46BUphoYqnPwJ4Z1kjBz5uRQT5HbQ77ph68Y1
E7m+UIh+LGoQsSnqRrioGey28FPR0EGYS5GJonsYO6LEO5JECbsp42KaMElASpbV
BdmhWKUEYclbsMAB/AOKMDEFTRziRc0DSrMCsyJewPCnjaVK6O8tRXpdv8c06mWe
gnMIo7UDqL4vF29h5eMnp21TDM3J5JeHPKAIkqgnY53/FrV8Bz8ujgFcXnffCsUp
1GDcAKFNuUN89dBPvv0dc9tErLVTRgn5/0IKvcoNzR01SFMDSsyml6+QdJ5/jSFA
pgkBDLsA8liYVG43XUfg3Qw20OAsaY131EHDDVyKNn+K7XzDH/0jA/Xu5GSfbygu
umo19wTBQa9jWiG15kWahayWErhPm2B6ayNs4e/SQgAKC2EyItTOl0MCcEfSEM46
IDdSU5uCQQ==
=ExBN
-END PGP SIGNATURE-



pgp2LwhfahWIp.pgp
Description: PGP signature
--- End Message ---

Bug#1074227: marked as done (goldencheetah: Unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 23:49:56 +
with message-id 
and subject line Bug#1074227: fixed in goldencheetah 1:3.5-6
has caused the Debian Bug report #1074227,
regarding goldencheetah: Unsatisfiable build-dependencies
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.)


-- 
1074227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: goldencheetah
Version: 1:3.5-5
Severity: serious
X-Debbugs-Cc: delta...@debian.org

Dear Maintainer,

your package has unsatisfiable build-dependencies, specifically
libqt5widgets5 and libqt5concurrent5.
These packages have been superseded by libqt5widgets5t64 and
libqt5concurrent5t64 respectively.

Build-depending on them is neither necessary nor recommended as the
corresponding packages are pulled automatically by qtbase5-dev.


--
Regards

Patrick Franz
--- End Message ---
--- Begin Message ---
Source: goldencheetah
Source-Version: 1:3.5-6
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated goldencheetah package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Jun 2024 01:24:16 +0200
Source: goldencheetah
Architecture: source
Version: 1:3.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1044738 1074227
Changes:
 goldencheetah (1:3.5-6) unstable; urgency=medium
 .
   * QA upload.
   * Drop superfluous B-D.  (Closes: #1074227)
   * Fix building twice in a row.  (Closes: #1044738)
   * Use the default salsa CI config.
   * Declare Rules-Requires-Root: no.
   * Enable all hardening flags.
   * Make documentation build reproducible.
   * Update Lintian overrides.
Checksums-Sha1:
 9f3e9e17a0343f43593355205bf01003833ce461 2391 goldencheetah_3.5-6.dsc
 0cada773ffbcb913ed60a5f3c5a1b66f152c741b 79760 
goldencheetah_3.5-6.debian.tar.xz
 7d70243870e221a0b3e43b6627452733a934e03a 15703 
goldencheetah_3.5-6_source.buildinfo
Checksums-Sha256:
 bf6a4f96dfaf32843a45c6064a950a3dcb60cc1d8a27ecfda7cc5201e7b2e35b 2391 
goldencheetah_3.5-6.dsc
 bb85584bbfe64e4472f6160c649f26e43e2561e96bfb630fd874f7bb21b38849 79760 
goldencheetah_3.5-6.debian.tar.xz
 fcc7b5f4e61020149fe2a89fceae1215fd9b0500e611db9c8d24d8c753badc8d 15703 
goldencheetah_3.5-6_source.buildinfo
Files:
 e6d51bf048ee5b3ebdfd33df2e0333dc 2391 misc optional goldencheetah_3.5-6.dsc
 9757f5b762d8c16741e629ab20a19c60 79760 misc optional 
goldencheetah_3.5-6.debian.tar.xz
 0dc1714b1f65951220696a366d9a23cb 15703 misc optional 
goldencheetah_3.5-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmaAmNsQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCA9dEACYYVoeWnhiXLtX5Al9/wfJ/nKsTNz/JwNy
aBG3kJ0maEb1mJ2XeMS/LfYlTIgkGrddQQifpvyFusZZ45A5DihE6uavQpxr8t4r
2v7iwt+gKzFFq6TQ2A9ZGJzHSMJAqxnYY5FvGUp15p9o45P2oJoKz28lnHP2JSkI
7wHjQ6cNa3ROtrp6bZWW6aFGBj/Y7ORsYpWUpKCjCgt3YcomMVXe7/Jib41lcmQ5
2a8Z5GcIGKggvbYa5ONxix1TsZV/NWTLtpFd/LCtCkmNZwHoI61UlUySG1f/GUZW
9r3iC3R28wpMKd7P/mKY1oWXRNY9eIIl6lTEqp1lRfvwYQwdAWAKcjqO4oxV7on1
LrY7oAcs3fccjeTV9eeKGp0V7q+wyWGsC7wuG3Pt29HMP9GInUbJpdq0TljGnJ3I
5ryfnIRvssU7T3oVBbJTXV36o4AKIPz6q/l6ALiyemKdKFQnGtOssSHjw6nkCl7J
uT7ySLk7hlCIWou7lig1syy3++yj6cXkblAmyZ7oGtNn+uRhXRqh6uVaY7YeGsfQ
LqzWLY+qMc0R0xd/2MqXIbjKIqY+6NEACl3lieGfyym9BXzcY5V1jPsBoIc7anPl
Y6jQbNjqVMB3g0DjyhP5ChM0g196qZOx5Xaz/+RugqmNitrWlcUiJqLMzhDzuTGN
I9L4A6ldEg==
=gvPI
-END PGP SIGNATURE-



pgp09qYmFHlII.pgp
Description: PGP signature
--- End Message ---

Bug#1074502: listparser: autopkgtest failure with Python 3.12

[Yogeswaran Umasankar]

Source: listparser
Version: 0.18-3
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: y...@debian.org
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Dear Maintainer,

listparser autopkgtests fail with Python 3.12  [0].

[0] https://ci.debian.net/packages/l/listparser/testing/arm64/

autopkgtest [23:35:58]: test command1: [---
/tmp/autopkgtest.jZHSp5/tree/lptest.py:174: SyntaxWarning: invalid escape 
sequence '\:'
  testBogusFilename = _bad_test('totally made up and bogus /\:')
/tmp/autopkgtest.jZHSp5/tree/lptest.py:401: DeprecationWarning: setDaemon() is 
deprecated, set the daemon attribute instead
  server.setDaemon(True)
.EEE..EETraceback
 (most recent call last):
  File "/usr/lib/python3.12/urllib/request.py", line 1344, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
  File "/usr/lib/python3.12/http/client.py", line 1336, in request
self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.12/http/client.py", line 1382, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.12/http/client.py", line 1331, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.12/http/client.py", line 1091, in _send_output
self.send(msg)
  File "/usr/lib/python3.12/http/client.py", line 1035, in send
self.connect()
  File "/usr/lib/python3.12/http/client.py", line 1001, in connect
self.sock = self._create_connection(

  File "/usr/lib/python3.12/socket.py", line 829, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
   ^^^
  File "/usr/lib/python3.12/socket.py", line 964, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
   ^^^
socket.gaierror: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/autopkgtest.OkgtBD/tree/lptest.py", line 413, in 
  File "/usr/lib/python3.12/unittest/runner.py", line 240, in run
test(result)
  File "/usr/lib/python3.12/unittest/suite.py", line 84, in __call__
return self.run(*args, **kwds)
   ^^^
  File "/usr/lib/python3.12/unittest/suite.py", line 122, in run
test(result)
  File "/usr/lib/python3.12/unittest/suite.py", line 84, in __call__
return self.run(*args, **kwds)
   ^^^
  File "/usr/lib/python3.12/unittest/suite.py", line 122, in run
test(result)
  File "/usr/lib/python3.12/unittest/case.py", line 690, in __call__
return self.run(*args, **kwds)
   ^^^
  File "/usr/lib/python3.12/unittest/case.py", line 634, in run
self._callTestMethod(testMethod)
  File "/usr/lib/python3.12/unittest/case.py", line 589, in _callTestMethod
if method() is not None:
   
  File "/tmp/autopkgtest.OkgtBD/tree/lptest.py", line 167, in fn
  File "/tmp/autopkgtest.OkgtBD/tree/listparser.py", line 521, in _mkfile
ret = opener.open(request)
  
  File "/usr/lib/python3.12/urllib/request.py", line 515, in open
response = self._open(req, data)
   ^
  File "/usr/lib/python3.12/urllib/request.py", line 532, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
 ^^^
  File "/usr/lib/python3.12/urllib/request.py", line 492, in _call_chain
result = func(*args)
 ^^^
  File "/usr/lib/python3.12/urllib/request.py", line 1373, in http_open
return self.do_open(http.client.HTTPConnection, req)
   ^
  File "/usr/lib/python3.12/urllib/request.py", line 1347, in do_open
raise URLError(err)
  ^
  File "/usr/lib/python3.12/urllib/error.py", line 25, in __init__
def __init__(self, reason, filename=None):

KeyboardInterrupt
ç√EE
==
ERROR: testImage (__main__.TestCases.testImage)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.jZHSp5/tree/lptest.py", line 153, in testImage
self.assert_(result.bozo == 1)

AttributeError: 'TestCases' object has no attribute 'assert_'. Did you mean: 
'assertIn'?

==
ERROR: testUserAgentCustomArg (__main__.TestCases.testUserAgentCustomArg)

Bug#1074500: pompem: autopkgtest failure with Python 3.12

[Yogeswaran Umasankar]

Package: pompem
Version: 0.2.0-6
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: y...@debian.org
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Dear Maintainer,

pompem autopkgtests fail with Python 3.12  [0].

autopkgtest [23:24:27]: test command1: [---
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
  BASIC_INFO_MESSAGE = """

Options:
  -h, --help  show this help message and exit
  -s, --search   text for search
  --txt   Write txt File
  --html  Write html File
  --updateupgrade to latest version
  -g, --get   Download exploit files
  
autopkgtest [23:24:28]: test command1: ---]
autopkgtest [23:24:28]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL stderr: 
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
autopkgtest [23:24:28]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
  BASIC_INFO_MESSAGE = """
autopkgtest [23:24:28]:  summary
command1 FAIL stderr: 
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'


[0] https://ci.debian.net/packages/p/pompem/testing/arm64

Bug#1073486: marked as done (genimage: FTBFS: ./test/test-setup.sh: line 117: fdisk: command not found)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 23:04:39 +
with message-id 
and subject line Bug#1073486: fixed in genimage 17-3
has caused the Debian Bug report #1073486,
regarding genimage: FTBFS: ./test/test-setup.sh: line 117: fdisk: command not 
found
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> SKIP: test/misc.test 1 # SKIP qemu (missing qemu-img of dd,diff,qemu-img)
> SKIP: test/misc.test 2 # SKIP fit (missing dtc,mkimage of mkimage,dtc)
> SKIP: test/misc.test 3 # SKIP rauc (missing rauc)
> SKIP: test/misc.test 4 # SKIP android-sparse (missing simg2img)
> SKIP: test/misc.test 5 # SKIP fip (missing fiptool)
> PASS: test/flash.test 1 - flash
> SKIP: test/flash.test 2 # SKIP jffs2 (missing mkfs_jffs2)
> SKIP: test/flash.test 3 # SKIP ubifs (missing mkfs_ubifs)
> SKIP: test/flash.test 4 # SKIP ubi (missing ubinize)
> SKIP: test/filesystem.test 1 # SKIP cpio (missing cpio)
> SKIP: test/filesystem.test 2 # SKIP cramfs (missing mkcramfs)
> SKIP: test/filesystem.test 3 # SKIP iso (missing genisoimage)
> SKIP: test/filesystem.test 4 # SKIP f2fs (missing 
> fsck_f2fs,sload_f2fs,mkfs_f2fs of mkfs_f2fs,sload_f2fs,fsck_f2fs)
> SKIP: test/filesystem.test 5 # SKIP squashfs (missing mksquashfs)
> PASS: test/filesystem.test 6 - tar
> SKIP: test/filesystem.test 7 # SKIP vfat (missing mcopy,mkdosfs of 
> dd,mkdosfs,mcopy)
> SKIP: test/ext.test 1 # SKIP ext2 (missing genext2fs of genext2fs,e2fsck)
> SKIP: test/ext.test 2 # SKIP ext2percent (missing genext2fs of 
> genext2fs,e2fsck)
> SKIP: test/ext.test 3 # SKIP ext3 (missing genext2fs of genext2fs,e2fsck)
> SKIP: test/ext.test 4 # SKIP ext4 (missing genext2fs of genext2fs,e2fsck)
> FAIL: test/ext.test 5 - mke2fs
> ERROR: test/ext.test - exited with status 1
> PASS: test/genimage.test 1 - exec
> PASS: test/genimage.test 2 - exec-fail
> SKIP: test/genimage.test 3 # SKIP includepath1 (missing sfdisk-gpt,fdisk-gpt 
> of fdisk-gpt,sfdisk-gpt)
> SKIP: test/genimage.test 4 # SKIP includepath2 (missing sfdisk-gpt,fdisk-gpt 
> of fdisk-gpt,sfdisk-gpt,includepath)
> SKIP: test/genimage.test 5 # SKIP includepath3 (missing sfdisk-gpt,fdisk-gpt 
> of fdisk-gpt,sfdisk-gpt,includepath)
> SKIP: test/genimage.test 6 # SKIP includepath4 (missing sfdisk-gpt,fdisk-gpt 
> of fdisk-gpt,sfdisk-gpt,includepath)
> SKIP: test/genimage.test 7 # SKIP includepath5 (missing !includepath)
> SKIP: test/hdimage.test 1 # SKIP hdimage (missing sfdisk,fdisk of 
> fdisk,sfdisk)
> PASS: test/hdimage.test 2 - hdimage2
> SKIP: test/hdimage.test 3 # SKIP hdimage4 (missing sfdisk-gpt,fdisk-gpt of 
> fdisk-gpt,sfdisk-gpt)
> SKIP: test/hdimage.test 4 # SKIP hdimage5 (missing sfdisk-gpt,fdisk-gpt of 
> fdisk-gpt,sfdisk-gpt)
> SKIP: test/hdimage.test 5 # SKIP hdimage6 (missing sfdisk,fdisk of 
> fdisk,sfdisk)
> SKIP: test/hdimage.test 6 # SKIP hdimage7 (missing sfdisk-gpt,fdisk-gpt of 
> fdisk-gpt,sfdisk-gpt)
> SKIP: test/hdimage.test 7 # SKIP hdimage-hybrid (missing sfdisk-gpt,fdisk-gpt 
> of fdisk-gpt,sfdisk-gpt)
> PASS: test/hdimage.test 8 - hdimage syntax
> PASS: test/hdimage.test 9 - gpt-overlap1
> PASS: test/hdimage.test 10 - gpt-overlap2
> PASS: test/hdimage.test 11 - gpt-overlap3
> SKIP: test/hdimage.test 12 # SKIP gpt-partition-types (missing sfdisk,fdisk 
> of fdisk,sfdisk)
> PASS: test/hdimage.test 13 - gpt-invalid-partition-types
> PASS: test/hdimage.test 14 - bootloader-hole1
> PASS: test/hdimage.test 15 - bootloader-hole2
> PASS: test/hdimage.test 16 - bootloader-hole3
> PASS: test/hdimage.test 17 - bootloader-hole4
> PASS: test/hdimage.test 18 - bootloader-hole5
> PASS: test/hdimage.test 19 - hdimage no-partition
> ===
>genimage 17: ./test-suite.log
> ===
> 
> # TOTAL: 48
> # PASS:  16
> # SKIP:  30
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 1
> 
> .. contents:: :depth: 2
> 
> PASS: test/genimage
> ===
> 
> ./test/test-setup.sh: line 116: sfdisk: command not found
> ./test/test-setup.sh: line 117: fdisk: command not found
> 7+0 records in
> 7+0 records out
> 3584 bytes (3.6 kB, 3.5 KiB) copied, 6.5674e-05 s, 54.6 MB/s
> 7+0 records in
> 7+0 records out
> 3584 bytes (3.6 kB, 3.5 

Bug#1074499: python-pydub: autopkgtest failure with Python 3.12

[Yogeswaran Umasankar]

Source: python-pydub
Version: 0.24.1-1
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: y...@debian.org
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Dear Maintainer,

python-pydub autopkgtests fail with Python 3.12  [0].

autopkgtest [22:58:42]: test command1: [---
/tmp/autopkgtest.2iyUmh/tree/pydub/utils.py:300: SyntaxWarning: invalid escape 
sequence '\('
  m = re.match('([su]([0-9]{1,2})p?) \(([0-9]{1,2}) bit\)$', token)
/tmp/autopkgtest.2iyUmh/tree/pydub/utils.py:301: SyntaxWarning: invalid escape 
sequence '\('
  m2 = re.match('([su]([0-9]{1,2})p?)( \(default\))?$', token)
/tmp/autopkgtest.2iyUmh/tree/pydub/utils.py:310: SyntaxWarning: invalid escape 
sequence '\('
  elif re.match('(flt)p?( \(default\))?$', token):
/tmp/autopkgtest.2iyUmh/tree/pydub/utils.py:314: SyntaxWarning: invalid escape 
sequence '\('
  elif re.match('(dbl)p?( \(default\))?$', token):
autopkgtest [22:58:42]: test command1: ---]
autopkgtest [22:58:42]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL stderr: 
/tmp/autopkgtest.2iyUmh/tree/pydub/utils.py:300: SyntaxWarning: invalid escape 
sequence '\('

[0] https://ci.debian.net/packages/p/python-pydub/testing/arm64/

Processed (with 1 error): Re: wicd: Depends on unmaintained pygtk

[Debian Bug Tracking System]

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

> tags 885140 -bullseye
Bug #885140 [src:wicd] wicd: Depends on unmaintained pygtk
Removed tag(s) bullseye.
> archive 885140
Bug #885140 [src:wicd] wicd: Depends on unmaintained pygtk
Bug 885140 cannot be archived
>
End of message, stopping processing here.

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

Bug#1074252: marked as done (qpdfview: unsatisfied dependencies after upgrading qt6 to version 6.6)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 18:45:09 -0400
with message-id 
and subject line closing 1074252 qpdfview QT 6.6 transition
has caused the Debian Bug report #1074252,
regarding qpdfview: unsatisfied dependencies after upgrading qt6 to version 6.6
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.)


-- 
1074252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qpdfview
Version: 0.5.0+ds-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: retecompu...@mag4.it

Dear Maintainer,
upgrading qt6 to version 6.6 removes qpdfview. Reinstall is impossible with the
following unsatisfied dependencies:
 qpdfview : Dipends: libqt6concurrent6t64 (>= 6.1.2) but is uninstallable
Dipends: libqt6dbus6t64 (>= 6.1.2) but is uninstallable
Dipends: libqt6gui6t64 (>= 6.4.0) but is uninstallable
Dipends: libqt6printsupport6t64 (>= 6.1.2) but is uninstallable
Dipends: libqt6sql6t64 (>= 6.1.2) but is uninstallable
Dipends: libqt6widgets6t64 (>= 6.3.0) but is uninstallable
 qpdfview-djvu-plugin : Dipends: libqt6gui6t64 (>= 6.1.2) but is uninstallable
Dipends: libqt6widgets6t64 (>= 6.1.2) but is
uninstallable
 qpdfview-pdf-poppler-plugin : Dipends: libqt6gui6t64 (>= 6.1.2) but is
uninstallable
   Dipends: libqt6widgets6t64 (>= 6.3.0) but is
uninstallable
 qpdfview-ps-plugin : Dipends: libqt6gui6t64 (>= 6.1.2) but is uninstallable
  Dipends: libqt6widgets6t64 (>= 6.1.2) but is
uninstallable
Regards!

Guido


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

Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

Hello,

This has been fixed in 0.5.0+ds-5+b1.

Cheers :)

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄
--- End Message ---

Bug#1042816: marked as done (x2goclient segfaults during connect under Wayland)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:35:53 +
with message-id 
and subject line Bug#1042816: fixed in x2goclient 4.1.2.3-2
has caused the Debian Bug report #1042816,
regarding x2goclient segfaults during connect under Wayland
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.)


-- 
1042816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x2goclient
Version: 4.1.2.2-2+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: juergen.fuchsber...@uni-graz.at

x2goclient crashes with segfault under wayland when connecting to a
remote x2go server. This bug is described under
https://bugzilla.redhat.com/show_bug.cgi?id=2018740.
This happens since upgrading from bullseye to bookworm.

Known workaround is starting it with QT_QPA_PLATFORM=xcb set, i.e.:
env QT_QPA_PLATFORM=xcb x2goclient

Log:
130 juf@wegc203081 ~ % x2goclient   
   :(
QSocketNotifier: Can only be used with threads started with QThread
x2go-INFO-1> "Starting X2Go Client 4.1.2.2..."
x2go-WARNING-1> English language requested, not loading translator.
x2go-WARNING-1> English language requested, not loading translator.
x2go-INFO-3> "Started X2Go Client."
x2go-INFO-8> "Starting connection to server: wegc203089:22"
RESUMING SESSION is KDRIVE:  false
[1]6097 segmentation fault  x2goclient


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 x2goclient depends on:
ii  libc6 2.36-9+deb12u1
ii  libcups2  2.4.2-3+deb12u1
ii  libgcc-s1 12.2.0-14
ii  libldap-2.5-0 2.5.13+dfsg-5
ii  libqt5core5a  5.15.8+dfsg-11
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5network55.15.8+dfsg-11
ii  libqt5svg55.15.8-3
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5x11extras5  5.15.8-2
ii  libssh-4  0.10.5-2
ii  libstdc++612.2.0-14
ii  libx11-6  2:1.8.4-2+deb12u1
ii  libxpm4   1:3.5.12-1.1
ii  nxproxy   2:3.5.99.26-5+b1
ii  openssh-client1:9.2p1-2

Versions of packages x2goclient recommends:
ii  openssh-server  1:9.2p1-2
ii  rdesktop1.9.0-2+b1

Versions of packages x2goclient suggests:
pn  pinentry-x2go  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: x2goclient
Source-Version: 4.1.2.3-2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated x2goclient package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Jun 2024 00:16:35 +0200
Source: x2goclient
Architecture: source
Version: 4.1.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 1042816
Changes:
 x2goclient (4.1.2.3-2) unstable; urgency=medium
 .
   * debian/control:
 + Drop Reinhard Tartler from Uploaders: field (on personal request).
   * debian/:
 + Introduce x2goclient wrapper that sets QT_QPA_PLATFORM to xcb and
   enables QT_AUTO_SCREEN_SCALE_FACTOR before launching the real x2goclient
   executable. (Closes: #1042816).
Checksums-Sha1:
 3d0e911c98cf48f19e6e49b537ae52f7873184da 2461 x2goclient_4.1.2.3-2.dsc
 198278c7702955a2f38b8711e29b38409bcadf41 23168 
x2goclient_4.1.2.3-2.debian.tar.xz
 b4d76bc034202b0fc6f23b7711faa5ce1abfa236 13566 
x2goclient_4.1.2.3-2_source.buildinfo
Checksums-Sha256:
 25cbcd28da32c6f6e177a000b54380956c900c60b44c6b18168eaae06b00904a 2461 
x2goclient_4.1.2.3-2.dsc
 

Bug#1050400: marked as done (aws-checksums: build-depends on non-existing libaws-c-common-dev)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:33:09 +
with message-id 
and subject line Bug#1074347: Removed package(s) from unstable
has caused the Debian Bug report #1050400,
regarding aws-checksums: build-depends on non-existing libaws-c-common-dev
to be marked as done.

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

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


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

Hi, aws-checksums build-depends on libaws-c-common-dev which does not
exist anywhere in the archive. This is the case since 2022-11-10.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.1.13-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1029332: marked as done (libaws-checksums1.0.0: Depends: libaws-c-common1 (>= 0.8.4) but it is not installable)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:33:09 +
with message-id 
and subject line Bug#1074347: Removed package(s) from unstable
has caused the Debian Bug report #1029332,
regarding libaws-checksums1.0.0: Depends: libaws-c-common1 (>= 0.8.4) but it is 
not installable
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.)


-- 
1029332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaws-checksums1.0.0
Version: 0.1.13-1
Severity: serious

The following packages have unmet dependencies:
 libaws-checksums1.0.0 : Depends: libaws-c-common1 (>= 0.8.4) but it is not 
installable
--- End Message ---
--- Begin Message ---
Version: 0.1.13-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#999965: marked as done (shadowsocks-libev: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:32:38 +
with message-id 
and subject line Bug#1074328: Removed package(s) from unstable
has caused the Debian Bug report #65,
regarding shadowsocks-libev: depends on obsolete pcre3 library
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.)


-- 
65: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shadowsocks-libev
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Version: 3.3.5+ds-10+rm

Dear submitter,

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

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

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

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

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

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

Bug#1072934: marked as done (shadowsocks-libev: Consider removing the package)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:32:38 +
with message-id 
and subject line Bug#1074328: Removed package(s) from unstable
has caused the Debian Bug report #1072934,
regarding shadowsocks-libev: Consider removing the package
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.)


-- 
1072934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shadowsocks-libev
Version: 3.3.5+ds-10
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com
Tags: sid

Hi,

Following the previous communication in March, I am considering to take action
and remove related packages in the ss-libev ecosystem. Package shadowsocks-libev
will be removed together with simple-obfs.

I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-17). If you
have any questions, please feel free to let me know.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 3.3.5+ds-10+rm

Dear submitter,

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

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

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

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

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

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

Bug#1073791: marked as done (shadowsocks-v2ray-plugin: Consider removing the package)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:29:43 +
with message-id 
and subject line Bug#1074273: Removed package(s) from unstable
has caused the Debian Bug report #1073791,
regarding shadowsocks-v2ray-plugin: Consider removing the package
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.)


-- 
1073791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shadowsocks-v2ray-plugin
Version: 1.3.1-4
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com 
shadowsocks-v2ray-plu...@packages.debian.org
Tags: sid

Hi,

Following the previous communication in March, I am considering to take action
and remove related packages in the ss-libev ecosystem. Package 
shadowsocks-v2ray-plugin
will be removed together with shadowsocks-libev.

I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-25). If you
have any questions, please feel free to let me know.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.3.1-4+rm

Dear submitter,

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

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

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

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

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

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

Bug#1072807: marked as done (rust-instant: crate is abandoned - recommended replacement is web_time)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:32:03 +
with message-id 
and subject line Bug#1074285: Removed package(s) from unstable
has caused the Debian Bug report #1072807,
regarding rust-instant: crate is abandoned - recommended replacement is web_time
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.)


-- 
1072807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-instant
Version: 0.1.12-3
Severity: serious
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The crate is buggy and unmaintained, according to this:
https://github.com/sebcrozet/instant/issues/52

The recommended (seemingly drop-in) replacement is web_time.

Raising severity as this crate seems unsuitable for long-term stable
distribution.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZj9l0ACgkQLHwxRsGg
ASHS+BAAmPfnmepyuOeGCTvaRhn5ec9CCVG1wFJ4Js4Ecja4vP5dkFp1pXg9XXky
iO2NoH0MC6fjjx5p0/6wPLy3L2UDqhnO/iqpvASCkt0eLIfY/v9ivaNgkf/59unt
aRVxXdeKVUKyJc1n3kW2tW5qpNe1WR/n7QdBO6pmXLZa8X13NhC0kBsoBk0fAYDr
gYqUAfy+2wLIU0o2qQpqRm0zXn5GxUlhnz6wERfCedryOzOfMaRtZyqWcZ5c+6Rw
28fStzt5zAJ+1gUR10J5PLS1u96x2cy0Yh3c6HIpjWmVcyOeiBRbhPYohM+NFtbR
xFRo1yt6gqNigmH12wramtnu9JwwVaStPiNwTYhx6nORRagOMhoODS0pQDcXSrGz
mX0sUDR935+NmTe0uCZ2DiS5PB9KrHFyvKQTJr17AkEq2WrkWNXsu40qgZzaf4K1
Lh6Iy61WANCzmyJ+iqhD3FVggLKx76mVcBtK+Oju6Ly6F4KIk5fhCiTjoyLVhjji
pAMJ9QrwVu/kUSMA5p9/XbHA+cU1tY7lY0K/ZRqm9aoOTh/6ianInF4QzpPn0/Ba
JQN7KuhzSRfKwDdthWmhUbFB8p1e8WckbWI0OTK2UYR/AxQExmoknBLqI8vLD7Fj
3JKrU5hnKwcqVzv91vKAgdTPPLYfsoFWm2N2GEjOga6p4/oPHMU=
=MNno
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.1.12-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#1066504: marked as done (wuzzah: FTBFS: utmpx-wrapper.c:8:23: error: implicit declaration of function ‘bail’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 22:26:10 +
with message-id 
and subject line Bug#1071904: Removed package(s) from unstable
has caused the Debian Bug report #1066504,
regarding wuzzah: FTBFS: utmpx-wrapper.c:8:23: error: implicit declaration of 
function ‘bail’ [-Werror=implicit-function-declaration]
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.)


-- 
1066504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wuzzah
Version: 0.53-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wall -pedantic -c utmpx-wrapper.c
> utmpx-wrapper.c: In function ‘setutent_wrapper’:
> utmpx-wrapper.c:8:23: error: implicit declaration of function ‘bail’ 
> [-Werror=implicit-function-declaration]
> 8 | if(ut_fd < 0) bail("shit man, no utmp record?", 1);
>   |   ^~~~
> utmpx-wrapper.c: In function ‘getutent_wrapper’:
> utmpx-wrapper.c:16:1: warning: control reaches end of non-void function 
> [-Wreturn-type]
>16 | }
>   | ^
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:206: utmpx-wrapper.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/wuzzah_0.53-3.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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 ---
Version: 0.53-3.1+rm

Dear submitter,

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

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

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

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

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

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

Processed: Bug#1042816 marked as pending in x2goclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042816 [x2goclient] x2goclient segfaults during connect under Wayland
Added tag(s) pending.

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

Bug#1042816: marked as pending in x2goclient

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1042816 in x2goclient 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/debian-remote-team/x2goclient/-/commit/c0e99d8aa66e01b319bc5860f59c935a57f9e349


debian/: Introduce x2goclient wrapper that sets QT_QPA_PLATFORM to xcb and 
enables QT_AUTO_SCREEN_SCALE_FACTOR before launching the real x2goclient 
executable. (Closes: #1042816).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042816

Bug#1065852: marked as done (dput-ng: Please drop dependencies on python3-distutils)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 21:37:09 +
with message-id 
and subject line Bug#1065852: fixed in dput-ng 1.40
has caused the Debian Bug report #1065852,
regarding dput-ng: Please drop dependencies on python3-distutils
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.)


-- 
1065852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dput-ng
Version: 1.39
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: dput-ng
Source-Version: 1.40
Done: Alexandre Detiste 

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

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

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated dput-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 29 Jun 2024 22:44:40 +0200
Source: dput-ng
Architecture: source
Version: 1.40
Distribution: unstable
Urgency: medium
Maintainer: dput-ng Maintainers 
Changed-By: Alexandre Detiste 
Closes: 1065852
Changes:
 dput-ng (1.40) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove extraneous dependency on python3-distutils (Closes: #1065852)
Checksums-Sha1:
 9927695c67d241b86789880ce03aca52e0aab067 2256 dput-ng_1.40.dsc
 12e3436711c2f56ef8e69533a3b375bb2b27e64c 88476 dput-ng_1.40.tar.xz
 6abd6ee327c6b736eab046a19fa330f44428029f 9250 dput-ng_1.40_source.buildinfo
Checksums-Sha256:
 0330b0156aeff2b87cc889f70e8be03d9414bd6ccc7cf6e2cfb36c758548176e 2256 
dput-ng_1.40.dsc
 a774a6a12de7afb3853bd7a0f02b0201c2d4c1d30f4b03531c8e8644cf83ef72 88476 
dput-ng_1.40.tar.xz
 60721664bb65ee8fbfd247a09cca69c27a9b3ceb0f8baf45d89aa100337f14e9 9250 
dput-ng_1.40_source.buildinfo
Files:
 7f93222ce63a46cbad87e7ea34e7bd7d 2256 devel optional dput-ng_1.40.dsc
 d571f03c28b020941c370f733bd4971b 88476 devel optional dput-ng_1.40.tar.xz
 1aa4e51eaa3d645bcc04084f2faa5e4a 9250 devel optional 
dput-ng_1.40_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmaAdZYRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBqmOxAAoQAeUFRlwSlfhiBeImINpwVE7e/WJ+z4
G1TRKIOaH8/XAxUf8CEIwcT7ndIbFrSRpFv7uxRS87nyfNdcLM2ak22P5qP3ES8D
OunFhUH43z7+jPtLEhDLyrvVVhF1RF0EDeJYy1AI4SrSsxQJvxwAmOQpG6qYpjmQ
1mN17KG5UeFN7yECYt4rRmS6/tp4P4YDxZMJNqw43hJoVaTxMuZC4h79gGDG1M51
v3yNX2GYYocClgzlPr/61Rxu1EfQsuvDGZNJNNLaiMiFLzmb517O9GTId5WCyzUc
seWGbdTLameh6I6/v7ejVYDtd25+HissBlETqFaWx7unuP0GHjzlSFS8kzwRwQpW
+45a5K3NPG3sCI7CtpBicui8xyVhVmNUcvaV345tNzb1xOjAe3c10tSPv78iiOBl
1wjh+pDMdZfmnq1/BxRQYW3MGoH2DlWVp3yLA2nOvhgFOqSZs1gxg6dbCfwgnTd1
lYYxK2/lvXxU+ukWkR6HMnvEq3+E8qmRCtArE9HzWO6ellqYM+uQWVrPl6H6G8Of
6OEG2TgkhbzS/TYe3OIgmvhGSI1hiy3YJNm7NNNoFU6ZljIu4dpyf4S0R2y+6ax5
S0/KCGEJagsz3Y3mNjh1s0nho3qyF4FKiyCDTni3TSsf4NLYsbrXbr8uuC24oD2d
7YUBTd8N2Vw=
=b9ML
-END PGP SIGNATURE-



pgpmo5XQ6ZMQl.pgp
Description: PGP signature
--- End Message ---

Processed: severity of 1066011 is normal

[Debian Bug Tracking System]

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

> severity 1066011 normal
Bug #1066011 [src:whipper] whipper: Please drop dependencies on 
python3-distutils
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: unarchiving 1056147

[Debian Bug Tracking System]

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

> unarchive 1056147
Bug #1056147 {Done: Andreas Beckmann } [src:midge] midge 
possibly contains non-DFSG-free examples 
Unarchived Bug 1056147
> thanks
Stopping processing here.

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

Processed: severity of 1066011 is serious

[Debian Bug Tracking System]

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

> severity 1066011 serious
Bug #1066011 [src:whipper] whipper: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1065989 is serious

[Debian Bug Tracking System]

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

> severity 1065989 serious
Bug #1065989 [src:tulip] tulip: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1065936 is serious

[Debian Bug Tracking System]

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

> severity 1065936 serious
Bug #1065936 [src:python-requests-cache] python-requests-cache: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1073218: marked as done (src:vim-eblook: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 20:52:03 +
with message-id 
and subject line Bug#1073218: fixed in vim-eblook 1.4.0-1.1
has caused the Debian Bug report #1073218,
regarding src:vim-eblook: fails to migrate to testing for too long: uploader 
built arch:all binaries
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.)


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

Source: vim-eblook
Version: 1.2.3+git2020-3.1
Severity: serious
Control: close -1 1.4.0-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:vim-eblook has been trying to migrate for 
37 days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=vim-eblook



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vim-eblook
Source-Version: 1.4.0-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated vim-eblook 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, 14 Jun 2024 21:11:38 +0200
Source: vim-eblook
Architecture: source
Version: 1.4.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yukiharu YABUKI 
Changed-By: Paul Gevers 
Closes: 1073218
Changes:
 vim-eblook (1.4.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1073218)
Checksums-Sha1:
 1b06703259d2992140a016d36735f2dc5ce1058b 1645 vim-eblook_1.4.0-1.1.dsc
 f1a9a328ea45a1ccfe52e160de97c5f0de202568 2708 
vim-eblook_1.4.0-1.1.debian.tar.xz
Checksums-Sha256:
 30c734933010fdb6e053073620d33bd3a3ec1e23bb32f0dcb2ea692d52eb966b 1645 
vim-eblook_1.4.0-1.1.dsc
 de589a52e31dbc7dfa1b05780ec46119ddf2742e07bf40137efb2896f8274c9e 2708 
vim-eblook_1.4.0-1.1.debian.tar.xz
Files:
 916a32dcb876a27b4e0fa9f23d1b9d33 1645 editors optional vim-eblook_1.4.0-1.1.dsc
 0941e5f8104881b5937eedf7813675c2 2708 editors optional 
vim-eblook_1.4.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZsliIACgkQnFyZ6wW9
dQo1zgf9EJDkB3gJeIvFIPczuY/TEnSm6uChj8Zjo1AhN5GTVp4Cnt2FIv4u/lhw
c9NOdLVYIeDiZzgpV2emSpe7oN8sMgzg/T3/XJyKEjcaQkZGiMePUQj8IJ5o0N2w
NX3U35Kf88IhgB6//HRAsZK9ZkMnaWBG4hF4oPWJBaBZI5XK3LH5RQXKvTKlSaW1
i6uwa7Grz5ZRmX5Gpn0H8iZfjpqVn3ebm/77F+3VunAcFdidTahxz4oaUX5xUVIu
6vwZ9rR8diNm9PiKW2hCJMJ4+4Dp5l1zwbxUCLb+dAtP1X91oXh218bcgCA0MnYA

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

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 20:50:11 +
with message-id 
and subject line Bug#1054780: fixed in spopt 0.6.1-1
has caused the Debian Bug report #1054780,
regarding spopt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> file spopt.py (for module spopt) not found
> creating /<>/.pybuild/cpython3_3.11_spopt/build/spopt
> copying spopt/_version.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt
> copying spopt/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt
> copying spopt/BaseClass.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt
> creating /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/p_dispersion.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/base.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/p_median.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/coverage.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/util.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> copying spopt/locate/p_center.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/locate
> creating /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/spenc.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/ward.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/base.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/region_k_means.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/objective_function.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/maxp.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/csgraph_utils.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/random_region.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/azp.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/components.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/azp_util.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/util.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> copying spopt/region/skater.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/region
> creating /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_random_regions.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_p_center.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_region_util.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_azp.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_p_dispersion.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_lscp.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_spenc.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_locate_util.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_lscpb.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_mclp.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_p_median.py -> 
> /<>/.pybuild/cpython3_3.11_spopt/build/spopt/tests
> copying spopt/tests/test_clscp-so.py -> 
> 

Processed: python3.12 transition

[Debian Bug Tracking System]

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

> severity 1065863 serious
Bug #1065863 [src:galpy] galpy: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065871 serious
Bug #1065871 [src:grokevt] grokevt: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065873 serious
Bug #1065873 [src:hamster-time-tracker] hamster-time-tracker: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065874 serious
Bug #1065874 [src:icu] icu: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065882 serious
Bug #1065882 [src:jhbuild] jhbuild: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065884 serious
Bug #1065884 [src:keras] keras: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065885 serious
Bug #1065885 [src:keras-applications] keras-applications: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065886 serious
Bug #1065886 [src:keras-preprocessing] keras-preprocessing: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065899 serious
Bug #1065899 [src:lomiri-calculator-app] lomiri-calculator-app: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065900 serious
Bug #1065900 [src:matrix-synapse] matrix-synapse: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065901 serious
Bug #1065901 [src:mdtraj] mdtraj: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065903 serious
Bug #1065903 [src:mm-common] mm-common: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065905 serious
Bug #1065905 [src:mongo-cxx-driver-legacy] mongo-cxx-driver-legacy: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065912 serious
Bug #1065912 [src:openscap-daemon] openscap-daemon: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065917 serious
Bug #1065917 [src:pulseaudio-dlna] pulseaudio-dlna: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065920 serious
Bug #1065920 [src:pypeg2] pypeg2: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065923 serious
Bug #1065923 [src:python-certbot] python-certbot: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065926 serious
Bug #1065926 [src:python-docker] python-docker: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065928 serious
Bug #1065928 [src:python-enigma] python-enigma: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065937 serious
Bug #1065937 [src:python-sparkpost] python-sparkpost: Please drop dependencies 
on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065943 serious
Bug #1065943 [src:pytorch-cuda] pytorch-cuda: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065945 serious
Bug #1065945 [src:q2-emperor] q2-emperor: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065946 serious
Bug #1065946 [src:q2-sample-classifier] q2-sample-classifier: Please drop 
dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065952 serious
Bug #1065952 [src:s-tui] s-tui: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065953 serious
Bug #1065953 [src:sagemath] sagemath: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065958 serious
Bug #1065958 [src:soapysdr] soapysdr: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065984 serious
Bug #1065984 [src:thefuck] thefuck: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065994 serious
Bug #1065994 [src:ust] ust: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065998 serious
Bug #1065998 [src:versiontools] versiontools: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1066009 serious
Bug #1066009 [src:wfuzz] wfuzz: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1066012 serious
Bug #1066012 [src:zfs-dkms] zfs-dkms: Please drop dependencies on 

Bug#1073219: marked as done (src:ifupdown-ng: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 20:42:54 +
with message-id 
and subject line Bug#1073219: fixed in ifupdown-ng 0.12.1-5.1
has caused the Debian Bug report #1073219,
regarding src:ifupdown-ng: fails to migrate to testing for too long: uploader 
built arch:all binaries
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.)


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

Source: ifupdown-ng
Version: 0.12.1-4
Severity: serious
Control: close -1 0.12.1-5
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ifupdown-ng has been trying to migrate for 
39 days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ifupdown-ng



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ifupdown-ng
Source-Version: 0.12.1-5.1
Done: Paul Gevers 

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ifupdown-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 21:13:07 +0200
Source: ifupdown-ng
Architecture: source
Version: 0.12.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Ifupdown NG Maintainers 
Changed-By: Paul Gevers 
Closes: 1073219
Changes:
 ifupdown-ng (0.12.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1073219)
Checksums-Sha1:
 a7bd7dddc8318852d3951eaedae4fd096e6f7856 2780 ifupdown-ng_0.12.1-5.1.dsc
 ef55613e71d34237a0abfc53a44ae359cd699d49 5596 
ifupdown-ng_0.12.1-5.1.debian.tar.xz
Checksums-Sha256:
 73eb8e704da1545547298627f2699cb19e2bfb71deb9cfef2ea8ece900157a67 2780 
ifupdown-ng_0.12.1-5.1.dsc
 29a354ddeb478fb5fe4b7549ad40cb29a347a6dd08d0fd3b03cf8e64b603fcf9 5596 
ifupdown-ng_0.12.1-5.1.debian.tar.xz
Files:
 32a01e7bfea7f0a025877ed6e8d6dc52 2780 admin optional ifupdown-ng_0.12.1-5.1.dsc
 aa1713c9be9cc7b011c3aa6f5dc1c94a 5596 admin optional 
ifupdown-ng_0.12.1-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZsllIACgkQnFyZ6wW9
dQpj3gf/cPwj3Jvow1XcJMx53YfbSIdPHBv0j1/j7k/JvrVv3Y4oVB7RqA6ZQQfa
k+1DFc3nUktKMVMMlrX1BAMrSKBDvLPJDa+RzrREhLDUDWTDWD4P3DKtU3s7ogby
E8LUU8lczvMzhQP6ismfCGXGST10IOuczqPse1u5v1bcd0SM7iMbUhJnJoNdytRK
BAnukEMhaJx4Fikn4aFpagvFhR8qmC29wFUFFweguNVUXr1oBB8EqtUi7oxC2GkX

Bug#1065853: marked as done (drm-info: Please drop dependencies on python3-distutils)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 20:42:26 +
with message-id 
and subject line Bug#1065853: fixed in drm-info 2.6.0-2
has caused the Debian Bug report #1065853,
regarding drm-info: Please drop dependencies on python3-distutils
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.)


-- 
1065853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drm-info
Version: 2.6.0-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: drm-info
Source-Version: 2.6.0-2
Done: Birger Schacht 

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

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated drm-info 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: Sat, 29 Jun 2024 21:58:34 +0200
Source: drm-info
Architecture: source
Version: 2.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sway and related packages team 
Changed-By: Birger Schacht 
Closes: 1065853
Changes:
 drm-info (2.6.0-2) unstable; urgency=medium
 .
   * Fix d/watch
   * d/control:
+ Drop python3-distutils dependency (Closes: #1065853)
+ Replace pkg-config with pkgconf
Checksums-Sha1:
 b34c5bcb5fbf27182df463faf368edc93e1629a1 2123 drm-info_2.6.0-2.dsc
 a3645fd2a5ad5744abd1489422817e74f563dcd5 2972 drm-info_2.6.0-2.debian.tar.xz
 0d4a6edbd800cb8b2cc1e7f882250c4c631adf73 7292 drm-info_2.6.0-2_amd64.buildinfo
Checksums-Sha256:
 86eb086462dcaac71317d52c9d6c7b720c46ab11681ff41aa9d4b94f8314e59f 2123 
drm-info_2.6.0-2.dsc
 66787ad8583ef933e8e9c43d990188b1e14ad8e7e920dce1f6ab322111f9a935 2972 
drm-info_2.6.0-2.debian.tar.xz
 a4e91fc3cfdfd2ab94272c377cd8a245532c3035b75272c5a30d32a386a0deea 7292 
drm-info_2.6.0-2_amd64.buildinfo
Files:
 f9e98eed7ec9698f5ae85566059e5c3f 2123 x11 optional drm-info_2.6.0-2.dsc
 214975a9016e9f9f90f0d6243d9b0efb 2972 x11 optional 
drm-info_2.6.0-2.debian.tar.xz
 f9812728fb76bc1a245e77aa4ac25afa 7292 x11 optional 
drm-info_2.6.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAmaAaUkSHGJpcmdlckBk
ZWJpYW4ub3JnAAoJECoMXWDyBL2w9zUQAMXO149x3JQ3j/5eP9X/CzEJxw2POgSP
SlquNC26z1gMyR4QE4in2dUSAP0l3deyUjc9daAzhmVeNP9oLBSPQG2wBf9XJT2L
xhTbQ+SeI6zYAQtwVEhnQ69NqI1v72f87TptXfRL+7yk3xHXQPYY5HkSyD750r5a
g4uFivkI6XRdus5Y/c1h8JKiXlqn76qHYukwoa1QA+GQRXI4OrZO50GUQGz7ynsR
Czs28oidKUgvKWftNqbz/2x9rszDBgJoXe3FlUdcR+vEI/9AWVBvEnVeLWOBvvKW
MQ1sOOahS7/IgG2nGNAdh0PUA7pwfYUmPeixU8Lu+EEvwKKxTQfBzO1y+6bhVxl8
67xbmpllCZ+9peBKap6fEWfcNw78qxXxsauD2TPIQ1B4luojsiLV4Ia9dI+rwo1k
080cfs6vQxK3IhVxbli+VDUFNQzmcpgS5s31XoAQ5rHs/NHroraTsQ2wR6olp2Nr
Dq5+LvpnOug3EgvqvNmNVcoZVNfRJcczACE4hmsLGyzLxgmMb6WBmYT644A/Qczz
m4aTHj9Po9tLiKKhM9cJRSWREuGhHSCcNrXcdn4ceaSWLAJ/w318Oh+ZSrOL/Be9
2bIaw9f3spnvhRRvVzcd/dluf7xtxDySPVN1tGwEurUagr7+/boktI/U9galwTBn
qGaEpqehT6nH
=jtGj
-END PGP SIGNATURE-



pgp4VPgsoLHlB.pgp
Description: PGP signature
--- End Message ---

Processed: python3.12 transition

[Debian Bug Tracking System]

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

> severity 1065822 serious
Bug #1065822 [src:anki] anki: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065830 serious
Bug #1065830 [src:astropy] astropy: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065837 serious
Bug #1065837 [src:cappuccino] cappuccino: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065843 serious
Bug #1065843 [src:djvubind] djvubind: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065848 serious
Bug #1065848 [src:docker-compose] docker-compose: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065850 serious
Bug #1065850 [src:dogtag-pki] dogtag-pki: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065851 serious
Bug #1065851 [src:doxyqml] doxyqml: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065852 serious
Bug #1065852 [src:dput-ng] dput-ng: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065853 serious
Bug #1065853 [src:drm-info] drm-info: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
> severity 1065858 serious
Bug #1065858 [src:fades] fades: Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> severity 1065860 serious
Bug #1065860 [src:fonts-cantarell] fonts-cantarell: Please drop dependencies on 
python3-distutils
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1065822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065822
1065830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065830
1065837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065837
1065843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065843
1065848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065848
1065850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065850
1065851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065851
1065852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065852
1065853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065853
1065858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065858
1065860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1074482: marked as done (liboxygenstyleconfig5-6: missing Breaks+Replaces: liboxygenstyleconfig5-5 (<< 4:6))

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 19:35:08 +
with message-id 
and subject line Bug#1074482: fixed in oxygen 4:6.1.0-2
has caused the Debian Bug report #1074482,
regarding liboxygenstyleconfig5-6: missing Breaks+Replaces: 
liboxygenstyleconfig5-5 (<< 4:6)
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.)


-- 
1074482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liboxygenstyleconfig5-6
Version: 4:6.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

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

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

  Preparing to unpack .../liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb ...
  Unpacking liboxygenstyleconfig5-6:amd64 (4:6.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/locale/ar/LC_MESSAGES/liboxygenstyleconfig.mo', which is also in 
package liboxygenstyleconfig5-5:amd64 4:5.27.11-1
  Errors were encountered while processing:
   /var/cache/apt/archives/liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb

The conflicting files are 
/usr/share/locale/*/LC_MESSAGES/liboxygenstyleconfig.mo


cheers,

Andreas


liboxygenstyleconfig5-5=4:5.27.11-1_liboxygenstyleconfig5-6=4:6.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: oxygen
Source-Version: 4:6.1.0-2
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated oxygen 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: Sat, 29 Jun 2024 21:16:14 +0200
Source: oxygen
Architecture: source
Version: 4:6.1.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1074482
Changes:
 oxygen (4:6.1.0-2) experimental; urgency=medium
 .
   [ Patrick Franz ]
   * Add missing Breaks+Replaces for liboxygenstyleconfig5-6 against
 liboxygenstyleconfig5-5 (Closes: #1074482).
Checksums-Sha1:
 508255990920e565c728d40e3d5ec968380dd75f 3755 oxygen_6.1.0-2.dsc
 7965430e39c45cf287e89f02fe6e51e5e29596df 19312 oxygen_6.1.0-2.debian.tar.xz
 2571670476318a797e2585842a73d9ad5ee75599 15187 oxygen_6.1.0-2_source.buildinfo
Checksums-Sha256:
 d01ecd2e8e67cba793143cf38ba949891140e405f96270768c3a8b737fba8087 3755 
oxygen_6.1.0-2.dsc
 c590036362fa232d57a644ca0450c8d5e008b775a94b5e02b840523abcc18039 19312 
oxygen_6.1.0-2.debian.tar.xz
 b5a26b05634ec8df528246e1ba262cb667f169507a75ef022e7099e1334756d8 15187 
oxygen_6.1.0-2_source.buildinfo
Files:
 ef41c657bea7547b1cc63ef0430f27bb 3755 kde optional oxygen_6.1.0-2.dsc
 376588fe651d76e6acb53b1e34a79d9c 19312 kde optional 
oxygen_6.1.0-2.debian.tar.xz
 b2a67a0eeefc58d9f9e4f22e93b82bb4 15187 kde optional 
oxygen_6.1.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmaAXY0ACgkQnp96YDB3
/lbZxQ/+LCJOr0DkCj3YIIdi17a0UY2hHu0jgbH0uDNIyz8umTJvZkRDBPYBSIfQ
u+4nan8MAQfq68vX4OjOZWt0r5V4C/XGFRyTJoZYwmsQ3T/MrSm1vHGWj8NIfFyU
nimUJ9/AjV/gdgeeOwC+oAkdTrkBNfjMT7BPgeZGaDfMot6xkNSdxonh7EthOcaN
o3OHM5G4sniIskvsaGKx639QjQHVCxVXqGSY2E/R+WipbSYZwB9n2/1iJJ5DKbyf
Teaqimi4uEgTfI3O3lqLZCS/apbAScAR/bnAYUPION7tvGEgaVw/VtQ0pbgWd2z+
eKVPD2RVxY4J6eagE9LMFbdwXXJ2sx74eRnLgIbI/tqmpAv6ECARG9Yf/8V1Dk64
fieqarHufiN27WA8Qilr9ChC5Z2aopdlID0+nbnfPLU56tVwABAnHkKG9FMAIeCH

Bug#1073561: openbabel: FTBFS: failing tests test_tautomer_2[27]

[Adrian Bunk]

On Mon, Jun 17, 2024 at 04:58:46PM +0300, Andrius Merkys wrote:
> Source: openbabel
> Version: 3.1.1+dfsg-9
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> 
> Hi,
> 
> openbabel FTBFS both in unstable (if a fix for #1073327 is applied) and
> testing with the following:
> 
> 99% tests passed, 2 tests failed out of 229
> 
> Total Test time (real) = 317.34 sec
> 
> The following tests FAILED:
>   149 - test_tautomer_22 (Subprocess aborted)
>   154 - test_tautomer_27 (Subprocess aborted)
> Errors while running CTest
> 
> It is not clear when the FTBFS first started happening as these tests do not
> seem to be covered by openbabel's autopkgtest.

I just tried, and it built for me.

Does it still fail for you?

> Andrius

cu
Adrian

Bug#1074493: rust-simba: failing autopkgtests

[Jeremy Bícha]

Source: rust-simba
Version: 0.9.0-1
Severity: serious
X-Debbugs-CC: werdah...@riseup.net

rust-simba is unable to migrate to Testing because its autopkgtests are failing.

Specifically, these tests:

rust-simba:@ FLAKY non-zero exit status 101
librust-simba-dev:portable_simd FAIL non-zero exit status 101
librust-simba-dev:wide FLAKY non-zero exit status 101

https://qa.debian.org/excuses.php?package=rust-simba

Thank you,
Jeremy Bícha

Processed: bug 1074448 is forwarded to https://github.com/corrosion-rs/corrosion/issues/501

[Debian Bug Tracking System]

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

> forwarded 1074448 https://github.com/corrosion-rs/corrosion/issues/501
Bug #1074448 [src:corrosion] corrosion: fails to build with rustc >= 1.79
Set Bug forwarded-to-address to 
'https://github.com/corrosion-rs/corrosion/issues/501'.
> thanks
Stopping processing here.

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

Bug#1074484: marked as done (python-recipe-scrapers: Fails to build)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 18:22:17 +
with message-id 
and subject line Bug#1074484: fixed in python-recipe-scrapers 14.57.0-2
has caused the Debian Bug report #1074484,
regarding python-recipe-scrapers: Fails to build
to be marked as done.

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

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


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

The build tests for python-recipe-scrapers are failing.

build log excerpt

  File 
"/<>/.pybuild/cpython3_3.12_recipe-scrapers/build/tests/library/test_readme.py",
line 94, in get_list_lines
with open("README.rst") as f:
 ^^
FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'

full build log
=
https://buildd.debian.org/status/package.php?p=python-recipe-scrapers

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: python-recipe-scrapers
Source-Version: 14.57.0-2
Done: Christian Marillat 

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

Debian distribution maintenance software
pp.
Christian Marillat  (supplier of updated 
python-recipe-scrapers 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: Sat, 29 Jun 2024 19:55:27 +0200
Source: python-recipe-scrapers
Architecture: source
Version: 14.57.0-2
Distribution: unstable
Urgency: medium
Maintainer: Christian Marillat 
Changed-By: Christian Marillat 
Closes: 1074484
Changes:
 python-recipe-scrapers (14.57.0-2) unstable; urgency=medium
 .
   * Disable tests.  Seems to be hard to ran tests with volatile data.
 (Closes: #1074484)
Checksums-Sha1:
 bcc90cee74162f4d1bdc8cc355690d417fd93cee 2039 
python-recipe-scrapers_14.57.0-2.dsc
 68c4c2c7a6f0d27cec0585a86c987bbe00ce3c3f 2788 
python-recipe-scrapers_14.57.0-2.debian.tar.xz
 6832ee123795c3f1fdca051ade0ff94e50132578 7488 
python-recipe-scrapers_14.57.0-2_source.buildinfo
Checksums-Sha256:
 8ae8282153fbe3c15559e8f4118cf961c81b3fc40302d98e27d9f4a6d88fea67 2039 
python-recipe-scrapers_14.57.0-2.dsc
 e3a74ce24849bee6d1e05e0ca9fe2aa27bf12ea18ed1a6171829b6f09d906aa1 2788 
python-recipe-scrapers_14.57.0-2.debian.tar.xz
 bf0cd1a9ff7267fff4cc663228443df6d74b85728795d72b8ad9b0ef0ef676c5 7488 
python-recipe-scrapers_14.57.0-2_source.buildinfo
Files:
 6984f21e2fee68c8287bed0ae574a728 2039 python optional 
python-recipe-scrapers_14.57.0-2.dsc
 d74b42b7058a10c4b32b1e4c82ae97a0 2788 python optional 
python-recipe-scrapers_14.57.0-2.debian.tar.xz
 2d6ed3ecac8c2fca3665a5e877ded41c 7488 python optional 
python-recipe-scrapers_14.57.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAmaATD0ACgkQXICMK2VV
gRdEpw//Qryyga1k9Z8qaBQOzDDeAHd8Cko3f/ba1eNCqI/zTmt0zh/uowb6TjT7
0BiaJ3B6eIIntXXNoG929vJaqbZjdHOmXKNCgpShl1QW4eUkpA3zsebmE/ngNx+z
XOX8NylE/3fLnmXlIgKLixfO+MYaV7pDTBwdqDsBlRqEFnmxKceuiFceLx1A+iQI
mrxen+RxDEakthk3XHQ0rz2+jDOqLpFNlYCLgA6toB0qakjy60vPJSggmUGgtu/G
hngPNqqagGmOnoGgGZN+6YOxAsgyC5lWjVqBBtTdiLNAkm14JdzvHePWASKiEU55
yJmr8fxXgnAIoCuIDSjsWyA5kJQLGiV8S7FQ81bkAZYLbe3ysOFgvIzNd/7bkITy
w4QNlAbimqYKI1bRjiyYslVpFg79QAkF/D1DeSYKvmoVjt8m3MAjMlf00/a82y4g
snqL1HTK83HWCHBptNCfRJpbsYH/RvHmcycsOxgbWNo34wK0t14OEuh6wXTM4tke
j6VILzdlOriWD/paZecLhOXLe6UfIORFRU6yY1SxyPY8mQRfMibqFzKTj2vvGeqN
ZxBJ2j/pssF0UJuXbKnyASkk1UHrSh94xVYZBFXJ3lRdrifzPz3Um11ySiQqV2QR
XH2dulMMjXlThzC2v7Aa3tV8iZO6J8d0ZVcXBDc0TIbo/CejtJQ=
=dIHe
-END PGP SIGNATURE-



pgpjfz9aRqd64.pgp
Description: PGP signature
--- End Message ---

Processed: bug 1074484 is forwarded to https://github.com/hhursev/recipe-scrapers/issues/1160

[Debian Bug Tracking System]

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

> forwarded 1074484 https://github.com/hhursev/recipe-scrapers/issues/1160
Bug #1074484 [src:python-recipe-scrapers] python-recipe-scrapers: Fails to build
Set Bug forwarded-to-address to 
'https://github.com/hhursev/recipe-scrapers/issues/1160'.
> thanks
Stopping processing here.

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

Bug#960638: fixed in shadow 1:4.15.1-1

[Yalusa Jongihlati]

is this still a bug:
grave bugs of login (→ ) 
 b1 - #1074157 - non-essential login breaks runuser (Fixed: 
util-linux/2.40.1-9)

serious bugs of login (→ ) 
 b2 - #1041547 - login: I can login as root without password despite it 
being forbidden (Fixed: shadow/1:4.13+dfsg1-2)
 b3 - #960638 - login no longer needs to be essential (Fixed: 
shadow/1:4.15.2-3)


I have

# cat /etc/apt/sources.list
deb http://debian.mirror.ac.za/debian/ stable main contrib non-free 
non-free-firmware
deb http://debian.mirror.ac.za/debian/ testing main contrib non-free 
non-free-firmware
deb http://debian.mirror.ac.za/debian/ sid main contrib non-free 
non-free-firmware


yet

# apt-cache policy shadow
N: Unable to locate package shadow

On Sat, 22 Jun 2024 15:06:09 + Debian FTP Masters wrote:
> Source: shadow
> Source-Version: 1:4.15.1-1
> Done: Chris Hofstaedtler
>
> We believe that the bug you reported is fixed in the latest version of
> shadow, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 960...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Chris Hofstaedtler (supplier of updated shadow 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: Sat, 22 Jun 2024 16:08:41 +0200
> Source: shadow
> Architecture: source
> Version: 1:4.15.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Shadow package maintainers
> Changed-By: Chris Hofstaedtler
> Closes: 745796 776314 791806 812127 832047 856902 960638 1006208 
1006216 1006225 1032393 1034312 1043236 1055582 1065350

> Changes:
> shadow (1:4.15.1-1) unstable; urgency=medium
> .
> * New upstream version 4.15.1
> Closes: #832047, #812127, #1034312, #856902, #791806
> Closes: #1006216, #1006225, #1006208
> * contrib/atudel, non-DFSG-compliant was removed upstream
> * Remove obsolete configure flag --without-libcrack
> * Use functions from libbsd (Closes: #1032393)
> * Build-Depend: libltdl-dev for LT_LIB_DLLOAD
> (Closes: #1065350)
> * Build-Depend: pkgconf
> * Drop upstream applied patches
> * Disable FTMP_FILE by default, drop login failure logging
> * Rebase patch 401_cppw_src.dpatch
> * Rename patch 402_cppw_selinux
> * Use upstream FAILLOG_ENAB code, incompatible with PAM
> (Closes: #776314)
> * Rebase patch 463_login_delay_obeys_to_PAM
> * Rebase patch 501_commonio_group_shadow
> * Rebase patch 502_debian_useradd_defaults
> * Rebase patch 506_relaxed_usernames
> * Rebase patch 542_useradd-O_option
> * Update upstream signing keys

Bug#953967: marked as done (grip: autopkgtest failure with Python 3.8 as default)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 16:34:40 +
with message-id 
and subject line Bug#953967: fixed in grip 4.6.1-1
has caused the Debian Bug report #953967,
regarding grip: autopkgtest failure with Python 3.8 as default
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.)


-- 
953967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grip
Version: 4.2.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
Tags: bullseye sid
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

The autopkgtests of grip started to fail with Python 3.8 as the
default Python3 interpreter [1].

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/g/grip/unstable/amd64/


=== FAILURES ===
__ test_help ___

def test_help():
>   assert run('-h') == usage
E   AssertionError: assert 'Usage:\n  gr...e terminal.\n' ==
'Usage:\n  gri...e terminal.\n'
E Skipping 1684 identical leading characters in diff, use -v to show
Eterminal.
E - Usage:
E -   grip [options] [] []
E -   grip -V | --version
E -   grip -h | --help
E - ...
E
E ...Full output truncated (29 lines hidden), use '-vv' to show

tests/test_cli.py:46: AssertionError
_ test_version _

def test_version():
>   assert run('-V') == version + '\n'
E   AssertionError: assert 'Grip 4.2.0\nGrip 4.2.0\n' == 'Grip 4.2.0\n'
E   Grip 4.2.0
E - Grip 4.2.0

tests/test_cli.py:51: AssertionError
___ test_bad_command ___

def test_bad_command():
simple_usage = '\n\n'.join(usage.split('\n\n')[:1])
with pytest.raises(CalledProcessError) as excinfo:
run('--does-not-exist')
>   assert excinfo.value.output == simple_usage + '\n'
E   AssertionError: assert 'Usage:\n  gr...-h | --help\n' ==
'Usage:\n  gri...-h | --help\n'
E Skipping 75 identical leading characters in diff, use -v to show
E   h | --help
E - Usage:
E -   grip [options] [] []
E -   grip -V | --version
E -   grip -h | --help

tests/test_cli.py:59: AssertionError
=== warnings summary ===
grip/constants.py:32
  /tmp/autopkgtest-lxc.jd8qyf51/downtmp/build.Ocx/src/grip/constants.py:32:
DeprecationWarning: invalid escape sequence \(
'url\([\'"]?(/static/fonts/octicons/[^\'" \)]+)[\'"]?\)')

grip/constants.py:35
  /tmp/autopkgtest-lxc.jd8qyf51/downtmp/build.Ocx/src/grip/constants.py:35:
DeprecationWarning: invalid escape sequence \(
'url\([\'"]?((?:/static|{0})/[^\'" \)]+)[\'"]?\)')

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 3 failed, 2 warnings in 1.17 seconds =
autopkgtest [06:48:41]: test command1: ---]
autopkgtest [06:48:42]: test command1:  - - - - - - - - - - results -
- - - - - - - - -
command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: grip
Source-Version: 4.6.1-1
Done: Michael R. Crusoe 

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated grip 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: Sat, 29 Jun 2024 18:10:49 +0200
Source: grip
Architecture: source
Version: 4.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael R. Crusoe 
Closes: 832000 877001 953967 1023626 1023627 1025825
Changes:
 grip (4.6.1-1) unstable; urgency=medium
 .
   * d/control: Rescue this old package and move it into python-team 
maintenance.
   * d/watch: modernize
   * New 

Bug#1025825: marked as done (ImportError: cannot import name 'safe_join' from 'flask')

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 16:34:41 +
with message-id 
and subject line Bug#1025825: fixed in grip 4.6.1-1
has caused the Debian Bug report #1025825,
regarding ImportError: cannot import name 'safe_join' from 'flask'
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.)


-- 
1025825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grip
Version: 4.2.0-3
Severity: important
X-Debbugs-Cc: rockst...@gmx.com

Dear Maintainer,

Program will not even start with the following trace:

```
$ grip -b
Traceback (most recent call last):
  File "/usr/bin/grip", line 9, in 
load_entry_point('grip==4.2.0', 'console_scripts', 'grip')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 486, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2867, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2471, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2477, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/share/grip/grip/__init__.py", line 13, in 
from .api import (
  File "/usr/share/grip/grip/api.py", line 8, in 
from .app import Grip
  File "/usr/share/grip/grip/app.py", line 28, in 
from .assets import GitHubAssetManager, ReadmeAssetManager
  File "/usr/share/grip/grip/assets.py", line 16, in 
from flask import safe_join
ImportError: cannot import name 'safe_join' from 'flask' 
(/usr/lib/python3/dist-packages/flask/__init__.py)
```

Please let me know if I can help to debug any further.


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

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grip depends on:
ii  python3   3.10.6-1
ii  python3-docopt0.6.2-4
ii  python3-flask 2.2.2-2
ii  python3-markdown  3.4.1-2
ii  python3-path-and-address  2.0.1-3
ii  python3-pygments  2.13.0+dfsg-1
ii  python3-requests  2.27.1+dfsg-1

grip recommends no packages.

grip suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grip
Source-Version: 4.6.1-1
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated grip 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: Sat, 29 Jun 2024 18:10:49 +0200
Source: grip
Architecture: source
Version: 4.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael R. Crusoe 
Closes: 832000 877001 953967 1023626 1023627 1025825
Changes:
 grip (4.6.1-1) unstable; urgency=medium
 .
   * d/control: Rescue this old package and move it into python-team 
maintenance.
   * d/watch: modernize
   * New upstream version. Closes: #832000, #1025825, #953967, #1023627, 
#1023626
   * Standards-Version: 4.6.2 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)
   * Secure URI in copyright format (routine-update)
   * Drop ancient X-Python-Version field (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Remove unnecessary 'Testsuite: autopkgtest' header.
   * d/upstream/metadata: added
   * 

Bug#1074490: twython: autopkgtest failure with Python 3.12

[Yogeswaran Umasankar]

Source: twython
Version: 3.8.2+dfsg-2
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: y...@debian.org
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Dear Maintainer,

twython autopkgtests fail with Python 3.12 [0].

autopkgtest [15:06:37]: test command1: [---
/tmp/autopkgtest.Ag7o89/tree/twython/api.py:433: SyntaxWarning: invalid escape 
sequence '\*'
  """Construct a Twitter API url, encoded, with parameters
/tmp/autopkgtest.Ag7o89/tree/twython/api.py:472: SyntaxWarning: invalid escape 
sequence '\*'
  """Returns a generator for results that match a specified query.
/tmp/autopkgtest.Ag7o89/tree/twython/streaming/types.py:38: SyntaxWarning: 
invalid escape sequence '\*'
  """Stream statuses/filter
/tmp/autopkgtest.Ag7o89/tree/twython/streaming/types.py:50: SyntaxWarning: 
invalid escape sequence '\*'
  """Stream statuses/sample
/tmp/autopkgtest.Ag7o89/tree/twython/streaming/types.py:62: SyntaxWarning: 
invalid escape sequence '\*'
  """Stream statuses/firehose
/tmp/autopkgtest.Ag7o89/tree/twython/streaming/types.py:74: SyntaxWarning: 
invalid escape sequence '\*'
  """Set/update statuses/filter

[0] https://ci.debian.net/packages/t/twython/testing/arm64

Bug#1074486: wordpress: CVE-2024-6307 CVE-2024-31111 CVE-2024-32111

[Salvatore Bonaccorso]

Source: wordpress
Version: 6.5.3+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for wordpress.

CVE-2024-6307[0]:
| WordPress Core is vulnerable to Stored Cross-Site Scripting via the
| HTML API in various versions prior to 6.5.5 due to insufficient
| input sanitization and output escaping on URLs. This makes it
| possible for authenticated attackers, with contributor-level access
| and above, to inject arbitrary web scripts in pages that will
| execute whenever a user accesses an injected page.


CVE-2024-3[1]:
| Improper Neutralization of Input During Web Page Generation (XSS or
| 'Cross-site Scripting') vulnerability in Automattic WordPress allows
| Stored XSS.This issue affects WordPress: from 6.5 through 6.5.4,
| from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through
| 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9
| through 5.9.9.


CVE-2024-32111[2]:
| Improper Limitation of a Pathname to a Restricted Directory ('Path
| Traversal') vulnerability in Automattic WordPress allows Relative
| Path Traversal.This issue affects WordPress: from 6.5 through 6.5.4,
| from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through
| 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9
| through 5.9.9, from 5.8 through 5.8.9, from 5.7 through 5.7.11, from
| 5.6 through 5.6.13, from 5.5 through 5.5.14, from 5.4 through
| 5.4.15, from 5.3 through 5.3.17, from 5.2 through 5.2.20, from 5.1
| through 5.1.18, from 5.0 through 5.0.21, from 4.9 through 4.9.25,
| from 4.8 through 4.8.24, from 4.7 through 4.7.28, from 4.6 through
| 4.6.28, from 4.5 through 4.5.31, from 4.4 through 4.4.32, from 4.3
| through 4.3.33, from 4.2 through 4.2.37, from 4.1 through 4.1.40.


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-2024-6307
https://www.cve.org/CVERecord?id=CVE-2024-6307
[1] https://security-tracker.debian.org/tracker/CVE-2024-3
https://www.cve.org/CVERecord?id=CVE-2024-3
[2] https://security-tracker.debian.org/tracker/CVE-2024-32111
https://www.cve.org/CVERecord?id=CVE-2024-32111
[3] https://wordpress.org/news/2024/06/wordpress-6-5-5/

Regards,
Salvatore

Bug#1074484: python-recipe-scrapers: Fails to build

[Jeremy Bícha]

Source: python-recipe-scrapers
Version: 14.57.0-1
Severity: serious
Tags: ftbfs

The build tests for python-recipe-scrapers are failing.

build log excerpt

  File 
"/<>/.pybuild/cpython3_3.12_recipe-scrapers/build/tests/library/test_readme.py",
line 94, in get_list_lines
with open("README.rst") as f:
 ^^
FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'

full build log
=
https://buildd.debian.org/status/package.php?p=python-recipe-scrapers

Thank you,
Jeremy Bícha

Bug#1074483: dcmtk: CVE-2024-27628

[Salvatore Bonaccorso]

Source: dcmtk
Version: 3.6.7-15
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://support.dcmtk.org/redmine/issues/1108
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.6.7-9~deb12u1

Hi,

The following vulnerability was published for dcmtk.

CVE-2024-27628[0]:
| Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to
| execute arbitrary code via the EctEnhancedCT method component.


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-2024-27628
https://www.cve.org/CVERecord?id=CVE-2024-27628
[1] https://support.dcmtk.org/redmine/issues/1108
[2] 
https://github.com/DCMTK/dcmtk/commit/ec52e99e1e33fc39810560421c0833b02da567b3

Regards,
Salvatore

Processed: dcmtk: CVE-2024-27628

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.6.7-9~deb12u1
Bug #1074483 [src:dcmtk] dcmtk: CVE-2024-27628
Marked as found in versions dcmtk/3.6.7-9~deb12u1.

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

Bug#1074482: liboxygenstyleconfig5-6: missing Breaks+Replaces: liboxygenstyleconfig5-5 (<< 4:6)

[Andreas Beckmann]

Package: liboxygenstyleconfig5-6
Version: 4:6.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

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

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

  Preparing to unpack .../liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb ...
  Unpacking liboxygenstyleconfig5-6:amd64 (4:6.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/locale/ar/LC_MESSAGES/liboxygenstyleconfig.mo', which is also in 
package liboxygenstyleconfig5-5:amd64 4:5.27.11-1
  Errors were encountered while processing:
   /var/cache/apt/archives/liboxygenstyleconfig5-6_4%3a6.1.0-1_amd64.deb

The conflicting files are 
/usr/share/locale/*/LC_MESSAGES/liboxygenstyleconfig.mo


cheers,

Andreas


liboxygenstyleconfig5-5=4:5.27.11-1_liboxygenstyleconfig5-6=4:6.1.0-1.log.gz
Description: application/gzip

Processed: Re: Bug#1071860: not fixed in 7.0-005-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1071860 [src:fis-gtm] fis-gtm: Searches for libgcrypt with libgcrypt-config
Added tag(s) pending.

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

Bug#1071860: not fixed in 7.0-005-2

[Andreas Metzler]

Control: tags -1 pending

On 2024-06-23 Andreas Metzler  wrote:
[...]
> I will give it a litte bit of time to check whether somebody else from
> -med picks this up and will NMU otherwise.

Hello,

I have now uploaded a NMU to delayed/7-days using the attached patch. I
have gone for the mininal change, dropping the respective code instead
of switching to pkgconf. It simpler, does not make a difference on
Debian systems and the whole thing does not make sense to me.

cu Andreas
diff -Nru fis-gtm-7.0-005/debian/changelog fis-gtm-7.0-005/debian/changelog
--- fis-gtm-7.0-005/debian/changelog	2024-06-22 21:59:20.0 +0200
+++ fis-gtm-7.0-005/debian/changelog	2024-06-29 15:41:01.0 +0200
@@ -1,3 +1,12 @@
+fis-gtm (7.0-005-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS without libgcrypt-config by simply dropping the respective code
+on Debian. libgcrypt headers are installed to /usr/include on Debian
+Closes: #1071860
+
+ -- Andreas Metzler   Sat, 29 Jun 2024 15:41:01 +0200
+
 fis-gtm (7.0-005-2) unstable; urgency=medium
 
   * Build-Depends: s/libgcrypt20-dev | //, pkgconf
diff -Nru fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff
--- fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff	1970-01-01 01:00:00.0 +0100
+++ fis-gtm-7.0-005/debian/patches/do-not-use_libgcrypt-config.diff	2024-06-29 15:40:24.0 +0200
@@ -0,0 +1,50 @@
+Description: Drop unnecessary call to libgcrypt-config
+ libgcrypt-config has been dropped in libgcrypt 1.11, the call here is
+ unnecessary on Debian (headers in /usr/include).
+ .
+ The whole code snippet is a little bit strange since it allows searching for
+ libgcrypt headers in a standard location while requiring that the library
+ itself can be found in a standard location.
+Author: Andreas Metzler 
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/1071860
+Last-Update: 2024-06-29
+
+--- fis-gtm-7.0-005.orig/CMakeLists.txt
 fis-gtm-7.0-005/CMakeLists.txt
+@@ -523,20 +523,21 @@ add_custom_command(
+ add_custom_target(gen_tls_options
+   DEPENDS ${GTM_BINARY_DIR}/gen_tls_options.h ${GTM_BINARY_DIR}/gen_tls_verify_options.h)
+ 
+-# Locate libgcrypt's header files (assumption: all others headers are found in the same location)
+-find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
+-if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
+-	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
+-else()
+-	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
+-	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
+-	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
+-	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
+-	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
+-		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
+-		include_directories(${LIBGCRYPT_INCLUDES})
+-	endif()
+-endif()
++# Disabled - Debian's libgcrypt header are installed in standard paths.
++# # Locate libgcrypt's header files (assumption: all others headers are found in the same location)
++# find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
++# if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
++# 	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
++# else()
++# 	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
++# 	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
++# 	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
++# 	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
++# 	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
++# 		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
++# 		include_directories(${LIBGCRYPT_INCLUDES})
++# 	endif()
++# endif()
+ 
+ # Building the three encryption libraries could by a loop of some sort, but
+ # manually creating each target is way easier.
diff -Nru fis-gtm-7.0-005/debian/patches/series fis-gtm-7.0-005/debian/patches/series
--- fis-gtm-7.0-005/debian/patches/series	2024-06-22 21:59:20.0 +0200
+++ fis-gtm-7.0-005/debian/patches/series	2024-06-29 15:40:57.0 +0200
@@ -1,2 +1,3 @@
 upstream_disable_autorelink
 upstream_donot_deploy_all_encryption_libs
+do-not-use_libgcrypt-config.diff


signature.asc
Description: PGP signature

Processed: bump severity of python 3.12 autopkgtest bugs

[Debian Bug Tracking System]

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

> severity 1061795 serious
Bug #1061795 [src:csound] csound fails its autopkg tests with Python 3.12
Severity set to 'serious' from 'important'
> severity 1061824 serious
Bug #1061824 [src:python-cloudflare] python-cloudflare fails its autopkg tests 
with Python 3.12
Severity set to 'serious' from 'important'
> severity 1061833 serious
Bug #1061833 [src:pywebdav] pywebdav autopkg fails its autopkg tests with 
Python 3.12
Severity set to 'serious' from 'important'
> severity 1061836 serious
Bug #1061836 [src:recon-ng] recon-ng fails its autopkg tests with Python 3.12
Severity set to 'serious' from 'important'
> severity 1061841 serious
Bug #1061841 [src:rstcheck] rstcheck fails its autopkg tests with Python 3.12
Severity set to 'serious' from 'important'
> severity 1061842 serious
Bug #1061842 [src:sdkmanager] sdkmanager fails its autopkg tests with Python 
3.12
Severity set to 'serious' from 'important'
> severity 1069219 serious
Bug #1069219 [src:pymatgen] pymatgen ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061795
1061824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061824
1061833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061833
1061836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061836
1061841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061841
1061842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061842
1069219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1071945: netatalk: FTBFS against libgcrypt 1.11

[Maytham Alsudany]

Ping to push back autoremoval of netatalk from testing.

-- 
Maytham Alsudany
Debian Maintainer

maytham @ OFTC
maytha8 @ Libera



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

Bug#1074136: marked as done (org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331))

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 12:32:27 +
with message-id 
and subject line Bug#1074136: fixed in org-mode 9.4.0+dfsg-1+deb11u3
has caused the Debian Bug report #1074136,
regarding org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code 
(CVE-2024-39331)
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.)


-- 
1074136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: org-mode
Version: 9.6.28+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: clone -1 -2
Control: reassign -2 src:emacs 1:29.3+1-3

Hi

There is a new vulnerability in Emacs Org mode. Details:

https://www.openwall.com/lists/oss-security/2024/06/23/1

Upstream fix (in org-mode);

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: org-mode
Source-Version: 9.4.0+dfsg-1+deb11u3
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated org-mode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 25 Jun 2024 09:19:27 +0200
Source: org-mode
Architecture: source
Version: 9.4.0+dfsg-1+deb11u3
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Emacsen team 
Changed-By: Salvatore Bonaccorso 
Closes: 1074136
Changes:
 org-mode (9.4.0+dfsg-1+deb11u3) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code
 (CVE-2024-39331) (Closes: #1074136)
Checksums-Sha1:
 c8303dbd411c40d6f53b523bc7ee0d70308cb909 2163 org-mode_9.4.0+dfsg-1+deb11u3.dsc
 963394472fcc72dfaf6c95fabcf8c6f11417c6d4 1295952 
org-mode_9.4.0+dfsg.orig.tar.xz
 d83c6c231996bd68107d5d61b1929879cc13eb1c 17128 
org-mode_9.4.0+dfsg-1+deb11u3.debian.tar.xz
 6fb9a6c2b8c867f21552c343fc714656dcfc557e 7135 
org-mode_9.4.0+dfsg-1+deb11u3_source.buildinfo
Checksums-Sha256:
 ce83394d98a47d2526f812bf5bbe77f4c11e8ec10cc1eb111e9582a179e18362 2163 
org-mode_9.4.0+dfsg-1+deb11u3.dsc
 dab4a49aa502a110e239cd2eb6926ef89dd76f01b3e4589409bf80a290229357 1295952 
org-mode_9.4.0+dfsg.orig.tar.xz
 074601cf3ed8374ab8772927789d94471de52a05c9224995fc7b60fb747f4b26 17128 
org-mode_9.4.0+dfsg-1+deb11u3.debian.tar.xz
 d63e094dcb7020f5b2bffa8f6d166e3958a9fa2f6d46e549e963db09d270dc8a 7135 
org-mode_9.4.0+dfsg-1+deb11u3_source.buildinfo
Files:
 c9320ba79083d110bfc13415945e497a 2163 lisp optional 
org-mode_9.4.0+dfsg-1+deb11u3.dsc
 aae084475e3cff3d586b2dfacabbabfb 1295952 lisp optional 
org-mode_9.4.0+dfsg.orig.tar.xz
 1c56c250b9d3abab7f4405eebd1c0b5a 17128 lisp optional 
org-mode_9.4.0+dfsg-1+deb11u3.debian.tar.xz
 037394b1145a7b948ab91a53d975cf1a 7135 lisp optional 
org-mode_9.4.0+dfsg-1+deb11u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmZ6cARfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EKPwP/Arwymwmw//z7DdcvIQzUUUQzjjGOf6Y
pTmoDHVpI37ndOvDiQ+dKr0M4Om6xH97Cck3U6MGGtdVPHZOgte+0H1a63XmQpC8
6reAqCQhftQFsKuPifrzWsVw0s3SE+yllmPwm23gEohPu5RtKrYoOm3nmuB/NlPs
hchyxB7ikI8ZMHZIjULTYlAu3J0nmyyn6IcRyzZ7v/7H3CeR99FfPvql+1yOWg4A
nto4dBTyzGOROa4jCgN6GzqmOZpht2yvJVefq1g3kpvdF1f4DwV9XY43vUXWeXAn
JtWReFwyaVCkro81iOoZVSNB2Ap+Id6NWzzXs/t5xT3sbLSOH3Belnk+dvFFIeav
cEmcorJJa2Py/aPSqDJ22YLKCosT//kVk7500PfA3sL6t1nMTJg8Csgr7so7Y0cX
lK7mj3kpaZdOB+QyKG/5388xBSogd6J6ghPo4DYjcpwGtlNHcBwJ07JTPBMDA0zq
XiKimcRq57j+jr4TYK4Ovs+9GIKRcdgpmi+yeO9QdU5GPFQHJcGgdMAhk3Fm06Xb
9dqJu0bYjhENdRXWrzpYxYcOipdoMcEzAUtMdCm5cIsGz2EcEoYNeznJb7BYlioD
d9JqXUecNwjgGR7J80asX1yGCskh12VHCvOsfn4/xkR217r2msDN4D4Gh25iIEnM
D3IrhdxY0xcE
=TCon
-END PGP SIGNATURE-



pgp6HXrmbbATE.pgp
Description: PGP signature
--- End Message ---

Processed: tagging 1073455

[Debian Bug Tracking System]

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

> tags 1073455 + trixie sid
Bug #1073455 [src:openstructure] openstructure FTBFS with scipy 1.12
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1073455: [Debichem-devel] Bug#1073455: openstructure: FTBFS: TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openstructure FTBFS with scipy 1.12
Bug #1073455 [src:openstructure] openstructure: FTBFS: TypeError: unsupported 
operand type(s) for -: 'NoneType' and 'float'
Changed Bug title to 'openstructure FTBFS with scipy 1.12' from 'openstructure: 
FTBFS: TypeError: unsupported operand type(s) for -: 'NoneType' and 'float''.
> tags -1 patch
Bug #1073455 [src:openstructure] openstructure FTBFS with scipy 1.12
Added tag(s) patch.

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

Bug#1073455: [Debichem-devel] Bug#1073455: openstructure: FTBFS: TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'

[Adrian Bunk]

Control: retitle -1 openstructure FTBFS with scipy 1.12
Control: tags -1 patch

On Tue, Jun 25, 2024 at 05:29:20PM +0300, Andrius Merkys wrote:
> control: forwarded -1 openstructure-us...@maillist.unibas.ch
> 
> On 2024-06-16 16:08, Lucas Nussbaum wrote:
> > ==
> > ERROR: testSpearmanCorrel (__main__.TestTable.testSpearmanCorrel)
> > --
> > Traceback (most recent call last):
> >File "/<>/modules/base/tests/test_table.py", line 1668, in 
> > testSpearmanCorrel
> >  self.assertAlmostEqual(tab.SpearmanCorrel('second','third'), 
> > -0.316227766)
> >File "/usr/lib/python3.11/unittest/case.py", line 904, in 
> > assertAlmostEqual
> >  diff = abs(first - second)
> > ~~^~~~
> > TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'
> 
> This failure seems to have been caused by an API change in scipy. I have
> reported the issue upstream. A simple fix would be to skip this test
> entirely via a patch. In the meantime let us wait for upstream's response.

This has now been fixed upstream:
https://git.scicore.unibas.ch/schwede/openstructure/-/commit/15a499485ede152b6d432b7c91f1084e9e11bd8f

> Andrius

cu
Adrian

Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

[Leah Neukirchen]

Hi, nq maintainer here.

I propose to make a new release 1.0, where fq is renamed to nqtail,
and by default I will install a symlink fq -> nqtail.

Debian (and other distros) are free to remove this symlink.

Since fq is widely packaged now
(https://repology.org/project/fq-inspect-binary-data/versions)
I hope this will resolve the issue.

Thanks,
-- 
Leah Neukirchenhttps://leahneukirchen.org/

Processed: Re: Bug#1061601: openstructure: FTBFS with Python 3.12 as default

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3.12
Bug #1061601 [src:openstructure] openstructure: FTBFS with Python 3.12 as 
default
Bug reassigned from package 'src:openstructure' to 'python3.12'.
No longer marked as found in versions openstructure/2.5.0-1.
Ignoring request to alter fixed versions of bug #1061601 to the same values 
previously set
> affects -1 src:openstructure
Bug #1061601 [python3.12] openstructure: FTBFS with Python 3.12 as default
Added indication that 1061601 affects src:openstructure
> close -1 3.12.2-1
Bug #1061601 [python3.12] openstructure: FTBFS with Python 3.12 as default
Marked as fixed in versions python3.12/3.12.2-1.
Bug #1061601 [python3.12] openstructure: FTBFS with Python 3.12 as default
Marked Bug as done

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

Bug#1061601: openstructure: FTBFS with Python 3.12 as default

[Adrian Bunk]

Control: reassign -1 python3.12
Control: affects -1 src:openstructure
Control: close -1 3.12.2-1

On Sat, Jan 27, 2024 at 09:28:06AM +0200, Graham Inggs wrote:
> Source: openstructure
> Version: 2.5.0-1
> Severity: important
> Tags: ftbfs patch
> User: debian-pyt...@lists.debian.org
> Usertags: python3.12
> 
> Hi Maintainer
> 
> openstructure FTBFS with Python 3.12 as the default version (i.e. with
> python3-defaults/3.12.1-1 from experimental).  I've copied what I hope
> is the relevant part of the log below.
> 
> Python 3.12 now returns 5 instead of 0 when all tests in a unit test
> are skipped.  This is the case for test_sec_struct.py when
> debian/patches/skip-dssp-tests.patch is applied.
>...

This was fixed in Python 3.12.2:
https://github.com/python/cpython/issues/113661

cu
Adrian

Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd

[Patrick Franz]

Hi,

On Thu, 27 Jun 2024 11:01:44 +0900 yokota  wrote:
> Hello,
> 
> I think this bug is not a libzstd's bug but qt6-base's bug.
> 
> Please check this QTBUG.
> > [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static
> > https://bugreports.qt.io/browse/QTBUG-119469
> 
> The QTBUG said this bug was fixed in Qt 6.7.2, so update Qt to 6.7.2
> will fixes the problem.
> 
> Or, back port QTBUG-119469 fix from git commits.
> https://code.qt.io/cgit/qt/qtbase.git/log/?qt=grep=QTBUG-119469
> 
> PS:
> Arch Linux also have this bug.
> > https://gitlab.archlinux.org/archlinux/packaging/packages/qt6-doc/-/
issues/1

Backporting these commits does not solve the issue for me. Maybe I am 
doing something wrong, but I still get the error in qt6-tools.

If anybody else wants to take a crack a it, go ahead. Because I cannot 
spend any more time on this.

Short of updating Qt to 6.7.2 or completely disabling zstd support in 
Qt, I'm kinda out of options. I cannot judge the consequence of removing 
zstd support and updating Qt will take several weeks at least.


-- 
Med vänliga hälsningar

Patrick Franz

Processed: Bug#1073447 marked as pending in wtforms-json

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073447 {Done: Carsten Schoenert } 
[src:wtforms-json] wtforms-json: 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.

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

Bug#1073447: marked as done (wtforms-json: 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 Sat, 29 Jun 2024 11:26:26 +
with message-id 
and subject line Bug#1073447: fixed in wtforms-json 0.3.5-4
has caused the Debian Bug report #1073447,
regarding wtforms-json: 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.)


-- 
1073447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wtforms-json
Version: 0.3.5-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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 sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> running config
> I: pybuild base:311: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_wtforms-json/build/wtforms_json
> copying wtforms_json/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_wtforms-json/build/wtforms_json
> running egg_info
> creating WTForms_JSON.egg-info
> writing WTForms_JSON.egg-info/PKG-INFO
> writing dependency_links to WTForms_JSON.egg-info/dependency_links.txt
> writing requirements to WTForms_JSON.egg-info/requires.txt
> writing top-level names to WTForms_JSON.egg-info/top_level.txt
> writing manifest file 'WTForms_JSON.egg-info/SOURCES.txt'
> reading manifest file 'WTForms_JSON.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'tests.py'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'docs'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'docs/_themes/.git'
> adding license file 'LICENSE'
> writing manifest file 'WTForms_JSON.egg-info/SOURCES.txt'
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_wtforms-json/build/wtforms_json
> copying wtforms_json/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_wtforms-json/build/wtforms_json
> running egg_info
> writing WTForms_JSON.egg-info/PKG-INFO
> writing dependency_links to WTForms_JSON.egg-info/dependency_links.txt
> writing requirements to WTForms_JSON.egg-info/requires.txt
> writing top-level names to WTForms_JSON.egg-info/top_level.txt
> reading manifest file 'WTForms_JSON.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'tests.py'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'docs'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'docs/_themes/.git'
> adding license file 'LICENSE'
> writing manifest file 'WTForms_JSON.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd 
> /<>/.pybuild/cpython3_3.12_wtforms-json/build; python3.12 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>
> collected 37 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.12_wtforms-json/build/tests/test_wtforms_alchemy.py _
> tests/test_wtforms_alchemy.py:8: in 
> Base = declarative_base(engine)
> :2: in declarative_base
> ???
> /usr/lib/python3/dist-packages/sqlalchemy/util/deprecations.py:386: in warned
> return fn(*args, **kwargs)  # type: ignore[no-any-return]
> /usr/lib/python3/dist-packages/sqlalchemy/ext/declarative/__init__.py:27: in 
> declarative_base
> return _declarative_base(*arg, **kw)
> E   TypeError: declarative_base() takes 0 positional arguments but 1 was given
> === warnings summary 
> ===
> tests/test_wtforms_alchemy.py:8
>   
> /<>/.pybuild/cpython3_3.12_wtforms-json/build/tests/test_wtforms_alchemy.py:8:
>  MovedIn20Warning: The ``declarative_base()`` function is now available as 
> sqlalchemy.orm.declarative_base(). 

Bug#1073447: marked as pending in wtforms-json

[Carsten Schoenert]

Control: tag -1 pending

Hello,

Bug #1073447 in wtforms-json 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/wtforms-json/-/commit/0d9b129d28e16bcef447438307830ed37703ba66


Rebuild patch queue from patch-queue branch

Added patch:
upstream/tests-Fix-warning-on-deprecated-declarative_base.patch

Closes: #1073447


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073447

Processed: fixed 1065341 in 2.6.0~rc-1~exp2

[Debian Bug Tracking System]

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

> fixed 1065341 2.6.0~rc-1~exp2
Bug #1065341 {Done: Andrius Merkys } [src:openstructure] 
src:openstructure: unsatisfied build dependency in testing: sip-dev
Marked as fixed in versions openstructure/2.6.0~rc-1~exp2.
> thanks
Stopping processing here.

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

Bug#1073350: marked as done (raptor2: FTBFS: raptor_libxml.c:256:12: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no member named ‘checked’)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 11:21:54 +
with message-id 
and subject line Bug#1073350: fixed in raptor2 2.0.16-4
has caused the Debian Bug report #1073350,
regarding raptor2: FTBFS: raptor_libxml.c:256:12: error: ‘xmlEntity’ {aka 
‘struct _xmlEntity’} has no member named ‘checked’
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.)


-- 
1073350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: raptor2
Version: 2.0.16-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> -DLIBRDFA_IN_RAPTOR -I../librdfa -DRAPTOR_INTERNAL=1 -I/usr/include/libxml2  
> -Wdate-time -D_FORTIFY_SOURCE=2   -I/usr/include/libxml2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o turtle_lexer.lo turtle_lexer.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -DLIBRDFA_IN_RAPTOR -I../librdfa 
> -DRAPTOR_INTERNAL=1 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/libxml2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> raptor_libxml.c  -fPIC -DPIC -o .libs/raptor_libxml.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -DLIBRDFA_IN_RAPTOR -I../librdfa 
> -DRAPTOR_INTERNAL=1 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/libxml2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> raptor_rdfxml.c  -fPIC -DPIC -o .libs/raptor_rdfxml.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -DLIBRDFA_IN_RAPTOR -I../librdfa 
> -DRAPTOR_INTERNAL=1 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/libxml2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> turtle_lexer.c  -fPIC -DPIC -o .libs/turtle_lexer.o
> raptor_libxml.c: In function ‘raptor_libxml_getEntity’:
> raptor_libxml.c:256:12: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no 
> member named ‘checked’
>   256 | if(!ret->checked)
>   |^~
> raptor_libxml.c:257:10: error: ‘xmlEntity’ {aka ‘struct _xmlEntity’} has no 
> member named ‘checked’
>   257 |   ret->checked = 1;
>   |  ^~
> make[3]: *** [Makefile:981: raptor_libxml.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/raptor2_2.0.16-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: raptor2
Source-Version: 2.0.16-4
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated raptor2 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: Sat, 29 Jun 2024 10:43:44 +0200

Bug#1074475: CVE-2024-38441: Heap out-of-bounds write in directory.c

[Daniel Markstedt]

Package: netatalk
Version: 3.1.18~ds-1+b2
Severity: critical
Tags: patch security upstream
Justification: root security hole
X-Debbugs-Cc: Debian Security Team 

This vulnerability in Netatalk arises due to a lack of validation for the 
length field after parsing user-provided data, leading to an out-of-bounds heap 
write of one byte (\0). Under specific configurations, this can result in an 
out-of-bounds write to the metadata of the next heap block, potentially 
allowing an attacker to execute code in the root context.

The upstream project has issued a patch and fixed version 3.2.1:

https://netatalk.io/security/CVE-2024-38441
https://github.com/Netatalk/netatalk/commit/77b5d99007cfef4d73d76fd6f0c26584891608e5.diff
https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-2-1

Bug#1074474: CVE-2024-38440: Heap out-of-bounds write in uams_dhx_pam.c

[Daniel Markstedt]

Package: netatalk
Version: 3.1.18~ds-1+b2
Severity: critical
Tags: patch security upstream
Justification: root security hole
X-Debbugs-Cc: Debian Security Team 

This vulnerability in Netatalk arises due to a lack of validation for the 
length field after parsing user-provided data, leading to an out-of-bounds heap 
write of one byte (\0). Under specific configurations, this can result in 
reading metadata of the next heap block, potentially causing a Denial of 
Service (DoS) under certain heap layouts or with ASAN enabled.

The upstream project has issued a patch and fixed version 3.2.1:

https://netatalk.io/security/CVE-2024-38440
https://github.com/Netatalk/netatalk/commit/77b5d99007cfef4d73d76fd6f0c26584891608e5.diff
https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-2-1

Bug#1071932: marked as done (libbdplus: FTBFS against libgcrypt 1.11)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 10:56:10 +
with message-id 
and subject line Bug#1071932: fixed in libbdplus 0.2.0-4
has caused the Debian Bug report #1071932,
regarding libbdplus: FTBFS against libgcrypt 1.11
to be marked as done.

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

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


-- 
1071932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbdplus
Version: 0.2.0-3
Severity: important
Tags: ftbfs
User: ametz...@debian.org
Usertags: libgcrypt-config-removal
Control: block 714589 by -1

Hello,

libbdplus uses libgcrypt-config to locate libgcrypt. This breaks
against libgcrypt 1.11 which does not ship libgcrypt-config anymore.
Please use pkg-config/pkgconf instead.

A development snapshot of the yet-unreleased libgcrypt 1.11 is available
in experimental.

cu Andreas
--- End Message ---
--- Begin Message ---
Source: libbdplus
Source-Version: 0.2.0-4
Done: Dylan Aïssi 

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated libbdplus 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: Sat, 29 Jun 2024 10:13:06 +0200
Source: libbdplus
Architecture: source
Version: 0.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dylan Aïssi 
Closes: 1071932
Changes:
 libbdplus (0.2.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Rely on pkgconf to detect libgcrypt instead of libgcrypt-config
   (Closes: #1071932)
   * Switch to pkgconf in Build-Deps
   * Standards-Version: 4.7.0 (no changes required)
Checksums-Sha1:
 92e2b4fdb318501a2217e4cfe594063eb62ad8ee 2076 libbdplus_0.2.0-4.dsc
 c29f65d764c50098e52857acafb019eb9ec5d392 3916 libbdplus_0.2.0-4.debian.tar.xz
 3103d907bb4c82553ea7bc52c1666c62ac6d7dcc 6458 libbdplus_0.2.0-4_amd64.buildinfo
Checksums-Sha256:
 1640d16319d2e271c748663d1352e8e6421f4e25dab8be6bb468ea634c88e209 2076 
libbdplus_0.2.0-4.dsc
 23ee4ebdaeb6a4992b8a48d75cc6aea81317e7615eeead2d38ad3c4736ca2134 3916 
libbdplus_0.2.0-4.debian.tar.xz
 2c51277923f712d16f0a26d60f9a357463acecdc26cd3105fc29008a9a2d049a 6458 
libbdplus_0.2.0-4_amd64.buildinfo
Files:
 4cd7aac26898c933e66ffd4f916c3de9 2076 libs optional libbdplus_0.2.0-4.dsc
 9a83b07f9abb2976efc7e9d23d381223 3916 libs optional 
libbdplus_0.2.0-4.debian.tar.xz
 712e96c1becd34c84526e2f6da889076 6458 libs optional 
libbdplus_0.2.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmZ/wz4ACgkQYS7xYT4F
D1TYfQ//QNddJXNLjPysUiu9PC/H/lYUYy7kz+IVz46wPTKPd18lFYJ0df+YEunE
WJBDgIxWkxWLZocqldEVCXDIGU6cCAInjoZbNDwzKWRTkfjmQIMAtF2E8shXfEGz
Y+6/msoCnYnq6bXIvTOlyrwnGWlirU+/e82SOgIHL97rPE5sJR3E34ZxVOKw5RLi
eKLJ1Pxocbqx65agpbRZKgfPmBwlZ760GGz1cQp815xYPkpo2Cy+glZO0Et6eCKt
DBHZ/+26iAENrBLOhN6kHk1OoQkbdR4q2WL7yVlL7FVSLegzUUMxLTmQUIy1XJdv
BKmeatVGLccaeCjcyt7YXTTVLDSyH/HhQt4n8qB655moJX0FnhICgXZB95pbtkxq
9HeaW33ZjTJdzZ/CnAQb6vrlOatHYxZNFJcI9SVkomsFphUPSMJaUgyplPq8EMop
c9Me50HJvT4sJWf9yubhXyAKtJ/9UBbjsbH9Hmp/ci8sBhboL0crAkM/EvrfnbBe
R/jSDnM/3sQrwZ3TUQHoklTM3zJkh/z+WSTfaX5MAbrgU4Bd2DvhCwRAC7LIUYiF
jRue07w96rwpxUVwxOvWkGm7hopAWBOIpFuW/Al+VRejKBe19rAg7VEJjjNM4Eed
QvTZF72t0B3NoSdU22mHALpnKZlMzgVTs4HSNFpZ7Pu9pwj6cEw=
=Ifro
-END PGP SIGNATURE-



pgp8UXfIid90I.pgp
Description: PGP signature
--- End Message ---

Bug#1071931: marked as done (libaacs: FTBFS against libgcrypt 1.11)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 10:56:02 +
with message-id 
and subject line Bug#1071931: fixed in libaacs 0.11.1-4
has caused the Debian Bug report #1071931,
regarding libaacs: FTBFS against libgcrypt 1.11
to be marked as done.

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

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


-- 
1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaacs
Version: 0.5.0-2
Severity: important
Tags: ftbfs patch
User: ametz...@debian.org
Usertags: libgcrypt-config-removal
Control: block 714589 by -1

Hello,

libaacs FTBFS against libgcrypt 1.11 which drops libgcrypt-config.
Since it ships an outdated version of AM_PATH_LIBGCRYPT() in
m4/libgcrypt.m4 that cannot handle this autoreconf does not help.

Simply removing this copy (m4/libgcrypt.m4) lets the build succeed.

A development snapshot of the yet-unreleased libgcrypt 1.11 is available
in experimental.

cu Andreas
--- End Message ---
--- Begin Message ---
Source: libaacs
Source-Version: 0.11.1-4
Done: Dylan Aïssi 

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated libaacs 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: Sat, 29 Jun 2024 08:49:50 +0200
Source: libaacs
Architecture: source
Version: 0.11.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dylan Aïssi 
Closes: 1071931
Changes:
 libaacs (0.11.1-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Christoph Anton Mitterer ]
   * Update debian/copyright
 .
   [ Dylan Aïssi ]
   * Remove m4/libgcrypt.m4 which ships an outdated version of
 AM_PATH_LIBGCRYPT() (Closes: #1071931)
   * Remove unneeded debian/salsa-ci.yml
   * Standards-Version: 4.7.0 (no changes required)
Checksums-Sha1:
 1c2cff3f0a57491920133957cba36b7ec8f607e8 2105 libaacs_0.11.1-4.dsc
 4e0cbb2beba96d425df9264b265904219c97731f 4872 libaacs_0.11.1-4.debian.tar.xz
 bf972906a54506505b5d7b5c9323f4472fc4f02f 6910 libaacs_0.11.1-4_amd64.buildinfo
Checksums-Sha256:
 1a7ac1341d0bbcf1395351fdd591fc9241e709dd7dee23cad8a21f08e6075b6d 2105 
libaacs_0.11.1-4.dsc
 21bf79323d31af8adf2dbb4aeffad8ae7dd8a4a88af374c256a498df885f2715 4872 
libaacs_0.11.1-4.debian.tar.xz
 3846780c934118b7f237154e5a0f1b44ebee865fcef6ed3ddf9e30ea85d1a3b7 6910 
libaacs_0.11.1-4_amd64.buildinfo
Files:
 fde8fff2ccc2c33d004458f87444f54a 2105 video optional libaacs_0.11.1-4.dsc
 bd3832657a43a5098b80f1a205f7373f 4872 video optional 
libaacs_0.11.1-4.debian.tar.xz
 944f716cf80ef0cbe8c4199d2907a7f5 6910 video optional 
libaacs_0.11.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmZ/s8YACgkQYS7xYT4F
D1S20BAAiR2hVT/zq+08SPiFX153UZSC2Gk/pZ5s2e8EwdcMeV+QzGDJCN8go20E
Di7+//0WnEQ0jCwH1vqF87bW7NTsJQx/LaYsold3ipuolHbEd9igqYae8+sWnMEl
QzxZGCBvY508y51yp4VAXk1Q3dMgICHeu4yWuiFei1um8/5+Qfg+ECcrQfJ3hT9I
jNzNM+NwCMgEg3QCimZfq8QTBY5kNhDZCjEdZgIkqKPnjUjeVs6lju6ECQlOD19O
hpP/RjBcfk8tF6G3BL1jv/jCyctWuieXyeghghxS3B8fUyzTSfwihznBtXnQHOEj
8jE1naNkZLoQr2i+pAdXWD/sotUvqcLI7yiojKAgqwaJLO5F2Tdythb4KSH4WFng
dP2ziLACzTQqAuRBclEe/iwkqPuKntzxWVsJUpuO/pkO71CiWxscCjjT8aplkqoA
w8fjA3uEWrggsqqoyyrlJZ00GvOUtoLqDqHm5Q1/mnAWIW/6sPIAqGdT9xygYO61
5dHOGmRvsmznElQXR2VRN9cz/cB7JSKBK2toR7bIhrMlJd0FuAYnNW95RU5QzWVo
6QV2MmJDyCtp7/SbsrjLemr3y6+KfCXp4g0/dgs9ApVFHsJNeglLwHtpWEUqxnqU
JGP+o9UaGIb6wFM0zSP3N5B31Gm1TdBgAlwEYKQ6GjaaHk22e/4=
=W3tI
-END PGP SIGNATURE-



pgp5b8fnUzW76.pgp
Description: PGP signature
--- End Message ---

Bug#1074473: CVE-2024-38439: Heap out-of-bounds write in uams_pam.c

[Daniel Markstedt]

Package: netatalk
Version: 3.1.18~ds-1+b2
Severity: critical
Tags: security upstream patch
Justification: root security hole
X-Debbugs-Cc: Debian Security Team 

This vulnerability in Netatalk arises due to a lack of validation for the 
length field after parsing user-provided data, leading to an out-of-bounds heap 
write of one byte (\0). Under specific configurations, this can result in an 
out-of-bounds write to the metadata of the next heap block, potentially 
allowing an attacker to execute code in the root context.

The upstream project has issued a patch and fixed version 3.2.1:

https://netatalk.io/security/CVE-2024-38439
https://github.com/Netatalk/netatalk/commit/77b5d99007cfef4d73d76fd6f0c26584891608e5.diff
https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-2-1

Processed: Re: Bug#1072816: sploitscan: Configuration files installed in Python modules directory

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1072816 {Done: Josenilson Ferreira da Silva } 
[sploitscan] sploitscan: Configuration files installed in Python modules 
directory
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sploitscan/0.9.1-3.

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

Bug#1072816: sploitscan: Configuration files installed in Python modules directory

[Peter Wienemann]

Control: reopen -1

On 2024-06-08 12:44:25, Peter Wienemann wrote:

sploitscan installs configuration files in the system Python modules
directory:

/usr/lib/python3/dist-packages/sploitscan/templates/report_template.html
/usr/lib/python3/dist-packages/sploitscan/config.json

As per Debian Policy 10.7.2 configuration files must reside in /etc (or
in case of multiple configuration files it is suggested to put them in
a subdirectory named after the package).


Dear Maintainer,

in my opinion version 0.9.1-3 does not provide a proper fix for the 
above issue. Now the situation looks like this:


/usr/lib/python3/dist-packages/sploitscan/templates/report_template.html 
-> ../../../../../share/doc/sploitscan/templates/report_template.html


/usr/lib/python3/dist-packages/sploitscan/config.json -> 
/etc/sploitscan/config.json


From my point of view moving the report template (report_template.html) 
to the documentation directory (/usr/share/doc/sploitscan) is 
inappropriate. Putting example configuration files under 
/usr/share/doc/sploitscan is fine but putting a file that controls the 
behavior of the program under /usr/share/doc/sploitscan violates Debian 
Policy. I think this file is a configuration file in the sense of Debian 
Policy 10.7.1 rather than documentation and therefore must go into /etc 
or a subdirectory thereof. It seems that upstream has even arranged to 
put this file into this location [0].


I also noticed that local changes in report_template.html are not 
preserved on package upgrades as required by Debian Policy 10.7.3.


In addition I found two minor issues:

1. Looking at the sploitscan code [1], I suppose that the link

/usr/lib/python3/dist-packages/sploitscan/config.json -> 
/etc/sploitscan/config.json


is not necessary (although I have not tested this).

2. The changelog entry closing this bug

--
debian/sploitscan.install: Files moved to usr/share (Closes: #1072816)
--

and the corresponding commit message [2] do not properly describe the 
actual change being performed. The change includes moving only a single 
file to usr/share, it moves another file to etc/sploitscan and in 
addition it removes the installation of yet another file.


Best regards,

Peter

[0] 
https://salsa.debian.org/pkg-security-team/sploitscan/-/blob/605deb3647c2c43315e0cd6e83f447bd7fab35c2/sploitscan/sploitscan.py#L620


[1] 
https://salsa.debian.org/pkg-security-team/sploitscan/-/blob/605deb3647c2c43315e0cd6e83f447bd7fab35c2/sploitscan/sploitscan.py#L412


[2] 
https://salsa.debian.org/pkg-security-team/sploitscan/-/commit/ce316a01edd1bb6449424d3ad0227a59e07a7528

Bug#1073828: libuim-data update fails due to undefined symbol

[Dmitry Shachnev]

Control: tags -1 + pending

On Fri, Jun 28, 2024 at 06:52:35PM +0200, Andreas Metzler wrote:
> Hello,
> 
> The latest iteration of 
> https://salsa.debian.org/debian/uim/-/merge_requests/15#note_501667
> is intended to fix this.

And I have just uploaded it to DELAYED/2.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: Bug#1073828: libuim-data update fails due to undefined symbol

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1073828 [libuim-data] libuim-data update fails due to undefined symbol
Added tag(s) pending.

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

Processed: Bug#1073448 marked as pending in mayavi2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073448 [src:mayavi2] mayavi2: FTBFS: TypeError: unsupported operand 
type(s) for -: 'str' and 'str'
Added tag(s) pending.

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

Bug#1073448: marked as pending in mayavi2

[Francesco Ballarin]

Control: tag -1 pending

Hello,

Bug #1073448 in mayavi2 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/mayavi2/-/commit/90e934bade793929423d3363c7fef31e41c3dcf5


Fix FTBS by adding 681e29acb678f49037df38f4c86fa767203a.patch.
Closes: #1073448


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073448

Bug#1071118: openjdk-11: Missing builds on armel and armhf

[Matthias Klose]

Build the current openjdk-11 package on an older distribution, then use 
that one to build it in unstable.

Bug#1055043: Porting carnivore to Python 3

[Taavi Väänänen]

Trying to run the Carnivore data collection script locally crashes for 
me at the moment, this seems to be a result from commit 0d01c4f5 which 
switches it and many other QA tools from Python 2 to Python 3. I sent 
 to fix those 
crashes, please review as I don't have direct commit access on that repo.


thanks,
Taavi


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: severity of 1061424 is serious

[Debian Bug Tracking System]

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

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

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

Bug#1071932: marked as pending in libbdplus

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #1071932 in libbdplus 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/multimedia-team/libbdplus/-/commit/3bbadbfc307493456041d70eca88f8ee5f542163


Rely on pkgconf to detect libgcrypt instead of libgcrypt-config (Closes: 
#1071932)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071932

Processed: Bug#1071932 marked as pending in libbdplus

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071932 [src:libbdplus] libbdplus: FTBFS against libgcrypt 1.11
Added tag(s) pending.

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

Bug#1072056: marked as done (texlive-bin: Migration blocker)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 09:55:56 +0200
with message-id 
and subject line Re: Bug#1072056: texlive-bin: Migration blocker
has caused the Debian Bug report #1072056,
regarding texlive-bin: Migration blocker
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.)


-- 
1072056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texlive-bin
Version: 2024.20240313.70630+ds-2
Severity: grave
Justification: renders package unusable

Should not migrate to testing for now.

H.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.28+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)


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

On 27.05.2024 23:09, Hilmar Preusse wrote:


Should not migrate to testing for now.



Macht hoch die Tür', die Tor' macht weit: Let's migrate TL 2024 to testing.

Hilmar
--
sigfault



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

Bug#1074391: More information

[Bastien Roucariès]

control: severity -1 important
control: retitle -1 should be split between arch and arch:all 

Thanks to Yadd partially solved.

However this package should be split between arch and arch:all part

Bastien

> On 6/28/24 01:04, Bastien Roucariès wrote:
> > Hi,
> > 
> > I get this backtrace (yadd could you get a glimpse)
> > 
> > Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'esbuild' imported from 
> > assemblyscript/assemblyscript/scripts/build.js
> > Did you mean to import 
> > "file:///usr/lib/x86_64-linux-gnu/nodejs/esbuild/lib/main.js"?
> >  at packageResolve (node:internal/modules/esm/resolve:854:9)
> >  at moduleResolve (node:internal/modules/esm/resolve:927:18)
> >  at defaultResolve (node:internal/modules/esm/resolve:1157:11)
> >  at ModuleLoader.defaultResolve 
> > (node:internal/modules/esm/loader:383:12)
> >  at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
> >  at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
> >  at ModuleWrap. (node:internal/modules/esm/module_job:87:39)
> >  at link (node:internal/modules/esm/module_job:86:36) {
> >code: 'ERR_MODULE_NOT_FOUND'
> > 
> > In all the case maybe this package could be split between arch/not arch part
> 
> Hi,
> 
> maybe a `pkgjs-ln esbuild` could fix this
> 



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

Processed: Re: More information

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1074391 [esbuild] esbuild: build esbuild main.js
Severity set to 'important' from 'serious'
> retitle -1 should be split between arch and arch:all
Bug #1074391 [esbuild] esbuild: build esbuild main.js
Changed Bug title to 'should be split between arch and arch:all' from 'esbuild: 
build esbuild main.js'.

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

Bug#1072652: marked as done (context-modules: Migration blocker)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 09:11:56 +0200
with message-id <07b84a17-9e48-4f86-80cd-4bd7eebbf...@web.de>
and subject line Re: Bug#1072652: context-modules: Migration blocker
has caused the Debian Bug report #1072652,
regarding context-modules: Migration blocker
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.)


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

Package should not migrate to testing for now.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.31+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)


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

On 05.06.2024 22:23, Hilmar Preusse wrote:


Package should not migrate to testing for now.



Macht hoch die Tür', die Tor' macht weit: Let's migrate TL 2024 to testing.

Hilmar
--
sigfault



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

Bug#1072651: marked as done (context: Migration blocker)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 09:11:00 +0200
with message-id 
and subject line Re: Bug#1072651: context: Migration blocker
has caused the Debian Bug report #1072651,
regarding context: Migration blocker
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.)


-- 
1072651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: context
Version: 2024.04.01.20240428+dfsg-2
Severity: grave
Justification: renders package unusable

Package should not migrate to testing for now.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.31+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)


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

On 05.06.2024 22:21, Hilmar Preusse wrote:


Package should not migrate to testing for now.



Macht hoch die Tür', die Tor' macht weit: Let's migrate TL 2024 to testing.

Hilmar
--
sigfault



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

Bug#1072055: marked as done (texlive-base: Migration blocker)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 09:09:17 +0200
with message-id <87af07ec-2cec-48bf-8583-0745d1303...@web.de>
and subject line Re: Bug#1072055: texlive-base: Migration blocker
has caused the Debian Bug report #1072055,
regarding texlive-base: Migration blocker
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.)


-- 
1072055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texlive-base
Version: 2024.20240401-2
Severity: grave
Justification: renders package unusable

Should not migrate to testing for now.

H.

-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

lrwxrwxrwx 1 root root 31 Apr  9  2023 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Mar 17 22:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Apr  9  2023 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Apr  9  2023 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2738 Mar 17 22:45 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Apr  1  2019 mktex.cnf
-rw-r--r-- 1 root root 475 Mar 17 22:43 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.28+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.4

Versions of packages texlive-base is related to:
ii  tex-common6.18
ii  texlive-binaries  2022.20220321.62855-5.1+deb12u1


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

On 27.05.2024 23:06, Hilmar Preusse wrote:


Should not migrate to testing for now.



Macht hoch die Tür', die Tor' macht weit: Let's migrate TL 2024 to testing.

Hilmar
--
--
sigfault



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

Bug#1072054: marked as done (biber: Migration blocker)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 09:08:15 +0200
with message-id 
and subject line Re: Bug#1072054: biber: Migration blocker
has caused the Debian Bug report #1072054,
regarding biber: Migration blocker
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.)


-- 
1072054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biber
Version: 2.20-2
Severity: grave

biber should not migrate to testing for now.

H.
-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.28+rpt-rpi-v8 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)


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

On 27.05.2024 23:01, Hilmar Preusse wrote:


biber should not migrate to testing for now.



Macht hoch die Tür', die Tor' macht weit: Let's migrate TL 2024 to testing.

Hilmar
--
sigfault



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

Bug#1070476: marked as done (openjdk-21: autopkgtest on i386: /usr/bin/ld: /usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: undefined reference to `_SafeFetch32_impl')

[Debian Bug Tracking System]

Your message dated Sat, 29 Jun 2024 06:57:09 +
with message-id 
and subject line Bug#1070476: fixed in openjdk-21 21.0.4~6ea-1
has caused the Debian Bug report #1070476,
regarding openjdk-21: autopkgtest on i386: /usr/bin/ld: 
/usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: undefined reference to 
`_SafeFetch32_impl'
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.)


-- 
1070476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-21
Version: 21.0.3+9-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

openjdk-21 is unable to migrate since the version in unstable fails its
autopkgtests on i386.

https://ci.debian.net/packages/o/openjdk-21/testing/i386/46308616/#S21

9507s autopkgtest [09:27:46]: test jni-link.sh: [---
9507s /usr/lib/jvm/java-21-openjdk-i386/lib/server
9507s /usr/bin/ld: /usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: 
undefined reference to `_SafeFetch32_impl'
9507s collect2: error: ld returned 1 exit status
9508s autopkgtest [09:27:47]: test jni-link.sh: ---]


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: openjdk-21
Source-Version: 21.0.4~6ea-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-21 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: Sat, 29 Jun 2024 07:21:02 +0200
Source: openjdk-21
Architecture: source
Version: 21.0.4~6ea-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Closes: 1070476
Changes:
 openjdk-21 (21.0.4~6ea-1) unstable; urgency=medium
 .
   * OpenJDK 21.0.4, build 6 (early access).
 .
   [ Matthias Klose ]
   * Build using GCC 10 for focal.
 .
   [ Vladimir Petko ]
   * Update patches for the snapshot build.
   * d/p/jdk-8331541.patch: Add fix for the link failure against libjvm.so
 on i386. Closes: #1070476.
Checksums-Sha1:
 465fd664432289a26f4a53e459c025be36134c11 5280 openjdk-21_21.0.4~6ea-1.dsc
 f232dd6908a864f8c741aabb11e942ea0028fed1 616784 
openjdk-21_21.0.4~6ea.orig-googletest.tar.xz
 5d8816c69ebd84a37ba96b1eaab9a5e587e5c06a 66359892 
openjdk-21_21.0.4~6ea.orig.tar.xz
 03705bde9009b0632db65a73cff9f585d6892128 211216 
openjdk-21_21.0.4~6ea-1.debian.tar.xz
 e542883a60944039be6b706101e36a637173dc7f 11544 
openjdk-21_21.0.4~6ea-1_source.buildinfo
Checksums-Sha256:
 fa18d464c1db90e5e4fcf2beb501795e3eff4afe0139b4da641589b26057de59 5280 
openjdk-21_21.0.4~6ea-1.dsc
 65165bc0ee3e518916f7374f71c4bce6071090f5c5bcd665fa5aea23cd73131d 616784 
openjdk-21_21.0.4~6ea.orig-googletest.tar.xz
 3c062b2e54b2837f2fe1530ec0dbfdfb63bd381b58aeaab82bbb19c4ae601ec2 66359892 
openjdk-21_21.0.4~6ea.orig.tar.xz
 2a8f5db4da327f0362f74525089aa461dc266b14f1d694239a6627cd941888f3 211216 
openjdk-21_21.0.4~6ea-1.debian.tar.xz
 48831b60e1c7e064ea16e815c9110ff2c222f7b0a8aa1452b8d7d6c6e8d90016 11544 
openjdk-21_21.0.4~6ea-1_source.buildinfo
Files:
 321e87db2f183bbccacb52a7273b5c83 5280 java optional openjdk-21_21.0.4~6ea-1.dsc
 b685050366e61b66f7693c8a883c182b 616784 java optional 
openjdk-21_21.0.4~6ea.orig-googletest.tar.xz
 079d86ae20a95a8167004bc62a502f5b 66359892 java optional 
openjdk-21_21.0.4~6ea.orig.tar.xz
 107724b760144e7a95bed0477b5b707b 211216 java optional 
openjdk-21_21.0.4~6ea-1.debian.tar.xz
 8d2106aed8445ace588ebb576b8db889 11544 java optional 
openjdk-21_21.0.4~6ea-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmZ/n58QHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9VcID/9ZQlt2iwJRgpg1slxiOdedXGX7OTexpPcy
5ZcV+v1W7jbxgJciDgtJfaTt3lVQQZTQWjO5+B3hPFxT4vdfwSzN2XnKcOZabHgs
aW7LlvhPe2qATTFZsKqQQ4BpbAji2WQ/l/uyrx98QNJDibWdB5xlgV8kqk8Kvb4s
IxFW4dysCWCQermGZaifjeOxdOqWs8A9U9NBztE5aGKEWIc/wAaLh57OY8uuwPV3
P6u4iUFrffI2zytpbSuZHQggqETZyGvMf45bDkXm8WPTuFf+SAASdK+LiHBEpoxq

Processed: Bug#1071931 marked as pending in libaacs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071931 [src:libaacs] libaacs: FTBFS against libgcrypt 1.11
Added tag(s) pending.

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

Bug#1071931: marked as pending in libaacs

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #1071931 in libaacs 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/multimedia-team/libaacs/-/commit/87e3cd8aeaa165624d531b2789f9fd9e5d9c01f5


Remove m4/libgcrypt.m4 which ships an outdated version of AM_PATH_LIBGCRYPT() 
(Closes: #1071931)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071931