Your message dated Fri, 19 May 2017 22:14:26 +0900 with message-id <20170519221426.0f118ca7d46da601aeb7ccda@gmail.com> 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 owner@bugs.debian.org immediately.) -- 861953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861953 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: runc/0.1.1+dfsg1-3
- From: Roger Shimizu <rogershimizu@gmail.com>
- Date: Sat, 06 May 2017 21:16:59 +0900
- Message-id: <[🔎] 590dbebe.858a620a.b755b.ac64@mx.google.com>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org 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. https://mentors.debian.net/package/runc 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 Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1diff -Nru runc-0.1.1+dfsg1/debian/changelog runc-0.1.1+dfsg1/debian/changelog --- runc-0.1.1+dfsg1/debian/changelog 2017-02-02 00:17:54.000000000 +0900 +++ runc-0.1.1+dfsg1/debian/changelog 2017-05-06 19:57:12.000000000 +0900 @@ -1,3 +1,15 @@ +runc (0.1.1+dfsg1-3) testing-proposed-updates; urgency=medium + + * Team upload. + * debian/control: + - Add Build-Depends: + golang-github-opencontainers-specs-dev (<< 1.0.0~rc2) + Since golang-github-opencontainers-specs-dev in sid is 1.0.0~rc2 + Which has FTBFS issue. We need to use the fixed version in + stretch, which is 1.0.0~rc1. (Closes: #858250) + + -- Roger Shimizu <rogershimizu@gmail.com> Sat, 06 May 2017 19:57:12 +0900 + runc (0.1.1+dfsg1-2) unstable; urgency=medium * Team upload. diff -Nru runc-0.1.1+dfsg1/debian/control runc-0.1.1+dfsg1/debian/control --- runc-0.1.1+dfsg1/debian/control 2016-11-30 07:18:25.000000000 +0900 +++ runc-0.1.1+dfsg1/debian/control 2017-05-06 19:57:12.000000000 +0900 @@ -14,6 +14,7 @@ golang-github-coreos-go-systemd-dev, golang-github-docker-go-units-dev, golang-github-opencontainers-specs-dev (>= 1.0.0~), + golang-github-opencontainers-specs-dev (<< 1.0.0~rc2), golang-github-seccomp-libseccomp-golang-dev, golang-github-vishvananda-netlink-dev, golang-go,
--- End Message ---
--- Begin Message ---
- To: Jonathan Wiltshire <jmw@debian.org>, 861953-done@bugs.debian.org, 858250@bugs.debian.org
- Subject: Re: Bug#861953: unblock: runc/0.1.1+dfsg1-3
- From: Roger Shimizu <rogershimizu@gmail.com>
- Date: Fri, 19 May 2017 22:14:26 +0900
- Message-id: <20170519221426.0f118ca7d46da601aeb7ccda@gmail.com>
- In-reply-to: <[🔎] 446e0924bc30da0db92623f60a7ba03d@debian.org>
- References: <[🔎] 590dbebe.858a620a.b755b.ac64@mx.google.com> <[🔎] 17bb8b04-71a9-8b19-4af3-2657a42bfda9@thykier.net> <[🔎] 20170508084052.a13de61eeafbd5843909eed7@gmail.com> <[🔎] 446e0924bc30da0db92623f60a7ba03d@debian.org>
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 <jmw@debian.org> 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: http://debomatic-amd64.debian.net/distribution#testing/runc/0.1.1+dfsg1-2/buildlog So I close the unblock request, and mark the original bug only affects unstable. It's not a RC for stretch. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1Attachment: pgpc_59M8cEe4.pgp
Description: PGP signature
--- End Message ---