Yo James!
I doubt anyone here knows ebuilds. All yours.
On Thu, 31 Jan 2019 20:15:53 -0800
James Browning via devel wrote:
> On 1/31/19, Gary E. Miller via devel wrote:
> > Yes. But not done. It likely broke the current Gentoo NTPsec
> > ebuild for git head.
>
> I have a patch for that.
On 1/31/19, Gary E. Miller via devel wrote:
> Yes. But not done. It likely broke the current Gentoo NTPsec ebuild
> for git head.
I have a patch for that.
--- a/net-misc/ntpsec/ntpsec-1.1.2.ebuild
+++ b/net-misc/ntpsec/ntpsec-1.1.2.ebuild
@@ -28,11 +28,11 @@ NTPSEC_REFCLOCK=(
shm pps
Yo Hal!
On Thu, 31 Jan 2019 17:38:45 -0800
Hal Murray via devel wrote:
> Gary said:
> > To refresh your memory, the python module version checks are new.
> > That broke casual multiple python side-by-side installs.
>
> It also exposed a potential bug.
Yes, a great thing.
> If you change t
Gary said:
> To refresh your memory, the python module version checks are new.
> That broke casual multiple python side-by-side installs.
It also exposed a potential bug. If you change the API to a module and forget
to install the other version you can get confusion.
--
These are my opinio
Yo Hal!
On Wed, 30 Jan 2019 19:46:32 -0800
Hal Murray via devel wrote:
> Gary said:
> > The ntpsec ebuild for Gentoo installs multiple python modules. I
> > wonder if this recent change broke that?
>
> I don't remember any recent changes in the install area.
To refresh your memory, the pyth
Gary said:
> The ntpsec ebuild for Gentoo installs multiple python modules. I wonder if
> this recent change broke that?
I don't remember any recent changes in the install area.
The change was to add version checking. It has pointed out a real problem
with separate locations for python2 and
Yo Hal!
On Wed, 30 Jan 2019 18:33:21 -0800
Hal Murray via devel wrote:
> Gary said:
> > I installed for Python 2.7, then I installed for Python 3.6. Then
> > I ran with python3.6, but my PYTHONPAATH was still for 2.7.
>
> Do typical installations run mixed python 2 and 3 like that, or is
>
Gary said:
> I installed for Python 2.7, then I installed for Python 3.6. Then I ran with
> python3.6, but my PYTHONPAATH was still for 2.7.
Do typical installations run mixed python 2 and 3 like that, or is that only
used for testing?
---
I think the mixed case can be made to work with
Yo James!
On Wed, 30 Jan 2019 17:29:24 -0800
James Browning via devel wrote:
> On 1/30/19, Gary E. Miller via devel wrote:
> > Yo James!
> >
> > On Wed, 30 Jan 2019 14:57:15 -0800
> > James Browning via devel wrote:
> >
> >> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch"
>
On 1/30/19, Gary E. Miller via devel wrote:
> Yo James!
>
> On Wed, 30 Jan 2019 14:57:15 -0800
> James Browning via devel wrote:
>
>> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch" this
>> is what happens when you have multiple versions of pylib/ installed
>> and only one versi
Yo James!
On Wed, 30 Jan 2019 14:57:15 -0800
James Browning via devel wrote:
> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch" this
> is what happens when you have multiple versions of pylib/ installed
> and only one version of ntpclients/.
OK, but I'm not sure why you specify
Yo Hal!
On Wed, 30 Jan 2019 14:00:35 -0800
Hal Murray wrote:
> Gary said:
> > Great, the python library mismatch code works:
> > Library/Binary version mismatch
> > Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
> > Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev
On 1/30/19, Hal Murray via devel wrote:
>
> Gary said:
>> Great, the python library mismatch code works:
>> Library/Binary version mismatch
>> Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
>> Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev ab0ea27cf)
>
> What did
Gary said:
> Great, the python library mismatch code works:
> Library/Binary version mismatch
> Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
> Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev ab0ea27cf)
What did you do to get that?
The version strings come fro
14 matches
Mail list logo