Git moonbase needs a fresh clone
ratler at lunar-linux.org
Fri Dec 4 09:06:38 CET 2009
Hey fellow developers,
I have now revoked everyones commit access until you can verify that you
have a clean moonbase, first then I will re-add your commit access.
We have managed to push out the bad changes a couple of times more since
we fixed the issue. I'm sorry for any inconvenience but this may cause
but right now it seem to be the best solution.
Lunar Linux developer - PGP public key 6E810F05
On Thu, 2009-12-03 at 15:23 -0600, Terry Chan wrote:
> To all lunar devs with git push rights on doppio.
> Due to a recent problem on doppio, you MUST get a NEW copy of the git moonbase
> git clone git://lunar-linux.org/lunar/moonbase.git
> I had to fix the problem on doppio with this command:
> git update-refs HEAD 1ed9c2debf5361b9b26b03d611a4cdb45cb5f0ed
> If you fail to clone a new moonbase your current git moonbase will be in an
> incorrect state if you have ANY of the elangelo changes in your repo from the
> last few days.
> Things to search for are "lvu DETAILS xfce4-panel" and the version number should
> be 4.6.1, not git- something or other.
> Also you should NOT have a copy of zbeta/mplayer in your repo.
> If you have either of those two cases then your repo is messed up and git pull
> will not correctly fix your repo. You MUST do a fresh git clone and get a brand
> spankin' new moonbase git repo for yourself.
> Terry Chan
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the Lunar