[pull] master from NixOS:master #84
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
The web UI directory was renamed from transmission/web in 3.00 [1] to transmission/public_html in 4.0.0 [2]. This change updates the AppArmor rules to fix the web UI when AppArmor is enabled. [1]: https://github.com/transmission/transmission/blob/3.00/libtransmission/platform.c#L627 [2]: https://github.com/transmission/transmission/blob/4.0.x/libtransmission/platform.cc#L324
This change adds an extraAppArmorPaths option to the transmission_4 derivation to allow additional read-only paths to be added to the ppArmor rules. This can be combined with the TRANSMISSION_WEB_HOME environment variable to override the web UI.
With the update to libtiff 4.6 in 0a74a54 , many tiff-processing utility executables got dropped: http://www.simplesystems.org/libtiff/releases/v4.6.0.html Some of these executables can still be "restored" with the configure switch `--enable-tools-unsupported`, but unfortunatelly, at least hylafaxplus (maybe more packages) relies on utilities that even cannot be restored with this switch. The commit at hand reintroduces the old libtiff version 4.5.1 as `libtiff_4_5` into nixpkgs. It restores the old build recipe with the following changes: * passthru.updateScript is dropped as it is of no use here * passthru.tests is dropped as it only contains packages that now build with the new libtiff version * patches are applied for the two CVEs that are fixed in 4.6.0 As libtiff 4.5 is no longer supported by libtiff developers, new vulnerabilities will likely go unnoticed unless they also affect the current version. To not disable hydra builds, we don't add `knownVulnerabilities` *for now*, but add comments to alert updaters of the current libtiff version so patches can be backported or the situation be reevaluated as a whole.
libtiff 4.6.0 (updated with 0a74a54) drops many tiff-processing utility executables, like tiff2ps and fax2ps, that are needed by hylafaxplus. As a result, the build fails with > FATAL ERROR: /nix/store/5i80biwsgjb4yhp4z81nsk3kp5rivd8f-libtiff-4.6.0-bin/bin/tiff2ps does not exist or is not an executable program! see https://hydra.nixos.org/build/239580858 . The commit at hand fixes the package by using libtiff_4_5 which got introduced in the previous commit. Note on long-term prospect for this situation: According to hylafaxplus developer Lee Howard, it might take months before one of these options (or a combination thereof) might be implemented: * a new package "tifftools" with the utility executables emerges * The hylafaxplus package incorporates the source of these executables and builds them by itself * hylafaxplus is rewritten so as to not use these programs * libtiff reincorporates the programs, maybe after fixing them Cf. https://sourceforge.net/p/hylafax/mailman/message/38259441/ Another reference: a discussion on the libtiff mailing list: https://www.asmail.be/msg0054915176.html
https://github.com/thanos-io/thanos/releases/tag/v0.32.0 https://github.com/thanos-io/thanos/releases/tag/v0.32.1 https://github.com/thanos-io/thanos/releases/tag/v0.32.2 https://github.com/thanos-io/thanos/releases/tag/v0.32.3 https://github.com/thanos-io/thanos/releases/tag/v0.32.4 Co-authored-by: Jonathan Davies <[email protected]>
gpxsee: 13.10 -> 13.11
rio: fix Darwin build and move cmake to Linux nativeBuildInputs
python311Packages.kombu: 5.3.3 -> 5.3.4
`lib.fileset`: Minor changes
Bump Typst tools and VSCode extension
transmission_4: update AppArmor rules
fossil: 2.22 -> 2.23
python311Packages.nettigo-air-monitor: refactor
terragrunt: 0.53.2 -> 0.53.4
turso-cli: 0.87.2 -> 0.87.4
cljfmt: init at 0.11.2
…-to-1.1.0 clipqr: 1.0.1 -> 1.1.0
argocd: 2.8.5 -> 2.9.1
go-ethereum: 1.13.4 -> 1.13.5
subtitleedit: 4.0.1 -> 4.0.2
buildMozillaMach: add options to disable signing requirement and to enable addon sideloading
…s.weasel python310Packages.weasel: 0.3.3 -> 0.3.4
dbmate: 2.7.0 -> 2.8.0
…s.umap-learn python311Packages.umap-learn: 0.5.4 -> 0.5.5
…s.pvextractor python310Packages.pvextractor: 0.3 -> 0.4
nixos/dockerTools: fixup proot/fakeroot code (fixes dockertools nixos test)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )