jiebi/CodeConvo huggingface dataset:
Change:
fetchbower = name: version: target: outputHash: stdenv.mkDerivation { name = "${name}-${bowerVersion version}"; <ins> SSL_CERT_FILE = "${cacert}/etc/ssl/certs/ca-bundle.crt"; </ins> buildCommand = '' fetch-bower --quiet --out=$PWD/out "${name}" "${target}" "${version}" # In some cases, the result of fetchBower is different depending

Discussion:
fetch-bower produces truncated nix-store entry when run under nix-build: Looking into the retrieved jquery in the nix store you can see jquery is actually missing: It works fine when trying to manually run it as a regular user: bower- generated by : run nix-build System: (16.09beta172. (Flounder)) Nix version: (nix-env (Nix) 1.11.4) Nixpkgs version: (16.09beta172.)
ping
Sorry for the delay I will test and merge today.
Hello thanks for your detailed report. I am getting slightly different results to you, so more investigation will be necessary. In my environment (NixOS 16.09 channel), there was no hash mismatch. Possibly something caused git to fail to download the jquery package. If it silently fails producing an incorrect result, then that is a bug in bower2nix which could be reported at
I am not sure this due to bower2nix. Fetch-bower is calling git and should handle the error's accordingly, no?
It consistently fails for me both on the latest unstable and 16.09 channels. Can you try updating your channels? My suspect was commit but I wasn't able to revert it cleanly to try it out.
By , I also mean . I have rolled the two programs into one repo. You are definitely right, is calling (indirectly, through the API), and should handle the error. I'm an avid subscriber to 16.09 and especially nixos-unstable, so have tested on those. Obviously it would be easier to fix the error handling if I can make fail myself. Do you have any further info about your setup which might be relevant? E.g. any proxy settings required for git to work. Can I also confirm that you are running before retrying ?
I don't have any proxy settings. Is it possible GitHub is rate limiting requests from bower? I found this thread interesting And yes I am running nix-store --delete before trying nix-build.
Hi are there any additional details I can provide? I am not that familiar with typescript or javascript, but I could try to narrow the issue down with some help.
How to reproduce: Expected output: bower package info json.

Actual output: nothing, not even an error message.
This problem is back. I can reproduce it by following the steps outlined in the top message. (latest nixpkgs-unstable) It did work for me a while ago though, so it looks like a regression. Did some digging around but I cannot figure it out. cc
Good catch, I think I've seen the same issue as well, but didn't bother (lack of time). Could be a different cause, but we have to start somewhere :)
Running produces correct result while -ing the following produces an output without jquery (just meta data)
Figured it out. Git doesn't see SSL certificates. I made it run with this expression I'll try to open a PR to fix this in nixpkgs. I'll also try to open a PR to bower2nix because there is a bug in it - missing SSL cert should not result in exit code 0.
Change:
gcc = stdenv.cc.cc; src = fetchurl { <del> url = http://www2.ati.com/drivers/linux/amd-catalyst-omega-14.12-linux-run-installers.zip; sha256 = "0jd2scrdlyapynxfjdrarnwcdzxjqrk5fg5i10g3bm0ay8v9hrk8"; </del> <ins> url = "http://www2.ati.com/drivers/linux/amd-driver-installer-15.20.1046-x86.x86_64.zip"; sha256 = "ffde64203f49d9288eaa25f4d744187b6f4f14a87a444bab6a001d822b327a9d"; </ins> curlOpts = "--referer http://support.amd.com/en-us/download/desktop?os=Linux%20x86_64"; }; <del> patchPhase = "patch -p1 < ${./fglrx_3.17rc6-no_hotplug.patch}"; </del> <ins> patchPhase = "patch -p1 < ${./kernel-api-fixes.patch}"; </ins> patchPhaseSamples = "patch -p2 < ${./patch-samples.patch}"; buildInputs =

Discussion:
I was given a tip by vcunat to upgrade the kernel to see if my GPU requires a newer kernel version (AMD has done a lot of adding to the linux kernel lately). But I received the same error when I tried upgrading to linuxPackages314 and linuxPackageslatest: /tmp/nix-build-ati-drivers-13.12- In function 'KCLACPIGetHandles': /tmp/nix-build-ati-drivers-13.12- error: 'struct acpidevnode' has no member named 'handle' pInfo-videohandle = pInfo-pcidev-; Can someone reproduce this? Suggested fix?
These are common problems. AMD's proprietary drivers have problems compiling with newer kernels. On gentoo they have patches , and they have multiple versions working, probably even with 3.14. The build process is a terrible mess though, so it won't be straightforward to port. Anyway, I'd think that the AMD work in kernel mostly only affects the free drivers.
True enough, and they might migrate completely to open source - but that time is not now :/ With the open source ATI drivers I'm seeing screen tears and all kinds of strange screen corruptions when, for instance, suspending to disk. I'm not sure this would be remedied by them releasing patches any time soon.
Try
This issue remains for 3.19 and 4.0. I'm still running 3.18 because of this. I hope there is some progress going on?
Driver needs an update to 15.5, which might fix your compilation issues? (I'll swap across to an ati card and test the update sometime in the coming week if nobody beats me to it) It's unlikely that your issues with 3.19 and 4.0 are the same compilation issues that this thread had initially, which were fixed in one of the ati driver updates.
Do you had any success?
I have a fix for this which fixes compilation issues and also upgrades to 15.07. Pull request incoming shortly as soon I get it properly merged into the tree rather than implemented as an override.
Thanks for getting to this dfoxfranke. I normally use my ati card for vga passthrough to a windows vm so this fell to the bottom of the priority list for me.
Change:
buildPythonApplication = if isQt6 then python3Packages.buildPythonApplication else mkDerivationWith python3Packages.buildPythonApplication; pname = "qutebrowser"; <del> version = if isQt6 then "unstable-2023-03-19" else "2.5.3"; </del> <ins> version = if isQt6 then "unstable-2023-04-18" else "2.5.3"; </ins> in assert withMediaPlayback -> gst_all_1 != null;

Discussion:
Qutebrowser crashes during startup with the following error message: Steps to reproduce the behavior: The derivation did not change for a while, and so I expect the reason is some changes in . commit hash: `
Change:
{ stdenv , fetchFromGitHub }: rec { <del> version = "2.8.0"; </del> <ins> version = "2.9.0"; </ins> src = fetchFromGitHub { owner = "openrazer"; repo = "openrazer"; rev = "v${version}"; <del> sha256 = "0mwg6b2y3wfpvgxb9lznwblb3bnrayn858nc4fbbg76zdp5bk5ky"; </del> <ins> sha256 = "1js7hq7zx5kj99brffrfaaah283ydkffmmrzsxv4mkd3nnd6rykk"; </ins> }; meta = with stdenv.lib; { homepage = "https://openrazer.github.io/";

Discussion:
<!-- 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: openrazer <!-- The current version can be found easily with the same process than 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.8.0 desired version: 2.9.0 maintainers: Please tag this issue in your PR.
Would you like to try sending a pull request Just change these two fields in the file: set to set to (hash obtained by running after changing the version)
lets see how this plays out. I raised a pull request:
Closed via
Change:
<ins> diff --git a/src/Makefile.am b/src/Makefile.am index 4b0c466..ce008fa 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -54,7 +54,7 @@ @chgrp games ${DOPEBIN} || chgrp wheel ${DOPEBIN} ||  ( echo "WARNING: Cannot change group of dopewars binary - the high";  echo "score file may be unreadable or unwriteable by some users" ) -	chmod 2755 ${DOPEBIN} +	chmod 755 ${DOPEBIN} install-data-local: ${mkinstalldirs} ${PIXDIR} </ins>

Discussion:
Dopewars is a game simulating the life of a drug dealer in New York. The aim of the game is to make lots and lots of money... unfortunately, you start the game with a hefty debt, accumulating interest, and the cops take a rather dim view of drug dealing... <!-- Describe the project a little: --Metadata homepage URL: source URL: license: GPL-2.0 platforms: Linux, Windows, MAC
Change:
sha256 = "134xk7rfj0xki9znryk5qf1nsfa318ahrrsi1k6ia7kipp7i3hb4"; }; <del> buildInputs = [ proot patchelf fakechroot runc simplejson pycurl coreutils nose mock ]; </del> <ins> buildInputs = [ proot patchelf fakechroot runc simplejson pycurl coreutils ]; </ins> postPatch = '' substituteInPlace udocker.py --replace /usr/sbin:/sbin:/usr/bin:/bin $PATH

Discussion:
I stumbled upon this package broken while working on , filing an issue to track it. Tested on commit . system: host os: multi-user?: sandbox: version: channels(root): channels(kalbasit): channels(yl): nixpkgs:
Change:
{ composeAndroidPackages, stdenv, lib, runtimeShell }: <del> { name, app ? null </del> <ins> { name , app ? null </ins> , platformVersion ? "33" , abiVersion ? "armeabi-v7a" , systemImageType ? "default" <del> , enableGPU ? false , extraAVDFiles ? [] </del> <ins> , enableGPU ? false # Enable GPU acceleration. It's deprecated, instead use `configOptions` below. , configOptions ? ( # List of options to add in config.ini lib.optionalAttrs enableGPU (lib.warn "enableGPU argument is deprecated and will be removed; use configOptions instead" { "hw.gpu.enabled" = "yes"; } ) ) , extraAVDFiles ? [ ] </ins> , package ? null , activity ? null , androidUserHome ? null , avdHomeDir ? null # Support old variable with non-standard naming! , androidAvdHome ? avdHomeDir <del> , sdkExtraArgs ? {} </del> <ins> , deviceName ? "device" , sdkExtraArgs ? { } </ins> , androidAvdFlags ? null , androidEmulatorFlags ? null }:

Discussion:
When you run it creates an AVD named if it doesn't exist. The problem is that it creates is in a wrong directory! Assume then run and then close the created and launched emulator, and now open the Android Studio to see the problem then open the "Device Manager" to see ! No corrupted file in Android Studio! I'll create a PR soon.
Fixed by I assume.
Change:
<ins> import ./make-test-python.nix ({ ... }: { name = "lldap"; nodes.machine = { pkgs, ... }: { services.lldap = { enable = true; settings = { verbose = true; ldap_base_dn = "dc=example,dc=com"; }; }; environment.systemPackages = [ pkgs.openldap ]; }; testScript = '' machine.wait_for_unit("lldap.service") machine.wait_for_open_port(3890) machine.wait_for_open_port(17170) machine.succeed("curl --location --fail http://localhost:17170/") print( machine.succeed('ldapsearch -H ldap://localhost:3890 -D uid=admin,ou=people,dc=example,dc=com -b "ou=people,dc=example,dc=com" -w password') ) ''; }) </ins>

Discussion:
Project description An lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication: clients that can only speak LDAP protocol can talk to it and use it as an authentication server. Metadata homepage URL: source URL: license: platforms: unix
Here is what I came up with so far (with big help from :heart:):
I marked this as stale due to inactivity. &rarr;
Still relevant
I gave it a try in in case someone would like to take a look at it :)
Change:
pillow setuptools xmlschema <del> packaging </del> <ins> cvss packaging_21_3 </ins> ]; nativeCheckInputs = [

Discussion:
Trying to install (either with nix-env or nix-shell) fails. I'm not sure if this is a macOS only issue or not. Steps to reproduce the behavior: for install to fail with error: Relevant error logs: Please run and paste the result.
Change:
jq moreutils esbuild # Required by `keytar`, which is a dependency of `vsce`. pkg-config libsecret <ins> ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.AppKit darwin.apple_sdk.frameworks.Security </ins> ]; # Follows https://github.com/rust-analyzer/rust-analyzer/blob/41949748a6123fd6061eb984a47f4fe780525e63/xtask/src/dist.rs#L39-L65

Discussion:
has been broken on since with build log failures that look like (excerpting from ): Another patch , fixed a related issue but did not fix the keytar dependency on Darwin. Fortunately, adding the necessary frameworks as conditional-on-darwin nativeBuildInputs in a manner similar to the way that is by fixes things here too. (PR incoming once I finish writing it up.) (and as a courtesy, though I know she has recently stepped down from maintaining the vscode extension)
Change:
<ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , rustPlatform , rustc , cargo , wrapGAppsHook4 , blueprint-compiler , libadwaita , desktop-file-utils , openssl }: stdenv.mkDerivation rec { pname = "televido"; version = "0.3.0"; src = fetchFromGitHub { owner = "d-k-bo"; repo = "televido"; rev = "v${version}"; hash = "sha256-qfUwPyutBNEnplD3kmTJXffzcWkEcR6FTLnT5YDSysU="; }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; hash = "sha256-CmQQH6a5xMq+v+P4/sbpQ7iDaGKtzV39FgufD5uxz4Y="; }; nativeBuildInputs = [ meson ninja pkg-config rustPlatform.cargoSetupHook rustc cargo wrapGAppsHook4 blueprint-compiler openssl ]; buildInputs = [ libadwaita desktop-file-utils ]; meta = with lib; { description = "Viewer for German-language public broadcasting live streams and archives"; homepage = "https://github.com/d-k-bo/televido"; license = licenses.gpl3; mainProgram = "televido"; maintainers = with maintainers; [ seineeloquenz ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description Televido (“Television” in Esperanto) lets you livestream, search, play and download media from German-language public television services. It is powered by 's API and the API which are both part of the project. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: GPL-3.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
description = "A tool for managing secrets, this binary includes the UI"; platforms = [ "x86_64-linux" "i686-linux" "x86_64-darwin" "aarch64-linux" ]; license = licenses.mpl20; <del> maintainers = with maintainers; [ offline psyanticy mkaito ]; </del> <ins> maintainers = with maintainers; [ offline psyanticy mkaito Chili-Man ]; </ins> }; }

Discussion:
, CVSSv3=5.3 (nixos-20.09) CVSSv3=5.3 (nixos-20.09) Scanned versions: nixos-20.09: . Cc Cc Cc Cc
Change:
gedit = throw "The ‘gnome.gedit’ alias was removed. Please use ‘pkgs.gedit’ directly."; # converted to throw on 2023-12-27 gnome-todo = throw "The ‘gnome.gnome-todo’ alias was removed. Please use ‘pkgs.endeavour’ directly."; # converted to throw on 2023-12-27 <ins> #### Removals anjuta = throw "`anjuta` was removed after not being maintained upstream and losing control of its official domain."; # 2024-01-16 </ins> }

Discussion:
If my sources are correct, the Project was archived in 2022 and the link for the Hompage now redirects to an indonesian gambling site. Linking to the could be better, but the Homepage link (on mentioned repo) also links to the gambling site.
The github repo does not look official. That would be But maybe it is time to remove it.
Considering the archived repo also links to the lapsed domain that now redirects to a gambling site, I'd be in favour of removal. However, that will also necessitate the removal of , which hasn't seen any updates since 2015. Neither has any maintainers, so I don't think the removal is likely to be objected to.
Change:
django-mailman3 django-q django_compressor <del> django_extensions </del> <ins> django-extensions </ins> djangorestframework flufl_lock mistune_2_0

Discussion:
python38Packages.djangoextensions and python39Packages.djangoextensions Fails to build. I discovered it as it was a dependency of Archivebox that also doesnt build now. Simple way to reproduce is: a file : I expected the package to build and not fail with errors. It appears it is the test's that fail and not the actual build. ! I have much larger file that I choose not to include as it is the same error i got in the minimal version and all the other clutter likely is not responsible. No maintainers for either of the packages :( Please run and paste the result. this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
Change:
{ lib <del> , writeShellScript </del> <ins> , writeShellApplication </ins> , coreutils , git , nix

Discussion:
say in no uncertain terms "The version attribute must start with a digit". however, a very large number of packages do not follow this naming guideline. almost all of these have a version starting with . on one occasion i was even instructed to change a version starting with a digit to a version starting with either common practice is wrong, or the documentation is wrong. my suggested fix would be to tweak the documentation to match common practice: versions must begin with a number, or the string followed by a YYYY-MM-DD date. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Should be fixed by
Change:
<del> { stdenv, lib, buildEnv, substituteAll </del> <ins> { stdenv, lib, buildEnv, substituteAll, runCommand </ins> , dwarf-fortress, dwarf-fortress-unfuck , dwarf-therapist , enableDFHack ? false, dfhack

Discussion:
Called from here: system: host os: multi-user?: sandbox: version: channels(root): channels(chris): nixpkgs:
I can reproduce this on system: host os: multi-user?: sandbox: version: channels(root): channels(addy): nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos
The problem seems to be, that already is a symlink. So it is no wonder that we can't edit it, as it is part of the original derivation. I'm not sure why that ever worked in the past, pkgs/build- hasn't been changed since there was an update to the dwarf-fortress derivation. I think the easiest way would to create the file in a separate derivation and add it to .
Change:
} updateFile("/etc/shadow", @shadowNew, 0600); <ins> { my $uid = getpwnam "root"; my $gid = getgrnam "shadow"; my $path = "/etc/shadow"; chown($uid, $gid, $path) || die "Failed to change ownership of $path: $!"; } </ins> # Rewrite /etc/subuid & /etc/subgid to include default container mappings

Discussion:
Describe the bug Currently, /etc/shadow belongs to the root group. For many use cases, this poses no problems, but when some program needs to use PAM to authenticate on the behalf of multiple users, the program needs to be executed as root (which seems generally unacceptable security-wise). One example is PAM authentication in Nginx, where the (see discussion on this). Expected behavior I think it's reasonable for /etc/shadow to belong to a group called "shadow" so users can make the decision on letting some programs/users read /etc/shadow. . If maintainers agree this is a reasonable thing to do, and if someone can confirm if this change is as simple as adding a group called shadow and adding a line in update-users- chown-ing /etc/shadow to root:shadow, then I'll create a PR. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I've tackled this in PTAL.
Just as a reminder, the 20.09 release is scheduled to happen this monday, the 28th. If this is still relevant to blocking the release, then there should be some forward movement. A blocker meeting has still yet to be scheduled. But, if you consider this item to still warrant blocking the entirety of the nixos-20.09 release, the please do so on the . A template for proposing an item can be found
As soon as the above PR is merged (), it can be backported to 20.09, and this issue won't be blocking 20.09 anymore.
Change:
inherit (darwin.apple_sdk.frameworks) CoreServices; }; <del> zoom-us = libsForQt59.callPackage ../applications/networking/instant-messengers/zoom-us { }; </del> <ins> zoom-us = libsForQt5.callPackage ../applications/networking/instant-messengers/zoom-us { }; </ins> zotero = callPackage ../applications/office/zotero { };

Discussion:
Describe the bug appears to be broken due to a Qt version mismatch. To Reproduce <details</detailsExpected behavior Zoom launches successfully. Additional context I'm running the proprietary NVIDIA drivers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Cant reproduce with same zoom-us version and qt5-base.
Hmm, I think we can probably use instead of . Though this shouldn't be happening in general... Hopefully backportable fixes on master.
I know it's not terribly helpful but FWIW I can also confirm zoom works for me on the same 19.09 commit using nvidia proprietary drivers.
Oh, weird. I don't have anything installed with (which is what caused this issue the last time I had it). Perhaps another one of the entries in is conflicting?
Maybe try It looks like it maybe tried to load two different versions of qt plugins in the same process. Shouldn't happen at all with qt wrappers that prefix .
This seems to work for me after that change. I haven't tried a video call yet but it does launch successfully, which it didn't previously.
Update: I can join calls but no video appears.
same issue here on ubuntu 18.04 with kde-neon it works by running it with
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
09 is EOL
Change:
<ins> { config, lib, ... }: { _file = "optionTypeFile.nix"; options.theType = lib.mkOption { type = lib.types.optionType; }; options.theOption = lib.mkOption { type = config.theType; default = {}; }; config.theType = lib.mkMerge [ (lib.types.submodule { options.nested = lib.mkOption { type = lib.types.int; }; }) (lib.types.submodule { _file = "other.nix"; options.nested = lib.mkOption { type = lib.types.str; }; }) ]; } </ins>

Discussion:
See the : the options aren't declared by any file (it's actually , but that's stripped at some point). I think this is most likely because they are declared inside a : but I don't know the module system well enough to troubleshoot this. This was causing the unstable channel import to because of an which should be fixed by This is an issue of the module system, so pinging
fixes this, thanks for the report!