bugfix : problems with compiling ron and base64 on nix rustc 1.92.0-nightly (839222065 2025-10-05)

[jmikedupont2]

using a recent compiler nix rustc 1.92.0-nightly (839222065 2025-10-05) on nix with latest version of ron (because of base64 also breaking)

Compiling config v0.15.18 (/data/data/com.termux.nix/files/home/pick-up-nix2/vendor/nix/cargo2nix/vendor/config-rs)
error[E0599]: no variant or associated item named `Float` found for enum `ron::Number` in the current scope
  --> src/file/format/ron.rs:30:26
   |
30 |             ron::Number::Float(value) => ValueKind::Float(value.get()),
   |                          ^^^^^ variant or associated item not found in `ron::Number`

error[E0599]: no variant or associated item named `Integer` found for enum `ron::Number` in the current scope
  --> src/file/format/ron.rs:31:26
   |
31 |             ron::Number::Integer(value) => ValueKind::I64(value),
   |                          ^^^^^^^ variant or associated item not found in `ron::Number`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `config` (lib) due to 2 previous errors

[epage]

This is titled "bugfix" but it isn't clear what the bug is. The change looks instead like an attempt at an upgrade but seems incomplete (since using a git dep).

Could you please clarify what is going on. Note that we generally ask for this to be done in an issue and get buy-in on a solution before posting a PR.

[jmikedupont2]

Yes sorry I thought I included the error and the patch basically there's a Cascade of patches where Ron is using a broken version of base64 and I had to upgrade all of them and make changes to all of them to get it to compile with the latest compiler I'll provide more details in a minute

…

On Tue, Nov 11, 2025, 20:39 Ed Page ***@***.***> wrote: *epage* left a comment (rust-cli/config-rs#713) <#713 (comment)> This is titled "bugfix" but it isn't clear what the bug is. The change looks instead like an attempt at an upgrade but seems incomplete (since using a git dep). Could you please clarify what is going on. Note that we generally ask for this to be done in an issue and get buy-in on a solution before posting a PR. — Reply to this email directly, view it on GitHub <#713 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5KQ2KPGTRY5KZ7AN3T2DL34KFT3AVCNFSM6AAAAACL2RHYAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMJZGQ4DIMBVGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jmikedupont2]

see ron-rs/ron#590
and marshallpierce/rust-base64#290

/nix/store/k0db47fx7mdl8bajzhk05x8414gf5w03-rustc/bin/rustc --version
rustc 1.92.0-nightly (839222065 2025-10-05)

[epage]

That is a warning, why does it matter?

[jmikedupont2]

error[E0599]: no variant or associated item named Integer found for enum ron::Number in the current scope
--> src/file/format/ron.rs:31:26

This is an error :
error[E0599]: no variant or associated item named Integer found for enum ron::Number in the current scope
--> src/file/format/ron.rs:31:26

[jmikedupont2]

So this works for me, it was blocking me, hopefullly it helps the next poor man down the line

[epage]

I'm assuming that error isn't what you would see with our published packages but from upgrading to an incompatible version of ron to upgrade base64 to resolve a warning.

I'm asking why that warning in base64 that started this matters. It is a regular occurrence for rustc upgrades to show new lints. This isn't a dance that is practical to go through for every package everytime. Cargo actually silences warnings from dependencies through a "cap lint" feature in the compiler.

[jmikedupont2]

I don't know but it was blocking my build you know if it's not an issue then you can ignore you can close it it's not a problem I'm just trying to be a good citizen here I'm going to downgrade the compiler to an older version

…

On Tue, Nov 11, 2025, 22:22 Ed Page ***@***.***> wrote: *epage* left a comment (rust-cli/config-rs#713) <#713 (comment)> I'm assuming that error isn't what you would see with our published packages but from upgrading to an incompatible version of ron to upgrade base64 to resolve a warning. I'm asking why that warning in base64 that started this matters. It is a regular occurrence for rustc upgrades to show new lints. This isn't a dance that is practical to go through for every package everytime. Cargo actually silences warnings from dependencies through a "cap lint" feature in the compiler. — Reply to this email directly, view it on GitHub <#713 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5KQ2MQ3H6ZIERCJHVNLTL34KRZFAVCNFSM6AAAAACL2RHYAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMJZG4YTSOJRG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>