IRC logs for #farmOS, 2023-06-23 (GMT)

2023-06-22
2023-06-24
TimeNickMessage
[00:11:49]* heartburn has quit (*.net *.split)
[00:13:37]* heartburn has joined #farmos
[10:30:47]<symbioquine[m]>I've been experimenting with the instructions from https://farmos.org/hosting/composer/ with an odd result...
[10:31:13]<symbioquine[m]>The version of farmos/farmos keeps getting locked at 2.0.0-alpha5.
[10:33:43]<symbioquine[m]>Does [this line](https://github.com/farmOS/composer-project/blob/402c1bbef648a6f124c7ad4c...) not include version 2.1.1?
[10:34:58]<symbioquine[m]>ACTION sent a shell code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/c25918937c...
[11:02:32]<symbioquine[m]><symbioquine[m]> "Does [this line](https://github..." <- It looks like it should: https://getcomposer.org/doc/articles/versions.md#caret-version-range-
[11:03:31]<symbioquine[m]>And Packagist knows about farmOS 2.1.1;
[11:03:31]<symbioquine[m]>* https://packagist.org/packages/farmOS/project
[11:03:31]<symbioquine[m]>* https://packagist.org/packages/farmos/farmos
[11:05:56]<symbioquine[m]>Interesting... I needed to add --ignore-platform-reqs for it to pick up version 2.1.1
[11:08:10]<wotnak[m]>tried composer create-project farmos/project:2.x-dev now and 2.1.1 was correctly installed for me, maybe your environment has some missing/outdated platform requirements that are enough for 2.0.0-alpha5 but not for newer versions
[11:10:26]<symbioquine[m]>Maybe. I'm on Arch Linux - with its rolling releases most stuff tends to be pretty up to date...
[11:14:06]<paul121[m]>Why did you add these flags? --ignore-platform-req=ext-simplexml --ignore-platform-req=ext-gd
[11:15:15]<symbioquine[m]>Because they shouldn't matter. I'm only trying to use my system's composer install to manage the dependencies in my composer.json/composer.lock file. Everything after that will be happening in a docker build...
[11:15:40]<paul121[m]>Gotcha
[11:16:16]<symbioquine[m]>That said, it's not working so well....
[11:16:37]<symbioquine[m]>Something is doing its own check for php-gd and failing despite that flag
[11:17:39]<paul121[m]>I've experimented with this in a similar way, but using the official composer docker image to do something like: docker run composer update
[11:17:50]<paul121[m]>and I had to pass in some of those platform flags
[11:17:56]<paul121[m]>because the composer docker image is quite slim
[11:18:09]<symbioquine[m]>Yeah, was just about to give up on using my system's php/composer versions
[11:18:09]<paul121[m]>trying to find my notes..
[11:22:43]<paul121[m]>basically this (scroll to Troubleshooting/PHP Version): https://hub.docker.com/_/composer
[11:23:28]<paul121[m]>$ docker run --rm --interactive --tty \
[11:23:28]<paul121[m]> --volume $PWD:/app \
[11:23:28]<paul121[m]> composer install --ignore-platform-reqs --no-scripts
[11:25:52]<symbioquine[m]>Well looks like I got it working with my system's php version - at least so far as a successful create-project.
[11:29:18]<paul121[m]>Nice. Simple things should work!
[11:38:02]<symbioquine[m]>Well it should work more easily without those ignore flags - and it should honor the ignore flags more fully...
[11:38:38]<symbioquine[m]>It turns out there are checks for php-gd and php-sodium that the ignore flags don't work for so I had to actually install/enable those.