Re: Heads up: merging SPDX related PRs
On Thu, Aug 24, 2023 at 11:08:14PM +0200, Sandro wrote: ...snip... > > I see. Could some sysadmin with supercow powers insert a tag globally? Or > would that be treading on a great many toes? We looked at adding some 'standard' tags, but they would need to be added to each package seperately. So, 30,000+ things per tag. It didn't seem worth the churn. When/if we move to some other setup, having some standard tags seems like a nice idea though. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
On Sun, 2023-08-20 at 12:19 +0200, Miroslav Suchý wrote: > Over the time we had several workshops about SPDX. Some people did > the SPDX migrations for others (me included). From file https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt I retrieve packages with my fas user and adapt one script to mass update my packages https://github.com/sergiomb2/herlper_scripts/blob/main/fedora/license-invalid-as-spdx.sh But I still have these to commit [1], the question is can you generate all PR(s) for trivial licenses (automatically) ? Thank you [1] dh-make - can be trivially converted to GPL-3.0-or-later docker-compose - can be trivially converted to Apache-2.0 dvdauthor - can be trivially converted to GPL-2.0-or-later fedora-dockerfiles - can be trivially converted to GPL-2.0-only fedora-review-plugin-java - can be trivially converted to GPL-2.0-or- later frei0r-plugins - can be trivially converted to GPL-2.0-or-later gammu - can be trivially converted to GPL-2.0-or-later ganyremote - can be trivially converted to GPL-3.0-or-later golang-github-containerd-aufs - can be trivially converted to Apache- 2.0 golang-github-containerd-btrfs - can be trivially converted to Apache- 2.0 golang-github-containerd-imgcrypt - can be trivially converted to Apache-2.0 golang-github-mitchellh-cli - can be trivially converted to MPL-2.0 google-gson - can be trivially converted to Apache-2.0 jdependency - can be trivially converted to Apache-2.0 kanyremote - can be trivially converted to GPL-3.0-or-later keychain - can be trivially converted to GPL-2.0-only libkgapi - can be trivially converted to GPL-2.0-or-later libprojectM - can be trivially converted to GPL-2.0-or-later libsmbios - can be trivially converted to GPL-2.0-or-later OR OSL-2.1 megaglest - can be trivially converted to GPL-3.0-or-later AND GPL-1.0- or-later movit - can be trivially converted to GPL-2.0-or-later pdfbox - can be trivially converted to Apache-2.0 perl-File-FcntlLock - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Git-Wrapper - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Mail-Box - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl perl-Mail-Transport-Dbx - can be trivially converted to GPL-2.0-or- later AND ( GPL-1.0-or-later OR Artistic-1.0-Perl ) perl-Object-Realize-Later - can be trivially converted to GPL-1.0-or- later OR Artistic-1.0-Perl perl-User-Identity - can be trivially converted to GPL-1.0-or-later OR Artistic-1.0-Perl platform - can be trivially converted to GPL-2.0-or-later po-debconf - can be trivially converted to GPL-2.0-or-later po4a - can be trivially converted to GPL-1.0-or-later python-apt - can be trivially converted to GPL-2.0-or-later python-gammu - can be trivially converted to GPL-2.0-or-later python-html2text - can be trivially converted to GPL-3.0-only python-libnacl - can be trivially converted to Apache-2.0 rawstudio - can be trivially converted to GPL-2.0-or-later redhat-lsb - can be trivially converted to GPL-2.0-only smb4k - can be trivially converted to GPL-2.0-or-later tetrinetx - can be trivially converted to GPL-2.0-only ufraw - can be trivially converted to GPL-2.0-or-later usb_modeswitch - can be trivially converted to GPL-2.0-or-later vid.stab - can be trivially converted to GPL-2.0-or-later webalizer - can be trivially converted to GPL-2.0-or-later -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
On 23-08-2023 14:55, Miroslav Suchý wrote: Dne 23. 08. 23 v 12:44 Sandro napsal(a): On 20-08-2023 12:19, Miroslav Suchý wrote: If you are workshop participant and have PR opened for longer than 14 days then let me know and I will merge it. Here's the one I made during Flock workshop: https://src.fedoraproject.org/rpms/90-Second-Portraits/pull-request/1 +1 Well, hours after I wrote above, the PR evolved into something broader. For folks interested, see the thread on the legal list [1]. Maybe it's a good idea to somehow tag these, so you get to see submitted SPDX related PRs instead of us having to report these manually? Interresting idea... but no. As reporter you can only tag the PR with tag that already exist in the project. And only owner of the project can create the tag. I see. Could some sysadmin with supercow powers insert a tag globally? Or would that be treading on a great many toes? [1] https://lists.fedoraproject.org/archives/list/le...@lists.fedoraproject.org/message/FEDCV5RVSSXSESWSLOX3CJQF776EJU4W/ -- Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
Dne 23. 08. 23 v 12:44 Sandro napsal(a): On 20-08-2023 12:19, Miroslav Suchý wrote: If you are workshop participant and have PR opened for longer than 14 days then let me know and I will merge it. Here's the one I made during Flock workshop: https://src.fedoraproject.org/rpms/90-Second-Portraits/pull-request/1 +1 Maybe it's a good idea to somehow tag these, so you get to see submitted SPDX related PRs instead of us having to report these manually? Interresting idea... but no. As reporter you can only tag the PR with tag that already exist in the project. And only owner of the project can create the tag. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
On 20-08-2023 12:19, Miroslav Suchý wrote: If you are workshop participant and have PR opened for longer than 14 days then let me know and I will merge it. Here's the one I made during Flock workshop: https://src.fedoraproject.org/rpms/90-Second-Portraits/pull-request/1 Maybe it's a good idea to somehow tag these, so you get to see submitted SPDX related PRs instead of us having to report these manually? -- Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
Dne 21. 08. 23 v 10:32 Florian Weimer napsal(a): Over the time we had several workshops about SPDX. Some people did the SPDX migrations for others (me included). Some of the PR are not merged yet. E.g. https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/251 The License: field is incomplete, it needs to pick up the autoconf exception. Fixed. Nice catch. Thank you. In past I waited until it is merged. Now I plan to be more progressive and I plan in these individual cases to: 1) create PR 2) wait 14 days 3) if there will be no response, the I will merge it as a proven packager. I assume you plan to translate just the License: field and not look at the actual license references in the source code for this. If that approach is acceptable, package maintainers could do the same thing. It would significantly speed up the conversion (e.g., no need to run fossology). No. I on these workshops we have done the full work. Not just plain translation of License field. But as you saw above - nobody is perfect. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: merging SPDX related PRs
* Miroslav Suchý: > Over the time we had several workshops about SPDX. Some people did the SPDX > migrations for others (me included). > > Some of the PR are not merged yet. E.g. > > https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/251 The License: field is incomplete, it needs to pick up the autoconf exception. > In past I waited until it is merged. Now I plan to be more progressive > and I plan in these individual cases to: > > 1) create PR > > 2) wait 14 days > > 3) if there will be no response, the I will merge it as a proven packager. I assume you plan to translate just the License: field and not look at the actual license references in the source code for this. If that approach is acceptable, package maintainers could do the same thing. It would significantly speed up the conversion (e.g., no need to run fossology). Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads up: merging SPDX related PRs
Over the time we had several workshops about SPDX. Some people did the SPDX migrations for others (me included). Some of the PR are not merged yet. E.g. https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/251 https://src.fedoraproject.org/rpms/anaconda-user-help/pull-request/2 In past I waited until it is merged. Now I plan to be more progressive and I plan in these individual cases to: 1) create PR 2) wait 14 days 3) if there will be no response, the I will merge it as a proven packager. If you are workshop participant and have PR opened for longer than 14 days then let me know and I will merge it. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
