• 0

    posted a message on Addons push to Curse (software)
    Quote from curseuser1 >>

    Just another data point: Capitalist and Janitor are have the same issue with Curse Client not seeing the new versions that the curse webpage shows.

     

    In case it helps, I'm using Curse Client v5 ("Version 5.1.1.844").

    Closing the loop:
    This version sees the updates:  7.1.6164.2253 Beta.
    Quote from Adrian_G2 >>

    i know, i'm not using them in the new client either and i don't see how to disable permanently those interface bits since i'm using only the addon updates section too ... but the warning was that the old client will not receive updates anymore after the migration... so upgrade and hope they will let us disable the other interface crap bits sometime soon.

     Hope indeed.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on Addons push to Curse (software)
    Quote from Adrian_G2 >>

    Curse Client v5? i thought that the old one was going to be scrapped and no longer function after the migration of the curse platform to the new site.. there was even a notification in-app about this migration around a month or two ago.

     

    my curse client says it's version 7.1.6164.2253 Beta

    Dunno.  I prefer the old client because it doesn't waste a lot of screen space and try to push a lot of crap on me that I don't want.  I just want my mods current, not an chat environment and other junk.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on Addons push to Curse (software)

    Just another data point: Capitalist and Janitor are have the same issue with Curse Client not seeing the new versions that the curse webpage shows.

     

    In case it helps, I'm using Curse Client v5 ("Version 5.1.1.844").

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Can't tag revision
    Quote from ZeldoKavira >>
    Quote from curseuser1 >>
    Quote from ZeldoKavira >>
    Quote from curseuser1 >>

    Hopefully not hijaaking the thread...

     

    ZeldoKavira - Can you take a look at Capitalist again?  I'm out of ideas for how to make it recognize that a Release package should be built.

     Your repo has no tags. To create a tag do the following
    svn copy trunk tags/1.0
    svn ci -m Message for push
    svn up
    Once you do this if it still doesn't work please let me know.
     I'm not sure what this translates to in Tortoise.  I'll try to find out.  Thanks.
     I am not sure either, it seems Tortoise is not pushing the tags and that is what your issue is :)
    Ok, so I finally had some luck with this.
    For future reference, what worked for me in Tortoise was this:
    1. right-click the directory, choose TortoiseSVN/Show log
    2. right-click the revision of interest, choose "Create branch/tag from revision"
    3. for the "To path", use /tags/r12345 (matching the number of the revision you chose in step 2)
    4. for the "Log message", enter "release" (or "beta")
    5. click OK

    Note that in step 3 you can call it whatever you want after the second slash (i.e. "/tags/thebestbuildever").  If that name includes "beta" or "release" or if the "Log message" contains "beta" or "release" the packager notices.

     

    Moderator note: The "numbered lists" don't appear to be working in the forum software.  When I edit, it shows 1-5 above but the posted version has bullets.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on recommended SVN client

    Is there a recommended SVN client?  I thought that's how I originally got TortoiseSVN, but that was years ago.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Can't tag revision
    Quote from ZeldoKavira >>
    Quote from curseuser1 >>

    Hopefully not hijaaking the thread...

     

    ZeldoKavira - Can you take a look at Capitalist again?  I'm out of ideas for how to make it recognize that a Release package should be built.

     Your repo has no tags. To create a tag do the following
    svn copy trunk tags/1.0
    svn ci -m Message for push
    svn up
    Once you do this if it still doesn't work please let me know.
     I'm not sure what this translates to in Tortoise.  I'll try to find out.  Thanks.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on Can't tag revision

    Hopefully not hijaaking the thread...

     

    ZeldoKavira - Can you take a look at Capitalist again?  I'm out of ideas for how to make it recognize that a Release package should be built.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Can't tag revision

    Ok, I'm now able to make beta and release tags/branches.  Not sore the next step to get the packager to recognize the head that I tagged/branched from should be upgraded to release.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Can't tag revision

    I get a very similar problem when I try to create /beta :

     

    [Window Title]
    TortoiseSVN

    [Main Instruction]
    Subversion reported an error:

    [Content]
    Unexpected HTTP status 502 'Bad Gateway' on '/wow/capitalist/!svn/rvr/124/trunk'

    [Close]

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Feedback is pointless when you delete threads

    Thanks.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on New packager

    Update: Hey, a package.  Looks like the old SVN path works for libcraftinfo, with the trimming after trunk.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on New packager
    Quote from ZeldoKavira >>

    Hey!

     

    So I looked into the packaging issue for you after getting some logs from the devs. It seems your Pkgmeta is invalid, You have https://repos.curseforge.com/wow/libcraftinfo/trunk/LibCraftInfo-1.0 as a dep but that folder does not exist under trunk. If you change it to https://repos.curseforge.com/wow/libcraftinfo/trunk it should package!

     

    Also as for the no author commit, they are fixing that now!

     

    Thanks :)

     Thanks for taking a look.
    I don't have any reference to repos.curseforge.com in my pkgmeta.  I have the following:
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceAddon-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConfig-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConsole-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDB-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDBOptions-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceEvent-3.0
    • svn://svn.wowace.com/wow/ace3/mainline/trunk/AceGUI-3.0
    • svn://svn.wowace.com/wow/callbackhandler/mainline/trunk/CallbackHandler-1.0
    • svn://svn.curseforge.com/wow/libcraftinfo/mainline/trunk

    Should all of these change to repos.curseforge.com?  Or just libcraftinfo?

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Packaging Errors with the new repo
    Quote from Vynn >>

    @curseuser1 they show up in the notifications button on the top right of the screen. They seem to clear after you log out of your session though. You should also get a daily digest with the same reports that show up in the notifications. 

    Ah, ok.  Hm.  Despite submitting two commits since the migration, there's no indication on the packaging side of things (Files link or notifications) that the packager trigger (or whatever) even noticed either of them.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on New packager
    You do not need GitHub or BitBucket accounts at all! You repo is failing to build for some reason, the devs are looking into it now. In the future this information will be surfaced but since the Dashboard had to be temporarily disabled its currently not easily viewable.
     Thanks for the clarification and info.
     
    Quote from ZeldoKavira >>

     Just FYI, Curse hosted repos are still there, under settings -> source. Select "Curse Forge" then select use existing, create new svn/mercurial/git, or restore archived

    Yup and it should have automatically set this for you!

    Yes, mine already had "CurseForge / Use your existing Subversion repository" set.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on Packaging Errors with the new repo

    Where are you seeing the packaging log?  I'm having trouble finding it on the new site.  Thanks.

    Posted in: WoW Sites Feedback
  • To post a comment, please or register a new account.