| 12 May 2023 |
hexa | ajs124 generated that list 🙂 | 12:58:52 |
@andreas.schraegle:helsinki-systems.de | In reply to @vcunat:matrix.org Could it be some commit mismatch? (e.g. between where this was computed and where you looked at dependencies) could be | 13:01:40 |
hexa |
121fa3293688 (HEAD -> ruby_2_7-eol) openssl_1_1: eol
95ce64b6a994 ruby_2_7: mark eol
64ef58cf89d1 (origin/master, origin/HEAD, master) Merge pull request #220825 from PanAeon/coltrane-init
| 13:15:56 |
hexa | * 121fa3293688 (HEAD -> ruby_2_7-eol) openssl_1_1: eol
95ce64b6a994 ruby_2_7: mark eol
64ef58cf89d1 (origin/master, origin/HEAD, master) Merge pull request #220825 from PanAeon/coltrane-init
| 13:15:58 |
hexa | ❯ ./maintainers/scripts/rebuild-amount.sh --print HEAD~1
Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
| 13:16:11 |
hexa | outputs nothing | 13:16:16 |
hexa | I think I'm holding this wrong | 13:16:21 |
hexa | Vladimír Čunát? | 13:25:28 |
vcunat | Yes, you need to do it after a revert. | 13:57:51 |
vcunat | It computes newly built derivations. | 13:58:01 |
vcunat | (or you can do --print HEAD HEAD~1 if I remember the order right) | 13:58:27 |
vcunat | hexa ⬆️ | 13:58:47 |
hexa | ❯ ./maintainers/scripts/rebuild-amount.sh --print HEAD~1 HEAD
Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
| 13:59:35 |
hexa | also printed an empty result | 13:59:38 |
hexa | HEAD~1 is the ruby_2_7 eol, HEAD is the openssl eol | 13:59:46 |
hexa | the idea was to exclude packages affected by the ruby eol | 13:59:57 |
vcunat | Is this pushed somewhere? | 14:00:24 |
vcunat | I can surely figure it out fast. I did it not long ago. | 14:01:21 |
hexa | https://github.com/mweinelt/nixpkgs/tree/just-for-vladimir | 14:01:31 |
vcunat | ./maintainers/scripts/rebuild-amount.sh --print HEAD HEAD~1
Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
1726 x86_64-darwin
3100 x86_64-linux
| 14:12:07 |
vcunat | hexa: so I put the list somewhere? | 14:12:20 |
hexa | gist? | 14:12:42 |
vcunat | I suspect your environment allowed these failures to pass. nix-env used on nixpkgs is quite impure in this sense, and the script isn't currently trying to avoid that. | 14:13:25 |
vcunat | Maybe it should be scrapped, possibly after merging any missing features into nixpkgs-review. | 14:13:54 |
vcunat | With the list as it is, it's certainly unmergable. Way worse than what you shown. | 14:15:41 |
vcunat | https://gist.github.com/vcunat/5f1e2c3f987819991f5d8d933327868d | 14:18:29 |
@andreas.schraegle:helsinki-systems.de | are you doing this based on master or staging-next? | 14:19:11 |