Github messages for voidlinux
 help / color / mirror / Atom feed
From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: How to handle broken sources
Date: Thu, 28 Apr 2022 18:08:11 +0200	[thread overview]
Message-ID: <20220428160811.WMEuPWOIqYajOYvJko0lV12xsqm9Nn_AcSeoNqN7g4A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36895@inbox.vuxu.org>

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

New comment by 4ricci on void-packages repository

https://github.com/void-linux/void-packages/issues/36895#issuecomment-1112383806

Comment:
> Nonetheless, I think a script to watch for broken links cannot hurt in the future.

It shouldn't be too hard. Something like this will verify the hashes too (but also download a lot of stuff):
```sh
rm -rf hostdir/sources
for i in $(find srcpkgs -name template | cut -d / -f 2); do
        ./xbps-src -I fetch "$i" >/dev/null 2>&1 || echo "$i: broken distfiles"
done
```

This one will just check if the the server returns a successfull status code:
```bash
source common/environment/setup/misc.sh
for pkg in $(find srcpkgs -name template | cut -d / -f 2); do
        unset homepage changelog distfiles
        source srcpkgs/"$pkg"/template 2>/dev/null
        for i in $homepage $changelog $distfiles; do
                if ! curl --silent --location --head --fail -o /dev/null "$i"; then
                        echo "$pkg: url $i is broken"
                fi
        done
done
```

  parent reply	other threads:[~2022-04-28 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
2022-04-28 13:00 ` Anachron
2022-04-28 13:10 ` Anachron
2022-04-28 13:12 ` Anachron
2022-04-28 13:21 ` leahneukirchen
2022-04-28 13:31 ` Anachron
2022-04-28 13:33 ` How to handle broken sources Anachron
2022-04-28 13:33 ` Anachron
2022-04-28 13:34 ` Anachron
2022-04-28 16:00 ` 4ricci
2022-04-28 16:08 ` 4ricci [this message]
2022-04-28 16:13 ` 4ricci
2022-04-28 18:09 ` 4ricci
2022-07-28  2:15 ` github-actions
2022-08-12  2:14 ` [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=20220428160811.WMEuPWOIqYajOYvJko0lV12xsqm9Nn_AcSeoNqN7g4A@z \
    --to=4ricci@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).