Re: Why is knot migration blocked by done 1081191?

* Niels Thykier [241108 14:12]: > Jakub Ružička: > > I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's > > marked as Done but the bug still blocks knot migration for reasons I > > don't understand: > > https://qa.debian.org/excuses.php?package=knot > > The problem is that the B

Re: Why is knot migration blocked by done 1081191?

Jakub Ružička: Hello, I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's marked as Done but the bug still blocks knot migration for reasons I don't understand: https://qa.debian.org/excuses.php?package=knot What do I need to do to finally finish migration? Cheers, Jakub Ruž

Why is knot migration blocked by done 1081191?

Hello, I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's marked as Done but the bug still blocks knot migration for reasons I don't understand: https://qa.debian.org/excuses.php?package=knot What do I need to do to finally finish migration? Cheers, Jakub Ružička signature.

Re: autopkgtest on s390x (was: Migration blocked by tests of depending package)

On Sat, 26 Oct 2024 at 11:02:29 +0200, Joachim Zobel wrote: > I have tried all available --boot options for autopkgtest with s390x > and was not able to create an image I suspect you mean autopkgtest-{build,virt}-qemu. autopkgtest itself (the test runner) does not have a --boot option. The ci.deb

Re: Migration blocked by tests of depending package

Am Freitag, dem 25.10.2024 um 08:08 +0200 schrieb Paul Gevers: > > 2. I am unable to reproduce the failing test since there is no working > > --boot option for autopkgtest and and I can't find any info on how to > > run qemu for that architecture. > > > I don't understand the remark in the first

Re: Migration blocked by tests of depending package

Hi Joachim, On 25-10-2024 07:22, Joachim Zobel wrote: The migration of our package mosquitto is blocked by failing autopkgtests of the depending package node-mqtt on s390x (See [1]). I have reported this as a bug for the failing depending package [2]. Thanks for reporting. To be fair, the s39

Migration blocked by tests of depending package

Hi. The migration of our package mosquitto is blocked by failing autopkgtests of the depending package node-mqtt on s390x (See [1]). I have reported this as a bug for the failing depending package [2]. We are facing two issues with this: 1. We would like to move to testing soon as the release fix

Re: Migration blocked

On 12/6/23 23:02, Paul Gevers wrote: Hi, On 05-12-2023 03:52, Yadd wrote:  I uploaded src:node-proxy-agents into unstable, which is the new source of node-proxy and node-https-proxy-agent. This package didn't migrate but I don't understand the reason of this block. The tracker[1] reports reg

Re: Migration blocked

Hi, On 05-12-2023 03:52, Yadd wrote: I uploaded src:node-proxy-agents into unstable, which is the new source of node-proxy and node-https-proxy-agent. This package didn't migrate but I don't understand the reason of this block. The tracker[1] reports regressions on node-proxy and node-https-

Re: Migration blocked

On 12/5/23 06:52, Yadd wrote: Hi all, I uploaded src:node-proxy-agents into unstable, which is the new source of node-proxy and node-https-proxy-agent. This package didn't migrate but I don't understand the reason of this block. The tracker[1] reports regressions on node-proxy and node-http

Migration blocked

Hi all, I uploaded src:node-proxy-agents into unstable, which is the new source of node-proxy and node-https-proxy-agent. This package didn't migrate but I don't understand the reason of this block. The tracker[1] reports regressions on node-proxy and node-https-proxy-agent (which are replac