-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Upgrade from CE to EE doesn't work without manual work #82
Comments
|
Thanks for your suggestion. I don't have a CentOS/RHEL system near me right now, so I would appreciate help here from someone who is able to test the change and create a PR. |
|
I'll take a look at this and get a PR going this week. |
|
@dhollinger Did you have a chance to create a PR? |
|
@tobru Crap, sorry. I have not, ended up not having the time. I can try taking a look at it this week, if I don't have time (or if you already have something ready), I'll step away. Don't want to be the holdup to fixing this any longer. Sorry again! |
Added separate repo configs for Enterprise vs Community versions of Gitlab. This is to prevent conflicts between the repo names and allow for automated upgrades from CE to EE.
At least on RHEL, as you use a single
yumreporesource with the same name for 2 different repos, when upgrading from CE to EE edition the Yum repo is not being updated and upgrade does not happen until you manually remove the old repo and do ayum clean.I think it would be enough to add edition to
yumreporesource name but unfortunately I don't have time to create a PR right now, sorry.The text was updated successfully, but these errors were encountered: