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

python-tornado_2.3-2~bpo60+1_multi.changes is NEW



(new) python-tornado_2.3-2~bpo60+1.debian.tar.gz optional web
(new) python-tornado_2.3-2~bpo60+1.dsc optional web
(new) python-tornado_2.3-2~bpo60+1_all.deb optional web
scalable, non-blocking web server and tools
 Tornado is an open source version of the scalable, non-blocking
 web server and tools that power FriendFeed. The FriendFeed application
 is written using a web framework that looks a bit like web.py or
 Google's webapp, but with additional tools and optimizations to take
 advantage of the underlying non-blocking infrastructure.
(new) python-tornado_2.3.orig.tar.gz optional web


Changes:
python-tornado (2.3-2~bpo60+1) squeeze-backports; urgency=low
 .
  * Rebuild for squeeze-backports.
  * Don't build python3-tornado package.
 .
python-tornado (2.3-2) unstable; urgency=low
 .
  * debian/control
    - Replaced the python3.2 in the Depends field of python3-tornado
      by $(python3:Depends)
  * Renamed python-tornado.examples to examples
  * Removed python3-tornado.examples
 .
python-tornado (2.3-1) unstable; urgency=low
 .
  [ Julian Taylor ]
  * Team upload
  * new upstream release
    - change debian/watch to download section instead of tag tarballs
      tag tarball contain lots of unnecessary website and test data
    - drop upstream applied CVE-2012-2374.patch
    - refresh patches
    - closes LP: #998615
  [ Carl Chenet]
  * debian/control
    - Replaced chaica@ohmytux.com by chaica@debian.org
    - Replace (python3:Depends) in python3-tornado Depends field
      because of https://github.com/facebook/tornado/issues/450
    - Modified the short description of python3-tornado package
  * Renamed examples to python-tornado.examples
  * Added python3-tornado.examples
 .
python-tornado (2.1.0-3) unstable; urgency=high
 .
  [ Julian Taylor ]
  * Team upload
  * bump X-Python-Version to >= 2.6
    lower versions require arch any for custom epoll extension
  * move to Section: web (Closes: #665854)
    - override lintian wrong-section-according-to-package-name
  * CVE-2012-2374.patch adopted from upstream's GIT (Closes: #673987)
 .
python-tornado (2.1.0-2) unstable; urgency=low
 .
  [ Thomas Kluyver ]
  * Package for Python 3 (Closes: #653643)
 .
  [ Julian Taylor ]
  * make packages arch all
  * debian/control
    - wrap-and-sort fields
  * remove unnecessary Dependencies and Breaks
  * convert copyright to dep5
  * bump standard to 3.9.3 (no changes)
 .
python-tornado (2.1.0-1) unstable; urgency=low
 .
  * Team upload
  * New upstream release (Closes: #636602)
  * Refreshed patches
  * Updated debian/copyright
  * Added myself to uploaders to have bugs closed with uploads
 .
python-tornado (1.2.1-1) unstable; urgency=low
 .
  * New upstream release
  * debian/control
    - Bump Standards-Version to 3.9.2
 .
python-tornado (1.2.0-1) unstable; urgency=low
 .
  * New upstream release.
  * Added debian/examples
  * Added patch to ignore ca-certificates.crt from sources
  * Added patch to look for ca-certificates.crt at the right place
  * debian/copyright
    - Added copyrights and license for some files
    - some files no more in the upstream sources
  * debian/control
    - Removed python-support
    - Replaced XS-Python-Version by X-Python-Version
    - Added Breaks: ${python:Breaks}
    - Added Recommends: python (>= 2.6) | python-multiprocessing
    - Added Depends: ca-certificates
  * debian/rules
    - Replaced dh $@ by dh $@ --with python2
  * debian/watch
    - fixed the path


Override entries for your package:

Announcing to debian-backports-changes@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.
ion wrong.  You'll get warnings above
if files already exist in other distributions.


Reply to: