The packages were probably rebuilt without changing their name/version (bad idea btw) and metadata either weren’t regenerated because of that or because of some other problem. You can mirror it and generate your own metadata or install the packages by hand until it gets fixed. Jan P.S.In my experience it’s best to always put a build number in the filename to avoid stuff like this, unless you can make sure you generate the same binary package every time (And that’s pretty hard usually). > On 23 Jul 2015, at 15:14, Samuel Taylor Liston <sam.liston@xxxxxxxx> wrote: > > I am having the same issue and haven't figured out a resolution yet. The repo is pointing to a valid URL, and I can whet the packages from that URL, but yum complains about them. My initial thought is that something is screwy with the md5sum either on package versions in the repo, or in my rpm db, but I have not confirmed that. > > Samuel T. Liston > ================ > Ctr. for High Perf. Computing > Univ. of Utah > 801.232.6932 > ================ > >> On Jul 23, 2015, at 7:05 AM, Wayne Betts <wbetts@xxxxxxx> wrote: >> >> I'm trying to use the ceph el6 yum repo. Yesterday afternoon, I found yum complain about 8 packages when trying to install or update ceph, such as this: >> >> (4/46): ceph-0.94.2-0.el6.x86_64.rpm | 21 MB 00:01 >> http://ceph.com/rpm-hammer/el6/x86_64/ceph-0.94.2-0.el6.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=Ceph clean metadata >> >> >> The other packages with the same fault are >> >> libcephfs1-0.94.2-0.el6.x86_64 >> librbd1-0.94.2-0.el6.x86_64 >> python-rados-0.94.2-0.el6.x86_64 >> python-cephfs-0.94.2-0.el6.x86_64 >> librados2-0.94.2-0.el6.x86_64 >> python-rbd-0.94.2-0.el6.x86_64 >> ceph-common-0.94.2-0.el6.x86_64 >> >> >> This is happening on all three machines I've tried it on. I've tried cleaning the metadata on my hosts as per the suggestion, without any change. >> >> There was no trouble pulling these packages with yum on Tuesday, July 14, and I can still use wget to pull individual packages seemingly without any problem. >> >> Is anyone else experiencing the same problem? Can the repo maintainers look into this? (Rebuild the metadata, or flush their reverse proxy server(s) if any?) >> >> Any suggestions for me to try on the client side? >> >> -- >> -Wayne Betts >> STAR Computing Support at BNL >> >> Physics Dept. >> PO Box 5000 >> Upton, NY 11973 >> >> wbetts@xxxxxxx >> 631-344-3285 >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |