Bug#861953: marked as done (unblock: runc/0.1.1+dfsg1-3)

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Bug#861953: marked as done (unblock: runc/0.1.1+dfsg1-3)

Debian Bug Tracking System
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]

861953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861953
Debian Bug Tracking System
Contact [hidden email] with problems

Package: release.debian.org
Severity: normal
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

I'm not DD yet, so I uploaded the package to mentors.

Please help to:
  - confirm it's OK to target "testing-proposed-updates"
  - help to sponsor the upload from mentors (if not, I'll file a RFS to
        mentors list)

Enclosed is the debdiff against the package in testing.

unblock runc/0.1.1+dfsg1-3

Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

control: tag 858250 -pending
control: affects 858250 -stretch +sid
control: notfound 858250 0.1.1+dfsg1-2

On Thu, 18 May 2017 12:48:11 +0100
Jonathan Wiltshire <[hidden email]> wrote:

> Control: tag -1 wontfix moreinfo
> Hi,
> 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.
Thanks for your explanation!

Yes, it builds well in stretch.
I did a s/unstable/testing/ for latest changelog, and upload it to DoM:

So I close the unblock request, and mark the original bug only affects unstable.
It's not a RC for stretch.

Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

debdiff_runc_0.1.1+dfsg1_-2_and-3.txt (1K) Download Attachment
attachment1 (849 bytes) Download Attachment