Re: [FOSSology] Black duck Software Competitor
Hello Himanshu, FOSSology is an open source application that focuses on license scanning, categorization and copyright. The application is free for you to download, install use from the project website at http://fossology.orghttp://fossology.org/. For additional information about FOSSology vs. Black Duck, I recommend the article posted by Bog Gobeille (FOSSology Architect) and co-written with Peter Vescuso (Black Duck VP Marketing) on the FOSSBazaar website at https://fossbazaar.org/content/black-duck-software-vs-fossology-project Thanks for your interest in FOSSOlogy. Mary Laser The FOSSology Project http://fossology.orghttp://fossology.org/ From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gugnani, Himanshu Sent: Tuesday, September 06, 2011 1:36 AM To: fossology@fossology.org Cc: Agarwal, Vishal Subject: [FOSSology] Black duck Software Competitor Hi Team, We require a product for our customer, that can replace Black duck Protex and is even more efficient. So please send us the quotation for the same and differentiation vis-à-vis Black Duck. Thanks and Regards, [Description: Description: Description: Description: cid:image001.png@01CB6EAE.CD450AD0] Himanshu Gugnani Technology Evangelist | SoftwareONE India Private Limited Office: +91 11 42235326 | Mobile: +91 9-34744 | Fax: +91 11 42235222 Email: himanshu.gugn...@softwareone.commailto:himanshu.gugn...@softwareone.com | www.softwareone.comhttp://www.softwareone.com/ [Description: Description: Description: Descrição: Descrição: Descrição: Descrição: Description: cid:image002.jpg@01C8A62B.F6CF3B80]Please don't print this e-mail unless you really need to inline: image001.pnginline: image002.jpg___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Drop support for RHEL5 in FOSSology 2.0?
Good to know. Thanks for your timely response. From: Fay Michael T [mailto:faymicha...@johndeere.com] Sent: Wednesday, August 17, 2011 2:00 PM To: Laser, Mary; fossology@fossology.org Subject: RE: Drop support for RHEL5 in FOSSology 2.0? We wouldn't be able to upgrade any time soon. Our IT department is probably a year out from allowing RHEL 6. This wouldn't be a big deal if 1.4.1 remains supported and big fixes are done, but if all such support drops shortly after 2.0 is out, we will have difficulty. From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Wednesday, August 17, 2011 2:56 PM To: fossology@fossology.org Subject: [FOSSology] Drop support for RHEL5 in FOSSology 2.0? Hello FOSSologists, We are deep into development test of FOSSology version 2.0 http://fossology.org/v2.0 and making good progress. A large part of 2.0 is a complete rewrite of the scheduler with a new dependency on libglib2.0-dev, version 2.23.0 or greater. We recently discovered the newest available version of glib in RHEL5 does not meet this requirement. We would like to consider dropping support for RHEL5 with FOSSology 2.0. This would require all current FOSSology users running under RHEL5 to upgrade to RHEL6. Please respond to this email Will this affect your FOSSology installation? Please respond to this email with your comments feedback. Thanks. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Nomos missing BSD reference?
Hi Pete, Based on your email, I see you're using a (older?) version of FOSSology which includes the (deprecated) bsam analyzer. Your first question below refers to a table generated using bsam. Since we're no longer supporting bsam, I don't have the means to reproduce your result in order to address your question. Maybe some other bsam user knows? I did download the openssl tar file and reproduce your results using nomos license analysis. Yes, clearly there is a BSD reference in the cmll file. It's not clear if this is a bug OR if nomos has chosen to not to enumerate this license in favor of more interesting licenses. I will file a bug to see which it is. Thanks for pointing it out. Mary Mary Laser The FOSSology Project http://fossology.org -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Peter Jalajas, GigaLock Backup Services Sent: Thursday, August 11, 2011 12:49 PM To: fossology@fossology.org Subject: [FOSSology] Nomos missing BSD reference? Hi all, I am just learning fossology. I have been scanning well-known projects for testing. I found these littles issues, I think. 1. Nomos sees the MPL reference in the file (as indicated in several places in fossy), but does not list it in the little Match/Item table at the top of page for that file. 2. Nomos doesn't see the explicit reference to BSD in file at all. Are these bugs, or am I missing something? Thanks, Pete Folder: Software Repository/ openssl-1.0.0d.tar.gz/ openssl-1.0.0d.tar/ openssl-1.0.0d/ crypto/ camellia/ asm/ cmll- x86_64.pl Nomos One-Shot | One-Shot Copyright/Email/URL * Nomos License | View | Info | View Copyright/Email/Url * Hex | Text | Formatted * Reanalyze | bsam License | bsam One-Shot | Recompare * Refresh Match Item view GPL v2+, LGPL v2.1+ The Nomos license scanner found: GPL_v2+ ,LGPL_v2.1+ ,MPL_v1.1 #!/usr/bin/env perl # # Copyright (c) 2008 Andy Polyakov ap...@openssl.org # # This module may be used under the terms of either the GNU General # Public License version 2 or later, the GNU Lesser General Public # License version 2.1 or later, the Mozilla Public License version # 1.1 or the BSD License. The exact terms of either license are # distributed along with this module. For further details see # http://www.openssl.org/~appro/camellia/. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Nomos missing BSD reference?
Good to know. Thanks Pete. BTW, the bug can be viewed at http://bugs.linux-foundation.org/show_bug.cgi?id=924 -Original Message- From: Peter Jalajas, GigaLock Backup Services FWIW, from my viewpoint, to be clear, it is _very_ important to indicate such less interesting licenses such as BSD because that would allow me to focus my time first on those files that _only_ have more interesting licenses such as GPL.) Thanks again! Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
-Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Peter Jalajas, GigaLock Backup Services Sent: Tuesday, August 02, 2011 8:22 PM To: fossology@fossology.org Subject: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression This is VERY likely the cause. Please do delete the uploads completely and try again. The delete must run to a successful completion before you try and upload again. Otherwise, you run the risk of having 2 uploads in your DB with the same signature. Mary Likely due to trying to delete a prior Upload of the RedHat test file that threw a couple of FAILED agents. Deleting these Uploads and starting again is no big deal, I'm just familiarizing myself with FOSSology. Suggestions welcome! (I'm not afraid of the command line.) Thanks! Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
See inline responses... -Original Message- Subject: Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression Thanks, Mary and Bob. Perhaps my problem was, more specifically, that I deleted the Uploaded file _while_ the Agents were still running on it? Should I have deleted the _jobs_ first, and then the Upload? Yes and yes. When I deleted the Upload, there were many jobs in the queue for _other_ Uploads. In such a case, could it take quite a long time before the Scheduler even _begins_ to delete the Upload? It depends on how your scheduler is configured. If you have installed on a single system (probably the case), and are using the default Scheduler.conf file, then you can run a max of 3 agents at one time (%Host localhost 3 1). I don't remember now, but I believe I recall seeing the delagent job at the very bottom of the queue for that Upload, making it appear that the Scheduler would delete the Upload only having completed all the jobs for that Upload (I don't recall the job numbers)--is that true? Yes Delete Upload doesn't automatically deletes all jobs for that Upload, does it? No. that has to be done manually Mary Thanks again, Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] 1.2.0 Inconsistency detected by ld.so; bad 1.4.0 svn url
Hi Pete, Welcome to FOSSology! Thank you for the feedback on your attempts to install 1.2.0, 1.3 and 1.4.0 FOSSology. I'm sorry you were advised to install 1.2.0. This is a very old version and had known critical defects that were addressed in a 1.2.1 release in September 2010. Our most recent release, 1.4.1, is the current supported version of FOSSology (http://fossology.org/download#supported_fossology_releases). As pointed out in your email below, our previous license scanner (bsam), included a license highlighting feature that is no longer available in nomos. This past week, we received several emails from users expressing their desire to see license highlighting reintroduced in a future release. (personally, I liked it, too.) We will look to put it back on our roadmap after the 2.0 release. I fixed the bad URL on our download page. Thanks for pointing it out. As I recall, the pkgmetagetta initialization error during installation was caused by a missing libextractor library. It looks like the old 1.2.0 version has a dependency that is no longer available on your relatively newer o/s. In all honesty, the best advice I can give you is to use our most recent 1.4.1 release for best results and optimal support. Mary Mary Laser The FOSSology Project http://fossology.org -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Peter Jalajas, GigaLock Backup Services Sent: Monday, August 01, 2011 7:55 PM To: fossology@fossology.org Subject: [FOSSology] 1.2.0 Inconsistency detected by ld.so; bad 1.4.0 svn url Hi all, New member and fossology user here. Version 1.2.0 was recommended to me, with: 1.2 has both nomos and bsam searches. Occasionally, bsam will find things that nomos doesn't and bsam highlights the license match, whereas nomos does not. So on nomos-only matches, you have to manually scan the file to find the match. I understand that 1.2 is no longer supported; and I very much don't want to debate those statements here. I'm on Ubuntu Natty 11.04 64 bit on Amazon EC2. I tried installing fossology 1.2 from both the Ubuntu repos (with sudo apt-get install fossology) and svn, and it didn't quite work, throwing... -- ... Initializing agents. Inconsistency detected by ld.so: dl-close.c: 737: _dl_close: Assertion `map-l_init_called' failed! FATAL: '/usr/local/lib/fossology/agents/pkgmetagetta -i' failed to initialize *** Setting up scheduler *** ... continued with no further errors -- ...during both the apt-get install and also the svn make install. That led to missing license-agent errors later (see the Initializing agents. log line above. Details of the license-agent error available upon request). I realize Ubuntu Natty 11.04 is not a supported platform. I worked around by installing 1.3 via svn: svn co https://fossology.svn.sourceforge.net/svnroot/fossology/tags/1.3.0/ . which has been working fine (I am scanning and reviewing results fine). Separate issue: Additional tests on this machine with 1.4 and trunk from similar urls worked fine. But please note that the url in this command: svn co http://fossology.svn.sourceforge.net/viewvc/fossology/branches/fossolog y-1.4.0/ from: http://fossology.org/download throws: svn: Repository moved temporarily to '/viewvc/fossology/branches/fossology-1.4.0/'; please relocate Instead, the link that worked for me was: svn co https://fossology.svn.sourceforge.net/svnroot/fossology/tags/1.4.0/ . (But I went back to 1.2 as recommended to me.) So, any help working through the unsupported 1.2.0 ld.so error at the top of this message would be appreciated. Thanks, Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] License highlighting (Bob Gobeille)
Hello FOSSologists! Thank you all for your votes. It's very important for us to hear from our users so we know how to prioritize the many features and requests we have on our to-do list. We REALY do listen and value your feedback. Keep it coming! The FOSSology Project http://fossology.org -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Dabrowski, Ivo Sent: Friday, July 29, 2011 6:12 AM Subject: Re: [FOSSology] License highlighting (Bob Gobeille) Here's my vote, too. BSAM as used in older versions of FOSSology reveals matches (and derivations) easily. Ivo -Ursprüngliche Nachricht- Von: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] Im Auftrag von Bob Gobeille Gesendet: Freitag, 29. Juli 2011 01:27 Betreff: Re: [FOSSology] License highlighting (Bob Gobeille) Oh - multiple pages. That is painful. Thanks for voting Dave. Bob Gobeille On Jul 28, 2011, at 4:43 PM, Dave McLoughlin wrote: I'll cast my vote, highlighting is very important to us. We spend a lot of time searching, scrolling and manually scanning contents to find a match when there's no highlighting. It's extremely painful when the contents are displayed across multiple pages. Dave Date: Wed, 27 Jul 2011 12:05:56 -0600 From: Bob Gobeille bob.gobei...@hp.com Subject: Re: [FOSSology] License highlighting Hello Volker, The database table license_file is where nomos records what license matched in what file. There are columns for where in the file the match occurred, but they are not currently populated by nomos. Would anyone else like to vote on how important highlighting the license match is? Bob Gobeille ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] v2.0 tasks code complete milestone
Hi Everyone, Thank you all for providing time estimates for each of your tasks. I've entered everything into ms project to get a projected date for our code complete milestone (as we agreed :) code complete INCLUDES all tests for checked-in code). The code complete milestone is set at October 28th. As I mentioned in our last meeting, Bob is the critical path right now. However there are many small tasks assigned to him that could be picked up by others as their tasks come to a completion. I'll be including additional milestones to project and track these critical pieces: Ø Successful Build/Install of 2.0 (for test purposes) Ø Nightly testing and reporting for the 2.0 branch Ø Package Automation Ø Test/debug cycle Ø Test complete Ø RC1 Ø Fix critical bugs Ø RC2 Ø Doc updates Ø Release I've attached a spreadsheet of tasks/owners/DTC generated from data exported from project. I intend to use this to track everyone's progress. I'll update it weekly and email to you. Thanks, Mary Mary Laser Open Source Program Office Hewlett Packard 970-898-0878 FO2.0.xls Description: FO2.0.xls ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Standards for reporting FOSSology test results
Hi All, FOSSology has established test frameworks and standard reports. The reporting standard is the unit report format. This varies depending on what is being tested: * c code: CUnit * PHP code: phpunit, or simpletest, phpunit is preferred for straight unit tests. By itself, phpunit cannot test UI's. * ui: simepletest. Only simpletest has a way to test a browser, but it can't deal with javascript updates to the screen. If you don't use one of the existing test frameworks, then whatever you choose must produce a xml report in junit format. The definition for the junit report format can be found on the fossology wiki at: http://fossology.org/test:junit_format It is strongly suggested that you use one of the existing test frameworks to create tests. If you choose not to, a suggested method to produce junit report formats is to wrap all test cases in PHUnit. By running PHPUnit with --log-junit flag, the results will be in junit format. Thanks for your support and compliance with these test reporting standards. Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Failed to insert upload record...
Hello again Yiling, Based on the postgres warnings, it appears the fossology database was NOT created during the installation. Please (re)run this command /usr/lib/fossology/fo-postinstall and examine the output carefully for errors. You should see messages indicating user fossy is being added (or is already added) and the fossology database is being built (or is already built). Please capture the output and send it to me for review. Thanks, Mary From: Yiling Tsai [mailto:tyle2...@gmail.com] Sent: Wednesday, July 13, 2011 1:57 AM To: Laser, Mary Subject: Re: [FOSSology] Failed to insert upload record... Thank you, Mary. I installed v1.4.0 with package, the system showed error Failed to insert upload record. It seemed the installation not successful. I upgraded it to V1.4.1 through Synaptic Package Manager, and Fossology seems to work : ) I checked the scheduler configuration in v1.4.1 installation with /usr/lib/fossology/fossology-scheduler -t -L stdout. I could see STATUS: All scheduler agents are operational. at the end of the stdout. But I connected to fossology db via psql -U fossy -d fossology, it showed psql: warning: extra command-line argument -d ignored psql: warning: extra command-line argument fossology ign psql: FATAL: Ident authentication failed for user fossy I found message below in log file (/var/log/postgresql/postgresql-8.4-main.log). 2011-07-13 15:48:30 CST LOG: provided username (fossy) and authenticated username (root) don't match 2011-07-13 15:48:30 CST FATAL: Ident authentication failed for user fossy Did my Fossology v1.4.1 work well? Hi Yiling, I need a little more information before I can address your error... 1. What version of fossology are you using? 2. Did you install from package or from source? 3. Was the installation successful? 4. Can you connect to you fossology db via psql -U fossy -d fossology ? (password: fossy) 5. Are there additional errors in the fossology log file (/var/log/fossology/fossology.log)? 6. Are there errors in the postgresql log file (/var/log/postgresql/postgresql-8.3-main.log)? Mary From: fossology-boun...@fossology.orgmailto:fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.orgmailto:fossology-boun...@fossology.org] On Behalf Of Yiling Tsai Sent: Tuesday, July 12, 2011 12:28 AM To: fossology@fossology.orgmailto:fossology@fossology.org Subject: [FOSSology] Failed to insert upload record... Hi, I am a newbie using Fossology, installed on Ubuntu 10.04. I tried to upload a .c file, the system showed 'Failed to insert upload record'. How can I check what happened to my Fossology system? Any help would be highly appreciated. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Failed to insert upload record...
Hi Yiling, I need a little more information before I can address your error... 1. What version of fossology are you using? 2. Did you install from package or from source? 3. Was the installation successful? 4. Can you connect to you fossology db via psql -U fossy -d fossology ? (password: fossy) 5. Are there additional errors in the fossology log file (/var/log/fossology/fossology.log)? 6. Are there errors in the postgresql log file (/var/log/postgresql/postgresql-8.3-main.log)? Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Yiling Tsai Sent: Tuesday, July 12, 2011 12:28 AM To: fossology@fossology.org Subject: [FOSSology] Failed to insert upload record... Hi, I am a newbie using Fossology, installed on Ubuntu 10.04. I tried to upload a .c file, the system showed 'Failed to insert upload record'. How can I check what happened to my Fossology system? Any help would be highly appreciated. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Database connection error
Hi Dave, Sorry your having such a difficult time :-( This is definitely a Postgres problem. Try these steps: 1. Carefully check the configuration of pg_hba.conf. Don't assume that what worked with your older Ubuntu version will work with Ubuntu 11.04. You may have to refer to the online PG docs. (they are an excellent resource) 2. Make sure user fossy owns the fossology db. You must become the postgres user and then invoke psql to examine the fossology db. 3. Once you can successfully access the db via psql -d fossology -U fossy, try starting the scheduler. 4. Please send us your solution for our troubleshooting page (http://fossology.org/troubleshooting). Mary From: Dave McLoughlin [mailto:dave.mclough...@openlogic.com] Sent: Friday, July 08, 2011 10:40 AM To: Laser, Mary; fossology@fossology.org Subject: RE: Database connection error Mary, I should have included the postgresql logs yesterday. Does this help pinpoint the issue? This is the last couple entries from the postgresql log: 2011-07-07 15:39:15 MDT [local] 4e162783.ccbLOG: provided username (fossy) and authenticated username (user) don't match 2011-07-07 15:39:15 MDT [local] 4e162783.ccbFATAL: Ident authentication failed for user fossy thanks, Dave -Original Message- From: Laser, Mary [mailto:mary.la...@hp.com] Sent: Thu 7/7/2011 3:59 PM To: Dave McLoughlin; fossology@fossology.org Subject: RE: Database connection error This usually is a symptom of a mis-configured postgres file; typically /etc/postgresql/8.3/main/pg_hba.conf Look in the postgres log file (/var/log/postgresql/postgresql-8.3-main.log) for additional clues to your error. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Dave McLoughlin Sent: Thursday, July 07, 2011 3:46 PM To: fossology@fossology.org Subject: [FOSSology] Database connection error I'm running into a problem with a database connection error after install of 1.4.1 on Ubuntu 1.4.1. When I re-ran fo-postinstall to make sure everything was okay I got: *** Running postinstall for everything *** *** Setting up the FOSSology database *** NOTE: fossology database already exists, not creating *** Checking for plpgsql support *** NOTE: plpgsql already exists in fossology database, good *** Creating user and group *** NOTE: group 'fossy' already exists, good. NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** NOTE: Repository already exists at /srv/fossology/repository NOTE: /srv/fossology/repository/localhost directory already exists *** Checking database connectivity *** NOTE: Connect succeeded, database is working. But my fossology.log shows 2011-07-07 13:30:49 scheduler[1030] : FATAL: fo_watchdog unable to connect to database. Terminating. 2011-07-07 13:34:30 scheduler[2408] : Log opened 2011-07-07 13:34:30 scheduler[2408] : Scheduler kill requested. Killing scheduler. Also trying psql I get: $ psql -d fossology -U fossy psql: FATAL: Ident authentication failed for user fossy Any ideas? Dave Any ideas? ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Deb install on Ubuntu
File locations are listed here: http://fossology.org/file_locations The debian install instructions are here: http://fossology.org/debian_install Please refer to the INSTALL file for Apache Config. http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.4.0~rc7/INSTALL?revision=4199view=markup Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Dave McLoughlin Sent: Thursday, July 07, 2011 10:06 AM To: fossology@fossology.org Subject: [FOSSology] Deb install on Ubuntu Up til now, I've only installed fossology from source. Yesterday I went to do a clean install of the latest release 1.4.1 on Ubuntu 11.04. So I downloaded fossology_1.4.1_all.deb (http://fossology.org/debian/ubuntu/maverick/fossology_1.4.1_all.deb). I double clicked on the package and it appears to have installed something. How do I know what it installed, where it installed it and what I need to do next to get fosslogy running? Is there a README associated with the deb package? I checked top -u fossy and it shows that it is running. But when I go to http://localhost/repo/, it appears Apache is not configured. So, it appears there are some additional steps I need to take to complete the install, I'm just not sure what they are. Any assistance would be appreciated. -- Dave McLoughlin | OpenLogic ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Deb install on Ubuntu
There are messages printed to stdout : ... Initializing agents. Initialization completed. Importing license_ref table data Initialization completed successfully. FOSSology postinstall complete, but sure to complete the remaining steps in the INSTALL instructions. Setting up fossology-scheduler-single (1.4.1) ... *** Setting up scheduler *** *** Checking Scheduler.conf *** NOTE: default /etc/fossology/Scheduler.conf created. Please check that is it correct for your environment or create a different one with mkschedconf. FOSSology postinstall complete, but sure to complete the remaining steps in the INSTALL instructions. Starting FOSSology job scheduler: scheduler. Setting up fossology-web-single (1.4.1) ... *** Setting up the web interface *** NOTE: Adding user www-data to group fossy FOSSology postinstall complete, but sure to complete the remaining steps in the INSTALL instructions. Setting up fossology (1.4.1) ... laser@squeezevm:~$ From: Gobeille, Robert Sent: Thursday, July 07, 2011 10:36 AM To: Laser, Mary Cc: Dave McLoughlin; fossology@fossology.org Subject: Re: [FOSSology] Deb install on Ubuntu Hi Mary, How is a user supposed to know this? Was there instructions in the apt-get install? Bob Gobeille On Jul 7, 2011, at 10:20 AM, Laser, Mary wrote: File locations are listed here: http://fossology.org/file_locations The debian install instructions are here: http://fossology.org/debian_install Please refer to the INSTALL file for Apache Config. http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.4.0~rc7/INSTALL?revision=4199view=markup Mary From: fossology-boun...@fossology.orgmailto:fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Dave McLoughlin Sent: Thursday, July 07, 2011 10:06 AM To: fossology@fossology.orgmailto:fossology@fossology.org Subject: [FOSSology] Deb install on Ubuntu Up til now, I've only installed fossology from source. Yesterday I went to do a clean install of the latest release 1.4.1 on Ubuntu 11.04. So I downloaded fossology_1.4.1_all.deb (http://fossology.org/debian/ubuntu/maverick/fossology_1.4.1_all.deb). I double clicked on the package and it appears to have installed something. How do I know what it installed, where it installed it and what I need to do next to get fosslogy running? Is there a README associated with the deb package? I checked top -u fossy and it shows that it is running. But when I go to http://localhost/repo/, it appears Apache is not configured. So, it appears there are some additional steps I need to take to complete the install, I'm just not sure what they are. Any assistance would be appreciated. -- Dave McLoughlin | OpenLogic ATT1..txt ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Database connection error
This usually is a symptom of a mis-configured postgres file; typically /etc/postgresql/8.3/main/pg_hba.conf Look in the postgres log file (/var/log/postgresql/postgresql-8.3-main.log) for additional clues to your error. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Dave McLoughlin Sent: Thursday, July 07, 2011 3:46 PM To: fossology@fossology.org Subject: [FOSSology] Database connection error I'm running into a problem with a database connection error after install of 1.4.1 on Ubuntu 1.4.1. When I re-ran fo-postinstall to make sure everything was okay I got: *** Running postinstall for everything *** *** Setting up the FOSSology database *** NOTE: fossology database already exists, not creating *** Checking for plpgsql support *** NOTE: plpgsql already exists in fossology database, good *** Creating user and group *** NOTE: group 'fossy' already exists, good. NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** NOTE: Repository already exists at /srv/fossology/repository NOTE: /srv/fossology/repository/localhost directory already exists *** Checking database connectivity *** NOTE: Connect succeeded, database is working. But my fossology.log shows 2011-07-07 13:30:49 scheduler[1030] : FATAL: fo_watchdog unable to connect to database. Terminating. 2011-07-07 13:34:30 scheduler[2408] : Log opened 2011-07-07 13:34:30 scheduler[2408] : Scheduler kill requested. Killing scheduler. Also trying psql I get: $ psql -d fossology -U fossy psql: FATAL: Ident authentication failed for user fossy Any ideas? Dave Any ideas? ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology release 1.4.1 now available
Greetings FOSSologists! The FOSSology Project is pleased to announce the release FOSSology 1.4.1. This is a bug fix release. The list of bugs addressed in this release are herehttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.4.1product=FOSSology. Unofficial install packages on the following platforms distros are now available for download at: * Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.1/ * For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.1/squeeze/ ./ * For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.1/lenny/./http://fossology.org/debian/1.4.1/lenny/ * For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ * The 1.4.1 release rpm packages for rhel5/centos5 rhel6 fedora12/13/14 i386 and x86_64 platforms can be downloaded from: http://fossology.org/rpms/epel/5/i386/fossology-1.4.1-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/5/x86_64/fossology-1.4.1-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/epel/6/i386/fossology-1.4.1-1.el6.i686.rpm -- rhel6 i386 http://fossology.org/rpms/epel/6/x86_64/fossology-1.4.1-1.el6.x86_64.rpm --- rhel6 x86_64 http://fossology.org/rpms/fedora/12/i386/fossology-1.4.1-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/12/x86_64/fossology-1.4.1-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/13/i386/fossology-1.4.1-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/13/x86_64/fossology-1.4.1-1.fc13.x86_64.rpm --- fedora13 x86_64 http://fossology.org/rpms/fedora/14/i386/fossology-1.4.1-1.fc14.i686.rpm --- fedora14 i386 http://fossology.org/rpms/fedora/14/x86_64/fossology-1.4.1-1.fc14.x86_64.rpm --- fedora14 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Rhel/CentOS repo file need add following lines: #FOSSology releases [fossology] name=Fossology releases baseurl=http://fossology.org/rpms/epel/$releasever/$basearch enabled=1 gpgcheck=0 3. Fedora repo file need add following lines: #FOSSology releases [fossology] name=Fossology releases baseurl=http://fossology.org/rpms/fedora/$releasever/$basearch enabled=1 gpgcheck=0 4. yum install fossology Notes: About Rhel6 packages, 1 dependency php-process not available in rhel default repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Viewing the contents of individual files in Synergy package fails
Hi Antti, I downloaded the synergy source package from the URL below to both our internal fossology repository and the public external instance at repo.fossology.org. Both ran to completion; results are here: http://repo.fossology.org/simpleIndex.php?mod=browseupload=225folder=26item=50842807show=detail Since I can't reproduce your results, my next best guess is your installation (or upgrade) for 1.4.1 did not complete successfully. Can you please check your fossology.log file and the postgres log file for errors or other clues that might indicate what's wrong? Did you install from source or packages? A fresh install or upgrade? You may want to re-run /usr/lib/fossology/fo-postinstall and see if it complains about anything. Mary From: Laser, Mary Sent: Wednesday, June 29, 2011 9:31 AM To: 'Antti Luoto'; 'fossology@fossology.org' Subject: RE: [FOSSology] Viewing the contents of individual files in Synergy package fails Hi Antti, Thanks for filing the bug report. I will download your package and attempt to reproduce the error. I'll send an update later today. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Antti Luoto Sent: Wednesday, June 29, 2011 6:13 AM To: 'fossology@fossology.org' Subject: [FOSSology] Viewing the contents of individual files in Synergy package fails I made a bug report (http://bugs.linux-foundation.org/show_bug.cgi?id=833) with the following text: -- Hello, We uploaded Synergy (http://synergy-foss.org/) source packages to Fossology (1.4.1 rc 1) running on Linux Ubuntu 10.04. The license browser seems to work well until, when trying to view the individual file contents, Fossology shows an error message: File contents are not available in the repository. This file is unpacked from [synergy-1.3.7-Source.tar.gz] Reunpack: synergy-1.3.7-Source.tar.gz A direct link to the package is here: http://synergy.googlecode.com/files/synergy-1.3.7-Source.tar.gz After noticing the problem we tried the same thing with packages http://synergy-foss.org/nightly/synergy-1.3.7-r1041-Source.tar.gz and http://synergy-foss.org/nightly/synergy-1.3.7-Linux-i686.deb, still achieving the same results. An interesting detail was, that files with license match X11 could be viewed normally. We have also tried reunpacking, deleting and reuploading the package without success. In addition, it seems that all the other packages are working normally. --- Does anyone have any ideas how to get the file contents visible in Fossology? Of course it is possible to browse the files under a certain license locally, as the license matching information is available, but it is not very efficient. Who's Who Legal: Leading expertise at HH Partners. See detailshttp://www.hhpartners.fi/posts/whos-who-legal-leading-expertise-at-hh-partners-43.php?ref=mail. Privileged and confidential information may be contained in this message. If you are not addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, kindly notify us by reply e-mail and delete this message immediately. Thank you. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Announcing availability of Release Candidate 1 for 1.4.1
Greetings FOSSologists! The FOSSology Project is pleased to announce RC1 packages for FOSSology 1.4.1. This is a bug fix release. The list of bugs addressed in this release are herehttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.4.1product=FOSSology. Unofficial install packages on the following platforms distros are now available for download and testing: * Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.1/ * For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.1/squeeze/ ./ * For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.1/lenny/./http://fossology.org/debian/1.4.1/lenny/ * For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ * The 1.4.1 rc1 packages for rhel5/centos5 rhel6 fedora12/13/14 i386 and x86_64 platforms can be downloaded from: http://fossology.org/rpms/epel/testing/5/i386/fossology-1.4.1rc1-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/testing/5/x86_64/fossology-1.4.1rc1-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/epel/testing/6/i386/fossology-1.4.1rc1-1.el6.i686.rpm -- rhel6 i386 http://fossology.org/rpms/epel/testing/6/x86_64/fossology-1.4.1rc1-1.el6.x86_64.rpm --- rhel6 x86_64 http://fossology.org/rpms/fedora/testing/12/i386/fossology-1.4.1rc1-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/testing/12/x86_64/fossology-1.4.1rc1-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/testing/13/i386/fossology-1.4.1rc1-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/testing/13/x86_64/fossology-1.4.1rc1-1.fc13.x86_64.rpm --- fedora13 x86_64 http://fossology.org/rpms/fedora/testing/14/i386/fossology-1.4.1rc1-1.fc14.i686.rpm --- fedora14 i386 http://fossology.org/rpms/fedora/testing/14/x86_64/fossology-1.4.1rc1-1.fc14.x86_64.rpm --- fedora14 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 4. yum --enablerepo=fossology-testing install fossology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] 1.2.1 to 1.4?
Hi Michael, We have not tested this. To be safe, I would do as this fossology (rpm) user proposed: I'll backup the database (filesystem level backup plus a dump of the database. Then can I simply perform an rpm -Uvh fossology-1.3.0-1.el5.x86_64.rpm followed by a rpm -Uvh fossology-1.4.0-1.el5.x86_64.rpm Also, Be sure to start the scheduler after upgrade #1. Bring up the UI and browse your repository to verify all is well before proceeding with the 1.4.0 upgrade. Please let us know how it goes. Thanks, Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Fay Michael T Sent: Tuesday, May 31, 2011 8:49 AM To: 'fossology@fossology.org' Subject: [FOSSology] 1.2.1 to 1.4? Has upgrading from 1.2.1 to 1.4 been tested? Or do you really need to go to 3 and then to 4? ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Cygwin Analysis causing scheduler restarts
Did your disk fill up? Take a look at the log file to see if you can identify what was being processed when the scheduler died. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Westphal, Raymond W Sent: Monday, May 23, 2011 6:32 AM To: fossology@fossology.org Subject: [FOSSology] Cygwin Analysis causing scheduler restarts Importance: High Good Morning Everyone. On Friday my customer uploaded Cygwin for analysis. I think it was a zip file. The job ran from 11:23am until I deleted it at around 8am on Sunday. I had to delete it because it caused Fossology scheduler to keep restarting. And that was causing the load average on the server to slowly climb. Has anyone had any experience with analyzing Cygwin? Any suggestions, please? Thanks, Thanks, Ray W. CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Cygwin Analysis causing scheduler restarts
Hi Ray, Thanks for telling us about the missing RHEL5 packages. They're there now :) When I've seen this type of behavior log file messaging, it usually means the unpack was not responding to the scheduler because it was having trouble unpacking a particular file OR the db was having difficulty processing the requests resulting for the unpack. The postgresql log file might have more clues. BTW, did you turn on autovacuum as we discussed last week? Upgrading (rpm -Uvh) is probably the fastest way around this current problem. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Westphal, Raymond W Sent: Monday, May 23, 2011 8:46 AM To: fossology@fossology.org Subject: Re: [FOSSology] Cygwin Analysis causing scheduler restarts Good Morning Bob/Good Morning Mary. Here is the info. from the log just prior to where the scheduler started its cycle of not responding and then restarting. 2011-05-20 13:51:46 scheduler[8691] : Child[1] 'agent=unpack host=localhost ' state=FREEING(2) @ Fri May 20 13:51:46 2011 2011-05-20 13:51:46 scheduler[8691] : Child[1] 'agent=unpack host=localhost ' state=FREE(1) @ Fri May 20 13:51:46 2011 2011-05-20 13:51:48 scheduler[8691] : Child[2] 'agent=adj2nest host=localhost ' state=SPAWNED(4) @ Fri May 20 13:51:48 2011 2011-05-20 13:51:48 scheduler[8691] : Child[2] 'agent=adj2nest host=localhost ' state=READY(5) @ Fri May 20 13:51:48 2011 2011-05-20 13:57:42 scheduler[8693] : *** Scheduler not responding: killing and restarting *** 2011-05-20 13:57:42 scheduler[8693] : *** Exiting fossology-scheduler PID 8691 QUIT *** 2011-05-20 13:58:46 scheduler[8693] : *** Scheduler restarted successfully by fo_watchdog *** 2011-05-20 13:58:46 scheduler[13944] : Log opened 2011-05-20 13:58:46 scheduler[13944] : Scheduler started. Build version: 1.2.1~3507, exported. I don't know of any resource issues. Disk did not fill up although it grew to 93% with about 2.5GB remaining. I think the ununpack completed. CPU and memory were apparently not an issue. The load average did start to climb slowly after the scheduler kept failing. I think the restarts of the scheduler leave select queries running and generates new queries. So when you watch top you can see the 4 or 5 select queries as the top processes. Bob - I presume your system is running 1.4.0. Can I do an rpm -Uvh to the 1.3.0 Fossology? I noticed the 1.4.0 rpm is for Red Hat 6. We are not running any Red Hat 6 yet. You think the 1.4.0 rpm will run on Red Hat 5? Thanks for the quick response. Ray W. From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Monday, May 23, 2011 9:22 AM To: Westphal, Raymond W Cc: fossology@fossology.org Subject: Re: [FOSSology] Cygwin Analysis causing scheduler restarts Importance: High Hi Ray, I just grabbed the source from the cygwin cvs, tared and uploaded it. On the system I used it took 7 minutes. http://repo.fossology.org/simpleIndex.php?mod=nomoslicenseshow=detailupload=148item=50608165 We have seen the scheduler problem you describe before. I think, as long as you aren't hitting some system resource, stopping the scheduler and restarting it might take care of the problem (btw, v2.0 has a new scheduler). Bob On May 23, 2011, at 6:31 AM, Westphal, Raymond W wrote: On Friday my customer uploaded Cygwin for analysis. I think it was a zip file. The job ran from 11:23am until I deleted it at around 8am on Sunday. I had to delete it because it caused Fossology scheduler to keep restarting. And that was causing the load average on the server to slowly climb. Has anyone had any experience with analyzing Cygwin? CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FW: FOSSology 1.4.0 release announcement
Please note corrections to yum configuration. Thanks Vincent! From: Ma, Dong (Vincent, ES-Best-Shore-Services-China-BJ) Sent: Thursday, May 19, 2011 5:20 PM To: Laser, Mary Subject: RE: FOSSology 1.4.0 release announcement Hi Mary, The yum repository should not use the testing repo, use the release repo: Rhel/CentOS repo file need add following lines: #FOSSology releases [fossology] name=Fossology releases baseurl=http://fossology.org/rpms/epel/$releasever/$basearch enabled=1 gpgcheck=0 Fedora repo file need add following lines: #FOSSology releases [fossology] name=Fossology releases baseurl=http://fossology.org/rpms/fedora/$releasever/$basearch enabled=1 gpgcheck=0 yum install fossology I have updated the wiki page: http://fossology.org/installing_fossology_with_rpm_s Vincent To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 release announcement
Greetings FOSSologists! The FOSSology Project is pleased to announce the release of FOSSology 1.4.0. Unofficial install packages on the following platforms distros are now available for download and install: · Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ · The 1.4.0 release rpm packages for rhel5/centos5 rhel6 fedora12/13/14 i386 and x86_64 platforms can be downloaded from http://fossology.org/rpms/: http://fossology.org/rpms/epel/5/i386/fossology-1.4.0-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/5/x86_64/fossology-1.4.0-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/epel/6/i386/fossology-1.4.0-1.el6.i686.rpm -- rhel6 i386 http://fossology.org/rpms/epel/6/x86_64/fossology-1.4.0-1.el6.x86_64.rpm --- rhel6 x86_64 http://fossology.org/rpms/fedora/12/i386/fossology-1.4.0-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/12/x86_64/fossology-1.4.0-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/13/i386/fossology-1.4.0-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/13/x86_64/fossology-1.4.0-1.fc13.x86_64.rpm --- fedora13 x86_64 http://fossology.org/rpms/fedora/14/i386/fossology-1.4.0-1.fc14.i686.rpm --- fedora14 i386 http://fossology.org/rpms/fedora/14/x86_64/fossology-1.4.0-1.fc14.x86_64.rpm --- fedora14 x86_64 Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 Release Candidate 7
Greetings FOSSologists! The FOSSology Project is pleased to announce RC7 packages for FOSSology 1.4.0. Unofficial install packages on the following platforms distros are now available for download and testing: § Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ § RPM Packages (rhel5/centos5, rhel6/centos6, fedora12, fedora13, fedora14 for i386 and x86_64) http://fossology.org/rpms/ Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] RHEL 5 rpms?
Thanks for asking! We are in the process of stress testing our stable top of trunk to see if it's ready to become our next release candidate (RC7). So far, the tests look good. We have a developers meeting scheduled in a few hours. As long as the tests remain error free, I will ask our Beijing team to create the RC7 RPMs and they should be available in the next 12 hours. Please send us your feedback on the rpm install/update experience. Thanks, Mary Laser The FOSSology Project http://fossology.org -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Fay Michael T Sent: Thursday, May 12, 2011 12:49 PM To: 'fossology@fossology.org' Subject: [FOSSology] RHEL 5 rpms? Any idea when the RHEL 5 rpms for 1.4 will be ready? I looked today and didn't see one. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FW: New rpm packages for 1.4.0rc7 avaiable
Thank You Vincent! From: Ma, Dong (Vincent, ES-Best-Shore-Services-China-BJ) Sent: Thursday, May 12, 2011 7:04 PM To: Laser, Mary Subject: New rpm packages for 1.4.0rc7 avaiable Hi Mary, The 1.4.0 rc7 packages for rhel5/centos5 rhel6 fedora12/13/14 i386 and x86_64 platform are built. You can download from http://fossology.org/rpms/epel/testing/5/i386/fossology-1.4.0rc7-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/testing/5/x86_64/fossology-1.4.0rc7-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/epel/testing/6/i386/fossology-1.4.0rc7-1.el6.i686.rpm -- rhel6 i386 http://fossology.org/rpms/epel/testing/6/x86_64/fossology-1.4.0rc7-1.el6.x86_64.rpm --- rhel6 x86_64 http://fossology.org/rpms/fedora/testing/12/i386/fossology-1.4.0rc7-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/testing/12/x86_64/fossology-1.4.0rc7-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/testing/13/i386/fossology-1.4.0rc7-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/testing/13/x86_64/fossology-1.4.0rc7-1.fc13.x86_64.rpm --- fedora13 x86_64 http://fossology.org/rpms/fedora/testing/14/i386/fossology-1.4.0rc7-1.fc14.i686.rpm --- fedora14 i386 http://fossology.org/rpms/fedora/testing/14/x86_64/fossology-1.4.0rc7-1.fc14.x86_64.rpm --- fedora14 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 4. yum --enablerepo=fossology-testing install fossology Notes: About Rhel6 packages, 1 dependency php-process not available in rhel default repository. You can download 1 copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html Vincent Ma ( 马冬 ) Best Shore Services China BJ HP Enterprise Services Telephone: +86 18610023880 IDD: +8610 65646766 Email: dong...@hp.commailto:dong...@hp.com [cid:image001.png@01CC114B.A743A770] inline: image001.png___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 Release Candidate 5
Greetings FOSSologists! The FOSSology Project is pleased to announce RC5 deb packages for FOSSology 1.4.0. Unofficial install packages on the following platforms distros are now available for download and testing: § Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ RPM packages will be available later this week (Thursday, 5/5/2011) from the project website: § RPM Packages (rhel5/centos5, rhel6/centos6, fedora12, fedora13, fedora14 for i386 and x86_64) http://fossology.org/rpms/ Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Documentation Updates for Fossology Release 1.4.0
Add to the needs update list; any page referencing GlobalSearch, E.g. http://fossology.org/config:how_to_configure_the_fossology_site This FOSSology system config variable has been removed. From: fossology-devel-boun...@fossology.org [mailto:fossology-devel-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Tuesday, April 26, 2011 5:54 PM To: fossology-de...@fossology.org; fossology@fossology.org Subject: [FOSSology-devel] Documentation Updates for Fossology Release 1.4.0 Hi FOSSologists, I 'm reviewing our pages on the fossology.org website to determine where we need to add new content, update pages and reorganize pages. I'd love to hear your thoughts and feedback on this subject, too. Is there something we're missing? Do you know of an out of date page that needs updating or obsolescing? Here is a list of what we've done (or plan to do), so far: New pages: http://fossology.org/release_notes 1.4.0 release notes added http://fossology.org/config:sysconfvariables developer notes for new fossology system config variables http://fossology.org/admin:timeouts discussion of session timeouts http://fossology.org/config:how_to_configure_the_fossology_site User docs for customizing the UI http://fossology.org/altui:alternateui User docs for new Simplified UI http://fossology.org/copyright:copyright_1.4.0 Copyright enhancements for 1.4.0 http://fossology.org/compare:comparing\ http://fossology.org/compare:licensediff 3 new docs for new compare feature http://fossology.org/compare:picker / Updated (or needs updating) pages: http://fossology.org/quickstart updated http://fossology.org/how_to_upload_files_for_analysis updated http://fossology.org/upload_from_a_file updated http://fossology.org/upload_from_a_url updated http://fossology.org/introduction_to_fossology updated http://fossology.org/customizingtips updated http://fossology.org/install updated http://fossology.org/buckets updated http://fossology.org/file_locations updated http://fossology.org/release_testing updated http://fossology.org/building_debian_packages needs update? http://fossology.org/fossology_rpm_package_process needs update Several new namespaces have been added to store our old or obsolete pages: § 0.6.1http://fossology.org/home?idx=0.6.1 § 0.9.0http://fossology.org/home?idx=0.9.0 § 1.0.0http://fossology.org/home?idx=1.0.0 § 1.1.0http://fossology.org/home?idx=1.1.0 § 1.2.0http://fossology.org/home?idx=1.2.0 § meetingshttp://fossology.org/home?idx=meetings * 2009http://fossology.org/?idx=meetings%3A2009 * 2010http://fossology.org/?idx=meetings%3A2010 * old_release_noteshttp://fossology.org/home?idx=old_release_notes TIA for your feedback! The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Documentation Updates for Fossology Release 1.4.0
Hi FOSSologists, I 'm reviewing our pages on the fossology.org website to determine where we need to add new content, update pages and reorganize pages. I'd love to hear your thoughts and feedback on this subject, too. Is there something we're missing? Do you know of an out of date page that needs updating or obsolescing? Here is a list of what we've done (or plan to do), so far: New pages: http://fossology.org/release_notes 1.4.0 release notes added http://fossology.org/config:sysconfvariables developer notes for new fossology system config variables http://fossology.org/admin:timeouts discussion of session timeouts http://fossology.org/config:how_to_configure_the_fossology_site User docs for customizing the UI http://fossology.org/altui:alternateui User docs for new Simplified UI http://fossology.org/copyright:copyright_1.4.0 Copyright enhancements for 1.4.0 http://fossology.org/compare:comparing\ http://fossology.org/compare:licensediff 3 new docs for new compare feature http://fossology.org/compare:picker / Updated (or needs updating) pages: http://fossology.org/quickstart updated http://fossology.org/how_to_upload_files_for_analysis updated http://fossology.org/upload_from_a_file updated http://fossology.org/upload_from_a_url updated http://fossology.org/introduction_to_fossology updated http://fossology.org/customizingtips updated http://fossology.org/install updated http://fossology.org/buckets updated http://fossology.org/file_locations updated http://fossology.org/release_testing updated http://fossology.org/building_debian_packages needs update? http://fossology.org/fossology_rpm_package_process needs update Several new namespaces have been added to store our old or obsolete pages: § 0.6.1http://fossology.org/home?idx=0.6.1 § 0.9.0http://fossology.org/home?idx=0.9.0 § 1.0.0http://fossology.org/home?idx=1.0.0 § 1.1.0http://fossology.org/home?idx=1.1.0 § 1.2.0http://fossology.org/home?idx=1.2.0 § meetingshttp://fossology.org/home?idx=meetings * 2009http://fossology.org/?idx=meetings%3A2009 * 2010http://fossology.org/?idx=meetings%3A2010 * old_release_noteshttp://fossology.org/home?idx=old_release_notes TIA for your feedback! The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 Release Candidate 3
Greetings! Additional testing with RC2 turned up one more bug that is addressed in RC3. Barring any other critical bugs, we feel RC3 has a strong probability of becoming our Final 1.4.0 release. As always, please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. Unofficial install packages on the following platforms distros are now available for download and testing: § Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ Note: The RC3 RPMs will be built Monday (in Beijing) and available for download and install as specified below. § RPM Packages (rhel5/centos5, rhel6/centos6, fedora12, fedora13, fedora14 for i386 and x86_64) http://fossology.org/rpms/ Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 Release Candidate 4
We are backing out the changes in RC3 and replacing all Debian/Ubuntu packages with a new RC4. RC4 is a source equivalent to RC2. We will have at least one more release candidate (RC5) next week. The FOSSology Project http://fossology.orghttp://fossology.org/ Greetings! Additional testing with RC2 turned up one more bug that is addressed in RC3. Barring any other critical bugs, we feel RC3 has a strong probability of becoming our Final 1.4.0 release. As always, please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. Unofficial install packages on the following platforms distros are now available for download and testing: § Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ Note: The RC3 RPMs will be built Monday (in Beijing) and available for download and install as specified below. § RPM Packages (rhel5/centos5, rhel6/centos6, fedora12, fedora13, fedora14 for i386 and x86_64) http://fossology.org/rpms/ Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FOSSology 1.4.0 Release Candidate 1
Greetings! The FOSSology Project is pleased to announce RC1 packages for FOSSology 1.4.0. Unofficial install packages on the following platforms distros are now available for download and testing: § RPM Packages (rhel5/centos5, rhel6/centos6, fedora12, fedora13, fedora14 for i386 and x86_64) http://fossology.org/rpms/ Note for Rhel6 packages: 1 dependency, php-process, is not available from the default rhel repository. You can download a copy from: http://fossology.org/rpms/epel/testing/6/i386/php-process-5.3.2-6.el6_0.1.i686.rpm http://fossology.org/rpms/epel/testing/6/x86_64/php-process-5.3.2-6.el6_0.1.x86_64.rpm Or you need apply this update: https://rhn.redhat.com/errata/RHSA-2011-0195.html To use yum install, you need to edit the repo file, /etc/yum.repo.d/: 1. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 2. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. yum --enablerepo=fossology-testing install fossology § Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.4.0/ For debian squeeze installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/squeeze/ ./ For debian lenny installs, add this line to your sources.list deb http://fossology.org/debian/1.4.0/lenny/./ For ubuntu: deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ New features/enhancements include: § New Comparison tool. This allows one to focus on the differences between two file trees. For example, you might want to compare two versions of a package to see what licenses changed. § A new simplified User Interface AND the option to assign the Simplified or Original UI on a per user basis. § Implement authentication using Siteminder § Improved user documentation § Multiple file upload from URL § Dramatic improvements in the copyright agent. § 1.4.0 Defect Listhttp://bugs.linux-foundation.org/buglist.cgi?query_format=advancedbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDtarget_milestone=1.3.1target_milestone=1.4product=FOSSology Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list at fossology@fossology.orgmailto:fossology@fossology.org. The FOSSology Project http://fossology.orghttp://fossology.org/ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] NOMOS - how to find differences compared to license templates?
Thanks for answering this email Raino. You are right on the mark. Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Raino Lintulampi Sent: Friday, April 15, 2011 5:25 AM To: Dabrowski, Ivo Cc: fossology@fossology.org Subject: Re: [FOSSology] NOMOS - how to find differences compared to license templates? Hi Ivo, How can I find additions or deletions in the source code license texts compared to the stored license templates using NOMOS? For example, if there is an additional not included in legally critical places? As stated on your how to interpret site under Percent of Match, verification should be possible. You can't. Nomos does not use templates but short text strings from licenses. See http://www.fossology.org/nomos for further information. What could be done with nomos is similar approach as is used with copyright agent. With copyright agent you can view the identified text string location in the file. In rare cases that kind of feature would have helped when it has been unclear why nomos claimed the file to have f.ex. GPL license. (GPL reference text has been in the middle or end of the file). But that would not tell how the text in file differs from the reference license text. My experience is that nomos is working very well. Old bsam results are left in database so if you have doubt you can make comparison with bsam results and nomos results. Best regards Raino Thank you and best regards Ivo Dabrowski ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] swap space
Hi Ray, There are at least 2 reasons why swap usage is going up over time; 1. there is a memory leak - in this case, restarting the scheduler will free up the space. However, we are not aware of any memory leaks in the version you're running. 2. Prior to 1.3.0, the method for processing files used increasing amounts of memory as the number of files/upload grew. This resulted in the behavior you describe. This method was changed in 1.3.0 to address this memory scalability problem. I think you may be running into this problem, since you are running an older version of FOSSology. To answer your questions, 1. No, you should not need to restart your scheduler regularly (unless there is an unknown memory leak). 2. Jobs in the queue will be restarted from the beginning, when the scheduler is restarted. 3. It would be good to know which jobs (if any) are running when this occurs. Through the UI, you can click on Admin - Scheduler - Status to see what jobs are running. 4. In addition to the UI instructions above, you can also look at the queue via Jobs - Queue - Details HTH, Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Westphal, Raymond W Sent: Thursday, April 07, 2011 7:07 AM To: fossology@fossology.org Subject: [FOSSology] swap space Good Morning. We have a monitor script running on our servers for things like filesystem, load average, swap space usage, etc. Yesterday I received an alert because the swap space usage on our Fossology server had reached 85%. I discovered that the scheduler was using the most virtual memory. I stopped and started the scheduler and the swap usage dropped to 13%. I'll probably increase the swap space. (Our Fossology server is running 1.2.1-3507 and it has 1.5GB of memory, 1GB of swap and 2 AMD 2800Mhz CPUs.) And so I have the following questions: Should I reset the scheduler regularly? If I reset the scheduler will jobs in the queue be lost? Should I check the queue before I reset the scheduler? If I need to check the queue, can you provide the query, please? Thanks, Ray W. CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Next Version?
Hi Ray, The next FOSSology release (1.4.0) is being functionally tested by the development team now. After this, we will begin package and install/update testing. Typically, our update testing consists of updating from the previous version to the new version. For this next release, that would be testing the upgrade path from 1.3.0 to 1.4.0. Since you are asking specifically about the 1.2.1 to 1.4.0 upgrade path, we can add this to our list as an opportunistic test goal. Mary Mary Laser The FOSSology Project http://fossology.orghttp://fossology.org/ From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Westphal, Raymond W Sent: Wednesday, March 23, 2011 10:01 AM To: fossology@fossology.org Subject: [FOSSology] Next Version? Hello Bob. I noticed In the next version (1.4) ... in the last post. I just recently upgraded 1.2.1. When will 1.4 be available and will I be able to go directly from 1.2.1 to 1.4? Thanks, Ray Westphal. CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] License Identifiers - FOSSology SPDX
Yes! We are closely following evolution of the SPDX standard. We will eventually align FOSSology to adopt the standard. Mary Mary Laser The FOSSology Project http://fossology.org -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Roger Meier Sent: Wednesday, March 23, 2011 4:07 PM To: fossology@fossology.org; s...@fossbazaar.org Subject: [FOSSology] License Identifiers - FOSSology SPDX Hi all I'm interested in using FOSSology and the SPDX standard for future projects. It would be great to have at least one well supported open source software solution like FOSSology which is using the SPDX standard. This will help all of us to be license compliant and economic whenever we use open source software. However, SPDX is still in definition phase and it probably does not fit perfectly to FOSSology. The license meta data is a very important thing required to automate license analysis and that's the place where I've identified a mismatch, the license short name or license identifier. FOSSology has some very nice metadata for each license, e.g. Date: 2004-01-01 00:00:00 URL: http://www.apache.org/licenses/LICENSE-2.0.txt shortname: ASL v2.0 fullname: Apache Software License v2.0 OSIapproved: Yes FSFfree: Yes GPLv2compatible: No GPLv3compatible: Yes copyleft: No notes: for further details see http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/a gents /license_files/Apachev2.0.meta?revision=HEADview=markup SPDX is using its own license identifier: Full name of License: Apache License 2.0 License Identifier: Apache-2 Source/URL: http://www.apache.org/licenses/LICENSE-2.0 Notes: This version was released: January 2004, This license is OSI certified for further details see http://www.spdx.org/wiki/working-version-license-list Are there any plans to align these identifiers? Does somebody know some other standards used for license meta data? -roger ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Help Deciphering Report
Hi SpottedOtter, It looks like the downloaded file was not unpacked. Did you see any errors in the log file (/var/log/fossology/fossology.log) indicating problems with unpack? I will try it on a 1.3.0 system (from http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.3.tar.gz) and see if I can duplicate your results. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of valerie duncan Sent: Thursday, February 17, 2011 11:50 AM To: fossology@fossology.org Subject: [FOSSology] Help Deciphering Report Hello. Attached please see report generated from a scan. We understand the list of licenses found. We were surprised at the rest of the report. Why do we not get just the nice report? What are we missing? Thanks for your help. SpottedOtter ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Help Deciphering Report
Hello again, I was able to download, unpack and analyze nagios-3.2.3.tar.gz on 3 systems (2 are running FO 1.3.0 and the other is a test system running ToT). They all had the same successful result. Which filetype does your FOSSology attribute to nagios-3.2.3.tar.gz? (Use the Info micromenu.) You should see something like Meta Data Item Meta Data Value 1 Unpacked file type application/x-gzip From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Thursday, February 17, 2011 1:17 PM To: valerie duncan; fossology@fossology.org Subject: Re: [FOSSology] Help Deciphering Report Hi SpottedOtter, It looks like the downloaded file was not unpacked. Did you see any errors in the log file (/var/log/fossology/fossology.log) indicating problems with unpack? I will try it on a 1.3.0 system (from http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.2.3.tar.gz) and see if I can duplicate your results. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of valerie duncan Sent: Thursday, February 17, 2011 11:50 AM To: fossology@fossology.org Subject: [FOSSology] Help Deciphering Report Hello. Attached please see report generated from a scan. We understand the list of licenses found. We were surprised at the rest of the report. Why do we not get just the nice report? What are we missing? Thanks for your help. SpottedOtter ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] dutch language file
This is wonderful Jeroen. Dank je wel! Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Jeroen Baten Sent: Tuesday, February 15, 2011 3:14 AM To: fossology@fossology.org Subject: [FOSSology] dutch language file Hi, It took me 1,5 days of hard work, but here is the language file for the nl_NL locale. greets, Jeroen Baten ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails Package Scan
The fix for the bug referenced below (#596) is in 1.3.0. However, I don't think that bug is the same problem Jeroen is having, based on what I see below. The problem description for #596 includes: On fedora/rhel system, ununpack agent get the wrong mimetype for debian binary package, it set debian binary packages as application/x-7z-w-compressed, so pkgagent didn't process these debian binary packages and cannot get the package info. The problem below shows the pkgagent dying. Mary -Original Message- From: Gobeille, Robert Sent: Friday, February 11, 2011 7:23 AM To: Jeroen Baten; Laser, Mary Cc: fossology@fossology.org Subject: Re: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails Package Scan This was supposed to be fixed on January 13. http://bugs.linux-foundation.org/show_bug.cgi?id=596 1.3.0 was released January 19. Mary, did this fix get into 1.3.0? Bob Gobeille On Feb 11, 2011, at 1:47 AM, Jeroen Baten wrote: Don't know if this helps, but this is a relevant piece of the log: 2011-02-10 13:42:27 scheduler[716] : Child[15] 'agent=pkgagent host=localhost ' state=SPAWNED(4) @ Thu Feb 10 13:42:27 2011 2011-02-10 13:42:27 scheduler[716] : Child[15] 'agent=pkgagent host=localhost ' state=READY(5) @ Thu Feb 10 13:42:27 2011 2011-02-10 13:42:27 scheduler[716] : Child[6] 'agent=buckets host=localhost ' state=FREE(1) @ Thu Feb 10 13:42:27 2011 2011-02-10 13:45:52 scheduler[716] : ERROR: Child[15] died prematurely (was state RUNNING, signal was 11) 2011-02-10 13:45:52 scheduler[716] : Thread 15: 2011-02-10 13:45:52 scheduler[716] : PID: 1736 2011-02-10 13:45:52 scheduler[716] : Pipes: in=8-9 / out=13- 12 2011-02-10 13:45:52 scheduler[716] : Attr: 'agent=pkgagent host=localhost ' 2011-02-10 13:45:52 scheduler[716] : Command: '/usr/local/lib/fossology/agents/pkgagent' 2011-02-10 13:45:52 scheduler[716] : Parm: 'pfile_pk=87202 pfilename=BE9651C3D92B8A76FD3D0C03FF5597411E8FF860.A0FD8E3774FED62ABEB 6C2CDA3362862.2639 mimetype=application/x-rpm ' 2011-02-10 13:45:52 scheduler[716] : Heartbeat: Thu Feb 10 13:45:42 2011 2011-02-10 13:45:52 scheduler[716] : State: Thu Feb 10 13:45:42 2011 2011-02-10 13:45:52 scheduler[716] : Status: 6 (RUNNING) 2011-02-10 13:45:52 scheduler[716] : Spawn: 1 at Thu Feb 10 13:42:27 2011 2011-02-10 13:45:52 scheduler[716] : DB: 2011-02-10 13:45:52 scheduler[716] : IsDB: 2 2011-02-10 13:45:52 scheduler[716] : DBJobKey: 128 2011-02-10 13:45:52 scheduler[716] : DBMSQrow: 1 2011-02-10 13:45:52 scheduler[716] : DBagent: 29 2011-02-10 13:45:52 scheduler[716] : Child[15] 'agent=pkgagent host=localhost ' state=FREEING(2) @ Thu Feb 10 13:45:52 2011 2011-02-10 13:45:52 scheduler[716] : Child[15] 'agent=pkgagent host=localhost ' state=FREE(1) @ Thu Feb 10 13:45:52 2011 On Thu, 2011-02-10 at 11:37 -0700, Bob Gobeille wrote: Hi Jeroen, The best place to see why an agent failed is in the fossology log file (/var/log/fossology/fossology.log). If you look there and see a spawning too fast error, that is a known (major) bug. See: http://bugs.linux-foundation.org/show_bug.cgi?id=636 If it is something different than what is in the bug report, please let us know. Thanks, Bob Gobeille ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Can fossology 1.3 be installed on RHEL5 64 bit Linux?
Hi Edward, I have not done a RHEL5 install. However, I did find this note in the support matrix indicating it is in progress http://fossology.org/download#supported_distro_s: RHEL 5.X in progress for 1.3.0, in general need to get some rpms from other sources see Installing FOSSologyhttp://fossology.org/rhel5_1.1. It appears you need to get additional RPMs (libmagic and libextractor) from other sources :(. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Edward Judge Sent: Wednesday, February 09, 2011 3:39 PM To: fossology@fossology.org Subject: [FOSSology] Can fossology 1.3 be installed on RHEL5 64 bit Linux? I am a fossology newbie and wanted to make sure that this was a supported install. I think I have setup my yum repository properly but when I go to install fossology I get the following error: [root@ejudgerhl local_repo]# yum install fossology Loaded plugins: installonlyn, rhnplugin Setting up Install Process Parsing package install arguments Resolving Dependencies -- Running transaction check --- Package fossology.x86_64 0:1.3.0-1.el5 set to be updated -- Processing Dependency: postgresql = 8.1.11 for package: fossology -- Processing Dependency: postgresql-server = 8.1.11 for package: fossology -- Processing Dependency: php-pear = 5.16 for package: fossology -- Processing Dependency: php-pgsql = 5.1.6 for package: fossology -- Processing Dependency: php = 5.1.6 for package: fossology -- Processing Dependency: /usr/bin/php for package: fossology -- Processing Dependency: p7zip-plugins for package: fossology -- Processing Dependency: poppler-utils for package: fossology --- Package fossology.i386 0:1.2.0-1.el5 set to be updated -- Processing Dependency: libmagic.so.1 for package: fossology -- Processing Dependency: libextractor.so.1 for package: fossology -- Processing Dependency: p7zip for package: fossology -- Running transaction check --- Package postgresql-server.x86_64 0:8.1.23-1.el5_6.1 set to be updated --- Package p7zip.x86_64 0:9.13-1.el5.rf set to be updated --- Package php-pear.noarch 1:1.4.9-6.el5 set to be updated -- Processing Dependency: php-devel for package: php-pear --- Package php-cli.x86_64 0:5.1.6-27.el5_5.3 set to be updated -- Processing Dependency: php-common = 5.1.6-27.el5_5.3 for package: php-cli --- Package p7zip-plugins.x86_64 0:9.13-1.el5.rf set to be updated --- Package postgresql.x86_64 0:8.1.23-1.el5_6.1 set to be updated --- Package php-pgsql.x86_64 0:5.1.6-27.el5_5.3 set to be updated -- Processing Dependency: php-pdo for package: php-pgsql --- Package fossology.i386 0:1.2.0-1.el5 set to be updated -- Processing Dependency: libmagic.so.1 for package: fossology -- Processing Dependency: libextractor.so.1 for package: fossology --- Package poppler-utils.x86_64 0:0.5.4-4.4.el5_5.14 set to be updated -- Processing Dependency: poppler = 0.5.4-4.4.el5_5.14 for package: poppler-utils --- Package php.x86_64 0:5.1.6-27.el5_5.3 set to be updated -- Running transaction check --- Package php-common.x86_64 0:5.1.6-27.el5_5.3 set to be updated --- Package php-devel.x86_64 0:5.1.6-27.el5_5.3 set to be updated --- Package php-pdo.x86_64 0:5.1.6-27.el5_5.3 set to be updated --- Package fossology.i386 0:1.2.0-1.el5 set to be updated -- Processing Dependency: libmagic.so.1 for package: fossology -- Processing Dependency: libextractor.so.1 for package: fossology --- Package poppler.x86_64 0:0.5.4-4.4.el5_5.14 set to be updated -- Finished Dependency Resolution fossology-1.2.0-1.el5.i386 from localrepo has depsolving problems -- Missing Dependency: libextractor.so.1 is needed by package fossology-1.2.0-1.el5.i386 (localrepo) fossology-1.2.0-1.el5.i386 from localrepo has depsolving problems -- Missing Dependency: libmagic.so.1 is needed by package fossology-1.2.0-1.el5.i386 (localrepo) Error: Missing Dependency: libmagic.so.1 is needed by package fossology-1.2.0-1.el5.i386 (localrepo) Error: Missing Dependency: libextractor.so.1 is needed by package fossology-1.2.0-1.el5.i386 (localrepo) [root@ejudgerhl local_repo]# yum repolist Loaded plugins: installonlyn, rhnplugin repo id repo namestatus fossologyFossology releases enabled : 7 localrepoFedora Core 5Client - My Local Repo enabled : 6 rhel-debuginfo Red Hat Enterprise Linux 5Client - x86_6 enabled : 4,370 rhel-x86_64-client-5 Red Hat Enterprise Linux Desktop (v. 5 f enabled : 8,182 rhel-x86_64-client-w RHEL Desktop Workstation (v. 5 for 64-bi enabled : 4,576 repolist: 17,141 [root@ejudgerhl local_repo]# ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] 1.3.0 Install issues
Hi Dave, You will need to remove or rename the directory below to get around this error. /usr/bin/install: cannot overwrite directory `/usr/local/lib/fossology/agents/copyright' with non-directory make[2]: *** [install] Error 1 Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Dave McLoughlin Sent: Tuesday, February 08, 2011 12:14 PM To: fossology@fossology.org Subject: [FOSSology] 1.3.0 Install issues I completed the upgrade from 1.1 to 1.2.1 this morning and the install worked fine. I was able to view all existing scans in my database. And I ran a new sample scan and it worked fine. I just attempted to upgrade to 1.3.0 and saw a few errors. I was wondering if you can help me debug. during the make install, I'm seeing: make[2]: Entering directory `/home/dave/fossology-1.3.0/agents/copyright' /usr/bin/install -D copyright /usr/local/lib/fossology/agents/ /usr/bin/install: cannot overwrite directory `/usr/local/lib/fossology/agents/copyright' with non-directory make[2]: *** [install] Error 1 make[2]: Leaving directory `/home/dave/fossology-1.3.0/agents/copyright' make[1]: *** [install-copyright] Error 2 make[1]: Leaving directory `/home/dave/fossology-1.3.0/agents' make: *** [install-agents] Error 2 Then when I run the fossology-scheduler test it fails: $ sudo /usr/local/lib/fossology/fossology-scheduler -t Exec failure reason: Permission denied *** StopScheduler DELETE from scheduler_status. Status , *** Logs say: 2011-02-08 12:06:05 scheduler[18844] : STATUS: 1 agents failed to initialize. 2011-02-08 12:06:05 scheduler[18844] : *** 1 agent failures. Scheduler exiting. Any help would be appreciated. Dave ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology 1.3.0 RHEL5 64-bit Dependency Question
I've been under the impression all dependencies are included with the packages we build. However, the install page (http://fossology.org/installing_fossology_with_rpm_s) doesn't say that explicitly. I know this was NOT the case with the previous release (as documented here: http://fossology.org/rhel5_1.1#installing_fossology_dependencies). Rando is checking now... Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of vdunca...@gmail.com Sent: Tuesday, February 08, 2011 1:50 PM To: fossology@fossology.org Subject: [FOSSology] Fossology 1.3.0 RHEL5 64-bit Dependency Question Does the Fossology 1.3.0 RHEL5 64-bit rpm contain the upstream dependencies such as libextractor, Sleuthkit, etc? ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Notes from our weekly FO team meeting posted...
http://fossology.org/2011.02.04 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] RFC: Bug 235 - compare license text for packages that change version
Hello FOSSology users developers, I've been updating and closing FOSSOlogy bugs in our bugzilla tracking tool (hosted by The Linux Foundation at http://bugs.linux-foundation.org/) and came across this very old enhancement request to compare license text for packages that change version, http://bugs.linux-foundation.org/show_bug.cgi?id=235. A variation of this request will be addressed by the difference toolhttp://fossology.org/difference_tool, currently under development for our next release (1.3.1). The new feature will identify License Differenceshttp://fossology.org/compare:comparing#license_differences between 2 files/packages. Does the new difference tool adequately address the bug request? If so, I will note this in the bug and set the target release for this request to 1.3.1. If not, the request needs to be refined and prioritized to build into a future release. Please let me know your thoughts. Thanks, Mary Mary Laser Open Source Program Office Hewlett Packard 970-898-0878 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Announcing FOSSology 1.3.0 Release
The FOSSology Project is pleased to announce the release of FOSSology 1.3.0. New in version 1.3.0: 1. Groups. Implemented user groups inside of fossology as an indirect but critical requirement for 1.3 because tagging (the real 1.3 requirement) is dependent on having groups to administer tag permissions. 2. File Tagging. The ability to attach a tag (short (max 32 character) tag, plus a long text) to a file or container. 3. Copyright agent replaced. A quick experiment showed that we get better results with simple heuristics rather than the old agent based on naive Bayes. 4. Fixed a cp2foss authentication bug that prevented bucket agent from getting scheduled. 5. Improvements to unpack agent. 6. Many bug fixes! For more information on the FOSSology project and to download the software, please visit http://fossology.org/. Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list. -- About FOSSology -- FOSSology is a Free Open Source Software (FOSS) project built around an open architecture for analyzing software. Existing modules include license analysis, Copyright/Email/URL scanner, analysis of deb and rpm packages. This open source software tool analyzes a given set of software packages, and reports items such as the software licenses used by these packages. More than simply reporting, Package X uses license Y, the FOSSology tool attempts to analyze every file within the package to determine its license. The license report is thus an aggregate of all of the different licenses found to be in use by a package. A single package may be labeled as GPL but contain files that use other licenses (BSD, OSL, or any of the hundreds of other licenses). Even if an exact license is unknown, the license may be identifiable by common license phrases. The FOSSology Project started as an internal software development effort within Hewlett Packard's Open Source and Linux Organization. The tool evolved over several years at HP from a few simple shell scripts to the much more comprehensive tool you see today. Enjoy! The FOSSology team ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] New release candidate for FO 1.3.0 now available
Greetings! The FOSSology Project is pleased to announce RC2 packages for FOSSology 1.3.0. Per the attachments, unofficial install packages on the following platforms distros are available for download: * RPM Packages (rhel5/centos5 fedora12 fedora13 i386 and x86_64) http://fossology.org/rpms/ (Please refer to the attached instructions to configure your system to use yum for installing the FOSSology packages.) * Debian/Ubuntu Packages (amd64 i386) http://fossology.org/debian/1.3.0-rc2/ For debian installs, add this line to your sources.list deb http://fossology.org/debian/1.3.0-rc2/ ./ For ubuntu deb http://fossology.org/debian/ubuntu/karmic/ ./ deb http://fossology.org/debian/ubuntu/lucid/ ./ deb http://fossology.org/debian/ubuntu/maverick/ ./ New features/enhancements include: 1. Groups. Implemented user groups inside of fossology as an indirect but critical requirement for 1.3 because tagging (the real 1.3 requirement) is dependent on having groups to administer tag permissions. 2. File Tagging I. The ability to attach a tag (short (max 32 character) tag, plus a long text) to a file or container. II. Tagging requires permission for creating, attaching, and viewing tags which is why we have a dependency on groups. 3. Copyright agent replaced. A quick experiment showed that we get better results with simple heuristics rather than the old agent based on naive Bayes. 4. Fixed a cp2foss authentication bug that prevented bucket agent from getting scheduled. 5. Many bug fixes! Please report bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list. Thanks, The FOSSology Project ---BeginMessage--- Hi Mary, The 1.3.0rc2 packages for rhel5/centos5 fedora12 fedora13 i386 and x86_64 platform are rebuilt. You can download from http://fossology.org/rpms/epel/testing/5/i386/fossology-1.3.0rc2-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/testing/5/x86_64/fossology-1.3.0rc2-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/fedora/testing/12/i386/fossology-1.3.0rc2-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/testing/12/x86_64/fossology-1.3.0rc2-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/testing/13/i386/fossology-1.3.0rc2-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/testing/13/x86_64/fossology-1.3.0rc2-1.fc13.x86_64.rpm --- fedora13 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 4. yum --enablerepo=fossology-testing install fossology Vincent Ma ( 马冬 ) Best Shore Services China BJ HP Enterprise Services Telephone: +86 18610023880 IDD: +8610 65645733 Email: dong...@hp.commailto:dong...@hp.com Description: cid:image001.png@01CAB6FE.113D0300 inline: image001.png---End Message--- ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Undefined Variables
Hi Ray, Release notes for version 1.2.1 are on our project website at http://fossology.org/release_notes. We typically don't include every single code change in the notes, but try to highlight the big changes. You can look at every subversion checkin on the sourceforge site at http://fossology.svn.sourceforge.net/viewvc/fossology/. You might want to start in tags. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Westphal, Raymond W Sent: Thursday, January 06, 2011 10:28 AM To: fossology@fossology.org Subject: Re: [FOSSology] Undefined Variables Importance: High Thanks for the response Bob. I have a somewhat related question. Are these and other code changes (fixes or removals) incorporated into the 1.2.1 install rpm at some time? Are they included in a 1.2.2 install rpm? Thanks, Ray W. From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Thursday, January 06, 2011 11:16 AM To: Westphal, Raymond W Cc: fossology@fossology.org Subject: Re: [FOSSology] Undefined Variables Hi Ray, It bothered me when I read you initial email because I thought I'd cleaned up almost all the code that generated php notices and I was surprised I missed this. The reason I missed it is because that code is only executed for bsam licenses, which I never use since we replaced it with the nomos scanner. So I'd rather remove the code than bother to clean it up. One thing we have received very little feedback on is the switch from bsam to nomos. This has surprised me. I wonder what will happen when we remove all the bsam code. Then none of the bsam results will be accessible. Bob Gobeille On Jan 6, 2011, at 7:41 AM, Westphal, Raymond W wrote: Thanks for your response Bob. Happy New Year! Ray W. From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Wednesday, January 05, 2011 6:14 PM To: Westphal, Raymond W Cc: fossology@fossology.orgmailto:fossology@fossology.org; Lancaster, Michael J Subject: Re: [FOSSology] Undefined Variables Hi Ray, Sorry for the late response. I've been enjoying the holidays. ;-) The PHP notices are benign. I have been trying to clean them up as I see them. So thanks. I'll take care of these. A quick fix is to configure your php.ini file to not report them. php.ini has a variable to set the reporting level called error_reporting: error_reporting = E_ALL | E_STRICT You could change this to: error_reporting = E_ALL ~E_NOTICE I'll fix the code tomorrow. To understand the differences in the number of licenses, you have to compare which ones were found. The new nomos scanner is much more accurate that the old bsam scanner, but there are differences in the way the licenses are reported. So you really have to look at the two license lists to see if 1.2.1 is missing something or 1.1.0 is reporting false positives. Thanks, Bob Gobeille On Dec 21, 2010, at 10:51 AM, Westphal, Raymond W wrote: Hello All. My users are comparing the 1.1.0 product to the 1.2.1 product by uploading files to each server. They noticed a difference in the analysis of antlr-3.2.jar. To quote: The old said there were 69 licenses id'd. The new said 64 licenses were id'd. During the test we noticed 924 PHP Notice events in the web server logs for Undefined variable. For example: PHP Notice: Undefined variable: Max in /webroot/www/common/common-license.php on line 446, PHP Notice: Undefined variable: Offset in /webroot/www/common/common-license.php on line 441, Is there an easy fix for the undefined variables in the common-license.php file? Would the Undefined variable cause the difference in the number of licenses identified? Thanks, Ray W. CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system. ATT1..txt ATT1..txt ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Test packages for FO 1.3.0 now available
Greetings Happy New Year! The FOSSology Project is pleased to announce availability of test packages for FOSSology 1.3.0. Per the attachments, unofficial install packages for testing on the following platforms distros are available for download: * Debian Packages (amd64 i386) http://fossology.org/debian/1.3.0-rc1/ * RPM Packages (rhel5/centos5 fedora12 fedora13 i386 and x86_64) http://fossology.org/rpms/ Please refer to the attached instructions to configure your system to use apt or yum for installing the FOSSology packages. (We are having trouble creating Ubuntu packages, but plan to have them available at release time.) New features/enhancements include: 1. Groups. http://fossology.org/perms Implemented user groups inside of fossology as an indirect but critical requirement for 1.3 because tagging (the real 1.3 requirement) is dependent on having groups to administer tag permissions. 2. http://fossology.org/tagging File Tagging I. The ability to attach a tag (short (max 32 character) tag, plus a long text) to a file or container. II. Tagging requires permission for creating, attaching, and viewing tags which is why we have a dependency on groups. 3. Copyright agent replaced. A quick experiment showed that we get better results with simple heuristics rather than the old agent based on naive Bayes. 4. Fixed a cp2foss authentication bug that prevented bucket agent from getting scheduled. 5. Many bug fixes! There are a couple known bugs in unpack when running under RHEL/Fedora. (http://bugs.linux-foundation.org/show_bug.cgi?id=596 and http://bugs.linux-foundation.org/show_bug.cgi?id=597) Fixes have been checked in and will be rolled into the next set of test packages. Please report any other bugs using our bug reporting system hosted by The Linux Foundation at http://bugs.linux-foundation.org/ OR, write to the fossology mailing list. Thanks, The FOSSology Project ---BeginMessage--- Hi Mary, The 1.3.0rc1 packages from Mark for lenny i386 and x86_64 platform are available. I put them on http://fossology.org/debian/1.3.0-rc1/ 1. To use apt-get install fossology, you need add the following to /etc/apt/sources.list on the machine where there are to be installed. deb http://fossology.org/debian/1.3.0-rc1/ ./ 2. How to install sudo apt-get update; sudo apt-get install fossology Notice: You need generate two files under /etc/apache2/sites-available, /etc/apache2/sites-enabled. I do not confirm if this is one defect. They are: /etc/apache2/sites-available/fossology /etc/apache2/sites-enabled/fossology File Content is: Alias /repo/ /usr/share/fossology/www/ Directory /usr/share/fossology/www AllowOverride None Options FollowSymLinks MultiViews Order allow,deny Allow from all # uncomment to turn on php error reporting #php_flag display_errors on #php_value error_reporting 2039 /Directory 3. I am testing the packages, if find any issues, will file bugs, or discuss with team. Thanks, Best Regards, - Larry Shi(Shi Yao-Bin) Open Source Program Office (EB-BAS-BECOM-BJ) China Hewlett-Packard yao-bin@hp.com -- ---End Message--- ---BeginMessage--- Hi Team, The 1.3.0rc1 packages for rhel5/centos5 fedora12 fedora13 i386 and x86_64 platform are available. You can download from http://fossology.org/rpms/epel/testing/5/i386/fossology-1.3.0rc1-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/testing/5/x86_64/fossology-1.3.0rc1-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/fedora/testing/12/i386/fossology-1.3.0rc1-1.fc12.i686.rpm --- fedora12 i386 http://fossology.org/rpms/fedora/testing/12/x86_64/fossology-1.3.0rc1-1.fc12.x86_64.rpm --- fedora12 x86_64 http://fossology.org/rpms/fedora/testing/13/i386/fossology-1.3.0rc1-1.fc13.i686.rpm --- fedora13 i386 http://fossology.org/rpms/fedora/testing/13/x86_64/fossology-1.3.0rc1-1.fc13.x86_64.rpm --- fedora13 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Rhel/CentOS repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 4. yum --enablerepo=fossology-testing install fossology Thanks, Vincent Ma ( 马冬 ) Hewlett-Packard Co.,
Re: [FOSSology] Detection of new license on FOSSology UI
-Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Hitoshi Yoshida Sent: Thursday, December 16, 2010 7:12 PM To: fossology@fossology.org Subject: Re: [FOSSology] Detection of new license on FOSSology UI Hello, Mark. Thank you for your reply. Yes, I have copied the nomos by using command “sudo make install”. It has copied it under “/usr/local/lib/fossology/agents/nomos”. After my investigation, I noticed that some files were detected license correctly. (It includes that command line is okay, but FOSSology is not good…) This phenomenon may occur if I uploaded the exact same file after re- compiling nomos agent. In this case, I think FOSSology remembered and indicated the old license That is correct. FOSSology creates a unique id for each upload and tracks the analysis performed on the upload. If you try to rerun the analysis without removing previous results from the database, FOSSology will detect the existing results and display them in the UI. To completely remove an upload, use the Organize - Uploads - Delete Uploaded File in the UI. If you only wish to remove the license analysis results, see http://fossology.org/usefulsql for some helpful sql commands. Mary information. （It was the same result even though I deleted or reanalyze the uploaded files by using FOSSology manu.) If I re-uploaded little different files after re-compiling, FOSSology indicated correct license information as I expected. Do you think my FOSSology environment is something wrong, and should fix it somehow? Regards, Hitoshi On Wed, 15 Dec 2010 18:48:31 -0800 Mark Donohoe mark.dono...@hp.com wrote: Hitoshi Yoshida wrote: Hello, I am trying to add a new license for Nomos License Scanner, but I cannot get a correct nomos license name on FOSSology yet. Basically, I followed the description at http://fossology.org/nomos;. At first, I have modified those STRINGS.in and parse.c, and then recompiled them. After this procedure, I could get a correct license name by executing nomos from command line below. $ sudo -u fossy ./nomos xyx-license.txt $ File LICENSE contains license(s) XYZ_v1.0 HOWEVER, I cannot detect any license name by uploading the file even thought I use the same file which is used for command line confirmation. Am I missing something to modify FOSSology? Or my environment (such as database) is something wrong? My environment version is: FOSSology version 1.2.1 (code revision 3709) Please help me to detect the new license on FOSSology UI. Regards, Hitoshi ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology Did you copy the new nomos to /usr/lib/fossology/agents/ ? if not then the ui is using the 'old' one before you made your changes. Hope that helps. -- Mark Donohoe OST, Cupertino CA. fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Something weird with buckets/pkgagent agent with src.rpm
Thanks for reporting the initial errors and verifying the fixes. Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Raino Lintulampi Sent: Tuesday, December 07, 2010 12:50 AM To: Gobeille, Robert Cc: fossology@fossology.org Subject: Re: [FOSSology] Something weird with buckets/pkgagent agent with src.rpm Hi Bob, There were two issues: - some src.rpm packages were not unpacked correctly by ununpack. This is corrected in a new ununpack agent version, - there was an error in escape string handling in pkgagent which is also corrected in a newer versions. After making those changes to 1.2.1 and uploading distro again everything went OK. Thanks Raino ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology install
Hi Jeff, Did you address the error in your pg_hba.conf file? 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bLOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bFATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bHINT: See server log for details. 2010-11-25 14:14:22 GMT [local] 4cee6f3e.6808FATAL: password authentication failed for user postgres Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of jeff.mca...@bt.com Sent: Friday, November 26, 2010 9:44 AM To: fossology@fossology.org Subject: [FOSSology] Fossology install Hi Wondered if someone can help with reasons why I cannot login to the /repo ...I have used the default userid and password but it just keeps returning the same login page Regards Jeff From: jeff.mca...@bt.com [mailto:jeff.mca...@bt.com] Sent: Thursday, November 25, 2010 7:45 AM To: Laser, Mary Subject: RE: OEL Fossology install Mary I have done the following 1. Checked postgresql.conf 2. Checked pg_hba.conf 3. Restarted and then connected to the db server and logged in with fossy credentials and all looks ok 4. Checked postgres log file and states some errors below [r...@rdl10366app02 pg_log]# cat postgresql-Thu.log 2010-11-25 14:06:24 GMT LOG: received fast shutdown request 2010-11-25 14:06:24 GMT LOG: shutting down 2010-11-25 14:06:24 GMT LOG: database system is shut down 2010-11-25 14:06:24 GMT LOG: logger shutting down 2010-11-25 14:07:06 GMT LOG: database system was shut down at 2010-11-25 14:06:24 GMT 2010-11-25 14:07:06 GMT LOG: checkpoint record is at 0/349BB0 2010-11-25 14:07:06 GMT LOG: redo record is at 0/349BB0; undo record is at 0/0; shutdown TRUE 2010-11-25 14:07:06 GMT LOG: next transaction ID: 641; next OID: 16389 2010-11-25 14:07:06 GMT LOG: next MultiXactId: 1; next MultiXactOffset: 0 2010-11-25 14:07:06 GMT LOG: database system is ready 2010-11-25 14:07:06 GMT LOG: transaction ID wrap limit is 2147484146, limited by database postgres 2010-11-25 14:10:38 GMT [local] 4cee6e5e.675eFATAL: password authentication failed for user postgres 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bLOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bFATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:10:38 GMT 127.0.0.1 4cee6e5e.676bHINT: See server log for details. 2010-11-25 14:14:22 GMT [local] 4cee6f3e.6808FATAL: password authentication failed for user postgres 2010-11-25 14:14:22 GMT 127.0.0.1 4cee6f3e.6815LOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:14:22 GMT 127.0.0.1 4cee6f3e.6815FATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:14:22 GMT 127.0.0.1 4cee6f3e.6815HINT: See server log for details. 2010-11-25 14:14:50 GMT [local] 4cee6f5a.684aFATAL: password authentication failed for user postgres 2010-11-25 14:14:50 GMT 127.0.0.1 4cee6f5a.6857LOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:14:50 GMT 127.0.0.1 4cee6f5a.6857FATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:14:50 GMT 127.0.0.1 4cee6f5a.6857HINT: See server log for details. 2010-11-25 14:29:03 GMT [local] 4cee72af.7469FATAL: password authentication failed for user postgres 2010-11-25 14:29:03 GMT 127.0.0.1 4cee72af.7477LOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:29:03 GMT 127.0.0.1 4cee72af.7477FATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:29:03 GMT 127.0.0.1 4cee72af.7477HINT: See server log for details. 2010-11-25 14:34:10 GMT [local] 4cee73e2.753eFATAL: password authentication failed for user postgres 2010-11-25 14:34:10 GMT 127.0.0.1 4cee73e2.754cLOG: invalid entry in file /var/lib/pgsql/data/pg_hba.conf at line 69, token 255.255.255.255 2010-11-25 14:34:10 GMT 127.0.0.1 4cee73e2.754cFATAL: missing or erroneous pg_hba.conf file 2010-11-25 14:34:10 GMT 127.0.0.1 4cee73e2.754cHINT: See server log for details. [r...@rdl10366app02 pg_log]# ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] OEL Fossology install
Hi Jeff, It looks as though your postgresql db server configuration is incomplete/incorrect. You must to edit the postgresql.conf and pg_hba.conf config files to have a fully functional db for FOSSology BEFORE you try to install configure FO. There is a brief description of this in the INSTALLhttp://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/INSTALL?revision=3690view=markup file. (There is exhaustive online documentation for PostgreSQLhttp://www.postgresql.org/docs/8.3/interactive/index.html install and configuration.) The most important things are: 1. the listen address in postgresql.conf listen_addresses = '*' 2. client authentication configuration file (pg_hba.conf) # IPv4 local connections: #hostall all 127.0.0.1/32 md5 hostall all 127.0.0.1 255.255.255.255md5 Restart the db server and try to connect to the db as user postgres: postg...@mysys:~$ psql Welcome to psql 8.3.12, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit postgres=# If this is successful, try connecting as user fossy (password fossy). If either of these fail, check the postgres log file for errors. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of jeff.mca...@bt.com Sent: Tuesday, November 23, 2010 4:26 AM To: fossology@fossology.org Subject: [FOSSology] OEL Fossology install Hi Just tried to install Fossology onto an OEL instance ( OracleEnterpriseServer ) and cannot quite complete the activity. Has someone seen these error messages before ? /etc/init.d/fossology start Starting FOSSology job scheduler: Logfile failure: Permission denied FATAL: Unable to log to logfile '/var/log/fossology' Logfile failure: Permission denied FATAL: Unable to log to logfile '/var/log/fossology' scheduler. [r...@rdl10366app02 init.d]# Also tried to re-run the postinstall script ...below [r...@rdl10366app02 init.d]# /usr/local/lib/fossology/fo-postinstall *** Running postinstall for everything *** *** Setting up the FOSSology database *** Password: psql: FATAL: password authentication failed for user postgres ERROR: postgresql isn't running *** Creating user and group *** NOTE: user 'fossy' already exists, good. *** Making sure needed dirs exist with right ownership/permissions *** NOTE: Repository already exists at /srv/fossology/repository NOTE: /srv/fossology/repository/localhost directory already exists *** Checking database connectivity *** ERROR: Unable to connect to the database Connection string: 'dbname=fossology host=localhost user=fossy password=fossy' Connection status: '1' ERROR: Failed to open database ERROR: unable to connect to database, please check /usr/local/etc/fossology/Db.conf [r...@rdl10366app02 init.d]# Regards JeffM ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Installing Fossology
Hi Jeff, Bob is out of the office today and he’s asked me to reply to your email. Yes, in general, you need to install all dependencies (everything you listed below more), tune the kernel, configure the applications (Postgres, apache, php). For dependencies, there is a utility packaged with FOSSology called fo-installdeps (http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.2.1/utils/fo-installdeps?revision=3505view=markup) that should install everything you need. We recognize our install process is much more complicated than it should be. We are trying to improve it with each new release. Please feel free to write to the mailing list for additional help. Mary Begin forwarded message: From: jeff.mca...@bt.commailto:jeff.mca...@bt.com jeff.mca...@bt.commailto:jeff.mca...@bt.com Date: November 12, 2010 6:16:03 AM MST To: Gobeille, Robert bob.gobei...@hp.commailto:bob.gobei...@hp.com Subject: Installing Fossology Bob Could you verify the steps we would need to take to install a fresh install of Fossology. I looked at the fossology site for OEL ( aka Red hat ) and it seems to say the following 1. Install Libextractor , sleuth kit , ucl ,upx , unrar cabextract – dependencies 2. Install postgresql php ? 3. Install the rpm 4. Configure the kernel 5. Configure postgresql 6. Configure php Is this the sequence you recommend ? Regards Jeff ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Removal of bSAM analyzer from FOSSology
Hello FOSSologists, As you may recall, we have been making noises about removing the bSAM license analyzer from FOSSOlogy for several months. In preparation for that, a new license analyzer (nomos) was introduced in release 1.2.0. The bSAM menus and functionality have remained in FOSSology, but we stopped support and enhancement of bSAM to encourage users to start using the new nomos analyzer. The bSAM functionality is scheduled to be removed in the first half of 2011. If you have bSAM generated license analysis results in your database, you will no longer have access to the results once bSAM is removed. Furthermore, there is NO upgrade path from bSAM results to nomos results. Therefore, you MUST rerun license analysis on your uploads using the nomos analyzer introduced in 1.2.0. You can run nomos analysis on uploads using these steps: 1. Select “Jobs” → “Agents” from the top menu bar. 2. Select the folder containing the upload you wish to analyze. 3. Select the upload to analyze. 4. A list of analyses available for the upload are listed in step 3 of the window. 5. Select the one you wish to run and Click on the “Analyze” button. 6. The job is automatically queued up run. If you have any questions, please email us at fossology@fossology.orgmailto:fossology@fossology.org. Thanks, The FOSSology Project ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] FOSSology on SuSE
Good Morning Stephan, It is most likely possible. Once the dependencies are met, the next challenge will be differences in pathnames. Fossology has been successfully installed and used with Fedora, RedHat, Debian and, Ubuntu distros. I see no reason why Suse could not be done, too. That said, I don’t recall ever hearing anyone that has done it yet. If you decide to try it, please take detailed notes, so we can publish/replicate your procedure. Thanks, Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Stephan Zinke Sent: Thursday, October 28, 2010 1:25 AM To: 'fossology@fossology.org' Subject: [FOSSology] FOSSology on SuSE Hi, My sysadmin checked your prerequisites (dependencies) and determined that possibly an installation would be fine on OpenSuse 11.1 as well. Can you confirm, or do you advise to use RHEL instead? Does anybody of you have experience in installing/using under SLES? Thanks a lot Stephan Zinke for EUMETSAT ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] how to contribute
Hi Wolfgang, Just to be sure we fixed the right typos, please check the pages where you saw the errors. Thanks, Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Donohoe, Mark Sent: Thursday, October 21, 2010 2:04 PM To: Wolfgang Strunk Cc: fossology@fossology.org Subject: Re: [FOSSology] how to contribute Wolfgang, In a way you did contribute. You let us know we had typos. Please tell us where next time. Another user reported the details and the wiki has been fixed. Best of luck in your work. Wolfgang Strunk wrote: Unfortunately I did not intend to be ironic at all. I think I completely made a fool of myeself. :-(( Still, after reading through the whole How to contribute section, I don't have a clue how to provide changes to the install documentation. I found two typos in shell scripts which lead to command line errors. -- Mark Donohoe OST, Cupertino CA. fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine
-Original Message- From: m...@lackof.org [mailto:m...@lackof.org] On Behalf Of Matt Taggart Subject: Re: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine I just edited a little to explain that just rebuilding the packages is enough if people want to do that until proper packages are available. Thanks Matt! Also, we have not tried or tested fossology using postgresql 8.4, yet. You can be the first :) I use 8.4, it works fine. Maybe the fossology developers should try it :) Good idea. We'll plan to do that with the next development cycle (post-1.3). Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine
Hi William, I apologize for the miscommunication on our website. The page was out of date and should not have stated that the latest version of fossology was available for ubuntu 9.10. :( (I have made the correction.) We do not have 1.2.1 packages for Ubuntu at this time. The instructions for installing FO 1.2.1 from source on Ubuntu 10.04http://fossology.org/ubuntu10.04_install_guide *should* work for Ubuntu 9.10. However, I don't know if this configuration was tested. Mark - do you know? Also, we have not tried or tested fossology using postgresql 8.4, yet. You can be the first :) Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Causey, William Sent: Tuesday, October 19, 2010 10:16 AM To: fossology@fossology.org Subject: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine Hi, I attempted to follow the steps to install the latest version of fossology on Ubuntu karmic koala (9.10) that are given in the fossology website: http://fossology.org/ubuntu The problem is I expected to install the latest version 1.2.1 but it appeared that the version was 1.1.0 instead. In addition to this instead of postgresql-8.4 being installed the version installed was postgresql-8.3. We would like to use the latest version of fossology as we already have the 1.1.0 running on another machine. Thanks Regards, William William Causey Texas Instruments Voice 214 567 2339 Cell: 214 803 8829 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine
Hi William, Yes, you can use the following procedure to upgrade from 1.1.1 to 1.2.1 on Ubuntu: 1. Stop the scheduler db server a. sudo /etc/init.d/fossology stop b. sudo /etc/init.d/postgresql stop 2. Remove the current install (this will NOT remove the database or repository) a. For package installs, use apt-get remove fossology b. For source installs, use fo-cleanold from the source tree 3. Install FO 1.2.1 from sources using the steps outlined in the Ubuntu 10.04 install guidehttp://fossology.org/ubuntu10.04_install_guide. Mark - Please confirm or make corrections, as necessary. If these instructions are correct, let's post them to the website for future reference. Mary From: Causey, William [mailto:w-caus...@ti.com] Sent: Tuesday, October 19, 2010 11:09 AM To: Laser, Mary; Donohoe, Mark Cc: fossology@fossology.org Subject: RE: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine Hi Mary, OK, so I think we'd rather use Ubuntu 10.04 but I have version 1.1.0 (fossology) running on my Ubuntu machine (10.04), is there a way I can upgrade to 1.2.1 without removing the data I have collected already with the older version of fossology? So I'd like to be able to run an update to pull the 1.2.1 version and then upgrade my fossology to 1.2.1? (I have postgresql 8.4 running on my machine now with fossology 1.1.0). Thanks Regards, William William Causey Texas Instruments Voice 214 567 2339 Cell: 214 803 8829 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Project update and packaging requests
Hello FOSSologists! The entire FOSSology development team is feverishly working to finish up coding and test writing for our 1.3 releasehttp://fossology.org/task_list#v_1.3. We are scheduled to ramp up functional and integration testing next month, addressing bugs as we find them. We'll build test packages shortly thereafter, and aim to have downloads available in December, just in time for the holidays! In a recent developer's meeting, we created a list of distros for which we will attempt to build FO 1.3 packages, with the help of Bruno Cornec's expertise and Package Builderhttp://www.project-builder.org/. This list includes CentOS5/RHEL5, Fedora 12/13, OpenSuSE 11.2, Mandriva 2010.1, Ubuntu 10.04/10.10. Debian packages will be handled by our FOSSology maintainer for debian, Matt Taggart - Thanks Matt! We've had some interest expressed on the mailing list and on our irc channel lately about FOSSology packages for additional distros. Have we captured all the requested distros in the list above? Note that our 1.3 developers are not able to build additional packages for the current release of FOSSology, 1.2.1, due to scarce resources and 1.3 deadlines. HOWEVER, we invite you to share your functionally tested packages via the mailing list. Thank for your contributions! The FOSSology Project ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine
Hi Gurbax, Did you try to uninstall the previous (1.1.0) version of fossology? If so, it does not appear to have worked. Note the message in your log file in #2 below : Scheduler started. Build version: 1.1.0, exported. Error #1 is most likely a symptom of an incomplete uninstall/install. Error #3 is a due to mis-configuration of Postgresql. Note the HINT about the SHMMAX kernel parameter. An incomplete uninstall of a package combined with a source install of 1.2.0 will leave pieces of both versions on your system! A very bad, mixed up configuration. Please verify apt-get remove successfully removes the 1.1.0 version before you try to install 1.2.1 from source. Mary -Original Message- From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Tuesday, October 19, 2010 4:12 PM To: Donohoe, Mark; Laser, Mary Cc: Causey, William; fossology@fossology.org Subject: RE: [FOSSology] Installing fossology on a Ubuntu karmic koala (9.10) machine Mark, Mary, We followed the instructions provided in your email, but are running into the following issues: 1. This command does not run, error message is that this file is not found: sudo fo-postinstall po.out 21 2. The following command errors out too: sudo /usr/lib/fossology/fossology-scheduler -t -L stdout 2010-10-19 17:10:09 scheduler[30586] : Scheduler started. Build version: 1.1.0, exported. 2010-10-19 17:10:09 scheduler[30586] : *** Scheduler started, PID 30586 *** ERROR: Unable to connect to the database Connection string: 'dbname=fossology host=localhost user=fossy password=fossy' Connection status: '1' 2010-10-19 17:10:09 scheduler[30586] : FATAL: Unable to connect to database. Exiting. 3. then I try to start the database and get another error message: sudo /etc/init.d/postgresql-8.3 start * Starting PostgreSQL 8.3 database server * The PostgreSQL server failed to start. Please check the log output: 2010-10-19 16:17:53 CDT 4cbe0b01.7639LOG: could not load root certificate file root.crt: No such file or directory 2010-10-19 16:17:53 CDT 4cbe0b01.7639DETAIL: Will not verify client certificates. 2010-10-19 16:17:53 CDT 4cbe0b01.7639FATAL: could not create shared memory segment: Invalid argument 2010-10-19 16:17:53 CDT 4cbe0b01.7639DETAIL: Failed system call was shmget(key=5432001, size=268632064, 03600). 2010-10-19 16:17:53 CDT 4cbe0b01.7639HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 268632064 bytes), reduce PostgreSQL's shared_buffers parameter (currently 32000) and/or its max_connections parameter (currently 43). If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for. The PostgreSQL documentation contains more information about shared memory configuration. Thanks for all your support. -gurbax ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology tabs are not working
Hello Khammer, FOSSology 1.0 is a VERY old version which is no longer supported. The problem you described below and many others, along with new enhancements performance improvements are available with the latest release, FOSSology 1.2.1http://fossology.org/home. Please use this version. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of kmohamed Sent: Tuesday, October 12, 2010 8:18 AM To: fossology@fossology.org Subject: [FOSSology] Fossology tabs are not working Importance: High Hi, I have installed Fossology 1.0.0.0 on ubuntu 9.10 and analyzed my source code.. It was working fine.. After the analysis of source code the Fossology options like Browse, Upload, Organise, Jobs and other tabs are not working. When I click on it, the page is blank. Nothing is showing up. When I checked the terminal, it said BUFFER OVERFLOW- PROCESS TERMINATED. I dont remember the exact error message..I think this could be the possible thing which made the Fossology not working properly. I didnt take the screen shot of the error message also. Sorry.. I have restarted the server, restarted the services of apache and fossology, cleared the cache etc.. But still I couldnt access the tabs. Do we have any options to check the software repository whether the source code which I have uploaded are safe and the reports generated are safe.? I need the reports of the source code, very important. Please help me in this regard.? Thanks, Khammer. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology tabs are not working
Just to be clear... you must reinstall with FOSSology 1.2.1 (rather than upgrade from your old 1.0 version). Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Tuesday, October 12, 2010 9:57 AM To: kmohamed; fossology@fossology.org Subject: Re: [FOSSology] Fossology tabs are not working Hello Khammer, FOSSology 1.0 is a VERY old version which is no longer supported. The problem you described below and many others, along with new enhancements performance improvements are available with the latest release, FOSSology 1.2.1http://fossology.org/home. Please use this version. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of kmohamed Sent: Tuesday, October 12, 2010 8:18 AM To: fossology@fossology.org Subject: [FOSSology] Fossology tabs are not working Importance: High Hi, I have installed Fossology 1.0.0.0 on ubuntu 9.10 and analyzed my source code.. It was working fine.. After the analysis of source code the Fossology options like Browse, Upload, Organise, Jobs and other tabs are not working. When I click on it, the page is blank. Nothing is showing up. When I checked the terminal, it said BUFFER OVERFLOW- PROCESS TERMINATED. I dont remember the exact error message..I think this could be the possible thing which made the Fossology not working properly. I didnt take the screen shot of the error message also. Sorry.. I have restarted the server, restarted the services of apache and fossology, cleared the cache etc.. But still I couldnt access the tabs. Do we have any options to check the software repository whether the source code which I have uploaded are safe and the reports generated are safe.? I need the reports of the source code, very important. Please help me in this regard.? Thanks, Khammer. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] License Listing
Hi Sesh, I think you are asking for a list of packages associated licenses for each(?) You can obtain such a list by clicking on the Nomos License List Download mini menu while browsing your upload. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Kothandaraman, Seshadrinathan Sent: Tuesday, October 05, 2010 12:13 AM To: 'fossology@fossology.org' Subject: [FOSSology] License Listing Hi, I have a subfolder under the main repository and all my packages of interest are in this subfolder. How can I export all the packages and associated licenses in a csv form? Thanks a lot, in advance, Sesh ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] License Listing
Hi Sesh, Such a scripting option does not exist...yet! But, it's completely do-able. All my developers are gone (vacations, national Chinese holiday, injury) till next week. Perhaps you or someone in the user community would like to make a contribution to the FOSSology project? :) Mary From: Kothandaraman, Seshadrinathan [mailto:seshadrinathan.kothandara...@deshawresearch.com] Sent: Thursday, October 07, 2010 10:02 PM To: Laser, Mary Subject: RE: License Listing Hi Mary, Yes. However, given that I have something like 200+ packages, I was looking at some scripting option. Basically I would like to have a CSV file which lists the packages and the licenses contained therein for each. I am new to FOSSology and am sure that this problem has been faced by veterans and a solution exists. Thanks a lot for your concern. I hope my login problem would soon be fixed. Sesh From: Laser, Mary [mailto:mary.la...@hp.com] Sent: Friday, October 08, 2010 9:28 AM To: Kothandaraman, Seshadrinathan; 'fossology@fossology.org' Subject: RE: License Listing Hi Sesh, I think you are asking for a list of packages associated licenses for each(?) You can obtain such a list by clicking on the Nomos License List Download mini menu while browsing your upload. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Kothandaraman, Seshadrinathan Sent: Tuesday, October 05, 2010 12:13 AM To: 'fossology@fossology.org' Subject: [FOSSology] License Listing Hi, I have a subfolder under the main repository and all my packages of interest are in this subfolder. How can I export all the packages and associated licenses in a csv form? Thanks a lot, in advance, Sesh ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] How to reschedule nomos license analysis?
Hello again Mike, I realized after I sent you email yesterday that I failed to mention that the instructions for adding a license are for the bsam license analysis ONLY. This method does not work for nomos license analysis. As it turns out, the instructions for adding a license for nomos analysishttp://www.fossology.org/nomos are a bit more complex and currently are incomplete. :( I need the expertise of one of our developers, however he's heads down trying to meet a deadline. I'll do my best to get some guidance on a solution for you and reply either way later today. Mary From: Mike Kinghan [mailto:mi...@symbian.org] Sent: Tuesday, October 05, 2010 1:29 AM To: Laser, Mary Cc: fossology@fossology.org Subject: Re: [FOSSology] How to reschedule nomos license analysis? Hi Mary, These instructions work fine. However I don't seem to have succeed in adding a new license to my analysis. I used the instructions here: http://www.fossology.org/how_to_add_a_license_template_or_license_phrase_and_re-analyze_licenses and I chose the method: Alternately: 1. Place your file under /usr/local/share/fossology/agents/licenses/. 1. Run 'sudo fossinit'. The ... sequence indicates that the licenses are being installed. Specifically I created the folder /usr/local/share/fossology/agents/licenses/proprietary and placed in it a raw license text file called Nokia Closed Copyright which contains the text: Copyright 2007 Nokia. All rights reserved. This material, including documentation and any related computer programs, is protected by copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia. This material also contains confidential information which may not be disclosed to others without the prior written consent of Nokia. I want to detect source files in the Symbian OS source tree from which this Nokia license has not been scrubbed. The fossinit process reported 1 more license processed (361) than the initial install. However I notice that after fossinit, there do does not exist a Nokia Closed Copyright.meta file, whereas all the default raw licenses have matching .meta files When I rescheduled the analysis, I expected the package to gain a Nomos License report-line for the Nokia Closed Copyright license, because I know there are matching files. But the rescheduled analysis ran in 0 time and did not report the new license. I guess the process I have followed is not sufficient to register a new license? I also tried entering the license via License Admin - Add License (which seems to be under construction). That operation reported the license added but resulted in nothing new appearing under /usr/local/share/fossology/agents/licenses/, and again made no difference when I reran the analysis. Br, Mike ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Announcing FOSSology 1.2.1 (Critical bug fix release for 1.2.0)
Hello FOSSologists! We are making this special point release available to address some critical bugs in the 1.2.0 release. The following bugs are fixed in 1.2.1: . 7zip unpack fix to cleanup temp files: http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3338 . copyright table creation failure: http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3348 . pkgagent fix #1; unable to locate control file:http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3324 (this was not in 1.2.0) . pkgagent fix #2; for deb packages with no dependencies:http://fossology.svn.sourceforge.net/fossology/?rev=3363view=rev . unpack: http://fossology.svn.sourceforge.net/fossology/?rev=3361view=rev . free temp name string on fopen error condition, svn#3362 . add error checking to fopen, svn#3359 . fix pkgagent dsc parsing, svn#3358 . fix copyright wrong variable name, svn#3355 . init script restart output, svn#3346 ALSO, a NEW supported distro matrix can be found at http://fossology.org/download#supported_distro_s. A BIG Thank You to everyone that helped identify and fix these bugs! The FOSSology Project ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] How to reschedule nomos license analysis?
Hi Mike, Yes, that page is out of date. Here is the correct click-by-click process for rescheduling an agent for analysis: 1. Click on the main Browse tab. 2. Navigate using the left navigation bar till you see your upload in the right hand window. 3. Click on the jobs link to see the history of jobs run on your upload. 4. On the right side of the window, locate the Reset | Delete actions for the agent you wish to rerun. 5. Click on Delete. The window will refresh and the job will be gone. 6. Select Jobs - Agents from the top menu bar. 7. Select the folder containing the upload you wish to analyze. 8. Select the upload to analyze. 9. A list of analyses available for the upload are listed in step 3. 10. Select the one you wish to run and Click on the Analyze button. 11. The job is automatically queued up run. I will update the instructions on fossology.org with these steps. Please let me know if they are OK/not OK. Thanks, Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Mike Kinghan Sent: Monday, October 04, 2010 2:21 AM To: fossology@fossology.org Subject: [FOSSology] How to reschedule nomos license analysis? Hi folks, I have added a new license to my foss 1.2 server (by placing the raw license in /usr/lib/share/fossology/agents/licenses and running fossinit) and now want to reschedule the nomos analysis of a package. I can't see any way to do this via the UI. The instructions at http://www.fossology.org/how_to_add_a_license_template_or_license_phrase_and_re-analyze_licenses#re-analyzing_licenses say: 1. Click Browse at the top menu. Navigate the tree until you find the upload to analyze. 1. Under the upload's description is a link to Reschedule license analysis. This will schedule the upload for a re-analysis. But in 1.2 no such link exists in the Browser. -- Mike Kinghan, Test Lead, Symbian +44(0)776 5222 793 Some facts about Symbian that we are legally obliged to tell you: Symbian Foundation Limited is a Company Limited by Guarantee and not having Share Capital We're registered in England and Wales - Companies House knows us by the number 6683783 Our address is 1 Boundary Row, Southwark, London SE1 8HP. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology Installation Issues - Please suggest
-Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Matt Taggart Sent: Monday, September 27, 2010 11:04 AM To: kmohamed Cc: fossology@fossology.org Subject: Re: [FOSSology] Fossology Installation Issues - Please suggest I'm having Hard time in installing the Fossology 1.2.0 on Ubuntu 10.04. I'm encountering few errors during installation. I need your help reg this. Based on the images you provided, I think you have a problem with your system's apt sources. Also it's not clear why you have a dapper- backports source if you using lucid. Try to get that working first and then we can answer fossology questions. Also see this post about problems with the current fossology packages on lucid http://fossology.org/pipermail/fossology/2010-September/001790.html Matt is correct. Your FO install problems are due to unresolved dependency issues and (most likely) a misconfigured /etc/apt/sources.list file. Thanks Matt! Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology Install
After you make the one line edit, you need to rebuild re-run fo_postinstall: make clean make sudo make install /usr/.../fo_postinstall From: Mikko-Pekka Partanen [mailto:mikko-pekka.parta...@hhpartners.fi] Sent: Friday, September 17, 2010 2:34 AM To: Laser, Mary; Donohoe, Mark Cc: Martin von Willebrand; fossology@fossology.org Subject: VS: [FOSSology] Fossology Install Hi Mary, What is the suggested procedure for applying this fix regarding the copyright agent? We built our installation from the sources and now just exchanging the copyright.py-file (in directory /user/[user-id]/[1.2.0.rc2]/agents/copyright-analysis/) did nothing. Should it be rebuilt or the installation process done partly again? Would it be easier to update to the next published version? Not sure whether this was the right place, but at least that was tried... Best, Mikko-Pekka Lähettäjä: Laser, Mary [mailto:mary.la...@hp.com] Lähetetty: 11. syyskuuta 2010 1:27 Vastaanottaja: Mikko-Pekka Partanen; Donohoe, Mark Kopio: Martin von Willebrand; fossology@fossology.org Aihe: RE: [FOSSology] Fossology Install Hi Mikko-Pekka, This issue has been reported and addressed. Please see the email thread discussion and fix here: http://fossology.org/pipermail/fossology/2010-August/001731.html Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Mikko-Pekka Partanen Sent: Friday, September 10, 2010 1:39 AM To: Donohoe, Mark Cc: Martin von Willebrand; fossology@fossology.org Subject: Re: [FOSSology] Fossology Install Hi Mark, Thanks for the instruction regarding getting the copyright agent to work. It seems that the sudo /usr/local/lib/fossology/fossology-scheduler -t -L stdout is not able to fix the problem. Below is the relevant output. Any further ideas? (As a note, the installation path in our ubuntu 10.4 installation seems to be /usr/local/lib/fossology and not /usr/lib/fossology.) 2010-09-10 10:30:46 scheduler[9418] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Fri Sep 10 10:30:46 2010 2010-09-10 10:30:47 scheduler[9418] : ERROR: In thread 7: Could not select table copyright. Database said: relation copyright does not exist 2010-09-10 10:30:47 scheduler[9418] : DEBUG[7]: ERROR: Could not select table copyright. Database said: relation copyright does not exist 2010-09-10 10:30:47 scheduler[9418] : DEBUG[7]: LINE 1: SELECT ct_pk FROM copyright LIMIT 1 2010-09-10 10:30:47 scheduler[9418] : DEBUG[7]: ^ 2010-09-10 10:30:47 scheduler[9418] : ERROR: In thread 7: sql=SELECT ct_pk FROM copyright LIMIT 1 2010-09-10 10:30:47 scheduler[9418] : DEBUG[7]: ERROR: sql=SELECT ct_pk FROM copyright LIMIT 1 2010-09-10 10:31:47 scheduler[9418] : ERROR: Child[7] failed to spawn after 61 seconds 2010-09-10 10:31:47 scheduler[9418] : ERROR: Child[7] failed command was: '/usr/local/lib/fossology/agents/copyright/run.py --model /usr/local/share/fossology/model.dat --agent' 2010-09-10 10:31:47 scheduler[9418] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Fri Sep 10 10:31:47 2010 2010-09-10 10:31:47 scheduler[9418] : Child[7] 'agent=copyright host=localhost ' state=FREEING(2) @ Fri Sep 10 10:31:47 2010 2010-09-10 10:31:47 scheduler[9418] : Child[7] 'agent=copyright host=localhost ' state=FREE(1) @ Fri Sep 10 10:31:47 2010 2010-09-10 10:31:47 scheduler[9418] : FAILED: Could not run thread 7: /usr/local/lib/fossology/agents/copyright/run.py --model /usr/local/share/fossology/model.dat -agent Regards, Mikko-Pekka Lähettäjä: Mark Donohoe [mailto:mark.dono...@hp.com] Lähetetty: 20. elokuuta 2010 18:39 Vastaanottaja: Mikko-Pekka Partanen Kopio: fossology@fossology.org; Martin von Willebrand Aihe: Re: VS: [FOSSology] Fossology Install ZMikko-Pekka, This is interesting as I have not been able to reproduce this. Fo-postinstall completes with errors due to the package agent not finding libextractor. I have tried a fix for that and it didn't seem to work. I am really replying to say that you might be able to get the copyright agent working by doing the following: 1. stop the scheduler: sudo /etc/init.d/fossology stop 2. Run the scheduler in selftest mode: sudo /usr/lib/fossology/fossology-scheduler -t -L stdout. In the output you should see that copyright complains about the db table not being there and then says it will create it. 3. Restart the scheduler: sudo /etc/init.d/fossology start That might be your problem and that might fix it. Hope that helps. Mikko-Pekka Partanen wrote: Hi all, We have also been successful in installing and using Fossology 1.2 pr2 in Ubuntu 10.04. If it helps, here is a very brief outline of what we did: Installed fresh Ubuntu 10.04 desktop version; Checked-out Fossology source from svn site: svn co https://fossology.svn.sourceforge.net/svnroot/fossology/tags/1.2.0~rc2/;https://fossology.svn.sourceforge.net/svnroot
Re: [FOSSology] FOSSology on Fedora 13
Yes, I agree. Vincent has used Project-Builder with some success but, has a run into a few problems, too. He will be attending your presentation next week. Thanks Bruno! Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Cornec, Bruno (Open Source and Linux Technology Architect) Sent: Thursday, September 09, 2010 9:35 AM To: fossology@fossology.org Subject: Re: [FOSSology] FOSSology on Fedora 13 mot said on Thu, Sep 09, 2010 at 03:45:17PM +0200: Do you have any idea/offer some help how to get it to run on fedora 13? Maybe time to re-consider the possibility to use Project-Builer.org for building fossology packages ? (Cf now obsolete: http://trac.project- builder.org/browser/projects/fossology/pbconf/tags/1.1.0) Bruno. -- Open Source Linux Profession Lead EMEA / http://opensource.hp.com HP/Intel/Red Hat Open Source Solutions Initiative / http://www.hpintelco.net http://www.HyPer-Linux.org http://mondorescue.org http://project- builder.org La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Uploading files over 1MB
Also, if you are using Upload from File, take note of the message, ...Many browsers, including Microsoft's Internet Explorer, have trouble uploading file larger than 650 Megabytes (a standard-size CD-ROM image). If your file is larger than 650 Megabytes, then choose one of the other upload options. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert Hi Leslie, Your php configuration may be the limitation here. Look in your php.ini file (mine is located in /etc/php5/apache2/) and check your max upload size: ; Maximum allowed size for uploaded files. upload_max_filesize = 4094M Bob Gobeille On Aug 19, 2010, at 2:19 PM, Haynes, Leslie D wrote: We have a new installation of Fossology 1.2 on RHEL 5.4. When we try to upload files over 1 MB the connection seems to timeout. Smaller files successfully upload. Any ideas/help is appreciated. ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology Install
Hi Gurbax, Our test lead, Mark, has just installed a VM with Ubuntu 10.4 to try the install. We should have more information for you later today. Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Wednesday, August 18, 2010 10:11 AM To: Gobeille, Robert Cc: Laser, Mary; fossology@fossology.org Subject: RE: [FOSSology] Fossology Install Bob, I am using Ubuntu 10.04 baseline, the other info I think that you are asking for is [cid:image001.jpg@01CB3ECA.FD999D90] I will wait to hear from you before start to install it. I will take the version that you suggest. Hopefully it will be up and running today. Thanks. Regards, Gurbax Deol 214-567-3311 -Original Message- From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Tuesday, August 17, 2010 4:20 PM To: Deol, Gurbax Cc: Laser, Mary; fossology@fossology.org Subject: Re: [FOSSology] Fossology Install Gurbax, I think the best thing to do now is provide the info taggart requested What distribution (name and version) are you using and what apt source are you using to get the packages? You shouldn't be having all these issues so with the above info we can at least test the release/disto combination. Bob Gobeille On Aug 17, 2010, at 3:01 PM, Deol, Gurbax wrote: Mary, Spent too much time trouble shooting it. Since it was a new machine I am setting up, I have un-installed and re-installed Ubuntu OS on my machine. At this point, there is no trace of Fossology. What is the best way to install Fossology without running into issues? Thanks for your support in advance. inline: image001.jpg___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology Install
Hi Gurbax, I just spoke with Mark and he will be contacting you today to verify your install method. Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Wednesday, August 18, 2010 2:42 PM To: Laser, Mary; Gobeille, Robert Cc: fossology@fossology.org Subject: RE: [FOSSology] Fossology Install Mary, Would you be get back to me today? Let me know what steps he takes to get it installed so i can do the same and not run into so many issues. Regards, Gurbax Deol 214-567-3311 From: Laser, Mary [mailto:mary.la...@hp.com] Sent: Wednesday, August 18, 2010 12:59 PM To: Deol, Gurbax; Gobeille, Robert Cc: fossology@fossology.org Subject: RE: [FOSSology] Fossology Install Hi Gurbax, Our test lead, Mark, has just installed a VM with Ubuntu 10.4 to try the install. We should have more information for you later today. Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Wednesday, August 18, 2010 10:11 AM To: Gobeille, Robert Cc: Laser, Mary; fossology@fossology.org Subject: RE: [FOSSology] Fossology Install Bob, I am using Ubuntu 10.04 baseline, the other info I think that you are asking for is [cid:image001.jpg@01CB3EE6.5848FE50] I will wait to hear from you before start to install it. I will take the version that you suggest. Hopefully it will be up and running today. Thanks. Regards, Gurbax Deol 214-567-3311 -Original Message- From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Tuesday, August 17, 2010 4:20 PM To: Deol, Gurbax Cc: Laser, Mary; fossology@fossology.org Subject: Re: [FOSSology] Fossology Install Gurbax, I think the best thing to do now is provide the info taggart requested What distribution (name and version) are you using and what apt source are you using to get the packages? You shouldn't be having all these issues so with the above info we can at least test the release/disto combination. Bob Gobeille On Aug 17, 2010, at 3:01 PM, Deol, Gurbax wrote: Mary, Spent too much time trouble shooting it. Since it was a new machine I am setting up, I have un-installed and re-installed Ubuntu OS on my machine. At this point, there is no trace of Fossology. What is the best way to install Fossology without running into issues? Thanks for your support in advance. inline: image001.jpg___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology install fails on Ubuntu
Hi Gurbax, There are several dependencies for fossology, described on the project website at http://fossology.org/sysadmin_documentation#installation. There is a utility called fo-installdeps we use to install dependencies. You can access it from the source tree at: http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/utils/fo-installdeps?revision=3388 Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Tuesday, August 17, 2010 9:19 AM To: Gobeille, Robert; Laser, Mary; fossology@fossology.org Subject: Fossology install fails on Ubuntu Bob, I was not able to get fossology to run after the initial install. So I have removed fossology with purge command. Now when I try to grep for fossology, I do not get any results. So it is removed. When I try to install it with sudo apt-get install fossology command, it gives error message Following package have unmet dependencies: Fossology: Depends: Fossology-web-single but it is not going to be installed E: broken packages If I try to install Fossology-web-single, then it lists another package that it has dependency, it goes on and on giving list of one package after the other. What is the best way to install fossology? Thanks. Regards, Gurbax Deol 214-567-3311 From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Wednesday, August 04, 2010 4:31 PM To: Deol, Gurbax Subject: Re: Question: Fossology on Ubuntu Hello Gurbax, In the installation you created a website. So you should be able to find it at http://yourhostname/repo/ Did you apt-get install or install from source? Would you mind if we have this conversation on our public mailing list? That way other developers can join. Bob Gobeille On Aug 4, 2010, at 3:05 PM, Deol, Gurbax wrote: Hello Bob, We, at TI, are looking into Fossology as one of the tools that we may want to work with. I managed to install Fossology on Ubuntu. After running into some issues, I seems to be installed. I have been looking at the Fossology website to find out how to invoke this tool. I am not able to do find anything on it. Once the tool is installed, how can I launch it? Thank you so much for all your assistance. Regards, Gurbax Deol Configuration Management Tools Texas Instruments, Inc. gur...@ti.comblocked::mailto:gur...@ti.com 214-567-3311 972-761-5168 Fax ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Db tables
Hi Matt, It looks like your database was created with the wrong encoding. By default, the postgres package is installed with UTF8 encoding. However, the fossology database cluster must be created with SQL_ASCII encoding. If you do not specify SQL_ASCII, the fossology db cluster will default to the postgres db encoding. This seems the most plausible explanation for your error below. You can check by invoking psql on the command line as user poastgres: postg...@mysys:~$ psql Welcome to psql 8.3.11, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit postgres=# \encoding SQL_ASCII postgres=# \c fossology You are now connected to database fossology. fossology=# \encoding SQL_ASCII fossology=# If your installation does not match the example above, I suggest you drop the fossology database (drop database fossology) and recreate it by re-running fo-postinstall. Mary -Original Message- From: McIntosh, Matt [mailto:matt_mcint...@mentor.com] Sent: Tuesday, August 17, 2010 11:31 AM To: Laser, Mary Subject: RE: Db tables Mary, This got me further. I'm now getting the below errors in the log. Also, did you see my second email yesterday with the binary display on the web pages? Thanks, -Matt 2010-08-17 10:14:43 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Tue Aug 17 10:14:43 2010 2010-08-17 10:14:44 scheduler[17680] : Child[7] 'agent=copyright host=localhost ' state=READY(5) @ Tue Aug 17 10:14:44 2010 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB Access error, returned -1. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB STATUS: PGRES_FATAL_ERROR 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: DB ERRMSG: invalid byte sequence for encoding UTF8: 0x00 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by client_encoding. 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: sql=INSERT INTO copyright (agent_fk, pfile_fk, copy_startbyte, copy_endbyte, content, hash, type) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: VALUES (24, 19421, 1235, 1276, E'http\:\/\/www\.w3\.org\/TR\/html4\/loose\.dtd\\\^A\000\^N', E'0x781313cb0a6a289b', 'url') 2010-08-17 10:14:44 scheduler[17680] : ERROR: In thread 7: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: ERROR: filename=9133AD80C7B6AC5E2880BFD86002DA81006CDB77.3FF4F6DD09C98FC3EF27C C D4531EECCD.6412 2010-08-17 10:14:44 scheduler[17680] : FATAL: In thread 7: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: FATAL: An error occurred in the main agent loop. Please consult the provided traceback. 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:Traceback (most recent call last): 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: File /usr/lib/fossology/agents/copyright/copyright.py, line 284, in agent 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]: print sys.stdout, 'ERROR: Could not process file.\n\tupload_pk = %s, pfile_pk = %s, pfilename = %s' % (upload_pk, jobs[i]['pfile_pk'], jobs[i]['pfilename']) 2010-08-17 10:14:44 scheduler[17680] : DEBUG[7]:NameError: global name 'jobs' is not defined 2010-08-17 10:14:54 scheduler[17680] : ERROR: Child[7] died prematurely (was state RUNNING, signal was 0) 2010-08-17 10:14:54 scheduler[17680] : Thread 7: 2010-08-17 10:14:54 scheduler[17680] : PID: 17819 2010-08-17 10:14:54 scheduler[17680] : Pipes: in=7-8 / out=10-9 2010-08-17 10:14:54 scheduler[17680] : Attr: 'agent=copyright host=localhost ' 2010-08-17 10:14:54 scheduler[17680] : Command: '/usr/lib/fossology/agents/copyright/run.py --model /usr/share/fossology/model.dat --agent' 2010-08-17 10:14:54 scheduler[17680] : Parm: '5 ' 2010-08-17 10:14:54 scheduler[17680] : Heartbeat: Tue Aug 17 10:14:44 2010 2010-08-17 10:14:54 scheduler[17680] : State: Tue Aug 17 10:14:44 2010 2010-08-17 10:14:54 scheduler[17680] : Status: 6 (RUNNING) 2010-08-17 10:14:54 scheduler[17680] : Spawn: 1 at Tue Aug 17 10:14:43 2010 2010-08-17 10:14:54
Re: [FOSSology] Db tables
Hi Matt, Matt Taggart discovered shortly after we released. We've checked in a (1 line) fix: http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3348 Sorry for the inconvenience. Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of McIntosh, Matt Sent: Monday, August 16, 2010 10:49 AM To: fossology@fossology.org Subject: [FOSSology] Db tables What file does the database table creation? After getting everything installed and uploading a couple of packages I found that the copyright job isn't running. In looking at the log I see that it tries to do a select from the copyright table. I don't have this table in the db. FYI: I did the install from the RHEL5 rpm. Log snippet is posted below. Thanks, -Matt 2010-08-13 14:04:32 scheduler[8247] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Fri Aug 13 14:04:32 2010 2010-08-13 14:04:32 scheduler[8247] : ERROR: In thread 7: Could not select table copyright. Database said: relation copyright does not exist at character 19 2010-08-13 14:04:32 scheduler[8247] : DEBUG[7]: ERROR: Could not select table copyright. Database said: relation copyright does not exist at character 19 2010-08-13 14:04:32 scheduler[8247] : ERROR: In thread 7: sql=SELECT ct_pk FROM copyright LIMIT 1 2010-08-13 14:04:32 scheduler[8247] : DEBUG[7]: ERROR: sql=SELECT ct_pk FROM copyright LIMIT 1 2010-08-13 14:05:42 scheduler[8247] : ERROR: Child[7] failed to spawn after 70 seconds 2010-08-13 14:05:42 scheduler[8247] : ERROR: Child[7] failed command was: '/usr/lib/fossology/agents/copyright/run.py --model /usr/share/fossology/model.dat --agent' 2010-08-13 14:05:42 scheduler[8247] : Child[7] 'agent=copyright host=localhost ' state=SPAWNED(4) @ Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : Child[7] 'agent=copyright host=localhost ' state=FREEING(2) @ Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : Child[7] 'agent=copyright host=localhost ' state=FREE(1) @ Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : Child[13] 'agent=sqlagent host=localhost ' state=FREE(1) @ Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : ERROR: Child[7] died prematurely (was state FREE, signal was 0) 2010-08-13 14:05:42 scheduler[8247] : Thread 7: 2010-08-13 14:05:42 scheduler[8247] : PID: 12691 2010-08-13 14:05:42 scheduler[8247] : Pipes: in=0-0 / out=0-0 2010-08-13 14:05:42 scheduler[8247] : Attr: 'agent=copyright host=localhost ' 2010-08-13 14:05:42 scheduler[8247] : Command: '/usr/lib/fossology/agents/copyright/run.py --model /usr/share/fossology/model.dat --agent' 2010-08-13 14:05:42 scheduler[8247] : Parm: '' 2010-08-13 14:05:42 scheduler[8247] : Heartbeat: Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : State: Fri Aug 13 14:05:42 2010 2010-08-13 14:05:42 scheduler[8247] : Status: 1 (FREE) 2010-08-13 14:05:42 scheduler[8247] : Spawn: 3 at Fri Aug 13 14:00:50 2010 2010-08-13 14:05:42 scheduler[8247] : DB: 2010-08-13 14:05:42 scheduler[8247] : IsDB: 0 2010-08-13 14:05:42 scheduler[8247] : DBJobKey: 0 2010-08-13 14:05:42 scheduler[8247] : DBMSQrow: 0 2010-08-13 14:05:42 scheduler[8247] : DBagent: 24 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] FW: Db tables
Forgot to reply all... -Original Message- From: Laser, Mary Sent: Monday, August 16, 2010 3:36 PM To: 'McIntosh, Matt' Subject: RE: Db tables Hi Matt, 2 more things you should try: 1) check to make sure there is an entry for the copyright agent in the Scheduler.conf file (in /etc/fossology). 2) please stop the scheduler, rerun fo-posinstall - check for errors; restart the scheduler; check log file for errors. Email errors, if any. Mary -Original Message- From: McIntosh, Matt [mailto:matt_mcint...@mentor.com] Sent: Monday, August 16, 2010 1:48 PM To: Laser, Mary Subject: RE: Db tables Mary, I looked in the file and ran the sql to create the table, indexes, etc. but now it looks like the job isn't getting run. If I look at the job queue it's there but it isn't running and I look in the log and the copyright agent isn't showing as being run. I uploaded a new package and it ran all the way through the other agents, but stopped at the copyright. Any ideas? Thanks, -Matt -Original Message- From: Laser, Mary [mailto:mary.la...@hp.com] Sent: Monday, August 16, 2010 11:10 To: McIntosh, Matt; fossology@fossology.org Subject: RE: Db tables Hi Matt, Matt Taggart discovered shortly after we released. We've checked in a (1 line) fix: http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrev i sion=3348 Sorry for the inconvenience. Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Question: Fossology on Ubuntu
Hi Gurbax, A couple hints from http://fossology.org/download#debian_and_ubuntu_binary_packages Make sure you have this entry in /etc/apt/sources.list: deb http://fossology.org/debian/1.2~rc2 ./ And, update your packages with: sudo apt-get update Then, you should be able to run: sudo apt-get install fossology Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: fossology-agents-single fossology-scheduler-single fossology-web-single ... Is PostgreSQL installed config'd? You will need to have apache2 installed and config'd properly to serve up repo pages from /usr/share/fossology/www/. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert Sent: Thursday, August 05, 2010 10:21 AM To: fossology@fossology.org Subject: Re: [FOSSology] Question: Fossology on Ubuntu Forwarding to list. On Aug 5, 2010, at 10:01 AM, Deol, Gurbax wrote: Bob, I ran the sudo apt-get install fossology. When I try to go to my localhost where I installed fossology, it does not have the repo dir in there. I am thinking I am missing something here. Seems like it is not as easy as take the install package, install it and run. Something does not seem to be right eventho it installed fine without any errors. Should I install it from the source instead of apt-get install? From: Bob Gobeille [mailto:bob.gobei...@hp.com] Sent: Wednesday, August 04, 2010 4:31 PM To: Deol, Gurbax Subject: Re: Question: Fossology on Ubuntu Hello Gurbax, In the installation you created a website. So you should be able to find it at http://yourhostname/repo/ Did you apt-get install or install from source? Would you mind if we have this conversation on our public mailing list? That way other developers can join. Bob Gobeille On Aug 4, 2010, at 3:05 PM, Deol, Gurbax wrote: Hello Bob, We, at TI, are looking into Fossology as one of the tools that we may want to work with. I managed to install Fossology on Ubuntu. After running into some issues, I seems to be installed. I have been looking at the Fossology website to find out how to invoke this tool. I am not able to do find anything on it. Once the tool is installed, how can I launch it? Thank you so much for all your assistance. Regards, Gurbax Deol ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Question: Fossology on Ubuntu
Aha! You must Config Postgres to allow db connection from your server. At the very least, you must specify listen_addresses and possibly port number in the postgresql.conf file (probably in /etc/postgresql/8.3/main/). Look for this section in the config file: #--- # CONNECTIONS AND AUTHENTICATION #--- # - Connection Settings - listen_addresses = '*' # what IP address(es) to listen on; # comma-separated list of addresses; # defaults to 'localhost', '*' = all #listen_addresses = '*' port = 5432 ... Mary From: Deol, Gurbax [mailto:gur...@ti.com] Sent: Thursday, August 05, 2010 3:21 PM To: Laser, Mary; fossology@fossology.org Subject: RE: [FOSSology] Question: Fossology on Ubuntu Hello Mary, I had already installed fossology using the sudo apt-get install fossology command. It installed clean. I have the sources.list with the entry and configured the apache as well. PostgreSQL is installed but have not done anything to configure it. I am still not able to start it. When I try to run it from command line, I get unable to open database connection. Regards, Gurbax Deol ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] FOSSology 1.2.1 planning
Taggart pointed out on irc that we may want to include a pkgagent fix, too: http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3324 Thanks Matt. We'll do that. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Laser, Mary Sent: Thursday, July 29, 2010 1:40 PM To: fossology@fossology.org Subject: [FOSSology] FOSSology 1.2.1 planning Hi Everyone, So far, we have 2 bug fixes to incorporate into 1.2.1: 1. 7zip unpack fix : http://fossology.svn.sourceforge.net/viewvc/fossology?view=revisionrevision=3338 2. copyright table creation failure: http://fossology.svn.sourceforge.net/fossology/?rev=3347view=rev Mark estimates 2 days to 1. Tag, build and test debs. 2. Assuming #1 works, build final debs create a tarball. 3. Upload debs tarball to sourceforge. 4. Download tarball and use to verify FO update. In addition, Vincent will need time to build RPMs and I will post release notes email an announcement. I DO NOT plan to update fossology.fc.hp.com or repo.fossology.org as neither of these instances are affected by the bugs. Anything else? Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] Announcing FOSSology 1.2.0 Release
The FOSSology Project is pleased to announce the release of FOSSology 1.2.0. New in version 1.2.0: * Faster and more accurate license detection. * Copyright/URL/email scanner. * Ability to customize reporting categories. * Faster report (web page) generation. * Cataloging both RPM and Debian package data. For more information on the FOSSology project please visit http://fossology.org/. Download the software at http://fossology.org/download. -- About FOSSology -- FOSSology is a Free Open Source Software (FOSS) project built around an open and modular architecture for analyzing software. Existing modules include license analysis, meta data extraction, Copyright/URL/email scanner, RPM and Debian package analysis, and MIME type identification. This open source software tool analyzes a given set of software packages, and reports items such as the software licenses used by these packages. More than simply reporting, Package X uses license Y, the FOSSology tool attempts to analyze every file within the package to determine its license. The license report is thus an aggregate of all of the different licenses found to be in use by a package. A single package may be labeled as GPL but contain files that use other licenses (BSD, OSL, or any of the hundreds of other licenses). Even if an exact license is unknown, the license may be identifiable by common license phrases. The FOSSology Project started as an internal software development effort within Hewlett Packard's Open Source and Linux Organization. The tool evolved over several years at HP from a few simple shell scripts to the much more comprehensive tool you see today. Enjoy! The FOSSology team ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Does fossology work on Ruby, Rails, and JS code?
Hi Andy, FOSSology looks for licensing in whatever text it is given. The search method does not vary based on file type. So, for example, the text of foo.c and foo.js are searched the same way. If it encounters an exact file match of a file it's analyzed before, it will not reanalyze but will use the license result from the prior analysis. Are we understanding each other, yet? ;-) Mary From: Andy Holmes [mailto:ahol...@rollstream.com] Sent: Tuesday, July 06, 2010 4:09 PM To: Laser, Mary Subject: RE: Does fossology work on Ruby, Rails, and JS code? Hi Mary, Thanks for the quick reply. What I'm really wondering is, if I run FOSSology analysis on our Ruby on Rails and javascript code, would it report any licenses based on a known, current database of Ruby/RoR/javascript/etc files, or would it basically not find any licenses because Rails (or javascript) aren't the types of files that FOSSology or its database are intended to analyze. Did that clarify my question or make it even cloudier? Thanks! Andy From: Laser, Mary [mailto:mary.la...@hp.com] Sent: Tuesday, July 06, 2010 6:03 PM To: Andy Holmes; fossology@fossology.org Subject: RE: Does fossology work on Ruby, Rails, and JS code? Hi Andy, I think you're asking whether we've ever run FOSSology analysis on the many javascript, ruby, or rails code. Not specifically (AFAIK). However, if the code is embedded in some other code or included as part of a distro, it will get analyzed. Does that answer your question? Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Andy Holmes Sent: Tuesday, July 06, 2010 10:13 AM To: fossology@fossology.org Subject: [FOSSology] Does fossology work on Ruby, Rails, and JS code? Hi, Just trying to determine whether there's a database in fossology that contains the many javascript, ruby, or rails license info. There's obviously a ton of FOSS in these areas, but they aren't yet typically the kinds of code to which big project licensing concerns would apply. Anyone have any info on the ability to search javascript or RoR code for licensing? Thanks, Andy ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
[FOSSology] new RPM packages available for 1.2rc2
Hello FOSSOlogists, We now have a release candidate, version 2 (rc2) available for FOSSology version 1.2.0. We welcome and encourage everyone to download and test FOSSology 1.2.0 installation and usage. RC2 is a last step before releasing to make sure that the packages work and the the code has no regressions. Release notes are still in process and can be found at http://fossology.org/release_notes Subversion check out: svn co https://fossology.svn.sourceforge.net/svnroot/fossology/tags/1.2.0-rc2/ See message below for updated RPM packages. Debian packages are forthcoming. Mary From: Ma, Dong (vinc...@bas-becom-bj) Sent: Friday, July 02, 2010 3:55 AM Subject: new RPM packages available for 1.2rc2 Hi Team, Today I have created 1.2rc2 packages for rhel5/centos5 fedora10 fedora11 i386 and x86_64 platform. You can download from http://fossology.org/rpms/epel/testing/5/i386/fossology-1.2.0rc2-1.el5.i386.rpm -- rhel5/centos5 i386 http://fossology.org/rpms/epel/testing/5/x86_64/fossology-1.2.0rc2-1.el5.x86_64.rpm --- rhel5/centos5 x86_64 http://fossology.org/rpms/fedora/testing/10/i386/fossology-1.2.0rc2-1.fc10.i386.rpm --- fedora10 i386 http://fossology.org/rpms/fedora/testing/10/x86_64/fossology-1.2.0rc2-1.fc10.x86_64.rpm --- fedora10 x86_64 http://fossology.org/rpms/fedora/testing/11/i386/fossology-1.2.0rc2-1.fc11.i586.rpm --- fedora11 i386 http://fossology.org/rpms/fedora/testing/11/x86_64/fossology-1.2.0rc2-1.fc11.x86_64.rpm --- fedora11 x86_64 To use yum install, 1.you need add repo file to /etc/yum.repo.d/. 2. Epel repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/epel/testing/$releasever/$basearch enabled=0 gpgcheck=0 3. Fedora repo file need add following lines: # FOSSology release candidates and other special builds [fossology-testing] name=Fossology testing baseurl=http://fossology.org/rpms/fedora/testing/$releasever/$basearch enabled=0 gpgcheck=0 4. yum --enablerepo=fossology-testing install fossology Thanks, Best Regards, Vincent Ma(Ma Dong) ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Fossology and selftest agent failure
Hi Tommi, The selftest agent performs a number of verifications, mostly for agent consistency across a cluster. In your case, it appears you are running on a single system (localhost). However, it also checks for consistency of the license cache (License.bsam) against the license data stored in the database. This is documented in the selftest code: /* CheckLicenses(): Verify that every entry in License.bsam exists in the DB *and* on the file system. List each license file found. Returns 1 on success, 0 on failure. */ The database and License.bsam file a generated by fo-postinstall. It sorta looks like you forgot to run fo-postinstall. Can you please run/rerun it and verify it completes successfully? Thanks, Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Tommi Sahim?ki Sent: Thursday, June 17, 2010 12:57 AM To: fossology@fossology.org Subject: [FOSSology] Fossology and selftest agent failure Hi, I have a problem that I am not able to fix with my Fossology installation. Fossology was working fine before something went wrong with the database. The database got extremely poor in performance. Then I dropped the database and installed Fossology again. Now I get the following log entry when I start the Scheduler. What causes this license mismatch in selftest agent and how can I fix it? -- 2010-06-17 09:36:36 scheduler[31618] : *** Scheduler started, PID 31618 *** 2010-06-17 09:36:36 scheduler[15324] : *** Scheduler restarted successfully by fo_watchdog *** 2010-06-17 09:36:36 scheduler[31618] : Job queue reset. 2010-06-17 09:36:36 scheduler[31618] : Child[0] 'agent=wget host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[1] 'agent=unpack host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[2] 'agent=adj2nest host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[3] 'agent=filter_license host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[4] 'agent=license host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[5] 'agent=licinspect host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[6] 'agent=mimetype host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[7] 'agent=specagent host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[8] 'agent=filter_clean host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[9] 'agent=delagent host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[10] 'agent=sqlagent host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[11] 'agent=sqlagenthost host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[12] 'agent=pkgmetagetta host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[13] 'agent=fosscp_agent host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[14] 'agent=fo_notify host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:36 scheduler[31618] : Child[15] 'agent=selftest host=localhost ' state=FREE(1) @ Thu Jun 17 09:36:36 2010 2010-06-17 09:36:38 scheduler[31618] : FATAL: Configuration on agent 'localhost' differs from scheduler. 2010-06-17 09:36:38 scheduler[31618] : FATAL: The difference is License 2010-06-17 09:36:38 scheduler[31618] : Observed on scheduler system: License: 'GPL/v2/GPL v2 Preamble' = 82785F9BF7CD20FF761D4FAA353B91DB5A57E58C.7A32D42E7CCB0C251832A64E0585EFCB.2778 2010-06-17 09:36:38 scheduler[31618] : Mismatch on localhost: License: 'GPL/v2/GPL v2 Preamble' = 82785F9BF7CD20FF761D4FAA353B91DB5A57E58C.7AAgent adj2nest: Build version: 1.1.0, exported. 2010-06-17 09:36:38 scheduler[31618] : FATAL: Host 'localhost' failed self-test. 2010-06-17 09:36:38 scheduler[31618] : FATAL: Self Test failed. Inconsistent agent(s) detected. Exiting. Best Regards and thanks, Tommi Sahimäki Uudessa IE8 selaimessa on uudet pikatoiminnot. Lataa.http://www.microsoft.com/finland/windows/products/winfamily/ie/beta/default.mspx
Re: [FOSSology] Help, how to use fo_notify?
Hello Passion, (nice name!) 1) fo_notify uses the email address from the user definition. Use Admin - Users - Edit Users to access the page to specify an email address and enable email notification. 2) Enabling email notification in the step above should cause cp2foss to schedule fo_notify. Thanks for your questions! Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Zhao, Passion Sent: Thursday, March 25, 2010 3:50 AM To: fossology@fossology.org Subject: [FOSSology] Help, how to use fo_notify? Hi, Excuse me for asking two simple question about fo_notify. I find there is fo_notify agent if the source package is uploaded through web. But I can't find where to configure argument for fo_notify, such as email address, ... hopefully I can input a command string to be called in the fo_notify :) Second question, when use fossjobs -a, there is no fo_notify agent, does it mean cp2foss can't add this agent to upload task from command line? Thank you. -- Rgds, Passion Zhao ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] [FOSSology-commits] SF.net SVN: fossology:[2918] trunk/fossology/agents/copyright_analysis
Thanks for capturing the TODO notes in our svn tree. This will help you/us
insure the list is completed.
Mary
-Original Message-
From: fossology-commits-boun...@fossology.org
[mailto:fossology-commits-boun...@fossology.org] On Behalf Of
adamrba...@users.sourceforge.net
Sent: Monday, March 22, 2010 11:02 PM
To: fossology-comm...@fossology.org
Subject: [FOSSology-commits] SF.net SVN: fossology:[2918]
trunk/fossology/agents/copyright_analysis
Revision: 2918
http://fossology.svn.sourceforge.net/fossology/?rev=2918view=rev
Author: adamrbates
Date: 2010-03-23 05:02:21 + (Tue, 23 Mar 2010)
Log Message:
---
Added some comments to the copyright library functions. Also added a TODO file
with changes and fixes that need to be made to the agent.
Modified Paths:
--
trunk/fossology/agents/copyright_analysis/copyright_library.py
Added Paths:
---
trunk/fossology/agents/copyright_analysis/TODO
Added: trunk/fossology/agents/copyright_analysis/TODO
===
--- trunk/fossology/agents/copyright_analysis/TODO
(rev 0)
+++ trunk/fossology/agents/copyright_analysis/TODO 2010-03-23 05:02:21 UTC
(rev 2918)
@@ -0,0 +1,47 @@
+In copyright.py v 2903:
+
+line 87:
+print sys.stderr, 'ERROR: Something is broken. Could not
connect to database.'
+1) Something is broken. is pretty redundant.
+2) I'm pretty sure the actual postgres error message is more specific than
Could not connect to database. Why don't you just print that out instead of
your own message? The libpq functions to get the error code and error message
string are PQresStatus() and PQresultErrorMessage(). I notice that you write
the error message string in some cases but not others.
+
+
+line 100:
+print sys.stderr, 'You must specify a model file for all phases of
the algorithm.
+1) What do you mean for all phases of the algorithm? There is only one
switch -m (--model) for specifying the model. So to reduce ambiguity (i.e. is
there a different model file for each phase), why not just say You mush
specify a model file..
+
+lines 122-129:
+if options.analyze_from_file:
+files = [line.rstrip() for line in
open(options.analyze_from_file).readlines()]
+for file in files:
+results = library.label_file(file,model)
+print %s :: % (file)
+if len(results) == 0:
+print No copyrights
+for i in range(len(results)):
+print \t[%d:%d] % (results[i][0], results[i][1])
+1) each of those print's are going to come out in the log file as ERROR:
Did you mean for these to be printed with --verbose only? They are
also going to be printed on separate lines in the scheduler log, is that what
you wanted?
+
+You get the idea. Here is a summary of tips.
+1) Please don't print debug to the log unless it is requested with the verbose
option.
+2) There are 5 options you should be using when printing to the log:
+ - FATAL Technical and detailed errors.
+ - ERROR Human readable errors.
+ - WARNING Human readable warning.
+ - LOG Machine readable warning.
+ - DEBUG Debugging message.
+3) Make sure your messages mean something to the intended reader.
+4) Make your messages as explicit as reasonable. For example, line 158:
+print sys.stderr, 'ERROR: Something is broken. Could not open
Repo.'
+would be improved by including the path you are trying to open. This
extra info will tell the reader if their config path file is correct.
+ Another example is the dbconnect error I mentioned above.
+ Another example is line 189:
+print sys.stderr, ERROR: DB Access error,\n%s %
db.status()
+ printing the status code is fine, but the error message
(PQresultErrorMessage()) is better. Who wants to go look up the message from
the code when you can just print the message?
+5) Starting on line 201 you have a couple of except: where you print a
traceback. It would be easier to understand the log if you print out why you
are doing the traceback before you print it. Or is it there and I'm just not
seeing it?
+6) When you want to know if a table exists, don't (potentially) count every
record like on line 220:
+if db.access2('SELECT count(ct_pk) FROM copyright;') != 1:
+Quicker would be select ct_pk from copyright limit 1.
+7) Semicolons aren't needed at the end of your sql stmt unless you are
stringing a bunch of statements together. the semicolon is a statement
separator so it isn't needed if you are only sending a single stmt to the
postmaster.
+8) This statement in 6) brings up a question about db.access2(). Does
access2() distinguish between an invalid query (like a syntax error) and no
records returned? It's important to give an error if the command fails. Is
db.access2() is a wrapper around the same function in
Re: [FOSSology] Bug#531864: libextractor and rpath
This looks very promising wrt fossology. :-) I tried building a (virtual) fossology system last week to reproduce the error but, I had issues with my VM host. I think rando may have some real hardware where we can try the fix on fossology. Thanks Ralph! Mary -Original Message- From: Ralph Siemsen [mailto:ral...@netwinder.org] Sent: Saturday, March 06, 2010 9:06 AM To: Christian Grothoff Cc: Laser, Mary Subject: Re: Bug#531864: libextractor and rpath Hi Christian, I think we've solved the problem with help of ndurner on #gnunet. The problem is in parsing of the /proc/%u/maps file. I've reported this in your bug tracker https://ng.gnunet.org/bugs/view.php?id=1544 Regards, -Ralph On Fri, Mar 05, 2010 at 07:48:13AM +0100, Christian Grothoff wrote: Hi Ralph Mary, I just wanted to say that if you do need my help, I'm typically on freenode IRC (#gnunet) and my AIM handle is grothoffaim. I may not answer immediately (often AFK). Happy hacking! Christian On Thursday 04 March 2010 08:15:24 pm Ralph Siemsen wrote: Hello Christian, Thanks for the explanation of how libtdl loading is supposed to work. It seems every week, there is a new way of doing things. I know about LD_LIBRARY_PATH and the /etc/ld.so.conf* stuff. I am not a Fossolgy developer, so I don't know what they are doing that might interefere with libtdl. I can grep the source code, if there are any particular things I should look for. I can also run the tools under strace and/or ltrace, if that helps. I encountered problems with libextractor finding its plugins, on Fedora. The Debian bug report appears to show the same symptoms that I encoutered. The patch that Fedora applied seems to fix the issue, although it is certainly a hack. I would like to get to the bottom of the mystery, would you be willing to help understand why things are failing? If you are on IRC, we can chat there - I'm rfs on the #freenode channel on irc.oftc.net. Many thanks, -Ralph ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] RHEL5 RPM fossology-1.1.0-1.el5.x86_64.rpm broken? Urgent please...
Yes, it does fix the problem. However, as Christian points out here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531864#44, that may not be the best way to address this issue. He goes on to suggest additional steps to root cause the error. I'm in the process of doing that now. So far, I can report that the extract command seems to work fine. So, now, I am digging deeper into how fossology use libextractor and, in particular, the search path expected by fossology. Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Ralph Siemsen Sent: Thursday, March 04, 2010 11:20 AM To: Jeff Sheltren Cc: fossology@fossology.org Subject: Re: [FOSSology] RHEL5 RPM fossology-1.1.0-1.el5.x86_64.rpm broken? Urgent please... On Thu, Mar 04, 2010 at 09:41:42AM -0800, Jeff Sheltren wrote: https://bugzilla.redhat.com/show_bug.cgi?id=452504 Ralph, can you verify that this libextractor update fixes the problem you had with FOSSology? If so, I'll work on pushing it to EPEL. Yes, I tested it on F12 where it did indeed solve the problem. I reported this as Anonymous Tester here: https://admin.fedoraproject.org/updates/F11/FEDORA-2009-12138 -R ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduling failed for Agent agent_unpack
-Original Message-
1) Was the upload successful? Please check to see you have
objects in the Software Repository folder using the top
level Browse menu item.
Nothing is listed under the Software Repository. However,
Admin - Dashboard reports 68.16 GB of the repository disk
are used. This disk was freshly formatted specifically to
hold the repository and was empty when I started this, so
something is there. An examination of the file system shows
that the space is being used by a 68GB file called
d5961574ffc7efb1f89dc21d3ad680130520b386.a5f60815a90e75be98b41
88abf42812f.72908984320.
I'm not sure why the web interface says that the repository is empty.
du --si /srv
73G /srv/fossology/repository/localhost/gold/d5/96/15
73G /srv/fossology/repository/localhost/gold/d5/96
73G /srv/fossology/repository/localhost/gold/d5
73G /srv/fossology/repository/localhost/gold
4.1k /srv/fossology/repository/localhost/files/d5/96/15
8.2k /srv/fossology/repository/localhost/files/d5/96
13k /srv/fossology/repository/localhost/files/d5
17k /srv/fossology/repository/localhost/files
73G /srv/fossology/repository/localhost
73G /srv/fossology/repository
73G /srv/fossology
17k /srv/lost+found
73G /srv
The listing above indicates the upload was successfully stored in the gold
subdirectory. However, the absence of content in the files subdirectory
confirms that unpack did not run successfully. (Otherwise you would see a lot
of stuff in there.)
2. Before trying to upload anything, please do the following:
- sudo /etc/init.d/fossology stop
- sudo /usr/lib/fossology/fossology-scheduler -t -L stdout
(this runs the fossology scheduler in test mode with
the output to
stdout. It should end with no agent failures.if not there is
something wrong with the install no uploads will work
unless this test passes).
It appears to have run successfully.
Yup, your output looks normal.
snip
2010-03-02 18:06:37 scheduler[24947] : STATUS: All scheduler
agents are operational.
2010-03-02 18:06:37 scheduler[24947] : *** 0 agent failures.
Scheduler exiting.
3. The material you tried to upload... it wasn't a source
repository was it?
(cvs, svn, git, etc)... we don't support that type of upload at
this point.
I am trying to feed it the gNewSense repository for their
upcoming version 3.0.
/usr/bin/rsync -av -P --delete --delete-before
us.archive.gnewsense.org::metad /middle
That should be OK.
4. mary's suggestion of uploading a single file is a good one, does
that work?
I grabbed a copy of the GPL from gnu.org and fed it to the
one-shot license thing and it did report it as being the GPL.
One-shot is not quite the same as uploading a file.
But, the next part is problematic...
2) The scheduler appears to be having trouble queuing up
jobs (Failed to insert job record). Please check the log
file (/var/log/fossology/fossology.log) for additional
FOSSology errors AND the PostgreSQL log file
(/var/log/postgresql/podtgresql-ver-main.log) for db errors.
The Apache logs do not show anything interested, other than
my browsing of the web interface. Checking
/var/log/postgresql/postgresql-8.3-main.log did prove to be
interesting. I'm wondering if the syntax errors it's
complaining about are at fault? Here's everything from last
night's log...
snip
This is the root of your problem. There should NOT be a syntax error in the
INSERT statement below. Bob I are looking into it now and will figure a
workaround for you.
TTYL,
Mary
2010-03-01 22:39:15 PST ERROR: invalid input syntax for integer:
2010-03-01 22:39:15 PST STATEMENT: INSERT INTO job
(job_user_fk,job_queued,job_priority,job_email_notify,job_name
,job_upload_fk)
VALUES
('',now(),'0','fo...@localhost','unpack','3');
2010-03-01 22:39:15 PST ERROR: invalid input syntax for integer:
2010-03-01 22:39:15 PST STATEMENT: INSERT INTO job
(job_user_fk,job_queued,job_priority,job_email_notify,job_name
,job_upload_fk)
VALUES
('',now(),'0','fo...@localhost','unpack','3');
2010-03-01 22:39:15 PST ERROR: syntax error at or near
order at character 58
2010-03-01 22:39:15 PST STATEMENT: SELECT jq_pk, jq_job_fk
FROM jobqueue WHERE jq_job_fk = order by jq_pk desc limit 1;
2010-03-01 22:39:15 PST ERROR: invalid input syntax for integer:
2010-03-01 22:39:15 PST STATEMENT: INSERT INTO job
(job_user_fk,job_queued,job_priority,job_email_notify,job_name
,job_upload_fk)
VALUES
('',now(),'-1','fo...@localhost','fo_notify','3');
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduling failed for Agent agent_unpack
I've since done two things early this morning in response to Mark Donohoe's message. 1. I seleced Upload From URL and gave it this: http://archive.gnewsense.org/gnewsense-metad/installer/3.0~bet a1/i386/netboot/mini.iso I also downloaded this file and did Upload From File: http://us.archive.gnewsense.org/gnewsense-metad/gnewsense-secu rity/pool/updates/main/a/acpid/acpid_1.0.8.orig.tar.gz I did both of these ~4.5 hours ago and everything is still listed as queued (wget hasn't ever run to get mini.iso.) I will check the logs when I have access to the machine this evening to see what's going on and report back. Is the scheduler running? Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Scheduling failed for Agent agent_unpack
Hi Jason, Based on the error messages below, this could be one of several problem: 1) Was the upload successful? Please check to see you have objects in the Software Repository folder using the top level Browse menu item. Assuming the upload was successful, the next thing to check is why unpack didn't run. 2) The scheduler appears to be having trouble queuing up jobs (Failed to insert job record). Please check the log file (/var/log/fossology/fossology.log) for additional FOSSology errors AND the PostgreSQL log file (/var/log/postgresql/podtgresql-ver-main.log) for db errors. 3) Also, as a sanity check, can you upload a single file? Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Jason Self Sent: Tuesday, March 02, 2010 6:42 AM To: fossology@fossology.org Subject: [FOSSology] Scheduling failed for Agent agent_unpack I have a new installation of FOSSology 1.1 using the package from backports.org on Debian 5.0. The software I want to analyze is already mounted available to the webserver as /middle. I go to Upload From Server and enter /middle for the directory, enable alphabetized sub-folders, and enter Metad for the description viewable name. I also check all the buttons: Schedule License Analysis, Schedule MIME-type Analysis, Schedule Metadata Analysis and Schedule Spec File Analysis. I then saw lots of disk activity and there was a job queued. Life seemed good and I went to bed. This morning there were no job in the queue and FOSSology wasn't going anything (i.e., there was no CPU usage no disk activity. The machine was idle.) When I go to Browse, I see the root Software Repository level, but there isn't anything beneath it. The Dashboard confirms that 68.16 GB is used by the repository, so it seems that everything was added but no agents were started/ran? /var/log/fossology/fossology.log has the following information but I'm not sure why they failed. Where else can I look? snip 2010-03-01 21:53:11 scheduler[8653] : DEBUG[21]: Loading /middle/ 2010-03-01 22:22:42 scheduler[8653] : DEBUG[21]: Uploading to folder: Software Repository 2010-03-01 22:22:42 scheduler[8653] : DEBUG[21]: Uploading as 'Metad' 2010-03-01 22:22:42 scheduler[8653] : DEBUG[21]: Upload description: 'Metad' 2010-03-01 22:39:15 scheduler[8653] : ERROR: In thread 21: Scheduling failed for Agent agent_unpack 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: ERROR: Scheduling failed for Agent agent_unpack 2010-03-01 22:39:15 scheduler[8653] : ERROR: In thread 21: message: Failed to insert job record 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: ERROR message: Failed to insert job record 2010-03-01 22:39:15 scheduler[8653] : ERROR: In thread 21: Scheduling failed for Agent agent_license 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: ERROR: Scheduling failed for Agent agent_license 2010-03-01 22:39:15 scheduler[8653] : ERROR: In thread 21: message: Failed to insert job record 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: ERROR message: Failed to insert job record 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: Warning: Queueing email failed: 2010-03-01 22:39:15 scheduler[8653] : DEBUG[21]: Failed to insert job record, job fo_notify not created 2010-03-01 22:54:21 scheduler[8653] : Child[21] 'agent=fosscp_agent host=localhost ' state=FREEING(2) @ Mon Mar 1 22:54:21 2010 2010-03-01 22:54:21 scheduler[8653] : Child[21] 'agent=fosscp_agent host=localhost ' state=FREE(1) @ Mon Mar 1 22:54:21 2010 ___ ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] RHEL5 RPM fossology-1.1.0-1.el5.x86_64.rpm broken? Urgent please...
The issue is that the RPM (and perhaps .deb as well?) fails to fully install, because of pkgmetagetta being called in the postinstall script. If the script simply printed a warning and continued on, it would be fine. But right now you end up with an incomplete and non-functional installation, since the script exits prematurely. At least tht was my finding, I can't speak for the original poster. That is correct. Mary ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] RHEL5 RPM fossology-1.1.0-1.el5.x86_64.rpm broken? Urgent please...
You're right; you MUST have a generated License.bsam file to run fossology. Unfortunately, as Ralph pointed out earlier in this thread: The issue is that the RPM (and perhaps .deb as well?) fails to fully install, because of pkgmetagetta being called in the postinstall script. If the script simply printed a warning and continued on, it would be fine. But right now you end up with an incomplete and non-functional installation, since the script exits prematurely. Because of the failure, the License.bsam fie was not generated. The file is generated during fossinit. please try running sudo /usr/bin/fossinit Mary From: Furosh One [mailto:fur...@gmail.com] Sent: Thursday, February 25, 2010 4:57 PM To: fossology@fossology.org Cc: Gobeille, Robert; Laser, Mary Subject: Re: [FOSSology] RHEL5 RPM fossology-1.1.0-1.el5.x86_64.rpm broken? Urgent please... Anyone know how to get around the License.bsam agent not being in /var/lib/fossology/agents directory? Can I download this from somewhere or copy it from my other machine (ubuntu 9.04) and place it on this server (rhel5 x86_64)? I would suspect not but can't start fossology due to this error (so far). Usually I'll fix one error and hope and pray not more come up. Errors: == [r...@san-psip fossology_install]# /etc/init.d/fossology start Starting FOSSology job scheduler: scheduler. 2010-02-25 15:52:12 scheduler[27881] : FATAL: Scheduler error: Unable to access license cache '/var/lib/fossology/agents/License.bsam' 2010-02-25 15:52:12 scheduler[27881] : FATAL: Self Test failed. Inconsistent agent(s) detected. Exiting. [r...@san-psip fossology_install]# ls -l /var/lib/fossology/agents/ total 0 [r...@san-psip fossology_install]# ls -l /var/lib/fossology/agents/License.bsam ls: /var/lib/fossology/agents/License.bsam: No such file or directory Please advise, pretty please =/ -Gibran ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] quick Unpack question?
Hi Gibran, Unpack is a single threaded process. You can only run one instance per download. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Furosh One Sent: Tuesday, February 23, 2010 3:41 PM To: fossology@fossology.org Subject: [FOSSology] quick Unpack question? Can you have multiple unpacks running on a single server fossology setup? I've seen many scheduler.conf files and have only seen one unpack (which is one of the longer processes to wait for in our case). On my server with total 16 CPUs, is it possible to have more unpacks to help out? -Regards, Gibran ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] The license analysis algorithm?
Hi Mike, The current 1.1 release of FOSSology uses the bsam algorithm described here: http://fossology.org/symbolic_alignment_matrix. The next version, 1.2, will include an additional license analysis method called nomos, which is primarily a pattern matching algorithm with MANY rules. And finally, there is a new algorithm under development for version 1.3 which we believe will be faster and more accurate than either of the previous 2 methods. It is discussed here http://fossology.org/f1. HTH, Mary Hi fossologists, Is there a high-level description of the algorithm used to compare the set of licenses with the files in an upload? - Or better, a high-level description of the algorithm you want it to be, i.e. what you currently regard as the best solution? I've skimmed the develop docs without coming across this? Cheers, Mike -- Mike Kinghan, Test Lead, Symbian +44(0)776 5222 793 ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Backups take a very, very long time... Possible culprit?
Thanks for the explanation Vincent. I had a similar experience when I did the full backup because my BACKUPDIR was in the fossy user directory. My full backup (60GB) also took about 6 hours with a single rsync thread. I will look at the instructions and add something specific about excluding BACKUPDIR using the include ab file. Mary From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Ma, Dong (vinc...@gdcc-bj-most) Sent: Thursday, January 28, 2010 8:34 PM To: Furosh One Cc: fossology@fossology.org Subject: Re: [FOSSology] Backups take a very, very long time... Possible culprit? Hi Gibran, I think your point will be right, if BACKUPDIR is located in an area that is being backed up, there may be causing a loop. Why you mounted BACKUPDIR directory share with other servers in the repository, I didn't suggest you do this. Anyway, if you want to exclude BACKUPDIR use include ab files, just add like this: + /repository/ + /db/ - /* + /repository/clear[1-3]/ - /repository/* -/repository/clear1/backup/ The BACKUPDIR will not be backup. Also I should share my experience about backup whole repository time, there will be a long time to cost, in my test my repository upload a Fedora11 source ISO, the gold files is about 4.2G, and unupacked files cost more than 55G storage, I backup this more than 60G repository use 2 rsync thread, it cost about 4 hours to finished. This test can give you for a reference. If cross NFS, I think will be slower than this. So we also provide a only backup gold files solution here: http://fossology.org/task:fossology_data_backup_and_restore_instruction_-_gold_files Hope helps for you. Thanks, Vincent From: Furosh One [mailto:fur...@gmail.com] Sent: Friday, January 29, 2010 7:19 AM To: Ma, Dong (vinc...@gdcc-bj-most) Subject: Fwd: Backups take a very, very long time... Possible culprit? Hello Ma Dong, I know you gave me some good help last time with the include/exclude files in the backup-scripts for fossology. Just wanted to forward this to you directly in case you might not see the mailing list ones for a while. Any help is appreciated. -Regards, Gibran -- Forwarded message -- From: Furosh One fur...@gmail.commailto:fur...@gmail.com Date: Thu, Jan 28, 2010 at 1:30 PM Subject: Backups take a very, very long time... Possible culprit? To: fossology@fossology.orgmailto:fossology@fossology.org I've played with the backups of our multi-setup repositories and had a couple of questions. Although the script seems to work that I downloaded from : http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/utils/backup/ Our repos are fairly big in size and we are directly connected to a giga-switch, I don't think the bottleneck is the network here. It is using network because all hosts are mounted via NFS and the BACKUP_LOCATION is on one of those mounted shares (the one with the most space avail). But all 6 machines are on the same subnet, same switch, and shouldn't really need to go out to the router and then back again. I would think it would be quick as far as network. However, its possible that the BACKUPDIR is located in an area that is also being backed up, which may be causing a loop. BACKUPDIR=/srv/fossology/repository/clear1/BACKUPS There's a small debate here at the office whether this is a network issue or a backup issue, or simply just a lot of data and processing (compression) of the entire backup-script that is taking such a long time. I just caught the fact that include has +/repository/ (which may also include our BACKUPDIR). To give you an idea of how long it was taking I started the script at 9 AM and by 3 PM it still hadn't finished. It was probably just 50% completed. We needed to do a scan so we had to kill the backup job. Exisintg include ab files: === gmarq...@san-clear5:~/Backup_Scripts/fossy_BackupScripts$ cat backup_include_a.mod + /repository/ + /db/ - /* + /repository/clear[1-3]/ - /repository/* gmarq...@san-clear5:~/Backup_Scripts/fossy_BackupScripts$ cat backup_include_b.mod + /repository/ - /* + /repository/clear[4-6]/ - /repository/* === Do I need to add my BACKUPDIR to - exclude? How would I write that to be able to still include the repo in clear1? -/repository/clear1/BACKUPS/* -- Would this be the way to do it? And does the order in the file matter? Thanks! -Regards, Gibran ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] book section on fossology
Nice write-up. Thanks Bob. Mary -Original Message- From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert Sent: Tuesday, November 24, 2009 3:54 PM To: fossology@fossology.org Subject: [FOSSology] book section on fossology If anyone is interested I was asked to write a section about FOSSology for a new book on open source license compliance. The first draft is: http://fossology.org/~bobg/haddad/ Bob Gobeille ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
