jiebi/CodeConvo huggingface dataset:
, CVSSv3=7.5 (nixos-21.05) CVSSv3=7.5 (nixos-21.05) CVSSv3=7.5 (nixos-21.05) NLnet Labs Routinator prior to 0.10.2 happily processes a chain of RRDP repositories of infinite length causing it to never finish a validation run. In RPKI, a CA can choose the RRDP repository it wishes to publish its data in. By continuously generating a new child CA that only consists of another CA using a different RRDP repository, a malicious CA can create a chain of CAs of de-facto infinite length. Routinator prior to version 0.10.2 did not contain a limit on the length of such a chain and will therefore continue to process this chain forever. As a result, the validation run will never finish, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all. In NLnet Labs Routinator prior to 0.10.2, a validation run can be delayed significantly by an RRDP repository by not answering but slowly drip-feeding bytes to keep the connection alive. This can be used to effectively stall validation. While Routinator has a configurable time-out value for RRDP connections, this time-out was only applied to individual read or write operations rather than the complete request. Thus, if an RRDP repository sends a little bit of data before that time-out expired, it can continuously extend the time it takes for the request to finish. Since validation will only continue once the update of an RRDP repository has concluded, this delay will cause validation to stall, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all. NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data.
On aarch64-darwin, while neovide does build and install successfully and I can launch it from the terminal, there is no app bundle that can be found in finder to launch neovide from there or pin it to the dock to launch from. Once opened the global menu calls it .neovide-unwrapped and the icon in the dock is a blank white page as a generic icon. I can only assume that once is fixed, that this will also be applicable to x86_64-darwin Steps to reproduce the behavior: neovide as either a system app in nix-darwin or a user app in home-manager on aarch64-darwin An app bundle name that will be linked into or depending on and usage I'd like to point out that the global menu title is .neovide-unwrapped to for sure indicate that this is the nix neovide and not the homebrew neovide ! ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Following PR MacOS app information a few days ago: We can install the files with next release of neovide.
Unable to build libxml2 Repro: nix-env -i libxml2 make[4]: Entering directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' CC CC libxml2- CC libxml.c:1649:43: warning: passing 'unsigned char ' to parameter of type 'const char ' converts between pointers to integer types with different sign [-Wpointer-sign] message = libxmlcharPtrConstWrap(ptr); ^~~ ./libxmlwrap.h:240:48: note: passing argument to parameter 'str' here PyObject libxmlcharPtrConstWrap(const char str); ^ 1 warning generated.
CCLD ld: library not found for -lintl clang-7: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: [Makefile:600: ] Error 1 make[4]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[3]: [Makefile:694: all-recursive] Error 1 make[3]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[2]: [Makefile:528: all] Error 2 make[2]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[1]: [Makefile:1479: all-recursive] Error 1 make[1]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make: [Makefile:893: all] Error 2 builder for '/nix/store/xcqdl8cfjjbjvh7g9ka0ip3r4awy80a8-libxml2-' failed with exit code 2 error: build of '/nix/store/xcqdl8cfjjbjvh7g9ka0ip3r4awy80a8-libxml2-' failed Metadata* system: host os: multi-user?: sandbox: version: channels(swarnpriya): nixpkgs:
Disclaimer: I barely know what I'm doing. I tried adding as a build input to libxml2. That got this error:
I've been getting this as well, since . Any clue? I think this sort of thing has happened before, but I don't recall the details.
I thought somebody else already fixed this after some discussion no irc. My proposal was essentially the patch above but guarded for python2 only.
Steps to reproduce the behavior: Commit seems likely to have broken the build for bitsandbytes. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I suspect the above output is related to that commit modifies or creates the module referenced above. I'm rebuilding setting the to and to to see if having dummy definitions solves the problem. Unfortunately it's slow going as it requires a full pytorch rebuild to see if it repaired bitsandbytes.
the trivial fix proposed above appears to resolve the build. Not sure if this would have ramifications elsewhere in the tree. Happy to PR the change if others want to help kick the tires
Oh!!! was mean to be a not ... how on earth did this even pass the tests (i.e. I only meant to abuse python's imperative-ness to override and keep all other symbols intact...)
a PR would be very welcome
looks like your original idea should also work, and be less broken in mysterious ways, I can do a quick PR after I make sure it works on my end.
Gotenberg crashes immediately on startup Enter the following into your nix config: It not crashing but starting up normally ! Gotenberg was to be used in conjunction with paperless-ngx. is the entire file Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Are there any more logs from the Gotenberg service? Or is the coredump all that's available?
Sadly that is all. The service log literally doesn't say anything. There you only see that the service started and immediately exited. This log i got by typing
Sorry for the slow response, but I looked at this and figured out the issue. Could you test and see if it fixes your issue?
Describe the bug After upgrading to NixOS 20.03, sudo often (but not always) segfaults: From the logs: Disabling appears to have made this problem to away, so the problem may be in . Metadata NixOS 20.03..
Maybe the patch to use a not insecure openssl is the source of the issue for you
same issue here - the sourceforge repo is way old, there's a github mirror but not maintained either, and there's a fork of the mirror which includes fixes for openssl 1.1.1:
I marked this as stale due to inactivity. &rarr;
Hmm, kinda forgot about this
I missed the fact that the "supported" branch didn't actually include the patch to fix this.
I saw the following during a rebuild: Error in file "/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-": "font/ttf" is an invalid MIME type ("font" is an unregistered media type) Error in file "/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-": "font/ttf" is an invalid MIME type ("font" is an unregistered media type) Error in file "/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-": "font/opentype" is an invalid MIME type ("font" is an unregistered media type) Error in file "/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-": "font/collection" is an invalid MIME type ("font" is an unregistered media type) Unknown system: host os: multi-user?: sandbox: version: nixpkgs:
I think we just need to update , c.f.
Ah, it seems that upstream has not released a version with the fixed commit in. The last tagged release was , they haven't tagged anything with the fix commit in. We could build from their git head, I guess, although I'm reluctant to do so. Perhaps complain ?
If the commit applies as a patch that would also be fine.
I'm still having this. had it for build and build (separately). build
Steps to reproduce the behavior: pyload-ng <!-- 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]:
Thank you for notifying me, the failure is caused by the lib not yet working on python 3.12. Apparently the git upstream of pyload replaced it with which I'm packaging in , so once that's done I'll get around to updating pyload (will probably have to switch to the git version since they rarely upload new releases to pypi). For now you can override the python version as a workaround:
The override works great. Thanks!
Hi there! I’m sorry to bother you with a ping. We realized that in the form of . All of our Nix expressions are meant to be MIT‐licensed, so this is a big problem, especially as packages using / may count as derivative works, potentially jeopardizing the licence status of Nixpkgs as a whole. We would therefore like to get permission from all contributors to this code to relicense their changes under the MIT license used for Nixpkgs. If you have any questions or concerns about this, please ask them in so that this issue can purely be for tracking the sign‐offs we’ve received. To agree to the relicensing, please reply to this issue with the following verbatim text: [x] [x] [x] [x] [x] [x] (confirmed via email) [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [ ] [x] [x] [ ] (GitHub account is gone, although as this was just a treewide removal with no other changes it’s unlikely to be copyrightable) [x] Authors of unmerged pull requests in the old repository (just in case we ever take code from them): [x] [x] [ ] [x] [ ] [x] [x] [x] (I have not checked for unmerged PRs to this part of Nixpkgs yet because it’s a pain.)
Apparently I can only ping so many people at once; please look at the original issue text, sorry!
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs. PS: nice catch and thanks for taking care of it
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs. Like, sure, we still use it in our toolchain, and this move is very nice.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , and the pkgs/development/tools/yarn2nix-moretea directory of the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs or any other OSI considered free software license. IIRC if we get everyone else on the list, then will be fine.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
Just another gentle ping; if you could check the original post at respond as requested it’d help us resolve this licensing issue.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
While it wouldn't hurt to get approval from the last 4 people, I don't think we need that to move ahead: gebner only authored , a minimal change that I don't think would be copyrightable egasismus only authored , another minimal change that I don't think would be copyrightable chawki008 only authored a PR that was never merged: eqyiel also only authored a PR that was never merged:
Yeah, I agree those changes aren’t copyrightable. I did email the authors of them but I’ll proceed with opening a PR to do the relicensing now.
I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.
Thanks so much to everyone for helping get this done so quickly, and for your contributions to the Nixpkgs ecosystem
All expressions in nixpkgs are supposed to be MIT licensed, but is licensed under GPL-3.0. as an externally developed project under different licensing terms that we use for nixpkgs. It was merged into nixpgks in without the license being changed to MIT or a compatible license. Every package using is using improperly licensed expressions, which at the time of writing looks to be a bit more than 25 packages. I have two proposed solutions, neither of which are particularly appealing: -license under MIT This would require assembling relicensing signatures from all existing yarn2nix authors which include both contributors when it was in nix-community & in nixpkgs. It's gonna take some time and keep us in license non-compliance in the mean time. , migrate packages to something else The newly looks like a good contender as pointed out by in chat. CCing authors and other relevant parties Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Just to repeat what I said on Matrix, if we can’t figure out something better in a few days I will open a relicensing issue and start the work of pinging all the contributors. Reimplementing it sounds nice, but I suspect it would take quite a while given the speed at which Nixpkgs language ecosystems tend to move.
yarn2nix can be easily misused and trigger IFD. I think too that in the long run we should replace it. Maybe yarnBuildHook/yarnConfigHook from are already enough and the package can easily be migrated?
(Nixpkgs potentially actually being GPLv3 is very much a bug IMO.) Migration is all well and good, but we probably ought to try to relicense anyway: we can’t change old revisions of Nixpkgs and it’s not good for multiple years of Nixpkgs history to be under unclear licensing conditions.
I guess re-licensing is the better way for now? We can ping all the contributors, from a glance I read most of the names before.
Yes, I think we should probably at least try. I will open a new GitHub issue for it today so that we can discuss here without it getting bogged down in rote responses.
Okay, here we go I guess:
Oof, thank you for trying to clean up that mess.
I just got the notification from the tracking issue and I feel that a big portion of any blame should go towards my direction because of the introduction in , rather than While I (try to) put a lot more thought into licenses today, it didn't cross my mind back then that vendoring with the included license could have such implications.
No worries – thanks for trying to improve the Node packaging situation in Nixpkgs and for your quick reply to the ping! This is an institutional failure IMO, and I think that it would have been caught before merge these days.
seems still active. It might be worth posting the same as on Discourse if you want people's replies to be public (unlike with email).
The project seems slow with releasing the latest changes, which (among other things) includes Package name: tiramisu Latest released version: 2.0., I suggest using the latest commit instead since there is no newer release yet <!-- Search your package here: --- Current version on the unstable channel: 2.0. Current version on the stable/release channel: 2.0. <!-- 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.
Package name: fluent-gtk-theme Latest released version: 2024-04-28 <!-- Search your package here: --- Current version on the unstable channel: 2023-06-20 Current version on the stable/release channel: 2023-06-20 <!-- 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]: