id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
271228694 | Keybase GUI shouldn't check hardcoded /keybase mountpoint
Issue description
The keybase-gui wrapper checks for a hardcoded value to see if kbfs is mounted there.
However, this is configurable through the kbfs service, and defaults to ~/keybase.
The wrapper should either be hard-coded to whatever options.services.kbfs.mountPoint is, or verify the status some other way (e.g calling keybase status).
Steps to reproduce
Set the following in configuration.nixservices.keybase.enable = true;
services.kbfs.enable = true;
nix-env -iA nixos.keybase-gui
rebuild your configuration
try to launch keybase-gui
Expected behavior
Tests pass and keybase-gui launches.
Actual behavior
Keybase is not mounted to /keybase.
You might need to run: kbfsfuse /keybase
Set NIX_SKIP_KEYBASE_CHECKS=1 if you want to skip this check.
Technical details
System: 18.03pre119292.cfafd6f5a8 (Impala)
Nix version: 1.11.15
Nixpkgs version: 18.03pre119292.cfafd6f5a8
Sandboxing enabled: false
^ added hardcoded ~/keybase
Hi @brainrape ,
While this does look like it'll work in most scenarios it doesn't solve the overall problem in #31261 as it's now just looking at two options of hardcoded mountpoint. A better solution would be to have the wrapper (I may have used the wrong word, if so, sorry) check for where keybase is mounted and then use that.
Are we not able to do that instead?
Updated PR with suggested fix.
@brainrape status?
Waiting for merge. @ mentioned maintainer.
| gharchive/issue | 2017-11-04T21:42:52 | 2025-04-01T06:37:18.556882 | {
"authors": [
"5paceToast",
"IvanMalison",
"brainrape",
"joncojonathan"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/issues/31261",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2341790926 | Update request: flutter 3.22.0 → 3.22.2
Package name: flutter
Latest released version: 3.22.2
Current version on the unstable channel: 3.22.0
Current version on the stable/release channel: 3.22.0
[x] Checked the nixpkgs pull requests
Notify maintainers
@NixOS/flutter
Note for maintainers: Please tag this issue in your PR.
Add a :+1: reaction to issues you find important.
I can get this later today
I can get this later today
Thank you!
@Henry-Hiles #318396
I'll test that tomorrow thanks!
| gharchive/issue | 2024-06-08T19:10:49 | 2025-04-01T06:37:18.561726 | {
"authors": [
"Henry-Hiles",
"RossComputerGuy"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/issues/318344",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
299814629 | tmux "crashes???" when konsole tab is closed
Issue description
I've been using Konsole for years and it works great with tmux. However since a few days ago on unstable small, when I close a Konsole tab, the tmux session "in that tab" gets killed/stopped or whatever....
Steps to reproduce
Use nixos-uunstable-small
Open Konsole
SSH into server
Start TMUX session
Right-click the konsole server tab and close it
Open new tap, ssh into same server again
Try to attach tmux
--> https://youtu.be/-hXLPQfoI70
This has been happening not longer than 2 weeks I think... maybe even less than 1 week - not sure how long but not very long.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
system: "x86_64-linux"
host os: Linux 4.14.21, NixOS, 18.03pre129183.a3c96fd4de3 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(hyper): ""
channels(root): "nixos-18.03pre129183.a3c96fd4de3"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs
Ok, I tested this on another server - same behaviour:
system: "x86_64-linux"
host os: Linux 4.9.81, NixOS, 18.03pre128357.327a84749ed (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(root): "nixos-18.03pre128357.327a84749ed"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs
If I do this on a non-nixos server it all works fine.
I tested on a third server - this time I get the expected behaviour:
system: "x86_64-linux"
host os: Linux 4.9.75, NixOS, 18.03pre124914.b9806751074 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(root): "nixos-18.03pre124914.b9806751074"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs
(so all works fine here)
Git bisect blames 672bb6b4abd27d9b2796152522b54f5b82c9f76b, I don't really see anything suspicious in there.
@LnL7 can you track this down with sysdig?
I'm not sure how much time I'll have this weekend, it's pretty easy to reproduce if anybody else wants to take a shot at it. Tmux will die when the ssh connection closes.
{ config, lib, pkgs, ... }:
{
services.mingetty.autologinUser = "root";
virtualisation.graphics = false;
users.users.foo = {
uid = 1000;
group = "foo";
isNormalUser = true;
openssh.authorizedKeys.keys = [ "..." ];
};
users.groups.foo = { gid = 1000; };
environment.systemPackages = [ pkgs.tmux ];
services.openssh.enable = true;
}
export QEMU_NET_OPTS="hostfwd=tcp::3000-:22"
nixos-rebuild build-vm -I nixos-config=foo.nix -I nixpkgs=.
./result/bin/run-nixos-vm
ssh -i ./foo_rsa -p 3000 foo@127.0.0.1
Git bisect blames 672bb6b4abd27d9b2796152522b54f5b82c9f76b, but I don't really see anything suspicious in there.
One thing that may be related is that it brings 1de98e85681e7d1028fe866fa220c05ce1ed842f, "plasma: 5.11.5 -> 5.12.1".
@LnL7 ah now, this is a different one. You need lingering enabled in logind, otherwise tmux get killed once, you close your ssh connnection, because your logind seat gets deallocated: https://github.com/NixOS/nixpkgs/issues/29234#issuecomment-340230209
@sjau are you experiencing this on a server via ssh or locally in konsole?
I've seen that issue with nix-build, tmux works fine it uses /tmp/tmux-$UID for the socket.
@Mic92
I experience this via ssh.... I tested it on 3 nixos servers... the 2 newer ones have that isse, an older one doesn't. Also non-nixos server don't have that issue either.
I'm affected by this issue as well, except I'm using rxvt-unicode as the terminal
Btw, it only happens if I start tmux as normal user. When I login by ssh as root user, start tmux, close the konsole tab and re-login, the tmux session is still running
This can be fixed by doing loginctl enable-linger $USER, where $USER is your user.
enable-linger does not change the behaviour.
Note that there's also nothing systemd related in bad commit git bisect ended up in.
I also tested it and the offending comit that I found was
f5e96d3e1b7 xz: set CONFIG_SHELL to /bin/sh, fix retained reference to bootstrap
I tested it now also on a live server - reverting back to commit 122fa75b2de619ceace4b94a613683e54c34ddd0 makes tmux run properly again.
Ok, it might not be that commit as I used
git log --oneline b9806751074..327a84749ed
and those two commits are adjacent
Maybe both enabling lingering and using systemd-run is needed?
cc https://github.com/NixOS/nixpkgs/issues/15798#issuecomment-222352494
Hmm, I tried this but it failed to start due to permissions?
Feb 26 05:52:42 gravity polkitd[8886]: Registered Authentication Agent for unix-process:9169:30559097 (system bus name :1.31 [/run/current-system/sw/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Feb 26 05:52:42 gravity systemd[5382]: run-rff29cc1b2fea4c84ad8787b5f7c40649.scope: Failed to add PIDs to scope's control group: Permission denied
Feb 26 05:52:42 gravity systemd[5382]: run-rff29cc1b2fea4c84ad8787b5f7c40649.scope: Failed with result 'resources'.
Feb 26 05:52:42 gravity systemd[5382]: Failed to start /run/current-system/sw/bin/screen hydra.
Perhaps related: https://bbs.archlinux.org/viewtopic.php?id=227953
Is this really desirable default behavior? If so, should probably be mentioned in release notes....
From https://bbs.archlinux.org/viewtopic.php?pid=1724323#p1724323 possible hint:
Ok, it seems that the distro package maintainer enabled systemd hybrid cgroup without kernel support.
Or maybe -Ddefault-kill-user-processes=false? It does seem rather hostile default behavior.
@dtzWill long long time ago, when this specific crazy change in systemd started affecting NixOS, we did add KillUserProcesses=no into logind.conf and never removed it. Because the default systemd behaviour is indeed hostile to any user who has a chance to install NixOS on their own.
Oh, well hooray for that ^_^. Good to know.
Chasing that:
$ find -L /run/current-system -name "logind.conf"
/run/current-system/etc/systemd/logind.conf
/run/current-system/systemd/etc/systemd/logind.conf
One of which sets KillUserProcesses=no nicely and the other does not. Hopefully/presumably the other is just an example/dead-end. Hmm.
Erm, maybe this is the problem? Poking at loginctl to try to see what it is reading from or what config it ends up with led me to try:
$ loginctl -p KillUserProcesses show-session
KillUserProcesses=yes
(I'm not a systemd expert, can someone take a look? Thanks!)
@dtzWill Thanks for the debugging. This is probably a regression due to the recent systemd update. I can confirm that I have KillUserProcesses=no in /etc/systemd/logind.conf but loginctl -p KillUserProcesses show-session will print KillUserProcesses=yes.
@fpletz @dtzWill I looked into that using sysdig it only tries to read ${pkgs.systemd}/etc/systemd/logind.conf, but not /etc/systemd/logind.conf. That's why configuration is never applied.
I made a pull request to our systemd fork that fixes the issue.
| gharchive/issue | 2018-02-23T18:56:06 | 2025-04-01T06:37:18.584236 | {
"authors": [
"7c6f434c",
"LnL7",
"MP2E",
"Mic92",
"dtzWill",
"fpletz",
"orivej",
"sjau"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/issues/35415",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
761225912 | bumpver: 2020.1107 -> 2020.1108
Motivation for this change
Update bumpver to last version
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[ ] NixOS
[ ] macOS
[x] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 106551 1
1 package built:
bumpver
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/405
| gharchive/pull-request | 2020-12-10T13:07:00 | 2025-04-01T06:37:18.591604 | {
"authors": [
"kfollesdal",
"nixos-discourse"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/106551",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
792616001 | nixos/nomad: fix data_dir-default-not-propagating bug
nixos/nomad: add newline
nixos/nomad: move data_dir default setting to allow propagation of default
Motivation for this change
The value of data_dir in the nomad module was only
set to its default if settings was not overridden at all.
This PR fixes the issue so that you can override settings
without having to specify the default value of data_dir.
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Once https://github.com/NixOS/nixpkgs/pull/109761 is landed I will update the test here by removing the explicit data_dir setting.
Once https://github.com/NixOS/nixpkgs/pull/109761 is landed I will update the test here by removing the explicit data_dir setting.
Thanks for merging!
Thanks for merging!
| gharchive/pull-request | 2021-01-23T17:52:11 | 2025-04-01T06:37:18.599387 | {
"authors": [
"cpcloud"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/110614",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
802983934 | sharness: Init at 1.1.0-dev
Motivation for this change
A simple portable shell library to write and run tests adhering to the Test Anything Protocol.
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Updated.
Result of nixpkgs-review pr 112309 at 44b06c61 run on aarch64-linux 1
1 package built:
sharness
| gharchive/pull-request | 2021-02-07T15:50:19 | 2025-04-01T06:37:18.604173 | {
"authors": [
"r-rmcgibbo",
"spacefrogg"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/112309",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
810442813 | python37Packages.django-auth-ldap: 2.2.0 -> 2.3.0
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.django-auth-ldap is: "Django authentication backend that authenticates against an LDAP service"
meta.homepage for python37Packages.django-auth-ldap is: "https://github.com/django-auth-ldap/django-auth-ldap"
meta.changelog for python37Packages.django-auth-ldap is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
Warning: a test defined in passthru.tests did not pass
0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 2.3.0 with grep in /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0
directory tree listing: https://gist.github.com/7bf054df94955bd3decdb01135a3d207
du listing: https://gist.github.com/a1e51bef52b9f35a33d7a8dbbc37e91b
Rebuild report (if merged into master) (click to expand)
9 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.django-auth-ldap https://github.com/r-ryantm/nixpkgs/archive/d158476f6d35ea676cb44fa0b125aa584a03a8b0.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0
ls -la /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
3 packages built:
python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap
Maintainer pings
cc @mmai for testing.
Result of nixpkgs-review pr 113482 at d158476f run on aarch64-linux 1
3 packages built:
python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap
| gharchive/pull-request | 2021-02-17T18:46:49 | 2025-04-01T06:37:18.615808 | {
"authors": [
"r-rmcgibbo",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/113482",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
814999722 | zeek: 3.2.3 -> 3.2.4
Motivation for this change
https://github.com/zeek/zeek/releases/tag/v3.2.4
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[x] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 114198 run on x86_64-linux 1
1 package built:
zeek
| gharchive/pull-request | 2021-02-24T01:43:14 | 2025-04-01T06:37:18.622059 | {
"authors": [
"fabaff",
"marsam"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/114198",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
826994917 | liburcu: 0.12.1 -> 0.12.2
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/liburcu/versions.
meta.description for liburcu is: "Userspace RCU (read-copy-update) library"
meta.homepage for liburcu is: "https://lttng.org/urcu"
meta.changelog for liburcu is: ""
Updates performed
Version update
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 0.12.2 with grep in /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2
directory tree listing: https://gist.github.com/1f47726e757fb7834481a662e34e6f23
du listing: https://gist.github.com/0493fa32bbae6ae5eac2181764686ce9
Rebuild report (if merged into master) (click to expand)
105 total rebuild path(s)
46 package rebuild(s)
46 x86_64-linux rebuild(s)
23 i686-linux rebuild(s)
9 x86_64-darwin rebuild(s)
27 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
appgate-sdp
aws-workspaces
bareos
bcachefs-tools
ceph
ceph-client
ceph-dev
codeql
coreclr
glusterfs
knot-dns
knot-resolver
libceph
liburcu
libvmi
lttng-tools
lttng-ust
multipath-tools
netsniff-ng
nfs-ganesha
ntirpc
osu-lazer
powershell
qemu_full
qemu_xen
qemu_xen-light
qemu_xen_4_10
qemu_xen_4_10-light
qubes-core-vchan-xen
samba4Full
sambaFull
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare
xen
xen-light
xen-slim
xenPackages.xen-light
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_10-light
xenPackages.xen_4_10-slim
xenPackages.xen_4_10-vanilla
xen_4_10
xen_4_10-light
xen_4_10-slim
zoxide
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A liburcu https://github.com/r-ryantm/nixpkgs/archive/af3185cdf18dea307f76a0550436c9e29b45f628.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2
ls -la /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
2 packages marked as broken and skipped:
bareos
samba4Full
8 packages failed to build:
coreclr
libvmi
qemu_xen (qemu_xen_4_10)
qemu_xen-light (qemu_xen_4_10-light)
qubes-core-vchan-xen
xen
xen-light
xen-slim
23 packages built:
appgate-sdp
aws-workspaces
bcachefs-tools
ceph
ceph-client
codeql
glusterfs
knot-dns
knot-resolver
libceph
liburcu
lttngTools (lttng-tools)
lttngUst (lttng-ust)
multipath-tools (multipath_tools)
netsniff-ng
nfs-ganesha
ntirpc
osu-lazer
powershell
qemu_full
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare
zoxide
Maintainer pings
cc @bjornfor for testing.
nixpkgs-review successful on macos 10.14
| gharchive/pull-request | 2021-03-10T02:55:58 | 2025-04-01T06:37:18.634665 | {
"authors": [
"r-ryantm",
"risicle"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/115679",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
854726924 | python3Packages.pyezviz: init at 0.1.8.7
Motivation for this change
Python interface for for Ezviz cameras
https://github.com/baqs/pyEzviz/
This is a Home Assistant dependency.
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 118920 run on x86_64-linux 1
2 packages built:
python38Packages.pyezviz
python39Packages.pyezviz
Result of nixpkgs-review pr 118920 at cb564f15 run on aarch64-linux 1
2 packages built successfully:
python38Packages.pyezviz
python39Packages.pyezviz
| gharchive/pull-request | 2021-04-09T17:35:48 | 2025-04-01T06:37:18.641968 | {
"authors": [
"fabaff",
"r-rmcgibbo"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/118920",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
863540735 | zoom-us 5.6.13632.0328 -> 5.6.16775.0418
Motivation for this change
zoom-us currently is in a broken state.
Version 5.6.13632.0328 is blocked from participating in calls, and fails with a "please upgrade to the latest version" message. At the same time, the tar file that is supposed to be version 5.6.16775.0418 is bit-identical to the previous version.
Thus, no upgrade path to fix the issue is currently available using a tar file.
In consequence, this PR upgrades to the current version using the .deb file provided by Zoom for Debian/Ubuntu.
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.
backport: https://github.com/NixOS/nixpkgs/pull/120038
Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.
Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.
Thanks for the update. Using the tarball again in https://github.com/NixOS/nixpkgs/pull/120243 - targeting master and in https://github.com/NixOS/nixpkgs/pull/120242 a backport + fix for the stable channel.
| gharchive/pull-request | 2021-04-21T07:33:45 | 2025-04-01T06:37:18.650372 | {
"authors": [
"LutzCle",
"Mic92",
"doronbehar"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/120032",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
915389060 | [21.05] Staging next
Motivation for this change
Jobset: https://hydra.nixos.org/jobset/nixpkgs/staging-21.05
previous 21.05 staging next PR: #124341
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[ ] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
I think I'll pause these stable branch staging-next's until hydra recovers. (<60k queued builds)
I don't think that is needed. Typically the phase of jobset just discovering builds already in cache is quite fast.
I don't think that is needed. Typically the phase of jobset just discovering builds already in cache is quite fast. EDIT: it seemed (mostly?) done when I first posted this comment already.
staging-next-21.05 shares haven't been dialed back from stabilizing the release. Most jobsets have <1000 shares, staging-next-21.05 has 20M https://hydra.nixos.org/jobset/nixpkgs/staging-next-21.05#tabs-configuration
OK, that might be set lower now if there's nothing really urgent, I suppose, but it seems just a matter of relative priorities.
| gharchive/pull-request | 2021-06-08T19:26:06 | 2025-04-01T06:37:18.658204 | {
"authors": [
"jonringer",
"vcunat"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/126251",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
936267060 | nixos/doc: convert "Chapter 58. Writing NixOS Modules" to CommonMark
Note for reviewers
Thank you for reviewing this PR. :-)
This PR also fixes a small typo in Example 58.12, it should be "Definition of attribute sets of submodules" :-)
The conversion of the examples is done manually, I handle examples in the following way:
The example itself:
::: {#ex-the-id-of-the-example .example}
::: {.title}
**Example: The Name of the Example**
:::
The content of the example.
:::
Mentioning a example:
See [Example: The Name of the Example](#ex-the-id-of-the-example) for more details.
It seems that CommonMark -> DocBook (using Pandoc) won't convert .example into <example></example>, but I still used .example because DocBook will be dropped one day and CommonMark -> HTML (using Pandoc) will produce <div class="example"></div> which I think will be fine to handle.
If you have a better idea about how to handle examples feel free to comment, thanks!
Motivation for this change
Related GitHub project
Related Discourse post
Things done
Do conversion of eight files from DocBook to CommonMark per RFC 72.
nixos/doc/manual/development/option-declarations.xml
nixos/doc/manual/development/option-types.xml
nixos/doc/manual/development/option-def.xml
nixos/doc/manual/development/meta-attributes.xml
nixos/doc/manual/development/importing-modules.xml
nixos/doc/manual/development/replace-modules.xml
nixos/doc/manual/development/freeform-modules.xml
nixos/doc/manual/development/settings-options.xml
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Will update all options links (if any) to only use the URI fragment tomorrow.
| gharchive/pull-request | 2021-07-03T14:37:10 | 2025-04-01T06:37:18.668776 | {
"authors": [
"bobby285271"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/129136",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
965018550 | zeroadPackages.zeroad-unwrapped: make it build on Hydra
This time for real, I hope. I'm sorry for my incomplete advice;
the explicit dontRecurseIntoAttrs confused me about what's the default
behavior in here.
Things done
(nothing applies... no hashes change)
Oops, duplicate of https://github.com/NixOS/nixpkgs/pull/133379
I checked but a bit earlier...
| gharchive/pull-request | 2021-08-10T14:03:39 | 2025-04-01T06:37:18.670943 | {
"authors": [
"vcunat"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/133385",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
971071995 | haskellPackages.readline: fix Setup.hs to work with Cabal 3
See https://github.com/NixOS/nixpkgs/pull/111985/ for previous discussion
Motivation for this change
readline is broken for Cabal3 build. I fixed it previously in this pull request, but the fix seems to have disappeared. I just reapplied it.
Is there a better way to keep this fix in place for the future? As you can seen in the previous PR, we tried to reach the maintainers of this package but we didn't succeed.
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[ ] NixOS
[ ] macOS
[x] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[X] Fits CONTRIBUTING.md.
Is there a better way to keep this fix in place for the future?
It might be a better idea to send this PR to the haskell-updates branch, and then back-port this PR after it is merged in there.
Each nixos release is branched-off from the master branch here in nixpkgs. https://github.com/NixOS/nixpkgs/pull/111985 was sent to release-20.09, so it never ended up in master. Sorry for not let telling you about this at the time.
If you send a PR to haskell-updates, then it should get merged into master.
I think there is some sort of action that lets us automatically create a backport, so hopefully it is not too much additional work for you.
As you can seen in the previous PR, we tried to reach the maintainers of this package but we didn't succeed.
One thing I was wondering, is there a repo for this readline package on github? If so, can you create an issue or send a PR there and link to it from a comment in the code? If you are able to send a PR, then you should also just be able to fetchpatch from that PR, which would mean that we wouldn't need to carry this patch around in nixpkgs.
If there is no upstream repo, the we'll probably have to carry around this patch in nixpkgs.
If you send a PR to haskell-updates, then it should get merged into master.
I think there is some sort of action that lets us automatically create a backport, so hopefully it is not too much additional work for you.
Ok, thanks. I'll look into sending this to haskell-updates then.
One thing I was wondering, is there a repo for this readline package on github? If so, can you create an issue or send a PR there and link to it from a comment in the code? If you are able to send a PR, then you should also just be able to fetchpatch from that PR, which would mean that we wouldn't need to carry this patch around in nixpkgs.
If there is no upstream repo, the we'll probably have to carry around this patch in nixpkgs.
I could not find any upstream repo for this package the other time, but from a bit of googling I believe Jan Stolarek may be the maintainer, I have just sent an email to them.
Otherwise I could also upload the source to my github and host the patch there, but that is also relatively ugly as it would end up being a sort of fork from hackage.
Should I close this PR then? I'll open another one to haskell-updates
I went ahead and created the new PR https://github.com/NixOS/nixpkgs/pull/134295.
Still trying to find a maintainer in parallel :)
| gharchive/pull-request | 2021-08-15T07:34:38 | 2025-04-01T06:37:18.683097 | {
"authors": [
"cdepillabout",
"samuelrivas"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/134124",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
976416245 | helix: 0.4.0 -> 0.4.1
Motivation for this change
Update helix to 0.4.1
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 135311 run on x86_64-linux 1
1 package built:
helix
| gharchive/pull-request | 2021-08-22T16:29:46 | 2025-04-01T06:37:18.690095 | {
"authors": [
"figsoda",
"yusdacra"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/135311",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
993739079 | python38Packages.databricks-connect: 8.1.11 -> 8.1.12
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.databricks-connect is: "Client for connecting to remote Databricks clusters"
meta.homepage for python38Packages.databricks-connect is: "https://pypi.org/project/databricks-connect"
meta.changelog for python38Packages.databricks-connect is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
Warning: a test defined in passthru.tests did not pass
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/beeline passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/beeline.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/docker-image-tool.sh passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/find-spark-home passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/find-spark-home.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/find_spark_home.py passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/load-spark-env.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/load-spark-env.sh passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/pyspark passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/pyspark-bazel passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/pyspark.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/pyspark2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/quicksilver passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/run-example passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/run-example.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-class passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-class.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-class2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-shell passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-shell-bazel passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-shell.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-shell2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-sql passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-sql.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-sql2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-submit passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-submit.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/spark-submit2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/sparkR passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/sparkR.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/sparkR2.cmd passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/databricks-connect passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/.find_spark_home.py-wrapped passed the binary check.
/nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin/.databricks-connect-wrapped passed the binary check.
7 of 34 passed binary check by having a zero exit code.
32 of 34 passed binary check by having the new version present in output.
found 8.1.12 with grep in /nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12
found 8.1.12 in filename of file in /nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12
directory tree listing: https://gist.github.com/1e7f7e09854e24ae5a783adad9b6f8c8
du listing: https://gist.github.com/9838824d56b713b18b4f189666c6a0ea
Rebuild report (if merged into master) (click to expand)
8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python38Packages.databricks-connect
python39Packages.databricks-connect
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.databricks-connect https://github.com/r-ryantm/nixpkgs/archive/1b9987bfd9678179115c9cacd444e7bad8df3a36.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12
ls -la /nix/store/j94c31wa851c6vclbsfnj18k0750hgkr-python3.8-databricks-connect-8.1.12/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
2 packages built:
python38Packages.databricks-connect
python39Packages.databricks-connect
Maintainer pings
cc @kfollesdal for testing.
Result of nixpkgs-review pr 137347 at 1b9987bf run on aarch64-linux 1
2 packages built successfully:
python38Packages.databricks-connect
python39Packages.databricks-connect
| gharchive/pull-request | 2021-09-11T03:54:55 | 2025-04-01T06:37:18.715217 | {
"authors": [
"r-rmcgibbo",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/137347",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
998931973 | vscode-extensions.mvllow.rose-pine: init at 1.3.6
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
@ofborg eval
Result of nixpkgs-review pr 138225 run on x86_64-linux 1
1 package built:
vscode-extensions.mvllow.rose-pine
| gharchive/pull-request | 2021-09-17T04:39:03 | 2025-04-01T06:37:18.721725 | {
"authors": [
"VergeDX",
"bobby285271",
"figsoda"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/138225",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1021676078 | libwebsockets: 4.2.1 -> 4.3.0
Motivation for this change
Update to latest upstream release 4.3.0
Change log: https://libwebsockets.org/git/libwebsockets/tree/changelog
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 141090 run on x86_64-linux 1
1 package failed to build:
driftnet
4 packages built:
ardour
janus-gateway
libwebsockets (libwebsockets_4_3)
ttyd
On nixos x86_64:
builder for '/nix/store/20qgg23xpy1ykam4hriv1f7bixd4ia2x-driftnet-1.3.0.drv' failed with exit code 2; last 10 log lines:
194 | { NULL, NULL } // sentinel
| ^
httpd.c:194:9: note: (near initialization for 'mount')
httpd.c:194:9: warning: excess elements in struct initializer
httpd.c:194:9: note: (near initialization for 'mount')
make[2]: *** [Makefile:375: httpd.o] Error 1
make[2]: Leaving directory '/build/source/src/http_display'
make[1]: *** [Makefile:454: all-recursive] Error 1
make[1]: Leaving directory '/build/source/src'
make: *** [Makefile:428: all-recursive] Error 1
Diff LGTM. Haven't found time to test this yet. Upstream appears to have enabled -Werror by default, which I'd like to have disabled to decrease the burden for compiler upgrades. Otherwise changelog looks ok too.
| gharchive/pull-request | 2021-10-09T10:46:26 | 2025-04-01T06:37:18.730249 | {
"authors": [
"Mindavi",
"fabaff",
"risicle"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/141090",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1064704021 | skopeo: 1.5.1 -> 1.5.2
https://github.com/containers/skopeo/releases/tag/v1.5.2
Motivation for this change
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
[x] Fits CONTRIBUTING.md.
@ofborg eval
| gharchive/pull-request | 2021-11-26T17:12:25 | 2025-04-01T06:37:18.738786 | {
"authors": [
"zowoq"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/147512",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1109190975 | python310Packages.pyvlx: 0.2.19 -> 0.2.20
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pyvlx is: "Python client to work with Velux units"
meta.homepage for python310Packages.pyvlx is: "https://github.com/Julius2342/pyvlx"
meta.changelog for python310Packages.pyvlx is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 0.2.20 with grep in /nix/store/j5nwiid099imnn0iiqranwpw4p3b3xjz-python3.10-pyvlx-0.2.20
found 0.2.20 in filename of file in /nix/store/j5nwiid099imnn0iiqranwpw4p3b3xjz-python3.10-pyvlx-0.2.20
Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)
First fifty rebuilds by attrpath
python310Packages.pyvlx
python39Packages.pyvlx
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/j5nwiid099imnn0iiqranwpw4p3b3xjz-python3.10-pyvlx-0.2.20 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pyvlx https://github.com/r-ryantm/nixpkgs/archive/61aa5d293b474733dda8a749a3e31ce635f40707.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j5nwiid099imnn0iiqranwpw4p3b3xjz-python3.10-pyvlx-0.2.20
ls -la /nix/store/j5nwiid099imnn0iiqranwpw4p3b3xjz-python3.10-pyvlx-0.2.20/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
2 packages built:
python310Packages.pyvlx
python39Packages.pyvlx
Maintainer pings
cc @fabaff for testing.
Result of nixpkgs-review pr 155856 run on x86_64-linux 1
2 packages built:
python310Packages.pyvlx
python39Packages.pyvlx
| gharchive/pull-request | 2022-01-20T11:34:33 | 2025-04-01T06:37:18.750120 | {
"authors": [
"fabaff",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/155856",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1140877498 | phoronix-test-suite: 10.8.1 -> 10.8.2
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/phoronix-test-suite/versions.
meta.description for phoronix-test-suite is: "Open-Source, Automated Benchmarking"
meta.homepage for phoronix-test-suite is: "https://www.phoronix-test-suite.com/"
meta.changelog for phoronix-test-suite is: ""
Updates performed
Version update
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2/bin/.phoronix-test-suite-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2/bin/phoronix-test-suite had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 10.8.2 with grep in /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2
found 10.8.2 in filename of file in /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2
Rebuild report (if merged into master) (click to expand)
2 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)
First fifty rebuilds by attrpath
phoronix-test-suite
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A phoronix-test-suite https://github.com/r-ryantm/nixpkgs/archive/a7c9fa3eab823271cbc5ece7771c48d8ccca4ceb.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2
ls -la /nix/store/hpqv538cx5cwa7ky5x90bplq93bbcw3y-phoronix-test-suite-10.8.2/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package built:
phoronix-test-suite
Maintainer pings
cc @davidak for testing.
Result of nixpkgs-review pr 160424 run on x86_64-linux 1
1 package built:
phoronix-test-suite
| gharchive/pull-request | 2022-02-17T04:57:00 | 2025-04-01T06:37:18.761538 | {
"authors": [
"davidak",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/160424",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
166853272 | curl: 7.47.1 -> 7.50.0
Motivation for this change
Update curl to the last version
Things done
[X] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)
[X] NixOS
[ ] OS X
[ ] Linux
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.
@vcunat, do you want to pull this into staging?
I'm confident curl doesn't cause a mass rebuild.
The change seems safe API-wise, too.
In that, merging now as it seems to build and runs fine.
@aycanirican pointed out in https://github.com/NixOS/nixpkgs/commit/fa03b541b2e6cd62761f1e9778654de99b0d4ec6#commitcomment-18462996 that this broke aws-sdk-cpp.
/tmp/nix-build-aws-sdk-cpp-0.13.11.drv-0/aws-sdk-cpp-0.13.11-src/aws-cpp-sdk-core/source/http/curl/CurlHandleContainer.cpp:123:5: error: invalid conversion from 'void*' to 'CURL* {aka Curl_easy*}' [-fpermissive]
curl_easy_setopt(handle, CURLOPT_NOSIGNAL, 1L);
^
In file included from /nix/store/idqyp6skbp1mp3w8xz3babcndcsnn6ax-curl-7.50.0-dev/include/curl/curl.h:2420:0,
Bumping the version of aws-sdk-cpp does not fix the issue.
Choices are either to revert to to create a parallel version of curl just for aws-sdk-cpp until they bump.
Thoughts?
Might make sense to wait until hydra comes back up to see the extent of what was broken by this commit
NIX_CFLAGS_COMPILE = '-fpermissive' should fix those cases, as suggested by the error message.
Thanks, done!
I'm confident curl doesn't cause a mass rebuild.
Now I see it does cause a nontrivial rebuild due to systemd indirectly depending on it. It wasn't the case about a year ago...
this broke nix on darwin and many other packages because of https://github.com/curl/curl/issues/926. lets stabilize this via staging please. otherwise others can not work on other packages in nixpkgs.
| gharchive/pull-request | 2016-07-21T15:47:20 | 2025-04-01T06:37:18.770289 | {
"authors": [
"garbas",
"mimadrid",
"obadz",
"vcunat"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/17152",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1293444410 | nixos/nginx: fix broken listenAddresses example
Description of changes
When using the example without the square brackets, nginx fails to start:
nginx-pre-start: nginx: [emerg] invalid port in "::1:80" of the "listen" directive in /nix/store/xyz-nginx.conf:29
nginx-pre-start: nginx: configuration file /nix/store/xyz-nginx.conf test failed
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
[x] Fits CONTRIBUTING.md.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1026
| gharchive/pull-request | 2022-07-04T17:47:35 | 2025-04-01T06:37:18.779059 | {
"authors": [
"Luflosi",
"nixos-discourse"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/180148",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1322736358 | sensu-go-cli: 6.6.6 -> 6.7.5
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sensu/sensu-go/releases.
meta.description for sensu-go-cli is: "Open source monitoring tool for ephemeral infrastructure & distributed applications"
meta.homepage for sensu-go-cli is: "https://sensu.io"
meta.changelog for sensu-go-cli is: ""
Updates performed
Golang update
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.7.4 with grep in /nix/store/l52i5q4w45n8wbyn2gdi5dxdc2sm0fsj-sensu-go-cli-6.7.4
found 6.7.4 in filename of file in /nix/store/l52i5q4w45n8wbyn2gdi5dxdc2sm0fsj-sensu-go-cli-6.7.4
Rebuild report (if merged into master) (click to expand)
3 total rebuild path(s)
3 package rebuild(s)
First fifty rebuilds by attrpath
sensu-go-agent
sensu-go-backend
sensu-go-cli
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/l52i5q4w45n8wbyn2gdi5dxdc2sm0fsj-sensu-go-cli-6.7.4 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sensu-go-cli https://github.com/r-ryantm/nixpkgs/archive/20673179e3e10849c9410b6f37decc9a8a0681fe.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l52i5q4w45n8wbyn2gdi5dxdc2sm0fsj-sensu-go-cli-6.7.4
ls -la /nix/store/l52i5q4w45n8wbyn2gdi5dxdc2sm0fsj-sensu-go-cli-6.7.4/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
3 packages built:
sensu-go-agent
sensu-go-backend
sensu-go-cli
Maintainer pings
cc @thefloweringash for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sensu/sensu-go/releases.
meta.description for sensu-go-cli is: "Open source monitoring tool for ephemeral infrastructure & distributed applications"
meta.homepage for sensu-go-cli is: "https://sensu.io"
meta.changelog for sensu-go-cli is: ""
Updates performed
Golang update
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.7.5 with grep in /nix/store/6kgzzawjry963qdc4ds172v4clshrp52-sensu-go-cli-6.7.5
found 6.7.5 in filename of file in /nix/store/6kgzzawjry963qdc4ds172v4clshrp52-sensu-go-cli-6.7.5
Rebuild report (if merged into master) (click to expand)
3 total rebuild path(s)
3 package rebuild(s)
First fifty rebuilds by attrpath
sensu-go-agent
sensu-go-backend
sensu-go-cli
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/6kgzzawjry963qdc4ds172v4clshrp52-sensu-go-cli-6.7.5 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sensu-go-cli https://github.com/r-ryantm/nixpkgs/archive/95898d794e963265790ac427f7c1566356609b19.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6kgzzawjry963qdc4ds172v4clshrp52-sensu-go-cli-6.7.5
ls -la /nix/store/6kgzzawjry963qdc4ds172v4clshrp52-sensu-go-cli-6.7.5/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
3 packages built:
sensu-go-agent
sensu-go-backend
sensu-go-cli
Maintainer pings
cc @thefloweringash for testing.
Result of nixpkgs-review pr 183843 run on x86_64-linux 1
3 packages built:
sensu-go-agent
sensu-go-backend
sensu-go-cli
| gharchive/pull-request | 2022-07-29T22:36:00 | 2025-04-01T06:37:18.799447 | {
"authors": [
"onny",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/183843",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1341062545 | xcp: 0.9.0 -> 0.9.1
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xcp/versions.
meta.description for xcp is: "An extended cp(1)"
meta.homepage for xcp is: "https://github.com/tarka/xcp"
meta.changelog for xcp is: ""
Updates performed
Rust version update
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.1 with grep in /nix/store/l8fiyfhabr2hqka9rnz563gb8hxghr0s-xcp-0.9.1
found 0.9.1 in filename of file in /nix/store/l8fiyfhabr2hqka9rnz563gb8hxghr0s-xcp-0.9.1
Rebuild report (if merged into master) (click to expand)
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
xcp
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/l8fiyfhabr2hqka9rnz563gb8hxghr0s-xcp-0.9.1 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xcp https://github.com/r-ryantm/nixpkgs/archive/3c5c3ce1aad4e3b7ec6c349718262e4d91b3af33.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l8fiyfhabr2hqka9rnz563gb8hxghr0s-xcp-0.9.1
ls -la /nix/store/l8fiyfhabr2hqka9rnz563gb8hxghr0s-xcp-0.9.1/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package built:
xcp
Maintainer pings
cc @legendofmiracles for testing.
Result of nixpkgs-review pr 187055 run on x86_64-linux 1
1 package built:
xcp
| gharchive/pull-request | 2022-08-17T01:48:22 | 2025-04-01T06:37:18.809551 | {
"authors": [
"onny",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/187055",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
184692663 | Fix texlive on darwin
Motivation for this change
texlive-2016 would not build on Darwin.
Things done
Unbreak build of clisp on Darwin (on which xindy depends on which texlive depends), which previously was Linux only.
Add a dependency to xindy to libiconv.
[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)
[ ] NixOS
[x] OS X
[ ] Linux
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.
ping @vbgl @matthewbauer @LnL7
cc @acowley
Thanks for the review! Done.
It's not perfect, apparently: https://github.com/NixOS/nixpkgs/issues/20062
| gharchive/pull-request | 2016-10-23T14:18:27 | 2025-04-01T06:37:18.815426 | {
"authors": [
"Mic92",
"copumpkin",
"mikesperber",
"vcunat"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/19800",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1433531838 | klipper: unstable-2022-10-25 -> unstable-2022-11-02
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: "The Klipper 3D printer firmware"
meta.homepage for klipper is: "https://github.com/KevinOConnor/klipper"
meta.changelog for klipper is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-10-31 in filename of file in /nix/store/l3mgmrh3i67r56fbmrw7gsywcmpny728-klipper-unstable-2022-10-31
Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)
4 package rebuild(s)
First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/l3mgmrh3i67r56fbmrw7gsywcmpny728-klipper-unstable-2022-10-31 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/431344ba195f2df9e437cf2bdbdf0e286b18ce0d.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l3mgmrh3i67r56fbmrw7gsywcmpny728-klipper-unstable-2022-10-31
ls -la /nix/store/l3mgmrh3i67r56fbmrw7gsywcmpny728-klipper-unstable-2022-10-31/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
4 packages built:
klipper
klipper-firmware
klipper-flash
klipper-genconf
Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: "The Klipper 3D printer firmware"
meta.homepage for klipper is: "https://github.com/KevinOConnor/klipper"
meta.changelog for klipper is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-02 in filename of file in /nix/store/xm7f6vxgh4r6mixgj7fwbf4xs8fna9gl-klipper-unstable-2022-11-02
Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)
4 package rebuild(s)
First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/xm7f6vxgh4r6mixgj7fwbf4xs8fna9gl-klipper-unstable-2022-11-02 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/8bcdd0df374d74eada46607edc9d6c6258f30f60.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xm7f6vxgh4r6mixgj7fwbf4xs8fna9gl-klipper-unstable-2022-11-02
ls -la /nix/store/xm7f6vxgh4r6mixgj7fwbf4xs8fna9gl-klipper-unstable-2022-11-02/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
4 packages built:
klipper
klipper-firmware
klipper-flash
klipper-genconf
Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: "The Klipper 3D printer firmware"
meta.homepage for klipper is: "https://github.com/KevinOConnor/klipper"
meta.changelog for klipper is: ""
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-03 in filename of file in /nix/store/s60vnjq931xkvh2hrbrhwfnszhm5b7iw-klipper-unstable-2022-11-03
Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)
4 package rebuild(s)
First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/s60vnjq931xkvh2hrbrhwfnszhm5b7iw-klipper-unstable-2022-11-03 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/ace92a6aec0b1b00f082a17c6d4cbbb3736418c4.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s60vnjq931xkvh2hrbrhwfnszhm5b7iw-klipper-unstable-2022-11-03
ls -la /nix/store/s60vnjq931xkvh2hrbrhwfnszhm5b7iw-klipper-unstable-2022-11-03/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
4 packages built:
klipper
klipper-firmware
klipper-flash
klipper-genconf
Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.
| gharchive/pull-request | 2022-11-02T17:33:29 | 2025-04-01T06:37:18.840776 | {
"authors": [
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/199198",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1501738379 | static-web-server: init at 2.14.1
Description of changes
https://sws.joseluisq.net
https://github.com/static-web-server/static-web-server
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
[x] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 206662 run on x86_64-linux 1
1 package built:
static-web-server
Huh, merged before finishing review 😅
Anyway, started server and it returned content as expected :)
SWS maintainer here.
Just a bit late thanks to all you guys and specially @figsoda for the effort to incorporate SWS into nixpkgs ⚡
It should be mentioned in the installation doc section soon.
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/testing-a-new-module-and-package-without-breaking-my-stable-nixos-install/27129/1
| gharchive/pull-request | 2022-12-18T04:21:03 | 2025-04-01T06:37:18.852672 | {
"authors": [
"clerie",
"figsoda",
"joseluisq",
"nixos-discourse"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/206662",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1564108124 | praat: 6.3.04 -> 6.3.05
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/praat/praat/releases.
meta.description for praat is: Doing phonetics by computer
meta.homepage for praat is: https://www.fon.hum.uva.nl/praat/
Updates performed
Version update
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.3.05 with grep in /nix/store/wa6j5adglnssdspjnl47d99y86xx7cnn-praat-6.3.05
found 6.3.05 in filename of file in /nix/store/wa6j5adglnssdspjnl47d99y86xx7cnn-praat-6.3.05
Rebuild report (if merged into master) (click to expand)
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
praat
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/wa6j5adglnssdspjnl47d99y86xx7cnn-praat-6.3.05 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A praat https://github.com/r-ryantm/nixpkgs/archive/6616e69312ec69c0c7246e6cb150928f662466b0.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wa6j5adglnssdspjnl47d99y86xx7cnn-praat-6.3.05
ls -la /nix/store/wa6j5adglnssdspjnl47d99y86xx7cnn-praat-6.3.05/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package built:
praat
Maintainer pings
cc @orivej for testing.
Result of nixpkgs-review pr 213751 run on x86_64-linux 1
1 package built:
praat
| gharchive/pull-request | 2023-01-31T11:11:19 | 2025-04-01T06:37:18.862976 | {
"authors": [
"JulienMalka",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/213751",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1699033395 | python311Packages.mkdocstrings-python: 0.9.0 -> 0.10.0
Changelog: https://github.com/mkdocstrings/python/blob/0.10.0/CHANGELOG.md
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 230507 run on x86_64-linux 1
1 package marked as broken and skipped:
netbox_3_3
5 packages built:
netbox
python310Packages.mkdocstrings-python
python310Packages.mkdocstrings-python.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist
| gharchive/pull-request | 2023-05-07T12:02:40 | 2025-04-01T06:37:18.872639 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/230507",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1709022868 | nixos/no-x-libs: add gst-plugins-bad, gst-plugins-rs
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
The gst-plugins-base hack is very similar to https://github.com/NixOS/nixpkgs/pull/231185/files#diff-bd924545a322bae41a5f57f50113281417c8ea50fec7801f606840410f492164R169
| gharchive/pull-request | 2023-05-14T17:52:12 | 2025-04-01T06:37:18.880981 | {
"authors": [
"SuperSandro2000"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/231891",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1710260873 | owncloud: 3.2.1 -> 4.0.0
Description of changes
Upgrade owncloud 3.2.1 -> 4.0.0
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[-] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
@ofborg build owncloud
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2218
| gharchive/pull-request | 2023-05-15T14:49:05 | 2025-04-01T06:37:18.889908 | {
"authors": [
"hellwolf",
"nixos-discourse"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/232056",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1728353101 | sonic-server: migrate to bindgenHook
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
@ofborg build sonic-server sonic-server.passthru.tests
| gharchive/pull-request | 2023-05-26T23:56:25 | 2025-04-01T06:37:18.897823 | {
"authors": [
"wegank"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/234329",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1771517514 | qownnotes: 23.6.5 -> 23.6.6
Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from repology.org.
meta.description for qownnotes is: Plain-text file notepad and todo-list manager with markdown support and Nextcloud/ownCloud integration
meta.homepage for qownnotes is: https://www.qownnotes.org/
meta.changelog for qownnotes is: https://www.qownnotes.org/changelog.html
Updates performed
Version update
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 23.6.6 with grep in /nix/store/j75gaa5qkar1rfiz7qcdqpbqcpfwcy37-qownnotes-23.6.6
found 23.6.6 in filename of file in /nix/store/j75gaa5qkar1rfiz7qcdqpbqcpfwcy37-qownnotes-23.6.6
Rebuild report (if merged into master) (click to expand)
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
qownnotes
Instructions to test this update (click to expand)
Build yourself:
nix-build -A qownnotes https://github.com/pbek/nixpkgs/archive/a9c0f2bd83553203465466e942052f93d8d2e391.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j75gaa5qkar1rfiz7qcdqpbqcpfwcy37-qownnotes-23.6.6
ls -la /nix/store/j75gaa5qkar1rfiz7qcdqpbqcpfwcy37-qownnotes-23.6.6/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package built:
qownnotes
Maintainer pings
cc @pbek @totoroot for testing.
Result of nixpkgs-review pr 239375 run on x86_64-linux 1
1 package built:
qownnotes
| gharchive/pull-request | 2023-06-23T14:01:32 | 2025-04-01T06:37:18.906581 | {
"authors": [
"pbek",
"totoroot"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/239375",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1801635804 | libplacebo: 5.264.1 -> 6.292.1
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libplacebo/versions.
meta.description for libplacebo is: Reusable library for GPU-accelerated video/image rendering primitives
meta.homepage for libplacebo is: https://code.videolan.org/videolan/libplacebo
meta.changelog for libplacebo is: https://code.videolan.org/videolan/libplacebo/-/tags/v6.292.0
Updates performed
Version update
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.292.0 with grep in /nix/store/lyr948g6pc8sqxnv2xlivxk919vmk4h9-libplacebo-6.292.0
found 6.292.0 in filename of file in /nix/store/lyr948g6pc8sqxnv2xlivxk919vmk4h9-libplacebo-6.292.0
Rebuild report (if merged into master) (click to expand)
144 total rebuild path(s)
144 package rebuild(s)
First fifty rebuilds by attrpath
MIDIVisualizer
adl
ani-cli
anime-downloader
anki
arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.cat9-wrapped
arcanPackages.durden-wrapped
arcanPackages.ffmpeg
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
audiobookshelf
celluloid
corrscope
cplay-ng
curseradio
deepin.dde-gsettings-schemas
deepin.deepin-movie-reborn
deepin.deepin-music
deepin.deepin-voice-note
dmlive
dra-cla
eaglemode
ff2mpv
ffcast
ffmpeg-full
ffmpeg_4-full
ffmpeg_5-full
ffmpeg_6-full
gonic
handbrake
haruna
hydrus
hypnotix
imagination
jellyfin
jellyfin-ffmpeg
jellyfin-media-player
jellyfin-mpv-shim
jftui
kaffeine
klipperscreen
kphotoalbum
libplacebo
libsForQt5.elisa
libsForQt5.kdenlive
libsForQt5.phonon-backend-vlc
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/lyr948g6pc8sqxnv2xlivxk919vmk4h9-libplacebo-6.292.0 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libplacebo https://github.com/r-ryantm/nixpkgs/archive/5836cbc28d5362a4ad467fb48e533ad28ebd10f0.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lyr948g6pc8sqxnv2xlivxk919vmk4h9-libplacebo-6.292.0
ls -la /nix/store/lyr948g6pc8sqxnv2xlivxk919vmk4h9-libplacebo-6.292.0/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package marked as broken and skipped:
obs-studio-plugins.obs-hyperion
134 packages failed to build:
MIDIVisualizer
adl
ani-cli
anime-downloader
anki
arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.cat9-wrapped
arcanPackages.durden-wrapped
arcanPackages.ffmpeg
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
audiobookshelf
celluloid
corrscope
cplay-ng
curseradio
deepin.dde-gsettings-schemas
deepin.deepin-movie-reborn
deepin.deepin-music
deepin.deepin-voice-note
dmlive
dra-cla
eaglemode
ff2mpv
ffcast
ffmpeg_6-full
gonic
handbrake
haruna
hydrus
hypnotix
imagination
jellyfin
jellyfin-ffmpeg
jellyfin-media-player
jellyfin-mpv-shim
jftui
kaffeine
klipperscreen
kphotoalbum
libsForQt5.elisa
libsForQt5.kdenlive
libsForQt5.phonon-backend-vlc
libsForQt5.plasmatube
libsForQt5.soundkonverter
libvlc
liquidsoap
manim
megaglest
memento
minitube
mnemosyne
mpc-qt
mpv
mpv-unwrapped
mpvScripts.inhibit-gnome
mpvScripts.mpris
mpvScripts.thumbfast
mpvpaper
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-ndi
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs
peek
plex-media-player
plex-mpv-shim
printrun
pympress
python310Packages.aigpy
python310Packages.dm-sonnet
python310Packages.moderngl-window
python310Packages.mpv
python310Packages.pydub
python310Packages.pyglet
python310Packages.python-vlc
python310Packages.pytmx
python310Packages.tensorflow-datasets
python311Packages.aigpy
python311Packages.moderngl-window
python311Packages.mpv
python311Packages.pydub
python311Packages.pyglet
python311Packages.python-vlc
python311Packages.pytmx
qimgv
radioboat
reaper
restream
somafm-cli
strawberry
stremio
sublime-music
subtitleedit
sunshine
tidal-dl
tone
video-trimmer
vlc
vokoscreen
wtwitch
ytfzf
2 packages built:
ffmpeg_4-full
libplacebo
Maintainer pings
cc @primeos @tadeokondrak for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libplacebo/versions.
meta.description for libplacebo is: Reusable library for GPU-accelerated video/image rendering primitives
meta.homepage for libplacebo is: https://code.videolan.org/videolan/libplacebo
meta.changelog for libplacebo is: https://code.videolan.org/videolan/libplacebo/-/tags/v6.292.1
Updates performed
Version update
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.292.1 with grep in /nix/store/kc2bqdndr3fq07qnc56zvy2ppwq655za-libplacebo-6.292.1
found 6.292.1 in filename of file in /nix/store/kc2bqdndr3fq07qnc56zvy2ppwq655za-libplacebo-6.292.1
Rebuild report (if merged into master) (click to expand)
149 total rebuild path(s)
149 package rebuild(s)
First fifty rebuilds by attrpath
MIDIVisualizer
adl
ani-cli
anime-downloader
anki
arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.cat9-wrapped
arcanPackages.durden-wrapped
arcanPackages.ffmpeg
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
audiobookshelf
celluloid
corrscope
cplay-ng
curseradio
deepin.dde-gsettings-schemas
deepin.deepin-movie-reborn
deepin.deepin-music
deepin.deepin-voice-note
dmlive
dra-cla
eaglemode
feishin
ff2mpv
ffcast
ffmpeg-full
ffmpeg_4-full
ffmpeg_5-full
ffmpeg_6-full
gonic
handbrake
haruna
hydrus
hypnotix
imagination
jellyfin
jellyfin-ffmpeg
jellyfin-media-player
jellyfin-mpv-shim
jftui
kaffeine
klipperscreen
kphotoalbum
libplacebo
libsForQt5.elisa
libsForQt5.kdenlive
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/kc2bqdndr3fq07qnc56zvy2ppwq655za-libplacebo-6.292.1 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libplacebo https://github.com/r-ryantm/nixpkgs/archive/29b436348a8ca87d2221d8cd39b32557629c6996.tar.gz
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kc2bqdndr3fq07qnc56zvy2ppwq655za-libplacebo-6.292.1
ls -la /nix/store/kc2bqdndr3fq07qnc56zvy2ppwq655za-libplacebo-6.292.1/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
4 packages marked as broken and skipped:
manim
obs-studio-plugins.obs-hyperion
python310Packages.moderngl-window
python311Packages.moderngl-window
91 packages failed to build:
MIDIVisualizer
arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.cat9-wrapped
arcanPackages.durden-wrapped
arcanPackages.ffmpeg
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
audiobookshelf
corrscope
deepin.deepin-music
deepin.deepin-voice-note
eaglemode
ffcast
ffmpeg_6-full
gonic
handbrake
haruna
imagination
jellyfin
jellyfin-ffmpeg
kaffeine
kphotoalbum
libsForQt5.elisa
libsForQt5.kdenlive
libsForQt5.phonon-backend-vlc
libsForQt5.soundkonverter
libvlc
liquidsoap
megaglest
minitube
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-ndi
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs
peek
printrun
pympress
python310Packages.aigpy
python310Packages.pydub
python310Packages.pyglet
python310Packages.python-vlc
python310Packages.pytmx
python311Packages.aigpy
python311Packages.pydub
python311Packages.pyglet
python311Packages.python-vlc
python311Packages.pytmx
reaper
restream
rofi-screenshot
strawberry
sunshine
tidal-dl
tone
video-trimmer
vlc
vokoscreen
wtwitch
43 packages built:
adl
ani-cli
anime-downloader
anki
celluloid
cplay-ng
curseradio
deepin.dde-gsettings-schemas
deepin.deepin-movie-reborn
dmlive
dra-cla
feishin
ff2mpv
ffmpeg_4-full
hydrus
hypnotix
jellyfin-media-player
jellyfin-mpv-shim
jftui
klipperscreen
libplacebo
libsForQt5.plasmatube
memento
mnemosyne
mpc-qt
mpv
mpv-unwrapped
mpvScripts.inhibit-gnome
mpvScripts.mpris
mpvScripts.thumbfast
mpvpaper
plex-media-player
plex-mpv-shim
python310Packages.mpv
python311Packages.mpv
qimgv
radioboat
somafm-cli
stremio
sublime-music
subtitleedit
tomato-c
ytfzf
Maintainer pings
cc @primeos @tadeokondrak for testing.
| gharchive/pull-request | 2023-07-12T19:38:04 | 2025-04-01T06:37:18.942057 | {
"authors": [
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/243134",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1868148385 | python311Packages.griffe: 0.35.0 -> 0.35.1
Diff: https://github.com/mkdocstrings/griffe/compare/refs/tags/0.35.0...0.35.1
Changelog: https://github.com/mkdocstrings/griffe/blob/0.35.1/CHANGELOG.md
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 251619 run on x86_64-linux 1
9 packages built:
griffe (python310Packages.griffe)
griffe.dist (python310Packages.griffe.dist)
netbox
python310Packages.mkdocstrings-python
python310Packages.mkdocstrings-python.dist
python311Packages.griffe
python311Packages.griffe.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist
Result of nixpkgs-review pr 251619 run on x86_64-linux 1
1 package marked as broken and skipped:
netbox_3_3
9 packages built:
griffe (python310Packages.griffe)
griffe.dist (python310Packages.griffe.dist)
netbox
python310Packages.mkdocstrings-python
python310Packages.mkdocstrings-python.dist
python311Packages.griffe
python311Packages.griffe.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist
| gharchive/pull-request | 2023-08-26T15:39:00 | 2025-04-01T06:37:18.954394 | {
"authors": [
"fabaff",
"matthiasbeyer"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/251619",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1931688145 | python311Packages.google-generativeai: 0.1.0 -> 0.2.1
Diff: https://github.com/google/generative-ai-python/compare/refs/tags/v0.1.0...v0.2.1
Changelog: https://github.com/google/generative-ai-python/releases/tag/v0.2.1
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Result of nixpkgs-review pr 259722 run on x86_64-linux 1
5 packages built:
home-assistant-component-tests.google_generative_ai_conversation
python310Packages.google-generativeai
python310Packages.google-generativeai.dist
python311Packages.google-generativeai
python311Packages.google-generativeai.dist
| gharchive/pull-request | 2023-10-08T07:36:04 | 2025-04-01T06:37:18.964289 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/259722",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1947440750 | xfce.xfconf: 4.18.1 -> 4.18.2
https://gitlab.xfce.org/xfce/xfconf/-/compare/xfconf-4.18.1...xfconf-4.18.2
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
@ofborg test xfce
| gharchive/pull-request | 2023-10-17T13:29:32 | 2025-04-01T06:37:18.973796 | {
"authors": [
"bobby285271"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/261644",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1949721841 | alpine-make-rootfs: init
Description of changes
alpine-make-rootfs is a tool a bit similar to the already-packaged alpine-make-vm-image. Instead of creating a full vm image, it only creates an Alpine Linux rootfs.
I've been using this already on my own projects, thought I'd package it to make it easy for others to use it as well.
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Since it's a new package and it doesn't need any overrides, wouldn't it be better to put in in by-name?
| gharchive/pull-request | 2023-10-18T13:12:01 | 2025-04-01T06:37:18.982523 | {
"authors": [
"DanielSidhion",
"nrabulinski"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/261828",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2034543797 | i3-open-next-ws: init at 0.1.5
Description of changes
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[x] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 273418 run on x86_64-linux 1
1 package built:
i3-open-next-ws
just changes to the meta attributes
This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3078
| gharchive/pull-request | 2023-12-10T21:36:51 | 2025-04-01T06:37:18.993919 | {
"authors": [
"nixos-discourse",
"quantenzitrone"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/273418",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2044713093 | restish: 0.19.0 -> 0.20.0
Diff: https://github.com/danielgtaylor/restish/compare/refs/tags/v0.19.0...v0.20.0
Changelog: https://github.com/danielgtaylor/restish/releases/tag/v0.20.0
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 274697 run on x86_64-linux 1
1 package built:
restish
| gharchive/pull-request | 2023-12-16T11:20:59 | 2025-04-01T06:37:19.006008 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/274697",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2071274111 | python311Packages.pymeteoclimatic: 0.0.6 -> 0.1.0
Diff: https://github.com/adrianmo/pymeteoclimatic/compare/0.0.6...0.1.0
Changelog: https://github.com/adrianmo/pymeteoclimatic/releases/tag/0.1.0
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 279692 run on x86_64-linux 1
5 packages built:
home-assistant-component-tests.meteoclimatic
python310Packages.pymeteoclimatic
python310Packages.pymeteoclimatic.dist
python311Packages.pymeteoclimatic
python311Packages.pymeteoclimatic.dist
Result of nixpkgs-review pr 279692 run on aarch64-darwin 1
4 packages built:
python310Packages.pymeteoclimatic
python310Packages.pymeteoclimatic.dist
python311Packages.pymeteoclimatic
python311Packages.pymeteoclimatic.dist
Result of nixpkgs-review pr 279692 run on aarch64-linux 1
4 packages built:
python310Packages.pymeteoclimatic
python310Packages.pymeteoclimatic.dist
python311Packages.pymeteoclimatic
python311Packages.pymeteoclimatic.dist
| gharchive/pull-request | 2024-01-08T21:45:29 | 2025-04-01T06:37:19.019726 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/279692",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2084942216 | electrum: 4.4.6 -> 4.5.0
Description of changes
version update - https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
@GrahamcOfBorg build electrum
| gharchive/pull-request | 2024-01-16T21:11:34 | 2025-04-01T06:37:19.029973 | {
"authors": [
"prusnak"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/281398",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2092519043 | python312Packages.overrides: 7.4.0 -> 7.6.0
Diff: https://github.com/mkorpela/overrides/compare/refs/tags/7.4.0...7.6.0
Changelog: https://github.com/mkorpela/overrides/releases/tag/7.6.0
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 282544 run on x86_64-linux 1
8 packages marked as broken and skipped:
python311Packages.elegy
python311Packages.elegy.dist
python311Packages.jupyter-contrib-nbextensions
python311Packages.jupyter-contrib-nbextensions.dist
python311Packages.openllm
python311Packages.openllm.dist
python311Packages.treex
python311Packages.treex.dist
25 packages failed to build:
python311Packages.arviz
python311Packages.arviz.dist
python311Packages.augmax
python311Packages.augmax.dist
python311Packages.bambi
python311Packages.bambi.dist
python311Packages.jupyterlab-git
python311Packages.jupyterlab-git.dist
python311Packages.layoutparser
python311Packages.layoutparser.dist
python311Packages.nbdime
python311Packages.nbdime.dist
python311Packages.nikola
python311Packages.nikola.dist
python311Packages.oauthenticator
python311Packages.oauthenticator.dist
python311Packages.pdfplumber
python311Packages.pdfplumber.dist
python311Packages.pymc
python311Packages.pymc.dist
python312Packages.qiling
python312Packages.qiling.dist
tts
tts.dist
wolfram-notebook
130 packages built:
cantor (libsForQt5.cantor ,plasma5Packages.cantor)
ihaskell
jupyter
jupyter-all
labplot
manim
manim.dist
nbqa
nbqa.dist
python311Packages.ansible-kernel
python311Packages.ansible-kernel.dist
python311Packages.batchspawner
python311Packages.batchspawner.dist
python311Packages.bqplot
python311Packages.bqplot.dist
python311Packages.bqscales
python311Packages.bqscales.dist
python311Packages.dalle-mini
python311Packages.dalle-mini.dist
python311Packages.distrax
python311Packages.distrax.dist
python311Packages.dm-haiku
python311Packages.dm-haiku.dist
python311Packages.dockerspawner
python311Packages.dockerspawner.dist
python311Packages.einops
python311Packages.einops.dist
python311Packages.encodec
python311Packages.encodec.dist
python311Packages.experiment-utilities
python311Packages.experiment-utilities.dist
python311Packages.flax
python311Packages.flax.dist
python311Packages.ipytablewidgets
python311Packages.ipytablewidgets.dist
python311Packages.jupyter
python311Packages.jupyter-collaboration
python311Packages.jupyter-collaboration.dist
python311Packages.jupyter-contrib-core
python311Packages.jupyter-contrib-core.dist
python311Packages.jupyter-lsp
python311Packages.jupyter-lsp.dist
python311Packages.jupyter-nbextensions-configurator
python311Packages.jupyter-nbextensions-configurator.dist
python311Packages.jupyter-server
python311Packages.jupyter-server-fileid
python311Packages.jupyter-server-fileid.dist
python311Packages.jupyter-server-mathjax
python311Packages.jupyter-server-mathjax.dist
python311Packages.jupyter-server.dist
python311Packages.jupyter.dist
python311Packages.jupyterhub
python311Packages.jupyterhub-ldapauthenticator
python311Packages.jupyterhub-ldapauthenticator.dist
python311Packages.jupyterhub-systemdspawner
python311Packages.jupyterhub-systemdspawner.dist
python311Packages.jupyterhub-tmpauthenticator
python311Packages.jupyterhub-tmpauthenticator.dist
python311Packages.jupyterhub.dist
python311Packages.jupyterlab
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab-lsp.dist
python311Packages.jupyterlab-server
python311Packages.jupyterlab-server.dist
python311Packages.jupyterlab.dist
python311Packages.jupytext
python311Packages.jupytext.dist
python311Packages.k-diffusion
python311Packages.k-diffusion.dist
python311Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter.dist
python311Packages.nbclassic
python311Packages.nbclassic.dist
python311Packages.nbdev
python311Packages.nbdev.dist
python311Packages.nix-kernel
python311Packages.nix-kernel.dist
python311Packages.notebook
python311Packages.notebook-shim
python311Packages.notebook-shim.dist
python311Packages.notebook.dist
python311Packages.notedown
python311Packages.notedown.dist
python311Packages.overrides
python311Packages.overrides.dist
python311Packages.phik
python311Packages.phik.dist
python311Packages.pyarr
python311Packages.pyarr.dist
python311Packages.pydeck
python311Packages.pydeck.dist
python311Packages.pymoo
python311Packages.pymoo.dist
python311Packages.python-fx
python311Packages.python-fx.dist
python311Packages.qgrid
python311Packages.qgrid.dist
python311Packages.qiling
python311Packages.qiling.dist
python311Packages.rlax
python311Packages.rlax.dist
python311Packages.rotary-embedding-torch
python311Packages.rotary-embedding-torch.dist
streamlit (python311Packages.streamlit)
streamlit.dist (python311Packages.streamlit.dist)
python311Packages.tsfresh
python311Packages.tsfresh.dist
python311Packages.vector
python311Packages.vector.dist
python311Packages.vega
python311Packages.vega.dist
python311Packages.vqgan-jax
python311Packages.vqgan-jax.dist
python311Packages.xarray-einstats
python311Packages.xarray-einstats.dist
python312Packages.nbdev
python312Packages.nbdev.dist
python312Packages.overrides
python312Packages.overrides.dist
python312Packages.pyarr
python312Packages.pyarr.dist
python312Packages.python-fx
python312Packages.python-fx.dist
quarto
rstudio
rstudio-server
rstudioServerWrapper
rstudioWrapper
sage
sageWithDoc
| gharchive/pull-request | 2024-01-21T10:16:02 | 2025-04-01T06:37:19.052119 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/282544",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2145012952 | doc: added nvidiaLegacy driver version 470 to available options in nixos manual
It is possible to install the nvidiaLegacy470 driver for the slightly outdated GPUs, but the documentation only has the hints how to install the drivers for the even older GPUs.
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
I don't understand this PR: were you actually able to enable the legacy nvidia drivers using nvidiaLegacy470? From what I understand, this option should cause an error to be thrown since https://github.com/NixOS/nixpkgs/pull/99323 (2020), and even that was removed in https://github.com/NixOS/nixpkgs/pull/244060 so now it does nothing.
I'm proposing to update the docs in https://github.com/NixOS/nixpkgs/pull/298956
| gharchive/pull-request | 2024-02-20T18:25:15 | 2025-04-01T06:37:19.063680 | {
"authors": [
"klinger",
"ncfavier"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/290231",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2171481135 | wire-desktop: mac 3.32.4589 -> 3.35.4861, linux 3.32.3079 -> 3.35.3348
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
This is the second time I've updated this version bump. I'll leave it for a bit longer but if no one's interested in reviewing I'll go ahead and self-merge this one.
| gharchive/pull-request | 2024-03-06T13:11:23 | 2025-04-01T06:37:19.073665 | {
"authors": [
"toonn"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/293769",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
265165085 | desktop-managers: Fix unsupported attribute 'xcfg'
Motivation for this change
After https://github.com/NixOS/nixpkgs/pull/30286 a nixos-rebuild results in:
error: Module `/etc/nixos/nixpkgs/nixos/modules/services/x11/desktop-managers/default.nix' has an unsupported attribute `xcfg'. This is caused by assignments to the top-level attributes `config' or `options'.
(use ‘--show-trace’ to show detailed location information)
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.
Closing because of https://github.com/NixOS/nixpkgs/pull/30385
| gharchive/pull-request | 2017-10-13T04:14:33 | 2025-04-01T06:37:19.078870 | {
"authors": [
"adisbladis"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/30380",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2319159008 | nu_scripts: 0-unstable-2024-05-19 -> 0-unstable-2024-06-01
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nu_scripts is: A place to share Nushell scripts with each other
meta.homepage for nu_scripts is: https://github.com/nushell/nu_scripts
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done
built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-05-26 in filename of file in /nix/store/sk4wljbnq1pnrh8hps19y6cy2hpl43vi-nu_scripts-0-unstable-2024-05-26
Rebuild report (if merged into master) (click to expand)
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
nu_scripts
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/sk4wljbnq1pnrh8hps19y6cy2hpl43vi-nu_scripts-0-unstable-2024-05-26 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nu_scripts https://github.com/r-ryantm/nixpkgs/archive/9916a250d26b6240e271502b7bb27ea48d5aab4f.tar.gz
Or:
nix build github:r-ryantm/nixpkgs/9916a250d26b6240e271502b7bb27ea48d5aab4f#nu_scripts
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sk4wljbnq1pnrh8hps19y6cy2hpl43vi-nu_scripts-0-unstable-2024-05-26
ls -la /nix/store/sk4wljbnq1pnrh8hps19y6cy2hpl43vi-nu_scripts-0-unstable-2024-05-26/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1
1 package built:
nu_scripts
Maintainer pings
cc @CardboardTurkey for testing.
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nu_scripts is: A place to share Nushell scripts with each other
meta.homepage for nu_scripts is: https://github.com/nushell/nu_scripts
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Compare changes on GitHub
Impact
Checks done
built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-06-01 in filename of file in /nix/store/n156kvffwhyqh9azsazblhis6xhpmxwx-nu_scripts-0-unstable-2024-06-01
Rebuild report (if merged into master) (click to expand)
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
nu_scripts
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/n156kvffwhyqh9azsazblhis6xhpmxwx-nu_scripts-0-unstable-2024-06-01 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nu_scripts https://github.com/r-ryantm/nixpkgs/archive/bec6bcc79f8e7af0f98e2cb0c43e0445d9d15dc6.tar.gz
Or:
nix build github:r-ryantm/nixpkgs/bec6bcc79f8e7af0f98e2cb0c43e0445d9d15dc6#nu_scripts
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n156kvffwhyqh9azsazblhis6xhpmxwx-nu_scripts-0-unstable-2024-06-01
ls -la /nix/store/n156kvffwhyqh9azsazblhis6xhpmxwx-nu_scripts-0-unstable-2024-06-01/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1
1 package built:
nu_scripts
Maintainer pings
cc @CardboardTurkey for testing.
| gharchive/pull-request | 2024-05-27T13:26:26 | 2025-04-01T06:37:19.096017 | {
"authors": [
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/315086",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2328393031 | Remove the revCount attribute from the generated flake registry
Description of changes
The revCount attribute is only present when the flake is an actual git
repo and not when using a flake reference with an input scheme for a git
forge that downloads tarballs instead (like github: or sourcehut:).
Because of this, the hash of the nixos config changes depending on
whether the config was built from a local git clone or from a flake ref
using one of those input schemes.
This leads to confusion (I lost quite some time figuring out what
happened here) and unnecessary rebuilds.
To my knowledge, there is no immediate benefit to including revCount in
the flake registry entry.
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Well at least for sourcehut, I don't get a revCount when I build using a sourcehut: reference, but I do get one when I build from a local clone:
Lix 2.90.0-beta.1
Type :? for help.
nix-repl> :lf sourcehut:~r-vdp/nixos-config
Added 21 variables.
nix-repl> sourceInfo
{
lastModified = 1717232731;
lastModifiedDate = "20240601090531";
narHash = "sha256-zCzXuwkyGoQDRvCSkOi2uv1NMd+yZjufZG6lzGVP5AA=";
outPath = "/nix/store/9ilkiqfx5m85riwmnc6b0p4qdrwy4s95-source";
rev = "23b24e1e7d993cb5ec005a3a22345524f9579c39";
shortRev = "23b24e1";
}
nix-repl> :lf .
Added 23 variables.
nix-repl> sourceInfo
{
lastModified = 1717232731;
lastModifiedDate = "20240601090531";
narHash = "sha256-zCzXuwkyGoQDRvCSkOi2uv1NMd+yZjufZG6lzGVP5AA=";
outPath = "/nix/store/9ilkiqfx5m85riwmnc6b0p4qdrwy4s95-source";
rev = "23b24e1e7d993cb5ec005a3a22345524f9579c39";
revCount = 2319;
shortRev = "23b24e1";
submodules = false;
}
@lf- have you had the time to give this some more thought?
| gharchive/pull-request | 2024-05-31T18:36:59 | 2025-04-01T06:37:19.108118 | {
"authors": [
"r-vdp"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/316225",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2342088711 | python311Packages.aioshelly: 10.0.0 -> 10.0.1
Diff: https://github.com/home-assistant-libs/aioshelly/compare/refs/tags/10.0.0...10.0.1
Changelog: https://github.com/home-assistant-libs/aioshelly/releases/tag/10.0.1
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 318471 run on x86_64-linux 1
41 packages built:
home-assistant-component-tests.airthings_ble
home-assistant-component-tests.aranet
home-assistant-component-tests.bluemaestro
home-assistant-component-tests.bluetooth_adapters
home-assistant-component-tests.bluetooth_le_tracker
home-assistant-component-tests.bthome
home-assistant-component-tests.dormakaba_dkey
home-assistant-component-tests.eufylife_ble
home-assistant-component-tests.fjaraskupan
home-assistant-component-tests.gardena_bluetooth
home-assistant-component-tests.govee_ble
home-assistant-component-tests.homekit_controller
home-assistant-component-tests.ibeacon
home-assistant-component-tests.inkbird
home-assistant-component-tests.kegtron
home-assistant-component-tests.keymitt_ble
home-assistant-component-tests.lamarzocco
home-assistant-component-tests.ld2410_ble
home-assistant-component-tests.led_ble
home-assistant-component-tests.moat
home-assistant-component-tests.mopeka
home-assistant-component-tests.oralb
home-assistant-component-tests.private_ble_device
home-assistant-component-tests.qingping
home-assistant-component-tests.rapt_ble
home-assistant-component-tests.ruuvitag_ble
home-assistant-component-tests.sensirion_ble
home-assistant-component-tests.sensorpro
home-assistant-component-tests.sensorpush
home-assistant-component-tests.shelly
home-assistant-component-tests.snooz
home-assistant-component-tests.switchbot
home-assistant-component-tests.thermobeacon
home-assistant-component-tests.thermopro
home-assistant-component-tests.tilt_ble
home-assistant-component-tests.xiaomi_ble
home-assistant-component-tests.yalexs_ble
python311Packages.aioshelly
python311Packages.aioshelly.dist
python312Packages.aioshelly
python312Packages.aioshelly.dist
| gharchive/pull-request | 2024-06-09T08:05:10 | 2025-04-01T06:37:19.122004 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/318471",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2386990824 | immich: init at 1.109.2; nixos/immich: init module
Description of changes
This adds the package, nixos module and nixos test for immich
Closes #244803
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Does this superseed #244803?
Yes
I occasionally see these messages in my logs:
server[36665]: [Nest] 36665 - 07/05/2024, 12:00:00 AM ERROR [Microservices:JobService] Unable to run job handler (thumbnailGeneration/generate-preview): Error: Cannot find ffprobe
server[36665]: [Nest] 36665 - 07/05/2024, 12:00:00 AM ERROR [Microservices:JobService] Error: Cannot find ffprobe
server[8610]: [Nest] 8610 - 07/02/2024, 10:35:52 PM WARN [Api:ServerInfoRepository~dfqq7ca6] Failed to read build-lock.json
ffprobe is provided by the ffmpeg the build already depends on. Perhaps it needs to be wrapped to have access to the binary at runtime.
Just wanted to say I'm psyched to see this getting added. Thanks for the work!
I have addressed most of the review comments now and rebased onto the current master. This broke albumentations, which I fixed in a seperate commit.
We will still need to wait for the upstream PR to get the geonames without downloading the full docker container
Ok, the albumentation fix got its own PR, I will rebase once that is merged: https://github.com/NixOS/nixpkgs/pull/325019/files
Ok, the albumentation fix got its own PR, I will rebase once that is merged: #325019
Merged :)
Yes, but we are waiting for a PR from upstream. When that is merged and a new release is cut, I will update this here accordingly
We get this error in the Immich logs while indexing photos:
Jul 09 23:26:18 server2 server[1740]: [Nest] 1740 - 07/09/2024, 11:26:18 PM ERROR [Microservices:JobService] Unable to run job handler (faceDetection/face-detection): Error: Machine learning request to "http://immich-machine-learning:3003" failed with ConnectTimeoutError: Connect Timeout Error
Setting
services.immich.environment.IMMICH_MACHINE_LEARNING_URL = "http://localhost:3003";
fixes the issue. Maybe we should have a default like IMMICH_MACHINE_LEARNING_URL = "${cfg.host}:3003"; or something.
Also would it be possible to rename the environment option to settings?
We get this error in the Immich logs while indexing photos:
Jul 09 23:26:18 server2 server[1740]: [Nest] 1740 - 07/09/2024, 11:26:18 PM ERROR [Microservices:JobService] Unable to run job handler (faceDetection/face-detection): Error: Machine learning request to "http://immich-machine-learning:3003" failed with ConnectTimeoutError: Connect Timeout Error
Setting
services.immich.environment.IMMICH_MACHINE_LEARNING_URL = "http://localhost:3003";
fixes the issue. Maybe we should have a default like IMMICH_MACHINE_LEARNING_URL = "${cfg.host}:3003"; or something.
I have no idea whether upstream actually supports that, but a Unix socket could be an even nicer option if they do.
There's an issue with HEIC / HEIF images, they can't be viewed and theres no thumbnail generated. Might be related to the implementation of libheif?
Error log of immich-server:
Jul 14 11:24:59 server2 server[174045]: [Nest] 174045 - 07/14/2024, 11:24:59 AM ERROR [Microservices:JobService] Unable to run job handler (thumbnailGeneration/generate-preview): Error: /var/lib/immich/upload/8046b9e9-b0cf-46d1-9bc7-542fca747436/81/a3/81a3dc3a-db01-45ea-abe5-ed6996ced369.HEIC: bad seek to 1531357
Jul 14 11:24:59 server2 server[174045]: heif: Unsupported feature: Unsupported codec (4.3000)
Jul 14 11:24:59 server2 server[174045]: [Nest] 174045 - 07/14/2024, 11:24:59 AM ERROR [Microservices:JobService] Error: /var/lib/immich/upload/8046b9e9-b0cf-46d1-9bc7-542fca747436/81/a3/81a3dc3a-db01-45ea-abe5-ed6996ced369.HEIC: bad seek to 1531357
Jul 14 11:24:59 server2 server[174045]: heif: Unsupported feature: Unsupported codec (4.3000)
Jul 14 11:24:59 server2 server[174045]: at Sharp.toFile (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/node_modules/sharp/lib/output.js:89:19)
Jul 14 11:24:59 server2 server[174045]: at MediaRepository.generateThumbnail (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/dist/repositories/media.repository.js:69:14)
Jul 14 11:24:59 server2 server[174045]: at MediaService.generateThumbnail (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/dist/services/media.service.js:158:48)
Jul 14 11:24:59 server2 server[174045]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Jul 14 11:24:59 server2 server[174045]: at async MediaService.handleGeneratePreview (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/dist/services/media.service.js:135:29)
Jul 14 11:24:59 server2 server[174045]: at async /nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/dist/services/job.service.js:148:36
Jul 14 11:24:59 server2 server[174045]: at async Worker.processJob (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/node_modules/bullmq/dist/cjs/classes/worker.js:394:28)
Jul 14 11:24:59 server2 server[174045]: at async Worker.retryIfFailed (/nix/store/k6sa9kikymqmbnpfbkvnamk1ci793d2p-immich-1.107.1/node_modules/bullmq/dist/cjs/classes/worker.js:581:24)
Jul 14 11:24:59 server2 server[174045]: [Nest] 174045 - 07/14/2024, 11:24:59 AM ERROR [Microservices:JobService] Object:
Jul 14 11:24:59 server2 server[174045]: {
Jul 14 11:24:59 server2 server[174045]: "id": "dd9353ed-3d2d-4099-b6cc-a5e8d5382519",
Jul 14 11:24:59 server2 server[174045]: "source": "upload"
Jul 14 11:24:59 server2 server[174045]: }
Isn't that expected? It is not listed as one of the formats on the Sharp website: https://sharp.pixelplumbing.com/#formats
I think the formatting check is broken. I do exactly what the CI says and nothing is changed any more but the check still fails
CI uses precisely the commit mentioned here to pull nixfkt-rfc-style from:
https://github.com/NixOS/nixpkgs/blob/master/ci/pinned-nixpkgs.json#L2
Using that should pass the check
Yes, the missing rebase was the issue.
I think I have now accounted for every bit of feedback, as well as updated to the latest version of immich
I noticed that a few videos were not getting thumbnails, and traced it back to missing ffmpeg encoders. Switching to ffmpeg-full fixes that
I noticed that a few videos were not getting thumbnails
Do you have any specific examples? Container type, encoding, etc? iirc ffmpeg-full was discouraged due to the larger closure.
I know that at least webp is missing from the normal ffmpeg
Let's leave it as ffmpeg for now, I'll go through and see if we can enable some more codecs in the regular ffmpeg package without impacting closure too much.
Related:
https://github.com/lovell/sharp/issues/3844
https://github.com/immich-app/immich/issues/4899
https://github.com/libvips/libvips/issues/3380
Nice share, this motivated me to dig a bit more.
So in the Docker setup they indeed add the -Dtiff=disable flag. I thought it would be a simple matter of overriding vips with that flag, however it doesn't cut it. It seems that the vips in buildInputs doesn't get used at all. The ./node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.42 appears in the immich derivation regardless if it's included or not. Its ldd output is very small, which makes me think this is the default library included in the sharp npm package, just patchelf-ed.
I managed to make it work by adding the below instructions to the derivation but surely there must be a better way to make sharp use the provided vips.
rm $out/node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.42
ln -s ${vips.out}/lib/libvips-cpp.so.42.17.2 $out/node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.42
Given the pace at which upstream development happens, we might want to warn users to stop the immich apps from auto-updating as we cannot ensure that we will be able to keep up in a timely manner.
I thought it would be a simple matter of overriding vips with that flag, however it doesn't cut it. It seems that the vips in buildInputs doesn't get used at all. The ./node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.42 appears in the immich derivation regardless if it's included or not. Its ldd output is very small, which makes me think this is the default library included in the sharp npm package, just patchelf-ed.
That should not be the case. There's no patchelfing going on here.
If we're downloading binaries, this should also be tagged with the appropriate sourceProvenance.
That should not be the case. There's no patchelfing going on here.
Ah yes indeed, I misinterpreted the output of ldd. It's the same file regardless of the OS.
If we're downloading binaries, this should also be tagged with the appropriate sourceProvenance.
I hope this won't be necessary as sharp supports building from the system vips. While investigating ad-hoc I noticed that it silently fails to build from source unless node-gyp and node-addon-api are installed before running npm install sharp. I suspect that the latter not being present as buildInput causing the issue, although as I haven't managed to package it I can't really be sure.
But when it is, then there will be a ./node_modules/sharp/src/build/Release/sharp-linux-x64.node file which is linked against the provided vips. It still embedds the prebuilt ./node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.42 for some reason but it has less priority so we should be able to delete it (and maybe the whole of ./node_modules/sharp/src/build/Release/sharp-linux-x64.node as upstream does.
(I was testing the automatic review using nixf-tidy, comments are generated above).
Seems like these issues got flagged by the new CI check:
Editing title won't print them to 'Files changed' overview, to avoid duplicate. Once a push happens it will. Also checking escaping with is disabled now.
Not sure why you're replying to me about that, I edited the title because it was inaccurate. And the nixf-tidy check did fire after I edited.
In case you don't know why it behaved like that, nevermind
Not sure if this is the correct place to ask, but I tried the Immich module from this PR (on commit 7290604) and it's not working on my server (however it does run on my main computer). I also tried running the official docker images and those worked, so I presume the issue is with the nix package.
I set IMMICH_LOG_LEVEL to verbose, but still the log only shows this which is not enough information for me to gain any insight:
`journalctl -b -u immich-server`
Started Immich backend server (Self-hosted photo and video backup solution).
immich-server.service: Main process exited, code=dumped, status=4/ILL
immich-server.service: Failed with result 'core-dump'.
immich-server.service: Consumed 27.786s CPU time, no IP traffic.
immich-server.service: Scheduled restart job, restart counter is at 1.
Started Immich backend server (Self-hosted photo and video backup solution).
immich-server.service: Main process exited, code=dumped, status=4/ILL
immich-server.service: Failed with result 'core-dump'.
immich-server.service: Consumed 19.285s CPU time, no IP traffic.
immich-server.service: Scheduled restart job, restart counter is at 2.
Started Immich backend server (Self-hosted photo and video backup solution).
immich-server.service: Main process exited, code=dumped, status=4/ILL
immich-server.service: Failed with result 'core-dump'.
immich-server.service: Consumed 18.356s CPU time, no IP traffic.
immich-server.service: Scheduled restart job, restart counter is at 3.
Started Immich backend server (Self-hosted photo and video backup solution).
immich-server.service: Main process exited, code=dumped, status=4/ILL
immich-server.service: Failed with result 'core-dump'.
immich-server.service: Consumed 18.251s CPU time, no IP traffic.
What kind of processor is this? You're running into illegal instructions and that should basically never happen on non-legacy hardware, especially not given that we target a generic x86_64-processor that should even run machines over a decade old.
Yeah it's quite old. It's an Intel Atom CPU D525. Is this not supported by nixpkgs? I haven't run into any issues running NixOS on it so far.
You'll definitely have to disable machine-learning. Unsure if that'd be sufficient though, that cpu only supports SSE3
I've been testing this module today, and discovered that generating thumbnails failed for heic files from my phone.
Log
Jul 29 19:33:34 weilite server[795]: [Nest] 795 - 07/29/2024, 7:33:34 PM ERROR [Microservices:JobService] Unable to run job handler (thumbnailGeneration/generate-preview): Error: /mnt/XinPhotos/immich/library/admin/2024/2024-05-14/20240514_161132.heic: bad seek to 7948144
Jul 29 19:33:34 weilite server[795]: heif: Unsupported feature: Unsupported codec (4.3000)
Jul 29 19:33:34 weilite server[795]: [Nest] 795 - 07/29/2024, 7:33:34 PM ERROR [Microservices:JobService] Error: /mnt/XinPhotos/immich/library/admin/2024/2024-05-14/20240514_161132.heic: bad seek to 7948144
Jul 29 19:33:34 weilite server[795]: heif: Unsupported feature: Unsupported codec (4.3000)
Jul 29 19:33:34 weilite server[795]: at Sharp.toFile (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/node_modules/sharp/lib/output.js:89:19)
Jul 29 19:33:34 weilite server[795]: at MediaRepository.generateThumbnail (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/dist/repositories/media.repository.js:69:14)
Jul 29 19:33:34 weilite server[795]: at MediaService.generateThumbnail (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/dist/services/media.service.js:164:48)
Jul 29 19:33:34 weilite server[795]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Jul 29 19:33:34 weilite server[795]: at async MediaService.handleGeneratePreview (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/dist/services/media.service.js:135:29)
Jul 29 19:33:34 weilite server[795]: at async /nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/dist/services/job.service.js:148:36
Jul 29 19:33:34 weilite server[795]: at async Worker.processJob (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/node_modules/bullmq/dist/cjs/classes/worker.js:394:28)
Jul 29 19:33:34 weilite server[795]: at async Worker.retryIfFailed (/nix/store/hjw0dx1ap99l7dqi06k1a5f2dmgl0akq-immich-1.109.2/node_modules/bullmq/dist/cjs/classes/worker.js:581:24)
Jul 29 19:33:34 weilite server[795]: [Nest] 795 - 07/29/2024, 7:33:34 PM ERROR [Microservices:JobService] Object:
Jul 29 19:33:34 weilite server[795]: {
Jul 29 19:33:34 weilite server[795]: "id": "db366035-dce6-4d12-8127-67ca60a12fb3"
Jul 29 19:33:34 weilite server[795]: }
This might be related to lovell/sharp#2518, so I agree with @GeoffreyFrogeye that it seems like vips provided in buildInputs is not used in the final result.
What's left here to fix? Looking forward to seeing this merged!
See the unresolved review comments.
I should have time this weekend to address the remaining comments
Great. I think we all appreciate @jvanbruegge continued work, including pioneering the packaging of immich after other continued efforts have failed (e.g. #244803). Considering how this package already provides a lot of value, I think it would be great to merge this after e.g. this weekend, even if not all problems are resolved. We can then open issues for any remaining problems, e.g. with thumbnail creation, and others can step in to fix those problems.
I think it should also generally not be seen as rude to simply take a seemingly stalled PR and continue work on it yourself. In the worst case where the original author does wish to continue working on it, they can simply pull back your changes into their branch. That's the beauty of FOSS and distributed version control.
So, I've addressed all review comments, and updated immich to the latest version. I am now looking into rebuilding sharp.
@Atemu adding the default environment to the environment config option causes the manual to fail, what should be done here?
ok, that took a while, but I finally managed to debug the build failure for pgvecto-rs. Now I can actually test my new changes and investigate the sharp rebuild
@jvanbruegge Maintainer of the pgvecto-rs package here. Thanks for fixing the build failure, I hadn't noticed it was failing! Judging by the date (29th July) it started failing, it seems to be releated to the upgrade to rustc 1.79.
Question for more experienced maintainers: is there a way to get notified when hydra fails to build a package you maintain?
adding the default environment to the environment config option causes the manual to fail, what should be done here?
The usual cause is using options or config in a default value, which necessitates setting defaultText = lib.literalExpression "...", but details will depend on the actual cause if it comes up again.
My only comment is around backups. I dont know immich at all, but do they have a backup solution included or do they just leave that to the user ? If they leave it to the user then it makes sense create a dedicated user and group for immich so that the backup user can just read immich directory as well. If they have a backup solution then maybe dynamic user might be a better fit.
To answer another comment i dont know how to find out with hydra that your builds failed. In my experience you just have to be on unstable and update your system every week with your packages.
Many people were involved in this PR, are we all ok to merge ?
If they leave it to the user then it makes sense create a dedicated user and group for immich
it already does? Immich does not have a dedicated backup feature so far
Many people were involved in this PR, are we all ok to merge ?
No, I am still trying to fix the thumbnails
maybe dynamic user might be a better fit
I think NixOS modules should always use a dynamic user if possible.
I assume in this case it's impossible because multiple services need access to the same data?
Many people were involved in this PR, are we all ok to merge ?
The newest substantial changes were pushed just hours ago, please give people some time to review before calling for further actions.
So, I tested if I really managed to fix the raw/heif issues and yes indeed :tada:
Here are some samples that work on a Docker setup if you want to test for yourself.
Thanks, for having a look at the issue, vips is built with -Dtiff=disable now.
Please pull https://github.com/jvanbruegge/nixpkgs/pull/1
Btw, 1.112 came out eith support for pg-vector 0.3. We are waiting before merging 0.3 to nixpkgs for the update for 1.112 to be done. Take the time you need though .
https://wiki.nixos.org/wiki/Nixpkgs/Reviewing_changes
Thank you for this!
Lookin forward for the merge
Ok, I have updated immich to the latest version and addressed all review comments again
1.115.0 is running nice and smooth for me! Thanks for all the hard work!
Yes, I also upgraded my deployment to the latest version of this PR and everything works
Given the huge popularity of Immich, I'd like to take a bit of time to really thank all the people involved in packaging this.
@jvanbruegge I'd like to thank you for bringing this to the finish line; I know it probably wasn't easy, given this PR was open almost 3 months ago. You started as a user requesting a package and ended up stepping up and sharing your work with the rest of the NixOS community, when it looked like the consensus was having a separate project. I'm sure the community will help you maintain both the package and the module up to date, given the frenetic rate at which Immich is being developed :)
There are a couple of unsung heroes I'd like to mention:
@oddlama, for taking one of the first stabs at this more than a year ago!
@diogotcorreia, for having packaged one of the blockers, pgvecto.rs! You also started by sharing your work in a comment, and ended up making it available to the whole nixpkgs and unblocking @oddlama / @jvanbruegge efforts! Thank you!
And a huge thanks to all the reviewers involved!
Amazing work! How can I properly integrate this into my nix config? Does anyone have a public server config I can take a look at.
Thanks!
https://github.com/jvanbruegge/server-config/blob/86d8f6ff4c9e576cdfd94410dd4e35e58c6e8e5d/caladan/services.nix#L10
Thank you @jvanbruegge, just trying to figure out how to integrate this with the differing directories I have things stored in. Thanks again for all your hard work! Very much appreciated!
back then i wrote this wiki page but not sure if its still up-to date https://wiki.nixos.org/wiki/Immich
Thank you so much for finally bringing immich to nixos!
I have one question: does the default setup support external libraries? Because I tried to add my local picture library on my server to immich as external library, but it cannot access any path I specify. It always gives EACCESS, even though the whole path is readable and executable by everyone.
@ISibboI This is probably because of the service hardening I did in the first version. You will have to add your directory to a ReadWritePaths directive for the relevant systemd units to make it work
@oddlama
This is probably because of the service hardening I did in the first version. You will have to add your directory to a ReadWritePaths directive for the relevant systemd units to make it work
This should be done automatically if it's not the default state directory imo.
I don't think that's the issue, as I also do not use the standard path and have no issues
Congratulations @jvanbruegge! This was one of the most through reviews I've seen, and you made it through! Thanks for all your hard work as well as the hard work of others to get this merged!
I was able to migrate my Docker Compose deployment. An issue I ran into was that file paths in the database were relative to immich's working directory, meaning that everything was prefixed with upload/. I was able to remedy this by replacing upload/ with my mediaLocation (which is also what the UPLOAD_LOCATION variable from my Compose deployment pointed to).
[!NOTE]
This is what worked for my installation that is a few years old. I am not sure if newer installations behave differently. Some facts about my Docker Compose installation:
The database is called immich
The database user is called immich
My UPLOAD_LOCATION (docker mount path) is set to /media/immich-library
Make a backup of your current library and save a copy of the following database dump
Enable NixOS Immich and switch. This will start an empty instance of Immich but will create the database and database user for us.1 In my case it looked like this:
services.immich = {
enable = true;
mediaLocation = "/media/immich-library";
};
Stop NixOS Immich
systemctl stop immich-server.service immich-machine-learning.service
Stop Docker Immich. Leave your postgres container running
Dump your database. The following command is going to dump it into Postgres' data directory, so it will be easy to access from your host system.
docker compose exec database pg_dump --user immich -f /var/lib/postgresql/data/dump.sql immich
Fix unset search_path variable.2
sed -i "s#SELECT pg_catalog.set_config('search_path', '', false);#SELECT pg_catalog.set_config('search_path', 'public', false);#" </path/to/immich/compose>/postgres/dump.sql
Replace upload/ path prefix.3 In my case I replace it with /media/immich-library
sed -i "s#upload/#/media/immich-library#g" </path/to/immich/compose>/postgres/dump.sql
Prepare NixOS database
sudo -u postgres psql immich
immich=# <paste following codeblock and exit>
DROP SCHEMA public CASCADE;
DROP SCHEMA vectors CASCADE;
CREATE SCHEMA public;
CREATE EXTENSION IF NOT EXISTS unaccent;
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
CREATE EXTENSION IF NOT EXISTS vectors;
CREATE EXTENSION IF NOT EXISTS cube;
CREATE EXTENSION IF NOT EXISTS earthdistance;
CREATE EXTENSION IF NOT EXISTS pg_trgm;
ALTER SCHEMA public OWNER TO immich;
ALTER SCHEMA vectors OWNER TO immich;
GRANT SELECT ON TABLE pg_vector_index_stat TO immich;
ALTER EXTENSION vectors UPDATE;
Import your dump. Make sure the file is readable. I moved it to a location that is readable by the postgres user.
sudo -u postgres psql immich -f </path/to/immich/compose>/postgres/dump.sql
Start NixOS Immich
systemctl start immich-server.service immich-machine-learning.service
Make sure you can actually view images on the web app.
If any of these steps fail, you should have your original (unmodified!) database as well as a backup of your media location.
1: As a precaution, you could make your existing Immich library read-only (i.e. chown -R root:root /media/immich-library) to avoid any modifications done by this empty installation of Immich.
2: Restoring a dump that uses Postgres earthdistance seems to fail if search_path isn't set to the target schema. See this StackOverflow comment
3: Perhaps you can inspect your database dump for this first. In my case every file reference started with upload/ (i.e. upload/thumbs/ instead of just thumbs/)
I hope this helps someone out there trying to get this working.
@Scrumplex could you PR that into a migration doc and link it in the patch notes?
Thank you @Scrumplex, I've been working on migration now, luckily I had a backup of my sql because I've broken it hahaha
I have written more in the last hour than I did on average per day for my bachelor's thesis. :sweat_smile:
See https://github.com/NixOS/nixpkgs/pull/344300 for my proposed NixOS manual documentation.
I'll keep "Allow edits and access to secrets by maintainers" in case someone with commit access wants to commit changes into my PR. I will go to bed now! :zzz:
Found an issue with the module, when running immich and changing the group services.immich.group = "test"; the redis service will have the wrong group and fail to start. The issue is this line, so it would make sense to just create the group if the name is immich.
https://github.com/NixOS/nixpkgs/blob/23cbb250f3bf4f516a2d0bf03c51a30900848075/nixos/modules/services/databases/redis.nix#L356
> journalctl -r -u redis-immich.service
Sep 25 04:42:53 HOSTNAME systemd[1]: Failed to start Redis Server - redis-immich.
Sep 25 04:42:53 HOSTNAME systemd[1]: redis-immich.service: Failed with result 'exit-code'.
Sep 25 04:42:53 HOSTNAME systemd[1]: redis-immich.service: Control process exited, code=exited, status=216/GROUP
Sep 25 04:42:53 HOSTNAME (rep-conf)[13315]: redis-immich.service: Failed at step GROUP spawning /nix/store/338pjs37wgmhghid8wbai5qgyssihq2n-redis-immich-prep-conf: No such process
Sep 25 04:42:53 HOSTNAME (rep-conf)[13315]: redis-immich.service: Failed to determine group credentials: No such process
Sep 25 04:42:53 HOSTNAME systemd[1]: Starting Redis Server - redis-immich...
If you use a non-socket postgres connection then services.immich.environment refers to cfg.database.port, but the module doesn't declare this option. Is this a bug, or am I missing something?
@bct i believe that is a bug, I can also reproduce.
Yes, that probably got lost somewhere during all of the rebasing for the reviews
Anyone had success testing this on aarch64?
It tries to build python3Packages.insightface which is broken on aarch64-linux, don't know if it would work removing it (without face recognition obviously). Moreover postgresqlPackages.pgvecto-rstoo is broken onaarch64-linux` and there may be other broken dependencies.
Sorry to interject but please create separate issues rather than commenting on this PR unless it is specifically something that requires the attention of the people who were involved in this PR.
A lot of people are subscribed and this code is in Nixpkgs now, so it should be treated like any other Nixpkgs code.
| gharchive/pull-request | 2024-07-02T19:22:48 | 2025-04-01T06:37:19.192567 | {
"authors": [
"Aleksanaa",
"Atemu",
"GaetanLepage",
"GeoffreyFrogeye",
"ISibboI",
"Kernald",
"NyCodeGHG",
"PowerUser64",
"RomeoV",
"Scrumplex",
"Titaniumtown",
"aciceri",
"bct",
"crertel",
"dav-wolff",
"diogotcorreia",
"dotlambda",
"eclairevoyant",
"gitwah",
"h7x4",
"happysalada",
"inclyc",
"jlbribeiro",
"jpds",
"jvanbruegge",
"oddlama",
"onny",
"qbit",
"rathmerdominik",
"rhoriguchi",
"xinyangli"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/324127",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2387064493 | fedifetcher: 7.1.1 -> 7.1.4
Diff: https://github.com/nanos/FediFetcher/compare/refs/tags/v7.1.1...v7.1.4
Description of changes
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
@ofborg build fedifetcher
| gharchive/pull-request | 2024-07-02T20:06:04 | 2025-04-01T06:37:19.205098 | {
"authors": [
"SuperSandro2000"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/324140",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2434025427 | python312Packages.cyclonedx-python-lib: refactor
Description of changes
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
Result of nixpkgs-review pr 330689 run on x86_64-linux 1
10 packages built:
checkov
checkov.dist
cyclonedx-python
cyclonedx-python.dist
pip-audit
pip-audit.dist
python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist
| gharchive/pull-request | 2024-07-28T16:58:13 | 2025-04-01T06:37:19.215703 | {
"authors": [
"fabaff"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/330689",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2566229353 | parpd: init 2.3.0
Fix https://github.com/NixOS/nixpkgs/issues/345461
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[x] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
@Aleksanaa Done.
| gharchive/pull-request | 2024-10-04T12:12:50 | 2025-04-01T06:37:19.225681 | {
"authors": [
"Bot-wxt1221"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/346418",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2568369348 | renode: 1.15.2 -> 1.15.3
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for renode is: Virtual development framework for complex embedded systems
meta.homepage for renode is: https://renode.io
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.3 in filename of file in /nix/store/dicby0bcpxqa3ws0mpbkz5jnz2w9rz8h-renode-1.15.3
Rebuild report (if merged into master) (click to expand)
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
renode
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/dicby0bcpxqa3ws0mpbkz5jnz2w9rz8h-renode-1.15.3 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A renode https://github.com/r-ryantm/nixpkgs/archive/12bfac6b125be9b6ed323e9f6268566384cb2217.tar.gz
Or:
nix build github:r-ryantm/nixpkgs/12bfac6b125be9b6ed323e9f6268566384cb2217#renode
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dicby0bcpxqa3ws0mpbkz5jnz2w9rz8h-renode-1.15.3
ls -la /nix/store/dicby0bcpxqa3ws0mpbkz5jnz2w9rz8h-renode-1.15.3/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1
1 package built:
renode
Maintainer pings
cc @otavio for testing.
[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.
Add a :+1: reaction to pull requests you find important.
@NixOS/nixpkgs-merge-bot merge
| gharchive/pull-request | 2024-10-05T23:41:29 | 2025-04-01T06:37:19.236570 | {
"authors": [
"otavio",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/346755",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2622978151 | python312Packages.python-docs-theme: 2024.6 -> 2024.10
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.python-docs-theme is: Sphinx theme for CPython project
meta.homepage for python312Packages.python-docs-theme is: https://github.com/python/python-docs-theme
meta.changelog for python312Packages.python-docs-theme is: https://github.com/python/python-docs-theme/blob/2024.10/CHANGELOG.rst
Updates performed
Ran passthru.UpdateScript
To inspect upstream changes
Impact
Checks done
built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.10 with grep in /nix/store/rs2qirl06p9myvkvz5z6m4zlzz83dids-python3.12-python-docs-theme-2024.10
found 2024.10 in filename of file in /nix/store/rs2qirl06p9myvkvz5z6m4zlzz83dids-python3.12-python-docs-theme-2024.10
Rebuild report (if merged into master) (click to expand)
3 total rebuild path(s)
3 package rebuild(s)
First fifty rebuilds by attrpath
python311Packages.python-docs-theme
python312Packages.python-docs-theme
Instructions to test this update (click to expand)
Either download from Cachix:
nix-store -r /nix/store/rs2qirl06p9myvkvz5z6m4zlzz83dids-python3.12-python-docs-theme-2024.10 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.python-docs-theme https://github.com/r-ryantm/nixpkgs/archive/edece1aa0db54b5c144d7f7cc92a7b970026e91e.tar.gz
Or:
nix build github:r-ryantm/nixpkgs/edece1aa0db54b5c144d7f7cc92a7b970026e91e#python312Packages.python-docs-theme
After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rs2qirl06p9myvkvz5z6m4zlzz83dids-python3.12-python-docs-theme-2024.10
ls -la /nix/store/rs2qirl06p9myvkvz5z6m4zlzz83dids-python3.12-python-docs-theme-2024.10/bin
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review
x86_64-linux
:white_check_mark: 4 packages built:
python311Packages.python-docs-theme
python311Packages.python-docs-theme.dist
python312Packages.python-docs-theme
python312Packages.python-docs-theme.dist
Maintainer pings
cc @KAction for testing.
[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.
Add a :+1: reaction to pull requests you find important.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352284
x86_64-linux
:white_check_mark: 4 packages built:
python311Packages.python-docs-theme
python311Packages.python-docs-theme.dist
python312Packages.python-docs-theme
python312Packages.python-docs-theme.dist
| gharchive/pull-request | 2024-10-30T05:43:17 | 2025-04-01T06:37:19.249690 | {
"authors": [
"NickCao",
"r-ryantm"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/352284",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2761556806 | qtcreator: pin llvmPackages 18
Build failure with llvm 19
[161/4146] Building CXX object src/libs/3rdparty/cplusplus/CMakeFiles/3rd_cplusplus.dir/Symbol.cpp.o
[162/4146] Building CXX object src/libs/3rdparty/cplusplus/CMakeFiles/3rd_cplusplus.dir/Symbols.cpp.o
[163/4146] Building C object src/libs/sqlite/CMakeFiles/SqliteInternal.dir/__/3rdparty/sqlite/carray.c.o
[164/4146] Automatic MOC for target QmlPuppetCommunication
[165/4146] Running AUTOMOC file extraction for target QmlPuppetCommunication
[166/4146] Building CXX object src/libs/3rdparty/cplusplus/CMakeFiles/3rd_cplusplus.dir/TranslationUnit.cpp.o
[167/4146] Building CXX object src/libs/languageutils/CMakeFiles/LanguageUtils.dir/fakemetaobject.cpp.o
[168/4146] Building CXX object src/libs/3rdparty/cplusplus/CMakeFiles/3rd_cplusplus.dir/Parser.cpp.o
[169/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqliteglobal.cpp.o
[170/4146] Linking CXX shared library nix/store/zx1wd8m2ndx2fdzb4is3vm6xah094242-qtcreator-15.0.0/lib/qtcreator/libLanguageUtils.so.15.0.0
[171/4146] Creating library symlink nix/store/zx1wd8m2ndx2fdzb4is3vm6xah094242-qtcreator-15.0.0/lib/qtcreator/libLanguageUtils.so.15 nix/store/zx1wd8m2ndx2fdzb4is3vm6xah094242-qtcreator-15.0.0/lib/qtcreator/libLanguageUtils.so
[172/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitebasestatement.cpp.o
FAILED: src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitebasestatement.cpp.o
/nix/store/xl0vlc2wdchfbq8536zs19pj2r3xdmma-clang-wrapper-19.1.5/bin/clang++ -DNANOTRACE_ENABLED -DQT_CORE_LIB -DQT_CREATOR -DQT_DISABLE_DEPRECATED_BEFORE=0x050900 -DQT_DISABLE_DEPRECATED_UP_TO=0x050900 -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_USE_QSTRINGBUILDER -DQT_WARN_DEPRECATED_BEFORE=0x060400 -DQT_WARN_DEPRECATED_UP_TO=0x060400 -DRELATIVE_DATA_PATH=\"../share/qtcreator\" -DRELATIVE_DOC_PATH=\"../share/doc/qtcreator\" -DRELATIVE_LIBEXEC_PATH=\"../libexec/qtcreator\" -DRELATIVE_PLUGIN_PATH=\"../lib/qtcreator/plugins\" -DSQLITEINTERNAL_LIBRARY -DSQLITE_CUSTOM_INCLUDE=config.h -DSQLITE_LIBRARY -DSqlite_EXPORTS -I/build/qt-creator-opensource-src-15.0.0/build/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/../3rdparty/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtCore -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/mkspecs/linux-g++ -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtGui -O3 -DNDEBUG -std=c++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -fPIC -Winvalid-pch -Xclang -include-pch -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx.pch -Xclang -include -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx -MD -MT src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitebasestatement.cpp.o -MF src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitebasestatement.cpp.o.d -o src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitebasestatement.cpp.o -c /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.cpp
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.cpp:4:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:11:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqliteids.h:150:36: error: reference to non-static member function must be called
150 | convertToString(string, id.contextId);
| ~~~^~~~~~~~~
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.cpp:4:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:416:43: error: no member named 'resetter' in 'BaseSqliteResultRange<ResultType>'
416 | : m_statement{std::move(other.resetter)}
| ~~~~~ ^
2 errors generated.
[173/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabase.cpp.o
FAILED: src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabase.cpp.o
/nix/store/xl0vlc2wdchfbq8536zs19pj2r3xdmma-clang-wrapper-19.1.5/bin/clang++ -DNANOTRACE_ENABLED -DQT_CORE_LIB -DQT_CREATOR -DQT_DISABLE_DEPRECATED_BEFORE=0x050900 -DQT_DISABLE_DEPRECATED_UP_TO=0x050900 -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_USE_QSTRINGBUILDER -DQT_WARN_DEPRECATED_BEFORE=0x060400 -DQT_WARN_DEPRECATED_UP_TO=0x060400 -DRELATIVE_DATA_PATH=\"../share/qtcreator\" -DRELATIVE_DOC_PATH=\"../share/doc/qtcreator\" -DRELATIVE_LIBEXEC_PATH=\"../libexec/qtcreator\" -DRELATIVE_PLUGIN_PATH=\"../lib/qtcreator/plugins\" -DSQLITEINTERNAL_LIBRARY -DSQLITE_CUSTOM_INCLUDE=config.h -DSQLITE_LIBRARY -DSqlite_EXPORTS -I/build/qt-creator-opensource-src-15.0.0/build/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/../3rdparty/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtCore -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/mkspecs/linux-g++ -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtGui -O3 -DNDEBUG -std=c++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -fPIC -Winvalid-pch -Xclang -include-pch -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx.pch -Xclang -include -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx -MD -MT src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabase.cpp.o -MF src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabase.cpp.o.d -o src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabase.cpp.o -c /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.cpp
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.cpp:4:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:11:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqliteids.h:150:36: error: reference to non-static member function must be called
150 | convertToString(string, id.contextId);
| ~~~^~~~~~~~~
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.cpp:4:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:416:43: error: no member named 'resetter' in 'BaseSqliteResultRange<ResultType>'
416 | : m_statement{std::move(other.resetter)}
| ~~~~~ ^
2 errors generated.
[174/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabasebackend.cpp.o
FAILED: src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabasebackend.cpp.o
/nix/store/xl0vlc2wdchfbq8536zs19pj2r3xdmma-clang-wrapper-19.1.5/bin/clang++ -DNANOTRACE_ENABLED -DQT_CORE_LIB -DQT_CREATOR -DQT_DISABLE_DEPRECATED_BEFORE=0x050900 -DQT_DISABLE_DEPRECATED_UP_TO=0x050900 -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_USE_QSTRINGBUILDER -DQT_WARN_DEPRECATED_BEFORE=0x060400 -DQT_WARN_DEPRECATED_UP_TO=0x060400 -DRELATIVE_DATA_PATH=\"../share/qtcreator\" -DRELATIVE_DOC_PATH=\"../share/doc/qtcreator\" -DRELATIVE_LIBEXEC_PATH=\"../libexec/qtcreator\" -DRELATIVE_PLUGIN_PATH=\"../lib/qtcreator/plugins\" -DSQLITEINTERNAL_LIBRARY -DSQLITE_CUSTOM_INCLUDE=config.h -DSQLITE_LIBRARY -DSqlite_EXPORTS -I/build/qt-creator-opensource-src-15.0.0/build/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/../3rdparty/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtCore -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/mkspecs/linux-g++ -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtGui -O3 -DNDEBUG -std=c++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -fPIC -Winvalid-pch -Xclang -include-pch -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx.pch -Xclang -include -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx -MD -MT src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabasebackend.cpp.o -MF src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabasebackend.cpp.o.d -o src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitedatabasebackend.cpp.o -c /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabasebackend.cpp
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabasebackend.cpp:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:11:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqliteids.h:150:36: error: reference to non-static member function must be called
150 | convertToString(string, id.contextId);
| ~~~^~~~~~~~~
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabasebackend.cpp:6:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:416:43: error: no member named 'resetter' in 'BaseSqliteResultRange<ResultType>'
416 | : m_statement{std::move(other.resetter)}
| ~~~~~ ^
2 errors generated.
[175/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqliteexception.cpp.o
[176/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitesessionchangeset.cpp.o
FAILED: src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitesessionchangeset.cpp.o
/nix/store/xl0vlc2wdchfbq8536zs19pj2r3xdmma-clang-wrapper-19.1.5/bin/clang++ -DNANOTRACE_ENABLED -DQT_CORE_LIB -DQT_CREATOR -DQT_DISABLE_DEPRECATED_BEFORE=0x050900 -DQT_DISABLE_DEPRECATED_UP_TO=0x050900 -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_USE_QSTRINGBUILDER -DQT_WARN_DEPRECATED_BEFORE=0x060400 -DQT_WARN_DEPRECATED_UP_TO=0x060400 -DRELATIVE_DATA_PATH=\"../share/qtcreator\" -DRELATIVE_DOC_PATH=\"../share/doc/qtcreator\" -DRELATIVE_LIBEXEC_PATH=\"../libexec/qtcreator\" -DRELATIVE_PLUGIN_PATH=\"../lib/qtcreator/plugins\" -DSQLITEINTERNAL_LIBRARY -DSQLITE_CUSTOM_INCLUDE=config.h -DSQLITE_LIBRARY -DSqlite_EXPORTS -I/build/qt-creator-opensource-src-15.0.0/build/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/../3rdparty/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtCore -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/mkspecs/linux-g++ -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtGui -O3 -DNDEBUG -std=c++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -fPIC -Winvalid-pch -Xclang -include-pch -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx.pch -Xclang -include -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx -MD -MT src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitesessionchangeset.cpp.o -MF src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitesessionchangeset.cpp.o.d -o src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitesessionchangeset.cpp.o -c /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitesessionchangeset.cpp
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitesessionchangeset.cpp:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitesessions.h:7:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:11:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqliteids.h:150:36: error: reference to non-static member function must be called
150 | convertToString(string, id.contextId);
| ~~~^~~~~~~~~
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitesessionchangeset.cpp:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitesessions.h:7:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:416:43: error: no member named 'resetter' in 'BaseSqliteResultRange<ResultType>'
416 | : m_statement{std::move(other.resetter)}
| ~~~~~ ^
2 errors generated.
[177/4146] Building CXX object src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitefunctionregistry.cpp.o
FAILED: src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitefunctionregistry.cpp.o
/nix/store/xl0vlc2wdchfbq8536zs19pj2r3xdmma-clang-wrapper-19.1.5/bin/clang++ -DNANOTRACE_ENABLED -DQT_CORE_LIB -DQT_CREATOR -DQT_DISABLE_DEPRECATED_BEFORE=0x050900 -DQT_DISABLE_DEPRECATED_UP_TO=0x050900 -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_USE_QSTRINGBUILDER -DQT_WARN_DEPRECATED_BEFORE=0x060400 -DQT_WARN_DEPRECATED_UP_TO=0x060400 -DRELATIVE_DATA_PATH=\"../share/qtcreator\" -DRELATIVE_DOC_PATH=\"../share/doc/qtcreator\" -DRELATIVE_LIBEXEC_PATH=\"../libexec/qtcreator\" -DRELATIVE_PLUGIN_PATH=\"../lib/qtcreator/plugins\" -DSQLITEINTERNAL_LIBRARY -DSQLITE_CUSTOM_INCLUDE=config.h -DSQLITE_LIBRARY -DSqlite_EXPORTS -I/build/qt-creator-opensource-src-15.0.0/build/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/../3rdparty/sqlite -I/build/qt-creator-opensource-src-15.0.0/src/libs -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtCore -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/mkspecs/linux-g++ -isystem /nix/store/dh5kclrfrvk7aknvk22n2bnz4x8kj1q6-qtbase-6.8.1/include/QtGui -O3 -DNDEBUG -std=c++20 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -fPIC -Winvalid-pch -Xclang -include-pch -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx.pch -Xclang -include -Xclang /build/qt-creator-opensource-src-15.0.0/build/src/libs/3rdparty/syntax-highlighting/CMakeFiles/QtCreatorPchConsole.dir/cmake_pch.hxx -MD -MT src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitefunctionregistry.cpp.o -MF src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitefunctionregistry.cpp.o.d -o src/libs/sqlite/CMakeFiles/Sqlite.dir/sqlitefunctionregistry.cpp.o -c /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitefunctionregistry.cpp
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitefunctionregistry.cpp:4:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitefunctionregistry.h:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:11:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqliteids.h:150:36: error: reference to non-static member function must be called
150 | convertToString(string, id.contextId);
| ~~~^~~~~~~~~
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitefunctionregistry.cpp:4:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitefunctionregistry.h:6:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitedatabase.h:9:
In file included from /build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitereadstatement.h:6:
/build/qt-creator-opensource-src-15.0.0/src/libs/sqlite/sqlitebasestatement.h:416:43: error: no member named 'resetter' in 'BaseSqliteResultRange<ResultType>'
416 | : m_statement{std::move(other.resetter)}
| ~~~~~ ^
2 errors generated.
[178/4146] Automatic MOC and UIC for target Utils
[179/4146] Building C object src/libs/sqlite/CMakeFiles/SqliteInternal.dir/__/3rdparty/sqlite/sqlite3.c.o
Things done
Built on platform(s)
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] sandbox = relaxed
[ ] sandbox = true
[ ] Tested, as applicable:
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] Fits CONTRIBUTING.md.
Add a :+1: reaction to pull requests you find important.
@ofborg build qtcreator
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368736
x86_64-linux
:fast_forward: 10 packages marked as broken and skipped:
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages_5.mivisionx
rocmPackages_5.mivisionx-cpu
rocmPackages_5.mivisionx-hip
rocmPackages_5.mivisionx-opencl
rocmPackages_6.mivisionx
rocmPackages_6.mivisionx-cpu
rocmPackages_6.mivisionx-hip
:white_check_mark: 1 package built:
qtcreator
| gharchive/pull-request | 2024-12-28T06:43:21 | 2025-04-01T06:37:19.265890 | {
"authors": [
"wentasah",
"wineee"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/368736",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
339219592 | whitebox-tools: init at 0.9.0
Motivation for this change
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.
@GrahamcOfBorg build whitebox-tools
Failure on aarch64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
cannot build derivation '/nix/store/1hgh2pg0gis0g29dkcc5aj5gh2a03ci8-rust_serde_derive-1.0.18.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/132j7mfl04zb7vlhdj9a6kgm6i3668bj-rust_crates-io-0.11.0.drv': 30 dependencies couldn't be built
cannot build derivation '/nix/store/37lmq2kc9fwscasgjvwr5s7wpjgjd636-rust_docopt-0.8.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/6i9xgpvlp3i943v09n91p4yc97vhhcvc-rust_git2-curl-0.7.0.drv': 20 dependencies couldn't be built
cannot build derivation '/nix/store/hdsnr2qc7ac19rnb9mrl3hj7w3107gzh-rust_ignore-0.2.2.drv': 18 dependencies couldn't be built
cannot build derivation '/nix/store/sbg4sjdjg534ij7g4ki9vj41s5kxiisq-rust_cargo-0.22.0.drv': 78 dependencies couldn't be built
cannot build derivation '/nix/store/vdaccxg8m8yjxk4vhv2m54ygykmhfabs-rust_cargo-vendor-0.1.13.drv': 79 dependencies couldn't be built
cannot build derivation '/nix/store/szv1gqq935xrhsb9bsj76i268qg779fa-whitebox_tools-0.9.0-vendor.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/i03ar26jrqv7snss735w73wlcr3wpm4q-whitebox_tools-0.9.0.drv': 3 dependencies couldn't be built
error: build of '/nix/store/i03ar26jrqv7snss735w73wlcr3wpm4q-whitebox_tools-0.9.0.drv' failed
Failure on x86_64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
cannot build derivation '/nix/store/gk7jma27balgcjhkm4r40zrb64b39hn5-rust_serde_derive-1.0.18.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/cb42b4wsk5531gfvw7nagwhk100dlh8z-rust_crates-io-0.11.0.drv': 30 dependencies couldn't be built
cannot build derivation '/nix/store/sly01qb04j3i03qi3m61905v8v5c7lvb-rust_docopt-0.8.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/w9zzb5fdr7pb1afv7j2lc3ls2nz0yg26-rust_git2-curl-0.7.0.drv': 20 dependencies couldn't be built
cannot build derivation '/nix/store/dz3j5lf77pd0pjv4jy971z8nnmp4qxhw-rust_ignore-0.2.2.drv': 18 dependencies couldn't be built
cannot build derivation '/nix/store/53xkf9vyx0b7ipw0b383jr5dsz82bhjd-rust_cargo-0.22.0.drv': 78 dependencies couldn't be built
cannot build derivation '/nix/store/yjvsqlbilv24ychxkd52qylf7qcqk93n-rust_cargo-vendor-0.1.13.drv': 79 dependencies couldn't be built
cannot build derivation '/nix/store/4c1vdq45pl0cfx73m08pmm35if3cgyag-whitebox_tools-0.9.0-vendor.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/22mqd97n017cjr5p9nyiivr09vkzmp93-whitebox_tools-0.9.0.drv': 3 dependencies couldn't be built
error: build of '/nix/store/22mqd97n017cjr5p9nyiivr09vkzmp93-whitebox_tools-0.9.0.drv' failed
Looks like rustc-1.27.0 is broken.
Success on x86_64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
shrinking /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin/whitebox_tools
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
checking for references to /build in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0...
/nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
Failure on x86_64-darwin (full log)
Attempted: whitebox-tools
Partial log (click to expand)
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
error: aborting due to previous error
error: Could not compile `whitebox_tools`.
To learn more, run the command again with --verbose.
builder for '/nix/store/z75nbfh8m4v0gazbzbja0w1nk3i71rc9-whitebox_tools-0.9.0.drv' failed with exit code 101
[31;1merror:[0m build of '/nix/store/z75nbfh8m4v0gazbzbja0w1nk3i71rc9-whitebox_tools-0.9.0.drv' failed
Success on aarch64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
shrinking /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0/bin/whitebox_tools
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
checking for references to /build in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0...
/nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
I'll fix this on darwin.
@GrahamcOfBorg build whitebox-tools
Success on aarch64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
/nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
Success on x86_64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
shrinking /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin/whitebox_tools
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
checking for references to /build in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0...
/nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
to check darwin build:
@GrahamcOfBorg build whitebox-tools
Success on x86_64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
shrinking /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin/whitebox_tools
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
checking for references to /tmp/nix-build-whitebox_tools-0.9.0.drv-0 in /nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0...
/nix/store/bqyzzfda84cfamsqm57pcxd0a4yqa8f1-whitebox_tools-0.9.0
Success on x86_64-darwin (full log)
Attempted: whitebox-tools
Partial log (click to expand)
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
installing
post-installation fixup
strip is /nix/store/7ddbq63v97nk8gkbf7gcsfmby37h6gbl-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/yr4b8lpfjixkh97nn8a73qhrj3z5q10n-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/yr4b8lpfjixkh97nn8a73qhrj3z5q10n-whitebox_tools-0.9.0
/nix/store/yr4b8lpfjixkh97nn8a73qhrj3z5q10n-whitebox_tools-0.9.0
Success on aarch64-linux (full log)
Attempted: whitebox-tools
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
shrinking /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0/bin/whitebox_tools
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0/bin
patching script interpreter paths in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
checking for references to /build in /nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0...
/nix/store/1q5xyrymspw126pzhlc8jzrnr5lq8d3i-whitebox_tools-0.9.0
| gharchive/pull-request | 2018-07-08T11:50:16 | 2025-04-01T06:37:19.283632 | {
"authors": [
"GrahamcOfBorg",
"Infinisil",
"mpickering",
"nlewo",
"xeji"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/43218",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
367221175 | zn_poly: 0.9 -> 0.9.1
Motivation for this change
Sage has taken over maintenance since the original author no longer
maintains the project.
The upgrade integrates various patches from sage. It also enables tuning by default, which now has to be disabled explicitly.
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[ ] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.
Success on aarch64-linux (full log)
Attempted: zn_poly
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1
shrinking /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1/lib/libzn_poly.so
shrinking /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1/lib/libzn_poly-0.9.so
shrinking /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1/lib/libzn_poly-0.9.1.so
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1/lib
patching script interpreter paths in /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1
checking for references to /build in /nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1...
/nix/store/ff4ya6fy78g5fzzym185sfk8fg3wr8kp-zn_poly-0.9.1
Success on x86_64-darwin (full log)
Attempted: zn_poly
Partial log (click to expand)
zn_array_mul_fft_dft()... ok
zn_array_invert()... ok
All tests passed.
installing
post-installation fixup
strip is /nix/store/9xjkb4xz0b5lmizij9ppxy7lkxdxhx6b-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/5rns1nmh7zkkljdsax34s6714q17wdkk-zn_poly-0.9.1/lib
patching script interpreter paths in /nix/store/5rns1nmh7zkkljdsax34s6714q17wdkk-zn_poly-0.9.1
/nix/store/5rns1nmh7zkkljdsax34s6714q17wdkk-zn_poly-0.9.1
Success on x86_64-linux (full log)
Attempted: zn_poly
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1
shrinking /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1/lib/libzn_poly-0.9.1.so
shrinking /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1/lib/libzn_poly-0.9.so
shrinking /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1/lib/libzn_poly.so
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1/lib
patching script interpreter paths in /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1
checking for references to /build in /nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1...
/nix/store/85iam4zzihnkkrjrlanal487ykv03xa5-zn_poly-0.9.1
| gharchive/pull-request | 2018-10-05T13:51:59 | 2025-04-01T06:37:19.292699 | {
"authors": [
"GrahamcOfBorg",
"timokau"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/47915",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
368416151 | gitea: 1.5.1 -> 1.5.2
Motivation for this change
https://blog.gitea.io/2018/10/gitea-1.5.2-is-released/
“This is a smaller release, with only 12 merged PRs, but it contains several security related fixes and so we recommend upgrading whenever possible.”
Should therefore be safe to backport to 18.09, and required to get the security fixes.
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.
Maintainer: @disassembler
Failure on aarch64-linux (full log)
Attempted: gitea
Partial log (click to expand)
code.gitea.io/gitea/models
code.gitea.io/gitea/modules/notification
code.gitea.io/gitea/modules/templates
code.gitea.io/gitea/modules/auth
code.gitea.io/gitea/modules/context
code.gitea.io/gitea/modules/lfs
code.gitea.io/gitea/routers/repo
code.gitea.io/gitea/routers/user
builder for '/nix/store/rz4y8f8pppi5k194gj7k89cskiapy8hf-gitea-1.5.2.drv' failed with exit code 47
error: build of '/nix/store/rz4y8f8pppi5k194gj7k89cskiapy8hf-gitea-1.5.2.drv' failed
Unexpected error: command failed with exit code 1 on x86_64-darwin (full log)
Attempted: gitea
Partial log (click to expand)
trying https://github.com/go-gitea/gitea/archive/v1.5.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 122 0 122 0 0 203 0 --:--:-- --:--:-- --:--:-- 202
100 17.9M 0 17.9M 0 0 4643k 0 --:--:-- 0:00:03 --:--:-- 6856k
unpacking source archive /private/tmp/nix-build-source.drv-0/v1.5.2.tar.gz
fixed-output derivation produced path '/nix/store/4gydlwklm9v77jk8zj3n03f7csmkq18z-source' with sha256 hash '1dr7pxb60y215625nndmisxl6n5zlq1aicaswsg3xfzlk7a93k7k' instead of the expected hash '049f4gs1lw14l0ybz6rx6sibwpqdihqrx1qgvs6ghy6asrc2blif'
cannot build derivation '/nix/store/jsm9n5l3qsr8n7filwzmcbxvkvpgf3xa-gitea-1.5.2.drv': 1 dependencies couldn't be built
error: build of '/nix/store/jsm9n5l3qsr8n7filwzmcbxvkvpgf3xa-gitea-1.5.2.drv' failed
aarch64 failure looks like a builder issue, we can try again later.
Please fix the hash mismatch on darwin.
Success on x86_64-linux (full log)
Attempted: gitea
Partial log (click to expand)
checking for references to /build in /nix/store/fz05imgv890j71v5jp8bc8j54wqvx9is-gitea-1.5.2-bin...
shrinking RPATHs of ELF executables and libraries in /nix/store/hypb926rcw4dw6df3pf9pshrj54mnxvy-gitea-1.5.2
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/hypb926rcw4dw6df3pf9pshrj54mnxvy-gitea-1.5.2
checking for references to /build in /nix/store/hypb926rcw4dw6df3pf9pshrj54mnxvy-gitea-1.5.2...
shrinking RPATHs of ELF executables and libraries in /nix/store/mj23a6lwgj105m2z58rh6llrn3mjymh8-gitea-1.5.2-data
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/mj23a6lwgj105m2z58rh6llrn3mjymh8-gitea-1.5.2-data
checking for references to /build in /nix/store/mj23a6lwgj105m2z58rh6llrn3mjymh8-gitea-1.5.2-data...
/nix/store/fz05imgv890j71v5jp8bc8j54wqvx9is-gitea-1.5.2-bin
@GrahamcOfBorg build gitea
Unexpected error: command failed with exit code 1 on x86_64-darwin (full log)
Attempted: gitea
Partial log (click to expand)
trying https://github.com/go-gitea/gitea/archive/v1.5.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 122 0 122 0 0 652 0 --:--:-- --:--:-- --:--:-- 655
100 17.9M 0 17.9M 0 0 5791k 0 --:--:-- 0:00:03 --:--:-- 6654k
unpacking source archive /private/tmp/nix-build-source.drv-0/v1.5.2.tar.gz
fixed-output derivation produced path '/nix/store/4gydlwklm9v77jk8zj3n03f7csmkq18z-source' with sha256 hash '1dr7pxb60y215625nndmisxl6n5zlq1aicaswsg3xfzlk7a93k7k' instead of the expected hash '049f4gs1lw14l0ybz6rx6sibwpqdihqrx1qgvs6ghy6asrc2blif'
cannot build derivation '/nix/store/jsm9n5l3qsr8n7filwzmcbxvkvpgf3xa-gitea-1.5.2.drv': 1 dependencies couldn't be built
error: build of '/nix/store/jsm9n5l3qsr8n7filwzmcbxvkvpgf3xa-gitea-1.5.2.drv' failed
Success on x86_64-linux (full log)
Attempted: gitea
Partial log (click to expand)
/nix/store/fz05imgv890j71v5jp8bc8j54wqvx9is-gitea-1.5.2-bin
Failure on aarch64-linux (full log)
Attempted: gitea
Partial log (click to expand)
code.gitea.io/gitea/routers/api/v1/repo
code.gitea.io/gitea/routers/api/v1/user
code.gitea.io/gitea/routers
code.gitea.io/gitea/routers/api/v1/org
code.gitea.io/gitea/routers/api/v1/admin
code.gitea.io/gitea/routers/admin
code.gitea.io/gitea/routers/api/v1
code.gitea.io/gitea/routers/routes
builder for '/nix/store/rz4y8f8pppi5k194gj7k89cskiapy8hf-gitea-1.5.2.drv' failed with exit code 45
error: build of '/nix/store/rz4y8f8pppi5k194gj7k89cskiapy8hf-gitea-1.5.2.drv' failed
builds fine on aarch64 when issued with --option cores 2. Probably some limitation with the default go routine settings. I vaguely recall some default thread limits.
@NixOS/darwin-maintainers Any idea why fetchFromGitHub expects a different hash on darwin?
@ElvishJerricco posted the following on IRC:
$ nix-prefetch-url --unpack https://github.com/go-gitea/gitea/archive/v1.5.2.tar.gz
unpacking...
path is '/nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz'
049f4gs1lw14l0ybz6rx6sibwpqdihqrx1qgvs6ghy6asrc2blif
$ ssh my-mac nix-prefetch-url --unpack https://github.com/go-gitea/gitea/archive/v1.5.2.tar.gz
unpacking...
path is '/nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz'
1dr7pxb60y215625nndmisxl6n5zlq1aicaswsg3xfzlk7a93k7k
```
My first guess is that it's due to macOS's case sensitive file system, but I haven't confirmed that the repo actually has any collisions.
Doesn't appear to have obvious case collisions on this macOS, so I'm not sure why it fails.
Furthermore, I'm on macOS, and:
$ nix-prefetch-url --unpack https://github.com/go-gitea/gitea/archive/v1.5.2.tar.gz
unpacking...
path is '/nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz'
049f4gs1lw14l0ybz6rx6sibwpqdihqrx1qgvs6ghy6asrc2blif
I'm not running a case-sensitive filesystem so I'm puzzled.
@ElvishJerricco I can't get the other .tar.gz, but perhaps you can unpack and diff the two trees on your linux box?
@copumpkin:
$ linux=/nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz
$ mac=/nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz
$ diff -r $linux $mac
Only in /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/heads: ブランチ
Only in /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/heads: ブランチ
Only in /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/heads: Grüßen
Only in /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/heads: Grüßen
Only in /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/tags: タグ
Only in /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/tags: タグ
Only in /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/tags: Ё
Only in /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/integrations/gitea-repositories-meta/user2/utf8.git/refs/tags: Ё
diff: /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/tz/testdata/testdir.lnk: No such file or directory
diff: /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/tz/testdata/testdir.lnk: No such file or directory
diff: /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/tz/testdata/test.lnk: No such file or directory
diff: /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/tz/testdata/test.lnk: No such file or directory
diff: /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/zip/testdata/testdir.lnk: No such file or directory
diff: /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/zip/testdata/testdir.lnk: No such file or directory
diff: /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/zip/testdata/test.lnk: No such file or directory
diff: /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/vendor/github.com/Unknwon/cae/zip/testdata/test.lnk: No such file or directory
diff: /nix/store/n3bg2vhxv8yfc631la9gfykglg3f55b3-v1.5.2.tar.gz/vendor/gopkg.in/macaron.v1/fixtures/symlink: No such file or directory
diff: /nix/store/jq8p6y5zjzhaipsb5wg6bqziw7i45q7g-v1.5.2.tar.gz/vendor/gopkg.in/macaron.v1/fixtures/symlink: No such file or directory
Maybe something unicode related? I'm on sierra, if that matters.
Ah yes, some of the unicode normalization of combining pairs (whether to store them as two characters or one) behavior can be weird. Not really sure what to do about that, other than to add a postFetch step to our fetchFromGitHub that strips that junk out
@copumpkin @ElvishJerricco does any of you have the time to implement test it?
I do not have a Mac to test it and never used one. Would probably take me 10x just to figure that out with always going through ofBorg :confused:
Here is a previous occurrence of the same issue.
If subdirs vendor and integrations are not necessary to the build process, then you can do:
src = fetchFromGitHub {
owner = "go-gitea";
repo = "gitea";
rev = "v${version}";
sha256 = "049f4gs1lw14l0ybz6rx6sibwpqdihqrx1qgvs6ghy6asrc2blif";
extraPostFetch = "rm -rf $out/integrations && rm -rf $out/vendor";
};
@c0bw3b you'll need to update the sha256 there.
Yes indeed that hash needs to be re-computed. I edited the code block.
Thank you all for taking a look at this, I was really lost at how it could possibly be the case that MacOS computes a different checksum than on Linux.
As one could expect from their names, I just verified that integrations contains integration tests and is not required for build, while vendor contains various third-party library dependencies and is indeed required, and needs selective manual / automatic filtering.
For further testing / discussion, I pushed a new version with a extraPostFetch that deletes offending files and still seems to work for me.
Some kind of automatic mechanism in the fetch function would still help though, so that this won't return on the next release, and nix-prefetch-git gives the correct sha256 sum. This would lead to hard-to-detect problems though if some project uses / starts to use affected unicode regions in file names that are relevant for the build process.
Could someone with the appropriate permissions please trigger a @GrahamcOfBorg build gitea?
@GrahamcOfBorg build gitea
Failure on aarch64-linux (full log)
Attempted: gitea
Partial log (click to expand)
code.gitea.io/gitea/vendor/github.com/Unknwon/cae/zip
code.gitea.io/gitea/vendor/github.com/glycerine/go-unsnap-stream
code.gitea.io/gitea/vendor/github.com/couchbase/vellum
code.gitea.io/gitea/vendor/code.gitea.io/git
code.gitea.io/gitea/vendor/github.com/Unknwon/i18n
code.gitea.io/gitea/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1
code.gitea.io/gitea/vendor/github.com/go-xorm/xorm
code.gitea.io/gitea/vendor/gopkg.in/testfixtures.v2
builder for '/nix/store/8jijwi2w49hsyfcyhb0mgana4hxp6sbd-gitea-1.5.2.drv' failed with exit code 43
error: build of '/nix/store/8jijwi2w49hsyfcyhb0mgana4hxp6sbd-gitea-1.5.2.drv' failed
Works fine on my mac.
$ nix build -f https://github.com/NixOS/nixpkgs/archive/0a5c7cf512fcefb4b337186f0aee69ae8dd1df2c.tar.gz gitea.src
[1 built, 55 copied (111.7 MiB), 37.0 MiB DL]
/nix/store/cg1gbwbc68ilw81djc13hp78bhgfsqq1-source
Success on x86_64-linux (full log)
Attempted: gitea
Partial log (click to expand)
checking for references to /build in /nix/store/7jk9mp702a9ry6qnv2rc40vhl8pxrzl8-gitea-1.5.2-bin...
shrinking RPATHs of ELF executables and libraries in /nix/store/w5h82yifgv8ifcpjm73v288k65n49766-gitea-1.5.2
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/w5h82yifgv8ifcpjm73v288k65n49766-gitea-1.5.2
checking for references to /build in /nix/store/w5h82yifgv8ifcpjm73v288k65n49766-gitea-1.5.2...
shrinking RPATHs of ELF executables and libraries in /nix/store/h51jpsy5mwx25h73qx3jj4vbs6gfll6z-gitea-1.5.2-data
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/h51jpsy5mwx25h73qx3jj4vbs6gfll6z-gitea-1.5.2-data
checking for references to /build in /nix/store/h51jpsy5mwx25h73qx3jj4vbs6gfll6z-gitea-1.5.2-data...
/nix/store/7jk9mp702a9ry6qnv2rc40vhl8pxrzl8-gitea-1.5.2-bin
18.03: 8ccf5b63b5786fbf1fdda05132df30e78260139b
18.09: 38f5b076d77ce204a237a5dc9238c3586e607707
Thanks! :smiley:
| gharchive/pull-request | 2018-10-09T22:01:52 | 2025-04-01T06:37:19.318548 | {
"authors": [
"ElvishJerricco",
"GrahamcOfBorg",
"andir",
"c0bw3b",
"copumpkin",
"florianjacob",
"xeji"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/48128",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
425131118 | linux_testing_bcachefs,bcachefs-tools: 2019-03-29
Motivation for this change
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
At least bcachefs-tools is broken on 2019-03-29.
Thank you!
| gharchive/pull-request | 2019-03-25T21:48:57 | 2025-04-01T06:37:19.324564 | {
"authors": [
"dywedir",
"eadwu"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/58296",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
58515055 | updating bitcoin and changing source location
I propose we pull the source from bitcoin.org, since the sha256 sums that are GPG signed match the source packages on bitcoin.org, but not the packages on github.
See:
https://bitcoin.org/bin/bitcoin-core-0.10.0/SHA256SUMS.asc
https://bitcoin.org/bin/bitcoin-core-0.10.0/bitcoin-0.10.0.tar.gz
https://github.com/bitcoin/bitcoin/archive/v0.10.0.tar.gz
Paging @roconnor @AndersonTorres since you are listed as maintainers.
| gharchive/pull-request | 2015-02-22T19:37:47 | 2025-04-01T06:37:19.327358 | {
"authors": [
"sfultong"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/6523",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
506861692 | dask: 2.2.0 -> 2.5.2, distributed: 2.4.0 -> 2.5.2, dask-ml: 0.11.0 -> 1.0.0, dask-jobqueue: 0.4.1 -> 0.7.0
Motivation for this change
Dask and relative packages were quite outdated.
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[ ] NixOS
[ ] macOS
[x] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.
Notify maintainers
cc @FRidh @costrouc
Thanks for the changes! Would you mind splitting out each update to its own commit? That makes it easier for tooling that uses the commit format, and also to selectively back out if something goes wrong.
@teh No problem, there are now four commits.
apologies, one more commit style change suggestion: distributed: 2.4.0->2.5.2 to distributed: 2.4.0 -> 2.5.2 (check the git commit log of nixpkgs for other examples). LGTM otherwise, thanks!
@GrahamcOfBorg build python3.pkgs.dask python3.pkgs.distributed python3.pkgs.dask-ml python3.pkgs.dask-jobqueue
apologies, one more commit style change suggestion: distributed: 2.4.0->2.5.2 to distributed: 2.4.0 -> 2.5.2 (check the git commit log of nixpkgs for other examples). LGTM otherwise, thanks!
Even better, prefix with the package set so it is an actual attribute path. That way the bot can pick it up.
So what do I have to do to get these packages updated? It's been ten days and I see that dask has already been replaced in master.
@francescocarzaniga I think roughly:
resolve conflict
prefix packages e.g. pythonPackages.dask-ml
ping @FRidh to merge
Nothing happening so closing.
| gharchive/pull-request | 2019-10-14T20:36:20 | 2025-04-01T06:37:19.336109 | {
"authors": [
"FRidh",
"francescocarzaniga",
"teh"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/71141",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
509367825 | kubecfg: 0.12.5 -> 0.13.1
Motivation for this change
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)
[ ] NixOS
[x] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Notify maintainers
cc @
@GrahamcOfBorg build kubecfg
| gharchive/pull-request | 2019-10-19T00:58:33 | 2025-04-01T06:37:19.341424 | {
"authors": [
"groodt",
"jonringer"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/71372",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
582536852 | Freeform modules
Motivation for this change
This implement freeform modules, which are like a combination between types.submodule and types.attrsOf: The options declared with the submodule are type-checked, while the others are combined using a freeform type. This has been a desired feature in multiple occasions now:
This will simplify NixOS/rfcs#42 drastically, making the process of declaring options corresponding to settings values very conventional.
Type checking for nixpkgs' config argument, as previously attempted in https://github.com/NixOS/nixpkgs/pull/57123 and https://github.com/NixOS/nixpkgs/pull/80582, will now be possible in a sane way.
How it looks like (updated for latest version) (evaluate with nix-instantiate --eval --strict example.nix -A config)
with import ./lib; evalModules {
modules = [{
options.settings = mkOption {
default = {};
type = with types; submodule {
# All values that don't have an associated option have to be of this type
freeformType = attrsOf int;
options.port = mkOption {
type = port;
default = 80;
description = "The port to use.";
};
};
};
# Works, even though foo isn't declared as an option
config.settings.foo = 10;
# error: The option value `settings.port' in `example.nix' is not of type
# `16 bit unsigned integer; between 0 and 65535 (both inclusive)'.
#config.settings.port = "not-a-port";
## Overrides default value
config.settings.port = 8080;
}];
}
Ping @roberth @Ma27 @rycee @Profpatsch @oxij
TODO
[x] Write tests
[x] Potentially separate orthogonal changes into a separate PR
[x] Write docs
[x] Check how this affects performance -> The current implementation is slower than it could be when many freeform values are defined, but since the number of them per module evaluation is expected to be rather low, I'll leave it at this for now.
I now separated the orthogonal changes into https://github.com/NixOS/nixpkgs/pull/82751
I don't think attrValueType is necessary if you merge in one go at the root of the submodule and then recursiveUpdate the unstructured values back into config.
This puts less burden on the types and, if we don't hardcode recursiveUpdate, it allows the module author to keep the unstructured attributes separate if desired.
@roberth I don't think this would work without big changes, because currently it's not known upfront which values are unstructured and which aren't, and this could get complicated with nested submodules and attrsOf and such.
@Infinisil mergeModules could return the option values and unstructured attrs separately. Doing so should also fix the laziness problem caused by generating fake option names for the unstructured definitions.
Quote for when the commit is lost:
TODO: This leads to infinite recursion in NixOS if it's always turned on, so some use cases won't be supported anymore because of unstructured attrs. Figure out what they are.
One feature I suspect may be lost due to this change is the ability to check for the existence of option declarations before defining them, which I think will be important when modules move into flakes and need to adapt a bit at runtime to their now variable environment.
I've used this to optionally define NixOps deployment keys in a NixOS-compatible module.
I'll make sure we have a test for this laziness property.
@roberth I think I see what you mean, this might be possible, I'll give it a try soon. Implementation would be a bit like: Do a recursive mergeModules' for declared options first. After that, determine which definitions haven't been matched with a declaration, and merge those with a single unstructured type. Then combine the results of the mergeModules' and the unstructured merge with something like recursiveUpdate (it will need to insert the fake option declarations). I don't think it needs to be configurable though, as it will essentially only allow unstructured values under option sets, which makes a lot of sense, and is also the behavior of the current implementation.
@roberth Done that! Commits need some cleanup, and other things are still left to do, but now the code is looking much nicer. I also did some very sweet cleanups related to this. Also I'm now not generating fake options anymore: Only .config will now contain unstructured values, .options doesn't, which should then also not get in the way of what you mentioned in https://github.com/NixOS/nixpkgs/pull/82802.
Unfortunately without attrValueType, a specific error message is significantly worse: With something like
{
config._module.unstructuredType = attrsOf int;
options.a.b = mkOption {};
config.a.c = "foo";
}
it now throws
The option value `a' in `example.nix' is not of type `signed integer'.
and if you change it to
{ config.a = 0; }
you get (as expected)
error: The option path `a' is an attribute set of options,
but it is defined to not be an attribute set in `example.nix'.
Did you define its value at the correct and complete path?
Instead of the previous (code now in https://github.com/Infinisil/nixpkgs/tree/partially-typed-v2-old)
The option `a.c' defined in `example.nix' does not exist
and the unstructured type `signed integer' of `a' does not support attribute sets.
I could get back the original error message if I add attrValueType again, but I'm not sure if it's worth it. Maybe that's better left for the future.
error message
This can probably be improved quite a bit by rethrowing the error with an extra message.
"The module at ${prefix} allows undeclared definitions to be mixed with known options, but a definition did not satisfy the type for undeclared definitions: ${caughtMsg}. This may also be the result of mistyping an otherwise known option."
@roberth Hm it does work with builtins.tryEval and a deepSeq on the unstructuredType.merge ..., but that's not very nice. I'd have to do some changes to how types throw errors to make it work without tryEval.
I think I'll have to get the attrValueType thing back after all. Not only does it allow for much better error messages in some cases, but after doing a performance check, I also found that the whole definition coercion thing is really slow due to the many list operations.
@roberth I think let's not do this attrValueType thing after all, for now. The current implementation here works well and has clean and simple code, the only problem is that it can be a bit slow if there are many unstructured attributes, but that will be a rare occurence. If this does becomes a problem in the future, it can still be changed then, though ideally this would also bring some module system improvements along with it so attrValueType can be implemented nicely (which it currently can't).
So I think the only thing left to do here is to write some docs. Also I think the naming is a bit off, it's not "partially typed modules", because everything is still type checked, there's just a fallback type now for undeclared options. "unstructured attributes" is also a bit unfitting. Maybe the feature could be called "Fallback-typing" instead.
I have now written some initial docs for this feature. Once the docs are finalized and reviewed, I think this is ready to be merged.
The docs read like you're describing a change, like you would in an rfc or a commit message
Yeah that's what I noticed too, will definitely try to improve on that
Another use would be to use packages as submodules,like what I would like to do in https://github.com/NixOS/nixpkgs/pull/89943
@roberth What do you think would be a better term for this feature? Maybe one of:
A fallback option type
Declarationless definitions
Optionless definitions
Freeform definitions
Freeform configuration
Freeform modules
The last one sounds pretty good imo
Freeform modules
The last one sounds pretty good imo
:100:
I'll wait until https://github.com/NixOS/nixpkgs/pull/75584 is merged so I can extend the "Options for Program Settings" section with this feature.
Now updated to term this feature freeform modules instead and revised the documentation to be less RFC-y. Also fixed a bug with freeform modules. Once the documentation is reviewed, I think this PR is ready for merging.
New section under "Writing modules":
New section under the settings option docs (introduced in #75584):
@roberth Thanks for all the suggestions, I implemented them now. After some thought, I think there's no reason not to introduce some syntactic sugar for freeformType, so I did that now. Was fairly easy to add even.
The freeform type doesn't seem to be visible in the generated option docs. Could we generate a line for an "option" like "${somePrefix}.*" there?
I think we've discussed this in an earlier pr, but I couldn't find it.
We may want to use a freeform "option" rather than a freeform type for this reason, because that provides an opportunity to provide the description string and an example.
@roberth With https://github.com/NixOS/nixpkgs/pull/82743/commits/2d45a62899d47c109a0b8ce4ca9d33265b8a1a37 the freeform type is shown as the submodules type. E.g. with a config like
{ lib, ... }: {
options.fofofofo = lib.mkOption {
type = lib.types.submodule {
freeformType = lib.types.attrsOf lib.types.str;
options.babababa = lib.mkOption {};
};
};
config = {
documentation.nixos.includeAllModules = true;
fileSystems."/".device = "ntest";
boot.loader.grub.device = "nodev";
};
}
Building with nix-build '<nixpkgs/nixos>' --arg configuration ./config.nix -A config.system.build.manual.manualHTML gives
Awesome! Thanks for all the reviewing and merging @roberth!
This broke nix-darwin, bisected to https://github.com/NixOS/nixpkgs/commit/fd75dc876586bde8cdb683a6952a41132e8db166
$ darwin-rebuild build --dry-run
building the system configuration...
error: The option `nixpkgs.localSystem' defined in `<unknown-file>' does not exist.
(use '--show-trace' to show detailed location information)
full trace
$ darwin-rebuild build --dry-run --show-trace
building the system configuration...
error: while evaluating the attribute 'activationScript' of the derivation 'darwin-system-20.09.git.78922ca+darwin3.47fe6db' at /Users/marsam/code/nix-config/darwin/modules/system/default.nix:74:7:
while evaluating the attribute 'activationScripts.script.text' at undefined position:
while evaluating 'g' at /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:276:19, called from undefined position:
while evaluating anonymous function at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:98:72, called from /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:279:20:
while evaluating the attribute 'value' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:450:9:
while evaluating the option `system.activationScripts.script.text':
while evaluating the attribute 'mergedValue' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:482:5:
while evaluating the attribute 'values' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:476:9:
while evaluating the attribute 'values' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:575:7:
while evaluating anonymous function at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:462:28, called from /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:462:17:
while evaluating definitions from `/Users/marsam/code/nix-config/darwin/modules/system/activation-scripts.nix':
while evaluating 'dischargeProperties' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:534:25, called from /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:463:137:
while evaluating the attribute 'value' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:327:44:
while evaluating the attribute 'activationScripts.applications.text' at undefined position:
while evaluating 'g' at /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:276:19, called from undefined position:
while evaluating anonymous function at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:98:72, called from /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:279:20:
while evaluating the attribute 'value' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:450:9:
while evaluating the option `system.activationScripts.applications.text':
while evaluating the attribute 'mergedValue' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:482:5:
while evaluating the attribute 'values' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:476:9:
while evaluating the attribute 'values' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:575:7:
while evaluating anonymous function at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:462:28, called from /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:462:17:
while evaluating definitions from `/Users/marsam/code/nix-config/darwin/modules/system/applications.nix':
while evaluating 'dischargeProperties' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:534:25, called from /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:463:137:
while evaluating the attribute 'value' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:327:44:
while evaluating the attribute 'passAsFile' of the derivation 'system-applications' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'darwin-manpages' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'manual-olinkdb' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'darwin-manual-combined' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'generated-docbook' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'options-db.xml' at /Users/marsam/code/nix-config/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating 'flip' at /Users/marsam/code/nix-config/nixpkgs/lib/trivial.nix:138:16, called from /Users/marsam/code/nix-config/darwin/doc/manual/default.nix:48:21:
while evaluating 'optionAttrSetToDocList'' at /Users/marsam/code/nix-config/nixpkgs/lib/options.nix:140:37, called from /Users/marsam/code/nix-config/darwin/doc/manual/default.nix:9:72:
while evaluating 'collect' at /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:178:19, called from /Users/marsam/code/nix-config/nixpkgs/lib/options.nix:162:67:
while evaluating 'isType' at /Users/marsam/code/nix-config/nixpkgs/lib/types.nix:14:18, called from /Users/marsam/code/nix-config/nixpkgs/lib/attrsets.nix:179:8:
while evaluating 'evalModules' at /Users/marsam/code/nix-config/nixpkgs/lib/modules.nix:21:17, called from /Users/marsam/code/nix-config/darwin/modules/documentation/default.nix:19:24:
The option `nixpkgs.localSystem' defined in `<unknown-file>' does not exist.
The only place nix-darwin uses nixpkgs.localSystem is in the manual https://github.com/LnL7/nix-darwin/blob/47fe6db9c9cd22c4ba57df3281f98f454880bea7/modules/documentation/default.nix#L20.
I'm not familiar with modules internals, so I'm appreciate any hint to for a proper fix
cc: @LnL7
@marsam I can't find a declaration for localSystem in nix-darwin, so the error message seems to be correct. Grepping only reveals the usage site you linked but no declaration.
The file analogous to Nixpkgs where I would expect it to be defined is https://github.com/LnL7/nix-darwin/blob/master/modules/nix/nixpkgs.nix
I don't think nix-darwin needs that option, so I've created a PR for the simple solution https://github.com/LnL7/nix-darwin/pull/216
NixOS-specific rant:
If a module needs access to cross-compilation info, it should generally be taken from pkgs directly; either pkgs.stdenv.hostPlatform, which is the what the eventual machine runs or if you really do need to care about where the config is built: pkgs.stdenv.buildPlatform. Generally you care about pkgs.stdenv.hostPlatform which can not be assumed to be equivalent to config.nixpkgs.localSystem because of config.nixpkgs.crossSystem. local and cross only make sense in the context of nixos-rebuild --target-host, which uses incompatible terminology...
TL;DR: I assume we'll revert this merge until the issues get resolved?
This merge also broke Hydra's evaluation of trunk-combined. It's some kind of interaction with other conditions and I haven't managed to reproduce it locally so far though @samueldr did (maybe this just triggered some Nix bug)... but the merge commit of this PR (6d0a85fe52) won't evaluate on Hydra whereas the parent commit succeeded.
The message is
error: [json.exception.type_error.302] type must be string, but is null
and it seems likely that it comes from evaluating nixos/release-combined.nix -A nixos.manual.x86_64-linux. Some context was on IRC yesterday.
@roberth Nice detective work! Both the nix-darwin and the hydra failures seem to originate from https://github.com/NixOS/nixpkgs/commit/fd75dc876586bde8cdb683a6952a41132e8db166, which apparently checks options stricter, but I'm not quite sure yet why (I'll investigate this a bit more)
Fyi, the hydra failure originates from this command now failing:
$ nix-instantiate nixos/tests/boot.nix -A biosCdrom
error: The option `virtualisation.qemu.consoles' defined in `/home/infinisil/src/nixpkgs/nixos/modules/testing/test-instrumentation.nix' does not exist.
Which is indeed fixed by @roberth's PR. Similar for nix-darwin.
TL;DR: I assume we'll revert this merge until the issues get resolved?
Shouldn't be necessary.
This change is merely exposing undeclared options that weren't discovered by the previous implementation.
I've merged a fix for the one that was blocking release-small. trunk-combined should also be fixed now, because it doesn't seem to suffer from other errors of the same time. We'll see when evaluation is done.
(I'm wondering, shouldn't TL;DR be a summary?)
Ah figured it out: The previous implementation only checked option existence for config paths that are evaluated, while the new one checks all of them unconditionally. Here's an example that illustrates this:
(import <nixpkgs/lib>).evalModules {
modules = [({ lib, ... }: {
options.root = lib.mkOption {};
options.foo.bar = lib.mkOption {};
config.root = "root";
config.foo.qux = "qux";
})];
}
Evaluating with nix-instantiate --eval -A config.root previously worked because config.foo wasn't evaluated, so it would still fail with nix-instantiate --eval -A config.foo. With the new implementation, both commands fail. I think this change in behavior is justified, because there can be other reasons an option doesn't exist other than the config path not being evaluated (e.g. misspellings). In fact I think this change might even fix https://github.com/NixOS/nixpkgs/issues/36590.
It looks like previously this was (ab)used to make evaluation not fail: https://github.com/NixOS/nixpkgs/blob/aeffd67cec5b76e327f244c7464a4254113836cc/nixos/modules/testing/test-instrumentation.nix#L11-L18
Thanks, that was really fast.
(I'm wondering, shouldn't TL;DR be a summary?)
I did consider that as something like summary/conclusion, explaining the details below, though I agree I typically see it used in a bit different way.
@Infinisil I think @LnL7 has a good point here https://github.com/LnL7/nix-darwin/pull/216#issuecomment-674966068 that this is an api change. Even if the old api is undocumented and untested, it may have an important role in modular code bases. Do you think it's feasible to warn about the old behavior or to emulate it?
If only warning about it is feasible, we can recommend to extract the option into a separate file, which may be a good idea.
I don't think trying to emulate the old behavior is a good idea, because from what we've seen already, that behavior was very prone to mistakes (https://github.com/NixOS/nixpkgs/issues/36590 and https://github.com/LnL7/nix-darwin/pull/216). While https://github.com/NixOS/nixpkgs/pull/95584 wasn't a mistake per se, it still relied on a hack to make it work.
I think it would be a good idea to mention this change in behavior though, probably in the breaking changes section in the release notes.
There doesn't seem to be any way to define typing for an optional setting, I was looking to set default = unset in some way, since some configuration handle null and "not set" differently.
@dali99 Indeed, that's something that could be improved in the future. See also https://github.com/NixOS/nixpkgs/pull/63553 which is related.
| gharchive/pull-request | 2020-03-16T19:03:41 | 2025-04-01T06:37:19.382705 | {
"authors": [
"Infinisil",
"dali99",
"marsam",
"pasqui23",
"roberth",
"vcunat"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/82743",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
589420525 | Revert "luaPackages.luv: 1.30.0-0 -> 1.34.1-1"
This reverts commit eaa47284113cda19a037b7fcbaa892ddb596b813.
With 81461cff5f540c92e5030f62b89ee7b64e85c6df luv also needs to be
downgraded until luarocks can be updated to 3.3.1 again.
Fixes #82727
Motivation for this change
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[x] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
On the luv issue, as we have no proper fix really (the current fix is just as complicated as the current one), I am fine with this. I have not understood yet if the issue on darwin was random or systematic (i.e., if it could be fixed by trying several times).
For reference the darwin build worked fine with luarocks-3.3.1 + luv-1.34.1-1 (even without your changes). So once #80528 is resolved we just have to make sure to update both.
| gharchive/pull-request | 2020-03-27T21:24:13 | 2025-04-01T06:37:19.390840 | {
"authors": [
"LnL7",
"teto"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/83532",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
636638482 | pyspinel: fix python3 build
Motivation for this change
Update to reference an upstream fix to build on python >=3.3
Things done
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[ ] NixOS
[x] macOS
[x] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
sorry for all the round about trips.
To comply with CONTRIBUTING.md please have the commit message name be of the format
<pkg-name>: <subject-line>
for more examples, please look at https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#submitting-changes
in your case, the commit message should be:
python3Packages.pyspinel: fix build
| gharchive/pull-request | 2020-06-11T00:46:40 | 2025-04-01T06:37:19.397102 | {
"authors": [
"jonringer",
"siriobalmelli"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/90108",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
649156631 | nixos/networkd: update options
Motivation for this change
To fix missing option DNSDefaultRoute= (see #91761) and other missing options.
Things done
I have not tested all options that I touched.
[ ] Tested using NixOps
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[ ] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.
I will update the PR following this comment.
This needs another rebase.
This needs another rebase.
Done
This is the second time I rebased my PR on master after more recent PRs than mine were merged. What guides the order in which PRs are merged?
Thanks!
This is the second time I rebased my PR on master after more recent PRs than mine were merged. What guides the order in which PRs are merged?
There's no specific order, but this PR is quite big, which is why it's harder to review.
Networking-Tests are looking good.
/nix/store/4y8k9isgglvhycvq59kg50hx62rw08kn-vm-test-run-Bond-Networking-Networkd
/nix/store/0kmcb3mwlm63hjkbd50h075d61ncqf0i-vm-test-run-Bridge-Networking-Networkd
/nix/store/dcz18v4qz82sx9ynr3wyqimzrmaigpgg-vm-test-run-OneInterfaceDHCP-Networking-Networkd
/nix/store/1g9p0kgpd8nzbv6kqkkcq08nh8hmvmxi-vm-test-run-SimpleDHCP-Networking-Networkd
/nix/store/3014l21l3qrg01s3x33ys08fgjqrs9lw-vm-test-run-Link-Networking-Networkd
/nix/store/jllmqcvalzn1imsb6x0r57dfcdw2v7cz-vm-test-run-Loopback-Networking-Networkd
/nix/store/431izfl3mb82crr6kaw143ky0r04c9yl-vm-test-run-MACVLAN-Networking-Networkd
/nix/store/p7vj2zfcl228a9p5ri27ycrdm1yix6v9-vm-test-run-Privacy-Networking-Networkd
/nix/store/fs1rk6x92h83gfm1f8pm4ps8158g17ph-vm-test-run-routes-Networking-Networkd
/nix/store/wvh4cha8ssx3ypplwqp75wf1phiy46yx-vm-test-run-Sit-Networking-Networkd
/nix/store/blbh606jdzsbgdadbavj8nl0ic00c4d0-vm-test-run-Static-Networking-Networkd
/nix/store/mgv2b09h658glqn8lgz2s3akxdwzf7d7-vm-test-run-Virtual-Networking-Networkd
/nix/store/8kfj6r2kh6ab2w5g6ix304fr21zlw2vz-vm-test-run-vlan-Networking-Networkd
I tried reviewing this, but it's really hard to do.
e9d13d3 added some commented-out checks due to Nix' <= 2.2 integer size, and 70407f0 commented them back in. Could this be squashed together, so we only add the checks in a single commit?
As much as I could try, each of these 2 commits do one logical thing and one thing only, as described by the commit messages
e9d13d3: update options for systemd 245. That commit synchronizes the code with the man page of networkd and, for homogeneity with the rest of the code, keeps avoiding the use of assertRange with 64bits integers.
70407f0: use assertRange with 64bits integers. This commit takes into account this comment. Perhaps it would better fit as a separate PR after this one would have been merged. Since the PR is about cleaning up the networkd module, I included this commit here.
I apologize if my commit messages were not clear enough.
Also, e9d13d3 does a bit too much at once. For example, it removes OriginalName. Is this intended?
Again, that commit synchronizes the code with the man page of networkd. The best way to review that I would suggest is to read the man page. For the specifics of OriginalName, refer to man systemd.link. I also try to double check by contacting the author here, without success. However, you kind of confirmed it yourself here. To facilitate our work, let's discuss specific code issues/questions with the review feature of Github.
Could you revise the commits, and make it these changes easier to review? Maybe something like this also deserves a separate commit.
I do not think it is beneficial because the commit does one clear logical thing. If you disagree, please describe what you mean by "these changes" because, as you may have noted, this is not the only thing I removed in this commit e9d13d3.
Thanks again for your patience! I'll try to react quicker on further updates.
Thank you as well for reviewing this.
Could we move on with this PR?
I gave this another close look, and while it is pretty hard to review due to the amount of changes, this seems to be fine, and should make things more readable and understandable in the longer run.
Thanks for the work you put in this, and your patience with me :-)
| gharchive/pull-request | 2020-07-01T17:38:42 | 2025-04-01T06:37:19.412288 | {
"authors": [
"datafoo",
"flokli",
"mweinelt"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/91960",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
103405721 | jack2: update from b5bceb to 460063
An especially important commit that this includes is https://github.com/jackaudio/jack2/commit/05216197b491d64036733a2d3be511456c1f65cd which changes the API to match jack1 and the official JACK specification.
I tested this. Travis failure is due to a network failure.
@andrewrk this does look like a nice improvement, but personally I'd rather wait for the next release. Does it fix any particular issue for you at the moment?
@wkennington why did you upgrade jack2 to 460063d8d from the v1.9.10 release (you didn't provide any reason in your commit message)? Do we need to have a separate unstable version of jack2 in addition to the stable release, or do we really need to use git master as the default?
@andrewrk this does look like a nice improvement, but personally I'd rather wait for the next release. Does it fix any particular issue for you at the moment?
Yes. This commit modifies the project I am working on to be compliant against jack1 and the official JACK specification. However it causes my project to fail to build from source when compiling against jack2Full. This nixpkgs update allows me to compile my project against jack1, jack2, and be compliant with the spec, at the same time.
Furthermore, the previous version of the package was not an official JACK release so I see no reason to prefer one arbitrary SHA1 over another.
@andrewrk ah, so if we added an expression for jack2-git, that would be OK for your development work (or if you override it locally). I'd be happy with that, but I'm also curious to hear why we're not using the release at the moment.
ah, so if we added an expression for jack2-git, that would be OK for your development work (or if you override it locally)
It's not so bad working from my nixpkgs fork for now. But I'm also collaborating with people from other distros whose package managers have updated to include this fix. For example, debian: https://packages.debian.org/source/sid/jackd2
@goibhniu I usually only use git snapshots if the build is fubar for one of
the releases or there is no release at all. I don't remember now what the
issue was but there was something wrong with the stable version at the time.
On Thu, Aug 27, 2015, 01:11 Andrew Kelley notifications@github.com wrote:
ah, so if we added an expression for jack2-git, that would be OK for your
development work (or if you override it locally)
It's not so bad working from my nixpkgs fork for now. But I'm also
collaborating with people from other distros whose package managers have
updated to include this fix. For example, debian:
https://packages.debian.org/source/sid/jackd2
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9467#issuecomment-135335582.
@wkennington thanks. If nobody objects, I'd like to try to get the released version working again and use that as the default and then we could also add jack2-git for @andrewrk and others, since jack2 stable releases seem to only happen every year or two. I'll add a separate ticket for it but if you want to have something sooner @andrewrk, I'd be happy to merge a PR with a separate expression for jack2-git.
| gharchive/pull-request | 2015-08-27T02:02:26 | 2025-04-01T06:37:19.421741 | {
"authors": [
"andrewrk",
"cillianderoiste",
"wkennington"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/9467",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
707505654 | [20.09] orangefs: 2.9.7 -> 2.9.8, fix build
Motivation for this change
backport #98525
ZHF: #97479
(cherry picked from commit aa25c6576611ebab7d7448fa30edad9eb1c1a066)
Things done
[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)
[x] NixOS
[ ] macOS
[ ] other Linux distributions
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
@GrahamcOfBorg test orangefs
tests passed
| gharchive/pull-request | 2020-09-23T16:20:32 | 2025-04-01T06:37:19.428600 | {
"authors": [
"jonringer"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/98573",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
107403578 | gitit: Remove staticDir and templatesDir
as these cannot be overridden if specified here.
My attempt to fix #9863. I don't know whether this is a step in the right direction or not.
Ping to all haskellers I can find, because I have no clue who is responsible for the service file
CC: @gebner @gridaphobe @jb55 @khumba @psibi @ttuegel
(Disclaimer, I don't know about gitit.) I see that there are config
options defined for those, and that the options are used in the
generated config file and the systemd service, but strangely, they're
hard-coded. It conflicts if you try to set it without your patch,
right? If so, looks fine to me, but I'd recommend setting default
attributes for staticDir and templatesDir to what they were
previously fixed to.
@khumba Good idea!
As the author of the module I would like to have these options available, which I'm using in a private module. For nixpkgs, it was commit https://github.com/NixOS/nixpkgs/commit/99750d89dd962cc7011b02e487ed1a38c7842524 that essentially made them useless.
@khumba that would require evaluation of the haskellPackages set.
I would recommend setting them null by default and changing the type to nullOr. Also checking for null in the config inclusion.
@edwtjo Sorry I do not understand your comment. Shall I set these options to null by default?
What's funny: As far as I can see, the path for the static and template dir is hard coded to the store itself in the service definition. And there is no way to override a service, is there? So this package is rather useless as-is.
@matthiasbeyer yes that is what I meant, but also modify configFile. Anyway these alterations will just be ugly hacks, let's avoid those on second thought.
And there is no way to override a service, is there? So this package is rather useless as-is.
I'm not exactly sure what you mean but no 99750d89dd962cc7011b02e487ed1a38c7842524 was not a very good idea. So since @edolstra don't want the computational and storage overhead with the module; The only correct way to move forward is to remove gitit.nix from the module list, reverting 99750d89dd962cc7011b02e487ed1a38c7842524 and instead requiring it to be manually added into your configuration.nix. Which was done in 122d5e497e6df55f4b2e5c353bb2224b79cfd7b0 and aeba3eabcdbfa6308d9af27b2a70e7864ec4d3e3
| gharchive/pull-request | 2015-09-20T16:39:51 | 2025-04-01T06:37:19.435045 | {
"authors": [
"edwtjo",
"khumba",
"matthiasbeyer"
],
"repo": "NixOS/nixpkgs",
"url": "https://github.com/NixOS/nixpkgs/pull/9962",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1968858983 | 🛑 GotHub gothub.frontendfriendly.xyz is down
In 66b3a3c, GotHub gothub.frontendfriendly.xyz (https://gothub.frontendfriendly.xyz) was down:
HTTP code: 0
Response time: 0 ms
Resolved: GotHub gothub.frontendfriendly.xyz is back up in 0cb0ddf after 10 minutes.
| gharchive/issue | 2023-10-30T17:17:16 | 2025-04-01T06:37:19.460359 | {
"authors": [
"Mine1984Craft"
],
"repo": "NoPlagiarism/services-personal-upptime",
"url": "https://github.com/NoPlagiarism/services-personal-upptime/issues/2780",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2080668940 | 🛑 AnonymousOverflow overflow.lunar.icu is down
In 3f86182, AnonymousOverflow overflow.lunar.icu (https://overflow.lunar.icu) was down:
HTTP code: 0
Response time: 0 ms
Resolved: AnonymousOverflow overflow.lunar.icu is back up in 39c7a71 after 10 minutes.
| gharchive/issue | 2024-01-14T10:22:43 | 2025-04-01T06:37:19.462866 | {
"authors": [
"Mine1984Craft"
],
"repo": "NoPlagiarism/services-personal-upptime",
"url": "https://github.com/NoPlagiarism/services-personal-upptime/issues/5619",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1891562094 | 🛑 rimgo rimgo.lunar.icu is down
In 595caf0, rimgo rimgo.lunar.icu (https://rimgo.lunar.icu) was down:
HTTP code: 0
Response time: 0 ms
Resolved: rimgo rimgo.lunar.icu is back up in 3765936 after 7 minutes.
| gharchive/issue | 2023-09-12T02:31:34 | 2025-04-01T06:37:19.465357 | {
"authors": [
"Mine1984Craft"
],
"repo": "NoPlagiarism/services-personal-upptime",
"url": "https://github.com/NoPlagiarism/services-personal-upptime/issues/967",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
595797653 | Add Knockback component(s)
Similar to DealsDamage and TakesDamage.
Knockback and KnockbackAffected.
For now, we just configure the entity configs to have knockback behavior.
Knockback components may be nice for a knockback state in the future, but has low priority for now.
Could also help with #41
| gharchive/issue | 2020-04-07T11:28:55 | 2025-04-01T06:37:19.468669 | {
"authors": [
"Noah2610"
],
"repo": "Noah2610/deathfloor",
"url": "https://github.com/Noah2610/deathfloor/issues/32",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
617089807 | Merge pull request #1 from NobyDa/master
修正误杀
merge NobyDa
pr拉反了小兄弟
pr拉反了小兄
发现了, 有点难受
| gharchive/pull-request | 2020-05-13T02:23:51 | 2025-04-01T06:37:19.470168 | {
"authors": [
"NobyDa",
"ZhipengRen"
],
"repo": "NobyDa/ND-AD",
"url": "https://github.com/NobyDa/ND-AD/pull/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
171017515 | Issue running npm install on Mac
Hi!
I tried an npm install
Here are my gross logs:
NodeOS git:(master) ✗ npm install
npm WARN prefer global node-ninja@1.0.2 should be installed with -g
npm WARN prefer global node-gyp@3.4.0 should be installed with -g
> kexec@2.0.2 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/kexec
> node-gyp rebuild
CXX(target) Release/obj.target/kexec/src/kexec.o
SOLINK_MODULE(target) Release/kexec.node
> nodeos-mount@0.2.0 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-mount
> node-gyp rebuild
CXX(target) Release/obj.target/mount/mount.o
../mount.cc:30:15: error: no matching function for call to 'mount'
int ret = mount(mounty->devFile.c_str(),
^~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/sys/mount.h:395:5: note: candidate function not viable: requires 4 arguments, but 5 were provided
int mount(const char *, const char *, int, void *);
^
../mount.cc:49:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "mount", "", mounty->devFile.c_str());
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:66:15: error: use of undeclared identifier 'umount'
int ret = umount(mounty->target.c_str());
^
../mount.cc:80:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "umount", "", mounty->target.c_str());
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:159:13: error: no matching function for call to 'mount'
int ret = mount(s_devFile.c_str(),
^~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/sys/mount.h:395:5: note: candidate function not viable: requires 4 arguments, but 5 were provided
int mount(const char *, const char *, int, void *);
^
../mount.cc:166:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "mount", "", s_devFile.c_str()));
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:184:13: error: use of undeclared identifier 'umount'; did you mean 'Umount'?
int ret = umount(s_target.c_str());
^~~~~~
Umount
../mount.cc:121:12: note: 'Umount' declared here
NAN_METHOD(Umount) {
^
../mount.cc:184:20: error: reference to type 'const FunctionCallbackInfo<v8::Value>' could not bind to an rvalue of type 'const char *'
int ret = umount(s_target.c_str());
^~~~~~~~~~~~~~~~
../mount.cc:121:1: note: passing argument to parameter 'info' here
NAN_METHOD(Umount) {
^
../../nan/nan.h:1298:64: note: expanded from macro 'NAN_METHOD'
Nan::NAN_METHOD_RETURN_TYPE name(Nan::NAN_METHOD_ARGS_TYPE info)
^
../mount.cc:186:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "umount", "", s_target.c_str()));
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
4 warnings and 5 errors generated.
make: *** [Release/obj.target/mount/mount.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:100:13)
gyp ERR! stack at ChildProcess.emit (events.js:185:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Darwin 16.0.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-mount
gyp ERR! node -v v5.8.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
NodeOS@1.0.0-RC2 /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS
├─┬ nodeos-barebones@1.0.0-RC2.3
│ ├─┬ cpio2tar@0.0.1
│ │ └── cpio-stream@1.3.0
│ ├─┬ download-manager@0.0.20
│ │ ├── diff@2.2.3
│ │ ├─┬ download@4.4.1 (git://github.com/nodeos/download.git#e405ae2b6bce31dd8220d0154bbe9964d5a66fb3)
│ │ │ ├─┬ caw@1.2.0
│ │ │ │ ├── get-proxy@1.1.0
│ │ │ │ ├── is-obj@1.0.1
│ │ │ │ ├── object-assign@3.0.0
│ │ │ │ └── tunnel-agent@0.4.3
│ │ │ ├─┬ each-async@1.1.1
│ │ │ │ └── set-immediate-shim@1.0.1
│ │ │ ├─┬ filenamify@1.2.1
│ │ │ │ ├── filename-reserved-regex@1.0.0
│ │ │ │ ├── strip-outer@1.0.0
│ │ │ │ └── trim-repeated@1.0.0
│ │ │ ├─┬ gulp-decompress@1.2.0
│ │ │ │ ├─┬ archive-type@3.2.0
│ │ │ │ │ └── file-type@3.8.0
│ │ │ │ ├─┬ decompress@3.0.0
│ │ │ │ │ ├─┬ buffer-to-vinyl@1.1.0
│ │ │ │ │ │ └── uuid@2.0.2
│ │ │ │ │ ├─┬ decompress-tar@3.1.0
│ │ │ │ │ │ ├── is-tar@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-tarbz2@3.1.0
│ │ │ │ │ │ ├── is-bzip2@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ ├─┬ seek-bzip@1.0.5
│ │ │ │ │ │ │ └─┬ commander@2.8.1
│ │ │ │ │ │ │ └── graceful-readlink@1.0.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-targz@3.1.0
│ │ │ │ │ │ ├── is-gzip@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-unzip@3.4.0
│ │ │ │ │ │ ├── is-zip@1.0.0
│ │ │ │ │ │ ├── stat-mode@0.2.1
│ │ │ │ │ │ ├── through2@2.0.1
│ │ │ │ │ │ └─┬ yauzl@2.6.0
│ │ │ │ │ │ ├── buffer-crc32@0.2.5
│ │ │ │ │ │ └─┬ fd-slicer@1.0.1
│ │ │ │ │ │ └── pend@1.2.0
│ │ │ │ │ └── vinyl-assign@1.2.1
│ │ │ │ └─┬ gulp-util@3.0.7
│ │ │ │ ├── array-differ@1.0.0
│ │ │ │ ├── beeper@1.1.0
│ │ │ │ ├── dateformat@1.0.12
│ │ │ │ ├─┬ fancy-log@1.2.0
│ │ │ │ │ └── time-stamp@1.0.1
│ │ │ │ ├─┬ gulplog@1.0.0
│ │ │ │ │ └── glogg@1.0.0
│ │ │ │ ├─┬ has-gulplog@0.1.0
│ │ │ │ │ └── sparkles@1.0.0
│ │ │ │ ├── lodash._reescape@3.0.0
│ │ │ │ ├── lodash._reevaluate@3.0.0
│ │ │ │ ├── lodash._reinterpolate@3.0.0
│ │ │ │ ├─┬ lodash.template@3.6.2
│ │ │ │ │ ├── lodash._basecopy@3.0.1
│ │ │ │ │ ├── lodash._basetostring@3.0.1
│ │ │ │ │ ├── lodash._basevalues@3.0.0
│ │ │ │ │ ├── lodash._isiterateecall@3.0.9
│ │ │ │ │ ├─┬ lodash.escape@3.2.0
│ │ │ │ │ │ └── lodash._root@3.0.1
│ │ │ │ │ ├─┬ lodash.keys@3.1.2
│ │ │ │ │ │ ├── lodash._getnative@3.9.1
│ │ │ │ │ │ ├── lodash.isarguments@3.0.9
│ │ │ │ │ │ └── lodash.isarray@3.0.4
│ │ │ │ │ ├── lodash.restparam@3.6.1
│ │ │ │ │ └── lodash.templatesettings@3.1.1
│ │ │ │ ├── minimist@1.2.0
│ │ │ │ ├─┬ multipipe@0.1.2
│ │ │ │ │ └─┬ duplexer2@0.0.2
│ │ │ │ │ └─┬ readable-stream@1.1.14
│ │ │ │ │ └── isarray@0.0.1
│ │ │ │ ├── object-assign@3.0.0
│ │ │ │ ├── through2@2.0.1
│ │ │ │ └── vinyl@0.5.3
│ │ │ ├── gulp-rename@1.2.2
│ │ │ ├── is-url@1.2.2
│ │ │ ├── read-all-stream@3.1.0
│ │ │ ├── stream-combiner2@1.1.1
│ │ │ ├─┬ vinyl@1.2.0
│ │ │ │ ├── clone@1.0.2
│ │ │ │ ├── clone-stats@0.0.1
│ │ │ │ └── replace-ext@0.0.1
│ │ │ ├─┬ vinyl-fs@2.2.1 (git://github.com/nodeos/vinyl-fs.git#7cee24e7d53e20aca890b818f92268a2984fc793)
│ │ │ │ ├─┬ duplexify@3.4.5
│ │ │ │ │ ├── end-of-stream@1.0.0
│ │ │ │ │ └── stream-shift@1.0.0
│ │ │ │ ├─┬ glob-stream@5.3.2
│ │ │ │ │ ├── extend@3.0.0
│ │ │ │ │ ├── glob@5.0.15
│ │ │ │ │ ├─┬ glob-parent@2.0.0
│ │ │ │ │ │ └── is-glob@2.0.1
│ │ │ │ │ ├─┬ micromatch@2.3.11
│ │ │ │ │ │ ├─┬ arr-diff@2.0.0
│ │ │ │ │ │ │ └── arr-flatten@1.0.1
│ │ │ │ │ │ ├── array-unique@0.2.1
│ │ │ │ │ │ ├─┬ braces@1.8.5
│ │ │ │ │ │ │ ├─┬ expand-range@1.8.2
│ │ │ │ │ │ │ │ └─┬ fill-range@2.2.3
│ │ │ │ │ │ │ │ ├── is-number@2.1.0
│ │ │ │ │ │ │ │ ├── isobject@2.1.0
│ │ │ │ │ │ │ │ ├── randomatic@1.1.5
│ │ │ │ │ │ │ │ └── repeat-string@1.5.4
│ │ │ │ │ │ │ ├── preserve@0.2.0
│ │ │ │ │ │ │ └── repeat-element@1.1.2
│ │ │ │ │ │ ├─┬ expand-brackets@0.1.5
│ │ │ │ │ │ │ └── is-posix-bracket@0.1.1
│ │ │ │ │ │ ├── extglob@0.3.2
│ │ │ │ │ │ ├── filename-regex@2.0.0
│ │ │ │ │ │ ├── is-extglob@1.0.0
│ │ │ │ │ │ ├─┬ kind-of@3.0.4
│ │ │ │ │ │ │ └── is-buffer@1.1.4
│ │ │ │ │ │ ├── normalize-path@2.0.1
│ │ │ │ │ │ ├─┬ object.omit@2.0.0
│ │ │ │ │ │ │ ├─┬ for-own@0.1.4
│ │ │ │ │ │ │ │ └── for-in@0.1.5
│ │ │ │ │ │ │ └── is-extendable@0.1.1
│ │ │ │ │ │ ├─┬ parse-glob@3.0.4
│ │ │ │ │ │ │ ├── glob-base@0.3.0
│ │ │ │ │ │ │ └── is-dotfile@1.0.2
│ │ │ │ │ │ └─┬ regex-cache@0.4.3
│ │ │ │ │ │ ├── is-equal-shallow@0.1.3
│ │ │ │ │ │ └── is-primitive@2.0.0
│ │ │ │ │ ├── ordered-read-streams@0.3.0
│ │ │ │ │ ├─┬ through2@0.6.5
│ │ │ │ │ │ └─┬ readable-stream@1.0.34
│ │ │ │ │ │ └── isarray@0.0.1
│ │ │ │ │ ├─┬ to-absolute-glob@0.1.1
│ │ │ │ │ │ └── extend-shallow@2.0.1
│ │ │ │ │ └── unique-stream@2.2.1
│ │ │ │ ├─┬ gulp-sourcemaps@1.6.0
│ │ │ │ │ ├── convert-source-map@1.3.0
│ │ │ │ │ ├── strip-bom@2.0.0
│ │ │ │ │ └── through2@2.0.1
│ │ │ │ ├── is-valid-glob@0.3.0
│ │ │ │ ├── merge-stream@1.0.0
│ │ │ │ ├─┬ strip-bom@2.0.0
│ │ │ │ │ └── is-utf8@0.2.1
│ │ │ │ ├─┬ strip-bom-stream@1.0.0
│ │ │ │ │ ├── first-chunk-stream@1.0.0
│ │ │ │ │ └── strip-bom@2.0.0
│ │ │ │ ├── through2@2.0.1
│ │ │ │ └─┬ through2-filter@2.0.0
│ │ │ │ └── through2@2.0.1
│ │ │ └─┬ ware@1.3.0
│ │ │ └─┬ wrap-fn@0.1.5
│ │ │ └── co@3.1.0
│ │ ├─┬ download-checksum@0.1.3
│ │ │ └─┬ openpgp@1.6.2
│ │ │ ├── es6-promise@1.0.0
│ │ │ ├─┬ node-fetch@1.6.0
│ │ │ │ └─┬ encoding@0.1.12
│ │ │ │ └── iconv-lite@0.4.13
│ │ │ ├── node-localstorage@1.1.2
│ │ │ └── zlibjs@0.2.0
│ │ ├─┬ download-status@2.2.1
│ │ │ ├─┬ chalk@0.5.1
│ │ │ │ ├── ansi-styles@1.1.0
│ │ │ │ ├─┬ has-ansi@0.1.0
│ │ │ │ │ └── ansi-regex@0.2.1
│ │ │ │ ├── strip-ansi@0.3.0
│ │ │ │ └── supports-color@0.2.0
│ │ │ ├─┬ lpad-align@1.1.0
│ │ │ │ ├── longest@1.0.1
│ │ │ │ ├── lpad@2.0.1
│ │ │ │ └─┬ meow@3.7.0
│ │ │ │ ├─┬ camelcase-keys@2.1.0
│ │ │ │ │ └── camelcase@2.1.1
│ │ │ │ ├── decamelize@1.2.0
│ │ │ │ ├─┬ loud-rejection@1.6.0
│ │ │ │ │ ├─┬ currently-unhandled@0.4.1
│ │ │ │ │ │ └── array-find-index@1.0.1
│ │ │ │ │ └── signal-exit@3.0.0
│ │ │ │ ├── map-obj@1.0.1
│ │ │ │ ├── minimist@1.2.0
│ │ │ │ ├─┬ normalize-package-data@2.3.5
│ │ │ │ │ ├── hosted-git-info@2.1.5
│ │ │ │ │ ├─┬ is-builtin-module@1.0.0
│ │ │ │ │ │ └── builtin-modules@1.1.1
│ │ │ │ │ └─┬ validate-npm-package-license@3.0.1
│ │ │ │ │ ├─┬ spdx-correct@1.0.2
│ │ │ │ │ │ └── spdx-license-ids@1.2.2
│ │ │ │ │ └─┬ spdx-expression-parse@1.0.2
│ │ │ │ │ └── spdx-exceptions@1.0.5
│ │ │ │ ├─┬ read-pkg-up@1.0.1
│ │ │ │ │ ├─┬ find-up@1.1.2
│ │ │ │ │ │ └── path-exists@2.1.0
│ │ │ │ │ └─┬ read-pkg@1.1.0
│ │ │ │ │ ├─┬ load-json-file@1.1.0
│ │ │ │ │ │ └── strip-bom@2.0.0
│ │ │ │ │ └── path-type@1.1.0
│ │ │ │ ├─┬ redent@1.0.0
│ │ │ │ │ ├─┬ indent-string@2.1.0
│ │ │ │ │ │ └─┬ repeating@2.0.1
│ │ │ │ │ │ └── is-finite@1.0.1
│ │ │ │ │ └── strip-indent@1.0.1
│ │ │ │ └── trim-newlines@1.0.0
│ │ │ └── object-assign@2.1.1
│ │ ├─┬ got@5.6.0
│ │ │ ├─┬ create-error-class@3.0.2
│ │ │ │ └── capture-stack-trace@1.0.0
│ │ │ ├── duplexer2@0.1.4
│ │ │ ├── is-plain-obj@1.1.0
│ │ │ ├── is-redirect@1.0.0
│ │ │ ├── is-retry-allowed@1.1.0
│ │ │ ├── is-stream@1.1.0
│ │ │ ├── lowercase-keys@1.0.0
│ │ │ ├── node-status-codes@1.0.0
│ │ │ ├─┬ parse-json@2.2.0
│ │ │ │ └─┬ error-ex@1.3.0
│ │ │ │ └── is-arrayish@0.2.1
│ │ │ ├── timed-out@2.0.0
│ │ │ └─┬ url-parse-lax@1.0.0
│ │ │ └── prepend-http@1.0.4
│ │ └─┬ strip-dirs@1.1.1
│ │ ├── get-stdin@4.0.1
│ │ ├─┬ is-absolute@0.1.7
│ │ │ └── is-relative@0.1.3
│ │ ├── is-natural-number@2.1.1
│ │ ├── minimist@1.2.0
│ │ └── sum-up@1.0.3
│ ├── minimist@1.2.0
│ └── nodeos-nodejs@6.3.1 (git://github.com/nodeos/nodejs.git#4168865150b8dd08cf7f9f21805c0d67972872d7)
├─┬ nodeos-cross-toolchain@1.0.0-RC2.11
│ ├─┬ fs-extra@0.30.0
│ │ ├── jsonfile@2.3.1
│ │ └── klaw@1.3.0
│ └─┬ prebuild-install@1.0.2
│ ├── minimist@1.2.0
│ └── simple-get@2.2.2
├── UNMET DEPENDENCY nodeos-initramfs@1.0.0-RC2.4
├── nodeos-mount-filesystems@0.1.6 extraneous
├── UNMET PEER DEPENDENCY nodeos-mount-utils@^0.1.0
├─┬ nodeos-rootfs@1.0.0-RC2.1
│ └─┬ genfatfs@1.0.1 (git://github.com/nodeos/genfatfs.git#6a8dba0a4f101e97fba1d40815e9212473a0b084)
│ └─┬ prebuild-install@1.1.0
│ └── minimist@1.2.0
├─┬ nodeos-usersfs@1.0.0-RC2
│ ├── debugfs@0.0.2
│ ├── genext2fs@1.4.1-0 (git://github.com/nodeos/genext2fs.git#bc47c9232d9660fbda5eaad285ca5fa0d7f399c4)
│ └─┬ node-wget@0.4.2
│ └─┬ request@2.27.0
│ ├── aws-sign@0.3.0
│ ├── cookie-jar@0.3.0
│ ├── forever-agent@0.5.2
│ ├─┬ form-data@0.1.4
│ │ ├── async@0.9.2
│ │ └─┬ combined-stream@0.0.7
│ │ └── delayed-stream@0.0.5
│ ├─┬ hawk@1.0.0
│ │ ├── boom@0.4.2
│ │ ├── cryptiles@0.2.2
│ │ ├── hoek@0.9.1
│ │ └── sntp@0.2.4
│ ├─┬ http-signature@0.10.1
│ │ ├── asn1@0.1.11
│ │ ├── assert-plus@0.1.5
│ │ └── ctype@0.5.3
│ ├── json-stringify-safe@5.0.1
│ ├── mime@1.2.11
│ ├── node-uuid@1.4.7
│ ├── oauth-sign@0.3.0
│ ├── qs@0.6.6
│ └── tunnel-agent@0.3.0
├── posix@4.0.2 extraneous
├─┬ prebuild@4.2.2 (git://github.com/piranna/prebuild.git#beef82503dbb1296d7606e551546b6a2f26333c4)
│ ├── async@1.5.2
│ ├── expand-template@1.0.2
│ ├─┬ ghreleases@1.0.5
│ │ ├── after@0.8.1
│ │ ├── ghrepos@2.0.0
│ │ ├─┬ ghutils@3.2.0
│ │ │ └─┬ jsonist@1.2.0
│ │ │ ├── bl@1.0.3
│ │ │ └─┬ hyperquest@1.2.0
│ │ │ └─┬ duplexer2@0.0.2
│ │ │ └─┬ readable-stream@1.1.14
│ │ │ └── isarray@0.0.1
│ │ ├── simple-mime@0.1.0
│ │ └── url-template@2.0.8
│ ├── github-from-package@0.0.0
│ ├── minimist@1.2.0
│ ├─┬ node-gyp@3.4.0
│ │ ├── fstream@1.0.10
│ │ ├─┬ nopt@3.0.6
│ │ │ └── abbrev@1.0.9
│ │ ├─┬ osenv@0.1.3
│ │ │ └── os-tmpdir@1.0.1
│ │ ├─┬ path-array@1.0.1
│ │ │ └── array-index@1.0.0
│ │ ├─┬ tar@2.2.1
│ │ │ └── block-stream@0.0.9
│ │ └─┬ which@1.2.10
│ │ └── isexe@1.1.2
│ ├── node-ninja@1.0.2
│ ├── noop-logger@0.1.1
│ ├─┬ npmlog@2.0.4
│ │ ├── ansi@0.3.1
│ │ ├─┬ are-we-there-yet@1.1.2
│ │ │ └── delegates@1.0.0
│ │ └─┬ gauge@1.2.7
│ │ ├── has-unicode@2.0.1
│ │ ├── lodash.pad@4.5.0
│ │ ├── lodash.padend@4.6.0
│ │ └── lodash.padstart@4.6.0
│ ├─┬ pump@1.0.1
│ │ └── end-of-stream@1.1.0
│ ├─┬ rc@1.1.6
│ │ ├── deep-extend@0.4.1
│ │ ├── ini@1.3.4
│ │ └── minimist@1.2.0
│ ├── semver@5.3.0
│ ├─┬ simple-get@1.4.3
│ │ └── unzip-response@1.0.0
│ ├── tar-fs@1.13.0
│ └─┬ tar-stream@1.5.2
│ └── bl@1.1.2
├── qemu@2.6.0 (git://github.com/nodeos/qemu.git#d15f8861fdd1e0a4940753aef5a0a0825b136665)
├─┬ suppose@0.6.1
│ ├─┬ force-array@3.1.0
│ │ └── is-array@1.0.1
│ └── string@3.3.1
└── usrbinenv@0.0.3 extraneous
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.8.0
npm ERR! npm v3.9.2
npm ERR! code ELIFECYCLE
npm ERR! nodeos-mount@0.2.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nodeos-mount@0.2.0 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-mount package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-mount
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-mount
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/npm-debug.log
@luii was trying to port NodeOS to be build on OSX, but he only did it
partially on some internal modules. nodeos-mount should be one of them,
don't know why id failing... Until the adaption is finished, you'll need to
build it a Linux environment.
El 13/8/2016 19:02, "Tyler James Leonhardt" notifications@github.com
escribió:
Hi!
I tried an npm install
Here are my gross logs:
NodeOS git:(master) ✗ npm install
npm WARN prefer global node-ninja@1.0.2 should be installed with -g
npm WARN prefer global node-gyp@3.4.0 should be installed with -g
kexec@2.0.2 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/kexec
node-gyp rebuild
CXX(target) Release/obj.target/kexec/src/kexec.o
SOLINK_MODULE(target) Release/kexec.node
nodeos-mount@0.2.0 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-mount
node-gyp rebuild
CXX(target) Release/obj.target/mount/mount.o
../mount.cc:30:15: error: no matching function for call to 'mount'
int ret = mount(mounty->devFile.c_str(),
^~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/sys/mount.h:395:5: note: candidate function not viable: requires 4 arguments, but 5 were provided
int mount(const char *, const char *, int, void *);
^
../mount.cc:49:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "mount", "", mounty->devFile.c_str());
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Localv8::Value NanErrnoException(
^
../mount.cc:66:15: error: use of undeclared identifier 'umount'
int ret = umount(mounty->target.c_str());
^
../mount.cc:80:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "umount", "", mounty->target.c_str());
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Localv8::Value NanErrnoException(
^
../mount.cc:159:13: error: no matching function for call to 'mount'
int ret = mount(s_devFile.c_str(),
^~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/sys/mount.h:395:5: note: candidate function not viable: requires 4 arguments, but 5 were provided
int mount(const char *, const char *, int, void *);
^
../mount.cc:166:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "mount", "", s_devFile.c_str()));
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Localv8::Value NanErrnoException(
^
../mount.cc:184:13: error: use of undeclared identifier 'umount'; did you mean 'Umount'?
int ret = umount(s_target.c_str());
^~~~~~
Umount
../mount.cc:121:12: note: 'Umount' declared here
NAN_METHOD(Umount) {
^
../mount.cc:184:20: error: reference to type 'const FunctionCallbackInfov8::Value' could not bind to an rvalue of type 'const char *'
int ret = umount(s_target.c_str());
^~~~~~~~~~~~~~~~
../mount.cc:121:1: note: passing argument to parameter 'info' here
NAN_METHOD(Umount) {
^
../../nan/nan.h:1298:64: note: expanded from macro 'NAN_METHOD'
Nan::NAN_METHOD_RETURN_TYPE name(Nan::NAN_METHOD_ARGS_TYPE info)
^
../mount.cc:186:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "umount", "", s_target.c_str()));
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Localv8::Value NanErrnoException(
^
4 warnings and 5 errors generated.
make: *** [Release/obj.target/mount/mount.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:100:13)
gyp ERR! stack at ChildProcess.emit (events.js:185:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Darwin 16.0.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-mount
gyp ERR! node -v v5.8.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
NodeOS@1.0.0-RC2 /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS
├─┬ nodeos-barebones@1.0.0-RC2.3
│ ├─┬ cpio2tar@0.0.1
│ │ └── cpio-stream@1.3.0
│ ├─┬ download-manager@0.0.20
│ │ ├── diff@2.2.3
│ │ ├─┬ download@4.4.1 (git://github.com/nodeos/download.git#e405ae2b6bce31dd8220d0154bbe9964d5a66fb3)
│ │ │ ├─┬ caw@1.2.0
│ │ │ │ ├── get-proxy@1.1.0
│ │ │ │ ├── is-obj@1.0.1
│ │ │ │ ├── object-assign@3.0.0
│ │ │ │ └── tunnel-agent@0.4.3
│ │ │ ├─┬ each-async@1.1.1
│ │ │ │ └── set-immediate-shim@1.0.1
│ │ │ ├─┬ filenamify@1.2.1
│ │ │ │ ├── filename-reserved-regex@1.0.0
│ │ │ │ ├── strip-outer@1.0.0
│ │ │ │ └── trim-repeated@1.0.0
│ │ │ ├─┬ gulp-decompress@1.2.0
│ │ │ │ ├─┬ archive-type@3.2.0
│ │ │ │ │ └── file-type@3.8.0
│ │ │ │ ├─┬ decompress@3.0.0
│ │ │ │ │ ├─┬ buffer-to-vinyl@1.1.0
│ │ │ │ │ │ └── uuid@2.0.2
│ │ │ │ │ ├─┬ decompress-tar@3.1.0
│ │ │ │ │ │ ├── is-tar@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-tarbz2@3.1.0
│ │ │ │ │ │ ├── is-bzip2@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ ├─┬ seek-bzip@1.0.5
│ │ │ │ │ │ │ └─┬ commander@2.8.1
│ │ │ │ │ │ │ └── graceful-readlink@1.0.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-targz@3.1.0
│ │ │ │ │ │ ├── is-gzip@1.0.0
│ │ │ │ │ │ ├── object-assign@2.1.1
│ │ │ │ │ │ └─┬ vinyl@0.4.6
│ │ │ │ │ │ └── clone@0.2.0
│ │ │ │ │ ├─┬ decompress-unzip@3.4.0
│ │ │ │ │ │ ├── is-zip@1.0.0
│ │ │ │ │ │ ├── stat-mode@0.2.1
│ │ │ │ │ │ ├── through2@2.0.1
│ │ │ │ │ │ └─┬ yauzl@2.6.0
│ │ │ │ │ │ ├── buffer-crc32@0.2.5
│ │ │ │ │ │ └─┬ fd-slicer@1.0.1
│ │ │ │ │ │ └── pend@1.2.0
│ │ │ │ │ └── vinyl-assign@1.2.1
│ │ │ │ └─┬ gulp-util@3.0.7
│ │ │ │ ├── array-differ@1.0.0
│ │ │ │ ├── beeper@1.1.0
│ │ │ │ ├── dateformat@1.0.12
│ │ │ │ ├─┬ fancy-log@1.2.0
│ │ │ │ │ └── time-stamp@1.0.1
│ │ │ │ ├─┬ gulplog@1.0.0
│ │ │ │ │ └── glogg@1.0.0
│ │ │ │ ├─┬ has-gulplog@0.1.0
│ │ │ │ │ └── sparkles@1.0.0
│ │ │ │ ├── lodash._reescape@3.0.0
│ │ │ │ ├── lodash._reevaluate@3.0.0
│ │ │ │ ├── lodash._reinterpolate@3.0.0
│ │ │ │ ├─┬ lodash.template@3.6.2
│ │ │ │ │ ├── lodash._basecopy@3.0.1
│ │ │ │ │ ├── lodash._basetostring@3.0.1
│ │ │ │ │ ├── lodash._basevalues@3.0.0
│ │ │ │ │ ├── lodash._isiterateecall@3.0.9
│ │ │ │ │ ├─┬ lodash.escape@3.2.0
│ │ │ │ │ │ └── lodash._root@3.0.1
│ │ │ │ │ ├─┬ lodash.keys@3.1.2
│ │ │ │ │ │ ├── lodash._getnative@3.9.1
│ │ │ │ │ │ ├── lodash.isarguments@3.0.9
│ │ │ │ │ │ └── lodash.isarray@3.0.4
│ │ │ │ │ ├── lodash.restparam@3.6.1
│ │ │ │ │ └── lodash.templatesettings@3.1.1
│ │ │ │ ├── minimist@1.2.0
│ │ │ │ ├─┬ multipipe@0.1.2
│ │ │ │ │ └─┬ duplexer2@0.0.2
│ │ │ │ │ └─┬ readable-stream@1.1.14
│ │ │ │ │ └── isarray@0.0.1
│ │ │ │ ├── object-assign@3.0.0
│ │ │ │ ├── through2@2.0.1
│ │ │ │ └── vinyl@0.5.3
│ │ │ ├── gulp-rename@1.2.2
│ │ │ ├── is-url@1.2.2
│ │ │ ├── read-all-stream@3.1.0
│ │ │ ├── stream-combiner2@1.1.1
│ │ │ ├─┬ vinyl@1.2.0
│ │ │ │ ├── clone@1.0.2
│ │ │ │ ├── clone-stats@0.0.1
│ │ │ │ └── replace-ext@0.0.1
│ │ │ ├─┬ vinyl-fs@2.2.1 (git://github.com/nodeos/vinyl-fs.git#7cee24e7d53e20aca890b818f92268a2984fc793)
│ │ │ │ ├─┬ duplexify@3.4.5
│ │ │ │ │ ├── end-of-stream@1.0.0
│ │ │ │ │ └── stream-shift@1.0.0
│ │ │ │ ├─┬ glob-stream@5.3.2
│ │ │ │ │ ├── extend@3.0.0
│ │ │ │ │ ├── glob@5.0.15
│ │ │ │ │ ├─┬ glob-parent@2.0.0
│ │ │ │ │ │ └── is-glob@2.0.1
│ │ │ │ │ ├─┬ micromatch@2.3.11
│ │ │ │ │ │ ├─┬ arr-diff@2.0.0
│ │ │ │ │ │ │ └── arr-flatten@1.0.1
│ │ │ │ │ │ ├── array-unique@0.2.1
│ │ │ │ │ │ ├─┬ braces@1.8.5
│ │ │ │ │ │ │ ├─┬ expand-range@1.8.2
│ │ │ │ │ │ │ │ └─┬ fill-range@2.2.3
│ │ │ │ │ │ │ │ ├── is-number@2.1.0
│ │ │ │ │ │ │ │ ├── isobject@2.1.0
│ │ │ │ │ │ │ │ ├── randomatic@1.1.5
│ │ │ │ │ │ │ │ └── repeat-string@1.5.4
│ │ │ │ │ │ │ ├── preserve@0.2.0
│ │ │ │ │ │ │ └── repeat-element@1.1.2
│ │ │ │ │ │ ├─┬ expand-brackets@0.1.5
│ │ │ │ │ │ │ └── is-posix-bracket@0.1.1
│ │ │ │ │ │ ├── extglob@0.3.2
│ │ │ │ │ │ ├── filename-regex@2.0.0
│ │ │ │ │ │ ├── is-extglob@1.0.0
│ │ │ │ │ │ ├─┬ kind-of@3.0.4
│ │ │ │ │ │ │ └── is-buffer@1.1.4
│ │ │ │ │ │ ├── normalize-path@2.0.1
│ │ │ │ │ │ ├─┬ object.omit@2.0.0
│ │ │ │ │ │ │ ├─┬ for-own@0.1.4
│ │ │ │ │ │ │ │ └── for-in@0.1.5
│ │ │ │ │ │ │ └── is-extendable@0.1.1
│ │ │ │ │ │ ├─┬ parse-glob@3.0.4
│ │ │ │ │ │ │ ├── glob-base@0.3.0
│ │ │ │ │ │ │ └── is-dotfile@1.0.2
│ │ │ │ │ │ └─┬ regex-cache@0.4.3
│ │ │ │ │ │ ├── is-equal-shallow@0.1.3
│ │ │ │ │ │ └── is-primitive@2.0.0
│ │ │ │ │ ├── ordered-read-streams@0.3.0
│ │ │ │ │ ├─┬ through2@0.6.5
│ │ │ │ │ │ └─┬ readable-stream@1.0.34
│ │ │ │ │ │ └── isarray@0.0.1
│ │ │ │ │ ├─┬ to-absolute-glob@0.1.1
│ │ │ │ │ │ └── extend-shallow@2.0.1
│ │ │ │ │ └── unique-stream@2.2.1
│ │ │ │ ├─┬ gulp-sourcemaps@1.6.0
│ │ │ │ │ ├── convert-source-map@1.3.0
│ │ │ │ │ ├── strip-bom@2.0.0
│ │ │ │ │ └── through2@2.0.1
│ │ │ │ ├── is-valid-glob@0.3.0
│ │ │ │ ├── merge-stream@1.0.0
│ │ │ │ ├─┬ strip-bom@2.0.0
│ │ │ │ │ └── is-utf8@0.2.1
│ │ │ │ ├─┬ strip-bom-stream@1.0.0
│ │ │ │ │ ├── first-chunk-stream@1.0.0
│ │ │ │ │ └── strip-bom@2.0.0
│ │ │ │ ├── through2@2.0.1
│ │ │ │ └─┬ through2-filter@2.0.0
│ │ │ │ └── through2@2.0.1
│ │ │ └─┬ ware@1.3.0
│ │ │ └─┬ wrap-fn@0.1.5
│ │ │ └── co@3.1.0
│ │ ├─┬ download-checksum@0.1.3
│ │ │ └─┬ openpgp@1.6.2
│ │ │ ├── es6-promise@1.0.0
│ │ │ ├─┬ node-fetch@1.6.0
│ │ │ │ └─┬ encoding@0.1.12
│ │ │ │ └── iconv-lite@0.4.13
│ │ │ ├── node-localstorage@1.1.2
│ │ │ └── zlibjs@0.2.0
│ │ ├─┬ download-status@2.2.1
│ │ │ ├─┬ chalk@0.5.1
│ │ │ │ ├── ansi-styles@1.1.0
│ │ │ │ ├─┬ has-ansi@0.1.0
│ │ │ │ │ └── ansi-regex@0.2.1
│ │ │ │ ├── strip-ansi@0.3.0
│ │ │ │ └── supports-color@0.2.0
│ │ │ ├─┬ lpad-align@1.1.0
│ │ │ │ ├── longest@1.0.1
│ │ │ │ ├── lpad@2.0.1
│ │ │ │ └─┬ meow@3.7.0
│ │ │ │ ├─┬ camelcase-keys@2.1.0
│ │ │ │ │ └── camelcase@2.1.1
│ │ │ │ ├── decamelize@1.2.0
│ │ │ │ ├─┬ loud-rejection@1.6.0
│ │ │ │ │ ├─┬ currently-unhandled@0.4.1
│ │ │ │ │ │ └── array-find-index@1.0.1
│ │ │ │ │ └── signal-exit@3.0.0
│ │ │ │ ├── map-obj@1.0.1
│ │ │ │ ├── minimist@1.2.0
│ │ │ │ ├─┬ normalize-package-data@2.3.5
│ │ │ │ │ ├── hosted-git-info@2.1.5
│ │ │ │ │ ├─┬ is-builtin-module@1.0.0
│ │ │ │ │ │ └── builtin-modules@1.1.1
│ │ │ │ │ └─┬ validate-npm-package-license@3.0.1
│ │ │ │ │ ├─┬ spdx-correct@1.0.2
│ │ │ │ │ │ └── spdx-license-ids@1.2.2
│ │ │ │ │ └─┬ spdx-expression-parse@1.0.2
│ │ │ │ │ └── spdx-exceptions@1.0.5
│ │ │ │ ├─┬ read-pkg-up@1.0.1
│ │ │ │ │ ├─┬ find-up@1.1.2
│ │ │ │ │ │ └── path-exists@2.1.0
│ │ │ │ │ └─┬ read-pkg@1.1.0
│ │ │ │ │ ├─┬ load-json-file@1.1.0
│ │ │ │ │ │ └── strip-bom@2.0.0
│ │ │ │ │ └── path-type@1.1.0
│ │ │ │ ├─┬ redent@1.0.0
│ │ │ │ │ ├─┬ indent-string@2.1.0
│ │ │ │ │ │ └─┬ repeating@2.0.1
│ │ │ │ │ │ └── is-finite@1.0.1
│ │ │ │ │ └── strip-indent@1.0.1
│ │ │ │ └── trim-newlines@1.0.0
│ │ │ └── object-assign@2.1.1
│ │ ├─┬ got@5.6.0
│ │ │ ├─┬ create-error-class@3.0.2
│ │ │ │ └── capture-stack-trace@1.0.0
│ │ │ ├── duplexer2@0.1.4
│ │ │ ├── is-plain-obj@1.1.0
│ │ │ ├── is-redirect@1.0.0
│ │ │ ├── is-retry-allowed@1.1.0
│ │ │ ├── is-stream@1.1.0
│ │ │ ├── lowercase-keys@1.0.0
│ │ │ ├── node-status-codes@1.0.0
│ │ │ ├─┬ parse-json@2.2.0
│ │ │ │ └─┬ error-ex@1.3.0
│ │ │ │ └── is-arrayish@0.2.1
│ │ │ ├── timed-out@2.0.0
│ │ │ └─┬ url-parse-lax@1.0.0
│ │ │ └── prepend-http@1.0.4
│ │ └─┬ strip-dirs@1.1.1
│ │ ├── get-stdin@4.0.1
│ │ ├─┬ is-absolute@0.1.7
│ │ │ └── is-relative@0.1.3
│ │ ├── is-natural-number@2.1.1
│ │ ├── minimist@1.2.0
│ │ └── sum-up@1.0.3
│ ├── minimist@1.2.0
│ └── nodeos-nodejs@6.3.1 (git://github.com/nodeos/nodejs.git#4168865150b8dd08cf7f9f21805c0d67972872d7)
├─┬ nodeos-cross-toolchain@1.0.0-RC2.11
│ ├─┬ fs-extra@0.30.0
│ │ ├── jsonfile@2.3.1
│ │ └── klaw@1.3.0
│ └─┬ prebuild-install@1.0.2
│ ├── minimist@1.2.0
│ └── simple-get@2.2.2
├── UNMET DEPENDENCY nodeos-initramfs@1.0.0-RC2.4
├── nodeos-mount-filesystems@0.1.6 extraneous
├── UNMET PEER DEPENDENCY nodeos-mount-utils@^0.1.0
├─┬ nodeos-rootfs@1.0.0-RC2.1
│ └─┬ genfatfs@1.0.1 (git://github.com/nodeos/genfatfs.git#6a8dba0a4f101e97fba1d40815e9212473a0b084)
│ └─┬ prebuild-install@1.1.0
│ └── minimist@1.2.0
├─┬ nodeos-usersfs@1.0.0-RC2
│ ├── debugfs@0.0.2
│ ├── genext2fs@1.4.1-0 (git://github.com/nodeos/genext2fs.git#bc47c9232d9660fbda5eaad285ca5fa0d7f399c4)
│ └─┬ node-wget@0.4.2
│ └─┬ request@2.27.0
│ ├── aws-sign@0.3.0
│ ├── cookie-jar@0.3.0
│ ├── forever-agent@0.5.2
│ ├─┬ form-data@0.1.4
│ │ ├── async@0.9.2
│ │ └─┬ combined-stream@0.0.7
│ │ └── delayed-stream@0.0.5
│ ├─┬ hawk@1.0.0
│ │ ├── boom@0.4.2
│ │ ├── cryptiles@0.2.2
│ │ ├── hoek@0.9.1
│ │ └── sntp@0.2.4
│ ├─┬ http-signature@0.10.1
│ │ ├── asn1@0.1.11
│ │ ├── assert-plus@0.1.5
│ │ └── ctype@0.5.3
│ ├── json-stringify-safe@5.0.1
│ ├── mime@1.2.11
│ ├── node-uuid@1.4.7
│ ├── oauth-sign@0.3.0
│ ├── qs@0.6.6
│ └── tunnel-agent@0.3.0
├── posix@4.0.2 extraneous
├─┬ prebuild@4.2.2 (git://github.com/piranna/prebuild.git#beef82503dbb1296d7606e551546b6a2f26333c4)
│ ├── async@1.5.2
│ ├── expand-template@1.0.2
│ ├─┬ ghreleases@1.0.5
│ │ ├── after@0.8.1
│ │ ├── ghrepos@2.0.0
│ │ ├─┬ ghutils@3.2.0
│ │ │ └─┬ jsonist@1.2.0
│ │ │ ├── bl@1.0.3
│ │ │ └─┬ hyperquest@1.2.0
│ │ │ └─┬ duplexer2@0.0.2
│ │ │ └─┬ readable-stream@1.1.14
│ │ │ └── isarray@0.0.1
│ │ ├── simple-mime@0.1.0
│ │ └── url-template@2.0.8
│ ├── github-from-package@0.0.0
│ ├── minimist@1.2.0
│ ├─┬ node-gyp@3.4.0
│ │ ├── fstream@1.0.10
│ │ ├─┬ nopt@3.0.6
│ │ │ └── abbrev@1.0.9
│ │ ├─┬ osenv@0.1.3
│ │ │ └── os-tmpdir@1.0.1
│ │ ├─┬ path-array@1.0.1
│ │ │ └── array-index@1.0.0
│ │ ├─┬ tar@2.2.1
│ │ │ └── block-stream@0.0.9
│ │ └─┬ which@1.2.10
│ │ └── isexe@1.1.2
│ ├── node-ninja@1.0.2
│ ├── noop-logger@0.1.1
│ ├─┬ npmlog@2.0.4
│ │ ├── ansi@0.3.1
│ │ ├─┬ are-we-there-yet@1.1.2
│ │ │ └── delegates@1.0.0
│ │ └─┬ gauge@1.2.7
│ │ ├── has-unicode@2.0.1
│ │ ├── lodash.pad@4.5.0
│ │ ├── lodash.padend@4.6.0
│ │ └── lodash.padstart@4.6.0
│ ├─┬ pump@1.0.1
│ │ └── end-of-stream@1.1.0
│ ├─┬ rc@1.1.6
│ │ ├── deep-extend@0.4.1
│ │ ├── ini@1.3.4
│ │ └── minimist@1.2.0
│ ├── semver@5.3.0
│ ├─┬ simple-get@1.4.3
│ │ └── unzip-response@1.0.0
│ ├── tar-fs@1.13.0
│ └─┬ tar-stream@1.5.2
│ └── bl@1.1.2
├── qemu@2.6.0 (git://github.com/nodeos/qemu.git#d15f8861fdd1e0a4940753aef5a0a0825b136665)
├─┬ suppose@0.6.1
│ ├─┬ force-array@3.1.0
│ │ └── is-array@1.0.1
│ └── string@3.3.1
└── usrbinenv@0.0.3 extraneous
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.8.0
npm ERR! npm v3.9.2
npm ERR! code ELIFECYCLE
npm ERR! nodeos-mount@0.2.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nodeos-mount@0.2.0 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-mount package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-mount
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-mount
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/npm-debug.log
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgfvo50bvX8fJ8OJvoXIe5KEq-t2Q5Kks5qffi6gaJpZM4Jjt0W
.
I dont think you mean me, because i dont own OSX.
I was doing testing and documenting on the internal modules (mount-filesystem...)
I bet it was you... I'm bad with the names, sorry. Anyway there was some
progress with that, but was not complete.
El 13/8/2016 19:52, "Philipp Czarnetzki" notifications@github.com
escribió:
I dont think you mean me, because i dont own OSX.
I was doing testing and documenting on the internal modules
(mount-filesystem...)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291#issuecomment-239633217, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvjfESSyTxHZvpjaUZq2wTZ71pEnlks5qfgRsgaJpZM4Jjt0W
.
@tylerl0706 it somehow dont even recognizes this preprocessor flag, it just uses the linux flag and then crashes the process.
Its also a duplicate NodeOS/nodeos-mount#5
Ok, it was being done by @joshgarde, sorry for the confusion. Could you be
able to give some insight about this and your OSX progresses?
El 13/8/2016 20:10, "Philipp Czarnetzki" notifications@github.com
escribió:
@tylerl0706 https://github.com/tylerl0706 it somehow dont even
recognizes this
https://github.com/NodeOS/nodeos-mount/blob/master/mount.cc#L36
preprocessor flag, it just uses the linux flag and then crashes the process.
Its also a duplicate NodeOS/nodeos-mount#5
https://github.com/NodeOS/nodeos-mount/issues/5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291#issuecomment-239633985, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvgCWi9it8fdWE64NoID4AOhBbqiiks5qfgiHgaJpZM4Jjt0W
.
This should be fixed in master, can you both confirm?
Did I do something wrong? I did a fresh clone of master.
NodeOS git:(master) npm install
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN prefer global marked@0.3.6 should be installed with -g
npm WARN prefer global npm@3.10.6 should be installed with -g
npm WARN prefer global forever@0.11.1 should be installed with -g
npm WARN prefer global node-ninja@1.0.2 should be installed with -g
npm WARN prefer global node-gyp@3.4.0 should be installed with -g
npm WARN prefer global slap@0.1.60 should be installed with -g
npm WARN prefer global loadtest@1.4.4 should be installed with -g
> kexec@2.0.2 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/kexec
> node-gyp rebuild
CXX(target) Release/obj.target/kexec/src/kexec.o
SOLINK_MODULE(target) Release/kexec.node
> bufferutil@1.2.1 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/bufferutil
> node-gyp rebuild
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
> nodeos-mount@0.3.0 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-mount
> node-gyp rebuild
CXX(target) Release/obj.target/mount/mount.o
../mount.cc:59:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "mount", "",
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:97:22: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
argv[0] = Nan::NanErrnoException(mounty->error, "umount", "",
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:193:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "mount", "",
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
../mount.cc:220:33: warning: 'NanErrnoException' is deprecated [-Wdeprecated-declarations]
return Nan::ThrowError(Nan::NanErrnoException(errno, "umount", "",
^
../../nan/nan.h:862:46: note: 'NanErrnoException' has been explicitly marked deprecated here
NAN_DEPRECATED inline v8::Local<v8::Value> NanErrnoException(
^
4 warnings generated.
SOLINK_MODULE(target) Release/mount.node
> posix@4.0.2 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/posix
> node-gyp rebuild
CXX(target) Release/obj.target/posix/src/posix.o
SOLINK_MODULE(target) Release/posix.node
> runas@3.1.1 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/runas
> node-gyp rebuild
CXX(target) Release/obj.target/runas/src/main.o
CXX(target) Release/obj.target/runas/src/runas_darwin.o
CXX(target) Release/obj.target/runas/src/fork.o
SOLINK_MODULE(target) Release/runas.node
> pathwatcher@6.7.1 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/pathwatcher
> node-gyp rebuild
CXX(target) Release/obj.target/pathwatcher/src/main.o
CXX(target) Release/obj.target/pathwatcher/src/common.o
CXX(target) Release/obj.target/pathwatcher/src/handle_map.o
CXX(target) Release/obj.target/pathwatcher/src/pathwatcher_unix.o
SOLINK_MODULE(target) Release/pathwatcher.node
> utf-8-validate@1.2.1 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/utf-8-validate
> node-gyp rebuild
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
> qemu@2.6.0 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/qemu
> prebuild-install -d https://github.com/NodeOS/qemu/releases/download/v{version}/{platform}-{arch}.tar.gz || npm run build
> nodeos-cross-toolchain@1.0.0-RC2.11 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-cross-toolchain
> scripts/install
> nodeos-nodejs@6.5.0 install /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-nodejs
> scripts/install
prebuild-install WARN install No prebuilt binaries found (target=v5.8.0 arch=x64 platform=darwin)
> nodeos-nodejs@6.5.0 build /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-nodejs
> scripts/build
rmdir: illegal option -- -
usage: rmdir [-p] directory ...
Downloading...
Done!
scripts/build: line 106: sha256sum: command not found
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3576 0 3576 0 0 20042 0 --:--:-- --:--:-- --:--:-- 20203
(23) Failed writing body
rmdir: illegal option -- -
usage: rmdir [-p] directory ...
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/.bin/npm" "run" "build" "--"
npm ERR! node v5.8.0
npm ERR! npm v3.10.6
npm ERR! code ELIFECYCLE
npm ERR! nodeos-nodejs@6.5.0 build: `scripts/build`
npm ERR! Exit status 5
npm ERR!
npm ERR! Failed at the nodeos-nodejs@6.5.0 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-nodejs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-nodejs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-nodejs
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/node_modules/nodeos-nodejs/npm-debug.log
NodeOS@1.0.0-RC2 /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS
├── abbrev@1.0.9
├── aproba@1.0.4
├── bin-man@0.2.0 extraneous
├── bin-pwd@0.0.0 extraneous
├── cpio2tar@0.0.1 extraneous
├── davius@0.0.1 extraneous
├── debugfs@0.0.2 extraneous
├── dhcpjs@0.5.0 extraneous
├── forever@0.11.1 extraneous (git://github.com/piranna/forever.git#88be8edd251750d3f2d053798c0137edc8182fbf)
├─┬ fstream@1.0.10
│ ├── graceful-fs@4.1.4
│ ├── inherits@2.0.1
│ └─┬ mkdirp@0.5.1
│ └── minimist@0.0.8
├── genext2fs@1.4.1-0 extraneous
├─┬ glob@7.0.5
│ ├── fs.realpath@1.0.0
│ ├── inflight@1.0.5
│ ├─┬ minimatch@3.0.2
│ │ └─┬ brace-expansion@1.1.5
│ │ ├── balanced-match@0.4.1
│ │ └── concat-map@0.0.1
│ ├── once@1.3.3
│ └── path-is-absolute@1.0.0
├── has-unicode@2.0.1
├── loadtest@1.4.4 extraneous
├── logon@0.1.1 extraneous
├─┬ node-gyp@3.4.0
│ ├─┬ minimatch@3.0.2
│ │ └─┬ brace-expansion@1.1.5
│ │ ├── balanced-match@0.4.1
│ │ └── concat-map@0.0.1
│ ├── nopt@3.0.6
│ ├─┬ npmlog@3.1.2
│ │ ├─┬ are-we-there-yet@1.1.2
│ │ │ └── delegates@1.0.0
│ │ ├── console-control-strings@1.1.0
│ │ ├─┬ gauge@2.6.0
│ │ │ ├── has-color@0.1.7
│ │ │ ├── object-assign@4.1.0
│ │ │ ├── signal-exit@3.0.0
│ │ │ ├─┬ string-width@1.0.1
│ │ │ │ ├─┬ code-point-at@1.0.0
│ │ │ │ │ └── number-is-nan@1.0.0
│ │ │ │ └─┬ is-fullwidth-code-point@1.0.0
│ │ │ │ └── number-is-nan@1.0.0
│ │ │ ├─┬ strip-ansi@3.0.1
│ │ │ │ └── ansi-regex@2.0.0
│ │ │ └── wide-align@1.1.0
│ │ └── set-blocking@2.0.0
│ ├─┬ osenv@0.1.3
│ │ ├── os-homedir@1.0.1
│ │ └── os-tmpdir@1.0.1
│ ├─┬ path-array@1.0.1
│ │ └─┬ array-index@1.0.0
│ │ ├─┬ debug@2.2.0
│ │ │ └── ms@0.7.1
│ │ └─┬ es6-symbol@3.1.0
│ │ ├── d@0.1.1
│ │ └─┬ es5-ext@0.10.12
│ │ └── es6-iterator@2.0.0
│ ├─┬ request@2.72.0
│ │ ├── aws-sign2@0.6.0
│ │ ├─┬ aws4@1.3.2
│ │ │ └─┬ lru-cache@4.0.1
│ │ │ ├── pseudomap@1.0.2
│ │ │ └── yallist@2.0.0
│ │ ├─┬ bl@1.1.2
│ │ │ └─┬ readable-stream@2.0.6
│ │ │ ├── core-util-is@1.0.2
│ │ │ ├── isarray@1.0.0
│ │ │ ├── process-nextick-args@1.0.6
│ │ │ ├── string_decoder@0.10.31
│ │ │ └── util-deprecate@1.0.2
│ │ ├── caseless@0.11.0
│ │ ├─┬ combined-stream@1.0.5
│ │ │ └── delayed-stream@1.0.0
│ │ ├── extend@3.0.0
│ │ ├── forever-agent@0.6.1
│ │ ├─┬ form-data@1.0.0-rc4
│ │ │ └── async@1.5.2
│ │ ├─┬ har-validator@2.0.6
│ │ │ ├─┬ chalk@1.1.3
│ │ │ │ ├── ansi-styles@2.2.1
│ │ │ │ ├── escape-string-regexp@1.0.5
│ │ │ │ ├── has-ansi@2.0.0
│ │ │ │ └── supports-color@2.0.0
│ │ │ ├─┬ commander@2.9.0
│ │ │ │ └── graceful-readlink@1.0.1
│ │ │ ├─┬ is-my-json-valid@2.13.1
│ │ │ │ ├── generate-function@2.0.0
│ │ │ │ ├─┬ generate-object-property@1.2.0
│ │ │ │ │ └── is-property@1.0.2
│ │ │ │ ├── jsonpointer@2.0.0
│ │ │ │ └── xtend@4.0.1
│ │ │ └─┬ pinkie-promise@2.0.1
│ │ │ └── pinkie@2.0.4
│ │ ├─┬ hawk@3.1.3
│ │ │ ├── boom@2.10.1
│ │ │ ├── cryptiles@2.0.5
│ │ │ ├── hoek@2.16.3
│ │ │ └── sntp@1.0.9
│ │ ├─┬ http-signature@1.1.1
│ │ │ ├── assert-plus@0.2.0
│ │ │ ├─┬ jsprim@1.2.2
│ │ │ │ ├── extsprintf@1.0.2
│ │ │ │ ├── json-schema@0.2.2
│ │ │ │ └── verror@1.3.6
│ │ │ └─┬ sshpk@1.7.4
│ │ │ ├── asn1@0.2.3
│ │ │ ├─┬ dashdash@1.13.0
│ │ │ │ └── assert-plus@1.0.0
│ │ │ ├── ecc-jsbn@0.1.1
│ │ │ ├── jodid25519@1.0.2
│ │ │ ├── jsbn@0.1.0
│ │ │ └── tweetnacl@0.14.3
│ │ ├── is-typedarray@1.0.0
│ │ ├── isstream@0.1.2
│ │ ├── json-stringify-safe@5.0.1
│ │ ├─┬ mime-types@2.1.10
│ │ │ └── mime-db@1.22.0
│ │ ├── node-uuid@1.4.7
│ │ ├── oauth-sign@0.8.1
│ │ ├── qs@6.1.0
│ │ ├── stringstream@0.0.5
│ │ ├── tough-cookie@2.2.2
│ │ └── tunnel-agent@0.4.2
│ ├── semver@5.1.0
│ └─┬ tar@2.2.1
│ └── block-stream@0.0.8
├── node-wget@0.4.2 extraneous
├── UNMET DEPENDENCY nodeos-barebones@github:nodeos/nodeos-barebones
├─┬ nodeos-cross-toolchain@1.0.0-RC2.11 (git://github.com/nodeos/nodeos-cross-toolchain.git#51e60f19ac7bca028f4d7148bc79802386777158)
│ ├─┬ async@2.0.1
│ │ └── lodash@4.15.0
│ ├─┬ download-manager@0.1.2
│ │ ├─┬ decompress-maybe@1.0.0
│ │ │ ├─┬ bzip2-maybe@1.0.0
│ │ │ │ ├── is-bzip2@1.0.0
│ │ │ │ ├─┬ peek-stream@1.1.1
│ │ │ │ │ └─┬ through2@0.5.1
│ │ │ │ │ ├─┬ readable-stream@1.0.34
│ │ │ │ │ │ └── isarray@0.0.1
│ │ │ │ │ └── xtend@3.0.0
│ │ │ │ ├── through2@2.0.1
│ │ │ │ └─┬ unbzip2-stream@1.0.9
│ │ │ │ ├─┬ buffer@3.6.0
│ │ │ │ │ ├── base64-js@0.0.8
│ │ │ │ │ └── ieee754@1.1.6
│ │ │ │ └── through@2.3.8
│ │ │ ├─┬ gunzip-maybe@1.3.1
│ │ │ │ ├─┬ browserify-zlib@0.1.4
│ │ │ │ │ └── pako@0.2.9
│ │ │ │ ├── is-deflate@1.0.0
│ │ │ │ ├── is-gzip@1.0.0
│ │ │ │ └─┬ through2@0.4.2
│ │ │ │ ├─┬ readable-stream@1.0.34
│ │ │ │ │ └── isarray@0.0.1
│ │ │ │ └─┬ xtend@2.1.2
│ │ │ │ └── object-keys@0.4.0
│ │ │ └─┬ pumpify@1.3.5
│ │ │ └─┬ duplexify@3.4.5
│ │ │ ├── end-of-stream@1.0.0
│ │ │ └── stream-shift@1.0.0
│ │ ├── diff@3.0.0
│ │ ├─┬ download-checksum@0.3.0
│ │ │ ├── inherits@2.0.1
│ │ │ └─┬ openpgp@2.3.3
│ │ │ ├─┬ node-fetch@1.6.0
│ │ │ │ └─┬ encoding@0.1.12
│ │ │ │ └── iconv-lite@0.4.13
│ │ │ └─┬ node-localstorage@1.3.0
│ │ │ └─┬ write-file-atomic@1.2.0
│ │ │ ├── imurmurhash@0.1.4
│ │ │ └── slide@1.1.6
│ │ ├─┬ got@6.3.0
│ │ │ ├─┬ create-error-class@3.0.2
│ │ │ │ └── capture-stack-trace@1.0.0
│ │ │ ├── duplexer3@0.1.4
│ │ │ ├── get-stream@1.1.0
│ │ │ ├── is-plain-obj@1.1.0
│ │ │ ├── is-redirect@1.0.0
│ │ │ ├── is-retry-allowed@1.1.0
│ │ │ ├── is-stream@1.1.0
│ │ │ ├── lowercase-keys@1.0.0
│ │ │ ├── node-status-codes@2.0.0
│ │ │ ├── timed-out@2.0.0
│ │ │ └─┬ url-parse-lax@1.0.0
│ │ │ └── prepend-http@1.0.4
│ │ ├─┬ multi-progress@2.0.0
│ │ │ └── progress@1.1.8
│ │ ├── rimraf@2.5.4
│ │ ├─┬ string.prototype.padend@3.0.0
│ │ │ ├─┬ define-properties@1.1.2
│ │ │ │ ├── foreach@2.0.5
│ │ │ │ └── object-keys@1.0.11
│ │ │ ├─┬ es-abstract@1.6.1
│ │ │ │ ├─┬ es-to-primitive@1.1.1
│ │ │ │ │ ├── is-date-object@1.0.1
│ │ │ │ │ └── is-symbol@1.0.1
│ │ │ │ ├── is-callable@1.1.3
│ │ │ │ └── is-regex@1.0.3
│ │ │ └── function-bind@1.1.0
│ │ └─┬ strip-dirs@2.0.0
│ │ └── is-natural-number@4.0.1
│ ├─┬ fs-extra@0.30.0
│ │ ├── graceful-fs@4.1.6
│ │ ├── jsonfile@2.3.1
│ │ ├── klaw@1.3.0
│ │ └── path-is-absolute@1.0.0
│ └─┬ prebuild-install@1.0.2
│ └── simple-get@2.2.2
├── UNMET DEPENDENCY nodeos-initramfs@github:nodeos/nodeos-initramfs
├── nodeos-mount-filesystems@0.2.1 extraneous
├── nodeos-mount-utils@0.2.0 extraneous
├── nodeos-reverse-proxy@0.1.0 extraneous
├─┬ nodeos-rootfs@1.0.0-RC2.0 (git://github.com/nodeos/nodeos-rootfs.git#4f3bc727dcc48ac4a1c90a18cf663cc1811c993e)
│ └─┬ genfatfs@1.0.1 (git://github.com/nodeos/genfatfs.git#6a8dba0a4f101e97fba1d40815e9212473a0b084)
│ └── prebuild-install@1.1.0
├── npm@3.10.6 extraneous
├─┬ npm-package-arg@4.2.0
│ └── hosted-git-info@2.1.5
├── npm-user-validate@0.1.5
├── ntp-client@0.5.3 extraneous
├── performance@1.1.1 extraneous
├─┬ prebuild@4.2.2 (git://github.com/piranna/prebuild.git#beef82503dbb1296d7606e551546b6a2f26333c4)
│ ├── async@1.5.2
│ ├── expand-template@1.0.2
│ ├─┬ ghreleases@1.0.5
│ │ ├── after@0.8.2
│ │ ├── ghrepos@2.0.0
│ │ ├─┬ ghutils@3.2.0
│ │ │ └─┬ jsonist@1.2.0
│ │ │ ├── bl@1.0.3
│ │ │ ├─┬ hyperquest@1.2.0
│ │ │ │ ├─┬ duplexer2@0.0.2
│ │ │ │ │ └─┬ readable-stream@1.1.14
│ │ │ │ │ └── isarray@0.0.1
│ │ │ │ └─┬ through2@0.6.5
│ │ │ │ └── readable-stream@1.0.34
│ │ │ └── json-stringify-safe@5.0.1
│ │ ├── simple-mime@0.1.0
│ │ └── url-template@2.0.8
│ ├── github-from-package@0.0.0
│ ├── minimist@1.2.0
│ ├─┬ mkdirp@0.5.1
│ │ └── minimist@0.0.8
│ ├─┬ node-gyp@3.4.0
│ │ ├── fstream@1.0.10
│ │ ├─┬ glob@7.0.6
│ │ │ ├── fs.realpath@1.0.0
│ │ │ └── inflight@1.0.5
│ │ ├─┬ minimatch@3.0.3
│ │ │ └─┬ brace-expansion@1.1.6
│ │ │ ├── balanced-match@0.4.2
│ │ │ └── concat-map@0.0.1
│ │ ├─┬ nopt@2.1.2
│ │ │ └── abbrev@1.0.9
│ │ ├─┬ osenv@0.1.3
│ │ │ └── os-tmpdir@1.0.1
│ │ ├─┬ path-array@1.0.1
│ │ │ └─┬ array-index@1.0.0
│ │ │ ├─┬ debug@2.2.0
│ │ │ │ └── ms@0.7.1
│ │ │ └─┬ es6-symbol@3.1.0
│ │ │ ├── d@0.1.1
│ │ │ └─┬ es5-ext@0.10.12
│ │ │ ├── es6-iterator@2.0.0
│ │ │ └── es6-symbol@3.1.0
│ │ ├── request@2.9.203
│ │ ├─┬ tar@2.2.1
│ │ │ └── block-stream@0.0.9
│ │ └─┬ which@1.2.11
│ │ └── isexe@1.1.2
│ ├── node-ninja@1.0.2
│ ├── noop-logger@0.1.1
│ ├─┬ npmlog@2.0.4
│ │ ├── ansi@0.3.1
│ │ ├─┬ are-we-there-yet@1.1.2
│ │ │ └── delegates@1.0.0
│ │ └─┬ gauge@1.2.7
│ │ ├── has-unicode@2.0.1
│ │ ├── lodash.pad@4.5.1
│ │ ├── lodash.padend@4.6.1
│ │ └── lodash.padstart@4.6.1
│ ├── os-homedir@1.0.1
│ ├─┬ pump@1.0.1
│ │ └── end-of-stream@1.1.0
│ ├─┬ rc@1.1.6
│ │ ├── deep-extend@0.4.1
│ │ ├── ini@1.3.4
│ │ └── strip-json-comments@1.0.4
│ ├── semver@5.1.0
│ ├─┬ simple-get@1.4.3
│ │ ├─┬ once@1.3.3
│ │ │ └── wrappy@1.0.2
│ │ └── unzip-response@1.0.1
│ ├── tar-fs@1.13.2
│ ├─┬ tar-stream@1.5.2
│ │ ├── bl@1.1.2
│ │ └─┬ readable-stream@2.0.6
│ │ ├── core-util-is@1.0.2
│ │ ├── isarray@1.0.0
│ │ ├── process-nextick-args@1.0.7
│ │ ├── string_decoder@0.10.31
│ │ └── util-deprecate@1.0.2
│ └── xtend@4.0.1
├── pstree@0.0.0 extraneous
├─┬ qemu@2.6.0 (git://github.com/nodeos/qemu.git#b0b91c77cb3081ae3708f00733d07693e26765bb)
│ └── prebuild-install@1.1.0
├─┬ read-package-tree@5.1.5
│ ├── debuglog@1.0.1
│ ├─┬ dezalgo@1.0.3
│ │ └── asap@2.0.4
│ ├─┬ read-package-json@2.0.4
│ │ ├─┬ glob@6.0.4
│ │ │ ├─┬ minimatch@3.0.0
│ │ │ │ └─┬ brace-expansion@1.1.3
│ │ │ │ ├── balanced-match@0.3.0
│ │ │ │ └── concat-map@0.0.1
│ │ │ └── path-is-absolute@1.0.0
│ │ ├─┬ json-parse-helpfulerror@1.0.3
│ │ │ └── jju@1.3.0
│ │ └─┬ normalize-package-data@2.3.5
│ │ ├─┬ is-builtin-module@1.0.0
│ │ │ └── builtin-modules@1.1.1
│ │ └─┬ validate-npm-package-license@3.0.1
│ │ ├─┬ spdx-correct@1.0.2
│ │ │ └── spdx-license-ids@1.2.0
│ │ └─┬ spdx-expression-parse@1.0.2
│ │ ├── spdx-exceptions@1.0.4
│ │ └── spdx-license-ids@1.2.0
│ └── readdir-scoped-modules@1.0.2
├─┬ readable-stream@2.1.4
│ ├── buffer-shims@1.0.0
│ ├── core-util-is@1.0.2
│ ├── isarray@1.0.0
│ ├── process-nextick-args@1.0.7
│ ├── string_decoder@0.10.31
│ └── util-deprecate@1.0.2
├── rimraf@2.5.3
├── slap@0.1.60 extraneous
├─┬ suppose@0.6.1
│ ├─┬ force-array@3.1.0
│ │ └── is-array@1.0.1
│ ├── string@3.3.1
│ └─┬ strip-ansi@3.0.1
│ └── ansi-regex@2.0.0
├── usrbinenv@0.0.3 extraneous
├─┬ which@1.2.10
│ └── isexe@1.1.2
└── wrappy@1.0.2
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of nodeos-barebones@1.0.0-RC2.2 but none was installed.
npm WARN nodeos-rootfs@1.0.0-RC2.0 requires a peer of nodeos-initramfs@1.0.0-RC2.3 but none was installed.
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.8.0
npm ERR! npm v3.9.2
npm ERR! code ELIFECYCLE
npm ERR! nodeos-nodejs@6.5.0 install: `scripts/install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nodeos-nodejs@6.5.0 install script 'scripts/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-nodejs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-nodejs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-nodejs
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/tylerleonhardt/Desktop/CompSci/Javascript/Node.js/NodeOS/NodeOS/npm-debug.log
I followed these steps: https://github.com/NodeOS/NodeOS#build-nodeos-in-five-steps
Good thing, now nodeos-mount compiles in OSX, so we could close this :-) Bad thing, your problem is compiling Node.js itself :-P It should not be difficult to add support for OSX on the build process, maybe both you and @luii could take a look on that? We could also automate the generation of prebuild images for it :-) After that, I think barebones should build flawlessly, initramfs maybe would have some extra problem due to libfuse... but definitely we are near to be able to build NodeOS on OSX, yay! :-D
Problems are in lines
rmdir: illegal option -- -
usage: rmdir [-p] directory ...
Downloading...
Done!
scripts/build: line 106: sha256sum: command not found
Goodness... GitHub has quite a delay between responding to the email and posting a comment. Please ignore the email comment i make...
Anyway..
On a mac, instead of "sha256sum" it's "shasum -a 256" we'll have to check for that.
As for the rmdir error, I'm not familiar enough with shell to give any input... Any thoughts on that one?
On a mac, instead of "sha256sum" it's "shasum -a 256" we'll have to check for that.
We can use that, sha256sum is somewhat an "alias" of shasum -a 256 (not exactly, but sort of).
As for the rmdir error, I'm not familiar enough with shell to give any input... Any thoughts on that one?
rm -r :-) I don't remember why `rmdir is being used instead... :-/
We can use that, sha256sum is somewhat an "alias" of shasum -a 256 (not exactly, but sort of).
Ah so shasum -a 256 works on Linux?
rm -r :-) I don't remember why `rmdir is being used instead... :-/
rmdir: illegal option -- -
There command is fine, but the options aren't. that's coming from:
https://github.com/NodeOS/nodejs/blob/master/scripts/build#L68
rmdir -p --ignore-fail-on-non-empty `dirname "$@"`
Can you provide what options support rmdir on OSX? rmdir -h or man rmdir should provide you them.
RMDIR(1) BSD General Commands Manual RMDIR(1)
NAME
rmdir -- remove directories
SYNOPSIS
rmdir [-p] directory ...
DESCRIPTION
The rmdir utility removes the directory entry specified by each directory
argument, provided it is empty.
Arguments are processed in the order given. In order to remove both a
parent directory and a subdirectory of that parent, the subdirectory must
be specified first so the parent directory is empty when rmdir tries to
remove it.
The following option is available:
-p Each directory argument is treated as a pathname of which all
components will be removed, if they are empty, starting with the
last most component. (See rm(1) for fully non-discriminant
recursive removal.)
The rmdir utility exits with one of the following values:
0 Each directory entry specified by a dir operand referred to an
empty directory and was removed successfully.
>0 An error occurred.
SEE ALSO
rm(1)
STANDARDS
The rmdir command is expected to be IEEE Std 1003.2 (``POSIX.2'') compat-
ible.
HISTORY
A rmdir command appeared in Version 1 AT&T UNIX.
BSD May 31, 1993 BSD
@piranna also, just to confirm,
shasum -a 256
works on Linux? So we could just change the command to that?
Regarding rmdir, seems it's just a matter of detect OSX and don't use the
flag there.
Regarding shasum, the command options seems to show they are equivalent.
El 11/9/2016 19:05, "Tyler James Leonhardt" notifications@github.com
escribió:
@piranna https://github.com/piranna also, just to confirm,
shasum -a 256
works on Linux? So we could just change the command to that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291#issuecomment-246191115, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvuTOPyPgRdOw18oRxSllCt6pfUsvks5qpDTkgaJpZM4Jjt0W
.
Regarding rmdir, seems it's just a matter of detect OSX and don't use the flag there
I guess my question is... Where is that error coming from?
Is it from --ignore-fail-on-non-empty?
Regarding rmdir, seems it's just a matter of detect OSX and don't use
the flag there
I guess my question is... Where is that error coming from?
Is it from --ignore-fail-on-non-empty?
Seems so, because man of OSX don't show it. That flag on Linux is to don't
set command status as error when it get to a non-empty folder when using
the -P flag (its stop condition), but maybe we can find another workaround.
Try to remove the flag and see if it works on OSX for you.
So I guess my last question is... after making the change, how could I actually test this?
So this is going to be quite the overhaul.
OS X doesn't have wget... I actually ended up using the package I made for NodeOS https://github.com/tylerl0706/wgetjs ;)
In shasum -a 256 -c --ignore-missing --status the --ignore-missing flag doesn't exist...
Which causes this to happen:
shasum: node-v6.5.0-darwin-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-headers.tar.gz: No such file or directory
shasum: node-v6.5.0-headers.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-arm64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-arm64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-armv6l.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-armv6l.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-armv7l.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-armv7l.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-ppc64le.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-ppc64le.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-ppc64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-ppc64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-x64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-x86.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-x86.tar.xz: No such file or directory
shasum: node-v6.5.0.pkg: No such file or directory
shasum: node-v6.5.0-sunos-x64.tar.gz: No such file or directory
shasum: node-v6.5.0-sunos-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-sunos-x86.tar.gz: No such file or directory
shasum: node-v6.5.0-sunos-x86.tar.xz: No such file or directory
shasum: node-v6.5.0.tar.xz: No such file or directory
shasum: node-v6.5.0-win-x64.7z: No such file or directory
shasum: node-v6.5.0-win-x64.zip: No such file or directory
shasum: node-v6.5.0-win-x86.7z: No such file or directory
shasum: node-v6.5.0-win-x86.zip: No such file or directory
shasum: node-v6.5.0-x64.msi: No such file or directory
shasum: node-v6.5.0-x86.msi: No such file or directory
shasum: win-x64/node.exe: No such file or directory
shasum: win-x64/node.lib: No such file or directory
shasum: win-x64/node_pdb.7z: No such file or directory
shasum: win-x64/node_pdb.zip: No such file or directory
shasum: win-x86/node.exe: No such file or directory
shasum: win-x86/node.lib: No such file or directory
shasum: win-x86/node_pdb.7z: No such file or directory
shasum: win-x86/node_pdb.zip: No such file or directory
... and then it crashes.
And people ask me why I stopped using OSX... :-P
It's strange OSX don't have wget, what do you have to download files? Curl?
We could replace for it, but I believe curl is optional in Linux and wget
is built-in... Other alternative is to generate a script to install build
dependencies using brew the same way we use apt for Ubuntu...
And regarding shasum flag, or we wrap it to capture the error (maybe a bash
function to mimic the behaviour of sha256sum?) or you install coreutils.
El 12/9/2016 7:29, "Tyler James Leonhardt" notifications@github.com
escribió:
So this is going to be quite the overhaul.
OS X doesn't have wget... I actually ended up using the package I made for
NodeOS https://github.com/tylerl0706/wgetjs ;)
In shasum -a 256 -c --ignore-missing --status the --ignore-missing flag
doesn't exist...
Which causes this to happen:
shasum: node-v6.5.0-darwin-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-headers.tar.gz: No such file or directory
shasum: node-v6.5.0-headers.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-arm64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-arm64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-armv6l.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-armv6l.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-armv7l.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-armv7l.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-ppc64le.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-ppc64le.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-ppc64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-ppc64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-x64.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-linux-x86.tar.gz: No such file or directory
shasum: node-v6.5.0-linux-x86.tar.xz: No such file or directory
shasum: node-v6.5.0.pkg: No such file or directory
shasum: node-v6.5.0-sunos-x64.tar.gz: No such file or directory
shasum: node-v6.5.0-sunos-x64.tar.xz: No such file or directory
shasum: node-v6.5.0-sunos-x86.tar.gz: No such file or directory
shasum: node-v6.5.0-sunos-x86.tar.xz: No such file or directory
shasum: node-v6.5.0.tar.xz: No such file or directory
shasum: node-v6.5.0-win-x64.7z: No such file or directory
shasum: node-v6.5.0-win-x64.zip: No such file or directory
shasum: node-v6.5.0-win-x86.7z: No such file or directory
shasum: node-v6.5.0-win-x86.zip: No such file or directory
shasum: node-v6.5.0-x64.msi: No such file or directory
shasum: node-v6.5.0-x86.msi: No such file or directory
shasum: win-x64/node.exe: No such file or directory
shasum: win-x64/node.lib: No such file or directory
shasum: win-x64/node_pdb.7z: No such file or directory
shasum: win-x64/node_pdb.zip: No such file or directory
shasum: win-x86/node.exe: No such file or directory
shasum: win-x86/node.lib: No such file or directory
shasum: win-x86/node_pdb.7z: No such file or directory
shasum: win-x86/node_pdb.zip: No such file or directory
... and then it crashes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291#issuecomment-246253180, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvo4SeAkjXcRF8-UMv2iOhYXjE7teks5qpOMdgaJpZM4Jjt0W
.
Regarding wget: Using my wget node package worked really well actually if you're alright with adding that as a dependency.
Regarding shasum: I can try those options.
In other news, I tried building this in Bash on Windows on the new Windows 10 anniversary update and it worked like a charm!
We support Windows!... sort of. haha
Regarding wget: Using my wget node package worked really well actually if you're alright with adding that as a dependency.
In what package are you having the Node.js problems? Is it nodeos-nodejs? If so, being a npm package we could add it as dependency, yes :-) I'm asking this because I'm trying to isolate the generic bits from the npm specific ones, so this way they could be more easily reused (not needing to have Node.js as platform dependency, only bash).
Regarding shasum: I can try those options.
Ok, please tell us your progresses :-)
In other news, I tried building this in Bash on Windows on the new Windows 10 anniversary update and it worked like a charm!
We support Windows!... sort of. haha
Holy sh*t! :-D I've really interested on WS4L since the beginning for this kind of things, that's freaking awesome! :-D Do you have some pics about it? Could you be able to write some text about how to do it (or better, update the readme file ;-) )? How much "Windows like" is this? Could be WS4L considered a native or standard Windows platform, or does it feels a bit alien like OSX MacPorts or Brew? :-)
In what package are you having the Node.js problems? Is it nodeos-nodejs?
Yep nodeos-nodejs
WS4L
So I may have spoken too soon... sorry. npm install didn't error out, but npm start gave me this guy:
root@DESKTOP-BSK1AS7:/mnt/c/Users/Tyler Leonhardt/NodeOS# npm start
> NodeOS@1.0.0-RC2 start /mnt/c/Users/Tyler Leonhardt/NodeOS
> scripts/start
fs.js:1014
return binding.readlink(pathModule._makeLong(path), options.encoding);
^
Error: ENOENT: no such file or directory, readlink 'out/latest'
at Error (native)
at Object.fs.readlinkSync (fs.js:1014:18)
at Object.<anonymous> (/mnt/c/Users/Tyler Leonhardt/NodeOS/scripts/start:11:15)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.runMain (module.js:590:10)
at run (bootstrap_node.js:394:7)
...
root@DESKTOP-BSK1AS7:/mnt/c/Users/Tyler Leonhardt/NodeOS# ls
bin Contributing.md doc Dockerfile LICENSE.txt node_modules npm-debug.log package.json README.md resources scripts vagga.yaml Vagrantfile root@DESKTOP-BSK1AS7:/mnt/c/Users/Tyler Leonhardt/NodeOS#
There doesn't seem to be any out directory... unless I'm looking in the wrong place.
That said... WS4L is really nice :) it actually feels really natural
In what package are you having the Node.js problems? Is it nodeos-nodejs?
Yep nodeos-nodejs
Then I think we could add, do a pull-request :-)
WS4L
There doesn't seem to be any out directory... unless I'm looking in the
wrong place.
Maybe you forgot the 'npm run build'?
That said... WS4L is really nice :) it actually feels really natural
I have read so :-) Is it enabled by default? Could it be considered a
native platform for Windows users?
Maybe you forgot the 'npm run build'?
Yep... I did. I gave that a shot and it instantly failed... Then I realized it was because my directory's path contained a space. There were a few places that this caused an issue.
I tried again from a fresh directory with a path that contains no space characters and it actually seemed to work for a while... until:
Generating nodeos user folder
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:325) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/cp -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/cp
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/ln -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/ln
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/ls -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/ls
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/mkdir -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/mkdir
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/cat -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/cat
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/rm -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/rm
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/mv -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-fs/bin/mv
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/ifconfig -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-ifconfig/ifconfig.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/ip -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-ip/ip.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/man -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-man/man.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/nsh -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-nsh/server.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/pwd -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-pwd/pwd.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/sh -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/bin-sh/sh.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/davius -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/davius/server.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/loadtest -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/loadtest/bin/loadtest.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/testserver-loadtest -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/loadtest/bin/testserver.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/wget -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/node-wget/cli.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/npm -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/npm/bin/npm-cli.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/node-ntp-client -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/ntp-client/bin/node-ntp-client
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/performance -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/performance/bin/performance.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/pstree -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/pstree/server.js
/mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/bin/slap -> /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/slap/slap.js
> bufferutil@1.2.1 install /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/build/nocona/nodeos/lib/node_modules/davius/node_modules/bufferutil
> node-gyp rebuild
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/local/bin/node" "/mnt/c/temp/NodeOS/node_modules/.bin/npm" "run" "build"
npm ERR! node v6.4.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! nodeos-usersfs@1.0.0-RC2 build: `scripts/build`
npm ERR! Exit status 21
npm ERR!
npm ERR! Failed at the nodeos-usersfs@1.0.0-RC2 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-usersfs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-usersfs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-usersfs
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/npm-debug.log
Error compiling ''
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.4.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! NodeOS@1.0.0-RC2 build: `scripts/build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the NodeOS@1.0.0-RC2 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the NodeOS package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs NodeOS
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls NodeOS
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/temp/NodeOS/npm-debug.log
I attempted to just run npm run build again to see if it could fix itself and ended up getting a different error that was cut off dude to my inability to scroll higher up:
genext2fs: device table line 20941 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20942 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20943 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20944 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20945 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20946 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20947 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20948 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20949 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20950 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20951 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20952 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20953 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20954 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20955 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20956 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20957 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20958 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20959 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20960 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20961 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20962 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20963 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20964 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20965 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20966 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20967 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20968 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20969 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20970 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20971 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20972 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20973 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/array/'
genext2fs: device table line 20974 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20975 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20976 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20977 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20978 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20979 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20980 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20981 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20982 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20983 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20984 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20985 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20986 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20987 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20988 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20989 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20990 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20991 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20992 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20993 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/reg-exp/'
genext2fs: device table line 20994 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 20995 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 20996 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 20997 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 20998 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 20999 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21000 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21001 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21002 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21003 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21004 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21005 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21006 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21007 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21008 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21009 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21010 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21011 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21012 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21013 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21014 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21015 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21016 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21017 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21018 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21019 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21020 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21021 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' genext2fs: device table line 21022 skipped: bad format for entry 'nodeos/lib/node_modules/slap/node_modules/npm/node_modules/node-gyp/node_modules/path-array/node_modules/array-index/node_modules/es6-symbol/node_modules/es5-ext/test/string/' ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/out/nocona is mounted.
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/local/bin/node" "/mnt/c/temp/NodeOS/node_modules/.bin/npm" "run" "build"
npm ERR! node v6.4.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! nodeos-usersfs@1.0.0-RC2 build: `scripts/build`
npm ERR! Exit status 42
npm ERR!
npm ERR! Failed at the nodeos-usersfs@1.0.0-RC2 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-usersfs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-usersfs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-usersfs
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/temp/NodeOS/node_modules/nodeos-usersfs/npm-debug.log
Error compiling ''
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.4.0
npm ERR! npm v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! NodeOS@1.0.0-RC2 build: `scripts/build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the NodeOS@1.0.0-RC2 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the NodeOS package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs NodeOS
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls NodeOS
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/temp/NodeOS/npm-debug.log
root@DESKTOP-BSK1AS7:/mnt/c/temp/NodeOS#
We're actually kind of getting there with this. If we can iron these last few issues we will be able to support WS4L :D
Is it enabled by default?
It's not. I think it's not because it's still in Beta and non-tech people don't need it. We'll see if they enable it by default when it hits 1.0 👍 that said, it's really easy to turn on.
Could it be considered a native platform for Windows users?
I think I would say so! It interacts with the same file system so you're able to make changes to your project on your Windows version of Atom and then run it in WS4L. It's really quite nice. It's still a work in progress... but I'm liking their progress!
Then I realized it was because my directory's path contained a space. There were a few places that this caused an issue
Interesting... Have you spotted them? It should be easy (but maybe a bit tedious) to fix by just wrapping the variables with the paths in quotes. If you are not on the shake of it, feel free to open a new issue :-)
npm ERR! nodeos-usersfs@1.0.0-RC2 build: scripts/build npm ERR! Exit status 21
This error is when installing nodeos user packages. It seems bufferutil is the one giving problems... Maybe you can check it standalone?
I attempted to just run npm run build again to see if it could fix itself and ended up getting a different error that was cut off dude to my inability to scroll higher up:
That new one is happening when adding the Ext2 features, that's really strange. Maybe it's not being correctly generated by genext2fs? Don't worry about that previous error lines, I have the error identified and done a patch as it's mostly harmless.
We're actually kind of getting there with this. If we can iron these last few issues we will be able to support WS4L :D
Yeah, it's ironic that the support to build NodeOS on Windows will come before than on OSX, lol :-P
Is it enabled by default?
It's not. I think it's not because it's still in Beta and non-tech people don't need it. We'll see if they enable it by default when it hits 1.0 :+1: that said, it's really easy to turn on.
Yeah, I have read a bit and seems to be just a matter of 5 minutes :-) You need to enable developer mode that definitely is a little big wall, but having some clear instructions on the readme it could work for newcomers :-)
Could it be considered a native platform for Windows users?
I think I would say so! It interacts with the same file system so you're able to make changes to your project on your Windows version of Atom and then run it in WS4L. It's really quite nice. It's still a work in progress... but I'm liking their progress!
My question was more related to how much good is it integrated... I know of cygwin and similar bits that seems to be like a hack and have their own environment. It's mostly about how much big is the "mental switch" to change from Windows environment to WSL and go back, and how much cost to feel a Linux user on WSL (it seems you'll feel at home... :-) )
Interesting... Have you spotted them? It should be easy (but maybe a bit tedious) to fix by just wrapping the variables with the paths in quotes. If you are not on the shake of it, feel free to open a new issue :-)
I can try to dig for them. I'll still open an issue also as a reminder to those contributing to not forget to wrap them in quotes.
Don't worry about that previous error lines
Do you mean the bufferutil problems or the genext2fs problems?
having some clear instructions on the readme it could work for newcomers :-)
I can totally write up instructions when I get this working :)
It's mostly about how much big is the "mental switch" to change from Windows environment to WSL and go back
Well, Bash is a lot different then cmd or PowerShell... so the syntax is a little foreign. That said, I think people who use cmd or PowerShell have an understanding of what a "shell" is... so switching over to bash probably isn't too bad because it's more or less just a change of syntax.
Don't worry about that previous error lines
Do you mean the bufferutil problems or the genext2fs problems?
genext2fs one
having some clear instructions on the readme it could work for newcomers :-)
I can totally write up instructions when I get this working :)
Cool! :-) Probably I'll be one of the first ones to follow them :-P
Well, Bash is a lot different then cmd or PowerShell... so the syntax is a little foreign. That said, I think people who use cmd or PowerShell have an understanding of what a "shell" is... so switching over to bash probably isn't too bad because it's more or less just a change of syntax.
Interesting... and the files are already available on the files explorer, hum... For apps distribution for plain users will be a bit challenguing, isn't it? Or maybe could this improve in the mid-term so final users don't notice difference between "native" Windows apps and WSL ones (at least when they add support for GUI apps...)?
Been busy with work but I'm here :) let me go ahead a kinda grab the important info here and put it in the other issue. I'm going to stop working on OS X building because it's not as far along as WSL if that's cool :)
How far did you get with OSX? If you got some progress we could merge it...
El 26/9/2016 21:27, "Tyler James Leonhardt" notifications@github.com
escribió:
Been busy with work but I'm here :) let me go ahead a kinda grab the
important info here and put it in the other issue. I'm going to stop
working on OS X building because it's not as far along as WSL if that's
cool :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/291#issuecomment-249671811, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvo7bnj8MGkamtfce2WMy0GqO7DvWks5quBy5gaJpZM4Jjt0W
.
Not too much but I'll push the few lines that I changed if you'd like :) I need to double check they still work on Linux.
I need to double check they still work on Linux.
That would be great :-D The CI will check them pass too... :-P
So I guess I'm picking this back up -
NodeOS still fails to compile on my Mac box, but I can't seem to source the error. The logs indicate it's coming from nodeos-cross-toolchain, but when I attempt to install nodeos-cross-toolchain directly, it works fine.
mkdir build-x86_64-cross-darwin16/libcpp
Configuring in build-x86_64-cross-darwin16/libcpp
rm: conftest.dSYM: is a directory
rm: conftest.dSYM: is a directory
configure: error: no usable dependency style found
make: *** [configure-build-libcpp] Error 1
make: *** Waiting for unfinished jobs....
configure: WARNING: cannot check for properly working vsnprintf when cross compiling, will assume it's ok
creating config.m4
Error building ''
rmdir: illegal option -- -
usage: rmdir [-p] directory ...
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/Volumes/NodeOS/NodeOS/node_modules/.bin/npm" "run" "build"
npm ERR! node v7.2.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! nodeos-cross-toolchain@1.0.0-RC3 build: `scripts/build`
npm ERR! Exit status 33
npm ERR!
npm ERR! Failed at the nodeos-cross-toolchain@1.0.0-RC3 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-cross-toolchain package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-cross-toolchain
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-cross-toolchain
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Volumes/NodeOS/NodeOS/node_modules/nodeos-cross-toolchain/npm-debug.log
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/Volumes/NodeOS/NodeOS/node_modules/.bin/npm" "install" "--production"
npm ERR! node v7.2.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! nodeos-cross-toolchain@1.0.0-RC3 install: `scripts/install`
npm ERR! Exit status 10
npm ERR!
npm ERR! Failed at the nodeos-cross-toolchain@1.0.0-RC3 install script 'scripts/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nodeos-cross-toolchain package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nodeos-cross-toolchain
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nodeos-cross-toolchain
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Volumes/NodeOS/NodeOS/node_modules/nodeos-cross-toolchain/npm-debug.log
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/Volumes/NodeOS/NodeOS/node_modules/.bin/npm" "run" "build"
npm ERR! node v7.2.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! libfuse@2.9.8-0 build: `scripts/build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the libfuse@2.9.8-0 build script 'scripts/build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libfuse package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs libfuse
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls libfuse
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Volumes/NodeOS/NodeOS/node_modules/libfuse/npm-debug.log
Also,
src-sockio
src-termios
both cause compilation errors on OSX, but because they're optional, it doesn't break the builds.
| gharchive/issue | 2016-08-13T17:02:48 | 2025-04-01T06:37:19.663274 | {
"authors": [
"joshgarde",
"luii",
"piranna",
"tylerl0706"
],
"repo": "NodeOS/NodeOS",
"url": "https://github.com/NodeOS/NodeOS/issues/291",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
238316018 | reload grid and clear Filter
var deferred = $('.mvc-grid').mvcgrid({
requestType: 'post', // defaults to get
reload: true,
data: {
ClearParameter: ClearFilter,
SBU: $(".ddlSBU").val(),
SegmentCode: $(".ddlSegment").val()
},
reloadEnded: function (grid) {
//$("#mvc-grid-AjaxSearch").val("param=value");
//ClearFilter = false;
}
});
What's your question? What did you try and what doesn't work?
i want clear filter and sort after reload grid
Clear it from the UI or server side?
If you are using your own filter data to query the models it should already be reset.
You can also disable them through grid configuration .Sortable(false) and .Filterable(false).
Did you managed to clear it?
| gharchive/issue | 2017-06-24T12:59:33 | 2025-04-01T06:37:19.696176 | {
"authors": [
"Muchiachio",
"thewinner55"
],
"repo": "NonFactors/MVC5.Grid",
"url": "https://github.com/NonFactors/MVC5.Grid/issues/93",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1086048998 | Fix Integration tests for Problem Index functionality
Fix integration tests for Problem Index page.
@evulins
where now we should component inputWithTags?
What do you mean? Where should we test it? :)
What I meant is that I wrote two tests in the previous test file for the pseudo inputWithTags component. And because of our mechanism structure they didn't work properly. Right now they are missing :D And I wonder if it's on purpose and if yes should we test it somewhere else?
@evulins oh, sure, I just forgot, I will paste them here, as because of the mechanics the also belong here. :)
👌 Nice!
| gharchive/pull-request | 2021-12-21T17:16:08 | 2025-04-01T06:37:19.700679 | {
"authors": [
"bazelajoanna",
"evulins",
"franiakat"
],
"repo": "Nontrivial-Things/thinking_classrooms_client",
"url": "https://github.com/Nontrivial-Things/thinking_classrooms_client/pull/29",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
161069186 | error when load config file in java
I get that error when trying to load the config file
`SEVERE: Servlet.service() for servlet [tasks] in context with path [/Crawler_NORCQNEX] threw exception [Servlet execution threw an exception] with root cause
java.lang.NoClassDefFoundError: com/norconex/collector/core/CollectorConfigLoader
at servlets.Tasks.doPost(Tasks.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
`
and that is the code of it
HttpCollectorConfig config = (HttpCollectorConfig) new CollectorConfigLoader(HttpCollectorConfig.class).loadCollectorConfig(configFile); HttpCollector collector = new HttpCollector(config);
I make sure that jar of this class is imported!!
Do you have that issue when you run it standalone?
It seems your webapp could not find that class so it looks like a classpath/classloading issue with your webapp.
As a side note, you may want to know the HTTP Collector is meant to be run in isolation/standalone (live and die with the JVM). The crawling/parsing of some files can be quite resource intensive sometimes and running it in a webapp may compromize the webapp stability and will likely not work as you expect. If you really want to run it in a web app, I recommend you launch the Collector as an external process. You are of course welcome to experiment. :-)
Thank you for your reply, but what do you mean is that I can't use the library inside my code ?
Of course not! You can use the library with your code. I was simply sharing what type of usage works best to save you trouble. The problem you have (NoClassDefFoundError) is likely not one of the HTTP Collector, but rather one of the library not being found by your Java app. You'll have to troubleshoot why your webapp (Tomcat) does not load some Jars/classes (assumming you've included all dependencies in your web app).
It works now! I added these jars to deployment classpath.. thanks a lot
| gharchive/issue | 2016-06-19T11:49:39 | 2025-04-01T06:37:19.731735 | {
"authors": [
"doaa-khaled",
"essiembre"
],
"repo": "Norconex/collector-http",
"url": "https://github.com/Norconex/collector-http/issues/263",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
450141780 | window.document.hasFocus instead of window.hasFocus?
It could potentially be a setting. But I think that it's better to show notification, if possible. Because user may be at a different tab in the same window?..
Seems sane.
| gharchive/pull-request | 2019-05-30T05:49:07 | 2025-04-01T06:37:19.741150 | {
"authors": [
"Wikiwide",
"marcusramberg"
],
"repo": "Nordaaker/convos",
"url": "https://github.com/Nordaaker/convos/pull/383",
"license": "Artistic-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2173632191 | Error Decoding Response Body
Not entirely sure what this is or what the issue is caused by, but Moruke's skin causes skindl to fail:
Test case: https://gamebanana.com/mods/481891
Can only reproduce on the first file (moruke_omura_red_.zip), which returns a broken response from the GameBanana API:
The other download links (which contain ID 481891 instead of 481890) work correctly, and properly contain the first file:
This is a GameBanana bug, nothing I can do to fix it. Select one of the other 1-Click Install buttons to download the mod.
| gharchive/issue | 2024-03-07T11:23:08 | 2025-04-01T06:37:19.800430 | {
"authors": [
"MagicalWitchAshley",
"NotNite"
],
"repo": "NotNite/skindl",
"url": "https://github.com/NotNite/skindl/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1063904855 | dailyjournal idea question improvements
i had an idea to improve the dailyreview questions.
also I talked to @jgclark a few days ago about the ideas.
here is now my PR with little improvements of the review questions.
now you can add subheading, which aren't rendered as commandbar questions but then with ### in the final note
additionally you can create bulletpoints
just read my README adjustments - I hope you understand what I did :D
i pushed the PR rework commit.
you can hardly see this here in the GitHub conversation
This sounds interesting, but will be a little hard for users to follow. Maybe you can make a short video of how this piece works and put that in the README?
On Thu, Nov 25, 2021 at 1:23 PM, Michael Wellner < @.*** > wrote:
i pushed the PR rework commit.
you can hardly see this here in the GitHub conversation
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (
https://github.com/NotePlan/plugins/pull/122#issuecomment-979474432 ) , or
unsubscribe (
https://github.com/notifications/unsubscribe-auth/ACEI6VEUR4OH3GVPZQ44HXLUN2SNXANCNFSM5IZIVZBQ
).
This sounds interesting, but will be a little hard for users to follow. Maybe you can make a short video of how this piece works and put that in the README?
…
hm ok how can I create this video? never done that before :D
I've tidied up the README a little more, removed the bold around the mood answer, and did some other changes ready for changes to the framework that you're probably not aware of yet. I will now publish this update.
You can still add bold around the mood output in your personal settings, but I don't want to force it on everyone else.
Look at Loom. It’s free.
Here’s a @jgclark video. But yours could be super short and focus on how u
use these new additions.
https://youtu.be/IWjr0dy3JhM https://youtu.be/IWjr0dy3JhM?t=115
On Thu, Nov 25 2021 at 1:52 PM, Michael Wellner @.***>
wrote:
This sounds interesting, but will be a little hard for users to follow.
Maybe you can make a short video of how this piece works and put that in
the README?
… <#>
hm ok how can I create this video? never done that before :D
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NotePlan/plugins/pull/122#issuecomment-979483399, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEI6VBSFWYZTEV7NTGXVPDUN2VYDANCNFSM5IZIVZBQ
.
| gharchive/pull-request | 2021-11-25T20:29:00 | 2025-04-01T06:37:19.810284 | {
"authors": [
"dwertheimer",
"jgclark",
"m1well"
],
"repo": "NotePlan/plugins",
"url": "https://github.com/NotePlan/plugins/pull/122",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2311281117 | Unlinked note finder
Searches through notes and find unlinked references to other note plan notes.
TODO
Add an action log note.
@aaronpoweruser This is great stuff. Thanks Aaron!
Question...what would you think about doing this as a PR against the np.Tidy plugin which has a command:
/List stubs: creates a note that lists all your notes that have wikilinks that lead nowhere.
Or is there a reason why you think this needs to be a free-standing plugin?
No strong preference as to where this lives. I was unsure if it should be in tidy, note helpers or its own plugin.
I'm going to keep iterating on the code here, once I'm happy with it I'll move it to wherever makes the most sense.
@aaronpoweruser I'm not yet sure what "unlinked references" are. But, yes, I agree that it sounds like a good candidate for NoteHelpers or Tidy. The former is more for things run on a particular note; the latter does things that run over all notes, or all recent notes.
Note helpers it is I'm thinking about removing the large global search after switching to regex parsing the performance unacceptable it takes tens of minutes to scan the entire note database. So the plug-in will only work on note at a time.
Once I finish up the code, I'll clean the documentation. The plug-in essentially scans are a given note and finds keywords that should link to other notes that are unlinked. It then creates a [[]] link to the found note.
My use cases is using voice dictation and having to go back in manually create a [[]] link to another note. this just automated the process.
I'll add on save trigger as well, so it should be fully automated
I'm happy with this now. Feel free to take a look at it.
I still need to add good public documentation and move to note helpers give me a few days
@jgclark Can you review please so I can merge and release.
@aaronpoweruser I'm confused. I've had a notification that you've done something new with this PR, but I can't see anything that's changed. Please advise.
Ive just been reponding to comments. new PS incoming.
Been using the new regex for the past week, with voice dictation and a on save tigger. On my notes my runtime has been sub 15ms consistently (Np writing the note to disk takes ~5ms). Its fast enough where I rarely tag notes by hand now.
I still need to record a new demo gif, but i'm happy with the code.
Old regex logic:
New regex:
Was a worthwhile effort, i'm finally comfortable with regexs.
I'm releasing 0.19.2 with some bug fixes. We can release 0.20.0 once you have the documentation updates for this.
| gharchive/pull-request | 2024-05-22T19:02:13 | 2025-04-01T06:37:19.818869 | {
"authors": [
"aaronpoweruser",
"dwertheimer",
"jgclark"
],
"repo": "NotePlan/plugins",
"url": "https://github.com/NotePlan/plugins/pull/572",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
300769663 | In build.ps1 scripts that fetch from ServerCommon, set SSL protocols
A lot of machines default to SSL 3.0 and TLS 1.0, which is not compatible with GitHub.
System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()
Workaround is to run this on your machine:
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
| gharchive/issue | 2018-02-27T19:52:29 | 2025-04-01T06:37:19.854620 | {
"authors": [
"joelverhagen"
],
"repo": "NuGet/NuGetGallery",
"url": "https://github.com/NuGet/NuGetGallery/issues/5551",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2677375508 | Working with new datasets
Does it support working with new Datasets?
if I am trying to work with
real_dataset = load_dataset("bitmind/AFHQ")
fake_dataset = load_dataset("bitmind/AFHQ___RealVisXL_V4.0")
How shall I setup the folder structure, a bit confused here
Guidance for using custom datasets has been added to the README. You can find it in section "Custom Dataset" under "Download Dataset".
| gharchive/issue | 2024-11-20T22:36:30 | 2025-04-01T06:37:19.866694 | {
"authors": [
"JaynouOliver",
"NuayHL"
],
"repo": "NuayHL/TimeStepGenerating",
"url": "https://github.com/NuayHL/TimeStepGenerating/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2751630176 | 🛑 Linkwarden is down
In 99c327d, Linkwarden (https://links.grobecker.me) was down:
HTTP code: 502
Response time: 3522 ms
Resolved: Linkwarden is back up in eb59213 after 5 minutes.
| gharchive/issue | 2024-12-19T23:54:40 | 2025-04-01T06:37:19.874562 | {
"authors": [
"Nugget2269"
],
"repo": "Nugget2269/ubiquitous-octo-carnival",
"url": "https://github.com/Nugget2269/ubiquitous-octo-carnival/issues/108",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1665534326 | FATAL: Error, the Windows SDK must be installed in Visual Studio.
Hey, so ive seen this issue like twice here, unfortunately reading through neither of them fixed it for me.
When I run py -m nuitka --version I get the following:
1.5.4
Commercial: None
Python: 3.10.2 (tags/v3.10.2:a58ebcc, Jan 17 2022, 14:12:15) [MSC v.1929 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Users\Admin\AppData\Local\Programs\Python\Python310\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\cl.exe (cl 14.0).
I installed basically all windows SDKS inside Visual Studio, its still telling me that theyre missing.
I installed nuitka via pip, python is standart cpython and installed via the official website.
I do use a venv to execute the command
I use a fair amount of packages in my project, but I dont think thta would be the problem as it compiles alright with the standart compiler, but I would like to use clang
I execute py -m nuitka main.py --onefile --plugin-enable=pyside6 --nofollow-import-to=tkinter --windows-uac-admin --clang
As you can see, ive tried basically every install:
Update: I tried to update nuitka to the most recent version, exact same issue.
So your version output shows you are using the community version, and your screenshot is for build tools.
@kayhayen could you clarify? And I apologize for sending the build tools, the normal tab basically looks the same though, all SDKs installed
So your version output shows you are using the community version.
Indeed I am, but the projects description states:
Visual Studio 2022 or higher on Windows, older versions will work but only supported for commercial users.
(the community editions work just fine)
So why is the community version not going to work?
Thank you very much for your time!
It is working fine. I notice a (2) in your screenshot title. Does that mean you have two of them installed? You might have previously bee using stuff that auto-installs things. I once tried to make Nuitka auto-install MSVC to its private parts with the correct components, but failed to do unfortunately. I think I saw these numbers in that case. You may want to configure the correct one.
Oh yea, that (2) is weird! I'll see what I can find about that.
Yes, you can waste my time.
| gharchive/issue | 2023-04-13T01:43:56 | 2025-04-01T06:37:19.880277 | {
"authors": [
"kayhayen",
"kennyhml"
],
"repo": "Nuitka/Nuitka",
"url": "https://github.com/Nuitka/Nuitka/issues/2166",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2458579837 | Nuitka Module Importing External Numba .so file
Nuitka Version 2.4.5, Python version 3.12.0
I am stuck on a question of having a Nuitka .so module import code outside of the module package that is compiled, specifically I want the compiled code inside a nuitka-ized module to reference code in a numba AOT-ized module.
Thanks for the help in advance. I am trying to work around using both numba and nuitka for my project. See the project structure below:
└── 📁nuitka_testing
└── run_func.py
└── 📁.venv
└── 📁src
└── 📁nuitka_funcs
└── __init__.py
└── test_nuitka_imports.py
└── numba_modules.cpython-312-x86_64-linux-gnu.so
└── __init__.py
I have used numba's AOT capabilities to create numba_modules.cpython-312-x86_64-linux-gnu.so which houses all my numba code, which I then import in nuitka_funcs/test_nuitka_imports.py, the content of which is below:
## test_nuitka_imports.py ##
from ..numba_modules import identity
def run(x):
y = identity(x)
return y
I can run my main function run_func.py (simply from src import run; run(5) ) when the nuitka_funcs folder is not compiled, but when i try to compile the nuitka_funcs folder into a .so using python -m nuitka --module nuitka_funcs --include-package=nuitka_funcs I get an assertion error AssertionError: <ModuleName ''>, crash report is attached:
nuitka-crash-report.txt
I gather it is because the code being compiled in the nuitka_funcs folder is importing code outside itself? If anyone could please help out on the right direction it'd be most appreciated. I just want to be able to reference outside, non-compiled code from inside a nuitka-ized .so module file, or any work-around for this use case. I have looked through other issues and they are either too vague to help me or don't seem to help me.
Thank you!
The example looks good to me, I will be trying to add Numba JIT support in the coming releases, so this will be useful as a starting point at least, before we see what larger packages also do.
| gharchive/issue | 2024-08-09T19:55:09 | 2025-04-01T06:37:19.886113 | {
"authors": [
"kayhayen",
"pveikos"
],
"repo": "Nuitka/Nuitka",
"url": "https://github.com/Nuitka/Nuitka/issues/3058",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1491417215 | User Manual: Escape backslashes in Windows paths
What does this PR do?
This PR makes a minor correction to the User Manual - the back-slashes in the Windows file paths in the table on use-case 4 were not escaped, so were not visible when the page was rendered.
Why was it initiated? Any relevant Issues?
It was initiated because I was reading the User Manual and noticed missing back-slashes in the Windows file paths in the table on use-case 4.
PR Checklist
[x] Correct base branch selected? Should be develop branch.
[x] Enabled commit hook or executed ./bin/autoformat-nuitka-source.
[x] All tests still pass. Check the Developer Manual about Running the Tests.
There are GitHub Actions tests that cover the most important
things however, and you are welcome to rely on those, but they might not
cover enough.
[x] Ideally new features or fixed regressions ought to be covered via new tests.
[x] Ideally new or changed features have documentation updates.
Thanks for fixing this, very good.
| gharchive/pull-request | 2022-12-12T09:33:45 | 2025-04-01T06:37:19.889472 | {
"authors": [
"joouha",
"kayhayen"
],
"repo": "Nuitka/Nuitka",
"url": "https://github.com/Nuitka/Nuitka/pull/1930",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
831056945 | Feature cli tokens
Improved token admin script in auth and fixed bug in useradd script in users. Also added some readme info about using oadadeploy as an option for installation.
It isn’t “hanging,” I’m guessing you didn’t pass any args and are probably running it with docker instead of docker-compose and probably forgot to pass “-it” to docker. The script prompts you for anything that wasn’t passed: I.e. if you gave no username, it prompts you for one. If you use docker and forget the “-it”, then you never see the prompt and can’t type the answer so it looks like it is hanging when it’s really just waiting for a username on stdin. Running it with docker-compose doesn’t require that you explicitly allocate a tty, so no extra flag necessary.
I want it to operate that way because you don’t have to memorize the flags in order to just add a user. I kept testing it and couldn’t figure out why it wouldn’t prompt me for any of the missing items until I saw that condition.
Aaron
Sent from my iPhone
On Mar 14, 2021, at 8:30 PM, Alex Layton @.***> wrote:
@awlayton commented on this pull request.
In oada/services/users/useradd.js:
@@ -28,7 +26,7 @@ async function findUserByUsername(username) {
// The main event:
async function run() {
try {
if (argv.h || argv.help || Object.keys(argv).length <= 1) {
Why did you remove this condition? It was to fix it hanging if called with no arguments. With this change it hangs for me again.
In oada/services/permissions-handler/server.js:
@@ -88,6 +96,10 @@ responder.on('request', function handleReq(req) {
responder.scopes = { read: true, write: true };
} else {
// Check for read permission
if (!req.scope || !req.scope.some) {
Why not just use Array.isArray?
In oada/services/auth/token.js:
@@ -0,0 +1,139 @@
+const argv = require('minimist')(process.argv.slice(2));
+const cloneDeep = require('clone-deep');
+const chalk = require('chalk');
+const uuid = require('uuid');
+const { authorizations, users } = @.***/lib-arangodb');
+
+if (!process.env.DEBUG) {
process.env.DEBUG = 'token:info,token:error';
A CLI tool should just be directly printing anything for user interaction rather than forcing debug to display it,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Yes I intentionally passed no arguments. I agree you should not have to remember the flags, but for me nothing happened when I ran it with no args so I made it print the help and exit.
What do you mean pass -it? Those are not flags for docker-compose run which is how I was running it.
To be clear, when I ran docker-compose run users add it never exited or printed anything. So I added that check.
You should use oadadeploy instead so you don’t have to remember docker details :). “oadadeploy admin useradd "
If you don’t want to use the oadadeploy script, then:
If users is running, simplest is to use exec: docker-compose exec users yarn run add
Otherwise, if you try “run” but you use it normally instead of by replacing the entrypoint w/ yarn, it will start a second users process listening and responding to Kafka.
Aaron
On Mar 15, 2021, at 9:56 PM, Alex Layton @.***> wrote:
Merged #83 https://github.com/OADA/oada-srvc-docker/pull/83 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/OADA/oada-srvc-docker/pull/83#event-4461892320, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2KEUH2A5MAEHSHI3GYYS3TD23ENANCNFSM4ZEQTZHA.
No, docker-compose run users add should work. If it does not work the wait it is, it needs to be changed. With that condition in it works for me when I supply flags.
Using run does not start another instance of the users service unless you are doing so in the useradd.js file.
Wouldn’t your entrypoint have to be yarn in order for that to work?
Aaron
On Mar 16, 2021, at 12:46 AM, Alex Layton @.***> wrote:
No, docker-compose run users add should work. If it does not work the wait it is, it needs to be changed. With that condition in it works for me when I supply flags.
Using run does not start another instance of the users service unless you are doing so in the useradd.js file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/OADA/oada-srvc-docker/pull/83#issuecomment-799944143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2KEUFNDC6EJVBVHF2UYE3TD3PD5ANCNFSM4ZEQTZHA.
It is already
https://github.com/OADA/oada-srvc-docker/blob/c4688206138f841bdf081c827e3cbebeb7b88ba8/oada/utils/entrypoint.sh#L3
| gharchive/pull-request | 2021-03-14T03:44:02 | 2025-04-01T06:37:19.937594 | {
"authors": [
"abalmos",
"aultac",
"awlayton"
],
"repo": "OADA/oada-srvc-docker",
"url": "https://github.com/OADA/oada-srvc-docker/pull/83",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
1127678673 | 2022-02-08-Websockets
As a follow up to #55, I'm adding a proposal for Websocket support. If this is not the right channel to do so, please let me know what's the official way of opening a proposal, as I don't see it in any of the docs, and I don't have the proposals folder when I forked the repo.
Find the filled proposal template below:
WebSockets
Metadata
Tag
Value
Proposal
2022-02-08-Websockets
Authors
Balazs Edes
Review Manager
TBD
Status
Proposal
Implementations
-
Issues
#55
Previous Revisions
-
Change Log
Date
Responsible Party
Description
2022-02-08
Balazs Edes
First draft created
Introduction
This proposal aims to make WebSocket api descriptions part of OpenAPI.
Motivation
Currently the OpenAPI standard is limited to describing what the http standard allows. More and more applications make use of WebSockets, which is a simple and standard way to build event driven systems, and runs in the most important platform end users see: the browser. Since there is demand for it, I propose to add the ability to describe WebSockets in OpenAPI schemas, as HTTP/WebSocket apis often complement each other.
There are other initiatives to describe event driven messaging (eg.: AsyncAPI), but in terms of maturity I haven't seen anything close to OpenAPI. AsyncAPI is also trying to acomplish a wide array of other goals which delay it's maturity further. Looking at the traction that #55 gained over the years, I think it would be a reasonable goal to add the ability to describe WebSockets in OpenAPI.
Proposed solution
This proposal aims to add a new WebSocket Payload Object type to the spec, and 2 additional fields to the Operation Object, publish and subscribe (better name suggestions are wellcome), that would allow us describing how to connect to a ws server, and what messages can we expect to receive or send.
Example
openapi: '3.3.0'
paths:
/sample-socket:
get:
operationId: 'sampleSocket'
publish:
description: 'Short description about the messages you can push towards the server'
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/CreateUserSchema'
- $ref: '#/components/schemas/DeleteUserSchema'
- $ref: '#/components/schemas/LikePostSchema'
subscribe:
description: 'Short description about the messages you can receive from the server'
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/UserCreatedSchema'
- $ref: '#/components/schemas/UserDeletedSchema'
- $ref: '#/components/schemas/PostLikedSchema'
Detailed design
The WebSocket spec is currently very simple. From our point of view it allows:
Connecting to an endpoint using a URL
Sending messages in either binary or text format
Receiving messages in either binary or text format
This proposal aims to allow OpenAPI users to describe exactly the above mentioned points:
What URL can I connect to, to talk to this WebSocket?
What's the format and shape of data I'm allowed to send
What's the format and shape of data I can expect to receive
Important: This OpenAPI spec proposal doesn't concern itself with any frameworks, or any higher level abstractions people usually build on top of event driven messaging protocols, like topics/subjects/channels, implied message serialization, etc. It simply describes the above mentioned 3 points, and any further abstractions can be built on top of this, but not part of the core schema.
Extension of the current OpenAPI spec
Add a WebSocket Payload Object type (very similar to Request Body Object, except the required field - which makes no sense here). It has the following fields:
description: string - A brief description of the payload.
content: Map[string, Media Type Object] The content of the payload.
Add an optional field in the Components Object type, so payloads can be reused:
webSocketPayloads: Map[string, WebSocket Payload Object] - Reuseable payloads
Add 2 optional fields on the Operation Object type:
publish: Reference Object | WebSocket Payload Object - describes the message(s) the client can publish/push to the server.
subscribe: Reference Object | WebSocket Payload Object - describes the message(s) the client can receive from the server.
Simple chat example
openapi: '3.3.0'
components:
schemas:
ChatMessage:
type: 'object'
required:
- 'from'
- 'to'
- 'message'
properties:
from:
type: 'string'
to:
type: 'string'
message:
type: 'string'
paths:
/chat-using-socket:
get:
operationId: 'chatSocket'
publish:
description: 'You can publish chat messages to this server'
content:
application/json:
schema:
$ref: '#/components/schemas/ChatMessage'
subscribe:
description: 'You can expect chat messages from the server'
content:
application/json:
schema:
$ref: '#/components/schemas/UserCreatedSchema'
Simple chat, but reusing payloads
openapi: '3.3.0'
components:
schemas:
ChatMessage:
type: 'object'
required:
- 'from'
- 'to'
- 'message'
properties:
from:
type: 'string'
to:
type: 'string'
message:
type: 'string'
webSocketPayloads:
ChatMessagePayload:
description: 'A chat message payload'
content:
application/json:
schema:
$ref: '#/components/schemas/ChatMessage'
paths:
/chat-using-socket:
get:
operationId: 'chatSocket'
publish:
$ref: '#/components/webSocketPayloads/ChatMessagePayload'
subscribe:
$ref: '#/components/webSocketPayloads/ChatMessagePayload'
Multiple message types
Note since channels/topics/subjects cannot be expressed we can use a union type with a discriminator to mimic this.
openapi: '3.3.0'
components:
schemas:
CreateUserSchema: '...'
DeleteUserSchema: '...'
LikePostSchema: '...'
PublishMessageSchema:
discriminator:
propertyName: 'action'
mapping:
CreateUser: '#/components/schemas/CreateUserSchema'
CreateUser: '#/components/schemas/CreateUserSchema'
LikePost: '#/components/schemas/LikePostSchema'
oneOf:
- $ref: '#/components/schemas/CreateUserSchema'
- $ref: '#/components/schemas/DeleteUserSchema'
- $ref: '#/components/schemas/LikePostSchema'
UserCreatedSchema: '...'
UserDeletedSchema: '...'
PostLikedSchema: '...'
SubscribeMessageSchema:
discriminator:
propertyName: 'type'
mapping:
UserCreated: '#/components/schemas/UserCreatedSchema'
UserDeleted: '#/components/schemas/UserDeletedSchema'
PostLiked: '#/components/schemas/PostLikedSchema'
oneOf:
- $ref: '#/components/schemas/UserCreatedSchema'
- $ref: '#/components/schemas/UserDeletedSchema'
- $ref: '#/components/schemas/PostLikedSchema'
paths:
/sample-socket:
get:
operationId: 'sampleSocket'
publish:
description: 'Short description about the messages you can push towards the server'
content:
application/json:
schema:
- $ref: '#/components/schemas/PublishMessageSchema'
subscribe:
description: 'Short description about the messages you can receive from the server'
content:
application/json:
schema:
- $ref: '#/components/schemas/SubscribeMessageSchema'
Backwards compatibility
As this change is additive (nothing is removed or modified in a non-backward compatible way) I don't see any backward compatibilty issues.
Alternatives considered
There can be many alternatives, my motivation was to add support for WebSocket api descriptions, while
Adding as few new concepts as possible
Allowing reuse the same way as with all other parts of the schema, through $refs
Just describing what the standard allows (no frameworks)
Not causing any breaking changes or backward compatibility issues
I'm happy to take onboard any suggestions, alternatives, modifications to this! I'm sure there are many things I haven't thought of.
| gharchive/issue | 2022-02-08T19:38:04 | 2025-04-01T06:37:19.957529 | {
"authors": [
"bali182"
],
"repo": "OAI/OpenAPI-Specification",
"url": "https://github.com/OAI/OpenAPI-Specification/issues/2880",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
211085719 | Clarify thinking behind .example object and .examples array ?
Please could someone provide some background on the decision to have both .example and .examples[] properties on the requestBody, responses and schemas?
It seems to me this might unnecessarily complicate documentation tooling, while the alternative is simply using a one-element array if only one example is provided. Extending an existing definition with a single example would involve more editing when adding a second one.
An operation object does not have both a .tag and .tags[] properties.
I also found the following wording confusing:
SHOULD be in the correct format as specified [in the] parameter encoding
I'm probably missing something.
From my perspective there wasn't a strong motivation for keeping the "example" property. It was primarily for simplicity and backward compatibility. We have added a fair amount of complexity to some objects, there was some reluctance to force example arrays on everyone.
We have made examples and example mutually exclusive, so for tooling it shouldn't be much more than an extra if statement to handle both properties.
The examples/example have been added to the content object, so when tooling people implement it, it will automatically work for requestBody, responses, callbacks, links, complex parameters.
The example has been left in for schemas. Maybe that isn't needed any more now that example objects are now reusable components.
It is possible there could be some streamlining, but if we were to remove example I think it would be more for reducing conceptual complexity, rather than making tooling easier.
@MikeRalphson does that answer your question? If so please close...
@fehguy @darrelmiller Thanks for the response. I would however question the need for "backwards compatibility" when there has explicitly been a breaking change in the version of the specification.
There seems to be no other examples of such mental backwards compatibility around servers, requestBodies etc.
I'm not wholly convinced by the simplicity argument either I'm afraid, there is one spec to create, but many tools, each of which would have to take this wrinkle into account.
If it looks like a wart, and sounds like a wart...
If it is unlikely to change, or is still up for consideration outside the public sphere of GitHub issues, then yes, please close.
Well this was actually requested and should hopefully be captured in the issues. Certainly nobody was creating work just for the sake of creating work.
I'll have a hunt through the issues.
Certainly nobody was creating work just for the sake of creating work.
I hope I didn't come off as remotely suggesting that.
No problem at all. I believe the examples arguments were around the requestBody changes
Looks like Issue 800 is the most relevant. In which @DavidBiesack expressed a preference for the oneOf example / examples. I could find no other requests for this specific feature in the issues.
I'll just chime in that my preference is strictly for ease of use of the API author. I think many cases one example is sufficient and using example: is very easy whereas using examples: and coding an array is just more tedious. I think tooling can pretty easily account for this and do the transformation for us; that's what computers are good at. Again, this is just my preference - -I tend to side on ease of use for people using OAS.
Understood, but I still contend that it doesn't smell like any other part of the OpenAPI 3 spec. ;)
It is a personal preference, I'm not strongly opposed to more uniform implementation (i.e. just examples: [ ]). (I do not think that preserving singular example: syntax just because it was singular in 2.0 is important here.)
I agree with @MikeRalphson. To me this seems overly verbose when a single item examples array would suffice. If the argument for having both is for 'backwards compatibility' then I think this needs to be revisited since 3.0 is strictly not compatible with 2.0. I would argue the cognitive load of understanding the difference outweighs any tediousness of coding an array (literally adding a - in yaml, json slightly more work sure).
| gharchive/issue | 2017-03-01T13:47:21 | 2025-04-01T06:37:19.968642 | {
"authors": [
"DavidBiesack",
"MikeRalphson",
"darrelmiller",
"fehguy",
"willdady"
],
"repo": "OAI/OpenAPI-Specification",
"url": "https://github.com/OAI/OpenAPI-Specification/issues/953",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1938772253 | Hapi 131 bugfixes
Lots of debugging here, had to:
update the reqs to use the latest hapi-schema
run the pg_dump command from the docker container
add the HDX API key
I guess the hapi-pipelines Dockerfile and publish workflow are redundant?
@mcarans I think publish will not be needed as I don't think we'd need to publish to PyPI. The dockerfile could be kept until we see exactly what we need for V2. What do you think?
| gharchive/pull-request | 2023-10-11T21:29:06 | 2025-04-01T06:37:20.106565 | {
"authors": [
"turnerm"
],
"repo": "OCHA-DAP/hapi-pipelines",
"url": "https://github.com/OCHA-DAP/hapi-pipelines/pull/46",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1346415068 | dhcp: adds test about leasetime keyword
Replaces #873
I want to build on it for other DHCP keywords ;-)
cf https://redmine.openinfosecfoundation.org/issues/5506
Closing in favor of #919 now that recent Suricata PR has been merged
| gharchive/pull-request | 2022-08-22T13:20:22 | 2025-04-01T06:37:20.357632 | {
"authors": [
"catenacyber"
],
"repo": "OISF/suricata-verify",
"url": "https://github.com/OISF/suricata-verify/pull/913",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
742942972 | Still active ?
The latest changes are three years old and recently lots of issues were closed without any explanation.
Is this project still active? If not: can this please be stated at the top of the README ?
The project is not active anymore, as Open Knowledge Austria does not exist anymore for more than 2 years. Started a new project from scratch 2 weeks ago, you can find here: https://github.com/skasberger/owat_api
You could add that information here:
https://github.com/OKFNat/offenewahlen_api
| gharchive/issue | 2020-11-14T06:38:49 | 2025-04-01T06:37:20.411276 | {
"authors": [
"akuckartz",
"skasberger"
],
"repo": "OKFNat/offenewahlen_api",
"url": "https://github.com/OKFNat/offenewahlen_api/issues/234",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2586760926 | Peer Review - SRS: Could add context diagram
Artifact Under Review
SRS Document
Team Number for Team Doing the Review
Team 10
Description of Issue
Within section 6.2. The Context of the Work, you could potentially add a context diagram to outline how external entities interact with an internal software system. (I'm not sure if it's required for your case but it was required for the scientific computing template and I saw a previous group example add it as part of their revision 1, section 4.1.1.) It could be helpful to give the reader a more abstract understanding of the system before diving into the use case diagram.
Team 10 TA: @Necried
| gharchive/issue | 2024-10-14T18:32:14 | 2025-04-01T06:37:20.414189 | {
"authors": [
"angelaw7"
],
"repo": "OKKM-insights/OKKM.insights",
"url": "https://github.com/OKKM-insights/OKKM.insights/issues/123",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
230520733 | Nextcloud 12's new editable public links should open docs with OnlyOffice
Nextcloud 12 now allows public link shares to be writable, so that a user can share a document with a non-Nextcloud user and have them jump into the editor. This functionality is advertised for use with Collabora/CODE, but I imagine OnlyOffice could use it as well.
Hello @steampoweredlawngnome
The issue has already been discussed earlier https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues/20
| gharchive/issue | 2017-05-22T21:10:52 | 2025-04-01T06:37:20.426762 | {
"authors": [
"JohnPerkin",
"steampoweredlawngnome"
],
"repo": "ONLYOFFICE/onlyoffice-owncloud",
"url": "https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues/71",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
682576780 | 1221 Search for case and show results
Motivation and Context
The first feature needed for ops-ui is to be able to search for cases via a postcode. This PR adds that functionality as well as IAP Audit logging and adding the CDN to ops-ui.
What has changed
Search for cases via postcode
IAP audit logging
Added flask/jinja templates to show postcode results.
Added Flask blueprints for routing
Now runs with Gunicorn
How to test?
Run with the other branches on the ticket. When you have cases in your database, you should be able to run the ops-ui and find cases with a postcode.
Try running this in your GCP environment and see if you can connect to it.
Anyone testing I can add to the IAP so you could try and connect to the domain set up in census-rm-ryangrundy
Links
Trello
Missing columns, specified in the acceptance criteria (although I personally think it's far too many):
org name
case type
estab type
UPRN
region
@NickGrantONS Org name is part of the address summary that gets put into the table. Estab type and case type are included in the page. UPRN and Region aren't in the prototype that we were basing this on. Could be a question for Dan if they need to be included
| gharchive/pull-request | 2020-08-20T09:46:19 | 2025-04-01T06:37:20.435761 | {
"authors": [
"AdamHawtin",
"ryangrundy7"
],
"repo": "ONSdigital/census-rm-ops-ui",
"url": "https://github.com/ONSdigital/census-rm-ops-ui/pull/3",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.