Once again I got bitten by an upgrade to ASSP wiping out my hack for the list. Totally my fault, as I was the one who upgraded ASSP in the first place this time and I don't mean a simple upgrade, emerge -u assp.
Since I am no longer a developer, ASSP has gone without a maintainer on Gentoo for just under 2yrs. I first put ASSP into Gentoo's portage and maintained the package, along with many others. A bit ago a user contributed an updated ASSP ebuild to Gentoo's Bugzilla. Since the package lacked a maintainer, after a while a developer came along and committed the contribution in bugzilla to portage. That upgrade wiped out my hack a few months back, mentioned on list. Which prompted me to make my hack a patch to be applied again. But I didn't automate the application of it. Yes I failed :) Now the updated version of ASSP on Gentoo had some errors, which I corrected. Along with updating the version of ASSP, bumped the ebuild version number to the latest version. After that took a little while, but I was able to get that back to the last Gentoo Developer who committed the last update to ASSP and since has taken over as maintainer. Of course with committing mine and others contributions, no worries still gave credit in changelog :) Anyway this time it was all me. I updated the ebuild, got it into portage, and then totally forgot about it when I updated the LUG mail server. Such that it wiped out my hack/patch. Which I did not catch till a user tried to subscribe and had problems today. Thankfully I kept it as a patch, so I just applied that again and all is well again. I now need to see about automating that, so its always applied, no more with this list subscription problems again crap ;) Likely won't do that in portage or in the ebuild. Since its just for the one machine, and is more of a hack than a true patch/fix for the problem/issue. Also it would be more work as the ebuild might get updated, or modified next I sync portage. Short of maintaining my own copy in a local overlay which is a pain. I will simply have cron apply the patch weekly before running the weekly update scripts. That way it will always be applied if it has not already been done so after any updates. Still kinda a hack, but an automated one :) -- William L. Thomson Jr. Systems Administrator Jacksonville Linux Users Group --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
