jiebi/CodeConvo huggingface dataset:
Project description <!-- Describe the project a little: --: Newt is a programming library for color text mode, widget based user interfaces. Newt can be used to add stacked windows, entry widgets, checkboxes, radio buttons, labels, plain text fields, scrollbars, etc., to text mode user interfaces. Newt is based on the slang library. is in nixpkgs but only built for targets. It would be great if it could also be built for Homebrew has a , but since I just started using Nix I wasn't able yet to port it to a Nix file. My best try can be . Metadata homepage URL: source URL: license: gpl2+ platforms: unix, linux, darwin
Describe the bug With default settings, sound won't play in the stable repository Tor Browser. I managed to get it working: for some reason, says this: I am still new to Nix so I am not sure what it should say, but it can't be right since this piece in got it working: (after of course) To Reproduce Steps to reproduce the behavior: to your system configuration but leave ALSA disabled to do anything that requires sound in the browser. Metadata system: host os: multi-user?: sandbox: version: channels: nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
me, too. any word on this? just open any youtube video, and there's no sound. if it matters, i'm using the latest on using overlays.
I marked this as stale due to inactivity. &rarr;
I am also interested in solving this. I am using nixos: 21.05.3761. (Okapi) Since I am new to nix, I just tried the package override from above, but this is not working. Reading through nix-pills is not really enlightening which files are involved in what...
Did you remember to uninstall and install after adding the override?
I get an error: but my is located in
Two possibilities that come to mind: 1: You didn't install by attribute. you need to do (assuming your nix channel name is ) as opposed to 2: Your is indeed in the wrong place or wrongly named. I don't recall straight how it should be named. Believe the nixpkgs manual with this one, not me.
After reading I put my stuff now into So tor browser sources are not there anymore... mhhhh... so in that sense I feel nixos is not holding its promises of reliability (caused by external party)
It's our problem, and a known issue. More info .
They have an alternative mirror recently to the unstable channel. If you try the newest unstable, it might download. Can't guarantee that though.
thank you for your attention/help - I will try this later and report back...
I have the following override: So tor-browser reports back the new version: 10.5.10 but I get the following error when playing a video - so audio does still not work:
... it seems that the overlay does not affect of the original package. This part of is not contained in the generated file: since I am quite a novice with nixos, any hint is welcome....
that worked, thanks alot!
For Chromium, there's a convenient way to define custom flags through . However, there doesn't seem to be a similar option for . I tried setting to "--touch-events", but touchscreen scrolling is not enabled when starting VSCode from desktop launcher, while running in console works as expected. Steps to reproduce the behavior: to "--touch-events" VSCode from desktop launcher on the editor area through touchscreen The editor should scroll as I drag. system: host os: multi-user?: sandbox: version: channels(yes): channels(root): nixpkgs:
Overriding idris-no-deps in nixpkgs results in a mismatch between versions of builtin packages and the compiler. With this derivation: I would expect to end up overriding the version of idris-no-deps in idrisPackages would change the derivations of builtin packages to be built with the supplied version of Idris. However, instead they are built with the Idris from the channel used. Leading to this error at build time (for Idris2): By examining the final result of the build I can see 2 versions of idris being used: Please run and paste the results.
Thought I might be able to solve this issue by specifying overrides as well. But no luck This is what the derivation for base looks like Specifically: Which contains the wrong version of Idris.
Same issue with non builtin packages as well. Also perhaps this is a better demonstration of the build time dependencies:
Thanks for the report, above PR should fix it, let me know if it works for you, then I'll merge it :)
Well actually I know it will work, but still. As a workaround if you don't want to change nixpkgs, an overlay should give no problems too:
Brilliant! Yes it's working for me and I'm now able to build Idris 2. Thank you very much!
The Haskell Hackage database allows distros to report which packages they ship, and include a link. Right now, it seems that nixpkgs reports all haskell packags, including broken ones. This makes for a bad user experience – I might see on hackage that nixos comes with a certain package, and then happily go ahead trying to use it, only later to get the dreaded error message. Same actually for repology, reporting packages as available that we know do not build is not great.
We intend to support all package. We just need haskell maintainer
Oh, absolutely! Maybe I shouldn't say “supported” but “available”.
No, we don't. We only intend to support packages which have value to our users. Hackage is append only and contains a lot of dead or niche packages.
I agree this should have been fixed long ago.
Cc: First of all, thanks to everyone for working on NixOS. Awesome 4.3 has a module called , it allows It can be used for theming, as shown in . However, the current build does not include the typelib files needed by the module making it unusable. The  implementation uses lgi to obtain via gobject-introspec return require('lgi').Gtk Since the current build does not include the typelib files needed, the above call fails. After some experimentation, I found out that both and are needed. For example: and try to load Gtk: fails with (the package that actually includes the typelib file) and add the folder to the environment variable: fails with and add it to and finally loads. Awesome as window manager to load the example gtk theme awesome the warnings issues by Awesome: I suggest that both and are as build inputs to the awesome package, I tried this out and it actually works. The catch is that the closure size increases by 123.9M: build awesome without gtk3-x11 and atk -99.6M build awesome with gtk3-x11 and atk -223.4M So, instead of adding the packages unconditionally, we could add an optional flag, like e.g. , defaulting to false. In this way, one could always build awesome and add it to . Ideally one could even add something like to the top level , a bit like : If a decision is made, I'd be happy to submit a PR. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: awesome 4.3 (Too long) Compiled against Lua 5.2.4 (running with Lua 5.2) D-Bus support: execinfo support: xcb-randr version: 1.6 LGI version: 0.9.2
It should not be necessary to use , should work just fine. See for docs on , which will populate the environment variable automatically.
Thanks, I'll have a look. For the record, I used because that's where told be the typelib files where. I am still keen on hearing what the correct solution would be regarding how to add support (closure size, optional arguments etc.). Thanks.
thanks for our suggestions.
Here are my thoughts: seems to work as well, the closure size is 222.9M instead of 223.4M seems quite conveniet, but awesome needs additional options in the wrapper and it's unclear to me whether we could do that after introducint uses that seems to have negative effects, see so we may have to look for alternative solutions anyway (Awesome does not seem to use much of GTK anyway as it's not a GTK app)
how could it shrink? can use as described in the doc PR to add more options. , I am aware of that but other than hardcoding the typelibs like we do in GNOME Shell extensions, we do not have anything better at the moment. See for deeper analysis.
¯()/¯ maybe it's got less dependencies built than the one? I see, I somehow missed that. It seems that works OK (I am using this in an overlay on NixOS waiting for the patches to land in the stable channel): In the end, AwesomeWM should not need the whole of gtk, I think that gtk should be made optional so one can turn it on or off. Thanks, I did notice that and I'll keep an eye on it
If I only do: then I get virtualbox + nvidia: If I enable virtualbox guest additions: then I get only virtualbox!!! and nvidia does not work anymore on my machine: this is because virtualbox guest additions is overriding services.xserver.videoDrivers: this is not necessary since by default the lists are merged workaround: then I get virtualbox + guest additions + nvidia: Ideally this should work out-of-the box, debugging this kind of behavior is very obscure, and also different configuration options should cohexist
On the master branch ethminer fails to compile with messages about missing getglobalepochcontext from ethash namespace. Attempt to build ethminer on master branch. Successful compilation. Root of the failure is in changes done to the structure of the dependency chfast/ethash; specifically, 0.6.0 -0.7.0. Patching the libethcore/EthashAux.h file in the ethminer repo, by adding to the headers, and the file by changing the line to does the job.
In gnome runs fine, in KDE plasma there are a couple problems: Unable to open file explorer when pressing "+", crashes with error Unable to add account, getting error Run in a pure shell: , use the and try to use it OR plasma installed and no other desktop environment: onedriver from nixpkgs (with home manager for example:) and press the button to add a folder. No errors we're missing the inputs and . should fix the gsettings schemas error (). The error requires env variable , we should probably wrap as explained . Quick and dirty way to make it work now, without wrapping, is adding those dependencies and adding the variable to the whole system: and to buildInputs and nativeBuildInputs respectively. (not sure which one for either): to the nixOS configuration the location of the variable: We should create a option eventually ahahha This is my configuration for the onedriver user service: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hello and thanks for reporting this! The is although it is only available in the channel for now, can you please test if the derivation from nixpkgs-unstable works for you? If not, I will add the missing dependency and make a PR asap :) As for the GIOEXTRAMODULES variable I am not sure there is something I can do at the derivation level.
Thanks I can confirm the version on the unstable channel doesn't crash with , but without the variable set the error is still present. I tried to wrap it by adding this line in the end of the postInstall script but it didn't fix it, running now shows two GIOEXTRAMODULES variables set tho I'll keep this open for now because of this problem and update the title the workaround for now is adding to the system configuration
Hey, I just pushed a small branch which should fix your issue with . I built the derivation locally and I get the right GIOEXTRAMODULES path set correctly by the script.
In my attempt in my previous comment, I had also tried a method that seemed to have set the correct GIOEXTRAMODULES path, but I tried your derivation and still: ! I grabbed your commit like this and it took a couple hours to build, it seems to have built a lot of programs besides onedriver, I'm still not a great nixOS wizard:
never mind, I'm dumb, forgot to change the package used in , now the error doesn't appear, but the window comes up grey? !
Trying to use the code from in my own config with callPackage gives me if I use instead of it works perfectly
using just also works
That is because is only on right now, if you're using you need to use , which is the same thing :) Glad to know the problem has been fixed for you. As for the blank page, it seems to be an upstream issue with onedriver and Plasma 6 (see jstaf/onedriver), but since I don't use Plasma I'm afraid I cannot help..
Project description The Open Observatory of Network Interference (OONI) is a free software project that aims to empower decentralized efforts in increasing transparency of Internet censorship around the world. please package as "ooniprobe-cli" ("ooniprobe" as alias) and "ooniprobe-desktop" like used here: Metadata homepage URL: source URL: license: mit (hidden in ) / BSD 3-Clause platforms: unix, linux, darwin, windows
I marked this as stale due to inactivity. &rarr;
...
I marked this as stale due to inactivity. &rarr;
Still relevant.
For visibility of our project it would be good if Steam can detect NixOS. Then it might appear in their stats: Error on console: Related to Currently detected system informations: steam system informations system: host os: multi-user?: sandbox: version: channels(davidak): channels(root): nixpkgs:
NixOS isn't configured to have . Kinda surprised they don't fallback to in favor of .
They actually do fall back but our doesn't support any files besides deprecated . We had a discussion before about correctness of providing on NixOS but I think we could do that, just print some error when supported LSB version is requested. Maybe we could steal Debian's modern implementation - I think they even use .
For a few days, when booting my amd computer with plymouth enabled I can't enter my passphrase anymore. Pushing keys multiple times eventually end up in one key-press being accepted. Booting with instead of suddenly has no more issues with keyboard entries. Steps to reproduce the behavior: NixOS Unstable to and with a LUKS/ZFS Passphrase -presses are omitted Every key I hit will be used. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- ? system: host os: multi-user?: sandbox: version: channels(pl): channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Upstream bug report Fixed in upstream already
Project description nodenv is one of version managers. I know you can manege with Nix itself, but majority of people in the frontend world assume everyone uses version managers which respect files like or , so you have to use them when you're working with them. Metadata homepage URL: source URL: license: MIT platforms: I'm not sure actually, but it's distributed as a homebrew formula
Hello, please check the merged pull request for notes on the package. The package works, but might need some changes or be extended to work better in the future.
Wow, thanks a lot for your help!
The audacious package imports audacious-plugins to build most of the common plugins and then link them into the audacious lib path. However, this makes it hard to add more audacious plugins, like vgmstream. The vgmstream package currently has its , because importing the audacious package causes an infinite recursion error. Steps to reproduce the behavior: vgmstream to audacious-plugins buildInputs audacious to vgmstream's buildInputs and comment out the disable configure flag -shell -p audacious-plugins I expected that adding vgmstream to audacious-plugins would enable the plugin. Instead, the build crashes with an infinite recursion. How is it currently working for audacious to import audacious-plugins and audacious-plugins to import audacious? Can this same magic be extended to other plugins? This about how fcitx is packaged shows that fcitx-addons imports fcitx with no reverse import, should the audacious package be refactored to be similar? Should the audacious package gain an extra parameter to take extra plugin derivations, which can be created outside of the audacious-plugins derivation? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Instead of adding , did you try to add instead? is without as input, and it is used to break the loop.
Thank you for the quick response! That would be elegant, but I don't see any result in my grep of nixpkgs or in the .
Sorry, it is here: Basically you need to do and this should do the trick. Considering that we are going to use this in more than one place it probably makes sense to introduce it as a , but the result is the same regardless.
Oh that's a neat trick! I'll try that approach out next. Thank you so much! I tried out the extra-plugins approach here, seems to work but is not ergonomic:
I , and it's a lot easier to use as a user! If it looks good as an approach, please provide some review feedback and I'll squash it down for a PR :)
Shall I send a PR for a final review?
Steps to reproduce the behavior: hydra build: build logs: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Not sure why this suddenly started failing after it worked fine for the last 11 days. Reproduced this and submitted a patch in that fixed it for me locally.
Thanks, I can confirm that the patch does work.
In my observation, it only breaks on , the works just fine. That's extremely weird.
I logged the test phase on the latest commit and the one before that, here’s what’s changed: Looks like it is to do with the
Nice work, It looks like is the commit that upgraded to pytest 8, but that was two weeks ago. So I'm not sure how this passed for 4 days ago.
The build that passed 4 days ago used as and the also wasn’t pointing to , here’s a snippet from the logs: The log file: But the latest build which failed, had set to and set to .
Steps to reproduce the behavior: oterm 0.2.7 unstable (I'm doing via home-manager on rev ) Fails finding a typer version Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I will check on my NixOS host later in the day to see if I can replicate.
There's a quick way to fix it:
Also, a PR in upstream:
Steps to reproduce the behavior: something which uses (easily ) Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --No maintainers, blame says last made a modification. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
No maintainers, blame says last made a modification. Hm, I can’t recall changing anything remotely related to LLVM and/or wrapper stuff recently. Which file(s) are you referring to?
Describe the bug nixos-unstable-small's package is broken: Seems related to beancount/fava To Reproduce Steps to reproduce the behavior: Expected behavior Fava builds correctly Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
I suspect this isn't the only app that broke with the switch from flask 1.2 to 2.0 and jinja 2 to 3.0.1
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
You can use in the expression for to pin and to compatible versions.
See:
I've been using cryptsetup with an SSD and without kernel crypto to run my entire NixOS and didn't noted any performance issues, but I agree that my patch was a temporary workaround, so enabling the crypto module would be a better solution.
The option also breaks the feature of that can be used when installing nixos to reason about the speed of disk encryption
The NixOS test works with and the kernel userapace crypto API enabled in on at least 19.03. was updated to 2.0.6 in the meantime, maybe the bug was fixed? Haven't noticed anything in release notes. This API shouldn't in fact be need for LUKS, only for tcrypt and the benchmark. Did you also run the test or did you just notice that on your local machine? Do you have any non-standard config concerning the initrd?
Hmm, even with the test succeeds. We need more information.
I haven't ran any tests, I just tested it in my work laptop and in a VM used to isolate the issue. I used a non-standard initrd config only for debugging, but after finding the problem I used the standard one. The only strange thing I did was to have a LUKS2 encrypted volume, which isn't very common (or at least it wasn't at the moment I experienced the issue). In a few days I will try to boot my system both with and without kernel crypto to check whether it is necessary or not.
I can confirm that I still have problems booting my system when kernel crypto is enabled. I put this in my , in an updated unstable NixOS: With this configuration, my system boots. If I uncomment the line, it doesn't because it fails to unencrypt my root partition. I'm using LVM inside a LUKS2 partition.
Here is the result of using when mounting my LUKS2 volume with kernel crypto enabled. The last image is the most important. Sorry for pasting screenshots, I didn't have a flash drive to copy the logs. ! ! ! ! !
Thank you very much for your detailed analysis. :+1: Oh, LUKS2! Seems the userspace API is indeed needed for LUKS2 but not LUKS1. I'll try to adapt the test and fix this issue. There are probably just some modules missing.
Commit introduced to the configuration of . This causes to no longer work, with the following message: Run , where is a truecrypt volume. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The issue for re-enabling kernel_crypto is
It also breaks
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
still important to me
I marked this as stale due to inactivity. &rarr;
are you sure this is still an issue? This seems to have been solved by . e.g. cryptsetup benchmark works just fine on my machine.
I did not check and do not care anymore. Thanks!