Hello Everyone,

We would like to congratulate Darshan, Kaushlendra and Ayush for their contributions to FOSSology community. We are very impressed by the overall quality of their work and organizational skills, keep up the good work and stay in touch with community.

Details of features that were developed in this GSOC-2020.

Project : FOSSology

Student Name : Darshan Kansagara

Feature Title : Dashboard (Python, influxDB, Grafana)

Wiki : https://github.com/darshank15/GSoC_2020_FOSSOlogy/wiki

Project : Atarashi

Student Name : Ayush (HastagAB)

Feature Title : Accelerating Atarashi

Wiki : https://github.com/hastagAB/GSoC-2020

Project : Atarashi

Student Name : Kaushlendra Pratap Singh

Feature Title : Refurbishing Atarashi

Wiki : https://github.com/Kaushl2208/GSoC-2020

We would also like to thank mentors(Michael, Shaheem, Anupam, Gaurav, Nicolas, Aman and Sandeep) for helping students achieve their targets.

Best Regards

Shaheem Azmal M MD

Hello,

Just started to work on Fossology tool last few days.

I am trying to upload linux5.4.30 component which is around 1.7G and not able to upload the file even after changing “post_max_size” & “upload_max_filesize”.

I was able to upload and scan other components less than 700MB.

I have Fossology installed using docker on R640 Dell server.

FOSSology version 3.8.0-86-gf0c84e229 (code revision f0c84e)

Below are the details. Please provide details if any modifications are needed.

root@abbf7f77a767:/fossology#    cat /etc/php/7.0/apache2/php.ini|grep memory_limit

memory_limit = 1002M

root@abbf7f77a767:/fossology# cat /etc/php/7.0/apache2/php.ini|grep post_max_size

post_max_size = 4001M

root@abbf7f77a767:/fossology# cat /etc/php/7.0/apache2/php.ini|grep upload_max_filesize

upload_max_filesize = 3000M

Also made some tunable and config changes to few files.

/etc/sysctl.conf

kernel.shmmax=67328311296

kernel.shmall=16437576

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep max_connections

max_connections = 100                   # (change requires restart)

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep shared_buffers

#shared_buffers = 128MB                 # min 128kB

shared_buffers = 32GB                   # min 128kB

#wal_buffers = -1                       # min 32kB, -1 sets based on shared_buffers

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep effective_cache_size

#effective_cache_size = 4GB

effective_cache_size = 10GB

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep work_mem

#work_mem = 4MB                         # min 64kB

work_mem = 2GB                          # min 64kB

#maintenance_work_mem = 64MB            # min 1MB

maintenance_work_mem = 6GB              # min 1MB

#autovacuum_work_mem = -1               # min 1MB, or -1 to use maintenance_work_mem

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep maintenance_work_mem

#maintenance_work_mem = 64MB            # min 1MB

maintenance_work_mem = 6GB              # min 1MB

#autovacuum_work_mem = -1               # min 1MB, or -1 to use maintenance_work_mem

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep fsync

#fsync = on                             # flush data to disk for crash safety

fsync = on                              # flush data to disk for crash safety

#wal_sync_method = fsync                # the default is the first option

                                        #   fsync

                                        #   fsync_writethrough

#data_sync_retry = off                  # retry or panic on failure to fsync

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep full_page_writes

#full_page_writes = on                  # recover from partial page writes

full_page_writes = off                  # recover from partial page writes

root@abbf7f77a767:/fossology# cat /etc/postgresql//9.6/main/postgresql.conf |grep autovacuum

#autovacuum_work_mem = -1               # min 1MB, or -1 to use maintenance_work_mem

#autovacuum = on                        # Enable autovacuum subprocess?  'on'

autovacuum = on                         # Enable autovacuum subprocess?  'on'

#log_autovacuum_min_duration = -1       # -1 disables, 0 logs all actions and

..

Thanks!

Dear all,

I like to inform you, that I have added a .NET implementation of the FOSSology REST API

to the FOSSology GitHub project:

https://github.com/fossology/FOSSology.REST.dotnet

The implementation covers most of the REST commands.

The unit tests will run on FOSSology in a docker container. Our goal is to add one further step

to the automation of software license compliance.

Do not hesitate to drop me an email in case of questions or suggestions.

Best regards,

Thomas

Siemens AG
Smart Infrastructure
mailto:thomas.graf@...

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 (debian folder) from the master branch and put it into another branch like chore/debian/jessie.

This is done so to avoid conflicts as Debian maintainers will be editing this packaging information in the FOSSology mirror (hosted at Debian Sala). And any change in upstream can result in conflicts.

As this change will alter the packaging steps required by many of FOSSology users, we need your feedback.

I have opened an issue on GitHub for the same: https://github.com/fossology/fossology/issues/1341

Kindly respond either on this thread or on the GitHub issue if you have any concerns regarding the same.

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 systems remove texts that would be interesting for license analysis purposes. In java, you should look at uploading .java-files and not .class-files.

Best

Martin

Martin von Willebrand, Attorney-at-law, Partner
HH Partners, Attorneys-at-law Ltd
Bulevardi 7, 5th floor
P.O. Box 232, 00101 Helsinki, Finland
Tel: +358 9 177 613, Fax: +358 9 653 873
GSM: +358 40 770 1818
martin.vonwillebrand@...
www.twitter.com/mvonwi
www.hhpartners.fi
Validos ry, Chairman, www.validos.org

HH Partners shines in international rankings. See details at hhpartners.fi.

Privileged and confidential information may be contained in this message. If you are not addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, kindly notify us by reply e-mail and delete this message immediately. Thank you.

Lähettäjä: main@... [mailto:main@...] Puolesta marc.mcgarry@...
Lähetetty: perjantai 12. lokakuuta 2018 17.57
Vastaanottaja: main@...
Aihe: [FOSSology] Help a newbie

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,

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 for some binary analysis tool (- next generation) or so. class files are usually results of a compiler so they omit source code comments which is where licensing statements are usually in.

2. FOSSology should be able to unpack *.jar files, so no need to zip it, except you would like to upload a set of jar files at once. If fossology cannot look into a jar file, it is a bug (and should be thus put in the issues tracker).

3. what is your point with “test” what are look for exactly?

Kind regards, Michael