I had a zypper install fail because in the process, it try to allocate 4.7 Gb and fails. Already it had allocated about 3gb. Then the actual install of the rpms was to take place.
My swap space is only about 4Gb.
Earlier I had tried to install using 2 repositories, the DVD and a KDE one. It failed because zypper seemed to be using an index of some other repository. That is when I tried to install with just the DVD. The uri on the comand line also failed to point to the DVD. I just went into yast2 and made the dvd the only active repository.
zypper and the 13.1 install have some serious bugs.
I also tried to install from booting the DVD. It would not recognize my luks partiitions even after providing the key.
This 13.1 install should be considered beta, not a release.
I was upgrading from 12.2 which is no longer supported. It may have been factory 12.2. I typed “zypper dup -l” I had the dvd in the drive and not mounted. I had tried to specify the uri earlier and it would not take it. I looked at the documentation for that and the 13.1 install. That is where I found out that I could use zypper. It asked me some questions to satisfy dependencied. Then it gave me a summary of the number of packages that are going to be upgraded, downgraded etc. Then I think it was going to start installing the rpms. My computer slowed down and almost locked up. It took me a long time to get top up and running in another console. I watched the memory usage gradually increase to about 3 Gb. Then my dinner was ready and I had to leave. When I came back I found the zypper process crashed after trying to allocate about 3.7Gb of memory which is more than my swap drive had. I can capture it all and make a log if someone is interested. I could even run strace. The file would be large though.
And it says, although not prominently, that you can not use that method
to upgrade from 12.2 to 13.1. Only from one version to the next, and the
previous version has to be fully updated.
> or maybe I could just use rpm with a script and install all the updated
Some people have managed to do it, but the procedure is not trivial nor
safe. Basically you have to manually update first zypper, rpm, and the
affected stack, and then maybe zypper dup succeeds. I can not guide
you with the details, sorry: as I consider it unsafe I’m not familiar
with its details.
Or, apply an offline upgrade instead. This one is often capable of
repairing a broken upgrade. Not always, but often.
But you say:
> I also tried to install from booting the DVD. It would not recognize my
> luks partiitions even after providing the key.
If the system is encrypted and is not recognized, that’d bad news and a
different issue. You have to find out first if the partitions are
mountable and readable, otherwise… caput.
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)