Your message dated Fri, 23 Aug 2019 09:02:10 +0100 with message-id <[email protected]> and subject line Re: Bug#830271: flatpak: Don't initialize system repo in postinst has caused the Debian Bug report #830271, regarding flatpak: Don't initialize system repo in postinst to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 830271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830271 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: flatpak Version: 0.6.7-1 Severity: normal Currently flatpak.postinst runs `flatpak remote-list --system` in order to initialize the system repo. I don't see any reason why this is needed, though. The user may only want to install user applications. Furthermore, install a system application is privileged and the system repository will be setup whenever that happens by flatpak in the exact same way that the postinst script is doing it. My real problem is that we want to have /var/lib/flatpak/repo be a symlink to /ostree/repo so we can share the objects for the runtimes with the OS. Having flatpak forcefully create the system repo in postinst makes it more difficult for us to manage this setup. The postrm script will still work correctly whether the postinst script creates the repo or not. Thanks! -- Dan Nicholson | +1.206.437.0833 | Endless
--- End Message ---
--- Begin Message ---On Tue, 14 Feb 2017 at 10:02:30 -0600, Dan Nicholson wrote: > Anyway, it's not a big deal. You can close this. Doing so now. smcv
--- End Message ---
