Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
many: add internal squashfuse copy as "snapfuse" #4030
Conversation
mvo5
added some commits
Oct 12, 2017
All checks have failed
mvo5
added this to the 2.29 milestone
Oct 12, 2017
All checks have failed
| @@ -0,0 +1,31 @@ | ||
| +The squashfuse distribution as a whole is copyright Dave |
|
@mvo5 can we not add the files that are generated? If you want I can give you a hand. |
Conan-Kudo
suggested changes
Oct 13, 2017
This seems very broken. I don't think I've ever heard of apt not being able to upgrade packages that add new dependencies on the upgrade command.
I'm also reluctant to say that doing this is okay at all...
|
Closing for now as we are looking for a cleaner approach. |
mvo5
closed this
Oct 16, 2017
mvo5
referenced this pull request
Oct 16, 2017
Open
debian,vendor: import github.com/snapcore/squashfs and use #4049
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mvo5 commentedOct 12, 2017
This PR adds a new "snapfuse" binary to the xenial (and higher) deb package. The binary is used inside lxd containers if no squashfuse is installed. This ensures that lxd containers always work without the need to install extra software in there. We (unfortunately) cannot add a simple dependency because that would break users who run
apt-get upgradeon a 16.04 install with snapd 2.0.2 or 2.0.10. No new dependencies are allowed in apt-get upgrade. However users who useapt upgradeorapt{,-get} {dist,full}-upgradeare fine.See LP: #1628389 for the details.