Processing control commands:
> close -1
Bug #1103253 [libmateweather1t64] Mate Weather Applet and Clock fail to load on
startup
Marked Bug as done
> fixed -1 1.26.3-4
Bug #1103253 {Done: Mike Gabriel } [libmateweather1t64]
Mate Weather Applet and Clock fail to load on startup
Marked as fixed in
Your message dated Mon, 12 May 2025 04:34:13 +
with message-id
and subject line Bug#1064135: fixed in r-cran-bigmemory 4.6.4-2
has caused the Debian Bug report #1064135,
regarding src:r-cran-bigmemory: fails to migrate to testing for too long:
autopkgtest fails on arm*, ppc64el and s390x
to b
Your message dated Mon, 12 May 2025 05:50:04 +0200
with message-id
and subject line Re: Bug#1105129: Please backport ntsync driver from Linux-6.14
to trixie
has caused the Debian Bug report #1105129,
regarding Please backport ntsync driver from Linux-6.14 to trixie
to be marked as done.
This mea
Your message dated Mon, 12 May 2025 05:45:26 +0200
with message-id
and subject line Re: Accepted openjdk-8 8u452-ga-1 (source) into unstable
has caused the Debian Bug report #1103900,
regarding openjdk-8: CVE-2025-30698 CVE-2025-30691 CVE-2025-21587
to be marked as done.
This means that you claim
Your message dated Mon, 12 May 2025 05:39:45 +0200
with message-id
and subject line Re: Bug#1102518: linux-image-6.1.0-32-amd64: Microhpone hotkey
event stop working - Lenovo laptop
has caused the Debian Bug report #1102518,
regarding linux-image-6.1.0-32-amd64: Microphone hotkey event stop worki
Your message dated Mon, 12 May 2025 02:37:28 +
with message-id
and subject line Bug#1095932: fixed in openjdk-8 8u452-ga-1
has caused the Debian Bug report #1095932,
regarding openjdk-8: Misbuilds packages when calling only binary-* targets
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 1089972
Bug #1089972 [sponsorship-requests] RFS: gambc/4.9.5-1 -- Gambit Scheme
interpreter and compiler
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1089972: https://bugs.debian.org/cgi
Your message dated Sun, 11 May 2025 22:06:41 +
with message-id
and subject line Bug#1104387: fixed in mdanalysis 2.9.0-8
has caused the Debian Bug report #1104387,
regarding mdanalysis: FTBFS randomly: E: Build killed with signal TERM after
150 minutes of inactivity
to be marked as done.
Thi
Your message dated Sun, 11 May 2025 21:49:10 +
with message-id
and subject line Bug#1104884: fixed in ibm-3270 4.3ga10-5
has caused the Debian Bug report #1104884,
regarding ibm-3270: will FTBFS during trixie support period
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 May 2025 17:42:56 -0400
with message-id
and subject line Re: Bug#1104007: chromium: Chromium opens but is invisible,
takes long to load.
has caused the Debian Bug report #1104007,
regarding chromium: long startup delay on KDE/X11
to be marked as done.
This means that y
Your message dated Sun, 11 May 2025 23:33:52 +0200
with message-id
and subject line Re: RFH: devscripts -- scripts to make the life of a Debian
Package maintainer easier
has caused the Debian Bug report #800413,
regarding RFH: devscripts -- scripts to make the life of a Debian Package
maintainer
Your message dated Sun, 11 May 2025 20:52:27 +
with message-id
and subject line Bug#1105095: fixed in virt-firmware 25.4.1-1
has caused the Debian Bug report #1105095,
regarding virt-firmware: please adapt
debian/patches/pkg_resources-is-deprecated.patch to avoid using the backport
to be mark
Processing commands for cont...@bugs.debian.org:
> close 1099362 2.8.0-2
Bug #1099362 [src:ruby-jekyll-seo-tag] ruby-jekyll-seo-tag: missing build
depdendency on tzdata
Marked as fixed in versions ruby-jekyll-seo-tag/2.8.0-2.
Bug #1099362 [src:ruby-jekyll-seo-tag] ruby-jekyll-seo-tag: missing bui
Processing commands for cont...@bugs.debian.org:
> close 1099356 5.63.0-2
Bug #1099356 [src:ruby-sequel] ruby-sequel: missing build depdendency on tzdata
Marked as fixed in versions ruby-sequel/5.63.0-2.
Bug #1099356 [src:ruby-sequel] ruby-sequel: missing build depdendency on tzdata
Marked Bug as
Processing commands for cont...@bugs.debian.org:
> close 1099360 1.3.7-2
Bug #1099360 [src:ruby-combustion] ruby-combustion: missing build depdendency
on tzdata
Marked as fixed in versions ruby-combustion/1.3.7-2.
Bug #1099360 [src:ruby-combustion] ruby-combustion: missing build depdendency
on t
Processing control commands:
> close -1 0.20.0+ds-3
Bug #1105124 [src:jsonnet] src:jsonnet: fails to migrate to testing for too long
Marked as fixed in versions jsonnet/0.20.0+ds-3.
Bug #1105124 [src:jsonnet] src:jsonnet: fails to migrate to testing for too long
Marked Bug as done
--
1105124: ht
Processing commands for cont...@bugs.debian.org:
> # uncomprehensible
> close 1105116
Bug #1105116 [gcc-12] gcc-12: Implement Latency Modifications
Marked Bug as done
> close 1105115
Bug #1105115 [initramfs-tools-core] initramfs-tools-core: latencies should be
alterable included
Marked Bug as don
Your message dated Sun, 11 May 2025 15:39:24 -
with message-id <20250511153924.3b02b...@debian.org>
and subject line Re: Bug#1102492: RFS: python-pwdlib/0.2.1-1 [ITP] -- Modern
password hashing for Python
has caused the Debian Bug report #1102492,
regarding RFS: python-pwdlib/0.2.1-1 [ITP] --
Processing commands for cont...@bugs.debian.org:
> reassign 1103183 libfckit0d
Bug #1103183 {Done: Alastair McKinstry } [fckit]
atlas-ecmwf: FTBFS: /usr/bin/ld: /lib/x86_64-linux-gnu/libfckit-gfortran.so.0d:
undefined reference to
`eckit::Exception::Exception(std::__cxx11::basic_string, std::al
Your message dated Sun, 11 May 2025 13:49:36 +
with message-id
and subject line Bug#1083728: fixed in pythran 0.17.0+ds-2
has caused the Debian Bug report #1083728,
regarding pythran: (build-)depends on deprecated module python3-pkg-resources
to be marked as done.
This means that you claim th
Your message dated Sun, 11 May 2025 13:20:21 +
with message-id
and subject line Bug#1104890: fixed in syslog-ng 4.8.1-5
has caused the Debian Bug report #1104890,
regarding syslog-ng: CVE-2024-47619
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> reassign 1104836 src:atf
Bug #1104836 [src:ifupdown-ng] ifupdown-ng: FTBFS: atf-check: ERROR: Caught
unexpected error: cannot create std::vector larger than max_size()
Bug reassigned from package 'src:ifupdown-ng' to 'src:atf'.
No longer marked a
Your message dated Sun, 11 May 2025 12:17:26 +
with message-id
and subject line unblock rust-asahi-btsync
has caused the Debian Bug report #1105048,
regarding unblock: rust-asahi-btsync/0.2.4-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Sun, 11 May 2025 11:34:31 +
with message-id
and subject line Bug#1101007: fixed in gnupg2 2.4.7-18
has caused the Debian Bug report #1101007,
regarding regression: gpg --edit-key clean removes signature that was kept in
2.2.45
to be marked as done.
This means that you clai
Your message dated Sun, 11 May 2025 13:07:24 +0200
with message-id
and subject line autogen/experimental was dropped, closing
experimental-specific file conflict bug
has caused the Debian Bug report #1104988,
regarding autogen has an undeclared file conflict on
/usr/share/aclocal/autoopts.m4
to
Your message dated Sun, 11 May 2025 10:15:37 +
with message-id
and subject line Bug#1105081: Removed package(s) from unstable
has caused the Debian Bug report #1105081,
regarding RM: haskell-x509-util -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been d
Your message dated Sun, 11 May 2025 10:11:40 +
with message-id
and subject line Bug#1105073: Removed package(s) from unstable
has caused the Debian Bug report #1082534,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #426041,
regarding lomoco: Add support for MX600
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #426855,
regarding lomoco: Writing to USB device: RES: Broken pipe
to be marked as done.
This means that you claim that the problem ha
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #810446,
regarding lomoco: please switch to libusb 1.0
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #682617,
regarding O: lomoco -- Logitech Mouse Control for USB mice
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #669614,
regarding O: lomoco -- Logitech Mouse Control for USB mice
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #437152,
regarding lomoco: Please support Logitech G3 Laser Mouse
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #498127,
regarding lomoco: Add support for MX 518 Gaming-grade mouse
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #414097,
regarding lomoco: Please support MX Revolution
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #395261,
regarding lomoco: does not notice failure to set resolution
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #360259,
regarding lomoco: doesn't support mice connected via a PS/2 adapter
to be marked as done.
This means that you claim that the
Your message dated Sun, 11 May 2025 10:18:10 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #1105091,
regarding RM: lomoco -- RoQA; upstream dead, orphaned
to be marked as done.
This means that you claim that the problem has b
Your message dated Sun, 11 May 2025 10:18:16 +
with message-id
and subject line Bug#1105091: Removed package(s) from unstable
has caused the Debian Bug report #1047178,
regarding lomoco: Fails to build source after successful build
to be marked as done.
This means that you claim that the prob
Your message dated Sun, 11 May 2025 10:17:36 +
with message-id
and subject line Bug#1105089: Removed package(s) from unstable
has caused the Debian Bug report #790732,
regarding O: sortmail -- simple mail sorter
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sun, 11 May 2025 10:17:36 +
with message-id
and subject line Bug#1105089: Removed package(s) from unstable
has caused the Debian Bug report #257095,
regarding sortmail: FTBFS(hurd-i386): unconditional use of MAXPATHLEN and
MAXHOSTNAMELEN
to be marked as done.
This means th
Your message dated Sun, 11 May 2025 10:17:33 +
with message-id
and subject line Bug#1105089: Removed package(s) from unstable
has caused the Debian Bug report #1105089,
regarding RM: sortmail -- RoQA; obsolete, orphaned
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 11 May 2025 10:17:36 +
with message-id
and subject line Bug#1105089: Removed package(s) from unstable
has caused the Debian Bug report #1097908,
regarding sortmail: ftbfs with GCC-15
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 11 May 2025 10:16:06 +
with message-id
and subject line Bug#1105082: Removed package(s) from unstable
has caused the Debian Bug report #1105082,
regarding RM: haskell-web-routes-boomerang -- ROM; obsolete
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 11 May 2025 10:16:37 +
with message-id
and subject line Bug#1105083: Removed package(s) from unstable
has caused the Debian Bug report #1084756,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:16:34 +
with message-id
and subject line Bug#1105083: Removed package(s) from unstable
has caused the Debian Bug report #1105083,
regarding RM: haskell-web-routes-happstack -- ROM; obsolete
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 11 May 2025 10:17:03 +
with message-id
and subject line Bug#1105084: Removed package(s) from unstable
has caused the Debian Bug report #1105084,
regarding RM: haskell-web-routes-th -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has be
Your message dated Sun, 11 May 2025 10:17:06 +
with message-id
and subject line Bug#1105084: Removed package(s) from unstable
has caused the Debian Bug report #1084757,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:16:07 +
with message-id
and subject line Bug#1105082: Removed package(s) from unstable
has caused the Debian Bug report #1084755,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:15:07 +
with message-id
and subject line Bug#1105080: Removed package(s) from unstable
has caused the Debian Bug report #1105080,
regarding RM: haskell-tagshare -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 11 May 2025 10:15:39 +
with message-id
and subject line Bug#1105081: Removed package(s) from unstable
has caused the Debian Bug report #1082922,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:15:09 +
with message-id
and subject line Bug#1105080: Removed package(s) from unstable
has caused the Debian Bug report #1082565,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:12:10 +
with message-id
and subject line Bug#1105074: Removed package(s) from unstable
has caused the Debian Bug report #1085428,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:14:41 +
with message-id
and subject line Bug#1105079: Removed package(s) from unstable
has caused the Debian Bug report #1085437,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:12:36 +
with message-id
and subject line Bug#1105075: Removed package(s) from unstable
has caused the Debian Bug report #1105075,
regarding RM: haskell-set-extra -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been d
Your message dated Sun, 11 May 2025 10:14:38 +
with message-id
and subject line Bug#1105079: Removed package(s) from unstable
has caused the Debian Bug report #1105079,
regarding RM: haskell-presburger -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 11 May 2025 10:10:45 +
with message-id
and subject line Bug#1105072: Removed package(s) from unstable
has caused the Debian Bug report #907110,
regarding Updating the lhs2tex Uploaders list
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 10:14:11 +
with message-id
and subject line Bug#1105078: Removed package(s) from unstable
has caused the Debian Bug report #1105078,
regarding RM: haskell-regexpr -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sun, 11 May 2025 10:13:07 +
with message-id
and subject line Bug#1105076: Removed package(s) from unstable
has caused the Debian Bug report #1105076,
regarding RM: haskell-publicsuffixlist -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 May 2025 10:11:39 +
with message-id
and subject line Bug#1105073: Removed package(s) from unstable
has caused the Debian Bug report #1105073,
regarding RM: haskell-mime -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 10:10:05 +
with message-id
and subject line Bug#1105071: Removed package(s) from unstable
has caused the Debian Bug report #1105071,
regarding RM: haskell-libxml-sax -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 11 May 2025 10:13:43 +
with message-id
and subject line Bug#1105077: Removed package(s) from unstable
has caused the Debian Bug report #1105077,
regarding RM: haskell-options -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sun, 11 May 2025 10:12:09 +
with message-id
and subject line Bug#1105074: Removed package(s) from unstable
has caused the Debian Bug report #1105074,
regarding RM: only -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:13:44 +
with message-id
and subject line Bug#1105077: Removed package(s) from unstable
has caused the Debian Bug report #1082184,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:10:43 +
with message-id
and subject line Bug#1105072: Removed package(s) from unstable
has caused the Debian Bug report #1105072,
regarding RM: lhs2tex -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 11 May 2025 10:14:13 +
with message-id
and subject line Bug#1105078: Removed package(s) from unstable
has caused the Debian Bug report #1082536,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:10:45 +
with message-id
and subject line Bug#1105072: Removed package(s) from unstable
has caused the Debian Bug report #1082301,
regarding Removal notice: orphaned
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:13:10 +
with message-id
and subject line Bug#1105076: Removed package(s) from unstable
has caused the Debian Bug report #1082006,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:10:07 +
with message-id
and subject line Bug#1105071: Removed package(s) from unstable
has caused the Debian Bug report #1081369,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:10:45 +
with message-id
and subject line Bug#1105072: Removed package(s) from unstable
has caused the Debian Bug report #1048248,
regarding lhs2tex: Fails to build source after successful build
to be marked as done.
This means that you claim that the pro
Your message dated Sun, 11 May 2025 10:12:39 +
with message-id
and subject line Bug#1105075: Removed package(s) from unstable
has caused the Debian Bug report #1081387,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:00:50 +
with message-id
and subject line Bug#1105032: Removed package(s) from unstable
has caused the Debian Bug report #1082413,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 09:59:47 +
with message-id
and subject line Bug#1105031: Removed package(s) from unstable
has caused the Debian Bug report #1082352,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:05:59 +
with message-id
and subject line Bug#1105058: Removed package(s) from unstable
has caused the Debian Bug report #1081386,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:08:54 +
with message-id
and subject line Bug#1105070: Removed package(s) from unstable
has caused the Debian Bug report #1105070,
regarding RM: haskell-hcwiid -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 11 May 2025 10:06:43 +
with message-id
and subject line Bug#1105060: Removed package(s) from experimental
has caused the Debian Bug report #1105060,
regarding RM: autogen/experimental -- ROM; Old development version, will not be
released since upstream is dead.
to be m
Your message dated Sun, 11 May 2025 10:08:04 +
with message-id
and subject line Bug#1105069: Removed package(s) from unstable
has caused the Debian Bug report #422310,
regarding libghc6-ldap-dev: unknown exception when using ldapOpen
to be marked as done.
This means that you claim that the pr
Your message dated Sun, 11 May 2025 10:08:04 +
with message-id
and subject line Bug#1105069: Removed package(s) from unstable
has caused the Debian Bug report #404275,
regarding ldap-haskell-doc: Please include a minimal usage example
to be marked as done.
This means that you claim that the p
Your message dated Sun, 11 May 2025 10:08:55 +
with message-id
and subject line Bug#1105070: Removed package(s) from unstable
has caused the Debian Bug report #1093530,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:08:02 +
with message-id
and subject line Bug#1105069: Removed package(s) from unstable
has caused the Debian Bug report #1105069,
regarding RM: ldap-haskell -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 10:07:22 +
with message-id
and subject line Bug#1105068: Removed package(s) from unstable
has caused the Debian Bug report #1105068,
regarding RM: haskell-hsp -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sun, 11 May 2025 10:06:26 +
with message-id
and subject line Bug#1105059: Removed package(s) from unstable
has caused the Debian Bug report #1105059,
regarding RM: haskell-qrencode -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 11 May 2025 10:05:28 +
with message-id
and subject line Bug#1105046: Removed package(s) from unstable
has caused the Debian Bug report #1105046,
regarding RM: haskell-cryptohash-cryptoapi -- ROM; obsolete
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 11 May 2025 10:05:58 +
with message-id
and subject line Bug#1105058: Removed package(s) from unstable
has caused the Debian Bug report #1105058,
regarding RM: haskell-gsasl -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 10:08:04 +
with message-id
and subject line Bug#1105069: Removed package(s) from unstable
has caused the Debian Bug report #1082566,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:06:27 +
with message-id
and subject line Bug#1105059: Removed package(s) from unstable
has caused the Debian Bug report #1082563,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:05:31 +
with message-id
and subject line Bug#1105046: Removed package(s) from unstable
has caused the Debian Bug report #1082561,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:07:23 +
with message-id
and subject line Bug#1105068: Removed package(s) from unstable
has caused the Debian Bug report #1082353,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 09:58:36 +
with message-id
and subject line Bug#1104974: Removed package(s) from unstable
has caused the Debian Bug report #743952,
regarding chronicle: Support for subdirectories in 'input'
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 11 May 2025 09:58:36 +
with message-id
and subject line Bug#1104974: Removed package(s) from unstable
has caused the Debian Bug report #696577,
regarding chronicle: funny calendar
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:03:13 +
with message-id
and subject line Bug#1105044: Removed package(s) from unstable
has caused the Debian Bug report #1084124,
regarding haskell-connection: FTBFS: Couldn't match expected type
to be marked as done.
This means that you claim that the p
Your message dated Sun, 11 May 2025 10:03:13 +
with message-id
and subject line Bug#1105044: Removed package(s) from unstable
has caused the Debian Bug report #1085013,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:04:17 +
with message-id
and subject line Bug#1102108: fixed in licenserecon 5.0
has caused the Debian Bug report #1102108,
regarding Files with multiple OR licensing options
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 11 May 2025 09:58:36 +
with message-id
and subject line Bug#1104974: Removed package(s) from unstable
has caused the Debian Bug report #696674,
regarding chronicle: cache and comments don't play well together
to be marked as done.
This means that you claim that the pro
Your message dated Sun, 11 May 2025 10:03:10 +
with message-id
and subject line Bug#1105044: Removed package(s) from unstable
has caused the Debian Bug report #1105044,
regarding RM: haskell-connection -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 11 May 2025 10:04:33 +
with message-id
and subject line Bug#1105045: Removed package(s) from unstable
has caused the Debian Bug report #1105045,
regarding RM: haskell-failure -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sun, 11 May 2025 10:04:36 +
with message-id
and subject line Bug#1105045: Removed package(s) from unstable
has caused the Debian Bug report #1082347,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sun, 11 May 2025 10:00:47 +
with message-id
and subject line Bug#1105032: Removed package(s) from unstable
has caused the Debian Bug report #1105032,
regarding RM: haskell-reform -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 11 May 2025 10:02:27 +
with message-id
and subject line Bug#1105043: Removed package(s) from unstable
has caused the Debian Bug report #1105043,
regarding RM: haskell-cryptohash-conduit -- ROM; obsolete
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 11 May 2025 10:01:44 +
with message-id
and subject line Bug#1105042: Removed package(s) from unstable
has caused the Debian Bug report #1105042,
regarding RM: haskell-bool-extras -- ROM; obsolete
to be marked as done.
This means that you claim that the problem has been
1 - 100 of 127 matches
Mail list logo
