Opened 16 years ago
Closed 15 years ago
#17419 closed submission (duplicate)
NEW PORT PyMOL-1.1
Reported by: | adfernandes (Andrew Fernandes) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.0 |
Keywords: | Cc: | dwing84@… | |
Port: | pymol |
Description
Here is a port for an X11 build of PyMOL. The fany installer is because of the brain-dead linux-assuming install script from the autohell tools.
Attachments (2)
Change History (11)
Changed 16 years ago by adfernandes (Andrew Fernandes)
comment:2 Changed 16 years ago by nerdling (Jeremy Lavergne)
Keywords: | science pymol x11 removed |
---|---|
Version: | 1.6.0 → 1.7.0 |
The portfile failed to fetch. Please update svn.url in the portfile.
svn: PROPFIND request failed on '/svnroot/pymol/branches/b11/pymol' svn: PROPFIND of '/svnroot/pymol/branches/b11/pymol': Server certificate verification failed: issuer is not trusted (https://pymol.svn.sourceforge.net) Warning: the following items did not execute (for pymol): org.macports.activate org.macports.fetch org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.archive org.macports.install Error: Target org.macports.fetch returned: Subversion check out failed Error: Status 1 encountered during processing.
comment:3 Changed 16 years ago by adfernandes (Andrew Fernandes)
The svn.url
as per the portfile is correct.
The port fails to fetch because of something going wrong between SVN's certificate repository and/or sourceforge's SSL certificate.
Note that the current svn.url is https://pymol.svn.sourceforge.net/svnroot/pymol/branches/b11/pymol
. You can change the url to attempt to match the certificate better by adding the HTTPS port as https://pymol.svn.sourceforge.net:443/svnroot/pymol/branches/b11/pymol
, but get identical results (see below).
My interpretation is that subversion is incorrectly failing to parse sourceforge's wildcard SSL certificate.
Summary - I believe that this behaviour is a bug in MacPorts/SVN. (In fact, the sourceforge certificate was issued on 12 Nov 2008, so I'm guessing that the Root CA is not in SVN's trusted CA database.
dyn129-100-144-235:pymol andrew$ mkdir tmp dyn129-100-144-235:pymol andrew$ cd tmp dyn129-100-144-235:tmp andrew$ svn co https://pymol.svn.sourceforge.net:443/svnroot/pymol/branches/b11/pymol Error validating server certificate for 'https://pymol.svn.sourceforge.net:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: *.svn.sourceforge.net - Valid: from Wed, 12 Nov 2008 01:25:27 GMT until Tue, 12 Jan 2010 01:25:27 GMT - Issuer: Equifax Secure Certificate Authority, Equifax, US - Fingerprint: 04:b2:70:e9:ba:cf:70:fc:e8:8a:22:86:14:13:51:97:1b:6a:de:38 (R)eject, accept (t)emporarily or accept (p)ermanently? t A pymol/configure A pymol/Makefile.in A pymol/ov A pymol/ov/src A pymol/ov/src/Makefile.delsci A pymol/ov/src/OVContext.h A pymol/ov/src/OVOneToOne.h A pymol/ov/src/Makefile.in A pymol/ov/src/OVOneToAny.c A pymol/ov/src/OVLexicon.c A pymol/ov/src/OVOneToAny.h A pymol/ov/src/ov_utility.c A pymol/ov/src/OVLexicon.h A pymol/ov/src/ov_utility.h A pymol/ov/src/OVreturns.h [... remainder deleted ...]
comment:4 Changed 16 years ago by jmroot (Joshua Root)
Type: | enhancement → submission |
---|
comment:5 Changed 16 years ago by (none)
Milestone: | Port Submissions |
---|
Milestone Port Submissions deleted
comment:6 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
It looks like this ticket will be obsoleted by #21376 which is a request for pymol 1.2r1.
Changed 15 years ago by adfernandes (Andrew Fernandes)
Attachment: | Portfile.2 added |
---|
pymol 1.2r2 - almost
comment:7 Changed 15 years ago by adfernandes (Andrew Fernandes)
Ha! Funny - I've spent part of the afternoon getting 1.2r2 (released October 05) running. My port is attached.
The thing builds... BUT... It needs either (a) pwm and tkinter OR (b) wxpython.
My 1.1 port built and ran fine with tkinter. However, this 1.2r2 portfile works fine until we get a crash in python 2.6.3's tkinter. (I have updated all versions on my local ports; the crash seems unavoidable). So... I decided to build wxPython... and the latest 2.8.10.1 won't build on the mac because they've left in all sorts of win/gtk-specific functions on the swig wrappers.
Yuck.
I'm building an old version of wxPython now, hoping it works.
comment:8 Changed 15 years ago by adfernandes (Andrew Fernandes)
comment:9 Changed 15 years ago by adfernandes (Andrew Fernandes)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
initial portfile