[ CC: original Bug #858250 ] On Sun, 07 May 2017 21:02:00 +0000 Niels Thykier <ni...@thykier.net> wrote:
> Roger Shimizu: > > Package: release.debian.org > > Severity: normal > > User: release.debian....@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. > > > Hi Roger, > > Thanks for working on fixing #858250 for stretch. :) > > Before there is an upload to testing-proposed-updates, the original bug > should be resolved in unstable first. That means that #858250 should be > closed in unstable first. > > On a related note, the Debian Bug Tracker can determine which suites are > affected by looking at found + fixed versions, so there is no need to > have two bugs for this (which is why I have merged #861966 back into > #858250). #858250 is not easy to fix for unstable, since there's already newer version runc/1.0.0~rc2+git20161109.131.5137186-2, with newer version of Build-Depends golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1. As stated by #858250, runc is FTBFS with golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1. So my original plan was just patch d/control to limit the version of Build-Depends. 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. What's your opinion? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
pgpE_Tcy57F41.pgp
Description: PGP signature
