jiebi/CodeConvo huggingface dataset:
Change:
, CVSSv3=7.5 (nixos-21.11) Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds. Scanned versions: nixos-21.11: . Cc

Discussion:
, buildPythonPackage , fetchPypi , pythonOlder <del> , pythonAtLeast </del> , pythonRelaxDepsHook , writeText , asttokens

, sphinx_rtd_theme , pytest-runner , setuptools-scm <ins> , git </ins> }: let

in buildPythonPackage rec { pname = "vyper"; <del> version = "0.3.1"; </del> <ins> version = "0.3.3"; </ins> format = "setuptools"; <del> disabled = pythonOlder "3.7" || pythonAtLeast "3.10"; </del> <ins> disabled = pythonOlder "3.7"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "sha256-fXug5v3zstz19uexMWokHBVsfcl2ZCdIOIXKeLVyh/Q="; </del> <ins> sha256 = "sha256-BAnNj27B1HAb9VVDA69bFGbQjeOpl0g5EB2juajqBAw="; </ins> }; nativeBuildInputs = [ <ins> # Git is used in setup.py to compute version information during building # ever since https://github.com/vyperlang/vyper/pull/2816 git </ins> pythonRelaxDepsHook pytest-runner setuptools-scm
Change:
giara fails to start but merely prints a python backtrace. Steps to reproduce the behavior: $ or add "" to and rebuild the system $ giara Start up the graphical reddit client. Add any other context about the problem here.
Thanks for reporting and sorry for the answering delay. I have looked into it and there is no easy fix for version 1.0 and version 1.0.1 requires a new dependency which is not yet in nixpkgs. I'll take a second look at it when time allows.
Yeah, the package requires an older version of libadwaita. And 1.0.1 requires

Discussion:
, glib-networking , libadwaita , appstream <ins> , blueprint-compiler </ins> }: python3.pkgs.buildPythonApplication rec { pname = "giara"; <del> version = "1.0"; </del> <ins> version = "1.0.1"; </ins> format = "other";

owner = "World"; repo = pname; rev = version; <del> hash = "sha256-xDIzgr8zYal0r0sASWqiSZANCMC52LrVmLjlnGAd2Mg="; </del> <ins> hash = "sha256-hKaniW+bbuKUrETMQGWwvC2kyudK9tCE/R69dOFzdQM="; </ins> }; nativeBuildInputs = [

pkg-config ninja wrapGAppsHook4 <ins> blueprint-compiler </ins> ]; buildInputs = [

beautifulsoup4 ]; <del> patches = [ # Proper support for gtk4 and libadwaita # @TODO: Remove when bumping the version. (fetchpatch { name = "giara-gtk4-libadwaita.patch"; url = "https://gitlab.gnome.org/World/giara/-/commit/6204427f8b8e3d8c72b669717a3f129ffae401d9.patch"; sha256 = "sha256-E8kbVsACPD2gkfNrzYUy0+1U7+/pIkUu4rCkX+xY0us="; }) ]; </del> postPatch = '' substituteInPlace meson_post_install.py  --replace "gtk-update-icon-cache" "gtk4-update-icon-cache"
Change:
The field of the ddclient service is world-readable but this is not made clear in the field description. The description should be updated to note this insecurity.
In general, having a (or other secret) field anywhere in NixOS modules/config feels like a bit of a no-no.

Discussion:
# TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio

description = "View and analyse contents of music audio files"; homepage = http://www.sonicvisualiser.org/; license = "GPLv2"; <del> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </del> <ins> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </ins> platforms = stdenv.lib.platforms.linux; }; }
Change:
This bug is very recent, within the last day or two, but affects both unstable and master. Whan I attempt to build , it first fails with this compilation error:
is the last version of that built for me.
Here is the commit that broke the build on my system:
Since it was using an old version of OpenSSL, could LibreSSL be used as a replacement? Isn’t that what Apple ships anyway?
with : Haven't yet rebuilt more than that, but it seems like it may generally be the fix.

Discussion:
{ lib, appleDerivation, xcbuildHook <del> , openssl, Librpcsvc, xnu, libpcap, developer_cmds }: </del> <ins> , libressl, Librpcsvc, xnu, libpcap, developer_cmds }: </ins> appleDerivation { nativeBuildInputs = [ xcbuildHook ]; <del> buildInputs = [ openssl xnu Librpcsvc libpcap developer_cmds ]; </del> <ins> buildInputs = [ libressl xnu Librpcsvc libpcap developer_cmds ]; </ins> NIX_CFLAGS_COMPILE = " -I./unbound -I${xnu}/Library/Frameworks/System.framework/Headers/";
Change:
golangci-lint on unstable does not build on darwin-x8664. This seems to have been caused by which switched the go version from 1.17 to 1.18 (to fix another (runtime) bug!) See hydra: FYI (sorry to ping but not really sure who else I would ask) - author/merger of - arbitrary maintainer
I think the issue is related to this commit in upstream go Also upstream issue for which that commit was introduced
The stdenv we use for is too old, currently it's 10.12. It failed to build in , it should have been marked as broken then. e.g.
I'm a bit new to nixos, is that declaration used just for the documentation purposes or it may force to build the derivation locally if conditions are met?
if you need it to build locally in the meantime you can create an overlay like this And if you're using , you can configure or inline it like
Unfortunately golangci-lint breaks with Go 1.18 projects if it's built with 1.17 at the moment, so this only works if you run it in a 1.17 project.
Are there any plans to update Apple SDK on x86_64-darwin? I've been dealing with a lot of pain recently using Nix on Darwin because of that.
There is an open issue about updating the SDK: You can try the above comment for changing the Go version back to 1.17. An alternative is using a prebuilt version of golangci-lint. For example: (Note: it's not a very nice solution, but works for the moment)

Discussion:
homepage = "https://golangci-lint.run/"; license = licenses.gpl3Plus; maintainers = with maintainers; [ anpryl manveru mic92 ]; <del> broken = stdenv.isDarwin && stdenv.isx86_64; </del> }; }
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.2.1 desired version: 2.2.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
let pname = "heroic"; <del> version = "2.2.1"; </del> <ins> version = "2.2.6"; </ins> name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases/download/v${version}/Heroic-${version}.AppImage"; <del> sha256 = "sha256-zzxf3eM1fUWTVtzzABcwlmptNuCVQafvotnbOiCzu0c="; </del> <ins> sha256 = "sha256-kL30/G4DpDPwGN7PvbWest7TcgL4Rd1c2OM4nRCT3bg="; </ins> }; appimageContents = appimageTools.extractType2 { inherit name src; };
Change:
Multiple packages are broken over using links which are temporary. Some directly refer to a specific mirror so they succeed so long as the server isn't down-throttled by sourceforge. Others are completely broken. The correct syntax for sourceforge source packages should be "mirror://sourceforge/...". The following is a partial list compiled from git grep | grep tar and some light manual editing. It might have false negatives and there could be other offending packages that aren't listed: Also note that occasionally sourceforge crashes to "disaster recovery mode" and requires javascript to download tarballs.
Is adding a travis check to prevent addition of links a good idea?
The problem is that is actually the official way to download tarballs from SourceForge. What makes it so unreliable is the same ticketing and load-balancing system SourceForge wants us to use... That's to say, before modifying travis, the list in pkgs/build- should be edited to start with the official to give SF a chance to regulate itself, and only fallback on the known servers list if the download fails or hangs.
No wonder people don't like SF. :/ Okay, I'm opening a new PR to update mirrors. Will follow up with editing out the links to use mirrors, and then add a travis job to enforce the convention.
We actually lucked out here. Windows users get their binaries packed with extra malware... Sounds great :) I'll close this issue now that you're on it. Thanks!

Discussion:
# SourceForge. sourceforge = [ <ins> http://downloads.sourceforge.net/ </ins> http://prdownloads.sourceforge.net/ http://heanet.dl.sourceforge.net/sourceforge/ http://surfnet.dl.sourceforge.net/sourceforge/
Change:
A number of dependencies which are technically optional (but without which some features don't work) appear to be missing from the SickRage package: (Presumably this requires some Python package?) (Presumably this requires ?) Steps to reproduce the behavior: SickGear from nixpkgs subtitle fetching a show with subtitles enabled at regular logs (for the subtitle warning) and error logs (for the rar error) I'm not entirely sure when or why SickGear fetches the file, but I think the subtitle fetch is attempted when a show episode is being searched for. Features should work out of the box. N/A N/A Please run and paste the result. Note: SickGear is installed from , even though I am running stable.
The only problem I can see is that unrar is unfree.... Just looking through the , it looks like it can also use bsdtar from libarchive.... so I'm not sure the best way to handle it.
Maybe you can test out

Discussion:
<ins> From e97f418803c1db9a753fa755a9ee0cf04eabaed3 Mon Sep 17 00:00:00 2001 From: rembo10 <rembo10@users.noreply.github.com> Date: Sun, 11 Sep 2022 13:00:29 +0530 Subject: [PATCH] Allow running on unsupported Python versions --- sickgear.py | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/sickgear.py b/sickgear.py index 9d0440bb..6d65e65d 100755 --- a/sickgear.py +++ b/sickgear.py @@ -43,10 +43,7 @@ versions = [((2, 7, 9), (2, 7, 18)), ((3, 7, 1), (3, 8, 14)), ((3, 9, 0), (3, 9, 2)), ((3, 9, 4), (3, 9, 14)), ((3, 10, 0), (3, 10, 7))]  # inclusive version ranges if not any(list(map(lambda v: v[0] <= sys.version_info[:3] <= v[1], versions))) and not int(os.environ.get('PYT', 0)): -    print('Python %s.%s.%s detected.' % sys.version_info[:3]) -    print('Sorry, SickGear requires a Python version %s' % ', '.join(map( -        lambda r: '%s - %s' % tuple(map(lambda v: str(v).replace(',', '.')[1:-1], r)), versions))) -    sys.exit(1) +    pass sys.path.insert(1, os.path.abspath(os.path.join(os.path.dirname(__file__), 'lib'))) is_win = 'win' == sys.platform[0:3] -- 2.37.2 </ins>

<del> { lib, stdenv, fetchFromGitHub, python3, makeWrapper }: </del> <ins> { lib, stdenv, fetchFromGitHub, python3, makeWrapper, libarchive }: </ins> let <del> pythonEnv = python3.withPackages(ps: with ps; [ cheetah3 ]); </del> <ins> pythonEnv = python3.withPackages(ps: with ps; [ cheetah3 lxml ]); </ins> in stdenv.mkDerivation rec { pname = "sickgear"; <del> version = "0.25.35"; </del> <ins> version = "0.25.40"; </ins> src = fetchFromGitHub { owner = "SickGear"; repo = "SickGear"; rev = "release_${version}"; <del> sha256 = "0hc43wfa256nkjm7bvsr6b7xsyilm1ks4x16kvpprqmj1symlkz3"; </del> <ins> sha256 = "sha256-AHV/HSKuVWZFdZdkFp9p7okAcFO40d9OqV20MaHKXaU="; </ins> }; <ins> patches = [ ./patches/override-python-version-check.patch ]; </ins> dontBuild = true; doCheck = false; nativeBuildInputs = [ makeWrapper ]; <del> buildInputs = [ pythonEnv ]; </del> <ins> buildInputs = [ pythonEnv libarchive ]; </ins> postPatch = '' substituteInPlace sickgear.py --replace "/usr/bin/env python2" "/usr/bin/env python"
Change:
Build of failed on x86_64-linux as of . This is currently breaking maintainers cc: aws-sdk-cpp maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag: -
Managed to bisect this down to would you mind taking a look?
Sure thing
There are commits between the release on nixpkgs (1.9.150) and the latest release (1.9.238) that fixes gcc11 / c++17 issues. : Testing building latest release; if it isn't something that can be considered (incompatibilities?) then adding them as patches should work.

Discussion:
<del> { lib, stdenv, fetchFromGitHub, fetchpatch, cmake, curl, openssl, s2n-tls, zlib </del> <ins> { lib , stdenv , fetchFromGitHub , cmake , curl , openssl , s2n-tls , zlib </ins> , aws-crt-cpp <del> , aws-c-cal, aws-c-common, aws-c-event-stream, aws-c-io, aws-checksums , CoreAudio, AudioToolbox </del> <ins> , aws-c-cal , aws-c-common , aws-c-event-stream , aws-c-io , aws-checksums , CoreAudio , AudioToolbox </ins> , # Allow building a limited set of APIs, e.g. ["s3" "ec2"]. apis ? ["*"] , # Whether to enable AWS' custom memory management.

stdenv.mkDerivation rec { pname = "aws-sdk-cpp"; <del> version = "1.9.150"; </del> <ins> version = "1.9.238"; </ins> src = fetchFromGitHub { owner = "aws"; repo = "aws-sdk-cpp"; rev = version; <del> sha256 = "sha256-fgLdXWQKHaCwulrw9KV3vpQ71DjnQAL4heIRW7Rk7UY="; </del> <ins> sha256 = "sha256-pEmsTfZXsvJMV79dGkjDNbUVajwyoYgzE5DCsC53pGY="; </ins> }; postPatch = '' <ins> # Missing includes for GCC11 sed '5i#include <thread>' -i  aws-cpp-sdk-cloudfront-integration-tests/CloudfrontOperationTest.cpp  aws-cpp-sdk-cognitoidentity-integration-tests/IdentityPoolOperationTest.cpp  aws-cpp-sdk-dynamodb-integration-tests/TableOperationTest.cpp  aws-cpp-sdk-elasticfilesystem-integration-tests/ElasticFileSystemTest.cpp  aws-cpp-sdk-lambda-integration-tests/FunctionTest.cpp  aws-cpp-sdk-mediastore-data-integration-tests/MediaStoreDataTest.cpp  aws-cpp-sdk-queues/source/sqs/SQSQueue.cpp  aws-cpp-sdk-redshift-integration-tests/RedshiftClientTest.cpp  aws-cpp-sdk-s3-crt-integration-tests/BucketAndObjectOperationTest.cpp  aws-cpp-sdk-s3-integration-tests/BucketAndObjectOperationTest.cpp  aws-cpp-sdk-s3control-integration-tests/S3ControlTest.cpp  aws-cpp-sdk-sqs-integration-tests/QueueOperationTest.cpp  aws-cpp-sdk-transfer-tests/TransferTests.cpp </ins> # Flaky on Hydra rm aws-cpp-sdk-core-tests/aws/auth/AWSCredentialsProviderTest.cpp # Includes aws-c-auth private headers, so only works with submodule build

patches = [ ./cmake-dirs.patch <del> # fix cmake config (fetchpatch { url = "https://github.com/aws/aws-sdk-cpp/commit/b102aaf5693c4165c84b616ab9ffb9edfb705239.diff"; sha256 = "sha256-38QBo3MEFpyHPb8jZEURRPkoeu4DqWhVeErJayiHKF0="; }) </del> ]; # Builds in 2+h with 2 cores, and ~10m with a big-parallel builder.
Change:
is failing to build due to test failures Steps to reproduce the behavior: Package should buikd Please run and paste the result.
Fails on Hydra:

Discussion:
, buildPythonPackage , fetchFromGitHub , importlib-resources <ins> , proxy_tools , pygobject3 </ins> , pyqtwebengine , pytest , pythonOlder , qt5 <ins> , qtpy , six </ins> , xvfb-run <del> , proxy_tools </del> }: buildPythonPackage rec { pname = "pywebview"; <del> version = "3.6.1"; </del> <ins> version = "3.6.3"; format = "setuptools"; </ins> disabled = pythonOlder "3.5"; src = fetchFromGitHub { owner = "r0x0r"; repo = "pywebview"; rev = version; <del> sha256 = "sha256-9o9ghqvU9Hnmf2aj/BqX7WBgS9ilRSnicR+qd25OfjI="; </del> <ins> hash = "sha256-qOLK4MHdpmcCazCNfojncD8XH7OJB2H/pIW5XAJAlDo="; </ins> }; nativeBuildInputs = [

propagatedBuildInputs = [ pyqtwebengine proxy_tools <del> ] ++ lib.optionals (pythonOlder "3.7") [ importlib-resources ]; </del> <ins> six ] ++ lib.optionals (pythonOlder "3.7") [ importlib-resources ]; </ins> checkInputs = [ <ins> pygobject3 </ins> pytest <ins> qtpy </ins> xvfb-run ];

popd ''; <del> pythonImportsCheck = [ "webview" ]; </del> <ins> pythonImportsCheck = [ "webview" ]; </ins> meta = with lib; { <del> homepage = "https://github.com/r0x0r/pywebview"; </del> description = "Lightweight cross-platform wrapper around a webview"; <ins> homepage = "https://github.com/r0x0r/pywebview"; </ins> license = licenses.bsd3; maintainers = with maintainers; [ jojosch ]; };
Change:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
Looks like another gcc11 issue. would you mind taking a look?

Discussion:
dm-sonnet = callPackage ../development/python-modules/dm-sonnet { }; <del> dm-tree = callPackage ../development/python-modules/dm-tree { }; </del> <ins> dm-tree = callPackage ../development/python-modules/dm-tree { abseil-cpp = pkgs.abseil-cpp.override { cxxStandard = "14"; }; }; </ins> dnachisel = callPackage ../development/python-modules/dnachisel { };
Change:
The output will include recent vector instructions if and only if the builder supports them. This break reproducibility. Steps to reproduce the behavior: on an Intel Sandy Bridge machine a derivation from a substituter. This results in a due to a instruction locally and run. No Both derivations should be identical. This is the segfault inside an assembly debugger ! This might affect projects in general. This is both an impurity and a usability problem because I cannot use certain derivations on some of my older computers. Please run and paste the result.
Looks like ncdu is using a standard which means you can pass, e.g. for a cross-compiled build. For example, . This will use "baseline" CPU features instead of targeting the host. If you want to be more precise, you can additionally pass a parameter to selectively enable or disable specific CPU features. In theory, these should be accessible from the stdenv. I suggest to additionally pass the glibc version, like this: (replacing "2.31" with the data from stdenv). Otherwise zig will target a glibc version that is older than necessary.
This would be great to have in the stdenv. Any zig build needs these parameters.
It should rather be a zig buildHook to not bloat stdenv more.
Proposed a fix in

Discussion:
PREFIX = placeholder "out"; <ins> # Avoid CPU feature impurity, see https://github.com/NixOS/nixpkgs/issues/169461 ZIG_FLAGS = "-Drelease-safe -Dcpu=baseline"; </ins> meta = with lib; { description = "Disk usage analyzer with an ncurses interface"; homepage = "https://dev.yorhel.nl/ncdu";
Change:
Installing hugo 0.96.0 under darwin results in an error. The last version wasn't broken. try: nix-env -iA Full log <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --The last PR seems to introduce the breaking changes Please run and paste the result.
Looks to be the same problem as (as well as a bunch of other packages already marked broken in Nixpkgs for x86_64-darwin for the same reason)

Discussion:
homepage = "https://golangci-lint.run/"; license = licenses.gpl3Plus; maintainers = with maintainers; [ anpryl manveru mic92 ]; <del> broken = stdenv.isDarwin && stdenv.isx86_64; </del> }; }
Change:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag: -
Not sure why these DeprecationWarning's are turning into errors, but oh well

Discussion:
pytestFlagsArray = [ "-W ignore::FutureWarning" <ins> "-W ignore::DeprecationWarning" </ins> ]; disabledTestPaths = [
Change:
Building the most recent version breaks under darwin Full log: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- the last version bump broke darwin builds Please run and paste the result.
1 is the last version that successfully builds under darwin. Everything above (currently 3.0.2 and 3.1.0) breaks during build.
2 has the same build problem:

Discussion:
darwin.apple_sdk.frameworks.Foundation ]; <ins> # Disable cwd support on darwin, because it requires macOS>=10.15 preConfigure = lib.optionalString stdenv.isDarwin '' for file in 3rd/bee.lua/bee/subprocess/subprocess_posix.cpp 3rd/luamake/3rd/bee.lua/bee/subprocess/subprocess_posix.cpp; do substituteInPlace $file --replace '#define SUPPORT_CWD 1' "" done ''; </ins> preBuild = '' cd 3rd/luamake ''
Change:
(3.7) on master for a few days now, even reached nixpkgs-unstable. I'm running into this because it's a dependency for tensorflow-probabilty. It's probably needs some cxx standard flag -

Discussion:
# we accept this fact because xcode_locator is only a short-lived process used during the build. ./no-arc.patch <ins> ./gcc11.patch </ins> # --experimental_strict_action_env (which may one day become the default # see bazelbuild/bazel#2574) hardcodes the default # action environment to a non hermetic value (e.g. "/usr/local/bin").

<ins> diff --git a/third_party/ijar/mapped_file_unix.cc b/third_party/ijar/mapped_file_unix.cc index 6e3a908..030e9ca 100644 --- a/third_party/ijar/mapped_file_unix.cc +++ b/third_party/ijar/mapped_file_unix.cc @@ -19,6 +19,7 @@ #include <sys/mman.h> #include <algorithm> +#include <limits> #include "third_party/ijar/mapped_file.h" diff --git a/third_party/ijar/zlib_client.h b/third_party/ijar/zlib_client.h index ed66163..c4b051e 100644 --- a/third_party/ijar/zlib_client.h +++ b/third_party/ijar/zlib_client.h @@ -16,6 +16,7 @@ #define THIRD_PARTY_IJAR_ZLIB_CLIENT_H_ #include <limits.h> +#include <limits> #include "third_party/ijar/common.h" </ins>
Change:
Project description Add Tibetan Machine OpenType font for Tibetan, Dzongkha, and Ladakhi languages. Metadata homepage URL: source URL: mirror://debian/pool/main/f/fonts-tibetan-machine/fonts-tibetan- license: gpl2+ platforms: all

Discussion:
<ins> { fetchzip, lib }: let version = "1.901b"; in fetchzip { name = "tibetan-machine-${version}"; url = "mirror://debian/pool/main/f/fonts-tibetan-machine/fonts-tibetan-machine_${version}.orig.tar.bz2"; sha256 = "sha256-A+RgpFLsP4iTzl0PMRHaNzWGbDR5Qa38lRegNJ96ULo="; postFetch = '' mkdir -p $out/share/fonts tar xf $downloadedFile --strip-components=1 -C $out/share/fonts ttf-tmuni-${version}/TibMachUni-${version}.ttf ''; meta = with lib; { description = "Tibetan Machine - an OpenType Tibetan, Dzongkha and Ladakhi font"; license = licenses.gpl2Plus; maintainers = with lib.maintainers; [ serge ]; platforms = platforms.all; }; } </ins>

theme-vertex = callPackage ../data/themes/vertex { }; <ins> tibetan-machine = callPackage ../data/fonts/tibetan-machine { }; </ins> times-newer-roman = callPackage ../data/fonts/times-newer-roman { }; tipa = callPackage ../data/fonts/tipa { };