Hi backports team,

On Sat, 18 May 2019 10:22:10 +0200 Andreas Beckmann <a...@debian.org> wrote:
> Package: netdata-core
> Version: 1.12.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: close -1 1.12.1-2
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch-backports' to 'buster' due to a version oerdering violation.
> 
> netdata-core | 1.12.0-1        | testing           | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.12.1-2~bpo9+1 | stretch-backports | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.12.2-2        | unstable          | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.14.0-1        | experimental      | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

The current version of netdata-core in unstable is very unlikely to get
unblocked. What do you suggest to do in such a case, remove the package
from stretch-backports? It doesn't comply with the backports policy.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to