mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <debian@fabian.gruenbichler.email>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Christian Schrrefl" <chrisi.schrefl@gmail.com>,
	"Russell King" <rmk+kernel@armlinux.org.uk>,
	"Rudraksha Gupta" <guptarud@gmail.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: arm `rustdoc` Rust 1.85.0-only build error
Date: Sat, 25 Jul 2026 19:19:19 +0200	[thread overview]
Message-ID: <18cf2372-0558-4a90-8faa-bdb2ca1cef61@app.fastmail.com> (raw)
In-Reply-To: <CANiq72nFZT0ZZS1R82qVjPg4A=FEU675-3yx+tv3XVA=twnUWQ@mail.gmail.com>

On Fri, Apr 3, 2026, at 12:19 PM, Miguel Ojeda wrote:
> On Fri, Apr 3, 2026 at 10:12 AM Fabian Grünbichler
> <debian@fabian.gruenbichler.email> wrote:
>>
>> I will check how the full diff for 1.85.1 looks like compared to just picking
>> the rustdoc fix referenced above, and then file a stable update request. AFAIU
>> either option works for you?
>
> Thanks for the reply and the details! Yeah, the timing was unfortunate :)
>
> Either works for us, in the sense that it is not a critical issue
> (i.e. it is just for generating the docs and just for arm32).
>
> Having said that, having the actual .1 release there is nicer in that
> we could consider raising the minimum version to that one (or perhaps
> at least print a warning if using .0).
>
> It also means we may get more focused testing and one less version
> around (e.g. currently I found this because I test our minimum, but
> generally I test the latest point versions).

Happy to report (with some delay ;)) that the next stable release of
Debian Trixie (13.7, planned for 12.09.2026) should contain an update
of rustc to 1.85.1, which got accepted into the proposed updates
suite today:

https://tracker.debian.org/news/1778462/accepted-rustc-1851dfsg1-1deb13u1-source-into-proposed-updates/

  reply	other threads:[~2026-07-25 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 19:00 Miguel Ojeda
2026-04-03  8:12 ` Fabian Grünbichler
2026-04-03 10:19   ` Miguel Ojeda
2026-07-25 17:19     ` Fabian Grünbichler [this message]
2026-07-28 19:39       ` Miguel Ojeda
2026-04-03 12:48   ` Gary Guo

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=18cf2372-0558-4a90-8faa-bdb2ca1cef61@app.fastmail.com \
    --to=debian@fabian.gruenbichler.email \
    --cc=ardb@kernel.org \
    --cc=chrisi.schrefl@gmail.com \
    --cc=guptarud@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rust-for-linux@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®