On Mon, Sep 21, 2009 at 21:51 +0200, Toni Mueller wrote:
> On Mon, 21.09.2009 at 12:13:46 +0200, Wolodja Wentland
> wrote:
Note
Let me first say one thing.
I actually planned to write a big "thank you for the discussion" mail
this evening, because I really had the feeling that I as
Hi,
On Mon, 21.09.2009 at 12:13:46 +0200, Wolodja Wentland
wrote:
> Hmmm, no. Python applications that need a specific version of Python
> should use
>
> #!/usr/bin/env pythonX.Y
>
> or
>
> #!/usr/bin/pythonX.Y
>
> stating that they need this specific version of Python.
how else is
On Mon, Sep 21, 2009 at 14:07 +0200, Siegfried Gevatter wrote:
> 2009/9/21 Josselin Mouette :
> >> Maybe the applications
> >> using /usr/bin/env should get a bug filled, I agree with that.
> Can someone explain again what is it that we are gong to gain by
> patching like 50% of all applications?
On Sun, Sep 20, 2009 at 01:34:24PM +0200, Matthias Klose wrote:
> On 02.07.2009 13:05, Jonas Meurer wrote:
>> why not wait for zope2.12 with python2.5/2.6 support, upload that one to
>> debian/unstable and afterwards file a request for removal for
>> zope2.10/zope2.11/python2.4? I believe that a zo
2009/9/21 Josselin Mouette :
>> Maybe the applications
>> using /usr/bin/env should get a bug filled, I agree with that.
Can someone explain again what is it that we are gong to gain by
patching like 50% of all applications?
--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer
Le lundi 21 septembre 2009 à 08:36 +0100, Floris Bruynooghe a écrit :
> This is indeed desired and the policy says to use /usr/bin/python, for
> reasons explained in this thread already. Maybe the applications
> using /usr/bin/env should get a bug filled, I agree with that.
Given their number, t
On Mon, Sep 21, 2009 at 08:36 +0100, Floris Bruynooghe wrote:
> On Mon, Sep 21, 2009 at 12:35:19AM +0200, Wolodja Wentland wrote:
> > On Sun, Sep 20, 2009 at 22:18 +0200, Bernd Zeimetz wrote:
> > > Wolodja Wentland wrote:
>> I really don't get it. How could it possibly be better to have a
>> wild
Trac for sure. Is there any _short_ howto about Debian backports for
Python folks?
--anatoly t.
On Mon, Sep 21, 2009 at 2:54 AM, W. Martin Borgert wrote:
> Hi,
>
> for some reasons I need lenny backports of python-django,
> python-webpy and trac. Some of the packages I don't need for
> "produc
hey,
On 20/09/2009 Matthias Klose wrote:
> On 20.09.2009 16:45, Jonas Meurer wrote:
> >if i got it right then packaging the dependencies as seperate packages
> >isn't an option for zope2.12, we'll have to include them within the
> >zope2.10 source tarball. the reason for that is, that zope2.12 req
[Toni Mueller, 2009-09-21]
> Unmet build dependencies: debhelper (>= 7.0.50) python-sphinx
python-sphinx is already backported (for Pylons users who have all the
backports available in bpo or [1] and soon will have pylons.debian.net
with some docs/warnings)
[1] http://people.debian.org/~piotr/len
Hi,
On Mon, 21.09.2009 at 01:54:13 +0200, W. Martin Borgert
wrote:
> for some reasons I need lenny backports of python-django,
I could make use of python-django 1.1 in Lenny. Until I have a
backport, I'll need to install it locally.
> Is someone interested in doing the backports? :~)
I brief
On Mon, Sep 21, 2009 at 12:35:19AM +0200, Wolodja Wentland wrote:
> On Sun, Sep 20, 2009 at 22:18 +0200, Bernd Zeimetz wrote:
> > Wolodja Wentland wrote:
>
> [ placed on top because this is the main point ]
>
> > > If however the *env python scheme is enforced in the policy the problems
> > > I o
12 matches
Mail list logo
