We are planning to release pulpcore==3.3.0 GA on April 8th. While we strive
for time-based releases, here are two items that we are hoping to include
based on feedback from Katello who would like to consume 3.3.0 in their
upcoming releases.
* The new repository repair API /pulp/api/v3/repair/ -
Hi,
I'd like to add one more question to this topic. Do you think it is a
blocker for PRs [0] & [1] as by testing [2] this features I haven't run
into real world example where two really same name packages appears.
I think this is a 'must have' feature but until we solve/decide it we can
have two
We'd like to start a discussion on the "relative path problem" identified
recently.
Problem:
Currently, a relative_path is tied to content in Pulp. This means that if a
content unit exists in two places within a repository or across
repositories, it has to be stored as two separate content units.
