libaxis2c symlinks madness makes for a bad upgrade experience
Bug #426752 reported by
Soren Hansen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| axis2c (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez | ||
| Karmic |
Fix Released
|
Medium
|
Thierry Carrez | ||
| rampart (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez | ||
| Karmic |
Fix Released
|
Medium
|
Thierry Carrez | ||
Bug Description
Axis2/C and Rampart/C traditionally would install into /opt. The Ubuntu
packages were made to be FHS compliant, but applications using Axis2/C
and Rampart still assumed the old, /opt style directory layout. As a
means to make ends meet, a lot of symlinks were added to make things
appear in the expected places for everyone. Specifically, I used
directory symlinks. Due to the way dpkg deals with this on upgrades,
people upgrading from 1.5.0-* to 1.6.0-* ended up with a barely
functional package. The only workaround is to remove the package
completely and install it again.
At the very least, we should start using file-only symlinks, so that
upgrades from now on will be painless.
| description: | updated |
Revision history for this message
| Chris Jones (cmsj) wrote | #1 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
Revision history for this message
| Soren Hansen (soren) wrote Re: [Bug 426752] Re: libaxis2c symlinks madness makes for a bad upgrade experience | #3 |
| Changed in axis2c (Ubuntu Karmic): | |
| assignee: | Soren Hansen (soren) → Canonical Server Team (canonical-server) |
| Changed in rampart (Ubuntu Karmic): | |
| assignee: | Soren Hansen (soren) → Canonical Server Team (canonical-server) |
| Changed in axis2c (Ubuntu Karmic): | |
| status: | In Progress → Triaged |
| Changed in rampart (Ubuntu Karmic): | |
| status: | In Progress → Triaged |
| Changed in axis2c (Ubuntu Karmic): | |
| assignee: | Canonical Server Team (canonical-server) → Thierry Carrez (ttx) |
| status: | Triaged → In Progress |
| Changed in rampart (Ubuntu Karmic): | |
| assignee: | Canonical Server Team (canonical-server) → Thierry Carrez (ttx) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in axis2c (Ubuntu Karmic): | |
| status: | In Progress → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in rampart (Ubuntu Karmic): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
If this is the same issue I saw, the resulting symlinks were barely functional enough to start things that link against libaxis (ldd against /usr/lib/
This meant that Eucalyptus init scripts couldn't start, so package upgrades failed and the only way to complete the upgrade from jaunty to karmic was to purge libaxis2c0 and re-install it.