Your message dated Fri, 31 Jul 2015 10:57:58 -0300
with message-id <[email protected]>
and subject line Re: Bug#793954: "debci status" always uses unstable/amd64
has caused the Debian Bug report #793954,
regarding "debci status" always uses unstable/amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
793954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793954
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debci
Version: 0.12
"bin/debci status --all" currently only works for unstable/amd64, as
there is no --suite/--arch CLI argument parsing. This prevents proper
packages.json generation for multiple suites/archs.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
--- Begin Message ---
On Wed, Jul 29, 2015 at 12:33:17PM +0200, Martin Pitt wrote:
> Package: debci
> Version: 0.12
>
> "bin/debci status --all" currently only works for unstable/amd64, as
> there is no --suite/--arch CLI argument parsing. This prevents proper
> packages.json generation for multiple suites/archs.
I am pretty sure this only applies to the code in git from a few days
ago and not to the code in the archive.
I fixed that yesterday.
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
