[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [ImportingCVSRepository] (edit) Modern instructions
From: |
Beuc |
Subject: |
[Savannah-cvs] [ImportingCVSRepository] (edit) Modern instructions |
Date: |
Mon, 04 Feb 2008 23:47:47 +0000 |
++added:
Nowadays, it's essentially::
vserver vcs-noshell enter
cd
infra/cvs/cvs_import.sh tarball_url project_name
# OR for a web repository ('web' is litteral here):
infra/cvs/cvs_import.sh tarball_url project_name web
cvs_import.sh is specific to Savannah, is not perfectly foolproof, and is not
necessarily updated when directories are renamed as the system evolves. Reading
it before using it sounds like a good plan.
-----
History
-------
For reference, here's how we manually imported CVS tarballs before
cvs_import.sh (and before vserver).
++added:
-----
--removed:
-
-From karl Sun Nov 5 19:42:57 +0000 2006
-From: karl
-Date: Sun, 05 Nov 2006 19:42:57 +0000
-Subject: out of date?
-Message-ID: <address@hidden://savannah.gnu.org/maintenance>
-
-1) on sv.gnu.org, /etc/group does not contain any projects. Where are gid's
recorded?
-
-2) as user svadmin, i presumably cannot chown to root. does it all have to be
done as root?
-
-3) /subsystems/cvs/root/cvs_import.sh does not exist (on sv.gnu.org).
-
-help?
-
--karl
-
-
-
-[8 more lines...]
--
forwarded from
https://savannah.gnu.org/maintenance/address@hidden://savannah.gnu.org/maintenance
- [Savannah-cvs] [ImportingCVSRepository] (edit) Modern instructions,
Beuc <=