Unable to do a binary upgrade

[Paul Klos]

On Monday 06 June 2011 22:19:59 Paul Klos wrote:
> Hi all,
> 
> I'm trying to do a (partially) binary installation using the instructions in the "Generating your own 00INDEX.rdf for installations or 
upgrades" 
> section of 1st.README.
> 
> The upgrade is from 2.3.1 to 2.3.2. My hardware is a powerpc (Excito Bubba|2) running Debian squeeze. It's not that powerful and a full 
> upgrade takes several days of compiling, which is why I'd be really happy if I could get the binary upgrade to work.
> 
> I downloaded the 2.3.2 source packages and linked all the binary packages into the same directory as per the instructions. Then I ran 
the 
> command:
> 
> sh install-kolab.sh -X
> 
> This created a new 00INDEX.rdf file, as expected.
> 
> Now, the new file is a lot bigger than the original one I downloaded: 464020 vs. 3512600 bytes, so 3.5M instead of 450k.
> 
> The new file has all the packages in it twice, both source and binary. If I run the upgrade it starts happiliy building "make" which I 
already 
> have as a binary package of the exact same version, as can be seen from the newly creatad 00INDEX.rdf (grep  "[<]rdf:Description" 
> 00INDEX.rdf | grep -i \"make):
> 
> <rdf:Description about="make-3.81-20080101" href="make-3.81-20080101.src.rpm">
> <rdf:Description about="make-3.81-20080101" href="make-3.81-20080101.ppc-bubba300-kolab.rpm">
> 
> I cancelled the upgrade process, but I'm kinda stumped now. What do I need to do to make it compile only the changed packages?
> 
> Thanks,
> 
> Paul
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users


Well, looks like I found it. I tried copying the binary packages into the working directory, instead of linking them. In a matter of minutes, I 
got output like this:

:::: /kolab/RPM/PKG/openpkg-20071227-20071227_kolab2.src.rpm ::::
:::: /kolab/RPM/PKG/openpkg-20071227-20071227_kolab2.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/make-3.81-20080101.src.rpm ::::
:::: /kolab/RPM/PKG/make-3.81-20080101.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/binutils-2.20-20091016.src.rpm ::::
:::: /kolab/RPM/PKG/binutils-2.20-20091016.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/gcc-4.2.2-20080101.src.rpm ::::
:::: /kolab/RPM/PKG/gcc-4.2.2-20080101.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/perl-5.10.0-20080103.src.rpm ::::
:::: /kolab/RPM/PKG/perl-5.10.0-20080103.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/openpkg-tools-1.4.6-20071231.src.rpm ::::
:::: /kolab/RPM/PKG/openpkg-tools-1.4.6-20071231.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/openssl-1.0.0d-20110222.src.rpm ::::
:::: /kolab/RPM/PKG/openssl-1.0.0d-20110222.src.rpm = 0 ::::
:::: /kolab/RPM/PKG/db-4.5.20.2-20070628_kolab1.src.rpm ::::
:::: /kolab/RPM/PKG/db-4.5.20.2-20070628_kolab1.src.rpm = 0 ::::

The upgrade saves the original /kolab/RPM/PKG directory to a different name, and then creates a new one, that holds links to the 
packages in the working directory. So if you start with linking the binary packages you already have, you end up with two links pointing to 
each other, and no real package anymore.

Paul