Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bozohttpd 20240126 -> 20260503 https://repology.org/project/bozohttpd/versions
attrpath: bozohttpd
Checking auto update branch...
No auto update branch exists
[version]
[version] updated version and sha256
[rustCrateVersion]
[rustCrateVersion] No cargoHash found
[golangModuleVersion]
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/by-name/bo/bozohttpd/package.nix b/pkgs/by-name/bo/bozohttpd/package.nix
index b1b3c5407233..2cdd6a122634 100644
--- a/pkgs/by-name/bo/bozohttpd/package.nix
+++ b/pkgs/by-name/bo/bozohttpd/package.nix
@@ -22,13 +22,13 @@
stdenv.mkDerivation (finalAttrs: {
pname = "bozohttpd";
- version = "20240126";
+ version = "20260503";
# bozohttpd is developed in-tree in pkgsrc, canonical hashes can be found at:
# http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/www/bozohttpd/distinfo
src = fetchurl {
url = "http://eterna23.net/bozohttpd/bozohttpd-${finalAttrs.version}.tar.bz2";
- hash = "sha512-fr1PnyYAS3wkpmj/npRC3A87UL9LIXw4thlM4GfrtlJbuX5EkWGVJnHJW/EmYp7z+N91dcdRJgdO79l6WJsKpg==";
+ hash = "sha512-pK92Z9QmTWdR0gp56SjZesEwibz3rLShbdiPfAyqKrLCS3PpQQpeLXv/wqvR7N8/GybmzM6Bp8STj6ZO1IjqEw==";
};
buildInputs = [
Successfully finished processing
[check][nixpkgs-review]
## `nixpkgs-review` result
Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).
Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `92200067e3af35cb133eaa9b2bbf9b785ac08824`
---
### `x86_64-linux`
:white_check_mark: 2 packages built:
- bozohttpd
- bozohttpd-minimal
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/bozohttpd/versions.
meta.description for bozohttpd is: Bozotic HTTP server; small and secure
meta.homepage for bozohttpd is: http://www.eterna23.net/bozohttpd/
meta.changelog for bozohttpd is: http://www.eterna23.net/bozohttpd/CHANGES
###### Updates performed
- Version update
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 20260503 with grep in /nix/store/7hqc1zimapgy7k5w28g3hk18dr4w0d6n-bozohttpd-20260503
- found 20260503 in filename of file in /nix/store/7hqc1zimapgy7k5w28g3hk18dr4w0d6n-bozohttpd-20260503
---
Rebuild report (if merged into master) (click to expand)
```
3 total rebuild path(s)
3 package rebuild(s)
First fifty rebuilds by attrpath
bozohttpd
bozohttpd-minimal
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/7hqc1zimapgy7k5w28g3hk18dr4w0d6n-bozohttpd-20260503 \
--option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
--option trusted-public-keys '
nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
```
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached 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 bozohttpd https://github.com/r-ryantm/nixpkgs/archive/92200067e3af35cb133eaa9b2bbf9b785ac08824.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/92200067e3af35cb133eaa9b2bbf9b785ac08824#bozohttpd
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/7hqc1zimapgy7k5w28g3hk18dr4w0d6n-bozohttpd-20260503
ls -la /nix/store/7hqc1zimapgy7k5w28g3hk18dr4w0d6n-bozohttpd-20260503/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`](https://github.com/Mic92/nixpkgs-review).
Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `92200067e3af35cb133eaa9b2bbf9b785ac08824`
---
### `x86_64-linux`
:white_check_mark: 2 packages built:
- bozohttpd
- bozohttpd-minimal
---
###### Maintainer pings
cc @liclac for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
> [!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`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot).
https://api.github.com/repos/NixOS/nixpkgs/pulls/516691