Bug#574096: installation problem report
Package: installation-reports Boot method: USB Flash Image version: debian-504-i386-netinst.iso Date: 03/16/10 Machine: Intel D510MO motherboard Processor: Intel Atom Memory: 512MB Partitions: installation media: USB Flash 2GB, target media: USB Flash 8GB Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] looking for drivers on the CD Configure network: [ ] Detect CD: [E] no CD present in the system - I quit Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I'm experimenting with various distributions and I successfully installed Ubuntu, Puppy, Fedora from USB Flash to USB Flash. Debian is the first distro, where I had to go USB CD to USB Flash route. Regards, Paul Jurczak. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/138183.84691...@web65405.mail.ac4.yahoo.com
Bug#574096: installation problem report
On Tuesday 16 March 2010, Paul Jurczak wrote: Comments/Problems: I'm experimenting with various distributions and I successfully installed Ubuntu, Puppy, Fedora from USB Flash to USB Flash. Debian is the first distro, where I had to go USB CD to USB Flash route. Debian supports all kinds of installation methods. Looks to me like you simply did not try the correct one. For installations from USB stick you should use the hd-media installation method. Please see our installation guide. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161059.50401.elen...@planet.nl
Re: Getting d-i to find firmware on the CD generated by debian-cd
[Petter Reinholdtsen] Yesterday, I figured out a workaround for this, and I wanted to share the solution with the rest of you, and ask if perhaps the default behaviour of debian-cd or d-i (hw-detect) should change to make this workaround unneeded. Further testing of this fix proved that it is insufficient. hw-detect call check-missing-firmware, which look on several devices (disk, USB sticks, floppies) for firmware, but fail to look on the CD itself. This, I must admit, is very sad. I had a look at the source of check-missing-firmware and saw it was looking in the firmware/ directory of several devices, and assumed it would also check the boot media, but no. :( Should hw-detect also look for firmware on the CD? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316104634.ga4...@login1.uio.no
Bug#574096: installation problem report
Please always reply to the BTS, not to the person responding. On Tuesday 16 March 2010, you wrote: Thank you for quick response. Do you mean that copying hd-media/boot.img.gz and .iso image to USB Flash will result in different installation behavior than preparing USB Flash with LiveUSB Creator and plain .iso image? I have no idea what LiveUSB Creator does. But if it only uses what's on the image it cannot work since, as you noticed, the installation image included on that will look for a CD *drive* instead of for a CD *image*. The main feature of the hd-media installation image is that it looks for CD images. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161208.03750.elen...@planet.nl
Re: Getting d-i to find firmware on the CD generated by debian-cd
On Tuesday 16 March 2010, Petter Reinholdtsen wrote: Further testing of this fix proved that it is insufficient. hw-detect call check-missing-firmware, which look on several devices (disk, USB sticks, floppies) for firmware, but fail to look on the CD itself. This, I must admit, is very sad. I had a look at the source of check-missing-firmware and saw it was looking in the firmware/ directory of several devices, and assumed it would also check the boot media, but no. :( Should hw-detect also look for firmware on the CD? I think the problem with that is that including the firmware on the CD in the first place is in contradiction with Debian's current policy not to include firmware in the distribution. The current firmware support is very explicitly limited to support loading from external media *prepared by the user*. An additional issue with non-free firmware is that including it in the way you propose would (I think) mean it will get loaded without any prompting of the user, which may in some cases violate licence terms. I can see that others may want to do things differently, but I'm not sure how much we can/should support that in standard D-I functionality. One option you have is to implement a custom, alternative version of 'mountmedia' for d-edu. Cheers, FJP P.S. Personally I would like to have more default support for loading firmware, but IMO we cannot do that without discussion with the rest of the project. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161237.45197.elen...@planet.nl
Re: Getting d-i to find firmware on the CD generated by debian-cd
Hi, On Dienstag, 16. März 2010, Frans Pop wrote: An additional issue with non-free firmware is that including it in the way you propose would (I think) mean it will get loaded without any prompting of the user, which may in some cases violate licence terms. i thought the same at first, but actually that's not the case. The user is still asked (by the package) if she wants to accept the licence. (As no preseeding takes place.) So there is only the issue of having the firmwares accessable in the first place, which should be preseeded/preseedable just like using non-free. cheers, Holger P.S.: should this be moved to a proper bug? signature.asc Description: This is a digitally signed message part.
Re: Getting d-i to find firmware on the CD generated by debian-cd
[Frans Pop] I think the problem with that is that including the firmware on the CD in the first place is in contradiction with Debian's current policy not to include firmware in the distribution. The current firmware support is very explicitly limited to support loading from external media *prepared by the user*. Well, the use case I am working on would be identical for a user who prepared a CD or DVD, so I believe it should work the same way with CDs and USB sticks. :) An additional issue with non-free firmware is that including it in the way you propose would (I think) mean it will get loaded without any prompting of the user, which may in some cases violate licence terms. Perhaps. I have not gotten to a point where I can test what happen. I believe the .deb will be installed normally into /target/ and display the license question at that point, but do not know yet. :) I can see that others may want to do things differently, but I'm not sure how much we can/should support that in standard D-I functionality. I'm working on a patch for hw-detect. One option you have is to implement a custom, alternative version of 'mountmedia' for d-edu. Actually, something causes main-menu to crash if I adjust mountmedia to return CD devices too, so I suspect it is better to adjust check-missing-firmware to also look in /cdrom/firmware/ for debs. This is the approach I am testing at the moment. Anyone know how the PXE installation can be adjusted to load firmware automatically from the .debs? I want servers with network cards needing firmware to work with PXE installation. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316114835.gc4...@login1.uio.no
Installer fails due to invalid signatures
Good morning, I sent a report to the debian bug reporting system (bug number 573791) but it seems to not have been taken serious, being shuffled between responsible owners. In short, a new net install fails completely everything time due to invalid signatures. A mirror install fails every time due to invalid signatures. A non mirror install fail on the security updates due to invalid signatures. And finally any current install fails on security updates due to invalid signatures. Not sure which section it is that ought look into this, but someone probably should. Happens with other lives debian based systems (e.g. ubuntu 9.10 server) too. I'm a novice Debian user (4 months), but have over 25 years across multiple systems and am a professional developer, so think I can recognise a must look at problem when I see one :) If it were only current installs that went wrong, I'd accept a user tweak being possible (though none of the suggested work arounds work), but for the new install to collapse 100% of the time isn't good. Thanks, Steve Clark - -sent 13th March 2010 Package: Apt-get as installed from CD 1 ISO of Debian 5.04. Also tried with net inst:Version: 5.04The bug has been happening since Friday, March 11th across all system here via multiple IPs. All were installed from Debian 5.04 CD ISO.- During apt-get update from an install by full CD ISO (CD 1) and changing sources.list to any of the security mirrors you get multiple warnings of invalid signatures for key id: 9AA38DCD55BE302B.-With net-inst (business card) CD:Attempting to install using mirror at ftp.uk.debian.org, you get the following error:Debstrap error:The following error occurred:Invalid release signature (key id: 9AA38DCD55BE302B)check /var/log/syslog or see virtual console 4 for the details-It suspect it's going to be affecting everyone with new installation attempts.Thanks in advance,Steve Clark -sent 14th March 2010 Good evening, I notice the bug has been re-assigned to the CD-ROM team. I'm not sure this is the most appropriate assignment, as further tests here have shown it also affects ubuntu server 9.10 installs too. I would suggest the problem lies with the latest security packages' signatures. If someone more experienced with debian installations could try a clean install for Debian 5.04 CD (linux system only - not using mirrors), select appropriate values for /etc/apt/sources and executre apt-get update they may recognise the problem immediately. I would further suggest that as it prevents any new installations of Debian since at least 11th March 2010, its serverity is a little higher than normal. Thanks, Steve Clark -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/005501cac4f3$9b5eaa90$6416a...@reallyweevil
Re: Getting d-i to find firmware on the CD generated by debian-cd
On Tuesday 16 March 2010, Holger Levsen wrote: On Dienstag, 16. März 2010, Frans Pop wrote: An additional issue with non-free firmware is that including it in the way you propose would (I think) mean it will get loaded without any prompting of the user, which may in some cases violate licence terms. i thought the same at first, but actually that's not the case. The user is still asked (by the package) if she wants to accept the licence. (As no preseeding takes place.) But that's only at the point where the package gets installed in the target system. And at that point the firmware is already in use. IMO a proper solution would ensure the licence dialog gets displayed before the firmware first gets loaded by the installer. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161350.45073.elen...@planet.nl
Re: Getting d-i to find firmware on the CD generated by debian-cd
On Tuesday 16 March 2010, Petter Reinholdtsen wrote: Actually, something causes main-menu to crash if I adjust mountmedia to return CD devices too, so I suspect it is better to adjust check-missing-firmware to also look in /cdrom/firmware/ for debs. Probably because the CD is already mounted and in use and mountmedia messes that up? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161352.30877.elen...@planet.nl
Bug#574116: hw-detect: Should look for firmware packages on CD and DVD too
Package: hw-detect
Version: 1.75
Tags:patch
User:debian-...@lists.debian.org
Usertag: debian-edu
When building a custom CD with firmware packages on the CD, and
symlinked from firmware/ to ../pool/non-free/, the packages are not
found by debian-installer. In fact, as far as I can see, there is no
way to put the firmware packages on a custom CD and get d-i to find
them.
I believe it should be possible to create a custom CD with the
firmware packages included, and propose to change hw-detect to make
sure it is able to find firmware packages on the CD. To avoid
cluttering the root, I propose to put such firmware debs in a
firmware/ subdirectory on the CD, and populate it with symlinks to the
debs in the APT repository on the CD. See
URL: http://lists.debian.org/debian-cd/2010/03/msg00023.html for a
description on how to do this using debian-cd.
If the deb include a license question displayed using debconf, the
question will still be presented when the deb is installed into
/target/, so the machine will not be set up to use non-free firmware
without notification. The non-free section of the mirror will not be
enabled automatically, so any updates to the firmware will not be
installed automatically.
This untested patch should implement my proposed change.
* Copy files using cp -aL to make sure not to copy symlinks but the
files pointed to by the symlinks.
* Add code to first check /cdrom/firmware/ for debs, and the look for
individual firmware files and debs and udebs on other media. Move
code to check debs and udebs to a new function to avoid copying
code. Not sure if it should look for udebs too.
Index: check-missing-firmware.sh
===
--- check-missing-firmware.sh (revision 62653)
+++ check-missing-firmware.sh (working copy)
@@ -91,7 +91,7 @@
log copying loose file $file from '$(dirname $f)' to
'$target'
mkdir -p $target
rm -f $target/$file
- cp -a $f $target || true
+ cp -aL $f $target || true
break
fi
done
@@ -150,15 +150,37 @@
if echo $1 | grep -q '\.deb$'; then
# cache deb for installation into /target later
mkdir -p /var/cache/firmware/
- cp -a $1 /var/cache/firmware/ || true
+ cp -aL $1 /var/cache/firmware/ || true
udpkg --unpack /var/cache/firmware/$(basename $1)
else
udpkg --unpack $1
fi
}
+check_for_firmware() {
+ echo $files | sed -e 's/ /\n/g' /tmp/grepfor
+ for filename in $@; do
+ if [ -f $filename ]; then
+ if check_deb_arch $filename list_deb_firmware
$filename | grep -qf /tmp/grepfor; then
+ log installing firmware package $filename
+ install_firmware_pkg $filename || true
+ fi
+ fi
+ done
+ rm -f /tmp/grepfor
+}
+
while check_missing ask_load_firmware; do
- # first, look for loose firmware files on the media.
+
+ # First, check if the firmware debs are available on the
+ # installation CD. This does not use anna because debs can
+ # have arbitrary dependencies, which anna might try to
b+ # install.
+ if [ -d /cdrom/firmware ]; then
+ check_for_firmware /cdrom/firmware/*.deb
+ fi
+
+ # second, look for loose firmware files on the media.
if mountmedia; then
for file in $files; do
try_copy $file
@@ -170,16 +192,7 @@
# This does not use anna because debs can have arbitrary
# dependencies, which anna might try to install.
if mountmedia driver; then
- echo $files | sed -e 's/ /\n/g' /tmp/grepfor
- for filename in /media/*.deb /media/*.udeb /media/*.ude
/media/firmware/*.deb /media/firmware/*.udeb /media/firmware/*.ude; do
- if [ -f $filename ]; then
- if check_deb_arch $filename
list_deb_firmware $filename | grep -qf /tmp/grepfor; then
- log installing firmware package
$filename
- install_firmware_pkg $filename || true
- fi
- fi
- done
- rm -f /tmp/grepfor
+ check_for_firmware /media/*.deb /media/*.udeb /media/*.ude
/media/firmware/*.deb /media/firmware/*.udeb /media/firmware/*.ude
umount /media || true
fi
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1nrvym-0003vv...@login1.uio.no
Re: Getting d-i to find firmware on the CD generated by debian-cd
[Holger Levsen] P.S.: should this be moved to a proper bug? Yes. Patch for hw-detect submitted in #574116. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316124952.ge4...@login1.uio.no
Re: Installer fails due to invalid signatures
reassign 573791 installation-reports tag 573791 unreproducible needinfo thanks On Tuesday 16 March 2010, steve clark wrote: I sent a report to the debian bug reporting system (bug number 573791) but it seems to not have been taken serious, being shuffled between responsible owners. I see it differently: you have an installation problem that nobody else is having and have not quite found the correct way to report it. The reason your bug report was reassigned is that the original report had an incorrect syntax. So it is *not* being shuffled around; someone was merely trying to correct your incorrect initial reporting. And please understand that reporting an issue incorrectly drastically increases the chance that it will be missed! Happens with other lives debian based systems (e.g. ubuntu 9.10 server) too. Please report issues with Ubuntu installs to Ubuntu. I'm a novice Debian user (4 months), but have over 25 years across multiple systems and am a professional developer, so think I can recognise a must look at problem when I see one :) In that case I would also expect you to recognize when a problem is so completely unlikely to escape the attention of the project publishing the software that it may well by an issue that's solely due to the inexperience of the user? I can assure you that, if Lenny really was not installable, we would be flooded with reports. Fortunately that has not happened. The fact that you consistently see the issue could also be explained by the fact that you're doing something consistently wrong maybe. !! I have just tried an install using the 5.04 netinst and using the !! ftp.uk.debian.org mirror without any problems. There may have been a temporary problem with that particular mirror. If there was it appears to be solved now. Did you try different mirrors? I would further suggest that as it prevents any new installations of Debian since at least 11th March 2010, its serverity is a little higher than normal. *If* the issue is confirmed to be a real issue *and* really affects all installations and not simply one isolated mirror, then yes. Until then a much more appropriate categorization is unreproducible, needs additional info. Now, to try to solve your problem, assuming that you can still reproduce it, we will need additional information. Please send us the syslog of a failed installation. You should be able to save it using the Save debug logs option in the main menu of the installer. Please gzip the syslog before sending it and send your reply _only_ to 573...@bugs.debian.org. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161438.13783.elen...@planet.nl
Processing of linux-kernel-di-armel-2.6_1.40_armel.changes
linux-kernel-di-armel-2.6_1.40_armel.changes uploaded successfully to localhost along with the files: linux-kernel-di-armel-2.6_1.40.dsc linux-kernel-di-armel-2.6_1.40.tar.gz kernel-image-2.6.32-3-iop32x-di_1.40_armel.udeb nic-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ide-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ide-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb loop-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nls-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext3-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext4-modules-2.6.32-3-iop32x-di_1.40_armel.udeb isofs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb jffs2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb jfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb fat-modules-2.6.32-3-iop32x-di_1.40_armel.udeb md-modules-2.6.32-3-iop32x-di_1.40_armel.udeb multipath-modules-2.6.32-3-iop32x-di_1.40_armel.udeb usb-modules-2.6.32-3-iop32x-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-iop32x-di_1.40_armel.udeb input-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-iop32x-di_1.40_armel.udeb sata-modules-2.6.32-3-iop32x-di_1.40_armel.udeb core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crc-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-iop32x-di_1.40_armel.udeb squashfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb kernel-image-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb loop-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nls-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext2-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext3-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext4-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb isofs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb jfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb fat-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb md-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb multipath-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb usb-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb input-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb sata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crc-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb squashfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb kernel-image-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb loop-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nls-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext2-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext3-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext4-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb isofs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb jfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb fat-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb minix-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb md-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb multipath-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb usb-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb input-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb sata-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb mmc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb squashfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb kernel-image-2.6.32-3-orion5x-di_1.40_armel.udeb nic-modules-2.6.32-3-orion5x-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-orion5x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb loop-modules-2.6.32-3-orion5x-di_1.40_armel.udeb nls-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb
Processing of flash-kernel_2.28_armel.changes
flash-kernel_2.28_armel.changes uploaded successfully to localhost along with the files: flash-kernel_2.28.dsc flash-kernel_2.28.tar.gz flash-kernel_2.28_armel.deb flash-kernel-installer_2.28_armel.udeb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nrzvl-0004qt...@ries.debian.org
Processed (with 1 errors): reassign
Processing commands for cont...@bugs.debian.org: reassign 573791 installation-reports Bug #573791 [cdimage.debian.org] apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11 Bug reassigned from package 'cdimage.debian.org' to 'installation-reports'. tag 573791 unreproducible needinfo Unknown tag/s: needinfo. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore. Bug #573791 [installation-reports] apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11 Added tag(s) unreproducible. 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 Archive: http://lists.debian.org/handler.s.c.126875651120016.transcr...@bugs.debian.org
flash-kernel_2.28_armel.changes ACCEPTED
Accepted: flash-kernel-installer_2.28_armel.udeb to main/f/flash-kernel/flash-kernel-installer_2.28_armel.udeb flash-kernel_2.28.dsc to main/f/flash-kernel/flash-kernel_2.28.dsc flash-kernel_2.28.tar.gz to main/f/flash-kernel/flash-kernel_2.28.tar.gz flash-kernel_2.28_armel.deb to main/f/flash-kernel/flash-kernel_2.28_armel.deb Override entries for your package: flash-kernel-installer_2.28_armel.udeb - standard debian-installer flash-kernel_2.28.dsc - source utils flash-kernel_2.28_armel.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nrzge-0006eo...@ries.debian.org
linux-kernel-di-armel-2.6_1.40_armel.changes REJECTED
Reject Reasons: Unknown distribution `unstablle'. linux-kernel-di-armel-2.6_1.40.dsc: source format '1.0' not allowed in unstablle (accepted: ) === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nrzhu-0006oj...@ries.debian.org
Processed: reassign
Processing commands for cont...@bugs.debian.org: tag 573791 moreinfo Bug #573791 [installation-reports] apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11 Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126875765528192.transcr...@bugs.debian.org
Bug#573791: apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11
Please note this log is taken just now using: debian 5.04 netinst business card image I have just tried with the same image (for i386), using ftp.nl.d.o as mirror without any problems. My log looks similar to you, except that I get good signatures... From my log: Mar 16 17:41:08 choose-mirror[6970]: INFO: suite/codename set to: stable/lenny [...] Mar 16 16:42:18 main-menu[1044]: INFO: Menu item 'bootstrap-base' selected Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Signature made Fri Jan 29 23:18:35 2010 UTC using RSA key ID 55BE302B Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Good signature from Debian Archive Automatic Signing Key (5.0/lenny) ftpmas...@debian.org Mar 16 16:42:21 debootstrap: Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Signature made Fri Jan 29 23:25:01 2010 UTC using DSA key ID F42584E6 Mar 16 16:42:21 debootstrap: gpgv: Mar 16 16:42:21 debootstrap: Good signature from Lenny Stable Release Key debian-rele...@lists.debian.org I wonder if somehow the files are getting corrupted during download. Can you copy the following two files from the installer after a debootstrap failure and send them: /target/var/lib/apt/lists/debootstrap.invalid_dists_lenny_Release /target/var/lib/apt/lists/debootstrap.invalid_dists_lenny_Release.gpg The first one should be zipped again. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003161756.37536.elen...@planet.nl
Processing of linux-kernel-di-armel-2.6_1.40_armel.changes
linux-kernel-di-armel-2.6_1.40_armel.changes uploaded successfully to localhost along with the files: linux-kernel-di-armel-2.6_1.40.dsc linux-kernel-di-armel-2.6_1.40.tar.gz kernel-image-2.6.32-3-iop32x-di_1.40_armel.udeb nic-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ide-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ide-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb loop-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nls-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext3-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext4-modules-2.6.32-3-iop32x-di_1.40_armel.udeb isofs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb jffs2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb jfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb fat-modules-2.6.32-3-iop32x-di_1.40_armel.udeb md-modules-2.6.32-3-iop32x-di_1.40_armel.udeb multipath-modules-2.6.32-3-iop32x-di_1.40_armel.udeb usb-modules-2.6.32-3-iop32x-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-iop32x-di_1.40_armel.udeb input-modules-2.6.32-3-iop32x-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-iop32x-di_1.40_armel.udeb sata-modules-2.6.32-3-iop32x-di_1.40_armel.udeb core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crc-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-iop32x-di_1.40_armel.udeb squashfs-modules-2.6.32-3-iop32x-di_1.40_armel.udeb kernel-image-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb loop-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nls-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext2-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext3-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext4-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb isofs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb jfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb fat-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb md-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb multipath-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb usb-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb input-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb sata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crc-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb squashfs-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb kernel-image-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb loop-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nls-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext2-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext3-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext4-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb isofs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb jfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb reiserfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb fat-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb minix-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb md-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb multipath-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb usb-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb usb-storage-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb input-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb nic-usb-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb sata-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb mmc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb squashfs-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb kernel-image-2.6.32-3-orion5x-di_1.40_armel.udeb nic-modules-2.6.32-3-orion5x-di_1.40_armel.udeb nic-shared-modules-2.6.32-3-orion5x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb scsi-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb loop-modules-2.6.32-3-orion5x-di_1.40_armel.udeb nls-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb
linux-kernel-di-armel-2.6_1.40_armel.changes is NEW
(new) ata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb extra debian-installer ATA disk modules This package contains core ATA disk modules used by both PATA and SATA disk drivers. (new) cdrom-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb standard debian-installer CDROM support This package contains core CDROM support for the kernel. (new) cdrom-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb standard debian-installer CDROM support This package contains core CDROM support for the kernel. (new) cdrom-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb standard debian-installer CDROM support This package contains core CDROM support for the kernel. (new) cdrom-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb standard debian-installer CDROM support This package contains core CDROM support for the kernel. (new) cdrom-core-modules-2.6.32-3-versatile-di_1.40_armel.udeb standard debian-installer CDROM support This package contains core CDROM support for the kernel. (new) core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb standard debian-installer Core modules This package contains core modules for the kernel, that will almost always be needed. (new) core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb standard debian-installer Core modules This package contains core modules for the kernel, that will almost always be needed. (new) core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb standard debian-installer Core modules This package contains core modules for the kernel, that will almost always be needed. (new) core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb standard debian-installer Core modules This package contains core modules for the kernel, that will almost always be needed. (new) core-modules-2.6.32-3-versatile-di_1.40_armel.udeb standard debian-installer Core modules This package contains core modules for the kernel, that will almost always be needed. (new) crc-modules-2.6.32-3-iop32x-di_1.40_armel.udeb extra debian-installer CRC modules This package contains CRC support modules. (new) crc-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb extra debian-installer CRC modules This package contains CRC support modules. (new) crc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb extra debian-installer CRC modules This package contains CRC support modules. (new) crc-modules-2.6.32-3-orion5x-di_1.40_armel.udeb extra debian-installer CRC modules This package contains CRC support modules. (new) crc-modules-2.6.32-3-versatile-di_1.40_armel.udeb extra debian-installer CRC modules This package contains CRC support modules. (new) crypto-dm-modules-2.6.32-3-iop32x-di_1.40_armel.udeb extra debian-installer devicemapper crypto module This package contains the devicemapper crypto (dm-crypt) module. (new) crypto-dm-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb extra debian-installer devicemapper crypto module This package contains the devicemapper crypto (dm-crypt) module. (new) crypto-dm-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb extra debian-installer devicemapper crypto module This package contains the devicemapper crypto (dm-crypt) module. (new) crypto-dm-modules-2.6.32-3-orion5x-di_1.40_armel.udeb extra debian-installer devicemapper crypto module This package contains the devicemapper crypto (dm-crypt) module. (new) crypto-dm-modules-2.6.32-3-versatile-di_1.40_armel.udeb extra debian-installer devicemapper crypto module This package contains the devicemapper crypto (dm-crypt) module. (new) crypto-modules-2.6.32-3-iop32x-di_1.40_armel.udeb extra debian-installer crypto modules This package contains crypto modules. (new) crypto-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb extra debian-installer crypto modules This package contains crypto modules. (new) crypto-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb extra debian-installer crypto modules This package contains crypto modules. (new) crypto-modules-2.6.32-3-orion5x-di_1.40_armel.udeb extra debian-installer crypto modules This package contains crypto modules. (new) crypto-modules-2.6.32-3-versatile-di_1.40_armel.udeb extra debian-installer crypto modules This package contains crypto modules. (new) ext2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb standard debian-installer EXT2 filesystem support This package contains the EXT2 filesystem module for the kernel. (new) ext2-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb standard debian-installer EXT2 filesystem support This package contains the EXT2 filesystem module for the kernel. (new) ext2-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb standard debian-installer EXT2 filesystem support This package contains the EXT2 filesystem module for the kernel. (new) ext2-modules-2.6.32-3-orion5x-di_1.40_armel.udeb standard debian-installer EXT2 filesystem support This package contains the EXT2 filesystem module for the kernel. (new) ext2-modules-2.6.32-3-versatile-di_1.40_armel.udeb standard debian-installer EXT2 filesystem support This package contains the EXT2 filesystem module for the kernel. (new)
Re: Getting d-i to find firmware on the CD generated by debian-cd
Frans Pop wrote: IMO a proper solution would ensure the licence dialog gets displayed before the firmware first gets loaded by the installer. The only relevant firmware package I can find that prompts with a license is firmware-ipw2x00. This was discussed in #504668 when they added the license prompt to the package: | Note: If one gets the firmware-ipw2100 packages, then copy it on a usb | key to provide the package to Debian-Installer (when DI detects the Wifi | card), then the preinst script isn't displayed. | | Which means that the license isn't accepted. This behaviour shouldn't | be a problem for ipw2100/ipw2200, since the license's FAQ handle this | case (see Bug #504671 and 449235) I don't know if #449235's conclusions about this are right. Though the FAQ can be read that way, it's just a FAQ, not a legal document. But it's worth considering before going too far down the rabbit hole of creating a way for d-i to display the license earlier than it does now. -- see shy jo signature.asc Description: Digital signature
Re: Getting d-i to find firmware on the CD generated by debian-cd
Frans Pop wrote: On Tuesday 16 March 2010, Holger Levsen wrote: On Dienstag, 16. März 2010, Frans Pop wrote: An additional issue with non-free firmware is that including it in the way you propose would (I think) mean it will get loaded without any prompting of the user, which may in some cases violate licence terms. i thought the same at first, but actually that's not the case. The user is still asked (by the package) if she wants to accept the licence. (As no preseeding takes place.) But that's only at the point where the package gets installed in the target system. And at that point the firmware is already in use. I checked, and the assumption that the firmware deb's debconf prompt is displayed seems to be untrue: hw-detect.post-base-installer.d/50install-firmware: for deb in /var/cache/firmware/*.deb; do if [ -f $deb ]; then cp -a $deb /target/tmp # TODO debconf passthrough if ! in-target dpkg -i /tmp/$(basename $deb); then # dpkg failed, force removal of package in-target dpkg --force-depends --remove $(deb_package $deb) || true fi in-target does not provide debconf passthrough, and apt-install cannot be used here. To use debconf passthrough here would require ripping the passthrough setup code out of debconf-apt-progress, It might be more expedient to make a pkgsel hook that uses apt-install to re-download and install the firmware debs. -- see shy jo signature.asc Description: Digital signature
Bug#574116: hw-detect: Should look for firmware packages on CD and DVD too
Petter Reinholdtsen wrote: The non-free section of the mirror will not be enabled automatically, so any updates to the firmware will not be installed automatically. While not relevant to this bug report(?), that is incorrect. See apt-setup preseeding done by hw-detect.post-base-installer.d/50install-firmware -- see shy jo signature.asc Description: Digital signature
Bug#568475: keyboard-configuration: Please use pc104 for *_PL.
Anton Zinoviev an...@lml.bas.bg: On Fri, Feb 05, 2010 at 02:19:24AM +0100, Piotr Engelking wrote: As of version 1.51, keyboard-configuration uses pc105 as the default keyboard model for *_PL locales. Please use pc104 instead, as this the keyboard that is normally used in Poland. True, but pc104 works only for people having a pc104 keyboard while pc105 works for both. Currently, keyboard-configuration defaults to pc104 for the Brazilian and US layouts. Shouldn't they perhaps be changed to pc105 as well, in the light of the above? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/814371d61003161206n161ec88fnafeff03e6e55b...@mail.gmail.com
Bug#568638: 'dpkg-reconfigure keyboard-configuration' takes no immediate effect
reopen 568638 severity 568638 wishlist thanks Anton Zinoviev an...@lml.bas.bg: On Sat, Feb 06, 2010 at 01:32:27PM +0100, Piotr Engelking wrote: Using 'dpkg-reconfigure keyboard-configuration' to switch the keyboard layout to French takes no effect, neither in console nor in X, until '/etc/init.d/console-setup reload' is run. This is because the only purpose of keyboard-configuration is to create a configuration file in /etc/default/keyboard. It doesn't configure the keyboard in any way. This is rather confusing, as other Debian packages tend to take their reconfiguration into effect immediately. Please consider at least printing an informative message after the reconfiguration what should the user do for the layout to actually change. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/814371d61003161207r5d11c186wc17c12672bbe...@mail.gmail.com
Bug#574158: firmware licenses never displayed
Package: hw-detect Severity: important firmware-ipw2100 has a license prompt that is supposed to be displayed to the user. If this firmware is loaded by d-i from media supplied by the user, this prompt is never actually displayed. In #504668, it's claimed that the license's FAQ allows this, which is the only reason I have not made this bug serious, yet. Conversely, in #449235, decisions seem to be made assuming that d-i will display the firmware prompt. I see three approaches to fixing this bug: 1. Change the post-base-installer hook to not install firmware debs with dpkg -i. It needs to use apt for debconf frontend proxying to work. One approach might be to move this to a pkgsel hook, and use the already available firmware debs to prepopulate /var/cache/apt/archives, so they don't have to be downloaded again. Only problem with this approach is it fails if the user, in apt-setup, chooses not to use non-free, or even chooses to install without a network mirror. In this case, the installed system might end up without firmware needed to boot. 2. Rip the debconf frontend proxy setup code out of debconf-apt-progress, and adapt so it can be used with dpkg -i. Or hack debconf-apt-progress to support running dpkg -i. 3. Provide some way for firmware debs to communicate to d-i that they have a license the user needs to see, and have check-missing-firmware display these licenses before the firmware is ever used. This is probably the most general approach, as it will allow us to support firmware where it's a hard requirement that the user sees the license. (Which may already be the case, depending on which lawyers you ask?) One way would be to add a header to the firmware deb: License-Agreement: /usr/share/doc/firmware-ipw2x00/copyright -- see shy jo signature.asc Description: Digital signature
linux-kernel-di-armel-2.6_1.40_armel.changes ACCEPTED
Accepted: ata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ata-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/cdrom-core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/cdrom-core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/cdrom-core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/cdrom-core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb cdrom-core-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/cdrom-core-modules-2.6.32-3-versatile-di_1.40_armel.udeb core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/core-modules-2.6.32-3-iop32x-di_1.40_armel.udeb core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/core-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/core-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/core-modules-2.6.32-3-orion5x-di_1.40_armel.udeb core-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/core-modules-2.6.32-3-versatile-di_1.40_armel.udeb crc-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crc-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crc-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crc-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crc-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crc-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crc-modules-2.6.32-3-orion5x-di_1.40_armel.udeb crc-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crc-modules-2.6.32-3-versatile-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-dm-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-dm-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-dm-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-dm-modules-2.6.32-3-orion5x-di_1.40_armel.udeb crypto-dm-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-dm-modules-2.6.32-3-versatile-di_1.40_armel.udeb crypto-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-modules-2.6.32-3-iop32x-di_1.40_armel.udeb crypto-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb crypto-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb crypto-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-modules-2.6.32-3-orion5x-di_1.40_armel.udeb crypto-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/crypto-modules-2.6.32-3-versatile-di_1.40_armel.udeb ext2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext2-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext2-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext2-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext2-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext2-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext2-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext2-modules-2.6.32-3-orion5x-di_1.40_armel.udeb ext2-modules-2.6.32-3-versatile-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext2-modules-2.6.32-3-versatile-di_1.40_armel.udeb ext3-modules-2.6.32-3-iop32x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext3-modules-2.6.32-3-iop32x-di_1.40_armel.udeb ext3-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext3-modules-2.6.32-3-ixp4xx-di_1.40_armel.udeb ext3-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext3-modules-2.6.32-3-kirkwood-di_1.40_armel.udeb ext3-modules-2.6.32-3-orion5x-di_1.40_armel.udeb to main/l/linux-kernel-di-armel-2.6/ext3-modules-2.6.32-3-orion5x-di_1.40_armel.udeb ext3-modules-2.6.32-3-versatile-di_1.40_armel.udeb to
Processed: reopen 568638
Processing commands for cont...@bugs.debian.org:
reopen 568638
Bug #568638 {Done: Anton Zinoviev an...@lml.bas.bg} [keyboard-configuration]
'dpkg-reconfigure keyboard-configuration' takes no immediate effect
severity 568638 wishlist
Bug #568638 [keyboard-configuration] 'dpkg-reconfigure keyboard-configuration'
takes no immediate effect
Severity set to 'wishlist' from 'normal'
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
Archive:
http://lists.debian.org/handler.s.c.126876874514292.transcr...@bugs.debian.org
Bug#574158: firmware licenses never displayed
On Tuesday 16 March 2010, Joey Hess wrote: 3. Provide some way for firmware debs to communicate to d-i that they have a license the user needs to see, and have check-missing-firmware display these licenses before the firmware is ever used. This is the option that I have had in the back of my mind for some time. I think for really structural support of firmware, we could repackage it like we do for kernel modules and include meta data (partially? automatically generated) about the deb something was taken from + licence requirements. That would also allow to e.g. skip old versions of firmware. My personal opinion is that it should actually be quite OK to include non-free firmware *udebs* on (CD) images as long as - the licence in no way limits distribution; - we never allow use of any non-free firmware without explicit ack by the user. The *debs* should IMO always be either downloaded from a mirror (using standard apt-install) with fallback support for installing them from an external medium. Under those conditions I think the project might be persuaded to accept inclusion of firmware in D-I images and on CDs. We should of course keep support for loading firmware that does not match these criteria from external media. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162108.20985.elen...@planet.nl
Bug#243857: Patch has been available in Ubuntu
tags 243857 + patch thanks Hey, Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch This code is in their current version of cdrom-detect and seems to work well in the exact same situation that d-i fails. Can we get this patch backported? I can do a NMU if there is no real maintainer willing to step up. Thanks! -- Joshua Kwan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316202304.ga10...@triplehelix.org
Processed: Patch has been available in Ubuntu
Processing commands for cont...@bugs.debian.org: tags 243857 + patch Bug #243857 [cdrom-detect] problem with 2 cds if one is not a d-i cd Bug #268950 [cdrom-detect] booting of cd for installation fails to mount with a DVD in another drive. Added tag(s) patch. Added tag(s) patch. 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 Archive: http://lists.debian.org/handler.s.c.126877138111966.transcr...@bugs.debian.org
Processed: Re: Bug#568475: keyboard-configuration: Please use pc104 for *_PL.
Processing commands for cont...@bugs.debian.org:
reopen 568475
Bug #568475 {Done: Anton Zinoviev an...@lml.bas.bg} [keyboard-configuration]
keyboard-configuration: Please use pc104 for *_PL.
retitle 568475 No need to use pc104 for Brazilian and US layouts
Bug #568475 [keyboard-configuration] keyboard-configuration: Please use pc104
for *_PL.
Changed Bug title to 'No need to use pc104 for Brazilian and US layouts' from
'keyboard-configuration: Please use pc104 for *_PL.'
thank you
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
Archive:
http://lists.debian.org/handler.s.c.126877177015813.transcr...@bugs.debian.org
Bug#568475: keyboard-configuration: Please use pc104 for *_PL.
reopen 568475 retitle 568475 No need to use pc104 for Brazilian and US layouts thank you On Tue, Mar 16, 2010 at 08:06:26PM +0100, Piotr Engelking wrote: Currently, keyboard-configuration defaults to pc104 for the Brazilian and US layouts. Shouldn't they perhaps be changed to pc105 as well, in the light of the above? Yes. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316203557.ga8...@debian.lan
Processed: Re: Bug#568638: 'dpkg-reconfigure keyboard-configuration' takes no immediate effect
Processing commands for cont...@bugs.debian.org: close 568638 Bug#568638: 'dpkg-reconfigure keyboard-configuration' takes no immediate effect 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Piotr Engelking inkerma...@gmail.com thank you 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 Archive: http://lists.debian.org/handler.s.c.126877321230677.transcr...@bugs.debian.org
Bug#568638: 'dpkg-reconfigure keyboard-configuration' takes no immediate effect
close 568638 thank you On Tue, Mar 16, 2010 at 08:07:02PM +0100, Piotr Engelking wrote: This is because the only purpose of keyboard-configuration is to create a configuration file in /etc/default/keyboard. It doesn't configure the keyboard in any way. This is rather confusing, as other Debian packages tend to take their reconfiguration into effect immediately. The only purpose of keyboard-configuration is to create /etc/default/keyboard and after dpkg-reconfigure the package only updates this file. It is not the purpose of keyboard-configuration to change the state of the keyboard in any way. It is difficult for keyboard-configuration to tell how many packages of Debian are using /etc/default/keyboard and what command is required in order to enforce the changes in this file. The current Debian policy does not permit the use of 'Note' Debconf-template in order to present the user with unimportant messages because they tend to become annoying. If console-setup is installed then the required information to setup the console is in /usr/share/doc/console-setup/README.gz. I don't know what is the proper method to update the keyboard in X or in BSD or in Hurd. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100316205958.gb8...@debian.lan
Problem with local repository
Hello, I'm trying to install Debian using the NetInst CD and a local repository created using the apt-mirror app. The installation with the local repository make the downloads of the first part well. But in the second part, when it need 5 files, it requires the internet. Anybody knows what could be happen? Thanks. -- Hugo Alberto Perlin
Processed: Re: Bug#243857: Patch has been available in Ubuntu
Processing commands for cont...@bugs.debian.org: tags 243857 + pending Bug #243857 [cdrom-detect] problem with 2 cds if one is not a d-i cd Bug #268950 [cdrom-detect] booting of cd for installation fails to mount with a DVD in another drive. Added tag(s) pending. Added tag(s) 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 debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126877650430214.transcr...@bugs.debian.org
Bug#243857: Patch has been available in Ubuntu
tags 243857 + pending thanks On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. This code is in their current version of cdrom-detect and seems to work well in the exact same situation that d-i fails. Can we get this patch backported? Part of the patch is already in our code. I've ported the rest and done some additional refactoring. Will commit after testing in the next few days. I can do a NMU if there is no real maintainer willing to step up. An NMU (upload not from the D-I SVN repo) is never really a solution in the case of D-I as it tends to increase rather than reduce the work for maintainers. In general NMUs should not be needed where packages are maintained by a generally active team. It also seems not indicated in this case as this is the first time a patch has been suggested for the issue. Providing (preferably tested) patches against current SVN helps maintainers a lot more and is very much appreciated. Pinging maintainers on bug reports is also always appreciated. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162255.02123.elen...@planet.nl
Re: Problem with local repository
On Tuesday 16 March 2010, Hugo Alberto Perlin wrote: I'm trying to install Debian using the NetInst CD and a local repository created using the apt-mirror app. The installation with the local repository make the downloads of the first part well. But in the second part, when it need 5 files, it requires the internet. Anybody knows what could be happen? What exactly do you mean by first part and second part? Are you sure that the packages in your local repository have a higher package version than the ones available on the mirror (including security updates!)? Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162302.42767.elen...@planet.nl
Bug#243857: Patch has been available in Ubuntu
Hi Joshua, On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. I can do a NMU if there is no real maintainer willing to step up. An NMU is not required (and does not really reduce the work of maintainers anyway). But a proper patch, preferably tested, that applies to the current version of the source package and that does not log messages saying Ubuntu would be most welcome. I would suggest changing the message to ... is not a valid installation CD (especially as it does not actually test if it is a Debian or Ubuntu CD; if you'd happen to have a Debian CD in one drive and an Ubuntu CD in the other, it would accept either...). Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162259.58474.elen...@planet.nl
Bug#243857: Patch has been available in Ubuntu
On Tuesday 16 March 2010, Frans Pop wrote: On Tuesday 16 March 2010, Joshua Kwan wrote: Looks like this bug hasn't seen action for quite a while. It seems like in the meantime, Ubuntu has fixed this bug. Check out this patch: http://launchpadlibrarian.net/18656164/cdrom-detect-better-flow.patch Thanks for the pointer. I can do a NMU if there is no real maintainer willing to step up. An NMU is not required (and does not really reduce the work of maintainers anyway). But a proper patch, preferably tested, that applies to the current version of the source package and that does not log messages saying Ubuntu would be most welcome. I would suggest changing the message to ... is not a valid installation CD (especially as it does not actually test if it is a Debian or Ubuntu CD; if you'd happen to have a Debian CD in one drive and an Ubuntu CD in the other, it would accept either...). Please ignore this mail. Apparently I had two versions open and by mistake also sent this early draft. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162325.05500.elen...@planet.nl
Fwd: Problem with local repository
On Tue, Mar 16, 2010 at 7:02 PM, Frans Pop elen...@planet.nl wrote: On Tuesday 16 March 2010, Hugo Alberto Perlin wrote: I'm trying to install Debian using the NetInst CD and a local repository created using the apt-mirror app. The installation with the local repository make the downloads of the first part well. But in the second part, when it need 5 files, it requires the internet. Anybody knows what could be happen? What exactly do you mean by first part and second part? The first part I mean the part before select what kind of installation, like Desktop, Data Base Server, Web Server... The second part is after that. Are you sure that the packages in your local repository have a higher package version than the ones available on the mirror (including security updates!)? Yes, the repository is sincronized every day with the debian mirror. The mirror.list is: deb http://ftp.br.debian.org/debian lenny main contrib non-free deb-src http://ftp.br.debian.org/debian lenny main contrib non-free deb http://ftp.br.debian.org/debian lenny main/debian-installer deb http://security.debian.org/ lenny/updates main contrib non-free deb-src http://security.debian.org/ lenny/updates main contrib non-free Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003162302.42767.elen...@planet.nl Thanks for the reply. -- Hugo Alberto Perlin
[D-I Manual] Build log for en (16 Mar 2010)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/appendix/preseed.xml
Updated to revision 62665.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100317001742.ga6...@mustang.funlabs.org
Bug#573791: apt-get update in Debian 5.04 (lenny) failing since updates of 2010-03-11
It is now working correctly via both ISPs here; no changes to any hardware/software/settings. Ah well, I'm sure there's an explanation to be found somewhere. Thanks for your time Frans, Steve -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/001201cac56c$f02b7480$6416a...@reallyweevil
Towards X11-based d-i: Gone through NEW
Hi, during the past days, I've been busy getting my changes merged into Debian packages, getting them uploaded, and getting them through NEW. Besides the X11-related packages I took care of, I should list udev, cairo, pango1.0, gtk+2.0, vte, and gtk2-engines. Their respective maintainers were very quick at merging them, and ftp folks VERY quick at accepting the several rounds of packages including new udebs. Current situation: == * udev is ready in unstable. * X11 packages (server, drivers, libraries) are ready in unstable. * cairo, pango1.0, gtk+2.0, vte, gtk2-engines are ready in experimental [gnome 2.30 rc packages]. * cairo is additionally ready in unstable [gnome 2.28 packages]. Right now, I spotted a few issues: * Missing version bump in Build-Depends, resulting in a dependency of libpango1.0-udeb → libcairo-directfb2-udeb. Should be trivial to fix. * An extra dependency in experimental: libcairo2-udeb → libstdc++6. At first, I thought “the latter seems to be the result of the addition of a qt backend in the latest cairo packages (only in experimental, the unstable udeb is OK). It should be easy to disable the qt part through a configure option for the udeb though.” But we even have: | dpkg-shlibdeps: warning: dependency on libstdc++.so.6 could be avoided if debian/libcairo2/usr/lib/libcairo.so.2.10906.0 were not uselessly linked against it (they use none of its symbols). Due to those issues, I couldn't build a netboot-gtk image to double-check that modified d-i packages (see below) were leading to a working image again. Proposed plan: == (1) In order to get everyone ready, I'd suggest (kindly) asking pkg-gnome folks to upload their 2.28 packages to unstable; so that the remaining packages can be rebuilt against them. I think it'd be nice not to wait and get entangled in the gnome 2.30 transition, that's why I'd like to go with the 2.28 ones (which were working fine for me). It'd be nice to make sure there's no directfb stuff left in Depends, before it gets uploaded. ;) (2) Once that done, I'll rebuild the following d-i packages against them: * cdebconf * cdebconf-entropy * cdebconf-terminal * rootskel-gtk (I'm going to file bugs against them in a few minutes anyway.) (3) If the resulting image boots fine, I'll be reporting here, and asking for those patches to be merged. If there are issues, I'll file bugs to fix those, and then report here, asking for those patches to be merged. (4) If everything goes alright at this point, I think we should be able to migrate the whole set of packages to testing, so that further updates only require to migrate a few packages at a time. Comments etc. welcome, as usual. Mraw, KiBi. signature.asc Description: Digital signature
