Flow 9.1.1 can not find utility packages

Using Neos & Flow
1

In a DDEV setup using PHP 8.5 and the following composer.json

{
    "name": "project/distribution",
    "config": {
        "vendor-dir": "Packages/Libraries",
        "bin-dir": "bin",
        "sort-packages": true,
        "allow-plugins": {
            "neos/composer-plugin": true
        }
    },
    "require": {
        "neos/flow": "9.1.1"
    },
    "repositories": {
        "packages": {
            "type": "path",
            "url": "./src/*"
        }
    },
    "scripts": {
        "post-update-cmd": "Neos\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
        "post-install-cmd": "Neos\\Flow\\Composer\\InstallerScripts::postUpdateAndInstall",
        "post-package-update": "Neos\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall",
        "post-package-install": "Neos\\Flow\\Composer\\InstallerScripts::postPackageUpdateAndInstall"
    }
}

The composer installation fails with reference to `neos/utility-mediatypes` despite the version being available here from packagist.org neos/utility-mediatypes - Packagist.org

    - Root composer.json requires neos/flow 9.1.1 -> satisfiable by neos/flow[9.1.1].
    - neos/flow 9.1.1 requires neos/utility-mediatypes 9.1.1 -> found neos/utility-mediatypes[3.2.0, ..., 3.3.x-dev, 4.0.0, ..., 4.3.x-dev, 5.0.0, ..., 5.3.x-dev, 6.0.0, ..., 6.3.x-dev, 7.0.0, ..., 7.3.x-dev, 8.0.0, ..., 8.4.x-dev, 9.0.0-beta1, ..., 9.2.x-dev] but it does not match the constraint.

Anything in the internal infrastructure that needs a “kick” or how come this error appear?

2

More infor: Running the command `composer outdated -a` displays the mediatypes as not being available as `9.1.1`

image
image1422×310 51.4 KB

3

Hi @sorenmalling .

I’ve tested that with DDEV PHP8.5 and don’t have any issues. Is this issue still present?

image
image1115×336 12.3 KB

4

Same command, new day, new result

Today I was able to update to Flow 9.1.1

But… doesn’t explain the issue of a single package not being available in the composer universe :slight_smile:

5

Really odd, but i had that same glitch with composer and a Neos.Neos package lately. It did show up on packagist but i could not require it even after various cache flushes. Only logging in as admin on packagist to update the package worked. That funnyness seems to be something on packagists side …

@lubitz maybe the automatic packagist webhook refresh calls by github are insufficient and we should add an additional layer of webhook calls explictly from our side to the jenkins. It would be unsual practice but obviously either github or packagist fools us every now and then with not updating our packages - especially during the subsplits where there are so many packages updated in a short time.

6

I assume some eventual consistency on the packagist side here. Also just had a package where packagist listed the latest version but it took half a day until composer found that version regardless how many caches I flushed.