[CC'ed are the maintainers of reverse (build-)dependencies.
Please reply only to .
If you're interested in this discussion, consider subscribing that list.]
Hi,
On 29.04.2015 20:56, Alessio Treglia wrote:
> I am afraid that I have to revive this discussion once again now that
> Jessie is out as w
mailping_0.0.4-3_amd64.changes uploaded successfully to localhost
along with the files:
mailping_0.0.4-3.dsc
mailping_0.0.4-3.diff.gz
mailping_0.0.4-3_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
--
To UNSUBSCRIBE, email to debian-qa-packages-re
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 01 May 2015 14:00:51 +
Source: mailping
Binary: mailping
Architecture: source all
Version: 0.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Thijs Kinkhorst
Description:
Package: mksh
Version: 50d-5
Severity: wishlist
Tags: upstream
Recently, since pdksh on Debian is now implemented by mksh, command-line
history no longer works like it used to several years ago.
I use ksh in vi-editing mode (set -o vi and FCEDIT=vi). Quite often, I
write short multi-line comman
blackbox_0.70.1-27_amd64.changes uploaded successfully to localhost
along with the files:
blackbox_0.70.1-27.dsc
blackbox_0.70.1-27.debian.tar.xz
blackbox_0.70.1-27_amd64.deb
libbt-dev_0.70.1-27_amd64.deb
libbt0_0.70.1-27_amd64.deb
Greetings,
Your Debian queue daemon (running on
Kenneth Pronovici dixit:
>I'll file a Debian bug to document the improvements I asked for, just
Please DO NOT file Debian bugs for upstream issues in mksh,
only for packaging issues.
This has been at the top of README.Debian for ages.
Debian bugs requesting functionality changes are likely to
g
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 01 May 2015 15:24:01 -0300
Source: blackbox
Binary: blackbox libbt-dev libbt0
Architecture: source amd64
Version: 0.70.1-27
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Herbert Pare
Your message dated Sat, 2 May 2015 01:14:41 +0200
with message-id <20150501231441.ga26...@sym.noone.org>
and subject line Re: Bug#482538: ytalk: unsafe use of getenv
has caused the Debian Bug report #482538,
regarding ytalk: unsafe use of getenv
to be marked as done.
This means that you claim that
Kenneth Pronovici dixit:
>I'm not trying to be snarky here, but I'm a little lost. This package
>is orphaned. If you're no longer the package maintainer, why should
>it even matter to you whether upstream issues are tracked as Debian
>bugs?
Because
① I’m upstream,
② I’m maintaining this packa
On Fri, May 1, 2015 at 5:36 PM, Thorsten Glaser wrote:
> Kenneth Pronovici dixit:
>>I'll file a Debian bug to document the improvements I asked for, just
> Please DO NOT file Debian bugs for upstream issues in mksh,
> only for packaging issues.
>
> This has been at the top of README.Debian for age
Kenneth Pronovici dixit:
>I filed the bug so nothing would get lost while the package is
>orphaned, which seems like a reasonable thing to do. The next
That may seem reasonable…
>maintainer might very well have a different policy for Debian bugs
>than you did. I would if it were my package.
…
On Fri, May 1, 2015 at 6:18 PM, Thorsten Glaser wrote:
> Kenneth Pronovici dixit:
>>I'm not trying to be snarky here, but I'm a little lost. This package
>>is orphaned. If you're no longer the package maintainer, why should
>>it even matter to you whether upstream issues are tracked as Debian
>>
12 matches
Mail list logo
