Public bug reported:

Please sync libidn 1.32-3.1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/control:
    - build without gengetopt which is in universe
Now that we can build packages in main using packages from universe as long as 
they don't generate a runtime dependency, this is safe to sync.

Changelog entries since current yakkety version 1.32-3ubuntu1:

libidn (1.32-3.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Move the library from /usr/lib to /lib (Closes: #814778)

 -- Laurent Bigonville <bi...@debian.org>  Mon, 30 May 2016 11:50:09
+0200

** Affects: libidn (Ubuntu)
     Importance: Wishlist
         Status: New

** Changed in: libidn (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync libidn 1.32-3.1 (main) from Debian unstable (main)

Status in libidn package in Ubuntu:
  New

Bug description:
  Please sync libidn 1.32-3.1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * debian/control:
      - build without gengetopt which is in universe
  Now that we can build packages in main using packages from universe as long 
as they don't generate a runtime dependency, this is safe to sync.

  Changelog entries since current yakkety version 1.32-3ubuntu1:

  libidn (1.32-3.1) unstable; urgency=medium

    * Non-maintainer upload.
    * Move the library from /usr/lib to /lib (Closes: #814778)

   -- Laurent Bigonville <bi...@debian.org>  Mon, 30 May 2016 11:50:09
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1592224/+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