Processed: golang-github-pion-webrtc.v3 accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> affects -1 buildd.debian.org
Bug #1070410 [src:golang-github-pion-webrtc.v3] golang-github-pion-webrtc.v3 
accesses the internet during build
Added indication that 1070410 affects buildd.debian.org

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

Bug#1070410: golang-github-pion-webrtc.v3 accesses the internet during build

[Jochen Sprickerhof]

Source: golang-github-pion-webrtc.v3
Version: 3.1.56-2
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org

Hi,

golang-github-pion-webrtc.v3 attempts network access during build.
This is forbidden by Policy 4.9:

  For packages in the main archive, required targets must not attempt
  network access, except, via the loopback interface, to services on the
  build host that have been started by the build.

This can be tested with the sbuild unshare backend:

=== NAME  TestDataChannelParamters_Go
util.go:41: Unexpected routines on test end:
goroutine 34 [select]:

github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).loop(0xc240a0, 
{0x9f4b80, 0xc3ec30})

/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:139
 +0x12d
created by 
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).BindRTCPWriter in 
goroutine 16

/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:74
 +0x115

goroutine 35 [select]:

github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).loop(0xc0001303c0,
 {0x9f4b80, 0xc3ec30})

/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:97
 +0x19c
created by 
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).BindRTCPWriter in 
goroutine 16

/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:86
 +0x115

goroutine 36 [select]:

github.com/pion/interceptor/pkg/report.(*SenderInterceptor).loop(0xc000130420, 
{0x9f4b80, 0xc3ec30})

/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:98
 +0x19c
created by 
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).BindRTCPWriter in 
goroutine 16

/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:87
 +0x115

[...]

Cheers Jochen

Bug#1070409: golang-github-pion-ice.v2: accesses the internet during build

[Jochen Sprickerhof]

Source: golang-github-pion-ice.v2
Version: 2.3.1-1
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org

Hi,

golang-github-pion-ice.v2 attempts network access during build.
This is forbidden by Policy 4.9:

  For packages in the main archive, required targets must not attempt
  network access, except, via the loopback interface, to services on the
  build host that have been started by the build.

This can be tested with the sbuild unshare backend:

=== RUN   TestConnectionStateCallback
goroutine profile: total 16
2 @ 0x43f36e 0x40999f 0x4095d2 0x71a847 0x476061
#   0x71a846
github.com/pion/ice/v2.(*Agent).startOnConnectionStateChangeRoutine.func1+0x46  
/<>/_build/src/github.com/pion/ice/v2/agent.go:424

2 @ 0x43f36e 0x438057 0x470a85 0x4a1ec7 0x4a4f0a 0x4a4ef3 0x565516 0x5a2004 
0x5a568e 0x5a567c 0x5a8745 0x476061
#   0x470a84internal/poll.runtime_pollWait+0x84 
/usr/lib/go-1.22/src/runtime/netpoll.go:345
#   0x4a1ec6internal/poll.(*pollDesc).wait+0x26 
/usr/lib/go-1.22/src/internal/poll/fd_poll_runtime.go:84
#   0x4a4f09internal/poll.(*pollDesc).waitRead+0x129
/usr/lib/go-1.22/src/internal/poll/fd_poll_runtime.go:89
#   0x4a4ef2internal/poll.(*FD).RawRead+0x112   
/usr/lib/go-1.22/src/internal/poll/fd_unix.go:708
#   0x565515net.(*rawConn).Read+0x35
/usr/lib/go-1.22/src/net/rawconn.go:44
#   0x5a2003golang.org/x/net/internal/socket.(*Conn).recvMsg+0x143  
/<>/_build/src/golang.org/x/net/internal/socket/rawconn_msg.go:27
#   0x5a568dgolang.org/x/net/internal/socket.(*Conn).RecvMsg+0x4ad  
/<>/_build/src/golang.org/x/net/internal/socket/socket.go:247
#   0x5a567bgolang.org/x/net/ipv4.(*payloadHandler).ReadFrom+0x49b  
/<>/_build/src/golang.org/x/net/ipv4/payload_cmsg.go:31
#   0x5a8744github.com/pion/mdns.(*Conn).start+0xe4 
/<>/_build/src/github.com/pion/mdns/conn.go:295

2 @ 0x43f36e 0x4510c5 0x4ea5b8 0x476061
#   0x4ea5b7context.(*cancelCtx).propagateCancel.func2+0x97 
/usr/lib/go-1.22/src/context/context.go:510

2 @ 0x43f36e 0x4510c5 0x719098 0x476061
#   0x719097github.com/pion/ice/v2.(*Agent).taskLoop+0x137  
/<>/_build/src/github.com/pion/ice/v2/agent.go:230

2 @ 0x43f36e 0x4510c5 0x71a5c5 0x476061
#   0x71a5c4
github.com/pion/ice/v2.(*Agent).startOnConnectionStateChangeRoutine.func2+0xa4  
/<>/_build/src/github.com/pion/ice/v2/agent.go:433

2 @ 0x43f36e 0x4510c5 0x71b113 0x476061
#   0x71b112
github.com/pion/ice/v2.(*Agent).connectivityChecks+0x1b2
/<>/_build/src/github.com/pion/ice/v2/agent.go:550

1 @ 0x434a31 0x4706bd 0x531871 0x5316a5 0x52e4cb 0x7748bd 0x476061
#   0x4706bcruntime/pprof.runtime_goroutineProfileWithLabels+0x1c   
/usr/lib/go-1.22/src/runtime/mprof.go:1079
#   0x531870runtime/pprof.writeRuntimeProfile+0xb0  
/usr/lib/go-1.22/src/runtime/pprof/pprof.go:774
#   0x5316a4runtime/pprof.writeGoroutine+0x44   
/usr/lib/go-1.22/src/runtime/pprof/pprof.go:734
#   0x52e4caruntime/pprof.(*Profile).WriteTo+0x14a  
/usr/lib/go-1.22/src/runtime/pprof/pprof.go:369
#   0x7748bc
github.com/pion/ice/v2.TestConnectionStateCallback.TimeOut.func2+0x3c   
/<>/_build/src/github.com/pion/transport/test/util.go:21

1 @ 0x43f36e 0x40999f 0x4095b2 0x4faeeb 0x4fd037 0x4fa01b 0x4fcf25 0x4fb92b 
0x77c2ac 0x43ef1d 0x476061
#   0x4faeeatesting.(*T).Run+0x3aa  
/usr/lib/go-1.22/src/testing/testing.go:1750
#   0x4fd036testing.runTests.func1+0x36 
/usr/lib/go-1.22/src/testing/testing.go:2161
#   0x4fa01atesting.tRunner+0xfa
/usr/lib/go-1.22/src/testing/testing.go:1689
#   0x4fcf24testing.runTests+0x444  
/usr/lib/go-1.22/src/testing/testing.go:2159
#   0x4fb92atesting.(*M).Run+0x68a  
/usr/lib/go-1.22/src/testing/testing.go:2027
#   0x77c2abmain.main+0x16b _testmain.go:225
#   0x43ef1cruntime.main+0x29c  
/usr/lib/go-1.22/src/runtime/proc.go:271

1 @ 0x43f36e 0x4510c5 0x73a965 0x766c5b 0x766c32 0x746425 0x4fa01b 0x476061
#   0x73a964github.com/pion/ice/v2.(*Agent).connect+0x124   
/<>/_build/src/github.com/pion/ice/v2/transport.go:53
#   0x766c5agithub.com/pion/ice/v2.(*Agent).Dial+0xfa   
/<>/_build/src/github.com/pion/ice/v2/transport.go:15
#   0x766c31github.com/pion/ice/v2.connect+0xd1 
/<>/_build/src/github.com/pion/ice/v2/transport_test.go:219
#   0x746424

Processed: golang-github-pion-ice.v2: accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> affects -1 buildd.debian.org
Bug #1070409 [src:golang-github-pion-ice.v2] golang-github-pion-ice.v2: 
accesses the internet during build
Added indication that 1070409 affects buildd.debian.org

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

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Shmerl]

On Sat, 4 May 2024 21:10:10 +0300 Jussi Pakkanen  wrote:
> The script runs fine on x64_64 but fails on arm64 (and probably also
> x86, but I did not test it). This would imply something wonky going on
> in the toolchain. The question then becomes where this should be
> reported to.

May be for rustc? It's worth filing the bug if it's not clear what the
root cause is. If it's not really rustc, developers will point that out.

Regards,
Shmerl.

Bug#1068390: marked as done (src:translate-toolkit: unsatisfied build dependency in testing: python3-levenshtein)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 11:25:12 +1000
with message-id 
and subject line Re: Bug#1068390: src:translate-toolkit: unsatisfied build 
dependency in testing: python3-levenshtein
has caused the Debian Bug report #1068390,
regarding src:translate-toolkit: unsatisfied build dependency in testing: 
python3-levenshtein
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.)


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

Source: translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



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

Version: 3.12.2-1

python3-levenshtein is now available in testing.


--
Stuart Prescott   http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer  http://www.debian.org/   stu...@debian.org
GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7--- End Message ---

Processed: Re: slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #1066213 [src:slrn] slrn: FTBFS: misc.c:376:4: error: implicit declaration 
of function ‘VA_COPY’ [-Werror=implicit-function-declaration]
Added tag(s) pending and patch.

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

Bug#1066213: slrn: FTBFS: misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration]

[Andreas Beckmann]

Followup-For: Bug #1066213
Control: tag -1 patch pending

Hi,

this was fixed and tagged in git a week ago, but so far no upload
happened.


Andreas

Bug#1061216: Please upgrade to llvm-toolchain-17

[Gregor Riepl]

As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -17.

This package depends on 14.


Not possible at this time. Trying to build openvdb 10.0.1 against LLVM 
17 results in the following error:


CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message):
  OpenVDB AX does not currently support LLVM versions >= 15 due to opaque
  pointer changes in LLVM.  Found unsuitable LLVM version "17.0.6"

The release notes for openvdb 11.1.0[1] mention compatibility with LLVM 
15, but not later versions. There's nothing listed for 11.0.0, and a 
quick test shows that this hasn't changed:


CMake Error at openvdb_ax/openvdb_ax/CMakeLists.txt:118 (message):
  OpenVDB AX does not currently support LLVM versions >= 16 due to opaque
  pointer changes in LLVM.  Found unsuitable LLVM version "17.0.6"

Which LLVM versions are you planning to remove?
Would it be possible to keep at least LLVM 15 until upstream has 
upgraded their code base?


[1] 
https://www.openvdb.org/documentation/doxygen/changes.html#v10_1_0_changes

Bug#1070403: marked as done (does not start because of an "OpenSSL version mismatch")

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 23:54:29 +
with message-id 
and subject line Bug#1070403: fixed in openssh-ssh1 1:7.5p1-17
has caused the Debian Bug report #1070403,
regarding does not start because of an "OpenSSL version mismatch"
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.)


-- 
1070403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-client-ssh1
Version: 1:7.5p1-16
Severity: grave
X-Debbugs-Cc: acct.deb...@tmcl.it

Any attempt to use ssh1 fails with:

"OpenSSL version mismatch. Built against 30100050, you have 30200020"

It looks like the cause is an runtime check of the OpenSSL version, which
requires that major and minor version are the same as those OpenSSH was
compiled against. This was appropriate for OpenSSL 1, but not for OpenSSL 3,
for which only checking the major version is enough to guarantee binary
compatibility.

This was fixed upstream in recent OpenSSH versions [1]. Could you please
backport it to ssh1?

Thanks,
Tommaso

[1] https://bugzilla.mindrot.org/show_bug.cgi?id=3548


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 openssh-client-ssh1 depends on:
ii  libc62.37-18
ii  libselinux1  3.5-2+b2
ii  libssl3t64   3.2.1-3
ii  zlib1g   1:1.3.dfsg-3.1

openssh-client-ssh1 recommends no packages.

openssh-client-ssh1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openssh-ssh1
Source-Version: 1:7.5p1-17
Done: Colin Watson 

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated openssh-ssh1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 May 2024 00:25:01 +0100
Source: openssh-ssh1
Architecture: source
Version: 1:7.5p1-17
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 1070403
Changes:
 openssh-ssh1 (1:7.5p1-17) unstable; urgency=medium
 .
   * Cherry-pick from upstream:
 - Handle OpenSSL >=3 ABI compatibility (closes: #1070403).
 - Update OpenSSL compat test for 3.x.
Checksums-Sha1:
 20ab72b3043a6177b660341a57dc334a5303e008 2204 openssh-ssh1_7.5p1-17.dsc
 4f2f5c6f56025809fa70cc4a47fcdc423b0cf07a 108476 
openssh-ssh1_7.5p1-17.debian.tar.xz
Checksums-Sha256:
 d00bdf3be52540a2bf3c299da02899386e65dfb1ea13281ed4a0d0288071fab8 2204 
openssh-ssh1_7.5p1-17.dsc
 260c5d6d1f2b54d36a7255d81ac83e3d89a7b0bc807e1b82071948c177e5fd1a 108476 
openssh-ssh1_7.5p1-17.debian.tar.xz
Files:
 7bdbb6edbd978c92de30c6de8284aa34 2204 net optional openssh-ssh1_7.5p1-17.dsc
 2fa1e71c85c510250f4dcc5db8ee69a0 108476 net optional 
openssh-ssh1_7.5p1-17.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmY2w/cACgkQOTWH2X2G
UAvK4Q//Tc1nYBQfkmWUdT1b0qHg7qjnBxCK2uVWY6279Ox86buRCWfTKnwbc46T
VJA3go/Nl75VwgrtLZq24KksYuADH3geX7GIhdUE5i2yhruEEGj2e+aMKgnZFAyC
aSfCfPxFQFf6OSlQ0Bwz2pD38JOWYDsxIMSwSZ7jAvNZ4YhXcgVTzv72KTqImbng
fkg/IyPJFyVSC+IuQ1Wf4DLAFcJr2qEMhH91iMp2ANJjjhr6JmE8kze7DpltN7GO
TbIp+ffLIMaBmlpBF/ZGIn6FEykyOEimhFU3xwZe3kmR3dP2JYJ047FRJ8vqLiXJ
klcV5+7iOFOQJASRMcB6bsqFXSLnLSybA6386VyZ+1xNoNtgFLk/N7YufE2ZpFRL
S/FlTPjFVOT7fev8tmlFOktY9pfFlipfzxoL3cFC945332d+J4ZL4+wTG8dnK8EQ
BuxCOXHxdEBcF7Dmyv9ldGoQ04fpHDXHNrmEKlZaYKt8ydgg+a3ZmY7w43WL9nk3
d1iCifeLbzT0kHL9NRdenGA9WfRn8AZSZbkPgzdAH7mgV4yLeuqB9zGG2sCp+xjS
wer0XrIpdvEBX76W6w4u9bRO2PSUuqzxTJnQ1HktZ3lvJBuCAVNjLYLdVZaixghG
x9H3lPn5GibKcNoB9aL01JzNzXhZFiPMLU43myQ4SmakNCTEvPo=
=1nDJ
-END PGP SIGNATURE-



pgpVkyMJH1j2D.pgp
Description: PGP 

Bug#1061205: marked as done (qt6-tools: Please upgrade to llvm-toolchain-18)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 23:30:08 +
with message-id 
and subject line Bug#1061205: fixed in qt6-tools 6.4.2-4
has caused the Debian Bug report #1061205,
regarding qt6-tools: Please upgrade to llvm-toolchain-18
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.)


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

Source: qt6-tools
Severity: important

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -17.

This package depends on 15.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: qt6-tools
Source-Version: 6.4.2-4
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated qt6-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 05 May 2024 01:02:01 +0200
Source: qt6-tools
Architecture: source
Version: 6.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1061205
Changes:
 qt6-tools (6.4.2-4) unstable; urgency=medium
 .
   [ Patrick Franz ]
   * Force build with llvm-toolchain-18 (Closes: 1061205).
Checksums-Sha1:
 74ff1cc032fafed837b02467901b20e3145ae690 3399 qt6-tools_6.4.2-4.dsc
 f100b929f61999302977a4080bb5d3a98e3bddcd 39004 qt6-tools_6.4.2-4.debian.tar.xz
 e9293e966cdd50fc175371c7d3b3bacd9bb69acc 13990 
qt6-tools_6.4.2-4_source.buildinfo
Checksums-Sha256:
 e3b0a236c5042e05cd2925db8bb5b9c1452acd8ae482d2747174aa4bd811ac1c 3399 
qt6-tools_6.4.2-4.dsc
 4497afe2a00a3a6b9a763ea667ca21219a5898e34e76c856969f4f619617f1bf 39004 
qt6-tools_6.4.2-4.debian.tar.xz
 df79cb62658675b274315b484caa6e71be79a06aa4bee0c3e373ed228652da8b 13990 
qt6-tools_6.4.2-4_source.buildinfo
Files:
 e2ac057cb55143bafa1203f2bef6cafa 3399 libs optional qt6-tools_6.4.2-4.dsc
 3c551c6c6a8d2d2218c6018b8ac29417 39004 libs optional 
qt6-tools_6.4.2-4.debian.tar.xz
 fefae6dbe4363ba8b2317825f2c69ee6 13990 libs optional 
qt6-tools_6.4.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmY2vpwACgkQnp96YDB3
/lbWDQ/+OMsQkA9YWKCIfMy7cwCRnw2cM/+KAkM6TosakhxUY69A3himGHIVAIOn
JtfZWDc0IbesTqNlL+YkgfLeg43IUe7sq5ncTWDpyiPobHGAHvqnfIvnL90P1FQk
Api8ltq3jG9+OTaARMVMi9z7Uk3HHTpO/gx4/3vgD1gWtqhwKMkoiAgaPfqlqRt+
VvC+VflTSSI7U8wxZ81QmqZar8u+zAGa/QDsXN+68DxoTZlCkSIf/8RuNs37NORd
jyxGpS8zxjO+nZvKirdl8RRGUi1bpWz7Rlx2ciraGuUaY8gntVJWBr3FCDv1Hvj2
KqQA1omhxPwrTamKk4GPImnh/fZjvBi+GOD6epHCExGVxClclCx5RxFOo+Mm8S/x
v7l1R6aQtXkaC8TMsTaq1b46/gUHk+zSrxKMFeTGEpk4arx2KVa2nzufl9HsqRhu
dkRKYuqcBdnKKdb0C44VR4WeWq3rhm868B/pMMv+TzFiguVJg1aDCFv8e6h4aH5q
D59OhoGVuU50VuuUWGUySPY3cB6X58gRVgl0CTLnzmlnxx4DYB0k5vdwwbsAAsxN
GHVi3kL16xzUEKP+LCEy7+d/mq7ofEweDJPvGz1NsV9fSbdnqBkJBetU0TD2/IcL
Fn/4qqYJScyfRb7fsTMGwcqTE/82HFJALX06tBFVBV0L7KNHjeU=
=5hZw
-END PGP SIGNATURE-



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

Processed: Bug#1070403 marked as pending in openssh-ssh1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070403 [openssh-client-ssh1] does not start because of an "OpenSSL 
version mismatch"
Added tag(s) pending.

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

Bug#1070403: marked as pending in openssh-ssh1

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1070403 in openssh-ssh1 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/ssh-team/openssh-ssh1/-/commit/237920039b48da3992bd91a16a123e7a9d50e103


Handle OpenSSL >=3 ABI compatibility

Closes: #1070403


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070403

Bug#1067073: marked as done (libncursesada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:18:07 +0200
with message-id 
and subject line close 1067073
has caused the Debian Bug report #1067073,
regarding libncursesada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR 
: a-calend.adb:371 overflow check 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.)


-- 
1067073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libncursesada
Version: 6.3.20211021-11
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=libncursesada=armel=6.3.20211021-11=1710701629=0

/usr/bin/gcc-13 -c -x ada -gnatA -gnataEfnoQq -gnatVa -gnatwa.eH.Y -Wall 
-Wextra -gnatyyM80 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -gno-record-gcc-switches 
-gnatec=/tmp/GPR.16132/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.16132/GNAT-TEMP-04.TMP 
/<>/src/terminal_interface-curses-trace.adb
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
terminal_interface-curses.ads:460:30: warning: memory layout out of order 
[-gnatw_r]
terminal_interface-curses.ads:490:10: warning: component clause out of order 
with respect to declaration [-gnatw_r]
terminal_interface-curses.ads:499:16: warning: component clause out of order 
with respect to declaration [-gnatw_r]
gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 6.3.20211021-11

The build succeeds with dependencies fixed for the time_t 64
transition.--- End Message ---

Bug#1067353: marked as done (anet: FTBFS: unsatisfiable build-dependencies: gnat (< 13), gnat-12)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:11:59 +0200
with message-id 
and subject line close 1067353
has caused the Debian Bug report #1067353,
regarding anet: FTBFS: unsatisfiable build-dependencies: gnat (< 13), gnat-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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 8.2), dh-sequence-ada-library, gnat-12, gprbuild, libahven11-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 8.2), dh-sequence-ada-library, gnat-12, gprbuild, libahven11-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [733 B]
> Get:5 copy:/<>/apt_archive ./ Packages [765 B]
> Fetched 2107 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libahven11-dev : Depends: gnat (< 13) but 13.2 is to be installed
>  sbuild-build-depends-main-dummy : Depends: gnat-12 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/anet_0.4.3-3_unstable.log

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

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

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

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

The build succeeds with dependencies updated for the time_t 64/gnat-13
transition.--- End Message ---

Bug#1069469: marked as done (libahven-dev not installable on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:14:03 +0200
with message-id 
and subject line close 1067224 1069469
has caused the Debian Bug report #1069469,
regarding libahven-dev not installable on armhf
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> ruby-pygments.rb, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [738 B]
> Get:5 copy:/<>/apt_archive ./ Packages [770 B]
> Fetched 2117 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/anet_0.5.0-3_unstable-armhf.log

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

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

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

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

The build succeeds and result can be installed with dependencies
updated for the time_t 64 transition.--- End Message ---

Bug#1067224: marked as done (libahven ftbfs on time_t64 architectures)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:14:03 +0200
with message-id 
and subject line close 1067224 1069469
has caused the Debian Bug report #1067224,
regarding libahven ftbfs on time_t64 architectures
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.)


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

Package: src:libahven
Version: 2.8-9
Severity: serious
Tags: sid trixie ftbfs

libahven ftbfs on time_t64 architectures:

[...]
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/<>'
LD_LIBRARY_PATH=stage/usr/lib/arm-linux-gnueabihf /usr/bin/make -C 
obj-dynamic check

make[2]: Entering directory '/<>/obj-dynamic'
make[3]: Entering directory '/<>/obj-dynamic'
"gprbuild" -P ../gnat_linux/build_ahven.gpr -aP../gnat_linux -p 
-Xdevelopment_build=false   -R -v -j4  -Xahven_soversion=31 -cargs:Ada 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/ahven-2.8-9 
-gno-record-gcc-switches -cargs:C -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 
-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/ahven-2.8-9 -cargs:C++ 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=3 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/ahven-2.8-9 -cargs:Fortran 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/ahven-2.8-9 -bargs  -largs 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined

gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

make[3]: *** [comfignat.mk:700: build_ahven.gpr.phony_target] Error 7
make[3]: Leaving directory '/<>/obj-dynamic'
make[2]: *** [Makefile:2: check] Error 2
make[2]: Leaving directory '/<>/obj-dynamic'
make[1]: *** [debian/rules:48: override_dh_auto_test-arch] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:27: binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Version: 2.8-9+b1

The build succeeds and result can be installed with dependencies
updated for the time_t 64 transition.--- End Message ---

Bug#1069421: marked as done (dbusada: FTBFS on armhf: build-dependency not installable: libahven-dev)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:03:28 +0200
with message-id 
and subject line close 1069421
has caused the Debian Bug report #1069421,
regarding dbusada: FTBFS on armhf: build-dependency not installable: 
libahven-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.)


-- 
1069421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbusada
Version: 0.6.2-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, g++-13, gnat (>= 13.1), gnat-13, gprbuild, 
> libahven-dev, libdbus-1-dev, libdbus-glib-1-dev, pkgconf, ruby-pygments.rb, 
> build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, g++-13, gnat (>= 13.1), gnat-13, gprbuild, 
> libahven-dev, libdbus-1-dev, libdbus-glib-1-dev, pkgconf, ruby-pygments.rb, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [799 B]
> Get:5 copy:/<>/apt_archive ./ Packages [831 B]
> Fetched 2239 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/dbusada_0.6.2-6_unstable-armhf.log

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

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

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

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

The build succeeds with dependencies updated for the time_t 64
transition.--- End Message ---

Bug#1069468: marked as done (pcscada: FTBFS on armhf: build-dependency not installable: libahven-dev)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:00:06 +0200
with message-id 
and subject line close 1069468
has caused the Debian Bug report #1069468,
regarding pcscada: FTBFS on armhf: build-dependency not installable: 
libahven-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.)


-- 
1069468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcscada
Version: 0.7.7-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> libpcsclite-dev, ruby-pygments.rb, build-essential, fakeroot
> Filtered Build-Depends: asciidoctor, debhelper-compat (= 13), dh-ada-library 
> (>= 9.1), dh-sequence-ada-library, gnat (>= 13.1), gprbuild, libahven-dev, 
> libpcsclite-dev, ruby-pygments.rb, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [755 B]
> Get:5 copy:/<>/apt_archive ./ Packages [787 B]
> Fetched 2151 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/pcscada_0.7.7-6_unstable-armhf.log

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

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

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

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

This was caused by the time_t 64 transition.
The build succeeds with updated dependencies.--- End Message ---

Bug#1069454: marked as done (libalog: FTBFS on armhf: build-dependency not installable: libahven-dev)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 01:01:38 +0200
with message-id 
and subject line close 1069454
has caused the Debian Bug report #1069454,
regarding libalog: FTBFS on armhf: build-dependency not installable: 
libahven-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.)


-- 
1069454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libalog
Version: 0.6.2-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), gprbuild, 
> libahven-dev, asciidoctor, ruby-pygments.rb, scour
> Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), gprbuild, 
> libahven-dev, asciidoctor, ruby-pygments.rb, scour
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [782 B]
> Get:5 copy:/<>/apt_archive ./ Packages [775 B]
> Fetched 2166 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libahven-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libalog_0.6.2-5_unstable-armhf.log

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

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

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

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

The build succeeds with dependencies updated for the time_t 64
transition.--- End Message ---

Bug#1069467: marked as done (gprbuild: FTBFS on armhf: unsatisfiable build-dependencies: gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gna

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 00:57:42 +0200
with message-id 
and subject line close 1069467
has caused the Debian Bug report #1069467,
regarding gprbuild: FTBFS on armhf: unsatisfiable build-dependencies: 
gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, 
libxmlada-unicode-dev (= 24.0.0-2), gnat-13-cab06c16, libxmlada-unicode-dev (= 
24.0.0-2), gnat-13-cab06c16, libxmlada-unicode-dev (= 24.0.0-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.)


-- 
1069467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gprbuild
Version: 2024.1.20231009-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), 
> libxmlada-dom-dev, libxmlada-input-dev, libxmlada-sax-dev, 
> libxmlada-schema-dev, dh-sequence-sphinxdoc, latexmk, python3-sphinx, 
> texinfo, tex-gyre, texlive-fonts-recommended, texlive-latex-extra
> Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, 
> dh-ada-library (>= 9.1), dh-sequence-ada-library, gnat (>= 13), 
> libxmlada-dom-dev, libxmlada-input-dev, libxmlada-sax-dev, 
> libxmlada-schema-dev, dh-sequence-sphinxdoc, latexmk, python3-sphinx, 
> texinfo, tex-gyre, texlive-fonts-recommended, texlive-latex-extra
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [916 B]
> Get:5 copy:/<>/apt_archive ./ Packages [910 B]
> Fetched 2435 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libxmlada-dom-dev : Depends: gnat-13-cab06c16 but it is not installable
>  Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-input-dev : Depends: gnat-13-cab06c16 but it is not installable
>Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-sax-dev : Depends: gnat-13-cab06c16 but it is not installable
>  Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
>  libxmlada-schema-dev : Depends: gnat-13-cab06c16 but it is not installable
> Depends: libxmlada-unicode-dev (= 24.0.0-2) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/gprbuild_2024.1.20231009-4_unstable-armhf.log

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

Bug#1067629: marked as done (FTBFS: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Sun, 5 May 2024 00:53:19 +0200
with message-id 
and subject line close 1067629
has caused the Debian Bug report #1067629,
regarding FTBFS: Build killed with signal TERM after 150 minutes of inactivity
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=phcpack=armhf=2.4.90%2Bdfsg-1=1711030010=0

   debian/rules execute_after_dh_auto_clean
make[1]: Entering directory '/<>'
gprclean src/Ada/Main/main.gpr || true
E: Build killed with signal TERM after 150 minutes of inactivity


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Version: 2024.1.20231009-5

Phcpack builds with the gprbuild version above, so this was most
probably caused by wrong date values related to the time_t 64 change.--- End Message ---

Bug#1070403: does not start because of an "OpenSSL version mismatch"

[Tommaso Colombo]

Package: openssh-client-ssh1
Version: 1:7.5p1-16
Severity: grave
X-Debbugs-Cc: acct.deb...@tmcl.it

Any attempt to use ssh1 fails with:

"OpenSSL version mismatch. Built against 30100050, you have 30200020"

It looks like the cause is an runtime check of the OpenSSL version, which
requires that major and minor version are the same as those OpenSSH was
compiled against. This was appropriate for OpenSSL 1, but not for OpenSSL 3,
for which only checking the major version is enough to guarantee binary
compatibility.

This was fixed upstream in recent OpenSSH versions [1]. Could you please
backport it to ssh1?

Thanks,
Tommaso

[1] https://bugzilla.mindrot.org/show_bug.cgi?id=3548


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 openssh-client-ssh1 depends on:
ii  libc62.37-18
ii  libselinux1  3.5-2+b2
ii  libssl3t64   3.2.1-3
ii  zlib1g   1:1.3.dfsg-3.1

openssh-client-ssh1 recommends no packages.

openssh-client-ssh1 suggests no packages.

-- no debconf information

Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

[Andreas Beckmann]

Followup-For: Bug #1068665
Control: tag -1 pending

Hi,

in order to make progress with the t64 transition, I've uploaded
Emanuele's patch as a NMU to DELAYED/2. Please let me know if I should
delay it longer.


Andreas

Processed: Re: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068665 [src:cfengine3] cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests 
failed
Added tag(s) pending.

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

Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 21:17:14 +
with message-id 
and subject line Bug#1064516: fixed in ruby-rack 2.2.7-1.1
has caused the Debian Bug report #1064516,
regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146
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.)


-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for ruby-rack.

CVE-2024-26141[0]:
Reject Range headers which are too large
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/62457686b26d33a15a254c7768c2076e8e02b48b 
(v2.2.8.1)

CVE-2024-25126[1]:
Fixed ReDoS in Content Type header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1

CVE-2024-26146[2]:
Fixed ReDoS in Accept header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/e4c117749ba24a66f8ec5a08eddf68deeb425ccd 
(v2.2.8.1)


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-26141
https://www.cve.org/CVERecord?id=CVE-2024-26141
[1] https://security-tracker.debian.org/tracker/CVE-2024-25126
https://www.cve.org/CVERecord?id=CVE-2024-25126
[2] https://security-tracker.debian.org/tracker/CVE-2024-26146
https://www.cve.org/CVERecord?id=CVE-2024-26146

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.2.7-1.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ruby-rack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 May 2024 22:55:26 +0300
Source: ruby-rack
Architecture: source
Version: 2.2.7-1.1
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Team 

Changed-By: Adrian Bunk 
Closes: 1064516
Changes:
 ruby-rack (2.2.7-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * CVE-2024-25126: ReDoS in Content Type header parsing
   * CVE-2024-26141: Reject Range headers which are too large
   * CVE-2024-26146: ReDoS in Accept header parsing
   * Closes: #1064516
Checksums-Sha1:
 f74ea2d462b8737d733fabf353e6c3d9797b2d84 2347 ruby-rack_2.2.7-1.1.dsc
 5f0f4c3a182eba4c4066b011623f01053c8ebc8e 279222 ruby-rack_2.2.7.orig.tar.gz
 6150b1489f5bbf7e4164c9da072976b3d3988d51 10932 
ruby-rack_2.2.7-1.1.debian.tar.xz
Checksums-Sha256:
 1dd5f94772d834d6b0f24d64d4890223f7fdc6c6b1248190acaf2e7726f3779d 2347 
ruby-rack_2.2.7-1.1.dsc
 e942379fba7a6aa18951973a95cc323c10af7aa7ff61207794bf6fea3ec822b4 279222 
ruby-rack_2.2.7.orig.tar.gz
 0bf5154539fdedd122ec3faef1f207681503559d0af4e348c29da701e31dda71 10932 
ruby-rack_2.2.7-1.1.debian.tar.xz
Files:
 d34fa63feef913c5426dfaa79cdaa82b 2347 ruby optional ruby-rack_2.2.7-1.1.dsc
 09f5512b2919ceffc5ab777aebf0c88a 279222 ruby optional 
ruby-rack_2.2.7.orig.tar.gz
 946e35965f30969180924c81317cb52f 10932 ruby optional 
ruby-rack_2.2.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmYz8XMACgkQiNJCh6LY
mLFy/Q/+OEpOrUfoSpwiFtXW6q5qSRCeRMCFTn40LGI3Qtfn5r8Yrj9/cMh7XTIE
OBXyEItK6BO5InugVO8qBe89dC77aql4L5AcGcZYpOBySGjWd7+WBY7HLqWjjDN5
d3jVq/kYQnpgahh0NkN9wu6Pe+e5J9/OSXW2XRAuAfEi8hMcpJSMnKlUp79GTNVE
ht92LRprlftq4tkCMeB47gTQF16fTZHTsaN02rdN5yoTiGyw3IGto6+flMztzq5e
EDaK3AnMwYgkzmlKT/xSz6zKCNi9N51kuyOpcUHFvQ5WieLoHvQ9TOjrU5W4Gq8y
2oWTZmVbwn0r+SbKtzsUWGT2bB4Omun618yvqDcwMuLe+L7oHjdIdGDsWIVeT/o1
7p1OYoGjhfZbje6YG5ckb3CPaaeGbxDhy/Zo/Is82buU+kFG0nOPunYUpyyfXMk7
n6fqBt2Fup/iPA9JFL6J+Fu2TpC3UpA+Kr/2pEqFnxIdB2YhNNmY44qTdpfu6pKP
sK0xoTlAM+H0ZpKqkybAG737+06b3PrC7kpWEcnPNCXUs5vqoGM1R3AyBpcJvpCT

Processed: sqlite3 breaks tracker autopkgtest: killed by signal 6 SIGABRT

[Debian Bug Tracking System]

Processing control commands:

> found -1 sqlite3/3.45.3-1
Bug #1070401 [src:sqlite3, src:tracker] sqlite3 breaks tracker autopkgtest: 
killed by signal 6 SIGABRT
Marked as found in versions sqlite3/3.45.3-1.
> found -1 tracker/3.4.2-3
Bug #1070401 [src:sqlite3, src:tracker] sqlite3 breaks tracker autopkgtest: 
killed by signal 6 SIGABRT
Marked as found in versions tracker/3.4.2-3.

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

Bug#1069344: marked as done (netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test])

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 21:50:00 +0200
with message-id <4767c8c8-976b-58b1-1a5a-af75d7c2c...@debian.org>
and subject line Re: netgen: FTBFS on armhf [debian/rules:66: 
override_dh_auto_test]
has caused the Debian Bug report #1069344,
regarding netgen: FTBFS on armhf [debian/rules:66: override_dh_auto_test]
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.)


-- 
1069344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netgen
Severity: serious
Tags: ftbfs
Control: found -1 6.2.2401+dfsg1-1.1+b1
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

netgen fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=netgen=armhf=6.2.2401%2Bdfsg1-1.1%2Bb1=1712667539=0

Regards,
--- End Message ---
--- Begin Message ---

On Sat, 20 Apr 2024 19:22:48 +0900 Kentaro HAYASHI  wrote:

netgen fails to build on armhf.



https://buildd.debian.org/status/fetch.php?pkg=netgen=armhf=6.2.2401%2Bdfsg1-1.1%2Bb1=1712667539=0


https://buildd.debian.org/status/fetch.php?pkg=netgen=armhf=6.2.2401%2Bdfsg1-1.1%2Bb1=1714847346=0

seems to have been a transient error or a flaky test


Andreas--- End Message ---

Bug#1063077: marked as done (syslog-ng: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 19:34:39 +
with message-id 
and subject line Bug#1063077: fixed in syslog-ng 4.4.0-1
has caused the Debian Bug report #1063077,
regarding syslog-ng: identified for time_t transition but no ABI in shlibs
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.)


-- 
1063077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 1:5.107.0-1
Severity: serious
Tags: patch sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
syslog-ng as a source package shipping runtime libraries whose ABI could
not be analyzed via abi-compliance-checker (and therefore to be on the
safe side we assume is affected).

syslog-ng is an interesting case, because it has no reverse-dependencies
in the archive aside from modules built from the same source package; but
it has a shlibs file declaring no version information at all, so any
external package that *did* build-depend on syslog-ng-dev is sure to get
incomplete runtime dependencies allowing for ABI skew.  Furthermore, the
module packages built from the source get a dependency on:

  syslog-ng-core (>= ${source:Version}), syslog-ng-core (<< 
${source:Version}.1~)

This for some reason assumes that there can never be ABI skew introduced by
a binNMU.  But if the ABI of the libraries in syslog-ng-core are affected by
64-bit time_t, and syslog-ng gets binNMUed, that's exactly what would happen!

So I think it's simply better to have strict versioned dependencies in
the shlibs as in the attached patch, which then makes the hard-coded
dependencies in debian/control unnecessary, allowing you to simplify the
package somewhat.

Since there are no external reverse-dependencies and no package renames
are required here, I do not intend to upload any NMUs for this.  But I
suggest applying the attached patch all the same, to guard against any
breakage due to binNMUs.

If you do not apply this patch, then because syslog-ng depends on at
least one library that is being renamed for the time_t transition
(libssl3), syslog-ng WILL be binNMUed, so if the syslog-ng-core ABI *is*
affected by time_t (which, again, we don't know for sure), there WILL be
ABI skew and packages could break at runtime due to insufficiently strict
dependencies.  I therefore recommend that you apply this patch, which is safe
to apply immediately without waiting for dpkg changes, just to be safe.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru syslog-ng-3.38.1/debian/changelog syslog-ng-3.38.1/debian/changelog
--- syslog-ng-3.38.1/debian/changelog   2023-01-30 18:18:56.0 +
+++ syslog-ng-3.38.1/debian/changelog   2024-02-04 21:35:03.0 +
@@ -1,3 +1,15 @@
+syslog-ng (3.38.1-5.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Adjust shlibs for syslog-ng-core to use a strict versioned depends;
+previously, modules used >=, << dependencies which did not account for
+the possibility of ABI skew in a binNMU, which is exactly what happens
+with the 64-bit time_t transition.
+  * Drop hard-coded dependency rules on syslog-ng-core from modules
+packages, now redundant.  
+
+ -- Steve Langasek   Sun, 04 Feb 2024 21:35:03 +
+
 syslog-ng (3.38.1-5) unstable; urgency=medium
 
   * Build without Criterion support.
diff -Nru syslog-ng-3.38.1/debian/control syslog-ng-3.38.1/debian/control
--- syslog-ng-3.38.1/debian/control 2023-01-30 18:18:56.0 +
+++ syslog-ng-3.38.1/debian/control 2024-02-04 21:32:59.0 +
@@ -150,7 +150,7 @@
 Package: syslog-ng-mod-mongodb
 Architecture: any
 Multi-Arch: foreign
-Depends: ${shlibs:Depends}, ${misc:Depends}, syslog-ng-core (>= 
${source:Version}), syslog-ng-core (<< ${source:Version}.1~)
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Suggests: mongodb-server
 Description: Enhanced system logging daemon (MongoDB plugin)
  syslog-ng is an enhanced log daemon, supporting a wide range of input
@@ -174,7 +174,7 @@
 Package: syslog-ng-mod-sql
 Architecture: any
 Multi-Arch: foreign
-Depends: 

Bug#1070365: marked as done (lyskom-elisp-client: FTBFS: tries to write to /usr/local)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 19:30:10 +
with message-id 
and subject line Bug#1070365: fixed in lyskom-elisp-client 
0.48+git.20231226.364902c3-3
has caused the Debian Bug report #1070365,
regarding lyskom-elisp-client: FTBFS: tries to write to /usr/local
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.)


-- 
1070365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lyskom-elisp-client
Version: 0.48+git.20231226.364902c3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

lyskom-elisp-client FTBFS in the minimal chroots used by the buildds:

https://buildd.debian.org/status/package.php?p=lyskom-elisp-client

...
cp lyskom-0.48+git.20231226.364902c3.el lyskom-0.48+git.20231226.364902c3.elc 
/usr/local/share/emacs/site-lisp
cp: cannot create regular file 
'/usr/local/share/emacs/site-lisp/lyskom-0.48+git.20231226.364902c3.el': 
Permission denied
cp: cannot create regular file 
'/usr/local/share/emacs/site-lisp/lyskom-0.48+git.20231226.364902c3.elc': 
Permission denied
make[1]: *** [Makefile:68: install] Error 1

make install should install to debian/tmp or similar, but not to
/usr/local

Andreas

PS: Hint: try building the package locally in a minimal buildd chroot
using pbuilder or sbuild
--- End Message ---
--- Begin Message ---
Source: lyskom-elisp-client
Source-Version: 0.48+git.20231226.364902c3-3
Done: Joel Rosdahl 

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

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

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

Debian distribution maintenance software
pp.
Joel Rosdahl  (supplier of updated lyskom-elisp-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 May 2024 20:38:31 +0200
Source: lyskom-elisp-client
Architecture: source
Version: 0.48+git.20231226.364902c3-3
Distribution: unstable
Urgency: medium
Maintainer: Joel Rosdahl 
Changed-By: Joel Rosdahl 
Closes: 1070365
Changes:
 lyskom-elisp-client (0.48+git.20231226.364902c3-3) unstable; urgency=medium
 .
   * Disable dh_auto_install (closes: #1070365)
Checksums-Sha1:
 7be4ed02f0385f73f7d96ab456470b8b0af38018 1920 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.dsc
 2163d9e3fa65159ea537b7152a49547d5be7e0d9 11012 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.debian.tar.xz
 ffd737893df0d94111a39239ea0b9b1efd75b5d7 15227 
lyskom-elisp-client_0.48+git.20231226.364902c3-3_amd64.buildinfo
Checksums-Sha256:
 f9d39c58336eb4f61514fa760f69d3e8dc1432c7e04d6e2ed79e5e98f60becfd 1920 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.dsc
 6d77bdf32e1a017a1ea6b89b2379e4162018bd5f69f104868b97d03802116e7e 11012 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.debian.tar.xz
 d3776f759c16dda4ae410588a8385707988ed8e6aa9499601c4ebe7c4121a997 15227 
lyskom-elisp-client_0.48+git.20231226.364902c3-3_amd64.buildinfo
Files:
 86716a691864902be39ee4304c503b17 1920 net optional 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.dsc
 e5f0c58d9be572ed7acdd333cb54d3e3 11012 net optional 
lyskom-elisp-client_0.48+git.20231226.364902c3-3.debian.tar.xz
 67ae4abe0b3e95193dfa0ebe5a114e20 15227 net optional 
lyskom-elisp-client_0.48+git.20231226.364902c3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWpOacaRnks9XhmpRmW3aB1WUrbgFAmY2gMwACgkQmW3aB1WU
rbj0Ww/+Ldm5PlD/t+8aOeM5PoULMeZ+8FyqsIAAreuC5HMGjGgh5IwFJ0s8Kszv
7m1aDLNv8XiyL0qBykDuyBNDCFJwZhyZ6j38nxNncZ1j5j7I7ZynrByOq5sGUUgr
rPmVPymYFVTAiKeIqIkuYvke+cAz450JLtMOcMBS7ENB4d7gx/y1IjwM4rF3HEAb
mpOKA5aqBWgT+gYGFSVxLk9q/ZRByC6ALEBczzwdS+JyYkfu1thbpPQDotjxWsDE
CPwX93L/xvdJFEE4Q2fTN7LqQyAwSzDGzVtqT7gNu9n39gNKUq7WVD5Mzua+wt4V
NABkcHf0uS53/l+TXWddPmNRyLKFuq9SCebXlgTYPn5vKruLUBnJ4g4q7oPyEzAv
hdhLeea7z9xTXpgrpgYsaRuaqDrQyNm6Zd/FObtPMaqg+lfG192vXiaIH6JNXAyD
GekBTsnlDh5KSOO4StVFlA0MR2SciF9dNbPiGUgf3obLPRCQGsCJpa/Av2dUWDWY
TXLbVvYteay3ANvrSUYOChzsjpIPIo1BWouKWd/rREi9WN4e/Zm5IJpZS4LGMnfI
apa+tdmINuP8L1EjohCtnof/hOb/oBfaefvsau90i6ib4eeo5g+dDZwU6t/Gh6aC
ASmHzAlqfAlJskKK9hxN0Jn7nADtElMwPGt7o4Y6qszoV05Wll8=
=yr2n
-END PGP SIGNATURE-



pgpvfnzlevUwG.pgp

Bug#1069535: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure retu

[Otto Kekäläinen]

control: forward -1 https://github.com/codership/galera/issues/659
control: forwarded -1 https://github.com/codership/galera/issues/659

Processed (with 1 error): Re: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--outpu

[Debian Bug Tracking System]

Processing control commands:

> forward -1 https://github.com/codership/galera/issues/659
Unknown command or malformed arguments to command.

> forwarded -1 https://github.com/codership/galera/issues/659
Bug #1069535 [src:galera-3] galera-3: FTBFS on armel: dh_auto_test: error: cd 
obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 
ARGS=--output-on-failure returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/codership/galera/issues/659'.

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

Processed: tagging 1070370, found 1070370 in 1.3a-3, found 1070370 in 1.3a-1.2, found 1070370 in 1.3a-1.1 ...

[Debian Bug Tracking System]

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

> tags 1070370 + upstream
Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837
Added tag(s) upstream.
> found 1070370 1.3a-3
Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837
Marked as found in versions dmitry/1.3a-3.
> found 1070370 1.3a-1.2
Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837
Marked as found in versions dmitry/1.3a-1.2.
> found 1070370 1.3a-1.1
Bug #1070370 [src:dmitry] dmitry: CVE-2017-7938 CVE-2020-14931 CVE-2024-31837
Marked as found in versions dmitry/1.3a-1.1.
> tags 1070371 + upstream
Bug #1070371 [src:ofono] ofono: CVE-2023-4232 CVE-2023-4233 CVE-2023-4234 
CVE-2023-4235
Added tag(s) upstream.
> tags 1070372 + upstream
Bug #1070372 {Done: Daniel Baumann } 
[src:tqdm] tqdm: CVE-2024-34062
Added tag(s) upstream.
> found 1070372 4.66.2-3
Bug #1070372 {Done: Daniel Baumann } 
[src:tqdm] tqdm: CVE-2024-34062
Marked as found in versions tqdm/4.66.2-3.
> tags 1070373 + upstream
Bug #1070373 [src:quickjs] quickjs: CVE-2024-33263
Added tag(s) upstream.
> forwarded 1070373 https://github.com/bellard/quickjs/issues/277
Bug #1070373 [src:quickjs] quickjs: CVE-2024-33263
Set Bug forwarded-to-address to 'https://github.com/bellard/quickjs/issues/277'.
> tags 1070374 + upstream
Bug #1070374 [src:social-auth-app-django] social-auth-app-django: CVE-2024-32879
Added tag(s) upstream.
> found 1070374 5.4.0-1
Bug #1070374 [src:social-auth-app-django] social-auth-app-django: CVE-2024-32879
Marked as found in versions social-auth-app-django/5.4.0-1.
> tags 1070375 + upstream
Bug #1070375 [src:python-jose] python-jose: CVE-2024-33663 CVE-2024-33664
Added tag(s) upstream.
> found 1070375 3.3.0+dfsg-4
Bug #1070375 [src:python-jose] python-jose: CVE-2024-33663 CVE-2024-33664
Marked as found in versions python-jose/3.3.0+dfsg-4.
> tags 1070376 + upstream
Bug #1070376 [src:uriparser] uriparser: CVE-2024-34402 CVE-2024-34403
Added tag(s) upstream.
> tags 1070377 + upstream
Bug #1070377 [src:frr] frr: CVE-2024-34088
Added tag(s) upstream.
> forwarded 1070377 https://github.com/FRRouting/frr/pull/15674
Bug #1070377 [src:frr] frr: CVE-2024-34088
Set Bug forwarded-to-address to 'https://github.com/FRRouting/frr/pull/15674'.
> tags 1070378 + upstream
Bug #1070378 [src:docker.io] docker.io: CVE-2024-32473
Added tag(s) upstream.
> tags 1070379 + upstream
Bug #1070379 [src:pytorch] pytorch: CVE-2024-31580 CVE-2024-31583 CVE-2024-31584
Added tag(s) upstream.
> tags 1070380 + upstream
Bug #1070380 [src:llvm-toolchain-18] llvm-toolchain-18: CVE-2024-31852
Added tag(s) upstream.
> tags 1070381 + upstream
Bug #1070381 [src:llvm-toolchain-17] llvm-toolchain-17: CVE-2024-31852
Added tag(s) upstream.
> tags 1070382 + upstream
Bug #1070382 [src:llvm-toolchain-16] llvm-toolchain-16: CVE-2024-31852
Added tag(s) upstream.
> tags 1070383 + upstream
Bug #1070383 [src:llvm-toolchain-15] llvm-toolchain-15: CVE-2024-31852
Added tag(s) upstream.
> tags 1070384 + upstream
Bug #1070384 [src:llvm-toolchain-14] llvm-toolchain-14: CVE-2024-31852
Added tag(s) upstream.
> tags 1070387 + upstream
Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391
Added tag(s) upstream.
> found 1070387 3.0.22-2
Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391
Marked as found in versions gdcm/3.0.22-2.
> found 1070387 3.0.22-3
Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391
Marked as found in versions gdcm/3.0.22-3.
> tags 1070388 + upstream
Bug #1070388 [src:jupyterhub] jupyterhub: CVE-2024-28233
Added tag(s) upstream.
> tags 1070390 + upstream
Bug #1070390 [src:opendmarc] opendmarc: CVE-2024-25768
Added tag(s) upstream.
> tags 1070392 + upstream
Bug #1070392 [src:exiv2] exiv2: CVE-2024-24826 CVE-2024-25112
Added tag(s) upstream.
> fixed 1070392 0.28.2+dfsg-1
Bug #1070392 [src:exiv2] exiv2: CVE-2024-24826 CVE-2024-25112
Marked as fixed in versions exiv2/0.28.2+dfsg-1.
> found 1070392 0.27.6-1
Bug #1070392 [src:exiv2] exiv2: CVE-2024-24826 CVE-2024-25112
Marked as found in versions exiv2/0.27.6-1.
> tags 1070393 + upstream
Bug #1070393 [src:gobgp] gobgp: CVE-2023-46565
Added tag(s) upstream.
> forwarded 1070393 https://github.com/osrg/gobgp/issues/2725
Bug #1070393 [src:gobgp] gobgp: CVE-2023-46565
Set Bug forwarded-to-address to 'https://github.com/osrg/gobgp/issues/2725'.
> tags 1070394 + upstream
Bug #1070394 [src:libstb] libstb: CVE-2023-47212
Added tag(s) upstream.
> tags 1070395 + upstream
Bug #1070395 [src:tinyproxy] tinyproxy: CVE-2023-40533 CVE-2023-49606
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1070370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070370
1070371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070371
1070372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070372
1070373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070373
1070374: 

Bug#1069535: [debian-mysql] Bug#1069535: Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure retu

[Otto Kekäläinen]

Forwarded: https://github.com/codership/galera/issues/659

Processed: Re: shishi: NMU diff for 64-bit time_t transition

[Debian Bug Tracking System]

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

> notfound 1062896 shishi/1.0.3-2
Bug #1062896 {Done: Simon Josefsson } [src:shishi] shishi: 
NMU diff for 64-bit time_t transition
No longer marked as found in versions shishi/1.0.3-2.
>
End of message, stopping processing here.

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

Processed: severity of 1021656 is serious

[Debian Bug Tracking System]

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

> severity 1021656 serious
Bug #1021656 [tt-rss] please package new upstream release
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: Re: Bug#1064486: rnp: FTBFS: Errors while running CTest

[Debian Bug Tracking System]

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

> found 1064486 0.16.3-1
Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest
Marked as found in versions rnp/0.16.3-1.
> tags 1064486 + ftbfs bookworm trixie sid
Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest
Added tag(s) trixie, bookworm, sid, and ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1054608 is serious

[Debian Bug Tracking System]

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

> severity 1054608 serious
Bug #1054608 [tt-rss] tt-rss: New entries always marked as read even if the 
unread counter is not null
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1064486: rnp: FTBFS: Errors while running CTest

[Santiago Vila]

found 1064486 0.16.3-1
tags 1064486 + ftbfs bookworm trixie sid
thanks

El 20/4/24 a las 14:12, Andreas Metzler escribió:

FWIW I also get testsuite errors on current sid on amd64
The following tests FAILED:
  83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed)
  90 - rnp_tests.test_ffi_security_profile (Failed)
 174 - rnp_tests.test_key_add_userid (Failed)
 254 - cli_tests-EncryptElgamal (Failed)


Hello. This is also happening in bookworm, I assume that for the same 
underlying reason,
so I'm adding the bookworm version.

I've put several build logs (both successful and failed, to compare) here:

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

Note that in those build logs I'm using different sbuild backends, but I believe
they are not the reason why now it fails while it did not before.
I suspect of openssl, but I have not made any test to confirm.

Thanks.

Processed: pistache: Please disable network tests in bookworm as well

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.0.5+ds-4
Bug #1070397 [src:pistache] pistache: Please disable network tests in bookworm 
as well
Marked as fixed in versions pistache/0.0.5+ds-4.

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

Bug#1070397: pistache: Please disable network tests in bookworm as well

[Santiago Vila]

Package: src:pistache
Version: 0.0.5+ds-3
Severity: serious
Tags: bookworm ftbfs
Control: fixed -1 0.0.5+ds-4

Dear maintainer:

Please disable network tests in bookworm as well, as they have started to fail
even when network access is allowed during build:

[ RUN  ] net_test.address_creation
../tests/net_test.cc:110: Failure
Expected equality of these values:
  address15.host()
Which is: "93.184.215.14"
  "93.184.216.34"
[  FAILED  ] net_test.address_creation (1 ms)

The test apparently expects www.example.com to have 93.184.216.34
as its IP address, but now it's 93.184.215.14.

Thanks.

Bug#1069337: marked as done (Update Depends for the time64 library renames)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 18:58:46 +
with message-id 
and subject line Bug#1069337: fixed in thunderbird 1:125.0~b3-1
has caused the Debian Bug report #1069337,
regarding Update Depends for the time64 library renames
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.)


-- 
1069337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:115.9.0-1+b1
Severity: serious

thunderbird explicitly Depends: libotr5. It should be changed to the t64 name
if it's really needed.

Note that the package is still installable because it's not built on 32-bit
time64 arches, but it still needs to be fixed so that libotr5 can be removed.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 thunderbird depends on:
ii  debianutils 5.17
ii  fontconfig  2.15.0-1.1
ii  kdialog 4:22.12.3-1+b1
ii  libasound2t64 [libasound2]  1.2.11-1+b1
ii  libatk1.0-0t64 [libatk1.0-0]2.52.0-1
ii  libc6   2.37-18
ii  libcairo-gobject2   1.18.0-3+b1
ii  libcairo2   1.18.0-3+b1
ii  libdbus-1-3 1.14.10-4+b1
pn  libdbus-glib-1-2
ii  libevent-2.1-7t64 [libevent-2.1-7]  2.1.12-stable-8.1+b3
ii  libffi8 3.4.6-1
ii  libfontconfig1  2.15.0-1.1
ii  libfreetype62.13.2+dfsg-1+b4
ii  libgcc-s1   14-20240330-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b3
ii  libglib2.0-0t64 [libglib2.0-0]  2.78.4-6
ii  libgtk-3-0t64 [libgtk-3-0]  3.24.41-4
ii  libnspr42:4.35-1.1+b1
ii  libnss3 2:3.99-1
pn  libotr5 
ii  libpango-1.0-0  1.52.1+ds-1
pn  librnp0 
ii  libstdc++6  14-20240330-1
ii  libvpx8 1.13.1-2
ii  libx11-62:1.8.7-1
ii  libx11-xcb1 2:1.8.7-1
ii  libxcb-shm0 1.17.0-1
ii  libxcb1 1.17.0-1
ii  libxext62:1.3.4-1+b1
ii  libxrandr2  2:1.5.4-1
ii  psmisc  23.7-1
ii  x11-utils   7.7+6+b1
ii  zenity  4.0.1-1+b1
ii  zlib1g  1:1.3.dfsg-3.1

Versions of packages thunderbird recommends:
ii  hunspell-ru [hunspell-dictionary]  1:24.2.2-1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.13-2
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.20.1-6+b1
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:125.0~b3-1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 14:28:56 +0200
Source: thunderbird
Architecture: source
Version: 1:125.0~b3-1
Distribution: experimental
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 1069337
Changes:
 thunderbird (1:125.0~b3-1) experimental; urgency=medium
 .
   [ William 

Bug#1070395: tinyproxy: CVE-2023-40533 CVE-2023-49606

[Moritz Mühlenhoff]

Source: tinyproxy
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for tinyproxy.

CVE-2023-40533[0]:
| An uninitialized memory use vulnerability exists in Tinyproxy 1.11.1
| while parsing HTTP requests. In certain configurations, a specially
| crafted HTTP request can result in disclosure of data allocated on
| the heap, which could contain sensitive information. An attacker can
| make an unauthenticated HTTP request to trigger this vulnerability.

https://talosintelligence.com/vulnerability_reports/TALOS-2023-1902

CVE-2023-49606[1]:
| A use-after-free vulnerability exists in the HTTP Connection Headers
| parsing in Tinyproxy 1.11.1 and Tinyproxy 1.10.0. A specially
| crafted HTTP header can trigger reuse of previously freed memory,
| which leads to memory corruption and could lead to remote code
| execution. An attacker needs to make an unauthenticated HTTP request
| to trigger this vulnerability.

https://talosintelligence.com/vulnerability_reports/TALOS-2023-1889


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40533
https://www.cve.org/CVERecord?id=CVE-2023-40533
[1] https://security-tracker.debian.org/tracker/CVE-2023-49606
https://www.cve.org/CVERecord?id=CVE-2023-49606

Please adjust the affected versions in the BTS as needed.

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Jussi Pakkanen]

On Sat, 4 May 2024 at 13:27, Jussi Pakkanen  wrote:

> Disabling tests is also not a great because it just hides the bug.
> Thus other packages that actually use this functionality are going to
> hit this eventually and file more bugs on Meson. That is a waste of
> everybody's time and energy.

I managed to replicate this bug without Meson. Attached is sample code
plus a build script that runs a few compilation commands in a shell
script.

The script runs fine on x64_64 but fails on arm64 (and probably also
x86, but I did not test it). This would imply something wonky going on
in the toolchain. The question then becomes where this should be
reported to.


rustcmixbug.tar.gz
Description: GNU Zip compressed data

Processed: Re: libkkc: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: Marisa.gir] Error 1

[Debian Bug Tracking System]

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

> found 1060951 1.78.1-15
Bug #1060951 [src:gobject-introspection] Build regression in multiarch 
g-ir-scanner
Marked as found in versions gobject-introspection/1.78.1-15.
>
End of message, stopping processing here.

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

Bug#1070388: jupyterhub: CVE-2024-28233

[Moritz Mühlenhoff]

Source: jupyterhub
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for jupyterhub.

CVE-2024-28233[0]:
| JupyterHub is an open source multi-user server for Jupyter
| notebooks. By tricking a user into visiting a malicious subdomain,
| the attacker can achieve an XSS directly affecting the former's
| session. More precisely, in the context of JupyterHub, this XSS
| could achieve full access to JupyterHub API and user's single-user
| server. The affected configurations are single-origin JupyterHub
| deployments and JupyterHub deployments with user-controlled
| applications running on subdomains or peer subdomains of either the
| Hub or a single-user server. This vulnerability is fixed in 4.1.0.

https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-7r3h-4ph8-w38g
https://github.com/jupyterhub/jupyterhub/commit/e2798a088f5ad45340fe79cdf1386198e664f77f


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-28233
https://www.cve.org/CVERecord?id=CVE-2024-28233

Please adjust the affected versions in the BTS as needed.

Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391

[Moritz Mühlenhoff]

Source: gdcm
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for gdcm.

These are fixed in 3.0.24:

CVE-2024-25569[0]:
| An out-of-bounds read vulnerability exists in the
| RAWCodec::DecodeBytes functionality of Mathieu Malaterre Grassroot
| DICOM 3.0.23. A specially crafted DICOM file can lead to an out-of-
| bounds read. An attacker can provide a malicious file to trigger
| this vulnerability.

https://talosintelligence.com/vulnerability_reports/TALOS-2024-1944

CVE-2024-22373[1]:
| An out-of-bounds write vulnerability exists in the
| JPEG2000Codec::DecodeByStreamsCommon functionality of Mathieu
| Malaterre Grassroot DICOM 3.0.23. A specially crafted DICOM file can
| lead to a heap buffer overflow. An attacker can provide a malicious
| file to trigger this vulnerability.

https://talosintelligence.com/vulnerability_reports/TALOS-2024-1935

CVE-2024-22391[2]:
| A heap-based buffer overflow vulnerability exists in the
| LookupTable::SetLUT functionality of Mathieu Malaterre Grassroot
| DICOM 3.0.23. A specially crafted malformed file can lead to memory
| corruption. An attacker can provide a malicious file to trigger this
| vulnerability.

https://talosintelligence.com/vulnerability_reports/TALOS-2024-1924


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-25569
https://www.cve.org/CVERecord?id=CVE-2024-25569
[1] https://security-tracker.debian.org/tracker/CVE-2024-22373
https://www.cve.org/CVERecord?id=CVE-2024-22373
[2] https://security-tracker.debian.org/tracker/CVE-2024-22391
https://www.cve.org/CVERecord?id=CVE-2024-22391

Please adjust the affected versions in the BTS as needed.

Bug#1066032: marked as done (pygobject: FTBFS on armhf: time_t build test failure)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 16:50:02 +
with message-id 
and subject line Bug#1066032: fixed in gobject-introspection 1.80.1-2
has caused the Debian Bug report #1066032,
regarding pygobject: FTBFS on armhf: time_t build test failure
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.)


-- 
1066032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygobject
Version: 3.47.0-3
Severity: serious
Tags: unstable trixie ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Although Debian has not yet gotten to pygobject in the time_t
transition for armel/armhf, Ubuntu has and experienced a build test
failure in test_gi.py for the test_time_t tests which I believe are
using functions in glib2.0. I assume Debian also experiences this
issue.

Test log excerpt

tests/test_gi.py ... [ 21%]
.
--- stderr ---
Fatal Python error: Aborted

Current thread 0xf785e020 (most recent call first):
  File "/<>/tests/test_gi.py", line 579 in test_time_t_in
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102
in _multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119
in _hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 175 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 198 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Full build log
==
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

Originally reported at https://launchpad.net/bugs/2056753

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.80.1-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gobject-introspection 
package)

(This message was 

Bug#1066900: marked as done (g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 16:50:02 +
with message-id 
and subject line Bug#1066900: fixed in gobject-introspection 1.80.1-2
has caused the Debian Bug report #1066900,
regarding g-ir-compiler: generates incorrect typelib when cross-compiling with 
different type sizes
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.)


-- 
1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gobject-introspection
Version: 1.78.1-16
Severity: serious
Justification: results in misbuilt packages
X-Debbugs-Cc: debian-cr...@lists.debian.org

When it converts GIR XML to binary typelib files, g-ir-compiler replaces
abstract types such as int and gsize (size_t) with concrete types such as
gint32 (int32_t) and guint64 (uint32_t). The way in which it does this
depends on the type sizes discovered at configure time when compiling
g-ir-compiler.

This means that cross-compiling for an arm64 or riscv64 host on an amd64
build machine should be OK, but cross-compiling for armhf or i386 on amd64
will produce invalid typelibs. I am sorry that I didn't notice this sooner.

A crude solution to this would be to revert gobject-introspection and
gobject-introspection-bin to be Multi-Arch: no, so that building typelibs
is no longer possible in cross-builds. [1]

A more refined version of that would be to change the relationship between
gobject-introspection and gobject-introspection-bin so that instead of the
current arrangement where the dependency is on a virtual package
gobject-introspection-linux-little-endian, it would be on a virtual package
that also reflects the word size in use:
gobject-introspection-linux-lp64-little-endian or similar. This would
preserve the ability to cross-compile in only those situations where it
would be correct. [2]

A workaround to enable cross-compiling between word sizes would be to use
the host architecture g-ir-compiler, and run it via qemu-user.
Unfortunately this will greatly increase the amount of host-architecture
code that needs to be run via emulation.

In the short term, I'm going to do [1] or [2] as a matter of urgency,
to ensure that Ubuntu 24.04 doesn't ship with faulty cross-tools that
claim to work but actually do not. Any further improvement can be in-scope
for #1030223 "gobject-introspection: make cross-compilation possible".

If we do [2] then we will have to be extra-careful to distinguish between
dissimilar ILP32 ABIs, because gobject-introspection currently hard-codes
that it thinks time_t is long and off_t is size_t, both of which happen
to be correct on LP64 and on i386, but neither of which is correct on
an ILP32 architecture that has transitioned to large file support and
64-bit time_t (such as armel and armhf in 2024) or an ILP32 architecture
that always had 64-bit off_t and time_t (such as x32).

I apologise for having been insufficiently careful when enabling this
feature.

smcv
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.80.1-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gobject-introspection 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 12:39:14 -0400
Source: gobject-introspection
Built-For-Profiles: noudeb
Architecture: source
Version: 1.80.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1065332 1066032 1066900
Changes:
 gobject-introspection (1.80.1-2) unstable; urgency=medium
 .
   * Release to unstable
 .
 gobject-introspection (1.80.1-1) experimental; urgency=medium
 .
   [ Jeremy Bícha ]
   * New upstream release
   * Drop time_t and off_t patches: applied in new release
 .
   [ Simon McVittie ]
   * d/copyright: Remove unused license paragraph
 .
 gobject-introspection (1.80.0-2) experimental; urgency=medium
 .
   * Merge packaging changes from 

Bug#1066470: marked as done (kxl: FTBFS: KXLsound.c:75:9: error: implicit declaration of function 'read'; did you mean 'fread'? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 16:36:08 +
with message-id 
and subject line Bug#1066470: fixed in kxl 1.2.4-1
has caused the Debian Bug report #1066470,
regarding kxl: FTBFS: KXLsound.c:75:9: error: implicit declaration of function 
'read'; did you mean 'fread'? [-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.)


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

Hi,

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

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

Relevant part (hopefully):
>  gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"KXL\" 
> -DVERSION=\"1.1.7\" -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
> -DHAVE_FCNTL_H=1 -DHAVE_MALLOC_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_TIME_H=1 
> -DHAVE_LINUX_JOYSTICK_H=1 -DHAVE_LINUX_SOUNDCARD_H=1 -DTIME_WITH_SYS_TIME=1 
> -DRETSIGTYPE=void -DHAVE_SELECT=1 -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> KXLjoystick.c  -fPIC -DPIC -o .libs/KXLjoystick.o
> KXLmisc.c: In function 'KXL_ReadU16':
> KXLmisc.c:196:3: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   196 |   fread(c, 1, 2, fp);
>   |   ^~
> KXLmisc.c: In function 'KXL_ReadU32':
> KXLmisc.c:209:3: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   209 |   fread(c, 1, 4, fp);
>   |   ^~
> KXLsound.c: In function 'KXL_SoundServer':
> KXLsound.c:75:9: error: implicit declaration of function 'read'; did you mean 
> 'fread'? [-Werror=implicit-function-declaration]
>75 | if (read(KXL_SoundData.Pipe[0], ,sizeof(Command)) != 
> sizeof(Command))
>   | ^~~~
>   | fread
> KXLsound.c:165:9: error: implicit declaration of function 'write'; did you 
> mean 'fwrite'? [-Werror=implicit-function-declaration]
>   165 | write(KXL_SoundData.Device, KXL_SoundData.PBuff, 
> fragment_size);
>   | ^
>   | fwrite
> KXLimage.c: In function 'KXL_ReadBitmapHeader':
> KXLimage.c:112:3: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   112 |   fread(hed->magic, 1, 2, fp);
>   |   ^~~
> KXLimage.c:166:7: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   166 |   fread(&(hed->data[i * hed->w]), hed->w, 1, fp);
>   |   ^~
> KXLsound.c: In function 'KXL_InitSound':
> KXLsound.c:262:7: error: implicit declaration of function 'pipe' 
> [-Werror=implicit-function-declaration]
>   262 |   if (pipe(KXL_SoundData.Pipe) < 0) {
>   |   ^~~~
> KXLsound.c:267:27: error: implicit declaration of function 'fork' 
> [-Werror=implicit-function-declaration]
>   267 |   if ((KXL_SoundData.ID = fork()) < 0) {
>   |   ^~~~
> KXLsound.c:273:5: error: implicit declaration of function 'close'; did you 
> mean 'pclose'? [-Werror=implicit-function-declaration]
>   273 | close(KXL_SoundData.Pipe[1]);
>   | ^
>   | pclose
> KXLsound.c: In function 'KXL_LoadSound':
> KXLsound.c:213:3: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   213 |   fread(dummy, sizeof(Uint8), 40, file);
>   |   ^
> KXLsound.c:216:3: warning: ignoring return value of 'fread' declared with 
> attribute 'warn_unused_result' [-Wunused-result]
>   216 |   fread(new.Data, sizeof(Uint8), new.Length, file);
>   |   ^~~~
> KXLjoystick.c: In function 

Processed: notfound 1068068 in bobcat/6.04.00-1, notfound 1068068 in bobcat/11.01.02-1

[Debian Bug Tracking System]

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

> notfound 1068068 bobcat/6.04.00-1
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
No longer marked as found in versions bobcat/6.04.00-1.
No longer marked as found in versions bobcat/6.04.00-1.
No longer marked as found in versions bobcat/6.04.00-1.
> notfound 1068068 bobcat/11.01.02-1
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
The source bobcat and version 11.01.02-1 do not appear to match any binary 
packages
No longer marked as found in versions bobcat/11.01.02-1.
No longer marked as found in versions bobcat/11.01.02-1.
No longer marked as found in versions bobcat/11.01.02-1.
> notfound 1068325 bobcat/6.04.00-1
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
Ignoring request to alter found versions of bug #1068325 to the same values 
previously set
Ignoring request to alter found versions of bug #1068068 to the same values 
previously set
Ignoring request to alter found versions of bug #1068327 to the same values 
previously set
> notfound 1068325 bobcat/11.01.02-1
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
The source bobcat and version 11.01.02-1 do not appear to match any binary 
packages
Ignoring request to alter found versions of bug #1068325 to the same values 
previously set
Ignoring request to alter found versions of bug #1068068 to the same values 
previously set
Ignoring request to alter found versions of bug #1068327 to the same values 
previously set
> notfound 1068327 bobcat/6.04.00-1
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
Ignoring request to alter found versions of bug #1068327 to the same values 
previously set
Ignoring request to alter found versions of bug #1068068 to the same values 
previously set
Ignoring request to alter found versions of bug #1068325 to the same values 
previously set
> notfound 1068327 bobcat/11.01.02-1
Bug #1068327 {Done: tony mancill } [src:icmake,src:bobcat] 
flexc++: FTBFS on armel, armhf (Segmentation fault)
Bug #1068068 {Done: tony mancill } [src:icmake,src:bobcat] 
Need rebootstrapping on armel and armhf
Bug #1068325 {Done: tony mancill } [src:icmake,src:bobcat] 
bisonc++: FTBFS on armel, armhf (override_dh_auto_clean Segmentation fault)
The source bobcat and version 11.01.02-1 do not appear to match any binary 
packages
Ignoring request to alter found versions of bug #1068327 to the same values 
previously set
Ignoring request to alter found versions of bug #1068068 to the same values 
previously set
Ignoring request to alter found versions of bug #1068325 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1070343: openfortivpn: stopped working after today's upgrade in Debian testing

[Francesco Poli]

Control: severity -1 important
Control: retitle -1 please warn users about the option --pppd-accept-remote 
needed for ppp >= 2.5.0


On Sat, 04 May 2024 00:23:32 +0200 Francesco Poli (wintermute) wrote:

[...]
>   Peer refused to agree to his IP address
[...]

I tried to downgrade ppp to version 2.4.9-1+1.1+b1 and openfortivpn is
working again.

By searching the web, I found openfortigui issue [#194], which mentions
the new option --pppd-accept-remote that has to be used with
openfortvpn, when ppp version >= 2.5.0 ...

[#194]: 

I actually added

  pppd-accept-remote = true

to my /etc/openfortivpn/MYNETWORK and now openfortivpn works again
(with ppp/2.5.0-1+2).

I am therefore lowering the severity of this bug report.

I am not closing it, though, since I believe that such an important
behavior change (the need to add an option, if ppp version >= 2.5.0)
should really be communicated to the users of the openfortivpn Debian
package users.
Maybe a NEWS.Debian file in /usr/share/doc/openfortivpn could be added
to document this new need?
I really believe that users should be warned about this!




-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpzLbZiGXaLd.pgp
Description: PGP signature

Processed: Re: Bug#1070343: openfortivpn: stopped working after today's upgrade in Debian testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1070343 [openfortivpn] openfortivpn: stopped working after today's upgrade 
in Debian testing
Severity set to 'important' from 'grave'
> retitle -1 please warn users about the option --pppd-accept-remote needed for 
> ppp >= 2.5.0
Bug #1070343 [openfortivpn] openfortivpn: stopped working after today's upgrade 
in Debian testing
Changed Bug title to 'please warn users about the option --pppd-accept-remote 
needed for ppp >= 2.5.0' from 'openfortivpn: stopped working after today's 
upgrade in Debian testing'.

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

Bug#1069490: marked as done (superlu-dist: FTBFS on armhf: tests fail)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 18:02:19 +0200
with message-id <5d090b3553aabb32fae284d4d4c87...@debian.org>
and subject line Re: Bug#1069490 superlu-dist: FTBFS on armhf: tests fail
has caused the Debian Bug report #1069490,
regarding superlu-dist: FTBFS on armhf: tests fail
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.)


-- 
1069490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: superlu-dist
Version: 8.2.1+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-arm-linux-gnueabihf'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j1
> UpdateCTestConfiguration  from 
> :/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Parse Config 
> file:/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Parse Config 
> file:/<>/obj-arm-linux-gnueabihf/DartConfiguration.tcl
> Test project /<>/obj-arm-linux-gnueabihf
> 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: 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-gnueabihf/TEST
> 1: Test timeout computed to be: 1500
> 1: --
> 1: Sorry!  You were supposed to get help about:
> 1: pmix_init:startup:internal-failure
> 1: But I couldn't open the help file:
> 1: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
> Sorry!
> 1: --
> 1: [ip-10-84-234-180:3632169] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
>  1/17 Test  #1: pdtest_1x1_1_2_8_20_SP ...***Failed0.02 sec
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-180:3632169] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> 
> 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-gnueabihf/TEST
> 2: Test timeout computed to be: 1500
> 2: --
> 2: Sorry!  You were supposed to get help about:
> 2: pmix_init:startup:internal-failure
> 2: But I couldn't open the help file:
> 2: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
> Sorry!
> 2: --
> 2: [ip-10-84-234-180:3632170] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
>  2/17 Test  #2: pdtest_1x1_3_2_8_20_SP ...***Failed0.01 sec
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-180:3632170] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> 
> 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 

Bug#1069472: marked as done (mpi4py-fft: FTBFS on armhf: tests fail)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 18:03:56 +0200
with message-id <9752a5007e505b40ac4ff58c858c3...@debian.org>
and subject line Re: Bug#1069472 mpi4py-fft: FTBFS on armhf: tests fail
has caused the Debian Bug report #1069472,
regarding mpi4py-fft: FTBFS on armhf: tests fail
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.)


-- 
1069472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi4py-fft
Version: 2.0.5-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/build/texinfo'
> makeinfo --no-split -o 'mpi4py-fft.info' 'mpi4py-fft.texi'
> mpi4py-fft.texi:1706: warning: could not find @image file 
> `mpi4py-fft-figures//<>/build/texinfo/.doctrees/images/feaa82f44023d4f401d0d133eb689f35762c6507/mpi4py-fft.txt'
>  nor alternate text
> make[2]: Leaving directory '/<>/build/texinfo'
> sed 
> "s|src=\"\(.*\).png\"|src=\"/usr/share/doc/python3-mpi4py-fft/html/_images/\1.png\"|g"
>  -i build/texinfo/mpi4py-fft.info
> sed "s|src=\"\(.*\).svg\"|src=\"\"|g" -i build/texinfo/mpi4py-fft.info
> sed "s|alt=\"Documentation Status\" 
> src=\"https://readthedocs.org/projects/mpi4py-fft/badge/?version=latest\;|alt=\"Latest
>  Documentation\" src=\"\"|" -i build/html/*.html
> sed "s|src=\"https://circleci.com.*svg\;|src=\"\"|" -i build/html/*.html
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd 
> /<>/.pybuild/cpython3_3.12_mpi4py-fft/build; python3.12 -m 
> unittest discover -v 
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-21:102862] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> [ip-10-84-234-21:102861] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start 
> a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
> [ip-10-84-234-21:102861] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start 
> a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
> --
> It looks like orte_init failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during orte_init; some of which are due to configuration or
> environment problems.  This failure appears to be an internal failure;
> here's some additional information (which may only be relevant to an
> Open MPI developer):
> 
>   orte_ess_init failed
>   --> Returned value Unable to start a daemon on the local node (-127) 
> instead of ORTE_SUCCESS
> --
> --
> It looks like MPI_INIT failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during MPI_INIT; some of which are due to configuration or environment
> problems.  This failure appears to be an internal failure; here's some
> additional information (which may only be relevant to an Open MPI
> developer):
> 
>   ompi_mpi_init: ompi_rte_init failed
>   --> Returned "Unable to start a daemon on the local node" (-127) instead of 
> "Success" (0)
> --
> *** An error occurred in MPI_Init_thread
> *** on a NULL communicator
> *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
> ***and potentially your MPI job)
> [ip-10-84-234-21:102861] Local abort before MPI_INIT completed completed 
> successfully, but am not able to aggregate error messages, and not able to 
> guarantee that all other processes were killed!
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12_mpi4py-fft/build; python3.12 -m 
> unittest discover -v 
> I: pybuild base:311: cd 
> 

Processed: Re: scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: execute_after_dh_auto_install] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #1069377 [src:scipy] scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: 
execute_after_dh_auto_install] Error 1
Ignoring request to alter tags of bug #1069377 to the same tags previously set

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

Bug#1069377: scipy: FTBFS on arm64: make[1]: *** [debian/rules:161: execute_after_dh_auto_install] Error 1

[Drew Parsons]

Source: scipy
Followup-For: Bug #1069377
Control: tags -1 ftbfs

This is an odd error.  Looks as if the behaviour changed in respect to
which exception gets emitted.

There's a new release needing to get packaged. Likely it resolves the
issue.

Bug#1069445: marked as done (h5py: FTBFS on armhf: tests fail)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 17:54:42 +0200
with message-id 
and subject line Re: Bug#1069445 h5py: FTBFS on armhf: tests fail
has caused the Debian Bug report #1069445,
regarding h5py: FTBFS on armhf: tests fail
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.)


-- 
1069445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h5py
Version: 3.10.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=/<>/.pybuild/cpython3_3.11_h5py_mpi/build mpirun -n 1 
> /usr/bin/make -C docs html
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-235:3065217] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> make[1]: *** [debian/rules:112: execute_after_dh_auto_build-indep] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/h5py_3.10.0-1_unstable-armhf.log

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

This error is in openmpi not h5py.  This specific error is now fixed.

Closing since not a bug in h5py.--- End Message ---

Bug#1070334: marked as done (libnet-frame-device-perl needs network access during build)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 15:49:22 +
with message-id 
and subject line Bug#1070334: fixed in libnet-frame-device-perl 1.12-2
has caused the Debian Bug report #1070334,
regarding libnet-frame-device-perl needs network access during build
to be marked as done.

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

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


-- 
1070334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-frame-device-perl
Version: 1.12-1
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org

Hi,

libnet-frame-device-perl fails to build with no network connection:

1..1
# Running under perl version 5.038002 for linux
# Current time local: Sat Apr 27 12:53:04 2024
# Current time GMT:   Sat Apr 27 12:53:04 2024
# Using Test.pm version 1.31
ok 1 # skip Test::Pod 1.00 required for testing
ok
Net::Frame::Device: updateFromDefault: unable to get dnet

This can be tested with the sbuild unshare backend.

Cheers Jochen
--- End Message ---
--- Begin Message ---
Source: libnet-frame-device-perl
Source-Version: 1.12-2
Done: Étienne Mollier 

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

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

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated 
libnet-frame-device-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 17:24:57 +0200
Source: libnet-frame-device-perl
Architecture: source
Version: 1.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Étienne Mollier 
Closes: 1070334
Changes:
 libnet-frame-device-perl (1.12-2) unstable; urgency=medium
 .
   * loopback-test.patch: new: fix test failures.
 The test suite relies on the existence of network interfaces leading
 to Internet.  However this may not be the case in Debian build
 environment.  This changes slightly alter the test suite to allow
 running against loopback interfaces, which are expected to be always
 available. (Closes: #1070334)
   * Set Rules-Requires-Root: no.
   * d/control: declare compliance to standards version 4.7.0.
   * d/control: set myself as uploader.
Checksums-Sha1:
 a68b39eaab1e6a4be63ff72f0fd47592cd22c1de 2637 
libnet-frame-device-perl_1.12-2.dsc
 e95b3c2f08328f4168b774178743a6618aeb0cd9 3452 
libnet-frame-device-perl_1.12-2.debian.tar.xz
Checksums-Sha256:
 df985f9c6aa46b7a5516b6f4bfd25722f2e1dd3d940a13744003a786ac9708e0 2637 
libnet-frame-device-perl_1.12-2.dsc
 009aa4b21c7ce4fdf19baedfdf1c0be7693b2fb25392dc3ada667999ba8c798f 3452 
libnet-frame-device-perl_1.12-2.debian.tar.xz
Files:
 21f467d082a704210e1531543c8ba8eb 2637 perl optional 
libnet-frame-device-perl_1.12-2.dsc
 e5faddc2d88d7cb9606bc6ab9346f200 3452 perl optional 
libnet-frame-device-perl_1.12-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmY2VG8UHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqaTg//RS6rJjI9kR1uSMPsf2oLETJr4rSO
QLKLFXUCI8WY/T+Aa8tCWUsg4qim+3VPkGqMTNv014RUTv5cytVbp9JfKg/4njQG
Mhq2BSDErJ8GhSMT2kzojyJ2ylTq9E01m17S1f81FdrNnMBoJaK7zYNSdsFqhVnt
jAh6xeLH5MW/l+nKH4fw6xQ19oj0D3YzvgO2+QGJIupKMx/xLEXx+u9HOOWTgS7y
RfitDijsLwHflJdevC7UnxjntrnoM1E0aM1PG8Z93GjlnfXdwZnS758T5kFYraIG
QNnBQnV1xzC609pbAd3gDmHM7GEAieNGdnJdF3/0Ts8RoZkT7MgvwFkASCLc7+R/
/sKL0aXqikFwQ4vdCbTzjpgCszZfK/z0K1YQehyqqY/tkuYyhuvNKXX+xm0tgzbt
FzGsqG0gSSmAJTJ9YmNfIYhPkCX3I/BdZgyesevurOzJBCC7OQ9RV9+P5I4tkF66
3zbsqoUH+meahmgQstnpRnhktLg/i5GXyGRwMJseHVZU1B6nC57eAA5FoY/wmaFP
kAGMFUoz86B14zgOe4PrA92/Zz3o4V1F2TmHCQ4+DvBRgGEJdXNaKJDviQUu9TnJ
UXcgZUe4ZmviWkwfwSlDoln2qUN5PwrnCsXFWG+rEbJEfSyMZHI44Y7zNI3U5/IK
bxjk7Lb4wHD26Nk=
=GlK7
-END PGP SIGNATURE-



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

Processed: Re: topal: FTBFS: debian/rules: debian_packaging.mk: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1067320 [src:topal] topal: FTBFS: debian/rules:8: 
/usr/share/ada/debian_packaging.mk: No such file or directory
Added tag(s) patch.

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

Bug#1067320: topal: FTBFS: debian/rules: debian_packaging.mk: No such file or directory

[Nicolas Boulenguez]

Source: topal
Followup-For: Bug #1067320
Control: tag -1 + patch

Hello.
Attachment 002 below fixes this bug.
Would you be OK with a non maintainer upload?

The other attachments are unrelated sugestions.
Would you be OK with a salsa.debian.org/debian/topal git repository?


PATH 1/10  updates the upstream part to version 82.


>From 31c2f14e91e2a01c75eb1309f17ea540ffb80571 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sat, 3 Dec 2022 18:56:23 +0100
Subject: [PATCH 02/10] Switch to dh-ada-library >= 8.2 for packaging.mk

---
 debian/control | 1 +
 debian/rules   | 3 +--
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index be7984d..53206e5 100644
--- a/debian/control
+++ b/debian/control
@@ -4,6 +4,7 @@ Priority: optional
 Maintainer: Phil Brooke 
 Build-Depends:
  debhelper-compat (= 13),
+ dh-ada-library (>= 8.2),
  gnat (>= 11),
  libreadline-dev,
  texlive,
diff --git a/debian/rules b/debian/rules
index cdd07e4..d3e38d5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,8 +4,7 @@
 
 DEB_BUILD_MAINT_OPTIONS := hardening=+all
 include /usr/share/dpkg/buildflags.mk
-include /usr/share/dpkg/buildopts.mk
-include /usr/share/ada/debian_packaging.mk
+include /usr/share/ada/packaging.mk
 
 # Compile Ada and C with the same compiler.
 CC := gnatgcc
-- 
2.39.2


>From a9e088d51c8f95a9e7cd60bee7e31f9e167834ed Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sat, 3 Dec 2022 18:57:35 +0100
Subject: [PATCH 03/10] Set CC from gnat version without the deprecated gnatgcc
 symbolic link

gcc-$MAJOR is also specific to Debian, but not to Ada.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index d3e38d5..b29f0ea 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,7 +7,7 @@ include /usr/share/dpkg/buildflags.mk
 include /usr/share/ada/packaging.mk
 
 # Compile Ada and C with the same compiler.
-CC := gnatgcc
+CC := gcc-$(DEB_GNAT_VERSION)
 
 # Upstream Makefile insists on rebuilding everything everytime.
 # SOURCE_DATE_EPOCH (set by debhelper) and the -m gnatmake option may
-- 
2.39.2


>From 6a3416662d4142d461f6c59bdaca4c3e495f59ff Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Wed, 20 Jul 2022 14:56:41 +0200
Subject: [PATCH 04/10] Drop full texlive from build dependencies

It was now redundant with more specific dependencies.
---
 debian/control | 1 -
 1 file changed, 1 deletion(-)

diff --git a/debian/control b/debian/control
index 53206e5..5669b2f 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,6 @@ Build-Depends:
  dh-ada-library (>= 8.2),
  gnat (>= 11),
  libreadline-dev,
- texlive,
  texlive-latex-base,
  texlive-latex-extra,
  texlive-fonts-recommended,
-- 
2.39.2


>From 2946bec7938ae412ac7cf632a2f2982a6b79355d Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Wed, 20 Jul 2022 14:57:05 +0200
Subject: [PATCH 05/10] Sort build dependencies

Dpkg supports the extra comma exactly for this purpose.
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 5669b2f..00262aa 100644
--- a/debian/control
+++ b/debian/control
@@ -7,10 +7,10 @@ Build-Depends:
  dh-ada-library (>= 8.2),
  gnat (>= 11),
  libreadline-dev,
+ texlive-fonts-extra,
+ texlive-fonts-recommended,
  texlive-latex-base,
  texlive-latex-extra,
- texlive-fonts-recommended,
- texlive-fonts-extra
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Homepage: https://www.zircon.org.uk/topal/
-- 
2.39.2


>From acb27a97b77357e5a17617c778119151161468de Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sat, 3 Dec 2022 19:18:57 +0100
Subject: [PATCH 06/10] Remove some trailing whitespaces

---
 debian/changelog | 1 -
 debian/rules | 1 -
 2 files changed, 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 03c854b..ba63f7a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -290,4 +290,3 @@ topal (0.6.4-1) unstable; urgency=low
   * Initial Release (closes: #143319).
 
  -- Phil Brooke   Sun, 21 Apr 2002 14:29:05 +
-
diff --git a/debian/rules b/debian/rules
index b29f0ea..c8539a8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -37,4 +37,3 @@ override_dh_auto_install:
 .PHONY: override_dh_installchangelogs
 override_dh_installchangelogs:
dh_installchangelogs Changelog.html
-
-- 
2.39.2


>From 6934d431d7d4efde5a7a2e2095e879d6488a083d Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Sun, 27 Aug 2023 14:03:48 +0200
Subject: [PATCH 07/10] Bump Standards-Version

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 00262aa..abc38ee 100644
--- a/debian/control
+++ b/debian/control
@@ -11,7 +11,7 @@ Build-Depends:
  texlive-fonts-recommended,
  texlive-latex-base,
  texlive-latex-extra,
-Standards-Version: 4.6.1
+Standards-Version: 4.7.0
 Rules-Requires-Root: no
 Homepage: https://www.zircon.org.uk/topal/
 
-- 

Processed: Re: mpich: libpmix-dev only available on 64-bit architectures

[Debian Bug Tracking System]

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

> severity 1070318 normal
Bug #1070318 [src:mpich] mpich: libpmix-dev only available on 64-bit 
architectures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: slurm-wlm-contrib: libpmix-dev only available on 64-bit architectures

[Debian Bug Tracking System]

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

> severity 1070320 normal
Bug #1070320 [src:slurm-wlm-contrib] slurm-wlm-contrib: libpmix-dev only 
available on 64-bit architectures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1070270: riseup-vpn: client no longer works due to cert verification problem

[Nilesh Patra]

Hi Matt,

Quoting Matt Taggart:
>  Package: riseup-vpn
>  Version: 0.21.11+ds1-5+b1
>  Severity: grave
>  
>  When attempting to run the bookworm riseup-vpn package, it fails to 
>  connect to riseup's servers and gives the following output:
>  
>  2024/05/01 18:21:23 Error fetching eip v3 
>  json:https://api.black.riseup.net/3/config/eip-service.json
>  
>  My understanding is that this is due to the package failing to be able 
>  to verify the current LetsEncrypt cert that host is using. More details at
>  
>  https://0xacab.org/leap/bitmask-vpn/-/issues/768
>  
>  (supposedly the current upstream snap has this fixed, but I haven't 
>  tried it)
>  
>  As this breaks what the package is supposed to do (at least when using 
>  riseup as provider, maybe there is a way to point it elsewhere?) I think 
>  this is grave. Also I think it might be a good candidate for being fixed 
>  in a stable release update.

If I am not mistaken, as per the said, issue, it is fixed in the commit
referenced here, right?


https://0xacab.org/leap/bitmask-vpn/-/commit/14cf64b10a97c29688f252a7d9d3481c8484aa1d

I tried this in my testing system and it seems I am able to connect to the VPN
with this patch applied. Can you confirm?

Consequently, I also did some work to cherry-pick this and prepare a stable-p-u
upload (not yet uploaded, will do after confirmation) and pushed my changes
at[1]. I have also compiled the `.deb` for stable and it is ready to be
consumed[2]. Do you think you could ask someone to check the same?

Other than that, I also tried to update the package in unstable to the latest
version to fixup this properly. I was able to build it, pushed my changes
here[3] and the `.deb` is available here[4]. Again, if you/someone else could
try this, it'd be great. It is working for me on my debian/testing system.

I would have attemped the update much sooner but unfortunately an update with
0xacab's gitlab broke my d/watch file and I did not notice a new version is out
there sooner.

I was thinking to go ahead with an upload, but there are a few things that I
would like to clarify before I do so (btw thanks to the maintainers for
committing a patch to use with qt6.4):

1. Why is the default provider set to "provider = bitmask" in
providers/vendor.conf? This leads to building the binary called bitmask-vpn
instead of riseup-vpn. Is there a thought of changing the binary name?

In current stage it points to just dummy APIs and hence I overrode it in d/rules
to build riseup-vpn instead.

2. In the vendor/gitlab.com/yawning/obfs4.git/ package, there are 3 license.
BSD-2-Clause, BSD-3-Clause and also GPL-3 for
vendor/gitlab.com/yawning/obfs4.git/internal/x25519ell2/x25519ell2.go - so what
exactly is the exact license? Is it redistributable under all the three? (I
don't think so?)

[1]: 
https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/bookworm-pu?ref_type=heads
[2]: https://people.debian.org/~nilesh/riseup-vpn-stable/
[3]: 
https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/sid?ref_type=heads
[4]: https://people.debian.org/~nilesh/riseup-vpn-0.24.5/

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: Bug#1070334 marked as pending in libnet-frame-device-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070334 [src:libnet-frame-device-perl] libnet-frame-device-perl needs 
network access during build
Added tag(s) pending.

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

Bug#1070334: marked as pending in libnet-frame-device-perl

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libnet-frame-device-perl/-/commit/b13569b50af94c9f812be0ba383eeb950557d914


loopback-test.patch: new: fix test failures.

The test suite relies on the existence of network interfaces leading
to Internet.  However this may not be the case in Debian build
environment.  This changes slightly alter the test suite to allow
running against loopback interfaces, which are expected to be always
available.

Closes: #1070334


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070334

Processed: Re: Bug#1070334: libnet-frame-device-perl needs network access during build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1070334 [src:libnet-frame-device-perl] libnet-frame-device-perl needs 
network access during build
Added tag(s) patch.

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

Bug#1070334: libnet-frame-device-perl needs network access during build

[Étienne Mollier]

Control: tags -1 + patch

Étienne Mollier, on 2024-05-03:
> Has someone an idea of better approach?

Answering to myself, the test suite does not actually attempt to
access the Internet, but it does attempt to access the device on
the build machine that can route by default to 1.1.1.1.  This is
not because it is a Cloudflare DNS, but merely because it is the
first usable ipv4 available at hand.  Especially in chroot-mode
unshare, there are no device leading to Internet exposed, thus
no device able to route to 1.1.1.1 with the default object
instanciation routine.

It turns out that the class can be told to construct objects
that refer to the loopback interface by asking for routes to the
loopback network (127/8 in ipv4, ::1/64 in ipv6).  I prepared a
patch in this direction and consider uploading soon.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Allman Brothers Band - Statesboro Blues
Description: fix build failure when no network interfaces are available.
 On buildd systems using sbuild chroot mode unshare, the network interface
 leading to Internet is not exposed.  However the default construction method
 for instanciating Net::Frame::Devices relies on the existence of a network
 interface able to route to 1.1.1.1.  This change adjusts the test suite items
 failing when not such interfaces are available, by trying to refer to loopback
 interfaces instead.  Note this slightly changes the meaning of the
 t/04-new-default.t, as it does not test the default behavior anymore, but it
 tests the behavior with ipv6 targets instead.
 .
 This addresses a Debian infrastructure specific behavior, probably not much
 worth forwarding upstream.

Author: Étienne Mollier 
Bug-Debian: https://bugs.debian.org/1070334
Forwarded: not-needed
Last-Update: 2024-05-04
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- libnet-frame-device-perl.orig/t/05-new-target.t
+++ libnet-frame-device-perl/t/05-new-target.t
@@ -2,7 +2,7 @@
 BEGIN { plan(tests => 1) }
 
 use Net::Frame::Device;
-my $d = Net::Frame::Device->new(target => '2.2.2.2') or die("Device::new");
+my $d = Net::Frame::Device->new(target => '127.1.1.1') or die("Device::new");
 print $d->cgDumper if $d->can('cgDumper');
 
 ok(1);
--- libnet-frame-device-perl.orig/t/04-new-default.t
+++ libnet-frame-device-perl/t/04-new-default.t
@@ -2,7 +2,7 @@
 BEGIN { plan(tests => 1) }
 
 use Net::Frame::Device;
-my $d = Net::Frame::Device->new or die("Device::new");
+my $d = Net::Frame::Device->new(target6 => '::1') or die("Device::new");
 print $d->cgDumper if $d->can('cgDumper');
 
 ok(1);


signature.asc
Description: PGP signature

Bug#1070369: sssd: CVE-2023-3758

[Salvatore Bonaccorso]

Source: sssd
Version: 2.9.4-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/SSSD/sssd/pull/7302
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for sssd.

CVE-2023-3758[0]:
| A race condition flaw was found in sssd where the GPO policy is not
| consistently applied for authenticated users. This may lead to
| improper authorization issues, granting or denying access to
| resources inappropriately.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3758
https://www.cve.org/CVERecord?id=CVE-2023-3758
[1] https://github.com/SSSD/sssd/pull/7302
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2223762
[3] 
https://github.com/SSSD/sssd/commit/e1bfbc2493c4194988acc3b2413df3dde0735ae3 

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1069984: marked as done (alire: Build-depends on NBS package libgnatcoll21-dev)

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 17:00:25 +0200
with message-id 

and subject line Bug#1069984: alire: Build-depends on NBS package 
libgnatcoll21-dev
has caused the Debian Bug report #1069984,
regarding alire: Build-depends on NBS package libgnatcoll21-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.)


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

The package libgnatcoll21-dev has been renamed to libgnatcoll-dev.  Once
libgnatcoll21-dev is decfufted, it will FTBFS.  Please update your build
depends.

Scott K
--- End Message ---
--- Begin Message ---
Version: 1.2.1-1.1

It was fixed by Nicolas Boulenguez as part of the gnat-13 transition
on 24 Jan 2024.--- End Message ---

Bug#1070365: lyskom-elisp-client: FTBFS: tries to write to /usr/local

[Andreas Beckmann]

Source: lyskom-elisp-client
Version: 0.48+git.20231226.364902c3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

lyskom-elisp-client FTBFS in the minimal chroots used by the buildds:

https://buildd.debian.org/status/package.php?p=lyskom-elisp-client

...
cp lyskom-0.48+git.20231226.364902c3.el lyskom-0.48+git.20231226.364902c3.elc 
/usr/local/share/emacs/site-lisp
cp: cannot create regular file 
'/usr/local/share/emacs/site-lisp/lyskom-0.48+git.20231226.364902c3.el': 
Permission denied
cp: cannot create regular file 
'/usr/local/share/emacs/site-lisp/lyskom-0.48+git.20231226.364902c3.elc': 
Permission denied
make[1]: *** [Makefile:68: install] Error 1

make install should install to debian/tmp or similar, but not to
/usr/local

Andreas

PS: Hint: try building the package locally in a minimal buildd chroot
using pbuilder or sbuild

Bug#1052090: marked as done (gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 46)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 14:46:23 +
with message-id 
and subject line Bug#1070323: Removed package(s) from unstable
has caused the Debian Bug report #1052090,
regarding gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME 
Shell 46
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.)


-- 
1052090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-bluetooth-quick-connect
Version: 36-2
Severity: serious
Tags: trixie sid upstream
Forwarded: https://github.com/bjarosze/gnome-bluetooth-quick-connect/issues/88
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-45
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org

As with every 6-month GNOME Shell release cycle, extensions will need to
be updated for GNOME Shell 45, which is currently being prepared in
experimental. A porting guide is available here:
https://gjs.guide/extensions/upgrading/gnome-shell-45.html

For the 44 -> 45 transition, most or all extensions will need
incompatible code changes, because GNOME Shell has switched from
non-standard gjs modules ("const Foo = imports.gi.Foo") to ECMAScript
modules ("import Foo from 'gi://Foo'") and all extensions need to do
the same. This means most or all extensions will split into a branch
for Shell <= 44 (which might not be maintained upstream any more) and
a branch for Shell >= 45.

I don't intend to put time into this change myself, because I no longer
use this extension (see #1043008), so I'm marking this as serious already
(justification: "in the package maintainer's opinion, makes the package
unsuitable for release"). If anyone else in the GNOME team wants to see
this extension stay available in Debian, now is your chance to take over
the package, at which point the severity of this bug becomes your choice.

If nobody steps up to maintain it, I will ask for this extension to be
removed when we are ready for the GNOME Shell 45 transition.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 36-2+rm

Dear submitter,

as the package gnome-shell-extension-bluetooth-quick-connect has just been 
removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#1069984: alire: Build-depends on NBS package libgnatcoll21-dev

[Nicolas Boulenguez]

Source: alire
Followup-For: Bug #1069984

Hello.

This bug is already fixed in 1.2.1-1.1.
The ideal way to close a bug is usually in debian/changelog, but this
bug was open after its fix has been uploaded to experimental,
so you should probably close it as described at
https://www.debian.org/Bugs/Developer#closing
with a mail to 1069984-d...@bugs.debian.org starting with
Version: 1.2.1-1.1

The 'debian/ 1.2.1-2' tag is only informative, it triggers no actual
upload.
However, its current contents are incorrect.
debian/changelog contains the same version twice.
Please fix this, then I will sponsor an upload and you will tag the
uploaded state as 'debian/1.2.1-2+really'.

Processed: Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/dask/dask/pull/11035
Bug #1068422 [python3-dask] can't import dask.dataframe - TypeError: descriptor 
'__call__' for 'type' objects doesn't apply to a 'property' object
Set Bug forwarded-to-address to 'https://github.com/dask/dask/pull/11035'.
> tags -1 fixed-upstream patch
Bug #1068422 [python3-dask] can't import dask.dataframe - TypeError: descriptor 
'__call__' for 'type' objects doesn't apply to a 'property' object
Added tag(s) patch and fixed-upstream.

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

Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

[Rebecca N. Palmer]

Control: forwarded -1 https://github.com/dask/dask/pull/11035
Control: tags -1 fixed-upstream patch

Thanks and probably yes (but I haven't tested that fix myself), as while 
it didn't happen in 3.11.8, it *does* happen in 3.11.9:

https://ci.debian.net/packages/d/dask/unstable/amd64/46185892/

Bug#1068610: dico: binary-all FTBFS

[Andreas Beckmann]

Followup-For: Bug #1068610
Control: tag -1 pending

Hi,

I've taken Holgers patch and imported it into the git repository on
salsa and uploaded it to DELAYED/2 to make progress with the t64
transition. Please let me know if I should delay it longer.
I've also fixed building the package twice in a row one the way.


Andreas

Processed: Re: dico: binary-all FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068610 [src:dico] dico: binary-all FTBFS
Added tag(s) pending.

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

Bug#1068057: marked as done (libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! ))

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 15:34:59 +0200
with message-id 
and subject line close 1068057
has caused the Debian Bug report #1068057,
regarding libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at 
compile time! )
to be marked as done.

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

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


-- 
1068057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtkada
Severity: serious
Tags: ftbfs
Control: found -1 24.0.0-2   
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

libgtkada fails to build on armel.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=libgtkada=armel=24.0.0-2=1711025590=0

Regards,
--- End Message ---
--- Begin Message ---
Thanks for reporting.
The problem was caused by the time_t64 transition in libgnat.
It has been fixed and libgtkada built on armhf.--- End Message ---

Bug#1065529: marked as done (interimap: Testsuite fails with openssl 3.2)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 13:34:29 +
with message-id 
and subject line Bug#1065529: fixed in interimap 0.5.7-3
has caused the Debian Bug report #1065529,
regarding interimap: Testsuite fails with openssl 3.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.)


-- 
1065529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: interimap
Version: 0.5.7-2
Severity: important
Tags: sid
control: affects -1 src:openssl
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-3.2

interimap's testsuite fails with OpenSSL 3.2, which is currently in
experimental, for the tests:

SSL_CAfile/$SSL_CERT_FILE... FAILED
TLS servername extension (SNI)... FAILED

Full log at
https://ci.debian.net/packages/i/interimap/unstable/amd64/43404948/

I'm currently puzzled where to look at. Could you please have a look?

Sebastian
--- End Message ---
--- Begin Message ---
Source: interimap
Source-Version: 0.5.7-3
Done: Guilhem Moulin 

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

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

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated interimap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 14:41:54 +0200
Source: interimap
Architecture: source
Version: 0.5.7-3
Distribution: unstable
Urgency: medium
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Closes: 1065529 1067763
Changes:
 interimap (0.5.7-3) unstable; urgency=medium
 .
   * d/patches:
 + Add upstream patch to generate X.509 version 3 CA prior to running the
   test suite. (Closes: #1065529)
 + Add patch from Simon Chopin to fix struct flock & timeval packing on
   armhf. (Closes: #1067763, LP: #2059120)
   * Update Standards-Version to 4.7.0 (no changes necessary).
Checksums-Sha1:
 bea0628addc5ca825e06f30f66fc5be596f931df 2361 interimap_0.5.7-3.dsc
 b6065c89d00acaf652f05af31b7cda4b9e2d1198 17700 interimap_0.5.7-3.debian.tar.xz
 77e47ac0e8d2761551341b62e83816193231c067 7828 interimap_0.5.7-3_amd64.buildinfo
Checksums-Sha256:
 1c3b29222cc619fd73238cc324e51fe99c9ef2b6f21e56ae4c0b591ef8971736 2361 
interimap_0.5.7-3.dsc
 692a62c858d95de5ab80f282bd58635eb16d89a639cff8bb5a8aef4064b6f89f 17700 
interimap_0.5.7-3.debian.tar.xz
 3e36fc26bf29754a6672e6bd1d0af2fa0cd51f36ec5fa92ca965dd2770456dfe 7828 
interimap_0.5.7-3_amd64.buildinfo
Files:
 29e84018ea728c48c3a34843a7e6f25e 2361 mail optional interimap_0.5.7-3.dsc
 8362f9a36e14a2b28d803a7e08054179 17700 mail optional 
interimap_0.5.7-3.debian.tar.xz
 53093f57368de987053fc5cf05a2e03f 7828 mail optional 
interimap_0.5.7-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmY2LeAACgkQ05pJnDwh
pVJdnRAAuXQxJiW2Ehfd058IobfLD0dpFbZqXDX2UPi4FPY8vcyZg7GKQNMFU4YA
OoHX77t/GMHNnZw7eOwYowhmaXrU8DZb7CkY6rvRHkB4pCA3zffJXGdcB27ilSZ5
vQfSLKD0xIKbD+hLmVhNuwMt7I0EvJ0r2z3w7ML0LEMqC6o9AwzdiKIDkQeJkrWp
TSEw5KzmCvzv6A3/19igcMoUn4C1I35nlcZcpQ5MEKXY6aY6zqrru6nBiExDbOnc
lTYftq/AGQaaLTKuJ2RQlN8xpGhu4us/OVxN1AbhpPBKKgGLvAWNv5FZVdMHn+c6
/HIAEz4QEDRw7uy70zZQhbaAgWzd/yrCUqxQgE3Qa6Vg+wfkig/6O3PmMn0SSNab
5peJuWdm0NrTYM1gBkDXb2XatgyWSKTmZr5zeJTYdJAUe9AznjeArEm4CUYDpHuI
Xjswjq/fbm0ZI/BWYzd8LzAKJcSgrfufVhtkkcogOFviwyMhtHGo1CkL7S/u0Ssx
w66zu78zfRPlW+c/WzLJ6M6f+OC3TUlKWaCL40PkLK2lVEeTKHPgQLKIW9AyvDqA
qqNbFjU4TVN3qVDCWb7igiVLBe02sJQMmmIR9S6GuRJUQdA4o/JiHfgR16PPvPFT
Bpe7u2SUbczVnQxhZWt0cjU68NijTvANQcosATliN1UN4TY4IMI=
=BA/D
-END PGP SIGNATURE-



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

Processed: Re: Bug#1070331: RFS: nq/0.5-0.1 [NMU] -- Lightweight queue system

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1005961
Bug #1070331 [sponsorship-requests] RFS: nq/0.5-0.1 [NMU] -- Lightweight queue 
system
1070331 was not blocked by any bugs.
1070331 was not blocking any bugs.
Added blocking bug(s) of 1070331: 1005961

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

Bug#1066579: marked as done (yubico-pam: FTBFS: ../pam_yubico.c:657:8: error: implicit declaration of function ‘mkostemp’; did you mean ‘mkstemp’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 12:20:46 +
with message-id 
and subject line Bug#1066579: fixed in yubico-pam 2.27-1
has caused the Debian Bug report #1066579,
regarding yubico-pam: FTBFS: ../pam_yubico.c:657:8: error: implicit declaration 
of function ‘mkostemp’; did you mean ‘mkstemp’? 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc 
> -DPACKAGE_NAME=\"pam_yubico\" -DPACKAGE_TARNAME=\"pam_yubico\" 
> -DPACKAGE_VERSION=\"2.26\" -DPACKAGE_STRING=\"pam_yubico\ 2.26\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"pam_yubico\" 
> -DVERSION=\"2.26\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DHAVE_SECURITY_PAM_APPL_H=1 
> -DHAVE_SECURITY_PAM_MODULES_H=1 -DHAVE_SECURITY__PAM_MACROS_H=1 
> -DHAVE_SECURITY_PAM_MODUTIL_H=1 -DHAVE_PAM_MODUTIL_DROP_PRIV=1 
> -DHAVE_LIBLDAP=1 -DHAVE_LIBYKCLIENT=1 -DHAVE_LIBYUBIKEY=1 -DHAVE_CR=1 -I. 
> -I..  -I/usr/include/ykpers-1  -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o pam_yubico.lo ../pam_yubico.c
> libtool: compile:  gcc -DPACKAGE_NAME=\"pam_yubico\" 
> -DPACKAGE_TARNAME=\"pam_yubico\" -DPACKAGE_VERSION=\"2.26\" 
> "-DPACKAGE_STRING=\"pam_yubico 2.26\"" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"pam_yubico\" -DVERSION=\"2.26\" 
> -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
> -DHAVE_SECURITY_PAM_APPL_H=1 -DHAVE_SECURITY_PAM_MODULES_H=1 
> -DHAVE_SECURITY__PAM_MACROS_H=1 -DHAVE_SECURITY_PAM_MODUTIL_H=1 
> -DHAVE_PAM_MODUTIL_DROP_PRIV=1 -DHAVE_LIBLDAP=1 -DHAVE_LIBYKCLIENT=1 
> -DHAVE_LIBYUBIKEY=1 -DHAVE_CR=1 -I. -I.. -I/usr/include/ykpers-1 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ../util.c  -fPIC -DPIC -o .libs/util.o
> libtool: compile:  gcc -DPACKAGE_NAME=\"pam_yubico\" 
> -DPACKAGE_TARNAME=\"pam_yubico\" -DPACKAGE_VERSION=\"2.26\" 
> "-DPACKAGE_STRING=\"pam_yubico 2.26\"" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"pam_yubico\" -DVERSION=\"2.26\" 
> -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
> -DHAVE_SECURITY_PAM_APPL_H=1 -DHAVE_SECURITY_PAM_MODULES_H=1 
> -DHAVE_SECURITY__PAM_MACROS_H=1 -DHAVE_SECURITY_PAM_MODUTIL_H=1 
> -DHAVE_PAM_MODUTIL_DROP_PRIV=1 -DHAVE_LIBLDAP=1 -DHAVE_LIBYKCLIENT=1 
> -DHAVE_LIBYUBIKEY=1 -DHAVE_CR=1 -I. -I.. -I/usr/include/ykpers-1 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ../drop_privs.c  -fPIC -DPIC -o .libs/drop_privs.o
> libtool: compile:  gcc -DPACKAGE_NAME=\"pam_yubico\" 
> -DPACKAGE_TARNAME=\"pam_yubico\" -DPACKAGE_VERSION=\"2.26\" 
> "-DPACKAGE_STRING=\"pam_yubico 2.26\"" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"pam_yubico\" -DVERSION=\"2.26\" 
> -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 

Bug#1059668: nmu FTBFS

[Alexandre Detiste]

Hi,

I upload this to allow new paramiko to migrate.

Greetings


tchet@quieter:~/deb/python-icecream$ cat debian/patches/python3.12
Forwarded: https://github.com/gruns/icecream/pull/147/files

--- a/tests/test_icecream.py
+++ b/tests/test_icecream.py
@@ -570,7 +570,7 @@
list(range(15))])

lines = err.getvalue().strip().splitlines()
-self.assertRegexpMatches(
+self.assertRegex(
lines[0],
r'ic\| test_icecream.py:\d+ in testMultilineContainerArgs\(\)',
)

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

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 13:13:00 +0200
with message-id 

and subject line FTBFS
has caused the Debian Bug report #1060963,
regarding paramiko: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/sftp.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/transport.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/ssh_exception.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/ed25519key.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/sftp_client.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/ssh_gss.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/sftp_attr.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/ecdsakey.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/ber.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/common.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/_version.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> copying paramiko/agent.py -> 
> /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
> 

Bug#1061208: marked as done (rocm-hipamd: Please upgrade to llvm-toolchain-18)

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 13:05:27 +0200
with message-id <3b21eee9-2a53-4e41-8ea8-2eec927dd...@debian.org>
and subject line Fixed in 5.7.1-1
has caused the Debian Bug report #1061208,
regarding rocm-hipamd: Please upgrade to llvm-toolchain-18
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.)


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

Source: rocm-hipamd
Severity: important

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -17.

This package depends on 15.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Version: 5.7.1-1--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 1061216 openvdb: Please upgrade to llvm-toolchain-18
Bug #1061216 [src:openvdb] Please upgrade to llvm-toolchain-17
Changed Bug title to 'openvdb: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
>
End of message, stopping processing here.

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

Processed (with 1 error): retitle

[Debian Bug Tracking System]

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

> retitle 1061205 qt6-tools: Please upgrade to llvm-toolchain-18
Bug #1061205 [src:qt6-tools] Please upgrade to llvm-toolchain-17
Changed Bug title to 'qt6-tools: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
> retitle 1061208 rocm-hipamd: Please upgrade to llvm-toolchain-18
Bug #1061208 [src:rocm-hipamd] Please upgrade to llvm-toolchain-17
Changed Bug title to 'rocm-hipamd: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
> retitle 1061212 emscripten: Please upgrade to llvm-toolchain-18
Bug #1061212 [src:emscripten] Please upgrade to llvm-toolchain-17
Changed Bug title to 'emscripten: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
> retitle 1061214 llvmlite: Please upgrade to llvm-toolchain-18
Bug #1061214 [src:llvmlite] Please upgrade to llvm-toolchain-17
Changed Bug title to 'llvmlite: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
> retitle 1061219 titron: Please upgrade to llvm-toolchain-18
Bug #1061219 [src:triton] Please upgrade to llvm-toolchain-17
Changed Bug title to 'titron: Please upgrade to llvm-toolchain-18' from 'Please 
upgrade to llvm-toolchain-17'.
> retitle 1061213 intel-graphics-compiler: Please upgrade to llvm-toolchain-18
Bug #1061213 [src:intel-graphics-compiler] Please upgrade to llvm-toolchain-17
Changed Bug title to 'intel-graphics-compiler: Please upgrade to 
llvm-toolchain-18' from 'Please upgrade to llvm-toolchain-17'.
> retitle1061216 openvdb: Please upgrade to llvm-toolchain-18
Unknown command or malformed arguments to command.
> retitle 1061215 oclgrind: Please upgrade to llvm-toolchain-18
Bug #1061215 [src:oclgrind] Please upgrade to llvm-toolchain-17
Changed Bug title to 'oclgrind: Please upgrade to llvm-toolchain-18' from 
'Please upgrade to llvm-toolchain-17'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061205
1061208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061208
1061212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061212
1061213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061213
1061214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061214
1061215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061215
1061219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Jussi Pakkanen]

On Fri, 3 May 2024 at 06:42, Shmerl  wrote:

> If real solution for this requires upstream involvement, may be it's worth 
> disabling
> these tests, until upstream is actually not broken? That would at least move 
> things
> forward, otherwise it might be stuck for who knows how long?

I am the upstream. All of this works in our CI and other distros
meaning that the only person who can reasonably fix this is also me.

Disabling tests is also not a great because it just hides the bug.
Thus other packages that actually use this functionality are going to
hit this eventually and file more bugs on Meson. That is a waste of
everybody's time and energy.

Bug#1069369: marked as done (lua-sec: FTBFS on arm64: ld: cannot find -lz: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 10:22:32 +
with message-id 
and subject line Bug#1069369: fixed in lua-sec 1.3.2-2
has caused the Debian Bug report #1069369,
regarding lua-sec: FTBFS on arm64: ld: cannot find -lz: No such file or 
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.)


-- 
1069369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-sec
Version: 1.3.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.


Relevant part (hopefully):
> /<>/debian/.dh_lua-libtool/libtool --tag=CC --mode=link 
> aarch64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/lua5.1   -Isrc -Wall -Wextra -Wl,--no-add-needed \
>   -static -o /<>/5.1-sec/app-static -I . -I 
> /<>/5.1-sec/ \
>   /usr/share/dh-lua/test/5.1/app.c 
> /<>/5.1-sec/liblua5.1-sec.la \
>   -Wl,-z,relro -lssl -lcrypto -lz -lzstd -ldl -pthread  -llua5.1-socket 
> -llua5.1 -lm -ldl 
> libtool: link: aarch64-linux-gnu-gcc -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1 -Isrc -Wall -Wextra 
> -Wl,--no-add-needed -o /<>/5.1-sec/app-static -I . -I 
> /<>/5.1-sec/ /usr/share/dh-lua/test/5.1/app.c -Wl,-z -Wl,relro  
> /<>/5.1-sec/.libs/liblua5.1-sec.a -lssl -lcrypto -lz -lzstd 
> -llua5.1-socket -llua5.1 -lm -ldl -pthread
> /usr/bin/ld: cannot find -lz: No such file or directory
> /usr/bin/ld: cannot find -lzstd: No such file or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/lua-sec_1.3.2-1_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: lua-sec
Source-Version: 1.3.2-2
Done: Victor Seva 

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated lua-sec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 11:15:28 +0200
Source: lua-sec
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: Victor Seva 
Closes: 1069369
Changes:
 lua-sec (1.3.2-2) unstable; urgency=medium
 .
   * add libz-dev and libzstd-dev to Build-Depends (Closes: #1069369)
   * update Standards-Version, no changes needed
Checksums-Sha1:
 e74ea1c86422ab264df3807dbabfa1a00f596777 1500 lua-sec_1.3.2-2.dsc
 096fcfc5cb70dd7827c65f2b0ab46d6b09d5a309 5944 lua-sec_1.3.2-2.debian.tar.xz
 a205f45e8656a8ee8d4bf56758d2c6b0ab4d3f26 6887 lua-sec_1.3.2-2_amd64.buildinfo
Checksums-Sha256:
 1b2cb098ced69783cbcbee5b64d4b66f1004babe7a081f600bf90c27329c0337 1500 
lua-sec_1.3.2-2.dsc
 a3e52fa781f73566dc3de01b78a0f6fe61f0ea2518a137aef2a2bdb73ac81bd9 5944 
lua-sec_1.3.2-2.debian.tar.xz
 

Bug#1070300: pmix_psquash_base_select failed during MPI_INIT on 32bit architectures

[Samuel Thibault]

Samuel Thibault, le ven. 03 mai 2024 19:00:22 +0200, a ecrit:
> This has been posing migration issues for quite some time, I have
> uploaded the attached fix to delayed/0.

Some of the components depend on libmca_common_libdstore which also
needs to be installed, otherwise openmpi emits some text on stderr,
which some autopkgtest don't like, I have uploaded the attached changes
to delayed/0

Samuel
diff -Nru openmpi-4.1.6/debian/changelog openmpi-4.1.6/debian/changelog
--- openmpi-4.1.6/debian/changelog  2024-05-03 18:53:52.0 +0200
+++ openmpi-4.1.6/debian/changelog  2024-05-04 11:32:26.0 +0200
@@ -1,3 +1,11 @@
+openmpi (4.1.6-13.2) unstable; urgency=medium
+
+  * Non-maintainer Upload
+  * Also install libmca_common_dstore.
+  * Do not install .la pmix files.
+
+ -- Samuel Thibault   Sat, 04 May 2024 11:32:26 +0200
+
 openmpi (4.1.6-13.1) unstable; urgency=medium
 
   * Non-maintainer Upload
diff -Nru openmpi-4.1.6/debian/rules openmpi-4.1.6/debian/rules
--- openmpi-4.1.6/debian/rules  2024-05-03 18:49:28.0 +0200
+++ openmpi-4.1.6/debian/rules  2024-05-04 11:32:26.0 +0200
@@ -288,7 +288,12 @@
echo "PMIX: install " ;  \
dh_install -p libopenmpi3t64 
$(LIBDIR)/openmpi/lib/libpmix.so.2.2.35 $(LIBDIR) ; \
dh_install -p libopenmpi3t64 /usr/share/pmix ; \
-   dh_install -p libopenmpi3t64 
/usr/lib/$(DEB_HOST_MULTIARCH)/openmpi/lib/pmix ; \
+   dh_install -p libopenmpi3t64 
"/usr/lib/$(DEB_HOST_MULTIARCH)/openmpi/lib/pmix/*.so" ; \
+   if test -f 
$(DESTDIR)/$(LIBDIR)/openmpi/lib/libmca_common_libdstore.so.1.0.2 ; then \
+   dh_install -p libopenmpi3t64 
$(LIBDIR)/libmca_common_libdstore.so.1.0.2 ; \
+   dh_link -p libopenmpi3t64
$(LIBDIR)/libmca_common_libdstore.so.1.0.2 
$(LIBDIR)/libmca_common_libdstore.so.1 ; \
+   dh_link -p libopenmpi-dev 
$(LIBDIR)/libmca_common_libdstore.so.1  $(LIBDIR)/libmca_common_libdstore.so ; \
+   fi ; \
dh_link -p libopenmpi3t64 $(LIBDIR)/libpmix.so.2.2.35 
$(LIBDIR)/libpmix.so.2  ; \
dh_link -p libopenmpi-dev $(LIBDIR)/libpmix.so.2
$(LIBDIR)/openmpi/lib/libpmix.so ; \
dh_link -p libopenmpi-dev $(LIBDIR)/libpmix.so.2
$(LIBDIR)/libpmix.so ; \

Bug#1070217: chromium: Symbol lookup error with libsnappy1v5>=1.2.0

[Martin Steigerwald]

Martin Steigerwald - 02.05.24, 16:43:28 CEST:
> Work-around for affected users:

Of course this work-around is no longer necessary.

Thank you for the quick fix, Laszlo. I appreciate it.

-- 
Martin

Bug#1070352: rust-err-derive: fails to build from source on all architectures

[Jonas Smedegaard]

Source: rust-err-derive
Version: 0.3.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package fails to build from source om all architectures.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmY1+IIACgkQLHwxRsGg
ASFEXQ/9ECTK/4Ztwvkm0XTX458Afj5nMERIk5LhOrZAoJK+uYVcTXBNPMjhlyhC
u4gk3/Gc/f+noel7Af26vpzawPaTbKSXHhcKAydjTDdTPgXNwhrgfWiqsOfOktoA
Vy6+l29wjcqwLqbDIvHCGc4wdMEsctB/w6+8zhYNkuzjXOFdY3sREl+SFfEzXql3
O8sMJHjBlisWtbqHftHVgLuk7nOmP56cNJB9a/suQ8WpX/vCawdQPrj0x2W2jT0O
QWLWrbc5Qxe0QuDbm+SeZnYlbUTqjfguP11xXc7xwo3GhRxrkMHtcuiUAjcIz/lk
hGaec5faM6BpdNOZaE3Gp94ct1fBmHt70cRuu2khbXABdvMLHmBFjzkf3iDI7Tev
FsU1AdxTiCzlYZ/l4biPmA/vdrp2KikeTwZ56xkv4jv7WtXpux1Ey4/VAeK8/wrm
Of9ENrlvhkgZdCthVy2Nt3u1eWn6kV/+BdyfNqohGoPjvQzopuuwG4elHf/3+WJz
eXynn+NhWyhb33YU12ROH2b4SxObK9olp6+Feo/fw3XIoT8A0+OnqMqBnOYYfPVW
ncBZa5/cqg0l/2L+5yRbRbSEWbf2tw7+6x3EU3KpXe5V/D/9SXp6TaM0xVdGWSJf
tgrlxcZGdRjCDEgATgumqjifhmP/0ThfXk4nNqF6byXwgEfDIJM=
=dcqX
-END PGP SIGNATURE-

Bug#1043002: marked as done (pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends)

[Debian Bug Tracking System]

Your message dated Sat, 4 May 2024 10:49:04 +0200
with message-id <01552f84-aaaf-4a84-9886-d844f14e6...@debian.org>
and subject line Re: pdm: Please replace python3-pep517 with 
python3-pyproject-hooks in Depends/Build-Depends
has caused the Debian Bug report #1043002,
regarding pdm: Please replace python3-pep517 with python3-pyproject-hooks in 
Depends/Build-Depends
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.)


-- 
1043002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdm
Version: 2.2.1+ds1-1
Severity: important

The python3-pep517 package has been replaced by python3-pyproject-hooks.
Please update your package depends and build-depends (this may required
a new upstream release - I did check and the current upstream release
supports using pyproject-hooks).

Once I request removal, I'll raise the severity of this to serious.  I
expect that by next week we'll be down to only two or three packages
left that use pep517, so I'll probably request it then.  If you need
more time to update this package, I can wait, please let me know.

Scott K
--- End Message ---
--- Begin Message ---

Version: 2.2.1+ds1-2

thanks

The bug number was missing from the changelog



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

Processed: reset severity

[Debian Bug Tracking System]

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

> severity 1016957 wishlist
Bug #1016957 [src:kbd-chooser] kbd-chooser: please add support for riscv64
Severity set to 'wishlist' from 'serious'
>
End of message, stopping processing here.

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

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

[Preuße]

Control: found -1 fq/0.9.0-2
Control: found -1 nq/0.3.1-4

On 18.02.2022 08:39, Axel Beckert wrote:

Hello,


Trying to install fq fails for me as follows:

Preparing to unpack .../archives/fq_0.0.4-2_amd64.deb ...
Unpacking fq (0.0.4-2) ...
dpkg: error processing archive /var/cache/apt/archives/fq_0.0.4-2_amd64.deb 
(--unpack):
  trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
  /var/cache/apt/archives/fq_0.0.4-2_amd64.deb

As these two "fq" seem to have completely different purposes, please
either rename one of the commands (or both) or add a Conflicts header to
conflict with the other package.



While preparing a NMU for nq Christoph Biedl pointed out, that the issue 
was solved the wrong way. According to the policy [1]


"Two different packages must not install programs with different 
functionality but with the same filenames. (...) If this case happens, 
one of the programs must be renamed. The maintainers should report this 
to the debian-devel mailing list and try to find a consensus about which 
program will have to be renamed. If a consensus cannot be reached, both 
programs must be renamed."


For now I reopen the bug, not 100% sure how to proceed. I'm not the 
maintainer of nq and I won't be able to make a strong decision like 
renaming a binary in the nq package.


Hilmar

[1] https://www.debian.org/doc/debian-policy/ch-files.html
--
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> found -1 fq/0.9.0-2
Bug #1005961 {Done: Daniel Milde } [nq,fq] nq,fq: trying to 
overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4
Marked as found in versions fq/0.9.0-2 and reopened.
> found -1 nq/0.3.1-4
Bug #1005961 [nq,fq] nq,fq: trying to overwrite '/usr/bin/fq', which is also in 
package nq 0.3.1-4
Ignoring request to alter found versions of bug #1005961 to the same values 
previously set

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

Processed: unarchive Bug#1005961

[Debian Bug Tracking System]

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

> unarchive 1005961
Bug #1005961 {Done: Daniel Milde } [nq,fq] nq,fq: trying to 
overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4
Unarchived Bug 1005961
>
End of message, stopping processing here.

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

Bug#1069878: marked as done (dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: error: too few arguments to function ‘dm_io’)

[Debian Bug Tracking System]

Your message dated Sat, 04 May 2024 07:49:11 +
with message-id 
and subject line Bug#1069878: fixed in dm-writeboost 2.2.17-0.1
has caused the Debian Bug report #1069878,
regarding dm-writeboost-dkms: kernel module fails to build for Linux 6.7.12: 
error: too few arguments to function ‘dm_io’
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.)


-- 
1069878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dm-writeboost-dkms
Version: 2.2.16-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

When installing the following packages (and its dependencies)
  linux-headers-6.7.12-amd64:amd64 6.7.12-1
  linux-image-6.7.12-amd64-unsigned:amd64 6.7.12-1
dkms fails to build dm-writeboost: please see attached make.log.

[This does not happen against the previous kernel package 
linux-image-6.7.9-amd64-unsigned.
BTW: This failure happens since kernel 6.7.11 (and 6.1.83, 6.6.23, 6.8.2 
respectively).]


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

Kernel: Linux 6.6.22 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dm-writeboost-dkms depends on:
ii  dkms  3.0.13-1

Versions of packages dm-writeboost-dkms recommends:
ii  dmsetup 2:1.02.196-1+b1
ii  kmod32-1
ii  writeboost  1.20170616-1.3

dm-writeboost-dkms suggests no packages.

-- no debconf information
DKMS make.log for dm-writeboost-2.2.16 for kernel 6.7.12-amd64 (x86_64)
Fr 26. Apr 09:58:48 CEST 2024
make -C /lib/modules/6.7.12-amd64/build 
M=/var/lib/dkms/dm-writeboost/2.2.16/build modules
make[1]: Verzeichnis „/usr/src/linux-headers-6.7.12-amd64“ wird betreten
make --no-print-directory -C /usr/src/linux-headers-6.7.12-amd64 \
-f /usr/src/linux-headers-6.7.12-common/Makefile modules
make -f /usr/src/linux-headers-6.7.12-common/scripts/Makefile.build 
obj=/var/lib/dkms/dm-writeboost/2.2.16/build need-builtin=1 need-modorder=1 
# cmd_mod /var/lib/dkms/dm-writeboost/2.2.16/build/dm-writeboost.mod
  printf '%s
'   dm-writeboost-target.o dm-writeboost-metadata.o dm-writeboost-daemon.o | 
awk '!x[$0]++ { print("/var/lib/dkms/dm-writeboost/2.2.16/build/"$0) }' > 
/var/lib/dkms/dm-writeboost/2.2.16/build/dm-writeboost.mod
# CC [M]  /var/lib/dkms/dm-writeboost/2.2.16/build/dm-writeboost-target.o
   x86_64-linux-gnu-gcc-13 
-Wp,-MMD,/var/lib/dkms/dm-writeboost/2.2.16/build/.dm-writeboost-target.o.d 
-nostdinc -I/usr/src/linux-headers-6.7.12-common/arch/x86/include 
-I./arch/x86/include/generated -I/usr/src/linux-headers-6.7.12-common/include 
-I./include -I/usr/src/linux-headers-6.7.12-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-6.7.12-common/include/uapi -I./include/generated/uapi 
-include /usr/src/linux-headers-6.7.12-common/include/linux/compiler-version.h 
-include /usr/src/linux-headers-6.7.12-common/include/linux/kconfig.h -include 
/usr/src/linux-headers-6.7.12-common/include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-6.7.12-common/= 
-std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE 
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx 
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 
-mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup 
-mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -mindirect-branch-cs-prefix 
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all 
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 
-fno-allow-store-data-races -fstack-protector-strong 
-ftrivial-auto-var-init=zero -fno-stack-clash-protection -pg -mrecord-mcount 
-mfentry -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 
-fno-strict-overflow -fno-stack-check -fconserve-stack -Wall -Wundef 
-Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type 
-Werror=strict-prototypes -Wno-format-security -Wno-trigraphs 
-Wno-frame-address -Wno-address-of-packed-member -Wframe-larger-than=2048 
-Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable 
-Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type 
-Wno-array-bounds 

Processed: severity of 1069538 is important

[Debian Bug Tracking System]

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

> # Arch: all builds are done on amd64 buildds only
> severity 1069538 normal
Bug #1069538 [src:zeroc-ice] zeroc-ice: FTBFS on armel: Gradle / Java heap space
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: found 1069439 in 3.9.1-1

[Debian Bug Tracking System]

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

> found 1069439 3.9.1-1
Bug #1069439 [src:arpack] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: 
test-suite.log] Error 1
Marked as found in versions arpack/3.9.1-1.
> thanks
Stopping processing here.

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

Processed: severity of 1058493 is grave

[Debian Bug Tracking System]

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

> severity 1058493 grave
Bug #1058493 [src:gamescope] gamescope: Please update to wlroots 0.17
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.

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