Yeh we are having problems where new RPM's are not always showing and it
isn't to do with the meta cache local on the box as we do a yum clean all
each time, sometimes they show and sometimes it's still showing only the
old version when we push a new file up and publish. It seems intermittent
and has only started happening since we upgraded 2.5 it has been fine for
months on 2.4 and i noticed that this looks like a new feature
implementation.

i can investigate further and raise a bug.

On 5 December 2014 at 17:25, Barnaby Court <[email protected]> wrote:

> Hi, This is by design.  If files have not been removed from the repo we
> perform an incremental publish which does not remove the old files.  If an
> RPM is removed from the repo we will perform a clean publish.  The
> repomd.xml will only reference the new files so yum should play nice.
>
> -Barnaby
>
> ----- Original Message -----
> From: "Jon Shanks" <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: Friday, December 5, 2014 12:16:53 PM
> Subject: [Pulp-list] quick functionality question about repo metadata
>
> Hi,
>
> I can't tell if there is a bug or if it's a new feature in pulp between
> 2.4 and 2.5 but the publish repo seems to create a new timestamped
> directory for the publish however the repodata directory still seems to
> retain other checksums and grows with each run i.e. the primary, filelist,
> updateinfo and other xml metadata seems to retain the previous meta
> information from the previous runs.
>
> Is there some reason for this?
>
> Thanks
>
> Jon
>
> _______________________________________________
> Pulp-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/pulp-list
>
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to