Your message dated Wed, 26 Mar 2025 11:50:33 +
with message-id
and subject line Bug#1073665: fixed in libreswan 5.2-2.1
has caused the Debian Bug report #1073665,
regarding libreswan: move aliased files from / to /usr (DEP17)
to be marked as done.
This means that you claim that the problem ha
Processing control commands:
> tags -1 patch
Bug #1095360 [src:nghttp2] nghttp2: FTBFS: Could not import extension
rubydomain.rubydomain
Added tag(s) patch.
--
1095360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Control: tags -1 patch
On Fri, Feb 07, 2025 at 12:12:03PM +, Santiago Vila wrote:
> [...]
> sphinx-build -b html -d manual/doctrees . manual/html
> Running Sphinx v8.1.3
> loading translations [en]... done
>
> Extension error:
> Could not import extension rubydomain.rubydomain (exception: N
Le Wed, 26 Mar 2025 16:45:00 +0100,
Luca Leonardo Scorcia a écrit :
> as another, simpler solution, a two-line fix for the issue has been merged
> upstream:
> https://gitlab.winehq.org/mono/mono/-/commit/cf37d8943fe5118fbfcea86149ad5b7b2d244103
> . I have built a debian backports package for book
Your message dated Wed, 26 Mar 2025 16:20:17 +
with message-id
and subject line Bug#1084765: fixed in python-xknx 3.6.0-1
has caused the Debian Bug report #1084765,
regarding python-xknx: FTBFS (requires network interfaces)
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tags -1 confirmed
Bug #1101232 [src:libmicrohttpd] libmicrohttpd: FTBFS: Wrong URI: `/one%0dtwo',
line: 304
Added tag(s) confirmed.
> forwarded -1 https://bugs.gnunet.org/view.php?id=9664
Bug #1101232 [src:libmicrohttpd] libmicrohttpd: FTBFS: Wrong URI: `/one%0dtwo'
Control: tags -1 confirmed
Control: forwarded -1 https://bugs.gnunet.org/view.php?id=9664
On Tue, Mar 25, 2025 at 12:10:59AM +, Santiago Vila wrote:
> [...]
> ==
>GNU libmicrohttpd 1.0.1: src/testcurl/test-suite.log
>
Hello all,
I'm not very familiar with legal language, but I'd like to point out
some things that seem apparent to me. Correct me if I'm making a
mistake.
On Tue, 25 Mar 2025 10:02:58 +0100 Sylvestre Ledru
wrote:
> The TOU doesnât violate any of the DFSG terms, as it doesnât (and wonât)
>
Your message dated Wed, 26 Mar 2025 09:09:10 +
with message-id
and subject line Bug#1101334: fixed in rust-mimalloc 0.1.44-1
has caused the Debian Bug report #1101334,
regarding Mimalloc < v0.1.39 Can Allocate Memory with Bad Alignment
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> affects 1101237 - src:lorsdawar src:abiword src:aspectc++ src:snapper
> src:libxml++2.6 src:ciftilib src:mediaconch src:afdko src:gnome-commander
> src:loggedfs src:thermald src:pinot src:dbus-cpp src:compiz-plugins-main
> src:mapserver src:cgr
Processing commands for cont...@bugs.debian.org:
> affects 1101235 - src:lorsdawar src:abiword src:aspectc++ src:snapper
> src:libxml++2.6 src:ciftilib src:mediaconch src:afdko src:gnome-commander
> src:loggedfs src:thermald src:pinot src:dbus-cpp src:compiz-plugins-main
> src:mapserver src:cgr
Your message dated Wed, 26 Mar 2025 13:20:37 +
with message-id
and subject line Bug#1078618: fixed in golang-github-micromdm-scep 2.3.0-1
has caused the Debian Bug report #1078618,
regarding golang-github-micromdm-scep: will FTBFS during trixie support period
to be marked as done.
This means
A bit more context about the fix: I tried temporarily changing the time
on my machine to 2028-07-01 and built this new upstream release
successfully, so please see if you are still able to reproduce this. It
seems upstream moved tests around and modified them, so chances are they
resolved this som
reassign 1100299 freerdp3-dev
affects 1100299 src:remmina
found 1100299 3.13.0+dfsg-1
close 1100299 3.14.0+dfsg-1
thanks
I received the following explanation from upstream:
-
After some research, it seems like this issue was cau
Processing commands for cont...@bugs.debian.org:
> reassign 1100299 freerdp3-dev
Bug #1100299 [src:remmina] remmina: FTBFS: plugins/rdp/rdp_plugin.c:1586:65:
error: implicit declaration of function
'freerdp_keyboard_get_rdp_scancode_from_x11_keycode'
Bug reassigned from package 'src:remmina' to
Processing commands for cont...@bugs.debian.org:
> tags 1099826 sid forky
Bug #1099826 [src:obs-ashmanix-countdown] FTBFS: error: ‘void
QCheckBox::stateChanged(int)’ is deprecated
Added tag(s) forky and sid.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> tags 1099826 + a11y
Bug #1099826 [src:obs-ashmanix-countdown] FTBFS: error: ‘void
QCheckBox::stateChanged(int)’ is deprecated
Added tag(s) a11y.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1099826: https://bu
Processing commands for cont...@bugs.debian.org:
> tags 1099826 - a11y
Bug #1099826 [src:obs-ashmanix-countdown] FTBFS: error: ‘void
QCheckBox::stateChanged(int)’ is deprecated
Removed tag(s) a11y.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1099826: https://
Hi,
as another, simpler solution, a two-line fix for the issue has been merged
upstream:
https://gitlab.winehq.org/mono/mono/-/commit/cf37d8943fe5118fbfcea86149ad5b7b2d244103
. I have built a debian backports package for bookworm with the change and
having tested on the actual device I can confirm
I think I see the problem.
The test run on 2025-01-29 03:55:04 UTC [1] against numpy/1:2.2.2+ds-2
should have failed, and prevented numpy from migrating to testing, but
debian/tests/control has all tests marked 'skip-not-installable'
(please don't do that), so the test result was considered 'neutr
Package: lintian
Version: 2.121.2
Severity: serious
Tags: ftbfs, patch
Dear Maintainer,
lintian has one unavailable build-dep on libperl-critic-freenode-perl,
see #1099305. The build log is below:
```
The following packages have unmet dependencies:
sbuild-build-depends-main-dummy : Depends: lib
you can fix this FTBFS by changing the version of cmake in the 3 files in
test/cmake/*.cmake
-cmake_minimum_required(VERSION 3.5)
+cmake_minimum_required(VERSION 3.25)
works for me -- 3.5 is apparently no longer supported by cmake. bookworm
has cmake version 3.25
Processing commands for cont...@bugs.debian.org:
> fixed 1101377 1.7.3-1
Bug #1101377 [syncthingtray] crashes on startup
Ignoring request to alter fixed versions of bug #1101377 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
110
Your message dated Wed, 26 Mar 2025 22:05:09 +
with message-id
and subject line Bug#1092262: fixed in purify 4.2.0-1
has caused the Debian Bug report #1092262,
regarding purify: FTBFS with spdlog 1.15
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
On Wed, Mar 26, 2025 at 01:38:40AM +, Mathias Gibbens wrote:
> Any progress investigating this? Otherwise I fear keepassxc will fall
> out of testing before the trixie release.
The failing test in 2.7.10 now is testentrymodel so this won't be
investigated further.
FAIL! : TestEntryModel::t
On Tue, Mar 11, 2025 at 03:27:04PM -0700, Vagrant Cascadian wrote:
>...
> This patch works for me with flash-kernel and u-boot-menu installed,
> with U_BOOT_SYNC_DTBS=true|false, but slightly changes the behavior of
> U_BOOT_SYNC_DTBS to put files in a different location.
>
> diff --git a/read-con
Source: json-tricks
Version: 3.11.0-4
Severity: serious
Control: close -1 3.17.3-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: s...@lists.debian.org
User: s...@lists.debian.org
Usertags: s390x
Dear maintainer(s),
The Release Team considers p
Source: glib-d
Version: 2.4.3-2
Severity: serious
Tags: ftbfs trixie sid
Forwarded: https://github.com/gtkd-developers/GlibD/issues/22
X-Debbugs-CC: m...@debian.org
glib-d fails to build in Debian Testing, at least in part because of a
change in glib 2.84. See the upstream bug for more details.
g
Processing control commands:
> close -1 3.17.3-1
Bug #1101381 [src:json-tricks] src:json-tricks: fails to migrate to testing for
too long: autopkgtest regression on s390x
Marked as fixed in versions json-tricks/3.17.3-1.
Bug #1101381 [src:json-tricks] src:json-tricks: fails to migrate to testing
Processing control commands:
> close -1 0.140-2
Bug #1101382 [src:culmus] src:culmus: fails to migrate to testing for too long:
uploader built arch:all binary
Marked as fixed in versions culmus/0.140-2.
Bug #1101382 [src:culmus] src:culmus: fails to migrate to testing for too long:
uploader buil
Your message dated Wed, 26 Mar 2025 20:36:09 +
with message-id
and subject line Bug#1064137: fixed in procdump 2.2-2
has caused the Debian Bug report #1064137,
regarding procdump no longer builds on mips64el/ppc64el/riscv64
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> close -1 0.7.9-13
Bug #1101385 [src:rust-axum] src:rust-axum: fails to migrate to testing for too
long
Marked as fixed in versions rust-axum/0.7.9-13.
Bug #1101385 [src:rust-axum] src:rust-axum: fails to migrate to testing for too
long
Marked Bug as done
--
11013
Source: stalin
Version: 0.11-7
Severity: serious
Control: close -1 0.11-8
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having
Source: rust-axum
Version: 0.6.20-36
Severity: serious
Control: close -1 0.7.9-13
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days a
Source: lme4
Version: 1.1-35.5-1
Severity: serious
Control: close -1 1.1-36-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as ha
Processing control commands:
> close -1 0.11-8
Bug #1101384 [src:stalin] src:stalin: fails to migrate to testing for too long:
new autopkgtest fails
Marked as fixed in versions stalin/0.11-8.
Bug #1101384 [src:stalin] src:stalin: fails to migrate to testing for too long:
new autopkgtest fails
Ma
Processing control commands:
> severity -1 grave
Bug #1085140 [ejabberd] ejabberd does not listen on any port after update to
24.07
Severity set to 'grave' from 'important'
--
1085140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085140
Debian Bug Tracking System
Contact ow...@bugs.debian
Your message dated Thu, 27 Mar 2025 00:47:23 +
with message-id
and subject line Bug#1100566: fixed in libxslt 1.1.35-1+deb12u1
has caused the Debian Bug report #1100566,
regarding libxslt: CVE-2025-24855: Use-after-free due to xsltEvalXPathStringNs
leaking xpathCtxt->node
to be marked as done
Your message dated Wed, 26 Mar 2025 20:35:59 +
with message-id
and subject line Bug#1101379: fixed in nvme-stas 2.4-3
has caused the Debian Bug report #1101379,
regarding nvme-stas: autopkgtest fails on all architectures
to be marked as done.
This means that you claim that the problem has bee
Your message dated Wed, 26 Mar 2025 20:35:53 +
with message-id
and subject line Bug#1101237: fixed in loggedfs 0.9+ds-5
has caused the Debian Bug report #1101237,
regarding loggedfs: FTBFS: /usr/include/unicode/localpointer.h:561:26: error:
parameter declared 'auto'
to be marked as done.
Thi
Source: gnome-calls
Version: 47.0-2
Severity: serious
Control: close -1 48.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: m...@lists.debian.org
User: m...@lists.debian.org
Usertags: mips64el
Dear maintainer(s),
The Release Team considers pac
On 26 March 2025 at 21:37, Paul Gevers wrote:
| Source: lme4
| Version: 1.1-35.5-1
| Severity: serious
| Control: close -1 1.1-36-1
| Tags: sid trixie
| User: release.debian@packages.debian.org
| Usertags: out-of-sync
Hm, it so happens that there was a new upstream version 1.1-37 released
ye
Control: tag -1 pending
Hello,
Bug #1054720 in jhbuild 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/jhbuild/-/commit/5c73ceeff1ce543dc6701fa3abee8
Control: tag -1 pending
Hello,
Bug #1065882 in jhbuild 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/jhbuild/-/commit/270ea48532b7e665a1170e52336dd
Processing control commands:
> tag -1 pending
Bug #1054720 [src:jhbuild] jhbuild: FTBFS: FileNotFoundError: [Errno 2] No such
file or directory: 'hello'
Added tag(s) pending.
--
1054720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054720
Debian Bug Tracking System
Contact ow...@bugs.debi
Processing control commands:
> tag -1 pending
Bug #1065882 [src:jhbuild] jhbuild: Please drop dependencies on
python3-distutils
Added tag(s) pending.
--
1065882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: nvme-stas
Version: 2.4-2
Severity: serious
Justification: blocks other packages from migrating to testing
Affects: iproute2
Dear Maintainer(s),
The new version of nvme-stas in unstable has been failing all
autopkgtest runs for the past couple of days. Test jobs on debci are
getting schedu
Your message dated Thu, 27 Mar 2025 00:47:23 +
with message-id
and subject line Bug#1100565: fixed in libxslt 1.1.35-1+deb12u1
has caused the Debian Bug report #1100565,
regarding libxslt: CVE-2024-55549: Use-after-free related to excluded result
prefixes
to be marked as done.
This means tha
Processing control commands:
> affects -1 - liburjtag
Bug #1100873 [src:urjtag] Conflicting binaries produced by liburjtag and urjtag
source package
Removed indication that 1100873 affects
--
1100873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100873
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1091288 in x2gokdriveclient 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/debian-remote-team/x2gokdrive/-/commit/e58dae773
Processing control commands:
> close -1 48.0-1
Bug #1101387 [src:gnome-calls] src:gnome-calls: fails to migrate to testing for
too long: FTBFS on mips64el
Marked as fixed in versions gnome-calls/48.0-1.
Bug #1101387 [src:gnome-calls] src:gnome-calls: fails to migrate to testing for
too long: FTB
Your message dated Sun, 23 Mar 2025 18:36:27 +
with message-id
and subject line Bug#1091288: fixed in x2gokdrive 0.0.0.3-2
has caused the Debian Bug report #1091288,
regarding x2gokdrive: FTBFS on armhf: x2gokdriveremote.c:137:74: error: passing
argument 4 of ‘TimerSet’ from incompatible poin
Processing commands for cont...@bugs.debian.org:
> retitle 1068051 tilix: FTBFS on armhf, s390x
Bug #1068051 {Done: Jeremy Bícha } [src:tilix] tilix: FTBFS:
linking error during build
Changed Bug title to 'tilix: FTBFS on armhf, s390x' from 'tilix: FTBFS: linking
error during build'.
> reopen 10
Package: syncthingtray
Version: 1.5.4-1
Severity: grave
Hi!
Syncthingtray doesn't start anymore on trixie:
anarcat@angela:~> syncthingtray
Info: Single instance application ID: Syncthing Tray-Martchus-1000
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Processing control commands:
> close -1 1.1-36-1
Bug #1101386 [src:lme4] src:lme4: fails to migrate to testing for too long
Marked as fixed in versions lme4/1.1-36-1.
Bug #1101386 [src:lme4] src:lme4: fails to migrate to testing for too long
Marked Bug as done
--
1101386: https://bugs.debian.org
Source: culmus
Version: 0.140-1
Severity: serious
Control: close -1 0.140-2
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days
Control: severity -1 normal
Control: retitle -1 RM: gbemol -- RoQA: unmaintained upstream, low usage,
depends on deprecated GTK 2
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:gbemol
Thanks
Hi,
as announced I hereby turn the pre-removal bug into a RoQA bug.
Kind regards
Andr
Processing control commands:
> affects -1 + libstrophe-dev
Bug #1100944 [libstrophe-doc] libstrophe-doc misses Breaks+Replaces:
libstrophe-dev (<< 0.14.0-2~)
Added indication that 1100944 affects libstrophe-dev
--
1100944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100944
Debian Bug Tra
Hi,
On Wed, 2025-03-26 at 10:22 +0100, Michael Biebl wrote:
> Am 21.02.25 um 14:38 schrieb John Paul Adrian Glaubitz:
> > Hi Michael,
> >
> > On Fri, 2025-02-14 at 23:13 +0100, Michael Biebl wrote:
> > > it appears that Frédéric Bonnard is not really active anymore.
> > > I've CCed you as PPC por
Package: golang-gitlab-gitlab-org-api-client-go-dev
Version: 0.123.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + golang-github-xanzy-go-gitlab-dev
golang-gitlab-gitlab-org-api-client-go-dev installs
/usr/share/gocode/src/github.com/xanzy/go-git
Processing control commands:
> affects -1 + golang-github-xanzy-go-gitlab-dev
Bug #1101345 [golang-gitlab-gitlab-org-api-client-go-dev] symlink vs directory
conflict for golang-gitlab-gitlab-org-api-client-go-dev overwriting
golang-github-xanzy-go-gitlab-dev
Added indication that 1101345 affects
Package: gitaly
Version: 16.11.6+ds1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + golang-gitlab-gitlab-org-gitaly-dev
The files /usr/share/gitaly/ruby/.bundle and
/usr/share/gitaly/ruby/Gemfile.lock are installed by both
gitaly/16.11.6+ds1-2 as
Processing control commands:
> affects -1 + golang-gitlab-gitlab-org-gitaly-dev
Bug #1101344 [gitaly] gitaly has an undeclared file conflict with
golang-gitlab-gitlab-org-gitaly-dev/unstable
Added indication that 1101344 affects golang-gitlab-gitlab-org-gitaly-dev
--
1101344: https://bugs.debia
Hi Helmut,
On 23 March 2025 at 19:57, Helmut Grohne wrote:
| On Sun, Mar 23, 2025 at 11:03:07AM -0500, Dirk Eddelbuettel wrote:
| > On 23 March 2025 at 13:53, Helmut Grohne wrote:
| > | Package: inn2,sm
| > | Severity: serious
| > | User: debian...@lists.debian.org
| > | Usertags: fileconflict
|
Package: linuxcnc-uspace
Version: 1:2.9.4-1
Severity: serious
User: helm...@debian.org
Usertags: dep17m2
Hi,
your package installs files in /lib:
/lib/udev/rules.d/99-shuttle.rules
/lib/udev/rules.d/99-xhc-whb04b-6.rules
/lib/udev/rules.d/99-xhc.rules
Starting with trixie, installing files i
Processing commands for cont...@bugs.debian.org:
> notfound 1100661 10.0.0+dfsg-2
Bug #1100661 {Done: Bastian Germann } [src:tinyxml2]
libtinyxml2-10: apparent ABI break
Ignoring request to alter found versions of bug #1100661 to the same values
previously set
> found 1100661 10.1.0+dfsg-1
Bug #
This is a regression in the latest package update.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073692
Seemingly those changes were dropped by accident.
The addition of the epoch looks spurious as well.
Usually, the addition of an epoch should be discussed on the
debian-devel mailing
Hi Adrian
Am 21.02.25 um 14:38 schrieb John Paul Adrian Glaubitz:
Hi Michael,
On Fri, 2025-02-14 at 23:13 +0100, Michael Biebl wrote:
it appears that Frédéric Bonnard is not really active anymore.
I've CCed you as PPC porter. Maybe you can have a look at this bug
report and do an NMU / take ov
Hello Mathieu,
I see that the package seems ready for upload in git, is there any
remaining blocker? Anything that I could do to help with this?
Given the timeline for the freeze [1] packages that are not in testing
by 2025-04-15 will skip the next stable release, so I think this is kind
of urgent
Your message dated Wed, 26 Mar 2025 10:20:16 +
with message-id
and subject line Bug#1084715: fixed in streamtuner2 2.2.2+dfsg-2.2
has caused the Debian Bug report #1084715,
regarding streamtuner2: removal of Python standard libraries in Python 3.13
to be marked as done.
This means that you cl
Processing control commands:
> severity -1 normal
Bug #1098886 [src:gbemol] gbemol: Should gbemol be removed from unstable?
Severity set to 'normal' from 'serious'
> retitle -1 RM: gbemol -- RoQA: unmaintained upstream, low usage, depends on
> deprecated GTK 2
Bug #1098886 [src:gbemol] gbemol: Sh
Processing control commands:
> forwarded -1 https://jira.mariadb.org/browse/MDEV-35424
Bug #1101340 [mariadb-server-core] mariadb-server-core:
innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.
Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-35424'.
--
Package: mariadb-server-core
Version: 1:10.11.11-0+deb12u1
Severity: critical
Tags: upstream
Justification: causes serious data loss
X-Debbugs-Cc: t...@security.debian.org
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situ
Your message dated Wed, 26 Mar 2025 08:35:05 +
with message-id
and subject line Bug#1100679: fixed in brickos 0.9.0.dfsg-14
has caused the Debian Bug report #1100679,
regarding brickos-doc/trixie misses Breaks+Replaces for brickos/bookworm
to be marked as done.
This means that you claim that
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-35424
Thanks for reporting! This will hopefully be fixed in next upstream release.
I do. Thanks.
Le mer. 26 mars 2025 à 10:47, Colin Watson a écrit :
> Alexandre, could you maybe have a look at this since this was your NMU?
On Tue, Mar 18, 2025 at 08:39:51PM +0100, Paul Gevers wrote:
Source: python-marshmallow
Version: 3.20.1-1.1
Severity: serious
Control: close -1 3.26.1-0.1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages
Processing control commands:
> notfound -1 2:21.2+dfsg-3
Bug #1100726 {Done: Vasyl Gello } [kodi] kodi:
Segmentation fault at startup
Ignoring request to alter found versions of bug #1100726 to the same values
previously set
--
1100726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100726
Package: kodi
Version: 2:21.2+dfsg-3
Followup-For: Bug #1100726
Dear Maintainer,
With the revert of the fix for this bug in kodi 2:21.2+dfsg-3, this
crash at startup is back.
I see no rationale for this revert. Was it intentional to push the
revert to Debian?
I have:
ii libtinyxml-dev:amd64
Control: notfound -1 2:21.2+dfsg-3
Nevermind I found the rational in the Debian changelog.
It turned out I did not upgrade kodi-pvr-nextpvr 21.3.1+ds-1 from
trixie which also depends on lintinyxml2 but version 10, to kodi-pvr-
nextpvr 21.3.2+ds-1 which depends on libtinyxml11.
So the mixup of tin
Control: notfound -1 2:21.2+dfsg-3
Nevermind I found the rational in the Debian changelog.
It turned out I did not upgrade kodi-pvr-nextpvr 21.3.1+ds-1 from
trixie which also depends on lintinyxml2 but version 10, to kodi-pvr-
nextpvr 21.3.2+ds-1 which depends on libtinyxml11.
So the mixup of tin
Your message dated Wed, 26 Mar 2025 23:07:43 +
with message-id
and subject line Bug#1068051: fixed in tilix 1.9.6-3
has caused the Debian Bug report #1068051,
regarding tilix: FTBFS: linking error during build
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Thu, 27 Mar 2025 00:32:24 +
with message-id
and subject line Bug#1100899: fixed in mercurial 6.3.2-1+deb12u1
has caused the Debian Bug report #1100899,
regarding mercurial: reflected XSS in hgweb (CVE-2025-2361)
to be marked as done.
This means that you claim that the probl
Processing control commands:
> notfound -1 2:21.2+dfsg-3
Bug #1100726 {Done: Vasyl Gello } [kodi] kodi:
Segmentation fault at startup
No longer marked as found in versions kodi/2:21.2+dfsg-3.
--
1100726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100726
Debian Bug Tracking System
Contac
Your message dated Fri, 21 Mar 2025 06:34:19 +
with message-id
and subject line Bug#1100133: fixed in openmsx 20.0+dfsg-1.1
has caused the Debian Bug report #1100133,
regarding openmsx: needs sourceful upload
to be marked as done.
This means that you claim that the problem has been dealt with
Package: dahdi-dkms
Version: 1:3.1.0+git20230717~dfsg-10
Severity: serious
Hi,
I have again a few updates for the -dkms package.
dkms.conf contains a duplicate module definition which can cause subtle
errors with dkms, therefore I'll make dkms error out on such dkms.conf
files in an upcoming dkm
86 matches
Mail list logo
