17 Sep 2024 |
Pol | Yes, we need resources, they are trivial | 15:23:17 |
@genghiz:talk.go7box.xyz | Had been thinking of putting some rudimentary rust skills to use by writing something, but I'm no software dev so I'll probably take some time to write | 15:23:26 |
Pol | The v2 of the builder is currently unstable and therefore, unusable. | 15:23:30 |
@genghiz:talk.go7box.xyz | For a php builder that is | 15:23:33 |
@genghiz:talk.go7box.xyz | Ah | 15:23:35 |
Pol | I think piotrkwiecinski will have a look at some point. I wish I could also have a look... but it's hard to start a new job with new stuff and work with PHP that I don't use anymore. | 15:24:17 |
@genghiz:talk.go7box.xyz | Yeah makes sense | 15:24:57 |
@genghiz:talk.go7box.xyz | Most of my work involves python and R when I code, so it's a bit difficult for me as well | 15:25:12 |
Pol | I do python now :) | 15:25:21 |
@genghiz:talk.go7box.xyz | Did you just volunteer to help a non-programmer code up stuff he has no business coding up? :P | 15:26:18 |
Pol | Sorry can you rephrase? | 15:28:10 |
@genghiz:talk.go7box.xyz | I was joking that I will now come to you with issues in my python code. | 15:29:34 |
@genghiz:talk.go7box.xyz | (I was not being serious of course) | 15:29:40 |
@genghiz:talk.go7box.xyz | Because you have been very nice in helping me with PHP in the past and I will take advantage of your good nature. ^_^ | 15:30:06 |
Pol | If I can help, I'll gladly do it since improving something in nixpkgs will potentially benefit me at some point too ;) | 15:32:32 |
| @genghiz:talk.go7box.xyz left the room. | 17:16:57 |
| Genghiz joined the room. | 17:18:44 |
20 Sep 2024 |
Genghiz | https://github.com/NixOS/nixpkgs/pull/341746 | 17:38:47 |
Genghiz | https://github.com/NixOS/nixpkgs/pull/342556 | 17:38:57 |
Genghiz | Would appreciate a merge on these. :) | 17:39:05 |
Genghiz | In reply to @genghiz:talk.go7box.xyz I'll do that I thought I'd do this but I think it's a bit more complicated than I had expected because it would be good to expose the option as well. The way I was thinking of doing it would hardcode it. | 17:40:08 |
Genghiz | In reply to @genghiz:cdw.go7box.xyz Would appreciate a merge on these. :) Both related to firefly-iii | 17:46:16 |
Genghiz | Hence the ping in this channel | 17:46:23 |
| Genghiz changed their display name from genghiz to Catman. | 17:49:53 |
| Genghiz changed their display name from Catman to Genghiz. | 17:50:09 |
22 Sep 2024 |
| patka joined the room. | 13:49:24 |
patka | Hello 👋
Currently packages built with buildComposerProject2 can't properly be updated because of the autoloader bug.
The bug seems to be in the apcu-autoloader that is enabled as a flag in the new composer builder, but wasn't used in the old one.
What about removing the flag from the new version until it's fixed upstream? It's not that big of a deal. Then we can atleast fix and update packages. | 13:54:37 |
Pol | Yes this is because of that flag indeed, but I would have prefered to have it fixed upstream though | 14:23:35 |
patka | Yeah, sure. Me too
But it wasnt enabled in the first composer builder. The packages that use the second builder are broken.
So we can either move the v2 packages back to v1, or temporarily disable the broken flag in v2 that wasn't even used in v1.
We can't not update the packages that currently use v2 until upstream decides to fix it | 14:26:54 |
patka | * Yeah, sure. Me too
But it wasnt enabled in the first composer builder. The packages that use the second builder are broken.
So we can either move the v2 packages back to v1, or temporarily disable the broken flag in v2 that wasn't even used in v1.
We can't not update the packages that currently use v2 until upstream decides to sometimes maybe possibly fix it. As soon as upstream fixes it we enable acpu-autoloader again
| 14:36:02 |