Last 2 commits in cdrom-checker
Hi Colin,
Do you target wheezy for the last 2 commits your made in cdrom
-checker?
I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a
good idea.I have however no idea for
1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-)
commit 1ec13c5a378076c10988237972d4df0f1eefafd3
Author: Colin Watson
Date: Wed Jan 9 12:11:09 2013 +
Mark argc parameter to main as unused.
diff --git a/debian/changelog b/debian/changelog
index 29db03b..14fdbfa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
cdrom-checker (1.24) UNRELEASED; urgency=low
* Fix "LDLFAGS" typo in Makefile.
+ * Mark argc parameter to main as unused.
-- Colin Watson Wed, 09 Jan 2013 12:05:27 +
diff --git a/main.c b/main.c
index a1b1b80..4a1409f 100644
--- a/main.c
+++ b/main.c
@@ -159,7 +159,7 @@ int check_cdrom() {
return(status);
}
-int main(int argc, char **argv) {
+int main(int argc __attribute__ ((unused)), char **argv) {
di_system_init(basename(argv[0]));
/* initialize the debconf frontend */
debconf = debconfclient_new();
commit e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0
Author: Colin Watson
Date: Wed Jan 9 12:05:52 2013 +
Fix "LDLFAGS" typo in Makefile.
diff --git a/Makefile b/Makefile
index 05232a2..47bf892 100644
--- a/Makefile
+++ b/Makefile
@@ -20,7 +20,7 @@
CC = gcc
CFLAGS = -W -Wall -Os -fomit-frame-pointer
LD = gcc
-LDLFAGS =
+LDFLAGS =
LDLIBS = -ldebconfclient -ldebian-installer
APP = cdrom-checker
diff --git a/debian/changelog b/debian/changelog
index edc9806..29db03b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cdrom-checker (1.24) UNRELEASED; urgency=low
+
+ * Fix "LDLFAGS" typo in Makefile.
+
+ -- Colin Watson Wed, 09 Jan 2013 12:05:27 +
+
cdrom-checker (1.23) unstable; urgency=low
[ Updated translations ]
--
signature.asc
Description: Digital signature
Bug#697905: persistent naming in crypttab
Package: partman-crypto Version: 56 Hi, I think that using udev persistent device naming in /etc/crypttab would be useful to prevent some dangerous situation, like the following one. I have a 3 disks setup with the first two in raid mode and the third as archive. The swap partitions are encrypted with dm-crypt and out of the raid. After the install /etc/crypttab contains: sda1_crypt /dev/sda1 /dev/urandom cipher=aes-xts-plain64,size=256,swap sdb1_crypt /dev/sdb1 /dev/urandom cipher=aes-xts-plain64,size=256,swap When the first or the second disk fails or begin removed, sdc is renamed sdb and the first partition (that unlucky was not a swap partition) is overwritten. The recover of the filesystem was not automatic and required to rewrite with zeros all the sectors overwritten by encrypted data, as explained by that mail message: https://www.redhat.com/archives/ext3-users/2011-January/msg00010.html As dm-crypt without luks do not supports UUIDs, udev persistent naming should prevent this situation in a safe manner, mapping the device and doing mkswap or mkfs only if the partition is exactly on the disk selected by the installer. In other cases it fails, that is safer than doing mkswap on random partitions. I have attached an untested patch to partman-crypto that should address this issue. As this is my first look of debian installer sources, this patch is not intended to be applied as is, but as a detailed explanation of the fix. The /etc/crypttab would be: sda1_crypt /dev/disk/by-id/scsi-NAME-SERIAL-part1 /dev/urandom ... This bug affects both squeeze and wheezy. Ciao--- partman-crypto-56/finish.d/crypto_config 2011-01-19 05:58:49.0 +0100 +++ partman-crypto-56-udevid/finish.d/crypto_config 2013-01-11 08:35:13.408173693 +0100 @@ -124,6 +124,9 @@ if cryptsetup isLuks "$source"; then local uuid=$(cryptsetup luksUUID "$source") source="UUID=$uuid" + else + # Use udev persistent device naming + source=$(find /dev/disk/by-id -lname "*/$(basename $source)" | tail -1) fi # Add entry to crypttab
Re: Last 2 commits in cdrom-checker
Christian PERRIER, le Fri 11 Jan 2013 07:12:49 +0100, a écrit : > Hi Colin, > > Do you target wheezy for the last 2 commits your made in cdrom > -checker? > > I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a > good idea.I have however no idea for > 1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-) It's completely harmless. Samuel -- 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/20130111095420.ga7...@type.bordeaux.inria.fr
Bug#697905: persistent naming in crypttab
Please unsubscribe.. Thank you. On Fri, Jan 11, 2013 at 2:49 PM, Trek wrote: > Package: partman-crypto > Version: 56 > > Hi, > > I think that using udev persistent device naming in /etc/crypttab > would be useful to prevent some dangerous situation, like the > following one. > > I have a 3 disks setup with the first two in raid mode and the third as > archive. The swap partitions are encrypted with dm-crypt and out of the > raid. After the install /etc/crypttab contains: > > sda1_crypt /dev/sda1 /dev/urandom cipher=aes-xts-plain64,size=256,swap > sdb1_crypt /dev/sdb1 /dev/urandom cipher=aes-xts-plain64,size=256,swap > > When the first or the second disk fails or begin removed, sdc is renamed > sdb and the first partition (that unlucky was not a swap partition) is > overwritten. The recover of the filesystem was not automatic and > required to rewrite with zeros all the sectors overwritten by encrypted > data, as explained by that mail message: > > https://www.redhat.com/archives/ext3-users/2011-January/msg00010.html > > > As dm-crypt without luks do not supports UUIDs, udev persistent naming > should prevent this situation in a safe manner, mapping the device and > doing mkswap or mkfs only if the partition is exactly on the disk > selected by the installer. In other cases it fails, that is safer than > doing mkswap on random partitions. > > I have attached an untested patch to partman-crypto that should address > this issue. As this is my first look of debian installer sources, this > patch is not intended to be applied as is, but as a detailed > explanation of the fix. The /etc/crypttab would be: > > sda1_crypt /dev/disk/by-id/scsi-NAME-SERIAL-part1 /dev/urandom ... > > > This bug affects both squeeze and wheezy. > > Ciao
Bug#697839: discover-data: usb 04b4:fd1[0123] is package sispmctl
[Helmut Grohne] > Package: discover-data > Version: 2.2013.01.09 > Severity: wishlist > > Petter Reinholdtsen called for updates to discover-data on planet.d.o. > So I can provide some IDs as well. Great. :) > The sispmctl package is used to switch a power socket. The current > version of the package detects the following USB ids as supported: > > 04B4:FD10 > 04B4:FD11 > 04B4:FD12 > 04B4:FD13 > > Could you add these devices to discover-data? Do you need more > information? It is enough information for discover-data, but the device information is missing from the USB ID list. I had a look in usb-device.xml, and these IDs are not assigned any information. Can you please visit http://www.linux-usb.org/> and add the required information for these USB devices there? We use http://www.linux-usb.org/usb.ids> as the source for USB device information. I'll add some dummy entries for now, but for this to work properly you should get it included in the official list. If you maintain a hardware related package yourself, you could also add a XB-Modaliases entry in debian/control to get my prototype to handle the hardware mapping correctly. I believe this also has the advantage of working with Jockey on Ubuntu too. :) -- 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/2fly5g0kozg@login1.uio.no
Re: Last 2 commits in cdrom-checker
On Fri, Jan 11, 2013 at 07:12:49AM +0100, Christian PERRIER wrote: > Do you target wheezy for the last 2 commits your made in cdrom > -checker? There's no pressing urgency to have them in wheezy, but they're also entirely harmless and can ride along with translation updates or whatever without causing any problems. If there are no more uploads of cdrom-checker before wheezy, then they can just stay on master and be uploaded later. > I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a > good idea.I have however no idea for > 1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-) It made the jenkins build stable and was non-intrusive enough that I didn't think it was necessary to put it on a jessie branch. -- Colin Watson [cjwat...@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/2013001916.gn21...@riva.dynamic.greenend.org.uk
Re: Adding preseeding and firmware to wheezy iso netinst
hi, I'm still lacking a bit behind. My image now boots as CD-ROM Legacy and CR-ROM EFI but not as USB EFI (which works with vanillia netinst b4). Here is my xorriso: xorriso -as mkisofs -r -J -joliet-long -l -cache-inodes \ -isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin -partition_offset 16 \ -v -A "$SHORT_NAME" -p "$LONG_NAME" -V "$SHORT_NAME" \ -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot --efi-boot boot/grub/efi.img \ -o debian-$DEBIAN_ISO_VERSION-netinst-nantes.iso cd -- Mathieu Parent -- 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/cafx5sbx_q7mpza5yx+rtboaxd4oi0b6tvupqm1mu+fym4o3...@mail.gmail.com
Bug#697839: marked as done (discover-data: usb 04b4:fd1[0123] is package sispmctl)
Your message dated Fri, 11 Jan 2013 10:32:34 + with message-id and subject line Bug#697839: fixed in discover-data 2.2013.01.11 has caused the Debian Bug report #697839, regarding discover-data: usb 04b4:fd1[0123] is package sispmctl 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: discover-data Version: 2.2013.01.09 Severity: wishlist Petter Reinholdtsen called for updates to discover-data on planet.d.o. So I can provide some IDs as well. The sispmctl package is used to switch a power socket. The current version of the package detects the following USB ids as supported: 04B4:FD10 04B4:FD11 04B4:FD12 04B4:FD13 Could you add these devices to discover-data? Do you need more information? Helmut --- End Message --- --- Begin Message --- Source: discover-data Source-Version: 2.2013.01.11 We believe that the bug you reported is fixed in the latest version of discover-data, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 697...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated discover-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jan 2013 11:16:53 +0100 Source: discover-data Binary: discover-data Architecture: source all Version: 2.2013.01.11 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Petter Reinholdtsen Description: discover-data - Data lists for Discover hardware detection system Closes: 697839 Changes: discover-data (2.2013.01.11) unstable; urgency=low . * Update HW mappings for USB devices: 1130:0202: Install package pymissile. 091e:0003: Install packages gpsbabel, gpsbabel-gui, gpsman, gpstrans, mkgmap, qlandkartegt, qlandkartegt-garmin and viking. 04b4:fd10, 04b4:fd11, 04b4:fd12 and 04b4:fd13: Install sispmctl (Closes: #697839) * Revert changed input charmap for usb.ids from UTF-8 to ISO-8859-1. It is not using the same charmap as pci.ids. Checksums-Sha1: 8b10af41b40788d5bdeaf33cb5674bdbcb23f9e7 1108 discover-data_2.2013.01.11.dsc c2daac27b7d08806727644f40d7955f74dee3160 918983 discover-data_2.2013.01.11.tar.gz b75bb234970a33ca47a50e6d905d9075c01a1e88 496994 discover-data_2.2013.01.11_all.deb Checksums-Sha256: 0c2746620dc4137b1412411030d74a1fc3f3c038bcbc5decadadf907e76ff6ac 1108 discover-data_2.2013.01.11.dsc 19b4498dd006de2c886e3279b5feaa874c9894a38c966dc1e38cfbe27c3963f3 918983 discover-data_2.2013.01.11.tar.gz 282f6ce16aef03514c9ec27cc8849339e05e4c260ce87a70c683f3ac6a1bdf4c 496994 discover-data_2.2013.01.11_all.deb Files: 9a9433ca0de7a3d161480156a4eb82ec 1108 libs optional discover-data_2.2013.01.11.dsc dff223c271f3e9c52e7ba065c96c92ff 918983 libs optional discover-data_2.2013.01.11.tar.gz f3916a6a799505f21926a6d79add7781 496994 libs optional discover-data_2.2013.01.11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFQ7+bu20zMSyow1ykRAsfhAJ4n6TLoObLSOsIp3hdxtSWCSYx8MACgi8mi 6boO4olRzk8rUQ1gx2KtFZ0= =NIpn -END PGP SIGNATURE End Message ---
Processing of discover-data_2.2013.01.11_i386.changes
discover-data_2.2013.01.11_i386.changes uploaded successfully to localhost along with the files: discover-data_2.2013.01.11.dsc discover-data_2.2013.01.11.tar.gz discover-data_2.2013.01.11_all.deb Greetings, Your Debian queue daemon (running on host franck.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/e1ttbkn-k3...@franck.debian.org
discover-data_2.2013.01.11_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jan 2013 11:16:53 +0100 Source: discover-data Binary: discover-data Architecture: source all Version: 2.2013.01.11 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Petter Reinholdtsen Description: discover-data - Data lists for Discover hardware detection system Closes: 697839 Changes: discover-data (2.2013.01.11) unstable; urgency=low . * Update HW mappings for USB devices: 1130:0202: Install package pymissile. 091e:0003: Install packages gpsbabel, gpsbabel-gui, gpsman, gpstrans, mkgmap, qlandkartegt, qlandkartegt-garmin and viking. 04b4:fd10, 04b4:fd11, 04b4:fd12 and 04b4:fd13: Install sispmctl (Closes: #697839) * Revert changed input charmap for usb.ids from UTF-8 to ISO-8859-1. It is not using the same charmap as pci.ids. Checksums-Sha1: 8b10af41b40788d5bdeaf33cb5674bdbcb23f9e7 1108 discover-data_2.2013.01.11.dsc c2daac27b7d08806727644f40d7955f74dee3160 918983 discover-data_2.2013.01.11.tar.gz b75bb234970a33ca47a50e6d905d9075c01a1e88 496994 discover-data_2.2013.01.11_all.deb Checksums-Sha256: 0c2746620dc4137b1412411030d74a1fc3f3c038bcbc5decadadf907e76ff6ac 1108 discover-data_2.2013.01.11.dsc 19b4498dd006de2c886e3279b5feaa874c9894a38c966dc1e38cfbe27c3963f3 918983 discover-data_2.2013.01.11.tar.gz 282f6ce16aef03514c9ec27cc8849339e05e4c260ce87a70c683f3ac6a1bdf4c 496994 discover-data_2.2013.01.11_all.deb Files: 9a9433ca0de7a3d161480156a4eb82ec 1108 libs optional discover-data_2.2013.01.11.dsc dff223c271f3e9c52e7ba065c96c92ff 918983 libs optional discover-data_2.2013.01.11.tar.gz f3916a6a799505f21926a6d79add7781 496994 libs optional discover-data_2.2013.01.11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFQ7+bu20zMSyow1ykRAsfhAJ4n6TLoObLSOsIp3hdxtSWCSYx8MACgi8mi 6boO4olRzk8rUQ1gx2KtFZ0= =NIpn -END PGP SIGNATURE- 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/e1ttbuc-0004ek...@franck.debian.org
Processed: Commited to svn
Processing commands for cont...@bugs.debian.org:
> tags 681994 + pending
Bug #681994 [discover] discover-config --list doesn't work
Added tag(s) pending.
> tags 533688 + pending
Bug #533688 [discover] (discover_2.1.2-3/avr32): FTBFS: Outdated
config.{sub,guess}
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
533688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533688
681994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.135790198010696.transcr...@bugs.debian.org
Bug#697915: Problem with LVM when installing latest Debian Wheezy
Package: installation-reports Boot method: Cd "debian-wheezy-DI-b4-amd64-netinst.iso". Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso Date: Friday 11 January 2013. Machine: Tested on VirtualBox and a Dell Optiplex 960 and a Dell PowerEdge R210. Processor: Memory: Partitions: Sys. fich.Type 1K-blocks Util. Disponible Uti% Monté sur rootfsrootfs19223252 1100720 17146048 7% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs37988 244 37744 1% /run /dev/mapper/vglocal-slash ext4 19223252 1100720 17146048 7% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs75960 0 75960 0% /run/shm /dev/sda1 ext4 93207 23165 65230 27% /boot fdisk -l Disque /dev/sda : 107.4 Go, 107374182400 octets 255 têtes, 63 secteurs/piste, 13054 cylindres, total 209715200 secteurs Unités = secteurs de 1 * 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Identifiant de disque : 0x0004cbc3 Périphérique Amorce DébutFin Blocs Id Système /dev/sda1 *2048 194559 96256 83 Linux /dev/sda2 194560 209713151 104759296 8e LVM Linux Disque /dev/mapper/vglocal-slash : 20.0 Go, 19998441472 octets 255 têtes, 63 secteurs/piste, 2431 cylindres, total 39059456 secteurs Unités = secteurs de 1 * 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Identifiant de disque : 0x Disque /dev/mapper/vglocal-swap : 998 Mo, 998244352 octets 255 têtes, 63 secteurs/piste, 121 cylindres, total 1949696 secteurs Unités = secteurs de 1 * 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Identifiant de disque : 0x Résultat de lspci -knn (ou lspci -nn) : 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] 00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) 00:0b.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) Installation du système de base : [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Hi, It seems there is a problem with partman and LVM. I created a VirtualBox machine with a 107.4 GB hard drive (sparce file). In the first place, I created 3 masters partitions with partman. - /dev/sda1/ as /boot in ext4 - 98.6 MB - /dev/sda2 as LVM partition - 50 GB - /dev/sda3 as LVM partition - 57.3 GB Next, I set up LVM and I created a VG with /dev/sda2. I realised that /dev/sda3 is useless to me, so i deleted it. Next, I deleted my VG and /dev/sda2. I created a new /dev/sda2 partition - 107.3 GB as LVM partition. When I tried to configure LVM, it show /dev/sda2 with 5 MB. I should see the new size of my /dev/sda2. I made an other VM with the same settings, and I found that if I made a LVM by mistake, the only way to display the correct size of /dev/sda2 is to recreate a default partition for /dev/sda. I hope everything I said can help. I can provide screenshot if you prefer. Have a nice day Benoît
Processed: Re: Bug#697868: debian-cd: cd 1 should install a network configuration tool
Processing commands for cont...@bugs.debian.org: > reassign 697868 tasksel Bug #697868 [debian-cd] debian-cd: cd 1 should install a network configuration tool Bug reassigned from package 'debian-cd' to 'tasksel'. No longer marked as found in versions debian-cd/3.1.10. Ignoring request to alter fixed versions of bug #697868 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 697868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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.13579107737138.transcr...@bugs.debian.org
Bug#688336: os-prober 1.56 and btrfs
This was found on Fedora 18.
Both os-prober and linux-boot-prober do not support root, boot, or
root+boot on a btrfs subvolume.
The attached patch corrects that. It supplies information such that
grub2, with an additional small patch, will not handle btrfs in
30_os-prober.
I have attached two additional small patches for os-prober which
suppresses debug messages until needed and to fix os-prober to handle
/boot on a separate logical volume.
Gene
diff -uNr os-prober-1.56-orig-1/common.sh os-prober-1.56/common.sh
--- os-prober-1.56-orig-1/common.sh 2013-01-10 08:33:45.200766262 -0500
+++ os-prober-1.56/common.sh 2013-01-10 08:34:43.644058934 -0500
@@ -127,6 +127,7 @@
done
}
+# add forth parameter to pickup btrfs subvol info
parsefstab () {
while read -r line; do
case "$line" in
@@ -137,12 +138,22 @@
set -f
set -- $line
set +f
-printf '%s %s %s\n' "$1" "$2" "$3"
+printf '%s %s %s %s\n' "$1" "$2" "$3" "$4"
;;
esac
done
}
+#check_btrfs_mounted $bootsv $bootuuid)
+check_btrfs_mounted () {
+ bootsv="$1"
+ bootuuid="$2"
+ bootdev=$(blkid | grep "$bootuuid" | cut -d ':' -f 1)
+ bindfrom=$(grep " btrfs " /proc/self/mountinfo |
+ grep " $bootdev " | grep " /$bootsv " | cut -d ' ' -f 5)
+ printf "%s" "$bindfrom"
+}
+
unescape_mount () {
printf %s "$1" | \
sed 's/\\011/ /g; s/\\012/\n/g; s/\\040/ /g; s/\\134/\\/g'
diff -uNr os-prober-1.56-orig-1/common.sh.orig os-prober-1.56/common.sh.orig
--- os-prober-1.56-orig-1/common.sh.orig 1969-12-31 19:00:00.0 -0500
+++ os-prober-1.56/common.sh.orig 2013-01-10 08:34:43.642058924 -0500
@@ -0,0 +1,293 @@
+newns () {
+ [ "$OS_PROBER_NEWNS" ] || exec /usr/lib/newns "$0" "$@"
+}
+
+cleanup_tmpdir=false
+cleanup_ro_partitions=
+cleanup () {
+ local partition
+ for partition in $cleanup_ro_partitions; do
+blockdev --setrw "$partition"
+ done
+ if $cleanup_tmpdir; then
+rm -rf "$OS_PROBER_TMP"
+ fi
+}
+
+require_tmpdir() {
+ if [ -z "$OS_PROBER_TMP" ]; then
+if type mktemp >/dev/null 2>&1; then
+ export OS_PROBER_TMP="$(mktemp -d /tmp/os-prober.XX)"
+ cleanup_tmpdir=:
+ trap cleanup EXIT HUP INT QUIT TERM
+else
+ export OS_PROBER_TMP=/tmp
+fi
+ fi
+}
+
+count_for() {
+ _labelprefix="$1"
+ _result=$(grep "^${_labelprefix} " /var/lib/os-prober/labels 2>/dev/null || true)
+
+ if [ -z "$_result" ]; then
+return
+ else
+echo "$_result" | cut -d' ' -f2
+ fi
+}
+
+count_next_label() {
+ require_tmpdir
+
+ _labelprefix="$1"
+ _cfor="$(count_for "${_labelprefix}")"
+
+ if [ -z "$_cfor" ]; then
+echo "${_labelprefix} 1" >> /var/lib/os-prober/labels
+ else
+sed "s/^${_labelprefix} ${_cfor}/${_labelprefix} $(($_cfor + 1))/" /var/lib/os-prober/labels > "$OS_PROBER_TMP/os-prober.tmp"
+mv "$OS_PROBER_TMP/os-prober.tmp" /var/lib/os-prober/labels
+ fi
+
+ echo "${_labelprefix}${_cfor}"
+}
+
+progname=
+cache_progname() {
+ case $progname in
+'')
+ progname="$(basename "$0")"
+ ;;
+ esac
+}
+
+log() {
+ cache_progname
+ logger -t "$progname" "$@"
+}
+
+error() {
+ log "error: $@"
+}
+
+warn() {
+ log "warning: $@"
+}
+
+debug() {
+ if [ -n "$OS_PROBER_ENABLE_DEBUG" ]; then
+log "debug: $@"
+ fi
+}
+
+result () {
+ log "result:" "$@"
+ echo "$@"
+}
+
+# shim to make it easier to use os-prober outside d-i
+if ! type mapdevfs >/dev/null 2>&1; then
+ mapdevfs () {
+readlink -f "$1"
+ }
+fi
+
+item_in_dir () {
+ if [ "$1" = "-q" ]; then
+ q="-q"
+ shift 1
+ else
+ q=""
+ fi
+ [ -d "$2" ] || return 1
+ # find files with any case
+ ls -1 "$2" | grep $q -i "^$1$"
+}
+
+# We can't always tell the filesystem type up front, but if we have the
+# information then we should use it. Note that we can't use block-attr here
+# as it's only available in udebs.
+fs_type () {
+ if (export PATH="/lib/udev:$PATH"; type vol_id) >/dev/null 2>&1; then
+ PATH="/lib/udev:$PATH" vol_id --type "$1" 2>/dev/null
+ elif type blkid >/dev/null 2>&1; then
+ blkid -o value -s TYPE "$1" 2>/dev/null
+ else
+ return 0
+ fi
+}
+
+parse_proc_mounts () {
+ while read -r line; do
+ set -f
+ set -- $line
+ set +f
+ printf '%s %s %s\n' "$(mapdevfs "$1")" "$2" "$3"
+ done
+}
+
+parsefstab () {
+ while read -r line; do
+ case "$line" in
+ "#"*)
+:
+ ;;
+ *)
+set -f
+set -- $line
+set +f
+printf '%s %s %s\n' "$1" "$2" "$3"
+ ;;
+ esac
+ done
+}
+
+unescape_mount () {
+ printf %s "$1" | \
+ sed 's/\\011/ /g; s/\\012/\n/g; s/\\040/ /g; s/\\134/\\/g'
+}
+
+ro_partition () {
+ if type blockdev >/dev/null 2>&1 && \
+ [ "$(blockdev --getro "$1")" = 0 ] && \
+ blockdev --setro "$1"; then
+ cleanup_ro_partitions="${cleanup_ro_partitions:+$cleanup_ro_partitions }$1"
+ trap cleanup EXIT HUP INT QUIT TERM
+ fi
+}
+
+find_label () {
+ local output
+ if type blkid >/dev/null 2>&1; then
+ # Hopefully everyone has blkid by now
+ output="$(blkid -o device -t LABEL="$1")" || return 1
+ echo "$output" | head -n1
+ elif
Re: Last 2 commits in cdrom-checker
Quoting Colin Watson (cjwat...@debian.org): > > I suspect e8ae8876bcea30cc45bcba25ed1e9ea2a317aff0 to be safe and a > > good idea.I have however no idea for > > 1ec13c5a378076c10988237972d4df0f1eefafd3, given my own C-fu..:-) > > It made the jenkins build stable and was non-intrusive enough that I > didn't think it was necessary to put it on a jessie branch. OK, so unless Cyril objects, I will upload a version with these fixes. Christian, still hunting pending stuff in master branches..:-) signature.asc Description: Digital signature
finish-install: save entropy for target system
I've just committed this change to finish-install.git, inspired by comments in https://factorable.net/weakkeys12.extended.pdf. (At least for systems using sysvinit, this is the only change that I can readily see needs to be made to Debian based on that paper.) I can't immediately point to a vulnerability caused by not having enough entropy at first boot, but entropy is a scarce resource in general on many systems and it seems worth going to some effort to preserve as much of it as possible. If you install your system once and then clone it, this change does mean that all the clones will start out with the same random seed. However, this is no worse than them starting out with no random seed at all; it just perturbs all their entropy pools in the same way. I think we should include this change in wheezy. Any comments? commit ff70cfbd2a6e93b23903c7f16dfdac0b79b46b98 Author: Colin Watson Date: Fri Jan 11 18:05:30 2013 + Save a random seed to the installed system so that it has better entropy on first boot (LP: #1098299). diff --git a/debian/changelog b/debian/changelog index 27f18f7..3481dfd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +finish-install (2.42) UNRELEASED; urgency=low + + * Save a random seed to the installed system so that it has better entropy +on first boot (LP: #1098299). + + -- Colin Watson Fri, 11 Jan 2013 16:32:28 + + finish-install (2.41) unstable; urgency=low * Make sure to run update-initramfs if both cryptsetup and console-setup diff --git a/finish-install.d/94random-seed b/finish-install.d/94random-seed new file mode 100755 index 000..b00aae1 --- /dev/null +++ b/finish-install.d/94random-seed @@ -0,0 +1,17 @@ +#! /bin/sh +set -e + +# If possible, save a random seed so that the installed system has better +# entropy on first boot. Based on /etc/init.d/urandom in initscripts. +if [ -c /dev/urandom ] && [ -d /target/var/lib/urandom ]; then + if ! POOLBYTES=$(( + ($(cat /proc/sys/kernel/random/poolsize 2>/dev/null) + 7) / 8 + )); then + POOLBYTES=512 + fi + umask 077 + dd if=/dev/urandom of=/target/var/lib/urandom/random-seed \ + bs="$POOLBYTES" count=1 >/dev/null 2>&1 +fi + +exit 0 Thanks, -- Colin Watson [cjwat...@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/2013080607.gb5...@riva.dynamic.greenend.org.uk
Re: finish-install: save entropy for target system
Quoting Colin Watson (cjwat...@debian.org): > I think we should include this change in wheezy. +1...unless Cyril really wants us to be feature-frozen during the RC stage, which would be understandable. signature.asc Description: Digital signature
Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
tags 681227 + patch block 651720 by 681227 # kFreeBSD bugfix couldn't enter wheezy yet due to regressions thanks Hi, On 07/01/13 19:56, Wouter Verhelst wrote: >> What to do with the workaround added by Wouter in grub-installer/1.84? > > The workaround tried to eliminate the possibility of invalid data coming > from "somewhere" in the installer. [...] I understand this made sense *if* a bug in the installer had been appending nonsense to an otherwise-valid $bootdev, but I think we've disproven this now. >> Silently ignoring a failure seems risky when we know that it should not >> happen. (Someone may want to specify multiple targets, and if one of >> them is typo'd it would be silently skipped in this case). > > That's indeed the only case that isn't caught by the current code. But that was at least caught by the original code - the GRUB install step failed if the user gave invalid input. Except in this bug report, the user thought the failure was a software bug, rather than wrong keyboard input which I'm sure it was. With the workaround still in place, it may silently ignore such an error, whether it comes from the user or from code, and I think that is a more harmful situation. Removing the workaround would close regressions #696903, #696942 affecting sid, unbreaking the sid_d-i daily images, where GRUB is not installable right now for kfreebsd-*, grub-yeeloong and apparently grub-efi systems. It would also allow important bugfix #681227 to migrate to testing. IMHO it would close this bug too, because it would mean the user-supplied bootdevs *are* being validated again. Patch for this actually just a diff limited to ./grub-installer from: $ git revert a070f516 99389d59 926cee22 Of course there are still ways to improve, e.g. offering a list of partitions to choose from instead of free-text input, but anything like that must surely wait until another release. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org diff --git a/grub-installer b/grub-installer index 9a72e54..f01eda1 100755 --- a/grub-installer +++ b/grub-installer @@ -645,16 +645,11 @@ info "Installing grub on '$bootdev'" update_mtab -installed=0 - if [ -z "$frdisk" ]; then + # Install grub on each space separated disk in the list bootdevs="$bootdev" for bootdev in $bootdevs; do - # workaround for #681227 - if ! [ "$bootdev" = dummy -o -b "$bootdev" -o -c "$bootdev" ]; then - continue - fi grub_install_params= if ! is_floppy "$bootdev"; then if $chroot $ROOT grub-install -h 2>&1 | grep -q no-floppy; then @@ -690,7 +685,6 @@ if [ -z "$frdisk" ]; then esac if [ "$CODE" = 0 ]; then info "grub-install ran successfully" - installed=$(( $installed + 1 )) else case $ARCH:$grub_package in *:grub|*:grub-pc|*:grub-efi|sparc:grub-ieee1275) @@ -707,12 +701,7 @@ if [ -z "$frdisk" ]; then exit 1 fi done - if [ $installed -lt 1 ]; then - error "no boot device found to install to" - # we should probably show an error message here, but I believe - # we're in string freeze... - exit 1 - fi + else # Semi-manual grub setup for Serial ATA RAID/multipath
Processed: Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Processing commands for cont...@bugs.debian.org:
> tags 681227 + patch
Bug #681227 [grub-installer] does not validate free-form input
Added tag(s) patch.
> block 651720 by 681227
Bug #651720 {Done: Wouter Verhelst } [src:grub-installer]
new ZFS install on / fails if /boot isn't ZFS
651720 was not blocked by any bugs.
651720 was not blocking any bugs.
Added blocking bug(s) of 651720: 681227
> # kFreeBSD bugfix couldn't enter wheezy yet due to regressions
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
651720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651720
681227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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.13579284001112.transcr...@bugs.debian.org
Bug#697890: installation-reports: iwconfig not in /sbin
Yes, indeed ! It's about wheezy-xfce (testing - build cd binay-1 20121217-05:10). During installation I got a ~"missing rt28xx" message and was asked to provide a "floppy" with the firmware. Answered "no" and proceeded with installation. As such the installation is OK, but it looks there are missing pieces or some access rights / configuration problems (see also #697331, #697327). Having found a fix (not the best solution) for #697331, #697327 I wanted to configure the WiFi device. I added deb http://ftp.be.debian.org/debian wheezy main contrib non-free in /etc/apt/sources.list and installed firmware-ralink (v 0.36) Then I started the xfce "network manager" (parameters -> network connections), filled in required information and wanted to check the status with iwconfig. Could only find this : root? root? find / -xdev -iname *iwconfig* /usr/share/bash-completion/completions/iwconfig root? -- 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/2013053627.d07c9de5c00c0370a7fe9...@mobistarmail.be
Bug#697953: installation report (successful)
Package: installation-reports Boot method: cdrom Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso Date: december, the 28th, 2012 Machine: DELL Latitude E6400 Processor: Intel(R) Core(TM)2 Duo CPU P8600@ Memory: Partitions: rootfs rootfs 9611492 66318402491412 73% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 404956 784 404172 1% /run /dev/disk/by-uuid/6d215c34-f024-4468-a9b9-6df0860901c9 ext4 9611492 66318402491412 73% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 2482300 802482220 1% /run/shm /dev/sda6 ext4 222520980 13794884 197422672 7% /home Résultat de lspci -knn (ou lspci -nn) : 0:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) 00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M-E LPC Interface Controller [8086:2917] (rev 03) 00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) 03:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ba) 03:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04) 03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 21) 0c:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4235] Installation du système de base : Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Two problems I encountered (and solved) right after the install. - shutdown I went with a kde install and there was a problem when shutting down. The shutdown messages appeared as expected, but the screen was not turned off at the end. The bug is similar to the one described in this page http://ubuntuforums.org/showthread.php?p=7806322 Following the advice, i.e. turning off the logout sound, solved the problem. This seems to be peculiar to kde. - printer I got an error "cups-authorization-canceled" when trying to install my printer. This was due to the fact that I was not registered in the lpadmin group. I had to install KUser to register myself in this group. It would be nice to be informed about this fact during the installation. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Bug#697890: installation-reports: iwconfig not in /sbin
On Fri, 2013-01-11 at 15:36 +0100, jswmb01x wrote: > Yes, indeed ! > > It's about wheezy-xfce (testing - build cd binay-1 20121217-05:10). > > During installation I got a ~"missing rt28xx" message and was asked to > provide a "floppy" with the firmware. Answered "no" and proceeded with > installation. As such the installation is OK, but it looks there are missing > pieces or some access rights / configuration problems (see also #697331, > #697327). > > Having found a fix (not the best solution) for #697331, #697327 I wanted to > configure the WiFi device. I added > deb http://ftp.be.debian.org/debian wheezy main contrib non-free > in /etc/apt/sources.list > and installed firmware-ralink (v 0.36) > > Then I started the xfce "network manager" (parameters -> network > connections), filled in required information and wanted to check the status > with iwconfig. > > Could only find this : > > root? > root? find / -xdev -iname *iwconfig* > /usr/share/bash-completion/completions/iwconfig > root? iwconfig (wireless-tools package) is obsolescent, but certainly iw and crda should get installed. I previously reported that against task-laptop (#653717) but since desktops commonly also have wireless networking I think that task-desktop should include them as well. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: Bug#697890: installation-reports: iwconfig not in /sbin
On Fri 11 Jan 2013 at 15:36:27 +0100, jswmb01x wrote: > Then I started the xfce "network manager" (parameters -> network > connections), filled in required information and wanted to check the > status with iwconfig. > > Could only find this : > > root? > root? find / -xdev -iname *iwconfig* > /usr/share/bash-completion/completions/iwconfig > root? You will get iwconfig by installing the wireless-tools package; or you could consider the alternative iw package. The Xfce task originally used wicd, not network-manager-gnome, and wireless-tools came with it as a dependency. -- 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/20130112001220.GO32121@desktop
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:mipsel Jan 10 00:10 buildd@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Jan 10 00:12 buildd@rem build_cobalt_netboot-2.6_ssh http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log * OLD BUILD:mipsel Jan 10 00:15 buildd@rem build_cobalt_netboot-2.6_common http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log * OLD BUILD:mipsel Jan 10 00:18 buildd@rem build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log * OLD BUILD:mipsel Jan 10 00:21 buildd@rem build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mipsel Jan 10 00:24 buildd@rem build_loongson-2f_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_loongson-2f_netboot-2.6.log Totals: 95 builds (0 failed, 6 old) -- 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/e1ttps8-0005j4...@ravel.debian.org
Bug#697953: marked as done (installation report (successful))
Your message dated Sat, 12 Jan 2013 08:12:06 +0100 with message-id <20130112071206.gm5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#697953: installation report (successful) has caused the Debian Bug report #697953, regarding installation report (successful) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: cdrom Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso Date: december, the 28th, 2012 Machine: DELL Latitude E6400 Processor: Intel(R) Core(TM)2 Duo CPU P8600@ Memory: Partitions: rootfs rootfs 9611492 66318402491412 73% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 404956 784 404172 1% /run /dev/disk/by-uuid/6d215c34-f024-4468-a9b9-6df0860901c9 ext4 9611492 66318402491412 73% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 2482300 802482220 1% /run/shm /dev/sda6 ext4 222520980 13794884 197422672 7% /home Résultat de lspci -knn (ou lspci -nn) : 0:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) 00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M-E LPC Interface Controller [8086:2917] (rev 03) 00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) 03:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ba) 03:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04) 03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 21) 0c:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4235] Installation du système de base : Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Two problems I encountered (and solved) right after the i
Bug#697890: marked as done (installation-reports: iwconfig not in /sbin)
Your message dated Sat, 12 Jan 2013 08:10:41 +0100 with message-id <20130112071041.gl5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#697890: installation-reports: iwconfig not in /sbin has caused the Debian Bug report #697890, regarding installation-reports: iwconfig not in /sbin 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Tried to configure the wireless interface. root? iwconfig bash: iwconfig : commande introuvable root? ls -l /sbin/i* -rwxr-xr-x 1 root root 72296 sep 7 09:54 /sbin/ifconfig -rwxr-xr-x 3 root root 54272 nov 3 18:59 /sbin/ifdown -rwxr-xr-x 3 root root 54272 nov 3 18:59 /sbin/ifquery -rwxr-xr-x 3 root root 54272 nov 3 18:59 /sbin/ifup -rwxr-xr-x 1 root root 40560 nov 16 22:25 /sbin/init lrwxrwxrwx 1 root root 9 aoû 27 03:55 /sbin/insmod -> /bin/kmod -rwxr-xr-x 1 root root 56384 nov 23 22:28 /sbin/insserv -rwxr-xr-x 1 root root 2382 jun 28 2012 /sbin/installkernel lrwxrwxrwx 1 root root 7 jun 21 2012 /sbin/ip -> /bin/ip lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/ip6tables -> xtables-multi lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/ip6tables-restore -> xtables- multi lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/ip6tables-save -> xtables-multi -rwxr-xr-x 1 root root 18696 sep 7 09:54 /sbin/ipmaddr lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/iptables -> xtables-multi lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/iptables-restore -> xtables- multi lrwxrwxrwx 1 root root13 jui 28 18:07 /sbin/iptables-save -> xtables-multi -rwxr-xr-x 1 root root 22800 sep 7 09:54 /sbin/iptunnel -rwxr-xr-x 1 root root 14552 sep 9 22:06 /sbin/isosize root? -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20121217-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux pc4 3.2.0-4-amd64 #1 SMP Debian 3.2.35-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Fa
Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Quoting Steven Chamberlain (ste...@pyro.eu.org): > Patch for this actually just a diff limited to ./grub-installer from: > > $ git revert a070f516 99389d59 926cee22 Agreed from my side. I guess we now just need Cyril's ACK to apply in git and probably buildunless something else is needed in grub-installer (which seems to remain as "the last place where we have to stabilize stuff"). signature.asc Description: Digital signature
