jiebi/CodeConvo huggingface dataset:
Describe the bug I'd like to build the python numpy package on an x86 machine for the armv7 architecture. numpy requires liblapack and blas, which require gfortran I already fixed one issue which is that liblapack couldn't find the gfortran compiler (see the overlay below) I'm trying to use the 20.03 release, latest commit. Here's what I'm running exactly: To Reproduce Steps to reproduce the behavior: -build here's the error I get Expected behavior The derivation builds Metadata Please run and paste the result. Maintainer information:
Maybe related to: ?
I'm not getting this in NixOS. It looks like a sandboxing issue. Can you try running this:
Thanks for responding! I launched this build on NixOs using an AMI on EC2 and I get the same result as in the issue report, here are the system details:
A similar issue exists on unstable when building for x86. Currently on: system: host os: multi-user?: sandbox: version: channels(root): channels(swflint): nixpkgs:
Package name: repgrep Latest released version: 0.15.0 <!-- Search your package here: --- Current version on the unstable channel: 0.14.3 Current version on the stable/release channel: 0.14.3 <!-- 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! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
option was changed to ddclient.domains, but instead of maintaining backwards compatibility the type was changed to a list of strings, which also was not in the release notes, which makes this a bug. I don't see why the type was not simply changed to an or of a string and a list of strings in order to maintain compatibility. Try to upgrade 18.03 with = ""; Any released 18.03 version.
As this breakage already happened, would there be a point in doing a patch for 18.09? (I could provide one, but I don't know, wether it will be merged into a stable branch.)
It would improve the experience for others (if you make it such that it works for both types). I cannot imagine any reason for it not being merged into a stable branch. I wouldn't mind merging it myself, but since I have no rights to do that you would have to wait longer.
hmm it looks like the module is in a weird state anyway. The config file, which is produced at the moment, doesn't look very useful, as all options will be applied to all domains likewise. So only one protocol can be used in nixos at the moment. If I am not mistaken I will need to change that into a config per domain, with a global part.
Your changes would introduce new features and go beyond what is in 18.09. 19.03 would be a good target. Due to the module system people could already use them in . Even then if would be nice if you could keep it backwards compatible. It's probably also relevant to consider whether there is an actual demand for what you are trying to do. For example, I would not be a potential user and most people would likely only use one protocol.
Not a problem, so I will just make the minimal possible change.
This needs to be reopened, because of a failure to build:
I'll take look. Which commit did you use?
Whatever was newest 15 hours ago in the release channel.
Yes, the change wasn't backported to the release branch :(
: Could you please reopen this and merge the change into release-18.09 ?
Project description swc is the "speedy web compiler" fast alternative to tsc, to compile typescript to javascript without type-checking swc is mentioned in a different context in adds 150 MByte to node_modules so it makes sense to factor-out swc to a global package example use: () on a 2x2GHz machine, swc is 10x faster than tsc = 2 minutes vs 20 minutes is a lightweight wrapper (1 MByte or so) but has as peer-dependency, so npm will install both Metadata homepage URL: source URL: license: apl2 platforms: all
K3s module example option () is causing a crash because kubelet verbosity can no longer be updated post-initialization k3s does not start with the option "--kubelet-arg=v=4" defined Suggest any other k3s option except this one <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: In the context of pip we previously deleted these files,
should have only eliminated the s and removed some of the platform-based (adding new broken/non-buildable attrs), but instead has changed the actual logic. Since that commit, no longer resolves into but into (note the wrong cuda release), later leading to evaluation errors This currently breaks on Steps to reproduce the behavior: We should probably add some tests for the selection logic as well... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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]:
I have a Samsung M2022W (usb) that works on a raspberrypi using raspbian (2017-11-29-raspbian-stretch-). I had to pick the ML-2160 driver in CUPS 2.2.1 as recommended by On NixOS (cups-2.2.2): [nawal nix-info system: "x8664-linux", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(nawal): "nixos-17.03-17.03.1082.", channels(root): "nixos-17.09.3149.", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs If I use services.printing = { enable = true; drivers = [ pkgs.samsungUnifiedLinuxDriver ]; extraConf = '' LogLevel debug ''; extraFilesConf = '' FileDevice yes ''; }; and pick the same driver, I get garbage printed out. I tried to track down the ppd on raspbian, but only found: pi $ grep 2160 /usr/share/cups/drv/splix- ModelName "ML-2160" PCFileName "" and (i.e. it generated the ppd when I installed the printer apparently).
On nixos: [nawal | grep 2160 /nix/store/6f2zx8dl4w0kzgw3wj8f466mvkcgc3dc-samsung-UnifiedLinuxDriver-4.00.39/opt/share/ppd/ML- /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- Having diffed them, I notice amongst a huge number of differences: [nawal diff /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- | grep Version < FileVersion: "2.0.0" < PSVersion: "(3010.000) 0" < QPDL QPDLVersion: "3" < *cupsVersion: 2.2 so raspbian is using a version "2.0.0" and "2.2" of something or other, whereas nixos is using a version "1.2" and "1.1" of similar things. I managed to get my printer to work by copying the ppd across, but I don't understand enough of cups (nor now have the inclination to learn) to figure out what's going on or how to make nixos do the right thing (i.e. in a word, print). I thought this might be useful for someone else who wants to pick it up? Happy to hack around the raspbian if you need more info, or try out things if you need me to while the sd card contains raspbian.
Can you find out what package on Raspbian provides the driver? Have you installed proprietary Samsung driver there? If not, can you try removing ? It seems we have latest version of but not the latest of the proprietary driver but you don't seem to use it.
I'll have a look tomorrow evening - how do i use the new splix without upgrading everything to the same commit?
Find out your current commit with (look at the suffix), then clone nixpkgs repository (), checkout current commit (), fetch my changes () and cherry-pick my patch atop your current commit (). Then you can rebuild nixpkgs with .
I can confirm this works.
The package can't be cross compiled to other architectures, tested: raspberry-pi and aarch-multiplatform Steps to reproduce the behavior: It should be compiled. This doesn't seem to a nix-only problem, but still influenced by nix. Doesn't compile on arm: AIX: Some missing support for aarch64: Doesn't compile via qemu for arm32v7 and arm64v8: The error I'm having doesn't seem to show up anywhere else though. And a few of those threads also post work arounds. There is no maintainer. $ nix-shell -p nix-info --run "nix-info -m" this path will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/xq77wmzk8d306anyk9rsvl4i4h7ihchw-bash-interactive-4.4-p23-dev copying path '/nix/store/xq77wmzk8d306anyk9rsvl4i4h7ihchw-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): channels(nix): nixpkgs: Maintainer information:
It seems to be that every package that declares in it's is failing to cross compile. If I put it in it fails with another error though: Should I open another, conglomerate, issue for all the other packages?
The latest major version 5.9 of the Linux kernel . Apparently, zstd compressed things decompress much faster and can cut boot times substantially, hence it seems worthwhile for us to support this scheme. Currently we are using bzip2. Unfortunately, I probably won't find time to work on this myself, but thought to open this issue to track progress.
I've [probably] been using it through a xanmod patch, not recently since the 5.9 release though. What I have in my files are and adding to of the kernel derivation
For the initrd image: For me (which might differ from the stock kernel NixOS provides): is already enabled, so set This enables ZSTD compression for initrd. However, which will need to as mentioned above.
I was wondering if zstd should be made a part of stdenv. are all available in stdenv on linux and with slowly becoming more common by being available in the kernel and used by various distribution's packaging it should make sense to include it.
Can this be closed? Did cover it all?
Yes, it did! Closing this issue. Thank you for pointing that out, didn't notice before.
Since PM stumpwm is now up to date but I have an issue in stumpwm module loading. SBCL will return the a package conflict error between packages "CLOSER-COMMON-LISP" and "DYNAMIC-MXINS" Steps to reproduce the behavior: to your stumpwm contrib modules in an appropriate directory a minimal file: reboot using stumpwm or refresh the stumpwm config using command (by default keystrokes are: ) Modules are loaded as expected Results of :
Hm, indeed. And maybe for debugging we should provide access to the «library» version of StumpWM…
We could try building using the Makefile instead of save-lisp-and-die. I did, but then there were problems with missing HOME. Then the problem was that the stumpwm build script seems to want to remember the value of HOME from compile-time on run-time (something like "/build") How did stumpwm work previously in nixpkgs?
Can you try with this?
I've to my . itself works fine: But the man pages are all missing: As far as I can tell, upstream provides them in DocBook format: and also provides a Makefile to build them: so this should hopefully be easily fixable. Steps to reproduce the behavior: . to read a man page for any of the binaries. Man pages should be provided. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting I have opened PR to fix it.
Pretty much all commands just show the "usage" output, regardless if the input is correct or not. For example, outputs: Steps to reproduce the behavior: , , , and many other commands incorrect output I expect to see the correct output, for example should show the current status of all miners.
How did you determine the commands? The printed help page does not list any of those as supported.
I got the commands from the Tracker documentation: You are right that they aren't listed in the help page. I do have manuals with usage for all those commands installed though.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Emby uses ffmpeg for transcoding media and for generating thumbnails. Emby fails to find the FFmpeg binary during the setup wizard but can be specified manually if FFmpeg has been installed separately. Add to , browse to , and advance through the wizard. System: 17.03pre92039. (Gorilla) Nix version:nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre92039.
cc
Funny thing is that I was just watching a movie when I was mentioned on a system without any ffmpeg/ffprobe binary. My system was upgraded from an older version (config was already existing so no check was done by the wizard). I was able to reproduce the issue. Will take a more detailed look at it sometime tomorrow :)
Trying to run an action with azure-cli that requries authentication, az will fail to read the cached authentication token from the token cache: This is due to a version mismatch of . will update the package, I checked that the authentication works afterwards. That's me! Please run and paste the result. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I also experience this issue with , as well as with . Thanks for adding the fix!
Setting to while setting to any non-empty value will cause a build failure because and both attempt to create The correct result would be for the contents of to be written out at the end of , after the stanzas provided by pulseaudio. Somewhat relatedly, the in and in pulseaudio's generated config doesn't make a whole lot of sense. means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the actually makes any difference.
I am having this issue as well. Easily replicated by setting those two options.
Can you make a pull request?
Should be fixed with . If there still is a problem, please reopen this issue.
Describe the bug When printing to Brother MFC-L2700DW printer (with created from a similar model in nixpkgs), CUPS often (but not always) complains about "Impossible to connect to Name or service not known" even though I followed the and enabled . To Reproduce Steps to reproduce the behavior: Brother MFC-L2700DW printer. NixOS as follows: (full configuration ) something to http://localhost:631/printers/BrotherMFC-L2700DWseries and see the "Impossible to connect to Name or service not known" message. Expected behavior The job is sent to the printer and printed. Additional context When the printer cannot be connected, running usually helps and the stuck job gets to the printer. After my investigation, I think that the cause is long delay in mDNS name resolution. By default NixOS uses NSS module, which tries to resolve both IPv4 and IPv6 addresses sequentially. It seems to start with IPv6, which does not resolve to a valid address so after 5s timeout the resolution continues with IPv4. So the address of the printer is returned after slightly more that 5 seconds (can be verified with ), which seems to be too long for CUPS so it gives up and tries again later and the same repeats, because nscd in NixOS does not cache the results. My current solution to the problem is to switch from NSS to with the following in my : I've also tried but it didn't help. The question is whether to make it easier for others. Possible things that come to my mind: Document this at Wiki Extend to provide e.g. option. Enable caching in nscd Something else? 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(wsh): nixpkgs: Maintainer information:
Confirm, I have the same problem (with Xerox WorkCentre). And your workaround fixed it for me too. Thanks!
I wanted to link this issue from the and found that there a comment suggesting that he might have the same problem. does the above workaround make your setup work without restarting cups after booting?
If yes, I'd update your comment, because it's not accurate. The is not needed, because it is pulled in by mentioned on the previous line.
Hi, I'm back and I'll test your workaround soon. About , I thought it should have been pulled, but it wasn't at the time. I vaguely remember triple checking and it wasn't there.
Sorry, I can't test it again. My printer is busted.
OK, thanks for letting me know :-)
Ok, my printer has sudently revived and this solves the issue for me as well.
I marked this as stale due to inactivity. &rarr;
Confirming that the issue still exists with current nixos-unstable.
Out of curiosity, is this workaround supposed to break or use outdated softwares? If not, would it make sense to directly apply your workaround by default?
This workaround makes mDNS working only for IPv4. If you are on a IPv6-only network, mDNS won't work for you. On mixed IPv4/IPv6 network, you might not see some devices. That's definitely not what some people want :-) Btw, may be relevant to this problem. I've not read all the comments there, but the keywords seem similar to what I remember when debugging this issue. I think the solution might be to increase or decrease some timeout somewhere, but I'm not sure where. More debugging/analysis is needed.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Same happening here with a Canon MF643C. I found a workaround, but yours seems better. Mine was to manually add the expected on '/etc/hosts' file. This only works if your printer has a fixed ip (like 10.1.2.3). networking.extraHosts = '' 10.1.2.3 '';
I also hit this issue. Given that (I assume) most people are running ipv4, can we not try the v4 exclusive module first, and still fallback to the one that also works with v6, so that it "just works" for this rather common use case? Given, that will slowdown v6 name resolution, but I guess we could also add a big warning in the option.
Looks like this is closed by
Unfortunately, that commit is not sufficient for me.
Current version of CUPS complains with: "No destination host name supplied by cups-browsed for printer "BrotherMFCL2700DWseriesmDNS", is cups-browsed running?" The referenced commit makes my contain the following line: hosts: mymachines mdns4minimal [NOTFOUND=return] files myhostname dns mdns With it, running returns an IPv6 address: fd76:76f3:2dcb:0:3205:5cff:fecb:4509 From the output of it seems that the command first asks for IPv6 address, so the is somehow ignored and the address is returned by at the end of the line. I can ping and connect that address via so I don't know why CUPS cannot print to it. Anyway, if I disable IPv6 in the printer, returns the IPv4 address, but only after the 5 second timeout, which is too long for CUPS. What I need is also at the end of line. I'll ask at and submit a PR to do that if people do not complain.
Please submit a PR.
Uses a direct printer install. Same sort of problems encountered.
<!-- 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: pmbootstrap <!-- 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: 1.45.0 desired version: 1.49.0 <!-- 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.
Describe the bug In order to be able to invoke the command from teleport is using  call. There is a wrapper around to bring into PATH . That means is invoked from without wrapper and the browser page never opens (due to missing ). To Reproduce Steps to reproduce the behavior: Expected behavior The path to the wrapper must be persisted in the Screenshots If applicable, add screenshots to help explain your problem. Additional context 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. Maintainer information:
Inkscape has support for openclipart but it doesn't work in the package provided by nixpkgs. inkscape to File -Import Clip Art... a search term and click the Search button. the in the GUI and in the terminal. NixOS 18.09 and nixpkgs master.
I researched a bit and thought adding glib-networking would fix it. I wrote the following patch, but it doesn't seem to have any effect:
I wonder whether it really is because TLS support is unavailable, or because uses an invalid security certificate?
Good point. Hm, that's weird. I followed that URL () a day or two ago (when I first noticed this) and was redirected to https:// without problems. But now I see the certificate warning in firefox.
I think it may be a packaging bug after all. Look at this grep: The message only appears in the glib tree, in the gdummytlsbackend.c file. No matches from glib-networking, which AFAIK, provides TLS support.
I tried the patch and am getting Probably because the site is down.
is not down for me.
Thank you!
Package name: ArchiSteamFarm Latest released version: 5.5.2.3 <!-- Search your package here: --- Current version on the unstable channel: 5.5.0.11 Current version on the stable/release channel: 5.4.12.5 <!-- 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! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It helps if I also open the PR when doing the update
Describe the bug When calling somebody using Microsoft Teams, it seems that the softwares fallback on ALSA plugin, which makes the audio output butchered (hearing noises when someone's talking, but unable to understand what this person is saying). To Reproduce Steps to reproduce the behavior: teams (require an Office 365 accounts) somebody Expected behavior It should use the PulseAudio backend during calls. Additional context I'm using Sway as my window manager (thus, running on wayland). Notify maintainers Microsoft Teams package maintainer: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(ely): nixpkgs:
How can one tell it that it falls back to the ALSA plugin? Apart from the butchered sound that is?
Inside Pavucontrol, you see it uses an "ALSA Plugin" as a backend. It shows ALSA only during a call, on the rest of the software it shows as a standard pulseaudio program output.