View Single Post
  #2   (View Single Post)  
Old 13th June 2008
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
Join Date: May 2008
Location: USA
Posts: 6,350

The reason for the failure to update the package is an update to libc, which makes the package out-of-date.

Snapshots of the OS are created on an as-needed basis. For popular architectures during normal day-to-day development periods, this may be daily, or every few days. But during hackathons, the frequency of snapshots may be every several hours. A hackathon is going on right now in Edmonton -- see the OpenBSD Journal for some recent information.

Snapshot packages, on the other hand, are updated less frequently. Understand that there are around 5000 packages to build, and that it can take days, depending on architecture and build platforms. On popular archs, this may be every couple of weeks. On less-popular archs, there are no snapshot packages created at all. On those architectures, -current users must build all their packages from ports themselves.

Snapshot packages are created for convenience. There is no synchronization with any particular snap of the OS.

The best practice for those who use snapshot packages is, in my humble opinion:
  1. Log console output, using script(1) or a similar facility
  2. Use "# pkg_add -iu" to update those packages which will update cleanly.
  3. Review the console output, and manually build packages from ports which are out of sync and fail to update.
  4. Use "# pkg_add -ir <list of packages>" for those packages which failed to update due to a dependent package which was out of sync but will update cleanly once the dependent package is updated.
  5. Run ports/infrastructure/build/out-of-date, and build any out-of-date packages for any ports which do not have packages built for them, either due to FLAVOR or licensing. I ignore packages marked out-of-date if they updated cleanly from the most recent snapshot package updates.
Reply With Quote