[pve-devel] trying to upgrade wheezy -> jessie + corosync1 ->corosync2

Alexandre DERUMIER aderumier at odiso.com
Wed Apr 29 13:41:05 CEST 2015


>>I'm retrying upgrade again, 

Ok, it's working fine with

#apt-get update 
#apt-get remove clvm 
->(upgrade libpve-storage-perl automaticaly) 
#apt-get dist-upgrade 
#apt-get install clvm (redhat cluster suite has been uninstall, so no libdlm3 conflict anymore).


Then only missing things is pve-manager configuration

Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Paramétrage de pve-manager (4.0-2) ...
Failed to get D-Bus connection: Erreur inconnue -1

(any idea ? maybe because of systemd not running ?)


and old corosync process not killed after uninstall of redhat-cluster-suite





----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 29 Avril 2015 13:33:39
Objet: Re: [pve-devel] trying to upgrade wheezy -> jessie + corosync1 ->corosync2

>>But we always provided an upgrade script in previous releases. That script can 
>>simply remove those conflicting packages before you run the upgrade. 
>>Would that work? 

Yes,It should work 

I'm retrying upgrade again, 

it's seem that 

#apt-get update 
#apt-get remove clvm 
->(upgrade libpve-storage-perl automaticaly) 
#apt-get dist-upgrade 

is working 

Need to do more tests to be sure 

----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Mercredi 29 Avril 2015 13:20:43 
Objet: Re: [pve-devel] trying to upgrade wheezy -> jessie + corosync1 ->corosync2 

> This dependency come from clvm package 
> 
> from which depend (old) libpve-storage-perl version. (not yet updated). 
> 
> forcing install of libpve-storage-perl with dpkg -i --force .deb seem to 
> resolve it. 
> 
> Maybe adding a trick like "provides: clvm " in a proxmox package could work ? 

IMHO such hacks are very fragile. 

But we always provided an upgrade script in previous releases. That script can 
simply remove those conflicting packages before you run the upgrade. 
Would that work? 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 



More information about the pve-devel mailing list