Bug#1072824: marked as done (odin FTBFS with VTK 9.3.0)

[Debian Bug Tracking System]

Your message dated Tue, 11 Jun 2024 05:04:09 +
with message-id 
and subject line Bug#1072824: fixed in odin 2.0.5-6
has caused the Debian Bug report #1072824,
regarding odin FTBFS with VTK 9.3.0
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.)


-- 
1072824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odin
Version: 2.0.5-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=odin=amd64=2.0.5-5%2Bb2=1717847424=0

...
checking for main in -lvtkIOLegacy-7.1... no
checking for main in -lvtkIOLegacy-7.0... no
checking for main in -lvtkIOLegacy-6.3... no
checking for main in -lvtkIOLegacy-6.2... no
checking for main in -lvtkIOLegacy-6.1... no
checking for main in -lvtkIOLegacy-6.0... no
checking for main in -lvtkIOLegacy-9.0... no
checking for main in -lvtkIOLegacy-9.1... no
checking for main in -lvtkIO... no
checking for main in -lvtkRendering... no
checking for main in -lvtkGraphics... no
checking for main in -lvtkFiltering... no
checking for main in -lvtkCommon... no
checking for vtkStructuredPoints.h... no
checking for vtkArrowSource.h... no
configure: error: VTK library missing
--- End Message ---
--- Begin Message ---
Source: odin
Source-Version: 2.0.5-6
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated odin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Jun 2024 06:11:40 +0200
Source: odin
Architecture: source
Version: 2.0.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Anton Gladky 
Closes: 1072824
Changes:
 odin (2.0.5-6) unstable; urgency=medium
 .
   * Team upload.
   * [65d4b30] Fix VTK9.3 compilation. (Closes: #1072824)
   * [912f77c] Minor fix in install-files
   * [bf37cb2] Refresh patches
Checksums-Sha1:
 6f46bfb6ddeab556bc59564e51ca8127cb29609d 2284 odin_2.0.5-6.dsc
 ae0d6004501b4f57a70be7e2ad7dd5c638d16c16 11024 odin_2.0.5-6.debian.tar.xz
 f7f8d75819d328de866b743bc52c7257fd0d0a85 23181 odin_2.0.5-6_source.buildinfo
Checksums-Sha256:
 5bae1b2a6e367952617b8932f9571431fa0d5e314e491eb83fe4b6d1c7bac72c 2284 
odin_2.0.5-6.dsc
 71a8871ed6c8d6c20396fb385d3630209e16c4116d07964ea3c83de66eeb6edb 11024 
odin_2.0.5-6.debian.tar.xz
 71cf24eda5e4920ca99347b3e88f89991808554ae0eec59368bc5020146c642b 23181 
odin_2.0.5-6_source.buildinfo
Files:
 32d20fa9418f10f58ce82ae7dc6dc571 2284 science optional odin_2.0.5-6.dsc
 274f9ea024e7b6b045610850518864c6 11024 science optional 
odin_2.0.5-6.debian.tar.xz
 e8e9d69870bca14bcb3702308efcd9fa 23181 science optional 
odin_2.0.5-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmZnz5AACgkQ0+Fzg8+n
/wZOuQ//UoG+viY9ecXkrCji20kOgo34qS6MaGX025wfiRO1NcwikxhGsc/ynsts
J+vq9wyLhp6uKZtTfKteJXV/elhIPpgnLZ9cUGzbLpek08RlYWobt3SB50sDSlJV
ku5NHAgbWWe25OawbnSA1qlt7uKdQ94OWo4Azkl04tg8KsN/sWpTpXYVPp9mu31/
7X7IuWwQ/x4HWbc387GGuJnfZo28gNAEuMCXjDrE3Kp9IDrugagvpPYG2AExRzwr
/+572pWbFCQc6upbZJ7HXqm/Obm1fTbmGsFKAT0RvhbDkPWGMUGbnCDyk8dv2LQm
LGvleGbXyM1cmtxCtBJxBa2jLBwjApQmoIhivLx1FGifowovjSLToOH0npzAmVDQ
U05wlE37w+QwdNbco7LX0VsSO84rgN+cetZ6FOhw4N9+wce8A41eK89brGHkhm6u
zedOELtWpDhfIs2QG6qeWi8DwcuQCQluKBzntEs9SpenIBzUMicyXr0rciKASHFs
w8ZzUegxJaXf8RWdR1lLU8UtuiPT5057KHrCNB7iD8RWJ5in4SSCNvmnmUEh4LqV
BHxDfgXz5b3W9Hv0mVjMtGe23iLUL94bIeLjhDJaGz/eCKxg9kzoq1Czh9QDRPzy
5bkIcMHs19Dg4XbrvQJyx82ERInXnMCyFkXzZl7UvaXXLh5ZgBY=
=A+Ax
-END PGP SIGNATURE-



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

Processed: Bug#1072824 marked as pending in odin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072824 [src:odin] odin FTBFS with VTK 9.3.0
Added tag(s) pending.

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

Bug#1072824: marked as pending in odin

[Anton Gladky]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/odin/-/commit/65d4b30820cd234ad26e1b753162352e38a2f62d


Fix VTK9.3 compilation. (Closes: #1072824)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072824

Bug#1070411: containerd fails to build as a normal user due to sysctl

[Reinhard Tartler]

Jochen Sprickerhof  writes:

> containerd uses sysctl during the build which fails as a normal user:
>
> === RUN   TestLinuxSandboxContainerSpec
> sandbox_run_linux_test.go:241: TestCase "spec should reflect original 
> config"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:124:
> Error Trace:
> /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:124
> 
> /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:259
> Error:  "" does not contain "0 2147483647"
> Test:   TestLinuxSandboxContainerSpec
> sandbox_run_linux_test.go:241: TestCase "host namespace"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:241: TestCase "should set supplemental groups 
> correctly"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:241: TestCase "should overwrite default sysctls"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations 
> should be set if LinuxContainerResources were provided"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations 
> should not be set if LinuxContainerResources were not provided"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations are 
> zero if the resources are set to 0"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
> --- FAIL: TestLinuxSandboxContainerSpec (0.00s)
>
> https://salsa.debian.org/go-team/packages/containerd/-/blob/debian/sid/pkg/cri/server/sandbox_run_linux_test.go#L124

Are you sure that the test is actually executing a sysctl(2) command?
Looking at the code, it seems to me that this is code is assembling a
runtime spec that the CRI implementation will then carry out.
Forthermore, the output above indicates that the assertion on line 123
actually holds, but the one on line 124 does not:

https://sources.debian.org/src/containerd/1.6.24~ds1-1/pkg/cri/server/sandbox_run_linux_test.go/#L124

The cause for this is most likely in 
https://sources.debian.org/src/containerd/1.6.24~ds1-1/pkg/cri/server/sandbox_run_linux.go/#L147.
 Here the code is explicitly checking whether it is running in in a 
usernamespace, which is exactly what 'unshare' is doing.

> This make the build fail for example in the sbuild unshare backend.

Well, technically the build of the code succeeds, but the tests don't
run in a usernamespace.

Arguably, the test could be updated to skip this assertion if running in
a user namespace.

Can you please help me understand whether, and if so since when, we have
the requirement that all packages must be buildable inside a
usernamespace and where was this announced to be release-critical?
(CC'ed debian-release for input).

I'm inclined to downgrade this bug to severity "normal" or "wishlist".

If that really needs to be fixed, I could imagine to either disable the
test, or change the test to skip that assertion if running inside a user
namespace.

I would recommend forwarding this as a bug to upsream to see how relevant
running the containerd testsuite is in a user namespace. This feels like
a rather fringe/niche use-case anyways.

Best,
-rt

Bug#1060474: marked as done (pulseaudio: Please switch Build-Depends to systemd-dev)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 23:34:05 +
with message-id 
and subject line Bug#1060474: fixed in pulseaudio 16.1+dfsg1-5.1
has caused the Debian Bug report #1060474,
regarding pulseaudio: Please switch Build-Depends to systemd-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.)


-- 
1060474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pulseaudio
Version: 16.1+dfsg1-3
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package pulseaudio declares a Build-Depends on systemd and/or
udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at .

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 16.1+dfsg1-5.1
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated pulseaudio 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: Mon, 10 Jun 2024 23:50:35 +0200
Source: pulseaudio
Architecture: source
Version: 16.1+dfsg1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Chris Hofstaedtler 
Closes: 1060474 1072960
Changes:
 pulseaudio (16.1+dfsg1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch Build-Depends to systemd-dev, fixing FTBFS. (Closes: #1060474)
   * Install systemd masking symlink and udev rule into /usr (DEP17).
 (Closes: #1072960)
Checksums-Sha1:
 cd2b3ddde49ed6387fc9061e16aad106acae0112 3778 pulseaudio_16.1+dfsg1-5.1.dsc
 1101744ad558dd81d27cfbe1284028a9cc657821 39496 
pulseaudio_16.1+dfsg1-5.1.debian.tar.xz
 a609a4683fa33c4fa7fa9cd3d510e5b210d64a1c 26016 
pulseaudio_16.1+dfsg1-5.1_arm64.buildinfo
Checksums-Sha256:
 9848c855d027c638f0f6003ace1f6c75b3c81aac643eb06a49d5ff7169a3140a 3778 
pulseaudio_16.1+dfsg1-5.1.dsc
 d0c5f3b92c79dd253d181eab6ce813db0208561081c6d666cc5548f6dc9aac3b 39496 
pulseaudio_16.1+dfsg1-5.1.debian.tar.xz
 acb525f84ff8a9ea55d3c5817cf69a6e4300b4382250e2945f5ec7c746f1d945 26016 
pulseaudio_16.1+dfsg1-5.1_arm64.buildinfo
Files:
 15d210aead13635cb5c18f4fbd323e38 3778 sound optional 
pulseaudio_16.1+dfsg1-5.1.dsc
 b415300084897d0619c78c328ba503a9 39496 sound optional 
pulseaudio_16.1+dfsg1-5.1.debian.tar.xz
 5b09863e7ed4963f8599c14416f60233 26016 sound optional 
pulseaudio_16.1+dfsg1-5.1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZnfKYACgkQXBPW25MF
LgOt+A//bUaq7RBYwEMFiixZOE69YVZSktzxVkHrjhHYGFnxPa57xtxbeyL6Y8Hx
eS7lpbVzuyWp0ORsPcVk5Q0E9hISk3V2U7AkccQM7+cdXTYpu85R4r0CsaLVSLfi
8effwPUbCQ720X2xhF69gQ/faTAD3CwOSmKrlpnpGt+C5TyW5T8Yvo62KIU80oyn

Bug#1072766: rust-alacritty: FTBFS: unsatisfiable build-dependencies

[James McCoy]

On Fri, Jun 07, 2024 at 05:23:32PM GMT, Santiago Vila wrote:
> 
> [...]
> 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: librust-copypasta-0.8+wayland-dev 
> (>= 0.8.1-~~) but it is not installable
>Depends: librust-copypasta-0.8+x11-dev (>= 
> 0.8.1-~~) but it is not installable
>Depends: librust-copypasta-0.8-dev (>= 
> 0.8.1-~~) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.
> E: Package installation failed
> Not removing build depends: cloned chroot in use
> 
> 

I missed this relationship when updating copypasta.

Rather than fix this directly in unstable's current alacritty package,
I'm going to finish the work to get the version in experimental uploaded
to unstable.  This will address the issue, since experimental's
alacritty uses copypasta 0.10.

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

Bug#1063647: marked as done (sysconfig: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 23:20:16 +
with message-id 
and subject line Bug#1063647: fixed in sysconfig 0.0.14+nmu1
has caused the Debian Bug report #1063647,
regarding sysconfig: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
1063647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysconfig
Version: 0.0.14
Severity: serious
Justification: Debian Policy section 4.9
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
.
(The severity of this bug at the time of the mass bug filing was set to
'important', and bumped to 'serious' after a month, but given that quite
some time has passed, I'm just setting it directly to 'serious' now, as
I'm planning to remove the fallback workaround for these targets in the
next dpkg upload.)

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: sysconfig
Source-Version: 0.0.14+nmu1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated sysconfig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 31 May 2024 22:22:45 +
Source: sysconfig
Architecture: source
Version: 0.0.14+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Debian S/390 Team 
Changed-By: Bastian Germann 
Closes: 1007056 1063647
Changes:
 sysconfig (0.0.14+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert to source format 3.0. (Closes: #1007056)
   * d/rules: Add missing targets. (Closes: #1063647)
Checksums-Sha1:
 584cf57bfca136907452e2d8ff4dff0d952f7d08 1361 sysconfig_0.0.14+nmu1.dsc
 97f1e0229a1326b70a3445d748b0fcbf37644cec 8788 sysconfig_0.0.14+nmu1.tar.xz
 4eeece881c40a4d71bf1590b5b2c4a933fd12116 5331 
sysconfig_0.0.14+nmu1_source.buildinfo
Checksums-Sha256:
 40e1a385a37a6ba0f6039c339a68ac7a3d4cb708916932cfde99bfcf4479d0e2 1361 
sysconfig_0.0.14+nmu1.dsc
 dfea559a222313c5415491f10064b734b69b1845742df0620a64d059be49f2ee 8788 
sysconfig_0.0.14+nmu1.tar.xz
 0cd902d5dd4b11ccc5803685a7e4a19a02241b006983246c09b1c33ef7d804b2 5331 
sysconfig_0.0.14+nmu1_source.buildinfo
Files:
 702db5283d2c7803e1892b20b9352c6f 1361 admin optional sysconfig_0.0.14+nmu1.dsc
 c1b9a795ea519e56c765b97f5b644456 8788 admin optional 
sysconfig_0.0.14+nmu1.tar.xz
 36b7e9f443bc2dd24a3c93696c1f8dd6 5331 admin optional 
sysconfig_0.0.14+nmu1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZaT9cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFEU3DADoX24RGJaSDHSn0dcmDKNf2F0Su7tY8Mkd
cK7uxuvbCYN7Pkoo+Zn59LLnglSUOx8hoHasXXmA3a6yDGxm+oLcnkU6b7YuuZlN
c7RfpqXhjm8hZPZFH/4E3x9G3AE4lxIAOZy2edwfhx5uxZRzXUWgXbx2eamEjHXt
Bz1QbHm73TleyPJSDu0ExCmO0k2wmKY8bEiVKAqKPS+LUYTcTJxwO5x7M3RJJliz
FaiGcRgdD56SGdqmzks1ZMYQavs8ob9xTB+bWgLxwnk/Q40BcoMguQPBeLUYxjdg
TkdpXBxCHrl2FbYNF08rx00SnOPd9gq1UPKn7+QNAtaIEdUWm9n9C3qr4zLj6haQ
F6r5nbpAVZ8scIP76Ogkp26O4d6+u0Bcdnh+Eo3c9mwJOcYM3My2U5jTylF1muKN
LMJ9e+7ZtUpsK9Kw3Pg1XKfBStM7kkbySzmbfmeM0QWaZnbrU+/kvYb74RXdh90L
e0N32M/94P/Vo6izC1fCMkXZGKE+oxM=
=pY3D
-END PGP SIGNATURE-



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

Bug#1060474: Bug#1072960: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

[Jeremy Bícha]

On Mon, Jun 10, 2024 at 6:24 PM Chris Hofstaedtler  wrote:
> I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.

Feel free to upload now without delay.

Thank you,
Jeremy Bícha

Bug#1072963: jpeg-xl: Failing autopkgtests on non-amd64

[Jeremy Bícha]

Source: jpeg-xl
Version: 0.9.2-6
Severity: serious
Tags: experimental

jpeg-xl in experimental has autopkgtests that are failing on all
architectures except for amd64.

Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst
and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64
architecture which means that libjxl-gdk-pixbuf is uninstallable on
architectures other than amd64.

https://ci.debian.net/packages/j/jpeg-xl/unstable/arm64/

https://salsa.debian.org/debian-phototools-team/libjxl/-/blob/debian/experimental/debian/libjxl-gdk-pixbuf.postinst

Thank you,
Jeremy Bícha

Bug#1071295: apt-cacher-ng: diff for NMU version 3.7.4-1.1

[Chris Hofstaedtler]

Control: tags -1 + patch pending

Dear maintainer,

I've prepared an NMU for apt-cacher-ng (versioned as 3.7.4-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru apt-cacher-ng-3.7.4/debian/changelog apt-cacher-ng-3.7.4/debian/changelog
--- apt-cacher-ng-3.7.4/debian/changelog	2021-12-07 14:50:20.0 +0100
+++ apt-cacher-ng-3.7.4/debian/changelog	2024-06-11 00:41:08.0 +0200
@@ -1,3 +1,11 @@
+apt-cacher-ng (3.7.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Simplify !defined(HAVE_STRLCPY) check to fix FTBFS (Closes: #1071295)
+  * Avoid installing empty /lib/systemd/system directory (Closes: #1059190)
+
+ -- Chris Hofstaedtler   Tue, 11 Jun 2024 00:41:08 +0200
+
 apt-cacher-ng (3.7.4-1) unstable; urgency=medium
 
   * New upstream version
@@ -514,7 +522,7 @@
 
 apt-cacher-ng (0.8.0~rc3-1) unstable; urgency=low
 
-  * New upstream version, first Sid upload of 0.8.x 
+  * New upstream version, first Sid upload of 0.8.x
 + systemd related changes: startup notification, restart on crashes
   (closes: #752255)
 + Now really fixes lookup of .default files in the resource directory
@@ -617,7 +625,7 @@
   * Review of maintainer scripts, now responsive to modification of
 CacheDir in existing configuration file(s)
   * Defensive behavior of Debconf integration (closes: #732606) and including
-NEWS.Debian to explain the extended config handling 
+NEWS.Debian to explain the extended config handling
   * added libssl-dev to build dependencies (now really closes: #729508)
   * fixing build failure on architectures where ancgfs is not built (i.e. Hurd)
   * Debconf description improvement in better German translation
@@ -630,7 +638,7 @@
 + fixes reading of certain .xz files (closes: #729941, #731804)
 + HTTPS support (closes: #729508)
   * more debconf controlled settings injected through a separate config
-file, partially based on the patch from 
+file, partially based on the patch from
 Geert Stappers  (closes: #726656)
   * policy version bump, and no longer recommending perl, there are enough
 functionality replacements implemented to work with just perl-base
@@ -812,7 +820,7 @@
 
 apt-cacher-ng (0.7.4-1) unstable; urgency=medium
 
-  * New upstream release 
+  * New upstream release
 + prevents endless looping in certain situations (LP: #15)
 + more tolerance to unstable connections and behavior fix for conflicting
   downloads in maintenance mode (closes: #672801)
@@ -1113,7 +1121,7 @@
 
 apt-cacher-ng (0.4.9-2) unstable; urgency=low
 
-  * Minor change to support Ubuntu release notes delivery with GET 
+  * Minor change to support Ubuntu release notes delivery with GET
 parameters (closes: #588662)
 
  -- Eduard Bloch   Sun, 11 Jul 2010 11:06:49 +0200
@@ -1139,7 +1147,7 @@
 
 apt-cacher-ng (0.4.7-1) unstable; urgency=low
 
-  * New upstream version 
+  * New upstream version
 + supports fallback backends descriptions which are used when the file is
   specified in the config but not configured properly. Intended to help
   in a heterogeneous Debian/Ubuntu environment (closes Ubuntu tasks
@@ -1164,7 +1172,7 @@
 
   * New upstream release
 + documented DnsCacheSeconds (Ubuntu bug 530524)
-+ Added simple implementation of SOAP request forwarding for PTS 
++ Added simple implementation of SOAP request forwarding for PTS
   access (closes: #453277)
 + Typo fix in userinfo.html (closes: #572171)
 
@@ -1224,7 +1232,7 @@
 + passing HTTP redirection target through to user (closes: #556234)
   * Unconfuse crontab expiration script when BindAdress contains multiple
 entries (patch by Hellekin O\. Wolf, closes: #554707)
- 
+
  -- Eduard Bloch   Sun, 22 Nov 2009 19:06:32 +0100
 
 apt-cacher-ng (0.4-1) unstable; urgency=low
diff -Nru apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch
--- apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch	1970-01-01 01:00:00.0 +0100
+++ apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch	2024-06-11 00:36:51.0 +0200
@@ -0,0 +1,26 @@
+Index: apt-cacher-ng-3.7.4/src/meta.h
+===
+--- apt-cacher-ng-3.7.4.orig/src/meta.h
 apt-cacher-ng-3.7.4/src/meta.h
+@@ -323,7 +323,7 @@ class NoCaseStringMap : public std::map<
+ static constexpr string_view svRN = szRN;
+ static constexpr string_view svLF = "\n";
+ 
+-#if !defined(HAVE_STRLCPY) || !HAVE_STRLCPY
++#if !defined(HAVE_STRLCPY)
+ size_t strlcpy(char *tgt, const char *src, size_t tgtSize);
+ #endif
+ }
+Index: apt-cacher-ng-3.7.4/src/meta.cc
+===
+--- apt-cacher-ng-3.7.4.orig/src/meta.cc
 apt-cacher-ng-3.7.4/src/meta.cc
+@@ -831,7 +831,7 @@ bool scaseequals(string_view a, string_v
+ return true;
+ }
+ 
+-#if !defined(HAVE_STRLCPY) || 

Processed: apt-cacher-ng: diff for NMU version 3.7.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #1071295 [src:apt-cacher-ng] apt-cacher-ng: FTBFS: src/meta.h:326:44: 
error: operator '!' has no right operand
Added tag(s) patch and pending.

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

Bug#1060474: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

[Chris Hofstaedtler]

Control: tags -1 + patch pending


Dear maintainer,

I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru pulseaudio-16.1+dfsg1/debian/changelog pulseaudio-16.1+dfsg1/debian/changelog
--- pulseaudio-16.1+dfsg1/debian/changelog	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/changelog	2024-06-10 23:50:35.0 +0200
@@ -1,3 +1,12 @@
+pulseaudio (16.1+dfsg1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch Build-Depends to systemd-dev, fixing FTBFS. (Closes: #1060474)
+  * Install systemd masking symlink and udev rule into /usr (DEP17).
+(Closes: #1072960)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 23:50:35 +0200
+
 pulseaudio (16.1+dfsg1-5) unstable; urgency=medium
 
   * Team upload
diff -Nru pulseaudio-16.1+dfsg1/debian/control pulseaudio-16.1+dfsg1/debian/control
--- pulseaudio-16.1+dfsg1/debian/control	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/control	2024-06-10 23:50:35.0 +0200
@@ -41,7 +41,7 @@
 libxcb1-dev,
 libxml2-utils ,
 libxtst-dev,
-systemd [linux-any]
+systemd-dev [linux-any]
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/pulseaudio-team/pulseaudio
diff -Nru pulseaudio-16.1+dfsg1/debian/pulseaudio.install pulseaudio-16.1+dfsg1/debian/pulseaudio.install
--- pulseaudio-16.1+dfsg1/debian/pulseaudio.install	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/pulseaudio.install	2024-06-10 23:50:35.0 +0200
@@ -5,7 +5,7 @@
 etc/pulse/daemon.conf
 etc/xdg/autostart/pulseaudio.desktop
 etc/xdg/Xwayland-session.d/00-pulseaudio-x11
-[linux-any] lib/udev/rules.d/90-pulseaudio.rules
+[linux-any] usr/lib/udev/rules.d/90-pulseaudio.rules
 usr/bin/pulseaudio
 usr/bin/start-pulseaudio-x11
 usr/lib/*/pulseaudio/libpulsecore-*.so
diff -Nru pulseaudio-16.1+dfsg1/debian/pulseaudio.links pulseaudio-16.1+dfsg1/debian/pulseaudio.links
--- pulseaudio-16.1+dfsg1/debian/pulseaudio.links	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/pulseaudio.links	2024-06-10 23:50:34.0 +0200
@@ -2,6 +2,6 @@
 
 [linux-any] /usr/share/alsa/alsa.conf.d/pulse.conf /etc/alsa/conf.d/99-pulse.conf
 
-/dev/null /lib/systemd/system/pulseaudio-enable-autospawn.service
+/dev/null /usr/lib/systemd/system/pulseaudio-enable-autospawn.service
 /run/pulseaudio-enable-autospawn /etc/pulse/client.conf.d/01-enable-autospawn.conf
 
diff -Nru pulseaudio-16.1+dfsg1/debian/rules pulseaudio-16.1+dfsg1/debian/rules
--- pulseaudio-16.1+dfsg1/debian/rules	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/rules	2024-06-10 23:50:35.0 +0200
@@ -39,6 +39,7 @@
   -Dstream-restore-clear-old-devices=true \
   -Dzshcompletiondir=/usr/share/zsh/vendor-completions \
   -Dsystemduserunitdir=/usr/lib/systemd/user \
+  -Dudevrulesdir=/usr/lib/udev/rules.d \
   -Dmodlibexecdir=/usr/lib/pulse-$(DEB_VERSION_UPSTREAM)/modules \
   -Dpulsedsp-location=/usr/\\'$$'LIB/pulseaudio \
   -Dgtk=enabled \

Processed: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #1060474 [src:pulseaudio] pulseaudio: Please switch Build-Depends to 
systemd-dev
Added tag(s) patch and pending.

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

Bug#1057576: marked as done (mako: FTBFS: dh_sphinxdoc: error: debian/python-mako-doc/usr/share/doc/python-mako-doc/html/search.html top-level node does not have data-content_root attribute)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 23:57:00 +0200
with message-id <20240610215700.rvxouigrondw6...@piotr.cc>
and subject line fixed in zzzeeksphinx
has caused the Debian Bug report #1057576,
regarding mako: FTBFS: dh_sphinxdoc: error: 
debian/python-mako-doc/usr/share/doc/python-mako-doc/html/search.html top-level 
node does not have data-content_root attribute
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.)


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

Package: src:mako
Version: 1.2.4+ds-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with=sphinxdoc,python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
running config
I: pybuild base:310: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:310: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_mako/build/mako

[... snipped ...]

test/test_template.py::ReservedNameTest::test_names_in_template PASSED   [ 85%]
test/test_template.py::ReservedNameTest::test_exclude_loop_context PASSED [ 85%]
test/test_template.py::ReservedNameTest::test_exclude_loop_template PASSED [ 
85%]
test/test_template.py::ControlTest::test_control PASSED  [ 85%]
test/test_template.py::ControlTest::test_blank_control_1 PASSED  [ 86%]
test/test_template.py::ControlTest::test_blank_control_2 PASSED  [ 86%]
test/test_template.py::ControlTest::test_blank_control_3 PASSED  [ 86%]
test/test_template.py::ControlTest::test_blank_control_4 PASSED  [ 86%]
test/test_template.py::ControlTest::test_blank_control_5 PASSED  [ 87%]
test/test_template.py::ControlTest::test_blank_control_6 PASSED  [ 87%]
test/test_template.py::ControlTest::test_blank_control_7 PASSED  [ 87%]
test/test_template.py::ControlTest::test_blank_control_8 PASSED  [ 87%]
test/test_template.py::ControlTest::test_commented_blank_control_1 PASSED [ 87%]
test/test_template.py::ControlTest::test_commented_blank_control_2 PASSED [ 88%]
test/test_template.py::ControlTest::test_commented_blank_control_3 PASSED [ 88%]
test/test_template.py::ControlTest::test_commented_blank_control_4 PASSED [ 88%]
test/test_template.py::ControlTest::test_commented_blank_control_5 PASSED [ 88%]
test/test_template.py::ControlTest::test_commented_blank_control_6 PASSED [ 88%]
test/test_template.py::ControlTest::test_commented_blank_control_7 PASSED [ 89%]
test/test_template.py::ControlTest::test_commented_blank_control_8 PASSED [ 89%]
test/test_template.py::ControlTest::test_multiline_control PASSED[ 89%]
test/test_template.py::GlobalsTest::test_globals PASSED  [ 89%]
test/test_template.py::RichTracebackTest::test_utf8_memory_syntax PASSED [ 89%]
test/test_template.py::RichTracebackTest::test_utf8_memory_runtime PASSED [ 90%]
test/test_template.py::RichTracebackTest::test_utf8_file_syntax PASSED   [ 90%]
test/test_template.py::RichTracebackTest::test_utf8_file_runtime PASSED  [ 90%]
test/test_template.py::RichTracebackTest::test_unicode_memory_syntax PASSED [ 
90%]
test/test_template.py::RichTracebackTest::test_unicode_memory_runtime PASSED [ 
91%]
test/test_template.py::RichTracebackTest::test_unicode_file_syntax PASSED [ 91%]
test/test_template.py::RichTracebackTest::test_unicode_file_runtime PASSED [ 
91%]
test/test_template.py::ModuleDirTest::test_basic PASSED  [ 91%]
test/test_template.py::ModuleDirTest::test_callable PASSED   [ 91%]
test/test_template.py::ModuleDirTest::test_custom_writer PASSED  [ 92%]
test/test_template.py::FilenameToURITest::test_windows_paths PASSED  [ 92%]
test/test_template.py::FilenameToURITest::test_posix_paths PASSED[ 92%]
test/test_template.py::FilenameToURITest::test_dont_accept_relative_outside_of_root
 PASSED [ 92%]
test/test_template.py::ModuleTemplateTest::test_module_roundtrip PASSED  [ 92%]
test/test_template.py::TestTemplateAPI::test_metadata PASSED [ 93%]
test/test_template.py::TestTemplateAPI::test_metadata_two PASSED [ 93%]
test/test_template.py::PreprocessTest::test_old_comments PASSED  [ 93%]

Processed: closing 1063190

[Debian Bug Tracking System]

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

> close 1063190
Bug #1063190 [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t 
transition
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Chris Hofstaedtler]

* Sam Hartman  [240610 23:13]:
> control: tags -1 +help
> 
> 
> Chris> Filing with severity: serious as the buildd network has
> Chris> started switching to sbuild with unshare backend, and
> Chris> multiple people have reproduced this problem.
> 
> I'm not running sbuild these days; I'm mostly moving toward
> containerized builds for my local development.
> I am currently setting up a new environment and if I can reproduce
> there, I'm happy to  look into it.

> But if it literally happens only on sbuild unshare, I'm going to need
> help because that's not a beast I have a desire to deal with.

A reduced version of the sbuild wiki page [1], which should give you a
working sbuild+unshare on top of a normal, amd64 Debian stable
install (not a container - VM is fine):

$ sudo apt install mmdebstrap uidmap
$ sudo apt install -t stable-backports sbuild
$ mkdir -p ~/.cache/sbuild
$ mmdebstrap --variant=buildd unstable ~/.cache/sbuild/unstable-amd64.tar
$ cat << "EOF" > ~/.sbuildrc
$chroot_mode = 'unshare';
EOF

This assumes you have a recently enough installed Debian stable,
otherwise /etc/subuid and /etc/subgid also need setting up. Example
contents:

% cat /etc/subuid
chris:10:65536
% cat /etc/subgid
chris:10:65536

Might need to logout/login after this.

To build/repro the failure:

$ apt source krb5
$ sbuild -d unstable
(...wait...)

Hope this helps,
Chris

[1] 
https://wiki.debian.org/sbuild#Option_1:_Using_unshare_with_mmdebstrap_.28no_root_needed.29

Bug#1071007:

[Paul Pfeister]

When building the rpm, I named the (rpm) package sherlock-project to have
parity with PyPI, due to the same conflicting package. The importable
module is still simply sherlock, however, which is _less than ideal_, and
should probably be addressed.

With this discussion now being had on the deb side, I just introduced the
conversation about renaming last night.

Still up for debate, but assuming we do decide to change it, we'll most
likely use sherlock_project (again, for parity). I don't like the
underscore, but it's the least likely to have conflict. I'll let you guys
know of the decision.

(executable would remain sherlock even if the package name changes)

Bug#1072159: marked as done (rust-pango-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/Pango-1.0.gir': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 21:21:11 +
with message-id 
and subject line Bug#1072159: fixed in rust-pango-sys 0.19.5-3
has caused the Debian Bug report #1072159,
regarding rust-pango-sys FTBFS with nocheck build profile: cp: cannot stat 
'/usr/share/gir-1.0/Pango-1.0.gir': 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.)


-- 
1072159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-pango-sys
Version: 0.19.5-2
Severity: serious
Tags: ftbfs trixie sid

rust-pango-sys fails to build from source when enabling the nocheck
build profile. A build ends with:

|dh_auto_configure -O--buildsystem=cargo
| debian cargo wrapper: options, profiles, parallel, lto: ['nocheck', 
'parallel=8'] ['nocheck'] ['-j8'] 0
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
| debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
|debian/rules execute_before_dh_auto_build
| make[1]: Entering directory '/<>'
| cp /usr/share/gir-1.0/GLib-2.0.gir /<>
| cp /usr/share/gir-1.0/GModule-2.0.gir /<>
| cp /usr/share/gir-1.0/GObject-2.0.gir /<>
| cp /usr/share/gir-1.0/Pango-1.0.gir /<>
| cp: cannot stat '/usr/share/gir-1.0/Pango-1.0.gir': No such file or directory
| make[1]: *** [debian/rules:12: execute_before_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:4: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Please review the  annotations in your package. Since trixie,
a nocheck build failure is considered release-critical.

Helmut
--- End Message ---
--- Begin Message ---
Source: rust-pango-sys
Source-Version: 0.19.5-3
Done: Matthias Geiger 

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

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

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

Debian distribution maintenance software
pp.
Matthias Geiger  (supplier of updated rust-pango-sys 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Jun 2024 22:58:28 +0200
Source: rust-pango-sys
Architecture: source
Version: 0.19.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Matthias Geiger 
Closes: 1072159
Changes:
 rust-pango-sys (0.19.5-3) unstable; urgency=medium
 .
   * source: build-depend on libpango1.0-dev (Closes: #1072159)
Checksums-Sha1:
 ee930a3dbe8e30da65da9a241867b46e05a8e2ce 1955 rust-pango-sys_0.19.5-3.dsc
 0c5a2718ba080fdb1a3501dc70b11641d406 4536 
rust-pango-sys_0.19.5-3.debian.tar.xz
 6337b6af5ff7eaec3b2024d17520e9a708a14810 9609 
rust-pango-sys_0.19.5-3_source.buildinfo
Checksums-Sha256:
 5d8245caaa956dd4798d5aeec2a71d12e413f5564f5a04e71b0ce6f09f936ece 1955 
rust-pango-sys_0.19.5-3.dsc
 cb2b32e3cf54117263482fac15f8bfa4c76ee2db17817f5fb0ee7913ed20cdd7 4536 
rust-pango-sys_0.19.5-3.debian.tar.xz
 ac22e1e149ad6a1c420f8a49cb2e5706bb391b61f8ec5ab646f30cefb21973c9 9609 
rust-pango-sys_0.19.5-3_source.buildinfo
Files:
 d0650118f13e6f24df3cd227b10f004b 1955 rust optional rust-pango-sys_0.19.5-3.dsc
 00586ef0e60d8f36d3395d76564f65a6 4536 rust optional 
rust-pango-sys_0.19.5-3.debian.tar.xz
 8a2398f76e53ac59c54484c14a7b47e7 9609 rust optional 
rust-pango-sys_0.19.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iIsEARYIADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCZmdo+BUcd2VyZGFoaWFz
QHJpc2V1cC5uZXQACgkQ7L7btge5sr4AtgEA7DNKIM/1rgwpypjQCq9Jb4FxVuP/
0+zGS6cKsQjgiGEA/ipJpiC9vWjc3GAiXSq9BMn07W55vttuMn3gIxRjIHQM
=HPy9
-END PGP SIGNATURE-



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

Processed: your mail

[Debian Bug Tracking System]

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

> block 1071892 by 1060848
Bug #1071892 [src:rust-transmission-client] rust-transmission-client: FTBFS: 
unsatisfiable build-dependencies
1071892 was not blocked by any bugs.
1071892 was not blocking any bugs.
Added blocking bug(s) of 1071892: 1060848
> thanks
Stopping processing here.

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

Processed: Re: Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +help
Bug #1072952 [src:krb5] krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build 
killed with signal TERM after 60 minutes of inactivity
Added tag(s) help.

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

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Sam Hartman]

control: tags -1 +help


Chris> Filing with severity: serious as the buildd network has
Chris> started switching to sbuild with unshare backend, and
Chris> multiple people have reproduced this problem.


I'm not running sbuild these days; I'm mostly moving toward
containerized builds for my local development.
I am currently setting up a new environment and if I can reproduce
there, I'm happy to  look into it.
But if it literally happens only on sbuild unshare, I'm going to need
help because that's not a beast I have a desire to deal with.

Processed: remove webext-noscript

[Debian Bug Tracking System]

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

> clone 922396 -1
Bug #922396 [webext-noscript] webext-noscript: version out of date -- does not 
work with current Firefox
Bug 922396 cloned as bug 1072956
> reassign -1 ftp.debian.org
Bug #1072956 [webext-noscript] webext-noscript: version out of date -- does not 
work with current Firefox
Bug reassigned from package 'webext-noscript' to 'ftp.debian.org'.
No longer marked as found in versions mozilla-noscript/10.1.9.6-2.
Ignoring request to alter fixed versions of bug #1072956 to the same values 
previously set
> severity -1 normal
Bug #1072956 [ftp.debian.org] webext-noscript: version out of date -- does not 
work with current Firefox
Severity set to 'normal' from 'serious'
> retitle -1 RM: mozilla-noscript -- RoQA: rc-buggy; does not support current 
> firefox
Bug #1072956 [ftp.debian.org] webext-noscript: version out of date -- does not 
work with current Firefox
Changed Bug title to 'RM: mozilla-noscript -- RoQA: rc-buggy; does not support 
current firefox' from 'webext-noscript: version out of date -- does not work 
with current Firefox'.
> thanks
Stopping processing here.

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

Processed: remove tinyjsd

[Debian Bug Tracking System]

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

> clone 971774 -1
Bug #971774 [tinyjsd] Doesn't support Thunderbird 68 / 78
Bug 971774 cloned as bug 1072955
> reassign -1 ftp.debian.org
Bug #1072955 [tinyjsd] Doesn't support Thunderbird 68 / 78
Bug reassigned from package 'tinyjsd' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1072955 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1072955 to the same values 
previously set
> severity -1 normal
Bug #1072955 [ftp.debian.org] Doesn't support Thunderbird 68 / 78
Severity set to 'normal' from 'grave'
> retitle -1 RM: tinyjsd -- RoQA; rc-buggy; abandoned upstream; alternative 
> exists
Bug #1072955 [ftp.debian.org] Doesn't support Thunderbird 68 / 78
Changed Bug title to 'RM: tinyjsd -- RoQA; rc-buggy; abandoned upstream; 
alternative exists' from 'Doesn't support Thunderbird 68 / 78'.
> thanks
Stopping processing here.

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

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Chris Hofstaedtler]

Source: krb5
Version: 1.20.1-6
Severity: serious
Tags: ftbfs
X-Debbugs-CC: jspri...@debian.org

Filing with severity: serious as the buildd network has started
switching to sbuild with unshare backend, and multiple people have
reproduced this problem.

When building krb5 with sbuild, configured to use the unshare
backend, the t_iprop.py test apparently times out without any
output.

Last few lines:

| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_general.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_hooks.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_dump.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_iprop.py
| E: Build killed with signal TERM after 60 minutes of inactivity

I'm attaching my own build log, running on arm64. Another build log
showing the same problem can be found here (ran on amd64):

https://people.debian.org/~sanvila/unshare/unstable-20240529/krb5_1.20.1-6_amd64-20240529T214515.396Z

My build log shows the result of an external SIGTERM instead of
sbuild killing it, but that's just a distracting detail.

I'll note this appears unrelated to #1063648.

Chris



krb5_1.20.1-6_arm64-killed.build.gz
Description: application/gzip

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

[Samuel Henrique]

Hello Thomas,

On Mon, 10 Jun 2024 at 12:03, Thomas Goirand  wrote:
>
> On 6/9/24 18:47, Samuel Henrique wrote:
> > Zigo,
> >> I just saw that sherlock (the social networks package) moved its python
> >> files to /usr/share, instead of /usr/lib/python3/dist-packages
> >> . This was
> >> the sensible thing to do, as it doesn't really need to expose itself as
> >> Python module.
> >
> > Not really, that was done by accident when Nilson was trying to remove the
> > system-wide init file (#1071007) and was reverted already.
> >
> > Upstream has mentioned (to me) that their intention is to provide a library 
> > for
> > sherlock, as we've had since the package was introduced.
>
> Well, sherlock is an app, and therefore, it's the sensible thing to do
> to push it's Python code in /usr/share. IMO, it shouldn't have been
> reverted.

The move was done as a workaround for another issue (the global __init__ file),
and upstream mentioned they would like to have the module available, so at the
time the revert was the right choice.

Now that we know there's also a clash with the sherlock package, the situation
is different.

> Normally, the one that owns the PyPi name such as:
> https://pypi.org/project/sherlock/
>
> also get to have the python module name. Clearly, sherlock (the social
> media package) didn't do that.

I agree with this.

> Now, if you know upstream, then probably you can convince them to rename
> their lib to something that doesn't clash? And also, maybe, add its
> software on PyPi?

Sherlock is there, but under https://pypi.org/project/sherlock-project.

So it does look like the right thing to do on Debian's side is to either not
let the module be importable or rename it (ideally done by upstream first).

Paul (as upstream), the sherlock module clashes with
https://pypi.org/project/sherlock/, which was published first and ships a
"sherlock" library.

Do you think it would make sense to change the name of the module provided by
your sherlock (just the module, not the executable), or alternatively for us to
not ship an importable library at all?

This is an issue that's going to happen on other distros as well, as far as I
know.

> >> Therefore, this bug can be closed, and there's IMO nothing more to do in
> >> the python-sherlock (the cluster lock package), as the conflict is now
> >> solved.
> >
> > I'll reopen 1072733 since the clash still exists.
>
> :(

We have a path forward now, at least after Paul replies, so it should be all
good (although the bug stays open until solved, right?!).

Cheers,

--
Samuel Henrique 

Processed: tagging 1056834

[Debian Bug Tracking System]

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

> tags 1056834 + upstream fixed-upstream
Bug #1056834 {Done: Nicholas D Steeves } [src:pyfuse3] 
pyfuse3: ftbfs with cython 3.0.x
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1072857: Proposed fix for #1072857

[Aurélien COUDERC]

Hi,

being hit by this too, I’ve sumbitted an MR at [1].

You’ll also find in attachment the same fix on top of the version of dput 
currently in the archive which is slightly different from the one in the salsa 
repo.
You can put it in /usr/share/dput/dput/dput.py as a short-term workaround.


[1] https://salsa.debian.org/debian/dput/-/merge_requests/13


Happy hacking,
--
Aurélien#! /usr/bin/python3
#
# dput/dput.py
# Part of ???dput???, a Debian package upload toolkit.
#
# This is free software, and you are welcome to redistribute it under
# certain conditions; see the end of this file for copyright
# information, grant of license, and disclaimer of warranty.

""" dput ??? Debian package upload tool. """

import configparser
import email.parser
from hashlib import (
md5,
sha1,
)
import importlib
import os
import os.path
import pkgutil
import re
import signal
import stat
import subprocess
import sys
import textwrap
import types

from . import configfile
from . import crypto
from .helper import dputhelper


app_library_path = os.path.dirname(__file__)

debug = 0


def import_upload_functions():
""" Import upload method modules and make them available. """
upload_methods = {}

package_name = "methods"
modules_path = os.path.join(app_library_path, package_name)
modules_found = [
name for (__, name, ispkg) in
pkgutil.iter_modules([modules_path])
if not ispkg]
if debug:
sys.stdout.write("D: modules_found: {!r}\n".format(modules_found))
for module_name in modules_found:
module = importlib.import_module("{package}.{module}".format(
package=".".join(["dput", package_name]),
module=module_name))
if debug:
sys.stdout.write("D: Module: {module_name} ({module!r})\n".format(
**vars()))
method_name = module_name
if debug:
sys.stdout.write("D: Method name: {}\n".format(method_name))

upload_methods[method_name] = module.upload

return upload_methods


def parse_changes(changes_file):
""" Parse the changes file. """
check = changes_file.read(5)
if check != "-":
changes_file.seek(0)
else:
# found a PGP header, gonna ditch the next 3 lines
# eat the rest of the line
changes_file.readline()
# Hash: SHA1
changes_file.readline()
# empty line
changes_file.readline()
if not changes_file.readline().find("Format") != -1:
changes_file.readline()
changes_text = changes_file.read()
changes = email.parser.HeaderParser().parsestr(changes_text)
if 'files' not in changes:
raise KeyError("No Files field in upload control file")
for file_spec in changes['files'].strip().split("\n"):
if len(file_spec.split()) != 5:
sys.stderr.write(textwrap.dedent("""\
Invalid Files line in .changes:
  {}
""").format(file_spec))
sys.exit(1)
return changes


def read_configs(config_files, debug):
""" Read configuration settings from config files.

:param config_files: Sequence of configuration files, open for reading.
:param debug: If true, enable debugging output.
:return: The resulting `ConfigParser` instance.

The config parser will parse each file in `config_files`. Configuration
from later files overrides earlier files.
"""
config = configparser.ConfigParser()

config.set('DEFAULT', 'login', "username")
config.set('DEFAULT', 'method', "scp")
config.set('DEFAULT', 'hash', "md5")
config.set('DEFAULT', 'allow_unsigned_uploads', "0")
config.set('DEFAULT', 'allow_dcut', "0")
config.set('DEFAULT', 'distributions', "")
config.set('DEFAULT', 'allowed_distributions', "")
config.set('DEFAULT', 'run_lintian', "0")
config.set('DEFAULT', 'run_dinstall', "0")
config.set('DEFAULT', 'check_version', "0")
config.set('DEFAULT', 'scp_compress', "0")
config.set('DEFAULT', 'default_host_main', "")
config.set('DEFAULT', 'post_upload_command', "")
config.set('DEFAULT', 'pre_upload_command', "")
config.set('DEFAULT', 'ssh_config_options', "")
config.set('DEFAULT', 'passive_ftp', "1")
config.set('DEFAULT', 'progress_indicator', "0")

for config_file in config_files:
if debug:
sys.stdout.write(
"D: Parsing configuration file ???{path}???\n".format(
path=config_file.name))
try:
config.read_file(config_file)
except configparser.ParsingError as e:
sys.stderr.write(textwrap.dedent("""\
Error parsing configuration file:
{0}
""").format(str(e)))
sys.exit(1)
config_file.close()

# only check for fqdn and incoming dir, rest have reasonable defaults
  

Bug#1056834: marked as done (pyfuse3: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 15:50:36 -0400
with message-id <877cewtw4z@digitalmercury.freeddns.org>
and subject line Re: Bug#1056834: pyfuse3: ftbfs with cython 3.0.x
has caused the Debian Bug report #1056834,
regarding pyfuse3: ftbfs with cython 3.0.x
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.)


-- 
1056834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyfuse3
Version: 3.2.1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Version: 3.3.0-0.1
Control: tag upstream fixed-upstream

This has been fixed for a while, but the bug wasn't closed from the
changelog.  Closing now.

Confirmed successful and reproducible with cython3 (= 3.0.10+dfsg-5).
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfuse3.html

Closing now.


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

Bug#1061743: marked as done (gramps ftbfs with Python 3.12 as default)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:35:34 +
with message-id 
and subject line Bug#1061743: fixed in gramps 5.2.2+dfsg-0.1
has caused the Debian Bug report #1061743,
regarding gramps ftbfs with Python 3.12 as default
to be marked as done.

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

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


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

Package: src:gramps
Version: 5.1.6+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails to build:

[...]
==
FAIL: test2_exec_CLI (gramps.cli.test.cli_test.Test.test2_exec_CLI)
--
Traceback (most recent call last):
  File "/<>/gramps/cli/test/cli_test.py", line 88, in 
test2_exec_CLI

self.assertEqual(process.returncode, 0,
AssertionError: 1 != 0 : executed CLI command ['/usr/bin/python3', 
'Gramps.py', '-i', '/<>/gramps/cli/test/min1r.ged', '-e', 
'/<>/gramps/cli/test/test_out.ged']


==
FAIL: test3_files_in_import_dir 
(gramps.cli.test.cli_test.Test.test3_files_in_import_dir)

--
Traceback (most recent call last):
  File "/<>/gramps/cli/test/cli_test.py", line 120, in 
test3_files_in_import_dir

self.assertEqual(process.returncode, 0,
AssertionError: 1 != 0 : executed CLI command ['/usr/bin/python3', 
'Gramps.py', '-i', '/<>/gramps/cli/test/min1r.ged', '-e', 
'/<>/gramps/cli/test/test_out.ged']


==
FAIL: test_number_of_ancestors 
(gramps.plugins.test.reports_test.TestDynamic.test_number_of_ancestors)

--
Traceback (most recent call last):
  File "/<>/gramps/plugins/test/reports_test.py", line 91, 
in test_method

self.assertTrue(test_function(out, err, report_name, **options))
AssertionError: False is not true

--
Ran 21830 tests in 277.329s

FAILED (failures=3, skipped=57)
ERROR: Unit test failure.
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: gramps
Source-Version: 5.2.2+dfsg-0.1
Done: Dr. Tobias Quathamer 

We believe that the bug you reported is fixed in the latest version of
gramps, 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.
Dr. Tobias Quathamer  (supplier of updated gramps 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: Mon, 10 Jun 2024 20:48:32 +0200
Source: gramps
Architecture: source
Version: 5.2.2+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Ross Gammon 
Changed-By: Dr. Tobias Quathamer 
Closes: 1061743
Changes:
 gramps (5.2.2+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload with maintainer's consent.
 .
   [ Alexandre Detiste ]
   * Remove build-dep on on python3-mock
 .
   [ Ross Gammon ]
   * New upstream version 5.2.0
   * Drop patches applied upstream
   * Update copyright holders
   * Refresh patches and update patch headers
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 5.2.2+dfsg
 This fixes a FTBFS with python 3.12. Closes: #1061743
   * Refresh patch to drop failing import test
   * Add new patch to set ResourcePath correctly
   * Update Standards-Version to 4.7.0, no changes needed
   * Update icon name for .desktop file
   * Do not use --verbose option for testing. Otherwise, the build log
 is huge (430 MB).
 .
   [ IOhannes m zmölnig (Debian/GNU) ]
   * Make sure that ~/.gramps exist when running upstream testsuite
Checksums-Sha1:
 55eb762b55b0e63db7efd336799f30d6a8bd2780 2135 gramps_5.2.2+dfsg-0.1.dsc
 4c870fb0df0518c779d02cb14491c2dc9d8da733 11481960 gramps_5.2.2+dfsg.orig.tar.xz
 a7bf6f77154d6d7dc52c22e40f66ebaa8cc1d87f 

Bug#969885: marked as done (megadown: [python] is required and it's not installed)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:20:10 +
with message-id 
and subject line Bug#1072945: Removed package(s) from unstable
has caused the Debian Bug report #969885,
regarding megadown: [python] is required and it's not installed
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.)


-- 
969885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: megadown
Version: 0~20180705+git83c53dd-1.1
Severity: important

in sid /usr/bin/python no longer exists, must be python2 or python3
dependency is on python3:any but the script calls python not python3:

[python] is required and it's not installed

ERROR: there are dependencies not present!


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

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages megadown depends on:
ii  bash 5.0-7
ii  curl 7.72.0-1
ii  openssl  1.1.1g-1
ii  pv   1.6.6-1+b1
ii  python3  3.8.2-3
ii  wget 1.20.3-1+b3

megadown recommends no packages.

megadown suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0~20180705+git83c53dd-1.1+rm

Dear submitter,

as the package megadown 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/1072945

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#1007941: marked as done (megadown: Should we remove this package?)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:20:10 +
with message-id 
and subject line Bug#1072945: Removed package(s) from unstable
has caused the Debian Bug report #1007941,
regarding megadown: Should we remove this package?
to be marked as done.

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

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


-- 
1007941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: megadown
Severity: serious
Version: 0~20180705+git83c53dd-1.1
X-Debbugs-CC: vivia.nikolai...@puri.sm

Dear Debian megadown package maintainer,

The package you maintain (megadown, https://tracker.debian.org/pkg/megadown )
has a longstanding release-critical bug (depends on removed python2), which
made the package unusable. There seems to be no activity in fixing this bug in
the last 5 years.

As a result, I am proposing to have this package removed from Debian archive.
If you have any idea on it, please let me know immediately by replying this
email. Otherwise I will submit a package removal request after 15 days (April
01, 2022). Feel free to let me know if you have any questions.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 0~20180705+git83c53dd-1.1+rm

Dear submitter,

as the package megadown 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/1072945

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#991003: marked as done (kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:19:20 +
with message-id 
and subject line Bug#1072932: Removed package(s) from unstable
has caused the Debian Bug report #991003,
regarding kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: 
find_symbol is no longer exported by the kernel
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.)


-- 
991003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kpatch-dkms
Version: 0.6.0-0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

kpatch-dkms fails to build a module for the latest kernel in stable.

For more context on this change in the kernel, please see the
corresponding bug in iptables-netflow-dkms:
https://bugs.debian.org/990123

DKMS make.log for kpatch-0.6.0 for kernel 4.19.0-17-amd64 (x86_64)
Mon Jul 12 17:13:04 UTC 2021
make: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod'
make -C core clean
make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \
Module.symvers
make[1]: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make -C core
make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make -C /lib/modules/4.19.0-17-amd64/build 
M=/var/lib/dkms/kpatch/0.6.0/build/kmod/core kpatch.ko
make[2]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
  CC [M]  /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c: In function 
'kpatch_find_external_symbol':
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:661:8: error: implicit 
declaration of function 'find_symbol'; did you mean 'sprint_symbol'? 
[-Werror=implicit-function-declaration]
  sym = find_symbol(name, NULL, NULL, true, true);
^~~
sprint_symbol
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:661:6: warning: assignment to 
'const struct kernel_symbol *' from 'int' makes pointer from integer without a 
cast [-Wint-conversion]
  sym = find_symbol(name, NULL, NULL, true, true);
  ^
cc1: some warnings being treated as errors
make[5]: *** 
[/usr/src/linux-headers-4.19.0-17-common/scripts/Makefile.build:309: 
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o] Error 1
make[4]: *** [/usr/src/linux-headers-4.19.0-17-common/Makefile:1738: kpatch.ko] 
Error 2
make[3]: *** [Makefile:146: sub-make] Error 2
make[2]: *** [Makefile:8: all] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.19.0-17-amd64'
make[1]: *** [Makefile:13: kpatch.ko] Error 2
make[1]: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make: *** [Makefile:7: all] Error 2
make: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod'

Andreas
--- End Message ---
--- Begin Message ---
Version: 0.6.0-0.2+rm

Dear submitter,

as the package kpatch 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/1072932

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#983648: marked as done (kpatch-dkms: fails to build module for Linux 5.10: uses unknown struct stack_trace)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:19:20 +
with message-id 
and subject line Bug#1072932: Removed package(s) from unstable
has caused the Debian Bug report #983648,
regarding kpatch-dkms: fails to build module for Linux 5.10: uses unknown 
struct stack_trace
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.)


-- 
983648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kpatch-dkms
Version: 0.6.0-0.2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

kpatch-dkms fails to build a module for the current kernel in sid:

DKMS make.log for kpatch-0.6.0 for kernel 5.10.0-3-amd64 (x86_64)
Sun Feb 28 01:36:52 CET 2021
make: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod'
make -C core clean
make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \
Module.symvers
make[1]: Leaving directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make -C core
make[1]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make -C /lib/modules/5.10.0-3-amd64/build 
M=/var/lib/dkms/kpatch/0.6.0/build/kmod/core kpatch.ko
make[2]: Entering directory '/var/lib/dkms/kpatch/0.6.0/build/kmod/core'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
  CC [M]  /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.o
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:143:15: error: variable 
'trace' has initializer but incomplete type
  143 | static struct stack_trace trace = {
  |   ^~~
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:144:3: error: 'struct 
stack_trace' has no member named 'max_entries'
  144 |  .max_entries = ARRAY_SIZE(stack_entries),
  |   ^~~
In file included from 
/usr/src/linux-headers-5.10.0-3-common/include/linux/list.h:9,
 from 
/usr/src/linux-headers-5.10.0-3-common/include/linux/module.h:12,
 from /var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:37:
/usr/src/linux-headers-5.10.0-3-common/include/linux/kernel.h:48:25: warning: 
excess elements in struct initializer
   48 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + 
__must_be_array(arr))
  | ^
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:144:17: note: in expansion of 
macro 'ARRAY_SIZE'
  144 |  .max_entries = ARRAY_SIZE(stack_entries),
  | ^~
/usr/src/linux-headers-5.10.0-3-common/include/linux/kernel.h:48:25: note: 
(near initialization for 'trace')
   48 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + 
__must_be_array(arr))
  | ^
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:144:17: note: in expansion of 
macro 'ARRAY_SIZE'
  144 |  .max_entries = ARRAY_SIZE(stack_entries),
  | ^~
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:145:3: error: 'struct 
stack_trace' has no member named 'entries'
  145 |  .entries = _entries[0],
  |   ^~~
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:145:13: warning: excess 
elements in struct initializer
  145 |  .entries = _entries[0],
  | ^
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:145:13: note: (near 
initialization for 'trace')
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c: In function 
'kpatch_verify_activeness_safety':
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:274:8: error: invalid use of 
undefined type 'struct stack_trace'
  274 |   trace.nr_entries = 0;
  |^
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:275:3: error: implicit 
declaration of function 'save_stack_trace_tsk' 
[-Werror=implicit-function-declaration]
  275 |   save_stack_trace_tsk(t, );
  |   ^~~~
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:276:12: error: invalid use of 
undefined type 'struct stack_trace'
  276 |   if (trace.nr_entries >= trace.max_entries) {
  |^
/var/lib/dkms/kpatch/0.6.0/build/kmod/core/core.c:276:32: error: invalid use of 
undefined type 'struct stack_trace'
  276 |   if (trace.nr_entries >= trace.max_entries) {
  |^
In file included from 
/usr/src/linux-headers-5.10.0-3-common/include/linux/kernel.h:16,
 from 
/usr/src/linux-headers-5.10.0-3-common/include/linux/list.h:9,
 from 
/usr/src/linux-headers-5.10.0-3-common/include/linux/module.h:12,
 from 

Bug#1061743: Gramps in Debian

[Dr. Tobias Quathamer]

Am 03.06.24 um 06:55 schrieb Ross Gammon:

I will try and take a look this week. But if I fail, either of you are
welcome to lose patience, merge it to master, and upload it for me. :-)


Hi Ross,

I've decided to lose patience. :-)

No, seriously, I've built Gramps locally and did some test runs with it. 
Everything seems to work fine, so I've pushed my latest changes to 
salsa, merged it into the master branch, and uploaded to unstable.


Regards,
Tobias



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1029189: marked as done (kpatch: FTBFS with shellcheck 0.9.0)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:19:20 +
with message-id 
and subject line Bug#1072932: Removed package(s) from unstable
has caused the Debian Bug report #1029189,
regarding kpatch: FTBFS with shellcheck 0.9.0
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.)


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

Hi,

kpatch/experimental recently started to FTBFS:

   dh_auto_test
make -j3 check
make[1]: Entering directory '/build/kpatch-0.9.7'
shellcheck kpatch/kpatch kpatch-build/kpatch-build kpatch-build/kpatch-cc

In kpatch/kpatch line 358:
break
^---^ SC2317 (info): Command appears to be 
unreachable. Check usage (or ignore if invoked indirectly).


In kpatch-build/kpatch-build line 809:
rpmbuild -D "_topdir $RPMTOPDIR" -bp --nodeps "--target=$(uname 
-m)" "$RPMTOPDIR"/SPECS/kernel$ALT.spec 2>&1 | logger ||

  ^--^ SC2086 (info): Double quote to prevent 
globbing and word splitting.

Did you mean: 
rpmbuild -D "_topdir $RPMTOPDIR" -bp --nodeps "--target=$(uname 
-m)" "$RPMTOPDIR"/SPECS/kernel"$ALT".spec 2>&1 | logger ||


In kpatch-build/kpatch-build line 1181:
"$TOOLSDIR"/create-diff-object $CDO_FLAGS "orig/$i" 
"patched/$i" "$KOBJFILE_NAME" \
   ^^ SC2086 (info): Double 
quote to prevent globbing and word splitting.

Did you mean: 
"$TOOLSDIR"/create-diff-object "$CDO_FLAGS" "orig/$i" 
"patched/$i" "$KOBJFILE_NAME" \


In kpatch-build/kpatch-build line 1244:
MAKEVARS[$idx]=${MAKEVARS[$idx]/${KPATCH_CC_PREFIX}/}
 ^--^ SC2004 (style): $/${} is unnecessary on arithmetic variables.


In kpatch-build/kpatch-build line 1263:
"$TOOLSDIR"/create-klp-module $extra_flags "$TEMPDIR/patch/tmp.ko" 
"$TEMPDIR/patch/$MODNAME.ko" 2>&1 | logger 1
  ^--^ SC2086 (info): Double quote 
to prevent globbing and word splitting.

Did you mean: 
"$TOOLSDIR"/create-klp-module "$extra_flags" "$TEMPDIR/patch/tmp.ko" 
"$TEMPDIR/patch/$MODNAME.ko" 2>&1 | logger 1

For more information:
  https://www.shellcheck.net/wiki/SC2086 -- Double quote to prevent globbing ...
  https://www.shellcheck.net/wiki/SC2317 -- Command appears to be unreachable...
  https://www.shellcheck.net/wiki/SC2004 -- $/${} is unnecessary on arithmeti...
make[1]: *** [Makefile:70: check] Error 1
make[1]: Leaving directory '/build/kpatch-0.9.7'
dh_auto_test: error: make -j3 check returned exit code 2


Andreas


kpatch_0.9.7-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.6.0-0.2+rm

Dear submitter,

as the package kpatch 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/1072932

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#1027889: marked as done (kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms))

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 19:19:20 +
with message-id 
and subject line Bug#1072932: Removed package(s) from unstable
has caused the Debian Bug report #1027889,
regarding kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms)
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.)


-- 
1027889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kpatch
Version: 0.6.0-0.2
Severity: serious
Tags: sid bookworm experimental

Hi,

please switch the Build-Depends of your package from `dkms` to `dh-dkms`
or (preferrably) `dh-sequence-dkms`.
With the latter you can also drop the `--with dkms` argument to `dh`.

Please consider adding
  Testsuite: autopkgtest-pkg-dkms
to the source stanza in debian/control s.t. the module gets build-tested
against any new kernel version in the archive and breakage is noticed
quickly.

If you have questions or need help for disabling the module build on
unsupported architectures/configurations (that may be exposed when
enabling the autopkgtest), don't hesitate to contact me.


Thanks

Andreas
--- End Message ---
--- Begin Message ---
Version: 0.6.0-0.2+rm

Dear submitter,

as the package kpatch 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/1072932

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#1072947: dropbear: autopkgtest remote-unlocking is flaky

[Luca Boccassi]

Source: dropbear 2024.85-2
Severity: serious
Justification: flaky debci is RC as per RT
User: debian...@lists.debian.org
Usertags: flaky

Dear Maintainer(s),

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

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

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

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: Bug#1039883: The issue impacts SSD disks as well (updating found version)

[Debian Bug Tracking System]

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

> found 1039883 6.5.8-1
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Marked as found in versions linux/6.5.8-1.
> thanks
Stopping processing here.

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

Processed: found 1039883 in 5.10.103-1, found 1039883 in 5.16.3-1~exp1, found 1039883 in 5.17~rc3-1~exp1

[Debian Bug Tracking System]

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

> # According to bisection in 5.10.94 5.15.17 5.16.3 and 5.17-rc1
> found 1039883 5.10.103-1
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Marked as found in versions linux/5.10.103-1.
> found 1039883 5.16.3-1~exp1
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Marked as found in versions linux/5.16.3-1~exp1.
> found 1039883 5.17~rc3-1~exp1
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Marked as found in versions linux/5.17~rc3-1~exp1.
> thanks
Stopping processing here.

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

Bug#1070327: marked as done (libauparse0t64 fails piuparts: missing postrm for /usr-move mitigation)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 18:04:23 +
with message-id 
and subject line Bug#1070327: fixed in audit 1:3.1.2-3
has caused the Debian Bug report #1070327,
regarding libauparse0t64 fails piuparts: missing postrm for /usr-move mitigation
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.)


-- 
1070327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: audit
Version: 1:3.1.2-2.1
Severity: serious
Justification: fails piuparts, blocks testing migration
Tags: patch
X-Debbugs-Cc: z...@debian.org

Hi,

I looked into why audit fails to migrate and noticed that it fails
piuparts as it leaves diversions behind after purge. The patch provided
by the /usr-move team failed to account for package removal and lacks
the postrm bit. I'm attaching a patch that fixes this problem. It also
removes the manual interpolation in favour of relying on dh_installdeb's
builtin interpolation. I'd appreciate a timely upload, because audit is
one of the last missing pieces moving forward with the /usr-move. Would
you mind a NMU?

Helmut
diff --minimal -Nru audit-3.1.2/debian/changelog audit-3.1.2/debian/changelog
--- audit-3.1.2/debian/changelog2024-02-28 04:02:13.0 +0100
+++ audit-3.1.2/debian/changelog2024-05-03 07:49:46.0 +0200
@@ -1,3 +1,10 @@
+audit (1:3.1.2-2.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix piuparts failure arising from /usr-move mitigation. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 03 May 2024 07:49:46 +0200
+
 audit (1:3.1.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru audit-3.1.2/debian/libauparse0t64.lintian-overrides 
audit-3.1.2/debian/libauparse0t64.lintian-overrides
--- audit-3.1.2/debian/libauparse0t64.lintian-overrides 2024-02-28 
03:58:37.0 +0100
+++ audit-3.1.2/debian/libauparse0t64.lintian-overrides 2024-05-03 
07:49:46.0 +0200
@@ -1 +1,2 @@
 libauparse0t64: package-name-doesnt-match-sonames libauparse0
+libauparse0t64: remove-of-unknown-diversion lib/* [postrm:*]
diff --minimal -Nru audit-3.1.2/debian/libauparse0t64.postrm 
audit-3.1.2/debian/libauparse0t64.postrm
--- audit-3.1.2/debian/libauparse0t64.postrm1970-01-01 01:00:00.0 
+0100
+++ audit-3.1.2/debian/libauparse0t64.postrm2024-05-03 07:49:40.0 
+0200
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -e
+
+case $1 in
+   remove|disappear)
+   for file in libauparse.so.0 libauparse.so.0.0.0; do
+   dpkg-divert --package libauparse0t64 --no-rename \
+   --remove --divert \
+   "/lib/#DEB_HOST_MULTIARCH#/$file.usr-is-merged" 
\
+   "/lib/#DEB_HOST_MULTIARCH#/$file"
+   done
+   ;;
+esac
+
+#DEBHELPER#
+
diff --minimal -Nru audit-3.1.2/debian/libauparse0t64.preinst 
audit-3.1.2/debian/libauparse0t64.preinst
--- audit-3.1.2/debian/libauparse0t64.preinst   1970-01-01 01:00:00.0 
+0100
+++ audit-3.1.2/debian/libauparse0t64.preinst   2024-05-03 07:49:46.0 
+0200
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -e
+
+case $1 in
+   install)
+   for file in libauparse.so.0 libauparse.so.0.0.0; do
+   dpkg-divert --package libauparse0t64 --no-rename \
+   --add --divert \
+   "/lib/#DEB_HOST_MULTIARCH#/$file.usr-is-merged" 
\
+   "/lib/#DEB_HOST_MULTIARCH#/$file"
+   done
+   ;;
+esac
+
+#DEBHELPER#
+
diff --minimal -Nru audit-3.1.2/debian/libauparse0t64.preinst.in 
audit-3.1.2/debian/libauparse0t64.preinst.in
--- audit-3.1.2/debian/libauparse0t64.preinst.in2024-02-28 
04:02:11.0 +0100
+++ audit-3.1.2/debian/libauparse0t64.preinst.in1970-01-01 
01:00:00.0 +0100
@@ -1,17 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case $1 in
-   install)
-   for file in libauparse.so.0 libauparse.so.0.0.0; do
-   dpkg-divert --package libauparse0t64 --no-rename \
-   --divert \
-   /lib/#DEB_HOST_MULTIARCH#/$file.usr-is-merged \
-   /lib/#DEB_HOST_MULTIARCH#/$file
-   done
-   ;;
-esac
-
-#DEBHELPER#
-
diff --minimal -Nru audit-3.1.2/debian/rules audit-3.1.2/debian/rules
--- audit-3.1.2/debian/rules2024-02-28 04:02:11.0 +0100
+++ audit-3.1.2/debian/rules2024-05-03 07:47:04.0 +0200
@@ -109,11 +109,6 @@
chgrp adm 

Processed: severity of 1067699 is serious

[Debian Bug Tracking System]

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

> severity 1067699 serious
Bug #1067699 [libllvm18] libllvm18:i386 contains files, also in libllvm18:amd64
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: unblock bug now that more specific bug was filed

[Debian Bug Tracking System]

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

> unblock 1071982 by 1052028
Bug #1071982 [src:jupyterhub] FTBFS: help2man fails
1071982 was blocked by: 1052028
1071982 was not blocking any bugs.
Removed blocking bug(s) of 1071982: 1052028
>
End of message, stopping processing here.

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

Bug#1072941: marked as done (libgl1-mesa-dri: not multi-arch coinstallable)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 17:22:28 +
with message-id 
and subject line Bug#1072941: fixed in mesa 24.1.1-2
has caused the Debian Bug report #1072941,
regarding libgl1-mesa-dri: not multi-arch coinstallable
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.)


-- 
1072941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699

I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.

Probably quite a few other people are going to experience the same
issue, therefore I am filing this as RC to prevent testing migration and
alert unstable users.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 24.1.1-2
Done: Timo Aaltonen 

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated mesa 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: Mon, 10 Jun 2024 19:59:35 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1072941
Changes:
 mesa (24.1.1-2) unstable; urgency=medium
 .
   * rules, control: Revert back to llvm 17. (Closes: #1072941)
Checksums-Sha1:
 e072d0673dd87fc21fe97e8f0c64f3870e157bf2 5926 mesa_24.1.1-2.dsc
 e937c0c72de1c68f4bf5e417e5ae6c0efcd3 103472 mesa_24.1.1-2.debian.tar.xz
 493f4f256b05851fa26bf8ed28d3064d390aae84 10590 mesa_24.1.1-2_source.buildinfo
Checksums-Sha256:
 3eea87f9ecf99fdf0e6f4a16b5bc40d0246f97df2d48ee88b9bc1247acaa6d37 5926 
mesa_24.1.1-2.dsc
 19e0461feda34c2883a5f2fd88f592f1568b22c001bdf37f8b634cb2c8cd39d2 103472 
mesa_24.1.1-2.debian.tar.xz
 f4844024ff404b4d73ca4846e3be27e2f3c029da26b419ef1b81b394b97fcdd0 10590 
mesa_24.1.1-2_source.buildinfo
Files:
 f9fe9f0aa79ea580d40f50913d6e8743 5926 graphics optional mesa_24.1.1-2.dsc
 6661fed4baf1baf61e6e4dd245dc9da2 103472 graphics optional 
mesa_24.1.1-2.debian.tar.xz
 9b21ca7ca0faf443852c3075d10822d1 10590 graphics optional 
mesa_24.1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmZnMQkACgkQy3AxZaiJ
hNzMiw/8DwO+13l9Fpls7wAf7sG9lwnfrmDfJjv/aEssd1ITxV2LiZWwWh2STP5L
/9OC7J8e2GyMZ49tkwmCr8nwHyoG9PxEMcnM9Mt7WdmHSQ8681y083+ySoxBb97m
uUpepWybzoTECl+Y5u46gp1BFlYlxuriebouSBWwzbrsaTLgEw/10SEaRjrXEOLL
CXJNFeraXMF/X0NHPHadhghv4A78iBJyg0bBfb02wQsKrVvtzUvWzoF+K4iVn5is
4GPzn6BDyZBE/LIkJ0/9ddS7e27qCf7y+uzuKK7Gg3AKKw2sVlGmU1rWIilK+1Ju
XUVJyDabTdg3b4hjlEnH9arlnL4nZqcNSyNyyUgQxBRrFvq1Krbxr7UilZfkXFC/
COPkfTKtBeoItWIMy9Q4ZjDgSU5EZbXxG0ee6xi/B0JLxX5A9n8DH4smFdTk1zE5
w3HZqGVRZx4Ui/f2kCqv+KICjL1Rb7g9GZhfKJrOPuHaslz/OIyyGc5XIBVnjwIw
3pJTXHobC5xa8A/uunPsa9NN8EUxVDFA4Ze4e9se6gG1shRtI887iFboyHPTpJp9
Cqo6s4c8zLMaA049ftF0CV4Z9zxMdsNXWrNjfOl34Dt4xdiGJ9cOcKICnIYUw8yj
u+PTor3MkybSB/QZCegIyYTfIT1nrV9q/8bt8bulSJqATwOGxrA=
=XFYq
-END PGP SIGNATURE-



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

Processed: Fixed

[Debian Bug Tracking System]

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

> fixed 1052200 4.3.4+dfsg1-1+deb12u1
Bug #1052200 {Done: Soren Stoutner } [electrum] electrum: 
Lightning security bug in bookworm 4.3.4+dfsg1-1
Marked as fixed in versions electrum/4.3.4+dfsg1-1+deb12u1.
> --
Stopping processing here.

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

Processed: libgl1-mesa-dri: not multi-arch coinstallable

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1067699
Bug #1072941 [libgl1-mesa-dri] libgl1-mesa-dri: not multi-arch coinstallable
1072941 was not blocked by any bugs.
1072941 was not blocking any bugs.
Added blocking bug(s) of 1072941: 1067699

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

Bug#1072941: libgl1-mesa-dri: not multi-arch coinstallable

[Sven Joachim]

Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699

I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.

Probably quite a few other people are going to experience the same
issue, therefore I am filing this as RC to prevent testing migration and
alert unstable users.


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

Processed (with 5 errors): Re: Bug#1039883: The issue impacts SSD disks as well (updating found version)

[Debian Bug Tracking System]

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

> found 1039883 6.1.90-1
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Marked as found in versions linux/6.1.90-1.
> On Thursday, 30 May 2024 14:39:16 CEST Emanuele Rocca wrote:
Unknown command or malformed arguments to command.
> > Just a quick note to confirm that I can reliably reproduce the issue
Unknown command or malformed arguments to command.
> > using a USB stick and the above script on Bookworm.
Unknown command or malformed arguments to command.
> >
Unknown command or malformed arguments to command.
> > uname -a is:
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#1039883: linux: ext4 corruption with symlinks

[Ben Hutchings]

On Sun, 5 Nov 2023 16:12:41 + Hervé Werner 
wrote:
> Hello
> 
> I'm sorry for the delay.
> 
> > Are you able to reliably preoeduce the issue and can bisect it to
> > the introducing commit?
> I faced this issue on real data but I struggled to find a reliable
> scenario to reproduce it. Here is what I just came up with:
>   sudo mkfs -t ext4 -O fast_commit,inline_data /dev/sdb
>   sudo mount /dev/sdb /mnt/
>   sudo install -d -o myuser /mnt/annex
>   cd /mnt/annex
>   git init && git annex init
>   for i in {1..2}; do
> for i in {1..1}; do
>   dd if=/dev/urandom of=file-${i} bs=1K count=1 2>/dev/null
> done
> git annex add -J cpus . >/dev/null && git annex sync -J cpus && git annex 
>fsck -J cpus >/dev/null
> git rm * && git annex sync  && git annex dropunused all
>   done
> 
> Then at some point the following error appears:
>   EXT4-fs error (device sdb): ext4_map_blocks:577: inode #3942343: block 4: 
>comm git-annex:w: lblock 1 mapped to illegal pblock 4 (length 1)
[...]

I can also reproduce this error message using the above script and:

- Linux 6.10-rc2
- A 2 GiB loopback devic instead of /dev/sdb

I bisected this back to:

commit 9725958bb75cdfa10f2ec11526fdb23e7485e8e4
Author: Xin Yin 
Date:   Thu Dec 23 11:23:37 2021 +0800
 
ext4: fast commit may miss tracking unwritten range during ftruncate

It is still possible to cleanly revert that commit from 6.10-rc2, and
doing so removes the error message.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

Processed: unblock bug now that more specific bug was filed

[Debian Bug Tracking System]

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

> unblock 1052028 by 1071982
Bug #1052028 [src:pydantic] please update to pydantic 2.x
1052028 was not blocked by any bugs.
1052028 was blocking: 1061609 1071982 1072938
Removed blocking bug(s) of 1052028: 1071982
>
End of message, stopping processing here.

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

Processed (with 1 error): jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2)

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1052028
Bug #1072938 [src:jupyterhub] jupyterhub: Unsatisfiable Build-Depends 
python3-pydantic (>= 2)
1072938 was not blocked by any bugs.
1072938 was not blocking any bugs.
Added blocking bug(s) of 1072938: 1052028
> unblock 107192 by 1052028
Failed to set blocking bugs of 107192: Not altering archived bugs; see 
unarchive.


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

Bug#1072938: jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2)

[Jeremy Bícha]

Source: jupyterhub
Version: 5.0.0+ds1-1
Severity: serious
Tags: ftbfs
Control: block -1 by 1052028
Control: unblock 107192 by 1052028
X-Debbugs-CC: lola...@debian.org

jupyterhub is unable to build from source because it has
Build-Depends: python3-pydantic >=2 but the latest version of
python3-pydantic in Debian is 1.10.14.

Thank you,
Jeremy Bícha

Bug#1072934: shadowsocks-libev: Consider removing the package

[Boyuan Yang]

Source: shadowsocks-libev
Version: 3.3.5+ds-10
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com
Tags: sid

Hi,

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

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

Thanks,
Boyuan Yang


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

Bug#1072935: simple-obfs: Consider removing the package

[Boyuan Yang]

Source: simple-obfs
Version: 0.0.5-6
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com
Tags: sid

Hi,

Following the previous communication in March, I am considering to take action
and remove related packages in the ss-libev ecosystem. The first targeted 
package
would be simple-obfs.

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

Thanks,
Boyuan Yang


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

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

[Chris Hofstaedtler]

On Mon, Jun 10, 2024 at 11:59:34AM +0200, Chris Hofstaedtler wrote:
> Hi,
> 
> On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote:
> > > "Simon" == Simon McVittie  writes:
[..]
> > Simon> However, even with both of those, if the krb5 test suite (or
> > Simon> protocol) is resolving the local hostname with AF_INET
> > Simon> (IPv4-only), and with either AI_ADDRCONFIG or NULL hints,
> > Simon> then that will not yield any results on an IPv6-only system
> > Simon> for the reasons discussed in #952740 and related bug reports.
> > 
> > Krb5 is very v6-happy.
> 
> It really seems like krb5 is not quite as ipv6-*only*-happy as one
> would like to think.

Adam (adsb) points out that the test code in
lib/rpc/unit-test/client.c [1] uses code that does not support
IPv6(-only). I.e. gethostbyname for a name that has no IPv4 address
will fail.

Please try fixing this before adding workarounds?

Chris

[1] 
https://sources.debian.org/src/krb5/1.20.1-6/src/lib/rpc/unit-test/client.c/#L127

Bug#1072597: marked as done (node-chownr: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 13:49:18 +
with message-id 
and subject line Bug#1072597: fixed in node-chownr 2.0.0-3
has caused the Debian Bug report #1072597,
regarding node-chownr: FTBFS: failing tests
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.)


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

Package: src:node-chownr
Version: 2.0.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
mkdir -p node_modules
ln -s ../. node_modules/chownr
/bin/sh -ex debian/tests/pkg-js/test
+ tap -R tap --no-cov test/concurrent-sync.js test/old-readdir.js
TAP version 13
# Subtest: test/concurrent-sync.js
# Subtest: get the ids to use
1..0
ok 1 - get the ids to use # time=26.223ms

# Subtest: run test

# Subtest: should complete successfully
1..0
ok 1 - should complete successfully # time=12.105ms

# Subtest: verify

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 2 - verify # time=9.361ms

# Subtest: verify a

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 3 - verify a # time=4.593ms

# Subtest: verify a/b

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 4 - verify a/b # time=3.91ms

# Subtest: verify a/b/c

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 5 - verify a/b/c # time=3.543ms

# Subtest: verify d

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 6 - verify d # time=2.939ms

# Subtest: verify d/e

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 7 - verify d/e # time=3.331ms

# Subtest: verify d/e/f

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 8 - verify d/e/f # time=6.116ms

# Subtest: verify g

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 9 - verify g # time=2.741ms

# Subtest: verify g/h

ok 1 - should match pattern provided
ok 2 - should match pattern provided
ok 3 - d1 turned into a file
ok 4 - should match pattern provided
ok 5 - expected to throw
ok 6 - expected to throw
1..6
ok 10 - verify g/h # 

Bug#1072604: marked as done (node-stream-shift: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 13:49:28 +
with message-id 
and subject line Bug#1072604: fixed in node-stream-shift 1.0.3+~1.0.2-1
has caused the Debian Bug report #1072604,
regarding node-stream-shift: FTBFS: failing tests
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.)


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

Package: src:node-stream-shift
Version: 1.0.1+~1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/@types/stream-shift -> ../../types-stream-shift
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/stream-shift
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# shifts next
ok 1 should be deeply equivalent
ok 2 should be deeply equivalent
# shifts next with core
ok 3 should be deeply equivalent
/<>/index.js:16
return state.buffer[0].length
   ^

TypeError: Cannot read properties of null (reading 'length')
at getStateLength (/<>/index.js:16:28)
at shift (/<>/index.js:6:99)
at Test. (/<>/test.js:24:10)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
at Immediate.next (/usr/share/nodejs/tape/lib/results.js:157:7)
at process.processImmediate (node:internal/timers:478:21)

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


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-stream-shift
Source-Version: 1.0.3+~1.0.2-1
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-stream-shift 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: Mon, 10 Jun 2024 17:19:54 +0400
Source: node-stream-shift
Architecture: source
Version: 1.0.3+~1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1072604
Changes:
 node-stream-shift (1.0.3+~1.0.2-1) unstable; urgency=medium
 .
   * Team upload
   * Update standards version to 4.6.2, no changes needed.
   * Declare compliance with policy 4.7.0
   * New upstream version 1.0.3+~1.0.2 (Closes: #1072604)
Checksums-Sha1: 
 2978f55712dc4c286e3ad396ff2e59c718afc0bf 2513 
node-stream-shift_1.0.3+~1.0.2-1.dsc
 56567b7f7fbeb48346d1c5114e7db4f43155564f 1605 
node-stream-shift_1.0.3+~1.0.2.orig-types-stream-shift.tar.gz
 c31d9ea077f8ea6a8841e54d17292922f31985e7 2291 
node-stream-shift_1.0.3+~1.0.2.orig.tar.gz
 9a62fd1b57fce177bdde24aad197cb0bc0e431f7 2968 

Bug#1068918: marked as done (node-zx: FTBFS test suite failure)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 17:32:34 +0400
with message-id 
and subject line Fixed elsewhere
has caused the Debian Bug report #1068918,
regarding node-zx: FTBFS test suite 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.)


-- 
1068918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-zx
Version: 7.1.1+~cs6.7.23-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

This package FTBFS in bookworm, even when using node-undici with fixed types.



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

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 ---

X-CrossAssassin-Score: 49590--- End Message ---

Processed: notfound 1068918 in node-zx/7.1.1+~cs6.7.23-2, notfound 1068918 in node-zx/7.1.1+~cs6.7.23-3

[Debian Bug Tracking System]

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

> notfound 1068918 node-zx/7.1.1+~cs6.7.23-2
Bug #1068918 [src:node-zx] node-zx: FTBFS test suite failure
No longer marked as found in versions node-zx/7.1.1+~cs6.7.23-2.
> notfound 1068918 node-zx/7.1.1+~cs6.7.23-3
Bug #1068918 [src:node-zx] node-zx: FTBFS test suite failure
No longer marked as found in versions node-zx/7.1.1+~cs6.7.23-3.
> thanks
Stopping processing here.

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

Bug#1072603: marked as done (node-read-package-json: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:19:44 +
with message-id 
and subject line Bug#1072603: fixed in node-read-package-json 5.0.2+~2.0.0-2
has caused the Debian Bug report #1072603,
regarding node-read-package-json: FTBFS: failing tests
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.)


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

Package: src:node-read-package-json
Version: 5.0.2+~2.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/npm-normalize-package-bin -> ../npm-normalize-package-bin
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/read-package-json
/bin/sh -ex debian/tests/pkg-js/test
+ ls test/basic.js test/bin-non-string.js test/bin.js test/bom.js 
test/bundle.js test/fill-types.js test/git-head.js test/helpful.js 
test/indexjs.js test/main-non-string.js test/mans.js test/non-json.js 
test/readmes.js test/semver.js test/underscores.js
+ grep -v test/git-head.js
+ tap --no-cov test/basic.js test/bin-non-string.js test/bin.js test/bom.js 
test/bundle.js test/fill-types.js test/helpful.js test/indexjs.js 
test/main-non-string.js test/mans.js test/non-json.js test/readmes.js 
test/semver.js test/underscores.js
TAP version 13
# Subtest: test/basic.js
# Subtest: basic test
ok 1 - expect truthy value
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - type is object
ok 6 - should be equal
ok 7 - should be equivalent
ok 8 - should be equal
ok 9 - should be equal
ok 10 - should be equivalent
ok 11 - should contain all provided fields
ok 12 - should be equivalent
1..12
ok 1 - basic test # time=73.281ms

1..1

# time=78.099ms
ok 1 - test/basic.js # time=78.099ms

# Subtest: test/bin-non-string.js
# Subtest: non-string bin entries
#
ok 1 - no error from readJson
ok 2 - should be equal
1..2
ok 1 - non-string bin entries # time=58.267ms

1..1

# time=65.274ms
ok 2 - test/bin-non-string.js # time=65.274ms

# Subtest: test/bin.js
# Subtest: Bin test
ok 1 - should be equal
ok 2 - should be equivalent strictly
1..2
ok 1 - Bin test # time=41.372ms

# Subtest: Bad bin test

ok 1 - should be equal
ok 2 - should be equal
1..2
ok 2 - Bad bin test # time=26.1ms

# Subtest: Empty bin test

ok 1 - should be equal
ok 2 - no mapping to bin because object was empty
1..2
ok 3 - Empty bin test # time=11.034ms

1..3

# time=87.294ms
ok 3 - test/bin.js # time=87.294ms

# Subtest: test/bom.js
# Subtest: BOM test
ok 1 - should be equivalent
1..1
ok 1 - BOM test # time=57.377ms

1..1

# time=70.553ms
ok 4 - test/bom.js # time=70.553ms

# Subtest: test/bundle.js
# Subtest: bundle-true
ok 1 - should match pattern provided
1..1
ok 1 - bundle-true # time=68.833ms

# Subtest: bundle-null

ok 1 - no bundleDependencies
ok 2 - no bundledDependencies
1..2
ok 2 - bundle-null # time=7.911ms

# Subtest: bundle-array

ok 1 - should match pattern provided
1..1
ok 3 - bundle-array # time=13.307ms

# Subtest: bundle-false

ok 1 - should match pattern provided
1..1
ok 4 - bundle-false # time=25.722ms

1..4

# time=127.224ms
ok 5 - test/bundle.js # time=127.224ms

# Subtest: test/fill-types.js
# Subtest: adds types with a custom main field
ok 1 - should match pattern provided
1..1
ok 1 - adds types with a custom main field # time=43.582ms

# Subtest: handles the inferred index.js

ok 1 - should match pattern provided
1..1
ok 2 - handles the inferred index.js # time=11.425ms

# Subtest: handles subpaths and starting with ./

ok 1 - should match pattern provided
1..1
ok 3 - handles subpaths and starting with ./ # time=3.784ms

# Subtest: handles 

Bug#1072602: marked as done (node-parse-json: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:19:37 +
with message-id 
and subject line Bug#1072602: fixed in node-parse-json 5.2.0+~cs5.1.7-2
has caused the Debian Bug report #1072602,
regarding node-parse-json: FTBFS: failing tests
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.)


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

Package: src:node-parse-json
Version: 5.2.0+~cs5.1.7-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
Link lines-and-columns/node_modules/assert -> /usr/share/nodejs/assert
Link lines-and-columns/node_modules/@types/mocha -> 
/usr/share/nodejs/@types/mocha
Link node_modules/lines-and-columns -> ../lines-and-columns
Link node_modules/@types/parse-json -> ../../types-parse-json
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
Found debian/nodejs/lines-and-columns/build
cd ./lines-and-columns && sh -ex 
../debian/nodejs/lines-and-columns/build
+ tsc --build tsconfig.build.json
+ mv build/index.js build/index.mjs
+ babeljs -o build/index.js --presets @babel/preset-env build/index.mjs
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/parse-json
/bin/sh -ex debian/tests/pkg-js/test
+ tape test.js
TAP version 13
# main
ok 1 should be truthy
ok 2 should throw
not ok 3 should throw
  ---
operator: throws
expected: |-
  '/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
  ErrorEXError { name: 'JSONError', codeFrame: '  1 | {\n  2 | \t"foo": true,\n> 3 | }\n| ^', 
fileName: 'foo.json', message: 'Expected double-quoted property name in JSON at position 16 while parsing 
\'{\t"foo": true,}\' in foo.json \n\n  1 | {\n  2 | \t"foo": true,\n> 3 | }\n| ^\n' }
at: Test. (/<>/test.js:15:4)
stack: |-
  JSONError: Expected double-quoted property name in JSON at position 16 while 
parsing '{   "foo": true,}' in foo.json
  
1 | {

2 | "foo": true,
  > 3 | }
  | ^
  
  at parseJson (/<>/index.js:29:21)

  at /<>/test.js:17:4
  at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
  at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test. (/<>/test.js:15:4)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next [as _onImmediate] 
(/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:478:21)
  ...
not ok 4 should throw
  ---
operator: throws
expected: |-
  '/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
  ErrorEXError { name: 'JSONError', fileName: 'foo.json', codeFrame: '  1 | {\n  2 | \t"foo": 
true,\n> 3 | }\n| ^', message: 'Expected double-quoted property name in JSON at position 16 while parsing 
\'{\t"foo": true,}\' in foo.json \n\n  1 | {\n  2 | \t"foo": true,\n> 3 | }\n| ^\n' }
at: Test. (/<>/test.js:24:4)
stack: |-
  JSONError: Expected double-quoted property name in JSON at position 16 while 
parsing '{   "foo": true,}' in foo.json
  
1 | {

2 | "foo": true,
  > 3 | }
  | ^
  
  at parseJson (/<>/index.js:29:21)

  at /<>/test.js:25:3
  at Test.throws (/usr/share/nodejs/tape/lib/test.js:630:3)
  at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test. (/<>/test.js:24:4)
  at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
  at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
  at Immediate.next [as _onImmediate] 
(/usr/share/nodejs/tape/lib/results.js:157:7)
  at process.processImmediate (node:internal/timers:478:21)
  ...
not ok 5 should throw
  ---
operator: throws
expected: |-
  '/Unexpected token "?}"?.*in foo\\.json/'
actual: |-
  ErrorEXError { name: 'JSONError', fileName: 

Bug#1072598: marked as done (node-decompress-response: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:19:26 +
with message-id 
and subject line Bug#1072598: fixed in node-decompress-response 6.0.0-3
has caused the Debian Bug report #1072598,
regarding node-decompress-response: FTBFS: failing tests
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.)


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

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

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
mkdir -p node_modules
ln -s ../. node_modules/decompress-response
/bin/sh -ex debian/tests/pkg-js/test
+ tape test/test.js
TAP version 13
# decompress gzipped content
ok 1 should be truthy
ok 2 should be truthy
ok 3 should be truthy
ok 4 should be truthy
ok 5 should be truthy
ok 6 should be truthy
ok 7 should be truthy
ok 8 should be truthy
ok 9 should be truthy
ok 10 should be truthy
ok 11 should be truthy
ok 12 should be truthy
ok 13 should be strictly equal
ok 14 should be falsy
# decompress deflated content
node:events:497
  throw er; // Unhandled 'error' event
  ^

Error: socket hang up
at Socket.socketOnEnd (node:_http_client:524:23)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections 
(node:internal/process/task_queues:82:21)
Emitted 'error' event on ClientRequest instance at:
at Socket.socketOnEnd (node:_http_client:524:9)
at Socket.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections 
(node:internal/process/task_queues:82:21) {
  code: 'ECONNRESET'
}

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


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-decompress-response
Source-Version: 6.0.0-3
Done: Yadd 

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

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

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-decompress-response 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: Mon, 10 Jun 2024 15:53:48 +0400
Source: node-decompress-response
Architecture: source
Version: 6.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1072598
Changes:
 node-decompress-response (6.0.0-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Apply multi-arch hints. + node-decompress-response: Add Multi-Arch:
 foreign
 .
   [ Yadd ]
   * Declare compliance with policy 4.7.0
   * Fix test for nodejs 20 (Closes: #1072598)
Checksums-Sha1: 
 

Bug#1072600: marked as done (node-json-parse-better-errors: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:05:54 +
with message-id 
and subject line Bug#1072600: fixed in node-json-parse-better-errors 
1.0.2+~cs3.3.1-3
has caused the Debian Bug report #1072600,
regarding node-json-parse-better-errors: FTBFS: failing tests
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.)


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

Package: src:node-json-parse-better-errors
Version: 1.0.2+~cs3.3.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/json-parse-even-better-errors -> 
../json-parse-even-better-errors
Link node_modules/@types/json-parse-better-errors -> 
../../types-json-parse-better-errors
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/json-parse-better-errors
cd ./json-parse-even-better-errors && sh -ex 
../debian/nodejs/json-parse-even-better-errors/test
+ tap -J test/index.js
TAP version 13
(node:186126) DeprecationWarning: deepEqual() is deprecated, use same() instead
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:186126) DeprecationWarning: isa() is deprecated, use type() instead
# Subtest: test/index.js
# Subtest: parses JSON
1..6
ok 1 - object
ok 2 - array
ok 3 - num
ok 4 - null
ok 5 - true
ok 6 - false
ok 1 - parses JSON # time=9.314ms

# Subtest: preserves indentation and newline styles

# Subtest: {"type":"object","newline":"\\n","indent":""}
ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 1 - {"type":"object","newline":"\\n","indent":""} # time=1.422ms

# Subtest: {"type":"array","newline":"\\n","indent":""}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 2 - {"type":"array","newline":"\\n","indent":""} # time=1.275ms

# Subtest: {"type":"object","newline":"\\n","indent":"  "}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 3 - {"type":"object","newline":"\\n","indent":"  "} # time=0.879ms

# Subtest: {"type":"array","newline":"\\n","indent":"  "}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 4 - {"type":"array","newline":"\\n","indent":"  "} # time=0.873ms

# Subtest: {"type":"object","newline":"\\n","indent":"\\t"}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 5 - {"type":"object","newline":"\\n","indent":"\\t"} # time=0.72ms

# Subtest: {"type":"array","newline":"\\n","indent":"\\t"}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 6 - {"type":"array","newline":"\\n","indent":"\\t"} # time=0.697ms

# Subtest: {"type":"object","newline":"\\n","indent":" \\t \\t "}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 7 - {"type":"object","newline":"\\n","indent":" \\t \\t "} # 
time=0.591ms

# Subtest: {"type":"array","newline":"\\n","indent":" \\t \\t "}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 8 - {"type":"array","newline":"\\n","indent":" \\t \\t "} # 
time=0.574ms

# Subtest: {"type":"object","newline":"\\r\\n","indent":""}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 9 - {"type":"object","newline":"\\r\\n","indent":""} # time=0.509ms

# Subtest: {"type":"array","newline":"\\r\\n","indent":""}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
ok 10 - {"type":"array","newline":"\\r\\n","indent":""} # time=0.553ms

# Subtest: {"type":"object","newline":"\\r\\n","indent":"  "}

ok 1 - preserved newline
ok 2 - preserved indent
1..2
   

Processed: Bug#1072602 marked as pending in node-parse-json

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072602 [src:node-parse-json] node-parse-json: FTBFS: failing tests
Added tag(s) pending.

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

Bug#1072602: marked as pending in node-parse-json

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-parse-json/-/commit/e81f2de8b3677dbe9ec47b4c31ffa2f0f8d8fa20


Fix test for nodejs 20

Closes: #1072602


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072602

Bug#1072306: marked as done (src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 12:06:30 +
with message-id 
and subject line Bug#1072306: fixed in r-cran-rcppparallel 5.1.7+dfsg-5
has caused the Debian Bug report #1072306,
regarding src:r-cran-rcppparallel: fails to migrate to testing for too long: 
autopkgtest regression
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.)


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

Source: r-cran-rcppparallel
Version: 5.1.7+dfsg-3
Severity: serious
Control: close -1 5.1.7+dfsg-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-rcppparallel has been trying to 
migrate for 38 days [2]. Hence, I am filing this bug. The version in 
unstable fails its own autopkgtest.


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


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


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


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-rcppparallel
Source-Version: 5.1.7+dfsg-5
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-rcppparallel 
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: Mon, 10 Jun 2024 13:01:46 +0200
Source: r-cran-rcppparallel
Architecture: source
Version: 5.1.7+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1072306
Changes:
 r-cran-rcppparallel (5.1.7+dfsg-5) unstable; urgency=medium
 .
   * Re-add r-base-dev to Test-Depends (seems dh-update-R removed it again)
 Closes: #1072306
Checksums-Sha1:
 72d2be13e0916944f27c2e5b692194c0e1797315 2314 
r-cran-rcppparallel_5.1.7+dfsg-5.dsc
 a136b96ecdc7d452f142d20f30edb6210dd5e03a 4844 
r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz
 11b8be02c01a9b2e750a552bbe0da5c4e3673382 11327 
r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 e665255faf807092a8eb1967a63ca74bc569b6b8c1cb15b23db59aa5226f6f97 2314 
r-cran-rcppparallel_5.1.7+dfsg-5.dsc
 b12f7eef61910bcee7227348414c1a36029739c55f19d2ca778725a9b91e511c 4844 
r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz
 2ad160fb659c486656abe920f8bb731a446f7944119d14ed3d6c1eaa3e28807c 11327 
r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo
Files:
 5d7b9b045d309029ecad7ad2692f9579 2314 gnu-r optional 
r-cran-rcppparallel_5.1.7+dfsg-5.dsc
 1737f31816dc6047dec0b48d17da24c0 4844 gnu-r optional 
r-cran-rcppparallel_5.1.7+dfsg-5.debian.tar.xz
 c2b85577579847e0563b11ddcba728b3 11327 gnu-r optional 
r-cran-rcppparallel_5.1.7+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1072603: marked as pending in node-read-package-json

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-read-package-json/-/commit/72376a4470eecc3642093b0aa108c46a0eb1c4fc


Fix test for nodejs 20

Closes: #1072603


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072603

Processed: Bug#1072603 marked as pending in node-read-package-json

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072603 [src:node-read-package-json] node-read-package-json: FTBFS: 
failing tests
Added tag(s) pending.

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

Bug#1072598: marked as pending in node-decompress-response

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-decompress-response/-/commit/0dfba119e62ea9ddf9b250a64ac0b7b85e40da7f


Fix test for nodejs 20

Closes: #1072598


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072598

Bug#1072366: libndp: CVE-2024-5564

[Moritz Muehlenhoff]

Hi Florian,

On Mon, Jun 10, 2024 at 08:41:27AM +0200, Florian Ernst wrote:
> Dear Security Team,
> 
> On Sat, Jun 01, 2024 at 04:57:53PM +0200, Salvatore Bonaccorso wrote:
> > [...]
> > [0] https://security-tracker.debian.org/tracker/CVE-2024-5564
> > https://www.cve.org/CVERecord?id=CVE-2024-5564
> 
> An updated package containing upstream's fix has just been uploaded and
> is waiting to be processed for unstable.
> 
> Upstream's fix: 
> https://github.com/jpirko/libndp/commit/05e4ba7b0d126eea4c04387dcf40596059ee24af
> (as referenced from https://github.com/jpirko/libndp/issues/26 and
> already seen by carnil)
> Debian change: 
> https://salsa.debian.org/debian/libndp/-/commit/a6136d60ef278c1aebee32f805ff473f0ee6ef99
> 
> The corresponding Debian change applies cleanly on bookworm / stable
> (naturally, as until today bookworm and sid both had libndp 1.8-1) and
> also on bullseye / oldstable and buster / oldoldstable (both having
> libndp 1.6-1).
> 
> I could prepare packages targeting (old)stable, if so desired. Or would
> it be easier for you if you just take over from here?

It would be great if you could prepare updates for bullseye-security and
bookworm-security [1]. Please use 1.6-1+deb11u1 and 1.8-1+deb12u1 as the
respective version numbers. security.debian.org also has autopkgtests set
up, so we should get some good coverage by reverse deps.

Cheers,
Moritz

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#bug-security

Processed: Bug#1072598 marked as pending in node-decompress-response

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072598 [src:node-decompress-response] node-decompress-response: FTBFS: 
failing tests
Added tag(s) pending.

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

Bug#1072600: marked as pending in node-json-parse-better-errors

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-json-parse-better-errors/-/commit/561d854312e653f3da710c13624315f5d8cf7e26


Fix test for Node.js 20

Closes: #1072600


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072600

Processed: Bug#1072600 marked as pending in node-json-parse-better-errors

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072600 [src:node-json-parse-better-errors] node-json-parse-better-errors: 
FTBFS: failing tests
Added tag(s) pending.

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

Bug#1071160: Fix in stable

[tic]

Hello guys,

Thanks for the quick upload to sid guys ! Do you know what is the plan for 
stable ? I see no activity to backport the fixes since the 2.45.1 release [0].

Thanks in advance
Tic

[0] : 
https://repo.or.cz/git/debian.git/shortlog/8d1426afa25b0a66ed65d9b56b8c11df5e35d973

publickey - tic@letic.fr - 0xBD6A3D8B.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#1063645: Aw: Re: markdown: missing required debian/rules targets build-arch and/or build-indep

[Johannes Schauer Marin Rodrigues]

Quoting Bastian Germann (2024-06-10 09:30:20)
> "Johannes Schauer Marin Rodrigues":
> > Do you have recommendations? I just need a drop-in replacement for markdown
> > into stdin, html on stdout. Nothing fancy.
> I would suggest discount or python3-markdown.

Brilliant! That tip was gold! All I did was this to fix the issue in my
package:

--- a/debian/control
+++ b/debian/control
@@ -37,7 +37,7 @@ Build-Depends-Arch:
  graphviz,
  black   ,
 Build-Depends-Indep:
- markdown ,
+ discount ,
  graphviz ,
 Vcs-Browser: https://salsa.debian.org/debian/botch
 Vcs-Git: https://salsa.debian.org/debian/botch.git


Much easier than fixing d/rules of src:markdown. ;)

signature.asc
Description: signature

Bug#1071007: Bug#1072733: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

[Thomas Goirand]

On 6/9/24 18:47, Samuel Henrique wrote:

Zigo,

I just saw that sherlock (the social networks package) moved its python
files to /usr/share, instead of /usr/lib/python3/dist-packages
. This was
the sensible thing to do, as it doesn't really need to expose itself as
Python module.


Not really, that was done by accident when Nilson was trying to remove the
system-wide init file (#1071007) and was reverted already.

Upstream has mentioned (to me) that their intention is to provide a library for
sherlock, as we've had since the package was introduced.


Well, sherlock is an app, and therefore, it's the sensible thing to do 
to push it's Python code in /usr/share. IMO, it shouldn't have been 
reverted.


Normally, the one that owns the PyPi name such as:
https://pypi.org/project/sherlock/

also get to have the python module name. Clearly, sherlock (the social 
media package) didn't do that.


Now, if you know upstream, then probably you can convince them to rename 
their lib to something that doesn't clash? And also, maybe, add its 
software on PyPi?



Therefore, this bug can be closed, and there's IMO nothing more to do in
the python-sherlock (the cluster lock package), as the conflict is now
solved.


I'll reopen 1072733 since the clash still exists.


:(

Cheers,

Thomas Goirand (zigo)

Bug#1072835: marked as done (jpeg-xl: Failing autopkgtests)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 10:49:14 +
with message-id 
and subject line Bug#1072835: fixed in jpeg-xl 0.9.2-6
has caused the Debian Bug report #1072835,
regarding jpeg-xl: Failing autopkgtests
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.)


-- 
1072835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpeg-xl
Version: 0.9.2-5
Severity: serious
Tags: experimental

jpeg-xl in experimental has failing autopkgtests.

https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl

https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/

autopkgtest log excerpt
==
md5sum: traffic_light-0-ec0.ppm: No such file or directory
traffic_light-0-ec0.ppm: FAILED open or read
traffic_light-0-ec1.pgm: FAILED open or read
md5sum: traffic_light-0-ec1.pgm: No such file or directory
md5sum: traffic_light-1-ec0.ppm: No such file or directory
traffic_light-1-ec0.ppm: FAILED open or read
md5sum: traffic_light-1-ec1.pgm: No such file or directory
traffic_light-1-ec1.pgm: FAILED open or read
md5sum: traffic_light-2-ec0.ppm: No such file or directory
traffic_light-2-ec0.ppm: FAILED open or read
md5sum: traffic_light-2-ec1.pgm: No such file or directory
traffic_light-2-ec1.pgm: FAILED open or read
md5sum: traffic_light-3-ec0.ppm: No such file or directory
traffic_light-3-ec0.ppm: FAILED open or read
md5sum: traffic_light-3-ec1.pgm: No such file or directory
traffic_light-3-ec1.pgm: FAILED open or read
md5sum: animation_patches-0-ec0.ppm: No such file or directory
animation_patches-0-ec0.ppm: FAILED open or read
md5sum: animation_patches-0-ec1.pgm: No such file or directory
animation_patches-0-ec1.pgm: FAILED open or read
md5sum: animation_patches-1-ec0.ppm: No such file or directory
animation_patches-1-ec0.ppm: FAILED open or read
md5sum: animation_patches-1-ec1.pgm: No such file or directory
animation_patches-1-ec1.pgm: FAILED open or read
pq_gradient.pgm: OK
md5sum: WARNING: 12 listed files could not be read

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: jpeg-xl
Source-Version: 0.9.2-6
Done: Mathieu Malaterre 

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

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

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated jpeg-xl 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: Mon, 10 Jun 2024 12:33:42 +0200
Source: jpeg-xl
Architecture: source
Version: 0.9.2-6
Distribution: experimental
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1072835
Changes:
 jpeg-xl (0.9.2-6) experimental; urgency=medium
 .
   * d/t/run-unit-test: Adapt test suite. Closes: #1072835
Checksums-Sha1:
 1d4ba779d84f8f6af46e91caf7313132d5b6b1ce 3154 jpeg-xl_0.9.2-6.dsc
 564b848bbbe8c4c45c545c5497ee34cb0620ae0a 20672 jpeg-xl_0.9.2-6.debian.tar.xz
 54812979d74a739e050def23e2d9201e716e963a 15234 jpeg-xl_0.9.2-6_source.buildinfo
Checksums-Sha256:
 86342363f8f3f6bbf64dd5dacfabf6342ac91fbef4effdaf82b6882c9fa31b93 3154 
jpeg-xl_0.9.2-6.dsc
 60dd259d20c4fb4d6610be1c9b6162f569f659cdd911b3de230b362115fb6f84 20672 
jpeg-xl_0.9.2-6.debian.tar.xz
 1f303386f454b772d4a55766a409b6ed8e529a8f47a17b02e862a845b50934a3 15234 
jpeg-xl_0.9.2-6_source.buildinfo
Files:
 9ef04676596f0ff1d141775a60df0ca4 3154 graphics optional jpeg-xl_0.9.2-6.dsc
 7e03b2450c67fe79a43dc425e7598a65 20672 graphics optional 
jpeg-xl_0.9.2-6.debian.tar.xz
 ebc4027d457178bff0b6b291fa2e7d2e 15234 graphics optional 
jpeg-xl_0.9.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmZm1rkRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0WzqBAAm6olVGAgoVy6bPOQZ39tngnQwpajvBLY
eA/LUIOPbaYgdg/wQ/KUyS5y9ie5yrewLljqY7g1pLnxMb02eqo6Gk8iUVJYhPUa
++ETNc9RNgNx0pveybzyxFfUT2HLeAP+URV+247XI/RKqQBkeK4hE99XgHyB+kPf
6amAvxJJdsxlN7MaDBWhMzhulh9XnFw8BHj2fzKGo/tWWSopxDQ58nDejpXCDnv+
xa8zAjgW873pfZDorF+4Xoy4Illyflw0yecxIESO19j4hyureV3RA4PNo8jcyU+T

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

[Chris Hofstaedtler]

Hi,

On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote:
> > "Simon" == Simon McVittie  writes:
[..]
> Simon> I am unsure whether there is consensus that "the result of
> Simon> gethostname() resolves to some address of the local machine"
> Simon> is also a reasonable thing to demand from all buildds as part
> Simon> of build-essential: /etc/hosts typically makes this true, but
> Simon> is not *guaranteed* to do so. On Linux, packages can ensure
> Simon> that it happens by build-depending on libnss-myhostname
> Simon> [linux-any], if necessary.

I have asked on #debian-buildd, and got the answer that all buildds
have their own hostname in /etc/hosts. Thus this is not the source
of the problem.

> Simon> However, even with both of those, if the krb5 test suite (or
> Simon> protocol) is resolving the local hostname with AF_INET
> Simon> (IPv4-only), and with either AI_ADDRCONFIG or NULL hints,
> Simon> then that will not yield any results on an IPv6-only system
> Simon> for the reasons discussed in #952740 and related bug reports.
> 
> Krb5 is very v6-happy.

It really seems like krb5 is not quite as ipv6-*only*-happy as one
would like to think.

> So, you're suggesting that I fix this by build-depending on
> libnss-myhostname [linux-any] assuming tests are enabled?
> If so, that's easy.

That might or might not help to swipe the problem under a large
enough carpet.

I'll note that on buildds using sbuild with unshare backend, the
setup will look slightly differently. More testing might be
required.

Chris

Processed: mythtv-status: diff for NMU version 1.1.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1052282 + patch
Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile
Added tag(s) patch.
> tags 1052282 + pending
Bug #1052282 [src:mythtv-status] mythtv-status FTBFS with nocheck profile
Added tag(s) pending.

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

Bug#1052282: mythtv-status: diff for NMU version 1.1.0-1.1

[Chris Hofstaedtler]

Control: tags 1052282 + patch
Control: tags 1052282 + pending


Dear maintainer,

I've prepared an NMU for mythtv-status (versioned as 1.1.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

The patch also moves the systemd units into /usr.

Regards.

diff -Nru mythtv-status-1.1.0/debian/changelog mythtv-status-1.1.0/debian/changelog
--- mythtv-status-1.1.0/debian/changelog	2023-07-22 14:16:49.0 +0200
+++ mythtv-status-1.1.0/debian/changelog	2024-06-10 11:26:48.0 +0200
@@ -1,3 +1,12 @@
+mythtv-status (1.1.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch makefile to stop running tests during dh_auto_build
+(Closes: #1052282)
+  * Patch makefile to install systemd units into /usr. (DEP17)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 11:26:48 +0200
+
 mythtv-status (1.1.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mythtv-status-1.1.0/debian/patches/makefile-man-path.patch mythtv-status-1.1.0/debian/patches/makefile-man-path.patch
--- mythtv-status-1.1.0/debian/patches/makefile-man-path.patch	2023-07-16 06:17:12.0 +0200
+++ mythtv-status-1.1.0/debian/patches/makefile-man-path.patch	1970-01-01 01:00:00.0 +0100
@@ -1,17 +0,0 @@
-Description: Install man pages to Debian location
-Author: Andrew Ruthven 
-Forwarded: not-needed
-Last-Update: 2023-07-16

-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/Makefile
-+++ b/Makefile
-@@ -2,7 +2,7 @@
- 
- BINDIR=$(DESTDIR)/usr/bin
- LIBEXECDIR=$(DESTDIR)/usr/libexec/mythtv-status
--MANDIR=$(DESTDIR)/usr/man
-+MANDIR=$(DESTDIR)/usr/share/man
- SYSTEMDDIR=$(DESTDIR)/lib/systemd/system
- 
- package=mythtv-status
diff -Nru mythtv-status-1.1.0/debian/patches/makefile.patch mythtv-status-1.1.0/debian/patches/makefile.patch
--- mythtv-status-1.1.0/debian/patches/makefile.patch	1970-01-01 01:00:00.0 +0100
+++ mythtv-status-1.1.0/debian/patches/makefile.patch	2024-06-10 11:26:48.0 +0200
@@ -0,0 +1,35 @@
+Description: Adapt Makefile for Debian build
+Author: Andrew Ruthven 
+Forwarded: not-needed
+Last-Update: 2024-06-10
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+* Install man pages to Debian location
+* Install systemd units into upstream location
+* Do not run tests while building "all" target
+
+Index: mythtv-status-1.1.0/Makefile
+===
+--- mythtv-status-1.1.0.orig/Makefile
 mythtv-status-1.1.0/Makefile
+@@ -2,8 +2,8 @@
+ 
+ BINDIR=$(DESTDIR)/usr/bin
+ LIBEXECDIR=$(DESTDIR)/usr/libexec/mythtv-status
+-MANDIR=$(DESTDIR)/usr/man
+-SYSTEMDDIR=$(DESTDIR)/lib/systemd/system
++MANDIR=$(DESTDIR)/usr/share/man
++SYSTEMDDIR=$(DESTDIR)/usr/lib/systemd/system
+ 
+ package=mythtv-status
+ releases=sid
+@@ -30,7 +30,7 @@ endif
+ TEST_VERBOSE=0
+ TEST_FILES=t/*.t
+ 
+-all: test
++all:
+ dist: test release
+ 
+ release: $(RELEASE_FILES)
diff -Nru mythtv-status-1.1.0/debian/patches/series mythtv-status-1.1.0/debian/patches/series
--- mythtv-status-1.1.0/debian/patches/series	2023-07-16 06:17:12.0 +0200
+++ mythtv-status-1.1.0/debian/patches/series	2024-06-10 11:26:48.0 +0200
@@ -1 +1 @@
-makefile-man-path.patch
+makefile.patch

Bug#1072760: ikiwiki: FTBFS: Parse errors: No plan found in TAP output

[Jonathan Dowland]

On Fri, Jun 07, 2024 at 05:22:32PM +0200, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:
…
> t/po.t   (Wstat: 65280 (exited 255) Tests: 38 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output

On the face of it this looks to be a result of po4a changes. I'm not
sure if the root cause is the same as #1072643 yet; further
investigation is required.


-- 
  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

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

[Jonas Smedegaard]

Quoting Jeremy Bícha (2024-04-21 19:47:08)
> Simple patch attached.

I am not convinced that this issue should be ignored: Might be revealing
the upstream bugs recently tracked upstream, which might in Debian be
affected by relaxed dependencies e.g. on concurrent-queue.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1072913: libnss-pgsql: remove from Debian?

[Chris Hofstaedtler]

Source: libnss-pgsql
Version: 1.4.0debian-8
Severity: serious

libnss-pgsql's last upload was in 2014. This was a maintainer
upload. The last upstream release apparently happened in 2007. This
is about 17 years ago at the time of writing.

libnss-pgsql currently has an open FTBFS bug, pointing to outdated C
coding standards. Various existing patches also point into this
direction.

NSS plugins should IMO be held to high standards of being up to date
and maintained.

I propose removing libnss-pgsql from Debian, as it seems to be
effectively unmaintained for a very long time already and it looks
like interest has vanished over time.

I propose reassigning this bug to ftp.debian.org in about a month
from now.

Chris

Processed: irker: diff for NMU version 2.23+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1060467 + patch
Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev
Added tag(s) patch.
> tags 1060467 + pending
Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev
Added tag(s) pending.

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

Processed (with 1 error): file loss caused by systemd-dev missing

[Debian Bug Tracking System]

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

> forcemerge 1060467 1072082
Bug #1060467 [src:irker] irker: Please switch Build-Depends to systemd-dev
Unable to merge bugs because:
package of #1072082 is 'irker' not 'src:irker'
Failed to forcibly merge 1060467: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1060467: irker: diff for NMU version 2.23+dfsg-1.1

[Chris Hofstaedtler]

Control: tags 1060467 + patch
Control: tags 1060467 + pending


Dear maintainer,

I've prepared an NMU for irker (versioned as 2.23+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru irker-2.23+dfsg/debian/changelog irker-2.23+dfsg/debian/changelog
--- irker-2.23+dfsg/debian/changelog	2023-02-14 15:37:08.0 +0100
+++ irker-2.23+dfsg/debian/changelog	2024-06-10 11:04:35.0 +0200
@@ -1,3 +1,10 @@
+irker (2.23+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depend on systemd-dev (Closes: #1060467)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 11:04:35 +0200
+
 irker (2.23+dfsg-1) unstable; urgency=low
 
   [ Debian Janitor ]
diff -Nru irker-2.23+dfsg/debian/control irker-2.23+dfsg/debian/control
--- irker-2.23+dfsg/debian/control	2023-02-14 15:37:08.0 +0100
+++ irker-2.23+dfsg/debian/control	2024-06-10 11:04:15.0 +0200
@@ -7,7 +7,7 @@
  debhelper-compat (= 13),
  pkg-config,
  python3,
- systemd,
+ systemd-dev,
  xmlto,
  dh-python
 Standards-Version: 4.6.2

Bug#1069575: FTBFS in experimental

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-05-26 11:20:09)
> On Sat, 25 May 2024 20:27:28 +0200 Jonas Smedegaard  wrote:
>  > Control: block -1 by 1071900
>  >
>  > Quoting Jonas Smedegaard (2024-05-25 20:13:12)
>  > > Ahh, you are talking about *async-channel* v2.3.0. Please consider in
>  > > future to mention crate name, both in email subject and in content, to
>  > > help disambiguate.
>  > >
>  > > I'll have a go at updating async-channel, and tighten dependency on 
> that
>  > > from async-process to see if that solves the FTBFS of async-process.
>  > >
>  > > Thanks for nudging,
>  >
>  > ...and now I remember what held me back last I had a look at this:
>  > async-channel v2.3.0 is broken. Bugfix released with v2.3.1 was to
>  > tighten dependency on concurrent-queue, to a version newer than what is
>  > in Debian.
>  >
>  >
>  > - Jonas
>  >
> 
>  > --
> 
> Ack,
> 
> I will look into updating concurrent-queue to 2.5.0 then.

Any news on updating concurrent-queue to 2.5.0?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1072912: supermin: /lib64: No such file or directory

[Chris Hofstaedtler]

Source: libguestfs
Version: 1:1.52.0-6.1
Severity: serious
User: helm...@debian.org
Usertags: dep17
X-Debbugs-CC: helm...@debian.org

The debootstrap set was uploaded, including a new glibc and
base-files. The owner and exact management of /lib64 has changed.

libguestfs tests now fail, possibly indicating it relies on some
intricate details of the /lib64 symlink. Please investigate and
update the source/tests.

https://ci.debian.net/packages/libg/libguestfs/testing/amd64/47493845/

> 3078 233s execl: /init: No such file or directory
[..]
> 3683 233s supermin: debug: listing directory /lib64
> 3684 233s /lib64: No such file or directory

Chris

Bug#1072798: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 08:49:49 +
with message-id 
and subject line Bug#1072798: fixed in nvidia-graphics-drivers-tesla-470 
470.256.02-1
has caused the Debian Bug report #1072798,
regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092
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.)


-- 
1072798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0090, 
CVE-2024-0092
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2024-0090, 
CVE-2024-0092
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2024-0090, 
CVE-2024-0092
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2024-0090, 
CVE-2024-0092
Control: tag -5 + wontfix
Control: close -5 450.248.02-4
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2024-0090, 
CVE-2024-0092
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2024-0090, 
CVE-2024-0092
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2024-0090, CVE-2024-0092
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: tag -8 + wontfix
Control: close -8 525.147.05-6
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2024-0090, 
CVE-2024-0091, CVE-2024-0092
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -9 535.43.02-1
Control: found -9 545.23.06-1
Control: found -9 550.40.07-1
Control: found -9 555.42.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1
Control: found -1 535.43.02-1
Control: found -1 545.23.06-1
Control: found -1 550.40.07-1
Control: found -1 555.42.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5551

CVE-2024-0090   NVIDIA GPU driver for Windows and Linux contains a
vulnerability where a user can cause an out-of-bounds write. A
successful exploit of this vulnerability might lead to code execution,
denial of service, escalation of privileges, information disclosure, and
data tampering.

CVE-2024-0091   NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where a user can cause an untrusted pointer dereference
by executing a driver API. A successful exploit of this vulnerability
might lead to denial of service, information disclosure, and data
tampering.

CVE-2024-0092   NVIDIA GPU Driver for Windows and Linux contains a
vulnerability where an improper check or improper handling of exception
conditions might lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R555, R550  CVE-2024-0090, CVE-2024-0091, CVE-2024-0092
R535, R470  CVE-2024-0090, CVE-2024-0092

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R555All driver versions prior to 555.52.04  555.52.04
R550All driver versions prior to 550.90.07  550.90.07
R535All driver versions prior to 535.183.01 535.183.01
R470All driver versions prior to 470.256.02 470.256.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.256.02-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-470, 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 

Bug#1064720: marked as done (ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 08:36:03 +
with message-id 
and subject line Bug#1064720: fixed in ruby-capybara 3.40.0+ds-1
has caused the Debian Bug report #1064720,
regarding ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:
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.)


-- 
1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara
Version: 3.36.0+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>   NoMethodError:
> undefined method `stdio' for Puma::Events:Class
> 
>   events = conf.options[:Silent] ? ::Puma::Events.strings : 
> ::Puma::Events.stdio
>   
> ^^
>   # /<>/lib/capybara/registrations/servers.rb:32:in `block 
> in '
>   # /<>/lib/capybara.rb:252:in `run_default_server'
>   # /<>/lib/capybara/registrations/servers.rb:4:in `block in 
> '
>   # /<>/lib/capybara/server.rb:77:in `block in boot'
> 
> Finished in 52.8 seconds (files took 1.06 seconds to load)
> 2512 examples, 36 failures, 6 pending
> 
> Failed examples:
> 
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:1]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by visiting a page directly
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:2]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host returns to 
> the app host when visiting a relative url
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:3]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by setting Capybara.app_host
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:4]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is 
> unaffected by following a relative link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:5]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by following an absolute link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:6]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is 
> unaffected by posting through a relative form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:7]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by posting through an absolute form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:8]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by following a redirect
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:9]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host maintains 
> fragment
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:10]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host redirects to 
> a fragment
> rspec /<>/spec/dsl_spec.rb:165 # Capybara::DSL#current_session 
> should change with the current driver
> rspec /<>/spec/dsl_spec.rb:171 # Capybara::DSL#current_session 
> should be persistent even across driver changes
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:1]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by visiting a page directly
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:2]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host returns 
> to the app host when visiting a relative url
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:3]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by setting Capybara.app_host
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:4]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> unaffected by following a relative link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:5]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by following an absolute link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:6]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> unaffected by posting through a relative form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:7]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by posting through an absolute form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:8]' # 
> 

Bug#1071309: closing 1071309

[Martin]

close 1071309 1.8.4-4
thanks

Processed: closing 1071309

[Debian Bug Tracking System]

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

> close 1071309 1.8.4-4
Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails
Marked as fixed in versions gajim/1.8.4-4.
Bug #1071309 [src:gajim] gajim: FTBFS: test_get_first_grapheme fails
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1071400: marked as done (src:specutils: unsatisfied build dependency in testing: python3-spectral-cube)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 09:48:15 +0200
with message-id 
and subject line Closing outdated bug
has caused the Debian Bug report #1071400,
regarding src:specutils: unsatisfied build dependency in testing: 
python3-spectral-cube
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.)


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

Source: specutils
Version: 1.14.0-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. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

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 ---
With the migration of specreduce, all build dependencies of specutils 
are now satisified again, and in 
https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html 
specutils doesn't appear anymore.


Therefore this bug can be closed.

Best

Ole--- End Message ---

Processed: Bug#1064720 marked as pending in ruby-capybara

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" 
failed: NoMethodError:
Ignoring request to alter tags of bug #1064720 to the same tags previously set

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

Bug#1064720: marked as pending in ruby-capybara

[Utkarsh Gupta]

Control: tag -1 pending

Hello,

Bug #1064720 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/dd48272e5a4623078b8688cb051c137e8b95fb94


Import Debian changelog version 3.40.0+ds-1

ruby-capybara (3.40.0+ds-1) unstable; urgency=medium

  [ Daniel Leidert ]
  * Team upload.
  * Make sure we don't require webdrivers on salsa CI

  [ Leandro Cunha ]
  * New upstream version 3.40.0+ds (Closes: #1064720)
  * d/copyright: Change upstream year and add Thomas Walpole according to the
upstream copyright file
  * d/patches: Fix FTBFS, refresh, rename and apply DEP-3
Drop fix-rack-version-nomethoderror.patch is unnecessary.
  * d/control: Remove deprecated XB-Ruby-Versions and XS-Ruby-Versions


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064720

Processed: Bug#1064720 marked as pending in ruby-capybara

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" 
failed: NoMethodError:
Ignoring request to alter tags of bug #1064720 to the same tags previously set

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

Bug#1064720: marked as pending in ruby-capybara

[Utkarsh Gupta]

Control: tag -1 pending

Hello,

Bug #1064720 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/2d5be37dfa3e7a243300b22f0ba943a48ef14b1f


Prepare for upload with urgency high

Fix a RC bug with FTBFS from Debian archive:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720

Webhook detect
Closes: #1064720


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064720

Bug#1063645: Aw: Re: markdown: missing required debian/rules targets build-arch and/or build-indep

[Bastian Germann]

"Johannes Schauer Marin Rodrigues":
> Do you have recommendations? I just need a drop-in replacement for markdown
> into stdin, html on stdout. Nothing fancy.

I would suggest discount or python3-markdown.

Bug#1071902: marked as done (rust-event-listener: event-listener v5 is considered buggy)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 09:03:50 +0200
with message-id <171800303034.255930.17606408195508401...@auryn.jones.dk>
and subject line Re: rust-event-listener: event-listener v5 is considered buggy
has caused the Debian Bug report #1071902,
regarding rust-event-listener: event-listener v5 is considered buggy
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.)


-- 
1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-event-listener
Version: 2.5.3-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

rust-event-listener v5 is considered buggy upstream, and therefore
unsuitable for a stable Debian release.

Please do *not* release this to Debian unstable, as it will cause at
least anything depending on async-lock to be impossible to resolve its
dependency chain.

https://github.com/smol-rs/async-lock/issues/81

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZSOQAACgkQLHwxRsGg
ASHLRg/9GYKK/Ef2K9e3D/ARSiUVyMY08zIrWer4zlQ+y2jBTJzXxfJu/AIAmx+p
fDbwOiVheuQ+OcTphy2gepYAaIUmyTVM7Y9LPgMqwDQ84wYTCUvR8Fd/UvZ32G93
Qtz/fYP37Xy9Cl0dNxEaun/6wysUkYAWrD/e+1zQsAwVrTqgGr4Ayx0XShP4IRG/
27FQ2NLGs23sRZYQ7C45uJOdZiQHXXTpntN5LyWflHcbQwamB98yqF/9Ncs3EGJp
1JjJGpy2MkAjY9ic5Cqh5mmOyUjCCOnf7k4XIgUh6jhr6ler8Iv+KQ/1LNgQq8GV
mVSrrBY6UaaNqJfGywYzpt/EZqi0qnZl5MhmCJeyWdWgFINk5z6njiTnsQF0bH5o
V1/SxvKvxYkzyCsF5wqNUDJvUjNwzd4BDZWJuBnTHqYEZ+szm8aEpEenuG4ouLpu
NDCj+CbG/b2/dV8Pzy+igUBuQH1BXyf4q9ghQ/qgRiGPbjoRHEgiFLLranRfx8yu
vFCkqcnTf5vboXMwTbH5WFxd2goFRorVmrS6aq3pj2sz3FWalqr/i/b+w/znfA7n
yGSm5+C6HmL7JPLuMzFEVjP/ICUgwzdCFKADKIaiE3SbKuOoQIXz5Ck4b13q7Zv9
Xvbh+BsA+zBqAdmBCcn1OXZJOSV8Ho13mxR2x3jxozBKvI0XyAQ=
=LybZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Quoting Jonas Smedegaard (2024-05-25 21:16:18)
> rust-event-listener v5 is considered buggy upstream, and therefore
> unsuitable for a stable Debian release.
> 
> Please do *not* release this to Debian unstable, as it will cause at
> least anything depending on async-lock to be impossible to resolve its
> dependency chain.
> 
> https://github.com/smol-rs/async-lock/issues/81

The issue is resolved upstream by now.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

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

Bug#1072366: marked as done (libndp: CVE-2024-5564)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 07:02:27 +
with message-id 
and subject line Bug#1072366: fixed in libndp 1.8-2
has caused the Debian Bug report #1072366,
regarding libndp: CVE-2024-5564
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.)


-- 
1072366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libndp
Version: 1.8-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.6-1

Hi,

The following vulnerability was published for libndp.

CVE-2024-5564[0]:
| A vulnerability was found in libndp. This flaw allows a local
| malicious user to cause a buffer overflow in NetworkManager,
| triggered by sending a malformed IPv6 router advertisement packet.
| This issue occurred as libndp was not correctly validating the route
| length information.


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-5564
https://www.cve.org/CVERecord?id=CVE-2024-5564

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libndp
Source-Version: 1.8-2
Done: Florian Ernst 

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

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

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

Debian distribution maintenance software
pp.
Florian Ernst  (supplier of updated libndp 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: Mon, 10 Jun 2024 08:11:09 +0200
Source: libndp
Architecture: source
Version: 1.8-2
Distribution: unstable
Urgency: high
Maintainer: Florian Ernst 
Changed-By: Florian Ernst 
Closes: 1072366
Changes:
 libndp (1.8-2) unstable; urgency=high
 .
   * [a6136d6] add debian/patches/CVE-2024-5564.patch from upstream fixing
 CVE-2024-5564 (Closes: #1072366)
   * [5119f5e] debian/rules: drop now-complete dh_strip --dbgsym-migration
   * [4d590c2] debian/copyright: update debian/ copyright years
   * [3d049d7] debian/control: Standards-Version 4.7.0 (no further changes
 required)
Checksums-Sha1:
 53da38f54a87fbb6acd3ee721436a46a265c9359 2027 libndp_1.8-2.dsc
 ec694003b9b75d7249e3c0654bf2c34b0db57d38 5236 libndp_1.8-2.debian.tar.xz
 5480c76493d639d1bc7f7d81e50cfafe8b0fdbf2 7272 libndp_1.8-2_amd64.buildinfo
Checksums-Sha256:
 47cd371905286c289ed59678278ae434404a5b7869c4c50c82f58fc356e881b6 2027 
libndp_1.8-2.dsc
 c2d3bb63291ff62a0368dcc23383018f18dce8aa873d478606676a50b19d0acb 5236 
libndp_1.8-2.debian.tar.xz
 a54a0f9548ec007cbebcfba42dfa764c683017debc1a754d8bac3b5ef00afb61 7272 
libndp_1.8-2_amd64.buildinfo
Files:
 c6990674ad79a5ef8b725b8e112012d9 2027 net optional libndp_1.8-2.dsc
 bcfd4e207c3247dd18d4553db3e0e0d6 5236 net optional libndp_1.8-2.debian.tar.xz
 180539840fff884bdcf4817f45bf4e99 7272 net optional libndp_1.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmZmmhgACgkQBjdBuvXd
Hs5A0w//QGxcT2M9burngsEeVrMlswBGRvYECJKqWiAIL2kJlXwaBWyR7zQ5YY3N
ox/n55qciX/P6jmmjoZlxxt4xS0nYe8znV7nPVSGjzLuR+YTWdGDifLXDYrN8HGY
ZHR+Ty15xVJEFUJa+F6Kx/IVATfDOFb3326idv6S39rOFUVdtKjtwN3PjzZhDAMS
33qFYTB+L4ahjq7i2Y/oTfEsbPSSq28qRwilDwyTXGVN+rnU7Cc6F0O8P6QRW74y
6xN5Mju8hnIKSf14Cv90HPVh0vlDq7DCLd/3Z+LABxMaTTi5xd44rWhCJm2xBaLm
9soQDOuf8O8hwpZGicgfryIun8UTidI16zgpzBvl1rIsHS2R/E4snPYOnDXnJ2DU
W1N1TUGz388mOE1id43LZb62+aZ+LZr81O4wvfw2rVZbCq29yZ3uJeEb6ecSouxj
TIWBCxIMT7w6fBmzeWCeBNjATRLW9lcpbSa1U9HxQX2lJtfrI7Jgj32KzMjxchhX
Nn7oRYEsnGZawB8MQWB7a/Pu9AMrxPqWyqEhupE+4ivyKAdQbJCRrUvO9pLKnMFF
ub8yTpeck19Iq5bYHXHyDn2nkmr3MW0zysUjwHcrvgjMNBgjh6lmUmsyGHHrhcDz
ZZVtHOjCJMPT5byhgLvoA2luun3Bs/ESVOpinkORGU+U7sO/SA8=
=mR6v
-END PGP SIGNATURE-



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

Bug#1063026: marked as done (Upcoming gtk update)

[Debian Bug Tracking System]

Your message dated Mon, 10 Jun 2024 07:02:18 +
with message-id 
and subject line Bug#1063026: fixed in helvum 0.5.1+20240328-2
has caused the Debian Bug report #1063026,
regarding Upcoming gtk update
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.)


-- 
1063026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: helvum
Version: 0.5.1-1
Severity: normal
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

upstream released a new gtk-rs this weekend. I will upload it to
experimental next weekend; once all affected source packages build fine
with the newer gtk I will upload it to unstable. Since this is a a minor
release patching should be possible; if this works a patch will reach
you then.

best,

werdahias


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

Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
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: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmW/m1cVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1l3YQALSdWXhQwqhU6pzYpxPf9pwfN9lR
pM6Od9BxTZbHfJjOfkJ9vc10d1HSZrfE3mS526tbNmVrEtrXiSMsIvoVbNsI8AfS
rpnbskvYv2WcHD2bLbyiw/nsvzsH5wySFCHMkIHF0pHzq1oDX3l3BhDlEM++6fdW
y3UbYFTTD9NoN5XYpoTFlmFyKKXHC6P/DjUe0cqnOh1K0sTaOMkb6PHhoc6gCb52
FQ9KxC9jJEISUypzz94O7NviD6wzsU6rritMbYHp3jpNMc9gJX35zhf+epoRBtLD
umpW6HrgkCJ58h2P+snP0edDfPtBZn93r/N1P83QZz9lQpnu7+2o/5AvCU1GAp50
g4ZxXn5cWPq52hPZ3dgp9eHwF5wIsegOOPx8aJ6yXsoM/8Uqhsd6Z0j6lvtYbOC9
A1ntKwpwGt/CrX+rF40oFAQDQvsz7ZW3Vzkjx8y/mgcYjybRuEbqBHg2X7/R7H/d
42xpXVJcsOh95Oh8ikNm3ROeZyhdlbty9YpMRZ/ZdgKFpY21gz8ljhvHiZkTUJUE
JcYmO8sMVYsaZ7Y7nSO6LPzFPGMHDRQ4E06DLmX73uVHH8VPMd/MLrJ2mRYBmMWY
KHU/bFZ4gRC8841Cz6ZN6jGHMT77o/gRpFgQi5xQ728zpzz8/7K5iMvyBPaiZbVR
nA2nj8HsYZd7Jai4
=uARj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: helvum
Source-Version: 0.5.1+20240328-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated helvum 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: Mon, 10 Jun 2024 08:22:26 +0200
Source: helvum
Architecture: source
Version: 0.5.1+20240328-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1063026
Changes:
 helvum (0.5.1+20240328-2) unstable; urgency=medium
 .
   * re-release targeted unstable;
 closes: bug#1063026, thanks to Jeremy Bícha
   * update copyright info: update coverage
Checksums-Sha1:
 d5b2bbde52530a8a666f84ba3e3aba229c96edfe 2255 helvum_0.5.1+20240328-2.dsc
 97f37d6107c8bfd2be6ede1603bf3d6dcc75fafc 19452 
helvum_0.5.1+20240328-2.debian.tar.xz
Checksums-Sha256:
 558de77676a73908fa15ea5ce94fbb784da202f49f9aedb329b148feaae71ad5 2255 
helvum_0.5.1+20240328-2.dsc
 3db1e39945b1a492e800cfbe42322c39f9cf23d1023938bc1d7ea290fa61253f 19452 
helvum_0.5.1+20240328-2.debian.tar.xz
Files:
 74f8df48f21f5afba68c04a1c10a44f7 2255 sound optional 
helvum_0.5.1+20240328-2.dsc
 2f2e589bd237429c9bbb8880c31fcc95 19452 sound optional 
helvum_0.5.1+20240328-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZmnxMACgkQLHwxRsGg
ASEpvA//aZfZYgoxo8mw53rj6Xu+8CgBYvl7ZZ1HYfZFJPeS+T0T6JTtXNwR2OD9
5ehqK1WO1h/hwUPDBVEmASMeYb9cOuYUaFM4VOhn9SxIge+ioEAseg/OBjF8jJV7
0XUsFuFsTlolbyZZwj3CZqEluExpJhguAYaq/vk/sE4FP0Z7K5tHCE5ZLSw0/lwn
jcZT3qUlT/gyPTGRFoWHap0pA8TCsDiO/gk5sORzAQB+nQdfGh+0U5GmgVqH+CjB
pbu/1JyRzxbKrAR9ZK9Hbie2vMFgONT+NBUM3tEXF8LFhVwjglrMNhkhKDlUM7C/
DNn+5+ueCrTy/WhvEsO4X/ANPvJiHNiaIqvNfGvb2oXiaCIMpNHAX/Au5ojJcmNa
kHSz5dC4MBgxKCxNk5RqBAbIFeQ3xase/Q/78rcSVE5IgdsNPxS9JwKU9gZQ65ar