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

xz: Switch from upstream tarball to git tarball #4475

Merged
merged 1 commit into from Mar 29, 2024
Merged

Conversation

lazka
Copy link
Member

@lazka lazka commented Mar 29, 2024

Run autogen to get the documentation built instead of just autoreconf Also needs extra build depends for things already included in the tarball.

And remove the signing key from the bad actor.

Run autogen to get the documentation built instead of just autoreconf
Also needs extra build depends for things already included
in the tarball.

And remove the signing key from the bad actor.
@lazka lazka mentioned this pull request Mar 29, 2024
@lazka lazka merged commit e711dd5 into msys2:master Mar 29, 2024
2 checks passed
@jeremyd2019
Copy link
Member

I'm (already) getting a checksum failure on that new tar.

@jeremyd2019
Copy link
Member

oh, access to the repository has been disabled due to terms of service violation. That's messing up the tar link too.

@jeremyd2019
Copy link
Member

jeremyd2019 commented Mar 30, 2024

For now, I'm reverting to 5.6.0-1 in my i686 msys repo. EDIT: oops, should have read first, 5.6.0 was also backdoored. But, luckily, it sounds like only linux x86_64 was targeted, and then only when building rpm or deb packages. Reverted to 5.4.6-2 now.

@lazka
Copy link
Member Author

lazka commented Mar 30, 2024

uh, annoying. It seems contra productive to hinder people from downgrading, or switching sources.

For now, I'm reverting to 5.6.0-1 in my i686 msys repo. EDIT: oops, should have read first, 5.6.0 was also backdoored. But, luckily, it sounds like only linux x86_64 was targeted, and then only when building rpm or deb packages. Reverted to 5.4.6-2 now.

Yeah, it shouldn't be a problem either way. But using git at least doesn't run any of the found (as of now) problematic code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants