Releases retrieved: 0.10.0 Upstream release that is considered latest: 0.10.0 Current version/release in rawhide: 0.9.1-2.fc37 URL: http://ziglang.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/13871/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/zig
The update is still in progress behind the scenes, even if its slow. Here is how I plan things to go: - 0.10.0 (or newer) will be proposed for Fedora 39 - Fedora 38 and older will stay on 0.9.1 because 0.10.0 introduced the self hosted compiler and with that a lot of breakage (which is allegedly why river took so long to update) - more work will be invested into getting all patches submitted upstream in a form that will not cause issues with other distros (previous patch has broken Nix compatibility) - spec file will be improved to allow for compat builds, so that in the future versioned releases of Zig can be created for packages that are struggling to update. while its being worked on irregular copr builds can be found here: https://copr.fedorainfracloud.org/coprs/sentry/zig/
Releases retrieved: 0.10.1 Upstream release that is considered latest: 0.10.1 Current version/release in rawhide: 0.9.1-2.fc37 URL: http://ziglang.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/13871/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/zig
(In reply to Jan Drögehoff from comment #1) > The update is still in progress behind the scenes, even if its slow. > > Here is how I plan things to go: > - 0.10.0 (or newer) will be proposed for Fedora 39 > - Fedora 38 and older will stay on 0.9.1 because 0.10.0 introduced the self > hosted compiler and with that a lot of breakage (which is allegedly why > river took so long to update) Thanks for working on that and for sharing the detailed plan! Fedora 38 is still in development though. Is it really too late to update it to zig 0.10.1? All the packages I maintain either in copr or in Fedora (river, waylock, ncdu2) already require 0.10.x :( > while its being worked on irregular copr builds can be found here: > https://copr.fedorainfracloud.org/coprs/sentry/zig/ Any chance you could fix builds for f36 and f38? It would allow me to unblock the copr package updates.
(In reply to Aleksei Bavshin from comment #3) > (In reply to Jan Drögehoff from comment #1) > > The update is still in progress behind the scenes, even if its slow. > > > > Here is how I plan things to go: > > - 0.10.0 (or newer) will be proposed for Fedora 39 > > - Fedora 38 and older will stay on 0.9.1 because 0.10.0 introduced the self > > hosted compiler and with that a lot of breakage (which is allegedly why > > river took so long to update) > > Thanks for working on that and for sharing the detailed plan! > > Fedora 38 is still in development though. Is it really too late to update it > to zig 0.10.1? All the packages I maintain either in copr or in Fedora > (river, waylock, ncdu2) already require 0.10.x :( Fedora 38 is already past the proposal deadline, and I don't wish to push anything in beyond that. Zig 0.10.0 would have fit into that deadline but with River, the (as far as I know) only package that depends on Zig in Fedora, taking a bit to update, because of breaking changes the self hosted compiler introduced, I could not manage to patch Zig to build sanely on Fedora. Patching Zig has proven to not be as trivial as hoped. There is a lot of stuff Zig assumes or does that is incompatible with how Fedora functions, like their handling of libraries, rpaths, build id's, etc. My goal is to get these changes into Zig itself so that other developers and maintainers can make use of them, without breaking anything in the process (notably their Nix support, which happened on the original rpath patch) Zig 0.10.0 could be introduced to Fedora 38 at a later point but I'll have to see how much the self hosted compiler actually breaks. > > while its being worked on irregular copr builds can be found here: > > https://copr.fedorainfracloud.org/coprs/sentry/zig/ > > Any chance you could fix builds for f36 and f38? It would allow me to > unblock the copr package updates. I think I can fix f38, but f36 would not be possible because of LLVM. If Fedora 36 is needed I can make a compat build of LLVM 15 for it, I've made contributions to the llvm and lld specs to make that possible.
> Fedora 38 is already past the proposal deadline, and I don't wish to push anything in beyond that. That makes sense. > Zig 0.10.0 would have fit into that deadline but with River, the (as far as I know) only package > that depends on Zig in Fedora, taking a bit to update, because of breaking changes the > self hosted compiler introduced, I could not manage to patch Zig to build sanely on Fedora. AFAIK, Isaac's main blocker for river was wlroots 0.16.1. zig 0.10 changes took less than a week to prepare. I can ask him if river could be patched for compatibility when the next breaking update of zig happens. Otherwise I'm fine with having river FTBFS until the next upstream release, as long as it installs. > If Fedora 36 is needed I can make a compat build of LLVM 15 for it, I've made contributions > to the llvm and lld specs to make that possible. No, if that's the problem then it's fine. I don't use f36 and it will be EOL in a few months anyways, no need to bother. Again, thanks for working on that!
(In reply to Jan Drögehoff from comment #4) > Zig 0.10.0 would have fit into that deadline but with River […] Small correction to this: System Wide Changes ended back on 2022-12-27, before the first River release that supported 0.10.0. (In reply to Aleksei Bavshin from comment #5) > AFAIK, Isaac's main blocker for river was wlroots 0.16.1. zig 0.10 changes > took less than a week to prepare. It might have been that. I'm going off from what I've been told, which may very well be wrong. -- Zig 0.10.0 builds for Fedora 37 and rawhide (to be 38) are on copr now. I haven't had time to look at Zig 0.10.1 now, are there are any breaking changes that would require it?
Been a while but I wanted to give an update on whats been done since the previous comment: There is now proper build-id support https://github.com/ziglang/zig/pull/15459 An alternative fix for rpaths has been made https://github.com/ziglang/zig/pull/15292, though it was received no attention so far. I've also gone ahead and locally refactored the spec to allow compat builds, which may be very useful in the future since LLVM, Zig and Fedora are all running on a different schedule. From what I have heard a release was delayed to the end of the month, which is right after the system wide change deadline. I'll have to look into if its worth proposing a change before the release.
(I had actually written this almost a week ago but apparently it got lost) Update on the situation: No System Wide proposal was made: the 0.11 release was pushed back to mid July (maybe more in the future) Fixes in regards to rpaths were merged (it then broke rpaths to local LLVM prefixes, though that does not affect Fedora) Work is being done to decouple Zig more from LLVM (https://github.com/ziglang/zig/issues/16270) (I suggest not getting evolved in that discussion since it has devolved completely out of control, Zig will not drop LLVM any time soon and the plan for the longest time was to make LLVM an optional component) this could potentially make Zig easier to package, if keeping up with LLVM and Fedora proves to be a problem. Though as we go on this should become a lesser problem because the major tasks are being completed.
Releases retrieved: 0.11.0 Upstream release that is considered latest: 0.11.0 Current version/release in rawhide: 0.9.1-4.fc39 URL: http://ziglang.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/13871/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/zig
Note that the llvm13/clang13/lld13 packages used by the current zig package have been opened, and that zig 0.11 upgrades to LLVM 16[1]. [1] https://ziglang.org/download/0.11.0/release-notes.html#LLVM-16
Maybe 0.12 for Fedora 40?
zig 0.11 is not available in Fedora 40 and rawhide. (In reply to Jens Petersen from comment #11) > Maybe 0.12 for Fedora 40? I'm not confident in Zig 0.12 being released before Fedora 40.