Re: Opening trunk for post-lenny changes?
Quoting Frans Pop (elen...@planet.nl): > On Wednesday 24 December 2008, Christian Perrier wrote: > > About Colin's remarks, my personal opinion is that it could be time to > > resync the lenny branch with trunk and work off that lenny branch, > > yes. Definitely, even. > > If "the team" would like me to I'm willing to do the sync. It's 100% clear > to me what is targeted for Lenny and thus what still needs syncing. I'm 150% OK with that, Frans. > > That way we could IMO open up trunk for post-lenny commits and re-enable > l10n syncs even without waiting for Otavio's return from VAC. > > Of course I'd take responsibility for any mistakes and do any clean ups if > it should later turn out any would be needed. I don't think anyone would blame you in any way. You know that we're doing much worse mistakes than you might do... Merry Christmas to you if you happen to celebrate it in some way... signature.asc Description: Digital signature
Processing of linux-kernel-di-arm-2.6_1.36_multi.changes
linux-kernel-di-arm-2.6_1.36_multi.changes uploaded successfully to localhost along with the files: crypto-dm-modules-2.6.26-1-orion5x-di_1.36_arm.udeb nic-modules-2.6.26-1-orion5x-di_1.36_arm.udeb input-modules-2.6.26-1-iop32x-di_1.36_arm.udeb core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb usb-modules-2.6.26-1-iop32x-di_1.36_arm.udeb fat-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-iop32x-di_1.36_arm.udeb sata-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb ide-modules-2.6.26-1-footbridge-di_1.36_arm.udeb usb-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb sata-modules-2.6.26-1-iop32x-di_1.36_arm.udeb md-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb loop-modules-2.6.26-1-orion5x-di_1.36_arm.udeb ext2-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb nic-usb-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb md-modules-2.6.26-1-iop32x-di_1.36_arm.udeb loop-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crypto-modules-2.6.26-1-footbridge-di_1.36_arm.udeb sata-modules-2.6.26-1-orion5x-di_1.36_arm.udeb loop-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb isofs-modules-2.6.26-1-iop32x-di_1.36_arm.udeb usb-storage-modules-2.6.26-1-orion5x-di_1.36_arm.udeb scsi-core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb linux-kernel-di-arm-2.6_1.36.tar.gz usb-storage-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-footbridge-di_1.36_arm.udeb reiserfs-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb multipath-modules-2.6.26-1-orion5x-di_1.36_arm.udeb fat-modules-2.6.26-1-footbridge-di_1.36_arm.udeb nic-shared-modules-2.6.26-1-orion5x-di_1.36_arm.udeb nls-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb nls-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crc-modules-2.6.26-1-orion5x-di_1.36_arm.udeb cdrom-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb jffs2-modules-2.6.26-1-orion5x-di_1.36_arm.udeb nic-usb-modules-2.6.26-1-orion5x-di_1.36_arm.udeb md-modules-2.6.26-1-footbridge-di_1.36_arm.udeb nic-modules-2.6.26-1-footbridge-di_1.36_arm.udeb core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb input-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb nic-shared-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crc-modules-2.6.26-1-footbridge-di_1.36_arm.udeb md-modules-2.6.26-1-orion5x-di_1.36_arm.udeb multipath-modules-2.6.26-1-iop32x-di_1.36_arm.udeb input-modules-2.6.26-1-orion5x-di_1.36_arm.udeb usb-storage-modules-2.6.26-1-iop32x-di_1.36_arm.udeb core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb usb-modules-2.6.26-1-footbridge-di_1.36_arm.udeb usb-storage-modules-2.6.26-1-footbridge-di_1.36_arm.udeb kernel-image-2.6.26-1-iop32x-di_1.36_arm.udeb fat-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ext2-modules-2.6.26-1-iop32x-di_1.36_arm.udeb nic-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb ata-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crc-modules-2.6.26-1-iop32x-di_1.36_arm.udeb kernel-image-2.6.26-1-ixp4xx-di_1.36_arm.udeb nic-usb-modules-2.6.26-1-iop32x-di_1.36_arm.udeb fat-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb ext3-modules-2.6.26-1-iop32x-di_1.36_arm.udeb isofs-modules-2.6.26-1-footbridge-di_1.36_arm.udeb kernel-image-2.6.26-1-orion5x-di_1.36_arm.udeb ide-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crc-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-modules-2.6.26-1-iop32x-di_1.36_arm.udeb reiserfs-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ext3-modules-2.6.26-1-orion5x-di_1.36_arm.udeb cdrom-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb multipath-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb reiserfs-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb loop-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb scsi-core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb nic-modules-2.6.26-1-iop32x-di_1.36_arm.udeb multipath-modules-2.6.26-1-footbridge-di_1.36_arm.udeb reiserfs-modules-2.6.26-1-footbridge-di_1.36_arm.udeb ext2-modules-2.6.26-1-orion5x-di_1.36_arm.udeb scsi-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb usb-modules-2.6.26-1-orion5x-di_1.36_arm.udeb linux-kernel-di-arm-2.6_1.36.dsc ide-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-modules-2.6.26-1-orion5x-di_1.36_arm.udeb kernel-image-2.6.26-1-footbridge-di_1.36_arm.udeb scsi-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ext3-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
linux-kernel-di-arm-2.6_1.36_multi.changes ACCEPTED
Accepted: ata-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ata-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb cdrom-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/cdrom-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb cdrom-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/cdrom-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crc-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crc-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crc-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crc-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crc-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crc-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crc-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crc-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-core-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-core-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-core-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-dm-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-dm-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-dm-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-dm-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-dm-modules-2.6.26-1-orion5x-di_1.36_arm.udeb crypto-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-modules-2.6.26-1-footbridge-di_1.36_arm.udeb crypto-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-modules-2.6.26-1-iop32x-di_1.36_arm.udeb crypto-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb crypto-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/crypto-modules-2.6.26-1-orion5x-di_1.36_arm.udeb ext2-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext2-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ext2-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext2-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb ext2-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext2-modules-2.6.26-1-orion5x-di_1.36_arm.udeb ext3-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext3-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ext3-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext3-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb ext3-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ext3-modules-2.6.26-1-orion5x-di_1.36_arm.udeb fat-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/fat-modules-2.6.26-1-footbridge-di_1.36_arm.udeb fat-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/fat-modules-2.6.26-1-iop32x-di_1.36_arm.udeb fat-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/fat-modules-2.6.26-1-ixp4xx-di_1.36_arm.udeb fat-modules-2.6.26-1-orion5x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/fat-modules-2.6.26-1-orion5x-di_1.36_arm.udeb ide-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ide-core-modules-2.6.26-1-iop32x-di_1.36_arm.udeb ide-modules-2.6.26-1-footbridge-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ide-modules-2.6.26-1-footbridge-di_1.36_arm.udeb ide-modules-2.6.26-1-iop32x-di_1.36_arm.udeb to pool/main/l/linux-kernel-di-arm-2.6/ide-mod
Re: Installation report HP-715/64 (HIL)
Frans Pop wrote: > On Wednesday 24 December 2008, Moritz Muehlenhoff wrote: >>> Is it possible that someone from the debian-installer teams add this >>> "modprobe hilkbd" somewhere to the bootup process? ... >> Can that be considered for rc2? > > Theoretically that would still be possible, but it is extremely late in > the day for such a change, especially without any detailed info about how > *exactly* this should be implemented. Sure. > Questions that come to mind are: > - why doesn't the kernel/udev autoload this module? Probably yes, but as we discussed last time, this needs to be implemented. I already looked into implementing it, but sadly it isn't that easy to understand all the flow between kernel and userspace and how to handle it then. So, it's still on my plan to do it, but there were some other kernel crashes which needed to be fixed before (e.g. bug 478717). Anyway, adding the needed stuff to udev will probably be too late for lenny anyway. > - is there any way to recognize whether the module should be loaded or > not (most hppa installs are headless)? > - if it's decided to load the module unconditionally for the installer, > it may still be possible to only do so when needed for the installed > system; can this be recognized somehow? I started up my system to find a way to detect if the hilkbd module should be loaded or not. Sadly I didn't find a clean way via sysfs or procfs. The only ugly solution I found is to grep the dmesg for the string "HIL", as the HIL controller is then printed while doing the inventory scan: : Searching for devices... : Found devices: : 1. Mirage Jr GSC Builtin Graphics at 0xf800 [1] ... : ... : 13. Mirage Jr Wax HIL at 0xf0201000 [5/0/1] : ... But even if this module is loaded on a system which does not has HIL this wouldn't hurt in any way, as the driver (drivers/input/keyboard/hilkbd.c) is constructed that way that it only gets initialized if it finds the HIL controller itself. This means that the linux kernel only calls the initialization function hil_init_chip() if the system has the HIL controller and it has been sucessfully matched against the contents of hil_tbl[]. So, modprobing for hilkbd will never break any non-HIL systems. I know you added some unconditional modprobes for some specifc modules for parisc (I forgot which ones, I think SCSI and such) in the past. My proposal would be to just add the modprobe for hilkbd there blindly as well. > - is loading the module for the installed system needed for the initrd > too (would be my guess), or just for the final system? Both. > We have repeatedly indicated in the debian-hppa list that the D-I team > needs porter support and this is *exactly* the kind of issue for which > knowledgable porter support is needed. I even had a long discussion with > Helge himself about that. Yes, I know and I've not forgotten that. http://www.archivum.info/linux.debian.ports.hppa/2008-06/msg00038.html http://lists.debian.org/debian-hppa/2008/05/msg00037.html > As this issue has been known for ages my first reaction is that it is too > late for RC2 and for Lenny. However, *if* porters work with the D-I team > to get the questions above answered the change could be implemented early > for squeeze and, after testing, it could then be considered for > backporting for a stable update release. I fully can understand your reaction here. Of course it would be sad if machines with HIL keyboards are _only_ installable via serial console then, but since they are quite old I don't assume there will be so many people trying lenny on parisc with HIL at all. On the other side, if you would add this modprobe I would try the lenny installer at once on 4 very different machines to rule out any problems due to the modprobe: - 715/64 with HIL only - B160L, no HIL, PS/2 keyboard/mouse - C3000 (32 and 64bit kernel), no HIL, USB keyboard/mouse only - Tadpole parisc laptop, PS/2 keyboard/mouse only Best regards, Helge -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509711: win32-loader: [INTL:vi] Vietnamese program translation update
On Thu, Dec 25, 2008 at 04:48:11PM +1030, Clytie Siddall wrote: > Package: win32-loader > Version: > Tags: l10n patch > Severity: wishlist > > The updated Vietnamese translation for the program file: win32-loader Thanks. But please do not open bugs for such things, you can commit it directly in SVN (I checked that you have access). Just make sure the build still works (e.g. run "debian/rules build"). -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509723: Support TFTP preseed fetch method
Package: debian-installer
Severity: wishlist
(I have a feeling I already reported this and been tagged WONTFIX;
apologies if this is the case and I can't find it in the BTS.)
Currently AFAICT the preseed file must be supplied either within the
initrd, on local media (including the install CD), or via HTTP or FTP.
I would find it useful if the preseed file could be fetched via TFTP.
This is particularly useful when netbooting, as I already have the
netboot files in debian-installer/ -- it would be easy for me to have
a second tree d-i/{etch,lenny}/preseed.cfg.
This is also useful when doing "fake" netboots with qemu, because then
I could do something like
qemu -tftp d-i/etch/ -bootp preseed.cfg \
-kernel debian-installer/linux -initrd debian-installer/initrd.gz
without needing to run a separate http process. (QEMU has built-in
support for providing DHCP and TFTP to the VM, but not HTTP.)
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#509723: Support TFTP preseed fetch method
Processing commands for cont...@bugs.debian.org: > reassign 509723 preseed Bug#509723: Support TFTP preseed fetch method Bug reassigned from package `debian-installer' to `preseed'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509723: Support TFTP preseed fetch method
reassign 509723 preseed thanks Quoting Trent W. Buck (trentb...@gmail.com): > Package: debian-installer > Severity: wishlist > > (I have a feeling I already reported this and been tagged WONTFIX; > apologies if this is the case and I can't find it in the BTS.) At least not in the bug reports for the preseed package. So let's record this here..:-) signature.asc Description: Digital signature
