Home Forums Software InstaDMG Behind a proxy – can’t run instadmg/AddOns/InstaUp2Date/instaUp2Date.py 10.6_vanilla –process

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #379348
    mgb123
    Participant

    I’m attempting to run a first time build but can’t seem to get InstaUp2Date to run – I’m guessing due to some proxy issues.

    Any advice in this area would be greatly appreciated!

    #379349
    nobrainer
    Participant

    We’re behind a proxy too…you can try copy / pasting the links from the catalog to a web browser and see if that gets you out..

    #379351
    mgb123
    Participant

    I’m able to get the files by hand from a browser, I’m just not able to get them with the InstaUp2Date. I did have to configure the proxy file for svn in order to get it to work, so I’m guessing a similar change might be needed for InstaUp2Date.

    #379357
    larkost
    Participant

    I have nowhere to test out proxied systems. A quick look indicated that the documentation on the python urllib2 module (what InstaUp2Date uses) seems to indicate that it should be reading the proxy information from the configuration framework. So in theory this should already be working. If you can figure out what has to be done to get urllib2 to work through your proxies, then I can try to add it, but short of that I don’t know what to do.

    #380949
    ktappe
    Participant

    [QUOTE][u]Quote by: larkost[/u][p]>I have nowhere to test out proxied systems. A quick look indicated that the documentation on the python urllib2 module (what InstaUp2Date uses) seems to indicate that it should be reading the proxy information from the configuration framework. So in theory this should already be working. If you can figure out what has to be done to get urllib2 to work through your proxies, then I can try to add it, but short of that I don’t know what to do.[/p][/QUOTE]
    I can’t get InstaUp2Date to work through our proxy servers either. Researching urllib2 reveals it does have parameters that must be passed in for it to go through proxies, which seems to imply it does not honor the Mac system’s proxy configuration.
    Specifically, when you build the parameters for urllib, you should do so via: urllib2.build_opener(proxy_support, authinfo), where proxy_support = urllib2.ProxyHandler({“http” : “http://proxy:8080”})

    What would be sweet if there were a way to suck the Mac system’s proxy info into this parameter. How about using:

    system_profiler | grep “HTTP Proxy Server”
    and
    system_profiler | grep “HTTP Proxy Port”

    I’m no Python jockey so I have to leave it to the experts to assemble these pieces into a working whole. But I hope I’ve helped the process along somehow. I’m stuck building OS X by hand until we can get this fixed.

    #380951
    Allister Banks
    Participant

    Hey ktappe,

    Not sure how not being able to get out of your proxy with the python process leaves you ‘stuck’ necessarily. You’re still able to run instaUp2Date with locally cached items. If you need assistance with that please let me know.

    Allister

    #380957
    Tim Sutton
    Participant

    Sure, he’s not completely stuck but he’s only left the option of manually downloading updates in a browser, checksumming each one, appending the sha1 to the dmg and placing them in the InstaUp2DateCaches folder. Doable, but he can’t even see what the correct naming format would be.

    Yanking the system proxy’s an option. If there’s a native framework available via PyObjC, Karl will certainly endorse that method above others. I recently had to parse system_profiler in a python script and it’s doable, but ugly. system_profiler outputs XML as an option, but it’s only designed for use by System Profiler.app. If you ever look at it, you’ll see it bears little resemblance to a logical structure. Going the system_profiler route, you’re stuck with parsing text subject to change, though by XML you’re using its internal key names, so safer than parsing the text output. Again, doable.

    The simplest option, of course, is to provide a command-line option to instaUp2Date.py to specify the proxy. On a related note, I think there’s actually quite a few “advanced” options for instadmg.bash that’d be very handy to have available to pass with the –process flag.

    #381169
    freepms
    Participant

    InstaUp2Date isn’t seeing through my proxy either. I’m a beginner to these tools, and was surprised to find them not honoring the system proxy settings. Here’s the output I get from instaUp2Date.py 10.6_vanilla –process (with the 10.6_vanilla.catalog updated with 10.6.8 combo etc):

    Exception: Got status code: 407 while trying to connect to remote url: http://support.apple.com/downloads/DL1399/en_US/MacOSXUpdCombo10.6.8.dmg

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.

Comments are closed