Errors in other crates with egui 0.30.0

[bircni]

Describe the bug
We are getting some linting bugs according to winit:
https://github.com/fluxxcode/egui-file-dialog/actions/runs/12360548656/job/34495753463?pr=221

To Reproduce
Steps to reproduce the behavior:

1. use egui 0.30.0
2. run clippy

[fluxxcode]

According to emilk's comment: #5489 (comment) the wayland feature needs to be enabled for eframe. However, when the feature is enabled, I get the following compiling errors on Arch:

error: failed to select a version for the requirement `egui-wgpu = "^0.30.0"`
candidate versions found which didn't match: 0.29.1, 0.29.0, 0.28.1, ...
location searched: crates.io index
required by package `eframe v0.30.0`
    ... which satisfies dependency `eframe = "^0.30.0"` (locked to 0.30.0) of package `egui-file-dialog v0.7.0 (/home/jannis/projects/egui-file-dialog)`
if you are looking for the prerelease package it needs to be specified explicitly
    egui-wgpu = { version = "0.26.0-alpha.2" }

egui-wgpu:v0.30.0 doesn't seem to be on crates.io yet

[lucasmerlin]

It's definitely there: https://crates.io/crates/egui-wgpu

Maybe try cleaning the cargo cache?

[fluxxcode]

Cache cleared, now showing bytemuck errors:

error: failed to select a version for `bytemuck`.
    ... required by package `wgpu-hal v23.0.1`
    ... which satisfies dependency `hal = "^23.0.0"` of package `wgpu v23.0.0`
    ... which satisfies dependency `wgpu = "^23.0.0"` of package `egui-wgpu v0.30.0`
    ... which satisfies dependency `egui-wgpu = "^0.30.0"` of package `eframe v0.30.0`
    ... which satisfies dependency `eframe = "^0.30.0"` (locked to 0.30.0) of package `egui-file-dialog v0.7.0 (/home/jannis/projects/egui-file-dialog)`
versions that meet the requirements `^1.19` are: 1.20.0, 1.19.0

all possible versions conflict with previously selected packages.

  previously selected package `bytemuck v1.18.0`
    ... which satisfies dependency `bytemuck = "^1.4"` (locked to 1.18.0) of package `tiny-skia-path v0.11.4`
    ... which satisfies dependency `tiny-skia-path = "^0.11.3"` (locked to 0.11.4) of package `usvg-tree v0.37.0`
    ... which satisfies dependency `usvg-tree = "^0.37.0"` (locked to 0.37.0) of package `usvg-parser v0.37.0`

failed to select a version for `bytemuck` which could resolve this conflict

Might also be an issue on my end...

[fluxxcode]

Yes, I thought so. After waiting 5 minutes without doing anything it now works. Maybe it was a bug with crates.io.

Can now compile eframe:v0.30.0 on Arch, with the wayland feature enabled. With that I would say the issue can actually be closed here.

[barries]

Another datapoint: On Ubuntu 22 running in WSL2, bumping egiu, egui_extras and eframe from 0.29 to 0.30 causes this; reverting to 0.29 fixes it. On Windows 11, builds find after a few minor tweaks (like Ui::new() no longer taking a LayerId).

$ cargo build
   Compiling winit v0.30.5
   Compiling foo-ui v0.0.0 (/home/barrie/foo/foo-ui-632)
error: The platform you're compiling for is not supported by winit                                                                                                                                                                            --> /home/barrie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.30.5/src/platform_impl/mod.rs:78:1
   |
78 | compile_error!("The platform you're compiling for is not supported by winit");
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0432]: unresolved import `self::platform`                                                                                                                                                                                              --> /home/barrie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.30.5/src/platform_impl/mod.rs:34:15
   |
34 | pub use self::platform::*;
   |               ^^^^^^^^ could not find `platform` in `self`

error[E0432]: unresolved imports `crate::platform_impl::PlatformCustomCursor`, `crate::platform_impl::PlatformCustomCursorSource`                                                                                                            --> /home/barrie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winit-0.30.5/src/cursor.rs:8:28
  |
8 | use crate::platform_impl::{PlatformCustomCursor, PlatformCustomCursorSource};
  |                            ^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^ no `PlatformCustomCursorSource` in `platform_impl`
  |                            |
  |                            no `PlatformCustomCursor` in `platform_impl`

...

[fluxxcode]

Another datapoint: On Ubuntu 22 running in WSL2, bumping egiu, egui_extras and eframe from 0.29 to 0.30 causes this; reverting to 0.29 fixes it. On Windows 11, builds find after a few minor tweaks (like Ui::new() no longer taking a LayerId).

Do you have the x11 and wayland features enabled for eframe?

[barries]

@fluxxcode:

Do you have the x11 and wayland features enabled for eframe?

Nope, didn't see that in the egui CHANGELOG.md, but it is in the eframe CHANGELOG.md and I just didn't think to check there. Many thanks for the clue-bat!!!