Public bug reported:

Please sync json-glib 0.16.0-1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * New upstream version, updated glib requirement
  * debian/control.in:
    - updated glib requirement
  * debian/control:
    - Use standards version 3.9.3
    - Bump build-depends on libglib2.0-dev
  * debian/libjson-glib-1.0-0.symbols:
    - Updated (non public symbols removed)
  * debian/libjson-glib-1.0-0.symbols:
    - Updated (non public symbols removed)

(all those changes have been done in the Debian version too)

Changelog entries since current saucy version 0.16.0-0ubuntu1:

json-glib (0.16.0-1) unstable; urgency=low

  [ Michael Biebl ]
  * Change section of gir1.2-json-1.0 to introspection.

  [ Josselin Mouette ]
  * Update repository URL.

  [ Laurent Bigonville ]
  * New upstream release
    - Bump libglib2.0-dev build-dependency to 2.34.0
    - debian/libjson-glib-1.0-0.symbols: Adjust .symbols file, the dropped
      symbols were not part of the public API
  * debian/control.in:
    - Bump Standards-Version to 3.9.4 (no further changes)
    - Use canonical URL's for VCS fields
  * debian/rules: Use DEB_LDFLAGS_MAINT_APPEND instead of LDFLAGS and include
    buildflags.mk to avoid overriding hardening flags
  * Add libjson-glib-1.0-common package: Upstream is now shipping translations

 -- Laurent Bigonville <[email protected]>  Tue, 18 Jun 2013 18:43:18
+0200

** Affects: json-glib (Ubuntu)
     Importance: Wishlist
         Status: New

** Changed in: json-glib (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195056

Title:
  Sync json-glib 0.16.0-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1195056/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to