Donovan Baarda <[EMAIL PROTECTED]> writes:
> I didn't think the new packages were using alternatives?
This is the first thing I checked:
chinon:~$ ls -al /usr/bin/python
lrwxr-xr-x1 root root 24 oct 16 12:14 /usr/bin/python ->
/etc/alternatives/python
>
> > > I discovered
Quoting Bruce Sass <[EMAIL PROTECTED]>:
> Hi,
>
> On 16 Oct 2001, Jérôme Marant wrote:
> <...>
> > I installed both python1.5 and python2.1. And installing both on the
> same
> > system broke _all_ my python 1.5 packages: this is the alternative
> issue
> > Perl people have warned us about.
Bastian Kleineidam writes:
> Jérôme Marant wrote:
>
> > I said previously that the upgrade when OK. This is true, but I hadn't
> > look
> > further at that moment.
>
>
> My upgrade had some errors:
No errors. The postinst just compiled the testsuite. Btw, do we really
need the testsuite as
Hi,
On 16 Oct 2001, Jérôme Marant wrote:
<...>
> I installed both python1.5 and python2.1. And installing both on the same
> system broke _all_ my python 1.5 packages: this is the alternative issue
> Perl people have warned us about.
>
> I discovered that /usr/bin/python is pointing to pyt
Jérôme Marant wrote:
I said previously that the upgrade when OK. This is true, but I hadn't look
further at that moment.
My upgrade had some errors:
File "/usr/lib/python2.1/test/nocaret.py", line 2
[x for x in x] = x
SyntaxError: can't assign to list comprehension
SyntaxError: from __futu
5 matches
Mail list logo