Re: [FOSSology] 1.0.0 Release Candidate 2 available

[Laser, Mary]

Hi Martin,
I was not able to reproduce this error and I cant see anything wrong with the 
line referenced below in the current top-of-tree 
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/utils/fo-installdeps?revision=1754&view=markup

Can update to the latest revision and re-run utils/fo-installdeps?
Please capture all output and send to the list.

Thanks,
Mary

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Martin
> von Willebrand
> Sent: Wednesday, December 10, 2008 3:45 AM
> To: fossology@fossology.org
> Subject: Re: [FOSSology] 1.0.0 Release Candidate 2 available
>
>
> Hi,
>
> I tried rc2 on a freshly installed Ubuntu 6.06. Apt-get
> install did not work (dependencies did not resolve correctly
> and it didn't start installation of dependencies - sorry I
> lost the exact notices).
>
> Installation with scripts:
>
> Fo-installdeps gave the following error (I'm pretty busy with
> something else, so I just quickly note):
>
> utils/fo-installdeps: line 151: syntax error near unexpected
> token ´;;'
> utils/fo-installdeps: line 151: ´;;'
>
> Rgds,
> Martin
>
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Hang identified

[Laser, Mary]

Yes.  This is how I was able to reproduce the problem.  By forcing the log to 
rotate every 2 minutes, we were able to cause a scheduler hang AND we observed 
apache db connections hanging, too.

Mary

> -Original Message-
> From: fossology-boun...@fossology.org
> [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert
> Sent: Thursday, December 11, 2008 10:01 PM
> To: Krawetz, Neal
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] Hang identified
>
> Did you try letting Postgres rotate its own logs instead of
> using logrotate?
>
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-
> logging.html
>
> Bob
>
>
> On Dec 11, 2008, at 5:14 PM, Krawetz, Neal wrote:
>
> > Hi Folks,
> >
> > Mary and I just debugged the "every morning" scheduler
> hang. Not only
> > can we repeat it, we can make APACHE hang (without needing
> > FOSSology!).
> >
> > The problem:
> > When PostgreSQL 8.1 does a log rotate, it ends up hanging
> connections
> > to the DB.
> >
> > Since the Scheduler keeps one connection open forever, that
> connection
> > hangs. As a result, all of the scheduler hangs.
> >
> > With Apache, DB connections are sustained until they timeout. There
> > are also multiple DB connections. What we are seeing: some of the
> > Apache connections appear hung -- the PHP scripts that
> access the DB
> > return no data and sometimes the session resets. Simply reloading
> > tells Apache to use a different (random/round-robin) DB connection
> > that will probably work (unless you are unlucky and reload
> using the
> > same hung DB connection).
> >
> >
> > The test:
> > Mary configured postgresql to rotate its logs every 2 minutes. Poof:
> > PHP
> > scripts that connect to the DB under Apache begin to die -- SQL
> > queries act inconsistent (some return results, yet on reload they
> > return
> > nothing) and sessions randomly time out. Also, the scheduler hangs.
> >
> >
> > One possible workaround:
> > When postgresql rotates its logs, we need to restart the scheduler.
> > This
> > can be done in /etc/logrotate.d/postgresql-common.  Add a
> section to
> > the
> > post-rotate:
> >
> >postrotate
> >   /etc/init.d/fossology restart > /dev/null
> >
> > Alternately, this can be put in /etc/logrotate.d/fossology, but be
> > sure it runs AFTER postgres rotates, and not before.
> >
> > In either case, this is ugly since it means that a stopped
> scheduler
> > will be restarted the next time the logs rotate.
> >
> > I'm open to other solutions if anyone else knows a
> good/elegant way to
> > detect and reset DB connections.
> >
> >
> > FAQ:
> > Why haven't we seen the Apache hangs?
> > Apache disconnects from the DB after a period of inactivity.
> > Since logs rotate between 4:30am and 6:30am, nobody is
> around to play
> > with the UI. All connections time out so Apache does not notice the
> > rotation.
> >
> > Also, Apache's logs rotate around the same time as Postgres, and
> > apache's postrotate says to restart apache. Thus, any
> potentially hung
> > connections are released.
> >
> >
> > So to summarize:
> > The scheduler hangs are not due to the scheduler. They are due to
> > PostgreSQL screwing up active connections when they rotate
> their logs.
> >
> >-Neal
> >
> >
> > ___
> > 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] Hang identified

[Laser, Mary]

Hi bob,
redirect_stderr = on# Enable capturing of stderr into log
log_directory = 'pg_log'# enabled for 2 minute rotation test
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # enabled for 2 minute rotation 
test
log_rotation_age = 2# changing to every 2 minutes to try and hang 
scheduler.

WRT 2) below, I'm not sure I'm following you.  But, what we did was reloaded a 
page in the UI that generated a query.  Sometimes it would come back with the 
info we were requesting (query was carried out on a non-hung connection) and 
sometimes not (query was trying to use a hung connection).  Eventually the hung 
apache connection would log us out.

Mary

> -Original Message-
> From: Gobeille, Robert
> Sent: Friday, December 12, 2008 9:34 AM
> To: Laser, Mary
> Cc: Krawetz, Neal; fossology@fossology.org
> Subject: Re: [FOSSology] Hang identified
>
> Could I have some more details (or just confirm that the following is
> correct):
>
> 1) set log_rotation_age = 2 in postgresql.conf What do you
> set the other log_rotation variables to?
>
> 2) write a php script that opens a connection and loops on a
> query Report all errors returned by the query
>
> Result is that in ~2minute, a query will issue to the db, and
> will never return.
>
> Do I have this right?
>
> Thanks,
> Bob
>
>
>
> On Dec 12, 2008, at 8:57 AM, Laser, Mary wrote:
>
> > Yes.  This is how I was able to reproduce the problem.  By
> forcing the
> > log to rotate every 2 minutes, we were able to cause a
> scheduler hang
> > AND we observed apache db connections hanging, too.
> >
> > Mary
> >
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Hang identified

[Laser, Mary]

Nealk?

> -Original Message-
> From: Gobeille, Robert
> Sent: Friday, December 12, 2008 9:47 AM
> To: Laser, Mary
> Cc: Krawetz, Neal; fossology@fossology.org
> Subject: Re: [FOSSology] Hang identified
>
> Hi Mary,
> On 2), Neal said you could reproduce the problem without fossology.
> So what script did you use?
>
> Thanks,
> Bob
>
>
> On Dec 12, 2008, at 9:45 AM, Laser, Mary wrote:
>
> > Hi bob,
> > redirect_stderr = on# Enable capturing of stderr
> > into log
> > log_directory = 'pg_log'# enabled for 2 minute
> > rotation test
> > log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # enabled
> for 2 minute
> > rotation test
> > log_rotation_age = 2# changing to every 2 minutes to try
> > and hang scheduler.
> >
> > WRT 2) below, I'm not sure I'm following you.  But, what we did was
> > reloaded a page in the UI that generated a query.
> Sometimes it would
> > come back with the info we were requesting (query was
> carried out on a
> > non-hung connection) and sometimes not (query was trying to
> use a hung
> > connection).  Eventually the hung apache connection would
> log us out.
> >
> > Mary
> >
> >> -Original Message-
> >> From: Gobeille, Robert
> >> Sent: Friday, December 12, 2008 9:34 AM
> >> To: Laser, Mary
> >> Cc: Krawetz, Neal; fossology@fossology.org
> >> Subject: Re: [FOSSology] Hang identified
> >>
> >> Could I have some more details (or just confirm that the
> following is
> >> correct):
> >>
> >> 1) set log_rotation_age = 2 in postgresql.conf What do you set the
> >> other log_rotation variables to?
> >>
> >> 2) write a php script that opens a connection and loops on a query
> >> Report all errors returned by the query
> >>
> >> Result is that in ~2minute, a query will issue to the db, and will
> >> never return.
> >>
> >> Do I have this right?
> >>
> >> Thanks,
> >> Bob
> >>
> >>
> >>
> >> On Dec 12, 2008, at 8:57 AM, Laser, Mary wrote:
> >>
> >>> Yes.  This is how I was able to reproduce the problem.  By
> >> forcing the
> >>> log to rotate every 2 minutes, we were able to cause a
> >> scheduler hang
> >>> AND we observed apache db connections hanging, too.
> >>>
> >>> Mary
> >>>
>
>
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load default extractor libraries

[Laser, Mary]

Hi Theresa,
I seem to recall seeing this message many months ago when I tried installing 
fossology on a RedHat distro.  IIRC, the libraries had been installed under a 
different path than the debian path; /usr/lib/libextractor is the debian path.  
Can you verify where libextractor is being installed?

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Monday, December 15, 2008 7:19 AM
To: fossology@fossology.org
Subject: Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Anyone?

From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Friday, December 12, 2008 10:35 AM
To: fossology@fossology.org
Subject: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi gang,
We tried installing rc1 on both Centos5 and Ubuntu and have the same error on 
both:

FATAL: Failed to load default extractor libraries.
FATAL: '/usr/lib/fossology/agents/pkgmetagetta -i' failed to initialize

Anyone know what we're missing?
We do have libextractor loaded, but is that causing the first fatal error?

Appreciate any help or thoughts!

Theresa Trauger
Software CM Tools
Foundation Repository IRAD
https://lmforge.isgs.lmco.com
610-531-1525 (M8253)
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load default extractor libraries

[Laser, Mary]

No, 64 bit should not be a problem.  (Most of our systems are 64 bit.)
In order to help diagnose the problem and a possible workaround, can you please 
create a link:

 /usr/lib/libextractor ->  /usr/lib64/libextractor


From: Trauger, Theresa J [mailto:theresa.j.trau...@lmco.com]
Sent: Monday, December 15, 2008 10:04 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi Mary,
We have it here: /usr/lib64/libextractor
Is it a problem that we are running on a 64 bit machine?

From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Monday, December 15, 2008 12:01 PM
To: Trauger, Theresa J; fossology@fossology.org
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi Theresa,
I seem to recall seeing this message many months ago when I tried installing 
fossology on a RedHat distro.  IIRC, the libraries had been installed under a 
different path than the debian path; /usr/lib/libextractor is the debian path.  
Can you verify where libextractor is being installed?

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Monday, December 15, 2008 7:19 AM
To: fossology@fossology.org
Subject: Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries
Anyone?

From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Friday, December 12, 2008 10:35 AM
To: fossology@fossology.org
Subject: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi gang,
We tried installing rc1 on both Centos5 and Ubuntu and have the same error on 
both:

FATAL: Failed to load default extractor libraries.
FATAL: '/usr/lib/fossology/agents/pkgmetagetta -i' failed to initialize

Anyone know what we're missing?
We do have libextractor loaded, but is that causing the first fatal error?

Appreciate any help or thoughts!

Theresa Trauger
Software CM Tools
Foundation Repository IRAD
https://lmforge.isgs.lmco.com
610-531-1525 (M8253)
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load default extractor libraries

[Laser, Mary]

yw :-)

We are running 0.5.16-2 on debian etch (it's pretty old, too).  You can find 
newer versions at
ftp://ftp.gnu.org/gnu/libextractor/


From: Trauger, Theresa J [mailto:theresa.j.trau...@lmco.com]
Sent: Monday, December 15, 2008 12:18 PM
To: Laser, Mary
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Thanks for the suggestion, I passed it on to our install guy!  Also, what 
version of libextractor is necessary?  I noticed that we are running an old 
version and I've asked that it be bumped to the latest.
Thanks again for your suggestion!
T

From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Monday, December 15, 2008 12:09 PM
To: Trauger, Theresa J; fossology@fossology.org
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

No, 64 bit should not be a problem.  (Most of our systems are 64 bit.)
In order to help diagnose the problem and a possible workaround, can you please 
create a link:

 /usr/lib/libextractor ->  /usr/lib64/libextractor


From: Trauger, Theresa J [mailto:theresa.j.trau...@lmco.com]
Sent: Monday, December 15, 2008 10:04 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries
Hi Mary,
We have it here: /usr/lib64/libextractor
Is it a problem that we are running on a 64 bit machine?

From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Monday, December 15, 2008 12:01 PM
To: Trauger, Theresa J; fossology@fossology.org
Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi Theresa,
I seem to recall seeing this message many months ago when I tried installing 
fossology on a RedHat distro.  IIRC, the libraries had been installed under a 
different path than the debian path; /usr/lib/libextractor is the debian path.  
Can you verify where libextractor is being installed?

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Monday, December 15, 2008 7:19 AM
To: fossology@fossology.org
Subject: Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries
Anyone?

From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Friday, December 12, 2008 10:35 AM
To: fossology@fossology.org
Subject: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed to load 
default extractor libraries

Hi gang,
We tried installing rc1 on both Centos5 and Ubuntu and have the same error on 
both:

FATAL: Failed to load default extractor libraries.
FATAL: '/usr/lib/fossology/agents/pkgmetagetta -i' failed to initialize

Anyone know what we're missing?
We do have libextractor loaded, but is that causing the first fatal error?

Appreciate any help or thoughts!

Theresa Trauger
Software CM Tools
Foundation Repository IRAD
https://lmforge.isgs.lmco.com
610-531-1525 (M8253)
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] progress: 1.0.0-rc1 install troubles -- FATAL: Failed to load default extractor libraries

[Laser, Mary]

Thanks for the update and feedback.
Mary

> -Original Message-
> From: fossology-boun...@fossology.org
> [mailto:fossology-boun...@fossology.org] On Behalf Of
> Trauger, Theresa J
> Sent: Wednesday, December 17, 2008 8:09 AM
> To: fossology@fossology.org
> Subject: [FOSSology] progress: 1.0.0-rc1 install troubles --
> FATAL: Failed to load default extractor libraries
>
> We seem to have passed that fatal error hurdle!
> Thanks everyone for their suggestions.  I'll be back if I
> can't get it running today!
> T
>
>
>
> -Original Message-
> From:, Matthew
> Sent: Tuesday, December 16, 2008 4:56 PM
> To: Trauger, Theresa J
> Subject: RE: [FOSSology] 1.0.0-rc1 install troubles -- FATAL:
> Failed to load default extractor libraries
>
> I updated ld.so.conf on the two Debian-based boxes, and got a
> similar result to the CentOS box.  The log files are
> /root/fo-post-afterldso.txt on both boxes if you want to
> look.  I think that's progress! :)  Also, the Debian boxes
> don't throw the PHP errors that CentOS does.
>
> The update file is /etc/ld.so.conf.d/libextractor.conf, which
> contains the path (/usr/lib/libextractor) on one line.  You
> should probably submit this back to the fossology guys so
> they can include this in their packages.
>
> Matt
> >
> > -Original Message-
> > From: m...@lackof.org [mailto:m...@lackof.org] On Behalf Of Matt
> Taggart
> > Sent: Monday, December 15, 2008 5:28 PM
> > To: Trauger, Theresa J
> > Cc: Laser, Mary; fossology@fossology.org
> > Subject: Re: [FOSSology] 1.0.0-rc1 install troubles -- FATAL: Failed
> to
> > load default extractor libraries
> >
> > > We have it here: /usr/lib64/libextractor
> > >
> > > Is it a problem that we are running on a 64 bit machine?
> >
> > Is that path on the CentOS machine?
> >
> > On the Ubuntu system do you have libextractor-plugins installed?
> >
> > On the CentOS system did you do an upstream install of
> libextractor or
> are
> > you using packages from somewhere?
> >
> > I don't think that path is a problem, as long as the
> library is in the
> > search path. If you did an upstream install maybe you need
> to add that
> > directory to /etc/ld.so.conf and run ldconfig so ld knows about it?
> >
> > Thanks,
> >
> > --
> > Matt Taggart
> > tagg...@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] Announcing FOSSology 1.0.0 Release

[Laser, Mary]

As a result of the new release, http://repo.fossology.org/ will be updated to 
the newest version today, Thursday morning, MST.  There may be a short downtime 
during the upgrade but any jobs running will be rescheduled upon restarting the 
new fossology scheduler .

Mary Laser
Fossology.org

> -Original Message-
> From: fossology-boun...@fossology.org
> [mailto:fossology-boun...@fossology.org] On Behalf Of Stangel, Daniel
> Sent: Wednesday, December 17, 2008 5:48 PM
> To: fossology@fossology.org
> Subject: [FOSSology] Announcing FOSSology 1.0.0 Release
>
> The FOSSology Project is pleased to announce the release of
> FOSSology 1.0.0
>
> New in version 1.0.0:
>
>   * Massive improvements to web-based user interface
> responsiveness, 50x or better speed-up, with retrieval and
> display of license reports in just seconds, for even the
> biggest reports.
>   * Huge improvements in license analysis speed, as much as
> 10 times faster, with analysis of full linux distribution DVD
> images in 24-48 hours (depending on system performance, CPU,
> memory, etc)
>   * License detection accuracy improvements - the library of
> licenses and terms that we search for and report has been
> carefully tuned based on lots and lots of real-world testing
>   * Completely redesigned build and release system, makes
> building and installing FOSSology from source code much
> easier, and also enables creation of FOSSology packages for
> common Linux distributions
>   * Software packaging of FOSSology for the Debian Linux
> distribution - For the first time, the FOSSology project has
> a complete set of packages to enable simple apt-based
> installation of FOSSology on most DEB-based Linux systems.
>   * (beta) Software packaging of FOSSology for the Fedora
> distribution, using native RPM packages.  These RPM packages
> should provide streamlined installation on most RPM-based
> systems (Redhat, SuSE, etc)
>   * Automated test suite to provide web-UI testing and
> validation by the FOSSology project and any other downstream users
>   * Self-test agent that allows FOSSology to inspect itself
> and report on common configuration problems that could impact
> FOSSology operation
>
> View the complete release notes for FOSSology 1.0.0 for more details:
> http://fossology.org/release_notes
>
> For more information on the FOSSology project and to download
> the software, please visit http://fossology.org/
>
>
> -- About FOSSology --
>
> Now celebrating its first birthday as an open source software
> project, 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, 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
>
>
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Announcing FOSSology 1.0.0 Release

[Laser, Mary]

Hello again FOSSologists,

During the fossology upgrade on http://repo.fossology.org/, there were also 
kernel upgrades applied that require a reboot.  I will be rebooting all systems 
at the completion of the fossology upgrade.  At this time (1PM, MST) 3 of 6 
systems have completed the upgrade.

I will send a final notice when all systems have been rebooted and fossology is 
back "online".

Thanks,
Mary

> -Original Message-
> From: Laser, Mary
> Sent: Thursday, December 18, 2008 9:31 AM
> To: Stangel, Daniel; fossology@fossology.org
> Subject: RE: Announcing FOSSology 1.0.0 Release
>
> As a result of the new release, http://repo.fossology.org/
> will be updated to the newest version today, Thursday
> morning, MST.  There may be a short downtime during the
> upgrade but any jobs running will be rescheduled upon
> restarting the new fossology scheduler .
>
> Mary Laser
> Fossology.org
>
> > -Original Message-
> > From: fossology-boun...@fossology.org
> > [mailto:fossology-boun...@fossology.org] On Behalf Of
> Stangel, Daniel
> > Sent: Wednesday, December 17, 2008 5:48 PM
> > To: fossology@fossology.org
> > Subject: [FOSSology] Announcing FOSSology 1.0.0 Release
> >
> > The FOSSology Project is pleased to announce the release of
> FOSSology
> > 1.0.0
> >
> > New in version 1.0.0:
> >
> >   * Massive improvements to web-based user interface
> responsiveness,
> > 50x or better speed-up, with retrieval and display of
> license reports
> > in just seconds, for even the biggest reports.
> >   * Huge improvements in license analysis speed, as much as
> 10 times
> > faster, with analysis of full linux distribution DVD images
> in 24-48
> > hours (depending on system performance, CPU, memory, etc)
> >   * License detection accuracy improvements - the library
> of licenses
> > and terms that we search for and report has been carefully
> tuned based
> > on lots and lots of real-world testing
> >   * Completely redesigned build and release system, makes
> building and
> > installing FOSSology from source code much easier, and also enables
> > creation of FOSSology packages for common Linux distributions
> >   * Software packaging of FOSSology for the Debian Linux
> distribution
> > - For the first time, the FOSSology project has a complete set of
> > packages to enable simple apt-based installation of
> FOSSology on most
> > DEB-based Linux systems.
> >   * (beta) Software packaging of FOSSology for the Fedora
> > distribution, using native RPM packages.  These RPM packages should
> > provide streamlined installation on most RPM-based systems (Redhat,
> > SuSE, etc)
> >   * Automated test suite to provide web-UI testing and
> validation by
> > the FOSSology project and any other downstream users
> >   * Self-test agent that allows FOSSology to inspect itself
> and report
> > on common configuration problems that could impact
> FOSSology operation
> >
> > View the complete release notes for FOSSology 1.0.0 for
> more details:
> > http://fossology.org/release_notes
> >
> > For more information on the FOSSology project and to download the
> > software, please visit http://fossology.org/
> >
> >
> > -- About FOSSology --
> >
> > Now celebrating its first birthday as an open source
> software project,
> > 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, 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
> >
> >
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

[FOSSology] FW: FOSSology RPM Packaging

[Laser, Mary]

Hi George & Shay,
I'm forwarding your inquiry to the fossology mailing list to include others 
that may be interested in testing RPM packaging.  (If you haven't done so 
already, please subscribe to the mailing list at http://fossology.org/ and use 
the list for future inquires. Thanks!)


Bruno -
Where/How do we download a test rpm for fossology?  (is this it? 
ftp://ftp.mondorescue.org/test/fedora/10/)

Thanks!
Mary



-Original Message-
From: george.p...@prudential.com [mailto:george.p...@prudential.com]
Sent: Tuesday, January 06, 2009 7:12 AM
To: Laser, Mary
Cc: shay.st...@prudential.com
Subject: FOSSology RPM Packaging

Mary,

I will be working with Shay Stowe on testing FOSSology 1.0 at Prudential.
We are interested in working with you on the RPM packaging - and we are going 
to first work with CentOS (which for all practical purposes is
Redhat)

If there is something that you can point us to and/or send us - this will allow 
Shay to start the process of installing FOSSology and getting it up
and running that will allow us to get actual experience with it.   Then we
have a series of tests we plan on running to see if its a viable solution for 
us.


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] FW: FOSSology RPM Packaging

[Laser, Mary]

Thanks Bruno!

George & Shay will be testing on Centos but, I'll let them respond directly 
regarding their needs for a specific RHELish package.

Mary

> -Original Message-
> From: Cornec, Bruno (Open Source and Linux Technology Architect)
> Sent: Tuesday, January 06, 2009 10:12 AM
> To: Laser, Mary
> Cc: fossology@fossology.org; shay.st...@prudential.com;
> george.p...@prudential.com
> Subject: Re: FW: FOSSology RPM Packaging
>
> Laser, Mary said on Tue, Jan 06, 2009 at 04:14:07PM +:
>
> > Bruno -
> > Where/How do we download a test rpm for fossology?  (is this it?
> > ftp://ftp.mondorescue.org/test/fedora/10/)
>
> Yes, that's the one I made. Now if you want rather a specific
> rhel-like package, please indicate a versio/arch and I'll try
> to add what is needed to my RHEL VM to geenrate those.
>
> Greetings,
> Bruno.
> --
> Linux Profession Lead EMEA  / Open Source Evangelist \
> HP C&I EMEA IET
> http://www.mondorescue.org / HP/Intel Solution Center \
> http://hpintelco.net
> Des infos sur Linux?  http://www.HyPer-Linux.org
> http://www.hp.com/linux
> La musique ancienne?  http://www.musique-ancienne.org
> http://www.medieval.org
>
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] email notification design review

[Laser, Mary]

Hi Mark,
Thanks for sending this out - it looks good!  I have 2 comments/suggestions:
 
1)  Under your assumptions, you may want to add "the agent will assume the 
email address given is correct".

2)  Adding a column to the user table for the email agent to timestamp when the 
notification was sent doesn't feel right.  
A) It will only record the most recent email sent - what if the user submits 
multiple jobs and wants email notifications for each?  Although, the user will 
receive multiple email notifications, only the most recent one will be recorded 
in the DB.
B) Adding an email timestamp column in the user table doesn't seem like the 
right place to store this info.  Maybe the email agent should maintain it's own 
table with info like, user, job id, timestamp, etc...

My 2 cents.
M 

> -Original Message-
> From: Donohoe, Mark 
> Sent: Monday, February 02, 2009 11:23 AM
> To: oslo.tools-team
> Subject: email notification design review
> 
> Folks,
> 
> This is mostly for Bob and Chan, but anyone is welcome to 
> read it and provide feedback.
> 
> The first draft of the email notification design is ready for 
> review.  
> Please review and provide feedback.  You can find it at:
> 
> http://fossology.org/email-design
> 
> Thanks for your time and comments.
> 
> --
> Mark Donohoe
> ALPS/OSTT, Cupertino CA.
> fossology.org
> 
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] adding a license phrase in 1.0.0

[Laser, Mary]

Hi Theresa,
Yes, that is the correct way to add a license template at this time.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Trauger, Theresa J
Sent: Tuesday, February 03, 2009 9:09 AM
To: fossology@fossology.org
Subject: [FOSSology] adding a license phrase in 1.0.0

Hi gang, I just wanted to verify that adding a license phrase still entails 
rebuilding the s/w?
http://fossology.org/how_to_add_a_license_template_or_license_phrase_and_re-analyze_licenses

The Phrase category is catching our "Company Name Proprietary" banners, and it 
would be nice to be able to quickly put these in their own category.
Thanks for all the good work!


Theresa Trauger
Software CM Tools
Foundation Repository IRAD
https://lmforge.isgs.lmco.com
610-531-1525 (M8253)
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Installation problem

[Laser, Mary]

Hi Daniel,
As Matt suggests below, this is most likely an authentication config issue.  In 
order to fix it, you'll probably need to edit the 
/etc/postgresql/8.1/main/pg_hba.conf file.  Here's a snippet from one of my 
test systems:

# "local" is for Unix domain socket connections only
#local   all all   ident sameuser
local   all all   md5
# IPv4 local connections:
hostall all 127.0.0.1/32  md5
hostall all 127.0.1.1/32  md5
# IPv6 local connections:
hostall all ::1/128   md5

HTH!
Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Matt Taggart
> Sent: Friday, February 13, 2009 4:37 AM
> To: daniel.goe...@clearstream.com
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] Installation problem
> 
> > Hi all,
> > 
> > after the installation of Fossology (last version), we do have a 
> > problem with the scheduler, here is the error message:
> [snip]
> > Would you have any idea why we encounter this issue?
> 
> Check you postgresql log and see if it's seeing the 
> connection attempt and denying it, that might give a clue.
> 
> Maybe you don't have the right auth methods enabled?
> What distro are you on?
> 
> Thanks,
> 
> --
> Matt Taggart
> tagg...@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

[FOSSology] Question about documentation; State vs. Stage

[Laser, Mary]

Hi Nealk,
I am reading/editing a document you wrote originally and getting confused about 
a section titled "Plugin States" where you discuss "plugins stages" 
(http://fossology.org/how_to_extend_the_user_interface#plugin_states).  I see 
states and stages as two very different things.  

Is the section titled correctly?

Mary Laser
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Question about documentation; State vs. Stage

[Laser, Mary]

OK, that makes sense.  
And, one further note of clarification; I don't see any direct mapping between 
the states discussed in the docs and the PLUGIN_STATEs defined in FO-Plugin.  
Correct?

Mary


> > Hi Nealk,
> > I am reading/editing a document you wrote originally and 
> getting confused about a section titled "Plugin States" where 
> you discuss "plugins stages" 
> (http://fossology.org/how_to_extend_the_user_interface#plugin_
> states).  I see states and stages as two very different things.  
> > 
> > Is the section titled correctly?
> > 
> > Mary Laser
> 
> Hi Mary,
> 
> You're right -- the section text is a little skimpy.
> 
> The "States" are denoted by each of the bold function. 
> Install, Initialize, PostInitialize, OutputOpen, etc.
> 
> The "Stages" are the section subheadings (Installation, 
> Run-Time Initialization, Output, Cleanup).
> 
> The picture for "Plugin Process
> Flow" (http://fossology.org/ui_architecture_overview) shows 
> the order that the stages are processed and which states are invoked.
> 
> Would you mind revising the paragraph after the heading 
> "Plugin States"?
> You'll probably also want to link in the picture.
> 
>  -Neal
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

[FOSSology] Location of License.bsam file

[Laser, Mary]

Hi Dave,
I think the issue you are experiencing has to do with the location of 
License.bsam, depending on if you install with a tarball or the deb package.  

The method for adding a license template on fossology.org was written BEFORE 
the deb package existed so, it assumes FOSSology was installed with a tarball.

The tarball install will create License.bsam in:
/var/local/lib/fossology/agents/License.bsam

The deb package will put License.bsam in:
/var/lib/fossology/agents/License.bsam

After you have added you new template and recreated the License.bsam file, 
please try copying it to the deb location and see if that fixes your issue.

Mary

Mary Laser
ALPS/OSTT
(970)898-0878 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Performance issue on FOSSOLogy server.

[Laser, Mary]

Hi Bennis,

You can specify number of CPUs in the Scheduler.conf file as described in 
http://fossology.org/scheduler#configuring_the_scheduler

your entry for a single localhost should start like this:

%Host localhost 2 1

HTH,
Mary

From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Monday, March 30, 2009 9:11 AM
To: fossology@fossology.org
Subject: [FOSSology] Performance issue on FOSSOLogy server.



I have installed Fossology on a virtual server and we are using two CPU's but 
the application is running on one CPU . Is there a way to change the 
configuration to use  both the CPU? Please let me know.

Thanks,
Bennis


top - 12:08:59 up 23:50,  1 user,  load average: 1.08, 1.03, 1.01
Tasks: 113 total,   2 running, 111 sleeping,   0 stopped,   0 zombie
Cpu(s): 50.2%us,  0.1%sy,  0.0%ni, 49.6%id,  0.0%wa,  0.0%hi,  0.1%si,  0.0%st
Mem:904188k total,   886644k used,17544k free, 2920k buffers
Swap:  2096440k total,   162552k used,  1933888k free,   343720k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
32396 fossy 25   0  491m 487m 2456 R  100 55.2 409:57.50 bsam-engine


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] "File contents are not available in the repository"

[Laser, Mary]

Hi Simon,
This "smells like" a permissions problem.  Please check your repository 
directory, where the uploaded files are stored in your filesystem, for the 
correct permissions.  It should look similar to this:

$ ls -al /srv/fossology/repository/localhost
total 20
drwxrws--- 5 fossy fossy 4096 2008-03-04 15:40 .
drwxrws--- 6 fossy fossy 4096 2009-03-27 17:23 ..
drwxrws--- 2 fossy fossy 4096 2009-03-27 16:42 files
drwxrws--- 2 fossy fossy 4096 2009-03-27 16:29 gold
drwxrws--- 2 fossy fossy 4096 2009-03-27 16:29 license

Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of  Simon
Sent: Monday, March 30, 2009 2:23 PM
To: fossology@fossology.org
Subject: [FOSSology] "File contents are not available in the repository"

Dear all,

I ran into a problem when viewing the content of a zip file uploaded to the 
server.

For the sake of demonstration, I have created a very simple a.zip, which 
contains a java file a.java.  In the a.java, I have put APL 2.0 in the 
beginning as comment.

I uploaded this zip file to fossology, which then completes all the analysis 
per my request.  When I view the license of the a.zip, it showed me there is a 
reference to APL 2.0.  When I click on the link Show, the fossology web site 
showed that a link to A.java.  So far so good.

But when I click on the link to A.java, it prompts me "File contents are not 
available in the repository.".  Why is this?

I noticed that some other file types would be shown, such as .properties, etc.  
What configuration controls what filetypes will be shown and what will not?

Thank you,

--
Simon
西门烧雪
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] "File contents are not available in the repository"

[Laser, Mary]

This should not happen :-(  and, I have not been able to reproduce it.  
I'll need more clues to try to diagnose your problem.

Are you able to view ANY of your uploads?
Have you verified the unpack of your zip file was successful and it's contents 
is on your file system?
Have you check the scheduler log file (/var/log/fossology/fossology.log) for 
errors during processing of your upload?

Mary



> -Original Message-
> From: 西门烧雪 Simon [mailto:sekatsi...@gmail.com] 
> Sent: Tuesday, March 31, 2009 6:35 AM
> To: Laser, Mary
> Subject: Re: [FOSSology] "File contents are not available in 
> the repository"
> 
> Mary,
> 
> The files were already in the correct permissions:
> 
> $ ls -al /srv/fossology/repository/localhost/
> total 48
> drwxrws---   5 fossy fossy 4096 Mar 30 16:11 .
> drwxrws---   4 fossy fossy 4096 Mar 30 15:57 ..
> drwxrws--- 258 fossy fossy 4096 Mar 30 15:58 files
> drwxrws---   4 fossy fossy 4096 Mar 30 16:07 gold
> drwxrws---   3 fossy fossy 4096 Mar 30 16:11 license
> -rw-r--r--   1 fossy fossy   25 Mar 30 15:38 selftest.txt
> 
> Please advise.  Thank you.
> 
> 2009/3/30 Laser, Mary 
> >
> > Hi Simon,
> > This "smells like" a permissions problem.  Please check 
> your repository directory, where the uploaded files are 
> stored in your filesystem, for the correct permissions.  It 
> should look similar to this:
> >
> > $ ls -al /srv/fossology/repository/localhost
> > total 20
> > drwxrws--- 5 fossy fossy 4096 2008-03-04 15:40 .
> > drwxrws--- 6 fossy fossy 4096 2009-03-27 17:23 ..
> > drwxrws--- 2 fossy fossy 4096 2009-03-27 16:42 files
> > drwxrws--- 2 fossy fossy 4096 2009-03-27 16:29 gold
> > drwxrws--- 2 fossy fossy 4096 2009-03-27 16:29 license
> >
> > Mary
> >
> > 
> > From: fossology-boun...@fossology.org 
> > [mailto:fossology-boun...@fossology.org] On Behalf Of  Simon
> > Sent: Monday, March 30, 2009 2:23 PM
> > To: fossology@fossology.org
> > Subject: [FOSSology] "File contents are not available in 
> the repository"
> >
> > Dear all,
> >
> > I ran into a problem when viewing the content of a zip file 
> uploaded to the server.
> >
> > For the sake of demonstration, I have created a very simple 
> a.zip, which contains a java file a.java.  In the a.java, I 
> have put APL 2.0 in the beginning as comment.
> >
> > I uploaded this zip file to fossology, which then completes 
> all the analysis per my request.  When I view the license of 
> the a.zip, it showed me there is a reference to APL 2.0.  
> When I click on the link Show, the fossology web site showed 
> that a link to A.java.  So far so good.
> >
> > But when I click on the link to A.java, it prompts me "File 
> contents are not available in the repository.".  Why is this?
> >
> > I noticed that some other file types would be shown, such 
> as .properties, etc.  What configuration controls what 
> filetypes will be shown and what will not?
> >
> > Thank you,
> >
> > --
> > Simon
> > 西门烧雪
> 
> 
> 
> --
> Simon
> 西门烧雪
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Performance issue on FOSSOLogy server.

[Laser, Mary]

Excellent!


From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Thursday, April 02, 2009 11:50 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: Performance issue on FOSSOLogy server.


I modified and it is much faster now.
Thanks,
Bennis


From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Monday, March 30, 2009 3:49 PM
To: Abraham Bennis; fossology@fossology.org
Subject: RE: Performance issue on FOSSOLogy server.

Hi Bennis,

You can specify number of CPUs in the Scheduler.conf file as described in 
http://fossology.org/scheduler#configuring_the_scheduler

your entry for a single localhost should start like this:

%Host localhost 2 1

HTH,
Mary

From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Monday, March 30, 2009 9:11 AM
To: fossology@fossology.org
Subject: [FOSSology] Performance issue on FOSSOLogy server.



I have installed Fossology on a virtual server and we are using two CPU's but 
the application is running on one CPU . Is there a way to change the 
configuration to use  both the CPU? Please let me know.

Thanks,
Bennis


top - 12:08:59 up 23:50,  1 user,  load average: 1.08, 1.03, 1.01
Tasks: 113 total,   2 running, 111 sleeping,   0 stopped,   0 zombie
Cpu(s): 50.2%us,  0.1%sy,  0.0%ni, 49.6%id,  0.0%wa,  0.0%hi,  0.1%si,  0.0%st
Mem:904188k total,   886644k used,17544k free, 2920k buffers
Swap:  2096440k total,   162552k used,  1933888k free,   343720k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
32396 fossy 25   0  491m 487m 2456 R  100 55.2 409:57.50 bsam-engine


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] considering a 1.0.1 release

[Laser, Mary]

 
Yes to both; they are safe AND we want them.
Mary

> 
> > agents/foss_license_agent/Licenses/Raw/Corporate/Intel.meta
> > agents/foss_license_agent/Licenses/Raw/Corporate/Intel reference 
> > agents/foss_license_agent/Licenses/Raw/Corporate/Intel 
> reference.meta 
> > 
> agents/foss_license_agent/Licenses/Raw/Corporate/Microsoft/Microsoft 
> > SDK EULA 
> > 
> agents/foss_license_agent/Licenses/Raw/Corporate/Microsoft/Microsoft 
> > SDK EULA.meta 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/Free Software 
> > License B v1.0 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/Free Software 
> > License B v1.0.meta 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/Free Software 
> > License B v1.1 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/Free Software 
> > License B v1.1.meta 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/SGI FSL B v1.0 
> > agents/foss_license_agent/Licenses/Raw/Corporate/SGI/SGI FSL B 
> > v1.0.meta 
> agents/foss_license_agent/Licenses/Raw/Corporate/SGI/SGI FSL 
> > B v1.1 
> agents/foss_license_agent/Licenses/Raw/Corporate/SGI/SGI FSL B 
> > v1.1.meta agents/foss_license_agent/Licenses/Raw/CPL/Common Public 
> > License v0.5 
> agents/foss_license_agent/Licenses/Raw/CPL/Common Public 
> > License v0.5.meta
> 
> I think these are all safe and we want them, Mary?
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] RPM packaging

[Laser, Mary]

Welcome Vincent!

Mary Laser 

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert
> Sent: Monday, April 13, 2009 9:36 AM
> To: fossology@fossology.org
> Cc: Ma, Dong (vinc...@gdcc-bj-most)
> Subject: [FOSSology] RPM packaging
> 
> Welcome Vincent!
> 
> Good news everyone.  Vincent just joined the fossology family 
> and he is going to be working on the RPM packaging.  So 
> please help him get up to speed as he asks questions (and 
> reads the list archive).
> 
> 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

Re: [FOSSology] Multi user installation

[Laser, Mary]

Hi Bennis,
Documentation describing why you might want to use multi system setup can be 
found here: http://fossology.org/multi-system_setup

(I don't know which version you are trying to install but, let's assume it's 
1.0.0.)

Installation instructions can be found in 
/usr/share/doc/fossology-common/INSTALL.multi (if you installed using apt-get) 
OR the file INSTALL.multi in the fossology home directory (if you built and 
installed from a tarball).  You can also see these instructions in the 
sourceforge subversion repository:  
http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.0.0/INSTALL.multi?view=markup.

As for libextractor, there are instructions in the INSTALL file for library 
dependencies.  This file can also be viewed here: 
http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.0.0/INSTALL?view=markup.

HTH,
Mary




> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> Sent: Monday, April 20, 2009 2:39 PM
> To: fossology@fossology.org
> Subject: [FOSSology] Multi user installation
> 
> I was trying to install Fossology on a multi system ( 
> Fossology App on one system and Database on the other ). 
> Installation Document with FOSSOlogy was not clear.
>  
> Please help me out to find these things.
> Documentation for Multi system installation ?
> Where can I find reliable source for libltdl / libextractor  ?
> 
> Thanks,
> Bennis
> 
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] new sendmail(1) dependency

[Laser, Mary]

Thanks Matt! 

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Matt Taggart
> Sent: Friday, April 24, 2009 8:57 PM
> To: Cornec, Bruno (Open Source and Linux Technology Architect)
> Cc: fossology@fossology.org
> Subject: [FOSSology] new sendmail(1) dependency
> 
> Hi,
> 
> This mail is mostly to Bruno, but others might want to know too...
> 
> rando and I have been talking about the install/package 
> implications of his new email notification work. He uses a 
> php function that calls sendmail(1) to send notifications. 
> This is an optional feature controlled by a checkbox in the 
> user profile.
> 
> I have added this optional requirement to the INSTALL 
> document, added it to fo-installdeps, and added it as a 
> "Suggests" level package dependency for the debian packaging. 
> (SVN #2014)
> 
> Bruno,
> You might consider adding an rpm dependency on "smtpdaemon" 
> to your .spec if you want this to just work. But it is an 
> optional feature so if there is a way to do a less strict 
> requirement use that I think.
> 
> Thanks,
> 
> --
> Matt Taggart
> tagg...@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] Scheduler startup problem

[Laser, Mary]

 
Hello Federico,
mkschedconf is a utility to create a configuration file for the scheduler, 
Scheduler.conf.  The first message below indicates you are unable to run it; 
perhaps it is missing or the permissions are wrong.  The second error occurs 
because the configuration file is not created.

Please check to see that the mkschedconf is available and executable:
/usr/lib/fossology/mkschedconf  (debian install)
/usr/local/lib/fossology/mkschedconf(built from source)

Mary


> Subject: [FOSSology] Scheduler startup problem
> 
> Hi all,
> 
> After installing succesfully Fossology on a debian-etch 
> system (both with the binary package and building from 
> source) i get the following errors on the log:
> 
> FATAL: Unable to run mkschedconf for self-test.
> FATAL: Inconsistent agent(s) detected.
> 
> and the scheduler doesn't start. The rest of the system 
> appears to be working (database access, web frontend, 
> individual agents...). 
> 
> Any clue of what is happening?
> 
> Thanks a lot,
> --
> Federico 
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Scheduler startup problem

[Laser, Mary]

Your permissions are correct.  

Can you please try running the utility directly (with the -L option)?  You 
should see something like this:

la...@mysystem:~$ /usr/lib/fossology/mkschedconf -L
agent=wget host=localhost | /usr/lib/fossology/agents/wget_agent -d 
/var/lib/fossology/agents
agent=unpack host=localhost | /usr/lib/fossology/agents/engine-shell unpack 
'/usr/lib/fossology/agents/ununpack -d /srv/fossology/repository/ununpack/%{U} 
-qRCQx'
agent=adj2nest host=localhost | /usr/lib/fossology/agents/adj2nest
agent=filter_license host=localhost | /usr/lib/fossology/agents/Filter_License
agent=filter_license host=localhost | /usr/lib/fossology/agents/Filter_License
agent=filter_license host=localhost | /usr/lib/fossology/agents/Filter_License
agent=license host=localhost | /usr/lib/fossology/agents/bsam-engine -L 20 -A 0 
-B 60 -G 15 -M 10 -E -T license -O n -- - /var/lib/fossology/agents/License.bsam
agent=license host=localhost | /usr/lib/fossology/agents/bsam-engine -L 20 -A 0 
-B 60 -G 15 -M 10 -E -T license -O n -- - /var/lib/fossology/agents/License.bsam
agent=licinspect host=localhost | /usr/lib/fossology/agents/licinspect
agent=licinspect host=localhost | /usr/lib/fossology/agents/licinspect
agent=mimetype host=localhost | /usr/lib/fossology/agents/mimetype
agent=mimetype host=localhost | /usr/lib/fossology/agents/mimetype
agent=mimetype host=localhost | /usr/lib/fossology/agents/mimetype
agent=specagent host=localhost | /usr/lib/fossology/agents/specagent
agent=filter_clean host=localhost | /usr/lib/fossology/agents/filter_clean -s
agent=delagent host=localhost | /usr/lib/fossology/agents/delagent -s
agent=sqlagent host=localhost | /usr/lib/fossology/agents/sqlagent
agent=sqlagenthost host=localhost | /usr/lib/fossology/agents/sqlagent -a sql
agent=pkgmetagetta host=localhost | /usr/lib/fossology/agents/pkgmetagetta
agent=pkgmetagetta host=localhost | /usr/lib/fossology/agents/pkgmetagetta
agent=pkgmetagetta host=localhost | /usr/lib/fossology/agents/pkgmetagetta
agent=fosscp_agent host=localhost | /usr/lib/fossology/agents/engine-shell 
fosscp_agent '/usr/bin/cp2foss %{*}'

If you get this result, please run it again and redirect the output to the 
location for the Scheduler.conf file (/etc/fossology/Scheduler.conf).  After 
that, try starting the fossology scheduler again.  If it fails, please send me 
the entire log.

Thanks,
Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of 
> Federico Gimenez Nieto
> Sent: Wednesday, April 29, 2009 4:36 AM
> To: fossology@fossology.org
> Subject: Re: [FOSSology] Scheduler startup problem
> 
> Hi Mary, thanks for your reply,
> 
> I currently have the application installed through the debian 
> package, the output of 'ls mkschedconf -all' at /usr/lib/fossology is:
> 
> -rwxr-xr-x  1 root root 19788 Dec 17 22:18 mkschedconf
> 
> The directories 'usr', 'lib' and 'fossology' also belong to 
> root:root and are readable and executable by all. Are these 
> the correct permission settings?
> 
> Cheers,
> --
> Federico
> 
> El Mar, 28 de Abril de 2009, 9:29 pm, Laser, Mary escribió:
> >
> > Hello Federico,
> > mkschedconf is a utility to create a configuration file for the 
> > scheduler, Scheduler.conf.  The first message below 
> indicates you are 
> > unable to run it; perhaps it is missing or the permissions 
> are wrong.  
> > The second error occurs because the configuration file is 
> not created.
> >
> > Please check to see that the mkschedconf is available and 
> executable:
> > /usr/lib/fossology/mkschedconf(debian install)
> > /usr/local/lib/fossology/mkschedconf(built from source)
> >
> > Mary
> >
> >
> >> Subject: [FOSSology] Scheduler startup problem
> >>
> >> Hi all,
> >>
> >> After installing succesfully Fossology on a debian-etch 
> system (both 
> >> with the binary package and building from
> >> source) i get the following errors on the log:
> >>
> >> FATAL: Unable to run mkschedconf for self-test.
> >> FATAL: Inconsistent agent(s) detected.
> >>
> >> and the scheduler doesn't start. The rest of the system 
> appears to be 
> >> working (database access, web frontend, individual agents...).
> >>
> >> Any clue of what is happening?
> >>
> >> Thanks a lot,
> >> --
> >> Federico
> >>
> 
> 
> --
> Federico Gimenez Nieto
> fgime...@coit.es
> 
> 
> ___
> 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 Digest, Vol 18, Issue 23

[Laser, Mary]

We are in the process of tagging a 1.1.0 release candidate.  An announcement 
will be made on this mailing list when it's ready for testing.

Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> Sent: Thursday, April 30, 2009 12:05 PM
> To: fossology@fossology.org
> Subject: Re: [FOSSology] fossology Digest, Vol 18, Issue 23
> 
>  When is fossology 1.0.1 going to be released. If so, please 
> send me the URL.
> 
> 
> Thanks,
> Bennis
> 
> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of 
> fossology-requ...@fossology.org
> Sent: Thursday, April 30, 2009 1:00 PM
> To: fossology@fossology.org
> Subject: fossology Digest, Vol 18, Issue 23
> 
> Send fossology mailing list submissions to
>   fossology@fossology.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://fossology.org/mailman/listinfo/fossology
> or, via email, send a message with subject or body 'help' to
>   fossology-requ...@fossology.org
> 
> You can reach the person managing the list at
>   fossology-ow...@fossology.org
> 
> When replying, please edit your Subject line so it is more 
> specific than "Re: Contents of fossology digest..."
> 
> 
> Today's Topics:
> 
>1. Re: [FOSSology-commits] SF.net SVN: fossology:[2040]
>   trunk/fossology/Makefile.conf (Matt Taggart)
>2. Re: [FOSSology-commits] SF.net SVN: fossology:[2052]
>   trunk/fossology/Makefile.conf (Matt Taggart)
>3. Re: [FOSSology-commits] SF.net SVN: fossology:[2052]
>   trunk/fossology/Makefile.conf (Stangel, Daniel)
>4. Re: [FOSSology-commits] SF.net SVN: fossology:[2052]
>   trunk/fossology/Makefile.conf (Matt Taggart)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 29 Apr 2009 16:12:35 -0700
> From: Matt Taggart 
> Subject: Re: [FOSSology] [FOSSology-commits] SF.net SVN:
>   fossology:[2040] trunk/fossology/Makefile.conf
> To: fossology@fossology.org
> Cc: fossology-comm...@fossology.org
> Message-ID: <20090429231235.966fbd6...@taggart.lackof.org>
> Content-Type: text/plain; charset=us-ascii
> 
> > Modified: trunk/fossology/Makefile.conf 
> > ===
> > --- trunk/fossology/Makefile.conf   2009-04-28 22:27:58 UTC 
> (rev 2039)
> > +++ trunk/fossology/Makefile.conf   2009-04-28 23:02:24 UTC 
> (rev 2040)
> > @@ -130,14 +130,17 @@
> >  DB=$(DBPATH)/libfossdb.a
> >  REPOPATH=$(TOP)/devel/libfossrepo
> >  REPO=$(REPOPATH)/libfossrepo.a
> > +AGENTLIBPATH=$(TOP)/devel/libfossagent
> > +AGENTLIB=$(REPOPATH)/libfossagent.a
> >  
> >  # for use when only generating objects and not linking
> >  CFLAGS_DBO=-I$(DBPATH) -L$(DBPATH)
> > -CFLAGS_REPOO=-I$(REPOPATH) -L$(REPOPATH)
> > +CFLAGS_REPO=-I$(REPOPATH) -L$(REPOPATH)
> 
> ^^^ This was not a typo, I know the name is confusing but the 
> O refers to 'objects'. I will revert.
> 
> --
> Matt Taggart
> tagg...@fossology.org
> 
> 
> 
> 
> --
> 
> Message: 2
> Date: Wed, 29 Apr 2009 16:19:31 -0700
> From: Matt Taggart 
> Subject: Re: [FOSSology] [FOSSology-commits] SF.net SVN:
>   fossology:[2052] trunk/fossology/Makefile.conf
> To: fossology@fossology.org
> Cc: fossology-comm...@fossology.org
> Message-ID: <20090429231931.f3b83d6...@taggart.lackof.org>
> Content-Type: text/plain; charset=us-ascii
> 
> >  # the version of our project
> > -VERSION=1.1.0~20090205
> > +VERSION=1.1.0~rc1
> 
> Top of tree doesn't even build, I think it's a little early 
> to be tagging rc1. In the past I did it _right_ before I was 
> going to generate tarballs and debian packages, which was 
> when we had been through some testing and thought it was 
> pretty much ready for release.
> 
> --
> Matt Taggart
> tagg...@fossology.org
> 
> 
> 
> 
> --
> 
> Message: 3
> Date: Wed, 29 Apr 2009 23:31:30 +
> From: "Stangel, Daniel" 
> Subject: Re: [FOSSology] [FOSSology-commits] SF.net SVN:
>   fossology:[2052] trunk/fossology/Makefile.conf
> To: "fossology@fossology.org" 
> Cc: "fossology-comm...@fossology.org"
>   
> Message-ID:
>   
> <8e9f698a1b44234cac23227bb1eeefa53d64fd9...@gvw1098exb.america
> s.hpqcorp.net>
>   
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Matt,
> 
> On Wed Apr 29, 2009 at 05:19 PM -0700, Matt Taggart wrote:
> >>  # the version of our project
> >> -VERSION=1.1.0~20090205
> >> +VERSION=1.1.0~rc1
> > 
> > Top of tree doesn't even build, I think it's a little early to be
> > tagging rc1. In the past I did it _right_ before I was going to
> > generate tarballs and debian packages, which was when we had been
> > through some testing and thought it was pretty much ready 
> for release.
> 
> We're not generating RC1 from top of tree, because bobg has 
> already begun making changes that break the build;  I'll be

Re: [FOSSology] License Analysis

[Laser, Mary]

Hi Abraham,
>From what I can tell, this looks OK.  And the behavior you describe, 
>"scheduler is continuously running for license analysis", is normal.  The 
>scheduler runs continuously waiting for requests (usually made thru the UI).  
>When a request is made, the scheduler spawns the jobs necessary to perform the 
>request.  In the case of your license analysis below, there are over 20M items 
>being inspected for licenses!  The scheduler will spawn millions of jobs to 
>examine each of these items.  Depending on your hardware and if these are new 
>or recurring objects, the analysis can take quite a long time (days).

You can always check your log file (/var/log/fossology/fossology.log) for 
errors if you suspect something is wrong.  The scheduler and jobs spawned by 
the scheduler log errors & information there.
Mary



> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> Sent: Tuesday, May 12, 2009 10:19 AM
> To: fossology@fossology.org
> Subject: [FOSSology] License Analysis
> 
>  
> I have installed fossology. I could upload a file for license 
> analysis. But the scheduler is continously running for  
> license analysis. Why this task is taking many days to 
> complete and please see the details below. Please correct me 
> if I am doing something wrong.
> 
> Thanks,
> Bennis
> 
> 
> 93 unpack  95,152 items
> Elapsed scheduled:
> Elapsed running: 
> 00:17:14
> 00:17:14
>  2009-04-23 09:38
> 94 / 93 adj2nest  1 item
> Elapsed scheduled:
> Elapsed running: 
> 00:01:01
> 00:01:01
>  2009-04-23 09:39
> Job/Dependency Job Name: license Reset | Delete | Priority: < 0 >
> 144 / 94 sqlagent  1 item
> Elapsed scheduled:
> Elapsed running: 
> 00:00:02
> 00:00:02
>  2009-05-07 15:50
> 145 / 144 filter_license  0 items
> Elapsed scheduled:
> Elapsed running: 
> 00:00:00
> 00:00:00
>  2009-05-07 15:51
> 146 / 145 license  20,220,516 items
> Elapsed scheduled:
> Elapsed running: 
> 1 day 02:41:26
> 1 day 02:26:01 
>   
> 147 / 146 licinspect   
> 148 / 147 filter_clean   
> 149 / 148 sqlagent   
> 150 / 148 sqlagent  
> 
> 
> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of 
> fossology-requ...@fossology.org
> Sent: Monday, May 11, 2009 1:00 PM
> To: fossology@fossology.org
> Subject: fossology Digest, Vol 19, Issue 9
> 
> Send fossology mailing list submissions to
>   fossology@fossology.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://fossology.org/mailman/listinfo/fossology
> or, via email, send a message with subject or body 'help' to
>   fossology-requ...@fossology.org
> 
> You can reach the person managing the list at
>   fossology-ow...@fossology.org
> 
> When replying, please edit your Subject line so it is more 
> specific than "Re: Contents of fossology digest..."
> 
> 
> Today's Topics:
> 
>1. Re: Question (Mark Donohoe)
> 
> 
> --
> 
> Message: 1
> Date: Mon, 11 May 2009 10:46:22 -0700
> From: Mark Donohoe 
> Subject: Re: [FOSSology] Question
> To: daniel.goe...@clearstream.com
> Cc: "fossology@fossology.org" 
> Message-ID: <4a08646e.1080...@hp.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> daniel.goe...@clearstream.com wrote:
> >
> > Dear user group,
> >
> > we have installed the patch but I am still not able to load 
> a complete 
> > directory. I have also tried to use the command line 
> cp2foss but I am 
> > also having some issues, please see below the syntax of the command 
> > line and the error message. Any help is more than welcome.
> >
> > /srv/fossology/bin/cp2foss  -f "Software Repository/Folder_dg" -d 
> > "Test spantax" -n "Test spantax"
> > /opt/fossy/SPANTAX/SPANTAX/appl/script
> >
> > PHP Warning:  Call-time pass-by-reference has been deprecated - 
> > argument passed by value;  If you would like to pass it by 
> reference, 
> > modify the declaration of menu_insert_r().  If you would like to 
> > enable call-time pass-by-reference, you can set 
> > allow_call_time_pass_reference to true in your INI file.  However, 
> > future versions may not support this any longer.  in 
> > /srv/fossology/share/fossology/www/common/common-menu.php 
> on line 244 
> > PHP Notice:  Undefined index:  updcache in 
> > /srv/fossology/share/fossology/www/plugins/ui-license.php 
> on line 114 
> > PHP Notice:  Undefined offset:  1 in 
> > /srv/fossology/share/fossology/www/common/common-parm.php 
> on line 98 
> > PHP Notice:  Undefined variable: PageHex in 
> > /srv/fossology/share/fossology/www/plugins/ui-view.php on 
> line 92 PHP
> > Notice:  Undefined variable: PageText in 
> > /srv/fossology/share/fossology/www/plugins/ui-view.php on 
> line 93 PHP
> > Notice:  Undefined variable: PageText in 
> > /srv/fossology/share/fossology/www/plugins/ui-view.php on line 94 
> > Loading /opt/fossy/SPANTAX/SPANTA

Re: [FOSSology] License Analysis

[Laser, Mary]

Hi Abraham,
This looks like a possible permissions problem.  You should have a repository 
directory (/srv/fossology/repository) with sub-directories (files & gold) owned 
by www-data:

laser@:/srv/fossology/repository$<mailto:laser@:/srv/fossology/repository$>
 ls -al
total 36
drwxrws--- 8 fossyfossy 4096 2009-05-12 18:22 .
drwxr-xr-x 4 root root  4096 2008-11-11 13:49 ..
drwxrws--- 2 www-data fossy 4096 2009-05-07 13:52 files
drwxrws--- 2 www-data fossy 4096 2009-05-07 13:52 gold

Please check your installation to see if it looks similar to the example above.

Thanks,
Mary





From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Thursday, May 14, 2009 8:17 AM
To: fossology@fossology.org
Subject: Re: [FOSSology] License Analysis (Laser, Mary)


I  couldn't find anything wrong in the fossology logs . But when I could see 
something junk coming to the SSH Client. Do you know why this is  displayed on 
the SSH Client ?

Thanks
Bennis


WARNING: File not in the repository (license 
86601A3957448BA52B49676214B9F51CACD08E6B.61316B4112879470690A73D474C4EF1B.142832)
WARNING: File not in the repository (license 
83D5FAAFF7A035E72AFA3BBC3C3BF30D805452FF.EEF86F8B8010C81C10EC7D5D3815CD2C.142826)
WARNING: File not in the repository (license 
7919D7A4EA54A4D03563939412B1A5DECA2F8D4D.60C37224420410AA05FA1D8998358E24.142743)
WARNING: File not in the repository (license 
E5DCD04EE035867E1F4800C6AB69CB2619F6C905.E25856F42E79071AE60A2BC52CE0E941.142687)
WARNING: File not in the repository (license 
F759D376D53BA19D4ED8460BD76F1BDA78D5C03D.DA1D49291A21629B9763A5E4ABF008BF.142474)
WARNING: File not in the repository (license 
8B13CB2D1E8CA6648859990A56D67CD39C91CA24.2E860085CB76B327B406E5E776B382D2.142449)
WARNING: File not in the repository (license 
67483025BBB1795AD2A40FB4BD9576D2C15F9474.E366629689C65F06037947844FD1CE0C.142440)
WARNING: File not in the repository (license 
B296F4A25ECA300A23DC6E403D3B62F832F049FD.9E2333260347F3842DBC85E48A1DD53D.142306)
WARNING: File not in the repository (license 
B567A1036759D9FD93573907BB0C2AA91C209396.C412288525066553A095E753D60E8BFC.142184)
WARNING: File not in the repository (license 
B562B9B3C112BD950131B39F13AF6ACF695B4563.10B046F5158C712573D9103CC55371CE.142007)
WARNING: File not in the repository (license 
8793105731F5576BED52C2C468281EA626381CF7.FC741E36088BD2FDC2173ED377F18265.141876)
WARNING: File not in the repository (license 
E4F4707F741DEE87AFD5719E1C552BE0D41CB91F.1533827BFB0CCF07FDFE9577B4E55A5B.141756)
WARNING: File not in the repository (license 
FA044D17E0ACF77BC0B21314A84667BC7AEF7E27.8FD598FDC1AC4AE82CB3BD5B53AB440F.141705)
WARNING: File not in the repository (license 
B14EB8F6293E879CB3873C030A6E456A6F23D5D8.41B9EFF5ADCF7A37C64053340721FF75.141625)
WARNING: File not in the repository (license 
9C4DC68BC2E62872896E8CFD781839698DD558F5.61DF9B0013E2ACFA8B14C2AC4D637615.141535)
WARNING: File not in the repository (license 
50452D85C7337CC6D437C4B8F702EF28D8B6C3A3.4594ED7ABBAAB8EA8C8FE1D5D9E8C9DD.141498)
WARNING: File not in the repository (license 
212376B446869B8A3CD7E8596D78C611E0A1F860.2C292AD145001B06E7C5AE810C1DC9D9.141460)
WARNING: File not in the repository (license 
EC110395C23CB2E6233AD440FDCAE06661FC8CBD.63D64BA4EB4F5E597FEC276D390FBCE7.141298)
WARNING: File not in the repository (license 
4E0F7FF3331A37650234F3AFEEA097BBD4163907.07F8212E212459A2202E1DAA7C319448.141141)
WARNING: File not in the repository (license 
DF095AA5B33C61B694F969A6A999E6E2FA977AEE.568BB696D308E679E5A3FFFACC435FD2.141060)
WARNING: File not in the repository (license 
A56306A53EC6AFCCC9C42CCF9D20B7C9DF85C08E.006A0777261CC648119BD174DD6D228B.140968)
WARNING: File not in the repository (license 
39C6BE715BAC9967E9242DC184F9EEB5710F7FE4.4CAB40330CA8F2590A17A84BB004083D.140849)
WARNING: File not in the repository (license 
2AA348D9F1F1792F8702F91C7D60175BF5B7E6FE.97163F9A4E97BD1345787BA3B30C6D0E.140799)
WARNING: File not in the repository (license 
EF6771D8C7B43283053909DBE3174D8AAAB37852.FC003169E6E2326236F7489DB02B7734.140536)
WARNING: File not in the repository (license 
71A900A8B7F89D80A5BF1790279EC61D7E7EC3DB.9CE46E8CA2F0384C3274806D49DA0DA7.140453)
WARNING: File not in the repository (license 
43FB1B2FECE8530919227D2C007410BD83C8E95E.5DF7E9713841818E33A3E15743B1F240.140408)
WARNING: File not in the repository (license 
F8AC4828415F2FC943F956DFF3835246365FB842.145EC47AF2039F2B1693DD3E4402F329.140105)
WARNING: File not in the repository (license 
8125E99CC793897EA10DFB91CA2C752B1A8DE9DC.0983225AF214B4CE1E9F852FC152CD2E.139996)


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Error while uploading

[Laser, Mary]

Hi Bennis,
In an earlier email (attached) you mentioned you were using a multi-system 
setup.  Is this still the case?  This is a VERY important distinction.  Please 
open the attached email, follow the instructions therein and let me know your 
result.

Thanks,
Mary


From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Monday, May 18, 2009 10:38 AM
To: Laser, Mary; fossology@fossology.org
Subject: Error while uploading


I am not able to upload files for license analyzing. Please see the error 
below. At the same time I am not seeing the folder called "gold" "files".  
Please advice.


--
ERROR upload 12 Failed to import file into the repository (RepImport=1). LOG 
upload 12 Failed to import /tmp/phpwnzvRE-uploaded from /tmp/phpwnzvRE-uploaded 
into gold 
8B9DEC2B11954542F0477B0753508DA1AE1D25CE.2BD616FFA4D43BCE5CB9C8BCD294B6AB.247850297
 The file has been uploaded. It is upload #12.

# ls /tmp
ossology-configs.A14814  fossology-configs.sG2988  random.vintelaflush
fossology-configs.A14980  fossology-configs.T20759  updatecron.bak
fossology-configs.Ah7621  fossology-configs.tT7567  vmware-config0
fossology-configs.b17067  fossology-configs.v21272  vmware-config1
fossology-configs.c11086  fossology-configs.w22920  vmware-config2
fossology-configs.II2844  fossology-configs.y25373
fossology-configs.M17024  fossology-configs.Z16985


Thanks,
Bennis


--- Begin Message ---
Oh! a multi -system setup?  In that case, it's probably a configuration problem.

You only need the PostgreSQL server software on the server/scheduler system.  
The agent systems will need PostgreSQL client software installed to access the 
db.  There are also several other configuration steps that need to be performed 
for a multi-system setup.  Did you follow the instructions in 
/usr/share/doc/fossology-common/fossology and 
http://fossology.org/multi-system_setup ?

In particular, you MUST edit the default Db.conf file on the agent systems so 
they know how to contact PostgreSQL server AND the Scheduler.conf file so the 
scheduler knows about the agent systems AND the RepPath.conf file to specify 
how you want the repository distributed across your systems.

Please verify you have performed the steps described in the documents 
referenced above.  Let me know if you have any questions.

Mary




From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Thursday, May 14, 2009 10:29 AM
To: Laser, Mary
Subject: RE: License Analysis

Looks like files & gold folder was created. Do u know how I can create these 
files? Mine is a multiuser environment, so do we have to run postgresql service 
on both the machines.
Thanks,
Bennis

________
From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Thursday, May 14, 2009 10:34 AM
To: Abraham Bennis; fossology@fossology.org
Subject: RE: License Analysis

Hi Abraham,
This looks like a possible permissions problem.  You should have a repository 
directory (/srv/fossology/repository) with sub-directories (files & gold) owned 
by www-data:

laser@:/srv/fossology/repository$<mailto:laser@:/srv/fossology/repository$>
 ls -al
total 36
drwxrws--- 8 fossyfossy 4096 2009-05-12 18:22 .
drwxr-xr-x 4 root root  4096 2008-11-11 13:49 ..
drwxrws--- 2 www-data fossy 4096 2009-05-07 13:52 files
drwxrws--- 2 www-data fossy 4096 2009-05-07 13:52 gold

Please check your installation to see if it looks similar to the example above.

Thanks,
Mary





From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Thursday, May 14, 2009 8:17 AM
To: fossology@fossology.org
Subject: Re: [FOSSology] License Analysis (Laser, Mary)


I  couldn't find anything wrong in the fossology logs . But when I could see 
something junk coming to the SSH Client. Do you know why this is  displayed on 
the SSH Client ?

Thanks
Bennis


WARNING: File not in the repository (license 
86601A3957448BA52B49676214B9F51CACD08E6B.61316B4112879470690A73D474C4EF1B.142832)
WARNING: File not in the repository (license 
83D5FAAFF7A035E72AFA3BBC3C3BF30D805452FF.EEF86F8B8010C81C10EC7D5D3815CD2C.142826)
WARNING: File not in the repository (license 
7919D7A4EA54A4D03563939412B1A5DECA2F8D4D.60C37224420410AA05FA1D8998358E24.142743)
WARNING: File not in the repository (license 
E5DCD04EE035867E1F4800C6AB69CB2619F6C905.E25856F42E79071AE60A2BC52CE0E941.142687)
WARNING: File not in the repository (license 
F759D376D53BA19D4ED8460BD76F1BDA78D5C03D.DA1D49291A21629B9763A5E4ABF008BF.142474)
WARNING: File not in the repository (license 
8B13CB2D1E8CA6648859990A56D67CD39C91CA24.2E860085CB76B327B406E5E776B382D2.142449)
WARNING: File not in the repository (license 
67483025BBB1795AD2A40FB4BD9576D2C15F9474.E366629689C65F06037947844FD1CE0C.142440)

[FOSSology] FW: Error while uploading

[Laser, Mary]

From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Thursday, May 21, 2009 12:32 PM
To: Laser, Mary
Subject: RE: Error while uploading

Thanks, I changed the permission as recommended.  Now I could upload the files. 
I am able to run a license analysis for small file but I am getting another 
error now. Please see details below and let me know how to proceed.

# ERROR: DBaccess(7): ERROR:  canceling statement due to statement timeout

ERROR: DBaccess timeout: 'SELECT DISTINCT(pfile_pk) as Akey,
pfile_sha1 || '.' || pfile_md5 || '.' || pfile_size AS A
FROM uploadtree,pfile
WHERE uploadtree.pfile_fk = pfile.pfile_pk
   AND pfile_mimetypefk is NULL AND upload_fk = '38'
LIMIT 5000;'
WARNING: scheduler is running slow.  It took 813 seconds to check agent status: 
Thu May 21 09:13:39 2009
ERROR: DBaccess(7): ERROR:  canceling statement due to statement timeout

ERROR: DBaccess timeout: 'SELECT DISTINCT(pfile_pk) as Akey,
pfile_sha1 || '.' || pfile_md5 || '.' || pfile_size AS A
FROM uploadtree,pfile
WHERE uploadtree.pfile_fk = pfile.pfile_pk
   AND pfile_mimetypefk is NULL AND upload_fk = '38'
LIMIT 5000;'
WARNING: scheduler is running slow.  It took 599 seconds to check agent status: 
Thu May 21 09:23:38 2009
ERROR: DBaccess(7): ERROR:  canceling statement due to statement timeout

ERROR: DBaccess timeout: 'SELECT DISTINCT(pfile_pk) as Akey,
pfile_sha1 || '.' || pfile_md5 || '.' || pfile_size AS A
FROM uploadtree,pfile
WHERE uploadtree.pfile_fk = pfile.pfile_pk
   AND pfile_mimetypefk is NULL AND upload_fk = '38'
LIMIT 5000;'
ERROR: DBaccess(7): ERROR:  syntax error at or near "." at character 323

Thanks,
Bennis


From: Laser, Mary [mailto:mary.la...@hp.com]
Sent: Monday, May 18, 2009 11:04 PM
To: Abraham Bennis; fossology@fossology.org
Subject: RE: Error while uploading

Hi Bennis,
In an earlier email (attached) you mentioned you were using a multi-system 
setup.  Is this still the case?  This is a VERY important distinction.  Please 
open the attached email, follow the instructions therein and let me know your 
result.

Thanks,
Mary

____
From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Monday, May 18, 2009 10:38 AM
To: Laser, Mary; fossology@fossology.org
Subject: Error while uploading


I am not able to upload files for license analyzing. Please see the error 
below. At the same time I am not seeing the folder called "gold" "files".  
Please advice.


--
ERROR upload 12 Failed to import file into the repository (RepImport=1). LOG 
upload 12 Failed to import /tmp/phpwnzvRE-uploaded from /tmp/phpwnzvRE-uploaded 
into gold 
8B9DEC2B11954542F0477B0753508DA1AE1D25CE.2BD616FFA4D43BCE5CB9C8BCD294B6AB.247850297
 The file has been uploaded. It is upload #12.

# ls /tmp
ossology-configs.A14814  fossology-configs.sG2988  random.vintelaflush
fossology-configs.A14980  fossology-configs.T20759  updatecron.bak
fossology-configs.Ah7621  fossology-configs.tT7567  vmware-config0
fossology-configs.b17067  fossology-configs.v21272  vmware-config1
fossology-configs.c11086  fossology-configs.w22920  vmware-config2
fossology-configs.II2844  fossology-configs.y25373
fossology-configs.M17024  fossology-configs.Z16985


Thanks,
Bennis


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Simple list of all rpms needed for installing fossology on rhel/centos

[Laser, Mary]

Nice Vincent!
Very useful for our RH/Centos users.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Ma, Dong (vinc...@gdcc-bj-most)
Sent: Wednesday, May 27, 2009 12:56 AM
To: fossology@fossology.org
Cc: Liang, Ricky (TSG-GDCC-BJ-MOST)
Subject: [FOSSology] Simple list of all rpms needed for installing fossology on 
rhel/centos

Hi all,

I have created a Wiki page on fossology.org about Simple list of all rpms 
needed for installing fossology on rhel/centos. The link below:

http://fossology.org/simple_list_of_all_rpms_needed_for_installing_fossology_on_rhel_centos

If you have any questions and comments feel free let me know.

Thanks.

Best Regards,
Vincent Ma(Ma Dong)

Hewlett-Packard Co.
IDD: +86 10 6564 5733
Email:  vinc...@fossology.org


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Scheduler entering a loop

[Laser, Mary]

Hello Bennis,
I don't see any indication that the scheduler is stuck in a loop.  The 
"WARNING" messages below are simply informational.
What do the subsequent messages look like?

Mary


From: Abraham Bennis [mailto:abrahamben...@johndeere.com]
Sent: Tuesday, May 26, 2009 11:01 AM
To: Laser, Mary
Cc: fossology@fossology.org
Subject: Scheduler entering a loop


Mary,

After uploading a file. Scheduler is entering into a loop. Is it something to 
do with the application or am I doing something wrong. Please see the error and 
file permission.

# WARNING pfile 
8B9DEC2B11954542F0477B0753508DA1AE1D25CE.2BD616FFA4D43BCE5CB9C8BCD294B6AB.247850297
 Unable to extract permission
LOG pfile 
8B9DEC2B11954542F0477B0753508DA1AE1D25CE.2BD616FFA4D43BCE5CB9C8BCD294B6AB.247850297
 WARNING: Unable to extract permission from 
/srv/fossology/repository/ununpack/1/8b9dec2b11954542f0477b0753508da1ae1d25ce.2bd616ffa4d43bce5cb9c8bcd294b6ab.247850297.unpacked.dir/JDMIG_src/additional/eclipse/workspace/e2fsprogs-1.40.2/tests/f_h_normal/image.gz.unpacked

Permission on this folder is

total 32508
drwxr-sr-x 2 fossy fossy 4096 Jan 18  2008 CVS
-rw-r--r-- 1 fossy fossy  289 Dec 19  2007 expect.1
-rw-r--r-- 1 fossy fossy   454847 Dec 19  2007 image.gz
-rw-r--r-- 2 fossy fossy 32768000 May 26 11:51 image.gz.unpacked
drwxrws--- 7 fossy fossy 4096 May 26 10:53 image.gz.unpacked.dir
-rw-r--r-- 1 fossy fossy   32 Dec 19  2007 name
-rw-r--r-- 1 fossy fossy  115 Dec 19  2007 script

Please advice.

Thanks,

Bennis
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

[FOSSology] FW: Identifying new license in Fossology

[Laser, Mary]

Oops!  forgot to cc the list.



From: Laser, Mary
Sent: Tuesday, June 02, 2009 1:08 PM
To: 'cloud...@yahoo.com'
Subject: RE: [FOSSology] Identifying new license in Fossology

If you are trying to add an entire license vs. a phrase, you should follow the 
directions for adding a license template.

License Terms are used to "fine tune" the results of an identified license.  
For instance, if a GPL v2 license is identified as GPL with unknown version, 
the section of identified license text will be compared against License Terms 
to pinpoint the exact license (GPL v2).

>From what you've described, the license cannot be identified (because there is 
>no template).  Therefore, there is no license text to compare against the 
>License Terms.

HTH,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Tuesday, June 02, 2009 11:52 AM
To: fossology@fossology.org
Subject: [FOSSology] Identifying new license in Fossology

Hello,

I am trying to identify a new license in Fossology.  I am using the "Manage 
License Terms" page through the UI to do this but am having some difficulty.  I 
created a new Canonical name called "Company Name" and created a new term that 
was specific to that group.  The term was the following:  "Copyright Company 
Name".  I then did an Upload from a URL which contained a license file that 
contained that term.  However, the result was it did not find the license.  
What's strange is when I add the term "proprietary" to the group, it recognizes 
it, but any other phrase, it does not recognize.  Should I be using the UI to 
identify a new license or should I follow the instructions on the page "How to 
Add a License Template or License Phrase and Re-Analyze Licenses" in the 
documenation to do this?  The documentation says it requires re-running the 
build and modifying the database.  Any help is greatly appreciated.


Thanks





___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] FW: Identifying new license in Fossology

[Laser, Mary]

Hi,
Thanks for the detailed description!  I think the instructions are slightly 
off. You need to create a directory (not a file) in 
/usr/local/share/fossology/agents/licenses/ for your new template.  The 
directory name should be meaningful.  For instance, all Adobe license are under 
the directory Adobe, like this:

la...@myhost:/usr/share/fossology/agents/licenses$<mailto:la...@myhost:/usr/share/fossology/agents/licenses$>
 ls -l Adobe/
total 24
-rw-r--r-- 1 root root 1883 2009-05-08 17:22 Adobe
-rw-r--r-- 1 root root  599 2009-05-08 17:22 Adobe AFM short
-rw-r--r-- 1 root root   12 2009-05-08 17:22 Adobe AFM short.meta
-rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe.meta
-rw-r--r-- 1 root root  498 2009-05-08 17:22 Adobe short
-rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe short.meta
This example contains 3 license templates and their corresponding .meta files.  
When the license analysis matches text to a template, the license 
identification is determined by the file name with the closest matching text.

Based upon what you describe below, I think you did the right thing - despite 
the poor instructions!

I don't know why the License group shows  and ~.  
Did you ever delete the original  you added to the license group 
BEFORE you created a license template?  If not, that could be the cause.  
Please try deleting ~.   Also, when you get a template match, 
there should be a "ref" link to click on that displays the reference template 
used to determine the match.  Please try clicking on that and tell me the 
result.  There should be a pathname corresponding to the path where your 
template lives.

Thanks,
Mary




From: cloud...@yahoo.com [mailto:cloud...@yahoo.com]
Sent: Wednesday, June 03, 2009 9:19 AM
To: fossology@fossology.org; Laser, Mary
Subject: Re: [FOSSology] FW: Identifying new license in Fossology

Thank you for your response.  I tried to follow the instructions below that 
were documented to add a license template:

 1.
Place your file under /usr/local/share/fossology/agents/licenses/.
 2.
Run 'sudo fossinit'. The "..." sequence indicates that the licenses are being 
installed.



I created a directory under /usr/local/share/fossology/agents/licenses/ called 
.  I noticed the files under the other directories containing the 
licenses were not just text files, but a different format.  I copied two files 
from a different directory, it included the file that included the license and 
the .meta file to the directory I created.  I then renamed the files to 
 and .meta.  I updated the file  to 
contain our license.  I then executed the following command:



/usr/local/bin/fossinit /usr/local/share/fossology/agents/licenses/



The command completed successfully, but when I went to the "Manage License 
Terms" Page, it showed the Canonical name twice, once as  and 
once as ~.  I then uploaded a file that contained the license and 
the result was it found a license of type license, not .  It 
seems that I'm not creating the license template correctly.  Could someone 
please provide details on how to properly create a license template under 
/usr/local/share/fossology/agents/licenses that has the same file type as the 
others.



Thank You


--- On Tue, 6/2/09, Laser, Mary  wrote:

From: Laser, Mary 
Subject: [FOSSology] FW: Identifying new license in Fossology
To: "fossology@fossology.org" 
Date: Tuesday, June 2, 2009, 4:08 PM

Oops!  forgot to cc the list.



From: Laser, Mary
Sent: Tuesday, June 02, 2009 1:08 PM
To: 'cloud...@yahoo.com'
Subject: RE: [FOSSology] Identifying new license in Fossology

If you are trying to add an entire license vs.. a phrase, you should follow the 
directions for adding a license template.

License Terms are used to "fine tune" the results of an identified license.  
For instance, if a GPL v2 license is identified as GPL with unknown version, 
the section of identified license text will be compared against License Terms 
to pinpoint the exact license (GPL v2).

>From what you've described, the license cannot be identified (because there is 
>no template).  Therefore, there is no license text to compare against the 
>License Terms.

HTH,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Tuesday, June 02, 2009 11:52 AM
To: fossology@fossology.org
Subject: [FOSSology] Identifying new license in Fossology

Hello,

I am trying to identify a new license in Fossology.  I am using the "Manage 
License Terms" page through the UI to do this but am having some difficulty.  I 
created a new Canonical name called "Company Name" and created a new term that 
was specific to that group.  The term was the following:  "Copyright Company 
Name".  I then did an Upload from a URL w

Re: [FOSSology] FW: Identifying new license in Fossology

[Laser, Mary]

Yeah!  I suspected that was the problem and I was just about to suggest you 
remove the extraneous files.

Thanks for the good news!
Mary


From: cloud...@yahoo.com [mailto:cloud...@yahoo.com]
Sent: Thursday, June 04, 2009 8:40 AM
To: Laser, Mary; Donohoe, Mark; fossology@fossology.org
Subject: Re: [FOSSology] FW: Identifying new license in Fossology

I did discover extra files in the new folder created, I didn't notice them 
before since they didn't show in the explorer window but they showed in the 
terminal, sorry for misleading you..  After removing the files, it worked 
correctly.  Thanks again for everyone's help.


--- On Thu, 6/4/09, cloud...@yahoo.com  wrote:

From: cloud...@yahoo.com 
Subject: Re: [FOSSology] FW: Identifying new license in Fossology
To: "MaryLaser" , mark.dono...@hp.com, 
"fossology@fossology.org" 
Date: Thursday, June 4, 2009, 9:24 AM

Hello All,

Thanks to all those who responded.  I started again with a new installation.  I 
created a directory under /usr/local/share/fossology/agents/licenses with the 
Company name.  I then copied the Adobe and Adobe.meta files from the Adobe 
folder to the folder I created.  I renamed them to Company and Company.meta.  
Next, I opened the Company file in a text editor and copied the Company's 
license into there and saved it.  I opened the Company.meta file in a text 
editor, modified the URL, and saved it.  There were no files that ended in a ~ 
in the new directory.  I only saw two files there.

After executing the command /usr/local/bin/fossinit 
/usr/local/share/fossology/agents/licenses, I noticed there
were two Canonical names added in the "Manage License Terms" page, they were 
Company and Adobe~.  The Adobe~ contained the license which I added.  I went to 
upload a license and it found it associated with the Adobe~ group.  It seems 
that I am not creating the license templates correctly.  What is the correct 
way of creating these files, can I copy it from another license directory and 
modify it using a text editor or is there some tool I need to use to generate 
these files?

Thanks

--- On Wed, 6/3/09, Mark Donohoe  wrote:

From: Mark Donohoe 
Subject: Re: [FOSSology] FW: Identifying new license in Fossology
To: "Laser, Mary" 
Cc: "cloud...@yahoo.com" , "fossology@fossology.org" 

Date: Wednesday, June 3, 2009, 8:35 PM

Laser, Mary wrote:

Folks,

As far as the file with ~ at the end.  That's an emacs back up file.  I don't 
know if other editors use a name like that or not.  Even if you just opened a 
file with emacs didn't make any changes, there may still be a backup file.
Hi,
Thanks for the detailed description!  I think the instructions are slightly 
off. You need to create a directory (not a file) in 
/usr/local/share/fossology/agents/licenses/ for your new template.  The 
directory name should be meaningful.  For instance, all Adobe license are under 
the directory Adobe, like this:

la...@myhost:/usr/share/fossology/agents/licenses$<http://us.mc435.mail.yahoo.com/mc/compose?to=la...@myhost:/usr/share/fossology/agents/licenses$>
 ls -l Adobe/
total 24
-rw-r--r-- 1 root root 1883 2009-05-08 17:22 Adobe
-rw-r--r-- 1 root root  599 2009-05-08 17:22 Adobe AFM short
-rw-r--r-- 1 root root   12 2009-05-08 17:22 Adobe AFM short.meta
-rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe.meta
-rw-r--r-- 1 root root  498 2009-05-08 17:22 Adobe short
-rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe short.meta
This example contains 3 license templates and their corresponding .meta files.  
When the license analysis matches text to a template, the license 
identification is determined by the file name with the closest matching text.

Based upon what you describe below, I think you did the right thing - despite 
the poor instructions!

I don't know why the License group shows  and ~.  
Did you ever delete the original  you added to the license group 
BEFORE you created a license template?  If not, that could be the cause.  
Please try deleting ~.   Also, when you get a template match, 
there should be a "ref" link to click on that displays the reference template 
used to determine the match.  Please try clicking on that and tell me the 
result.  There should be a pathname corresponding to the path where your 
template lives.

Thanks,
Mary




From: 
cloud...@yahoo.com<http://us.mc435.mail.yahoo.com/mc/compose?to=cloud...@yahoo.com>
 
[mailto:cloud...@yahoo.com<http://us.mc435.mail.yahoo.com/mc/compose?to=cloud...@yahoo.com>]
Sent: Wednesday, June 03, 2009 9:19 AM
To: 
fossology@fossology.org<http://us.mc435.mail.yahoo.com/mc/compose?to=fossol...@fossology.org>;
 Laser, Mary
Subject: Re: [FOSSology] FW: Identifying new license in Fossology

Thank you for your response.  I tried to follow the instructions below that 
were documented to add a

Re: [FOSSology] Updating a License Template

[Laser, Mary]

Hi Cloud,
I don't understand why you are getting strange results.  I've added lots of 
license templates but, not quite the way you describe it.  I'm going to try to 
duplicate your error here so I can debug/explain.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Thursday, June 04, 2009 11:43 AM
To: fossology@fossology.org
Subject: [FOSSology] Updating a License Template

Hello,

I created a license template under /usr/local/share/fossology/agents/licenses.  
There was a directory created named Company w/ two files, a Company and a 
Company.meta file.  After executing the following command, the new license 
appeared under the "Manage License Term" page.
/usr/local/bin/fossinit /usr/local/share/fossology/agents/licenses/

I then added another license under Company by including a Company2 and 
Company2.meta file.  After executing the command above, the license under the 
"Manage License Term" page was not updated, it only showed the first license 
that was created for the Company.  I then deleted the Canonical name through 
the UI, renamed the directory under /usr/local/bin/fossinit 
/usr/local/share/fossology/agents/licenses/ to Company2, and then executed the 
command above.  When I go to the "Manage License Term" page, the new license 
does not appear.  How can I update an existing license template and how come 
when I removed it and re-added under a different name, it didn't work?  Any 
help is greatly appreciated.

Thanks


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] License template not being recognized

[Laser, Mary]

Hi Cloud,
Perhaps I'm confused.  What I understood is you created a license template that 
looks like this:
Copyright: copyright (c) 2008 Company:
After running fossinit, the new license is NOT added (because it is less than 
12 tokens).  So, you still have the same set of license templates you had 
before attempting to add the one above.

Then, you uploaded a file containing the line:
Copyright: copyright (c) 2008 Company:
The license scan will "tag" a section of your file as containing a potential 
license based on the "copyright" keyword.  However, when that section is 
compared against all the license templates, it will NOT find a match.  
Therefore, fossology will consider your upload void of any license.

Does that make sense?

For "phrases" that do not qualify as licenses (Eg: Copyright: copyright (c) 
2008 Company: ), the phrase can be added to a list of "one sentence license 
phrases" in the function 1sl.c 
(http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/agents/foss_license_agent/Filter_License/1sl.c?view=markup).
  Obviously, this code change requires you to recompile/rebuild the code.

Mary


From: cloud...@yahoo.com [mailto:cloud...@yahoo.com]
Sent: Wednesday, June 10, 2009 8:46 AM
To: fossology@fossology.org; Laser, Mary
Subject: RE: [FOSSology] License template not being recognized

Thanks for the reply.  I had a file that contained the following line which was 
uploaded:
Copyright: copyright (c) 2008 Company
Shouldn't it have recognized as a license based on the keywords below because 
it was not.

--- On Tue, 6/9/09, Laser, Mary  wrote:

From: Laser, Mary 
Subject: RE: [FOSSology] License template not being recognized
To: "cloud...@yahoo.com" 
Date: Tuesday, June 9, 2009, 11:50 PM

Hi Cloud,

A license template must be more than 12 tokens.  Anything less can be treated 
as a phrase or "licterm" (license term).  The latter requires a code change.

A list of keywords defined in the wordcheck functions are used to identify text 
which might contain a 
license.(http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/agents/foss_license_agent/Filter_License/wordcheck.c?view=markup).
  This list includes words such as, "acknowledgement", "agreement", 
"copyright", "disclaimer", "distribute", "liability", "license", "patent", 
"preamble",  "permission", "proprietary", "trademark", etc...

Looking at your example specifically, it contains one of the license keywords 
(copyright), however, it is less than 12 tokens.  Therefore, is is not 
considered a valid license.

HTH,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Tuesday, June 09, 2009 7:46 AM
To: fossology@fossology.org
Subject: [FOSSology] License template not being recognized

Hello,

I created a license template with just the following contents:
Copyright: copyright (c) 2008 Company:

This file was under the directory /usr/share/fossology/agents/licenses
I then executed the command
/usr/local/bin/fossinit /usr/local/share/fossology/agents/licenses
When I went to the "Manage License Terms" page, the new license did not appear. 
 If more content is added to the license template, it would appear.  Is there a 
minimum of what needs to appear in the license template?  What type of 
requirement is there for the content that needs to appear in the template?

Thank You




___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Multithreading

[Laser, Mary]

Hi Bennis,
Please take a look at the documentation for configuring the scheduler & agents 
at http://fossology.org/scheduler#configuring_the_scheduler.  There is an 
example posted there.

email with question/comments if it's not clear.
Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Thursday, June 11, 2009 8:30 AM
To: fossology@fossology.org
Subject: [FOSSology] Multithreading


I installed fossology application and I could run a license analysis. I would 
like to know whether the application is multi-threaded and how to configure the 
application to utilize both the CPU. Please kindly reply with an example.
__
Thanks,
Bennis




___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Multithreading

[Laser, Mary]

Yes & Yes.

:-)
Mary 

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> Sent: Friday, June 12, 2009 10:06 AM
> To: Matt Taggart
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] Multithreading
> 
> 
> If I am adding another CPU to the same machine, would it show 
> a better performance? Does this application support 64 Bit CPU? 
> 
> 
> Thanks,
> Bennis
> -Original Message-
> From: m...@lackof.org [mailto:m...@lackof.org] On Behalf Of 
> Matt Taggart
> Sent: Thursday, June 11, 2009 3:22 PM
> To: Abraham Bennis
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] Multithreading 
> 
> > I was trying to configure a single user system and I recreated the 
> > schedule r.conf.  Looks like application is using only one CPU.
> > Please see Schedule r.conf below & let me know if there is a way to 
> > make the application to uti lize both the CPU's.
> 
> mkschedconf uses '# of CPUs minus one' for agents, to ensure 
> that the scheduler itself still has cpu time to keep things 
> running smoothly. If you only have two CPUs in the system 
> it's expected that only one copy of an agent will run. You 
> can override this (at your peril) using the -C option to 
> mkschedconf (run it with -h for more options/info).
> 
> --
> Matt Taggart
> tagg...@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] Installation and download of Fossology

[Laser, Mary]

Hi Heinz,

Please add this line:

deb http://fossology.org/debian/ ./
(as documented here: 
http://fossology.org/link_to_source_download_at_sourceforge.net#binary_packages)

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of heinz.h.hi...@daimler.com
Sent: Monday, June 15, 2009 6:55 AM
To: fossology@fossology.org
Subject: [FOSSology] Installation and download of Fossology


Hello,

I am looking for the binary files of fossology. If I use the apt packages 
configuration for Debian, I get a mistake.
I have added the following lines into /etc/apt/sources.list

deb http://fossology.org/debian/ ./

Then I used "apt-get update" and "apt-get install fossology" on the command 
line, but it did not work. Does anybody know what I have to do to download and 
install the binaries?

Regards,
Heinz

If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Questions about API for Fossology and Future Directions

[Laser, Mary]

Hi Claude,
Yes, there is a command line program to perform uploads into fossology called 
cp2foss.  (http://fossology.org/cp2foss)

In the soon-t-be release 1.1 version of fossology, you will have the capability 
of enabling email notification on a user by user basis.  This will send email 
to the user when processing of the upload completes.  
(http://fossology.org/how_to_use_email_notification)

Finally, we maintain a roadmap of release features at 
http://fossology.org/roadmap.

HTH,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Friday, June 19, 2009 9:41 AM
To: fossology@fossology.org
Subject: [FOSSology] Questions about API for Fossology and Future Directions

Hello,

We have some questions regarding the current capability of Fossology and its 
future directions.  We understand how we can upload a file through the UI so it 
can be scanned for licenses.  However, we would like to automate this process 
from start to finish.  Is there some kind of API available in which we can 
login to Fossology, upload a file for scanning, determine when the scan is 
complete, and find out the results.  If not, when do you think such an API 
would be available.

We are also interested in knowing what kind of new features are being planned 
for the future releases.  Is there a page on the Fossology website that shows 
future plans for the product.  Any help would greatly be appreciated.

Thank You


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Questions about API for Fossology and Future Directions

[Laser, Mary]

Hi Claude,
There are a few different ways to access the DB from within an application.  
You can use libpq (http://www.postgresql.org/docs/8.3/static/libpq.html), the C 
application programmer's interface to PostgreSQL.
You can also use a DB API, such as, 
http://wiki.python.org/moin/UsingDbApiWithPostgres.  Both of these provide 
delete capability.  Another option is to use a simplified library built 
exclusively for fossology, libfossdb 
(http://fossology.org/database#db_api_libfossdb).

Mary




From: cloud...@yahoo.com [mailto:cloud...@yahoo.com]
Sent: Friday, June 19, 2009 11:51 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: [FOSSology] Questions about API for Fossology and Future Directions

Hi,

Thanks for your quick reply.  A couple of other questions.  How can we access 
the results from the database?  How is this currently being handled by 
Fossology when it does its reporting?  Also, are there other commands available 
such as delete via an API.


Thanks


--- On Fri, 6/19/09, Laser, Mary  wrote:

From: Laser, Mary 
Subject: RE: [FOSSology] Questions about API for Fossology and Future Directions
To: "cloud...@yahoo.com" , "fossology@fossology.org" 

Date: Friday, June 19, 2009, 12:06 PM

Hi Claude,
Yes, there is a command line program to perform uploads into fossology called 
cp2foss.  (http://fossology.org/cp2foss)

In the soon-t-be release 1.1 version of fossology, you will have the capability 
of enabling email notification on a user by user basis.  This will send email 
to the user when processing of the upload completes.  
(http://fossology.org/how_to_use_email_notification)

Finally, we maintain a roadmap of release features at 
http://fossology.org/roadmap.

HTH,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Friday, June 19, 2009 9:41 AM
To: fossology@fossology.org
Subject: [FOSSology] Questions about API for Fossology and Future Directions

Hello,

We have some questions regarding the current capability of Fossology and its 
future directions.  We understand how we can upload a file through the UI so it 
can be scanned for licenses.  However, we would like to automate this process 
from start to finish.  Is there some kind of API available in which we can 
login to Fossology, upload a file for scanning, determine when the scan is 
complete, and find out the results.  If not, when do you think such an API 
would be available.

We are also interested in knowing what kind of new features are being planned 
for the future releases.  Is there a page on the Fossology website that shows 
future plans for the product.  Any help would greatly be appreciated.

Thank You




___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Automated Procedure using Fossology

[Laser, Mary]

Hi Claude,

Answers to your questions:

1) Yes, cp2foss is the best solution.

2) email notification is NOT sent out for every sub-job scheduled to process an 
upload.  You will only receive one notification of the completed analysis. If 
you prefer to use a database trigger, that should work, too.

3) Yes, you can definitely query the database for license info.  You might want 
to take a look at the common set of php functions for license queries: 
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/ui/common/common-license.php?revision=1579&view=markup

4) I've never created a BIRT report but, from what I know of it, this should be 
possible.

5) There is a agent, accessible via the fossology UI, to delete uploads.  You 
may want to take a look at this code to see how it's done: 
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/agents/delagent/delagent.c?view=markup
  

License scanning is currently done manually on a project-by-project basis.

Mary





From: fossology-boun...@fossology.org 
[mailto:fossology-boun...@fossology.org] 
  On Behalf Of cloud...@yahoo.com
Sent: Wednesday, June 24, 2009 6:44 AM
To: fossology@fossology.org
Subject: [FOSSology] Automated Procedure using Fossology


Hello, 
 
We are planning on implementing the following automated procedure using 
Fossology and would 
  like to find out if this is a plausible solution or if there is a better 
approach of doing 
  the automation.
 
1. Use cp2foss to upload files for scanning.
2. Implement a job monitoring utility program to determine when job has 
completed. One 
way we are thinking of doing this is to use a database trigger. The 
reason we do not 
want to depend on the e-mail is because multiple e-mails are sent 
out for each sub-job 
associated with an uploaded file - Is this correct?
3. When a job has completed, extract the data results into our own 
database. We hope we 
could read the fossology database to get the license types of an 
uploaded file out.
4. Interpret the results from the database and produce a BIRT report.
5. We are still lacking an automated way to delete uploaded files to 
make spaces for new 
uploaded files. Any ideas on this?
 
Meanwhile, is there an automated way in which HP using Fossology to 
scan its build for 
  licenses and if so, how is it done?  Any help is greatly appreciated. 
 
Thank You



___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Automated Procedure using Fossology

[Laser, Mary]

Thanks for the delagent correction Bob.

Mary 

> -Original Message-
> From: Gobeille, Robert 
> Sent: Wednesday, June 24, 2009 11:33 AM
> To: cloud...@yahoo.com
> Cc: fossology@fossology.org; Laser, Mary
> Subject: Re: [FOSSology] Automated Procedure using Fossology
> 
> Hi Claude,
> Rather than looking at the delagent.c code, just run it (it's 
> a command line utility).
> 
> Usage: ./delagent [options]
>List or delete uploads.
>Options
>-i   :: Initialize the DB, then exit.
>-u   :: List uploads IDs.
>-U # :: Delete upload ID.
>-l   :: List uploads IDs. (same as -u, but goes with -L)
>-L # :: Delete ALL licenses associated with upload ID.
>-f   :: List folder IDs.
>-F # :: Delete folder ID and all uploads under this folder.
>Folder '1' is the default folder.  '-F 1' will delete
>every upload and folder in the navigation tree.
>-s   :: Run from the scheduler.
>-T   :: TEST -- do not update the DB or delete any files (just  
> pretend)
>-v   :: Verbose (-vv for more verbose)
> 
> 
> The only thing on your list that I think may give you trouble 
> is selecting the license information from the database.  This is one  
> reason why we are greatly simplifying the process in 1.2.   For now,  
> if you could share your report definition, we could offer 
> some specific help.
> 
> Bob Gobeille
> 
> 
> 
> On Jun 24, 2009, at 11:20 AM, Laser, Mary wrote:
> 
> > Hi Claude,
> >
> > Answers to your questions:
> >
> > 1) Yes, cp2foss is the best solution.
> >
> > 2) email notification is NOT sent out for every sub-job 
> scheduled to 
> > process an upload.  You will only receive one notification of the 
> > completed analysis. If you prefer to use a database trigger, that 
> > should work, too.
> >
> > 3) Yes, you can definitely query the database for license 
> info.  You 
> > might want to take a look at the common set of php functions for 
> > license queries: 
> > 
> http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/
> > ui/common/common-license.php?revision=1579&view=markup
> >
> > 4) I've never created a BIRT report but, from what I know 
> of it, this 
> > should be possible.
> >
> > 5) There is a agent, accessible via the fossology UI, to delete 
> > uploads.  You may want to take a look at this code to see how it's
> > done: 
> > 
> http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/
> > agents/delagent/delagent.c?view=markup
> >
> > License scanning is currently done manually on a project-by-project 
> > basis.
> >
> > Mary
> >
> >
> >
> > 
> >
> > From: fossology-boun...@fossology.org 
> > [mailto:fossology-boun...@fossology.org
> > ]
> >  On Behalf Of cloud...@yahoo.com
> > Sent: Wednesday, June 24, 2009 6:44 AM
> > To: fossology@fossology.org
> > Subject: [FOSSology] Automated Procedure using Fossology
> > 
> > 
> > Hello,
> > 
> > We are planning on implementing the following automated 
> procedure 
> > using Fossology and would
> >  like to find out if this is a plausible solution or if 
> there is a 
> > better approach of doing
> >  the automation.
> > 
> > 1. Use cp2foss to upload files for scanning.
> > 2. Implement a job monitoring utility program to 
> determine when job 
> > has completed. One
> > way we are thinking of doing this is to use a 
> database trigger.  
> > The reason we do not
> > want to depend on the e-mail is because multiple 
> e-mails are sent 
> > out for each sub-job
> > associated with an uploaded file - Is this correct?
> > 3. When a job has completed, extract the data results 
> into our own 
> > database. We hope we
> > could read the fossology database to get the 
> license types of an 
> > uploaded file out.
> > 4. Interpret the results from the database and produce 
> a BIRT report.
> > 5. We are still lacking an automated way to delete 
> uploaded files to 
> > make spaces for new
> > uploaded files. Any ideas on this?
> > 
> > Meanwhile, is there an automated way in which HP using 
> Fossology to 
> > scan its build for
> >  licenses and if so, how is it done?  Any help is greatly 
> > appreciated.
> > 
> > Thank You
> > 
> >
> >
> > ___
> > 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] How to construct the full path for the entries in table 'agent_lic_meta'

[Laser, Mary]

Hi Sam,
there are two ways to get this info.  You can query the database directly with:

SELECT * from (SELECT * from uploadtree2path($UploadtreePk)) AS path ORDER BY 
lft ASC;

Or, you can use the php function Dir2Path in ui/common/common-dir.php 
(http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.0.0/ui/common/common-dir.php?revision=1780&view=markup)

Pass the uploadtree_pk value from the uploadtree table.

Mary







From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Zhou, Sam
Sent: Wednesday, June 24, 2009 10:58 AM
To: fossology@fossology.org
Subject: [FOSSology] How to construct the full path for the entries in table 
'agent_lic_meta'


Folks,

We are trying to generate a report from fossology database. I noticed the final 
result are stored in table 'agent_lic_meta'.

CREATE TABLE "agent_lic_meta"(
 "pfile_fk" int4 not null ,
 "tok_pfile" int4 ,
 "tok_match" int4 ,
 "version" varchar(32) ,
 "phrase_text" varchar(256) ,
 "tok_pfile_start" int4 ,
 "tok_pfile_end" int4 ,
 "tok_license_start" int4 ,
 "tok_license_end" int4 ,
 "tok_license" int4 ,
 "lic_fk" int4 ,
 "pfile_path" varchar ,
 "license_path" varchar ,
 "agent_lic_meta_pk" int4 not null default 
nextval('agent_lic_meta_agent_lic_meta_pk_seq'::regclass)
)

Each row contains potential legal phrase captured in a file. However, I see no 
obvious way to
re-construct the full path based on the information provided by that table.

Which columns can trace back to 'uploadtree' and 'pfile' to re-contruct the 
full path (of that file having legal phrase)? Has the 'pfile_path' column 
something to do with it?

For your reference, I also copy 'uploadtree' and 'pfile' schema here,

CREATE TABLE "uploadtree"(
 "uploadtree_pk" int4 not null default 
nextval('uploadtree_uploadtree_pk_seq'::regclass),
 "parent" int4 ,
 "upload_fk" int4 not null ,
 "pfile_fk" int4 ,
 "ufile_mode" int4 ,
 "lft" int4 ,
 "rgt" int4 ,
 "ufile_name" text
)

CREATE TABLE "pfile"(
 "pfile_pk" int4 not null default nextval('pfile_pfile_pk_seq'::regclass),
 "pfile_md5" bpchar(32) not null ,
 "pfile_sha1" bpchar(40) not null ,
 "pfile_size" int8 not null ,
 "pfile_mimetypefk" int4 ,
 "pfile_usecount" int4 not null default 0,
 "pfile_liccount" int4
)

Thanks a lot,
Sam.

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Antwort: Re: Upload and Analyze of Zip/tar.bz2 files

[Laser, Mary]

Hello Heinz,
The debian release candidate testing packages (rc5) for 1.1 are available from
deb http://fossology.org/debian/1.1.0~rc5-T/lenny/ ./
deb http://fossology.org/debian/1.1.0~rc5-T/etch/ ./
etch is debian 4.0 and lenny is debian 5.0.  ( Check this out for an in-depth 
description of debian versioning http://en.wikipedia.org/wiki/Debian#Releases).

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of heinz.h.hi...@daimler.com
Sent: Thursday, July 09, 2009 9:10 AM
To: Gobeille, Robert
Cc: fossology@fossology.org
Subject: [FOSSology] Antwort: Re: Upload and Analyze of Zip/tar.bz2 files


Hello Bob,
where is the version 1.1 located. Is it 
http://fossology.org/debian/1.1.0~rc4/etch/ ?
And what is the difference between etch and lenny
Best Regards,
Heinz



bob.gobei...@hp.com

06.07.2009 17:11

An
heinz.h.hi...@daimler.com
Kopie
fossology@fossology.org
Thema
Re: [FOSSology] Upload and Analyze of Zip/tar.bz2 files


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

[FOSSology] 1.1.0 Release Candidate 5 available

[Laser, Mary]

Dear FOSSologists,

A 1.1.0 release candidate for FOSSology is now available for download and 
testing.  We have undergone several rounds of internal testing (hence the RC5 
designation).  Barring any new issues, we feel this candidate has a very good 
chance of becoming the official release.  Please download, install and exercise 
the application.  Report any issues to the fossology mailing list.

The debian release candidate packages for 1.1 are available using apt from:
deb http://fossology.org/debian/1.1.0~rc5/lenny/ ./ 
deb http://fossology.org/debian/1.1.0~rc5/etch/ ./

RPMs for
RHEL5 (i386 and x86-64)
RHEL4 (i386 and x86-64)
CentOS 5 (i386)
CentOS 4 (i386)
Will be posted on http://fossology.org/ on Monday.

You are interested enough in FOSSology to be subscribed to this mailing list, 
that means you are ideal for helping us test this release candidate to ensure 
that it's ready for release. Please give it a try and send 
problems/questions/results to the mailing list.

Thanks,

The FOSSology Team
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Unable to login after setup

[Laser, Mary]

Hello Lin,
As Bob mentions below, our 1.1.0 release candidate has just been announced and, 
so far, it looks very good.  If possible, I highly recommend using the latest 
release.

It appears something went wrong during the installation.

 1.
Did you see any errors during build or install?  If you're not sure, it doesn't 
hurt to re-run it.
 2.
Did you complete the configuration steps described in the INSTALL doc for 
PostgreSQL and Apache2?  If you follow the instructions in the INSTALL doc, you 
should not need to create the link to get the fossology UI working.
 3.
How were you able to update the fossy username?
 4.
Please check the postgres, fossology and Apache log files for errors/clues 
indicating why you can't login.  Reply to this email with the relevant info.

Thanks,
Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Gobeille, Robert
Sent: Friday, July 10, 2009 9:38 AM
To: Lin Ramachandran
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Unable to login after setup


On Jul 10, 2009, at 5:21 AM, Lin Ramachandran wrote:

Hi,

I am a bit new to the open source code and all. I have setup Fossology in an 
Fedora Core 9 machine and it took a whopping nine hours to set it up - had to 
resolve many decencies and very much to the blogs available I was able to make 
it run. But now I face a problem that I am not able to login to Fossology using 
the default username and password : fossy, fossy.

I had to create a link to the fossology to get the Web UI of Fossology running, 
i.e. I created a soft link to the folder /usr/local/share/fossology/www inside 
/var/www/html

( /var/www/html/fossology -> /usr/local/share/fossology/www )

and then I was able to get the UI in the browser. But the problem is that I am 
not able to login to fossology with the username fossy. I have  updated the 
password of user fossy, but I am still not able to login. When I try to login, 
it comes back to the same page with the "Home" and the "Help" menu being 
activated only while all the other menu options are disabled.

Hi Lin,
It sounds like you have had a terrible experience.  Hopefully, with all our 
install packages in release 1.1, no one else will have to go through this.  The 
1.1 testing is going very well.  I expect an official release around the end of 
next week.

Did you go through the post-install instructions  (section 2.2.3 in the INSTALL 
document)?

Places to look to see what is going wrong are the log files (/var/log).  Take a 
look at the postgres, fossology, and apache log files.

I'm sure someone on the list with more experience than I with brand new 
installs will help you.

Bob Gobeille
b...@fossology.org
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] 1.1.0 Release Candidate 5 available

[Laser, Mary]

> -Original Message-
> 
> > A 1.1.0 release candidate for FOSSology is now available 
> for download and testing.  We have undergone several rounds 
> of internal testing (hence the RC5 designation).  Barring any 
> new issues, we feel this candidate has a very good chance of 
> becoming the official release.  Please download, install and 
> exercise the application.  Report any issues to the fossology 
> mailing list.
> 
> Would it be possible to have a SVN tag as well ?
> 
> Bruno.


Yes.  You will find the subversion tag 1.1.0~rc5 under 
http://fossology.svn.sourceforge.net/viewvc/fossology/tags/


Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Unable to login after setup

[Laser, Mary]

Hi Lin,
Glad to hear you got it working finally.  See attached email for RPM packages.

Mary


From: Lin Ramachandran [mailto:lramachand...@tataelxsi.co.in]
Sent: Tuesday, July 14, 2009 5:15 AM
To: Laser, Mary
Cc: Gobeille, Robert; fossology@fossology.org
Subject: Re: [FOSSology] Unable to login after setup

Hi ,

Atlast I was able to login. the problem was the permissions in the system for 
each of the files was not correct. It was a blind action but it worked :-)

Lin

--- Begin Message ---
Hi all,

I have uploaded the CentOS/RHEL RPM packages on Sourceforge and fossology.org.

On sourceforge you can download from:
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.i386.rpm/download
   (centos4/rhel4 i386)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.x86_64.rpm/download
 (centos4/rhel4 x86_64)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.i386.rpm/download
   (centos5/rhel5 i386)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.x86_64.rpm/download
 (centos5/rhel5 x86_64)

On fossology.org you can download rpms, srcrpms and develrpms from:
http://fossology.org/rpms/1.1.0~rc5/centos/4/  (centos4/rhel4 i386 x86_64)
http://fossology.org/rpms/1.1.0~rc5/centos/5/  (centos5/rhel5 i386 x86_64)

>From Yum install with yum repo at
  http://fossology.org/rpms/1.1.0~rc5/centos/4/fossology.repo  (centos4 
i386 x86_64)
and  http://fossology.org/rpms/1.1.0~rc5/centos/5/fossology.repo  (centos5 i386 
x86_64)

  If you install on x86_64 do yum install fossology.x86_64 in order to 
avoid mixed deps.

Any questions feel free let me know. Thanks.

Best Regards,
Vincent Ma(Ma Dong)

Hewlett-Packard Co.
IDD: +86 010 6564 5733
Email: dong...@hp.com<mailto:dong...@hp.com>

--- End Message ---
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

[FOSSology] FW: 1.1.0RC5 RPM packages available on Sourceforge and fossology.org

[Laser, Mary]

Forwarding from Vincent.
Mary


From: Ma, Dong (vinc...@gdcc-bj-most)
Sent: Tuesday, July 14, 2009 5:01 AM
Subject: 1.1.0RC5 RPM packages available on Sourceforge and fossology.org

Hi all,

I have uploaded the CentOS/RHEL RPM packages on Sourceforge and fossology.org.

On sourceforge you can download from:
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.i386.rpm/download
   (centos4/rhel4 i386)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos4.x86_64.rpm/download
 (centos4/rhel4 x86_64)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.i386.rpm/download
   (centos5/rhel5 i386)
https://sourceforge.net/projects/fossology/files/fossology/fossology-1.1.0rc5-0.centos5.x86_64.rpm/download
 (centos5/rhel5 x86_64)

On fossology.org you can download rpms, srcrpms and develrpms from:
http://fossology.org/rpms/1.1.0~rc5/centos/4/  (centos4/rhel4 i386 x86_64)
http://fossology.org/rpms/1.1.0~rc5/centos/5/  (centos5/rhel5 i386 x86_64)

>From Yum install with yum repo at
  http://fossology.org/rpms/1.1.0~rc5/centos/4/fossology.repo  (centos4 
i386 x86_64)
and  http://fossology.org/rpms/1.1.0~rc5/centos/5/fossology.repo  (centos5 i386 
x86_64)

  If you install on x86_64 do yum install fossology.x86_64 in order to 
avoid mixed deps.

Any questions feel free let me know. Thanks.

Best Regards,
Vincent Ma(Ma Dong)

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Delete files

[Laser, Mary]

Hello Heinz,
The agent responsible for deleing uploads is delagent.  You can access it from 
the UI via Organize -> Uploads -> Delete Uploaded File.

The agent can also be invoked from the command line:

la...@mysystem:~/fossology-1.1.0/agents/delagent$
 /usr/local/lib/fossology/agents/delagent -?
/usr/local/lib/fossology/agents/delagent: invalid option -- ?
Usage: /usr/local/lib/fossology/agents/delagent [options]
  List or delete uploads.
  Options
  -i   :: Initialize the DB, then exit.
  -u   :: List uploads IDs.
  -U # :: Delete upload ID.
  -l   :: List uploads IDs. (same as -u, but goes with -L)
  -L # :: Delete ALL licenses associated with upload ID.
  -f   :: List folder IDs.
  -F # :: Delete folder ID and all uploads under this folder.
  Folder '1' is the default folder.  '-F 1' will delete
  every upload and folder in the navigation tree.
  -s   :: Run from the scheduler.
  -T   :: TEST -- do not update the DB or delete any files (just pretend)
  -v   :: Verbose (-vv for more verbose)

As you can see from the usage menu above, you'll need to pass it the upload id. 
 If you know the upload ids for each of the uploads you wish to delete, this 
would be the way to do it.

Bob or Mark may have an easier solution.  anyone?

Mary




From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of heinz.h.hi...@daimler.com
Sent: Tuesday, July 14, 2009 6:48 AM
To: fossology@fossology.org
Subject: [FOSSology] Delete files


Hello,

We have a lot of single files uploaded into fossology. We have currently about 
200 single files on the system and there are in different folders. And now we 
don't need them any longer and would like to delete them. Do you have any idea 
how we can delete all of them immediatley?

Regards,
Heinz
If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Scheduler Status page

[Laser, Mary]

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert
> Sent: Tuesday, July 14, 2009 12:24 PM
> To: Donohoe, Mark
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] Scheduler Status page
> 
> So you are proposing that we add notes about all outstanding 
> bugs targeted for 1.1 to the release notes?
> Sounds reasonable to me.  There aren't very many.  I think it 
> would be good to get these down to a one liner + url to the bug.
> 
> Bob
> 
> 
> On Jul 14, 2009, at 12:16 PM, Donohoe, Mark wrote:
> 
> >
> >
> > Bob, so what should we put in the release notes?  It seems 
> like we are
> > going to ship with it in the current state, so it would be good to
> > document in the release notes what the issues are (I'm not sure what
> > they are)
> >
> > Mary?  Thoughts on this.
> >>
> >>

Mark & Bob,

Yes, there are a handful of open bugs that will not get fixed for 1.1.  (At 
least 3 I know of, are license identification issues that should be addressed 
in 1.2.)  As Bob suggests, we should add these to the Known Issues section of 
the release notes  http://fossology.org/release_notes#known_issues.

Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Scheduler Status page

[Laser, Mary]

 

> -Original Message-
> 
> 
> On Jul 14, 2009, at 12:46 PM, Laser, Mary wrote:
> 
> > Yes, there are a handful of open bugs that will not get 
> fixed for 1.1.  
> > (At least 3 I know of, are license identification issues 
> that should 
> > be addressed in 1.2.)  As Bob suggests, we should add these to the 
> > Known Issues section of the release notes  
> > http://fossology.org/release_notes#known_issues
> > .
> 
> Is someone volunteering to do this?
> 

I suggest each bug owner document their bugs in the known issues section.

Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Error when executing cp2foss command using 1.1.1 RC5

[Laser, Mary]

Hi Claude,
I an earlier email thread, Bob had you comment out the pkgmetagetta agent in 
Scheduler.conf as a work around for the libextractor bug.  Since that agent is 
commented out, you can't run it.  The "-q all" option in cp2foss tells it to 
run ALL agents.  Please use a comma separated list to specify which agents you 
wish to run (i.e. all, EXCEPT pkgmetageta).

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Friday, July 17, 2009 1:02 PM
To: fossology@fossology.org
Subject: [FOSSology] Error when executing cp2foss command using 1.1.1 RC5

Hello,

After executing the following command:
cp2foss -q all -p tmp -n test -d "test upload" http:///LICENSE.zip
I receive the following error:
[r...@rh bin]# cp2foss -q all -p tmp -n test -d "test upload" 
http:///LICENSE.zip
Loading http:///LICENSE.zip
  Uploading to folder: '/tmp'
  Uploading as 'test'
  Upload description: 'test upload'
LOG upload 2 Downloaded http:///LICENSE.zip to wget.default_download
ERROR: Scheduling failed for Agent agent_pkgmetagetta
ERROR message: Pkgmetagetta not installed.

Any help is greatly appreciated.  Thanks.


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Question about adding new licenses to existing installation without doing upgrade

[Laser, Mary]

Hi Claude,
For this release, it's possible.  (I can't say if it will be that way in future 
releases.)  If I were doing it, I would download & untar the fossology 1.1.0 
tarball and then replace the Raw directory (Raw license templates & meta files) 
in you existing installation with the one from the tarball.  Be sure to run 
fossinit to re-populate the db with new license info and rebuild the license 
cache file used by the license analyzer.  Be sure you have your Raw directory 
saved incase something goes awry.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of cloud...@yahoo.com
Sent: Friday, July 17, 2009 1:11 PM
To: fossology@fossology.org
Subject: [FOSSology] Question about adding new licenses to existing 
installation without doing upgrade

Hello,

As Fossology comes out with new releases, is there a way to upload the new 
licenses that were added to the new release of Fossology to an existing 
installation of Fossology without having to do an upgrade.


Thanks


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Agent terminated prematurely

[Laser, Mary]

Hi Landon,
We have recently release fossology 1.1.0 with MANY bug fixes and improvements 
to the scheduler.  My first recommendation is to upgrade your installation to 
this new release and try the analysis again. 

If you can't upgrade, here are some other tips for 1.0.0:
Did the error below came from the fossology log file?  If you do not have 
messages going to the log file, please stop the scheduler and restart it with 
the "-L" option.  

You should also look in the postgresql log file for clues.  If you have not 
done so already, you should enable logging in the postgresql.conf and increase 
the level of logging for debugging purposes  (E.g.: log_min_error_statement = 
info)

Mary



> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Landon Jurgens
> Sent: Monday, July 27, 2009 11:09 AM
> To: fossology@fossology.org
> Subject: [FOSSology] Agent terminated prematurely
> 
> Team,
> 
>   I've setup a fossology 1.0.0 with the updated file to 
> allow it to handle loading directories. I've run two of the 4 
> jobs successfully but the last two keep failing. I've had a 
> few jobs fail be resetting them seems to fix the problem more 
> often than not. These two jobs keep failing and the only info 
> I get back is:
> 
> jq_endtextFailed: Failed: Agent terminated prematurely
> 
> I was wondering where should I look to get some more info 
> about the failure. I don't really see anything under the 
> Troubleshooting section of the site but I figure it must 
> exist somewhere.
> 
> --
> Landon Jurgens
> 
> 721 Visions Drive
> Skaneateles, NY 13152, USA
> GE Inspection Technologies
> http://www.geinspectiontechnologies.com/
> ___
> 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] Agent terminated prematurely

[Laser, Mary]

 
See inline responses.
Mary

> -Original Message-
> From: Landon Jurgens [mailto:landon.jurg...@ge.com] 
> Sent: Monday, July 27, 2009 1:47 PM
> To: Laser, Mary
> Cc: fossology@fossology.org
> Subject: RE: [FOSSology] Agent terminated prematurely
> 
> Mary,
> 
>   I couldn't understand how to execute with the -L 
> option. (something like /etc/init.d/fossology restart -L?)

Stop the scheduler. (/etc/init.d/fossology stop)
Edit the file /etc/default/fossology and add " -L "
Start the scheduler. (/etc/init.d/fossology start)

Based on what you sent me below, it looks like you already have the error log 
enabled.

> 
> I looked and found the error log. Here's What I got for the 
> last "event"
> since it all occurred within the same minute.
> 2009-07-27 01:13:02 scheduler[32191] : Child[13]
> 'agent=specagent host=localhost ' state=SPAWNED(4) @ 
> Mon Jul 27
> 01:13:02 2009
> 2009-07-27 01:13:02 scheduler[32191] : Child[13]
> 'agent=specagent host=localhost ' state=READY(5) @ Mon Jul 27
> 01:13:02 2009
> 2009-07-27 01:13:02 scheduler[32191] : ERROR: Child[13] died
> prematurely (was state RUNNING, signal was 6)
> 2009-07-27 01:13:02 scheduler[32191] : 
> Thread 13:
> 2009-07-27 01:13:02 scheduler[32191] :   PID:   32319
> 2009-07-27 01:13:02 scheduler[32191] :   Pipes: in=7->8 /
> out=10->9
> 2009-07-27 01:13:02 scheduler[32191] :   Attr:
> 'agent=specagent host=localhost '
> 2009-07-27 01:13:02 scheduler[32191] :   Command:
> '/usr/lib/fossology/agents/specagent'
> 2009-07-27 01:13:02 scheduler[32191] :   Parm:
> 'akey="217746"
> 
> a="1ABA3D7CC24E2B63FA06E5CE301F3E8391BF5E12.3D2E009EA8BA8B705A
> 30FD265A389BAA.4076"
> '
> 2009-07-27 01:13:02 scheduler[32191] :   Heartbeat:  
> Mon Jul 27
> 01:13:02 2009
> 2009-07-27 01:13:02 scheduler[32191] :   State:  
> Mon Jul 27
> 01:13:02 2009
> 2009-07-27 01:13:02 scheduler[32191] :   Status: 
> 6 (RUNNING)
> 2009-07-27 01:13:02 scheduler[32191] :   Spawn:  3 at Mon
> Jul 27 01:11:45 2009
> 2009-07-27 01:13:02 scheduler[32191] :   DB:
> 2009-07-27 01:13:02 scheduler[32191] : IsDB: 2
> 2009-07-27 01:13:02 scheduler[32191] : DBJobKey: 160
> 2009-07-27 01:13:02 scheduler[32191] : DBMSQrow: 0
> 2009-07-27 01:13:02 scheduler[32191] : DBagent:  22
> 2009-07-27 01:13:02 scheduler[32191] : Child[13]
> 'agent=specagent host=localhost ' state=FREEING(2) @ 
> Mon Jul 27
> 01:13:02 2009
> 2009-07-27 01:13:02 scheduler[32191] : Child[13]
> 'agent=specagent host=localhost ' state=FREE(1) @ Mon Jul 27
> 01:13:02 2009

Clearly, the dying agent is the specagent.  If you are only interested in a 
license analysis, you can omit this part of the analysis by leaving it 
unchecked in the UI when you upload your file for analysis.


> I updated my postgresql.conf file and restarted the fossology 
> agent and got a lot more in the log file (See attached). I 

The attached file was the fossology log NOT postgresql log.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Agent terminated prematurely

[Laser, Mary]

 

> -Original Message-
> From: Landon Jurgens [mailto:landon.jurg...@ge.com] 
> Sent: Tuesday, July 28, 2009 5:55 AM
> To: Laser, Mary
> Cc: fossology@fossology.org
> Subject: RE: [FOSSology] Agent terminated prematurely
> 
> I see where I misunderstood your question. 
> 
> I've attached the file but I found a lot of the same entries
> 
> 2009-07-26 06:40:08 EDT WARNING:  nonstandard use of 
> escape in a
> string literal at character 130
> 2009-07-26 06:40:08 EDT HINT:  Use the escape string 
> syntax for
> escapes, e.g., E'\r\n'.

This WARNING was introduce with PostgreSQL 8.3.  The fossology code has been 
modified in 1.1 to eliminate these benign and annoying messages.

> 
> I was able to grep some more info out
> 
> lan...@server1:~$ cat /var/log/postgresql/postgresql-8.3-main.log|grep
> LOG
> 2009-07-27 01:11:46 EDT LOG:  could not receive data from client:
> Connection reset by peer
> 2009-07-27 01:11:46 EDT LOG:  unexpected EOF on client connection
> 2009-07-27 01:12:29 EDT LOG:  could not receive data from client:
> Connection reset by peer

...

> but I didn't get anything from these errors either.
> 
> I'm thinking that it might be easier to take what I got so 
> far and then make the upgrade to 1.1.0.

That is, by far, the best solution.

Mary 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] stack smashing problem with filter_license agent

[Laser, Mary]

FYI - there is a bug filed against this problem with several attachments that 
may be helpful
http://bugs.linux-foundation.org/show_bug.cgi?id=350

Mary
 

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Gobeille, Robert
> Sent: Friday, July 31, 2009 9:17 AM
> To: Mitrinovic Dragoslav-FDM224
> Cc: fossology@fossology.org
> Subject: Re: [FOSSology] stack smashing problem with 
> filter_license agent
> 
> 
> On Jul 30, 2009, at 4:29 PM, Mitrinovic Dragoslav-FDM224 wrote:
> 
> > Team,
> >
> > I am running 1.1.0~rc5 release candidate, which I've rebuilt on my 
> > Ubuntu 9.04 box using unmodified rc5 debian source package.
> >
> > I am having problems with Filter_License terminating prematurely.
> > Eventually, all activity dies down and analysis remains stuck, even 
> > though scheduler is alive, as evidenced by recent "update time" in
> > Admin->Scheduler->Status.
> 
> Were you loading an open source package/iso?  If so, can you 
> say which one.  I haven't seen this problem, so it would be 
> really helpful if we could either reproduce it here or if you 
> could rebuild filter_license with a memory debugger 
> (valgrind, electricfence, ...).
> 
> 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

Re: [FOSSology] Fossology installation troubles : ERROR: Unable to initialize.

[Laser, Mary]

Hi Jonathan,
Since the error is occurring during database creation, we need to examine the 
PostgreSQL log file for clues - /var/log/postgres/postgresql.log.  If you 
don't see any useful information in there, please 1)  edit your postgresql.conf 
file to enable more verbose logging (log_min_messages = info, 
client_min_messages = log, log_min_error_statement = info); 2) restart the 
PostgreSQL server; 3) rerun fo-postinstall to generate the error again  3) 
re-examine the PostgreSQL log file.

Please send errors from the pg log file.

Thanks,
Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Jonathan Parès
> Sent: Tuesday, August 04, 2009 5:26 AM
> To: fossology@fossology.org
> Subject: [FOSSology] Fossology installation troubles : ERROR: 
> Unable to initialize.
> 
> Dear all,
> 
> I am trying to install fossology 1.1.0 from the source code 
> on my system (Ubuntu 8.04), and I have a problem with the 
> automatic configuration post-installation script.
> 
> When I execute the fo-postinstall script I have this result :
> 
>  sudo /usr/local/lib/fossology/fo-postinstall
> *** 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.
> *** Initializing database tables ***
> Applying database schema
> ERROR: Unable to initialize.
> 
> 
> As mentioned inside the INSTALL text file, I have modified 
> the Apache, PHP and Postgresql config files.
> 
> For information you can find the different configuration 
> files of my system and for PHP and Postgresql. I mention too 
> that I can connect to the postgresql server successfully with 
> the postgres user. So I have no idea from where could come 
> from the problem. I have had a discussion on the Fossology 
> IRC channel with "vincent", and we didn't success to pass the 
> fo-postinstall step.
> 
> Relying on your help,
> 
> Best regards,
> 
> Jonathan
> 
> 
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] List of Licences

[Laser, Mary]

hello Heinz,
All the licenses we use in FOSSology are in the directory:  
/usr/share/fossology/agents/licenses/...

Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of heinz.h.hi...@daimler.com
Sent: Tuesday, August 04, 2009 9:39 AM
To: fossology@fossology.org
Subject: [FOSSology] List of Licences


Hello,

Is there a way how to get a complete list of licences I can find with fossology?

Normally I would look into the database and try to receive some information 
from there. I think it should be easier, but I don't know where to look at.

Best Regards,
Heinz
If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Fossology installation troubles : ERROR: Unable to initialize.

[Laser, Mary]

Hi Jonathan,
Thank you for this additional information.  I will take a look at fossinit to 
see why the error is occurring.

Mary


From: Jonathan Parès [mailto:jonathan.pa...@gmail.com]
Sent: Wednesday, August 05, 2009 1:27 AM
To: Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Dear Mary,

It seems it's a problem of script and not of my database. The postgresql log 
file is not updated/modified by the execution of the fo-postinstall script.

Consequently I think it's a problem of script, inside the fo-postinstall script 
or the other ones called by the fo-postinstall.

Following the result of the running with the -x parameter of the script :

virtual...@ubuntu-8-04-vbx:~$ sudo bash -x 
/usr/local/lib/fossology/fo-postinstall
++ getopt -o adwseoh --long 
agent,database,web,web-only,scheduler,scheduler-only,everything,overwrite,help 
-n fo-postinstall --
+ OPTS=' --'
+ '[' 0 '!=' 0 ']'
+ eval set -- ' --'
++ set -- --
+ '[' ' --' = ' --' -o ' --' = ' -o --' ']'
+ EVERYTHING=1
+ true
+ case "$1" in
+ shift
+ break
+ '[' ']'
+ '[' ']'
+ '[' 1 ']'
+ echo '*** Running postinstall for everything ***'
*** Running postinstall for everything ***
+ AGENT=1
+ DATABASE=1
+ WEBONLY=1
+ SCHEDULERONLY=1
++ id -u
+ '[' 0 '!=' 0 ']'
+ '[' 1 ']'
+ /usr/local/lib/fossology/dbcreate
*** Setting up the FOSSology database ***
NOTE: fossology database already exists, not creating
*** Checking for plpgsql support ***
NOTE: plpgsql already exists in fossology database, good
+ '[' 1 ']'
+ '[' -e /usr/local/etc/fossology/RepPath.conf ']'
++ cat /usr/local/etc/fossology/RepPath.conf
+ REPO=/srv/fossology/repository
+ echo '*** Creating user and group ***'
*** Creating user and group ***
+ grep -q '^fossy:' /etc/group
+ echo 'NOTE: group '\''fossy'\'' already exists, good.'
NOTE: group 'fossy' already exists, good.
+ grep -q '^fossy:' /etc/passwd
+ echo 'NOTE: user '\''fossy'\'' already exists, good.'
NOTE: user 'fossy' already exists, good.
++ grep '^fossy:' /etc/passwd
++ cut -d: -f 7
+ USERSHELL=/bin/bash
+ '[' /bin/bash = /bin/false ']'
+ echo '*** Making sure needed dirs exist with right ownership/permissions ***'
*** Making sure needed dirs exist with right ownership/permissions ***
+ '[' '!' -d /var/local/lib/fossology ']'
+ chown root:fossy /var/local/lib/fossology
+ chmod 2775 /var/local/lib/fossology
+ '[' '!' -d /var/local/lib/fossology/agents ']'
+ chown root:fossy /var/local/lib/fossology/agents
+ chmod 2775 /var/local/lib/fossology/agents
+ '[' '!' -d /srv/fossology/repository ']'
+ echo 'NOTE: Repository already exists at /srv/fossology/repository'
NOTE: Repository already exists at /srv/fossology/repository
+ '[' -d /srv/fossology/repository/ununpack ']'
+ '[' -e /usr/local/etc/fossology/Hosts.conf ']'
+ grep -q '^localhost' /usr/local/etc/fossology/Hosts.conf
+ '[' 0 == 0 ']'
+ '[' '!' -d /srv/fossology/repository/localhost ']'
+ echo 'NOTE: /srv/fossology/repository/localhost directory already exists'
NOTE: /srv/fossology/repository/localhost directory already exists
+ echo '*** Checking database connectivity ***'
*** Checking database connectivity ***
+ DBCONF=/usr/local/etc/fossology/Db.conf
+ '[' '!' -f /usr/local/etc/fossology/Db.conf ']'
+ chgrp fossy /usr/local/etc/fossology/Db.conf
+ '[' -x /usr/local/lib/fossology/dbcheck ']'
+ /usr/local/lib/fossology/dbcheck
+ '[' 0 '!=' 0 ']'
+ echo 'NOTE: Connect succeeded, database is working.'
NOTE: Connect succeeded, database is working.
+ echo '*** Initializing database tables ***'
*** Initializing database tables ***
+ /usr/local/bin/fossinit
Applying database schema
+ '[' 255 '!=' 0 ']'
+ echo 'ERROR: Unable to initialize.'
ERROR: Unable to initialize.
+ exit 1


>From here seems to come from the problem :
+ '[' 255 '!=' 0 ']'

Thanks for your help.

Best regards,

Jonathan

2009/8/4 Laser, Mary mailto:mary.la...@hp.com>>
Hi Jonathan,
Since the error is occurring during database creation, we need to examine the 
PostgreSQL log file for clues - /var/log/postgres/postgresql.log.  If you 
don't see any us

Re: [FOSSology] Again: File contents are not available in the repository

[Laser, Mary]

 > -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of  Simon
> Sent: Wednesday, August 05, 2009 1:38 PM
> To: fossology@fossology.org
> Subject: [FOSSology] Again: File contents are not available 
> in the repository
> 
> Mary,
> 
> Last time, I didn't follow through on this matter because I 
> suspected that my installing process was defective.
> 
> This time, using Fossology 1.1.0 GA, I successfully installed 
> by using the official rpm.  So I want to tackle this issue again.
> 
> I am not able to view ANY of my uploads.  (See attached for 
> the zip file used for this analysis) Unpack seems successful, 
> judged by that the tasks were all finished successfully.  I 
> don't know how to verify that the content is on my file system.
> The /var/log/fossology/fossology.log shows that everything 
> was successful.  (initially shown error, but was caused by 
> postgres didn't start in time)
> 
> Please advise.  Thank you.
> 
> --
> Simon
> 西门烧雪

Hi Simon,
I saved your zip file to my desktop, uploaded it (from the UI using "Upload -> 
From File") and analyzed it with my fossology 1.1 instance.  I had no issues.  

Are you uploading it the same way?  (from the UI using "Upload -> From File")  
If not, what method are you using?

Please look at the postgresql log file for errors that might have occurred when 
inserting the data for your upload. 

Mary 



___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Again: File contents are not available in the repository

[Laser, Mary]

The default location for the postgresql log file is 
/var/log/postgresql/postgresql--main.log.  You should also check your 
postgresql configuration file (/etc/postgresql/8.3/main/postgresql.conf) to see 
if you have logging enabled and to verify the log file location.  Please set 
"log_statement = all" so we can see if the upload data is being inserted into 
the database successfully.

Thanks,
Mary


> -Original Message-
> From: 西门烧雪 Simon [mailto:sekatsi...@gmail.com] 
> Sent: Thursday, August 06, 2009 6:36 AM
> To: Laser, Mary
> Subject: Re: [FOSSology] Again: File contents are not 
> available in the repository
> 
> Mary,
> 
> I used the Upload -> From File, like you did.
> 
> Where is the postgresql log files?  I checked /var/log, but not found.
> 
> I can provide all the information you need to analyze this issue.
> Could you give me a list (and locations please since I am 
> deficient in advanced Unix) of locations to look for?
> 
> Thanks,
> 
> > Hi Simon,
> > I saved your zip file to my desktop, uploaded it (from the 
> UI using "Upload -> From File") and analyzed it with my 
> fossology 1.1 instance.  I had no issues.
> >
> > Are you uploading it the same way?  (from the UI using 
> "Upload -> From File")  If not, what method are you using?
> >
> > Please look at the postgresql log file for errors that 
> might have occurred when inserting the data for your upload.
> >
> > Mary
> >
> >  > -Original Message-
> >> From: fossology-boun...@fossology.org 
> >> [mailto:fossology-boun...@fossology.org] On Behalf Of  Simon
> >> Sent: Wednesday, August 05, 2009 1:38 PM
> >> To: fossology@fossology.org
> >> Subject: [FOSSology] Again: File contents are not available in the 
> >> repository
> >>
> >> Mary,
> >>
> >> Last time, I didn't follow through on this matter because 
> I suspected 
> >> that my installing process was defective.
> >>
> >> This time, using Fossology 1.1.0 GA, I successfully installed by 
> >> using the official rpm.  So I want to tackle this issue again.
> >>
> >> I am not able to view ANY of my uploads.  (See attached 
> for the zip 
> >> file used for this analysis) Unpack seems successful, 
> judged by that 
> >> the tasks were all finished successfully.  I don't know 
> how to verify 
> >> that the content is on my file system.
> >> The /var/log/fossology/fossology.log shows that everything was 
> >> successful.  (initially shown error, but was caused by postgres 
> >> didn't start in time)
> >>
> >> Please advise.  Thank you.
> >>
> >> --
> >> Simon
> >> 西门烧雪
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Fossology installation troubles : ERROR: Unable to initialize.

[Laser, Mary]

Hi Jonathan,

The message "Applying database schema" comes from the function ApplySchema in 
/usr/share/fossology/www/plugins/core-schema.php.  Immediately after this is 
printed, we check for the existence of the core-schema.dat file (also in  
/usr/share/fossology/www/plugins/) followed by a validity check.  If these 2 
tests pass, the core-schema.dat file is read and applied to the database.  
Since we are not seeing any messages in the postgresql log file indicating the 
schema is being applied, I'd guess that one of the 2 previous tests failed.  
Please check to see that the core-schema.dat file is present, readable and 
valid.  You can check it against this copy: 
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/ui/plugins/core-schema.dat?revision=2095&view=markup.

Mary



____
From: Laser, Mary
Sent: Wednesday, August 05, 2009 9:26 AM
To: 'Jonathan Parès'
Cc: fossology@fossology.org
Subject: RE: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Hi Jonathan,
Thank you for this additional information.  I will take a look at fossinit to 
see why the error is occurring.

Mary


From: Jonathan Parès [mailto:jonathan.pa...@gmail.com]
Sent: Wednesday, August 05, 2009 1:27 AM
To: Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Dear Mary,

It seems it's a problem of script and not of my database. The postgresql log 
file is not updated/modified by the execution of the fo-postinstall script.

Consequently I think it's a problem of script, inside the fo-postinstall script 
or the other ones called by the fo-postinstall.

Following the result of the running with the -x parameter of the script :

virtual...@ubuntu-8-04-vbx:~$ sudo bash -x 
/usr/local/lib/fossology/fo-postinstall
++ getopt -o adwseoh --long 
agent,database,web,web-only,scheduler,scheduler-only,everything,overwrite,help 
-n fo-postinstall --
+ OPTS=' --'
+ '[' 0 '!=' 0 ']'
+ eval set -- ' --'
++ set -- --
+ '[' ' --' = ' --' -o ' --' = ' -o --' ']'
+ EVERYTHING=1
+ true
+ case "$1" in
+ shift
+ break
+ '[' ']'
+ '[' ']'
+ '[' 1 ']'
+ echo '*** Running postinstall for everything ***'
*** Running postinstall for everything ***
+ AGENT=1
+ DATABASE=1
+ WEBONLY=1
+ SCHEDULERONLY=1
++ id -u
+ '[' 0 '!=' 0 ']'
+ '[' 1 ']'
+ /usr/local/lib/fossology/dbcreate
*** Setting up the FOSSology database ***
NOTE: fossology database already exists, not creating
*** Checking for plpgsql support ***
NOTE: plpgsql already exists in fossology database, good
+ '[' 1 ']'
+ '[' -e /usr/local/etc/fossology/RepPath.conf ']'
++ cat /usr/local/etc/fossology/RepPath.conf
+ REPO=/srv/fossology/repository
+ echo '*** Creating user and group ***'
*** Creating user and group ***
+ grep -q '^fossy:' /etc/group
+ echo 'NOTE: group '\''fossy'\'' already exists, good.'
NOTE: group 'fossy' already exists, good.
+ grep -q '^fossy:' /etc/passwd
+ echo 'NOTE: user '\''fossy'\'' already exists, good.'
NOTE: user 'fossy' already exists, good.
++ grep '^fossy:' /etc/passwd
++ cut -d: -f 7
+ USERSHELL=/bin/bash
+ '[' /bin/bash = /bin/false ']'
+ echo '*** Making sure needed dirs exist with right ownership/permissions ***'
*** Making sure needed dirs exist with right ownership/permissions ***
+ '[' '!' -d /var/local/lib/fossology ']'
+ chown root:fossy /var/local/lib/fossology
+ chmod 2775 /var/local/lib/fossology
+ '[' '!' -d /var/local/lib/fossology/agents ']'
+ chown root:fossy /var/local/lib/fossology/agents
+ chmod 2775 /var/local/lib/fossology/agents
+ '[' '!' -d /srv/fossology/repository ']'
+ echo 'NOTE: Repository already exists at /srv/fossology/repository'
NOTE: Repository already exists at /srv/fossology/repository
+ '[' -d /srv/fossology/repository/ununpack ']'
+ '[' -e /usr/local/etc/fossology/Hosts.conf ']'
+ grep -q '^localhost' /usr/local/etc/fossology/Hosts.conf
+ '[' 0 == 0 ']'
+ '[' '!' -d /srv/fossology/repository/localhost ']'
+ echo 'NOTE: /srv/fossology/repository/localhost directory already exists'
NOTE: /srv/fossology/repository/localhost directory already exists
+ echo '*** Checking database connectivity ***'
*** Checking database connectivity ***
+ DBCONF=/usr/local/etc/foss

Re: [FOSSology] Fossology installation troubles : ERROR: Unable to initialize.

[Laser, Mary]

Hi Jonathan,
Thanks for the update.  I spent several hours Friday examining the PostgreSQL 
log file you sent me and could not find the source of your problem.  I don't 
think it's due to encoding but, I'll look specifically for that issue.

I will also try to recreate the problem you describe below "Postgresql doesn't 
like the database creation with an encoding different from UTF-8, and the 
fossology database uses the SQL-ASCII encoding".

Thanks again,
Mary


From: Jonathan Parès [mailto:jonathan.pa...@gmail.com]
Sent: Sunday, August 09, 2009 9:10 PM
To: Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Dear Mary,

I have decided to install CentOS-5.3 as virtual machine on my PC. Fossology is 
working like a charm now. I would like helping you to fix this problem on 
Ubuntu 8.04, but I have done a backup on my virtual machine and now I don't 
have fossology installed on it anymore. But it seems that the 8.3 release of 
Postgresql doesn't like the database creation with an encoding different from 
UTF-8, and the fossology database uses the SQL-ASCII encoding ... This 
information must be confirmed, may be the problem comes from this.

Best regards,

Jonathan

2009/8/6 Laser, Mary mailto:mary.la...@hp.com>>
Hi Jonathan,

The message "Applying database schema" comes from the function ApplySchema in 
/usr/share/fossology/www/plugins/core-schema.php.  Immediately after this is 
printed, we check for the existence of the core-schema.dat file (also in  
/usr/share/fossology/www/plugins/) followed by a validity check.  If these 2 
tests pass, the core-schema.dat file is read and applied to the database.  
Since we are not seeing any messages in the postgresql log file indicating the 
schema is being applied, I'd guess that one of the 2 previous tests failed.  
Please check to see that the core-schema.dat file is present, readable and 
valid.  You can check it against this copy: 
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/ui/plugins/core-schema.dat?revision=2095&view=markup.

Mary




From: Laser, Mary
Sent: Wednesday, August 05, 2009 9:26 AM
To: 'Jonathan Parès'
Cc: fossology@fossology.org<mailto:fossology@fossology.org>
Subject: RE: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Hi Jonathan,
Thank you for this additional information.  I will take a look at fossinit to 
see why the error is occurring.

Mary


From: Jonathan Parès 
[mailto:jonathan.pa...@gmail.com<mailto:jonathan.pa...@gmail.com>]
Sent: Wednesday, August 05, 2009 1:27 AM
To: Laser, Mary
Cc: fossology@fossology.org<mailto:fossology@fossology.org>
Subject: Re: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Dear Mary,

It seems it's a problem of script and not of my database. The postgresql log 
file is not updated/modified by the execution of the fo-postinstall script.

Consequently I think it's a problem of script, inside the fo-postinstall script 
or the other ones called by the fo-postinstall.

Following the result of the running with the -x parameter of the script :

virtual...@ubuntu-8-04-vbx:~$ sudo bash -x 
/usr/local/lib/fossology/fo-postinstall
++ getopt -o adwseoh --long 
agent,database,web,web-only,scheduler,scheduler-only,everything,overwrite,help 
-n fo-postinstall --
+ OPTS=' --'
+ '[' 0 '!=' 0 ']'
+ eval set -- ' --'
++ set -- --
+ '[' ' --' = ' --' -o ' --' = ' -o --' ']'
+ EVERYTHING=1
+ true
+ case "$1" in
+ shift
+ break
+ '[' ']'
+ '[' ']'
+ '[' 1 ']'
+ echo '*** Running postinstall for everything ***'
*** Running postinstall for everything ***
+ AGENT=1
+ DATABASE=1
+ WEBONLY=1
+ SCHEDULERONLY=1
++ id -u
+ '[' 0 '!=' 0 ']'
+ '[' 1 ']'
+ /usr/local/lib/fossology/dbcreate
*** Setting up the FOSSology database ***
NOTE: fossology database already exists, not creating
*** Checking for plpgsql support ***
NOTE: plpgsql already exists in fossology database, good
+ '[' 1 ']'
+ '[' -e /usr/local/etc/fossology/RepPath.conf ']'
++ cat /usr/local/etc/fossology/RepPath.conf
+ REPO=/srv/fossology/repository
+ echo '*** Creating user and group ***'
*** Creating user and group ***
+ grep -q '^fossy:' /etc/group
+ echo 'NOTE: group '\''fossy'\'' already exists, good.'
NOTE: group 'fossy' already exists, good.
+ grep -q '^fossy:' /etc/passwd
+ echo 'NOTE: user '\''fossy'\'' already exists, good

Re: [FOSSology] Survey - for next version of FOSSology

[Laser, Mary]

> 
> I agree.  We did it mostly as an example to show our 
> potential.  But now I'm thinking that we shouldn't have 
> released it until we actually use the data.  Right now it's a 
> cost with no benefit unless people are doing direct db 
> queries or are counting on a UI to use it in the future.  The 
> only feedback I've gotten so far is from folks who do not 
> know what this agent does.
> 
> So far we have the following options:
> 
> 1) Do nothing.  Leave as is.
> 2) Make pkgmetagetta a separate package (requires minor code 
> changes and pkgmetagetta will never do selftest even if installed)
> 3) Leave packaging alone, but make same minor code changes as 
> in 2, so that pkgmetagetta is NEVER run.
> 
> I don't feel strongly about this but am asking for feedback 
> to find out if users would like a change.
> 
> Votes
> taggart: option 1 or 2
> bobg: option 1, 2, or 3  ;-)
> 
Mary: option 2 or 3

However, I think selftest should always be performed if an agent is installed.  
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem wile uploading a winzip file

[Laser, Mary]

 
> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> Sent: Wednesday, August 12, 2009 12:12 PM
> To: fossology@fossology.org
> Subject: [FOSSology] Problem wile uploading a winzip file
> 
>  
> I am having a problem while uploading a winzip file using the 
> option "Upload from Server" . Please let me know how to 
> resolve this problem.
> 
> Thanks,
> Bennis 
> 

Hi Bennis,
I had a similar problem yesterday and it turned out my Scheduler.conf file was 
wrong.  (If you have installed fossology 1.1 from a deb package, this file will 
reside in /etc/fossology/Scheduler.conf.)

Please send me your log file and your Scheduler.conf file.  Also, what version 
of fossology are you running and what distro.

Thanks,
Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem wile uploading a winzip file

[Laser, Mary]

Hi Bennis,
Thanks for the files.  According to the log file the winzip file does not 
reside on your localhost in the location you specified:

2009-08-11 15:09:02 scheduler[25919] : DEBUG[13]: Loading 
/upload/winscp419source.zip
2009-08-11 15:09:02 scheduler[25919] : FATAL: In thread 13:  
'/upload/winscp419source.zip' does not exist.

Can you verify this please?
Mary


> -Original Message-
> From: Abraham Bennis [mailto:abrahamben...@johndeere.com] 
> Sent: Wednesday, August 12, 2009 1:33 PM
> To: Laser, Mary
> Subject: RE: Problem wile uploading a winzip file
> 
> We are running on fossology 1.1 on a RHEL 5.3. Please see the 
> attached files.
> 
> Thanks,
> Bennis
> 
> 
> 
> -Original Message-
> From: Laser, Mary [mailto:mary.la...@hp.com]
> Sent: Wednesday, August 12, 2009 2:05 PM
> To: Abraham Bennis; fossology@fossology.org
> Subject: RE: Problem wile uploading a winzip file
> 
>  
> > -Original Message-
> > From: fossology-boun...@fossology.org 
> > [mailto:fossology-boun...@fossology.org] On Behalf Of Abraham Bennis
> > Sent: Wednesday, August 12, 2009 12:12 PM
> > To: fossology@fossology.org
> > Subject: [FOSSology] Problem wile uploading a winzip file
> > 
> >  
> > I am having a problem while uploading a winzip file using 
> the option 
> > "Upload from Server" . Please let me know how to resolve 
> this problem.
> > 
> > Thanks,
> > Bennis
> > 
> 
> Hi Bennis,
> I had a similar problem yesterday and it turned out my 
> Scheduler.conf file was wrong.  (If you have installed 
> fossology 1.1 from a deb package, this file will reside in 
> /etc/fossology/Scheduler.conf.)
> 
> Please send me your log file and your Scheduler.conf file.  
> Also, what version of fossology are you running and what distro.
> 
> Thanks,
> Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Again: File contents are not available in the repository

[Laser, Mary]

Hi Simon,
Thanks for sending the postgresql log file and for correcting the pathnames.  
(I incorrectly assumed you were on a debian-based distro and referred you to 
the wrong locations - sorry.)  What distro are you using?

Based on my initial examination of your log file, all the jobs ran successfully 
and the data from the analysis was saved in the database.  (See the attached 
file for the relevant postgresql statements.)

I'm looking for other clues in the postgresql log file and I'll respond with 
more as soon as I find something.

Mary




> -Original Message-
> From: 西门烧雪 Simon [mailto:sekatsi...@gmail.com] 
> Sent: Thursday, August 06, 2009 10:25 AM
> To: Laser, Mary
> Subject: Re: [FOSSology] Again: File contents are not 
> available in the repository
> 
> My postgres conf is located under
> /var/lib/pgsql/data
> 
> I have modified, so that
> log_statement = all # none, mod, ddl, all
> 
> /etc/init.d/postgresql restart
> 
> Uploaded the zip file again, the problem persists.
> 
> The postgres log file, 
> /var/lib/pgsql/data/pg_log/postgresql-Thu.log, is attached.  
> I didn't find anything more obvious than the followings, 
> which I think is obnoxious.
> 
> ERROR:  prepared statement 
> "FolderGetFromUpload_1_exported" already exists
> ERROR:  prepared statement "DirGetNonArtifact_exported" 
> already exists
> ERROR:  prepared statement "DirGetNonArtifact_exported" 
> already exists
> ERROR:  prepared statement "DirGetNonArtifact_exported" 
> already exists
> 
> 
> 
> 2009/8/6 Laser, Mary :
> > The default location for the postgresql log file is 
> /var/log/postgresql/postgresql--main.log.  You 
> should also check your postgresql configuration file 
> (/etc/postgresql/8.3/main/postgresql.conf) to see if you have 
> logging enabled and to verify the log file location.  Please 
> set "log_statement = all" so we can see if the upload data is 
> being inserted into the database successfully.
> >
> > Thanks,
> > Mary
> >
> >
> >> -Original Message-
> >> From: 西门烧雪 Simon [mailto:sekatsi...@gmail.com]
> >> Sent: Thursday, August 06, 2009 6:36 AM
> >> To: Laser, Mary
> >> Subject: Re: [FOSSology] Again: File contents are not available in 
> >> the repository
> >>
> >> Mary,
> >>
> >> I used the Upload -> From File, like you did.
> >>
> >> Where is the postgresql log files?  I checked /var/log, 
> but not found.
> >>
> >> I can provide all the information you need to analyze this issue.
> >> Could you give me a list (and locations please since I am 
> deficient 
> >> in advanced Unix) of locations to look for?
> >>
> >> Thanks,
> >>
> >> > Hi Simon,
> >> > I saved your zip file to my desktop, uploaded it (from the
> >> UI using "Upload -> From File") and analyzed it with my 
> fossology 1.1 
> >> instance.  I had no issues.
> >> >
> >> > Are you uploading it the same way?  (from the UI using
> >> "Upload -> From File")  If not, what method are you using?
> >> >
> >> > Please look at the postgresql log file for errors that
> >> might have occurred when inserting the data for your upload.
> >> >
> >> > Mary
> >> >
> >> >  > -Original Message-
> >> >> From: fossology-boun...@fossology.org 
> >> >> [mailto:fossology-boun...@fossology.org] On Behalf Of  Simon
> >> >> Sent: Wednesday, August 05, 2009 1:38 PM
> >> >> To: fossology@fossology.org
> >> >> Subject: [FOSSology] Again: File contents are not 
> available in the 
> >> >> repository
> >> >>
> >> >> Mary,
> >> >>
> >> >> Last time, I didn't follow through on this matter because
> >> I suspected
> >> >> that my installing process was defective.
> >> >>
> >> >> This time, using Fossology 1.1.0 GA, I successfully 
> installed by 
> >> >> using the official rpm.  So I want to tackle this issue again.
> >> >>
> >> >> I am not able to view ANY of my uploads.  (See attached
> >> for the zip
> >> >> file used for this analysis) Unpack seems successful,
> >> judged by that
> >> >> the tasks were all finished successfully.  I don't know
> >> how to verify
> >> >> that the content is on my file system.
> >> >> The /var/log/fossology/fossology.log shows that everything was 
> >> >> successful.  (initially shown error, but was caused by postgres 
> >> >> didn't start in time)
> >> >>
> >> >> Please advise.  Thank you.
> >> >>
> >> >> --
> >> >> Simon
> >> >> 西门烧雪
> 
> 
> 
> --
> Simon
> 西门烧雪
> 

simons_pglog.odt
Description: simons_pglog.odt
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Handling duplicate files from multiple uploads....

[Laser, Mary]

Hi Tom,
Actually, fossology already does this!  Each file analyzed has a unique 
identifier associated with it and stored in the database.  If the file should 
be re-uploaded for analysis, fossology will recognize it and not redo the 
analysis.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of thomas.j.mur...@kodak.com
Sent: Thursday, August 13, 2009 10:46 AM
To: fossology@fossology.org; fossology-boun...@fossology.org
Subject: [FOSSology] Handling duplicate files from multiple uploads


We would like our product teams to submit their source code for open source 
analysis at periodic times throughout the development cycle (at least once per 
year for active projects).   Most likely they will create a .tar for their 
source code directory and upload to our fossology server.   We would like to 
avoid re-analyzing and reporting files that have already been reported from 
earlier runs.   Can you recommended a method for handling this situation 
without burdening the product development teams too much (i.e. so they don't 
have to keep track of the files and somehow filter them for subsequent runs)?


Thanks,

Tom Murray

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Handling duplicate files from multiple uploads....

[Laser, Mary]

Tom,
Here is a mockup of how it will be reported 
http://fossology.org/~bobg/1.2reqs/pkghistory.html.
Is this useful?

Mary


From: thomas.j.mur...@kodak.com [mailto:thomas.j.mur...@kodak.com]
Sent: Thursday, August 13, 2009 11:15 AM
To: Gobeille, Robert; Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Handling duplicate files from multiple uploads


Bob and Mary,

I was aware that reanalysis was not performed on duplicate files --- but how do 
we present the data so that the user isn't tracking down the same files that 
have been 'flagged' with a license.

It looks like v 1.2 will indicate if there are license changes from one upload 
of the same file(s) to the next?   I must have missed that in the features 
list how will it be reported?  or is there a mockup screenshot of this 
capability?   ---

Basically, I just want the user to be able to zero in on the changes from the 
last upload relative to detected licenses.

thanks

Tom Murray




Bob Gobeille 

08/13/2009 12:56 PM

To
"thomas.j.mur...@kodak.com" 
cc
fossology@fossology.org
Subject
Re: [FOSSology] Handling duplicate files from multiple uploads






On Aug 13, 2009, at 10:45 AM, 
thomas.j.mur...@kodak.com<mailto:thomas.j.mur...@kodak.com> wrote:


We would like our product teams to submit their source code for open source 
analysis at periodic times throughout the development cycle (at least once per 
year for active projects).   Most likely they will create a .tar for their 
source code directory and upload to our fossology server.   We would like to 
avoid re-analyzing and reporting files that have already been reported from 
earlier runs.   Can you recommended a method for handling this situation 
without burdening the product development teams too much (i.e. so they don't 
have to keep track of the files and somehow filter them for subsequent runs)?

Hi Tom,
I just wrote (yesterday) the sql to do this in v 1.2.  Take two uploads - 
report the license changes.

Bob Gobeille
b...@fossology.org<mailto:b...@fossology.org>

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Fossology installation troubles : ERROR: Unable to initialize.

[Laser, Mary]

Hi Jonathan,
I've done some research on your inability to create the fossology database with 
SQL_ASCII encoding.  According to the PostgreSQL documentation, SQL_ASCII 
encoding is supported when the database character set is compatible with the 
server's locale 
setting.(http://www.postgresql.org/docs/8.3/interactive/multibyte.html)

 From the PostgreSQL documentation page on Locale Support 
(http://www.postgresql.org/docs/8.3/interactive/locale.html):

Locale support is automatically initialized when a database cluster is created 
using initdb. initdb will initialize the database cluster with the locale 
setting of its execution environment by default, so if your system is already 
set to use the locale that you want in your database cluster then there is 
nothing else you need to do. If you want to use a different locale (or you are 
not sure which locale your system is set to), you can instruct initdb exactly 
which locale to use by specifying the --locale option.
What locale is your system set to?  (Try examining the LANG or LC_ALL 
environment variables).

Also, you might want to try recreating your database cluster using the --locale 
option.  After you have done that, see if you can create a test database with 
SQL_ASCII encoding.

Good Luck!  I hope this helps.
Mary



From: Jonathan Parès [mailto:jonathan.pa...@gmail.com]
Sent: Monday, August 10, 2009 8:48 PM
To: Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Fossology installation troubles : ERROR: Unable to 
initialize.

Dear Mary,

I have read this in the Postegresql wiki page of the French Ubuntu community 
about the release 8.3 :

"Il est important de remarquer que lors de l'installation, les bases de données 
sont créées en unicode et qu'à cause de cela, il ne sera pas possible de créer 
une base de données dans un autre encodage."

that means in English :

"It's important to notice that during the installation, the database schemes 
are created with the unicode encoding and due to this, it will not possible to 
create an other scheme with an other encoding."

Best regards,

Jonathan

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] split this list?

[Laser, Mary]

I agree we need 2 lists (support & development) but, I'd rather not keep this 
current address.  I'm afraid we'd lose track of issues needing attention and it 
would discourage users from posting to the correct email list. 

Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Benson, 
> Channing D
> Sent: Friday, August 14, 2009 6:36 AM
> To: Gobeille, Robert; fossology@fossology.org
> Subject: Re: [FOSSology] split this list?
> 
> 
> It would seem to me helpful to have at least a couple new 
> categories: troubleshooting help, and developer topics, as 
> well as keeping the current address as a general catch-all.
> 
> Channing Benson
> Open Source / Linux R&D
> Hewlett-Packard Company
> (610) 328-3691
> 
> 
> > -Original Message-
> > From: fossology-boun...@fossology.org
> > [mailto:fossology-boun...@fossology.org] On Behalf Of 
> Gobeille, Robert
> > Sent: Thursday, August 13, 2009 4:45 PM
> > To: fossology@fossology.org
> > Subject: [FOSSology] split this list?
> >
> > When we started fossology we created this single general purpose 
> > mailing list for user questions, support, developers, ...
> >
> > A lot of the traffic lately has been developer oriented and an 
> > occasional support/help request has gone unanswered.  Is it 
> time to be 
> > thinking about splitting this into separate developer and 
> support/help 
> > lists?
> >
> > Thanks,
> > Bob Gobeille
> > b...@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
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] split this list?

[Laser, Mary]

OK.  I thought you were proposing to split this list (see subject line) into 2 
NEW lists.  
Keeping this and adding a new developer mail list will be just fine, too.

M

> -Original Message-
> From: Gobeille, Robert 
> Sent: Friday, August 14, 2009 10:18 AM
> To: Laser, Mary
> Cc: Benson, Channing D; fossology@fossology.org
> Subject: Re: [FOSSology] split this list?
> 
> I was thinking just the opposite.  I'd like to keep 
> fossology@fossology.org
>   for question/help/support, and add a 
> fossology-de...@fossology.org for developer issues.  If you 
> don't know what list to use, that's fossology@fossology.org . 
>  This way there is no change for users just looking for help.
> 
> Bob Gobeille
> b...@fossology.org
> 
> On Aug 14, 2009, at 10:14 AM, Laser, Mary wrote:
> 
> > I agree we need 2 lists (support & development) but, I'd rather not 
> > keep this current address.  I'm afraid we'd lose track of issues 
> > needing attention and it would discourage users from posting to the 
> > correct email list.
> >
> > Mary
> >
> >> -Original Message-
> >> From: fossology-boun...@fossology.org 
> >> [mailto:fossology-boun...@fossology.org] On Behalf Of Benson, 
> >> Channing D
> >> Sent: Friday, August 14, 2009 6:36 AM
> >> To: Gobeille, Robert; fossology@fossology.org
> >> Subject: Re: [FOSSology] split this list?
> >>
> >>
> >> It would seem to me helpful to have at least a couple new
> >> categories: troubleshooting help, and developer topics, as well as 
> >> keeping the current address as a general catch-all.
> >>
> >> Channing Benson
> >> Open Source / Linux R&D
> >> Hewlett-Packard Company
> >> (610) 328-3691
> >>
> >>
> >>> -Original Message-
> >>> From: fossology-boun...@fossology.org 
> >>> [mailto:fossology-boun...@fossology.org] On Behalf Of
> >> Gobeille, Robert
> >>> Sent: Thursday, August 13, 2009 4:45 PM
> >>> To: fossology@fossology.org
> >>> Subject: [FOSSology] split this list?
> >>>
> >>> When we started fossology we created this single general purpose 
> >>> mailing list for user questions, support, developers, ...
> >>>
> >>> A lot of the traffic lately has been developer oriented and an 
> >>> occasional support/help request has gone unanswered.  Is it
> >> time to be
> >>> thinking about splitting this into separate developer and
> >> support/help
> >>> lists?
> 
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem about install Fossology1.1

[Laser, Mary]

Sending again to cc the fossology list.


Hi Denis,
take a look at the instructions here 
http://fossology.org/rhel4_1.1http://fossology.org/rhel4_1.1>.  This 
has all the info you need to resolve your dependencies.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Denis GONG
Sent: Wednesday, August 26, 2009 11:25 PM
To: fossology@fossology.org
Subject: [FOSSology] Problem about install Fossology1.1

Dear support,

When I install Fossology1.1 in RHEL 4,it is prompt to install dependency  
software at first.
Where can I download these software? Can you give me the link of your website?
Thanks in advance.

[r...@psre045 opt]# rpm -ivh ./fossology-1.1.0-1.fc11.x86_64.rpm
error: Failed dependencies:
cabextract is needed by fossology-1.1.0-1.fc11.x86_64
file-libs is needed by fossology-1.1.0-1.fc11.x86_64
genisoimage is needed by fossology-1.1.0-1.fc11.x86_64
libextractor is needed by fossology-1.1.0-1.fc11.x86_64
libextractor-plugins is needed by fossology-1.1.0-1.fc11.x86_64
libextractor.so.1()(64bit) is needed by fossology-1.1.0-1.fc11.x86_64
libpq.so.5()(64bit) is needed by fossology-1.1.0-1.fc11.x86_64
php >= 5.1.6 is needed by fossology-1.1.0-1.fc11.x86_64
php-pear >= 5.16 is needed by fossology-1.1.0-1.fc11.x86_64
php-pgsql >= 5.1.6 is needed by fossology-1.1.0-1.fc11.x86_64
php-process is needed by fossology-1.1.0-1.fc11.x86_64
poppler-utils is needed by fossology-1.1.0-1.fc11.x86_64
postgresql >= 8.1.11 is needed by fossology-1.1.0-1.fc11.x86_64
postgresql-server >= 8.1.11 is needed by fossology-1.1.0-1.fc11.x86_64
rtld(GNU_HASH) is needed by fossology-1.1.0-1.fc11.x86_64
sleuthkit is needed by fossology-1.1.0-1.fc11.x86_64
upx is needed by fossology-1.1.0-1.fc11.x86_64


Kind Regards,


Denis Gong (巩文林）
Celluar System Division
ST-Ericsson Wireless

[cid:865340715@27082009-066A]
1105-1110,Sino-Life Tower, Xizhi Men North St, No.56, Haidian Dist, 
Beijing,P.R.C.100082
Tel: +86 10 59847034 Mobile: +86 13601353951 
denis.g...@stericsson.com
www.stericsson.com

<>___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Fossology test samples

[Laser, Mary]

Hi Jonathan,
There are some tests we use for license metrics here:
http://fossology.svn.sourceforge.net/viewvc/fossology/tags/1.1.0/tests/TestData/licenses/

We do not currently have a "test sample project" as you describe below.  Care 
to contribute one?  :-)

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Jonathan Parès
Sent: Thursday, August 27, 2009 4:59 AM
To: fossology@fossology.org
Subject: [FOSSology] Fossology test samples

Dear all,

I use Fossology and its database to analyze FLOSS projects and retrieve some 
metrics as :

- Number of distinct licenses incorporated;
- Number of unlicensed files;
- Number of FLOSS licensed files;

To check if my metrics are accurate, I am looking for a test sample project 
where it's possible to know before the analysis these numbers and after compare 
my results with the expected results.

Has the Fossology team some test sample projects with accurate results already 
available that could feel my needs ?

Best regards,

Jonathan


--

Jonathan Parès,
Open Source Software engineer,
Qualipso project,
O-Engine/GMRC,
Open Source Competence Center (China),
Guangzhou China.
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Licterm table, "Phrase" meaning and number of licenses for a file

[Laser, Mary]

Hi Jonathan,
There is a discussion about License Phrases and interpreting license analysis 
in the fossology project documentation: 
http://fossology.org/how_to_interpret_the_license_analysis_report#license_phrases.
  Please take a look and see if this answers your questions.

Thanks,
Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Jonathan Parès
Sent: Friday, August 28, 2009 8:31 AM
To: fossology@fossology.org
Subject: [FOSSology] Licterm table, "Phrase" meaning and number of licenses for 
a file

Dear all,

I would like to know what is the exact meaning of the "Phrase" item inside the 
licterm table. It seems to correspond to the files where the "license" is 
described by a simple sentence. I am right ?

Then I have noticed in the database (the licterm_name table) that a file can be 
associated to several licenses with different rates of matching (0, 1, 2), I am 
right too ? If yes it doesn't help me in my work ...

Thanks for your replies,

Jonathan

--

Jonathan Parès,
Open Source Software engineer,
Qualipso project,
O-Engine/GMRC,
Open Source Competence Center (China),
Guangzhou China.
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem about install Fossology1.1

[Laser, Mary]

Hi Denis,
There are many other mirrors listed on the Centos website 
(https://www.centos.org/).  This one worked for me:  
http://ftp.cuhk.edu.hk/pub/Linux/centos/

Mary


From: Denis GONG [mailto:denis.g...@stericsson.com]
Sent: Monday, August 31, 2009 2:13 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: Problem about install Fossology1.1

Dear support,
I download the following PHP rpm file :

   php-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/

 *   php-cli-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pdo-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pear-1.4.11-1.el4s1.1 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-common-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pgsql-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/

But I failed to install them, here is the  error prompt:

[r...@pek3l045 opt]# rpm -ivh php-5.1.6-3.el4s1.10.x86_64.rpm
error: php-5.1.6-3.el4s1.10.x86_64.rpm: V3 DSA signature: BAD, key ID 443e1821
error: php-5.1.6-3.el4s1.10.x86_64.rpm cannot be installed

Are the RPM files is damaged?  Can you give other download web site?





Kind Regards,


Denis Gong (巩文林）
Celluar System Division
ST-Ericsson Wireless

[cid:122421415@31082009-1867]
1105-1110,Sino-Life Tower, Xizhi Men North St, No.56, Haidian Dist, 
Beijing,P.R.C.100082
Tel: +86 10 59847034 Mobile: +86 13601353951 
denis.g...@stericsson.com<mailto:denis.g...@stericsson.com>
www.stericsson.com<http://www.stericsson.com>


<>___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem about install Fossology1.1

[Laser, Mary]

Denis,
You might try this, too 
http://forums.theplanet.com/lofiversion/index.php/t42180.html.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Laser, Mary
Sent: Monday, August 31, 2009 9:40 AM
To: Denis GONG; fossology@fossology.org
Subject: Re: [FOSSology] Problem about install Fossology1.1

Hi Denis,
There are many other mirrors listed on the Centos website 
(https://www.centos.org/).  This one worked for me:  
http://ftp.cuhk.edu.hk/pub/Linux/centos/

Mary


From: Denis GONG [mailto:denis.g...@stericsson.com]
Sent: Monday, August 31, 2009 2:13 AM
To: Laser, Mary; fossology@fossology.org
Subject: RE: Problem about install Fossology1.1

Dear support,
I download the following PHP rpm file :

   php-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/

 *   php-cli-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pdo-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pear-1.4.11-1.el4s1.1 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-common-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/
 *   php-pgsql-5.1.6-3.el4s1.10 # download from centosplus 
http://mirror.centos.org/centos/4/centosplus/

But I failed to install them, here is the  error prompt:

[r...@pek3l045 opt]# rpm -ivh php-5.1.6-3.el4s1.10.x86_64.rpm
error: php-5.1.6-3.el4s1.10.x86_64.rpm: V3 DSA signature: BAD, key ID 443e1821
error: php-5.1.6-3.el4s1.10.x86_64.rpm cannot be installed

Are the RPM files is damaged?  Can you give other download web site?





Kind Regards,


Denis Gong (巩文林）
Celluar System Division
ST-Ericsson Wireless

[cid:658445815@31082009-186E]
1105-1110,Sino-Life Tower, Xizhi Men North St, No.56, Haidian Dist, 
Beijing,P.R.C.100082
Tel: +86 10 59847034 Mobile: +86 13601353951 
denis.g...@stericsson.com<mailto:denis.g...@stericsson.com>
www.stericsson.com<http://www.stericsson.com>


<>___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Changing the repository in Fossology

[Laser, Mary]

yes, it can be done.  If you move it and keep the same pathname, you don't need 
to change anything.  If you move it to a new pathname, you'll need to change 
the pathname in /etc/fossology/RepPath.conf


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Dave McLoughlin
Sent: Friday, September 18, 2009 8:05 AM
To: fossology@fossology.org
Subject: [FOSSology] Changing the repository in Fossology

Can I move a repository in Fossology after it has been created and populated?  
I was recently analyzing some source and ran out of disk space on the partition 
where my repository is stored.  I'd like to know if I can move the repository 
to a larger partition.


Dave McLoughlin |

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] sh: fossjobs: not found error

[Laser, Mary]

At the very least, you will need to change RepPath.conf & Scheduler.conf.  
Also, check these file locations:  http://fossology.org/file_locations

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Dave McLoughlin
Sent: Monday, September 21, 2009 3:56 PM
To: fossology@fossology.org
Subject: [FOSSology] sh: fossjobs: not found error

I just installed Fossology 1.1.0 on Ubuntu 9.04.  I had previously installed it 
in the default location and it was running fine (after I took care of the stack 
smashing issue).  I just did a fresh install from source on a new system, but 
this time I put Fossology in a non-standard location, i.e. I tried to install 
it in a volume labeled /audit.

I've been trying to run some license analysis from "server uploads", but the 
agent keeps failing after a few minutes.  The logs aren't showing any error 
messages.  Here's the last few lines of my log:

2009-09-21 13:28:01 scheduler[4999] : Child[13] 'agent=fosscp_agent 
host=localhost ' state=SPAWNED(4) @ Mon Sep 21 13:28:01 2009
2009-09-21 13:28:01 scheduler[4999] : Child[13] 'agent=fosscp_agent 
host=localhost ' state=READY(5) @ Mon Sep 21 13:28:01 2009
2009-09-21 13:28:01 scheduler[4999] : DEBUG[13]: Loading 
/audit/openlogic/studio-1
2009-09-21 13:33:38 scheduler[4999] : DEBUG[13]: Uploading to folder: Software 
Repository
2009-09-21 13:33:38 scheduler[4999] : DEBUG[13]: Uploading as 'Studio 1'
2009-09-21 13:33:38 scheduler[4999] : DEBUG[13]: Upload description: 'Studio 1'
2009-09-21 13:45:11 scheduler[4999] : Child[13] 'agent=fosscp_agent 
host=localhost ' state=FREEING(2) @ Mon Sep 21 13:45:11 2009
2009-09-21 13:45:11 scheduler[4999] : Child[13] 'agent=fosscp_agent 
host=localhost ' state=FREE(1) @ Mon Sep 21 13:45:11 2009
2009-09-21 13:45:22 scheduler[4999] : Child[14] 'agent=fo_notify host=localhost 
' state=SPAWNED(4) @ Mon Sep 21 13:45:22 2009
2009-09-21 13:45:22 scheduler[4999] : Child[14] 'agent=fo_notify host=localhost 
' state=READY(5) @ Mon Sep 21 13:45:22 2009
2009-09-21 13:46:23 scheduler[4999] : DEBUG[14]: Mail has been queued by 
fo-notify
2009-09-21 14:01:32 scheduler[4999] : Child[14] 'agent=fo_notify host=localhost 
' state=FREEING(2) @ Mon Sep 21 14:01:32 2009
2009-09-21 14:01:32 scheduler[4999] : Child[14] 'agent=fo_notify host=localhost 
' state=FREE(1) @ Mon Sep 21 14:01:32 2009



But in the shell where I start Fossology from I keep seeing "sh: fossjobs: not 
found".

Please let me know if you have any suggestions.




Dave McLoughlin |  OpenLogic


___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Problem about install Fossology1.1

[Laser, Mary]

Hello Denis,
Can you be more specific about what you want to change?  OR, what result you 
are trying to obtain?

Mary


From: Denis GONG [mailto:denis.g...@stericsson.com]
Sent: Monday, September 28, 2009 4:04 AM
To: Ma, Dong (vinc...@gdcc-bj-most); Laser, Mary; fossology@fossology.org
Subject: RE: Problem about install Fossology1.1

Vincent, Laser
Thanks your help. Our Fossology is running normally.
We want to change some scan parameter .
Can you tell me how to chang?

Thanks.

Kind Regards,


Denis Gong (巩文林）
Celluar System Division
ST-Ericsson Wireless

[cid:905312422@28092009-0B70]
1105-1110,Sino-Life Tower, Xizhi Men North St, No.56, Haidian Dist, 
Beijing,P.R.C.100082
Tel: +86 10 59847034 Mobile: +86 13601353951 
denis.g...@stericsson.com<mailto:denis.g...@stericsson.com>
www.stericsson.com<http://www.stericsson.com>

<>___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] [FOSSology-devel] removing Admin > Database > Schema from UI

[Laser, Mary]

I don't thing I've ever used any of these options.  They were added a long time 
ago for debugging purposes by one of our developers.  I'm in complete agreement 
with your proposal below.

Mary


> 
> I'm considering removing from the schema functions from the 
> UI (Admin  > Database > Schema).  Does anyone use these?
> 
> The UI allows the following functions:
> 1. export the current schema
> 2. apply a new schema
> 3. compare a core-schema.dat with the installed schema 4. 
> view the current schema
> 
> I think 1 makes more sense as a stand alone utility since you 
> only do this either to generate a new release or for 
> developers to share a master schema that's being worked on.  
> Anyone see a reason to have this in the UI other than a 
> convenience for developers?
> 
> I think 2 only makes sense in our install script or as a 
> stand alone utility for developers.  Having this wrapped up 
> in a plugin just makes it hard to use (IMHO).
> 
> 3 is useful for developers.   I don't see end users using it.  When  
> you do a fo upgrade, there is no step where you compare the 
> new and old schemas and I doubt if anyone would want to anyway.
> 
> I don't find 4 useful at all since it displays the schema in 
> a very hard to read, non common, format.
> 
> So even though this isn't a high priority, since my head is 
> already wrapped around these functions it would be a good 
> time to do a cleanup and make life simpler (more productive) 
> for the developers.  My thoughts are:
> 
> A.   move 1 & 2 from plugins to stand alone utilities
> B.   probably keep 3 but move it under the Help > Debug menu
> C.   remove 4 completely since there are better interfaces to 
> do this  
> (phppgadmin, pgadmin III)
> 
> Comments?
> 
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Question on Agent Status

[Laser, Mary]

Hi Heinz,
We'll need additional information to help diagnose this problem.  Please do the 
following:

  /usr/lib/fossology/fossology-scheduler -t

This will test every agent to see if it runs, then quit.  Output will be sent 
to the log file.  Please look at the log file and see if it gives you any clues 
about what is wrong.  If you need help, send us the log file output.

Thanks,
Mary



Hello Mark,

I have tried to update Fossology on lenny 1.1.0 
(http://www.fossology.org/debian/lenny-backports/, please refer to attachment 
slide 2). It seems to work everything, but then I realized, that the agents 
(refer to attachment slide 3) are not running.

I tried to restart the agents with "sudo /etc/init.d/fossology restart", but it 
did not help.

A re-installation of fossology did not help either.

Do you have any idea how I can start the system properly? And what goes wrong 
with the update?

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Fossology and command line

[Laser, Mary]

Hello Heinz,
In the latest released version of cp2foss, the -a option has been deprecated.  
(Please use "cp2foss -h" to see all valid options.)  For the specific example 
you mention below, all you need to do is invoke cp2foss with the file name, 
directory path or URL to the archive you wish to upload.

You can specify which agents you want to run against your upload with the -q 
option.

The upload will be stored in the default repository location unless you modify 
it with the -f option.

Results from the analysis will be stored in the db and can be viewed in the UI.

The the options you are using with fossjobs are correct.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of heinz.h.hi...@daimler.com
Sent: Wednesday, October 07, 2009 8:31 AM
To: fossology@fossology.org
Subject: [FOSSology] Fossology and command line


Hello,

we would like to make an assessment completely on the command line. Therefore I 
have been thinking of some input on the command line as follows.

cp2foss -a /folder/file.tar  => Upload of tar-File into database
fossjobs -u  => I list all jobs and get an ID 20 back
fossjobs -U 20 -P 5 => Give ID 20 a higher priority

Is this correct so far? How does a command look like to set the type of 
analyses, e.g. licence analyses? And how do I get the results of this analysis 
back?

Regards,
Heinz


If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Some progress .. new problem

[Laser, Mary]

Hi George,
I understand from Bob that your License.bsam file is missing (not corrupt).  
This file is created during installation when using one of the package manager 
tools (apt or yum).  I saw from one of your previous emails in this thread that 
your yum install had a couple errors (stemming from the missing libextractor).  
So,... I would recommend one of 2 courses of action:

 1.
If you have resolved the libextractor dependency error, re-run yum to see if it 
can successfully complete without errors and build your License.bsam file.
 2.
Try running fo-postinstall (should be in /usr/lib/fossoslogy/fo-postinstall)  
which will also build License.bsam

Let me know how it goes.
Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Gobeille, Robert
Sent: Tuesday, October 27, 2009 12:19 PM
To: George A Pace
Cc: Stangel, Daniel; fossology@fossology.org
Subject: Re: [FOSSology] Some progress .. new problem

The scheduler is never starting because you have a corrupt License.bsam file 
(see below for path).
Could you email it to me?

Bob


On Oct 27, 2009, at 12:13 PM, George A Pace wrote:
2009-10-27 14:04:13 scheduler[3959] : FATAL: Scheduler error:  Unable to access 
license cache '/var/lib/fossology/agents/License.bsam'
2009-10-27 14:04:13 scheduler[3959] : FATAL: Self Test failed.  Inconsistent 
agent(s) detected.  Exiting.
2009-10-27 14:09:13 scheduler[3933] : *** Scheduler not responding: killing and 
restarting ***
2009-10-27 14:09:13 scheduler[3995] : Log opened
2009-10-27 14:09:13 scheduler[3995] : Scheduler started.  Build version: 1.1.0, 
exported.

___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Sharing some early FOSSology usage experiences

[Laser, Mary]

 
Thanks for the contribution Matt!

Mary

> -Original Message-
> From: fossology-boun...@fossology.org 
> [mailto:fossology-boun...@fossology.org] On Behalf Of Matt Taggart
> Sent: Wednesday, October 28, 2009 4:45 PM
> To: George A Pace
> Cc: fossology-boun...@fossology.org; fossology@fossology.org
> Subject: Re: [FOSSology] Sharing some early FOSSology usage 
> experiences
> 
> > 2.  It doesn't look like FOSSology supports the 7Zip compression 
> > format
> 
> Thanks for pointing this out. I just commited (SVN 2613 and 
> 2614) some changes to add support for 7zip, but they aren't 
> tested yet.
> 
> People who are upset about having to install yet another 
> dependency on their system can blame George :)
> 
> (seriously though, p7zip is available for 
> Debian/Ubuntu/Fedora, and is in EPEL for RHEL4 and RHEL5, so 
> we should be OK)
> 
> --
> Matt Taggart
> tagg...@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] Backup jobs failing

[Laser, Mary]

Hi Bennis,
The files stored in the directory listed below are the original downloads (in 
the gold subdirectory) , the unpacked objects (in the files sub-directory) , 
the FOSSology license cache files (created during analysis) and files for 
testing under sub-directory test.

If you remove files from the repository, you will no longer be able to browse 
the contents of your uploads and other UI plugins may not work properly.  
Therefore, I would recommend NOT removing these files.

Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Abraham Bennis
Sent: Monday, November 02, 2009 12:43 PM
To: fossology@fossology.org
Subject: [FOSSology] Backup jobs failing


I am having a problem while we run our backup jobs. These backup jobs are 
failing in the folder "/srv/fossology/repository/localhost". Please let me know 
if we could delete the files inside the repository folder after running the 
license analysis?
__
Thanks,
Bennis Abraham



___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Unable to Connect to database...

[Laser, Mary]

Hello Furosh,
You should also check the PostgreSQL log in the directory /var/log/postgresql/. 
 My guess is it's a problem with connections and/or authentication specified in 
your postgresql.conf file (/etc/postgresql//main/postgresql.conf).

Also, try accessing the fossology db from the command line:

  psql -d fossology -u fossy


Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Furosh One
Sent: Thursday, November 19, 2009 11:42 AM
To: fossology@fossology.org
Subject: [FOSSology] Unable to Connect to database...

Can anyone point me to areas to check/troubleshoot for agents not being able to 
connect to the central DB server?

My central DB server is host: clear5
All /etc/hosts file for all agents have an entry for clear1-6 and can ping all 
using things such as:
ping clear1
ping clear5
ssh fo...@fossy

Clear5 - Db.conf:
--
dbname=fossology;
host=localhost;
user=fossy;
password=fossy;
--

Agent - Clear1 - Db.conf:
--
dbname=fossology;
host=clear5;
user=fossy;
password=fossy;
--

Error Logs:
==
*** Checking database connectivity ***
ERROR: Unable to connect to the database
  Connection string: 'dbname=fossology host=clear5 user=fossy password=fossy'
  Connection status: '1'
ERROR: Failed to open database
ERROR: unable to connect to database, please check /etc/fossology/Db.conf
==

What can I check to ensure connecting to remote DB server on clients or server? 
Ports? There in a lab environment with no firewall but its a new install of 
Ubuntu v9.10, maybe I have to open up a port or service?

-Regards,
FuRoSh...
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Unable to Connect to database...

[Laser, Mary]

Oops, I forgot the most important config file, 
/etc/postgresql/8/main/pg_hba.conf.

Mary


From: Laser, Mary
Sent: Thursday, November 19, 2009 11:52 AM
To: 'Furosh One'; fossology@fossology.org
Subject: RE: [FOSSology] Unable to Connect to database...

Hello Furosh,
You should also check the PostgreSQL log in the directory /var/log/postgresql/. 
 My guess is it's a problem with connections and/or authentication specified in 
your postgresql.conf file (/etc/postgresql//main/postgresql.conf).

Also, try accessing the fossology db from the command line:

  psql -d fossology -u fossy


Mary



From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Furosh One
Sent: Thursday, November 19, 2009 11:42 AM
To: fossology@fossology.org
Subject: [FOSSology] Unable to Connect to database...

Can anyone point me to areas to check/troubleshoot for agents not being able to 
connect to the central DB server?

My central DB server is host: clear5
All /etc/hosts file for all agents have an entry for clear1-6 and can ping all 
using things such as:
ping clear1
ping clear5
ssh fo...@fossy

Clear5 - Db.conf:
--
dbname=fossology;
host=localhost;
user=fossy;
password=fossy;
--

Agent - Clear1 - Db.conf:
--
dbname=fossology;
host=clear5;
user=fossy;
password=fossy;
--

Error Logs:
==
*** Checking database connectivity ***
ERROR: Unable to connect to the database
  Connection string: 'dbname=fossology host=clear5 user=fossy password=fossy'
  Connection status: '1'
ERROR: Failed to open database
ERROR: unable to connect to database, please check /etc/fossology/Db.conf
==

What can I check to ensure connecting to remote DB server on clients or server? 
Ports? There in a lab environment with no firewall but its a new install of 
Ubuntu v9.10, maybe I have to open up a port or service?

-Regards,
FuRoSh...
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] Unable to Connect to database...

[Laser, Mary]

Hi Furosh,
When invoking psql with "-U", it should automatically prompt you for a password 
(see psql --help).  Since it's not doing it, you can force the prompt with -W.

psql -d fossology -U fossy -W

try that.
Mary



From: Furosh One [mailto:fur...@gmail.com]
Sent: Thursday, November 19, 2009 5:20 PM
To: Gobeille, Robert
Cc: Laser, Mary; fossology@fossology.org
Subject: Re: [FOSSology] Unable to Connect to database...

Okay I read up on the configuring the pg_hba.conf file for remote access.
I added the following to the file:
# Enable access for Fossology agents to connect to fossology DB:
hostallall10.3.3.0/24<http://10.3.3.0/24>trust

This should allow all my 5 agents to access it now.

However, I tested the login to fossology db on the server and login 
authentication fails:

gmarq...@san-clear5:~$ psql -d fossology -U fossy
psql: FATAL:  Ident authentication failed for user "fossy"


I can probably remove a package and then reinstall fossology to correct this, 
but is there another way to correct the login here? I would obviously need to 
correct this on the server before the agents can connect.

-FuRoSh...
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' differs from scheduler.

[Laser, Mary]

Hi Furosh,
I commend you on your persistence!

Host.conf  and Db.conf both look fine.

The repository path file RepPath.conf should be identical on the server and 
agents systems:

RepPath.conf:
=
/srv/fossology/repository

You're ALMOST there!
Mary


From: Furosh One [mailto:fur...@gmail.com]
Sent: Friday, November 20, 2009 12:52 PM
To: fossology@fossology.org
Cc: Donohoe, Mark; Matt Taggart; Laser, Mary; Gobeille, Robert
Subject: scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' differs 
from scheduler.

Hopefully this would finalize the setup/install on this cluster I got. 
(crossing-hands...)

I also went to the agents and re-ran the 'fo_postinstall -a' on clear1 to see 
if that would result in not having clear1 have a FATAL error. If it read clear2 
then I knew I had to do the same on the other agents. I also went back to the 
server to run the fo_postinstall and also same results.

All agent mounted on Server are okay, all ssh auto-login okay, all 
cross-mounting on agents okay.

Hosts.conf (on ALL machines server/agents):

clear1 * 00 32
clear2 * 33 65
clear3 * 66 99
clear4 * 9a cc
clear6 * cd ff

Db.conf (on ALL machines server/agents):
=
dbname=fossology;
host=clear5;
user=fossy;
password=fossy;

RepPath.conf: (on SERVER)
=
/srv/fossology/repository

I was guessing the server would know to point to Hosts.conf to know each agent 
repos were located in /srv/fossology/repository/%Host/ or $Host somehow, but 
maybe I'm wrong???

RepPath.conf: (on AGENTS)
=
/srv/fossology/repository/clearX   (<-- X being 1 for clear1, 2 for clear2, 3 
for clear3, etc.)

These directories clear1, clear2, clear3, etc were all created on the agent 
machines and permissions are okay.
Also I can 'su fossy' and touch files or write to 
/srv/fossology/repository/clearX/ from Server (not sure why self-test is 
failing).

I have used the mkschedconf script to create the scheduler. I used both 
double-quotes and single quotes (single quotes look similar to the default 
Scheduler.conf file) and still same results when attempting to start.

I have clear1, clear2, clear3, clear4, clear6 all as agents and clear5 is the 
server.
I used this to create the scheduler.conf file:

/usr/lib/fossology/mkschedconf -C 2 -R '/usr/bin/ssh fo...@clear1 %s' -H clear1 
\
/usr/lib/fossology/mkschedconf -C 2 -R '/usr/bin/ssh fo...@clear2 %s' -H clear2 
\
/usr/lib/fossology/mkschedconf -C 2 -R '/usr/bin/ssh fo...@clear3 %s' -H clear3 
\
/usr/lib/fossology/mkschedconf -C 2 -R '/usr/bin/ssh fo...@clear4 %s' -H clear4 
\
/usr/lib/fossology/mkschedconf -C 2 -R '/usr/bin/ssh fo...@clear6 %s' -H clear6 
\
> new_scheduler.conf

I also tried with "%s" and same results. Here are the error logs in 
/var/log/fossology/fossology.log:
=
2009-11-20 11:30:13 scheduler[1402] : FATAL: Configuration on agent 'clear1' 
differs from scheduler.
2009-11-20 11:30:13 scheduler[1402] : FATAL: The difference is Repository
2009-11-20 11:30:13 scheduler[1402] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 11:30:13 scheduler[1402] :   Mismatch on clear1: Repository: clear1 
* 00 32 # Fri Nov 20 11:30:08 2009
2009-11-20 11:30:13 scheduler[1402] : FATAL: Configuration on agent 'clear2' 
differs from scheduler.
2009-11-20 11:30:13 scheduler[1402] : FATAL: The difference is Repository
2009-11-20 11:30:13 scheduler[1402] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 11:30:13 scheduler[1402] :   Mismatch on clear2: Repository: clear1 
* 00 32 # Fri Nov 20 11:30:08 2009
2009-11-20 11:30:13 scheduler[1402] : FATAL: Configuration on agent 'clear3' 
differs from scheduler.
2009-11-20 11:30:13 scheduler[1402] : FATAL: The difference is Repository
2009-11-20 11:30:13 scheduler[1402] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 11:30:13 scheduler[1402] :   Mismatch on clear3: Repository: clear1 
* 00 32 # Fri Nov 20 11:30:08 2009
2009-11-20 11:30:14 scheduler[1402] : FATAL: Configuration on agent 'clear4' 
differs from scheduler.
2009-11-20 11:30:14 scheduler[1402] : FATAL: The difference is Repository
2009-11-20 11:30:14 scheduler[1402] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 11:30:14 scheduler[1402] :   Mismatch on clear4: Repository: clear1 
* 00 32 # Fri Nov 20 11:30:08 2009
2009-11-20 11:30:14 scheduler[1402] : FATAL: Configuration on agent 'clear6' 
differs from scheduler.
2009-11-20 11:30:14 scheduler[1402] : FATAL: The difference is Repository
2009-11-20 11:30:14 scheduler[1402] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 11:30:14 scheduler[1402] :   Mismatch on clear6: Repository: clear1 
* 00 32 # Fri Nov 20 11:30:08 2

Re: [FOSSology] scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' differs from scheduler.

[Laser, Mary]

FOSSology uses the Hosts.conf file to determine where to put repository info.

Mary



From: Furosh One [mailto:fur...@gmail.com]
Sent: Friday, November 20, 2009 2:07 PM
To: Laser, Mary
Cc: fossology@fossology.org; Donohoe, Mark; Matt Taggart; Gobeille, Robert
Subject: Re: scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' 
differs from scheduler.

Thanks Mary,

Okay I will make this change on all machines. I'm just wondering how the 
repository will know to place the files/folders withing each of the 
/srv/fossology/repository/ clear1/ clear2/ clear3/, etc directories.

Again maybe I'm just over thinking this so I'll just change it to all be 
/srv/fossology/repository to see if that corrects my issue.
Thanks again!!!

-FuRoSh...

On Fri, Nov 20, 2009 at 12:38 PM, Laser, Mary 
mailto:mary.la...@hp.com>> wrote:
Hi Furosh,
I commend you on your persistence!

Host.conf  and Db.conf both look fine.

The repository path file RepPath.conf should be identical on the server and 
agents systems:

RepPath.conf:
=
/srv/fossology/repository

You're ALMOST there!
Mary
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' differs from scheduler.

[Laser, Mary]

Hello Gilbran,
The permissions for /srv/fossology/repository/ must be identical on all systems 
- server and agents.  Is this the case?

Mary


From: Furosh One [mailto:fur...@gmail.com]
Sent: Friday, November 20, 2009 4:11 PM
To: Laser, Mary
Cc: fossology@fossology.org; Donohoe, Mark; Matt Taggart; Gobeille, Robert
Subject: Re: scheduler[1402] : FATAL: Configuration on agent 'HOSTNAMES' 
differs from scheduler.

Thanks again Mary!!! However I made sure the server and all of the agents had 
/srv/fossology/repository in the RepPath.conf file. Rebooted the agents and 
then the server and I end up with new error messages.

And trust me I've paid close attention to see if its something I can resolve 
quickly. I attempted to do things and compare all machines to make sure all 
settings are correct, all permissions are good 'chmod g+rwxs /srv/fossology/ 
and repository/' and I still get errors =/

gmarq...@san-clear5:~$<mailto:gmarq...@san-clear5:~$> sudo ls -l /srv/fossology/
total 12
-rwxrwxr-x 1 fossy fossy  406 2009-11-18 08:55 clear1_authorized_keys
-rwxrwxr-x 1 fossy fossy  406 2009-11-18 08:47 clear5_authorized_keys
drwxrwsr-x 9 fossy fossy 4096 2009-11-19 19:23 repository
gmarq...@san-clear5:~$<mailto:gmarq...@san-clear5:~$>
gmarq...@san-clear5:~$<mailto:gmarq...@san-clear5:~$> sudo ls -l 
/srv/fossology/repository/
total 28
drwxrwsr-x 2 fossy fossy 4096 2009-11-20 15:00 clear1
drwxrwsr-x 2 fossy fossy 4096 2009-11-20 15:00 clear2
drwxrwsr-x 2 fossy fossy 4096 2009-11-20 15:00 clear3
drwxrwsr-x 2 fossy fossy 4096 2009-11-20 15:00 clear4
drwxrwsr-x 2 fossy fossy 4096 2009-11-20 15:00 clear6
drwxrwsr-x 2 fossy fossy 4096 2009-11-18 13:33 localhost
drwxrws--- 3 fossy fossy 4096 2009-11-19 19:23 ununpack


2009-11-20 15:05:44 scheduler[2502] : FATAL: Configuration on agent 'clear2' 
differs from scheduler.
2009-11-20 15:05:44 scheduler[2502] : FATAL: The difference is FATAL
2009-11-20 15:05:44 scheduler[2502] :   Observed on scheduler system: FATAL: 
Setgid for group missing on /srv/fossology/repository
2009-11-20 15:05:44 scheduler[2502] :   Mismatch on clear2: Permissions: OK 
RepPath.conf
2009-11-20 15:05:44 scheduler[2502] : FATAL: Configuration on agent 'clear3' 
differs from scheduler.
2009-11-20 15:05:44 scheduler[2502] : FATAL: The difference is FATAL
2009-11-20 15:05:44 scheduler[2502] :   Observed on scheduler system: FATAL: 
Setgid for group missing on /srv/fossology/repository
2009-11-20 15:05:44 scheduler[2502] :   Mismatch on clear3: Permissions: OK 
RepPath.conf
2009-11-20 15:05:44 scheduler[2502] : FATAL: Configuration on agent 'clear4' 
differs from scheduler.
2009-11-20 15:05:44 scheduler[2502] : FATAL: The difference is Repository
2009-11-20 15:05:44 scheduler[2502] :   Observed on scheduler system: 
Repository: clear1 * 00 32 #
2009-11-20 15:05:44 scheduler[2502] :   Mismatch on clear4: Repository: clear1 
* 00 32 # Fri Nov 20 15:05:42 2009
2009-11-20 15:05:45 scheduler[2502] : FATAL: Configuration on agent 'clear6' 
differs from scheduler.
2009-11-20 15:05:45 scheduler[2502] : FATAL: The difference is FATAL
2009-11-20 15:05:45 scheduler[2502] :   Observed on scheduler system: FATAL: 
Setgid for group missing on /srv/fossology/repository
2009-11-20 15:05:45 scheduler[2502] :   Mismatch on clear6: Permissions: OK 
RepPath.conf
2009-11-20 15:05:45 scheduler[2502] : FATAL: Host 'clear2' failed self-test.
2009-11-20 15:05:45 scheduler[2502] : FATAL: Host 'clear3' failed self-test.
2009-11-20 15:05:45 scheduler[2502] : FATAL: Host 'clear4' failed self-test.
2009-11-20 15:05:45 scheduler[2502] : FATAL: Host 'clear6' failed self-test.
2009-11-20 15:05:45 scheduler[2502] : FATAL: Self Test failed.  Inconsistent 
agent(s) detected.  Exiting.


Once I make changes anywhere (agents or server) I can simply restart the 
fossology init script correct?
/etc/init.d/scheduler {start|stop|restart|force-reload}

I've been rebooting and praying very hard!!!

-Regards,
Gibran
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Re: [FOSSology] scheduler[4007] : FATAL: Scheduler and Repository errors?

[Laser, Mary]

Hi Gilbran,
The error below indicates inconsistent Hosts.conf files on the server 
(scheduler) and the clear4 and clear6 agents.  The script that performs this 
comparison is VERY PICKY.  The files must be EXACT - no carriage returns, white 
space, etc.   I would recommend you replace the Hosts.conf on the failing 
agents with the Hosts.conf file from the server.

Mary


From: fossology-boun...@fossology.org [mailto:fossology-boun...@fossology.org] 
On Behalf Of Furosh One
Sent: Saturday, November 21, 2009 8:17 PM
Anyone know of other areas I can check for this??


Then restarted fossology, '/etc/init.d/fossology restart' then cat the 
fossology.log and here's the new messages:

2009-11-20 15:45:43 scheduler[4007] : FATAL: Configuration on agent 'clear4' 
differs from scheduler.
2009-11-20 15:45:43 scheduler[4007] : FATAL: The difference is Repository
2009-11-20 15:45:43 scheduler[4007] :   Observed on scheduler system: 
Repository: clear6 * cd ff #
2009-11-20 15:45:43 scheduler[4007] :   Mismatch on clear4: Repository: clear6 
* cd ff # Fri Nov 20 15:45:40 2009
2009-11-20 15:45:44 scheduler[4007] : FATAL: Configuration on agent 'clear6' 
differs from scheduler.
2009-11-20 15:45:44 scheduler[4007] : FATAL: The difference is Repository
2009-11-20 15:45:44 scheduler[4007] :   Observed on scheduler system: 
Repository: clear2 * 33 65 #
2009-11-20 15:45:44 scheduler[4007] :   Mismatch on clear6: Repository: clear2 
* 33 65 # Fri Nov 20 15:45:40 2009
2009-11-20 15:45:44 scheduler[4007] : FATAL: Host 'clear4' failed self-test.
2009-11-20 15:45:44 scheduler[4007] : FATAL: Host 'clear6' failed self-test.
2009-11-20 15:45:44 scheduler[4007] : FATAL: Self Test failed.  Inconsistent 
agent(s) detected.  Exiting.

It seems after everything I check and/or change, I get a new error.
And I've even tried to look at the scripts that run to see what it's checking 
for to return these error messages.

-Regards,
Gmarquez

"I have not failed, I've just found 10,000 ways that won't work."
"If I find 10,000 ways something won't work, I haven't failed. I am not 
discouraged, because every wrong attempt discarded is another step forward."
"Results! I have gotten a lot of results. I know several thousand things that 
won't work."
-Thomas Alva Edison
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology