Re: Git migration: next step
Dnia 3 Kwietnia 2012, 6:34 pm, Wt, Kacper Kornet napisał(a): I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your favourite package would like after migration please see: git://carme.pld-linux.org/packages/pkg Also some documentation has been written: http://www.pld-linux.org/dokuwiki/pld-gitolite http://www.pld-linux.org/dokuwiki/howto-git Can we agree a naming convention? Something like: package-name: description (it's similar to kernel patches) i.e. xorg-driver-input-wacom: up to 14.0.0 or xorg-driver-input-wacom: fix invalid BuildReq? Are we going to use git tag to mark a new version of the software or version of the spec or both? Is Signed-off-by required in patches? [..] A. Should PLD move to git with the similar setup? Yes [..] C. When should the migration take place? ASAP [..] 6. Setup mailing list for git commits I think there is no need for a separate list. -- Regards, Przemo Firszt ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: next step
On Thu, Apr 05, 2012 at 09:00:34AM +0100, Przemo Firszt wrote: Are we going to use git tag to mark a new version of the software or version of the spec or both? JFYI, ALT Linux uses both -- with tags being convenient to prepare the tarball for the build system. See also gear* and girar* if anyone's interested (the discussions and wiki are mostly in Russian but there are English manpages too). -- WBR, Michael Shigorin m...@altlinux.ru -- Linux.Kiev http://www.linux.kiev.ua/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: next step
On Thu, Apr 05, 2012 at 09:00:34AM +0100, Przemo Firszt wrote: Dnia 3 Kwietnia 2012, 6:34 pm, Wt, Kacper Kornet napisał(a): I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your favourite package would like after migration please see: git://carme.pld-linux.org/packages/pkg Also some documentation has been written: http://www.pld-linux.org/dokuwiki/pld-gitolite http://www.pld-linux.org/dokuwiki/howto-git Can we agree a naming convention? Something like: package-name: description (it's similar to kernel patches) i.e. xorg-driver-input-wacom: up to 14.0.0 or xorg-driver-input-wacom: fix invalid BuildReq? I don't find package-name: prefix useful, as there (AFAIK) will be one package per repository. Are we going to use git tag to mark a new version of the software or version of the spec or both? NVR tags should be done automatically like in CVS. Is Signed-off-by required in patches? No sense IMO if committer is the author. [..] 6. Setup mailing list for git commits I think there is no need for a separate list. Agreed, single [cvs-]commit list should suffice. -- Jakub Boguszhttp://qboosh.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: next step
On Tue, Apr 03, 2012 at 08:04:27PM +0200, Arkadiusz Miśkiewicz wrote: On Tuesday 03 of April 2012, Kacper Kornet wrote: Is cvsadmin job for git described anywhere? http://sitaramc.github.com/gitolite/admin.html But I will prepare small description on our wiki. How I (as user) can change my ssh key? In the current setup no. You have to send your public key to the admin. But it is possible to enable ordinary users to change their keys. admin defined command - 404 Fixed. http://www.pld-linux.org/dokuwiki/howto-git Are auto- tags restricted for pld-builders only? (should be). Yes, only builder of the given PLD flavour can write them. None (even builders) can remove or rewrite them. How workflow with DEVEL or APACHE_2_2 and such branches should look like? (aka are there any things different from cvs) If you use builder script everything should be the same. The difference is that in git branches and tags are in separate name spaces so it is possible to have concurrently a branch DEVEL, and a tag DEVEL pointing to different commits. B. Is there anything more that should be done before D day? We have few scripts in CVSROOT (restricting access, cia bot notification, commit log notification, cdg, namecheck, filter tags,...). Are these scripts ported to git version of repository? ciabot - implemented cdg - for now I would leave it in CVS sending notifications to distfiles and pld-cvs - implemented filter_tas.sh - seems to be not used currently Assuming that the migration to git would take place it could go according to the following plan: 2. Push converted repositories from gitolite setup on carme to git.pld-linux.org I would go for converting from current cvs from scratch (especially things are modified on cvs server side sometimes). It is taken into account. The conversion is based on *,v file rsynced from cvs.pld-linux.org How long such conversion takes? My estimate is about 12-18h on carme. 3. Setup git-daemon and gitweb access gitweb == or != cgit nowdays? Yes. Gitweb is a perl code developed together with git. Cgit is written in C and developed separately. -- Kacper Kornet ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: next step
On Tue, Apr 03, 2012 at 08:32:43PM +0200, Paweł Sikora wrote: On Tuesday 03 of April 2012 19:34:10 Kacper Kornet wrote: So there are following questions: B. Is there anything more that should be done before D day? do we need an extra 'Changed files:' section in git changelog? It is only in commits that are result of ocnversion from CVS. I was asked to add the information on which CVS revisions the git commit is based. -- Kacper Kornet ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: next step
On 05/04/12 18:01, Jakub Bogusz wrote: Are we going to use git tag to mark a new version of the software or version of the spec or both? NVR tags should be done automatically like in CVS. i would expect here a bit change with the tag transforming as . was illegal in cvs, but valid in git, i would not do the transformation if possible, and thus git autotags would be auto-dist-N-V-R, i.e: auto-th-rpm-4.5-65 how it is done now and how was planned? -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: ftp move is comming
On Monday 26 of March 2012, Arkadiusz Miśkiewicz wrote: ftp move is comming soon It happened. Current TODO list: http://ep09.pld-linux.org/~pldth/main.txt http://ep09.pld-linux.org/~pldth/main-i686.txt http://ep09.pld-linux.org/~pldth/main-i486.txt -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
