[intrepid] some packages still depend on dummy package libcupsys2

Fixed the problem for xpp and flphoto.

This bug was fixed in the package libnet-cups-perl - 0.55-3ubuntu1

---------------
libnet-cups-perl (0.55-3ubuntu1) intrepid; urgency=low

  * Transition from libcupsys2 to libcups2 (lp: #279345):
    - Build-depend on libcups2-dev
    - Suggest cups-common
    (This changes can be dropped in jaunty as the current Debian package has
     them already)

 -- Michael Bienia <email address hidden> Thu, 09 Oct 2008 21:29:35 +0200

This bug was fixed in the package eggcups - 0.20-0ubuntu2

---------------
eggcups (0.20-0ubuntu2) intrepid; urgency=low

  * Rebuild for libcupsys2 -> libcups2 transition (lp: #279345).

 -- Michael Bienia <email address hidden> Thu, 09 Oct 2008 21:37:36 +0200

This bug was fixed in the package fox1.4 - 1.4.34-1ubuntu1

---------------
fox1.4 (1.4.34-1ubuntu1) intrepid; urgency=low

  * Transition from libcupsys2 to libcups2 (lp: #279345):
    + debian/control: Replace libcupsys2-dev with libcups2-dev.

 -- Michael Bienia <email address hidden> Thu, 09 Oct 2008 21:44:47 +0200

This bug was fixed in the package fox1.6 - 1.6.25-1ubuntu1

---------------
fox1.6 (1.6.25-1ubuntu1) intrepid; urgency=low

  * Transition from libcupsys2 to libcups2 (lp: #279345):
    + debian/control: Replace libcupsys2-dev with libcups2-dev.

 -- Michael Bienia <email address hidden> Thu, 09 Oct 2008 21:47:27 +0200

could you not use a bug which lists lot of task to handle transitions but rather opens different bugs and tag those?
the issue has already been discussed but your way to use this bug sends a comment for every change to everybody subscribed to any of the component listed there which means lot of mails for no good reason

Sebastian, I'm not sure who opened the task for each package; I just opened it for Ubuntu and asked about linking. Next time I'll open separate bugs from the start.

Sebastian, since we're on the subject, there are a couple hundred non-transitional packages which depend on transitional ones:

$ aptitude search '?depends(~dtransitional)?not(~dtransitional)'|wc -l
243

It seems a huge job for someone to go through all of those, verify them (the query it's probably not very precise) and create separate bugs for each. I think it would be more appropriate to create a generic bug like this one, which lists the problem and the query. Bug-fixers would just take the query and fix whatever they can, and perhaps add separate bugs for each issue they fix. Then, when the number of packages involved gets to a few dozen we can create the rest of the bugs. What do you think?

do you really think that's trying to clean those transitionnal binary now is the best use of the efforts we can do before intrepid? I would let those being fixed during a normal cycle and not bother opening bugs for everything listed there

kde4libs fixed in 4:4.1.2-0ubuntu5

This bug was fixed in the package lsb - 3.2-20ubuntu1

---------------
lsb (3.2-20ubuntu1) jaunty; urgency=low

  * Resynchronise with Debian (cups dependency change fixes LP: #279345).
    Remaining changes:
    - Don't conflict with python (>= 2.6).
    - Depend on postfix rather than exim4 as preferred mail-transport-agent
      alternative.
    - Depend on libgl1-mesa-glx rather than libgl1-mesa as preferred libgl1
      alternative.
    - Add Ubuntu logging functions.
  * Revert some apparently unintentional dependency changes on the Ubuntu
    side of the merge: move libncurses5 and libpam0g dependencies back from
    lsb-base to lsb-core; set lsb's dependencies on lsb-printing,
    lsb-multimedia, and lsb-languages back to suggestions; and remove lsb's
    suggestion of lsb-qt4.

lsb (3.2-20) unstable; urgency=low

  * Revert change in 3.2-16 that broke killproc due to my misunderstanding
    of the spec. (Closes: #495587)
  * pidofproc now also checks for /var/run/$base.pid if -p is not specified,
    fixing conformance with the spec.

lsb (3.2-19) unstable; urgency=low

  * Return 0 in log_failure_msg too.

lsb (3.2-18) unstable; urgency=low

  * Also fix case where stdout isn't color-capable. (Closes: #493505, again)

lsb (3.2-17) unstable; urgency=low

  * log_{success,failure,warning}_msg suck, please don't use them for
    Debian scripts. Nonetheless, breakage fixed. (Closes: #493505)

lsb (3.2-16) unstable; urgency=low

  * Add a bugscript to lsb-release to help figure out why people keep
    getting very strange results.
  * Lenny will be Debian 5.0, not Debian 4.1; fix accordingly.
  * Improve output of lsb-specified logging functions; deal with
    in-the-wild variations that omit messages.
  * No longer use --retry in start-stop-daemon calls. (Closes: #451529)
  * Fix behavior of killproc and pidofproc when no pidfile is passed in.
  * Call pidof with -x to include scripts that may be daemonized.
  * Change dependencies *cupsys* -> *cups*. (Closes: #490381)

lsb (3.2-15) unstable; urgency=low

  * Add Basque [eu] translation. (Closes: #491005)
  * Fix log_action_end_msg_pre function definition (_post was defined twice).
    (Closes: #491087)

 -- Colin Watson <email address hidden> Sun, 02 Nov 2008 23:48:49 +0000

Fixed in latest scribus-ng (jaunty)

Fixed in jaunty

Fixed with latest merge.