Update async-global-executor dependency

[werdahias]

No description provided.

[agx]

@samcday would it make sense to switch deps 3.0 to give distros some leeway in micro versions? We're doing that in xdg-desktop-portal-phosh and pfs too.

[a-wai]

FWIW this wouldn't be needed 3.0.0 is actually interpreted as >= 3.0.0, < 4

[agx]

Ah right, I thought 3.0 would give us >= 3.0.x but <= 3.1.0 but it doesn't (https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html)

[github-actions]

The CI build recorded and generated some videos

Demo video (shown on README and release notes)

accent-colours

emergency-calls

first-run

simple-flow

trivial-flow

[samcday]

Apologies for the delay here. Thanks for the contributions ya'll 🙏

[samcday]

@werdahias / @a-wai / @agx maybe one of ya'll could help teach me the ways of the Debian, here? After merging this PR I decided to try and get phrog building .debs as part of upstream CI (#138).

It seems that the async-global-exec crate is still 2.x even on unstable. So I picked experimental but I'm getting really cursed depsolver issues that make me think phrog should maybe not be playing in that sandpit 😅

So I guess a specific question is: what's the best way to ensure phrog upstream stays in sync with Debian? Feel free to drop any thoughts on that linked PR :)

[agx]

So I guess a specific question is: what's the best way to ensure phrog upstream stays in sync with Debian?

I'm not much of a Rust person so I'll just say what we're doing in other packages:

• Be conservative with crate dependencies, the fewer the better. If possible don't depend on most recent features. This is done to ease distro maintainers life
• Don't specify the Rust crates in the dependencies by default as our aim is not to test the build in Debian but provide a package that matches closely what the developer committed.

If one wants to do perform both a crates.io and a build with crates using Debian packages one can use build profiles.

[a-wai]

It seems that the async-global-exec crate is still 2.x even on unstable. So I picked experimental [...]

Actually v3 was uploaded to unstable yesterday, and is now available there ;) Regarding your issue, it could be due to a dependency confict, e.g. another crate explicitly depending on async-global-exec v2. The best way to be sure would be to try installing all build-deps manually in a container

So I guess a specific question is: what's the best way to ensure phrog upstream stays in sync with Debian? Feel free to drop any thoughts on that linked PR :)

I'd just stick with unstable for CI, and maybe mark it as "allowed to fail" as there will be issues with broken dependency chain from time to time