Dear Gabriele,

On 14-03-2020 12:02, Gabriele wrote:
> Many thanks for your email. As I have only recently started managing
> packages on Debian, I am not sure if there is anything that I have to do
> about this at all. If I understand correctly, the issue here is caused
> by the fact that the latest sources (which are of version 1.0.0) are no
> longer in sync with the version 0.7.0-1 of the Debian package. Some
> (automated, I think) emails I have received after this one seems to
> suggest that this issue has now been resolved.

Indeed, your package migrated:

paul@testavoira ~ $ rmadison austin -s testing,unstable -asource
austin     | 1.0.0-1       | testing    | source
austin     | 1.0.0-1       | unstable   | source

Looking at the build logs, I think your package failed on armhf,
mips64el and mipsel before, but the underlaying issue apparently was
resolved. Apparently somebody "gave-back" the failed builds, which now
succeeded and the blocking issue was resolved (the missing builds).

> Is my understanding correct? Or is there something that I still need to do?

Your understanding is correct. What you can still do is close this bug.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to