Did a quick test and the patch i mentioned is not involved.

Note that I only see this problem with EPEL, not with RHEL repos which also 
publishes erratas/advisories. So the problem is probably on the EPEL side, or..?


//Adam


________________________________
From: [email protected] <[email protected]> on behalf of 
Winberg Adam <[email protected]>
Sent: 08 February 2021 10:55
To: [email protected]
Subject: Re: [Pulp-list] epel syncs all advisories every time


I'm not sure, but I think this behaviour might have started after I applied the 
following patch:

https://github.com/pulp/pulp_rpm/commit/1652026913308e8348543af6f62c3b5c5f89985b#diff-0b195d23762f04b205940bafb5889ddf96181afde122ead35f8c65fe03527647


//Adam


________________________________
From: [email protected] <[email protected]> on behalf of 
Winberg Adam <[email protected]>
Sent: 08 February 2021 10:39
To: [email protected]
Subject: [Pulp-list] epel syncs all advisories every time


I sync the rhel8 and rhel7 epel repo every day, and for some reason all 
advisories are removed and added each time:


    "content_summary": {
        "added": {
            "rpm.advisory": {
                "count": 2540,
                "href": 
"/pulp/api/v3/content/rpm/advisories/?repository_version_added=/pulp/api/v3/repositories/rpm/rpm/10e51ae6-65c7-42aa-8ab1-ffebdf752500/versions/19/"
            },
            "rpm.package": {
                "count": 6,
                "href": 
"/pulp/api/v3/content/rpm/packages/?repository_version_added=/pulp/api/v3/repositories/rpm/rpm/10e51ae6-65c7-42aa-8ab1-ffebdf752500/versions/19/"
            }
        },
        "removed": {
            "rpm.advisory": {
                "count": 2536,
                "href": 
"/pulp/api/v3/content/rpm/advisories/?repository_version_removed=/pulp/api/v3/repositories/rpm/rpm/10e51ae6-65c7-42aa-8ab1-ffebdf752500/versions/19/"
            }
        }
    },


This also leads to problem when I want to copy new advisories to my frozen epel 
repo:
pulp_rpm.app.exceptions.AdvisoryConflict: Incoming and existing advisories have 
the same id and timestamp but different and intersecting package lists. At 
least one of them is wrong. Advisory id: FEDORA-EPEL-2019-927a9446df

So it seems that the advisory has actually changed, which seems weird. And 
changed every day? Is this some quirk in the EPEL sources or a bug in Pulp?

//Adam




_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to