[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#543118: marked as done (ITP: python-cloudfiles -- Python interface to Rackspace CloudFiles service)

Your message dated Sat, 13 Nov 2010 14:17:01 -0600
with message-id <4CDEF23D.1060100@pbandjelly.org>
and subject line 
has caused the Debian Bug report #543118,
regarding ITP: python-cloudfiles -- Python interface to Rackspace CloudFiles service
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
543118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543118
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Michael Shuler <michael@pbandjelly.org>

  Package name    : python-cloudfiles
  Version         : 1.4.0
  Upstream Author : Cloud Files <cloudfiles@rackspacecloud.com>
  URL             : http://github.com/rackspace/python-cloudfiles/
  License         : MIT
  Programming Lang: Python
  Description     : Python interface to Rackspace Cloud Files service

python-cloudfiles provides a simple interface to the Rackspace Cloud Files
service. "Cloud Files is reliable, scalable and affordable web-based
storage for backing up and archiving all your static content". Find out
more at <http://www.rackspacecloud.com/cloud_hosting_products/files>.

To use this module you will need to sign up to Rackspace Cloud Files and
provide a "user" and "key". If you use this module, you will incurr costs
as specified by Rackspace. Please check the costs. If you use this module
with your user and key you will be responsible for these costs.

(This module will be maintained under the Debian Python Modules Team)

--- End Message ---
--- Begin Message --- Closing ITP without packaging. While upstream will continue API backward compatibility, upstream is moving to a larger community project; names will change (again), etc. - see openstack.org 

--
Michael

--- End Message ---
Reply to: