Your message dated Fri, 30 Dec 2022 08:32:52 +0100
with message-id <4e14729a1cca590f9f4fb63bdf4442d7d6dce1c5.ca...@z-51.de>
and subject line Re: new upstream version 0.0.8
has caused the Debian Bug report #1026317,
regarding new upstream version 0.0.8
to be marked as done.
This means that you clai
Your message dated Fri, 30 Dec 2022 07:35:09 +
with message-id
and subject line Bug#965600: fixed in jack-tools 20131226-1.1
has caused the Debian Bug report #965600,
regarding jack-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> close 1027291
Bug #1027291 [sponsorship-requests] RFS: dh-sysuser/1.3.8+really1.4.2 --
debhelper addon to handle creation of system users
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1027291:
Your message dated Fri, 30 Dec 2022 06:34:13 +
with message-id
and subject line Bug#1018334: fixed in cwlformat 2022.02.18-2
has caused the Debian Bug report #1018334,
regarding cwlformat: build-depends on python3-nose or uses it for autopkgtest
to be marked as done.
This means that you claim
Your message dated Fri, 30 Dec 2022 06:19:03 +
with message-id
and subject line Bug#1015687: fixed in terraphast 0.0+git20200413.8af2e4c+dfsg-2
has caused the Debian Bug report #1015687,
regarding terraphast: ftbfs with LTO (link time optimization) enabled
to be marked as done.
This means tha
Your message dated Thu, 29 Dec 2022 23:49:15 +
with message-id
and subject line Bug#1026986: fixed in console-setup 1.215
has caused the Debian Bug report #1026986,
regarding console-setup: "Dead" keys do not work for Greek keyboard layout in
tty
to be marked as done.
This means that you cla
Your message dated Fri, 30 Dec 2022 00:26:12 +0100
with message-id
and subject line Re: Bug#1027057: transition: coq-bignums 8.17.0-1
has caused the Debian Bug report #1027057,
regarding transition: coq-bignums 8.17.0-1
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 29 Dec 2022 22:19:51 +
with message-id
and subject line Bug#1003674: fixed in php-sabre-vobject 2.1.7-6.1
has caused the Debian Bug report #1003674,
regarding php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError:
Epoch doesn't fit in a PHP integer
to be
Your message dated Thu, 29 Dec 2022 21:56:53 +
with message-id
and subject line Fixed in 1.1.2-2
has caused the Debian Bug report #1017650,
regarding rust-zram-generator: BD-Uninstallable
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, 29 Dec 2022 13:46:54 -0800
with message-id <874jtdnar5.fsf@yucca>
and subject line Re: Bug#997689: smplayer: please make the build reproducible
has caused the Debian Bug report #997689,
regarding smplayer: please make the build reproducible
to be marked as done.
This means
Your message dated Thu, 29 Dec 2022 21:49:24 +
with message-id
and subject line Bug#1027020: fixed in davmail 6.0.1.3390-4
has caused the Debian Bug report #1027020,
regarding davmail-server: fails to install: insserv: script davmail-server:
service davmail already provided!
to be marked as d
Your message dated Thu, 29 Dec 2022 21:35:17 +
with message-id
and subject line Bug#992060: fixed in pytsk 20200117-3.1
has caused the Debian Bug report #992060,
regarding pytsk: please make the build reproducible
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 29 Dec 2022 21:08:09 +
with message-id <20221229210809.ga3295...@tack.einval.com>
and subject line Closing old bug
has caused the Debian Bug report #385814,
regarding Include patch for GNU GRUB bug #14407, partition table offset not
reset when changing to CD
to be marke
Your message dated Thu, 29 Dec 2022 21:07:36 +
with message-id
and subject line Bug#1027251: fixed in python-cooler 0.8.11-5
has caused the Debian Bug report #1027251,
regarding python-cooler: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 29 Dec 2022 21:05:42 +
with message-id
and subject line Bug#1025656: fixed in edk2 2022.11-2
has caused the Debian Bug report #1025656,
regarding synchronous exception when using qemu-efi-aarch64 2022.11
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> close 1027279
Bug #1027279 [sponsorship-requests] RFS: python-fire/0.5.0-1 [QA] [RC] --
automatically generate CLIs from absolutely any Python object
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
-
Your message dated Thu, 29 Dec 2022 20:38:37 +
with message-id
and subject line Bug#1026619: fixed in python-fire 0.5.0-1
has caused the Debian Bug report #1026619,
regarding python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute
'coroutine'
to be marked as done.
This means th
Your message dated Thu, 29 Dec 2022 20:37:39 +
with message-id
and subject line Bug#1025120: fixed in libetpan 1.9.4-3.1
has caused the Debian Bug report #1025120,
regarding libetpan: CVE-2022-4121: Null Pointer Dereference STATUS Response
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 12:28:25 -0800
with message-id <87fscylzti.fsf@yucca>
and subject line Re: Bug#994979: python-tomli: please make the build
reproducible
has caused the Debian Bug report #994979,
regarding python-tomli: please make the build reproducible
to be marked as done.
Th
Your message dated Thu, 29 Dec 2022 19:49:13 +
with message-id
and subject line Bug#1027241: fixed in compyle 0.8.1-4
has caused the Debian Bug report #1027241,
regarding pysph: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 29 Dec 2022 19:49:47 +
with message-id
and subject line Bug#1027211: fixed in python-pbcore 2.1.2+dfsg-4
has caused the Debian Bug report #1027211,
regarding python-pbcore: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the prob
Your message dated Thu, 29 Dec 2022 19:23:03 +
with message-id
and subject line Bug#1027137: fixed in kicad 6.0.10+dfsg-2
has caused the Debian Bug report #1027137,
regarding kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets
is compiled with the EGL canvas"
to be marked as d
Your message dated Thu, 29 Dec 2022 19:19:28 +
with message-id
and subject line Bug#991181: fixed in cmocka 1.1.5-2.1
has caused the Debian Bug report #991181,
regarding cmocka: reproducible builds: Embeds build path in documentation
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 30 Dec 2022 08:09:08 +1300
with message-id
and subject line Re: Bug#1019818: wxmaxima: Please transition to wxwidgets3.2
has caused the Debian Bug report #1019818,
regarding wxmaxima: Please transition to wxwidgets3.2
to be marked as done.
This means that you claim that th
Your message dated Thu, 29 Dec 2022 19:05:47 +
with message-id
and subject line Bug#999178: fixed in libuninum 2.7-1.2
has caused the Debian Bug report #999178,
regarding libuninum: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you
Your message dated Thu, 29 Dec 2022 19:06:51 +
with message-id
and subject line Bug#999110: fixed in tcd-utils 20061127-2.1
has caused the Debian Bug report #999110,
regarding tcd-utils: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that
Your message dated Thu, 29 Dec 2022 19:07:39 +
with message-id
and subject line Bug#965861: fixed in vcheck 1.2.1-7.2
has caused the Debian Bug report #965861,
regarding vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the p
Your message dated Thu, 29 Dec 2022 19:06:51 +
with message-id
and subject line Bug#965835: fixed in tcd-utils 20061127-2.1
has caused the Debian Bug report #965835,
regarding tcd-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim t
Your message dated Thu, 29 Dec 2022 20:07:32 +0100
with message-id <5b902d0c-45f2-bc5b-edc2-a3998e793...@debian.org>
and subject line Re: ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed:
Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/,
'==').strip.should == "Progress: |==
Your message dated Thu, 29 Dec 2022 19:05:47 +
with message-id
and subject line Bug#965695: fixed in libuninum 2.7-1.2
has caused the Debian Bug report #965695,
regarding libuninum: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that t
Your message dated Thu, 29 Dec 2022 19:04:47 +
with message-id
and subject line Bug#965523: fixed in flobopuyo 0.20-5.1
has caused the Debian Bug report #965523,
regarding flobopuyo: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 18:42:30 +
with message-id
and subject line Bug#999305: fixed in iat 0.1.3-7.1
has caused the Debian Bug report #999305,
regarding iat: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 18:42:14 +
with message-id
and subject line Bug#966862: fixed in gramophone2 0.8.13a-3.2
has caused the Debian Bug report #966862,
regarding gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple
definition of `midi'; /tmp/ccHnI4GU.o:./global.h:70:
Your message dated Thu, 29 Dec 2022 18:41:24 +
with message-id
and subject line Bug#999156: fixed in dbench 4.0-2.1
has caused the Debian Bug report #999156,
regarding dbench: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim
Your message dated Thu, 29 Dec 2022 18:41:42 +
with message-id
and subject line Bug#998958: fixed in filler 1.02-6.4
has caused the Debian Bug report #998958,
regarding filler: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim
Your message dated Thu, 29 Dec 2022 18:43:52 +
with message-id
and subject line Bug#999046: fixed in netsend 0.0~svnr250-1.5
has caused the Debian Bug report #999046,
regarding netsend: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that
Your message dated Thu, 29 Dec 2022 18:41:33 +
with message-id
and subject line Bug#998956: fixed in efax-gtk 3.2.8-2.3
has caused the Debian Bug report #998956,
regarding efax-gtk: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you
Your message dated Thu, 29 Dec 2022 18:43:52 +
with message-id
and subject line Bug#965747: fixed in netsend 0.0~svnr250-1.5
has caused the Debian Bug report #965747,
regarding netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim th
Your message dated Thu, 29 Dec 2022 18:42:30 +
with message-id
and subject line Bug#965589: fixed in iat 0.1.3-7.1
has caused the Debian Bug report #965589,
regarding iat: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 29 Dec 2022 18:42:22 +
with message-id
and subject line Bug#965578: fixed in hasciicam 1.1.2-1.1
has caused the Debian Bug report #965578,
regarding hasciicam: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 18:41:42 +
with message-id
and subject line Bug#965521: fixed in filler 1.02-6.4
has caused the Debian Bug report #965521,
regarding filler: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 29 Dec 2022 18:42:14 +
with message-id
and subject line Bug#965567: fixed in gramophone2 0.8.13a-3.2
has caused the Debian Bug report #965567,
regarding gramophone2: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you clai
Your message dated Thu, 29 Dec 2022 18:41:33 +
with message-id
and subject line Bug#965505: fixed in efax-gtk 3.2.8-2.3
has caused the Debian Bug report #965505,
regarding efax-gtk: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that t
Your message dated Thu, 29 Dec 2022 18:41:24 +
with message-id
and subject line Bug#965484: fixed in dbench 4.0-2.1
has caused the Debian Bug report #965484,
regarding dbench: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the pro
Your message dated Thu, 29 Dec 2022 18:41:42 +
with message-id
and subject line Bug#780484: fixed in filler 1.02-6.4
has caused the Debian Bug report #780484,
regarding filler: Man page is not distributed
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 29 Dec 2022 18:41:33 +
with message-id
and subject line Bug#955830: fixed in efax-gtk 3.2.8-2.3
has caused the Debian Bug report #955830,
regarding efax-gtk: unnecessarily Build-Depends on deprecated dbus-glib
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 29 Dec 2022 18:44:28 +
with message-id
and subject line Bug#1027223: fixed in pyrr 0.10.3-5
has caused the Debian Bug report #1027223,
regarding pyrr: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Thu, 29 Dec 2022 18:42:14 +
with message-id
and subject line Bug#760662: fixed in gramophone2 0.8.13a-3.2
has caused the Debian Bug report #760662,
regarding gramophone2: FTBFS with clang instead of gcc
to be marked as done.
This means that you claim that the problem has be
Your message dated Thu, 29 Dec 2022 18:42:14 +
with message-id
and subject line Bug#738279: fixed in gramophone2 0.8.13a-3.2
has caused the Debian Bug report #738279,
regarding gramophone2: Please support building with --as-needed
to be marked as done.
This means that you claim that the probl
Your message dated Thu, 29 Dec 2022 18:43:52 +
with message-id
and subject line Bug#1011647: fixed in netsend 0.0~svnr250-1.5
has caused the Debian Bug report #1011647,
regarding RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon
to be marked as done.
This means that you c
Your message dated Thu, 29 Dec 2022 18:42:03 +
with message-id
and subject line Bug#1027214: fixed in gasic 0.0.r19-8
has caused the Debian Bug report #1027214,
regarding gasic: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 29 Dec 2022 17:55:01 +
with message-id
and subject line Bug#1026040: fixed in ipe-tools 1:7.2.24.1-3
has caused the Debian Bug report #1026040,
regarding pdftoipe: Fix build with Poppler >= 22.09
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Dec 2022 17:56:14 +
with message-id
and subject line Bug#1027239: fixed in pygac 1.7.1-2
has caused the Debian Bug report #1027239,
regarding pygac: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Thu, 29 Dec 2022 18:18:27 +0100
with message-id
and subject line Re: Bug#1026055: lapack breaks openturns autopkgtest:
undefined reference to `ztrsyl3_' (and 3 more)
has caused the Debian Bug report #1026055,
regarding lapack breaks openturns autopkgtest: undefined reference to
Your message dated Thu, 29 Dec 2022 17:25:14 +
with message-id
and subject line Bug#1027086: fixed in ruby-rest-client 2.1.0-3
has caused the Debian Bug report #1027086,
regarding ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error:
to be marked as d
Your message dated Thu, 29 Dec 2022 17:22:56 +
with message-id
and subject line Bug#1027231: fixed in numcodecs 0.11.0+ds-3
has caused the Debian Bug report #1027231,
regarding numcodecs: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has b
Your message dated Thu, 29 Dec 2022 17:13:28 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #989060,
regarding CVE-2021-28902 CVE-2021-28903 CVE-2021-28904 CVE-2021-28905
CVE-2021-28906
to be marked as done.
This means that y
Your message dated Thu, 29 Dec 2022 17:13:23 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #1027275,
regarding RM: libyang -- RoQA; RC-buggy, replaced by libyang2
to be marked as done.
This means that you claim that the probl
Your message dated Thu, 29 Dec 2022 17:13:28 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #1003767,
regarding libyang: autopkgtest failure (and tests the src:libyang2 packages)
to be marked as done.
This means that you claim
Your message dated Thu, 29 Dec 2022 17:13:28 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #1003766,
regarding libyang must stop building libyang-tools
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Dec 2022 17:13:28 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #1001585,
regarding libyang: dep8 failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Thu, 29 Dec 2022 17:13:28 +
with message-id
and subject line Bug#1027275: Removed package(s) from unstable
has caused the Debian Bug report #162,
regarding libyang: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem has be
Your message dated Thu, 29 Dec 2022 17:08:59 +
with message-id
and subject line Bug#1027274: Removed package(s) from unstable
has caused the Debian Bug report #999208,
regarding phamm: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that y
Your message dated Thu, 29 Dec 2022 17:08:28 +
with message-id
and subject line Bug#1027269: Removed package(s) from unstable
has caused the Debian Bug report #993554,
regarding O: cakephp -- rapid application development framework for PHP
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 17:08:59 +
with message-id
and subject line Bug#1027274: Removed package(s) from unstable
has caused the Debian Bug report #977580,
regarding phamm: Fix Apache configuration to use mod_php7.c, not mod_php5.c
to be marked as done.
This means that you claim t
Your message dated Thu, 29 Dec 2022 17:08:28 +
with message-id
and subject line Bug#1027269: Removed package(s) from unstable
has caused the Debian Bug report #985673,
regarding CVE-2020-15400
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, 29 Dec 2022 17:08:59 +
with message-id
and subject line Bug#1027274: Removed package(s) from unstable
has caused the Debian Bug report #924731,
regarding phamm: CVE-2018-20806: Reflected XSS in Phamm login page
to be marked as done.
This means that you claim that the p
Your message dated Thu, 29 Dec 2022 17:08:59 +
with message-id
and subject line Bug#1027274: Removed package(s) from unstable
has caused the Debian Bug report #965772,
regarding phamm: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim tha
Your message dated Thu, 29 Dec 2022 17:08:54 +
with message-id
and subject line Bug#1027274: Removed package(s) from unstable
has caused the Debian Bug report #1027274,
regarding RM: phamm -- RoQA; unsupported upstream (appects only pull requests),
has security issues
to be marked as done.
T
Your message dated Thu, 29 Dec 2022 17:08:28 +
with message-id
and subject line Bug#1027269: Removed package(s) from unstable
has caused the Debian Bug report #782431,
regarding cakephp 3.0 is released
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Thu, 29 Dec 2022 17:08:28 +
with message-id
and subject line Bug#1027269: Removed package(s) from unstable
has caused the Debian Bug report #1026993,
regarding cakephp -- seriously outdated branch
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 29 Dec 2022 17:06:51 +
with message-id
and subject line Bug#1027178: Removed package(s) from unstable
has caused the Debian Bug report #974586,
regarding loganalyzer: depends on php5 to use mysql db as a backend.
to be marked as done.
This means that you claim that the
Your message dated Thu, 29 Dec 2022 17:06:51 +
with message-id
and subject line Bug#1027178: Removed package(s) from unstable
has caused the Debian Bug report #956621,
regarding loganalyzer: New upstream version 4.1.11 available.
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 29 Dec 2022 17:06:22 +
with message-id
and subject line Bug#1027157: Removed package(s) from unstable
has caused the Debian Bug report #911033,
regarding O: libopkele -- OpenID support library in C++
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Dec 2022 17:05:57 +
with message-id
and subject line Bug#1027156: Removed package(s) from unstable
has caused the Debian Bug report #911032,
regarding O: libapache2-mod-auth-openid -- OpenID authentication module for
Apache2
to be marked as done.
This means that yo
Your message dated Thu, 29 Dec 2022 17:07:59 +
with message-id
and subject line Bug#1027184: Removed package(s) from unstable
has caused the Debian Bug report #846823,
regarding Updating the primesense-nite-nonfree Uploaders list
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 29 Dec 2022 17:07:59 +
with message-id
and subject line Bug#1027184: Removed package(s) from unstable
has caused the Debian Bug report #771189,
regarding primesense-nite-nonfree: Nite needs license key file
to be marked as done.
This means that you claim that the probl
Your message dated Thu, 29 Dec 2022 17:07:59 +
with message-id
and subject line Bug#1027184: Removed package(s) from unstable
has caused the Debian Bug report #771187,
regarding primesense-nite-nonfree: Package broken because openni.org is gone
to be marked as done.
This means that you claim
Your message dated Thu, 29 Dec 2022 17:05:57 +
with message-id
and subject line Bug#1027156: Removed package(s) from unstable
has caused the Debian Bug report #759209,
regarding libapache2-mod-auth-openid: Can't locate API module structure
`auth_openid_module'
to be marked as done.
This mean
Your message dated Thu, 29 Dec 2022 17:07:31 +
with message-id
and subject line Bug#1027181: Removed package(s) from unstable
has caused the Debian Bug report #626369,
regarding selfhtml: Selfhtml starter
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 29 Dec 2022 17:05:57 +
with message-id
and subject line Bug#1027156: Removed package(s) from unstable
has caused the Debian Bug report #556641,
regarding DB directory needs to be writeable for www-data
to be marked as done.
This means that you claim that the problem ha
Your message dated Thu, 29 Dec 2022 17:07:31 +
with message-id
and subject line Bug#1027181: Removed package(s) from unstable
has caused the Debian Bug report #552544,
regarding selfhtml: debian/watch file
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Thu, 29 Dec 2022 17:08:24 +
with message-id
and subject line Bug#1027269: Removed package(s) from unstable
has caused the Debian Bug report #1027269,
regarding RM: cakephp -- RoQA; 2.x branch unmaintained upstream, QA maintained,
has security issues
to be marked as done.
T
Your message dated Thu, 29 Dec 2022 17:07:54 +
with message-id
and subject line Bug#1027184: Removed package(s) from unstable
has caused the Debian Bug report #1027184,
regarding RM: primesense-nite-nonfree -- RoQA; broken for a long time
to be marked as done.
This means that you claim that t
Your message dated Thu, 29 Dec 2022 17:06:47 +
with message-id
and subject line Bug#1027178: Removed package(s) from unstable
has caused the Debian Bug report #1027178,
regarding RM: loganalyzer -- RoQA; unmaintained, broken
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Dec 2022 17:07:26 +
with message-id
and subject line Bug#1027181: Removed package(s) from unstable
has caused the Debian Bug report #1027181,
regarding RM: selfhtml -- RoQA; obsolete, RC-buggy, unmaintained
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 29 Dec 2022 17:06:19 +
with message-id
and subject line Bug#1027157: Removed package(s) from unstable
has caused the Debian Bug report #1027157,
regarding RM: libopkele -- RoQA; dead upstream; orphaned; leaf library
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 17:05:24 +
with message-id
and subject line Bug#1027141: Removed package(s) from unstable
has caused the Debian Bug report #1027141,
regarding RM: rust-svgdom -- ROM; Deprecated upstream and doesn't build against
newer roxmltree/xmlparser
to be marked as do
Your message dated Thu, 29 Dec 2022 17:05:52 +
with message-id
and subject line Bug#1027156: Removed package(s) from unstable
has caused the Debian Bug report #1027156,
regarding RM: libapache2-mod-auth-openid -- RoQA; dead upstream; orphaned;
alternatives exist
to be marked as done.
This me
Your message dated Thu, 29 Dec 2022 17:04:55 +
with message-id
and subject line Bug#1027109: Removed package(s) from unstable
has caused the Debian Bug report #1027109,
regarding RM: python-pykafka -- ROM; No reverse (b-)depends, RC buggy
to be marked as done.
This means that you claim that t
Your message dated Thu, 29 Dec 2022 17:05:28 +
with message-id
and subject line Bug#1027141: Removed package(s) from unstable
has caused the Debian Bug report #1026853,
regarding rust-svgdom: (build-)depends on old version of rust-roxmltree
to be marked as done.
This means that you claim that
Your message dated Thu, 29 Dec 2022 17:04:59 +
with message-id
and subject line Bug#1027109: Removed package(s) from unstable
has caused the Debian Bug report #1024352,
regarding pykafka: please make the build reproducible
to be marked as done.
This means that you claim that the problem has b
Your message dated Thu, 29 Dec 2022 17:04:59 +
with message-id
and subject line Bug#1027109: Removed package(s) from unstable
has caused the Debian Bug report #1023921,
regarding pykafka: diff for NMU version 2.7.0-2.1
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Dec 2022 17:04:59 +
with message-id
and subject line Bug#1027109: Removed package(s) from unstable
has caused the Debian Bug report #1023916,
regarding pykafka: Unmaintained upstream?
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Thu, 29 Dec 2022 17:05:28 +
with message-id
and subject line Bug#1027141: Removed package(s) from unstable
has caused the Debian Bug report #1006988,
regarding rust-svgdom: still needed in the archive?
to be marked as done.
This means that you claim that the problem has bee
Your message dated Thu, 29 Dec 2022 17:07:31 +
with message-id
and subject line Bug#1027181: Removed package(s) from unstable
has caused the Debian Bug report #1002966,
regarding selfhtml: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Thu, 29 Dec 2022 17:07:59 +
with message-id
and subject line Bug#1027184: Removed package(s) from unstable
has caused the Debian Bug report #1002887,
regarding primesense-nite-nonfree: Removal of obsolete debhelper compat 5 and 6
in bookworm
to be marked as done.
This mean
Your message dated Thu, 29 Dec 2022 17:06:22 +
with message-id
and subject line Bug#1027157: Removed package(s) from unstable
has caused the Debian Bug report #194,
regarding libopkele: depends on obsolete pcre3 library
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Dec 2022 16:54:49 +
with message-id
and subject line Bug#916998: fixed in ulogd2 2.0.8-1
has caused the Debian Bug report #916998,
regarding ulogd2 FTCBFS: mysql/libpq detection broken
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Thu, 29 Dec 2022 16:54:49 +
with message-id
and subject line Bug#805940: fixed in ulogd2 2.0.8-1
has caused the Debian Bug report #805940,
regarding file /var/log/ulog doesn't belong to user ulog
to be marked as done.
This means that you claim that the problem has been deal
1 - 100 of 144 matches
Mail list logo
