This page maintains the FOSSology Project release notes, from the most recent release to the oldest release.
Date: 11 November 2008
Date: 2 July 2008
Please refer to the README file contained in the fossology download for first time installation instructions.
If you are updating a previous fossology installation, please follow the update process below.
If the fossology scheduler is running, stop it with:
sudo /etc/init.d/fossology stop
Uncompress the fossology-0.9.0.tar.gz file into a build directory and build.
tar -xzvf fossology-0.9.0.tar.gz cd fossology-0.9.0 make make install sudo ./install.sh -f
After successfully installing 0.9.0, you will need to generate a new scheduler.conf file using
/usr/local/fossology/agents/mkconfig
Invoke mkconfig with the -? option to see which options you should specify for your environment.
Restart the fossology scheduler with:
sudo /etc/init.d/fossology start
Open a browser & browse to the fossology repository:
http:<fossology host>/repo/
Login to fossology as user fossy.
Move your mouse over the “Admin” tab and click on “Initialize”.
After initialization is complete, select Organize→License→Default Terms
Next, select Admin→Database→Check Templates
Know Problem with “Help → About”
Problem: “Help → About” does not return any version/code revision.
Description: see above
Solution: make tar is not putting the version in the pathinclude.h.php.
This issue will be addressed in the next release.
Date: 28 May 2008
Please refer to the README file contained in the fossology download for first time installation instructions.
If you are updating a previous fossology installation, please follow the update process below.
If the fossology scheduler is running, stop it with:
sudo /etc/init.d/fossology stop
Uncompress the fossology-0.8.0.tar.gz file into a build directory and build.
tar -xzvf fossology-0.8.0.tar.gz cd fossology-0.8.0 make make install sudo ./install.sh -f
Restart the fossology scheduler with:
sudo /etc/init.d/fossology start
Know Problem with attempting to Reset or Delete jobs WHILE they are running.
Problem: Attempts to Reset or Delete a job while the job is running will fail.
Description: Job will be marked as failed, it will continue to run and all jobs dependent on it will run.
Solution: Do not attempt to Reset or Delete running jobs.
In the next release, the Reset | Delete micromenus will not be displayed for running jobs.
Known Problems with cp2foss at 0.8.0 release
Problem: cp2foss can’t find fossjobs
Description: cp2foss expects to find a program called fossjobs in /usr/local/bin. fossjobs gets installed as fossjobs.php in /usr/local/bin due to a makefile issue.
Solution: as root create a symlink in /usr/local/bin called fossjobs and link it to fossjobs.php.
This problem should be fixed in 0.8.1.
Problem: cp2foss will create duplicate upload folders.
Description: cp2foss does not correctly detect when a file has been uploaded into a upload folder. As a result it will create duplicate upload folders with the same name. This situation only occurs when the same upload folder is used in the same folder path. For example if foo.c is uploaded into upload folder foo.c and that is loaded into folder path /bar/baz/ and then reloaded again in to /bar/baz there will be two upload folders, both called foo.c.
Solution: Don’t do multiple uploads into the same upload folder/folder path. If this situation does occur. The Organize→Uploads→Delete Uploaded File menu option should be used to remove the duplicate(s).
This problem is scheduled to be fixed in the 0.8.1 release.
Date: 30 April 2008
Please refer to the README file contained in the fossology download for first time installation instructions.
If you are updating a previous fossology installation, please follow the update process below.
If the fossology scheduler is running, stop it with:
sudo /etc/init.d/fossology stop
Remove the scheduler.conf file (you may want to save a copy if you have customized it):
rm -rf /usr/local/share/fossology/agents/scheduler.conf
Uncompress the fossology-0.7.0.tar.gz file into a build directory and build.
tar -xzvf fossology-0.7.0.tar.gz cd fossology-0.7.0 make make install sudo ./install.sh -f
If you saved a copy of your customized scheduler.conf file, add your customizations into the newly created scheduler.conf file.
Restart the fossology scheduler with:
sudo /etc/init.d/fossology start
Date: 13 February 2008
Please refer to the README file contained in the fossology download for first time installation instructions.
If you are updating a 0.6.0 fossology installation, please follow the update process below.
Also see Known Issues section below.
If the fossology scheduler is running, stop it with:
sudo /etc/init.d/fossology stop
Remove 0.6.0 license information used to create the bsam cache file:
rm -rf /usr/local/share/fossology/agents/licenses/*
Uncompress the fossology-0.6.1.tar.gz file into a build directory and build.
tar -xzvf fossology-0.6.1.tar.gz cd fossology-0.6.1 make make install sudo ./install.sh -f
Restart the fossology scheduler with:
sudo /etc/init.d/fossology start
Date: 18 December 2007 The initial public release of FOSSology.
Please refer to the README file contained in the fossology download for first time installation instructions.
If you are updating a fossology installation created with pre-release bits, please follow the update process below.
A freshly installed system cannot create a new folder in the UI on the first try. The second and subsequent attempts succeed.
The unpack agent extracts files from containers. A container is any kind of file that stores other files. unpack uses utilities, such as, tar, gzip, ar, rpm, zcat, etc. to perform the extraction. In cases where the container is corrupt or otherwise ill-formed, the utilities may fail to successfully extract. The unpack agent will report this as a warning and skip to the next container. The warnings can be safely ignored. An example of a failed extraction and subsequent unpack warning is:
WARNING pfile 1153340 Minor zip error... ignoring error. LOG pfile 1153340 Minor zip error(2)... ignoring error. WARNING pfile 1153340 Command bzcat failed LOG pfile 1153340 WARNING Command bzcat failed: /srv/fossology/repository//ununpack/0/916132eba75e9fcb069c7b6327f60b3b318ceef0. \ 6ab7c5ecb2f03728c63644e4250bde34.656852992.dir/SRPMS/iscsi-initiator-utils- \ 6.2.0.742-0.5.el5.src.rpm.unpacked.dir/iscsi-initiator-utils-drop-bad-events.patch
At peak processing times, the show jobs status window will display jobs in a ready or scheduled state for a long time (typically when processing many projects at once or large projects). This is normal behavior and dependent on the number and speed of the agents running.
The following messages are written to the log file each time the agent pkgmettagetta executes on 64 bit processors.
Loading `libextractor_exiv2' plugin failed: /usr/lib/libextractor/libextractor_exiv2.so: cannot open shared object file: No such file or directory Loading `libextractor_ole2' plugin failed: /usr/lib/libextractor/libextractor_ole2.so: cannot open shared object file: No such file or directory Loading `libextractor_ogg' plugin failed: /usr/lib/libextractor/libextractor_ogg.so: cannot open shared object file: No such file or directory Loading `libextractor_mpeg' plugin failed: /usr/lib/libextractor/libextractor_mpeg.so: cannot open shared object file: No such file or directory
Perform the following steps to update and existing fossology database.
invoke psql as user fossy
psql -U fossy -d fossology
cut-n-paste the following lines at the fossology⇒ prompt:
alter table agent_lic_raw add column lic_url text; alter table agent_lic_raw add column lic_date timestamp with time zone; comment on column agent_lic_raw.lic_url is 'URL origin of the license'; comment on column agent_lic_raw.lic_date is 'when license text was captured'; alter table jobqueue add column jq_elapsedtime integer default 0; alter table jobqueue add column jq_processedtime integer default 0; alter table jobqueue add column jq_itemsprocessed integer default 0; comment on column jobqueue.jq_elapsedtime is 'Elapsed secs working on jq'; comment on column jobqueue.jq_processedtime is 'sum of process times (secs) from all agents'; comment on column jobqueue.jq_itemsprocessed is 'sum of files processed by all agents';