Re: Changelog unchanged

2006-02-10 Thread Bruce Dubbs
Kev Buckley wrote: > As the "one person reporting confusion" might I just expand on why I > think it doesn't sit too well not to document changes in the Changelog. > > Someone sees a date change in the SVN tag after a few days of > "inactivity" and assumes that there's been a change. They go to

Re: GPM, W3M and Lynx instruction changes

2006-02-10 Thread Alexander E. Patrakov
I wrote: http://wiki.linuxfromscratch.org/blfs/wiki/Links Whoops, should be http://wiki.linuxfromscratch.org/blfs/wiki/LinksBrowser I (mistakenly) thought that Links means something special to Trac. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://

GPM, W3M and Lynx instruction changes

2006-02-10 Thread Alexander E. Patrakov
Hello, Yesterday and today I added the following pages to Trac: http://wiki.linuxfromscratch.org/blfs/wiki/GPM http://wiki.linuxfromscratch.org/blfs/wiki/W3M http://wiki.linuxfromscratch.org/blfs/wiki/Lynx http://wiki.linuxfromscratch.org/blfs/wiki/Links The first three of them contain changes

Re: Bootstrapping GCC

2006-02-10 Thread Dan Nicholson
On 2/6/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote: > Hello All, > > In talking with Ryan Oliver, there seems to be one final thing that we > can do to our current build which will help stabilize it completely: add > 'make bootstrap' to the gcc build of chapter 6. > > > Comments? As I said in a

Re: [DIY BUG] bash wants en_US locale

2006-02-10 Thread Jeremy Huntwork
Randy McMurchy wrote: Either way, I don't see why we couldn't release a UTF-8 ready version of LFS, and a BLFS that is as best as we can do (with a caveat up front stating that the UTF-8 implementation is incomplete, and my not work correctly. Agreed. UTF-8 has been present but broken in LFS f

Re: [DIY BUG] bash wants en_US locale

2006-02-10 Thread Randy McMurchy
Alexander E. Patrakov wrote these words on 02/10/06 03:25 CST: > I do not blame BLFS. Thanks for personally clarifying this issue. > I am just saying that it is a huge (but doable!) > job for me to verify all BLFS packages. My point is that if we release > both LFS and BLFS now, I didn't rea

Re: Changelog unchanged

2006-02-10 Thread Kev Buckley
> > On Wed, Feb 08, 2006 at 09:18:41AM -0500, Jeremy Huntwork wrote: > > > > Manuel, I wonder if it's best to leave the date alone when making > > strictly XML changes. Either that, or start adding Changelog entries for > > them. Just so its not confusing to those comparing the Changelog with

Re: [DIY BUG] bash wants en_US locale

2006-02-10 Thread Justin R. Knierim
Alexander E. Patrakov wrote: Justin R. Knierim wrote: Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't reproduce the error either. Sorry for the noise, I can't figure it out. The issue is probably that the old root password contained some non-ASCII character, and someone recent

Re: [DIY BUG] bash wants en_US locale

2006-02-10 Thread Alexander E. Patrakov
Randy McMurchy wrote: Justin R. Knierim wrote these words on 02/09/06 09:50 CST: IMO he isn't blaming BLFS for problems with UTF-8. Then you and I read plain English differently. IMO, the following statement directly conflicts with what you say above: "But it is indeed better to say

Re: [DIY BUG] bash wants en_US locale

2006-02-10 Thread Alexander E. Patrakov
Justin R. Knierim wrote: Nevermind, I just tried with the 6.2-pre3 LiveCD and I can't reproduce the error either. Sorry for the noise, I can't figure it out. The issue is probably that the old root password contained some non-ASCII character, and someone recently changed the password to pure