mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #628] Composer lockfile problem #427
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#427
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ksieluzycki on GitHub (Sep 26, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/628
Originally assigned to: @jasonmunro on GitHub.
Hello,
During installation I encountered following error from composer install:
No vendor dir present, checking platform requirements from the lock file
In Locker.php line 324:
[LogicException]
No lockfile found. Unable to read locked packages
I thought it should create composer lock if necessary, but it didn't. I also tried composer update, but it also shows same error and does not create composer lock.
It looks like check-platform-reqs is invoked as pre-command and it requires composer lock. I just edited composer.json:
After that composer install completed succesfully.
Tested on:
Composer version 2.4.2 2022-09-14 16:11:15
on Debian 11.5 and on Artix
Regards,
Krzysztof
@jasonmunro commented on GitHub (Sep 26, 2022):
Appreciate the feedback. We have been discussing removing this from the composer.json file as I ran into the same issue. In my case I had scripted an update process that was calling composer as root. Once I modified that it started working even with the check-platform-reqs active.
@marclaporte commented on GitHub (Nov 1, 2022):
Closing in favor of: