Package: linux-2.6
Version: 2.6.18.dfsg.1-12
How surprised I was after booting linux-image-2.6.18-4-xen-686 that it
does not like my CPU.
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Celeron(R) M processor 1.30GHz
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yves-Alexis Perez wrote:
> Package: linux-2.6
> Severity: wishlist
>
> Hi,
>
> ams is the Apple Motion Sensor present in various powerbooks (and maybe
> macbooks pro). Values from the sensor can be read from linux using the
> "ams" module now present
On lun, 2007-05-28 at 10:01 +0200, Jonas Smedegaard wrote:
> > Could this module be enabled on Debian kernel for platforms that
> support
> > it?
>
> From drivers/hwmon/Kconfig it seems the driver is only for 32bit
> PowerMacs.
Could it be enabled for 32bit powermacs. Or even only for powerbooks
(CC maintainer of procps as a heads-up)
On Monday 21 May 2007 22:36, Frans Pop wrote:
> My hercules s/390 emulator no longer receives packets sent from other
> boxes to the external IP address it has on the host system. It appears
> that iptables prerouting is broken somehow.
Update on this issue
Processing commands for [EMAIL PROTECTED]:
> reassign 425960 linux-image-2.6.21-1-prep
Bug#425960: initramfs-tools: prep ppc root= not present
Bug reassigned from package `initramfs-tools' to `linux-image-2.6.21-1-prep'.
> --
Stopping processing here.
Please contact me if you need assistance.
D
This is on upstream bugzilla, and there's a patch and a workaround:
http://bugzilla.kernel.org/show_bug.cgi?id=7201
I didn't know if I should set the forwarded and/or patch tag, since I'm
not a kernel team member...
--
Damián Viano(Des) ¯ ¯ - _ _ - ¯ ¯
GPG: 0x6EB9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yves-Alexis Perez wrote:
> On lun, 2007-05-28 at 10:01 +0200, Jonas Smedegaard wrote:
>>> Could this module be enabled on Debian kernel for platforms that
>> support
>>> it?
>> From drivers/hwmon/Kconfig it seems the driver is only for 32bit
>> PowerMa
On lun, 2007-05-28 at 11:47 +0200, Jonas Smedegaard wrote:
> There's no Linux kernel officially compiled for Debian that is
> targeted
> at powerbooks only.
>
Yeah but it can be enabled for 32bits powermacs. It won't load on
powermacs without hardware, but like every module.
--
Yves-Alexis
--
forwarded 397975 http://bugzilla.kernel.org/show_bug.cgi?id=7201
tags 397975 + upstream
thanks
> I didn't know if I should set the forwarded and/or patch tag, since I'm
> not a kernel team member...
I'm not either, but it is allowed. I'm not sure if the kernel team will
want to apply the patch o
Processing commands for [EMAIL PROTECTED]:
> forwarded 397975 http://bugzilla.kernel.org/show_bug.cgi?id=7201
Bug#397975: /boot/vmlinuz-2.6.18-1-k7: Oops when plugging USB Nokia phone
Noted your statement that Bug has been forwarded to
http://bugzilla.kernel.org/show_bug.cgi?id=7201.
> tags 3979
* Sven Luther ([EMAIL PROTECTED]) [070528 12:14]:
> On Mon, May 28, 2007 at 11:17:39AM +0200, Bastian Blank wrote:
> > On Mon, May 28, 2007 at 08:38:24AM +0200, Joey Schulze wrote:
> > > I can understand the latter. However, maybe it was just a mistake and
> > > waldi didn't want to remove Sven bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yves-Alexis Perez wrote:
> On lun, 2007-05-28 at 11:47 +0200, Jonas Smedegaard wrote:
>> There's no Linux kernel officially compiled for Debian that is
>> targeted
>> at powerbooks only.
>>
> Yeah but it can be enabled for 32bits powermacs. It won't lo
* Andreas Barth ([EMAIL PROTECTED]) [070528 12:28]:
> It seems that waldi doesn't want to do it, and also not to give any
> statement that he wanted to kick you out. I consider this a very bad
> behaviour, at least. And not acceptable.
After some more pressure on IRC, your commit access has been r
found 423040 2.6.21-2
thanks
-pkg linux-2.6 ver 2.6.20-3
- linux-2.6-2.6.20/Documentation/netlabel/draft-ietf-cipso-ipsecurity-01.txt
+pkg linux-2.6 ver 2.6.21-2
+ linux-2.6-2.6.21/Documentation/netlabel/draft-ietf-cipso-ipsecurity-01.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
Processing commands for [EMAIL PROTECTED]:
> found 423040 2.6.21-2
Bug#423040: Source package contains non-free IETF RFC/I-D
Bug marked as found in version 2.6.21-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
On Mon, May 28, 2007 at 12:28:16PM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [070528 12:14]:
> > On Mon, May 28, 2007 at 11:17:39AM +0200, Bastian Blank wrote:
> > > On Mon, May 28, 2007 at 08:38:24AM +0200, Joey Schulze wrote:
> > > > I can understand the latter. However, ma
On lun, 2007-05-28 at 12:24 +0200, Jonas Smedegaard wrote:
> > Yeah but it can be enabled for 32bits powermacs. It won't load on
> > powermacs without hardware, but like every module.
>
>
> I see no problem simply enabling it globally, and let the Linux code
> resolve the architectures relevant o
On Mon, May 28, 2007 at 12:41:59PM +0200, Andreas Barth wrote:
> * Andreas Barth ([EMAIL PROTECTED]) [070528 12:28]:
> > It seems that waldi doesn't want to do it, and also not to give any
> > statement that he wanted to kick you out. I consider this a very bad
> > behaviour, at least. And not acce
Sven Luther wrote:
> > After some more pressure on IRC, your commit access has been restored.
>
> It is not enough, i want the suspension revoked, since it was a stupid
> decision, which has achieved nothing except worsen the situation, and
> was taken contrary to the DAMs procedure, and in a shad
On Monday 28 May 2007 11:11, Frans Pop wrote:
> Somehow this causes default ipv4 settings defined in /etc/sysctl.conf
> to no longer be applied to eth0.
Quoting Herbert Xu (emphasis is mine):
"Changing the value in default only affects interfaces which are
*registered* afterwards. Previously the
* Sven Luther ([EMAIL PROTECTED]) [070528 13:23]:
> [...]
Sven, this whole thread is about that your commit access to the kernel
svn repro was revoked without anyone telling you. What then happened is
that the alioth admins published that waldi revoked the access, waldi
refused to comment to it, a
On Mon, May 28, 2007 at 01:05:41PM +0200, Frans Pop wrote:
> Quoting Herbert Xu (emphasis is mine):
> "Changing the value in default only affects interfaces which are
> *registered* afterwards. Previously they affected interfaces which are
> *brought up* afterwards.
>
> I'll talk to others to s
Package: linux-2.6
Version: 2.6.21-4
Severity: important
The boot failed with the following messages.
Linux version 2.6.21-1-parisc64-smp (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc
version 4.1.37
FP[0] enabled: Rev 1 Model 16
The 64-bit Kernel has started...
Initialized PDC Console for debugging
Package: initramfs-tools
Version: 0.87b
Severity: critical
Tags: patch
Justification: breaks the whole system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I cross-compiled an arm kernel from linux-source-2.6.21 using make-kpkg. After
installing it on my Linksys NSLU2, the system became unbootab
Package: initramfs-tools
Version: 0.88
Severity: important
Hi,
there seems to be something wrong with recent changes to hook-functions.
With initramfs-tools 0.88:
[EMAIL PROTECTED]:~# LANG=C dpkg-reconfigure linux-image-2.6.22-rc3
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs
On Monday 28 May 2007 15:06, Frans Pop wrote:
> The boot failed with the following messages.
Additional info: this was the official package (grabbed from incoming).
It was compiled using (from the build log [1]):
libc6-dev_2.5-7
linux-kernel-headers_2.6.18-7
gcc-4.1_4.1.2-8
g++-4.1_4.1.2-8
binuti
On Mon, May 28, 2007 at 04:33:56PM +0200, Frans Pop wrote:
> On Monday 28 May 2007 15:06, Frans Pop wrote:
> > The boot failed with the following messages.
>
> Additional info: this was the official package (grabbed from incoming).
>
> It was compiled using (from the build log [1]):
> libc6-dev_2
Package: linux-image-2.6.18-4-k7
Version: 2.6.18.dfsg.1-12etch2
Severity: important
Our office server had an ext3 volume remount itself read-only after an
error in handing a disk write. This is the first time this error or
anything like it has occurred. Another ext3 file system on the same
phys
On Mon, May 28, 2007 at 01:03:29PM +0200, Joey Schulze wrote:
> Sven Luther wrote:
> > > After some more pressure on IRC, your commit access has been restored.
> >
> > It is not enough, i want the suspension revoked, since it was a stupid
> > decision, which has achieved nothing except worsen the
On Mon, May 28, 2007 at 01:33:28PM +0200, Andreas Barth wrote:
> * Sven Luther ([EMAIL PROTECTED]) [070528 13:23]:
> > [...]
>
> Sven, this whole thread is about that your commit access to the kernel
This whole thread is about me being stopped from doing meaningful debian
technical contribution a
Sven, stop it already!
We've seen this several times already.
You're not bringing up anything new.
You're not helping yourself if you continue.
Regards,
Joey
--
It's practically impossible to look at a penguin and feel angry.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
On Mon, May 28, 2007 at 05:40:26PM +0200, Joey Schulze wrote:
> Sven, stop it already!
why should i ? The times i stopped, i got punished worse without
provocation ?
> We've seen this several times already.
Yes, so, what ? I have seen that if i don't make a fuss over this,
everyone is pretty hap
Package: linux-image-2.6.21-1-powerpc
Version: 2.6.21-4
Severity: important
File: kernel
I don't know if this is a hardware problem or a kernel bug. the
same hardware had served correctly for years, so I sincerely hope it's a
kernel bug...
I'm not sure when the problem started to display...
a c
kernel-image-2.6.8-sparc_2.6.8-16_sparc.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-sparc_2.6.8-16.dsc
kernel-image-2.6.8-sparc_2.6.8-16.tar.gz
kernel-headers-2.6.8-4_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb
kernel-image
kernel-image-2.6.8-alpha_2.6.8-17_alpha.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-alpha_2.6.8-17.dsc
kernel-image-2.6.8-alpha_2.6.8-17.tar.gz
kernel-headers-2.6.8-4_2.6.8-17_alpha.deb
kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb
kernel-image-2.6
kernel-image-2.6.8-s390_2.6.8-6_s390.changes uploaded successfully to localhost
along with the files:
kernel-image-2.6.8-s390_2.6.8-6.dsc
kernel-image-2.6.8-s390_2.6.8-6.tar.gz
kernel-patch-2.6.8-s390_2.6.8-6_all.deb
kernel-headers-2.6.8-4_2.6.8-6_s390.deb
kernel-image-2.6.8-4-s390_2.6.8-
kernel-image-2.6.8-amd64_2.6.8-17_i386.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-amd64_2.6.8-17.dsc
kernel-image-2.6.8-amd64_2.6.8-17.tar.gz
kernel-headers-2.6.8-13_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb
kernel-image
kernel-patch-powerpc-2.6.8_2.6.8-13_powerpc.changes uploaded successfully to
localhost
along with the files:
kernel-patch-powerpc-2.6.8_2.6.8-13.dsc
kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz
kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb
ker
kernel-image-2.6.8-i386_2.6.8-17_i386.changes uploaded successfully to localhost
along with the files:
kernel-image-2.6.8-i386_2.6.8-17.dsc
kernel-image-2.6.8-i386_2.6.8-17.tar.gz
kernel-headers-2.6.8-4_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb
kernel-image-2.6.8-4-68
kernel-image-2.6.8-ia64_2.6.8-15_ia64.changes uploaded successfully to localhost
along with the files:
kernel-image-2.6.8-ia64_2.6.8-15.dsc
kernel-image-2.6.8-ia64_2.6.8-15.tar.gz
kernel-headers-2.6.8-4_2.6.8-15_ia64.deb
kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
kernel-image-2.6-it
kernel-source-2.6.8_2.6.8-17_ia64.changes uploaded successfully to localhost
along with the files:
kernel-source-2.6.8_2.6.8-17.dsc
kernel-source-2.6.8_2.6.8-17.diff.gz
kernel-patch-debian-2.6.8_2.6.8-17_all.deb
kernel-source-2.6.8_2.6.8-17_all.deb
kernel-tree-2.6.8_2.6.8-17_all.deb
ker
kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
kernel-headers-2.6-mckinley
(new) kernel-headers-2.6.8-4_2.6.8-6_s390.deb optional devel
Header files related to Linux kernel version 2.6.8 on IBM S/390
This package provides kernel header files for version 2.6.8 on IBM S/390,
for sites that want the latest kernel headers. Please read
/usr/share/doc/kernel-headers-2.6.8/de
(new) kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb optional devel
Linux kernel headers 2.6.8 for generic x86_64 systems
This package provides kernel header files for version 2.6.8 on all x86_64
systems, for sites that want the latest kernel headers. Please read
/usr/share/doc/kernel-h
(new) kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb optional devel
Linux kernel headers 2.6.8 on 386
This package provides kernel header files for version 2.6.8 on 386.
Please read /usr/share/doc/kernel-headers-2.6.8-4/debian.README.gz for
details
(new) kernel-headers-2.6.8-4-686-smp_2.6.8-17_i38
(new) kernel-build-2.6.8-4_2.6.8-16_sparc.deb optional devel
Headers for building modules for Linux 2.6.8
This package provides kernel header files for building modules for the
precompiled kernel images on the 64-bit SPARC architecture (uniprocessor and
multiprocessor.)
(new) kernel-headers-2.6.
(new) kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb optional devel
Linux kernel headers 2.6.8 on Alpha
This package provides kernel header files for version 2.6.8 on
the Alpha architecture,
for sites that want the latest kernel headers.
Please read /usr/share/doc/kernel-headers-2.6.8-4-gene
Your message dated Mon, 28 May 2007 19:06:58 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Problem might be due to defect sectors
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
(new) kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb optional devel
build infrastructure for kernel version 2.6.8-4-power3-smp
.
Together with kernel-headers-2.6.8-4, this package provides the
infrastructure for building additional modules for 2.6.8-4-power3-smp.
(new) kernel-build-2.6.8-4
On Monday 28 May 2007 16:19, Sven Luther wrote:
Hi !
I'm not involved in your job at all, but I am a member of debian-kernel list
because I like to read about : "What is new in this area ?" What I can see
here is only personal issues unfortunately. I am telling You it is not worth
it... People
Your message dated Mon, 28 May 2007 12:49:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422273: xserver-xorg-input-evdev: Num Lock light indicator
stopped functioning
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been d
On Mon, May 28, 2007 at 06:11:29PM +0100, Paweł Krzywicki wrote:
> On Monday 28 May 2007 16:19, Sven Luther wrote:
>
> Hi !
> I'm not involved in your job at all, but I am a member of debian-kernel list
> because I like to read about : "What is new in this area ?" What I can see
> here is only p
Package: kernel-image-2.6-em64t-p4-smp
Followup-For: Bug #409616
As kdetv does not crash my machine now, when using the correct kernel
image package "linux-image-2.6.20-1-amd64_2.6.20-3", this bug can be
closed.
Best regards
Torquil Sørensen
-- System Information:
Debian Release: lenny/sid
APT
Package: linux-source-2.6.18
Version: 2.6.18.dfsg.1-12etch2
Dear Co-Worker!
Well I actually do not know who to blame, but my system shows some strange
behaviour during booting. On Saturday, it claimed that ide_cd is missing,
yesterday I have got a lot of "hda: dma_intr: status=0x58"-error messa
On Monday 28 May 2007 19:06, Sven Luther wrote:
>
> No, we are volunteers, who do this out of our free time and work.
I know this ... But I am saying that you should not be concentrated on some
kind of "silly fights"...
>
> > Listen, I know something about C and C++ programming and I have to muc
Dear Co-Workers!
Bug#33522 [1] might not be of relevance but it characterizes my problems
pretty good.
In this spirit
Yours Gernot
---
[1]
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/554a7a34bf236bbe/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
reassign 426440 linux-2.6
thanks
On May 28, Miernik <[EMAIL PROTECTED]> wrote:
> ping: sendmsg: No buffer space available
Not related to user space unless the contrary is proven.
--
ciao,
Marco
signature.asc
Description: Digital signature
Processing commands for [EMAIL PROTECTED]:
> reassign 426440 linux-2.6
Bug#426440: /usr/sbin/pppd: sometimes connection with Option GlobeTrotter card
hangs, ping: sendmsg: No buffer space available
Bug reassigned from package `ppp' to `linux-2.6'.
> thanks
Stopping processing here.
Please conta
On Sun, 27 May 2007, Rafal Czlonka wrote:
> maximilian attems wrote:
> > hmmm never seen,
> > can you pleas post the output of
> > sh -x mkinitramfs-kpkg
>
> + set -eu
thanks and urrgs please post output of
sh -x mkinitramfs-kpkg -o /tmp/fooo
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROT
On Mon, 28 May 2007, Clayton wrote:
> On Fri, 25 May 2007 15:23:20 +0200
> maximilian attems <[EMAIL PROTECTED]> wrote:
>
> > On Fri, May 25, 2007 at 09:04:10PM +0800, clayton wrote:
> > > Package: linux-image-2.6.20-1-686
> > > Version: 2.6.20-3
> > > Severity: normal
> >
> > can you please tes
Package: initramfs-tools
Version: 0.88
Severity: important
After upgrade to 0.88 (it works with etch's 0.87b), I cannot create
initramfs anymore:
update-initramfs: Generating /boot/initrd.img-2.6.18-4-686
Error: missing mapper/cr_hda root /dev/mapper/cr_hda5 /sys entry
The root seems to be
Accepted:
kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerp
Accepted:
kernel-build-2.6.8-4_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-4_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4
Accepted:
kernel-headers-2.6.8-4_2.6.8-6_s390.deb
to pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-4_2.6.8-6_s390.deb
kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb
to
pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb
kernel-image-2.6.8-4-s390_2.6
Accepted:
kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
kernel-headers-2
Accepted:
kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb
to
pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb
kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb
to
pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb
kernel-hea
Accepted:
kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb
kernel-headers-2
Your message dated Mon, 28 May 2007 23:06:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317286: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317286: fixed in kernel-image-2.6.8-s390 2.6.8-6
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 c
Accepted:
kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8-sm
Your message dated Mon, 28 May 2007 23:06:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311357: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323557: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372621: fixed in kernel-image-2.6.8-ia64 2.6.8-15
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
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323557: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:13 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372621: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-image-2.6.8-alpha 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:30 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321442: fixed in kernel-image-2.6.8-sparc 2.6.8-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
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317286: fixed in kernel-image-2.6.8-i386 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354493: fixed in kernel-image-2.6.8-i386 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-image-2.6.8-amd64 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354493: fixed in kernel-image-2.6.8-ia64 2.6.8-15
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
Your message dated Mon, 28 May 2007 23:06:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372621: fixed in kernel-image-2.6.8-alpha 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354493: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321442: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-image-2.6.8-i386 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349774: fixed in kernel-image-2.6.8-i386 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317286: fixed in kernel-image-2.6.8-ia64 2.6.8-15
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
Your message dated Mon, 28 May 2007 23:06:13 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-image-2.6.8-hppa 2.6.8-7
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 c
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372621: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349774: fixed in kernel-image-2.6.8-ia64 2.6.8-15
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
Your message dated Mon, 28 May 2007 23:06:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336153: fixed in kernel-image-2.6.8-s390 2.6.8-6
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 c
Your message dated Mon, 28 May 2007 23:06:30 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354493: fixed in kernel-image-2.6.8-sparc 2.6.8-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
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372621: fixed in kernel-image-2.6.8-i386 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321442: fixed in kernel-image-2.6.8-s390 2.6.8-6
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 c
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321442: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:30 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317286: fixed in kernel-image-2.6.8-sparc 2.6.8-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
Your message dated Mon, 28 May 2007 23:06:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323557: fixed in kernel-image-2.6.8-amd64 2.6.8-17
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
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349774: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
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 t
Your message dated Mon, 28 May 2007 23:06:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311357: fixed in kernel-image-2.6.8-alpha 2.6.8-17
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
1 - 100 of 134 matches
Mail list logo