Then I suppose you caught the right person at the right time in IRC - I certainly cannot fix the repos (nor do I have the access). I do know that those who have the ability have been informed of the issue and that yours is not the only affected project. I'll bring it up again.
As for Curse "cutting the funding"; there are a number of subsystems to CurseForge/WoWAce. Some have higher priority than others, and some are currently actively being worked on - stopping work mid-stride isn't something that many would recommend.
One other thing I should mention -- not sure if I have already -- but LCD4WoW changes/tags aren't being reported to #wowace. Not sure if this is related to the packager issue or not. I made sure it's set to report at any rate.
I changed it back to use wowace repo. It was still using the wowace repo technically, but it showed it was pointing to github. StarTip is the same way. I could never get the external repo feature working on either project.
Edit: But Repo has been reporting commits for StarTip. hmm
I have to apologize for how I acted in this thread. It appears not many people have the level of access required to fix projects in this state, as Torhal himself said. Odd that the root cause can't be fixed though.
Somehow I can't get my addon to package.
I commit the changes as usual, tag repo, and nothing happens.
I tried tagging it again and again, changed repo type to alpha/beta/release, nothing works. Packager status isn't showing anything either. Is the packager offline or something?
@Iroared:
Please search for existing threads about an issue before creating a new one. I've merged your thread with the other one that was already posted.
Discovered svn repository: wow/battlegroundtargets/mainline
Joining all threads
Updating svn://svn.wowace.com/wow/battlegroundtargets/mainline/trunk in /media/repositories/packaging/svn-local-checkout/wow/battlegroundtargets/mainline...
Done with svn://svn.wowace.com/wow/battlegroundtargets/mainline/trunk
Finished joining all threads
Creating zip /media/repositories/packaging/zip/wow/BattlegroundTargets-r27.zip... Done
Unsuccessful attempt at uploading /media/repositories/packaging/zip/wow/BattlegroundTargets-r27.zip. 403 FORBIDDEN:
Form invalid: {'nolib_file_id': [u'Invalid input.']}
Packager finished: 2011-08-20T01:05:21.621612.
Completed in 0:00:01.049860
please help, thanks
EDIT:
another checkout and commit works fine. anyway, some server admin should take a look at above error...
I'm having similar problems with my DArcBinds project. I have what I believe is a correct .pkgmeta file inside my github repo, but what I'm getting out isn't what I understand should be coming out.
I have 3 associated directories, 2 of which are inside the main DArcBinds folder, and they're not getting moved via my .pkgmeta directive. I've found other examples of a .pkgmeta in action, but this is most probably a PEBKAC.
I tagged the repo for my addon, LibDataBroker-1.0 hours ago, and it isn't getting packaged. Having check the packager, it appears to be working, as it is getting Minecraft updates, and some other stuff.
Something afoot at the Circle K?
Also, to those who program Curseforge, Rift supports English, German, French, Korean, and Russian. The Translation tab only shows English.
So I got SVN working, uploaded my files and it built the .zip files showing that everything works. Now I have since then updated several files, but it has not created any more new packages. Is there something I need to do to force it to build r3?
Sounds like you are suffering the same issues I am. The packager is having issues right now. And like me, we should continue talking in the other thread. Phanx will go easier on you because you are new; I should have known better LOL.
@mgaiser: I put your project into the packager queue - you have a new file. There was an issue today that stopped everything from packaging which has since been fixed.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
As for Curse "cutting the funding"; there are a number of subsystems to CurseForge/WoWAce. Some have higher priority than others, and some are currently actively being worked on - stopping work mid-stride isn't something that many would recommend.
One other thing I should mention -- not sure if I have already -- but LCD4WoW changes/tags aren't being reported to #wowace. Not sure if this is related to the packager issue or not. I made sure it's set to report at any rate.
Edit: But Repo has been reporting commits for StarTip. hmm
I commit the changes as usual, tag repo, and nothing happens.
I tried tagging it again and again, changed repo type to alpha/beta/release, nothing works. Packager status isn't showing anything either. Is the packager offline or something?
http://www.wowace.com/packager/
Please search for existing threads about an issue before creating a new one. I've merged your thread with the other one that was already posted.
please help, thanks
EDIT:
another checkout and commit works fine. anyway, some server admin should take a look at above error...
I have 3 associated directories, 2 of which are inside the main DArcBinds folder, and they're not getting moved via my .pkgmeta directive. I've found other examples of a .pkgmeta in action, but this is most probably a PEBKAC.
Something afoot at the Circle K?
Also, to those who program Curseforge, Rift supports English, German, French, Korean, and Russian. The Translation tab only shows English.