[ISSUE] Openbox website is gone

[ISSUE] Openbox website is gone

[Anachron]

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

New issue by Anachron on void-packages repository

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

Description:
https://www.openbox.org/

Seems like someone didn't renew subscription. We should probably switch to https://github.com/Mikachu/openbox (as it still has `3.6.1` tag that we have packaged).

Re: Openbox website is gone

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Should we maybe create a script that automatically catches missing sources and notifies us?

@q66 @leahneukirchen @ahesford @abenson 

Re: Openbox website is gone

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Seems like a local issue with my `ISP` or `VPS` provider. I will investigate further.

Problem stands: How do we handle gone sources?

Re: Openbox website is gone

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Seems like a local issue with my `ISP` or `VPS` provider. I will investigate further.

Problem stands: How do we handle gone sources?

Edit:
Isn't the internet a beautiful system?

```
$ getent hosts openbox.org
134.117.27.24   openbox.org

$ getent hosts cccg.ca
134.117.27.24   cccg.ca
```

Re: Openbox website is gone

[leahneukirchen]

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

New comment by leahneukirchen on void-packages repository

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

Comment:
Loads fine here, and virtual hosting is nothing new either.

We have copies of old tarballs on https://sources.voidlinux.org/openbox-3.6.1/ and else use Debian as a fallback.

Ideally they'd add the tarballs to the releases of course.

Re: Openbox website is gone

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Yeah I figured it's on my end, read my third reply. I'm still debugging. 

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

Re: How to handle broken sources

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Should we maybe create a script that automatically catches missing sources and notifies us?

@q66 @leahneukirchen @ahesford @abenson 

Re: How to handle broken sources

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Seems like a local issue with my `ISP` or `VPS` provider. I will investigate further.

Problem stands: How do we handle gone sources?

Edit:
Isn't the internet a beautiful system?

```
$ getent hosts openbox.org
134.117.27.24   openbox.org

$ getent hosts cccg.ca
134.117.27.24   cccg.ca
```

Re: How to handle broken sources

[Anachron]

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

New comment by Anachron on void-packages repository

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

Comment:
Yeah I figured it's on my end, read my third reply. I'm still debugging. 

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

Edit: Edited the issue to reflect that this topic is now about a script to check for missing sources.

Re: How to handle broken sources

[4ricci]

[-- Attachment #1: Type: text/plain, Size: 1011 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
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
```

Re: How to handle broken sources

[4ricci]

[-- 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
```

Re: How to handle broken sources

[4ricci]

[-- Attachment #1: Type: text/plain, Size: 1065 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
        i="${i%>*}"
        if ! curl --silent --location --head --fail -o /dev/null "$i"; then
                        echo "$pkg: url $i is broken"
                fi
        done
done
```

Re: How to handle broken sources

[4ricci]

[-- Attachment #1: Type: text/plain, Size: 1080 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 successful 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
                i="${i%>*}"
                if ! curl --silent --location --head --fail -o /dev/null "$i"; then
                        echo "$pkg: url $i is broken"
                fi
        done
done
```

Re: How to handle broken sources

[github-actions]

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

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] How to handle broken sources

[github-actions]

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

Closed issue by Anachron on void-packages repository

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

Description:
I was asking myself if we should run a script periodically (like check-updates) that checks if the source is still available?