As title says: I'm trying to upload changes to my project, but for some reason, the revisions wont show in "files". They are indeed uploaded to the svn...
Chance anyone got a suggestion of, what the issue is? Thanks on advance.
I now have another issue: Curse still shows latest file as "1.0.3b", even tho i've tagged the latest upload as "1.0.4b" - it appears correctly on curseforge, but appearently, it does not sync with curse... Is this just me being unpatient? (almost 24 hours ago) - or have i done something wrong?
EDIT: Seems it is correctly synced with the curseclient - only the curse-website seems to not show the correct "Latest File"
Don't intend to hijack this thread, but it seems like it could be related; the last couple of releases I've attempted to do have ended up with the packager uploading the previous tag's zip file for the 'with-lib' copy, and the newly-tagged zip file for the 'nolib' copy.
Packager seemed to trigger a "500 Internal Server Error" back in February when the problem first arose - I've attempted to delete the files then re-tag and re-release, but the deleted files from the previous tag are the ones which get uploaded to the files list. I've ended up releasing twice in order to get things working - I figured it was a transient issue but today's attempt says otherwise.
Here's the link to the packager log - versions 1.0.0, 1.0.1, and 1.0.2 are the problematic tag attempts.
Don't intend to hijack this thread, but it seems like it could be related; the last couple of releases I've attempted to do have ended up with the packager uploading the previous tag's zip file for the 'with-lib' copy, and the newly-tagged zip file for the 'nolib' copy.
Packager seemed to trigger a "500 Internal Server Error" back in February when the problem first arose - I've attempted to delete the files then re-tag and re-release, but the deleted files from the previous tag are the ones which get uploaded to the files list. I've ended up releasing twice in order to get things working - I figured it was a transient issue but today's attempt says otherwise.
Here's the link to the packager log - versions 1.0.0, 1.0.1, and 1.0.2 are the problematic tag attempts.
I'm guessing your repository wasn't originally Git. I've seen this happen with some conversions from SVN, though I've never had the issue myself.
I re0queued the project and the packager produced a valid file. Let me know if it happens again.
Chance anyone got a suggestion of, what the issue is? Thanks on advance.
I now have another issue: Curse still shows latest file as "1.0.3b", even tho i've tagged the latest upload as "1.0.4b" - it appears correctly on curseforge, but appearently, it does not sync with curse... Is this just me being unpatient? (almost 24 hours ago) - or have i done something wrong?
EDIT: Seems it is correctly synced with the curseclient - only the curse-website seems to not show the correct "Latest File"
Packager seemed to trigger a "500 Internal Server Error" back in February when the problem first arose - I've attempted to delete the files then re-tag and re-release, but the deleted files from the previous tag are the ones which get uploaded to the files list. I've ended up releasing twice in order to get things working - I figured it was a transient issue but today's attempt says otherwise.
Here's the link to the packager log - versions 1.0.0, 1.0.1, and 1.0.2 are the problematic tag attempts.
I'm guessing your repository wasn't originally Git. I've seen this happen with some conversions from SVN, though I've never had the issue myself.
I re0queued the project and the packager produced a valid file. Let me know if it happens again.
No, the repo was a git repo from day one. Thanks for the troubleshoot/fix!