Are the Mepis 3.43 repos

Which repo fails? If everytime is a different one then maybe it's a temporary problem with that one, if it's the same one it might be absolete or replaced with a different one, please provide info...
--
Check out Mepis wiki: www.mepis.org/docs

I will give an example right now: as I type this reply, I will access synaptic.

Step 01 -- I go into synaptic, no problem.

Step 02 -- I hit "reload" and this is where the "problem" begins. I always have 13 packages or whatever they are called to download.

Then I get this message:

The repository might be no longer available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and the correct writing of the repository address in the preferences.

ftp://ftp.nerim.net/debian-marillat/dists/etch/main/binary-i386/Packages.gz: Unable to fetch file, server said 'Can't open /debian-marillat/dists/etch/main/binary-i386/Packages.gz: No such file or directory ' [IP: 62.4.17.14 21]

Step 03 -- Then I get this:

The following problems were found on your system:

W: There are no public key available for the following key IDs: A70DAF536070D3A1

Step 04 -- I hit "ok" and I am back in synaptic, ready and able to download stuff, except I suppose whatever those messages said I cannot download.

Step 05 -- As far as "failure consistency" (i.e., which repo, package, etc) in Step 02, it seems to vary. Usually it is only one (1) repo that fails but I have had two (2) or more "fail." I have not kept track of exactly which repos fail. The public key (Step 03) statement has been around for quite some time too, but I don't think it has been around as long as the repo problem.

Does the above information tell you anything? I don't know what it means. I've been getting stuff like that for many months.

I never paid attention to it because I never thought it impacted me. However, I am trying to install VMware Server (I have a post or two on this website detailing my VMware Server efforts) and have received messages about repos or packages as "Failed to fetch" or 'Failed to open file', so it made me wonder if I had a synaptic based problem.

ftp://ftp.nerim.net/ doesn't exit anymore, if you search on Google you'll find explanations...

For this issue look here:
www.mepis.org/docs/en/index.php/Public_key_not_available_error

--
Check out Mepis wiki: www.mepis.org/docs

Also, there is a lot of activity going on in the Debian community. On my 3.3 machines that are at a client's site, I have had to modify my repositories to go to various "mirror" sites. The main ones just seem to get bogged down.

All I can suggest is to be patient

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless

Adrian, Jon:

Thank you for that info.

I now know that the repo in question is down.

Strangely though, this other repo:

"ftp://ftp.us.debian.org"

seems to be the specific repo causing trouble with my VMware Server install efforts. I posted a long terminal output on my VMware post (http://www.mepis.org/node/11985). The "ftp://ftp.us.debian.org" gave occassional messages such as:

"Unable to fetch file, server said 'Failed to open file. ' [IP: 128.101.240.212 21]"

So, if I upgraded to 6.0, does either of you think doing so could help resolve my: a) repo issue and b) public key issue? Would upgrading to 6.0 help my VMware efforts?

MBA Whore, I don't know that upgrading to 6.0 would necessarily "solve" your current repository problems. Probably the only way that you could test that would be to swap in a new drive and try an install to it. You can't test by using the 6.0 Live CD, because you cannot install software with it

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless