Re: [squid-dev] mirrors with missing files

[Alex Rousskov]

On 2023-11-02 07:59, Stuart Henderson wrote:

On 2023-11-01, Amos Jeffries  wrote:

On 1/11/23 09:59, Alex Rousskov wrote:

On 2023-10-31 15:39, Francesco Chemolli wrote:

Before we can migrate ..., we need to deprecate, cleanup and simplify
a lot.


Do you really, really _need_ to "deprecate, cleanup, and simplify a lot"
in order to stop mirroring tomorrow?! Start doing new minor releases on
GitHub a month from now? FWIW, I have asked for specifics many times,
but am still unaware of any serious obstacles on the way to those goals.



As I have mentioned multiple times ... there is a reason we have Jenkins
building the tarballs.


Please run the following commands:

wget
https://github.com/squid-cache/squid/archive/refs/tags/SQUID_6_3.tar.gz &&
tar -xvf SQUID_6_3.tar.gz &&
./configure &&
make check


That's using github's on-the-fly generated tarballs; it's also possible to
upload a "release artefact" which is the proper project-generated tar.gz.



Hi Stuart,

I hope you have better luck with dismantling these poor excuses and 
FUD! I have been doing that for a long time with no signs of success. 
"Where there is a will, there is a way". We lack the former IMO.



> (and it doesn't preclude _also_ having mirrors)

... or other valid solutions (for other problems, including the alleged 
problem of "USA hosted content").


Alex.



See e.g. the irssi releases, https://github.com/irssi/irssi/releases/tag/1.4.5
(though also notice the ugly way they try to make sure people download the
correct file...)



___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Stuart Henderson]

On 2023-11-01, Amos Jeffries  wrote:
> On 1/11/23 09:59, Alex Rousskov wrote:
>> On 2023-10-31 15:39, Francesco Chemolli wrote:
>>> Before we can migrate ..., we need to deprecate, cleanup and simplify 
>>> a lot.
>> 
>> Do you really, really _need_ to "deprecate, cleanup, and simplify a lot" 
>> in order to stop mirroring tomorrow?! Start doing new minor releases on 
>> GitHub a month from now? FWIW, I have asked for specifics many times, 
>> but am still unaware of any serious obstacles on the way to those goals.
>> 
>
> As I have mentioned multiple times ... there is a reason we have Jenkins 
> building the tarballs.
>
>
> Please run the following commands:
>
> wget 
> https://github.com/squid-cache/squid/archive/refs/tags/SQUID_6_3.tar.gz &&
>   tar -xvf SQUID_6_3.tar.gz &&
>   ./configure &&
>   make check

That's using github's on-the-fly generated tarballs; it's also possible to
upload a "release artefact" which is the proper project-generated tar.gz.
See e.g. the irssi releases, https://github.com/irssi/irssi/releases/tag/1.4.5
(though also notice the ugly way they try to make sure people download the
correct file...)

(and it doesn't preclude _also_ having mirrors)


___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Alex Rousskov]

On 2023-11-01 12:05, Amos Jeffries wrote:

On 1/11/23 09:59, Alex Rousskov wrote:

On 2023-10-31 15:39, Francesco Chemolli wrote:
Before we can migrate ..., we need to deprecate, cleanup and simplify 
a lot.


Do you really, really _need_ to "deprecate, cleanup, and simplify a 
lot" in order to stop mirroring tomorrow?! Start doing new minor 
releases on GitHub a month from now? FWIW, I have asked for specifics 
many times, but am still unaware of any serious obstacles on the way 
to those goals.


As I have mentioned multiple times ... there is a reason we have Jenkins 
building the tarballs.


The reasons I have heard multiple times do not preclude disabling 
mirroring tomorrow and doing releases on GitHub a month from now.



AFAICT, there is just lack of shared goals (or shared priorities) 
rather than serious obstacles on the way of achieving those two 
specific goals.


FWIW, one of those goals that we appear not to share is freedom of 
information > ... specifically to have Squid code available to everyone.
FWIW, I support that particular goal (among others). That goal certainly 
does not preclude disabling mirroring tomorrow and doing releases on 
GitHub a month from now.



There exist countries in this world who forbid access to USA hosted 
content. Having squid-cache.org mirrored keeps us largely out of the 
political arean.


We do not need mirrors to make Squid available on non-US hosted servers, 
especially stale, broken, and infested mirrors (i.e. the subject of this 
email thread).


Alex.

___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Amos Jeffries]

On 1/11/23 09:59, Alex Rousskov wrote:

On 2023-10-31 15:39, Francesco Chemolli wrote:
Before we can migrate ..., we need to deprecate, cleanup and simplify 
a lot.


Do you really, really _need_ to "deprecate, cleanup, and simplify a lot" 
in order to stop mirroring tomorrow?! Start doing new minor releases on 
GitHub a month from now? FWIW, I have asked for specifics many times, 
but am still unaware of any serious obstacles on the way to those goals.




As I have mentioned multiple times ... there is a reason we have Jenkins 
building the tarballs.



Please run the following commands:

wget 
https://github.com/squid-cache/squid/archive/refs/tags/SQUID_6_3.tar.gz &&

tar -xvf SQUID_6_3.tar.gz &&
./configure &&
make check

AFAICT, there is just lack of shared goals (or shared priorities) rather 
than serious obstacles on the way of achieving those two specific goals.





FWIW, one of those goals that we appear not to share is freedom of 
information ... specifically to have Squid code available to everyone. 
There exist countries in this world who forbid access to USA hosted 
content. Having squid-cache.org mirrored keeps us largely out of the 
political arean.



Cheers
Amos
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Alex Rousskov]

On 2023-10-31 15:39, Francesco Chemolli wrote:
Before we can migrate ..., we need to 
deprecate, cleanup and simplify a lot.


Do you really, really _need_ to "deprecate, cleanup, and simplify a lot" 
in order to stop mirroring tomorrow?! Start doing new minor releases on 
GitHub a month from now? FWIW, I have asked for specifics many times, 
but am still unaware of any serious obstacles on the way to those goals.


AFAICT, there is just lack of shared goals (or shared priorities) rather 
than serious obstacles on the way of achieving those two specific goals.


Alex.


On 2023-10-31 15:39, Francesco Chemolli wrote:
> Hi all,
> I agree, it would be awesome to rely on a more more than delivery
> network for our website.
> At this time it is complicated. Oh website is large as a result of
> posting mailing list, archives and a lot of release files, patches,
> change sets. Before we can migrate to anything different, we need to
> deprecate, cleanup and simplify a lot.
> Any help would be greatly appreciated
>
> @mobile
>


On Tue, 31 Oct 2023 at 19:32, Alex Rousskov wrote:

On 2023-10-31 06:08, Adam Majer wrote:
 > I've looked at the mirrors posted,
 >
 > http://www.squid-cache.org/Download/mirrors.html
 >
 > and these seem all obsolete.

Thank you for doing this analysis! I have been begging the Project to
drop all mirrors for a long time now. I failed to convince others that
the associated embarrassment and waste of time are just not worth the
benefits. Maybe your observations will be the last straw...


 > I'm not sure, but maybe a more reliable way would be to migrate to
 > github.com  for the releases.

FWIW, I am quite sure, and has been making that suggestion for several
years now. GitHub is far from perfect, but using its release posting
features (correctly) will dramatically decrease our release overheads
and delays. This migration is not trivial, and I have failed to
convince
others that it is worth their time to start migrating.

Alex.

___
squid-dev mailing list
squid-dev@lists.squid-cache.org 
https://lists.squid-cache.org/listinfo/squid-dev




___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Francesco Chemolli]

Hi all,
I agree, it would be awesome to rely on a more more than delivery network
for our website.
At this time it is complicated. Oh website is large as a result of posting
mailing list, archives and a lot of release files, patches, change sets.
Before we can migrate to anything different, we need to deprecate, cleanup
and simplify a lot.
Any help would be greatly appreciated

@mobile


On Tue, 31 Oct 2023 at 19:32, Alex Rousskov <
rouss...@measurement-factory.com> wrote:

> On 2023-10-31 06:08, Adam Majer wrote:
> > I've looked at the mirrors posted,
> >
> >http://www.squid-cache.org/Download/mirrors.html
> >
> > and these seem all obsolete.
>
> Thank you for doing this analysis! I have been begging the Project to
> drop all mirrors for a long time now. I failed to convince others that
> the associated embarrassment and waste of time are just not worth the
> benefits. Maybe your observations will be the last straw...
>
>
> > I'm not sure, but maybe a more reliable way would be to migrate to
> > github.com for the releases.
>
> FWIW, I am quite sure, and has been making that suggestion for several
> years now. GitHub is far from perfect, but using its release posting
> features (correctly) will dramatically decrease our release overheads
> and delays. This migration is not trivial, and I have failed to convince
> others that it is worth their time to start migrating.
>
> Alex.
>
> ___
> squid-dev mailing list
> squid-dev@lists.squid-cache.org
> https://lists.squid-cache.org/listinfo/squid-dev
>
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Alex Rousskov]

On 2023-10-31 06:08, Adam Majer wrote:

I've looked at the mirrors posted,

   http://www.squid-cache.org/Download/mirrors.html

and these seem all obsolete.


Thank you for doing this analysis! I have been begging the Project to 
drop all mirrors for a long time now. I failed to convince others that 
the associated embarrassment and waste of time are just not worth the 
benefits. Maybe your observations will be the last straw...



I'm not sure, but maybe a more reliable way would be to migrate to 
github.com for the releases.


FWIW, I am quite sure, and has been making that suggestion for several 
years now. GitHub is far from perfect, but using its release posting 
features (correctly) will dramatically decrease our release overheads 
and delays. This migration is not trivial, and I have failed to convince 
others that it is worth their time to start migrating.


Alex.

___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] mirrors with missing files

[Adam Majer]

I've looked at the mirrors posted,

  http://www.squid-cache.org/Download/mirrors.html

and these seem all obsolete. The Canadian one has squid 6.1, and the 
rest don't go past 5.9 or are simply no longer resolving.



I'm not sure, but maybe a more reliable way would be to migrate to 
github.com for the releases. There are already tags there, but are 
missing is just the signed tarballs.


https://github.com/squid-cache/squid/releases

- Adam

PS. FWIW, the download of squid 6.4 is not reliable in the DNS rotation 
as some of the mirrors there are broken.


These two mirrors are broken (mirror.marwan.ma), returning 404

196.200.160.70
2001:4310:f1::70

and these two are working...

67.215.9.148
212.199.163.170

___
squid-dev mailing list
squid-dev@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-dev