Hello all, During our effort to publish FOSSology as a Debian package, we got few suggestions from the Debian community. One of those suggestion is to remove the Debian packaging information

Hello all, After two release candidates, making fixes for REST API installation and various migration tests, FOSSology is stable enough for a new release. The main features of the 3.5.0 release can be

Hello, currently, I am not aware of the FOSSology project planning to support "ALL features of SPDX 2.1 specification in future releases", for a number of reasons, just a few examples: * Spec 2.1

Hi all, As announced in the release, https://github.com/fossology/fossology/wiki/FOSSology-3.1-Release-Announcement-(Working-Version) Key features in FOSSology 3.1 are: Support for SPDX 2.1 document

Fossology agent doing the unpacking will unpack zip-packages and jar-packages, even if they are nested. You likely want to run source code files through Fossology, though, because many build

Hello, oh interesting, I have not seen your point from your answer, glad that our e-mails crossed. Kind regards, Michael

Hello, your mail raises a few questions, I try to bring a few considerations. 1. „classes“ refers to *.class files? if yes, then this is maybe not the right thing for FOSSology, but maybe

Hi Marc, Yes, Fossology will open all compressed files (zip, tgz, jar, etc.) and scan the contents. This is done recursively, so that a jar in a zip is also opened and its

I am trying to run software packages/components through fossology. If i zip the package folder (with the jar file inside), will this successfully test all of the classes inside?

Hello again, I came to the conclusion that, - from an SPDX point of view, the packages is what I need to describe the embedded components and dependencies included in the scanned project - The SPDX

Dear All, I am having a hard using Fossology to fulfil my needs efficiently. I would like to share one of the core aspect I am struggling with, and would love to see if some of you are facing the same

3.3.0 worked well when I tried it for eval purposes...

Hello, maybe soon ready by Anupam: https://github.com/fossology/fossology/pull/1122 Or, you could try the last release, 3.3.0 where we did not see the errors. Kind regards, Michael

Hey, thanks for the answer. Restarting the scheduler as you mentioned help me for the first time. Unfortunately I have to do a more complex license scan until next Thuesday and have to

Yeah, that worked. Thanks!

Hello, looks like we have an unfortunate time with the scheduler the past days. Regarding the apache message: I am not sure if this indicates a serious problem. As far as I know the server

Hello, I am new to Flossology and have installed the software using vagrant and Virtualbox. The installation worked fine and I can use a Fossology instance on

Hello Geoffrey, Please restart the scheduler. You can do it by using the running container name and calling exec on it. To get current container name or id, run: docker container ls CONTAINER ID

Just uploaded 74 k .zip file. Nothing happened. My show jobs page now shows 6 jobs waiting. The scheduler status still shows Connection to the scheduler failed. Is the scheduler