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

Impossible to release to AUR when more than 2 packages are defined in a single file #4679

Closed
3 of 4 tasks
bartekpacia opened this issue Mar 10, 2024 · 2 comments · Fixed by #4712
Closed
3 of 4 tasks
Assignees
Labels
bug Something isn't working

Comments

@bartekpacia
Copy link
Contributor

What happened?

Take a look at this GH Actions run:

https://github.com/bartekpacia/fhome/actions/runs/8224293931/job/22487945611

here's the GoReleaser config file: https://github.com/bartekpacia/fhome/blob/c55710f8db41b758b75fd67a1d8624c3fe503adc/.goreleaser.yaml

I'm really not sure what is happening. First item from aurs is released fine, but then second one fails with that error.

How can we reproduce this?

Unfortunately I'm not sure. It happens only on CI where I have set up credentials. I cannot share the credentials.

But I will appreciate if you just take a look at it.

goreleaser version

v1.24.0

GoReleaser Check

  • goreleaser check shows no errors

Search

  • I did search for other open and closed issues before opening this

Supporter

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

No response

@bartekpacia bartekpacia added bug Something isn't working triage Issue pending triage by one of the maintainers labels Mar 10, 2024
@caarlos0
Copy link
Member

def a bug, thanks for reporting

@caarlos0 caarlos0 added bug Something isn't working and removed bug Something isn't working triage Issue pending triage by one of the maintainers labels Mar 11, 2024
caarlos0 added a commit that referenced this issue Mar 19, 2024
closes #4679

Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
@caarlos0
Copy link
Member

check #4712

caarlos0 added a commit that referenced this issue Mar 20, 2024
#4712)

- using the sha256 of the git url as repo name so we avoid race
conditions
- actually made the git client have a global lock so it doesn't step
over itself

closes #4679

Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants