Bug#1041590: nvidia-installer-cleanup install fail

[Terrance Hendrik]

Package: nvidia-installer-cleanup
Version: 20220217+3
system info
```
$ uname-a
Linux  6.3.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.11-1
(2023-07-01) x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie
```

steps to represent

```
# apt install nvidia-installer-cleanup
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  nvidia-installer-cleanup
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/13.3 kB of archives.
After this operation, 48.1 kB of additional disk space will be used.
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package nvidia-installer-cleanup.
(Reading database ... 421224 files and directories currently installed.)
Preparing to unpack .../nvidia-installer-cleanup_20220217+3_amd64.deb ...
Unpacking nvidia-installer-cleanup (20220217+3) ...
Setting up nvidia-installer-cleanup (20220217+3) ...
dpkg: error processing package nvidia-installer-cleanup (--configure):
 installed nvidia-installer-cleanup package post-installation script
subprocess returned error exit status 30
Errors were encountered while processing:
 nvidia-installer-cleanup
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

perl trace log in the attachment.

Thanks!

Bug#1041588: grep -r fails with "Operation not supported"

[Santiago Ruano Rincón]

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

El 21/07/23 a las 04:06, Vincent Lefevre escribió:
> On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> > There is a major regression in grep 3.11-1: I now get an error
> > 
> > cventin:~/Mail> grep -r xxxyyyzzz oldarc
> > grep: oldarc/cur: Operation not supported
> 
> And no such issue with grep from the upstream git.

How are you compiling it? My intuition is this comes from gnulib. But a
reproducer is needed to confirm.

Tagging with moreinfo, and downgrading the severity since I cannot
reproduce it myself:

santiago@novelo ~/C/Riseup> grep -r xxxyyyzzz INBOX/
INBOX/new/1689905669.3476970_3.novelo,U=46874:2,:cventin:~/Mail> grep -r 
xxxyyyzzz oldarc
INBOX/cur/1689905669.3476970_5.novelo,U=46876:2,S:> cventin:~/Mail> grep -r 
xxxyyyzzz oldarc

Please, feel free to bump the severity back again if you are able to
find out a way to reproduce it.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1041588: grep -r fails with "Operation not supported"

[Vincent Lefevre]

On 2023-07-21 04:06:51 +0200, Vincent Lefevre wrote:
> On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> > There is a major regression in grep 3.11-1: I now get an error
> > 
> > cventin:~/Mail> grep -r xxxyyyzzz oldarc
> > grep: oldarc/cur: Operation not supported
> 
> And no such issue with grep from the upstream git.

Well, if I recompile from f951840aa510277fe48e5f2579a98f517246ea86
(tag: v3.11), I can reproduce the error.

The error disappears with

commit 6980733869e8a0311c7eb26cb554dde6a1c26b5b
Author: Jim Meyering 
Date:   2023-06-25 02:28:15 +0200

build: update gnulib to latest

So this is a bug in gnulib.

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

Bug#1041588: grep -r fails with "Operation not supported"

[Vincent Lefevre]

On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> There is a major regression in grep 3.11-1: I now get an error
> 
> cventin:~/Mail> grep -r xxxyyyzzz oldarc
> grep: oldarc/cur: Operation not supported

And no such issue with grep from the upstream git.

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

Bug#1041589: select-editor.1: some remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

Package: sensible-utils
Version: 0.0.20
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and editorial fixes for the man page.

The patch is in the attachment.

-.-.

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"echo .kern 0 | groff -man -Z - " instead of "nroff -man"

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual, the following
must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint select-editor.1":

mandoc: select-editor.1:7:2: WARNING: skipping paragraph macro: br at the end 
of SH
mandoc: select-editor.1:10:104: STYLE: input text line longer than 80 bytes: 
provides a coherent ...
mandoc: select-editor.1:11:92: STYLE: input text line longer than 80 bytes: It 
lists the availab...
mandoc: select-editor.1:12:102: STYLE: input text line longer than 80 bytes: 
The results are stor...
mandoc: select-editor.1:15:86: STYLE: input text line longer than 80 bytes: 
SELECTED_EDITOR vari...

-.-.

Increase type size of ~ (tilde) to make it more visible
in the output of "troff".

12:The results are stored as SELECTED_EDITOR variable in ~/.selected_editor, 
which is sourced and used by

-.-.

Use the correct macro for the font change of a single argument or
split the argument into two.

6:.BR select-editor
9:.BR select-editor
17:.BR select-editor

-.-.

Split lines longer than 100 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

select-editor.1: line 10length 104
provides a coherent mechanism for selecting and storing a preferred 
sensible-editor on a per-user basis.

select-editor.1: line 12length 102
The results are stored as SELECTED_EDITOR variable in ~/.selected_editor, which 
is sourced and used by


-.-.

Prohibit hyphenation of "~/.selected_editor" and "SELECTED_EDITOR" by
using '\%' in front of the words.

-.-.

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

Kernel: Linux 6.3.7-1 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information
--- select-editor.1 2023-07-21 01:08:47.0 +
+++ select-editor.1.new 2023-07-21 01:31:10.0 +
@@ -3,18 +3,21 @@
 .SH NAME
 select-editor \- select your default sensible-editor from all installed editors
 .SH SYNOPSIS
-.BR select-editor
-.br
+.B select-editor
 .SH DESCRIPTION
-.BR select-editor
-provides a coherent mechanism for selecting and storing a preferred 
sensible-editor on a per-user basis.
-It lists the available editors on a system and interactively prompts the user 
to select one.
-The results are stored as SELECTED_EDITOR variable in ~/.selected_editor, 
which is sourced and used by
+.B select-editor
+provides a coherent mechanism for selecting and storing a preferred
+sensible-editor on a per-user basis.
+It lists the available editors on a system and interactively prompts
+the user to select one.
+The results are stored as SELECTED_EDITOR variable in 
\%\s+3~\s-3/.selected_editor,
+which is sourced and used by
 .B sensible-editor
 command.
-SELECTED_EDITOR variable is overridden by the VISUAL and EDITOR environment 
variables.
+\%SELECTED_EDITOR variable is overridden by the VISUAL and EDITOR
+environment variables.
 .SH AUTHOR
-.BR select-editor
+.B select-editor
 was written by Dustin Kirkland .
 .SH "SEE ALSO"
 .BR sensible-editor (1)

Bug#1017564: (no subject)

[Daniel Swarbrick]

Snipping the test failure output from the build log so it does not get 
archived:


--- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims (0.00s)
    --- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims/static (0.01s)
    --- PASS: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/custom_nbf_leeway_using_exp_with_no_clock_skew_leeway 
(0.02s)
    --- PASS: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_auto_clock_skew_leeway 
(0.02s)
    --- PASS: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/auto_nbf_leeway_using_exp_with_custom_clock_skew_leeway 
(0.02s)
    --- PASS: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/no_nbf_leeway_using_iat_with_auto_clock_skew_leeway 
(0.02s)
    --- FAIL: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_no_clock_skew_leeway_with_default_leeway 
(0.02s)
    --- FAIL: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_no_clock_skew_leeway 
(0.02s)
    --- FAIL: 
TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_auto_nbf_leeway_using_exp_with_no_clock_skew_leeway 
(0.02s)


These look quite likely to be timing-sensitive tests, which are often a 
headache on Debian CI.


I have just uploaded consul 1.9.17+dfsg2-1 and as of now, it builds 
successfully on armel. That does not rule out the possibility however 
that these are intermittent test failures.




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041588: grep -r fails with "Operation not supported"

[Vincent Lefevre]

Package: grep
Version: 3.11-1
Severity: grave
Justification: renders package unusable

There is a major regression in grep 3.11-1: I now get an error

cventin:~/Mail> grep -r xxxyyyzzz oldarc
grep: oldarc/cur: Operation not supported

This is just a big maildir mailbox (195700 messages).

The strace output has

[...]
81082 openat(5, "1511962287.17728_1395.cventin:2,S", 
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW) = 6
81082 newfstatat(6, "", {st_mode=S_IFREG|0600, st_size=1171, ...}, 
AT_EMPTY_PATH) = 0
81082 read(6, "Return-Path:  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1022006: Info received (Bug#1022006: Acknowledgement (New version fixes a warning))

[Bjarni Ingi Gislason]

  This was a one time without the similar output in the first e-mail. 
So the behaviour is unchanged.  Happens after this sequence of commands:

xinit &
firefox-esr
einstein
exit (from einstein)
exit (from twm)
[pushing the return key returns to the shell]

Bug#1041587: sensible-browser.1: some remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

Package: sensible-utils
Version: 0.0.20
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and editorial fixes for the man page.

The patch is in the attachment.

-.-.

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"echo '.kern 0' | groff -man -Z -" instead of "nroff -man"

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual, the following
must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint sensible-browser.1":

mandoc: sensible-browser.1:7:2: WARNING: skipping paragraph macro: br at the 
end of SH
mandoc: sensible-browser.1:15:57: STYLE: whitespace at end of input line

-.-.

Input file is sensible-browser.1

Remove space characters at the end of lines.

Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

15:Any string acceptable as a command_string operand to the 

-.-.

Use the correct macro for the font change of a single argument or
split the argument into two.

9:.BR sensible-browser

-.-.

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

16:.B sh -c

-.-.

[ "test-groff" is a developmental version of "groff" ]

Input file is ./sensible-browser.1

Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z 
-rCHECKSTYLE=0":

troff: backtrace: file '':15
troff::15: warning: trailing space in the line

-.-.



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

Kernel: Linux 6.3.7-1 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information
--- sensible-browser.1  2023-07-20 21:31:57.0 +
+++ sensible-browser.1.new  2023-07-20 21:37:36.0 +
@@ -4,16 +4,15 @@
 sensible-browser \- sensible web browsing
 .SH SYNOPSIS
 .BR sensible-browser " url"
-.br
 .SH DESCRIPTION
-.BR sensible-browser
+.B sensible-browser
 makes sensible decisions on which web browser to call.
 Programs in Debian can use this script
 as their default web browser or emulate their behavior.
 .br
 BROWSER environment variable could be set, and will be used if set.
-Any string acceptable as a command_string operand to the 
-.B sh -c
+Any string acceptable as a command_string operand to the
+.B sh \-c
 command shall be valid.
 .SH "STANDARD"
 Documentation of behavior of sensible-utils under a debian system is available 
under

Bug#1041586: src:pyethash: Migrate away from obsolete ‘distutils’

[Ben Finney]

Source: pyethash
Version: 0.1.27-2
Severity: important
Tags: upstream
Forwarded: https://github.com/ethereum/ethash/issues/141

The upstream source uses the Python ‘distutils’ module.

In Python 3.10 and 3.11, Distutils has been formally marked as deprecated.
Code that imports ‘distutils’ will no longer work from Python 3.12.

The upstream source needs to migrate to modern Python build tools.

-- 
 \  “If you don't fail at least 90 percent of the time, you're not |
  `\aiming high enough.” —Alan Kay |
_o__)  |
Ben Finney 

signature.asc
Description: PGP signature

Bug#1041295: smartd.conf.5: some remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

On Mon, Jul 17, 2023 at 09:45:17AM +0200, Bruce Allen wrote:
> Dear Bjarni,
> 
> thanks very much for the corrections/patches to the man pages.
> 
> I reviewed the diff and it looks good.  Something I was wondering: why are
> you inserting the zero width characters '\&' in various places?  I thought
> that there were only needed to avoid an input sequence being misinterpreted
> as a control character.  But in many places where you have inserted it, I
> did not realize that this was a possibility.
> 
  '\&' is, with the current layout of the source text, unnecessary,
but the position of the words can later change.
  So using '\&' is just a measure in advance.

  My explanation was:

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line
(by splitting the line into more lines).

  Can you suggest a better explanation?

  Maybe I should add after the sentence in parentheses:

"by reflowing, reorganising, reformatting the source text."

Extreme case: each word in a textual line is put in a separate line.

Bug#1037878: Processed: tagging 1037878

[Thomas Preud'homme]

Unfortunately I won't be able to do it until August but anyone feel free to do 
an NMU.

My apologies. Best regards,
Thomas

On 21 July 2023 07:04:57 GMT+08:00, alpha_one_x86 
 wrote:
>Fixed into the last version, please update to Ultracopier 2.2.6.7

Bug#1033385: The proposed patch works

[Karine Crèvecœur]

Hi,

I have encoutered the same bug. When playing a video with mpv, mplayer
or vlc, switching to another windows while in fullscreen leads to crash
of openbox.

So, I have tested the proposed path. It works perfectly. Thanks to
Aaron.

I use debian/sid. apt policy libglib2.0-0 returns:

libglib2.0-0:
  Installed: 2.76.4-3
  Candidate: 2.76.4-3
  Version table:
 *** 2.76.4-3 900
900 https://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
 2.76.4-1 100
100 https://deb.debian.org/debian rc-buggy/main amd64 Packages


openbox version I use is 3.6.1-10.

--
Karine Crèvecœur

Bug#1041487: RFS: gnss-sdr/0.0.18-2 [RC] [Team] -- Global navigation satellite systems software defined receiver

[Bo YU]

Hi!
>This was sponsored.

Maybe I am missing something here.

Where to find the new verison uploaded about the package?
https://tracker.debian.org/pkg/gnss-sdr

BR,
Bo

Bug#1037878: Processed: tagging 1037878

[alpha_one_x86]

Fixed into the last version, please update to Ultracopier 2.2.6.7

Bug#1041581: gnome-shell-extension-top-icons-plus: needs update for GNOME Shell 44

[Simon McVittie]

Control: tags -1 + wontfix

On Thu, 20 Jul 2023 at 23:39:15 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44.

It's dead upstream, and the version in Bookworm has a Recommends on
a replacement, so I've asked for removal and I don't plan to work on
solving this.

smcv

Bug#1041585: RM: gnome-shell-extension-top-icons-plus -- ROM; unmaintained upstream, superseded by g-s-e-appindicator

[Simon McVittie]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: gnome-shell-extension-top-icons-p...@packages.debian.org
Control: affects -1 + src:gnome-shell-extension-top-icons-plus

The "Top Icons Plus" extension for GNOME Shell is unmaintained upstream
and has been for some time. I think instead of looking at whether it can
be made compatible with Shell 44, it's time to remove it.

The version in bookworm already Recommends the suggested replacement,
gnome-shell-extension-appindicator (which is why I wanted to keep it alive
until bookworm, to give users an exit strategy).

Thanks,
smcv

Bug#1041564: lios: missing dependency 'speech-dispatcher'

[Boruch Baum]

Hi Samuel, I appreciate the quick response. Like I mentioned. I did get
lios working by installing the dependency. Fortunately, my terminal
emulator was still open and had what you asked for in its scroll-back,
so here's the python traceback:


$ lios
/usr/lib/python3/dist-packages/lios/ui/gtk/print_dialog.py:26: PyGIWarning: 
PangoCairo was imported without specifying a version first. Use 
gi.require_version('PangoCairo', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import PangoCairo
/usr/lib/python3/dist-packages/lios/ui/gtk/terminal.py:24: PyGIWarning: Vte was 
imported without specifying a version first. Use gi.require_version('Vte', 
'2.91') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GObject, Vte

(lios:1979671): Gtk-WARNING **: 17:14:40.398: Cannot connect attribute 'text' 
for cell renderer class 'lios+ui+gtk+tree_view+CellRendererToggle' since 
attribute does not exist
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 591, in 
_connect_with_autospawn
self._server_spawn(connection_args)
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 687, in 
_server_spawn
raise SpawnError("Can't find Speech Dispatcher spawn command %s"
speechd.client.SpawnError: Can't find Speech Dispatcher spawn command 
/usr/bin/speech-dispatcher

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/lios", line 8, in 
linux_intelligent_ocr_solution()
  File "/usr/lib/python3/dist-packages/lios/main.py", line 184, in __init__
self.preferences.set_default_speech_module_and_language()
  File "/usr/lib/python3/dist-packages/lios/preferences.py", line 103, in 
set_default_speech_module_and_language
test = speech.Speech()
   ^^^
  File "/usr/lib/python3/dist-packages/lios/speech.py", line 24, in __init__
super(Speech,self).__init__(client_name)
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 578, in __init__
self._connect_with_autospawn(connection_args, autospawn)
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 594, in 
_connect_with_autospawn
raise ce
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 584, in 
_connect_with_autospawn
self._conn = _SSIP_Connection(**connection_args)
 ^^^
  File "/usr/lib/python3/dist-packages/speechd/client.py", line 190, in __init__
raise SSIPCommunicationError("Can't open socket using method "
speechd.client.SSIPCommunicationError: Can't open socket using method 
unix_socket
Original error: [Errno 2] No such file or directory
Additional error: Can't find Speech Dispatcher spawn command
/usr/bin/speech-dispatcher

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0

Bug#1041584: Consider switching to wondershaper 1.4.1

[Andrey Semashev]

Package: wondershaper
Version: 1.1a-10.1
Source: wondershaper

Please, consider switching to a newer version of wondershaper from this
repository:

https://github.com/magnific0/wondershaper

At the moment, the latest version here is 1.4.1.

This version has a few notable improvements over 1.1a, in particular:

- Improved quality of traffic shaping, especially for ingress traffic,
which no longer drops packets.
- Ability to limit only ingress or only egress traffic.
- Support for configuration files.

In order to support selective traffic limiting, the new version has a
different command line syntax, which should probably be mentioned in the
NEWS.

Bug#1041564: lios: missing dependency 'speech-dispatcher'

[Samuel Thibault]

Please always keep the bug in Cc, so that I am not the only recipient of
the mail. Writing to me only means risking falling in the middle of my
vacations and thus not getting an answer for weeks, or that I just don't
have the time to answer and thus you would at best get a terse answer,
or worse, no answer at all... Conversely, keeping the bug in Cc means
avoiding all these issues completely, you'll involve all the community
to help you, make the answers you get available to everyone, and even
archived for web crawlers to find them whenever somebody has the same
issue.

Boruch Baum, le jeu. 20 juil. 2023 18:16:23 -0400, a ecrit:
>   File "/usr/lib/python3/dist-packages/lios/preferences.py", line 103, in 
> set_default_speech_module_and_language
> test = speech.Speech()
>^^^

Ok, I see, that's on first launch.  It's indeed an upstream issue, I
have submitted a patch which we can include in Debian.

Thanks for your report,
Samuel

Bug#1041583: gnome-shell-extension-weather: needs update for GNOME Shell 44

[Simon McVittie]

Control: severity 1038412 important
Control: tags 1038412 + trixie sid fixed-upstream
Control: tags -1 + fixed-upstream
Control: merge 1038412 -1

On Thu, 20 Jul 2023 at 23:39:54 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44.

Sorry, I missed the previous bug report from Amr Ibrahim which says the
current version is not compatible with Shell 44, but version 121 is.

smcv

Bug#1041567: gnome-shell-extension-arc-menu: needs update for GNOME Shell 44

[Simon McVittie]

On Thu, 20 Jul 2023 at 23:24:52 +0100, Simon McVittie wrote:
> If a new upstream version is compatible with Shell 43 but not 44,
> please upload to experimental for now.

That should of course have said: if the new version is compatible with
*44* but not *43*, please upload to experimental for now.  Sorry for
any confusion caused!

smcv

Bug#1041576: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44

[Andres Salomon]

Thanks for the reminder. The current version does work on gnome 44 w/ 
no other changes, just gotta upload a new version.


I'll also update the dependency to limit it to gnome-shell between 40 
and 44 (inclusive) when I do that.


On Thu, Jul 20 2023 at 11:33:41 PM +01:00:00, Simon McVittie 
 wrote:

Package: gnome-shell-extension-no-annoyance
Version: 0+20220925-c6804a4-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org 


Usertags: gnome-shell-44

This extension's apt/dpkg dependencies say it is compatible with all
versions of GNOME Shell since 40, but its metadata disagrees and does
not list GNOME Shell 44 (currently available in experimental) as a
compatible version. Depending what has changed, it might need either a
simple metadata update or code changes.

I'd recommend adding dependencies on

gnome-shell (>= x), gnome-shell (<< y~)

for suitable values of x and y, so that it can only be co-installed 
with

versions of GNOME Shell for which compatibility has been checked.
For version 0+20220925-c6804a4-3 the appropriate dependency seems to 
be


gnome-shell (>= 40), gnome-shell (<< 44~)

but obviously this will change when compatibility with version 44
is added.

smcv

Bug#1041568: gnome-shell-extension-dashtodock: needs update for GNOME Shell 44

[Simon McVittie]

Control: severity 1033100 important
Control: tags 1033100 + trixie sid fixed-upstream
Control: tags -1 + fixed-upstream
Control: merge 1033100 -1

On Thu, 20 Jul 2023 at 23:26:16 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44.

Sorry, I missed the pre-existing bug #1033100, in which Amr Ibrahim
reports that the current version is not compatible with 44 but the new
version 84 is.

smcv

Bug#1041583: gnome-shell-extension-weather: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-weather
Version: 119-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041582: gnome-shell-extension-vertical-overview: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-vertical-overview
Version: 10-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041581: gnome-shell-extension-top-icons-plus: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-top-icons-plus
Version: 27-8
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041580: gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-tiling-assistant
Version: 39-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44
Control: fixed -1 39-3

The version of gnome-shell-extension-tiling-assistant in unstable is
not marked as compatible with GNOME Shell 44, but the version in
experimental is.

If the version in experimental is suitable to be uploaded to unstable
even while the GNOME Shell in unstable is still version 43, please do
so, and close this bug in that upload. If not, the version currently
in testing/unstable can stay until we are ready to go ahead with GNOME
Shell 44.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready.

Thanks,
smcv

Bug#1041579: gnome-shell-extension-system-monitor: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-system-monitor
Version: 40-5
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041578: gnome-shell-extension-shortcuts: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-shortcuts
Version: 1.3.6-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041577: gnome-shell-extension-panel-osd: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-panel-osd
Version: 1.0.50.gc032923-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041576: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-no-annoyance
Version: 0+20220925-c6804a4-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension's apt/dpkg dependencies say it is compatible with all
versions of GNOME Shell since 40, but its metadata disagrees and does
not list GNOME Shell 44 (currently available in experimental) as a
compatible version. Depending what has changed, it might need either a
simple metadata update or code changes.

I'd recommend adding dependencies on

gnome-shell (>= x), gnome-shell (<< y~)

for suitable values of x and y, so that it can only be co-installed with
versions of GNOME Shell for which compatibility has been checked.
For version 0+20220925-c6804a4-3 the appropriate dependency seems to be

gnome-shell (>= 40), gnome-shell (<< 44~)

but obviously this will change when compatibility with version 44
is added.

smcv

Bug#1041575: gnome-shell-extension-impatience: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-impatience
Version: 0.4.8-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041571: gnome-shell-extension-flypie: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-flypie
Version: 21-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041574: gnome-shell-extension-hamster: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-hamster
Version: 0.10.0+git20210628-4
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041573: gnome-shell-extension-gamemode: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-gamemode
Version: 8-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041572: gnome-shell-extension-freon: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-freon
Version: 52+dfsg-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041570: gnome-shell-extension-espresso: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-espresso
Version: 7-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041569: gnome-shell-extension-easyscreencast: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-easyscreencast
Version: 1.7.0-2
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041568: gnome-shell-extension-dashtodock: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-dashtodock
Version: 75-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv

Bug#1041567: gnome-shell-extension-arc-menu: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-arc-menu
Version: 49+forkv29-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready to go ahead.

If a new upstream version is compatible with Shell 43 but not 44,
please upload to experimental for now.

Thanks,
smcv

Bug#1041566: gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 44

[Simon McVittie]

Package: gnome-shell-extension-bluetooth-quick-connect
Severity: important
Tags: trixie sid fixed-upstream
Forwarded: 
https://github.com/bjarosze/gnome-bluetooth-quick-connect/commit/17e9615270c3b740ed726caa080813449e41e2a5
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension is known not to be compatible with GNOME Shell 44, and
will need to be updated.

New upstream version 36 is compatible with Shell 44, but incompatible
with Shell 43, so will have to go to experimental to start with. I'm
still using Shell 43 at the moment, so it would be great if someone who
is already using 44 could test and upload the new version.

Thanks,
smcv

Bug#1041565: RFP: lib60870 -- lib60870 library for IEC 60870-5 based protocols in C

[Martin]

Package: wnpp
Severity: wishlist

* Package name: lib60870
  Version : v2.3.2
  Upstream Author : Michael Zillgith 
* URL or Web page : https://github.com/mz-automation/lib60870
* License : GPL-3
  Description : lib60870 library for IEC 60870-5 based protocols in C

The current implementation contains code for the IEC 60870-5-101
(application layer and serial link layer) and IEC 60870-5-104 (protocool
over TCP/IP) specifications.

Features:

 - support for all application layer message types
 - master and slave
 - balanced and unbalanced link layers (for CS 101 serial communication)
 - client/server for CS 104 TCP/IP communication
 - CS 104 redundancy group support
 - CS101 slave/CS104 server: file service support
 - Supports most TLS features required by IEC 62351-3 (third party code
   mbedtls required)
 - portable C99 code

Bug#1041564: lios: missing dependency 'speech-dispatcher'

[Samuel Thibault]

Control: tags -1 + unreproducible

Hello,

boruch baum, le jeu. 20 juil. 2023 17:47:12 -0400, a ecrit:
> Running this program as packaged by debian fails with a python error
> pointing to a missing speech-dispatcher.

Please post the actual error you are getting, since I cannot reproduce
this error.

> Manually installing debian package 'speech-dispatcher{,-espeak}' fixes
> the issue.
> 
> My opinion is that there are two issues in this bug report. First,
> there is the issue of the missing dependency, which is definiely a
> debian issue. What might be an upstream issue is why a speech
> dispatcher is a requirement for a scanner / OCR program? At most, it
> should be a 'suggests' or 'recommends'. See that package lios
> currently has a 'depends' on package 'espeak'.

The error could tell how to fix this. Here I'm not seeing any issue.

Samuel

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Bill Allombert]

On Sun, Jul 16, 2023 at 12:42:11PM +0100, Luca Boccassi wrote:
> If there is somebody who's ignoring things, that would be yourself,
> given this change has been not only been explicitly requested, but even
> provided _BY_ the CTTE, as you would have easily found out if you
> actually went and checked:
> 
> https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/93
> http://meetbot.debian.net/debian-ctte/2023/debian-ctte.2023-07-11-17.58.log.html
> 
> Debian Community Team, Adam is once again sabotaging the CTTE's work
> with hostile NMUs, could you please intervene? Thank you.

This is premature.

> In the meanwhile, I'll immediately revert the sabotage.

If this package is so important, why is it maintained by NMUs ?
Why cannot the maintainers do a proper upload ?

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1041564: lios: missing dependency 'speech-dispatcher'

[boruch baum]

Package: lios
Version: 2.7.2-6
Severity: normal
X-Debbugs-Cc: boruch_b...@gmx.com

Dear Maintainer,

Running this program as packaged by debian fails with a python error
pointing to a missing speech-dispatcher. Manually installing debian
package 'speech-dispatcher{,-espeak}' fixes the issue.

My opinion is that there are two issues in this bug report. First,
there is the issue of the missing dependency, which is definiely a
debian issue. What might be an upstream issue is why a speech
dispatcher is a requirement for a scanner / OCR program? At most, it
should be a 'suggests' or 'recommends'. See that package lios
currently has a 'depends' on package 'espeak'.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (680, 'stable-security'), (660, 'stable-updates'), (650, 
'stable'), (500, 'oldstable-security'), (450, 'testing'), (400, 'oldstable'), 
(300, 'oldoldstable'), (200, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages lios depends on:
ii  aspell-en2020.12.07-0-1
ii  espeak   1.48.15+dfsg-3
ii  gir1.2-gst-plugins-base-1.0  1.22.4-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-vte-2.91  0.70.3-1
ii  imagemagick  8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6
ii  poppler-utils22.12.0-2+b1
ii  python3  3.11.2-1+b1
ii  python3-enchant  3.2.2-1
ii  python3-gi   3.42.2-3+b1
ii  python3-gi-cairo 3.42.2-3+b1
ii  python3-sane 2.9.1-2+b4
ii  python3-speechd  0.11.4-2
ii  tesseract-ocr5.3.0-2

Versions of packages lios recommends:
ii  gnome-icon-theme  3.12.0-5

Versions of packages lios suggests:
pn  cuneiform  

-- no debconf information

Bug#1041563: RM: malaga -- RoQA; no rdeps; orphaned; depends on gtk2; dead upstream

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:malaga

Please remove malaga. It is orphaned, dead upstream, and it depends on 
gtk2. Also, it does not have any reverse dependencies.

Bug#1041562: dracut-core: dracut 059 produces broken unified kernel images with systemd 254

[Pawel Jasiak]

Package: dracut-core
Version: 059-4
Severity: normal
Tags: patch
X-Debbugs-Cc: cont...@jasiak.dev

Dear Maintainer,

dracut produces broken unified kernel images with systemd 254.

To reproduce:
dracut --uefi --kver ${kernel-version}

dracut produces the following warning:
objcopy: /var/tmp/dracut.JFHsiy/uefi/linux.efi:.osrel: section below image base
objcopy: /var/tmp/dracut.JFHsiy/uefi/linux.efi:.linux: section below image base
objcopy: /var/tmp/dracut.JFHsiy/uefi/linux.efi:.initrd: section below image base

It's not recognized as error and produces an image:
dracut: *** Creating UEFI image file '/boot/efi/EFI/Linux/linux.efi' done ***

As a result in next boot systemd-boot fails to load the image:
Error loading \EFI\Linux\linux.efi: Load error

Expected behavior:
Produced image should be a valid image.

Fixes are already in dracut master branch:
- f32e95bcadbc5158843530407adc1e7b700561b1
- 33a66ed04bdc30eccb172a0cd6dcc36d9d74f825


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

Kernel: Linux 6.4.4-tartar (SMP w/32 CPU threads; PREEMPT)
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)

Versions of packages dracut-core depends on:
ii  cpio   2.13+dfsg-7.1
ii  e2fsprogs  1.47.0-2
ii  kmod   30+20230519-1
ii  kpartx 0.9.4-5
ii  libc6  2.37-6
ii  libkmod2   30+20230519-1
ii  udev   254~rc2-3

Versions of packages dracut-core recommends:
ii  binutils  2.40.90.20230714-2
pn  console-setup 
ii  cryptsetup2:2.6.1-4
pn  dmraid
ii  dmsetup   2:1.02.185-2
ii  lvm2  2.03.16-2
ii  mdadm 4.2+20230508-5
pn  pigz  
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1
ii  systemd   254~rc2-3

dracut-core suggests no packages.

-- no debconf information

Bug#1041561: node-jszip-utils: Please create a dist version

[Bastien Roucariès]

Source: node-jszip-utils
Severity: wishlist

Dear Maintainer,

Could you create a dist version and browserified version ? it is needed for
some package in the tree

Thanks

bastien


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

Bug#1041560: node-jszip: Please create a dist version

[Bastien Roucariès]

Source: node-jszip
Severity: wishlist

Dear Maintainer,

Could you create a dist version and browerify version. It is needed for package 
in the tree

Thanks

Bastien


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

Bug#1041559: Recommends non-existent package linux-musl-dev

[Josh Triplett]

Package: musl-dev
Version: 1.2.3-1
Severity: serious
X-Debbugs-Cc: j...@joshtriplett.org

musl-dev Recommends linux-musl-dev, which does not appear to exist in
the archive.

Policy 2.2.1 "The main archive area":
> package must not declare a "Pre-Depends", "Depends", "Recommends",
> "Build-Depends", "Build-Depends-Indep", or "Build-Depends-Arch"
> relationship on a non-*main* package unless that package is only
> listed as a non-default alternative for a package in *main*



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

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
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)

Versions of packages musl-dev depends on:
ii  gcc [gcc-x86-64-linux-gnu]  4:13.1.0-4
ii  musl1.2.3-1

Versions of packages musl-dev recommends:
pn  linux-musl-dev  

musl-dev suggests no packages.

-- no debconf information

Bug#1040007: libwww-mechanize-perl: migrate to libhttp-cookiejar-perl?

[Steve Langasek]

Package: libwww-perl
Followup-For: Bug #1040007
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Control: title -1 spurious runtime dependency on libhttp-cookiejar-perl
Control: tags -1 patch

After closer examination here, I've determined that:

 - libwww-perl has gained a dependency on libhttp-cookiejar-perl, but the
   code does not use it at runtime
 - it does use libhttp-cookies-perl out of the box, with which
   libhttp-cookiejar-perl is redundant
 - libhttp-cookiejar-perl does not provide the same full set of interfaces as
   libhttp-cookies-perl and is not a drop-in replacement
 - libhttp-cookiejar-perl claims to be a "safer" cookie jar, but this is
   conditional on installing Mozilla::PublicSuffix which is not packaged in
   Debian.

So I am recommending that this new dependency be dropped, instead.

It is reasonable to keep it as a build-dependency.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libwww-perl-6.71/debian/control libwww-perl-6.71/debian/control
--- libwww-perl-6.71/debian/control 2023-07-08 06:34:13.0 -0700
+++ libwww-perl-6.71/debian/control 2023-07-20 12:47:43.0 -0700
@@ -45,7 +45,6 @@
  libhtml-tagset-perl,
  libhtml-tree-perl,
  libhttp-cookies-perl,
- libhttp-cookiejar-perl,
  libhttp-date-perl,
  libhttp-message-perl,
  libhttp-negotiate-perl,

Bug#1035496: fixed

[Matthias Klose]

now fixed with the ca-certificates-java updates

Bug#1041558: gsd-media-keys[…]: Unable to get default sink/source

[Al Ma]

Package: gnome-settings-daemon
Version: 43.0-4
In my journal I see the following warnings:
Jul 20 04:44:36 AnonymizedMachineName gsd-media-keys[1263]: Unable to get 
default sink
Jul 20 04:44:36 AnonymizedMachineName gsd-media-keys[1263]: Unable to get 
default source
The (hopefully, relevant) segment of the log is attached.
What do these warnings tell us?  Any bugs here?  The computer has no source and 
no sink, at least not in their everyday meanings.  Still, the computer exhibits 
other issues at boot, so I wonder what are we warned about here, which 
consequences do these warnings have, and how to avoid whichever trouble might 
be invited.
Gratefully,
AlMa
Jul 20 04:44:12 AnonymizedMachineName gsd-media-keys[1263]: Failed to grab 
accelerator for keybinding settings:rotate-video-lock
Jul 20 04:44:12 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: 
dbus-daemon[1085]: [session uid=119 pid=1085] Successfully activated service 
'org.gnome.ScreenSaver'
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.0631] dhcp4 (wlp179s0): state changed new lease, 
address=IPv4AddressOne
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.0639] policy: set 'AnonymizedWiFiName' (wlp179s0) as default for 
IPv4 routing and DNS
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.0645] dns-mgr: Writing DNS information to /sbin/resolvconf
Jul 20 04:44:13 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: 
dbus-daemon[1085]: [session uid=119 pid=1085] Activating service 
name='org.freedesktop.systemd1' requested by ':1.10' (uid=119 pid=1232 
comm="/usr/libexec/gsd-sharing")
Jul 20 04:44:13 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: 
dbus-daemon[1085]: [session uid=119 pid=1085] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
Jul 20 04:44:13 AnonymizedMachineName gsd-sharing[1232]: Failed to StopUnit 
service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
Jul 20 04:44:13 AnonymizedMachineName gsd-sharing[1232]: Failed to StopUnit 
service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: Joining mDNS multicast 
group on interface wlp179s0.IPv4 with address IPv4AddressOne.
Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: New relevant interface 
wlp179s0.IPv4 for mDNS.
Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: Registering new 
address record for IPv4AddressOne on wlp179s0.IPv4.
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1200] device (wlp179s0): state change: ip-config -> ip-check 
(reason 'none', sys-iface-state: 'managed')
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1244] device (wlp179s0): state change: ip-check -> secondaries 
(reason 'none', sys-iface-state: 'managed')
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1248] device (wlp179s0): state change: secondaries -> activated 
(reason 'none', sys-iface-state: 'managed')
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1256] manager: NetworkManager state is now CONNECTED_SITE
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1271] device (wlp179s0): Activation: successful, device activated.
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.1282] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]:   
[1689821053.3941] agent-manager: 
agent[d1470084c37e1102,:1.37/org.gnome.Shell.NetworkAgent/119]: agent registered
Jul 20 04:44:14 AnonymizedMachineName dbus-daemon[797]: [system] Activating via 
systemd: service name='org.freedesktop.realmd' unit='realmd.service' requested 
by ':1.37' (uid=119 pid=1141 comm="/usr/bin/gnome-shell")
Jul 20 04:44:14 AnonymizedMachineName systemd[1]: Starting realmd.service - 
Realm and Domain Configuration...
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: Loaded settings from: 
/usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: holding daemon: startup
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: starting service
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: GLib-GIO: Using 
cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus 
< 2.73.3)
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: connected to bus
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: GLib-GIO: 
_g_io_module_get_default: Found default implementation local (GLocalVfs) for 
‘gio-vfs’
Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: released daemon: startup
Jul 20 04:44:14 AnonymizedMachineName dbus-daemon[797]: [system] Successfully 
activated service 'org.freedesktop.realmd'
Jul 20 

Bug#967586: libquicktime: depends on deprecated GTK 2

[Bastian Germann]

I think just dropping libquicktime_config is a good idea to fix this.

Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

[Forest]

The fixed version has been in Testing for over a week now. Does another step
remain in order to get it into Stable or Backports?

This is blocking the installation of the java runtime on Bookworm systems
(unless, presumably, they upgraded from Bullseye and already had it).

Bug#1041557: r-cran-bookdown breaks r-cran-flextable autopkgtest: `bookmarks` has length 3, not length 0

[Paul Gevers]

Source: r-cran-bookdown, r-cran-flextable
Control: found -1 r-cran-bookdown/0.34+dfsg-1
Control: found -1 r-cran-flextable/0.8.4-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of r-cran-bookdown the autopkgtest of 
r-cran-flextable fails in testing when that autopkgtest is run with the 
binary packages of r-cran-bookdown from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
r-cran-bookdownfrom testing0.34+dfsg-1
r-cran-flextable   from testing0.8.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-bookdown

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-flextable/35990349/log.gz

 94s BEGIN TEST testthat.R
 94s  94s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
 94s Copyright (C) 2023 The R Foundation for Statistical Computing
 94s Platform: x86_64-pc-linux-gnu (64-bit)
 94s  94s R is free software and comes with ABSOLUTELY NO WARRANTY.
 94s You are welcome to redistribute it under certain conditions.
 94s Type 'license()' or 'licence()' for distribution details.
 94s  94s R is a collaborative project with many contributors.
 94s Type 'contributors()' for more information and
 94s 'citation()' on how to cite R or R packages in publications.
 94s  94s Type 'demo()' for some demos, 'help()' for on-line help, or
 94s 'help.start()' for an HTML browser interface to help.
 94s Type 'q()' to quit R.
 94s  94s > library(testthat)
 94s > library(flextable)
 94s > library(officer)
 94s >  94s > test_check("flextable")
107s [ FAIL 1 | WARN 0 | SKIP 5 | PASS 163 ]
107s 107s ══ Skipped tests (5) 
═══

108s • On CRAN (5): 'test-as_flextable.R:3:1', 'test-borders.R:3:1',
108s   'test-captions-rmd.R:188:3', 'test-keep-next.R:3:1', 
'test-md-captions.R:3:1'
108s 108s ══ Failed tests 

108s ── Failure ('test-captions-rmd.R:150:3'): with word_document2 
──

108s `bookmarks` has length 3, not length 0.
108s 108s [ FAIL 1 | WARN 0 | SKIP 5 | PASS 163 ]
108s Error: Test failures
108s Execution halted
108s autopkgtest [11:46:05]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041556: src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Paul Gevers]

Source: r-cran-checkmate
Version: 2.1.0-1
Severity: serious
Control: close -1 2.2.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041555: bookworm-pu: package stunnel4/3:5.68-2+deb12u1

[Peter Pentchev]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: stunn...@packages.debian.org, r...@debian.org
Control: affects -1 + src:stunnel4

Hi,

This is a pre-approval request before I upload an update to
the stunnel4 package targetting bookworm to fix a bug in
the handling of improperly closed TLS connections; see #1041545.
The patch was taken from stunnel4 version 5.70 that I just
uploaded to unstable.

[ Reason ]
In versions before 5.70, stunnel4 fails to recognize a new OpenSSL 3.x
error code that signals that the remote side closed the network
connection without performing a proper TLS shutdown. Instead, stunnel
treats this situation as an error.

If there was any pending data that the stunnel service had enqueued for
sending over the encrypted connection, it is discarded, so if the TLS
session is later resumed, the encrypted data stream will be corrupted.

[ Impact ]
Quoting from the changelog entry for version 5.70:

  - Fixed TLS socket EOF handling with OpenSSL 3.x.
This bug caused major interoperability issues between
stunnel built with OpenSSL 3.x and Microsoft's
Schannel Security Support Provider (SSP).

The stunnel4 version in bookworm can fail to interoperate with
some TLS applications, thus rendering the package unusable for
people who want to set up such tunnels.

[ Tests ]
For the present there are no automated tests for this problem, but
it can be reproduced manually using the following procedure:
- set up a tunnel in non-client mode (stunnel4 accepts TLS connections
  and forwards to a plain-text service) listening on e.g. a loopback
  address and forwarding to e.g. another port on the loopback address
- start (or restart) the stunnel4 service (a systemd user service will
  work just as well) so that it listens for incoming TLS connections
- start a program that listens for plain-text connections, e.g.
  `nc -v -l 127.0.0.2 8086`
- use `openssl s_client -connect ...` to connect to the stunnel instance
- type a couple of words on both sides to make sure data is being
  forwarded correctly
- kill the OpenSSL `s_client` process using e.g. an ABRT or FPE signal so
  that it does not get a chance to perform the proper TLS shutdown
- look for an error message in the logs of the stunnel service;
  the error may look like:
  "LOG3[0]: SSL_read: ../ssl/record/rec_layer_s3.c:303:
   error:0A000126:SSL routines::unexpected eof while reading"

The appearance of this error message means that stunnel has failed to
recognize the OpenSSL error code that signifies an unexpectedly closed
network connection, and treats it as an error instead of a closed
connection. With the attached patch, stunnel will instead report
"LOG6[1]: TLS socket closed (SSL_read)".

[ Risks ]
The code is easy to follow for people familiar with the C language;
it is a no-op if the OpenSSL version used does not support that particular
error code, and if it does, it is recognized and treated as a closed
network connection event.

In my opinion the risk is minimal, if any at all.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
A new patch is added as the debian/patches/08-tls-eof.patch file;
it adds several lines to the "handle an SSL error" case in
the src/client.c file.

diff -Nru stunnel4-5.68/debian/changelog stunnel4-5.68/debian/changelog
--- stunnel4-5.68/debian/changelog  2023-02-12 13:40:09.0 +0200
+++ stunnel4-5.68/debian/changelog  2023-07-20 22:01:31.0 +0300
@@ -1,3 +1,11 @@
+stunnel4 (3:5.68-2+deb12u1) bookworm; urgency=medium
+
+  * Add the 08-tls-eof patch to fix the handling of a peer closing
+a TLS connection without proper TLS shutdown messaging.
+Closes: #1041545
+
+ -- Peter Pentchev   Thu, 20 Jul 2023 22:01:31 +0300
+
 stunnel4 (3:5.68-2) unstable; urgency=medium
 
   * Add the 07-tests-errmsg patch to fix the FTBFS on several architectures
diff -Nru stunnel4-5.68/debian/patches/08-tls-eof.patch 
stunnel4-5.68/debian/patches/08-tls-eof.patch
--- stunnel4-5.68/debian/patches/08-tls-eof.patch   1970-01-01 
02:00:00.0 +0200
+++ stunnel4-5.68/debian/patches/08-tls-eof.patch   2023-07-20 
22:00:46.0 +0300
@@ -0,0 +1,41 @@
+Description: Fix handling of socket closed without TLS shuttdown
+ In versions before 5.70, stunnel4 fails to recognize a new OpenSSL 3.x
+ error code that signals that the remote side closed the network
+ connection without performing a proper TLS shutdown. Instead, stunnel
+ treats this situation as an error.
+ .
+ If there was any pending data that the stunnel service had enqueued for
+ sending over the encrypted connection, it is discarded, so if the TLS
+ session is later resumed, the encrypted data stream will be corrupted.
+Bug-Debian: https://bugs.debian.org/1041545

Bug#1041043: [Pkg-samba-maint] Bug#1041043: samba domain netlogon broken after windows 10/11 Jul-2023 update

[Michael Tokarev]

20.07.2023 18:04, Heil, Stefan пишет:

Dear list / Samba maintainers,

Will the fix for this also make it into Bullseye / Samba 4.13? If so,
is there a (tentative) ETA?


Please do not use 4.13. It is dead.  I especially do *not* want to
backport this bugfix to bullseye samba, because it will give false
sense of security.

See also:

https://lists.debian.org/debian-security-announce/2021/msg00201.html

In short: running samba which released in bullseye as an AD-DC is
not supported already because that version had numerous other security
issues. And the issue we have with jul-23 win updates is about the ad-dc.
Samba 4.16 had a major rewrite of some core components (eg vfs has been
basically rewritten) exactly to fix other security issues, and further
vital fixes for the domain components are based on that.


I'm wondering if we can wait for the fix or if I need to install it
from bullseye-backports, which I am trying to avoid, if possible.


bullseye-backports already has the fixed version, and recent (jul-19)
security release of samba is on the way to bullseye-backports too as
I write this.  Samba in backports is in excellent shape, it is
uncomparable to what we have in bullseye.

/mjt

Bug#1041554: bookworm-pu: package openscap/1.3.7+dfsg-1+deb12u1

[Håvard Flaget Aasen]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: opens...@packages.debian.org, havard.f.aa...@pfft.no
Control: affects -1 + src:openscap

The application 'oscap-docker' in openscap-utils is non-functional
because of a missing dependency on python3-openscap, python3-openscap is
also missing a dependency on python3-docker, this release fixes both
issues and closes: #1040936.

[ Reason ]
Missing dependency for the package openscap-utils and python3-openscap,
most likely introduced with the update to version 1.3.5.
This stable release is the first to hold the 'oscap-docker'.

[ Impact ]
oscap-docker will not work until the users has manually added the
missing dependencies.

[ Tests ]
Manually tested with running the application with the required
dependencies installed.

[ Risks ]
I would say none, since it is only two added dependencies.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Add python3-openscap as dependency for openscap-utils and python3-docker
as dependency for python3-openscap. Added 'bookworm' as target for CI in
d/salsa-ci.yml, this change is not documented in the changelog.

[ Other info ]
No

Regards,
-- 
Håvard
diff -Nru openscap-1.3.7+dfsg/debian/changelog 
openscap-1.3.7+dfsg/debian/changelog
--- openscap-1.3.7+dfsg/debian/changelog2023-01-27 23:41:17.0 
+0100
+++ openscap-1.3.7+dfsg/debian/changelog2023-07-20 19:50:10.0 
+0200
@@ -1,3 +1,10 @@
+openscap (1.3.7+dfsg-1+deb12u1) bookworm; urgency=medium
+
+  * Update dependencies for openscap-utils and python3-openscap
+Closes: #1040936
+
+ -- Håvard F. Aasen   Thu, 20 Jul 2023 19:50:10 +0200
+
 openscap (1.3.7+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru openscap-1.3.7+dfsg/debian/control openscap-1.3.7+dfsg/debian/control
--- openscap-1.3.7+dfsg/debian/control  2023-01-27 23:41:17.0 +0100
+++ openscap-1.3.7+dfsg/debian/control  2023-07-20 19:50:10.0 +0200
@@ -92,6 +92,7 @@
 Section: python
 Architecture: linux-any
 Depends: libopenscap25 (= ${binary:Version}),
+ python3-docker,
  ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends},
@@ -167,6 +168,7 @@
 Package: openscap-utils
 Architecture: linux-any
 Depends: openscap-scanner (= ${binary:Version}),
+ python3-openscap (= ${binary:Version}),
  rpm,
  ${misc:Depends},
  ${python3:Depends},
diff -Nru openscap-1.3.7+dfsg/debian/salsa-ci.yml 
openscap-1.3.7+dfsg/debian/salsa-ci.yml
--- openscap-1.3.7+dfsg/debian/salsa-ci.yml 2023-01-27 23:41:17.0 
+0100
+++ openscap-1.3.7+dfsg/debian/salsa-ci.yml 2023-07-20 19:50:10.0 
+0200
@@ -2,3 +2,6 @@
 include:
   - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
   - 
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+variables:
+  RELEASE: 'bookworm'

Bug#1041524: logcheck: badly handles "rsyslog + journalctl" checking

[Richard Lewis]

On Thu, 20 Jul 2023 12:15:25 +0200 Thomas Parmelan
 wrote:

Some interesting ideas in here - i think i am missing something though:

> The systemd journal is checked by default, in addition to rsyslog files,
> starting with logcheck version 1.4.1. But the format of timestamps are
> different by default for journal (uses the old-school format: "Jul 20
> 11:51:03") and rsyslog >= 8.2210.0-3 (uses an RFC3339-compatible format:
> "2023-07-20T11:51:03.046581+0200"). So logcheck cannot compare them
> correctly.

I understand until the word "compare" here - are you saying that rules
don't match entries from rsyslog or from systemd? because both seem to
be matched fine for me!

> Also, journalctl can emit multi-line logs, whereas rsyslog cannot.
>
> The attached patch adds a new ISO_TIMESTAMPS config variable to the logcheck
> script, allowing logcheck to:
>   - call journalctl with "-o short-iso-precise" in order to get a
> nearly-RFC3339-compatible timestamp
>   - add the missing ':' between the timezone hours and minutes to convert the
> journalctl shot-iso-precise timestamp to the exact RFC3339 timestamp
> format used by rsyslog

I think my question above is related to this bullet: a typical prefix
in the logcheck-database of rules is

^(\w{3} [ :0-9]{11}|[0-9T:.+-]{32})

which should match both rules without needing to change the format,
and includes a : wherever it occurs have we got something wrong in
this, and if so, what?

>   - join continuous lines (lines starting with whitespace) from
> journalctl output, as rsyslog only logs them as one line

this part i understand (although i didnt check the sed logic closely)
and agree it would be worth doing: is it definitely correct that a
blank line is always a continuation line like this?

>   - handle SORTUNIQ correctly even when using ISO_TIMESTAMPS

i didnt understand this bit of the patch (copied below):- it seems to
have a lot of repetition, and introduce a call to 'uniq', but only
sometimes:

(i also wonder why anything is better than just 'sort -u' regardless
of timestamp format): can you explain what the issue is that is being
solved?


-if [ "$SORTUNIQ" -eq 1 ];then
-   SORT="sort -u"
-else
-   SORT="sort -k 1,3 -s"
-fi

- $SORT "$TMPDIR/logoutput"/* | sed -e 's/[[:space:]]\+$//' >
"$TMPDIR/logoutput-sorted" \
+# Use "sort -u" or "sort ... | uniq"
+if [ "$SORTUNIQ" -eq 1 ];then
+ SORT_OPTS="-u"
+ sort $SORT_OPTS "$TMPDIR/logoutput"/* | sed -e 's/[[:space:]]\+$//'
> "$TMPDIR/logoutput-sorted" \
+   || error "Could not save sorted log content to
$TMPDIR/logoutput-sorted"
+else
+ if [ "$ISO_TIMESTAMPS" -eq 1 ]; then
+ SORT_OPTS="-k 1 -s"
+ else
+ SORT_OPTS="-k 1,3 -s"
+ fi
+ sort $SORT_OPTS "$TMPDIR/logoutput"/* | sed -e 's/[[:space:]]\+$//'
| uniq > "$TMPDIR/logoutput-sorted" \
|| error "Could not save sorted log content to
$TMPDIR/logoutput-sorted"
+fi

Bug#1038441: Horde uses obsolete each() function throughout its code.

[Michael Schlueter]

A fix is already available at github: 
https://github.com/horde/imp/commit/10535860c24f2677671fbbc0d97129c994225c37

Bug#1041553:

[Sid T]

Control: retitle -1 Fails to remove packages during update (backport)

Bug#1041374: Working again

[par78]

The DNS problems regarding www.cipherdyne.org are solved, 
https://www.cipherdyne.org/cgi-bin/myip is working as expected.


So everything works as expected again.


But the bug is still there – maybe you can have a short look and (if 
not a Debian problem) push it upstream.
But there is absolutely no urgency – I think this has been a 
extremly rare event.



Thanks for bringing the package into Debian. Great work!



Best wishes

Patrick


OpenPGP_0xBDDAAA4B5B0D663E.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041553:

[Sid T]

Control: retitle -1 gnome-software: GNOME Software fails to remove packages
to satisfy dependencies (backport request)

Bug#1041553: gnome-software: GNOME Software fails to remove packages to satisfy dependencies

[sidt]

Package: gnome-software
Version: 43.5-1
Severity: important
Tags: patch
X-Debbugs-Cc: sidto...@gmail.com

Dear Maintainer,

GNOME Software fails to update system, if the update involves removal of any
package.

Please refer https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2232

This issue affects "apt" based package backends, though it's not clear why
"dnf" based package backends are not affected. This issue is fixed in gnome-44
and main (gnome-45) branches. This fix is not available in gnome-43 branch (
and upstream will not be back-porting the fix to gnome-43 branch ).

Since this greatly affects the usability of GNOME Software, it would make sense
to port the patch to gnome-43 branch ( and any relevant branches ) downstream
in Debian & Ubuntu.

Thanks!



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

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

Versions of packages gnome-software depends on:
ii  appstream0.16.2-1
ii  apt-config-icons 0.16.2-1
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gnome-software-common43.5-1
ii  gsettings-desktop-schemas44.0-2
ii  libadwaita-1-0   1.3.3-2
ii  libappstream40.16.2-1
ii  libc62.37-6
ii  libcairo21.16.0-7
ii  libfwupd21.9.3-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.76.4-2
ii  libgtk-4-1   4.10.4+ds-2
ii  libgtk3-perl 0.038-3
ii  libgudev-1.0-0   237-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmalcontent-0-00.11.0-4
ii  libpackagekit-glib2-18   1.2.6-5
ii  libpango-1.0-0   1.50.14+ds-1
ii  libpolkit-gobject-1-0122-4
ii  libsoup-3.0-03.2.2-2
ii  libxmlb2 0.3.10-2
ii  packagekit   1.2.6-5
ii  software-properties-gtk  0.99.30-4

Versions of packages gnome-software recommends:
ii  fwupd  1.9.3-1

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-snap 

-- no debconf information

Bug#1041523: tracker.debian.org: displays autopkgtest for other src:package on same page

[Raphael Hertzog]

Hello,

On Thu, 20 Jul 2023, Martin-Éric Racine wrote:
> The tracker at  shows autopkgtest 
> results for both this src:package and for another src:package.

I see no autopkgtest results at all. They are only shown when something
fails... and in that case, it only shows results of the current package.
Ex here:
https://tracker.debian.org/pkg/android-platform-frameworks-base

If you are referring to information shown in the "testing migrations"
panel, then I'm afraid that this is meant to replicate information output
by britney and it is expected that it shows autopkgtest results of reverse
dependencies.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Bug#1039911: transition: sdl12-compat taking over libsdl1.2-dev

[Sebastian Ramacher]

On 2023-07-20 12:56:16 +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 18:18:09 +0100, Simon McVittie wrote:
> > On Sun, 16 Jul 2023 at 18:55:28 +0200, Sebastian Ramacher wrote:
> > > Could you check whether that is an issue in sdl12-compat or
> > > libsdl-perl?
> >
> > I already opened  and marked it as
> > blocking this transition-tracker bug.
> 
> After talking to SDL upstream, it looks as though libsdl-perl was always
> doing something that ought to be undefined behaviour (freeing the global
> video surface object, which is "owned" by the SDL video implementation),
> but an implementation quirk of libsdl1.2 meant that attempting to free
> the global video surface was silently ignored.

Thanks for handling this issue.

> The regression with sdl12-compat is because sdl12-compat is more likely
> to deallocate the global video surface and allocate a new one, whereas
> libsdl1.2 would usually keep using the same global video surface for the
> lifetime of the process, even if parameters like the colour depth changed.
> 
> Possible solutions to continue this transition:
> 
> 1. fix libsdl-perl (#1041211, RC; I sent a potential patch upstream, but
>I've never tried writing Perl XS bindings before, so I'm not very
>confident that I'm getting it right)
> 
> 2. work around the issue in sdl12-compat because they aim for bug-for-bug
>compatibility (#1041416, wishlist, also forwarded upstream), after
>which #1041211 can be downgraded to non-RC
> 
> 3. kick out libsdl-perl, dizzy, frozen-bubble and pangzero from testing
>until at least one of those two bugs can be fixed
>(I've checked with `dak rm -R -n -s testing` that those four source
>packages would be enough)

I added removal hints. The libsdl-perl maintainers should have enough
time until the release of trixie to fix the bug and make it eligible to
migrate back to testing.

Cheers
-- 
Sebastian Ramacher

Bug#1041551: ITP: node-corepack -- Zero-runtime-dependency package acting as bridge between Node projects and their package managers

[Israel Galadima]

Package: wnpp
Severity: wishlist
Owner: Israel Galadima 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name    : node-corepack
  Version : 0.19.0
  Upstream Author : Corepack contributors
* URL : https://github.com/nodejs/corepack#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Zero-runtime-dependency package acting as bridge 
between Node projects and their package managers


Corepack is a zero-runtime-dependency Node.js script that acts as a 
bridge between
Node.js projects and the package managers they are intended to be used 
with during
development. In practical terms, Corepack lets you use Yarn, npm, and 
pnpm without

having to install them.

This package will be maintained by the Debian JavaScript Team.



OpenPGP_0x3679ECB87B7CEC0C.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041485: RFS: spades/3.15.5+dfsg-2.1 [NMU] [RC] -- genome assembler for single-cell and isolates data sets

[Bo YU]

Hi!

On Fri, Jul 21, 2023 at 1:12 AM Étienne Mollier  wrote:
>
> Hi,
>
> Bo YU, on 2023-07-21:
> > On Thu, Jul 20, 2023 at 5:34 PM Étienne Mollier  wrote:
> > > Bo YU, on 2023-07-20:
> > > > I will clean up the change for here and upstream.
> > >
> > > Sounds good, let us know once you pushed your modification.
> >
> > I have updated it here:
> > https://salsa.debian.org/med-team/spades
> >
> > The only thing this is uncertain about is whether the distribution
> > should be UNRELEASE or unstable
> > in changelog. In Debian python team, it was `UNRELEASE` if team upload
> > from non-DD/DM. So l use it there.
>
> I'm fine with both convention; having a the changelog entry
> stating "unstable" at least makes it clear the last person
> having touched intended to have the package ready for upload.
> The state can be reverted easily to UNRELEASED if something off
> is noted.
>
> By contrast the tag would be more problematic to remove after
> being pushed to the VCS.  Personally, I usually run dgit, which
> does the tagging for me on upload, so always tag and push after
> the actual upload of the package.
>
> > Could you have a look?:)
>
> The RC bug is appropriately addressed, well done!
>
> The only issues I caught were some trailing blank spaces in the
> changelog, and the named log entry was a bit redundant since
> your change is the only one since last spades upload.  I patched
> these out along setting the package to ready it for upload; see
> what I mean:
>
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,8 +1,6 @@
> -spades (3.15.5+dfsg-3) UNRELEASED; urgency=medium
> -
> +spades (3.15.5+dfsg-3) unstable; urgency=medium
> +
>* Team upload.
> -
> -  [Bo YU]
>* Add fix-gcc13.patch to fix gcc-13 build issues. (Closes: 
> #1037863)
>
>   -- Bo YU   Thu, 20 Jul 2023 21:38:50 +0800
>
>
> Otherwise your bug fix is uploaded.
> Thank you for your contribution!

Thanks for your upload and fixed it for me. I will keep it mind.

BR,
Bo

>
> Have a nice day,  :)
> --
>   .''`.  Étienne Mollier 
>  : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
>  `. `'   sent from /dev/pts/2, please excuse my verbosity
>`-on air: Need - Entheogen

Bug#1041550: sensible-utils: Issues in man pages

[Helge Kreutzmann]

Package: sensible-utils
Version: 0.0.21
Severity: minor
Tags: patch

While updating the German translation I noticed the following issues
in the man pages. Since your e-mail provider blocks my e-mail, I
cannot send them directly but rather by this BTS:

Isseu: FIXME The number (here and the follwing lines) is not bold, e.g. 
B → B(7)
"B<$VISUAL> - see B"

"B<$EDITOR> - see B"

…

Issue: CONFORMS → CONFORMING
"CONFORMS TO"

Issue: Align string with updated string for sensible-pager
"sensible-browser - sensible web browsing"

Issue: Align string with updated string for sensible-pager
"sensible-pager - sensible paging"

Issue: Align string with updated string for sensible-pager
"sensible-terminal-emulator - sensible terminal emulator"

Once you fixed those, I gladly update the German translation as well.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1041270: dynarmic: broke ABI without SONAME bump

[Andrea Pappacoda]

On Sun, 16 Jul 2023 18:34:16 +0200 Sebastian Ramacher 
 wrote:

> Source: dynarmic
> Version: 6.4.8+ds-2
> Severity: serious
>
> 
https://ci.debian.net/data/autopkgtest/testing/amd64/y/yuzu/35884387/log.gz

>
>  60s yuzu-cmd: symbol lookup error: yuzu-cmd: undefined symbol: 
_ZN8Dynarmic3A327Context4RegsEv


Hi Sebastian, thanks for your report. I've uploaded a new version with 
a possible fix on Mentors, you can find it at 
. I've also attached a 
debdiff for your convenience.


Feel free to upload it to unstable if you find this solution 
reasonable. Since this is only a soname change, without any actual 
library change, I believe that uploading to experimental first is 
unnecessary.


If it doesn't look right to you, I'll be happy to hear your feedback :)

Thanks again!

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49

diff -Nru dynarmic-6.4.8+ds/debian/changelog dynarmic-6.4.8+ds/debian/changelog
--- dynarmic-6.4.8+ds/debian/changelog	2023-07-05 22:03:58.0 +0200
+++ dynarmic-6.4.8+ds/debian/changelog	2023-07-20 19:13:04.0 +0200
@@ -1,3 +1,9 @@
+dynarmic (6.4.8+ds-3) unstable; urgency=medium
+
+  * d/{control,patches}: set soversion to major.minor (Closes: #1041270)
+
+ -- Andrea Pappacoda   Thu, 20 Jul 2023 19:13:04 +0200
+
 dynarmic (6.4.8+ds-2) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru dynarmic-6.4.8+ds/debian/control dynarmic-6.4.8+ds/debian/control
--- dynarmic-6.4.8+ds/debian/control	2023-07-05 22:03:58.0 +0200
+++ dynarmic-6.4.8+ds/debian/control	2023-07-20 19:11:30.0 +0200
@@ -25,7 +25,7 @@
  In the pursuit of speed, some behavior not commonly depended upon is elided.
  Therefore this emulator does not match spec.
 
-Package: libdynarmic6
+Package: libdynarmic6.4
 Architecture: any-amd64 any-arm64
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends},
@@ -39,7 +39,7 @@
 Section: libdevel
 Architecture: any-amd64 any-arm64
 Depends: libboost-dev,
- libdynarmic6 (= ${binary:Version}),
+ libdynarmic6.4 (= ${binary:Version}),
  llvm-dev,
  ${misc:Depends}
 Description: ${source:Synopsis} - development
diff -Nru dynarmic-6.4.8+ds/debian/libdynarmic6.4.install dynarmic-6.4.8+ds/debian/libdynarmic6.4.install
--- dynarmic-6.4.8+ds/debian/libdynarmic6.4.install	1970-01-01 01:00:00.0 +0100
+++ dynarmic-6.4.8+ds/debian/libdynarmic6.4.install	2023-07-20 19:11:30.0 +0200
@@ -0,0 +1 @@
+usr/lib/*/libdynarmic.so.6.4*
diff -Nru dynarmic-6.4.8+ds/debian/libdynarmic6.install dynarmic-6.4.8+ds/debian/libdynarmic6.install
--- dynarmic-6.4.8+ds/debian/libdynarmic6.install	2023-07-05 22:03:58.0 +0200
+++ dynarmic-6.4.8+ds/debian/libdynarmic6.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/*/libdynarmic.so.6*
diff -Nru dynarmic-6.4.8+ds/debian/patches/series dynarmic-6.4.8+ds/debian/patches/series
--- dynarmic-6.4.8+ds/debian/patches/series	2023-07-05 22:03:58.0 +0200
+++ dynarmic-6.4.8+ds/debian/patches/series	2023-07-20 19:04:31.0 +0200
@@ -1 +1,2 @@
 revert-catch2-v3.patch
+soname.patch
diff -Nru dynarmic-6.4.8+ds/debian/patches/soname.patch dynarmic-6.4.8+ds/debian/patches/soname.patch
--- dynarmic-6.4.8+ds/debian/patches/soname.patch	1970-01-01 01:00:00.0 +0100
+++ dynarmic-6.4.8+ds/debian/patches/soname.patch	2023-07-20 19:06:45.0 +0200
@@ -0,0 +1,28 @@
+Description: build: set SOVERSION to major.minor
+ Dynarmic uses semantic versioning, restricting backwards-incompatible
+ changes to major releases. This backwards compatibility, though, refers
+ to API changes, and disregards ABI stability. Since having to maintain a
+ compatible ABI between major releases is somewhat of a pain, and it
+ arguably doesn't matter that much for dynarmic, setting the SOVERSION to
+ major.minor allows for breaking ABI changes to be made between feature
+ releases, and not only major ones.
+ .
+ To be clear, this patch doesn't try to enforce a new policy, but just
+ reflects how the project has handled ABI changes in the past. That is,
+ these kind of changes have been made already.
+Author: Andrea Pappacoda 
+Origin: upstream, https://github.com/merryhime/dynarmic/pull/758
+Bug-Debian: https://bugs.debian.org/1041270
+Last-Update: 2023-07-20
+
+--- dynarmic-6.4.8+ds.orig/src/dynarmic/CMakeLists.txt
 dynarmic-6.4.8+ds/src/dynarmic/CMakeLists.txt
+@@ -455,7 +455,7 @@ target_include_directories(dynarmic PUBL
+ )
+ set_target_properties(dynarmic PROPERTIES
+ VERSION ${dynarmic_VERSION}
+-SOVERSION ${dynarmic_VERSION_MAJOR}
++SOVERSION ${dynarmic_VERSION_MAJOR}.${dynarmic_VERSION_MINOR}
+ )
+ target_compile_options(dynarmic PRIVATE ${DYNARMIC_CXX_FLAGS})
+ target_link_libraries(dynarmic

Bug#1036676: transition: nvidia-cuda-toolkit 12

[Sebastian Ramacher]

On 2023-07-17 10:58:35 +0200, Andreas Beckmann wrote:
> On 11/07/2023 09.09, Sebastian Ramacher wrote:
> > Okay, please go ahead whenevery you are ready.
> 
> Everything should be ready to migrate. Maybe you can hint mumax3 temporarily
> out of testing, AUTORM would happen in two weeks.

Removal hint added.

Cheers
-- 
Sebastian Ramacher

Bug#1041546: marked as done (libreoffice: terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException')

[Rene Engelhard]

Hi,

Am 20.07.23 um 19:06 schrieb Debian Bug Tracking System:

Your message dated Thu, 20 Jul 2023 20:04:13 +0300
with message-id 

and subject line solved
has caused the Debian Bug report #1041546,
regarding libreoffice: terminate called after throwing an instance of 
'com::sun::star::container::NoSuchElementException'
to be marked as done.


You write:

"I am rarely using it and never touching config or anything. It just
upgraded automatically for a long time."


This should work... But automatically if it involves version updates 
IMHO is a bad idea in any case. One just does it for stable and 
security, maybe


"So there is simple solution:

apt-get purge libreoffice*
apt-get install libreoffice

And now it successfully starts.  Sorry."


OK. :)


Regards,


Rene

Bug#1041549: sensible-utils: [INTL:de] updated German man page translation

[Helge Kreutzmann]

Package: sensible-utils
Version: 0.0.21
Severity: wishlist
Tags: patch l10n

Please find the updated German man page translation for sensible-utils
attached.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of sensible-utils man page template to German
# Copyright (C) Helge Kreutzmann , 2011, 2017, 2021, 2023.
# This file is distributed under the same license as the sensible-utils package.
#
msgid ""
msgstr ""
"Project-Id-Version: sensible-utils man page 0.0.21\n"
"POT-Creation-Date: 2023-07-04 13:43+\n"
"PO-Revision-Date: 2023-07-19 20:39+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: utf-8\n"

#. type: TH
#: sensible-editor.man sensible-browser.man
#, no-wrap
msgid "SENSIBLE-EDITOR"
msgstr "SENSIBLE-EDITOR"

#. type: TH
#: sensible-editor.man sensible-terminal.man
#, no-wrap
msgid "28 Aug 2022"
msgstr "28. Aug. 2022"

#. type: TH
#: sensible-editor.man sensible-browser.man sensible-pager.man
#: select-editor.man sensible-terminal.man
#, no-wrap
msgid "Debian"
msgstr "Debian"

#. type: SH
#: sensible-editor.man sensible-browser.man sensible-pager.man
#: select-editor.man sensible-terminal.man
#, no-wrap
msgid "NAME"
msgstr "NAME"

#. type: Plain text
#: sensible-editor.man
msgid "sensible-editor - launch sensibly chosen text editor"
msgstr "sensible-editor - Starten eines sinnvoll ausgewählten Texteditors"

#. type: SH
#: sensible-editor.man sensible-browser.man sensible-pager.man
#: select-editor.man sensible-terminal.man
#, no-wrap
msgid "SYNOPSIS"
msgstr "ÜBERSICHT"

#. type: Plain text
#: sensible-editor.man
msgid "B [OPTIONS...]"
msgstr "B [OPTIONEN …]"

#. type: SH
#: sensible-editor.man sensible-browser.man sensible-pager.man
#: select-editor.man sensible-terminal.man
#, no-wrap
msgid "DESCRIPTION"
msgstr "BESCHREIBUNG"

#. type: Plain text
#: sensible-editor.man
msgid ""
"B makes sensible decisions on which editor to call.  "
"Programs in Debian can invoke this script to get a good default editor."
msgstr ""
"B trifft sinnvolle Entscheidungen, welcher Editor "
"aufgerufen wird. Programme in Debian können dieses Skript aufrufen, um einen "
"guten Vorgabe-Editor zu erhalten."

#. type: Plain text
#: sensible-editor.man
msgid ""
"B looks for an appropriate choice of editor in a series of "
"places, and uses the first candidate that works.  It starts by checking "
"environment variables, followed by a variable defined via B "
"then tries the default editor command defined by the alternatives system, "
"with a series of hard-coded command names as fallbacks."
msgstr ""
"B sucht an einer Reihe von Stellen nach einer geeigneten "
"Wahl für einen Editor und verwendet den ersten funktionierenden Kandidaten. "
"Zuerst überprüft er die Umgebungsvariablen, gefolgt von einer mittels 
B definierten Variablen. Anschließend wird der durch das Alternatives-"
"System definierte Vorgabe-Editor versucht. Eine Reihe von hartkodierten "
"Befehlsnamen dienen als Rückfalloptionen."

#. type: Plain text
#: sensible-editor.man
msgid ""
"Variables will be skipped if unset or null, but may include extra whitespace-"
"separated parameters such as a I<--verbose> flag.  Once B "
"has a candidate commandline, it will try to run it (passing on the arguments "
"it was given as the files to be edited).  If this fails because the command "
"couldn't be executed (exit code 126)  or was not found (exit code 127), it "
"tries the next candidate."
msgstr ""
"Variablen werden übersprungen, falls sie nicht gesetzt oder Null sind. Sie "
"können aber zusätzliche, durch Leerraum getrennte Parameter wie den Schalter "
"»I<--verbose>« enthalten. Sobald B eine sinnvolle "
"Kandidaten-Befehlszeile ermittelt hat, wird es versuchen, diese auszuführen "
"(wobei die an es übergebenen Argumente als zu bearbeitende Dateien "
"angegeben werden). Falls dies fehlschlägt, da der Befehl nicht ausgeführt "
"werden konnte (Exit-Code 126) oder nicht gefunden wurde (Exit-Code 127), "
"wird es den nächsten Kandidaten ausprobieren."

#. type: Plain text
#: sensible-editor.man
msgid "The specific candidates B tries, in order, are:"
msgstr ""
"Die in dieser Reihenfolge von B versuchten Kandidaten sind:"

#. type: IP
#: sensible-editor.man
#, no-wrap
msgid "\\(bu"
msgstr "\\(bu"

# FIXME The number (here and the follwing lines) is not bold, e.g. 
B → B(7)
#. type: Plain text
#: sensible-editor.man
msgid "B<$VISUAL> - see B"
msgstr "B<$VISUAL> - siehe B(7)"

#. type: Plain text
#: sensible-editor.man
msgid "B<$EDITOR> - see B"
msgstr "B<$EDITOR> - siehe B(7)"

#. type: Plain text
#: sensible-editor.man
msgid "B<$SENSIBLE_EDITOR>"
msgstr "B<$SENSIBLE_EDITOR>"

#. type: Plain text
#: sensible-editor.man
msgid 

Bug#1041541: ffmpeg: libsvtav1 encoding broken

[Sebastian Ramacher]

On 2023-07-20 17:16:38 +0200, Wouter Verhelst wrote:
> Package: ffmpeg
> Version: 7:5.1.3-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I ran the following on a bookworm machine:
> 
> ffmpeg -i foo.mp4 -c:a libopus -c:v libsvtav1 -crf 35 -preset 8 -y foo.webm
> 
> This proceeded to encode the video in AV1. However, when I tried the
> same on unstable, I received the following output:
> 
> wouter@pc220518:~$ ffmpeg -i foo.mp4 -c:a libopus -c:v libsvtav1 -preset 8 
> -crf 35 -y foo.webm
> ffmpeg version 5.1.3-1 Copyright (c) 2000-2022 the FFmpeg developers
>   built with gcc 12 (Debian 12.2.0-14)
>   configuration: --prefix=/usr --extra-version=1 --toolchain=hardened 
> --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu 
> --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa 
> --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b 
> --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d 
> --enable-libflite --enable-libfontconfig --enable-libfreetype 
> --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm 
> --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg 
> --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq 
> --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy 
> --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh 
> --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab 
> --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 
> --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq 
> --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl 
> --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl 
> --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 
> --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r 
> --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
>   libavutil  57. 28.100 / 57. 28.100
>   libavcodec 59. 37.100 / 59. 37.100
>   libavformat59. 27.100 / 59. 27.100
>   libavdevice59.  7.100 / 59.  7.100
>   libavfilter 8. 44.100 /  8. 44.100
>   libswscale  6.  7.100 /  6.  7.100
>   libswresample   4.  7.100 /  4.  7.100
>   libpostproc56.  6.100 / 56.  6.100
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'foo.mp4':
>   Metadata:
> major_brand : isom
> minor_version   : 512
> compatible_brands: isomiso2avc1mp41
> title   : Make the code work for you: Flutter Code Generation
> date: 2022-02-05
> encoder : Lavf58.45.100
>   Duration: 00:38:59.68, start: 0.00, bitrate: 564 kb/s
>   Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), 
> yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 430 kb/s, 24.98 fps, 25 
> tbr, 12800 tbn (default)
> Metadata:
>   handler_name: VideoHandler
>   vendor_id   : [0][0][0][0]
>   Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 96000 Hz, mono, 
> fltp, 125 kb/s (default)
> Metadata:
>   handler_name: SoundHandler
>   vendor_id   : [0][0][0][0]
> Stream mapping:
>   Stream #0:0 -> #0:0 (h264 (native) -> av1 (libsvtav1))
>   Stream #0:1 -> #0:1 (aac (native) -> opus (libopus))
> Press [q] to stop, [?] for help
> [libopus @ 0x564c58b50d80] No bit rate set. Defaulting to 64000 bps.
> Svt[info]: ---
> Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.6.0
> Svt[info]: SVT [build]  : GCC 12.3.0   64 bit
> Svt[info]: ---
> Svt[error]: Instance 1:  MinQpAllowed must be smaller than MaxQpAllowed
> Svt[error]: Instance 1 : Invalid use_qp_file. use_qp_file must be [0 - 1]
> [libsvtav1 @ 0x564c58b51d80] Error setting encoder parameters: bad parameter 
> (0x80001005)
> Error initializing output stream 0:0 -- Error while opening encoder for 
> output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width 
> or height
> [libopus @ 0x564c58b50d80] 1 frames left in the queue on closing
> Conversion failed!
> 
> If any further information is required, please do not hesitate to let me
> know.

libsvtav1 broke its ABI without a transition. See #1041302.

Cheers
-- 
Sebastian Ramacher

Bug#1041332: mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg

[Andreas Beckmann]

On 20/07/2023 18.54, Eriberto Mota wrote:

Thanks a lot for spotting this issue. My current (emergency) plans:

1. Reopening the bug #1039103 and make it as wontfix, quoting #1040860.

no need to wontfix, we will just postpone the proper fix a bit

2. Reverting the changes in Sid.
better keep the changes for now, that should make it easier to recover 
sid from the mishandled conffile ...

3. Asking to Release Team how to proceed (is possible to drop the PU or
need I to send a new PU as a revision to revert the changes?).
IIRC it is possible to (temporary) cancel a PU request (by not letting 
it migrate from stable-proposed-updates to stable) ...

4. Making a new PU if needed.

... and replace it with a fixed one later

You probably need to rattle on the release team's door s.t. they take 
some action before it is too late ...



Andreas

PS: I'll be mostly afk next week ... will look into it thereafter

PPS: raw sketch for a better solution:
- use dpkg-maintscript-helper rm_conffile to get rid of the old one (if 
unmodified) or rename it to .dpkg-backup (if modified)
- if the .dpkg-backup exists, and the new conffile is still unmodified, 
replace it

-...
(unfortunately it's now too late for using dpkg-maintscript-helper 
mv_conffile)


Andreas

Bug#1041485: RFS: spades/3.15.5+dfsg-2.1 [NMU] [RC] -- genome assembler for single-cell and isolates data sets

[Étienne Mollier]

Hi,

Bo YU, on 2023-07-21:
> On Thu, Jul 20, 2023 at 5:34 PM Étienne Mollier  wrote:
> > Bo YU, on 2023-07-20:
> > > I will clean up the change for here and upstream.
> >
> > Sounds good, let us know once you pushed your modification.
> 
> I have updated it here:
> https://salsa.debian.org/med-team/spades
> 
> The only thing this is uncertain about is whether the distribution
> should be UNRELEASE or unstable
> in changelog. In Debian python team, it was `UNRELEASE` if team upload
> from non-DD/DM. So l use it there.

I'm fine with both convention; having a the changelog entry
stating "unstable" at least makes it clear the last person
having touched intended to have the package ready for upload.
The state can be reverted easily to UNRELEASED if something off
is noted.

By contrast the tag would be more problematic to remove after
being pushed to the VCS.  Personally, I usually run dgit, which
does the tagging for me on upload, so always tag and push after
the actual upload of the package.

> Could you have a look?:)

The RC bug is appropriately addressed, well done!

The only issues I caught were some trailing blank spaces in the
changelog, and the named log entry was a bit redundant since
your change is the only one since last spades upload.  I patched
these out along setting the package to ready it for upload; see
what I mean:

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,6 @@
-spades (3.15.5+dfsg-3) UNRELEASED; urgency=medium
-  
+spades (3.15.5+dfsg-3) unstable; urgency=medium
+
   * Team upload.
-  
-  [Bo YU]
   * Add fix-gcc13.patch to fix gcc-13 build issues. (Closes: #1037863)
 
  -- Bo YU   Thu, 20 Jul 2023 21:38:50 +0800


Otherwise your bug fix is uploaded.
Thank you for your contribution!

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Need - Entheogen


signature.asc
Description: PGP signature

Bug#1041548: synaptic: home page link fails if FireFox open

[jtl]

Package: synaptic
Version: 0.91.3
Severity: normal
X-Debbugs-Cc: jt...@yahoo.com

Dear Maintainer,

If FireFox is open and you click the Home Page link in Synaptic Package Manger, 
you get a the message dialog 
“Firefox is already running, but is not responding. To use Firefox, you must 
first close the existing Firefox 
process, restart your device, or use a different profile.”

If FireFox is closed, works as expected.

-- System Information:
Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-pkg6.02.6.1
ii  libc62.36-9
ii  libept1.6.0  1.2.1
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvte-2.91-00.70.3-1
ii  libxapian30  1.4.22-1
ii  pkexec   122-3
ii  policykit-1  122-3
ii  polkitd  122-3

Versions of packages synaptic recommends:
ii  libgtk3-perl  0.038-3
ii  xdg-utils 1.1.3-4.1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
ii  software-properties-gtk  0.99.30-4
ii  tasksel  3.73

-- no debconf information

Bug#1041547: login: I can login as root without password despite it being forbidden

[ircuser]

Package: login
Version: 1:4.13+dfsg1-1+b1
Severity: serious
X-Debbugs-Cc: ircu...@gmail.com

Dear Maintainer,

On a newly installed debian bookworm /usr/share/doc/passwd/NEWS.Debian.gz 
mentions a new PREVENT_NO_AUTH option that is supposed to prevent login to 
passwordless accounts.

The option is found in /etc/login.defs and has the default value:
PREVENT_NO_AUTH superuser

I removed root password using `passwd -d root` so that `grep root /etc/shadow` 
reads:
root::19519:0:9:7:::

I can now login to root on a tty just by typing root as the login name. I can 
also login to root just by typing `su` from a regular user account. 
"PREVENT_NO_AUTH superuser" has no effect.

I then changed the option to "PREVENT_NO_AUTH yes", which is supposed to 
prevent all passwordless account login.

I created a new user account `useradd -m -s /bin/bash testuser` and deleted its 
password `passwd -d testuser`. If I run `grep testuser /etc/shadow` it reads:
testuser::19558:0:9:7:::

I can now also login to this account on a tty without any password. `su 
newuser` also doesn't need any password. I can also still login to the root 
account by doing `su`.

https://sources.debian.org/src/shadow/1:4.13+dfsg1-1/src/su.c/?hl=504#L504

and

https://sources.debian.org/src/shadow/1:4.13+dfsg1-1/src/login.c/?hl=980#L980

indicate that this should not be possible. It looks like PREVENT_NO_AUTH 
doesn't do anything at all.

This was replicated on IRC by another user too.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C, 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 login depends on:
ii  libaudit1   1:3.0.9-1
ii  libc6   2.36-9
ii  libcrypt1   1:4.4.33-2
ii  libpam-modules  1.5.2-6
ii  libpam-runtime  1.5.2-6
ii  libpam0g1.5.2-6

login recommends no packages.

login suggests no packages.

-- Configuration Files:
/etc/login.defs changed:
MAIL_DIR/var/mail
FAILLOG_ENAByes
LOG_UNKFAIL_ENABno
LOG_OK_LOGINS   no
SYSLOG_SU_ENAB  yes
SYSLOG_SG_ENAB  yes
FTMP_FILE   /var/log/btmp
SU_NAME su
HUSHLOGIN_FILE  .hushlogin
ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ENV_PATHPATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
TTYGROUPtty
TTYPERM 0600
ERASECHAR   0177
KILLCHAR025
UMASK   022
PASS_MAX_DAYS   9
PASS_MIN_DAYS   0
PASS_WARN_AGE   7
UID_MIN  1000
UID_MAX 6
SUB_UID_MIN10
SUB_UID_MAX 60010
SUB_UID_COUNT   65536
GID_MIN  1000
GID_MAX 6
SUB_GID_MIN10
SUB_GID_MAX 60010
SUB_GID_COUNT   65536
LOGIN_RETRIES   5
LOGIN_TIMEOUT   60
CHFN_RESTRICT   rwh
DEFAULT_HOMEyes
USERGROUPS_ENAB yes
ENCRYPT_METHOD SHA512
NONEXISTENT /nonexistent
PREVENT_NO_AUTH yes


-- no debconf information

Bug#1041525: ITP: arcos-desktop -- The ArcOS Project

[Izaak Kuipers]

Although it hasn't been publicly announced yet, from version 5.0.8 onwards 
we'll be supplying Debian packages alongside Windows, AppImages and RPM 
packages. It's my fault for not referencing this change in the original report.

On Thu, 20 Jul 2023 09:21:57 -0300 David Bremner  wrote:
> Izaak Kuipers  writes:
>
> > ArcOS is an Operating System Environment built using web technologies. It 
> > uses
> > svelte, making it easy to maintain and blazingly fast. For more information
> > about the ArcOS project, be sure to check out the website. The ArcOS team is
> > also ready to talk to you through our Discord server!
>
> Since you currently only supply windows MSI installers, perhaps you can
> fill us in a bit on how you plan to package ArcOS for Debian. Perhaps
> more importantly, maybe you can explain what advantage being shipped
> with Debian will provide for users; what kind of OS integration is
> possible, and why would installing via debian be better than installing
> a package from your site as is currently done for Windows.
>
>

Bug#1040633: pilkit autopkg tests fail with pillow 10.0.0

[Dan Bungert]

Upstream proposal resolves this:

https://github.com/matthewwithanm/pilkit/pull/66/commits/e2eb73e1798865a201e570fced0bac195b2a590c

-Dan

Bug#1037586: ayatana-indicator-session: ftbfs with GCC-13

[Jeremy Bícha]

I think this is a more helpful build log excerpt:

/<>/tests/backend-dbus/mock-login1-seat.cc: In member
function ‘GVariant* MockLogin1Seat::list_sessions()’:
/<>/tests/backend-dbus/mock-login1-seat.cc:122:30: error:
‘uint32_t’ was not declared in this scope
  122 |  uint32_t(it.second->uid()),
  |  ^~~~
/<>/tests/backend-dbus/mock-login1-seat.cc:24:1: note:
‘uint32_t’ is defined in header ‘’; did you forget to
‘#include ’?
   23 | #include "mock-user.h"
  +++ |+#include 
   24 |

Thank you,
Jeremy Bícha

Bug#1041533: xen-system-amd64: Xen fails to start hvm type VMs when a vncpasswd is set

[zithro]

Hello,

I -think- VNC auth has been removed from the last QEMU versions.
Also maybe related, QEMU in Debian is not configured with VNC_SASL 
(there was a discussion about it in #debian-xen).


Wait for confirmations, meanwhile there is another option: SSH (maybe 
even more secure ?).


The workaround is to make the VNC servers only accessible from dom0, 
then to create SSH tunnels to connect to them :


1. in the domU config file, select "127.0.0.1" as the IP address to 
listen to, and remove everything about authentication
2. from your management host, create a tunnel, something like "ssh -nN 
-L localhost:12345:localhost:59xx user@dom0"

3. from your management host, use VNC_APP:12345 to connect to the display

The "xx" for the tunnel represent the "VNC display id" you've chosen in 
your domU config file, so if you have "vnclisten = 127.0.0.1:12", the 
real IP address is "127.0.0.1:5912" (in your case, you'd pick 5901).


Hope it helps.

PS: as for documentation it will be in the new Debian Xen wiki page 
(which I'm rewriting, for now it's still an offline draft).


--
Cyril Rébert / zithro

Bug#1030895: qt6-webengine: Enable riscv64 support

[Bo YU]

Hi!

On Thu, Jul 20, 2023 at 10:15 PM Patrick Franz  wrote:
>
> Hi,
>
> On Sat, 15 Apr 2023 23:32:53 +0800 Bo YU  wrote:
> [...]
> > Could you try it on the next upload?
> >
> > Thanks again for all here.
>
> Before we can consider applying this patch, there is the question of
> maintenance. I am not very keen on having a 12.000-line patch to
> maintain for qtwebengine which in itself is already hard to maintain.
>
> Just for fun, I tried to apply the patch to the recently released Qt
> Webengine 6.5.2 and unfortunately, a significant number of hunks from
> various subpackages could not be applied and would have to be
> readjusted. I'm afraid we'll run into the very same problem for each new
> Qt release. And that makes such a patch unsuitable.

Thanks for the heads up. Maintaining such a large patch is quite unsuitable.
Packaging Chromium has the same issue, but it has fewer lines patch than here.
The major issue is to have conflict with ppc64's patch.

It is wise to push these changes to Chromium upstream. But it will
cost a long time maybe.
>
> So, unless you have an idea how to avoid running into this problem...
Okay, let me think about a workaround before upstream supports this.
Thanks again.

Bo
>
>
> --
> Med vänliga hälsningar
>
> Patrick Franz
>
> --
> To unsubscribe, send mail to 1030895-unsubscr...@bugs.debian.org.

Bug#1041332: mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg

[Eriberto Mota]

Hi Andreas,

On Mon, 17 Jul 2023 17:22:21 +0200
Andreas Beckmann  wrote:

> Package: mrtg
> Version: 2.17.10-5+deb12u1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 1040860 with -1
> 
> Hi,
> 
> during a test with piuparts I noticed your package modifies conffiles.
> This is forbidden by the policy, see
> https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

[...]
 
> I'd suggest to withdraw the 2.17.10-5+deb12u1 bookworm-pu update and
> revisit that for the next point release (there is no time left to fix
> this properly before saturday). I have some idea how this could be
> solved better, but I need to try that first.

Thanks a lot for spotting this issue. My current (emergency) plans:

1. Reopening the bug #1039103 and make it as wontfix, quoting #1040860.
2. Reverting the changes in Sid.
3. Asking to Release Team how to proceed (is possible to drop the PU or
   need I to send a new PU as a revision to revert the changes?).
4. Making a new PU if needed.

What you think about this?

Regards,

Eriberto

Bug#1041546: libreoffice: terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException'

[Rene Engelhard]

Hi,

Am 20.07.23 um 18:42 schrieb Rene Engelhard:

To compare: You can't also break apache config or merge new config stuff

   ^ not

Regards,


Rene

Bug#1041546: libreoffice: terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException'

[Rene Engelhard]

Hi,

To clarify and compare the scenario:

So wjhat did you change there and did you merge stuff added there when 
ucf prompted you do do so?

[...]
Please try with a clean config, merginConfiguration file Package Exists 
Changed g actual updates into them when you update. That is *YOUR* 
reponsibility as an admin.


In any case, "of course" a clean LO in sid starts up just fine.


To compare: You can't also break apache config or merge new config stuff 
in there and complain that apache doesn't start anymore. Or for any 
other service.


This config is in /etc because it's configuration. Like e.g. apache2.
You could change it, yes. (even though it affects stuff in the user 
config only if that user config never got created already...)
But that doesn't mean you can do anything with it, and this doesn't mean 
you  can leave out stuff there added in newer LibreOffice versions 
because as we see stuff relies on keys present.


That's why this uses ucf. It has even a three-way merge option...

Regards,


Rene

Bug#1041546: libreoffice: terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException'

[Rene Engelhard]

severity 1041546 important

tag  1041546 + moreinfo

tag 1041546 + unreproducible

thanks


Hi,

Am 20.07.23 um 18:19 schrieb Vladmimir Stavrinov:

Package: libreoffice
Version: 4:7.5.5~rc2-1
Severity: grave
Justification: renders package unusable


I do not think so.



Just won't start (hang forever) while issuing the subject.


NoSuchElementException?


/etc/libreoffice/registry/writer.xcd  libreoffice-writer  YesYes


So wjhat did you change there and did you merge stuff added there when 
ucf prompted you do do so?


Probably even manually.

That config is not willy-nilly, it is also needed for proper startup.

I bet you didn't merge needed keys for startup.


Configuration filePackage Exists Changed
/etc/libreoffice/registry/calc.xcdlibreoffice-calcYesYes

Same here.

Configuration filePackage Exists Changed
/etc/libreoffice/registry/draw.xcdlibreoffice-drawYesYes
/etc/libreoffice/registry/graphicfilter.xcd   libreoffice-drawYes
Yes1041546


and here.


ii  glx-alternative-nvidia   1.2.2  
amd64allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia-tesla-470-0:amd64  470.199.02-1   
amd64NVIDIA binary EGL library (Tesla 470 version)
ii  libgl1-nvidia-tesla-470-glvnd-glx:amd64  470.199.02-1   
amd64NVIDIA binary OpenGL/GLX library (GLVND variant) 
(Tesla 470 version)
ii  libgles-nvidia-tesla-470-1:amd64 470.199.02-1   
amd64NVIDIA binary OpenGL|ES 1.x library (Tesla 470 version)
ii  libgles-nvidia-tesla-470-2:amd64 470.199.02-1   
amd64NVIDIA binary OpenGL|ES 2.x library (Tesla 470 version)
ii  libglx-nvidia-tesla-470-0:amd64  470.199.02-1   
amd64NVIDIA binary GLX library (Tesla 470 version)
ii  libnvidia-egl-wayland1:amd64 1:1.1.10-1 
amd64Wayland EGL External Platform library -- shared library
ii  libnvidia-tesla-470-cfg1:amd64   470.199.02-1   
amd64NVIDIA binary OpenGL/GLX configuration library (Tesla 
470 version)
ii  libnvidia-tesla-470-cuda1:am1041546d64  470.199.02-1
   amd64NVIDIA CUDA Driver Library (Tesla 470 version)
ii  libnvidia-tesla-470-eglcore:amd64470.199.02-1   
amd64NVIDIA binary EGL core libraries (Tesla 470 version)
ii  libnvidia-tesla-470-glcore:amd64 470.199.02-1   
amd64NVIDIA binary OpenGL/GLX core libraries (Tesla 470 
version)
ii  libnvidia-tesla-470-glvkspirv:amd64  470.199.02-1   
amd64NVIDIA binary Vulkan Spir-V compiler library (Tesla 
470 version)
ii  libnvidia-tesla-470-ml1:amd64470.199.02-1   
amd64NVIDIA Management Library (NVML) runtime library 
(Tesla 470 version)
ii  libnvidia-tesla-470-ptxjitcompiler1:amd64470.199.02-1   
amd64NVIDIA PTX JIT Compiler library (Tesla 470 version)
ii  libnvidia-tesla-cfg1:amd64   525.125.06-1   
amd64NVIDIA binary OpenGL/GLX configuration library (Tesla 
version)
ii  nvidia-egl-common525.125.06-1   
amd64NVIDIA binary EGL driver - common files
ii  nvidia-installer-cleanup 20220217+3 
amd64cleanup after driver installation with the 
nvidia-installer
ii  nvidia-kernel-common 20220217+3 
amd64NVIDIA binary kernel module support files
ii  nvidia-modprobe  535.54.03-1
amd64utility to load NVIDIA kernel modules and create 
device nodes
ii  nvidia-persistenced  525.85.05-1
amd64daemon to maintain persistent software state in the 
NVIDIA driver
ii  nvidia-settings-tesla-470470.161.03-1   
amd64tool for configuring the NVIDIA graphics driver (Tesla 
470 version)
ii  nvidia-support   20220217+3 
amd64NVIDIA binary graphics driver support files
ii  nvidia-tesla-470-alternative 470.199.02-1   
amd64allows the selection of NVIDIA as GLX provider (Tesla 
470 version)
ii  nvidia-tesla-470-driver  470.199.02-1   
amd64NVIDIA metapackage 

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Andrea Pappacoda]

On Sun, 16 Jul 2023 16:07:00 +0200 Sebastian Ramacher 
 wrote:

> Source: cpp-httplib
> Version: 0.13.1+ds-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in 
the past)

>
> When starting an uncoordinated transition, please at least ensure 
that

> the package at least builds on all suported platforms.

Hi Sebastian, thanks for the report. It isn't easy for me to test that 
cpp-httplib's test suite passes on all architectures, since I only have 
access to amd64 machines. Nonetheless, I'll look into this as soon as 
possible.


Thanks again!

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49

Bug#1041485: RFS: spades/3.15.5+dfsg-2.1 [NMU] [RC] -- genome assembler for single-cell and isolates data sets

[Bo YU]

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

Hi!

On Thu, Jul 20, 2023 at 5:34 PM Étienne Mollier  wrote:
>
> Hi Bo,
>
> Bo YU, on 2023-07-20:
> > On Thu, Jul 20, 2023 at 2:27 AM Étienne Mollier  wrote:
...
>
> In case your haven't come by it yet, you can have a look and
> bookmark the Debian Med policy manual here[1].  These guidelines
> ensure rough consistency between packages under Debian Med
> umbrella; there are about one thousand and a half.
>
> [1]: https://med-team.pages.debian.net/policy/
>
> If you agree to it, please feel free to proceed, git easily

I have read the policy and accepted it.

> allows reverting changes anyway; just don't force push without
> discussing the matter on the mailing list first.
>
...
> > I will clean up the change for here and upstream.
>
> Sounds good, let us know once you pushed your modification.

I have updated it here:
https://salsa.debian.org/med-team/spades

The only thing this is uncertain about is whether the distribution
should be UNRELEASE or unstable
in changelog. In Debian python team, it was `UNRELEASE` if team upload
from non-DD/DM. So l use it there.
Could you have a look?:)

BR,
Bo
>
> Have a nice day,  :)
> --
>   .''`.  Étienne Mollier 
>  : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
>  `. `'   sent from /dev/pts/2, please excuse my verbosity
>`-on air: Neal Morse - So Many Roads

Bug#1041413: Package: distrobox; Missing dependency: uidmap

[Doug Baggett]

No problem! I just wanted to clarify something else. The uidmap package is
installed by default on Debian 12, at least it was for me. However, I
encountered an issue when testing Distrobox on MX Linux 23 RC2. MX Linux
uses Debian's repositories, but it seems that they don't install uidmap by
default like Debian 12 does. I discovered this when I installed Distrobox
on MX Linux and tried to create a container. That's when I encountered the
newidmap error and realized it was because MX Linux didn't have uidmap
installed, and Distrobox didn't list it as a dependency.

I reported it to the MX Linux devs and they suggested I file a report.

On Thu, Jul 20, 2023 at 11:41 AM Michel Alexandre Salim <
mic...@michel-slm.name> wrote:

> Hi Doug,
>
> On Tue, Jul 18, 2023 at 12:38:46PM -0400, Doug Baggett wrote:
> > Package: distrobox
> > Version: 1.4.2.1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I am reporting a missing dependency issue with distrobox on Debian 12.
> The
> > uidmap package is required but not listed as a dependency. This causes
> > problems when trying to use distrobox, as it cannot function properly
> > without it.
> >
> > Please add it as a dependency for distrobox to resolve this issue.
> >
> > Thank you for your attention to this matter!
> >
> Thank you for catching this! Since bookworm is in full freeze I'll do a
> bugfix for this and do an update in unstable to the newer 1.5 release
> later.
>
> Thanks,
>
> --
> Michel Alexandre Salim
> identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
>

Bug#1041546: libreoffice: terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException'

[Vladmimir Stavrinov]

Package: libreoffice
Version: 4:7.5.5~rc2-1
Severity: grave
Justification: renders package unusable

Just won't start (hang forever) while issuing the subject.


-- Package-specific info:
All deployed bundled extensions:

Identifier: com.sun.star.comp.Calc.NLPSolver
  Version: 0.9
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: This extension integrates into Calc and offers new Solver 
engines to use for optimizing nonlinear programming models.

  bundled Packages: {
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/help
  is registered: yes
  Media-Type: application/vnd.sun.star.help
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/components.rdb
  is registered: yes
  Media-Type: application/vnd.sun.star.uno-components
  Description: 

  }

Identifier: com.sun.wiki-publisher
  Version: 1.2.0
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: The Wiki Publisher enables you to create Wiki articles on 
MediaWiki servers without having to know the syntax of the MediaWiki markup 
language. Publish your new and existing documents transparently with the Writer 
to a wiki page.

  bundled Packages: {
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/help
  is registered: yes
  Media-Type: application/vnd.sun.star.help
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcs
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-schema
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiEditor/
  is registered: yes
  Media-Type: application/vnd.sun.star.basic-library
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/components.rdb
  is registered: yes
  Media-Type: application/vnd.sun.star.uno-components
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Addons.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/ProtocolHandler.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/OptionsDialog.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Filter.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Types.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Paths.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  }

All deployed shared extensions:


All deployed user extensions:



Experimental features enabled:

Installed VCLplugs:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----=
un  libreoffice-gtk3   (no description available)
un  libreoffice-kf5(no description available)
un  libreoffice-qt5(no description available)

Java (javaldx):
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/client:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/native_threads:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64

Java:
http://openoffice.org/2004/java/framework/1.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>

file:///usr/lib/jvm/java-8-openjdk-amd64/jre


Configuration filePackage Exists Changed
/etc/libreoffice/registry/writer.xcd  libreoffice-writer  YesYes
All deployed bundled extensions:

Identifier: com.sun.star.comp.Calc.NLPSolver
  Version: 0.9
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: This extension integrates into Calc and offers new Solver 
engines to use for optimizing nonlinear programming models.

  bundled Packages: {
  URL: 

Bug#1041545: [stunnel4] Fails to recognize EOF on a TLS socket without a proper TLS shutdown

[Peter Pentchev]

Package: stunnel4
Version: 3:5.68-2
Severity: important
Tags: patch upstream
X-Debbugs-Cc: r...@debian.org

In versions before 5.70, stunnel4 fails to recognize a new OpenSSL 3.x
error code that signals that the remote side closed the network
connection without performing a proper TLS shutdown. Instead, stunnel
treats this situation as an error.

If there was any pending data that the stunnel service had enqueued for
sending over the encrypted connection, it is discarded, so if the TLS
session is later resumed, the encrypted data stream will be corrupted.

This is fixed in stunnel-5.70 by a block of code in the src/client.c
file handling the SSL_R_UNEXPECTED_EOF_WHILE_READING error constant.


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.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 stunnel4 depends on:
ii  adduser 3.134
ii  init-system-helpers 1.65.2
ii  libc6   2.37-5
ii  libssl3 3.0.9-1
ii  libsystemd0 253.5-1
ii  libwrap07.6.q-32
ii  netbase 6.4
ii  openssl 3.0.9-1
ii  perl5.36.0-7
ii  systemd [systemd-sysusers]  253.5-1

stunnel4 recommends no packages.

Versions of packages stunnel4 suggests:
pn  logcheck-database  

-- no debconf information



signature.asc
Description: PGP signature

Bug#1041413: Package: distrobox; Missing dependency: uidmap

[Michel Alexandre Salim]

Hi Doug,

On Tue, Jul 18, 2023 at 12:38:46PM -0400, Doug Baggett wrote:
> Package: distrobox
> Version: 1.4.2.1
> Severity: important
> 
> Dear Maintainer,
> 
> I am reporting a missing dependency issue with distrobox on Debian 12. The
> uidmap package is required but not listed as a dependency. This causes
> problems when trying to use distrobox, as it cannot function properly
> without it.
> 
> Please add it as a dependency for distrobox to resolve this issue.
> 
> Thank you for your attention to this matter!
>
Thank you for catching this! Since bookworm is in full freeze I'll do a
bugfix for this and do an update in unstable to the newer 1.5 release
later.

Thanks,

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: PGP signature

Bug#1037747: libwebsockets: diff for NMU version 4.1.6-4

[Gianfranco Costamagna]

Control: tags 1037747 + patch
Control: tags 1037747 + pending

Dear maintainer,

I've prepared an NMU for libwebsockets (versioned as 4.1.6-4) and
uploaded.

diff -Nru libwebsockets-4.1.6/debian/changelog 
libwebsockets-4.1.6/debian/changelog
--- libwebsockets-4.1.6/debian/changelog2022-08-07 10:46:31.0 
+0200
+++ libwebsockets-4.1.6/debian/changelog2023-07-20 17:27:19.0 
+0200
@@ -1,3 +1,12 @@
+libwebsockets (4.1.6-4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch:
+- cherry-pick upstream patch to fix a build failure with gcc-13
+  (Closes: #1037747)
+
+ -- Gianfranco Costamagna   Thu, 20 Jul 2023 
17:27:19 +0200
+
 libwebsockets (4.1.6-3) unstable; urgency=medium

   * Update self-testing.
diff -Nru 
libwebsockets-4.1.6/debian/patches/f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch
 
libwebsockets-4.1.6/debian/patches/f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch
--- 
libwebsockets-4.1.6/debian/patches/f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch
   1970-01-01 01:00:00.0 +0100
+++ 
libwebsockets-4.1.6/debian/patches/f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch
   2023-07-20 17:27:19.0 +0200
@@ -0,0 +1,30 @@
+From f9d1f25abe896b9fa1de780e4a5cb41116926a29 Mon Sep 17 00:00:00 2001
+From: Andy Green 
+Date: Wed, 14 Jun 2023 07:14:23 +0100
+Subject: [PATCH] openssl-server: enum vs int disagreement
+
+https://github.com/warmcat/libwebsockets/issues/2907
+---
+ lib/tls/openssl/openssl-server.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/lib/tls/openssl/openssl-server.c 
b/lib/tls/openssl/openssl-server.c
+index f2e77324f..1fc819293 100644
+--- a/lib/tls/openssl/openssl-server.c
 b/lib/tls/openssl/openssl-server.c
+@@ -607,13 +607,13 @@ lws_tls_server_new_nonblocking(struct lw
+   return 0;
+ }
+
+-int
++enum lws_ssl_capable_status
+ lws_tls_server_abort_connection(struct lws *wsi)
+ {
+   SSL_shutdown(wsi->tls.ssl);
+   SSL_free(wsi->tls.ssl);
+
+-  return 0;
++  return LWS_SSL_CAPABLE_DONE;
+ }
+
+ enum lws_ssl_capable_status
diff -Nru libwebsockets-4.1.6/debian/patches/series 
libwebsockets-4.1.6/debian/patches/series
--- libwebsockets-4.1.6/debian/patches/series   2020-09-08 01:12:45.0 
+0200
+++ libwebsockets-4.1.6/debian/patches/series   2023-07-20 17:27:19.0 
+0200
@@ -1,3 +1,4 @@
 #echo-actually-exit.patch
 #echo-off-by-one.patch
 #add-missing-headers.patch
+f9d1f25abe896b9fa1de780e4a5cb41116926a29.patch



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041043: samba domain netlogon broken after windows 10/11 Jul-2023 update

[Heil, Stefan]

Dear list / Samba maintainers,

Will the fix for this also make it into Bullseye / Samba 4.13? If so,
is there a (tentative) ETA?

I'm wondering if we can wait for the fix or if I need to install it
from bullseye-backports, which I am trying to avoid, if possible. 

Thank you!

Best,
Stefan

Bug#1041544: src:python-glance-store: fails to migrate to testing for too long: autopgktest regression on ppc64el and s390x

[Paul Gevers]

Source: python-glance-store
Version: 4.1.0-4
Severity: serious
Control: close -1 4.3.1-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-glance-store has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The autopkgtest of 
the version in unstable fails on ppc64el and s390x where it succeeded 
with older versions.


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=python-glance-store



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041538: dh-python: Unhelpful inclusion of optional packages in Depends

[Stefano Rivera]

Hi Piotr (2023.07.20_14:58:03_+)
> can you show me how poetry / pyproject / whatever parsed this file
> interpreted it? I.e. what's in installed requires.txt
> 
> (I suspect it's a hard dependency there)

Yep, that's the issue, METEDATA contains:

Requires-Dist: httpcore (>=0.17.3) ; python_version >= "3.8"
Requires-Dist: sniffio (>=1.1,<2.0)

I'd call this an upstream poetry issue.

It shouldn't declare optional dependencies as required. It should rather
create an extra to encapsulate any optional dependencies that aren't
part of a defined extra.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272