Add flatpak update notification and auto proxy config #604
Conversation
alimirjamali
force-pushed
the
flatpak-update-support
branch
from
b78279d to
5cb8b88
Compare
alimirjamali
force-pushed
the
flatpak-update-support
branch
from
5cb8b88 to
0e8a2e6
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #604 +/- ##
=======================================
Coverage 71.10% 71.10%
=======================================
Files 3 3
Lines 481 481
=======================================
Hits 342 342
Misses 139 139 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Automatic proxy config for flatpak in TemplateVMs. Notify dom0 if system-wide (in TemplateVM) flatpaks are outdated. A separate patch to `qubes-core-admin-linux` & `vmupdate` will enable easy update of (in Template) flatpaks via the updater. related: QubesOS/qubes-issues#2766
alimirjamali
force-pushed
the
flatpak-update-support
branch
from
0e8a2e6 to
659e8e6
Compare
|
There is one rough edge to document - proxy won't work just after installing flatpak package - you need to restart the template for that. |
Another option would be writing individual post-install hooks per package manager? (dnf, apt, pacman, ...)? But it would a little bit painful. And where to document? |
Just looked at the Flatpak documentation again. For Archlinux, Debian, Ubuntu, ...; they already advise user to restart the system anyways: So only a hook is needed for Qubes Fedora templates (which do not have it installed by default). |
https://doc.qubes-os.org/en/latest/user/how-to-guides/how-to-install-software.html seems like a good place to add section about Flatpak. I don't think there need to be any automatic restart or anything like that, keep it simple. |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025110513-4.3&flavor=pull-requests Test run included the following:
Upload failures
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025081011-4.3&flavor=update
Failed tests24 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/149225#dependencies 81 fixed
Unstable testsPerformance TestsPerformance degradation:18 performance degradations
Remaining performance tests:157 tests
|
|
This is weird, clearly some network access uses proxy, because adding remote worked, search also works. But But |
|
I haven't checked, but I'm afraid the remote-ls failure will also break updates check... |
This does not happen on my system (or at least on Fedora 43. I will try it on Fedora 42 and will report back 
|
Ok. It works on Fedora 43 and is broken on Fedora 42. I have to investigate |
|
Ok. It believe the issue be similar to this: And when did sudo enable secure path by default? And I wonder why we did not find about this earlier? https://www.sudo.ws/posts/2024/09/why-sudo-1.9.16-enables-secure_path-by-default/ |
3 participants
Automatic proxy config for flatpak in TemplateVMs. Notify dom0 if system-wide (in TemplateVM) flatpaks are outdated.
A separate patch to
qubes-core-admin-linux&vmupdatewill enable easy update of (in Template) flatpaks via the updater.related: QubesOS/qubes-issues#2766