Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Openbox website is gone
@ 2022-04-28 12:56 Anachron
  2022-04-28 13:00 ` Anachron
                   ` (13 more replies)
  0 siblings, 14 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 12:56 UTC (permalink / raw)
  To: ml

[-- 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).

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: Openbox website is gone
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
@ 2022-04-28 13:00 ` Anachron
  2022-04-28 13:10 ` Anachron
                   ` (12 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:00 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: Openbox website is gone
  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
                   ` (11 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:10 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: Openbox website is gone
  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
                   ` (10 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:12 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: Openbox website is gone
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (2 preceding siblings ...)
  2022-04-28 13:12 ` Anachron
@ 2022-04-28 13:21 ` leahneukirchen
  2022-04-28 13:31 ` Anachron
                   ` (9 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: leahneukirchen @ 2022-04-28 13:21 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: Openbox website is gone
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (3 preceding siblings ...)
  2022-04-28 13:21 ` leahneukirchen
@ 2022-04-28 13:31 ` Anachron
  2022-04-28 13:33 ` How to handle broken sources Anachron
                   ` (8 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:31 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (4 preceding siblings ...)
  2022-04-28 13:31 ` Anachron
@ 2022-04-28 13:33 ` Anachron
  2022-04-28 13:33 ` Anachron
                   ` (7 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:33 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (5 preceding siblings ...)
  2022-04-28 13:33 ` How to handle broken sources Anachron
@ 2022-04-28 13:33 ` Anachron
  2022-04-28 13:34 ` Anachron
                   ` (6 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:33 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (6 preceding siblings ...)
  2022-04-28 13:33 ` Anachron
@ 2022-04-28 13:34 ` Anachron
  2022-04-28 16:00 ` 4ricci
                   ` (5 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: Anachron @ 2022-04-28 13:34 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (7 preceding siblings ...)
  2022-04-28 13:34 ` Anachron
@ 2022-04-28 16:00 ` 4ricci
  2022-04-28 16:08 ` 4ricci
                   ` (4 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: 4ricci @ 2022-04-28 16:00 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (8 preceding siblings ...)
  2022-04-28 16:00 ` 4ricci
@ 2022-04-28 16:08 ` 4ricci
  2022-04-28 16:13 ` 4ricci
                   ` (3 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: 4ricci @ 2022-04-28 16:08 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (9 preceding siblings ...)
  2022-04-28 16:08 ` 4ricci
@ 2022-04-28 16:13 ` 4ricci
  2022-04-28 18:09 ` 4ricci
                   ` (2 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: 4ricci @ 2022-04-28 16:13 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (10 preceding siblings ...)
  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
  13 siblings, 0 replies; 15+ messages in thread
From: 4ricci @ 2022-04-28 18:09 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (11 preceding siblings ...)
  2022-04-28 18:09 ` 4ricci
@ 2022-07-28  2:15 ` github-actions
  2022-08-12  2:14 ` [ISSUE] [CLOSED] " github-actions
  13 siblings, 0 replies; 15+ messages in thread
From: github-actions @ 2022-07-28  2:15 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [ISSUE] [CLOSED] How to handle broken sources
  2022-04-28 12:56 [ISSUE] Openbox website is gone Anachron
                   ` (12 preceding siblings ...)
  2022-07-28  2:15 ` github-actions
@ 2022-08-12  2:14 ` github-actions
  13 siblings, 0 replies; 15+ messages in thread
From: github-actions @ 2022-08-12  2:14 UTC (permalink / raw)
  To: ml

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2022-08-12  2:14 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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).