-Shore-
Services-China-BJ)
Sent: Tuesday, February 15, 2011 3:56 PM
To: Jeroen Baten
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails Package
Scan
Thanks Jeroen, I'll use this for debugging.
Vincent
-Original Message-
From: Jeroen
@fossology.org
Subject: RE: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails
Package Scan
So it is!
Files associated with
be9651c3d92b8a76fd3d0c03ff5597411e8ff860.a0fd8e3774fed62abeb6c2cda33
62862.2639
1: Folder: Software Repository/
Fossology_1_3_0
] Weird scan of fossology-1.3.0.tar.gz fails Package
Scan
Fedora 14
On Tue, 2011-02-15 at 08:11 +, Ma, Dong (Vincent,
ES-Best-Shore-Services-China-BJ) wrote:
Hi Jeroen,
In my test system(Debian Lenny), this file mimetype didn't recognize as '
application/x-rpm ', what's your system
: RE: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails Package
Scan
Fedora 14
On Tue, 2011-02-15 at 08:11 +, Ma, Dong (Vincent,
ES-Best-Shore-Services-China-BJ) wrote:
Hi Jeroen,
In my test system(Debian Lenny), this file mimetype didn't recognize as '
application/x
Don't know if this helps, but this is a relevant piece of the log:
2011-02-10 13:42:27 scheduler[716] : Child[15] 'agent=pkgagent
host=localhost ' state=SPAWNED(4) @ Thu Feb 10 13:42:27 2011
2011-02-10 13:42:27 scheduler[716] : Child[15] 'agent=pkgagent
host=localhost ' state=READY(5) @ Thu Feb
This was supposed to be fixed on January 13.
http://bugs.linux-foundation.org/show_bug.cgi?id=596
1.3.0 was released January 19. Mary, did this fix get into 1.3.0?
Bob Gobeille
On Feb 11, 2011, at 1:47 AM, Jeroen Baten wrote:
Don't know if this helps, but this is a relevant piece of the log:
To: Jeroen Baten; Laser, Mary
Cc: fossology@fossology.org
Subject: Re: [FOSSology] Weird scan of fossology-1.3.0.tar.gz fails
Package Scan
This was supposed to be fixed on January 13.
http://bugs.linux-foundation.org/show_bug.cgi?id=596
1.3.0 was released January 19. Mary, did this fix get
This is the info I found. Maybe it helps you people.
Kind regards, Jeroen Baten
jq_pk 128
jq_job_fk 108
job_namePackage Scan
jq_type pkgagent
job_priority0
jq_args SELECT pfile_pk as pfile_pk, pfile_sha1 || '.' || pfile_md5 ||
'.' || pfile_size AS pfilename, mimetype_name
Hi Jeroen,
The best place to see why an agent failed is in the fossology log file
(/var/log/fossology/fossology.log).
If you look there and see a spawning too fast error, that is a known (major)
bug. See:
http://bugs.linux-foundation.org/show_bug.cgi?id=636
If it is something different than
9 matches
Mail list logo