Re: pkgtools/pkgin-0.9.3 issue?

[Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost>]

On 19 August 2015 at 13:25, Fredrik Pettai <pettai%nordu.net@localhost> wrote:
>
> On 18 Aug 2015, at 21:34 , Jonathan Perkin <jperkin%joyent.com@localhost> wrote:
>
>> * On 2015-08-17 at 18:23 BST, Matthias Ferdinand wrote:
>>
>>> since upgrading from pkgin-0.8.0 to 0.9.1 / 0.9.2, "pkgin av" only shows
>>>    Requested list is empty.
>>> and re-reading local and remote summary at each invocation.
>>>
>>> In /opt/pkgsrc/var/db/pkgin/sql.log I see lots of entries like
>>>    SQL error: near ")": syntax error
>>>    SQL query: );
>>>
>>> This not only happens on old Linux installs, but also on Ubuntu
>>> 12.04/14.04
>>
>> This should now be fixed in 0.9.3 which I've just committed to pkgsrc,
>> as well as a few other build fixes (e.g. it is now WARNS=4 clean on
>> Ubuntu 12.04).
>>
>> Please test (especially on other systems) and let me know of any
>> issues.
>
> Hi,
>
> So I updated pkgin to 0.9.3 and noticed this problem (see the space calculation):
>
> bash-4.3# uname -a
> NetBSD guineapig.nordu.net 7.0_RC3 NetBSD 7.0_RC3 (GENERIC.201508171550Z) amd64
>
> bash-4.3# grep -v "#" /usr/pkg/etc/pkgin/repositories.conf
> http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/7.0/All
>
> bash-4.3# pkgin fug
> calculating dependencies... done.
> libXfixes-5.0.1 (to be installed) conflicts with installed package Xfixes-2.0.1nb5.
> proceed ? [y/N] y
> pkgin: /usr/pkg does not have enough space for installation (11G required but only 2939M are available)
>                                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> bash-4.3# pkg_info | wc -l
>      392
>
> bash-4.3# du -sh /usr/pkg
> 857M    /usr/pkg
>
> It sounds odd that nearly ~1G of packages would grow to 11G then upgraded… but there might be a prebuilt package (or packages) that has become unreasonable large for some unknown reason…
>
> Re,
> /P

There's a thread of mine of a few months ago about this. I think pkgin
fug is a dangerous option in any case.

I'd rather suggest:

# pkgin update && pkgin autoremove && pkgin upgrade