Stack overflow on hackage upload
I can't seem to upload the new GD release to hackage: $ cabal-upload dist/gd-3000.1.0.tar.gz Uploading dist/gd-3000.1.0.tar.gz... ERROR: 500 Internal Server Error <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> http://www.w3.org/1999/xhtml"
I get the same error when using my web browser to upload. I have attached the tarball I tried to upload. /Björn
On Thu, 2007-05-10 at 15:27 +0100, Ross Paterson wrote:
On Thu, May 10, 2007 at 02:01:30PM +0200, Bjorn Bringert wrote:
I can't seem to upload the new GD release to hackage:
Sorry about that. Fixed now.
I was hoping this might be the same bug that prevents me from uploading cabal-1.1.6.2.tar.gz but it seems not. I still get 400 error during upload after a few 100k. I suspect it's a server side limit on the upload size. Cabal-1.1.6 is just under 500k and Cabal-1.1.6.2 is just over. Perhaps I should try and reduce the size of the tarball by taking the built docs out (I'm not sure why they're in there, that's just what the current cabal makefile does). In case anyone else wants to try, the tarball is on the Cabal website: http://haskell.org/cabal/download.html Duncan
On Thu, May 10, 2007 at 10:30:17PM +0100, Duncan Coutts wrote:
I was hoping this might be the same bug that prevents me from uploading cabal-1.1.6.2.tar.gz but it seems not. I still get 400 error during upload after a few 100k.
I suspect it's a server side limit on the upload size. Cabal-1.1.6 is just under 500k and Cabal-1.1.6.2 is just over. Perhaps I should try and reduce the size of the tarball by taking the built docs out (I'm not sure why they're in there, that's just what the current cabal makefile does).
The problem is probably the use of getInputFPS for the uploaded file -- a lazy bytestring version would be handy.
On May 11, 2007, at 1:14 , Ross Paterson wrote:
On Thu, May 10, 2007 at 10:30:17PM +0100, Duncan Coutts wrote:
I was hoping this might be the same bug that prevents me from uploading cabal-1.1.6.2.tar.gz but it seems not. I still get 400 error during upload after a few 100k.
I suspect it's a server side limit on the upload size. Cabal-1.1.6 is just under 500k and Cabal-1.1.6.2 is just over. Perhaps I should try and reduce the size of the tarball by taking the built docs out (I'm not sure why they're in there, that's just what the current cabal makefile does).
The problem is probably the use of getInputFPS for the uploaded file -- a lazy bytestring version would be handy.
getInputFPS already returns a lazy ByteString, iirc. Besides, even strict bytestrings should work fine with 500k, right? /Björn
On Fri, May 11, 2007 at 11:05:22AM +0200, Bjorn Bringert wrote:
On May 11, 2007, at 1:14 , Ross Paterson wrote:
On Thu, May 10, 2007 at 10:30:17PM +0100, Duncan Coutts wrote:
I suspect it's a server side limit on the upload size.
The problem is probably the use of getInputFPS for the uploaded file -- a lazy bytestring version would be handy.
getInputFPS already returns a lazy ByteString, iirc. Besides, even strict bytestrings should work fine with 500k, right?
Ah yes, getInputFPS works fine with large files. So much for that theory. The problem is in the package cabal-1.1.6.2.tar.gz itself: the name of the tar file, directory, .cabal file and package must match exactly. As the error message says: could not extract cabal-1.1.6.2/cabal.cabal from cabal-1.1.6.2.tar.gz
On Fri, 2007-05-11 at 11:39 +0100, Ross Paterson wrote:
On Fri, May 11, 2007 at 11:05:22AM +0200, Bjorn Bringert wrote:
On May 11, 2007, at 1:14 , Ross Paterson wrote:
On Thu, May 10, 2007 at 10:30:17PM +0100, Duncan Coutts wrote:
I suspect it's a server side limit on the upload size.
The problem is probably the use of getInputFPS for the uploaded file -- a lazy bytestring version would be handy.
getInputFPS already returns a lazy ByteString, iirc. Besides, even strict bytestrings should work fine with 500k, right?
Ah yes, getInputFPS works fine with large files. So much for that theory.
The problem is in the package cabal-1.1.6.2.tar.gz itself: the name of the tar file, directory, .cabal file and package must match exactly. As the error message says:
could not extract cabal-1.1.6.2/cabal.cabal from cabal-1.1.6.2.tar.gz
Ah! Getting that error message would have been very handy, rather than a generic apache 400 error page. Right, I'll fix it and upload. Thanks for investigating. Duncan
participants (3)
-
Bjorn Bringert -
Duncan Coutts -
Ross Paterson