[Urgent] Issues with legacy haxelib about haxelib HOT 4 CLOSED

Alright, I'm going to go through this in detail in the morning (I'll be anti-social and sitting in the back corner of the conference if I don't get it done before 10am).

Juraj if you're in Paris already it would be great to sit down with you and see where you got to with this - I believe you said you made some progress? Truth be told I haven't really looked into it yet to try and grasp what's happening.

It'll also be helpful if I can see what's going on on the actual server... so if someone with SSH/FTP/whatever access can help me out that would be appreciated.

from haxelib.

I'm on it right now. Unfortunately I lack the permissions :D

The reason this broke is that I tried putting the new uploads to files (instead of files/2.0) and move the old one to files/legacy' (instead offiles').

So on the server, I copied to files to the new location, but left the old ones there, "for the time being" or so I thought. Unfortunately, I never removed them, so we never became aware that this cannot work. And the problem surfaced only when more and more files got uploaded. So right now I am trying to get the permissions to move the stuff around and then I'm going to push a new haxelib_client update, that will also sit in files and files/3.0.

Btw, do you have an idea than files/3.0? Ideally, the file location would stay the same for a long time.

from haxelib.

Ah, that makes sense.

As for a better name than 3.0, I don't know... Is haxelib 4 likely to break
backward compatibility again? If not you can just do "new", but I thought
it would be better to have something meaningful if we ever do break
compatibility again (even if it's several versions from now,
"haxelib-new-new" is just wrong!) But if there's a better suggestion you
have until Nicolas' talk tomorrow morning to implement it :)

So is this likely to resolve all the various issues about downloads of new
libraries not working? Or is there more left to look at?

Jason

On Fri, May 24, 2013 at 7:38 AM, Juraj Kirchheim
[email protected]:

I'm on it right now. Unfortunately I lack the permissions :D

The reason this broke is that I tried putting the new uploads to files(instead of
files/2.0) and move the old one to files/legacy' (instead offiles').

So on the server, I copied to files to the new location, but left the old
ones there, "for the time being" or so I thought. Unfortunately, I never
removed them, so we never became aware that this cannot work. And the
problem surfaced only when more and more files got uploaded. So right now I
am trying to get the permissions to move the stuff around and then I'm
going to push a new haxelib_client update, that will also sit in filesand
files/3.0.

Btw, do you have an idea than files/3.0? Ideally, the file location would
stay the same for a long time.

—
Reply to this email directly or view it on GitHubhttps://github.com/back2dos/haxelib/issues/39#issuecomment-18387441
.

from haxelib.

It's been fixed directly on the website (requires 3.0 final haxelib client or selfupdate)

from haxelib.