Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 13 May 2005 23:21:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
tag 266591 + fixed
tag 279382 + fixed
tag 285767 + fixed
tag 290329 + fixed
tag 291386 + fixed
tag 292080 + fixed
tag 295412 + fixed
tag 295422 + fixed
tag 296894 + fixed
tag 297724 + fixed
tag 298727 + fixed
tag 301455 + fixed
tag 303281 + fixed
tag 303401 + fixed
tag 306219 + fixed
quit
This me
Processing commands for [EMAIL PROTECTED]:
> tag 266591 + fixed
Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device
Tags were: pending moreinfo
Tags added: fixed
> tag 279382 + fixed
Bug#279382: 64-bit kernel -> ldd -> mkinitrd issue
Tags were: sarge patch
Bug#292080: error ins
Accepted:
initrd-tools_0.1.79.dsc
to pool/main/i/initrd-tools/initrd-tools_0.1.79.dsc
initrd-tools_0.1.79.tar.gz
to pool/main/i/initrd-tools/initrd-tools_0.1.79.tar.gz
initrd-tools_0.1.79_all.deb
to pool/main/i/initrd-tools/initrd-tools_0.1.79_all.deb
Announcing to debian-devel-changes@lists
initrd-tools_0.1.79_i386.changes uploaded successfully to localhost
along with the files:
initrd-tools_0.1.79.dsc
initrd-tools_0.1.79.tar.gz
initrd-tools_0.1.79_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Processing commands for [EMAIL PROTECTED]:
> severity 308682 important
Bug#308682: pcmcia-cs-udeb: pcmcia with kernel 2.6 hang up the machine in a
Toshiba Satellite A80-131, with 2.4 there is no problem.
Severity set to `important'.
> reassign 308682 kernel-source-2.6.8
Bug#308682: pcmcia-cs-ude
Accepted:
kernel-doc-2.6.11_2.6.11-4_all.deb
to pool/main/k/kernel-source-2.6.11/kernel-doc-2.6.11_2.6.11-4_all.deb
kernel-patch-debian-2.6.11_2.6.11-4_all.deb
to
pool/main/k/kernel-source-2.6.11/kernel-patch-debian-2.6.11_2.6.11-4_all.deb
kernel-source-2.6.11_2.6.11-4.diff.gz
to pool/main/
Your message dated Fri, 13 May 2005 17:17:52 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307553: fixed in kernel-source-2.6.11 2.6.11-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the cas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I created the pwc-source package [1] and now its in new queue pending to be
included on sid [2].
Sean Finney its my sponsor but We have no experience on kernel modules
packages. And We want to make
pre-built modules for official debian kernel in orde
kernel-source-2.6.11_2.6.11-4_powerpc.changes uploaded successfully to localhost
along with the files:
kernel-source-2.6.11_2.6.11-4.dsc
kernel-source-2.6.11_2.6.11-4.diff.gz
kernel-patch-debian-2.6.11_2.6.11-4_all.deb
kernel-source-2.6.11_2.6.11-4_all.deb
kernel-tree-2.6.11_2.6.11-4_all.
Accepted:
kernel-build-2.6.11-power3-smp_2.6.11-2_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.11/kernel-build-2.6.11-power3-smp_2.6.11-2_powerpc.deb
kernel-build-2.6.11-power3_2.6.11-2_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.11/kernel-build-2.6.11-power3_2.6.11-2_powerpc.
kernel-patch-powerpc-2.6.11_2.6.11-2_powerpc.changes uploaded successfully to
localhost
along with the files:
kernel-patch-powerpc-2.6.11_2.6.11-2.dsc
kernel-patch-powerpc-2.6.11_2.6.11-2.tar.gz
kernel-headers-2.6.11-powerpc_2.6.11-2_powerpc.deb
kernel-image-2.6.11-power3_2.6.11-2_powerpc.
I had the same problem after the latest ubuntu upgrade. I fixed it by
adding an initscript which removes the mapper device before crypdisks.
It still asks a password, so it can't be used with remote reboots.
Not directly related to this bug, but I suggest also that the linurc
script could print s
Processing commands for [EMAIL PROTECTED]:
> reassign 308878 kernel-image-2.6.10-1-686-smp
Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
Bug reassigned from package `kernel' to `kernel-image-2.6.10-1-686-smp'.
> --
Stopping processing here.
Please contact me if you need assistance.
Package: kernel-image
Version: 2.6.10-1-686-smp and 2.6.11-1-686-smp
Severity: Grave
The latest smp kernels fails to boot due to the root partiton is not
found, resulting in a kernel panic. Kernels 2.6.8 and 2.6.9 boot OK.
Hardware is dual Celerons.
When installing these kernels I get an error no
Authentic replica Rolex and other watches for gentlemen
and ladies from just $229
Use this promotional link to get best ever prices:
http://www.replicas4me.net
teenage mq salish zk dime uo convey au
chadwick zjz diminution mgs [2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Fri, 2005-05-13 at 11:53 -0400, Joey Hess wrote:
> dann frazier wrote:
> > On Thu, 2005-05-12 at 10:50 -0400, Joey Hess wrote:
> > > Horms wrote:
> > > > ia64: version in Sarge: 2.6.8-12
> > > >
> > > > http://svn.debian.org/wsvn/kernel/trunk/kernel/ia64/kernel-image-2.6.8-ia64-2.6.8/debian
On Fri, 2005-05-13 at 18:33 +0900, Horms wrote:
> In the case of the ia64-ptrace fix,
> I am not sure if this code is needed by subsequent security fixes
> or not.
I needed that to form a baseline to backport the fix for CAN-2005-0136.
The previous baseline had incompatible changes in ivt.S.
> Michael,
>
> All I can say at this point is that it didn't work without specifying
> the kernel argument. As far as 2.6.8 goes, it didn't work period. I
> tried it with the kernel arg and it didn't work, but it did work with
> 2.6.12-rc4 and 2.6.11.8. However again, I did need to explicitly give
dann frazier wrote:
> On Thu, 2005-05-12 at 10:50 -0400, Joey Hess wrote:
> > Horms wrote:
> > > ia64: version in Sarge: 2.6.8-12
> > >
> > > http://svn.debian.org/wsvn/kernel/trunk/kernel/ia64/kernel-image-2.6.8-ia64-2.6.8/debian/changelog?op=file&rev=0&sc=0
> >
> > Will -14 will be an ABI c
Package: kernel-source-2.6.11
Version: 2.6.11-3
Severity: important
When running an em64t kernel with either the megaraid driver or the newer
megaraid_mbox driver, and the machine in question has 4GiB of memory,
reads/writes past the 130GiB mark (approximately) of a partition on the
logical scsi
Hi,
I have been working on this update issue and I am happy to report that
I have made good progress.
Firstly, to clarify, I am working on two sets of updates.
A testing-security update, which will only include security fixes.
And a testing-proposed-updates, which will include some other fixes as
On Fri, May 13, 2005 at 09:54:13AM +0100, Colin Watson wrote:
> FWIW, MODULES=dep works fine for me on my PowerBook.
>
> I think this change is probably worth it - we've had a number of issues
> in the past with large initrds on powerpc.
Thanks Colin, ...
BTW, on a unrelated topic, have you also
FWIW, MODULES=dep works fine for me on my PowerBook.
I think this change is probably worth it - we've had a number of issues
in the past with large initrds on powerpc.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> reassign 308878 kernel
Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
Warning: Unknown package 'kernel-image'
Bug reassigned from package `kernel-image' to `kernel'.
>
En
39 matches
Mail list logo
