Project

Profile

Help

Story #4001

As a user I would like to add modulemd and modulemd-defaults to the skip list

Added by paji@redhat.com about 3 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Pulp rpm repo type now lets you skip the following units when syncing rpm, drpm, srpm, erratum and distribution.
For consistency it might make more sense to add modulemd and modulemd-defaults also.

When the user specifies a modulemd to be skipped, the RPMs for that module should not be synced either. Modulemd-defaults should not be synced either.

History

#1 Updated by dkliban@redhat.com about 3 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#2 Updated by ipanova@redhat.com about 3 years ago

this skip list will lead to the situation when modular rpms will be synced and become ursine.
Ursine modular rpm can break client's system.

This would make sense only in case rpms are skipped along with modulemd.

#3 Updated by ttereshc about 3 years ago

+1 to Ina's point.

That skip functionality should be smart and skip related RPMs as well.
If there is no real demand for that feature, I wouldn't add it just for the sake of consistency.

#4 Updated by amacdona@redhat.com about 3 years ago

  • Groomed changed from Yes to No
  • Sprint Candidate changed from Yes to No

#5 Updated by dkliban@redhat.com about 3 years ago

  • Description updated (diff)

Updated the description to include the 'smart' behavior.

#6 Updated by paji@redhat.com about 3 years ago

  1. Do you guys do the "smart" behavior for errata ?
  2. I could see this feature useful if some repo or cdn has broken module md while good packages. I would agree it being a lower priority.
  3. Where does this word "ursine" come from ....

#7 Updated by ttereshc about 3 years ago

1. Do you guys do the "smart" behavior for errata ?

No, we don't.
RPMs and an Erratum where they are referred can be both present in a repo but they also can live separately:
- only RPMs are synced - it's fine,
- only Erratum is synced - it's fine (it can be on purpose, so user selectively adds RPMs to a repo later). Only Errata and no RPMs is quite useless but harmless,
- both RPMs and an Erratum are synced - it's fine.

For modules it's critical to do it smart way:
- only a module is synced and no RPMs - it's bad, it's a broken module, tools like dnf will complain.
- only modular RPMs are synced - it's bad, even worse than the previous case, because it can mess up dependency resolution (modular rpms will be used when non-modular should be) .
- a module and all its RPMs are sync - it's the only good option.

2. I could see this feature useful if some repo or cdn has broken module md while good packages. I would agree it being a lower priority.

I understand this potential use case, however see my comment above, it's not worth risking, in my opinion. If RPMs are good they won't be re-downloaded, just checked during a sync.

3. Where does this word "ursine" come from ....

Modularity folks use it a lot. I guess it describes how bad/damaging and clumsy modular RPMs can be when they don't have their module in a repo ;)

#8 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#9 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF