Bug#1050683: pep517: Should not be released with Trixie

[Scott Kitterman]

Source: pep517
Severity: serious
Justification: Maintainer opinion

This package has been replace by python-pyproject-hooks and should not
be in Trixie.

Scott K

Bug#1043123: marked as done (llvm-toolchain-13: do not release with trixie)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 04:17:02 +
with message-id 
and subject line Bug#1017679: Removed package(s) from unstable
has caused the Debian Bug report #1043123,
regarding llvm-toolchain-13: do not release with trixie
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.)


-- 
1043123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-13
Version: 1:13.0.1-13
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Let's reduce the number of llvm-toolchains in trixie.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1:13.0.1-13+rm

Dear submitter,

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

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

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

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

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

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

Bug#1036611: marked as done (python3-lldb-13: broken symlinks: /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13*.so.1 -> ../../../../..//libLLVM-13.0.1.so.1)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2023 04:17:02 +
with message-id 
and subject line Bug#1017679: Removed package(s) from unstable
has caused the Debian Bug report #1036611,
regarding python3-lldb-13: broken symlinks: 
/usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13*.so.1 -> 
../../../../..//libLLVM-13.0.1.so.1
to be marked as done.

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

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


-- 
1036611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-lldb-13
Version: 1:13.0.1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
broken symlinks:

0m38.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.0.1.so.1 -> 
../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13)
  /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.so.1 -> 
../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13)

The correct target would be /usr/lib//libLLVM-13.so.1


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 1:13.0.1-13+rm

Dear submitter,

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

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

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

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

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

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

Processed: tagging 1028592

[Debian Bug Tracking System]

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

> tags 1028592 + ftbfs
Bug #1028592 [src:tagcoll2,src:libwibble] tagcoll2 2.0.14-2 fails to build on 
sid
Ignoring request to alter tags of bug #1028592 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#1050680: yubikey-luks: Depends on removed package cryptsetup-run

[Guilhem Moulin]

On Mon, 28 Aug 2023 at 01:56:04 +0200, Guilhem Moulin wrote:
> cryptsetup-run has been a transitional package since the buster release,
> and has now been removed following #1038285.  Looks like I failed to
> properly check reverse depends; yubikey-luks should replace ‘Depends:
> cryptsetup-run’ with ‘Depends: cryptsetup’.

Uploaded the attached debdiff to DELAYED/7.

-- 
Guilhem.
diffstat for yubikey-luks-0.5.1+29.g5df2b95 yubikey-luks-0.5.1+29.g5df2b95

 changelog |8 
 control   |2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -Nru yubikey-luks-0.5.1+29.g5df2b95/debian/changelog 
yubikey-luks-0.5.1+29.g5df2b95/debian/changelog
--- yubikey-luks-0.5.1+29.g5df2b95/debian/changelog 2022-10-15 
12:58:53.0 +0200
+++ yubikey-luks-0.5.1+29.g5df2b95/debian/changelog 2023-08-28 
01:59:49.0 +0200
@@ -1,3 +1,11 @@
+yubikey-luks (0.5.1+29.g5df2b95-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace ‘Depends: cryptsetup-run’ with ‘Depends: cryptsetup’ as
+src:cryptsetup no longer ships the former (Closes: #1050680)
+
+ -- Guilhem Moulin   Mon, 28 Aug 2023 01:59:49 +0200
+
 yubikey-luks (0.5.1+29.g5df2b95-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru yubikey-luks-0.5.1+29.g5df2b95/debian/control 
yubikey-luks-0.5.1+29.g5df2b95/debian/control
--- yubikey-luks-0.5.1+29.g5df2b95/debian/control   2021-01-02 
17:38:35.0 +0100
+++ yubikey-luks-0.5.1+29.g5df2b95/debian/control   2023-08-28 
01:59:43.0 +0200
@@ -13,7 +13,7 @@
 
 Package: yubikey-luks
 Architecture: all
-Depends: cryptsetup-run, initramfs-tools, yubikey-personalization (>= 1.5), 
${misc:Depends}
+Depends: cryptsetup, initramfs-tools, yubikey-personalization (>= 1.5), 
${misc:Depends}
 Recommends: cryptsetup-initramfs, expect
 Description: YubiKey two factor authentication for LUKS disks
  With this extension to the initramfs-tools, you can unlock a LUKS encrypted


signature.asc
Description: PGP signature

Bug#1050680: yubikey-luks: Depends on removed package cryptsetup-run

[Guilhem Moulin]

Source: yubikey-luks
Version: 0.5.1+29.g5df2b95-6.1
Severity: serious

Hi,

cryptsetup-run has been a transitional package since the buster release,
and has now been removed following #1038285.  Looks like I failed to
properly check reverse depends; yubikey-luks should replace ‘Depends:
cryptsetup-run’ with ‘Depends: cryptsetup’.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1050516: marked as done (checkit-tiff: FTBFS on big-endian platforms)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2023 22:19:17 +
with message-id 
and subject line Bug#1050516: fixed in checkit-tiff 1.4.4-1
has caused the Debian Bug report #1050516,
regarding checkit-tiff: FTBFS on big-endian platforms
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.)


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

Source: checkit-tiff
Severity: serious
X-Debbugs-Cc: a...@andreas-romeyke.de, oltma...@zib.de

The new checkit-tiff upstream version 1.4.3 does not build on big-endian 
platforms. Note: it was updated from 0.4.2, so the issue is not 
necessarily only in 1.4.3. You can get logs at 
https://buildd.debian.org/status/package.php?p=checkit-tiff


The issue triggers multiple times on running the test suite and ends up:
"(HE)TIFF Header error, not a MAGIC BYTE for TIFF: 0x2a00"
--- End Message ---
--- Begin Message ---
Source: checkit-tiff
Source-Version: 1.4.4-1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated checkit-tiff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Aug 2023 23:57:43 +0200
Source: checkit-tiff
Architecture: source
Version: 1.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Bastian Germann 
Closes: 1050516
Changes:
 checkit-tiff (1.4.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.4.4 (Closes: #1050516).
Checksums-Sha1:
 dbe203af4d56f94a453f987ebfd7636f6c7643a9 1985 checkit-tiff_1.4.4-1.dsc
 030118d90ec3f6fc7f688028ef3339d031ae6dd0 1252072 checkit-tiff_1.4.4.orig.tar.xz
 7bff67a54da2f419e73316b185e2a556b11d1d6c 3920 
checkit-tiff_1.4.4-1.debian.tar.xz
 5aa3a50e5188f2566c3e644e3f129e6713d00f52 7027 
checkit-tiff_1.4.4-1_source.buildinfo
Checksums-Sha256:
 2bd4ca1f28110718f5f7d588d5040c2fb4f2decf0681560f9d7003f72b4f2b8b 1985 
checkit-tiff_1.4.4-1.dsc
 9503615a050366353d82fc3b15f7a09517fe04d9a969a31c7cd14dfbc9135a63 1252072 
checkit-tiff_1.4.4.orig.tar.xz
 dec70358f5bd0a286d0f04d684e928eee6a9e96d3d46cd93d4c327525273b21f 3920 
checkit-tiff_1.4.4-1.debian.tar.xz
 8a6338f391f5cc8a04cc3384fbe842477ca556894839afba6b8fd8ce7b8709f0 7027 
checkit-tiff_1.4.4-1_source.buildinfo
Files:
 e7723f8243b9e2f1af930624df656091 1985 science optional checkit-tiff_1.4.4-1.dsc
 c0e4af6ac9470938800d072736fd0e93 1252072 science optional 
checkit-tiff_1.4.4.orig.tar.xz
 693a5ac0744f607fd0d3d6c8ef1b8252 3920 science optional 
checkit-tiff_1.4.4-1.debian.tar.xz
 9842ed129ab9560ca71fcb23c7ef29b9 7027 science optional 
checkit-tiff_1.4.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTrx/cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFC+nC/4usDP7Ez4O3f+l6iMUYgcgpN0mnSf5kCkr
3npf0RuCKlBaojg+6RttOwH5hlf6+ZsNKpN3UTm2Z1xVaikpOShPY24w6/XVtyz6
3B+pGJtlyVq3XIXzEspzOGYhdU+q1YwsAOkViliMmbXbGU7olSlZZXgnLR2w0pgE
WkEbALHV8FUloLZg4o+zx0W4wORAtQm2J7V0tCREsZv7nISK9wkbY6nNafhdbKPP
H5pL7lSFn75uamji76A2mAilEfj+KMPu+ShOrWA/UTmE2ZvNO3HIH2KINduCPSlh
8lVDVC7TqYmLPbT88HujrVsUzVlpNgkO7oAr4GqbSs7PjbpYw2YCL1h8zZV/6RQn
g2RLFHtnKRTK7VSAIlceYyJ66fQ4TZAH+FiRm/6KNaGCTEppGtw9iMMEyFLsTSz3
dH5CB/0fwdp5pdXi0y6JVAvLJSJZlOm0B+ymRqAQhnw9BEpB5/b3Sem/g2AzOJv2
GgZ9hbTM+AII+GT4ARdIYHpP3+xemLk=
=mQ7v
-END PGP SIGNATURE End Message ---

Bug#1040802: xkb-data: Breaks altgr in Norwegian layout

[Gunnar Hjalmarsson]

Control: severity -1 normal
Control: tags -1 + moreinfo

Thanks for your report!

Tollef Fog Heen wrote:

With commit 0fb34101788d84e9a1d98b3730cc7b9295e0f19b in
xkeyboard-config, `group(alts_toggle)` changed behaviour in a way
such that the right alt no longer generates altgr.


Apparently the purpose of the change was to make the "Both Alts" 
shortcut work again, after a long period when it didn't work.


https://salsa.debian.org/xorg-team/data/xkeyboard-config/-/commit/0fb34101

And in a working state, I'm not surprised to hear that "Both Alts" 
conflicts with the use of Right Alt for accessing 3rd and 4th level symbols.


I can't help asking why you set the "group(alts_toggle)" option at all. 
You don't seem to use any other keyboard layout but Norwegian anyway. So 
even before you have answered, my advice would be to just drop that 
option wherever you set it and move on. ;)


In any case the issue is not severity "serious", especially not in a 
Debian distro context.


--
Regards,
Gunnar Hjalmarsson

Processed: Re: Bug#1040802: xkb-data: Breaks altgr in Norwegian layout

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1040802 [xkb-data] xkb-data: Breaks altgr in Norwegian layout
Severity set to 'normal' from 'serious'
> tags -1 + moreinfo
Bug #1040802 [xkb-data] xkb-data: Breaks altgr in Norwegian layout
Added tag(s) moreinfo.

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

Bug#1050516: checkit-tiff: FTBFS on big-endian platforms

[Andreas Romeyke]

Hi,

On Fri, 25 Aug 2023 17:39:39 +0200
Bastian Germann  wrote:

> Source: checkit-tiff
> Severity: serious
> X-Debbugs-Cc: a...@andreas-romeyke.de, oltma...@zib.de
> 
> The new checkit-tiff upstream version 1.4.3 does not build on
> big-endian platforms. Note: it was updated from 0.4.2, so the issue
> is not necessarily only in 1.4.3. You can get logs at
> https://buildd.debian.org/status/package.php?p=checkit-tiff
> 
> The issue triggers multiple times on running the test suite and ends
> up: "(HE)TIFF Header error, not a MAGIC BYTE for TIFF: 0x2a00"

There is a new v1.4.4 release which should fix the big-endian issues.
Sucessfully tested with m68k-linux-gnu-gcc, see file 'FAQ'. Not tested
with ICC proflib.

See https://git.fsfe.org/art1pirat/checkit_tiff/releases for a short
summary of the release.

Please do not hesitate to contact me, if you detect further bugs.

With best regards

Andreas

-- 
Dipl. Inf. (FH) Andreas Romeyke, http://andreas-romeyke.de/


pgpuhjPEXtQ7c.pgp
Description: Digitale Signatur von OpenPGP

Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

[Aurelien Jarno]

Source: enblend-enfuse
Version: 4.2-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

enblend-enfuse fails to build from source. From my build log on amd64:

| /usr/bin/gnuplot --default-settings -e 'DATA_DIR="../../doc"' \
| -e 'set output "log-transform.tex"; set terminal epslatex color 
size 4.5in,3.375in' ../../doc/log-transform.gp && \
| mv log-transform.tex log-transform.pstex
| /usr/bin/m4 --fatal-warnings --prefix-builtins --synclines 
--define='dot_output_type=eps' ../../doc/uml-dot.m4 
../../doc/external-mask-workflow.dot | \
| /usr/bin/dot  -Teps -Gsize=4.75,8.5 -oexternal-mask-workflow.eps
| failed at node 36[0]
| dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.
| /bin/bash: line 2: 2820245 Done/usr/bin/m4 
--fatal-warnings --prefix-builtins --synclines --define='dot_output_type=eps' 
../../doc/uml-dot.m4 ../../doc/external-mask-workflow.dot
|  2820246 Aborted (core dumped) | /usr/bin/dot -Teps 
-Gsize=4.75,8.5 -oexternal-mask-workflow.eps
| make[5]: *** [Makefile:978: external-mask-workflow.eps] Error 134
| make[5]: Leaving directory '/<>/build-def/doc'
| make[4]: *** [Makefile:592: all-recursive] Error 1
| make[4]: Leaving directory '/<>/build-def/doc'
| make[3]: *** [Makefile:444: all-recursive] Error 1
| make[3]: Leaving directory '/<>/build-def'
| make[2]: *** [Makefile:385: all] Error 2
| make[2]: Leaving directory '/<>/build-def'
| dh_auto_build: error: cd build-def && make -j12 returned exit code 2
| make[1]: *** [debian/rules:37: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:66: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=enblend-enfuse=riscv64=4.2-10=1693064284=0

Regards
Aurelien

Bug#1050674: ispell-czech: FTBFS: Can't exec "/<>/debian/myspell-cs.install"

[Aurelien Jarno]

Source: ispell-czech
Version: 20040229-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

ispell-czech fails to build from source:

| install -o 0 -g 0 -m 644 ./czech.aff 
/<>/debian/tmp/usr/lib/ispell
| install -o 0 -g 0 -m 644 ./czech.hash 
/<>/debian/tmp/usr/lib/ispell
| rm -f ./czech.hash
| make[1]: Leaving directory '/<>'
|dh_install -a
| Can't exec "/<>/debian/myspell-cs.install": No such file or 
directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1616.
| dh_install: error: cannot run debian/myspell-cs.install: No such file or 
directory
| make: *** [debian/rules:4: binary-arch] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

A full build log is available:
https://buildd.debian.org/status/fetch.php?pkg=ispell-czech=arm64=20040229-6=1692525149=0

Regards
Aurelien

Bug#1050673: gmult: FTBFS: error: Argument 1: Cannot convert from `unowned uint8[]' to `unowned string'

[Aurelien Jarno]

Source: gmult
Version: 11.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

gmult fails to build from source. From my build log on amd64:

| valac -C --pkg=config --target-glib=2.70 --vapidir /<>/vapi 
--pkg gtk4 --target-glib ' 2.70' --pkg glib-2.0 --pkg libadwaita-1 
--color=always --directory gmult/gmult.p --basedir ../gmult 
--gresources=../data/resources.xml ../gmult/main.vala ../gmult/Canvas.vala 
../gmult/CharBox.vala ../gmult/DigitBox.vala ../gmult/GtkMult.vala 
../gmult/MultPuzzle.vala ../gmult/ScalingLetter.vala ../gmult/Separator.vala 
../gmult/TableBox.vala
| ../gmult/CharBox.vala:44.29-44.36: error: Argument 1: Cannot convert from 
`unowned uint8[]' to `unowned string'
|44 | provider.load_from_data(css.data);
|   | ^~~~  
| ../gmult/CharBox.vala:44.5-44.37: error: 1 missing arguments for `void 
Gtk.CssProvider.load_from_data (string, ssize_t)'
|44 | provider.load_from_data(css.data);
|   | ^ 
| ../gmult/ScalingLetter.vala:40.19-40.35: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|40 | var context = get_style_context();
|   |   ^   
| ../gmult/ScalingLetter.vala:40.9-40.15: warning: `Gtk.StyleContext' has been 
deprecated since 4.10
|40 | var context = get_style_context();
|   | ^~~   
| ../gmult/ScalingLetter.vala:41.5-41.22: warning: `Gtk.Snapshot.render_layout' 
has been deprecated since 4.10
|41 | snap.render_layout(context, x, y, layout);
|   | ^~
| ../gmult/CharBox.vala:56.5-56.28: warning: `Gtk.Widget.get_style_context' has 
been deprecated since 4.10
|56 | button.get_style_context().add_provider(provider, 
Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION);
|   | ^~~~  
 
| ../gmult/TableBox.vala:28.5-28.16: warning: `Gtk.DropTarget.on_drop' has been 
deprecated since vala-0.58. Use DropTarget.drop
|28 | drag.on_drop.connect(handle_drag_drop);
|   | ^~~~   
| ../gmult/Separator.vala:13.17-13.33: warning: `Gtk.Widget.get_style_context' 
has been deprecated since 4.10
|13 | var style = get_style_context ();
|   | ^
| ../gmult/Separator.vala:13.9-13.13: warning: `Gtk.StyleContext' has been 
deprecated since 4.10
|13 | var style = get_style_context ();
|   | ^
| Compilation failed: 2 error(s), 7 warning(s)
| ninja: build stopped: subcommand failed.
| dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j12 -v 
returned exit code 1
| make: *** [debian/rules:6: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=gmult=riscv64=11.0-1=1693145453=0

Regards
Aurelien

Bug#1050672: granite-7: FTBFS: error: Argument 1: Cannot convert from `unowned uint8[]' to `unowned string'

[Aurelien Jarno]

Source: granite-7
Version: 7.3.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

granite-7 fails to build from source. From my build log on amd64:

| valac -C --define=LINUX --abi-stability --hide-internal --target-glib=2.50 
--pkg posix --pkg gtk4 --pkg gobject-2.0 --target-glib 2.50 --pkg glib-2.0 
--pkg gio-unix-2.0 --pkg gio-2.0 --pkg gee-0.8 --color=always --directory 
lib/libgranite-7.so.7.3.0.p --basedir ../lib --library granite-7 --header 
lib/granite-7.h --vapi ../granite-7.vapi --gir ../Granite-7.0.gir 
--gresources=../lib/Styles/styles.gresource.xml ../lib/DateTime.vala 
../lib/Constants.vala ../lib/Init.vala ../lib/Services/Application.vala 
../lib/Services/AsyncMutex.vala ../lib/Services/ContractorProxy.vala 
../lib/Services/Portal.vala ../lib/Services/Settings.vala 
../lib/Services/System.vala ../lib/Widgets/AbstractSettingsPage.vala 
../lib/Widgets/AbstractSimpleSettingsPage.vala ../lib/Widgets/AccelLabel.vala 
../lib/Widgets/DatePicker.vala ../lib/Widgets/Dialog.vala 
../lib/Widgets/HeaderLabel.vala ../lib/Widgets/HyperTextView.vala 
../lib/Widgets/MessageDialog.vala ../lib/Widgets/ModeSwitch.vala 
../lib/Widgets/OverlayBar.vala ../lib/Widgets/Placeholder.vala 
../lib/Widgets/SettingsSidebarRow.vala ../lib/Widgets/SettingsSidebar.vala 
../lib/Widgets/Settings.vala ../lib/Widgets/SwitchModelButton.vala 
../lib/Widgets/TimePicker.vala ../lib/Widgets/Toast.vala 
../lib/Widgets/Utils.vala ../lib/Widgets/ValidatedEntry.vala lib/Config.vala
| ../lib/Init.vala:53.9-53.24: warning: `Gtk.StyleContext' has been deprecated 
since 4.10
|53 | Gtk.StyleContext.add_provider_for_display (display, 
base_provider, Gtk.STYLE_PROVIDER_PRIORITY_THEME);
|   | ^~~~  

| ../lib/Init.vala:56.13-56.28: warning: `Gtk.StyleContext' has been deprecated 
since 4.10
|56 | Gtk.StyleContext.add_provider_for_display (display, 
app_provider, Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION);
|   | ^~~~  
 
| ../lib/Widgets/AccelLabel.vala:110.43-110.71: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|   110 | var accel_label_context = 
accel_label.get_style_context ();
|   |   
^
| ../lib/Widgets/AccelLabel.vala:110.21-110.39: warning: `Gtk.StyleContext' has 
been deprecated since 4.10
|   110 | var accel_label_context = 
accel_label.get_style_context ();
|   | ^~~   
 
| ../lib/Widgets/HyperTextView.vala:252.9-252.20: warning: `Gtk.show_uri' has 
been deprecated since 4.10
|   252 | Gtk.show_uri (null, uri, Gdk.CURRENT_TIME);
|   | ^~~~   
| ../lib/Widgets/ModeSwitch.vala:91.9-91.37: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|91 | mode_switch.get_style_context ().add_class 
(Granite.STYLE_CLASS_MODE_SWITCH);
|   | ^ 
   
| ../lib/Widgets/SettingsSidebarRow.vala:83.9-83.37: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|83 | title_label.get_style_context ().add_class 
(Granite.STYLE_CLASS_H3_LABEL);
|   | ^ 

| ../lib/Widgets/SettingsSidebar.vala:95.17-95.39: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|95 | label.get_style_context ().add_class 
(Granite.STYLE_CLASS_H4_LABEL);
|   | ^~~   
  
| ../lib/Widgets/SwitchModelButton.vala:53.49-53.83: warning: 
`Gtk.Widget.get_style_context' has been deprecated since 4.10
|53 | unowned var description_style_context = 
description_label.get_style_context ();
|   | 
^~~
| ../lib/Widgets/SwitchModelButton.vala:53.21-53.45: warning: 
`Gtk.StyleContext' has been deprecated since 4.10
|53 | unowned var description_style_context = 
description_label.get_style_context ();
|   | ^ 
 
| ../lib/Widgets/Utils.vala:269.38-269.45: error: Argument 1: Cannot convert 
from `unowned uint8[]' to `unowned string'
|   269 | css_provider.load_from_data (css.data);
|   |  ^~~~  
| ../lib/Widgets/Utils.vala:269.9-269.46: error: 1 missing arguments for `void 
Gtk.CssProvider.load_from_data (string, ssize_t)'
|   

Bug#1050671: zabbix: FTBFS: malformed import path "[cmd/compile]": invalid char '['

[Aurelien Jarno]

Source: zabbix
Version: 1:6.0.14+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

zabbix fails to build from source. From my build log on amd64:

| make[1]: Leaving directory '/<>'
|dh_strip -a -O--max-parallel=4
|dh_makeshlibs -a -O--max-parallel=4
|dh_shlibdeps -a -O--max-parallel=4
|dh_installdeb -a -O--max-parallel=4
|debian/rules override_dh_gencontrol
| make[1]: Entering directory '/<>'
| if [ -d "debian/zabbix-agent2" ]; then DH_GOPKG="..." dh_golang 
--package=zabbix-agent2 --sourcedirectory=src/go/ ;fi
| malformed import path "[cmd/compile]": invalid char '['
| dh_golang: error: go list -f '\
| {{ .Dir }}/{{ index (or .GoFiles .CgoFiles .TestGoFiles .XTestGoFiles 
.IgnoredGoFiles) 0 }}' returned exit code 1
| make[1]: *** [debian/rules:197: override_dh_gencontrol] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:83: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=zabbix=riscv64=1%3A6.0.14%2Bdfsg-1=1693070592=0

Regards
Aurelien

Bug#1050670: mod-gnutls: FTBFS: GnuTLS: Failed to initialize: (-1250) An unimplemented or disabled feature has been requested.

[Aurelien Jarno]

Source: mod-gnutls
Version: 0.9.0-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

mod-gnutls fails to build from source due to testsuite issue. From my
build log on amd64:

| 
| Testsuite summary for mod_gnutls 0.9.0
| 
| # TOTAL: 34
| # PASS:  1
| # SKIP:  0
| # XFAIL: 0
| # FAIL:  33
| # XPASS: 0
| # ERROR: 0
| 
| See test/test-suite.log
| 

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=mod-gnutls=riscv64=0.9.0-1.1=1693057445=0

Regards
Aurelien

Bug#1031046: Unacceptable - Asterisk is too popular to exclude

[debian . org]

Hello Moritz,

I've read your bug report at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031046


I believe it to be unacceptable to exclude Asterisk from Bookworm. 
Asterisk is used by a LOT of users worldwide and, as you've noted, is 
frequently the subject of security concerns.


The VoIP Team is currently working on a plan to resolve your concerns.

If we don't provide Debian users with secure packages, they will use 
packages from less reputable sources and chaos will ensue.


I believe the VoIP team can deliver on the commitments you are asking 
for, we are working on raising a bigger team of volunteers so we can 
more effectively address CVEs.


Stay tuned.

David

Bug#1050667: DSA for jupyter-core in oldstable triggers nbconvert autopkgtest

[Paul Gevers]

Source: nbconvert
Version: 5.6.1-3
Severity: serious
Tags: bullseye

[Please CC me on replies]

 Forwarded Message 
Subject: DSA for jupyter-core in oldstable triggers nbconvert autopkgtest
Date: Thu, 3 Aug 2023 11:37:04 +0200
From: Paul Gevers 
To: nbconv...@packages.debian.org
CC: debian-release 

Hi nbconvert maintainers,

DSA 5422 [1] seems to be triggering an autopkgtest regression in 
nbconvert. Looking at the name of the test, this could be a serious 
problem for nbconvert users on oldstable. Can you please investigate and 
let us know if you need to fix nbconvert in the next point release update?


 From the log [2]:
109s === FAILURES 
===
109s _ TestNbConvertApp.test_default_config 
_

109s
109s self = testMethod=test_default_config>

109s
109s def test_default_config(self):
109s """
109s Does the default config work?
109s """
109s with self.create_temp_cwd(['notebook*.ipynb', 
'jupyter_nbconvert_config.py']):

109s >   self.nbconvert('--log-level 0')
109s
109s 
/usr/lib/python3/dist-packages/nbconvert/tests/test_nbconvertapp.py:227:
109s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _

109s
109s self = testMethod=test_default_config>
109s parameters = ['--log-level', '0'], ignore_return_code = False, 
stdin = None

109s
109s def nbconvert(self, parameters, ignore_return_code=False, 
stdin=None):

109s """
109s Run nbconvert as a shell command, listening for both Errors and
109s non-zero return codes. Returns the tuple (stdout, stderr) of
109s output produced during the nbconvert run.
109s
109s Parameters
109s --
109s parameters : str, list(str)
109s List of parameters to pass to IPython.
109s ignore_return_code : optional bool (default False)
109s Throw an OSError if the return code
109s """
109s cmd = [sys.executable, '-m', 'nbconvert']
109s if sys.platform == 'win32':
109s if isinstance(parameters, string_types):
109s cmd = ' '.join(cmd) + ' ' + parameters
109s else:
109s cmd = ' '.join(cmd + parameters)
109s else:
109s if isinstance(parameters, string_types):
109s parameters = shlex.split(parameters)
109s cmd += parameters
109s p = Popen(cmd, stdout=PIPE, stderr=PIPE, stdin=PIPE)
109s stdout, stderr = p.communicate(input=stdin)
109s if not (p.returncode == 0 or ignore_return_code):
109s >   raise OSError(bytes_to_str(stderr))
109s E   OSError
109s
109s /usr/lib/python3/dist-packages/nbconvert/tests/base.py:162: OSError

Paul

[1] https://security-tracker.debian.org/tracker/DSA-5422
[2] 
https://ci.debian.net/data/autopkgtest/oldstable/amd64/n/nbconvert/36344377/log.gz


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050367: marked as done (qtcreator: FTBFS with newer yaml-cpp [PATCH])

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2023 19:11:37 +
with message-id 
and subject line Bug#1050367: fixed in qtcreator 10.0.2-4
has caused the Debian Bug report #1050367,
regarding qtcreator: FTBFS with newer yaml-cpp [PATCH]
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.)


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

Source: qtcreator
Version: 10.0.2-1ubuntu1
Severity: important
tags: patch

Hello, looks like the new yaml-cpp version is making the embedded cmake fail to 
detect it.
An easy workaround/patch is the following:

diff -Nru qtcreator-10.0.2/debian/rules qtcreator-10.0.2/debian/rules
--- qtcreator-10.0.2/debian/rules   2022-11-29 08:15:58.0 +
+++ qtcreator-10.0.2/debian/rules   2023-08-23 08:59:59.0 +
@@ -32,6 +32,10 @@
 %:
dh $@ --builddirectory=builddir
 
+override_dh_auto_clean:

+   dh_auto_clean
+   rm -rf cmake/Findyaml-cpp.cmake
+
 override_dh_auto_configure:
dh_auto_configure --buildsystem=cmake -- \
-DBUILD_DEVELOPER_DOCS=ON \

thanks for considering it, this bug will become serious once yaml-cpp 
transition is ack'd by Release Team
G.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 10.0.2-4
Done: Pino Toscano 

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated qtcreator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Aug 2023 20:45:25 +0200
Source: qtcreator
Architecture: source
Version: 10.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 1050367
Changes:
 qtcreator (10.0.2-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Pino Toscano ]
   * Revert the changes done in 10.0.2-2 and 10.0.2-3:
 - first of all, they were uploaded totally untested, unreviewed, as
   "team upload", whereas they were effectively NMUs, as Gianfranco is not
   part of the team
 - the fix-yaml-cpp-search.patch patch is an own creation not forwarded
   upstream
 - the nonsense in dh_auto_clean, i.e. removing cmake/Findyaml-cpp.cmake,
   causes the above patch to even not work at all
   * Backport upstream commit 170f9acfb41704b68e2ba98690fd6d5e98addd85 to find
 yaml-cpp 0.8; patch upstream_ClangTools-Add-support-for-yaml-cpp-0.8.patch.
 (Closes: #1050367)
   * Drop build tweaks for mipsel, as that architecture was recently
 discontinued.
   * Update lintian overrides.
 .
   [ Lisandro Damián Nicanor Pérez Meyer ]
   * Update Qt packages listed as build dependencies that have changed their
 name.
Checksums-Sha1:
 4f28fd80d004981eddcc5591707782432d2f8719 2725 qtcreator_10.0.2-4.dsc
 a2fea479498fd2fa56f2b4c06c93b2318a073d69 30576 qtcreator_10.0.2-4.debian.tar.xz
 114403c629a467e70d6921c836c764a2a9bac511 12631 
qtcreator_10.0.2-4_source.buildinfo
Checksums-Sha256:
 d49f91dd2a226e7b14089a82737a1b76e9d1a053fcd2a5a2b1ed19eac0db9783 2725 
qtcreator_10.0.2-4.dsc
 01d1839ecbaa1427b73d7e2d3bf6957ade167457ea0d29b4573e32315953ee1c 30576 
qtcreator_10.0.2-4.debian.tar.xz
 67445b73e63765b14b9d037c3ac89c0babcf1d15bab2ae1357633ebb71ecc592 12631 
qtcreator_10.0.2-4_source.buildinfo
Files:
 6ccd89dc3a0b85a9d424dba3319b4da8 2725 devel optional qtcreator_10.0.2-4.dsc
 c8f5a30148c582ba76721ef9c2fbc6a6 30576 devel optional 
qtcreator_10.0.2-4.debian.tar.xz
 dbace85106eb258629a5824cd3b7046e 12631 devel optional 
qtcreator_10.0.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmTrmgUACgkQLRkciEOx
P00s1A/+KJt43Du8/Y1811MyCh0xlYFjWav7dKcJJnYsh6tWL1AzhLnf/dZ+E/do
LcLoFYCYhKMYc/7vzTbJ9pOn8mIbelFkcWn8lS5CFPD8XuTjGqC0bEfugLQJ2c5/
7RO8/015m8rmn8UrEmoO3ftBV70uml4NOrcOCv2WOe4T1Hg2M+nl8QXzkCaUcVns
B1w53l+1fkFQdD9ODwqGlLd7BpSdc8nM4llnXUZLj2IPQQQnwFuuc+8L2sgYyWam

Processed: notfixed 1050367 in qtcreator/10.0.2-2, reopening 1050367

[Debian Bug Tracking System]

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

> notfixed 1050367 qtcreator/10.0.2-2
Bug #1050367 {Done: Gianfranco Costamagna } 
[src:qtcreator] qtcreator: FTBFS with newer yaml-cpp [PATCH]
No longer marked as fixed in versions qtcreator/10.0.2-2.
> reopen 1050367
Bug #1050367 {Done: Gianfranco Costamagna } 
[src:qtcreator] qtcreator: FTBFS with newer yaml-cpp [PATCH]
Bug reopened
Ignoring request to alter fixed versions of bug #1050367 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Debian Bug Tracking System]

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

> reassign 1050429 gcc-13 13.2.0-2
Bug #1050429 [musl-tools] musl: unusable on mipsel, mips64el: 
mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Bug reassigned from package 'musl-tools' to 'gcc-13'.
No longer marked as found in versions musl/1.2.3-1.
Ignoring request to alter fixed versions of bug #1050429 to the same values 
previously set
Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: 
unrecognised command-line option '-EL'
Marked as found in versions gcc-13/13.2.0-2.
> notfound 1050429 12.3.0-8
Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: 
unrecognised command-line option '-EL'
There is no source info for the package 'gcc-13' at version '12.3.0-8' with 
architecture ''
Unable to make a source version for version '12.3.0-8'
Ignoring request to alter found versions of bug #1050429 to the same values 
previously set
> affects 1050429 musl-tools
Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: 
unrecognised command-line option '-EL'
Added indication that 1050429 affects musl-tools
> thanks
Stopping processing here.

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

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Thorsten Glaser]

reassign 1050429 gcc-13 13.2.0-2
notfound 1050429 12.3.0-8
affects 1050429 musl-tools
thanks

Dixi quod…

>The -EL is not even musl-specific?!
>
>(sid_mips64el-dchroot)tg@eller:~$ cat 
>"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
[…]

Worse, doing mips64el-linux-gnuabi64-gcc{,-12} -dumpspecs and
diffing the result, there’s no change regarding -EL either.

This looks like a genuine GCC bug? I’m reassigning.

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Thorsten Glaser]

Dixi quod…

>(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -EL
>(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -specs 
>"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
>mips64el-linux-gnuabi64-gcc: error: unrecognized command-line option '-EL'
>(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc-12 hi.c -EL
>(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc-12 hi.c -specs 
>"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
>(sid_mips64el-dchroot)tg@eller:~$ _
>
>… but a regression (?) in GCC 13 versus GCC 12.

The -EL is not even musl-specific?!

(sid_mips64el-dchroot)tg@eller:~$ cat 
"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
%rename cpp_options old_cpp_options

*cpp_options:
-nostdinc -isystem /usr/include/mips64el-linux-musl -isystem include%s 
%(old_cpp_options)

*cc1:
%(cc1_cpu) -nostdinc -isystem /usr/include/mips64el-linux-musl -isystem 
include%s

*link_libgcc:
-L/usr/lib/mips64el-linux-musl -L .%s

*libgcc:
libgcc.a%s %:if-exists(libgcc_eh.a%s)

*startfile:
%{!shared: /usr/lib/mips64el-linux-musl/Scrt1.o} 
/usr/lib/mips64el-linux-musl/crti.o crtbeginS.o%s

*endfile:
crtendS.o%s /usr/lib/mips64el-linux-musl/crtn.o

*link:
-dynamic-linker /lib/ld-musl-mips64el.so.1 -nostdlib %{shared:-shared} 
%{static:-static} %{rdynamic:-export-dynamic}

*esp_link:


*esp_options:


*esp_cpp_options:


(sid_mips64el-dchroot)tg@eller:~$ _

There’s no -EL in that file‽ So apparently GCC 13 is breaking of itself?

bye,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Thorsten Glaser]

Dixi quod…

>According to upstream documentation, -EL is supposed to be supported
>by the compiler driver:

OK so it’s not the compiler *driver*…

(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -EL
(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -specs 
"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
mips64el-linux-gnuabi64-gcc: error: unrecognized command-line option '-EL'
(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc-12 hi.c -EL
(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc-12 hi.c -specs 
"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
(sid_mips64el-dchroot)tg@eller:~$ _

… but a regression (?) in GCC 13 versus GCC 12.

bye,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#1041810: librsvg: CVE-2023-38633

[Salvatore Bonaccorso]

Hi Simon,

On Sat, Aug 19, 2023 at 06:57:30PM +0200, Salvatore Bonaccorso wrote:
> Hi Simon,
> 
> On Sun, Jul 30, 2023 at 09:48:57PM +0100, Simon McVittie wrote:
> > On Sun, 30 Jul 2023 at 22:04:24 +0200, Salvatore Bonaccorso wrote:
> > > For bullseye I think we should simply pick the upstream commit?
> > 
> > Yes: we didn't keep up with upstream 2.50.x so there are a bunch of
> > unrelated fixes (2.50.4 up to .7) which would be out of scope for a
> > security update. If it was a package I knew better then I might be
> > advocating the new upstream release, but I can't really assess risk vs
> > benefit for librsvg, so cherry-picking the equivalent of .8 and .9 seems
> > more conservative.
> > 
> > 
> > compiles successfully, I'll try it in a bullseye VM next.
> 
> If you are happy with the results and coverage from unstable, would
> you be open to prepare/finalize next the respective updates for
> bookworm-security and bullseye-security?
> 
> Thanks a lot for your work so far on it!

With some delays DSA released for it. In fact, I guess anybody running
e.g. a webservice converting untrusted svg files would sandbox anyway
such a service. Upstream correctly noted that in the upstream issue.

Thanks for your work and contributing the update!

Regards,
Salvatore

Bug#1042343: binutils-msp430: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_build] Error 1

[Thiago Marques]

On Sun, Aug 27, 2023 at 12:25:53PM +0200, Bastian Germann wrote:
> The stuff that is currently in debian/patches should be patched at the 
> binutils-source package (if the files were 
> available, which they are not). Please hand in your patches there and only 
> maintain binutils patches that are 
> platform-specific.
> 
> Thanks!
Hi,
Ok, I will do it.
I'm working on a new version of this package with the fix. I will use
the upstream (Texas Instruments, Inc) patch.

Regards,

Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

[Thorsten Glaser]

Hm.

According to upstream documentation, -EL is supposed to be supported
by the compiler driver:

https://gcc.gnu.org/onlinedocs/gcc/MIPS-Options.html

bye,
//mirabilos
-- 
  "Using Lynx is like wearing a really good pair of shades: cuts out
   the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
 -- Henry Nelson, March 1999

Bug#1042147: virt-manager: FTBFS: AssertionError: Conversion outputs did not match.

[Fabio Fantoni]

after saw the autoremove from testing on 08 September for an RC and 
nobody working on it I did a search upstream for the fix, was not 
present so I created the patch and forwarded upstream 
(https://github.com/virt-manager/virt-manager/pull/559). After I created 
an MR: 
https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/16


can someone merge and release new build before the autoremove from 
testing please?




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033167: marked as done (usrmerge: messes with /etc/shells)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2023 12:36:14 +
with message-id 
and subject line Bug#1033167: fixed in usrmerge 36
has caused the Debian Bug report #1033167,
regarding usrmerge: messes with /etc/shells
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.)


-- 
1033167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 25
Severity: serious
Justification: violates policy section 10.7.4
Control: affects -1 + debianutils dash
X-Debbugs-Cc: jo...@debian.org, cl...@debian.org, andre...@debian.org, 
debian-rele...@lists.debian.org

Hi,

I think that it is quite obvious that /etc/shells is debianutils'
territory. When I found that on some systems /etc/shells was out of sync
with /var/lib/shells.state, I was quite puzzled until I noticed that
usrmerge messes with this file. This really is debianutils'
configuration file and usrmerge has no business in touching it in
uncoordinated ways. Refer to policy section 10.7.4 for details, so
usrmerge is technically rc-buggy. However, usrmerge does have reason to
touch it, so the solution is not simply to drop convert-etc-shells with
no replacement.

Let us dive a bit into how an essential system can come to be.

1. We start either merged (e.g. debootstrap or mmdebstrap with
   --hook-dir=.../merged-usr) or unmerged (mmdebstrap without hook or
   an old debootstrap --no-merged-usr).

2. We either install usrmerge or usr-is-merged. Though we cannot
   combine starting unmerged with usr-is-merged for obvious reasons.

3. The last invocation of update-shells happens before or after
   usrmerge.postinst. (Not relevant in case of usr-is-merged)

So what happens in these cases?

If and only if usrmerge is used, convert-etc-shells turns /bin/sh into
/usr/bin/sh. So whenever we start out merged and use usr-is-merged,
/usr/bin/sh goes missing.

If usrmerge is used, the order of entries in /etc/shells depends on
whether update-shells is run after it or not. Likewise
/var/lib/shells.state also depends. This is not some mmdebstrap-specific
problem. You can easily observe this with debootstrap --no-merged-usr
and installing usrmerge vs just doing debootstrap.

This is bad from a reproducibility point of view and it is rooted in
usrmerge not cooperating with other packages, but instead doing things
behind their back, which happens to violate policy.

So how to fix this?

For one thing, the /bin/sh difference is rooted in the fact that /bin/sh
is a standard value of debianutils and not managed using shells.d even
though dash ships plain /bin/sh these days. I think dash should just add
/bin/sh to /usr/share/debianutils/shells.d/dash and we'd be done as all
entries in shells.d are correctly managed wrt. merged-/usr by
update-shells.

The next thing is that convert-etc-shells needs to go away from
usrmerge. In the age of systems with usr-is-merged, there is no
convert-etc-shells (as there is no usrmerge), so it must work without
somehow anyway. When you run update-shells after a merge, it will pick
up the merged shell locations (for shells managed in shells.d) and add
them to /etc/shells. So usrmerge should ensure that update-shells is
called after having performed the merge. This is the only way to get
reproducibility. (That doesn't quite answer yet when to run it, how to
run it, nor whether that makes convert-etc-shells unnecessary though.)

Then we still have add-shell and remove-shell and most packages using
them induce policy violations (reverting admin changes on upgrade), so
we want to change them to the shells.d mechanism in the long run, but
that's not where we are today and especially not what we can rely on in
bookworm. So for these entries, we still do need convert-etc-shells and
indeed we cannot just delete it. convert-etc-shells compensates for the
difference in behaviour of add-shell pre-merge vs post-merge.

I think the best solution here would be merging convert-etc-shells into
update-shells. Whenever we run update-shells, it should check whether
the system is already merged and when it is, perform the equivalent to
convert-etc-shells. Then usrmerge can just install an empty (except for
a comment) /usr/share/debianutils/shells.d/usrmerge to trigger
update-shells and things become fully reproducible in all cases, because
no matter how we started, we will run update-shells post merge and
that'll do the right thing. And since usrmerge now uses the tools
provided by debianutils, this fully resolves the policy violation. Also
note that usr-is-merged does not have to invoke the trigger 

Bug#1037846: marked as done (rocm-smi-lib: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2023 12:03:35 +
with message-id 
and subject line Bug#1037846: fixed in rocm-smi-lib 5.2.3-3
has caused the Debian Bug report #1037846,
regarding rocm-smi-lib: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rocm-smi-lib
Version: 5.2.3-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/rocm-smi-lib_5.2.3-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
  (arch=riscv64 
armel)_ZTVSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.2.0
  (arch=any-amd64 arm64 mips64el ppc64el s390x alpha ia64 ppc64 sparc64 
any-i386 armhf mipsel hppa m68k powerpc 
sh4)_ZTVSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.5.2
  (arch=riscv64 
armel)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.2.0
- 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
+#MISSING: 5.2.3-2# 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
  
(optional)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.1.0
  
(arch=riscv64)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapImSt10shared_ptrISt6vectorImSaImEEESt4lessImESaISt4pairIKmS5_EEESaISC_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.2.0
- 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapImSt10shared_ptrISt6vectorImSaImEEESt4lessImESaISt4pairIKmS5_EEESaISC_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
+#MISSING: 5.2.3-2# 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapImSt10shared_ptrISt6vectorImSaImEEESt4lessImESaISt4pairIKmS5_EEESaISC_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
  
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapImSt10shared_ptrISt6vectorImSaImEEESt4lessImESaISt4pairIKmS5_EEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.1.0
  
(arch=armel)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapIySt10shared_ptrISt6vectorIySaIyEEESt4lessIyESaISt4pairIKyS5_EEESaISC_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.2.0
  (arch=any-i386 armhf mipsel hppa m68k powerpc 
sh4)_ZTVSt23_Sp_counted_ptr_inplaceISt3mapIySt10shared_ptrISt6vectorIySaIyEEESt4lessIyESaISt4pairIKyS5_EEESaISC_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.1.0
  
(arch=riscv64)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorImSaImEESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.2.0
- 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorImSaImEESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
+#MISSING: 5.2.3-2# 
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorImSaImEESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 4.5.2
  
(optional)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorImSaImEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.1.0
  
(arch=armel)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorIySaIyEESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.2.0
  (arch=any-i386 armhf mipsel hppa m68k powerpc 
sh4)_ZTVSt23_Sp_counted_ptr_inplaceISt6vectorIySaIyEESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.1.0
@@ -11574,6 +11653,7 @@
  
_ZZNKSt7__cxx1112regex_traitsIcE16lookup_classnameIPKcEENS1_10_RegexMaskET_S6_bE12__classnames@Base
 4.5.2
  

Bug#1050606: marked as done (find: ‘/lib/systemd/system-sleep’: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2023 11:49:09 +
with message-id 
and subject line Bug#1050606: fixed in cryptsetup 2:2.6.1-5
has caused the Debian Bug report #1050606,
regarding find: ‘/lib/systemd/system-sleep’: No such file or directory
to be marked as done.

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

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


-- 
1050606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup-suspend
Version: 2:2.6.1-4
Severity: serious

The cryptsetup-suspend wrapper makes unconditional use of the
/lib/systemd/system-sleep directory.

This directory was removed from the systemd package as a result of the
discussion in https://salsa.debian.org/systemd-team/systemd/-/merge_requests/208

The failing autopkgtest of cryptsetup is now blocking the testing
migration of the systemd package (thus the RC severity).

Please update cryptsetup-suspend-wrapper to handle the case where the
directory /lib/systemd/system-sleep is missing.

Regards,
Michael
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.6.1-5
Done: Guilhem Moulin 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Aug 2023 12:24:57 +0200
Source: cryptsetup
Architecture: source
Version: 2:2.6.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 1038285 1050606
Changes:
 cryptsetup (2:2.6.1-5) unstable; urgency=medium
 .
   [ Guilhem Moulin ]
   * d/control: Drop cryptsetup-run transitional binary package.
 (Closes: #1038285)
 .
   [ Michael Biebl ]
   * cryptsetup-suspend-wrapper: Don't error out on missing
 /lib/systemd/system-sleep directory, which was removed from the systemd
 package. (Closes: #1050606)
Checksums-Sha1:
 f6035ae57546d47376f622441047943284321ac1 3548 cryptsetup_2.6.1-5.dsc
 7887cc027df4a35d8339cc10500dad4f70f1b66d 157956 
cryptsetup_2.6.1-5.debian.tar.xz
 66e522620d090c798640bb6a1e7e79179d17e739 11364 
cryptsetup_2.6.1-5_amd64.buildinfo
Checksums-Sha256:
 43c19a436ac24f9cc4130a277a6675fa9d498de2e58e3c7dd25c458f28ae64e8 3548 
cryptsetup_2.6.1-5.dsc
 bfeabdcadecd2975b4c0d94ec4bddc6efa57ebedc6ff7a6d33ae0b656cd24ba3 157956 
cryptsetup_2.6.1-5.debian.tar.xz
 2104d730ece823baf0130a792e49bf01acdc01a378e1ea01edfa65f5a5db965c 11364 
cryptsetup_2.6.1-5_amd64.buildinfo
Files:
 de143e4ab238c8a682d16ba39b017503 3548 admin optional cryptsetup_2.6.1-5.dsc
 09833db056b9766fde71ce601089141a 157956 admin optional 
cryptsetup_2.6.1-5.debian.tar.xz
 9eb850e381be23480e4b94e447875d93 11364 admin optional 
cryptsetup_2.6.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmTrJcsACgkQ05pJnDwh
pVIh5A//TIH7ybDnK1qdEsj7XsttAwoeMnq5SSLfNjnsMHeOfYn3Rysn27AdfOpt
i/DUyUEuU/CT5ArmM3VFcDsMtD5lmY1FEltbkuoXfjyWAC7JcO/uAjjIzxayzI/O
1vqAbZXVFe05o9t9qsA4apVIit2R6H7lCGARIj2QXFTq0MRY6VgLXQ6r6OeGLMwN
oN5iEbO2rkT5DjvsuTqAvcU/7ArjWg3Kh0ZyFDPz8i4TJIyQdjvZPoq4Y+vPxpDs
wh/V339sW9PFFo3yZ+fZYTo87a3gVcnIepPTHN/nQJeEcYrxB31L39bwSeq05z4u
8Avww96LQdsKCf3ZrMZISSUdh++mjpTdh18orH6jKDMugaPSpmNxPqQCFKKQqbJs
yaI52YHGMS43oNte6wUzf9vWt63fbVmOEf2r9Npd4/63wcXuRiRWPuicf/Scbqha
nJoEUIQcmp+Z9K+3FE983fG+rWRHFPXuTvuPUcXFUAAsGhYcjoTt75jiK6TaCUXH
3cZPc2ya8qv5ii/sIlWdZDn4xY4yGieutF/CxKYhwrzZhRAnqoKGwObYex3S5yzh
UHLcIhZDTTNi1VO5O5EuX4Sjw0gTAxe1kCjvMVSbtounNgbDW/UzEZsK4PpMTOeT
3mGeWZdS9xUsMv51I+YWGDSnMM8eC7qXjeStPz6N+SDGsNt9MdU=
=yBru
-END PGP SIGNATURE End Message ---

Bug#1050432: rpy2: FTBFS on mips64el

[Dirk Eddelbuettel]

On 27 August 2023 at 18:44, YunQiang Su wrote:
| Maybe there is something wrong with ffi. (In fact the complex support of mips
| was added by me. ;)

Hah.
 
| I am looking for a way to use debug to debug the extensions.
| If you have any documents, can you point it to me.

I can help you with R, I think here the issue is more on the Python side.

But to the best of my knowledge, the applications languages generally just
call into the C library 'and assume things work'.  But maybe here we need
another compile-time / link-time option to turn ffi on?

Dirk

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

Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl

[Niko Tyni]

(full quote for the benefit of the Aurelien and other glibc maintainers)

On Sat, Aug 26, 2023 at 09:07:38PM +0300, Niko Tyni wrote:
> Package: perl
> Version: 5.36.0-8
> Severity: serious
> X-Debbugs-Cc: debian-powe...@lists.debian.org
> Control: affects -1 libfile-fcntllock-perl
> 
> Hi,
> 
> debugging an unexpected autopkgtest failure of
> libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found
> it's because the old perl binary (5.36.0-7) was built with the fcntl(2)
> constant F_GETLK == 12, but the new one with F_GETLK == 5 [2].
> 
> There are no source or build system changes in perl that would have caused
> this change. The failure is currently blocking perl testing migration,
> so filing at 'serious'.
> 
> Perl is built with -D_FILE_OFFSET_BITS=64, and I see that on bullseye
> this causes F_GETLK == F_GETLK64 == 12, but on bookworm and later
> F_GETLK == 5 while F_GETLK64 == 12 [3]. I didn't find the exact
> change that caused this yet.
> 
> As can be expected from the above, building libfile-fcntllock-perl on
> bookworm against perl_5.36.0-7 makes it fail its test suite in a similar
> way. And rebuilding it on sid against perl_5.36.0-8 makes it pass.
> 
> On amd64 the constants have stayed equal (== 5) from bullseye to sid,
> and _FILE_OFFSET_BITS=64 doesn't affect them. What's the deal on ppc64el?
> 
> Copying the powerpc porters list. Could you please look into this?
> 
> [1] 
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/libf/libfile-fcntllock-perl/34669085/log.gz
> [2] perl -MPOSIX -E 'say F_GETLK'
> [3] printf '#include \nF_GETLK\nF_GETLK64\n' | cpp 
> -D_FILE_OFFSET_BITS=64 | tail -2

I think the relevant change here is this in libc6-dev_2.36-9+deb12u1 for 
bookworm:

--- libc6-dev_2.36-9/usr/include/powerpc64le-linux-gnu/bits/fcntl.h 
2023-04-10 09:35:16.0 +0100
+++ libc6-dev_2.36-9+deb12u1/usr/include/powerpc64le-linux-gnu/bits/fcntl.h 
2023-07-13 19:07:47.0 +0100
@@ -33,6 +33,12 @@
 # define __O_LARGEFILE 020
 #endif
 
+#if __WORDSIZE == 64
+# define F_GETLK   5
+# define F_SETLK   6
+# define F_SETLKW  7
+#endif
+

and a similar one in 2.37-2 for trixie/sid.

The applicable changelog entry is presumably

   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 [...]
 - Not affecting bookworm release architectures:
   - Fix LFS POSIX lock constants for powerpc64.

Aurelien, it seems that there's an oversight as ppc64el is a release 
architecture?

I can see that this changed for the better, but what should I do with the above
breakage? Rebuild perl and libfcntl-fcntllock-perl and declare some Breaks?
Do we want to do that for stable too?
-- 
Niko Tyni   nt...@debian.org

Processed: lua5.2: remove as soon as all reverse dependencies are gone

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1050599 1050598 1050597 1050596 1050540 1050543 1050624 1050625 
> 1050626 1050627
Bug #1050640 [src:lua5.2] lua5.2: remove as soon as all reverse dependencies 
are gone
1050640 was not blocked by any bugs.
1050640 was not blocking any bugs.
Added blocking bug(s) of 1050640: 1050540, 1050625, 1050598, 1050599, 1050596, 
1050543, 1050597, 1050627, 1050624, and 1050626
> block -1 by 1050628 1050629 1050630 1050631 1050632 1050633 1050634 1050635 
> 1050636 1050637
Bug #1050640 [src:lua5.2] lua5.2: remove as soon as all reverse dependencies 
are gone
1050640 was blocked by: 1050626 1050624 1050627 1050597 1050599 1050543 1050598 
1050596 1050625 1050540
1050640 was not blocking any bugs.
Added blocking bug(s) of 1050640: 1050633, 1050637, 1050636, 1050634, 1050630, 
1050631, 1050632, 1050629, 1050635, and 1050628

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

Bug#1033167: usrmerge: messes with /etc/shells

[Luca Boccassi]

On Thu, 22 Jun 2023 22:52:53 +0200 Andreas Beckmann 
wrote:
> Hi Marco,
> 
> two questions about convert-etc-shells:
> 
> 1.) why does usrmerge.postinst call /usr/lib/usrmerge/convert-etc-
shells 
> (nearly) unconditionally (i.e. on every upgrade of the usrmerge 
> package)? Shouldn't that be a one-shot update and therefore be called
at 
> the end of maybe_convert (from within maybe_convert, not after), s.t.
it 
> is skipped if the system is already converted?
> 
> 2.) can you call update-shells from within convert-etc-shells (or
from 
> usrmerge.postinst directly before calling convert-etc-shells), s.t.
most 
> of the /etc/shells modifications are performed by update-shells and
the 
> state file /var/lib/shells.state gets updated properly?
> 
> I have just uploaded a NMU for debianutils to DELAYED/10 that fixes
some 
> issues (#1035820) and maybe makes convert-etc-shells superfluous.

Hello Andreas and Helmut,

Is there anything left to do here after Andreas' NMU fixing
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035820 last month,
or can we close this?

-- 
Kind regards,
Luca Boccassi


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

Bug#1050432: rpy2: FTBFS on mips64el

[YunQiang Su]

Dirk Eddelbuettel  于2023年8月27日周日 16:52写道：
>
>
> On 27 August 2023 at 14:09, YunQiang Su wrote:
> | Dirk Eddelbuettel  于2023年8月27日周日 00:15写道：
> | >
> | >
> | > Hi all,
> | >
> | > As the test failures for complex valued variables appeared to be systemic 
> on
> | > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) 
> and
> | > conditioned the number of failing tests away via
> | >
> | >   @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
> 'little',
> | >   reason="Complex tests fails for 'mips64el'.")
> | >
> | > Maybe the porters team can shed some light on why we needed it, and if 
> this
> | > worked (the autobuilders will tell us soon enough) I can pass the patch 
> on to
> | > Laurent for a possible inclusion upstream.
> | >
> |
> | Sorry for the late reply. I can work on it.
>
> Appreciate that!
>
> (While my fix corrected the build, it is a stop-gap as it avoids the issue. A
> real fix would be good.)
>
> | Do you knwo any way to run a single testcase?
>
> Can you start from the unit tests I conditioned out?  Each of those has
> simple expression with a complex in it. Those should be executable directly
> in the Python interpreter. You probably need all the build-deps (python, R,
> rpy2, numpy, ...) installed.
>

Maybe there is something wrong with ffi. (In fact the complex support of mips
was added by me. ;)

I am looking for a way to use debug to debug the extensions.
If you have any documents, can you point it to me.

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



-- 
YunQiang Su

Bug#1050623: intake: autopkgtest needs update for dask 2023.8.0

[Graham Inggs]

Source: intake
Version: 0.6.6-1
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the upload of dask 2023.8.0+dfsg-1, the autopkgtests of intake
are failing [1].  I've copied what I hope is the relevant part of the
log below.  This same failure causes intake to FTBFS in unstable.

Regards
Graham


[1] https://ci.debian.net/packages/i/intake/testing/amd64/


103s === FAILURES
===
103s ___ test_remote_env

103s
103s intake_server = 'intake://localhost:7483'
103s
103s def test_remote_env(intake_server):
103s import os
103s os.environ['INTAKE_TEST'] = 'client'
103s catalog = open_catalog(intake_server)
103s catalog.remote_env
103s with pytest.raises(Exception) as e:
103s catalog.remote_env.read()
103s
103s with pytest.raises(Exception) as e:
103s catalog.local_env
103s >   assert 'path-client' in str(e.value)
103s E   assert 'path-client' in "('Connection aborted.',
RemoteDisconnected('Remote end closed connection without response'))"
103s E+  where "('Connection aborted.',
RemoteDisconnected('Remote end closed connection without response'))"
= str(ConnectionError(ProtocolError('Connection aborted.',
RemoteDisconnected('Remote end closed connection without response'
103s E+where ConnectionError(ProtocolError('Connection
aborted.', RemoteDisconnected('Remote end closed connection without
response'))) = .value
103s
103s intake/catalog/tests/test_remote_integration.py:247: AssertionError

Processed: Bug#1037846 marked as pending in rocm-smi-lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037846 [src:rocm-smi-lib] rocm-smi-lib: ftbfs with GCC-13
Added tag(s) pending.

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

Bug#1050606: marked as pending in cryptsetup

[Guilhem Moulin]

Control: tag -1 pending

Hello,

Bug #1050606 in cryptsetup 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/cryptsetup-team/cryptsetup/-/commit/2609636237a72ba204aae4ec26f6f4d15db8831c


cryptsetup-suspend-wrapper: Don't error out on missing 
/lib/systemd/system-sleep directory.

This directory was removed from the systemd package as a result of the
discussion in 
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/208 .

Closes: #1050606


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050606

Processed: Bug#1050606 marked as pending in cryptsetup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050606 [cryptsetup-suspend] find: ‘/lib/systemd/system-sleep’: No such 
file or directory
Added tag(s) pending.

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

Bug#1037846: marked as pending in rocm-smi-lib

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1037846 in rocm-smi-lib 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/rocm-team/rocm-smi-lib/-/commit/3d23c4b1243b4577c48a21c0910aa7987d009a2d


d/*.symbols*: update symbols table for gcc 13.

Closes: #1037846
Closes: #1042134


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037846

Processed: Bug#1042134 marked as pending in rocm-smi-lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042134 [src:rocm-smi-lib] rocm-smi-lib: FTBFS: dpkg-gensymbols: error: 
some symbols or patterns disappeared in the symbols file: see diff output below
Added tag(s) pending.

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

Bug#1042134: marked as pending in rocm-smi-lib

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1042134 in rocm-smi-lib 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/rocm-team/rocm-smi-lib/-/commit/3d23c4b1243b4577c48a21c0910aa7987d009a2d


d/*.symbols*: update symbols table for gcc 13.

Closes: #1037846
Closes: #1042134


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042134

Processed: Re: Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 kmod does not work with XZ in-kernel module decompression
Bug #1050586 [kmod] kmod is broken with custom kernels with 
CONFIG_MODULE_COMPRESS_*=y
Bug #1050582 [kmod] kmod is broken with custom kernels with 
CONFIG_MODULE_COMPRESS_*=y
Changed Bug title to 'kmod does not work with XZ in-kernel module 
decompression' from 'kmod is broken with custom kernels with 
CONFIG_MODULE_COMPRESS_*=y'.
Changed Bug title to 'kmod does not work with XZ in-kernel module 
decompression' from 'kmod is broken with custom kernels with 
CONFIG_MODULE_COMPRESS_*=y'.

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

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Marco d'Itri]

Control: retitle -1 kmod does not work with XZ in-kernel module decompression

On Aug 27, Jon Westgate  wrote:

> Note that I already had "Support in-kernel module decompression" selected
> when the compression method was XZ.
> 
> Would you like me to try without it?
No need to: we know that everything works fine without in-kernel 
decompression, because this is how the Debian kernel is configured.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Jon Westgate]

All,
To confirm that switching to ZSTD works.

I ran make menuconfig,
   [*] Enable loadable module support  --->

        Module compression mode (ZSTD) --->
        [*]   Support in-kernel module decompression
Note that I already had "Support in-kernel module decompression" 
selected when the compression method was XZ.


Would you like me to try without it?

On a side note switching module compression mode did not require a full 
recompile.
I presume it just linked in a different module decompressor, then 
compressed the modules using ZSTD on the fly when I ran make modules_install


Jon

On 27/08/2023 11:24, Jon Westgate wrote:

Dear Marco and others,

I will do a test build using ZSTD and see if that works. - I think the 
first thing I did was to switch back to XZ when this first happened 
Yesterday.


I've been using XZ for module compression since it was available, I 
just select it using make menuconfig I'm not using anything other than 
a slight tweek to the debian build.
I don't use signing as my UEFI allows me not to, the only other thing 
I do different to Debian is to build in USB support, filesystem 
support for ext4 and BTRFS and build in SCSI, LIBATA so that should my 
initrd fail for any reason I'm not left high and dry with no keyboard 
support and no access to a filesystem. I used to build in networking 
support, but I only do that systems that I use for firewalling as 
systemd won't allow networking unless everything else is mostly perfect.


I started using module compression for net boot thin clients as it 
made the resulting initrd way quicker to load over TFTP. Later on I 
switched to using it on all my systems as it made the boot process 
much quicker.


Finally I found that on recent 6.x kernels it was required due to a 
size limit that seemed to appear initrd. I'm not sure what makes this 
limit, it's there in grub and refind.


If what you say is true then kmod might have been masking a kernel bug 
for the last year.


I'm not doing anything clever here, I just get my source from 
cdn.kernel.org, use make menuconfig or vim to edit the .config and 
make -j8 && make -j8 modules_install && make install then reboot.

I'm not applying any patches, I do used the NVIDIA drivers on some boxes.

Jon


On 27/08/2023 02:10, Marco d'Itri wrote:

On Aug 26, Jon Westgate <0...@fsck.tv> wrote:


The error message it gave was "decompresson failed with status 6"

Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with
settings that are not supported by this XZ decoder".
So it looks like you have compressed the modules (how?) with XZ settings
which are supported by the userspace loader but not by the kernel one.







OpenPGP_0x420652A8C309A3B2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Jon Westgate]

Dear Marco and others,

I will do a test build using ZSTD and see if that works. - I think the 
first thing I did was to switch back to XZ when this first happened 
Yesterday.


I've been using XZ for module compression since it was available, I just 
select it using make menuconfig I'm not using anything other than a 
slight tweek to the debian build.
I don't use signing as my UEFI allows me not to, the only other thing I 
do different to Debian is to build in USB support, filesystem support 
for ext4 and BTRFS and build in SCSI, LIBATA so that should my initrd 
fail for any reason I'm not left high and dry with no keyboard support 
and no access to a filesystem. I used to build in networking support, 
but I only do that systems that I use for firewalling as systemd won't 
allow networking unless everything else is mostly perfect.


I started using module compression for net boot thin clients as it made 
the resulting initrd way quicker to load over TFTP. Later on I switched 
to using it on all my systems as it made the boot process much quicker.


Finally I found that on recent 6.x kernels it was required due to a size 
limit that seemed to appear initrd. I'm not sure what makes this limit, 
it's there in grub and refind.


If what you say is true then kmod might have been masking a kernel bug 
for the last year.


I'm not doing anything clever here, I just get my source from 
cdn.kernel.org, use make menuconfig or vim to edit the .config and make 
-j8 && make -j8 modules_install && make install then reboot.

I'm not applying any patches, I do used the NVIDIA drivers on some boxes.

Jon


On 27/08/2023 02:10, Marco d'Itri wrote:

On Aug 26, Jon Westgate <0...@fsck.tv> wrote:


The error message it gave was "decompresson failed with status 6"

Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with
settings that are not supported by this XZ decoder".
So it looks like you have compressed the modules (how?) with XZ settings
which are supported by the userspace loader but not by the kernel one.





OpenPGP_0x420652A8C309A3B2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042343: binutils-msp430: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_build] Error 1

[Bastian Germann]

The stuff that is currently in debian/patches should be patched at the binutils-source package (if the files were 
available, which they are not). Please hand in your patches there and only maintain binutils patches that are 
platform-specific.


Thanks!

Processed: Re: Bug#1050606: Acknowledgement (find: ‘/lib/systemd/system-sleep’: No such file or directory)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1050606 [cryptsetup-suspend] find: ‘/lib/systemd/system-sleep’: No such 
file or directory
Added tag(s) patch.

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

Bug#1050606: Acknowledgement (find: ‘/lib/systemd/system-sleep’: No such file or directory)

[Michael Biebl]

Control: tags -1 + patch

Please find attached a patch which should be sufficient to address this 
issue. I can offer to NMU, in case you are busy.



Regards,
Michael
diff --git a/debian/scripts/suspend/cryptsetup-suspend-wrapper b/debian/scripts/suspend/cryptsetup-suspend-wrapper
index 52e09dd1..953196c0 100644
--- a/debian/scripts/suspend/cryptsetup-suspend-wrapper
+++ b/debian/scripts/suspend/cryptsetup-suspend-wrapper
@@ -46,6 +46,7 @@ read_config() {
 # Run all executable scripts in directory SYSTEM_SLEEP_PATH with arguments ARGS
 # mimic systemd behavior
 run_dir() {
+[ -d "$SYSTEM_SLEEP_PATH" ] || return 0
 find "$SYSTEM_SLEEP_PATH" -type f -executable -execdir {} "$@" \;
 }
 


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050618: rocrand: failing autopkgtests on gfx1030

[Christian Kastner]

Source: rocrand
Version: 5.5.1-1
Severity: serious

The tests from ci.rocm.debian.net failed on gfx1030 [1]. I'm filing this
RC bug to prevent migration to testing.

[1] 
https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocrand/83/log.gz

Bug#1050432: rpy2: FTBFS on mips64el

[Dirk Eddelbuettel]

On 27 August 2023 at 14:09, YunQiang Su wrote:
| Dirk Eddelbuettel  于2023年8月27日周日 00:15写道：
| >
| >
| > Hi all,
| >
| > As the test failures for complex valued variables appeared to be systemic on
| > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
| > conditioned the number of failing tests away via
| >
| >   @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
| >   reason="Complex tests fails for 'mips64el'.")
| >
| > Maybe the porters team can shed some light on why we needed it, and if this
| > worked (the autobuilders will tell us soon enough) I can pass the patch on 
to
| > Laurent for a possible inclusion upstream.
| >
| 
| Sorry for the late reply. I can work on it.

Appreciate that!

(While my fix corrected the build, it is a stop-gap as it avoids the issue. A
real fix would be good.)

| Do you knwo any way to run a single testcase?

Can you start from the unit tests I conditioned out?  Each of those has
simple expression with a complex in it. Those should be executable directly
in the Python interpreter. You probably need all the build-deps (python, R,
rpy2, numpy, ...) installed.

Dirk

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

Bug#1049952: csh: maintained by ubuntu-devel-disc...@lists.ubuntu.com

[Bastian Germann]

X-Debbugs-Cc: mckins...@debian.org

On Thu, 17 Aug 2023 11:34:56 +0200 Lucas Nussbaum  wrote:

Hi,

this package is maintained by ubuntu-devel-disc...@lists.ubuntu.com,
which is not a suitable contact point for Debian packages maintenance
according to https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

This is most likely due to generating the source package on an Ubuntu
machine. I think there's some magic that replaces the Maintainer field
in the Ubuntu tooling.


Alastair, as you are the owner of the Vcs-Git and the uploader of the last 
years,
would you please make yourself the Maintainer of csh? Otherwise I will orphan 
the package.

Thanks,
Bastian

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Antonio]

ticket:

https://techpatterns.com/forums/about3040.html

Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed

[Antonio]

I don't build kernel from source, I use binary packages installed from 
liquorix repositories https://liquorix.net/.


I opened a ticket to their forum, maybe a recompilation of the kernel is 
enough.


We await your reply...


Il 27/08/23 03:10, Marco d'Itri ha scritto:

On Aug 26, Jon Westgate <0...@fsck.tv> wrote:


The error message it gave was "decompresson failed with status 6"

Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with
settings that are not supported by this XZ decoder".
So it looks like you have compressed the modules (how?) with XZ settings
which are supported by the userspace loader but not by the kernel one.

Bug#1050530: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1050530: fixed in python3.11 3.11.5-2)

[Jochen Sprickerhof]

Hi Matthias,

I think it would be enough to add the tzdata-legacy dependency to 
libpython3.11-testsuite.


I've also send a patch upstream to switch to the normal name:

https://github.com/python/cpython/pull/108533

Cheers Jochen

* Debian Bug Tracking System  [2023-08-26 19:09]:

This is an automatic notification regarding your Bug report
which was filed against the src:python3.11 package:

#1050530: python3.11: autopkgtest needs update for new version of tzdata

It has been closed by Debian FTP Masters  (reply to 
Matthias Klose ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to Matthias Klose ) by
replying to this email.


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



Date: Sat, 26 Aug 2023 19:05:36 +
To: 1050530-cl...@bugs.debian.org
Reply-To: Matthias Klose 
From: Debian FTP Masters 
Subject: Bug#1050530: fixed in python3.11 3.11.5-2




Date: Fri, 25 Aug 2023 21:08:52 +0200
To: sub...@bugs.debian.org
User-Agent: Mozilla Thunderbird
From: Paul Gevers 
Subject: python3.11: autopkgtest needs update for new version of tzdata

Source: python3.11
Version: 3.11.4-1
Severity: serious
X-Debbugs-CC: tzd...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:tzdata

Dear maintainer(s),

With a recent upload of tzdata the autopkgtest of python3.11 fails in 
testing when that autopkgtest is run with the binary packages of 
tzdata from unstable. It passes when run with only packages from 
testing. In tabular form:


  passfail
tzdata from testing2023c-10
python3.11 from testing3.11.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. I note that 
src:tzdata recently introduced a tzdata-legacy package although I 
don't know if that has to do with the failure.


Currently this regression is blocking the migration of tzdata to 
testing [1]. Of course, tzdata shouldn't just break your autopkgtest 
(or even worse, your package), but it seems to me that the change in 
tzdata was intended and your package needs to update to the new 
situation.


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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.11/37127326/log.gz

1107s ==
1107s FAIL: test_variable_tzname 
(test.test_email.test_utils.LocaltimeTests.test_variable_tzname)

1107s --
1107s Traceback (most recent call last):
1107s   File "/usr/lib/python3.11/test/support/__init__.py", line 847, 
in inner

1107s return func(*args, **kwds)
1107s^^^
1107s   File "/usr/lib/python3.11/test/test_email/test_utils.py", line 
155, in test_variable_tzname

1107s self.assertEqual(t1.tzname(), 'MSK')
1107s AssertionError: 'Europe' != 'MSK'
1107s - Europe
1107s + MSK








signature.asc
Description: PGP signature

Bug#1050614: src:dpf-plugins: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: dpf-plugins
Version: 1.6+ds-2
Severity: serious
Control: close -1 1.7+ds-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:dpf-plugins has been trying to migrate for 
31 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=dpf-plugins



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.7+ds-1
Bug #1050614 [src:dpf-plugins] src:dpf-plugins: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked as fixed in versions dpf-plugins/1.7+ds-1.
Bug #1050614 [src:dpf-plugins] src:dpf-plugins: fails to migrate to testing for 
too long: uploader built arch:all binaries
Marked Bug as done

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

Processed: src:numba: fails to migrate to testing for too long: triggers autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.57.1+dfsg-1
Bug #1050613 [src:numba] src:numba: fails to migrate to testing for too long: 
triggers autopkgtest failure
Marked as fixed in versions numba/0.57.1+dfsg-1.
Bug #1050613 [src:numba] src:numba: fails to migrate to testing for too long: 
triggers autopkgtest failure
Marked Bug as done
> affects -1 src:python-sparse
Bug #1050613 {Done: Paul Gevers } [src:numba] src:numba: 
fails to migrate to testing for too long: triggers autopkgtest failure
Added indication that 1050613 affects src:python-sparse

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

Bug#1050613: src:numba: fails to migrate to testing for too long: triggers autopkgtest failure

[Paul Gevers]

Source: numba
Version: 0.56.4+dfsg-2
Severity: serious
Control: close -1 0.57.1+dfsg-1
X-Debbugs-CC: python-spa...@packages.debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: affects -1 src:python-sparse

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:numba has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable triggers 
failures in python-sparse on amd64 and ppc64el (the rest regressed 
already last year).


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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050432: rpy2: FTBFS on mips64el

[YunQiang Su]

Dirk Eddelbuettel  于2023年8月27日周日 00:15写道：
>
>
> Hi all,
>
> As the test failures for complex valued variables appeared to be systemic on
> the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
> conditioned the number of failing tests away via
>
>   @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
> 'little',
>   reason="Complex tests fails for 'mips64el'.")
>
> Maybe the porters team can shed some light on why we needed it, and if this
> worked (the autobuilders will tell us soon enough) I can pass the patch on to
> Laurent for a possible inclusion upstream.
>

Sorry for the late reply. I can work on it.
Do you knwo any way to run a single testcase?

> Cheers,  Dirk
>
> --
> dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
>


-- 
YunQiang Su