Flatpak system repo keeps getting re-enabled

[ajgringo619]

I have moved my Flatpak installation to my /home partition, using the user repo instead of the system repo. However, during some of the system updates, the system repo is re-enabled, which causes any new Flatpaks to be installed under /. Is there any way to permanently disable this "feature"?

[xenopeek]

This needs further troubleshooting to find out what is doing this. I suggest taking help for that from the support forums if you haven't already found a solution or workaround. If the root cause is found to be in a component maintained by Linux Mint this issue can be reopened.

[mtwebster]

Mintinstall and the package system we use (in mint-common) are more or less hardcoded to use the system installation at the moment, to mimic behavior of the default package manager. It's probably getting re-enabled when the package cache is updated.

I'll take a look at making this a bit more flexible. The specific things that probably re-enables it is the mintinstall-update-pkgcache program, which is run periodically by mintupdate. As a workaround, if you were to not use mintinstall, you could edit this script to do nothing. Unfortunately there's not really much else to do for the moment.

[gm10]

@mtwebster nah, it's only

mintinstall/debian/postinst

Line 38 in 9663877

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Happy new year. ;)

[JoeJoeTV]

It would be nice, if the possibility to change the location that mintinstall uses would be added, as flapaks are filling up my relatively small root partition, while I have lots of space on the home partition or on other drives.

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[github-actions]

This issue has been automatically closed due to inactivity.

If you can still reproduce this issue on a current version,
please feel free to reopen it with updated information.