--- python-dateutil-1.4.1.orig/debian/docs +++ python-dateutil-1.4.1/debian/docs @@ -0,0 +1,2 @@ +NEWS +README --- python-dateutil-1.4.1.orig/debian/changelog +++ python-dateutil-1.4.1/debian/changelog @@ -0,0 +1,64 @@ +python-dateutil (1.4.1-3ubuntu1) oneiric; urgency=low + + * Switch to dh_python2. (LP: #788514) + + -- Barry Warsaw Thu, 14 Jul 2011 14:36:13 -0400 + +python-dateutil (1.4.1-3) unstable; urgency=low + + * [95a66ef] depend on tzdata and update description + * [93fe8b9] don't depend on pysupport internals (Closes: #516907) - + thanks to Josselin Mouette for pointing this out and providing a fix + + -- Guido Günther Tue, 24 Feb 2009 22:30:33 +0100 + +python-dateutil (1.4.1-2) unstable; urgency=low + + * [a5de481] don't ship timezone information (Closes: #416204) + * [4f4aa5d] add README.source + * [174ea3e] bump standards version + + -- Guido Guenther Tue, 30 Sep 2008 18:49:25 +0200 + +python-dateutil (1.4.1-1) unstable; urgency=low + + * [292923b] New Upstream version 1.4.1 + * [abd914e] uscan: justs downloading is enough + + -- Guido Guenther Thu, 14 Aug 2008 08:44:02 +0200 + +python-dateutil (1.4-1) unstable; urgency=low + + * new upstream version + * add watch file from dehs.debian.org + * build-depend on python-setuptools + + -- Guido Guenther Wed, 12 Mar 2008 10:59:20 +0100 + +python-dateutil (1.3-1) unstable; urgency=low + + * New Upstream Version + + -- Guido Guenther Mon, 10 Dec 2007 10:10:42 +0100 + +python-dateutil (1.2-1) unstable; urgency=low + + * New Upstream Version + + -- Guido Guenther Sun, 05 Aug 2007 14:35:21 +0200 + +python-dateutil (1.1-1) unstable; urgency=low + + * new upstream version + * add pyversions file + * depend on python-all-dev instead of python-dev so we can build for all + currently supported python versions + + -- Guido Guenther Tue, 12 Sep 2006 14:52:14 +0200 + +python-dateutil (1.0-1) unstable; urgency=low + + * Initial release (Closes: #386256) + + -- Guido Guenther Wed, 6 Sep 2006 10:33:06 +0200 + --- python-dateutil-1.4.1.orig/debian/rules +++ python-dateutil-1.4.1/debian/rules @@ -0,0 +1,13 @@ +#!/usr/bin/make -f + +DEB_TAR_SRCDIR := python-dateutil +DEB_AUTO_CLEANUP_RCS := yes + +DEB_PYTHON_CLEAN_ARGS = --all + +include /usr/share/cdbs/1/rules/debhelper.mk +include /usr/share/cdbs/1/class/python-distutils.mk +include /usr/share/cdbs/1/rules/patchsys-quilt.mk + +install/python-dateutil:: + rm -f debian/python-dateutil/usr/lib/`pyversions -d`/site-packages/dateutil/zoneinfo/zoneinfo-*.tar.gz --- python-dateutil-1.4.1.orig/debian/compat +++ python-dateutil-1.4.1/debian/compat @@ -0,0 +1 @@ +5 --- python-dateutil-1.4.1.orig/debian/copyright +++ python-dateutil-1.4.1/debian/copyright @@ -0,0 +1,268 @@ +This package was debianized by Guido Guenther on +Wed, 6 Sep 2006 10:33:06 +0200. + +It was downloaded from http://labix.org/python-dateutil + +Upstream Author: Gustavo Niemeyer + +Copyright notice (as found in LICENSE in the original source). +-------------------------------------------------------------- + +A. HISTORY OF THE SOFTWARE +========================== + +Python was created in the early 1990s by Guido van Rossum at Stichting +Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands +as a successor of a language called ABC. Guido remains Python's +principal author, although it includes many contributions from others. + +In 1995, Guido continued his work on Python at the Corporation for +National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) +in Reston, Virginia where he released several versions of the +software. + +In May 2000, Guido and the Python core development team moved to +BeOpen.com to form the BeOpen PythonLabs team. In October of the same +year, the PythonLabs team moved to Digital Creations (now Zope +Corporation, see http://www.zope.com). In 2001, the Python Software +Foundation (PSF, see http://www.python.org/psf/) was formed, a +non-profit organization created specifically to own Python-related +Intellectual Property. Zope Corporation is a sponsoring member of +the PSF. + +All Python releases are Open Source (see http://www.opensource.org for +the Open Source Definition). Historically, most, but not all, Python +releases have also been GPL-compatible; the table below summarizes +the various releases. + + Release Derived Year Owner GPL- + from compatible? (1) + + 0.9.0 thru 1.2 1991-1995 CWI yes + 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes + 1.6 1.5.2 2000 CNRI no + 2.0 1.6 2000 BeOpen.com no + 1.6.1 1.6 2001 CNRI yes (2) + 2.1 2.0+1.6.1 2001 PSF no + 2.0.1 2.0+1.6.1 2001 PSF yes + 2.1.1 2.1+2.0.1 2001 PSF yes + 2.2 2.1.1 2001 PSF yes + 2.1.2 2.1.1 2002 PSF yes + 2.1.3 2.1.2 2002 PSF yes + 2.2.1 2.2 2002 PSF yes + 2.2.2 2.2.1 2002 PSF yes + 2.3 2.2.2 2002-2003 PSF yes + +Footnotes: + +(1) GPL-compatible doesn't mean that we're distributing Python under + the GPL. All Python licenses, unlike the GPL, let you distribute + a modified version without making your changes open source. The + GPL-compatible licenses make it possible to combine Python with + other software that is released under the GPL; the others don't. + +(2) According to Richard Stallman, 1.6.1 is not GPL-compatible, + because its license has a choice of law clause. According to + CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1 + is "not incompatible" with the GPL. + +Thanks to the many outside volunteers who have worked under Guido's +direction to make these releases possible. + + +B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON +=============================================================== + +PSF LICENSE AGREEMENT FOR PYTHON 2.3 +------------------------------------ + +1. This LICENSE AGREEMENT is between the Python Software Foundation +("PSF"), and the Individual or Organization ("Licensee") accessing and +otherwise using Python 2.3 software in source or binary form and its +associated documentation. + +2. Subject to the terms and conditions of this License Agreement, PSF +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python 2.3 +alone or in any derivative version, provided, however, that PSF's +License Agreement and PSF's notice of copyright, i.e., "Copyright (c) +2001, 2002 Python Software Foundation; All Rights Reserved" are +retained in Python 2.3 alone or in any derivative version prepared by +Licensee. + +3. In the event Licensee prepares a derivative work that is based on +or incorporates Python 2.3 or any part thereof, and wants to make +the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python 2.3. + +4. PSF is making Python 2.3 available to Licensee on an "AS IS" +basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.3 WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS +A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 2.3, +OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +6. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +7. Nothing in this License Agreement shall be deemed to create any +relationship of agency, partnership, or joint venture between PSF and +Licensee. This License Agreement does not grant permission to use PSF +trademarks or trade name in a trademark sense to endorse or promote +products or services of Licensee, or any third party. + +8. By copying, installing or otherwise using Python 2.3, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. + + +BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 +------------------------------------------- + +BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 + +1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an +office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the +Individual or Organization ("Licensee") accessing and otherwise using +this software in source or binary form and its associated +documentation ("the Software"). + +2. Subject to the terms and conditions of this BeOpen Python License +Agreement, BeOpen hereby grants Licensee a non-exclusive, +royalty-free, world-wide license to reproduce, analyze, test, perform +and/or display publicly, prepare derivative works, distribute, and +otherwise use the Software alone or in any derivative version, +provided, however, that the BeOpen Python License is retained in the +Software, alone or in any derivative version prepared by Licensee. + +3. BeOpen is making the Software available to Licensee on an "AS IS" +basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE +SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS +AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY +DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +5. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +6. This License Agreement shall be governed by and interpreted in all +respects by the law of the State of California, excluding conflict of +law provisions. Nothing in this License Agreement shall be deemed to +create any relationship of agency, partnership, or joint venture +between BeOpen and Licensee. This License Agreement does not grant +permission to use BeOpen trademarks or trade names in a trademark +sense to endorse or promote products or services of Licensee, or any +third party. As an exception, the "BeOpen Python" logos available at +http://www.pythonlabs.com/logos.html may be used according to the +permissions granted on that web page. + +7. By copying, installing or otherwise using the software, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. + + +CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 +--------------------------------------- + +1. This LICENSE AGREEMENT is between the Corporation for National +Research Initiatives, having an office at 1895 Preston White Drive, +Reston, VA 20191 ("CNRI"), and the Individual or Organization +("Licensee") accessing and otherwise using Python 1.6.1 software in +source or binary form and its associated documentation. + +2. Subject to the terms and conditions of this License Agreement, CNRI +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python 1.6.1 +alone or in any derivative version, provided, however, that CNRI's +License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) +1995-2001 Corporation for National Research Initiatives; All Rights +Reserved" are retained in Python 1.6.1 alone or in any derivative +version prepared by Licensee. Alternately, in lieu of CNRI's License +Agreement, Licensee may substitute the following text (omitting the +quotes): "Python 1.6.1 is made available subject to the terms and +conditions in CNRI's License Agreement. This Agreement together with +Python 1.6.1 may be located on the Internet using the following +unique, persistent identifier (known as a handle): 1895.22/1013. This +Agreement may also be obtained from a proxy server on the Internet +using the following URL: http://hdl.handle.net/1895.22/1013". + +3. In the event Licensee prepares a derivative work that is based on +or incorporates Python 1.6.1 or any part thereof, and wants to make +the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python 1.6.1. + +4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" +basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS +A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, +OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +6. This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +7. This License Agreement shall be governed by the federal +intellectual property law of the United States, including without +limitation the federal copyright law, and, to the extent such +U.S. federal law does not apply, by the law of the Commonwealth of +Virginia, excluding Virginia's conflict of law provisions. +Notwithstanding the foregoing, with regard to derivative works based +on Python 1.6.1 that incorporate non-separable material that was +previously distributed under the GNU General Public License (GPL), the +law of the Commonwealth of Virginia shall govern this License +Agreement only as to issues arising under or with respect to +Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this +License Agreement shall be deemed to create any relationship of +agency, partnership, or joint venture between CNRI and Licensee. This +License Agreement does not grant permission to use CNRI trademarks or +trade name in a trademark sense to endorse or promote products or +services of Licensee, or any third party. + +8. By clicking on the "ACCEPT" button where indicated, or by copying, +installing or otherwise using Python 1.6.1, Licensee agrees to be +bound by the terms and conditions of this License Agreement. + + ACCEPT + + +CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 +-------------------------------------------------- + +Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, +The Netherlands. All rights reserved. + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation, and that the name of Stichting Mathematisch +Centrum or CWI not be used in advertising or publicity pertaining to +distribution of the software without specific, written prior +permission. + +STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO +THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE +FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT +OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. --- python-dateutil-1.4.1.orig/debian/control +++ python-dateutil-1.4.1/debian/control @@ -0,0 +1,31 @@ +Source: python-dateutil +Section: python +Priority: optional +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Guido Guenther +Build-Depends: cdbs (>= 0.4.90~), debhelper (>= 5), quilt, python-all-dev (>= 2.6.6-3~), python-setuptools +Standards-Version: 3.8.0 +XS-Vcs-Git: git://git.debian.org/git/calendarserver/python-dateutil.git +XS-Vcs-Browser: http://git.debian.org/?p=calendarserver/python-dateutil.git +X-Python-Version: >= 2.3 + +Package: python-dateutil +Architecture: all +Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}, tzdata +Description: powerful extensions to the standard datetime module + It features: + . + * computing of relative deltas (next month, next year, next monday, last week + of month, etc); + * computing of relative deltas between two given date and/or datetime objects + * computing of dates based on very flexible recurrence rules, using a superset + of the iCalendar specification. Parsing of RFC strings is supported as well. + * generic parsing of dates in almost any string format + * timezone (tzinfo) implementations for tzfile(5) format files + (/etc/localtime, /usr/share/zoneinfo, etc), TZ environment string (in all + known formats), iCalendar format files, given ranges (with help from + relative deltas), local machine timezone, fixed offset timezone, UTC + timezone + * computing of Easter Sunday dates for any given year, using Western, Orthodox + or Julian algorithms + --- python-dateutil-1.4.1.orig/debian/examples +++ python-dateutil-1.4.1/debian/examples @@ -0,0 +1 @@ +example.py --- python-dateutil-1.4.1.orig/debian/README.source +++ python-dateutil-1.4.1/debian/README.source @@ -0,0 +1,6 @@ +Building python-dateutil for Debian +----------------------------------- + +The python-dateutil source package uses quilt to apply and remove its patches. +Please refer to /usr/share/doc/quilt/README.source for information about how to +use quilt for source packages. --- python-dateutil-1.4.1.orig/debian/watch +++ python-dateutil-1.4.1/debian/watch @@ -0,0 +1,3 @@ +version=3 +opts=uversionmangle=s/\.(tar.*|tgz|zip|gz|bz2)$//i,dversionmangle=s/[-.+~]?(cvs|svn|git|snapshot|pre|hg)(.*)$//i,pasv \ +http://labix.org/python-dateutil (?:.*/)?python-dateutil-?_?([\d+\.]+|\d+)\.(tar.*|tgz|zip|gz|bz2|) --- python-dateutil-1.4.1.orig/debian/patches/series +++ python-dateutil-1.4.1/debian/patches/series @@ -0,0 +1 @@ +fix_locale.diff --- python-dateutil-1.4.1.orig/debian/patches/fix_locale.diff +++ python-dateutil-1.4.1/debian/patches/fix_locale.diff @@ -0,0 +1,13 @@ +Index: python-dateutil/example.py +=================================================================== +--- python-dateutil.orig/example.py 2006-09-06 13:21:44.000000000 +0200 ++++ python-dateutil/example.py 2006-09-06 13:21:56.000000000 +0200 +@@ -5,7 +5,7 @@ + from datetime import * + import commands + import os +-now = parse(commands.getoutput("date")) ++now = parse(commands.getoutput("LC_ALL=C date")) + today = now.date() + year = rrule(YEARLY,bymonth=8,bymonthday=13,byweekday=FR)[0].year + rdelta = relativedelta(easter(year), today)