Authors CurseForge

OHHHHH.....

i shouldnt do things this early...

sounds like you need to run it as root. Or change file permissions on WUU.log

yeah, i got it to work correctly, i had to put it in the apps folder. :P meh

Im not having any changelog summery being created anymore, worked for a couple of days and now has stopped working.

Quote from Greywind »

Im not having any changelog summery being created anymore, worked for a couple of days and now has stopped working.

Yeah, I'm seeing the same error myself :( Will look at it next weekend - I'm a bit busy during the week these days :|

Quote from paradigmlie »

yeah, i got it to work correctly, i had to put it in the apps folder. :P meh

Yep, the OS X instructions leaves a bit to be desired - I'll work on it when I get my Mac back (and try to make a better .dmg, with the Applications link and stuff)

lejordet: The changelogs in the script is changing towards a final format.

Quote from Kaelten »

lejordet: The changelogs in the script is changing towards a final format.

Ah, that explains it :) I'm using a rather strict regexp to parse 'em :)

I assume I'm going to be unpopular if I as if you can add the xml changelogs back into the zips? :P (yep, I followed the thread back last time you changed anything ;))

EDIT: this thread, for those who wondered :)

txt logs are going to be in the zips, xml logs and txt logs will be available on the server for direct download.

Quote from Kaelten »

txt logs are going to be in the zips, xml logs and txt logs will be available on the server for direct download.

Perfect :D That way we don't have to stress the servers more than necessary :)

I'm also going to add an option to delete the local changelogs when you exit WUU, to save space :)

:) although I will say that the space used should be less now than it was previously. Also deleting the logs would inhibit wau from being used alongside wuu. It might be rare but I'm sure someone out there does it or switches back and forth ect.

Quote from Kaelten »

:) although I will say that the space used should be less now than it was previously. Also deleting the logs would inhibit wau from being used alongside wuu. It might be rare but I'm sure someone out there does it or switches back and forth ect.

I'll make it an option anyhow (default disabled, of course), so it's up to the users to decide whether they want it or not. I'm sure it's important for someone to save the space in question :)

(For the record, in my installation (262 addons), the changelogs took 1.1Mb (out of 49.5Mb - about 2.22% (all numbers are "space takenon disk", not the file size (I like nesting parentheses (like this)))))

k, I'd appriciate it you'd warn them that wau will have issues if they enable it.


where those numbers including the old xml logs for externals? and multiple logs for each successive update.

Quote from Kaelten »

k, I'd appriciate it you'd warn them that wau will have issues if they enable it.


where those numbers including the old xml logs for externals? and multiple logs for each successive update.

Those were with only the latest changelog for each addon (I'm running no-ext, and CleanOnUpdate)

I should not that most changelogs are 1-3Kb, while the one I have for Threat-1.0 is 135Kb (???)

EDIT: Oh, yes, I'll of course add a huge sign with "OH GOD THIS'LL MAKE WAU EXPLODE DON'T TOUCH" ;)

lol, heh, I guess they add up quick (especially over 262 addons ehem)

Quote from Kaelten »

lol, heh, I guess they add up quick (especially over 262 addons ehem)

Yep, I run this set of addons nowadays (of course, running no-ext and LoD-extract makes the numbers explode ;))

I love the updater except for one major problem that actually makes it nearly unusable for me: when you manually delete addons from the directory, it redownloads them if you run the updater. Even if I completely rescan with WUU (every option under "addon"), it still has addons I removed days ago. I half-hacked together a solution with keeping a window open in my addon directory and just deleting the new directories, but its a huge hassle.

I'm half tempted to convert my addons to Ace2 only so I can just use their SVN updater.

Quote from tupper »

I love the updater except for one major problem that actually makes it nearly unusable for me: when you manually delete addons from the directory, it redownloads them if you run the updater. Even if I completely rescan with WUU (every option under "addon"), it still has addons I removed days ago. I half-hacked together a solution with keeping a window open in my addon directory and just deleting the new directories, but its a huge hassle.

I'm half tempted to convert my addons to Ace2 only so I can just use their SVN updater.

You have to delete the addon from within WUU ([Del] in the addon list, or ctrl-D) for WUU to "forget" the addon :)

I still half-expect rescanning my directory to clear the missing folders from my WUU list, or maybe just highlight the entries that are missing. But I've become accustomed to using it as a file manager, too.

I was using my addons with no exts and unembedded packages, but because I was having too much errors ingame (AUldLangSyne was going mad) I wanted to go back to "normal" mode with no exts. Now my question, how can I do that? I first hid outdated and ignored, then deleted all relative and finally "forced" updated all my files. Do you maybe know a smarter method? Thanks and greets

Rollibock

Getting this error with Cartographer, Bigwigs & oRA2 with Handling Addon packages turned on.

2007-07-09 16:50:44: (INFO) Handling Addon package
2007-07-09 16:50:45: (ERROR) Installation of oRA2 failed: maximum recursion depth exceeded
2007-07-09 16:50:45: (INFO) oRA2 is updated to 43194.1

I believe the addon is not updated either :(

I turned off off handling addon packages and tried to delete the related addons in WUU and recieved this error: I was removing Bigwigs_BlackTemple

File "WurmCommon.pyc", line 595, in findAllRelated
File "WurmCommon.pyc", line 593, in findAllRelated
File "WurmCommon.pyc", line 837, in getAtype
File "logging\__init__.pyc", line 1055, in log
File "logging\__init__.pyc", line 1178, in isEnabledFor
RuntimeError: maximum recursion depth exceeded

This made me think the error wasn't to do with handling the packages. I turned addon packages back on, but turned off the option to delete addons before updating. All addons updated successfully.

I hope this helps :)