Ask Your Question
0

libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: checksum error

asked 2015-07-21 22:51:25 -0500

RL gravatar image

As of today:

dnf update: ... [MIRROR] libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: Downloading successful, but checksum doesn't match. Calculated: 951b005d1465c6965ba2d34a0039026404f419e259cc29185019604027b3315f(sha256) Expected: a045fb4d89ec85c9d568d70b18587b102ae7a3a7ef639741ce01f6788437fbe5(sha256) [FAILED] libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: No more mirrors to try - All mirrors were already tried without success Error: Error downloading packages: Cannot download drpms/libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: All mirrors were tried

Something's wrong in the repository! R.

edit retag flag offensive close merge delete

Comments

I had a similar error, but couldn't download:

[MIRROR] libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: Curl error (78): Remote file not found for ftp://mirror.cedia.org.ec/fedora/updates/22/x86_64/drpms/libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm [RETR response: 550] [MIRROR] libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm: Status code: 404 for http://mirror.cedia.org.ec/fedora/upd... [FAILED] libinput-0.19.0-2.fc22_0.19.0-3.fc22.x86_64.drpm

yuriploc gravatar imageyuriploc ( 2015-07-22 15:43:29 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2015-07-21 23:23:33 -0500

It means you had a network error, and your file is incomplete or corrupt. dnf tried to download the file from a different mirror but gave up. You have a bad connection that needs to be resolved. When you run dnf again, it will try the mirrors again - once you have better network connectivity things should just work.

If you can run dnf without a network issue, and you still get this error, do a "dnf clean cache" and try your update/install again.

edit flag offensive delete link more

Comments

Hmm, your answer puzzles me. The dnf message says:

"Downloading successful, but checksum doesn't match."

If (according to your answer) dnf reports a successful download, when in fact it was not, then that indicates a bug in dnf file management vs download failures..... However, I rather think that there was a temporary mistake in the repository, which seems to have been fixed by now. -R.

RL gravatar imageRL ( 2015-07-22 23:34:43 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2015-07-21 22:51:25 -0500

Seen: 221 times

Last updated: Jul 21 '15