Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Hunt for dead packages & more
Date: Tue, 09 Aug 2022 15:23:17 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38555@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]

New issue by meator on void-packages repository

https://github.com/void-linux/void-packages/issues/38555

Description:
Hi. I've compiled a list of all distfiles and homepages of all packages in the void-packages GitHub repository. I then tried to test each and every URL Voidlinux has to offer to see whether they are still accessible without problems. Here is a JSON file that represents several days of sending HEAD requests[^1].

[data.json](https://github.com/void-linux/void-packages/files/9290529/data.json.txt)

I've only processed the template files, so packages that were [removed from the repos](https://github.com/void-linux/void-packages/issues/23575) but are still on the mirrors aren't listed in the file. I hope this will help me and others to uncover dead links and other problems with the packages.

The JSON file is a collections of URLs and responses. There are three types of responses:

1. normal response (for example `HTTP/2 200` or `HTTP/1.1 404 Not Found`)
2. `Error`: This means that `curl -Is` had a nonzero exit status (the page probably doesn't exist anymore).
3. `Timed out`: It took more than a minute to get the info.

I will in the near future make a PR that will remove or fix the packages with `Error` or 404 status.

I've also noticed that some `http://` links returned `HTTP/1.1 301 Moved Permanently`. [Repology also doesn't like `http`](https://repology.org/repository/void_x86_64/problems). It might be useful to `https`ify all `http` links which support it to improve security and to make Repology happy. But a bulk `distfiles` and `homepage` change would mean that a lot o packages would have to be rebuilt just to change the metadata of the package. One solution would be to do it but without revbumping the files, but usefulness of this is questionable. What do you think?

[^1]: I've been using `curl -Is | head -1` to do the work so FTP files have `Last-Modified` instead of HTTP response or nothing at all (but that doesn't mean it's bad). The gopher URLs also don't have anything there (there are only two of those URLs: `geomyidae` and `sacc` homepages).

             reply	other threads:[~2022-08-09 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 13:23 meator [this message]
2022-08-09 13:56 ` meator
2022-08-14  8:43 ` meator
2022-08-24  0:08 ` classabbyamp
2022-08-24  0:10 ` classabbyamp
2022-08-24  7:47 ` meator
2022-11-23  2:06 ` github-actions
2022-12-07  2:37 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38555@inbox.vuxu.org \
    --to=meator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).