Looks like finally a version for 2.6.39 and 3.0 kernels is available:
Thanks a lot
I'm not in favor of adding this version to the tree (unless p.masked), this is *current* (ie. head) version, it's not properly versioned and file content changes without any version change in file name.
No problem, do what ever you prefer as you know much more about TOI than me :-)
Do patches _have_ to be rolled? (Git trees are available and always up to date).
I'd prefer to have them at least with time stamp, something like current-20110801-tuxonice-for-2.6.39.patch.bz2 - that would help a lot, otherwise if you change the tarballs without changing file name users will start getting checksum/size mismatches.
*** Bug 377327 has been marked as a duplicate of this bug. ***
*** Bug 377323 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> Do patches _have_ to be rolled? (Git trees are available and always up to
The problem with git (in this case) is you need to checkout a whole copy of the Linux kernel using more bandwidth and you can not mirror a changing git repo with the GPG key sighing in tacked.
So the only download URL would be 'git.kernel.org'.
If you make tarballs the tarballs would be mirrored on the Gentoo mirrors and it would keep the load off your web server.
I'm guesting your using a script to create the patch tarball from git?
If you made the folder 'http://tuxonice.net/files/' readable as an index you could update your script to use a symlink from current-20110801-tuxonice-for-3.0.patch.bz2 to current-tuxonice-for-3.0.patch.bz2.
Ones you have updated the script it should work with out added to your work load.
Sorry for the slow reply - too much on my plate at the moment.
Fair enough. Yes, I am using a script. I'll seek to find the time to script uploading updates etc, to make life easier for both of us.
Feel free to prod me if I take a while to do it - grossly overloaded, as always (partly self inflicted!).
(In reply to comment #8)
> Sorry for the slow reply - too much on my plate at the moment.
> Fair enough. Yes, I am using a script. I'll seek to find the time to script
> uploading updates etc, to make life easier for both of us.
Awesome! Thank you Nigel.
Would be nice to have at least a 2.6.39 version as it should solve bug 378639, that is a bit annoying :S
Thanks a lot :)
I sent a email to Nigel Cunningham the other day and he is still over overworked.
Krzysztof Pawlik can you add the two new versions with a package mask until he finds time to add the date versioning please?
Nigel, any news here? I know you are probably busy a lot but kernel 2.6.38 is a bit unstable with Sandybridge Intel graphics card :(
Thanks a lot
Created attachment 289445 [details]
Ebuild for kernel 3.0.4
For anyone who just wants a quick fix to upgrade to a more recent kernel, here's the ebuild I've been using - I just copied the latest one to the new version number, updated the URL for the tuxonice patch (using current-tuxonice-for-3.0.patch, so this is not a particularly safe method, since the file on tuxonice.net may change without changing the file name), and bumped the gentoo patches to the correct version for 3.0.4. To install, just add this to your local overlay and run ebuild digest on it.
Krzysztof, regarding current-tuxonice-for* files changing from time to time without updating their names, I think we could handle this downstream a bit like I am currently doing in bluez ebuilds with oui.txt file, that is basically, ship us a copy from our dev space:
"# Because of oui.txt changing from time to time without noticement, we need to supply it
# ourselves instead of using http://standards.ieee.org/regauth/oui/oui.txt directly.
# See bugs #345263 and #349473 for reference.
As I don't think tuxonice has any license preventing us to do that ;)
+*tuxonice-sources-3.0.6 (12 Oct 2011)
+ 12 Oct 2011; Pacho Ramos <email@example.com> +tuxonice-sources-3.0.6.ebuild,
+ Version bump and add myself as co-maintainer.