Warning: Unable to resolve dependency 'chocolatey'
When using the action today, the output is:
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'apache-httpd 2.4.55 constraint: chocolatey (>= 1.2.0)', 'cmake.install 3.27.4 constraint: chocolatey (>= 0.10.5)', 'php 8.2.10 constraint: chocolatey (>= 0.10.0)'
Unable to resolve dependency 'chocolatey': Unable to resolve dependencies. 'chocolatey 1.1.0' is not compatible with 'apache-httpd 2.4.55 constraint: chocolatey (>= 1.2.0)'.
Does it really try to install chocolatey itself?
I have also just started getting this error - but it was working well quite recently, like a week ago or so. Now, CygWin installation is failing in the same way.
Any news on this?
So it seems to me like some problem with CygWin repositories/mirrors:
I switched to the official CygWin install action, and specified manually some mirror. It worked. Than, after a while - it stopped working in the same way as this action. Initially, I thought that it is something due to mirror overuse by the CI (the build was executed several times), but then I had a look at the contents on the mirror - the signature files that were present when it was working (I checked!) were gone. So, it seems like some unfinished/invalid update of CygWin repositories(?) that propagates.
If it is so, this causes issues in case of every CygWin installation action (or whatever using CygWin's installer).
I believe the recent outage is the problem described in the Signature files missing thread on the Cygwin mailing list. Assuming that is the case, I think it should be resolved now, at least for most mirrors.
I still get "Unable to resolve dependency 'chocolatey'" messages--as I had before the recent problem started--but Cygwin is able to install and run again for me on CI with this action.
Yep, it seems it is working, now.
(I meant: the CygWin installer, as I wrote I started using a different action...).