MongoDB | 297951

Info

This issue is likely related to SERVER-18516. The issue occurs when I try to mirror your repo using debmirror with the following command: debmirror -v --diff=none --method=http --rsync-extra=none -h repo.mongodb.org -r /apt/ubuntu -d trusty/mongodb-org/3.0 -s multiverse --no-check-gpg /data/html/apt/common-mongodb This results in the following 404 error: Warning: --rsync-extra is not configured to mirror the trace files. This configuration is not recommended. Mirroring to /data/html/apt/common-mongodb from http://repo.mongodb.org/apt/ubuntu/ Arches: i386 Dists: trusty/mongodb-org/3.0 Sections: multiverse Including source. Pdiff mode: none Not checking Release gpg signatures. Will clean up after mirroring. Attempting to get lock ... Getting meta files ... [ 0%] Getting: dists/trusty/mongodb-org/3.0/Release... ok [ 0%] Getting: dists/trusty/mongodb-org/3.0/InRelease... failed 404 Not Found [ 0%] Getting: dists/trusty/mongodb-org/3.0/Release.gpg... ok Missing: .temp/dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages.gz [ 99%] Getting: dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages.gz... failed 404 Not Found Missing: .temp/dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages [ 99%] Getting: dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages... failed 404 Not Found Errors: Download of dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages.gz failed: 404 Not Found dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages.gz failed checksum verification Download of dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages failed: 404 Not Found dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages failed checksum verification Failed to download some Package, Sources or Release files! WARNING: releasing 1 pending lock.. It looks like the debmirror application is trying to use the following path which doesn't exist (note the duplicate of mongodb-org/mongodb-org): dists/trusty/mongodb-org/mongodb-org/3.0/multiverse/binary-i386/Packages.gz I'm guessing it is pulling this incorrect path from one of the release file it pulls but have yet to pin point this down any further. I will continue to look at my side but would greatly appreciate if you folks could check if this issue is being created at your end? Thanks!

Top User Comments

ernie.hershey@10gen.com commented on Tue, 5 Jul 2016 22:37:39 +0000: I think there's something subtly wrong either in our Release file contents or in the logic in the debmirror script. It's attaching the 'codename' from the Release file to the distribution passed on the command line, both of which contain 'mongodb-org' and lead to the incorrect URL path. As a workaround, here's a debmirror command line that works, by bypassing our Releases file. I also specify an architecture with packages, and not to download sources, which we don't provide .debs or repo metadata for. debmirror --ignore-missing-release --arch amd64 --nosource -v --diff=none --method=http --rsync-extra=none -h repo.mongodb.org -r /apt/ubuntu -d trusty/mongodb-org -s 3.0/multiverse --no-check-gpg /data/html/apt/common-mongodb An initial test with the original debmirror invocation from the ticket description works if I change the codename in the Release file from "trusty/mongodb-org" to "trusty" works. The fix may be as simple as that.

Steps to Reproduce