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

Re: guitarix_0.39.0+dfsg1-1_amd64.changes ACCEPTED into unstable



Hi Hermann

On 2020-03-03 10:14:59, Hermann Meyer wrote:
> What is the reason for this:
> 
>  * This package will soon be part of the auto-zita-convolver
>    <https://release.debian.org/transitions/html/auto-zita-convolver.html>
>    transition. You might want to ensure that your package is ready for
>    it. You can probably find supplementary information in the
>    debian-release archives <https://lists.debian.org/debian-release/>
>    or in the corresponding release.debian.org bug
>    <https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=release.debian.org@packages.debian.org;tag=transition>.

This means that zita-convolver 4 is ready in experimental and we need to
allocate a transition slot for that to move to unstable.

> 
>  * excuses <https://qa.debian.org/excuses.php?package=guitarix>:
>      o Migration status for guitarix (0.38.1-1 to 0.39.0+dfsg1-1):
>        BLOCKED: Rejected/violates migration policy/introduces a regression
>      o Issues preventing migration:
>      o Not built on buildd: arch amd64 binaries uploaded by me@viccuad.me
>      o Not built on buildd: arch all binaries uploaded by
>        me@viccuad.me, a new source-only upload is needed to allow migration
>      o Additional info:
>      o Piuparts tested OK -
>        https://piuparts.debian.org/sid/source/g/guitarix.html
>      o 18 days old (needed 5 days)
>      o Not considered

Either a new source only upload is performed or someone requests a
binNMU from the release team. In any case, the binaries need to be built
on a buildd.

> Anything we could help with from upstream?

No, these are issues we have to deal with on the Debian side.

Best
-- 
Sebastian Ramacher


Reply to: