Accepted flatpak 1.4.2-2 (source) into unstable

Simon McVittie Tue, 09 Jul 2019 14:49:36 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jul 2019 17:59:57 +0100
Source: flatpak
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: high
Maintainer: Utopia Maintenance Team 
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Changes:
 flatpak (1.4.2-2) unstable; urgency=medium
 .
   * Upload to unstable
   * d/gbp.conf: Return to debian/master branch
   * Use debhelper-compat 12
   * Standards-Version: 4.4.0 (no changes required)
 .
 flatpak (1.4.2-1) experimental; urgency=medium
 .
   * New upstream release
   * d/p/Don-t-register-polkit-agent-if-we-cannot-connect-to-syste.patch:
     Add proposed patch to avoid crashing if the system bus is unavailable,
     working around policykit-1 bug #923046
   * d/salsa-ci.yml: Request standard CI on salsa.debian.org
   * d/p/tests-Skip-tests-that-use-system-helper-if-uid-or-gid-is-.patch:
     Avoid testing the system helper if uid or gid is zero.
     The system helper refuses to run in test mode if it has privileges,
     but some CI systems (currently including salsa-ci) run as uid or
     gid 0 in a disposable container.
   * d/test.sh: Don't run tests under linux32, even if reprotest did the
     build under linux32
   * d/test.sh: Don't output non-test logs (notably
     debian/output/reprotest.log on salsa-ci) after running tests
 .
 flatpak (1.4.1-1) experimental; urgency=high
 .
   * New upstream stable release
     - This reverts an unintended ABI break in 1.4.0.
 .
 flatpak (1.4.0-1) experimental; urgency=medium
 .
   * New upstream stable release
 .
 flatpak (1.3.4-1) experimental; urgency=medium
 .
   * New upstream development release
     - Incompatible change: /etc/flatpak/remotes.d/*.conf are no longer
       read, and are superseded by /etc/flatpak/remotes.d/*.flatpakrepo
   * Require libostree 2019.2, for OSTREE_REPO_PULL_FLAGS_MIRROR
   * Install flatpak-docker-seccomp.json to /u/s/d/flatpak/examples.
     This seccomp profile can be used to configure a Docker container to
     allow bubblewrap and Flatpak to be run, with some caveats:
     - The host kernel must allow unprivileged user namespace creation
       (for example Debian with sysctl kernel.unprivileged_userns_clone=1,
       or recent Ubuntu in its default configuration)
     - Use the seccomp profile
       (docker run --security-opt seccomp=flatpak-docker-seccomp.json)
     - Make the host system /proc visible in the container
       (docker run -v=/proc:/host/proc)
     - Run flatpak as an ordinary user in the container, not as root
   * d/copyright: Update
   * d/libflatpak0.symbols: Update
 .
 flatpak (1.3.3-1) experimental; urgency=medium
 .
   * New upstream development release
     - Drop patches that were applied upstream
     - d/libflatpak0.symbols: Update
 .
 flatpak (1.3.2-1) experimental; urgency=medium
 .
   * New upstream development release
   * d/watch: Watch for development (odd-numbered) versions
   * d/gbp.conf: Branch to upstream/latest and debian/experimental
   * Depend on adduser and create _flatpak user in postinst.
     This is now required by the helper that installs apps and runtimes
     system-wide.
   * Disable SELinux module for now.
     Advice from SELinux users/maintainers on whether/how this can fit
     into Debian systems with the non-default SELinux LSM would be welcomed.
   * Build-depend on libfuse-dev and install new revokefs-fuse helper
   * d/libflatpak0.symbols: Update
   * d/copyright: Update
   * Build-depend on policykit-1 for tests
   * Build-depend on fuse for tests
   * d/p/Use-system-copy-of-xdg-dbus-proxy-for-build-time-tests-if.patch:
     Use the correct system xdg-dbus-proxy for build-time tests
   * d/p/Skip-some-tests-if-we-can-t-use-FUSE.patch:
     Skip tests that rely on FUSE when built on a buildd, in a schroot
     or in a Docker container. FUSE doesn't work in any of these places.
Checksums-Sha1:
 333e8a335cd0c35f0ae286a963b8e7b6178323d0 3395 flatpak_1.4.2-2.dsc
 a603a55ab7ee0b0102fab2498915d404dde11472 28012 flatpak_1.4.2-2.debian.tar.xz
 ba57bcba01e501d2fac82c4135c507aef4a8e363 12357 flatpak_1.4.2-2_source.buildinfo
Checksums-Sha256:
 89801eeefbc8336d4311a89a90805112e495a1d9389f4a0c45863016cd985a15 3395 
flatpak_1.4.2-2.dsc
 972164485181b0051399ae3e088050f9a474ded28ca4bd97069a5c1dc6349d6e 28012 
flatpak_1.4.2-2.debian.tar.xz
 bed429cfc7482995b3718f9b77140e87d52232bd92a05e17577833fcf16033b9 12357 
flatpak_1.4.2-2_source.buildinfo
Files:
 3200383cdb4190a0dbd1ecb0efa41b1a 3395 admin optional flatpak_1.4.2-2.dsc
 e47427edcf356c91d93c69c5291c3ba7 28012 admin optional 
flatpak_1.4.2-2.debian.tar.xz
 70a6de6f06bd2a86f520a72ef9a11856 12357 admin optional 
flatpak_1.4.2-2_source.buildinfo
Accepted flatpak 1.4.2-2 (source) into unstable

Reply via email to
