[Pkg-parrot-devel] libparrot6.0.0 gone, rakudo needs a binNMU on amd64?

[Alessandro Ghedini]

On lun, lug 14, 2014 at 06:57:18 +0200, Dominique Dumont wrote:
> On Monday 14 July 2014 15:14:21 you wrote:
> > while going through packages with out of date binaries[1], I noticed
> > that parrot dropped libparrot6.0.0; 
> 
> Weird, I uploaded parrot 6.3.0 a while ago. libparrot6.3.0 for amd64 was 
> supposed to come directly from my machine.

AFAICT parrot is fine, but rakudo still Depends on libparrot6.0.0 and
parrotapi-6.0.0. That's why it's uninstallable in sid (while parrot can be
installed just fine AFAICT).

> > it's seen in the cruft report[2] but
> > it can't go away since rakudo depends on it. It looks to me like rakudo
> > could benefit from a binNMU on amd64?
> 
> ok. If I understand correctly wanna_build.txt, I should ask for a 'gb 
> parrot_6.3.0-1 . amd64' ...
> 
> This should unblock rakudo which was built with parrot_6.3.0.

That's not possible... I just looked and parrot 6.3.0-1 (the current sid
version) was uploaded on 2014-05-05, while rakudo 2014.03.01-1 was uploaded on
2014-04-12, it just can't have been built with parrot 6.3.0. So what needs a
rebuild is actually rakudo, not parrot.

> Except that nqp was upgraded so rakudo must be rebuilt. And rakudo needs to be
> updated.. oh well...

Yeah, it's a pretty big mess. I wonder if instead of doing the parrotapi-* thing
(like perl does) it'd be better to do like gcc and python do, i.e. upload a new
source package for each major version named parrot-X.Y.Z with similarly named
binary packages (parrot-X.Y.Z, parrot-minimal-X.Y.Z, parrot-devel-X.Y.Z, ...)
and then have a parrot-defaults source package with packages named parrot,
parrot-minimal, ... that simply depend on the latest release.

rakudo and nqp would simply (build) depend on whatever parrot-X.Y.Z (with
related parrot-X.Y.Z and libparrotX.Y.Z binary packages) thay need, so that new
parrot versions would not make them uninstallable. parrot needs to go through
NEW anyway on each new release since it always bumps the SONAME for libparrot,
so that wouldn't be any different.

Cheers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-parrot-devel/attachments/20140714/e81acc49/attachment.sig>