[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-05 Thread Troy Dawson
On Wed, May 4, 2022 at 1:00 PM Miro Hrončok  wrote:

> On 04. 05. 22 15:40, Troy Dawson wrote:
> > I just want to make sure that you are querying RHEL 9.0 and not 9.1.
>
> Well, I was querying 9.1, so you have a point. However, with 9.0 it is
> almost
> the same:
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability} -a | pkgname | sort
> |
> uniq ) <(repoquery -q --repo=epel9 -a | pkgname | sort | uniq)
>
> libwmf
> libwmf-lite
> pybind11-devel
> python3-pybind11
> tesseract
> tesseract-devel
> tesseract-langpack-eng
> tesseract-tessdata-doc
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability}-source -a | pkgname
> |
> sort | uniq ) <(repoquery -q --repo=epel9-source -a | pkgname | sort |
> uniq)
>
> libwmf
> pybind11
> tesseract
> tesseract-tessdata
>
>
> The only difference I can spot is anthy-unicode-devel and
> double-conversion-devel, which apparently might be allowed in EPEL 9 for
> now.
>

There is now a new function added to the "Will-It" family.
"Will-It-Duplicate"
I figured I already had 80% of what was needed already written, so why not.
There are indeed duplicates of upstream in both epel9 and epel8.

https://tdawson.fedorapeople.org/epel/willit/epel9/status-duplicates.html
https://tdawson.fedorapeople.org/epel/willit/epel8/status-duplicates.html

It also does epel7, but right now there seems to be a bug in that.

So, now we can easily see the duplicate packages to remove them.
And, we'll get them removed.  Removing is much easier than adding.

We are still investigating how this happened for pybind11, tesseract and
tesseract-tessdata.  Those shouldn't have been able to be branched.

For libwmf it seems it was a race condition.
The new RHEL workflow checks epel9 to see if a package is already there.
At the time work started on libwmf, it wasn't in epel9, so it didn't create
a bug.
Then libwmf was branched in epel9, because libwmf wasn't in CentOS Stream 9
yet.
They both came out within a couple weeks of each other.
The odds of that happening again are pretty slim, and the effort to fix
that sort of race condition is pretty high.
So we'll just let Will-It-Duplicate find those race condition problems.

Troy
___
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


[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-05 Thread Miro Hrončok

On 04. 05. 22 22:03, Josh Boyer wrote:

The only difference I can spot is anthy-unicode-devel and
double-conversion-devel, which apparently might be allowed in EPEL 9 for now.

Both of those were requested and added in the last month
(anthy-unicode-devel just this week).  That should be reflected in
CentOS Stream 9 now(ish) and a future version of RHEL 9 at some point.


That is how I udnerstood this.

The rest of the packages however appear to be both in EPEL 9 and in RHEL 9.0.

--
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


[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-04 Thread Josh Boyer
On Wed, May 4, 2022 at 4:00 PM Miro Hrončok  wrote:
>
> On 04. 05. 22 15:40, Troy Dawson wrote:
> > I just want to make sure that you are querying RHEL 9.0 and not 9.1.
>
> Well, I was querying 9.1, so you have a point. However, with 9.0 it is almost
> the same:
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability} -a | pkgname | sort |
> uniq ) <(repoquery -q --repo=epel9 -a | pkgname | sort | uniq)
>
> libwmf
> libwmf-lite
> pybind11-devel
> python3-pybind11
> tesseract
> tesseract-devel
> tesseract-langpack-eng
> tesseract-tessdata-doc
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability}-source -a | pkgname |
> sort | uniq ) <(repoquery -q --repo=epel9-source -a | pkgname | sort | uniq)
>
> libwmf
> pybind11
> tesseract
> tesseract-tessdata
>
>
> The only difference I can spot is anthy-unicode-devel and
> double-conversion-devel, which apparently might be allowed in EPEL 9 for now.

Both of those were requested and added in the last month
(anthy-unicode-devel just this week).  That should be reflected in
CentOS Stream 9 now(ish) and a future version of RHEL 9 at some point.

josh
___
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


[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-04 Thread Miro Hrončok

On 04. 05. 22 15:40, Troy Dawson wrote:

I just want to make sure that you are querying RHEL 9.0 and not 9.1.


Well, I was querying 9.1, so you have a point. However, with 9.0 it is almost 
the same:


$ comm -12 <(repoquery -q 
--repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability} -a | pkgname | sort | 
uniq ) <(repoquery -q --repo=epel9 -a | pkgname | sort | uniq)


libwmf
libwmf-lite
pybind11-devel
python3-pybind11
tesseract
tesseract-devel
tesseract-langpack-eng
tesseract-tessdata-doc

$ comm -12 <(repoquery -q 
--repo=RHEL9.0-{BaseOS,AppStream,CRB,HighAvailability}-source -a | pkgname | 
sort | uniq ) <(repoquery -q --repo=epel9-source -a | pkgname | sort | uniq)


libwmf
pybind11
tesseract
tesseract-tessdata


The only difference I can spot is anthy-unicode-devel and 
double-conversion-devel, which apparently might be allowed in EPEL 9 for now.


--
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


[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-04 Thread Troy Dawson
Hi Miro,
Thank you for looking into this.
One thing to keep in mind is that what is in CentOS Stream 9 right now, is
going into RHEL 9.1, so some of this won't be in epel9 for another 6-7
months.
I've noticed that in your query's you do a RHEL9 query.  Where is that
coming from?
I just want to make sure that you are querying RHEL 9.0 and not 9.1.


On Wed, May 4, 2022 at 5:55 AM Miro Hrončok  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:
>


> I always assumed fedora-scm-requests admins would refuse such branch
> requests,
> but apparently not:
>
> https://pagure.io/releng/fedora-scm-requests/issue/42248
>

In theory, they do block RHEL requests.  And I've had a couple blocked, so
I know it works, or at least used to work.
We'll have to do some investigation.

>
>
> I've checked and we have more components that clash:
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9-{BaseOS,AppStream,CRB,HighAvailability}-source -a | pkgname |
> sort
> | uniq ) <(repoquery -q --repo=epel9-source -a | pkgname | sort | uniq)
>
> libwmf
> pybind11
> tesseract
> tesseract-tessdata
>
>
Thank you for this list, of source packages that are duplicates.
We'll have to look into how they got built.


>
> As well as "binary" RPMs:
>
> $ comm -12 <(repoquery -q
> --repo=RHEL9-{BaseOS,AppStream,CRB,HighAvailability}
> -a | pkgname | sort | uniq ) <(repoquery -q --repo=epel9 -a | pkgname |
> sort |
> uniq)
>
> anthy-unicode-devel
> double-conversion-devel
>

anthy-unicode-devel and double-conversion-devel are mine.
They were built from anthy-unicode-epel and double-conversion-epel

Those two devel packages are not available in the epel9 buildroot, or
weren't last time I checked.
I also have not had the bug closed from Red Hat, so I haven't checked in a
month or two.



> Do I understand correctly that this is still *not* allowed? If so, what
> can we
> do to prevent it?
>

It shouldn't be allowed, and it shouldn't have happened.  We'll have to
look into it.

Troy
___
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


[EPEL-devel] Re: RHEL 9 packages available in EPEL 9 (in different versions as well)

2022-05-04 Thread Stephen John Smoogen
On Wed, 4 May 2022 at 08:55, Miro Hrončok  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