Packages vim-common vim-tiny xxd not found
Closed, ResolvedPublic

Description

This morning

bash
sudo apt update
sudo apt upgrade

failed with:

txt
Err:1 https://repo.puri.sm/pureos green/main amd64 xxd amd64 2:8.1.0875-4
  404  Not Found [IP: 138.201.228.45 443]
Err:2 https://repo.puri.sm/pureos green/main amd64 vim-common all 2:8.1.0875-4
  404  Not Found [IP: 138.201.228.45 443]
Err:3 https://repo.puri.sm/pureos green/main amd64 vim-tiny amd64 2:8.1.0875-4
  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/v/vim/xxd_8.1.0875-4_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/v/vim/vim-common_8.1.0875-4_all.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/v/vim/vim-tiny_8.1.0875-4_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

After more careful investigation I noticed that the packages had a version mismatch.

The following versions are available on repo.puri.sm

Available: https://repo.puri.sm/pureos/pool/main/v/vim/vim-common_8.1.0875-5_all.deb
Database:  https://repo.puri.sm/pureos/pool/main/v/vim/vim-common_8.1.0875-4_all.deb

Available: https://repo.puri.sm/pureos/pool/main/v/vim/vim-tiny_8.1.0875-5_amd64.deb
Database:  https://repo.puri.sm/pureos/pool/main/v/vim/vim-tiny_8.1.0875-4_amd64.deb

Available: https://repo.puri.sm/pureos/pool/main/v/vim/xxd_8.1.0875-5_amd64.deb
Database:  https://repo.puri.sm/pureos/pool/main/v/vim/xxd_8.1.0875-4_amd64.deb
itay-grudev edited the task description. (Show Details)
itay-grudev edited the task description. (Show Details)
itay-grudev edited the task description. (Show Details)
jonas.smedegaard closed this task as "Resolved".Mon, Jun 24, 2:16 PM
jonas.smedegaard claimed this task.
jonas.smedegaard added a subscriber: jonas.smedegaard.

Thanks for reporting.

Seems you simply did the apt update just before the vim package got updated in the archive.

In other words I suspect the final remark in the error message would have helped - together with a bit of patience.

Closing this as a non-bug. Please don't let that discourage you: Your continued reporting issues is highly appreciated, and even when "closed" you can still contribute followup remarks to this issue, e.g. if you experience same issue again and suspect something else is really going on here.

Add Comment