freedink-dfarc_3.14-4_source.changes uploaded successfully to localhost
along with the files:
freedink-dfarc_3.14-4.dsc
freedink-dfarc_3.14-4.debian.tar.xz
freedink-dfarc_3.14-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 12 Sep 2020 09:37:01 +0200
Source: freedink-dfarc
Architecture: source
Version: 3.14-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Pino Toscano
Changes:
freedink-dfarc (3.14-4
ncap_1.9.2-7_source.changes uploaded successfully to localhost
along with the files:
ncap_1.9.2-7.dsc
ncap_1.9.2-7.debian.tar.xz
ncap_1.9.2-7_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Sat, 12 Sep 2020 21:21:07 +
with message-id
and subject line Bug#969849: fixed in ncap 1.9.2-7
has caused the Debian Bug report #969849,
regarding ncap: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been dealt
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 12 Sep 2020 21:48:39 +0100
Source: ncap
Architecture: source
Version: 1.9.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Sudip Mukherjee
Closes: 969849
Changes:
ncap (1.9.2-7
Chris Lamb wrote:
> [..]
Friendly ping on this?
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Package: doclifter
Version: 2.19-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Issuing "doclifter groff_diff.7", which produced a few lines on
standard error.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Running "pylint /usr/bi
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#935184: fixed in mdadm 4.1-6
has caused the Debian Bug report #935184,
regarding mdadm: [INTL:fr] French debconf templates translation
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#872118: fixed in mdadm 4.1-6
has caused the Debian Bug report #872118,
regarding mdadm: fdisk build-dependency needed (for tests)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#932791: fixed in mdadm 4.1-6
has caused the Debian Bug report #932791,
regarding mdadm: inconsistent documentation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#915182: fixed in mdadm 4.1-6
has caused the Debian Bug report #915182,
regarding mdadm: typo in man page
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#960132: fixed in mdadm 4.1-6
has caused the Debian Bug report #960132,
regarding mdadm: mdcheck_start.service trying to start unexisting file
to be marked as done.
This means that you claim that the problem ha
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#933773: fixed in mdadm 4.1-6
has caused the Debian Bug report #933773,
regarding mdadm: manual page incorrectly documents --size option
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#619043: fixed in mdadm 4.1-6
has caused the Debian Bug report #619043,
regarding mdadm: [PATCH] debian/README.recipes - Clarify short options
to be marked as done.
This means that you claim that the problem ha
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#956350: fixed in mdadm 4.1-6
has caused the Debian Bug report #956350,
regarding mdadm: [INTL:de] updated German debconf translation
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#916946: fixed in mdadm 4.1-6
has caused the Debian Bug report #916946,
regarding mdadm: Trivial typo in man page (not the same as in bug 915182)
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#940851: fixed in mdadm 4.1-6
has caused the Debian Bug report #940851,
regarding [INTL:nl] Updated Dutch translation for the configuration of mdadm
to be marked as done.
This means that you claim that the prob
Your message dated Sun, 13 Sep 2020 04:18:28 +
with message-id
and subject line Bug#962946: fixed in mdadm 4.1-6
has caused the Debian Bug report #962946,
regarding mdadm: --name not valid in grow mode
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Hi Adam,
> /usr/share/mdadm/mkconf attempts to read DEVICE out of
> /etc/mdadm/mdadm.conf, using sed. It does this, with a simple regex,
> "s/^DEVICE //p". This is not valid.
Doesn't mkconf merely transfer the value? I think the code works as
expected. It may not work for other whitespace, as yo
Your message dated Sat, 12 Sep 2020 21:52:08 -0700
with message-id
and subject line mdadm: Cron comment doesn't match code
has caused the Debian Bug report #853042,
regarding mdadm: Cron comment doesn't match code
to be marked as done.
This means that you claim that the problem has been dealt wi
20 matches
Mail list logo
