On July 3, 2005 09:27, Adeodato Simó wrote: > > The real question is why the kde packages don't conflict with earlier > > kdm versions if they don't work with them... (not that kde had too few > > conflicts, how about a little backwards compatibility anyway?) > > This situation is mostly fixed in our SVN since Jun 9, but there has > not been another upload to experimental since then. .oO(Must implement > that svn post-commit hook that tags pending and attachs changelog > entry when closing a bug in SVN, like subversion (the pacakge) does.) > > We tightened the kdm dependency on kdebase-bin, which was the one > causing problems. As now kdm Depends: kdebase-bin (= ${Source-Version), > kdm will necessarily get upgraded whenever kdebase is. > > This, er, solves the problem after people upgrade to kdm 3.4.1. The > possibility of remaining with an un-upgraded 3.3.2 remains, but I > haven't decided what to do with that yet. Perhaps a one-time versioned > conflicts (kdebase-bin Conflicts: kdm (<< 4:3.4.1-2), what do you > think, Christopher?).
Seems fine to me! Cheers, Christopher Martin
pgph3fvmTiYLW.pgp
Description: PGP signature