No luck. Should upgrading from one repo to the next work (and is it supported)?
[root@shoe /opt/local/etc]# pkgin fug calculating dependencies... done. pkgin: scmgit-base-1.7.9.3 has no associated repository [root@shoe /opt/local/etc]# pkg_delete scmgit-base-1.7.9.3 pkg_delete: No matching package for basename `scmgit-base-1.7.9.3' of `scmgit-base-1.7.9.3' [root@shoe /opt/local/etc]# pkg_delete scmgit-base pkg_delete: No matching package for basename `scmgit-base' of `scmgit-base' [root@shoe /opt/local/etc]# It seems like the real packages are gone, but “pkgin” is just referencing some old stale data? Where is this data stored? On Jun 1, 2014, at 8:32 AM, Filip Hajny <[email protected]> wrote: > 1. 6. 2014 v 16:27, Anil Jangity via smartos-discuss > <[email protected]>: > >> I am upgrading from an older repo (from 2012) to a newer one (2014Q1). >> >> [root@shoe /var/log]# pkgin fug >> calculating dependencies... done. >> pkgin: scmgit-base-1.7.9.3 has no associated repository >> [root@shoe /var/log]# >> > > Yes, things like that are just bound to happen if you try to upgrade an > existing VM to a newer pkgsrc set. > >> [root@shoe /var/log]# pkgin list |grep scmgit >> scmgit-base-1.7.9.3 GIT Tree History Storage Tool (base package) >> >> (I think when I ran the rm earlier, it *did* remove the files, but my guess >> is, the package metadata is still stuck around somewhere. That’s why it >> still shows up) > > You’ll have to use the standard core tools here I guess. Try `pkg_delete > scmgit-base` and `pkgin -f up` to force a full update of the pkgin meta db. > > -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
