Skip to main content

PHP Composer does not report reason for choosing to skip a version of a package. Why / How to change?

I'm going crazy here. I have a custom platform that I deploy to projects via composer. My new version is version v3.6.29. It turns out that one of my new dependencies for this project got a random $ character inserted into the middle of the package name (due to my fat fingers) in the composer.json file of the platform, which basically broke it.

I went to the site I wanted to install this new version for and did composer update vendor/pkg-name and it goes through and checks and just says its has nothing to update... but I know for a fact there is an update. So obviously there is some reason it chose not to install the new version...

BUT WHY?

You would think composer would be smart enough to think that I might want to know the reason it chose not to update to to the latest compatible version, right? I guess not! But How can I force this in the future?

I tried composer update -vvv vendor/pkg-name and that literally told me nothing new.

I also tried composer why-not and composer prohibits for my package and received no useful information.

The only way I was able to find out what the problem was, was by doing:

rm -rf vendor;
rm -rf composer.lock;
vim composer.json
-- Change version of my platform from "~3.6.0" to the specific version I wanted to install, "3.6.29"
-- Save / Quit Vim
composer install

And then I finally get this output:

  Problem 1
    - Root composer.json requires vendor/pkg-name 3.6.29 -> satisfiable by vendor/pkg-name[v3.6.29].
    - vendor/pkg-name v3.6.29 requires vendor2/pkg$name2 ^2.8 -> could not be found, it looks like its name is invalid, "$" is not allowed in package names.

I mean do you think, maybe, quite possibly, that I might want to know this is the reason that it would not upgrade to the latest version? Maybe not, I guess in a normally scenario the installer might not care about the reason but from my point of view as the developer of said package that is refusing to install to the latest I want to know why its skipping it.

My questions is simply this: When composer refuses to install the version of a package you want, and that you know exists, but is not telling you WHY, how can you FORCE it to explain it's self when it decides to fall back to a version that is "acceptable" to it rather than the optimal version?

I feel like jumping through the hoops I had to jump through to figure out the problem cannot possibly be the best way to accomplish this? What am I missing here?

Thanks in advance.



source https://stackoverflow.com/questions/68957959/php-composer-does-not-report-reason-for-choosing-to-skip-a-version-of-a-package
Labels:

Comments

Post a Comment

Popular posts from this blog

Where and how is this Laravel kernel constructor called? [closed]

Where and how is this Laravel kernel constructor called? public fucntion __construct(Application $app, $Router $roouter) { } I have read the documentation and some online tutorial but I can find any clear explanation. I am learning Laravel and I am wondering where does this kernel constructor receives its arguments from. "POSTMOTERM" CLARIFICATION: Here is more clarity.I have checked the boostrap/app.php and it is only used for boostrapping the interfaces into the container class. What is not clear to me is where and how the Kernel class is instatiated and the arguments passed to the object calling the constructor.Something similar to; obj = new kernel(arg1,arg2) or, is the framework using some magic functions somewhere? Special gratitude to those who burn their eyeballs and brain cells on this trivia before it goes into a full blown menopause alias "MARKED AS DUPLICATE". To some of the itchy-finger keyboard warriors, a.k.a The mods,because I believe in th...
Post a Comment
Read more

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...
Post a Comment
Read more

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype
Post a Comment
Read more