Can't Install Azure IoT Edge RC4 on redhat - azure-iot-edge

Error: Package: aziot-edge-1.2.0-0.1.rc4.el7.x86_64 (/aziot-edge-1.2.0-0.1.rc4.el7.x86_64)
Requires: aziot-identity-service >= 1.2.0-0.1.rc4
Installed: aziot-identity-service-1.2.0~rc4-1.x86_64 (#/aziot-identity-service-1.2.0.rc4-1.x86_64)
aziot-identity-service = 1.2.0~rc4-1

The iotedge team recently made a change to fix this problem. If you remove the packages and try again I think it should work.

Related

Why vcpkg can't install packages?

When I try to install matplotlib-cpp using vcpkg, the console always returns Computing installation plan..., then nothing happens. After that, I checked the installation package with .\vcpkg list. It seems that this package has not been installed.
I also tried to install other packages and encountered the same situation.
Environment:
Windows 10, 64 bit build 19042
Visual Studio 2019
cmake 3.21.0-rc2
Git
The scene where the problem occurred
We also ran into this. Extremely painful to find as CMake seems to work otherwise. If you use vcpkg at all I would advise not trying CMake 3.21.0 until this is fixed.

"error: #error "OpenCV 4.x+ requires enabled C++11 support"

How can I fix this?
I installed OpenCV 4.1.0 without a problem on Centos 7.6 following this guide:
https://linuxize.com/post/how-to-install-opencv-on-centos-7/
Now I'm trying to install php-opencv
https://github.com/hihozhou/php-opencv
And it's failing when I make. (Under the Compile and install php-opencv extension header on that link).
Many thanks, COMPLETELY out of my depth here.

Is there support for an easy install of the runtime on a Suse Linux Enterprise Server 12?

We are running SLES 12 servers. I wanted to install the Azure Iot Edge Runtime on our machines. So far there is no easy way (rpm package). Are there plans to add support for OpenSuse and SLES 12 SP2?
https://github.com/Azure/azure-iotedge/releases
You can find platform support for Azure IoT Edge here: https://learn.microsoft.com/en-us/azure/iot-edge/support
If your platform is not listed there, you can nevertheless try and install Azure IoT Edge Runtime and report issues here: https://github.com/azure/iotedge/issues .
I would also suggest that you fill a new feature request here: https://feedback.azure.com/forums/907045-azure-iot-edge
Thanks!
You can find one approach to build and install the IoT Edge runtime on SLES 12 from https://github.com/vjrantal/iotedge-suse-build.
The approach in that repository is to build the .rpm packages of the runtime using Docker and then use zypper to install those packages to the target host based on SLES 12.

Jenkins problems with ruby-runtime v0.12

After an upgrade got a red box in jenkins:
There are dependency errors loading some plugins:
When I visit plug in page: there are no upgrades available:
When I visit Available tab, Ruby run-time is already installed with 0.12 version and there are no updates for the Gitlab Hook Plugin
How do I fix this?
I had the same issue on Ubuntu 16.04 + with openjdk 9. I switched to oracle JDK 8, the plug-in installed properly.
Check the plug-in if it's installed. It wasn't installed with gitlab plug-in install for me.
Hope this helps !
In case of windows issue with Jenkins try reinstall Jenkins from "Program Files x86" to C:\Jenkins.
This solved issue with GitLab Hook and Ruby-runtime plugins.

How can I get the signature of the update version of NuGet to match he installed version?

Im using Visual Wb Developer 2012 Express. I'm trying to update NuGet. Inside the error log i find this:
Install Error : VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
at VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
at VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)
How can i get the signature of the update version of NuGet to match he installed version?
Nuget's had some issues with upgrades requiring the user first uninstall the old addin, and then installing the new version fresh. Give that a shot. Upgrades after that should be ok.

Resources