test-update-portal timing out during installed-tests #4065
Comments
ids1024
pushed a commit
to pop-os/flatpak
that referenced
this issue
Jan 28, 2021
a-wai
pushed a commit
to a-wai/flatpak
that referenced
this issue
Mar 16, 2021
flatpak (1.10.1-2) unstable; urgency=medium
* d/patches: Disable FUSE-based revokefs if any of several factors fail.
This fixes FTBFS in pbuilder, and hopefully also on Launchpad
autobuilders.
flatpak (1.10.1-1) unstable; urgency=medium
* New upstream release
- Fix a regression in 'flatpak build' after fixing CVE-2021-21261
(Closes: #980323)
flatpak (1.10.0-2) unstable; urgency=medium
* Upload 1.10.x branch to unstable
* Add CVE-2021-21261 reference to 1.8.5-1 changelog entry
flatpak (1.10.0-1) experimental; urgency=medium
* d/control: Fix branch in Vcs-Git for experimental
* Merge packaging from unstable
* New upstream release, starting the 1.10.x branch
* Drop patches, applied upstream
* d/flatpak.install: Install new systemd environment generator
* d/tests: Mark update portal test as flaky due to
flatpak#4065
flatpak (1.8.5-1) unstable; urgency=high
* New upstream release fixing a sandbox escape vulnerability
(GHSA-4ppf-fxf6-vxg2, CVE-2021-21261)
* Mark patch for #975710 as having been applied upstream
flatpak (1.8.4-2) unstable; urgency=medium
* Mark patch for #972138 as having been applied upstream
* Add patch to avoid gvfs-daemon being started when logging in as root.
Thanks to Mourad De Clerck (Closes: #975710)
* Add package-specific info from bubblewrap to bug reports.
In particular, this will tell us whether it's setuid.
flatpak (1.9.3-2) experimental; urgency=medium
* Add patch to avoid gvfs-daemon being started when logging in as root.
Thanks to Mourad De Clerck (Closes: #975710)
* Add package-specific info from bubblewrap to bug reports.
In particular, this will tell us whether it's setuid.
flatpak (1.9.3-1) experimental; urgency=medium
* Merge packaging changes from unstable
* New upstream release
* d/p/variant-schema-compiler-Disable-optimized-calculation-of-.patch:
Drop patch, which should be unnecessary with the new version
* Mark remaining patch as forwarded
flatpak (1.8.4-1) unstable; urgency=medium
* debian/o.fd.Flatpak.pkla: sync with rules provided by upstream
* Use debian/unstable branch for packaging
* New upstream release
* d/p/variant-schema-compiler-Disable-optimized-calculation-of-.patch:
Drop patch, which should be unnecessary with the new version
flatpak (1.8.3-2) unstable; urgency=medium
* Preferentially build-depend on libgdk-pixbuf-2.0-dev.
We don't need the deprecated Xlib integration that is also pulled in
by the older libgdk-pixbuf2.0-dev package (see #974870).
* Standards-Version: 4.5.1 (no changes required)
flatpak (1.9.2-1) experimental; urgency=medium
* Branch for experimental
* New upstream development release
* Update ostree build-dependency
* Use upstream's autogen.sh now that it's shipped
* d/copyright: Update
* d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch:
Drop patch that was applied upstream
* d/p/Skip-a-test-case-if-etc-mtab-doesn-t-exist.patch:
Work around a test failure that can happen in sbuild
* Update symbols file.
Ignore removal of flatpak_http_error_quark (aka FLATPAK_HTTP_ERROR),
which is not in any public headers and is not referenced by any
other Debian package.
flatpak (1.8.3-1) unstable; urgency=medium
* New upstream release
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
flatpak (1.8.2-2) unstable; urgency=medium
[ Laurent Bigonville ]
* debian/control: Add libmalcontent-0-dev to the build-dependencies.
This provides optional parental controls for app installation and
launching.
[ Simon McVittie ]
* Add Suggests on malcontent-gui
flatpak (1.8.2-1) unstable; urgency=medium
* New upstream release
- Drop patch for #964541, applied upstream
flatpak (1.8.1-2) unstable; urgency=medium
* Include flatpak-bisect and flatpak-coredumpctl in libflatpak-dev
- Depends: python3, to be able to run the scripts themselves
- Recommends: flatpak, for both scripts
- Suggests: gdb and systemd-coredump, for flatpak-coredumpctl
- Suggests: python3-gi and ostree, for flatpak-bisect
* d/p/Fix-argument-order-of-clone-for-s390x-in-seccomp-filter.patch:
Add proposed patch to fix seccomp filtering on s390x.
Thanks to Julian Andres Klode. (Closes: #964541, LP: #1886814)
flatpak (1.8.1-1) unstable; urgency=medium
* New upstream stable release
flatpak (1.8.0-1) unstable; urgency=medium
* New upstream stable release
- Update configure options
- Install gdm env.d fragment, but only as an example file.
It is harmful on systems where environment.d(5) works (in particular
systems using systemd), because it overwrites additions to the
XDG_DATA_DIRS coming from other app frameworks like Snap.
However, using either this fragment or manual configuration might
be necessary on non-systemd systems. See
/usr/share/doc/flatpak/README.Debian for more details.
- d/flatpak.README.Debian: Add
flatpak (1.7.3-1) experimental; urgency=medium
* New upstream development release
* Install new fish completions
* Enable new libzstd support
* Install new sysusers.d fragment
* d/libflatpak0.symbols: Update.
Ignore deletion of flatpak_oci_error_quark(), which was not public API.
flatpak (1.7.1-1) experimental; urgency=medium
* New upstream development release
- Sideloading apps now works differently.
Flatpak no longer supports installing from local network peers, and
sideloading from a local USB drive is no longer automatic.
Instead of being configured via `flatpak config sideload-repos`,
enabling sideloading is now done by creating a symbolic link in
/var/lib/flatpak/sideload-repos or /run/flatpak/sideload-repos.
flatpak (1.6.3-1) unstable; urgency=medium
* New upstream stable release
flatpak (1.7.0~git20200330-1) experimental; urgency=medium
* New upstream snapshot
- d/copyright: Update
- Drop all patches, applied upstream
* Revert "d/control: Add spurious Build-Conflicts on elogind packages".
experimental buildds now use aptitude rather than aspcud, so this
particular workaround shouldn't be necessary, even in experimental.
* Explicitly build-depend on python3-pyparsing.
This is required to generate the variant schema compiler.
* d/p/variant-schema-compiler-Disable-optimized-calculation-of-.patch:
Disable optimized calculation of offset size.
This doesn't seem to be completely portable, and it isn't clear why not,
so disable it until we have more answers.
flatpak (1.7.0~git20200325-1) experimental; urgency=medium
* Branch for 1.7.x and Debian experimental
- d/control, d/gbp.conf: Use debian/experimental packaging branch
- d/gbp.conf: Use upstream/latest branch
- d/watch: Watch for development releases
* New upstream snapshot
* Build-depend on python3 even when not running tests, for
variant-schema-compiler
* Update symbols file
* d/patches: Add patches proposed upstream to formalize deprecations
and fix rebuild of generated files
* d/control: Add spurious Build-Conflicts on elogind packages.
As in 1.5.0-1, this works around a build-dependency resolver failure
when using the same aspcud resolution behaviour as official Debian
experimental buildds, and can safely be reverted in distributions
that only have elogind, such as Devuan.
flatpak (1.6.2-1) unstable; urgency=medium
* New upstream stable release
flatpak (1.6.1-1) unstable; urgency=medium
* New upstream stable release
* Use secure URI in Homepage field.
* Set upstream metadata fields: Repository.
* Remove obsolete field Name from debian/upstream/metadata (already
present in machine-readable debian/copyright).
* Standards-Version: 4.5.0 (no changes required)
flatpak (1.6.0-1) unstable; urgency=medium
* New upstream stable release
- d/p/testlibrary-Don-t-assert-that-progress-is-signalled.patch:
Drop workaround, the leaks that broke this test have been fixed
- Drop other patches, applied upstream
- Bump xdg-desktop-portal dependency to 1.6.x.
That version has new API which Flatpak apps might rely on, so the
corresponding versions should be tested and backported together.
* d/watch: Only watch for stable releases
* Set upstream branch to upstream/1.6.x
* Drop xdg-desktop-portal from Depends to Recommends.
Installing xdg-desktop-portal 1.6.x is strongly recommended, but
strictly speaking it is not required: some of the simpler Flatpak
apps can work without it. (Closes: #947022)
* tests: Depend on fuse and policykit-1
* Revert Build-Conflicts on elogind to be nice to non-systemd derivatives.
This was a workaround for the build-dependency resolver used in
experimental, and is unnecessary now that I'm targeting unstable.
flatpak (1.5.2-1) experimental; urgency=medium
* New upstream development release
- d/copyright: Update
- d/control: Depend on bubblewrap 0.4.0
- Update d/libflatpak0.symbols
* d/tests/build: Use correct compiler for proposed autopkgtest
cross-architecture testing support
* Make autopkgtests shellcheck-clean
* d/p/debian/Use-Python-3-for-test-web-server.patch:
Drop patch, no longer needed.
The tests now require Python 3 upstream, and no longer support
Python 2.
* Depend on xdg-desktop-portal 1.5.4.
This is probably not strictly required, but they are likely to be
released together and some features will need it.
* d/tests/build: Use correct compiler for proposed autopkgtest
cross-architecture testing support
* Make autopkgtests shellcheck-clean
* d/patches:
Add proposed patches from upstream PR 3307 to fix memory and fd leaks
* d/patches:
Add proposed patches from upstream PR 3310, 3311, 3312 to fix some
minor memory leaks
* d/p/testlibrary-Don-t-assert-that-progress-is-signalled.patch:
Remove problematic assertions while the failure is investigated
flatpak (1.5.0-1) experimental; urgency=medium
* New upstream development release
- Update d/libflatpak0.symbols
* Standards-Version: 4.4.1 (no changes required)
* Set packaging branch to debian/experimental
* tests: Depend on socat
* d/control: Add spurious Build-Conflicts on elogind packages.
This works around a build-dependency resolver failure when using
the same aspcud resolution behaviour as official Debian experimental
buildds, which for some reason tries to co-install systemd and elogind,
causing failure to install build-dependencies.
(This can safely be reverted in distributions that only have elogind,
such as Devuan.)
flatpak (1.4.3-1) unstable; urgency=medium
* New upstream stable release
- d/p/Don-t-register-polkit-agent-if-we-cannot-connect-to-syste.patch,
d/p/tests-Skip-tests-that-use-system-helper-if-uid-or-gid-is-.patch:
drop patches, applied upstream
* Remove redundant --libexecdir, no longer needed with compat level 12
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Linux distribution and version
Debian unstable (rolling release)
Flatpak version
1.9.3, also tried master as of commit 8a00d43
Description of the problem
When running installed-tests (in a qemu virtual machine via Debian's autopkgtest framework), I'm frequently getting
test-update-portal@system.wrap.testand/ortest-update-portal@user.wrap.testfailing with:I haven't noticed this with 1.8.x, so it might be a regression?
Steps to reproduce
https://salsa.debian.org/debian/flatpak/-/blob/debian/experimental/debian/tests/gnome-desktop-testing
The text was updated successfully, but these errors were encountered: