I can see my latest releases in Packagist but when I install the package it uses an older one and trying to install using the version number gives "Could not find package..." error.
Example:
I create a new release and push to GitHub.
I scan in Packagist and it finds the new release.
I install the package and it installs an older release and can't find the new one.
Link to Package: https://packagist.org/packages/3cwebdev/drupal-composer-install
Link to GitHub repo: https://github.com/3CWebDev/drupal-composer-install
v1.13.0 is the latest release but it always installs 1.10
Related
We are using blobfuse version 1.0.2 and would like to upgrade it to latest version like 1.3.1. How we can upgrade it to latest version without uninstalling and reinstalling blobfuse ?
I see you may raise the issue in github here.
And the answer is that:
now 1.3.2 is the latest. At this time you can clone the source could and build it, command git clone https://github.com/Azure/azure-storage-fuse. It will create an azure-storage-fuse directory, if you run ./build.sh from this dir it will create a blobfuse binary in the build directory. you can mount just like an installed version Eg: ./build/blofuse ~/blobfusemntdir --tmp-path=< your path>
I have WSL 18.04 (Ubuntu) and I want to use NuGet.exe to install a Nuget Package to a folder (not .csproj) using the code below:
nuget install Test.Nuget.Version -OutputDirectory packages
In WSL, I use sudo apt install nuget. However that will only install an old nuget version 2.8.xxx in Ubuntu. =(
In order to run nuget install command, I must use the latest version of NuGet version (5.x.x) installed in Ubuntu.
Is it possible to install latest NuGet version in Ubuntu?
If yes, how can I do so?
Normally you can get nuget to update itself:
nuget.exe update -self
However recently, because I assume they have updated the min TLS version, one can get the following error:
The authentication or decryption has failed.
Error while sending TLS Alert (Fatal:InternalError): System.IO.IOException:
So your nuget version has to be new enough to upgrade itself.
So you have to get a new nuget.exe by alternative means:
curl https://dist.nuget.org/win-x86-commandline/latest/nuget.exe -o nuget.exe
I tried to update my gitlab-CE from 10.3.2 to the latest one (currently the 11.4). And it gives me this honestly safe error.
[...]
gitlab preinstall: It seems you are upgrading from 10.x version series
gitlab preinstall: to 11.x series. It is recommended to upgrade
gitlab preinstall: to the last minor version in a major version series first before
gitlab preinstall: jumping to the next major version.
gitlab preinstall: Please follow the upgrade documentation at https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations
gitlab preinstall: and upgrade to 10.8 first.
dpkg: error processing archive /var/cache/apt/archives/gitlab-ce_11.2.3-ce.0_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/gitlab-ce_11.2.3-ce.0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root#this-vm# apt-cache policy gitlab-ce | grep Installed
Installed: 10.3.2-ce.0
But how to install to the latest minor version ? The documentation they are referring to, doesn't say how to do it.
Do you guys encounter any problem like this ?
Try to update to the latest minor version as suggested here:
apt-get update
apt-get install gitlab-ce=<YOUR-LATEST-MINOR-VERSION>-ce.0
gitlab-ctl reconfigure
gitlab-ctl restart
In your case latest minor is: 10.8.6 [as of today].
You can check the release list.
Remember to check the changes between your initial and target versions.
For CentOS/RHEL reference:
To install minor version on (CentOS/RHEL). Follow below steps.
To update minor version on 11.xx to latest version of 11.11.5:
sudo yum install gitlab-ce-11.11.5-ce.0.el6.x86_64
Similarly for all other version, You can find the specific version/install command you need to use at https://packages.gitlab.com/gitlab/gitlab-ce. Search for a version string such as gitlab-ce-11. Click on the RPM or Deb package for your OS version, then you will see all version of gitlab where you can findout latest version name and install it as stated above but just replace it with your minor version name i,e. gitlab-ce-11.11.5-ce.0.el6.x86_64
Upgrading from one version to another version should be followed as per the recommendation below or official page here.
12.7.5 -> 12.10.5
11.3.4 -> 11.11.1
10.6.6 -> 10.8.3
11.3.4 -> 11.11.8
10.6.6 -> 10.8.7
9.2.3 -> 9.5.5
8.9.4 -> 8.12.3
Always recommended that first upgrade to the latest available minor version within your major version and then upgrade it next stable version.
I was trying to update our existing gitlab-ce version 11.2.1 to latest gitlab-ce 12.2.0. After installing the 12.2.0 using yum update when I tried gitlab-ctl reconfigure. I got the error saying you need to install gitlab 11.0.0 first.
So, I removed the gitlab 12.2.0 and installed the 11.0.0 version using
yum remove gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
wget https://ftp.sjtu.edu.cn/sites/gitlab-ce/yum/el7/gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
rpm -Uvh gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
gitlab-ctl reconfigure
sudo gitlab-ctl restart
The process was successful, My old data was there and I could login with my old credentials. The version in front-end was showing 11.0.0. Now to get to latest version I did
gitlab-ctl stop
yum remove gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
wget https://ftp.sjtu.edu.cn/sites/gitlab-ce/yum/el7/gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
rpm -Uvh gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
gitlab-ctl reconfigure
gitlab-ctl restart
I got on version 12 but then I got another error the alermanager service was not starting so I added the following block to /etc/gitlab/gitlab.rb
alertmanager['flags'] = {
'cluster.advertise-address' => "127.0.0.1:9093",
}
I restarted the gitlab and everything was running.
gitlab-ctl restart
`enter code here`Check the latest version
1.sudo gitlab-rake gitlab:env:info:If it is above 13.12.0 then proceed with step 3.If its below please follow serially.
2."sudo apt upgrade gitlab-ee=13.12.5-ee.0": Update to any version of 13.12.x.
3.sudo apt-get update
4.sudo apt-get install gitlab-ee
Improving this answer, if you need to install/update manually, all you have to do is:
Download the required package here https://packages.gitlab.com/gitlab/gitlab-ee/
Run rpm -Uvh packageName.rpm
gitlab-ctl reconfigure
gitlab-ctl restart
You are good to go.
A useful tool now exists that a allows you to set the current and desired version. The tool then tells you the intervening versions you need to install in order to upgrade (please note that you Must apply the versions in a specific order as some updates make database changes later updates rely upon)
Link to Gitlab upgrade path
I'm trying to run Kubernetes on a local Centos server and have had some issues (for example, with DNS). A version check shows that I'm running Kubernetes 1.2 Alpha 1. Since the full release is now available from the Releases Download page, I'd like to upgrade and see if that resolves my issue. The documentation for installing a prebuilt binary release states:
Download the latest release and unpack this tar file on Linux or OS X, cd to the created kubernetes/ directory, and then follow the getting started guide for your cloud.
However, the Getting Started Guide for Centos says nothing about using a prebuilt binary. Instead, it tells you to set up a yum repo and run a yum install command:
yum -y install --enablerepo=virt7-docker-common-release kubernetes
This command downloads and installs the Alpha1 release. In addition, it attempts to install Docker 1.8 (two releases down from the current 1.10), which fails if Docker is already installed.
How can I install from a prebuilt binary and use an existing Docker?
According to the Table of Solutions for installing Kubernetes, the maintainer of the CentOS getting started guide is #coolsvap. You should reach out to him to ask about getting the pre-built binary updated to the official release.
I have patched and recompiled a debian package. By default when I upgrade, apt wants to upgrade it with the SAME version from the repository instead.
Now, I want to convince it (by using apt-pinning, and not hold) to keep the local package if the version is the same, and try to upgrade only if the remote version is newer.
How can I do that?
Just make a local revision and upgrade the version, something like:
dch -v 1.0-1local1
Then pin that version.