Why is there so much more security patches in the redhat kernel, compare here:
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=redhat+kernel
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=debian+kernel
when alot of the advisories seems to be affect debian as well?
Is it up to the wendor to
Package: initramfs-tools
Severity: important
The latest version of initramfs-tools (0.44) calls update-initramfs in
postinst to regenerate the latest initramfs on upgrades (see initramfs-tools
changelog, version 0.40ubuntu6).
This can be potentially very dangerous if the newer initramfs-tools
Hi Simon
2.4.27-12 has been released into sid, this is a call to rebuild for
all the different architectures. So far it is only available for i386
(which I built). I'll get powerpc rolling, I had mistakenly thought it
was removed from Sid. Perhaps it should be, we can address that
another
Michael Schmitz [EMAIL PROTECTED] writes:
Thanks. But the vanilla kernel-2.6.15-rc5 has not this problem.
Confirmed. So we conclude linux-source-2.6.15 is broken.
No. We concluded that linux-source-2.6.15 has a patch that broke
it. I'm adding Debian kernel Team on CC for reference.
--
On Wed, Dec 14, 2005 at 10:57:49AM +0900, Horms wrote:
2.4.27-12 has been released into sid, this is a call to rebuild for all
the different architectures. So far it is only available for i386 (which
I built). I'll get powerpc rolling, I had mistakenly thought it was
removed from Sid. Perhaps
Horms wrote:
2.4.27-12 has been released into sid, this is a call to rebuild for all
the different architectures. So far it is only available for i386 (which
I built). I'll get powerpc rolling, I had mistakenly thought it was
removed from Sid. Perhaps it should be, we can address that another
Suggest merge with #343042, it seems this is happening to lots of
people.
I attempted the fix mentioned in #343042, adding MODULE ide-generic
and MODULE ide-disk to /etc/haird/Default.cfg, and running yaird -v
-o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686, but the same error
occured. I have
I did not forget that bug; and I would like to solve it ASAP.
- it seems to me that my bug is not generic to the Debian-Alpha-SMP kernels, but
rather directly to all
Linux-SMP due to a likely bug in the PCI device Qlogick 4010 (scsi card)
with some module like
qlasomething
I think about that
On Wed, 2005-12-14 at 10:41 -0500, Rich Johnson wrote:
On Dec 12, 2005, at 1:13 PM, dann frazier wrote:
You are trying to build 2.6.8 with gcc 4. 2.6.8 isn't in sid and
gcc 4
isn't in sarge. Closing.
If you want to build this on sid anyway, try setting CC to gcc-3.3 in
your
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: grave
Justification: renders package unusable
Installing (or upgrading) the package linux-image-2.6.14-2-686 the
post-installation script returns error code 128.
Configuro linux-image-2.6.14-2-686 (2.6.14-5) ...
Running depmod.
Hello.
Would it be possible to include the bigphysarea patch in Debian 2.6
kernels, and enable it by default? It is necessary for hardware which
has large DMA buffers and which does not support scatter-gather DMA.
Example: Zoran ZR36067. It also does not bother anything else by being
enabled
reassign 343363 kernel-package
stop
On Wed, Dec 14, 2005 at 07:33:56PM +0100, Andrea Franzese wrote:
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: grave
Justification: renders package unusable
Installing (or upgrading) the package linux-image-2.6.14-2-686 the
Processing commands for [EMAIL PROTECTED]:
reassign 343363 kernel-package
Bug#343363: package linux-image-2.6.14-2-686 won't install due to a
post-installation script error.
Bug reassigned from package `linux-image-2.6.14-2-686' to `kernel-package'.
stop
Stopping processing here.
Please
kernel-image-2.4.27-alpha_2.4.27-10sarge1_alpha.changes uploaded successfully
to localhost
along with the files:
kernel-image-2.4.27-alpha_2.4.27-10sarge1.dsc
kernel-image-2.4.27-alpha_2.4.27-10sarge1.tar.gz
kernel-headers-2.4.27-2_2.4.27-10sarge1_alpha.deb
kernel-image-2.4.27-ia64_2.4.27-10sarge1_ia64.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.4.27-ia64_2.4.27-10sarge1.dsc
kernel-image-2.4.27-ia64_2.4.27-10sarge1.tar.gz
kernel-headers-2.4.27-2_2.4.27-10sarge1_ia64.deb
PGP/GnuPG signature check failed on
kernel-image-2.4.27-i386_2.4.27-10sarge1_i386.changes
gpg: Signature made Wed Aug 17 18:49:36 2005 PDT using DSA key ID 87B1CFB5
gpg: Can't check signature: public key not found
(Exit status 2)
kernel-image-2.4.27-i386_2.4.27-10sarge1_i386.changes has bad
kernel-image-2.4.27-sparc_2.4.27-9sarge1_sparc.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.4.27-sparc_2.4.27-9sarge1.dsc
kernel-image-2.4.27-sparc_2.4.27-9sarge1.tar.gz
kernel-headers-2.4.27-2_2.4.27-9sarge1_sparc.deb
PGP/GnuPG signature check failed on
kernel-patch-powerpc-2.4.27_2.4.27-10sarge1_powerpc.changes
gpg: Signature made Wed Aug 17 18:50:26 2005 PDT using DSA key ID 87B1CFB5
gpg: Can't check signature: public key not found
(Exit status 2)
kernel-patch-powerpc-2.4.27_2.4.27-10sarge1_powerpc.changes
kernel-source-2.4.27_2.4.27-10sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-source-2.4.27_2.4.27-10sarge1.dsc
kernel-source-2.4.27_2.4.27-10sarge1.diff.gz
kernel-source-2.4.27_2.4.27.orig.tar.gz
kernel-patch-debian-2.4.27_2.4.27-10sarge1_all.deb
kernel-image-2.6.8-alpha_2.6.8-16sarge1_alpha.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-alpha_2.6.8-16sarge1.dsc
kernel-image-2.6.8-alpha_2.6.8-16sarge1.tar.gz
kernel-headers-2.6.8-2_2.6.8-16sarge1_alpha.deb
kernel-image-2.6.8-amd64_2.6.8-16sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-amd64_2.6.8-16sarge1.dsc
kernel-image-2.6.8-amd64_2.6.8-16sarge1.tar.gz
kernel-headers-2.6.8-11_2.6.8-16sarge1_i386.deb
PGP/GnuPG signature check failed on
kernel-image-2.6.8-i386_2.6.8-16sarge1_i386.changes
gpg: Signature made Tue Aug 16 19:17:24 2005 PDT using DSA key ID 87B1CFB5
gpg: Can't check signature: public key not found
(Exit status 2)
kernel-image-2.6.8-i386_2.6.8-16sarge1_i386.changes has bad PGP/GnuPG
kernel-image-2.6.8-ia64_2.6.8-14sarge1_ia64.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-ia64_2.6.8-14sarge1.dsc
kernel-image-2.6.8-ia64_2.6.8-14sarge1.tar.gz
kernel-headers-2.6.8-2_2.6.8-14sarge1_ia64.deb
kernel-image-2.6.8-s390_2.6.8-5sarge1_s390.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-s390_2.6.8-5sarge1.dsc
kernel-image-2.6.8-s390_2.6.8-5sarge1.tar.gz
kernel-patch-2.6.8-s390_2.6.8-5sarge1_all.deb
kernel-headers-2.6.8-2_2.6.8-5sarge1_s390.deb
kernel-image-2.6.8-sparc_2.6.8-15sarge1_sparc.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-sparc_2.6.8-15sarge1.dsc
kernel-image-2.6.8-sparc_2.6.8-15sarge1.tar.gz
kernel-headers-2.6.8-2_2.6.8-15sarge1_sparc.deb
kernel-patch-powerpc-2.6.8_2.6.8-12sarge1_powerpc.changes uploaded successfully
to localhost
along with the files:
kernel-patch-powerpc-2.6.8_2.6.8-12sarge1.dsc
kernel-patch-powerpc-2.6.8_2.6.8-12sarge1.tar.gz
kernel-headers-2.6.8_2.6.8-12sarge1_powerpc.deb
kernel-source-2.6.8_2.6.8-16sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-source-2.6.8_2.6.8-16sarge1.dsc
kernel-source-2.6.8_2.6.8-16sarge1.diff.gz
kernel-source-2.6.8_2.6.8.orig.tar.gz
kernel-patch-debian-2.6.8_2.6.8-16sarge1_all.deb
Mapping stable-security to proposed-updates.
Accepted:
kernel-headers-2.6.8-2_2.6.8-5sarge1_s390.deb
to
pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-2_2.6.8-5sarge1_s390.deb
kernel-image-2.6.8-2-s390-tape_2.6.8-5sarge1_s390.deb
to
Mapping stable-security to proposed-updates.
Accepted:
kernel-build-2.4.27-2_2.4.27-10sarge1_alpha.deb
to
pool/main/k/kernel-image-2.4.27-alpha/kernel-build-2.4.27-2_2.4.27-10sarge1_alpha.deb
kernel-headers-2.4.27-2-generic_2.4.27-10sarge1_alpha.deb
to
Mapping stable-security to proposed-updates.
Warning: Propogating upload to unstable
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload to unstable
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload to unstable
Warning: Propogating
Mapping stable-security to proposed-updates.
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload to testing-proposed-updates
Warning: Propogating upload
Mapping stable-security to proposed-updates.
Accepted:
kernel-headers-2.6.8-2-generic_2.6.8-16sarge1_alpha.deb
to
pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-2-generic_2.6.8-16sarge1_alpha.deb
kernel-headers-2.6.8-2-smp_2.6.8-16sarge1_alpha.deb
to
Mapping stable-security to proposed-updates.
Rejected: The key (0x76EF8CE887B1CFB5) used to sign
kernel-source-2.6.8_2.6.8-16sarge1.dsc wasn't found in the keyring(s).
Warning: ignoring kernel-source-2.6.8_2.6.8.orig.tar.gz, since it's already in
the archive.
===
If you don't understand why
Mapping stable-security to proposed-updates.
Accepted:
kernel-build-2.6.8-power3-smp_2.6.8-12sarge1_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3-smp_2.6.8-12sarge1_powerpc.deb
kernel-build-2.6.8-power3_2.6.8-12sarge1_powerpc.deb
to
Mapping stable-security to proposed-updates.
Accepted:
kernel-headers-2.6.8-11-amd64-generic_2.6.8-16sarge1_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-11-amd64-generic_2.6.8-16sarge1_i386.deb
kernel-headers-2.6.8-11-amd64-k8-smp_2.6.8-16sarge1_i386.deb
to
Mapping stable-security to proposed-updates.
Rejected: The key (0x76EF8CE887B1CFB5) used to sign
kernel-source-2.4.27_2.4.27-10sarge1.dsc wasn't found in the keyring(s).
Warning: ignoring kernel-source-2.4.27_2.4.27.orig.tar.gz, since it's already
in the archive.
===
If you don't understand
Mapping stable-security to proposed-updates.
Accepted:
kernel-build-2.4.27-2_2.4.27-10sarge1_ia64.deb
to
pool/main/k/kernel-image-2.4.27-ia64/kernel-build-2.4.27-2_2.4.27-10sarge1_ia64.deb
kernel-headers-2.4.27-2-itanium-smp_2.4.27-10sarge1_ia64.deb
to
Hello,
I'm starting to believe I found a bug in ALSA driver snd_es18xx. I don't know
against which package I should file the bug. Could anybody point me to the
right direction ?
Thanks
Paulo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
kernel-source-2.4.27_2.4.27-10sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-source-2.4.27_2.4.27-10sarge1.dsc
kernel-source-2.4.27_2.4.27-10sarge1.diff.gz
kernel-patch-debian-2.4.27_2.4.27-10sarge1_all.deb
kernel-doc-2.4.27_2.4.27-10sarge1_all.deb
Your message dated Wed, 14 Dec 2005 19:47:14 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#311164: fixed in kernel-source-2.4.27 2.4.27-10sarge1
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
Your message dated Wed, 14 Dec 2005 19:47:25 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#309308: fixed in kernel-source-2.6.8 2.6.8-16sarge1
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 Wed, 14 Dec 2005 19:47:25 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#322339: fixed in kernel-source-2.6.8 2.6.8-16sarge1
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 Wed, 14 Dec 2005 19:47:15 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#323318: fixed in kernel-source-2.4.27 2.4.27-10sarge1
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
Your message dated Wed, 14 Dec 2005 19:47:25 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#323059: fixed in kernel-source-2.6.8 2.6.8-16sarge1
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
Mapping stable-security to proposed-updates.
Accepted:
kernel-doc-2.6.8_2.6.8-16sarge1_all.deb
to pool/main/k/kernel-source-2.6.8/kernel-doc-2.6.8_2.6.8-16sarge1_all.deb
kernel-patch-debian-2.6.8_2.6.8-16sarge1_all.deb
to
Mapping stable-security to proposed-updates.
Accepted:
kernel-doc-2.4.27_2.4.27-10sarge1_all.deb
to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-10sarge1_all.deb
kernel-patch-debian-2.4.27_2.4.27-10sarge1_all.deb
to
Package: kernel-image-2.4.27-nubus
Version: 2.4.27-11
When the kernel start to get some memory that was swapped, the
application that it need that memory almost in 90% of times will crash
when the quantity of memory it need is more than 30 megabytes of swapped
memory, causing illegal instructions
kernel-patch-powerpc-2.4.27_2.4.27-10sarge1_powerpc.changes uploaded
successfully to localhost
along with the files:
kernel-patch-powerpc-2.4.27_2.4.27-10sarge1.dsc
kernel-patch-powerpc-2.4.27_2.4.27-10sarge1.tar.gz
kernel-patch-2.4.27-apus_2.4.27-10sarge1_powerpc.deb
kernel-image-2.4.27-i386_2.4.27-10sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.4.27-i386_2.4.27-10sarge1.dsc
kernel-image-2.4.27-i386_2.4.27-10sarge1.tar.gz
kernel-headers-2.4.27-2_2.4.27-10sarge1_i386.deb
kernel-image-2.6.8-i386_2.6.8-16sarge1_i386.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-i386_2.6.8-16sarge1.dsc
kernel-image-2.6.8-i386_2.6.8-16sarge1.tar.gz
kernel-headers-2.6.8-2_2.6.8-16sarge1_i386.deb
Mapping stable-security to proposed-updates.
Accepted:
kernel-build-2.4.27-2_2.4.27-10sarge1_i386.deb
to
pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-2_2.4.27-10sarge1_i386.deb
kernel-headers-2.4.27-2-386_2.4.27-10sarge1_i386.deb
to
Mapping stable-security to proposed-updates.
Accepted:
kernel-headers-2.6.8-2-386_2.6.8-16sarge1_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-386_2.6.8-16sarge1_i386.deb
kernel-headers-2.6.8-2-686-smp_2.6.8-16sarge1_i386.deb
to
Hi,
On Tue, Dec 06, 2005 at 03:48:40PM +0100, Max Vozeler wrote:
Package: linux-2.6
Version: 2.6.12-10
Severity: important
This bug is a bit weird :-)
Apparently the binaries in m68k -headers were built for i386.
Yes, this may very well be possible, since the m68k linux-* packages were
Package: linux-doc-2.6.14
Version: 2.6.14-4
Severity: minor
Please s/varios/various/ in the long description.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
54 matches
Mail list logo
