Your message dated Tue, 27 Aug 2019 03:02:49 +
with message-id
and subject line Bug#875165: fixed in qwt 6.1.4-1.1
has caused the Debian Bug report #875165,
regarding [qwt] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 27 Aug 2019 02:37:37 +
with message-id
and subject line Bug#925637: fixed in bcal 2.1+git20190806.6c8d325-1
has caused the Debian Bug report #925637,
regarding bcal: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> close 927702
Bug #927702 [sponsorship-requests] RFS: python-aiosqlite/0.10.0-1 [ITP] --
sqlite library for Python 3 using asyncio
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
927702:
Processing commands for cont...@bugs.debian.org:
> close 923683
Bug #923683 [sponsorship-requests] RFS: python-pynetstring/0.2-1 [ITP] --
netstring library for Python 3
Marked Bug as done
> stop
Stopping processing here.
Please contact me if you need assistance.
--
923683:
Your message dated Tue, 27 Aug 2019 01:07:26 +
with message-id
and subject line Bug#935769: Removed package(s) from experimental
has caused the Debian Bug report #916505,
regarding tensorflow: Please package the Python interface for tensorflow
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 01:07:22 +
with message-id
and subject line Bug#935769: Removed package(s) from experimental
has caused the Debian Bug report #935769,
regarding RM: tensorflow -- ROM; orphaned
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:07:26 +
with message-id
and subject line Bug#935769: Removed package(s) from experimental
has caused the Debian Bug report #927205,
regarding O: tensorflow -- Computation using data flow graphs for scalable
machine learning
to be marked as done.
This
Your message dated Tue, 27 Aug 2019 01:07:26 +
with message-id
and subject line Bug#935769: Removed package(s) from experimental
has caused the Debian Bug report #929485,
regarding libtensorflow-dev: Missing dependency - package depends on
libprotoc-dev
to be marked as done.
This means that
Your message dated Tue, 27 Aug 2019 01:05:47 +
with message-id
and subject line Bug#935854: Removed package(s) from unstable
has caused the Debian Bug report #860983,
regarding pylint: called emacs-package-install as a new-style add-on, but has
no compat file
to be marked as done.
This
Your message dated Tue, 27 Aug 2019 01:04:08 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #935848,
regarding RM: musique -- RoQA; unmaintained, depends on qt4
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Aug 2019 01:02:35 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #935841,
regarding RM: python-googlecloudapis -- RoM; RC-buggy; uninstallable
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:05:47 +
with message-id
and subject line Bug#935854: Removed package(s) from unstable
has caused the Debian Bug report #928705,
regarding pylint: Missing dependency on astroid 1.5.0
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:03:47 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #874822,
regarding [automoc] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:03:47 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #879292,
regarding Updating the automoc Uploaders list
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:02:40 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #927169,
regarding python-googlecloudapis: unsatisfiable build-dependencies in sid
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 01:04:36 +
with message-id
and subject line Bug#935850: Removed package(s) from unstable
has caused the Debian Bug report #935850,
regarding RM: qxmlrpc -- RoQA; depends on qt4, dead upstream, unmaintained, no
reverse dependencies
to be marked as done.
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #875061,
regarding [musique] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:05:47 +
with message-id
and subject line Bug#935854: Removed package(s) from unstable
has caused the Debian Bug report #613646,
regarding pylint.el redefines emacs key bindings which are reserved for the user
to be marked as done.
This means that you
Your message dated Tue, 27 Aug 2019 01:02:40 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #838638,
regarding /usr/bin/python3-google-api-tools broken; missing several
dependencies, does not work even after doing so
to be
Your message dated Tue, 27 Aug 2019 01:05:42 +
with message-id
and subject line Bug#935854: Removed package(s) from unstable
has caused the Debian Bug report #935854,
regarding RM: pylint2 -- ROM; replaced by pylint
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:03:09 +
with message-id
and subject line Bug#935840: Removed package(s) from unstable
has caused the Debian Bug report #906195,
regarding O: python-protorpc-standalone -- Google Protocol RPC
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:03:09 +
with message-id
and subject line Bug#935840: Removed package(s) from unstable
has caused the Debian Bug report #904603,
regarding python3-protorpc-standalone: fails to install with Python 3.7
to be marked as done.
This means that you claim that
Your message dated Tue, 27 Aug 2019 01:03:05 +
with message-id
and subject line Bug#935840: Removed package(s) from unstable
has caused the Debian Bug report #935840,
regarding RM: python-protorpc-standalone -- RoQA; orphaned; RC-buggy;
incompatible with Python 3.7
to be marked as done.
Your message dated Tue, 27 Aug 2019 01:02:40 +
with message-id
and subject line Bug#935841: Removed package(s) from unstable
has caused the Debian Bug report #927316,
regarding python3-googlecloudapis: The python3-googlecloudapis package says it
provides the Python 2.x version
to be marked
Your message dated Tue, 27 Aug 2019 01:06:09 +
with message-id
and subject line Bug#935856: Removed package(s) from unstable
has caused the Debian Bug report #935856,
regarding RM: astroid2 -- ROM; outdated, replaced by astroid, only required by
pylint2 (RM'ed too)
to be marked as done.
Your message dated Tue, 27 Aug 2019 01:03:41 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #935847,
regarding RM: automoc -- RoQA; depends on qt4
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:04:39 +
with message-id
and subject line Bug#935850: Removed package(s) from unstable
has caused the Debian Bug report #875178,
regarding [qxmlrpc] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:03:47 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #809530,
regarding Please set CMake Policy 0059 to avoid loads of warnings
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:05:47 +
with message-id
and subject line Bug#935854: Removed package(s) from unstable
has caused the Debian Bug report #563000,
regarding pylint: wrongly tries to open emacs locks
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #705985,
regarding musique: When musique create first library access, fs change to
read-only
to be marked as done.
This means that
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #662017,
regarding musique: Sort artists/albums alphabetically
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #694455,
regarding musique: Artists are shown wrong
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #719453,
regarding Please update musique
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #655898,
regarding musique can only read one collection directory
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:03:47 +
with message-id
and subject line Bug#935847: Removed package(s) from unstable
has caused the Debian Bug report #487710,
regarding automoc: Package description is not clear
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 01:04:16 +
with message-id
and subject line Bug#935848: Removed package(s) from unstable
has caused the Debian Bug report #662014,
regarding musique: Provide list views
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #741042,
regarding rebuildd daemon dies when requeueing a job
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:00:57 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #921957,
regarding O: pygdchart2 -- Python OO interface to GDChart
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #779554,
regarding rebuildd: provide an option to not store the build logs in the
database
to be marked as done.
This means that you
Your message dated Tue, 27 Aug 2019 01:00:51 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #935837,
regarding RM: pygdchart2 -- RoQA; orphaned; ancient; dead upstream; no Python 3
support and no reverse deps
to be marked as
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #784941,
regarding rebuildd-httpd crashes due to bug in gdchart
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:00:57 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #468987,
regarding buggy Python API memory handling in example C code
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #928532,
regarding O: rebuildd -- build daemon aiming at rebuilding Debian packages
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #863526,
regarding rebuildd: homepage link is broken
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:00:57 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #301564,
regarding python2.3-gdchart2: Pie problems with 0 values
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #673435,
regarding tarball contains build/ directory and build-stamp-rebuildd
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:00:57 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #450330,
regarding pygdchart2: debian/watch fails to report upstream's version
to be marked as done.
This means that you claim that
Your message dated Tue, 27 Aug 2019 01:00:57 +
with message-id
and subject line Bug#935837: Removed package(s) from unstable
has caused the Debian Bug report #433627,
regarding pygdchart2: diff for NMU version 0.beta1-3.4
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #875059,
regarding [ntrack] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:59:07 +
with message-id
and subject line Bug#935757: Removed package(s) from unstable
has caused the Debian Bug report #935757,
regarding RM: bzr-search -- ROM; unmaintained upstream, python2 only
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #610570,
regarding rebuildd exit in unittest with disk I/O error
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #663196,
regarding rebuildd: please add hook after a build failure
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #874844,
regarding [choreonoid] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 27 Aug 2019 00:57:30 +
with message-id
and subject line Bug#935742: Removed package(s) from unstable
has caused the Debian Bug report #874864,
regarding [daemonfs] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:58:18 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #935751,
regarding RM: ntrack -- RoQA; unmaintained, dead upstream, partly depends on
qt4, no reverse deps
to be marked as done.
This
Your message dated Tue, 27 Aug 2019 00:59:59 +
with message-id
and subject line Bug#935835: Removed package(s) from unstable
has caused the Debian Bug report #866431,
regarding htmlgen: depends on obsolete python-imaging (replace with python3-pil
or python-pil)
to be marked as done.
This
Your message dated Tue, 27 Aug 2019 00:59:59 +
with message-id
and subject line Bug#935835: Removed package(s) from unstable
has caused the Debian Bug report #588724,
regarding python-htmlgen: MailTo.antispam() doesn't work with Python >= 2.5
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #659143,
regarding Add multi repository support
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #657914,
regarding rebuildd: Add debconf configuration
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 00:58:45 +
with message-id
and subject line Bug#935756: Removed package(s) from unstable
has caused the Debian Bug report #935756,
regarding RM: bzr-xmloutput -- ROM; python2 only, unmaintained
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 00:59:55 +
with message-id
and subject line Bug#935835: Removed package(s) from unstable
has caused the Debian Bug report #935835,
regarding RM: htmlgen -- RoQA; orphaned; RC-buggy; ancient; no Python 3 support
and no reverse deps
to be marked as done.
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #834718,
regarding choreonoid: maintainer address bounces
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #759408,
regarding [ntrack-module-libnl-0] Not work with kernel 3.16
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 27 Aug 2019 00:58:48 +
with message-id
and subject line Bug#935756: Removed package(s) from unstable
has caused the Debian Bug report #667637,
regarding RFA: bzr-xmloutput -- XML Communication plugin for Bazaar
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:00:21 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #935836,
regarding RM: rebuildd -- RoQA; orphaned; low popcon; dead upstream; Python
2-only
to be marked as done.
This means that you
Your message dated Tue, 27 Aug 2019 00:57:53 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #935747,
regarding RM: choreonoid -- RoQA; unmaintained, RC-buggy, depends on qt4
to be marked as done.
This means that you claim that
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #843875,
regarding ntrack: checking reportbug for real
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #595716,
regarding rebuildd daemon dies - "sqlobject.dberrors.OperationalError: database
is locked"
to be marked as done.
This means
Your message dated Tue, 27 Aug 2019 00:59:59 +
with message-id
and subject line Bug#935835: Removed package(s) from unstable
has caused the Debian Bug report #929537,
regarding O: htmlgen -- Python library for the generation of HTML
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #834715,
regarding libcnoid-dev: arch-dependent file in "Multi-Arch: same" package
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #842763,
regarding choreonoid FTBFS on armel and armhf: no matching function for call to
'QTransform::map(int, int, double*, double*)'
Your message dated Tue, 27 Aug 2019 00:59:34 +
with message-id
and subject line Bug#935758: Removed package(s) from unstable
has caused the Debian Bug report #935758,
regarding RM: snakefood -- ROM; python2 code; not needed anymore
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 01:00:32 +
with message-id
and subject line Bug#935836: Removed package(s) from unstable
has caused the Debian Bug report #553418,
regarding Please include an error for missing rebuildd-httpd dependancies
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #859357,
regarding choreonoid shouldn't disable PIE
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 00:58:00 +
with message-id
and subject line Bug#935747: Removed package(s) from unstable
has caused the Debian Bug report #807796,
regarding choreonoid: incomplete copyright
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 27 Aug 2019 00:57:26 +
with message-id
and subject line Bug#935742: Removed package(s) from unstable
has caused the Debian Bug report #935742,
regarding RM: daemonfs -- RoQA; depends on qt4, dead upstream, unmaintained
to be marked as done.
This means that you claim
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #672786,
regarding libntrack0: Crash inside ntrack during kde startup (or when running
kded)
to be marked as done.
This means that
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #664064,
regarding linux-image-3.3.0-rc6-amd64: 4 messages every minute in syslog from
netlink
to be marked as done.
This means that
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #589343,
regarding fails to build with -jmany
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #766765,
regarding ntrack-module-rtnetlink-0: IPv6 network status not reported correctly
to be marked as done.
This means that you
Your message dated Tue, 27 Aug 2019 00:58:27 +
with message-id
and subject line Bug#935751: Removed package(s) from unstable
has caused the Debian Bug report #641231,
regarding libntrack0: circular dependency with ntrack-module-libnl-0
to be marked as done.
This means that you claim that the
Your message dated Mon, 26 Aug 2019 20:26:34 -0400
with message-id <20190827002634.ga22...@digitalmercury.dynalias.net>
and subject line Re: Bug#657730: Confirmed in 3.39.1+dfsg-2 (buster)
has caused the Debian Bug report #657730,
regarding calibre: crashes before starting
to be marked as done.
Your message dated Mon, 26 Aug 2019 20:23:31 -0400
with message-id <20190827002257.ga21...@digitalmercury.dynalias.net>
and subject line Re: Bug#677110: Please confirm if bug affects a supported
Calibre version
has caused the Debian Bug report #677110,
regarding calibre: Error trying to open some
Your message dated Mon, 26 Aug 2019 20:15:26 -0400
with message-id <20190827001523.ga21...@digitalmercury.dynalias.net>
and subject line Re: Bug#917579: new upstream version (3.36)
has caused the Debian Bug report #917579,
regarding new upstream version (3.36)
to be marked as done.
This means
Your message dated Tue, 27 Aug 2019 01:29:17 +0200
with message-id <94c5deda-ca36-6bd1-e1aa-1ef4fc1b1...@fishpost.de>
and subject line Bug#610741: fixed in mtd-utils 1:2.1.1-1
has caused the Debian Bug report #610741,
regarding mtd-utils: Some spelling errors in mkfs.jffs2 help and manpage
to be
Your message dated Tue, 27 Aug 2019 01:22:43 +0200
with message-id
and subject line Re: Bug#911078: triplea: Fails to start with
NullPointerException
has caused the Debian Bug report #911078,
regarding triplea: Fails to start with NullPointerException
to be marked as done.
This means that you
Your message dated Mon, 26 Aug 2019 23:16:02 +
with message-id
and subject line Bug#931977: fixed in startpar 0.64~beta-1
has caused the Debian Bug report #931977,
regarding startpar: uninitialized variable
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 26 Aug 2019 23:14:20 +
with message-id
and subject line Bug#633858: fixed in insserv 1.21.0~beta-1
has caused the Debian Bug report #633858,
regarding -v not as safe as it sounds
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 26 Aug 2019 23:06:57 +
with message-id
and subject line Bug#916182: fixed in dbacl 1.14.1-2
has caused the Debian Bug report #916182,
regarding dbacl FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 26 Aug 2019 19:06:59 -0400
with message-id <20190826230656.ga14...@digitalmercury.dynalias.net>
and subject line fixed
has caused the Debian Bug report #714572,
regarding emacs-goodies-el: csv-mode customize-mode
to be marked as done.
This means that you claim that the
Your message dated Tue, 27 Aug 2019 00:40:50 +0200
with message-id <20190826224050.ga22...@angband.pl>
and subject line Re: Bug#935808: RFS: dbacl 1.14.1-2 [QA upload]
has caused the Debian Bug report #935808,
regarding RFS: dbacl/1.14.1-2 -- digramic Bayesian text classifier
to be marked as done.
Your message dated Mon, 26 Aug 2019 22:36:57 +
with message-id
and subject line Bug#934930: fixed in novnc 1:1.0.0-2
has caused the Debian Bug report #934930,
regarding python-novnc: depends on cruft package.
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 26 Aug 2019 18:12:07 -0400
with message-id <871rx7y3t4.fsf@paluero>
and subject line Re: Bug#935806: RFS: ffe 0.3.9-1 [QA upload]
has caused the Debian Bug report #935806,
regarding RFS: ffe/0.3.9-1 -- Tool for parsing flat and CSV files and
converting them to different
Your message dated Mon, 26 Aug 2019 21:48:37 +
with message-id
and subject line Bug#902257: fixed in man-db 2.8.7-1
has caused the Debian Bug report #902257,
regarding groff-base: nroff crashes when the environment variable SHELL is unset
to be marked as done.
This means that you claim that
Your message dated Mon, 26 Aug 2019 21:50:19 +
with message-id
and subject line Bug#916041: fixed in uw-imap 8:2007f~dfsg-7
has caused the Debian Bug report #916041,
regarding libc-client2007e: add SNI support
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 26 Aug 2019 21:50:19 +
with message-id
and subject line Bug#876074: fixed in uw-imap 8:2007f~dfsg-7
has caused the Debian Bug report #876074,
regarding uw-imap FTCBFS: uses the build architecture compiler
to be marked as done.
This means that you claim that the
Your message dated Mon, 26 Aug 2019 21:50:19 +
with message-id
and subject line Bug#770022: fixed in uw-imap 8:2007f~dfsg-7
has caused the Debian Bug report #770022,
regarding libc-client2007e: unselectable socket in ssl_getdata() where sock >=
FD_SETSIZE (similar to #478193)
to be marked as
Your message dated Mon, 26 Aug 2019 21:34:23 +
with message-id
and subject line Bug#925645: fixed in blender 2.80+dfsg-3
has caused the Debian Bug report #925645,
regarding blender: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 26 Aug 2019 21:10:11 +
with message-id
and subject line Bug#844046: fixed in weasyprint 48-1
has caused the Debian Bug report #844046,
regarding ITP: : weasyprint -- Visual rendering engine for HTML and CSS that
can export to PDF
to be marked as done.
This means that
Your message dated Mon, 26 Aug 2019 21:09:11 +
with message-id
and subject line Bug#935831: fixed in node-turbolinks 5.2.0+dfsg-1
has caused the Debian Bug report #935831,
regarding node-turbolinks: Incorrect symlink to /usr/lib in
/usr/share/javascript
to be marked as done.
This means that
1 - 100 of 206 matches
Mail list logo
