Skip to content

Conversation

maflcko
Copy link
Contributor

@maflcko maflcko commented Jun 30, 2025

Remove them, similar to the rpm removal.

Also, remove third-party maintained bitcoin-core packages from the list, while touching this file, as explained in the commit message.

@maflcko maflcko force-pushed the 2506-deb-readme branch from dc1399b to 5fe09b9 Compare July 3, 2025 16:36
MarcoFalke added 3 commits July 3, 2025 18:44
@maflcko maflcko force-pushed the 2506-deb-readme branch from 5fe09b9 to 797c1a6 Compare July 3, 2025 16:45
@fanquake
Copy link
Member

@maflcko
Copy link
Contributor Author

maflcko commented Jul 28, 2025

I haven't looked extensively, but there are packagers that point directly to these files. i.e https://github.com/NixOS/nixpkgs/blob/9771deb49b9b8b0b83615d11c070b071b18db2ab/pkgs/applications/blockchains/bitcoin/default.nix#L31 or https://github.com/void-linux/void-packages/blob/b931884fcc6114400b4cad338a286478b2c731e9/srcpkgs/bitcoin/template#L16.

They shouldn't be affected if they use an URL based on commit id. And using a volatile URL in build scripts seems brittle anyway. But I am happy to close this one.

Should I move the third commit to a new pull?

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.

2 participants