Please allow kdeaddons 4:3.3.2-4 into sarge

[Ben Burton <bab@debian.org>]

Hi,

I recently uploaded kdeaddons 4:3.3.2-4, as well as 4:3.3.2-3 a week
earlier, neither of which made the 10-day wait before the freeze was
announced.

The relevant changelog entries are:

  kdeaddons (4:3.3.2-4) unstable; urgency=low

    * Replaced vimpart's long list of GUI vim dependencies with the single
      (vim-gtk | gvim).  This removes an indirect (and unnecessary) conflict
      between vimpart and the new vim-full package, and should avoid similar
      such problems in the future (closes: #306538).

   -- Ben Burton <bab@debian.org>  Sun,  1 May 2005 13:41:04 +1000

  kdeaddons (4:3.3.2-3) unstable; urgency=low

    * Made the default vimpart dependency vim-gtk (closes: #304189).
      Previously it was kvim, but kvim has since been removed from debian.
    * Added a note in vimpart.README.Debian that the above change may require
      you to reconfigure your vimpart in the control centre.
    * Don't use 'libsuff=64' on amd64 or ppc64 (closes: #301794).

   -- Ben Burton <bab@debian.org>  Mon, 25 Apr 2005 23:08:18 +1000

The actual patches are quite small.  Moreover, I'm eager to see these
changes in sarge because they address some recent changes in binary vim
packages.  Specifically, the vimpart package (built from kdeaddons)
needs some flavour of gvim installed (any will do) in order to operate.
The issues are:

- kvim has been removed completely.  This was previously the default
  gvim in a long list of alternatives for vimpart's dependencies.  It was
  dropped in 4:3.3.2-3 and vim-gtk was instead chosen as the new default.

- vim-full was added a little over a week ago, and has already made it
  into sarge.  Since the various flavours of gvim conflict with each
  other and vim-full was not in the dependency list for vimpart, this
  meant that vimpart essentially conflicted with vim-full (because
  whichever gvim you chose for the vimpart would conflict with
  vim-full).  Such a conflict is unnecessary (not only can vimpart be
  installed with vim-full just fine, but it can operate with it).  This
  issue was addressed in the 4:3.3.2-4 upload, with the long list of
  gvim alternatives replaced by a single dependency on the virtual
  package gvim (thus catching vim-full and avoiding similar problems in
  the future).

I'm particularly eager to get this into sarge because of the unnecessary
(and unpleasant) indirect conflict with vim-full, which was resolved in -4.
If could you could consider moving this package into testing it would be
much appreciated.

Thanks - Ben.