Librarian loses media type of tarball

[Leonard Richardson]

On Friday the 14th, I uploaded a tarball to the Beautiful Soup project using the web browser. I used wget to verify that the tarball was served as application/x-tgz. I did this because my users were complaining (see bug 702816) that the Launchpad librarian was serving tarballs as text/html.

A few days later, my users are complaining again. I used wget to verify that the tarball was now being served as text/html.

It's possible that I'm misremembering what happens. I have discovered a bug in a launchpadlib contrib script which sends a nonexistent content type when uploading a tarball, making the librarian serve it as text/html. It's possible that the tarball I uploaded on Friday *never* had a media-type of application/x-tgz. But I remember verifying this, and my user confirms that easy_install worked for a while, and then stopped:

http://groups.google.com/group/beautifulsoup/browse_thread/thread/1509dd57309408e5

I have deleted the text/html tarball and used the fixed script to re-upload the tarball:

http://launchpad.net/beautifulsoup/trunk/3.2/+download/BeautifulSoup-3.2.0.tar.gz

Once again I've used wget to verify that the tarball is served as application/x-tgz. If it suddenly switches to text/html, I'll know this is a bug in the Launchpad librarian and not an artifact of a mistake I made on Friday.