Re: pkg_add tests
On Fri, Jan 24, 2014 at 11:15:21PM -0600, Shawn K. Quinn wrote: > On Fri, Jan 24, 2014, at 06:50 AM, Marc Espie wrote: > > You should realize that the pkg tools have gone thru *major internal > > changes* > > over the last month or so. > > > > If you see weird things happening, now is a really good time to report > > them, > > before it's too late... > > > > > > Also, the 5.4 -> 5.5 update is going to be "fun": there was a kernel flag > > day. > > > > The proper way to update packages will be along the lines of: > > in 5.4: > > > > pkg_info -mq >list > > pkg_delete * > > > > (update to 5.5) > > in 5.5, install new packages: > > pkg_add -z -l list > > > > > > Again, there might be issues. Now is a very good time to start > > looking... > Do we have to do any of this if we have been following snapshots or > -current? Are there any other gotchas related to these for those of us > who are running snapshots or -current? I haven't had any obvious Bad > Things jump up and bite me yet, want to keep it that way. > (Software-related, at least; having my onboard SATA controller fall down > and go boom kind of falls outside the realm of that.) Nope. You already went over the hurdle of timestamps. But if you have some 5.4 installs, or if people want to check how 5.4->5.5 goes, well, it will soon be the time to do so. Basically, the big change for them is that pkg_add now always installs the quirks package first, and it uses it to hunt for package names on fuzzy installs. e.g., the above scenario that I outlined should now get people over the 5.4 -> 5.5 hurdle *while handling package renames correctly*. Obviously, this hasn't been tested too much yet... As for the usefulness of testing, for instance, I made a large booboo in an extra check in pkg_sign. Fortunately rpe@ caught it fairly early, so a fixed amd64 snap should be on its way out soon (and it was just garbled archives, so rsync should chew on that one really fast compared to the usual slooow trickle of snapshots out).
Re: pkg_add tests
> Do we have to do any of this if we have been following snapshots or > -current? Are there any other gotchas related to these for those of us > who are running snapshots or -current? I haven't had any obvious Bad > Things jump up and bite me yet, want to keep it that way. > (Software-related, at least; having my onboard SATA controller fall down > and go boom kind of falls outside the realm of that.) We are starting to stabilize towards the next release. There's been some pretty big changes... One thing that would help is to get some good "clean snapshot installs". If we get those, then we can know the installs are looking great. That will make it easier for us to handle bug reports relating to upgrades.
Re: pkg_add tests
On Fri, Jan 24, 2014, at 06:50 AM, Marc Espie wrote: > You should realize that the pkg tools have gone thru *major internal > changes* > over the last month or so. > > If you see weird things happening, now is a really good time to report > them, > before it's too late... > > > Also, the 5.4 -> 5.5 update is going to be "fun": there was a kernel flag > day. > > The proper way to update packages will be along the lines of: > in 5.4: > > pkg_info -mq >list > pkg_delete * > > (update to 5.5) > in 5.5, install new packages: > pkg_add -z -l list > > > Again, there might be issues. Now is a very good time to start > looking... Do we have to do any of this if we have been following snapshots or -current? Are there any other gotchas related to these for those of us who are running snapshots or -current? I haven't had any obvious Bad Things jump up and bite me yet, want to keep it that way. (Software-related, at least; having my onboard SATA controller fall down and go boom kind of falls outside the realm of that.) -- Shawn K. Quinn skqu...@rushpost.com
pkg_add tests
You should realize that the pkg tools have gone thru *major internal changes* over the last month or so. If you see weird things happening, now is a really good time to report them, before it's too late... Also, the 5.4 -> 5.5 update is going to be "fun": there was a kernel flag day. The proper way to update packages will be along the lines of: in 5.4: pkg_info -mq >list pkg_delete * (update to 5.5) in 5.5, install new packages: pkg_add -z -l list Again, there might be issues. Now is a very good time to start looking...
