[Pkg-parrot-devel] Parrot 3.3.0-1 package is in mentors

Alessandro Ghedini al3xbio at gmail.com
Sun Apr 24 20:29:31 UTC 2011


On Sun, Apr 24, 2011 at 11:41:51AM -0700, Allison Randal wrote:
> On 04/24/2011 11:19 AM, Alessandro Ghedini wrote:
> > On Sat, Apr 23, 2011 at 08:16:57PM -0500, Kyle Willmon wrote:
> >>
> >> I use git-buildpackage[1] for the package that I maintain.
> [...]
> > 
> > That's also the tool used by pkg-perl for packages on git and many others
> > packaging teams (e.g. pkg-multimedia).
> [...]
> > (if needed, I can help doing the initial push)
> 
> Those guides are great! Experienced help is always a welcome addition.
> Kyle and Alessandro, if you apply for dev status in pkg-parrot, I'll
> grant you access.
> 
> Alessandro, have you used git-import-dsc or git-import-orig? I'm looking
> for how to import the full history of Parrot Debian packages into the
> git repository. Something like the automated Bazaar imports of Ubuntu
> packages that the Launchpad team does:
> 
> https://wiki.ubuntu.com/DistributedDevelopment/UnderTheHood/Importer
> 
> (It's fine if the solution is a manual series of commands, run on each
> old release, since we're only building the history once.)

git-import-dscs (note the final 's') imports all the versions of a package 
but it does not preserve changelog messages, it only saves e.g. 
"Imported Upstream version X.Y.Z" and "Imported Debian patch X.Y.Z".

You can try this with:

    $ git import-dscs --pristine-tar --debsnap parrot

If you are interested also in the changelog messages it should be possible
to manually modify the "Debian patch" commit messages with git-rebase 
adding the changes from the debian/changelog, e.g:

    Imported Debian patch X.Y.Z

    * Change X
    * Change Y
    ...

Anyway, I'm ghedo-guest on alioth (I can't apply from the web interface 
right now, I'll do it tomorrow if needed).

Cheers

-- 
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'



More information about the Pkg-parrot-devel mailing list