Bug#928455: [pre-a] unblock: perl6-zef/0.6.2-2
Control: tags -1 moreinfo confirmed
Mo Zhou:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> X-Debbugs-CC: Robert Lemmen <robertle@semistable.com>, Dominique Dumont <dod@debian.org>
>
> Please unblock package perl6-zef
>
> (explain the reason for the unblock here)
>
> As I reported in #928454, the outdated mirror URL list renders zef,
> the perl6 package manager nearly unusable:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928454
>
> Luckily we can fix the package for Buster by simply updating the list:
> https://github.com/ugexe/zef/blob/master/resources/config.json#L60-L62
> I asked upstream author on IRC and they acked that the mirror list is
> not likely to be changed for the Buster lifecycle.
>
> (include/attach the debdiff against the package in testing)
>
> ```
> --- config.json.orig 2019-05-05 03:31:08.251673414 +0000
> +++ config.json 2019-05-05 03:32:01.744441262 +0000
> @@ -57,10 +57,9 @@
> "name" : "p6c",
> "auto-update" : 1,
> "mirrors" : [
> - "http://ecosystem-api.p6c.org/projects1.json",
> - "http://ecosystem-api.p6c.org/projects.json",
> + "https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json",
> "git://github.com/ugexe/Perl6-ecosystems.git",
> - "https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json"
> + "http://ecosystem-api.p6c.org/projects1.json"
> ]
> }
> },
> ```
>
> unblock perl6-zef/0.6.2-2
>
> [...]
>
Hi,
Please go ahead with the upload and remove the moreinfo tag when it is
in unstable and ready to be unblocked.
For future reference:
* We generally need to full debdiff to know exactly what we will be
approving. In this case, I assumed you need that change plus an
upload to d/changelog only (hopefully sparing us from a round trip)
* Assuming this is indeed the only change, it would have been faster
and easier for both parties if you had uploaded it to sid in parallel
with the unblock request.
- I appreciate that you may prefer a "rather safe than sorry"-
approach, which is greatly appreciated with potential risky
changes.
Thanks,
~Niels
Reply to: