Create a new release to support D10

Created on 16 January 2023, over 1 year ago
Updated 20 April 2023, about 1 year ago

Problem/Motivation

Currently the dev-version of this module supports D10.
Seems like a great time to create a new release?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium JeroenT πŸ‡§πŸ‡ͺ

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States kevinquillen

    Is anyone looking into this? I can find some time this month if not.

  • πŸ‡§πŸ‡ͺBelgium JeroenT πŸ‡§πŸ‡ͺ

    Thank you, @kevinquillen!

  • First commit to issue fork.
  • Status changed to Fixed about 1 year ago
  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Not sure yet what's wrong (can't find a bug in the commit), but composer refuses to download ^2.2 for Drupal 9.5.7
    8.x-2.1 is kept.

    Is anyone else experiencing the same?

  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    No, but when you have such an issue, you always want to explicitly require that version with "composer require drupal/media_entity_download:2.2", and then check what kind of conflict it reports.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    @Berdir: Thanks for the hint!

    I tried that:
    composer require drupal/media_entity_download:2.2 -W:

    Loading composer repositories with package information
    Updating dependencies
    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - Root composer.json requires drupal/media_entity_download 2.2, found drupal/media_entity_download[dev-1.x, dev-2.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.0-beta1, 2.0.0, 2.1.0, 2.x-dev (alias of dev-2.x)] but it does not match the constraint.
    
    
    Installation failed, reverting ./composer.json and ./composer.lock to their original content.
    

    while /admin/modules/update definitely shows the update to be available.

    Also I tried:

    composer require drupal/media_entity_download:^2.2
    ./composer.json has been updated
    Running composer update drupal/media_entity_download
    Gathering patches for root package.
    Loading composer repositories with package information
    Updating dependencies
    Lock file operations: 0 installs, 1 update, 0 removals
      - Upgrading drupal/media_entity_download (2.1.0 => dev-2.x eeff52c)
    Writing lock file
    Installing dependencies from lock file (including require-dev)
    Package operations: 0 installs, 1 update, 0 removals
      - Syncing drupal/media_entity_download (dev-2.x eeff52c) into cache
    Gathering patches for root package.
    Gathering patches for dependencies. This might take a minute.
      - Removing drupal/media_entity_download (2.1.0)
      - Installing drupal/media_entity_download (dev-2.x eeff52c): Cloning eeff52caea from cache

    So I ran composer cc to clear caches and tried both again. Same results.
    All other modules update as expected. Strange.

  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    Works fine for me, what about doing the same in a new drupal composer template with nothing else?

  • πŸ‡©πŸ‡ͺGermany webflo

    @Anybody try to run "composer why-not drupal/media_entity_download 2.2.0"

  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    Well, per #10, 2.2 is not reported as a valid version at all in that error, so no idea what's going on, but I don't think why-not will be able to tell you more?

    1.2k users already updated to 2.2 per https://www.drupal.org/project/usage/media_entity_download β†’ , no idea what's wrong with your site, do you have a custom repository set or so, maybe you used a merge request once?

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thanks @Berdir and @webflo. To be honest, I have no idea yet, never had that problem before. But I'll find and fix it :)
    And hopefully I'll be able to tell you about the reasons here.

    My intention was primarily to let you know, if the same happens to other users, but that doesn't seem to be the case. So, all good. Thank you very much!

  • πŸ‡©πŸ‡ͺGermany stefan.korn Jossgrund

    Hi, I am having the same problem as described by Anybody. So far no clue, why it is happening.

  • πŸ‡©πŸ‡ͺGermany stefan.korn Jossgrund

    I see composer (with verbose output) going to https://packages.drupal.org/files/packages/8/p2/drupal/media_entity_down... - If I am checking this in my browser there is no version 2.2 there. Can this maybe be some sort of cache issue on the packages.drupal.org end? Varnish? maybe regionally depending? Anybody and myself are both from Germany.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thanks @stefan.korn!
    Perhaps a new 8.x-2.3 tagged release could simply fix this. Or not... the question is, if it's worth a try or use this case to find out the deeper reason.

  • πŸ‡©πŸ‡ͺGermany stefan.korn Jossgrund

    Yes, one can probably wait a bit, if this got resolved on its own after some time.

    If everything fails, we might use the dev version instead (which works on my end, getting the latest changes).

    Anyway, this seems to be more of an drupal infrastructure issue and not the fault of this module.

  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    I have this now as well, this looks indeed like a new infrastructure issue.

    - Root composer.json requires drupal/media_entity_download 2.2, found drupal/media_entity_download[dev-1.x, dev-2.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.0-beta1, 2.0.0, 2.1.0, 2.x-dev (alias of dev-2.x)] but it does not match the constraint.

    I guess I still had 2.2 in my local composer cache?

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024