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
Fred,
Pulp does not make guarantees about preserving mtime on files or ensuring that
mtime sorts in lock-step with epoch-version-release. That is not a use case
pulp tries to support, but it would be interesting to know why that's useful to
you.
Publishing a yum repo makes it available to the
On 01/07/2015 05:49 PM, ben.stan...@exemail.com.au wrote:
Here is info about where pulp logs things:
https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging
The documentation there regarding rsyslogd is incorrect (at least for RHEL7).
Hi Ben,
I filed a bug about this
Pulp 2.5.2-0.2.beta is now available in the beta repo. This release addresses
the following issues:
https://bugzilla.redhat.com/show_bug.cgi?id=1179463
https://bugzilla.redhat.com/show_bug.cgi?id=1171278
https://bugzilla.redhat.com/show_bug.cgi?id=1159040