Skip to content
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

regression: remote-build doesn't accept comma-seperated architectures #4516

Closed
mr-cal opened this issue Jan 10, 2024 · 3 comments
Closed

regression: remote-build doesn't accept comma-seperated architectures #4516

mr-cal opened this issue Jan 10, 2024 · 3 comments
Labels
bug Actual bad behavior that don't fall into maintenance or documentation

Comments

@mr-cal
Copy link
Collaborator

mr-cal commented Jan 10, 2024

Bug Description

In snapcraft 8.0.1, snapcraft remote-build --architectures=amd64,arm64 fails to split a list of architectures.

This logic needs to be added to the remote-build cli handler.

To Reproduce

snapcraft remote-build --architectures=amd64,arm64

Environment

n/a

snapcraft.yaml

n/a

Relevant log output

2024-01-10 10:21:08.174 remote-build error: Architecture not supported by the remote builder.
The following architectures are not supported by the remote builder: ['amd64,arm64'].
Please remove them from the architecture list and try again.

Additional context

No response

@mr-cal mr-cal added the bug Actual bad behavior that don't fall into maintenance or documentation label Jan 10, 2024
Minoru added a commit to newsboat/newsboat that referenced this issue Jan 24, 2024
1. `--build-for` got broken: canonical/snapcraft#4516
2. delta files are no longer created.
@mr-cal mr-cal closed this as completed Feb 7, 2024
@mr-cal
Copy link
Collaborator Author

mr-cal commented Feb 7, 2024

Regression fixed in #4543

Minoru added a commit to newsboat/newsboat that referenced this issue Mar 3, 2024
`--build-for` reverted to its previous behaviour:
canonical/snapcraft#4516
@JGCarroll
Copy link
Contributor

Hi,

As of Snapcraft 8.2.7, this appears to have returned in the exact same manner as it were originally.

@mr-cal
Copy link
Collaborator Author

mr-cal commented Aug 19, 2024

Thanks, unfortunately Snapcraft has regressed on this again. I will track this in a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Actual bad behavior that don't fall into maintenance or documentation
Projects
None yet
Development

No branches or pull requests

2 participants