Ticket #586 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

zephyr 2 to zephyr 3 distro upgrade makes you lose

Reported by: geofft Owned by:
Priority: normal Milestone: Summer 2010 (Lucid Deploy)
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description (last modified by broder) (diff)

If you do a do-release-upgrade from a libzephyr3 release to a libzephyr4 one, you lose.

Because debathena-zephyr-config et al. depend on libzephyr4-krb5 | libzephyr3-krb, the libzephyr3-krb you already had installed satisfies that dependency, meaning that nothing pulls in libzephyr4-krb5. When do-release-upgrade cleans up at the end of the upgrade, it doesn't remove libzephyr3-krb because it's still depended on by zephyr-config.

Meanwhile, because things like pidgin depend on some form of libzephyr4, you end up with both libzephyr3-krb and libzephyr4 (no -krb5), and you're sad.

The only fix I've been able to come up with is to create a debathena-libzephyr, which depends on libzephyr4-krb5 | libzephyr3-krb on releases that still have zephyr 2, and just libzephyr4-krb5 on releases that only have zephyr 3. And then depend on that everywhere we currently have a libzephyr4-krb5 | libzephyr3-krb dependency.

(This allows us to accommodate the eventuality where zephyr 3 gets backported to Hardy + Jaunty)

Change History

comment:1 Changed 11 years ago by broder

  • Description modified (diff)

comment:2 Changed 11 years ago by jdreed

  • Milestone changed from The Distant Future to Fall 2010

comment:3 Changed 11 years ago by andersk

What if we changed debathena-zephyr-config from

Depends: libzephyr4-krb5 | libzephyr3-krb, zephyr-clients, …

to

Depends: libzephyr4-krb5 | zephyr-clients (<< 3.0~), zephyr-clients (>= 3.0~) | libzephyr3-krb, zephyr-clients, …

?

comment:4 Changed 11 years ago by jdreed

  • Status changed from new to development

I implemented Anders' suggestion in r24727 and uploaded it to -dev. It appears to work. Testing is difficult, because update-manager will disable the development repo (because it doesn't know how to turn "jaunty-development" into "karmic-development"). However, re-enabling the repo right after update-manager disables it appears to work.

On a stock Jaunty debathena-standard, after upgrading to Karmic, I now have libzephyr4-krb5 installed.

comment:5 Changed 11 years ago by jdreed

  • Milestone changed from Fall 2010 to Summer 2010 (Lucid Deploy)

comment:6 Changed 11 years ago by broder

  • Status changed from development to proposed

This actually moved to proposed shortly after it went into production

comment:7 Changed 11 years ago by broder

This was actually still in -development, but it is now in -proposed.

comment:8 Changed 11 years ago by broder

  • Status changed from proposed to closed
  • Resolution set to fixed

Moved to production today, so this should be fixed.

Note: See TracTickets for help on using tickets.