Your message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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 message dated Tue, 18 Apr 2006 18:48:14 -0700 (PDT)
with message-id <[EMAIL PROTECTED]>
and subject line Fixed by today's 2.6.16-8 upload
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
Package: initramfs-tools
Version: 0.59b
I've reported this before, but now I've traced it...
During kernel upgrade on S/390 I see this error:
ln: creating symbolic link `/tmp/mkinitramfs_laxXYw//etc/modprobe.d/dasd'
to `/tmp/initramfs_dasd': File exists
The attached trace (which cost me quite
There are disparities between your recently accepted upload and the
override file for the following file(s):
kernel-image-2.6-power3-smp_2.6.16-8_powerpc.deb: package says priority is
extra, override says optional.
kernel-image-2.6-power3_2.6.16-8_powerpc.deb: package says priority is extra,
ove
Accepted:
kernel-image-2.6-power3-smp_2.6.16-8_powerpc.deb
to pool/main/l/linux-2.6/kernel-image-2.6-power3-smp_2.6.16-8_powerpc.deb
kernel-image-2.6-power3_2.6.16-8_powerpc.deb
to pool/main/l/linux-2.6/kernel-image-2.6-power3_2.6.16-8_powerpc.deb
kernel-image-2.6-power4-smp_2.6.16-8_powerpc.d
linux-2.6_2.6.16-8_powerpc.changes uploaded successfully to localhost
along with the files:
linux-2.6_2.6.16-8.dsc
linux-2.6_2.6.16-8.diff.gz
linux-doc-2.6.16_2.6.16-8_all.deb
linux-manual-2.6.16_2.6.16-8_all.deb
linux-patch-debian-2.6.16_2.6.16-8_all.deb
linux-source-2.6.16_2.6.16-8_al
On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote:
> waldi why not add your patch to update-grub to the next stable release?
> kernel-package 8 should be able to cope with the stderr output, no?
Yeah should work, but this have to be checked.
Bastian
--
Suffocating together ... w
maximilian attems a écrit :
severity 363344 important
tags 363344 moreinfo
thanks
cher bertrand,
On Tue, Apr 18, 2006 at 06:04:08PM +0200, BERTRAND Joël wrote:
Package: initramfs-tools
Version: 0.59b
Severity: grave
Arch: sparc
hmm it may be serious, but for now i go for important.
anyway
Your message dated Tue, 18 Apr 2006 11:33:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363032: fixed in linux-2.6 2.6.16-8
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
On Mon, 17 Apr 2006, Andreas Metzler wrote:
> At short glance the respective changes in update-grub seem to be like
> this:
> -echo -n "Searching for splash image... "
> +echo -n "Searching for splash image ... " >&2
> i.e. the newer update-grub is simply sending to stderr instead of
> stdout.
>
Your message dated Tue, 18 Apr 2006 19:00:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#361270: Upgrade of initramfs-tools made kernel unbootable
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
Accepted:
initramfs-tools_0.60.dsc
to pool/main/i/initramfs-tools/initramfs-tools_0.60.dsc
initramfs-tools_0.60.tar.gz
to pool/main/i/initramfs-tools/initramfs-tools_0.60.tar.gz
initramfs-tools_0.60_all.deb
to pool/main/i/initramfs-tools/initramfs-tools_0.60_all.deb
Announcing to debian-deve
initramfs-tools_0.60_i386.changes uploaded successfully to localhost
along with the files:
initramfs-tools_0.60.dsc
initramfs-tools_0.60.tar.gz
initramfs-tools_0.60_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
reopen 362816
stop
>* update-initramfs: Warn in big letters about grub and lilo installs.
> (closes: #362816)
upps that was an typo,
reopening that bug for consideration about stricter udev dependency.
linux-images >= 2.6.16 solve that anyway as they don't need ide.agent,
which missed f
Processing commands for [EMAIL PROTECTED]:
> reopen 362816
Bug#362816: initramfs-tools: Initramfs-tools creates a buggy initrd image file.
Bug reopened, originator not changed.
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(a
Processing commands for [EMAIL PROTECTED]:
> severity 363344 important
Bug#363344: initramfs-tools and HyperSPARC processor
Severity set to `important'.
> tags 363344 moreinfo
Bug#363344: initramfs-tools and HyperSPARC processor
There were no tags set.
Tags added: moreinfo
> thanks
Stopping proc
severity 363344 important
tags 363344 moreinfo
thanks
cher bertrand,
On Tue, Apr 18, 2006 at 06:04:08PM +0200, BERTRAND Joël wrote:
> Package: initramfs-tools
> Version: 0.59b
> Severity: grave
> Arch: sparc
hmm it may be serious, but for now i go for important.
anyway you omitted lots of inform
Package: initramfs-tools
Version: 0.59b
Severity: grave
Arch: sparc
It is impossible to build a ramfs image on a HyperSPARC
workstation. I have try to install etch/sparc on a SS20 that runs with
four HyperSPARC processors. When it boots, system hangs when it tries to
load the ramfs image.
> > I have this problem, and it is not caaauused by the ATI timer bug. I
> > don't have an ATI chipset, and none of the suggesssted fixes for the
> > ATI timer bug (booting with disable_timer_pin_1, noapic, acpi=off,
> > notsc, etc.) has any effect.
>
> Did you upgrade your BIOS? This completely s
Bastian Blank <[EMAIL PROTECTED]> writes:
> On Mon, Apr 17, 2006 at 07:50:59PM +0200, Frederik Schueler wrote:
>> On Sun, Apr 16, 2006 at 02:32:12PM +0200, Bastian Blank wrote:
>> > There are two or so possibilities to do that:
>> > - Build them in the i386 build. This will raise the count of imag
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.10
> retitle 362153 vbi interface in bttv broken
Bug#362153: nxtvepg: Fails to work with kernel 2.6.16
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if
Your upload was successful. These packages are now available:
- initramfs-tools
If you think you found a bug or just want to contact us please send
an email to [EMAIL PROTECTED] Thanks for using our service.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
Processing commands for [EMAIL PROTECTED]:
> reassign 362153 linux-source-2.6.16
Bug#362153: nxtvepg: Fails to work with kernel 2.6.16
Bug reassigned from package `nxtvepg' to `linux-source-2.6.16'.
> retittle 362153 vbi interface in bttv broken
Unknown command or malformed arguments to command.
Your message dated Tue, 18 Apr 2006 07:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362568: fixed in initramfs-tools 0.60
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 n
Your message dated Tue, 18 Apr 2006 07:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362816: fixed in initramfs-tools 0.60
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 n
Your message dated Tue, 18 Apr 2006 07:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358917: fixed in initramfs-tools 0.60
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 n
Your message dated Tue, 18 Apr 2006 07:02:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348147: fixed in initramfs-tools 0.60
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 n
Your message dated Tue, 18 Apr 2006 07:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358649: fixed in initramfs-tools 0.60
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 n
Package: linux-image-2.6.16-1-686
Version: 2.6.16-7
Severity: normal
The advansys module (for advansys SCSI cards) is no longer part of the
package. It was available in linux-image-2.6.15-1-686.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'un
On Tue, Apr 18, 2006 at 05:48:23AM -0400, Andrew Schulman wrote:
> I have this problem, and it is not caaauused by the ATI timer bug. I don't
> have an ATI chipset, and none of the suggesssted fixes for the ATI timer
> bug (booting with disable_timer_pin_1, noapic, acpi=off, notsc, etc.) has
>
Forgot to mention an important fact: the timer and keyboard work normally
for the first 5-30 hours after boot. I haven't been able to determine any
particular events (e.g. network traffic as one person reported) that
trigger the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
I have this problem, and it is not caaauused by the ATI timer bug. I don't
have an ATI chipset, and none of the suggesssted fixes for the ATI timer
bug (booting with disable_timer_pin_1, noapic, acpi=off, notsc, etc.) has
any effect.
My system clock runs about 5% fast, with a lot of aariab
Your message dated Tue, 18 Apr 2006 11:13:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line DMA timeout causing filesystem corruption
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 n
40 matches
Mail list logo
