Re: Maintaining your system with snapshots
On Sat, 21 Feb 2015 12:22:34 + (UTC) Stuart Henderson wrote: (exception being if I want to save packages that match a snapshot I've installed on a number of systems). I do that for offline systems. For online systems where I know which packages I want then I use PKG_CACHE and check all packages install on one system (in sync with base) and copy the packages to the others. Stu's previous tip can be useful pkg_info -q previously_installed.txt pkg_delete -X /usr/bin/env PKG_CACHE=/usr/ports/write/packages pkg_add -zl previously_installed.txt Though for some reason I have had to manually install gnome-icon-theme the last twice or so.
Re: Maintaining your system with snapshots
On 2015-02-21, Stuart Henderson s...@spacehopper.org wrote: Do you mean that you have mirrored a complete snapshots/packages/(arch) locally to use as a source for pkg_add? If so, make sure your mirror is all from the same package snapshot. Basically, check that dates on the upstream mirror are consistent and use something like rsync -yav --delete to fetch/update the whole directory. You can also use the SHA256.sig file. -- Christian naddy Weisgerber na...@mips.inka.de
Re: Maintaining your system with snapshots
On 2015-02-20, lm l...@redabierta.es wrote: I've got a local copy of the complete packages tree for convenience, so I don't have to update base and ports everytime I want to install a new package, but it still seems some packages don't match the base system and they crash. Do you mean that you have mirrored a complete snapshots/packages/(arch) locally to use as a source for pkg_add? If so, make sure your mirror is all from the same package snapshot. Basically, check that dates on the upstream mirror are consistent and use something like rsync -yav --delete to fetch/update the whole directory. I don't do this myself though, I prefer to just update my system if I run into a mismatch. (exception being if I want to save packages that match a snapshot I've installed on a number of systems).
Re: Maintaining your system with snapshots
On 2015-02-20, jungle Boogie jungleboog...@gmail.com wrote: On 20 February 2015 at 07:38, trondd tro...@gmail.com wrote: It is so quick and easy to update to another snapshot, if I find a package that doesn't work, I simply update to the latest snapshot. If you are on -current but you haven't updated in many, many snapshot cycles, do you update current or just get the latest snapshot? By updating current, I mean getting source from CVS: cvs -q up -Pd Use the snapshot. Source updates are more likely to require manual intervention.
Re: Maintaining your system with snapshots
On Fri, Feb 20, 2015 at 10:19:41AM +0100, lm wrote: I'm giving a try to snapshots for the first time. The system feels great, but I'm having some issues trying to maintain base system and ports synced. packages for releases and snapshots are built separately. mixing snapshot (-current) packages with stable or release versions is not supported (libraries and other dependencies are likely to not match). I've got a local copy of the complete packages tree for convenience, so I don't have to update base and ports everytime I want to install a new package, but it still seems some packages don't match the base system and they crash. at most times you can upgrade to a new snapshot and afterwards run pkg_add -u to update installed packages. Assuming, of course your PKG_PATH environment variable is set to something sensible. How do you maintain your system fresh? What do you follow? Primarily, read the FAQ. It links to the runnning -current document, which has a lot of handy tips for avoiding bad breakage (in most cases the chance of bad breakage is small, but do read the thing). As for works for me guides, my (by now somewhat dated) blog post [1] may still be useful despite needing some updates (such as don't bother running sysmerge with those arguments anymore (actually don't use any arguments to sysmerge in most cases), and hold off doing that until after you've booted into the new system, and likely other nits I may possibly address in the near future). - Peter [1] http://bsdly.blogspot.no/2012/07/keeping-your-openbsd-system-in-trim.html -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Maintaining your system with snapshots
On 20 February 2015 at 07:38, trondd tro...@gmail.com wrote: It is so quick and easy to update to another snapshot, if I find a package that doesn't work, I simply update to the latest snapshot. If you are on -current but you haven't updated in many, many snapshot cycles, do you update current or just get the latest snapshot? By updating current, I mean getting source from CVS: cvs -q up -Pd It's still less time lost than rebuilding the packages locally. Tim. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: Maintaining your system with snapshots
On 2/20/15, jungle Boogie jungleboog...@gmail.com wrote: If you are on -current but you haven't updated in many, many snapshot cycles, do you update current or just get the latest snapshot? Personally, I don't run -current from source. I have built subsets of the tree to pick up a patch. But my usecase isn't the same. I don't think it would matter if you built from source or used an old snapshot. Just pay attention to the following current page. And don't quote me on this. :) Tim.
Re: Maintaining your system with snapshots
On 20 Feb 2015, Peter N. M. Hansteen wrote: As for works for me guides, my (by now somewhat dated) blog post [1] may still be useful despite needing some updates (such as don't bother running sysmerge with those arguments anymore (actually don't use any arguments to sysmerge in most cases), and hold off doing that until after you've booted into the new system, and likely other nits I may possibly address in the near future). - Peter [1] http://bsdly.blogspot.no/2012/07/keeping-your-openbsd-system-in-trim.html Peter's post is certainly helpful (thank you Peter). Another place I've found useful is http://daemonforums.org/showthread.php?t=8865 See particularly the contribution of iggimi in this link, which I've found extremely helpful. Anthony -- Anthony Campbellhttp://www.acampbell.uk
Re: Maintaining your system with snapshots
It is so quick and easy to update to another snapshot, if I find a package that doesn't work, I simply update to the latest snapshot. Maybe once or twice I have hit the situaton where the snapshot was out of date with the snapshot packages and I couldn't use my system right after upgrading. I either check for a mirror that has synced the latest packages or wait a day and I'm good to go. It's still less time lost than rebuilding the packages locally. Tim.
Re: Maintaining your system with snapshots
On Fri, Feb 20, 2015 at 10:21 AM, Steve Williams st...@williamsitconsulting.com wrote: Hi, I have been using snapshots for my system, but don't update too often. Sometimes there's a package I want to install, but because my snapshot is old (stale when compared to the current repository), I can't get the package. What I have started to do is download the ports.tar.gz when I install a snapshot. I have no idea if this is a supported approach, but I've never had a problem building from ports when I need something after the fact. The downside of doing this is I get MANY packages installed that are dependencies of building a port. As someone else mentioned, snapshot packages are usually perfectly sufficient, unless you have some corner case like an arch that doesn't refresh frequently or you need a very recent fix. There are occasional hiccups but rarely are they serious; this is the tradeoff for following closer to the development edge. If you are tired of old build dependencies, look into pkg_delete -a. You may need to alternate pkg_info -m and pkg_add -aa to mark your packages appropriately. On my systems, ONLY my required packages are marked as manually installed, so that I can run pkg_delete -a immediately after sysmerge and pkg_add -u. --david
Re: Maintaining your system with snapshots
Thanks for your reply! packages for releases and snapshots are built separately. mixing snapshot (-current) packages with stable or release versions is not supported (libraries and other dependencies are likely to not match). I was not mixing them, but I have the feeling I might be using an outdated -current base system (maybe just a few days, installed from snapshot) with more recent packages (installed from a more recent snapshot). I was concerned about it, as I think base system and packages need to be completely on sync. As for works for me guides, my (by now somewhat dated) blog post [1] may still be useful despite needing some updates (such as don't bother running sysmerge with those arguments anymore (actually don't use any arguments to sysmerge in most cases), and hold off doing that until after you've booted into the new system, and likely other nits I may possibly address in the near future). Your blog post was the one that encouraged me to go to -current :) Congrats for all the great work, Luis [1] http://bsdly.blogspot.no/2012/07/keeping-your-openbsd-system-in-trim.html
Re: Maintaining your system with snapshots
On 20/02/2015 2:19 AM, lm wrote: Hi there! I'm giving a try to snapshots for the first time. The system feels great, but I'm having some issues trying to maintain base system and ports synced. I've got a local copy of the complete packages tree for convenience, so I don't have to update base and ports everytime I want to install a new package, but it still seems some packages don't match the base system and they crash. How do you maintain your system fresh? What do you follow? Thanks, Luis Hi, I have been using snapshots for my system, but don't update too often. Sometimes there's a package I want to install, but because my snapshot is old (stale when compared to the current repository), I can't get the package. What I have started to do is download the ports.tar.gz when I install a snapshot. I have no idea if this is a supported approach, but I've never had a problem building from ports when I need something after the fact. The downside of doing this is I get MANY packages installed that are dependencies of building a port. For example: autoconf-2.13p2 automatically configure source code on many Un*x platforms autoconf-2.52p4 automatically configure source code on many Un*x platforms autoconf-2.59p3 automatically configure source code on many Un*x platforms autoconf-2.61p3 automatically configure source code on many Un*x platforms autoconf-2.64 automatically configure source code on many Un*x platforms autoconf-2.65 automatically configure source code on many Un*x platforms autoconf-2.69p0 automatically configure source code on many Un*x platforms Yes, I've had this system going for a while! lol. Cheers, Steve W.
Re: Maintaining your system with snapshots
On 2/20/2015 9:21 AM, Steve Williams wrote: On 20/02/2015 2:19 AM, lm wrote: Hi there! I'm giving a try to snapshots for the first time. The system feels great, but I'm having some issues trying to maintain base system and ports synced. I've got a local copy of the complete packages tree for convenience, so I don't have to update base and ports everytime I want to install a new package, but it still seems some packages don't match the base system and they crash. How do you maintain your system fresh? What do you follow? Thanks, Luis Hi, I have been using snapshots for my system, but don't update too often. Sometimes there's a package I want to install, but because my snapshot is old (stale when compared to the current repository), I can't get the package. What I have started to do is download the ports.tar.gz when I install a snapshot. I have no idea if this is a supported approach, but I've never had a problem building from ports when I need something after the fact. The downside of doing this is I get MANY packages installed that are dependencies of building a port. For example: autoconf-2.13p2 automatically configure source code on many Un*x platforms autoconf-2.52p4 automatically configure source code on many Un*x platforms autoconf-2.59p3 automatically configure source code on many Un*x platforms autoconf-2.61p3 automatically configure source code on many Un*x platforms autoconf-2.64 automatically configure source code on many Un*x platforms autoconf-2.65 automatically configure source code on many Un*x platforms autoconf-2.69p0 automatically configure source code on many Un*x platforms Yes, I've had this system going for a while! lol. Cheers, Steve W. +1 I do the exact same thing. I have a machine up for couple of weeks and want to add some newer software I compile from ports that I had downloaded with the snapshot on a test computer. If it works fine, if not, I check current snapshot or other version. To me that freedom is one of the great things about OpenBSD. Thank you developers! Victor
