I published version 1.2 which doesn't depend on bodhi-client anymore. It is
now on PyPI and Bodhi updates are in testing.

On Tue, Jan 23, 2024 at 12:59 PM Jakub Kadlcik <jkadl...@redhat.com> wrote:

> Thank you for the feedback Stephen,
> I didn't realize how many and how complicated dependencies the bodhli
> client package has. It was no problem when installing via DNF but you are
> right with the pip installation -
> https://github.com/rpm-software-management/fedora-distro-aliases/issues/3
>
> Please subscribe the issue, I will fix it soon :-)
>
> On Fri, Jan 19, 2024 at 8:34 PM Stephen Gallagher <sgall...@redhat.com>
> wrote:
>
>> On Thu, Jan 18, 2024 at 10:32 AM Stephen Gallagher <sgall...@redhat.com>
>> wrote:
>> >
>> > On Wed, Jan 17, 2024 at 5:58 AM Jakub Kadlcik <jkadl...@redhat.com>
>> wrote:
>> > >
>> > > Hello,
>> > > I just wanted to quickly announce a small project I did in
>> collaboration with the Packit folks.
>> > >
>> > > Do you have some tools or services that perform actions on all
>> currently active Fedora releases? And do you have to manually update their
>> list every time a new Fedora release is branched or EOLed? The
>> fedora-distro-aliases will make your life easier.
>> > >
>> > > https://github.com/rpm-software-management/fedora-distro-aliases
>> > >
>> > > It defines aliases such as `fedora-stable`, `epel-all`,
>> `fedora-latest`, etc. To evaluate them, it queries Bodhi, so they are
>> always up-to-date (but the tradeoff is that it requires an internet
>> connection). There are multiple examples in the project README but the
>> usage is simple, e.g.:
>> > >
>> > >     >>> from fedora_distro_aliases import get_distro_aliases
>> > >     >>> aliases = get_distro_aliases()
>> > >     >>> [x.namever for x in aliases["fedora-all"]]
>> > >     ['fedora-38', 'fedora-39', 'fedora-rawhide']
>> > >
>> > > The package is already in Fedora, give it a shot,
>> >
>> > Thanks! I'll look into updating
>> > https://github.com/sgallagher/get-fedora-releases-action with this.
>>
>> Scratch that, it appears that `pip3 install fedora_distro_aliases`
>> requires installing krb5 devel packages (and compiling it) on the
>> target system before it can be used. This had the effect in my testing
>> of increasing the time spent running my Action from ~10s to ~240s,
>> which is too big of an increase. Is there a good reason why you're
>> using the complete BodhiClient interface instead of just doing simple
>> HTTP requests against https://bodhi.fedoraproject.org/releases ?
>> --
>> _______________________________________________
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to 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/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to 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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to