Hi, On 08-06-2019 23:15, Dr. Tobias Quathamer wrote: > thanks for the update. I suspect that the FTBFS is due to the (probably > accidental) upload of a new version of > golang-github-mendersoftware-mender-artifact to unstable instead of > experimental. > > I've just reverted that package with a +really version. Could you > reschedule the binNMU in a couple of hours, after the updated package > has been ACCEPTED in unstable? Will do so shortly. > Should I file a separate bug report for the unblock of > golang-github-mendersoftware-mender-artifact? I'll take care of that. 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 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 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 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 Paul
Attachment:
signature.asc
Description: OpenPGP digital signature