Your message dated Fri, 2 Dec 2022 12:39:01 +0100
with message-id
and subject line Re: Bug#904113: CVE-2018-11489
has caused the Debian Bug report #904113,
regarding CVE-2018-11489
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Sat, 03 Dec 2022 07:35:03 +
with message-id
and subject line Bug#1025354: fixed in emacs-cmake-mode 3.25.1+ds-2
has caused the Debian Bug report #1025354,
regarding emacs-cmake-mode: non-breaking-space chars in name part of Maintainer
field
to be marked as done.
This means
Processing control commands:
> close -1
Bug #1004275 [php] php upgrade apache2: After upgrade php install apache2 and i
have intalled lighttpd
Marked Bug as done
--
1004275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Your message dated Sat, 03 Dec 2022 06:50:03 +
with message-id
and subject line Bug#1015882: fixed in dicomscope 3.6.0-25
has caused the Debian Bug report #1015882,
regarding dicomscope: Missing java-wrappers dependency
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> close -1 2022.11.0-2
Bug #1025358 [src:python-xarray] src:python-xarray: fails to migrate to testing
for too long: autopkgtest regression
Marked as fixed in versions python-xarray/2022.11.0-2.
Bug #1025358 [src:python-xarray] src:python-xarray: fails to migrate to t
Processing control commands:
> close -1 2.1-6
Bug #1025357 [src:jbigkit] src:jbigkit: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions jbigkit/2.1-6.
Bug #1025357 [src:jbigkit] src:jbigkit: fails to migrate to testing for too
long: autopkgtest regressi
Your message dated Sat, 3 Dec 2022 07:27:31 +0100
with message-id
and subject line Re: Bug#1021806: python3-click: Will you please upgrade to the
latest version?
has caused the Debian Bug report #1021806,
regarding python3-click: Will you please upgrade to the latest version?
to be marked as done
Your message dated Sat, 03 Dec 2022 04:50:07 +
with message-id
and subject line Bug#1025200: fixed in ruby-mime-types 3.4.1-2
has caused the Debian Bug report #1025200,
regarding ruby-mime-types-data breaks ruby-mime-types autopkgtest: not found
to be marked as done.
This means that you claim
Your message dated Sat, 03 Dec 2022 03:49:02 +
with message-id
and subject line Bug#1019630: fixed in ruby-hoe 3.22.1+dfsg1-3
has caused the Debian Bug report #1019630,
regarding ruby-hoe: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that t
Your message dated Sat, 03 Dec 2022 01:05:33 +
with message-id
and subject line Bug#1025009: fixed in emacs 1:28.2+1-8
has caused the Debian Bug report #1025009,
regarding emacs: CVE-2022-45939: ctags local command execute vulnerability
to be marked as done.
This means that you claim that the
Your message dated Sat, 03 Dec 2022 00:49:49 +
with message-id
and subject line Bug#1007679: fixed in pidgin-awayonlock 0.5.2-1.1
has caused the Debian Bug report #1007679,
regarding pidgin-awayonlock: please consider upgrading to 3.0 source format
to be marked as done.
This means that you cl
Your message dated Sat, 03 Dec 2022 00:49:42 +
with message-id
and subject line Bug#1007673: fixed in pgreplay 1.2.0-2.1
has caused the Debian Bug report #1007673,
regarding pgreplay: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the probl
Your message dated Sat, 03 Dec 2022 00:27:26 +
with message-id
and subject line Bug#1025316: fixed in rosegarden 1:22.06-2
has caused the Debian Bug report #1025316,
regarding rosegarden: FTBFS with fftw3 (3.3.10-1)
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sat, 03 Dec 2022 00:26:53 +
with message-id
and subject line Bug#1007374: fixed in nmzmail 1.1-4
has caused the Debian Bug report #1007374,
regarding nmzmail: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 03 Dec 2022 00:26:47 +
with message-id
and subject line Bug#1007038: fixed in ng-utils 1.0-1.1
has caused the Debian Bug report #1007038,
regarding ng-utils: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 03 Dec 2022 00:25:19 +
with message-id
and subject line Bug#982406: fixed in markdown 1.0.1-12
has caused the Debian Bug report #982406,
regarding mark markdown Multi-Arch: foreign
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 03 Dec 2022 00:24:07 +
with message-id
and subject line Bug#1007648: fixed in libimage-base-bundle-perl 1.0.7-3.5
has caused the Debian Bug report #1007648,
regarding libimage-base-bundle-perl: please consider upgrading to 3.0 source
format
to be marked as done.
This
Your message dated Sat, 03 Dec 2022 00:24:48 +
with message-id
and subject line Bug#1007565: fixed in libtree-multinode-perl 1.0.14-0.1
has caused the Debian Bug report #1007565,
regarding libtree-multinode-perl: please consider upgrading to 3.0 source format
to be marked as done.
This means
Your message dated Sat, 03 Dec 2022 00:24:40 +
with message-id
and subject line Bug#1007536: fixed in libromana-perligata-perl 0.55-1.4
has caused the Debian Bug report #1007536,
regarding libromana-perligata-perl: please consider upgrading to 3.0 source
format
to be marked as done.
This mea
Your message dated Sat, 03 Dec 2022 00:24:33 +
with message-id
and subject line Bug#1007486: fixed in libnbcompat 20180822-5.1
has caused the Debian Bug report #1007486,
regarding libnbcompat: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that
Your message dated Sat, 03 Dec 2022 00:24:55 +
with message-id
and subject line Bug#1007473: fixed in libuser-perl 1.9-1.2
has caused the Debian Bug report #1007473,
regarding libuser-perl: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the
Your message dated Sat, 03 Dec 2022 00:25:03 +
with message-id
and subject line Bug#1007295: fixed in lsmbox 2.1.3-1.1
has caused the Debian Bug report #1007295,
regarding lsmbox: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the problem h
Your message dated Sat, 03 Dec 2022 00:25:19 +
with message-id
and subject line Bug#1007067: fixed in markdown 1.0.1-12
has caused the Debian Bug report #1007067,
regarding markdown: please consider upgrading to 3.0 source format
to be marked as done.
This means that you claim that the proble
Your message dated Sat, 03 Dec 2022 00:19:30 +
with message-id
and subject line Bug#1025273: fixed in dpkg 1.21.11
has caused the Debian Bug report #1025273,
regarding dpkg-genbuildinfo: fails when no cross compiler is available
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 02 Dec 2022 23:52:14 +
with message-id
and subject line Bug#1007380: fixed in libhtml-element-extended-perl 1.18-1.3
has caused the Debian Bug report #1007380,
regarding libhtml-element-extended-perl: please consider upgrading to 3.0
source format
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> close 994260
Bug #994260 [sponsorship-requests] RFS: blop-lv2/1.0.4-1 [ITP] -- Bandlimited
LADSPA Oscillator Plugins ported to LV2
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
994260: https://
Your message dated Fri, 02 Dec 2022 22:08:01 +
with message-id
and subject line Bug#1024956: fixed in manuel 1.12.4-2
has caused the Debian Bug report #1024956,
regarding manuel: (autopkgtest) needs update for python3.11AssertionError:
output looks slightly different
to be marked as done.
Th
Your message dated Fri, 2 Dec 2022 22:46:35 +0100
with message-id <20221202224635.17fcf...@frustcomp.hnjs.home.arpa>
and subject line Closed due to incorrect use of the option
has caused the Debian Bug report #951067,
regarding apache2: unable to disable TLSv1
to be marked as done.
This means that
Your message dated Fri, 02 Dec 2022 22:04:58 +
with message-id
and subject line Bug#1007517: fixed in libdatapager-perl 0.01-2.3
has caused the Debian Bug report #1007517,
regarding libdatapager-perl: please consider upgrading to 3.0 source format
to be marked as done.
This means that you cla
Your message dated Fri, 02 Dec 2022 21:52:39 +
with message-id
and subject line Bug#1025148: fixed in rpcsvc-proto 1.4.3-1
has caused the Debian Bug report #1025148,
regarding rpcsvc-proto FTCBFS: runs the built rpcgen
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Dec 2022 21:51:10 +
with message-id
and subject line Bug#1025271: fixed in gtk+3.0 3.24.35-2
has caused the Debian Bug report #1025271,
regarding libgtk-3-0: Testing printer is available per default -> intentional?
to be marked as done.
This means that you claim tha
Your message dated Fri, 02 Dec 2022 21:51:54 +
with message-id
and subject line Bug#1018407: fixed in mirtop 0.4.25-2
has caused the Debian Bug report #1018407,
regarding mirtop: build-depends on python3-nose or uses it for autopkgtest
to be marked as done.
This means that you claim that the
Your message dated Fri, 02 Dec 2022 21:51:20 +
with message-id
and subject line Bug#1007386: fixed in libanyevent-serialize-perl 0.04-1.2
has caused the Debian Bug report #1007386,
regarding libanyevent-serialize-perl: please consider upgrading to 3.0 source
format
to be marked as done.
This
Your message dated Fri, 02 Dec 2022 21:36:31 +
with message-id
and subject line Bug#984244: fixed in mpqc 2.3.1-22
has caused the Debian Bug report #984244,
regarding mpqc: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Your message dated Fri, 02 Dec 2022 21:10:17 +
with message-id
and subject line Bug#1023767: fixed in neomutt 20220429+dfsg1-4.1
has caused the Debian Bug report #1023767,
regarding neomutt: unable to find gpgme-config
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Dec 2022 21:06:44 +
with message-id
and subject line Bug#1025332: fixed in ibus-cangjie 2.4-7
has caused the Debian Bug report #1025332,
regarding Subtle build failure
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, 2 Dec 2022 16:39:59 -0400
with message-id <20221202203959.utwhjv7yr6dko...@haydn.kardiogramm.net>
and subject line dh-python dropped 2.x support
has caused the Debian Bug report #634271,
regarding have dh_python2 automatically detect python-pkg-resources dependency
to be mar
Your message dated Fri, 2 Dec 2022 16:39:59 -0400
with message-id <20221202203959.utwhjv7yr6dko...@haydn.kardiogramm.net>
and subject line dh-python dropped 2.x support
has caused the Debian Bug report #903702,
regarding dh-python: dh_python2 & ${python:Depends} gives uninstallable
"pypy:any"
to b
Your message dated Fri, 2 Dec 2022 16:43:10 -0400
with message-id <20221202204310.nbm56qfzttnko...@haydn.kardiogramm.net>
and subject line Re: Bug#925947: apt-listchanges: warns on postinst: -V is
ignored in pypycompile
has caused the Debian Bug report #925947,
regarding apt-listchanges: warns on
Your message dated Fri, 2 Dec 2022 16:39:59 -0400
with message-id <20221202203959.utwhjv7yr6dko...@haydn.kardiogramm.net>
and subject line dh-python dropped 2.x support
has caused the Debian Bug report #732713,
regarding test t201 fails: has wrong assumptions about symlink handling
to be marked as
Your message dated Fri, 2 Dec 2022 16:39:59 -0400
with message-id <20221202203959.utwhjv7yr6dko...@haydn.kardiogramm.net>
and subject line dh-python dropped 2.x support
has caused the Debian Bug report #634271,
regarding dh-python: generate dependency on python{,3}-pkg-resources ?
to be marked as d
Your message dated Fri, 2 Dec 2022 19:37:54 +
with message-id
and subject line Re: Bug#1021319: GIMP crashed with a fatal error: fatal error:
Segmentation fault
has caused the Debian Bug report #1021319,
regarding GIMP crashed with a fatal error: fatal error: Segmentation fault
to be marked a
Your message dated Fri, 2 Dec 2022 19:33:15 +
with message-id
and subject line Re: Bug#1025328: Fwd: GIMP Segmentation fault in
g_object_new_with_properties
has caused the Debian Bug report #1025328,
regarding Fwd: GIMP Segmentation fault in g_object_new_with_properties
to be marked as done.
Your message dated Fri, 02 Dec 2022 19:21:03 +
with message-id
and subject line Bug#978344: fixed in spellutils 0.7+debian-1
has caused the Debian Bug report #978344,
regarding spellutils: FTBFS: configure:4772: error: possibly undefined macro:
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
Your message dated Fri, 2 Dec 2022 20:05:28 +0100
with message-id <20221202190528.mo6wfjhhtf5ie...@jwilk.net>
and subject line Re: Bug#954811: git tag -h: "the field 'creatordate' requires
access to object data"
has caused the Debian Bug report #954811,
regarding git tag -h: "the field 'creatordat
Your message dated Fri, 02 Dec 2022 19:00:16 +
with message-id
and subject line Bug#1025248: fixed in uwsgi 2.0.21-1
has caused the Debian Bug report #1025248,
regarding uwsgi: FTBFS with ruby3.1 as default
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 02 Dec 2022 19:00:16 +
with message-id
and subject line Bug#1024459: fixed in uwsgi 2.0.21-1
has caused the Debian Bug report #1024459,
regarding uwsgi: Build and runtime dependencies on openjdk-11 that will not be
in bookworm
to be marked as done.
This means that you
Your message dated Fri, 02 Dec 2022 19:00:11 +
with message-id
and subject line Bug#1024742: fixed in golang-github-blackfireio-osinfo 1.0.3-1
has caused the Debian Bug report #1024742,
regarding ITP: golang-github-blackfireio-osinfo -- Go library to identify the
underlying operating system
t
Your message dated Fri, 02 Dec 2022 19:00:11 +
with message-id
and subject line Bug#1024740: fixed in golang-github-aquasecurity-table 1.8.0-2
has caused the Debian Bug report #1024740,
regarding ITP: golang-github-aquasecurity-table -- tables for terminals, in Go
(library)
to be marked as do
Your message dated Fri, 02 Dec 2022 19:00:12 +
with message-id
and subject line Bug#1024728: fixed in golang-github-rabbitmq-amqp091-go 1.5.0-1
has caused the Debian Bug report #1024728,
regarding ITP: golang-github-rabbitmq-amqp091-go -- Go client for AMQP 0.9.1
to be marked as done.
This me
Your message dated Fri, 02 Dec 2022 19:00:11 +
with message-id
and subject line Bug#1024583: fixed in golang-github-casbin-casbin 2.57.0-1
has caused the Debian Bug report #1024583,
regarding ITP: golang-github-casbin-casbin -- Authorization library that
supports access control models like AC
Your message dated Fri, 02 Dec 2022 19:00:10 +
with message-id
and subject line Bug#1000803: fixed in dh-python 5.20221203
has caused the Debian Bug report #1000803,
regarding dh-python: add pybuild-autopkgtest, a test runner
to be marked as done.
This means that you claim that the problem ha
Your message dated Fri, 2 Dec 2022 19:55:37 +0100
with message-id
and subject line Re: Bug#1025337: nmu: texstudio_4.3.1+ds-1
has caused the Debian Bug report #1025337,
regarding nmu: texstudio_4.3.1+ds-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Fri, 2 Dec 2022 19:54:48 +0100
with message-id
and subject line Re: Bug#1025293: nmu: tpm2-tools_5.3-1
has caused the Debian Bug report #1025293,
regarding nmu: tpm2-tools_5.3-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 02 Dec 2022 18:08:44 +
with message-id
and subject line Bug#1024941: fixed in pcre2 10.40-3
has caused the Debian Bug report #1024941,
regarding pcre2: support the noudeb build profile
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Fri, 02 Dec 2022 18:04:11 +
with message-id
and subject line Bug#1021875: fixed in dh-python 5.20221202
has caused the Debian Bug report #1021875,
regarding dh-python: dh_python3 does not support --remaining-packages
to be marked as done.
This means that you claim that the
Your message dated Fri, 02 Dec 2022 18:04:11 +
with message-id
and subject line Bug#942959: fixed in dh-python 5.20221202
has caused the Debian Bug report #942959,
regarding dh-python: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been de
Your message dated Fri, 02 Dec 2022 18:04:11 +
with message-id
and subject line Bug#1018952: fixed in dh-python 5.20221202
has caused the Debian Bug report #1018952,
regarding pybuild-plugin-pyproject: Allow building multiple libraries in a
single source package
to be marked as done.
This me
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #986212,
regarding pypy: Intermittent SIGILL and segv on armhf with Armada XP buildds
to be marked as done.
This means that you claim t
Your message dated Fri, 02 Dec 2022 18:01:41 +
with message-id
and subject line Bug#943301: Removed package(s) from unstable
has caused the Debian Bug report #943301,
regarding RM: zyn -- RoQA; py2 leftover; RC buggy; dead upstream
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Dec 2022 18:01:44 +
with message-id
and subject line Bug#943301: Removed package(s) from unstable
has caused the Debian Bug report #967236,
regarding zyn: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #918048,
regarding pypy: FTBFS (stage1) on x32, probably cpu64ilp32 issue
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Dec 2022 18:01:44 +
with message-id
and subject line Bug#943301: Removed package(s) from unstable
has caused the Debian Bug report #964696,
regarding zyn: FTBFS: pkg-config cannot find lv2core
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Dec 2022 18:02:14 +
with message-id
and subject line Bug#945625: Removed package(s) from unstable
has caused the Debian Bug report #945625,
regarding RM: cicero -- RoQA; py2 leftover; dead upstream
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 02 Dec 2022 18:01:08 +
with message-id
and subject line Bug#938645: Removed package(s) from unstable
has caused the Debian Bug report #938645,
regarding RM: telepathy-salut -- RoQA; py2 leftover; dead upstream
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 02 Dec 2022 18:00:35 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #937511,
regarding RM: pypy -- RoQA; py2 leftover; no rdeps
to be marked as done.
This means that you claim that the problem has been d
Your message dated Fri, 02 Dec 2022 18:00:02 +
with message-id
and subject line Bug#1025301: Removed package(s) from unstable
has caused the Debian Bug report #922584,
regarding limereg: depends on non-existing libboost-program-options1.67.0
to be marked as done.
This means that you claim tha
Your message dated Fri, 02 Dec 2022 18:00:02 +
with message-id
and subject line Bug#1025301: Removed package(s) from unstable
has caused the Debian Bug report #922584,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #816043,
regarding PyPy has no _bsddb module
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #801819,
regarding pypy: Creates strange virtualenvs
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #767546,
regarding pypy: Build cppyy backend
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 02 Dec 2022 18:01:12 +
with message-id
and subject line Bug#938645: Removed package(s) from unstable
has caused the Debian Bug report #757129,
regarding telepathy-salut: Fails to send message on IPv6-only system
to be marked as done.
This means that you claim that the
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #703664,
regarding please ship a python-rpython package (or the rpython binary(s) with a
private module)
to be marked as done.
This me
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #732241,
regarding pypy: numpypy no longer included
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Fri, 02 Dec 2022 18:00:42 +
with message-id
and subject line Bug#937511: Removed package(s) from unstable
has caused the Debian Bug report #1011926,
regarding pypy shouldn't be shipped in bookworm
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 02 Dec 2022 17:59:59 +
with message-id
and subject line Bug#1025301: Removed package(s) from unstable
has caused the Debian Bug report #1025301,
regarding RM: limereg -- ROM; Unmaintained upstream + RC buggy
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Dec 2022 17:59:59 +
with message-id
and subject line Bug#1025301: Removed package(s) from unstable
has caused the Debian Bug report #1025301,
regarding RM: limereg -- ROM; Unmaintained upstream + RC buggy
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Dec 2022 17:59:59 +
with message-id
and subject line Bug#1025301: Removed package(s) from unstable
has caused the Debian Bug report #1025301,
regarding RM: limereg -- ROM; Unmaintained upstream + RC buggy
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Dec 2022 17:57:37 +
with message-id
and subject line Bug#1025294: Removed package(s) from unstable
has caused the Debian Bug report #1025294,
regarding RM: cov-core -- ROM; Dead Upstream; Unused; Merged Into Other Projects
to be marked as done.
This means that you c
Your message dated Fri, 02 Dec 2022 17:56:19 +
with message-id
and subject line Bug#1025260: Removed package(s) from unstable
has caused the Debian Bug report #1025260,
regarding RM: wtdbg2 [arm64 armel armhf i386 mips64el mipsel ppc64el s390x
alpha hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd
Your message dated Fri, 02 Dec 2022 17:52:18 +
with message-id
and subject line Bug#1016005: Removed package(s) from unstable
has caused the Debian Bug report #1016005,
regarding RM: jellyfish1 [armel armhf i386 s390x] -- ROM; Does not work on
32bit architectures
to be marked as done.
This m
Your message dated Fri, 02 Dec 2022 12:53:06 -0500
with message-id <2040973.Hf39QsagXs@localhost>
and subject line Re: RM: libnthash-dev [armel armhf i386 mipsel s390x] -- ROM;
Does not build on 32 bit architectures any more
has caused the Debian Bug report #1025225,
regarding RM: libnthash-dev [a
Your message dated Fri, 02 Dec 2022 12:53:34 -0500
with message-id <1851291.D2K6c13GDK@localhost>
and subject line Re: RM: libnthash-dev [armel armhf i386 mipsel s390x] -- ROM;
Does not build on 32 bit architectures any more
has caused the Debian Bug report #1025226,
regarding RM: libnthash-dev [a
Your message dated Fri, 02 Dec 2022 17:52:18 +
with message-id
and subject line Bug#1016005: Removed package(s) from unstable
has caused the Debian Bug report #1016005,
regarding RM: jellyfish1 [alpha armel armhf i386 s390x x32 sparc64 ppc64] --
ROM; architectures are restricted to 64bit - pl
Your message dated Fri, 02 Dec 2022 17:51:27 +
with message-id
and subject line Bug#1025199: Removed package(s) from unstable
has caused the Debian Bug report #1025199,
regarding RM: kraken [armel armhf i386 s390x] -- ROM; dependency jellifish1
doesn't support 32-bit archs
to be marked as don
Your message dated Fri, 02 Dec 2022 17:50:57 +
with message-id
and subject line Bug#1025191: Removed package(s) from experimental
has caused the Debian Bug report #1025191,
regarding RM: cyphesis-cpp/experimental -- ROM; unstable upstream, unsuitable
for Debian
to be marked as done.
This mea
Your message dated Fri, 02 Dec 2022 17:34:47 +
with message-id
and subject line Bug#1020520: fixed in cxxtools 3.0.0-1.1
has caused the Debian Bug report #1020520,
regarding cxxtools: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Fri, 02 Dec 2022 17:35:39 +
with message-id
and subject line Bug#1018382: fixed in iva 1.0.11+ds-3
has caused the Debian Bug report #1018382,
regarding iva: build-depends on python3-nose or uses it for autopkgtest
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 02 Dec 2022 17:20:24 +
with message-id
and subject line Bug#1020527: fixed in pam-p11 0.3.1-1.2
has caused the Debian Bug report #1020527,
regarding pam-p11: upcoming FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 02 Dec 2022 17:05:25 +
with message-id
and subject line Bug#984039: fixed in drawxtl 5.5-6
has caused the Debian Bug report #984039,
regarding drawxtl: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Fri, 02 Dec 2022 17:06:00 +
with message-id
and subject line Bug#1016584: fixed in node-canvas-confetti 1.5.1+~1.4.3-2
has caused the Debian Bug report #1016584,
regarding node-canvas-confetti: please make the build reproducible
to be marked as done.
This means that you cla
Your message dated Sat, 3 Dec 2022 00:45:38 +0800
with message-id
and subject line Re: Wrong soversion in libfm-qt11=1.2.0-1
has caused the Debian Bug report #1024687,
regarding libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities
to be marked as done.
This means that you claim th
Your message dated Fri, 02 Dec 2022 16:36:10 +
with message-id
and subject line Bug#1023738: fixed in orthanc-dicomweb 1.7+dfsg-6
has caused the Debian Bug report #1023738,
regarding orthanc-dicomweb FTBFS with node-axios 1.1
to be marked as done.
This means that you claim that the problem ha
Your message dated Fri, 02 Dec 2022 17:32:22 +0100
with message-id <166999874237.2199.5540921309820018...@auryn.jones.dk>
and subject line Re: ITP: rust-lazy-regex -- lazy static regexes checked at
compile time
has caused the Debian Bug report #1022727,
regarding ITP: rust-lazy-regex -- lazy stati
Your message dated Fri, 02 Dec 2022 17:34:04 +0100
with message-id <166999884466.2199.17991228963706510...@auryn.jones.dk>
and subject line Re: ITP: rust-ureq -- simple and safe HTTP client
has caused the Debian Bug report #1022241,
regarding ITP: rust-ureq -- simple and safe HTTP client
to be mark
Your message dated Fri, 02 Dec 2022 17:29:03 +0100
with message-id <166999854311.2199.7600405185185979...@auryn.jones.dk>
and subject line Re: ITP: rust-isahc -- practical HTTP client that is fun to use
has caused the Debian Bug report #1022811,
regarding ITP: rust-isahc -- practical HTTP client th
Your message dated Fri, 02 Dec 2022 16:20:32 +
with message-id
and subject line Bug#1018477: fixed in python-deeptools 3.5.1-2
has caused the Debian Bug report #1018477,
regarding python-deeptools: build-depends on python3-nose or uses it for
autopkgtest
to be marked as done.
This means that
Your message dated Fri, 02 Dec 2022 15:53:36 +
with message-id
and subject line Bug#1020742: fixed in manpages-l10n 4.16.0-2
has caused the Debian Bug report #1020742,
regarding manpages-l10n: add symlinks rather than relying on whatis references
to be marked as done.
This means that you clai
Your message dated Fri, 02 Dec 2022 15:34:18 +
with message-id
and subject line Bug#1022373: fixed in healpix-java 3.60+ds-5
has caused the Debian Bug report #1022373,
regarding healpix-java: FTBFS: rm: cannot remove 'images': No such file or
directory
to be marked as done.
This means that y
Your message dated Fri, 02 Dec 2022 15:22:45 +
with message-id
and subject line Bug#1010311: fixed in silkaj 0.11.0-1
has caused the Debian Bug report #1010311,
regarding python-duniterpy breaks silkaj autopkgtest: cannot import name
'BlockUID' from 'duniterpy.documents'
to be marked as done.
1 - 100 of 135 matches
Mail list logo
