Based on the packager log it seemed to be stuck trying to package an old tag (where I was attempting to get it to pull libraries from GitHub over SVN), so I deleted that tag and pushed to the Curse repo, but it seems completely oblivious and hasn't even tried to run again.
Well, it seems to have successfully made a package now (and back dated it!) but the packager status page is still showing nothing but error messages from an old failed run.
I'm 100% sure I just blew up the packager by accidentally pushing all of my tags in my Ovale repository instead of just the latest one. I have no idea how to fix this.
Currently, Curse.com believes the latest tag is 3.1.15 when it should be 6.0.38.
The packager is fine, its packaging all the things you give it to package.
Its doing exactly what you told it to do, is all. Although it sometimes gets confused when it has so many tags to process at once.
Once its done, just push another new tag on top, and at your own discretion delete the files you never wanted to have in the first place.
Just be careful what you push, the packager just works through whatever list you give it. Git isn't for everyone, apparently!
I did exactly this. The packager now incrementally thinks the latest release is 3.1.16, 3.1.17, 3.1.18, etc., every time I make and push a new tag. I don't really see how this has anything to do with Git, but I guess that's just me.
I guess I can "work around" this by tagging and pushing 250 betas until the packager catches up to the correct release tag. Just let me know if I should go this route.
http://wow.curseforge.com/addons/ouf-phanx/repositories/mainline/packager/
Based on the packager log it seemed to be stuck trying to package an old tag (where I was attempting to get it to pull libraries from GitHub over SVN), so I deleted that tag and pushed to the Curse repo, but it seems completely oblivious and hasn't even tried to run again.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premiumedit: Same error on http://www.wowace.com/packager/
-
View User Profile
-
View Posts
-
Send Message
AdminThis is still an issue. I tagged GridLayoutByRole 1.2 and the packager is ignoring my tag again.
-
View User Profile
-
View Posts
-
Send Message
Admin-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Admin-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://www.wowace.com/addons/libra/
-
View User Profile
-
View Posts
-
Send Message
Adminhttp://wow.curseforge.com/addons/broker-reincarnation/repositories/mainline/packager/
-
View User Profile
-
View Posts
-
Send Message
Admin-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorCurrently, Curse.com believes the latest tag is 3.1.15 when it should be 6.0.38.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorIts doing exactly what you told it to do, is all. Although it sometimes gets confused when it has so many tags to process at once.
Once its done, just push another new tag on top, and at your own discretion delete the files you never wanted to have in the first place.
Just be careful what you push, the packager just works through whatever list you give it. Git isn't for everyone, apparently!
-
View User Profile
-
View Posts
-
Send Message
Admin