Your message dated Wed, 16 Apr 2025 06:36:23 +
with message-id
and subject line Bug#1103226: fixed in chromium 135.0.7049.95-1
has caused the Debian Bug report #1103226,
regarding chromium: FTBFS:
gen/third_party/blink/renderer/platform/color_data.cc:138:7: error: fallthrough
annotation does
Your message dated Wed, 16 Apr 2025 05:38:05 +
with message-id <3352178.44csPzL39Z@frame>
and subject line
has caused the Debian Bug report #1082837,
regarding ITP: mauiman -- Maui manager library with server and public library
API
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 16 Apr 2025 05:22:02 +
with message-id <13741701.uLZWGnKmhe@frame>
and subject line
has caused the Debian Bug report #1082836,
regarding ITP: mauikit -- Templated convergent controls and multi-platform
utilities for Maui applications
to be marked as done.
This means t
Processing commands for cont...@bugs.debian.org:
> reassign 1103210 python-levenshtein 0.27.1-1
Bug #1103210 [src:textdistance] textdistance: FTBFS: RuntimeError: cannot
import Levenshtein.distance
Bug reassigned from package 'src:textdistance' to 'python-levenshtein'.
No longer marked as found i
Your message dated Wed, 16 Apr 2025 04:19:30 +
with message-id
and subject line Bug#1102379: fixed in hyperkitty 1.3.12-3
has caused the Debian Bug report #1102379,
regarding hyperkitty: FTBFS: FAIL: test_header
(hyperkitty.tests.test_templatetags.TestDecorate.test_header)
to be marked as don
Your message dated Wed, 16 Apr 2025 04:19:17 +
with message-id
and subject line Bug#1102717: fixed in gnupg2 2.4.7-15
has caused the Debian Bug report #1102717,
regarding gnupg: fails to interact with HSM after upgrade from 2.2.46
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 16 Apr 2025 03:58:11 +
with message-id
and subject line Bug#1078617: fixed in golang-github-fsouza-go-dockerclient
1.12.1-1
has caused the Debian Bug report #1078617,
regarding golang-github-fsouza-go-dockerclient: will FTBFS during trixie
support period
to be marked
Processing commands for cont...@bugs.debian.org:
> close 1102551
Bug #1102551 [sponsorship-requests] RFS: runit-services/0.9.1 -- UNIX init
scheme with service supervision (services)
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1102551: https:
Your message dated Wed, 16 Apr 2025 01:49:05 +
with message-id
and subject line Bug#1103146: fixed in jsonpickle 4.0.2+dfsg-2
has caused the Debian Bug report #1103146,
regarding jsonpickle: FTBFS in testing/i386: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.13 re
Your message dated Wed, 16 Apr 2025 01:33:59 +
with message-id
and subject line Bug#1102482: fixed in runit-services 0.9.1
has caused the Debian Bug report #1102482,
regarding runit-services: rsyslog logrotate workaround not set up on upgrade
from bookworm
to be marked as done.
This means th
Your message dated Wed, 16 Apr 2025 01:04:26 +
with message-id
and subject line Bug#1101500: fixed in upx-ucl 4.2.4-1.1
has caused the Debian Bug report #1101500,
regarding upx-ucl: CVE-2025-2849
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 16 Apr 2025 09:55:08 +0900
with message-id
and subject line r-cran-multitaper is now in Debian.
has caused the Debian Bug report #1101591,
regarding r-cran-waveslim: FTBFS: build-dependency not installable:
r-cran-multitaper
to be marked as done.
This means that you claim
Your message dated Wed, 16 Apr 2025 02:49:10 +0200
with message-id
and subject line Re: linux-source-6.6: make localmodconfig does not configure
USB storage, nor cdrom filesystem
has caused the Debian Bug report #1066976,
regarding linux-source-6.6: make localmodconfig does not configure USB stor
Your message dated Wed, 16 Apr 2025 01:44:22 +0200
with message-id <87r01t3s89@christian.marillat.net>
and subject line Re: Bug#1103259: distcc starts unexpectedly
has caused the Debian Bug report #1103259,
regarding distcc starts unexpectedly
to be marked as done.
This means that you claim th
Your message dated Tue, 15 Apr 2025 23:19:52 +
with message-id
and subject line Bug#1043037: fixed in mlmmj 1.5.0-1
has caused the Debian Bug report #1043037,
regarding Switch upstream source to fork after release of MLMMJ 1.4
to be marked as done.
This means that you claim that the problem h
Your message dated Tue, 15 Apr 2025 22:52:55 +
with message-id
and subject line Bug#1044625: fixed in guile-semver 0.1.1-4
has caused the Debian Bug report #1044625,
regarding guile-semver: Fails to build source after successful build
to be marked as done.
This means that you claim that the p
Your message dated Tue, 15 Apr 2025 22:35:43 +
with message-id
and subject line Bug#1044673: fixed in guile-json 4.7.3-3
has caused the Debian Bug report #1044673,
regarding guile-json: Fails to build source after successful build
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 15 Apr 2025 22:11:05 +
with message-id
and subject line Bug#1103044: fixed in mat2 0.13.5-1.2
has caused the Debian Bug report #1103044,
regarding mat2: unsatisfiable dependency on python2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 15 Apr 2025 22:07:16 +
with message-id
and subject line Bug#1095986: fixed in curl 8.13.0-2
has caused the Debian Bug report #1095986,
regarding curl: build against openssl again instead of gnutls
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 15 Apr 2025 21:47:57 +
with message-id
and subject line Bug#1044559: fixed in guile-lzlib 0.3.0-2
has caused the Debian Bug report #1044559,
regarding guile-lzlib: Fails to build source after successful build
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 15 Apr 2025 21:07:12 +
with message-id
and subject line Bug#1103208: fixed in supysonic 0.7.9+ds-2
has caused the Debian Bug report #1103208,
regarding supysonic: FTBFS: dh_install: error: missing files, aborting
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Apr 2025 21:06:24 +
with message-id
and subject line Bug#1100320: fixed in qt6-webengine 6.8.2+dfsg-4
has caused the Debian Bug report #1100320,
regarding skanpage: FTBFS in testing/arm64: make: *** [debian/rules:6: binary]
Error 2
to be marked as done.
This means
Your message dated Tue, 15 Apr 2025 21:06:24 +
with message-id
and subject line Bug#1100320: fixed in qt6-webengine 6.8.2+dfsg-4
has caused the Debian Bug report #1100320,
regarding qt6-pdf-dev: missing Qt6Pdf files (which are in qt6-webengine-dev
instead) break cmake-based builds w/o qt6-web
Your message dated Tue, 15 Apr 2025 20:42:33 +
with message-id
and subject line Bug#1102970: fixed in guile-git 0.9.0-2
has caused the Debian Bug report #1102970,
regarding guile-git: FTBFS in testing: dh_auto_test: error: cd
debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verb
Your message dated Tue, 15 Apr 2025 20:35:20 +
with message-id
and subject line Bug#1102663: fixed in crmsh 4.6.1-2
has caused the Debian Bug report #1102663,
regarding crmsh: crmsh's update_err failing with "NameError: name
'cibadmin_opt' is not defined"
to be marked as done.
This means tha
Processing commands for cont...@bugs.debian.org:
> forcemerge 1103180 976297
Bug #1103180 {Done: ba...@debian.org} [wnpp] ITP: ripgrep-all -- rga wraps
ripgrep and enables it to search in pdf, docx, sqlite, jpg and more
Bug #976297 [wnpp] ITP: ripgrep-all -- search in PDFs, E-Books, and archives
Your message dated Tue, 15 Apr 2025 19:49:20 +
with message-id
and subject line Bug#1030904: fixed in libgovirt 0.3.9-6
has caused the Debian Bug report #1030904,
regarding libgovirt: tests are not thread-safe
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Tue, 15 Apr 2025 19:49:43 +
with message-id
and subject line Bug#1103194: fixed in pcs 0.12.0-2
has caused the Debian Bug report #1103194,
regarding pcs: FTBFS: rm: cannot remove
'/<>/debian/tmp/usr/lib/python3/dist-packages/*.dist-info/COPYING':
No such file or directory
Your message dated Tue, 15 Apr 2025 19:21:16 +
with message-id
and subject line Bug#1102465: fixed in petsc 3.22.5+dfsg1-2
has caused the Debian Bug report #1102465,
regarding petsc: PETSc was configured with one MPICH/Open MPI mpi.h version but
now appears to be compiling using an older vers
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1101928: fixed in sbuild 0.89.0
has caused the Debian Bug report #1101928,
regarding sbuild fails to initiate podman-based autopkgtest
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1101753: fixed in sbuild 0.89.0
has caused the Debian Bug report #1101753,
regarding sbuild: newuidmap: Target process is owned by a different user
to be marked as done.
This means that you claim that the prob
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1100769: fixed in sbuild 0.89.0
has caused the Debian Bug report #1100769,
regarding sbuild-debian-developer-setup: Support non-native chroot architectures
to be marked as done.
This means that you claim that
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#834736: fixed in sbuild 0.89.0
has caused the Debian Bug report #834736,
regarding sbuild: Being able to choose format for build log filenames
to be marked as done.
This means that you claim that the problem h
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#963756: fixed in sbuild 0.89.0
has caused the Debian Bug report #963756,
regarding sbuild: Better enforce incompatibility between '--arch-all
--no-arch-any' vs '--append-to-version'
to be marked as done.
This
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1087430: fixed in sbuild 0.89.0
has caused the Debian Bug report #1087430,
regarding sbuild: expose underlying fs in unshare mode
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1091222: fixed in sbuild 0.89.0
has caused the Debian Bug report #1091222,
regarding sbuild: reproducible build paths breaks developer workflows with
default schroot configuration and purge_build_directory="su
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#731573: fixed in sbuild 0.89.0
has caused the Debian Bug report #731573,
regarding sbuild: Please clarify help output of sbuild-adduser
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1094982: fixed in sbuild 0.89.0
has caused the Debian Bug report #1094982,
regarding sbuild --verbose -D does not show invocation of dpkg-source
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1095063: fixed in sbuild 0.89.0
has caused the Debian Bug report #1095063,
regarding sbuild: --make-binNMU requires -m, -e or -k but only -m is accepted
and fails
to be marked as done.
This means that you cl
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#1032302: fixed in sbuild 0.89.0
has caused the Debian Bug report #1032302,
regarding sbuild: Lintian exit status confusion
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1100636: fixed in sbuild 0.89.0
has caused the Debian Bug report #1100636,
regarding sbuild: Shows message E: Failed to execute “dpkg-buildtree”: No such
file or directory when building packages for bookworm
t
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1099551: fixed in sbuild 0.89.0
has caused the Debian Bug report #1099551,
regarding sbuild: does no longer work with schroot in some cases (?)
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1090360: fixed in sbuild 0.89.0
has caused the Debian Bug report #1090360,
regarding sbuild: running autopkgtests is broken
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 15 Apr 2025 19:21:24 +
with message-id
and subject line Bug#1057768: fixed in sbuild 0.89.0
has caused the Debian Bug report #1057768,
regarding debian/tests/get_default_release.py fails when
stable-proposed-updates is enabled
to be marked as done.
This means that you
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#1050147: fixed in sbuild 0.89.0
has caused the Debian Bug report #1050147,
regarding sbuild: Allow hiding output sections (e.g., Changes, Buildinfo)
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 15 Apr 2025 19:21:23 +
with message-id
and subject line Bug#1033352: fixed in sbuild 0.89.0
has caused the Debian Bug report #1033352,
regarding sbuild: autokpgtest-virt-server needs host $HOME
to be marked as done.
This means that you claim that the problem has been d
Processing commands for cont...@bugs.debian.org:
> close 854714 0.5.0-1
Bug #854714 [src:trocla] trocla: FTBFS randomly (failing tests)
Marked as fixed in versions trocla/0.5.0-1.
Bug #854714 [src:trocla] trocla: FTBFS randomly (failing tests)
Marked Bug as done
> thanks
Stopping processing here.
Your message dated Tue, 15 Apr 2025 18:50:53 +
with message-id
and subject line Bug#1103159: fixed in python-fido2 1.2.0-2
has caused the Debian Bug report #1103159,
regarding ModuleNotFoundError: No module named 'smartcard.pcsc.PCSCContext'
since 2.2.1-2 to 2.2.2-1 upgrade
to be marked as do
Your message dated Tue, 15 Apr 2025 19:35:27 +0100
with message-id
and subject line re: feature trace is unusable
has caused the Debian Bug report #1102275,
regarding feature trace is unusable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Tue, 15 Apr 2025 18:22:39 +
with message-id
and subject line Bug#1102068: fixed in mpich 4.3.0-6
has caused the Debian Bug report #1102068,
regarding libfabric: FTBFS on 32-bit arches: ofi_cma.h: error: passing argument
2 of 'ofi_consume_iov' from incompatible pointer type
Your message dated Tue, 15 Apr 2025 18:19:46 +
with message-id
and subject line Bug#1103229: fixed in ltt-control 2.13.15-2
has caused the Debian Bug report #1103229,
regarding ltt-control:FTBFS:build failed(error: 'health_state' undeclared)
to be marked as done.
This means that you claim tha
Your message dated Tue, 15 Apr 2025 18:17:10 +
with message-id
and subject line Bug#1101978: fixed in chromium 135.0.7049.84-1~deb12u1
has caused the Debian Bug report #1101978,
regarding chromium: passwords not available after upgrade to 135.0.7049.52-1
to be marked as done.
This means that
Your message dated Tue, 15 Apr 2025 18:19:29 +
with message-id
and subject line Bug#1103256: fixed in golang-github-smallstep-certificates
0.20.0-5
has caused the Debian Bug report #1103256,
regarding golang-github-smallstep-crypto: FTBFS during tests when built with
nebula >= 1.9.3
to be ma
Your message dated Tue, 15 Apr 2025 18:17:25 +
with message-id
and subject line Bug#1100829: fixed in debian-archive-keyring 2023.3+deb12u2
has caused the Debian Bug report #1100829,
regarding debian-archive-keyring: trixie SRM key
to be marked as done.
This means that you claim that the prob
Your message dated Tue, 15 Apr 2025 18:17:25 +
with message-id
and subject line Bug#1100828: fixed in debian-archive-keyring 2023.3+deb12u2
has caused the Debian Bug report #1100828,
regarding debian-archive-keyring: trixie archive signing keys
to be marked as done.
This means that you claim
Your message dated Tue, 15 Apr 2025 18:17:25 +
with message-id
and subject line Bug#1099223: fixed in debian-archive-keyring 2023.3+deb12u2
has caused the Debian Bug report #1099223,
regarding debian-archive-keyring: FTBFS: gpg: Can't check signature: No public
key
to be marked as done.
This
Your message dated Tue, 15 Apr 2025 18:04:56 +
with message-id
and subject line Bug#1093056: fixed in xterm 398-1
has caused the Debian Bug report #1093056,
regarding xterm: Alt key combinations with non-Latin keyboard layouts don't
send escape sequences in modifyOtherKeys mode 2
to be marked
Your message dated Tue, 15 Apr 2025 17:45:30 +
with message-id
and subject line Bug#1103167: Removed package(s) from unstable
has caused the Debian Bug report #1103167,
regarding RM: golang-github-getlantern-context -- ROM; leaf package, unused
to be marked as done.
This means that you claim
Your message dated Tue, 15 Apr 2025 17:45:02 +
with message-id
and subject line Bug#1103166: Removed package(s) from unstable
has caused the Debian Bug report #1103166,
regarding RM: golang-github-getlantern-ops -- ROM; leaf package, unused
to be marked as done.
This means that you claim that
Your message dated Tue, 15 Apr 2025 17:45:57 +
with message-id
and subject line Bug#1103168: Removed package(s) from unstable
has caused the Debian Bug report #1103168,
regarding RM: golang-github-apparentlymart-go-openvpn-mgmt -- ROM; leaf
package, unused
to be marked as done.
This means th
Your message dated Tue, 15 Apr 2025 17:44:39 +
with message-id
and subject line Bug#1102689: Removed package(s) from unstable
has caused the Debian Bug report #1090881,
regarding ruby-mail-room: FTBFS with ruby-mocha 2: ERROR: Test "ruby3.1"
failed: Failure/Error: @server.start
to be mar
Your message dated Tue, 15 Apr 2025 17:44:39 +
with message-id
and subject line Bug#1102689: Removed package(s) from unstable
has caused the Debian Bug report #945211,
regarding ruby-mail-room ftbfs with ruby-redis 4 in experimental
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 15 Apr 2025 17:44:37 +
with message-id
and subject line Bug#1102689: Removed package(s) from unstable
has caused the Debian Bug report #1102689,
regarding RM: ruby-mail-room -- ROM; rc buggy, not needed anymore
to be marked as done.
This means that you claim that the p
Your message dated Tue, 15 Apr 2025 17:41:52 +
with message-id
and subject line Bug#1102636: Removed package(s) from unstable
has caused the Debian Bug report #1102636,
regarding RM: golang-step-crypto-dev -- RoM; not used, replaced by
golang-github-smallstep-crypto
to be marked as done.
Thi
Your message dated Tue, 15 Apr 2025 17:44:13 +
with message-id
and subject line Bug#1102688: Removed package(s) from unstable
has caused the Debian Bug report #837088,
regarding ruby-devise: 4.1.1-3 cause Circular dependency fail positives
to be marked as done.
This means that you claim that
Your message dated Tue, 15 Apr 2025 17:44:39 +
with message-id
and subject line Bug#1102689: Removed package(s) from unstable
has caused the Debian Bug report #1101712,
regarding ruby-mail-room: FTBFS: Failure/Error: @server.start
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 15 Apr 2025 17:43:43 +
with message-id
and subject line Bug#1102668: Removed package(s) from unstable
has caused the Debian Bug report #982199,
regarding enable tests (fails only on buildd)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 15 Apr 2025 17:44:11 +
with message-id
and subject line Bug#1102688: Removed package(s) from unstable
has caused the Debian Bug report #1102688,
regarding RM: ruby-devise -- ROM; rc buggy, not needed now
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 15 Apr 2025 17:42:51 +
with message-id
and subject line Bug#1102666: Removed package(s) from unstable
has caused the Debian Bug report #1102666,
regarding RM: ruby-poltergeist -- ROM; unused leaf package
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 15 Apr 2025 17:43:42 +
with message-id
and subject line Bug#1102668: Removed package(s) from unstable
has caused the Debian Bug report #1102668,
regarding RM: ruby-graphlient -- ROM; unused, its dependency has an rc bug
to be marked as done.
This means that you claim t
Your message dated Tue, 15 Apr 2025 17:43:16 +
with message-id
and subject line Bug#1102667: Removed package(s) from unstable
has caused the Debian Bug report #1102667,
regarding RM: ruby-devise-two-factor -- ROM; rc-buggy, unused
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 15 Apr 2025 17:42:24 +
with message-id
and subject line Bug#1102665: Removed package(s) from unstable
has caused the Debian Bug report #1102665,
regarding RM: ruby-devise-token-authenticatable -- ROM; unused leaf package
to be marked as done.
This means that you claim
Your message dated Tue, 15 Apr 2025 17:43:18 +
with message-id
and subject line Bug#1102667: Removed package(s) from unstable
has caused the Debian Bug report #1082382,
regarding ruby-devise-two-factor: CVE-2024-8796
to be marked as done.
This means that you claim that the problem has been de
Your message dated Tue, 15 Apr 2025 17:43:18 +
with message-id
and subject line Bug#1102667: Removed package(s) from unstable
has caused the Debian Bug report #1084360,
regarding ruby-devise-two-factor: FTBFS: failing tests
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 15 Apr 2025 17:41:53 +
with message-id
and subject line Bug#1102636: Removed package(s) from unstable
has caused the Debian Bug report #1100967,
regarding golang-step-crypto-dev and golang-github-smallstep-crypto-dev have
undeclared file conflicts
to be marked as done.
Your message dated Tue, 15 Apr 2025 17:44:13 +
with message-id
and subject line Bug#1102688: Removed package(s) from unstable
has caused the Debian Bug report #1095881,
regarding ruby-devise: autopkgtest failure with rails 7:
/usr/share/rubygems-integration/all/gems/railties-7.2.2.1/lib/rails
Your message dated Tue, 15 Apr 2025 17:44:13 +
with message-id
and subject line Bug#1102688: Removed package(s) from unstable
has caused the Debian Bug report #1033629,
regarding ruby-devise: workaround to pass riscv64 autopkgtest
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 15 Apr 2025 17:43:18 +
with message-id
and subject line Bug#1102667: Removed package(s) from unstable
has caused the Debian Bug report #1009636,
regarding ruby-devise-two-factor: CVE-2021-43177 - possible reuse of OTP due to
incomplete fix for CVE-2015-7225
to be marke
Your message dated Mon, 14 Apr 2025 23:06:09 +
with message-id
and subject line Bug#1092693: fixed in software-properties 0.111-1
has caused the Debian Bug report #1092693,
regarding software-properties-gtk: Does not start FileNotFoundError:
'/usr/bin/apt-key'
to be marked as done.
This mean
Your message dated Mon, 14 Apr 2025 08:34:10 +
with message-id
and subject line Bug#862386: fixed in gnustep-examples 1:1.4.0+git20210703-1
has caused the Debian Bug report #862386,
regarding incomplete build
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Tue, 15 Apr 2025 17:40:27 +
with message-id
and subject line Bug#1102542: Removed package(s) from unstable
has caused the Debian Bug report #1102542,
regarding RM: dante [armel armhf] -- RoQA; no longer builds on armel/armhf
to be marked as done.
This means that you claim t
Your message dated Tue, 15 Apr 2025 17:40:11 +
with message-id
and subject line Bug#1102530: Removed package(s) from unstable
has caused the Debian Bug report #1089267,
regarding memkind: FTBFS with make 4.4.1
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Tue, 15 Apr 2025 17:39:16 +
with message-id
and subject line Bug#1102510: Removed package(s) from unstable
has caused the Debian Bug report #1078314,
regarding qtorganizer-eds: FTBFS: The following tests FAILED: 5 -
recurrence-test (Failed)
to be marked as done.
This means
Your message dated Tue, 15 Apr 2025 17:40:10 +
with message-id
and subject line Bug#1102530: Removed package(s) from unstable
has caused the Debian Bug report #1102530,
regarding RM: memkind -- ROM; dead upstream, library with no users
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Apr 2025 17:39:15 +
with message-id
and subject line Bug#1102510: Removed package(s) from unstable
has caused the Debian Bug report #1102510,
regarding RM: qtorganizer-eds -- ROM; replaced by qtorganizer-mkcal
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Apr 2025 17:39:39 +
with message-id
and subject line Bug#1102509: Removed package(s) from unstable
has caused the Debian Bug report #1102509,
regarding RM: evolution-data-server-lomiri -- ROM; not needed anymore
to be marked as done.
This means that you claim that t
Your message dated Tue, 15 Apr 2025 17:36:48 +
with message-id
and subject line Bug#1102506: Removed package(s) from unstable
has caused the Debian Bug report #1091960,
regarding xfce4-sntray-plugin: FTBFS: mv: cannot stat
'/<>/debian/tmp/usr/lib/xfce4': No such file or directory
to be marked
Your message dated Tue, 15 Apr 2025 17:37:36 +
with message-id
and subject line Bug#1102508: Removed package(s) from unstable
has caused the Debian Bug report #1102508,
regarding RM: lomiri-abook2cal-syncd -- ROM; replaced by contactsd
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Apr 2025 17:36:48 +
with message-id
and subject line Bug#1102506: Removed package(s) from unstable
has caused the Debian Bug report #1086771,
regarding vala-sntray-plugin: Wrong placement of the library file prevents
detection of the plugin by vala-panel
to be marke
Your message dated Tue, 15 Apr 2025 17:37:12 +
with message-id
and subject line Bug#1102507: Removed package(s) from unstable
has caused the Debian Bug report #1102507,
regarding RM: lomiri-sync-monitor -- ROM; not needed anymore
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 15 Apr 2025 17:36:46 +
with message-id
and subject line Bug#1102506: Removed package(s) from unstable
has caused the Debian Bug report #1102506,
regarding RM: xfce4-sntray-plugin -- ROM; upstream inactive
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 15 Apr 2025 17:36:14 +
with message-id
and subject line Bug#1101718: Removed package(s) from unstable
has caused the Debian Bug report #1101718,
regarding RM: rust-extprim -- ROM; unused
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 15 Apr 2025 17:36:16 +
with message-id
and subject line Bug#1101718: Removed package(s) from unstable
has caused the Debian Bug report #1053625,
regarding rust-extprim: Remove from Debian?
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 15 Apr 2025 17:36:48 +
with message-id
and subject line Bug#1102506: Removed package(s) from unstable
has caused the Debian Bug report #1048204,
regarding xfce4-sntray-plugin: Fails to build source after successful build
to be marked as done.
This means that you claim
Your message dated Tue, 15 Apr 2025 17:35:23 +
with message-id
and subject line Bug#1101522: Removed package(s) from unstable
has caused the Debian Bug report #1101522,
regarding RM: python-pytest-flake8 -- ROM; Dead upstream and broken
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Apr 2025 17:35:48 +
with message-id
and subject line Bug#1101696: Removed package(s) from unstable
has caused the Debian Bug report #1101696,
regarding RM: python-glob2 -- ROM; old backport of Python3 stdlib to Python2
to be marked as done.
This means that you claim
Your message dated Tue, 15 Apr 2025 17:35:49 +
with message-id
and subject line Bug#1101696: Removed package(s) from unstable
has caused the Debian Bug report #1085916,
regarding python-glob2: Python SyntaxWarning
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 15 Apr 2025 17:32:35 +
with message-id
and subject line Bug#1099979: Removed package(s) from unstable
has caused the Debian Bug report #330814,
regarding adabrowse: please do not extend the user's project; create a new one
instead
to be marked as done.
This means that
Your message dated Tue, 15 Apr 2025 17:33:56 +
with message-id
and subject line Bug#1099983: Removed package(s) from unstable
has caused the Debian Bug report #934722,
regarding urweb: _FORTIFY_SOURCE=2 causes extreme slowdown
to be marked as done.
This means that you claim that the problem h
Your message dated Tue, 15 Apr 2025 17:34:20 +
with message-id
and subject line Bug#1099985: Removed package(s) from unstable
has caused the Debian Bug report #1099985,
regarding RM: anfo -- RoQA; rc-buggy
to be marked as done.
This means that you claim that the problem has been dealt with.
I
1 - 100 of 232 matches
Mail list logo
