From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] superseded: [PATCH proxmox 1/8] cargo: bump msrv to 1.87
Date: Wed, 10 Dec 2025 11:57:05 +0100 [thread overview]
Message-ID: <s8o345i61vi.fsf@proxmox.com> (raw)
In-Reply-To: <392975f8-252d-4d62-ab8c-adffe591343a@proxmox.com> (Thomas Lamprecht's message of "Wed, 10 Dec 2025 10:02:46 +0100")
Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
> Am 10.12.25 um 09:40 schrieb Maximiliano Sandoval:
>> Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
>>
>>> Am 09.12.25 um 11:53 schrieb Maximiliano Sandoval:
>>>> proxmox-fixed-string uses std::str::from_utf8_unchecked which was
>>>> stabilized on 1.87, see its announcement [1].
>>>>
>>>> [1] https://blog.rust-lang.org/2025/05/15/Rust-1.87.0/
>>>
>>> Shouldn't proxmox-fixed-string then get that msrv bump though?
>>
>> We can do that, but then it becomes a bit unruly to manage a per crate
>> msrv. I'll send a patch doing that.
>
> IMO having to manually track where a dependency that requires higher
> msrv is used is *much* harder and error prone than declaring that relation
> for where it's actually used. I.e., with your patch we're still missing
> PDM, pve-rs, ...?
>
> On the contrary, if you declare dependency info for proxmox-fixed-string,
> then debcargo will automatically generate a d/control dependency relation
> like:
>
> rustc:native (>= 1.87) <!nocheck>,
>
> Thus everything using that as build-dependency will get ensure the
> correct rustc version is installed for all users of that crate, not
> just one.
Superseded-by: https://lore.proxmox.com/all/20251210105615.215532-1-m.sandoval@proxmox.com/
--
Maximiliano
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-12-10 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 10:52 [pbs-devel] " Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 2/8] don't hide a lifetimes that are elided elsewhere Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 3/8] auth-api: remove unnecessary return Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 4/8] deb-version: remove unnecesary vec! call Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 5/8] fixed-string: remove unused import Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 6/8] rest-server: " Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 7/8] http: remove unnecessary conversion Maximiliano Sandoval
2025-12-09 10:52 ` [pbs-devel] [PATCH proxmox 8/8] router: replace clone with std::slice::from_ref Maximiliano Sandoval
2025-12-09 16:22 ` [pbs-devel] [PATCH proxmox 1/8] cargo: bump msrv to 1.87 Thomas Lamprecht
2025-12-10 8:40 ` Maximiliano Sandoval
2025-12-10 9:02 ` Thomas Lamprecht
2025-12-10 10:57 ` Maximiliano Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s8o345i61vi.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox