| 9 Dec 2024 |
 maralorn | Just wondered whether there was any triggering event. | 12:45:07 |
| 10 Dec 2024 |
|  @tomodachi94:matrix.org joined the room. | 02:04:57 |
| @tomodachi94:matrix.org | Is it possible to remove a package from haskellPackages? If so, when is it appropriate to do so? | 02:05:32 |
| @tomodachi94:matrix.org | Context: the haskellPackages.opentracing* packages are deprecated by upstream: https://github.com/NixOS/nixpkgs/issues/261927 | 02:06:53 |
| @tomodachi94:matrix.org | * Is it possible to remove a package from haskellPackages? If so, when is it appropriate to do so (same as any package? Something different)? | 02:30:37 |
| @tomodachi94:matrix.org | Context: I'm trying to remove all of the haskellPackages.opentracing* packages (OpenTracing is deprecated afaict): https://github.com/NixOS/nixpkgs/issues/261927 | 03:29:01 |
| @tomodachi94:matrix.org | On second thought, some of those packages might still be maintained? | 05:37:30 |
| maralorn | In reply to @tomodachi94:matrix.org
Is it possible to remove a package from haskellPackages? If so, when is it appropriate to do so (same as any package? Something different)? No, not really. We can mark them broken, insecure or unsupported but removal is currently not on the menu. | 10:13:08 |
| maralorn | What problem are you trying to solve? There are thousands of unmaintained/deprecated packages on hackage. | 10:14:38 |
 sterni (he/him) | maralorn: I've PR-ed the second bump, it evals fine, compilation is untested though | 20:16:15 |
 alexfmpe | In reply to @maralorn:maralorn.de
Possibly already today. Indeed, it came out | 22:53:29 |
| alexfmpe | I guess the next cycle here is LTS 23? | 22:53:51 |
| maralorn | Next cycle yes. First we need to finish the current one. Which has been bumped to the final 22 version. | 22:55:32 |
| @tomodachi94:matrix.org | In reply to@maralorn:maralorn.de
What problem are you trying to solve? There are thousands of unmaintained/deprecated packages on hackage. Dropping software that is impossible to responsibly maintain, but see above message (looks like the main one is still maintained) | 23:55:22 |
| 11 Dec 2024 |
|  marijan changed their profile picture. | 14:19:53 |
| 12 Dec 2024 |
|  mrtni joined the room. | 06:26:26 |
| @tomodachi94:matrix.org | * Dropping software that is impossible to responsibly maintain, but see above message (looks like the main package is still maintained) | 20:39:51 |
|  @pseudomata:matrix.org left the room. | 23:07:31 |
| 13 Dec 2024 |
|  Funky joined the room. | 06:34:00 |
 Hungry Joe | Hi, I just wanted to check that this PR was in the right place, and was visible to the right people
https://github.com/NixOS/nixpkgs/pull/363022
Cheers | 12:13:32 |
| maralorn | It‘s at least on my todo list, but I am currently swampd. | 12:17:30 |
| maralorn | * It‘s at least on my todo list, but I am currently swamped. | 12:17:32 |
| Hungry Joe | Thanks, so long as it's on your radar | 12:19:18 |
|  trexd joined the room. | 14:14:11 |
| trexd | Hello, If there is a package on hackage I want to make available in in nixpkgs do I have to wait for the next snapshot or can I upstream it myself somehow? | 14:35:26 |
| maralorn | Waiting sounds right. | 14:47:45 |
| alexfmpe | Yeah not much point adding an override to nixpkgs that just lasts a few weeks on average (current snapshot is abnormally delayed due to reasons) | 16:24:29 |
| alexfmpe | I'd just override locally and remove when next snapshot makes its way to you | 16:25:00 |
| trexd | I'm working with the maintainer to provide the package in Nixpkgs but otherwise I have it working locally. The current overlay is difficult to maintain because of all the packages in the repo under the cabal.project so part of the reason providing the package in nixpkgs would make it easier for those who just want to use it without developing on all the packages. | 16:28:07 |
| alexfmpe | Huh, are all these packages waiting for the next snapshot? | 16:29:10 |
