Processed: retitle 1072885 to php8.2: CVE-2024-5458

[Debian Bug Tracking System]

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

> # CVE-2024-4577 should be windows specific
> retitle 1072885 php8.2: CVE-2024-5458
Bug #1072885 [src:php8.2] php8.2: CVE-2024-4577 CVE-2024-5458
Changed Bug title to 'php8.2: CVE-2024-5458' from 'php8.2: CVE-2024-4577 
CVE-2024-5458'.
> thanks
Stopping processing here.

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

Bug#1073200: marked as done (ppx-expect: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jun 2024 08:17:15 +0200
with message-id 
and subject line Re: ppx-expect: FTBFS in sid
has caused the Debian Bug report #1073200,
regarding ppx-expect: FTBFS in sid
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.)


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

Source: ppx-expect
Version: 0.16.0-5
Severity: serious

Hello, after the new round of ocaml updates, the package started FTBFS.
I noticed 0.17.0 is out

(cd _build/default && /usr/bin/ocamlc.opt -w -40 -g -bin-annot -I 
evaluator/.ppx_expect_evaluator.objs/byte -I /usr/lib/ocaml/base -I 
/usr/lib/ocaml/base/base_internalhash_types -I /usr/lib/ocaml/base/caml -I 
/usr/lib/ocaml/base/shadow_stdlib -I /usr/lib/ocaml/jane-street-headers -I 
/usr/lib/ocaml/ppx_compare/runtime-lib -I /usr/lib/ocaml/ppx_enumerate/runtime-lib -I 
/usr/lib/ocaml/ppx_hash/runtime-lib -I /usr/lib/ocaml/ppx_inline_test/config -I 
/usr/lib/ocaml/ppx_inline_test/runtime-lib -I /usr/lib/ocaml/ppx_sexp_conv/runtime-lib 
-I /usr/lib/ocaml/ppxlib/print_diff -I /usr/lib/ocaml/re -I /usr/lib/ocaml/seq -I 
/usr/lib/ocaml/sexplib0 -I /usr/lib/ocaml/stdio -I /usr/lib/ocaml/time_now -I 
collector/.expect_test_collector.objs/byte -I common/.expect_test_common.objs/byte -I 
config/types/.expect_test_config_types.objs/byte -I 
make-corrected-file/.make_corrected_file.objs/byte -I 
matcher/.expect_test_matcher.objs/byte -intf-suffix .ml -no-alias-deps -o 
evaluator/.ppx_expect_evaluator.objs/byte/ppx_expect_evaluator.cmo -c -impl 
evaluator/ppx_expect_evaluator.ml)
File "evaluator/ppx_expect_evaluator.ml", line 82, characters 6-10:
82 | | None -> File.initial_dir ()
   

content of that file was removed in 
https://github.com/janestreet/ppx_expect/commit/f613355a6bc949ec7e6fa8e8d62604aa503cac09#diff-b3af3e6c316a3aadcb636cb79d80da1220d2565c5cbfd03d1cecd44af0f744dd

G.


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

Version: 0.17.0-1

Le 14/06/2024 à 14:12, Gianfranco Costamagna a écrit :

Source: ppx-expect
Version: 0.16.0-5
Severity: serious

Hello, after the new round of ocaml updates, the package started FTBFS.
I noticed 0.17.0 is out

(cd _build/default && /usr/bin/ocamlc.opt -w -40 -g -bin-annot -I 
evaluator/.ppx_expect_evaluator.objs/byte -I /usr/lib/ocaml/base -I 
/usr/lib/ocaml/base/base_internalhash_types -I /usr/lib/ocaml/base/caml 
-I /usr/lib/ocaml/base/shadow_stdlib -I 
/usr/lib/ocaml/jane-street-headers -I 
/usr/lib/ocaml/ppx_compare/runtime-lib -I 
/usr/lib/ocaml/ppx_enumerate/runtime-lib -I 
/usr/lib/ocaml/ppx_hash/runtime-lib -I 
/usr/lib/ocaml/ppx_inline_test/config -I 
/usr/lib/ocaml/ppx_inline_test/runtime-lib -I 
/usr/lib/ocaml/ppx_sexp_conv/runtime-lib -I 
/usr/lib/ocaml/ppxlib/print_diff -I /usr/lib/ocaml/re -I 
/usr/lib/ocaml/seq -I /usr/lib/ocaml/sexplib0 -I /usr/lib/ocaml/stdio -I 
/usr/lib/ocaml/time_now -I collector/.expect_test_collector.objs/byte -I 
common/.expect_test_common.objs/byte -I 
config/types/.expect_test_config_types.objs/byte -I 
make-corrected-file/.make_corrected_file.objs/byte -I 
matcher/.expect_test_matcher.objs/byte -intf-suffix .ml -no-alias-deps 
-o evaluator/.ppx_expect_evaluator.objs/byte/ppx_expect_evaluator.cmo -c 
-impl evaluator/ppx_expect_evaluator.ml)

File "evaluator/ppx_expect_evaluator.ml", line 82, characters 6-10:
82 | | None -> File.initial_dir ()
    

content of that file was removed in 
https://github.com/janestreet/ppx_expect/commit/f613355a6bc949ec7e6fa8e8d62604aa503cac09#diff-b3af3e6c316a3aadcb636cb79d80da1220d2565c5cbfd03d1cecd44af0f744dd


G.--- End Message ---

Bug#1073244: ruby-xmlrpc has an undeclared file conflict on /usr/bin/console

[Helmut Grohne]

Package: ruby-xmlrpc
Version: 0.3.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + conserver-client

ruby-xmlrpc has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/bin/console is contained in the packages
 * conserver-client
   * 8.2.6-2 as present in bullseye
   * 8.2.7-2+b1 as present in bookworm
   * 8.2.7-2+b3 as present in trixie|unstable
 * ruby-xmlrpc/0.3.3-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1073243: libcompiler-libs-ocaml-dev, libstdlib-ocaml and libstdlib-ocaml-dev have an undeclared file conflict

[Helmut Grohne]

Package: libstdlib-ocaml,libcompiler-libs-ocaml-dev,libstdlib-ocaml-dev
Version: 5.2.0-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libfindlib-ocaml

libcompiler-libs-ocaml-dev, libstdlib-ocaml and libstdlib-ocaml-dev have
an undeclared file conflict. This may result in an unpack error from
dpkg.

The files
 * /usr/lib/ocaml/compiler-libs/META
 * /usr/lib/ocaml/ocamldoc/META
are contained in the packages
 * libcompiler-libs-ocaml-dev/5.2.0-1~exp1 as present in experimental
 * libfindlib-ocaml
   * 1.8.1-2 as present in bullseye
   * 1.9.6-1+b1 as present in bookworm
   * 1.9.6-1+b2 as present in trixie|unstable

The files
 * /usr/lib/ocaml/dynlink/META
 * /usr/lib/ocaml/threads/META
are contained in the packages
 * libfindlib-ocaml
   * 1.8.1-2 as present in bullseye
   * 1.9.6-1+b1 as present in bookworm
   * 1.9.6-1+b2 as present in trixie|unstable
 * libstdlib-ocaml-dev/5.2.0-1~exp1 as present in experimental

The files
 * /usr/lib/ocaml/stdlib/META
 * /usr/lib/ocaml/str/META
 * /usr/lib/ocaml/unix/META
are contained in the packages
 * libfindlib-ocaml
   * 1.8.1-2 as present in bullseye
   * 1.9.6-1+b1 as present in bookworm
   * 1.9.6-1+b2 as present in trixie|unstable
 * libstdlib-ocaml/5.2.0-1~exp1 as present in experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: ruby-xmlrpc has an undeclared file conflict on /usr/bin/console

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + conserver-client
Bug #1073244 [ruby-xmlrpc] ruby-xmlrpc has an undeclared file conflict on 
/usr/bin/console
Added indication that 1073244 affects conserver-client

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

Processed: libcompiler-libs-ocaml-dev, libstdlib-ocaml and libstdlib-ocaml-dev have an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libfindlib-ocaml
Bug #1073243 [libstdlib-ocaml,libcompiler-libs-ocaml-dev,libstdlib-ocaml-dev] 
libcompiler-libs-ocaml-dev, libstdlib-ocaml and libstdlib-ocaml-dev have an 
undeclared file conflict
Added indication that 1073243 affects libfindlib-ocaml

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

Bug#1067782: datalad downloads dependencies during the build

[Yaroslav Halchenko]

severity -1 normal
thanks

Hi Matthias,

I have failed to reproduce this. I have built 0.19.6-2 in a clean
pbuilder chroot and got

neurodebian@smaug ~/deb/builds/datalad/0.19.6-2-rebuild % grep -1 
'Searching for tqdm' *build
datalad_0.19.6-2_amd64.build-Using /usr/lib/python3/dist-packages
datalad_0.19.6-2_amd64.build:Searching for tqdm==4.66.4
datalad_0.19.6-2_amd64.build-Best match: tqdm 4.66.4
--
datalad_0.19.6-2_amd64.build-Using /usr/lib/python3/dist-packages
datalad_0.19.6-2_amd64.build:Searching for tqdm==4.66.4
datalad_0.19.6-2_amd64.build-Best match: tqdm 4.66.4
--
datalad_0.19.6-2_amd64.build-Using /usr/lib/python3/dist-packages
datalad_0.19.6-2_amd64.build:Searching for tqdm==4.66.4
datalad_0.19.6-2_amd64.build-Best match: tqdm 4.66.4

then I updated and uploaded packaging for 1.1.0-1 and saw similar hits, no 
attempts to get to pypi:

neurodebian@smaug ~/deb/builds/datalad/0.19.6-2-rebuild % grep 'Reading 
https://pypi.org/' *build
neurodebian@smaug ~/deb/builds/datalad/1.1.0-1 % grep 'Reading 
https://pypi.org/' *build

NB Frankly, removing setting empty http_proxy resulted in tests to freeze but
that is orthogonal to this since tests are ran past installation of
depends.

So it would be interesting to know more details on the process to build the
package.  If could be reproduced from a blank debian system (may be a
dockerfile or alike to reproduce) -- would be great.

As can't reproduce, lowering severity

Cheers,

On Tue, 26 Mar 2024, Matthias Klose wrote:

> Package: src:datalad
> Version: 0.19.6-2
> Severity: serious
> Tags: sid trixie

> datalad downloads dependencies during the build:

> [...]
> running build_ext
> Creating /<>/bin/datalad.egg-link (link to .)
> Adding datalad 0.19.6 to easy-install.pth file
> Installing datalad script to bin
> Installing git-annex-remote-datalad script to bin
> Installing git-annex-remote-datalad-archives script to bin
> Installing git-annex-remote-ora script to bin
> Installing git-annex-remote-ria script to bin
> Installing git-credential-datalad script to bin

> Installed /<>
> Processing dependencies for datalad==0.19.6
> Searching for tqdm>=4.32.0
> Reading https://pypi.org/simple/tqdm/
> Downloading 
> https://files.pythonhosted.org/packages/2a/14/e75e52d521442e2fcc9f1df3c5e456aead034203d4797867980de558ab34/tqdm-4.66.2-py3-none-any.whl#sha256=1ee4f8a893eb9bef51c6e35730cebf234d5d0b6bd112b0271e10ed7c24a02bd9
> Best match: tqdm 4.66.2
> Processing tqdm-4.66.2-py3-none-any.whl
> Installing tqdm-4.66.2-py3-none-any.whl to /<>/bin
> Adding tqdm 4.66.2 to easy-install.pth file
> Installing tqdm script to bin



-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik



signature.asc
Description: PGP signature

Bug#1070186: marked as done (python3-datalad: Don't recommend python3-boto)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jun 2024 03:49:07 +
with message-id 
and subject line Bug#1070186: fixed in datalad 1.1.0-1
has caused the Debian Bug report #1070186,
regarding python3-datalad: Don't recommend python3-boto
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.)


-- 
1070186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-datalad
Version: 0.19.6-2
Severity: serious

Debian Policy § 2.2 says that packages in main (like python3-datalad)
are not allowed to have Recommends on packages that are not in main
(unless it is only a non-default alternative for a package in main).

python3-datalad Recommends: python3-boto but python3-boto has been
removed from Testing and will likely be removed from Unstable soon.
See https://bugs.debian.org/1058652

The replacement is python3-boto3 but the package will likely need
changes to upstream code to work with the new version.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: datalad
Source-Version: 1.1.0-1
Done: Yaroslav Halchenko 

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

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

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated datalad package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 14:21:02 -0400
Source: datalad
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Closes: 1063611 1070186
Changes:
 datalad (1.1.0-1) unstable; urgency=medium
 .
   * debian/control
 - *depends on 7zip as preferred to p7zip-full. I do not think there
   are any changes to upstream needed (Closes: #1063611)
 - replace python3-boto with python3-boto3 (Closes: #1070186)
 - add python3-boto3 to build-depends -- testing seems require it
   * debian/patches
 - refreshed
 - deb_setup_no_msgpack_and_duecredit is removed since not needed
   since deb_loosenup_setup_requires just makes it depend on "core" set
   of packages only anyways
Checksums-Sha1:
 d3c26118bcc4fbdf2f77f48f209926490620d34e 2791 datalad_1.1.0-1.dsc
 f2c8e9a5dd5c4e2f06fd84a33ea261f260e8de56 1423136 datalad_1.1.0.orig.tar.gz
 276be83c25c50322b1f6b4653624adbc59e802b9 19492 datalad_1.1.0-1.debian.tar.xz
 63bc8273c7aff5a4d893cb86aa91d2601cd83720 13386 datalad_1.1.0-1_source.buildinfo
Checksums-Sha256:
 4beff267a016c2d2538f9a6f2e017052fb0201c7d3c684c7fc8e486469f96bbe 2791 
datalad_1.1.0-1.dsc
 3403232696ae0e6cbcec56d7cccfac1be8b5d98f66f235e4751dd44fd9f5e8eb 1423136 
datalad_1.1.0.orig.tar.gz
 680487e8987815c20b33323ca3c9348844e3cd48ccc7da2fc066923238294b87 19492 
datalad_1.1.0-1.debian.tar.xz
 a60a2a92dd21e36a249aa6d813421c5c42470a0e61face0a659181bf3d2a3c2d 13386 
datalad_1.1.0-1_source.buildinfo
Files:
 47c47db106ee2ea25c3c0da692ff86fa 2791 science optional datalad_1.1.0-1.dsc
 3b39393b28264775990a40371fdf672c 1423136 science optional 
datalad_1.1.0.orig.tar.gz
 d717f6c4acdaf350dd496c7db3965ec9 19492 science optional 
datalad_1.1.0-1.debian.tar.xz
 3a53f61891dfdd2eece19f5f354cb1d9 13386 science optional 
datalad_1.1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmZsxwAACgkQot4jUGLa
M/o6+A//UiasidhSFpUV6UZuXP7wOYbaRrFAqo40ME40B4MxunvV0opaPypQyuwO
tVbVDdCf3M+O0XK3Iy0D2DUNm/rkBOn22cQhcTFhd38blWpnqkXoUzgjAkGa1us5
ehdR6Y8BoaVH9g7TfqLJ8FCl8h2yDbQ8roFyN2GM3IdYlMv+vUfz5FK2zNRNWpqO
PBGVIL0mxDjO2xoxruQyRAM+vD3o490S0dtRxcmGyQzJVN2u+S2j1BftiNFUbPQI
LGK7CL2kfOUT9nfeyHWJY2h56GnTslcYRUBiEn02ilc1d9EZa6HL/AkZmNBcr2Af
2I/va0Ufv964c5iOj88AwzfxsbHY4MSiCNIGhkri5tSGl6b9Al0lGOV8wQlkrWC1
Ei9YqL1y5uTOme105hWqPfmcabtW5tTCTGjxwGe2/gFSQbYjZhlxPvGxFsVxnfFy
YlmUgWlvJdG991btTwnBaPlV/J26z19+e/ljFIW11NF3lH7L8D3TY8SqTMd3psqe
m3lsvl8zzutI7sfmkd6x/nC/oodK07UpOuMK6UYNqsDXCj1tRKwfMdlbxreaRTy9
37hyLBbseIOfrZeY7Hz3dvLRL2ka9TzBqkP2GAKWu9BDCbcE5dSI0t5eKsBvwMpX
mIJp5j5uZl3znjqWNkeUvTuNNCGaRogVjqmPlXKnVib8krQHBtY=
=QG0Q
-END PGP SIGNATURE-



pgpWUY7WM

Bug#1073239: bb: either no sound frozen text output while using pulseaudio as default on more recent debian

[t]

Package: bb
Version: 1.3rc1-12
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@treaki.tk

hi there,

debian 11 and i have seen this bug since debian 7 or so, it dosnt play 
with sound, only without, thats anoying cause the sound makes it mouch nicer


please look into it finally.

T


-- System Information:
Debian Release: 11.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 
'oldstable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-28-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bb depends on:
ii libaa1 1.4p5-48
ii libc6 2.31-13+deb11u8
ii libmikmod3 3.3.11.1-6

bb recommends no packages.

bb suggests no packages.

-- no debconf information

Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

[Ben Finney]

On 14-Jun-2024, Martin Dosch wrote:

> I am also affected by this bug. I have not added any dput config and 
> therefore nowhere specified a delay so it must be a faulty default 
> config:

At https://salsa.debian.org/debian/dput/-/merge_requests/14> is a
merge request proposing to fix this bug.

Before merging, I need confirmation from someone experiencing this bug,
that the resulting package does indeed fix the bug.

Can you try the resulting Dput package, and confirm whether it corrects the
behaviour in your case?

-- 
 \   “We jealously reserve the right to be mistaken in our view of |
  `\  what exists, given that theories often change under pressure |
_o__)  from further investigation.” —Thomas W. Clark, 2009 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#1073040: dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split'

[Ben Finney]

On 14-Jun-2024, Christoph Berg wrote:
> Re: Ben Finney
> > At https://salsa.debian.org/debian/dput/-/merge_requests/15> is a
> > merge request proposing to fix this bug.
> > 
> > Can you try the resulting Dput package, and confirm whether it corrects
> > the behaviour in your case?
> 
> I don't think I have any ssh options set - it was already failing on
> the default case. I'd say just upload and I'll report back if it's
> still failing.

Before uploading a version that claims to fix the bug, I'll need
confirmation the bug is in fact fixed. Can you try the modified program and
confirm the bug is fixed in that modified version?

-- 
 \ “The Things to do are: the things that need doing, that you see |
  `\ need to be done, and that no one else seems to see need to be |
_o__)   done.” —Richard Buckminster Fuller, 1970-02-16 |
Ben Finney 


signature.asc
Description: PGP signature

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

[Chris Hofstaedtler]

* Sam Hartman  [240614 22:52]:
> > "Chris" == Chris Hofstaedtler  writes:
> 
> Chris> When building krb5 with sbuild, configured to use the unshare
> Chris> backend, the t_iprop.py test apparently times out without any
> Chris> output.
> 
> I'm guessing, but have not confirmed that sbuild unshare is setting up a
> network namespace with nothing but lo in it.

Yeah. For details, you can check:
https://sources.debian.org/src/sbuild/0.85.10/lib/Sbuild/ChrootUnshare.pm/#L320

> I've certainly seen the same behavior you see in such a configuration.
> What's happening is that get_wildcard_address in kpropd.c passes
> AI_ADDRCONFIG into getaddrinfo.  Since loopback addresses are ignored by
> AI_ADDRCONFIG, there is no valid v4 or v6 address and  the routine fails
> to find a wildcard address to bind to.
> 
> I'm mistified why the daemon doesn't just fail at thait point, but I
> have not looked into that.

Having it stuck there is certainly annoying.

> I did modify get_wildcard_address to prefer AI_ADDRCONFIG but to fall
> back to calling getaddrinfo without AI_ADDRCONFIG if that's all that
> will work.
> 
> That's enough for t_kpropd.py to succeed.
> I'm working through a few other FTBFS issues in a container, some of
> which apparently didn't show up for sbuild unshare (they happen earlier
> in the build) but which are getting in my way.
> I hope to have 1.21.2 uploaded and building by end of weekend.

Great. Thanks for your work!

Chris

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

[Sam Hartman]

> "Chris" == Chris Hofstaedtler  writes:

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

I'm guessing, but have not confirmed that sbuild unshare is setting up a
network namespace with nothing but lo in it.
I've certainly seen the same behavior you see in such a configuration.
What's happening is that get_wildcard_address in kpropd.c passes
AI_ADDRCONFIG into getaddrinfo.  Since loopback addresses are ignored by
AI_ADDRCONFIG, there is no valid v4 or v6 address and  the routine fails
to find a wildcard address to bind to.

I'm mistified why the daemon doesn't just fail at thait point, but I
have not looked into that.
I did modify get_wildcard_address to prefer AI_ADDRCONFIG but to fall
back to calling getaddrinfo without AI_ADDRCONFIG if that's all that
will work.

That's enough for t_kpropd.py to succeed.
I'm working through a few other FTBFS issues in a container, some of
which apparently didn't show up for sbuild unshare (they happen earlier
in the build) but which are getting in my way.
I hope to have 1.21.2 uploaded and building by end of weekend.


signature.asc
Description: PGP signature

Bug#1073230: varna: autopkgtest regression: errors and than hangs

[Paul Gevers]

Source: varna
Version: 3-93+ds-5
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it started to fail 
recently. Can you please investigate the situation and fix it? I copied 
some of the output at the bottom of this report.


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


Because the test seems to hang and only times out after 2:47h I have 
added it to our reject_list and will remove it when this bug is closed.


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073229: rust-temp-testdir: autopkgtest timeouts: test::should_not_leave_a_dangling_empty_directory hangs

[Paul Gevers]

Source: rust-temp-testdir
Version: 0.2.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. What's worse, 
it fails because it seems to hang and eventually times out due to 
autopkgtest. Can you please investigate the situation and fix it? I 
copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


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


Paul

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

 26s test test::should_resolve_root_in_env ... FAILED
 26s test test::should_resolve_rstest_temp_dir_root_name_in_env ... FAILED
 26s test test::tempdir_permanent_should_do_not_remove_dir ... FAILED
 26s test test::two_temp_dir_should_have_different_path ... FAILED
 86s test test::should_not_leave_a_dangling_empty_directory has been 
running for over 60 seconds
10026s autopkgtest [09:37:55]: ERROR: timed out on command "su -s 
/bin/bash debci ...


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:makedumpfile: fails to migrate to testing for too long: fails its own autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:1.7.5-2
Bug #1073226 [src:makedumpfile] src:makedumpfile: fails to migrate to testing 
for too long: fails its own autopkgtest
Marked as fixed in versions makedumpfile/1:1.7.5-2.
Bug #1073226 [src:makedumpfile] src:makedumpfile: fails to migrate to testing 
for too long: fails its own autopkgtest
Marked Bug as done

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

Bug#1073226: src:makedumpfile: fails to migrate to testing for too long: fails its own autopkgtest

[Paul Gevers]

Source: makedumpfile
Version: 1:1.7.5-1
Severity: serious
Control: close -1 1:1.7.5-2
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:makedumpfile has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
added an autopkgtest (thanks for that), but it fails.


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=makedumpfile



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:libmodule-faker-perl: fails to migrate to testing for too long: blocked by non-migrating dependency

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.027-1
Bug #1073225 [src:libmodule-faker-perl] src:libmodule-faker-perl: fails to 
migrate to testing for too long: blocked by non-migrating dependency
Marked as fixed in versions libmodule-faker-perl/0.027-1.
Bug #1073225 [src:libmodule-faker-perl] src:libmodule-faker-perl: fails to 
migrate to testing for too long: blocked by non-migrating dependency
Marked Bug as done
> block -1 by 1071967
Bug #1073225 {Done: Paul Gevers } [src:libmodule-faker-perl] 
src:libmodule-faker-perl: fails to migrate to testing for too long: blocked by 
non-migrating dependency
1073225 was not blocked by any bugs.
1073225 was not blocking any bugs.
Added blocking bug(s) of 1073225: 1071967

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

Bug#1073225: src:libmodule-faker-perl: fails to migrate to testing for too long: blocked by non-migrating dependency

[Paul Gevers]

Source: libmodule-faker-perl
Version: 0.025-1
Severity: serious
Control: close -1 0.027-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1071967

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:libmodule-faker-perl has been trying to 
migrate for 33 days [2]. Hence, I am filing this bug. The version in 
unstable has a new dependency that's not ready to migrate: 
libdata-fake-perl.


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=libmodule-faker-perl



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-pascal-devel] Bug#1072718: lazarus: Lazarus fails to compile itself

[Debian Bug Tracking System]

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

> package lazarus
Limiting to bugs with field 'package' containing at least one of 'lazarus'
Limit currently set to 'package':'lazarus'

> severity 1072718 normal
Bug #1072718 [lazarus] lazarus: Lazarus fails to compile itself
Severity set to 'normal' from 'serious'
> tags 1072718 - ftbfs + confirmed
Bug #1072718 [lazarus] lazarus: Lazarus fails to compile itself
Removed tag(s) ftbfs.
Bug #1072718 [lazarus] lazarus: Lazarus fails to compile itself
Added tag(s) confirmed.
>
End of message, stopping processing here.

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

Processed: src:slurm-wlm: fails to migrate to testing for too long: not installable on armel, armhf and i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 23.11.7-1
Bug #1073224 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing for too 
long: not installable on armel, armhf and i386
Marked as fixed in versions slurm-wlm/23.11.7-1.
Bug #1073224 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing for too 
long: not installable on armel, armhf and i386
Marked Bug as done

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

Bug#1073224: src:slurm-wlm: fails to migrate to testing for too long: not installable on armel, armhf and i386

[Paul Gevers]

Source: slurm-wlm
Version: 23.11.4-2
Severity: serious
Control: close -1 23.11.7-1
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:slurm-wlm has been trying to migrate for 
33 days [2]. Hence, I am filing this bug. The migration software warns 
that slurm-wlm-basic-plugins can't be installed on armel, armhf and i386.


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=slurm-wlm



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073223: src:strace: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: strace
Version: 6.5-0.1
Severity: serious
Control: close -1 6.8-2
X-Debbugs-CC: tsu.y...@gmail.com, e...@debian.org, zu...@debian.org
Tags: sid trixie ftbfs
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:strace has been trying to migrate for 35 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on s390x.


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=strace



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:strace: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.8-2
Bug #1073223 [src:strace] src:strace: fails to migrate to testing for too long: 
FTBFS on s390x
Marked as fixed in versions strace/6.8-2.
Bug #1073223 [src:strace] src:strace: fails to migrate to testing for too long: 
FTBFS on s390x
Marked Bug as done

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

Bug#1072718: [Pkg-pascal-devel] Bug#1072718: lazarus: Lazarus fails to compile itself

[Peter B]

On 07/06/2024 02:26, Bas van Besouw wrote:

Package: lazarus
Version: 3.0+dfsg1-8
Severity: serious
Tags: ftbfs


Hi Bas,

some general points about bug reporting;

1)  The tag ftbfs is used when the package does not build from the 
debian source (using debuild or whatever)


https://buildd.debian.org/status/package.php?p=lazarus
Lazarus is building fine from source.

When a compiler fails to build something locally, that is not ftbfs.
If the package really was ftbfs, there would be nothing for users to 
install.



2)  The severity serious means a "severe violation of Debian policy".

https://www.debian.org/Bugs/Developer#severities

Lazarus failing to rebuild the IDE, but generally working fine apart 
from that, is unfortunate, and definitely

a [Normal] bug, but it is hardly a "severe violation of Debian policy".


Regards,
Peter

P.S.   I can reproduce this problem too, with both 3.0 & 3.4 Debian 
packages,

  but rebuilding the IDE works with the Arch Linux 3.4 package.

Processed: src:syncthingtray: fails to migrate to testing for too long: FTBFS on arm64 and i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.2-1
Bug #1073222 [src:syncthingtray] src:syncthingtray: fails to migrate to testing 
for too long: FTBFS on arm64 and i386
Marked as fixed in versions syncthingtray/1.5.2-1.
Bug #1073222 [src:syncthingtray] src:syncthingtray: fails to migrate to testing 
for too long: FTBFS on arm64 and i386
Marked Bug as done

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

Bug#1073222: src:syncthingtray: fails to migrate to testing for too long: FTBFS on arm64 and i386

[Paul Gevers]

Source: syncthingtray
Version: 1.4.12-1
Severity: serious
Control: close -1 1.5.2-1
Tags: sid trixie ftbfs
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:syncthingtray has been trying to migrate 
for 38 days [2]. Hence, I am filing this bug. The version in unstable 
failed to build on arm64 and i386.


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=syncthingtray



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073221: src:tpm2-tss: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Source: tpm2-tss
Version: 4.0.1-7.2
Severity: serious
Control: close -1 4.1.3-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1070720

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:tpm2-tss has been trying to migrate for 38 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on armel and armhf as reported in bug 1070720.


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=tpm2-tss



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:tpm2-tss: fails to migrate to testing for too long: FTBFS on armel and armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 4.1.3-1
Bug #1073221 [src:tpm2-tss] src:tpm2-tss: fails to migrate to testing for too 
long: FTBFS on armel and armhf
Marked as fixed in versions tpm2-tss/4.1.3-1.
Bug #1073221 [src:tpm2-tss] src:tpm2-tss: fails to migrate to testing for too 
long: FTBFS on armel and armhf
Marked Bug as done
> block -1 by 1070720
Bug #1073221 {Done: Paul Gevers } [src:tpm2-tss] 
src:tpm2-tss: fails to migrate to testing for too long: FTBFS on armel and armhf
1073221 was not blocked by any bugs.
1073221 was not blocking any bugs.
Added blocking bug(s) of 1073221: 1070720

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

Processed: src:ifupdown-ng: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.12.1-5
Bug #1073219 [src:ifupdown-ng] src:ifupdown-ng: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked as fixed in versions ifupdown-ng/0.12.1-5.
Bug #1073219 [src:ifupdown-ng] src:ifupdown-ng: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked Bug as done

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

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

[Paul Gevers]

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

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1073189 src:awscli
Bug #1073189 [awscli] awscli: ImportError: cannot import name DEFAULT_CIPHERS 
from urllib3.util.ssl_
Bug reassigned from package 'awscli' to 'src:awscli'.
No longer marked as found in versions awscli/2.15.22-1.
Ignoring request to alter fixed versions of bug #1073189 to the same values 
previously set
> reassign 1073191 src:awscli
Bug #1073191 [awscli] awscli: ImportError: cannot import name DEFAULT_CIPHERS 
from urllib3.util.ssl_
Bug reassigned from package 'awscli' to 'src:awscli'.
No longer marked as found in versions awscli/2.15.22-1.
Ignoring request to alter fixed versions of bug #1073191 to the same values 
previously set
> forcemerge 1073178 1073189 1073191
Bug #1073178 [src:awscli] awscli: please update awsci and/or botocore to 
support urllib3 2.x
Bug #1073191 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Severity set to 'serious' from 'important'
Marked as found in versions awscli/2.15.22-1.
Bug #1073189 [src:awscli] awscli: ImportError: cannot import name 
DEFAULT_CIPHERS from urllib3.util.ssl_
Severity set to 'serious' from 'important'
Marked as found in versions awscli/2.15.22-1.
Merged 1073178 1073189 1073191
>
End of message, stopping processing here.

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

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

[Paul Gevers]

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

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:vim-eblook: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.4.0-1
Bug #1073218 [src:vim-eblook] src:vim-eblook: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked as fixed in versions vim-eblook/1.4.0-1.
Bug #1073218 [src:vim-eblook] src:vim-eblook: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked Bug as done

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

Processed (with 1 error): forcibly merging 1073178 1073189 1073191

[Debian Bug Tracking System]

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

> forcemerge 1073178 1073189 1073191
Bug #1073178 [src:awscli] awscli: please update awsci and/or botocore to 
support urllib3 2.x
Unable to merge bugs because:
package of #1073191 is 'awscli' not 'src:awscli'
package of #1073189 is 'awscli' not 'src:awscli'
Failed to forcibly merge 1073178: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1058104: astropy-helpers: FTBFS: ModuleNotFoundError: No module named 'imp'

[Boyuan Yang]

X-Debbugs-CC: oleb...@debian.org

Hi,

On Thu, 14 Dec 2023 08:51:59 +0100 Ole Streicher  wrote:
> Control: tags -1 wontfix
> 
> astropy-helpers is an outdated helper package for building packages in 
> the Astropy ecosystem. It is recently superceded by extension-helpers. 
> The package should end its career now, and be removed before trixie.
> 
> I think that there are no longer Debian packages build-dependent from 
> astropy-helpers. If there are, thes should be instead updated and/or 
> ported to extension-helpers.

==
-> % build-rdeps python3-astropy-helpers
Reverse Build-depends in unstable/main:
---

astroquery
hipspy

Found a total of 2 reverse build-depend(s) for python3-astropy-helpers.

Reverse Build-depends in unstable/contrib:
--

No reverse build-depends found for python3-astropy-helpers.

Reverse Build-depends in unstable/non-free:
---

No reverse build-depends found for python3-astropy-helpers.

Reverse Build-depends in unstable/non-free-firmware:


No reverse build-depends found for python3-astropy-helpers.
===

Two reverse-dependencies exist, and both of them are not having active
upstream development. You are also listed as the uploader for them.

If you believe that this issue will not be fixed upstream, please review
the current status of these packages and determine how to proceed. Thanks!

Best,
Boyuan Yang


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

Bug#1039883: linux: ext4 corruption with symlinks

[Luis Henriques]

On Mon 10 Jun 2024 06:03:58 PM +02, Ben Hutchings wrote;

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

Because I recently fixed an issue in the fast commit code[1] I was hoping
that you were hitting the same bug.  I've executed the reproducer with the
fix (which hasn't been merged yet) and realised it's definitely a
different problem.

Debugged the issue a bit, it seems to be related with the fact that
ext4_fc_write_inode_data() isn't able to cope with the fact that
'ei->i_fc_lblk_len' is set to EXT_MAX_BLOCKS.

I'm CC'ing Harshad, maybe he has some idea.

[1] https://lore.kernel.org/all/20240529092030.9557-2-luis.henriq...@linux.dev

Cheers,
-- 
Luís

Bug#1073199: botch: please update from libyojson-ocaml-dev to new yojson-tools package

[Johannes Schauer Marin Rodrigues]

Hi,

I'm on vacation right now with very limited internet.

If you like, please feel free to NMU.

Thanks!

cheers, josch

Quoting Gianfranco Costamagna (2024-06-14 14:36:58)
> Hello, we should also add it to build-depends:
> 
> --- botch-0.24/debian/control   2024-06-14 14:01:13.0 +0200
> +++ botch-0.24/debian/control   2024-06-14 14:35:36.0 +0200
> @@ -36,6 +36,7 @@
>libgraph-easy-perl  ,
>graphviz,
>black   ,
> + yojson-tools,
>   Build-Depends-Indep:
>discount ,
>graphviz ,
> 
> G.
> 
> On Fri, 14 Jun 2024 14:06:43 +0200 Gianfranco Costamagna 
>  wrote:
> > Package: botch
> > Version: 0.24-3
> > Severity: serious
> > Tags: patch
> > 
> > 
> > Hello, new yojson 2.2.1-1 created a new yojson-tools package, making this 
> > package fail
> > it's own autopkgtests due to missing tools (ydump)
> > 
> > I think the best way to move forward is to update the dependency of your 
> > package
> > 
> >* Depend on yojson-tools instead of old libyojson-ocaml-dev
> >  to fix missing ydump tool (split from libyojson-ocaml-dev)
> >  This fixes autopkgtests
> > 
> > 
> > Thanks for considering the patch.
> > 
> > --- botch-0.24/debian/control 2024-06-10 12:40:37.0 +0200
> > +++ botch-0.24/debian/control 2024-06-14 14:01:13.0 +0200
> > @@ -60,7 +60,7 @@
> >python3-pygraphviz (>= 1.4~rc1),
> >zutils,
> >dpkg-dev,
> > - libyojson-ocaml-dev,
> > + yojson-tools,
> >   # libjs-jquery-tablesorter and libjs-jquery are needed to look at the 
> > generated
> >   # HTML with javascript bling
> >   Recommends:

signature.asc
Description: signature

Processed: (No Subject)

[Debian Bug Tracking System]

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

> found 1066820 python-aiosmtpd/1.2.2-1
Bug #1066820 {Done: Jakob Haufe } [src:python-aiosmtpd] 
python-aiosmtpd: CVE-2024-27305
Marked as found in versions python-aiosmtpd/1.2.2-1.
> found 1072119 python-aiosmtpd/1.2.2-1
Bug #1072119 {Done: Jakob Haufe } [src:python-aiosmtpd] 
python-aiosmtpd: CVE-2024-34083
Marked as found in versions python-aiosmtpd/1.2.2-1.
> thanks
Stopping processing here.

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

Bug#1073205: docker-compose: new python3-requests dependency brokes docker-compose

[Ernesto Domato]

Package: docker-compose
Version: 1.29.2-6
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: edom...@gmail.com

Dear Maintainer,

docker-compose depends on python3-compose which in turn depends on
python3-requests

Yesterday it was updated from 2.31.0+dfsg-2 to 2.32.3+dfsg-1 and brokes docker-
compose
with "Not supported URL scheme http+docker" error

Here [1] is an issue report against docker-py, a Docker SDK for Python that
explains the problem.

My knowledge of Python is very poor, but later I'll try to do a patch to fix
the problem.

Best regards,
Ernesto

[1] https://github.com/docker/docker-py/issues/3256


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

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

Versions of packages docker-compose depends on:
ii  python33.11.8-1
ii  python3-compose1.29.2-6
ii  python3-distutils  3.12.3-3.1

Versions of packages docker-compose recommends:
ii  docker.io  20.10.25+dfsg1-3

docker-compose suggests no packages.

-- no debconf information

Processed: (No Subject)

[Debian Bug Tracking System]

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

> found 1066820 python-aiosmtpd/1.4.3-1.1
Bug #1066820 {Done: Jakob Haufe } [src:python-aiosmtpd] 
python-aiosmtpd: CVE-2024-27305
Marked as found in versions python-aiosmtpd/1.4.3-1.1.
> found 1072119 python-aiosmtpd/1.4.3-1.1
Bug #1072119 {Done: Jakob Haufe } [src:python-aiosmtpd] 
python-aiosmtpd: CVE-2024-34083
Marked as found in versions python-aiosmtpd/1.4.3-1.1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1073188: dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1073188 [src:dxvk] dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc 
using -mbranch-protection=standard
Added tag(s) patch.

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

Bug#1073188: dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard

[Emanuele Rocca]

Control: tags -1 + patch

On 2024-06-14 10:42, Emanuele Rocca wrote:
>  stderr: x86_64-w64-mingw32-gcc: error: unrecognized command-line option 
> ‘-mbranch-protection=standard’

Please consider applying the attached patch to fix this FTBFS bug by
using CFLAGS as defined for amd64 instead of arm64.

The patch additionally uses x86_64-w64-mingw32-objcopy on arm64 instead
of aarch64-w64-mingw32-objcopy given that the latter does not exist.

Thanks,
  ema
diff -Nru dxvk-2.3.1/debian/changelog dxvk-2.3.1/debian/changelog
--- dxvk-2.3.1/debian/changelog	2024-05-08 09:37:24.0 +
+++ dxvk-2.3.1/debian/changelog	2024-06-14 11:54:49.0 +
@@ -1,3 +1,11 @@
+dxvk (2.3.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use amd64 CFLAGS when building on arm64 (Closes: #1073188).
+  * Use x86_64-w64-mingw32-objcopy on arm64.
+
+ -- Emanuele Rocca   Fri, 14 Jun 2024 13:54:49 +0200
+
 dxvk (2.3.1-1) unstable; urgency=medium
 
   * NUR:
diff -Nru dxvk-2.3.1/debian/rules dxvk-2.3.1/debian/rules
--- dxvk-2.3.1/debian/rules	2024-05-08 09:37:24.0 +
+++ dxvk-2.3.1/debian/rules	2024-06-14 11:54:49.0 +
@@ -14,6 +14,11 @@
 # fails with: unrecognized option '-z'
 export DEB_BUILD_MAINT_OPTIONS := hardening=-relro
 
+ifeq ($(DEB_TARGET_ARCH),arm64)
+	CFLAGS = $(shell dpkg-architecture -aamd64 -f -c dpkg-buildflags --get CFLAGS)
+	CXXFLAGS = $(shell dpkg-architecture -aamd64 -f -c dpkg-buildflags --get CXXFLAGS)
+endif
+
 LDFLAGS += -flto -Wl,--build-id
 
 # Meson flags
diff -Nru dxvk-2.3.1/debian/strip_debug.sh dxvk-2.3.1/debian/strip_debug.sh
--- dxvk-2.3.1/debian/strip_debug.sh	2024-05-08 09:37:24.0 +
+++ dxvk-2.3.1/debian/strip_debug.sh	2024-06-14 11:54:49.0 +
@@ -33,6 +33,10 @@
 # Sequence made according to dh_strip but using binutils-mingw-w64-x86-64 tools
 # https://salsa.debian.org/debian/debhelper/-/blob/main/dh_strip
 
+if [ "${DEB_HOST_GNU_CPU}" = "aarch64" ]; then
+	DEB_HOST_GNU_CPU=x86_64
+fi
+
 # Note: --compress-debug-sections is not supported by winedbg and will cause a crash
 ${DEB_HOST_GNU_CPU}-w64-mingw32-objcopy --only-keep-debug "$BINARY_FILE" "$DEBUG_FILE"
 chmod 0644 "$DEBUG_FILE"

Bug#1073199: botch: please update from libyojson-ocaml-dev to new yojson-tools package

[Gianfranco Costamagna]

Hello, we should also add it to build-depends:

--- botch-0.24/debian/control   2024-06-14 14:01:13.0 +0200
+++ botch-0.24/debian/control   2024-06-14 14:35:36.0 +0200
@@ -36,6 +36,7 @@
  libgraph-easy-perl  ,
  graphviz,
  black   ,
+ yojson-tools,
 Build-Depends-Indep:
  discount ,
  graphviz ,

G.

On Fri, 14 Jun 2024 14:06:43 +0200 Gianfranco Costamagna 
 wrote:

Package: botch
Version: 0.24-3
Severity: serious
Tags: patch


Hello, new yojson 2.2.1-1 created a new yojson-tools package, making this 
package fail
it's own autopkgtests due to missing tools (ydump)

I think the best way to move forward is to update the dependency of your package

   * Depend on yojson-tools instead of old libyojson-ocaml-dev
 to fix missing ydump tool (split from libyojson-ocaml-dev)
 This fixes autopkgtests


Thanks for considering the patch.

--- botch-0.24/debian/control   2024-06-10 12:40:37.0 +0200
+++ botch-0.24/debian/control   2024-06-14 14:01:13.0 +0200
@@ -60,7 +60,7 @@
   python3-pygraphviz (>= 1.4~rc1),
   zutils,
   dpkg-dev,
- libyojson-ocaml-dev,
+ yojson-tools,
  # libjs-jquery-tablesorter and libjs-jquery are needed to look at the 
generated
  # HTML with javascript bling
  Recommends:


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073200: ppx-expect: FTBFS in sid

[Gianfranco Costamagna]

Source: ppx-expect
Version: 0.16.0-5
Severity: serious

Hello, after the new round of ocaml updates, the package started FTBFS.
I noticed 0.17.0 is out

(cd _build/default && /usr/bin/ocamlc.opt -w -40 -g -bin-annot -I 
evaluator/.ppx_expect_evaluator.objs/byte -I /usr/lib/ocaml/base -I 
/usr/lib/ocaml/base/base_internalhash_types -I /usr/lib/ocaml/base/caml -I 
/usr/lib/ocaml/base/shadow_stdlib -I /usr/lib/ocaml/jane-street-headers -I 
/usr/lib/ocaml/ppx_compare/runtime-lib -I /usr/lib/ocaml/ppx_enumerate/runtime-lib -I 
/usr/lib/ocaml/ppx_hash/runtime-lib -I /usr/lib/ocaml/ppx_inline_test/config -I 
/usr/lib/ocaml/ppx_inline_test/runtime-lib -I /usr/lib/ocaml/ppx_sexp_conv/runtime-lib 
-I /usr/lib/ocaml/ppxlib/print_diff -I /usr/lib/ocaml/re -I /usr/lib/ocaml/seq -I 
/usr/lib/ocaml/sexplib0 -I /usr/lib/ocaml/stdio -I /usr/lib/ocaml/time_now -I 
collector/.expect_test_collector.objs/byte -I common/.expect_test_common.objs/byte -I 
config/types/.expect_test_config_types.objs/byte -I 
make-corrected-file/.make_corrected_file.objs/byte -I 
matcher/.expect_test_matcher.objs/byte -intf-suffix .ml -no-alias-deps -o 
evaluator/.ppx_expect_evaluator.objs/byte/ppx_expect_evaluator.cmo -c -impl 
evaluator/ppx_expect_evaluator.ml)
File "evaluator/ppx_expect_evaluator.ml", line 82, characters 6-10:
82 | | None -> File.initial_dir ()
   

content of that file was removed in 
https://github.com/janestreet/ppx_expect/commit/f613355a6bc949ec7e6fa8e8d62604aa503cac09#diff-b3af3e6c316a3aadcb636cb79d80da1220d2565c5cbfd03d1cecd44af0f744dd

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073199: botch: please update from libyojson-ocaml-dev to new yojson-tools package

[Gianfranco Costamagna]

Package: botch
Version: 0.24-3
Severity: serious
Tags: patch


Hello, new yojson 2.2.1-1 created a new yojson-tools package, making this 
package fail
it's own autopkgtests due to missing tools (ydump)

I think the best way to move forward is to update the dependency of your package

  * Depend on yojson-tools instead of old libyojson-ocaml-dev
to fix missing ydump tool (split from libyojson-ocaml-dev)
This fixes autopkgtests


Thanks for considering the patch.

--- botch-0.24/debian/control   2024-06-10 12:40:37.0 +0200
+++ botch-0.24/debian/control   2024-06-14 14:01:13.0 +0200
@@ -60,7 +60,7 @@
  python3-pygraphviz (>= 1.4~rc1),
  zutils,
  dpkg-dev,
- libyojson-ocaml-dev,
+ yojson-tools,
 # libjs-jquery-tablesorter and libjs-jquery are needed to look at the generated
 # HTML with javascript bling
 Recommends:


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073196: marked as done (python3-docker: It does not work with the new version of python3-requests)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 11:49:49 +
with message-id 
and subject line Bug#1073196: fixed in python-docker 6.1.3-0.2
has caused the Debian Bug report #1073196,
regarding python3-docker: It does not work with the new version of 
python3-requests
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.)


-- 
1073196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-docker
Version: 6.1.3-0.1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ltw...@debian.org

It is fixed upstream here: https://github.com/docker/docker-py/pull/3257/files


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

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

Versions of packages python3-docker depends on:
ii  python33.11.8-1
ii  python3-distutils  3.12.3-3.1
ii  python3-packaging  24.0-1
ii  python3-requests   2.32.3+dfsg-1
ii  python3-urllib32.0.7-2
ii  python3-websocket  1.7.0-1

python3-docker recommends no packages.

python3-docker suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-docker
Source-Version: 6.1.3-0.2
Done: Salvo 'LtWorf' Tomaselli 

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

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

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

Debian distribution maintenance software
pp.
Salvo 'LtWorf' Tomaselli  (supplier of updated python-docker 
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, 14 Jun 2024 13:14:53 +0200
Source: python-docker
Architecture: source
Version: 6.1.3-0.2
Distribution: unstable
Urgency: medium
Maintainer: Docker Compose Team 
Changed-By: Salvo 'LtWorf' Tomaselli 
Closes: 1073196
Changes:
 python-docker (6.1.3-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream patch to work with new python3-requests (Closes: #1073196)
Checksums-Sha1:
 be592c52524413ba0bc7a06695749f06b65cc88c 2276 python-docker_6.1.3-0.2.dsc
 251fb85baac0717a54801882b93e310d320fb092 5924 
python-docker_6.1.3-0.2.debian.tar.xz
 a3271ba8fa7125f24e326cd8354d18a67408003c 7342 
python-docker_6.1.3-0.2_amd64.buildinfo
Checksums-Sha256:
 e9726387c35da8a8947396ff198533b18f1366f5841a6cfe6b6472fa6d0b44b5 2276 
python-docker_6.1.3-0.2.dsc
 8e11e7619d2dee53dc60a297300ad4c7bec0bf8aacfba7e94c6066525a7546f3 5924 
python-docker_6.1.3-0.2.debian.tar.xz
 bba4213676e732d87171f26367a7a87a8ab7b07b98a4a11857410792aca87a0d 7342 
python-docker_6.1.3-0.2_amd64.buildinfo
Files:
 b6662eb450be69abecd6e435355216d7 2276 python optional 
python-docker_6.1.3-0.2.dsc
 1c5604a911caeebad75355e4b706b88c 5924 python optional 
python-docker_6.1.3-0.2.debian.tar.xz
 e2386aa78f0311c72640c6efaca324a4 7342 python optional 
python-docker_6.1.3-0.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmZsKOAACgkQs6fPDIAY
hs8tbg//Xht2Vu/vy1azYRC4vs5XuSs33nDGPEyIFdX5B2xetU2GsOtxajz7FX7t
ygFYinDPKdVNVGR3PhO6XClDhcFJx3KhBVjRCLvFAPTpsEkXq7WT65NTtCaPScNE
KIOqje5Gl/Xn2bPcO+E42cutWafp4JfmXydoy1d/b1t6aLuWAjUpD0PriZKNaUbu
bgqL0+YV9o51FIJzkVSoyAAJXHs1mxlIeRXFoCw5G0ogPSdhPTPrbveQkrES4hzy
Dnw3TBcqXqD3TblvfScnvFM4sBgvcC0e88UhX2U6QChg6rnK4NhJtnCDVltVvGIM
EwlhG5RtT+Ak00Wtah3+f9mN9YU2de6sE2d2V92fcu/GgknO/tom2MFbSuJsEI2r
T+iK1e7MAf2rGx+yg25v92ZHq7M6S4heB9iD73ZjhVjjYPZi3rrI3h+1RYkhtREd
dWFuRBVF/poCdWUTtwh6xa91wBlRxmYF/zU9knuepFW4tpv2SgF/Nr/Fz/HK6Ydu
JvhbeUDfdjS0akF1Iev5uyJclvA/cy4s0xZ4/q6C1McGo0Lsw4wCLtOIq4nCYaH+
3oMwzUAuDjzsPvj7wjEepBluvkPTt0Dpv/766qxbT+3hTetaZQ1H2xTe51UwcoJL
psgYuVSGKgmJj7fy/7iLKe2HnURTefvjLz7VmEaeQKAvsxzcAVc=
=Y9+H
-END PGP SIGNATURE-



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

Bug#1073078: marked as done (puredata breaks pd-iemmatrix autopkgtest: it now times out)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 11:49:37 +
with message-id 
and subject line Bug#1073078: fixed in pd-iemmatrix 0.4.1-1
has caused the Debian Bug report #1073078,
regarding puredata breaks pd-iemmatrix autopkgtest: it now times out
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.)


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

Source: puredata, pd-iemmatrix
Control: found -1 puredata/0.55.0+ds-1
Control: found -1 pd-iemmatrix/0.4.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of puredata the autopkgtest of pd-iemmatrix fails 
in testing when that autopkgtest is run with the binary packages of 
puredata from unstable. What's worse, where the test normally passes 
within 10s of seconds to 2 minutes, it now times out after 2:47 hours. 
It passes when run with only packages from testing. In tabular form:


   passfail
puredata   from testing0.55.0+ds-1
pd-iemmatrix   from testing0.4.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Unfortunately 
there's isn't much to see.


Currently this regression is blocking the migration of puredata to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=puredata

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pd-iemmatrix/47558213/log.gz

 46s /usr/bin/pd
10043s autopkgtest [07:14:01]: ERROR: timed out on command "su -s 
/bin/bash debci -c set -e; exec 
/tmp/autopkgtest-lxc.scjcgjj4/downtmp/wrapper.sh 
--artifacts=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-artifacts 
--chdir=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src 
--env=DEB_BUILD_OPTIONS=parallel=64 --env=DEBIAN_FRONTEND=noninteractive 
--env=LANG=C.UTF-8 --unset-env=LANGUAGE --unset-env=LC_ADDRESS 
--unset-env=LC_ALL --unset-env=LC_COLLATE --unset-env=LC_CTYPE 
--unset-env=LC_IDENTIFICATION --unset-env=LC_MEASUREMENT 
--unset-env=LC_MESSAGES --unset-env=LC_MONETARY --unset-env=LC_NAME 
--unset-env=LC_NUMERIC --unset-env=LC_PAPER --unset-env=LC_TELEPHONE 
--unset-env=LC_TIME --script-pid-file=/tmp/autopkgtest_script_pid 
--source-profile 
--stderr=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-stderr 
--stdout=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-stdout 
--tmp=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/autopkgtest_tmp 
--make-executable=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src/debian/tests/run-suite-sysinstalled 
--
/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src/debian/tests/run-suite-sysinstalled" 
(kind: test)

10043s autopkgtest [07:14:01]: test run-suite-sysinstalled



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pd-iemmatrix
Source-Version: 0.4.1-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-iemmatrix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 08:52:51 +0200
Source: pd-iemmatrix
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073076 1073078
Changes:
 pd-iemmatrix (0.4.1-1) unstable; urgency=medium
 .
   * New upstream version 0.4.1
 (Closes: #1073076, #1073078)
   * Switch to dh-sequence-puredata
   * Update d/watch (GitLab likes breaking things

Bug#1073076: marked as done (pd-iemmatrix: autopkgtest regression on s390x: failing test doesn't stop)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 11:49:37 +
with message-id 
and subject line Bug#1073078: fixed in pd-iemmatrix 0.4.1-1
has caused the Debian Bug report #1073078,
regarding pd-iemmatrix: autopkgtest regression on s390x: failing test doesn't 
stop
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.)


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

Source: pd-iemmatrix
Version: 0.4.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it failed to fail 
nicely on s390x today, triggered by an upload of puredata. The s390x 
host that we use for ci.d.n was running out of disk space multiple times 
today and I debugged it down that the culprit is pd-iemmatrix.


When I manually start the test on testing with
"""
root@ci-worker-s390x-01:~# /usr/bin/autopkgtest --no-built-binaries 
--timeout=30600 --user debci --apt-upgrade 
--pin-packages=unstable=src:puredata '--add-apt-source=deb-src 
http://deb.debian.org/debian unstable main contrib non-free 
non-free-firmwaredeb http://deb.debian.org/debian unstable main contrib 
non-free non-free-firmware' pd-iemmatrix -- lxc --sudo --name elbrus 
autopkgtest-testing-s390x

"""
I see a file appearing in 
/tmp/autopkgtest-lxc.3gwldww1/downtmp/build.sYI/src/tests/ called 
runtests.log.20240612-1935.1678 which keeps on growing until I kill the 
test (currently at 27 GB), it ends with seemingly endless repeats of:

regression-test: 301 tests passed
regression-test: 0 tests failed
error: quit already called with exit code 0

I'll file a bug report with puredata shortly as a pure testing run is 
still fine.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pd-iemmatrix
Source-Version: 0.4.1-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-iemmatrix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 08:52:51 +0200
Source: pd-iemmatrix
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073076 1073078
Changes:
 pd-iemmatrix (0.4.1-1) unstable; urgency=medium
 .
   * New upstream version 0.4.1
 (Closes: #1073076, #1073078)
   * Switch to dh-sequence-puredata
   * Update d/watch (GitLab likes breaking things)
   * Bump standards version to 4.7.0
Checksums-Sha1:
 af77350916f9168b2fc9fd002a7b951783434d16 2216 pd-iemmatrix_0.4.1-1.dsc
 c40274042cf2da445e9f44f5fe3b6dcccf5f017c 204265 pd-iemmatrix_0.4.1.orig.tar.bz2
 f6ff5ace8794e88a6cd50c5ca701744e2c5baadc 8004 
pd-iemmatrix_0.4.1-1.debian.tar.xz
Checksums-Sha256:
 0300549d8fab8b9b33423a63e6cef8ecccd4e3a6219d2663f2d33cb5c359569b 2216 
pd-iemmatrix_0.4.1-1.dsc
 0426b3651f73210145929bbddd907f88ae48e6bc0f6b31af51712f0a068e1a4b 204265 
pd-iemmatrix_0.4.1.orig.tar.bz2
 13e2fc65a8d61a22a6bdef5703f465aab852a3f730770234415d1ee5c06668b5 8004 
pd-iemmatrix_0.4.1-1.debian.tar.xz
Files:
 cead494eaaaefeeab76a9e00ffb958a9 2216 sound optional pd-iemmatrix_0.4.1-1.dsc
 147d02830dd85abdc28e58f6c72c3fbf 204265 sound optional 
pd-iemmatrix_0.4.1.orig.tar.bz2
 de72b02b4e18e8d2c562b1da47a87083 8004 sound optional 
pd-iemmatrix_0.4.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZsKkoACgkQtlAZxH96
NvjahQ//ekhFhicoP1Bc2ZnaR1ezOuSlxZeeeoMBV8hk49gItPaweXO/C8yX260A
baRP14JUBvLRiZfZq16khjvwgOG1ljf8zuAK/7O3C4gQfSaNW9DrSbEGH+CCyrYi
8AAjQ7gUw4aCBIbb0rjjkAeMFqcAEtFB2SjL9RkKYlgFXygFaEuHbXCh25MY+p6f
QdplS/FYecYcGTUwDbW2u/itZDmSwFvZ+wGhsrbs8D/X7burZj+pzcRHBEi7X3Wq
ergXpjYaY5OO5ZzyvAsuC1c2d0YFXrOLZXPLATLXgz4l7eD8bG/2ipNCnBVQHJYJ
7CJon34jLRf3vpos0NeSQKqFNi1Fl78/Jq8vWaCeDkPhDTdanuMppLlvpv1CRwuR
4U9L6dbCzuH76ob

Bug#1073078: marked as done (puredata breaks pd-iemmatrix autopkgtest: it now times out)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 11:49:37 +
with message-id 
and subject line Bug#1073076: fixed in pd-iemmatrix 0.4.1-1
has caused the Debian Bug report #1073076,
regarding puredata breaks pd-iemmatrix autopkgtest: it now times out
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.)


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

Source: puredata, pd-iemmatrix
Control: found -1 puredata/0.55.0+ds-1
Control: found -1 pd-iemmatrix/0.4.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of puredata the autopkgtest of pd-iemmatrix fails 
in testing when that autopkgtest is run with the binary packages of 
puredata from unstable. What's worse, where the test normally passes 
within 10s of seconds to 2 minutes, it now times out after 2:47 hours. 
It passes when run with only packages from testing. In tabular form:


   passfail
puredata   from testing0.55.0+ds-1
pd-iemmatrix   from testing0.4.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Unfortunately 
there's isn't much to see.


Currently this regression is blocking the migration of puredata to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=puredata

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pd-iemmatrix/47558213/log.gz

 46s /usr/bin/pd
10043s autopkgtest [07:14:01]: ERROR: timed out on command "su -s 
/bin/bash debci -c set -e; exec 
/tmp/autopkgtest-lxc.scjcgjj4/downtmp/wrapper.sh 
--artifacts=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-artifacts 
--chdir=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src 
--env=DEB_BUILD_OPTIONS=parallel=64 --env=DEBIAN_FRONTEND=noninteractive 
--env=LANG=C.UTF-8 --unset-env=LANGUAGE --unset-env=LC_ADDRESS 
--unset-env=LC_ALL --unset-env=LC_COLLATE --unset-env=LC_CTYPE 
--unset-env=LC_IDENTIFICATION --unset-env=LC_MEASUREMENT 
--unset-env=LC_MESSAGES --unset-env=LC_MONETARY --unset-env=LC_NAME 
--unset-env=LC_NUMERIC --unset-env=LC_PAPER --unset-env=LC_TELEPHONE 
--unset-env=LC_TIME --script-pid-file=/tmp/autopkgtest_script_pid 
--source-profile 
--stderr=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-stderr 
--stdout=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/run-suite-sysinstalled-stdout 
--tmp=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/autopkgtest_tmp 
--make-executable=/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src/debian/tests/run-suite-sysinstalled 
--
/tmp/autopkgtest-lxc.scjcgjj4/downtmp/build.pM8/src/debian/tests/run-suite-sysinstalled" 
(kind: test)

10043s autopkgtest [07:14:01]: test run-suite-sysinstalled



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pd-iemmatrix
Source-Version: 0.4.1-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-iemmatrix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 08:52:51 +0200
Source: pd-iemmatrix
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073076 1073078
Changes:
 pd-iemmatrix (0.4.1-1) unstable; urgency=medium
 .
   * New upstream version 0.4.1
 (Closes: #1073076, #1073078)
   * Switch to dh-sequence-puredata
   * Update d/watch (GitLab likes breaking things

Bug#1073076: marked as done (pd-iemmatrix: autopkgtest regression on s390x: failing test doesn't stop)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 11:49:37 +
with message-id 
and subject line Bug#1073076: fixed in pd-iemmatrix 0.4.1-1
has caused the Debian Bug report #1073076,
regarding pd-iemmatrix: autopkgtest regression on s390x: failing test doesn't 
stop
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.)


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

Source: pd-iemmatrix
Version: 0.4.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it failed to fail 
nicely on s390x today, triggered by an upload of puredata. The s390x 
host that we use for ci.d.n was running out of disk space multiple times 
today and I debugged it down that the culprit is pd-iemmatrix.


When I manually start the test on testing with
"""
root@ci-worker-s390x-01:~# /usr/bin/autopkgtest --no-built-binaries 
--timeout=30600 --user debci --apt-upgrade 
--pin-packages=unstable=src:puredata '--add-apt-source=deb-src 
http://deb.debian.org/debian unstable main contrib non-free 
non-free-firmwaredeb http://deb.debian.org/debian unstable main contrib 
non-free non-free-firmware' pd-iemmatrix -- lxc --sudo --name elbrus 
autopkgtest-testing-s390x

"""
I see a file appearing in 
/tmp/autopkgtest-lxc.3gwldww1/downtmp/build.sYI/src/tests/ called 
runtests.log.20240612-1935.1678 which keeps on growing until I kill the 
test (currently at 27 GB), it ends with seemingly endless repeats of:

regression-test: 301 tests passed
regression-test: 0 tests failed
error: quit already called with exit code 0

I'll file a bug report with puredata shortly as a pure testing run is 
still fine.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pd-iemmatrix
Source-Version: 0.4.1-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-iemmatrix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Jun 2024 08:52:51 +0200
Source: pd-iemmatrix
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073076 1073078
Changes:
 pd-iemmatrix (0.4.1-1) unstable; urgency=medium
 .
   * New upstream version 0.4.1
 (Closes: #1073076, #1073078)
   * Switch to dh-sequence-puredata
   * Update d/watch (GitLab likes breaking things)
   * Bump standards version to 4.7.0
Checksums-Sha1:
 af77350916f9168b2fc9fd002a7b951783434d16 2216 pd-iemmatrix_0.4.1-1.dsc
 c40274042cf2da445e9f44f5fe3b6dcccf5f017c 204265 pd-iemmatrix_0.4.1.orig.tar.bz2
 f6ff5ace8794e88a6cd50c5ca701744e2c5baadc 8004 
pd-iemmatrix_0.4.1-1.debian.tar.xz
Checksums-Sha256:
 0300549d8fab8b9b33423a63e6cef8ecccd4e3a6219d2663f2d33cb5c359569b 2216 
pd-iemmatrix_0.4.1-1.dsc
 0426b3651f73210145929bbddd907f88ae48e6bc0f6b31af51712f0a068e1a4b 204265 
pd-iemmatrix_0.4.1.orig.tar.bz2
 13e2fc65a8d61a22a6bdef5703f465aab852a3f730770234415d1ee5c06668b5 8004 
pd-iemmatrix_0.4.1-1.debian.tar.xz
Files:
 cead494eaaaefeeab76a9e00ffb958a9 2216 sound optional pd-iemmatrix_0.4.1-1.dsc
 147d02830dd85abdc28e58f6c72c3fbf 204265 sound optional 
pd-iemmatrix_0.4.1.orig.tar.bz2
 de72b02b4e18e8d2c562b1da47a87083 8004 sound optional 
pd-iemmatrix_0.4.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZsKkoACgkQtlAZxH96
NvjahQ//ekhFhicoP1Bc2ZnaR1ezOuSlxZeeeoMBV8hk49gItPaweXO/C8yX260A
baRP14JUBvLRiZfZq16khjvwgOG1ljf8zuAK/7O3C4gQfSaNW9DrSbEGH+CCyrYi
8AAjQ7gUw4aCBIbb0rjjkAeMFqcAEtFB2SjL9RkKYlgFXygFaEuHbXCh25MY+p6f
QdplS/FYecYcGTUwDbW2u/itZDmSwFvZ+wGhsrbs8D/X7burZj+pzcRHBEi7X3Wq
ergXpjYaY5OO5ZzyvAsuC1c2d0YFXrOLZXPLATLXgz4l7eD8bG/2ipNCnBVQHJYJ
7CJon34jLRf3vpos0NeSQKqFNi1Fl78/Jq8vWaCeDkPhDTdanuMppLlvpv1CRwuR
4U9L6dbCzuH76ob

Processed: tagging 1073014

[Debian Bug Tracking System]

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

> tags 1073014 + help moreinfo unreproducible
Bug #1073014 [src:dhcpcd] dhcpcd: flaky autopkgtest: Obtaining network 
configuration for veth1 via dhcp... timed out
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 1073014

[Debian Bug Tracking System]

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

> tags 1073014 + help
Bug #1073014 [src:dhcpcd] dhcpcd: flaky autopkgtest: Obtaining network 
configuration for veth1 via dhcp... timed out
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1072971: kuserfeedback: FTBFS on s390x: OpenGLInfoSourceTest::testOpenGLInfoSource() '!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mesa 24.1.1-2
Bug #1072971 [src:kuserfeedback] kuserfeedback: FTBFS on s390x: 
OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE
Bug reassigned from package 'src:kuserfeedback' to 'mesa'.
No longer marked as found in versions kuserfeedback/1.3.0-3.
Ignoring request to alter fixed versions of bug #1072971 to the same values 
previously set
Bug #1072971 [mesa] kuserfeedback: FTBFS on s390x: 
OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE
There is no source info for the package 'mesa' at version '24.1.1-2' with 
architecture ''
Unable to make a source version for version '24.1.1-2'
Marked as found in versions 24.1.1-2.
> affects -1 kuserfeedback
Bug #1072971 [mesa] kuserfeedback: FTBFS on s390x: 
OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE
Added indication that 1072971 affects kuserfeedback
> retitle -1 mesa: fails to initialize OpenGL on s390x: Unexpected format 
> PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
Bug #1072971 [mesa] kuserfeedback: FTBFS on s390x: 
OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE
Changed Bug title to 'mesa: fails to initialize OpenGL on s390x: Unexpected 
format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb' from 
'kuserfeedback: FTBFS on s390x: OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE'.

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

Bug#1072971: kuserfeedback: FTBFS on s390x: OpenGLInfoSourceTest::testOpenGLInfoSource() '!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE

[Emilio Pozuelo Monfort]

Control: reassign -1 mesa 24.1.1-2
Control: affects -1 kuserfeedback
Control: retitle -1 mesa: fails to initialize OpenGL on s390x: Unexpected 
format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb

On 11/06/2024 09:06, Emilio Pozuelo Monfort wrote:

Source: kuserfeedback
Version: 1.3.0-3
Severity: serious

Hi,

During a rebuild for the Qt6 transition, your package failed to build on s390x:

 * Start testing of OpenGLInfoSourceTest *
 Config: Using QtTest library 5.15.13, Qt 5.15.13 (s390x-big_endian-lp64 
shared (dynamic) release build; by GCC 13.2.0), debian unknown
 PASS   : OpenGLInfoSourceTest::initTestCase()
 Mesa 24.1.1-2 implementation error: Unexpected format 
PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
 Please report at https://gitlab.freedesktop.org/mesa/mesa/-/issues
 QWARN  : OpenGLInfoSourceTest::testOpenGLInfoSource() Unrecognized OpenGL 
version
 QWARN  : OpenGLInfoSourceTest::testOpenGLInfoSource() Unrecognized OpenGL 
version
 Mesa 24.1.1-2 implementation error: Unexpected format 
PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
 Please report at https://gitlab.freedesktop.org/mesa/mesa/-/issues
 FAIL!  : OpenGLInfoSourceTest::testOpenGLInfoSource() 
'!m.value(QLatin1String("vendor")).toString().isEmpty()' returned FALSE. ()
Loc: [./autotests/openglinfosourcetest.cpp(36)]

Full build log at 
https://buildd.debian.org/status/fetch.php?pkg=kuserfeedback&arch=s390x&ver=1.3.0-3%2Bb3&stamp=1718075730&raw=0


Actually this looks like a regression in mesa in 24.1. A few rdeps are failing
their autopkgtests with the same PIPE_FORMAT_X8B8G8R8_SRGB error, e.g.:

https://ci.debian.net/packages/k/kodi/testing/s390x/47675600/
https://ci.debian.net/packages/o/openscad/testing/s390x/47689316/

Cheers,
Emilio

Bug#1067782: Uses deprecated tooling to build package

[Michael Hanke]

It is unclear why tqdm (and tqdm specifically) is downloaded. The build
log confirms that python3-tqdm (4.66.2-2) was installed as a
build-dependency.

That being said, the step that triggers the download is preceded with
the message


PYTHONPATH="bin:" python3 setup.py develop --install-dir bin
running develop
/usr/lib/python3/dist-packages/setuptools/command/develop.py:40: 
EasyInstallDeprecationWarning: easy_install command is deprecated.
!!



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

See https://github.com/pypa/setuptools/issues/917 for details.



!!
  easy_install.initialize_options(self)
/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!



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

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



!!

Possibly the problem is caused by a toolchain that should no longer be
used to begin with.

-- 
Michael Hanke
GPG: 4096R/C073D2287FFB9E9B
http://psychoinformatics.de

Bug#1070186: New upstream fixed problem

[Michael Hanke]

The current 1.0.3 release no longer depends on boto and has moved to
boto3.

-- 
Michael Hanke
GPG: 4096R/C073D2287FFB9E9B
http://psychoinformatics.de

Processed: bug 1073074 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1901899, tagging 1073074

[Debian Bug Tracking System]

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

> forwarded 1073074 https://bugzilla.mozilla.org/show_bug.cgi?id=1901899
Bug #1073074 [firefox] firefox: looses previous tabs
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1901899'.
> tags 1073074 + upstream
Bug #1073074 [firefox] firefox: looses previous tabs
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1073196: python3-docker: It does not work with the new version of python3-requests

[Salvo "LtWorf" Tomaselli]

Package: python3-docker
Version: 6.1.3-0.1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ltw...@debian.org

It is fixed upstream here: https://github.com/docker/docker-py/pull/3257/files


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

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

Versions of packages python3-docker depends on:
ii  python33.11.8-1
ii  python3-distutils  3.12.3-3.1
ii  python3-packaging  24.0-1
ii  python3-requests   2.32.3+dfsg-1
ii  python3-urllib32.0.7-2
ii  python3-websocket  1.7.0-1

python3-docker recommends no packages.

python3-docker suggests no packages.

-- no debconf information

Bug#1066548: marked as done (pd-iemnet: FTBFS: udpserver.c:666:5: error: implicit declaration of function ‘error’; did you mean ‘herror’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 10:34:19 +
with message-id 
and subject line Bug#1066548: fixed in pd-iemnet 0.3.0-6
has caused the Debian Bug report #1066548,
regarding pd-iemnet: FTBFS: udpserver.c:666:5: error: implicit declaration of 
function ‘error’; did you mean ‘herror’? [-Werror=implicit-function-declaration]
to be marked as done.

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

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


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

Hi,

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

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

Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DVERSION='"0.3.0"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o udpserver.pd_linux.o -c udpserver.c
>  info: making udpclient.pd_linux.o in lib iemnet
> udpserver.c: In function ‘udpserver_connectpoll’:
> udpserver.c:666:5: error: implicit declaration of function ‘error’; did you 
> mean ‘herror’? [-Werror=implicit-function-declaration]
>   666 | error("[%s] accept failed", objName);
>   | ^
>   | herror
> iemnet.c: In function ‘iemnet__socket2addressout’:
> iemnet.c:97:5: error: implicit declaration of function ‘error’; did you mean 
> ‘herror’? [-Werror=implicit-function-declaration]
>97 | error("unable to get address from socket:%d", sockfd);
>   | ^
>   | herror
> iemnet.c: In function ‘iemnet__register’:
> iemnet.c:226:27: warning: macro "__DATE__" might prevent reproducible builds 
> [-Wdate-time]
>   226 |   post("compiled "BUILD_DATE"");
>   |   ^~
> iemnet.c:214:27: warning: macro "__TIME__" might prevent reproducible builds 
> [-Wdate-time]
>   214 | # define BUILD_DATE "on " __DATE__ " at " __TIME__
>   |   ^~~~
> iemnet.c:226:27: note: in expansion of macro ‘BUILD_DATE’
>   226 |   post("compiled "BUILD_DATE"");
>   |   ^~
> iemnet_sender.c: In function ‘iemnet__sender_getsockopt’:
> iemnet_sender.c:279:5: error: implicit declaration of function ‘error’; did 
> you mean ‘herror’? [-Werror=implicit-function-declaration]
>   279 | error("iemnet::sender: getsockopt returned %d",
>   | ^
>   | herror
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DVERSION='"0.3.0"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o udpclient.pd_linux.o -c udpclient.c
>  info: making udpreceive.pd_linux.o in lib iemnet
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DVERSION='"0.3.0"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o udpreceive.pd_linux.o -c 
> udpreceive.c
>  info: making udpsend.pd_linux.o in lib iemnet
> cc1: some warnings being treated as errors
> cc -DPD -I "/usr/include/pd"  -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -DVERSION='"0.3.0"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o udpsend.pd_linux.o -c udpsend.c
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> iemnet_sender.pd_linux.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/pd-iemnet_0.3.0-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-202403

Bug#1060775: marked as done (tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 10:35:03 +
with message-id 
and subject line Bug#1060775: fixed in tmuxp 1.47.0-2
has caused the Debian Bug report #1060775,
regarding tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError
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.)


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

Source: tmuxp
Version: 1.31.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. I'm seeing a pattern that it happens more often 
on our amd64 host ci-worker13 and often on our s390x which are rather 
powerful hosts. The test fails in different locations, but as far as I 
saw always on a line that asserts capture_pane (see example below). 
Could it be that the code (either the real code or the test code) should 
wait a bit until the "pane" has been substantiated? Or maybe that 
comment earlier is of interest: Give slow shells some time to settle as 
otherwise tests might fail.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

From
https://ci.debian.net/packages/t/tmuxp/testing/s390x/41364351/

 59s @pytest.mark.skipif(
 59s has_lt_version("3.0"),
 59s reason="needs -e flag for new-window and split-window 
introduced in tmux 3.0",

 59s )
 59s def test_environment_variables(session: Session) -> None:
 59s workspace = ConfigReader._from_file(
 59s 
test_utils.get_workspace_file("workspace/builder/environment_vars.yaml")

 59s )
 59s workspace = loader.expand(workspace)
 59s
 59s builder = WorkspaceBuilder(session_config=workspace, 
server=session.server)

 59s builder.build(session)
 59s # Give slow shells some time to settle as otherwise tests 
might fail.

 59s time.sleep(0.3)
 59s
 59s assert session.getenv("FOO") == "SESSION"
 59s assert session.getenv("PATH") == "/tmp"
 59s
 59s no_overrides_win = session.windows[0]
 59s pane = no_overrides_win.panes[0]
 59s pane.send_keys("echo $FOO")
 59s assert pane.capture_pane()[1] == "SESSION"
 59s
 59s window_overrides_win = session.windows[1]
 59s pane = window_overrides_win.panes[0]
 59s pane.send_keys("echo $FOO")
 59s assert pane.capture_pane()[1] == "WINDOW"
 59s
 59s pane_overrides_win = session.windows[2]
 59s pane = pane_overrides_win.panes[0]
 59s pane.send_keys("echo $FOO")
 59s assert pane.capture_pane()[1] == "PANE"
 59s
 59s both_overrides_win = session.windows[3]
 59s pane = both_overrides_win.panes[0]
 59s pane.send_keys("echo $FOO")
 59s >   assert pane.capture_pane()[1] == "WINDOW"
 59s E   IndexError: list index out of range
 59s


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tmuxp
Source-Version: 1.47.0-2
Done: Sebastien Delafond 

We believe that the bug you reported is fixed in the latest version of
tmuxp, 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.
Sebastien Delafond  (supplier of updated tmuxp 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, 14 Jun 2024 11:28:48 +0200
Source: tmuxp
Architecture: source
Version: 1.47.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Closes: 1060775
Changes:
 tmuxp (1.47.0-2) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * debian/tests: skip test_environment_variables (Closes: #1060775)
Checksums-Sha1:
 d04f634d0c75d

Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

[Martin Dosch]

Package: dput
Version: 1.2
Followup-For: Bug #1072857

Dear Maintainer,

I am also affected by this bug. I have not added any dput config and 
therefore nowhere specified a delay so it must be a faulty default 
config:

`find ~ -name \*dput.cf` didn't find anything.

I worked around by specifying `--delayed 0` on the command line.

Best regards,
Martin

-- Package-specific info:

-- /etc/dput.cf --
# Example dput.cf that defines the host that can be used
# with dput for uploading.

[DEFAULT]
login   = *
method  = ftp
hash= md5
allow_unsigned_uploads  = 0
allow_dcut  = 0
run_lintian = 0
run_dinstall= 0
check_version   = 0
scp_compress= 0
post_upload_command =
pre_upload_command  =
passive_ftp = 1
default_host_main   =
allowed_distributions   = (?!UNRELEASED)

[ftp-master]
fqdn= ftp.upload.debian.org
incoming= /pub/UploadQueue/
login   = anonymous
allow_dcut  = 1
method  = ftp
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# https://lists.debian.org/debian-project/2009/05/msg00036.html
[ftp-eu]
fqdn= ftp.eu.upload.debian.org
method  = ftp
incoming= /pub/UploadQueue/
login   = anonymous
allow_dcut  = 1
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# https://lists.debian.org/debian-devel-announce/2008/09/msg7.html
[ssh-upload]
login   = *
# login = another_username
fqdn= ssh.upload.debian.org
method  = scp
incoming= /srv/upload.debian.org/UploadQueue/
allow_dcut  = 1
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# And if you want to override one of the defaults, add it here.
# For example, comment out the next line
# post_upload_command   = /path/to/some/script
# pre_upload_command= /path/to/some/script

[security-master]
fqdn= ftp.security.upload.debian.org
method  = ftp
incoming= /pub/SecurityUploadQueue
login   = anonymous
allow_dcut  = 1
# This has been added at the request of the security team.
# Please be sure to know what you are doing before taking it out.
pre_upload_command  = /usr/share/dput/helper/security-warning

[security-master-unembargoed]
fqdn= ftp.security.upload.debian.org
method  = ftp
incoming= /pub/OpenSecurityUploadQueue
login   = anonymous
allow_dcut  = 1
# This has been added at the request of the security team.
# Please be sure to know what you are doing before taking it out.
pre_upload_command  = /usr/share/dput/helper/security-warning

[ubuntu]
fqdn= upload.ubuntu.com
method  = ftp
incoming= /
login   = anonymous

[ppa]
fqdn= ppa.launchpad.net
method  = ftp
# replace  with your Launchpad ID
incoming= ~/ubuntu
login   = anonymous

[mentors]
method  = ftp
fqdn= mentors.debian.net
incoming= /pub/UploadQueue
login   = anonymous

[local]
method  = local
incoming= ~/public_html/debian/mini-dinstall/incoming
run_dinstall= 0
post_upload_command = /usr/bin/mini-dinstall --batch


# Local variables:
# coding: utf-8
# mode: conf
# End:
# vim: fileencoding=utf-8 filetype=config :

-- /home/martin/.config/dput/dput.cf --

-- /home/martin/.dput.cf --

[DEFAULT]
login = *
method = ftp
hash = md5
allow_unsigned_uploads = 0
allow_dcut = 0
distributions = 
allowed_distributions = (?!UNRELEASED)
run_lintian = 0
run_dinstall = 0
check_version = 0
scp_compress = 0
default_host_main = 
post_upload_command = 
pre_upload_command = 
ssh_config_options = 
passive_ftp = 1
progress_indicator = 0
delayed = 

[ftp-master]
fqdn = ftp.upload.debian.org
incoming = /pub/UploadQueue/
login = anonymous
allow_dcut = 1
method = ftp
allowed_distributions = (?!UNRELEASED|.*-security)

[ftp-eu]
fqdn = ftp.eu.upload.debian.org
method = ftp
incoming = /pub/UploadQueue/
login = anonymous
allow_dcut = 1
allowed_distributions = (?!UNRELEASED|.*-security)

[ssh-upload]
login = *
fqdn = ssh.upload.debian.org
method = scp
incoming = /srv/upload.debian.org/UploadQueue/
allow_dcut = 1
allowed_di

Bug#1073063: ausweisapp should depend on qml6-module-qtquick-effects

[John Paul Adrian Glaubitz]

On Fri, 2024-06-14 at 10:33 +0200, Sune Stolborg Vuorela wrote:
> On Friday, June 14, 2024 10:25:59 AM CEST John Paul Adrian Glaubitz wrote:
> > I'm not denying that. However, a package named "qml6-module-qtquick-effects"
> > doesn't sound like an interpreter to me.
> > 
> > Thus, I don't really see how I am supposed to know as a maintainer what
> > packages add Depends except for trial and error. Why not have one canonical
> > "qt-interpretor" package or similar that applications can depend on?
> 
> This is a module for a interpreted language. It is not much different than a 
> python package might need a hardcoded dependency on python-foo if it uses 
> that. or a perl package might need a hardcoded dependency on libperl-foo-bar-
> baz if it uses the Foo::Bar::Baz perl module for important functionality.
> 
> all qml*-module packages are qml (interpreted language) extensions.
> 
> And yes. trial and error - or reading the sources - is for many interpreted 
> languages the only way of figuring it out.

Ugh, that's truly a step backwards and way to add more burden to maintainers.

I guess we'll be seeing plenty of such bug reports in the future when extensions
get moved around or new ones get added.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1073114: unburden-home-dir: stop build-depending on pcre3

[Axel Beckert]

Control: tag -1 + patch pending

Hi again

Axel Beckert wrote:
> The sole reason I use it over grep is that it supports multiline
> matches. It though seems that grep might be able to do that — albeit
> non-obviously — via "grep -Pzov", too.

Nope, even much simpler cases fail to remove just a substring from a
single line:

~ → printf 'foo\ngnarz\nbar\n' | fgrep -voz nar
~ → printf 'foo\ngnarz\nbar\n' | fgrep -ov nar

etc.

> Otherwise, I'll probably just use the original with "perl -E". It's
> just the build system trying to remove any unwanted crap (multiline
>  tags including their contents) from the generated HTML
> documentation.

The following change works and produces byte for byte the identical
result as "pcregrep -Mv", it's just a bit longer:

-   pcregrep -Mv 
']*>[^<]*|<(form|input).*?>|' | \
+   perl -E 'local $$/; my $$input=<>; $$input =~ 
s:]*>[^<]*\n*|<(form|input).*?>|\n*::gsm; print 
$$input;' | \

("$$" instead of "$" is needed even inside single quotes as this is
inside a Makefile where $ is a special character already.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#1073114: unburden-home-dir: stop build-depending on pcre3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch pending
Bug #1073114 [src:unburden-home-dir] unburden-home-dir: stop build-depending on 
pcre3
Added tag(s) patch and pending.

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

Bug#1072792: marked as done (nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 09:36:00 +
with message-id 
and subject line Bug#1072792: fixed in nvidia-graphics-drivers 535.183.01-1
has caused the Debian Bug report #1072792,
regarding nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, 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.)


-- 
1072792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072792
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
Source-Version: 535.183.01-1
Done: Andreas Beckmann 

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

Bug#1073040: dput: Fails when processing ssh_config_options value: AttributeError: 'list' object has no attribute 'split'

[Christoph Berg]

Re: Ben Finney
> At https://salsa.debian.org/debian/dput/-/merge_requests/15> is a
> merge request proposing to fix this bug.
> 
> Can you try the resulting Dput package, and confirm whether it corrects the
> behaviour in your case?

Hi,

I don't think I have any ssh options set - it was already failing on
the default case. I'd say just upload and I'll report back if it's
still failing.

Thanks!

Christoph

Processed: Re: Bug#1073114: unburden-home-dir: stop build-depending on pcre3

[Debian Bug Tracking System]

Processing control commands:

> tag -1  + confirmed
Bug #1073114 [src:unburden-home-dir] unburden-home-dir: stop build-depending on 
pcre3
Added tag(s) confirmed.

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

Bug#1073114: unburden-home-dir: stop build-depending on pcre3

[Axel Beckert]

Control: tag -1  + confirmed

Hi Chris,

Chris Hofstaedtler wrote:
> we want to get rid of pcre3 in trixie. As such unburden-home-dir's
> Build-Depends on pcregrep dependency will become unsatisfiable.

Thanks for the bug report! So pcregrep hasn't been ported (by
PCRE upstream) to libpcre2 either? *sigh*

The sole reason I use it over grep is that it supports multiline
matches. It though seems that grep might be able to do that — albeit
non-obviously — via "grep -Pzov", too.

Otherwise, I'll probably just use the original with "perl -E". It's
just the build system trying to remove any unwanted crap (multiline

Processed: Bug#1066548 marked as pending in pd-iemnet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066548 [src:pd-iemnet] pd-iemnet: FTBFS: udpserver.c:666:5: error: 
implicit declaration of function ‘error’; did you mean ‘herror’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066548: marked as pending in pd-iemnet

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-iemnet/-/commit/4a651ed3e7e7b60bd8b2094878988541399ed07a


Add patch to fix FTBFS du to changed API

Closes: #1066548


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066548

Processed: severity of 1065849 is serious

[Debian Bug Tracking System]

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

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

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

Bug#1073188: dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard

[Emanuele Rocca]

Source: dxvk
Version: 2.3.1-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: pac-bti

dxvk fails to build from source on arm64 due to the aarch64-specific
compiler flag -mbranch-protection=standard leaking into CFLAGS used by
x86_64-w64-mingw32-gcc:

 meson.build:1:0: ERROR: Unable to detect linker for compiler 
`x86_64-w64-mingw32-gcc -Wl,--version -flto -Wl,--build-id -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -mbranch-protection=standard -Wdate-time 
-D_FORTIFY_SOURCE=2`
 stdout: 
 stderr: x86_64-w64-mingw32-gcc: error: unrecognized command-line option 
‘-mbranch-protection=standard’

Bug#1073063: ausweisapp should depend on qml6-module-qtquick-effects

[Sune Stolborg Vuorela]

On Friday, June 14, 2024 10:25:59 AM CEST John Paul Adrian Glaubitz wrote:
> I'm not denying that. However, a package named "qml6-module-qtquick-effects"
> doesn't sound like an interpreter to me.
> 
> Thus, I don't really see how I am supposed to know as a maintainer what
> packages add Depends except for trial and error. Why not have one canonical
> "qt-interpretor" package or similar that applications can depend on?

This is a module for a interpreted language. It is not much different than a 
python package might need a hardcoded dependency on python-foo if it uses 
that. or a perl package might need a hardcoded dependency on libperl-foo-bar-
baz if it uses the Foo::Bar::Baz perl module for important functionality.

all qml*-module packages are qml (interpreted language) extensions.

And yes. trial and error - or reading the sources - is for many interpreted 
languages the only way of figuring it out.

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank

Bug#1073063: ausweisapp should depend on qml6-module-qtquick-effects

[John Paul Adrian Glaubitz]

On Fri, 2024-06-14 at 09:39 +0200, Sune Stolborg Vuorela wrote:
> Control: severity -1 serious
> 
> Missing dependencies are RC
> 
> > This is a common problem with Qt6 and has been reported for a different
> > dependency before, see [1]. 
> 
> It is normal for interpreted languages to have their dependencies managed 
> manually. This is just another version of that.

I'm not denying that. However, a package named "qml6-module-qtquick-effects"
doesn't sound like an interpreter to me.

Thus, I don't really see how I am supposed to know as a maintainer what packages
add Depends except for trial and error. Why not have one canonical 
"qt-interpretor"
package or similar that applications can depend on?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: Re: Bug#1073063: ausweisapp should depend on qml6-module-qtquick-effects

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1073063 [ausweisapp] ausweisapp should depend on 
qml6-module-qtquick-effects
Severity set to 'serious' from 'normal'

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

Processed: reassign 1073144 to plasma-workspace, notfound 1073038 in 0.70-1, found 1073038 in 0.72-1 ...

[Debian Bug Tracking System]

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

> reassign 1073144 plasma-workspace 4:5.27.11.1-1
Bug #1073144 [plamsa-workspace] plasma-workspace: Please drop 
/usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf
Warning: Unknown package 'plamsa-workspace'
Bug reassigned from package 'plamsa-workspace' to 'plasma-workspace'.
No longer marked as found in versions 4:5.27.11.1-1.
Ignoring request to alter fixed versions of bug #1073144 to the same values 
previously set
Bug #1073144 [plasma-workspace] plasma-workspace: Please drop 
/usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf
Marked as found in versions plasma-workspace/4:5.27.11.1-1.
> notfound 1073038 0.70-1
Bug #1073038 [po4a] po4a: Fails due to undefined subroutine 
Locale::Po4a::Pod::dgettext
There is no source info for the package 'po4a' at version '0.70-1' with 
architecture ''
Unable to make a source version for version '0.70-1'
No longer marked as found in versions 0.70-1.
> found 1073038 0.72-1
Bug #1073038 [po4a] po4a: Fails due to undefined subroutine 
Locale::Po4a::Pod::dgettext
Marked as found in versions po4a/0.72-1.
> fixed 1039898 11.74-1
Bug #1039898 [libapache2-mod-qos] mod-qos can not be enabled correctly for 
apache2 in Debian 12
Marked as fixed in versions libapache2-mod-qos/11.74-1.
> thanks
Stopping processing here.

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

Bug#1072765: marked as done (python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js is missing)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2024 10:53:01 +0300
with message-id 
and subject line Re: Bug#1072765: python-skbio: FTBFS: dh_sphinxdoc: error: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js
 is missing
has caused the Debian Bug report #1072765,
regarding python-skbio: FTBFS: dh_sphinxdoc: error: 
debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js
 is missing
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.)


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

Package: src:python-skbio
Version: 0.5.9-4
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 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mv simde-sse2.h simde-sse2.h.orig
rm -f skbio/alignment/_ssw_wrapper.c skbio/diversity/_phylogenetic.c 
skbio/stats/__subsample.c skbio/metadata/_intersection.c
dh_auto_configure
I: pybuild base:311: python3.12 setup.py config
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 
'language_level' not set, using 2 for now (Py2). This will change in a later release! File: 
/<>/skbio/alignment/_ssw_wrapper.pyx
  tree = Parsing.p_module(s, pxd, full_module_name)
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 
'language_level' not set, using 2 for now (Py2). This will change in a later release! File: 
/<>/skbio/diversity/_phylogenetic.pyx
  tree = Parsing.p_module(s, pxd, full_module_name)

[... snipped ...]

copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/blast6_default_single_line
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/phylip_invalid_seq_too_short
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/legacy9_and_blast7_default
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/error_long_qual.fastq
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/ordination_exp_Ordination_CCA_site
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/ordination_exp_Ordination_RDA_species
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/fastq_whitespace_only_lines
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/phylip_invalid_too_many_seqs
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/fasta_multi_seq 
-> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/phylip_invalid_empty_line_before_header
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/fasta_single_bio_seq_non_defaults
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/legacy9_invalid_too_many_columns
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/stockholm_whitespace_only_lines
 -> 
/<>/debian/python3-skbio/usr/lib/python3.11/dist-packages/skbio/io/format/tests/data
copying 
/<>/.pybuild/cpython3_3.11_skbio/build/skbio/io/format/tests/data/stockholm_no_data
 -> 
/<>/debian/python3-skbio/usr/lib/python3.1

Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'

[Mark Robinson]

On 14/06/24 19:02, IOhannes m zmölnig (Debian/GNU) wrote:

On 14/06/2024 05:59, Mark Robinson wrote:

Package: gramps
Version: 5.2.2+dfsg-0.1
Severity: grave
Justification: causes non-serious data loss


bummer.


New version of gramps in Trixie upgrade.

Insisted on upgrading database advising to create backup without means.


the latter would be an upstream bug.


Most likely, but a Debian upgrade which takes the system into a state 
which requires a database upgrade while removing the ability to make a 
backup may justify a Debian News entry so users can back out of the 
software upgrade and perform the backup.



Upgraded and loaded database.

Spat error, lost new record.


could you get into detail with the last bit?
- when was the new record created?
- how was it lost?


On completing the database migration I created a new person, added birth 
and death information including a new death location and notes, and 
clicked OK.


This resulted in the python error referred to in the headline which left 
the new person with the OK button greyed out and no way to save it. The 
record was lost.


This information appears to have been lost in submitting the report:

User Information: 
===


Just after version upgrade and DB conversion.
Being unable to backup a database after upgrading Gramps and before converting 
the database is highly problematic.




Error Details: 
===


11723: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree 
works, you can delete the zip file at 
/home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-04.zip
15060: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree 
works, you can delete the zip file at 
/home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-08.zip
15068: WARNING: updatecallback.py: line 94: UpdateCallback with total == 0 
created
3905173: ERROR: grampsapp.py: line 188: Unhandled exception
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gramps/gui/editors/editperson.py", line 
984, in save
self.db.commit_person(self.obj, trans)
  File "/usr/lib/python3/dist-packages/gramps/gen/db/generic.py", line 1911, in 
commit_person
self.add_to_surname_list(person, trans.batch)
  File "/usr/lib/python3/dist-packages/gramps/gen/db/generic.py", line 2450, in 
add_to_surname_list
i = bisect.bisect(self.surname_list, name)
^^
TypeError: '<' not supported between instances of 'str' and 'NoneType'


System Information: 
===


Gramps version: 5.2.2 
Python version: 3.11.9 
BSDDB version: 6.2.9 (5, 3, 28) 
sqlite version: 3.46.0 (2.6.0) 
LANG: en_GB.UTF-8

OS: Linux
Distribution: 6.7.12-amd64

GTK version: 3.24.42
gobject version: 3.48.2
cairo version  : (1, 26, 0)




Ta,
Mark

Processed: severity of 1071992 is serious

[Debian Bug Tracking System]

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

> severity 1071992 serious
Bug #1071992 [src:sqlmodel] sqlmodel: please make this package compatible with 
SQL Alchemy 2.x
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'

[Debian/GNU]

On 14/06/2024 05:59, Mark Robinson wrote:

Package: gramps
Version: 5.2.2+dfsg-0.1
Severity: grave
Justification: causes non-serious data loss


bummer.



Dear Maintainer,

New version of gramps in Trixie upgrade.

Insisted on upgrading database advising to create backup without means.



the latter would be an upstream bug.




Upgraded and loaded database.

Spat error, lost new record.



could you get into detail with the last bit?
- when was the new record created?
- how was it lost?


i would expect that either the db migration fails (in which case records 
might get lost, but regardless of being "new" or not).
or the db migration succeeds, and then everything should work™ (if it 
doesn't then it should also not work with a completely new db - and 
gramps would be seriously broken)


gmdsar
IOhannes