jiebi/CodeConvo huggingface dataset:
After upgrading to eww 0.6.0 from unstable I've got problems showing some strings in some of my widgets, one that shows the hour and another the minutes using two digits each one, i.e. : "09 : 10". When using eww 0.6.0 the string shown is like this: "... : ..." In eww's github repo I can see that there is a commit after version 0.6.0: And cloning eww repo with that commit, compiling it and using a local eww executable the problem explained before disappears for me. There's also another problem, asking eww-0.6.0 for version number shows it's 0.5.0: unstable eww 0.6.0 some string truncation (I think this is the problem) see "..." where a two char string with the hour should appear. eww should work as expected. Cloning eww repo with latest commit after v0.6.0 was published solves the problem for me.
~The current package for eww is . How did you install 0.6.0 from nixpkgs?~ ~As for the outdated 0.5.0 version in nixpkgs, there are three maintainers for eww in nixpkgs so it probably will be updated shortly, perhaps fetching a commit with the solution to the string truncation problem you describe.~ EDIT: i was wrong, see comment below.
I got it installed today from unstable when upgrading my system: But, as you say, if I look for it into unstable () it shows version 0.5.0...I can't understand very well this...I'm relatively new to nixos. Ok, I'll wait then. Thanks for your interest in this.
Oh sorry, you're right! There is eww 0.6.0 in master, although it didn't make it into unstable yet. I built the package and, indeed, truncation is broken the version is incorrectly reported So the truncation was fixed, as you mention, after the release, and the reported version . That . If you can't wait, for it, i'd recommend you use the package output from the eww flake.
I personally have been using it for a while and it works correctly (let me know if you need help, i'm on the matrix server with the same username). For now, I guess this issue can be closed because both are upstream bugs and the fixes will make it into a future release.
I think I we can backport the changes using patches. I'll send a PR.
Still I don't know how this 0.6.0 version was pulled from unstable into my system...I'm in my way learning nixos. Flakes! my never ending story :). I'll try to use it and if I have problems I'll try to ping you on the matrix server. Thx!
Since 0.6.0 reached unstable, of course, and you updated your channels/inputs. BTW the search can be out-of-date, so don't expect 100% accuracy from it.
Yep, that makes sense to me and seems to be the missing piece that confused me: how could it be possible that in the search appeared version 0.5 and I had installed v 0.6. thanks for clarifying it for me and for your work in Nixos.
Describe the bug dmd keeps references to boostrap compiler. To Reproduce Steps to reproduce the behavior: Expected behavior dmd has no references to boostrap compiler Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): nixpkgs: Maintainer information: Note: to prevent future regressions, it would be nice to add to the derivation ()
I marked this as stale due to inactivity. &rarr;
Still an issue
I marked this as stale due to inactivity. &rarr;
The final merged version of isn't building. Just build with the initial configuration that would give on a UEFI machine, along with: Build successfully and boot into Dom0 on next reboot. <img width="1201" alt="image" src=""During the progress of , the issue isn't happening as of . Might be a regression happened in the last few commits before it's merged. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Whoops. That's my bad. Will make a PR in a few.
Steps to reproduce the behavior: azure-cli 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.
For now, changing python used to seems to fix the build:
Made a PR that fixes the failure.
Will investigate this failure and try to fix it (by using Python 3.11), but the build was working before (We may temporarily fix it using as a workaround), some dependencies must have been changed, from before, not sure which one is causing this failure, I'd need to bisect commits on master branch, I guess...
The failure is because of python3.11, the tests didn't work properly on 3.11. Upstream fixed those tests for a future release. For now we can either rollback the python used to 3.10, or back port the tests fixed. From what I tested, nothing is broken on 3.11 except for those tests.
Thanks a lot for those clarifications and appreciating a lot your help in fixing all this However, we can't really make sure that those tests won't break again, unless we pin a patch on those ? And this is what you've done in your fix PR. I'll be trying the latest release 2.53.1 with the dependencies cleanup.
Describe the bug The is failing. I bisected this problem to “linux: Init 5.8”. The error message matches , which points to both a workaround of recompiling systemd against Linux 5.8 headers, and an upstream systemd patch (systemd/systemd) that’s in systemd 246 () and was backported in 245.7 as systemd/systemd-stable To Reproduce Steps to reproduce the behavior: Notify maintainers Cc Metadata Please run and paste the result. Maintainer information:
My PR wasn't merged, Linux 5.8 ended up being by someone else.
Linking for visibility: that PR was
The PR bumping systemd to 245.7 is at
Is it really helpful to send systemd 245.7 to given that will be unable to advance without it? Or are you thinking we also want to revert the bump in for now?
Maybe we should revert in master, and re-revert it in staging again. I let and decide about this, they've been doing the staging rounds.
Hey all, question: How do you spot which tests block the channels? I always track and every few days I notice nixos-unstable doesn't progress. When it don't I see an issue with the "channel blocker" label and I always wonder..
Click on the “Hydra job for tests” link and go to the “Constituents” tab.
The postStart script of elasticsearch fails when a special values like or ( ) is used for services.elasticsearch.listenAddress as the script expects an IP or a hostname. Using an ip as listenAddress ist not always a viable option especially when generating NixOS images upfront for a dynamic deployment (e.g. on Azure or EC2) I am not sure how to address this issue. Perhaps one shall check netstat output to find out which ip was bound to? /cc
Yes i agree, we should implement another option for es url, I'm fine even with removing postStart. You can create pull request if you need fix asoap, I will put it on to-do.
Package name: hyprland Latest released version: 0.36.0 <!-- Search your package here: --- Current version on the unstable channel: 0.35.0 Current version on the stable/release channel: 0.32.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]: The 035.0 has a bug that makes my system crash very often (nullptr when monitor is disconnected) the issue is supposed to be fixed in 0.36.0.
After reboot, while systemd units are still loading, if user clicks on Systemd-Manger extension the entire DE will crash and Gnome will force a log out of that user. Moreover, Systemd-Manager is at v14 when v15 is out from the developer. Steps to reproduce the behavior: Computer DE loads and user is logged in on Systemd-Manager (while the systemd units [custom systemd units by the user into the extension] are still loading for example "bitcoind") crashes and forces log out No crashing of DE and you should be able to see in Systemd-Manager the units that have not started without it crashing Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Any news on this? Thanks so much!
Any news on this Thanks so much!
Update should be contained in
sweet!!! Thanks, I will keep an eye on it. Thanks again!
I checked and plus the superseding still contain version 14. The author notes on the that they will no longer be publishing to that site, and indeed the latest version available for download there is still 14. So the metadata for that extension may need to be manually overridden in nixpkgs since it is not going to get the latest from via the automated update process.
This works as a standalone package, for inclusion in you'd probably be fine not declaring ,,. Would be happy to make a PR for it, though it's not something I'd actively mantain/use myself. Just updating the metadata itself wont do, as it would still be pulling from for nonexistent files.
Looks good! That updated package does fix the crash for me.
did you just install the package from nixos?
yes, it seems then having its own package would be the best no?
Ah no, it would need a PR to even get into nixpkgs. I just it to my local config using an overlay.
okay, well I will look into how to overly in a nix file. Also, it is hard to maintain a package? As, maybe I could learn how to maintain this extension if will be unable to maintain it?
Maintaining an extension like this should be as simple as increasing the version number when a new release exists, given it's lack of external dependencies or nixos-specific quirks that need to be patched (there may be some out there). What I meant by not mantaining it is that I do not actively use it within my setup. And I assume these manually packaged ones would need at least a "reference" mantainer to keep it in check and direct issues to.
Thanks for the good info ! Well, I can be the maintainer, but I might need help from time to time. I will use your code if that is okay? So, next steps to put in the PR and then add me as the maintainer. Also, would you want to be on this as well?
piegamesde was only the maintainer of the original extension package because they're the . Manually packaged extensions go in and generally have a maintainer attribute set.
Circling back to this... I would like to be the maintainer of this plugin. However, I have never maintained a piece of software on github and I only have minimal skills with shell and nix configuration files. I have never made or packaged a nix module before. Should this task be reserved for someone else with more skills or is there someone who could mentor me in how to be a maintainer? Thank you all for the help in this.
Added this to extension creator's github :
Okay, I figured out how to add 's code into my existing setup. For all the noobs out there this is what I did it: I did NOT use the "overlay" process in NixOS as describe here: I used the process as described here: This is an excellent write up BTW! Save this link for future use. With these resources in mind, this is what I did. I used 's code and named the file . This naming is arbitrary. It can be anything you want as long it has at the end. Then, move that file into directory. Do this via terminal and you must be the user. Then in my NixOS (not nix) configuration file () I simply into the Then, like always, as root This is all explained in the link above. Limitations: hack does not put the new is in the official repository.
This needs to be done by someone and they will become the maintainer. you use this hack you will have to update the for NixOS whenever the developers of release a new update.
Upstream devs released version 16. Whoo hooo! Here is the .nix to make it work on your local machine. Again, this is not in the main nixpkgs repo. You will have to use this code and follow my "hack"above to get it to run in your local nix install. Thanks again to for the original code.
Package name: gummy Latest released version: 0.6.0 <!-- Search your package here: --- Current version on the unstable channel: 0.3 Current version on the stable/release channel: 0.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! --- There is an open pull request () by from October 2023, but it has not been merged and later versions of the program have been released since then. I think it is also worth noting that the source code repository of the is no longer available on GitHub. as the repository has moved to Codeberg (see ). Notify maintainers (last updated the package) <!-- 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]:
I updated my linked PR to the latest version.
Thank you for updating it so quickly! Is there a time frame in which we can expect the pull request to be merged by someone?
Package name: gummy Latest released version: 0.5.4 <!-- Search your package here: --- Current version on the unstable channel: 0.3 Current version on the stable/release channel: 0.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 I've tried to bump the version to 0.5.4. <details<summaryThe build fails when downloading json-poputlate</summary</details<!-- If the result shows no maintainers, tag the person that last updated the package. --
Package name: itch Latest released version: 26.1.3 Current version on the unstable channel: 26.1.3 Current version on the stable/release channel: 26.1.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! --- The current version is broken since butler is marked broken 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]:
The latest version on seems to be 26.1.3 which is used in the package.
There is 26.1.5 as a source code , but current package uses binaryBytecode
libgtop is not reproducible, since it embed the output of into one of its binaries. See or build on 2 machines with different kernel versions. Report attached since r13y will not keep it, I think: libgtop build should be reproducible. This patch works from a nixpkgs perspective: However, it should ideally be reported and fixed upstream. N/A Maintainer information:
I marked this as stale due to inactivity. &rarr;
Description Attempting to install conan with nix-env on Mac OS X errors out with the following message: To Reproduce Steps to reproduce the behavior: Expected behavior As Mac OS X is a supported platform for conan, it's expected that it would install. Additional context This appears to be due to conan's dependency on the python3-distro package, which only compiles on Linux architectures. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(tclemons): channels(root): nixpkgs:
There is about the use of imagemagick in NextCloud due to . Admins may want to disable it unless they are certain that users won't upload untrusted files (which can easily happen by accident if folder sync is active). NextCloud is only passing certain file types to imagemagick but it is doing so based on the file extension. Therefore, an attacker can pass any file type to imagemagick. I have tested this with a PNM image (not supported by NextCloud) that I have renamed to . doesn't get a preview image but does, i.e. NextCloud thinks it is HEIF and passes it to ImageMagick, which processes it as PNM. There are several ways to disable imagick: in the NextCloud config. This will not only disable imagick but also previews for PNG and JPEG (which do not use imagick). in the NextCloud config. This may need manual adjustment after a NextCloud update. the extension for PHP. This also disables it for NextCloud plugins. Option 1 and 2 can already be used by an admin if the drawbacks are acceptable. However, I think 3 is the best option in most cases. has options that disable the other PHP extensions that used to be by default. I think we should do the same for imagick. If imagick is disabled, NextCloud will automatically disable the preview generators that need it. It will also show a warning about that (which is subject to debate in the issue linked above) and there may be some implications for the themes app (which I don't use). Therefore, I think we should keep imagick enabled by default and leave the decision to the admin. We could also add a suitable policy for ImageMagick and thereby disable any file formats or features that are considered insecure. I don't think I could write such a policy and be sure that it is secure (or even "secure enough"). In addition, we will have to keep it up-to-date with newer versions and CVEs. That is why I recommend that we only add a simple off switch. The above information is based on NextCloud 20. I will wait until and NextCloud 21 have landed in nixos-unstable (and on my server) and then test again and create a PR if there is any interest in having this upstream.
Ouch, decisions based purely on a file ext is a behavior that sounds pretty broken to me :/ Optiobally disabling imagemagick and adjusting the config accordingly sounds reasonable to me, so feel free to file a PR. You can ping me for a review or if you need assistance with modifying the module :)
It's ok for what they do with it. It won't do double duty as a mitigation but I guess that was never intended. Thanks. Any suggestions on a name for the new option? Simply ? Should I add any tests for that? The existing tests only test three different configurations so adding one just for imagick seems like overkill. It should be quite easy though. If we want to test that previews actually aren't generated... Well, that's a different story. We would have to automate the web interface, for that. I think the existing tests are only testing the service, CLI and WebDAV.
As imagemagick enabled will remain the default, I'd suggest . Yes, adding a fourth VM test just for imagemagick is indeed an overkill IMHO since those tend to be fairly expensive. I'd suggest to write a testcase in , other integrations such as are also tested there. Right that could be a non-trivial thing to solve. Maybe check if there's a REST API or a way to implement this with the CLI of . But I don't think it'd be worth spending too much time on this if there's no reasonable way to test :)
I think we still want to test the default option in so we will need a second configuration that disables imagick. We don't have to start that VM if we only want to check whether imagick is in its closure. As there isn't any test helper for that, we probably don't want to do that though ;-) see Unfortunately, qemu on ARM is too unreliable for the automatic tests because qemu crashes when started on one of the little cores (i.e. 4 out of 6 times). I have done some interactive testing of the above commit but not an automated run. I will have to find some system that is not ARM, not high-security, not already virtualized...
Qemu/KVM does work if a kernel build or stress-ng is hogging the big cores :) is ready for review.
Imhex failed to start. Steps to reproduce the behavior: -shell -p imhex --run imhex Shows the following errors: Imhex start up normally. Adding -v, --verbose doesn't give more information. I don't know how to either.
Maintainer ping:
Can repro on master, but can't repro if I checkout and build from it, it should be possible to bisect and find out at what point this broke.
First bad commit: <details<summarygit bisect log</summary</details
Seems there's a bunch of upstream reports of breakage with glfw 3.4
This might be fixed with The PR was merged into 1.90.6, but 1.33.2 contains a vendored 1.90.4, which doesn't contain the fix. My guess is that updating from the current 1.33.2 in nixpkgs to the latest version upstream (1.35.3 as of today) should fix the issue, as the latter contains a vendored updated to version 1.90.8, which should contain the fix.
Looks like the PR was closed, are you talking about instead?
Yes, sorry. I got the PR reference from: ... which also references the commit you mentioned.
Still crashes on imhex 1.35.3, which I more or less expected.
After applying both PRs and , finally works on my system with the current . Note: both PRs were needed, either one alone didn't fix all the issues for me.
Solved, marking as closed.
<!-- 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: gvm-libs <!-- 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: 21.4.2 desired version: 21.4.3 <!-- 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 NetworkManager is a particularly important component and we don't have any tests for it that could block a channel advance. In particular, a change can happen on nixos-unstable leaving users without functioning networking, and while rollbacks are possible it isn't an excuse to allow that to reach production systems. NixOS doesn't produce either. Manual testing is also cumbersome if we want to make a new stable release. Upstream NetworkManager does have some integration testing but obviously not useful to us. I think to start, if we at least had a test that verifies the services start without issues would be great.
Agreed. While developing tests for the multipath TCP module I was surprised to see no networkmanager module. I had some difficulties with the nixos test infrastructure at first because the test infra will by default install a slirp interface () and it messed up the interface naming. Like I would clear but interfaces would still be named starting from instead of . Just thought I would mention it in case the brave soul writing the test is interested in multihoming. (but that's more a concern I have with the test infra).
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 .
Bleh.
I marked this as stale due to inactivity. &rarr;
consequences of our inactions