Problem/Motivation

The latest release introduces a dependency "landrok/activitypub": "dev-headers", but dev-headers doesn't exist.

Steps to reproduce

Proposed resolution

Maybe that dependency should be entirely removed, looking into #3590589: Switch back to landrok/activitypub?

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork activitypub-3590800

Command icon 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:

About issue forks

Comments

jurgenhaas created an issue. See original summary.

jurgenhaas opened merge request !79

jurgenhaas’s picture

jurgenhaas
he/him
Primary language German
Location Gottmadingen
commented
Status: Active » Needs review

Would be great if we could get a fresh alpha with this, so that we can install it easily.

jurgenhaas’s picture

jurgenhaas
he/him
Primary language German
Location Gottmadingen
commented

Ah, wait, I just realized that the project defined a temporary repository in its composer.json:


  "repositories": [
    {
      "type": "vcs",
      "url": "https://github.com/swentel/activitypub_landrok"
    },
  }

The problem is, that doesn't work for Drupal sites, because the repository definition only works in the root composer.json. Repositories from dependencies are ignored.

swentel’s picture

swentel commented

The problem is, that doesn't work for Drupal sites, because the repository definition only works in the root composer.json. Repositories from dependencies are ignored.

Darn, didn't know that. I only tested it in running composer install in the AP folder - and because the test bot worked fine, I more or less assumed everything was ok.

Not sure what the best option is, I really do need that version as it contains changes which haven't been merged yet with the main repository of that package. I'll see if I can push that one further today!

swentel’s picture

swentel commented

Tracking this in #3590589: Switch back to landrok/activitypub also.

jurgenhaas’s picture

jurgenhaas
he/him
Primary language German
Location Gottmadingen
commented

Not sure what the best option is

You could probably publish your temporary package on packagist.org with a 0.0.1 version under your namespace. Then, you can remove that again later, when the official package is ready.

The testbot didn't capture it because it runs the projects composer.json as root project.