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.
Problem/Motivation
I think if you install a meta package with our fixture manipulator and then call \Drupal\package_manager\ComposerInspector::getInstalledPackagesList
the InstalledPackage object will the project root as the path. It should probably be null.
this is probably a problem with getInstalledPackagesList but it could be the FixtureManipulator.
We can manually test by pointing getInstalledPackagesList at a real composer project with metapackage.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#8 | Screenshot 2023-03-14 at 5.50.45 PM.png | 303.49 KB | yash.rode |
Issue fork automatic_updates-3345646
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Wim LeersI'm pretty sure it's the former based on the observations I had while working on #3343827: Update FixtureManipulator to work with InstalledPackagesList, real composer show command, but of course we'll need to confirm 👍
Is this really
core-mvp
though?Comment #3
tedbowyes you are right
core-post-mvp
Comment #5
yash.rode CreditAttribution: yash.rode at Acquia commentedComment #6
yash.rode CreditAttribution: yash.rode at Acquia commentedComment #8
yash.rode CreditAttribution: yash.rode at Acquia commentedI can confirm that it is not the FixtureManipulator which is causing this problem as you can see in the screen-shot
. So it is composer
show()
which is causing the problem ingetInstalledPackagesList()
. I tried debugging it and created a git clone of composer and added a var_dump() incomopser-testing/composer/src/Composer/Command/ShowCommand.php
when
$input->getOption('path')
is true but I am not able to create a meta package in that git clone.Comment #9
yash.rode CreditAttribution: yash.rode at Acquia commentedComment #10
Wim Leersgit clone
you mention is of Composer itself, so of course you cannot make a meta package inside that git clone?! 🤔Comment #11
tedbowComment #13
phenaproximaComment #14
phenaproximaComment #15
tedbowLooks pretty good but a couple MR comments
Comment #16
phenaproximaComment #17
phenaproximaComment #18
Wim LeersComment #19
phenaproxima🏓
Comment #20
Wim LeersIf the necessary follow-ups existed, this would be RTBC. We need both an upstream Composer issue filed and an issue in our issue queue.
Comment #21
Wim LeersComment #23
phenaproximaComment #24
Wim Leers