-
Notifications
You must be signed in to change notification settings - Fork 148
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.
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
Conflict satellite-maintain < 0.0.3 #11378
Conversation
No
|
Repoclosure complains about this, which I don't understand, as the We could use the same "hack" we did in Line 6 in 0baf56d
But I hoped this is not necessary 😞 |
Looks like the repoclosure issue is a "known issue" in DNF world at least: rpm-software-management/dnf-plugins-core#549 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK!
I'm liking the conditional dependencies!
Okay, but we gate our publishing on repoclosure (not like some other projects cough), so that means we need the |
I actually kind of like the Just throwing another thought out there: would using |
I am not sure what DNF would do about that (prefer to upgrade s-m vs keep the old f-m package), but certainly can try? |
62d9866
to
4532a29
Compare
update not available:
update available:
|
packages/foreman/rubygem-foreman_maintain/rubygem-foreman_maintain.spec
Outdated
Show resolved
Hide resolved
In foreman_maintain 1.8.0 we moved some Satellite-specific metadata to the Satellite-specific satellite-maintain package, but the normal upgrade procedure doesn't enforce the right satellite-maintain version to be present, thus leading to upgrade errors. Let's enforce this requirement at the package level.
4532a29
to
f5c4cde
Compare
In foreman_maintain 1.8.0 we moved some Satellite-specific metadata to
the Satellite-specific satellite-maintain package, but the normal
upgrade procedure doesn't enforce the right satellite-maintain version
to be present, thus leading to upgrade errors. Let's enforce this
requirement at the package level.