The tests defined in passthru.tests, if any, passed
found 0.41.3 with grep in /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.3
found 0.41.3 in filename of file in /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.3
Rebuild report (if merged into master) (click to expand)
```
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
geesefs
```
Instructions to test this update (click to expand)
---
Either **download from Cachix**:
```
nix-store -r /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.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 geesefs https://github.com/r-ryantm/nixpkgs/archive/2ed0caae234def089c1149a71112db25ba07ff59.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/2ed0caae234def089c1149a71112db25ba07ff59#geesefs
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.3
ls -la /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.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.
[!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.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yandex-cloud/geesefs/releases.
meta.description for geesefs is: Finally, a good FUSE FS implementation over S3
meta.homepage for geesefs is: https://github.com/yandex-cloud/geesefs
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath geesefs ```Instructions to test this update (click to expand)
--- Either **download from Cachix**: ``` nix-store -r /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.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 geesefs https://github.com/r-ryantm/nixpkgs/archive/2ed0caae234def089c1149a71112db25ba07ff59.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/2ed0caae234def089c1149a71112db25ba07ff59#geesefs ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.3 ls -la /nix/store/hx6pi4hlyavqcmj9gwyfiq9crlg4p5gj-geesefs-0.41.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-reviewrun on x86_64-linux 11 package built:
Maintainer pings
cc @flokli for testing.
Add a :+1: reaction to pull requests you find important.