!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

193 Members
Keeping nixpkgs up to date. r-ryantm bot. https://github.com/ryantm/nixpkgs-update and https://github.com/nix-community/infra/blob/master/build02/nixpkgs-update.nix57 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
30 Jun 2024
@jshcmpbll:beeper.comjshcmpbllHi all, I just noticed a PR for a package I maintain has merge conflicts. Does anyone know the proper way to handle that? Should I just dismiss the PR or is there a mechanism to fix conflicts? Thanks! https://github.com/NixOS/nixpkgs/pull/32319421:50:00
1 Jul 2024
@ryantm:matrix.orgryantmI close it. It will regenerate.12:07:39
@ryantm:matrix.orgryantm* I closed it. It will regenerate.12:07:51
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @ryantm:matrix.org
There's no API. The bot is hosted by a nix-community server. I donate to them to help pay for it.

have you already thought about the problem of how to make it easy for maintainers to get notified of build issues with their packages?

what comes to mind is a thing where i can request the bot to send a message to the contact i have in maintainer-list.nix, proving that i control it; and then, notify me when a package i maintain breaks (via the same channel, so email/matrix).

does this seem useful and doable in the current codebase? i know zero haskell lol

18:40:29
2 Jul 2024
@katexochen:matrix.orgPaul Meyer (katexochen) left the room.06:12:38
@asymmetric:matrix.dapp.org.ukasymmetricor perhaps we could file issues in a separate repo and tag maintainers there, with the option to opt out? or is that too aggressive/spammy?08:23:40
4 Jul 2024
@philiptaron:matrix.orgPhilip Taron (UTC-8) left the room.15:46:37

Show newer messages


Back to Room ListRoom Version: 9