Unable to install base distribution on a new machine

Using Neos & Flow Flow App Development
1

Hello all!

As you know I’ve installed many flowbased applications on several server. :wink:

Now on our new Ubuntu 24.04 LTS with PHP 8.5.3, installation of Flow 8.3.x/8.4.x/9.x fails and I don’t know why (composer is V. 2.9.5).

I.e. install base distribution with

composer create-project --keep-vcs neos/flow-base-distribution . 8.4.2

Fails with

Root composer.json requires neos/welcome ~8.4.0, found neos/welcome[8.4.x-dev] but it does not match your minimum-stability

Fixed this with editing composer.json to

“neos/welcome”: “~8.4.x-dev”

Now all packages are downloaded but after that tons of:

Class Neos\Flow\Composer\InstallerScripts is not autoloadable, can not call post-package-install script

Ignoring this and execute

./flow core:setfilepermissions johndoe www-data www-data

ends up in

sudo: unable to resolve host machinex: Name or service not known
sudo: unable to resolve host machinex: Name or service not known
sudo: unable to resolve host machinex: Name or service not known
sudo: unable to resolve host machinex: Name or service not known
sudo: unable to resolve host machinex: Name or service not known
sudo: unable to resolve host machinex: Name or service not known

Note: I’m user root on this server!

(Of course the application is not reachable via web browser.)

I dont not have this problem in the past…

Any idea, was ist wrong here?

2

Hello @mexoona ,

I’ve fixed the missing package version. A release was missing there.

But I can’t reproduce the error:
sudo: unable to resolve host machinex: Name or service not known

This also doesn’t look like a Flow error message.

3

Hello Denny!

Thanks a lot!

I’ve done further investigations and solved two “sub problems”:

  • the unable to resolve host was due missing entry in /etc/hosts file
  • setfilepermissions itself does not set users and acls due to missing linux package “acl”

But the major problem with “… is not autoloadable …” persists. :frowning:

May be this is the initial failure:

- Installing neos/composer-plugin (2.1.3): Extracting archive
Class Neos\Flow\Composer\InstallerScripts is not autoloadable, can not call post-package-install script

- Installing behat/gherkin (v4.16.1): Extracting archive

- Installing symfony/process (v8.0.5): Extracting archiv

[...]

- Installing phpunit/phpunit (9.6.34): Extracting archive
Class Neos\Flow\Composer\InstallerScripts is not autoloadable, can not call post-package-install script

last message about 128 times …

4

Does this really cause errors in your installed Flow-Application? Or just the message while installation?

We’ve got these errors in our build-pipelines about 200-300 times. Composer tries to hit the InstallerScripts of Flow-Framework for every package it installs and this “Error” (more like a warning) occurs for every Package which is installed before the InstallerScripts are installed and callable.

In our case, composer also throws these messages. Nevertheless everything is installed well and works perfectly.

5

Hello Niklas!

Thank you for your remark! On my “researches” I’ve read about this behavior at “support.hostpoint.ch” → “Neos auf Managed Flex Server” too.

On CLI Flow installation worked already - only the web frontend seems not to work.

But my problem arises due to a dump Apache configuration failure: I’ve missed to set the “DocumentRoot” to

DocumentRoot …/example.com/htdocs/Web

(no “/Web” at the end). What a shame! :unamused_face: Lots of wasted hours to find the problem…

Thanks again!