Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

composer install gives error #4

Closed
chaosarium opened this issue Jan 7, 2022 · 4 comments
Closed

composer install gives error #4

chaosarium opened this issue Jan 7, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@chaosarium
Copy link

chaosarium commented Jan 7, 2022

Hi!

Great to see this project going again!

Describe the bug
Unable to install dependencies.

To Reproduce
I tried the installation instructions in readme by running composer install hugofara/lwt

That gave me the error Invalid argument hugofara/lwt. Use "composer require hugofara/lwt" instead to add packages to your composer.json., so I ran composer require hugofara/lwt and got this:

❯ composer require hugofara/lwt

Installation failed, deleting ./composer.json.

In RequireCommand.php line 210:

  No composer.json present in the current directory (./composer.json), this may be the cause of t
  he following exception.


In InitCommand.php line 907:

  Could not find a version of package hugofara/lwt matching your minimum-stability (stable). Requ
  ire it with an explicit version constraint allowing its desired stability.

Specifying version by running composer require hugofara/lwt:dev-master gives this:

❯ composer require hugofara/lwt:dev-master
./composer.json has been created
Running composer update hugofara/lwt
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires hugofara/lwt dev-master -> satisfiable by hugofara/lwt[dev-master].
    - hugofara/lwt dev-master requires aehlke/tag-it ^2.0 -> could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, deleting ./composer.json.

Switching to the dev-dev version and testing on Linux result in the same error

Expected behavior
composer install hugofara/lwt simply works

Desktop:
PHP version: tested on both 7.4.3 on Ubuntu 20.04.3 with Firefox and 7.4.12 on MacOS 12.0.1 with Safari and Vivaldi
Composer version: 2.2.3 on Ubuntu 20.04.3 with Firefox and 2.3-dev on MacOS 12.0.1 with Safari and Vivaldi

Unfortunately, I know little about PHP and couldn't figure out how to resolve the issue. But I'm really looking forward to seeing the future of this project!

@HugoFara
Copy link
Owner

HugoFara commented Jan 7, 2022

Hi!

Thank you for this review! I created the composer file a bit early, and I no time to really test it... However I can figure out quite well what is happening, it should be a short time before it gets solved.

Bug 1: composer install not working

The problem is that composer uses git tags to get the versions (v2.0.4 or 2.0.4) however I used v2.0.4-fork and that prevents composer from setting the version properly. I should publish v2.1.0 next week, solving this problem. The stable version of this package is in fact empty, which is why the ./composer.json file is missing.

Bug 2: composer dev install not working

But your other remark brings significant change. For unstable version (dev install), this is an unexpected bug. Thank you for noticing it, it should be quickly solved in a bug-fix release v2.0.5. The technical issue is that no ./composer.json is in the required repo, the practical problem is that the repo has been dead for 8 years now.

I'm resurrecting this project from ashes because I see potential in it. Yet I'm crawling into dead dependencies and a decade of stagnation into a fast changing environment. If you want to help me a bit, your issues give me good hints on where to act next. Please consider starring the repository, because it is my only mean of advertising for now ;)

@HugoFara HugoFara self-assigned this Jan 7, 2022
@HugoFara HugoFara added the bug Something isn't working label Jan 7, 2022
@chaosarium
Copy link
Author

Thanks for the reply and all your work! I am still having issue getting 2.0.4 installed properly so I haven't done much testing yet.

As I use lwt on a daily basis, I am happy to do some testing if I have time (already starred the repo). There's been lots of issue with this old programme but I see no better alternative. Since I don't know PHP, I did my best working around some of the issues by changing the HTML and CSS. Also, I'm not a developer and I'm new to open source projects with more than one contributer. However, I might be able to contribute to improving the user interface. I feel like this might be a good topic for a discussion thread(?)

@HugoFara
Copy link
Owner

HugoFara commented Jan 9, 2022

Hi!

I just released v2.1.0 that should solve the issues. Does it work for you?

If you want to suggest an enhancement, you can create a new issue. If you don't have a precise idea look at the discussions tab, which is a free chat ;)

Enjoy!

@chaosarium
Copy link
Author

Hi!

Thanks for the update. v2.1.0 works now! However, there seems to be a path issue after composer require as I reported in #5.

I think this issue can be closed now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants