MX Linux Forum

Posted: **Fri Jun 22, 2018 4:34 am**

We are having problems with our server, that we hope to fix Friday/Saturday (US time).

Until this is fixed, using repo-manager change default (http://repo.antixlinux.com/stretch) to another.

Posted: **Fri Jun 22, 2018 11:34 am**

I will update mx-repo-manager to replace the server with a postinst script. No manual changes needed, just do a regular update.

Posted: **Fri Jun 22, 2018 6:18 pm**

anticapitalista wrote: ↑Fri Jun 22, 2018 4:34 am We are having problems with our server, that we hope to fix Friday/Saturday (US time).

Until this is fixed, using repo-manager change default (http://repo.antixlinux.com/stretch) to another.

When I look into one of the mirrors Release-files like this one
http://iso.mxrepo.com/antix/stretch/dis ... ch/Release
or this one
https://ftp.fau.de/mxlinux-packages/ant ... ch/Release
I do see references to Content-files like this example:

Code: Select all

 98c0cf9a19a82e500b18dcd49e77c3eb 114784994 main/Contents-amd64
 282ec630f2952efef93460870958ae68 5819077 main/Contents-amd64.gz

But there are no Content-files neither here
http://iso.mxrepo.com/antix/stretch/dists/stretch/main/
nor here
https://ftp.fau.de/mxlinux-packages/ant ... etch/main/
The actual Content-files are here:
http://iso.mxrepo.com/antix/stretch/dists/stretch/ or
https://ftp.fau.de/mxlinux-packages/ant ... s/stretch/
I assume that might be the reason I got error messages within some of my mx installations.
IMHO, the content files need either go into the subfolder or the Release-files needs to get fixed.

fehlix

Posted: **Fri Jun 22, 2018 7:24 pm**

Probably because they have pulled from the antiX repo when it was down. Patience is needed until it is fully fixed.

Posted: **Fri Jun 22, 2018 7:47 pm**

anticapitalista wrote: ↑Fri Jun 22, 2018 7:24 pm Probably because they have pulled from the antiX repo when it was down. Patience is needed until it is fully fixed.

Not sure how mirroring takes place, but would not assume a mirror put's the files into the wrong directory.
Looking onto the time stamp they match to the release files. But might just wrongly placed Content files within the master itself. So yes, we are patient.

Code: Select all

┌<─ ftp://ftp.fau.de/mxlinux-packages/antix/stretch/dists/stretch ────.[^]>┐
│.n                      Name                        │ Size  │ Modify time │
│/..                                                 │UP--DIR│11. Jun 2017 │
│/dev                                                │   4096│11. Jun 2017 │
│/main                                               │   4096│11. Jun 2017 │
│/nosystemd                                          │   4096│11. Jun 2017 │
│ Contents-amd64.gz                                  │5819077│15. Jun 22:42│
│ Contents-i386.gz                                   │7992100│15. Jun 22:41│
│ Contents-i486.gz                                   │1127938│15. Jun 22:42│
│ Contents-i686.gz                                   │1127938│15. Jun 22:42│
│ Contents-ia64.gz                                   │1127938│15. Jun 22:42│
│ Release                                            │  20177│15. Jun 22:42│
│ Release.gpg                                        │    473│15. Jun 22:42│
├──────────────────────────────────────────────────────────────────────────┤
│UP--DIR                                                                   │
└──────────────────────────────────────────────────────────────────────────┘

MX Linux Forum

antiX default repos unreliable

antiX default repos unreliable

Re: antiX default repos unreliable

Re: antiX default repos unreliable

Re: antiX default repos unreliable

Re: antiX default repos unreliable