To be clear, I responded quickly and vocally only in case someone who
does run something
that would break would see it before actually breaking things horribly.
For many people that solution can work.
I've been regularly doing that on a zone I run in the JPC
that only really runs nginx and some node.js applications.
It started at 2012Q1 and is now on 2013Q4.
But that zone has no database and before doing those upgrades I always
back everything up
in a way that makes it easy to roll back if the upgrade doesn't go smoothly.
So, to second Renato's suggestion:
*IF* you don't have any applications that will break horribly,
and if you have good backups and are confident you could recover from pkgsrc
screwing up everything royally, then updating all your packages to the
latest pkgsrc
release is an option to consider.
Renato, I hope you can forgive my tone. I only wanted to protect others from
possibly breaking databases and becoming sad and/or angry.
-Nahum
On 04/10/2014 10:47 AM, renato morano wrote:
sorry :(
On 10 April 2014 16:46, renato morano <[email protected]> wrote:
I complain
On 10 April 2014 16:44, Nahum Shalman <[email protected]> wrote:
BE CAREFUL WITH THAT!!!
That is not necessarily safe if your zone runs, for example, Postgres.
Postgres minor version
upgrades break on-disk format compatibilty and pkgsrc doesn't do anything to
handle that
if you just switch which branch you're on like that.
For some zones that's okay, but I would never make that as a blanket
recommendation!
-Nahum
On 04/10/2014 10:42 AM, renato morano wrote:
vi /opt/local/etc/pkgin/repositories.conf
then
from http://pkgsrc.joyent.com/packages/SmartOS/^^2013Q1^^/i386/All
to
http://pkgsrc.joyent.com/packages/SmartOS/^^2013Q4^^/i386/All
you can find more information about pkgsrc on
http://pkgsrc.joyent.com/installing.html
:D
On 10 April 2014 16:30, Matthew Law <[email protected]> wrote:
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.
Thanks,
M.
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed:
https://www.listbox.com/member/archive/rss/184463/22541654-e1fbdf62
Modify Your Subscription: https://www.listbox.com/member/?&;
Powered by Listbox: http://www.listbox.com
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed:
https://www.listbox.com/member/archive/rss/184463/22541654-e1fbdf62
Modify Your Subscription:
https://www.listbox.com/member/?&;
Powered by Listbox: http://www.listbox.com
--
"<Free> as in free speech, not as in <free> beer." (RMS)
The more you do the more you own. (AL)
Run zpool scrub periodically and sleep more soundly
"Tutto ciò che si dona, ritorna..."
Renato Morano
cell.3284117069
-------------------------------------------
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
