You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: witch_spells Folder Not Copied to Host System in Snapcraft
Description:
During the Snapcraft build process, the folder witch_spells is correctly mounted within the .snap package and appears at the location /var/witch_craft/witch_spells when the package is unpacked using unsquashfs. However, the contents of witch_spells are not being copied to the expected destination on the host system upon installation, which prevents their access by the application.
Steps to Reproduce:
Build the .snap package with Snapcraft, ensuring the witch_spells folder is included.
Verify the contents of the .snap file using unsquashfs and confirm that witch_spells is present at /var/witch_craft/witch_spells.
Install the snap on the host system and attempt to access /var/witch_craft/witch_spells from the host environment.
Notice that witch_spells is missing on the host, even though it appears in the .snap package.
Expected Behavior:
The witch_spells folder should be copied to /var/witch_craft/witch_spells on the host system during installation, making its contents accessible to the application.
Observed Behavior:
The witch_spells folder remains within the .snap package but is not copied to the final location on the host.
Potential Causes:
Snapcraft Configuration: The Snapcraft YAML configuration might lack proper directives to ensure the witch_spells folder is copied to the final location.
Confinement Issues: If the snap uses strict confinement, it may not have the necessary permissions to copy files to /var.
Snap Layouts or Bind Mounts: Snap layouts or bind mounts might be misconfigured, preventing witch_spells from being linked to the host system.
Suggested Solution:
Verify Snapcraft YAML Configuration: Ensure the witch_spells directory is properly defined in the Snapcraft YAML under the layout section to bind it to /var/witch_craft/witch_spells.
Check Confinement Settings: If using strict confinement, verify that the snap has the necessary permissions or consider using classic confinement if feasible.
Add Post-Install Hook (if applicable): If Snapcraft configuration alone does not resolve the issue, consider adding a post-install hook to manually copy witch_spells to the desired location on the host.
The text was updated successfully, but these errors were encountered:
Issue:
witch_spells
Folder Not Copied to Host System in SnapcraftDescription:
During the Snapcraft build process, the folder
witch_spells
is correctly mounted within the.snap
package and appears at the location/var/witch_craft/witch_spells
when the package is unpacked usingunsquashfs
. However, the contents ofwitch_spells
are not being copied to the expected destination on the host system upon installation, which prevents their access by the application.Steps to Reproduce:
.snap
package with Snapcraft, ensuring thewitch_spells
folder is included..snap
file usingunsquashfs
and confirm thatwitch_spells
is present at/var/witch_craft/witch_spells
./var/witch_craft/witch_spells
from the host environment.witch_spells
is missing on the host, even though it appears in the.snap
package.Expected Behavior:
The
witch_spells
folder should be copied to/var/witch_craft/witch_spells
on the host system during installation, making its contents accessible to the application.Observed Behavior:
The
witch_spells
folder remains within the.snap
package but is not copied to the final location on the host.Potential Causes:
witch_spells
folder is copied to the final location./var
.witch_spells
from being linked to the host system.Suggested Solution:
Verify Snapcraft YAML Configuration: Ensure the
witch_spells
directory is properly defined in the Snapcraft YAML under thelayout
section to bind it to/var/witch_craft/witch_spells
.Check Confinement Settings: If using strict confinement, verify that the snap has the necessary permissions or consider using classic confinement if feasible.
Add Post-Install Hook (if applicable): If Snapcraft configuration alone does not resolve the issue, consider adding a
post-install
hook to manually copywitch_spells
to the desired location on the host.The text was updated successfully, but these errors were encountered: