Processed: Dupe of #320422, adjusting severity/tags/package and merging
Processing commands for [EMAIL PROTECTED]: severity 321752 important Bug#321752: linux-image-2.6.12-1-k7: generates incorrect /vmlinuz, /initrd.img links Severity set to `important'. tags 321752 pending Bug#321752: linux-image-2.6.12-1-k7: generates incorrect /vmlinuz, /initrd.img links There were no tags set. Tags added: pending reassign 321752 linux-2.6 Bug#321752: linux-image-2.6.12-1-k7: generates incorrect /vmlinuz, /initrd.img links Bug reassigned from package `linux-image-2.6.12-1-k7' to `linux-2.6'. merge 321752 320422 Bug#320422: linux-image-2.6.12-1: error in postinst that creates dangling symlinks Bug#321752: linux-image-2.6.12-1-k7: generates incorrect /vmlinuz, /initrd.img links Merged 320422 321752. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-kernel-di udebs [Was: Re: 2.6.12 upload]
On Thu, Jul 28, 2005 at 06:18:28PM +0200, Goswin von Brederlow wrote: Bastian Blank [EMAIL PROTECTED] writes: On Thu, Jul 28, 2005 at 04:49:01PM +0900, Horms wrote: I tend to aggree, though I believe Franz Pop, or perhaps some of the other d-i team members have reason for keeping these images separate. Perhaps they could reiterate them here. Mostly two reasons: - Changes in the d-i packages don't trigger a complete rebuild. - There are more then 200 different binary packages. Bastian At the start changes have been common and modules have been added or removed or packages been split or joined. But hasn't that settled down now? Aren't the linux-kernel-di udebs consistent enough to be handled by kernel-source uploads? I've CCed debian-boot to get a broader opinion. Notice that i believe this is a bogus argument anyway. The right way to solve this would be for the main kernel package to provide one .udeb for each individual module, and then the problem of regrouping them or not and changing sizes goes away all by itself. And we even gain flexibility at the d-i image build level, and make third-party (particularly non-free modules) .udeb inclusion easier. We would not be limited to the actual artificial and sometime bogus grouping and separation of .udebs, and we would have the possibility to download only those drivers we need. If all other technical aspects are solved (more to this below), this would be the most clean and elegant solution. Sadly, it seems that the dpkg/apt/whatever infrastructure will have some trouble keeping up with the *HUGE* amount of .udebs involved, and this was probably the reason why this was not done for the sarge timeframe, especially as we where in the we will release next month loop. But now we are at the start of a new release cycle, and there should be no major reason not to solve this technical huge-number-of-udebs problem in our infrastructure. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Let's have udeb's for each single module ...
On Thu, Jul 28, 2005 at 12:07:44PM +0100, Colin Watson wrote: On Tue, Jul 26, 2005 at 03:26:04PM +0200, Goswin von Brederlow wrote: The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. Last I checked, dak was being reeducated so that it could be told about udebs it needed to keep around due to them being in initrd builds. The same approach could be used fairly easily to keep kernel source around until the corresponding udebs have been rebuilt. The main problem with moving udebs into the kernel build process, I think, is that the installer team needs to be able to change their structure relatively frequently; for example, the exact balance of modules in various udebs affects whether it's possible to build installer floppies and other media with space restrictions. Historically, having the udebs be controlled by the d-i team made sense. This goes away by having single .udeb per module, and a .udeb dependency tree generated by or in the same way as the depmod stuff. Is it really all that much complicated to teach the infrastructure to handle bigger number of .udeb packages, than doing loads of hacky workaround like the above ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6 - subarch and patches
On Wed, Aug 03, 2005 at 07:57:22PM +0200, Christoph Hellwig wrote: On Wed, Aug 03, 2005 at 07:55:12PM +0200, Bastian Blank wrote: - Each arch may specify an architectury specific patch, each image package may specify another patch, it may shared between more than one image. Or fix the architectures to not require them. The mips changes are fine for any other architecture, although they should be split into a few more. The m68k patch as-is isn't, but we hope to have m68k compiling from mainline sources soon after the 2.6.14 tree opens. I hope the powerpc/apus patch will be fine soon, but what about things like the (upcoming ?) powerpc/nubus patch ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#279491: No disk detected on an IBM RS6000 7043-260 (sym53c8xx driver)
On Fri, Aug 05, 2005 at 12:13:24PM +0900, Horms wrote: On Thu, Aug 04, 2005 at 11:28:47AM +0200, Ralph wrote: Hello ! I'm new to this list, I'm Ralph from Germany. I'm running into the same problem with sym53c8xx on my 7043-260. i can now boot fine the machine with kernel-image-2.6.8-power3-smp version 2.6.8-6. if i use kernel-image-2.6.8-power3 version 2.6.8-6 i get problem with the symbios controller. i attached the full log of the UP kernel and a piece of the log of the working SMP kernel. Could you be so kind and provide that smp-kernel binary to me. I cannot build my own one, because i don't have a unix system yet and want to make the 7043-260 the one. Hi, The 2.6.8-6 version of this package is no longer supported. If you really want to find it, try http://snapshot.debian.net/ The latst version of this package is 2.6.8-12 which is available in the Debian Archive mirrors. e.g. http://ftp.debian.org/debian/pool/main/k/kernel-patch-powerpc-2.6.8/ There are also newer upstream kernel versions available for power pc, 2.6.11, and 2.6.12. They are also available in the Debian Archive mirrors. e.g.: http://ftp.debian.org/debian/pool/main/k/kernel-patch-powerpc-2.6.11/ http://ftp.debian.org/debian/pool/main/l/linux-2.6/ Notice that : 1) the d-i images doesn't use the -smp kernels. 2) the 2.6.8 kernels need an initrd, which is probably only buildable from an installed system. 3) the 2.6.12 have dropped support for ppc64 (power3 and power4) subarches, until the toolchain guys get their act together and finally build the ppc64 biarch toolchain we can use. 4) in any case, the new ppc64 kernels will be SMP only, i am dropping the uniprocessor flavour on them. 5) i built (have not done yet, but will do post 2.6.12-2), d-i images, altough the fact that the .udebs are not in the archive make them more or less none-usable. Ralph, in any case, you will want the -pseries kernel on your hardware, the other options being -pseries-power4 which is power4 optimized, and -iseries-legacy, for pre-power5 iseries. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#279491: No disk detected on an IBM RS6000 7043-260 (sym53c8xx driver)
On Monday 08 August 2005 10:57, Sven Luther wrote: 4) in any case, the new ppc64 kernels will be SMP only, i am dropping the uniprocessor flavour on them. AFAIK this should solve the problem with the symbios controller and make the 7043-260 both installable and usable (but i don't have the machine handy anymore). cheers, alessandro -- B-Open Solutions srl - http://www.bopen.it/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321167: linux-image: say the difference vs. kernel-image
On Sat, Aug 06, 2005 at 10:11:21AM +0800, Dan Jacobson wrote: I'm sorry but all that is over my head, beyond my level. All I know is that all the files in pool/main/l/linux-2.6/ need Descriptions that even the most bumblesome user could understand. You are welcome to propose such descriptions in a patch or even just plain text in this bug report. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321442: kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c)
On Fri, Aug 05, 2005 at 05:15:57PM +0200, LT-P wrote: Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction ?? pmac_ide_dma_read ??: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction ?? pmac_ide_dma_write ??: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction ?? pmac_ide_setup_dma ??: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 Can you please enable BLK_DEV_IDEDMA_PCI and see if that resolves your problem. If it does, then the following patch should fix Kconfig so that BLK_DEV_IDEDMA_PCI needs to be enabled for BLK_DEV_IDE_PMAC to be enabled. It should patch cleanly against Debian's 2.6.8 and Linus' current Git tree. -- Horms BLK_DEV_IDEDMA_PCI seems to be needed for BLK_DEV_IDE_PMAC to compile Signed-off-by: Horms [EMAIL PROTECTED] --- a/drivers/ide/Kconfig.orig 2005-08-08 17:48:17.0 +0900 +++ b/drivers/ide/Kconfig 2005-08-08 17:48:48.0 +0900 @@ -749,8 +749,6 @@ This allows the kernel to change PIO, DMA and UDMA speeds and to configure the chip to optimum performance. -endif - config BLK_DEV_IDE_PMAC bool Builtin PowerMac IDE support depends on PPC_PMAC IDE=y @@ -759,6 +757,8 @@ most of the recent Apple Power Macintoshes and PowerBooks. If unsure, say Y. +endif + config BLK_DEV_IDE_PMAC_ATA100FIRST bool Probe internal ATA/100 (Kauai) first depends on BLK_DEV_IDE_PMAC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian sarge freeze computer
On 8/2/05, Paulo Neves [EMAIL PROTECTED] wrote: Hi Alexander, Hummm, I think this IBM computers don't like kernel 2.6 :). I install kernel 2.4.27 and until now works fine too. Regards, Paulo On 8/2/05, Alexander Fisher [EMAIL PROTECTED] wrote: Paulo Neves wrote: Hi all, I have a problem that occurs on 2 IBM PIV 2.4Ghz, 1 Gb RAM and 40Gb IDE HDD with debian sarge 3.1 (kernel 2.6). On other computer, the same debian don't give-me any problem. Hi I've exactly the same problem with similar symtoms. Its also on IBM 2.4Ghz P4s (Netvistas - I've tried two identical machines). Its not like its a complete freeze, but the system becomes *so* slow it may as well be. For example, the 'beep' you get when bash autocomplete fails lasts for several seconds. A shutdown takes tens of minutes. I've no graphical environment installed and am pretty sure that its a kernel issue. I've witnessed this problem on both 2.6.8-2 and 2.6.11-1 (from unstable). So far, 2.4.27-2 seems to be unaffected. I'm not sure about load average, but my cpu average was also around 0%. If it helps, I'm using XFS on top of LVM on top of RAID 1. Any suggestions? I might give a vanilla 2.6.12.3 kernel a go. Kind Regards, Alex Hi All. I'm still trying to get this fixed. I've cc-ed the debian kernel list to see if anybody there has any thoughts. http://lists.debian.org/debian-user/2005/08/msg00072.html In my opinion using a 2.4 kernel is at best a workaround and not a solution. I've given 2.6.12-1-686 a go. It also slows right down after a while. I just ran time sleep 1 real0m0.000s user 0m0.000s sys 0m0.000s The operation actually took around 17 seconds. Any suggestions on what I should try next? Thanks, Alex
Bug#282023: marked as done (kernel-source-2.6.9: 6to4 tunnel interface cannot be freed on shutdown, causing hang)
Your message dated Mon, 8 Aug 2005 13:15:58 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-source-2.6.9: 6to4 tunnel interface cannot be freed on shutdown, causing hang 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 Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 19 Nov 2004 08:17:09 + From [EMAIL PROTECTED] Fri Nov 19 00:17:09 2004 Return-path: [EMAIL PROTECTED] Received: from mxfep02.bredband.com [195.54.107.73] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CV3x6-r2-00; Fri, 19 Nov 2004 00:17:09 -0800 Received: from thales.home.better.se ([83.227.74.123] [83.227.74.123]) by mxfep02.bredband.com with ESMTP id [EMAIL PROTECTED]; Fri, 19 Nov 2004 09:16:36 +0100 Received: from thales.home.better.se (localhost.localdomain [127.0.0.1]) by thales.home.better.se (8.13.1/8.13.1/Debian-16) with ESMTP id iAJ8GaMO004102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Nov 2004 09:16:36 +0100 Received: (from [EMAIL PROTECTED]) by thales.home.better.se (8.13.1/8.13.1/Submit) id iAJ8GZZL004101; Fri, 19 Nov 2004 09:16:35 +0100 Message-Id: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Marcus Better [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-source-2.6.9: 6to4 tunnel interface cannot be freed on shutdown, causing hang X-Mailer: reportbug 2.63 Date: Fri, 19 Nov 2004 09:16:35 +0100 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-source-2.6.9 Version: 2.6.9-2 Severity: normal I have configured a 6to4 tunnel for IPv6 access. When I do a shutdown or reboot of the system, I get the following on the console: Deconfiguring network interfaces... unregister_netdevice: Waiting for tun6to4 to become free. Usage count=1 unregister_netdevice: Waiting for tun6to4 to become free. Usage count=1 unregister_netdevice: and so on, with the last line repeated at 10 second intervals. I cannot break out of this loop except by turning off the power. I have observed this with my custom-compiled kernel, and also with the official kernel, and on two different machines. It happens even if I haven't actually transferred any data over the tunnel. The first system is an Athlon XP 2400+ desktop. The other one is an Acer TravelMate 223X laptop with a Mobile Celeron at 1.13 Ghz. The 6to4 tunnel device looks as follows (IP addresses removed): ~$ /sbin/ifconfig tun6to4 tun6to4 Link encap:IPv6-in-IPv4 inet6 addr: 2002::::1/16 Scope:Global inet6 addr: ::83.227.xxx.yyy/128 Scope:Compat UP RUNNING NOARP MTU:1480 Metric:1 (packet stats removed, all zeros) ~$ ip tunnel show tun6to4: ipv6/ip remote any local 83.227.xxx.yyy ttl 255 -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9custom-skas3-v7 Locale: LANG=sv_SE.ISO-8859-15, LC_CTYPE=sv_SE.ISO-8859-15 Versions of packages kernel-source-2.6.9 depends on: ii binutils 2.15-4 The GNU assembler, linker and bina ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information --- Received: (at 282023-done) by bugs.debian.org; 8 Aug 2005 11:16:38 + From [EMAIL PROTECTED] Mon Aug 08 04:16:38 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E25cT-0008Ng-00; Mon, 08 Aug 2005 04:16:38 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id 5BA2B5C00F; Mon, 8 Aug 2005 13:15:58 +0200 (CEST) Date: Mon, 8 Aug 2005 13:15:58 +0200 From: Maximilian Attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: kernel-source-2.6.9: 6to4 tunnel interface cannot be freed on shutdown, causing hang Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii
Bug#321940: linux-2.6: [powerpc] per flavour archs should have asm-ppc64 symlink too.
Package: linux-2.6 Severity: normal Hi, with current 2.6.12, the symlinks for asm-* are fine, and i belive it is enough to ship -2 as is, as we don't have ppc64 kernels yet. Now, the current setup includes asm-ppc and asm-ppc64 in the common kernel header files, but the per flavour include only the asm-ppc symlink. I believe that we should either provide both, or provide one or the other depending on being a 64bit or 32bit flavour. Providing both is way easier to do. The same happens for the asm symlink too, but i believe that it should be set correctly for 64bit or 32bit flavours, not sure though, but this will need checking on the way to -3. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian sarge freeze computer
On Mon, Aug 08, 2005 at 11:11:41AM +0100, Alexander Fisher wrote: On 8/2/05, Paulo Neves [EMAIL PROTECTED] wrote: Hi Alexander, Hummm, I think this IBM computers don't like kernel 2.6 :). I install kernel 2.4.27 and until now works fine too. Regards, Paulo On 8/2/05, Alexander Fisher [EMAIL PROTECTED] wrote: Paulo Neves wrote: Hi all, I have a problem that occurs on 2 IBM PIV 2.4Ghz, 1 Gb RAM and 40Gb IDE HDD with debian sarge 3.1 (kernel 2.6). On other computer, the same debian don't give-me any problem. Hi I've exactly the same problem with similar symtoms. Its also on IBM 2.4Ghz P4s (Netvistas - I've tried two identical machines). Its not like its a complete freeze, but the system becomes *so* slow it may as well be. For example, the 'beep' you get when bash autocomplete fails lasts for several seconds. A shutdown takes tens of minutes. I've no graphical environment installed and am pretty sure that its a kernel issue. I've witnessed this problem on both 2.6.8-2 and 2.6.11-1 (from unstable). So far, 2.4.27-2 seems to be unaffected. I'm not sure about load average, but my cpu average was also around 0%. If it helps, I'm using XFS on top of LVM on top of RAID 1. Any suggestions? I might give a vanilla 2.6.12.3 kernel a go. Kind Regards, Alex Hi All. I'm still trying to get this fixed. I've cc-ed the debian kernel list to see if anybody there has any thoughts. http://lists.debian.org/debian-user/2005/08/msg00072.html In my opinion using a 2.4 kernel is at best a workaround and not a solution. I've given 2.6.12-1-686 a go. It also slows right down after a while. I just ran time sleep 1 real0m0.000s user 0m0.000s sys 0m0.000s The operation actually took around 17 seconds. Any suggestions on what I should try next? Thanks, Alex try with the 2.6.12 image acpi=off pci=routeirq lapic=off you may need one of those or all. if that doesn't work please report bug on bugzilla.kernel.org on wednesday i'm back and i could supply you with an 2.6.13-rc6 image. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321756: linux-image-2.6.12-1-k7: Automount (GNOME desktop) doesn't work any more for external USB harddisks
On Sun, Aug 07, 2005 at 03:06:21PM +0200, Haug Bürger wrote: Package: linux-image-2.6.12-1-k7 Version: 2.6.12-1 Severity: important th the 2.6.12 kernel the automount (GNOME desktop) doesn't work any more for my external USB harddisks. After connecting there is a message in the messages telling me the drive type etc. but the the icons don't show up any more. Same works wonderful when booting kernel-image-2-6-11 on my mostly sarge(stable) system. i guess your udev is outdated? also you may need a newer gnome2-vfs. what is dmesg saying. please bear in mind we cant support mixed installs. debian-user mailinglist might be the better place than bug report. -- maks
Processed: Tagging pending
Processing commands for [EMAIL PROTECTED]:
tags 320817 pending
Bug#320817: /usr/src/linux-headers-2.6.12-1-powerpc/include/asm{,-ppc} symlinks
broken
There were no tags set.
Tags added: pending
tags 321625 pending
Bug#321625: linux-2.6: [powerpc] does not include mkvmlinuz support
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#319878: kernel-image-2.6-686: the entire range of 2.6 deb ian kernels do not install on m/cs with = 48mb RAM
On Mon, Jul 25, 2005 at 11:25:18PM +0100, Luke Kenneth Casson Leighton wrote: On Mon, Jul 25, 2005 at 11:56:21AM -0300, Humberto Massa Guimar?es wrote: ** Luke Kenneth Casson Leighton :: possible solutions: * fix the bloody 2.6 kernel so it doesn't use so much damn memory. * fix the debian-specific, debian-created and debian-responsible initrd ramdisk so it doesn't require so much damn memory. * provide an alternate compact ramdisk if fixing the default ramdisk isn't a viable option. Remember Debian is a volunteer-driven organization. Implement the features you need yourself and then ask (politely) for the inclusion of your contribution. Or, you can ask (more politely still) for someone more knowledgeable than you (like Horms) to implement one of your suggestions. But what you should NOT do is to demand features like your e-mail seemed to. if you read it carefully, you will note that the wording doesn't make any demands. it _does_ however hint at some socially uncomfortable responsibilities. Luke, do you have an idea of what exactly is the problem with 2.6 kernels and low memory support ? Could you describe it, especially since i believe it is only a problem related on how the initrd is generated, and the fact that initrd-tools creates insanely big initrds by default ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#279491: No disk detected on an IBM RS6000 7043-260 (sym53c8xx driver)
Hello ! Thanks a lot, i finally succeeded in installing the most recent version by doing a boot with a modified sarge-powerpc-bc-lbb.iso on my 7043-260. The main problem was, that I didn't have a linux machine, so I had to deal several things with a windows pc. The following steps made it: get http://www.solinno.co.uk/leigh/sarge-powerpc-bc-lbb.iso use http://www.slysoft.com/download/SetupVirtualCloneDrive.exe on windows pc, mount iso and copy contents to an empty directory on harddisk. replace on harddisk yaboot in /ppc/chrp and /install with http://www.solinno.co.uk/leigh/yaboot replace all on harddisk in /install/power3 with http://people.debian.org/~luther/d-i/sarge/images/daily/power3/netboot/ (thanks a lot, Sven) use latest cdrtools for windows and do a mkisofs -chrp-boot -U -r -hide-rr-moved -o /sarge.iso . within the directory of where you copied the cd. burn the resulting iso to cd using whatever you use to burn cds. If this cd doesn't boot automatically on the system, boot it in OpenFirmware with boot cdrom:,\ppc\chrp\yaboot video=ofonly this should get the debianinstaller running either on serial terminal or on the(in my machine)gxt2000p console, depending the console-setting in OpenFirmware AND gives me some ttys on my gxt2000p. After the netdetect and BEFORE choosing debian mirror I had to change the mtu size of eth0, because in my windows network environment i'm using mtu=1400 because of DSL-internet-connection. ifconfig eth0 mtu 1400 When partitioning harddisk, make sure to create the first partition as 8MB prep-boot. BEFORE debianinstaller wants to install yaboot to this partition, you have to edit ybin (i used nano) and find the following: if [ -n $magicboot ] ; then echo 12 $PRG:$ERR \`magicboot' scripts cannot be used with fstype=raw local CONFERR=1 fi place a comment here: # local CONFERR=1 Not doing this will leave you in an loop in debianinstaller where you can't get out. Now installation should work. BEFORE rebooting after this successful installation I modified the etc/apt/sources.list to get the etch, did an apt-get -u update and insalled the latest smp-kernel with apt-get install kernel-image-2.6-power3-smp After that a you have to kill a process that tries to write some logfiles, but never finishes... That's it. Removing CD an rebooting should boot fine from Harddisk now and get you to the rest of debian installation, which works fine. (and where i'm stucked now with not beeing able to run X11 because of my gxt2000p graphic adapter). Did I forget something ? If yes, please contact me. Thanks to all helpers. Ralph -Ursprungliche Nachricht- Von: Horms [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. August 2005 05:13 An: Ralph Cc: [EMAIL PROTECTED]; debian-kernel@lists.debian.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Re: Bug#279491: No disk detected on an IBM RS6000 7043-260 (sym53c8xx driver) On Thu, Aug 04, 2005 at 11:28:47AM +0200, Ralph wrote: Hello ! I'm new to this list, I'm Ralph from Germany. I'm running into the same problem with sym53c8xx on my 7043-260. i can now boot fine the machine with kernel-image-2.6.8-power3-smp version 2.6.8-6. if i use kernel-image-2.6.8-power3 version 2.6.8-6 i get problem with the symbios controller. i attached the full log of the UP kernel and a piece of the log of the working SMP kernel. Could you be so kind and provide that smp-kernel binary to me. I cannot build my own one, because i don't have a unix system yet and want to make the 7043-260 the one. Hi, The 2.6.8-6 version of this package is no longer supported. If you really want to find it, try http://snapshot.debian.net/ The latst version of this package is 2.6.8-12 which is available in the Debian Archive mirrors. e.g. http://ftp.debian.org/debian/pool/main/k/kernel-patch-powerpc-2.6.8/ There are also newer upstream kernel versions available for power pc, 2.6.11, and 2.6.12. They are also available in the Debian Archive mirrors. e.g.: http://ftp.debian.org/debian/pool/main/k/kernel-patch-powerpc-2.6.11/ http://ftp.debian.org/debian/pool/main/l/linux-2.6/ -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312973: kernel-image-2.6.11-1-k7: Same problem here.
Followup-For: Bug #312973 Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-7 Hello, I can't vouch for the sound playback problems but I'm seeing the clock drift problem on my system as well: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2600+ stepping: 0 cpu MHz : 1913.322 cache size : 512 KB nForce2 Chipset. It used to work fine in 2.6.8 and lower, the problem appeared after going to 2.6.11. Though I fear this is upstream, please let me know if I can provide any system information useful in debugging this. Greetings, Michel -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo kernel-image-2.6.11-1-k7 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321964: linux-2.6: package that depends on all -headers for $arch
Package: linux-2.6 Version: 2.6.12-1 Severity: wishlist There used to exist packages that depend on all -headers packages for a particular arch (eg. kernel-headers-2.6.11-1-i386). This is very useful for build-depends when autobuilding external module packages. Such packages seem to no longer exist with the new kernel packaging - please consider to re-add something like it. cheers, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ACL patches in Debian 2.4 series kernel.
I have read the cahngelog for Debian version of kernel 2.4.27 (and .26 too) and I have found that the latest version of Posix ACL patches seems to be 0.8.71, merged by Herbert Xu in April 2004. As far as I know, this version has bug that makes default ACLs disappear from directories using ext3 filesystem in certain conditions. I have asked on the ACL mailing list and I was told that the bug was fixed in verion 0.8.72. Has this bug also been fixed in Debian 2.4 kernels or not? I had found nothing about it in Debian bug tracking system and in kernel changelog. Kind regards -- Fabio Kurgan Muzzi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321964: linux-2.6: package that depends on all -headers for $arch
On Mon, Aug 08, 2005 at 03:52:33PM +0200, Max Vozeler wrote: Package: linux-2.6 Version: 2.6.12-1 Severity: wishlist There used to exist packages that depend on all -headers packages for a particular arch (eg. kernel-headers-2.6.11-1-i386). This is very useful for build-depends when autobuilding external module packages. Such packages seem to no longer exist with the new kernel packaging - please consider to re-add something like it. Now that waldi has gencontrol.py creating dummy packages and rules for the various linux-image and linux-header packages, we can throw the all-headers package back in. There was some issue of what it should actually be called, however.. Calling it linux-headers-2.6.12-1-i386 doesn't work too well for all archs, since we end up w/ linux-headers-2.6.12-1-powerpc, which conflicts w/ the name of a flavour. Suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322004: kernel-source-2.6.8: Fails to compile on a X86_64 platform
Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: important Justification: fails to build from source -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-11-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information This is the error message shown: arch/x86_64/kernel/entry.S: Assembler messages: arch/x86_64/kernel/entry.S:81: Error: Macro with this name was already defined arch/x86_64/kernel/entry.S:100: Error: Macro with this name was already defined make[1]: *** [arch/x86_64/kernel/entry.o] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6 - subarch and patches
On Mon, Aug 08, 2005 at 10:47:53AM +0200, Sven Luther wrote: On Wed, Aug 03, 2005 at 07:57:22PM +0200, Christoph Hellwig wrote: On Wed, Aug 03, 2005 at 07:55:12PM +0200, Bastian Blank wrote: - Each arch may specify an architectury specific patch, each image package may specify another patch, it may shared between more than one image. Or fix the architectures to not require them. The mips changes are fine for any other architecture, although they should be split into a few more. The m68k patch as-is isn't, but we hope to have m68k compiling from mainline sources soon after the 2.6.14 tree opens. I hope the powerpc/apus patch will be fine soon, but what about things like the (upcoming ?) powerpc/nubus patch ? Let's just work with the people to sort it out early enough. It's not like it'll be stable enough for a distro as soon as the port is mostly running anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-2.6_2.6.12-2_i386.changes
linux-2.6_2.6.12-2_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.12-2.dsc linux-2.6_2.6.12-2.diff.gz linux-source-2.6.12_2.6.12-2_all.deb linux-tree-2.6.12_2.6.12-2_all.deb linux-patch-debian-2.6.12_2.6.12-2_all.deb linux-doc-2.6.12_2.6.12-2_all.deb linux-headers-2.6.12-1_2.6.12-2_i386.deb linux-headers-2.6.12-1-386_2.6.12-2_i386.deb linux-image-2.6.12-1-386_2.6.12-2_i386.deb linux-headers-2.6.12-1-686_2.6.12-2_i386.deb linux-image-2.6.12-1-686_2.6.12-2_i386.deb linux-headers-2.6.12-1-686-smp_2.6.12-2_i386.deb linux-image-2.6.12-1-686-smp_2.6.12-2_i386.deb linux-headers-2.6.12-1-k7_2.6.12-2_i386.deb linux-image-2.6.12-1-k7_2.6.12-2_i386.deb linux-headers-2.6.12-1-k7-smp_2.6.12-2_i386.deb linux-image-2.6.12-1-k7-smp_2.6.12-2_i386.deb linux-image-386_2.6.12-2_i386.deb linux-image-2.6-386_2.6.12-2_i386.deb linux-headers-2.6-386_2.6.12-2_i386.deb linux-image-686_2.6.12-2_i386.deb linux-image-2.6-686_2.6.12-2_i386.deb linux-headers-2.6-686_2.6.12-2_i386.deb linux-image-686-smp_2.6.12-2_i386.deb linux-image-2.6-686-smp_2.6.12-2_i386.deb linux-headers-2.6-686-smp_2.6.12-2_i386.deb linux-image-k7_2.6.12-2_i386.deb linux-image-2.6-k7_2.6.12-2_i386.deb linux-headers-2.6-k7_2.6.12-2_i386.deb linux-image-k7-smp_2.6.12-2_i386.deb linux-image-2.6-k7-smp_2.6.12-2_i386.deb linux-headers-2.6-k7-smp_2.6.12-2_i386.deb kernel-image-2.6-386_2.6.12-2_i386.deb kernel-image-2.6-686_2.6.12-2_i386.deb kernel-image-2.6-686-smp_2.6.12-2_i386.deb kernel-image-2.6-k7_2.6.12-2_i386.deb kernel-image-2.6-k7-smp_2.6.12-2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.12-2_i386.changes REJECTED
Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6 - subarch and patches
On Mon, Aug 08, 2005 at 09:00:01PM +0200, Christoph Hellwig wrote: On Mon, Aug 08, 2005 at 10:47:53AM +0200, Sven Luther wrote: On Wed, Aug 03, 2005 at 07:57:22PM +0200, Christoph Hellwig wrote: On Wed, Aug 03, 2005 at 07:55:12PM +0200, Bastian Blank wrote: - Each arch may specify an architectury specific patch, each image package may specify another patch, it may shared between more than one image. Or fix the architectures to not require them. The mips changes are fine for any other architecture, although they should be split into a few more. The m68k patch as-is isn't, but we hope to have m68k compiling from mainline sources soon after the 2.6.14 tree opens. I hope the powerpc/apus patch will be fine soon, but what about things like the (upcoming ?) powerpc/nubus patch ? Let's just work with the people to sort it out early enough. It's not like it'll be stable enough for a distro as soon as the port is mostly running anyway. I have big hopes for the apus case to be cleanly integrated in the near future, but the nubus case is more problematic. But we will see. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322034: periodic Kernel panic with reiserfs 3.6 partition (twice a month)
Package: kernel-image-2.6.11-1-686 Version: 2.6.11-7 Severity: normal SYMTOMS The combination of LVM2 + Kernel 2.6.11 + Reiserfs 3.6 periodically paniced about 1-2 times a month during period of more than 6 months. BACKGROUND The 60G laptop hard drive was partitioned using standard Debian netinstaller using one vg0 group (LVM2) containing 3 partitions: /var= ext3 /usr= Reiserfs /home = ext3 Like below. However this listing no longer show the reserfs parition, since the problematic partition was recently converted to ext3. /dev/mapper/vg0-home on /home type ext3 (rw,data=journal) /dev/mapper/vg0-usr on /usr type ext3 (rw,data=journal) /dev/mapper/vg0-var on /var type ext3 (rw,data=journal) OTHER INFORMATION See the atached notes in case they provide some more light to this situation. As for testing why this happend I'm unable to shed more light into this. I no longer use reiserfs partitions. The Laptop served for: - MTA; Exim 4.52 (daemon heavy) - Database; Postgres 7.4.7 - Version control; CVSd server 1.0.7 The services were not under heavy load (average load value 0.1-0.5) with 312M memory since they served only small home network. The PC was connected with - WiFi; Orinoco Lucent gold 10Mb Any of the above disk I/O may have triggered the corruption or then it may be something with reiserfs and kernel interoperability. --- [NOTE: LVM information] # pvscan -v Wiping cache of LVM-capable devices Wiping internal cache Walking through all physical volumes PV /dev/hda6 VG vg0 lvm2 [49.79 GB / 0free] Total: 1 [49.79 GB] / in use: 1 [49.79 GB] / in no VG: 0 [0 ] # lvdisplay vg0 --- Logical volume --- LV Name/dev/vg0/usr VG Namevg0 LV UUIDFSBHgx-ivV2-Et44-xOBQ-6oXV-vFjF-COFkQT LV Write Accessread/write LV Status available # open 1 LV Size3.00 GB Current LE 768 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:0 --- Logical volume --- LV Name/dev/vg0/var VG Namevg0 LV UUIDnAlu24-D3s2-21fX-Vevz-5mAn-1H83-v7LI1i LV Write Accessread/write LV Status available # open 1 LV Size30.01 GB Current LE 7683 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:1 --- Logical volume --- LV Name/dev/vg0/home VG Namevg0 LV UUIDOz6Nb5-GuJe-OgJ6-vXKB-qg7s-7jD3-ZgHJBi LV Write Accessread/write LV Status available # open 1 LV Size16.78 GB Current LE 4295 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:2 # lvdisplay vg0 --- Logical volume --- LV Name/dev/vg0/usr VG Namevg0 LV UUIDFSBHgx-ivV2-Et44-xOBQ-6oXV-vFjF-COFkQT LV Write Accessread/write LV Status available # open 1 LV Size3.00 GB Current LE 768 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:0 --- Logical volume --- LV Name/dev/vg0/var VG Namevg0 LV UUIDnAlu24-D3s2-21fX-Vevz-5mAn-1H83-v7LI1i LV Write Accessread/write LV Status available # open 1 LV Size30.01 GB Current LE 7683 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:1 --- Logical volume --- LV Name/dev/vg0/home VG Namevg0 LV UUIDOz6Nb5-GuJe-OgJ6-vXKB-qg7s-7jD3-ZgHJBi LV Write Accessread/write LV Status available # open 1 LV Size16.78 GB Current LE 4295 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:2 bongo:~# vgdisplay vg0 --- Volume group --- VG Name vg0 System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 6 VG Access read/write VG Status resizable MAX LV0 Cur LV3 Open LV 3 Max PV0 Cur PV1 Act PV1 VG Size 49.79 GB PE Size 4.00 MB Total PE 12746 Alloc PE / Size 12746 / 49.79 GB Free PE / Size 0 / 0 VG UUID
Bug#322058: please include vt1211 sensor chip patch
Package: linux-source-2.6.12 Version: 2.6.12-1 Severity: wishlist Hi, It would be wonderful if you could include this patch in the stock debian kernel: http://hem.bredband.net/ekmlar/vt1211.html It's the sensor chip contained in mini-ITX boards, among others, providing temperature readings, etc. Regards, -- Álvaro Martínez Echevarría ``Pero yo que he sentido una vez en mis manos temblar la alegría / ya no podré morir nunca. / Pero yo que he tocado una vez las agudas agujas del pino / ya no podré morir nunca''. [José Hierro, El muerto]
Bug#322086: ALSA support for ali5451 is sill broken
Package: linux-image-2.6.12-1-686 Version: 2.6.12-1 In April, I filed the attached bug report, which was summarily closed with a claim that a workaround existed and it was fixed in version 2.6.12. At the time I was too busy to look into this further, so I just limped along without sound and waited for 2.6.12. Well, 2.6.12 is here now, and it doesn't fix my sound problems. I have exactly the same symptoms that I did under 2.6.11: sound devices are present and can be accessed by programs as if everything was normal, but nothing comes out of the speakers. Moreover, I finally got around to trying the workaround that was posted to my previous bug report. It doesn't fix the problem under *either* 2.6.11 or 2.6.12 for me. Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | Fate always wins... | | at least, when people stick to the rules. | | -- Terry Pratchett, _Interesting Times_ | \ Got APT? -- Debian GNU/Linux http://www.debian.org ---/ ---BeginMessage--- Package: kernel-image-2.6.11-1-686 Version: 2.6.11-2 Severity: normal My sound card worked fine in 2.6.10, but I don't get any sound output in 2.6.11. The driver is loaded and appears in /proc: jester:~ lsmod|grep snd snd_usb_audio 67392 0 snd_usb_lib13088 1 snd_usb_audio usbcore 120312 7 usbhid,ehci_hcd,uhci_hcd,pwc,snd_usb_audio,snd_usb_lib snd_rawmidi24032 1 snd_usb_lib snd_seq_device 8652 1 snd_rawmidi snd_ali545123556 2 snd_ac97_codec 78360 1 snd_ali5451 snd_pcm_oss53344 1 snd_pcm92712 4 snd_usb_audio,snd_ali5451,snd_ac97_codec,snd_pcm_oss snd_timer 24580 1 snd_pcm snd_page_alloc 10020 1 snd_pcm snd_mixer_oss 19872 2 snd_pcm_oss snd55300 9 snd_usb_audio,snd_rawmidi,snd_seq_device,snd_ali5451,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss soundcore 9664 3 snd jester:~ cat /proc/asound/cards 0 [A5451 ]: ALI5451 - ALI 5451 ALI 5451 at 0x8800, irq 11 Programs that use the sound card appear to work fine, but no sound output is generated. Of course, the mixer volume is just where it was before (about 80% of the maximum). Daniel -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- /- Daniel Burrows [EMAIL PROTECTED] -\ | You keep on using that word. I do not think | |it means what you think it means. | | -- The Princess Bride | \--- Be like the kid in the movie! Play chess! -- http://www.uschess.org --/ pgpBOLvuUjCfZ.pgp Description: PGP signature ---End Message--- pgpVTpFHk2jHj.pgp Description: PGP signature
Re: linux-2.6_2.6.12-2_i386.changes REJECTED
On Mon, Aug 08, 2005 at 01:18:20PM -0700, Debian Installer wrote: Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. I guess we need an epoch -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6_2.6.12-2_i386.changes REJECTED
On Tue, 2005-08-09 at 10:34 +0900, Horms wrote: On Mon, Aug 08, 2005 at 01:18:20PM -0700, Debian Installer wrote: Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. I guess we need an epoch Give the man an epoch! 2.6.12-2 is re-tagged in svn, w/ some epoch spiffiness that waldi did; only the transition packages (kernel-image-*) got epoch'd. We're both building test packages.. Hopefully this should appease katie. -- Andres Salomon [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#321167: linux-image: say the difference vs. kernel-image
Processing commands for [EMAIL PROTECTED]: tag 321167 +pending Bug#321167: linux-image: say the difference vs. kernel-image There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321964: linux-2.6: package that depends on all -headers for $arch
On Mon, Aug 08, 2005 at 12:50:47PM -0400, Andres Salomon wrote: On Mon, Aug 08, 2005 at 03:52:33PM +0200, Max Vozeler wrote: Package: linux-2.6 Version: 2.6.12-1 Severity: wishlist There used to exist packages that depend on all -headers packages for a particular arch (eg. kernel-headers-2.6.11-1-i386). This is very useful for build-depends when autobuilding external module packages. Such packages seem to no longer exist with the new kernel packaging - please consider to re-add something like it. Now that waldi has gencontrol.py creating dummy packages and rules for the various linux-image and linux-header packages, we can throw the all-headers package back in. There was some issue of what it should actually be called, however.. Calling it linux-headers-2.6.12-1-i386 doesn't work too well for all archs, since we end up w/ linux-headers-2.6.12-1-powerpc, which conflicts w/ the name of a flavour. linux-headers-2.6.12-1-arch-all - linux-headers-2.6.12-1-i386-all - linux-headers-2.6.12-1-powerpc-all Does that work? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321885: linux-source-2.6.12: Please enable CONFIG_PALINFO as built-in for IA64
tag 321885 +pending thanks On Mon, Aug 08, 2005 at 10:00:25AM +1000, Ian Wienand wrote: Package: linux-source-2.6.12 Severity: normal Tags: patch Hi, As mentioned in http://www.gelato.unsw.edu.au/archives/linux-ia64/0508/14811.html CONFIG_PALINFO isn't built-in to Debian kernels. This causes important developer applications such as pfmon, that should just work, to fail. I believe it would be best to enable it by default, as per attached. Hi, Dann Frazier has enabled this in the debian-kernel SVN tree and it should appear in the next release. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322058: marked as done (please include vt1211 sensor chip patch)
Your message dated Tue, 9 Aug 2005 11:45:19 +0900 with message-id [EMAIL PROTECTED] and subject line Bug#322058: please include vt1211 sensor chip patch 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 Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Aug 2005 22:35:01 + From [EMAIL PROTECTED] Mon Aug 08 15:35:01 2005 Return-path: [EMAIL PROTECTED] Received: from mail23.sea5.speakeasy.net [69.17.117.25] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E2GCz-6V-00; Mon, 08 Aug 2005 15:35:01 -0700 Received: (qmail 12534 invoked from network); 8 Aug 2005 22:35:00 - Received: from marsupilami.thehackers.org ([EMAIL PROTECTED]) (envelope-sender [EMAIL PROTECTED]) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for [EMAIL PROTECTED]; 8 Aug 2005 22:35:00 - Received: from alvaro (helo=localhost) by marsupilami.thehackers.org with local-esmtp (Exim 3.35 #1 (Debian)) id 1E2GCu-0007qO-00 for [EMAIL PROTECTED]; Mon, 08 Aug 2005 15:34:56 -0700 Date: Mon, 8 Aug 2005 15:34:56 -0700 (PDT) From: Alvaro Martinez Echevarria [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: please include vt1211 sensor chip patch Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY=8323328-2067676060-1123540496=:27872 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_20,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-2067676060-1123540496=:27872 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Package: linux-source-2.6.12 Version: 2.6.12-1 Severity: wishlist Hi, It would be wonderful if you could include this patch in the stock debian kernel: http://hem.bredband.net/ekmlar/vt1211.html It's the sensor chip contained in mini-ITX boards, among others, providing temperature readings, etc. Regards, -- =C1lvaro Mart=EDnez Echevarr=EDa ``Pero yo que he sentido una vez en mis manos temblar la alegr=EDa / ya no podr=E9 morir nunca. / Pero yo que he tocado una vez las agudas agujas del pino / ya no podr=E9 morir nunca''. [Jos=E9 Hierro, El muerto] --8323328-2067676060-1123540496=:27872-- --- Received: (at 322058-done) by bugs.debian.org; 9 Aug 2005 02:47:01 + From [EMAIL PROTECTED] Mon Aug 08 19:47:01 2005 Return-path: [EMAIL PROTECTED] Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E2K8r-0007dz-00; Mon, 08 Aug 2005 19:47:01 -0700 Received: by koto.vergenet.net (Postfix, from userid 7100) id 9E7F834039; Tue, 9 Aug 2005 11:47:00 +0900 (JST) Date: Tue, 9 Aug 2005 11:45:19 +0900 From: Horms [EMAIL PROTECTED] To: Alvaro Martinez Echevarria [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#322058: please include vt1211 sensor chip patch Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] X-Cluestick: seven User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 On Mon, Aug 08, 2005 at 03:34:56PM -0700, Alvaro Martinez Echevarria wrote: Package: linux-source-2.6.12 Version: 2.6.12-1 Severity: wishlist Hi, It would be wonderful if you could include this patch in the stock debian kernel: http://hem.bredband.net/ekmlar/vt1211.html It's the sensor chip contained in mini-ITX boards, among others, providing temperature readings, etc. The kernel packages provided by the kernel-team do not include out of tree drivers, as it is too much of a maintenice buden, and we would like to encourage people to get their code accepted upstream. If this is not possible a kernel-patch package is probably the best option. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a
Bug#321167: linux-image: say the difference vs. kernel-image
tag 321167 +pending thanks On Mon, Aug 08, 2005 at 10:51:36AM +0200, Sven Luther wrote: On Sat, Aug 06, 2005 at 10:11:21AM +0800, Dan Jacobson wrote: I'm sorry but all that is over my head, beyond my level. All I know is that all the files in pool/main/l/linux-2.6/ need Descriptions that even the most bumblesome user could understand. You are welcome to propose such descriptions in a patch or even just plain text in this bug report. Dan, I hope this patch addresses your concerns. It also fixes some minor formating issues, just ignore that noise. -- Horms Index: control.headers.in === --- control.headers.in (revision 3684) +++ control.headers.in (working copy) @@ -11,7 +11,12 @@ the [EMAIL PROTECTED]@[EMAIL PROTECTED]@-(flavour) package, matching the flavour of the kernel you intend the build for. To obtain such a set for the currently running kernel it is sufficient to run a command - + . apt-get install [EMAIL PROTECTED]@[EMAIL PROTECTED]@-$(uname -r) . - and it will be unpacked in /usr/src/[EMAIL PROTECTED]@[EMAIL PROTECTED]@-(flavour). + and it will be unpacked in + /usr/src/[EMAIL PROTECTED]@[EMAIL PROTECTED]@-(flavour). + . + This packages is produced using an updated kernel packaging system + and replaces older kernel-headers packages + Index: control.image.in === --- control.image.in(revision 3684) +++ control.image.in(working copy) @@ -16,3 +16,7 @@ Description: Linux kernel @version@ image on @class@ machines This package provides the binary image and pre-built loadable modules for Linux kernel @version@ on @class@ machines. + . + This packages is produced using an updated kernel packaging system + and replaces older kernel-image packages + Index: control.main.in === --- control.main.in (revision 3684) +++ control.main.in (working copy) @@ -29,6 +29,9 @@ /usr/share/doc/[EMAIL PROTECTED]@/Documentation/00-INDEX . for the detailed description of the contents. + . + This packages is produced using an updated kernel packaging system + and replaces older kernel-doc packages Package: [EMAIL PROTECTED]@ Architecture: all @@ -42,6 +45,9 @@ patches. Note that these patches do NOT apply against a pristine Linux @version@ kernel but only against the kernel tarball [EMAIL PROTECTED]@[EMAIL PROTECTED]@.orig.tar.gz from the Debian archive. + . + This packages is produced using an updated kernel packaging system + and replaces older kernel-source packages Package: [EMAIL PROTECTED]@ Architecture: all @@ -69,3 +75,6 @@ . The package serves no purpose outside of the Debian build and archive infrastructure. + . + This packages is produced using an updated kernel packaging system + and replaces older kernel-tree packages Index: control.headers.flavour.in === --- control.headers.flavour.in (revision 3684) +++ control.headers.flavour.in (working copy) @@ -8,6 +8,10 @@ This package provides the architecture-specific kernel header files for Linux kernel @version@ on @class@ machines, generally used for building out-of-tree kernel modules. These files are going to be - installed into /usr/src/[EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@flavour@, and can - be used for building modules that load into the kernel provided by the - [EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@flavour@ package. + installed into /usr/src/[EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@flavour@, + and can be used for building modules that load into the kernel provided by + the [EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@flavour@ package. + . + This packages is produced using an updated kernel packaging system + and may replace packages older kernel-headers or kernel-build + depending on the architecture -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#321866: kernel-image-2.6.8-2-k7: tattered symlinks left in / after purge
Processing commands for [EMAIL PROTECTED]: reassign 321866 linux-2.6 Bug#321866: kernel-image-2.6.8-2-k7: tattered symlinks left in / after purge Bug reassigned from package `kernel-image-2.6.8-2-k7' to `linux-2.6'. severity 321866 important Bug#321866: kernel-image-2.6.8-2-k7: tattered symlinks left in / after purge Severity set to `important'. merge 321866 320422 321752 Bug#320422: linux-image-2.6.12-1: error in postinst that creates dangling symlinks Bug#321752: linux-image-2.6.12-1-k7: generates incorrect /vmlinuz, /initrd.img links Bug#321866: kernel-image-2.6.8-2-k7: tattered symlinks left in / after purge Merged 320422 321752 321866. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6_2.6.12-2_i386.changes REJECTED
On Tue, 2005-08-09 at 10:34 +0900, Horms wrote: On Mon, Aug 08, 2005 at 01:18:20PM -0700, Debian Installer wrote: Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. I guess we need an epoch Why not use linux-image-foo instead of kernel-image-foo, w/ an appropriate Replaces/Conflicts/Provides? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Security Updates and kernel-tree fun
Hi, Referring to http://people.debian.org/~dannf/kernel-stats/kernel-avail.html (thanks dannf) I notice that the following kernel-tree versions are in use in Sarge: 2.4.27-10: alpha, i386, ia64, powerpc (latest) 2.4.27-9: powerpc 2.4.27-8: s390 2.4.27-5: apus(so old its scary) 2.6.8-16: alpha, i386, ia64, m68k (latest) 2.6.8-15: sparc 2.6.8-13: hppa, powerpc, s390 Now as I understand, security updates can only include security fixes. Examining 2.6.8, in the case of arches that use 2.6.8-16, this is easy enough, just add security fixes, make that 2.6.8-16sarge1, and be done with it. Same for sarge2 and so on and so forth. But what about the architectures that use 2.6.8-15 and 2.6.8-13? The easy way out would be for them to use 2.6.8-16sarge1 as well. But this means that they get a bunch of non-security patches (though the majority are security fixes) to bring the up to 2.6.8-16 and then the 2.6.8-16sarge1 fixes on top of that. Presumably this is not acceptable to the security team (though it would be great if it was). So my idea is to extend the way we handle patches internally. And as of 2.6.8-13 and 2.4.27-8 (2.4.27-5 is so old I really am scared), and mark off all the security patches. Fortunately this is mostly done in the change log. And then allow us to build a kernel-source-2.6.8-16sarge1, that can satisfy kernel-tree-2.6.8-Nsarge1, where 13 = N = 16. Confused? Let me try and illustrate by example. Lets say we examine 2.6.8-13, 14, 15, 16 and what is currently in SVN. We can do this by examining the series files - which are in turn used to patch the tree to any known version. series/2.6.8-14: A.patch b.patch series/2.6.8-15: C.patch d.patch series/2.6.8-16: E.patch f.patch series/2.6.8-16.svn: G.patch h.patch (2.6.8-16.svn is just a dummy name I made up to represent the patches added to svn since 2.6.8-16) So basically, if you have 2.6.8-13 and you want to get to 2.6.8-14, you apply the patches A and b. And if you have 2.6.8-13 and you want to patch all the way up to the latest and greatest, you add patches A, b, C, d, E, f, G and h. So far so good. Now lets say, that through examination of the change log we know that the uppercase patches (A, C, E, G) are either security fixes, or required for a security fixes. My idea is to copy the series directory and remove all the non-security patches, using the data above this would give. sec-series/2.6.8-14: A.patch sec-series/2.6.8-15: C.patch sec-series/2.6.8-16: E.patch sec-series/2.6.8-16.svn: G.patch And then extend the way the patching works so that if I ask for series/2.6.8-13sarge1, then it will patch up to 2.6.8-13 using the data in series (information for = 2.6.8-13 not shown above), and then use the data in sec-series beyond that. So 2.6.8-13sarge1 would be a tree with the following applied: A.patch C.patch E.patch G.patch 2.6.8-15sarge1 would be A.patch b.patch C.patch d.patch E.patch G.patch And 2.6.8-16sarge1 would be A.patch b.patch C.patch d.patch E.patch f.patch G.patch The nice thing about this approach is that the kernel-source package would contain all the updated patches, so if people wanted to build their own kernel, they could choose a fairly wide range of patch levels. And the other nice thing is that most of the security patches are already noted as such in the change logs, so this wouldn't be terribly difficult to implement. The bad thing about this is that its kind of complex, and thus certain to confuse people. But I think that is a reflection of the complexity of the problem at hand (and indeed the complexity of the kernel packaging in Sarge). -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6_2.6.12-2_i386.changes REJECTED
On Mon, Aug 08, 2005 at 10:31:31PM -0600, dann frazier wrote: On Tue, 2005-08-09 at 10:34 +0900, Horms wrote: On Mon, Aug 08, 2005 at 01:18:20PM -0700, Debian Installer wrote: Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686-smp_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-386_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-k7_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in unstable = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in testing = new version (2.6.12-2) targeted at unstable. Rejected: kernel-image-2.6-686_2.6.12-2_i386.deb: old version (101) in stable = new version (2.6.12-2) targeted at unstable. I guess we need an epoch Why not use linux-image-foo instead of kernel-image-foo, w/ an appropriate Replaces/Conflicts/Provides? Good point. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6_2.6.12-2_i386.changes REJECTED
On Mon, Aug 08, 2005 at 10:31:31PM -0600, dann frazier wrote: Why not use linux-image-foo instead of kernel-image-foo, w/ an appropriate Replaces/Conflicts/Provides? This is not an appropriate upgrade path as this headers don't ask apt to install the new package. Bastian -- We have phasers, I vote we blast 'em! -- Bailey, The Corbomite Maneuver, stardate 1514.2 signature.asc Description: Digital signature
