ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Alexey Tourbin <at@altlinux.ru>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: [devel] U: git-svn broken (+ solution)
Date: Wed, 13 Sep 2006 01:51:46 +0400
Message-ID: <20060912215146.GM17693@localhost.localdomain> (raw)
In-Reply-To: <20060912152730.GI17693@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

On Tue, Sep 12, 2006 at 07:27:30PM +0400, Alexey Tourbin wrote:
> > После чего master будет отбранчен от refs/remotes/git-svn.
> > 
> > Дальше git-svn fetch && git pull . refs/remotes/git-svn
> 
> Я уже разобрался, но всё равно спасибо.
> git-svn fetch работает очень долго.

Хуже того, git-svn теряет отдельные изменения!
ЭТО ВООБЩЕ...

Если же экспортировать GIT_SVN_NO_LIB=1, то git-svn работает гораздо
быстрее; кроме того, потерянных изменений в таком случае с ходу не
обнаруживается.

Мораль: GIT_SVN_NO_LIB=1 git-svn fetch http://...
и ТОЛЬКО так.

Проблема, по-видимому, в том, что перловые привязки глючные.
Тестирует их кто-нибудь или нет одному демиургу известно.

$ grep -A9 -ni wonderful /usr/bin/git-svn
2998:   # Wonderfully consistent library, eh?
2999-   # 160013 - svn:// and file://
3000-   # 175002 - http(s)://
3001-   #   More codes may be discovered later...
3002-   if ($errno == 175002 || $errno == 160013) {
3003-           return;
3004-   }
3005-   croak "Error from SVN, ($errno): ", $err->expanded_message,"\n";
3006-};
3007-
$

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2006-09-12 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 12:12 [devel] git-svn Alexey Tourbin
2006-09-12 15:17 ` Alexey I. Froloff
2006-09-12 15:27   ` Alexey Tourbin
2006-09-12 15:32     ` Pavlov Konstantin
2006-09-12 17:31       ` Alexey I. Froloff
2006-09-12 21:51     ` Alexey Tourbin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060912215146.GM17693@localhost.localdomain \
    --to=at@altlinux.ru \
    --cc=devel@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git