24 Jan 2025 |
| Paul Meyer (katexochen) joined the room. | 15:52:04 |
Paul Meyer (katexochen) | Hey, I merged https://github.com/NixOS/nixpkgs/pull/376046 yesterday, which added updateScript to azure-cli-extensions, but it looks like it's not working in nixpkgs-update. Locally I get the following:
❯ nix-shell maintainers/scripts/update.nix --argstr path azure-cli-extensions.ssh
Going to be running update for following packages:
- python3.12-ssh-2.0.5
Press Enter key to continue...
Running update for:
- python3.12-ssh-2.0.5: UPDATING ...
- python3.12-ssh-2.0.5: DONE.
Packages updated!
❯ git diff --no-ext-diff
diff --git a/pkgs/by-name/az/azure-cli/extensions-manual.nix b/pkgs/by-name/az/azure-cli/extensions-manual.nix
index 254ad69d2c23..823ab0fb0989 100644
--- a/pkgs/by-name/az/azure-cli/extensions-manual.nix
+++ b/pkgs/by-name/az/azure-cli/extensions-manual.nix
@@ -113,9 +113,9 @@
ssh = mkAzExtension rec {
pname = "ssh";
- version = "2.0.5";
+ version = "2.0.6";
url = "https://azcliprod.blob.core.windows.net/cli-extensions/ssh-${version}-py3-none-any.whl";
- hash = "sha256-gMmLENe/HOQAW3aUrt0FxHNVRWd1umElMIvmX7D+/JM=";
+ hash = "sha256-PSIGtOa91WxpzFCauZ5d5tx/ZtCRsBhbejtVfY3Bgss=";
description = "SSH into Azure VMs using RBAC and AAD OpenSSH Certificates";
propagatedBuildInputs = with python3Packages; [
oras
but the log says there was no diff: https://nixpkgs-update-logs.nix-community.org/azure-cli-extensions.ssh/2025-01-24.log Any ideas what could be wrong?
| 16:01:49 |
zowoq | The bot checks for new update scripts twice a day and updates are run on the merge base of master and staging so sometimes the the bot attempts an update script that doesn't work on the current merge base. | 23:39:57 |
25 Jan 2025 |
Paul Meyer (katexochen) | Makes sense, thanks. Will wait and observe. :) | 09:00:11 |
27 Jan 2025 |
| srhb joined the room. | 07:39:29 |
srhb | Can someone help me understand by the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?
I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,
ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True
ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False
How do I fix this? :)
| 08:21:04 |
srhb | * Can someone help me understand why the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?
I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,
ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True
ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False
How do I fix this? :)
| 08:24:43 |
FliegendeWurst (@GPN23) | In reply to @srhb:matrix.org
Can someone help me understand why the bot created https://github.com/NixOS/nixpkgs/pull/374876 ? (downgrade filebeat 8 -> filebeat 7) -- is it because I, in a misguided attempt to stay consistent with the existing filebeat7 attr named it filebeat8 rather than filebeat_8 ?
I tried loading up nixpkgs-update in a ghci repl, but it appears to indicate I'm good on that front,
ghci> versionCompatibleWithPathPin "filebeat8" "8.16.1"
True
ghci> versionCompatibleWithPathPin "filebeat8" "7.17.27"
False
How do I fix this? :)
Probably you need to fix the updateScript, that is what the bot used. | 08:54:21 |
srhb | Ah, yes. I'll have a look at that. | 08:54:43 |
srhb | Yep, thanks, think I fixed it, https://github.com/NixOS/nixpkgs/pull/377256 | 09:13:52 |
28 Jan 2025 |
Perchun Pak [don't ping; dm instead] | could we reopen https://github.com/Mic92/nixpkgs-review/issues/430 please?
see https://github.com/NixOS/nixpkgs/pull/377508#issuecomment-2618905015 | 20:34:31 |
2 Feb 2025 |
| pbsds changed their display name from pbsds to pbsds (FOSDEM). | 16:04:48 |
3 Feb 2025 |
| pbsds changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:35 |
5 Feb 2025 |
| detroyejr joined the room. | 01:49:47 |
6 Feb 2025 |
Morgan (@numinit) | What's the usual practice for nested attributes where I'd like to expose an update script? For instance, we want to expose a single attribute in androidenv , which is an attrset, not a derivation itself. | 03:29:53 |
Morgan (@numinit) | Provided, this is also a custom update script not using nix-update or something else. | 03:30:42 |
Morgan (@numinit) | Do I need to expose the passthru on the top level attribute? Is the solution a well placed recurseIntoAttrs? Never done this before, so unsure. :-) | 03:34:15 |
Perchun Pak [don't ping; dm instead] | is this what are you looking for? | 07:43:46 |
Perchun Pak [don't ping; dm instead] | https://github.com/NixOS/nixpkgs/blob/34c5ee1a54bbf1ccfd2f5443564ccb6e71c05879/pkgs/applications/editors/vim/plugins/non-generated/blink-cmp/default.nix#L1 | 07:43:47 |
Perchun Pak [don't ping; dm instead] | * https://github.com/NixOS/nixpkgs/blob/34c5ee1a54bbf1ccfd2f5443564ccb6e71c05879/pkgs/applications/editors/vim/plugins/non-generated/blink-cmp/default.nix | 07:43:52 |
Morgan (@numinit) | Close-ish. More wondering how a passthru.updateScript that's not nixpkgs-update (i.e. it's a custom script) would work on an attribute that isn't toplevel. | 21:07:05 |
8 Feb 2025 |
| Marcel joined the room. | 20:26:59 |
10 Feb 2025 |
| carlossless joined the room. | 18:50:35 |
carlossless | Would anyone know why eval could be failing on an update PR here: https://github.com/NixOS/nixpkgs/pull/380939#issuecomment-2648941718? | 18:51:12 |
11 Feb 2025 |
| ramblurr joined the room. | 11:52:59 |
14 Feb 2025 |
| bmgsh joined the room. | 06:37:48 |
15 Feb 2025 |
| BenjB83 joined the room. | 10:17:36 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:04 |
18 Feb 2025 |
bmgsh | i recently manually updated package optinix i can see from https://r.ryantm.com/log/ that it has never been attempted to automatically update. is there some process to register a package for autoupdates? | 06:03:19 |
K900 | The auto-updates pull from repology, and that being a nix specific tool, it's probably not tracked on there | 06:04:35 |