[Bug 1955475] [NEW] Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)

Launchpad Bug Tracker 1955475 at bugs.launchpad.net
Tue Dec 21 09:48:47 UTC 2021


You have been subscribed to a public bug by fossfreedom (fossfreedom):

Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Correctly restore +x permissions on the .install for dh_exec

I've done a test build of the debian package and installed the resulting .deb installs just fine.
Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu

In addition the v0.9.0 of the package ensures alignment with the v0.9.0 series of the
other ayatana packages that have already migrated to ubuntu.

Changelog entries since current jammy version 0.8.4-4ubuntu2:

libayatana-indicator (0.9.0-1) unstable; urgency=medium

  * New upstream release.
  * debian/patches:
    + Drop all previous patches. All shipped upstream.
    + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't
      export private symbols.
  * debian/:
    + Adjust to upstream build system switch (autotools -> CMake).
  * debian/control:
    + Bump Standards-Version: to 4.6.0. No changes needed.
    + Add missing dev:pkg dependency to libayatana-indicator3-dev:
      libayatana-ido3-dev (>= 0.8.0).
    + Enforce usage of version 0.9.0 of the Ayatana IDO library.
  * debian/copyright:
    + Update auto-generated copyright.in reference file.
    + Update copyright attributions.
  * debian/watch:
    + Use format version 4.
  * debian/rules:
    + Install NEWS file as upstream ChangeLog.
  * debian/upstream/metadata:
    + Update points of contact, put UBports Foundation in Donation: field.

 -- Mike Gabriel <sunweaver at debian.org>  Thu, 18 Nov 2021 13:35:28 +0100

** Affects: libayatana-indicator (Ubuntu)
     Importance: Wishlist
         Status: New

-- 
Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1955475
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list