| 1 | | broder knows what's going on. broder, please edit this description. |
| | 1 | If you do a do-release-upgrade from a libzephyr3 release to a libzephyr4 one, you lose. |
| | 2 | |
| | 3 | 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. |
| | 4 | |
| | 5 | 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. |
| | 6 | |
| | 7 | 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. |
| | 8 | |
| | 9 | (This allows us to accommodate the eventuality where zephyr 3 gets backported to Hardy + Jaunty) |
