-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fix snap build - TypeError: expected string or bytes-like object #253
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Hi OS: Ubuntu 18.04.6 LTS below is modified snapcraft.yaml file:
|
It may also be more transparent if we build snap packages using a Github Action instead of via the snap store. We could use https://github.com/snapcore/action-build for this. This would have the added benefit of creating a release when we tag and uploading a snap to that release which could be manually installed. |
Fixed in #264 |
Closing this was premature as further testing reveals that even though we can build referencing gstreamer archives instead of git checkout - video doesn't actually play. |
The above error is fixed by this PR: canonical/snapcraft#3628, which unfortunately did not quite make it into 6.1. I have tried a build with snapcraft from edge (which is version 7) and the build is successful. However with v7 I then can't login to snapcraft. I think the solution will be to wait for the next release of snapcraft, which contains the fix we need. It may be that this gets solved out by either of these two issues: |
A final update (I hope). The video issue seen when referencing the gstreamer archives in snap actually turned out to be a video issue under Wayland and a false lead. Further testing with the snap built using the gstreamer archives (rev 238 in edge) shows that it is functional, video plays and all seems well. With that I think this issue can be closed with a big thanks to @gamenfs for pointing us in the right direction. |
The snap build currently fails with the following error:
The text was updated successfully, but these errors were encountered: