Re: Go protobuf v2
On Fri, Jul 10, 2020 at 2:45 AM Clément Hermann <nodens@debian.org> wrote:
[...]
> Not really, sounds like the best plan available to me.
> Do we know how many package are affected, currently ?
>
The bump of golang-goprotobuf-dev from v1.3.4 to v1.4.x itself needs
to take care.
Last week I rebuilt the reverse. Some important packages FTBFS.
2020/07/08 05:23:16 FAILED: packer, but maybe unrelated to new changes
(see buildlogs/packer_1.3.4+dfsg-4 and
buildlogs_recheck/packer_1.3.4+dfsg-4)
2020/07/08 05:23:16 FAILED: flannel, but maybe unrelated to new
changes (see buildlogs/flannel_0.9.1~ds1-1 and
buildlogs_recheck/flannel_0.9.1~ds1-1)
2020/07/08 05:23:16 FAILED: gitaly, but maybe unrelated to new changes
(see buildlogs/gitaly_1.78.0+dfsg-2 and
buildlogs_recheck/gitaly_1.78.0+dfsg-2)
2020/07/08 05:23:16 FAILED: prometheus-process-exporter, but maybe
unrelated to new changes (see
buildlogs/prometheus-process-exporter_0.4.0+ds-1 and
buildlogs_recheck/prometheus-process-exporter_0.4.0+ds-1)
2020/07/08 05:23:16 FAILED: gitlab-ci-multi-runner, but maybe
unrelated to new changes (see
buildlogs/gitlab-ci-multi-runner_13.0.1+dfsg-1 and
buildlogs_recheck/gitlab-ci-multi-runner_13.0.1+dfsg-1)
2020/07/08 05:23:16 FAILED: golang-github-containers-image, but maybe
unrelated to new changes (see
buildlogs/golang-github-containers-image_5.0.0-2 and
buildlogs_recheck/golang-github-containers-image_5.0.0-2)
2020/07/08 05:23:16 FAILED: rkt, but maybe unrelated to new changes
(see buildlogs/rkt_1.30.0+dfsg1-9 and
buildlogs_recheck/rkt_1.30.0+dfsg1-9)
2020/07/08 05:23:16 FAILED: golang-google-cloud (see
buildlogs/golang-google-cloud_0.56.0-1)
2020/07/08 05:23:16 FAILED: consul (see buildlogs/consul_1.7.4+dfsg1-1)
2020/07/08 05:23:16 FAILED: golang-github-grpc-ecosystem-grpc-gateway
(see buildlogs/golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2)
2020/07/08 05:23:16 FAILED: etcd (see buildlogs/etcd_3.2.26+dfsg-8)
AFAIK, It's not urgent to update this package, maybe we can even start
the transition post bullseye.
--
Shengjing Zhu
Reply to: