On Tuesday 03 May 2016 18:47:39 Andrew Savchenko wrote: > On Tue, 03 May 2016 09:56:29 +0100 Peter Humphrey wrote:
--->8 > > What is the approved method of reading change-logs nowadays? > > If you are using git sync, just go to /usr/portage/sci-misc/boinc > and run `git log .` there. > > If you are using rsync sync, read end of the ChangeLog file, tail > -n 50 should do the job. 'equery c boinc' should work too. Okay, thanks. > Looks like your problem comes from broken rsync mirror with outdated > ChangeLog files. No, I see it now: 'equery c boinc' returns the ChangeLog section that refers to the currently installed version, not to any earlier or later ones. If I know what later versions are available I can do something like "equery c =sci-misc/boinc-7.6.31" but I hadn't done so until just now. What's happened, I think, is that the init script change introduced into the latest version has been silently back-ported to the previous version. That's why I didn't see it in the ChangeLog, and it explains why I didn't get it during routine updates - only when I uninstalled the package and reinstalled it. A learning point has emerged here: it's dangerous to specify a version in package.keywords. I can't say I'm delighted to have spent three weeks in fruitless bug chasing, just because of an undocumented change that had already fixed my problem behind my back. At least I understand what's going on now. Thanks for your help, Andrew. -- Rgds Peter
