Bug #5479
closedAppend our built packages with some sort of inktank/ceph identifier
0%
Description
Seems like our packages should have something appended to them so we know they are the inktank/ceph ones. I ran into an issue today trying to get ceph-qa-chef updated to install the new fastcgi packages and the problem was they were the same exact versions as the centos ones so they were getting installed from the epel repo instead of our modified ones from our local repo.
I was able to work around it by installing a yum's repo priority tool and setting ours to a higher priority but in general I think we would want an identifier to not have this type of problem.
I guess the question is if other things being equal except the version being appended with some text does it make it a higher or lower version.
Updated by Anonymous almost 11 years ago
- Status changed from New to In Progress
We're doing a bunch of backports now, do you think the ceph tag is needed on unmodified packages ?
Updated by Sandon Van Ness almost 11 years ago
Well if the modified/backported version needs to be utilized for ceph stuff. I think the point is so when someone adds our repo they can just do yum install 'package' without specifying a version so the ceph one needs to be the highest version so it uses ours instead of the primary repo one which it will do if the names/versions are identical.
I guess a workaround with this is in our documentation if we tell people to install repopriority and have our repo set at a higher priority then that would probably work too. That is basically how I am working around this right now in ceph-qa-chef.
I guess Ian C. would be the one to make the call on this.
Updated by Ian Colle about 10 years ago
- Status changed from In Progress to 12
- Assignee deleted (
Anonymous)