GNOME Bugzilla – Bug 706339
ftpadmin "500 Internal Server Error" from Bugzilla
Last modified: 2013-08-20 20:15:36 UTC
When I install a new goffice I get a scary complaint about "500 Internal Server Error" with no clue as to what the real problem is. This does not happen when I install gnumeric, for what that is worth. Apart from the scary message, everything appears to be just fine. The problem isn't new. This has happened for years. Preparing installation of goffice-0.10.5.tar.bz2: - Checking consistency: ............., done - Checking previous tarball: ............., done - NEWS, done (diff, 20 lines) - ChangeLog, done (diff, 116 lines) - Creating tar.xz from tar.bz2: ............., done - Creating sha256sum, done Module: goffice Version: 0.10.5 (previous version: 0.10.4) Destination: /ftp/pub/GNOME/sources/goffice/0.10/ Install goffice? [Y/n] Installing goffice-0.10.5.tar.bz2: - Moving files: ...., done - Updating LATEST-IS, done - Updating known versions, done - Removing original tarball, done Doing notifications: - Informing ftp-release-list, done - Triggering GNOME library update, done - Adding new version to GNOME Bugzilla<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, bugmaster@gnome.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> <hr> <address>Apache/2.2.3 (Red Hat) Server at bugzilla.gnome.org Port 443</address> </body></html> , done - Triggering ftp.gnome.org update, churchill.acc.umu.se, done
I can very well imagine that it's always the case for goffice, as its name is "libgoffice" in Bugzilla. Hence no product with the same name to create a new "Version" field entry for, but could fail more gracefully...
*** This bug has been marked as a duplicate of bug 706440 ***