Bug#1076036: python3-setuptools: uninstallable in unstable

[Julian Gilbey]

On Tue, Jul 09, 2024 at 07:57:42PM +0100, Colin Watson wrote:
> Package: python3-setuptools
> Version: 68.1.2-2
> Severity: grave
> Justification: renders package unusable
> 
> Following
> https://tracker.debian.org/news/1543129/accepted-python3-stdlib-extensions-3124-1-source-into-unstable/,
> python3-setuptools is uninstallable in unstable:
> 
>   # apt install python3-setuptools
>   Some packages could not be installed. This may mean that you have
>   requested an impossible situation or if you are using the unstable
>   distribution that some required packages have not yet been created
>   or been moved out of Incoming.
>   The following information may help to resolve the situation:
>   
>   Unsatisfied dependencies:
>python3-setuptools : Depends: python3-distutils but it is not installable
>   Error: Unable to correct problems, you have held broken packages.
>   # apt install python3-setuptools python3-distutils
>   Package python3-distutils is not available, but is referred to by another 
> package.
>   This may mean that the package is missing, has been obsoleted, or
>   is only available from another source
>   
>   Error: Package 'python3-distutils' has no installation candidate
> 
> This obviously seems likely to break builds of a large number of other
> packages - we noticed it in debusine's reprotest CI jobs.

And note that this is separate from #1056198 about the
build-dependencies; this bug is caused because of the dependency on
python3-distutils which is no longer in unstable.

Best wishes,

   Julian

Bug#1051567: marked as done (cubicsdr: FTBFS with RtAudio 6)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jul 2024 05:18:55 +
with message-id 
and subject line Bug#1051567: fixed in cubicsdr 0.2.7+dfsg-4
has caused the Debian Bug report #1051567,
regarding cubicsdr: FTBFS with RtAudio 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.)


-- 
1051567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cubicsdr
Version: 0.2.7+dfsg-2
Severity: important
Tags: ftbfs patch

Dear Maintainer,

cubicsdr ftbfs with RtAudio6 (currently found in experimental)

```
/<>/src/audio/AudioThread.cpp: In member function ‘void 
AudioThread::setupDevice(int)’:
/<>/src/audio/AudioThread.cpp:435:12: error: ‘RtAudioError’ does 
not name a type; did you mean ‘RtAudioErrorType’?
  435 | catch (RtAudioError& e) {
  |^~~~
  |RtAudioErrorType
/<>/src/audio/AudioThread.cpp:436:9: error: ‘e’ was not declared 
in this scope
  436 | e.printMessage();
  | ^
/<>/src/audio/AudioThread.cpp: In member function ‘virtual void 
AudioThread::run()’:
/<>/src/audio/AudioThread.cpp:539:16: error: ‘RtAudioError’ does 
not name a type; did you mean ‘RtAudioErrorType’?
  539 | catch (RtAudioError& e) {
  |^~~~
  |RtAudioErrorType
/<>/src/audio/AudioThread.cpp:540:13: error: ‘e’ was not declared 
in this scope
  540 | e.printMessage();
  | ^
make[3]: *** [CMakeFiles/CubicSDR.dir/build.make:485: 
CMakeFiles/CubicSDR.dir/src/audio/AudioThread.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
```

Attached you find a patch that fixes the FTBFS (but is otherwise untested, so
use with care).
No debdiff this time, sorry

cheers
Description: Fix FTBFS with RtAudio 6
 Replace try/catch with checking for return codes
Author: IOhannes m zmölnig
Origin: Debian
Forwarded: no
Last-Update: 2023-09-09
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: cubicsdr-0.2.7+dfsg/src/audio/AudioThread.cpp
===
--- cubicsdr-0.2.7+dfsg.orig/src/audio/AudioThread.cpp
+++ cubicsdr-0.2.7+dfsg/src/audio/AudioThread.cpp
@@ -7,6 +7,7 @@
 #include "CubicSDR.h"
 #include "DemodulatorInstance.h"
 #include 
+#include 
 
 //50 ms
 #define HEARTBEAT_CHECK_PERIOD_MICROS (50 * 1000) 
@@ -378,7 +379,6 @@ void AudioThread::setupDevice(int device
 
 opts.streamName = "CubicSDR Audio Output";
 
-try {
 if (deviceController.find(outputDevice.load()) != 
deviceController.end()) {
 //'this' is not the controller, so remove it from the bounded list:
 //beware, we must take the controller mutex, because the audio 
callback may use the list of bounded
@@ -418,8 +418,14 @@ void AudioThread::setupDevice(int device
 else if (deviceController[parameters.deviceId] == this) {
 
 //Attach callback
-dac.openStream(, nullptr, RTAUDIO_FLOAT32, sampleRate, 
, , (void *)this, );
-dac.startStream();
+   if(dac.openStream(, nullptr, RTAUDIO_FLOAT32, 
sampleRate, , , (void *)this, )) {
+   std::cerr << dac.getErrorText() << std::endl;
+   return;
+   }
+if(dac.startStream()) {
+   std::cerr << dac.getErrorText() << std::endl;
+   return;
+   }
 }
 else {
 //we are a bound thread, add ourselves to the controller 
deviceController[parameters.deviceId].
@@ -431,11 +437,6 @@ void AudioThread::setupDevice(int device
 }
 active = true;
 
-}
-catch (RtAudioError& e) {
-e.printMessage();
-return;
-}
 if (deviceId != -1) {
 outputDevice = deviceId;
 }
@@ -530,15 +531,12 @@ void AudioThread::run() {
 }
 else {
 // 'this' is a controller thread:
-try {
 if (dac.isStreamOpen()) {
-dac.stopStream(); 
+if(dac.stopStream()) {
+   std::cerr << dac.getErrorText() << std::endl;
+   }
 }
 dac.closeStream();
-}
-catch (RtAudioError& e) {
-e.printMessage();
-}
 }
 
 //std::cout << "Audio thread done." << std::endl;
--- End Message ---
--- Begin Message ---
Source: cubicsdr
Source-Version: 0.2.7+dfsg-4
Done: tony mancill 

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

A 

Processed: Bug#1051567 marked as pending in cubicsdr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051567 [src:cubicsdr] cubicsdr: FTBFS with RtAudio 6
Added tag(s) pending.

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

Bug#1051567: marked as pending in cubicsdr

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1051567 in cubicsdr 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-hamradio-team/cubicsdr/-/commit/8ff5b083e721a7549d24367a677490b8c739848a


Fix FTBFS with RtAudio 6 (Closes: #1051567)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051567

Bug#1076057: marked as done (librust-wayland-sys-dev: impossible to install: depends on librust-memoffset-0.6+default-dev)

[Debian Bug Tracking System]

Your message dated Wed, 10 Jul 2024 02:42:39 +
with message-id 
and subject line Bug#1076057: fixed in rust-wayland-sys 0.31.3-1
has caused the Debian Bug report #1076057,
regarding librust-wayland-sys-dev: impossible to install: depends on 
librust-memoffset-0.6+default-dev
to be marked as done.

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

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


-- 
1076057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-wayland-sys-dev
Version: 0.31.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package is impossible to install, as it depends on missing
package librust-memoffset-0.6+default-dev.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmaNxgwACgkQLHwxRsGg
ASEQGw/8CVdzUuAYefO21HpPt5iNC/vBNtcq6YdsJh1wxAIt3p2lvlXjpXznTMfW
XJfBLH3okJZuT+znDZn4l8JyJiyOmSA5/KvGvcrGe9g469UJgLfgvqrUTaTL6by7
iDMRxLJhsXoBIhOAGiyn1V/2eLongzQXu2H1rdME+cZUOsVoqOvChDdpM5ZtgK0w
LGwimffsaO+ZH3yPuXEec2FqRB0vApIleQM2dyRCXqhTZMyFENoDUyHUhpN/UrBk
7l4OEobqAiYMd3v1A2WxENgvD4Dz4gLlfOcZFxfNlD7CphWKo045qzHXvjsVPOJo
Jvr/8a+Okgn++40wD5TAx9MbiRuXD4EknLZmONakwbbBEzD0FhA/q76vux4eQAmC
EUrFR9gOhTt99ZYVecLCpWL54tnabK+cTJ/jaXlDMG4eeVGl2AG2QN/sbTKJAC6Z
G+kyBfTZYhFrFzVxcFO12CT1vpAKG6DPNKY80Ox91mzdM/h4pg/mDJkK5TQ9hD14
rIyrz8A9SpjUeBRY+zpPFbOR2fGVu/7RsYDTWCoVIsRltSmXTBlCknmBX3jBuKa3
1kkrdXYtLVTEiW4gHRB2hZ5GSRXlbMeykuCK1wKy2BVjzvzOI8LKBdztVD3816f7
K8RId0999g4ko3NO/U+Mk2SIfNgKHcB8fBxO9Kc6Q096vIWemoQ=
=qrAZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-wayland-sys
Source-Version: 0.31.3-1
Done: Peter Michael Green 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Jul 2024 00:50:30 +
Source: rust-wayland-sys
Architecture: source
Version: 0.31.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1076057
Changes:
 rust-wayland-sys (0.31.3-1) unstable; urgency=medium
 .
   * Team upload.
   * Package wayland-sys 0.31.3 from crates.io using debcargo 2.6.1
   * Relax memoffset dependency (Closes: #1076057).
Checksums-Sha1:
 252ebc5a72aa95077f347005e75588b2ac09bdaa 2383 rust-wayland-sys_0.31.3-1.dsc
 6b1fa94f14585a35d467e1db0cc6f2884e94386f 8573 
rust-wayland-sys_0.31.3.orig.tar.gz
 02968143d157d4486f8fb1529ef7331dff5e6a30 3396 
rust-wayland-sys_0.31.3-1.debian.tar.xz
 504db093c6abca6f777543d599d797fc2f1a7303 11088 
rust-wayland-sys_0.31.3-1_source.buildinfo
Checksums-Sha256:
 2016da941a8780a5c95a019b40e753e854b61fdf1176b2eb892bcf5ed32fec4c 2383 
rust-wayland-sys_0.31.3-1.dsc
 4a6754825230fa5b27bafaa28c30b3c9e72c55530581220cef401fa422c0fae7 8573 
rust-wayland-sys_0.31.3.orig.tar.gz
 325a05050e9994f170ef492a2faeb00c76eb87360c7c5667dd0438cc7e694dbc 3396 
rust-wayland-sys_0.31.3-1.debian.tar.xz
 9d8adadb94f9b6b6066e5c95e1bd622fd8cf4c52f156fc8ba1783853ab9c4a6f 11088 
rust-wayland-sys_0.31.3-1_source.buildinfo
Files:
 e2abf115594aacf62f9642c93b64c9f1 2383 rust optional 
rust-wayland-sys_0.31.3-1.dsc
 42400cf91907d878f4620040a477265e 8573 rust optional 
rust-wayland-sys_0.31.3.orig.tar.gz
 3e4c04ca7c2cb24b7167ccde64fc51e8 3396 rust optional 
rust-wayland-sys_0.31.3-1.debian.tar.xz
 b00e8d9053831fb632e5339c459a2246 11088 rust optional 
rust-wayland-sys_0.31.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmaN3xsUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xsocg//Y7epByHjujrQsjjmdtYgasSGLkN0
wVi6Bt0LLsBKCIgWIRf6otDYU/m78kZwcRBwhktPGUeedXyRumvCMP2P4OmCtdIB
Qj/dDicLDIGvkANma+hPP9WtTs4tC1oUzKeeRvlm99H0XMBxsA4FjaFpXRlLq43r
XYc5SqlGN8sDV3VauofCNTOhq/SALu28VZqkVSi4y0mhQHDp0xEAd9fOjth5igLD
ye9x0EZaD+K4sYTgTeJnNRoHh64Y0rfOOfRO1v0boGuc0Q+KLs9fuhNfD/y3OWDP
ok+2tkrm/XLVcBCTLOmPx3QDZwcRr80RJIDA9oUv8QWpQiAw8nf7RTatdAaNHLA8

Bug#1076058: marked as done (librust-wayland-sys-0.29-dev: impossible to install: depends on librust-memoffset-0.6+default-dev)

[Debian Bug Tracking System]

Your message dated Tue, 9 Jul 2024 20:53:26 -0400
with message-id 

and subject line Re: Bug#1076058: librust-wayland-sys-0.29-dev: impossible to 
install: depends on librust-memoffset-0.6+default-dev
has caused the Debian Bug report #1076058,
regarding librust-wayland-sys-0.29-dev: impossible to install: depends on 
librust-memoffset-0.6+default-dev
to be marked as done.

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

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


-- 
1076058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-wayland-sys-0.29-dev
Version: 0.29.5-2+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package is impossible to install, as it depends on missing
package librust-memoffset-0.6+default-dev.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmaNx0oACgkQLHwxRsGg
ASGRShAArnuj8fFrZlDGZ3vKbmhiVjuCkA2wEtY9D5GRor6M8HDJtKvctSUY4bJD
xEoU7UD6lG65/Avc1q+WMeoCHYDi+Jm/jaPqhZWcErs4PxQ2apVwOgLcmk94zoNE
uoTkuAgv4paM5xjH4d4ZsF7LAh7jqSH+Ejh38Meu38yazF7S3o88igEU55S1PbQF
JUOu6PoFNi4DmxZUCSOanD5JEIqPCRDK6245X3Kiv6IQJ9UrGEqBtnqRGJVSbPXC
oDW4sVftnfanoNk76f/BAxC0xash5JeM7TRQBW9pduUPUH4rjrtDB8q+s9b7QhON
u7hJ65y9BpemWleWmTMSeevCu9DjiZeXvbOebwQEvxKNF/rlg99P6/TwYvlKD5HL
Hpz/atfenX7GT9Nm2bHgkM3ZUCKbYOrq4mbGbus9XYpnDBkLk3vgx5zS94uDIH05
6Vd+/u1DC84zj3N101NuEvoJe8YJHAjW4wdV1gQFC6WZo3XSwfiKGMKub+Gl734t
9BUQ/FMC+FisA1z4S8rJMBSPPY/uFC1fqr7oriZ7FyPGr2fs9qybpeC5/02FCVR/
f45YmP82jdU+i9r6dq9wZSXC6CoJB8R8uI2j8ovhztt3h4aXtGotNokb/Mu+sZkb
sVJ/a1bKmJXcDyKdNpAW+w+NRelPWQ4LXHaYwxzrfPz1tJ84hmc=
=ZMr2
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.29.5-3

On Wed, Jul 10, 2024 at 01:27:06AM GMT, Jonas Smedegaard wrote:
> Binary package is impossible to install, as it depends on missing
> package librust-memoffset-0.6+default-dev.

A fix for this was uploaded in -3, shortly before the bug was filed.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB--- End Message ---

Bug#1076060: LICENSE.txt says Apache 2.0, not GPL-3

[Paul R. Tagliamonte]

Package: meshtastic
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

The LICENSE file is Apache 2. The pyproject.toml says GPL-3. I did some
looking upstream, and there's a bug[1] and a PR that was fixed last week[2].

I don't love the way this source package is right now, but the Debian
metadata is correct, and since it's GPL-3 we comply given common-licenses.

Please ensure once upstream releases with a fixed LICENSE you update sid.
Please do not allow this package into testing like this.

Paul, on behalf of the ftpteam

[1]: https://github.com/meshtastic/python/issues/422
[2]: https://github.com/meshtastic/python/pull/582

-- 
:wq

Processed: severity 1052507

[Debian Bug Tracking System]

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

> severity 1052507 serious
Bug #1052507 [src:azure-cosmos-python] azure-cosmos-python: upstream has moved 
to another repository
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Processed: 1073411 1072312

[Debian Bug Tracking System]

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

> severity 1073411 normal
Bug #1073411 [src:azure-cli] azure-cli: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Severity set to 'normal' from 'serious'
> severity 1072312 normal
Bug #1072312 [src:azure-cli] azure-cli: autopkgtest regression with pytest 8.2
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#1076058: librust-wayland-sys-0.29-dev: impossible to install: depends on librust-memoffset-0.6+default-dev

[Jonas Smedegaard]

Package: librust-wayland-sys-0.29-dev
Version: 0.29.5-2+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package is impossible to install, as it depends on missing
package librust-memoffset-0.6+default-dev.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmaNx0oACgkQLHwxRsGg
ASGRShAArnuj8fFrZlDGZ3vKbmhiVjuCkA2wEtY9D5GRor6M8HDJtKvctSUY4bJD
xEoU7UD6lG65/Avc1q+WMeoCHYDi+Jm/jaPqhZWcErs4PxQ2apVwOgLcmk94zoNE
uoTkuAgv4paM5xjH4d4ZsF7LAh7jqSH+Ejh38Meu38yazF7S3o88igEU55S1PbQF
JUOu6PoFNi4DmxZUCSOanD5JEIqPCRDK6245X3Kiv6IQJ9UrGEqBtnqRGJVSbPXC
oDW4sVftnfanoNk76f/BAxC0xash5JeM7TRQBW9pduUPUH4rjrtDB8q+s9b7QhON
u7hJ65y9BpemWleWmTMSeevCu9DjiZeXvbOebwQEvxKNF/rlg99P6/TwYvlKD5HL
Hpz/atfenX7GT9Nm2bHgkM3ZUCKbYOrq4mbGbus9XYpnDBkLk3vgx5zS94uDIH05
6Vd+/u1DC84zj3N101NuEvoJe8YJHAjW4wdV1gQFC6WZo3XSwfiKGMKub+Gl734t
9BUQ/FMC+FisA1z4S8rJMBSPPY/uFC1fqr7oriZ7FyPGr2fs9qybpeC5/02FCVR/
f45YmP82jdU+i9r6dq9wZSXC6CoJB8R8uI2j8ovhztt3h4aXtGotNokb/Mu+sZkb
sVJ/a1bKmJXcDyKdNpAW+w+NRelPWQ4LXHaYwxzrfPz1tJ84hmc=
=ZMr2
-END PGP SIGNATURE-

Bug#1076057: librust-wayland-sys-dev: impossible to install: depends on librust-memoffset-0.6+default-dev

[Jonas Smedegaard]

Package: librust-wayland-sys-dev
Version: 0.31.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package is impossible to install, as it depends on missing
package librust-memoffset-0.6+default-dev.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmaNxgwACgkQLHwxRsGg
ASEQGw/8CVdzUuAYefO21HpPt5iNC/vBNtcq6YdsJh1wxAIt3p2lvlXjpXznTMfW
XJfBLH3okJZuT+znDZn4l8JyJiyOmSA5/KvGvcrGe9g469UJgLfgvqrUTaTL6by7
iDMRxLJhsXoBIhOAGiyn1V/2eLongzQXu2H1rdME+cZUOsVoqOvChDdpM5ZtgK0w
LGwimffsaO+ZH3yPuXEec2FqRB0vApIleQM2dyRCXqhTZMyFENoDUyHUhpN/UrBk
7l4OEobqAiYMd3v1A2WxENgvD4Dz4gLlfOcZFxfNlD7CphWKo045qzHXvjsVPOJo
Jvr/8a+Okgn++40wD5TAx9MbiRuXD4EknLZmONakwbbBEzD0FhA/q76vux4eQAmC
EUrFR9gOhTt99ZYVecLCpWL54tnabK+cTJ/jaXlDMG4eeVGl2AG2QN/sbTKJAC6Z
G+kyBfTZYhFrFzVxcFO12CT1vpAKG6DPNKY80Ox91mzdM/h4pg/mDJkK5TQ9hD14
rIyrz8A9SpjUeBRY+zpPFbOR2fGVu/7RsYDTWCoVIsRltSmXTBlCknmBX3jBuKa3
1kkrdXYtLVTEiW4gHRB2hZ5GSRXlbMeykuCK1wKy2BVjzvzOI8LKBdztVD3816f7
K8RId0999g4ko3NO/U+Mk2SIfNgKHcB8fBxO9Kc6Q096vIWemoQ=
=qrAZ
-END PGP SIGNATURE-

Processed: BTS housekeeping

[Debian Bug Tracking System]

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

> # build dependencies were not installable during time_t transition
> close 1069473
Bug #1069473 [src:prelude-manager] prelude-manager: FTBFS on armhf: 
unsatisfiable build-dependencies
Marked Bug as done
> close 1069479
Bug #1069479 [src:libpreludedb] libpreludedb: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> close 1069506
Bug #1069506 [src:prelude-lml] prelude-lml: FTBFS on armhf: unsatisfiable 
build-dependencies
Marked Bug as done
> close 1069514
Bug #1069514 [src:trophy] trophy: FTBFS on armhf: unsatisfiable dependencies
Marked Bug as done
> close 1069530
Bug #1069530 [src:mumudvb] mumudvb: FTBFS on armhf: unsatisfiable 
build-dependency: libzvbi-common (= 0.2.42-1.1) but 0.2.42-2 is to be installed
Marked Bug as done
> # stale binaries have been removed
> close 1069497
Bug #1069497 [src:osmo-hlr] osmo-hlr: FTBFS on armhf: build-dependency not 
installable: libosmo-netif-dev (>= 1.2.0)
Marked Bug as done
> # binary-all does not have to be buildable on !amd64
> close 1069462
Bug #1069462 [src:snek] snek: FTBFS on armhf: build-dependency not installable: 
gcc-arm-linux-gnueabi
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069462
1069473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069473
1069479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069479
1069497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069497
1069506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069506
1069514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069514
1069530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068468: marked as done (tracker: failing autopkgtest)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 22:50:19 +
with message-id 
and subject line Bug#1068468: fixed in tracker 3.7.3-2
has caused the Debian Bug report #1068468,
regarding tracker: failing autopkgtest
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.)


-- 
1068468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tracker
Version: 3.7.1-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/tracker/-/issues/434

tracker's autopkgtest began failing after the update from 3.7.0 to
3.7.1. This is preventing tracker from being eligible for migration to
Testing.

I have reported the issue upstream.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: tracker
Source-Version: 3.7.3-2
Done: Sebastien Bacher 

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

Debian distribution maintenance software
pp.
Sebastien Bacher  (supplier of updated tracker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jul 2024 23:08:29 +0200
Source: tracker
Built-For-Profiles: noudeb
Architecture: source
Version: 3.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Sebastien Bacher 
Closes: 1068468
Changes:
 tracker (3.7.3-2) unstable; urgency=medium
 .
   [ Alessandro Astone ]
   * Fix autopkgtests and cherrypick some upstream build fixes
 (Closes: #1068468)
Checksums-Sha1:
 9e4a2ca732e8bd3dd3012c85b18d3b5507609b51 2829 tracker_3.7.3-2.dsc
 885b89cd6df7a38c3a62cb2d190e73d8b4dbd0c2 26852 tracker_3.7.3-2.debian.tar.xz
 7292c1f1d6694955d2837465a789071e2a6d45f9 23928 tracker_3.7.3-2_source.buildinfo
Checksums-Sha256:
 4ed4a6d3082c3b5647a7e80fd003287220d210202861378960beb58b23163a8c 2829 
tracker_3.7.3-2.dsc
 fe7c071c90afe427f1e94504c08f2fa4b88bed72b6b74febc9fda1d2084f0169 26852 
tracker_3.7.3-2.debian.tar.xz
 e1bbd42379669281b8d8a468640b80e14b80dd12006aeb9e038ff25a3b98a38b 23928 
tracker_3.7.3-2_source.buildinfo
Files:
 b000adfa407ac13a763f1a765f8fb0f4 2829 utils optional tracker_3.7.3-2.dsc
 126cc76c9abb0005ea885aa83dccbb7c 26852 utils optional 
tracker_3.7.3-2.debian.tar.xz
 2ca7b0a20cf3375571c0cf95efee848a 23928 utils optional 
tracker_3.7.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERyS4b0fgKRXe6kniPr1EkD7bBJYFAmaNp4QACgkQPr1EkD7b
BJbpIA/8C2Tq14w5S+MJdqzyC63ScqfjJn2ruC6gqUs3449cdGY6+xWr3zzodvsY
IRNO5zC7HRsj1CzRObspLVPE3UuFU4fcNk+fsdW8IEG08TfwIgF+TZ8HLwl1/+9J
s2cexvYzBYpF7INMB6PCaKwQf3mnXDlzewn9OsLF+1Pfy5v7N2ZP+uc/cMW23OjV
KtFUBc/oWSbebk+KnpqEe5CGa4jFaDdEAyDcIw9FsjvKTsyBLhS5fGXwLck8Fn52
bBAi+uDDSjxjR6hU156/OGuFZAkQvrb55m2jRWxZhZkjh45IY944A7CLGd6PZgOe
7sUJEgOJh7ggmSZDW1bckUexqIOfG8GhkqIBw3iJJWSpeRB3rdwS6lmbzmjvsjy/
DbzadKU9ovbVkYnBauVCnJFp8peDR2SShsTijLgCXx0rRGTVwWagMBrVbvo9A9Pq
ptGopA3bz6/S4UhIUOCOsBsKoBhilcjV+WKPU7S9Si4pfu5VP/B/Tt8URs3rSUI5
9QHdSoLrrhqSmqDZelc/e+R12+OK0H59ifZv6ab6lCftLdH8ySdVpZx1CYUlRYWj
h5JKrZ2HfPi7nH4P3bOnij2LyJDVuZJr3D8aRUcAc712VX/qRByFsm9XufQOqEGO
mStw9TG+N6XvLSGk9EZ/6XsUL4I2RmhqvEq/o5O+wVOpN6C6DTc=
=v/JL
-END PGP SIGNATURE-



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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1069429 src:openmpi
Bug #1069429 [src:dbcsr] dbcsr: FTBFS on armhf: tests fail
Bug reassigned from package 'src:dbcsr' to 'src:openmpi'.
No longer marked as found in versions dbcsr/2.6.0-2.
Ignoring request to alter fixed versions of bug #1069429 to the same values 
previously set
> forcemerge 1069433 1069429
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi] 
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Removed indication that 1069439 affects src:ruby-mpi, src:mpgrafic, src:arpack, 
src:python-escript, and src:gtg-trace
Added indication that 1069439 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Removed indication that 1069418 affects src:ruby-mpi, src:mpgrafic, src:arpack, 
src:python-escript, and src:gtg-trace
Added indication that 1069418 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Removed indication that 1069433 affects src:gtg-trace, src:ruby-mpi, 
src:mpgrafic, src:arpack, and src:python-escript
Added indication that 1069433 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Removed indication that 1069511 affects src:ruby-mpi, src:mpgrafic, 
src:python-escript, src:arpack, and src:gtg-trace
Added indication that 1069511 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Removed indication that 1069512 affects src:gtg-trace, src:mpgrafic, 
src:ruby-mpi, src:python-escript, and src:arpack
Added indication that 1069512 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Bug #1069429 [src:openmpi] dbcsr: FTBFS on armhf: tests fail
Marked Bug as done
Added indication that 1069429 affects 
src:python-escript,src:gtg-trace,src:arpack,src:ruby-mpi,src:mpgrafic
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-3 and openmpi/4.1.6-12.
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069511 {Done: Samuel Thibault } [src:openmpi] 
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Merged 1069418 1069429 1069433 1069439 1069511 1069512
> affects 1069433 src:dbcsr
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069429 {Done: Samuel Thibault } [src:openmpi] 
dbcsr: FTBFS on armhf: tests fail
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi] 
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:dbcsr
Added indication that 1069418 affects src:dbcsr
Added indication that 1069429 affects src:dbcsr
Added indication that 1069439 affects src:dbcsr
Added indication that 1069511 affects src:dbcsr
Added indication that 1069512 affects src:dbcsr
> thanks
Stopping processing here.

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

Processed: tagging 1063190 as pending

[Debian Bug Tracking System]

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

> tags  1063190 +pending
Bug #1063190 [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t 
transition
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1068468: marked as pending in tracker

[Sebastien Bacher]

Control: tag -1 pending

Hello,

Bug #1068468 in tracker 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/gnome-team/tracker/-/commit/587320af234305f93f80aefc31ff81a8b3a2bf69


Fix autopkgtests

libtracker-sparql-3-0 is the only library loaded form LD_LIBRARY_PATH.
First we compile the tests, which will also compile this library, then
we replace it with the system installed version of the library, which
will dlopen loadable modules from /usr/lib/$arch/tracker-3.0/

libtracker-common is a static library, so we cannot use the system
installed version. We must compile it masking the BUILDROOT macro
to make it load modules from /usr/lib/$arch/tracker-3.0/ rather than
from the build dir.

We can re-enable the tracker:sparql suite because it's passing.

Closes: #1068468


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068468

Processed: Bug#1068468 marked as pending in tracker

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068468 [src:tracker] tracker: failing autopkgtest
Added tag(s) pending.

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

Bug#1061241: endless-sky: debian/copyright incomplete

[Bo YU]

Hi,

Thanks for pointing out this. The upload for 0.10.4-1 was from me, so I
am trying to fix the issue now. But before this, it seems I can learn
more from here.:)

On Sun, Jan 21, 2024 at 10:56:05AM +, Damyan Ivanov wrote:


The upgrade to 0.10.4 missed the changes in upstream licensing and
copyright notices.

The changes in the summary, as supplied by upstream, can be seen at
https://salsa.debian.org/games-team/endless-sky/-/commit/d7fef4cf2282a3ab364133093e5f156bc5f1d790#521307ddb67a4abc14248801dae5e5989aca76c1


right. The changes in upstream copyright should affect debian/copyright
also. Understand it now.



Note that this 'copyright' file looks much like Debian's
'debian/copyright' but fails some expectations like listing general
Files: patterns before more specific ones so it can't be used verbatim.


So can I think the issue was for upstream copyright? But it seems it was
fixed by upstream[0]

In fact I think we can reduce some text extern for license description
for debian/copyright also.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061241#12

Thanks all,

BR,
Bo





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1076036: python3-setuptools: uninstallable in unstable

[Colin Watson]

On Tue, Jul 09, 2024 at 07:57:51PM +0100, Colin Watson wrote:
> Following
> https://tracker.debian.org/news/1543129/accepted-python3-stdlib-extensions-3124-1-source-into-unstable/,
> python3-setuptools is uninstallable in unstable:

Indeed, setuptools Build-Depends: dh-python Depends: python3-setuptools,
so unstable's ability to build anything Python-related has been
completely botched and this should have been done in some other order.
I guess it can be fixed with a manual build of setuptools against an
older version of dh-python, although it will also be necessary to deal
with https://bugs.debian.org/1056198 ("src:setuptools: build depends on
dh-python but build conflicts with python3-setuptools").

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: closing 1069373

[Debian Bug Tracking System]

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

> close 1069373 0.4.0~alpha7-2
Bug #1069373 [src:oxigraph] oxigraph: FTBFS on arm64: unsatisfiable 
build-dependencies: librust-oxhttp-0.1+default-dev, 
librust-oxhttp-0.1+rayon-dev, librust-oxhttp-0.1+rustls-dev
Marked as fixed in versions oxigraph/0.4.0~alpha7-2.
Bug #1069373 [src:oxigraph] oxigraph: FTBFS on arm64: unsatisfiable 
build-dependencies: librust-oxhttp-0.1+default-dev, 
librust-oxhttp-0.1+rayon-dev, librust-oxhttp-0.1+rustls-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1076036: python3-setuptools: uninstallable in unstable

[Colin Watson]

Package: python3-setuptools
Version: 68.1.2-2
Severity: grave
Justification: renders package unusable

Following
https://tracker.debian.org/news/1543129/accepted-python3-stdlib-extensions-3124-1-source-into-unstable/,
python3-setuptools is uninstallable in unstable:

  # apt install python3-setuptools
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  Unsatisfied dependencies:
   python3-setuptools : Depends: python3-distutils but it is not installable
  Error: Unable to correct problems, you have held broken packages.
  # apt install python3-setuptools python3-distutils
  Package python3-distutils is not available, but is referred to by another 
package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  
  Error: Package 'python3-distutils' has no installation candidate

This obviously seems likely to break builds of a large number of other
packages - we noticed it in debusine's reprotest CI jobs.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: hplip: diff for NMU version 3.22.10+dfsg0-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1075760 + pending
Bug #1075760 [hplip-gui] hplip-gui breaks with python 3.12
Added tag(s) pending.

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

Bug#1075760: hplip: diff for NMU version 3.22.10+dfsg0-5.1

[Boyuan Yang]

Control: tags 1075760 + pending

Dear maintainer,

I've prepared an NMU for hplip (versioned as 3.22.10+dfsg0-5.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru hplip-3.22.10+dfsg0/debian/changelog 
hplip-3.22.10+dfsg0/debian/changelog
--- hplip-3.22.10+dfsg0/debian/changelog2024-04-26 17:39:02.0 
-0400
+++ hplip-3.22.10+dfsg0/debian/changelog2024-07-09 00:32:24.0 
-0400
@@ -1,3 +1,10 @@
+hplip (3.22.10+dfsg0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use read_file instead of readfp for python 3.12 (Closes: #1075760)
+
+ -- Tianyu Chen   Tue, 09 Jul 2024 12:32:24 +0800
+
 hplip (3.22.10+dfsg0-5) unstable; urgency=medium
 
   * take care of implicit function declarations (Closes: #1066348)
diff -Nru hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch 
hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
--- hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
1969-12-31 19:00:00.0 -0500
+++ hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
2024-07-09 00:32:24.0 -0400
@@ -0,0 +1,51 @@
+Description: Use read_file instead of readfp for python 3.12
+Author: Tianyu Chen 
+Bug-Debian: https://bugs.debian.org/1075760
+Forwarded: no
+Last-Update: 2024-07-09
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/base/g.py
 b/base/g.py
+@@ -128,7 +128,7 @@ class ConfigBase(object):
+ try:
+ fp = open(self.filename, "r")
+ try:
+-self.conf.readfp(fp)
++self.conf.read_file(fp)
+ except configparser.MissingSectionHeaderError:
+ print("")
+ log.error("Found No Section in %s. Please set the http 
proxy for root and try again." % self.filename)
+--- a/ui/devmgr4.py
 b/ui/devmgr4.py
+@@ -1227,7 +1227,7 @@ class DevMgr4(DevMgr4_base):
+ 
+ hplip_conf = ConfigParser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+ 
+ try:
+--- a/ui4/devmgr5.py
 b/ui4/devmgr5.py
+@@ -1024,7 +1024,7 @@ class DevMgr5(QMainWindow,  Ui_MainWindo
+ 
+ hplip_conf = configparser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+ 
+ try:
+--- a/ui5/devmgr5.py
 b/ui5/devmgr5.py
+@@ -1072,7 +1072,7 @@ class DevMgr5(Ui_MainWindow_Derived, Ui_
+ 
+ hplip_conf = configparser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+ 
+ try:
diff -Nru hplip-3.22.10+dfsg0/debian/patches/series 
hplip-3.22.10+dfsg0/debian/patches/series
--- hplip-3.22.10+dfsg0/debian/patches/series   2024-04-26 17:39:02.0 
-0400
+++ hplip-3.22.10+dfsg0/debian/patches/series   2024-07-09 00:32:24.0 
-0400
@@ -82,3 +82,4 @@
 0082-Some-of-the-print-modes-for-DeskJet-815C-are-incorre.patch
 0083-add-format-string-to-snprintf.patch
 0084-take-care-of-implicit-declaration-of-functions.patch
+0085-python-3.12-compat.patch


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

Processed: playmidi: FTBFS when built in parallel

[Debian Bug Tracking System]

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

> retitle 1076021 playmidi: FTBFS when built in parallel
Bug #1076021 {Done: Santiago Vila } [playmidi] playmidi: 
FTBFS
Changed Bug title to 'playmidi: FTBFS when built in parallel' from 'playmidi: 
FTBFS'.
> thanks
Stopping processing here.

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

Bug#1076031: freecad seems linked to python 3.11

[Prior Jerome]

Package: freecad
Version: 0.21.2+dfsg1-4
Severity: grave
Justification: renders package unusable

ldd /usr/bin/freecad | grep found
libpyside2.cpython-311-x86_64-linux-gnu.so.5.15 => not found
libshiboken2.cpython-311-x86_64-linux-gnu.so.5.15 => not found



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

Kernel: Linux 5.9.0-0.bpo.5-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 freecad depends on:
ii  freecad-python3  0.21.2+dfsg1-4

Versions of packages freecad recommends:
ii  calculix-ccx2.21-1
ii  graphviz2.42.4-1
ii  python3-opencamlib  2023.01.11-5

Versions of packages freecad suggests:
pn  povray  

-- no debconf information

Bug#1076030: superlu-dist: FTBFS with mpich as default MPI implementation on 32 bit architectures: 0% tests passed, 17 tests failed out of 17

[Sebastian Ramacher]

Source: superlu-dist
Version: 8.2.1+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=superlu-dist=armel=8.2.1%2Bdfsg1-1%2Bb3=1720482168=0

est 1
  Start  1: pdtest_1x1_1_2_8_20_SP

1: Test command: /usr/bin/mpiexec "-n" "1" "--allow-run-as-root" "./pdtest" 
"-r" "1" "-c" "1" "-s" "1" "-b" "2" "-x" "8" "-m" "20" "-f" 
"/<>/EXAMPLE/g20.rua"
1: Working Directory: /<>/obj-arm-linux-gnueabi/TEST
1: Test timeout computed to be: 1500
1: [mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized 
argument allow-run-as-root
1: [mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
1: [mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
1: [mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
1: [mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters
 1/17 Test  #1: pdtest_1x1_1_2_8_20_SP ...***Failed0.00 sec
[mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized argument 
allow-run-as-root
[mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
[mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
[mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
[mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters

test 2
  Start  2: pdtest_1x1_3_2_8_20_SP

2: Test command: /usr/bin/mpiexec "-n" "1" "--allow-run-as-root" "./pdtest" 
"-r" "1" "-c" "1" "-s" "3" "-b" "2" "-x" "8" "-m" "20" "-f" 
"/<>/EXAMPLE/g20.rua"
2: Working Directory: /<>/obj-arm-linux-gnueabi/TEST
2: Test timeout computed to be: 1500
2: [mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized 
argument allow-run-as-root
2: [mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
2: [mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
2: [mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
2: [mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters
 2/17 Test  #2: pdtest_1x1_3_2_8_20_SP ...***Failed0.00 sec
[mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized argument 
allow-run-as-root
[mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
[mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
[mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
[mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters

test 3
  Start  3: pdtest_1x2_1_2_8_20_SP

3: Test command: /usr/bin/mpiexec "-n" "2" "--allow-run-as-root" "./pdtest" 
"-r" "1" "-c" "2" "-s" "1" "-b" "2" "-x" "8" "-m" "20" "-f" 
"/<>/EXAMPLE/g20.rua"
3: Working Directory: /<>/obj-arm-linux-gnueabi/TEST
3: Test timeout computed to be: 1500
3: [mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized 
argument allow-run-as-root
3: [mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
3: [mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
3: [mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
3: [mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters
 3/17 Test  #3: pdtest_1x2_1_2_8_20_SP ...***Failed0.00 sec
[mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized argument 
allow-run-as-root
[mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
[mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
[mpiexec@arm-conova-02] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
[mpiexec@arm-conova-02] main (mpiexec/mpiexec.c:54): error parsing parameters

test 4
  Start  4: pdtest_1x2_3_2_8_20_SP

4: Test command: /usr/bin/mpiexec "-n" "2" "--allow-run-as-root" "./pdtest" 
"-r" "1" "-c" "2" "-s" "3" "-b" "2" "-x" "8" "-m" "20" "-f" 
"/<>/EXAMPLE/g20.rua"
4: Working Directory: /<>/obj-arm-linux-gnueabi/TEST
4: Test timeout computed to be: 1500
4: [mpiexec@arm-conova-02] match_arg (lib/utils/args.c:166): unrecognized 
argument allow-run-as-root
4: [mpiexec@arm-conova-02] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
4: [mpiexec@arm-conova-02] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
4: [mpiexec@arm-conova-02] 

Bug#1076029: openfoam: FTBFS with mpich as default MPI implementation on armhf and i386: PstreamGlobals.H:42:10: fatal error: mpi.h: No such file or directory

[Sebastian Ramacher]

Source: openfoam
Version: 1912.200626-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=openfoam=armhf=1912.200626-2%2Bb4=1720486618=0

g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/Pstream/dummy=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -O3  -DNoRepository 
-ftemplate-depth-100  -IlnInclude -I. -I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -shared -Xlinker 
--add-needed -Xlinker --no-as-needed 
/<>/build/linux64Gcc/src/Pstream/dummy/UPstream.o 
/<>/build/linux64Gcc/src/Pstream/dummy/UIPread.o 
/<>/build/linux64Gcc/src/Pstream/dummy/UOPwrite.o 
-L/<>/platforms/linux64Gcc/lib \
  -o /<>/platforms/linux64Gcc/lib/dummy/libPstream.so
wclean mpi
wmake  mpi (mpi=SYSTEMOPENMPI)
wmake mpi
ln: ./lnInclude
gcc: error: unrecognized command-line option ‘--showme:compile’
Making dependency list for source file PstreamGlobals.C
gcc: error: unrecognized command-line option ‘--showme:compile’
Making dependency list for source file UPstream.C
gcc: error: unrecognized command-line option ‘--showme:compile’
Making dependency list for source file UIPread.C
gcc: error: unrecognized command-line option ‘--showme:compile’
Making dependency list for source file UOPwrite.C
gcc: error: unrecognized command-line option ‘--showme:compile’
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/Pstream/mpi=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -O3  -DNoRepository 
-ftemplate-depth-100 -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX  
-Wno-old-style-cast -Wno-unused-local-typedefs -Wno-array-bounds 
-Wno-deprecated-declarations -fpermissive -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c UOPwrite.C -o 
/<>/build/linux64GccSYSTEMOPENMPI/src/Pstream/mpi/UOPwrite.o
gcc: error: unrecognized command-line option ‘--showme:compile’
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/Pstream/mpi=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -O3  -DNoRepository 
-ftemplate-depth-100 -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX  
-Wno-old-style-cast -Wno-unused-local-typedefs -Wno-array-bounds 
-Wno-deprecated-declarations -fpermissive -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c UIPread.C -o 
/<>/build/linux64GccSYSTEMOPENMPI/src/Pstream/mpi/UIPread.o
In file included from UOPwrite.C:33:
PstreamGlobals.H:42:10: fatal error: mpi.h: No such file or directory
   42 | #include 
  |  ^~~
compilation terminated.
gcc: error: unrecognized command-line option ‘--showme:compile’
make[2]: *** [/<>/wmake/rules/General/transform:35: 
/<>/build/linux64GccSYSTEMOPENMPI/src/Pstream/mpi/UOPwrite.o] 
Error 1
make[2]: *** Waiting for unfinished jobs
In file included from UIPread.C:33:
PstreamGlobals.H:42:10: fatal error: mpi.h: No such file or directory
   42 | #include 
  |  ^~~
compilation terminated.
make[2]: *** [/<>/wmake/rules/General/transform:35: 
/<>/build/linux64GccSYSTEMOPENMPI/src/Pstream/mpi/UIPread.o] Error 
1

Cheers
-- 
Sebastian Ramacher

Bug#1076028: h5py: FTBFS with mpich as default MPI implementation on armel, armhf, i386: build/h5py/_debian_h5py_mpi/tests/test_file.py::TestMPI::test_mpio make[1]: *** [debian/rules:125: override_dh_

[Sebastian Ramacher]

Source: h5py
Version: 3.11.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=h5py=armel=3.11.0-2%2Bb1=1720479778=0

build/h5py/_debian_h5py_mpi/tests/test_file.py::TestContextManager::test_context_manager
 PASSED [ 62%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestUnicode::test_nonexistent_file_unicode
 PASSED [ 62%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestUnicode::test_unicode 
PASSED [ 62%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestUnicode::test_unicode_hdf5_python_consistent
 PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestFileProperty::test_close 
PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestFileProperty::test_mode 
PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestFileProperty::test_property 
PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestClose::test_close PASSED [ 
63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestClose::test_close_multiple_default_driver
 PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestClose::test_closed_file 
PASSED [ 63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestFlush::test_flush PASSED [ 
63%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestRepr::test_repr PASSED [ 
64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestFilename::test_filename 
PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestCloseInvalidatesOpenObjectIDs::test_close
 PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestCloseInvalidatesOpenObjectIDs::test_close_one_handle
 PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestPathlibSupport::test_pathlib_accepted_file
 PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestPathlibSupport::test_pathlib_name_match
 PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestPickle::test_dump_error 
PASSED [ 64%]
build/h5py/_debian_h5py_mpi/tests/test_file.py::TestMPI::test_mpio make[1]: *** 
[debian/rules:125: override_dh_auto_test-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:55: build-arch] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1076027: abinit: FTBFS with mpich as default MPI implementation on 32 bit architectures: Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to INTEGER(4)

[Sebastian Ramacher]

Source: abinit
Version: 9.10.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=abinit=armel=9.10.4-3%2Bb2=1720487900=0

mpifort -DHAVE_CONFIG_H -I. -I../..  -I../../shared/common/src/10_defs 
-I../../shared/common/src/10_defs -I../../shared/common/src/12_hide_mpi 
-I../../shared/common/src/12_hide_mpi -I../../shared/common/src/14_hidewrite 
-I../../shared/common/src/14_hidewrite -I../../shared/common/src/16_hideleave 
-I../../shared/common/src/16_hideleave -I../../shared/common/src/27_toolbox_oop 
-I../../shared/common/src/27_toolbox_oop 
-I../../shared/common/src/28_numeric_noabirule 
-I../../shared/common/src/28_numeric_noabirule -I../../shared/libpaw/src 
-I../../shared/libpaw/src -I../../src/44_abitypes_defs 
-I../../src/44_abitypes_defs -I../../shared/common/src/incs 
-I../../shared/common/src/incs -I../../shared/common/src/mods 
-I../../shared/common/src/mods -I../../src/incs -I../../src/incs 
-I../../src/mods -I../../src/mods -I../../shared/libpaw/incs 
-I../../shared/libpaw/incs -I../../shared/libpaw/mods 
-I../../shared/libpaw/mods -I/usr/include/hdf5/serial   -ffree-form -J../mods  
-I/usr/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -ffree-line-length-none 
-fallow-argument-mismatch -c -o m_xredistribute.o m_xredistribute.F90
m_wffile.F90:3578:66:

 3578 |  call xmpio_type_struct(nbval+2,length1,depl1,type1,filetype,ierr)
  |  1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
m_wffile.F90:3461:66:

 3461 |  call xmpio_type_struct(nbval+2,length1,depl1,type1,filetype,ierr)
  |  1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
m_wffile.F90:2791:66:

 2791 |  call xmpio_type_struct(nbval+2,length1,depl1,type1,filetype,ierr)
  |  1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
m_wffile.F90:2658:66:

 2658 |  call xmpio_type_struct(nbval+2,length1,depl1,type1,filetype,ierr)
  |  1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
m_wffile.F90:1748:77:

 1748 |call 
xmpio_type_struct(nb+2,BlockLength,BlockDepl,BlockType,filetype,ierr)
  | 
1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
m_wffile.F90:1809:79:

 1809 |  call 
xmpio_type_struct(nb+2,BlockLength,BlockDepl,BlockType,filetype,ierr)
  | 
  1
Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to 
INTEGER(4)
make[4]: *** [Makefile:1205: m_wffile.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/src/51_manage_mpi'
make[3]: *** [Makefile:1249: all-recursive] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:1468: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:1393: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:20: build-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1076026: elpa: FTBFS with mpich as default MPI on i386: FAIL validate_complex_2stage_banded_default.sh (exit status: 15)

[Sebastian Ramacher]

Source: elpa
Version: 2022.11.001-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=elpa=i386=2022.11.001-3%2Bb1=1720479509=0

FAIL: validate_complex_2stage_banded_default.sh
===

Fatal error in internal_Init: Other MPI error, error stack:
internal_Init(48301)...: MPI_Init(argc=(nil), argv=(nil)) failed
MPII_Init_thread(242)..: 
MPID_Init(67)..: 
init_world(171): channel initialization failed
MPIDI_CH3_Init(84).: 
MPID_nem_init(314).: 
MPID_nem_tcp_init(175).: 
MPID_nem_tcp_get_business_card(397): 
GetSockInterfaceAddr(369)..: gethostbyname failed, x86-conova-02 (errno 
4)
Fatal error in internal_Init: Other MPI error, error stack:
internal_Init(48301)...: MPI_Init(argc=(nil), argv=(nil)) failed
MPII_Init_thread(242)..: 
MPID_Init(67)..: 
init_world(171): channel initialization failed
MPIDI_CH3_Init(84).: 
MPID_nem_init(314).: 
MPID_nem_tcp_init(175).: 
MPID_nem_tcp_get_business_card(397): 
GetSockInterfaceAddr(369)..: gethostbyname failed, x86-conova-02 (errno 
4)
FAIL validate_complex_2stage_banded_default.sh (exit status: 15)

build/elpa2_print_kernels
 This program will give information on the ELPA2 kernels, 
 which are available with this library and it will give 
 information if (and how) the kernels can be choosen at 
 runtime

  ELPA supports threads: no

 Information on ELPA2 real case: 
 === 
  choice via environment variable: yes
  environment variable name  : ELPA_DEFAULT_real_kernel

  Available real kernels are: 

   ELPA_2STAGE_REAL_GENERIC
   ELPA_2STAGE_REAL_GENERIC_SIMPLE
   ELPA_2STAGE_REAL_GENERIC_SIMPLE_BLOCK4
   ELPA_2STAGE_REAL_GENERIC_SIMPLE_BLOCK6


 Information on ELPA2 complex case: 
 === 
  choice via environment variable: yes
  environment variable name  : ELPA_DEFAULT_complex_kernel

  Available complex kernels are: 

   ELPA_2STAGE_COMPLEX_GENERIC
   ELPA_2STAGE_COMPLEX_GENERIC_SIMPLE


# error out in case of test suite failures
if grep ^FAIL build/test-suite.log; then exit 1; fi
FAIL: 
validate_c_version_complex_double_eigenvalues_1stage_analytic_explicit_default.sh
FAIL 
validate_c_version_complex_double_eigenvalues_1stage_analytic_explicit_default.sh
 (exit status: 15)
FAIL: validate_c_version_complex_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_c_version_complex_double_eigenvalues_1stage_analytic_default.sh 
(exit status: 15)
FAIL: 
validate_c_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL 
validate_c_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
 (exit status: 15)
FAIL: 
validate_c_version_real_double_eigenvalues_1stage_analytic_explicit_default.sh
FAIL 
validate_c_version_real_double_eigenvalues_1stage_analytic_explicit_default.sh 
(exit status: 15)
FAIL: validate_c_version_real_double_eigenvalues_1stage_analytic_default.sh
FAIL validate_c_version_real_double_eigenvalues_1stage_analytic_default.sh 
(exit status: 15)
FAIL: 
validate_c_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
FAIL 
validate_c_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
 (exit status: 15)
FAIL: 
validate_c_version_complex_double_cholesky_1stage_random_explicit_default.sh
FAIL 
validate_c_version_complex_double_cholesky_1stage_random_explicit_default.sh 
(exit status: 15)
FAIL: validate_c_version_complex_double_cholesky_1stage_random_default.sh
FAIL validate_c_version_complex_double_cholesky_1stage_random_default.sh (exit 
status: 15)
FAIL: validate_c_version_real_double_cholesky_1stage_random_explicit_default.sh
FAIL validate_c_version_real_double_cholesky_1stage_random_explicit_default.sh 
(exit status: 15)
FAIL: validate_c_version_real_double_cholesky_1stage_random_default.sh
FAIL validate_c_version_real_double_cholesky_1stage_random_default.sh (exit 
status: 15)
FAIL: 
validate_c_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
FAIL 
validate_c_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
 (exit status: 15)
FAIL: validate_c_version_complex_double_eigenvectors_1stage_random_default.sh
FAIL validate_c_version_complex_double_eigenvectors_1stage_random_default.sh 
(exit status: 15)
FAIL: 
validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
FAIL 
validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
 (exit status: 15)
FAIL: 
validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
FAIL 

Bug#1076025: elpa: FTBFS with mpich as default MPI implementation on armel and armhf: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

[Sebastian Ramacher]

Source: elpa
Version: 2022.11.001-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=elpa=armel=2022.11.001-3%2Bb1=1720487973=0

dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libelpa19/DEBIAN/symbols doesn't match 
completely debian/libelpa19.symbols
--- debian/libelpa19.symbols (libelpa19_2022.11.001-3+b1_armel)
+++ dpkg-gensymbolsMbVCy9   2024-07-09 01:19:26.616530530 +
@@ -4,15 +4,39 @@
  LEN@Base 2022.11.001
  STRUCTURE_PARAMETERS@Base 2022.11.001
  __add_tmp_MOD_add_tmp_double@Base 2022.11.001
+ __aligned_mem_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __aligned_mem_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __aligned_mem_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __aligned_mem_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __aligned_mem_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __aligned_mem_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  __check_monotony_MOD_check_monotony_double@Base 2022.11.001
+ __cholesky_cuda_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_cuda_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_cuda_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_cuda_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_cuda_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_cuda_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  __cholesky_cuda_MOD_cuda_copy_double_a_tmatc@Base 2022.11.001
  __cholesky_cuda_MOD_cuda_copy_double_complex_a_tmatc@Base 2022.11.001
  __cholesky_cuda_MOD_cuda_copy_float_a_tmatc@Base 2022.11.001
  __cholesky_cuda_MOD_cuda_copy_float_complex_a_tmatc@Base 2022.11.001
+ __cholesky_gpu_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_gpu_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_gpu_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_gpu_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_gpu_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_gpu_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  __cholesky_gpu_MOD_gpu_copy_double_a_tmatc@Base 2022.11.001
  __cholesky_gpu_MOD_gpu_copy_double_complex_a_tmatc@Base 2022.11.001
  __cholesky_gpu_MOD_gpu_copy_float_a_tmatc@Base 2022.11.001
  __cholesky_gpu_MOD_gpu_copy_float_complex_a_tmatc@Base 2022.11.001
+ __cholesky_hip_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_hip_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_hip_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_hip_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cholesky_hip_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cholesky_hip_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  __cholesky_hip_MOD_hip_copy_double_a_tmatc@Base 2022.11.001
  __cholesky_hip_MOD_hip_copy_double_complex_a_tmatc@Base 2022.11.001
  __cholesky_hip_MOD_hip_copy_float_a_tmatc@Base 2022.11.001
@@ -27,6 +51,12 @@
  __cuda_c_kernel_MOD_launch_my_pack_cuda_kernel_real_double@Base 2022.11.001
  __cuda_c_kernel_MOD_launch_my_unpack_cuda_kernel_complex_double@Base 
2022.11.001
  __cuda_c_kernel_MOD_launch_my_unpack_cuda_kernel_real_double@Base 2022.11.001
+ __cuda_functions_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cuda_functions_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cuda_functions_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cuda_functions_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __cuda_functions_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __cuda_functions_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  __cuda_functions_MOD_cublas_ccopy_cptr@Base 2022.11.001
  __cuda_functions_MOD_cublas_ccopy_intptr@Base 2022.11.001
  __cuda_functions_MOD_cublas_cgemm_cptr@Base 2022.11.001
@@ -165,6 +195,12 @@
  __elpa_abstract_impl_MOD_elpa_set_double@Base 2022.11.001
  __elpa_abstract_impl_MOD_elpa_set_float@Base 2022.11.001
  __elpa_abstract_impl_MOD_elpa_set_integer@Base 2022.11.001
+ __elpa_api_MOD___copy___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __elpa_api_MOD___copy___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __elpa_api_MOD___def_init___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __elpa_api_MOD___def_init___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
+ __elpa_api_MOD___vtab___iso_c_binding_C_funptr@Base 2022.11.001-3+b1
+ __elpa_api_MOD___vtab___iso_c_binding_C_ptr@Base 2022.11.001-3+b1
  

Bug#1076021: marked as done (playmidi: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 17:35:25 +
with message-id 
and subject line Bug#1076021: fixed in playmidi 2.4debian-17
has caused the Debian Bug report #1076021,
regarding playmidi: FTBFS
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.)


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

Package: playmidi
Version: 2.4debian-16
Severity: serious
Tags: ftbfs

This is to let everybody know that I'm aware that the QA upload I've just made
does not build ok. I'll try to fix this myself.

Thanks.
--- End Message ---
--- Begin Message ---
Source: playmidi
Source-Version: 2.4debian-17
Done: Santiago Vila 

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated playmidi 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, 09 Jul 2024 19:25:00 +0200
Source: playmidi
Architecture: source
Version: 2.4debian-17
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Closes: 1076021
Changes:
 playmidi (2.4debian-17) unstable; urgency=medium
 .
   * QA upload.
   * Disable parallel build for now. Closes: #1076021.
Checksums-Sha1:
 fc8dc9fffefc215cd914380b609df4b1a1ec15e8 1564 playmidi_2.4debian-17.dsc
 b10c860eca28aef41727e264cb02cd60fcb5bdc5 31800 
playmidi_2.4debian-17.debian.tar.xz
 fca5e9c83ec36ff92199ef8112d23edaef5be87c 6112 
playmidi_2.4debian-17_source.buildinfo
Checksums-Sha256:
 b436362c42d115bf0b82f20388ffcb8cf2179ace1f635109122a4ec5e7efc0d1 1564 
playmidi_2.4debian-17.dsc
 7ff012f2fd83cc55b26bff46d05044895025d9ae44f4e0c10794e8e9fe8d2762 31800 
playmidi_2.4debian-17.debian.tar.xz
 7a22583d0c78b7aba5997d38abf5696f5922edff968f01bc27fc88bed9339412 6112 
playmidi_2.4debian-17_source.buildinfo
Files:
 dbcf4051bacc815556a0133943e78fe0 1564 sound optional playmidi_2.4debian-17.dsc
 8da2b529fc92aab338cc8fb6a57bb2dc 31800 sound optional 
playmidi_2.4debian-17.debian.tar.xz
 79541bbd70f1f0814ada25ce020cb053 6112 sound optional 
playmidi_2.4debian-17_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmaNcyoACgkQQc5/C58b
izLp+Qf/fCMSTIRR6sn0K34d0omzsuMBtXqnFZv9Cu58yXbhwA3k50At7BdNBeeD
MscVKDbRy8baWpNxnjCASDIKjJcJAhDKA1swFsQ/M7SWKm8+xiWLNBoaXLMvkocm
048FyHM0ynPYrduNJPgIZDsEX0bkuiaCQX23gm1i74ZXvCSI9nY3F//h9u6qMths
QW+4tbUHZhTJsAXNwRTs+wuDtBny3xAck8FgVcO0ZqTLDCdU+m4/rlM/8K8BhVan
kLQNm57QJCAbulAquwHmHYjN1D6A+u+QCpMmQMir6UUoL3QzKNKnuoajcx5ve0bP
N/3IqW/Fja2pdPuCnxMSPVexH+dQFg==
=CV3q
-END PGP SIGNATURE-



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

Bug#1039883: linux: ext4 corruption with symlinks

[Ben Hutchings]

Control: tag -1 patch fixed-upstream

A fix was applied to the ext4 "dev" branch earlier today:


I would still want to wait at least a week or two before cherry-picking
it, in case of regressions.

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, on joining IRC



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

Processed: Re: linux: ext4 corruption with symlinks

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch fixed-upstream
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Added tag(s) patch and fixed-upstream.

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

Bug#1076021: playmidi: FTBFS

[Santiago Vila]

Package: playmidi
Version: 2.4debian-16
Severity: serious
Tags: ftbfs

This is to let everybody know that I'm aware that the QA upload I've just made
does not build ok. I'll try to fix this myself.

Thanks.

Bug#1072816: marked as done (sploitscan: Configuration files installed in Python modules directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 16:49:29 +
with message-id 
and subject line Bug#1072816: fixed in sploitscan 0.10.3-1
has caused the Debian Bug report #1072816,
regarding sploitscan: Configuration files installed in Python modules directory
to be marked as done.

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

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


-- 
1072816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sploitscan
Version: 0.9.1-1
Severity: serious

Hi,

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).

Best regards,

Peter
--- End Message ---
--- Begin Message ---
Source: sploitscan
Source-Version: 0.10.3-1
Done: Josenilson Ferreira da Silva 

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

Debian distribution maintenance software
pp.
Josenilson Ferreira da Silva  (supplier of updated 
sploitscan 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, 09 Jul 2024 10:39:03 -0300
Source: sploitscan
Architecture: source
Version: 0.10.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Josenilson Ferreira da Silva 
Closes: 1072816 1074476 1074771
Changes:
 sploitscan (0.10.3-1) unstable; urgency=medium
 .
   [ Dmitry Shachnev ]
   * Use links file to symlink config.json
 .
   [ Josenilson Ferreira da Silva ]
   * New upstream version 0.10.3 (Closes: #1074476, #1074771)
   * debian/rules: Removed unnecessary command
   * debian/sploitscan.install:
  Configuration file moved to /etc directory (Closes:  #1072816 )
   * debian/sploitscan.links: Changed symbolic link
Checksums-Sha1:
 451dfd84a05759f45ba8df4162d5c6051ea8da07 2111 sploitscan_0.10.3-1.dsc
 c4204a43ad4fc1778abbf8b3bf562653e160ffa9 34983 sploitscan_0.10.3.orig.tar.gz
 8916d1175b056bc52477c9723e9fac4596f77bf9 3268 sploitscan_0.10.3-1.debian.tar.xz
 65ecccd4d7af7c37a95f6a0455caeed7ff5964e7 9934 
sploitscan_0.10.3-1_source.buildinfo
Checksums-Sha256:
 82fe339f955bca0c3efaca7c70163b3bd99f49e04ce18c42979520a410501b30 2111 
sploitscan_0.10.3-1.dsc
 9c8490e2a75f3073412fdb311a6029258e3961decdbf8bf9bce5ef03c980e98d 34983 
sploitscan_0.10.3.orig.tar.gz
 099dc5c86113e65e853d71ff53dd7ae3e8c3d59b398b0389e79315f953ad4658 3268 
sploitscan_0.10.3-1.debian.tar.xz
 b251ace422c819597cf679220415b241bd91839993ec6ea1e6b9a171ebcc0b53 9934 
sploitscan_0.10.3-1_source.buildinfo
Files:
 52bb9e1990a5cc95e14a953a64dfa651 2111 misc optional sploitscan_0.10.3-1.dsc
 517031b6ecddb9fad3506588ebc4e5ab 34983 misc optional 
sploitscan_0.10.3.orig.tar.gz
 5daa012f1b07039db201d3f33e174b56 3268 misc optional 
sploitscan_0.10.3-1.debian.tar.xz
 956ea345508aae2ba7ab9e1d249a654d 9934 misc optional 
sploitscan_0.10.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmaNZ2cACgkQB6n1YjE0
Rs2SfhAApFEetxY2+XtQL4UhMFJNmvDS7S1dFdhBtQRcyyR4Qn/UOG5Ul/KCBXET
ZmROdcGz+rOXr95g36JxH+D5Ef2j09dvbM9E+1LXN3p8RTUzQjx/zi2D71vsVzZ6
wN22ZLb6nXlUMv09uhe+0MzU90hKPc22JRU4Nbt02T0sEcTZJ8S4GveQjE9RvaGl
TW95VP/T60UjGxZyQ8EspGTi2RJMC8PZtinL4wG5SQvfvOVy/woghW3M13JRHkJu
WNPDWkwgSsc5XWE0hg7yP6ZfdcGF+q9jouySGu2jffJrz4InOdIOFcb42NTcUIDW
1PFe0a862kWVJx+Jm/hILreAXqGkR9L+5asQJONItErqfDVybtPbkYEM2xBmFobq
DUvynsMgcaKpmojXzoqJljmobCPBEZvv2DNB0eO7gawqQGcYcYk4pZK6So0yNvnE
m6T8xdp3TA+28mp4Or0cC6OBFCQOHt6eKevEaV6VT/grwdDJlfwZQ6eYF0C/psRu
2Vpy8BP87p+k/HWcChKkolv3F9UwelAVaQZr8LnsaJ4Kg15QmSkbXRfK7z7HlWYN
+HNnypOkBEuBY3Dfwh9Np72XjbEyRgTnWMOmnVPmhi0TudF04+jE+PXHvNLHkuLP
rIGIIBxTJC27xBkZTeShwWvB37BQWrzlqLVyA5/XE+j9/DwLyeM=
=SV0+
-END PGP SIGNATURE-



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

Processed: closing 1075978

[Debian Bug Tracking System]

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

> close 1075978 0.7-2-2
Bug #1075978 [src:rmpi] rmpi: FTBFS on 32 bit architectures: configure: error: 
"Cannot find mpi.h header file"
The source 'rmpi' and version '0.7-2-2' do not appear to match any binary 
packages
Marked as fixed in versions rmpi/0.7-2-2.
Bug #1075978 [src:rmpi] rmpi: FTBFS on 32 bit architectures: configure: error: 
"Cannot find mpi.h header file"
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

[Agustin Martin]

El mar, 9 jul 2024 a las 14:26, Pierre-Elliott Bécue
() escribió:
>
> Feel free to upload it even not as a NMU. (you can add a Team Upload
> entry if you prefer)
>
> If you decide to NMU, don't --delay it. :)
>
> I have no time for owncloud-client now, but otherwise I'll try to look
> into it in August.

Thanks, Pierre-Elliot.

Just uploaded as team upload (took a bit longer since I missed that
source-only uploads to NEW are not allowed, and libowncloudsync0t64 is
NEW). Should be already in the NEW queue.

I have also created a merge request with the changes in salsa.debian.org.

I have left behind old libowncloudsync0.lintian-overrides (did not
delete it) and used new one (libowncloudsync0t64.lintian-overrides)
from original patch. Seems that lintian does not complain about what
old libowncloudsync0.lintian-overrides deals with, but you know better
about that.

Regards,

-- 
Agustin

Bug#1074706: [Pkg-pascal-devel] Bug#1074706: fpc: FTBFS: make[1]: *** [Makefile:9: de] Error 1

[Peter B]

On 02/07/2024 14:30, Lucas Nussbaum wrote:

Source: fpc
Version: 3.2.2+dfsg-33
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

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


Relevant part (hopefully):


snip

/usr/bin/make -C fpcsrc/utils/fpdoc/intl install 
INSTALL_PREFIX=/<>/debian/tmp/usr 
PP=/<>/fpcsrc/compiler/ppcx64
make[1]: Entering directory '/<>/fpcsrc/utils/fpdoc/intl'
msgfmt fpdoc.de.po dwriter.de.po -o fpdoc.de.mo
msgfmt: input file doesn't contain a header entry with a charset specification
make[1]: *** [Makefile:9: de] Error 1


The immediate cause of the build fail, is that msgfmt is called against 
de.po files which have no header.

Until recently, fpc built OK, and msgfmt did not appear in the build logs.

I have no idea why this problem has just appeared now,
but the build can be saved by commenting out the build of the de.mo files.

In d/rules
  #$(MAKE) -C fpcsrc/utils/fpdoc/intl install $(INSTALLOPTS)

and in d/fp-utils.install.in
  #usr/share/locale


Regards,
Peter

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Dirk Eddelbuettel]

On 9 July 2024 at 18:42, Adrian Bunk wrote:
| On Tue, Jul 09, 2024 at 10:34:43AM -0500, Dirk Eddelbuettel wrote:
| > 
| > Adrian,
| 
| Hi Dirk,
| 
| > Will the patch to configure.ac, with the build system as it is, ensure
| > autoconf is called or should I do that manually and hence also patch
| > configure?
| 
| just add the patch.

I reckoned as much.

| The autoreconf sequence is enabled by default since debhelper compat 10,
| and the package uses compat 13.

Very nice.

It's been uploaded (while killing some time at Frankfurt's airport).

Thanks again, Dirk

 
| > Dirk
| 
| cu
| Adrian

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1072535: puma: flaky autopkgtest -> now fails always

[Paul Gevers]

Hi,

On Mon, 3 Jun 2024 22:01:32 +0200 Paul Gevers  wrote:

I noticed that it regularly
fails.


It stopped being flaky and now always fails:

163s   1) Failure:
163s TestExampleCertExpiration#test_certs_not_expired 
[/tmp/autopkgtest-lxc.fbnre70j/downtmp/build.P6e/src/test/test_example_cert_expiration.rb:40]:
163s Cert puma/chain_cert/cert.crt has expired. Check the 
puma/chain_cert for a `.rb` with instructions on how to regenerate.


Paul

https://ci.debian.net/packages/p/puma/testing/amd64/48752836/


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Adrian Bunk]

On Tue, Jul 09, 2024 at 10:34:43AM -0500, Dirk Eddelbuettel wrote:
> 
> Adrian,

Hi Dirk,

> Will the patch to configure.ac, with the build system as it is, ensure
> autoconf is called or should I do that manually and hence also patch
> configure?

just add the patch.

The autoreconf sequence is enabled by default since debhelper compat 10,
and the package uses compat 13.

> Dirk

cu
Adrian

Processed: bug 1075814 is forwarded to https://github.com/PlotPyStack/PlotPy/issues/17

[Debian Bug Tracking System]

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

> forwarded 1075814 https://github.com/PlotPyStack/PlotPy/issues/17
Bug #1075814 [src:plotpy] plotpy: Fails to build on arm64
Set Bug forwarded-to-address to 
'https://github.com/PlotPyStack/PlotPy/issues/17'.
> thanks
Stopping processing here.

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

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Dirk Eddelbuettel]

Adrian,

Will the patch to configure.ac, with the build system as it is, ensure
autoconf is called or should I do that manually and hence also patch
configure?

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1076017: purity-off: autopkgtest regression on arm64: output keeps growing

[Paul Gevers]

Source: purity-off
Version: 0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, on arm64 it recently 
started to fill the entire disk with its output file in $AUTOPKGTEST_TMP 
(in testing and unstable, I haven't checked stable). On an otherwise 
empty host, there's 63 GB free, a watchdog kicks in at 95% disk usage 
and prevents most damage, but the current scheduled job for purity-off 
on arm64 never finishes. Can you please investigate the situation and 
fix it? The output only shows the first test passes: OK: 100.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


For now, I have added purity-off to our reject-list on arm64 to avoid 
more jobs to get scheduled.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1074519: marked as done (graph-tool: autopkgtest failure with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 14:49:03 +
with message-id 
and subject line Bug#1074519: fixed in graph-tool 2.71+ds-2
has caused the Debian Bug report #1074519,
regarding graph-tool: autopkgtest failure with Python 3.12
to be marked as done.

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

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


-- 
1074519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graph-tool
Version: 2.68+ds-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

graph-tool's autopkgtests fail with Python 3.12 [1].  I've copied what
I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/g/graph-tool/testing/amd64/


105s autopkgtest [22:10:51]: test command2: [---
105s g++ -O3 -fopenmp -std=gnu++17 -Wall -fPIC `pkg-config --cflags
--libs graph-tool-py3.11` -shared kcore.cc -o libkcore.so
105s Package graph-tool-py3.11 was not found in the pkg-config search path.
105s Perhaps you should add the directory containing `graph-tool-py3.11.pc'
105s to the PKG_CONFIG_PATH environment variable
105s Package 'graph-tool-py3.11', required by 'virtual:world', not found
105s In file included from /usr/include/boost/python/detail/prefix.hpp:13,
105s from /usr/include/boost/python/args.hpp:8,
105s from /usr/include/boost/python.hpp:11,
105s from kcore.cc:1:
105s /usr/include/boost/python/detail/wrap_python.hpp:57:11: fatal
error: pyconfig.h: No such file or directory
105s 57 | # include 
105s | ^~~~
105s compilation terminated.
105s make: *** [Makefile:6: libkcore.so] Error 1
105s make: Target 'ALL' not remade because of errors.
--- End Message ---
--- Begin Message ---
Source: graph-tool
Source-Version: 2.71+ds-2
Done: Jerome Benoit 

We believe that the bug you reported is fixed in the latest version of
graph-tool, 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.
Jerome Benoit  (supplier of updated graph-tool 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, 09 Jul 2024 13:52:04 +
Source: graph-tool
Architecture: source
Version: 2.71+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jerome Benoit 
Closes: 1074519
Changes:
 graph-tool (2.71+ds-2) unstable; urgency=medium
 .
   * Serious Bug Fix release, now soft-encode Python version in demos
 material (Closes: #1074519).
   * Debianization:
 - d/patches/*:
   - d/p/upstream-harden-demos-cppextensions-Makefile.patch, introduce;
 - d/adhoc/downloads/doc/demos/animation/Makefile, harden accordingly.
Checksums-Sha1:
 11fa669a1011f9361ac81f936344ddcc29f849bf 3828 graph-tool_2.71+ds-2.dsc
 82a09c80684067232447efce5a9a8671192c1e57 363736 
graph-tool_2.71+ds-2.debian.tar.xz
 7becb3e600a648c5286ecf79468a86d60c3db2d7 15647 
graph-tool_2.71+ds-2_source.buildinfo
Checksums-Sha256:
 fc14c38abe368ad846b8cfd666a3900932b0b4a553c1b951ff9761f45240b049 3828 
graph-tool_2.71+ds-2.dsc
 5e3b881a1977b04e2631564b1fc7ea993401b7f5f0fb2a32c91fc78453064bdd 363736 
graph-tool_2.71+ds-2.debian.tar.xz
 bfcb595ec1aa3d71eddc5dcc6e8e393129b9db8d0e2dd2c883ecacb973fc122f 15647 
graph-tool_2.71+ds-2_source.buildinfo
Files:
 54ac0d7eceba983cc5dd951347c9aa4b 3828 python optional graph-tool_2.71+ds-2.dsc
 23fc7a3e34737c2ee0d4038efaeb56c1 363736 python optional 
graph-tool_2.71+ds-2.debian.tar.xz
 5024e397a2deece0a27c7293b8010511 15647 python optional 
graph-tool_2.71+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAmaNSvAVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLK/kf/A3sdjCAdnbGn7bLO/j2zMmNcCaU
Bv5ZiBAzrJZBP4GulWvQwexL52XLkkI4qYiPesWZ+K8uHnl5NCnHTZjSJ8VRIvEY
543xXIPXszkG86WEPX+9Qoj6HQxnM0HhM8csgtf5zrIUHq8kWrsEf5cI676DD+vP
uSFI6kJUTU56JtvJyVcRA+R4fiS8hydnWnZmx6OVK9I0o2kz2SHprWdrmeJThjUz
TcOho6N6rd1ZJWcO0mbg3RTBD079vIjsuKWY1/ATleBw6G1meCY2kei1IeNpqYAE
xlPiOrf4aCZ/lP/l3iTzM9233b4YlLYFDN20cdZN4jMgm4dAUIMEtTzbfMVA7qfL
AepCus1fiH/7p7D6vAopgv3LJlhbSdkqHShdVomtBvA1oKC4aTKLViTNc96M1jAV

Processed: Bug#1074519 marked as pending in graph-tool

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074519 [src:graph-tool] graph-tool: autopkgtest failure with Python 3.12
Added tag(s) pending.

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

Processed: Bug#1074519 marked as pending in graph-tool

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074519 [src:graph-tool] graph-tool: autopkgtest failure with Python 3.12
Ignoring request to alter tags of bug #1074519 to the same tags previously set

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

Bug#1074519: marked as pending in graph-tool

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1074519 in graph-tool 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/graph-tool/-/commit/8241cb8ab067385a15d38fd4617f457acc583c1c


d/patches/python3.12: Fix autopkgtest failure. Closes: #1074519

Closes: #1074519


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074519

Bug#1074519: marked as pending in graph-tool

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1074519 in graph-tool 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/graph-tool/-/commit/8241cb8ab067385a15d38fd4617f457acc583c1c


d/patches/python3.12: Fix autopkgtest failure. Closes: #1074519

Closes: #1074519


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074519

Bug#1074742: marked as done (org-roam: FTBFS: make[2]: *** [Makefile:84: texi] Error 255)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 13:35:07 +
with message-id 
and subject line Bug#1074742: fixed in org-roam 2.2.2-2
has caused the Debian Bug report #1074742,
regarding org-roam: FTBFS: make[2]: *** [Makefile:84: texi] Error 255
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> 
> Error: wrong-type-argument (consp nil)
>   mapbacktrace(#f(compiled-function (evald func args flags) # -0x147e755222517960>))
>   debug-early-backtrace()
>   debug-early(error (wrong-type-argument consp nil))
>   []
>   apply(#f(compiled-function ( async subtreep visible-only body-only 
> ext-plist) "Export current buffer to a Texinfo file.\n\nIf narrowing is 
> active in the current buffer, only export its\nnarrowed part.\n\nIf a region 
> is active, export that region.\n\nA non-nil optional argument ASYNC means the 
> process should happen\nasynchronously.  The resulting file should be 
> accessible through\nthe `org-export-stack' interface.\n\nWhen optional 
> argument SUBTREEP is non-nil, export the sub-tree\nat point, extracting 
> information from the headline properties\nfirst.\n\nWhen optional argument 
> VISIBLE-ONLY is non-nil, don't export\ncontents of hidden elements.\n\nWhen 
> optional argument BODY-ONLY is non-nil, only write code\nbetween 
> \"\\begin{document}\" and \"\\end{document}\".\n\nEXT-PLIST, when provided, 
> is a property list with external\nparameters overriding Org default settings, 
> but still inferior to\nfile-local settings.\n\nReturn output file's name." 
> (interactive nil) #) nil)
>   org-texinfo-export-to-texinfo()
>   funcall-interactively(org-texinfo-export-to-texinfo)
>   command-execute(org-texinfo-export-to-texinfo)
>   command-line-1(("-f" "package-initialize" "-l" "ox-extra" "-l" 
> "ox-texinfo+" "--eval" "(or (require 'org-man nil t) (require 'ol-man))" 
> "org-roam.org" "--eval" "(ox-extras-activate '(ignore-headlines))" "--eval" 
> "(setq indent-tabs-mode nil)" "--eval" "(setq org-src-preserve-indentation 
> nil)" "--funcall" "org-texinfo-export-to-texinfo"))
>   command-line()
>   normal-top-level()
> make[2]: *** [Makefile:84: texi] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/org-roam_2.2.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=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: org-roam
Source-Version: 2.2.2-2
Done: Aymeric Agon-Rambosson 

We believe that the bug you reported is fixed in the latest version of
org-roam, 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.
Aymeric Agon-Rambosson  (supplier of updated org-roam 
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, 09 Jul 2024 14:47:42 +0200
Source: org-roam
Architecture: source
Version: 2.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Aymeric Agon-Rambosson 

Bug#1072847: fixed in lacme 0.8.3-1

[Sakari Ailus]

Hi Guilhem,

On Fri, Jul 05, 2024 at 11:15:31AM +0200, Guilhem Moulin wrote:
> Hi Sakari,
> 
> On Fri, 05 Jul 2024 at 08:23:56 +, Sakari Ailus wrote:
> > The removal of the intermediate certificates (or not including the current
> > ones) however is an issue as the server using the issued certificate still
> > needs to provide them to the clients.
> 
> The path pointed to by ‛certificate-chain’ contains the entire chain
> (excluding the root) as provided by Let's Encrypt.
> 
> > While it's certainly possible for the lacme user to obtain these
> > certificates directly from Let's encrypt, it'd be quite convenient to
> > continue to provide them in the lacme package itself, even if the package
> > does need to be updated from time to time for that reason.
> 
> Do you have a concrete usecase?  It appears Let's Encrypt has settled on
> intermediates with <2y lifetime (i.e., shorter than Debian Stable's
> lifetime), and earlier rotation is at their own discretion, so I don't
> see how we can reliably provide them as part of the source package.
> (Updating via (o)s-pu might be an option, but that would only work if
> the rotation is announced early enough ahead of the point release
> freeze.)

I believe the issues were actually caused by a local misconfiguration.
After fixing that, the certificate chain is deployed correctly. I
understand the intermediate certificate was present in lacme-provided CA
certificates previously and that's no longer the case.

Apologies for the noise.

-- 
Kind regards,

Sakari Ailus

Bug#1071952: marked as done (purple-lurch: FTBFS against libgcrypt 1.11)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 12:52:04 +
with message-id 
and subject line Bug#1071952: fixed in purple-lurch 0.7.0-2.1
has caused the Debian Bug report #1071952,
regarding purple-lurch: 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.)


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

Hello,

purple-lurch 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: purple-lurch
Source-Version: 0.7.0-2.1
Done: Andreas Metzler 

We believe that the bug you reported is fixed in the latest version of
purple-lurch, 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 Metzler  (supplier of updated purple-lurch 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, 09 Jul 2024 14:27:06 +0200
Source: purple-lurch
Architecture: source
Version: 0.7.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Andreas Metzler 
Closes: 1066710 1071952
Changes:
 purple-lurch (0.7.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing prototype to fix ftbfs. Closes: #1066710
   * Use pkg-config to locate libgcrypt. Closes: #1071952
Checksums-Sha1: 
 c63fc1bbf977b47ee429001327764482893aa66e 2253 purple-lurch_0.7.0-2.1.dsc
 a2981bc73e39774f8b1a7fab48ab54c1d4697333 13192 
purple-lurch_0.7.0-2.1.debian.tar.xz
Checksums-Sha256: 
 649423ca8685a29e0b2393a6495e2417de3e888ca75c0772d08cf9afe395c95d 2253 
purple-lurch_0.7.0-2.1.dsc
 7c0e8cdced65ce29a34af3cec11fb7290036ee4b3f912a1fc174da4e0470f171 13192 
purple-lurch_0.7.0-2.1.debian.tar.xz
Files: 
 0bda54f31a2d70b7460052d01aec4936 2253 net optional purple-lurch_0.7.0-2.1.dsc
 ab34067854a34ab3c1c75dec18015b8a 13192 net optional 
purple-lurch_0.7.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNLMcACgkQpU8BhUOC
FISIGA/8C5vFJwD9eb3jHe6j+e9j0cWwrrcouUadwNb4vlQdvzlsq4QL369ZcEc1
0AiXWRx48HhIIMncQp3miXPlN2+4NwZU9Gvz3MeMuu8Va6Iom1jPUOOSkq0eCnWp
zVhqF/BMk/IWI90hhw8DiwtXPv1UaOJdFDNI3GZ6RHavNndLp6Dr6Clg0sI8E4jl
ipJHu4Y+f1pvuzY8UJMgMmwRSWpe67a/KaVr5jrEcHvCKx/t6o8jURevNQfXavmL
SKmazjqCnLwZ+Y8SIkPIP+KTPEN/uYWWDKvCrLvQJAbGyslj5yvfYI/bAWTcvxmL
9lmKwpBkND862PDT7Xmp8EMHHg2EXRbeh8XX68LNP2jJh/5Au7WUTBVjmhp2a4EF
H4O2vkCHI7w3kGZwQk4g1tA4tGGwU4z5NGhx8bM0E5XrOtjpqjH42wG5Whs0/4Wg
E0g8fDWzkw221QnQP2NuULDzoWLJgFhQf+5K/t+NQMfAGg/oGNXgyUPfCJQ9czTc
w0Ryvra+dtHMke0morQQmNxiJJ8CGLncxsy53PtMyJjuqFkPI5GiqbM63V2eyAwB
166YHeYWZ8Bvm3aFn8yTRnxx6qGX2ViejyWafMUqnh4FyCB2r/xDr2TtMRDQ6Gbv
PTuRijFshnN+Jiw4/l2eX38F+k8/oTGRXFchId0syPlG+vaCTbE=
=7yRg
-END PGP SIGNATURE-



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

Bug#1066710: marked as done (purple-lurch: FTBFS: ./test/test_lurch_util.c:69:5: error: implicit declaration of function ‘lurch_util_axc_log_func’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 12:52:04 +
with message-id 
and subject line Bug#1066710: fixed in purple-lurch 0.7.0-2.1
has caused the Debian Bug report #1066710,
regarding purple-lurch: FTBFS: ./test/test_lurch_util.c:69:5: error: implicit 
declaration of function ‘lurch_util_axc_log_func’ 
[-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.)


-- 
1066710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: purple-lurch
Version: 0.7.0-2
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):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -std=c11 -Wall -g -Wstrict-overflow -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/libpurple 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
> -I/usr/include/libxml2 -I/usr/include/libomemo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -I/usr/include/axc 
> -I/usr/include/signal  -I/usr/include/signal  -I./headers/jabber -O0 -c 
> ./test/test_lurch_util.c -o build/test_lurch_util.o
> ./test/test_lurch_util.c: In function ‘test_lurch_util_axc_log_func_error’:
> ./test/test_lurch_util.c:69:5: error: implicit declaration of function 
> ‘lurch_util_axc_log_func’ [-Werror=implicit-function-declaration]
>69 | lurch_util_axc_log_func(AXC_LOG_ERROR, "test", 4, axc_ctx_p);
>   | ^~~
> ./test/test_lurch_api.c: In function 
> ‘test_lurch_api_status_im_handler_disabled’:
> ./test/test_lurch_api.c:831:92: warning: passing argument 4 of 
> ‘lurch_api_status_im_handler’ discards ‘const’ qualifier from pointer target 
> type [-Wdiscarded-qualifiers]
>   831 | lurch_api_status_im_handler(NULL, other_bare_jid, 
> lurch_api_status_im_handler_cb_mock, mock_user_data);
>   |   
>  ^~
> In file included from ./test/test_lurch_api.c:13:
> ./test/../src/lurch_api.h:128:163: note: expected ‘void *’ but argument is of 
> type ‘const char *’
>   128 | void lurch_api_status_im_handler(PurpleAccount * acc_p, const char * 
> contact_bare_jid, void (*cb)(int32_t err, lurch_status_t status, void * 
> user_data_p), void * user_data_p);
>   |   
>   
>~~~^~~
> ./test/test_lurch_api.c: In function 
> ‘test_lurch_api_status_im_handler_not_supported’:
> ./test/test_lurch_api.c:866:92: warning: passing argument 4 of 
> ‘lurch_api_status_im_handler’ discards ‘const’ qualifier from pointer target 
> type [-Wdiscarded-qualifiers]
>   866 | lurch_api_status_im_handler(NULL, other_bare_jid, 
> lurch_api_status_im_handler_cb_mock, mock_user_data);
>   |   
>  ^~
> ./test/../src/lurch_api.h:128:163: note: expected ‘void *’ but argument is of 
> type ‘const char *’
>   128 | void lurch_api_status_im_handler(PurpleAccount * acc_p, const char * 
> contact_bare_jid, void (*cb)(int32_t err, lurch_status_t status, void * 
> user_data_p), void * user_data_p);
>   |   
>   
>~~~^~~
> ./test/test_lurch_api.c: In function 
> ‘test_lurch_api_status_im_handler_no_session’:
> ./test/test_lurch_api.c:905:92: warning: passing argument 4 of 
> ‘lurch_api_status_im_handler’ discards ‘const’ qualifier from pointer target 
> type [-Wdiscarded-qualifiers]
>   905 | lurch_api_status_im_handler(NULL, other_bare_jid, 
> lurch_api_status_im_handler_cb_mock, mock_user_data);
>   |   
>  ^~
> 

Processed: Re: Bug#1069407: mercurial: FTBFS on arm64: dh_auto_test: error: make -j4 check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 4 --blacklist /<>/debian/mercurial.tes

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1052811 1074678 1069407
Bug #1052811 [src:mercurial] mercurial: test-http-bad-server.t intermittent 
failure
Bug #1052811 [src:mercurial] mercurial: test-http-bad-server.t intermittent 
failure
Marked as found in versions mercurial/6.7.2-1 and mercurial/6.7.4-1.
Bug #1069407 [src:mercurial] mercurial: FTBFS on arm64: dh_auto_test: error: 
make -j4 check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 4 
--blacklist /<>/debian/mercurial.test_blacklist" returned exit 
code 2
Severity set to 'important' from 'serious'
Marked as found in versions mercurial/6.4.4-2 and mercurial/6.7.4-1.
Added tag(s) upstream.
Bug #1074678 [src:mercurial] mercurial: FTBFS: dh_auto_test: error: make -j8 
check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 8 --blacklist 
/<>/debian/mercurial.test_blacklist" returned exit code 2
Severity set to 'important' from 'serious'
Marked as found in versions mercurial/6.4.4-2 and mercurial/6.7.2-1.
Added tag(s) upstream.
Merged 1052811 1069407 1074678

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

Bug#1069407: mercurial: FTBFS on arm64: dh_auto_test: error: make -j4 check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 4 --blacklist /<>/debian/mercurial.test_blacklist" re

[Julien Cristau]

Control: forcemerge 1052811 1074678 1069407

On Sat, Apr 20, 2024 at 14:08:55 +0200, Lucas Nussbaum wrote:

> Source: mercurial
> Version: 6.7.2-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on arm64.
> 
> 
[...]
> > --- /<>/tests/test-http-bad-server.t
> > +++ /<>/tests/test-http-bad-server.t.err
> > @@ -42,7 +42,7 @@
> >$ cat hg.pid > $DAEMON_PIDS
> >  
> >$ hg clone http://localhost:$HGPORT/ clone
> > -  abort: error: (\$ECONNRESET\$|\$EADDRNOTAVAIL\$) (re)
> > +  abort: error: Connection refused
> >[100]
> >  
> >  (The server exits on its own, but there is a race between that and 
> > starting a new server.
> > 
> > ERROR: test-http-bad-server.t output changed

On Tue, Jul  2, 2024 at 14:47:34 +0200, Lucas Nussbaum wrote:

> Source: mercurial
> Version: 6.7.4-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240702 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
[...]
> > --- /<>/tests/test-http-bad-server.t
> > +++ /<>/tests/test-http-bad-server.t.err
> > @@ -42,7 +42,7 @@
> >$ cat hg.pid > $DAEMON_PIDS
> >  
> >$ hg clone http://localhost:$HGPORT/ clone
> > -  abort: error: (\$ECONNRESET\$|\$EADDRNOTAVAIL\$) (re)
> > +  abort: error: Connection refused
> >[100]
> >  
> >  (The server exits on its own, but there is a race between that and 
> > starting a new server.
> > 
> > ERROR: test-http-bad-server.t output changed

You filed this before; merging.

Cheers,
Julien

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Michael Tokarev]

09.07.2024 15:29, Christian Marillat пишет:

On 09 juil. 2024 15:25, Michael Tokarev  wrote:


09.07.2024 15:23, Christian Marillat wrote:

On 09 juil. 2024 13:18, Michael Tokarev  wrote:
[...]


I don't know what "NIC support is missing" means.  Qemu can't be built
without support for networking.  The -nic option is obsolete for a long
time, that's true, but it works still.

Missing network card support.


You gave no additional information here.  I already read the same in your
first email, and I can't understand it.  I also wrote back that the above
command parameters works just fine on my system with qemu 9.0.0+ds-1.
There's no need for this ping-pong, - if you want the issue to be fixed,
you have to provide the information requested, instead of repeating the
same information as before.

I expect to see the same output with 1:8.2.5+ds-2 when qemu 9 return
nothing.


I'll keep this bug report hanging there for now, requesting for more info
about the original issue.  Unless such info will be available, I'll just
close it so it doesn't dusturb my work, - because in the way it now is,
it's useless.


Last time I'll report a bug against qemu. It's a shame.


Indeed it is a shame that you can't provide info requested 3 times.
Thank you for not filing more useless bug reports in the future.

/mjt


ristian


--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Christian Marillat]

On 09 juil. 2024 15:25, Michael Tokarev  wrote:

> 09.07.2024 15:23, Christian Marillat wrote:
>> On 09 juil. 2024 13:18, Michael Tokarev  wrote:
>> [...]
>> 
> I don't know what "NIC support is missing" means.  Qemu can't be built
> without support for networking.  The -nic option is obsolete for a long
> time, that's true, but it works still.
 Missing network card support.
>>>
>>> You gave no additional information here.  I already read the same in your
>>> first email, and I can't understand it.  I also wrote back that the above
>>> command parameters works just fine on my system with qemu 9.0.0+ds-1.
>>> There's no need for this ping-pong, - if you want the issue to be fixed,
>>> you have to provide the information requested, instead of repeating the
>>> same information as before.
>> I expect to see the same output with 1:8.2.5+ds-2 when qemu 9 return
>> nothing.
>
> I'll keep this bug report hanging there for now, requesting for more info
> about the original issue.  Unless such info will be available, I'll just
> close it so it doesn't dusturb my work, - because in the way it now is,
> it's useless.

Last time I'll report a bug against qemu. It's a shame.

ristian

Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

[Pierre-Elliott Bécue]

Hey,

Agustin Martin  wrote on 09/07/2024 at 09:48:14+0200:

> On Fri, Jun 28, 2024 at 12:58:52PM +0200, Andreas Beckmann wrote:
>> Control: found -1 5.2.1.13040+dfsg-2
>> 
>> On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin 
>> wrote:
>> > On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott Bécue wrote:
>> > > close 1063190 > thanks
>> > 
>> > Hi, Pierre-Elliott
>> > 
>> > owncloud-client seems still not in testing because of #1063190.
>> > 
>> > Missing version in bug closing?
>> 
>> The 5.x uploads have reverted the t64 renaming of libowncloudsync0 to
>> libowncloudsync0t64 without any explanation why the transition would not be
>> needed for this package.
>> The t64 nmu needs to be reinstated before this package can migrate to
>> testing.
>
> Hi,
>
> Thanks for the clarification.
>
> Seems that qt6 transition was handled in experimental in parallel to t64
> changes and that t64 stuff went finally missing when upgrading
> owncloud-client from experimental.
>
> I am attaching a possible patch for current owncloud-client 
> 5.2.1.13040+dfsg-2. It is based on Lucas and Benjamin patches and
> (hopefully) updated for current owncloud-client package. This patch
> does not include the associated debian/changelog entry.
>
> Hope this helps.

Feel free to upload it even not as a NMU. (you can add a Team Upload
entry if you prefer)

If you decide to NMU, don't --delay it. :)

I have no time for owncloud-client now, but otherwise I'll try to look
into it in August.

-- 
PEB


signature.asc
Description: PGP signature

Bug#1073312: marked as done (libxslt: FTBFS: extensions.c:392:33: error: implicit declaration of function ‘getenv’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 12:24:23 +
with message-id 
and subject line Bug#1073312: fixed in libxslt 1.1.35-1.1
has caused the Debian Bug report #1073312,
regarding libxslt: FTBFS: extensions.c:392:33: error: implicit declaration of 
function ‘getenv’ [-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.)


-- 
1073312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxslt
Version: 1.1.35-1
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. -I..  
> -I.. -I../libxslt -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 
> -Wall -Wextra -Wformat=2 -Wmissing-format-attribute -Wshadow -c -o extra.lo 
> extra.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../libxslt -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 -Wall -Wextra -Wformat=2 
> -Wmissing-format-attribute -Wshadow -c extensions.c  -fPIC -DPIC -o 
> .libs/extensions.o
> extensions.c: In function ‘xsltExtModuleRegisterDynamic’:
> extensions.c:392:33: error: implicit declaration of function ‘getenv’ 
> [-Werror=implicit-function-declaration]
>   392 | ext_directory = (xmlChar *) getenv("LIBXSLT_PLUGINS_PATH");
>   | ^~
> extensions.c:34:1: note: ‘getenv’ is defined in header ‘’; did you 
> forget to ‘#include ’?
>33 | #include "extensions.h"
>   +++ |+#include 
>34 | 
> extensions.c:392:21: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
>   392 | ext_directory = (xmlChar *) getenv("LIBXSLT_PLUGINS_PATH");
>   | ^
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I.. -I../libxslt -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 
> -Wall -Wextra -Wformat=2 -Wmissing-format-attribute -Wshadow -c -o 
> functions.lo functions.c
> numbers.c: In function ‘xsltNumberFormatTokenize’:
> numbers.c:350:5: warning: ‘xmlStringCurrentChar’ is deprecated 
> [-Wdeprecated-declarations]
>   350 | while (! (IS_LETTER(val=xmlStringCurrentChar(NULL, format+ix, 
> )) ||
>   | ^
> In file included from numbers.c:22:
> /usr/include/libxml2/libxml/parserInternals.h:576:33: note: declared here
>   576 | XMLPUBFUN int   xmlStringCurrentChar
> (xmlParserCtxtPtr ctxt,
>   | ^~~~
> numbers.c:350:5: warning: ‘xmlStringCurrentChar’ is deprecated 
> [-Wdeprecated-declarations]
>   350 | while (! (IS_LETTER(val=xmlStringCurrentChar(NULL, format+ix, 
> )) ||
>   | ^
> /usr/include/libxml2/libxml/parserInternals.h:576:33: note: declared here
>   576 | XMLPUBFUN int   xmlStringCurrentChar
> (xmlParserCtxtPtr ctxt,
>   | ^~~~
> numbers.c:350:5: warning: ‘xmlStringCurrentChar’ is deprecated 
> [-Wdeprecated-declarations]
>   350 | while (! (IS_LETTER(val=xmlStringCurrentChar(NULL, format+ix, 
> )) ||
>   | ^
> /usr/include/libxml2/libxml/parserInternals.h:576:33: note: declared here
>   576 | XMLPUBFUN int   xmlStringCurrentChar
> (xmlParserCtxtPtr ctxt,
>   | ^~~~
> numbers.c:350:5: warning: ‘xmlStringCurrentChar’ is deprecated 
> [-Wdeprecated-declarations]
>   350 | while (! (IS_LETTER(val=xmlStringCurrentChar(NULL, format+ix, 
> )) ||
>   | ^
> /usr/include/libxml2/libxml/parserInternals.h:576:33: note: declared here
>   576 | XMLPUBFUN int   xmlStringCurrentChar
> (xmlParserCtxtPtr ctxt,
>   | ^~~~
> numbers.c:350:5: warning: ‘xmlStringCurrentChar’ is 

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Christian Marillat]

On 09 juil. 2024 13:37, Michael Tokarev  wrote:

> 09.07.2024 13:18, Michael Tokarev wrote:
> ..>> -net nic,model=help should display a list of available network devices.
>> If you want this to happen, I suggest you to open bug report in the
>> upstream qemu issue tracker.  I definitely wont add debian-specific
>> code to display help for an obsolete option in qemu.
>> 
>>> All these command line options come from the manpage.
>> No, you're wrong: -net nic,model=help is not documented in the
>> manpage.
>
> I stand corrected, it's me who's wrong here.  This exact command is
> documented in the manpage:
>
>  Use -net nic,model=help for a list of available devices for your target.
>
> Obviously the manpage needs correction here.  It's broken for a long time.

Not only the man page. qemu-system-ppc64 -help display -nic and -net. Al
so the same from the online documentation.

https://www.qemu.org/docs/master/system/invocation.html#hxtool-5

Christian

Bug#1071937: marked as done (libxslt: FTBFS against libgcrypt 1.11)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 12:24:23 +
with message-id 
and subject line Bug#1071937: fixed in libxslt 1.1.35-1.1
has caused the Debian Bug report #1071937,
regarding libxslt: 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.)


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

Hello,

libxslt 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: libxslt
Source-Version: 1.1.35-1.1
Done: Andreas Metzler 

We believe that the bug you reported is fixed in the latest version of
libxslt, 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 Metzler  (supplier of updated libxslt 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, 09 Jul 2024 13:56:17 +0200
Source: libxslt
Architecture: source
Version: 1.1.35-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Andreas Metzler 
Closes: 1071937 1073312
Changes:
 libxslt (1.1.35-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing #include  to fix FTFBS. Closes: #1073312
   * Use pkg-config to locate libgcrypt. Closes: #1071937
Checksums-Sha1: 
 4443c6270d651254b96bea2fd6aa0b47eaf04cfb 2163 libxslt_1.1.35-1.1.dsc
 896608932e701530e3b2618dd6d82e46809be085 22212 libxslt_1.1.35-1.1.debian.tar.xz
Checksums-Sha256: 
 102a6976eb833e719d34339e4a8346553d89325b8850c4fad0942a58aad03abe 2163 
libxslt_1.1.35-1.1.dsc
 6e7107620dc85c9d16e2650297cb1f86fe3e38ad0ee8d646e90fc3608f522eaf 22212 
libxslt_1.1.35-1.1.debian.tar.xz
Files: 
 d0d37cbd26e67fb6c645482b4371f63d 2163 text optional libxslt_1.1.35-1.1.dsc
 81a1589bb4985a17f60f665209a64a75 22212 text optional 
libxslt_1.1.35-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNJxcACgkQpU8BhUOC
FIRlSxAAlZeuGoqXHIXdIQUDwCtVRQaZVv16HJTRaHSD8m/KJ+i10GaJoZTEinkn
T80sjP1px3042Rnz8c5u8SqmzQo1CuUCuJ6WlylvCHUaMpSRHkcOo7AhDZZu8UmY
+g8hVZHZy5AS89VPeKzMXWOOaLxE1pqhUagafqsgVC64+zEPNexaP/PUUmfYbCq2
sJbrxi/TtfpmvDA0QYE6yRBvyHSRjxmzvjGwppvzKmDKCfaYwcofDS/3ZJgVOm19
kvnNqlmK3mfccwn22gTKu+p1FMzz8Dt8tDaAVYQ/dV+5BlwRFY6q+6QS9hO5tnrH
CRpyznDYDFdap137wX2ulq85bwGzmb+G/bQZncaOX7O/q24QA96xmAKf1ozWgSj3
U3gkefSCXbYLtUlPlIxHluA2F3x6b+hzBGx+QqEDfVU8bhjniVksQ4mI0zEFwO7B
8rVOz/hoT3jl6DWOoLQ7P2RjZl9j8X336LpfWBh6+4YmbvEVxUMVm8tuv1jcCEeC
k7kZyS7Kg3/95jrd/XrWiZFSipuXAdxYiJmOLTBUwU/wuY8w5Dq7PvIVqhNTFbdn
1SH5TAtT6RzraeK1hhuETZpLh3tYc3j+I9hGw3oMCdS215FmR/3ZjViiecc0NvMR
IVN8CnKqnZF88rxYucvvjXw9K1bTvWiwa/TQkN9z4JPjMxR7rT4=
=N0Oq
-END PGP SIGNATURE-



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

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Michael Tokarev]

09.07.2024 15:23, Christian Marillat wrote:

On 09 juil. 2024 13:18, Michael Tokarev  wrote:

[...]


I don't know what "NIC support is missing" means.  Qemu can't be built
without support for networking.  The -nic option is obsolete for a long
time, that's true, but it works still.

Missing network card support.


You gave no additional information here.  I already read the same in your
first email, and I can't understand it.  I also wrote back that the above
command parameters works just fine on my system with qemu 9.0.0+ds-1.
There's no need for this ping-pong, - if you want the issue to be fixed,
you have to provide the information requested, instead of repeating the
same information as before.


I expect to see the same output with 1:8.2.5+ds-2 when qemu 9 return
nothing.


I'll keep this bug report hanging there for now, requesting for more info
about the original issue.  Unless such info will be available, I'll just
close it so it doesn't dusturb my work, - because in the way it now is,
it's useless.

Thanks,

/mjt

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Christian Marillat]

On 09 juil. 2024 13:18, Michael Tokarev  wrote:

[...]

>>> I don't know what "NIC support is missing" means.  Qemu can't be built
>>> without support for networking.  The -nic option is obsolete for a long
>>> time, that's true, but it works still.
>> Missing network card support.
>
> You gave no additional information here.  I already read the same in your
> first email, and I can't understand it.  I also wrote back that the above
> command parameters works just fine on my system with qemu 9.0.0+ds-1.
> There's no need for this ping-pong, - if you want the issue to be fixed,
> you have to provide the information requested, instead of repeating the
> same information as before.

I expect to see the same output with 1:8.2.5+ds-2 when qemu 9 return
nothing.

,
| $ qemu-system-ppc64 -net nic,model=help
| Available NIC models:
| e1000
| e1000-82544gc
| e1000-82545em
| e1000e
| i82550
| i82551
| i82557a
| i82557b
| i82557c
| i82558a
| i82558b
| i82559a
| i82559b
| i82559c
| i82559er
| i82562
| i82801
| igb
| ne2k_pci
| pcnet
| rtl8139
| sungem
| tulip
| virtio-net-pci
| virtio-net-pci-non-transitional
| virtio-net-pci-transitional
| vmxnet3
`

Christian

Bug#1072947: marked as done (dropbear: autopkgtest remote-unlocking is flaky)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 12:19:19 +
with message-id 
and subject line Bug#1072947: fixed in dropbear 2024.85-3
has caused the Debian Bug report #1072947,
regarding dropbear: autopkgtest remote-unlocking is flaky
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.)


-- 
1072947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dropbear 2024.85-2
Severity: serious
Justification: flaky debci is RC as per RT
User: debian...@lists.debian.org
Usertags: flaky

Dear Maintainer(s),

The remote-unlocking autopkgtest is flaky, and often requires a retry
to pass, with no other changes. As per RT, this is RC. Example:

https://ci.debian.net/packages/d/dropbear/testing/amd64/47506735/
https://ci.debian.net/packages/d/dropbear/testing/amd64/47426591/
https://ci.debian.net/packages/d/dropbear/testing/amd64/47261698/
https://ci.debian.net/packages/d/dropbear/testing/amd64/47105607/

887s Connection timed out during banner exchange
887s Connection to 127.0.0.1 port 10022 timed out
887s + rv=255
887s + [ 255 -ne 255 ]
887s + [ 1 -le 1 ]
887s + echo ERROR: Couldn't SSH into QEMU: maximum number of tries exceeded
887s ERROR: Couldn't SSH into QEMU: maximum number of tries exceeded
887s + exit 1
887s + kill 29110

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: dropbear
Source-Version: 2024.85-3
Done: Guilhem Moulin 

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated dropbear 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, 09 Jul 2024 12:07:08 +0200
Source: dropbear
Architecture: source
Version: 2024.85-3
Distribution: unstable
Urgency: medium
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Closes: 1072947
Changes:
 dropbear (2024.85-3) unstable; urgency=medium
 .
   * DEP-8: Mark remote-unlocking as flaky.  To be re-evaluated if/when the
 test runs on environment where KVM is available.  (Closes: #1072947)
   * d/t/remote-unlocking: Also install systemd-cryptsetup in the guest.  This
 is needed to unlock the swap device at boot time (not at initramfs stage).
Checksums-Sha1:
 653d736c720c3d8aabed723ab3418efcdb763962 2524 dropbear_2024.85-3.dsc
 3f3b5b850bfee2442831a51fa82b45031ce2577e 34908 dropbear_2024.85-3.debian.tar.xz
 6ee0988dfc033f2b57bd9fcae70b7cf18aaba8a8 6851 
dropbear_2024.85-3_amd64.buildinfo
Checksums-Sha256:
 c22ef5f96669385f645a9d8daf8357a62e05d7d183eae3d47362b64142b4e60a 2524 
dropbear_2024.85-3.dsc
 01708138132642c8595fa19f35fc1de57f7240654556e520a2996f5b1e4053cd 34908 
dropbear_2024.85-3.debian.tar.xz
 c4ff7a7c8871e7fc5dd39b562b07aa7529466330972d486b74d8fe16ee9db727 6851 
dropbear_2024.85-3_amd64.buildinfo
Files:
 e715622c8c99ba9343bb509922ad8cb3 2524 net optional dropbear_2024.85-3.dsc
 5b3776f3879920f62a6aea9379fd63da 34908 net optional 
dropbear_2024.85-3.debian.tar.xz
 b411baae6c3e707e78ee18635bfdc937 6851 net optional 
dropbear_2024.85-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmaNDuoACgkQ05pJnDwh
pVK2eQ/+O7olXfb0rCQe+tN8avaPX764Vrk0ItMqYTPAVwz34jOyU/yR2CZlnxGb
zRECFmmWiGm78lcbE+kK3C8cOqBlpxX56+UxwEoauxtMl0gzNM2WjIwCZqVcNivu
xqWy4QJWRX0E3WDBzfvLmJhJlBKjUNUBIWhmJLg0XRPdgBTWDxEDAPw/xS07+QZS
PAfFBaSgI6rl1fuNyztPzLkZ7BR06aMl+yfEfFW21FM4jlsfbqWeFNSpgk/LezjP
qRHB5ByAs9V07ZEq3JIGAl0d3U9ImGQPPkCL8GQoZEQxKRrUGbxf39Bd3m9XVhzv
HbQH8rAXNZSC+V/0rE/MZhs5vXWUA1x9vzp87OHX3jF4BQ3A29KczxBt1Q1TX//C
0rE+L+f01OCFbOgeRc8+p0WTzHTa7lnPpo9w2hUG0N6bona5wokCh6CkomcXqDBQ
0lCcZ0KgkHT6X0UghI/0BS+g9dMRAAG7z7Wxsiq/9TnJ6ZT8IsI4qf02v3m8B/H7
O4JosGHawqeXKfL86dbcftFFTK6E7LYrklbqmaa9ofReWqsizRjHIxOS6AQFhr2r
F5XbzM1iCRLKhXTsgT9zF8PLYu0CGUIF8o62wYjYmLPP59kH1GrPyp3DxkxWNt2j
7BnPGaBtkYcxHcEe7R0iHt8kr4TnjOLila5MJbADWwOtODaZPik=
=aJ3I
-END PGP SIGNATURE-



pgpc0ymVStEhh.pgp
Description: PGP signature
--- End 

Bug#1073465: marked as done (python-wsgi-intercept: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 11:50:17 +
with message-id 
and subject line Bug#1073465: fixed in python-wsgi-intercept 1.13.0-1
has caused the Debian Bug report #1073465,
regarding python-wsgi-intercept: FTBFS: tests failed
to be marked as done.

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

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


-- 
1073465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wsgi-intercept
Version: 1.9.3-5
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for i in 3.12 3.11 ; do \
>   PYMAJOR=`echo $i | cut -d'.' -f1` ; \
>   echo "===> Testing with python$i (python$PYMAJOR)" ; \
>   WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=$i PYTHONPATH=. python$i -m 
> pytest wsgi_intercept/tests ; \
> done
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python3.12 (python3)
> ===> Testing with python3.12 (python3)
> + WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=3.12 PYTHONPATH=. python3.12 -m 
> pytest wsgi_intercept/tests
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>
> collected 80 items
> 
> wsgi_intercept/tests/test_http_client.py .ss [  
> 8%]
> wsgi_intercept/tests/test_httplib2.py    [ 
> 18%]
> wsgi_intercept/tests/test_interceptor.py [ 
> 43%]
> wsgi_intercept/tests/test_module_interceptor.py ..   [ 
> 46%]
> wsgi_intercept/tests/test_requests.py .FFsF.ss   [ 
> 61%]
> wsgi_intercept/tests/test_response_headers.py .. [ 
> 63%]
> wsgi_intercept/tests/test_urllib.py ...ss[ 
> 75%]
> wsgi_intercept/tests/test_urllib3.py .FFF.ss [ 
> 88%]
> wsgi_intercept/tests/test_wsgi_compliance.py .   
> [100%]
> 
> === FAILURES 
> ===
> __ test_https 
> __
> 
> def test_https():
> with InstalledApp(wsgi_app.simple_app, host=HOST, port=443) as app:
> >   resp = 
> > requests.get('https://some_hopefully_nonexistant_domain:443/')
> 
> wsgi_intercept/tests/test_requests.py:57: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/requests/api.py:73: in get
> return request("get", url, params=params, **kwargs)
> /usr/lib/python3/dist-packages/requests/api.py:59: in request
> return session.request(method=method, url=url, **kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:589: in request
> resp = self.send(prep, **send_kwargs)
> /usr/lib/python3/dist-packages/requests/sessions.py:703: in send
> r = adapter.send(request, **kwargs)
> /usr/lib/python3/dist-packages/requests/adapters.py:667: in send
> resp = conn.urlopen(
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:770: in urlopen
> conn = self._get_conn(timeout=pool_timeout)
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:296: in _get_conn
> return conn or self._new_conn()
> /usr/lib/python3/dist-packages/urllib3/connectionpool.py:1071: in _new_conn
> return self.ConnectionCls(
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> .HTTPS_WSGIInterceptor 
> object at 0x7fc8ad095af0>
> args = ()
> kwargs = {'assert_fingerprint': None, 'assert_hostname': None, 'blocksize': 
> 16384, 'ca_cert_dir': None, ...}
> 
> def __init__(self, *args, **kwargs):
> if 'strict' in kwargs and sys.version_info > (3, 0):
> kwargs.pop('strict')
> kwargs.pop('socket_options', None)
> kwargs.pop('key_password', None)
> kwargs.pop('server_hostname', None)
> if sys.version_info > (3, 12):
> kwargs.pop('key_file', None)
> kwargs.pop('cert_file', None)
> >   WSGI_HTTPSConnection.__init__(self, *args, **kwargs)
> E   TypeError: HTTPSConnection.__init__() got an unexpected keyword 
> argument 

Bug#1073465: marked as pending in python-wsgi-intercept

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-wsgi-intercept/-/commit/060e069e5b5be48ac6d8cf106d96a3dc452bd642


Add support-urllib3-2.x.patch (Closes: #1073465).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073465

Processed: Bug#1073465 marked as pending in python-wsgi-intercept

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073465 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: tests 
failed
Added tag(s) pending.

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

Bug#1071933: marked as done (libccrtp: FTBFS against libgcrypt 1.11)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 11:34:11 +
with message-id 
and subject line Bug#1071933: fixed in libccrtp 2.0.9-4.1
has caused the Debian Bug report #1071933,
regarding libccrtp: 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.)


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

Hello,

libccrtp FTBFS against libgcrypt 1.11 which drops libgcrypt-config.  It
ships an outdated customized version of AM_PATH_LIBGCRYPT() called
AM_PATH_LIBGCRYPT_CCRTP in m4/libgcrypt_local.m4 that cannot handle the
removal of libgcrypt-config.

Replacing AM_PATH_LIBGCRYPT_CCRTP with upstream's AM_PATH_LIBGCRYPT
would probably help but I would suggest to simply 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: libccrtp
Source-Version: 2.0.9-4.1
Done: Andreas Metzler 

We believe that the bug you reported is fixed in the latest version of
libccrtp, 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 Metzler  (supplier of updated libccrtp 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, 09 Jul 2024 13:14:07 +0200
Source: libccrtp
Architecture: source
Version: 2.0.9-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Andreas Metzler 
Closes: 1071933
Changes:
 libccrtp (2.0.9-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Delete outdated (and renamed) copy of libgcrypt.m4 and use upstream macro
 instead to fix FTBFS against libgcrypt without libgcrypt-config.
 Closes: #1071933
Checksums-Sha1: 
 072fb951e08362b5a3e7c906acfe2f5031c25bb7 2135 libccrtp_2.0.9-4.1.dsc
 e6c44ded8a4730ea24ed614df437fbcaff1fb5ec 12424 libccrtp_2.0.9-4.1.debian.tar.xz
Checksums-Sha256: 
 0dd022a96c63b557e2fd066b43a8a6741b2a011ee50666385607befece350fa1 2135 
libccrtp_2.0.9-4.1.dsc
 4d601926f48ae7dd618b0aa5cbf47f5abc2d05b8094359a0e3d95b8561c994b2 12424 
libccrtp_2.0.9-4.1.debian.tar.xz
Files: 
 c258ec680f5a7ef4eac1f4d11c995bbc 2135 devel optional libccrtp_2.0.9-4.1.dsc
 f830af3f1d74c4dcfef90258bd119adc 12424 devel optional 
libccrtp_2.0.9-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNHb8ACgkQpU8BhUOC
FITvMQ//ShaUIVqkaoXeq+661CSgdwGYfMkY9DTARu3qRzcgq+QyV147MnjkScQ1
utJZgrrhpMNB6NTh5WYqzpc+AaM35FfczJz+feMVE9C/P7gb4dniyMzNywb08rhe
+csPbbXupCv0XX1l9Y+O9+UAbo60HEprUuXeLWbegUVEeuTrbZUTyJhckExKWga3
s1cOwYmzipA04zK/C3+dSJlidf8dklIAIrVbNwQOmgVBc6hktOr2Rv8SVqF2u+Di
VdfSLqTgV0myy0JEY3TfV/+xsUHoc3bRJb1ynIGR5LWcSEUgL9cCJkjE1sL+SMox
f1hoSoFmUsXKHOC1yfssrn+XKm38FOcTPdGpFPSm/3R2qnbyj9P158WjFQWcSJ4g
IIQ1to0Kn9J2+42+l/+cSqah7ClfCUxLR/Iy2FASSSzo97hPSc8d56BOIi+JjeQC
kZ3ymaPZc0jQPXYv734dP6gAKcKWoxEekewJyTX4t/1gIimU3nUpash3JP7zgK+G
X0uldcps0JU0We1+BbA3PQR3BD3d3Rh4VT9+pkkdLBp7xASLKwqb5ZbBoYOpTkHA
hxcb9LC46QaHkRewWmVaYhKAu5uSWi/MZ4dcRKf32BGEndyZrOwDRe+daCvJ2GbO
6M5QC0gt4ExbXMUXCdQS/h+3zz1ZqoIj0+Co69Tnnr2Fdka7Gwk=
=O7Ft
-END PGP SIGNATURE-



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

Processed: libccrtp: diff for NMU version 2.0.9-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1071933 + patch
Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11
Added tag(s) patch.
> tags 1071933 + pending
Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11
Added tag(s) pending.

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

Bug#1071933: libccrtp: diff for NMU version 2.0.9-4.1

[Andreas Metzler]

Control: tags 1071933 + patch
Control: tags 1071933 + pending

Dear maintainer,

I've prepared an NMU for libccrtp (versioned as 2.0.9-4.1) and
uploaded it to unstable.

Regards.
diff -Nru libccrtp-2.0.9/debian/changelog libccrtp-2.0.9/debian/changelog
--- libccrtp-2.0.9/debian/changelog	2024-05-03 20:35:11.0 +0200
+++ libccrtp-2.0.9/debian/changelog	2024-07-09 13:14:07.0 +0200
@@ -1,3 +1,12 @@
+libccrtp (2.0.9-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Delete outdated (and renamed) copy of libgcrypt.m4 and use upstream macro
+instead to fix FTBFS against libgcrypt without libgcrypt-config.
+Closes: #1071933
+
+ -- Andreas Metzler   Tue, 09 Jul 2024 13:14:07 +0200
+
 libccrtp (2.0.9-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff
--- libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff	1970-01-01 01:00:00.0 +0100
+++ libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff	2024-07-09 13:14:07.0 +0200
@@ -0,0 +1,117 @@
+Description: Delete outdated (and renamed) copy of libgcrypt.m4 to fix FTBFS
+ against libgcrypt without libgcrypt-config.
+Author: Andreas Metzler 
+Bug-Debian: https://bugs.debian.org/1071933
+Last-Update: 2024-07-09
+
+--- libccrtp-2.0.9.orig/m4/libgcrypt_local.m4
 /dev/null
+@@ -1,108 +0,0 @@
+-dnl Autoconf macros for libgcrypt
+-dnl   Copyright (C) 2002, 2004 Free Software Foundation, Inc.
+-dnl
+-dnl This file is free software; as a special exception the author gives
+-dnl unlimited permission to copy and/or distribute it, with or without
+-dnl modifications, as long as this notice is preserved.
+-dnl
+-dnl This file is distributed in the hope that it will be useful, but
+-dnl WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
+-dnl implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+-
+-
+-dnl AM_PATH_LIBGCRYPT([MINIMUM-VERSION,
+-dnl   [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND ]]])
+-dnl Test for libgcrypt and define LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS.
+-dnl MINIMUN-VERSION is a string with the version number optionalliy prefixed
+-dnl with the API version to also check the API compatibility. Example:
+-dnl a MINIMUN-VERSION of 1:1.2.5 won't pass the test unless the installed 
+-dnl version of libgcrypt is at least 1.2.5 *and* the API number is 1.  Using
+-dnl this features allows one to prevent build against newer versions of libgcrypt
+-dnl with a changed API.
+-dnl
+-AC_DEFUN([AM_PATH_LIBGCRYPT_CCRTP],
+-[ AC_ARG_WITH(libgcrypt-prefix,
+-AC_HELP_STRING([--with-libgcrypt-prefix=PFX],
+-   [prefix where LIBGCRYPT is installed (optional)]),
+- libgcrypt_config_prefix="$withval", libgcrypt_config_prefix="")
+-  if test x$libgcrypt_config_prefix != x ; then
+- if test x${LIBGCRYPT_CONFIG+set} != xset ; then
+-LIBGCRYPT_CONFIG=$libgcrypt_config_prefix/bin/libgcrypt-config
+- fi
+-  fi
+-
+-  AC_PATH_PROG(LIBGCRYPT_CONFIG, libgcrypt-config, no)
+-  tmp=ifelse([$1], ,1:1.2.0,$1)
+-  if echo "$tmp" | grep ':' >/dev/null 2>/dev/null ; then
+- req_libgcrypt_api=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\1/'`
+- min_libgcrypt_version=`echo "$tmp" | sed 's/\(.*\):\(.*\)/\2/'`
+-  else
+- req_libgcrypt_api=0
+- min_libgcrypt_version="$tmp"
+-  fi
+-
+-  AC_MSG_CHECKING(for LIBGCRYPT - version >= $min_libgcrypt_version)
+-  ok=no
+-  if test "$LIBGCRYPT_CONFIG" != "no" ; then
+-req_major=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-req_minor=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
+-req_micro=`echo $min_libgcrypt_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
+-libgcrypt_config_version=`$LIBGCRYPT_CONFIG --version`
+-major=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
+-minor=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
+-micro=`echo $libgcrypt_config_version | \
+-   sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
+-if test "$major" -gt "$req_major"; then
+-ok=yes
+-else 
+-if test "$major" -eq "$req_major"; then
+-if test "$minor" -gt "$req_minor"; then
+-   ok=yes
+-else
+-   if test "$minor" -eq "$req_minor"; then
+-   if test "$micro" -ge "$req_micro"; then
+- ok=yes
+-   fi
+-   fi
+-fi
+-fi
+-fi
+-  fi
+-  if test $ok = yes; then
+-AC_MSG_RESULT([yes ($libgcrypt_config_version)])
+-  else
+-AC_MSG_RESULT(no)
+-  

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Michael Tokarev]

09.07.2024 13:18, Michael Tokarev wrote:
..>> -net nic,model=help should display a list of available network devices.


If you want this to happen, I suggest you to open bug report in the
upstream qemu issue tracker.  I definitely wont add debian-specific
code to display help for an obsolete option in qemu.


All these command line options come from the manpage.


No, you're wrong: -net nic,model=help is not documented in the manpage.


I stand corrected, it's me who's wrong here.  This exact command is
documented in the manpage:

 Use -net nic,model=help for a list of available devices for your target.

Obviously the manpage needs correction here.  It's broken for a long time.

/mjt

--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1074739: marked as pending in hisat2

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/hisat2/-/commit/190ff5a5b4b017bbd57f210bb57e7ff89d79e595


d/patches/no_imp: add Python3.12 support.

Closes: #1074739


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074739

Processed: Bug#1074739 marked as pending in hisat2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074739 [src:hisat2] hisat2: FTBFS: make[1]: *** [debian/rules:39: 
override_dh_auto_build] Error 1
Added tag(s) pending.

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

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

[Paul Gevers]

Hi,

On 08-07-2024 10:07 p.m., Salvatore Bonaccorso wrote:

If you think it worth enough knowing if either is the case, I can
install the backports kernel again on the arm64 hosts, but obviously
that will be annoying for us. Please let me know if I should pursue this
(I would be expecting a bit quicker turn around on this bug if you say
yes now ;) ).


If you can test with the unstable kernel that would be great.  If you
are limited to only stable and backports, then you should probably wait
until 6.8 is in backports rather than testing the current 6.7 backport
that has only one of the fixes.


In the last weekly kernel team meeting we discussed about some of the
open issues, and we wondered if you were able to test again with
either a unstable kernel, or if that's not possible with the current
versions available trough backports?


Grr, sorry, I forgot about this.


Unfortunately for the 6.8.y series though the package is not yet out
of backports-new.


I'll see what I can do.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073316: marked as done (manaplus: FTBFS: resources/wallpaper.cpp:156:24: error: ‘time’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 10:21:24 +
with message-id 
and subject line Bug#1073316: fixed in manaplus 2.1.3.17-8
has caused the Debian Bug report #1073316,
regarding manaplus: FTBFS: resources/wallpaper.cpp:156:24: error: ‘time’ was 
not declared in this scope
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.)


-- 
1073316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manaplus
Version: 2.1.3.17-7
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):
> g++ -DPACKAGE_NAME=\"ManaPlus\" -DPACKAGE_TARNAME=\"manaplus\" 
> -DPACKAGE_VERSION=\"2.1.3.17\" -DPACKAGE_STRING=\"ManaPlus\ 2.1.3.17\" 
> -DPACKAGE_BUGREPORT=\"aka...@inbox.ru\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"manaplus\" -DVERSION=\"2.1.3.17\" -DHAVE_STDIO_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_SOCKET_H=1 
> -DHAVE_SYS_PARAM_H=1 -DSTDC_HEADERS=1 -DTIME_WITH_SYS_TIME=1 
> -DSELECT_TYPE_ARG1=int -DSELECT_TYPE_ARG234=\(fd_set\ \*\) 
> -DSELECT_TYPE_ARG5=\(struct\ timeval\ \*\) -DHAVE_VPRINTF=1 -DHAVE_FORK=1 
> -DHAVE_VFORK=1 -DHAVE_GETPAGESIZE=1 -DHAVE_WORKING_VFORK=1 
> -DHAVE_WORKING_FORK=1 -DHAVE_MMAP=1 -DHAVE_ATEXIT=1 -DHAVE_FLOOR=1 
> -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_MEMSET=1 -DHAVE_MKDIR=1 
> -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_DUP2=1 
> -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMCHR=1 -DHAVE_MEMMOVE=1 -DHAVE_POW=1 
> -DHAVE_PUTENV=1 -DHAVE_REALPATH=1 -DHAVE_SETENV=1 -DHAVE_SETLOCALE=1 
> -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_MUNMAP=1 -DHAVE_MALLOC_TRIM=1 
> -DHAVE_LIBINTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 
> -DHAVE_WCHAR_H=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 
> -DHAVE_LIBSDL2=1 -DHAVE_LIBSDL2_IMAGE=1 -DHAVE_LIBSDL2_TTF=1 
> -DHAVE_LIBSDL2_MIXER=1 -DHAVE_LIBSDL2_NET=1 -DUSE_INTERNALSDLGFX=1 
> -DHAVE_SDL_H=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1 
> -DHAVE_CURL_CURL_H=1 -DHAVE_LIBXML2=1 -DHAVE_LIBXML_XMLREADER_H=1 
> -DHAVE_LIBPNG=1 -DUSE_X11=1 -DHAVE_ARPA_INET_H=1 -DHAVE_FCNTL_H=1 
> -DHAVE_MALLOC_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIBGL=1 
> -DHAVE_LIBRT=1 -DHAVE_EXECINFO_H=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2  
> -I/usr/include/libpng16  -I/usr/include/SDL2 -D_REENTRANT -I/usr/include/SDL2 
> -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/webp  -I/usr/include/SDL2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 
> -I/usr/include/opus -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/libinstpatch-2 
> -pthread -D_REENTRANT -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  
> -I/usr/include/SDL2 -D_REENTRANT  -I/usr/include/SDL2 -D_REENTRANT 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/sysprof-6 -pthread   -I/usr/include/libxml2  
> -DPKG_DATADIR=\""/usr/share/manaplus/"\" -DLOCALEDIR=\""/usr/share/locale"\" 
> -Wall-DUSE_X11 -DENABLE_ASSERTS -DHAVE_EXECINFO -DHAVE_GLEXT  
> -DENABLE_LIBXML  -DUSE_OPENGL-DUSE_MUMBLE  -I./sdl2gfx -DUSE_SDL2  
> -DTMWA_SUPPORT -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -DUNITESTSDIR=\"testsdir\" -c -o 
> utils/manaplus-copynpaste.o `test -f 'utils/copynpaste.cpp' || echo 
> './'`utils/copynpaste.cpp
> resources/wallpaper.cpp: In static member function ‘static std::string 
> Wallpaper::getWallpaper(int, int)’:
> resources/wallpaper.cpp:156:24: error: ‘time’ was not declared in this scope
>   156 | srand(CAST_U32(time(nullptr)));
>   |^~~~
> resources/wallpaper.cpp:47:1: note: ‘time’ is defined in header ‘’; 
> did you forget to ‘#include ’?
>46 | #include "debug.h"
>   +++ |+#include 
>47 | 
> g++ -DPACKAGE_NAME=\"ManaPlus\" -DPACKAGE_TARNAME=\"manaplus\" 
> -DPACKAGE_VERSION=\"2.1.3.17\" -DPACKAGE_STRING=\"ManaPlus\ 2.1.3.17\" 

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Michael Tokarev]

09.07.2024 13:11, Christian Marillat wrote:

On 09 juil. 2024 12:53, Michael Tokarev  wrote:


Control: tag -1 + moreinfo unreproducible

09.07.2024 12:09, Christian Marillat wrote:

Package: qemu-system-ppc
Version: 1:9.0.1+ds-1
Severity: serious
Dear Maintainer,
My working configuration with 1:8.2.5+ds-2 was:
,
| -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap
`
Now with 1:9.0.1+ds-1 qemu-system-ppc64 doesn't start.
Apparently NIC support is missing:


I don't know what "NIC support is missing" means.  Qemu can't be built
without support for networking.  The -nic option is obsolete for a long
time, that's true, but it works still.


Missing network card support.


You gave no additional information here.  I already read the same in your
first email, and I can't understand it.  I also wrote back that the above
command parameters works just fine on my system with qemu 9.0.0+ds-1.
There's no need for this ping-pong, - if you want the issue to be fixed,
you have to provide the information requested, instead of repeating the
same information as before.


If the -nic option (and -net option) are obsolete why these options are
still documented in the manpage ?


Because -net is still supported.  This is unrelated to your original problem,
isn't it?

..

What do you expect here?  Is the problem you're reporting boils
down to missing support for -net nic,model=help (for obsolete
option -nic)?  If yes, perhaps the bug title is wrong?


-net nic,model=help should display a list of available network devices.


If you want this to happen, I suggest you to open bug report in the
upstream qemu issue tracker.  I definitely wont add debian-specific
code to display help for an obsolete option in qemu.


All these command line options come from the manpage.


No, you're wrong: -net nic,model=help is not documented in the manpage.

/mjt

--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Christian Marillat]

On 09 juil. 2024 12:53, Michael Tokarev  wrote:

> Control: tag -1 + moreinfo unreproducible
>
> 09.07.2024 12:09, Christian Marillat wrote:
>> Package: qemu-system-ppc
>> Version: 1:9.0.1+ds-1
>> Severity: serious
>> Dear Maintainer,
>> My working configuration with 1:8.2.5+ds-2 was:
>> ,
>> | -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap
>> `
>> Now with 1:9.0.1+ds-1 qemu-system-ppc64 doesn't start.
>> Apparently NIC support is missing:
>
> I don't know what "NIC support is missing" means.  Qemu can't be built
> without support for networking.  The -nic option is obsolete for a long
> time, that's true, but it works still.

Missing network card support.

If the -nic option (and -net option) are obsolete why these options are
still documented in the manpage ? 

> The above command (with additional parameters specifying image file and
> other stuff) works for me just fine.
>
>> ,
>> | $ sudo qemu-system-ppc64 -net nic,model=help
>
> Do not run qemu as root.
>
>> | qemu-system-ppc64: warning: hub port hub0port0 has no peer
>> | qemu-system-ppc64: warning: netdev hub0port0 has no peer
>> | qemu-system-ppc64: warning: requested NIC (#net062, model help)
>> | was not created (not supported by this machine?)
>> `
>
> What do you expect here?  Is the problem you're reporting boils
> down to missing support for -net nic,model=help (for obsolete
> option -nic)?  If yes, perhaps the bug title is wrong?

-net nic,model=help should display a list of available network devices.

All these command line options come from the manpage.

Christian

Processed: r-bioc-cwl: build-deps are satisfiable now

[Debian Bug Tracking System]

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

> notfound 1071884 1.18.0+ds-2
Bug #1071884 {Done: "Michael R. Crusoe" } [src:r-bioc-rcwl] 
r-bioc-rcwl: FTBFS: unsatisfiable build-dependencies
No longer marked as found in versions r-bioc-rcwl/1.18.0+ds-2.
>
End of message, stopping processing here.

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

Processed: Re: Bug#1076008: qemu-system-ppc: Missing NIC ?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #1076008 [qemu-system-ppc] qemu-system-ppc: Missing NIC ?
Added tag(s) moreinfo and unreproducible.

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

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Michael Tokarev]

Control: tag -1 + moreinfo unreproducible

09.07.2024 12:09, Christian Marillat wrote:

Package: qemu-system-ppc
Version: 1:9.0.1+ds-1
Severity: serious

Dear Maintainer,

My working configuration with 1:8.2.5+ds-2 was:

,
| -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap
`

Now with 1:9.0.1+ds-1 qemu-system-ppc64 doesn't start.
Apparently NIC support is missing:


I don't know what "NIC support is missing" means.  Qemu can't be built
without support for networking.  The -nic option is obsolete for a long
time, that's true, but it works still.

The above command (with additional parameters specifying image file and
other stuff) works for me just fine.


,
| $ sudo qemu-system-ppc64 -net nic,model=help


Do not run qemu as root.


| qemu-system-ppc64: warning: hub port hub0port0 has no peer
| qemu-system-ppc64: warning: netdev hub0port0 has no peer
| qemu-system-ppc64: warning: requested NIC (#net062, model help) was not 
created (not supported by this machine?)
`


What do you expect here?  Is the problem you're reporting boils
down to missing support for -net nic,model=help (for obsolete
option -nic)?  If yes, perhaps the bug title is wrong?

I can't get head or tail of this report.

Thanks,

/mjt

--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1073460: marked as done (python-zake: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 09:49:25 +
with message-id 
and subject line Bug#1073460: fixed in python-zake 0.2.2-7
has caused the Debian Bug report #1073460,
regarding python-zake: FTBFS: tests failed
to be marked as done.

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

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


-- 
1073460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-zake
Version: 0.2.2-6
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> # test_purge_clients_triggered is not deterministic. See #923827
> set -ex && for i in 3.12 3.11 ; do \
>   PYTHON=python$i python$i -m pytest -v -k "not 
> test_child_watch_no_create and not test_purge_clients_triggered" ; \
> done
> + PYTHON=python3.12 python3.12 -m pytest -v -k not test_child_watch_no_create 
> and not test_purge_clients_triggered
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0 -- 
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 0 items / 2 errors
> 
>  ERRORS 
> 
> __ ERROR collecting zake/tests/test_client.py 
> __
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'TestClient' object has no attribute 'runTest'. Did you 
> mean: 'subTest'?
> __ ERROR collecting zake/tests/test_client.py 
> __
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'TestMultiClient' object has no attribute 'runTest'. Did 
> you mean: 'subTest'?
> === warnings summary 
> ===
> zake/version.py:19
>   /<>/zake/version.py:19: DeprecationWarning: pkg_resources is 
> deprecated as an API. See 
> https://setuptools.pypa.io/en/latest/pkg_resources.html
> import pkg_resources
> 
> ../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:2871
> ../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:2871
>   /usr/lib/python3/dist-packages/pkg_resources/__init__.py:2871: 
> DeprecationWarning: Deprecated call to 
> `pkg_resources.declare_namespace('zope')`.
>   Implementing implicit namespace packages (as specified in PEP 420) is 
> preferred to `pkg_resources.declare_namespace`. See 
> https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
> declare_namespace(pkg)
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> === short test summary info 
> 
> ERROR zake/tests/test_client.py::TestClient - AttributeError: 'TestClient' 
> ob...
> ERROR zake/tests/test_client.py::TestMultiClient - AttributeError: 
> 'TestMulti...
> !!! Interrupted: 2 errors during collection 
> 
>  3 warnings, 2 errors in 0.32s 
> =
> make[1]: *** [debian/rules:26: override_dh_auto_test] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/python-zake_0.2.2-6_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 

Bug#1076008: qemu-system-ppc: Missing NIC ?

[Christian Marillat]

Package: qemu-system-ppc
Version: 1:9.0.1+ds-1
Severity: serious

Dear Maintainer,

My working configuration with 1:8.2.5+ds-2 was:

,
| -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap
`

Now with 1:9.0.1+ds-1 qemu-system-ppc64 doesn't start.
Apparently NIC support is missing:

,
| $ sudo qemu-system-ppc64 -net nic,model=help
| qemu-system-ppc64: warning: hub port hub0port0 has no peer
| qemu-system-ppc64: warning: netdev hub0port0 has no peer
| qemu-system-ppc64: warning: requested NIC (#net062, model help) was not 
created (not supported by this machine?)
`

Christian


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

Kernel: Linux 6.9.8-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 qemu-system-ppc depends on:
ii  libaio1t64  0.3.113-8
ii  libbpf1 1:1.4.3-1
ii  libc6   2.38-14
ii  libcapstone44.0.2-5.1
ii  libfdt1 1.7.0-2+b1
ii  libfuse3-3  3.14.0-6
ii  libglib2.0-0t64 2.80.4-1
ii  libgmp102:6.3.0+dfsg-2+b1
ii  libgnutls30t64  3.8.6-2
ii  libhogweed6t64  3.10-1
ii  libibverbs1 52.0-2
ii  libjpeg62-turbo 1:2.1.5-3
ii  libnettle8t64   3.10-1
ii  libnuma12.0.18-1
ii  libpixman-1-0   0.42.2-1+b1
ii  libpmem11.13.1-1.1+b1
ii  libpng16-16t64  1.6.43-5
ii  librdmacm1t64   52.0-2
ii  libsasl2-2  2.1.28+dfsg1-6
ii  libseccomp2 2.5.5-1
ii  libslirp0   4.8.0-1
ii  libudev1256.2-1
ii  liburing2   2.6-1
ii  libvdeplug2t64  4.0.1-5.1
ii  libzstd11.5.6+dfsg-1
ii  qemu-system-common  1:9.0.1+ds-1
ii  qemu-system-data1:9.0.1+ds-1
ii  zlib1g  1:1.3.dfsg+really1.3.1-1

Versions of packages qemu-system-ppc recommends:
ii  ipxe-qemu   1.0.0+git-20190125.36a4c85-5.1
pn  qemu-block-extra
ii  qemu-system-gui 1:9.0.1+ds-1
ii  qemu-system-modules-opengl  1:9.0.1+ds-1
pn  qemu-system-modules-spice   
ii  qemu-utils  1:9.0.1+ds-1
ii  seabios 1.16.3-2

Versions of packages qemu-system-ppc suggests:
pn  samba  
pn  vde2   

-- no debconf information

Bug#1074752: marked as done (cura: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 08:49:03 +
with message-id 
and subject line Bug#1074752: fixed in uranium 5.0.0-5
has caused the Debian Bug report #1074752,
regarding cura: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 
test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: invalid-imports
> 
> 1: Test command: /usr/bin/python3 "scripts/check_invalid_imports.py"
> 1: Working Directory: /<>
> 1: Test timeout computed to be: 1500
> test 2
>   Start  2: pytest-main
> 
> 2: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-main.xml" 
> "/<>/tests"
> 2: Working Directory: /<>/obj-x86_64-linux-gnu
> 2: Environment variables: 
> 2:  PYTHONPATH=/<>:/usr/share/uranium:
> 2: Test timeout computed to be: 1500
> test 3
>   Start  3: pytest-DigitalLibrary
> 
> 3: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-DigitalLibrary.xml"
>  "/<>/plugins/DigitalLibrary"
> 3: Working Directory: /<>/obj-x86_64-linux-gnu
> 3: Environment variables: 
> 3:  
> PYTHONPATH=/<>/plugins/DigitalLibrary:/<>:/usr/share/uranium:
> 3: Test timeout computed to be: 1500
> test 4
>   Start  4: pytest-FirmwareUpdateChecker
> 
> 4: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-FirmwareUpdateChecker.xml"
>  "/<>/plugins/FirmwareUpdateChecker"
> 4: Working Directory: /<>/obj-x86_64-linux-gnu
> 4: Environment variables: 
> 4:  
> PYTHONPATH=/<>/plugins/FirmwareUpdateChecker:/<>:/usr/share/uranium:
> 4: Test timeout computed to be: 1500
> test 5
>   Start  5: pytest-LegacyProfileReader
> 
> 5: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-LegacyProfileReader.xml"
>  "/<>/plugins/LegacyProfileReader"
> 5: Working Directory: /<>/obj-x86_64-linux-gnu
> 5: Environment variables: 
> 5:  
> PYTHONPATH=/<>/plugins/LegacyProfileReader:/<>:/usr/share/uranium:
> 5: Test timeout computed to be: 1500
> test 6
>   Start  6: pytest-PostProcessingPlugin
> 
> 6: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-PostProcessingPlugin.xml"
>  "/<>/plugins/PostProcessingPlugin"
> 6: Working Directory: /<>/obj-x86_64-linux-gnu
> 6: Environment variables: 
> 6:  
> PYTHONPATH=/<>/plugins/PostProcessingPlugin:/<>:/usr/share/uranium:
> 6: Test timeout computed to be: 1500
> test 7
>   Start  7: pytest-VersionUpgrade25to26
> 
> 7: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-VersionUpgrade25to26.xml"
>  "/<>/plugins/VersionUpgrade/VersionUpgrade25to26"
> 7: Working Directory: /<>/obj-x86_64-linux-gnu
> 7: Environment variables: 
> 7:  
> PYTHONPATH=/<>/plugins/VersionUpgrade/VersionUpgrade25to26:/<>:/usr/share/uranium:
> 7: Test timeout computed to be: 1500
> test 8
>   Start  8: pytest-VersionUpgrade26to27
> 
> 8: Test command: /usr/bin/python3 "-m" "pytest" 
> "--junitxml=/<>/obj-x86_64-linux-gnu/junit-pytest-VersionUpgrade26to27.xml"
>  "/<>/plugins/VersionUpgrade/VersionUpgrade26to27"
> 8: Working Directory: /<>/obj-x86_64-linux-gnu
> 8: Environment variables: 
> 8:  
> PYTHONPATH=/<>/plugins/VersionUpgrade/VersionUpgrade26to27:/<>:/usr/share/uranium:
> 8: Test timeout computed to be: 1500
>  1/14 Test  #1: invalid-imports ..   Passed0.19 sec
> test 

Bug#1074239: marked as done (cura: Cura fails to start)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 08:49:03 +
with message-id 
and subject line Bug#1074239: fixed in uranium 5.0.0-5
has caused the Debian Bug report #1074239,
regarding cura: Cura fails to start
to be marked as done.

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

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


-- 
1074239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cura
Version: 5.0.0-3
Severity: normal

Dear Maintainer,

 I installed the latest cura, typed 'cura' in a terminal window, and got a heap 
of debug messages, but no cura window.

 Some  messages that may be relevant:
2024-06-25 09:12:27,979 - ERROR - [MainThread] UM.PluginRegistry._findPlugin 
[730]: Exception: Import error loading module TrimeshReader
2024-06-25 09:12:27,980 - ERROR - [MainThread] UM.PluginRegistry._findPlugin 
[730]: Traceback (most recent call last):
2024-06-25 09:12:27,981 - ERROR - [MainThread] UM.PluginRegistry._findPlugin 
[730]:   File "/usr/lib/python3/dist-packages/UM/PluginRegistry.py", line 728, 
in _findPlugin
2024-06-25 09:12:27,981 - ERROR - [MainThread] UM.PluginRegistry._findPlugin 
[730]: module = imp.load_module(plugin_id, file, path, desc)  # type: 
ignore #MyPy gets the wrong output type from imp.find_module for some reason.
 2024-06-25 09:12:29,758 - ERROR - [MainThread] 
UM.Qt.QtApplication.createQmlComponent [606]: 
file:///usr/lib/cura/plugins/ModelChecker/ModelChecker.qml:8:1: Type 
UM.SimpleButton unavailable


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

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

Versions of packages cura depends on:
ii  cura-engine  1:5.0.0-4+b1
ii  fdm-materials5.0.0-2
ii  fonts-open-sans  1.11-2
ii  python3  3.11.8-1
ii  python3-certifi  2024.6.2-1
ii  python3-charon   5.0.0-4
ii  python3-cryptography 42.0.5-2
ii  python3-keyring  25.2.1-1
ii  python3-pynest2d 5.0.0-3+b1
ii  python3-pyqt66.7.0-1+b2
ii  python3-requests 2.32.3+dfsg-1
ii  python3-savitar  5.0.0-4.1+b1
ii  python3-sentry-sdk   1.40.4-3
ii  python3-serial   3.5-2
ii  python3-shapely  2.0.4-1
ii  python3-uranium  5.0.0-4
ii  qml6-module-qt-labs-folderlistmodel  6.6.2+dfsg-3
ii  qml6-module-qtqml-workerscript   6.6.2+dfsg-3
ii  qml6-module-qtquick-controls 6.6.2+dfsg-3
ii  qml6-module-qtquick-dialogs  6.6.2+dfsg-3
ii  qml6-module-qtquick-layouts  6.6.2+dfsg-3
ii  qml6-module-qtquick-templates6.6.2+dfsg-3
ii  qml6-module-qtquick-window   6.6.2+dfsg-3
ii  qt6-qpa-plugins  6.6.2+dfsg-8
ii  uranium-plugins  5.0.0-4

Versions of packages cura recommends:
ii  python3-zeroconf  0.132.2-2

cura suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: uranium
Source-Version: 5.0.0-5
Done: Gregor Riepl 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jul 2024 10:42:06 +0200
Source: uranium
Architecture: source
Version: 5.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Gregor Riepl 
Closes: 1074239 1074752
Changes:
 uranium (5.0.0-5) unstable; urgency=medium
 .
   * Replace 

Bug#1073458: marked as done (python-observabilityclient: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 08:40:15 +
with message-id 
and subject line Bug#1073458: fixed in python-observabilityclient 0.1.1-3
has caused the Debian Bug report #1073458,
regarding python-observabilityclient: FTBFS: tests failed
to be marked as done.

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

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


-- 
1073458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-observabilityclient
Version: 0.1.1-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[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-observabilityclient
> + echo python-observabilityclient
> + sed s/python-//
> + PY_MODULE_NAME=observabilityclient
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.12 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/command/develop.py:40: 
> EasyInstallDeprecationWarning: easy_install command is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` and ``easy_install``.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://github.com/pypa/setuptools/issues/917 for details.
> 
> 
> 
> !!
>   easy_install.initialize_options(self)
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/observabilityclient
> creating build/lib/observabilityclient/v1
> copying observabilityclient/v1/__init__.py -> build/lib/observabilityclient/v1
> copying observabilityclient/v1/rbac.py -> build/lib/observabilityclient/v1
> copying observabilityclient/v1/base.py -> build/lib/observabilityclient/v1
> copying observabilityclient/v1/client.py -> build/lib/observabilityclient/v1
> copying observabilityclient/v1/cli.py -> build/lib/observabilityclient/v1
> copying observabilityclient/v1/python_api.py -> 
> build/lib/observabilityclient/v1
> copying observabilityclient/__init__.py -> build/lib/observabilityclient
> copying observabilityclient/plugin.py -> build/lib/observabilityclient
> copying observabilityclient/client.py -> build/lib/observabilityclient
> copying observabilityclient/i18n.py -> build/lib/observabilityclient
> copying observabilityclient/prometheus_client.py -> 
> build/lib/observabilityclient
> creating build/lib/observabilityclient/utils
> copying observabilityclient/utils/__init__.py -> 
> build/lib/observabilityclient/utils
> copying observabilityclient/utils/metric_utils.py -> 
> build/lib/observabilityclient/utils
> running egg_info
> creating python_observabilityclient.egg-info
> writing 

Bug#1073457: marked as done (python-requests-mock: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 08:40:27 +
with message-id 
and subject line Bug#1073457: fixed in python-requests-mock 1.12.1-1
has caused the Debian Bug report #1073457,
regarding python-requests-mock: FTBFS: tests failed
to be marked as done.

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

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


-- 
1073457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-requests-mock
Version: 1.11.0-1
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for pyvers in `py3versions -vr 2>/dev/null` ; do \
>   PYTHONPATH=. python$pyvers -m pytest -v tests -k 'not test_simple and 
> not test_one'; \
> done
> + py3versions -vr
> + PYTHONPATH=. python3.12 -m pytest -v tests -k not test_simple and not 
> test_one
> = test session starts 
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0 -- 
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 5 items / 8 errors / 2 deselected / 3 selected
> 
>  ERRORS 
> 
>  ERROR collecting tests/test_adapter.py 
> 
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'SessionAdapterTests' object has no attribute 'runTest'. 
> Did you mean: 'subTest'?
>  ERROR collecting tests/test_custom_matchers.py 
> 
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'CustomMatchersTests' object has no attribute 'runTest'. 
> Did you mean: 'subTest'?
>  ERROR collecting tests/test_fixture.py 
> 
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'MockingTests' object has no attribute 'runTest'. Did you 
> mean: 'subTest'?
>  ERROR collecting tests/test_matcher.py 
> 
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'TestMatcher' object has no attribute 'runTest'. Did you 
> mean: 'subTest'?
>  ERROR collecting tests/test_mocker.py 
> _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'MockerTests' object has no attribute 'runTest'. Did you 
> mean: 'subTest'?
>  ERROR collecting tests/test_mocker.py 
> _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'MockerHttpMethodsTests' object has no attribute 
> 'runTest'. Did you mean: 'subTest'?
>  ERROR collecting tests/test_request.py 
> 
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'RequestTests' object has no attribute 'runTest'. Did you 
> mean: 'subTest'?
> ___ ERROR collecting tests/test_response.py 
> 
> 

Bug#1073381: marked as done (git-build-recipe: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 09 Jul 2024 08:40:38 +
with message-id 
and subject line Bug#1073381: fixed in python-testtools 2.7.2-1
has caused the Debian Bug report #1073381,
regarding git-build-recipe: FTBFS: dh_auto_test: error: pybuild --test -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.)


-- 
1073381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-build-recipe
Version: 0.3.7
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 '/<>'
> env -u LANGUAGE LC_ALL=C.UTF-8 dh_auto_test
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.11.9, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>
> collected 0 items / 13 errors
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'GitTestCase' object has no attribute 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'ResolveRevisionsTests' object has no attribute 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'DebUpstreamVariableTests' object has no attribute 
> 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'VersionExtractBaseTests' object has no attribute 
> 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'DebVersionVariableTests' object has no attribute 
> 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_deb_version.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'RecipeBranchTests' object has no attribute 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_functional.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'GitTestCase' object has no attribute 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_functional.py _
> /usr/lib/python3/dist-packages/testtools/testcase.py:241: in __init__
> test_method = self._get_test_method()
> /usr/lib/python3/dist-packages/testtools/testcase.py:696: in _get_test_method
> return getattr(self, method_name)
> E   AttributeError: 'FunctionalBuilderTests' object has no attribute 'runTest'
> _ ERROR collecting 
> .pybuild/cpython3_3.11/build/gitbuildrecipe/tests/test_recipe.py _
> 

Bug#1073460: marked as pending in python-zake

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-zake/-/commit/3ade1cbf2bf53ad17804b9eeb43265e896f8947d


Build-depends on testtools >= 2.7.2 (Closes: #1073460).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073460

Processed: Bug#1073460 marked as pending in python-zake

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073460 [src:python-zake] python-zake: FTBFS: tests failed
Added tag(s) pending.

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

Processed: Bug#1073458 marked as pending in python-observabilityclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073458 [src:python-observabilityclient] python-observabilityclient: 
FTBFS: tests failed
Added tag(s) pending.

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

Bug#1073458: marked as pending in python-observabilityclient

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/libs/python-observabilityclient/-/commit/fbc77764beda169cd5630d642fc0286fac9a8023


Build-depends on testtools >= 2.7.2 (Closes: #1073458).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073458

Processed: Bug#1073457 marked as pending in python-requests-mock

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073457 [src:python-requests-mock] python-requests-mock: FTBFS: tests 
failed
Added tag(s) pending.

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

Bug#1073457: marked as pending in python-requests-mock

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-requests-mock/-/commit/76a674d15a139cc144b4847a3567d1605fae45b7


Build-Depends on testtools >= 2.7.2 (Closes: #1073457).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073457

Processed: Bug#1073381 marked as pending in python-testtools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073381 [python3-testtools] git-build-recipe: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.

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

Bug#1073381: marked as pending in python-testtools

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-testtools/-/commit/eb9a5a7cc42665c474c66fc0a2717b7f645d79a3


d/changelog closes: #1073381


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073381

Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

[Agustin Martin]

On Fri, Jun 28, 2024 at 12:58:52PM +0200, Andreas Beckmann wrote:
> Control: found -1 5.2.1.13040+dfsg-2
> 
> On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin 
> wrote:
> > On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott Bécue wrote:
> > > close 1063190 > thanks
> > 
> > Hi, Pierre-Elliott
> > 
> > owncloud-client seems still not in testing because of #1063190.
> > 
> > Missing version in bug closing?
> 
> The 5.x uploads have reverted the t64 renaming of libowncloudsync0 to
> libowncloudsync0t64 without any explanation why the transition would not be
> needed for this package.
> The t64 nmu needs to be reinstated before this package can migrate to
> testing.

Hi,

Thanks for the clarification.

Seems that qt6 transition was handled in experimental in parallel to t64
changes and that t64 stuff went finally missing when upgrading
owncloud-client from experimental.

I am attaching a possible patch for current owncloud-client 
5.2.1.13040+dfsg-2. It is based on Lucas and Benjamin patches and
(hopefully) updated for current owncloud-client package. This patch
does not include the associated debian/changelog entry.

Hope this helps.

-- 
Agustin
>From 371901b1e6cf3fdbc3833e9c76a982a45b9dcfec Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo 
Date: Mon, 8 Jul 2024 16:36:30 +0200
Subject: [PATCH] Adapt previous nmu_owncloud-client.debdiff to new
 5.2.1.13040+dfsg-2 version (#1063190).

Original nmu_owncloud-client.debdiff by Lucas Kanashiro and Benjamin Drung.

Adapted for 5.2.1.13040+dfsg-2 using qt6.

Signed-off-by: Agustin Martin Domingo 
---
 debian/control   | 16 +---
 ...sync0.install => libowncloudsync0t64.install} |  0
 debian/libowncloudsync0t64.lintian-overrides |  3 +++
 3 files changed, 12 insertions(+), 7 deletions(-)
 rename debian/{libowncloudsync0.install => libowncloudsync0t64.install} (100%)
 create mode 100644 debian/libowncloudsync0t64.lintian-overrides

diff --git a/debian/control b/debian/control
index dbabf8c..39329f9 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,8 @@ Section: net
 Priority: optional
 Maintainer: ownCloud for Debian maintainers 
 Uploaders: Pierre-Elliott Bécue 
-Build-Depends: cmake,
+Build-Depends: dpkg-dev (>= 1.22.5),
+	   cmake,
debhelper-compat (= 13),
extra-cmake-modules,
libkdsingleapplication-qt6-dev,
@@ -22,7 +23,7 @@ Homepage: https://owncloud.org/sync-clients/
 Package: owncloud-client
 Architecture: any
 Multi-Arch: no
-Depends: libowncloudsync0 (= ${binary:Version}),
+Depends: libowncloudsync0t64 (= ${binary:Version}),
  libqt6sql6-sqlite,
  libqt6svg6,
  ${misc:Depends},
@@ -40,12 +41,13 @@ Description: folder synchronization with an ownCloud server - GUI
  owncloud-client provides the graphical client specialising in
  synchronizing with cloud storage provided by ownCloud.
 
-Package: libowncloudsync0
+Package: libowncloudsync0t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Replaces: libocsync0
-Breaks: libocsync0
+Replaces: libowncloudsync0, libocsync0
+Breaks: libowncloudsync0 (<< ${source:Version}), libocsync0
 Section: libs
 Description: ownCloudSync folder synchronization - libraries
  The ownCloudSync system lets you always have your latest files wherever
@@ -60,7 +62,7 @@ Description: ownCloudSync folder synchronization - libraries
 Package: libowncloudsync-dev
 Architecture: any
 Multi-Arch: same
-Depends: libowncloudsync0 (= ${binary:Version}), ${misc:Depends}
+Depends: libowncloudsync0t64 (= ${binary:Version}), ${misc:Depends}
 Replaces: libocsync-dev
 Breaks: libocsync-dev
 Section: libdevel
@@ -88,7 +90,7 @@ Description: ownCloudSync folder synchronization - shared data
 
 Package: owncloud-client-cmd
 Architecture: any
-Depends: libowncloudsync0 (= ${binary:Version}),
+Depends: libowncloudsync0t64 (= ${binary:Version}),
  libqt6sql6-sqlite,
  ${misc:Depends},
  ${shlibs:Depends}
diff --git a/debian/libowncloudsync0.install b/debian/libowncloudsync0t64.install
similarity index 100%
rename from debian/libowncloudsync0.install
rename to debian/libowncloudsync0t64.install
diff --git a/debian/libowncloudsync0t64.lintian-overrides b/debian/libowncloudsync0t64.lintian-overrides
new file mode 100644
index 000..6d50bcf
--- /dev/null
+++ b/debian/libowncloudsync0t64.lintian-overrides
@@ -0,0 +1,3 @@
+#The lib is so unstable, that it makes no sense to ship symbolfiles
+libowncloudsync0t64: no-symbols-control-file usr/lib/*/libowncloud*.so.*
+libowncloudsync0t64: package-name-doesnt-match-sonames libowncloud-csync0 libowncloudResources0 libowncloudsync0
-- 
2.45.2

Bug#1061241: endless-sky: debian/copyright incomplete

[Róka Tibeti]

Hey,

We fixed the copyright file upstream to follow the Debian specification. 
This fix is present in the latest stable release, 0.10.8.


-- tibetiroka

Bug#1074250: ifupdown2: PR offered to maintainers for merge

[Jan Huijsmans]

Package: ifupdown2
Version: 3.0.0-1.1
Followup-For: Bug #1074250

I found this bug yesterday on my systems, it was reported upstream on
4-4-2024, maintainer asked for a pull request so it could be patched but
it was never offered.

The maintainer just got a pull request by me to patch this issue. Please
incorporate the patch into the package and update.


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 
'oldoldstable'), (500, 'testing'), (500, 'oldstable'), (100, 'stable'), (50, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.7-amd64 (SMP w/32 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=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ifupdown2 depends on:
ii  iproute2  6.9.0-1
ii  python3   3.12.2-1

ifupdown2 recommends no packages.

Versions of packages ifupdown2 suggests:
ii  bridge-utils 1.7.1-2
pn  ethtool  
ii  isc-dhcp-client  4.4.3-P1-5
pn  python3-gvgen
pn  python3-mako 

-- no debconf information

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Blair Noctis]

On 09/07/2024 02:02, Matthias Geiger wrote:
> On 08.07.24 18:45, Jonas Smedegaard wrote:
>> Quoting Matthias Geiger (2024-07-07 11:21:07)
>>> On 07.07.24 10:10, Jonas Smedegaard wrote:
>>> [...]
 [...]
>>> isahc requires sluice only for some pipe functionality in two files.
>>> Since patching sluice proves to be hard I'd
>>>
>>> opt to patch isahc to use something like stdio::piped() rather than
>>> sluice::pipe. Then I can file a RM request for sluice since it's not
>>> used elsewhere and we can finish this transition.
>> Makes great sense.
> 
> I attached my wip for using os_pipe instead of sluice. Still has four errors
> atm; I'd appreciate some knowledgable people looking into it (CC'd ncts). I do
> not have any more time atm to sink into this; will pick it up later unless
> someone beats me to it.
> 
> best,
> 
> werdahias

The errors came from the fact that os_pipe is sync, while isahc is async. I've
implemented a simple wrapper for the pipe reader & writer; rather long, thus put
in a fork: https://salsa.debian.org/ncts/rust-isahc/-/commits/replace-sluice.

Note that os_pipe can fail, thus two `todo!()`s. OTOH, sluice returns directly
the pipe, without wrapping in Result, so I think there is space for improvement.

-- 
Sdrager,
Blair Noctis


OpenPGP_0xC21D9AD423A39727.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature