On 3/17/08, Hisham <[EMAIL PROTECTED]> wrote: > > > 2.6.24.x kernel: This kernel opps while mounting squashfs > > filesystems. Obviously, this is a problem for the livecd. Last I > > talked with Lucas, he had a few patches to try but I don't know the > > current status. > >
Still need an update, Lucas?? > > OpenOffice (238): I've built 2.3.1_bin-r2 in ChrootCompile. This > > solved the freedesktop entry problem but openoffice won't load. I > > tracked this down to the lack of symlinks in bin (to ../programs) for > > openoffice.org2.3.bin, soffice.bin, pagein. Oddly, the recipe makes > > the soffice.bin symlink. Also, the soffice link is made twice. > > I'm taking this one. It seems to have the most problems in the LiveCD itself (ok on HD). > > mplayer (260): need an updated skel (maybe enchanced?) for a > > ~/.mplayer/subfont.ttf symlink. Recommendations for the font to use? > > > In my machine here I have a link > /Programs/MPlayer/Current/Shared/mplayer/subfont.ttf -> > /Files/Fonts/TrueType/Vera.ttf > Perhaps we could even copy the font there, to simplify things. > I just checked my 014rc-something, 014-final, and 014.b-internal installs. There is no /F/Fonts/TT/Vera.ttf. Fixing the symlink in /P/MPlayer/C/Share/mplayer is a better fix than changing skel. (added note to bugs) > > > > Squashfs on AM2 (283): Unable to reproduce on my AM2 machine. Is the > > bug a gross failure or subtle (read corruption)? > > > I'm not sure, but I think it fails to boot. I have access to an AM2 > machine, still need to test this. > Ok. It may be a BIOS issue. I know Solaris complained about an AMD errata. I upgraded my BIOS and all was well. > > > Boot in VirtualBox (284): I don't have Virtualbox installed (and no > > gcc 3.x to build). If someone has a Virtualbox package I'd appreciate > > it. Would rather not introduce gcc3 into my system. > > If someone has this built, I'd love a copy. Thanks. > > > > Broken Links after install (199): RemoveBroken needs to be run in > Installer? > > Comments? > > Sudo overwrites files (204): This is a longstanding problems. There > > is a suggested change to the sudo recipe in the bug tracker. Has the > > recipe been updated? > > I've experienced this countless times. If we have a fix, this really should go in. (Bug moved to 014) > > > In a nutshell, we need new Scripts, EnchancedSkel, Installer releases > > (changes may not be in svn). Updated Sudo, OpenOffice > > recipes/packages. Updated Xorg package. I'll take ownership of the > > OpenOffice changes. They seem to be LiveCD specific. > > > > Now, to talk about PostInstall. I'm going to be a bit verbose because > > I won't be there tomorrow to respond to question regarding what I > > mean. The PostInstall script is run to create an EFFECT (I'll use > > this a lot) on the system (create id/keys, set ownership based on > > created user/group, etc). This effect should be distinct for each > > install. The LiveCD is a type of install. It should be affected by > > the PostInstall scripts. Whether this happens during ISO generation > > or boot is debateable but probably minor. > > > > So the LiveCD needs PostInstall effects. These effects should not be > > mirrored to the HD during install. During install, PostInstall needs > > to be run to generate the distinct effects for that system. > > > > I'm worried that Installer is not sophisticated enough to prevent > > transferring the LiveCD effects to the HD. There are only 4 > > PostInstall scripts on the LiveCD, so they can be special cased for > > 014.b but a plan for general use would be great for beyond. Similar > > concerns apply for R/Requirements as well. > > > I believe the effects applied to the LiveCD environment all go into > Settings directories and the user's home directory, while the > Installer does not use these directories, using each package's > Defaults/Settings instead. IIRC, André was the one who worked on this, > so he may be able to confirm. In this case, we shouldn't have a > problem running PostInstalls (for example) on LiveCD boot for the > LiveCD environment, and then running them again for the installed > system. > This needs to be investigated and decided whether to include for 014.b or not. > > On IRC, Jonas and I discussed upping KDE to 3.5.9. At that point, I > > started to think that 014.b could be more than a bugfix release. > > Keeping the stage 1 core, updating the stage 2 desktop and stage 3 > > apps. With the timeline, I'm sure that is not feasible. I'd like more > > details wrt pressing CD. Is this for a magazine? Is it worth the > > rush? Especially since 014 is a little dated. > > Given that KDE 3.5.9 itself is also a bugfix release, I'm kinda > favorable to that idea as well. > Still an open issue. Jonas knows a bug (not in tracker) in KDE-Base. I guess we can try 3.5.9 and fallback to 3.5.8 if problems arise. Someone volunteer to build packages? > > > For the ISO, I'd prefer to receive binary packages. Hopefully those > > providing packages would have more detailed knowledge of the > > application and could test the package thoroughly. This should catch > > bugs before they get to an ISO rc. To implement this, I could set up > > a webdav dropbox on calica.com. Maybe ftp as well. Another option is > > SVN. To build packages, you'd just need ChrootCompile on 014. For > > 015, we could have an image that runs under lguest. Please discuss > > this on IRC and provide feedback. > > > As mentioned in the IRC metting, simpler is better. I'd prefer using ftp. > Ok, ftp. I'll look into servers that support virtual users. > > > SVN migration. This requires changes in BuildLiveCD tools. Hopefully > > these changes won't take too long to implement or cause other > > regressions. > > > Yes. I can look at that later in the week unless someone beats me to it. > I've pretty much completed this. A little testing and I'll commit. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
