pkg-1.3.0 fails to detect updated package (and other problems)

[Paul Mather]

On Jul 25, 2014, at 2:56 PM, Baptiste Daroussin <bapt at FreeBSD.org> wrote:

> On Fri, Jul 25, 2014 at 02:53:37PM -0400, Paul Mather wrote:
>> (Please Cc: any replies to me directly because I am not subscribed to 
>> this list.)
>> 
>> I've been using pkgng for quite a while now, largely in tandem with 
>> poudriere.  I build custom pkgng repositories for several systems and 
>> have been very, very happy with the setup.
>> 
>> The recent upgrade of pkg to 1.3 has caused a few problems.  I've also 
>> had to get used to a few new behaviours (like "pkg delete" offering to 
>> delete dependent packages rather than just refusing to do so unless you 
>> force it with "-f" or use "-R").
>> 
>> A minor problem I encountered is that "ENABLED: NO" in my repository 
>> .conf file no longer appears to disable the repository as it had done 
>> under pkg 1.2.  It wasn't until I used "enabled: no" that pkg 1.3 
>> considered the repository disabled.
>> 
>> The biggest problem I've encountered, however, is that "pkg upgrade" 
>> does not seem to recognise all the updates that are available.  I'm not 
>> sure whether this is a pkg problem or a poudriere problem.  (I'm 
>> currently running pkg 1.3.0 and poudriere 3.0.16.)  When I did a "pkg 
>> upgrade" on the client machine, it upgraded pkg from 1.2.7_4 to 1.3.0.  
>> For some reason, it complained about an "internal solver error" and 
>> also went through two rounds of updates (are the multiple rounds of 
>> updates to be expected with pkg 1.3?):
> 
[[... etc. ...]]

> pkg 1.3.1 is on the way to get released and fixes all the issues you are
> reporting (we hope so :))
> 
> I'm tracking a last bug (and yes this is compatible with poudriere 3.0.16


Thank you, that is great news!  I really appreciate pkg + poudriere, as 
it makes local package management and updating so much easier.  I also 
greatly appreciate how responsive pkgng development has been for those 
of us who have followed it from early on.  Thanks again!

Cheers,

Paul.