Bug 2272927 - libsecret: One COPYING shadows the other in /usr/share/licenses/libsecret-devel/COPYING
Summary: libsecret: One COPYING shadows the other in /usr/share/licenses/libsecret-dev...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libsecret
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-03 10:05 UTC by Miro Hrončok
Modified: 2025-11-13 01:10 UTC (History)
5 users (show)

Fixed In Version: libsecret-0.21.7-7.fc43 libsecret-0.21.7-4.fc42
Clone Of:
Environment:
Last Closed: 2025-11-06 02:43:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2024-04-03 10:05:02 UTC
Description of problem:

The devel subpackage has:

  %files devel
  %license COPYING docs/reference/COPYING
  ...

And as a result, only one of the COPYING files is installed into /usr/share/licenses/libsecret-devel. RPM warns about this:

  File listed twice: /usr/share/licenses/libsecret-devel/COPYING

It seems to me that which file actually ends in the package is a matter of chance.
E.g. in the rawhide's libsecret-devel-0.21.3-1.fc41.x86_64 it is the docs/reference/COPYING one. However, when I build the package locally with mock, it is the LGPL one.


Version-Release number of selected component: 0.21.3-1.fc41


Steps to Reproduce:
1. build the package

Actual results:
RPM wanrs:  File listed twice: /usr/share/licenses/libsecret-devel/COPYING
Only one COPYING is included in the package, possibly an arbitrary one.

Expected results:
RPM does not warn. Both files are included in the package, if desired, under a different name (or location).

Comment 1 Kalev Lember 2024-04-03 21:00:06 UTC
Looks like this is a regression from commit https://src.fedoraproject.org/rpms/libsecret/c/1107d4a0c098b6b2c6345c484cb4be8e79a976dd

I guess there are a few ways to solve this, but the simplest is probably to just drop the "COPYING" file from libsecret-devel and only ship "docs/reference/COPYING".  The first "COPYING" file is already included in the base libsecret package (which libsecret-devel requires) and I don't think there is any need to install it again as part of the -devel package.

Comment 2 Miro Hrončok 2024-04-04 09:27:14 UTC
I concur with your conclusion that the first "COPYING" file does not need to be there.

However, the docs/reference/COPYING file does not apply to the entire devel package, so including just that as "COPYING" seems confusing.

Does the package even ship other files from docs/reference? If not, perhaps this COPYING file should not be shipped at all -- and the devel package should not include either of the files... ?

Comment 3 Aoife Moloney 2025-02-26 13:00:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 4 Debarshi Ray 2025-03-07 21:47:28 UTC
Recently, the following change was done:
 %files devel
-%license COPYING docs/reference/COPYING
+%license COPYING

... as part of this commit:
https://src.fedoraproject.org/rpms/libsecret/c/ed7ef7e6d4ae1b12c55fd979170e95178ca28bab


Together with this commit:
https://src.fedoraproject.org/rpms/libsecret/c/afc97c7fcf58dafdf05805b15e2d615d92ff0e19

... I see that the top-level COPYING file is now shipped by libsecret, libsecret-devel and libsecret-mock-service.  I don't know if that's a good or bad thing, but it seemed at least vaguely relevant here.  :)

Comment 5 Debarshi Ray 2025-03-07 21:49:29 UTC
(In reply to Miro Hrončok from comment #2)
> I concur with your conclusion that the first "COPYING" file does not need to
> be there.
> 
> However, the docs/reference/COPYING file does not apply to the entire devel
> package, so including just that as "COPYING" seems confusing.
> 
> Does the package even ship other files from docs/reference? If not, perhaps
> this COPYING file should not be shipped at all -- and the devel package
> should not include either of the files... ?

Yes, the libsecret-devel subpackage does ship the content from docs/reference, because that's the reference API documentation for libsecret.  Almost all libraries in the GNOME platform do something similar.

Comment 6 Fedora Admin user for bugzilla script actions 2025-03-19 03:41:45 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Fedora Admin user for bugzilla script actions 2025-10-31 02:12:34 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 8 Debarshi Ray 2025-11-03 22:59:04 UTC
We should also update the License tag to include docs/reference/COPYING (ie., GCR-docs).

Comment 9 Fedora Update System 2025-11-03 23:02:09 UTC
FEDORA-2025-04cb513f17 (libsecret-0.21.7-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-04cb513f17

Comment 10 Fedora Update System 2025-11-04 04:20:53 UTC
FEDORA-2025-04cb513f17 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-04cb513f17`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-04cb513f17

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-11-05 16:51:25 UTC
FEDORA-2025-7998c8fb4c (libsecret-0.21.7-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7998c8fb4c

Comment 12 Fedora Update System 2025-11-06 02:43:24 UTC
FEDORA-2025-04cb513f17 (libsecret-0.21.7-7.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-11-06 03:38:38 UTC
FEDORA-2025-7998c8fb4c has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7998c8fb4c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7998c8fb4c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2025-11-13 01:10:25 UTC
FEDORA-2025-7998c8fb4c (libsecret-0.21.7-4.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.