Trouble using apt-get

Lately attempts to use apt-get have been going awry, like so:

bob@raspberrypi:~ $ sudo apt-get clean bob@raspberrypi:~ $ sudo apt-get update Get:1

formatting link
stretch InRelease [15.0 kB] Hit:2
formatting link
stretch InRelease Get:3
formatting link
stretch/main armhf Packages [11.7 MB] Err:3
formatting link
stretch/main armhf Packages Hash Sum mismatch Hashes of expected file: - Filesize:11662628 [weak] - SHA256:203e317bfde8cbbcb7677160459573bcb0f1a60dc07fec7b9c4faab3c1a8494e - SHA1:25d446506d592a3207e8917177a3e8d8849b81a8 [weak] - MD5Sum:4fb63b0668099b0752c75d45f18fedc6 [weak] Hashes of received file: - SHA256:6d332bfac22e51d07bb18d8e664c6ee5d85868321738d123bc7a0fb9898156c9 - SHA1:79f7cdbc6ee28d91472d330f7629136fed235fa0 [weak] - MD5Sum:884352f5fbcfed64a47b7611b11af246 [weak] - Filesize:6799545 [weak] Last modification reported: Mon, 24 Jun 2019 04:30:23 +0000 Release file created at: Mon, 24 Jun 2019 16:28:10 +0000 Fetched 6,815 kB in 1min 8s (98.9 kB/s) Reading package lists... Done E: Failed to fetch
formatting link
Hash Sum mismatch Hashes of expected file: - Filesize:11662628 [weak] - SHA256:203e317bfde8cbbcb7677160459573bcb0f1a60dc07fec7b9c4faab3c1a8494e - SHA1:25d446506d592a3207e8917177a3e8d8849b81a8 [weak] - MD5Sum:4fb63b0668099b0752c75d45f18fedc6 [weak] Hashes of received file: - SHA256:6d332bfac22e51d07bb18d8e664c6ee5d85868321738d123bc7a0fb9898156c9 - SHA1:79f7cdbc6ee28d91472d330f7629136fed235fa0 [weak] - MD5Sum:884352f5fbcfed64a47b7611b11af246 [weak] - Filesize:6799545 [weak] Last modification reported: Mon, 24 Jun 2019 04:30:23 +0000 Release file created at: Mon, 24 Jun 2019 16:28:10 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead.

Anybody got a workaround? This has persisted for several days.

Thanks for reading,

Reply to
bob prohaska
Loading thread data ...

Huh! I was just going to post about my own problem, which is slightly different, but I wonder if the cause is not what I thought?

My Pi is an old one that's using Wheezy. As it does the job perfectly for me, I have no reason to update. Except...

I happened to want to use tcpdump, but find it isn't there. So I went to apt-get it, but that failed, suggesting an 'apt-get update'. Did that, and *everything* was 404! Do they really not keep archives for more that four years, or is something else going on?

I thought, Oh well, I'll just compile the thing from source... But tcpdump requires libpcap, which requires flex, which requires libtoolize... At that point I gave up, as I can't install anything.

Are my expectations too high? (:-/)

-- Pete --

Reply to
Pete

I'm not a Raspbian user, but the first post includes reference to:

formatting link
and browsing that in a web browser finds a "dists/wheezy" directory.

I suggest adding that to /etc/apt/sources.list, if it's not already there.

Yeah, I've done a fair bit of that. It does wear a bit when you get so far along the dependency trail just to find one that refuses to compile.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

On Sun, 7 Jul 2019 00:00:03 +0000 (UTC), snipped-for-privacy@GoodeveCa.net (Pete) declaimed the following:

Ancient...

Buster is due out (well, the R-Pi 4 is using a pre-release "testing" image as Stretch won't work on it), and even Jessie is being phased out.

I suspect it isn't time -- but versions... Wheezy is FOUR generations old in relation to Buster. That makes it the "WinXP" in relation to "Win10".

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

o/~ talking to myself in public o/~

On Sun, 07 Jul 2019 11:40:54 -0400, Dennis Lee Bieber declaimed the following:

Actually, it IS out... as of yesterday.

formatting link
So expect a newer Raspbian/NOOBS image in a few days, configured for the "stable" release.

Well, might also be time -- from the linked announcement Buster "...will be supported for the next 5 years...", so Wheezy could easily have fallen out of the support range... Confirmed on

formatting link

Wheezy support expired May of LAST year. Jessie is in "long term support" until June of next year, Stretch will be go into LTS next year until summer of 2022. LTS appears to be a volunteer team, and not formal Debian security patches.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

It's a separate project certainly, to what extent it is more "volunteer" than the rest of the package administration I'm not sure. I don't know if LTS Debian packages ever make it as far as the Raspbian respository either.

As far as the security patches themselves go, they're simply builds of patches released by the developers of each program, so they're just as formal as the packages for the stable distro. The issue is that some programs may not receive the patches as quickly or as regularly as they do for mainstream supported distro versions.

But poster is not trying to deal with security updates, just install a package that was available originally, and presumably he's happy with a slightly outdated version. The secuirty implications of that are another matter, and depend of what he's doing with the Pi.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

Yuck, basically... I'm not used to systems 'expiring' (not being a Windows user...). I'm still making heavy use of my 20+ years old BeOS machine; slow, but perectly adequate for email, usenet (:-/), and much of browsing. And I consider 'support' to be a bit different from keeping an archive around. My Pi, similarly, is perfectly good for what it's currently used for -- mostly a 'reminder server' for my other machines and playing audio streams.

I expect I'll get a Pi4 pretty soon, and of course will put Buster on that, but it won't obsolete the other board.

Exactly. It's behind a firewall, with the only port exposed being a private one for the reminder service (so I can access it from the coffee shop!). I tried opening port 80 for a while, but got fed up with all the malevolent probes.

-- Pete --

Reply to
Pete

Thanks, but digging into that seems to show that it's only raspbian itself. No other packages.

The format of the list is a bit different. Not sure how it works:

deb

formatting link
wheezy main contrib non-free rpi deb-src
formatting link
wheezy main contrib non-free rpi

Maybe I'll dig around a bit. See if I can find anything.

-- Pete --

Reply to
Pete

Well, maybe I'll forgive 'em... (:-/) I should always remember to wander the web a bit before complaining too hard. I did a search for "raspberrypi wheezy repo", and it threw up a forum discussion sparked by somebody with just the same problem. The answer is to replace the url above with:

formatting link

I just put that in both the above lines (not sure if I should have changed the 'deb-src' line -- maybe they are still appropriate?), and I was able to install my package. (After remembering to also do "apt-get update"!)

Thanks, all.

-- Pete --

Reply to
Pete

On Mon, 8 Jul 2019 01:25:59 +0000 (UTC), snipped-for-privacy@GOODEVEca.net (Pete) declaimed the following:

I suspect mine is getting bogged down by such too... But having lost the 10MB (per email address) static web space from Earthlink (I'm paying to keep the email addresses alive, but no longer have the web space for scratch files), I set up a dynamic DNS account and set up an nginx server on a Pi3B (now if I could figure out how to keep it from creating status files for the DDNS update calls, to reduce wear on the SD card; I can't justify running a TB hard drive just for log files).

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

The packages are in the "pool" directory. The package manager gets the package lists from within the "dists/wheezy" directory, then uses that to locate compatible packages within "pool/".

I'm guessing they're Raspbian specific packages, while the other archive link is for Debian packages that are compatible with Rasbian. If so, then you'd want both in /etc/sources.list

Yes, put it in the deb-src part as well. I'm not sure what the format is for the Debian archive in /etc/sources.list. There's "main", "staging", and "untested". If I assume that this is about testing Debian packages to see whether they break under Raspbian, perhaps use: deb

formatting link
wheezy main deb-src
formatting link
wheezy main

But as I say, I'm not a Rasbian user and am just guessing based on my knowledge of Debian. Anyway you've got the package you wanted, so maybe it doesn't matter until the next time you want to install a new program.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

Mmm.. I don't think so. I looked there too -- and everywhere else I coukld think of -- and didn't see anything but core stuff.

Yeah, I was being silly. As the deb-src line also contains "wheezy", it must be specific.

Anyway, all good now.

Thanks,

-- Pete --

Reply to
Pete

I've made sure I have a static IP just because I thought I might want to have a local web server, but it never actually has seemed worth it. Maybe I'm fortunate in having a local friendly ISP, that gives me web space for a very reasonable price. The static IP makes the above-mentioned coffee-shop access simple, though.

Cheers,

-- Pete --

Reply to
Pete

It looks like it's a small sub-set of what's really available for Debian, but there are packages for Chromium in there, for example:

formatting link

I think the idea is that you use the Debian packages in combination with the Raspbian packages, and the former probably provide some of the required dependencies for the latter.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

On Tue, 9 Jul 2019 20:05:40 +0000 (UTC), snipped-for-privacy@GOODEVEca.net (Pete) declaimed the following:

Well... the dynamic DNS isn't too much of a hassle -- other than the fact that U-verse routers don't include software to update the DDNS system (unlike my older DSL routers which included configuration pages for dynamic DNS service). As a result, I have to run a CRON job to periodically pester the DDNS so it can link my router IP to the domain name. And that leaves a residue file on each update -- so I have another CRON job that deletes the residue files when they are something like two days old. I tried configuring the CRON job to direct stdout/stderr to the bit-bucket but doesn't seem to take or the residue file is not stdout/stderr of the task itself.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

You could configure it to keep the file on a ramdisk.

--
__          __ 
#_ < |\| |< _#
Reply to
Computer Nerd Kev

On Thu, 11 Jul 2019 00:09:28 +0000 (UTC), snipped-for-privacy@telling.you.invalid (Computer Nerd Kev) declaimed the following:

If I could figure out how to redirect them, the bit-bucket would be enough... Otherwise I'd have to put my home directory itself into RAM.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

The problem seemed to go away some days ago, but it has returned so I tried using aptitude.

Using apt-get it appeared the files were coming from a mirror at UC Berkeley. Using aptitude the files are coming from raspberrypi.org, so it's not a mirror problem. Aptitude still reports hash sum mismatches. Copy from the aptitude terminal window doesn't work, so it isn't easy to quote an example, but the text looks roughly similar with different sums and filesizes.

The only other quirk is that the download starts fast, tens of kB/sec, and slows to ones or twos of kB/sec. Speedof.me reports 5 MB/s down, 1 MB/s up, so the connection isn't the issue.

Thanks for reading, any ideas appreciated.

bob prohaska

Reply to
bob prohaska

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.