On Sunday, March 05, 2017 07:44:37 PM Jack wrote: > I just tried using craft for the first time in several months, and have > run into a number of issues. Help or suggestions on any of them would > be appreciated. (I posted some of these to the IRC channel, but so far, > haven't seen any response.) >
I encountered many of these myself. Yes, you must have Python3.6. I suggest installing Python3.6 first (in c:\python36) and also make very sure you are not setting PYTHONHOME. I'm stuck on another problem with wget. I think craft is picking up the wget from my already installed C:\Program Files (x86)\Gow and it doesn't like that. ie. *** Handling package: wget, action: all *** *** Action: fetch for gnuwin32/wget *** SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = C:\Program Files (x86)\Gow/etc/wgetrc Action: fetch for gnuwin32/wget FAILED *** Craft all failed: all of gnuwin32/wget failed after 0:00:00 *** fatal error: package gnuwin32/wget all failed > 1) per an error message, I upgraded my python from 3.5 to 3.6. However, > I then got some messages about needing to set the python27 variable. Is > 2.7 really needed in addition to 3.6? Am I just asking for trouble > pointing python27 to my 3.6 version? > > 2) on https://community.kde.org/Windows the link near the bottom to the > source code in git points to raft.git instead of craft.git. > > 3) is there still no single craft command to update all installed packages? > > 4) I initially got a strange error, which suggests typos in two calls to > craftDebug.log.debug in craft/bin/utils.py. I've attached a patch file > showing the two lines I changed - both removing the leading 'f' from the > start of the call '(f"C...' and also fixing a spelling error in one from > Coammand to Command. > > 5) Attempting to upgrade libpng, I get compile errors with 1.5.28 > (default target) and also with 1.6.6 and 1.6.27. I'll be glad to post > more details if anyone is interested. > > I suspect I will still have problems with mpir, but haven't gotten that > far yet. (I believe it was a compile error related to make using either > absolute or relative path, when only the other actually works > correctly. I've posted about it some time ago, but never got a good > resolution.) > > Jack >
