[SERVER-20087] Debian repository broken - Hash Sum mismatch Created: 21/Aug/15  Updated: 04/Sep/15  Resolved: 22/Aug/15

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Josip Sokcevic Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20095 Redhat repository broken - Metadata f... Closed
Operating System: ALL
Participants:

 Description   

Don't think this is the right project, but best I could find.

Doing apt-get update currently reports:

W: Failed to fetch gzip:/var/lib/apt/lists/partial/repo.mongodb.org_apt_ubuntu_dists_trusty_mongodb-org_3.0_multiverse_binary-amd64_Packages Hash Sum mismatch

sources.list:
deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.0 multiverse

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

Let me know if you need more information



 Comments   
Comment by Ernie Hershey [ 22/Aug/15 ]

Glad to hear it's fixed! Thanks for writing back.

Comment by Josip Sokcevic [ 22/Aug/15 ]

Hi Ernie, thanks for explanation.where should I post. The problem is fixed so gonna close the ticket. Thanks again

edit: looks like I don't have permissions for that so I'll let you handle it.

Comment by Ernie Hershey [ 22/Aug/15 ]

Hi josip@thebackplane.com - this is the right project for bug reports against MongoDB but I think this is more of an operational issue than a bug. Technically the best place to post a problem like this is the user mailing list on google groups - https://groups.google.com/forum/?#!forum/mongodb-user.

It looks like the problem was the result of timestamp mismatches in new repo metadata generation code causing old invalid files to persist despite new files being generated. I updated the repo metadata to the correct files. Can you try again and let me know if it works now?

Generated at Thu Feb 08 03:53:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.