On Wed, 4 May 2022 at 08:55, Miro Hrončok <mhron...@redhat.com> wrote:

> Hello EPEL.
>
> I have just found out that the pybind11 component from c9s / RHEL 9 CRB
> has
> been built in EPEL 9 in different version:
>
>
> ....


> Do I understand correctly that this is still *not* allowed? If so, what
> can we
> do to prevent it?
>
>
It shouldn't happen, but it doesn't mean it can't happen. It needs to be
fixed but that needs people to have the time and energy to do it over all
the other sh*t-sandwiches they are trying to clean off their plates.

The most common reasons this happens are in the order I have seen them
1. The package was originally put into EPEL because it was for only arches
that aren't shipped in RHEL. It should have remained at the same level as
the ones in RHEL but didn't.
2. The package was put into EPEL before it was put into a channel in RHEL.
This happens a LOT with the Stream method of moving things during the beta
period. Stuff have gone from BuildRoot-only to CRB to AppStream multiple
times.
3. There are timing bugs and general bugs in PDC and other tools which are
meant to help stop this. PDC is dead-ware with no upstream so fixing it is
fun. The other scripts depend on learning what is in Stream and are
fallible. It would take someone running the scripts that releng has to see
why in this case it didn't stop the action.
4. Human mistake somehow allowing this to happen over other things.

1 might be possibly fixed if the compose system knew to lock certain
packages with certain versions. So if pybind11 was meant to be only for
stuff not shipped in s390x/ppc64 then if the version was pushed beyond what
was know the 'compose' would not allow it. [This is a freeform idea and
probably broken in a million ways]
2/3/4 might be possibly fixed with a 'releng toddler' which does what you
did every day and screams if it finds that these conflicts happen on any
arch. Then a report can be made of which arch the conflict happens and what
could be done to fix it. [Again freeform idea and probably broken.]





> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to