-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
staging-next: 21.11 iteration 1 #144730
staging-next: 21.11 iteration 1 #144730
Conversation
polkit: fix musl build
Current release lacks dependencies on local espeak-ng: cd dictsource && ESPEAK_DATA_PATH=/build/espeak-ng LD_LIBRARY_PATH=../src: \ ../src/espeak-ng --compile=yue && cd .. bash: line 1: ../src/espeak-ng: No such file or directory Should be fixed in next release: espeak-ng/espeak-ng#1029 Can't apply patch as is as Makefile.am diverged quite a bit since 1.50 release.
* FluidSynth 1.1.11 was kept around as a dependency of some packages that hadn't yet adjusted to API breakages. All of these packages now use FluidSynth 2.x, so fluidsynth_1 can be removed. It has been broken ever since glib was updated to 2.70 and was affected by an unpatched CVE. * Refactor expression a bit, use pname instead of name. * Add changelog entry in case someone was using this downstream (accidentally?). Fixes #141508. Fixes #124624.
espeak-ng: explicitly disable parallel building
Co-authored-by: Zak B. Elep <[email protected]>
Co-authored-by: Sandro <[email protected]>
protobuf: 3.18.0 -> 3.19.0
glib: follow profile updates when searching apps
libvpx: 1.10.0 -> 1.11.0
Signed-off-by: Felix Singer <[email protected]>
This contains the fix for build error with bision 3.8. See https://gerrit.libreoffice.org/c/core/+/122082
Looks like we are a day behind on this. Anything holding up the merge? I'd like to help get this merged by EOD at least, if possible. |
Regarding that issue, it seems like there is some approval for a fix: #145459 (3 hours ago) that should ideally be merged into staging-next. |
Hydra's take on this, though some new failures were apparently temporary and will disappear on restart: https://hydra.nixos.org/eval/1721869?compare=1721771 I noticed the libreoffice regression mentioned a bit above, too. Nothing else stood out to me, though in the comparison there still are over 10k unfinished builds. |
Currently `clangUseLLVM` is broken since it uses libcxx and compiler-rt but also specifies `--gcc-toolchain`, which leads to weird compile errors when including C++ headers.
It was my third time attempting to review it. if there are flakey builds then it's possible i just got lucky a few times. |
[staging-next] libreoffice*: update and fix build
This reverts commit c7aef6d. I believe it should work again since today, though I'm being a bit conservative, pushing to `staging-next` instead of `master`.
This comment has been minimized.
This comment has been minimized.
Runs on my systems just fine now. Firefox and Thunderbird work as well.
|
https://hydra.nixos.org/eval/1722344?compare=1722301#tabs-now-fail We're certainly not perfect, but to me this PR seems OK for |
Another staging-next iteration. Documentation here: https://nixos.org/manual/nixpkgs/stable/#submitting-changes-staging-next-branch
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
Per the release schedule we are still restricted to non-breaking changes to release critical packages, and the plan is to merge in about a week (Nov 12).
Next staging-next: #146259