Re: some try-ark suggestions

<[email protected]> Sun, 10 Jun 2001 13:31:46 -0500 (CDT)
Newsgroups gmane.comp.sysutils.ark.devel
Message-ID <[email protected]>
   Date: Sun, 10 Jun 2001 15:47:24 +0100
   From: Jonathan Hogg <[email protected]>
   Cc: "Will Partain" <[email protected]>, <[email protected]>,
	   <[email protected]>

   On 10/6/01 0:28, [email protected] wrote:

   >I sort of agree with what Harlan wrote in a separate post:  you need to
   >iron this out automatically in the code, and not force the user to pick up
   >that hot iron himself/herself.

   Hi Berto,

   OK. As per Harlan's suggestion and your problem, I've just bashed in some 
   code that I think will do The Right Thing with the different versions of 
   Python and PyXML. I've tried it with Python 1.5.2 + PyXML 0.6.5, Python 
   2.1 + PyXML 0.6.5, and straight Python 2.1 - anyone out there got a 
   version of PyXML earlier than 0.6.x to try for me?

   Please grab the latest version of xmlfile.py from CVS and try for me.

Jonathan:

I mv'ed aside my second failed ark setup and did another CVS checkout of
the very latest stuff.  Several diff commands picked up your xmlfile.py
revision and confirmed that nothing else essentially had changed.

After copying over my myteam1 directory (based on the sample1 directory)
from yesterday's attempt, I get this:

[berto@localhost myteam1]$ try-ark/try-ark | tee /tmp/try-ark.out
try-ark/try-ark: warning: this script may be overly paranoid and, um, wrong...
+ ./arkcmd package reveal --verbose --use-deps=max arkbase
Traceback (most recent call last):
  File "./arkcmd", line 79, in ?
    main()
  File "./arkcmd", line 66, in main
    things_mgr.doToolSubcommand()
  File "./ark/thing.py", line 175, in doToolSubcommand
    victims       = self.unpackSpecs(ark_ctrl.cmdLineNonOptions())
  File "./ark/thing.py", line 108, in unpackSpecs
    thing = self.lookup(thing_name,team_id)
  File "./ark/thing.py", line 69, in lookup
    team_id = ark.team.ACTING_TEAM().id
  File "./ark/team.py", line 55, in ACTING_TEAM
    _ActingTeam.instance = ArkTeam(acting_team_id)
  File "./ark/team.py", line 135, in __init__
    (self._is_prototype, xml_version, self._xmlf) = xml_file.read(explicit_filename="%s/team.xml" % (ark.control.ArkControl().repository(team_id)))
  File "./ark/xmlfile.py", line 152, in read
    root_elem.normalize()
  File "/usr/lib/python2.0/xml/dom/minidom.py", line 74, in __getattr__
    raise AttributeError, key
AttributeError: normalize

Am I getting any warmer?

Someone might suggest that I simply remove my botched PyXML installation
and grab an RPM that will install it into /usr/lib/python2.0, not
/usr/local/lib/python2.0, as the current SourceForge-hosted RPM does.
On the other hand, if I and/or the PyXML package maintainers "botched" things,
it could happen to anyone.  What's the correct response to this?  Just tell
me (and many others?) to go fix my (our) botched installation(s)?  Or for
the Arusha code to be robust enough to deal with these messes?

I favor your continuing to hack a software solution to this problem.  ;-)

Berto

-------------------------------------------------------------------------------
Robert Osterlund, Unix Systems Manager                [email protected]
Grad School of Business, U of Chicago                       phone: 773/702-8898
1101 E. 58th Street, #309, Chicago, IL 60637, USA             fax: 773/702-0233