7:12 a.m.
Hello folks,
Following up on the steps provided by the documentation [1], I would like to announce that
I am willing to unretire the package rust-starship [2]. I use this app on a daily basis,
and it seems like the previous maintainer is no longer interested in keeping the package,
so I would like to take over the ownership.
I will follow up on the remaining steps within the next few hours.
Please, let me know if there is anything else I should know about.
Thank you.
[1] https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retireme...
[2] https://src.fedoraproject.org/rpms/rust-starship
8:26 a.m.
On Wed, Nov 30, 2022 at 2:13 PM Mauricio Teixeira
<netmask(a)fedoraproject.org> wrote:
Hello folks,
Following up on the steps provided by the documentation [1], I would like to announce
that I am willing to unretire the package rust-starship [2]. I use this app on a daily
basis, and it seems like the previous maintainer is no longer interested in keeping the
package, so I would like to take over the ownership.
I will follow up on the remaining steps within the next few hours.
Please, let me know if there is anything else I should know about.
Thank you.
Hi!
Great to see that you're interested in resurrecting the starship
package. However, maintaining it and keeping it up-to-date in Fedora
requires a substantial amount of time, so you'd either have to
familiarize yourself with Rust packaging (and most likely assume
responsibility for ~a dozen library dependencies).
The previous maintainer is a seasoned Fedora packager and didn't have
the capacity to do that, so I'm not sure it's a good starting point
for you:
https://bugzilla.redhat.com/show_bug.cgi?id=2051601
If you'd like to use starship packages for Fedora, there's a COPR with
unofficial packages (maintained by the same packager who originally
maintained the package in Fedora) that should work fine but are built
in a way that's not allowed for official Fedora packages:
https://copr.fedorainfracloud.org/coprs/atim/starship/
Fabio
7:37 a.m.
On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider <asn(a)redhat.com> wrote:
On Wednesday, 30 November 2022 18:43:50 CET Mauricio Teixeira wrote:
> Fabio,
Hi Fabio,
> What is so bad about the COPR package that can't be used in the main repo?
It downloads packages from the internet and doesn't use system rust packages.
There are a lot of tools that do this. I just noticed that the
docker-ce SRPMs over at www.docker.com do this. ansible-core and
awscli also install internal versions of what should be separately
published python modules, it's an ongoing issue, and one of the
reasons to build things in "mock" or "koji" to prevent just that sort
of reaching out to thard party web sites during package compilation.
It's just the sort of off-site requirement that broke nodejs for a
*lot* of people for a while,
9:16 a.m.
On Fri Feb 17, 2023 at 08:37 -0500, Nico Kadel-Garcia wrote:
On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider
<asn(a)redhat.com> wrote:
> It downloads packages from the internet and doesn't use system rust packages.
ansible-core and awscli also install internal versions of what
should
be separately published python modules,
To be clear, it's RHEL/CentOS Stream's ansible-core package that does
this. They include sdists of jinja2, markupsafe (neeeded by jinja2),
packaging, pyparsing (needed by packaging), and resolvelib in the SRPM
and build/install them into a special vendor directory that ansible adds
to sys.path :(. Fedora's ansible-core's package does not do this, and I
very much am not a fan of the practice.
--
Maxwell G (@gotmax23)
Pronouns: He/They
1:08 p.m.
On Fri, Feb 17, 2023 at 10:17 AM Maxwell G <maxwell(a)gtmx.me> wrote:
On Fri Feb 17, 2023 at 08:37 -0500, Nico Kadel-Garcia wrote:
> On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider <asn(a)redhat.com> wrote:
> > It downloads packages from the internet and doesn't use system rust
packages.
> ansible-core and awscli also install internal versions of what should
> be separately published python modules,
To be clear, it's RHEL/CentOS Stream's ansible-core package that does
this. They include sdists of jinja2, markupsafe (neeeded by jinja2),
packaging, pyparsing (needed by packaging), and resolvelib in the SRPM
and build/install them into a special vendor directory that ansible adds
to sys.path :(. Fedora's ansible-core's package does not do this, and I
very much am not a fan of the practice.
Also "straightplugin". I see your name in the %changelog for
ansible-core in Fedora, thanks for your work there. I based my
published SRPM code on Fedora. If you've successfully navigated the
Fedora submission process, which I've never managed, despite a few
attempts..... Would you care to help me walk through them? Or can I
feed you the needed .spec files to get them into EPEL and possibly
help clean up the RHEL backports? I've some significant speedups and
improvements for the "ansible" package, as well, and I see your name
in the %changelog for that as well.
11:34 a.m.
New subject: Ansible and contributions (was Re: Willing to unretire package:
rust-starship)
(This is the second response I wrote to this email. I accidentally
deleted the first one :/)
On Fri Feb 17, 2023 at 14:08 -0500, Nico Kadel-Garcia wrote:
On Fri, Feb 17, 2023 at 10:17 AM Maxwell G <maxwell(a)gtmx.me>
wrote:
>
> On Fri Feb 17, 2023 at 08:37 -0500, Nico Kadel-Garcia wrote:
> > On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider <asn(a)redhat.com>
wrote:
> > > It downloads packages from the internet and doesn't use system rust
packages.
>
> > ansible-core and awscli also install internal versions of what should
> > be separately published python modules,
>
> To be clear, it's RHEL/CentOS Stream's ansible-core package that does
> this. They include sdists of jinja2, markupsafe (neeeded by jinja2),
> packaging, pyparsing (needed by packaging), and resolvelib in the SRPM
> and build/install them into a special vendor directory that ansible adds
> to sys.path :(. Fedora's ansible-core's package does not do this, and I
> very much am not a fan of the practice.
<snip>
I see your name in the %changelog for ansible-core in Fedora, thanks
for your work there. I based my published SRPM code on Fedora.
Sure :).
If you've successfully navigated the Fedora submission process,
which
I've never managed, despite a few attempts..... Would you care to help
me walk through them? Or can I feed you the needed .spec files to get
them into EPEL and possibly help clean up the RHEL backports? I've
some significant speedups and improvements for the "ansible" package,
as well, and I see your name in the %changelog for that as well.
What are you seeking to accomplish? If you simply want to help with
maintenance or submit improvements, src.fedoraproject.org pull requests
are welcome. If you submit enough quality pull requests, I could
eventually add you as a comaintainer [1]. If you'd like to submit a new
package to Fedora, take a look at [2].
[1] https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_policy/#comai...
[2]
https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Proc...
--
Best,
Maxwell G (@gotmax23)
Pronouns: He/They
437
days inactive
517
days old
7 comments
5 participants
participants (5)
-
Andreas Schneider -
Fabio Valentini -
Mauricio Teixeira -
Maxwell G -
Nico Kadel-Garcia