Attached is a new ebuild based on 1.0_pre3 from portage. Since upstream doesn't seem to be releasing any new tarballs, this is based on a specific git revision (latest as of today), it pulls a tarball straight from git.kernel.org's gitweb. Includes mcelog.init (slightly modified) from bug #310757. Added kernel config check, dropped virtual/cron dep as the system service is the preferred run method now. The cron.daily file is still installed but not active by default now. Builds and runs fine here. I know the versioning is a bit funny but upstream has released pre3 and may release pre4 so I was advised to set a dated version between those releases. Open to more suggestions. Reproducible: Always
Created attachment 299197 [details] mcelog-1.0_pre4_pre20110805.ebuild
Created attachment 299199 [details] mcelog.init
I was looking into getting a new version of mcelog (need support for newer hardware) so I contacted the author (Andi Kleen). He stated that the git tree is stable and packagers just use snapshots from it for new packages. I wouldn't expect a new actual release soon (if ever). Other than updating the ebuild again to use a more recent commit, is there anything else keeping this ebuild out of the tree?
I just checked on this today, and upstream git.kernel.org's snapshot tarballs are now including a timestamp, so the tarball checksum changes with every fetch. This is pretty much game-over for fetching a tarball from git.kernel.org directly, someone would have to host a snapshot in their dev space. That said, I bumped my ebuild to the most recent commit bec51ee686f29abd48c6ee4b67cff72135e80156 (dated 2012-06-14) and it builds and runs just fine here.
This package is now maintainer-needed. If you want proxy-maintain it, poke the relative herd.
Created attachment 322649 [details] mcelog-1.0_pre4_pre20120807.ebuild Good news! Well, not great news, this package is still m-w and on it's last leg, BUT-- Someone yesterday pointed me to another source for snapshot tarballs on Andi Kleen's github, where he does the commits before moving them over to git.k.o, so I have a working updated ebuild to share. You can verify that the github commits on this source match the commits on git.k.o (they just happen on github sooner), so it is indeed the same source.
(In reply to comment #6) > Created attachment 322649 [details] > mcelog-1.0_pre4_pre20120807.ebuild > > Good news! Well, not great news, this package is still m-w and on it's last > leg, BUT-- > > Someone yesterday pointed me to another source for snapshot tarballs on Andi > Kleen's github, where he does the commits before moving them over to > git.k.o, so I have a working updated ebuild to share. You can verify that > the github commits on this source match the commits on git.k.o (they just > happen on github sooner), so it is indeed the same source. I can be your proxy maintainer, the only note is that I would move to 1.0_pre3_p20120807 version number, see http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap3 for naming policy Thanks
Created attachment 324728 [details] app-admin/mcelog-1.0_pre3_p20120918.ebuild Updated snapshot ebuild w/ proper versioning, and upstream added some more SB support. I would be happy to proxy maintain this, but I don't know anything about that process. Can you point me in the right direction? Thanks
+*mcelog-1.0_pre3_p20120918 (24 Oct 2012) + + 24 Oct 2012; Julian Ospald <hasufell@gentoo.org> + +mcelog-1.0_pre3_p20120918.ebuild, + +files/mcelog-1.0_pre3_p20120918-build.patch, +files/mcelog.init, + metadata.xml: + version bump by Ben Kohler wrt #399241 new maintainer/proxymaintainer @pacho too slow, but add yourself as maintainer if you like @iamben you have been added as proxymaintainer which basically means you will be CCed on bugs and can ping me on version bumps etc http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml?style=printable
Thanks Julian, I am simply plenty of work at the moment :|
