| 23 Jan 2024 |
|  @waldyrious:matrix.org left the room. | 22:13:04 |
| 27 Jan 2024 |
|  @lehmanator:gnulinux.club removed their profile picture. | 16:59:03 |
| @lehmanator:gnulinux.club removed their display name Sam Lehman. | 17:02:55 |
| @lehmanator:gnulinux.club left the room. | 17:06:33 |
| 29 Jan 2024 |
|  Sam Lehman joined the room. | 11:02:30 |
| Sam Lehman set a profile picture. | 11:06:02 |
| 31 Jan 2024 |
|  @federicodschonborn:matrix.org changed their profile picture. | 03:35:58 |
| @federicodschonborn:matrix.org changed their profile picture. | 06:21:35 |
| 7 Feb 2024 |
 evils | so, i fixed the update script for the KiCad package, and added 2 more packages (kicad-testing and kicad-testing-small)
now automatic updates seem to work, maybe too well
it's doing some duplicate work by also trying to update the -small packages
(or maybe the full package is the one that should be ignored, it includes a massive set of 3D models that have never failed to "build")
| 17:57:52 |
| evils | * so, i fixed the update script for the KiCad package, and added 2 more packages (kicad-testing and kicad-testing-small)
now automatic updates seem to work, maybe too well
it's doing some duplicate work by also trying to update the -small packages
(or maybe the full package is the one that should be ignored, it includes a massive set of 3D models that have never failed to "build" (but exceed hydra size limit)) | 17:59:21 |
| evils | though it also seems to be skipping kicad-unstable(-small) | 18:03:30 |
| evils | ah doh, the kicad-unstable attempts are probably failing because there's new dependencies, for which i have a local update, but was waiting hoping the test failure would be resolved xD | 18:05:47 |
| 15 Feb 2024 |
|  Luke joined the room. | 02:18:13 |
|  a-kenji joined the room. | 19:16:00 |
| 25 Feb 2024 |
|  Simon Menke set a profile picture. | 15:25:57 |
| 27 Feb 2024 |
|  Jeremy Fleischman (jfly) joined the room. | 04:52:43 |
| Jeremy Fleischman (jfly) | As a maintainer of a package on nixpkgs, what should I be doing to ensure that nixpkgs-update can keep my package up to date? I guess I had expected it would create PRs even if the build is failing, and it would be my job to fix those PRs. evils recently explained that that's not the case, and reading the code, I believe they're right.
Should I just be periodically running a command like nix-shell maintainers/scripts/update.nix --argstr maintainer jfly to make sure my packages are staying fresh?
| 04:59:09 |
| evils | ha, was considering pinging you here :) | 05:00:07 |
| evils | * ha, was considering pinging you here :)
i'd also love to know if there's a way to be informed | 05:15:48 |
 Mindavi | Subscribe to the GitHub releases rss feeds :) | 10:29:14 |
| Mindavi | Oh whatever they use as a release platform | 10:29:26 |
| 28 Feb 2024 |
 hexa | repology provides a per maintainer rss feed | 08:55:47 |
| Jeremy Fleischman (jfly) | hmm... GitHub releases and repology don't feel actionable to me. If I get a notification from repology about a new version of some package, shouldn't I still wait (a day? two?) for nixpkgs-update to post a PR? | 09:05:07 |
| Mindavi | Depends on how lazy you want to be :), you don't need to depend on the bot. But I understand that you'd rather only get pinged on success or issues instead of for each release. | 10:33:51 |
| Jeremy Fleischman (jfly) | Is this a feature that nixpks-update would be open to? I could imagine it creating a PR (perhaps in draft mode) and pinging the maintainers. | 17:59:43 |
| 29 Feb 2024 |
| hexa | 
Download image.png | 12:40:09 |
| hexa | 
Download image.png | 12:40:16 |
| hexa | kinda two PRs for the same package | 12:40:27 |
| 8 Mar 2024 |
|  Guilhem joined the room. | 16:50:39 |
| 14 Mar 2024 |
| @federicodschonborn:matrix.org left the room. | 02:04:49 |
