Source: lighttpd
Version: 1.4.53-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of lighttpd the autopkgtest of lighttpd fails in
testing when that autopkgtest is run with the binary packages of
lighttpd from
Processing control commands:
> retitle -1 Doxygen breaks toulbar2
Bug #920459 [src:toulbar2] toulbar2 ftbfs in unstable
Changed Bug title to 'Doxygen breaks toulbar2' from 'toulbar2 ftbfs in
unstable'.
> affects 921779 toulbar2
Bug #921779 [src:doxygen] cascade of FTBFS
Added indication that
changetrack 4.7-6 is marked for autoremoval from testing on 2019-03-24
It (build-)depends on packages with these RC bugs:
921758: rcs: FTBFS (failing tests)
simulavr 1.0.0+git20160221.e53413b-1 is marked for autoremoval from testing on
2019-03-25
It (build-)depends on packages with these RC bugs:
921775: avr-libc: FTBFS (LaTeX error)
autofs 5.1.2-4 is marked for autoremoval from testing on 2019-03-24
It (build-)depends on packages with these RC bugs:
921761: sssd: FTBFS (failing tests)
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
reportbug-ng |2.2 | source, all
--- Reason ---
ROM; not maintained by me for long time
--
Note that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #867174,
regarding reportbug-ng: incorrect work with kmail
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #919168,
regarding Please update to python3-debianbts
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #866143,
regarding [reportbug-ng] Unable to select Thunderbird as mail client
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #853186,
regarding reportbug-ng should not depend on any installed mail transport agent
(MTA)
to be marked as done.
This means that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #833935,
regarding [reportbug-ng] Crash on bad connection
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #834104,
regarding reportbug-ng: Uses obsolete dpkg --print-installation-architecture
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #832708,
regarding [reportbug-ng] Generate incorrect URL encoded mail content
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #913365,
regarding [reportbug-ng] ..silly wee typo in reportbug-ng --help output
to be marked as done.
This means that you claim that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #817153,
regarding MUA is opened with empty email
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #899089,
regarding [reportbug-ng] Allow for arbitrary tags in package searches
to be marked as done.
This means that you claim that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #784772,
regarding [reportbug-ng] Dark Theme not Applied
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #764750,
regarding [reportbug-ng] typo within german localisation "Fehlerbericht Details"
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #841527,
regarding reportbug-ng: Missing installed packages versions in the reports
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #755392,
regarding [reportbug-ng] Smart handling for bugs against "general" psedo package
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #764747,
regarding [reportbug] typo within german localisation "Fehlerbericht Details"
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #898499,
regarding [reportbug-ng] sigsegv on exit
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #771030,
regarding reportbug-ng: reportbug does not allow to edit bugreport, hangs
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #774170,
regarding reportbug-ng corrupts non-ACSII characters in summary
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #718441,
regarding reportbug-ng: tool does not find any bugs
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #601232,
regarding [reportbug-ng] if I click on mailto: hyperlink in showed bugreport
nothing happens
to be marked as done.
This
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #710072,
regarding reportbug-ng ignores LC_MESSAGES
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #648224,
regarding [reportbug-ng] no MUA brought up when reporting against hplip with
"Send additional bugscript information if
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #628906,
regarding [reportbug-ng] Strange characters in the report
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #699169,
regarding [reportbug-ng] Calling the MUA failed: Syntax error: EOF in backquote
substitution
to be marked as done.
This
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #72,
regarding reportbung-ng: fails at reporting version number of (some) deps/recs
packages
to be marked as done.
This means
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #648977,
regarding [reportbug-ng] does not escape characters in bug title
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #660477,
regarding [reportbug-ng] segfault after showing image attachment
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #706421,
regarding reportbug-ng will not send bugs: fails invoking mail client
to be marked as done.
This means that you claim that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #691760,
regarding [reportbug-ng] Partially translated into Spanish language
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #655663,
regarding [reportbug-ng] Please support sending copies of reports to other
addresses (X-Debbugs-CC)
to be marked as done.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #624825,
regarding reportbug-ng: Dependence on xterm
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #753819,
regarding Please add support for adding attachments via bug-scripts
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #639441,
regarding [reportbug-ng] Black text color
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #729116,
regarding [reportbug-ng] Calling icedove instead of thunderbird
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #651376,
regarding [reportbug-ng] Many strings are not translated into Spanish.
to be marked as done.
This means that you claim that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #601233,
regarding [reportbug-ng] In displayed bugreport "Open in New Window" and "Save
Link..." context menu options of hyperlinks do
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #597698,
regarding [reportbug-ng] Dialog appearing when reporting to iceweasel is too big
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 15 Feb 2019 15:05:10 -0500
Source: shhopt
Architecture: source
Version: 1.1.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Closes: 909104
Changes:
shhopt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #631621,
regarding [reportbug-ng] Crash on not readable source.list.d/file
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #636665,
regarding [reportbug-ng] report modifying buttons may refer to wrong report
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #626235,
regarding [reportbug-ng] reportbug-ng doesn't show forwarded bugs
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #601234,
regarding [reportbug-ng] Make an option to open selected bugreport(s) in
external browser
to be marked as done.
This means
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #549906,
regarding reportbug-ng: please add bug number on additional information dialog
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #577796,
regarding Should inform the user when BTS is not available.
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #547560,
regarding manpage : French translation
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #594217,
regarding [reportbug-ng] files rejected bug reports due to stray space "Message
with no Package: tag cannot be processed!"
to
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #594216,
regarding [reportbug-ng] doesn't handle non-ASCII characters in summaries ("?",
"?", "?", etc.)
to be marked as done.
This
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #565648,
regarding [reportbug-ng] extraneous characters on the end of the line in
evolution
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #526271,
regarding [reportbug-ng] Show bug report immediately when there's only one
entry in the summary list
to be marked as done.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #544526,
regarding reportbug-ng: dependencies fulfilled by virtual packages lack
information
to be marked as done.
This means that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #548871,
regarding reportbug-ng: does not check for newer versions before reporting a bug
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #498012,
regarding Wish for "Using Reportbug-NG" text to be hideable.
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #526125,
regarding reportbug-ng: please make it easier to distinguish initial report and
followups
to be marked as done.
This means
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #530945,
regarding [reportbug-ng] package specific information window too big
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #494282,
regarding [reportbug-ng] ultimate user friendliness using WM_CLASS
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #489359,
regarding [reportbug-ng] update-button
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #526122,
regarding reportbug-ng: doesn't include any identification field in mail headers
to be marked as done.
This means that you
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #507980,
regarding [reportbug-ng] Add a mode for tracking bug
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #509991,
regarding [reportbug-ng] (with evolution) Please add support for choosing
default reporting mail address
to be marked as
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #464843,
regarding bookmark option
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #478436,
regarding [reportbug-ng] Do not work with a proxy with password
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #498014,
regarding Wish for shorter column name than "Bugnumber", e.g. "No." or "ID"
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #492715,
regarding doublequotes entered in input field summary do NOT get escaped,
following * triggers shell filename expansion
to be
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #457189,
regarding please add tab support
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #482827,
regarding [reportbug-ng] Please add message for: "package not found" and
"package has not bugs"
to be marked as done.
This
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #458571,
regarding Please run debsums before submitting a bug report
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #448852,
regarding reportbug-ng: some Debian terms are not explained for novices
to be marked as done.
This means that you claim that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #457045,
regarding Visually mark merged bugs.
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #458575,
regarding Make it possible to manipulate the bug status
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #448847,
regarding reportbug-ng: translations should tell the user to try to talk in
english
to be marked as done.
This means that
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #445287,
regarding doesn't report network error
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #416133,
regarding Package history drop-down
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #431788,
regarding [reportbug-ng] Please add support for GMail and Hotmail webmails if
possible.
to be marked as done.
This means
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #431788,
regarding Gmail, or at least $EDITOR as mail client
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #435553,
regarding Add search on package names
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #452818,
regarding Misses support for Bugs: control field
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #433580,
regarding Doesn't adhere to bidi status
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #435849,
regarding please map + on "ok" of close/moreinfo details dialog
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #440568,
regarding No feedback on MUA invocation
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #416586,
regarding Please provide option to define own MUA/editor combo
to be marked as done.
This means that you claim that the
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #431788,
regarding Add the possibility to send bug with webmail (gmail in my case)
to be marked as done.
This means that you claim
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #433300,
regarding Allow searching in the bug text
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #432129,
regarding addtional information - no tags available
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:55:13 +
with message-id
and subject line Bug#922382: Removed package(s) from unstable
has caused the Debian Bug report #431318,
regarding option to submit to lists.debian.org
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Feb 2019 20:44:25 +
with message-id
and subject line Bug#909104: fixed in shhopt 1.1.7-4
has caused the Debian Bug report #909104,
regarding shhopt FTCBFS: does not pass cross tools to make
to be marked as done.
This means that you claim that the problem has been
shhopt_1.1.7-4_source.changes uploaded successfully to localhost
along with the files:
shhopt_1.1.7-4.dsc
shhopt_1.1.7-4.debian.tar.xz
shhopt_1.1.7-4_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
binary:libzbarqt-dev is NEW.
binary:libzbarqt0 is NEW.
binary:libzbarqt0 is NEW.
binary:libzbarqt-dev is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are
Your message dated Fri, 15 Feb 2019 12:56:14 -0500
with message-id
and subject line Mark bug 602954 as done
has caused the Debian Bug report #602954,
regarding zbar-tools: zbarimg should accept an image on stdin
to be marked as done.
This means that you claim that the problem has been dealt
zbar_0.21-4_amd64.changes uploaded successfully to localhost
along with the files:
zbar_0.21-4.dsc
zbar_0.21.orig.tar.gz
zbar_0.21-4.debian.tar.xz
libbarcode-zbar-perl-dbgsym_0.21-4_amd64.deb
libbarcode-zbar-perl_0.21-4_amd64.deb
libzbar-dev_0.21-4_amd64.deb
Your message dated Fri, 15 Feb 2019 12:52:26 -0500
with message-id <5fe968bf8d5e971aa1915f9632efe615a0462257.ca...@debian.org>
and subject line Mark bug 910899 as done
has caused the Debian Bug report #910899,
regarding zbar: SQ code support
to be marked as done.
This means that you claim that
Source-only uploads to NEW are not allowed.
binary:libzbarqt-dev is NEW.
binary:libzbarqt0 is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
zbar_0.21-4_source.changes uploaded successfully to localhost
along with the files:
zbar_0.21-4.dsc
zbar_0.21-4.debian.tar.xz
zbar_0.21-4_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
-3) unstable; urgency=medium
.
* QA upload.
* debian/patches:
+ Replace custom codespell typo fix patches with upstream
applied one.
+ Cherry-pick upstream patches till 20190215 to fix grammar
error in configure.ac script.
* debian/control:
+ Mark libbarcode
Package: irqbalance
Version: 1.5.0-3
Severity: normal
irqbalance apparently now depends on runit-helper.
For systems without runit installed, that is a strange additional
dependency.
Would it be possible to remove that dependency (or move it to a
Recommends: or something) to help make simpler
1 - 100 of 103 matches
Mail list logo
