This is the first project that I am using Git for, and I believe I have followed everything in the wiki. When I initially pushed my repository to WowAce, I did not see any commits, even though I have it set to package Alpha, Beta, and Release. I proceeded to add a "v1" tag and pushed that, and still nothing. I switched directories and cloned just to be sure, and everything was in place, including the tag.
So after a few more commits and still nothing, I asked around IRC and vhaarr mentioned tagging which got me thinking that I should try the web interface to see what would happen. I entered "v2" and submitted, and seconds later my v1, v1-nolib, and only the v2-nolib were packaged. I have since deleted the v1, as I had forgotten the .pkgmeta file back then, but I am still very confused with this right now.
Where did my v2 (without the -nolib) go? Why isn't the packager detecting my commits?
For some reason my project LCD4WoW won't package. The packager page shows blank, and I've made commits and tags, but nothing. I think it broke when I got it approved from experimental state. I made it "Planning" right after submitting for the approval, thinking that would stop it from going public since I found out shortly after submitting for approval that the project got vandalized.
Either that or my hacker wants me to think someone at WoWAce/CurseForge is sabotaging my projects. *wrenched nerves*
Ok, it's creating packages that overlap each other, meaning the previous tag is being packaged with the current tag, but only partially, as in only one file out of -libs and -nolibs.
Nobody knows? I'm about to just create a whole new addon if nobody can help.
Happened to StarTip as well. >.< Reported that one too. Still haven't heard anything back from the report on LCD4WoW. Guess they're busy, or/and they simply hate me.
Somehow StarTip's working again. I disabled packaging, then I changed the repository to point to GitHub, and then I tagged, then turned on packaging again, and tagged twice and it was fixed. Doesn't work for LCD4WoW though.
Also, I changed LCD4WoW and StarTip both to point to GitHub for repository pulls. The packager is still pulling from wowace's git repo.
Good luck getting this fixed. They're "busy" it seems. None of this is your fault. The packager does this and has been doing this forever. It has something to do with converting repositories... or that's the excuse I was given recently. Seeing as you didn't convert yours, then I'm not sure what it is. People act really incompetent though when it comes to this issue...
I did see you mention your problem in IRC a few times, so it's good to know that I'm not the only one dealing with this. For the time being I just changed it to an Subversion repo until things are fixed, though I don't really know how to tell when they are.
We warned you in IRC starlon, not to do what you were doing. I specifically said that you would likely break something (spoken from experience). What you did was voluntary.
And WTF did you make another thread about this for. It isn't like your posts about it lacked detail in the other places you posted them.
]
Just settle down and be patient - or go try and figure it out on your own. Did you delete all your tags for example? That was something we told you you would have to do.
What exactly did he do that you told him not to do? Though our problems sound similar, I know our situations are not the same. In my case I made a new Git repository on a new addon, and in his he used an external Git repository from what I can only assume was some sort of WowAce-hosted repository.
What exactly did he do that you told him not to do? Though our problems sound similar, I know our situations are not the same. In my case I made a new Git repository on a new addon, and in his he used an external Git repository from what I can only assume was some sort of WowAce-hosted repository.
Actually my bad, I thought starlon made this post. I was tired when I read it.
And what exactly was I told not to do? o.O Someone said if I changed the repo on my library, then it would break addons that embed it. Nobody said "if you touch your project in any way at all, then you'll break it."
As far as whose fault it is that the packager breaks, then you'll have to look to the devs whom wrote the thing. Don't blame users.
So after a few more commits and still nothing, I asked around IRC and vhaarr mentioned tagging which got me thinking that I should try the web interface to see what would happen. I entered "v2" and submitted, and seconds later my v1, v1-nolib, and only the v2-nolib were packaged. I have since deleted the v1, as I had forgotten the .pkgmeta file back then, but I am still very confused with this right now.
Where did my v2 (without the -nolib) go? Why isn't the packager detecting my commits?
The addon can be found here:
http://www.wowace.com/addons/balerochealers/
Either that or my hacker wants me to think someone at WoWAce/CurseForge is sabotaging my projects. *wrenched nerves*
Nobody knows? I'm about to just create a whole new addon if nobody can help.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Adminlol
Btw, since you don't hate me, I'll be stalking you on Google+. Beware.
Also, I changed LCD4WoW and StarTip both to point to GitHub for repository pulls. The packager is still pulling from wowace's git repo.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd WTF did you make another thread about this for. It isn't like your posts about it lacked detail in the other places you posted them.
]
Just settle down and be patient - or go try and figure it out on your own. Did you delete all your tags for example? That was something we told you you would have to do.
-
View User Profile
-
View Posts
-
Send Message
Admin-
View User Profile
-
View Posts
-
Send Message
Curse PremiumActually my bad, I thought starlon made this post. I was tired when I read it.
Seems someone would fix the source, since it's so prevalent and such a nuisance. Did Curse cut the funding or something?
And what exactly was I told not to do? o.O Someone said if I changed the repo on my library, then it would break addons that embed it. Nobody said "if you touch your project in any way at all, then you'll break it."
As far as whose fault it is that the packager breaks, then you'll have to look to the devs whom wrote the thing. Don't blame users.