| 9 May 2023 |
 hexa | wait no, I mistook that for another project | 12:08:28 |
| 10 May 2023 |
|  @rasmus:rend.al left the room. | 19:56:34 |
| 12 May 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 00:58:46 |
 aidalgol | I have a project that I would like to submit for the nix-community GitHub org: https://github.com/aidalgol/nix-steam-fetcher a nix fetcher for Steam "depots", intended to aid writing flakes for game servers that are distributed exclusively via Steam. | 04:04:58 |
 Mic92 | aidalgol: should be fine, just as a general comment. Maybe having one example use in the fetcher directly in the README would be helpful because the project linked as an example also don't directly have an example in its readme and one has to dig through code | 06:34:01 |
| Mic92 | {
name,
debug ? false,
appId,
depotId,
manifestId,
branch ? null,
hash,
}: | 06:34:06 |
| Mic92 | it might be also easier to use if the fetcher would just exposed as packages.fetchSteam instead of having to use an overlay, which hides the origin of the function. | 06:35:39 |
| Mic92 | * it might be also easier to use if the fetcher would just exposed as packages.<system>.fetchSteam instead of having to use an overlay, which hides the origin of the function. | 06:35:50 |
| Mic92 | Just make sure you don't upload any assets to the repository that are not redistributable. We had one instance of DMCA for nix-community already. If you are planning to do that it would be better not in this org. | 06:36:59 |
| Mic92 | * it might be also easier to use if the fetcher would just exposed as packages.<system>.fetchSteam instead of having to use an overlay, which hides the origin of the function when being imported into a larger project. | 06:37:23 |
| aidalgol | No intention to upload any assets. | 10:30:41 |
| aidalgol | In reply to@joerg:thalheim.io
it might be also easier to use if the fetcher would just exposed as packages.<system>.fetchSteam instead of having to use an overlay, which hides the origin of the function when being imported into a larger project. I had tried that initially, but nixpkgs.config.allowUnfree was not having any effect on the non-free package in the flake. See https://discourse.nixos.org/t/using-unfree-packages-from-flakes/27372 | 10:32:11 |
| Mic92 | aidalgol: you maybe want to consider this than: https://github.com/numtide/nixpkgs-unfree | 10:48:52 |
| Mic92 | It's also baked by a binary cache | 10:49:06 |
| Mic92 | you got an organisation invite | 10:50:09 |
| aidalgol | Thanks, I'll try that. | 10:50:18 |
| Mic92 | zowoq: what is the new workflow for migrating a repository again? | 10:50:30 |
 raitobezarius | Creating an issue I guess | 10:51:51 |
| aidalgol | I'll address these issues first. | 10:52:56 |
| @federicodschonborn:matrix.org changed their profile picture. | 19:34:15 |
| @federicodschonborn:matrix.org changed their display name from Federico Schonborn to Federico Damián Schonborn. | 19:34:59 |
| 13 May 2023 |
 zowoq | In reply to @joerg:thalheim.io
zowoq: what is the new workflow for migrating a repository again? Settings -> Member privileges -> Repository creation -> Public. I've enabled it. | 00:46:24 |
| zowoq | In reply to @joerg:thalheim.io
zowoq: what is the new workflow for migrating a repository again? * Settings -> Member privileges -> Repository creation -> Public. I've enabled it. (and disabled again as the repo was transferred.) | 01:35:28 |
| aidalgol | OK, it's transferred. I could not figure out how to redo it with passing packages instead of with overlays, though. | 01:39:31 |
| 16 May 2023 |
| hexa | the aarch64-community builder is unreachable. cc cole-h | 00:17:44 |
 @cole-h:matrix.org | In reply to @hexa:lossy.network
the aarch64-community builder is unreachable. cc cole-h Should come back up in the next couple minutes. Ping me again if that doesn't happen? | 00:34:18 |
| hexa | or well … 💤 | 00:37:18 |
| zowoq | I've deployed the fix for the hercules problems we were having a couple of weeks ago, seems to be working fine but please let me know if you start seeing errors. | 04:07:41 |
| 17 May 2023 |
|  6t8k joined the room. | 16:20:35 |
| 19 May 2023 |
|  @1e1001:matrix.org left the room. | 03:18:43 |
