I noticed the repomd.xml on artifactory is a little different (see below). This
is why pulp doesn't sync when optimize is true. Is the revision optional field
in repomd.xml?
http://linux.duke.edu/metadata/repo;
xmlns:rpm="http://linux.duke.edu/metadata/rpm;>
FYI, the single container now includes pulp_python thanks to Fabricio.
https://hub.docker.com/repository/docker/pulp/pulp-fedora31
David
On Wed, Jan 13, 2021 at 8:06 AM David Davis wrote:
> Awesome! Thanks pulp_python team!
>
> David
>
>
> On Wed, Jan 13, 2021 at 4:00 AM Matthias Dellweg
>
The sync task examines the repomd.xml and the revision number in it. All
the logic for optimizing the sync is here[0].
[0]
https://github.com/pulp/pulp_rpm/blob/3.7/pulp_rpm/app/tasks/synchronizing.py#L169-L175
On Wed, Jan 13, 2021 at 1:45 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net>
Happy new year.
I run a mirrored sync with upstream. The sync didn't pick up new rpms in
upstream repo. I rerun sync with optimize=false and it synced all rpms. I do
see the file names from new rpms are in the filelists.xml.gz of the upstream
repodata. Just wondering which repo data does pulp
Awesome! Thanks pulp_python team!
David
On Wed, Jan 13, 2021 at 4:00 AM Matthias Dellweg
wrote:
> Yay, finally! Thank you!
>
> On Wed, Jan 13, 2021 at 4:43 AM Grant Gainey wrote:
>
>> On Tue, Jan 12, 2021 at 6:30 PM Gerrod Ubben wrote:
>>
>>> pulp_python 3.0.0 is now Generally Available!
Yay, finally! Thank you!
On Wed, Jan 13, 2021 at 4:43 AM Grant Gainey wrote:
> On Tue, Jan 12, 2021 at 6:30 PM Gerrod Ubben wrote:
>
>> pulp_python 3.0.0 is now Generally Available! [0] It is compatible with
>> pulpcore 3.9.0+.
>>
>
> Congratulations Gerrod - big milestone for pulp_python,
