Your message dated Sun, 20 Nov 2022 07:51:31 +
with message-id
and subject line Bug#1024135: fixed in rust-sysinfo 0.26.7-1
has caused the Debian Bug report #1024135,
regarding rust-sysinfo: please upgrade to 0.24
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 20 Nov 2022 07:15:52 +0100
with message-id
and subject line Re: Bug#985701: python-mako-doc: broken symlinks:
/usr/share/doc/python-mako/rst -> ../python-mako-doc/rst -> html/_sources
has caused the Debian Bug report #985701,
regarding python-mako-doc: broken symlinks:
Your message dated Sun, 20 Nov 2022 02:35:53 +
with message-id
and subject line Bug#1023234: fixed in gnuradio 3.10.4.0-4
has caused the Debian Bug report #1023234,
regarding gnuradio FTCBFS: unsatisfiable sphinx dependency
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 20 Nov 2022 01:06:19 +
with message-id
and subject line Bug#960278: fixed in python-debian 0.1.49
has caused the Debian Bug report #960278,
regarding python-debian: Don't loose whitespace information when editing
Copyright.files
to be marked as done.
This means that
Your message dated Sun, 20 Nov 2022 01:06:19 +
with message-id
and subject line Bug#1011937: fixed in python-debian 0.1.49
has caused the Debian Bug report #1011937,
regarding Make python-debian (more) portable
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 20 Nov 2022 00:51:55 +
with message-id
and subject line Bug#1018909: fixed in kwallet-kf5 5.100.0-1
has caused the Debian Bug report #1018909,
regarding libkf5wallet-bin: Cannot disable Freedesktop Secret Service
to be marked as done.
This means that you claim that
Your message dated Sun, 20 Nov 2022 00:19:05 +
with message-id
and subject line Bug#1024313: fixed in amgcl 1.4.3-3
has caused the Debian Bug report #1024313,
regarding amgcl: b-d on python3-all-dev, but not built for all supported
Python3 versions
to be marked as done.
This means that you
Your message dated Sun, 20 Nov 2022 00:06:41 +
with message-id
and subject line Bug#1024265: fixed in opengv 1.0+1git91f4b1-7
has caused the Debian Bug report #1024265,
regarding opengv: Build for all supported python3 versions or Build-Depend on
python3-dev
to be marked as done.
This means
Your message dated Sun, 20 Nov 2022 00:04:33 +
with message-id
and subject line Bug#328498: fixed in cdebconf 0.265
has caused the Debian Bug report #328498,
regarding switch to cdebconf as default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 20 Nov 2022 00:05:09 +
with message-id
and subject line Bug#1022124: fixed in libdbd-oracle-perl 1.80-4
has caused the Debian Bug report #1022124,
regarding libdbd-oracle-perl needs binaries uploaded for the perl 5.36
transitions
to be marked as done.
This means that
Your message dated Sun, 20 Nov 2022 00:04:33 +
with message-id
and subject line Bug#1006492: fixed in cdebconf 0.265
has caused the Debian Bug report #1006492,
regarding cdebconf should not depend on debconf
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> close 982145
Bug #982145 [sponsorship-requests] RFS: fuzzel/1.8.2-1 [ITP] -- Application
launcher for wlroots based Wayland compositors
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
982145:
Your message dated Sat, 19 Nov 2022 23:39:53 +
with message-id
and subject line Bug#1023101: fixed in llvm-toolchain-15 1:15.0.5-2
has caused the Debian Bug report #1023101,
regarding llvm-15 ftbfs on mips64el
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 19 Nov 2022 23:39:53 +
with message-id
and subject line Bug#1022577: fixed in llvm-toolchain-15 1:15.0.5-2
has caused the Debian Bug report #1022577,
regarding llvm-toolchain-15: Mesa on armel,armhf fails with LLVM ERROR: Cannot
select
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> close 1022523
Bug #1022523 [src:lttnganalyses] lttnganalyses: FTBFS: AssertionError: "Error:
Cannot open trace: 'utf-8' codec [53 chars]byte" != 'Timerange: [1970-01-01
00:00:01.[1221 chars]3%\n'
Marked Bug as done
> thanks
Stopping
Your message dated Sun, 20 Nov 2022 01:17:23 +0200
with message-id
and subject line 1.8 is now in unstable
has caused the Debian Bug report #999863,
regarding gnome-subtitles: new upstream release 1.7.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 19 Nov 2022 23:06:08 +
with message-id
and subject line Bug#1023420: fixed in libvirt 8.9.0-1
has caused the Debian Bug report #1023420,
regarding libvirt FTBFS: missing Build-Depends: mount
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> reassign 1022375 llvm-14-dev
Bug #1022375 [src:halide] halide: FTBFS: make[2]: *** [debian/rules:97:
perform_stage_build] Error 2
Bug reassigned from package 'src:halide' to 'llvm-14-dev'.
No longer marked as found in versions halide/14.0.0-2.
Processing control commands:
> fixed -1 1:15.0.5-1
Bug #1022551 [llvm-15-dev] llvm-15's cmake now requires clang-tools-15,
clang-tidy-15, clangd-15, even if unused
Marked as fixed in versions llvm-toolchain-15/1:15.0.5-1.
> close -1
Bug #1022551 [llvm-15-dev] llvm-15's cmake now requires
Your message dated Sat, 19 Nov 2022 22:10:32 +
with message-id
and subject line Bug#1020064: fixed in tcsh 6.21.00-2
has caused the Debian Bug report #1020064,
regarding tcsh: FTBFS: | ./conftest.c:20: undefined reference to `crypt'
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 22:10:32 +
with message-id
and subject line Bug#999754: fixed in tcsh 6.21.00-2
has caused the Debian Bug report #999754,
regarding tcsh: character class expansion is badly broken
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 21:22:02 +
with message-id
and subject line Bug#1022283: fixed in python-wikkid 0.4-1
has caused the Debian Bug report #1022283,
regarding python-wikkid: FTBFS: ModuleNotFoundError: No module named
'breezy.merge3'
to be marked as done.
This means that you
Your message dated Sat, 19 Nov 2022 20:37:10 +
with message-id
and subject line Bug#1023227: fixed in breezy 3.3.0+bzr7661-5
has caused the Debian Bug report #1023227,
regarding breezy: autopkgtest regression: Non-UTF-8 code starting with '\xf2'
in file /usr/bin/brz
to be marked as done.
Your message dated Sat, 19 Nov 2022 19:53:13 +
with message-id
and subject line Bug#973922: fixed in radvd 1:2.19-1
has caused the Debian Bug report #973922,
regarding New upstream (2.19)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Processing commands for cont...@bugs.debian.org:
> close 1024452
Bug #1024452 [sponsorship-requests] RFS: cbonsai/1.3.1-1 -- terminal-based
bonsai tree generator
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1024452:
Your message dated Sat, 19 Nov 2022 19:47:26 +
with message-id
and subject line Bug#1024267: fixed in krb5 1.18.3-6+deb11u3
has caused the Debian Bug report #1024267,
regarding krb5: CVE-2022-42898: integer overflows in PAC parsing
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 19:49:18 +
with message-id
and subject line Bug#1024249: fixed in wordpress 5.7.8+dfsg1-0+deb11u2
has caused the Debian Bug report #1024249,
regarding wordpress: update to 5.7.8+dfsg1-0+deb11u1 have missing dependencies
in bullseye-security
to be marked as
Your message dated Sat, 19 Nov 2022 19:49:17 +
with message-id
and subject line Bug#1022575: fixed in wordpress 5.7.8+dfsg1-0+deb11u1
has caused the Debian Bug report #1022575,
regarding wordpress: Wordpress 6.0.3 security release 16 issues
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 19:35:30 +
with message-id
and subject line Bug#1024227: fixed in gpodder 3.11.0-3
has caused the Debian Bug report #1024227,
regarding gpodder: please change suggests from youtube-dl to yt-dlp
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 19:41:36 +0100
with message-id
and subject line Re: Bug#1020799: Transition: pkg-config to pkgconf: 2022-11-11
has caused the Debian Bug report #1020799,
regarding transition: pkg-config
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 18:17:51 +
with message-id
and subject line Bug#1021668: fixed in xen 4.14.5+86-g1c354767d5-1
has caused the Debian Bug report #1021668,
regarding xen: CVE-2022-33749 CVE-2022-33748 CVE-2022-33747 CVE-2022-33746
to be marked as done.
This means that you
Your message dated Sat, 19 Nov 2022 18:17:08 +
with message-id
and subject line Bug#1023427: fixed in pixman 0.40.0-1.1~deb11u1
has caused the Debian Bug report #1023427,
regarding pixman: CVE-2022-44638
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 19 Nov 2022 17:56:37 +0100
with message-id <5d8ca557-c50f-8214-f63c-5ad41f792...@debian.org>
and subject line Close Bug #961365
has caused the Debian Bug report #961365,
regarding ITP: jacksum -- Computes checksums, CRCs and message digests
to be marked as done.
This means
Your message dated Sat, 19 Nov 2022 17:49:55 +
with message-id
and subject line Bug#1024243: fixed in dbus-fast 1.75.0-2
has caused the Debian Bug report #1024243,
regarding python3-dbus-fast: significant increase in installation size due to
new dependencies
to be marked as done.
This means
Your message dated Sat, 19 Nov 2022 17:05:17 +
with message-id
and subject line Bug#950284: fixed in libclass-dbi-plugin-abstractcount-perl
0.08-3
has caused the Debian Bug report #950284,
regarding Remove me from Uploaders
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 19 Nov 2022 16:35:51 +
with message-id
and subject line Bug#1024272: fixed in jhead 1:3.06.0.1-5
has caused the Debian Bug report #1024272,
regarding jhead: CVE-2021-34055: heap-buffer-overflow of exif.c in function
Put16u
to be marked as done.
This means that you
Your message dated Sat, 19 Nov 2022 16:18:23 +
with message-id
and subject line Bug#1019007: fixed in util-linux 2.38.1-3
has caused the Debian Bug report #1019007,
regarding rfkill(8): List options for supported device types
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 19 Nov 2022 16:18:23 +
with message-id
and subject line Bug#1003095: fixed in util-linux 2.38.1-3
has caused the Debian Bug report #1003095,
regarding /usr/bin/script: hangs when child doesn't read input fast enough
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 16:14:04 +
with message-id
and subject line Bug#1021971: fixed in pychopper 2.7.2-1
has caused the Debian Bug report #1021971,
regarding python3-pychopper: New upstream release available, but routine-update
fails.
to be marked as done.
This means that you
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #437035,
regarding gkrellm-x86info: not handling nostrip build option (policy 10.1)
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #998977,
regarding gkrellm-x86info: missing required debian/rules targets build-arch
and/or build-indep
to be marked as done.
This
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #669731,
regarding [PATCH] gkrellm-x86info: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #967415,
regarding gkrellm-x86info: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #501280,
regarding gkrellm-x86info shows garbage frequency
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #253524,
regarding gkrellm-x86info ignores Pentium 4 modulation
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 19 Nov 2022 15:44:54 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #1002714,
regarding gkrellm-x86info: Obsoleted by gkrellm-cpufreq?
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 19 Nov 2022 15:44:47 +
with message-id
and subject line Bug#1024411: Removed package(s) from unstable
has caused the Debian Bug report #1024411,
regarding RM: gkrellm-x86info -- RoQA; unmaintained, RC-buggy, dead upstream,
replacement exists
to be marked as done.
Your message dated Sat, 19 Nov 2022 15:43:33 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #999301,
regarding vsdump: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #999150,
regarding cryptcat: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #998948,
regarding ibam: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that
Your message dated Sat, 19 Nov 2022 15:42:30 +
with message-id
and subject line Bug#1024407: Removed package(s) from unstable
has caused the Debian Bug report #998928,
regarding scim-canna: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means
Your message dated Sat, 19 Nov 2022 15:44:02 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #994639,
regarding O: dvbsnoop -- DVB / MPEG stream analyzer
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #967534,
regarding ibam: depends on deprecated GTK 2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 19 Nov 2022 15:43:33 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #965868,
regarding vsdump: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:44:02 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #965497,
regarding dvbsnoop: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #965470,
regarding cryptcat: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #948599,
regarding cryptcat FTCBFS: builds for the build architecture
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #928162,
regarding ibam FTCBFS: uses the build architecture toolchain
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:44:02 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #780222,
regarding dvbsnoop: out-of-bounds read
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #670928,
regarding [PATCH] cryptcat: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:43:33 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #829917,
regarding vsdump: Uses deprecated gnome-common macros/variables
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #790506,
regarding Please support ARM64 (add arm64 to architecture line)
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #715415,
regarding cryptcats "hashingfunction" is stupid
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #670977,
regarding cryptcat: Update 2003 version to 1.2 2005
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #700157,
regarding ibam: doesn't work if battery isn't BAT0
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:41:59 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #670928,
regarding [PATCH] cryptcat: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #669862,
regarding [PATCH] ibam: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:43:33 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #664396,
regarding [PATCH] vsdump: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #656286,
regarding ibam FTBFS on armhf, architecture list mismatch in debian/control
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #650377,
regarding ibam --plotdeviations causes a syntax error in gnuplot
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:42:30 +
with message-id
and subject line Bug#1024407: Removed package(s) from unstable
has caused the Debian Bug report #558631,
regarding Missing autoreconf to fix 554821 or similar bugs in the future
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:44:02 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #644248,
regarding dvbsnoop: continuity counter checking wrong in presence of adaptation
field
to be marked as done.
This means that
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #498302,
regarding gkrellm-ibam: Typo in german description
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #414560,
regarding ibam: Doesn't work with more than one battery
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 19 Nov 2022 15:42:30 +
with message-id
and subject line Bug#1024407: Removed package(s) from unstable
has caused the Debian Bug report #407367,
regarding scim-canna: incorrect source character encoding
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #243259,
regarding ibam: Misbehaving
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #260530,
regarding The ibam package needs an init.d script + a mini daemon
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #171766,
regarding wishlist: more explanation of output
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #160091,
regarding ibam: Bad graph
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #160091,
regarding ibam: Plot needs annotation!
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #153713,
regarding gkrellm-ibam: Default text is too wide
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 19 Nov 2022 15:43:05 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #153421,
regarding ibam doesn't seem to know about suspend/standby
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 19 Nov 2022 15:43:56 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #1024410,
regarding RM: dvbsnoop -- RoQA; unmaintained, RC-buggy, dead upstream
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:43:29 +
with message-id
and subject line Bug#1024409: Removed package(s) from unstable
has caused the Debian Bug report #1024409,
regarding RM: vsdump -- RoQA; unmaintained, RC-buggy, dead upstream
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:42:52 +
with message-id
and subject line Bug#1024408: Removed package(s) from unstable
has caused the Debian Bug report #1024408,
regarding RM: ibam -- RoQA; unmaintained, RC-buggy, dead upstream
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:42:25 +
with message-id
and subject line Bug#1024407: Removed package(s) from unstable
has caused the Debian Bug report #1024407,
regarding RM: scim-canna -- RoQA; unmaintained, RC-buggy, dead upstream
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:41:54 +
with message-id
and subject line Bug#1024406: Removed package(s) from unstable
has caused the Debian Bug report #1024406,
regarding RM: cryptcat -- RoQA; unmaintained, RC-buggy, dead upstream
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:41:25 +
with message-id
and subject line Bug#1024393: Removed package(s) from unstable
has caused the Debian Bug report #1024393,
regarding RM: pyparsing2 -- ROM (team); no rdeps; newer version in Debian
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:44:02 +
with message-id
and subject line Bug#1024410: Removed package(s) from unstable
has caused the Debian Bug report #1005986,
regarding Please migrate away from dpatch
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 19 Nov 2022 15:42:30 +
with message-id
and subject line Bug#1024407: Removed package(s) from unstable
has caused the Debian Bug report #1005984,
regarding Please migrate away from dpatch
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #996331,
regarding llvm-toolchain-11: [mips64el] LLVM ERROR: 64-bit code requested on a
subtarget that doesn't support it!
to be
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #995140,
regarding llvm-11-runtime: replace "which" by "command -v" in postinst script
to be marked as done.
This means that you
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #992349,
regarding libclang-common-11-dev: Cannot install amd64 and armhf together
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #990101,
regarding clang-11: Problem building mixed C & C++ code with UBSan sanitizer
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:37:56 +
with message-id
and subject line Bug#1024339: Removed package(s) from unstable
has caused the Debian Bug report #987090,
regarding O: ion -- NASA implementation of Delay-Tolerant Networking (DTN)
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #986746,
regarding systemd: Symbols are missing when building systemd by Clang
to be marked as done.
This means that you claim that
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #979495,
regarding clang_delta (creduce, cvise) segfaults when built with LLVM 11
to be marked as done.
This means that you claim
Your message dated Sat, 19 Nov 2022 15:37:21 +
with message-id
and subject line Bug#1024338: Removed package(s) from unstable
has caused the Debian Bug report #984936,
regarding O: setcolortemperature -- Set screen color temperature
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #981610,
regarding libllvm11: segfault in writeConstants () llvm/ADT/DenseMap.h:613 on
i386
to be marked as done.
This means that
Your message dated Sat, 19 Nov 2022 15:36:25 +
with message-id
and subject line Bug#1000941: Removed package(s) from unstable
has caused the Debian Bug report #978943,
regarding clang-check dumps stack trace with no CLI args
to be marked as done.
This means that you claim that the problem
1 - 100 of 163 matches
Mail list logo
