On Sun, Dec 17, 2006 at 09:20:53AM -0600, Randy McMurchy wrote:
> Just FYI, Alexander, but nobody can really see what is being committed
> right now in any of the books, so don't be surprised if there are
> "no objections". Mail is not being sent for the commits, therefore, the
> only way to check
Randy McMurchy wrote:
> Alexander E. Patrakov wrote these words on 12/17/06 02:22 CST:
>
>> if nobody has objections, I am going to release r1796 of both trunk and
>> the 6.2 branch as 6.3-pre1 and 6.2-4 CDs. The build has already started
>> on ums.usu.ru for trunk.
>>
>
> Just FYI, Alexa
Alexander E. Patrakov wrote these words on 12/17/06 02:22 CST:
>
> if nobody has objections, I am going to release r1796 of both trunk and
> the 6.2 branch as 6.3-pre1 and 6.2-4 CDs. The build has already started
> on ums.usu.ru for trunk.
Just FYI, Alexander, but nobody can really see what is b
Archaic wrote:
On Sun, May 21, 2006 at 03:27:01PM +0100, Matthew Burgess wrote:
Anyone having issues with any of the above feel free to point fingers
and laugh in my general direction, oh and anything more constructive
would be appreciated too :-)
There are still bugs that need to be dealt
On 5/22/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
On the 'Locale Related Issues' page in BLFS it opens with:
"This page contains information about locale related problems and
issues. In this paragraph you'll find a generic overview of things
that can come up when configuring your system for
Jeremy Huntwork wrote these words on 05/22/06 08:52 CST:
> I think I understand your concern here. A note in BLFS saying that
> multibyte locale support in LFS/BLFS is new and not fully tested for
> each package, along with the reminder to check the wiki for user notes
> should suffice don't yo
Alexander E. Patrakov wrote:
1) BLFS still has http://wiki.linuxfromscratch.org/blfs/ticket/1957 .
Since BLFS has marked this as WONTFIX, the fact that BLFS includes known
broken applications without notice must be mentioned in LFS, and support
should be disclaimed completely. Ideally, it shoul
Matthew Burgess wrote:
1) Package freeze (Wed. 24th)
2) Cut an RC1 (Wed. 24th)
3) Release (Wed. 31st)
Sorry, I cannot agree with this plan.
1) BLFS still has http://wiki.linuxfromscratch.org/blfs/ticket/1957 . Since BLFS
has marked this as WONTFIX, the fact that BLFS includes known broken
On Sun, May 21, 2006 at 10:20:53PM -0700, Jim Gifford wrote:
> Archaic,
>Can you provide a link to that post?
I'll link to every pending lfs-dev item in my inbox. The first one is a
summary with several more links (some of which are already dealt with).
http://linuxfromscratch.org/pipermail/l
Archaic,
Can you provide a link to that post?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
On Sun, May 21, 2006 at 03:27:01PM +0100, Matthew Burgess wrote:
>
> Anyone having issues with any of the above feel free to point fingers
> and laugh in my general direction, oh and anything more constructive
> would be appreciated too :-)
There are still bugs that need to be dealt with. Some
Randy McMurchy wrote:
3. I thought LFS would have already by now put a package freeze
so that we can get a new release out (hint, hint)
Yeah, I know. Real life has been getting in the way. I should be able
to declare a package freeze some time this week. The plan will be:
1) Package f
12 matches
Mail list logo
