Bug#861953: marked as done (unblock: runc/0.1.1+dfsg1-3)
Your message dated Fri, 19 May 2017 22:14:26 +0900
with message-id <[hidden email]>
and subject line Re: Bug#861953: unblock: runc/0.1.1+dfsg1-3
has caused the Debian Bug report #861953,
regarding unblock: runc/0.1.1+dfsg1-3
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 [hidden email] immediately.)
User: [hidden email] Usertags: unblock
Please unblock package runc
Since there's already a newer package in unstable, I guess it's
necessary to use "testing-proposed-updates"
Here I'm fixing #858250, which is FTBFS RC issue.
As I test, it's not related to golang-github-urfave-cli, but only need
to fix the version of golang-github-opencontainers-specs, 1.0.0~rc1,
the version in stretch.
Without the patch, unstable targeting build will install
golang-github-opencontainers-specs 1.0.0~rc2, and final fail to build.
I try to build by command:
DIST=stretch git-pbuilder create
gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder --git-dist=stretch
On Thu, 18 May 2017 12:48:11 +0100
Jonathan Wiltshire <[hidden email]> wrote:
> Control: tag -1 wontfix moreinfo
> On 2017-05-08 00:40, Roger Shimizu wrote:
> > Since you say it should fix unstable first, then stretch or t-p-u,
> > now I think we may just leave runc/0.1.1+dfsg1-2 (current in stretch)
> > as it is in stretch. Because it builds OK (without FTBFS) for stretch.
> > The #858250 FTBFS only occurs on unstable.
> If runc currently builds in stretch, there is no need to touch it (and
> #858250 should be tagged 'sid').
> It's not clear from #858250 if that is actually the case or not though.