On Fri 04 Oct 2019 at 19:33:53 -0400, Bob Bernstein wrote:
> On Fri, Oct 04, 2019 at 12:42:44PM +0200, Rhialto wrote:
>
> > So something weird may be going on.
>
> I would give assent to that speculation.
>
> > The package that adds
> > /usr/pkg/lib/perl5/vendor_perl/5.28.0/LWP.pm is
> > p5-l
On Fri, Oct 04, 2019 at 12:42:44PM +0200, Rhialto wrote:
> So something weird may be going on.
I would give assent to that speculation.
> The package that adds
> /usr/pkg/lib/perl5/vendor_perl/5.28.0/LWP.pm is
> p5-libwww-6.39.
I used this hint to solve (apparently) the problem of the
missi
On Thu 03 Oct 2019 at 22:59:21 -0400, Bob Bernstein wrote:
> A series of misadventures that began nicely enough with a
> successful cvs up of my pkgsrc tree, followed by an uneventful
> run of pkg_rolling-update has however left me with a new perl5, as
> noted ver. 5.30.0, that appears not to ha
A series of misadventures that began nicely enough with a
successful cvs up of my pkgsrc tree, followed by an uneventful
run of pkg_rolling-update has however left me with a new perl5, as
noted ver. 5.30.0, that appears not to have finished its build.
My attention was aroused when I tried what
A series of misadventures that began nicely enough with a
successful cvs up of my pkgsrc tree, followed by an uneventful
run of pkg_rolling-update has however left me with a new perl5, as
noted ver. 5.30.0, that appears not to have finished its build.
My attention was aroused when I tried what
