Change logs for packagekit source package in Yakkety

  • packagekit (1.1.1-1ubuntu1) yakkety; urgency=medium
    
      * Merge with Debian; remaining changes:
        + Client tools alternatively depend on or recommend aptdaemon's
          compatibility layer
        + packagekit provides the virtual packagekit-system-interface
        + Add break on packagekit-plugin-click <= 0.3
    
    packagekit (1.1.1-1) unstable; urgency=medium
    
      * New upstream release: 1.1.1
      * Drop the manual -dbg package in favor of the auto-generated
        dbgsym packages
      * Drop progress-callback-notified.patch: Applied upstream
      * aptcc-full-package-origin.patch: Make aptcc backend return a
        complete origin ID
      * Use secure Vcs-* URLs
      * Bump standards version: No change needed
      * debian/rules: Remove some dead logic
    
    packagekit (1.1.0-2) unstable; urgency=medium
    
      * progress-callback-notified.patch: Fix GIR annotations for
        PkProgressCallback callbacks in async functions.
        This prevents crashes when using PackageKit from languages
        like Python.
    
    packagekit (1.1.0-1) unstable; urgency=medium
    
      * New upstream release: 1.1.0
      * Drop the browser plugin
        - Removed upstream, "appstream://" URLs are much more useful today.
          Also, browser plugins will go away in the near future anyway.
        - Remove browser plugin information from debian/copyright
      * Drop pkid-state-in-data.patch: Applied upstream
      * Update symbols file
    
    packagekit (1.0.11-2) unstable; urgency=medium
    
      * pkid-state-in-data.patch: Always set data part of a package-id to
        "installed" if the package is installed, and do not include repo
        information in that case.
        The previous behavior broke GNOME Software removals (Closes: #804094)
    
    packagekit (1.0.11-1) unstable; urgency=medium
    
      * New upstream release: 1.0.11
        - Reworked downloading of changelogs (Closes: #794697)
        - Works with APT 1.1 now (Closes: #798709)
      * Update .symbols file
    
    packagekit (1.0.10-1) unstable; urgency=medium
    
      * New upstream release: 1.0.10
      * Drop patches: Applied upstream
    
    packagekit (1.0.8-1) unstable; urgency=medium
    
      * New upstream release: 1.0.8
        - Closes: #797138
      * Refresh patches, drop libsystemd-only patch (applied upstream)
      * Add Vala VAPI file and missing metadata
      * critical-warnings.patch: Fix critical compile warnings
      * dont-assume-time_t-is-long.patch: Fix build on x32 (Closes: #777509)
        - Thanks to Adam Borowski for the patch!
      * Do not recommend gnome-packagekit-session anymore
        - The interface is now part of GNOME-Software, so we need to
          recommend that instead.
    
    packagekit (1.0.6-1) unstable; urgency=medium
    
      * New upstream release: 1.0.6
      * Update symbols file
      * Build-depend on libsystemd only, instead of the deprecated
        libsystemd-* libs (Closes: #779757)
      * Use HTTPS for Debian Wiki links (Closes: #784794)
        - Thanks to Raphael Geissert for the patch!
      * Use the fd.o URL of PackageKit, instead of packagekit.org
        as homepage, since the latter is now only a redirect to the former
        location
    
    packagekit (1.0.1-2) unstable; urgency=medium
    
      * Ship with pkla file for older PolicyKit versions (Closes: #766792)
      * Place temporary data in subdirectory in /tmp (Closes: #764928)
      * Don't try to ask any questions if we are running in
        non-interactive mode (Closes: #764926)
      * Drop obsolete configuration (Closes: #768420)
      * Recommend PackageKit session-interface providers for packages
        which need a session-interface (Closes: #770814)
    
    packagekit (1.0.1-1) unstable; urgency=medium
    
      * New upstream release: 1.0.1
      * Drop patches: Applied upstream
      * Build package using dh-systemd to cleanup stuff on package removal
      * Drop Python3 backend bindings
      * Remove dist-upgrade notification support from aptcc
        - This only really worked on Ubuntu, and the functionality relies
          on outdated Python code and needs to be reimplemented in a
          sane way. There is no need to ship cruft with Jessie.
    
    packagekit (1.0.0-3) unstable; urgency=medium
    
      * Don't explicitly pass systemd unit path to configure
        - Should resolve FTBFS on non-Linux ports
    
    packagekit (1.0.0-2) unstable; urgency=medium
    
      * Add patch to fix systemd-dependent conditional compilation
        - Will hopefully resolve the FTBFS on !linux
    
    packagekit (1.0.0-1) unstable; urgency=medium
    
      * New upstream release: 1.0.0
        - This release drops support for plugins
        - Aptcc is now the only viable backend for Debian, other
          backends have been removed upstream.
      * Drop patches: Applied upstream
      * Update symbols file
      * Update copyright
      * Bring back the PackageKit command-not-found support in a
        separate package.
    
    packagekit (0.9.5-2) unstable; urgency=medium
    
      * Include missing header for plugin builds
    
    packagekit (0.9.5-1) unstable; urgency=medium
    
      * Upload to unstable
      * New upstream release: 0.9.5
      * Drop all previous patches: Applied upstream
      * Drop defaults.diff: Debian's defaults are now upstream
      * Take patch from upstream to increase hardcoded transation limits
      * Update symbols file
    
    packagekit (0.9.4-1) experimental; urgency=medium
    
      * New upstream release: 0.9.4
      * Drop build-dep on browsers, use npapi-sdk instead (Closes: #754373)
      * Drop patches which have been applied upstream
      * npapi-sdk.patch: Compile using npapi-sdk
    
     -- Matthias Klose <email address hidden>  Thu, 19 May 2016 18:55:02 +0200
  • packagekit (0.8.17-4ubuntu6~gcc5.4ubuntu2) yakkety; urgency=medium
    
      * Fix segfault on AptIntf::init() (LP: #1569292)
        aptcc: Don't ask about config changes if we are not interactive
        aptcc: Always respect the noninteractive flag
        aptcc: Fix several compiler warnings
        aptcc: Ensure proxy and frontend-socket aren't used if they are NULL
    
     -- Seyeong Kim <email address hidden>  Fri, 29 Apr 2016 12:12:01 +0200
  • packagekit (0.8.17-4ubuntu6~gcc5.4ubuntu1) xenial; urgency=high
    
      * Cherrypick
        https://github.com/hughsie/PackageKit/commit/30bfee4d41944bbfbd7a40c7f3fa1004fc6effa9
        to fix FTBFS with apt 1.1.
    
     -- Dimitri John Ledkov <email address hidden>  Wed, 09 Dec 2015 18:02:41 +0000