| Summary: | repoman wrongly complains about 'Gentoo Foundation' copyright in old ebuilds | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Repoman | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ulm |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
repoman: Allow legacy "Gentoo Foundation" copyright before 2019.
repoman: Allow legacy "Gentoo Foundation" copyright before 2019. |
||
|
Description
Michał Górny
2019-06-18 07:06:03 UTC
(In reply to Michał Górny from comment #0) > I'm pretty sure the policy so far was not to change copyright headers > unless you were changing the ebuild as well. I don't think that we have defined any such policy. Please provide a reference. "Gentoo Foundation" agrees neither with GLEP 76 nor with tree policy (quoted in the first paragraph of the commit message), so repoman should display a warning. In any case, repoman will only update the header if the ebuild has changed. (In reply to Ulrich Müller from comment #1) > "Gentoo Foundation" agrees neither with GLEP 76 nor with tree policy (quoted > in the first paragraph of the commit message), so repoman should display a > warning. Correction: Theoretically, "Copyright YEARS Gentoo Foundation" could be a valid attribution by GLEP 76, if all authors of the file had previously assigned copyright to Gentoo Technologies Inc., and if subsequently the ebuild hasn't had any copyrightable changes after 2005. However, I believe that finding even a single such example would be hard. Also, it would still not comply with tree policy. If you believe old ebuilds should be updated, then let's mass-update them instead of having people bothered by repoman warnings for ancient ebuilds. (In reply to Michał Górny from comment #3) > If you believe old ebuilds should be updated, then let's mass-update them > instead of having people bothered by repoman warnings for ancient ebuilds. This was discussed in the 20190113 Council meeting, and (tacid) consensus was that we won't do a change in bulk, but update ebuilds as we go along. Then repoman shouldn't bother people if there is no other change pending. Created attachment 580074 [details, diff]
repoman: Allow legacy "Gentoo Foundation" copyright before 2019.
As discussed in #gentoo-portage.
Created attachment 580076 [details, diff]
repoman: Allow legacy "Gentoo Foundation" copyright before 2019.
Small update, with fixed grouping inside the if statement.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=31465138ddc319a98eae71f95b9fb3a07b866f62 commit 31465138ddc319a98eae71f95b9fb3a07b866f62 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2019-06-18 11:48:33 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2019-06-18 18:41:31 +0000 repoman: Allow legacy "Gentoo Foundation" copyright before 2019. Bug: https://bugs.gentoo.org/688278 Signed-off-by: Ulrich Müller <ulm@gentoo.org> Signed-off-by: Zac Medico <zmedico@gentoo.org> repoman/lib/repoman/modules/linechecks/gentoo_header/header.py | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a639af12aa9535a903e7a13a88a71e3cd0acd1d commit 6a639af12aa9535a903e7a13a88a71e3cd0acd1d Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2019-06-20 01:17:24 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2019-06-20 01:18:44 +0000 app-portage/repoman: Bump to version 2.3.15 #688278 Accept 'Gentoo Foundation' copyright for old ebuilds Closes: https://bugs.gentoo.org/688278 Package-Manager: Portage-2.3.67, Repoman-2.3.15 Signed-off-by: Zac Medico <zmedico@gentoo.org> app-portage/repoman/Manifest | 1 + app-portage/repoman/repoman-2.3.15.ebuild | 63 +++++++++++++++++++++++++++++++ 2 files changed, 64 insertions(+) |