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
--trust-gpg-keys
option for update
#296
Comments
That is correct. Given that to
That should certainly not be the case: If you have an installed version in the phive.xml, that very version is (or should at least) be reinstalled. That's the exact and sole reason to have that information tracked. On update it should update to whatever is latest that still falls into the range defined by the constraint.
Looks like we're indeed lacking documentation for that. We very much do support that: |
We're storing the So the 'user' running the update won't usually be the same as the one initially installing. Also, as this is an automated process, there is no-one to press Y; we are using (We need to be able to run different versions of PHPUnit depending on the PHP version, because there isn't a version compatible with both PHP 7.2 and PHP 8.)
Starting with the following entry in <phar name="phpunit" version="^7.5.20" installed="7.5.20" location="./tools/phpunit.phar" copy="true"/> I run phive install phpunit The <phar name="phpunit" version="^9.4.3" installed="9.4.3" location="./tools/phpunit" copy="false"/> The version in `tools' is not updated but a batch file (this is on Windows) is created linking to version 9.4.3 installed for the current user. Not sure if that's what's supposed to happen. However, if I were to instead run |
Interesting use case. Let me think about it. I'm still not convinced, as I don't see this as preferable or even viable process:
As your main problem is that your CI run doesn't have the required public key in its key ring because the original install occurred on a different system, you could simply fix that by having the key imported directly using
The above command tells For now: If you merely want to re-create the state configured in
I see why that is happening and I agree that is probably at least surprising if not wrong: It previously was installed using
Yes. The later indeed seems correct. |
It seems this option is only available for
install
and not forupdate
.But
install
will install the latest version and ignore version constraints set inphive.xml
, and there doesn't seem to be a way of specifying version constraints on the command line (at least I can't see anything listed when runningphive
without parameters to get the built-in help).The text was updated successfully, but these errors were encountered: