Earlier today, we migrated to a shiny new stack on shiny new servers. As part of this, we're also migrating the repository services, which will remain offline for a little while longer.
Not to worry, your repositories are safe and sound, we're just doing the repository server move out of band of the main migration.
I'll update this post once repository services are back online.
Update: Repo services have been restored.
Repo is down again :( http://www.downforeveryoneorjustme.com/repo.bukkit.org
The packer seems to be not working at all. So i had to update my addon by using the Update Wizard.
Are there any issues with pushing/cloning git repos? I'm not able to push or clone my project.
I still have problems with the packager:IOError: [Errno 2] No such file or directory: '/media/cf-repositories/packager/zip/rom/dailynotes-v6.0.2.1.zip'
thx..working again
@oscarucb: Go
Server move has been in the works for months. We can't plan around patches we don't know about.
The packager is running again.
Really need the packager fixed ASAP...
And would like to make the obvious observation that deciding to change server hardware the week after a major content patch (ie probably the highest-volume week of the year) was spectacularly POOR planning...
I'm having the same issue with the packager as well. It's not detecting my commits. I submitted a ticket.
Another catastrophe adverted
I just uploaded a new revision for KBM and nothing appeared for the packager (r747). It is a release version too which sucks :(
@tiker: Go
Same here, packager status also says "no data available" so information about the last package processes (before the migration) are gone?
@dandraffbal: Go
@oilidhun: Go
UPDATE: i can upload now
Is the packager broken as well? I uploaded some changes via svn but the packager hasn't built the new download yet.
I get the same error when I try to upload files.
@dandraffbal: Go
i get the same error every time
I still can't upload a new version of my addon :(
Fails with message: "There was an error uploading your file, please try again." (Tried with FF 24.0, Chrome 29.0, and IE 10)