Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Faulty epel-release from the (unofficial) armhfp epel repo breaks updates #41

Closed
markVnl opened this issue Jun 4, 2020 · 3 comments
Closed

Faulty epel-release from the (unofficial) armhfp epel repo breaks updates #41

markVnl opened this issue Jun 4, 2020 · 3 comments
Assignees
@markVnl
Labels
bug verified

Comments

@markVnl
Copy link
Member

markVnl commented Jun 4, 2020 •
edited

The (noarch) package epel-release-7-12.noarch.rpm landed in the the unofficial armhfp-epel repository.

This package conflicts with nethserver-arm-epel
Moreover the yum configuration (epel.repo) it would pull in points to non-exsisting repositories.

Proposal:

  • exclude the offending package in (our) working yum epel.repo configuration
@markVnl markVnl mentioned this issue Jun 4, 2020
Merged
@markVnl markVnl self-assigned this Jun 4, 2020
@markVnl markVnl added the bug label Jun 4, 2020
@markVnl
Copy link
Member Author

markVnl commented Jun 5, 2020 •
edited

In nethserver-arm testing is a package with above proposal:

(if you did install the faulty epel-release remove this first and (re)install nethserver-arm-epel)

yum update --enablerepo=nethserver-testing nethserver-arm-epel

After installation of this test package the epel-release package should be ignored.

@markVnl
Copy link
Member Author

markVnl commented Jun 8, 2020

nethserver-arm-epel-7.2 released.

Note
Revisit this workaround if upstream (CentOS) moved somewhere on this issue.

See comments in PR including
https://lists.centos.org/pipermail/arm-dev/2020-June/007867.html

@markVnl
Copy link
Member Author

markVnl commented Jun 8, 2020

Closing with the above promise.

@markVnl markVnl closed this as completed Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markVnl markVnl

Labels
bug verified
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@markVnl