RE: Invalid Arguement?

Seems I had a typo on the line number. Should have been #298 not #238
after comment
# Open the other shelves
Sorry about that.

I actually looked in the C python module for Python 1.5.2 and found where the 
error is generated.  If you go look on the Python mailing lists, you WILL find 
that a common reported cause for this error is Berkeley DB version skew.
See http://mail.python.org/pipermail/python-list/2001-January/024648.html as an 
example of this.

I'm not saying that is what it is. But.... Amuse me.

Take my added line out. Build your channel. Do the 'file' thing.
Put my line in (where it belongs). Start up current. Do the 'file' thing on the 
new file in /tmp.  If the versions are the same, this is not the problem. If 
they are different, it is the problem.  Then the question is WHY.

Are you building the channel AND running the server as the SAME user with the 
same environment?

Try EXACTLY the rpm's I reported working.  That better work!

Toby


Quoting Matt Bottrell <[email protected]>:

> [ previous comments deleted ]
> 
> Toby,
> 
> Have confirmed the following:
> 
> 1. Didn't have compat-glibc installed.  (Now installed)
> 2. Confirmed I have either later or same RPMS as yourself installed.
> 
> 3. Added the line:
> ------------ CODE SNIPPET from channel.py --------------
>      if self.dep_files.has_key(dep):
>                 dep_file = self.dep_files[dep][0]   # <-- [0] FIXME
> 
>                 # Here we return all possible archs for that pkg.
>                 return self.arch_index[dep_file]
> 
>             else:
>                 # No hit for that file. It can't be a provide or name,
>                 # (not if it starts with a /) so, we dump.
> Added this --->  junk = bsddb.btopen('/tmp/test.wdb', 'w')    <--- Added
> this!
>                  return None
> 
> ------------ CODE SNIPPET from channel.py --------------
> 
> 4. Re-ran channel creation, restarted current via the 'service current
> restart' 
> command.  Then checked for /tmp/test.wdb -- It wasn't there.  8-(  I don't 
> think this piece of code is actually running...
> 
> 5. Confirmed the following after creating a channel:
> 
> file rpm_index.wdb
> rpm_index.wdb: Berkeley DB 1.85/1.86 (Btree, version 3, native byte-order)
> 
> 
> Okay -- I'm now officially running at a blank.   8-)
> 
> 
> One recommendation -- Include the dependancy in the spec file file for
> compat-
> glibc -- however this still hasn't resolved my problem.  But will ensure
> others 
> have it installed.
> 
> I'll grab the tarball and give that a whirl next....   It might be a broken
> 
> SRPM that I'm working from...
> 
> Regards,
> 
> Matt.
> 
> PS:  I'm really open to ideas now!  8-)  I'm definately drawing a blank!
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
>