* [ISSUE] Hunt for dead packages & more
@ 2022-08-09 13:23 meator
2022-08-09 13:56 ` meator
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: meator @ 2022-08-09 13:23 UTC (permalink / raw)
To: ml
[-- 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).
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
@ 2022-08-09 13:56 ` meator
2022-08-14 8:43 ` meator
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: meator @ 2022-08-09 13:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/38555#issuecomment-1209417495
Comment:
Here is a more `grep` friendly version (beware, CRLF):
[data.txt](https://github.com/void-linux/void-packages/files/9291348/data.txt)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
2022-08-09 13:56 ` meator
@ 2022-08-14 8:43 ` meator
2022-08-24 0:08 ` classabbyamp
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: meator @ 2022-08-14 8:43 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/38555#issuecomment-1214312738
Comment:
Here is the same data with added `maintainer`:
[data.txt](https://github.com/void-linux/void-packages/files/9332966/data.txt)
[data.json](https://github.com/void-linux/void-packages/files/9332967/data.json.txt)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
2022-08-09 13:56 ` meator
2022-08-14 8:43 ` meator
@ 2022-08-24 0:08 ` classabbyamp
2022-08-24 0:10 ` classabbyamp
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2022-08-24 0:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/38555#issuecomment-1225010238
Comment:
repology has a nice list of similar problems: https://repology.org/repository/void_x86_64/problems
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
` (2 preceding siblings ...)
2022-08-24 0:08 ` classabbyamp
@ 2022-08-24 0:10 ` classabbyamp
2022-08-24 7:47 ` meator
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2022-08-24 0:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/38555#issuecomment-1225010238
Comment:
repology has a nice list of similar problems: https://repology.org/repository/void_x86_64/problems ([json](https://repology.org/api/v1/repository/void_x86_64/problems))
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
` (3 preceding siblings ...)
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
6 siblings, 0 replies; 8+ messages in thread
From: meator @ 2022-08-24 7:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/38555#issuecomment-1225327261
Comment:
Repology is great but they (I think) don't include the distfiles which are the main problem. I've included the same link to my first comment.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
` (4 preceding siblings ...)
2022-08-24 7:47 ` meator
@ 2022-11-23 2:06 ` github-actions
2022-12-07 2:37 ` [ISSUE] [CLOSED] " github-actions
6 siblings, 0 replies; 8+ messages in thread
From: github-actions @ 2022-11-23 2:06 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/38555#issuecomment-1324457693
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] 8+ messages in thread
* Re: [ISSUE] [CLOSED] Hunt for dead packages & more
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
` (5 preceding siblings ...)
2022-11-23 2:06 ` github-actions
@ 2022-12-07 2:37 ` github-actions
6 siblings, 0 replies; 8+ messages in thread
From: github-actions @ 2022-12-07 2:37 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Closed 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).
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-12-07 2:37 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-09 13:23 [ISSUE] Hunt for dead packages & more meator
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
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).