On 25 September 2014 08:14, Gunnar Zötl <g...@tset.de> wrote: > > >> Hisham <h...@hisham.hm> hat am 24. September 2014 um 15:07 geschrieben: >> On 24 September 2014 04:27, Gunnar Zötl <g...@tset.de> wrote: >> > Hmmm... weird. I had 2.1.2 installed manually, which has this "issue", and >> > then >> > installed luarocks 2.2.0 via luarocks. Strangely enough, luarocks is still >> > at >> > 2.1.2 on my system. I will need to investigate this... oh well. >> >> Perhaps 2.1.2 is in /usr/local and 2.2.0 ended up in ~/.luarocks? > > Nope, that's not it. I removed it from luarocks and reinstalled it with the > still present luarocks, and not it's at 2.2.0. However, because of the > previously installed older version, there are now a lot of files ending in ~ > about.
Ah, I think 2.2.0 misreports its own version number, sorry about that. > If I install 2.2.0 manually, will it register itself with luarocks so > that this does not happen? Yes if you install with `make bootstrap`. -- Hisham ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
