This is also affecting Rarity. I can't get the add-on to build properly as a result of this issue. Can we get an update from anyone? It's not specific to Mercurial, as it happens to only SVN repos in my example.
Seems back up now. Cool that we got no response on this issue. Curse has really gone to shit these past six months. I've got users yelling at me over the packaging bug, and now they're telling me the Client is forcing Alpha builds on them when they set it to Release, again blaming me. The whole platform is inherently unreliable now. It had a good run, but I guess all things come to an end.
Surprised this hasn't gotten any attention yet. This issue also affects me. It completely broke packaging yet again for Rarity. You guys really need to test with multi-line keys any time you touch the localization portion of the packager.
You do need to enter a URL. The directory is what I'm talking about, it's the URL, and it requires some memory or looking up to find. Anyway, it turns out that TortoiseSVN saves your last tag's URL, making this trivial. Since this was SVN-only and it's not as hard as I thought it was, disregard. It's not a big deal.
Must have. :) Out of curiosity, what does the approval process involve? I'm familiar with Apple's, but they use a lot of automated tools and symbol checkers, and then they actually install and run the app. Are you doing any of that? What things would trigger something to not be approved? (This might warrant a larger blog post, maybe.)
This issue affected my add-on Rarity as well. Currently I'm unable to post updates to that add-on due to this. I submitted a ticket and Torhal responded, saying he has made the developers aware of the issue, and it is affecting multiple add-ons.