[
https://ovirt-jira.atlassian.net/browse/OVIRT-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25073#comment-25073
]
Pavel Zhukov commented on OVIRT-997:
------------------------------------
[[email protected]]
The explanation why it happens is here:
{quote}The idea of repoman is to
1. Take all the sources.
2. Filter each of them.
3. Join the packages after filters together and form the repo.
In this case we use several sources S(1), S(2), ... S(N) each with
"only-missing" filter. When only-missing filter is used for each S(N+1) it
checks if package with such name is already sourced from S(N) and it is there
then it will skip the addition. No version comparison is done for
"only-missing" and it is as expected as the idea of the filter is to append
missing packages.
I think you need to use "latest" filter instead of "only-missing", e.g.
"latest=1" will keep only latest version of each package from the source. Then
if several source have the same package it will take 1 latest version from each
and it should be safe as yum/dnf will install the latest version from
compose.{quote}
https://gerrit.ovirt.org/#/c/68788/2
If several sources are used you have to use latest=1 parameter. Otherwise only
first artifact will be used.
> master/latest.tested and 4.1/latest.tested are not populated with nightly
> builds of ovirt-provider-ovn
> ------------------------------------------------------------------------------------------------------
>
> Key: OVIRT-997
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-997
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: danken
> Assignee: infra
>
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
