Closed seth-shaw-unlv closed 3 years ago
Any takers, @Islandora/8-x-committers?
i can give it a whirl if you'd like - anything in particular i should look for?
Nope. It should be ready to go. I just need a Drupal 9 compatible release so I can get my ArchivesSpace module updated too.
Although a smoke test never hurts!
Upgrade status is returning 2 warnings:
Controlled Access Terms, --
Scanned on Mon, 11/16/2020 - 15:42
FILE:
web/modules/contrib/controlled_access_terms/tests/src/Kernel/EdtfUtilsTest.php
STATUS LINE MESSAGE
--------------------------------------------------------------------------------
Check manually Class PHPUnit\Framework\TestCase not found.
--------------------------------------------------------------------------------
Check manually 15 Class PHPUnit\Framework\TestCase not found.
--------------------------------------------------------------------------------
Huh... I wonder how it missed that before. 😕
Thanks.... I'll see what I can do.
@elizoller, do you have devel installed on the test box? See https://www.drupal.org/project/upgrade_status/issues/3137754.
@seth-shaw-unlv The changes visible at Files changed make sense with respect to compatibility to Drupal 9 but I look at the composer patch I'd need to apply https://patch-diff.githubusercontent.com/raw/Islandora/controlled_access_terms/pull/58.patch it includes a bunch of other changes around controlled_access_terms_defaults config yml's and field changes. Am I driving composer wrong?
i did drush pm-uninstall devel
and re-ran drush us-a controlled_access_terms
and got the same output - is that what you meant by having 'devel' installed?
@kayakr, I believe your patch was based on an older commit. The master→main commit that contains a bunch of these changes was back in September.
@elizoller, huh... no devel should be installed: drush en -y devel
.
devel was enabled before. did drush pm-enable devel
and drush us-a controlled_access_terms
and got the same error. i'll try another build.
@kayakr, I believe your patch was based on an older commit. The master→main commit that contains a bunch of these changes was back in September.
https://patch-diff.githubusercontent.com/raw/Islandora/controlled_access_terms/pull/58.patch is a patch based on your current PR. What I'm seeing is the changes included in https://github.com/Islandora/controlled_access_terms/compare/8.x-1.x...seth-shaw-unlv:8.x-1.x - did you rebase your fork before making the Drupal 9 changes?
@kayakr, oh! I see that now. I thought I had rebased my branch before I made the changes... and the github interface is only showing what I changed... but maybe I didn't rebase and Github is glossing over that.
Controlled Access Terms, -- Scanned on Mon, 11/16/2020 - 16:03
No known issues found.
This is with the Islandora box from dev.
Ah, I simply did a merge upstream (see https://github.com/Islandora/controlled_access_terms/pull/58/commits/720e64ec81d675822ad129dc320fa8669ad9a17c), instead of a rebase.
Controlled Access Terms, -- Scanned on Mon, 11/16/2020 - 16:03
No known issues found.
This is with the Islandora box from dev.
🎉 At least it isn't just me. 😅
then ignore me - debbie, review and merge?
Ah, for future reference, @elizoller,
Adding drupal/core-dev
In order to be able to run Drupal core's PHPUnit test suite, you will have to install an additional metapackage, drupal/core-dev.
Thanks, @dflitner!
thank you @seth-shaw-unlv that did the trick and thanks @dflitner for swooping in with the merge
GitHub Issue: Resolves https://github.com/Islandora/documentation/issues/1679
What does this Pull Request do?
Drupal 9 readiness.
What's new?
core_version_requirement: ^8 || ^9
.How should this be tested?
composer require drupal/geolocation:^3.2 drupal/token:^1.7
composer require 'drupal/upgrade_status:^3.0' && drush en -y devel upgrade_status && drush us-a controlled_access_terms
Interested parties
@Islandora/8-x-committers, esp @kayakr