| 15 Apr 2024 |
 aislinnpearson | In reply to @symbioquine:matrix.org
There are definitely some rough edges still though - of course 🧪🔥 And this is fine - at the moment it’s only a theoretical discussion. We add values to our plots using a .csv upload that’s loosely based on the frictionless data concept - but I’d like to find a better user interface for it. It’s always interesting to see what other people have done | 12:25:35 |
 symbioquine | In reply to @aislinnpearson:matrix.org
This would be great Sounds good. Just let me know what works best for you... Here (Matrix), forum, Jitsi, etc | 12:33:44 |
| aislinnpearson | I’m just walking back from lunch. Will check my diary but jitsi is always good! | 12:37:53 |
| symbioquine | Drupal/Composer wizards here: Maybe I'm missing something obvious... Trying to pin farmOS to version 3.2.0 with the command composer require -W 'farmos/farmos:3.2.0', but it fails saying;
Root composer.json requires drupal/core-composer-scaffold 10.2.3, 10.2.5, found drupal/core-composer-scaffold[8.8.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.3.x-dev, 11.x-dev] but it does not match the constraint.
| 16:14:30 |
| symbioquine | composer update works fine to get from my the same starting state to farmos/farmos:3.2.1, but I can't seem to get it to update to 3.2.0. | 16:16:24 |
| symbioquine | If I didn't need to test something specific against 3.2.0 that wouldn't be a problem | 16:17:12 |
 mstenta | Hmm docker pull farmos/farmos:3.x maybe? | 16:18:52 |
| mstenta | (on a call at the moment... back later) | 16:18:59 |
| symbioquine | I was under the impression that the version of the farmOS docker container I'm running these commands under shouldn't matter because I'm using composer to manage the versions of farmOS and all my php dependencies... | 16:19:45 |
| symbioquine | I'm actually running these commands under the 3.1.2 docker image at the moment I think. | 16:20:20 |
| symbioquine | Okay, also tried the same update under the farmos/farmos:3.2.0 docker image with the same result. | 16:26:51 |
| mstenta | Back. Hmm the reason I suggested the image update is because I ran into something recently where the composer.lock was messing up tests... but that was different | 16:32:04 |
| mstenta | Looking closer at your error now... | 16:32:14 |
| mstenta | Oh did you run composer update twice? | 16:32:55 |
| mstenta | (Unfortunately that's necessary) | 16:33:11 |
| mstenta |
composer require -W 'farmos/farmos:3.2.0'
I don't usually do it this way... I usually update the composer.json version manually and then run composer update (twice)
| 16:33:45 |
| mstenta | Maybe composer require -W doesn't work because of the way we use composer-merge-plugin | 16:34:54 |
| symbioquine | Hmmm, I've been testing without running composer update. I.e. roll back to the git version of my composer.json and composer.lock where I was at farmOS 3.1.2, then trying to pin farmOS to 3.2.0 with the command I listed above. | 16:34:58 |
| symbioquine | Oh weird... I deleted a my vendor and web directories (which aren't tracked in git) and it looks like it has worked this time... | 16:37:43 |
| symbioquine | I thought composer would just consider the versions described in composer.json and composer.lock - then apply whatever is specified there in "building out" those directories | 16:38:36 |
| symbioquine | i.e. I'd assumed the contents of those directories should be strict "outputs" of a given version closure, but it seems like they're not. | 16:40:12 |
| symbioquine | I guess my build/update process should just pessimistically delete those directories before doing anything else | 16:40:51 |
| symbioquine | In reply to @symbioquine:matrix.org
I guess my build/update process should just pessimistically delete those directories before doing anything else This is in the context of building my custom farmOS docker image - obviously I know that the web directory is important in other contexts. | 16:41:58 |
| mstenta | Yea composer is some black magic... 🧙♂️🤷 | 16:44:50 |
| mstenta | The require -W flag has always been a little suspect to me... but who knows... glad you got it to work! | 16:45:17 |
| symbioquine | Well, I'll report in a moment whether it yields a working farmOS instance 🫣 | 16:46:02 |
| symbioquine | It did work btw | 19:30:57 |
| 16 Apr 2024 |
 farmBOT | @farmOS@fosstodon.org => Learn about the new #farmOS features included in v3.2.0 https://farmos.org/blog/2024/farmOS-3.2.0/ => https://fosstodon.org/@farmOS/112280596772902963 | 12:21:32 |
| 17 Apr 2024 |
| farmBOT left the room. | 11:32:44 |
| farmBOT joined the room. | 11:33:17 |
