-
Notifications
You must be signed in to change notification settings - Fork 46
Conversation
…nd created a default layer vanilla variant selection
…ged dockerfile in accordance with docker build changes
The upgrade fails (even with apt-get upgrade --with-new-pkgs):
The problem can be later fixed with |
Something like that works as a one-liner (but it is ugly):
|
I think the problem here might be that your version is 6.17.0-0.20171127154954gitb76a638 which is newer than the known "split version" in packages/xroad/debian/control: "Breaks: xroad-common (<= 6.17.0-0.20171018082348git2ecf68ed)" That got confusing. Let me know if you want clarification on it. The installation should work fine for releases, since the comparison is larger than the latest release (6.16). It's the development builds that will break until they have the control file updated with the latest possible non-split build. One solution would be jumping to version 6.17.1 or higher I guess instead of doing the control file fixes until everyone has the split packages. |
As soon as it does not affect real users upgrading from release version then it is OK. I just tested upgrading from 6.16 and it worked properly. |
Hi! You have renamed the file xroad-common.xroad-confclient.upstart → xroad-confclient.xroad-confclient.upstart, but in .gitignore it still exists (packages/xroad/debian/xroad-common.xroad-confclient.upstart). |
Ok, thanks for spotting this @kristoheero. We will correct this and it will be included in our next pull request. |
PVAYLADEV-861: Migration for modified configuration properties to ensure backwards compatibility
Changelist
Additional notes about the xroad-common package split
On Ubuntu machines, X-Road packages should be updated with
apt-get upgrade --with-new-pkgs
so that the new packages are installed during the update. As an alternative to you can useapt upgrade
which installs new dependencies by default. After update please verify that all the installed X-Road packages have the same version (e.g. 6.17.0).