Bug 2050854 - snapd is not installable on Amazon Linux 2
Summary: snapd is not installable on Amazon Linux 2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: snapd
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zygmunt Krynicki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-04 19:19 UTC by Brad Warren
Modified: 2022-02-04 19:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-04 19:44:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brad Warren 2022-02-04 19:19:21 UTC
Description of problem: snapd is not installable on Amazon Linux 2


Version-Release number of selected component (if applicable): 2.54.2-1.el7


How reproducible: always


Steps to Reproduce:
1. sudo amazon-linux-extras install epel
2. sudo yum install snapd

Actual results:

Error: Package: snapd-selinux-2.54.2-1.el7.noarch (epel)
           Requires: selinux-policy-base >= 3.13.1-268.el7_9.2
           Installed: selinux-policy-targeted-3.13.1-192.amzn2.6.7.noarch (installed)
               selinux-policy-base = 3.13.1-192.amzn2.6.7


Expected results: snapd is installed

Additional info:

The problem can be made smaller by installing Amazon's selinux-ng extra. After doing this using the command `sudo amazon-linux-extras install selinux-ng`, the error becomes:

Error: Package: snapd-selinux-2.54.2-1.el7.noarch (epel)
           Requires: selinux-policy-base >= 3.13.1-268.el7_9.2
           Installed: selinux-policy-targeted-3.13.1-268.amzn2.2.2.noarch (@amzn2extra-selinux-ng)
               selinux-policy-base = 3.13.1-268.amzn2.2.2

Is it possible to relax snapd-selinux's selinux-policy-base dependency to make it easier to install snapd on Amazon Linux 2? Given the popularity of Amazon Linux 2 in EC2, I think making it installable there would be a significant benefit to the snap ecosystem.

I've also been talking to Amazon about this, but the best suggestion I've got from them so far is to install selinux-ng and ignore the dependency conflict. Is it possible to resolve the issue here or make it easier for them to resolve there?

Comment 1 Maciek Borzecki 2022-02-04 19:44:30 UTC
This is exactly what is also generated by %{selinux_requires} RPM macro. I'm not a SELinux expert, but given that the modules are compiled down to a binary representation, I would assume that policy versions have meaning and it's not a matter of relaxing the dependency.

You can always rebuild the package yourself from the source RPM or suggest to Amazon to provide snapd in their Extras repository. I'm not a customer of Amazon, so I have no say in what they provide in their repositories.


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