Bug #444932 and bug #458606 are very important bugs affecting our current official install cd isos, and also new gentoo installations for stable "genkernel all" users. These have been fixed in git and even in newer genkernel releases, but there are too many major changes and regressions in those new versions for them to be ready for stablization any time soon. I would like to request that we add these 2 individual fixes to the current well-tested 3.4.45 release as an -r1 revbump so that we can get these fixes pushed out to stable users (and releng's autobuild isos) ASAP. The 2 relevant commits are: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commit;h=3817a4959faa3d93df9d1340364f77020271d1f2 http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commit;h=4c93a5adb7dd45cfeddba111f5c51902f5eac3a8 Thanks!
There are a lot of bugs popping up in the newer releases of genkernel which are causing not insignificant delay in getting a new stable release out to fix the release engineering issues. While I'm personally excited to see all of the great work going into genkernel (which is causing the bugs, and then more work going into genkernel) we simply can't wait for things to stablize. Would it be possible to make a revbump with these two patches for the stable genkernel so we can start making working livecds again? Honestly only #458606 is critical but the other was is important and very trivial.
arches: this is a quick-stable request for genkernel v3.4.45.1. target keywords: alpha amd64 arm hppa ia64 ppc ppc64 s390 sparc x86 It backports some of the safe fixes from v3.4.47 to the previous stable v3.4.45, due to new hardware/kernels needs. Please test & stabilize. Fixes backported: USB3: #458606, #452888 RTC: #444932 Docs: #432956 switch_root: #422471 newer pax-utils support: (no bug#)
alpha stable
amd64 stable
arm stable
hppa stable
ia64 stable
ppc64 stable
ppc stable
s390 stable
sparc stable
x86 stable. Last arch, closing
(In reply to Agostino Sarubbo from comment #6) > hppa stable I doubt that you even tested this. genkernel certainly didn't work out of the box on the first HPPA system I tested with.
(In reply to Jeroen Roovers from comment #13) > (In reply to Agostino Sarubbo from comment #6) > > hppa stable > > I doubt that you even tested this. genkernel certainly didn't work out of > the box on the first HPPA system I tested with. I don't know how much testing was done but this appears to be a previously existing bug. Given the fixes (some pretty important) I'll leave this to the hppa team to stable or not at this time.
(In reply to Jeroen Roovers from comment #13) > (In reply to Agostino Sarubbo from comment #6) > > hppa stable > > I doubt that you even tested this. genkernel certainly didn't work out of > the box on the first HPPA system I tested with. I doubt you know what the word regression means...
(In reply to Rick Farina (Zero_Chaos) from comment #14) > (In reply to Jeroen Roovers from comment #13) > > (In reply to Agostino Sarubbo from comment #6) > > > hppa stable > > > > I doubt that you even tested this. genkernel certainly didn't work out of > > the box on the first HPPA system I tested with. > > I don't know how much testing was done but this appears to be a previously > existing bug. Given the fixes (some pretty important) I'll leave this to > the hppa team to stable or not at this time. I've reverted since there was no reason for a new version to go stable at this time. Perhaps we'll stabilise a newer fixed version. Feel free to close this one.
OK, let's stabilise for HPPA under the presumption that nobody is actually using this without a custom configuration. Stable for HPPA. Closing.
