pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Python (Multi) installation?
On Sun, 16 Sep 2018, Thomas Klausner wrote:
> On Sat, Sep 15, 2018 at 04:03:19PM -0500, John D. Baker wrote:
> > Could it be the failure to install python37 with an existing python36
> > was because the python36 install predated the availability of python37
> > and so raised a conflict?
> >
> > Perhaps explicitly rebuild/replace python36 early will remove conflict
> > when python37 is to be installed?
>
> All the python3 packages conflicted until
>
> revision 1.12
> date: 2017-12-13 13:56:10 +0100; author: jperkin; state: Exp; lines: +2 -1; commitid: oId3ftm4FnPzmJiA;
> python36: Disable libpython3.so.
>
> This is a useless library (we've built it incorrectly for a long time so it
> contains no valid symbols) that only creates CONFLICTS with other python3
> packages. No objection on tech-pkg. Bump PKGREVISION.
>
>
> Could it be that your installed package was built before that commit?
No. That system is my first-line crash-test dummy when building packages
and most recently updated everything as per pkgsrc-2018Q2. Alas, the
packages are gone now, so I can't verify the date stamps.
As the freeze for Q3 approaches, I'll fire off another system that
had also updated everything to pkgsrc-2018Q2 and see if it happens
again (python36-3.6.5nb1 built 13 July 2018).
Hmm. pkgsrc-HEAD has python36-3.6.6*, so perhaps that caused other
python3x-wanting packages to skip the installed python36-3.6.5 and demand
python37?
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Home |
Main Index |
Thread Index |
Old Index