Hi Shawn,
I install SUNWcherrypy out of the packages built every night for
testing of other bits too. Do you have a changeset ID for the CherryPy
you'd suggest I use (perhaps 1193?)?
Thank you,
Clay
On Sat, 11 Jul 2009, Shawn Walker wrote:
Clay Baenziger wrote:
Hi all,
I'm also seeing these errors on my IPS servers too (no Apache in play).
I hit this when publishing to my SPARC IPS server (using changeset 1211 on
OSOL build 117) and DIY testing is hitting this when trying to do an AI
install off my X86 IPS server (running changeset 1211 on OSOL build 117).
Any suggestions?
What happens if you nuke the cherrypy directory in the proto area:
$WS/proto/root_`uname -p`/vendor-packages/cherrypy/
...before you start the build import?
Although the depot server hasn't changed, cherrypy was recently patched with
408 timeout error fix from the cherrypy website. It looks as though that may
have made the problem worse for some cases, while fixing others (which we
verified it fixed other cases).
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss