Bug#1035282: firmware-brcm80211: broken symlinks: /lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt

2023-04-29 Thread Salvatore Bonaccorso 
Hi,

On Sun, Apr 30, 2023 at 03:18:08AM +0200, Andreas Beckmann wrote:
> Package: firmware-brcm80211
> Version: 20230210-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> >From the attached log (scroll to the bottom...):
> 
> 0m14.9s ERROR: WARN: Broken symlinks:
>   /lib/firmware/brcm/brcmfmac4356-sdio.khadas,vim2.txt -> 
> brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)
>   /lib/firmware/brcm/brcmfmac4356-sdio.vamrs,rock960.txt -> 
> brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)
> 
> Severity serious, since this likely means that the kernel cannot find
> the firmware at the expected location.

Seems to be a consequence of upstream's change in 4ffcf980a535 ("brcm:
rename Rock960 NVRAM to AP6356S and link devices to it") in 20220411.

In the Debian packaging adding the nvram for 96boards Rock960,
happened in 20210208-1, so at least stable users indeed might suffer
from a problem switching from bullseye to bookworm. For the one with
khadas VIM2's WiFi,s there is no regreession at least as the symlink
was added in 20210511-1~exp1.

Will have a look.

Regards,
Salvatore

Bug#1030626: Unable to print PDF file with Evince on Gnome on Debian 12.

2023-04-29 Thread Serkan KURT 
Dear Maintainer,Unfortunately the problem persists.I reinstalled the system 
with the iso dated 2023-04-05. All updates have been made as of now.
yours sincerely

Bug#1035130: Don't reopen bugreports closed by the maintainer

2023-04-29 Thread Sandro Tosi 
the fact that you ignore part of your responsibilities as a Debian
package maintainer is already a pity, but the fact you're trying to
hide real problems in your packages as well as preventing others (not
only the maintainer or the submitter has the ability to provide
patches) from working on them, and on top of that severely
underestimating how the a _little_ help from every rdeps of numpy
vastly improves Debian's ability to upgrade that package, is simply
shameful.

I've reopened once again; if you don't have the technical abilities to
work on these bugs, that's fine, let others take care of them.

On Sun, Apr 30, 2023 at 12:31 AM Sebastiaan Couwenberg
 wrote:
>
> Reopening these bugreports won't get me to work on them.
>
> You'll need to provide patches for me to consider spending time on
> autopkgtests for these packages.
>
> Kind Regards,
>
> Bas
>
> --
>   GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1035294: grub2: [INTL:ru] Russian debconf templates translation update

2023-04-29 Thread Yuri Kozlov 
Package: grub2
Version: 2.06-13
Severity: wishlist
Tags: l10n patch

Russian debconf templates translation update is attached.


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

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


ru.po.gz
Description: application/gzip

Bug#1035293: gnome-shell-extension-arc-menu: Arc Menu search doesn't work in Bookworm

2023-04-29 Thread Trevor Clark 
Package: gnome-shell-extension-arc-menu
Version: 49+forkv29-3
Severity: important
X-Debbugs-Cc: r.trevor.cl...@gmail.com

Dear Maintainer,

   * When using the search functionality in Arc Menu the interface says
"Searching" but never returns any results.


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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-shell-extension-arc-menu depends on:
ii  gnome-shell  43.4-1

Versions of packages gnome-shell-extension-arc-menu recommends:
ii  gir1.2-gmenu-3.0  3.36.0-1.1

gnome-shell-extension-arc-menu suggests no packages.

-- no debconf information

Bug#905745: util-linux: tty hijacking possible in "su" via TIOCSTI ioctl

2023-04-29 Thread Salvatore Bonaccorso 
Control: reassign -1 src:util-linux

Hi Cris,

On Sat, Apr 29, 2023 at 11:47:40PM +0200, Chris Hofstaedtler wrote:
> Control: reassign -1 src:linux
> Control: affects -1 src:util-linux
> 
> Dear Kernel Maintainers, Security Team,
> 
> * Sam Morris :
> > Linux 6.2 introduces a sysctl dev.tty.legacy_tiocsti sysctl which can be
> > used to disable TIOCSTI. The default value of the sysctl is set at build
> > time with CONFIG_LEGACY_TIOCSTI.
> > 
> > 
> 
> Maybe we can get this into 6.1?

(For the metainformation I'm assigning it back to su, where the CVE(s)
originally got assigned, but we can close the bug in future once the
root issue is addressed on kernel side, I hope you are okay with
that).

It is unlikely we are going to enable this in bookworm, even if the
change will be backported to 6.1.y, that is if the change would now be
backported, I assume we will need to stick with the default being
enabled. The time was too narrow before the
freeze. But we have #1033095[1] for the corresponding bug on src:linux
and to disable TIOCSTI it early in the trixie development cycle by
default (which comes automatically).

 [1]: https://bugs.debian.org/1033095

Hope this helps so far?

Regards,
Salvatore

Bug#1033088: ntpsec: mssntp in ntp.conf breaks time service to all clients

2023-04-29 Thread Richard Laager 

On 4/29/23 21:54, Steven Monai wrote:
I downloaded and unpacked this source on a Bookworm host. The build 
system bundled with the source ("waf") seems to assume python 2.x, but, 
unfortunately, Bookworm provides only python3. Any hints?


Quick approach is try this:
python3 waf configure ...
python3 waf build

A longer, but possibly better, approach might be something like:
git clone g...@salsa.debian.org:debian/ntpsec.git
cd ntpsec
git checkout debian/1.1.3+dfsg1-1
debuild -uc -us

An intermediate approach might be to test with the binary package from 
buster. You can get download links here, by architecture, plus there are 
links to related packages, some of which (like python3-ntp) you might need:

https://packages.debian.org/buster/ntpsec

Hopefully this will turn out to be something broken during code 
cleanups/refactorings in NTPsec that you can bisect (at least somewhat).


--
Richard



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035292: debian-edu-fai: fails to purge - command (deluser|adduser) in postrm not found

2023-04-29 Thread Andreas Beckmann 
Package: debian-edu-fai
Version: 2022.04.14.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.

The fix should be easy: your package is using adduser or deluser from
the adduser package, which is only priority important. Using useradd or
userdel from the passwd package (priority required) should fix this
problem.

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833
Consensus seems to be not to remove system users (to avoid reusing UIDs
which could grant access to the wrong files) but to "lock" them (where
"locking"/"unlocking" is not yet precisely defined). Until that has
been decided it should be sufficient to have the postrm script ignore
any errors from deluser:
  deluser ... || true

>From the attached log (scroll to the bottom...):

0m20.1s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpephm8a0q', 'dpkg', '--purge', 'debian-edu-fai']
0m20.1s DUMP: 
  (Reading database ... 8077 files and directories currently installed.)
  Purging configuration files for debian-edu-fai (2022.04.14.1) ...
  /var/lib/dpkg/info/debian-edu-fai.postrm: 21: deluser: not found
  dpkg: error processing package debian-edu-fai (--purge):
   installed debian-edu-fai package post-removal script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   debian-edu-fai
0m20.1s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpephm8a0q', 'dpkg', '--purge', 'debian-edu-fai']


cheers,

Andreas


debian-edu-fai_2022.04.14.1.log.gz
Description: application/gzip

Bug#1035291: desktop-autoloader: fails to purge - command (deluser|adduser) in postrm not found

2023-04-29 Thread Andreas Beckmann 
Package: desktop-autoloader
Version: 0.0.4-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.

The fix should be easy: your package is using adduser or deluser from
the adduser package, which is only priority important. Using useradd or
userdel from the passwd package (priority required) should fix this
problem.

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833
Consensus seems to be not to remove system users (to avoid reusing UIDs
which could grant access to the wrong files) but to "lock" them (where
"locking"/"unlocking" is not yet precisely defined). Until that has
been decided it should be sufficient to have the postrm script ignore
any errors from deluser:
  deluser ... || true

>From the attached log (scroll to the bottom...):

0m21.8s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpb252mt2q', 'dpkg', '--purge', 
'desktop-autoloader']
0m21.8s DUMP:
  (Reading database ... 8072 files and directories currently installed.)
  Purging configuration files for desktop-autoloader (0.0.4-1) ...
  /var/lib/dpkg/info/desktop-autoloader.postrm: 25: deluser: not found
  dpkg: error processing package desktop-autoloader (--purge):
   installed desktop-autoloader package post-removal script subprocess returned 
error exit status 127
  Errors were encountered while processing:
   desktop-autoloader
0m21.8s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpb252mt2q', 'dpkg', '--purge', 
'desktop-autoloader']


cheers,

Andreas


desktop-autoloader_0.0.4-1.log.gz
Description: application/gzip

Bug#1035290: kismet: fails to purge - command (deluser|adduser) in postrm not found

2023-04-29 Thread Andreas Beckmann 
Package: kismet
Version: 2016.07.R1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.

The fix should be easy: your package is using adduser or deluser from
the adduser package, which is only priority important. Using useradd or
userdel from the passwd package (priority required) should fix this
problem.

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833
Consensus seems to be not to remove system users (to avoid reusing UIDs
which could grant access to the wrong files) but to "lock" them (where
"locking"/"unlocking" is not yet precisely defined). Until that has
been decided it should be sufficient to have the postrm script ignore
any errors from deluser:
  deluser ... || true

>From the attached log (scroll to the bottom...):

0m15.6s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp6_lhwlij', 'dpkg', '--purge', 'kismet']
0m15.6s DUMP:
  (Reading database ... 8069 files and directories currently installed.)
  Purging configuration files for kismet (2016.07.R1-1+b1) ...
  Cannot remove group kismet because delgroup command is not found
  dpkg: error processing package kismet (--purge):
   installed kismet package post-removal script subprocess returned error exit 
status 128
  Errors were encountered while processing:
   kismet
0m15.6s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp6_lhwlij', 'dpkg', '--purge', 'kismet']


cheers,

Andreas


kismet_2016.07.R1-1+b1.log.gz
Description: application/gzip

Bug#1033088: ntpsec: mssntp in ntp.conf breaks time service to all clients

2023-04-29 Thread Steven Monai 

On 2023-04-28 10:20 p.m., Richard Laager wrote:
Can you confirm whether you get either of these messages to stderr on 
startup:


A) MS-SNTP signd operations currently block ntpd degrading service to 
all clients.


Definitely this one, A.

Is there any chance you could test with ntpsec 1.1.3? You'd have to 
build from source (and note that upstream stores the config file in 
/etc/ntp, not /etc/ntpsec). It is available here:

https://ftp.ntpsec.org/pub/releases/ntpsec-1.1.3.tar.gz


I downloaded and unpacked this source on a Bookworm host. The build 
system bundled with the source ("waf") seems to assume python 2.x, but, 
unfortunately, Bookworm provides only python3. Any hints?


I've forwarded the bug 
upstream. You can see the URL in the control commands at the top of this 
message.


Thanks, much appreciated!

Cheers,
-S.M.

Bug#1035289: merecat: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/merecat/examples/merecat.conf

2023-04-29 Thread Andreas Beckmann 
Package: merecat
Version: 2.31+git20220513+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

>From the attached log (scroll to the bottom...):

  Setting up merecat (2.31+git20220513+ds-4) ...
  Error: The new file usr/share/doc/merecat/examples/merecat.conf does not 
exist!
  dpkg: error processing package merecat (--configure):
   installed merecat package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   merecat


Cheers,

Andreas


merecat_2.31+git20220513+ds-4.log.gz
Description: application/gzip

Bug#1035288: redmine-plugin-local-avatars: fails to install: LoadError: cannot load such file -- local_avatars

2023-04-29 Thread Andreas Beckmann 
Package: redmine-plugin-local-avatars
Version: 1.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up redmine (5.0.4-5) ...
  [ESC][33mDon't run Bundler as root. Bundler can ask for sudo if it is needed, 
and
  installing your bundle as root will break this application for all non-root
  users on this machine.[ESC][0m
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml with new version
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  rake aborted!
  LoadError: cannot load such file -- local_avatars
  
/usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in
 `require'
  
/usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in
 `require'
  /usr/share/redmine/plugins/redmine_local_avatars/init.rb:42:in `'
  /usr/share/redmine/lib/redmine/plugin_loader.rb:31:in `load'
  /usr/share/redmine/lib/redmine/plugin_loader.rb:31:in `run_initializer'
  /usr/share/redmine/lib/redmine/plugin_loader.rb:108:in `each'
  /usr/share/redmine/lib/redmine/plugin_loader.rb:108:in `block in load'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in
 `instance_exec'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in
 `block in make_lambda'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:198:in
 `block (2 levels) in halting'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:604:in
 `block (2 levels) in default_terminator'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in
 `catch'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in
 `block in default_terminator'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:199:in
 `block in halting'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in
 `block in invoke_before'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in
 `each'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in
 `invoke_before'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:105:in
 `run_callbacks'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/reloader.rb:88:in
 `prepare!'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application/finisher.rb:124:in
 `block in '
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in
 `instance_exec'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in
 `run'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:61:in
 `block in run_initializers'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:60:in
 `run_initializers'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application.rb:391:in
 `initialize!'
  /usr/share/redmine/config/environment.rb:16:in `'
  
/usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in
 `require'
  
/usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in
 `require'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:332:in
 `block in require'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:299:in
 `load_dependency'
  
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:332:in
 `require'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application.rb:367:in
 `require_environment!'
  
/usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'
  Tasks: TOP => db:migrate => db:load_config => environment
  (See full trace by running task with --trace)
  dpkg: error processing package redmine (--configure):
   installed redmine package post-installation script subprocess returned error 
exit status 1
  dpkg: dependency problems prevent configuration of 
redmine-plugin-local-avatars:
   redmine-plugin-local-avatars depends on

Bug#1035287: netopeer2: missing Depends: adduser

2023-04-29 Thread Andreas Beckmann 
Package: netopeer2
Version: 2.0.35-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up netopeer2 (2.0.35-1+b1) ...
  /var/lib/dpkg/info/netopeer2.postinst: 24: addgroup: not found
  dpkg: error processing package netopeer2 (--configure):
   installed netopeer2 package post-installation script subprocess returned 
error exit status 127
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   netopeer2


cheers,

Andreas


netopeer2_2.0.35-1+b1.log.gz
Description: application/gzip

Bug#1035286: dnssec-trigger: missing Depends: openssl

2023-04-29 Thread Andreas Beckmann 
Package: dnssec-trigger
Version: 0.17+repack-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up dnssec-trigger (0.17+repack-5+b2) ...
  setup in directory /etc/dnssec-trigger
  generating dnssec_trigger_server.key
  /usr/sbin/dnssec-trigger-control-setup: 196: openssl: not found
  /usr/sbin/dnssec-trigger-control-setup fatal error: could not genrsa
  dpkg: error processing package dnssec-trigger (--configure):
   installed dnssec-trigger package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   dnssec-trigger


cheers,

Andreas


dnssec-trigger_0.17+repack-5+b2.log.gz
Description: application/gzip

Bug#1034756: dpkg: please add support for riscv32

2023-04-29 Thread Bo YU 
Hi!

Sorry for the later reply.
On Thu, Apr 27, 2023 at 12:30 AM Jessica Clarke  wrote:
>
> On 26 Apr 2023, at 17:22, Bo YU  wrote:
> >
> > Hi,
> > On Tue, Apr 25, 2023 at 02:08:33PM -0400, Darius Rad wrote:
> >> On Tue, Apr 25, 2023 at 10:52:52PM +0800, Bo YU wrote:
> >>> On Tue, Apr 25, 2023 at 04:22:49AM +0200, Guillem Jover wrote:
> >>>
> >>> >
> >>> > > I thought the riscv32 has met the request[2] also.
> >>> >
> >>> > I assume the ABI is set in stone and well defined.
> >>> >
> >>
> >> There are three ABIs for 32-bit RISC-V.  They are well defined, but it is
> >> not clear which ABI is being proposed for Debian here.
> >>
> >>> > > Please let me know if there is any issue.
> >>> >
> >>> > I think at the time when we added riscv64 we didn't also add riscv32
> >>> > because it was not clear whether there was then interest or demand,
> >>> > and I don't recall whether there were concerns about what ISA baseline
> >>> > to choose? (But I guess this would use the default baseline specified
> >>> > currently by the compiler.)
> >>>
> >>> There is no doubt that the porting of riscv64 is our first priority and
> >>> it's already in a good shape -- except for the official port.:(
> >>>
> >>> For riscv32 case, I think it'd be pretty helpful to let users to setup
> >>> rv32 Debian rootfs or to let rv32 Debain run on RISC-V 32 bit hardware 
> >>> that
> >>> will be emerged in the near future.
> >>
> >> Do you have any references for this hardware?
> >
> > From my vague memory, there will be k230 fully support rv32 in userspace
> > from canaan. Sorry, I was trying to find news or useful url but fail
> > here.
>
> From what I can see it’s using a C908 which is RV64. Maybe it can also
> do RV32 if you switch mode, but why would you, just as we don’t
> recommend people run i386 on amd64.

I consulted relevant people on this topic. If running on rv32 mode, it will save
about 8% ddr.
>
> RV32-only Unix-capable hardware would be more interesting, but seems
> like a foolish thing to build in this decade.
>
> >>> Here I simply assume that rv32 compiler with `--with-arch=rv32gc
> >>> --with-abi=ilp32d`[0] is enough?
> >>>
> >>
> >> That is one choice, but not the only one.
> >>
> >> The argument in favor of a 32-bit port of RISC-V is typically motivated by
> >> the assumption that such processors will be smaller, in terms of the
> >> hardware (i.e., ASIC gates or FPGA LUTs).  However, as compared to rv64gc,
> >> eliminating floating point typically provides a much more significant
> >> decrease in size.  Thus, often when one is talking about smaller, 32-bit
> >> RISC-V processors, they *also* eliminate floating point.  In other words,
> >> the processors are rv32imac, not rv32gc.
> >>
> >> In fact, I wouldn't be surprised if rv64imac processors were more common
> >> than rv32gc, given the minimal hardware resources for 64-bit versus 32-bit,
> >> all else being equal.
> >
> > Thanks for explaining this. Here are some of my thoughts about it.
> >
> > I think, as a distribution, we should provide a basic baseline of
> > instruction set supported to cover most hardware vendors. We should not 
> > assume that hardware vendors will product their CPUs on a certain 
> > instruction
> > set.
>
> We should support hardware that does exist, not hardware that might
> exist. So long as there is no RV32-only Unix-capable hardware out
> there, what is the point in Debian producing a distribution?
Sorry, I do not understand correctly maybe here. If you talk about the point
of porting riscv32, porting one arch in emulators before real hardware
came out should be feasible. Now qemu can support rv32 and the upstream
toolchain is well also. Certainly, this is also the result of RISC-V people
supporting 64-bit and 32-bit from the beginning. On the other hand, as a
distribution, if we have the opportunity to get more people to choose Debian
over other distributions or yocto, the porting may also make sense from this
point of view.

If you talk about the baseline ABI according to hardware, yeah, this
is still open.

>
> > In addition, refer to other 32-bit architectures, like armhf[1] and 
> > mips[2], They are also supporting floating point instructions(IIUC).
>
> Because they date back to when 32-bit computing was common practice,
> and wanted floating-point. These days, 64-bit is the standard, and
> there is little motivation for building a 32-bit core with
> floating-point given the tiny additional area needed to make it 64-bit
> (especially since you already need 64-bit data paths for the D
> extension).
>
> > Also, keep
> > the same baseline with rv64, maybe it will reduce confusion for users.
> > I am not sure how much would we benefit from dropping support for 'F' or
> > 'D', but maybe we can't lost something if we support full set(rv32gc)
> > from port's view.
>
> If you’re going to provide a distribution for RV32, dropping F and D
> seems like the right thing to do, since that’s the only sensible thing
> to build hardware for. But

Bug#1035285: bit-babbler: missing Depends: adduser

2023-04-29 Thread Andreas Beckmann 
Package: bit-babbler
Version: 0.9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up bit-babbler (0.9) ...
  /var/lib/dpkg/info/bit-babbler.postinst: 104: addgroup: not found
  dpkg: error processing package bit-babbler (--configure):
   installed bit-babbler package post-installation script subprocess returned 
error exit status 127
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   bit-babbler


cheers,

Andreas


bit-babbler_0.9.log.gz
Description: application/gzip

Bug#1035284: znc: missing Depends: adduser

2023-04-29 Thread Andreas Beckmann 
Package: znc
Version: 1.8.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up znc (1.8.2-3+b4) ...
  /var/lib/dpkg/info/znc.postinst: 7: addgroup: not found
  dpkg: error processing package znc (--configure):
   installed znc package post-installation script subprocess returned error 
exit status 127
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   znc


cheers,

Andreas


znc_1.8.2-3+b4.log.gz
Description: application/gzip

Bug#1011900: monkeysphere: FTBFS: ...Could not chdir to home directory /home/user42: No such file or directory

2023-04-29 Thread James Valleroy 

tags 1011900 patch
thanks

I opened an MR to fix this issue:
https://salsa.debian.org/pkg-privacy-team/monkeysphere/-/merge_requests/1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035110: ITP: drminfo -- Small utility to dump info about DRM devices

2023-04-29 Thread Paul Wise 
On Sat, 2023-04-29 at 15:13 -0600, Rodrigo Siqueira wrote:

> * Package name    : drminfo
> * URL : https://gitlab.freedesktop.org/emersion/drm_info

This is already packaged in Debian as drm-info.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1035283: virtualbox-ext-pack: missing Depends: ca-certificates

2023-04-29 Thread Andreas Beckmann 
Package: virtualbox-ext-pack
Version: 7.0.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up virtualbox-ext-pack (7.0.8-1) ...
  virtualbox-ext-pack: downloading: 
https://download.virtualbox.org/virtualbox/7.0.8/Oracle_VM_VirtualBox_Extension_Pack-7.0.8.vbox-extpack
  The file will be downloaded into /usr/share/virtualbox-ext-pack
  Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-7.0.8.vbox-extpack: 
expected 452320f3b1da42b30c32ea5ab5887983b575638ceb4e3beacfefbbb3b0510a48, 
removing the file.
  dpkg: error processing package virtualbox-ext-pack (--configure):
   installed virtualbox-ext-pack package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   virtualbox-ext-pack


Downloading from a https:// site needs ca-certificates.

The postinst script should ideally handle failure to download the file
as a separate error before verifying the checksum.


cheers,

Andreas

Bug#1035282: firmware-brcm80211: broken symlinks: /lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt

2023-04-29 Thread Andreas Beckmann 
Package: firmware-brcm80211
Version: 20230210-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m14.9s ERROR: WARN: Broken symlinks:
  /lib/firmware/brcm/brcmfmac4356-sdio.khadas,vim2.txt -> 
brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)
  /lib/firmware/brcm/brcmfmac4356-sdio.vamrs,rock960.txt -> 
brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211)

Severity serious, since this likely means that the kernel cannot find
the firmware at the expected location.


cheers,

Andreas


firmware-brcm80211_20230210-4.log.gz
Description: application/gzip

Bug#1035281: firmware-intel-sound: broken symlinks: /lib/firmware/intel/dsp_fw_*.bin -> avs/*/dsp_basefw.bin

2023-04-29 Thread Andreas Beckmann 
Package: firmware-intel-sound
Version: 20230310-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

>From the attached log (scroll to the bottom...):

0m13.1s ERROR: WARN: Broken symlinks:
  /lib/firmware/intel/dsp_fw_bxtn.bin -> avs/apl/dsp_basefw.bin 
(firmware-intel-sound)
  /lib/firmware/intel/dsp_fw_cnl.bin -> avs/cnl/dsp_basefw.bin 
(firmware-intel-sound)
  /lib/firmware/intel/dsp_fw_glk.bin -> avs/apl/dsp_basefw.bin 
(firmware-intel-sound)
  /lib/firmware/intel/dsp_fw_kbl.bin -> avs/skl/dsp_basefw.bin 
(firmware-intel-sound)
  /lib/firmware/intel/dsp_fw_release.bin -> avs/skl/dsp_basefw.bin 
(firmware-intel-sound)

Severity serious, since that likely means the firmware is missing at
the expected location.

cheers,

Andreas


firmware-intel-sound_20230310-1~exp1.log.gz
Description: application/gzip

Bug#1035280: pipewire-pulse 0.3.70 client side crash when load-module module-zeroconf-discover against a pipewire-pulse with module-native-protocol-tcp and module-zeroconf-publish

2023-04-29 Thread Alban Browaeys 
Package: pipewire
Version: 0.3.70-1
Severity: important

Dear Maintainer,

I upgraded pipewire to 0.3.70 on boht the pipewire-pulse client and server side 
of the native "pulseaudio" tcp tunnel.

I restart pipewire and pipewire-pulse user systemd services and then the client 
box pipewire-pulse started constantly
 crashing and reloading.

systemctl  --user status pipewire-pulse
× pipewire-pulse.service - PipeWire PulseAudio
 Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; 
preset: enabled)
 Active: failed (Result: core-dump) since Sun 2023-04-30 02:07:45 CEST; 10s 
ago
   Duration: 1.593s
TriggeredBy: ○ pipewire-pulse.socket
Process: 2254260 ExecStart=/usr/bin/pipewire-pulse (code=dumped, 
signal=SEGV)
   Main PID: 2254260 (code=dumped, signal=SEGV)
CPU: 1.175s

avril 30 02:07:41 cyclope systemd[7728]: Started pipewire-pulse.service - 
PipeWire PulseAudio.
avril 30 02:07:41 cyclope pipewire-pulse[2254260]: mod.pulse-tunnel: failed to 
connect: Connection refused
avril 30 02:07:41 cyclope pipewire-pulse[2254260]: mod.zeroconf-discover: Can't 
load module: Connexion refusée
avril 30 02:07:43 cyclope systemd[7728]: Stopping pipewire-pulse.service - 
PipeWire PulseAudio...
avril 30 02:07:45 cyclope systemd-coredump[2254277]: Process 2254260 
(pipewire-pulse) of user 1000 dumped core.
 
 Stack trace of thread 
2254260:
 #0  0x7f58a57d0ea0 
pw_impl_module_schedule_destroy (libpipewire-0.3.so.0 + 0x72ea0)
 #1  0x7f58a4c64b0d 
do_schedule_destroy (libpipewire-module-pulse-tunnel.so + 0x5b0d)
 #2  0x7f58a5885a4f 
flush_items (libspa-support.so + 0x6a4f)
 #3  0x7f58a5885899 
source_event_func (libspa-support.so + 0x6899)
 #4  0x7f58a5887f9e 
loop_iterate (libspa-support.so + 0x8f9e)
 #5  0x7f58a57cd78b 
pw_main_loop_run (libpipewire-0.3.so.0 + 0x6f78b)
 #6  0x5590e0b4c457 
main (pipewire + 0x1457)
 #7  0x7f58a55a418a 
__libc_start_call_main (libc.so.6 + 0x2718a)
 #8  0x7f58a55a4245 
__libc_start_main_impl (libc.so.6 + 0x27245)
 #9  0x5590e0b4c5f1 
_start (pipewire + 0x15f1)
 
 Stack trace of thread 
2254264:
 #0  0x7f58a5685c06 
epoll_wait (libc.so.6 + 0x108c06)
 #1  0x7f58a5896ec0 
impl_pollfd_wait (libspa-support.so + 0x17ec0)
 #2  0x7f58a5887e1b 
loop_iterate (libspa-support.so + 0x8e1b)
 #3  0x7f58a57a7f6c 
do_loop (libpipewire-0.3.so.0 + 0x49f6c)
 #4  0x7f58a5605fd4 
start_thread (libc.so.6 + 0x88fd4)
 #5  0x7f58a5685820 
__clone (libc.so.6 + 0x108820)
 
 Stack trace of thread 
2254269:
 #0  0x7f58a5678fff 
__GI___poll (libc.so.6 + 0xfbfff)
 #1  0x7f58a3ec02e1 n/a 
(libpulse.so.0 + 0x342e1)
 #2  0x7f58a3eb1fa4 
pa_mainloop_poll (libpulse.so.0 + 0x25fa4)
 #3  0x7f58a3eb2606 
pa_mainloop_iterate (libpulse.so.0 + 0x26606)
 #4  0x7f58a3eb26b0 
pa_mainloop_run (libpulse.so.0 + 0x266b0)
 #5  0x7f58a3ec03b9 n/a 
(libpulse.so.0 + 0x343b9)
 #6  0x7f58a3e6133f n/a 
(libpulsecommon-16.1.so + 0x5b33f)
 #7  0x7f58a5605fd4 
start_thread (libc.so.6 + 0x88fd4)
 #8  0x7f58a5685820 
__clone (libc.so.6 + 0x108820)
 
 Stack trace of thread 
2254275:
 #0  0x7f58a5678fff 
__GI___poll (libc.so.6 + 0xfbfff)

Bug#1035117: coreutils: pr: -o + -n break the output completely

2023-04-29 Thread наб 
Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

-- >8 --
% pr -mJ <(printf '%s\n' a b c d e f) <(printf '%s\n' a b c d e f) -n   | cat 
-sA
$
2023-04-30 01:53  Page 1$
$
1^Ia^Ia$
2^Ib^Ib$
3^Ic^Ic$
4^Id^Id$
5^Ie^Ie$
6^If^If$
$
% pr -mJ <(printf '%s\n' a b c d e f) <(printf '%s\n' a b c d e f) -o4   | cat 
-sA
$
$
2023-04-30 01:53  Page 1$
$
a^Ia$
b^Ib$
c^Ic$
d^Id$
e^Ie$
f^If$
$
-- >8 --
this is exactly what I expect from both POSIX and pr(1) so far.

However:
-- >8 --
% pr -mJ <(printf '%s\n' a b c d e f) <(printf '%s\n' a b c d e f) -o4 -n  | 
cat -sA
$
$
2023-04-30 01:53  Page 1$
$
^I1   a^Ia$
^I2   b^Ib$
^I3   c^Ic$
^I4   d^Id$
^I5   e^Ie$
^I6   f^If$
$
-- >8 --

Where did the tab after the -o come from?
Where did the tab after the numbers go?
Where did the three spaces after the numbers come from?

Correct output for the page body is, naturally,
  "1^Ia^Ib$"
   n()
resp. for each line.

Same happens in just -m mode (but with more shit between the columns).
Same happens in normal columnation
(but much worse, and only on the numbers for the first column):
-- >8 --
% { printf '%s\n' a b c d e f; printf '%s\n' a b c d e f; } | pr -2 -o4 -n   | 
cat -sA
$
$
2023-04-30 01:58  Page 1$
$
^I1   a^I^I^I^I7^Ia$
^I2   b^I^I^I^I8^Ib$
^I3   c^I^I^I^I9^Ic$
^I4   d^I^I^I^I   10^Id$
^I5   e^I^I^I^I   11^Ie$
^I6   f^I^I^I^I   12^If$
$
% { printf '%s\n' a b c d e f; printf '%s\n' a b c d e f; } | pr -2a -o4 -n   | 
cat -sA
$
$
2023-04-30 01:59  Page 1$
$
^I1   a^I^I^I^I2^Ib$
^I3   c^I^I^I^I4^Id$
^I5   e^I^I^I^I6^If$
^I7   a^I^I^I^I8^Ib$
^I9   c^I^I^I^I   10^Id$
   11   e^I^I^I^I   12^If$
$
-- >8 --

Best,
наб

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

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035118: linux-base: Presence of GPG signatures in /boot causes wrong kernels to be listed with linux-version

2023-04-29 Thread abrasamji 
Package: linux-base
Version: 4.6
Severity: important
X-Debbugs-Cc: debian.62...@simplelogin.com

Dear Maintainer,

Grub2 supports additional secure boot capabilities that are not commonly used 
but are required for security. These new features are being referenced in some 
security guides online.  An end user may sign their initrd.img and vmlinuz 
files with a GPG detached signature. See Grub2's manual, section 18.2 "Using 
digital signatures in GRUB" for details.

Presence of these detached signatures causes the "linux-version" script to 
return the .sig files as valid kernels.  Thus, when something runs 
update-initramfs -u (which calls "linux-version list"), the initramfs script 
will ingest the output from linux-version and overwrite an initrd.sig file with 
an initramfs, as well as several other negative effects from not having the 
proper kernel modules available.

The impact is an unbootable system, where Grub attempts to boot the correct 
kernel, but the initrd.img is not updated with new data, and the signature for 
the original initrd.img is overwritten with improper data. System can be 
recovered by picking an old kernel in the grub bootloader.

Thank you

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

Kernel: Linux 6.2.13-stripes-1-s-1.58 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_RANDSTRUCT
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 linux-base depends on:
ii  debconf [debconf-2.0]  1.5.77

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/removing-title:
  linux-base/removing-running-kernel: true

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Peter Ehlert 



On 4/29/23 15:41, Pascal Hambourg wrote:

Hello Peter,

On 29/04/2023 at 16:02, Peter Ehlert wrote:


Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub

install was on a drive without bios_grub

when install was finished, a list of drives was displayed, asking 
where to install GRUB.

the install drive was highlighted
I selected the drive with bios_grub
the display showed "installing GRUB on (...drive it was installed on...)


According to /var/log/syslog, GRUB was successfully installed on 
/dev/sdb although this drive has no BIOS boot partition:


Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb'
Apr 28 23:55:51 grub-installer: info: grub-install does not support
--no-floppy
Apr 28 23:55:51 grub-installer: info: Running chroot /target
grub-install  --force "/dev/sdb"
Apr 28 23:55:51 grub-installer: Installing for i386-pc platform.
Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT
partition label contains no BIOS Boot Partition; embedding won't be
possible.
Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not
possible.  GRUB can only be installed in this setup by using
blocklists.  However, blocklists are UNRELIABLE and their use is
discouraged..
Apr 28 23:56:01 grub-installer: Installation finished. No error reported.
Apr 28 23:56:01 grub-installer: info: grub-install ran successfully


(several other OS's are on that drive if that matters)

reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? 


the GRUB that was on the only disk with a bios_grub flagged partition.

That does not seem possible according to the above logs. Are you sure 
that the machine rebooted from this disk ? 

apparently so. I know of none other.
GRUB menu showed all of the other systems as before the install.
(note that /dev/sd* naming is not stable across reboots and does not 
match BIOS disk numbering/naming)

I am aware of that



boot from another OS:
# grub-install /dev/sde && update-grub
now my GRUB menu includes the new system


In chroot or directly from the other OS ?

directly from the other OS (also Bookworm), my default
Running grub-install directly from another OS just installed that 
other OS's GRUB on /dev/sde and running update-grub directly just 
added the new Debian installation to that other OS's boot menu if 
os-prober is enabled.

yes, I enabled os-prober

Bug#1035115: gnome-shell-extension-gpaste: Please update to 43.2 for Debian 12

2023-04-29 Thread Amr Ibrahim 
Package: gnome-shell-extension-gpaste
Version: 43.1-3
Severity: normal
Tags: upstream

Hello,

Please update to 43.2 for Debian 12. It contains a potential fix for a crash
under heavy memory load.

https://github.com/Keruspe/GPaste/blob/gpaste-43/NEWS

NEW in 43.2 (20/03/2023)
=
- Avoid crash under heavy memory load


Best,
Amr


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (100, 'unstable'), 
(50, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell-extension-gpaste depends on:
ii  gir1.2-gpaste-2  43.1-3
ii  gnome-shell  43.4-1
ii  gpaste-2 43.1-3

gnome-shell-extension-gpaste recommends no packages.

gnome-shell-extension-gpaste suggests no packages.

-- no debconf information

Bug#1035114: The lower horizontal bar of ⋢ (U+22E2) is missing by default.

2023-04-29 Thread Al Ma 
Package: emacs
Version: 1:27.1+1-3.1+deb11u2
1. In gnome, open gnome-characters and emacs.
2. In gnome-characters, find ⋢ (U+22E2) and copy it.
3. Paste it via Ctrl+y to the emacs scratch buffer.
4. Observe that the charater misses a lower bar.
In the attached screenshot, on the right you see the correct representation in 
gnome-characters, and on the left the wrong one in emacs. What you see on the 
left is the negation of ⊏, whereas you expect the negation of ⊑.
In case it's a font issue, please feel free to reassign the bug report 
appropriately.
Gratefully,
Alma

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Pascal Hambourg 

Hello Peter,

On 29/04/2023 at 16:02, Peter Ehlert wrote:


Legacy aka BIOS booting
system has 4 physical disk drives, all GPT partition tables
only one drive has a partition with bios_grub

install was on a drive without bios_grub

when install was finished, a list of drives was displayed, asking where 
to install GRUB.

the install drive was highlighted
I selected the drive with bios_grub
the display showed "installing GRUB on (...drive it was installed on...)


According to /var/log/syslog, GRUB was successfully installed on 
/dev/sdb although this drive has no BIOS boot partition:


Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb'
Apr 28 23:55:51 grub-installer: info: grub-install does not support
--no-floppy
Apr 28 23:55:51 grub-installer: info: Running chroot /target
grub-install  --force "/dev/sdb"
Apr 28 23:55:51 grub-installer: Installing for i386-pc platform.
Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT
partition label contains no BIOS Boot Partition; embedding won't be
possible.
Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not
possible.  GRUB can only be installed in this setup by using
blocklists.  However, blocklists are UNRELIABLE and their use is
discouraged..
Apr 28 23:56:01 grub-installer: Installation finished. No error reported.
Apr 28 23:56:01 grub-installer: info: grub-install ran successfully


(several other OS's are on that drive if that matters)

reboot gave me the Old GRUB menu, not including my new system.


What do you mean by "old GRUB menu" ? The GRUB which was previously 
installed on /dev/sdb ? That does not seem possible according to the 
above logs. Are you sure that the machine rebooted from this disk ? 
(note that /dev/sd* naming is not stable across reboots and does not 
match BIOS disk numbering/naming)



boot from another OS:
# grub-install /dev/sde && update-grub
now my GRUB menu includes the new system


In chroot or directly from the other OS ?
Running grub-install directly from another OS just installed that other 
OS's GRUB on /dev/sde and running update-grub directly just added the 
new Debian installation to that other OS's boot menu if os-prober is 
enabled.

Bug#1034796: kio-gdrive: Does not work. Network account create does not propose gogle drive

2023-04-29 Thread Nicholas D Steeves 
Control: severity -1 important
Control: tag -1 moreinfo

Justification: Package is not unusable for everyone.  See the following
for further info: https://www.debian.org/Bugs/Developer#severities

Reply follows inline:

Eric Valette  writes:

> Using dolphin for network, you can select gdrive but it does not propose to 
> add
> a google account.
>

That's odd, mine shows a "New account" button.

> Using systemsettings, I have the same problem and using the command rpoposed 
> in the
> packahe readme.md gives:
> kioclient5 exec gdrive:/
> kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/gdrive" 
> not found
> kf.kio.core: KIO::get didn't emit a mimetype! Please fix the KIO worker for 
> URL QUrl("gdrive:/")
>

Hmm, that sounds like the KIO worker wasn't registered properly.  I'll
assume you ran "kdeinit5 # or just [logout and] re-login" as stated in
the README.  Assuming this was the case indicates some kind of breakage
elsewhere.

> Kernel: Linux 5.15.108 (SMP w/8 CPU threads; PREEMPT)

Neat, I track this branch too :)

> Versions of packages kio-gdrive depends on:
> ii  kaccounts-integration  4:22.12.3-1
> ii  kio5.104.0-1

Are you able to reproduce this bug with a pure testing/bookworm or
sid/unstable system?  If so, please provide steps to reproduce, and
remove the moreinfo tag from this bug at that time.

Assuming the README was followed, it appears that the trigger condition
is kio (or another package) from experimental.  I wonder if the ABI was
silently broken by upstream again, and that's what's going on here?  If
you'd like to test this hypothesis, try downloading the source package
for kio-gdrive, install the *-dev packages for the versions of the
libraries you're using on this installation, then dpkg-buildpackage,
debuild, or similar, as you prefer.

Alternatively, I wonder if this is a wishlist bug expressing how
annoying it is to have to "kdeinit5 # or just [logout and] re-login"?  I
would totally relate, by the way, because I find that annoying too.


Regards,
Nicholas

Bug#1035112: coreutils: pr: -e broken?

2023-04-29 Thread наб 
Package: coreutils
Version: 8.32-4+b1
Version: 9.1-1
Severity: normal

Dear Maintainer,

-- >8 --
$ pr -e-20 | cat -s
a-e
ą-ę

2023-04-30 00:19  Page 1

a   e
ąę
-- >8 --

First is right  (the e is at column 21),
second is wrong (the ę is at column 22).

Best,
наб

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

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Peter Ehlert 



On 4/29/23 09:21, Steve McIntyre wrote:

On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:

On 4/29/23 07:23, Steve McIntyre wrote:

Hi Peter,

Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.

there is no file "installer" in /var/log

Right, it's a directory with multiple files in it. Could you also


Mr. McIntyre:

I sent several email Huge responses to the list.
I copied the contents of all of the files... were they received?

if not I can repeat or find a pastebin service of some sort.

Thanks, Peter


share the other files please?


I found /var/log/installer/syslog

Thanks...

Bug#905745: util-linux: tty hijacking possible in "su" via TIOCSTI ioctl

2023-04-29 Thread Chris Hofstaedtler 
Control: reassign -1 src:linux
Control: affects -1 src:util-linux

Dear Kernel Maintainers, Security Team,

* Sam Morris :
> Linux 6.2 introduces a sysctl dev.tty.legacy_tiocsti sysctl which can be
> used to disable TIOCSTI. The default value of the sysctl is set at build
> time with CONFIG_LEGACY_TIOCSTI.
> 
> 

Maybe we can get this into 6.1?

Thanks,
Chris

Bug#1035111: RFP: ticker -- Terminal stock ticker with live updates and position tracking

2023-04-29 Thread Fjords 

Package: ticker
Severity: wishlist

Hello, I noticed there is a lack of functional stock ticker packages for 
Debian (and maybe GNU/Linux in general) that I've come across one via 
GitHub that is cli-based and has a good layout. You can set which stocks 
to view in the config file or append them to the command. There are DEB 
files provided by the author here (they work on Debian Bullseye, 
Bookworm, and Sid): 
https://github.com/achannarasappa/ticker/releases/tag/v4.5.6


It would be nice to have this packaged for Debian officially. Thank you.

Upstream: https://github.com/achannarasappa/ticker

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

2023-04-29 Thread Richard Lewis 
On Fri, 28 Apr 2023 16:00:14 +0200 Helge Kreutzmann
 wrote:
> > +  Greatly expanded translations of man pages
> > +  
> > +Thank to many efforts of our translators, the translation of many
> >
> > That feels like one many too many for one sentence.
>
> There are often (but not always) several translators working on many
> translations. So you could remove the first "many".
>
> >
> > +manpages has been greatly expanded (e.g. we have complete
> > translation
> > +of systemd user pages into German now) and various new languages
> > have
> > +been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian,
> > +Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).
> >
> > I happen to know that "Norwegian" is ambiguous? There's Bokmål and Nynorsk.
> > I assume the former is meant, maybe "Norwegian (Bokmål)"?
> >
> > My spelling checker also suggests Ukrainian and Vietnamese.
>
> I apologize for the sloppy wording/spelling. Please correct all three.

Shouldn't it include
- what is a 'man' page - i bet many people don't know this nowadays!
- how do i install and use the new translations? (do i choose what
language 'man foo' gives me? is it automatic if my locale is correct?
do i need a new package? - i certainly don't know this bit!)

I also thought
- "new languages" is unclear: does it really mean all those languages
have been added for the first time ever? (seems a bit unlikely to me,
but that';s how i read the diff?)
- too many repetition of "translation" - focus on the benefit to users
(new stuff) not the mechanism of how it was made!
- is "user" needed in the bit about systemd? (i assume not)
- seems odd to put completion of systemd before adding the other
languages  (based on my assumption about the number of people likely
benefiting)
- i assume there is no way to count the translations? eg would be very
nice if it said "(x% translated)" after each language

So something like:


Many more man pages have been translated

Thanks to our translators, documentation in
man-page format is available in many more
languages.

For example, many more  man pages
are now available in
Czech, Danish, Greek, Finnish, Indonesian, Macedonian, Norwegian
(Bokmål), Russian, Serbian, Swedish, Ukrainian and Vietnamese,
and all systemd man pages are
now available in German.


To ensure the man command shows you documentation
in your language (where possible), install the
manpages
package and select your language using
dpkg-reconfigure locales.

Bug#948674: Any news on the otter browser packaging?

2023-04-29 Thread Gürkan Myczko 

Hi Martin,

The link you provided to the prospective package returns a 404, 
unfortunately.
Could you please provide a link to your current code for other to 
contribute?


Here's what I have, best to use dget on it:
http://sid.ethz.ch/debian/otter-browser/


Thanks in advance,
Mt


HTH,

Bug#1035110: ITP: drminfo -- Small utility to dump info about DRM devices

2023-04-29 Thread Rodrigo Siqueira 
Package: wnpp
Owner: Rodrigo Siqueira 
X-Debbugs-Cc: siqueirajor...@riseup.net
Severity: wishlist

* Package name: drminfo
  Version : 2.4.0 
  Upstream Contact: Simon Ser , Scott Anderson 

* URL : https://gitlab.freedesktop.org/emersion/drm_info
* License : MIT
  Programming Lang: C
  Description : Small utility to dump info about DRM devices

The drm_info is a small tool for getting GPU information such as
supported formats, capabilities, properties, etc. This is a valuable
tool to collect GPU data from the Direct Rendering Manager (DRM)
perspective, which can guide developers and users about some specific
feature support in a GPU. The website https://drmdb.emersion.fr/ is an
example of an extensive database built with the drm_info tool and with
the collaboration of multiple people.

I already have the drminfo package available at:

 https://salsa.debian.org/siqueira/drminfo

Thanks

-- 
Rodrigo Siqueira
https://siqueira.tech


signature.asc
Description: PGP signature

Bug#1035098: Bug#1034958: Consequence of #951598

2023-04-29 Thread Julien ÉLIE 

Hi Marco,


Would this work for you? Please let me know ASAP since the hard freeze
is very close.


As you plan on uploading a new package (thanks for it!), could you also 
please add this specific fix for ovsqlite-util?


https://github.com/InterNetNews/inn/commit/a130d658317b623ba72d447ff3461389487917d2

It was fixed between 2.7.1rc1 and the final 2.7.1 version.
Naturally, uploading 2.7.1 would be best if it can be done at this step 
of the freeze.


Also, it may be useful to add libdbd-sqlite3-perl as a dependency of the 
inn2 package so that people can directly use ovsqlite-util.  (As 
libsqlite is already listed in the dependencies, this Perl module could 
be listed as well).


--
Julien ÉLIE

« Le chemin le plus court d'un point à un autre est la ligne droite, à
  condition que les deux points soient bien en face l'un de l'autre. »
  (Pierre Dac)

Bug#1035109: perl: CVE-2023-31484

2023-04-29 Thread Salvatore Bonaccorso 
Source: perl
Version: 5.36.0-7
Severity: normal
Tags: security upstream
Forwarded: https://github.com/andk/cpanpm/pull/175
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for perl.

Sorry for the initial swapping of the CVEs, CVE-2023-31484 is the one
associated with CPAN.pm.

CVE-2023-31484[0]:
| CPAN.pm before 2.35 does not verify TLS certificates when downloading
| distributions over HTTPS.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-31484
https://www.cve.org/CVERecord?id=CVE-2023-31484
[1] https://github.com/andk/cpanpm/pull/175
[2] 
https://github.com/andk/cpanpm/commit/9c98370287f4e709924aee7c58ef21c85289a7f0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1035106: RFS: cdreaper/3.0.0-1 [ITP 1035103] -- Graphical audio CD ripper and encoder

2023-04-29 Thread Andreas Ronnquist 
On Sat, 29 Apr 2023 20:10:02 +0100,
Peter Blackman wrote:

>Package: sponsorship-requests
>Severity: wishlist
>
>Dear mentors,
>
>I am looking for a sponsor for my package "cdreaper":
>
>cdreaper is the Gtk3 fork of asunder
>https://tracker.debian.org/pkg/asunder
>
>I would like to set up a packaging VCS on Salsa under the debian group,
>but don't have the privilege to create an empty repository there myself.
>
>  * Package name : cdreaper
>    Version  : 3.0.0-1
>    Upstream contact : Salamandar 
>  * URL  : https://gitlab.gnome.org/Salamandar/Reaper
>  * License  : GPL-2, CC0-1.0
>  * Vcs  : pending
>    Section  : sound
>

Please notice that there might be a rename of the project (See #4 on
the upstream bugtracker [1]).

On another note - I would gladly co-maintain this (whatever the name
turns out to be in the end :).

1: https://gitlab.gnome.org/Salamandar/Reaper/-/issues/7#note_1733028

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

Bug#1035108: ITP: rdflib-sqlalchemy -- RDFLib store using SQLAlchemy dbapi as back-end

2023-04-29 Thread Dominik George 
Package: wnpp
Severity: wishlist
Owner: Dominik George 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rdflib-sqlalchemy
  Version : 0.5.4
  Upstream Contact: Mark Watts
* URL : https://github.com/RDFLib/rdflib-sqlalchemy
* License : BSD-3-clause
  Programming Lang: Python
  Description : RDFLib store using SQLAlchemy dbapi as back-end

RDFlib-SQLAlchemy is a formula-aware store for RDFlib that uses SQLAlchemy
to persist triples in relational databases.


I will maintain the package under the Debian Python Team.

-BEGIN PGP SIGNATURE-

iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZE15njEaaHR0cHM6Ly93
d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz
aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3UpmAP4nttkSjVJbdmIU0ECtjWju
Z00zP7ebS3KHBCGyww0XLgEA+lIczQMdcGq7n9TOKRryhAhQ8hRwdWj7uc8cCQ5R
jQ8=
=tzxJ
-END PGP SIGNATURE-

Bug#1035107: unblock: singular/1:4.3.1-p3+ds-2

2023-04-29 Thread Jerome Benoit 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package singular.

This package fixes the RC bug #1034769:
the python3-brial packages is removed from the build-dependency list
(and it is substituted with python3).

This change is necessary to provide singular on all supported arch
while it does not affect its buildings as the python3-brial material
is actually not used by singular.

Please find the source diff.

unblock singular/1:4.3.1-p3+ds-2

Best wishes, Jerome
diff -Nru singular-4.3.1-p3+ds/debian/changelog 
singular-4.3.1-p3+ds/debian/changelog
--- singular-4.3.1-p3+ds/debian/changelog   2023-01-03 16:14:59.0 
+0100
+++ singular-4.3.1-p3+ds/debian/changelog   2023-04-27 10:16:02.0 
+0200
@@ -1,3 +1,9 @@
+singular (1:4.3.1-p3+ds-2) unstable; urgency=medium
+
+  * RC fix release, discard dependency on python3-brial (Closes: #1034769).
+
+ -- Jerome Benoit   Thu, 27 Apr 2023 08:16:02 +
+
 singular (1:4.3.1-p3+ds-1) unstable; urgency=medium
 
   * New upstream micro version.
diff -Nru singular-4.3.1-p3+ds/debian/control 
singular-4.3.1-p3+ds/debian/control
--- singular-4.3.1-p3+ds/debian/control 2023-01-03 15:38:50.0 +0100
+++ singular-4.3.1-p3+ds/debian/control 2023-04-27 10:15:55.0 +0200
@@ -10,7 +10,7 @@
  libreadline-dev,
  libgmp-dev, libmpfr-dev, libglpk-dev, libcdd-dev, libflint-dev, libntl-dev,
  graphviz, 4ti2, normaliz, surf-alggeo, topcom,
- python3-brial
+ python3
 Build-Depends-Indep:
  doxygen,
  rdfind, symlinks

Bug#1035101: Failed to detect HD if Intel RST-RAID is active

2023-04-29 Thread Thomas Viehweger 




Apparently we have that option enabled in the regular linux package:

 debian/config/kernelarch-x86/config:CONFIG_INTEL_RST=m

but the relevant module isn't shipped in any udebs:

 /lib/modules//kernel/drivers/platform/x86/intel/intel-rst.ko

Would you be willing to test an unofficial amd64 netinst image that
would ship that extra module, to see if the installer (1) sees the disk
and (2) can do something with it?


Hi,

I am able to do one test...

Bug#1034519: chrony: AppArmor profile denies creation of chrony.ppsX.sock

2023-04-29 Thread Ryan Govostes 
Sorry, I didn't receive your original e-mail.

The proposed rule would be fine, but I don't see why /run/chrony*.sock
would be too permissive. The "chrony" prefix would be sufficient to
ensure that it is not possible to maliciously configure chrony to
control a path that "belongs" to another piece of software. The user
may want to use their own device naming scheme, like /dev/serial0
(used on Raspberry Pi OS) or /dev/gps0, which would be prohibited by
the more strict rule.

The only other example from the chrony.conf documentation is
"bindcmdaddress /var/run/chrony/chronyd.sock" (used for the chronyc
tool to issue commands to the daemon) but that's just an example, not
a default.

Ryan

On Fri, Apr 28, 2023 at 5:52 AM Vincent Blut  wrote:
>
> Le 2023-04-17 20:45, Vincent Blut a écrit :
> > Control: severity -1 important
> > Control: tags -1 moreinfo
> >
> > Hi Ryan,
> >
> > Le 2023-04-17 14:54, Ryan Govostes a écrit :
> > > Package: chrony
> > > Version: 4.3
> > > Severity: normal
> > > X-Debbugs-Cc: rgovos...@gmail.com
> > >
> > > Dear Maintainer,
> > >
> > > gpsd and chronyd can communicate via domain sockets such as 
> > > /var/run/chrony.ttyS0.sock. chronyd creates the sockets and gpsd connects 
> > > to them.
> > >
> > > However, the AppArmor profile for chronyd is too strict; it only allows 
> > > the creation of sockets for tty devices, and not pps devices.
> > >
> > > @{run}/chrony.tty{,*}.sock rw,
> >
> > Indeed, this rule is too restrictive…
> >
> > > The corresponding rules on the gpsd profile are:
> > >
> > > /{,var/}run/chrony.tty{,S,USB,AMA}[0-9]*.sock rw,
> > > /tmp/chrony.tty{,S,USB,AMA}[0-9]*.sock rw,
> > >
> > > Could these be relaxed to allow /var/run/chrony.*.sock?
> >
> > …This might be too permissive though. Could you please tell me if changing 
> > the
> > rule to "@{run}/chrony{,.clk}.{tty,pps}*.sock rw," meets your need?
>
> Any update on this Ryan?
>
> Cheers,
> Vincent

Bug#1035106: RFS: cdreaper/3.0.0-1 [ITP 1035103] -- Graphical audio CD ripper and encoder

2023-04-29 Thread Peter Blackman 

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

cdreaper is the Gtk3 fork of asunder
https://tracker.debian.org/pkg/asunder

I would like to set up a packaging VCS on Salsa under the debian group,
but don't have the privilege to create an empty repository there myself.

 * Package name : cdreaper
   Version  : 3.0.0-1
   Upstream contact : Salamandar 
 * URL  : https://gitlab.gnome.org/Salamandar/Reaper
 * License  : GPL-2, CC0-1.0
 * Vcs  : pending
   Section  : sound

The source builds the following binary packages:

  cdreaper - Graphical audio CD ripper and encoder

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/cdreaper/cdreaper_3.0.0-1.dsc

Changes for the initial release:

 cdreaper (3.0.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1035103)

Regards,
--
  Peter Blackman

Bug#1035105: bullseye-pu: package distro-info-data/0.51+deb11u4

2023-04-29 Thread Stefano Rivera 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: distro-info-d...@packages.debian.org, bdr...@debian.org
Control: affects -1 + src:distro-info-data

As usual, a distro-info-data update.

[ Reason ]
There's a new Ubuntu development release, a bookworm release date, and
some minor Ubuntu EoL changes.

* Update data to 0.58:
  - Add Debian 14 "forky" with a vague creation date.
  - Correct Ubuntu 23.04 release date to 2023-04-20.
  - Tighten validate-csv-data heuristics, restricting Ubuntu EoLs to
Tue-Thursday.
  - Document Ubuntu ESM overlap period (LP: #2003949)
  - Add Ubuntu 23.10 Mantic Minotaur (LP: #2018028)
  - Set the planned release date for Debian bookworm (and an EoL based on it).
  - Adjust trixie's creation date to match bookworm's release.

[ Impact ]
Debian stable is unaware of the current Ubuntu development release, and
Debian bookworm release dates.

Currently:

$ debian-distro-info -t --date=2023-06-10
bookworm
$ debian-distro-info -s --date=2023-06-10
bullseye
$ ubuntu-distro-info -df
ubuntu-distro-info: Distribution data outdated.
Please check for an update for distro-info-data. See 
/usr/share/doc/distro-info-data/README.Debian for details.

Expected:

$ debian-distro-info -t --date=2023-06-10
trixie
$ debian-distro-info -s --date=2023-06-10
bookworm
$ ubuntu-distro-info -df
Ubuntu 23.10 "Mantic Minotaur"


[ Tests ]
Autopkgtests passed.
The changes include some updates to tests around the Ubuntu EoL dates.

Manually tested as above.

[ Risks ]
Data-only package, this will bring it up to parity with unstable.

[ 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
diff -Nru distro-info-data-0.51+deb11u3/debian/changelog 
distro-info-data-0.51+deb11u4/debian/changelog
--- distro-info-data-0.51+deb11u3/debian/changelog  2022-10-30 
07:31:55.0 -0400
+++ distro-info-data-0.51+deb11u4/debian/changelog  2023-04-29 
14:30:57.0 -0400
@@ -1,3 +1,17 @@
+distro-info-data (0.51+deb11u4) bullseye; urgency=medium
+
+  * Update data to 0.58:
+- Add Debian 14 "forky" with a vague creation date.
+- Correct Ubuntu 23.04 release date to 2023-04-20.
+- Tighten validate-csv-data heuristics, restricting Ubuntu EoLs to
+  Tue-Thursday.
+- Document Ubuntu ESM overlap period (LP: #2003949)
+- Add Ubuntu 23.10 Mantic Minotaur (LP: #2018028)
+- Set the planned release date for Debian bookworm (and an EoL based on 
it).
+- Adjust trixie's creation date to match bookworm's release.
+
+ -- Stefano Rivera   Sat, 29 Apr 2023 14:30:57 -0400
+
 distro-info-data (0.51+deb11u3) bullseye; urgency=medium
 
   * Update data to 0.55:
diff -Nru distro-info-data-0.51+deb11u3/debian.csv 
distro-info-data-0.51+deb11u4/debian.csv
--- distro-info-data-0.51+deb11u3/debian.csv2022-10-30 07:31:55.0 
-0400
+++ distro-info-data-0.51+deb11u4/debian.csv2023-04-29 14:30:57.0 
-0400
@@ -15,7 +15,8 @@
 9,Stretch,stretch,2015-04-26,2017-06-17,2020-07-06,2022-06-30,2027-06-30
 10,Buster,buster,2017-06-17,2019-07-06,2022-08-14,2024-06-30,2029-06-30
 11,Bullseye,bullseye,2019-07-06,2021-08-14,2024-08-14
-12,Bookworm,bookworm,2021-08-14
-13,Trixie,trixie,2023-08-01
+12,Bookworm,bookworm,2021-08-14,2023-06-10,2026-06-10
+13,Trixie,trixie,2023-06-10
+14,Forky,forky,2025-08-01
 ,Sid,sid,1993-08-16
 ,Experimental,experimental,1993-08-16
diff -Nru distro-info-data-0.51+deb11u3/ubuntu.csv 
distro-info-data-0.51+deb11u4/ubuntu.csv
--- distro-info-data-0.51+deb11u3/ubuntu.csv2022-10-30 07:31:55.0 
-0400
+++ distro-info-data-0.51+deb11u4/ubuntu.csv2023-04-29 14:30:57.0 
-0400
@@ -26,14 +26,15 @@
 16.10,Yakkety Yak,yakkety,2016-04-21,2016-10-13,2017-07-20
 17.04,Zesty Zapus,zesty,2016-10-13,2017-04-13,2018-01-13
 17.10,Artful Aardvark,artful,2017-04-13,2017-10-19,2018-07-19
-18.04 LTS,Bionic 
Beaver,bionic,2017-10-19,2018-04-26,2023-04-26,2023-04-26,2028-04-26
+18.04 LTS,Bionic 
Beaver,bionic,2017-10-19,2018-04-26,2023-05-31,2023-05-31,2028-04-26
 18.10,Cosmic Cuttlefish,cosmic,2018-04-26,2018-10-18,2019-07-18
 19.04,Disco Dingo,disco,2018-10-18,2019-04-18,2020-01-23
 19.10,Eoan Ermine,eoan,2019-04-18,2019-10-17,2020-07-17
-20.04 LTS,Focal 
Fossa,focal,2019-10-17,2020-04-23,2025-04-23,2025-04-23,2030-04-23
+20.04 LTS,Focal 
Fossa,focal,2019-10-17,2020-04-23,2025-05-29,2025-05-29,2030-04-23
 20.10,Groovy Gorilla,groovy,2020-04-23,2020-10-22,2021-07-22
 21.04,Hirsute Hippo,hirsute,2020-10-22,2021-04-22,2022-01-20
 21.10,Impish Indri,impish,2021-04-22,2021-10-14,2022-07-14
-22.04 LTS,Jammy 
Jellyfish,jammy,2021-10-14,2022-04-21,2027-04-21,2027-04-21,2032-04-21
+22.04 LTS,Jammy 
Jellyfish,jammy,2021-10-14,2022-04-21,2027-06-01,2027-06-01,2032-04-21
 22.10,Kinetic Kudu,kinetic,2022-04-21,2022-10-20,2023-07-20

Bug#1035104: hdajackretask silently doesn't save anything without pkexec

2023-04-29 Thread Andrey Rakhmatullin 
Package: alsa-tools-gui
Version: 1.2.5-2
Severity: serious

If you try to "Apply now" or "Install boot override", it should run
pkexec but if pkexec isn't installed (and it's not in
Depends/Recommends/Suggests) then the app will still show the success
box while not actually doing anything.


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages alsa-tools-gui depends on:
ii  libasound21.2.8-1+b1
ii  libc6 2.36-9
ii  libfltk1.31.3.8-5
ii  libglib2.0-0  2.74.6-2
ii  libgtk-3-03.24.37-2
ii  libgtk2.0-0   2.24.33-2
ii  libstdc++612.2.0-14

alsa-tools-gui recommends no packages.

alsa-tools-gui suggests no packages.

-- no debconf information

Bug#1035101: Failed to detect HD if Intel RST-RAID is active

2023-04-29 Thread Cyril Brulebois 
Hallo Thomas,

and thanks for your report.

Thomas Viehweger  (2023-04-29):
> Detect hard drives: [E]
> 
> The Hard disk was not detected because Intel RST was configured in
> RAID mode.
> 
> Tried Ubuntu 23.04 installer which gives the correct hint.
> 
> After configuring Intel RST to AHCI mode, the harddisk was detected
> and installation was successful.
> 
> It would be nice if this installer could check the RST mode, too.

Apparently we have that option enabled in the regular linux package:

debian/config/kernelarch-x86/config:CONFIG_INTEL_RST=m

but the relevant module isn't shipped in any udebs:

/lib/modules//kernel/drivers/platform/x86/intel/intel-rst.ko

Would you be willing to test an unofficial amd64 netinst image that
would ship that extra module, to see if the installer (1) sees the disk
and (2) can do something with it?

(Also putting the kernel team in the loop.)


Tschüss,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035103: ITP: cdreaper -- Graphical audio CD ripper and encoder

2023-04-29 Thread Peter Blackman 

Package: wnpp
Severity: wishlist
Owner: Peter 
X-Debbugs-Cc: debian-de...@lists.debian.org, pe...@pblackman.plus.com

* Package name    : cdreaper
  Version : 3.0.0
  Upstream Contact: Salamandar 
* URL : https://gitlab.gnome.org/Salamandar/Reaper
* License : GPL2
  Programming Lang: C
  Description : Graphical audio CD ripper and encoder

Can be used to save tracks from Audio CDs. Main features:
 * Supports WAV, MP3, Ogg Vorbis, FLAC, and Wavpack audio files
 * Uses CDDB to name and tag each track
 * Can encode to multiple formats in one session
 * Creates M3U playlists
 * Allows for each track to be by a different artist
 * Does not require a specific desktop environment (just Gtk3)

This is the Gtk3 fork of asunder (it now has its own name)
I have called this package cdreaper, as the name reaper is already in use 
elsewhere;
https://repology.org/project/reaper/versions

I will maintain the package myself and need a sponsor.

The package has been set up on the AUR and Open Build Service.
https://aur.archlinux.org/packages/cdreaper
https://build.opensuse.org/package/show/home:PeterBBB/cdreaper

Bug#1034958: Consequence of #951598

2023-04-29 Thread Helge Kreutzmann 
tags 1034958 + patch
thanks

On Sat, Apr 29, 2023 at 06:42:44PM +0200, Marco d'Itri wrote:
> On Apr 29, Helge Kreutzmann  wrote:
> 
> > Reverse, I believe manpages-dev should declare:
> > Breaks:   inn2-dev (<< 2.7.0-1)
> > Replaces: inn2-dev (<< 2.7.0-1)
> > 
> > Is this fine for you?
> Yes.

-- 
  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#1026881: x2goserver: unsuable desktop, composite?

2023-04-29 Thread pb 

As of 29.4. none of the desktop environments work out of the box. When chosing
window managers, such as marco, that have compoisiting enabled, things are bad.
There are big black bars around the windows (not an issue) when activiating
comppsition and all feels very bad. The Desktop-Environments mate, cinnaom
do not work at all, lxqt has unusable bars. Xfce starts, but again with
horrible black bars, and feels extremly sluggish. There are many redrawing 
artefacts
making all desktops unreadable. When deactivating the compositing, things 
improve but
only for xfce it results in a somehow workable state. The bars disappear and 
there are
close to none redrawing artefacts left. Xfce feels very slow but almost usable. 
All
other evnironments not so much.

Somehow there is still something wrong deep in the X-stuff? No opengl for
even the lightest desktop candy?

The following errors still appear in .xsession-x2go...errors.
===
...
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.freedesktop.systemd1 exited with status 1

/etc/x2go/Xsession.d/30x11-common_xresources: Zeile 16: has_option: Kommando 
nicht gefunden.
xhost:  must be on local machine to add or remove hosts.
localuser:peter being added to access control list
/etc/x2go/Xsession.d/75dbus_dbus-launch: Zeile 9: has_option: Kommando nicht 
gefunden.
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.freedesktop.systemd1 exited with status 1

dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.freedesktop.systemd1 exited with status 1

/etc/x2go/Xsession.d/90x11-common_ssh-agent: Zeile 9: has_option: Kommando 
nicht gefunden.
...
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.freedesktop.systemd1 exited with status 1

/usr/bin/iceauth:  creating new authority file /run/user/1000/ICEauthority
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: 
Process org.freedesktop.systemd1 exited with status 1

gpg-agent: Ein gpg-agent läuft bereits - ein weiterer wird nicht gestartet

(xfwm4:16757): xfwm4-WARNING **: 18:48:01.894: XSync extension too old (3.0).

(xfwm4:16757): xfwm4-WARNING **: 18:48:01.900: The display does not support the 
XComposite extension.

(xfwm4:16757): xfwm4-WARNING **: 18:48:01.901: The display does not support the 
XPresent extension.

(xfwm4:16757): xfwm4-WARNING **: 18:48:01.901: Compositing manager disabled.

(xfwm4:16757): xfwm4-WARNING **: 18:48:02.695: Another compositing manager is 
running on screen 0

(xfsettingsd:16768): xfsettingsd-CRITICAL **: 18:48:02.790: Your XI is too old 
(1.3) version 1.4 is required.

(xfsettingsd:16768): xfsettingsd-WARNING **: 18:48:02.790: Failed to create 
device filter
Xfce power manager is not running

(xfce4-power-manager:16788): xfce4-power-manager-WARNING **: 18:48:03.291: 
Monitor is not DPMS capable

(process:16798): GLib-CRITICAL **: 18:48:03.328: g_strv_contains: assertion 
'str != NULL' failed
xscreensaver: 18:48:03: "cinnamon-screensaver" is already running on display 
:50.0 (window 0x61)
Fehlgeschlagen: Entität nicht vorhanden

** (light-locker:16808): ERROR **: 18:48:03.449: Environment variable 
XDG_SESSION_PATH not set. Is LightDM running?
qt.qpa.xcb: X server does not support XInput 2
xfce4-panel-Message: 18:48:03.593: Plugin "(null)-7" was not found and has been 
removed from the configuration
Xfce-Energieverwaltung: Eine andere Energieverwaltung läuft bereits

** (xiccd:16838): WARNING **: 18:48:03.621: EDID is empty
Ein anderer Benachrichtigungsdienst läuft – es wird beendet
qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 649, major code: 130 (Unknown), minor 
code: 47
blueman-applet 18.48.03 WARNING  PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher 
priority
blueman-applet 18.48.03 WARNING  PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher 
priority


** (xiccd:16838): CRITICAL **: 18:48:04.302: failed to create colord device: failed to obtain 
org.freedesktop.color-manager.create-device auth


** (wrapper-2.0:16903): WARNING **: 18:48:04.492: No outputs have backlight 
property

(wrapper-2.0:16903): xfce4-power-manager-plugin-WARNING **: 18:48:04.610: Xfce4-power-manager: The panel plugin is 
present, so the tray icon gets disabled.


(xfce4-power-manager:16788): xfce4-power-manager-WARNING **: 18:48:04.783: 
could not map keysym 1008ffa8 to keycode
xfce4-power-manager:16788): xfce4-power-manager-WARNING **: 18:48:05.040: Failed to get keyboard max

Bug#1035102: grub-efi-amd64: GRUB_GFXMODE=2560x1440 and GRUB_BACKGROUND=/usr/share/desktop-base/emerald-theme/grub

2023-04-29 Thread Hoareau J.P. 
Package: grub-efi-amd64
Version: 2.06-12
Severity: minor
X-Debbugs-Cc: hoarea...@free.fr

Dear Maintainer,

GRUB_GFXMODE=2560x1440 and GRUB_BACKGROUND=/usr/share/desktop-base/emerald-
theme/grub , have no effect on GRUB resolution or background image.

I updated to Debian 12 (Bookworm) grub-efi, grub-efi-amd64 and grub-efi-
amd64-bin to version 2.06-12 yesterday and found that grub-efi was updated. I
customized the "/etc/default/grub" file to get the resolution of my screen
(2560x1440) by modifying the parameter GRUB_GFXMODE=2560x1440. This action has
no effect when restarting the PC. I did an "update-grub" before the reboot.
GRUB_BACKGROUND=/usr/share/desktop-base/emerald-theme/grub does't display the
background image.

Thanks for your help.



-- Package-specific info:

*** BEGIN /proc/mounts
/dev/nvme0n1p2 / ext4 rw,noatime 0 0
/dev/nvme1n1p1 /mnt/nvme1n1p1 ext4 rw,nosuid,nodev,relatime 0 0
/dev/nvme0n1p1 /boot/efi vfat 
rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/nvme2n1p1 /mnt/nvme2n1p1 ext4 rw,nosuid,nodev,relatime,stripe=4 0 0
/dev/sda1 /mnt/sda1 ext4 rw,nosuid,nodev,relatime 0 0
/dev/nvme3n1p1 /mnt/nvme3n1p1 ext4 rw,nosuid,nodev,relatime,stripe=8191 0 0
/dev/sdd1 /mnt/sdd1 ext4 rw,nosuid,nodev,relatime 0 0
/dev/sdd2 /mnt/sdd2 ext4 rw,nosuid,nodev,noexec,relatime 0 0
/dev/sdb3 /mnt/sdb3 fuseblk 
ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sdb4 /mnt/sdb4 ext4 rw,nosuid,nodev,relatime 0 0
/dev/sdb1 /mnt/sdb1 fuseblk 
ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 0f66e83c-a0cf-4657-85da-685b13f3c823
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=2560x1440
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=2560x1440
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-0f66e83c-a0cf-4657-85da-685b13f3c823' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 
0f66e83c-a0cf-4657-85da-685b13f3c823
echo'Loading Linux 6.1.0-7-amd64 ...'
linux   /boot/vmlinuz-6.1.0-7-amd64 
root=UUID=0f66e83c-a0cf-4657-85da-685b13f3c823 ro  quiet splash
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-6.1.0-7-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-0f66e83c-a0cf-4657-85da-685b13f3c823' {
menuentry 'Debian GNU/Linux, with Linux 6.1.0-7-amd64' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-6.1.0-7-amd64-advanced-0f66e83c-a0cf-4657-85da-685b13f3c823' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod part_gpt

Bug#1034986: xmorph: missing Breaks+Replaces for libmorph when upgrading from bullseye

2023-04-29 Thread Andreas Metzler 
On 2023-04-27 Helmut Grohne  wrote:
> Package: xmorph
> Version: 1:20150712-1
> Severity: serious
> Justification: dpkg unpack error

> Attempting to unpack xmorph/1:20150712-1 from Debian bookworm
> on a minimal Debian bullseye with libmorph/1:20140707+nmu2.1
> installed, causes an unpack error from dpkg due to
> /usr/share/man/man1/morph.1.gz being contained in both packages.

> | Selecting previously unselected package xmorph.
> | (Reading database ... 4692 files and directories currently installed.)
> | Preparing to unpack .../xmorph_1%3a20150712-1_amd64.deb ...
> | Unpacking xmorph (1:20150712-1) ...
> | dpkg: error processing archive ./xmorph_1%3a20150712-1_amd64.deb (--unpack):
> |  trying to overwrite '/usr/share/man/man1/morph.1.gz', which is also in 
> package libmorph 1:20140707+nmu2.1
> | Errors were encountered while processing:
> |  ./xmorph_1%3a20150712-1_amd64.deb
[...]

Trivial patch:
--- a/debian/control
+++ b/debian/control
@@ -38,6 +38,8 @@ Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends}
 Suggests: imagemagick | netpbm | xmorph-example
+Breaks: libmorph (<< 1:20150712-1~)
+Replaces: libmorph (<< 1:20150712-1~)
 Description: digital image warp and morph (x11)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1034958: Consequence of #951598

2023-04-29 Thread Marco d'Itri 
On Apr 29, Helge Kreutzmann  wrote:

> Reverse, I believe manpages-dev should declare:
> Breaks:   inn2-dev (<< 2.7.0-1)
> Replaces: inn2-dev (<< 2.7.0-1)
> 
> Is this fine for you?
Yes.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1034958: Consequence of #951598

2023-04-29 Thread Helge Kreutzmann 
Hello Marco,
thanks for your speedy reply.

On Sat, Apr 29, 2023 at 06:26:21PM +0200, Marco d'Itri wrote:
> Would this work for you? Please let me know ASAP since the hard freeze
> is very close.
> 
> Package: inn2-dev
> Breaks: manpages-dev (<< 6.03-2)

I'm not the maintainer of manpages, but this would be logically the
correct solution and I'm quite sure that this is the correct one.

Reverse, I believe manpages-dev should declare:
Breaks:   inn2-dev (<< 2.7.0-1)
Replaces: inn2-dev (<< 2.7.0-1)

Is this fine for you?

Greetings

  Helge
-- 
  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#1035101: Failed to detect HD if Intel RST-RAID is active

2023-04-29 Thread Thomas Viehweger 

Package: installation-reports

Boot method: USB stick
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
Date: 2023-04-29

Machine: Dell Latitude 7400
Processor: i7-8665Ulspc
Memory: 16 GB
Partitions: -

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

The Hard disk was not detected because Intel RST was configured in RAID mode.
Tried Ubuntu 23.04 installer which gives the correct hint.
After configuring Intel RST to AHCI mode, the harddisk was detected and 
installation was successful.
It would be nice if this installer could check the RST mode, too.

See: https://help.ubuntu.com/rst/

Bug#1035100: Unrelated political statement in main UI

2023-04-29 Thread Dominik George 
Package: thonny
Version: 4.0.1-1
Severity: important
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Thonny now has a Ukraine flag in its main UI, linking to a GitHub page
about the Russian invasion.

This is problematic for two reasons:

 * Thonny is used for education, and education should, inherently,
   be free of political views, if not related to the subject of
   the course
 * GitHub invades on user privacy, and the main UI should not
   drop users into a browser leading to a privacy-invading web
   platform

(The second point is even worse for the Python Tutor linked from the menu,
which is a shitload of tracking and advertising; will be reported separately.)

The Ukraine button should be removed (even though I personally agree with
the linked content.


This issue is a blocker for using Thonny for its original purpose, and the
context of the target group of its packaging team.

Cheers,
NIk


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

Kernel: Linux 6.1.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=C.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 thonny depends on:
ii  mypy   1.0.1-1
ii  pylint 2.16.2-2
ii  python33.11.2-1+b1
ii  python3-asttokens  2.2.1-1
ii  python3-docutils   0.19+dfsg-6
ii  python3-jedi   0.18.2-1
ii  python3-mypy   1.0.1-1
ii  python3-pip23.0.1+dfsg-1
ii  python3-pkg-resources  66.1.1-1
ii  python3-send2trash 1.8.1~b0-2
ii  python3-serial 3.5-1.1
ii  python3-tk 3.11.2-2
ii  python3-venv   3.11.2-1+b1
ii  python3-wheel  0.38.4-2

Versions of packages thonny recommends:
ii  xsel1.2.0+git9bfc13d.20180109-4
ii  zenity  3.44.0-1

Versions of packages thonny suggests:
ii  python3-distro  1.8.0-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iMAEARYKAGgWIQSk6zxRYJYchegBkTEK5VTlRg4b3QUCZE1EjzEaaHR0cHM6Ly93
d3cuZG9taW5pay1nZW9yZ2UuZGUvZ3BnLXBvbGljeS50eHQuYXNjGBxuYXR1cmVz
aGFkb3dAZGViaWFuLm9yZwAKCRAK5VTlRg4b3W4iAQCDRLgBVM6VDoiHrs1KOhmb
CItExlVFSHIILuWryqqZFAD9EHQLnjEttKONGgDJw84mhOnmxUn9yqh11AlSlH2l
eQk=
=tOF6
-END PGP SIGNATURE-

Bug#1031401: postgrey.service %r specifier deprecated

2023-04-29 Thread Mathias Gibbens 
  As I upgrade systems, I'm encountering this warning as well. I
haven't looked into what the fix would require, but I hope it could be
a targeted fix appropriate for an upload during the hard freeze, so
bookworm can ship with a version of postgrey that isn't emitting this
message.

Mathias

On Thu, 16 Feb 2023 15:54:59 +0100 Yuri D'Elia  wrote:
> Source: postgrey
> Version: 1.37-1.1
> Severity: normal
> 
> systemd complains about %r usage when reloading postgrey's service file:
> 
> postgrey.service: Specifier '%r' used in unit configuration, which is
> deprecated. Please update your unit file, as it does not work as
> intended.


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

Bug#1034958: Consequence of #951598

2023-04-29 Thread Marco d'Itri 
Would this work for you? Please let me know ASAP since the hard freeze
is very close.

Package: inn2-dev
Breaks: manpages-dev (<< 6.03-2)

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#948674: Any news on the otter browser packaging?

2023-04-29 Thread Martin Quinson 
Hello Gürkan,

The link you provided to the prospective package returns a 404, unfortunately.
Could you please provide a link to your current code for other to contribute?

Thanks in advance, 
Mt

-- 
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.



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

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Steve McIntyre 
On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote:
>
>On 4/29/23 07:23, Steve McIntyre wrote:
>> Hi Peter,
>> 
>> Could you please share a copy of the installer logs? You should be
>> able to find them in /var/log/installer on the installed system.
>there is no file "installer" in /var/log

Right, it's a directory with multiple files in it. Could you also
share the other files please?

>I found /var/log/installer/syslog

Thanks...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt

Bug#1035099: RFS: sentrypeer/3.0.0-1 -- SIP peer to peer honeypot for VoIP

2023-04-29 Thread Gavin Henry 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : sentrypeer
   Version  : 3.0.0-1
   Upstream contact : Gavin Henry - ghe...@sentrypeer.org
 * URL  : https://sentrypeer.org
 * License  : GPL-2.0 or GPL-3.0
 * Vcs  : https://github.com/SentryPeer/SentryPeer
   Section  : net

The source builds the following binary packages:

  sentrypeer - SIP peer to peer honeypot for VoIP

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sentrypeer/sentrypeer_3.0.0-1.dsc

Changes for the initial release:

 sentrypeer (3.0.0-1) UNRELEASED; urgency=medium
 .
   * Initial release
--
Kind Regards,

Gavin Henry.
https://sentrypeer.org

Bug#1027456: Bug#1031982: bullseye-pu: package gcc-10/10.2.1-6+deb11u1

2023-04-29 Thread Salvatore Bonaccorso 
Hi,

On Sun, Feb 26, 2023 at 11:39:02AM +0100, Salvatore Bonaccorso wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bullseye
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: gcc...@packages.debian.org, j...@debian.org, d...@ubuntu.com, 
> dia...@skoll.ca, h...@knorrie.org, 1027...@bugs.debian.org, car...@debian.org
> Control: affects -1 + src:gcc-10
> 
> Dear stable release managers, hi Matthias,
> 
> When compiling 6.1.y kernel with gcc-10 (relevant for backports).
> It was back reported at
> https://lore.kernel.org/stable/187e8f10-2b73-3a18-d9ad-48b2d84bd...@pm.kalamlacki.eu/
> and in #1027456. It can be shown as well with a reduced testcase:
> 
> cut-cut-cut-cut-cut-cut-
> unsigned int
> strlen(char *s) {
>   for (; *s;)
> ;
> }
> 
> struct i2c_adapter {
>   char name[48];
> };
> 
> struct {
>   int instance;
>   struct i2c_adapter i2c_adap[];
> } * init_cx18_i2c_cx;
> 
> const struct i2c_adapter cx18_i2c_adap_template = {""};
> int init_cx18_i2c___trans_tmp_1;
> 
> void
> init_cx18_i2c() {
>   int i = 0;
>   for (;; i++) {
> init_cx18_i2c_cx->i2c_adap[i] = cx18_i2c_adap_template;
> init_cx18_i2c___trans_tmp_1 = strlen(init_cx18_i2c_cx->i2c_adap[i].name);
>   }
> }
> cut-cut-cut-cut-cut-cut-
> 
> and in gcc upstream at
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824 .
> 
> The debdiff attached cherry-picks the upstream commit and was verified
> for both the testcase above and through Hans van Kranenburg as well
> for the kernel, in https://bugs.debian.org/1027456#61
> 
> So in order to make for bullseye-backports the 6.1.y kernel possible
> we need something to move forward.
> 
> Matthias, comments?

Is there interest in seeing this in bullseye? For the official bpo Ben
has wokarounded the entry, so the Debian backports are not directly
anymore affected by this:

https://salsa.debian.org/kernel-team/linux/-/commit/1f327c0c51ed9ca0a60c4a755feec29ffe48f0a0

But other self-compiling newer kernels might be affected.

The change was only tested against the specific case, so thus further
input is needed.

Otherwise we can as well drop this proposed update if there is not
enough confidence.

Regards,
Salvatore

Bug#989632: dash: remove unnecessary diversion of /bin/sh

2023-04-29 Thread Luca Boccassi 
On Wed, 9 Jun 2021 12:18:58 +0200 Helmut Grohne 
wrote:
> > Upshot: the proposal below doesn't bring us closer to that ideal,
> but
> > it doesn't bring us further away either.  And I like the idea of
> > making the default configuration simpler.
> 
> \o/
>
> > Summary: I like what this patch aims to do; I think it needs some
> tweaking to
> > be easier to read but then it should be good to apply.
> 
> Updated patch attached.

I've rebased the patch, including the change currently in the
debian/experimental branch to drop the ash diversion upgrade path, and
done the following testing in a bookworm amd64 chroot:

Without sh -> bash diversion:

upgrade dash bookworm -> dash patched
upgrade dash bullseye -> dash bookworm -> dash patched
upgrade dash bullseye -> dash patched
downgrade dash patched -> dash bookworm
downgrade dash patched -> dash bullseye

Then, downgrade dash to bullseye, install sh -> bash diversion via
debconf ('echo "dash dash/sh boolean false" | debconf-set-selections'
and then 'dpkg-reconfigure dash'), then repeated the set above.

In all upgrade cases we end up with no diversions configured and sh ->
dash. In the downgrade to bullseye case without setting debconf we go
back to having the diversion in place.

In the downgrade from patched to bullseye case with debconf set to
false there is no diversion in place, but from current bookworm to
bullseye the bash diversion is restored - is this something that needs
to be fixed? Changing debconf back to 'true' and doing a reconfigure
readds it already as things stand. Do we care about this use case?
Given bash as /bin/sh is really not supported anymore, I tend to think
that we don't and it's fine as-is.

MR: https://salsa.debian.org/debian/dash/-/merge_requests/19

I think we should ship these changes in bookworm. Why?

- we get diversion-less essential package set already in bookworm
- we get diversion-less uber-essential dash already in bookworm
- we get maintainer-script free uber-essential dash in trixie
- in case we need to go down the canonicalization-by-dh forced
migration path in trixie to lift the moratorium on moving files, we
don't have /bin/sh diversions as a blocker and the path remains open

Yes, I realize it is late, and I wish I had come across this ticket
some months ago. But we still have time, and the benefits are great :-)

-- 
Kind regards,
Luca Boccassi


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

Bug#1032655: psi-plus segfaults

2023-04-29 Thread Mad Horse 
This issue seems to only occur when running psi-plus under wayland. It will not 
occur when only X (either Xorg, Xwayland by running `WAYLAND_DISPLAY="" 
psi-plus` or ssh-forwarded X) is available.

Bug#907852: Potential patch for #907852

2023-04-29 Thread Helge Kreutzmann 
tags 907852 + patch
forwarded 907852 https://github.com/glanois/abcde/issues/3
thanks

By private e-mail, I received the follwing information:


Hi -

I ran into this same problem myself yesterday -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907852

I diagnosed and fixed the problem.  See
https://github.com/glanois/abcde/issues/3

I located a bug report for this in the abcde Bugzilla -
https://abcde.einval.com/bugzilla/show_bug.cgi?id=100

I added a comment there.


Greetings

  Helge
-- 
  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#1034939: [Pkg-rust-maintainers] Bug#1034939: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye

2023-04-29 Thread Fabian Grünbichler 
On Fri, Apr 28, 2023 at 08:42:07PM +0100, Peter Green wrote:
> On 28/04/2023 18:58, Fabian Grünbichler wrote:
> > I see no practical issue with 2 meaning we can't have multiple semver
> > suffix packages variants of a single crate installed - having the
> > unversioned and one semver suffix package in one suite at any given time
> > should already be the exception, having more than that should be even
> > more rare,
> 
> In an ideal world I would agree, the transition from semver
> "n" to semver "n+1" would be complete before the transition
> from semver "n+1" to semver "n+2" starts.
> 
> I've certainly seen cases where that didn't happen though.
> clap springs to mind as a currently ongoing one where we
> have versions 2, 3 and 4 of clap in bookworm and clap 2
> still has more users than clap 3 and 4 combined.

in the archive, yes. in one transitive build dep tree that requires them
to be co-installed?

there are only a few crates that come my mind that bump that often and
are that widely used that we might run into it. clap ticks the first
box, but since it's mainly used by binaries directly (it's for argument
parsing after all ;)). nom would be a realistic use case where a big
project might transitively pull in 3 versions at some point (we
currently have 3.x, 4.x and 7.x (unversioned) in the archive, but 3.x
and 4.x seem to be cruft and removable.

I did a quick check (obviously, this is only a point-in-time snapshot!),
right now we have rust binaries with the following 18 semver suffix
dependencies in their transitive build dep tree in unstable (according
to X-Cargo-Built-Using):

rust-ahash-0.7 (= 0.7.6-11)
rust-arrayvec-0.5 (= 0.5.2-2)
rust-blake2b-simd-0.5 (= 0.5.11-1)
rust-block-buffer-0.9 (= 0.9.0-1)
rust-cfg-if-0.1 (= 0.1.10-2)
rust-clap-2 (= 2.34.0-3)
rust-clap-3 (= 3.2.23-4)
rust-digest-0.9 (= 0.9.0-2)
rust-env-logger-0.7 (= 0.7.1-3)
rust-foreign-types-0.3 (= 0.3.2-1)
rust-foreign-types-shared-0.1 (= 0.1.1-1)
rust-md-5 (= 0.10.1-1)
rust-mio-0.6 (= 0.6.23-2)
rust-semver-0.9 (= 0.9.0-3)
rust-semver-parser-0.7 (= 0.7.0-1)
rust-sha-1-0.9 (= 0.9.8-1)
rust-sha2-0.9 (= 0.9.9-2)
rust-sha3-0.9 (= 0.9.1-1)

of these, only three are (transitively) depended on in both semver
suffix and unversioned variants by any one package according to
X-Cargo-Built-Using:

rust-cfg-if is used in two versions by:
 qwertone
 alacritty
 bat
 fd-find
 libslirp-helper
 rust-code-analysis-cli
 sniffglue

rust-mio by:
 alacritty
 libslirp-helper

rust-semver by:
 grcov
 rusty-tags

keep in mind that this possible misses some additional dependency trees
that are not resulting in any binary crate binary packages (e.g.,
packaging efforts that are not yet finished).

> >and there should be no need to have them *installed* at the
> >same time since these packages are only used as build deps.
> 
> More than one semver of the same crate can be used in the same
> build process. Also collapse_features means that crates often end
> up in the transitive build-dependency graph of a package even
> though they are not actually used in the build.
> 
> I feel this is the kind of thing that would rarely cause problems,
> but when it does cause problems they would be of the
> "painted into a corner" type that are very difficult to deal with.

well, dealing with boils down to either:
- delay the crate update until more users of the outdated version have
  upgraded upstream and we can drop an old version
- write the patches for doing that upgrade and submit them upstream
- fork the oldest version in Debian to give a new name and patch its
  users (meh)
- manually dropping the Breaks+Replaces after ensuring that the
  offending combination of versions doesn't exist in the archive anymore

the first two are valid options IMHO, and decrufting an old version
before introducing a second old version into the archive seems desirable
in almost all cases that I can think of, regardless of whether it is
*needed* or not.

that being said - I now did some practical tests:
- install librust-mio-dev from bullseye
- install librust-mio-extras-dev from bookworm (which depends on
  mio 0.6)

now do a regular dist-upgrade, no problem, since librust-mio-dev gets
unpacked first (old files for 0.6.23 gone) and only then
librust-mio-0.6-dev gets unpacked (new files for 0.6.23 are not
conflicting) - that might just be luck though? or the Breaks guiding
the ordering, even though technically it only ensures that the broken
package is deconfigured, not that it is upgraded?

I see no practical difference when repeating the experiment with
librust-mio-0.6-dev patched + bumped to switch the B+R to
librust-mio-dev (<< 0.6.24~), the upgrade works just as fine.

with Replaces + Conflicts on librust-mio-0.6.23-dev, the upgrade works
as well. attempting to install the librust-mio-dev package from bullseye
then removes the librust-mio-0.6-dev package cause of the conflicts, as
desired and expected. the same is true with the current package from
bookworm as well as with the

Bug#1035076: Subject: Regarding the reported bug in Plymouth package

2023-04-29 Thread Manuel Rosa 
Dear Maintainer,

I am writing to you regarding the reported bug in the Plymouth package for
Debian. As a member of the development team, I would like to reinforce the
request made by one of our team members regarding the review of the code.

We understand that you may receive a large number of bug reports, but we
believe that this particular issue deserves attention. It is affecting the
user experience and, as a result, may discourage some users from using the
Debian operating system.

We appreciate your hard work and dedication to maintaining the Plymouth
package, and we understand that reviewing the code may take some time.
However, we kindly request that you prioritize this issue and keep us
updated on its progress.

Thank you for your time and consideration.

Best regards, Manuel Rosa

Bug#1034958: Consequence of #951598

2023-04-29 Thread Helge Kreutzmann 
Hello *,
I had a look at this RC bug. The problem was detected in #1004888 on 
the inn2 side and properly resolved within the package, however, as
the fix was not coordinated with manpages, no package relationships
were set (see below).

On the manpages side this was dealt (partially) with in #951598. 
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug=951598;msg=16
and the final changelog entry:
* Reinstall file.3 as it is no longer conflicts with newer release
  of inn2-dev.

However, this neither introduced the correct package relationships as
documented here:
https://wiki.debian.org/PackageTransition

This sitaution is #9 in the above wiki page, requiering both packages 
to act on.

Thus manpages needs another upload containing (only) the fixed
package relationship.

Similarly, inn2 needs the correct pacakge relastionships as well (in a
coordinated fashion).

If you need help preparing this trivial fix please let me know[1].

Greetings

Helge

[1] Tobias, guess who would be sponsoring it so maybe a MU is much
quicker :-))
-- 
  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#1035034: unblock: libmodulemd/2.14.0-3

2023-04-29 Thread Peter Pentchev 
Control: tags -1 -moreinfo

On Fri, Apr 28, 2023 at 08:55:51PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo confirmed
> 
> On 2023-04-28 04:58:51 +0300, Peter Pentchev wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > X-Debbugs-Cc: libmodul...@packages.debian.org, 
> > team+pkg-...@tracker.debian.org, r...@debian.org
> > Control: affects -1 + src:libmodulemd
> > 
> > Please unblock package libmodulemd; this is a pre-approval request
> > before I upload version 2.14.0-3 to unstable.
> 
> Please remove the moreinfo tag once the package is available in
> unstable.

libmodulemd-2.14.0-3 is in unstable now and it is already built for
all release architectures.

Thanks!

> > In version 2.13.0-1, I moved a file from the libmodulemd-dev package to
> > the gir1.2-modulemd-2.0 one, and I forgot to add the appropriate
> > Breaks+Replaces relationship. Helmut Grohne kindly reminded me in
> > the severity: serious bug #1034935 (thanks!).
> > 
> > [ Reason ]
> > Declare the Breaks+Replaces relationship so that dpkg will not fail to
> > unpack the new version of the gir-* package over the old version of
> > the -dev one.
> > 
> > [ Impact ]
> > An upgrade from bullseye to bookworm will break, see #1034935.
> > 
> > [ Tests ]
> > piuparts, I guess... no idea why I did not notice that :(
> > 
> > [ Risks ]
> > IMHO, no risk 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 testing
> > 
> > unblock libmodulemd/2.14.0-3
> 
> > diff -Nru libmodulemd-2.14.0/debian/changelog 
> > libmodulemd-2.14.0/debian/changelog
> > --- libmodulemd-2.14.0/debian/changelog 2022-12-26 13:38:43.0 
> > +0200
> > +++ libmodulemd-2.14.0/debian/changelog 2023-04-28 04:48:28.0 
> > +0300
> > @@ -1,3 +1,10 @@
> > +libmodulemd (2.14.0-3) unstable; urgency=medium
> > +
> > +  * Declare that the gir-* package Breaks+Replaces older versions of
> > +the -dev one. Closes: #1034935
> > +
> > + -- Peter Pentchev   Fri, 28 Apr 2023 04:48:28 +0300
> > +
> >  libmodulemd (2.14.0-2) unstable; urgency=medium
> >  
> >* Use the GitHub API in the watch file.
> > diff -Nru libmodulemd-2.14.0/debian/control 
> > libmodulemd-2.14.0/debian/control
> > --- libmodulemd-2.14.0/debian/control   2022-12-26 13:38:30.0 
> > +0200
> > +++ libmodulemd-2.14.0/debian/control   2023-04-28 04:45:57.0 
> > +0300
> > @@ -70,6 +70,8 @@
> >  Section: introspection
> >  Architecture: any
> >  Multi-Arch: same
> > +Breaks: libmodulemd-dev (<< 2.13.0-1~)
> > +Replaces: libmodulemd-dev (<< 2.13.0-1~)
> >  Depends:
> >   ${gir:Depends},
> >   ${misc:Depends},
> 
> 
> 
> 
> -- 
> Sebastian Ramacher

-- 
-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Steve McIntyre 
Hi Peter,

Could you please share a copy of the installer logs? You should be
able to find them in /var/log/installer on the installed system.

On Sat, Apr 29, 2023 at 07:02:43AM -0700, Peter Ehlert wrote:
>Package: grub-installer
>Boot method: USB
>Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
>download from Debian
>Date: 2023-04-28 ~17
>
>Machine: HP Z820 Workstation
>Processor: 2x 8-core model: Intel Xeon E5-2687W
>Memory: 47.06 GiB
>Partitions:
>peter@RC2net:~$ df -T
>Filesystem Type 1K-blocks    Used Available Use% Mounted on
>udev   devtmpfs  24636332   0  24636332   0% /dev
>tmpfs  tmpfs  4934304    1988   4932316   1% /run
>/dev/sda6  ext4  28660644 4485828  22693600  17% /
>tmpfs  tmpfs 24671508   0  24671508   0% /dev/shm
>tmpfs  tmpfs 5120  12  5108   1% /run/lock
>/dev/sda8  ext4  19046484 908  18052708   1% /home
>tmpfs  tmpfs  4934300  56   4934244   1% /run/user/1000
>peter@RC2net:~$
>
>Output of lspci and lspci -n:
>
>peter@RC2net:~$ lspci
>00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
>00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 1a (rev 07)
>00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 1b (rev 07)
>00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 2a (rev 07)
>00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root
>Port 3a in PCI Express Mode (rev 07)
>00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map,
>VTd_Misc, System Management (rev 07)
>00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status
>and Global Errors (rev 07)
>00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
>00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Virtual Root Port (rev 05)
>00:16.0 Communication controller: Intel Corporation C600/X79 series chipset
>MEI Controller #1 (rev 05)
>00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r
>Controller (rev 05)
>00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT
>Controller (rev 05)
>00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>Connection (Lewisville) (rev 05)
>00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2
>Enhanced Host Controller #2 (rev 05)
>00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High
>Definition Audio Controller (rev 05)
>00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 2 (rev b5)
>00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 5 (rev b5)
>00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
>Root Port 3 (rev b5)
>00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2
>Enhanced Host Controller #1 (rev 05)
>00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
>00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller
>(rev 05)
>00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA
>RAID Controller (rev 05)
>00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host
>Controller (rev 05)
>01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
>Connection
>02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express
>Fusion-MPT SAS-2 (rev 05)
>04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset
>4-Port SATA Storage Control Unit (rev 05)
>05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730]
>(rev a1)
>05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev
>a1)
>08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI
>Host Controller (rev 02)
>09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a
>Controller (rev 70)
>3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev
>07)
>3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0
>(rev 07)
>3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0
>(rev 07)
>3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev
>07)
>3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1
>(rev 07)
>3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1
>(rev 07)
>3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 0 (rev 07)
>3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 1 (rev 07)
>3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 2 (rev 07)
>3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control
>Unit 3 (rev 07)
>3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt
>Control Registers (rev 07)
>3f:0b.3 System peripheral:

Bug#947388: anki: Bug seems to be resolved in Debian Bullseye

2023-04-29 Thread Rahul Amaram 
Package: anki
Followup-For: Bug #947388

Dear Maintainer,

This bug seems to be resolved in Debian Bullseye.

Thanks,
Rahul.

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages anki depends on:
ii  libjs-jquery3.5.1+dfsg+~3.5.5-7
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-ui 1.12.1+dfsg-8+deb11u1
ii  libjs-mathjax   2.7.9+dfsg-1
ii  libqt5core5a5.15.2+dfsg-9
ii  python3 3.9.2-3
ii  python3-bs4 4.9.3-1
ii  python3-decorator   4.4.2-2
ii  python3-distro  1.5.0-1
ii  python3-distutils   3.9.2-1
ii  python3-jsonschema  3.2.0-3
ii  python3-markdown3.3.4-1
ii  python3-pyaudio 0.2.11-1.3+b1
ii  python3-pyqt5   5.15.2+dfsg-3
ii  python3-pyqt5.qtwebchannel  5.15.2+dfsg-3
ii  python3-pyqt5.qtwebengine   5.15.2-2
ii  python3-requests2.25.1+dfsg-2
ii  python3-send2trash  1.6.0~b1+git20210122.2eb3242-1

Versions of packages anki recommends:
ii  python3-matplotlib  3.3.4-1

Versions of packages anki suggests:
pn  dvipng  
pn  lame
ii  mpv 0.32.0-3

-- no debconf information

Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)

2023-04-29 Thread Nilesh Patra 
On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote:
> and we have other errors for other architectures which all contain
> the string "numba".  IMHO this is a mess we can hardly fix in hard
> freeze.  I see only two chances:

I haven't done a thorough research but it is probably originating from
numba itself.

>1. Restrict the architectures to amd64 and ppc64el (which are
>   the only ones where the build succeeds or

We maybe a little too late for this as well.

>2. Remove the package from testing for the moment.  The only
>   rdepends is currently pan-grazing-incidence which will be
>   lowered to suggests once we re-render debian-pan metapackages.

It is a possible option but it maybe a useful package in itself.
This numba situation has arised due to uploading a new upstream update
of genx during hard freeze (I wonder why this happened).
I think we do have a third alternative:

> What do you think?

3. Cherry-pick the commit[6] for fixing this bug and upload to t-p-u by
asking release team first, or go ahead with a +really scheme whichever
seems better, but it needs to be done quickly.

> [1] 
>

Bug#1035097: grub-install: efivars_set_variable fails due to dump-* files in /sys/firmware/efi/efivars

2023-04-29 Thread Daniel Savi 
Package: grub-install
Severity: normal
X-Debbugs-Cc: pub...@gaess.ch

Dear Maintainer,

When updating our headless server, we've got the following warning:
grub-install: Warnung: Cannot set EFI variable Boot.
grub-install: Warnung: efivarfs_set_variable: writing to fd 8 failed: Auf dem
Gerät ist kein Speicherplatz mehr verfügbar.
grub-install: Warnung: _efi_set_variable_mode: ops->set_variable() failed: Auf
dem Gerät ist kein Speicherplatz mehr verfügbar.
grub-install: Fehler: failed to register the EFI boot entry: Auf dem Gerät ist
kein Speicherplatz mehr verfügbar.

The german part means: out of memory (or disk space)

The /sys/firmware/efi/efivars was full of "dump-*" files.
The problem seems related to this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989384

But our system is not an old Thinkpad :-) And acpi-call-dkms isn't even
installed. It is an Asrock Deskmini A300 AMD Ryzen system. It was running
Buster until this week, when updated to debian 11 bullseye. Please ignore the
system information below as I'm reporting this from my laptop (which actually
is a thinkpad) and not the affected system.

Our system couldn't reboot for more than a year (maybe even more) when issuing
"sudo reboot now". Now, after "rm /sys/firmware/efi/efivars/dump-*", grub-
install updates the efivars and our server reboots properly for the first time
after years!

I'm writing to you because I think the problem may be more widespread than
known. I had no idea how to fix the reboot problem and I tried to find the
cause several times. So I'd suggest to automatically look for such dump-* files
when this error arises and delete them with the install-grub script. If you
think this is too dangerous, you could add a comment to the warning, that users
should check if the have any /sys/firmware/efi/efivars/dump-* files and delete
them manually.

I also would like to thank you for all the work you put into Debian, I
appreciate it very much!
Kind regards, Daniel


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

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

Bug#1035096: installation-report Bookworm RC2 GRUB not installed

2023-04-29 Thread Peter Ehlert 

Package: grub-installer
Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso
download from Debian
Date: 2023-04-28 ~17

Machine: HP Z820 Workstation
Processor: 2x 8-core model: Intel Xeon E5-2687W
Memory: 47.06 GiB
Partitions:
peter@RC2net:~$ df -T
Filesystem Type 1K-blocks    Used Available Use% Mounted on
udev   devtmpfs  24636332   0  24636332   0% /dev
tmpfs  tmpfs  4934304    1988   4932316   1% /run
/dev/sda6  ext4  28660644 4485828  22693600  17% /
tmpfs  tmpfs 24671508   0  24671508   0% /dev/shm
tmpfs  tmpfs 5120  12  5108   1% /run/lock
/dev/sda8  ext4  19046484 908  18052708   1% /home
tmpfs  tmpfs  4934300  56   4934244   1% /run/user/1000
peter@RC2net:~$

Output of lspci and lspci -n:

peter@RC2net:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 1a (rev 07)
00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 1b (rev 07)
00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 2a (rev 07)
00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express 
Root Port 3a in PCI Express Mode (rev 07)
00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address 
Map, VTd_Misc, System Management (rev 07)
00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control 
Status and Global Errors (rev 07)

00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Virtual Root Port (rev 05)
00:16.0 Communication controller: Intel Corporation C600/X79 series 
chipset MEI Controller #1 (rev 05)
00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r 
Controller (rev 05)
00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT 
Controller (rev 05)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 05)
00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 
Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 2 (rev b5)
00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 5 (rev b5)
00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI 
Express Root Port 3 (rev b5)
00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 
Enhanced Host Controller #1 (rev 05)

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC 
Controller (rev 05)
00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset 
SATA RAID Controller (rev 05)
00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host 
Controller (rev 05)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection
02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 
PCI-Express Fusion-MPT SAS-2 (rev 05)
04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset 
4-Port SATA Storage Control Unit (rev 05)
05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 
730] (rev a1)
05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller 
(rev a1)
08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a 
Controller (rev 70)
3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 
(rev 07)
3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 0 (rev 07)
3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 0 (rev 07)
3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 
(rev 07)
3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 1 (rev 07)
3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 
Reut 1 (rev 07)
3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 0 (rev 07)
3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 1 (rev 07)
3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 2 (rev 07)
3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power 
Control Unit 3 (rev 07)
3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt 
Control Registers (rev 07)
3f:0b.3 System peripheral: Intel Corporation Xeon E5/Core i7 Semaphore 
and Scratchpad Configuration Registers (rev 07)
3f:0c.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast 
Register 0 (rev 07)
3f:0c.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast 
Register 0 (rev 07)

Bug#1035095: lomiri-desktop-session: Unable to install aside gnome-core

2023-04-29 Thread Adrien Dorsaz 

Package: lomiri-desktop-session
Severity: wishlist

Dear Maintainer,

I wanted to install the Lomiri desktop to try it aside my GNOME desktop.

Although there's a conflict between lomiri-desktop-session and gnome-core.

Due to this conflict I am unable to install Lomiri without uninstalling 
GNOME.


Actually gnome-core depends on pipewire-audio and lomiri-desktop-session
depends on pulseaudio.

pulseaudio package is itself in conflict with pipewire-audio, that's why I
cannot install Lomiri aside GNOME.

As pipewire-audio installs a Pulseaudio compatible API with the 
pipewire-pulse
package, is it possible to update the lomiri-desktop-session to depends 
either

on pulseaudio or on pipewire-audio? (or, maybe, piperwire-pulse?)

Looking further, I've seen there will be also a conflict with the ayatana-
indicator-sound package which depends on pulseaudio too. The 
ayatana-indicator-

sound package is installed by the package lomiri.

Best regards,

Adrien Dorsaz


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CH:fr

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

Versions of packages lomiri-desktop-session depends on:
ii dbus 1.14.6-1
pn lomiri 
pn lomiri-terminal-app 
pn pulseaudio 

Versions of packages lomiri-desktop-session recommends:
ii content-hub 1.0.2-1
ii inotify-tools 3.22.6.0-4
ii lomiri-calculator-app 4.0.1-1
ii lomiri-camera-app 4.0.2+dfsg-1
ii lomiri-clock-app 4.0.2-1
ii lomiri-filemanager-app 1.0.2+dfsg-1
ii lomiri-gallery-app 3.0.1-1
ii lomiri-mediaplayer-app 1.0.2+dfsg-1
ii lomiri-music-app 3.0.2-1
ii morph-browser 1.0.2+dfsg-1

Versions of packages lomiri-desktop-session suggests:
ii lomiri-docviewer-app 3.0.3+dfsg-1
ii xwayland 2:22.1.9-1

Bug#1035089: bookworm: gpgv must be installed for successful upgrades

2023-04-29 Thread Justin B Rye 
Jonathan Wiltshire wrote:
> Attached patch adds a section in the upgrade guide to ensure gpgv is
> installed. Most users will have this if they have followed previous
> upgrade guidance not to skip releases. However, without it they will not
> be able to upgrade at all because the release signing key is not
> validated correctly.

A bit more explanation in the text would be helpful.  Mind you, users
who have been disregarding standard procedure to the extent of doing
leapfrog dist-upgrades seem unlikely to be paying close attention to
the procedure recommended in the bullseye-to-bookworm release notes!

I gather this is an extra precautionary step *before* the upgrade, but
is this "in case you've somehow accidentally ended up with only gpgv1
by accident" or are we expecting there to be users who have insisted
on sticking with the familiar v1 UI or something?  If there aren't,
it's hard to see why gpgv1 still exists, let alone still satisfying
apt's gpgv dependency even on bookworm... surely that has to be a bug?
If it isn't, it is at least confusing enough to need some explanation.

> +  
> +Check gpgv is installed
> +
> +  APT needs gpgv version 2 or greater to verify the 
> keys used
> +  to sign releases of . Ensure it is installed with:

Maybe something like:
APT needs gpgv version 2 or greater to verify the 
keys used
to sign releases of . Since gpgv1 technically satisfies 
the
dependency but is useful only in specialized circumstances, users may 
wish to
ensure the correct version is installed with:

> +
> +
> +$ apt install gpgv
> +
> +  

Requires root, so make it:
   # apt install gpgv
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#1035094: udev: /dev/serial/by-id/ symlinks not created anymore for USB devices

2023-04-29 Thread Felix Geyer 

Package: udev
Version: 247.3-7+deb11u2
Tags: bullseye

Since udev 247.3-7+deb11u2 /dev/serial/by-id/* symlinks are not created anymore for USB serial 
devices.

This is a regression from backporting 
udev-always-create-device-symlinks-for-USB-disks.patch

It was fixed upstream by https://github.com/systemd/systemd/pull/25246

The diff doesn't apply cleanly because we don't have
https://github.com/systemd/systemd-stable/commit/451ba55fecd8b494add2001b3ca3c1915c8fd655

Apply this commit and the PR fixes the issue for me.

Felix

Bug#1035093: ayatana-indicator-sound: Unable to install Lomiri desktop aside GNOME desktop due to pulseaudio dependency

2023-04-29 Thread Adrien Dorsaz 

Package: ayatana-indicator-sound
Severity: wishlist

Dear Maintainer,

I wanted to install the Lomiri desktop to try it aside my GNOME desktop.

Although there's a conflict between ayatana-indicator-
sound (which is installed by the lomiri package) and gnome-core packages.

Due to this conflict I am unable to install Lomiri without uninstalling 
GNOME.


Actually gnome-core depends on pipewire-audio and ayatana-indicator-
sound depends on pulseaudio.

pulseaudio package is itself in conflict with pipewire-audio, that's why I
cannot install Lomiri aside GNOME.

As pipewire-audio installs a Pulseaudio compatible API with the 
pipewire-pulse

package, is it possible to update the ayatana-indicator-
sound to depends either on pulseaudio or on pipewire-audio? (or, maybe,
piperwire-pulse?)

For your information, there's a similar issue with the package 
lomiri-desktop-

session.
So I've opened for this package a similar bug report.

This issue is not limited to the Lomiri desktop, but to all desktops 
depending

on
the ayatana-indicator-sound package.

Best regards,

Adrien Dorsaz


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CH:fr

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

Versions of packages ayatana-indicator-sound depends on:
ii ayatana-indicator-common 0.9.8-1
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4
ii init-system-helpers 1.65.2
ii libaccountsservice0 22.08.8-6
ii libayatana-common0 0.9.8-1
ii libc6 2.36-9
ii libgee-0.8-2 0.20.6-1
ii libglib2.0-0 2.74.6-2
ii libglib2.0-bin 2.74.6-2
ii libnotify4 0.8.1-1
ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1
ii libpulse0 16.1+dfsg1-2+b1
pn pulseaudio 

Versions of packages ayatana-indicator-sound recommends:
ii accountsservice 22.08.8-6
ii gnome-control-center 1:43.4.1-1
ii lomiri-system-settings 1.0.1-2
ii pavucontrol 5.0-2

Versions of packages ayatana-indicator-sound suggests:
pn lomiri-greeter-session-broadcast

Bug#1035028: unblock: iso-codes/4.15.0-1

2023-04-29 Thread Dr. Tobias Quathamer 

control: tags -1 = confirmed

Am 29.04.23 um 12:49 schrieb Sebastian Ramacher:

Control: tags -1 moreinfo confirmed

Thanks. Please go ahea and remove the moreinfo tag once the package is
available in unstable.


Hi,

the package is now uploaded to unstable. I've also added the confirmed 
tag, because your mail didn't go to the BTS, so the control command 
didn't have any effect. Hope that's okay.


Regards,
Tobias



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035092: gnome-shell: Nautilus doesn't gain focus when launched from directory search

2023-04-29 Thread Chandra Sekar 
Package: gnome-shell
Version: 43.4-1
Severity: normal
X-Debbugs-Cc: chandru...@gmail.com

Dear Maintainer,

Nautilus window does not gain focus immediately, when it is launched by 
searching
for a directory in Gnome Activities. It gains focus immediately, if
launched by choosing the "Files" application.

Steps to reproduce.

1. Launch any application, say Firefox.
2. Press the Super key to enter "Activities".
3. Type the name of any directory and hit Enter to open it.
4. Observe that the application launched in step #1 still has the focus.
5. Use Alt+Tab to change the focus to the newly opened Nautilus window.

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-adw-1 1.2.2-1
ii  gir1.2-atk-1.0   2.46.0-5
ii  gir1.2-atspi-2.0 2.46.0-5
ii  gir1.2-freedesktop   1.74.0-3
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gdm-1.0   43.0-3
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomebluetooth-3.042.5-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-gtk-4.0   4.8.3+ds-2
ii  gir1.2-gweather-4.0  4.2.0-2
ii  gir1.2-ibus-1.0  1.5.27-5
ii  gir1.2-mutter-11 43.4-2
ii  gir1.2-nm-1.01.42.4-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-rsvg-2.0  2.54.5+dfsg-1
ii  gir1.2-soup-3.0  3.2.2-2
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-webkit2-4.1   2.40.0-3
ii  gnome-backgrounds43.1-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell-common   43.4-1
ii  gsettings-desktop-schemas43.0-1
ii  gstreamer1.0-pipewire0.3.65-3
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libecal-2.0-23.46.4-2
ii  libedataserver-1.2-273.46.4-2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgjs0g 1.74.2-1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libglib2.0-bin   2.74.6-2
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-2043.2-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   3.24.37-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libical3 3.0.16-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmutter-11-0   43.4-2
ii  libnm0   1.42.4-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpolkit-agent-1-0  122-3
ii  libpolkit-gobject-1-0122-3
ii  libpulse-mainloop-glib0  16.1+dfsg1-2+b1
ii  libpulse016.1+dfsg1-2+b1
ii  libsecret-1-00.20.5-3
ii  libsystemd0  252.6-1
ii  libwayland-server0   1.21.0-1
ii  libx11-6 2:1.8.4-2
ii  libxfixes3   1:6.0.0-2
ii  python3

Bug#1035091: RM: speech-dispatcher-ibmtts [amd64] -- RoQA; ANAIS; only for i386

2023-04-29 Thread Andreas Beckmann 
Package: ftp.debian.org
Severity: normal

speech-dispatcher-contrib (0.11.0~rc2-1) experimental; urgency=medium

...
- control: Build speech-dispatcher-ibmtts only on i386.
...

 -- Samuel Thibault   Thu, 17 Jun 2021 00:07:32 +0200


Andreas

Bug#1032994: unblock: node-webpack/5.76.1+dfsg1+~cs17.16.16-1

2023-04-29 Thread Salvatore Bonaccorso 
Control: severity 1032904 serious

Hi Yadd,

On Wed, Mar 15, 2023 at 09:11:46PM +0100, Paul Gevers wrote:
> Control: tags -1 moreinfo
> 
> Hi Yadd,
> 
> On 15-03-2023 13:38, Yadd wrote:
> > [ Reason ]
> > node-webpack is vulnerable to cross-realm object access
> > (#1032904, CVE-2023-28154).
> 
> This doesn't look like a targeted fix, but rather seems to include much
> more.
> 
> How about reverting and providing a fix only for that CVE please?

have you seen Paul's comment/question above? We have now a somehow
unfortunate situation that the CVE is fixed in unstable, and it is
fixed with the last point release as well in bullseye. But it is still
open in bookworm.

I will bump for this reason the severity of #1032904 to RC as it is a
regression on this regards.

Regards,
Salvatore

Bug#1035042: wpewebkit: ftbfs riscv64 Error: open CFI at the end of file; missing .cfi_endproc directive

2023-04-29 Thread Alberto Garcia 
Control: tags -1 moreinfo

On Fri, Apr 28, 2023 at 05:57:34AM +, sun min wrote:
> Source: wpewebkit
> Version: 2.38.6-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> My sbuild for risv64 archtecture log says:

Hi, wpewebkit 2.38.x has been building fine in riscv64 for a while
without many problems:

   https://buildd.debian.org/status/logs.php?pkg=wpewebkit=riscv64

There was a failure in November 2022 seemingly because of a compiler
bug, but that's about it.

What is the exact environment that you are using to build webkit?

Berto

Bug#1035090: chkrootkit has odd output on riscv64

2023-04-29 Thread Richard Lewis 
package: chkrootkit
version: 0.57-2
severity: normal
tags: unreproducible

According to https://ci.debian.net/packages/c/chkrootkit/
the tests fail on riscv64 - but passes on all debian architectures,

Another bug that wont be fixed before bookworm, but should be
investigated a little further (this is mainly a reminder to myself to
recheck)

See here:
https://ci.debian.net/data/autopkgtest/unstable/riscv64/c/chkrootkit/32562909/log.gz

PASS: Testing: cron-with-diff-mode-03-full-after-update (chkrootkit-daily)
FAIL: cron-with-diff-mode-04-full-no-ionice

I dont see why the second one failed while the first passed.

The only difference is a stray '+d' apparently at the end of log.today
- but unless i am misreading, _not_ in the output of chkrootkit so i
dont see what the issue is.

but perhaps the tests need to include a 'cat log.today' as well to
help debug failures here.

Bug#1035089: bookworm: gpgv must be installed for successful upgrades

2023-04-29 Thread Jonathan Wiltshire 
Package: release-notes
Severity: normal
Tags: patch
X-Debbugs-Cc: j...@debian.org

Hi,

Attached patch adds a section in the upgrade guide to ensure gpgv is
installed. Most users will have this if they have followed previous
upgrade guidance not to skip releases. However, without it they will not
be able to upgrade at all because the release signing key is not
validated correctly.
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 8f176d80..cdd14a45 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -451,6 +451,16 @@ $ apt-forktracer | sort
 
   
 
+  
+Check gpgv is installed
+
+  APT needs gpgv version 2 or greater to verify the 
keys used
+  to sign releases of . Ensure it is installed with:
+
+
+$ apt install gpgv
+
+  
   
 Check package status

Bug#1034816: aide aborts with error "realloc: failed to allocate memory", exit code 22

2023-04-29 Thread Thomas Dorner 
> Well today I run it with dmalloc.  I'll need some time to handle the
> 28 GB of log-file, especially as it apparently contains at least one
> large chunk of 0-bytes.

OK, so that log file looks inconspicuous.  The reallocations are a few
various followed by one series of one permanently growing big one (up
to 1792464 bytes; maybe reading in the DB into the internal
representation?), a growing small one (growing in 4 bytes steps up to
112 bytes), a huge gap without any reallocations, lots (~55% of all) of
reallocations from 257 to something smaller and 4 ones from 99 bytes to
190 bytes).  Unfortunately that wasn't the end of the log file, there
were still ~2900 other memory actions after it.¹

I'll try something different when the failure occurs again - today it
didn't (maybe my timing was wrong), so it probably will be a few days.

Best regards, Thomas
¹ My (maybe completely wrong ;-) theory would be that dmalloc only logs
  after the call returned and it failed in the call itself.  (I logged
  using the tags log-trans and log-stats aka 0x9.)
-- 
퓣퓱퓸퓶퓪퓼 퓓퓸퓻퓷퓮퓻

Bug#1035088: unblock: gelemental/2.0.2-1

2023-04-29 Thread Graham Inggs 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gelemen...@packages.debian.org
Control: affects -1 + src:gelemental

Please unblock package gelemental

[ Reason ]
This is a maintenance release from upstream with only the following changes:
* an updated Russian translation
* fix button colours with new Yaru themes (src:yaru-theme in Debian)
* avoid FTBFS with Pango 1.50 (merged patch from Debian)

[ Impact ]
* Users will not benefit from the updated Russian translation.
* Buttons will not appear in different colours for users of new Yaru themes.

[ Tests ]
gElemental has no autopkgtests.
I have tested the gElemental UI with every Yaru theme.

[ Risks ]
The Russian translation could introduce new mistranslations.
The changes for the new Yaru themes are specifically targeted at the
new theme names, so should not be able to affect users of other
themes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [ ] attach debdiff against the package in testing

[ Other info ]
Upstream regenerated configuration files (autoreconf -fi) which
introduced a lot of noise in the debdiff.  I provide two filtered
debdiffs, one with only Debian packaging changes:
filterdiff -i '*/debian/*'
and the other with only upstream changes (excluding regenerated
configuration files and the Russian translation):
filterdiff -x '*/debian/*' -x '*/aclocal.m4' -x '*/configure' -x
'*/config.*' -x '*/ltmain.sh' -x '*/Makefile.in*' -x '*/intltool-*.in'
-x '*/po/ru.po'

unblock gelemental/2.0.2-1


debian-only.debdiff
Description: Binary data


upstream-only.debdiff
Description: Binary data

Bug#1035087: unblock: debian-archive-keyring/2023.3

2023-04-29 Thread Jonathan Wiltshire 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-archive-keyr...@packages.debian.org, j...@debian.org
Control: affects -1 + src:debian-archive-keyring

Please unblock package debian-archive-keyring

[ Reason ]
Users who upgrade from bullseye to bookworm
(debian-archive-keyring_2021.1.1 -> 2023.2) will have leftover keyrings
in /etc/apt/trusted.gpg.d as well as the new ASCII fragements.  In
contrast, users who have followed bookworm for some time do not because
an intermediate version did the right things. The jump in version for
normal upgraders reveals the issue.
This is bug #1033153.

[ Impact ]
Misleading listings of keys from apt, and the danger that user changes
don't take effect because of the duplication.

[ Tests ]
Thorough manual testing with a range of upgrade paths.

[ Risks ]
Trivial change to clean up obsolete files - the risk is low.
Source debdiff attached.

[ 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 testing


unblock debian-archive-keyring/2023.3
diff -Nru debian-archive-keyring-2023.2/debian/changelog 
debian-archive-keyring-2023.3/debian/changelog
--- debian-archive-keyring-2023.2/debian/changelog  2023-03-17 
17:03:56.0 +
+++ debian-archive-keyring-2023.3/debian/changelog  2023-03-28 
21:31:07.0 +0100
@@ -1,3 +1,9 @@
+debian-archive-keyring (2023.3) unstable; urgency=medium
+
+  * Reinstate cleanup of the APT keyrings for buster (Closes: #1033153)
+
+ -- Jonathan Wiltshire   Tue, 28 Mar 2023 21:31:07 +0100
+
 debian-archive-keyring (2023.2) unstable; urgency=medium
 
   * Reinstate buster keys for apt as fragments (Closes: #1033077)
diff -Nru 
debian-archive-keyring-2023.2/debian/debian-archive-keyring.maintscript 
debian-archive-keyring-2023.3/debian/debian-archive-keyring.maintscript
--- debian-archive-keyring-2023.2/debian/debian-archive-keyring.maintscript 
2023-03-17 17:03:56.0 +
+++ debian-archive-keyring-2023.3/debian/debian-archive-keyring.maintscript 
2023-03-28 21:23:44.0 +0100
@@ -9,6 +9,9 @@
 rm_conffile 
/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg 2022.1~~
 rm_conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg 2022.1~~
 # These ones are replaced by asc fragments
+rm_conffile /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg 2023.3~~
+rm_conffile 
/etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg 2023.3~~
+rm_conffile /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg 2023.3~~
 rm_conffile /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg 
2022.1~~
 rm_conffile 
/etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg 2022.1~~
 rm_conffile /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg 2022.1~~

Bug#1035076: plymouth: Plymouth package has defective hard-dependency on systemd

2023-04-29 Thread Laurent Bigonville 

tag 1035076 + wontfix
thanks

Le 29/04/23 à 00:10, john faulk a écrit :

Dear Maintainer,

Hello,

The Plymouth Package has a hard-dependency on systemd for installation. This
should not be the case, seeing as there are initscripts present for it. I have
tested a simple fix where elogind is added in the source control file as an
alternative to systemd's dependency, and it has worked every time I have tried
it. This will allow non-systemd users to use plymouth, and is a very simple
fix.


Like explained in bug #1035076, the fact that systemd is pulled by the 
plymouth package doesn't mean you cannot use it with an other initsystem 
on debian, the package that actually changes the default initsystem is 
"systemd-sysv", not "systemd"


Removing the dependency might break plymouth at it requires some udev 
rules files that are shipped by the systemd package (the rules are used 
to tag the framebuffer devices/heads installed on the machines).


So removing that could break some setup

Kind regards,

Laurent Bigonville

Bug#1035017: unblock: pdl/1:2.081-2

2023-04-29 Thread Sebastiaan Couwenberg 

Control: tags -1 - moreinfo

On 4/29/23 10:51, Sebastian Ramacher wrote:

On 2023-04-27 16:52:36 +0200, Bas Couwenberg wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:pdl

Please unblock package pdl

[ Reason ]
It fixed the upgrade failure from bullseye reported in #1034942.

[ Impact ]
Upgrade from bullseye to bookworm fails.

[ Tests ]
autopkgtest, Salsa CI, and upstream test suite.

I've manually verified the fix for #1034942 by upgrading a bullseye chroot to 
bookworm using the fixed pdl from my local repo.

[ Risks ]
Low, the other changes that were pending in git since 1:2.081-1 don't risk 
breakage.

[ 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 testing

[ Other info ]
The package has been uploaded to unstable.

unblock pdl/1:2.081-2



diff -Nru pdl-2.081/debian/changelog pdl-2.081/debian/changelog
--- pdl-2.081/debian/changelog  2022-10-27 18:57:46.0 +0200
+++ pdl-2.081/debian/changelog  2023-04-27 15:54:44.0 +0200
@@ -1,3 +1,22 @@
+pdl (1:2.081-2) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Bas Couwenberg ]
+  * Add Rules-Requires-Root to control file.
+  * Add a debhelper sequence to run dh_pdl.


Would you mind re-uploading without that change? It doesn't seem to
provide a targetted fix for a bug report.


I'd rather not. While not a targeted fix, it also doesn't risk 
introducing regressions.



+  * Bump Standards-Version to 4.6.2, no changes.
+  * Add Breaks/Replaces on libpdl-stats-perl to fix upgrade.
+(closes: #1034942)
+
+  [ Debian Janitor ]
+  * Update lintian override info to new format:
++ debian/source/lintian-overrides: line 2
++ debian/pdl.lintian-overrides: line 6, 10, 22, 28
+  * Use secure URI in Homepage field.
+
+ -- Bas Couwenberg   Thu, 27 Apr 2023 15:54:44 +0200
+
  pdl (1:2.081-1) unstable; urgency=medium
  
* Team upload.  


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1035086: for post-bookworm: failures on non-debian archs: chkproc fails on hurd

2023-04-29 Thread Richard Lewis 
package: chkrootkit
version: 0.57-2
severity: normal

This bug is a reminder of an issue that don't affect debian but seem
to show up on non-debian architectures.
I will look at this once bookworm is released

chkproc fails on hurd - i think the #endif on line 252 of patched
chkproc.c should be at the end -- this is matching the very first #if
on line 61 so there is no issue unless run on non-linux

See: https://buildd.debian.org/status/package.php?p=chkrootkit#problem-3

chkproc.c:443:11: note: include ‘’ or provide a declaration
of ‘isdigit’
chkproc.c:454:7: error: ‘dirproc’ undeclared (first use in this
function); did you mean ‘proc’?
  454 |   dirproc[atol(tmp_d_name)] = 1;
  |   ^~~
  |   proc
chkproc.c:456:4: warning: implicit declaration of function ‘closedir’
[-Wimplicit-function-declaration]
  456 |closedir(proc);
  |^~~~
chkproc.c:415:25: warning: unused parameter ‘verbose’ [-Wunused-parameter]
  415 | void populate_psdir(int verbose)
  | ^~~
make[1]: *** [Makefile:52: chkproc] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true"
returned exit code 2
make: *** [debian/rules:10: binary-arch] Error 255

Bug#1035047: unblock: [pre-approval] xdg-desktop-portal-wlr/0.7.0-1

2023-04-29 Thread Jochen Sprickerhof 

Control: tags -1 - moreinfo

* Sebastian Ramacher  [2023-04-29 10:25]:

On 2023-04-28 11:26:00 +0200, Jochen Sprickerhof wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: xdg-desktop-portal-...@packages.debian.org, Birger Schacht 

Control: affects -1 + src:xdg-desktop-portal-wlr

Please unblock package xdg-desktop-portal-wlr

[ Reason ]
Latest Chromium in testing fails to screen share with
xdg-desktop-portal-wlr. This is fixed with xdg-desktop-portal-wlr 0.7.0.


ACK. Please remove the moreinfo tag once the package is available in
unstable.


Thanks, it was just accepted into unstable.

Cheers Jochen


signature.asc
Description: PGP signature

Bug#1034652: unblock: reportbug/12.0.0

2023-04-29 Thread Nis Martensen 
control: tags -1 - moreinfo

> Please go ahead and remove the moreinfo tag once the upload happened.

Thank you Paul. Uploaded, removing moreinfo tag.

 Nis

Bug#1035025: chkrootkit.service does not run every day if system gets suspended

2023-04-29 Thread Richard Lewis 
On Thu, 27 Apr 2023, 20:57 richardn,  wrote:

Thanks for the bug report - this is an interesting one! (see below)

/lib/systemd/system/chkrootkit.timer contains -
>
> # then run every day
> OnUnitActiveSec=24h
>
> This is a monotonic timer. According to systemd.timer manpage -
>
> These are monotonic timers, independent of wall-clock time and
> timezones. If the computer is temporarily suspended, the monotonic
> clock generally pauses, too.
>
 a realtime (i.e. wallclock) timer should be used e.g
>
> OnCalendar=daily
>

maybe, although also - if the system is suspended for 24h, is there
actually a benefit in having the check run on resume?
as you say, it will (i think - it seems to work for me!) run once the
system has been active for a cumulative 24h

you can do 'systemctl edit systemd.timer' and make a drop-in that changes
the setting locally
 (you might need to reset OnUnitActiveSec to empty as well as setting
OnCalendar=daily in the drop-in file)

i'm not sure what the debian policy on this is (i dont think there is
one?), or what the best default is - am not at all averse
to changing the default, but given:
- how close to the  bookworm release we are
- this seems to be a matter of opinion as to what setting is the best
default
- it's quite hard to properly test the impact of these settings
- how easy it is to change locally (see above)

i am tempted to leave it as-is for now (and revisit post-release) - if
other people think the default should change, please respond to this bug
too!

Bug#1024504: libvirt FTCBFS: misdetects linux/kvm.h

2023-04-29 Thread Andrea Bolognani 
[sending again in a form that will be visible on the bug's page]

On Sun, Nov 20, 2022 at 06:01:13PM +0100, Helmut Grohne wrote:
> libvirt fails to cross build from source when building on amd64 for
> armhf or armel. It uses meson's has_header to figure out whether
> linux/kvm.h exists and due to linux-libc-dev:amd64 being installed,
> /usr/include/linux/kvm.h exists. has_header is able to figure this out
> without actually including it. When libvirt actually #includes it,
> asm/kvm.h is missing as that's a multiarch headers. Thus linux headers
> should be tested with check_header, which actually #includes it. While
> has_header may seem relatively useless at this point, it is far quicker
> than check_header. Thus I'm proposing to only employ check_header for
> linux headers. I'm attaching a patch for your convenience.

Thanks for the report and tentative patch, Helmut!

I've decided to go for a slightly different approach when submitting
the change upstream [1]; after verifying that the overhead caused by
just using check_header() all the time is negligible, we ultimately
went for that approach [2][3].

The fix is going to be part of libvirt 9.3.0, which will be released
next week.


[1] https://listman.redhat.com/archives/libvir-list/2023-April/239672.html
[2] https://listman.redhat.com/archives/libvir-list/2023-April/239679.html
[3] 
https://gitlab.com/libvirt/libvirt/-/commit/0324adb647885932efc97eefcfe08f6a8db60ae1
-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Bug#1033301: linux: arm64 kernel size increased from 31 to 39 MB, causing u-boot-rpi to fail

2023-04-29 Thread Salvatore Bonaccorso 
Hi Aurelien,

On Sat, Apr 29, 2023 at 09:50:57AM +0200, Aurelien Jarno wrote:
> control: reassign -1 pahole/1.24-4
> control: retitle -1 pahole: BTF deduplication issues causing arm64 kernel 
> size increase
> control: tag -1 + fixed-upstream
> control: tag -1 + patch
> control: affects -1 u-boot-rpi src:linux
> 
> Hi,
> 
> On 2023-03-21 23:11, Aurelien Jarno wrote:
> > Source: linux
> > Version: 6.1.15-1
> > Severity: important
> > Tags: upstream
> > X-Debbugs-Cc: vagr...@debian.org
> > Control: affects -1 + u-boot-rpi
> > 
> > Hi,
> > 
> > Following the upgrade of the kernel from 6.1.12-1 to 6.1.15-1 on a
> > Raspberry Pi 3 Model B Plus, u-boot (from the u-boot-rpi package) failed
> > to boot with:
> > 
> > | 40175552 bytes read in 1695 ms (23 MiB/s)
> > | 43794863 bytes read in 1817 ms (23 MiB/s)
> > | Moving Image from 0x8 to 0x20, end=299
> > | ERROR: RD image overlaps OS image (OS=0x20..0x299)
> > 
> > I tracked the issue to a significant increase of the kernel size between
> > version 6.1.12-1 and 6.15-1:
> > 
> > | 31492   /boot/vmlinuz-6.1.0-5-arm64
> > | 39236   /boot/vmlinuz-6.1.0-6-arm64
> > 
> > This is more than the 36MB that is allowed by u-boot with the default
> > load addresses. A workaround is to shift the load addresses at the
> > u-boot level as in the attached patch.
> > 
> > I have tracked issue on the upstream kernel side to the following commit
> > on the stable tree:
> > 
> > | commit 3e3e4d234d46e48480a7c7c35399fa811182e8ef
> > | Author: Masahiro Yamada 
> > | Date:   Thu Oct 13 08:35:00 2022 +0900
> > | 
> > | arm64: remove special treatment for the link order of head.o
> > | 
> > | commit 994b7ac1697b4581b7726d2ac64321e3c840229b upstream.
> > | 
> > | In the previous discussion (see the Link tag), Ard pointed out that
> > | arm/arm64/kernel/head.o does not need any special treatment - the only
> > | piece that must appear right at the start of the binary image is the
> > | image header which is emitted into .head.text.
> > | 
> > | The linker script does the right thing to do. The build system does
> > | not need to manipulate the link order of head.o.
> > | 
> > | Link: 
> > https://lore.kernel.org/lkml/CAMj1kXH77Ja8bSsq2Qj8Ck9iSZKw=1F8Uy-uAWGVDm4-CG=e...@mail.gmail.com/
> > | Suggested-by: Ard Biesheuvel 
> > | Signed-off-by: Masahiro Yamada 
> > | Reviewed-by: Nicolas Schier 
> > | Link: 
> > https://lore.kernel.org/r/20221012233500.156764-1-masahi...@kernel.org
> > | Signed-off-by: Will Deacon 
> > | Signed-off-by: Tom Saeger 
> > | Signed-off-by: Greg Kroah-Hartman 
> > 
> > The problem is still reproducible on Linus' master.
> > 
> > I am reporting the bug to the linux package as I believed there is no
> > real reason for such an increase in the kernel size. In case I missed
> > something and this is actually wanted, the bug can be reassigned to the
> > u-boot package.
> 
> This has been discussed upstream, and it appears that the issue is not
> reproducible with pahole 1.25. Looking at the part that needs to be
> backported to the Debian package, I have found that the issue is caused
> by the following patch backported in version 1.24-4:
> 
> 02-encode-DW_TAG_unspecified_type-returning-routines-as-void.patch
> 
> This patch has an issue, and memory is not initialized after allocation,
> so garbage values are used instead. A one-liner fix has been committed
> upstream not so long after the initial patch:
> 
> https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?id=b72f5188856df0abf45e1a707856bb4e4e86153c
> 
> I am therefore reassigning the bug to pahole where the bug should be
> fixed. Even if Bookworm is now fully frozen, I personally believe this
> bug should still be fixed before the release. That said, this has to be
> discussed with the release team, and as pahole is a key package you need
> a pre-approval *before* the upload to sid. 

Thanks for tracking this down!

Domenico, I would say, it would eben be good to have this in in the
archive for bookworm before the next (last?) linux upload for bookworm
ideally. This is not yet planned but, the last one should probably be
latest in the week of 15th May.

Regards,
Salvatore

Bug#1035028: unblock: iso-codes/4.15.0-1

2023-04-29 Thread Dr. Tobias Quathamer 

control: tags -1 - moreinfo

Am 28.04.23 um 21:30 schrieb Sebastian Ramacher:

Please provide the debdiff with the translation updates stripped.


I've attached the output of this command:

$ debdiff iso-codes_4.13.0-1.dsc iso-codes_4.15.0-1.dsc | filterdiff -x 
"*.po"


Regards,
Tobias
diff -Nru iso-codes-4.13.0/CHANGELOG.md iso-codes-4.15.0/CHANGELOG.md
--- iso-codes-4.13.0/CHANGELOG.md	2023-02-28 11:14:27.0 +0100
+++ iso-codes-4.15.0/CHANGELOG.md	2023-04-27 23:19:57.0 +0200
@@ -7,6 +7,33 @@
 and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.15.0] – 2023-04-27
+
+### Changed
+
+- Translation updates for ISO 3166-1
+- Translation updates for ISO 3166-3
+- Translation updates for ISO 639-2
+
+
+## [4.14.0] – 2023-04-27
+
+### Changed
+
+- Translation updates for ISO 3166-1
+- Translation updates for ISO 3166-2
+- Translation updates for ISO 3166-3
+- Translation updates for ISO 639-2
+- Translation updates for ISO 639-3
+- Translation updates for ISO 639-5
+- Translation updates for ISO 4217
+- Translation updates for ISO 15924
+
+### Fixed
+
+* ISO 3166-2: Fix wrong Spanish translation
+
+
 ## [4.13.0] – 2023-02-28
 
 ### Added
@@ -278,7 +305,10 @@
   two and a half years. Please use the JSON data files instead.
 
 
-[UNRELEASED]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.12.0...main
+[UNRELEASED]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.15.0...main
+[4.15.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.14.0...v4.15.0
+[4.14.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.13.0...v4.14.0
+[4.13.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.12.0...v4.13.0
 [4.12.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.11.0...v4.12.0
 [4.11.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.10.0...v4.11.0
 [4.10.0]: https://salsa.debian.org/iso-codes-team/iso-codes/compare/v4.9.0...v4.10.0
diff -Nru iso-codes-4.13.0/configure iso-codes-4.15.0/configure
--- iso-codes-4.13.0/configure	2023-02-28 11:14:43.0 +0100
+++ iso-codes-4.15.0/configure	2023-04-27 23:22:08.0 +0200
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for iso-codes 4.13.0.
+# Generated by GNU Autoconf 2.71 for iso-codes 4.15.0.
 #
 #
 # Copyright (C) 1992-1996, 1998-2017, 2020-2021 Free Software Foundation,
@@ -607,8 +607,8 @@
 # Identity of this package.
 PACKAGE_NAME='iso-codes'
 PACKAGE_TARNAME='iso-codes'
-PACKAGE_VERSION='4.13.0'
-PACKAGE_STRING='iso-codes 4.13.0'
+PACKAGE_VERSION='4.15.0'
+PACKAGE_STRING='iso-codes 4.15.0'
 PACKAGE_BUGREPORT=''
 PACKAGE_URL=''
 
@@ -1251,7 +1251,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures iso-codes 4.13.0 to adapt to many kinds of systems.
+\`configure' configures iso-codes 4.15.0 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1318,7 +1318,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of iso-codes 4.13.0:";;
+ short | recursive ) echo "Configuration of iso-codes 4.15.0:";;
esac
   cat <<\_ACEOF
 
@@ -1396,7 +1396,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-iso-codes configure 4.13.0
+iso-codes configure 4.15.0
 generated by GNU Autoconf 2.71
 
 Copyright (C) 2021 Free Software Foundation, Inc.
@@ -1433,7 +1433,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by iso-codes $as_me 4.13.0, which was
+It was created by iso-codes $as_me 4.15.0, which was
 generated by GNU Autoconf 2.71.  Invocation command line was
 
   $ $0$ac_configure_args_raw
@@ -2386,7 +2386,7 @@
 
 # Define the identity of the package.
  PACKAGE='iso-codes'
- VERSION='4.13.0'
+ VERSION='4.15.0'
 
 
 printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -3318,7 +3318,7 @@
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by iso-codes $as_me 4.13.0, which was
+This file was extended by iso-codes $as_me 4.15.0, which was
 generated by GNU Autoconf 2.71.  Invocation command line was
 
   CONFIG_FILES= $CONFIG_FILES
@@ -3373,7 +3373,7 @@
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config='$ac_cs_config_escaped'
 ac_cs_version="\\
-iso-codes config.status 4.13.0
+iso-codes config.status 4.15.0
 configured by $0, generated by GNU Autoconf 2.71,
   with options \\"\$ac_cs_config\\"
 
diff -Nru iso-codes-4.13.0/configure.ac iso-codes-4.15.0/configure.ac
--- iso-codes-4.13.0/configure.ac	2023-02-28 11:14:36.0 +0100
+++ iso-codes-4.15.0/configure.ac	2023-04-27

Bug#854497: ext4magic: SIGSEGV while recovery from encrypted USB stick

2023-04-29 Thread Joachim Reichel 

Hi Markus,

I also experienced this crash. I can confirm that your patch solved the problem, 
thanks!


Best regards,
  Joachim

  1   2   >