nixos/nixpkgs - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Expand)	Author	Age	Files	Lines
*	python3Packages: format with nixfmt	Martin Weinelt	2024-05-22	1	-17/+14
*	python3Packages.arrow: 1.2.3 -> 1.3.0	Martin Weinelt	2023-12-20	1	-7/+14
*	python3.pkgs.*: Explicitly pass buildPythonPackage format parameter•••Long term we should move everything over to `pyproject = true`, but in the mean time we can work towards deprecating the implicit `format` paremeter. cc https://github.com/NixOS/nixpkgs/issues/253154 cc @mweinelt @figsoda	adisbladis	2023-12-07	1	-0/+1
*	python3.pkgs: Migrate fetchers to use hash•••when they already rely on SRI hashes.	Martin Weinelt	2023-03-03	1	-1/+1
*	treewide: switch to nativeCheckInputs•••checkInputs used to be added to nativeBuildInputs. Now we have nativeCheckInputs to do that instead. Doing this treewide change allows to keep hashes identical to before the introduction of nativeCheckInputs.	Guillaume Girol	2023-01-21	1	-1/+1
*	python3Packages.arrow: 1.2.2 -> 1.2.3	Martin Weinelt	2022-09-18	1	-2/+2
*	python3Packages.arrow: 1.2.1 -> 1.2.2	Martin Weinelt	2022-03-14	1	-2/+2
*	python3Packages.arrow: 1.2.0 -> 1.2.1	Jonathan Ringer	2021-11-30	1	-2/+2
*	python3Packages.arrow: 1.1.1 -> 1.2.0	Martin Weinelt	2021-10-11	1	-2/+2
*	python3Packages.arrow: 1.1.0 -> 1.1.1	Martin Weinelt	2021-09-01	1	-2/+2
*	pythonPackages.arrow: 1.0.3 -> 1.1.0	Alvar Penning	2021-06-21	1	-2/+4
*	python3Packages.arrow_1: merge into python3Packages.arrow•••They are the same version.	Robert Schütz	2021-05-13	1	-7/+17
*	python3Packages.arrow: 0.17.0 -> 1.0.3	Frederik Rietdijk	2021-04-03	1	-2/+2
*	treewide: remove stdenv where not needed	Pavol Rusnak	2021-01-25	1	-1/+1
*	Recover the complicated situation after my bad merge•••I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state	Vladimír Čunát	2020-10-26	1	-2/+2
*	Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"•••I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.	Vladimír Čunát	2020-10-25	1	-2/+2
*	pythonPackages.arrow: 0.15.8 -> 0.17.0	Drew Risinger	2020-10-12	1	-2/+2
*	python: arrow: 0.15.6 -> 0.15.8	Frederik Rietdijk	2020-08-04	1	-2/+2
*	python.pkgs.arrow: disable failing test	Frederik Rietdijk	2020-06-11	1	-5/+7
*	python3Packages.arrow: fix dependencies	Jonathan Ringer	2020-05-11	1	-10/+17
*	python3Packages.arrow: 0.15.5 -> 0.15.6	Frederik Rietdijk	2020-05-11	1	-2/+2
*	pythonPackages.arrow: fix license (#85803)	Drew	2020-04-22	1	-1/+1
*	pythonPackages.arrow: 0.15.4 -> 0.15.5	Drew Risinger	2020-03-26	1	-2/+2
*	python: arrow: 0.15.2 -> 0.15.4	Frederik Rietdijk	2019-11-22	1	-2/+2
*	pythonPackages.arrow: fix build	Jonathan Ringer	2019-10-27	1	-2/+2
*	python: arrow: 0.13.2 -> 0.15.2	Frederik Rietdijk	2019-10-27	1	-2/+2
*	python: arrow: 0.13.1 -> 0.13.2	Frederik Rietdijk	2019-06-15	1	-2/+2
*	python: arrow: 0.12.1 -> 0.13.1	Frederik Rietdijk	2019-02-17	1	-4/+5
*	python: arrow: 0.12.0 -> 0.12.1	Frederik Rietdijk	2018-01-20	1	-2/+2
*	python.pkgs.arrow: fix python 2 build	Frederik Rietdijk	2018-01-03	1	-0/+4
*	python: arrow: 0.10.0 -> 0.12.0	Frederik Rietdijk	2017-12-31	1	-6/+5
*	pythonPackages.arrow: move to python-modules	Jörg Thalheim	2017-07-21	1	-0/+27