Dan Nicholson

Results 213 comments of Dan Nicholson

I did a little auditing of usage of `flatpak_transaction_set_no_deploy` and it's shorter GI version `set_no_deploy` (fortunately almost no one has a similar API). https://github.com/search?q=flatpak_transaction_set_no_deploy&type=Code flatpak gnome-software https://codesearch.debian.net/search?q=flatpak_transaction_set_no_deploy&literal=1 flatpak gnome-software https://github.com/search?q=set_no_deploy&type=code...

`--no-deploy` was trickier to search for. GitHub's search doesn't let you search for that on it's own, so I searched for [`flatpak no-deploy`](https://github.com/search?q=flatpak+no-deploy&type=code). Those were all from within flatpak either...

Don't know how I missed eos-updater. I think you're correct that this wouldn't affect it.

I haven't tested this at all and would appreciate some guidance and suggested tests. This came out of a discussion on the flatpak matrix channel. See [the ostree documentation](https://ostreedev.github.io/ostree/reference/ostree-Core-repository-independent-functions.html#OSTREE-MAX-METADATA-SIZE:CAPS) for...

After several years I finally ported our code to use transactions. It occurred to me that adding a `localcache_repos` property to `FlatpakTransaction` wouldn't be too invasive. That's far from a...

I ran into the last one and it comes from a lack of consistent request mocking. That was exacerbated by 8e64e45b8769a6c7fb172a30f55192e3be2a7a37 since it now does a `HEAD` request before any...

@jlebon Thank you! I could not figure out the right private/bind magic to make that happen. Let me try that out.

Yeah, I noticed that later searching around about pivot_root. I had a try hacking in the root mount, but it didn't quite work out.

In case anyone ever feels like picking this up, https://gist.github.com/dbnicholson/da8aa72ea3bd7ee8731c9da2792fd5a3 is what I played with before but didn't get working.

I don't see any reason why case 1 (bubblewrap started by a privileged user inside a chroot) couldn't work. It's why I opened the issue and started working on fixes...