Florian Klink

/remove-lifecycle rotten

/remove-lifecycle rotten

[nixpkgs](https://github.com/nixos/nixpkgs) also ships these patches downstream to fix their builds. IIRC, this so far wasn't merged as CI uses 16.04 to generate an AppImage, which is using a super old...

I rebased this to latest `master` - the conflict was fairly trivial. I also opened https://github.com/GoldenCheetah/GoldenCheetah/pull/4119, which only contains https://github.com/GoldenCheetah/GoldenCheetah/commit/1e089e3abd270f86f6a00b66e608cd837c8e6430 (so doesn't update CI to a more recent bison version).

@amtriathlon merging in 1e089e3 only also doesn't work, as it'll break the windows CI.

> Thanks, but we've decided to skip the lock file for now until the code is more stable, as they mostly generate merge conflicts at the moment sweat_smile. Do you...

I had someone else opening a nixpkgs PR packaging iroh, and they also had to manually provide a Cargo.lock file: https://github.com/NixOS/nixpkgs/pull/198678#pullrequestreview-1161173069 With the 0.1.0 release now out, would you reconsider...

I don't have 1.13 provided anymore in my distribution. Should this line succeed with other Go versions, like 1.15 or 1.16 too? Further looking at the `config.yml`, where is `uroottest/test-image-amd64:v3.2.13`...

> 1.15 def. I was just discovering some other 1.16 issues earlier, so I doubt 1.16 works right now. Yeah, I was just confused by the readme explicitly mentioning 1.13....

Is there some tracking issue/wip branch for this? I tried [banging my head against getting a build pipeline for GitHub Actions](https://github.com/flokli/u-root/pull/1), but even in the unit tests there's various places...