Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

2023-07-16 Thread gregor herrmann
On Sun, 16 Jul 2023 06:42:53 +0400, Yadd wrote:

> Gitlab::API::v4 uses JSON::MaybeXS which may use a different JSON stack. I
> just added a "use JSON" in t/salsa.pm. Maybe this is enough to fix this
> issue
> 
> https://salsa.debian.org/debian/devscripts/-/commit/5bbc8778

Thanks for taking care of this issue!

I think it also needs a runtime dependency on libjson-perl, cf.
https://bugs.debian.org/1038486
https://salsa.debian.org/debian/devscripts/-/merge_requests/356


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

2023-07-15 Thread Yadd

On 7/15/23 22:46, Paul Gevers wrote:

Source: libgitlab-api-v4-perl
Version: 0.26-3
Severity: serious
Control: close -1 0.27-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038486

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:libgitlab-api-v4-perl has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The package in 
unstable triggers an autopkgtest issue in devscripts, which is reported 
in bug 1038486.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul


Hi,

the error looks to be:

 55s t/salsa-config.t .. ok
 56s Undefined subroutine ::to_json called at ./t/salsa.pm line 49.
 56s # Tests were run but no plan was declared and done_testing() was 
not seen.

 56s # Looks like your test exited with 255 just after 1.
 56s t/salsa.t .

Gitlab::API::v4 uses JSON::MaybeXS which may use a different JSON stack. 
I just added a "use JSON" in t/salsa.pm. Maybe this is enough to fix 
this issue


https://salsa.debian.org/debian/devscripts/-/commit/5bbc8778

Regards,
Yadd



Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

2023-07-15 Thread Paul Gevers

Source: libgitlab-api-v4-perl
Version: 0.26-3
Severity: serious
Control: close -1 0.27-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038486

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:libgitlab-api-v4-perl has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The package in 
unstable triggers an autopkgtest issue in devscripts, which is reported 
in bug 1038486.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=libgitlab-api-v4-perl



OpenPGP_signature
Description: OpenPGP digital signature