jiebi/CodeConvo huggingface dataset:
Change:
Describe the bug bolt 0.9 appears to have broken/flaky tests. As of I cannot rebuild my system. Hydra fails in the same way: To Reproduce Build bolt-0.9, (hopefully) observe test failure. Expected behavior Bolt passes tests/has tests disabled. Screenshots N/A Additional context N/A Notify maintainers Metadata Maintainer information:
cc
This is now blocking the nixos-unstable channel. One restart didn't fix it. Upstream issue No response for two weeks.
The perceived nondeterminism of the test may have been caused by the presence of mount options on some/most of the builders. I've proposed to remove atime-dependent assertions in and upstream (linked from there)

Discussion:
, ninja , pkgconfig , fetchFromGitLab <ins> , fetchpatch </ins> , python3 , umockdev , gobject-introspection

(p: [ p.pygobject3 p.dbus-python p.python-dbusmock ])) ]; <del> # meson install tries to create /var/lib/boltd patches = [ ./0001-skip-mkdir.patch ]; </del> <ins> patches = [ # meson install tries to create /var/lib/boltd ./0001-skip-mkdir.patch # https://github.com/NixOS/nixpkgs/issues/104429 # Upstream issue: https://gitlab.freedesktop.org/bolt/bolt/-/issues/167 (fetchpatch { name = "disable-atime-tests.diff"; url = "https://gitlab.freedesktop.org/roberth/bolt/-/commit/1f672a7de2ebc4dd51590bb90f3b873a8ac0f4e6.diff"; sha256 = "134f5s6kjqs6612pwq5pm1miy58crn1kxbyyqhzjnzmf9m57fnc8"; }) ]; </ins> postPatch = '' patchShebangs scripts tests
Change:
Describe the bug On kernels newer than 5.8 exfat is natively supported by the kernel. However, if is used, nix will pull in exfat package and will use the fuse driver. This can be bypassed by not using the type and mounting by hand (there is no link for , but works still). To Reproduce Steps to reproduce the behavior: an exfat volume it to the attribute, e.g. that filesystem type is using . Expected behavior Using native kernel module for mounting exfat filesystems when kernel version is newer than 5.8. Additional context A check alike this already exists for the package () It seems that the check in could be responsible for this. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
should be for proper userspace to go with the new in kernel driver
Just got bitten by this on . Both FUSE and native can coexist, but if (from the package) is in the path, the utility will prefer it unless called with the flag (even with ). As there's no way to disable the utility from being built from current exfat, I suggest we switch to (I can submit a PR to package this) for applicable kernels.
Can confirm this behavior, having exfatprogs with newer kernels is definitely recommended.

Discussion:
release instead of 1.0.x </para> </listitem> <ins> <listitem> <para> If <literal>exfat</literal> is included in <literal>boot.supportedFilesystems</literal> and when using kernel 5.7 or later, the <literal>exfatprogs</literal> user-space utilities are used instead of <literal>exfat</literal>. </para> </listitem> </ins> </itemizedlist> </section> <section xml:id="sec-release-21.11-notable-changes">

- The `nomad` package now defaults to a 1.1.x release instead of 1.0.x <ins> - If `exfat` is included in `boot.supportedFilesystems` and when using kernel 5.7 or later, the `exfatprogs` user-space utilities are used instead of `exfat`. </ins> ## Other Notable Changes {#sec-release-21.11-notable-changes} - The setting [`services.openssh.logLevel`](options.html#opt-services.openssh.logLevel) `"VERBOSE"` `"INFO"`. This brings NixOS in line with upstream and other Linux distributions, and reduces log spam on servers due to bruteforcing botnets.

{ config = mkIf (any (fs: fs == "exfat") config.boot.supportedFilesystems) { <del> system.fsPackages = [ pkgs.exfat ]; </del> <ins> system.fsPackages = if config.boot.kernelPackages.kernelOlder "5.7" then [ pkgs.exfat # FUSE ] else [ pkgs.exfatprogs # non-FUSE ]; </ins> }; }
Change:
Describe the bug The uses the following source definition to build (in ): This source is no longer available, returning an HTP 302 redirect to a new homepage: Navigating the new home, this seems to be an alternative download location: However it seems to be a different file (warning, very slow download, file is ~ 140M in size): To Reproduce Steps to reproduce the behavior: -shell -p cups-kyodialog3 Expected behavior Packabe builds properly. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(marc): nixpkgs: Maintainer information:
I was slightly wrong because I don't understand how is supposed to work; it is the same file. The following works for me: I had to add the URL fragment to get to extract the file though.
does kyodialog3 works this way? Could you create a merge request?

Discussion:
dontStrip = true; src = fetchzip { <del> url = "https://usa.kyoceradocumentsolutions.com/content/dam/kdc/kdag/downloads/technical/executables/drivers/kyoceradocumentsolutions/us/en/Kyocera_Linux_PPD_Ver_${version}.tar.gz"; </del> <ins> url = "https://la.kyoceradocumentsolutions.com/content/dam/kdc/kdag/downloads/technical/executables/drivers/kyoceradocumentsolutions/lad/en/Kyocera_Linux_PPD_Ver_${version}.tar.gz"; </ins> sha256 = "11znnlkfssakml7w80gxlz1k59f3nvhph91fkzzadnm9i7a8yjal"; };
Change:
Describe the bug Build failure on hydra release-20.09 () To Reproduce Expected behavior Screenshots Additional context Notify maintainers Metadata Please run and paste the result. Maintainer information:
Seems like an unreliable test. Removed channel blocker severity.
again...
Please keep this label only for when its currently blocking, as these items are shown on
Aand it's back, on 20.09
This is a flaky test, but not a channel blocker. advanced a day ago: !
Some differences in the log : bad log from previous comment : successful log from local build This error seems closest to the root cause. A subsequent error seems to be about a fallback that doesn't work. In the successful log, no ramdisk is "detected", presumably because the virtual usb drive became the root filesystem. <details<summaryprobably less relevant log</summary</details<details<summarydiff command</summarycanon(){ sed -e 's/ [0-9][.][0-9]//g'; }; diff -U3 --color=always <(canon <~/Downloads/6m5q895jfljzd662wz9yiz66vsc3kxmy-vm-test-run-boot-bios-) <(canon </tmp/nri21z7knvx3zkdxzip88376m178gy6m-vm-test-run-boot-bios-) | less -R </details
Again. This issue may show selection bias because I only check 20.09.
Duplicate of
I marked this as stale due to inactivity. &rarr;

Discussion:
sha256 = "sha256-gTRf9XENAfbFB3asYCXnw4OV4Af6VE1W56K2xpYDhgM="; revert = true; }) <ins> # make nixos tests that boot from USB more stable # https://lists.nongnu.org/archive/html/qemu-devel/2022-05/msg01484.html (fetchpatch { url = "https://gitlab.com/raboof/qemu/-/commit/3fb5e8fe4434130b1167a995b2a01c077cca2cd5.patch"; sha256 = "sha256-evzrN3i4ntc/AFG0C0rezQpQbWcnx74nXO+5DLErX8o="; }) </ins> ] ++ lib.optional nixosTestRunner ./force-uid0-on-9p.patch;
Change:
The postfix module keeps adding a smtp entry to even though I have set . I would like to overwrite the default smtp service in , but postfix uses the last entry in the file (which is always the default one). To Reproduce Steps to reproduce the behavior: postfix: smtp : in Expected behavior following line should be excluded from Additional context Here's the resulting file with double entries: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- it looks like you wrote this part a while ago. Have you heard of this issue? Metadata Maintainer information:
I think, I fixed this a long time ago in my private nixpkgs repository and never upstreamed the change. I'll make a pull request.
Issue seems to be fixed. Thanks for the quick help!

Discussion:
}; services.postfix.masterConfig = { <del> smtp_inet = { name = "smtp"; type = "inet"; private = false; command = "smtpd"; }; </del> pickup = { private = false; wakeup = 60;

in concatLists (mapAttrsToList mkKeyVal cfg.submissionOptions); }; } // optionalAttrs cfg.enableSmtp { <ins> smtp_inet = { name = "smtp"; type = "inet"; private = false; command = "smtpd"; }; </ins> smtp = {}; relay = { command = "smtp";
Change:
Describe the bug Additional context I to because I wanted to play around with it before setting it as login shell. Not off to a good start. Notify maintainers Notifying these 3 because they all touched the pkg recently. Metadata system: host os: multi-user?: sandbox: version: nixpkgs:
I ran this in a , using , and the issue appears to be fixed. However, on I continue to see the same problem with , but seems to work.
I marked this as stale due to inactivity. &rarr;

Discussion:
find scripts -name 'xonsh*' -exec sed -i -e "s|env -S|env|" {} ; find -name "*.xsh" | xargs sed -ie 's|/usr/bin/env|${coreutils}/bin/env|' patchShebangs . <ins> substituteInPlace scripts/xon.sh  --replace 'python' "${python3Packages.python}/bin/python" ''; makeWrapperArgs = [ "--prefix PYTHONPATH : ${placeholder "out"}/lib/${python3Packages.python.libPrefix}/site-packages" ]; postInstall = '' wrapProgram $out/bin/xon.sh  $makeWrapperArgs </ins> ''; disabledTests = [
Change:
Describe the bug I'm using PCManFM as Filemanager and if I try to open a File with VSCode it only opens an empty file. (This issue is known: ). To fix this the issue recommends to change to in the desktop file. To Reproduce Steps to reproduce the behavior: to open a file in PCManFM with VSCode Expected behavior File is opened in VSCode Screenshots ! In VSCode I manullly opened the file on the left and tried to open it with PCManFM. As you can see, %U tells PCManFM to return a URL, but VSCode doesn't know what to do with it. So will be converted to . Additional context I'm not quite sure whether I'm the only one with this issue, I haven't seen any other issue explaining this same problem. But a friend of mine who I introduced to NixOS also had this Problem, so I'm probably not alone. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(vincentcui): nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos Maintainer information:
I already tried to change in to (Notice the part in the desktop entry) After I made this change and build it with (with NIXPKGS=<location of the changed nixpkgs directory) VSCode would open files from PCManFM without issue. I also haven't seen any other bugs created by this. I'm quite new to Nix and this is also my first issue, it would be really nice if you could tell me if I could have done something different or better.

Discussion:
desktopName = longName; comment = "Code Editing. Redefined."; genericName = "Text Editor"; <del> exec = "${executableName} %U"; </del> <ins> exec = "${executableName} %F"; </ins> icon = "code"; startupNotify = "true"; categories = "Utility;TextEditor;Development;IDE;";
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 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: texlive- current version: 2.9.1 desired version: 2.10.1 <!-- 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.
Can you tell a bit about your use case?
I knew I forgot something! :smile: I'm using emacs + org-mode, and am using the =unicode-math= package with =stix2-otf= along with lualatex. In order to preview equations, the pipeline goes /However/, =dvisvgm= 2.9.1 doesn't understand the extended font data that lualatex emits (see the comments in ), and so produces corrupt output images. This was fixed in 2.10.1, which was recently released and pushed to CTAN.

Discussion:
, freetype, gd, libXaw, icu, ghostscript, libXpm, libXmu, libXext , perl, perlPackages, python2Packages, pkgconfig , poppler, libpaper, graphite2, zziplib, harfbuzz, potrace, gmp, mpfr <del> , cairo, pixman, xorg, clisp, biber, xxHash </del> <ins> , brotli, cairo, pixman, xorg, clisp, biber, woff2, xxHash </ins> , makeWrapper, shortenPerlShebang }:

}; <del> dvisvgm = stdenv.mkDerivation { </del> <ins> dvisvgm = stdenv.mkDerivation rec { </ins> pname = "texlive-dvisvgm.bin"; <del> inherit version; inherit (common) src; </del> <ins> version = "2.11"; # TODO: dvisvgm was switched to build from upstream sources # to address https://github.com/NixOS/nixpkgs/issues/104847 # We might want to consider reverting that change in the future. src = fetchurl { url = "https://github.com/mgieseki/dvisvgm/releases/download/${version}/dvisvgm-${version}.tar.gz"; sha256 = "12b6h0h8rc487yjh3sq9zsdabm9cs2vqcrb0znnfi8277f87zf3j"; }; </ins> nativeBuildInputs = [ pkgconfig ]; <del> # TODO: dvisvgm still uses vendored dependencies buildInputs = [ core/*kpathsea*/ ghostscript zlib freetype /*potrace xxHash*/ ]; preConfigure = "cd texk/dvisvgm"; configureFlags = common.configureFlags ++ [ "--with-system-kpathsea" ]; </del> <ins> buildInputs = [ core/*kpathsea*/ brotli ghostscript zlib freetype woff2 potrace xxHash ]; </ins> enableParallelBuilding = true; };
Change:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
Hi Opened PR for this.

Discussion:
<ins> # DLib {#dlib} [DLib](http://dlib.net/) is a modern, C++-based toolkit which provides several machine learning algorithms. ## Compiling without AVX support {#compiling-without-avx-support} Especially older CPUs don't support [AVX](https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) (Advanced Vector Extensions) instructions that are used by DLib to optimize their algorithms. On the affected hardware errors like `Illegal instruction` will occur. In those cases AVX support needs to be disabled: ```nix self: super: { dlib = super.dlib.override { avxSupport = false; }; } ``` </ins>

<del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="dlib"> <title>DLib</title> <para> <link xlink:href="http://dlib.net/">DLib</link> is a modern, C++-based toolkit which provides several machine learning algorithms. </para> <section xml:id="compiling-without-avx-support"> <title>Compiling without AVX support</title> <para> Especially older CPUs don't support <link xlink:href="https://en.wikipedia.org/wiki/Advanced_Vector_Extensions">AVX</link> (<abbrev>Advanced Vector Extensions</abbrev>) instructions that are used by DLib to optimize their algorithms. </para> <para> On the affected hardware errors like <literal>Illegal instruction</literal> will occur. In those cases AVX support needs to be disabled: <programlisting>self: super: { dlib = super.dlib.override { avxSupport = false; }; }</programlisting> </para> </section> </section> </del>

This chapter contains information about how to use and maintain the Nix expressions for a number of specific packages, such as the Linux kernel or X.org. </para> <xi:include href="citrix.section.xml" /> <del> <xi:include href="dlib.xml" /> </del> <ins> <xi:include href="dlib.section.xml" /> </ins> <xi:include href="eclipse.section.xml" /> <xi:include href="elm.section.xml" /> <xi:include href="emacs.section.xml" />
Change:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.

Discussion:
<ins> # Elm {#sec-elm} To start a development environment do ```ShellSession nix-shell -p elmPackages.elm elmPackages.elm-format ``` To update the Elm compiler, see <filename>nixpkgs/pkgs/development/compilers/elm/README.md</filename>. To package Elm applications, [read about elm2nix](https://github.com/hercules-ci/elm2nix#elm2nix). </ins>

<del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-elm"> <title>Elm</title> <para> To start a development environment do <command>nix-shell -p elmPackages.elm elmPackages.elm-format</command> </para> <para> To update Elm compiler, see <filename>nixpkgs/pkgs/development/compilers/elm/README.md</filename>. </para> <para> To package Elm applications, <link xlink:href="https://github.com/hercules-ci/elm2nix#elm2nix">read about elm2nix</link>. </para> </section> </del>

<xi:include href="citrix.xml" /> <xi:include href="dlib.xml" /> <xi:include href="eclipse.xml" /> <del> <xi:include href="elm.xml" /> </del> <ins> <xi:include href="elm.section.xml" /> </ins> <xi:include href="emacs.section.xml" /> <xi:include href="firefox.section.xml" /> <xi:include href="ibus.xml" />
Change:
in have you tested it? i get this problem on OS X (darwin) and NixOS (x86_64).
Should be fixed now, thanks!
I successfully built it as it was a dependency of a project I installed. But building with and even installing a dependent package does not reveal issues in meta data. Thanks for noticing it. Can you please tell me how you found it?
tarball job checks information:
i tried to test another PR () and got the error above. i don't see how is a dependency of or does that informations get evaluated for all packages? you can use nox to easily test PRs like you can see above. before creating a PR you can test with the problem is solved, thank you! :+1:

Discussion:
meta = { homepage = https://github.com/cedadev/ndg_httpsclient/; description = "Provide enhanced HTTPS support for httplib and urllib2 using PyOpenSSL"; <del> license = licenses.bsd; </del> <ins> license = licenses.bsd2; </ins> maintainers = with maintainers; [ DamienCassou ]; }; };
Change:
sites like and google hangouts crash the content process within chromium, it has also been mentioned on the irc channel
I've confirmed that it's not coming from . Checking to see if it's . cc
I've confirmed that is the culprit. Shall we revert?
fwiw I have had this problem with beta channel chromium too for at least several weeks. I'm currently on version 46.0.2490.64, but it definitely applied to other versions. Is there an upstream bug that anyone has seen for this?
This seems related: I guess there might be some issue getting /dev/urandom from inside chromium's sandbox, see: and
If is indeed our issue, then the problem is that we don't have OpenSSL enabled. Looks like it was disabled by and replaced by NSS. do you want to comment on whether re-enabling is a good idea?
Looks like another solution might be to apply this patch: EDIT: Ooops, I realize I just paraphrased
OpenSSL was more or less officially supported at the time I created the Chromium source build but it was broken by upstream on a regular basis, so I switched to NSS. It however seems to have changed, see the the following document: I'm working on Chromium this week, so I'll investigate and test this as well.
Wouldnt it make more sense to just use the bundled boringssl for chromium? aszlig wrote:
Maybe, as said, I have to catch up on all those Chromium issues these days anyway, so I'll investigate. Using as much system dependencies as possible has the advantage that it cuts down build time, so we might want to avoid using more bundled dependencies.
But it has the major disadvantage of not being tested by upstream chromium developers. I think in the case chromium where we have a solid security story for bundled dependencies, we should use bundling as it provides more stability. I have a hunch that we arent saving more than 10% (although probably far less) build time by providing our own dependencies anyway. It would be worth investigating what that breakdown actually looks like. aszlig wrote:
thanks for fixing this in !
: As this issue is fixed, would one of you mind to close this bug ?
yeah, srtp works great on 47 and 48

Discussion:
sha256bin64 = "1m8vv3qh79an3719afz7n2ijqanf4cyxz2q4bzm512x52z5zipl7"; }; stable = { <del> version = "46.0.2490.71"; sha256 = "1dnwhwvn39x8lm1jszjn8y7vy478zy75gm696rr2dvk4kqj1hjyd"; sha256bin32 = "1v1acg32dzmkydzy7sh6xjbzqar052iw8x8hql2yjz5kxznir4sf"; sha256bin64 = "15ladhxiym760mid5zq09vp73irzwlp31br9yqslzgv4460ma3np"; </del> <ins> version = "45.0.2454.101"; sha256 = "1yw5xlgy5hd3iwcyf0sillq5p367fcpvp4mizpmv52cwmv52ss0v"; sha256bin32 = "1ll8lmkmx7v74naz1vcnrwk5ighh0skfcb66jkq4kgxrb5fjgwm5"; sha256bin64 = "1cwbd3n77dnbfnrfr8g0qng9xkgvz6y7mx489gpx1wsamgi42bzj"; </ins> }; }
Change:
After installing I cannot get voice and video working. I additionally installed and , but no luck either.
See on how to resolve this issue by setting . I'd recommend to document this in the wiki as a first fix.
Please check if fixes your issue.
I believe the issue is fixed by and should be closed.
I'm closing this as it should be fixed by . Feel free to reopen if the issue persists.

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; }; }