xmlto: sources no longer available from upstream
Maintainers usually reply within 1 day
@L1TerminalFault is already working on this.
Since Oct 28, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- shell, xml
- Domain
- build-system
Research direction
The failing download is the source URL in the xmlto package template under srcpkgs/xmlto, which points at pagure.io and now returns Not Found. Start by checking that template's distfiles and checksum fields, then compare against the Linux From Scratch mirror the reporter linked. Done means the template fetches and its checksum verifies, verified by running xbps-src on the xmlto package.
Written by the indexing model from the issue text.
Description
Is this a new report?
Yes
System Info
Void 7.2.12_1 x86_64-musl AuthenticAMD uptodate rF
Package(s) Affected
xmlto-0.0.29_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Correct download of xmlto.
Actual behaviour
=> xmlto-0.0.29_1: fetching distfile 'xmlto-0.0.29.tar.gz' from 'https://pagure.io/xmlto/archive/0.0.29/xmlto-0.0.29.tar.gz'...
ERROR: xbps-fetch: failed to fetch: https://pagure.io/xmlto/archive/0.0.29/xmlto-0.0.29.tar.gz: Not Found
=> ERROR: xmlto-0.0.29_1: failed to fetch 'xmlto-0.0.29.tar.gz'.
Following the sunset of Pagure, it appears the xmlto release is no longer available
The Linux From Scratch mirror of it passes checksum verification. https://anduin.linuxfromscratch.org/BLFS/xmlto/xmlto-0.0.29.tar.gz
Steps to reproduce
Build xmlto.
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 2.8k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 335
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from void-linux/void-packages
-
bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
void-linux/void-packages#63249 ·
Maintainers usually reply within 1 day
-
AI 🤖 bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
void-linux/void-packages#63041 · 1 comment ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63016 ·
Maintainers usually reply within 1 day
-
nextcloud-client: VFS plugins installed where the client does not searchMay be free again A pull request for this issue was closed without being merged. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
void-linux/void-packages#62700 ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
void-linux/void-packages#62661 ·
Maintainers usually reply within 1 day
All issues in void-linux/void-packages
Similar issues
-
GEFSv12
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 64/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100