[Pkg-parrot-devel] Parrot 4.3.0 with FTBFS fix, should we package it?

Alessandro Ghedini al3xbio at gmail.com
Sat May 12 14:49:46 UTC 2012


On Thu, Apr 26, 2012 at 12:06:12AM +0200, Alessandro Ghedini wrote:
> I have just created a new repository on git.debian.org to hold the parrot
> packaging [0]. It is based on the github repository of Allison, with the
> addition of the newer Debian versions.
> 
> I have also imported the upstream release 4.3.0 in the topic/release-4.3.0 [1]
> branch. I haven't done much changes, though I am planning to import the
> dh_parrot plugin and friend soonish. You can build the current version with:
> 
> > git clone git+ssh://git.debian.org/git/pkg-parrot/parrot.git
> > git buildpackage --git-debian-branch=topic/release-4.3.0
> 
> I have already tested it with the new releases of both NQP and Rakudo, and
> everything seems to work fine. In any case, before uploading the new version, I
> would wait for 4.0.0 to migrate to testing (that is roughly a couple of weeks if
> everything goes fine).

Given that parrot and its reverse dependencies (nqp and rakudo) migrated to
testing, I think it may be time to finalize the 4.3.0-1 upload (either the one I
have been preparing or any other), possibly in time for the stable freeze.

Allison, what do you think?

Cheers

-- 
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-parrot-devel/attachments/20120512/9e094e0f/attachment.pgp>


More information about the Pkg-parrot-devel mailing list