Git Product home page Git Product logo

fossology / fossology Goto Github PK

View Code? Open in Web Editor NEW
752.0 63.0 401.0 303.66 MB

FOSSology is an open source license compliance software system and toolkit. As a toolkit you can run license, copyright and export control scans from the command line. As a system, a database and web ui are provided to give you a compliance workflow. License, copyright and export scanners are tools used in the workflow.

Home Page: https://fossology.github.io/

License: GNU General Public License v2.0

Makefile 0.07% Shell 2.26% PHP 35.64% PureBasic 0.03% C 16.46% Perl 0.04% HTML 34.66% JavaScript 2.69% Java 0.03% C++ 1.99% Python 0.67% CSS 0.15% PLpgSQL 0.03% Roff 0.82% Dockerfile 0.03% Hack 0.04% Twig 3.21% CMake 1.19%
fossology spdx license-management license compliance oss license-checking license-scan compliance-check compliance-automation

fossology's Introduction

FOSSology

Gitpod ready-to-code GPL-2.0 CII Best Practices Coverage Status Slack Channel GitHub release (latest by date) YouTube Channel REUSE status

About

FOSSology is an open source license compliance software system and toolkit. As a toolkit, you can run license, copyright, and export control scans from the command line. As a system, a database and web UI are provided to give you a compliance workflow. In one click you can generate an SPDX file or a ReadMe with all the copyrights notices from your software. FOSSology deduplication means that you can scan an entire distro, rescan a new version, and only the changed files will get rescanned. This is a big time saver for large projects.

Check out Who Uses FOSSology!

FOSSology does not give legal advice. https://fossology.org/

Requirements

The PHP versions 7.3 and later are supported to work for FOSSology. FOSSology requires Postgresql as the database server and apache httpd 2.6 as the web server. These and more dependencies are installed by utils/fo-installdeps.

To install Python dependencies, run install/fo-install-pythondeps.

Installation

FOSSology should work with many Linux distributions.

See https://github.com/fossology/fossology/releases for source code download of the releases.

For installation instructions see Install from Source page in Github Wiki

Docker

FOSSology comes with a Dockerfile allowing the containerized execution both as a single instance or in combination with an external PostgreSQL database. Note: It is strongly recommended to use an external database for production use since the standalone image does not take care of data persistency.

A pre-built Docker image is available from Docker Hub and can be run using the following command:

docker run -p 8081:80 fossology/fossology

The docker image can then be used using http://IP_OF_DOCKER_HOST:8081/repo user fossy password fossy.

If you want to run Fossology with an external database container, you can use Docker Compose, via the following command:

docker-compose up

Docker Compose is a tool that allows you to define and run multi-container applications using a YAML file. FOSSology provides a docker-compose.yml file that defines three services: scheduler, web, and db.

The scheduler service runs the FOSSology scheduler daemon, which handles the analysis tasks. The web service runs the FOSSology web server, which provides the web interface. The db service runs a PostgreSQL database server, which stores the FOSSology data.

The docker-compose up command starts all the three services at once.

The FOSSology web service allows you to configure its database connection using some environment variables. These variables are defined in the docker-compose.yml file under the environment key.

  • FOSSOLOGY_DB_HOST: Hostname of the PostgreSQL database server. An integrated PostgreSQL instance is used if not defined or set to localhost.
  • FOSSOLOGY_DB_NAME: Name of the PostgreSQL database. Defaults to fossology.
  • FOSSOLOGY_DB_USER: User to be used for PostgreSQL connection. Defaults to fossy.
  • FOSSOLOGY_DB_PASSWORD: Password to be used for PostgreSQL connection. Defaults to fossy.

You can change them if you want to use a different database server or credentials.

Vagrant

FOSSology comes with a VagrantFile that can be used to create an isolated environment for FOSSology and its dependencies.

Pre-requisites: Vagrant >= 2.x and Virtualbox >= 5.2.x

Steps:

git clone https://github.com/fossology/fossology
cd fossology/
vagrant up

The server must be ready at http://localhost:8081/repo/. The login credentials are:

user: fossy
pass: fossy

Test Instance

For trying out FOSSology quickly, a test instance is also available at https://fossology.osuosl.org/. This instance can be deleted or reinstalled at any time, thus it is not suitable for serving as your productive version. The login credentials are as follows:

Username: fossy
Password: fossy

Note: The test instance is not up to date with the latest release. The instance will reset every night at 2 am UTC and all the user uploaded data will be lost.

Quick dev prototype with GitPod.io

FOSSology is ready to be coded on GitPod.io. To use it, you would need to setup an account. You can directly use the following button to launch the project on GitPod.io: Link to Gitpod

Once in, you should see 2 terminals, one running FOSSology scheduler and one running the installation.

Handy scripts/aliases

For the ease of usability, following aliases/scripts have been defined and can be used:

  • conffoss: This will reconfigure cmake with all variables
  • buildfoss: This will build the FOSSology using cmake
  • installfoss: This will install FOSSology
  • fossrun: Run the FOSSology scheduler
  • pg_stop: Stop PostgreSQL server
  • pg_start: Start PostgreSQL server

Documentation

We are currently migrating our documentation to Github. At this stage, you can find general documentation at: https://www.fossology.org/get-started/basic-workflow/ and developer docs on Github Wiki and https://fossology.github.io/

Support

Mailing lists, FAQs, Release Notes, and other useful info are available by clicking the documentation tab on the project website. We encourage all users to join the mailing list and participate in discussions. There is also a #fossology IRC channel on the freenode IRC network if you'd like to talk to other FOSSology users and developers. See Contact Us

Contributing

We really like contributions in several forms, see CONTRIBUTING.md

Licensing

The original FOSSology source code and associated documentation including these web pages are Copyright (C) 2007-2012 HP Development Company, L.P. In the past years, other contributors added source code and documentation to the project, see the NOTICES file or the referring files for more information.

Any modifications or additions to source code or documentation contributed to the FOSSology project are Copyright (C) the contributor, and should be noted as such in the comments section of the modified file(s).

FOSSology is licensed under GPL-2.0

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2 of the License

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Exception:

All of the FOSSology source code is licensed under the terms of the GNU General Public License version 2, with the following exceptions:

libfossdb and libfossrepo libraries are licensed under the terms of the GNU Lesser General Public License version 2.1, LGPL-2.1.

This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License.

This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301  USA

Please see the LICENSE file included with this software for the full texts of these licenses.

fossology's People

Contributors

ag4ums avatar aman-codes avatar bcornec avatar bufferoverflow avatar darshank15 avatar dependabot[bot] avatar deveaud-m avatar fogninid avatar gmishx avatar joshovi avatar larainema avatar markdo avatar max-wittig avatar maxhbr avatar mcjaeger avatar nicolastoussaint avatar peterdavehello avatar pguttmann avatar rlintu avatar robertvolkmann avatar rohitpandey49 avatar sandipbhuyan avatar shaheemazmalmmd avatar soham4abc avatar stefanschroeder avatar steffen-weber avatar taggart avatar timurphy avatar vargenau avatar yaobinshi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fossology's Issues

Fossology incorrectly reporting license(s) for jqRangeSlider

Both nomos and monk appear to have "opportunities" revealed by the package jqRangeSlider at -
https://github.com/ghusse/jQRangeSlider
Download URL - https://github.com/ghusse/jQRangeSlider/archive/master.zip

Monk is reporting https://github.com/ghusse/jQRangeSlider/blob/master/MIT-License.txt as JSON (92%) rather than MIT even though the "interesting" phrase "The Software shall be used for Good, not Evil." is absent!

Nomos is reporting some files as simply GPL rather than dual MIT/GPL - for instance https://github.com/ghusse/jQRangeSlider/blob/master/Readme.md

bucket tag link not active


Author Name: Bob Gobeille
Original Redmine Issue: 1029, http://www.fossology.org/issues/1029
Original Date: 2012/02/14
Original Assignee: Bob Gobeille


The bucket browser has a tag link in the histogram, but the link is not active (it's just text). The idea is to make it easy to tag all the items in a bucket.

Agents need to give more informative error messages in the logs


Author Name: Mark Donohoe
Original Redmine Issue: 549, http://www.fossology.org/issues/549
Original Date: 2012/01/25
Original Assignee: Mary Laser


The agent logs do not contain enough information to determine what went wrong. Using an error code like 3 or agent code 12 does not indicate what the real error was. Saying only in the log that the agent failed is also not helpful when trying to figure out what the problem is or how it might be fixed.

The agents should give informative messages like 'file xxx not found', no permission to write to xxxx, can't schedule scheduler, go db error xxxx, etc...

Migrate wiki to github

It would nice to be able to contribute edits to a wiki on github as well. i.e. creating an entry on building nomos on mac:

brew update
brew install glib

Then edit makefile.conf to append brew's include path to glib as a CFLAG:

-I/usr/local/Cellar/glib/2.42.0/include/glib-2.0/

showjobs creates blank windows when next is pressed but no additional jobs are present


Author Name: Cat X
Original Redmine Issue: 1335, http://www.fossology.org/issues/1335
Original Date: 2012/02/28
Original Assignee: Bob Gobeille


The 'showjobs' window creates extra blank windows beyond the existing list of jobs when 'next' or the subsequent number is pressed.

In the attached screenshot, the only window that has jobs listed is #1. If 'next' or the last number in the sequence is pressed, a new empty window, one greater in the sequence is generated.

I'm currently running FOSSology version 2.0.0-devel (code revision 5550)

wget shouldn't be using NOKILL special option


Author Name: Alex Norton
Original Redmine Issue: 1557, http://www.fossology.org/issues/1557
Original Date: 2012/03/15
Original Assignee: Mary Laser


Currently the delagent uses the NOKILL special flag so that the scheduler will not kill it when it is fetching large uploads. If an agent does not call the fo_scheduler_heart() function periodically, the scheduler will kill the agent because it believes that it is no longer going to complete its task. When performing very large uploads, the wget agent will no call fo_scheduler_heart() frequently enough and the scheduler was killing it.

As a patch for this problem, the NOKILL option was added to the wget agent. Wget should be changed to instead correctly call fo_scheduler_heart() since it is still working.

can not see the license text


Author Name: larry shi
Original Redmine Issue: 717, http://www.fossology.org/issues/717
Original Date: 2012/02/02
Original Assignee: larry shi


  1. upload one file, analyze it with nomos
  2. click [License Browser] to see the license info
  3. click license name, for example: The Nomos license scanner found: GPL_v2, click [GPL_v2]
  4. one window popup, the error msg 'Original license text is not in the FOSSology database.'

I am not sure it this issue can be fixed afer the license data is imported from fossology.org.

fo-postinstall script failed with new commit

Hi Andreas,

The new commit you yesterday checked in break the fo-postinstall script, caused following errors, what's the new commits used for?

*** update the database and license_ref table ***
PHP Fatal error: Interface 'Fossology\Lib\Plugin\Plugin' not found in /usr/local/share/fossology/lib/php/Plugin/FO_Plugin.php on line 68
PHP Stack trace:
PHP 1. {main}() /usr/local/lib/fossology/fossinit.php:0
PHP 2. bootstrap() /usr/local/lib/fossology/fossinit.php:105
PHP 3. require_once() /usr/local/lib/fossology/fossinit.php:425
Database connectivity is good.

scheduler startup tests fail inconsistently on multiserver installations

I have observed this on two multi server installations (fossologyitg.fc and fossology.fc). When the scheduler starts and runs the startup tests on the agent machines, some of the tests fail. Restarting the scheduler will result in different failures (or all successful). In the example below, all tests passed after a scheduler restart.

For example:
'2014-12-16 09:37:24 scheduler [2080] :: NOTE: *****************************************************************
2014-12-16 09:37:24 scheduler [2080] :: NOTE: *** FOSSology scheduler started ***
2014-12-16 09:37:24 scheduler [2080] :: NOTE: *** pid: 2081 ***
2014-12-16 09:37:24 scheduler [2080] :: NOTE: *** verbose: 1 ***
2014-12-16 09:37:24 scheduler [2080] :: NOTE: *** config: /etc/fossology ***
2014-12-16 09:37:24 scheduler [2080] :: NOTE: *****************************************************************
2014-12-16 09:37:25 scheduler [2080] :: JOB[-15].nomos[2112.foitgagent1]: agent failed, code: 251
2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.957: agent foitgagent1.nomos has failed scheduler startup test
2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.300: agent foitgagent1.nomos has been invalidated, removing from agents
2014-12-16 09:37:25 scheduler [2080] :: JOB[-15].nomos[2112.foitgagent1]: agent didn't send version information: "FATAL libfossscheduler.c.128: unable to insert into agent table: ERROR: duplicate key value violates unique constraint "agent_unique_name_rev""
2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.300: agent foitgagent1.mimetype has been invalidated, removing from agents
2014-12-16 09:37:25 scheduler [2080] :: JOB[-11].mimetype[2107.foitgagent1]: agent didn't send version information: "FATAL libfossscheduler.c.128: unable to insert into agent table: ERROR: duplicate key value violates unique constraint "agent_unique_name_rev""
2014-12-16 09:37:25 scheduler [2080] :: JOB[-11].mimetype[2107.foitgagent1]: agent was killed by signal: 9.Killed
2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.957: agent foitgagent1.mimetype has failed scheduler startup test
'

please check the count items in 'License Browser' page

Hi,

If you take a look at
http://fossology.ow2.org/?mod=nomoslicense&upload=36&item=269768
you'll see :

51 Unique licenses
3676 Licenses found
5023 Files with no licenses
9378 Files

And here
http://fossology.ow2.org/?mod=nomoslicense&upload=18&item=113950 :

16 Unique licenses
185 Licenses found
826 Files with no licenses
974 Files

As I understand, "Licenses found" means "Files with Licenses found" ?
If I'm correct, the sum of the two should equal "Files" ?

Thanks !

the msg above is not the latest UI, however, if test the latest License Browser page, will find 'Scanner Count', 'Files with no detected licenses', etc are inaccurate.

scheduler should test for running agents before killing itself


Author Name: Bob Gobeille
Original Redmine Issue: 681, http://www.fossology.org/issues/681
Original Date: 2012/02/01
Original Assignee: Alex Norton


Killing the scheduler kills all the running agents. I think we need to add a failsafe such as:

  1. if there are running agents, the scheduler needs to tell the user and not do the kill. It should also tell the user to use the -f (see #2 below) if the really want to force the kill.

  2. add a new switch, like -f to force the scheduler to die (the current behavior).

  3. add a new option to tell the scheduler to not schedule any new jobs and exit when the current ones are done. That is, just finish running the current jobs, email the user who requested this option, then exit.

Scheduler Administration usability


Author Name: Bob Gobeille
Original Redmine Issue: 447, http://www.fossology.org/issues/447
Original Date: 2012/01/13
Original Assignee: Mary Laser


Scheduler Administration has some usability issues. These are a combination of UI issues and data not coming from the scheduler.

For example, rather than pause job 687, I should be able to pause "mytar.tar nomos (job 687)"

Also, you should only be able to pause a job, change priority, shutdown the scheduler, etc., if you have the right permission level.

There is no way to kill a job.

Job status could be formatted much better

JOB_COMPLETE, JOB_CHECKEDOUT, etc., are not explained

Some operation result in empty secondary pulldowns. For example, if you unpause a job and there are no jobs to unpause. The user can then hit submit on this. The user should just be told that there are no jobs to unpause.

Display fossology.conf should be an option.

missing module conf files after source install


Author Name: Bob Gobeille
Original Redmine Issue: 1773, http://www.fossology.org/issues/1773
Original Date: 2012/04/10
Original Assignee: Bob Gobeille


Running cluster configuration tests from 2.0 source install (http://www.fossology.org/projects/fossology/wiki/Cluster_Test_Cases#Cluster-configuration-tests-Verify-agents-run-on-systems-as-configured)
fossology.log reports missing module conf files:

2012-04-10 11:55:11 scheduler [575] :: CONFIG: Could not find /usr/local/etc/fossology/mods-enabled/www/www.conf
2012-04-10 11:55:11 scheduler [575] :: CONFIG: Could not find /usr/local/etc/fossology/mods-enabled/scheduler/scheduler.conf
2012-04-10 11:55:11 scheduler [575] :: CONFIG: Could not find /usr/local/etc/fossology/mods-enabled/debug/debug.conf

Remove unused indexes


Author Name: Bob Gobeille
Original Redmine Issue: 1755, http://www.fossology.org/issues/1755
Original Date: 2012/04/09
Original Assignee: Bob Gobeille


based on a scan of fo.usa, remove indexes from the db schema that are not used. Specifically:
copyright.agent_fx_idx
attrib.attrib_key_fk_idx

schemaname | relname | indexrelname | idx_scan | index_size
------------+------------------+----------------------------+------------+------------
public | agent_lic_status | processed_idx | 0 | 41 MB
public | copyright | agent_fk_idx | 0 | 2713 MB
public | report_cache | report_cache_createdts | 0 | 32 kB
public | attrib | attrib_key_fk_idx | 1 | 152 MB
public | agent_lic_status | inrepository_idx | 4 | 41 MB

Please have showjobs check the log file size and if huge display the first (or last) n lines and give the log path, rather than error out


Author Name: Mary Laser
Original Redmine Issue: 1731, http://www.fossology.org/issues/1731
Original Date: 2012/04/04
Original Assignee: Bob Gobeille


the RHEL6.1 iso completed, but showjobs cannot display the ununpack job (#461), due to a memory allocation error. I suspect it's because the log file is huge
๎€‚ maryl looks at log file size ....
wow
-rw-rwS--- 1 fossy fossy 3.4G Apr 3 20:28 /srv/fossology/repository/snape/logs/00/04/61/000461
could you file an issue on that please
bobg: I don't think it's an issue. we ran ununpack with -v
but the code could check the file size and if huge display the first (or last) n lines and give the log path, rather than error out
bobg: oh, I see what you mean. k
for 2.0.1

license and bucket filters in search


Author Name: Bob Gobeille
Original Redmine Issue: 483, http://www.fossology.org/issues/483
Original Date: 2012/01/20
Original Assignee: Bob Gobeille


add license and bucket filters in search. This allows the user to get a linear list of all the files in a tree with a certain license (or bucket). Then they can click through to view each one. Combined with tags, for example a tag that says what files need review, this becomes a very powerful feature.

change color on complete in show jobs


Author Name: Mark Donohoe
Original Redmine Issue: 609, http://www.fossology.org/issues/609
Original Date: 2012/01/28
Original Assignee: Bob Gobeille


It would be nice to change the color to green for a completed item when viewing My Recent Jobs, the gray color is not very eye catching. It could just be the column, or the whole row.

utilities used by ununpack in different distros produce different number of items processed


Author Name: Mary Laser
Original Redmine Issue: 1437, http://www.fossology.org/issues/1437
Original Date: 2012/03/07
Original Assignee: Dong Ma


utilities used by ununpack may vary slightly from distro to distro resulting in a different number of items processed. It would be useful to identify where the differences are occurring and build this into our testing: [[Cluster_Test_Cases#Verify-upload-files-numbers]]

interface.c WARNINGS while interacting with Admin Scheduler UI


Author Name: Mary Laser
Original Redmine Issue: 627, http://www.fossology.org/issues/627
Original Date: 2012/01/30
Original Assignee: Dong Ma


2012-01-30 14:22:25 scheduler [12164] :: WARNING interface.c.126: INTERFACE: invalid command:

maryl> norton: do you know why I'm getting these warnings?...
2012-01-30 11:43:55 scheduler [9804] :: WARNING interface.c.126: INTERFACE: invalid command:
norton: They are generated while using the Scheduler Administration UI
someone is sending the scheduler whitespace as a command
if you turn the verobse flag for the interface file on, you will get to see exactly how much white space was sent

UI to set up remote cluster


Author Name: Bob Gobeille
Original Redmine Issue: 1341, http://www.fossology.org/issues/1341
Original Date: 2012/02/29


Given all the problems we have setting up remote clusters, perhaps we need a UI to do it for us. It can verify the connectivity, install agents, set up the conf files, etc.

Some buttons have ! but others do not


Author Name: Paul Holland
Original Redmine Issue: 1227, http://www.fossology.org/issues/1227
Original Date: 2012/02/22
Original Assignee: Mary Laser


Upon selecting various "Upload" menu items, I noticed that some of the buttons have explanation points (!) and others do not:

  • Upload from File (no - "Upload")
  • Upload from Server (yes - "Upload!")
  • Upload from URL (yes - "Upload!")
  • One-Shot Analysis (yes - "Analyze!")
  • One-Shot Copyright ... (no - "Upload and scan")

The buttons should be consistent re: the convention, with our without.

View License Audit vs Edit concluded license

View License has a micro-menu "Audit" link and a regular link to "Edit concluded license". I think it is confusing to have two links named differently that do the same thing. I would remove the "Audit" link in the micro menu since it seems superfluous.

scheduler unable to kill a job that hasn't started


Author Name: Bob Gobeille
Original Redmine Issue: 543, http://www.fossology.org/issues/543
Original Date: 2012/01/25
Original Assignee: Alex Norton


In fo_cli:

kill 831 this job is no longer needed
Command received
Invalid kill command: job 0 does not exist
status
scheduler:11981 revision:(null) daemon:0 jobs:1 log:/var/log/fossology/fossology.log port:5555 verbose:1

There needs to be a way to cancel a job that hasn't started.

descriptions removed with multiple uploads of the same file


Author Name: Mark Donohoe
Original Redmine Issue: 1149, http://www.fossology.org/issues/1149
Original Date: 2012/02/18
Original Assignee: Bob Gobeille


If a file is uploaded multiple times (from file, from url, from server) showjobs only displays that last comment. For testing it's nice to see all the comments, for example, one of the uploads was the second try to see if things worked. The comments can help sort out the different test scenarios.

License Browser has a wrong behavior after migration from 2.6.1 to 2.6.2

license browser is not able to display the license report.

test scenario:

  1. install fossology 2.6.1. on Debian 7.0 32bit
  2. upload one package with all the agents scheduling.
  3. upgrade fossology to 2.6.2 http://www.fossology.org/releases/2.6.2-rc1/debian/
  4. will find this defect even you reschedule all the jobs on that package.
  5. however, miracle happen, after I restart the scheduler, everything work well

need your help to the confirm.
not sure if this is a defect, weird. hope the reason is because my test method or test evn.
thanks.

selecting cancel from my recent jobs page causes "" interface


Author Name: Mark Donohoe
Original Redmine Issue: 1095, http://www.fossology.org/issues/1095
Original Date: 2012/02/16
Original Assignee: Dong Ma


Using svn 5519 on snape.ostt, selecting 'Cancel' in the showjobs page causes this message in the fossology.log and it appears that the jobs are not stopped. Sometimes it works but the display is not updated.

2012-02-16 14:17:14 scheduler [19744] :: INTERFACE: new interface connection
2012-02-16 14:17:14 scheduler [19744] :: INTERFACE: received "kill 194 "Killed by fossy""
2012-02-16 14:17:14 scheduler [19744] :: INTERFACE: send "received"
2012-02-16 14:17:14 scheduler [19744] :: INTERFACE: received ""
2012-02-16 14:17:14 scheduler [19744] :: WARNING interface.c.129: INTERFACE: invalid command: ""
2012-02-16 14:17:16 scheduler [19744] :: INTERFACE: new interface connection
2012-02-16 14:17:16 scheduler [19744] :: INTERFACE: received "kill 195 "Killed by fossy""
2012-02-16 14:17:16 scheduler [19744] :: INTERFACE: send "received"
2012-02-16 14:17:16 scheduler [19744] :: INTERFACE: received ""
2012-02-16 14:17:16 scheduler [19744] :: WARNING interface.c.129: INTERFACE: invalid command: ""
2012-02-16 14:18:37 scheduler [19744] :: SIGNALS: Scheduler received alarm signal, checking job states

can not edit the information for a license


Author Name: larry shi
Original Redmine Issue: 1443, http://www.fossology.org/issues/1443
Original Date: 2012/03/08
Original Assignee: Bob Gobeille


reproduce:

  1. click on [Admin]-->[License Admin] menu, then click on any edit icon, click on the link 'update' to change some items of this license.
  2. repeat the step 1, get one error msg :

File: /usr/local/share/fossology/www/ui/admin-license-file.php, Line number: 361
ERROR: duplicate key value violates unique constraint "rf_md5unique"
UPDATE license_ref set rf_active='true', marydone='false', rf_shortname='3DFX', rf_fullname='', rf_url='', rf_notes='', rf_text_updatable='false', rf_detector_type='2', rf_text='License by Nomos.', rf_md5='2837743839a3f8e500aed1b9144452bb' WHERE rf_pk='202'
#0 debugbacktrace() called at [/usr/local/share/fossology/lib/php/common-db.php:158]
#1 DBCheckResult(, UPDATE license_ref set

             rf_active='true', 
             marydone='false',
             rf_shortname='3DFX',
             rf_fullname='',
             rf_url='',
             rf_notes='',
             rf_text_updatable='false',
             rf_detector_type='2',
             rf_text='License by Nomos.',
             rf_md5='2837743839a3f8e500aed1b9144452bb'
        WHERE rf_pk='202', /usr/local/share/fossology/www/ui/admin-license-file.php, 361) called at [/usr/local/share/fossology/www/ui/admin-license-file.php:361]

#2 admin_license_file->Updatedb(Array ([rf_pk] => 202,[req_marydone] => all,[req_shortname] => All,[updateit] => true,[rf_active] => true,[marydone] => false,[rf_shortname] => 3DFX,[rf_fullname] => ,[rf_text] => License by Nomos.,[rf_text_updatable] => false,[rf_detector_type] => 2,[rf_url] => ,[rf_notes] => )) called at [/usr/local/share/fossology/www/ui/admin-license-file.php:457]
#3 admin_license_file->Output() called at [/usr/local/share/fossology/www/ui/index.php:51]

the reason is because for now, almost all the 'license text' are 'License by Nomos.', but definition of license_ref say rf_md5 should be unique, rf_md5 is from md5(rf_text) .

any method to add a fresh user except through GUI?


Author Name: larry shi
Original Redmine Issue: 1953, http://www.fossology.org/issues/1953
Original Date: 2012/05/14
Original Assignee: Bob Gobeille


any method to add a fresh user except through GUI?

if one user want to upload something through cp2foss, have to pass the authentication, but you know,
after one user install fossology, there is not any user in USER table till the user visits UI(http://hostname/repo/), adding fossy/fossy.

also for test automation, after running testing/db/createTestDB.php, create one new DB and sysconf, you can not visit the GUI, so there is not any user in USER table,
more details according to your respone if needed.

fixing adj2nest work around


Author Name: Alex Norton
Original Redmine Issue: 597, http://www.fossology.org/issues/597
Original Date: 2012/01/27
Original Assignee: Alex Norton


Some agents don't update the number of item processed quickly and for large uploads will go a very long time without changing this number. This results in the scheduler choosing to kill the agent because it believes that the agent has entered an infinite loop. There should be a way for an agent to turn off this feature when the scheduler deals with it or for the agent to correctly be able to update the number of items processed.

Adj2nest is currently the only agent that is having this problem and is currently using a dummy fo_scheduler_heart(1) to keep the scheduler from killing it when it is processing large distributions. This work around it not ideal and should be replace with a more long term solution.

Upload from file failed with unhelpful error

Upload from File just failed with the error below. It is very frustrating to users to get errors that don't tell them what is wrong. We need to improve the error message.

Upload failed for file Fedora-12-source-DVD.iso: FATAL wget_agent.c.137: upload 2240 Failed to import /tmp/phpliy0fR-uploaded from /tmp/phpliy0fR-uploaded into repository gold 3135D6F013A19D0BF460C558A9E865796282BE9C.FF494BED045C64861B807A56F301897A.4544911360

c library unit tests aren't running


Author Name: Alex Norton
Original Redmine Issue: 1527, http://www.fossology.org/issues/1527
Original Date: 2012/03/14
Original Assignee: Mark Donohoe


The nightly build is not running the unit tests for the c library functions. I figured this out because I went to check that some changes I made recently hadn't broken the tests for the fossconfig library and found that the tests for fossconfig and libfossscheduler didn't even build and haven't for several months.

The relevant tests can be found under src/lib/c/tests

I have fixed the tests so that they will now build but they don't run currently because of a failure in libfossdb.

UI improvement to concluded license handling

I propose following changes for handling concluded license in
different views.

  1. Adding new user permission level ("Audit"). The user has to
    have this permission level in order to change/review licenses.
  2. Removing the 'Edit concluded license' button from View License
    view if concluded license has already been set. In that case
    additional change has to be done via Audit menu.
  3. Adding possibility to set concluded license directly from
    List Files for License in case concluded license has not been
    set. Also it could be useful to set concluded license for
    multiple files at the same time.
  4. Concluded license is shown in addition to scanner result in
    List Files for License view.
  5. Restoring the capability to change nomos scanner result.

All these changes except setting concluded license for multiple
files are demonstrated in the patch which can be found in
http://www.fossology.org/issues/8103.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.