Re: [Pkg-octave-devel] Migrate the SVN repos to Git
On Tue, May 05, 2009 at 09:48:31AM +0200, Rafael Laboissiere wrote:
> * Rafael Laboissiere <rafael@debian.org> [2009-05-04 22:29]:
>
> > I started already but not with a package. The web site sources are now
> > under Git control:
> >
> > http://git.debian.org/?p=pkg-octave/www.git
>
> I migrated octave-epstk as a test case:
>
> http://git.debian.org/?p=pkg-octave/octave-epstk.git
>
> Everything seems to work fine. I also removed the obsolete SVN
> repository for octave-epstk.
>
> I will eventually update the DOG Guidelines to reflect the use of Git. At
> some point I should look at git-buildpackage (I do not know about it yet).
> A possible workflow for using the Git repositories is like this:
>
> $ PKG=src-package-name
> $ VER=some-version
> $ apt-get source $PKG
> $ cd $PKG-$VER
> $ rm -rf debian
> # The following is equivalent to svn checkout
> $ git clone ssh://git.debian.org/git/pkg-octave/$PKG.git .
> # Edit debian/* files
> $ debuild -i
> $ dupload
> $ git commit -a -m "Debian release ${PKG}_$VER-1"
> $ git push # equivalent to svn commit
I just tried to follow this and I no longer have access to the repo
through ssh, just normal git, does the alioth password not work for
this?
Also, when I try this with git clone
git://git.debian.org/git/pkg-octave/$PKG.git . instead of
ssh://git.debian.... then if I do this straight after removing the
debian dir I get a "fatal: destination path '.' already exists and is
not an empty directory." and if I skip the . in the end I get a new
directory called $PKG and beneath that a debian directory with all the
debian files, so I don't have a normal dir structure, but rather a
$PKG/$PKG/debian with the upstream in the first $PKG directory (hope
you understood that).
Does the ssh update behave differently?
Cheers
Oli
Reply to: