Bug 26719

Summary:	Add libseccomp-static to Mageia repos to port snapd from Fedora
Product:	Mageia	Reporter:	Kristoffer Grundström <lovaren>
Component:	New RPM package request	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	libseccomp-static-devel	CVE:
Status comment:

Description Kristoffer Grundström 2020-06-02 23:58:08 CEST

Description of problem: I took a look in the Fedora spec file for snapd and it clearly says that libseccomp-static is needed to build snapd.

Version-Release number of selected component (if applicable): 2.4.3

How reproducible: All the time.

Steps to Reproduce:
1. Open your browser.
2. Go to https://www.pkgs.org/download/snapd
3. Download the src.rpm from one of the Fedora versions.
4. Extract the spec file.
5. Open the spec file.
6. One of the BuildRequires in that spec file is called libseccomp-static
7. Do urpmq -y libseccomp-static and you won't get any hits.

Comment 1 Kristoffer Grundström 2020-06-02 23:59:13 CEST

The src.rpm can be found here: https://fedora.pkgs.org/rawhide/fedora-x86_64/snapd-2.45-1.fc33.x86_64.rpm.html

Comment 2 Lewis Smith 2020-06-03 20:55:50 CEST

Are you asking for snapd itself (whatever it is) to be added to Mageia?
For libseccomp, we have it.

If this new package request is specifically for the static version to enable the port (by whom?) of a Fedora package, this looks out of court.

CC: (none) => lewyssmith

Comment 3 Kristoffer Grundström 2020-06-03 23:11:52 CEST

1. To begin with I'm asking to get libseccomp-static packaged.
2. I'm working on porting snapd to Mageia 7.

Comment 4 Lewis Smith 2020-06-04 22:28:18 CEST

Understood.
I doubt that this new pkg request is valid if it is only to enable the snapd port. Could you not include libseccomp-static as part of that port?

I do not like closing anything 'invalid' where the intention is good, but with Mageia 8 starting testing, the packagers are more than busy.
Appreciate your interest anyway.

Resolution: (none) => INVALID
Status: NEW => RESOLVED