- This needs a team bug subscriber for whichever team is looking after
this.  ~unity-api-team?

- libzmqpp-dev should probably depend on libzmq3-dev (not libzmq5-dev).
The 3 version is a replacement for the deprecated 5 version, it seems.
Plus that would make the Build-Depends and the Depends consistent.  Not
a blocker, just saying.

- This isn't in Debian, which puts all the maintenance burden on the
above team.  Is there a reason they don't have it?

- There's a patch ("mkdir_before_install.diff") that's not being used.
Is that obsolete?

** Changed in: zmqpp (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zmqpp in Ubuntu.
https://bugs.launchpad.net/bugs/1617005

Title:
  [MIR] zmqpp

Status in zmqpp package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe.

  [Rationale]
   * This package is required by unity-scopes-api.

  [Security]
   * No known security issues at this time, it has been in active use on our 
touch devices since a very long time already.

  [Quality assurance]
   * This package comes with a set of unit tests that are all being run during 
build-time.

  [Dependencies]
   Most dependencies are already in main, with only a small nitpick:
   * libboost-test-dev is in universe, but its source boost-defaults is already 
in main.
   * zeromq3 has a MIR filled as well 
(https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1597439)

  [Maintenance]
   * This package is used by Canonical upstream projects so the packaging is 
maintained by Canonical. The upstream code is actively maintained and developed 
by the zeromq team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1617005/+subscriptions

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

Reply via email to