Your message dated Fri, 04 Apr 2025 05:05:15 +
with message-id
and subject line Bug#1101970: fixed in workrave 1.10.53-2
has caused the Debian Bug report #1101970,
regarding workrave: missing Replaces for workrave-data
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> severity -1 normal
Bug #1101974 [firmware-atheros] [firmware-atheros] firmware: failed to load
ath9k_htc/htc_9271-1.4.0.fw (-2)
Severity set to 'normal' from 'grave'
> tags -1 + moreinfo
Bug #1101974 [firmware-atheros] [firmware-atheros] firmware: failed to load
at
Your message dated Thu, 03 Apr 2025 23:05:59 +
with message-id
and subject line Bug#1057563: fixed in gdb-doc 16.2-1
has caused the Debian Bug report #1057563,
regarding gdb-doc: FTBFS: /usr/bin/install: cannot stat
'../../../gdb/doc/stabs': No such file or directory
to be marked as done.
Th
Your message dated Fri, 04 Apr 2025 01:05:03 +
with message-id
and subject line Bug#1101114: fixed in inn2 2.7.3~rc1-1
has caused the Debian Bug report #1101114,
regarding inn2 and sm have an undeclared file conflict on
/usr/share/man/man1/sm.1.gz
to be marked as done.
This means that you cl
Processing control commands:
> block 1101756 by -1
Bug #1101756 [libbson-xs-perl] Should libbson-xs-perl be shipped in trixie?
1101756 was not blocked by any bugs.
1101756 was not blocking any bugs.
Added blocking bug(s) of 1101756: 1102011
--
1101756: https://bugs.debian.org/cgi-bin/bugreport.c
Your message dated Thu, 03 Apr 2025 22:06:23 +
with message-id
and subject line Bug#1101853: fixed in libcode-tidyall-perl 0.84~ds-2
has caused the Debian Bug report #1101853,
regarding libcode-tidyall-perl: FTBFS: Failed 1/24 test programs. 4/222
subtests failed.
to be marked as done.
This
Your message dated Thu, 03 Apr 2025 22:49:59 +
with message-id
and subject line Bug#1052376: fixed in lxpanel 0.11.0-1
has caused the Debian Bug report #1052376,
regarding lxpanel: no longer obeys its geometry settings
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 03 Apr 2025 22:50:00 +
with message-id
and subject line Bug#1075243: fixed in lxpanel 0.11.0-1
has caused the Debian Bug report #1075243,
regarding lxpanel: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 03 Apr 2025 22:49:59 +
with message-id
and subject line Bug#855521: fixed in lxpanel 0.11.0-1
has caused the Debian Bug report #855521,
regarding lxpanel: freezes all the desktop environment if started or lauch no
matter desktop are used
to be marked as done.
This mea
Your message dated Thu, 03 Apr 2025 22:19:12 +
with message-id
and subject line Bug#1101968: fixed in booth 1.2-3
has caused the Debian Bug report #1101968,
regarding booth: autopkgtest needs update for new version of crmsh: warning on
stderr
to be marked as done.
This means that you claim t
Your message dated Thu, 03 Apr 2025 22:11:03 +
with message-id
and subject line Bug#1101983: fixed in zigpy-zigate 0.13.2-3
has caused the Debian Bug report #1101983,
regarding zigpy-zigate: rebuild creates empty package
to be marked as done.
This means that you claim that the problem has bee
Your message dated Thu, 03 Apr 2025 22:09:08 +
with message-id
and subject line Bug#1089017: fixed in python-beartype 0.20.2-1
has caused the Debian Bug report #1089017,
regarding python-beartype: autopkgtest failure with Python 3.13
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 03 Apr 2025 21:46:06 +
with message-id
and subject line Bug#1101344: fixed in gitaly 16.11.6+ds1-4
has caused the Debian Bug report #1101344,
regarding gitaly has an undeclared file conflict with
golang-gitlab-gitlab-org-gitaly-dev/unstable
to be marked as done.
This
Thanks for the report,
On 4/1/25 18:34, Santiago Vila wrote:
Package: src:php-nesbot-carbon
Version: 2.72.6-2
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
Note 1: If this was a random package I would use
Processing commands for cont...@bugs.debian.org:
> severity 1101844 important
Bug #1101844 [src:php-nesbot-carbon] php-nesbot-carbon: FTBFS: tests fail on
31th March
Severity set to 'important' from 'serious'
> tags 1101844 + confirmed upstream
Bug #1101844 [src:php-nesbot-carbon] php-nesbot-carb
Processing control commands:
> tag -1 pending
Bug #1101853 [src:libcode-tidyall-perl] libcode-tidyall-perl: FTBFS: Failed
1/24 test programs. 4/222 subtests failed.
Added tag(s) pending.
--
1101853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101853
Debian Bug Tracking System
Contact ow.
Control: tag -1 pending
Hello,
Bug #1101853 in libcode-tidyall-perl 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/perl-team/modules/packages/libcode-tidyall-p
On Sat, Mar 29, 2025 at 04:33:27PM -0400, Dave Vasilevsky wrote:
user debian-rele...@lists.debian.org
usertag 1101258 + bsp-2025-03-ca-montreal
thank you
Upstream seems to be aware of this:
https://github.com/MagicStack/uvloop/issues/637
This looks unrelated.
--
WBR, wRAR
signature.asc
Desc
I am uploading a NMU with the attached changes to fix this issue.diff -Nru lxpanel-0.10.1/debian/changelog lxpanel-0.10.1/debian/changelog
--- lxpanel-0.10.1/debian/changelog 2023-09-16 02:17:33.0 +
+++ lxpanel-0.10.1/debian/changelog 2025-04-03 20:00:17.0 +
@@ -1,3
Your message dated Thu, 03 Apr 2025 20:51:23 +
with message-id
and subject line Bug#1075243: fixed in lxpanel 0.10.1-4.1
has caused the Debian Bug report #1075243,
regarding lxpanel: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
> Wiadomość napisana przez Ivan Linty w dniu 2 kwi 2025, o
> godz. 23:39:
>
> Package: snapd
> Version: 2.67-1
> Severity: serious
> X-Debbugs-Cc: ilint...@gmail.com
>
> No fonts in gtk-dialogs in walc snap application, Android studio snap
> application fail to start: this happens after I h
Source: php-horde-imp
Version: 6.2.27-3.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 6.2.27-3
Hi,
The following vulnerability was published for php-horde-imp.
CVE-2025-30349[0]:
| Horde IMP th
Processing control commands:
> found -1 6.2.27-3
Bug #1102003 [src:php-horde-imp] php-horde-imp: CVE-2025-30349
Marked as found in versions php-horde-imp/6.2.27-3.
--
1102003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: trafficserver
Version: 9.2.5+ds-1
Severity: grave
Tags: upstream security
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 9.2.5+ds-0+deb12u1
Hi,
The following vulnerability was published for trafficserver.
CVE-2024-53868[0]:
| Apache Traffic Server allows request
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:mat2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Settin
Hi xuser,
On Thu, Apr 03, 2025 at 05:53:36PM +, xuser wrote:
> I think asterisk should be added to debian trixie.
Asterisk is not likeley to be in trixie because of a lack of resources for
handling the large amount of security response work it seems to generate
(or has generated in the past a
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:upx-ucl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Set
Source: esys-particle
Version: 2.3.5+dfsg2-8
Severity: serious
Tags: ftbfs
Hi Maintainer
When built with Python 3.13 only, esys-particle builds successfully,
but then the resulting package does not seem to be functioning
correctly and the autopkgtests time out (see #946206).
Comparing the binary
Your message dated Thu, 03 Apr 2025 16:20:04 +
with message-id
and subject line Bug#1094073: fixed in tupi 0.2+git08-6
has caused the Debian Bug report #1094073,
regarding tupi: FTBFS: make[2]: *** No targets specified and no makefile found.
Stop.
to be marked as done.
This means that you c
Processing control commands:
> severity -1 serious
Bug #1101824 [maven-plugin-tools] Maven plugins that use Javadoc-based Mojos
FTBFS
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #1101824 [maven-plugin-tools] Maven plugins that use Javadoc-based Mojos
FTBFS
Added tag(s) patch.
[Jeremy Bícha, 2025-04-03]
> It might be the debian/rules part of
> https://salsa.debian.org/homeassistant-team/deps/zigpy-zigate/-/commit/45728ada18
or instead of PYBUILD_AFTER_INSTALL use debian/python3-zigpy-zigate.pyremove
file
with each directory to remove in a separate line.
That said, I d
Processing control commands:
> affects -1 src:crmsh src:pacemaker
Bug #1101968 [src:booth] booth: autopkgtest needs update for new version of
crmsh: warning on stderr
Added indication that 1101968 affects src:crmsh and src:pacemaker
--
1101968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Control: tags -1 - upstream
I'm removing the "upstream" tag, because at
https://github.com/kislyuk/argcomplete/issues/491#issuecomment-2774459991
the upstream author says:
Argcomplete does not activate global completion by default and does
not recommend that distributions activate it by d
Processing control commands:
> tags -1 - upstream
Bug #1101675 [python3-argcomplete] python3-argcomplete: breaks zsh completions
Removed tag(s) upstream.
--
1101675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Thu, Apr 3, 2025 at 10:46 AM Piotr Ozarowski wrote:
> That said, I don't see a reason to add it or PYBUILD_AFTER_INSTALL at
> all. debian and build directories are not installed into dist-paclages
> in my sbuild env.
Yes, my preference is to remove the entire export
PYBUILD_AFTER_INSTALL secti
Processing control commands:
> severity -1 serious
Bug #1101729 [src:r-cran-rcppparallel] r-cran-rcppparallel: FTBFS can't parse
dependency libtbb12 (>= ii
Severity set to 'serious' from 'minor'
--
1101729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101729
Debian Bug Tracking System
Con
Your message dated Thu, 03 Apr 2025 14:37:37 +
with message-id
and subject line Bug#1099426: fixed in r-cran-rmpfr 1.0-0-2
has caused the Debian Bug report #1099426,
regarding r-cran-rmpfr FTBFS on 32-bit
to be marked as done.
This means that you claim that the problem has been dealt with.
If
It might be the debian/rules part of
https://salsa.debian.org/homeassistant-team/deps/zigpy-zigate/-/commit/45728ada18
that needs to be reverted.
Thank you,
Jeremy Bícha
Source: zigpy-zigate
Version: 0.13.2-2
Severity: serious
X-Debbugs-CC: edw...@4angle.com
If zigpy-zigate is rebuilt, this is the only files it installs:
drwxr-xr-x root/root 0 ./
drwxr-xr-x root/root 0 ./usr/
drwxr-xr-x root/root 0 ./usr/lib/
drwxr-xr-x root/root 0
Your message dated Thu, 03 Apr 2025 12:19:22 +
with message-id
and subject line Bug#1085045: fixed in cfortran 20210827-1.1
has caused the Debian Bug report #1085045,
regarding cfortran: trying to overwrite '/usr/include/cfortran.h', which is
also in package libcfitsio-dev:amd64 4.5.0-2
to be
Your message dated Thu, 03 Apr 2025 12:06:17 +
with message-id
and subject line Bug#1069515: fixed in eclib 20250122-2
has caused the Debian Bug report #1069515,
regarding eclib: FTBFS on armhf: dh_auto_test: error: make -j4 check
"TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
Package: wine64
Severity: grave
Version: 10.0~rc2~repack-3
Affects: dxvk
Quack,
In preparing a new version of dxvk I noticed the autopkgtest failing.
Currently the only changes on our side is a repack and in the test dxvk
is not even ran yet since we first need to create a prefix and that
fa
Source: booth
Version: 1.2-2
Severity: serious
X-Debbugs-CC: cr...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:crmsh src:pacemaker
Dear maintainer(s),
With a recent upload of crmsh the autopkgtest of booth fails in testing
On Wed, Apr 02, 2025 at 06:38:25PM +, Stefano Rivera wrote:
> Hi Josh (2025.04.02_17:56:48_+)
> > As you said, the TC or the project cannot *require* that a maintainer do
> > work they've objected to. However, I think it's reasonable for a
> > maintainer to say "OK, fine, this isn't the out
On Thu, 3 Apr 2025 08:24:46 +0200 Helmut Grohne
wrote:
> Package: systemd-resolved
> Version: 257.4-9
> Severity: serious
> User: helm...@debian.org
> Usertags: dep17p1
> Control: affects -1 + systemd
>
> Dear systemd maintainers,
>
> thanks for reintroducing systemd-resolved. I'm not sure why t
Your message dated Thu, 03 Apr 2025 10:19:35 +
with message-id
and subject line Bug#1100824: fixed in selinux-python 3.8.1-2
has caused the Debian Bug report #1100824,
regarding policycoreutils-dev misses Breaks+Replaces for
policycoreutils-gui/bookworm
to be marked as done.
This means that
Control: tag -1 pending
Hello,
Bug #1101965 in systemd 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/systemd-team/systemd/-/commit/b9d337abd9144c70ce8370d9261
Your message dated Thu, 03 Apr 2025 10:07:03 +
with message-id
and subject line Bug#1100302: fixed in ros2-colcon-python-setup-py 0.2.9-2
has caused the Debian Bug report #1100302,
regarding ros2-colcon-python-setup-py: FTBFS: ImportError: cannot import name
'setup' from 'setuptools' (unknown
Processing control commands:
> severity -1 serious
Bug #946206 [src:esys-particle] esys-particle: autopkgtest times out when
module import fails
Severity set to 'serious' from 'important'
--
946206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946206
Debian Bug Tracking System
Contact ow..
Processing control commands:
> tag -1 pending
Bug #1100302 [src:ros2-colcon-python-setup-py] ros2-colcon-python-setup-py:
FTBFS: ImportError: cannot import name 'setup' from 'setuptools' (unknown
location)
Added tag(s) pending.
--
1100302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100
Control: tag -1 pending
Hello,
Bug #1100302 in ros2-colcon-python-setup-py 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/robotics-team/ros2-colcon-python-set
Processing commands for cont...@bugs.debian.org:
> severity 1099221 normal
Bug #1099221 [src:cupt] cupt: FTBFS: Failed test 'error message is right'
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1099221: https://bugs.debia
severity 1099221 normal
thanks
I can build the package again. Maybe some build-dependency got fixed,
but I don't know which one. Please allow me to keep this open while
I still investigate.
Thanks.
Processing control commands:
> reopen -1
Bug #1101729 {Done: Bastian Germann }
[src:r-cran-rcppparallel] r-cran-rcppparallel: FTBFS can't parse dependency
libtbb12 (>= ii
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need
Your message dated Thu, 3 Apr 2025 10:26:21 +0100
with message-id
and subject line pydiscovergy builds successfully with sbuild unshare
has caused the Debian Bug report #1099266,
regarding pydiscovergy: FTBFS: E pydiscovergy.error.HTTPError: Request failed:
RESPX: https://api.inexogy.com/public
Your message dated Thu, 3 Apr 2025 10:25:12 +0100
with message-id
and subject line pyecoforest builds successfully with sbuild unshare
has caused the Debian Bug report #1099268,
regarding pyecoforest: FTBFS: E respx.models.AllMockedAssertionError: RESPX:
http://127.0.0.1/recepcion_datos_4.cgi')
Control: tags -1 + patch
I asked on #debian-ruby, and was told that File.exists? was removed in
ruby 3.2, and that File.exist? should be used instead.
The following patch got the package building again:
--- tupi-0.2+git08.orig/configure.rb
+++ tupi-0.2+git08/configure.rb
@@ -180,7 +180,7 @@ _EOH
Control: reopen -1
Hi Bastian
While adjusting the version of the onetbb would avoid the FTBFS in
r-cran-rcppparallel right now, if onetbb ever gets an update in
stable, a backport, a +really upload, or an epoch, then
r-cran-rcppparallel will FTBFS again.
This really needs to be fixed in r-cran-r
Package: node-blueprintjs-core
Version: 4.17.8~git20230417213433.6dab069+ds1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + node-blueprintjs-colors
Both node-blueprintjs-core from trixie and sid and
node-blueprintjs-colors version 5.0.0~alpha.0+ds
Processing commands for cont...@bugs.debian.org:
> tags 1075939 + sid trixie
Bug #1075939 {Done: Bastian Germann } [python3-pyinotify]
python3-pyinotify missing runtime dependency
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
107593
Package: workrave
Version: 1.10.51.1-4
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + workrave-data
Hi,
two files were moved from workrave-data to workrave in version
1.10.51.1-4 (according to its d/changelog):
* /usr/share/gir-1.0/Wor
Processing control commands:
> tags -1 + patch
Bug #1094073 [src:tupi] tupi: FTBFS: make[2]: *** No targets specified and no
makefile found. Stop.
Added tag(s) patch.
--
1094073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094073
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> affects -1 + workrave-data
Bug #1101970 [workrave] workrave: missing Replaces for workrave-data
Added indication that 1101970 affects workrave-data
--
1101970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101970
Debian Bug Tracking System
Contact ow...@bugs.d
Processing control commands:
> affects -1 + node-blueprintjs-colors
Bug #1101969 [node-blueprintjs-core] node-blueprintjs-core overwrites
node-blueprintjs-colors
Added indication that 1101969 affects node-blueprintjs-colors
--
1101969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101969
D
I had a look, and the problem is that configure.rb is failing to create
makefiles, breaking the build completely.
This is the relevant failure message:
* Checking for Libav... * Configure failed. error was: undefined method
`exists?' for class File
# force qmake-generated Makefiles to respect
Hi,
Please try again after installing python3-zombie-imp
Greetings
Alexandre
Your message dated Thu, 03 Apr 2025 07:08:34 +
with message-id
and subject line Bug#1101857: fixed in plastex 3.1-2
has caused the Debian Bug report #1101857,
regarding plastex: FTBFS: autobuilder hangs
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
67 matches
Mail list logo
