Your message dated Fri, 11 Feb 2022 06:19:16 +
with message-id
and subject line Bug#1004280: fixed in raspi-firmware 1.20220120+ds-1
has caused the Debian Bug report #1004280,
regarding raspi-firmware: Autogenerated-file warning fixes and clarification
for config.txt
to be marked as done.
Th
Your message dated Fri, 11 Feb 2022 06:00:08 +
with message-id
and subject line Bug#1002911: fixed in zlmdb 21.1.1-1
has caused the Debian Bug report #1002911,
regarding ITP: zlmdb -- Object-relational in-memory database layer based on LMDB
to be marked as done.
This means that you claim that
Your message dated Fri, 11 Feb 2022 05:22:40 +
with message-id
and subject line Bug#995720: Removed package(s) from unstable
has caused the Debian Bug report #995720,
regarding RM: perl6-tap-harness -- ROM; obsolete, replaced by raku-tap-harness
to be marked as done.
This means that you claim
Your message dated Fri, 11 Feb 2022 05:22:47 +
with message-id
and subject line Bug#995720: Removed package(s) from unstable
has caused the Debian Bug report #994651,
regarding Updating the perl6-tap-harness Uploaders list
to be marked as done.
This means that you claim that the problem has b
Your message dated Fri, 11 Feb 2022 05:13:57 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #974789,
regarding RM: llvm-toolchain-9 -- ROM; Try to limit the number of llvm versions
to be marked as done.
This means that you clai
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #961547,
regarding clang++ fails to find libstdc++ headers if libgcc-10-dev is installed
but libstdc++-10 is not.
to be marked as done.
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #959116,
regarding llvm-toolchain-9: Enabling -fPIE by default like gcc?
to be marked as done.
This means that you claim that the probl
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #954322,
regarding llvm-9: Should build-depend on libxml2-dev
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #951675,
regarding z3 causing llvm linking issues
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #945310,
regarding clang-9: Sanitizer suppressions file can not be parsed
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #945073,
regarding libclang-common-9-dev: missing libclang_rt.fuzzer-i386.a
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #944319,
regarding lld-9: please package development headers
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #852746,
regarding crash if multiple ICDs dynamically linked to LLVM: LLVM ERROR:
inconsistency in registered CommandLine options
to be
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #852746,
regarding Gimp fails to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #942826,
regarding python-clang-9 should be merged with python3-clang-9
to be marked as done.
This means that you claim that the proble
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #943816,
regarding Please get rid of python2 dependencies
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #941817,
regarding llvm-toolchain-9: FTBFS on x32
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #852746,
regarding gimp: Failure to start - GTK problem
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #852746,
regarding gimp: Crashes on startup with "Option 'polly' registered more than
once"
to be marked as done.
This means that you
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #1000850,
regarding FTBFS on armhf and s390x: Build killed with signal TERM after 150
minutes of inactivity
to be marked as done.
This
Your message dated Fri, 11 Feb 2022 05:14:09 +
with message-id
and subject line Bug#974789: Removed package(s) from unstable
has caused the Debian Bug report #1000838,
regarding libclang-cpp9: +b1 binNMU segfaults in pocl
to be marked as done.
This means that you claim that the problem has be
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #997211,
regarding fam: FTBFS: Client.c++:29:10: fatal error: rpc/rpc.h: No such file or
directory
to be marked as done.
This means th
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #865158,
regarding fam: please build-depend on automake, not obsolete automake1.11
to be marked as done.
This means that you claim that
Your message dated Fri, 11 Feb 2022 05:06:41 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #966273,
regarding RM: fam -- RoQA; replaced by gamin; unmaintained; upstream dead
to be marked as done.
This means that you claim that
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #644201,
regarding libfam0: libfam exports C++ class "Client" which is not part of
public API
to be marked as done.
This means that yo
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #572242,
regarding Reopen bug 252896
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #556020,
regarding famd uses port 783, which was later claimed by SpamAssassin
to be marked as done.
This means that you claim that the
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #523906,
regarding fam: incredibly slow 1st kde login
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #483811,
regarding /usr/sbin/famd: famd stops with a segfault.
to be marked as done.
This means that you claim that the problem has bee
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #483811,
regarding [fam] fam segfaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #485499,
regarding famd: Lots of "connect: Connection refused" messages from LTSP clients
to be marked as done.
This means that you cla
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #449601,
regarding fam: Frequent messages "stat on $file failed" in syslog
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #446159,
regarding famd do not send events about file creation/modification
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #403272,
regarding libfam0: libfam doesn't need to link libstdc++
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #395107,
regarding fam 2.7.0-6sarge1 manpage for famd references famd.conf - should be
fam.conf
to be marked as done.
This means that
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #332847,
regarding libfam0c102 is not replaced automatically by libfam0 on upgrades
to be marked as done.
This means that you claim tha
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #331413,
regarding fam: can't unmount cdrom
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #331413,
regarding fam: Prevents disk umount
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #315591,
regarding Installing fam removes all packages that depend on ligamin0
to be marked as done.
This means that you claim that the
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #315591,
regarding Installing fam removes all packages that depend on ligamin0
to be marked as done.
This means that you claim that the
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #302428,
regarding famd has a limit of about 1024 monitor requests
to be marked as done.
This means that you claim that the problem ha
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #302428,
regarding nautilus blocks execution of gedit / file-roller when browsing
/usr/share/doc
to be marked as done.
This means that
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #302428,
regarding fam: stop monitoring directories after ~250 dirs
to be marked as done.
This means that you claim that the problem ha
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #301147,
regarding missing 'Suggests' for libfam-dev
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #290529,
regarding Mounting USB key from gnome transfers famd process to root
to be marked as done.
This means that you claim that the
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #288223,
regarding fam: uses PATH_MAX which is not defined on HURD
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #280617,
regarding Automatically update the rc.d links
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #241143,
regarding Dies with Assertion
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #247335,
regarding Unhelpful "connection refused" (no address or hostname)
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #239540,
regarding fam: duplicating and missing events
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 11 Feb 2022 05:06:57 +
with message-id
and subject line Bug#966273: Removed package(s) from unstable
has caused the Debian Bug report #162959,
regarding fam: should use TCP wrappers
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> close 1004111
Bug #1004111 [unattended-upgrades] unattended-upgrades: upgrade of
chromium-browser and others skipped on Raspberry Pi OS
Marked Bug as done
--
1004111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004111
Debian Bug Tracking System
Contact ow..
Your message dated Fri, 11 Feb 2022 00:42:23 +0100
with message-id <4191221.HceWNZktDX@grumly>
and subject line
has caused the Debian Bug report #793739,
regarding frameworkintegration: Should not depend on fonts-oxygen
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 10 Feb 2022 23:00:08 +
with message-id
and subject line Bug#986067: fixed in r-cran-sampling 2.9-1
has caused the Debian Bug report #986067,
regarding ITP: r-cran-sampling -- Draw random samples using different sampling
schemes
to be marked as done.
This means that yo
Your message dated Thu, 10 Feb 2022 23:31:43 +0100
with message-id
and subject line Re: memtest86+: Should not run update-grub unconditionally in
postinst
has caused the Debian Bug report #481468,
regarding memtest86+: Should not run update-grub unconditionally in postinst
to be marked as done.
Your message dated Thu, 10 Feb 2022 22:52:32 +0100
with message-id
and subject line Re: Bug#898627: man-db: dependency loop
has caused the Debian Bug report #898627,
regarding man-db: dependency loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 10 Feb 2022 20:57:42 +0100
with message-id
and subject line Re: Bug#1004106: wireplumber: Unable to change default device
has caused the Debian Bug report #1004106,
regarding wireplumber: Unable to change default device
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 969438
Bug #969438 [double-conversion] double-conversion: Please make new autopkgtests
cross-test-friendly
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969438: https://bugs.debian.org/
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#992707: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #992707,
regarding exiv2: CVE-2021-34335
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#992706: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #992706,
regarding exiv2: CVE-2021-34334
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#992705: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #992705,
regarding exiv2: CVE-2021-32815
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#988731: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #988731,
regarding exiv2: CVE-2021-32617
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#988481: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #988481,
regarding exiv2: CVE-2021-29623
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#988242: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #988242,
regarding exiv2: CVE-2021-29464
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#988241: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #988241,
regarding exiv2: CVE-2021-29463
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#987736: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #987736,
regarding exiv2: CVE-2021-29473
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#987450: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #987450,
regarding exiv2: CVE-2021-29470
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#987277: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #987277,
regarding CVE-2021-29458
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#986888: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #986888,
regarding exiv2: CVE-2021-3482
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 Thu, 10 Feb 2022 19:36:24 +
with message-id
and subject line Bug#1000788: fixed in exiv2 0.27.5-1
has caused the Debian Bug report #1000788,
regarding exiv2: Update version to >=0.27.4 to enable CR3 support
to be marked as done.
This means that you claim that the problem ha
Your message dated Thu, 10 Feb 2022 19:04:15 +
with message-id
and subject line Bug#1004181: fixed in wolfssl 5.1.1-1
has caused the Debian Bug report #1004181,
regarding wolfssl: CVE-2022-23408
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Thu, 10 Feb 2022 17:36:05 +
with message-id
and subject line Bug#1005254: fixed in ssreflect 1.14.0-6
has caused the Debian Bug report #1005254,
regarding libcoq-mathcomp,libcoq-mathcomp-*: missing Breaks+Replaces:
libssreflect-coq (<< 1.14.0-4)
to be marked as done.
This
Your message dated Thu, 10 Feb 2022 16:00:08 +
with message-id
and subject line Bug#1001612: fixed in deltarpm 3.6.3+dfsg-1
has caused the Debian Bug report #1001612,
regarding ITP: deltarpm -- Tools to create and apply deltarpms
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 10 Feb 2022 15:36:35 +
with message-id
and subject line Bug#1005261: fixed in odil 0.12.1-5
has caused the Debian Bug report #1005261,
regarding odil ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 10 Feb 2022 15:19:23 +
with message-id
and subject line Bug#1001841: fixed in liblouis 3.20.0-2
has caused the Debian Bug report #1001841,
regarding liblouisutdml: FTBFS: tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Thu, 10 Feb 2022 15:19:23 +
with message-id
and subject line Bug#1001841: fixed in liblouis 3.20.0-2
has caused the Debian Bug report #1001841,
regarding liblouisutdml autopkgtest failing with the new liblouis
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 10 Feb 2022 15:59:02 +0100
with message-id
and subject line oops, wrong bug
has caused the Debian Bug report #996414,
regarding python-fastimport: autopkgtest regression: 2 failures + lots of
RuntimeError: maximum recursion depth exceeded
to be marked as done.
This means
Your message dated Thu, 10 Feb 2022 15:00:08 +
with message-id
and subject line Bug#1005266: fixed in libxcvt 0.1.1-2
has caused the Debian Bug report #1005266,
regarding xserver-xorg-core-udeb: uninstallable: depends on non-udeb libxcvt0
to be marked as done.
This means that you claim that t
Your message dated Thu, 10 Feb 2022 15:26:05 +0100
with message-id
and subject line Re: Bug#1004385: wireplumber: VLC freezes 20+ seconds before
starting
has caused the Debian Bug report #1004385,
regarding wireplumber: VLC freezes 20+ seconds before starting
to be marked as done.
This means th
Your message dated Thu, 10 Feb 2022 14:15:19 +0100
with message-id
and subject line Re: Bug#1005268: mpv: symbol lookup error: mpv: undefined
symbol: wl_proxy_marshal_flags
has caused the Debian Bug report #1005268,
regarding mpv: symbol lookup error: mpv: undefined symbol:
wl_proxy_marshal_flag
Your message dated Thu, 10 Feb 2022 13:04:31 +
with message-id
and subject line Bug#1004929: fixed in python-orderedmultidict 1.0-5
has caused the Debian Bug report #1004929,
regarding python-orderedmultidict: fix collections import under py3.10
to be marked as done.
This means that you claim
Your message dated Thu, 10 Feb 2022 12:49:14 +
with message-id
and subject line Bug#209185: fixed in man-db 2.10.1-1
has caused the Debian Bug report #209185,
regarding man-db in cron.daily fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 10 Feb 2022 13:39:32 +0100
with message-id <20220210123932.ga13...@inutil.org>
and subject line Python 2 packages no longer built
has caused the Debian Bug report #937290,
regarding pillow: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Thu, 10 Feb 2022 12:20:54 +
with message-id
and subject line Bug#1005255: fixed in telegram-desktop 3.5.2+ds-1
has caused the Debian Bug report #1005255,
regarding telegram-desktop: error: ‘Config’ is not a member of ‘webrtc’
to be marked as done.
This means that you claim
Your message dated Thu, 10 Feb 2022 12:20:54 +
with message-id
and subject line Bug#1004767: fixed in telegram-desktop 3.5.2+ds-1
has caused the Debian Bug report #1004767,
regarding telegram-desktop: FTBFS with ffmpeg 5.0
to be marked as done.
This means that you claim that the problem has b
Your message dated Thu, 10 Feb 2022 11:33:42 +
with message-id
and subject line Bug#953090: fixed in kamailio 5.5.3-2
has caused the Debian Bug report #953090,
regarding FTBFS on ia64: /usr/bin/ld:
/usr/lib/gcc/ia64-linux-gnu/9/../../../ia64-linux-gnu/Scrt1.o: in function
`_start': (.text+0x
Your message dated Thu, 10 Feb 2022 10:29:22 +
with message-id
and subject line Re: Bug#1005194: qosmic, build-depends on obsolete package.
has caused the Debian Bug report #1005194,
regarding qosmic, build-depends on obsolete package.
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> close 1003317
Bug #1003317 [wnpp] ITP: primecount -- fast prime number counter C/C++ library
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003317: https://bugs.debian.org/cgi-bin/bugreport.cg
Processing control commands:
> close -1 0.801-1
Bug #1005274 [src:libio-async-perl] src:libio-async-perl: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions libio-async-perl/0.801-1.
Bug #1005274 [src:libio-async-perl] src:libio-async-perl: fails to migra
Your message dated Thu, 10 Feb 2022 10:04:24 +
with message-id
and subject line Bug#1005263: fixed in dnswire 0.2.0-2
has caused the Debian Bug report #1005263,
regarding dnswire FTBFS: rm: cannot remove 'src/dnstap.pb': Is a directory
to be marked as done.
This means that you claim that the
Your message dated Thu, 10 Feb 2022 10:41:18 +0100
with message-id <349949b0-6a82-629c-d09a-fccd132d0...@debian.org>
and subject line Re: Bug#967945: systemd is way too aggressive in deleting
journals of yesterday
has caused the Debian Bug report #967945,
regarding systemd is way too aggressive in
Your message dated Thu, 10 Feb 2022 10:14:06 +0100
with message-id
and subject line Re: Bug#1004947: Loses keystrokes until dialog displayed
has caused the Debian Bug report #1004947,
regarding Loses keystrokes until dialog displayed
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 10 Feb 2022 10:16:26 +0100
with message-id
and subject line Re: Bug#1004946: Cannot hold down backspace to delete password
has caused the Debian Bug report #1004946,
regarding Cannot hold down backspace to delete password
to be marked as done.
This means that you claim tha
Your message dated Thu, 10 Feb 2022 09:19:12 +
with message-id
and subject line Bug#1005248: fixed in dehydrated-hook-ddns-tsig 0.1.4-7
has caused the Debian Bug report #1005248,
regarding dehydrated-hook-ddns-tsig: Resolve DeprecationWarning for
dns.resolver.query()
to be marked as done.
Th
Your message dated Thu, 10 Feb 2022 09:03:57 +
with message-id
and subject line Bug#1004071: fixed in google-guest-agent 2026.00-3
has caused the Debian Bug report #1004071,
regarding google-guest-agent,python3-google-compute-engine: both ship
/usr/bin/google_metadata_script_runner
to be
Your message dated Thu, 10 Feb 2022 10:01:23 +0100
with message-id
and subject line Re: Bug#997919: pipewire: Automatich profile selection for
bluetooth headsets fails since 0.3.39
has caused the Debian Bug report #997919,
regarding pipewire: Automatich profile selection for bluetooth headsets f
Your message dated Thu, 10 Feb 2022 09:19:22 +0100
with message-id <20220210091922.188f2...@vip.jcf.pm>
and subject line Re: Bug#1005262: RFS: color-picker/1.0.3-1 -- Powerful screen
color picker based on Qt
has caused the Debian Bug report #1005262,
regarding RFS: color-picker/1.0.3-1 -- Powerful
Your message dated Thu, 10 Feb 2022 08:38:53 +
with message-id
and subject line Bug#1002172: fixed in py3exiv2 0.7.2-1.1
has caused the Debian Bug report #1002172,
regarding py3exiv2: FTBFS: wrap_python.hpp:57:11: fatal error: pyconfig.h: No
such file or directory
to be marked as done.
This
Your message dated Thu, 10 Feb 2022 08:39:00 +
with message-id
and subject line Bug#1001545: fixed in pyopencl 2021.2.13-1
has caused the Debian Bug report #1001545,
regarding pyopencl, build-depends on package that is no longer in testing
to be marked as done.
This means that you claim that
99 matches
Mail list logo
