-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EL7 kmod repo metadata not updated #4327
Comments
Looks like the machinery had a hiccup, I've refreshed it and it's providing 0.6.54 now. Thank you for reporting this. |
Hi, We mirror the kmod repo but it doesn't seem to contain the last 0.6.5.5 release of today. Or is it just me being impatient to get my hands on the the fresh RPMs ? Thank you for your help. |
@herver it looks like the repodata didn't get updated, I manually refreshed it and everything looks good now. |
Thanks 👍 |
@herver refreshed the 3l6 kmod repo. |
Hi there, The metadata for the kmod repo for el6/7 are still lagging behind, the RPMs are there for 0.6.5.7 but the repodata didn't get updated (which causes mirror creation to skip these). Could you please have a look ? (and possibly automated it as for the normal repo ?) |
I noticed that this time the kmod RPMs haven't been built for 0.6.5.8. They don't show up here: http://archive.zfsonlinux.org/?prefix=epel/7/kmod/x86_64/zfs-0.6.5 nor in the metadata. If you need a hand to get this working (or builders), please let me know ! |
@herver a month or so back the EPEL and Fedora repositories were migrated from http://archive.zfsonlinux.org to http://download.zfsonlinux.org. An updated zfs-release package was published in the archive repo but it wouldn't have overwritten your As of today the main zfs repository contains packages for 0.6.5.8 and the zfs-testing repository contains the 0.7.0-rc2 release candidate. |
Hello there,
I'm using the kmod repo that @behlendorf mentioned here but it seems like although zfs-0.6.5.4 RPMs are there the metadata of the repo are stuck with the previous 0.6.5.3.
Would you mind refreshing these ?
The text was updated successfully, but these errors were encountered: