Your message dated Sat, 8 Jul 2006 22:48:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#377423: linux-image-2.6.16-2-em64t-p4-smp: Fails to find
boot device (AHCI ICH7 Family)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem ha
Package: linux-image-2.6.16-2-em64t-p4-smp
Version: 2.6.16-14
Severity: serious
Justification: 3
Hardware:
ASUS P5WD2
Maxtor SATA 300G
DELL monitor with 4 usb card readers FPW2004
Configuration:
Maxtor hard drive connected to SATA port 1 (sda)
The ATA bus is configured in BIOS to AHCI mode.
Prob
Processing commands for [EMAIL PROTECTED]:
> reassign 376488 linux-2.6
Bug#376488: linux-headers-2.6.17-1-686: unmet dependencies
Bug reassigned from package `linux-headers-2.6.17-1-686' to `linux-2.6'.
> forcemerge 368544 376488
Bug#368544: linux-headers-2.6.17-rc3-amd64-k8: depends on non-exist
Your message dated Sat, 08 Jul 2006 11:49:02 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#376012: fixed in linux-2.6.16 2.6.16-16
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 case it is
Your message dated Sat, 08 Jul 2006 11:49:02 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#376926: fixed in linux-2.6.16 2.6.16-16
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 case it is
linux-2.6.16_2.6.16-16_powerpc.changes uploaded successfully to localhost
along with the files:
linux-2.6.16_2.6.16-16.dsc
linux-2.6.16_2.6.16-16.diff.gz
linux-doc-2.6.16_2.6.16-16_all.deb
linux-manual-2.6.16_2.6.16-16_all.deb
linux-patch-debian-2.6.16_2.6.16-16_all.deb
linux-source-2.6
Accepted:
linux-2.6.16_2.6.16-16.diff.gz
to pool/main/l/linux-2.6.16/linux-2.6.16_2.6.16-16.diff.gz
linux-2.6.16_2.6.16-16.dsc
to pool/main/l/linux-2.6.16/linux-2.6.16_2.6.16-16.dsc
linux-doc-2.6.16_2.6.16-16_all.deb
to pool/main/l/linux-2.6.16/linux-doc-2.6.16_2.6.16-16_all.deb
linux-header
Processing commands for [EMAIL PROTECTED]:
> severity 376488 grave
Bug#376488: linux-headers-2.6.17-1-686: unmet dependencies
Severity set to `grave' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
severity 376488 grave
thanks
Rationale: bug renders package unusable.
--
.Adam Di [EMAIL PROTECTED]http://www.debian.org/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> reassign 377375 linux-2.6
Bug#377375: linux-headers-2.6.17-1-k7: Requires linux-kbuild-2.6.17 which does
not exist
Bug reassigned from package `linux-headers-2.6.17-1-k7' to `linux-2.6'.
> forcemerge 368544 377375
Bug#368544: linux-headers-2.6.17-rc3-
Package: linux-headers-2.6.17-1-k7
Severity: grave
Justification: renders package unusable
Subject says it all. This headers package has been out here for over
a week without a corresponding kbuild package.
Kindly provide the kbuild package, or fix the headers package not to require
the kbuild p
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Your message dated Sat, 08 Jul 2006 07:13:46 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368544: fixed in linux-kbuild-2.6 2.6.17-1
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 case it
Accepted:
linux-kbuild-2.6.17_2.6.17-1_powerpc.deb
to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6.17_2.6.17-1_powerpc.deb
linux-kbuild-2.6_2.6.17-1.diff.gz
to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.17-1.diff.gz
linux-kbuild-2.6_2.6.17-1.dsc
to pool/main/l/linux-kbuild-2.6/linux-
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> severity 377350 normal
Bug#377350: linux-modules-2.6.16-2-xen-686_2.6.16-15 depends on initramfs-tools
Severity set to `normal' from `important'
>
End of message, stopping processing
Package: linux-modules-2.6.16-2-xen-686
Version: 2.6.16-15
Severity: important
linux-modules-2.6.16-2-xen-686 only contains modules for xen domains,
and should not require any initrd or initramfs tools.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (
Package: linux-2.6
Severity: normal
Tags: patch
Host protected area (sometimes called hidden protected area) is used to
have a hidden partition at the end of the harddrive.
The linux kernel disables HPA on boot and makes the whole harddrive
available to the kernel. I have a /home partition overlap
Your message dated Sat, 08 Jul 2006 11:40:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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 case it is now your responsibility to reopen the
* Andi Kleen <[EMAIL PROTECTED]> [2006-07-07 23:28]:
> Is that a board with VIA chipset?
Yes, according to lspci, there's a VIA K8T800Pro and VT8237.
:00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
:00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
* Bastian Blank <[EMAIL PROTECTED]> [2006-07-07 20:13]:
> linux-2.6* is not binNMU-able. This upload includes source changes.
This latter has nothing to do with the former at all.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
35 matches
Mail list logo
