Sync flatpak 1.8.2-3 (universe) from Debian sid (main)

[Andrew Hayzen]

Please sync flatpak 1.8.2-3 (universe) from Debian sid (main)

Changelog entries since current groovy version 1.8.2-2:

flatpak (1.8.2-3) unstable; urgency=medium

  * d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch:
    Add proposed patch to skip parental controls if accountsservice is not
    installed.
    The malcontent package (which activates parental controls support)
    depends on accountsservice, but the libmalcontent-0-0 client library
    does not, so we need to cope gracefully with the case where
    neither malcontent nor accountsservice is installed. Presumably, in such
    installations the sysadmin did not want the parental controls feature.
    Ideally libmalcontent would do this itself (#972145). (Closes: #972138)
  * Add Depends on dbus, for the well-known system bus service.
    Now that the parental controls feature is enabled, Flatpak will refuse
    to run apps if the D-Bus system bus is unavailable. Previously, it would
    have partially worked (but with severely reduced functionality, in
    particular only --user installations).
  * d/control: Canonicalize case of Multi-Arch
  * Update lintian overrides to silence some false-positives

 -- Simon McVittie <email address hidden> Thu, 15 Oct 2020 09:47:28 +0100

[Thomas Ward (teward)]

Hello.

According to the tool to indicate whether a package is seeded or not, Flatpak is currently seeded in Ubuntu Budgie and Xubuntu:

$ seeded-in-ubuntu flatpak
flatpak (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
gir1.2-flatpak-1.0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak-dev (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported

Ubuntu is now in Final Freeze - per the Final Freeze announcement [1], packages need to fit one of these two categories:

1) Release critical bugs that affect ISOs, installers, or otherwise
   can't be fixed easily post-release.

2) Bug fixes that would be suitable for post-release SRUs, which we may
   choose to accept, reject, or shunt to -updates for 0-day SRUs on a
   case-by-case basis. This second case should have SRU-style bugs filed
   with the appropriate template, referenced in changelog.

I don't see a justification included on the sync request that would put this request into either of the categories as this does not have any SRU template.

The only new changes I can see here are that it has a dependency on DBus, but that you fix an issue with Parental Control checks. That's likely SRUable post-release.

However, I don't see justification to sync this at this time given we are in Final Freeze.

[Andrew Hayzen (ahayzen)]

Oh sorry, I didn't realise that flatpak was being seeded in some flavours :-)

The main reason for this sync was to try and fix the issues with 1.8.2-2 which is currently in groovy-proposed, I didn't want this version to accidentally reach a release pocket. As if the user doesn't have the accountsservice installed it will cause flatpak not to work correctly (which might even be the case for some of these seeded flavours). 1.8.2-3 provides fixes for this.

If 1.8.2-2 is rejected from proposed, then we might not even need to sync 1.8.2-3 for groovy if the parental controls stuff stays correctly disabled with 1.8.2-1. And if it does cause issues or we want to enable it, then I'm happy to do a SRU after release.

The autopkgtests are failing for the package in proposed, so hopefully it will be rejected.