Hi Shengjing, On 19-05-2019 17:01, Shengjing Zhu wrote: > On Sun, May 19, 2019 at 4:06 AM Paul Gevers <elbrus@debian.org> wrote: >> On 18-05-2019 17:10, Shengjing Zhu wrote: >>> On Sat, May 18, 2019 at 10:53 PM Paul Gevers <elbrus@debian.org> wrote: >>> I'm sure most packages can't migrate to testing after binNMU in unstable. >>> like etcd, nomad, snapd, umoci... which build-depends >>> golang-golang-x-sys and/or golang-github-mattn-go-isatty(which are >>> updated in unstable unexpectedly). >> >> Can those packages be reverted to have the content of buster, e.g. with >> a +really version? Than we can schedule the binNMU's in unstable and >> have them migrate with these changelog only change packages. >> > > This could cause another mess. Since we are close to buster release, I > hope this can be avoid... I fear this is part of the problem of the static linking in combination with the freeze. Without major changes to the Debian infrastructure, the golang ecosystem really needs to refrain from updating in unstable during the freeze. At this moment it's best to make unstable in line with testing again. > 1. I'm not sure how many golang dev packages started a "trasition" in unstable, > > ``` > zhsj@coccia:~$ cat golang-divarication.sql [...] > (And please take another note that some leaf/binary packages, like > hugo, influxdb, mtail.. already uploaded new version in unstable...) They will need to be reverted as well if I understand correctly. > 2. more packages need rebuild I don't understand why you say that. Only the reverse build dependencies of golang-golang-x-net-dev need to be rebuild and migrate to testing, no? That the packages in unstable aren't all build with the sources in unstable is normal right, so no big deal. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature