I'm trying to build and install security/openssh-portable, but when I
do, make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0 or
greater, but you have 1.5.6. You must upgrade the ports-mgmt/pkg port first.
*** Error code 1
Stop.
make: stopped in /usr/ports/sec
On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim
wrote:
> I'm trying to build and install security/openssh-portable, but when I do,
> make errors out with:
>
> ===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0 or greater,
> but you have 1.5.6. You must upgrade the ports-mgmt/pkg port fir
On 2015-09-28 21:31, Kevin Oberman wrote:
On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim
wrote:
I'm trying to build and install security/openssh-portable, but when I do,
make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0 or greater,
but you have 1.5.6. You must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 09/29/2015 02:12 AM, Mel Pilgrim wrote:
> On 2015-09-28 21:31, Kevin Oberman wrote:
>> On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim
>> wrote:
>>
>>> I'm trying to build and install security/openssh-portable, but
>>> when I do, make error
On 2015-09-29 08:24, Janky Jay, III wrote:
I ran into this exact same issue using SVN and portmaster to upgrade
'git'. Upgrading 'pkg' using portmaster (portmaster -d 'pkg-1.5.6')
before running 'portmaster -ad' fixed the issue. Generally, though,
portmaster usually updates pkg first and
On 29/09/2015 21:34, Mel Pilgrim wrote:
> The ports system was changed to make mandatory a version of pkg that was
> not available by the default method. That's a POLA violation, but it
> appears no one wants to talk about it.
To turn that around, why are you mixing pkgs from a quarterly branch
w
Matthew Seaman wrote:
> To turn that around, why are you mixing pkgs from a quarterly branch
> with ports compiled from head? If you use ports/pkgs from a consistent
> source then you won't suffer from this problem.
There are many reasons to use ports and many to use packages. These reasons
are
On Tue, Sep 29, 2015 at 01:34:23PM -0700, Mel Pilgrim wrote:
> On 2015-09-29 08:24, Janky Jay, III wrote:
> > I ran into this exact same issue using SVN and portmaster to upgrade
> > 'git'. Upgrading 'pkg' using portmaster (portmaster -d 'pkg-1.5.6')
> > before running 'portmaster -ad' fixed th
Baptiste Daroussin writes:
> The change that was made was having the default packages on releases point to
> quarterly branch of the ports tree. This was noted in the release note.
Yes, but that really only helps people who already understand version
control. I'll try to come up with some text t
For the vast majority of ports and packages it won't make any difference
whether they are installed are from head, quarterly and/or archives (in my
experience, options dependencies aside). Isn't the issue here a dependency on
the version of 'pkg' being enforced by 'pkg'? If so shouldn't this be f
"Roger Marquis" writes:
> For the vast majority of ports and packages it won't make any difference
> whether they are installed are from head, quarterly and/or archives (in my
> experience, options dependencies aside). Isn't the issue here a dependency on
> the version of 'pkg' being enforced by
I just went to svnweb.freebsd.org with Firefox web browser, and see the
difference with branches of ports and base.
I clicked on ports, then branches, then 2015Q3, then ports-mgmt, and see that
the version of pkg is 1.5.6.
But I use only the head branch.
Quarterly ports branches are comparable
On 2015-09-30 16:16, Lowell Gilbert wrote:
In short, there is nothing broken in pkg(8) per se. I am pretty sure
this problem does not come up if you do everything from quarterly or
everything from head; it's strictly an issue of conflicts between the
two.
More to the point, that using the defau
On 10/1/2015 3:28 AM, Mel Pilgrim wrote:
> On 2015-09-30 16:16, Lowell Gilbert wrote:
>> In short, there is nothing broken in pkg(8) per se. I am pretty sure
>> this problem does not come up if you do everything from quarterly or
>> everything from head; it's strictly an issue of conflicts between
14 matches
Mail list logo
