From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 31 May 2009 00:31:05 +0400 From: "Alexey I. Froloff" To: ALT Devel discussion list Message-ID: <20090530203105.GB29599@altlinux.org> References: <1243710538.16625.20.camel@latitude> <20090530195538.GA29599@altlinux.org> <1243714317.16625.44.camel@latitude> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline In-Reply-To: <1243714317.16625.44.camel@latitude> User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: [devel] =?koi8-r?b?7cXe1Nkgz8Ig3MvT0MHO08nJ?= X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux Team development discussions List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2009 20:31:10 -0000 Archived-At: List-Archive: List-Post: --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 31, 2009 at 12:11:57AM +0400, Alexey Rusakov wrote: > =E4=C1, =DA=C1=C2=D2=CF=D3=D8, =C9=CE=D4=C5=D2=C5=D3=CE=CF. 00:42 -!- arekm (i=3Darekm@pld-linux/arekm) has joined #altlinux 00:42 hello, I have few question about your cvs->git conversion. An= yone with the knowledge alive? 00:59 arekm: best way to convert cvs to git is to use parsecvs 00:59 arekm: but you need access to raw cvsroot 01:00 this is possible with sf.net or savannah, they allow anon rsy= nc access 01:01 raorn: I'm not interested in strict conversion process, more = about altlinux layout, commit scripts, automatization and such 01:01 arekm: there's special package called gear 01:02 where? http://git.altlinux.org/archive/g/gear don't see it he= re 01:02 arekm: there was no cvs->git conversion except for kernel 01:02 Lost: didn't altlinux use cvs for specs/sources? 01:02 arekm: people/ldv/packages/gear.git 01:02 no 01:02 only for kernel 01:02 no cvs, only git 01:03 uh, so what was used? 01:03 nothing ;-) 01:03 ups 8) 01:03 each maintainer had own version 01:03 one repo - one package 01:04 svn/cvs/darcs etc :) 01:04 well, not exactly one 01:04 =D7=D3=C5=CD =D3=D0=CF=CB=CF=CA=CE=CF=CA =CE=CF=DE=C9! 01:04 there were no official VCS for specs before 01:06 all mintainers now have his own repo for each package. we pul= l changes from other maintainers 01:11 gear just prepares all tarballs, patches and spec and then it= just passes it to rpmbuild or hasher 01:21 arekm: so, you want to migrate to git? ;-) 01:21 * raorn .oO( =DD=C1=D3 ldv =CE=C1=DE=CE=D5=D4 =C2=C1=C7=D2=C5=D0=CF= =D2=D4=D9 =C9=DA =D0=CC=C4 =D3=CC=C1=D4=D8 ;-))) ) 01:21 raorn: considering it but spliting flat cvs into git tree loo= ks like nightmare 01:23 arekm: i don't think it's possible. but you can take one xxx.= spec,v and convert it to git, then take next, then next, and finally you wi= ll kill yourself ;-) 01:23 arekm: git-cvsimport? 01:23 wart: ONLY parsecvs 01:24 Or you don't have a strict CVSROOT<->git repo correspondence? 01:24 raorn: Or parsecvs. They're both crappy, in fact. 01:24 cvsimport sucks cock 01:24 wart: the problem is not with the cvs->git conversion. The pr= oblem is with making flat->tree conversion 01:24 arekm: take one file from repo and feed it to parsecvs 01:25 arekm: Could you elaborate? 01:25 arekm: or you can use gear-srpmimport 01:25 On flat->tree. I didn't quite get it. 01:25 if you can export all versions of a package 01:25 wart: see http://cvs.pld-linux.org/SPECS/ and http://cvs.pld-= linux.org/SOURCES/ - flat for all packages 01:26 arekm: in gear terms, package is not just spec, but sources a= nd packages in one git tree 01:26 so you don't really (easily) know which file belongs to which= package 01:26 so the problem is in separating the sources of different packa= ges into different trees? 01:26 *patches 01:26 wRAR: yes (on all branches/tags) 01:26 arekm: Well, you could create a whole bunch of srpms and impor= t them with gear. 01:26 Of course, you'll loose history then. 01:27 this is what i told before 01:27 wart: and i want/need history 01:27 what "history"? 01:27 of specs/sources 01:27 raorn: CVS history. For specs. 01:27 history of package changes or history of spec editions? 01:27 CVS history. 01:27 why? 01:27 If it's not the same as package log, it's trashed. 01:28 who need this? 01:28 needs what? 01:28 Why do you need git/cvs, then? 01:28 editing history? 01:28 cvs history 01:28 editing history? 01:28 or any history? 01:28 not "who". why? 01:28 Because that's what version control is all about. 01:29 what is "version"? 01:29 bb all 01:29 raorn: cvs commit. 01:29 cvs commit is just transport 01:29 raorn: We're talking about version control now. 01:30 what "version" you want to control and why? 01:30 raorn: =EB=CF=CE=DE=C1=CA =D4=D5=D0=C9=D4=D8. 01:30 =D4=D9 =D4=D5=D0=C9=DB=D8 01:30 =FC=D4=CF =D4=D9 =D4=D5=D0=C9=DB=D8. 01:30 =F5 =DE=C5=CC=CF=D7=C5=CB=C1 cvs history. 01:30 =D3=D0=C5=CB=CF=D7 01:30 =E9 =CF=CE =CE=C5 =C8=CF=DE=C5=D4 =C5=A3 =D0=CF=D4=C5=D2=D1=D4= =D8. 01:30 raorn: =C7=C4=C5 =D4=D9 =D0=D2=C5=C4=CC=C1=C7=C1=C5=DB=D8 =C9= =D3=D4=CF=D2=C9=C0 =D3=D0=C5=CB=C1 =D7=DA=D1=D4=D8 =C5=DD=A3? 01:31 =C9=CC=C9 =D0=D2=C5=C4=CC=C1=C7=C1=C5=DB=D8 =DA=C1=C2=C9=D4=D8? 01:31 arekm: I think that it won't be hard to modify gear to support= your scheme. 01:32 arekm: As an import source. 01:32 btw. /me wonders if there are realtime translations for irssi= (using google translate for example) 01:32 wart: will check 01:32 s/translations/translators/ 01:32 does it matter, were there 10 changes in spec or just 1 chang= e between two subsequent versions of a package? 01:32 Hell yes it does. 01:32 it does 01:33 oh 01:33 =C2=CC=C9=CE 01:33 why? 01:33 raorn: =C1 =C7=C4=C5 =D4=D9 =C5=DD=A3 =D7=CF=DA=D8=CD=A3=DB=D8= "change between two subsequent versions of a package"? 01:33 so you know who broke things in middle for example 01:33 wRAR: =D0=CF =D4=C5=C7=D5, =C5=D3=CC=C9 =CF=CE=C9 =C5=D3=D4=D8 01:33 =F4=DC=C7=D5 =C7=C4=C5? 01:33 =C1 01:33 =D4=C5=C7=D5 =D7 =C3=D7=D3=C5 01:33 =D7 cvs, =C2=CC=C9=CE 01:33 =C1 =D2=C1=DA=CE=C9=C3=C1? 01:34 =D2=C5=CC=C9=DA =D0=C1=CB=C5=D4=C1 =D4=C5=D6=C9=D4=D3=D1 01:34 =F4=D9 =D6=C5 =D0=D2=C5=C4=CC=C1=C7=C1=C5=DB=D8 =D7=D9=CB=C9= =CE=D5=D4=D8 cvs. 01:34 =F7=CD=C5=D3=D4=C5 =D3 =D4=DC=C7=C1=CD=C9. 01:34 =E4=C1 =C9 =C9=CE=C4=C9=D7=C9=C4=D5=C1=CC=D8=CE=D9=C5 =C9=DA= =CD=C5=CE=C5=CE=C9=D1 =DA=CE=C1=D4=D8 =CE=C1=C4=CF. 01:34 =C9=CD=C5=CE=CE=CF. =DC=D4=CF =CE=C1=DA=D9=D7=C1=C5=D4=D3=D1 = "=CD=C9=C7=D2=C1=C3=C9=D1 =D3 =DE=C1=D3=D4=C9=DE=CE=D9=CD =D3=CF=C8=D2=C1= =CE=C5=CE=C9=C5=CD =C9=D3=D4=CF=D2=C9=C9" 01:35 =EF=CE =C9 =D3=D0=D2=C1=DB=C9=D7=C1=C5=D4 -- =CB=C1=CB =C5=A3 = =D3=CF=C8=D2=C1=CE=C9=D4=D8. =E1 =CE=C1=C4=C5=CC=C1=D7 srpm'=CF=D7 =CE=C5 = =C2=D5=C4=C5=D4 =CE=C9=DE=C5=C7=CF. 01:35 arekm: what do you wand to do? completly migrate from cvs to = git? or something else? 01:37 raorn: completly migrate. I was thinking that altlinux used c= vs before but well, I was wrong 01:37 ALTLinux doesn't use git even know. 01:38 now 01:38 we don't build packages directly from git on build server 01:38 ehm, so what's the purpose of git.altlinux.org? 01:39 git hosting 01:39 arekm: well, in this case you can sacrifice detailed history.= those packages already released. simpliest way is to import all srpms with= gear-srpmimport 01:39 and what about /archives/ on it? 01:39 old package history 01:40 all packages imported in git from srpms 01:40 so it's just for hosting history of released packages, am I c= orrect? 01:40 arekm: There will be The Day, when packages will be built from= git. But nobody knows when. 01:40 Unreleased also. 01:40 ldv is working on that 01:40 Something like alioth for Debian, if you know. 01:41 git hosting so that people could collaborate 01:42 arekm: for me, it's easier to track upstream VCS in separate = branch and keep all changes as commits, not patch files 01:42 in this case i don't use package/spec history 01:48 arekm: in alt linux you don't have to use git if you want to = build packages. and /archive/ is just holding history for those who want to= keep it when they start using git =F0=CF =D0=CF=D3=CC=C5=C4=CE=C9=CD =C4=C1=CE=CE=D9=CD =CF=CE=C9 =D4=C1=CB = =C5=DD=A3 =C9 =CE=C5 =CF=D0=D2=C5=C4=C5=CC=C9=CC=C9=D3=D8 =D3 =D0=C5=D2=C5= =C5=DA=C4=CF=CD, =CE=CF =CF=D4 =D3=D7=CF=C5=CA =D0=CC=CF=D3=CB=CF=CA =D3=D4=D2=D5=CB=D4=D5=D2=D9 = =D5=D6=C5 =D3=CF=C2=C9=D2=C1=C0=D4=D3=D1 =D5=C8=CF=C4=C9=D4=D8. --=20 Regards, Sir Raorn. --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkohl4kACgkQVqT7+fkT8wqFpwCdEJx40HlkgyzImAAbYf8RipED pzQAnRTjV1qEg1l33ROa5Fs1X570AXj7 =g0dz -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc--