| 9 Jun 2023 |
 Pol | So, the first commit will be the one tagged with 8.2.7 I guess. | 19:47:50 |
| Pol | Oh boy the branch management in the php project, I don't get it. | 19:49:22 |
| Pol | Feel free to take care of it I don't know if I will be able to do it. | 20:30:00 |
 Jan Tojnar | I think I will leave it to PHP maintainers, still have bunch of GNOME libraries I need to update 😆 | 20:40:45 |
| 12 Jun 2023 |
 @etu:failar.nu | By the time we drop 8.0 we should probably move to 8.2 as default as well 🙂 | 09:02:51 |
| Pol | Is there someone who can review this commit and let me know if it's ok? Basically, this is a composer plugin: https://github.com/NixOS/nixpkgs/pull/225401/commits/8b034b8edc879c62eab285c46256c47bb05a72f7 | 16:38:10 |
| Pol | * Is there someone who can review this commit and let me know if it's ok? Basically, this is a composer plugin: https://github.com/NixOS/nixpkgs/pull/225401/commits/858868a383ea9c071e69f99e9e10c3793547d381 | 16:42:53 |
| Pol | * Is there someone who can review this commit and let me know if it's ok? Basically, this is a composer plugin: https://github.com/NixOS/nixpkgs/pull/225401/commits/cfce10ee2d809f9ab80469be79bff1253dcedd66 | 16:58:28 |
| Pol | (link updated) | 17:02:22 |
 tgerbet | In reply to @drupol:matrix.org
Is there someone who can review this commit and let me know if it's ok? Basically, this is a composer plugin: https://github.com/NixOS/nixpkgs/pull/225401/commits/cfce10ee2d809f9ab80469be79bff1253dcedd66 Maybe it would be best to retrieve the keys directly from the repository https://github.com/composer/composer.github.io
This way we are sure they do not suddenly change.
Do you need them at all? From my understanding those keys are only useful to verify the installer which we does not seem to be the case here
| 17:13:06 |
| Pol | Good idea with the Github repo. Going to do it. | 17:26:03 |
| Pol | Keys are required to avoid this: | 17:26:08 |
| Pol | 
Download image.png | 17:26:56 |
| Pol | On the top you have the version without it, on the bottom you have the version with it. | 17:27:04 |
| tgerbet | Oh okay, I did not know it was looking for that. Maybe it should be done directly in phpPackages.composer as it seems to also have the problem. It is probably not specific to your plugin | 17:32:35 |
| Pol | True, but I have no clue on how to integrate that. | 17:33:41 |
| Pol | Do you think adding a composerHome input to composer derivation is a good idea? | 17:34:01 |
| Pol | I just pushed the changes for the composer keys ! https://github.com/NixOS/nixpkgs/pull/225401/commits/9e1540b6f6f7055af9710aa1c8c83b9966953cce | 17:34:24 |
| tgerbet | In reply to @drupol:matrix.org
Do you think adding a composerHome input to composer derivation is a good idea? Probably not, it will break too many things (e.g. access to GH OAuth access token) | 17:38:55 |
| Pol | Mmhm I don't know | 17:40:15 |
| tgerbet | It looks like we only get those warnings/errors because we are using the phar and in this situation it expects to be able to upgrade itself https://github.com/composer/composer/blob/bbea3e5284fd859373c292c7f696f9647f9a59ef/src/Composer/Command/DiagnoseCommand.php#L152 | 17:41:33 |
| Pol | Actually, we can reproduce the same issue with the src version, let me do a poc | 17:42:25 |
| Pol | Oh no you're right | 17:43:34 |
| Pol | 
Download image.png | 17:43:37 |
| Pol | It only does that with the PHAR indeed. | 17:43:45 |
| Pol | So sad it doesnt use proper XDG standard. | 17:44:29 |
| Pol | So we could install those keys in a specific place and be done with it. | 17:44:44 |
| tgerbet | Yep. Since it is more of a Composer issue than something related to the plugin I would just let not bother with the keys in the plugin. It's not like a composer diagnose will be issue while building the PHP packages 😄 | 17:53:16 |
| Pol | I just wanted to be just pixel perfect... "just in case of... " | 17:58:04 |
| tgerbet | Unpacking the phar archive seems to work https://github.com/NixOS/nixpkgs/pull/237410 | 19:02:36 |
