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.
The new twitter version 6 depends on oauth_common but not on oauth, drush doesn't know about the connection so I recommend adding a dependency on oauth module.
Comment | File | Size | Author |
---|---|---|---|
#10 | twitter-n1967798-10.patch | 1.49 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaNot sure what can be done about this because the OAuth project was poorly named. Maybe this might help?
Comment #2
DamienMcKennaTriggering the testbot.
Comment #3
DamienMcKennaTriggering the testbot.
Comment #4
DamienMcKennaClosed a duplicate: #2355833: Twitter incorrectly requires oauth_common
Comment #5
steinmb CreditAttribution: steinmb commentedI suggest we do nothing. This module is not the only one seeing this problem.
Had a look into https://github.com/drush-ops/drush/blob/master/commands/pm/pm.drush.inc
Comment #6
DamienMcKennaIt's more of a core Drupal limitation than a problem with Drush: #2205271: Project namespace for dependencies
Comment #7
steinmb CreditAttribution: steinmb commentedAh thanks :) Should we put this issue to 'postponed' until there is working D7 backported?
Comment #8
DamienMcKennaI'm not sure the issue will be resolved for D7, I think we could do a workaround until then. Would you mind giving the patch a try? Thanks.
Comment #9
steinmb CreditAttribution: steinmb commentedNo big difference running from drush.
Comment #10
DamienMcKennaI finally tested this, and yes, it doesn't work. The reason for this is that hook_requirements() is ran after the info file's dependencies are tested, so we could either remove the line from the info file and use the patch or just deal with it :-\
This patch updates the instructions in README.txt to note the module name conflict.
Comment #12
steinmb CreditAttribution: steinmb commentedWhat does this sentence actually mean?
Why do you not think the core issue will be fixed for D7? It is tagged with a "needs backport" and found nothing in the comments it that indicate that I will not be back ported.
Comment #16
DamienMcKennaCommitted. I removed the line from the 7.x branches and rewrote it for the 6.x branch so it actually made sense.