Would it be possible to upgrade to Plasma 5.17?
Ideally (pending agreement from maintainers), I would like to get this in:
This includes opt-in new behavior for
fetchCargo that makes it much more efficient and possible to cache in hashed mirrors, but at the cost of changing the
cargoSha256 for Rust applications (once opted in). I’m planning on sending a treewide PR that updates all the Rust applications to the new behavior and makes it opt-out once the infra lands, so it’d be nice of the functionality for that new behavior is on the NixOS release so that backporting changes to 20.03 will be easier for maintainers.
Note that the proposed functionality has no functional change to how we build Rust applications, just how we manage the cargo vendor directory.
networking.resolvconf.useHostResolvConf option seems to have been superseeded by
networking.useHostResolvConf and doesn’t do anything anymore.
I think it would be nice to have that fixed for 20.03, as that was quite confusing when figuring out why DNS didn’t work.
Overlayfs instead of unionfs on installation media is long overdue. Every major distribution is using it.
If I read this correctly, the option silently did nothing and now you’ll be warned about that if you use it. What do you suggest to improve? https://github.com/NixOS/nixpkgs/pull/79243/files
Ah, I’m sorry… I didn’t realize the PR happened after you wrote this.
I’m starting to get nervous about https://github.com/NixOS/nixpkgs/pull/77578 and its inclusion in 20.03
It would also be great to include Ungoogled Chromium:
Would be great to get some attention to https://github.com/NixOS/nixpkgs/pull/78453 to get memtest fixed with EFI.
Hello everyone again. Me and @disassembler personal assessment of master right now is it’s very clear for branch off. But we don’t have perfect vision, if there’s anything serious please PM us on IRC or mention us in #nixos-dev.
I plan to begin the beta tasks around 18:30 UTC.
Just want to confirm that 20.03 was branched at the time we said.
I haven’t done the Zero Hydra failure and beta announcement (this is essentially a call for testing), because we ran into an issue with the release-20.03 jobset not evaluating https://github.com/NixOS/nixpkgs/issues/79907. This means hydra isn’t building anything, so that obviously would make any contributions to 20.03 difficult. Anyways, if you have PRs coming into master that has security implications please ping us @NixOS/nixos-release-managers.
If Hydra isn’t evaluating release-20.03 why isn’t unstable also affected, or is it?
It is not evaluating either https://hydra.nixos.org/jobset/nixos/trunk-combined#tabs-errors
Is it too late to consider adding rakudo-2020.01?
https://github.com/NixOS/nixpkgs/pull/76656 was just merged into unstable, I’m worried that 20.03 might release with 2017.01 which is quite outdated.
@sgo if you want something backported, open a PR. Don’t forget to use
@worldofpeace I think it would be great to include into 20.03:
- bump of smartmontools as we currently have 1+ year old version with old devicedb https://github.com/NixOS/nixpkgs/pull/81099
- go 1.14 - it was released yesterday, but there are releases every half a year and we had 1.13 in 19.09, so, it’ll be great to have 1.14 in 20.03 https://github.com/NixOS/nixpkgs/pull/81071
I can do and test backports for them as soon as (if? ) accepted to master.
I can help do some go1.14 testing.
Chiming in that I’d really appreciate NixOS/nixpkgs#81557 getting backported. It’s a pretty simple patch to
/nixos/modules/misc/documentation.nix, and solves what can be a really poignant pain point if hit.
Sorry about the delay in getting this submitted.
3 posts were split to a new topic: 21.05 feature freeze