Your message dated Sat, 1 Oct 2022 01:53:21 +0200
with message-id <fe058e33-9bc8-382e-c485-253520ea8...@debian.org>
and subject line Re: support aliases by default or manual for suite names
has caused the Debian Bug report #990004,
regarding support aliases by default or manual for suite names
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 ow...@bugs.debian.org
immediately.)
--
990004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debspawn
Version: 0.5.0-1
Severity: wishlist
I have a container named sid-amd64 but it cannot be used if I mention
suite as unstable. I think it would be a good idea to have this mapping
by default for official names.
$ debspawn build unstable
[sudo] password for pravi:
ERROR: The container image for "unstable-amd64" does not exist. Please
create it first.
$ debspawn list
[sid-amd64]
Architecture = amd64
Suite = sid
Size = 234.6MiB
--- End Message ---
--- Begin Message ---
Source: debspawn
Source-Version: 0.5.1-1
Done: Matthias Klumpp <m...@debian.org>
Hi!
This issue was actually already addressed in debspawn 0.5.1, but somehow
this bug report fell through the cracks.
Images can now have arbitrary names (but if none is given, they will
pick the suite name by default).
Cheers,
Matthias
--- End Message ---
