EPEL 8: %__python3 == /usr/bin/python3 creates runtime problems with alternatives

[Miro Hrončok]

Hello EPEL folks,

In EL 8, it is possible to change the "meaning" of /usr/bin/python3 because it 
is managed by alternatives:

$ ls -l /usr/bin/python3
   lrwxrwxrwx. ... /usr/bin/python3 -> /etc/alternatives/python3

And since %__python3 on EPEL 8 is set to /usr/bin/python3 by epel-rpm-macros:

$ rpm --eval '%__python3'
   /usr/bin/python3

When packages have %py3_shebang_fix on EPEL 8:

%py3_shebang_fix %{buildroot}%{_bindir}/*

The shebengs have #!/usr/bin/python3 in them.

(This is done by %__brp_mangle_shebangs automatically, so even packages without 
%py3_shebang_fix might be affected.)

But when the package has importable modules in %{python3_sitelib} or 
%{python3_sitearch} or simply depends on other Python 3.6 modules, and the user 
uses alternatives to change /usr/bin/python3 to e.g. python3.9, the script no 
longer works.

I suppose the default value of %__python3 needs to be /usr/bin/python3.6 to 
prevent this way of shooting the users to their legs.

(I apologize for letting the alternatives happen, but that ship has sailed a 
long time ago. Fortunately, EL 9 no longer have this.)

[Troy Dawson]

On Tue, Nov 8, 2022 at 5:06 AM Miro Hrončok  wrote:
> Hello EPEL folks,
>
> In EL 8, it is possible to change the "meaning" of /usr/bin/python3
> because it
> is managed by alternatives:
>
> $ ls -l /usr/bin/python3
>    lrwxrwxrwx. ... /usr/bin/python3 -> /etc/alternatives/python3
>
> And since %__python3 on EPEL 8 is set to /usr/bin/python3 by
> epel-rpm-macros:
>
> $ rpm --eval '%__python3'
>    /usr/bin/python3
>
> When packages have %py3_shebang_fix on EPEL 8:
>
> %py3_shebang_fix %{buildroot}%{_bindir}/*
>
> The shebengs have #!/usr/bin/python3 in them.
>
> (This is done by %__brp_mangle_shebangs automatically, so even packages
> without
> %py3_shebang_fix might be affected.)
>
> But when the package has importable modules in %{python3_sitelib} or
> %{python3_sitearch} or simply depends on other Python 3.6 modules, and the
> user
> uses alternatives to change /usr/bin/python3 to e.g. python3.9, the script
> no
> longer works.
>
> I suppose the default value of %__python3 needs to be /usr/bin/python3.6
> to
> prevent this way of shooting the users to their legs.
>
> (I apologize for letting the alternatives happen, but that ship has sailed
> a
> long time ago. Fortunately, EL 9 no longer have this.)
>
> --
> Miro Hrončok
> --

Hi Miro,
You have explained the problem very well, and a possible solution.
But I'm a bit confused as to what you want to happen.

Is this a heads up, that you are going to change something?
Do you want us to discuss what is the best thing to do?
Are you letting us know about the problem, and want someone else to
implement a solution?

Troy Dawson

[Miro Hrončok]

On 08. 11. 22 22:36, Troy Dawson wrote:
> Hi Miro,
> You have explained the problem very well, and a possible solution.
> But I'm a bit confused as to what you want to happen.
>
> Is this a heads up, that you are going to change something?
> Do you want us to discuss what is the best thing to do?

Yes, that was my intention.
> Are you letting us know about the problem, and want someone else to implement a 
> solution?

I was prepared to implement it myself, but Maxwell is already looking into it.

https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54

[Miro Hrončok]

On 09. 11. 22 20:07, Miro Hrončok wrote:
> On 08. 11. 22 22:36, Troy Dawson wrote:
> > Hi Miro,
> > You have explained the problem very well, and a possible solution.
> > But I'm a bit confused as to what you want to happen.
> >
> > Is this a heads up, that you are going to change something?
> > Do you want us to discuss what is the best thing to do?
>
> Yes, that was my intention.
> > Are you letting us know about the problem, and want someone else to implement 
> > a solution?
>
> I was prepared to implement it myself, but Maxwell is already looking into it.
>
> https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54

As a followup, when we merge this, we might neeed to rebuild some affected 
packages.

A naïve query that returns everything that uses /usr/bin/python3 shebang but 
probably wants /usr/bin/python3.6:

$ comm -12 <(repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | sort) 
<(repoquery -q --repo=epel8 --whatrequires 'python3.6dist(*)' --whatrequires 
'python(abi) = 3.6' | sort)
apprise-0:1.0.0-1.el8.noarch
argparse-manpage-0:4-1.el8.noarch
cekit-0:4.4.0-1.el8.noarch
copr-cli-0:1.103-1.el8.noarch
csmock-common-0:3.3.4-1.el8.noarch
csmock-plugin-gitleaks-0:3.3.4-1.el8.noarch
csmock-plugin-infer-0:3.3.4-1.el8.noarch
csmock-plugin-unicontrol-0:3.3.4-1.el8.noarch
distgen-0:1.14-1.el8.noarch
dmlite-shell-0:1.15.2-11.el8.x86_64
drgn-0:0.0.21-1.el8.x86_64
fedpkg-0:1.43-2.el8.noarch
fts-rest-client-0:3.12.0-1.el8.noarch
glances-0:3.3.0.1-1.el8.noarch
kf5-kapidox-0:5.96.0-1.el8.noarch
lightdm-gtk-greeter-settings-0:1.2.2-18.el8.noarch
meld-0:3.20.4-1.el8.noarch
mozo-0:1.26.2-1.el8.noarch
nordugrid-arc-arcctl-0:6.16.1-1.el8.x86_64
nordugrid-arc-arex-0:6.16.1-1.el8.x86_64
nordugrid-arc-0:6.16.1-1.el8.x86_64
podman-compose-0:1.0.3-3.el8.noarch
pypolicyd-spf-0:2.9.3-1.el8.noarch
PyQt-builder-0:1.13.0-2.el8.noarch
python3-bloom-0:0.11.2-1.el8.noarch
python3-breathe-0:4.11.1-1.el8.noarch
python3-django3-0:3.2.15-3.el8.noarch
python3-dotenv-0:0.19.2-4.el8.noarch
python3-impacket-0:0.10.0-1.el8.noarch
python3-ipython-0:7.16.3-1.el8.noarch
python3-junitxml-0:0.7-28.el8.noarch
python3-kaptan-0:0.5.12-15.el8.noarch
python3-kiwi-0:9.24.48-2.el8.noarch
python3-subunit-test-0:1.4.0-13.el8.noarch
python3-subunit-0:1.4.0-13.el8.noarch
python3-tabulate-0:0.8.10-1.el8.noarch
python3-testrepository-0:0.0.20-29.el8.noarch
python3-vcstool-0:0.3.0-1.el8.noarch
python3-virt-firmware-0:1.5-1.el8.noarch
python3-websockify-0:0.10.0-3.el8.noarch
rednotebook-0:2.26-1.el8.noarch
resalloc-openstack-0:9.3-1.el8.noarch
resalloc-server-0:4.8-1.el8.noarch
resalloc-webui-0:4.8-1.el8.noarch
retrace-server-0:1.24.2-1.el8.noarch
suricata-0:5.0.10-1.el8.x86_64
s3cmd-0:2.3.0-1.el8.noarch
tito-0:0.6.21-1.el8.noarch
yamllint-0:1.28.0-1.el8.noarch

But obviously, anything in this list *might* be affected:

$ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | wc -l
92
$ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | sort | 
uniq | wc -l
73

And I am not even querying EPEL 8 Next.

[Miro Hrončok]

On 21. 11. 22 12:56, Miro Hrončok wrote:
> On 09. 11. 22 20:07, Miro Hrončok wrote:
> > On 08. 11. 22 22:36, Troy Dawson wrote:
> > > Hi Miro,
> > > You have explained the problem very well, and a possible solution.
> > > But I'm a bit confused as to what you want to happen.
> > >
> > > Is this a heads up, that you are going to change something?
> > > Do you want us to discuss what is the best thing to do?
> >
> > Yes, that was my intention.
> > > Are you letting us know about the problem, and want someone else to 
> > > implement a solution?
> >
> > I was prepared to implement it myself, but Maxwell is already looking into it.
> >
> > https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54
>
> As a followup, when we merge this, we might neeed to rebuild some affected 
> packages.
>
> A naïve query that returns everything that uses /usr/bin/python3 shebang but 
> probably wants /usr/bin/python3.6:
>
> $ comm -12 <(repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | sort) 
> <(repoquery -q --repo=epel8 --whatrequires 'python3.6dist(*)' --whatrequires 
> 'python(abi) = 3.6' | sort)
> apprise-0:1.0.0-1.el8.noarch
> argparse-manpage-0:4-1.el8.noarch
> cekit-0:4.4.0-1.el8.noarch
> copr-cli-0:1.103-1.el8.noarch
> csmock-common-0:3.3.4-1.el8.noarch
> csmock-plugin-gitleaks-0:3.3.4-1.el8.noarch
> csmock-plugin-infer-0:3.3.4-1.el8.noarch
> csmock-plugin-unicontrol-0:3.3.4-1.el8.noarch
> distgen-0:1.14-1.el8.noarch
> dmlite-shell-0:1.15.2-11.el8.x86_64
> drgn-0:0.0.21-1.el8.x86_64
> fedpkg-0:1.43-2.el8.noarch
> fts-rest-client-0:3.12.0-1.el8.noarch
> glances-0:3.3.0.1-1.el8.noarch
> kf5-kapidox-0:5.96.0-1.el8.noarch
> lightdm-gtk-greeter-settings-0:1.2.2-18.el8.noarch
> meld-0:3.20.4-1.el8.noarch
> mozo-0:1.26.2-1.el8.noarch
> nordugrid-arc-arcctl-0:6.16.1-1.el8.x86_64
> nordugrid-arc-arex-0:6.16.1-1.el8.x86_64
> nordugrid-arc-0:6.16.1-1.el8.x86_64
> podman-compose-0:1.0.3-3.el8.noarch
> pypolicyd-spf-0:2.9.3-1.el8.noarch
> PyQt-builder-0:1.13.0-2.el8.noarch
> python3-bloom-0:0.11.2-1.el8.noarch
> python3-breathe-0:4.11.1-1.el8.noarch
> python3-django3-0:3.2.15-3.el8.noarch
> python3-dotenv-0:0.19.2-4.el8.noarch
> python3-impacket-0:0.10.0-1.el8.noarch
> python3-ipython-0:7.16.3-1.el8.noarch
> python3-junitxml-0:0.7-28.el8.noarch
> python3-kaptan-0:0.5.12-15.el8.noarch
> python3-kiwi-0:9.24.48-2.el8.noarch
> python3-subunit-test-0:1.4.0-13.el8.noarch
> python3-subunit-0:1.4.0-13.el8.noarch
> python3-tabulate-0:0.8.10-1.el8.noarch
> python3-testrepository-0:0.0.20-29.el8.noarch
> python3-vcstool-0:0.3.0-1.el8.noarch
> python3-virt-firmware-0:1.5-1.el8.noarch
> python3-websockify-0:0.10.0-3.el8.noarch
> rednotebook-0:2.26-1.el8.noarch
> resalloc-openstack-0:9.3-1.el8.noarch
> resalloc-server-0:4.8-1.el8.noarch
> resalloc-webui-0:4.8-1.el8.noarch
> retrace-server-0:1.24.2-1.el8.noarch
> suricata-0:5.0.10-1.el8.x86_64
> s3cmd-0:2.3.0-1.el8.noarch
> tito-0:0.6.21-1.el8.noarch
> yamllint-0:1.28.0-1.el8.noarch
>
> But obviously, anything in this list *might* be affected:
>
> $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | wc -l
> 92
> $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | sort | 
> uniq | wc -l
> 73

I am building all the packages in 
https://copr.fedorainfracloud.org/coprs/churchyard/epel8-python3.6-shebang-r... 
to see if the shebang changes.

When it does change I plan to rebuild the package in EPEL 8.
> And I am not even querying EPEL 8 Next.

There seem to be 13 packages in EPEL Next and none of them requires 
/usr/bin/python3.

[Miro Hrončok]

On 11. 12. 22 15:48, Miro Hrončok wrote:
> On 21. 11. 22 12:56, Miro Hrončok wrote:
> > On 09. 11. 22 20:07, Miro Hrončok wrote:
> > > On 08. 11. 22 22:36, Troy Dawson wrote:
> > > > Hi Miro,
> > > > You have explained the problem very well, and a possible solution.
> > > > But I'm a bit confused as to what you want to happen.
> > > >
> > > > Is this a heads up, that you are going to change something?
> > > > Do you want us to discuss what is the best thing to do?
> > >
> > > Yes, that was my intention.
> > > > Are you letting us know about the problem, and want someone else to 
> > > > implement a solution?
> > >
> > > I was prepared to implement it myself, but Maxwell is already looking into it.
> > >
> > > https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54
> >
> > As a followup, when we merge this, we might neeed to rebuild some affected 
> > packages.
> >
> > A naïve query that returns everything that uses /usr/bin/python3 shebang but 
> > probably wants /usr/bin/python3.6:
> >
> > $ comm -12 <(repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | 
> > sort) <(repoquery -q --repo=epel8 --whatrequires 'python3.6dist(*)' 
> > --whatrequires 'python(abi) = 3.6' | sort)
> > apprise-0:1.0.0-1.el8.noarch
> > argparse-manpage-0:4-1.el8.noarch
> > cekit-0:4.4.0-1.el8.noarch
> > copr-cli-0:1.103-1.el8.noarch
> > csmock-common-0:3.3.4-1.el8.noarch
> > csmock-plugin-gitleaks-0:3.3.4-1.el8.noarch
> > csmock-plugin-infer-0:3.3.4-1.el8.noarch
> > csmock-plugin-unicontrol-0:3.3.4-1.el8.noarch
> > distgen-0:1.14-1.el8.noarch
> > dmlite-shell-0:1.15.2-11.el8.x86_64
> > drgn-0:0.0.21-1.el8.x86_64
> > fedpkg-0:1.43-2.el8.noarch
> > fts-rest-client-0:3.12.0-1.el8.noarch
> > glances-0:3.3.0.1-1.el8.noarch
> > kf5-kapidox-0:5.96.0-1.el8.noarch
> > lightdm-gtk-greeter-settings-0:1.2.2-18.el8.noarch
> > meld-0:3.20.4-1.el8.noarch
> > mozo-0:1.26.2-1.el8.noarch
> > nordugrid-arc-arcctl-0:6.16.1-1.el8.x86_64
> > nordugrid-arc-arex-0:6.16.1-1.el8.x86_64
> > nordugrid-arc-0:6.16.1-1.el8.x86_64
> > podman-compose-0:1.0.3-3.el8.noarch
> > pypolicyd-spf-0:2.9.3-1.el8.noarch
> > PyQt-builder-0:1.13.0-2.el8.noarch
> > python3-bloom-0:0.11.2-1.el8.noarch
> > python3-breathe-0:4.11.1-1.el8.noarch
> > python3-django3-0:3.2.15-3.el8.noarch
> > python3-dotenv-0:0.19.2-4.el8.noarch
> > python3-impacket-0:0.10.0-1.el8.noarch
> > python3-ipython-0:7.16.3-1.el8.noarch
> > python3-junitxml-0:0.7-28.el8.noarch
> > python3-kaptan-0:0.5.12-15.el8.noarch
> > python3-kiwi-0:9.24.48-2.el8.noarch
> > python3-subunit-test-0:1.4.0-13.el8.noarch
> > python3-subunit-0:1.4.0-13.el8.noarch
> > python3-tabulate-0:0.8.10-1.el8.noarch
> > python3-testrepository-0:0.0.20-29.el8.noarch
> > python3-vcstool-0:0.3.0-1.el8.noarch
> > python3-virt-firmware-0:1.5-1.el8.noarch
> > python3-websockify-0:0.10.0-3.el8.noarch
> > rednotebook-0:2.26-1.el8.noarch
> > resalloc-openstack-0:9.3-1.el8.noarch
> > resalloc-server-0:4.8-1.el8.noarch
> > resalloc-webui-0:4.8-1.el8.noarch
> > retrace-server-0:1.24.2-1.el8.noarch
> > suricata-0:5.0.10-1.el8.x86_64
> > s3cmd-0:2.3.0-1.el8.noarch
> > tito-0:0.6.21-1.el8.noarch
> > yamllint-0:1.28.0-1.el8.noarch
> >
> > But obviously, anything in this list *might* be affected:
> >
> > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | wc -l
> > 92
> > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | sort | 
> > uniq | wc -l
> > 73
>
> I am building all the packages in 
> https://copr.fedorainfracloud.org/coprs/churchyard/epel8-python3.6-shebang-r... to see if the shebang changes.

Something else came up, than the holidays and suddenly that repo is expired 
because I have created it as temporary :D

Will start over.
> When it does change I plan to rebuild the package in EPEL 8.
> > And I am not even querying EPEL 8 Next.
>
> There seem to be 13 packages in EPEL Next and none of them requires 
> /usr/bin/python3.

[Miro Hrončok]

On 30. 01. 23 20:13, Miro Hrončok wrote:
> On 11. 12. 22 15:48, Miro Hrončok wrote:
> > On 21. 11. 22 12:56, Miro Hrončok wrote:
> > > On 09. 11. 22 20:07, Miro Hrončok wrote:
> > > > On 08. 11. 22 22:36, Troy Dawson wrote:
> > > > > Hi Miro,
> > > > > You have explained the problem very well, and a possible solution.
> > > > > But I'm a bit confused as to what you want to happen.
> > > > >
> > > > > Is this a heads up, that you are going to change something?
> > > > > Do you want us to discuss what is the best thing to do?
> > > >
> > > > Yes, that was my intention.
> > > > > Are you letting us know about the problem, and want someone else to 
> > > > > implement a solution?
> > > >
> > > > I was prepared to implement it myself, but Maxwell is already looking into it.
> > > >
> > > > https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54
> > >
> > > As a followup, when we merge this, we might neeed to rebuild some affected 
> > > packages.
> > >
> > > A naïve query that returns everything that uses /usr/bin/python3 shebang but 
> > > probably wants /usr/bin/python3.6:
> > >
> > > $ comm -12 <(repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | 
> > > sort) <(repoquery -q --repo=epel8 --whatrequires 'python3.6dist(*)' 
> > > --whatrequires 'python(abi) = 3.6' | sort)
> > > apprise-0:1.0.0-1.el8.noarch
> > > argparse-manpage-0:4-1.el8.noarch
> > > cekit-0:4.4.0-1.el8.noarch
> > > copr-cli-0:1.103-1.el8.noarch
> > > csmock-common-0:3.3.4-1.el8.noarch
> > > csmock-plugin-gitleaks-0:3.3.4-1.el8.noarch
> > > csmock-plugin-infer-0:3.3.4-1.el8.noarch
> > > csmock-plugin-unicontrol-0:3.3.4-1.el8.noarch
> > > distgen-0:1.14-1.el8.noarch
> > > dmlite-shell-0:1.15.2-11.el8.x86_64
> > > drgn-0:0.0.21-1.el8.x86_64
> > > fedpkg-0:1.43-2.el8.noarch
> > > fts-rest-client-0:3.12.0-1.el8.noarch
> > > glances-0:3.3.0.1-1.el8.noarch
> > > kf5-kapidox-0:5.96.0-1.el8.noarch
> > > lightdm-gtk-greeter-settings-0:1.2.2-18.el8.noarch
> > > meld-0:3.20.4-1.el8.noarch
> > > mozo-0:1.26.2-1.el8.noarch
> > > nordugrid-arc-arcctl-0:6.16.1-1.el8.x86_64
> > > nordugrid-arc-arex-0:6.16.1-1.el8.x86_64
> > > nordugrid-arc-0:6.16.1-1.el8.x86_64
> > > podman-compose-0:1.0.3-3.el8.noarch
> > > pypolicyd-spf-0:2.9.3-1.el8.noarch
> > > PyQt-builder-0:1.13.0-2.el8.noarch
> > > python3-bloom-0:0.11.2-1.el8.noarch
> > > python3-breathe-0:4.11.1-1.el8.noarch
> > > python3-django3-0:3.2.15-3.el8.noarch
> > > python3-dotenv-0:0.19.2-4.el8.noarch
> > > python3-impacket-0:0.10.0-1.el8.noarch
> > > python3-ipython-0:7.16.3-1.el8.noarch
> > > python3-junitxml-0:0.7-28.el8.noarch
> > > python3-kaptan-0:0.5.12-15.el8.noarch
> > > python3-kiwi-0:9.24.48-2.el8.noarch
> > > python3-subunit-test-0:1.4.0-13.el8.noarch
> > > python3-subunit-0:1.4.0-13.el8.noarch
> > > python3-tabulate-0:0.8.10-1.el8.noarch
> > > python3-testrepository-0:0.0.20-29.el8.noarch
> > > python3-vcstool-0:0.3.0-1.el8.noarch
> > > python3-virt-firmware-0:1.5-1.el8.noarch
> > > python3-websockify-0:0.10.0-3.el8.noarch
> > > rednotebook-0:2.26-1.el8.noarch
> > > resalloc-openstack-0:9.3-1.el8.noarch
> > > resalloc-server-0:4.8-1.el8.noarch
> > > resalloc-webui-0:4.8-1.el8.noarch
> > > retrace-server-0:1.24.2-1.el8.noarch
> > > suricata-0:5.0.10-1.el8.x86_64
> > > s3cmd-0:2.3.0-1.el8.noarch
> > > tito-0:0.6.21-1.el8.noarch
> > > yamllint-0:1.28.0-1.el8.noarch
> > >
> > > But obviously, anything in this list *might* be affected:
> > >
> > > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | wc -l
> > > 92
> > > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | sort 
> > > | uniq | wc -l
> > > 73
> >
> > I am building all the packages in 
> > https://copr.fedorainfracloud.org/coprs/churchyard/epel8-python3.6-shebang-r... to see if the shebang changes.
>
> Something else came up, than the holidays and suddenly that repo is expired 
> because I have created it as temporary :D
>
> Will start over.
> > When it does change I plan to rebuild the package in EPEL 8.

The following packages FTBFS:

kwin

The following packages still build after an hour and I need to remember to 
check them later:

qt-creator
root

The rest needs a rebuild:

ansible-collection-community-general
ansible-packaging
argparse-manpage
asterisk
cepces
clifm
cockpit-file-sharing
distgen
fedpkg
fmf
fts-rest-client
git-tools
ipython
kcachegrind
kde-dev-scripts
kf5-kapidox
konversation
lightdm-gtk-greeter-settings
meld
mozo
netplan
packit
plasma-desktop
pluma
podman-compose
pypolicyd-spf
PyQt-builder
python-bloom
python-breathe
python-colcon-core
python-django3
python-dotenv
python-impacket
python-junitxml
python-kaptan
python-tabulate
python-testrepository
python-vcstool
python-websockify
resalloc
retrace-server
rlwrap
rpmconf
sasutils
subunit
s3cmd
tacacs
tito
vcs-diff-lint
zchunk

I don't want to disrupt any "the rawhide and epel8 branch must be in sync" 
workflows, so I'll probably send PRs.

[Miro Hrončok]

On 30. 01. 23 21:39, Miro Hrončok wrote:
> > > When it does change I plan to rebuild the package in EPEL 8.
>
> The following packages FTBFS:
>
> kwin

It failed because it has an %if-%rhel-defined Patch :(

Trying again from a patched spec.
> The following packages still build after an hour and I need to remember to 
> check them later:
>
> qt-creator

Built, needs a rebuild as well.
> root

Still in progress.

[Miro Hrončok]

On 30. 01. 23 22:29, Miro Hrončok wrote:
> On 30. 01. 23 21:39, Miro Hrončok wrote:
> > > > When it does change I plan to rebuild the package in EPEL 8.
> >
> > The following packages FTBFS:
> >
> > kwin
>
> It failed because it has an %if-%rhel-defined Patch :(
>
> Trying again from a patched spec.

Done. Also needs a rebuild.
> > The following packages still build after an hour and I need to remember to 
> > check them later:
> >
> > qt-creator
>
> Built, needs a rebuild as well.
> > root
>
> Still in progress.

Done. Also needs a rebuild.

All the packages needed a rebuild. All PRs open (and some fo them already merged).

A handful of packages uses rpmautospec and Pagure does not allow me to send an 
empty PR. I've emailed the maintainers.

[Miro Hrončok]

On 30. 01. 23 21:39, Miro Hrončok wrote:
> On 30. 01. 23 20:13, Miro Hrončok wrote:
> > On 11. 12. 22 15:48, Miro Hrončok wrote:
> > > On 21. 11. 22 12:56, Miro Hrončok wrote:
> > > > On 09. 11. 22 20:07, Miro Hrončok wrote:
> > > > > On 08. 11. 22 22:36, Troy Dawson wrote:
> > > > > > Hi Miro,
> > > > > > You have explained the problem very well, and a possible solution.
> > > > > > But I'm a bit confused as to what you want to happen.
> > > > > >
> > > > > > Is this a heads up, that you are going to change something?
> > > > > > Do you want us to discuss what is the best thing to do?
> > > > >
> > > > > Yes, that was my intention.
> > > > > > Are you letting us know about the problem, and want someone else to 
> > > > > > implement a solution?
> > > > >
> > > > > I was prepared to implement it myself, but Maxwell is already looking into 
> > > > > it.
> > > > >
> > > > > https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/54
> > > >
> > > > As a followup, when we merge this, we might neeed to rebuild some affected 
> > > > packages.
> > > >
> > > > A naïve query that returns everything that uses /usr/bin/python3 shebang 
> > > > but probably wants /usr/bin/python3.6:
> > > >
> > > > $ comm -12 <(repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | 
> > > > sort) <(repoquery -q --repo=epel8 --whatrequires 'python3.6dist(*)' 
> > > > --whatrequires 'python(abi) = 3.6' | sort)
> > > > apprise-0:1.0.0-1.el8.noarch
> > > > argparse-manpage-0:4-1.el8.noarch
> > > > cekit-0:4.4.0-1.el8.noarch
> > > > copr-cli-0:1.103-1.el8.noarch
> > > > csmock-common-0:3.3.4-1.el8.noarch
> > > > csmock-plugin-gitleaks-0:3.3.4-1.el8.noarch
> > > > csmock-plugin-infer-0:3.3.4-1.el8.noarch
> > > > csmock-plugin-unicontrol-0:3.3.4-1.el8.noarch
> > > > distgen-0:1.14-1.el8.noarch
> > > > dmlite-shell-0:1.15.2-11.el8.x86_64
> > > > drgn-0:0.0.21-1.el8.x86_64
> > > > fedpkg-0:1.43-2.el8.noarch
> > > > fts-rest-client-0:3.12.0-1.el8.noarch
> > > > glances-0:3.3.0.1-1.el8.noarch
> > > > kf5-kapidox-0:5.96.0-1.el8.noarch
> > > > lightdm-gtk-greeter-settings-0:1.2.2-18.el8.noarch
> > > > meld-0:3.20.4-1.el8.noarch
> > > > mozo-0:1.26.2-1.el8.noarch
> > > > nordugrid-arc-arcctl-0:6.16.1-1.el8.x86_64
> > > > nordugrid-arc-arex-0:6.16.1-1.el8.x86_64
> > > > nordugrid-arc-0:6.16.1-1.el8.x86_64
> > > > podman-compose-0:1.0.3-3.el8.noarch
> > > > pypolicyd-spf-0:2.9.3-1.el8.noarch
> > > > PyQt-builder-0:1.13.0-2.el8.noarch
> > > > python3-bloom-0:0.11.2-1.el8.noarch
> > > > python3-breathe-0:4.11.1-1.el8.noarch
> > > > python3-django3-0:3.2.15-3.el8.noarch
> > > > python3-dotenv-0:0.19.2-4.el8.noarch
> > > > python3-impacket-0:0.10.0-1.el8.noarch
> > > > python3-ipython-0:7.16.3-1.el8.noarch
> > > > python3-junitxml-0:0.7-28.el8.noarch
> > > > python3-kaptan-0:0.5.12-15.el8.noarch
> > > > python3-kiwi-0:9.24.48-2.el8.noarch
> > > > python3-subunit-test-0:1.4.0-13.el8.noarch
> > > > python3-subunit-0:1.4.0-13.el8.noarch
> > > > python3-tabulate-0:0.8.10-1.el8.noarch
> > > > python3-testrepository-0:0.0.20-29.el8.noarch
> > > > python3-vcstool-0:0.3.0-1.el8.noarch
> > > > python3-virt-firmware-0:1.5-1.el8.noarch
> > > > python3-websockify-0:0.10.0-3.el8.noarch
> > > > rednotebook-0:2.26-1.el8.noarch
> > > > resalloc-openstack-0:9.3-1.el8.noarch
> > > > resalloc-server-0:4.8-1.el8.noarch
> > > > resalloc-webui-0:4.8-1.el8.noarch
> > > > retrace-server-0:1.24.2-1.el8.noarch
> > > > suricata-0:5.0.10-1.el8.x86_64
> > > > s3cmd-0:2.3.0-1.el8.noarch
> > > > tito-0:0.6.21-1.el8.noarch
> > > > yamllint-0:1.28.0-1.el8.noarch
> > > >
> > > > But obviously, anything in this list *might* be affected:
> > > >
> > > > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 | wc -l
> > > > 92
> > > > $ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | sort 
> > > > | uniq | wc -l
> > > > 73
> > >
> > > I am building all the packages in 
> > > https://copr.fedorainfracloud.org/coprs/churchyard/epel8-python3.6-shebang-r... to see if the shebang changes.
> >
> > Something else came up, than the holidays and suddenly that repo is expired 
> > because I have created it as temporary :D
> >
> > Will start over.
> > > When it does change I plan to rebuild the package in EPEL 8.
>
> The following packages FTBFS:
>
> kwin
>
> The following packages still build after an hour and I need to remember to 
> check them later:
>
> qt-creator
> root
>
> The rest needs a rebuild:
>
> ansible-collection-community-general
> ansible-packaging
> argparse-manpage
> asterisk
> cepces
> clifm
> cockpit-file-sharing
> distgen
> fedpkg
> fmf
> fts-rest-client
> git-tools
> ipython
> kcachegrind
> kde-dev-scripts
> kf5-kapidox
> konversation
> lightdm-gtk-greeter-settings
> meld
> mozo
> netplan
> packit
> plasma-desktop
> pluma
> podman-compose
> pypolicyd-spf
> PyQt-builder
> python-bloom
> python-breathe
> python-colcon-core
> python-django3
> python-dotenv
> python-impacket
> python-junitxml
> python-kaptan
> python-tabulate
> python-testrepository
> python-vcstool
> python-websockify
> resalloc
> retrace-server
> rlwrap
> rpmconf
> sasutils
> subunit
> s3cmd
> tacacs
> tito
> vcs-diff-lint
> zchunk
>
> I don't want to disrupt any "the rawhide and epel8 branch must be in sync" 
> workflows, so I'll probably send PRs.

I merged the PRs without response, built the packages and submitted the Bodhi 
updates. They gone stable by now. This has been "done" from my part.

Leftovers are on track:

$ repoquery -q --repo=epel8 --whatrequires /usr/bin/python3 --source | pkgname

ansible-collection-community-general
https://src.fedoraproject.org/rpms/ansible-collection-community-general/pull...

mozo
my PR was merged but not built, submitted the update myself
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5dd853f8d9

pluma
my PR was merged but not built, submitted the update myself
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-9ad2aefde7

python-breathe
my PR was merged but not built, submitted the update myself
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-fa62ba56a1

sasutils
a new update obsoleted mine
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c24c6f50bf

zchunk
a new update obsoleted mine
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1ca44ec69f