Re: Please remember to push the pristine-tar branch!
Excerpts from Lucas Nussbaum's message of Thu May 19 09:39:20 -0700 2011:
> On 19/05/11 at 07:44 -0700, Clint Byrum wrote:
> > Excerpts from Antonio Terceiro's message of Wed May 18 13:50:47 -0700 2011:
> > > Jérémy Lal escreveu isso aí:
> > > > On 17/05/2011 22:25, Lucas Nussbaum wrote:
> > > > > Hi,
> > > > >
> > > > > Please remember to create and push the pristine-tar branch, so that we
> > > > > can recreate identical source packages from the git repo.
> > > > >
> > > > > If you use a squeeze development system, I don't think that it's an
> > > > > issue: git import-orig will create the pristine-tar branch
> > > > > automatically. If you don't, I'm not sure of what is going wrong, but if
> > > > > you find out, please document it in the RubyInWheezy wiki page.
> > > >
> > > > You might want to add a debian/gbp.conf file containing :
> > > > [DEFAULT]
> > > > pristine-tar = True
> > > > sign-tags = True
> > > >
> > > > Another usage of that file that could be interesting to agree upon :
> > > > That file also allows to deal with the case of having multiple versions (that have
> > > > their own branches) of the same package, by adding :
> > > > upstream-branch = <upstream branch name>
> > > > debian-branch = <debian branch name>
> > > >
> > > > Since there is no consensus about that, let me propose something already used
> > > > in some packages (i mean not only the ones i'm dealing with).
> > > > To manage stable, unstable, experimental changes on versions of the same package,
> > > > let's name them :
> > > > master, upstream : for current work, unstable/testing
> > > > master-experimental, upstream-experimental : work-in-progress
> > > > master-stable, upstream-stable : for security updates
> > > >
> > > > then put debian/gbp.conf each master* branch, so that git-buildpackage, git-import-orig
> > > > on those will not wreak havoc.
> > > > It is obvious most packages won't need this, but when they do it's useful to have a
> > > > common layout.
> > > >
> > > > Note : there is only one pristine-tar branch, in any case.
> > >
> > > I think that makes a lot o sense, and it would be nice to have some docs
> > > on the wiki about how to manage packages in the team's repositories with
> > > all these dos and don'ts, like we had in the past for the subversion
> > > repos. There's a starting point already in the RubyInWheezy in wiki
> > > page:
> > >
> > > http://wiki.debian.org/Teams/Ruby/RubyInWheezy#Using_Git
> > >
> > > Volunteers?
> >
> > So I just clicked that link, having never maintained packags in git
> > before, nor having ever used mr. It failed quite handily for me:
> >
> > clint@clint-MacBookPro:~/pkg/pkg-ruby-extras/pkg-ruby-extras$ mr checkout
> > mr checkout: no repositories found to work on
> >
> > I tried running ./make-mrconfig .. which did do some SSH operations and
> > filled up .mrconfig. But still, mr checkout does not pull down anything.
> >
> > Before I dive into mr's inner workings, maybe somebody else has a clue?
> >
> > I've attached the .mrconfig...
>
> Which version of mr are you using? By any chance, is it ancient?
Heh.. possibly.. 0.51 .. the version in Ubuntu 11.04. 1.03 does seem to work
correctly.
I added a note to the wiki page that versions prior to 1.03 may have problems.
Reply to: