D10: Update recommendation for Bean (drupal/bean)

Created on 29 February 2024, 4 months ago
Updated 5 March 2024, 4 months ago

Problem/Motivation

Project url: https://www.drupal.org/project/bean β†’

This module has been previously vetted for Drupal 9 with the following snippet added to curated.json:

        {
            "package": "drupal/bean_migrate",
            "constraint": "1.0.0",
            "patches": {
                "Issue #3199294: Remove source count caching workaround when core issue is resolved": "https://www.drupal.org/files/issues/2022-06-24/bean_migrate-remove_source_count_caching_workaround-3199294-14.diff",
                "Issue #3200943: Remove custom block config destination when core issue 3200936 is resolved": "https://www.drupal.org/files/issues/2021-03-01/bean_migrate-remove_block_config_destination-3200943-3.patch",
                "Issue #3200951: Remove custom block_content entity destination plugin when core issue 3200949 gets resolved": "https://www.drupal.org/files/issues/2021-03-01/bean_migrate-remove_custom_block_content_destination-3200951-2.patch",
                "Issue #3354022: Tests fail since Drupal 9.5": "https://www.drupal.org/files/issues/2023-04-21/3354022-4.patch"
            },
            "install": [
                "bean_migrate",
                "block_content"
            ],
            "replaces": [
                {
                    "name": "bean"
                },
                {
                    "name": "bean_entitycache"
                },
                {
                    "name": "bean_admin_ui"
                },
                {
                    "name": "bean_usage"
                },
                {
                    "name": "bean_uuid"
                }
            ],
            "vetted": true
        },

Since this module does not need a Drupal 8+ counterpart (as blocks are entities now and support fields) all this needs to do is migrate things in using core blocks + types

Steps to reproduce

n/a

Proposed resolution

Re-vet the module to determine if the same recommendation applies, or if things need to be updated.

Remaining tasks

  1. Install a fresh D7 site
  2. Set up Bean + add content
  3. Create new D10 codebase using acli
  4. Create D10 site, run migrations via AM:A
  5. Verify the content and types are in place
  6. Run test - tests/src/FunctionalJavascript/BeanMigrationTest.php - by opening a sibling MR against 1.9.x and altering AMA__10__RECOMMENDATIONS__VERSION in the .gitlab-ci.yml file

User interface changes

n/a

API changes

n/a

Data model changes

n/a

πŸ“Œ Task
Status

Needs work

Version

1.9

Component

Recommendations β€” Drupal 10

Created by

πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dan612
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    I installed the latest version of Bean on my Drupal 7 site and set up a new "Hero banner" block type:

    Here it is on the front end attached to my home page Main Content region:

    There is no newer release of Bean Migrate β†’ and as such the recommendation should be the same. When I went to run the acli command I was met with the following:

    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - zendframework/zend-feed[dev-master, dev-develop, 2.11.0, ..., 2.13.x-dev] require php ^5.6 || ^7.0 -> your php version (8.1.27) does not satisfy that requirement.
        - laminas/laminas-feed[2.12.0, ..., 2.12.x-dev] require php ^5.6 || ^7.0 -> your php version (8.1.27) does not satisfy that requirement.
        - symfony/psr-http-message-bridge[v1.1.0, ..., 1.1.x-dev] require php ^5.3.3 || ^7.0 -> your php version (8.1.27) does not satisfy that requirement.
        - symfony/psr-http-message-bridge[v1.2.0, ..., v1.3.0] require php ^7.1 -> your php version (8.1.27) does not satisfy that requirement.
        - drupal/core[8.9.11, ..., 8.9.x-dev] require php ^7.0.8 -> your php version (8.1.27) does not satisfy that requirement.
        - laminas/laminas-feed[2.13.0, ..., 2.14.x-dev] require php ^7.3 || ~8.0.0 -> your php version (8.1.27) does not satisfy that requirement.
        - drupal/core[9.0.10, ..., 9.0.x-dev] require php ^7.3 -> your php version (8.1.27) does not satisfy that requirement.
        - Root composer.json requires drupal/bean_migrate 1.0.0 -> satisfiable by drupal/bean_migrate[1.0.0].
        - Root composer.json requires drupal/color ^1 -> satisfiable by drupal/color[1.0.1, 1.0.2, 1.0.3, 1.x-dev].
        - drupal/bean_migrate 1.0.0 requires drupal/core ^8.8 || ^9 -> satisfiable by drupal/core[8.8.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev].
        - You can only install one version of a package, so only one of these can be installed: drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.3.x-dev, 11.x-dev].
        - You can only install one version of a package, so only one of these can be installed: drupal/core[8.7.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].
        - drupal/core-recommended 10.2.3 requires drupal/core 10.2.3 -> satisfiable by drupal/core[10.2.3].
        - Only one of these can be installed: drupal/core[8.0.0-beta12, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.4.3, 10.0.0-alpha1, ..., 10.0.0-alpha6], drupal/color[1.0.1, 1.0.2, 1.0.3, 1.x-dev]. drupal/core replaces drupal/color and thus cannot coexist with it.
        - drupal/core[9.0.0-alpha1, ..., 9.0.0-alpha2] require symfony/psr-http-message-bridge ^1.2.0 -> satisfiable by symfony/psr-http-message-bridge[v1.2.0, v1.3.0].
        - drupal/core[8.9.0-beta1, ..., 8.9.10] require symfony/psr-http-message-bridge ^1.1.2 -> satisfiable by symfony/psr-http-message-bridge[v1.1.2, 1.1.x-dev, v1.2.0, v1.3.0].
        - drupal/core[8.8.0-alpha1, ..., 8.8.x-dev] require zendframework/zend-feed ^2.12 -> satisfiable by laminas/laminas-feed[2.12.0, ..., 2.23.x-dev], zendframework/zend-feed[2.12.0, 2.12.x-dev, 2.13.x-dev].
        - Root composer.json requires drupal/core-recommended 10.2.3 -> satisfiable by drupal/core-recommended[10.2.3].
    

    It appears this module cannot be installed via composer at the moment without Composer Lenient using this patch πŸ“Œ Drupal 10 compatibility Needs work

    πŸ€” not sure what to do here. Is this hard blocked until the Bean Migrate composer.json file is updated?

  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • Merge request !45#3424757: Update bean recommendation β†’ (Open) created by dan612
  • Pipeline finished with Failed
    4 months ago
    Total: 177s
    #107426
  • Status changed to Needs review 4 months ago
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • Pipeline finished with Failed
    4 months ago
    Total: 186s
    #107427
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    Now CI can feel my pain as well 😁

      Problem 1
        - drupal/drupal[8.4.0-alpha1, ..., 8.7.x-dev] require composer/installers ^1.0.24 -> found composer/installers[v1.0.24, ..., 1.x-dev] but it conflicts with your root composer.json require (^2.0).
        - drupal/bean_migrate 1.0.0 requires drupal/core ^8.8 || ^9 -> satisfiable by drupal/drupal[8.4.8, 8.5.15, 8.6.18, 8.7.14].
        - Root composer.json requires drupal/bean_migrate 1.0.0 -> satisfiable by drupal/bean_migrate[1.0.0].
    
  • Status changed to Needs work 4 months ago
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    πŸ“Œ D10: Update recommendation for Field Group (drupal/field_group) Fixed landed, this needs a reroll.

    Also: can you please create a "test MR"? πŸ™

  • Pipeline finished with Failed
    4 months ago
    Total: 125s
    #111884
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

    I took care of

    1. this needs a reroll
    2. Also: can you please create a "test MR"? πŸ™

    Will get going on the latter half of comment #8 πŸ“Œ D10: Update recommendation for Bean (drupal/bean) Needs work

  • Pipeline finished with Failed
    4 months ago
    Total: 187s
    #111894
  • Pipeline finished with Failed
    4 months ago
    Total: 638s
    #111888
Production build 0.69.0 2024