Re: Sponsorship for Math::Quaternion and File::Tee
> On Fri, 2 Nov 2012 23:22:18 +0100
> Salvatore Bonaccorso <carnil@debian.org> wrote:
>
> Hi Dima
>
> On Fri, Nov 02, 2012 at 02:27:09PM -0700, Dima Kogan wrote:
> > I've got a set of packages I'd like to get sponsored. They have been done for a
> > little while, and seem to work well.
> >
> > The first ones are these two:
> >
> > http://mentors.debian.net/package/libmath-quaternion-perl
> > http://mentors.debian.net/package/libfile-tee-perl
> >
> > They are both more or less straight out of dh-make-perl, with cleaned up
> > descriptions, copyrights and such. The repos are already on Alioth. The ITP bugs
> > are attached in the mentors links above.
>
> Hmm, have you added them via guide in[1]? It looks like they are
> missing in our meta.git mrconfig.
>
> [1]: http://pkg-perl.alioth.debian.org/git.html#pushing_to_git_debian_org
>
> We have a meta.git repository, containing a .mrconfig to be able to
> track all pkg-perl packages.
The instructions say
$ ../../alioth-git-repo
I wasn't clear on where to get this (apt-file couldn't find it). Searching more
thoroughly, it looks like it lives in pkg-perl/meta.git, as you say. The
document didn't state this at all. What do you think about packaging those tools
together with dh-make-perl? Even if the document was clear, I don't think it
should be required to have to check out some git repo in order to push up the
code "correctly". I can help with this.
For the record, I used dh-make-perl to create the repo. This created an "origin"
remote, but didn't actually create it on the server, which made "git push" not
work. I then used "gbp-create-remote" to create the server repo and push it up.
Another nice thing to do would be to make gbp-create-remote recognize that it's
pushing up to a particular project (pkg-perl in this case), and to do whatever
extra work is needed. Then the individual teams wouldn't need to have different
procedures. I know this involves more than just pkg-perl, but it could be a good
goal. Thoughts?
dima
Reply to: