I've downgraded tar using snapshot:
http://snapshot.debian.net/archive/2006/04/16/debian/pool/main/t/tar/
And I've implemented Josselin's suggestions:
http://hendry.iki.fi/debian/unstable/webpy_0.138-2_i386.changes
sam$ lintian webpy_0.138-2_i386.changes
W: webpy source: build-depends-without-arc
http://hendry.iki.fi/debian/unstable/webpy_0.138-2_i386.changes
I had another go with policy, though I can't run it through lintian atm
due to a broken tar(#375300).
Could someone please check over the diff?
http://hendry.iki.fi/debian/unstable/webpy_0.138-2.diff.gz
If it's good, it could serve
On 2006-06-19T09:45+0200 Matthias Klose wrote:
> flup was probably built with python as found in experimental.
It was built on unstable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
thing.
- Forwarded message from Kai Hendry <[EMAIL PROTECTED]> -----
From: Kai Hendry <[EMAIL PROTECTED]>
To: Fabio Tranchitella <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], Sanghyeon Seo <[EMAIL PROTECTED]>
Subject: Re: New webpy for sponsored upload
Date: Sun, 18 Jun 2006
http://hendry.iki.fi/debian/unstable/flup_0.2015-1_i386.changes
sam$ sudo dpkg -i python-flup_0.2015-1_all.deb
(Reading database ... 133811 files and directories currently installed.)
Preparing to replace python-flup 0.1968-1 (using python-flup_0.2015-1_all.deb)
...
Unpacking replacement python-f
Ok, I've had python-support from http://wiki.debian.org/DebianPythonFAQ
pointed out to me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
transition is going to take a long time, then I guess I'll
have to.
Best wishes,
- Forwarded message from Kai Hendry <[EMAIL PROTECTED]> -----
From: Kai Hendry <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: feedparser
Date: Sun, 7 May 2006 23:44:54 +0900
Reply-To: Kai Hend
On 2006-02-04T10:13+0900 Sanghyeon Seo wrote:
> # Python distutils script for Debian package
> # Seo Sanghyeon
>
> from distutils.core import setup
> setup(packages=[
> 'simpleparse',
> 'simpleparse.common',
> 'simpleparse.xml',
> ])
>
> That's all.
>
> setup.py is a good idea in
and that setup.py in sync. Argh!
I'm not even sure *where* and *what* setup.py does with this values like
keywords, platforms and classifiers *on a Debian system*. I think they
aren't necessary, so can I do without it?
----- Forwarded message from Kai Hendry <[EMAIL PROTECTED]> -
Arg! Yes there is a rogue re.pyc in there.
It was very very dangerous(yes, and silly) to name my initial re
experimentation file re.py.
Sorry for wasting your time,
-Kai
On Sun, Nov 10, 2002 at 10:11:19PM +1100, Andrew Bennetts wrote:
> Is there a file called "re.pyc" in the same directory as
test.py is:
import re
p = re.compile('[a-z]+')
print p
The first error message is from python2.1, python2.2 and last
python2.3 from SID.
I think this is a serious packaging error, as it works on [GCC 2.96
2731 (Red Hat Linux 7.2 2.96-109)] on linux2
Regards,
-Kai Hendry
[EMAIL
11 matches
Mail list logo