Unable to apt-clone dist-upgrade from NCP 2.0 Beta 1

[Ben Klang]

Tonight I installed a fresh copy of Nexenta 2.0 Beta 1 from the ISO on the Nexenta.org website. The following output is observed while running apt-clone dist-upgrade:

(Reading database ... 28026 files and directories currently installed.)
Preparing to replace libncurses5 5.5-1nexenta5 (using .../libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb) ...
Unpacking replacement libncurses5 ...
ld.so.1: bash: fatal: relocation error: file /lib/libncurses.so.5: symbol main: referenced symbol not found
dpkg: warning - old post-removal script killed by signal (Killed)
dpkg - trying script from the new package instead ...
ld.so.1: bash: fatal: relocation error: file /lib/libncurses.so.5: symbol main: referenced symbol not found
dpkg: error processing /var/cache/apt/archives/libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb (--unpack):
 subprocess new post-removal script killed by signal (Killed)
Errors were encountered while processing:
 /var/cache/apt/archives/libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb

apt-clone then offers to roll back the failed upgrade. Full apt-clone output is attached.

[Ben Klang (bklang)]

After some discussion in IRC (Thanks rootard!) I was able to find a workaround. The problem appears to be that the pre/post scripts in the package call bash, which chokes on the newly installed libncurses library. Copying libncurses.so.5 to /tmp/nlulib and then installing the package works. I don't know if it is considered an acceptable solution to copy libncurses into nexenta-lu or not.

[Tim Spriggs (tim-tajinc)]

Erast is taking charge on the upgrade path from NCP1->NCP2.

This solution seems to work for both the older bash (pre-upgrade) and the newer bash (post-upgrade).

[unifiednick (nick-earnshaw)]

This solution doesn't work for me. Could it be I installed on x64, but changed to force 32-bit mode so I could use iscsi?

root@nas:/# cp /lib/libncurses.so.5 /tmp/nlulib
root@nas:/# apt-get install libncurses5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
  libgpmg1
The following packages will be upgraded:
  libncurses5
1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Need to get 178kB of archives.
After this operation, 49.2kB disk space will be freed.
Get:1 http://apt.nexenta.org hardy-unstable/main libncurses5 5.6+20071124-1nexenta3 [178kB]
Fetched 178kB in 2s (88.1kB/s)
(Reading database ... 28590 files and directories currently installed.)
Preparing to replace libncurses5 5.5-1nexenta6+64 (using .../libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb) ...
Unpacking replacement libncurses5 ...
ld.so.1: bash: fatal: relocation error: file /lib/libncurses.so.5: symbol main: referenced symbol not found
dpkg: warning - old post-removal script killed by signal (Killed)
dpkg - trying script from the new package instead ...
ld.so.1: bash: fatal: relocation error: file /lib/libncurses.so.5: symbol main: referenced symbol not found
dpkg: error processing /var/cache/apt/archives/libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb (--unpack):
 subprocess new post-removal script killed by signal (Killed)
Errors were encountered while processing:
 /var/cache/apt/archives/libncurses5_5.6+20071124-1nexenta3_solaris-i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Tim Spriggs (tim-tajinc)]

This fix should work if you are using apt-clone and you place /lib/libncurses.so.5 into /tmp/nlulib/.

[rk (rkasl)]

I did exactly that , but still have the same error. Please advice. Thanks.
.. this is on my system:
 ls -lah /lib/libncurses.so.5 lrwxrwxrwx 1 root root 17 Feb 15 20:02 /lib/libncurses.so.5 -> libncurses.so.5.5
I copy the actual file, but nothing, then I cp it to /tmp/nlulib/ and renamed it to libncurses.so.5, but nothing, ... maybe I should cp the actual file and then create the link as its in /lib

[rk (rkasl)]

based on IRC discussion about this subject, this worked at this point:
* wget http://apt.nexenta.org/dists/hardy-unstable/main/binary-solaris-i386/shells/bash_3.2-0nexenta17_solaris-i386.deb (to update bash)
* apt-get -f install (to meet dependencies)
* apt-clone --force-yes upgrade (to do the upgrade)

[David Bartley (dtbartle-csclub)]

On Mon, Feb 23, 2009 at 2:39 PM, rk <email address hidden> wrote:
> based on IRC discussion about this subject, this worked at this point:
> * wget http://apt.nexenta.org/dists/hardy-unstable/main/binary-solaris-i386/shells/bash_3.2-0nexenta17_solaris-i386.deb (to update bash)

I think you are missing 'dpkg -i bash_3.2-0nexenta17_solaris-i386.deb' here.

> * apt-get -f install (to meet dependencies)
> * apt-clone --force-yes upgrade (to do the upgrade)
>

-- David

[DevX (palma-victor)]

I just tried the procedure you have talked about and it worked for me with out a problem.

* wget http://apt.nexenta.org/dists/hardy-unstable/main/binary-solaris-i386/shells/bash_3.2-0nexenta17_solaris-i386.deb (to update bash)
dpkg -i bash_3.2-0nexenta17_solaris-i386.deb (install the bash package)
* apt-get -f install (to meet dependencies)
* apt-clone --force-yes upgrade (to do the upgrade)

[Andy Boyett (aboyett)]

I just did a clean install of NCP 2.0 b104 beta1 and an apt-clone dist-upgrade completed successfully and the machine rebooted into the new 2.0 RC1 based checkpoint. This bug appears to be resolved unless the original reporter was upgrading from NCP 2.0 b84 beta1.

[anilg (anil-verve)]

Fixed in the latest bits