hi,

- about the problem of different packages depending on different versions of python:

  i think the best way would be to make different packages python2.2 and
  python2.1. this is the way it is done in the debian distribution. the python
  debian is just a very small package that depends on the default python version
  (python2.1 in the case of debian) and that provides symbolic links to the
  binaries and man pages.

  i also made the following observation: the fink .deb file contains python source code
  files (.py) as well as byte-compiled files (.pyc). the debian (linux) .deb packages 
only
  contain the source files and byte-compile them in the postinst script. maybe
  this is the better way to handle python packages in general.

- about zope not running:

  i would really like to understand what goes wrong. it works fine with me and
  i got positive feedback about the package form another user on the zope
  maliling list. this is why i even moved the package to stable. probably i
  should remove it from stable untill the problem is solved...

- about fink update-all upgrading python and breaking dependencies:

  i asked about it in another mail on the list. i don't understand what is
  happening. zope depends explicitely on python-2.1.2-1. i don't know why
  fink and dpkg are not respecting the dependency and are upgrading python to
  version python 2.2.1-1. has anybody any idea?

cheers,
  kilian

On Wed, Apr 24, 2002 at 09:53:46AM -0400, Chris Devers wrote:
> 
> On Wed, 24 Apr 2002, Stephan Jaeger wrote:
> 
> > - The first problem is that python has to be downgraded to version 2.1
> > Is there any solution for this problem available?
> > The downgrade works fine, so I am not too concerned about that. It is
> > just a bit annoying that I cannot use the command "fink upgrade-all"
> > anymore.
> 
> I had the same problem. Downgrading Python to 2.1 broke packages that were
> built against Python 2.2. I'd have put up with this -- I'm more interested
> in Zope than I am in some of the other Pythone related software -- but I
> can't even get it to work right. In the end I just ended up removing Zope
> for now, bringing Python back to 2.2, and the breakages all went away.
> (Except, of course, that I don't have Fink's Zope installed any more...)
> 
> > stephan@localhost (/dev/ttyp5) ~ > /sw/sbin/zopectl start
> > Starting Zope...Traceback (most recent call last):
> >    File "/sw/sbin/zope-z2", line 476, in ?
> >      import ZServer
> >    File "/sw/lib/zope/ZServer/__init__.py", line 26, in ?
> >      from medusa import asyncore
> >    File "/sw/lib/zope/ZServer/medusa/asyncore.py", line 50, in ?
> >      import select
> > ImportError: No module named select
> > 
>....................................................................................................
> 
> Yes, this is the error I was getting with Zope too. Spent half an hour or
> so trying to figure it out before giving up & removing Zope & restoring
> Python to 2.2.
> 
> As interested as I am in Zope, I don't think I'll try it again until
> either [a] it can work against Python 2.2 (preferred solution), or [b] a
> way is found to have multiple versions of Python present. Actually, I was
> hoping that would be pretty easy -- I installed a different version of
> Zope last week, and it included a copy of Python with it. I was hoping I
> could just change the #!/ lines to point to the other, good version, but
> apparently the problem is much more subtle than that, as this change
> didn't end up helping anything at all. *shrug*
> 
> 
> --
> Chris Devers                                [EMAIL PROTECTED]
> Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
> 
> "More war soon. You know how it is."    -- mnftiu.cc
> 
> 
> _______________________________________________
> Fink-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/fink-users

_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to