Re: Rust Stack Spring Cleaning - 2024 Edition
On 11/04/2024 15:26, Fabio Valentini wrote: Hello Rust packagers, I'm continuously working on reducing unnecessary accumulation of cruft in the Rust package stack in Fedora, and I have been keeping track of unused library packages for almost three years now. Thanks for working on this! For packages where I am *not* the primary maintainer, I need help: - Is this package still required for something that I don't know about, or can it be dropped? - Was it added as a dependency for something else, but packaging this "something else" was abandoned? - Was it needed at the time, but is the library no longer needed now? *snip* - principis (1): rust-escape8259 I packaged this as it's a new dependency for rust-libtest-mimic, added in 0.7.0 [0]. If this dependency is no longer necessary, please let me know and I'll be happy to retire it. [0]: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2258358 -- Arthur Bols fas/irc: principis -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
On Mon, Apr 22, 2024 at 5:13 PM Peter Robinson wrote: > > I am aware of a few of the above I'm listed against that my deps no > longer requre (eg passwd) but I hadn't got around to working out what > else depended on them to retire without possibly breaking something > else, overall happy for them to be retired as part of the mass > retirement if there's no other deps. Whoops, sorry about that - I constructed the "packages per maintainer" list manually, apparently I was too tired to check that everybody included in the table is also included in the per-maintainer lists :( > There's also some that are deps on things still in progress like > rust-rustls-pki-types (rhbz 2272351 has dep details), not sure how to > tag those so I don't have to do more work to repackage them. Thanks for checking! FYI, rustls-pki-types is no longer a leaf package since I updated rustls / reqwest to newer versions. Fabio -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
On Thu, 11 Apr 2024 at 14:26, Fabio Valentini wrote: > > Hello Rust packagers, > > I'm continuously working on reducing unnecessary accumulation of cruft > in the Rust package stack in Fedora, and I have been keeping track of > unused library packages for almost three years now. > > Some of these packages have been unused leaves for over two years! > > I will again start being more proactive with orphaning / retiring > affected packages where I am the primary maintainer, starting > incrementally from the packages which have been unused for the longest > time - unless I know of a reason to keep a specific package, for > example: > > - something that depends on the package is still going through package review > - the package was updated to a "breaking" release and a compat package > was created, and now the "main" package is not depended on while the > compat package is in use > > If you know of a reason why a leaf package where I am the primary > maintainer should not be retired, please let me know, and I will > exclude it from the list. > > For packages where I am *not* the primary maintainer, I need help: > > - Is this package still required for something that I don't know > about, or can it be dropped? > - Was it added as a dependency for something else, but packaging this > "something else" was abandoned? > - Was it needed at the time, but is the library no longer needed now? > > Keeping unused packages around only makes maintenance of the Rust > stack more difficult due to the more "dense" dependency graph that > needs to be considered when pushing "breaking" changes. Over the past > year or so, the number of Rust packages in Fedora has grown by almost > 50% from about 2200 to over 3000, which is making this issue worse. > > Full report included below (view in monospace font for correct formatting). > > Thank you for your help, > Fabio > > +--++---+--+ > | Package | Leaf since | Leaf days | Maintainer > | > +--++---+--+ > | rust-curve25519-dalek| 2021-11-18 | 875 | dcavalca > | > | rust-gstreamer-editing-services | 2021-11-18 | 875 | atim > | > | rust-gstreamer-player| 2021-11-18 | 875 | atim > | > | rust-rand_jitter | 2021-11-18 | 875 | jistone > | > | rust-rand_os | 2021-11-18 | 875 | jistone > | > | rust-tower-test | 2021-11-18 | 875 | decathorpe > | > | rust-tower-util | 2021-11-18 | 875 | decathorpe > | > | rust-partial-io | 2022-02-06 | 795 | decathorpe > | > | rust-minimad | 2022-02-18 | 783 | dcavalca > | > | rust-libhandy| 2022-02-20 | 781 | decathorpe > | > | rust-tiger | 2022-02-20 | 781 | decathorpe > | > | rust-rand_hc | 2022-02-21 | 780 | jistone > | > | rust-benfred-read-process-memory | 2022-02-27 | 774 | dcavalca > | > | rust-custom_error| 2022-02-27 | 774 | dcavalca > | > | rust-madvr_parse | 2022-02-27 | 774 | dcavalca > | > | rust-os-release | 2022-02-27 | 774 | dcavalca > | > | rust-strict | 2022-02-27 | 774 | dcavalca > | > | rust-subprocess | 2022-02-27 | 774 | dcavalca > | > | rust-libxml | 2022-04-07 | 735 | decathorpe > | > | rust-snake_case | 2022-04-25 | 717 | decathorpe > | > | rust-openat-ext | 2022-04-28 | 714 | walters > | > | rust-log-mdc | 2022-05-05 | 707 | decathorpe > | > | rust-cargo-manifest | 2022-05-06 | 706 | laiot > | > | rust-digest_auth | 2022-05-06 | 706 | laiot > | > | rust-binascii| 2022-05-10 | 702 | saluki > | > | rust-inlinable_string| 2022-05-10 | 702 | decathorpe > | > | rust-ubyte | 2022-05-10 | 702 | decathorpe > | > | rust-email-encoding | 2022-05-17 | 695 | saluki > | > | rust-tabular | 2022-05-23 | 689 | jbtrystram > | > | rust-async-mutex | 2022-06-01 | 680 | decathorpe > | > | rust-awc | 2022-06-01 | 680 | decathorpe > | > | rust-infer | 2022-06-15 | 666 | decathorpe > | > | rust-escape_string | 2022-07-08 | 643 | dcavalca > | > | rust-actix
Re: Rust Stack Spring Cleaning - 2024 Edition
On Fri, Apr 19, 2024 at 5:37 PM Davide Cavalca wrote: > > On 2024-04-11 06:26, Fabio Valentini wrote: > > - dcavalca (33): rust-base-x, rust-benfred-read-process-memory, > > rust-cap, rust-combine, rust-concolor, rust-cpc, > > rust-curve25519-dalek, rust-custom_error, rust-escape_string, > > rust-esphome, rust-exitfailure, rust-gmp-mpfr-sys, rust-hyperlocal, > > rust-local-encoding, rust-local_ipaddress, rust-madvr_parse, > > rust-memcached-rs, rust-minimad, rust-names, rust-netstat2, > > rust-os-release, rust-pathsearch, rust-random, rust-rusttype, > > rust-serde_bser, rust-smallstr, rust-rust-strict, rust-subprocess, > > rust-temp_testdir, rust-termwiz, rust-tokio-compat, rust-typed-builder > > Some of these (e.g. rust-cpc, rust-names) publish binaries; it'd > probably be good to exclude those from leaf cleanup (or bucket them > separately, as it's not uncommon for packages with binaries to be > leaves). The rest are part of various in-progress packaging efforts > (e.g. termwiz is for wezterm) and I'd rather keep them around for > another cycle while these move forward. Thanks! Sorry about that, I thought I had excluded all packages that provide applications, but apparently I missed some. Though I don't think cpc and names were specifically packaged for their executables, but as dependencies for something else? As for termwiz / wezterm, do you plan to reopen / resubmit the package review requests that have been stalled out? Thanks, Fabio -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
On 2024-04-11 06:26, Fabio Valentini wrote: - dcavalca (33): rust-base-x, rust-benfred-read-process-memory, rust-cap, rust-combine, rust-concolor, rust-cpc, rust-curve25519-dalek, rust-custom_error, rust-escape_string, rust-esphome, rust-exitfailure, rust-gmp-mpfr-sys, rust-hyperlocal, rust-local-encoding, rust-local_ipaddress, rust-madvr_parse, rust-memcached-rs, rust-minimad, rust-names, rust-netstat2, rust-os-release, rust-pathsearch, rust-random, rust-rusttype, rust-serde_bser, rust-smallstr, rust-rust-strict, rust-subprocess, rust-temp_testdir, rust-termwiz, rust-tokio-compat, rust-typed-builder Some of these (e.g. rust-cpc, rust-names) publish binaries; it'd probably be good to exclude those from leaf cleanup (or bucket them separately, as it's not uncommon for packages with binaries to be leaves). The rest are part of various in-progress packaging efforts (e.g. termwiz is for wezterm) and I'd rather keep them around for another cycle while these move forward. Thanks! Cheers Davide -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
On Thu, 2024-04-11 at 15:26 +0200, Fabio Valentini wrote: > > - alciregi (1): rust-backoff > Hello. This is required by a package still under review (waiting for a reviewer actually). https://bugzilla.redhat.com/show_bug.cgi?id=2268499 Thank you, Alessio -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
> I'm continuously working on reducing unnecessary accumulation of cruft in the Rust package stack in Fedora, and I have been keeping track of unused library packages for almost three years now. Thanks for taking the time and looking into this! > - blinxen (8): rust-btoi, rust-fallible_collections, rust-noisy_float, rust-parse-size, rust-ptyprocess, rust-sanitize-filename, rust-serde_plain, rust-symlink I don't remember why these were packaged. They can be safely retired, if nothing depends on them. -- ___ 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
Re: [Rust] Re: Rust Stack Spring Cleaning - 2024 Edition
On Thu, Apr 11, 2024 at 9:09 PM Michel Lind wrote:
>
> > | rust-atomic-traits | 2022-09-02 | 587 | salimma
> >|
> Still trying to package mmtk, please keep this one for now
Then please follow up, the review request for mmtk was closed due to inactivity:
https://bugzilla.redhat.com/show_bug.cgi?id=2040994
> > | rust-signal | 2023-02-23 | 413 | salimma
> >|
> Not sure about this one. Looks like psutil depends on it, and ytop
> depends on psutil, but ytop is almost 4 years old... probably retire it
https://bugzilla.redhat.com/show_bug.cgi?id=2048155
Looks like pipewire bindings version < 0.7 depended on this, but
dropped the dependency with v0.7.
> > | rust-sptr| 2023-03-28 | 380 | salimma
> >|
> This is needed by portable-atomic which is needed by pyo3, right?
sptr is a dev-dependency for portable-atomic only, and portable-atomic
tests can no longer be run from the published tarbals.
It might be ok to drop sptr.
> > | rust-xcb | 2023-05-10 | 337 | salimma
> >|
> We can kill this I guess. Death to X
Looks like this used to be a dependency of x11-clipboard <0.7, but no
longer is as of v0.7.0.
> > | rust-powierza-coefficient| 2023-06-16 | 300 | salimma
> >|
> I wonder what used it in the past. crates.io now only lists kn ... so
> yeah kill it
This was packaged for nu-command, but the dependency has since been dropped:
https://bugzilla.redhat.com/show_bug.cgi?id=2211278
> > | rust-wayland-commons | 2024-01-02 | 100 | salimma
> >|
> Looks like wayland-{client,server} no longer needs this (since > 0.29).
> Kill.
Agree, this crate seems to have been dropped from wayland-rs.
> > | rust-nom-supreme | 2024-01-04 |98 | salimma
> >|
> Can't find what's actually using it, maybe kill
This was packaged for wax:
https://bugzilla.redhat.com/show_bug.cgi?id=2174116
And was was packaged for nu-command:
https://bugzilla.redhat.com/show_bug.cgi?id=2174146
But wax no longer depends on nom-supreme as of v0.6.0.
> > | rust-vec1| 2024-01-04 |98 | salimma
> >|
> Ditto - not sure what I needed this for, probably dropped upstream
Same here:
https://bugzilla.redhat.com/show_bug.cgi?id=2174097
This used to be a dependency of wax, but it was dropped as of v0.6.0
> > | rust-rlimit | 2024-01-17 |85 | salimma
> >|
> Ditto
Can't tell - the review request isn't marked as blocking anything.
https://bugzilla.redhat.com/show_bug.cgi?id=2258271
At least it's a dependency of "bsdutils":
https://crates.io/crates/bsdutils
So maybe it was part of the coreutils dependency tree for some of the
missing uu_* tools?
> > | rust-base32 | 2024-01-20 |82 | salimma
> >|
> rbw needs this, still in progress
Noted, thank you for checking!
Fabio
--
___
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
Re: Rust Stack Spring Cleaning - 2024 Edition
On Thu, Apr 11, 2024 at 7:45 PM Ben Beasley wrote: > > The rust-circular-buffer crate was packaged as a dependency for bpftop, > https://github.com/Netflix/bpftop. > > I won’t necessarily be packaging bpftop myself, but I know several > parties are interested in doing so, and I expect it will happen soon one > way or the other. Thanks! I forgot about that, it's good to have this in writing. > A few existing dependencies still need to be updated first: > > Problem 1: nothing provides requested (crate(anyhow/default) >= 1.0.81 > with crate(anyhow/default) < 2.0.0~) > Problem 2: nothing provides requested (crate(libbpf-rs/default) >= > 0.23.0 with crate(libbpf-rs/default) < 0.24.0~) > Problem 3: nothing provides requested (crate(libbpf-sys/default) >= > 1.4.0 with crate(libbpf-sys/default) < 2.0.0~) > Problem 4: nothing provides requested (crate(ratatui) >= 0.26.1 with > crate(ratatui) < 0.27.0~) > Problem 5: nothing provides requested (crate(ratatui/crossterm) >= > 0.26.1 with crate(ratatui/crossterm) < 0.27.0~) > Problem 6: nothing provides requested (crate(tui-input/default) >= > 0.8.0 with crate(tui-input/default) < 0.9.0~) I can update anyhow tomorrow, that should be a simple update. Michel said he'll be looking at libbpf-rs / libbpf-sys soon. ratatui can be updated too, though it might require a compat package for the current version tui-input seems to be a new dependency. Thank you for checking, Fabio -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
On Thu, Apr 11, 2024 at 01:45:26PM -0400, Ben Beasley wrote: > The rust-circular-buffer crate was packaged as a dependency for bpftop, > https://github.com/Netflix/bpftop. > > I won’t necessarily be packaging bpftop myself, but I know several parties > are interested in doing so, and I expect it will happen soon one way or the > other. > > A few existing dependencies still need to be updated first: > > Problem 1: nothing provides requested (crate(anyhow/default) >= 1.0.81 with > crate(anyhow/default) < 2.0.0~) > Problem 2: nothing provides requested (crate(libbpf-rs/default) >= 0.23.0 > with crate(libbpf-rs/default) < 0.24.0~) > Problem 3: nothing provides requested (crate(libbpf-sys/default) >= 1.4.0 > with crate(libbpf-sys/default) < 2.0.0~) > Problem 4: nothing provides requested (crate(ratatui) >= 0.26.1 with > crate(ratatui) < 0.27.0~) > Problem 5: nothing provides requested (crate(ratatui/crossterm) >= 0.26.1 > with crate(ratatui/crossterm) < 0.27.0~) > Problem 6: nothing provides requested (crate(tui-input/default) >= 0.8.0 > with crate(tui-input/default) < 0.9.0~) > Speaking of all the bpf* - I have a TODO (will ping the chat too) to update below, which I expect will require a lot of libbpf-* to be updated. For ratatui -- nu-explore >= 0.91.0 needs 0.26, but I dropped it to 0.25 instead, trying to remember why. Ah... because dua-cli, gimoji, and tui-react needs the old one ❯ fedrq-cratedeps-verbose.sh ratatui rust-dua-cli : (crate(ratatui) >= 0.25.0 with crate(ratatui) < 0.26.0~) rust-gimoji : (crate(ratatui/default) >= 0.25.0 with crate(ratatui/default) < 0.26.0~) rust-nu-explore : (crate(ratatui/default) >= 0.25.0 with crate(ratatui/default) < 0.26.0~) rust-tui-react : (crate(ratatui) >= 0.25.0 with crate(ratatui) < 0.26.0~) Best, -- _o) Michel Lind (né Salim) _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: PGP signature -- ___ 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
Re: Rust Stack Spring Cleaning - 2024 Edition
Hi Fabio,
On Thu, Apr 11, 2024 at 03:26:13PM +0200, Fabio Valentini wrote:
> If you know of a reason why a leaf package where I am the primary
> maintainer should not be retired, please let me know, and I will
> exclude it from the list.
>
Thanks for organizing the cleanup!
>
> +--++---+--+
> | Package | Leaf since | Leaf days | Maintainer
> |
> +--++---+--+
> | rust-atomic-traits | 2022-09-02 | 587 | salimma
> |
Still trying to package mmtk, please keep this one for now
> | rust-signal | 2023-02-23 | 413 | salimma
> |
Not sure about this one. Looks like psutil depends on it, and ytop
depends on psutil, but ytop is almost 4 years old... probably retire it
> | rust-sptr| 2023-03-28 | 380 | salimma
> |
This is needed by portable-atomic which is needed by pyo3, right?
> | rust-xcb | 2023-05-10 | 337 | salimma
> |
We can kill this I guess. Death to X
> | rust-powierza-coefficient| 2023-06-16 | 300 | salimma
> |
I wonder what used it in the past. crates.io now only lists kn ... so
yeah kill it
> | rust-wayland-commons | 2024-01-02 | 100 | salimma
> |
Looks like wayland-{client,server} no longer needs this (since > 0.29).
Kill.
> | rust-nom-supreme | 2024-01-04 |98 | salimma
> |
Can't find what's actually using it, maybe kill
> | rust-vec1| 2024-01-04 |98 | salimma
> |
Ditto - not sure what I needed this for, probably dropped upstream
> | rust-async-process | 2024-01-07 |95 | decathorpe
> |
> | rust-notify-debouncer-mini | 2024-01-07 |95 | decathorpe
> |
> | rust-safetensors | 2024-01-07 |95 | thunderbirdtr
> |
> | rust-unidecode | 2024-01-15 |87 | decathorpe
> |
> | rust-rlimit | 2024-01-17 |85 | salimma
> |
Ditto
> | rust-base32 | 2024-01-20 |82 | salimma
> |
rbw needs this, still in progress
>
> - salimma (10): rust-atomic-traits, rust-base32, rust-nom-supreme,
> rust-powierza-coefficient, rust-rlimit, rust-signal, rust-sptr,
> rust-vec1, rust-wayland-commons, rust-xcb
>
Best,
--
_o) Michel Lind (né Salim)
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
signature.asc
Description: PGP signature
--
___
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
Re: Rust Stack Spring Cleaning - 2024 Edition
The rust-circular-buffer crate was packaged as a dependency for bpftop, https://github.com/Netflix/bpftop. I won’t necessarily be packaging bpftop myself, but I know several parties are interested in doing so, and I expect it will happen soon one way or the other. A few existing dependencies still need to be updated first: Problem 1: nothing provides requested (crate(anyhow/default) >= 1.0.81 with crate(anyhow/default) < 2.0.0~) Problem 2: nothing provides requested (crate(libbpf-rs/default) >= 0.23.0 with crate(libbpf-rs/default) < 0.24.0~) Problem 3: nothing provides requested (crate(libbpf-sys/default) >= 1.4.0 with crate(libbpf-sys/default) < 2.0.0~) Problem 4: nothing provides requested (crate(ratatui) >= 0.26.1 with crate(ratatui) < 0.27.0~) Problem 5: nothing provides requested (crate(ratatui/crossterm) >= 0.26.1 with crate(ratatui/crossterm) < 0.27.0~) Problem 6: nothing provides requested (crate(tui-input/default) >= 0.8.0 with crate(tui-input/default) < 0.9.0~) Some of these might just reflect over-aggressive bounds from dependabot that could be loosened downstream, but other minimum versions are likely real. On 4/11/24 9:26 AM, Fabio Valentini wrote: Hello Rust packagers, I'm continuously working on reducing unnecessary accumulation of cruft in the Rust package stack in Fedora, and I have been keeping track of unused library packages for almost three years now. Some of these packages have been unused leaves for over two years! I will again start being more proactive with orphaning / retiring affected packages where I am the primary maintainer, starting incrementally from the packages which have been unused for the longest time - unless I know of a reason to keep a specific package, for example: - something that depends on the package is still going through package review - the package was updated to a "breaking" release and a compat package was created, and now the "main" package is not depended on while the compat package is in use If you know of a reason why a leaf package where I am the primary maintainer should not be retired, please let me know, and I will exclude it from the list. For packages where I am *not* the primary maintainer, I need help: - Is this package still required for something that I don't know about, or can it be dropped? - Was it added as a dependency for something else, but packaging this "something else" was abandoned? - Was it needed at the time, but is the library no longer needed now? Keeping unused packages around only makes maintenance of the Rust stack more difficult due to the more "dense" dependency graph that needs to be considered when pushing "breaking" changes. Over the past year or so, the number of Rust packages in Fedora has grown by almost 50% from about 2200 to over 3000, which is making this issue worse. Full report included below (view in monospace font for correct formatting). Thank you for your help, Fabio +--++---+--+ | Package | Leaf since | Leaf days | Maintainer | +--++---+--+ | rust-curve25519-dalek| 2021-11-18 | 875 | dcavalca | | rust-gstreamer-editing-services | 2021-11-18 | 875 | atim | | rust-gstreamer-player| 2021-11-18 | 875 | atim | | rust-rand_jitter | 2021-11-18 | 875 | jistone | | rust-rand_os | 2021-11-18 | 875 | jistone | | rust-tower-test | 2021-11-18 | 875 | decathorpe | | rust-tower-util | 2021-11-18 | 875 | decathorpe | | rust-partial-io | 2022-02-06 | 795 | decathorpe | | rust-minimad | 2022-02-18 | 783 | dcavalca | | rust-libhandy| 2022-02-20 | 781 | decathorpe | | rust-tiger | 2022-02-20 | 781 | decathorpe | | rust-rand_hc | 2022-02-21 | 780 | jistone | | rust-benfred-read-process-memory | 2022-02-27 | 774 | dcavalca | | rust-custom_error| 2022-02-27 | 774 | dcavalca | | rust-madvr_parse | 2022-02-27 | 774 | dcavalca | | rust-os-release | 2022-02-27 | 774 | dcavalca | | rust-strict | 2022-02-27 | 774 | dcavalca | | rust-subprocess | 2022-02-27 | 774 | dcavalca | | rust-libxml | 2022-04-07 | 735 | decathorpe | | rust-snake_case | 2022-04-25 | 717 | decathorpe | | rust-openat-ext | 2022-04-28 | 714 | walters | | rust-log-mdc | 2022-05-05 | 707 | decathorpe | |
Rust Stack Spring Cleaning - 2024 Edition
Hello Rust packagers, I'm continuously working on reducing unnecessary accumulation of cruft in the Rust package stack in Fedora, and I have been keeping track of unused library packages for almost three years now. Some of these packages have been unused leaves for over two years! I will again start being more proactive with orphaning / retiring affected packages where I am the primary maintainer, starting incrementally from the packages which have been unused for the longest time - unless I know of a reason to keep a specific package, for example: - something that depends on the package is still going through package review - the package was updated to a "breaking" release and a compat package was created, and now the "main" package is not depended on while the compat package is in use If you know of a reason why a leaf package where I am the primary maintainer should not be retired, please let me know, and I will exclude it from the list. For packages where I am *not* the primary maintainer, I need help: - Is this package still required for something that I don't know about, or can it be dropped? - Was it added as a dependency for something else, but packaging this "something else" was abandoned? - Was it needed at the time, but is the library no longer needed now? Keeping unused packages around only makes maintenance of the Rust stack more difficult due to the more "dense" dependency graph that needs to be considered when pushing "breaking" changes. Over the past year or so, the number of Rust packages in Fedora has grown by almost 50% from about 2200 to over 3000, which is making this issue worse. Full report included below (view in monospace font for correct formatting). Thank you for your help, Fabio +--++---+--+ | Package | Leaf since | Leaf days | Maintainer | +--++---+--+ | rust-curve25519-dalek| 2021-11-18 | 875 | dcavalca | | rust-gstreamer-editing-services | 2021-11-18 | 875 | atim | | rust-gstreamer-player| 2021-11-18 | 875 | atim | | rust-rand_jitter | 2021-11-18 | 875 | jistone | | rust-rand_os | 2021-11-18 | 875 | jistone | | rust-tower-test | 2021-11-18 | 875 | decathorpe | | rust-tower-util | 2021-11-18 | 875 | decathorpe | | rust-partial-io | 2022-02-06 | 795 | decathorpe | | rust-minimad | 2022-02-18 | 783 | dcavalca | | rust-libhandy| 2022-02-20 | 781 | decathorpe | | rust-tiger | 2022-02-20 | 781 | decathorpe | | rust-rand_hc | 2022-02-21 | 780 | jistone | | rust-benfred-read-process-memory | 2022-02-27 | 774 | dcavalca | | rust-custom_error| 2022-02-27 | 774 | dcavalca | | rust-madvr_parse | 2022-02-27 | 774 | dcavalca | | rust-os-release | 2022-02-27 | 774 | dcavalca | | rust-strict | 2022-02-27 | 774 | dcavalca | | rust-subprocess | 2022-02-27 | 774 | dcavalca | | rust-libxml | 2022-04-07 | 735 | decathorpe | | rust-snake_case | 2022-04-25 | 717 | decathorpe | | rust-openat-ext | 2022-04-28 | 714 | walters | | rust-log-mdc | 2022-05-05 | 707 | decathorpe | | rust-cargo-manifest | 2022-05-06 | 706 | laiot| | rust-digest_auth | 2022-05-06 | 706 | laiot| | rust-binascii| 2022-05-10 | 702 | saluki | | rust-inlinable_string| 2022-05-10 | 702 | decathorpe | | rust-ubyte | 2022-05-10 | 702 | decathorpe | | rust-email-encoding | 2022-05-17 | 695 | saluki | | rust-tabular | 2022-05-23 | 689 | jbtrystram | | rust-async-mutex | 2022-06-01 | 680 | decathorpe | | rust-awc | 2022-06-01 | 680 | decathorpe | | rust-infer | 2022-06-15 | 666 | decathorpe | | rust-escape_string | 2022-07-08 | 643 | dcavalca | | rust-actix | 2022-07-18 | 633 | decathorpe | | rust-envsubst| 2022-07-18 | 633 | jlebon | | rust-esphome | 2022-07-18 | 633 | dcavalca | | rust-fail| 2022-07-18 | 633 | jlebon | |
