On Tuesday 05 February 2008, dann frazier wrote:
On Mon, Feb 04, 2008 at 01:53:43AM +0100, Frans Pop wrote:
Finally I created the etch-support udeb which does two things:
1) add an early base-installer hook script that sets the 'altmeta'
template
2) add an partman init.d hook script
On Sun, Feb 03, 2008 at 05:23:14PM -0200, Otavio Salvador wrote:
As suggested by Frans, with many good points, we'll release with
2.6.22 but just after it, we'll start to work to release another beta
with 2.6.24 kernel.
This should allow us to install a etchnhalf 2.6.24 on hardware supported
On Mon, Feb 04, 2008 at 01:53:43AM +0100, Frans Pop wrote:
Finally I created the etch-support udeb which does two things:
1) add an early base-installer hook script that sets the 'altmeta'
template
2) add an partman init.d hook script that changes the default
inode_size from 256 to 128
* dann frazier [EMAIL PROTECTED] [2008-02-05 01:13]:
On Sun, Feb 03, 2008 at 05:23:14PM -0200, Otavio Salvador wrote:
As suggested by Frans, with many good points, we'll release with
2.6.22 but just after it, we'll start to work to release another beta
with 2.6.24 kernel.
This should
Martin Michlmayr [EMAIL PROTECTED] writes:
Given we're doing a beta based on 2.6.22 now, how quickly could we get
another beta based on 2.6.24 out? Can you be done relatively quickly
after the beta based on 2.6.22?
I guess we can.
d-i itself isn't receiving deeply changes latelly (except
On Monday 04 February 2008, Frans Pop wrote:
You've probably seen that a new grub has been uploaded, which should
solve this issue for unstable and etch^Wlenny.
However, there are also plans to use the Lenny Beta release of the
installer for Etch+1/2 installations: installs of Etch, but with
* Otavio Salvador [EMAIL PROTECTED] [2008-02-05 16:43]:
d-i itself isn't receiving deeply changes latelly (except latest Frans
partman improvements but that has been very well test by him, as
usual) and other minor things. I guess we could do another in begin of
April or so, dunno for sure.
I
On Sunday 03 February 2008, Otavio Salvador wrote:
Also note that I have _never_ intended the massbuild script to be used
for mass uploads when switching to a new kernel minor version [1]. I
still feel that porters should be responsible for checking their
configurations and included
Quoting Frans Pop ([EMAIL PROTECTED]):
Sorry for the long explanation below, but I really want people to understand
what is happening and why so we are agreed on this implementation and don't
have nasty surprises after the point release.
Your mail (which I read carefully) requires ACK from
Kartik Mistry [EMAIL PROTECTED] writes:
On Feb 4, 2008 12:53 AM, Otavio Salvador [EMAIL PROTECTED] wrote:
With all comments that has been sent to this thread, I've changed the
timeline to the following:
snip
+--+---+
|March 3, 2007
Frans Pop [EMAIL PROTECTED] writes:
Before begin to answer, I want to say that I agree with you and will
follow your advice of do a 2.6.22 based release and prepare a beta2
changing the kernel just after beta1 release.
On Thursday 31 January 2008, Otavio Salvador wrote:
- kernel to release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With all comments that has been sent to this thread, I've changed the
timeline to the following:
+--+---+
| Date | What happens |
On Sunday 03 February 2008, Otavio Salvador wrote:
- e2fsprogs inode size change
Lastest release[1] changed the default inode size to 256
bytes. This is not yet on lenny but is already available on sid and
will hit lenny in few days.
1.
Frans Pop [EMAIL PROTECTED] writes:
On Sunday 03 February 2008, Otavio Salvador wrote:
- e2fsprogs inode size change
Lastest release[1] changed the default inode size to 256
bytes. This is not yet on lenny but is already available on sid and
will hit lenny in few days.
On Sunday 03 February 2008, Frans Pop wrote:
I have been quite disappointed that there was no real follow-up to my
mails, which now leaves us in the situation that there is basically no
support yet to select the correct kernel for etch+1/2.
Being the sucker that I am, I did start to look into
Hello Ted,
On Wed, 30 Jan 2008 08:00:20 -0500, Ted Tso wrote:
If the grub maintainers can't figure out a way to break up the
monolithic patch quickly, or to get it incorporated into Debian, or
get it upstreamed ASAP, one of the things that I could do is change
mke2fs.conf in the udeb file, so
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.
Your message has been sent to the package maintainer(s):
[EMAIL PROTECTED] (Theodore Y.
Frans Pop [EMAIL PROTECTED] writes:
...
You've probably seen that a new grub has been uploaded, which should solve
this issue for unstable and etch.
Lenny
...
--
O T A V I OS A L V A D O R
-
E-mail:
On Feb 4, 2008 12:53 AM, Otavio Salvador [EMAIL PROTECTED] wrote:
With all comments that has been sent to this thread, I've changed the
timeline to the following:
snip
+--+---+
|March 3, 2007 |planned release date
On Fri, Feb 01, 2008 at 09:51:07PM -0500, Joey Hess wrote:
It's far to early to switch d-i to 2.6.24, especially since it drops
support for most of /proc/acpi, including the parts used by
laptop-detect.
I suspect you already know this, but for the record, that's not an
intrinsic property of
Joey Hess [EMAIL PROTECTED] writes:
Otavio Salvador wrote:
We have 2.6.22 as a safe bed on lenny now and their udebs are there
too however since EtchAndHalf intends to release with 2.6.24 and it
has been uploaded to sid already I'm considering a better option to
us to release
Hi,
On Fri, Feb 01, 2008 at 09:51:07PM -0500, Joey Hess wrote:
It's far to early to switch d-i to 2.6.24, especially since it drops
support for most of /proc/acpi, including the parts used by
laptop-detect.
I still think this switch was an extremely premature and really, really
bad idea.
We
On Saturday 02 February 2008, Otavio Salvador wrote:
It's far to early to switch d-i to 2.6.24, especially since it drops
support for most of /proc/acpi, including the parts used by
laptop-detect.
I've uploaded laptop-detect with this fixed (using your provided
patch) so it is solved on
On Thursday 31 January 2008, Otavio Salvador wrote:
- kernel to release
We have 2.6.22 as a safe bed on lenny now and their udebs are there
too however since EtchAndHalf intends to release with 2.6.24 and it
has been uploaded to sid already I'm considering a better option to
us
On Friday 01 February 2008, dann frazier wrote:
Is there anything special we need to add to deal with etch 1/2
kernel metapackages? We were talking about using a name like
linux-image-2.6-686-etchnhalf.
As I explained in my mails re etch+1/2 some time back [1] , D-I simply will
not install
Quoting Frans Pop ([EMAIL PROTECTED]):
My conclusion is that unless you are willing to significantly delay the Beta
release, I don't see any way you can do the release with 2.6.24.
I would suggest to do the release with 2.6.22 and keep the option to do a
quick new release based on 2.6.24.
Otavio Salvador wrote:
We have 2.6.22 as a safe bed on lenny now and their udebs are there
too however since EtchAndHalf intends to release with 2.6.24 and it
has been uploaded to sid already I'm considering a better option to
us to release with it.
linux-2.6 has been built
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ Reply-To adjusted to debian-boot so we can keep this discussion in a
single mailing list ]
Hello folks,
I've been working at migrations of packages for lenny and I think
we're more or less fine to define a timeline to the end of Febuary for
the
On Thu, Jan 31, 2008 at 08:04:23PM -0200, Otavio Salvador wrote:
- kernel to release
We have 2.6.22 as a safe bed on lenny now and their udebs are there
too however since EtchAndHalf intends to release with 2.6.24 and it
has been uploaded to sid already I'm considering a better
29 matches
Mail list logo
