date:20240209

Source: fgallery
Version: 1.9.1+ds-1
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

2024-02-09 Thread Philip Hands

Michael Tokarev  writes:

> 09.02.2024 16:58, ca...@allfreemail.net
>> Package: console-setup
>> Followup-For: Bug #1063518
>> 
>> Consider making all scripts provided by console-setup
>> shellcheck-clean, there are lots of tiny issues that can turn into
>> big issues under the right conditions.
>
> Please do not do this. Shellcheck is a huge problem and we had large amount
> of bugs due to people trying to apply its suggestions.  It's very difficult
> in many cases to spot why shellcheck is wrong (classic is the suggestion to
> put $var into double quotes "$var" which breaks badly if $var is supposed to
> contain zero or more separate words - this way, even boot scripts has become
> buggy leading to system becoming unbootable).
>
> Shellcheck is a very bad tool.

I think the reality is somewhere between these two positions.

Shellcheck is not particularly helpful for most of D-I because it
doesn't have a shell variant that perfectly matches our busybox sh
build.  That might have just improved, since I notice that a busybox sh
variant has just been merged upstream, so we'll see if that makes things
better.

On the other hand, if I'd been paying attention at the time, the fact
that this change dropped the number of shellcheck reports for setupcon
from 189 to 1 should have rung some alarm bells, but it seems that I've
learnt to ignore the little '!' in my emacs status bar -- I'll have to
keep an eye on that in future.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

Bug#1063564: engrampa: transition from p7zip to 7zip

Source: engrampa
Version: 1.26.1-4
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063321: libwxgtk3.2-1t64 has an undeclared file conflict

2024-02-09 Thread Scott Talbert


On Tue, 6 Feb 2024, Helmut Grohne wrote:


Package: libwxgtk3.2-1t64
Version: 3.2.4+dfsg-3.1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libwxgtk-gl3.2-1 libwxgtk-gl3.2-1t64 libwxgtk-media3.2-1 
libwxgtk-media3.2-1t64 libwxgtk-webview3.2-1 libwxgtk-webview3.2-1t64
X-Debbugs-Cc: vor...@debian.org

libwxgtk3.2-1t64 has an undeclared file conflict. This may result in an
unpack error from dpkg.


Hello Steve,

Are you planning on fixing this, or would you like me to?  If the latter, 
how would you like the fix submitted before this is uploaded to unstable?


Regards,
Scott

Bug#1063534: [Debian-iot-maintainers] Bug#1063534: libjwt: CVE-2024-25189

2024-02-09 Thread Moritz Muehlenhoff

On Fri, Feb 09, 2024 at 04:40:31PM +0100, Thorsten Alteholz wrote:
> Hi Moritz,
> 
> thanks for the bug. Upstream knows about the issue and already fixed it [1]
> + [2].

Thanks. I think the real worl impact is pretty negligible, it's enough to land
a fix for the next release, but not for released suites.

Cheers,
Moritz

Bug#1061468: gloo: attempts to build on unsupported 32 bit systems

2024-02-09 Thread Petter Reinholdtsen

[Dan Bungert]
> Thanks Paul, I didn't know about that.  Clearly architecture-is-64-bit
> is the better solution.

I did not know about it either, and I agree that it is a much better
solution than listing individual architectures.  It will ensure new 64
bits architectures will be handled automatically, and avoid my major
objection of maintaing a list of individual architectures.

> Do you consider that scenario likely?

I have no idea.  I continue to be amazed by the prorities and choices
make with computers, and have no way to evaluate the likelyhood . :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#1063563: ghostscript: ps2epsi fails with Error: /undefined in /finddevice

2024-02-09 Thread Stephan Boettcher

Package: ghostscript
Version: 10.02.1~dfsg-3
Severity: normal

The version 10.0.0~dfsg-10 works and produces the expected output.
10.01.2~dfsg-1 works as well.

10.02.1~dfsg-3 does not:

$ ps2epsi hvosc-doc_sch.ps hvosc-doc_sch.eps
Error: /undefined in /finddevice
Operand stack:   (bit)
Execution stack:   %interp_exit   .runexec2   --nostringval--   --nostringval-- 
  --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1944   1   3   %oparray_pop   
1943   1   3   %oparray_pop   1928   1   3   %oparray_pop   1801   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   
--nostringval--
Dictionary stack:   --dict:746/1123(ro)(G)--   --dict:0/20(G)--   
--dict:99/200(L)--
Current allocation mode is local
Current file position is 4836
GPL Ghostscript 10.02.1: Unrecoverable error, exit code 1

Is this similar to bug #1003926 ?

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

Kernel: Linux 6.1.21-falbala (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ghostscript depends on:
ii  libc62.37-15
ii  libgs10  10.0.0~dfsg-10

ghostscript recommends no packages.

ghostscript suggests no packages.

-- no debconf information

Bug#1062167: globus-rsl: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 14:32:37 +0100
Source: globus-rsl
Architecture: source
Version: 11.4-1
Distribution: unstable



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

Bug#1063156: myproxy: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 14:44:42 +0100
Source: myproxy
Architecture: source
Version: 6.2.16-1
Distribution: unstable



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

Bug#1062157: globus-gsi-credential: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 14:19:40 +0100
Source: globus-gsi-credential
Architecture: source
Version: 8.4-1
Distribution: unstable



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

Bug#1062156: globus-gsi-cert-utils: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 14:04:34 +0100
Source: globus-gsi-cert-utils
Architecture: source
Version: 10.11-1
Distribution: unstable



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

Bug#1062160: globus-gsi-sysconfig: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 15:12:34 +0100
Source: globus-gsi-sysconfig
Architecture: source
Version: 9.6-1
Distribution: unstable



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

Bug#1062153: globus-gridftp-server: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 13:48:21 +0100
Source: globus-gridftp-server
Architecture: source
Version: 13.25-1
Distribution: unstable



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

Bug#1062145: globus-gass-copy: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 12:34:54 +0100
Source: globus-gass-copy
Architecture: source
Version: 10.13-1
Distribution: unstable



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

Bug#1062141: globus-common: NMU diff for 64-bit time_t transition

Package updated in unstable:

Date: Fri, 09 Feb 2024 11:13:35 +0100
Source: globus-common
Architecture: source
Version: 18.14-1
Distribution: unstable



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

Bug#1063534: [Debian-iot-maintainers] Bug#1063534: libjwt: CVE-2024-25189

2024-02-09 Thread Thorsten Alteholz


Hi Moritz,

thanks for the bug. Upstream knows about the issue and already fixed it 
[1] + [2].


  Thorsten

[1] 
https://github.com/benmcollins/libjwt/commit/f73bac57c5bece16ac24f1a70022aa34355fc1bf
[2] 
https://github.com/benmcollins/libjwt/commit/a5d61ef4f1b383876e0a78534383f38159471fd6

Bug#1063562: dt-schema: Please add version dependency for jsonschema

2024-02-09 Thread Sebastian Reichel

Package: dt-schema
Version: 2023.11-3
Severity: normal

Dear Maintainer,

This package completly breaks when using python3-jsonschema from
experimental (4.19.2-1). I had a quick look and upstream is aware
of the issue. The build script wants a version < 4.18:

https://github.com/devicetree-org/dt-schema/blob/main/pyproject.toml#L28

Also this commit message mentions not supporting recent versions of
the jsonschema module:

https://github.com/devicetree-org/dt-schema/commit/fb80ec43c2044d32cf576ef7c660eedf9c38f9ae

Please add this version information to the "Depends: " section of
the package (i.e. Depends: python3-jsonschema (<4.18)).

Thanks,

-- Sebastian

Bug#1063561: dtrx: transition from p7zip to 7zip

Source: dtrx
Version: 8.5.3-1
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

2024-02-09 Thread Michael Tokarev


09.02.2024 17:57, Thorsten Bonow :

dash << 'EOF'    [15:28:53]
if $( (true) 2>/dev/null); then
  echo "42"
fi
EOF
42

which only works in dash because of the added space between the command 
substitution $(...) and the subshell (...).

Does dash think it has to do arithmetic expansion "$((...))"?


Yes, arithmetic, and that's what bash does too.  dash does not understand
space between two closing parens though, ') )'.  And this is logical - if
the opening is "((", use the same matching "))" for closing.

$(( ... )) is arithmetic expression,
$( ( ... ) ) is a subshell.

Everything else is asking for trouble like this.


But what's POSIX take on this?  I couldn't find anything.  Is this a bug in 
dash or in setupcon?


It's a bug in setupcon.

/mjt

Bug#1063560: dt-schema: Package does not work properly for latest upstream kernel

2024-02-09 Thread Sebastian Reichel

Package: dt-schema
Version: 2023.11-3
Severity: normal
Tags: patch

Dear Maintainer,

I see a huge amount of warning being reported when running CHECK_DTBS in
the kernel tree (latest master). After cherry-picking the following two
upstream commits things are working properly:

https://github.com/devicetree-org/dt-schema/commit/6774d386e3fb42c2a556d7217af63938d76737cb.patch
https://github.com/devicetree-org/dt-schema/commit/fb80ec43c2044d32cf576ef7c660eedf9c38f9ae.patch

Please add them to the Debian packaging. For reference most of the
incorrectly reported issues look like this:

Error in referenced schema matching $id: 
http://devicetree.org/schemas/types.yaml

Thanks,

-- Sebastian

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

2024-02-09 Thread Thorsten Bonow


Thorsten Bonow  writes:


[...]


But what's POSIX take on this?  I couldn't find anything.  Is this a
bug in dash or in setupcon?


I'm stupid[1].  It's a bug in setupcon, POSIX requires the space:

"The syntax of the shell command language has an ambiguity for
expansions beginning with "$((", which can introduce an arithmetic
expansion or a command substitution that starts with a subshell.
Arithmetic expansion has precedence; that is, the shell shall first
determine whether it can parse the expansion as an arithmetic
expansion and shall only parse the expansion as a command substitution
if it determines that it cannot parse the expansion as an arithmetic
expansion.  The shell need not evaluate nested expansions when
performing this determination.  If it encounters the end of input
without already having determined that it cannot parse the expansion
as an arithmetic expansion, the shell shall treat the expansion as an
incomplete arithmetic expansion and report a syntax error.  A
conforming application shall ensure that it separates the "$(" and '('
into two tokens (that is, separate them with white space) in a command
substitution that starts with a subshell.  For example, a command
substitution containing a single subshell could be written as:

$( (command) )"


Footnotes:
[1]  
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03

Bug#1063559: diffoscope: transition from p7zip to 7zip

Source: diffoscope
Version: 255
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1059148: Fixed upstream

2024-02-09 Thread Uli Schlachter


Hi,

this issue was now fixed upstream and thus should be solved in an
upcoming release:
http://cvs.schmorp.de/rxvt-unicode/src/command.C?r1=1.603=1.604=date

Cheers,
Uli

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

2024-02-09 Thread Thorsten Bonow


Package: console-setup
Version: 1.225
Severity: grave

After the upgrade from 1.223, console-setup.service failed to start 
due

to a syntax error in the setupcon script:

,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`

It looks like dash does not like the construct in line 907 where 
there

is an opening '$((' but the closing parentheses are split.

,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`


I tried

dash << 'EOF'[15:28:53]
if $( (true) 2>/dev/null); then
 echo "42"
fi
EOF
42

which only works in dash because of the added space between the 
command substitution $(...) and the subshell (...).


Does dash think it has to do arithmetic expansion "$((...))"?

bash and zsh in sh mode accept nesting a subshell within the command 
substitution without an extra space.  In the last version of the 
script, backticks were used, circumventing this issue.


But what's POSIX take on this?  I couldn't find anything.  Is this a 
bug in dash or in setupcon?


Toto

PS: To the proposal of a cleanup: 'checkbashisms' doesn't return any
errors, but IMHO, at least closing (double) quotes on
a line of their own should be fixed:

$ cat /bin/setupcon | grep -n "^\(\"\|'\)$"
[15:47:07]

87:'
145:"
148:"
190:"
193:"
208:"

Bug#1063558: pgpainless 1.6.6 is available

2024-02-09 Thread Daniel Kahn Gillmor

Package: src:pgpainless
Version: 1.6.5-1
Severity: wishlist

pgpainless 1.6.6 is available upstream.  it would be great to have it in
debian.

Thanks,

--dkg


signature.asc
Description: PGP signature

Bug#1063557: deepin-boot-maker: transition from p7zip to 7zip

Source: deepin-boot-maker
Version: 5.7.8+dfsg-3
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063556: [INTL:sv] Swedish strings for firebuild debconf

2024-02-09 Thread Martin Bagge / brother


package: firebuild
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.
--
brother# Translation of firebuild debconf template to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the firebuild package.
#
# Martin Bagge , 2024
msgid ""
msgstr ""
"Project-Id-Version: firebuild\n"
"Report-Msgid-Bugs-To: firebu...@packages.debian.org\n"
"POT-Creation-Date: 2022-11-14 17:54+0100\n"
"PO-Revision-Date: 2024-02-09 16:06+0100\n"
"Last-Translator: Martin Bagge \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Do you accept the terms of the Firebuild license?"
msgstr "Accepterar du villkoren i licensen för Firebuild?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Firebuild users are required to acknowledge and accept the license. Please "
"find it below. If you accept this license, the package installation will "
"continue. If you refuse it, it will be interrupted."
msgstr ""
"Användare av Firebuild måste aktivt bekräfta licensvillkoren, se nedan. Om "
"du accepterar dessa villkor kommer paketinstallationen att fortsätta. Om "
"inte så kommer installationen att avbrytas."

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Firebuild is free for personal use or commercial trial."
msgstr ""
"Firebuild får användas fritt för privat bruk eller som utvärdering i "
"kommernsiella sammanhang."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Non-trial commercial use requires licenses available from https://firebuild.;
"com."
msgstr ""
"Övrig användning i kommersiella sammanhang är inte tillåtet utan en licens "
"från https://firebuild.com.;

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Modification and redistribution are permitted, but commercial use of "
"derivative works is subject to the same requirements of this license."
msgstr ""
"Ändringar och vidareförmedling är tillåtet men kommersiell användning lyder "
"fortsatt under samma villkor."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR "
"IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, "
"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE "
"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER "
"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING "
"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS "
"IN THE SOFTWARE."
msgstr ""
"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR "
"IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, "
"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE "
"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER "
"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING "
"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS "
"IN THE SOFTWARE."

#. Type: error
#. Description
#: ../templates:2001
msgid "The license has been refused"
msgstr "Licensvillkoren har avvisats"

#. Type: error
#. Description
#: ../templates:2001
msgid ""
"Please remove the firebuild packages or reinstall the firebuild package (e."
"g. via apt-get install --reinstall firebuild) to get prompted to accept the "
"license again."
msgstr ""
"Vänligen ta bort firebuild-paketen ellr installera om firebuild-paketet (med "
"hjälp av apt-get install --reinstall firebuild) för att återigen visa "
"licensfrågan."

Bug#1063551: dnsmasq: install systemd units below /usr (DEP17)

Package: dnsmasq
Version: 2.89-1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

we want to finalize the /usr-merge transition by moving aliased files
from / to /usr via DEP17. dnsmasq is involved, because it contains
aliased systemd units. I'm attaching a patch, because dnsmasq cannot use
dh-sequence-movetousr as it does not use debhelper. Note that this patch
must not be uploaded to bookworm-backports or earlier.

Helmut
diff -u dnsmasq-2.89/debian/changelog dnsmasq-2.89/debian/changelog
--- dnsmasq-2.89/debian/changelog
+++ dnsmasq-2.89/debian/changelog
@@ -1,3 +1,10 @@
+dnsmasq (2.89-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move systemd units to /usr for DEP17. (closes: #-1)
+
+ -- Helmut Grohne   Fri, 09 Feb 2024 15:01:03 +0100
+
 dnsmasq (2.89-1) unstable; urgency=low
 
* New upstream.
diff -u dnsmasq-2.89/debian/rules dnsmasq-2.89/debian/rules
--- dnsmasq-2.89/debian/rules
+++ dnsmasq-2.89/debian/rules
@@ -176,7 +176,7 @@
-d debian/trees/daemon/usr/share/dnsmasq \
-d debian/trees/daemon/usr/share/doc/dnsmasq \
-d debian/trees/daemon/etc/default \
-   -d debian/trees/daemon/lib/systemd/system \
+   -d debian/trees/daemon/usr/lib/systemd/system \
-d debian/trees/daemon/usr/lib/tmpfiles.d \
 -d debian/trees/daemon/etc/insserv.conf.d
install -m 644 debian/conffiles debian/trees/daemon/DEBIAN
@@ -195,8 +195,8 @@
install -m 644 debian/default debian/trees/daemon/etc/default/dnsmasq
install -m 644 dnsmasq.conf.example debian/trees/daemon/etc/dnsmasq.conf
install -m 644 debian/readme.dnsmasq.d 
debian/trees/daemon/etc/dnsmasq.d/README
-   install -m 644 debian/systemd.service 
debian/trees/daemon/lib/systemd/system/dnsmasq.service
-   install -m 644 debian/systemd@.service 
debian/trees/daemon/lib/systemd/system/dnsmasq@.service
+   install -m 644 debian/systemd.service 
debian/trees/daemon/usr/lib/systemd/system/dnsmasq.service
+   install -m 644 debian/systemd@.service 
debian/trees/daemon/usr/lib/systemd/system/dnsmasq@.service
install -m 644 debian/tmpfiles.conf 
debian/trees/daemon/usr/lib/tmpfiles.d/dnsmasq.conf
install -m 644 debian/insserv 
debian/trees/daemon/etc/insserv.conf.d/dnsmasq
install -m 644 debian/copyright 
debian/trees/daemon/usr/share/doc/dnsmasq/copyright

Bug#1063555: crunch: transition from p7zip to 7zip

Source: crunch
Version: 3.6-3
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063554: firmware-linux-free: move files to /usr (DEP17)

Package: firmware-linux-free
Version: 20200122-2
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

we want to finalize the /usr-merge transition by moving all aliased
files from / to /usr via DEP17 to avoid any negative effects arising
from aliasing. firmware-linux-free is involved, because it installs
firmware files below /lib/firmware. Since it cannot be converted
automatically using dh-sequence-movetousr, I'm attaching a patch. This
patch should not be uploaded to bookworm-backports or earlier. Also note
that firmware-carl9170 is in the process of taking over firmware from
firmware-linux-free and doing so will cause a file loss (DEP17 P1). This
is tracked as #1050989. I do not expect that firmware-linux-free needs
to support firmware-carl9170 in mitigating this.

Helmut
diff --minimal -Nru firmware-free-20200122/debian/changelog 
firmware-free-20200122/debian/changelog
--- firmware-free-20200122/debian/changelog 2023-08-20 21:56:54.0 
+0200
+++ firmware-free-20200122/debian/changelog 2024-02-09 15:42:17.0 
+0100
@@ -1,3 +1,10 @@
+firmware-free (20200122-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move files to /usr (DEP17). (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 09 Feb 2024 15:42:17 +0100
+
 firmware-free (20200122-2) unstable; urgency=medium
 
   [ Ben Hutchings ]
diff --minimal -Nru firmware-free-20200122/debian/rules.real 
firmware-free-20200122/debian/rules.real
--- firmware-free-20200122/debian/rules.real2023-08-20 21:39:29.0 
+0200
+++ firmware-free-20200122/debian/rules.real2024-02-09 15:42:07.0 
+0100
@@ -15,7 +15,7 @@
dh_prep
@for i in $(FILES); do \
  s="$${i%:*}"; \
- d=/lib/firmware/"$${i#*:}"; \
+ d=/usr/lib/firmware/"$${i#*:}"; \
  echo install -m644 -D "$$s" debian/$(PACKAGE_NAME)"$$d"; \
  install -m644 -D "$$s" debian/$(PACKAGE_NAME)"$$d"; \
done

Bug#1063550: dhcp-helper: move files to /usr for DEP17

Package: dhcp-helper
Version: 1.2-3.1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

we want to move all files from aliased to locations to /usr to finalize
the /usr-merge transition via DEP17. dhcp-helper is involved, because it
installs a systemd unit below /lib. I'm sending you a patch for this
move, because it cannot be automatically moved via
dh-sequence-movetousr. This patch should not be uploaded to
bookworm-backports or earlier.

Helmut
diff --minimal -Nru dhcp-helper-1.2/debian/changelog 
dhcp-helper-1.2/debian/changelog
--- dhcp-helper-1.2/debian/changelog2022-11-23 23:52:28.0 +0100
+++ dhcp-helper-1.2/debian/changelog2024-02-09 14:16:21.0 +0100
@@ -1,3 +1,10 @@
+dhcp-helper (1.2-3.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move systemd unit to /usr for DEP17. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 09 Feb 2024 14:16:21 +0100
+
 dhcp-helper (1.2-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru dhcp-helper-1.2/debian/rules dhcp-helper-1.2/debian/rules
--- dhcp-helper-1.2/debian/rules2021-01-03 21:26:06.0 +0100
+++ dhcp-helper-1.2/debian/rules2024-02-09 14:16:18.0 +0100
@@ -43,7 +43,7 @@
-d debian/tmp/usr/share/man/man8\
 -d debian/tmp/etc/init.d\
 -d debian/tmp/etc/default\
-   -d debian/tmp/lib/systemd/system\
+   -d debian/tmp/usr/lib/systemd/system\
-d debian/tmp/var/run
install -m 644 debian/conffiles debian/tmp/DEBIAN
install -m 755 debian/postinst debian/postrm debian/prerm 
debian/tmp/DEBIAN
@@ -53,7 +53,7 @@
 endif
install -m 755 debian/init debian/tmp/etc/init.d/dhcp-helper
install -m 644 debian/default debian/tmp/etc/default/dhcp-helper
-   install -m 644 debian/systemd.service 
debian/tmp/lib/systemd/system/dhcp-helper.service
+   install -m 644 debian/systemd.service 
debian/tmp/usr/lib/systemd/system/dhcp-helper.service
 ifeq (,$(findstring nodocs,$(DEB_BUILD_OPTIONS)))
cp CHANGELOG debian/tmp/usr/share/doc/$(package)/changelog
gzip -9n debian/tmp/usr/share/doc/$(package)/changelog

Bug#1063553: libexpat1: move files to /usr (DEP17)

Package: libexpat1
Version: 2.5.0-2
Tags: patch
User: helm...@debian.org
Usertags: dep17

Hi,

we want to finalize the /usr-merge transition by moving aliased files
from / to /usr via DEP17 to get rid of problems arising from aliasing.
libexpat1 cannot be converted automatically, because it does not use dh.
Hence, I am sending a patch that performs the move. Do not upload this
patch to bookworm-backports or earlier as you would violate the earlier
/usr-merge moratorium.

Helmut
diff --minimal -Nru expat-2.5.0/debian/changelog expat-2.5.0/debian/changelog
--- expat-2.5.0/debian/changelog2023-06-14 22:08:48.0 +0200
+++ expat-2.5.0/debian/changelog2024-02-09 15:07:25.0 +0100
@@ -1,3 +1,10 @@
+expat (2.5.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move files to /usr (DEP17). (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 09 Feb 2024 15:07:25 +0100
+
 expat (2.5.0-2) unstable; urgency=medium
 
   [ Samuel Thibault  ]
diff --minimal -Nru expat-2.5.0/debian/libexpat1-udeb.install 
expat-2.5.0/debian/libexpat1-udeb.install
--- expat-2.5.0/debian/libexpat1-udeb.install   2012-03-20 19:39:42.0 
+0100
+++ expat-2.5.0/debian/libexpat1-udeb.install   2024-02-09 15:07:15.0 
+0100
@@ -1 +1 @@
-lib/*/libexpat.so.*usr/lib
+usr/lib/*/libexpat.so.*usr/lib
diff --minimal -Nru expat-2.5.0/debian/libexpat1.install 
expat-2.5.0/debian/libexpat1.install
--- expat-2.5.0/debian/libexpat1.install2017-12-17 08:33:25.0 
+0100
+++ expat-2.5.0/debian/libexpat1.install2024-02-09 15:07:21.0 
+0100
@@ -1,3 +1,2 @@
 usr/lib/*/*.so.*
-lib/*/*.so.*
 ../../expat/AUTHORSusr/share/doc/libexpat1/
diff --minimal -Nru expat-2.5.0/debian/rules expat-2.5.0/debian/rules
--- expat-2.5.0/debian/rules2023-06-14 22:08:48.0 +0200
+++ expat-2.5.0/debian/rules2024-02-09 15:06:51.0 +0100
@@ -102,15 +102,6 @@
 endif
$(MAKE) -C build/ install DESTDIR=$(CURDIR)/debian/tmp
$(MAKE) -C buildw/lib install DESTDIR=$(CURDIR)/debian/tmp APIHEADER=
-   # Move libexpat.so.* to /lib so that zfsutils can use it.
-   mkdir -p $(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH)
-   mv $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libexpat.so.* \
-   $(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH)/
-   for i in $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libexpat.so 
; do \
-   dest=$$(readlink $$i) ; \
-   rm -f $$i ; \
-   ln -s /lib/$(DEB_HOST_MULTIARCH)/$$dest $$i ; \
-   done
mkdir -p debian/tmp/usr/include/$(DEB_HOST_MULTIARCH)
mv debian/tmp/usr/include/expat_config.h 
debian/tmp/usr/include/$(DEB_HOST_MULTIARCH)/.

Bug#1063552: libfreebsd-glue-0: move files to /usr (DEP17)

Package: libfreebsd-glue-0
Version: 0.2.22+nmu1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

we want to finalize the /usr-merge transition by moving all aliased
files from / to /usr via DEP17 to avoid any negative effects arising
from aliasing. libfreebsd-glue-0 is involved, because it installs a
shared library below /lib and does not use dh, which would allow
converting it automatically. I am attaching a patch to perform the move.
Do not upload this patch to bookworm-backports or earlier as you would
violate the earlier /usr-merge file move moratorium.

Helmut
diff --minimal -Nru freebsd-glue-0.2.22+nmu1/debian/changelog 
freebsd-glue-0.2.22+nmu2/debian/changelog
--- freebsd-glue-0.2.22+nmu1/debian/changelog   2023-08-07 01:20:16.0 
+0200
+++ freebsd-glue-0.2.22+nmu2/debian/changelog   2024-02-09 15:29:32.0 
+0100
@@ -1,3 +1,10 @@
+freebsd-glue (0.2.22+nmu2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move files to /usr (DEP17). (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 09 Feb 2024 15:29:32 +0100
+
 freebsd-glue (0.2.22+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru 
freebsd-glue-0.2.22+nmu1/debian/libfreebsd-glue-0-udeb.install 
freebsd-glue-0.2.22+nmu2/debian/libfreebsd-glue-0-udeb.install
--- freebsd-glue-0.2.22+nmu1/debian/libfreebsd-glue-0-udeb.install  
2014-08-25 21:40:16.0 +0200
+++ freebsd-glue-0.2.22+nmu2/debian/libfreebsd-glue-0-udeb.install  
2024-02-09 15:29:12.0 +0100
@@ -1 +1 @@
-debian/tmp-udeb/lib/libfreebsd-glue.so.*   lib
+debian/tmp-udeb/usr/lib/libfreebsd-glue.so.*   usr/lib
diff --minimal -Nru freebsd-glue-0.2.22+nmu1/debian/libfreebsd-glue-0.install 
freebsd-glue-0.2.22+nmu2/debian/libfreebsd-glue-0.install
--- freebsd-glue-0.2.22+nmu1/debian/libfreebsd-glue-0.install   2014-08-25 
21:40:16.0 +0200
+++ freebsd-glue-0.2.22+nmu2/debian/libfreebsd-glue-0.install   2024-02-09 
15:29:15.0 +0100
@@ -1 +1 @@
-lib/libfreebsd-glue.so.*
+usr/lib/libfreebsd-glue.so.*
diff --minimal -Nru freebsd-glue-0.2.22+nmu1/debian/rules 
freebsd-glue-0.2.22+nmu2/debian/rules
--- freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-07 01:20:16.0 
+0200
+++ freebsd-glue-0.2.22+nmu2/debian/rules   2024-02-09 15:28:57.0 
+0100
@@ -29,6 +29,7 @@
MAKEOBJDIRPREFIX=$(CURDIR)/obj-deb \
CFLAGS="$(CFLAGS) -O2" \
DESTDIR="$(DESTDIR)" \
+   SHLIBDIR=/usr/lib \
bmake -m /usr/share/mk-freebsd \
CC=$(CC) \
$(NULL)
@@ -37,6 +38,7 @@
MAKEOBJDIRPREFIX=$(CURDIR)/obj-udeb \
CFLAGS="$(CFLAGS) -Os" \
DESTDIR="$(DESTDIR)-udeb" \
+   SHLIBDIR=/usr/lib \
bmake -m /usr/share/mk-freebsd \
CC=$(CC) \
RESCUE=yes \
@@ -76,7 +78,7 @@
dh_testroot
dh_prep -a
dh_installdirs -a
-   mkdir -p $(DESTDIR){,-udeb}/{usr/,}lib
+   mkdir -p $(DESTDIR){,-udeb}/usr/lib
 
$(PMAKE) install
$(PMAKE_UDEB) install

Bug#1052730: ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:

2024-02-09 Thread Pirate Praveen

Control: forwarded -1 
https://github.com/collectiveidea/delayed_job/pull/1203


On Tue, 26 Sep 2023 14:40:49 +0200 Lucas Nussbaum  wrote:


Relevant part (hopefully):
>  ArgumentError:
>Invalid Timezone: US/Eastern


Forwarded fix upstream 
https://github.com/collectiveidea/delayed_job/pull/1203

Bug#1063549: openstack-cluster-installer: Enhancement: preliminary Ceph radosgw support

2024-02-09 Thread Jim Scadden

Package: openstack-cluster-installer
Tags: patch
Severity: wishlist

I've raised a Merge Request [1] to add Ceph radosgw support to OCI. I've
included more detailed information in the MR description, and in the git
commit messages.

Once omission at present is firewall rules. I wanted to get this first
merge request in before spending too much time on this, to (a) try to
keep the commits as small as possible, and (b) find out as early as
possible if I'm heading in the wrong direction! I'm intending to add
firewall rules in the coming weeks.

--

Regards
Jim Scadden (FloydianJim)

[1] 
https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer/-/merge_requests/45

Bug#1061468: gloo: attempts to build on unsupported 32 bit systems

2024-02-09 Thread Dan Bungert

[Paul Wise]
> The right way to do this is to Build-Depend: architecture-is-64-bit

Thanks Paul, I didn't know about that.  Clearly architecture-is-64-bit is the
better solution.

[Petter Reinholdtsen]
> [Dan Bungert]
> > I suggest adjusting the control file to reflect this state so that
> > builds are only attempted on 64 bit systems.
> Why?  Which problem are you trying to solve?  Doing such change will
> fail to automatically discover if gloo start working on other
> architectures, and require extra work to keep the list of architectures
> up to date as Debian evolves.  As far as I can see, the disadvantage of
> trying to build on non-supported architectures is a few wasted CPU
> cycles, while the advantage is less human time spent on package
> maintenance.  Did I miss something?  To me, saving humans time is more
> valuable than saving CPU time.

Saving humans time is a tradeoff I will agree with.  Another angle though is
the time of people looking at problems across an architecture or, like me, who
are temporarily looking at this package and checking why some of the builds
fail.  These "some builds fail" bugs can sometimes indicate a flaky build and
that the rest of the builds can't be considered stable.

Of course that's not the case here - it's a straightforward case of builds
being disabled for 32 bit arches, which is a reasonable decision for upstream
to make.  No problem there.  A bit unfortunate that cmake has this critical
string not at the end of the log file, so the "tail of log" reports at
https://buildd.debian.org/status/package.php?p=gloo are missing this detail,
but that's a cmake issue.

So the tradeoff I'm proposing is making it simpler for others looking at the
package, to remove failed builds that we know will fail.  It indeed has the
downside that if the 32 bit support status changes it will require a change to
reverse.  Do you consider that scenario likely?

There is side benefit here that the CPU time being saved is a bit more rarefied
than amd64.

If the above is uncompelling, you are of course free to decline the change.

-Dan

Bug#1063548: check-all-the-things: transition from p7zip to 7zip

Source: check-all-the-things
Version: 2017.05.20+nmu1
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063547: avfs: transition from p7zip to 7zip

Source: avfs
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063546: atool: transition from p7zip to 7zip

Source: atool
Version: 0.39.0-13
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063545: ark: transition from p7zip to 7zip

Source: ark
Version: 4:23.08.1-2
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063542: python-parsl-doc: please make the build reproducible

2024-02-09 Thread James Addison

Followup-For: Bug #1063542
Description: improve Sphinx documentation reproducibility by preserving 
argument defaults
 The TaskVineManagerConfig dataclass includes an 'address' attribute that
 is set to the value of socket.gethostname() when the class is loaded.
 .
 Meanwhile, the TaskVineExecutor.__init__ method 'manager_config' argument
 has a default value of a no-args constructed TaskVineManagerConfig instance.
 .
 When Sphinx builds documentation, by default it will emit a Python repr() of
 the manager_config argument, causing the hostname of the build host to be
 included.
 .
 We can solve that by instructing the Sphinx autodoc extension to retain the
 textual representation of argument lists as they are found in the source
 code, instead of evaluated and repr'd equivalents.
Author: James Addison 

---
Bug-Debian: https://bugs.debian.org/1063542

--- python-parsl-2023.11.13+ds.orig/docs/conf.py
+++ python-parsl-2023.11.13+ds/docs/conf.py
@@ -363,3 +363,4 @@ autodoc_default_options = {
 'members': True,
 'undoc-members': True
 }
+autodoc_preserve_defaults = True

Bug#1063544: android-platform-external-libunwind: transition from p7zip to 7zip

Source: android-platform-external-libunwind
Version: 10.0.0+r36-4
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972041 is related

Thank you for maintaining software in debian.

Bug#1063543: amavisd-new: transition from p7zip to 7zip

Source: amavisd-new
Version: 1:2.13.0-3
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

2024-02-09 Thread Michael Tokarev


09.02.2024 16:58, ca...@allfreemail.net

Package: console-setup
Followup-For: Bug #1063518

Consider making all scripts provided by console-setup shellcheck-clean, there 
are lots of tiny issues that can turn into big issues under the right 
conditions.


Please do not do this. Shellcheck is a huge problem and we had large amount
of bugs due to people trying to apply its suggestions.  It's very difficult
in many cases to spot why shellcheck is wrong (classic is the suggestion to
put $var into double quotes "$var" which breaks badly if $var is supposed to
contain zero or more separate words - this way, even boot scripts has become
buggy leading to system becoming unbootable).

Shellcheck is a very bad tool.

/mjt

Bug#1063542: python-parsl-doc: please make the build reproducible

2024-02-09 Thread James Addison

Package: python-parsl-doc
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: hostname
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

I'm an occasional volunteer with the Reproducible Builds[1] project, and
recently noticed that the python-parsl-doc package failed to build from source
reproducibly.

The cause is that the hostname of the build host appears in some of the
documentation built by Sphinx and the autodoc extension.  The hostname
is evaluated from a class attribute that calls the Python socket.gethostname
method.

I'll attach a patch momentarily that resolves the problem by enabling the
Sphinx autodoc extension 'autodoc_preserve_defaults' configuration setting[2].
Please note that this does affect other output in the documentation.


In more detail:

The TaskVineManagerConfig dataclass includes an 'address' attribute[3] that
is set to the value of socket.gethostname() when the class is loaded.

Meanwhile, the TaskVineExecutor.__init__ method 'manager_config' argument[4]
has a default value of a no-args constructed TaskVineManagerConfig instance.

When Sphinx builds documentation, by default it will emit a Python repr() of
the manager_config argument, causing the hostname of the build host to be
included.

We can solve that by instructing the Sphinx autodoc extension to retain the
textual representation of argument lists as they are found in the source
code, instead of evaluated and repr'd equivalents.

Regards,
James

[1] - https://reproducible-builds.org/

[2] - 
https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_preserve_defaults

[3] - 
https://sources.debian.org/src/python-parsl/2023.11.13%2Bds-1/parsl/executors/taskvine/manager_config.py/#L151

[4] - 
https://sources.debian.org/src/python-parsl/2023.11.13%2Bds-1/parsl/executors/taskvine/executor.py/#L106

Bug#1063541: acetoneiso: transition from p7zip to 7zip

Source: acetoneiso
Version: 2.4-4
Severity: normal

Dear Maintainer,

your package Depends/Recommends/Suggests or has some other relation to the 
p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in 
debian trixie and will eventually be removed from debian. They have been 
replaced by 7zip and 7zip-rar packages.

If necessary, please modify your package to use the executables from the 7zip 
package instead. If everything everything behaves as expected, then remove 
p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip 
and/or 7zip-rar.

This bug is currently filed with normal priority but the priority will be 
increased as the release date of debian trixie gets closer.

Thank you for maintaining software in debian.

Bug#1063540: libhibernate-validator-java: CVE-2023-1932

Source: libhibernate-validator-java
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for libhibernate-validator-java.

CVE-2023-1932[0]:
rendering of invalid html with SafeHTML leads to HTML injection and XSS

https://bugzilla.redhat.com/show_bug.cgi?id=1809444


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063539: undertow: CVE-2023-4639

Source: undertow
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for undertow.

CVE-2023-4639[0]:
https://bugzilla.redhat.com/show_bug.cgi?id=2166022


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063538: python-multipart: CVE-2024-24762

Source: python-multipart
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for python-multipart.

CVE-2024-24762[0]:
| FastAPI is a web framework for building APIs with Python 3.8+ based
| on standard Python type hints. When using form data, `python-
| multipart` uses a Regular Expression to parse the HTTP `Content-
| Type` header, including options. An attacker could send a custom-
| made `Content-Type` option that is very difficult for the RegEx to
| process, consuming CPU resources and stalling indefinitely (minutes
| or more) while holding the main event loop. This means that process
| can't handle any more requests. It's a ReDoS(Regular expression
| Denial of Service), it only applies to those reading form data,
| using `python-multipart`. This vulnerability has been patched in
| version 0.109.0.

This was reported by fastapi:
https://github.com/tiangolo/fastapi/security/advisories/GHSA-qf9m-vfgh-m389

But the actual code fix within Debian is in python-multipart:
https://github.com/Kludex/python-multipart/commit/20f0ef6b4e4caf7d69a667c54dff57fe467109a4
https://github.com/Kludex/python-multipart/pull/75

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063537: ckeditor3: CVE-2024-24815 CVE-2024-24816

Source: ckeditor3
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerabilities were published for ckeditor3.

CVE-2024-24815[0]:
| CKEditor4 is an open source what-you-see-is-what-you-get HTML
| editor. A cross-site scripting vulnerability has been discovered in
| the core HTML parsing module in versions of CKEditor4 prior to
| 4.24.0-lts. It may affect all editor instances that enabled full-
| page editing mode or enabled CDATA elements in Advanced Content
| Filtering configuration (defaults to `script` and `style` elements).
| The vulnerability allows attackers to inject malformed HTML content
| bypassing Advanced Content Filtering mechanism, which could result
| in executing JavaScript code. An attacker could abuse faulty CDATA
| content detection and use it to prepare an intentional attack on the
| editor. A fix is available in version 4.24.0-lts.

https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-fq6h-4g8v-qqvm
https://github.com/ckeditor/ckeditor4/commit/8ed1a3c93d0ae5f49f4ecff5738ab8a2972194cb

CVE-2024-24816[1]:
| CKEditor4 is an open source what-you-see-is-what-you-get HTML
| editor. A cross-site scripting vulnerability vulnerability has been
| discovered in versions prior to 4.24.0-lts in samples that use the
| `preview` feature. All integrators that use these samples in the
| production code can be affected. The vulnerability allows an
| attacker to execute JavaScript code by abusing the misconfigured
| preview feature. It affects all users using the CKEditor 4 at
| version < 4.24.0-lts with affected samples used in a production
| environment. A fix is available in version 4.24.0-lts.

https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-mw2c-vx6j-mg76
https://github.com/ckeditor/ckeditor4/commit/8ed1a3c93d0ae5f49f4ecff5738ab8a2972194cb


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063536: ckeditor: CVE-2024-24815 CVE-2024-24816

Source: ckeditor
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerabilities were published for ckeditor.

CVE-2024-24815[0]:
| CKEditor4 is an open source what-you-see-is-what-you-get HTML
| editor. A cross-site scripting vulnerability has been discovered in
| the core HTML parsing module in versions of CKEditor4 prior to
| 4.24.0-lts. It may affect all editor instances that enabled full-
| page editing mode or enabled CDATA elements in Advanced Content
| Filtering configuration (defaults to `script` and `style` elements).
| The vulnerability allows attackers to inject malformed HTML content
| bypassing Advanced Content Filtering mechanism, which could result
| in executing JavaScript code. An attacker could abuse faulty CDATA
| content detection and use it to prepare an intentional attack on the
| editor. A fix is available in version 4.24.0-lts.

https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-fq6h-4g8v-qqvm
https://github.com/ckeditor/ckeditor4/commit/8ed1a3c93d0ae5f49f4ecff5738ab8a2972194cb

CVE-2024-24816[1]:
| CKEditor4 is an open source what-you-see-is-what-you-get HTML
| editor. A cross-site scripting vulnerability vulnerability has been
| discovered in versions prior to 4.24.0-lts in samples that use the
| `preview` feature. All integrators that use these samples in the
| production code can be affected. The vulnerability allows an
| attacker to execute JavaScript code by abusing the misconfigured
| preview feature. It affects all users using the CKEditor 4 at
| version < 4.24.0-lts with affected samples used in a production
| environment. A fix is available in version 4.24.0-lts.

https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-mw2c-vx6j-mg76
https://github.com/ckeditor/ckeditor4/commit/8ed1a3c93d0ae5f49f4ecff5738ab8a2972194cb


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063534: libjwt: CVE-2024-25189

Source: libjwt
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for libjwt.

CVE-2024-25189[0]:
| libjwt 1.15.3 uses strcmp (which is not constant time) to verify
| authentication, which makes it easier to bypass authentication via a
| timing side channel.

The report is
https://github.com/P3ngu1nW/CVE_Request/blob/main/benmcollins%3Alibjwt.md
but it doesn't seem to have been reported upstream yet.


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063535: node-ip: CVE-2023-42282

Source: node-ip
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for node-ip.

CVE-2023-42282[0]:
| An issue in NPM IP Package v.1.1.8 and before allows an attacker to
| execute arbitrary code and obtain sensitive information via the
| isPublic() function.

It seems upstream has been unresponsive to the reports:
https://huntr.com/bounties/bfc3b23f-ddc0-4ee7-afab-223b07115ed3/
https://cosmosofcyberspace.github.io/npm_ip_cve/npm_ip_cve.html


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'

Package: console-setup
Followup-For: Bug #1063518

Consider making all scripts provided by console-setup shellcheck-clean, there 
are lots of tiny issues that can turn into big issues under the right 
conditions.

https://tracker.debian.org/pkg/shellcheck

Bug#1063533: Performance with packages with large numbers of tests

2024-02-09 Thread Ian Jackson

Package: autopkgtest
Version: 5.32
Severity: wishlist

tl;dr:

  autopkgtest is slower than it needs to be for packages with many
  tests.  I can see at least one easy opportunity for a potentially
  substantial improvement, and have another more doubtful idea.

Background and factual information:

src:dgit has over a hundred autopkgtests (115 in all right now, but
some don't run in CI due to Restrictions; only 108 run in CI).  This
is convenient for isolating failures.  The tests are grouped into
(currently) 26 stanzas in debian/tests/control.

These tests usually take around 40 minutes to run in a formal run
under autopkgtest.  Sometimes the time taken exceeds the default
1-hour timeout in salsa CI.

Some of the tests are very fast - one or two seconds.  Some take much
longer.

(During a manual run outside autopkgtest, a complete run of the tests
takes about 8 minutes, but that's with CPU parallelism so isn't
comparable.  I haven't done a non-parallel benchmark run.)

Proposal 1:

Observing the logs, I see that even for tests in the same stanza,
autopkgtest prpeares and installs an autopkgtest-satdep package,
between every test.

For short tests, this dominates the execution time.  In the logs eg
 https://salsa.debian.org/dgit-team/dgit/-/jobs/5270905
it seems to take about 6 seconds.

So I think skipping the testbed re-preparation for tests within the
same stanza would save about 6 seconds per such test, or 530-ish
seconds for each run.  Ie, it might cut 20% off the total runtime for
this package.

I'm hoping that this would be relatively straightforward to implement.

Proposal 2:

*Re*installing packages involved with many of the tests seems quite
expensive.  For src:dgit, most of the tests involve installing
dgit.deb.  dgit and its dependencies seem to take about 20s to
install.

If the test stanzas could be sequenced into "chains" where each test
is has a monotonically longer dependency list, the intervening satdep
installation, to get from one test stanza in the chain, to the nest
stanza, wouldn't need to involve *reinstalling* anything.

I'm not sure how much time this would save.  Also it's not clear to me
that this would always be 100% faithful.  After dependency resolution
is not monotonic: an extra dependency might result in *deinstallation*
of packages.

So this proposal is more fanciful but I thought I would share it
anyway.

Regards,c
Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

2024-02-09 Thread Diederik de Haas

On Friday, 9 February 2024 13:39:23 CET Arno Lehmann wrote:
> [Fr Feb  9 13:25:08 2024] CPU: 20 PID: 84300 Comm: kworker/20:0 Not
> tainted 6.5.0-0.deb12.4-amd64 #1  Debian 6.5.10-1~bpo12+1
> [Fr Feb  9 13:25:08 2024] Hardware name: ASUS System Product Name/ROG
> STRIX X670E-A GAMING WIFI, BIOS 1904 01/29/2024

I see you have (now) an up-to-date BIOS. Good.

> [Fr Feb  9 13:25:08 2024] Workqueue: events igc_watchdog_task [igc]
> [Fr Feb  9 13:25:08 2024] RIP: 0010:igc_rd32+0x8d/0xa0 [igc]
> [Fr Feb  9 13:25:08 2024] Code: 48 c7 c6 10 36 3a c0 e8 81 aa dd e6 48
> 8b bb 28 ff ff ff e8 05 12 b4 e6 84 c0 74 bc 89 ee 48 c7 c7 38 36 3a c0
> e8 c3 2e 53 e6 <0f> 0b eb aa b8 ff ff ff ff e9 15 0f 04 e7 0f 1f 44 00
> 00 90 90 90
> [Fr Feb  9 13:25:08 2024] RSP: 0018:b034cc61bdd8 EFLAGS: 00010282
> [Fr Feb  9 13:25:08 2024] RAX:  RBX: 97078f882cb8
> RCX: 0027
> [Fr Feb  9 13:25:08 2024] RDX: 97169e7213c8 RSI: 0001
> RDI: 97169e7213c0
> [Fr Feb  9 13:25:08 2024] RBP: c030 R08: 
> R09: b034cc61bc68
> [Fr Feb  9 13:25:08 2024] R10: 0003 R11: 9716dde3ac28
> R12: 97078f882000
> [Fr Feb  9 13:25:08 2024] R13:  R14: 970784592d40
> R15: c030
> [Fr Feb  9 13:25:08 2024] FS:  ()
> GS:97169e70() knlGS:
> [Fr Feb  9 13:25:08 2024] CS:  0010 DS:  ES:  CR0: 80050033
> [Fr Feb  9 13:25:08 2024] CR2: 7f5271155f80 CR3: 000434bc6000
> CR4: 00750ee0
> [Fr Feb  9 13:25:08 2024] PKRU: 5554
> [Fr Feb  9 13:25:08 2024] Call Trace:
> [Fr Feb  9 13:25:08 2024]  
> [Fr Feb  9 13:25:08 2024]  ? igc_rd32+0x8d/0xa0 [igc]
> [Fr Feb  9 13:25:08 2024]  ? __warn+0x81/0x130
> [Fr Feb  9 13:25:08 2024]  ? igc_rd32+0x8d/0xa0 [igc]
> [Fr Feb  9 13:25:08 2024]  ? report_bug+0x171/0x1a0
> [Fr Feb  9 13:25:08 2024]  ? srso_alias_return_thunk+0x5/0x7f
> [Fr Feb  9 13:25:08 2024]  ? prb_read_valid+0x1b/0x30
> [Fr Feb  9 13:25:08 2024]  ? handle_bug+0x41/0x70
> [Fr Feb  9 13:25:08 2024]  ? exc_invalid_op+0x17/0x70
> [Fr Feb  9 13:25:08 2024]  ? asm_exc_invalid_op+0x1a/0x20
> [Fr Feb  9 13:25:08 2024]  ? igc_rd32+0x8d/0xa0 [igc]
> [Fr Feb  9 13:25:08 2024]  ? igc_rd32+0x8d/0xa0 [igc]
> [Fr Feb  9 13:25:08 2024]  igc_update_stats+0x8a/0x6d0 [igc]
> [Fr Feb  9 13:25:08 2024]  igc_watchdog_task+0x9d/0x4a0 [igc]
> [Fr Feb  9 13:25:08 2024]  process_one_work+0x1df/0x3e0
> [Fr Feb  9 13:25:08 2024]  worker_thread+0x51/0x390
> [Fr Feb  9 13:25:08 2024]  ? __pfx_worker_thread+0x10/0x10
> [Fr Feb  9 13:25:08 2024]  kthread+0xe5/0x120
> [Fr Feb  9 13:25:08 2024]  ? __pfx_kthread+0x10/0x10
> [Fr Feb  9 13:25:08 2024]  ret_from_fork+0x31/0x50
> [Fr Feb  9 13:25:08 2024]  ? __pfx_kthread+0x10/0x10
> [Fr Feb  9 13:25:08 2024]  ret_from_fork_asm+0x1b/0x30
> [Fr Feb  9 13:25:08 2024]  
> [Fr Feb  9 13:25:08 2024] ---[ end trace  ]---
>
> Can anybody suggest what information I can provide to tackle this?

I think it's best to take this issue upstream.

$ scripts/get_maintainer.pl drivers/net/ethernet/intel/igc/ returned this:
Jesse Brandeburg  (supporter:INTEL ETHERNET DRIVERS)
Tony Nguyen  (supporter:INTEL ETHERNET DRIVERS)
"David S. Miller"  (maintainer:NETWORKING DRIVERS)
Eric Dumazet  (maintainer:NETWORKING DRIVERS)
Jakub Kicinski  (maintainer:NETWORKING DRIVERS)
Paolo Abeni  (maintainer:NETWORKING DRIVERS)
intel-wired-...@lists.osuosl.org (moderated list:INTEL ETHERNET DRIVERS)
net...@vger.kernel.org (open list:NETWORKING DRIVERS)
linux-ker...@vger.kernel.org (open list)

To do that, I'd certainly send an email to net...@vger.kernel.org as that is
the Mailing List. You can choose to add others from that list too.
In that email I recommend to include the following info:
- Description of the problems: I'd focus on the NIC stuff, but do also mention
  the issue you encountered with NVMe.
- A list or table with the kernel versions you detected the problem with. 
  Try to find/use the upstream version as the Debian version (6.1.0-17) is
  often not (that) useful for the upstream maintainers. `uname -a` will show
  both. Via https://tracker.debian.org/pkg/linux I found that 6.1.0-17 is
  upstream version 6.1.69 as the 6.1.69-1 upload had "Bump ABI to 17" at the
  end of the changelog.
  IIUC this is not a regression; mention that too.
- A/The stacktrace(s) you got. This usually allows the upstream maintainers
  to pinpoint where the problem lies.

HTH

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

Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

2024-02-09 Thread Pirate Praveen


Control: severity -1 important

On 9/2/24 6:48 PM, Pirate Praveen wrote:
Without libjs-underscore in build depends, the test should fail, but it 
is passing.


ruby-rails-assets-underscore source package includes underscore.js and 
it is replaced by symlink to libjs-underscore only in dh_install stage 
so rake assets:precompile can still find it.


So it looks like gem2deb test is working as expected, but we still need 
to figure out a way out for symlinks. May be we should just link them in 
the build target itself as a solution. If that is the recommended 
solution, we can close this bug with a note in dh_ruby documentation.

Bug#1063532: ITP: ford -- Fortran Documentation tool

2024-02-09 Thread Alastair McKinstry

Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org

* Package name: ford
  Version : 7.0.5
  Upstream Contact: Christopher MacMackin 
* URL : https://github.com/Fortran-FOSS-Programmers/ford
* License : GPL
  Programming Lang: Python
  Description : Fortran Documentation tool

The goal of FORD is to be able to reliably produce documentation for modern
Fortran software which is informative and nice to look at. The documentation
should be easy to write and non-obtrusive within the code. While it will never
be as feature-rich as Doxygen, hopefully FORD will be able to provide a good
alternative for documenting Fortran projects.

Ford is already used (if present) by several projects packaged in Debian.

I intend to manage it in Salsa; perhaps in Debian-Science team.

Bug#1063530: node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1

2024-02-09 Thread Dylan Aïssi

Source: node-undici
Version:  5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3
Severity: serious
Tags: bookworm
Usertags: apertis-ftbfs
Justification: FTBFS

Hello,

While doing a rebuild of some node packages in Bookworm, it appears several
packages (at least ~ 50 pkgs) no longer build with nodejs 18.19.0+dfsg-6~deb12u1
(from bookworm-security repo) while they still successfully build with nodejs
18.13.0+dfsg1-1 (from the main bookworm repo). They all fail with the
same error:
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

Since, I am not sure which package need to be fixed (nodejs, node-undici or
all of them), I fill this bug against the package referred by the error message,
please reassign to the relevent package.

Below is the relevant part of the log:

   dh_auto_build --buildsystem=nodejs
Found debian/nodejs/additional_components
Adding component(s): types
/!\ types/package.json not found
/!\ types/package.json not found
Unable to load types
No build command found, searching known files
Found debian/nodejs/llparse-builder/build
cd ./llparse-builder && sh -ex ../debian/nodejs/llparse-builder/build
+ tsc
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:325:84 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

325 type _Request = typeof globalThis extends { onmessage: any
} ? {} : import("undici-types").Request;

~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:326:85 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

326 type _Response = typeof globalThis extends { onmessage:
any } ? {} : import("undici-types").Response;

 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:327:85 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

327 type _FormData = typeof globalThis extends { onmessage:
any } ? {} : import("undici-types").FormData;

 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:328:84 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

328 type _Headers = typeof globalThis extends { onmessage: any
} ? {} : import("undici-types").Headers;

~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:330:22 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

330 : import("undici-types").RequestInit;
 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:336:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

336 type RequestInfo = import("undici-types").RequestInfo;
  ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:337:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

337 type HeadersInit = import("undici-types").HeadersInit;
  ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:338:32 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

338 type BodyInit = import("undici-types").BodyInit;
   ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:339:39 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

339 type RequestRedirect = import("undici-types").RequestRedirect;
  ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:340:42 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

340 type RequestCredentials = import("undici-types").RequestCredentials;
 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:341:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

341 type RequestMode = import("undici-types").RequestMode;
  ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:342:38 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

342 type ReferrerPolicy = import("undici-types").ReferrerPolicy;
 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:343:34 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.

343 type Dispatcher = import("undici-types").Dispatcher;
 ~~

../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:344:37 -
error TS2307: Cannot find module

Bug#1063531: RFS: mplayer/2:1.5+svn38446-2 -- movie player for Unix-like systems

2024-02-09 Thread Lorenzo

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "mplayer":

 * Package name : mplayer
   Version  : 2:1.5+svn38446-2
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://mplayerhq.hu
 * License  : LGPL-2.1+, Expat, ISC, public-domain-tom, GPL-2+,
   BSD-2-Clause, other-2, other-1
 * Vcs  : https://salsa.debian.org/multimedia-team/mplayer
   Section  : video

The source builds the following binary packages:

  mplayer-gui - movie player for Unix-like systems (GUI variant)
  mencoder - MPlayer's Movie Encoder
  mplayer - movie player for Unix-like systems
  mplayer-doc - documentation for MPlayer

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/mplayer/

Alternatively, you can download the package with 'dget' using this
command:

  dget -x
  
https://mentors.debian.net/debian/pool/main/m/mplayer/mplayer_1.5+svn38446-2.dsc

Git repo:

  https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=heads

Changes since the last upload:

 mplayer (2:1.5+svn38446-2) unstable; urgency=medium
 .
   * build a noaltivec variant of mplayer for powerpc
   * install alternatives for mplayer-altivec and
  mplayer-noaltivec on powerpc; the altivec
  variant has the highest priority (Closes: #410962)
   * d/control: B-D:
   - add dh-exec
   - replace obsolete pkg-config with pkgconf

Regards,
Lorenzo

Bug#1052455: RE: freetype 2.12.1+dfsg-5+deb12u1 makes chromium segfault at startup

2024-02-09 Thread Hugh McMaster

Hi Jonathan,

On Wed, 7 Feb 2024 at 04:47, Jonathan Wiltshire wrote:

> What's your plan at this point? We have skipped this update in two point
> releases now and it needs a resolution.

Thanks for following up. I’d actually forgotten about this.

I’d still like to disable the incomplete and incompatible COLRv1 support in
Bookworm’s FreeType library.

The additional patch Ben Wagner identified is required.

Chromium seems to have fixed the bug we encountered last year, as I tested
a build of FreeType as originally submitted and had no issues.

To avoid any surprises though, we should add the extra patch.

When is the next point release scheduled for?

Hugh

>

Bug#1063529: wdiff: broken when the input contains a null character

2024-02-09 Thread Vincent Lefevre

Package: wdiff
Version: 1.2.2-6
Severity: normal

wdiff is broken when the input contains a null character.
For instance, create 2 files a and b with

  printf "a\n2\n3\n4\n5\n6\n7\n8\n" > a
  printf "b\n2\n3\n4\n5\n6\n7\n8\n\000\n" > b

$ wdiff a b
b
2
3
4
5
6
7
8

instead of something like

[-a-]{+b+}
2
3
4
5
6
7
8
{+^@+}

Similarly, the following is incorrect:

$ diff -au a b | wdiff -d
++ b2024-02-09 14:11:23.981863795 +0100
@@ -1,4 +1,4 @@
b
2
3
4
@@ -6,3 +6,4 @@
6
7
8

There is no such issue if I replace \000 by \001.
So this is specific to the null character.

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

Kernel: Linux 6.6.13-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wdiff depends on:
ii  libc6  2.37-15
ii  libtinfo6  6.4+20240113-1

wdiff recommends no packages.

Versions of packages wdiff suggests:
ii  wdiff-doc  1.2.2-6

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

2024-02-09 Thread Pirate Praveen


Control: severity -1 serious

On Fri, 9 Feb 2024 00:30:03 +0530 Pirate Praveen 
 wrote:
For majority of packages that wraps javascript assets, the actual assets 
are shipped in a libjs-* package and ruby-* package only include a 
symbolic link.


Testing further with ruby-rails-assets-underscore, the test is passing 
even with a broken symbolic link.


Try building master branch which has this commit
https://salsa.debian.org/ruby-team/ruby-rails-assets-underscore/-/commit/194c526208b3be29870f745d9ac0bfbc9af6d66c

Without libjs-underscore in build depends, the test should fail, but it 
is passing.

Bug#1063528: calling less PAGER a second time after resizing the terminal does not use new size

2024-02-09 Thread VA


Package: ipython3
Version: 8.20.0-1

- Start with a 80x24 terminal
- Set "export PAGER=less"
- Open "ipython3"
- Run "import os"
- Run "os??"
- Press "q" to quit pager
- Maximize terminal window
- Run again "os??"
- Scroll view with pagedown/pageup

With xterm, the text scrolled is clipped into a 80x24 area in the 
top-left area corner, which is suboptimal.


With several libvte-based terminals, scrolling down displays a new 80x24 
page of the text but below the previous page. Scrolling up does very 
confusing things, which is worse.

Bug#1063527: einsteinpy: test_plotting fails to converge with scipy 1.11

2024-02-09 Thread Drew Parsons

Source: einsteinpy
Version: 0.4.0-3
Severity: important
Control: block 1061605 by -1

einsteinpy is failing test_plotting with scipy 1.11 from experimental

143s if disp:
143s msg = ("Failed to converge after %d iterations, value is %s."
143s% (itr + 1, p))
143s >   raise RuntimeError(msg)
143s E   RuntimeError: Failed to converge after 50 iterations, value is 
nan.
143s 
143s /usr/lib/python3/dist-packages/scipy/optimize/_zeros_py.py:381: 
RuntimeError
143s __ ERROR at setup of test_plot_calls_plt_plot 
__

likewise test_plotter_has_correct_attributes
 
scipy 1.11 is currently in experimental but I'd like to upload soon to
unstable to resolve Bug#1061605, which would make this bug serious.

Bug#1063526: astroml: test_iterative_PCA fails with scipy 1.11: unexpected keyword argument 'sym_pos'

2024-02-09 Thread Drew Parsons

Source: astroml
Version: 1.0.2-2
Severity: important
Control: block 1061605 by -1

astroml is failing test_iterative_PCA with scipy 1.11 from experimental

 82s for i in range(n_samples):
 82s VWV = np.dot(VT[:n_ev], (notM[i] * VT[:n_ev]).T)
 82s >   coeffs[i] = solve(VWV, VWx[:, i], sym_pos=True, 
overwrite_a=True)
 82s E   TypeError: solve() got an unexpected keyword argument 
'sym_pos'
 82s 
 82s 
/usr/lib/python3/dist-packages/astroML/dimensionality/iterative_pca.py:127: 
TypeError
 
>From the error description it's probably easy to fix, just need to
work out what is going on with the sym_pos argument.
 
scipy 1.11 is currently in experimental but I'd like to upload soon to
unstable to resolve Bug#1061605, which would make this bug serious.

Bug#958587: lockdown FTBFS due to B-D: dh-systemd

Control: retitle -1 lockdown FTBFS: Build-Depends on deprecated dh-systemd 
which is no longer available
Control: tags -1 + ftbfs

This bug has become a FTBFS. Tagging as such.

Helmut

Bug#1063525: d-spy FTBFS with nocheck profile: ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable

Source: d-spy
Version: 1.8.0-1
Severity: serious
Tags: ftbfs trixie sid

d-spy fails to build from source when built with the nocheck build
profile. Since trixie such a failure is considered release-critical. A
build ends with:

| ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or 
not executable
| dh_auto_configure: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 
returned exit code 1
| make: *** [debian/rules:8: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#1027889: use of dh_dkms without b-d: dh-dkms is a FTBFS

Control: retitle -1 kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or 
dh-dkms)
Control: tags -1 + ftbfs

Using dh_dkms without Build-Depends: dh-dkms makes the package ftbfs:

| make[1]: dh_dkms: No such file or directory
| make[1]: *** [debian/rules:23: override_dh_install] Error 127
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:11: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Andreas filed the bug at serious severity, but it doesn't yet correctly
identify as FTBFS.

Helmut

Bug#1063524: brltty: move aliased files to /usr (DEP17)

Source: brltty
Version: 6.6-4
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

we want to finalize the /usr-merge transition by moving all files to
/usr via DEP17 and thus remove practical problems arising from aliasing.
brltty is involved, because it installs various files in aliased
locations and it cannot be moved by enabling the dh-sequence-movetousr
addon as it does not use dh. In order to move this forward efficiently,
I have prepared a patch to manually perform the move. Note that this
patch must not be uploaded to bookworm-backports or earlier. If you wish
to continue backporting, you may defer applying this patch or add a
manual dh_movetousr call before dh_installdeb. Please ensure that files
are moved before trixie's toolchain freeze though.

Helmut
diff --minimal -Nru brltty-6.6/debian/brltty-espeak.dirs 
brltty-6.6/debian/brltty-espeak.dirs
--- brltty-6.6/debian/brltty-espeak.dirs2021-01-28 17:18:34.0 
+0100
+++ brltty-6.6/debian/brltty-espeak.dirs2024-02-08 17:59:12.0 
+0100
@@ -1,2 +1,2 @@
-lib/brltty
+usr/lib/brltty
 
diff --minimal -Nru brltty-6.6/debian/brltty-flite.dirs 
brltty-6.6/debian/brltty-flite.dirs
--- brltty-6.6/debian/brltty-flite.dirs 2021-01-28 17:18:34.0 +0100
+++ brltty-6.6/debian/brltty-flite.dirs 2024-02-08 17:59:12.0 +0100
@@ -1,2 +1,2 @@
-lib/brltty
+usr/lib/brltty
 
diff --minimal -Nru brltty-6.6/debian/brltty-speechd.dirs 
brltty-6.6/debian/brltty-speechd.dirs
--- brltty-6.6/debian/brltty-speechd.dirs   2021-01-28 17:18:34.0 
+0100
+++ brltty-6.6/debian/brltty-speechd.dirs   2024-02-08 17:59:12.0 
+0100
@@ -1,2 +1,2 @@
-lib/brltty
+usr/lib/brltty
 
diff --minimal -Nru brltty-6.6/debian/brltty-udeb.dirs 
brltty-6.6/debian/brltty-udeb.dirs
--- brltty-6.6/debian/brltty-udeb.dirs  2021-01-28 17:18:34.0 +0100
+++ brltty-6.6/debian/brltty-udeb.dirs  2024-02-08 17:59:12.0 +0100
@@ -1,7 +1,7 @@
 etc/brltty
-lib/udev/rules.d
-lib/brltty
-lib/debian-installer.d
-lib/debian-installer-startup.d
-lib/udev
+usr/lib/udev/rules.d
+usr/lib/brltty
+usr/lib/debian-installer.d
+usr/lib/debian-installer-startup.d
+usr/lib/udev
 usr/lib/finish-install.d
diff --minimal -Nru brltty-6.6/debian/brltty-x11.dirs 
brltty-6.6/debian/brltty-x11.dirs
--- brltty-6.6/debian/brltty-x11.dirs   2021-01-28 17:18:34.0 +0100
+++ brltty-6.6/debian/brltty-x11.dirs   2024-02-08 17:59:12.0 +0100
@@ -1,2 +1,2 @@
 etc/brltty
-lib/brltty
+usr/lib/brltty
diff --minimal -Nru brltty-6.6/debian/brltty.dirs brltty-6.6/debian/brltty.dirs
--- brltty-6.6/debian/brltty.dirs   2021-01-28 17:18:34.0 +0100
+++ brltty-6.6/debian/brltty.dirs   2024-02-08 17:59:12.0 +0100
@@ -1,4 +1,4 @@
 etc/brltty
-lib/brltty
+usr/lib/brltty
 usr/share/initramfs-tools/hooks
 usr/share/initramfs-tools/scripts/init-premount
diff --minimal -Nru brltty-6.6/debian/brltty.install 
brltty-6.6/debian/brltty.install
--- brltty-6.6/debian/brltty.install2022-06-18 09:31:08.0 +0200
+++ brltty-6.6/debian/brltty.install2024-02-08 17:59:12.0 +0100
@@ -1,18 +1,18 @@
 debian/tmp/etc/brltty etc
-debian/tmp/bin/brltty bin
-debian/tmp/bin/eutp usr/bin
-debian/tmp/bin/vstp usr/bin
-debian/tmp/bin/brltty-atb usr/bin
-debian/tmp/bin/brltty-ctb usr/bin
-debian/tmp/bin/brltty-ktb usr/bin
-debian/tmp/bin/brltty-ttb usr/bin
-debian/tmp/bin/brltty-trtxt usr/bin
-debian/tmp/bin/brltty-clip usr/bin
-debian/tmp/bin/brltty-hid usr/bin
-debian/tmp/bin/brltty-lscmds usr/bin
-debian/tmp/bin/brltty-morse usr/bin
-debian/tmp/bin/brltty-tune usr/bin
-debian/tmp/lib/brltty lib
+debian/tmp/usr/bin/brltty usr/bin
+debian/tmp/usr/bin/eutp usr/bin
+debian/tmp/usr/bin/vstp usr/bin
+debian/tmp/usr/bin/brltty-atb usr/bin
+debian/tmp/usr/bin/brltty-ctb usr/bin
+debian/tmp/usr/bin/brltty-ktb usr/bin
+debian/tmp/usr/bin/brltty-ttb usr/bin
+debian/tmp/usr/bin/brltty-trtxt usr/bin
+debian/tmp/usr/bin/brltty-clip usr/bin
+debian/tmp/usr/bin/brltty-hid usr/bin
+debian/tmp/usr/bin/brltty-lscmds usr/bin
+debian/tmp/usr/bin/brltty-morse usr/bin
+debian/tmp/usr/bin/brltty-tune usr/bin
+debian/tmp/usr/lib/brltty usr/lib
 debian/tmp/usr/share/locale
 debian/initramfs/hooks/brltty usr/share/initramfs-tools/hooks
 debian/initramfs/scripts/init-premount/brltty 
usr/share/initramfs-tools/scripts/init-premount
diff --minimal -Nru brltty-6.6/debian/brltty.links 
brltty-6.6/debian/brltty.links
--- brltty-6.6/debian/brltty.links  2021-01-28 17:18:34.0 +0100
+++ brltty-6.6/debian/brltty.links  2024-02-08 17:59:12.0 +0100
@@ -1 +1 @@
-/bin/brltty /sbin/brltty
+/usr/bin/brltty /usr/sbin/brltty
diff --minimal -Nru brltty-6.6/debian/changelog brltty-6.6/debian/changelog
--- brltty-6.6/debian/changelog 2023-09-05 00:11:56.0 +0200
+++ brltty-6.6/debian/changelog 2024-02-08 17:59:12.0 +0100
@@ -1,3 +1,10 @@
+brltty (6.6-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * DEP17: Move files to /usr.

Bug#1063523: duo-unix FTCBFS: uses AC_RUN_IFELSE