Randy McMurchy wrote:
Randy McMurchy wrote these words on 05/07/08 06:37 CST:
Bruce Dubbs wrote these words on 05/07/08 01:20 CST:
Is it time to do a freeze/rc1?
I'm off to work and will look at this, then publish something official
this evening.
Didn't get around
Hi all,
since I'm new to the editors group (or for any other reason) I may have missed
something, so don't hit me too hard for the following question(s).
It seems so that we need to update some directories (files in it) on anduin in
case of a version update, right? That dir is
Thomas Trepl wrote:
Hi all,
since I'm new to the editors group (or for any other reason) I may have
missed
something, so don't hit me too hard for the following question(s).
It seems so that we need to update some directories (files in it) on anduin
in
case of a version update,
Alexander E. Patrakov wrote:
DJ Lucas wrote:
The real problem with it is, if we keep holding for every version
increment, we'll never get 6.3 out the door.
And do we really need to get 6.3 out of the door? Essentially, without an
errata
page, without the team tracking security issues
Jeremy Huntwork wrote:
Alexander E. Patrakov wrote:
DJ Lucas wrote:
The real problem with it is, if we keep holding for every version
increment, we'll never get 6.3 out the door.
And do we really need to get 6.3 out of the door? Essentially, without an
errata
page, without the team
Thomas Trepl wrote these words on 05/09/08 01:07 CST:
It seems so that we need to update some directories (files in it) on anduin
in
case of a version update, right? That dir is /srv/ftp/BLFS/
If i understood this thread right, we need to keep that directories uptodate
since there is
Randy McMurchy wrote these words on 05/09/08 05:00 CST:
I do not want to get into a situation where if someone follows
LFS stable, we need to tell them to pull SVN sources from XYZ
day and render it yourself in order to find a combination of
packages that is compatible with one-another.
I
Randy McMurchy wrote:
I do not want to get into a situation where if someone follows
LFS stable, we need to tell them to pull SVN sources from XYZ
day and render it yourself in order to find a combination of
packages that is compatible with one-another.
The compatibility problem automatically
Alexander E. Patrakov wrote these words on 05/09/08 01:10 CST:
And do we really need to get 6.3 out of the door? Essentially, without an
errata
page, without the team tracking security issues and bugs, it will be just a
snapshot, not a proper distro release. Maybe versionless BLFS (i.e.,
Randy McMurchy wrote:
Thomas Trepl wrote these words on 05/09/08 01:07 CST:
It seems so that we need to update some directories (files in it) on anduin
in
case of a version update, right? That dir is /srv/ftp/BLFS/
If i understood this thread right, we need to keep that directories
Moving to blfs=dev...
For reference, see http://wiki.linuxfromscratch.org/blfs/ticket/2533
BLFS Trac wrote:
Comment (by [EMAIL PROTECTED]):
I'm not sure if Bruce has changed his mind, or if he thinks our
policy is dated, or what, but he has turned 180 degrees on this
one. The last time
On Fri, May 9, 2008 at 12:06 PM, Bruce Dubbs [EMAIL PROTECTED] wrote:
For reference, see http://wiki.linuxfromscratch.org/blfs/ticket/2533
Another way to solve this is to install multiple bdb versions in
parallel. Most of the distros do it.
--
Tushar Teredesai
mailto:[EMAIL PROTECTED]
DJ Lucas wrote:
Randy McMurchy wrote:
Randy McMurchy wrote these words on 05/07/08 06:37 CST:
Bruce Dubbs wrote these words on 05/07/08 01:20 CST:
Is it time to do a freeze/rc1?
I'm off to work and will look at this, then publish something
13 matches
Mail list logo
