| 15 Dec 2022 |
|  ribosomerocker changed their profile picture. | 19:53:02 |
| 18 Dec 2022 |
 @trofi:matrix.org | https://r.ryantm.com/log/strace/ <- did not run since January? Noticed there was a release 8 days ago, filed update PR manually. But I'm wondering if it's expected. | 12:56:52 |
 ryantm | trofi: Hmm, yeah that's bad. There's obviously problems with the bot, since Repology had newer versions between then and now. https://repology.org/project/strace/history | 22:28:20 |
| 23 Dec 2022 |
| @trofi:matrix.org | Trying to run nixpkgs-update locally to see how it would handle gawk. My attempt:
$ ./result/bin/nixpkgs-update update-batch --attrpath gawk
Configured Nixpkgs-Update Options:
----------------------------------
GitHub User: trofi
Send pull request on success: NO
Batch update: YES
Calculate Outpaths: NO
CVE Security Report: NO
Run nixpkgs-review: NO
Nixpkgs Dir: "/home/slyfox/.cache/nixpkgs"
update info uses attrpath: YES
----------------------------------
nixpkgs-update: Prelude.head: empty list
Is there a verbose mode maybe to figure out where that Prelude.head: empty list come from?
| 19:18:33 |
| ryantm | It's probably failing to find the GitHub token @trofi | 19:42:37 |
| @trofi:matrix.org | Aha | 19:43:15 |
| @trofi:matrix.org | Looks like my token is read fine. Instead it fails at https://github.com/ryantm/nixpkgs-update/blob/main/src/Update.hs#L768 . Looks like parseUpdates updateInfo only contains [Left "Unable to parse update: gawk"] for such command line. | 21:33:27 |
| @trofi:matrix.org | Looking at the option parsing update-batch --attrpath gawk is still unacceptable and requires versions passed: https://github.com/ryantm/nixpkgs-update/blob/main/src/Utils.hs#L233. I naively expected versions to be extracted from nixpkgs checkout and packages-to-update.txt. | 21:44:40 |
| 24 Dec 2022 |
|  @omlet:matrix.org left the room. | 00:22:26 |
| 30 Dec 2022 |
|  Federico Damián Schonborn joined the room. | 00:21:15 |
| 9 Feb 2023 |
|  @rdfg77:kde.org left the room. | 06:47:10 |
| 14 Mar 2023 |
|  pbsds joined the room. | 15:31:26 |
| 25 Mar 2023 |
|  amardeeps joined the room. | 04:45:46 |
|  @valconius:matrix.org joined the room. | 23:45:57 |
| 26 Mar 2023 |
|  rbutani joined the room. | 00:26:14 |
| 31 Mar 2023 |
|  @kranzes:matrix.org joined the room. | 00:53:32 |
| 5 Apr 2023 |
|  Redstone joined the room. | 05:48:00 |
|  @ulli:hrnz.li joined the room. | 18:41:17 |
| 6 Apr 2023 |
|  Lordie joined the room. | 14:01:06 |
| Lordie | Hi, I see that in the wiki there's an easy way to update the node packages in nixpkgs, by running ./pkgs/development/node-packages/generate.sh, however, running that script is not automated and I couldn't find a issue for it | 14:45:43 |
| Lordie | But I imagined that there's a reason for it not being automated yet | 14:45:50 |
| Lordie | I don't know if running that script would fit into this project | 14:46:20 |
 j-k | the script takes fooooreeeeeveeeeer to run.
I think nixpkgs-updates avoids any of the big language attributesets like JS & haskell AFAIK | 14:49:16 |
 hexa | it works for python packages, which is kinda big | 14:53:13 |
| hexa | but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript | 14:53:56 |
| j-k | well for python most things are standalone right? like the package has it's own src. rather than a mega sources.json that gets mapped out to many packages? | 14:54:31 |
| hexa | yep | 14:55:33 |
| Lordie | In reply to @hexa:lossy.network
but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript do you mean, pulling it out of nixpkgs/pkgs/development/node-packages into nixpkgs/pkgs/development/foo/bar and make a derivation using buildNpmPackage instead? | 15:02:01 |
| Lordie | In reply to @hexa:lossy.network
but if you care about a package within nodePackages, and it uses packages-lock.json (aka npm), convert it to use buildNpmPackage and use nix-update as the updateScript * do you mean, to pull it out of nixpkgs/pkgs/development/node-packages into nixpkgs/pkgs/development/foo/bar and make a derivation using buildNpmPackage instead? | 15:02:25 |
| hexa | yes | 15:02:42 |
