On Sun, Dec 19, 2010 at 07:30:48PM +0100, Bill Allombert wrote: > Package: cyrus-sasl2-dbg > Version: 2.1.23.dfsg1-7 > Severity: important > > Hello Debian Cyrus SASL Team, > > There is a circular dependency between cyrus-sasl2-dbg, > cyrus-sasl2-heimdal-dbg > and cyrus-sasl2-mit-dbg: > > cyrus-sasl2-dbg :Depends: cyrus-sasl2-mit-dbg, cyrus-sasl2-heimdal-dbg > cyrus-sasl2-heimdal-dbg :Depends: cyrus-sasl2-dbg (= 2.1.23.dfsg1-7) > cyrus-sasl2-mit-dbg :Depends: cyrus-sasl2-dbg (= 2.1.23.dfsg1-7) > > Circular dependencies are known to cause problems during upgrade, so we > should try to get rid of them. > > In that case, since the packages are build from the same source, I do not see > much point to having three packages if the user is required to install all of > them anyway. > Bill,
Please see #601977 and let me know if you still feel the same way. Basically, the dependency from cyrus-sasl2-dbg is on "cyrus-sasl2-mit-dbg | cyrus-sasl2-heimdal-dbg", while the two specific -dbg packages depend on the main package. Basically, if a user installs the cyrus-sasl2-dbg, we want them to also get the specific symbols for one of MIT or Heimdal. This also takes care of a bug in the Lenny -> Squeeze upgrade process (reported in #601977). However, if the user goes the route of installing either cyrus-sasl2-mit-dbg or cyrus-sasl2-heimdal-dbg, then we also need to make sure that they get the common -dbg symbols. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
