GNOME Bugzilla – Bug 706440
Error while setting-up release tarball
Last modified: 2013-11-21 14:56:49 UTC
[zeeshanak@master ~]$ ftpadmin install gnome-maps-3.9.90.1.tar.xz Gathering information and sorting on version: ., done Preparing installation of gnome-maps-3.9.90.1.tar.xz: - Checking consistency: .., done - Checking previous tarball: .., done - NEWS, done (diff, 33 lines) - Copying tar.xz, done - Creating sha256sum, done Module: gnome-maps Version: 3.9.90.1 (previous version: 3.9.5) Destination: /ftp/pub/GNOME/sources/gnome-maps/3.9/ Install gnome-maps? [Y/n] Installing gnome-maps-3.9.90.1.tar.xz: - 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 Your tarball will appear in the following location on ftp.gnome.org: http://download.gnome.org/sources/gnome-maps/3.9/ It is important to retain the trailing slash for compatibility with broken http clients, and to use http as it is less taxing on the server. 1c51d717ce863cd6f42020a56899621cd5c90586ab15fce7c1dbc871ec692f85 gnome-maps-3.9.90.1.news 3ee14aa26bbd6352f0ca8cd49915b5bd66af3dc74f079b2e1ee2b2badd683139 gnome-maps-3.9.90.1.tar.xz The ftp-release-list email uses information from the modules DOAP file. Make sure at least the following fields are filled in: name, shortdesc, description, download-page, bug-database See http://live.gnome.org/MaintainersCorner#doap Please report any problems to: https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin [zeeshanak@master ~]$
Andre, what's happening today with the automatic new version creation of ftpadmin?
Doing something like "/usr/bin/curl -q -L "https://bugzilla.gnome.org/add-version.cgi?gnome-maps|3.9.5" returns me 'exists' but the new version isn't there at all, any idea?
*** Bug 706339 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Andre, what's happening today with the automatic new version creation of > ftpadmin? Errm, I neither know the problem nor the code of that script, sorry.
Zeeshan, did someone create the new version on bugzilla manually? what the script does is calling "/usr/bin/curl -q -L "https://bugzilla.gnome.org/add-version.cgi?product|new_version" and as far as I see there's a component called '3.9.x' on bugzilla already, in addition the command above results in a 'exists, gnome-maps' output. I'm wondering if someone add the version manually and caused the internal error when called.
(In reply to comment #5) > Zeeshan, did someone create the new version on bugzilla manually? what the > script does is calling "/usr/bin/curl -q -L > "https://bugzilla.gnome.org/add-version.cgi?product|new_version" and as far as > I see there's a component called '3.9.x' on bugzilla already, in addition the > command above results in a 'exists, gnome-maps' output. I'm wondering if > someone add the version manually and caused the internal error when called. Its possible that I myself did that but I don't recall doing it. :(
The GNOME Infrastructure Team is currently migrating its bug / issue tracker away from Bugzilla to Request Tracker and therefore all the currently open bugs have been closed and marked as OBSOLETE. The following move will also act as a cleanup for very old and ancient tickets that were still living on Bugzilla. If your issue still hasn't been fixed as of today please report it again on the relevant RT queue. More details about the available queues you can report the bug against can be found at https://wiki.gnome.org/Sysadmin/RequestTracker. Thanks for your patience, the GNOME Infrastructure Team