1 registered user
in last 24 hours
]project-open[ Source Code Access via CVS
This page describes how to access the ]project-open[ source code repository and how to update your ]project-open[ installations manually.
The ]project-open[ source code is maintained using a CVS version control system. The current CVS repository is located at:
- Server: cvs.project-open.net
The server names "berlin.dnaslias.com" and "berlin.project-open.net" are deprecated and may soon disappear.
- Directory: /home/cvsroot
- Username/password: anonymous/ (user anonymous with empty password)
A sample CVS command for an update operation is:
cvs -d :pserver:email@example.com:/home/cvsroot update
Installing CVS on Linux and Windows
CVS (http://www.nongnu.org/cvs/) is the version control system used to keep the ]project-open[ product code. You need to install a CVS client on your computer in order to access the ]project-open[ cvs server:
CVS is available with all major Linux distributions. Please enter "cvs" in a Linux terminal to check whether CVS is already installed.
To install CVS you can enter "yum install cvs" (CentOS and Red Hat Linux) or "apt-get install cvs" (Debian and Ubuntu).
We recommend the Tortoise CVS (http://www.tortoisecvs.org/) as CVS client. It is proven and free.
Source Code and CVS Control
The source code of your ]project-open[ installation is located at:
Below the /packages/ folder you should find some 200 folders which correspond to ]project-open[ list of packages.
In order to work with CVS, your source code needs to include "CVS" folders in every package. Depending on your installer, these "CVS" folder may be available or not.
To check for CVS folders, please go to any package (for example: /packages/acs-admin/) folder and list the available sub-directories. You should see something like this:
Please check if the "CVS" folder is present in your installation.
Downloading the latest released ]project-open[ code
The ]po[ from time to time releases "Upgrade Installers" on www.SourceForge.net.
Pleas go to http://www.sourceforge.net/projects/project-open/files/ and download the upgrade installer "project-open-Update-X.Y.Z.V.W.tgz" of the latest version.
Please move your /packages/ somewhere and unpack the project-open-Update-X.Y.Z.V.W.tgz file:
# cd /web/projop/
# tar xzf project-open-Update-X.Y.Z.V,W.tgz
You can use 7-Zip (http://www.7-zip.org/) to unpack the ".tgz" file.
(There will be a warning during the extraction process, which you can ignore.)
Retrieving the /packages/ folder via CVS
You can also retrieve the /packages/ folder directly via CVS (Linux):
# su - projop
# cd /web/projop/
# mv packages packages.old
# mkdir packages
# export CVSROOT=:pserver:firstname.lastname@example.org:/home/cvsroot
# cvs checkout intranet-core
# cp intranet-core/all-checkout.sh .
# bash all-checkout.sh
On Windows you can perform the same steps using the CygWin command line.
Updating to the Latest Version ("HEAD")
Please see the section above ("Retrieving the /packages/ folders via CVS") for getting the latest version of the source code.
You can also issue the following command in Linux:
# su - projop
# cd /web/projop/packages/
# cvs update -PdA
You will also have to upgrade your system after an update of your source code in the /packages/ folder.
]project-open[ Versions Overview
Please see the list of versions for details about released versions.
The "HEAD" version of ]project-open[ is in general relatively stable, and several users have reported to upgrade their system regularly to HEAD.
However, generally users should stay with stable versions released on SourceForge either as installers or as "Upgrades".
CVS Packages on the ]po[ CVS Server
The ]project-open[ product consists of some 200 packages which include both free and commercial packages (please see licenses and www.project-open.com -> Shop for details). Also, some of the packages are:
- unstable or
- not yet prepared for a general audience,
so they are not included in the normal product releases. Please treat these packages carefully and never try them on a production server. Please use a development server instead.
Troubleshooting CVS Issues
In case cvs updates do not perform as expected please check the following:
1) Check availability of CVS server:
In case responses do time out please check your DNS server entries in /etc/resolv.conf
2) Check /etc/hosts
Some older ]po[ VM's have an entry to a local IP for cvs.project-open.net Please delete this entry.
3) Check if you can connect to the cvs server:
su - projop
usually results in
Logging in to :pserver:email@example.com:2401/home/cvsroot
This prompt is send from the local cvs tool. Just hit ENTER for 'no password' and you should be able to execute cvs commands. Check this by doing the following:
cvs status intranet-core.info
The result should be something like:
File: intranet-core.info Status: Needs Patch
Working revision: 1.104
Repository revision: 1.108 /home/cvsroot/intranet-core/intranet-core.info,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
4) CVS server busy?
In case everything worked fine, a cvs update might time out due to to maxim number of allowed to connections. Please try to run the update at a later point in time again.
Access and Permissions
Most of the packages above are accessible for the CVS user "anonymous" with an empty password.
However, access to some packages (the ones listed as closed-source in www.project-open.com -> Shop) is restricted to privileged users. Please contact us if you are interested in some of these packages: