On Thu, Jan 20, 2005 at 05:46:39PM +0900, Horms wrote:
> On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> > On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:2
* Joey Hess <[EMAIL PROTECTED]> [2005-01-20 16:13]:
> mips
> No abiname. Kernel updated and in testing; udebs updated.
> No initrd daily builds since Dec 31 so new udebs untested.
I made the daily build on Dec 31 with the new kernel so udebs are
tested. In any case, I asked Thiemo Seu
On Thu, Jan 20, 2005 at 11:11:14PM +0100, Christian T. Steigies wrote:
> > > I have no idea about the abichanges, m68k uses no abiname? Is that a
> > > problem?
> > The downside of not includeing an abiname in the package name is that
> > past d-i releases will break once the updated kernels and
On Thu, Jan 20, 2005 at 04:58:10PM -0500, Joey Hess wrote:
> Christian T. Steigies wrote:
> > I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make
> > it
> > urgent...: Too young, only 7 of 10 days old
> > For 2.4.27 I am waiting for the latest kernel-source to be released be
On Thu, Jan 20, 2005 at 10:25:47PM +0100, Christian T. Steigies wrote:
> On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
> >
> > Update for current status, 10 days after my first mail:
> >
> > m68k
> > No abiname; not updated. ?
> >
> > [This is another arch that I'd consider
Christian T. Steigies wrote:
> I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
> urgent...: Too young, only 7 of 10 days old
> For 2.4.27 I am waiting for the latest kernel-source to be released before I
> build new images. This is supposed to happen today/tomorrow? I
On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
>
> Update for current status, 10 days after my first mail:
>
> m68k
> No abiname; not updated. ?
>
> [This is another arch that I'd consider releasing d-i rc3 without
> it being updated for the kernel security fixes.]
Joey Hess wrote:
> Before we can release d-i rc3 we need all the kernels updated with at
> least some security fixes, notably the ones that change the kernel
> module ABI, and we need to update things to reflect the new kernel
> "abiname". Here's my understanding of the current status of that:
Upd
On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > > > As far as I know, no other arches except amd64 (not
On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > > As far as I know, no other arches except amd64 (not tracking that) are
> >
> > mips and mipsel have been updated.
On Mon, Jan 10, 2005 at 04:24:27PM -0500, Joey Hess wrote:
> Before we can release d-i rc3 we need all the kernels updated with at
> least some security fixes, notably the ones that change the kernel
> module ABI, and we need to update things to reflect the new kernel
> "abiname". Here's my underst
On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > As far as I know, no other arches except amd64 (not tracking that) are
>
> mips and mipsel have been updated. However, given the new local root
> exploit (fixed in SVN), we'
* Joey Hess wrote:
> Norbert Tretkowski wrote:
> > Updated alpha packages were accepted a few hours ago.
>
> Do you or maybe vorlon plan to rebuild linux-kernel-di-alpha with
> them?
I'll update the package tomorrow.
Norbert
Steve Langasek wrote:
> For 2.4, this requires i2c, kernel-latest-2.4-i386, linux-wlan-ng,
> lm-sensors, and oprofile-source to be ready to go at the same time with
> packages built against the new ABI. Of these, oprofile-source has had a
> recent upload, but has only out-of-date modules (none bui
On Tuesday 11 January 2005 11:54, Christian Perrier wrote:
> For *very very* nasty errors (such as a bad spelling error which would
> make every single Bulgarian user laugh loudly), you may request for an
> update and get a chance that someone takes care of it.
For Dutch I have done several spelli
Norbert Tretkowski wrote:
> Updated alpha packages were accepted a few hours ago.
Do you or maybe vorlon plan to rebuild linux-kernel-di-alpha with them?
--
see shy jo
signature.asc
Description: Digital signature
Quoting Ognyan Kulev ([EMAIL PROTECTED]):
> Specifically for the Bulgarian translation, there aren't any major
> problems that I'm aware of :-) There were some inconsistencies in the
> translation of the 2nd level but I have to refresh my experience with
> debian-installer before complaining a
Christian Perrier wrote:
RC3 or whatever it will be called will be based on the sarge
branch. So, indeed, as far as Bulgarian is concerned, you're already
complete.
However, if you have fixes to the translations, you should commit them
to the sarge branch. Please note, however that no systematic up
Quoting Ognyan Kulev ([EMAIL PROTECTED]):
> Joey Hess wrote:
> >Before we can release d-i rc3
>
> Will translation updates be allowed for RC3? If yes (I hope), what's the
> time frame and to which branch they should go in?
RC3 or whatever it will be called will be based on the sarge
branch. So,
Joey Hess wrote:
Before we can release d-i rc3
Will translation updates be allowed for RC3? If yes (I hope), what's the time
frame and to which branch they should go in?
Regards,
ogi
On Tue, Jan 11, 2005 at 10:12:59AM +0100, Christian Perrier wrote:
> Quoting Colin Watson ([EMAIL PROTECTED]):
> > > What is "quite a few" changes here? I thought the next d-i release was
> > > going to be bugfixes and kernel updates only?
> > I think Christian really meant "quite few" (i.e. "no
Quoting Colin Watson ([EMAIL PROTECTED]):
> > What is "quite a few" changes here? I thought the next d-i release was
> > going to be bugfixes and kernel updates only?
>
> I think Christian really meant "quite few" (i.e. "not many") rather than
> "quite a few" (i.e. "several") here.
Bingo. I hav
* Joey Hess wrote:
> As far as I know, no other arches except amd64 (not tracking that)
> are updated.
Updated alpha packages were accepted a few hours ago.
Norbert
On Mon, Jan 10, 2005 at 04:24:27PM -0500, Joey Hess wrote:
> Before we can release d-i rc3 we need all the kernels updated with at
> least some security fixes, notably the ones that change the kernel
> module ABI, and we need to update things to reflect the new kernel
> "abiname". Here's my underst
On Mon, Jan 10, 2005 at 03:44:37PM -0800, Steve Langasek wrote:
> On Mon, Jan 10, 2005 at 11:17:09PM +0100, Christian Perrier wrote:
> > Quoting Joey Hess ([EMAIL PROTECTED]):
> > > Before we can release d-i rc3 we need all the kernels updated with at
>
> > Should it be called RC3 or "whatever bet
On Mon, Jan 10, 2005 at 11:17:09PM +0100, Christian Perrier wrote:
> Quoting Joey Hess ([EMAIL PROTECTED]):
> > Before we can release d-i rc3 we need all the kernels updated with at
> Should it be called RC3 or "whatever better sounds like an official
> release name"?
> Given that we indeed made
* Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> As far as I know, no other arches except amd64 (not tracking that) are
mips and mipsel have been updated. However, given the new local root
exploit (fixed in SVN), we'll all need to make another round of
updates anyway.
--
Martin Michlmayr
h
Quoting Joey Hess ([EMAIL PROTECTED]):
> Before we can release d-i rc3 we need all the kernels updated with at
Should it be called RC3 or "whatever better sounds like an official
release name"?
Given that we indeed made quite few(?) changes, isn't it time for an
official stamped release?
Before we can release d-i rc3 we need all the kernels updated with at
least some security fixes, notably the ones that change the kernel
module ABI, and we need to update things to reflect the new kernel
"abiname". Here's my understanding of the current status of that:
i386
2.4 and 2.6 upd
29 matches
Mail list logo