$ ./change-override -c main -B cpdb-backend-cups
Override component to main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic: universe/net -> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic amd64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic arm64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic armhf: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic ppc64el: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic riscv64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic s390x: universe/net/optional/100% 
-> main
Override [y|N]? y
7 publications overridden.


** Changed in: cpdb-backend-cups (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cpdb-backend-cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747760

Title:
  [MIR] cpdb-backend-cups

Status in cpdb-backend-cups package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Already in universe

  Built for all supported architectures

  [Rationale]

  The Common Printing Dialog Backends (CPDB) project of OpenPrinting is
  about separating the print dialogs of different GUI toolkits and
  applications (GTK, Qt, LibreOffice, ...) from the different print
  technologies (CUPS/IPP, Google Cloud Print, ...) so that they can get
  developed independently and so always from all applications one can
  print with all print technologies and changes in the print
  technologies get supported quickly.

  If one opens the print dialog, the dialog will not talk directly to
  CUPS, Google Cloud Print, or any other printing system. For this
  communication there are the backends. The dialog will find all
  available backend and sends commands to them, for listing all
  available printers, giving property/option lists for the selected
  printers, and printing on the selcted printer. This communication is
  done via D-Bus. So the backends are easily exchangeable and for
  getting support for a new print technology only its backend needs to
  get added.

  [Security]

  No known security issues, no CVEs for cpdb-backend-cups known.

  The backends are triggered via session D-Bus and always run as the
  same user as the calling print dialog, so they do not introduce
  additional security problems.

  The separation of the communication with individual print technologies
  makes this code only be needed once (in the appropriate backend)
  instead of in each print dialog. This simplifies the security
  maintenance.

  [Quality assurance]

  - The Ubuntu Printing Team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups
  https://github.com/OpenPrinting/cpdb-backend-cups/issues

  No upstream tests or autopkgtests.

  [Dependencies]

  Depends on cpdb-libs, MIR in bug 1747759.

  [Standards compliance]

  The package meets the FHS and Debian Policy standards (4.1.0)

  [Maintenance]

  - Actively developed upstream. Last release was 1.0.0
  https://github.com/OpenPrinting/cpdb-backend-cups/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups/+bug/1747760/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to