-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snapcraft 8.2.1: snapcraft pack
not respecting <directory>
arg to find snapcraft.yaml
#4769
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-2861.
|
Thanks for the report. I can confirm this is a regression. We had a similar report in the Snapcraft channel on Matrix here. I'll take a look and see what we can do to fix this. |
got an issue about this on goreleaser too |
also worth noting that before this version the Before, we created an structure like this:
and it was enough for it to work. is this behavior being removed? if so, this should probably have been a major release 🤔 |
No, sorry about this. This was an unintentional regression and we're working on a fix. As a temporary workaround, you can revert to the previous release with the revisions listed here: https://forum.snapcraft.io/t/call-for-testing-snapcraft-8-2-1/39928/2 |
Thank you for the speedy response @mr-cal -- much appreciated! |
This should be fixed in snapcraft 8.2.6, which has been released to If anyone here can test and confirm, I would appreciate it. Thanks! |
Retested with 8.2.6, LGTM. Thanks for the fix! |
goreleaser tests are passing with 8.2.6! thanks! |
chezmoi passing too, thanks! |
It's actually a little bit more complicated than that. Launchpad plus:
The obvious solution is to rename But this could also be a regression. |
Bug Description
When using snapcraft 8.2.1, I find that repacking an existing snap by using the directory arg has regressed. Reverting snapcraft (to 8.0.5 in my case) allows this to work again.
To Reproduce
workaround:
Environment
Ubuntu 24.04
snapcraft.yaml
# n/a
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: