Also seems to be failing on PhanxBuffs. It did at least run the packager and produce a status log but it doesn't seem to be able to see the tag, since it says:
Skipping zip for wow/phanxbuffs/mainline, it has a new alpha build but is set to package Beta and Release.
Another addon I tagged earlier was packaged correctly right away, so I don't really know what the problem is.
I slapped 'em both back into the queue and PhanxChat packaged, but PhanxBuffs did not. No idea why, either, since the damn packager log isn't displaying...
I deleted the tag on Curse for PhanxBuffs, and re-pushed the repo with tags again, and it actually packaged it... though Git also reported the previous tag was new too, despite it definitely already existing on Curse since it was packaged when it was created in December... who knows!
The svn repository packager is not working. Please fix, Thanks.
I need to know which project didn't package, so I can re-queue it.
The issue isn't "the packager for this particular type of version control is broken," it's "the packager was never made aware that this particular project needs to be packaged."
Not exactly a packager problem, but I have an uploaded ZIP file on CurseForge for Ovale that was approved four hours ago, but the new release information has not propagated to Curse.com yet. Is there something else I need to do to get that working again?
After setting up the repository on curseforge for http://wow.curseforge.com/addons/doom-shards/ the packager only packaged three or four tags + one alpha build once yesterday after some fiddling. Tags pushed after that aren't processed (no further activity under Packager Status).
Honestly at this point the packager is so slow and fucks up so often I feel I'd be better off just creating and uploading ZIPs by hand...
Another addon I tagged earlier was packaged correctly right away, so I don't really know what the problem is.
-
View User Profile
-
View Posts
-
Send Message
Project Authorhttp://wow.curseforge.com/addons/opie-masque/
Tag was created and pushed on 2/25 (last Wednesday) but there's still no file, and the packager log reports no activity since January.
-
View User Profile
-
View Posts
-
Send Message
Project Author-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Project AuthorYou have a new zip file!
-
View User Profile
-
View Posts
-
Send Message
Project AuthorI need to know which project didn't package, so I can re-queue it.
The issue isn't "the packager for this particular type of version control is broken," it's "the packager was never made aware that this particular project needs to be packaged."
I made a tag that didn't make it. Queued it before that last alpha got packaged (but after I queued that), in case that matters!
-
View User Profile
-
View Posts
-
Send Message
Project AuthorApparently the tag never made it to the server: I re-queued, and got this...
http://wow.curseforge.com/addons/conspicuous-spirits/repositories/mainline/packager/
No package for the latest tag (6.2.0.25) and "no data available" on the log page.
-
View User Profile
-
View Posts
-
Send Message
Project Author-
View User Profile
-
View Posts
-
Send Message
Project AuthorThanks for your time.
-
View User Profile
-
View Posts
-
Send Message
Project AuthorI've pointed someone to this thread who may be able to figure things out. Can't give an ETA, unfortunately.