[Bug 552004] Re: poldek: impossible to upgrade from i686 to x86_64

[Arkadiusz Miśkiewicz]

multilib = no in poldek.conf:

# rpm -q dos2unix
dos2unix-3.1-21.i686
[root at gucio ~]# poldek --cmd "install --reinstall dos2unix"
warn: RPM works in multilib mode, while poldek not
Loading [pndir]th...
Loading [pndir]th...
15660 packages read
Processing dependencies...
dos2unix-3.1-21 obsoleted by dos2unix-3.1-21
There are 1 package to install, 1 to remove:
I dos2unix-3.1-21
R dos2unix-3.1-21
This operation will use 2.3KB of disk space.
Need to get 12.1KB of archives (12.1KB to download).

Retrieving th::dos2unix-3.1-21.x86_64.rpm...
.............................. 100.0% [12.1K (12.1K/s)]                  
Executing rpm --upgrade --replacefiles --replacepkgs -vh --root /...
warning: /root/tmp/poldek-cache-root/ftp_ftp1.pld-linux.org.dists.th.PLD.x86.64.RPMS/dos2unix-3.1-21.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID e4f1bc2d
Preparing...                ########################################### [100%]
   1:dos2unix               ########################################### [100%]
[root at gucio ~]# rpm -q dos2unix
dos2unix-3.1-21.i686
dos2unix-3.1-21.x86_64

-- 
poldek: impossible to upgrade from i686 to x86_64
https://bugs.launchpad.net/bugs/552004
You received this bug notification because you are subscribed to PLD
Linux.

Status in PLD Linux Distribution: New

Bug description:
I have a i686 th system. Upgraded rpm and poldek (to poldek-0.30-0.20080820.23.40.x86_64). Fixed /etc/rpm/platform to contain x86_64 version.



Tried to use poldek to upgrade/switch to x86_64 packages BUT poldek shows no possible upgrades in poldek "llu" command.



What's worse doing "install --reinstall dos2unix" to make poldek switch i686 package to x86_64 one (that worked long time ago) it... installs dos2unix x86_64 version while still leaving i686 files and rpmdb information. So I end up with having both dos2unix installed (i686 and x86_64 in rpmdb) but files on filesystem are only from x86_64 version.



How can I migrate from i686 to x86_64 now with this silly behaviour?