Your message dated Sat, 12 Jan 2019 10:44:29 +0100
with message-id <20190112094429.ga2...@semistable.com>
and subject line fixed in 2018.12
has caused the Debian Bug report #915561,
regarding moarvm 2018.11 appears to be broken
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.)
--
915561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moarvm
Version: 2018.11+dfsg-1
Severity: important
moarvm 2018.11 seems to be broken on soem architectures, as evident from
the buildd logs of nqp and rakudo. filing this bug to keep the broken
2018.11 out of testing in favor of 2018.10. dependencies will make sure
nqp, rakudo and perl itself are kept in unstable in the broken versions
as well
--- End Message ---
--- Begin Message ---
2018.12 builds on all archs now, closing
--
Robert Lemmen http://www.semistable.com
signature.asc
Description: PGP signature
--- End Message ---
