Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 02 Sep 2019 20:14:44 -0400
Source: xmldiff
Architecture: source
Version: 2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Sandro Tosi
Closes: 269347 524981 588148 921610
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 02 Sep 2019 20:19:23 -0400
Source: xmldiff
Architecture: source
Version: 2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Sandro Tosi
Changes:
xmldiff (2.3-2) unstable;
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #629380,
regarding qemu-kvm: Cannot create domain (/usr/bin/kvm exit status 1)
to be marked as done.
This means that you claim that
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #643581,
regarding ulatencyd: start-up timing issue
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #740771,
regarding ulatencyd: Ulatencyd not mout all threads on multithread programs
(plugin-container)
to be marked as done.
This
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #739859,
regarding ulatencyd: Ulatencyd don't do anithing
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #379534,
regarding svnmailer: first non empty log line in the subject
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #379533,
regarding svnmailer: please support some $body configureability
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #411759,
regarding author should be configurable via config file
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #469184,
regarding svnmailer: Should support multiple recipients with a single to_addr
containing substitutions
to be marked as done.
Your message dated Tue, 03 Sep 2019 05:33:51 +
with message-id
and subject line Bug#938725: Removed package(s) from unstable
has caused the Debian Bug report #565800,
regarding tunapie: audio player: not possible to use "killall -e vlc ; vlc "
to be marked as done.
This means that you claim
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #412027,
regarding svnmailer: "diffs stripped" MIME part has incorrect
Content-Disposition
to be marked as done.
This means that you
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #629380,
regarding ulatencyd: virtinst fails to create VM because it cannot create cgroup
to be marked as done.
This means that you
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #643580,
regarding lxc should handle cgroups by itself
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #740829,
regarding ulatencyd: When set user.poison on plugin-container gnome-shell is
put on psn_ group wo notice.
to be marked as
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #643580,
regarding ulatencyd: tries to mount cgroup sysfs
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:32:37 +
with message-id
and subject line Bug#938607: Removed package(s) from unstable
has caused the Debian Bug report #379535,
regarding svnmailer: diff in a single part instead of splitted diff
to be marked as done.
This means that you claim that the
Your message dated Mon, 2 Sep 2019 23:24:49 -0400
with message-id
and subject line Re: xmldiff: wrong result on small change - xmldiff removes
text node
has caused the Debian Bug report #882582,
regarding xmldiff: wrong result on small change - xmldiff removes text node
to be marked as done.
Version: 0.11.0-7+rm
Dear submitter,
as the package dynagen has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936460
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
fts | 1.1-2 | source, all
fts-clacks | 1.1-2 | all
fts-fai-ldap | 1.1-2 | all
fts-ltsp-ldap | 1.1-2 | all
fts-opsi | 1.1-2 | all
---
Version: 1.1-2+rm
Dear submitter,
as the package fts has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936568
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
dynagen | 0.11.0-7 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Version: 0.1.3+dfsg-9+rm
Dear submitter,
as the package djagios has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936410
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
djagios | 0.1.3+dfsg-9 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #741086,
regarding ulatencyd: Please on systemd place start position after
systemd-logind.service
to be marked as done.
This means
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #755373,
regarding systemd-sysv: Can not normal shutdown with ulatencyd
to be marked as done.
This means that you claim that the
Version: 1.0.2-2+rm
Dear submitter,
as the package tagainijisho has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/939281
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #757341,
regarding ulatencyd conflicts with default systemd configuration
to be marked as done.
This means that you claim that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
tagainijisho |1.0.2-2 | source, amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
tagainijisho-common |1.0.2-2 | all
tagainijisho-dic-de |1.0.2-2 | all
xmldiff_2.3-2_source.changes uploaded successfully to localhost
along with the files:
xmldiff_2.3-2.dsc
xmldiff_2.3-2.debian.tar.xz
xmldiff_2.3-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
xmldiff_2.3-1_source.changes uploaded successfully to localhost
along with the files:
xmldiff_2.3-1.dsc
xmldiff_2.3.orig.tar.gz
xmldiff_2.3-1.debian.tar.xz
xmldiff_2.3-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#524981: fixed in xmldiff 2.3-1
has caused the Debian Bug report #524981,
regarding xmldiff: "IndexError" when comparing two files which have namespaces
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#921610: fixed in xmldiff 2.3-1
has caused the Debian Bug report #921610,
regarding xmldiff: update package to 2.2 with python3 support
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#938849: fixed in xmldiff 2.3-1
has caused the Debian Bug report #938849,
regarding xmldiff: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:37:45 +
with message-id
and subject line Bug#939281: Removed package(s) from unstable
has caused the Debian Bug report #875200,
regarding [tagainijisho] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Sep 2019 05:37:45 +
with message-id
and subject line Bug#939281: Removed package(s) from unstable
has caused the Debian Bug report #672718,
regarding tagainijisho: some part of GUI is too small to display its content
to be marked as done.
This means that you claim
Your message dated Tue, 03 Sep 2019 05:37:45 +
with message-id
and subject line Bug#939281: Removed package(s) from unstable
has caused the Debian Bug report #801599,
regarding tagainijisho: Tagaini Jisho 1.0.3 released 08. Mar, 2015
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #755373,
regarding systemd-sysv: Can not normal /sbin/shutdown (even as root)
to be marked as done.
This means that you claim that the
Version: 2.1.19-1+rm
Dear submitter,
as the package tunapie has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938725
The
Version: 0.5.0-9+rm
Dear submitter,
as the package ulatencyd has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938749
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
whyteboard | 0.41.1-6 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Version: 0.41.1-6+rm
Dear submitter,
as the package whyteboard has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938822
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #755996,
regarding ulatencyd: Install ulatencyd with systemd can not normal shutdown
(even as root)
to be marked as done.
This means
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #743686,
regarding ulatencyd: Ulatencyd start without consolekit support
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 05:35:03 +
with message-id
and subject line Bug#938822: Removed package(s) from unstable
has caused the Debian Bug report #774724,
regarding whyteboard: "Sheets -> Resize Canvas" window cannot be closed -
lockup.
to be marked as done.
This means that you
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #741902,
regarding ulatencyd: clashes with libvirt-bin
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #741505,
regarding ulatencyd: On group active unable to set cpu.share from configuration
to be marked as done.
This means that you
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #744897,
regarding ulatency-gui don't start any gui
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #682712,
regarding ulatencyd: please use system copy of libprocps
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Sep 2019 05:33:51 +
with message-id
and subject line Bug#938725: Removed package(s) from unstable
has caused the Debian Bug report #835357,
regarding tunapie: [INTL:pt_BR] rename pt.po to pt_BR.po
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #772383,
regarding ulatencyd: bashism in /bin/sh script
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:34:27 +
with message-id
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #892756,
regarding ulatencyd: fix lua or luajit build dependency
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Sep 2019 05:37:45 +
with message-id
and subject line Bug#939281: Removed package(s) from unstable
has caused the Debian Bug report #673118,
regarding tagainijisho: should not check for new version by default
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 05:37:45 +
with message-id
and subject line Bug#939281: Removed package(s) from unstable
has caused the Debian Bug report #672728,
regarding tagainijisho: tagaini jisho doesn't warn when preferred dictionary
language isn't installed
to be marked as done.
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
tunapie | 2.1.19-1 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
ulatency | 0.5.0-9+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
ulatencyd |0.5.0-9 | source
ulatencyd | 0.5.0-9+b1 | amd64, arm64, armel, armhf, i386,
Your message dated Tue, 03 Sep 2019 05:25:09 +
with message-id
and subject line Bug#936410: Removed package(s) from unstable
has caused the Debian Bug report #933259,
regarding djagios: Useless after icinga removal
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:26:17 +
with message-id
and subject line Bug#936460: Removed package(s) from unstable
has caused the Debian Bug report #572451,
regarding dynagen: Add an option to avoid asking for importing configurations
to be marked as done.
This means that you claim
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
mailman-api |0.2.9-2 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Version: 0.99.1-5+rm
Dear submitter,
as the package gozerbot has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936642
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gozerbot | 0.99.1-5 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gaduhistory | 0.5-4 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
nixstatsagent | 1.1.32-2 | source, amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
--- Reason ---
RoQA; orphaned; Python 2 only; dead
Version: 0.5.dfsg-3+rm
Dear submitter,
as the package p9m4 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/937228
The
Version: 1.1.32-2+rm
Dear submitter,
as the package nixstatsagent has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
p9m4 | 0.5.dfsg-3 | source
prover9-mace4 | 0.5.dfsg-3 | all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
photo-uploader | 0.12-4 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; upstream discontinued support; low popcon
Version: 0.12-4+rm
Dear submitter,
as the package photo-uploader has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/937284
Version: 0.5-4+rm
Dear submitter,
as the package gaduhistory has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936576
Version: 0.2.9-2+rm
Dear submitter,
as the package mailman-api has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/936980
Your message dated Mon, 2 Sep 2019 23:26:41 -0400
with message-id
and subject line Removal of xupdate from xmldiff
has caused the Debian Bug report #275755,
regarding python2.3-xmldiff: Whitespace handling incorrect
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 2 Sep 2019 23:26:41 -0400
with message-id
and subject line Removal of xupdate from xmldiff
has caused the Debian Bug report #269349,
regarding python2.3-xmldiff: xupdate output contains unneeded statements
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 2 Sep 2019 23:26:41 -0400
with message-id
and subject line Removal of xupdate from xmldiff
has caused the Debian Bug report #270188,
regarding python2.3-xmldiff: xupdate output format incorrect (for lexus)
to be marked as done.
This means that you claim that the problem
On Sun, 18 Aug 2019 13:59:42 +0200 Peter Kleiweg wrote:
> Package: xmldiff
> Version: 0.6.10-3
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> I ran xmldiff on two xml files.
>
>* What was the outcome of this action?
>
> The program immediately swallowed up
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #566507,
regarding podracer: podracer may put torrent file in the podcast directory
instead of donwloading the podcast
to be marked as
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #353301,
regarding podracer: configurability of the output directory
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #377660,
regarding podracer: fails to download long URLs
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #396257,
regarding podracer: loses contents of log file if disk is full
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Sep 2019 05:31:26 +
with message-id
and subject line Bug#938312: Removed package(s) from unstable
has caused the Debian Bug report #871747,
regarding qmtest: please transition from jadetex to texlive-formats-extra
to be marked as done.
This means that you claim
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #812980,
regarding podracer: .mp3/.ogg/.m4a/.m4b than the extension of the file will not
be registered in the play list.
to be marked
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #386042,
regarding podracer: Fails with traceback as result
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #353298,
regarding podracer: add a verbose option
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Sep 2019 05:30:01 +
with message-id
and subject line Bug#937306: Removed package(s) from unstable
has caused the Debian Bug report #530873,
regarding fails to download from Bitfellas podcast
to be marked as done.
This means that you claim that the problem has been
Version: 1.0.9-3+rm
Dear submitter,
as the package svnmailer has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938607
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
svnmailer |1.0.9-3 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Version: 2.4.1-3+rm
Dear submitter,
as the package qmtest has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938312
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
python-sigmask |2.4.1-3 | amd64, arm64, armel, armhf, i386, mipsel,
ppc64el, s390x
python-sigmask | 2.4.1-3+b1 | mips64el
qmtest |2.4.1-3 | source, all
---
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#269347: fixed in xmldiff 2.3-1
has caused the Debian Bug report #269347,
regarding python2.3-xmldiff: output illogical and inefficient
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#588148: fixed in xmldiff 2.3-1
has caused the Debian Bug report #588148,
regarding Description of xmldiff states correction instead of comparison
to be marked as done.
This means that you claim that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
podracer | 1.4-4 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
Version: 1.4-4+rm
Dear submitter,
as the package podracer has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/937306
The
Version: 0.1.1-7+rm
Dear submitter,
as the package swaml has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938609
The
Version: 1.0.0-4+rm
Dear submitter,
as the package pybit has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/937390
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
swaml |0.1.1-7 | source, all
--- Reason ---
RoQA; orphaned; Python 2 only; dead upstream; low popcon
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
pybit |1.0.0-4 | source
pybit-client |1.0.0-4 | all
pybit-common |1.0.0-4 | all
pybit-svn |1.0.0-4 | all
pybit-watcher |1.0.0-4 | all
pybit-web |1.0.0-4 |
Your message dated Mon, 02 Sep 2019 06:33:12 +
with message-id
and subject line Bug#937390: Removed package(s) from unstable
has caused the Debian Bug report #789906,
regarding pybit: Obsolete ‘daemon.pidlockfile’ API migrated to
‘python-lockfile’ library
to be marked as done.
This means
Your message dated Mon, 02 Sep 2019 06:34:33 +
with message-id
and subject line Bug#938609: Removed package(s) from unstable
has caused the Debian Bug report #509204,
regarding swaml: Manpage doesn't help wrt config file
to be marked as done.
This means that you claim that the problem has
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 02 Sep 2019 08:37:15 -0300
Source: dpatch
Architecture: source
Version: 2.0.39
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Joao Eriberto Mota Filho
Changes:
dpatch (2.0.39)
Processing control commands:
> block 936325 with 936221 936394 936460 938945 936996 937330 937336 937577
> 936237 883146 939024 938425 938623 938728
Bug #936325 [src:configobj] configobj: Python2 removal in sid/bullseye
936325 was not blocked by any bugs.
936325 was not blocking any bugs.
Added
dpatch_2.0.39_source.changes uploaded successfully to localhost
along with the files:
dpatch_2.0.39.dsc
dpatch_2.0.39.tar.xz
dpatch_2.0.39_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
1 - 100 of 120 matches
Mail list logo
