| Summary: | Upgrading to >=dev-vcs/gitolite-3* breaks gitolite | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Enno Gröper <enno+gentoo> |
| Component: | Current packages | Assignee: | Christian Ruppert (idl0r) <idl0r> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
The warning will now be shown correctly when upgrading from 2.x. Also: *ANY* user should read the ChangeLog or NEWS or whatever else when doing major upgrades. The message warns the user and also show a link that points to the upgrade guide. |
Upgrading to =dev-vcs/gitolite-3.04 left my gitolite unusable. There was no warning about this prior or after installing the new version. Perhaps, because 'has_version "=dev-vcs/gitolite-2*"' does never work in _postinst_ (after merging the new version)? Reproducible: Always Steps to Reproduce: 1. emerge -uvD world 2. 3. Actual Results: Only the notice about checking the correct homedir is shown. Gitolite is in an unusable state. Expected Results: Upgrade hints (specific to what was already done by the ebuild, see below) or at least a warning, that gitolite doesn't work anymore. I would prefer a warning prior to installing. My messages after upgrading retrieved from portage log: >>> Messages generated by process 16668 on 2012-09-16 19:15:16 CEST for package dev-vcs/gitolite-3.04: WARN: postinst LOG: postinst Please make sure that your 'git' user has the correct homedir (/var/lib/gitolite). Especially if you're migrating from gitosis. WARN: postinst ----------- My steps to upgrade: USE="tools" emerge -1av gitolite su - git check-g2-compat # showed no problems mv .gitolite.rc old.grc git clone repositories/gitolite-admin.git old.ga rm -rf repositories/gitolite-admin.git/ mv .gitolite .gitolite.old # preserving hooks and logs gitolite setup -a admin cd old.ga/ gitolite push -f -------- To get "check-g2-compat" script you have to reemerge gitolite with tools USE-flag. Using the gitolite upgrade guide, I could omit the code substep of step 1 and obviously the complete step 2 (installing g3)