[Pulp-list] Pulp publish ordering

[Frédéric Conrotte]

Hello

We have an issue with the order used by Pulp to publish our RPMs.

We are using a continuous integration process where we publish a new snapshot RPM with each commit, which means we have several versions of the same binary in our repo.

Each RPM is named with the pattern <rpm name>-<version>-<build>.noarch.rpm

Which means we produce for instance:
myrpm-0.0.1-1.noarch.rpm
myrpm-0.0.1-2.noarch.rpm
myrpm-0.0.1-3.noarch.rpm
myrpm-0.0.1-4.noarch.rpm
in our repo

The problem is that the "pulp-admin rpm repo publish run" command does not respect the build number ordering.

[root at d0puppetmaster victorbuckservices]# pwd
/var/www/pub/yum/http/repos/victorbuckservices

[root at d0puppetmaster victorbuckservices]# ls -l vbackbone-datamanager-0.2.0-*
lrwxrwxrwx 1 apache apache 172 Jan  8 16:29 vbackbone-datamanager-0.2.0-840.noarch.rpm -> /var/lib/pulp/content/rpm/vbackbone-datamanager/0.2.0/840/noarch/48b449d6b741f6ffa899231fbf01eb1138fa2cd8461f0f0ffeba86cfb9dbab09/vbackbone-datamanager-0.2.0-840.noarch.rpm
lrwxrwxrwx 1 apache apache 172 Jan  8 16:29 vbackbone-datamanager-0.2.0-833.noarch.rpm -> /var/lib/pulp/content/rpm/vbackbone-datamanager/0.2.0/833/noarch/770e94499567267a76e1237bb2f73a79767d38bd9826e72820269aefa291110a/vbackbone-datamanager-0.2.0-833.noarch.rpm
lrwxrwxrwx 1 apache apache 172 Jan  8 16:29 vbackbone-datamanager-0.2.0-832.noarch.rpm -> /var/lib/pulp/content/rpm/vbackbone-datamanager/0.2.0/832/noarch/ca9bf712fcf499391594877103caae1faf8428f2c58a1a59afe7324fbda6dfd8/vbackbone-datamanager-0.2.0-832.noarch.rpm
lrwxrwxrwx 1 apache apache 172 Jan  8 16:29 vbackbone-datamanager-0.2.0-829.noarch.rpm -> /var/lib/pulp/content/rpm/vbackbone-datamanager/0.2.0/829/noarch/9a98ff8308765ff6218d78df1a6f066c35bc32516264ce292bc2fac827a7867d/vbackbone-datamanager-0.2.0-829.noarch.rpm
lrwxrwxrwx 1 apache apache 172 Jan  8 16:29 vbackbone-datamanager-0.2.0-728.noarch.rpm -> /var/lib/pulp/content/rpm/vbackbone-datamanager/0.2.0/728/noarch/11874a76ddcaed2da0d87f67925f7e025a590749cd9adb1a9f8794e878acffb2/vbackbone-datamanager-0.2.0-728.noarch.rpm

Look at the "build" part of the RPM name, ls -rtl does not order them sequentially, which means the publish command did not take in account the time at which they were uploaded.

Furthermore, I've been digging into the following files

/repodata/*-filelists.xml.gz
/repodata/*-other.xml.gz
/repodata/*-primary.xml.gz
/repodata/*-updateinfo.xml.gz

and I cannot find the latest uploaded RPM in these files.

Can you explain either:

-        How the publish command could meet my requirement?

-        How the repodata files are generated ?

Many thanks for your help

Fred

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20150108/11ccbac5/attachment.htm>