| 2021-03-13 00:15:30 |
Robie Basak |
description |
I'm updating the git-ubuntu classic snap to be based on core20. In doing this, I'm building a deb, and then installing it using stage-packages. See bug 1918968 for a deeper explanation of this use case.
Expected: "stage-packages: git-ubuntu" ships all required dependencies in the snap.
Actual: packages already in the core20 snap are elided from the effective "stage-packages" list. Since this classic snap cannot make use of what is in the core20 snap safely, the result is a snap with missing dependencies.
Workaround: explicitly specify every single required dependency, recursively, that is also present in the core20 snap.
The list of packages to use for the workaround is tedious to determine.
To fix, maybe the eliding behaviour should be disabled for a classic snap, or able to be turned off with an option. |
I'm updating the git-ubuntu classic snap to be based on core20. In doing this, I'm building a deb, and then installing it using stage-packages. See bug 1918968 for a deeper explanation of this use case.
Expected: "stage-packages: [git-ubuntu]" ships all required dependencies in the snap.
Actual: packages already in the core20 snap are elided from the effective "stage-packages" list. Since this classic snap cannot make use of what is in the core20 snap safely, the result is a snap with missing dependencies.
Workaround: explicitly specify every single required dependency, recursively, that is also present in the core20 snap.
The list of packages to use for the workaround is tedious to determine.
To fix, maybe the eliding behaviour should be disabled for a classic snap, or able to be turned off with an option. |
|
