[pve-devel] from wheezy to jessie upgrade issue

[Alexandre DERUMIER]

So, I think that the deb package should deploy to the symlink 5.20


/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/PVE/IPCC/IPCC.so



----- Mail original -----
De: "lyt_yudi" <lyt_yudi at icloud.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "moula BADJI" <moulab1 at hotmail.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 9 Mars 2015 06:09:50
Objet: Re: [pve-devel] from wheezy to jessie upgrade issue





在 2015年3月9日，上午11:35，Alexandre DERUMIER < aderumier at odiso.com > 写道： 

Looking at proxmox pve-cluster package, 
they are a IPPC.so deployed in 

/usr/lib/x86_64-linux-gnu/perl5/5.20.1/auto/PVE/IPCC/IPCC.so 


(5.20.1 not 5.20) 




yes, here: 

# ls -l 
total 8 
lrwxrwxrwx 1 root root 6 Mar 2 06:35 5.20 -> 5.20.2 
drwxr-xr-x 3 root root 4096 Mar 7 20:50 5.20.1 
drwxr-xr-x 32 root root 4096 Mar 7 20:18 5.20.2 

# ls -l 5.20.1/auto/PVE/IPCC/ 
total 12 
-rw-r--r-- 1 root root 10336 Mar 4 17:14 IPCC.so 

# ls -l 5.20.2/auto/PVE/IPCC/ 
ls: cannot access 5.20.2/auto/PVE/IPCC/: No such file or directory 

I’m copy that to 5.20.2 dir, it’s solove. 

# cp -r 5.20.1/auto/PVE 5.20.2/auto/ 

…... 
The following partially installed packages will be configured: 
libpve-access-control librados2-perl proxmox-ve-3.10.0 pve-cluster pve-firewall pve-manager qemu-server 
No packages will be installed, upgraded, or removed. 
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 
Need to get 0 B of archives. After unpacking 0 B will be used. 
Setting up pve-cluster (4.0-1) ... 
Setting up libpve-access-control (4.0-1) ... 
Setting up librados2-perl (1.0-2) ... 
Setting up pve-firewall (2.0-1) ... 
Installing new version of config file /etc/init.d/pvefw-logger ... 
Setting up qemu-server (4.0-2) ... 
Setting up pve-manager (4.0-2) ... 
Installing new version of config file /etc/init.d/pve-manager ... 
Setting up proxmox-ve-3.10.0 (4.0-29) ... 
installing proxmox release key: OK 
….. 

thanks again.