Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

NZ Repository problem?

Discussion about the MEPIS Community's Repo.
Post Reply
Message
Author
User avatar
Gordon Cooper
Forum Guide
Forum Guide
Posts: 1983
Joined: Mon Nov 21, 2011 5:50 pm

NZ Repository problem?

#1 Post by Gordon Cooper » Sat Dec 03, 2016 9:39 pm

Currently getting 404 error for three items notified e.g. http://mx.debian.nz/mx/repo/pool/main/t ... _amd64.deb 404 Not Found. Others are snapshot and smxi-inxi.

Was like this 7 hours ago, waited but no change. Anyone else with similar error?
Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
Primary OS : MX-17.1 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.
Dell9010, MX-17.1, Win7

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4343
Joined: Wed Jul 12, 2006 4:05 pm

Re: NZ Repository problem?

#2 Post by timkb4cq » Sat Dec 03, 2016 9:47 pm

The current version that should be on the server is: thunderbird_45.5.1~mozillabinaries-1mx15+1_amd64.deb
Try running sudo apt-get update, or reloading in Synaptic.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
tascoast
Forum Guide
Forum Guide
Posts: 1081
Joined: Sat Aug 06, 2011 4:58 am

Re: NZ Repository problem?

#3 Post by tascoast » Sat Dec 03, 2016 9:57 pm

It's OK here for 64-bit. I did have some 404 glitches a few days ago but seemed to get over that.
My 32-bit install just updated fine.
I updated Thunderbird earlier on the 64-bit install. I'll try the Live USB 64-bit next.... :thumbup:

(I suppose all the failed translation bits are just nothing to worry about, since they have always appeared during a reload)
Lenovo ThinkCentre A58 4GBRAM, MX-16 RC1/MX14.04/MX-15.01/antiX16(64-bit)-Aspire One D255E 1.66GHz, 512KB cache, 1GB RAM-MX-15.01/W10

User avatar
Gordon Cooper
Forum Guide
Forum Guide
Posts: 1983
Joined: Mon Nov 21, 2011 5:50 pm

Re: NZ Repository problem?

#4 Post by Gordon Cooper » Sat Dec 03, 2016 10:22 pm

Was still getting 404's when working thru' the notifier so downloaded them with Synaptic, probably a glitch at my end as synaptic listed extra update packages not showing through the notifier. Thanks.
Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
Primary OS : MX-17.1 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.
Dell9010, MX-17.1, Win7

User avatar
BitJam
Forum Guide
Forum Guide
Posts: 2472
Joined: Sat Aug 22, 2009 11:36 pm

Re: NZ Repository problem?

#5 Post by BitJam » Sat Dec 03, 2016 10:30 pm

If one of our repos goes down, you can have you sources pointed to the next closest repo with the command:

Code: Select all

sudo localize-repo --ignore=$REPO_CODE <country-code|timezone>
The current repo codes are:

Code: Select all

ec = Ecuador
gr = Greece
la = Los Angeles, USA
nl = Netherlands
nz = New Zealand
ut = Utah, USA
tw = Taiwan
So if you are in New Zealand and you want to bypass our New Zealand repo for for now then run:

Code: Select all

sudo localize-repo --ignore nz nz
Use --hosts to see the hosts that would be used without making any changes. For example:

Code: Select all

localize-reopo --hosts --ignore=nz nz
 AX: http://ftp.yzu.edu.tw/Linux/mx-workspace/antix
 MX: http://ftp.yzu.edu.tw/Linux/mx-workspace/mx
 MP: http://ftp.yzu.edu.tw/Linux/mx-workspace/mepiscr
deb: ftp.nz.debian.org/debian
Once the repo is back up you can change back to it by omitting the --ignore parameter.

On the live system you can accomplish the same thing with the "norepo=xx" cheat. For example to avoid the New Zealand repo use "norepo=nz".
Will I cry when it's all over?
When I die will I see Heaven?

User avatar
Gordon Cooper
Forum Guide
Forum Guide
Posts: 1983
Joined: Mon Nov 21, 2011 5:50 pm

Re: NZ Repository problem?

#6 Post by Gordon Cooper » Sun Dec 04, 2016 3:46 am

@ Bitjam. Thank you for that guidance. I have no problems working with repos, but have been using the Repo Manager in MX Tools to change a source. Have not really solved the original error. When the NZ server seemed to be failing, I swapped over to Taiwan and found a partially different and much smaller list of updates.
Came back to NZ and was told that over a dozen packages, already installed, were surplus and that apt-get autoremove should be used to delete them. These must/may have been picked up as dependencies for something that I had not intentionally downloaded. Something was definitely wrong but not defined, and as Tascoast, across the ditch, found no difficulties, it is probably an error on my part. All seems to be behaving now, so will wait for the next time, if it ever happens.
Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
Primary OS : MX-17.1 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.
Dell9010, MX-17.1, Win7

Post Reply

Return to “CR Discussion”