From owner-freebsd-ports@FreeBSD.ORG  Wed Jun 26 01:48:07 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 2A76B6D2
 for <ports@freebsd.org>; Wed, 26 Jun 2013 01:48:07 +0000 (UTC)
 (envelope-from amurphy@gsoft.com.au)
Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10])
 by mx1.freebsd.org (Postfix) with ESMTP id A2F0410B8
 for <ports@freebsd.org>; Wed, 26 Jun 2013 01:48:06 +0000 (UTC)
Received: from [127.0.0.1] (Zia.gsoft.com.au [203.31.81.56])
 (authenticated bits=0)
 by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r5Q1lrWP072463
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Wed, 26 Jun 2013 11:17:54 +0930 (CST)
 (envelope-from amurphy@gsoft.com.au)
Message-ID: <51CA485C.1040505@gsoft.com.au>
Date: Wed, 26 Jun 2013 11:18:12 +0930
From: Adrian Murphy <amurphy@gsoft.com.au>
User-Agent: Mozilla/5.0 (Windows NT 6.0;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ports@freebsd.org
Subject: pkg & portmaster
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.55 () ALL_TRUSTED,BAYES_00,RP_MATCHES_RCVD
X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 01:48:07 -0000

Hi,

I noticed portmaster developed a problem after a recent update to 
ports-mgmt/pkg where the following appears in the output:

[: false: bad number

I traced it to lines in portmaster where np_orphan is set:

np_orphan=`pkg query "%a" $upg_port`

It appears 'pkg query "%a"' used to return 0 or 1 and now it returns 
'true' or 'false'.

The 'pkg help query' text says "%a  Returns 1 if the matched package is 
an orphan package and can be pkg-autoremove(1)'d, 0 otherwise"


I further ran into trouble with ports-mgmt/pkg-devel today where 
portmaster calls:
    pkg info pkg

This fails with ports-mgmt/pkg-devel unless the line is changed to:
    pkg info pkg-devel

This stopped portmaster from working.

I reverted to using ports-mgmt/pkg to get around this.

Regards, Adrian