10-30-2009
you should try do : yum install cvs
You could use yum search also
yum search cvs.
And finally consider to move to subversion
10 More Discussions You Might Find Interesting
1. Linux
Guys does anyone have a good plan or structured tutorial on how to install Psybnc on CentOS platform, ive gave it a try and im on my 4th hour now , i just cant seem to get it working.
Thanks in advance (0 Replies)
Discussion started by: wmccull
0 Replies
2. Solaris
Hi all,
I am tring to install CVS on my solaris machine.
so, I got a package cvs-1.11.22-sol10-x86-local from internet, and did this
"pkgadd -d cvs-1.11.22-sol10-x86-local"
and the output I got is
The following packages are available:
1 SMCcvs cvs
(x86)... (2 Replies)
Discussion started by: eamani_sun
2 Replies
3. Red Hat
Hi,
I am trying to install phyton on my centos.
When I write:
yum install phyton
I get the message that it doesn't find the package.
How should I fix it? (4 Replies)
Discussion started by: programAngel
4 Replies
4. Virtualization and Cloud Computing
Hi,
I have installed VirtualBox, downloaded CentOS 5.5 and created a VirtualMachine where i have installed the 'server' versión of CentOS 5.5
As I installed Virtual Box a new network device appeared '192.16.1.250' in my 'real' machine. I was unable to reach my webserver so i istalled CentOS once... (5 Replies)
Discussion started by: motoko
5 Replies
5. UNIX and Linux Applications
Hi every body
I am facing problem installing spamassassin on my CentOS - Direct Admin VPS
The installation ended with the following error
REQUIRED module out of date: Archive::Tar
optional module missing: Digest::SHA
optional module missing: Mail::SPF
optional module missing: IP::Country... (0 Replies)
Discussion started by: rizwan65
0 Replies
6. Linux
I am not able to find any references related to installing centOS in i686 machine ?
Is it supported or not ?
This does not list it at all, so a little bit confused CentOS - Wikipedia, the free encyclopedia
No luck with google also ! Appreciate if somebody can help. Thanks. (1 Reply)
Discussion started by: thegeek
1 Replies
7. Red Hat
Hello folks,
I am trying to install Xen on centos 6!
Kindly check out the following screen shots!
What should I do?
Regards (0 Replies)
Discussion started by: ahmedamer12
0 Replies
8. UNIX for Dummies Questions & Answers
I'm kinda new to Linux, I'm mostly run websites, and it's rather easy to do everything... except install this PECL LUA plugin. :wall:
I start by running this command: pecl install lua-0.9.4
downloading lua-0.9.4.tgz ...
Starting to download lua-0.9.4.tgz (12,617 bytes)
.....done: 12,617... (0 Replies)
Discussion started by: blackstar
0 Replies
9. Red Hat
hi,
i am try to install a package in centos 6.2 x86-64 but unable to find any package in centos media iso.
In RHEL we have a product folder which contain all the list of rpm but in centos i cant found that.
I have use yum command but it also cant work show me the message no module named yum.... (1 Reply)
Discussion started by: zeeshan047
1 Replies
10. Red Hat
I have added grub2 efi package to package folder in extracted iso folder and used below command to create repo
createrepo -v PackagesFolder
I didn't do any changes in comps.xml as an entry with grub2efi is already present in packages required.
Am getting following error.
File... (1 Reply)
Discussion started by: Sumanthsv
1 Replies
LEARN ABOUT DEBIAN
git-cvsexportcommit
GIT-CVSEXPORTCOMMIT(1) Git Manual GIT-CVSEXPORTCOMMIT(1)
NAME
git-cvsexportcommit - Export a single commit to a CVS checkout
SYNOPSIS
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot]
[-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
DESCRIPTION
Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository.
Specify the name of a CVS checkout using the -w switch or execute it from the root of the CVS working copy. In the latter case GIT_DIR must
be defined. See examples below.
It does its best to do the safe thing, it will check that the files are unchanged and up to date in the CVS checkout, and it will not
autocommit by default.
Supports file additions, removals, and commits that affect binary files.
If the commit is a merge commit, you must tell git cvsexportcommit what parent the changeset should be done against.
OPTIONS
-c
Commit automatically if the patch applied cleanly. It will not commit if any hunks fail to apply or there were other problems.
-p
Be pedantic (paranoid) when applying patches. Invokes patch with --fuzz=0
-a
Add authorship information. Adds Author line, and Committer (if different from Author) to the message.
-d
Set an alternative CVSROOT to use. This corresponds to the CVS -d parameter. Usually users will not want to set this, except if using
CVS in an asymmetric fashion.
-f
Force the merge even if the files are not up to date.
-P
Force the parent commit, even if it is not a direct parent.
-m
Prepend the commit message with the provided prefix. Useful for patch series and the like.
-u
Update affected files from CVS repository before attempting export.
-k
Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ becomes $Revision$) in working CVS checkout before applying patch.
-w
Specify the location of the CVS checkout to use for the export. This option does not require GIT_DIR to be set before execution if the
current directory is within a git repository. The default is the value of cvsexportcommit.cvsdir.
-W
Tell cvsexportcommit that the current working directory is not only a Git checkout, but also the CVS checkout. Therefore, Git will
reset the working directory to the parent commit before proceeding.
-v
Verbose.
CONFIGURATION
cvsexportcommit.cvsdir
The default location of the CVS checkout to use for the export.
EXAMPLES
Merge one patch into CVS
$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git cvsexportcommit -v <commit-sha1>
$ cvs commit -F .msg <files>
Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo
$ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1>
Merge pending patches into CVS automatically -- only if you really know what you are doing
$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-CVSEXPORTCOMMIT(1)