python3-qt5-webkit for EPEL 8
by Orion Poplawski
The python-qt5 package in RHEL 8 does not ship the webkit package. I'm
assuming that this is unlikely to be changed since qt5-qtwebkit isn't in
RHEL but is in EPEL.
I think I'm close to producing a python-qt5-epel package here [1] that
produces python3-qt5-webkit and would love to hear from people more
familiar with the package if this seems like it's reasonable/workable.
I think we're depending on the fact that the RHEL python3-qt5-devel
package does ship the WebKit sip files and that these would match up
with what this package ships.
It also just seems like webengine isn't in there, or I'm missing what's
needed to build it. I also don't need it for my purposes.
[1] - https://copr.fedorainfracloud.org/coprs/orion/python-qt5-epel/
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
11 hours, 7 minutes
Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
by Maxwell G
On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote:
Hi all,
> Hi, Orion
> Thanks for raising this question.
Indeed!
> I wonder if it's possible to continue to update collections to the
> newest versions anyway. If someone wants to use the collection version
> provided in "big ansible", they would use ansible 6.3.0 with all
> included. If they want a newer collection, they can install a separate
> newest RPM.
I agree. I think we should update collections to the next major version
(if it exists) after each RHEL minor release and then keep them updated
with point releases in between. We update the ansible bundle to the next
major version that corresponds to RHEL's ansible-core version at each
RHEL minor release, so it makes to do the same with the standalone
collection packages. Collection versions that are EOL upstream won't be
tested with newer ansible-core versions.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/They
4 days, 6 hours
Fwd: Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
by Maxwell G
2023-01-31T14:05:11Z David Moreau-Simard <moi(a)dmsimard.com>:
Hi,
Answer in-line but I also want to extend an invititation to everyone here
to join #ansible-packaging on libera.chat (or #packaging:ansible.com on
Matrix) which is a low signal-to-noise ratio channel to talk about
Ansible packaging things such as this one :)
------- Original Message -------
On Tuesday, January 31st, 2023 at 8:01 AM, Sagi Shnaidman
<sshnaidm(a)redhat.com> wrote:
> Hi, Orion
> Thanks for raising this question.
>
> I use both ways - either ansible distro with all-inclusive, or ansible
> (distro or "core") with specific collection installed separately when I
> need a newer version of collection, for example. I wonder if it's
> possible to continue to update collections to the newest versions
> anyway. If someone wants to use the collection version provided in "big
> ansible", they would use ansible 6.3.0 with all included. If they want
> a newer collection, they can install a separate newest RPM.
>
> But not sure if dependencies can be a problem here, like which
> collection version depends on other collection versions (for example
> ansible.utils, which is part of multiple collection dependencies).
We took this use case into account when we refacoted the Fedora ansible
package to match the "post ansible 2.9 era", see:
* https://fedoraproject.org/wiki/Changes/Ansible5
*
https://src.fedoraproject.org/rpms/ansible/blob/rawhide/f/ansible.spec#_207
TL;DR:
* The ansible package installs collections to the python site-lib
* The ansible collections packages should (generally?) install to
/usr/share
* Installing manually from galaxy installs to ~/.ansible
The order of precedence makes it so galaxy-installed collections will
have priority over those installed by the collection packages which have
precedence over those installed by the ansible package.
There may be edge cases where mismatched dependencies could lead to
issues but I'm not sure we can do much about that.
> Let me know what you think.
>
> Thanks
>
> On Tue, Jan 31, 2023 at 2:14 PM Paul Howarth <paul(a)city-fan.org> wrote:
>> On Mon, 30 Jan 2023 21:13:11 -0700
>> Orion Poplawski <orion(a)nwra.com> wrote:
>>
>>> So, I'm wondering if we should have some kind of (at least
>>> semi-)coordinated plan for updating ansible collections in EPEL?
>>>
>>> My initial thought is we would sort of piggy back on to what the
>>> "ansible" community collection bundles on top of the ansible-core
>>> package provided by RedHat. So, currently in EL8.7 we have:
>>>
>>> ansible-core-2.13.3
>>>
>>> and EPEL ships:
>>>
>>> ansible-6.3.0 - which corresponds to the ansible community package
>>> that ships with ansible-2.13.3.
>>>
>>> Then we would endeavor to ship the individual package collection
>>> versions that are contained in that package, .e.g: (taken from the
>>> MANIFEST.json files):
>>>
>>> ansible.posix 1.4.0
>>> ansible.utils 2.6.1
>>> chocolatey.chocolatey 1.3.0
>>> community.docker 2.7.1
>>> community.general 5.5.0
>>> community.libvirt 1.2.0
>>> community.mysql 3.4.0
>>> community.rabbitmq 1.2.2
>>> containers.podman 1.9.4
>>> netbox.netbox 3.7.1
>>
>> Sounds like a reasonable plan to me.
>>
>>> For reference, currently in epel we have:
>> ...
>>> ansible-collection-community-libvirt.noarch 1.1.0-3.el8
>>> epel
>>
>> I updated ansible-collection-community-libvirt to 1.2.0:
>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-98b1fc46a5
>>
>>> I don't really have a particular agenda here, just trying to solicit
>>> people's thoughts. Personally I like minimal installs so I have been
>>> only using ansible-core + collections on the systems I maintain and
>>> would like to continue to see them be usable together.
>>
>> I too just use ansible-core + collections on the systems I maintain.
>>
>> Regards, Paul.
>>
>
>
> --
> Best regards
> Sagi Shnaidman
6 days, 9 hours
Fwd: Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
by Maxwell G
2023-01-31T13:02:09Z Sagi Shnaidman <sshnaidm(a)redhat.com>:
Hi, Orion
Thanks for raising this question.
I use both ways - either ansible distro with all-inclusive, or ansible
(distro or "core") with specific collection installed separately when I
need a newer version of collection, for example. I wonder if it's
possible to continue to update collections to the newest versions anyway.
If someone wants to use the collection version provided in "big ansible",
they would use ansible 6.3.0 with all included. If they want a newer
collection, they can install a separate newest RPM.
But not sure if dependencies can be a problem here, like which collection
version depends on other collection versions (for example ansible.utils,
which is part of multiple collection dependencies).
Let me know what you think.
Thanks
On Tue, Jan 31, 2023 at 2:14 PM Paul Howarth <paul(a)city-fan.org> wrote:
> On Mon, 30 Jan 2023 21:13:11 -0700
> Orion Poplawski <orion(a)nwra.com> wrote:
>
>> So, I'm wondering if we should have some kind of (at least
>> semi-)coordinated plan for updating ansible collections in EPEL?
>>
>> My initial thought is we would sort of piggy back on to what the
>> "ansible" community collection bundles on top of the ansible-core
>> package provided by RedHat. So, currently in EL8.7 we have:
>>
>> ansible-core-2.13.3
>>
>> and EPEL ships:
>>
>> ansible-6.3.0 - which corresponds to the ansible community package
>> that ships with ansible-2.13.3.
>>
>> Then we would endeavor to ship the individual package collection
>> versions that are contained in that package, .e.g: (taken from the
>> MANIFEST.json files):
>>
>> ansible.posix 1.4.0
>> ansible.utils 2.6.1
>> chocolatey.chocolatey 1.3.0
>> community.docker 2.7.1
>> community.general 5.5.0
>> community.libvirt 1.2.0
>> community.mysql 3.4.0
>> community.rabbitmq 1.2.2
>> containers.podman 1.9.4
>> netbox.netbox 3.7.1
>
> Sounds like a reasonable plan to me.
>
>> For reference, currently in epel we have:
> ...
>> ansible-collection-community-libvirt.noarch 1.1.0-3.el8
>> epel
>
> I updated ansible-collection-community-libvirt to 1.2.0:
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-98b1fc46a5
>
>> I don't really have a particular agenda here, just trying to solicit
>> people's thoughts. Personally I like minimal installs so I have been
>> only using ansible-core + collections on the systems I maintain and
>> would like to continue to see them be usable together.
>
> I too just use ansible-core + collections on the systems I maintain.
>
> Regards, Paul.
>
--
Best regards
Sagi Shnaidman
6 days, 9 hours
Replace versioned MODULE_COMPAT_ requires by generators
by Jitka Plesnikova
Hi,
I am preparing replacement of versioned MODULE_COMPAT_ requires by
dependency generators.
More details about the change can be found in mail thread [1].
The dependency generator, which I have prepared for Fedora, does not
work for EPEL.
I would like to help maintainers who prefer one version of the spec file
for all releases,
if it is possible.
Could be the following file added to the package epel-rpm-macros (or
anything like this) for EPEL 9?
$ cat perlcompat.attr
%__perlcompat_requires() %{lua:
local path = rpm.expand('%1')
local perl_ver = rpm.expand('%{perl_version}')
if path:match('.+%.so$') and perl_ver ~= "" then
print('perl(:MODULE_COMPAT_' .. perl_ver .. ')')
else
print('perl-libs')
end
}
%__perlcompat_path
^(%{perl_vendorarch}|%{perl_vendorlib}|%{perl_privlib}|%{perl_archlib})/.+
But I don't know how to do it for EPEL 7/8, because the above file
doesn't work.
It ends with error [2]:
error: Couldn't exec perl-libs: No such file or directory
Do you have any idea if there is any other way how to provide
maintainers this functionality for EPEL 7/8?
Thanks for any advice,
Jitka
[1]
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
[2]
https://download.copr.fedorainfracloud.org/results/jplesnik/perl-epel/cen...
--
Jitka Plesnikova
Senior Software Engineer
Red Hat
6 days, 9 hours
A coordinated plan for ansible-collection updates in EPEL?
by Orion Poplawski
So, I'm wondering if we should have some kind of (at least
semi-)coordinated plan for updating ansible collections in EPEL?
My initial thought is we would sort of piggy back on to what the
"ansible" community collection bundles on top of the ansible-core
package provided by RedHat. So, currently in EL8.7 we have:
ansible-core-2.13.3
and EPEL ships:
ansible-6.3.0 - which corresponds to the ansible community package that
ships with ansible-2.13.3.
Then we would endeavor to ship the individual package collection
versions that are contained in that package, .e.g: (taken from the
MANIFEST.json files):
ansible.posix 1.4.0
ansible.utils 2.6.1
chocolatey.chocolatey 1.3.0
community.docker 2.7.1
community.general 5.5.0
community.libvirt 1.2.0
community.mysql 3.4.0
community.rabbitmq 1.2.2
containers.podman 1.9.4
netbox.netbox 3.7.1
For reference, currently in epel we have:
ansible-collection-ansible-posix.noarch 1.4.0-1.el8 epel
ansible-collection-ansible-utils.noarch 2.6.1-1.el8 epel
ansible-collection-chocolatey-chocolatey.noarch 1.4.0-1.el8 epel
ansible-collection-community-docker.noarch 2.6.0-1.el8 epel
ansible-collection-community-general.noarch 3.8.9-1.el8 epel
ansible-collection-community-libvirt.noarch 1.1.0-3.el8 epel
ansible-collection-community-mysql.noarch 3.5.1-1.el8 epel
ansible-collection-community-rabbitmq.noarch 1.2.3-1.el8 epel
ansible-collection-containers-podman.noarch 1.10.1-1.el8 epel
ansible-collection-netbox-netbox.noarch 3.7.1-1.el8 epel
However, it's hard for me to resist the allure of the shiny and new, so
I've updated chocolatey. Similarly some others have been updated to
later versions.
The other interesting case here is community.general - ansible has it at
5.5.0, but it looks like Maxwell G has taken the generally preferred
course for EPEL of sticking with the stable release track of 3.X.
Although I suspect very few collections maintain multiple release tracks
(no idea).
I don't really have a particular agenda here, just trying to solicit
people's thoughts. Personally I like minimal installs so I have been
only using ansible-core + collections on the systems I maintain and
would like to continue to see them be usable together.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
6 days, 16 hours
EPEL 8: %__python3 == /usr/bin/python3 creates runtime problems with alternatives
by 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.)
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
6 days, 18 hours
Fedora EPEL 7 updates-testing report
by updates＠fedoraproject.org
The following Fedora EPEL 7 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2b409ccc37 imlib2-1.4.9-8.el7
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-970698785b golang-1.18.9-1.el7
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f41d6b3e32 python3-pygments-2.4.2-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
distribution-gpg-keys-1.82-1.el7
Details about builds:
================================================================================
distribution-gpg-keys-1.82-1.el7 (FEDORA-EPEL-2023-a165426a96)
GPG keys of various Linux distributions
--------------------------------------------------------------------------------
Update Information:
- move symlink of fedora-rawhide to fedora-39 - add openEuler new key - update
copr keys - add fedora 40 gpg key
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miroslav Such�� <msuchy(a)redhat.com> 1.82-1
- move symlink of fedora-rawhide to fedora-39
- add openEuler new key
- update copr keys
- add fedora 40 gpg key
--------------------------------------------------------------------------------
1 week
Fedora EPEL 8 updates-testing report
by updates＠fedoraproject.org
The following Fedora EPEL 8 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5792a74fc0 advancecomp-2.5-1.el8
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1d186ca718 python-rq-1.12.0-1.el8
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-d92a0ff759 syncthing-1.23.0-2.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
PyQt-builder-1.13.0-3.el8
ansible-packaging-1-8.2.el8
cockpit-file-sharing-2.4.1-6.el8
distribution-gpg-keys-1.82-1.el8
group-service-1.4.0-1.el8
opendmarc-1.4.2-10.el8
podman-compose-1.0.3-4.el8
pypolicyd-spf-2.9.3-5.el8
python-dotenv-0.19.2-5.el8
python-impacket-0.10.0-2.el8
python-junitxml-0.7-29.el8
python-kaptan-0.5.12-16.el8
python-sphinx_lv2_theme-1.2.0-2.el8
yubihsm-shell-2.4.0-1.el8
Details about builds:
================================================================================
PyQt-builder-1.13.0-3.el8 (FEDORA-EPEL-2023-f263a8ead2)
The PEP 517 compliant PyQt build system
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
ChangeLog:
* Wed Jan 18 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.13.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
--------------------------------------------------------------------------------
================================================================================
ansible-packaging-1-8.2.el8 (FEDORA-EPEL-2023-b0371d3d2d)
RPM packaging macros and generators for Ansible collections
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 1-8.2
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
cockpit-file-sharing-2.4.1-6.el8 (FEDORA-EPEL-2023-e6b7a0556c)
Cockpit user interface for managing SMB and NFS file sharing.
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8 See
https://lists.fedoraproject.org/archives/list/epel-
devel(a)lists.fedoraproject.org/thread/RE3PG72B5AX7NTACPDSBGOWCMN7I3OQJ/
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <miro(a)hroncok.cz> - 2.4.1-6
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
distribution-gpg-keys-1.82-1.el8 (FEDORA-EPEL-2023-60a3fd5c7c)
GPG keys of various Linux distributions
--------------------------------------------------------------------------------
Update Information:
- move symlink of fedora-rawhide to fedora-39 - add openEuler new key - update
copr keys - add fedora 40 gpg key
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miroslav Such�� <msuchy(a)redhat.com> 1.82-1
- move symlink of fedora-rawhide to fedora-39
- add openEuler new key
- update copr keys
- add fedora 40 gpg key
--------------------------------------------------------------------------------
================================================================================
group-service-1.4.0-1.el8 (FEDORA-EPEL-2023-53692e6ccf)
Dbus Group management CLI tool
--------------------------------------------------------------------------------
Update Information:
- update to 1.4.0
--------------------------------------------------------------------------------
ChangeLog:
* Thu Jan 26 2023 Wolfgang Ulbrich <fedora(a)raveit.de> - 1.4.0-1
- update to 1.4.0
--------------------------------------------------------------------------------
================================================================================
opendmarc-1.4.2-10.el8 (FEDORA-EPEL-2023-24345cb694)
A Domain-based Message Authentication, Reporting & Conformance (DMARC) milter and library
--------------------------------------------------------------------------------
Update Information:
Fixes systemd service file to use environment $OPTIONS at startup, and $MAINPID
at config reload, as expected.
--------------------------------------------------------------------------------
ChangeLog:
* Sun Jan 29 2023 Matt Domsch <mdomsch(a)fedoraproject.org> - 1.4.2-10
- escape systemd service file OPTIONS and MAINPID references so they exist at runtime
* Thu Jan 19 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.4.2-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
--------------------------------------------------------------------------------
================================================================================
podman-compose-1.0.3-4.el8 (FEDORA-EPEL-2023-ce9bd808e5)
Run docker-compose.yml using podman
--------------------------------------------------------------------------------
Update Information:
Shebang rebuild
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 1.0.3-4
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
pypolicyd-spf-2.9.3-5.el8 (FEDORA-EPEL-2023-be43a5f08f)
SPF Policy Server for Postfix (Python implementation)
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 2.9.3-5
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
python-dotenv-0.19.2-5.el8 (FEDORA-EPEL-2023-0575025775)
Read key-value pairs from a .env file and set them as environment variables
--------------------------------------------------------------------------------
Update Information:
Shebang rebuild
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 0.19.2-5
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
python-impacket-0.10.0-2.el8 (FEDORA-EPEL-2023-5c03b168e3)
Collection of Python classes providing access to network packets
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 0.10.0-2
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
python-junitxml-0.7-29.el8 (FEDORA-EPEL-2023-35d7c49212)
PyJUnitXML, a pyunit extension to output JUnit compatible XML
--------------------------------------------------------------------------------
Update Information:
Shebang rebuild
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 0.7-29
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
python-kaptan-0.5.12-16.el8 (FEDORA-EPEL-2023-07d90802b6)
Configuration parser
--------------------------------------------------------------------------------
Update Information:
Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Miro Hron��ok <mhroncok(a)redhat.com> - 0.5.12-16
- Rebuilt to change Python shebangs to /usr/bin/python3.6 on EPEL 8
--------------------------------------------------------------------------------
================================================================================
python-sphinx_lv2_theme-1.2.0-2.el8 (FEDORA-EPEL-2023-8466fc0b5c)
A minimal pure-CSS theme for Sphinx
--------------------------------------------------------------------------------
Update Information:
Version 1.2.0
--------------------------------------------------------------------------------
ChangeLog:
* Fri Jan 20 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.2.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Sep 1 2022 Guido Aulisi <guido.aulisi(a)gmail.com> - 1.2.0-1
- Update to 1.2.0
* Fri Jul 22 2022 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.0.0-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Mon Jun 13 2022 Python Maint <python-maint(a)redhat.com> - 1.0.0-7
- Rebuilt for Python 3.11
* Fri Jan 21 2022 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.0.0-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Fri Jul 23 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.0.0-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Fri Jun 4 2021 Python Maint <python-maint(a)redhat.com> - 1.0.0-4
- Rebuilt for Python 3.10
* Wed Jan 27 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.0.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
--------------------------------------------------------------------------------
================================================================================
yubihsm-shell-2.4.0-1.el8 (FEDORA-EPEL-2023-3860b78555)
Tools to interact with YubiHSM 2
--------------------------------------------------------------------------------
Update Information:
New upstream release (#2165239)
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jan 30 2023 Jakub Jelen <jjelen(a)redhat.com> - 2.4.0-1
- New upstream release (#2165239)
* Sat Jan 21 2023 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.2-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Sat Jul 23 2022 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.2-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Mon Jun 27 2022 Jakub Jelen <jjelen(a)redhat.com> - 2.3.2-1
- New upstream release (#2100542)
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #2165239 - yubihsm-shell-2.4.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2165239
--------------------------------------------------------------------------------
1 week
