10. 4. 2014 v 16:30, Matthew Law <[email protected]>: > On Thu, April 10, 2014 11:38 am, Filip Hajny wrote: >> This part suggests that nothing happened at all - pkgin should have >> realized that the upstream database changed, and update the local one too. >> Can you try ‘pkgin -y -f up’ to force the update? >> >> Worst case, you can always ‘pkg_add -u openssl’ using the core canonical >> pkg_add tool. > > [root@myzone ~]# pkgin -y -f up > database for http://pkgsrc.joyent.com/packages/SmartOS/2013Q1/i386/All is > up-to-date > > [root@myzone ~]# pkgin -y -f install openssl > calculating dependencies... done. > nothing to do. > > I'm stumped by this. Any ideas? - I'd rather stick to the high level > tools if possible rather than using pkg_add, etc. >
You don’t have to afraid - pkg_add etc. are actually the canonical native tools that pkgsrc comes with. pkgin is just a 3rd party tool that we prefer in our docs because it allows you to search (among others). I’d say do it for the sake of having your system patched up. Unfortunately we’ve seen pkgin misperform way too often in this regard - i.e. not recognizing there’s an update upstream, especially in the older package sets. You can just tear down its database and re-sync: rm -f /var/db/pkgin/pkgin.db pkgin -y up The database contains meta information about package and there’s really no significant harm in recreating it from scratch over and over again. -F ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
