Issue #222: prepopulate should respect obsoletes - pungi

pungi

#222 prepopulate should respect obsoletes

Closed: Invalid None Opened 8 years ago by lkocman.

Seems like prepopulate mechanism drags in rpms that were obsoleted by something new.
Could we basically not include any obsoleted packages even if they're in prepopulate?

https://bugzilla.redhat.com/show_bug.cgi?id=1309236#c3

Thanks

Lubos

lkocman commented 8 years ago

Other option would be to allow this and simply say that people need to configure expected behavior ... This is not valid behavior in RHEL world where the compose represents just "latest state of product in time" however the history of product lives in delivery channels ... thus we don't want to put these obsoleted bits into "compose (read snapshot of product in time, with only latest pkgs)

ausil commented 8 years ago

I can not see the bug so i do not know what is in it. however we should include all rpms even if they are obsoleted if the configs say pull them in.

lsedlar commented 8 years ago

I agree with Dennis that if config says a package should go in, it should go in.

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Milestone

None

pungi

Source Code

Documentation

#222 prepopulate should respect obsoletes Closed: Invalid None Opened 8 years ago by lkocman.

Metadata

#222 prepopulate should respect obsoletes

Closed: Invalid None Opened 8 years ago by lkocman.