> >
> > > I'm not sure what to do. Here's a couple of solutions:
> > [...]
> > > 2) Only make a python1.5-kjbuckets package. (Nah.)
> > [...]
> > > 5) Use date in version, i.e. 2.2.port.20011104 or similar. (Best
> > >solution I ca
Le Sun, Nov 04, 2001 at 11:39:46PM +0100, Matthias Klose pianota:
> Denis writes:
> > we want to use Python >2.1 because of some different reasons
> > among which the need to use Zope 2.4
>
> >2.1 or >= 2.1 ?
You're right, >= 2.1
> > - on our production server, we still use Python 1.5 with Z
Donovan Baarda <[EMAIL PROTECTED]> writes:
> I would hope that you also make a python1.5-kjbuckets so that older
> python1.5 programs that used it can still use it. You them also make
> a python2.2-kjbuckets (2.2.0-port.20011104) package if you want
> something newer.
>
>
Denis writes:
> Hi all,
>
>
> I hope I may post this kind of message here (it's a user point
> of view) I don't know this list, I've just read a few threads
> up to now.
>
> Here, we're a bunch of Debian-Python users and we are a bit
> lost with the debian upgrade. What would be your best advice
Hi all,
I hope I may post this kind of message here (it's a user point
of view) I don't know this list, I've just read a few threads
up to now.
Here, we're a bunch of Debian-Python users and we are a bit
lost with the debian upgrade. What would be your best advice in
our situation :
we want to
> [...]
> > 2) Only make a python1.5-kjbuckets package. (Nah.)
> [...]
> > 5) Use date in version, i.e. 2.2.port.20011104 or similar. (Best
> >solution I can come up with.)
> [...]
>
> I would hope that you also make a python1.5-kjbuckets so that older
>
ons, but it's not as official as one could hope. For instance,
> the version number is still the same as the old upstream version
> (2.2).
>
> I'm not sure what to do. Here's a couple of solutions:
[...]
> 2) Only make a python1.5-kjbuckets package. (Nah.)
[...]
&
Joel Rosdahl writes:
> 5) Use date in version, i.e. 2.2.port.20011104 or similar. (Best
>solution I can come up with.)
but use something like 2.2.0.port.011104, so you don't need an epoch
for the next official 2.2.1 version.
ber bump.)
4) Use an epoch version, i.e. 1:2.2. (Ugh.)
5) Use date in version, i.e. 2.2.port.20011104 or similar. (Best
solution I can come up with.)
Opinions?
Regards,
Joel
[1] Found at: http://www.pythonpros.com/arw/kjbuckets/
[2] Available here: http://phd.pp.ru/Software/
Baruch Even writes:
> Hello,
>
> I've noticed that python package conflicts with LyX, I've also seen the
> discussion on the python policy but couldn't understand the exact
> reasons for this action and how to solve it.
>
> I'd appreciate some explanation, it is also a good idea to file bug
> rep
Hello,
I've noticed that python package conflicts with LyX, I've also seen the
discussion on the python policy but couldn't understand the exact
reasons for this action and how to solve it.
I'd appreciate some explanation, it is also a good idea to file bug
reports on all such conflicted packages
11 matches
Mail list logo
