Hi Shengjing, On 10-06-2019 19:52, Shengjing Zhu wrote: > On Mon, Jun 10, 2019 at 2:03 AM Paul Gevers <elbrus@debian.org> wrote: >> 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 Done and it worked, but ehwww. Please try to figure out how to improve robustness. >> 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. But not for so long. So I expect it to be worked on. A build failure fix is needed for that CVE upload as well. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature