Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Core must NEVER reference a dev-master (or @dev) package.
When it does, it breaks composer_manager and any other usage of "composer update" because Composer tries to update the package but finds no matching .git directory for it.
We already fixed mink-phantomjs-driver in #2629772: Update mink-phantomjs-driver to a tagged release but missed jcalderonzumba/gastonjs, which wasn't triggering an error cause there were no new commits.
Since there's no jcalderonzumba/gastonjs release at this point, we should start by pinning the requirement to a commit, therefore resolving the bug.
Comment | File | Size | Author |
---|---|---|---|
#11 | 2652068.8.for-8.1.patch | 9.38 KB | catch |
| |||
#9 | 2652068.8.for-8.1-do-not-test.patch | 9.38 KB | alexpott |
#8 | 2652068.8.patch | 8.99 KB | alexpott |
#5 | update-2652068-5.patch | 4.14 KB | mglaman |
Comments
Comment #2
bojanz CreditAttribution: bojanz at Centarro commentedwebflo points out that only a tagged release will work.
So we need to wait on https://github.com/jcalderonzumba/gastonjs/issues/18
Comment #3
tom friedhof CreditAttribution: tom friedhof at ActiveLAMP commentedTo work around this you can just delete the dependency in question out of the vendor directory. We have these two lines in our rebuild script.
Comment #4
JeroenTIssue https://github.com/jcalderonzumba/gastonjs/issues/18 is now fixed.
Comment #5
mglamanHere is a patch which updates jcalderonzumba/gastonjs to v1.0.2
Comment #6
BerdirNot sure about our current standards/rules on how to specify the dependency versions exactly but this seems consistent with other examples.
This would be very nice to see fixed.
Comment #7
saltednut++ this is a pain for distro maintenance right now! :D
Comment #8
alexpottThe patch attached in #5 generates an error after applying and running composer install...
I think this is the error the patch is trying to fix. Here's a patch that does the update AND also passes the composer install test.
I generated this by:
Comment #9
alexpottAnd here's a patch for 8.1 since the patch in #8 does not apply. Generated in exactly the same way.
Comment #10
BerdirDiscussed and tested.
The difference is that the previous patch didn't update installed.json, so composer still assumed it had a source checkout and the old version and got confused.
The patch in #8 is the right thing to do and composer install doesn't update anything as it shouldn't, since it is already there. Sorry for not testing this better.
Comment #11
catchJust running the 8.1 patch past the bot in case.
Comment #13
alexpott@catch that's a bug - you can't change version and submit a patch to test on that branch at the same time. I pressed retest :)
Comment #14
alexpottCreated #2667338: Update file's version for testing when issue's version is selected to address the d.o testing bug...
Comment #17
catchCommitted/pushed separately to 8.1.x and 8.0.x.