linuxboot / linuxboot/heads

Find orgs willing to host Heads/coreboot tarball mirrors from Purism

Open
#1,767 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature freeze - 2025-01-30
Dominant language
Makefile
Stars
1.6k
Forks
211
Avg merge
4d 21h
Merged PRs (30d)
6

Description

pur.ism domain went offline yesterday, as reported in many places over Matrix channels from at home ROM builders.

As of today, only one mirror is available for packages https://github.com/linuxboot/heads/blob/51ade5bd10f6866f5a1afc5442ac5d2bc3aa7a20/bin/fetch_source_archive.sh#L6

This DNS renewal problem is not the first nor will be the last, but in puri.sm case, prevented matrix, CircleCI compilation of some packages, Purism forum, main website and all puri.sm subdomains to be reachable.

I contacted Todd by email from registrar public reference, but that email was read only late and no action was took in a timely matter so that working hours of registrar permitted fixing the issue in a timely manner. _Having one mirror is better then none, having many would be better_. Even more if tarballs would be unified, but where we still reply on puris.sm for coreboot forks and github for mostly anything needed otherwise, but as tarball hacks. This should be generalized so that tarballs is norm for everythig and cached and mirrored, and used.

---

Two solutions for the future :
- Administrators/ Point of contact should be managed offline so that maintainers/stakeholders can be contacted from secondary channels (phone, emails. other communication channels)
- Other mirrors need to be added so that this cannot happen for future commit of that one adding new mirrors in the future https://github.com/linuxboot/heads/blob/51ade5bd10f6866f5a1afc5442ac5d2bc3aa7a20/bin/fetch_source_archive.sh#L6

@JonathonHall-Purism ?

----
Some ongoing discussions for rsync mirroring would be interesting, but that would require Purism setting that up first @JonathonHall-Purism

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with bin/fetch_source_archive.sh at the referenced line to understand the current package mirror configuration and how tarballs are fetched. Review the linked discussion and identify organizations willing to host mirrors; the work is complete when a durable, agreed mirror arrangement is documented and the fetch process no longer depends on a single source.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, shell
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.