[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928227: unblock: golang-golang-x-net-dev/1:0.0+git20181201.351d144+dfsg-3



Hi Paul,

On Mon, Jun 10, 2019 at 2:03 AM Paul Gevers <elbrus@debian.org> wrote:
[...]
> However, it seems that my previous report was missing some pieces (I
> only check amd64 last time).
>
> coyim FTBFS previously already on arm64
> https://buildd.debian.org/status/fetch.php?pkg=coyim&arch=arm64&ver=0.3.8%2Bds-6%2Bb10&stamp=1552303594&raw=0
>

No idea why it fails but I can reproduce it. So I filed #930332.

> google-cloud-print-connector FTBFS on armel
> https://buildd.debian.org/status/fetch.php?pkg=google-cloud-print-connector&arch=armel&ver=1.12-1%2Bb22&stamp=1559987469&raw=0
>
> prometheus FTBFS on armel
> https://buildd.debian.org/status/fetch.php?pkg=prometheus&arch=armel&ver=2.7.1%2Bds-3%2Bb11&stamp=1559988997&raw=0
>
> prometheus-alertmanager FTBFS on mips
> https://buildd.debian.org/status/fetch.php?pkg=prometheus-alertmanager&arch=mips&ver=0.15.3%2Bds-3%2Bb1&stamp=1559990584&raw=0
>

For google-cloud-print-connector, prometheus, prometheus-alertmanager,
I've built them successfully on porterbox.
Could you please gb them and try again?

gb google-cloud-print-connector 1.12-1+b22 . armel
gb prometheus 2.7.1+ds-3+b11 . armel
gb prometheus-alertmanager 0.15.3+ds-3+b1 . mips

> rclone FTBFS previously already on mips and mipsel
> https://buildd.debian.org/status/fetch.php?pkg=rclone&arch=mips&ver=1.45-2%2Bb10&stamp=1552305912&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=rclone&arch=mipsel&ver=1.45-2%2Bb10&stamp=1552305234&raw=0
>

I've upload rclone 1.45-3(and already unblocked by niels)

> rkt FTBFS previously already on arm64 and ppc64el
> https://buildd.debian.org/status/fetch.php?pkg=rkt&arch=arm64&ver=1.30.0%2Bdfsg-7%2Bb10&stamp=1552301141&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=rkt&arch=ppc64el&ver=1.30.0%2Bdfsg-7%2Bb10&stamp=1552301135&raw=0
>

I haven't checked this, but it is in autoremoval status.

--
Shengjing Zhu


Reply to: