Hi all,
Ole Streicher, on 2025-07-14:
> Am 14.07.25 um 07:48 schrieb Lucas Nussbaum:
> > In #1109178 (emmax: fails to dist-upgrade from bookworm (related to
> > libatlas3-base removal)), Etienne added a Breaks to libatlas3-base to
> > work-around the issue.
> >
> > Maybe the break could be set in
Hi Lucas, Etienne,
Am 14.07.25 um 07:48 schrieb Lucas Nussbaum:
In #1109178 (emmax: fails to dist-upgrade from bookworm (related to
libatlas3-base removal)), Etienne added a Breaks to libatlas3-base to
work-around the issue.
Maybe the break could be set in libpacke instead.
liblapacke already
On 14/07/2025 14:50, Mathias Gibbens wrote:
On Mon, 14 Jul 2025 11:28:38 +0900 John Crawley wrote:
This bug report has been tagged "patch" but there seems to be no patch
available.
I tagged with patch because I think the fix is just a one line change
in the postinst script:
diff --git a
Hi,
A MWE is:
PKG=pyhoca-cli; mmdebstrap --chrooted-customize-hook="set -x ; apt -y install
$PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list && apt update &&
apt dist-upgrade -y" bookworm /dev/null
Lucas
On 13/07/25 at 14:55 +0200, Ole Streicher wrote:
> Control: tags -1 moreinfo
>
> Hi Lucas,
>
> Am 13.07.25 um 10:17 schrieb Lucas Nussbaum:
> > Broken liblapacke:amd64 Breaks on libatlas3-base:amd64 < 3.10.3-13 @ii mK >
> > (< 3.10.3-14)
> >Considering libatlas3-base:amd64 1 as a solution to
On Mon, 14 Jul 2025 11:28:38 +0900 John Crawley wrote:
> This bug report has been tagged "patch" but there seems to be no patch
> available.
I tagged with patch because I think the fix is just a one line change
in the postinst script:
> diff --git a/debian/firmware-b43-installer.postinst
> b
Hi Santiago,
Le 14/07/2025 à 02:36, Santiago Vila a écrit :
On Sun, Jul 13, 2025 at 08:03:24AM +0200, Pierre Gruet wrote:
However, my feeling is that the bug is not RC, since it shows up only in
VMs: in practice it does not affect the autobuilders nor the developers on
their individual machines
This bug report has been tagged "patch" but there seems to be no patch
available.
--
John
On Sun, Jul 13, 2025 at 08:03:24AM +0200, Pierre Gruet wrote:
> However, my feeling is that the bug is not RC, since it shows up only in
> VMs: in practice it does not affect the autobuilders nor the developers on
> their individual machines. What do you think?
Those seem weak reasons to me.
We d
Your message dated Sun, 13 Jul 2025 22:49:03 +
with message-id
and subject line Bug#1051785: fixed in gdm3 48.0-2
has caused the Debian Bug report #1051785,
regarding gdm3 won't allow logins when a smartcard/yubikey is plugged
to be marked as done.
This means that you claim that the problem h
Processing control commands:
> tag -1 pending
Bug #1051785 [gdm3] gdm3 won't allow logins when a smartcard/yubikey is plugged
Ignoring request to alter tags of bug #1051785 to the same tags previously set
--
1051785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051785
Debian Bug Tracking S
Processing control commands:
> tag -1 pending
Bug #1051785 [gdm3] gdm3 won't allow logins when a smartcard/yubikey is plugged
Added tag(s) pending.
--
1051785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1051785 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gdm/-/commit/a282369756946506a53b1ec55f8a2009af7c
Control: tag -1 pending
Hello,
Bug #1051785 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gdm/-/commit/dc6ab49be2bfdd730a8a7176020217cafc1d
Processing commands for cont...@bugs.debian.org:
> found 1108377 bsd-mailx/8.1.2-0.20220412cvs-1
Bug #1108377 {Done: Andrew Bower } [bsd-mailx] bsd-mailx:
allow TMPDIR env to override /tmp
Marked as found in versions bsd-mailx/8.1.2-0.20220412cvs-1.
> thanks
Stopping processing here.
Please cont
Processing commands for cont...@bugs.debian.org:
> severity 1109139 normal
Bug #1109139 [calamares-settings-debian] calamares-settings-debian: Update
GNOME pinned applications
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Sun, 13 Jul 2025 22:59:50 +0200
with message-id
and subject line Seems fixed elsewhere
has caused the Debian Bug report #1108164,
regarding fails to start in trixie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Sun, 13 Jul 2025 20:49:06 +
with message-id
and subject line Bug#1109052: fixed in bmake 20200710-17
has caused the Debian Bug report #1109052,
regarding bmake: autopkgtest regression: illegal argument to -j -- must be
positive integer!
to be marked as done.
This means tha
On Sun, Jul 13, 2025 at 04:33:04AM +, Luke Yasuda wrote:
> Package: tika
> Version: 1.22-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> Hello,
>
> This package fails to build from source and thus should be removed from
Hi
Adding RT and Python team to this bug because I feel this is actually a
bug else where (namely `py3clean` / `dh-python`). With that said, I do
not think we can fix this properly for `trixie` and instead should rely
on the work around of having `libexpat1` Pre-Depends on `libc` as Lucas
su
Processing commands for cont...@bugs.debian.org:
> found 1109199 2.42.12+dfsg-4
Bug #1109199 [libgdk-pixbuf-2.0-0] libgdk-pixbuf-2.0-0: regression: gthumb
fails to launch after fixing CVE-2025-7345
Marked as found in versions gdk-pixbuf/2.42.12+dfsg-4.
> thanks
Stopping processing here.
Please c
Processing commands for cont...@bugs.debian.org:
> reassign 1109199 libgdk-pixbuf-2.0-0
Bug #1109199 [libgdk-pixbuf2.0-0] libgdk-pixbuf2.0-bin: gthumb fails to launch
Bug reassigned from package 'libgdk-pixbuf2.0-0' to 'libgdk-pixbuf-2.0-0'.
Ignoring request to alter found versions of bug #1109199
Your message dated Sun, 13 Jul 2025 18:34:00 +
with message-id
and subject line Bug#1108377: fixed in bsd-mailx 8.1.2-0.20220412cvs-1.1
has caused the Debian Bug report #1108377,
regarding bsd-mailx: allow TMPDIR env to override /tmp
to be marked as done.
This means that you claim that the pr
Your message dated Sun, 13 Jul 2025 18:19:17 +
with message-id
and subject line Bug#1109161: fixed in puppet-module-puppetlabs-firewall 8.0.0-4
has caused the Debian Bug report #1109161,
regarding Compiling crashes when providers are needed, after a puppetserver
reload
to be marked as done.
Your message dated Sun, 13 Jul 2025 17:49:07 +
with message-id
and subject line Bug#1108944: fixed in ganeti 3.1.0~rc2-3
has caused the Debian Bug report #1108944,
regarding ganeti-3.1: upgrading from ganeti-3.0 (bookworm) fails -- diversion
clash
to be marked as done.
This means that you cl
Processing commands for cont...@bugs.debian.org:
> found 1109161 8.0.0-3
Bug #1109161 [puppet-module-puppetlabs-firewall] Compiling crashes when
providers are needed, after a puppetserver reload
Marked as found in versions puppet-module-puppetlabs-firewall/8.0.0-3.
> thanks
Stopping processing he
Processing commands for cont...@bugs.debian.org:
> severity 1109161 serious
Bug #1109161 [src:puppetserver] Compiling crashes when providers are needed,
after a puppetserver reload
Severity set to 'serious' from 'important'
> reassign 1109161 puppet-module-puppetlabs-firewall
Bug #1109161 [src:pu
Your message dated Sun, 13 Jul 2025 16:34:13 +
with message-id
and subject line Bug#1102611: fixed in django-pipeline 4.0.0-4
has caused the Debian Bug report #1102611,
regarding django-pipeline: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dea
Control: tag -1 pending
Hello,
Bug #1102611 in django-pipeline reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/django-pipeline/-/commit/f19
Processing control commands:
> tag -1 pending
Bug #1102611 [src:django-pipeline] django-pipeline: autopkgtest failure
Added tag(s) pending.
--
1102611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sun, 13 Jul 2025 16:05:45 +
with message-id
and subject line Bug#1108799: fixed in py3dns 4.0.2-4
has caused the Debian Bug report #1108799,
regarding py3dns: autopkgtest regression: '96.7.128.186' != '93.184.215.14'
to be marked as done.
This means that you claim that the
Hi,
On Thu, 10 Jul 2025, at 14:56, Paul Gevers wrote:
> Your package has an autopkgtest, great. However, it fails since January
> 2025. Can you please investigate the situation and fix it? I copied some
> of the output at the bottom of this report.
Thanks for reporting this. I understand this h
Control: tag -1 pending
Hello,
Bug #1108799 in py3dns reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/packages/py3dns/-/commit/8ecad09e26d0f42ab29b0
Processing control commands:
> tag -1 pending
Bug #1108799 [src:py3dns] py3dns: autopkgtest regression: '96.7.128.186' !=
'93.184.215.14'
Added tag(s) pending.
--
1108799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Package: lxqt-wayland-session
Version: 0.1.1-2
Followup-For: Bug #1109153
X-Debbugs-Cc: mode...@gmail.com
Dear Don Xu,
When I first saw that LXQt had Wayland support, I was excited it felt like a
big step forward
for the desktop. But that excitement quickly turned into disappointment when
the
On Thu, Feb 06, 2025 at 05:20:07PM +0100, Eduard Bloch wrote:
> > Shouldn't this package have a corresponding -dkms package?
>
> Maybe, but IMHO there is not much public interest in that kernel module
> except for very specialized Live Linux distros, i.e. I cannot remember
> anyone reporting this
Your message dated Sun, 13 Jul 2025 13:19:01 +
with message-id
and subject line Bug#1074831: fixed in awesfx 0.5.2-1.2
has caused the Debian Bug report #1074831,
regarding awesfx: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Processing commands for cont...@bugs.debian.org:
> forwarded 1109199 https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/262
Bug #1109199 [libgdk-pixbuf2.0-0] libgdk-pixbuf2.0-bin: gthumb fails to launch
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/262'.
> th
Your message dated Sun, 13 Jul 2025 14:08:35 +0100
with message-id
and subject line Re: Bug#1108968: bitstruct: autopkgtest regression: invalid
command 'test'
has caused the Debian Bug report #1108968,
regarding bitstruct: autopkgtest regression: invalid command 'test'
to be marked as done.
This
Processing control commands:
> reassign -1 libgdk-pixbuf2.0-0
Bug #1109199 [libgdk-pixbuf2.0-bin] libgdk-pixbuf2.0-bin: gthumb fails to launch
Bug reassigned from package 'libgdk-pixbuf2.0-bin' to 'libgdk-pixbuf2.0-0'.
No longer marked as found in versions gdk-pixbuf/2.42.12+dfsg-4.
Ignoring reque
Your message dated Sun, 13 Jul 2025 14:04:04 +0100
with message-id
and subject line Re: Bug#1061758: python-xmlrunner ftbfs with Python 3.12 as
default
has caused the Debian Bug report #1061758,
regarding python-xmlrunner ftbfs with Python 3.12 as default
to be marked as done.
This means that yo
Processing control commands:
> tags -1 moreinfo
Bug #1109179 [source-extractor] source-extractor: fails to dist-upgrade from
bookworm (related to libatlas3-base removal)
Added tag(s) moreinfo.
--
1109179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109179
Debian Bug Tracking System
Conta
Processing control commands:
> tags -1 moreinfo
Bug #1109176 [psfex] psfex: fails to dist-upgrade from bookworm (related to
libatlas3-base removal)
Added tag(s) moreinfo.
--
1109176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109176
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> tags -1 moreinfo
Bug #1109177 [scamp] scamp: fails to dist-upgrade from bookworm (related to
libatlas3-base removal)
Added tag(s) moreinfo.
--
1109177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109177
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Control: tags -1 moreinfo
Hi Lucas,
Am 13.07.25 um 10:17 schrieb Lucas Nussbaum:
Broken liblapacke:amd64 Breaks on libatlas3-base:amd64 < 3.10.3-13 @ii mK > (<
3.10.3-14)
Considering libatlas3-base:amd64 1 as a solution to liblapacke:amd64 0
Holding Back liblapacke:amd64 rather than chan
Hello,
On Sun, Jul 13, 2025 at 2:17 PM EiPi Fun wrote:
> Cause lxqt is designed to be independent of wayland compositors or
> x11 window managers, it may not be encouraged to ship lxqt with a
> default wayland compositor.
The whole LXQt desktop are also independent of window manager, but
Debian
Actually the thing reported is designed to be at the moment.
For users who do not install a wayland compositor, the wayland session
of lxqt will crash.
There are two necessary configurations in the
$HOME/.config/lxqt/session.
```
compositor=labwc
lock_command_wayland=swaylock
```
the compositor
Your message dated Sun, 13 Jul 2025 12:04:19 +
with message-id
and subject line Bug#1109178: fixed in emmax 0~beta.20100307-6
has caused the Debian Bug report #1109178,
regarding emmax: fails to dist-upgrade from bookworm (related to libatlas3-base
removal)
to be marked as done.
This means t
Processing control commands:
> tag -1 pending
Bug #1109178 [emmax] emmax: fails to dist-upgrade from bookworm (related to
libatlas3-base removal)
Added tag(s) pending.
--
1109178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109178
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #1109178 in emmax reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/emmax/-/commit/048e41f7e1438cd7a8133b822f646ab686b
Package: wpasupplicant-udeb (2:2.10-24)
Severity: grave
Justification: renders package unusable for users who try to connect to wifi
using WPA3-Personal authentication
Usertags: Intel Core Ultra i9-185H CPU (amd64), Intel Wifi AX211 chipset
Boot method: USB
Image version: debian-trixie-DI-rc2-am
Hi Pierre, Hi Santiago,
Pierre Gruet, on 2025-07-13:
> However, my feeling is that the bug is not RC, since it shows up only in
> VMs: in practice it does not affect the autobuilders nor the developers on
> their individual machines. What do you think?
Thank you for your input, I have been trying
Package: source-extractor
Version: 2.28.2+ds-1
Severity: serious
Hi,
The following fails:
- In bookworm, install source-extractor
- dist-upgrade to trixie
I would expect source-extractor to be upgraded, but it is not.
MWE:
PKG=source-extractor; mmdebstrap --chrooted-customize-hook="set -x ; apt
Package: emmax
Version: 0~beta.20100307-5
Severity: serious
Hi,
The following fails:
- In bookworm, install emmax
- dist-upgrade to trixie
I would expect emmax to be upgraded, but it is not.
MWE:
PKG=emmax; mmdebstrap --chrooted-customize-hook="set -x ; apt -y install $PKG
&& sed -e s/bookworm
Package: psfex
Version: 3.24.2-2
Severity: serious
Hi,
The following fails:
- In bookworm, install psfex
- dist-upgrade to trixie
I would expect psfex to be upgraded, but it is not.
MWE:
PKG=psfex; mmdebstrap --chrooted-customize-hook="set -x ; apt -y install $PKG
&& sed -e s/bookworm/trixie/
Package: scamp
Version: 2.14.0-1
Severity: serious
Hi,
The following fails:
- In bookworm, install scamp
- dist-upgrade to trixie
I would expect scamp to be upgraded, but it is not.
MWE:
PKG=scamp; mmdebstrap --chrooted-customize-hook="set -x ; apt -y install $PKG
&& sed -e s/bookworm/trixie/
Package: libfst-dev
Version: 1.7.9-5
Severity: serious
While testing upgrades from bookworm to trixie, I ran into the following
problem.
If I:
- install libfst-dev in bookworm
- upgrade to trixie (apt update && apt dist-upgrade)
Then libfst-dev is not upgraded.
MWE:
mmdebstrap --chrooted-customiz
57 matches
Mail list logo
