Bug #1164

Reversioning of RST breaks existing installations

Added by Anonymous almost 12 years ago. Updated almost 12 years ago.

Status:ResolvedStart date:09/11/2012
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:-

Description

Current rst-trunk is now building debian package version 0.8, which was previously package and lib version 2.0 as far as I understand. All existing installations won`t get updates any more because the old package 2.0 is treated more up-to-date than the new 0.8.

So all packages we built on our CI server are now linked against librst.so.0.8, but existing installations will keep having librst.so.2.0 installed. This will break installations for all external partners (eg. our AMARSi users).

History

#1 Updated by Anonymous almost 12 years ago

So, the issue could be sort-of solved. Michael G. and myself did:
  1. Deleting all rst-2.0 packages from the package server
  2. Running rst-trunk-package job to have version rst-0.8 distributed to the server
  3. We will have to do the same for the package mirror of our external partner EPFL
After that, users with existing installations including rst will have to
  1. Remove rst package from their system (eg. sudo apt-get remove rst). This will of course also kick all depending packages
  2. Delete the local apt package cache (eg. sudo apt-get clean). Otherwise the locally cached rst-2.0 will get reinstalled
  3. Reinstall rst or depending packages, this will then install rst-0.8.

Note: We definitely have to be more careful in the future when it comes to our deployment, especially the rsx packages. Lots of people (even external partners) and continuously deployed packages are depending on that now.

#2 Updated by S. Wrede almost 12 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Not nice but works for me!

@Arne: Are you going to tell the AMARSi users about this or do we wait until we got the next version ready?

Also available in: Atom PDF