date:20250301

Bug#1099309: ITP: jfree-demos -- Various demo programs for JFree projects

2025-03-01 Thread Christian Bayle

Package: wnpp
Severity: wishlist
Owner: Christian Bayle 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: jfree-demos
  Version : 2.0
  Upstream Contact: David Gilbert 
* URL : https://github.com/jfree/jfree-demos
* License : BSD-3-Clause
  Programming Lang: Java
  Description : Various demo programs for JFree projects


Various demo programs for JFree projects, including:

JFreeChart
JFreeSVG
JFree PDF
Orson Charts

Bug#1099308: dpkg-dev: Use of uninitialized value $v{"DEB_HOST_MULTIARCH"} in concatenation (.) or string at /usr/bin/dpkg-architecture line 354.

2025-03-01 Thread Santiago Vila


Package: dpkg-dev
Version: 1.22.15

Hello Guillem et al.

I was going to ask ftpmaster to remove the "hello-traditional" package,
but decided to still make a "last release" so that it's archived in 
snapshot.d.o.

To my surprise the package failed to build on hurd-i386:

[...]
Use of uninitialized value $v{"DEB_HOST_MULTIARCH"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_ABI"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_BITS"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_CPU"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_ENDIAN"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_LIBC"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_ARCH_OS"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_GNU_CPU"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_GNU_SYSTEM"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_GNU_TYPE"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
Use of uninitialized value $v{"DEB_TARGET_MULTIARCH"} in concatenation (.) or 
string at /usr/bin/dpkg-architecture line 354.
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture hurd-i386
invalid host_arch hurd-i386 at /usr/bin/dpkg-checkbuilddeps line 122.
dpkg-buildpackage: error: build dependencies/conflicts unsatisfied; aborting

Is this a bug in dpkg-dev?

( The package now has autotools-dev as its only build-dependency,
  which is clearly strange but not technically a bug )

Thanks.

Bug#1099312: RM: faceup -- ROM; obsolete, now included in Emacs core

2025-03-01 Thread Sean Whitton

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: fac...@packages.debian.org
Control: affects -1 + src:faceup

Hello,

Please drop this source package, we don't need it anymore now that Emacs 30.1
is in sid.  Rdeps have been updated.  Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#932553: reopening

2025-03-01 Thread Sean Whitton

control: reopen -1
control: tag -1 + pending

Hello,

tag2upload does indeed need to pass -k to dgit, and now does.


.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1098707: gnome-core: Switch from evince to papers

2025-03-01 Thread Frederic Peters


Hi,

Jeremy Bícha wrote:

I propose that we switch gnome-core to depend on papers instead of
evince for Debian Trixie.


I installed papers yesterday and in my case I was not impressed as it 
feels much slower than evince, both at startup and in operation, with 
a sensible lag when opening the headerbar menu.


Maybe it's related to me still using X, not Wayland. (?)

Also, I inadvertently ran papers *.pdf in a directory with a bunch of  
files (but not that much, 28 files, for a total of 13M), and the ouf 
of memory killer had to intervene.


I did not investigate further as I had no time for it and it was just 
simpler to switch back to evince. Looking at it now, with the same 
simple PDF, Papers consume ~4 times the memory Evince consume.


Hopefully it works better for others and performance/memory issues 
will be addressed but maybe the switch could be delayed to the next 
release?



Fred

Bug#1099126: sbuild: The repository 'http://deb.debian.org/debian UNRELEASED Release' does not have a Release file.

2025-03-01 Thread Picca Frédéric-Emmanuel

Package: sbuild
Version: 0.88.4
Severity: important

Dear Maintainer,

I am preparing a package which is in UNRELEASE

then I get this error message

autopkgtest
---

autopkgtest [17:20:31]: starting date and time: 2025-02-28 17:20:31+0100
autopkgtest [17:20:31]: version 5.46
autopkgtest [17:20:31]: host page; command line: /usr/bin/autopkgtest 
/home/picca/debian/science-team/pyfai_2025.01-1.dsc 
/home/picca/debian/science-team/pyfai_2025.01-1_amd64.changes -- unshare 
--release UNRELEASED --arch amd64
: failure: ['mmdebstrap', '--variant=apt', 
'--skip=output/mknod,cleanup/apt/lists', '--customize-hook=sed "s/^deb /deb-src 
/" "$1/etc/apt/sources.list" > "$1/etc/apt/sources.list.d/src.list" && 
APT_CONFIG=$MMDEBSTRAP_APT_CONFIG apt-get update', '--arch=amd64', 
'UNRELEASED', '/tmp/tmpmmh21k3n/chroot.tar'] failed (exit status 25, stderr "I: 
automatically chosen mode: unshare\nI: chroot architecture amd64 is equal to 
the host's architecture\nI: automatically chosen format: tar\nI: using 
/tmp/mmdebstrap.GM3OTA6QeQ as tempdir\nI: skipping output/mknod as requested 
for ./dev/console\nI: skipping output/mknod as requested for ./dev/full\nI: 
skipping output/mknod as requested for ./dev/null\nI: skipping output/mknod as 
requested for ./dev/ptmx\nI: skipping output/mknod as requested for 
./dev/random\nI: skipping output/mknod as requested for ./dev/tty\nI: skipping 
output/mknod as requested for ./dev/urandom\nI: skipping output/mknod as 
requested for ./dev/zero\nI: running apt-get update...\nIgn:1 
http://deb.debian.org/debian UNRELEASED InRelease\nErr:2 
http://deb.debian.org/debian UNRELEASED Release\n  404  Not Found [IP: 
2a04:4e42:6a::644 80]\nReading package lists...\nE: The repository 
'http://deb.debian.org/debian UNRELEASED Release' does not have a Release 
file.\nE: apt-get update --error-on=any -oAPT::Status-Fd=<$fd> 
-oDpkg::Use-Pty=false failed\nW: hooklistener errored out: E: received eof on 
socket\n\nI: main() received signal PIPE: waiting for setup...\nI: removing 
tempdir /tmp/mmdebstrap.GM3OTA6QeQ...\nE: mmdebstrap failed to run\n")
autopkgtest [17:20:32]: ERROR: testbed failure: unexpected eof from the testbed
Exception ignored in: <_io.TextIOWrapper name=6 encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe

E: Autopkgtest run failed.

So it seems that the unshare backend does not support the UNRELEASE release :)

Cheers

Frederic


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

Kernel: Linux 6.12.16-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 sbuild depends on:
ii  adduser 3.142
ii  libsbuild-perl  0.88.4
ii  perl5.40.1-2

Versions of packages sbuild recommends:
ii  autopkgtest  5.46
ii  debootstrap  1.0.140
ii  iproute2 6.13.0-1
ii  mmdebstrap   1.5.6-3
ii  schroot  1.6.13-6
ii  uidmap   1:4.17.3-1

Versions of packages sbuild suggests:
ii  e2fsprogs  1.47.2-1
ii  kmod   34-2
ii  wget   1.24.5-2+b1

-- no debconf information

Bug#1025781: getdns: new upstream version 1.7.2

2025-03-01 Thread Thomas Uhle


Control: retitle -1 getdns: new upstream version 1.7.3

Dear maintainers,

the bugfix release 1.7.3 is now more than two years old.  Do you think 
that there is a chance to get this version into trixie before the freeze?


Unfortunately, libgetdns' soname has changed to 12, so I guess the 
library's binary package needs to be renamed to libgetdns12 which means 
getdns has to pass the NEW queue again.


Best regards,

Thomas Uhle

Bug#1099192: 3.51.0 breaks ibus-anthy

2025-03-01 Thread Raul Tambre

Source: python3-gi
Version: 3.51.0-1
Severity: normal

Dear maintainer,

Upgrading to 3.51.0-1 breaks my Japanese IME that I use through ibus-anthy.
Downgrading python3-gi and python3-gi-cairo to 3.50.0-4+b1 reliably fixes this.

With the problematic version the IME stays selectable but the input remains 
English-only.
The following errors are logged in the system journal while trying to type in 
the Gnome text editor for example:

  Mar 01 15:22:29 viljandi gnome-shell[2594]: Gio.IOErrorEnum: Timeout was 
reached
  
  Stack trace:

_promisify/proto[asyncFunc]/
  Mar 01 15:01:33 viljandi sh[12405]: import factory
  Mar 01 15:01:33 viljandi sh[12405]:   File 
"/usr/share/ibus-anthy/engine/factory.py", line 33, in 
  Mar 01 15:01:33 viljandi sh[12405]: import engine
  Mar 01 15:01:33 viljandi sh[12405]:   File 
"/usr/share/ibus-anthy/engine/engine.py", line 42, in 
  Mar 01 15:01:33 viljandi sh[12405]: gi_require_version('Anthy', '9000')
  Mar 01 15:01:33 viljandi sh[12405]: ~~^
  Mar 01 15:01:33 viljandi sh[12405]:   File 
"/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in require_version
  Mar 01 15:01:33 viljandi sh[12405]: raise ValueError('Namespace %s not 
available' % namespace)
  Mar 01 15:01:33 viljandi sh[12405]: ValueError: Namespace Anthy not available

It seems to have been logged by the org.freedesktop.IBus.session.GNOME.service 
user service.
I've not been able to reproduce this particular error anymore.
After downgrading and upgrading python3-gi the IME now stays and only results 
in the first error snippet.

Is this breakage intentional in the new version?
Should I barking up the anthy or ibus-anthy tree?

All the best
Raul

Bug#1099178: dupload: Fail to check signature

2025-03-01 Thread Guillem Jover


Hi!

On Sat, 2025-03-01 at 11:36:09 +0100, Christian Marillat wrote:

Package: dupload
Version: 2.13.0
Severity: serious



Since 2.13.0 dupload doesn't work.

Downgrading to 2.12.0 solve this issue.

,
| $ debrelease -S
| dupload: warning: mail options disabled, cannot run '/usr/sbin/sendmail': No 
such file or directory
| dupload note: no announcement will be sent.
| Checking OpenPGP signatures on ../displaycal-py3_3.9.14-3_source.changes...
| gpgv: Signature made Sat Mar  1 11:27:32 2025 CET
| gpgv:using RSA key A401FF99368FA1F98152DE755C808C2B65558117
| gpgv: Can't check signature: No public key
| openpgp-check: error: cannot verify OpenPGP signature for 
../displaycal-py3_3.9.14-3_source.changes: no acceptable signature found
|
| dupload: error: Pre-upload '/usr/share/dupload/openpgp-check %1' failed for 
../displaycal-py3_3.9.14-3_source.changes
`


I assume this is fallout from the new OpenPGP multi-backend support, 
which requires passing explicit keyrings for hosts that have an 
openpgp-check hook enabled. This is the case for pre-configured hosts 
in the shipped conffile, but I'm assuming you might be using a custom 
host entry?


I improved yesterday the error reporting to make this error condition 
more clear and how to fix it. And I'm thinking about adding a NEWS 
entry, because I guess the implications of the changes are not obvious 
at all.


Thanks,
Guillem

Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-01 Thread /dev/fra

Package: elpa-doom-themes
Version: 2.3.0-2
Severity: important
X-Debbugs-Cc: dev...@inventati.org

Dear Maintainer,

After the upgrade to Emacs 30 in Testing, Doom themes fail to render 
everything properly and the following message is displayed:

> Invalid face box: :line-width, 1, :style, none

The problem is known and reported here:
https://github.com/doomemacs/themes/issues/809.

And fixed upstream with this commit:
https://github.com/doomemacs/themes/pull/811

Would it be possible to cherry-pick this commit and apply it to the
elpa-doom-themes package in Sid/Testing?

Cheers

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

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

Versions of packages elpa-doom-themes depends on:
ii  dh-elpa-helper  2.1.5
ii  emacsen-common  3.0.5

Versions of packages elpa-doom-themes recommends:
ii  emacs   1:30.1+1-3
ii  emacs-pgtk [emacs]  1:30.1+1-3

elpa-doom-themes suggests no packages.

-- no debconf information

Bug#1099196: alsatplg.1: Some remarks and a patch with editorial changes for this man page

2025-03-01 Thread Bjarni Ingi Gislason

Package: alsa-utils
Version: 1.2.13-1
Severity: minor
Tags: patch

   * What led up to the situation?

 Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man 
page"

  [Use "groff -e ' $' -e '\\~$' " to find obvious trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?


an.tmac::30: style: .TH missing fourth argument; consider 
package/project name and version (e.g., "groff 1.23.0")
an.tmac::108: style: 1 leading space(s) on input line
troff::108: warning: trailing space in the line
troff::112: warning: trailing space in the line


   * What outcome did you expect instead?

 No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.


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

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

Versions of packages alsa-utils depends on:
ii  kmod  33+20240816-2
ii  libasound2t64 1.2.13-1+b1
ii  libatopology2t64  1.2.13-1+b1
ii  libc6 2.40-7
ii  libfftw3-single3  3.3.10-2+b1
ii  libncursesw6  6.5+20250216-1
ii  libsamplerate00.2.2-4+b2
ii  libtinfo6 6.5+20250216-1

alsa-utils recommends no packages.

Versions of packages alsa-utils suggests:
pn  dialog  

-- no debconf information
Input file is alsatplg.1

Output from "mandoc -T lint  alsatplg.1": (shortened list)

  1 input text line longer than 80 bytes: Topology Interface: ...
  5 skipping paragraph macro: sp after SH
  2 whitespace at end of input line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Output from "test-groff -mandoc -t -ww -z alsatplg.1": (shortened list)

  2 trailing space in the line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Show if generated from reStructuredText

Who is actually generating this man page?  Debian or upstream?

Is the generating software out of date?

1:.\" Man page generated from reStructuredText.

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

Number of lines affected is

2

-.-.

Remove space in the first column, if not indented.
Use ".in +n" and ".in" to end it; ".nf" and ".fi" to end
it, for an extra indention.

alsatplg.1:108: 
 

-.-.

Strings longer than 3/4 of a standard line length (80)
Use "\:" to split the string at the end of an output line, for example a
long URL (web address)

108  
 
112 Topology Interface:  
 

-.-.

Wrong distance between sentences in the input file.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

Mark a final abbreviation point as such by suffixing it with "\&".

Some sentences (etc.) do not begin on a new line.

Split (sometimes) lines after a punctuation mark; before a conjunction.

N.B.

  The number of lines affected can be too large to be in a patch.

  Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.

Use

#!/usr/bin/sh

sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\.  */\1.\n/g' $1

to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"


44:a driver to work on a different devices. The driver is also
53:from the file system. Firmware updates can be pushed without
54:having to update the drivers. The new firmware just needs

-.-.

Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".

alsatplg.1:38:alsatplg (ALSA Topology compiler) is a program to compile topology
alsatplg.1:88:sort the configuration iden

Bug#1098698: linux: Segfault and system hang on larger network file transfers

2025-03-01 Thread Salvatore Bonaccorso

Hi Paul,

On Sat, Mar 01, 2025 at 08:21:58AM -0500, Paul DeKraker wrote:
> Here is a log collected via netconsole.
> 
> Thanks,
> Paul
> 
> On Thu, Feb 27, 2025 at 11:39 AM Salvatore Bonaccorso 
> wrote:
> 
> > Hi Paul,
> >
> > On Mon, Feb 24, 2025 at 09:12:43PM -0500, Paul DeKraker wrote:
> > > I just tried 6.12.16 and as with 6.12.15 the system locks up / becomes
> > > completely unresponsive and needs to be hard reset when attempting a
> > large
> > > transfer from a network share to the local computer, so this probably is
> > a
> > > separate issue. If there is something more I can do to capture this
> > > behavior please let me know.
> >
> > Thanks for confirming. Yes now we have to get to fresh logs. As I
> > understand you cannot access the system (not even remotely via SSH) to
> > gather the kernel logs after the issue appears?
> >
> > In this case we might be successfull if you attach a netconsole and
> > have another system available which can capture the logs.
> > Documentation can be found here:
> >
> > https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole
> >
> > Would you be able to try that and provide fresh logs for the recent
> > 6.12.y kernels?

Thanks a lot for the log, this was very helpful. At first glance it
looks like this issue:
https://lore.kernel.org/netfs/cakpou+_4muwygqtrtbxcmi+-k3pgvlysnpadkmhoyb7gz0i...@mail.gmail.com/

There is a submitted patch but it does not look like it got applied
already, checking.

Might you be able to test the patch from
https://lore.kernel.org/netfs/20250210191118.316-1-max.kellerm...@ionos.com/
to see if it fixes the issue?

You can follow the procedure in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
to do the "simple patching and building".

Regards,
Salvatore

Bug#1073483: Intent to NMU apt-src to fix its trivial FTBFS bug

2025-03-01 Thread Helge Kreutzmann

Hello László,
Am Sat, Mar 01, 2025 at 03:00:50PM +0100 schrieb László Böszörményi (GCS):
> On Sat, Mar 1, 2025 at 1:05 PM Helge Kreutzmann  wrote:
> > If there are any questions, please let me know.
>  Seems the French man page was generated incorrectly. It ends with:
> .SH "POD ERRORS"
> .IX Header "POD ERRORS"
> Hey! \fBThe above document had some coding errors, which are explained 
> below:\fR
> .IP "Around line 234:" 4
> .IX Item "Around line 234:"
> Unterminated L<...> sequence
> 
> I've fixed it and you can check my iteration [1] if it meets your approval.

Sorry that I missed that one.

Actually, now there is a closing parenthesis missing, but don't worry,
I insert it in my copy which I use to ask for updated translations.
I'm going to prepare that now, so please upload.

Btw., I did not update to the latest version of policy.

Looking forward to the upload.

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#1099023: Unnecessary dependence of gdm3 on xwayland

2025-03-01 Thread Stephan Verbücheln

> Having apps that are not native Wayland silently fail to run for
> those people feels bad to me.

Of course this should be automatically installed for applications which
require it. But that should be a dependency of the respective
application, directly or indirectly, for instance as a dependency of
GTK2.

Regards


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

Bug#1099199: RFS: wtmpdb/0.71.0+git20250228.4e4b54e-1 [ITA] -- utility to display login/logout/reboot information

2025-03-01 Thread Andrew Bower

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : wtmpdb
   Version  : 0.71.0+git20250228.4e4b54e-1
   Upstream contact : Thorsten Kukuk
 * URL  : https://github.com/thkukuk/wtmpdb/
 * License  : BSD-2-Clause
 * Vcs  : https://salsa.debian.org/debian/wtmpdb
   Section  : admin

The source builds the following binary packages:

  libwtmpdb0 - wtmp database shared library
  libwtmpdb-dev - libwtmpdb development files
  libpam-wtmpdb - wtmp database PAM module
  wtmpdb - utility to display login/logout/reboot information

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/w/wtmpdb/wtmpdb_0.71.0+git20250228.4e4b54e-1.dsc

Changes since the last upload:

 wtmpdb (0.71.0+git20250228.4e4b54e-1) experimental; urgency=medium
 .
   * New maintainer (Closes: #1092022)
   * New upstream version (Closes: #1099168)
 - drop all patches; they are included upstream
 - exclude new 'wtmpdbd' daemon from packaging
 - include unreleased 'wtmpdb import' command (Closes: #1086559)
   * Patch integer format string errors affecting ILP32 archs
   * Patch out noisy logging when systemd not running
   * d/control
 - add myself as maintainer
 - already conforming with policy v4.7.2
 - non-essential libaudit dependency not available for Hurd
   * d/wtmpdb.cron.monthly
 - appease SC2166
 - squelch non-error output
   * d/copyright: reflect additional and updated content
   * d/lrc.config: do not check excluded wtmpdbd and varlink content
   * add d/upstream/metadata
   * dh_installinit: no-stop-on-upgrade

Regards,
-- 
  Andrew Bower


signature.asc
Description: PGP signature

Bug#1099200: RFS: pdsh/2.35-0.1 [NMU] -- Efficient rsh-like utility, for using hosts in parallel

2025-03-01 Thread Arif Ali

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : pdsh
   Version  : 2.35-0.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : [fill in URL of upstream's web site]
 * License  : [fill in]
 * Vcs  : [fill in URL of packaging vcs]
   Section  : net

The source builds the following binary packages:

  pdsh - Efficient rsh-like utility, for using hosts in parallel

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/p/pdsh/pdsh_2.35-0.1.dsc

Changes since the last upload:

 pdsh (2.35-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream Release (Closes #1094108)

Regards,

Bug#1099202: amixer.1: Some remarks and a patch with editorial changes for this man page

2025-03-01 Thread Bjarni Ingi Gislason

Package: alsa-utils
Version: 1.2.13-1
Severity: minor
Tags: patch

   * What led up to the situation?

 Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man 
page"

  [Use "groff -e ' $' -e '\\~$' " to find obvious trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?


an.tmac::1: style: .TH missing fourth argument; consider package/project 
name and version (e.g., "groff 1.23.0")
troff::124: warning: trailing space in the line
troff::133: warning: trailing space in the line
troff::138: warning: trailing space in the line


   * What outcome did you expect instead?

 No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.


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

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

Versions of packages alsa-utils depends on:
ii  kmod  33+20240816-2
ii  libasound2t64 1.2.13-1+b1
ii  libatopology2t64  1.2.13-1+b1
ii  libc6 2.40-7
ii  libfftw3-single3  3.3.10-2+b1
ii  libncursesw6  6.5+20250216-1
ii  libsamplerate00.2.2-4+b2
ii  libtinfo6 6.5+20250216-1

alsa-utils recommends no packages.

Versions of packages alsa-utils suggests:
pn  dialog  

-- no debconf information
Input file is amixer.1

Output from "mandoc -T lint  amixer.1": (shortened list)

  1 input text line longer than 80 bytes: This document is by ...
  4 whitespace at end of input line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Output from "test-groff -mandoc -t -ww -z amixer.1": (shortened list)

  4 trailing space in the line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

Number of lines affected is

4

-.-.

Wrong distance between sentences in the input file.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

Mark a final abbreviation point as such by suffixing it with "\&".

Some sentences (etc.) do not begin on a new line.

Split (sometimes) lines after a punctuation mark; before a conjunction.

  Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.

Use

#!/usr/bin/sh

sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\.  */\1.\n/g' $1

to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"

12:for the default soundcard and device. This is a good way to see a list
35:Sets the simple mixer control contents. The parameter can be the volume
54:A simple mixer control must be specified. Only one device can be controlled
61:A simple mixer control must be specified. Only one device can be controlled
74:Sets the card control contents. The identifier has these components: iface,
75:name, index, device, subdevice, numid. The next argument specifies the value
80:Shows the card control contents. The identifier has same syntax as for
98:Select the card number to control. The device name created from this
104:Select the device name to control. The default control name is 'default'.
112:Only sset and cset are accepted.  Other commands are ignored.
121:Quiet mode. Do not show results of changes.
143:will set the master volume of the second card to \-20dB.  If the master
148:will increase the PCM volume of the second card with 2dB.  When both

-.-.

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\" in the source.  

Line 169, length 91

This document is by Paul Winkler  and Jaroslav Kysela 
.

-.-.

The name of a man page is typeset in bold and the section in roman
(see man-pages(7)

Bug#1092101: retitle 1092101 to osmo-cbc -- Osmocom Cell Broadcast Centre

2025-03-01 Thread Guido Günther

retitle -1 ITP: osmo-cbc -- Osmocom Cell Broadcast Centre

Hi,
On Sat, Mar 01, 2025 at 11:16:22AM +0100, Jakub Wilk wrote:
> * Guido Günther , 2025-02-26 17:42:
> > retitle 1092101 osmo-cbc -- Osmocom Cell Broadcast Centre
> 
> AFAICS this just removed the "RFP: " prefix from the bug title, which
> doesn't make sense to me. Did you mean to do something else?

That is true. I wonder where the ITP went, thanks for bringing this up.
Cheers,
 -- Guido

> 
> -- 
> Jakub Wilk
>

Bug#1099111: dupload: Recent changes broke buildd-uploader

2025-03-01 Thread John Paul Adrian Glaubitz

Hello,

On Sat, 2025-03-01 at 14:58 +0100, Guillem Jover wrote:
> > I have not investigated the problem in detail yet. However, downgrading 
> > dupload
> > to 2.11.2 fixes the problem for me.
> 
> I'd assume this is due to the new OpenPGP multi-backend support, which 
> makes the openpgp-hook require explicit keyrings options.

OK.

> I suppose buildd might be failing like this if dupload exited with a 
> failure? (Which I think deserves its own bug report, to handle that 
> more gracefully.)
> 
> Before the upload I coordinated with Aurelien Jarno to make sure this 
> time around the buildds had the required config changes:
> 
>
> https://salsa.debian.org/dsa-team/mirror/dsa-puppet/-/commit/44cb84d9f0a85d29c82e63f2e8ad1eb9b92530cc
> 
> But, I guess the instance you are reporting for might be independent 
> from DSA?

The DSA-maintained instances are only building the packages for the release
architectures. Debian Ports packages are built on separate machines and
therefore such configuration changes would have to be applied there as well:

https://salsa.debian.org/debian-ports-team/dsa-puppet

> The default debian hosts configured in the shipped conffile contain 
> the required changes so if you are using a custom one, then that might 
> need to be adapted? Otherwise it would be nice to know what's going 
> wrong.

Not sure what you mean with "default Debian hosts"?

> I improved the error reporting on git, and will be adding a NEWS entry 
> because this fallout I guess was unexpected.

Yes, breaking changes should be communicated in the NEWS file and I suggest
that the required configuration changes are added to the default configuration
files of the src:sbuild package which also contains the buildd binary package.

Adrian

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

Bug#1099193: Please add a USB driver for HP OfficeJet Pro 8132e

2025-03-01 Thread Till Kamppeter


CUPS is totally OK, the errors come from HPLIP.

Debian folks should really update to the current version of HPLIP, 3.24.4. It 
should be easy, just porting over the Ubuntu package.


And modern HP printers do not need HPLIP, they are driverless, for both printing 
and scanning.

Bug#1099253: nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not found

2025-03-01 Thread Andreas Beckmann

Please clean up all the 'pahole: not found' bugs, that's #1098706 in 
src:linux and an upload for that is on the way to sid.


Thanks.

Andreas

Bug#1099245: libzypp: FTBFS: The following tests FAILED: 69 - YUMDownloader_test (Failed)

2025-03-01 Thread Santiago Vila

Package: src:libzypp
Version: 17.36.2-1
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DDOC_INSTALL_DIR=/usr/share/doc \
-DLIB=lib/x86_64-linux-gnu \
-DINCLUDE=include/x86_64-linux-gnu \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_SKIP_RPATH=FALSE \

[... snipped ...]


58: Test command: 
/<>/obj-x86_64-linux-gnu/tests/parser/RepoindexFileReader_test 
"--catch_system_errors=no"
58: Working Directory: /<>/obj-x86_64-linux-gnu/tests/parser
58: Test timeout computed to be: 1500
58: Running 1 test case...
58: 
58: [1;32;49m*** No errors detected
58: [0;39;49m
57/89 Test #58: RepoindexFileReader_test .   Passed0.03 sec
test 59
  Start 59: HistoryLogReader_test

59: Test command: 
/<>/obj-x86_64-linux-gnu/tests/parser/HistoryLogReader_test 
"--catch_system_errors=no"
59: Working Directory: /<>/obj-x86_64-linux-gnu/tests/parser
59: Test timeout computed to be: 1500
59: Running 1 test case...
59: 
59: [1;32;49m*** No errors detected
59: [0;39;49m
58/89 Test #59: HistoryLogReader_test    Passed0.03 sec
test 60
  Start 60: RepomdFileReader_test

60: Test command: 
/<>/obj-x86_64-linux-gnu/tests/parser/yum/RepomdFileReader_test 
"--catch_system_errors=no"
60: Working Directory: /<>/obj-x86_64-linux-gnu/tests/parser/yum
60: Test timeout computed to be: 1500
60: Running 1 test case...
60: /<>/tests/parser/yum/data/repomd-1.xml
60: 
60: [1;32;49m*** No errors detected
60: [0;39;49m
59/89 Test #60: RepomdFileReader_test    Passed0.01 sec
test 61
  Start 61: inidict_test

61: Test command: 
/<>/obj-x86_64-linux-gnu/tests/parser/inifile/inidict_test 
"--catch_system_errors=no"
61: Working Directory: 
/<>/obj-x86_64-linux-gnu/tests/parser/inifile
61: Test timeout computed to be: 1500
61: Running 2 test cases...
61: 
61: [1;32;49m*** No errors detected
61: [0;39;49m
60/89 Test #61: inidict_test .   Passed0.01 sec
test 62
  Start 62: iniparser_test

62: Test command: 
/<>/obj-x86_64-linux-gnu/tests/parser/inifile/iniparser_test 
"--catch_system_errors=no"
62: Working Directory: 
/<>/obj-x86_64-linux-gnu/tests/parser/inifile
62: Test timeout computed to be: 1500
62: Running 2 test cases...
62: 
62: [1;32;49m*** No errors detected
62: [0;39;49m
61/89 Test #62: iniparser_test ...   Passed0.01 sec
test 63
  Start 63: DUdata_test

63: Test command: /<>/obj-x86_64-linux-gnu/tests/repo/DUdata_test 
"--catch_system_errors=no"
63: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
63: Test timeout computed to be: 1500
63: Running 1 test case...
63: 
63: [1;32;49m*** No errors detected
63: [0;39;49m
62/89 Test #63: DUdata_test ..   Passed0.07 sec
test 64
  Start 64: ExtendedMetadata_test

64: Test command: 
/<>/obj-x86_64-linux-gnu/tests/repo/ExtendedMetadata_test 
"--catch_system_errors=no"
64: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
64: Test timeout computed to be: 1500
64: Running 1 test case...
64: 
64: [1;32;49m*** No errors detected
64: [0;39;49m
63/89 Test #64: ExtendedMetadata_test    Passed0.06 sec
test 65
  Start 65: PluginServices_test

65: Test command: 
/<>/obj-x86_64-linux-gnu/tests/repo/PluginServices_test 
"--catch_system_errors=no"
65: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
65: Test timeout computed to be: 1500
65: Running 1 test case...
65: 
65: [1;32;49m*** No errors detected
65: [0;39;49m
64/89 Test #65: PluginServices_test ..   Passed0.03 sec
test 66
  Start 66: RepoLicense_test

66: Test command: 
/<>/obj-x86_64-linux-gnu/tests/repo/RepoLicense_test 
"--catch_system_errors=no"
66: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
66: Test timeout computed to be: 1500
66: Running 1 test case...
66: 
66: [1;32;49m*** No errors detected
66: [0;39;49m
65/89 Test #66: RepoLicense_test .   Passed0.07 sec
test 67
  Start 67: RepoSigcheck_test

67: Test command: 
/<>/obj-x86_64-linux-gnu/tests/repo/RepoSigcheck_test 
"--catch_system_errors=no"
67: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
67: Test timeout computed to be: 1500
67: Running 6 test cases...
67: 
67: [1;32;49m*** No errors detected
67: [0;39;49m
66/89 Test #67: RepoSigcheck_test    Passed0.37 sec
test 68
  Start 68: RepoVariables_test

68: Test command: 
/<>/obj-x86_64-linux-gnu/tests/repo/RepoVariables_test 
"--catch_system_errors=no"
68: Working Directory: /<>/obj-x86_64-linux-gnu/tests/repo
68: Test timeout computed to be: 1500
68: Running 4 test cases..

Bug#1001647: visidata phones home

2025-03-01 Thread Christoph Berg

Re: Anja
> The creator of VisiData goes into great depth here about his decision to
> enable motd by default: https://github.com/saulpw/visidata/issues/913
> 
> The privacy page is here: https://www.visidata.org/privacy/.

This privacy policy is incomplete. You are collecting PII (the IP
address of users of the program, not just the website visitors), but
there is no data protection officer defined, no contact address for
enquiries, etc. As you probably have users in Europe, the GDPR apply,
and this is a violation.

Collecting PII needs a legitimate reason, and the one stated here "we
like to have numbers of users" sounds nice to have, but I really don't
see it outweighing the interest of the user to remain private.

TBH, you are on very slippery ground here and would be far better off
by turning this off for legal reasons.

As already mentioned, there is the Debian popularity contest (which is
opt-in), and it does have visidata numbers:

https://qa.debian.org/popcon.php?package=visidata

This is how this works in Debian. Please you can keep the feature, but
make it opt-in.

There is no written policy for this yet, but every other package I
know with such a feature has turned it off in the packaging.

Thanks.

Christoph

Bug#1009154: pinfo: initializelinks.c:159: finddot: Assertion `closest>=str' failed

2025-03-01 Thread Sven Geuer

On Thu, 7 Apr 2022 20:58:27 +0200 Jakub Wilk  wrote:
> Package: pinfo
> Version: 0.6.13-1.1
> 
> pinfo crashes on the "Fixed date options" node of gcal.info:
> 
>    $ dpkg-query -W gcal
>    gcal   4.1-3.1
> 
>    $ pinfo --node='Fixed date options' gcal
>    pinfo: initializelinks.c:159: finddot: Assertion `closest>=str' failed.
>   
>Aborted

This bug is caused by the fact that pinfo can not deal with references
spanning more then two lines. The "Fixed date options" node of
gcal.info contains references starting at then end of a line, covering
the entire following line and terminating in the line after next. See  
lines 3098-3100 and 3113-3115 of unpacked /usr/share/info/gcal.info.gz.

The way how pinfo handles two-line-references is not extendable to more
lines. A change would require a major rework of how pinfo handles
paragraphs of text, IMHO.

-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585

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

Bug#1099303: transition: xen 4.20

2025-03-01 Thread Maximilian Engelhardt

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: x...@packages.debian.org, h...@knorrie.org, m...@daemonizer.de, 
t...@security.debian.org
Control: affects -1 + src:xen

We would like to update xen to 4.20 for Trixie. This gives us the benefit of 
about 7 month longer upstream security support during the lifetime of Trixie 
(till about March 2028). The Debian xen team does not have the resources to 
provide security support without upstream support, so we usually end security 
support in Debian when upstream support ends.

Xen 4.20.0~rc2+1-gfcde5e0de8-1~exp1 is already in experimental and the 
automatic transition tracker at 
https://release.debian.org/transitions/html/auto-xen.html looks good.

I did a rebuild of all the three reverse-dependencies listed on the transition 
tracker (kexec-tools, qemu, libvirt) with xen 4.20 and found no issues.

Xen 4.20 final release is scheduled for March 5th [1]. We can either upload 
the final version shortly after the release date or already now the latest 
upstream stable-4.20 branch. As upstream is in hard code freeze there are only 
very small changes expected till the final release.

Please let us know the opinion of the release team about this request.

Thanks

[1] 
https://lists.xenproject.org/archives/html/xen-announce/2025-02/msg7.html


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

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

2025-03-01 Thread Jeremy Bícha

On Sat, Mar 1, 2025 at 4:58 PM Hank Knox  wrote:
> Yes, I did and I would be happy to prepare an updated package. There is
> an updated upstream version which I have not yet tried out, but I assume
> it works under GNOME Shell 48 and making a Debian package should be simple.

The newer version (git commits) are months old and the metadata.json
file there doesn't even claim GNOME Shell 47 support. However, you may
be able to update the existing patch to add 48.

> Jeremy, it seems like it would make sense to bring this under the
> umbrella of the GNOME packaging team. I would be happy to be responsible
> for it if someone on the team is willing to mentor me. I would
> appreciate help finding a workflow that fits the GNOME team's workflow.

The Salsa repo is explicitly a fork of the Debian GNOME repo so yes,
it would be easy to move it back to team maintenance.

I still wouldn't feel obligated to update every GNOME Shell extension
myself since I don't use most of them.

The standard team workflow is at https://wiki.debian.org/Gnome/Git but
many of the packaged extensions don't fully follow that. This
extension is a bit more complicated to maintain because upstream
hasn't tagged any releases. I didn't get around to updating the
documentation to describe how to use our workflow with git snapshots.
You can ignore the team workflow for now though.

Thank you,
Jeremy Bícha

Bug#1099319: lvm2: thin_check has moved to /usr/bin

2025-03-01 Thread Doug Freed

Package: lvm2
Version: 2.03.27-1
Severity: normal
X-Debbugs-Cc: dwfr...@mtu.edu

LVM tools expect to find thin_check and friends in /usr/sbin, but since the
rust rewrite of thin-provisioning-tools, they are now found in /usr/bin.  LVM
actions that would call thin_check and friends (like activating a thin-pool)
thus complain about not being able to run them.


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

Kernel: Linux 6.12.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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)

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.201-1
ii  dmsetup   2:1.02.201-1
ii  libaio1t640.3.113-8+b1
ii  libblkid1 2.40.4-5
ii  libc6 2.40-7
ii  libdevmapper-event1.02.1  2:1.02.201-1
ii  libedit2  3.1-20250104-1
ii  libselinux1   3.8-4
ii  libsystemd0   257.3-1
ii  libudev1  257.3-1

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  1.1.0-3+b1

lvm2 suggests no packages.

-- no debconf information

Bug#1099199: RFS: wtmpdb/0.71.0+git20250228.4e4b54e-1 [ITA] -- utility to display login/logout/reboot information

2025-03-01 Thread Maytham Alsudany

Hi Andrew,

The packaging looks good to me. Just one question: do you plan on
including the wtmpdbd daemon later, or are you permanently excluding it
from the packaging?

Thanks!
-- 
Maytham


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

Bug#1098649: mysql-workbench: remove from Debian?

2025-03-01 Thread Dmitry Smirnov

Hi Jeremy,

Thanks for closing this issue. I'm surprised you've noticed new upload
of mysql-workbench so fast!

I was just about to reply to you...

On Saturday, 22 February 2025 6:37:43 PM AEDT Jeremy Bícha wrote:
> mysql-workbench was removed from Testing in 2018. Can we please remove
> it from Debian now?

I prefer to keep it please. It was removed from "testing" only due to
lack of "sensible security support due to Oracle's policies" (#923347),
but it is a useful software without alternatives that yours truly use often.

It is actively maintained upstream and trivially backportable so I believe
it would be better to maintain it, especially because re-introducing such
heavy package with large code base through NEW process is very slow and
difficult, let alone hard on ftp-master's team.

I'm yet to make up my mind between options either to declare the package
as unsupported with security team, or maintain it in "fasttrack" [1].
(Either way it should remain in "unatable".)

[1]: https://fasttrack.debian.net/

> This was asked before in 2021: https://bugs.debian.org/982683

Unfortunately I'm affected by personal circumstances that severely affect
my capacity. I may be slow to respond.

> I noticed this package today as I was checking why the old
> libpoppler140 was not automatically removed from Debian.

But M-W don't depend on "libpoppler", at least not directly...

> mysql-workbench's presence in Unstable is causing cruft libraries to
> not be removed.

That's unfortunate... Sorry for neglecting the package for so long.
(I wish I was not its only maintainer...)

> mysql-workbench is not installable at least because pcre3 was removed
> from Unstable.

That was not the only problem but it is all fixed now, as of yesterday.

Thank you for your concerns.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

If men were basically good, we would not require government; if men were
basically evil, we could not afford to grant any man the power of
government.
 -- Robert LeFevre, "The Fundamental of Liberty" (1988)

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

Bug#1099274: python-infoblox-client: FTBFS: E TypeError: argument of type 'NoneType' is not iterable

2025-03-01 Thread Santiago Vila

Package: src:python-infoblox-client
Version: 0.6.0-3
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --buildsystem=pybuild --with python3
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
dh binary --buildsystem=pybuild --with python3
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build" 
module
I: pybuild base:311: python3.13 -m build --skip-dependency-check --no-isolation 
--wheel --outdir /<>/.pybuild/cpython3_3.13  
* Building wheel...
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:270: UserWarning: 
Unknown distribution option: 'test_suite'
  warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:270: UserWarning: 
Unknown distribution option: 'tests_require'
  warnings.warn(msg)
running bdist_wheel
The [wheel] section is deprecated. Use [bdist_wheel] instead.
/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:124: 
SetuptoolsDeprecationWarning: bdist_wheel.universal is deprecated
!!



With Python 2.7 end-of-life, support for building universal wheels
(i.e., wheels that support both Python 2 and Python 3)
is being obviated.
Please discontinue using this option, or if you still need it,
file an issue with pypa/setuptools describing your use case.

By 2025-Aug-30, you need to update your project and remove deprecated 
calls
or your builds will no longer be supported.



!!
  self.finalize_options()
running build
running build_py
creating build/lib/infoblox_client
copying infoblox_client/feature.py -> build/lib/infoblox_client
copying infoblox_client/exceptions.py -> build/lib/infoblox_client
copying infoblox_client/objects.py -> build/lib/infoblox_client
copying infoblox_client/utils.py -> build/lib/infoblox_client
copying infoblox_client/__init__.py -> build/lib/infoblox_client
copying infoblox_client/object_manager.py -> build/lib/infoblox_client
copying infoblox_client/connector.py -> build/lib/infoblox_client
running egg_info
creating infoblox_client.egg-info
writing infoblox_client.egg-info/PKG-INFO
writing dependency_links to infoblox_client.egg-info/dependency_links.txt
writing requirements to infoblox_client.egg-info/requires.txt
writing top-level names to infoblox_client.egg-info/top_level.txt
writing manifest file 'infoblox_client.egg-info/SOURCES.txt'
reading manifest file 'infoblox_client.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found under 
directory '*'
warning: no previously-included files matching '*.py[co]' found under directory 
'*'
adding license file 'LICENSE'
adding license file 'AUTHORS.rst'
writing manifest file 'infoblox_client.egg-info/SOURCES.txt'
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/infoblox_client
copying build/lib/infoblox_client/feature.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/exceptions.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/objects.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/utils.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/__init__.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/object_manager.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
copying build/lib/infoblox_client/connector.py -> 
build/bdist.linux-x86_64/wheel/./infoblox_client
running install_egg_info
Copying infoblox_client.egg-info to 
build/bdist.linux-x86_64/wheel/./infoblox_client-0.6.0.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/infoblox_client-0.6.0.dist-info/WHEEL
creating 
'/<>/.pybuild/cpython3_3.13/.tmp-u8o6r_9e/infoblox_client-0.6.0-py2.py3-none-any.whl'
 and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'infoblox_client/__init__.py'
adding 'infoblox_client/connector.py'
adding 'infoblox_client/exceptions.py'
adding 'i

Bug#1099272: python-bimmer-connected: FTBFS: E AttributeError: module 'httpx._types' has no attribute 'VerifyTypes'.

2025-03-01 Thread Santiago Vila

Package: src:python-bimmer-connected
Version: 0.16.3-1.1
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --buildsystem=pybuild --with python3
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
dh binary --buildsystem=pybuild --with python3
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild

[... snipped ...]





# Package would be ignored #

Python recognizes 'bimmer_connected.tests.responses.I20' as an 
importable package[^1],
but it is absent from setuptools' `packages` configuration.

This leads to an ambiguous overall configuration. If you want to 
distribute this
package, please make sure that 'bimmer_connected.tests.responses.I20' 
is explicitly added
to the `packages` configuration field.

Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).

You can read more about "package discovery" on setuptools documentation 
page:

- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

If you don't want 'bimmer_connected.tests.responses.I20' to be 
distributed and are
already explicitly excluding 'bimmer_connected.tests.responses.I20' via
`find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or 
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.

You can read more about "package data files" on setuptools 
documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
  even if it does not contain any `.py` files.
  On the other hand, currently there is no concept of package data
  directory, all directories are treated like packages.



!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: 
Package 'bimmer_connected.tests.responses.J29' is absent from the `packages` 
configuration.
!!




# Package would be ignored #

Python recognizes 'bimmer_connected.tests.responses.J29' as an 
importable package[^1],
but it is absent from setuptools' `packages` configuration.

This leads to an ambiguous overall configuration. If you want to 
distribute this
package, please make sure that 'bimmer_connected.tests.responses.J29' 
is explicitly added
to the `packages` configuration field.

Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).

You can read more about "package discovery" on setuptools documentation 
page:

- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

If you don't want 'bimmer_connected.tests.responses.J29' to be 
distributed and are
already explicitly excluding 'bimmer_connected.tests.responses.J29' via
`find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or 
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.

You can read more about "package data files" on setuptools 
documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
  even if it does not contain any `.py` files.
  On the other hand, currently there is no concept of package data
  directory, all directories are treated like packages.

**

Bug#1091790: plasma-workspace-data: Global Theme: All Categories Missing

2025-03-01 Thread Aurélien COUDERC

Le mardi 31 décembre 2024, 14:17:09 UTC+1 vajdao a écrit :
> Package: plasma-workspace-data
> Version: 4:5.27.5-2+deb12u2
> Severity: important
> X-Debbugs-Cc: moaja2...@mozmail.com
> 
> Dear Maintainer,
> 
> I hope I backtraced the source of package well, did this with apt-file search.

Was a temporary problem.
See https://bugs.kde.org/show_bug.cgi?id=495903#c7

So closing.


Happy hacking,
--
Aurélien

Bug#1099294: virt-top: FTBFS: Error: No implementation provided for the following modules: "Dune_site__Dune_site_data" referenced from "Dune_site__Helpers"

2025-03-01 Thread Santiago Vila

Package: src:virt-top
Version: 1.1.1-1
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
dh clean --with ocaml
   dh_ocamlclean
   dh_clean
 debian/rules binary
dh binary --with ocaml
   dh_update_autotools_config
   dh_autoreconf
configure.ac: warning: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION 
or AM_GNU_GETTEXT_REQUIRE_VERSION
configure.ac:30: warning: The macro 'AC_PROG_CC_STDC' is obsolete.
configure.ac:30: You should run autoupdate.
./lib/autoconf/c.m4:1669: AC_PROG_CC_STDC is expanded from...
configure.ac:30: the top level
configure.ac:125: installing './config.guess'
configure.ac:125: installing './config.sub'
   dh_ocamlinit
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether sleep supports fractional seconds... yes
checking filesystem timestamp resolution... 0.01
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking xargs -n works... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking how to run the C preprocessor... gcc -E
checking for gcc option to enable large file support... none needed
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libxml-2.0... yes
checking for ocamlc... ocamlc
OCaml version is 5.3.0
OCaml library path is /usr/lib/x86_64-linux-gnu/ocaml/5.3.0
checking for ocamlopt... ocamlopt
checking for ocamlc.opt... ocamlc.opt
checking for ocamlopt.opt... ocamlopt.opt
checking for ocaml... ocaml
checking for ocamldep... ocamldep
checking for ocamlmktop... ocamlmktop
checking for ocamlmklib... ocamlmklib
checking for ocamldoc... ocamldoc
checking for ocamlbuild... no
checking for ocamlfind... ocamlfind
checking for OCaml findlib package unix... found
checking for OCaml findlib package libvirt... found
checking for OCaml findlib package curses... found
checking for OCaml findlib package calendar... not found
checking for OCaml findlib package gettext... found
checking if OCaml â-runtime-variant _picâ works... yes
checking for perldoc... perldoc
checking for ocaml-gettext... ocaml-gettext
checking for xgettext... xgettext
checking for msgcat... msgcat
checking for msgfmt... msgfmt
checking for msgmerge... msgmerge
checking msgfmt is GNU tool... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking 32-bit host C ABI... no
checking for egrep -e... /usr/bin/grep -E
checking for ELF binary format... yes
checking for the common suffixes of directories in the library search path... 
lib,lib,lib64
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyPreferredLanguages... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
configure: creating src/opt_gettext.ml
-

Bug#1099260: nvidia-graphics-drivers-tesla: FTBFS: /bin/sh: 1: pahole: not found

2025-03-01 Thread Santiago Vila

Package: src:nvidia-graphics-drivers-tesla
Version: 525.147.05-13
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{525.147.05}g;' \
-e 's{#MAJOR#}{525}g;' \
-e 's{#NVIDIA#}{nvidia-tesla}g;' \
-e 's{#VARIANT#}{-tesla}g;' \
-e 's{#CURRENT#}{tesla}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-kernel}g;' \

[... snipped ...]

/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035748rm+0x207: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035787rm+0x6f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035927rm+0x49: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036413rm+0xc: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035955rm+0x5c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv035962rm+0x9: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036407rm+0x4: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036203rm+0x4: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035969rm+0x5f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036464rm+0x12: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036273rm+0x1f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036250rm+0x33: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036481rm+0xde: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036232rm+0x3e7: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036450rm+0x6b0: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036502rm+0xa91: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011292rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011295rm+0x28: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036372rm+0x20: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036374rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036383rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011289rm+0x56: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011184rm+0x18a: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036381rm+0x30: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011286rm+0x59: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011265rm+0x15: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036376rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011271rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036385rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011268rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035915rm+0xac: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035939rm+0xbb: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036419rm+0xcc9: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011372rm+0x18d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011374rm+0x184: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011357rm+0x31d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: war

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

2025-03-01 Thread Andres Salomon


Hi Hank,

Did you see this? Are you interested in preparing an update for the package?

Thanks,
Andres

On 2/28/25 14:12, Jeremy Bícha wrote:

I am explicitly emailing you to let you know that
gnome-shell-extension-no-annoyance will be removed from Debian Testing
in a few days as part of the GNOME Shell 48 transition because of this
bug. See the earlier email for more details:
https://bugs.debian.org/1096057

It can stay in Testing or be returned to Testing if someone updates
debian/control and metadata.json to mark it compatible with GNOME
Shell 48. I didn't do that myself because I do not know how to trigger
the "Window is ready" notification that this extension suppresses so I
can't verify whether the extension works. (I'm also not a maintainer
for the extension so I don't think it's my responsibility to fix this
bug.)

Note that packages that are not in Testing by April 15 will not be
able to be included in Debian 13.

https://release.debian.org/testing/freeze_policy.html

Thank you,
Jeremy Bícha




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1077311: konsole: no key repeat under wayland

2025-03-01 Thread Aurélien COUDERC

Le jeudi 26 décembre 2024, 18:52:19 UTC+1 Antti Salmela a écrit :
> I'm not the original reporter, but made the switch to wayland recently and
> encountered the same issue. My system is mostly running trixie.
> 
> On Sun, Jul 28, 2024 at 11:15:57AM -0400, Jesse Rhodes wrote:
> > Are you using plasma? In the Keyboard tab under System Settings ->
> > Input Devices, what are your settings for when a key is held, and does
> > it work in the test area? I'm attaching a screenshot of what this
> > looks like on my system, in case of locale differences.
> > 
> > If you are not using plasma, please describe your environment and any
> > other steps to reproduce the issue.
> 
> I noticed that I had configured IBus Wayland from System settings / Keyboard /
> Virtual Keyboard for some reason. After I disabled that by selecting "None",
> key repeat in konsole worked as expected.
> 
> But the problem is not exclusively with konsole, the test area also had
> issues, like the first repeat worked and after that it didn't. After
> checking things it seems like all programs using wayland natively have the 
> same
> issue, konsole (with vim) was just where it was most apparent.

Closing since it’s not a konsole problem specifically.

Feel free to reopen / reassign / open a new bug in ibus if you want to push the 
issue further.


Happy hacking,
--
Aurélien

Bug#961138: autodep8 uses host APT packages to generate dependencies for pkg-r-autopkgtest tests

2025-03-01 Thread Andreas Tille

Hi Jochen,

if you can provide a patch / MR I'm fine to apply it but currently
I have no more free spoons to work on this.

Thank you
   Andreas.

Am Sat, Mar 01, 2025 at 09:56:15PM +0100 schrieb Jochen Sprickerhof:
> * Antonio Terceiro  [2021-10-29 09:53]:
> > On Fri, Oct 29, 2021 at 07:46:30AM +0200, Andreas Tille wrote:
> > > Control: tags -1 help
> > > 
> > > Hi,
> > > 
> > > any hint from debian-ci list how to solve this?
> > 
> > Quoting Paul from
> > https://salsa.debian.org/ci-team/autodep8/-/merge_requests/10#note_279588,
> > I think the right way to solve this is:
> > 
> > > Maybe instead of querying, the code could just unconditionally add all
> > > packages in the Suggests and for each add an alternative that's always
> > > installed? I recall that apt will install the first alternative if it
> > > easily can.
> 
> I would simply add add them all to Suggests. As they are not automatically
> installed by default it should be fine if not all are installable.
> 
> Note that this bug is related to #1089197 and makes this package non
> reproducible on reproduce.debian.net. Also we would like to drop apt and the
> apt cache from the build chroot so fixing this would be appreciated.
> 
> Cheers Jochen



-- 
https://fam-tille.de

Bug#1099219: check-manifest: FTBFS: E subprocess.CalledProcessError: Command 'bzr' died with .

2025-03-01 Thread Sergio Durigan Junior

Control: retitle -1 bzr crashes with SIGABRT when trying to commit files
Control: reassign -1 src:bzr/2.7.0+bzr6622+brz
Control: affects -1 + src:check-manifest
Control: severity -1 critical

On Saturday, March 01 2025, Santiago Vila wrote:

> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
[...]
> if rc:
>>   raise subprocess.CalledProcessError(rc, command[0], output=stdout)
> E   subprocess.CalledProcessError: Command 'bzr' died with 
> .

Thanks for the bug.

This is a problem with bzr, which is used by check-manifest when doing
tests.

It's easily reproducible:

--8<---cut here---start->8---
# bzr init
Created a standalone tree (format: 2a)
# bzr whoami --branch "Test " 

  
# mkdir -p b/c
# touch a.txt b/b.txt b/c/d.txt
# bzr add -- a.txt b/b.txt b/c/d.txt
adding a.txt
adding b
adding b/b.txt
adding b/c
adding b/c/d.txt
# bzr commit -m Initial
Committing to: /tmp/

  
bzr: breezy/bzr/_dirstate_helpers_pyx.c:11215: 
__pyx_f_6breezy_3bzr_21_dirstate_helpers_pyx_update_entry: Assertion 
`PyTuple_Check(__pyx_v_details)' failed.
Aborted (core dumped)
--8<---cut here---end--->8---

Reassigning to the proper package.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#1099243: libthrust: FTBFS: Could not find a configuration file for package "libcudacxx"

2025-03-01 Thread Andreas Beckmann


Control: tag -1 wontfix

On 3/1/25 22:01, Santiago Vila wrote:

Package: src:libthrust
Version: 2.1.1-1



   The following configuration files were considered but not accepted:

 /usr/share/cmake/libcudacxx/libcudacxx-config.cmake, version: 2.2.0.0


src:libthrust, src:cub, src:libcudacxx are awaiting cruft removal as 
they have been superseded by src:cccl.



Andreas

Bug#1099253: nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not found

2025-03-01 Thread Santiago Vila


El 1/3/25 a las 22:37, Andreas Beckmann escribió:

Please clean up all the 'pahole: not found' bugs, that's #1098706 in src:linux 
and an upload for that is on the way to sid.


Ok, done.

Bug#1099205: elpa-magit: Error Symbol's value as variable is void: magit-commit-absorb

2025-03-01 Thread Xiyue Deng

Olivier Berger  writes:

> Package: elpa-magit
> Version: 4.3.0-1
> Severity: normal
>
> Dear Maintainer,
>
> If I'm not mistaken, there's now an issue with magit 4.3.0 running Emacs 30.1 
> in testing.
>
> Issueing M-x magit-status after Emacs has started, from a directory 
> containing a git checkout of a repo, I get an error about magit-commit-absorb
>
> The Messages buffer reports :
> require: Symbol’s value as variable is void: magit-commit-absorb
>
> The *Async-native-compile-log* buffer reports: 
>
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-sequence.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-sequence.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-notes.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-notes.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-worktree.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-worktree.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-tag.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-tag.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-merge.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-merge.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-branch.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-branch.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-reset.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-reset.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-files.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-files.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compiling /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-refs.el...
> /usr/share/emacs/site-lisp/elpa/magit-4.3.0/magit-refs.el: Error Symbol's 
> value as variable is void: magit-commit-absorb
> Compilation finished.
>
> Hope this is indeed linked to the Debian package, and not some strange 
> customization on my side.
>
> Best regards,
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'testing'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 
> 'bullseye-backports-staging')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.12.12-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 elpa-magit depends on:
> ii  dh-elpa-helper  2.1.5
> ii  elpa-compat 30.0.2.0+dfsg-1
> ii  elpa-llama  0.6.0-2
> ii  elpa-magit-section  4.3.0-1
> ii  elpa-seq2.24-2
> ii  elpa-transient  0.8.4-1
> ii  elpa-with-editor3.4.3-1
> ii  emacsen-common  3.0.5
> ii  git 1:2.47.2-0.1
>
> elpa-magit recommends no packages.
>
> elpa-magit suggests no packages.
>
> -- no debconf information
>
> -- 
> Olivier BERGER
> https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8
> Ingenieur Recherche - Dept INF
> Institut Mines-Telecom, Telecom SudParis, Evry (France)
>

I cannot seem to reproduce this: tried removing the eln-cache, launching
Emacs and "M-x magit-status" on a git directory, and my
*Async-native-compile-log* doesn't show any warning/error regarding
magit.

Can you try starting a clean Emacs using "emacs -Q", load only magit
(probably also transient and other dependencies), and try to reproduce
this?

-- 
Regards,
Xiyue Deng


signature.asc
Description: PGP signature

Bug#1099254: nvidia-graphics-drivers-legacy-390xx: FTBFS: /bin/sh: 1: pahole: not found

2025-03-01 Thread Santiago Vila

Package: src:nvidia-graphics-drivers-legacy-390xx
Version: 390.157-11
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build --with dkms
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{390.157}g;' \
-e 's{#MAJOR#}{390}g;' \
-e 's{#NVIDIA#}{nvidia-legacy-390xx}g;' \
-e 's{#VARIANT#}{-legacy-390xx}g;' \
-e 's{#CURRENT#}{legacy-390xx}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-legacy-390xx-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2b0: data relocation to !ENDBR: _nv035290rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2b8: data relocation to !ENDBR: _nv035286rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2c0: data relocation to !ENDBR: _nv035265rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2c8: data relocation to !ENDBR: _nv035268rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2d0: data relocation to !ENDBR: _nv035271rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2d8: data relocation to !ENDBR: _nv035267rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2e0: data relocation to !ENDBR: _nv035275rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2e8: data relocation to !ENDBR: _nv035266rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2f0: data relocation to !ENDBR: _nv035274rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2f8: data relocation to !ENDBR: _nv035269rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x300: data relocation to !ENDBR: _nv035293rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x308: data relocation to !ENDBR: _nv035277rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x310: data relocation to !ENDBR: _nv035156rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x318: data relocation to !ENDBR: _nv035156rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x320: data relocation to !ENDBR: _nv035315rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x328: data relocation to !ENDBR: _nv035316rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x330: data relocation to !ENDBR: _nv035280rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x338: data relocation to !ENDBR: _nv035279rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x340: data relocation to !ENDBR: _nv035295rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x348: data relocation to !ENDBR: _nv035158rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x350: data relocation to !ENDBR: _nv035294rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x358: data relocation to !ENDBR: _nv035157rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x360: data relocation to !ENDBR: _nv035171rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x368: data relocation to !ENDBR: _nv035172rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x370: data relocation to !ENDBR: _nv035263rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x378: data relocation to !ENDBR: _nv035264rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x380: data relocation to !ENDBR: _nv035193rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x388: data relocation to !ENDBR: _nv035189rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x390: data relocation to !ENDBR: _nv035180rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x398: data relocation to !ENDBR: _nv035185rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3a0: data relocation to !ENDBR: _nv035196rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3a8: data relocation to !ENDBR: _nv035192rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3b0: data relocation to !ENDBR: _nv035181rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3b8: data relocation to !ENDBR: _nv035186rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3c0: data relocation to !ENDBR: _nv035195rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3c8: data relocation to !ENDBR: _nv035191rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x3d0: data relocation to !ENDBR: _nv035194rm+0x0
/<>/kernel-source-tree/nvidia

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

2025-03-01 Thread Hank Knox


Hi Andres,

Yes, I did and I would be happy to prepare an updated package. There is 
an updated upstream version which I have not yet tried out, but I assume 
it works under GNOME Shell 48 and making a Debian package should be simple.


Jeremy, it seems like it would make sense to bring this under the 
umbrella of the GNOME packaging team. I would be happy to be responsible 
for it if someone on the team is willing to mentor me. I would 
appreciate help finding a workflow that fits the GNOME team's workflow.


Let me know the best way to move forward with this. In the meantime, 
I'll start updating and testing the Debian package.


Best,

Hank

On 3/1/25 16:10, Andres Salomon wrote:

Hi Hank,

Did you see this? Are you interested in preparing an update for the 
package?


Thanks,
Andres

On 2/28/25 14:12, Jeremy Bícha wrote:

I am explicitly emailing you to let you know that
gnome-shell-extension-no-annoyance will be removed from Debian Testing
in a few days as part of the GNOME Shell 48 transition because of this
bug. See the earlier email for more details:
https://bugs.debian.org/1096057

It can stay in Testing or be returned to Testing if someone updates
debian/control and metadata.json to mark it compatible with GNOME
Shell 48. I didn't do that myself because I do not know how to trigger
the "Window is ready" notification that this extension suppresses so I
can't verify whether the extension works. (I'm also not a maintainer
for the extension so I don't think it's my responsibility to fix this
bug.)

Note that packages that are not in Testing by April 15 will not be
able to be included in Debian 13.

https://release.debian.org/testing/freeze_policy.html

Thank you,
Jeremy Bícha



--
Hank Knox, FRSC
Schulich School of Music of
McGill University (retired)
Montreal, QC

Bug#1099305: RM: libperl-critic-freenode-perl -- ROM; deprectated upstream / renamed/replaced

2025-03-01 Thread gregor herrmann

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: libperl-critic-freenode-p...@packages.debian.org, 
debian-p...@lists.debian.org
Control: affects -1 + src:libperl-critic-freenode-perl
User: ftp.debian@packages.debian.org
Usertags: remove

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please remove libperl-critic-freenode-perl from the archive.
It has been updated to / renamed to / replaced by 
libperl-critic-community-perl (and only was a transitional dummy 
package since bookworm).


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmfDmsRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYGjw//VkRUdfeT/pHc9ZuBY5WD50oNgbc440Tqi0/Y8NGyNSLkG98g05LrG1A4
+c7SQjERCgIHb2hoU5TSj+MwVrtZ4IA5vf/UIQ3oiHP/8BblnbDdQUB4ePrvRYhg
DSiWOFQQxWFyhN2QpbQdAxtNPt3u3oZRFv3jHpSSPHpTyGXD1nyhQNf8IN8wh5vo
aGHvaf0xom/foMeHUo48m6H4k0isuysVqXrvAYAS7AA5A0ay0hv5AWkZFeKrl+lK
R8mhLDlSyCkpsqWJa2fsL3r8knoxs+HDSbrGmJLcNKZPNIathtJISkMqlFvGKZ5P
oxo/P6C2YHNvOG10zP+78Bh3DYG5jBzny82VEKl+HfCH9b/uKoAgdY3h3HOV7jy6
idO+nFnFoj1euG1rZvCceIorazm7++XAgrxD2FMI11Cy95y9Lab3pl/tjP+4Uf20
SIvQxIdrRtmfs92GtWK4QNsQCtbWlthLI0QrK+NplCQ27yKWRsiwIJWJ/u/VFhRX
o9Jo+KyCgW6kL+q8h/Mz57mP+cMaddP4/hgiiOMZmQACvRgh4q8xixDRAEMdpzwD
6FuBxH9Z9AW8OlX5xf8cFeZubQwI5pIK+Pr2xDP+3fF4EE+UQR7pvhnL3k9B1o0v
i/SHvquZp1F4RRMKFh65fFUMBlpXlvMfH5U0dDI1EIZPNMPUWCY=
=XpFy
-END PGP SIGNATURE-

Bug#1099302: People still can avoid multiple ...cont

2025-03-01 Thread Marian Corcodel

People can build a list in format .txt in kernel with reserved names used around
MODULE_DEVICE_TABLE, relative to names used by pci_id to avoid
duplicates, repeat ,loader
program is good make good job against this situation, seems random
number generator have
some issuess, or just voluntary just remove pci_id from kernel and let
developersto chose his name, and result double guards agains stringfy
problems.

Bug#1099306: ITP: libperl-critic-policy-plicease-prohibitarrayassignaref-perl -- Perl::Critic policy about not assigning an anonymous arrayref to an array

2025-03-01 Thread gregor herrmann

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libperl-critic-policy-plicease-prohibitarrayassignaref-perl
  Version : 100.00
  Upstream Author : Kevin Ryde Graham Ollis 
* URL : 
https://metacpan.org/release/Perl-Critic-Policy-Plicease-ProhibitArrayAssignAref
* License : GPL-3+
  Programming Lang: Perl
  Description : Perl::Critic policy about not assigning an anonymous 
arrayref to an array

The Perl::Critic::Policy::Plicease::ProhibitArrayAssignAref policy is a fork
of Perl::Critic::Policy::ValuesAndExpressions::ProhibitArrayAssignAref. It
differs from the original by not having a dependency on List::MoreUtils.

It asks you not to assign an anonymous arrayref to an array

 @array = [ 1, 2, 3 ]; # bad

The idea is that it's rather unclear whether an arrayref is intended, or
might have meant to be a list like

 @array = ( 1, 2, 3 );

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1068733: lvm2: diff for NMU version 2.03.27-1.1

2025-03-01 Thread Luke W Faraone

Control: tags 1068733 + patch
Control: tags 1068733 + pending

Dear maintainer,

I've prepared an NMU for lvm2 (versioned as 2.03.27-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru lvm2-2.03.27/debian/changelog lvm2-2.03.27/debian/changelog
--- lvm2-2.03.27/debian/changelog	2024-11-04 09:06:21.0 +
+++ lvm2-2.03.27/debian/changelog	2025-03-02 07:13:05.0 +
@@ -1,3 +1,10 @@
+lvm2 (2.03.27-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Include lvresize_fs_helper (Closes: #1068733)
+
+ -- Luke W Faraone   Sun, 02 Mar 2025 07:13:05 +
+
 lvm2 (2.03.27-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru lvm2-2.03.27/debian/lvm2.install lvm2-2.03.27/debian/lvm2.install
--- lvm2-2.03.27/debian/lvm2.install	2024-11-04 09:06:21.0 +
+++ lvm2-2.03.27/debian/lvm2.install	2025-03-02 07:13:05.0 +
@@ -50,6 +50,7 @@
 usr/sbin/vgs
 usr/sbin/vgscan
 usr/sbin/vgsplit
+usr/libexec/lvresize_fs_helper
 usr/lib/tmpfiles.d/lvm2.conf
 usr/share/man/man5/lvm.conf.5
 usr/share/man/man7/lvmcache.7


signature.asc
Description: PGP signature

Bug#1089197: Bug#961138: autodep8 uses host APT packages to generate dependencies for pkg-r-autopkgtest tests

2025-03-01 Thread Jochen Sprickerhof


Hi Andreas,

* Andreas Tille  [2025-03-01 22:39]:

if you can provide a patch / MR I'm fine to apply it but currently
I have no more free spoons to work on this.


The real question here is how to solve #1089197, i.e. how to encode the 
package relationships without depending on the apt cache (grep-aptavail 
or rmadison or anything else that is network related). I have no 
experience with R packages so I would need some input here. Possible 
ways I see are:


1. Don't add relations automatically and let the maintainer do it.

2. Always add all package names from the DISCRIPTION file to Suggest:
   From my understanding this would need some mapping from the R package 
	 name to the Debian package name and maybe a rename of the Debian 
	 packages to simplify the mapping.


3. Add the list of R package in Debian to dh-r and use it to convert the 
   package name. Note that this needs to be updated whenever a R 
	 packages is added or removed in Debian. (This is what dh-python has, 
	 afair).


Cheers Jochen


signature.asc
Description: PGP signature

Bug#1098529: anymarkup: FTBFS: E assert 2 == 0

2025-03-01 Thread John Paul Adrian Glaubitz

Control: severity -1 normal

Hello Santiago,

On Fri, 2025-02-21 at 23:26 +, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:
> 
> 
> [...]
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.12_anymarkup/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.12' does not exist -- can't clean it
> I: pybuild base:311: python3.13 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.13_anymarkup/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.13' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> running config
> I: pybuild base:311: python3.13 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_anymarkup/build/anymarkup
> copying anymarkup/cli.py -> 
> /<>/.pybuild/cpython3_3.12_anymarkup/build/anymarkup
> copying anymarkup/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_anymarkup/build/anymarkup
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.13_anymarkup/build/anymarkup
> copying anymarkup/cli.py -> 
> /<>/.pybuild/cpython3_3.13_anymarkup/build/anymarkup
> copying anymarkup/__init__.py -> 
> /<>/.pybuild/cpython3_3.13_anymarkup/build/anymarkup
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd 
> /<>/.pybuild/cpython3_3.12_anymarkup/build; python3.12 -m pytest 
> test
> = test session starts 
> ==
> platform linux -- Python 3.12.9, pytest-8.3.4, pluggy-1.5.0
> rootdir: /<>
> plugins: typeguard-4.4.1
> collected 25 items
> 
> test/test_cli.py F.  [ 
> 24%]
> test/test_cli_ini.py .   [ 
> 44%]
> test/test_cli_json.py ...[ 
> 56%]
> test/test_cli_json5.py ...   [ 
> 68%]
> test/test_cli_toml.py ...[ 
> 80%]
> test/test_cli_xml.py ..  [ 
> 88%]
> test/test_cli_yaml.py .. [ 
> 96%]
> test/test_imports.py .   
> [100%]
> 
> === FAILURES 
> ===
> __ TestCli.test_no_arguments 
> ___
> 
> self = 
> runner = 
> 
> def test_no_arguments(self, runner):
> result = runner.invoke(cli)
> >   assert result.exit_code == 0
> E   assert 2 == 0
> E+  where 2 = .exit_code
> 
> test/test_cli.py:17: AssertionError
> === short test summary info 
> 
> FAILED test/test_cli.py::TestCli::test_no_arguments - assert 2 == 0
> = 1 failed, 24 passed in 0.16s 
> =
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12_anymarkup/build; python3.12 -m pytest 
> test
> I: pybuild base:311: cd 
> /<>/.pybuild/cpython3_3.13_anymarkup/build; python3.13 -m pytest 
> test
> = test session starts 
> ==
> platform linux -- Python 3.13.2, pytest-8.3.4, pluggy-1.5.0
> rootdir: /<>
> plugins: typeguard-4.4.1
> collected 25 items
> 
> test/test_cli.py F.  [ 
> 24%]
> test/test_cli_ini.py .   [ 
> 44%]
> test/test_cli_json.py ...[ 
> 56%]
> test/test_cli_json5.py ...   [ 
> 68%]
> test/test_cli_toml.py ...[ 
> 80%]
> test/test_cli_xml.py ..  [ 
> 88%]
> test/test_cli_yaml.py .. [ 
> 96%]
> test/test_imports.py .   
> [100%]
> 
> === FAILURES 
> =

Bug#1099302: linux-source: People still can avoid multiple definitions symbol on loader.

2025-03-01 Thread Corcodel Marian

Package: linux-source
Severity: normal
Tags: patch
X-Debbugs-Cc: corcodel.mar...@gmail.com

Hi
Bellow i explain simple method used only for research purpose used as
countermeasure in order to run MODULE_DEVICE_TABLE macro whithout .ko file,
just fixing stringfy problems ,like:

ld: drivers/usb/host/ehci-pci.o:(.rodata+0x0): multiple definition of
`__mod_pci__pci_ids_device_table';
drivers/tty/serial/8250/8250_mid.o:(.rodata+0x0): first defined here
ld: drivers/usb/host/ohci-pci.o:(.rodata+0x0): multiple definition of
`__mod_pci__pci_ids_device_table';
drivers/tty/serial/8250/8250_mid.o:(.rodata+0x0): first defined here


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

Kernel: Linux 6.12.5+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
pn  linux-source-6.1  

linux-source recommends no packages.

linux-source suggests no packages.
>From 50aca464b8042c0805431cf1bd6ea9dc946ee481 Mon Sep 17 00:00:00 2001
From: Corcodel Marian 
Date: Sat, 1 Mar 2025 23:56:17 +0100
Subject: [PATCH] Avoid multiple definition on loader

Short example how to avoid multiple definition on loader, problems stringfy.
---
 drivers/tty/serial/8250/8250_lpss.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/tty/serial/8250/8250_lpss.c 
b/drivers/tty/serial/8250/8250_lpss.c
index 776ec1ef2..05aebfdc5 100644
--- a/drivers/tty/serial/8250/8250_lpss.c
+++ b/drivers/tty/serial/8250/8250_lpss.c
@@ -402,7 +402,7 @@ static const struct lpss8250_board qrk_board = {
.exit = qrk_serial_exit,
 };
 
-static const struct pci_device_id pci_ids[] = {
+static const struct pci_device_id pci_idsa[] = {
{ PCI_DEVICE_DATA(INTEL, QRK_UARTx, &qrk_board) },
{ PCI_DEVICE_DATA(INTEL, EHL_UART0, &ehl_board) },
{ PCI_DEVICE_DATA(INTEL, EHL_UART1, &ehl_board) },
@@ -418,11 +418,11 @@ static const struct pci_device_id pci_ids[] = {
{ PCI_DEVICE_DATA(INTEL, BDW_UART2, &byt_board) },
{ }
 };
-MODULE_DEVICE_TABLE(pci, pci_ids);
+MODULE_DEVICE_TABLE(pci, pci_idsa);
 
 static struct pci_driver lpss8250_pci_driver = {
.name   = "8250_lpss",
-   .id_table   = pci_ids,
+   .id_table   = pci_idsa,
.probe  = lpss8250_probe,
.remove = lpss8250_remove,
 };
-- 
2.39.5

Bug#1098633: closed by Sebastiaan Couwenberg (towncrier: FTBFS: E twisted.trial.unittest.FailTest: False is not true)

2025-03-01 Thread Ben Finney

On Sat, 1 Mar 2025, Sebastiaan Couwenberg wrote:
 
> notfound 1098633 towncrier/24.8.0-2
> severity 1098633 normal
> thanks
> 
> The package not longer FTBFS with python-click reverted back to 8.1.

Thank you for reporting, and then following up to confirm the resolution
of, this bug.

-- 
 \ “Pinky, are you pondering what I'm pondering?” “I think so, but |
  `\  where will we find an open tattoo parlor at this time of |
_o__)   night?” —_Pinky and The Brain_ |
Ben Finney 


signature.asc
Description: PGP signature

Bug#1099307: librep: binary-all FTBFS

2025-03-01 Thread Adrian Bunk

Source: librep
Version: 0.92.7-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: наб 

https://buildd.debian.org/status/fetch.php?pkg=librep&arch=all&ver=0.92.7-2&stamp=1740751732&raw=0

...
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: librep-dev (12), librep16 (4), rep (4), rep-doc (1)
 * dh_installdocs: librep-dev (0), librep16 (0), rep (0), rep-doc (0)
 * dh_installinfo: librep-dev (0), librep16 (0), rep (0), rep-doc (1)
 * dh_installman: librep-dev (1), librep16 (0), rep (0), rep-doc (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.

Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:19: binary-indep] Error 255

Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using

2025-03-01 Thread Maytham Alsudany

Hi Simon,

On Mon, 2025-02-03 at 13:32 +0100, Simon Josefsson wrote:
[...]
> Maybe adding an example for embedded static C object code like this
> would help clarify the intention.

Would adding the following after the first paragraph be sufficient in 
your view?

  Note that you do not need to list source packages recursively. For example, 
  consider the following situation: A package named "foo" declares 
  Static-Built-Using on "bar". "bar" declares Static-Built-Using on "baz". As 
  long as "foo" does not directly incorporate the contents of the "baz" package 
  during its build, then "foo" must not list "baz" in its Static-Built-Using 
  field.

--
Maytham

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

Bug#1099313: pypy3: rtupdate crash

2025-03-01 Thread Witold Baryluk

Package: pypy3
Version: 7.3.19+dfsg-3
Severity: important
X-Debbugs-Cc: witold.bary...@gmail.com

Hi


Setting up pypy3 (7.3.19+dfsg-1) ...
running pypy3 rtupdate hooks for 7.3
RPython traceback:
  File "rpython_jit_metainterp.c", line 59307, in BlackholeInterpreter_run
  File "rpython_jit_metainterp_2.c", line 13021, in dispatch_loop
Fatal RPython error: AssertionError
Aborted (core dumped)
error running pypy3 rtupdate hook public_modules.rtupdate
dpkg: error processing package pypy3 (--configure):
 installed pypy3 package post-installation script subprocess returned error 
exit status 4


This was not happening in 7.3.17+dfsg-3



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

Kernel: Linux 6.12.10-amd64 (SMP w/32 CPU threads; PREEMPT)
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 pypy3 depends on:
ii  libbz2-1.01.0.8-6
ii  libc6 2.40-5
ii  libexpat1 2.6.4-1
ii  libffi8   3.4.6-1
ii  libgcc-s1 14.2.0-12
ii  libgdbm6t64   1.24-2
ii  liblzma5  5.6.3-1+b1
ii  libncursesw6  6.5-2+b1
ii  libsqlite3-0  3.46.1-1
ii  libssl3t643.4.0-2
ii  libtinfo6 6.5-2+b1
ii  pypy3-lib 7.3.17+dfsg-3
ii  zlib1g1:1.3.dfsg+really1.3.1-1+b1

pypy3 recommends no packages.

Versions of packages pypy3 suggests:
pn  pypy3-doc  
ii  pypy3-tk   7.3.17+dfsg-3

-- no debconf information

Bug#1091806: RFS: ydotool/1.0.4-1 [ITA] -- Generic Linux command-line automation tool

2025-03-01 Thread Maytham Alsudany

Hi Andre,

On Tue, 2024-12-31 at 18:44 +0100, Andre Paiusco wrote:
>  ydotool (1.0.4-1) unstable; urgency=medium
>  .
>* Change of maintainers (Closes: #1086596).
>* New upstream release (Closes: #1053561).
>* Move license from MIT to AGPL-3.0
>* Update Standard version and Compat version

Could you please fork the existing Salsa repo[1] and push your changes
to git?

I've got a few points about the packaging:
- One package rather than two (which has already been mentioned).
- debian/upstream/metadata from DEP12[2] would be nice to have.
- Consider adding yourself to d/copyright.
- Bump Standards-Version to the recently-release 4.7.2.
- The package doesn't need to build-depend on both debhelper and
debhelper-compat. Build-Depends: debhelper should be dropped.

Additionally, could you please add me as an Uploader?

-- 
Maytham

[1]: https://salsa.debian.org/debian/ydotool
[2]: https://dep-team.pages.debian.net/deps/dep12/


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

Bug#1099199: RFS: wtmpdb/0.71.0+git20250228.4e4b54e-1 [ITA] -- utility to display login/logout/reboot information

2025-03-01 Thread Andrew Bower

Hi Maytham,

On Sun, Mar 02, 2025 at 12:46:30PM +0800, Maytham Alsudany wrote:
> On Sat, 2025-03-01 at 15:55 +, Andrew Bower wrote:
> > Changes since the last upload:
> > 
> >  wtmpdb (0.71.0+git20250228.4e4b54e-1) experimental; urgency=medium
> >  .
> >* New maintainer (Closes: #1092022)
> >* New upstream version (Closes: #1099168)
> >  - drop all patches; they are included upstream
> >  - exclude new 'wtmpdbd' daemon from packaging
> >  - include unreleased 'wtmpdb import' command (Closes: #1086559)
> >* Patch integer format string errors affecting ILP32 archs
> >* Patch out noisy logging when systemd not running
> >* d/control
> >  - add myself as maintainer
> >  - already conforming with policy v4.7.2
> >  - non-essential libaudit dependency not available for Hurd
> >* d/wtmpdb.cron.monthly
> >  - appease SC2166
> >  - squelch non-error output
> >* d/copyright: reflect additional and updated content
> >* d/lrc.config: do not check excluded wtmpdbd and varlink content
> >* add d/upstream/metadata
> >* dh_installinit: no-stop-on-upgrade
> 
> Could you please push your changes to the Salsa repo?

They are there in the debian/experimental branch. Upstream and
pristine-tar branches and tags should also be present.

Thanks!

Andrew

Bug#1093044: kwave: Update kwave to latest version

2025-03-01 Thread Aurélien COUDERC

control: fixed -1 24.12.2-1

Bug#1076456: iptables-netflow-dkms: No more builds on Debian 11 Bullseye since kernel linux-image-5.10.0-31-amd64 (5.10.221-1) due to "unexport find_module" kernel backport from 5.12

2025-03-01 Thread Andreas Beckmann

Followup-For: Bug #1076456

A patch for this issue as well as patches for supporting up to Linux
v6.13 are available in
https://salsa.debian.org/debian/iptables-netflow/-/merge_requests/4

I have only tested that the module builds again for all the kernels in
oldstable, stable, testing, sid, experimental. No usage of the module on
newer kernels has been tried.

I intend to NMU this in a few days with short delay to get the fixes
into sid, which is a prerequisite to cherry-picking some of them for the
next bookworm point release.


Andreas

Bug#1099314: RM: eglot -- ROM; obsolete, now included in Emacs core

2025-03-01 Thread Sean Whitton

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: eg...@packages.debian.org, sergi...@debian.org
Control: affects -1 + src:eglot

Hello,

Please drop this source package, we don't need it anymore now that Emacs 30.1
is in sid.  No rdeps.  The upstream repo is inactive; development now happens
in emacs.git.  Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1099315: reportbug: BTS mail forwarding causes DMARC failures

2025-03-01 Thread Martin Schwenke

Package: reportbug
X-Debbugs-Cc: mar...@meltin.net
Version: 13.1.0
Severity: important

Dear Maintainer,

When I submit a Debian bug using reportbug, I receive many DMARC
reports with failures in them.  It appears that the Debian BTS
forwards emails without changing the original sender.  This makes DKIM
and SPF fail in many cases.  It would be better to rewrite the sender
to, say,  before forwarding the message.

It is hard to judge the severity of this, since I don't know how many
recipients' SPAM filtering might have rejected the message based on
DMARC/DKIM/SPF failures.  Therefore, I'm marking it as important.

Here are some example outputs from dmarc-cat, for DMARC reports
relating to email forwarded by the Debian BTS (it is difficult for me
to provide attachments because of my local machine email config):

$ dmarc-cat 
gmx.net\!meltin.net\!1740787200\!1740873599\!cf6fcf3b8bb843b6acd2385e77dd2f5b.xml.gz
 
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: GMX — noreply-dm...@sicher.gmx.net
From 2025-03-01 11:00:00 +1100 AEDT to 2025-03-02 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(1):
IP Count   From   RFrom  RDKIM   RSPF
bendel.debian.org. 4   meltin.net meltin.net failnone

$ dmarc-cat yahoo.com\!meltin.net\!1740787200\!1740873599.xml.gz 
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: Yahoo — dmarch...@yahooinc.com
From 2025-03-01 11:00:00 +1100 AEDT to 2025-03-02 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(1):
IP Count   From   RFrom  RDKIM RSPF
bendel.debian.org. 1   meltin.net meltin.net permerror none

$ dmarc-cat google.com\!meltin.net\!1737158400\!1737244799.zip 
dmarc-cat 0.15.0,parallel/j12 by Ollivier Robert

Reporting by: google.com — noreply-dmarc-supp...@google.com
From 2025-01-18 11:00:00 +1100 AEDT to 2025-01-19 10:59:59 +1100 AEDT

Domain: meltin.net
Policy: p=none; dkim=r; spf=r

Reports(10):
IP  Count   From   RFromRDKIM   RSPF
 
mitropoulos.debian.org. 36  meltin.net meltin.net   failnone
 
mail.tryninja.io.   29  meltin.net meltin.net   failnone
 
i-bif.cloudflare-email.net. 2   meltin.net meltin.net   failnone
 
bendel.debian.org.  2   meltin.net meltin.net   failpass
 
smtp-mx-ubuntu-0.canonical.com. 1   meltin.net meltin.net   fail
softfail 
bendel.debian.org.  1   meltin.net meltin.net   failnone
 
mail-sor-f69.google.com.1   meltin.net meltin.net   failpass
 
smtp-mx-ubuntu-1.canonical.com. 1   meltin.net meltin.net   fail
softfail 
mail-sor-f41.google.com.1   meltin.net mokyokit.com passpass
 
yw-1204.doraji.xyz. 1   meltin.net meltin.net   failnone
 

Thanks...


-- Package-specific info:
** Environment settings:
EDITOR=editor
PAGER=less
VISUAL=editor
NAME='Martin Schwenke'
INTERFACE=text

** /home/martins/.reportbugrc:
reportbug_version "7.10.3"
mode standard
ui text
offline
email "mar...@meltin.net"
no-cc
list-cc-me
smtphost reportbug.debian.org

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

Kernel: Linux 6.12.11-rt-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt2.9.30
ii  python33.13.2-1
ii  python3-reportbug  13.1.0
ii  sensible-utils 0.0.24

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail  4.3.0-2+b3
ii  debconf 1.5.89
pn  debsums 
pn  dlocate 
ii  emacs-bin-common1:30.1+1-3
ii  file1:5.45-3+b1
ii  gnupg   2.2.46-1
ii  postfix [mail-transport-agent]  3.9.1-10+b1
pn  python3-urwid   
pn  reportbug-gtk   
ii  xdg-utils   1.2.1-2

Versions of packages python3-reportbug depends on:
ii  apt2.9.30
ii  file   1:5.45-3+b1
ii  python33.13.2-1
ii  python3-apt2.9.9+b1
ii  python3-debian 0.1.49
ii  python3-debianbts  4.1.1
ii  python3-requests   2.32.3+dfsg-4
ii  sensible-utils 0.0.24

python3-reportbug suggests no packages.

-- no debconf information



peace & happiness,
martin

Bug#1099316: libgit-annex-perl: missing build depdendency on tzdata

2025-03-01 Thread Jochen Sprickerhof

Source: libgit-annex-perl
Version: 0.008-1
Severity: normal

Hi,

libgit-annex-perl has a missing build depdendency on tzdata. Currently
the buildds still have it installed by default but that will change
after the trixie release. This also makes the package not reproducible
on reproduce.debian.net.

Cheers Jochen

Bug#1099318: python3-pyqt6 : Depends: qt6-base-private-abi (= 6.7.2)

2025-03-01 Thread Michael Ott

Package: python3-pyqt6
Version: 6.8.1-1+b1
Severity: important

Dear Maintainer,

I try to install calibre on my system but it is not posible

I checked the package version and found this:
Unsatisfied dependencies:
 python3-pyqt6 : Depends: qt6-base-private-abi (= 6.7.2)
Error: Unable to correct problems, you have held broken packages.

Qt is already on version 6.8.2


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (710, 'unstable'), (670, 'testing'), (660, 'experimental'), (600, 
'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 6.13-rc7-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pyqt6 depends on:
ii  libc6  2.41-3
pn  libqt6core6
ii  libqt6core6t64 [qt6-base-private-abi]  6.8.2+dfsg-5
ii  libqt6dbus66.8.2+dfsg-5
ii  libqt6gui6 6.8.2+dfsg-5
ii  libqt6network6 6.8.2+dfsg-5
ii  libqt6opengl6  6.8.2+dfsg-5
ii  libqt6openglwidgets6   6.8.2+dfsg-5
ii  libqt6printsupport66.8.2+dfsg-5
ii  libqt6sql6 6.8.2+dfsg-5
ii  libqt6test66.8.2+dfsg-5
ii  libqt6widgets6 6.8.2+dfsg-5
ii  libqt6xml6 6.8.2+dfsg-5
ii  libstdc++6 15-20250220-1
ii  python33.13.2-1
ii  python3-pyqt6.sip  13.10.0-1+b1
pn  qt6-base-abi   

python3-pyqt6 recommends no packages.

python3-pyqt6 suggests no packages.

Bug#1099199: RFS: wtmpdb/0.71.0+git20250228.4e4b54e-1 [ITA] -- utility to display login/logout/reboot information

2025-03-01 Thread Andrew Bower

Hi Maytham,

On Sun, Mar 02, 2025 at 02:27:19PM +0800, Maytham Alsudany wrote:
> The packaging looks good to me. Just one question: do you plan on
> including the wtmpdbd daemon later, or are you permanently excluding it
> from the packaging?

Thanks!

Personally I'm not convinced of the merit and wisdom of including the
daemon. Certainly not for trixie but I anticipate seeing if it could be
made optionally available, reviewing its impact and discussing on the
BTS.

Andrew

Bug#1099311: git-debrebase: Should strip epoch from generated d/changelog message

2025-03-01 Thread Sean Whitton

Package: git-debrebase
Version: 12.7
Severity: minor

Dear maintainer,

For sbcl git-debrebase generates

--8<---cut here---start->8---
sbcl (2:2.5.2-1) UNRELEASED; urgency=medium

  * Update to new upstream version 2:2.5.2.

 -- Sean Whitton   Sun, 02 Mar 2025 09:20:46 +0800
--8<---cut here---end--->8---

But I think it should strip the epoch from the free text part, i.e.

  * Update to new upstream version 2.5.2.

since the epoch is not something from upstream.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1099308: dpkg-dev: Use of uninitialized value $v{"DEB_HOST_MULTIARCH"} in concatenation (.) or string at /usr/bin/dpkg-architecture line 354.

2025-03-01 Thread Guillem Jover

Hi!

On Sun, 2025-03-02 at 02:50:35 +0100, Santiago Vila wrote:
> Package: dpkg-dev
> Version: 1.22.15

> I was going to ask ftpmaster to remove the "hello-traditional" package,
> but decided to still make a "last release" so that it's archived in 
> snapshot.d.o.
> 
> To my surprise the package failed to build on hurd-i386:
> 
> [...]
> Use of uninitialized value $v{"DEB_HOST_MULTIARCH"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_ABI"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_BITS"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_CPU"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_ENDIAN"} in concatenation (.) 
> or string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_LIBC"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_ARCH_OS"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_GNU_CPU"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_GNU_SYSTEM"} in concatenation (.) 
> or string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_GNU_TYPE"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
> Use of uninitialized value $v{"DEB_TARGET_MULTIARCH"} in concatenation (.) or 
> string at /usr/bin/dpkg-architecture line 354.
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture hurd-i386
> invalid host_arch hurd-i386 at /usr/bin/dpkg-checkbuilddeps line 122.
> dpkg-buildpackage: error: build dependencies/conflicts unsatisfied; aborting
> 
> Is this a bug in dpkg-dev?

That would seem a bit strange as I do not recall recent changes that
would affect his.

In any case, just to make sure, I was unable to reproduce this on my
hurd-i386 VM. I even tried on an amd64 chroot to remove the
build-essential and gcc packages (which is where the arch comes from),
but those fail gracefully too.

> ( The package now has autotools-dev as its only build-dependency,
>   which is clearly strange but not technically a bug )

This looks like the chroot might have issues? Perhaps the prefixed
fixchroot command in front of dpkg-buildpackage is interacting badly
with it? (Which seems specific to the hurd-* ports).

I'm CCing the debian-hurd list.

Thanks,
Guillem

Bug#1099150: soapyuhd: FTBFS: /build/reproducible-path/soapyuhd-0.4.1/UHDSoapyDevice.cpp:724:101: error: invalid new-expression of abstract class type ‘UHDSoapyRxStream’

2025-03-01 Thread A. Maitland Bottoms

I've uploaded a new version of UHD. Looks like upstream patches
from upstream SoapySDR have the changes needed to build again.

I'll prepare a soapyuhd 0.4.1-5 to address this soon.

-Maitland

Bug#1099199: RFS: wtmpdb/0.71.0+git20250228.4e4b54e-1 [ITA] -- utility to display login/logout/reboot information

2025-03-01 Thread Maytham Alsudany

Hi Andrew,

On Sat, 2025-03-01 at 15:55 +, Andrew Bower wrote:
> Changes since the last upload:
> 
>  wtmpdb (0.71.0+git20250228.4e4b54e-1) experimental; urgency=medium
>  .
>* New maintainer (Closes: #1092022)
>* New upstream version (Closes: #1099168)
>  - drop all patches; they are included upstream
>  - exclude new 'wtmpdbd' daemon from packaging
>  - include unreleased 'wtmpdb import' command (Closes: #1086559)
>* Patch integer format string errors affecting ILP32 archs
>* Patch out noisy logging when systemd not running
>* d/control
>  - add myself as maintainer
>  - already conforming with policy v4.7.2
>  - non-essential libaudit dependency not available for Hurd
>* d/wtmpdb.cron.monthly
>  - appease SC2166
>  - squelch non-error output
>* d/copyright: reflect additional and updated content
>* d/lrc.config: do not check excluded wtmpdbd and varlink content
>* add d/upstream/metadata
>* dh_installinit: no-stop-on-upgrade

Could you please push your changes to the Salsa repo?

Thanks,
Maytham


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

Bug#1099291: starlette: FTBFS: E assert '{"example":123}' == '{"example": 123}'

2025-03-01 Thread Santiago Vila

Package: src:starlette
Version: 0.41.3-2
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build" 
module
I: pybuild base:311: python3.13 -m build --skip-dependency-check --no-isolation 
--wheel --outdir /<>/.pybuild/cpython3_3.13_starlette  
* Building wheel...
Successfully built starlette-0.41.3-py3-none-any.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.13 with 
"installer" module
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.13_starlette/build; python3.13 -m pytest 
tests
= test session starts ==
platform linux -- Python 3.13.2, pytest-8.3.4, pluggy-1.5.0
rootdir: /<>/.pybuild/cpython3_3.13_starlette/build
configfile: pyproject.toml
plugins: anyio-4.8.0, typeguard-4.4.2
collected 863 items

tests/middleware/test_base.py .x.x.. [  4%]
...  [  6%]
tests/middleware/test_cors.py .. [  9%]
tests/middleware/test_errors.py  [ 11%]
tests/middleware/test_gzip.py .. [ 12%]
tests/middleware/test_https_redirect.py ..   [ 12%]
tests/middleware/test_middleware.py ..   [ 12%]
tests/middleware/test_session.py ..  [ 14%]
tests/middleware/test_trusted_host.py .  [ 14%]
tests/middleware/test_wsgi.py .F...F [ 15%]
tests/test__utils.py ..  [ 17%]
tests/test_applications.py . [ 22%]
.[ 23%]
tests/test_authentication.py ... [ 24%]
tests/test_background.py [ 25%]
tests/test_concurrency.py .. [ 26%]
tests/test_config.py .   [ 26%]
tests/test_convertors.py ..  [ 27%]
tests/test_datastructures.py ..  [ 31%]
tests/test_endpoints.py  [ 33%]
tests/test_exceptions.py .   [ 35%]
tests/test_formparsers.py .. [ 41%]
..   [ 44%]
tests/test_requests.py ...FF..FF [ 49%]
 [ 53%]
tests/test_responses.py  [ 59%]
.[ 66%]
tests/test_routing.py .. [ 71%]
...  [ 76%]
tests/test_schemas.py ...[ 76%]
tests/test_staticfiles.py .. [ 82%]
 [ 83%]
tests/test_status.py ..  [ 83%]
tests/test_templates.py  [ 86%]
tests/test_testclient.py .   [ 91%]
tests/test_websockets.py ... [ 96%]
 [100%]

=== FAILURES ===
___ test_wsgi_post[asyncio] 

test_client_factory = functools.partial(, backend='asyncio', backend_options={})

def test_wsgi_post(test_client_factory: TestClientFactory) -> None:
app = WSGIMiddleware(echo_body)
client = test_client_factory(app)
response = client.post("/", json={"example": 123})
assert response.status_code == 200
>   assert response.text

Bug#1099301: libpam-tmpdir: please set TMPDIR ACLs for compatibility with subuids

2025-03-01 Thread Roberto C. Sanchez

Package: libpam-tmpdir
Version: 0.09+b2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After updating sbuild recently (to version 0.88.4~bpo12+2) I started
experiencing build failures like this:

I: Unpacking /home/roberto/.cache/sbuild/unstable-amd64.tar.zst to 
/tmp/user/2000/tmp.sbuild.IBpZHAqVJp...
tar: /tmp/user/2000/tmp.sbuild.IBpZHAqVJp: Cannot open: Permission denied
tar: Error is not recoverable: exiting now
bad exit status (512) for tar
E: ABORT: Received PIPE signal (requesting cleanup and shutdown)

(the last line repeates several hundred or thousand times)

It would appear that sbuild now respects the setting of TMPDIR, and when
using it in an unshare configuration, the process is run under a subuid.

Regards,

- -Roberto

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

Kernel: Linux 6.1.0-31-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 libpam-tmpdir depends on:
ii  libc6   2.36-9+deb12u9
ii  libpam-runtime  1.5.2-6+deb12u1
ii  libpam0g1.5.2-6+deb12u1

libpam-tmpdir recommends no packages.

libpam-tmpdir suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAmfDgusACgkQldFmTdL1
kUI6tBAAt9NT8ei7usC/el9KrrdBLh5XBxEwA6pUVVQLiTcoAb9WicwO27JrQif9
bxVQ/8YtTLZj1RnrYhki3EQRDBp6TZoihC3cfUGjjinqHtucyiXy6BYLhevnVg+1
hijo52RiFqP+Fs9+5Xd6JIU+kB0slgh8/QGoCOAqlGJyGrrQsstAbEjrKpDayADd
Sm6rcttBovJ+1BQxZwx3AS8vpaD4gIvjRsMDU2jFZ4qE3SJkY7mMA8x5qldLKuna
Pe6FE/5L4lzBW/H7+QVxF+c6skq2V8odqmXJQrAxl7vYyL4rMdhXz6H9DHerli3A
q+jFHV0rRtGlBSsq1Yksvv57sszPtx/w3kMOQfDoAhrjWz38Oor/7MPdxc8s6IRI
CPqIsEKaN2x7mdDW0YnIhz000JbdfMRQZz72Ky29O9db5Z14XldmUNn38HVugg6q
VlnfvZjvEn1tt2QOFZkZWuCSIvGSx2ms5LLbPSBAS7eAU8gTvmVmOlYtszLGzdiF
sOuVjF5TaLSDc2SoLyZ3wjxsaj3Tvj1dq/KZdtUw598L1RgZgGemfMwqLR+kwjy4
UT7hDYC5L9Yz4y60nBpSNg9Se/EeJLYGUyl71W4uB161OSPb+V8Mga3vVvdLhfE2
/b7kOIBPZi1Ax18/hHSk3HxbLO1bZgZUA5YRcOZROqL6fpnDv8w=
=NbjM
-END PGP SIGNATURE-

Bug#1001647: visidata phones home

2025-03-01 Thread cacin

Package: visidata
Version: 3.0.2-1
Followup-For: Bug #1001647

I am submitting a patch for the version of visidata currently packaged in
debian sid to eliminate the default behavior of the application phoning home,
which has raised some privacy concerns.

When this patch is applied, visidata will not phone home by default anymore.
Users retain the possibility to enable the phoning home functionality by
explicitly specifying the options.motd_url option in their visidatarc
configuration file with a suitable value.

There is an existing lintian tag, privacy-breach-generic, which can be used as
an indication that phoning home is considered undesirable behavior within the
debian project. Additionally, other packages in debian, for example gpsbabel
[1], have also been modified to remove similar privacy issues, further
establishing a precedent for this change.

While this behavior is not explicitly codified in debian policy yet, phoning
home goes against user expectations when utilizing debian-provided packages.

[1] 
https://salsa.debian.org/debian-gps-team/pkg-gpsbabel/-/tree/master/debian/patches?ref_type=heads
diff --git a/visidata/motd.py b/visidata/motd.py
index 571a8de..e1aaa75 100644
--- a/visidata/motd.py
+++ b/visidata/motd.py
@@ -12,7 +12,7 @@ import random
 
 from visidata import options, asyncsingle, vd, VisiData
 
-vd.option('motd_url', 'https://visidata.org/motd-'+vd.version, 'source of 
randomized startup messages', sheettype=None)
+vd.option('motd_url', '', 'source of randomized startup messages', 
sheettype=None)
 
 
 vd.motd = 'Support VisiData: https://github.com/sponsors/saulpw'

Bug#1099300: linux-source: Iteration MODULE_DEVICE_TABLE seem do not is safe

2025-03-01 Thread Corcodel Marian

Package: linux-source
Severity: normal
X-Debbugs-Cc: corcodel.mar...@gmail.com

Hi Iteration MODULE_DEVICE_TABLE seem do not is safe, which depend by parameter
CONFIG_MODULE but is not all systems is build with modules, carefoul here.


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

Kernel: Linux 6.12.5+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
pn  linux-source-6.1  

linux-source recommends no packages.

linux-source suggests no packages.

Bug#1099101: further information

2025-03-01 Thread Aurélien COUDERC

Le vendredi 28 février 2025, 12:44:38 UTC+1 Michael Becker a écrit :
> under X11 konsole behaves as expected
> the problem only occurs under wayland

Works for me under Wayland.

Can you check what you have in System Settings / Shortcuts / Common Actions / 
Navigation for the Backward Word and Forward Word actions ?

Bug#1099135: kwin_wayland: uses 100% CPU when I drag window to top edge multiple times and freezes desktop (Bug#1095945)

2025-03-01 Thread Antonio


Package: kwin-wayland
Version: 4:6.3.0-2
Severity: important

Dear Maintainer,
please consider updating kwin (kwin-wayland packages) to version 6.3.2 
to fix the above bug.


Thanks,
Antonio


References:

https://lists.debian.org/debian-qt-kde/2025/02/msg00442.html

https://bugs.kde.org/show_bug.cgi?id=499913
https://bugs.kde.org/show_bug.cgi?id=493797

Bug#1099179: komposter: FTBFS on amd64: patch.c:575:11: error: assignment to ‘unsigned int ’ from incompatible pointer type ‘long unsigned int ’ [-Wincompatible-pointer-types]

2025-03-01 Thread Adrian Bunk

Control: tags -1 patch

On Sat, Mar 01, 2025 at 12:20:22PM +0100, Sebastian Ramacher wrote:
> Source: komposter
> Version: 0+git20201216+ds-6
> Severity: serious
>...
> patch.c:575:11: error: assignment to ‘unsigned int *’ from incompatible 
> pointer type ‘long unsigned int *’ [-Wincompatible-pointer-types]
>   575 |   fptr=(unsigned long*)(&rf);
>   |   ^
>...

A fix is attached.

cu
Adrian
Description: u32 always matches int in Debian, and fix a usage in patch.c
Author: Adrian Bunk 

--- komposter-0+git20201216+ds.orig/arch.h
+++ komposter-0+git20201216+ds/arch.h
@@ -12,13 +12,13 @@
 
 
 // dword size depending on platform
-#if __x86_64__
+//#if __x86_64__
   #define u32 unsigned int
   #define s32 int
-#else
-  #define u32 unsigned long
-  #define s32 long
-#endif
+//#else
+//  #define u32 unsigned long
+//  #define s32 long
+//#endif
 
 
 // Apple Mac OS X
--- komposter-0+git20201216+ds.orig/patch.c
+++ komposter-0+git20201216+ds/patch.c
@@ -572,7 +572,7 @@ void patch_draw_modulator(void)
 i=sscanf(modeditbox, "%f", &rf);
 if (i==1) {
   rf=knob_scale2float(mod[csynth][mi].scale, rf);
-  fptr=(unsigned long*)(&rf);
+  fptr=(u32*)(&rf);
   fmask=0x; j=32;
   while(j>modquantifier[csynth][cpatch[csynth]][mi]) { fmask<<=1; j--; }
   *fptr&=fmask;

Bug#1099310: python3-stdlib-extensions should drop 3.12

2025-03-01 Thread Adrian Bunk

Source: python3-stdlib-extensions
Version: 3.13.1-1
Severity: serious

python3-stdlib-extensions should drop 3.12.

Bug#1086798: bookworm-pu: package mariadb 1:10.11.10-0+deb12u1

2025-03-01 Thread Otto Kekäläinen

Hi,

> Please go ahead, bearing in mind that the window for 12.10 closes next
> weekend.

Thanks! Upload is done
(https://tracker.debian.org/news/1623097/accepted-mariadb-110-0deb12u1-source-into-proposed-updates/)
but I don't see builds happening at
https://buildd.debian.org/status/package.php?p=mariadb&suite=bookworm.
I guess I will see the build results next weekend?

> > Also note that the sooner this can be uploaded to
> > stable-updates-proposed, the more time we will have to collect
> > build/test/user feedback and potentially catch any potential
> > regressions before the next point release in actual stable-updates.
>
> I don't think you mean stable-updates here [
> https://lists.debian.org/debian-devel-announce/2011/03/msg00010.html ]

Right, I meant proposed-updates -> stable (bookworm).

Bug#1099307: librep: binary-all FTBFS

2025-03-01 Thread наб

Control: tags -1 + pending

  
https://salsa.debian.org/debian/librep/-/commit/bf6b39cff1d5cbf1fc6d0c7c53a335e44580d7ed
and this is tagged debian/0.92.7-2
but is not in the 0.92.7-2 dsc 💀
so Andreas uploaded a .changes from the wrong revision, reads like?


signature.asc
Description: PGP signature

Bug#1075716: ktouch: Unable to type characters under native wayland client

2025-03-01 Thread Aurélien COUDERC

control: fixed -1  4:24.12.0-1

Bug#1099283: ros-vcstools: FTBFS: E subprocess.CalledProcessError: Command '['bzr', 'commit', '-m', 'initial']' died with .

2025-03-01 Thread Santiago Vila

Package: src:ros-vcstools
Version: 0.1.42-9
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules clean
dh clean --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.13 setup.py clean 
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:270: UserWarning: 
Unknown distribution option: 'tests_require'
  warnings.warn(msg)
running clean
removing '/<>/.pybuild/cpython3_3.13/build' (and everything under 
it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.13' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --buildsystem=pybuild

[... snipped ...]

def check_call(*popenargs, **kwargs):
"""Run command with arguments.  Wait for command to complete.  If
the exit code was zero then return, otherwise raise
CalledProcessError.  The CalledProcessError object will have the
return code in the returncode attribute.

The arguments are the same as for the call function.  Example:

check_call(["ls", "-l"])
"""
retcode = call(*popenargs, **kwargs)
if retcode:
cmd = kwargs.get("args")
if cmd is None:
cmd = popenargs[0]
>   raise CalledProcessError(retcode, cmd)
E   subprocess.CalledProcessError: Command '['bzr', 'commit', '-m', 
'initial']' died with .

/usr/lib/python3.13/subprocess.py:421: CalledProcessError
___ ERROR at setup of BzrClientTest.test_get_url_nonexistant ___

self = 

@classmethod
def setUpClass(self):
self.root_directory = tempfile.mkdtemp()
self.directories = dict(setUp=self.root_directory)
self.remote_path = os.path.join(self.root_directory, "remote")
os.makedirs(self.remote_path)

# create a "remote" repo
subprocess.check_call(["bzr", "init"], cwd=self.remote_path)
subprocess.check_call(["touch", "fixed.txt"], cwd=self.remote_path)
subprocess.check_call(["bzr", "add", "fixed.txt"], cwd=self.remote_path)
>   subprocess.check_call(["bzr", "commit", "-m", "initial"], 
> cwd=self.remote_path)

test/test_bzr.py:63: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

popenargs = (['bzr', 'commit', '-m', 'initial'],)
kwargs = {'cwd': '/tmp/tmpxb1c4agh/remote'}, retcode = -6
cmd = ['bzr', 'commit', '-m', 'initial']

def check_call(*popenargs, **kwargs):
"""Run command with arguments.  Wait for command to complete.  If
the exit code was zero then return, otherwise raise
CalledProcessError.  The CalledProcessError object will have the
return code in the returncode attribute.

The arguments are the same as for the call function.  Example:

check_call(["ls", "-l"])
"""
retcode = call(*popenargs, **kwargs)
if retcode:
cmd = kwargs.get("args")
if cmd is None:
cmd = popenargs[0]
>   raise CalledProcessError(retcode, cmd)
E   subprocess.CalledProcessError: Command '['bzr', 'commit', '-m', 
'initial']' died with .

/usr/lib/python3.13/subprocess.py:421: CalledProcessError
 ERROR at setup of BzrClientTest.test_url_matches_with_shortcut 

self = 

@classmethod
def setUpClass(self):
self.root_directory = tempfile.mkdtemp()
self.directories = dict(setUp=self.root_directory)
self.remote_path = os.path.join(self.root_directory, "remote")
os.makedirs(self.remote_path)

# create a "remote" repo
subprocess.check_call(["bzr", "init"], cwd=self.remote_path)
subprocess.check_call(["touch", "fixed.txt"], cwd=self.remote_path)
subprocess.check_call(["bzr", "add", "fixed.txt"], cwd=self.remote_path)
>   subprocess.check_call(["bzr", "commit", "-m", "initial"], 
> cwd=self.remote_path)

test/test_bzr.py:63: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

popenargs = (['bzr', 'commit', '-m', 'initial'],)
kwargs = {'cwd': '/tmp/tmpxb1c4agh/remote'}, retcode = -6
cmd = ['bzr', 'commit', '-m', 'initial']

def check_call(*popenargs, **kwargs):
"""Run command with arguments.  Wait for command to complete.  If
the exit code was zero then return, otherwise raise
CalledProcessError.  The CalledProcessError object will have the
return code in the returncode attribute.

The arguments are the same as for the call function.  Example:

check_call(["ls", "-l"])
"""
retcode = call(*popenargs, **kwargs)
if retcode:
cmd = kwargs.get("args")
if cmd is None:

Bug#1099304: please update crate cc to v1.2

2025-03-01 Thread Jonas Smedegaard

Source: rust-cc
Version: 1.1.14-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update crate cc to v1.2.


-BEGIN PGP SIGNATURE-

wsG7BAEBCgBvBYJnw5ksCRAsfDFGwaABIUcUAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmfWA5HdLPvcR1hUe1xAyInAtAeW7aRa2usQoO63eiEj
uxYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAADN+A/9GuZe8mdVB3tIYaV/WYEGIdKv
PpfehNqa4mWNNkKL49QUgrI87QlLhUbHtFyGbHTdkJn7W6tLRPv//vje1KiyUw8e
/kPUpq0LlPkKFhReUAFW3u7ZcN/PgExf1giKOa9ZWo/bAMfshZem+Dm9+P57NKNi
aLLA62BPAROny7TJ654l14wwaftSJdZKCF3T1g6qXaK5De6KQY+cb/13XNulAejT
S0TNPu4SGOQ2FXf+49pJMolGiYvyPbg3vOqTxivLmgylcplhkGWnqXTC9aXQyOAE
PNK4IwpbtUs//GMjlcahG89ysK/DBJwANbLz1l/Qp+Yc7zhHlFPqIsjXfHzTMiEE
v4jPKdlk3W5qUro559V/FvuRE8h5Jvbn+S+NGH8fzX6FUu5AGWnuSYGWAR5igf9q
6NsXJkqXkAar3NfpayKGCRZmoGSNZe3WnIgrV4EU9yV1OnxwDThr0DGBdoTo6tTD
udTQ1GMyvD7nU5eI316iBPvXHEfT0YOs4w3PaoRUXIdtuG3G72Zezf3wKCVnvmeg
3+I1P+3DOXR55+OB7d83RZuBtogOT2HDC8O+7mDLYH3KZZW5lxP2RVRU0yc/BayP
tikhuMp1OlfKoYzYaAuqyTAWbR1rjkrpl8ZJmIOojGr+nyz1wJozwjq3PogwaS0Y
cB+jassj0HCFJZVRK4Y=
=YVNs
-END PGP SIGNATURE-

Bug#1098661: fixed in linux 6.13.5-1~exp1

2025-03-01 Thread Bastian Blank

On Fri, Feb 28, 2025 at 09:14:33PM +0100, Salvatore Bonaccorso wrote:
> > I suggest that "flash-kernel" should be updated if zboot is to be enabled 
> > again in the future.
> Can you please fill a bug aainst frash-kernel as well (as Bastian
> cloned this one for grub as well?)

I'm trying to write those bugs.  There are more targets that needs them.
And we may want to start to use usertags for them.

Right now on my list is:
- flash-kernel
- raspi-firmware
- qemu (https://gitlab.com/qemu-project/qemu/-/issues/2810)

Any more?

Do we want to provide a tool for that?  Doing it in shell is cumbersome.

Bastian

-- 
There are certain things men must do to remain men.
-- Kirk, "The Ultimate Computer", stardate 4929.4

Bug#1099177: Recommends non-existing webext-plasma-browser-integration

2025-03-01 Thread Michael Biebl

Package: plasma-desktop
Version: 4:6.3.2-1
Severity: normal

The latest update added a Recommends on
webext-plasma-browser-integration.
This package does not exist in the archive though.


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

Kernel: Linux 6.12.16-amd64 (SMP w/16 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 plasma-desktop depends on:
ii  accountsservice23.13.9-7
ii  breeze 4:6.3.2-1
ii  kactivitymanagerd  6.3.2-1
ii  kde-cli-tools  4:6.3.2-1
ii  kded6  6.11.0-1
ii  kio6   6.11.0-1
ii  layer-shell-qt 6.3.2-1
ii  libaccounts-qt6-1  1.17-4+b1
ii  libc6  2.41-2
ii  libcanberra0   0.30-17+b1
ii  libglib2.0-0t642.83.5-1
ii  libibus-1.0-5  1.5.32~rc1-1
ii  libicu72   72.1-6
ii  libkaccounts6-24:24.12.0-1
ii  libkf6attica6  6.11.0-1
ii  libkf6authcore66.11.0-1
ii  libkf6baloo6   6.11.0-1
ii  libkf6bookmarks6   6.11.0-1
ii  libkf6codecs6  6.11.0-1
ii  libkf6completion6  6.11.0-1
ii  libkf6configcore6  6.11.0-1
ii  libkf6configgui6   6.11.0-1
ii  libkf6configwidgets6   6.11.0-1
ii  libkf6coreaddons6  6.11.0-1
ii  libkf6crash6   6.11.0-1
ii  libkf6dbusaddons6  6.11.0-1
ii  libkf6globalaccel6 6.11.0-1
ii  libkf6guiaddons6   6.11.0-1
ii  libkf6i18n66.11.0-1
ii  libkf6i18nlocaledata6  6.11.0-1
ii  libkf6iconwidgets6 6.11.0-1
ii  libkf6itemviews6   6.11.0-1
ii  libkf6jobwidgets6  6.11.0-1
ii  libkf6kcmutils66.11.0-1
ii  libkf6kcmutilscore66.11.0-1
ii  libkf6kcmutilsquick6   6.11.0-1
ii  libkf6kiocore6 6.11.0-1
ii  libkf6kiofilewidgets6  6.11.0-1
ii  libkf6kiogui6  6.11.0-1
ii  libkf6kiowidgets6  6.11.0-1
ii  libkf6newstuffcore66.11.0-1
ii  libkf6notifications6   6.11.0-1
ii  libkf6notifyconfig66.11.0-1
ii  libkf6package6 6.11.0-1
ii  libkf6runner6  6.11.0-1
ii  libkf6service-bin  6.11.0-1
ii  libkf6service6 6.11.0-1
ii  libkf6solid6   6.11.0-1
ii  libkf6sonnetcore6  6.11.0-1
ii  libkf6sonnetui66.11.0-1
ii  libkf6svg6 6.11.0-1
ii  libkf6widgetsaddons6   6.11.0-1
ii  libkf6windowsystem66.11.0-1
ii  libkf6xmlgui6  6.11.0-1
ii  libkworkspace6-6   4:6.3.2-1
ii  libnotificationmanager14:6.3.2-1
ii  libpackagekitqt6-1 1.1.2-1+b1
ii  libplasma6 6.3.2-1
ii  libplasmaactivities6   6.3.2-1
ii  libplasmaactivitiesstats1  6.3.2-1
ii  libplasmaquick66.3.2-1
ii  libprocesscore10   4:6.3.2-1
ii  libqt6core6t64 [qt6-base-private-abi]  6.7.2+dfsg-6
ii  libqt6dbus66.7.2+dfsg-6
ii  libqt6gui6 6.7.2+dfsg-6
ii  libqt6network6 6.7.2+dfsg-6
ii  libqt6qml6 6.7.2+dfsg-11
ii  libqt6quick6   6.7.2+dfsg-11
ii  libqt6quickwidgets66.7.2+dfsg-11
ii  libqt6sql6 6.7.2+dfsg-6
ii  libqt6waylandclient6   6.7.2-5
ii  libqt6widgets6 6.7.2+dfsg-6
ii  libqt6xml6

Bug#1099176: gnucash: QIF import fails

2025-03-01 Thread Martin Schwenke

Package: gnucash
Version: 1:5.10-0.1
Severity: important
Tags: upstream
X-Debbugs-Cc: mar...@meltin.net

Dear Maintainer,

QIF import fails.  The entire process appears as though it is followed
successfully but no records are imported from the imported QIF files.

Upstream bug https://bugs.gnucash.org/show_bug.cgi?id=799492 covers
this issue.  Comment 5 contains a patch that works around the bug
(worked for me!), which could be added to the Debian version of the
package until a fixed upstream version is released.

Thanks...

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

Kernel: Linux 6.12.11-rt-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages gnucash depends on:
ii  gnucash-common  1:5.10-0.1
ii  guile-3.0   3.0.10+really3.0.10-4
ii  guile-3.0-libs  3.0.10+really3.0.10-4
ii  libaqbanking44  6.6.0-1
ii  libboost-filesystem1.83.0   1.83.0-4.1
ii  libboost-locale1.83.0   1.83.0-4.1
ii  libboost-program-options1.83.0  1.83.0-4.1
ii  libc6   2.40-7
ii  libcairo2   1.18.2-2
ii  libcrypt-ssleay-perl0.73.06-2+b4
ii  libdate-manip-perl  6.96-1
ii  libdbi1t64  0.9.0-6.1+b1
ii  libfinance-quote-perl   1.64-3
ii  libgcc-s1   14.2.0-16
ii  libgdk-pixbuf-2.0-0 2.42.12+dfsg-2
ii  libglib2.0-0t64 2.83.3-2
ii  libgtk-3-0t64   3.24.48-4
ii  libgwengui-gtk3-79t64   5.12.0-1
ii  libgwenhywfar79t64  5.12.0-1
ii  libhtml-tableextract-perl   2.15-2
ii  libhtml-tree-perl   5.07-3
ii  libicu7272.1-6
ii  libofx7t64  1:0.10.9-1.1+b2
ii  libpango-1.0-0  1.56.1-1
ii  libpangocairo-1.0-0 1.56.1-1
ii  libpython3.13   3.13.2-1
ii  libsecret-1-0   0.21.6-3
ii  libstdc++6  14.2.0-16
ii  libwebkit2gtk-4.1-0 2.46.6-1
ii  libwww-perl 6.77-1
ii  libxml2 2.12.7+dfsg+really2.9.14-0.2+b2
ii  perl5.40.1-2
ii  zlib1g  1:1.3.dfsg+really1.3.1-1+b1

Versions of packages gnucash recommends:
ii  gnucash-docs 5.10-0.1
pn  python3-gnucash  
pn  yelp 

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information

Bug#1099132: update-fonts-dir.8: Some remarks and a patch with editorial changes for this man page

2025-03-01 Thread Bjarni Ingi Gislason

Package: xfonts-utils
Version: 1:7.7+7
Severity: minor
Tags: patch

   * What led up to the situation?

 Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man 
page"

  [Use "groff -e ' $' -e '\\~$' " to find obvious trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?


devtag.tmac: warning: Refrain from reading this file again


   * What outcome did you expect instead?

 No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.


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

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

Versions of packages xfonts-utils depends on:
ii  libc6 2.40-7
ii  libfontenc1   1:1.1.8-1+b2
ii  libfreetype6  2.13.3+dfsg-1
ii  x11-common1:7.7+24
ii  xfonts-encodings  1:1.0.4-2.2
ii  zlib1g1:1.3.dfsg+really1.3.1-1+b1

xfonts-utils recommends no packages.

xfonts-utils suggests no packages.

-- no debconf information
Input file is update-fonts-dir.8

Output from "mandoc -T lint  update-fonts-dir.8": (shortened list)


  1 skipping insecure request: mso
  3 whitespace at end of input line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Output from "test-groff -mandoc -t -ww -z update-fonts-dir.8": (shortened list)

  2 trailing space in the line

Remove trailing space with: sed -e 's/  *$//'

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

Number of lines affected is

3

-.-.

FSF office address update.  See
https://lists.gnu.org/archive/html/bug-gnulib/2024-09/msg4.html

17:.\" Suite 330, Boston, MA 02111-1307 USA

-.-.

Trailing space in a macro call.
Remove with "sed -i -e 's/  *$//'"

94:.IR /usr/share/fonts/X11/ directory 

-.-.

Section headings (.SH and .SS) do not need quoting.

148:.SH "EXIT STATUS"
174:.SH "SEE ALSO"

-.-.

Output from "test-groff  -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z 
":

devtag.tmac: warning: Refrain from reading this file again
troff::93: warning: trailing space in the line
troff::95: warning: trailing space in the line

-.-.

Generally:

Split (sometimes) lines after a punctuation mark; before a conjunction.
--- update-fonts-dir.8  2025-02-28 17:24:09.003667398 +
+++ update-fonts-dir.8.new  2025-02-28 17:30:49.020033775 +
@@ -90,9 +90,9 @@ in package maintainer scripts is provide
 displays a brief usage message and exits.
 .PP
 .B \-7\fR, \fB\-\-x11r7\-layout
-switches the font layout to the one introduced in X11R7: fonts in 
-.IR /usr/share/fonts/X11/ directory 
-(default is: fonts in 
+switches the font layout to the one introduced in X11R7: fonts in
+.IR /usr/share/fonts/X11/ directory
+(default is: fonts in
 .IR /usr/lib/X11/fonts/ directory)
 .SH OPERANDS
 .B update\-fonts\-dir
@@ -145,7 +145,7 @@ The supplied
 was invalid.
 .B update\-fonts\-dir
 skipped it.
-.SH "EXIT STATUS"
+.SH EXIT STATUS
 .TP
 0
 .B update\-fonts\-dir
@@ -171,6 +171,6 @@ command.
 .SH AUTHOR
 .B update\-fonts\-dir
 was written by Branden Robinson.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR mkfontdir (1x)
 .\" vim:set et tw=80:
  Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)

[gn]roff -mandoc -t -ww -b -z -K utf8 

  The same goes for man pages that are used as an input.

  For a style guide use

  mandoc -T lint

-.-

  Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.

  It should also check its input files for too long (> 80) lines.

  This is just a simple quality control measure.

  The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.

  Common defects:

  Not removing trailing spaces (in in- and output).
  The reason for these trailing spaces should be found and eliminated.

  "git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")

  Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced.

  The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.

  See man-pages(7), item "semantic newline".

-.-

The difference between the formatted output of the original and patched file
can be seen with:

  nroff -mandoc  > 
  nroff -mandoc  >

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

2025-03-01 Thread Jeremy Bícha

I am explicitly emailing you to let you know that
gnome-shell-extension-no-annoyance will be removed from Debian Testing
in a few days as part of the GNOME Shell 48 transition because of this
bug. See the earlier email for more details:
https://bugs.debian.org/1096057

It can stay in Testing or be returned to Testing if someone updates
debian/control and metadata.json to mark it compatible with GNOME
Shell 48. I didn't do that myself because I do not know how to trigger
the "Window is ready" notification that this extension suppresses so I
can't verify whether the extension works. (I'm also not a maintainer
for the extension so I don't think it's my responsibility to fix this
bug.)

Note that packages that are not in Testing by April 15 will not be
able to be included in Debian 13.

https://release.debian.org/testing/freeze_policy.html

Thank you,
Jeremy Bícha

Bug#1078229: xserver-xorg-video-ivtvdev: FTBFS with GCC 14: error: assignment ... from incompatible pointer type ...

2025-03-01 Thread Petter Reinholdtsen

Control: tags -1 + patch

The following patch should get the package building again:

Description: Fix build problems with newer Xorg and compiler.
 Ensure correct method and variable declaration to avoid fatal
 compiler warnings.
Author: Petter Reinholdtsen 
Forwarded: no
Last-Update: 2025-03-01
---
Index: xserver-xorg-video-ivtvdev-salsa/src/ivtv.c
===
--- xserver-xorg-video-ivtvdev-salsa.orig/src/ivtv.c2025-03-01 
08:38:08.0 +
+++ xserver-xorg-video-ivtvdev-salsa/src/ivtv.c 2025-03-01 08:39:21.550211876 
+
@@ -314,7 +314,7 @@
 int i;
 GDevPtr *devSections;
 int numDevSections;
-char *dev;
+const char *dev;
 Bool foundScreen = FALSE;
 int *usedChips;
 int numUsed;
Index: xserver-xorg-video-ivtvdev-salsa/src/ivtv_hw.c
===
--- xserver-xorg-video-ivtvdev-salsa.orig/src/ivtv_hw.c 2025-03-01 
08:38:08.0 +
+++ xserver-xorg-video-ivtvdev-salsa/src/ivtv_hw.c  2025-03-01 
08:39:14.554137292 +
@@ -168,12 +168,12 @@
 /* open correct framebuffer device  */
 
 static int
-ivtv_open(int scrnIndex, char *dev, char **namep, IVTVDevPtr devPtr)
+ivtv_open(int scrnIndex, const char *dev, char **namep, IVTVDevPtr devPtr)
 {
 struct fb_fix_screeninfo fix;
 int fbufId = 255;
 int yuvId;
-char *devid;
+const char *devid;
 int fd;
 
 /* try argument (from XF86Config) first */
@@ -211,7 +211,7 @@
 if (fd == -1 || devPtr == NULL)
return fd;
 
-devid = dev + 7;
+devid = &dev[7];
 
 if (*devid == '/')
devid++;
@@ -340,9 +340,9 @@
 
 Bool
 #if XSERVER_LIBPCIACCESS
-ivtvHWProbe(struct pci_device *PciInfo, char *device, char **namep)
+ivtvHWProbe(struct pci_device *PciInfo, const char *device, char **namep)
 #else
-ivtvHWProbe(pciVideoPtr pPci, char *device, char **namep)
+ivtvHWProbe(pciVideoPtr pPci, const char *device, char **namep)
 #endif
 {
 int fd;
@@ -372,9 +372,9 @@
 
 Bool
 #if XSERVER_LIBPCIACCESS
-ivtvHWInit(ScrnInfoPtr pScrn, struct pci_device *PciInfo, char *device)
+ivtvHWInit(ScrnInfoPtr pScrn, struct pci_device *PciInfo, const char *device)
 #else
-ivtvHWInit(ScrnInfoPtr pScrn, pciVideoPtr pPci, char *device)
+ivtvHWInit(ScrnInfoPtr pScrn, pciVideoPtr pPci, const char *device)
 #endif
 {
 TRACE_ENTER("Init");
@@ -464,7 +464,7 @@
 int virtX = pScrn->display->virtualX;
 int virtY = pScrn->display->virtualY;
 struct fb_var_screeninfo var;
-char **modename;
+const char **modename;
 DisplayModePtr mode, this, last = NULL;
 
 TRACE_ENTER("VerifyModes");
@@ -688,10 +688,9 @@
 /*  */
 /* these can be hooked directly into ScrnInfoRec*/
 
-int
-ivtvHWValidMode(int scrnIndex, DisplayModePtr mode, Bool verbose, int flags)
+ModeStatus
+ivtvHWValidMode(ScrnInfoPtr pScrn, DisplayModePtr mode, Bool verbose, int 
flags)
 {
-ScrnInfoPtr pScrn = xf86Screens[scrnIndex];
 IVTVDevPtr devPtr = IVTVDEVPTR(pScrn);
 struct fb_var_screeninfo var;
 
@@ -701,7 +700,7 @@
 xfree2ivtv_fblayout(pScrn, &devPtr->var);
 var.activate = FB_ACTIVATE_TEST;
 if (0 != ioctl(devPtr->fd, FBIOPUT_VSCREENINFO, (void *)(&devPtr->var))) {
-   xf86DrvMsg(scrnIndex, X_ERROR,
+   xf86DrvMsg(pScrn->scrnIndex, X_ERROR,
"ValidMode: FBIOPUT_VSCREENINFO failed (%s)\n", strerror(errno));
return MODE_BAD;
 }
Index: xserver-xorg-video-ivtvdev-salsa/src/ivtv_hw.h
===
--- xserver-xorg-video-ivtvdev-salsa.orig/src/ivtv_hw.h 2025-03-01 
08:38:08.0 +
+++ xserver-xorg-video-ivtvdev-salsa/src/ivtv_hw.h  2025-03-01 
08:39:53.102548048 +
@@ -61,11 +61,11 @@
 #endif
 
 #if XSERVER_LIBPCIACCESS
-Bool ivtvHWProbe(struct pci_device *PciInfo, char *device, char **namep);
-Bool ivtvHWInit(ScrnInfoPtr pScrn, struct pci_device *PciInfo, char *device);
+Bool ivtvHWProbe(struct pci_device *PciInfo, const char *device, char **namep);
+Bool ivtvHWInit(ScrnInfoPtr pScrn, struct pci_device *PciInfo, const char 
*device);
 #else
 Bool ivtvHWProbe(pciVideoPtr pPci, char *device, char **namep);
-Bool ivtvHWInit(ScrnInfoPtr pScrn, pciVideoPtr pPci, char *device);
+Bool ivtvHWInit(ScrnInfoPtr pScrn, pciVideoPtr pPci, const char *device);
 #endif
 char *ivtvHWGetName(ScrnInfoPtr pScrn);
 int ivtvHWGetDepth(ScrnInfoPtr pScrn, int *fbbpp);
@@ -86,7 +86,7 @@
 void ivtvHWRestore(ScrnInfoPtr pScrn);
 void ivtvHWLoadPalette(ScrnInfoPtr pScrn, int numColors, int *indices,
 LOCO * colors, VisualPtr pVisual);
-int ivtvHWValidMode(int scrnIndex, DisplayModePtr mode, Bool verbose, int 
flags);
+ModeStatus ivtvHWValidMode(ScrnInfoPtr pScrn, DisplayModePtr mode, Bool 
verbose, int flags);
 Bool ivtvHWSwitchMode(SWITCH_MODE_ARGS_DECL);
 void ivtvHWAdjustFrame(A

Bug#1099161: apt: allow to set Acquire::https::CAInfo and friends per repo in .sources

2025-03-01 Thread Julian Andres Klode

On March 1, 2025 12:46:09 AM GMT+01:00, Christoph Anton Mitterer 
 wrote:
>Now I know that I can set Acquire::https::CAInfo and friends, but it
>seems only globally?!

My understanding is that all options can be set per hostname, e.g.

Acquire::https::example.com::CaInfo

>It would however make sense to set these on a per-repo basis.

That could also make sense for ease of use. It's best if you don't need to 
touch apt.conf or apt_preferences for pinning for that matter.

sent from my phone, excuse the brevity, if any

Bug#1099171: Upgrade Debian Policy Standards Version to latest 4.7.2

2025-03-01 Thread c . buhtz


Package: backintime
Version: 1.5.3-1

Hello,
I checked the difference between 4.7.0 and 4.7.2 and can't find 
something relevant to backintime. So it seems the version can be 
upgraded.


btw: I am preparing the 1.5.4 release at upstream until 1th April to get 
included in upcoming Debian 13.


Regards,
Christian

Bug#1098995: notmuch: test suite regressions with fixed GnuPG

2025-03-01 Thread David Bremner

Daniel Kahn Gillmor  writes:

>
> Please see the attached patch.
>
>--dkg
>
> From 6d7f5791830c6d3e7607812116e63c866f3c587c Mon Sep 17 00:00:00 2001
> From: Daniel Kahn Gillmor 
> Date: Thu, 27 Feb 2025 13:14:08 -0500
> Subject: [PATCH] Accept "key-missing" from a signature from a revoked key
>
> We have traditionally expected a signature to show up as "revoked"
> when the signing key is revoked.  However, GnuPG's recent fix to avoid
> a denial of service against legitimate signatures appears to have
> changed the status of signature verification from keys which happen to
> have been revoked.
>
> See https://bugs.debian.org/1098995 and https://dev.gnupg.org/T7547
>
> This change makes the test suite a little bit less brittle while we
> look for a resolution from upstream.  It should probably also be
> backported to debian unstable unless a notmuch release to unstable is
> imminent.
>
> Signed-off-by: Daniel Kahn Gillmor 
> ---
>  test/T350-crypto.sh | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/test/T350-crypto.sh b/test/T350-crypto.sh
> index 27c0e86d..712a0c07 100755
> --- a/test/T350-crypto.sh
> +++ b/test/T350-crypto.sh
> @@ -453,6 +453,7 @@ y
>  | gpg --no-tty --quiet --import
>  output=$(notmuch show --format=json --verify subject:"test signed message 
> 001" \
>  | notmuch_json_show_sanitize \
> +| sed -e 's/"key-\(revoked\|missing\)"/"key-revoked"/g' \
>  | sed -e 's|"created": [1234567890]*|"created": 946728000|')
>  expected='[[[{"id": "X",
>   "match": true,
> -- 
> 2.47.2

I have applied this patch to the release and master branches.  It will
be part of 0.39~rc2 or 0.39.

Bug#1099173: Evolution 3.55 keeps forgetting UI settings

2025-03-01 Thread Stephan Verbücheln

Package: evolution
Version: 3.55.2-1

Evolution keeps forgetting the settings for the switcher icons (mail,
contacts, calendar, tasks and memos).

Steps to reproduce:
1. Menu View -> Switcher Appearance -> “Icons only”
2. Switcher now has icons only.
3. Close Evolution and launch it again.
4. Switcher has icons and text again.

Regards


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

Bug#1081434: dpkg-source: should refuse to apply indented diffs, or at least give a warning

2025-03-01 Thread Tj

Package: dpkg-dev
Followup-For: Bug #1081434
X-Debbugs-Cc: tj.iam...@proton.me

Excuse me for butting in; I'm not sure if this could be a solution or
not. I just proposed a patch in bug #1099170 "dpkg-source: Source/Patch:
fix parsing of patch header" and was pointed to this bug as a possible
duplicate - it is not.

However after working with the code I wonder if there might be an
elegant way to avoid the spawned 'patch' tool mis-reading the header in
this way:

analyze() keeps track of the entire header:

   $patch_header .= "$line\n";
...
  *$self->{analysis}{$destdir}{patchheader} = $patch_header;
  return *$self->{analysis}{$destdir};

apply() and check_apply() both do:

  my $analysis = $self->analyze($destdir, %opts);
  ...
$self->ensure_open('r');

At this point the spawned process is about to be passed its input via
standard input. Could the solution be to simply seek() beyond the header
before spawn() dup's the file descriptor - something like:

  seek($self, length( %{$analysis->{patchheader}} ), 0);

Bug#1099078: dh_numpy3 should emit ABI dependencies only when necessary

2025-03-01 Thread Timo Röhling


Hi Adrian,

On Fri, 28 Feb 2025 00:21:14 +0200 Adrian Bunk  wrote:
dh_numpy3 should do something similar to 
missing-dependency-on-numpy-abi for determining whether or not an ABI 
dependency is necessary.
I have added some detection logic to dh_numpy3 similar to the Lintian 
check, but with a different marker string.



Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1098872: php-nesbot-carbon 2.65.0-1+deb12u1 flagged for acceptance

2025-03-01 Thread Adam D Barratt

package release.debian.org
tags 1098872 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: php-nesbot-carbon
Version: 2.65.0-1+deb12u1

Explanation: fix arbitrary file include issue [CVE-2025-22145]

Bug#1094952: systemtap-client: not installable due to missing dnsutils

2025-03-01 Thread Bastian Germann

I am uploading a NMU to fix this. The changes are in git.

Bug#1099179: komposter: FTBFS on amd64: patch.c:575:11: error: assignment to ‘unsigned int ’ from incompatible pointer type ‘long unsigned int ’ [-Wincompatible-pointer-types]

2025-03-01 Thread Sebastian Ramacher

Source: komposter
Version: 0+git20201216+ds-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-am...@lists.debian.org, sramac...@debian.org
User: debian-am...@lists.debian.org
Usertags: amd64

https://buildd.debian.org/status/fetch.php?pkg=komposter&arch=amd64&ver=0%2Bgit20201216%2Bds-6&stamp=1740663145&raw=0

patch.c:574:42: warning: conversion to ‘int’ from ‘unsigned int’ may change the 
sign of the result [-Wsign-conversion]
  574 |   rf=knob_scale2float(mod[csynth][mi].scale, rf);
  |   ~~~^~
patch.c:575:11: error: assignment to ‘unsigned int *’ from incompatible pointer 
type ‘long unsigned int *’ [-Wincompatible-pointer-types]
  575 |   fptr=(unsigned long*)(&rf);
  |   ^
patch.c:579:41: warning: conversion to ‘int’ from ‘unsigned int’ may change the 
sign of the result [-Wsign-conversion]
  579 |   f=knob_float2scale(mod[csynth][mi].scale, rf);
  |  ~~~^~

Cheers
-- 
Sebastian Ramacher

Bug#1099180: RFP: python-pwdlib -- Modern password hashing for Python

2025-03-01 Thread Mathias Behrle

Package: wnpp
Severity: wishlist

* Package name: python-pwdlib
  Version : 0.2.1
  Upstream Contact: Francois Voron https://github.com/frankie567
* URL : https://github.com/frankie567/pwdlib
* License : MIT
  Programming Lang: Python
  Description : Modern password hashing for Python

From the README:
For years, the de-facto standard to hash passwords was passlib. Unfortunately,
it has not been very active recently and its maintenance status is under
question. Starting Python 3.13, passlib won't work anymore. That's why I
decided to start pwdlib, a password hash helper for the modern Python era.
However, it's not designed to be a complete replacement for passlib, which
supports numerous hashing algorithms and features.

The original passlib project
(https://foss.heptapod.net/python-libs/passlib)
is currently unmaintained s. 
https://foss.heptapod.net/python-libs/passlib/-/issues/187

pwdlib seems to be a vital and maintained project.
Some rdepends of passlib have already switched pwdlib. Tryton will use
it starting from version 7.6.
https://foss.heptapod.net/tryton/tryton/-/merge_requests/2022/commits

S.a. https://github.com/frankie567/pwdlib/discussions/1

-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

Bug#1098053: uudeview C23 compatibility

2025-03-01 Thread Andreas Metzler

On 2025-02-28 Hanno Böck  wrote:
> The relevant prototype issues should now be fixed in the git repo.
> (There are still more #ifdef's with macros that should be removed, but
> they should not prevent compilation with modern compilers.)

Thank you!

> The other C23 issues are tracked here:
> https://github.com/hannob/uudeview/issues/32

> We need to define some C feature macros, but that also causes a
> compatibility issue with hostent (see CI failure). Have to look into
> this later, shouldn't be too hard to fix.

> Call for help: Is anyone here actively using inews? I maintain it due
> to my interest in keeping the uudeview tool alive, yet inews is part of
> it. I've fixed compilation issues, but have currently no easy way to
> test it.

We have always been building uudeview with --enable-inews=/usr/bin/inews
and have not used the included mini-inews in Debian.

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#1099181: linphone: FTBFS: Could not find a package configuration file provided by "ortp"

2025-03-01 Thread Sebastian Ramacher

Source: linphone
Version: 5.2.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=linphone&arch=amd64&ver=5.2.0-5%2Bb3&stamp=1740769868&raw=0

-- Setting install rpath to /usr/lib/x86_64-linux-gnu
-- Could NOT find belcard (missing: belcard_DIR)
CMake Warning at CMakeLists.txt:139 (message):
  Could not find the belcard library!


CMake Error at CMakeLists.txt:149 (find_package):
  Could not find a package configuration file provided by "ortp" with any of
  the following names:

ortpConfig.cmake
ortp-config.cmake

  Add the installation prefix of "ortp" to CMAKE_PREFIX_PATH or set
  "ortp_DIR" to a directory containing one of the above files.  If "ortp"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!

Cheers
-- 
Sebastian Ramacher

Bug#1099074: jinja2 3.1.2-1+deb12u2 flagged for acceptance

2025-03-01 Thread Adam D Barratt

package release.debian.org
tags 1099074 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: jinja2
Version: 3.1.2-1+deb12u2

Explanation: fix arbitrary code execution issues [CVE-2024-56201 CVE-2024-56326]

Bug#1098873: tzdata 2025a-0+deb12u1 flagged for acceptance

2025-03-01 Thread Adam D Barratt

package release.debian.org
tags 1098873 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: tzdata
Version: 2025a-0+deb12u1

Explanation: new upstream release; update data for Paraguay; update leap second 
information

1 2 3 >

1 - 100 of 271 matches

Mail list logo