mirror of https://github.com/ryantm/nixpkgs-update.git synced 2024-12-14 21:33:46 +03:00

Updating nixpkgs packages since 2018

Go to file

Ryan Mulligan 0bd5de1acb switch back to old hash splitter In Nix 2.2, the expected hash output seems to have changed back to what it was before.		2019-08-03 15:07:36 -07:00
.github	add FUNDING.yml	2019-07-01 19:32:40 -07:00
src	switch back to old hash splitter	2019-08-03 15:07:36 -07:00
test	Time: add doctests	2019-06-08 14:41:16 -07:00
.gitattributes	add clean & smudge filter	2018-04-06 17:36:52 +02:00
.gitignore	revamp build files & pin nixpkgs	2019-03-31 13:54:29 -07:00
.hindent.yaml	add clean & smudge filter	2018-04-06 17:36:52 +02:00
.travis.yml	try using cachix with travis	2019-07-30 20:23:31 -07:00
default.nix	add nix dependency	2019-08-03 15:05:19 -07:00
LICENSE	LICENSE: use text supplied by Creative Commons directly	2019-05-21 06:33:30 -07:00
nixpkgs-update.nix	revamp build files & pin nixpkgs	2019-03-31 13:54:29 -07:00
package.yaml	add polysemy suggested extensions and ghc options	2019-06-08 05:45:24 -07:00
README.md	use shell for running nixpkgs-update to get proper dependencies	2019-08-03 15:05:53 -07:00

README.md

nixpkgs-update

The future is here; let's evenly distribute it!

Introduction

nixpkgs-update is the code used by @r-ryantm to semi-automatically update nixpkgs. It uses package repository information from Repology.org to generate a list of outdated packages. A package is considered "outdated" if a newer version of the package is available at any other repository tracked by Repology. nixpkgs-update tries to update each package in the dumbest way that could work. It find-replaces the old version number with the new one, uses nix-build to try to get the new hash, then tries to build the package. If it succeeds, it checks the outputs and makes a pull request. It also uploads the built package to Cachix, which people can use to manually test the package without building it themselves.

nixpkgs-update features

Checks

A number of checks are performed to help nixpkgs maintainers gauge the liklihood that an update was successful. All the binaries are run with various flags to see if they have a zero exit code and output the new version number. The outpath directory tree is searched for files containing the new version number. A directory tree and disk usage listing is provided.

Rebuild reports

The PRs made by nixpkgs-update say what packages need to be rebuilt if the pull request is merged. This uses the same mechanism OfBorg uses to put rebuild labels on PRs. Not limited by labels, it can report the exact number of rebuilds and list some of the attrpaths that would need to be rebuilt.

PRs against staging

If a PR merge would cause more than 100 packages to be rebuilt, the PR is made against staging.

Logs

Logs from r-ryantm's runs are available on Discourse. There are a lot of packages nixpkgs-update currently has no hope of updating. Please dredge the logs to find out why your pet package is not receiving updates.

Cachix

By uploading the build outputs to Cachix, nixpkgs-update allows you to test a package with one command.

Instructions

Clone this repo:

git clone https://github.com/ryantm/nixpkgs-update && cd nixpkgs-update

Get a list of oudated packages and place them in a packages-to-update.txt file in the root directory of this repository.

git clone https://github.com/ryantm/repology-api.git && cd repology-api
nix run nixpkgs.cabal2nix -c cabal2nix --shell --hpack . > shell.nix && nix-build shell.nix && result/bin/repology-api > ../packages-to-update.txt

Return back cd .. and run the tool nix shell --run "nixpkgs-update --update"

Adding new dependencies / updating Cabal file

nix run nixpkgs.haskellPackages.hpack -c hpack && nix run nixpkgs.cabal2nix -c cabal2nix --hpack . > nixpkgs-update.nix

Development tips

Run a type checker in the background for quicker type checking feedback:

nix-shell --run ghcid