jiebi/CodeConvo huggingface dataset:
I have installed the TeXLive package on my system, but its binary script fails to run because: its directory is not found in it does not have an explicitly dependency on it does not have an explicitly dependency on the module for Python 2 cannot be found. Please fix this issues so that the script can be run. (Maybe can take a look at this.)
cc
Well, the first two bullets would be fixed very simply by but I don't yet have framework to add external python dependencies to the scripts.
Nothing new here? A similar problem happens with :
cc Maybe while a good solution is not engineered, a package for without the TeX stuff can be to . It would contain the binary with support for the needed Python dependencies. What do you think?
There aren't any true binaries, are there? It's just python scripts IIRC. But still, what you propose is probably the easiest way to resolve this somehow.
It is just a Python script that depends on the module.
My attempt at it:
So pygmentex works as expected now?
It works! It can be tested by downloading the example document from the distribution on , unzipping the downloaded files, removing the Python script and the LaTeX style class, and than compiling : The result is , with many examples of code listings typeset by Pygments.
OK, then I think we can close this.
Sorry for necromancing this (should I have opened a new issue instead?), but it doesn't "just work" – or needs further documentation on how to use it: The created by building the pygmentex texlive package can not find the module. gives us such an environment, just try running the command from there -The package though provides a executable which works just fine and finds the needed pygments python module. So how to combine these both packages? In particular I ran into this when trying to use the texlive package, as that seems to directly invoke the executable during build. Issue appears on release-18.09
I encountered the same issue, the latex package seems to be working fine tough (and can be used as a replacement)
I have in both with (which provides the style file and a non-functional Python script, because of missing Python dependencies) and (which provides the script). This setup works for me.
I still do not know a way of allowing Python module dependencies for Python scripts installed through .
This is to be fixed in
Package name: gnubg Latest released version: 1.07.001 <!-- Search your package here: --- Current version on the unstable channel: 1.06.002 Current version on the stable/release channel: 1.06.002 <!-- 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.
I packaged this in 2015 and I have no idea why.
I'm trying to use the mwprocapture nixos module (which uses the mwprocapture kernel package) on 20.09 (linuxPackageslatest), and I get the following: Is this known and/or already fixed somewhere? (Also, is it safe to use it anyways?) I'd love to try and fix it further myself, but I don't know how to splice in a local/development nix file into my for development purposes :sweatsmile: (also CC
Looks like upgrading the package version resolved things. Will create a PR soon.
Thanks for the heads up.
I'm trying out NixOS 19.09 and notice that Enlightenment is still being built under X. Enlightenment 23.0 have some highlight. One of them being "Massive improvements to Wayland support".
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 . 3. Ask on the on .
It would be nice to hear about the recent progress.
I've set up a borgmatic backup script using the borgmatic service. I can run the backup manually by running as root, but fails with the following error: Here is the service definition I used: I then tried to pass an absolute path to cat, by replacing with and got the following similar error: Steps to reproduce the behavior: one of the service definitions above and observe that running it manually works. the output in No errors, as both and are present on the system, and I can run I also noticed that borgmatics default value for , , causes an error when the borgmatic service is run. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As I know, NixOS package doesn't use your settings, which mean what you can use in your shell environment doesn't mean the package can use. User can use and whatever command they like in , I can't put everything in . So my suggestion is to use the format when using a command provided by other packages. As for your pgdump command not found, I suggest change it into Good caught, I will file a PR to change the default value.
This works, but I'm curious why it's not the default? As is, the service doesn't work for postgres dumps?
If we make this default, I think it will add those packages (pkgs.{mysql,postgresql,mariadb}) to nix store even the user doesn't need it. And I prefer to keep the package in minimal. Personally, I use the following code to use mysqldump
That's fair. Thanks for the feedback :-) Do we leave this issue open until has been merged?
You can keep it open, it will auto close once merged.
As it stands, the NixOS MPD module runs MPD as a systemd system service. As such it expects that the MPD user account (mpd by default) has control over the audio device. This conflicts with PulseAudio when it's used as a systemd user service (the default configuration). The intent of this change is to extend the MPD module so that it can be configured to run as a systemd user service. The changes remain backwards-compatible so users can continue with a system-wide configuration or go with a per-user config. I have a proof-of-concept of the modified module which I'm currently experimenting with. It can be used in as follows: The result is MPD running within a user slice: [ ] Ability to use a different per user; Probably by providing a option which overrides the other options and simply points to a file in the users home directory (ex. ). [ ] See if it's possible to get realtime scheduling to work. [x] Add NixOS tests. Currently there aren't any. The different options make for numerous potential combinations; I'm to lazy to test all of them manually.
did you ever add support for running mpd as a user service? It looks like just tests in preparation for running it as a user service.
Wow, I forgot all about this. Perhaps because I soon after stopped using MDP. The implementation is still on Github:
An alternative could be to let it talk to pulseaudio over the network. In the past I have used a config in mpd like audio_output { type "pulse" name "pulseaudio" server "127.0.0.1" } and then some config in to allow this access.
When launching the extension through Inkscape, the application freezes. Steps to reproduce the behavior: Inkscape the extension under Extensions Text Launch TexText Maybe linked to <!-- not actually involved, sorry --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
hmm, it opens pretty much instantly for me on current nixos-unstable (). Do you see any error messages in the terminal where you opened Inkscape?
No error message is reported on the terminal. Is there a flag I should add to the command for verbosity? I had someone else test this and they reported the same behavior. Something else I noticed is that Inkscape returns to normal if I let it hang for 1 or 2 minutes, but no sign of the extension's window.
I don't know if its related, but I tried the builtin formula extension, and I get this error when clicking on apply: <details</detailsDo you see anything suspicious?
sorry for the ping again, but I just noticed that trying to launch TexText results in a file with this content:
No worries about the ping! Unfortunately the errors you found in don't seem to be related to TexText. The errors from the builtin formula extension don't immediately give me anything to go on either.
I was able to identify two problems that are (most likely) causing the issue. The first is the python bindings for gobject-introspection that were missing. I submitted a PR for this one and now at least the extension window opens when I click on it. The second is related to Inkscape throwing a segmentation fault when trying to use the extension. I opened an issue here I don't know what's causing it though. Hopefully we can figure this out. EDIT: Please ignore the first issue. For the second one, there seem to be a fix on the way. I will close this issue if it resolves it.
Great that you were able to figure it out!
Sorry to revive this thread, it doesn't work for me. the script errors out i believe because it doesn't contain the path to package.
I'm afraid we'd need a bit more information. I just tested on latest nixos-unstable () using the above and it worked for me.
Describe the bug Since made it into nixpkgs-unstable I can't install neovim on an M1 laptop anymore, error is: To Reproduce Steps to reproduce the behavior: an M1 macbook run Expected behavior neovim to successfully install Screenshots N/A Additional context Notify maintainers Metadata Maintainer information:
Is it possible for you to check if reverting fixes the issue?
Yeah, that did the trick. It is weird as I can install luajit with no issue so maybe this is just an issue with the build setup rather than with the lua interpreter?
Refs I will test this on my M1 as well tonight
Sorry, tonight came later than I expected - I encountered the same issue on M1 and filed , which fixes it. Seems that luajit version is not the issue here ( did not work), as was suggested in Guess we should do a bit more digging
After upgrading to the current version of nixpgs (nixos-unstable) anki starts up to a blank main window. According to the documentation () that is because of the system glibc having changed to a version not compatible with anki. Their suggested fix is that users move to using the beta package instead. Steps to reproduce the behavior: -shell -p Anki working as usual Add any other context about the problem here. Please run and paste the result. Excerpt from
Can confirm the behaviour.
OAuth2 Proxy's Nginx plugin used to forward and headers to downstream programs. This stopped working after I updated on unstable channel, which is potentially related to or . Steps to reproduce the behavior: up OAuth2 Proxy + Nginx up of header name . does not recognize the session More simply: up OAuth2 Proxy + Nginx or something similar the headers — and used to be present, but not anymore and are passed to downstream servers under Nginx. I have I went on upgrade of nixpkgs unstable from sometime late January to a few hours ago, which is what led me to the two PRs mentioned above. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
are you able to play around a bit and confirm if the changes mentioned introduced this regression?
yes. I can't really pin-point to what exactly since there were a lot of changes. Instead, I just have a local fork from (prior to the changes mentioned in the PRs above).
I have a pretty good idea what it could be.
Can you give a try? I didn't test it yet, so it could completely break everything and be completely insecure, just as warning.
fantastic work please let us know how it goes ‍
Sorry for the late reply, I haven't been able to have time to test it out. Now that I do, it seems like has been converted to . This won't be an easy find-and-replace for me to try in my setup, so I will have to find some time to do proper cleanup.
I am encountering the following error after launching Pinta 2.0.2. I thought initially that it was a problem in the Adwaita theme itself, but whatever the GTK theme I use, I always have the problem. I tried on two different machines and had the same problem with both. NixOS with unstable channel Ubuntu + Nix 2.5.1 with unstable channel I did not have this problem in the last packaged version of Pinta. Maybe it is there since the 2.0.2 upgrade? Pinta should launch without this error. ! Please run and paste the result.
This looks like exactly the same problem discussed on Except that it should be fixed. Not sure what is happening here, and I don't have access to a Linux machine right now to debug. Maybe can help?
I also have this issue. It also causes the toolbar on the left to not appear.
Can someone show me the contents of the directory inside the package? It should have a directory/file somewhere, inside the icons directory (I don't remember the exact path). If this is missing, this is probably the issue.
It is missing:
Huh... I think I can blindly patch this issue, however someone will need to test on the PR.
Wait, I was wrong, it is there, but not in :
It shouldn't be in , it should be in . This is the issue. This can be probably fixed later correctly by setting some setting on , but since I don't have access to a Linux system for now I will just duplicate the assets for now. Later on I can do a proper fix.
Can someone test this PR please:
Waouh that was fast. Thanks a lot, both of you for your reactivity!
In 's tray menu the options "Floating Window Exceptions" & "Active Hint Color" don't work. Steps to reproduce the behavior: & enable pop-shell in GNOME (Wayland). pop-shell's tray menu and try clicking the mentioned options. Further dialogs should open for the respective features.
I found the problem: the compiled (g)js are not executible in filesystem. I do not know a solution yet. Most beautiful solution, fix chmod in pop-shell (but how ...). Or after compiling with an workaround in nix. Other solutions are set path to gjs during patching. Till fixing, you can run this features in your in, with calling it per gjs ...
Project description OpenTofu is a fork of Terraform, which is no longer under a free license (and should be marked as unfree for releases = 1.6.0). This fork is from the free sources before the license change to a source-available BSL license. Metadata homepage URL: source URL: license: mpl platforms: unix
cc some active maintainers of terraform:
Related issue:
I think it would be a good idea to wait for it to be actually named, see OpenTF is a placeholder name, and at this point OpenTF didn't release an alpha.
Will to take this on later today if nobody else grabs it.
Pull request has been opened, if the current Terraform maintainers are okay with it I can add them to the maintainers section of the new package. Otherwise more than happy to take responsibility for it.
Since won't build () From the above logs: Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Can reproduce on my ZFS system, not on my ext4 system though.
I can't reproduce by running on any system.
I was able to build from that commit nix store is zfs backed
It's more relevant whether is.
The renameat2 syscall used isn't (fully?) supported by ZFS: I'm not sure how that relates to this issue only occurring with , I guess it's related to the sandbox.
/tmp is tmpfs for me
Thanks for filing the upstream issue!
universal-ctags is not built with jansson, which means that universal-ctags does not have support for outputting JSON files. Steps to reproduce the behavior: universal-ctags with error: Expected: Tags file created with json format. Additional context I think this can be resolved by simply adding to the , but I've never written a nix package before so I'm not certain. I did this locally and it seemed to work, but I don't know if there's a better way to do it. Metadata Maintainer information:
cc I took a whack at fixing this locally. If this looks good to you, let me know and I can create a PR. I'm really new to Nix so it's likely I did something wrong.
Welcome and thanks a lot for the wonderful bug description Open the PR of course! You can update the package to the last version or add yourself to maintainers too if you are agree Don't hesitate to ask if your find any troubles
Describe the bug In the AVX512 support was turned back on in openblas, allowing for the use of dynamic, AVX512 optimized compute kernels. started to discover problems with AVX512 while working on the and I can confirm that this problem affects multiple packages that are built against openblas. The problem already manifest itself in that packages fail their unit tests, when build on an AVX512 enabled machine (see for a detailed list). The tests either fail due to a wrong result or time out. I could indentify 5 different packages which are affected by this bug, leading to the conclusions this very likely affects many more packages. Affected versions of openblas, which I have tested, are 0.3.13 (master/release-21.05) and 0.3.15 (in staging at the moment). The problem disappears when: is complied with in is injected into the test phase or just set at runtime. Note that any core type that does not use AVX512 works fine here (tested: , or , but , which uses AVX512 fails). is turned off at openblas build time and is set to a non-AVX512 target (see point 2). you seem to be making use AVX512 optimizations. Did you notice any problems? I suggest to revert and thus re-introduce the makeFlag in openblas. To Reproduce an affected program which is linked against openblas on an Intel CPU that supports AVX512 instructions (e.g. Xeon Scalable) and check the results. In nixpkgs it is at least that is affected (delivers wrong results). , for example, on an Intel CPU with AVX512: the self tests/unit tests never finish in this case. external packages fail to run their tests on and AVX512 enabled machine: Notify maintainers CC Metadata This should affect since (~January 2021) and . The tests I have carried out were run with versions from the ~last week.
Sorry to hear that :(. Then we should indeed revert that change again.
Can this be closed?
The PR has been merged into staging. Should we wait to close the issue until the fix reaches master?
Running reports: To Reproduce on NixOS 19.09. . Metadata I ran but got .
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 .
I had this same problem today.
I marked this as stale due to inactivity. &rarr;
Not stale; this is still a problem on a flakes based NixOS system using
Describe the bug The package that there was a directory in go's tools repo. Unfortunately, this directory was removed on commit  Not sure when the binary stopped being shipped in nixpkgs. To Reproduce Steps to reproduce the behavior: latest version of the the directory of the output from the derivation and assert the command is no longer there /a Expected behavior The gopls command should be available, it's a crucial binary, as it is used for lsp support Notify maintainers Metadata Please run and paste the result. Maintainer information:
is now available in package. This was changed in
Uhm, silly me, didn't check there was an independent package now. Would you say it is a good idea to update the referenced comment in this ticket? I can volunteer to update the comment.
Yes, I think so. Let's add a reference to this issue as well.
Created the PR: Apologies for the delay
Project description Epson Scan 2 is a scanning utility for epson printers and scanners. Metadata homepage URL: source URL: license: platforms: linux
I spent some time on this, but probably packaging epsonscan2 isn't worth the effort. My findings: build is quite tricky, as the sources contain some amount of tweaks (overrides) to standard cmake variables for build/install paths, and some install commands don't use , non-free software plugin is required for network scanning: sources of epsonscan2 are hard-coded to search the plugin in same path as is the installation path of epsonscan2, which doesn't play nice the immutability, the scanner might be supported already by My all-in-one printer is EcoTank L3160, which isn't listed in , but is similar to EcoTank L3150. And, all that was need is the following config: Terminal output:
I've managed to get this working on PR . As you said, building is a complete pain and required a fair bit of patching. It would be great if other Epson scanner owners could test this!
Works for me with Epson L3150 with wifi connection and non free plugins.
fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test