Skip to content

Bump MSRV to 1.99 #11475

Open
Open

Description

@oech3

Next Ubuntu LTS adopted Rust 1.93:
#9533 (comment)

Also this is needed for NetBSD CI #11470 (comment)

Activity

  1. Ecordonnier commented on Mar 24, 2026

    @Ecordonnier
    Collaborator

    The next yocto LTS version (released in April 2026) will use rust 1.94, so an update to 1.93 would be OK for yocto consumers of uutils-coreutils.

  2. xtqqczze commented on Mar 24, 2026

    @xtqqczze
  3. xtqqczze commented on Mar 25, 2026

    @xtqqczze
  4. oech3 commented on Apr 11, 2026

    @oech3
    ContributorAuthor

    OpenBSD CI blocks this...

      ## tooling info
      cargo 1.90.0 (840b83a10 2025-07-30) (built from a source tarball)
      rustc 1.90.0 (1159e78c4 2025-09-14) (built from a source tarball)
    
  5. xtqqczze commented on Apr 11, 2026

    @xtqqczze
    Collaborator

    We shouldn't bump MSRV unnecessarily anyway. Could you clarify the purpose of this issue?

  6. oech3 commented on Apr 11, 2026

    @oech3
    ContributorAuthor

    Old toolchain just blocks new features and faster build tools.

  7. xtqqczze commented on Apr 11, 2026

    @xtqqczze
    Collaborator

    We can bump MSRV when it is justified, are there specific features in 1.93 that we could use?

  8. oech3 commented on Apr 11, 2026

    @oech3
    ContributorAuthor

    Currently unsafe assume_init_mut only.

    Also there are some pending renovate PRs.

  9. xtqqczze commented on Apr 11, 2026

    @xtqqczze
    Collaborator

    Currently unsafe assume_init_mut only.

    Also there are some pending renovate PRs.

  10. oech3 commented on Apr 11, 2026

    @oech3
    ContributorAuthor

    todo comments is ugly. Why should we avoid this even next ubuntu lts achieved it?
    uutils is not a library crate and all release binaries are published from main.
    Also there is rustup.

  11. xtqqczze commented on Apr 25, 2026

    @xtqqczze
    Collaborator

    Unless there is a strong justification for raising the MSRV, it should be avoided as it could make backporting more difficult. Let's review bumping MSRV to 1.93 when Ubuntu 25.10 reaches end-of-life (2026-07-01).

  12. oech3 commented on May 19, 2026

    @oech3
    ContributorAuthor

    I'm interested in "if let guard", but it is Rust 1.95+. Too high to bump...

  13. oech3 commented on May 19, 2026

    @oech3
    ContributorAuthor

    if let guard is not an importent example, but cannot Ubuntu LTS backport Rust itself?

  14. xtqqczze commented on Aug 30, 2026

    @xtqqczze
    Collaborator

    OpenBSD CI blocks this...

      ## tooling info
      cargo 1.90.0 (840b83a10 2025-07-30) (built from a source tarball)
      rustc 1.90.0 (1159e78c4 2025-09-14) (built from a source tarball)
    

    OpenBSD CI now has 1.94.1, but I'm still not interested in bumping without a specific use case.

  15. changed the title [-]Bump MSRV to 1.93[/-] [+]Bump MSRV to 1.99[/+] on Oct 2, 2026
  16. oech3 commented on Oct 2, 2026

    @oech3
    ContributorAuthor

    1.99.0 is needed to drop filetime crate.

  17. xtqqczze commented on Oct 5, 2026

    @xtqqczze
    Collaborator

    Path::is_empty is available in Rust 1.98, although not important since we can use path.as_os_str().is_empty().

  18. mattsu2020 commented on Nov 7, 2026

    @mattsu2020
    Contributor

    #16231 (comment)
    Introducing zbus 6 requires raising the MSRV to at least Rust 1.89.

  19. oech3 commented on Nov 7, 2026

    @oech3
    ContributorAuthor

    I prefer 1.93

  20. xtqqczze commented on Nov 7, 2026

    @xtqqczze
    Collaborator

    Introducing zbus 6 requires raising the MSRV to at least Rust 1.89.

    Tracked by #14950.

  21. oech3 commented on Nov 13, 2026

    @oech3
    ContributorAuthor

    1.100 is needed to fix stdbuf #16427 . This is serious packaging issue for downstream.

  22. mitar commented on Nov 13, 2026

    @mitar
    Contributor

    Cargo 1.100 is what breaks make install in #16427, as its new build directory layout has no target/<profile>/deps/ anymore, so requiring it does not fix that issue. In #16427 I mentioned a way for make to work with every cargo version.

    Cargo 1.100 does fix #16422, but that issue only affects test builds in the release profile, which can avoid it with CARGO_PROFILE_RELEASE_PANIC=unwind.

    For downstream: Ubuntu 26.04 builds rust-coreutils with its default rustc 1.93, and the newest versioned rustc it currently has is 1.97, so a minimum Rust version of 1.100 would keep it from building newer uutils releases with its own toolchain.

  23. oech3 commented on Nov 13, 2026

    @oech3
    ContributorAuthor

    Hmm.. I really don't want to have 2 make CI just for this...

  24. xtqqczze commented on Nov 13, 2026

    @xtqqczze
    Collaborator

    Please can we limit discussion on build-dir-new-layout to #16427. I would also propose closing this issue, as it does not appear to be actionable.

  25. oech3 commented on Nov 13, 2026

    @oech3
    ContributorAuthor
  26. xtqqczze commented on Nov 17, 2026

    @xtqqczze
    Collaborator

    I plan to bump to Rust 1.91 shortly, see #16627. If there are any new Rust 1.91 features we can use please mention them there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions