Bug#761619: installation-reports: Disk scan hangs
Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, I tried the b1 netinst ISO (debian-jessie-DI-b1-amd64-netinst.iso, MD5 8a386a16ab2939e00bfd5efa27007216.) The installer came up normally but the disk scan hung. This might be due to multiple btrfs filesystems or a bcache partition. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable'), (190, 'testing'), (180, 'unstable'), (3, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140915055524.8654.60317.reportbug@ws.local
Bug#761619: Acknowledgement (installation-reports: Disk scan hangs)
blkid info /dev/bcache0: LABEL=btrfs0 UUID=df532815-f9df-42a3-9f4f-3cdf3bb3d2d9 UUID_SUB=79f8e311-3000-438c-9d95-08dc07b328b0 TYPE=btrfs /dev/mapper/megaraid-root: LABEL=debroot UUID=b3f534ce-5509-4ab9-88ca-feb4a3041131 TYPE=ext4 /dev/mapper/S830--512A-CentOS5: LABEL=sandboxes UUID=8bde1219-e609-4fc0-aff0-be4c3e7da578 SEC_TYPE=ext2 TYPE=ext3 /dev/mapper/S830--512A-root: UUID=52ad8d8f-5c0c-4d7d-9bb0-aad9b25fa559 TYPE=ext4 /dev/mapper/vg--debHD-home: UUID=fef87605-40e0-44bd-b2e9-4202891b08a4 TYPE=ext4 /dev/mapper/vg--debHD-root: UUID=2fc7a241-7504-4ead-9509-ce22577a9849 TYPE=ext4 /dev/mapper/vg--debHD-swap: UUID=0d5a3423-cb9b-4e23-acaa-a108e24406ff TYPE=swap /dev/sda2: LABEL=boot UUID=efdcfb4c-8644-48f0-adee-936741dae73b TYPE=ext2 /dev/sda3: UUID=KxCXGk-ELu4-2su6-8o60-PVf4-xSWC-rMu2JK TYPE=LVM2_member /dev/sda4: UUID=008c20b6-8055-4bb8-8a52-adceaf9de75b TYPE=swap /dev/sdb1: LABEL=System Reserved UUID=968699FA8699DB57 TYPE=ntfs /dev/sdb2: UUID=02FE9C1FFE9C0D53 TYPE=ntfs /dev/sdb3: UUID=fd14c1fb-99f7-4205-a825-a2701a93f55c TYPE=ext4 /dev/sdb5: UUID=f034f2ef-eaad-40af-8530-83f3b4691b6d UUID_SUB=af9b7cc6-afe7-48fd-b297-f69aa3b82c72 TYPE=btrfs /dev/sdc1: UUID=74ee9800-2a3e-4d5f-b768-803faccf99c2 TYPE=ext2 /dev/sdc5: UUID=9W92nI-hA9c-sjtk-DuQz-miR0-WrVK-oDDmWI TYPE=LVM2_member /dev/sde1: UUID=72a7d6d8-9c7c-47a3-8949-6cc3ced78153 TYPE=ext4 /dev/sde2: UUID=07f88f79-abfa-4b0a-88f8-0891e2333db4 TYPE=swap /dev/sde5: UUID=LWWgc9-Beyf-6v55-F3I9-ePeP-7K05-wlAEdw TYPE=LVM2_member /dev/sdf1: LABEL=SeagateBackup UUID=3f8b489c-c294-415a-abb9-ac1baeed22bb UUID_SUB=cb7983a7-a516-48a2-b989-f67871332a72 TYPE=btrfs /dev/sdg1: LABEL=SeagateBackup UUID=3f8b489c-c294-415a-abb9-ac1baeed22bb UUID_SUB=7eeb3143-5d9a-4f32-a058-18e29fa23d74 TYPE=btrfs /dev/sdh1: LABEL=Debian jessie-DI-b1 amd64 1 TYPE=iso9660 /dev/sdh2: SEC_TYPE=msdos UUID=378E-F825 TYPE=vfat /dev/sdj1: UUID=2C55-1C1F TYPE=vfat
Bug#761619: Acknowledgement (installation-reports: Disk scan hangs)
parted info. sdd1 is the bcache partition. parted Description: Binary data
Bug#761619: installation-reports: Disk scan hangs
parted info (sdd1 is the bcache partition) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5416816b.7020...@gmail.com
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
[Samuel Thibault] I have attached the syslog, interestingly: Aug 26 00:10:17 grub-installer: info: Installing grub on '' Yes, I suspect that is a typo in the script somewhere, failing to set the default. partman succeed in picking a good default, perhaps grub-installer can use the same logic? Anyway, I ran a Debian Edu installation using DEBCONF_DEBUG=developer, and got this output from the grub-installer run: Aug 25 21:07:34 main-menu[176]: INFO: Menu item 'grub-installer' selected Aug 25 21:07:34 debconf: -- SETTITLE debian-installer/grub-installer/title Aug 25 21:07:34 debconf: -- 0 OK Aug 25 21:07:34 debconf: -- CAPB backup Aug 25 21:07:34 debconf: -- 0 multiselect backup progresscancel align escape plugin-terminal Aug 25 21:07:34 grub-installer: info: architecture: i386/generic Aug 25 21:07:34 debconf: -- GET base-installer/install-recommends Aug 25 21:07:34 debconf: -- 0 true Aug 25 21:07:36 debconf: -- GET mirror/protocol Aug 25 21:07:36 debconf: -- 0 http Aug 25 21:07:36 debconf: -- GET mirror/http/proxy Aug 25 21:07:36 debconf: -- 0 Aug 25 21:07:36 debconf: -- GET debconf/priority Aug 25 21:07:36 debconf: -- 0 critical Aug 25 21:07:36 debconf: -- GET debian-installer/locale Aug 25 21:07:36 debconf: -- 0 en_GB.UTF-8 Aug 25 21:07:39 in-target: debconf (developer): frontend started Aug 25 21:07:39 in-target: debconf (developer): Trying to find a templates file.. Aug 25 21:07:39 in-target: debconf (developer): Trying /usr/bin/debconf-apt-progress.templates Aug 25 21:07:39 in-target: debconf (developer): Trying /usr/share/debconf/templates/debconf-apt-progress.templates Aug 25 21:07:39 in-target: debconf (developer): Couldn't find a templates file. Aug 25 21:07:39 in-target: debconf (developer): frontend running, package name is Aug 25 21:07:39 in-target: debconf (developer): starting /usr/bin/debconf-apt-progress --no-progress --logstderr -- apt-get -q -y --no-remove install grub-common Aug 25 21:07:39 in-target: debconf (developer): -- GET debconf/priority Aug 25 21:07:39 in-target: debconf (developer): -- 0 high Aug 25 21:07:39 in-target: Reading package lists... Aug 25 21:07:39 in-target: Aug 25 21:07:40 in-target: Building dependency tree... Aug 25 21:07:40 in-target: Aug 25 21:07:40 in-target: Reading state information... Aug 25 21:07:40 in-target: Aug 25 21:07:40 in-target: The following extra packages will be installed: Aug 25 21:07:40 in-target: os-prober Aug 25 21:07:40 in-target: Suggested packages: Aug 25 21:07:40 in-target: multiboot-doc grub-emu xorriso Aug 25 21:07:40 in-target: The following NEW packages will be installed: Aug 25 21:07:40 in-target: grub-common os-prober Aug 25 21:07:41 in-target: debconf (developer): -- SUBST debconf-apt-progress/info DESCRIPTION Retrieving file 1 of 2 Aug 25 21:07:41 in-target: debconf (developer): -- 0 Aug 25 21:07:41 in-target: debconf (developer): -- PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 in-target: debconf (developer): DATA debconf-apt-progress/info type text Aug 25 21:07:41 debconf: -- DATA debconf-apt-progress/info type text Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41 in-target: debconf (developer): 0 OK Aug 25 21:07:41 in-target: debconf (developer): DATA debconf-apt-progress/info description Retrieving file 1 of 2 Aug 25 21:07:41 debconf: -- DATA debconf-apt-progress/info description Retrieving file 1 of 2 Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41 in-target: debconf (developer): 0 OK Aug 25 21:07:41 in-target: debconf (developer): PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 debconf: -- PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41 in-target: debconf (developer): 0 OK Aug 25 21:07:41 in-target: debconf (developer): -- 0 OK Aug 25 21:07:41 kernel: [ 8259.395341] ISO 9660 Extensions: Microsoft Joliet Level 3 Aug 25 21:07:41 kernel: [ 8259.395831] ISO 9660 Extensions: RRIP_1991A Aug 25 21:07:41 in-target: debconf (developer): -- SUBST debconf-apt-progress/info DESCRIPTION Retrieving file 1 of 2 Aug 25 21:07:41 in-target: debconf (developer): -- 0 Aug 25 21:07:41 debconf: -- DATA debconf-apt-progress/info type text Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41 in-target: debconf (developer): -- PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 in-target: debconf (developer): DATA debconf-apt-progress/info type text Aug 25 21:07:41 in-target: debconf (developer): 0 OK Aug 25 21:07:41 in-target: debconf (developer): DATA debconf-apt-progress/info description Retrieving file 1 of 2 Aug 25 21:07:41 debconf: -- DATA debconf-apt-progress/info description Retrieving file 1 of 2 Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41 in-target: debconf (developer): 0 OK Aug 25 21:07:41 in-target: debconf (developer): PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 debconf: -- PROGRESS INFO debconf-apt-progress/info Aug 25 21:07:41 debconf: -- 0 OK Aug 25 21:07:41
Linux kernel ABI bump in testing: from 3.14-2 to 3.16-1
Linux kernel ABI bump in testing: from 3.14-2 to 3.16-1 Full summary: http://d-i.debian.org/kernel-summary.html#testing -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtrfh-0005wg...@dillon.debian.org
Re: Linux kernel ABI bump in testing: from 3.14-2 to 3.16-1
Linux kernel watcher debian-boot@lists.debian.org (2014-09-15): Linux kernel ABI bump in testing: from 3.14-2 to 3.16-1 Full summary: http://d-i.debian.org/kernel-summary.html#testing Interesting… linux-image-3.16-1-arm64 | 3.16.2-3 | testing | arm64 linux-image-3.16-1-arm64-dbg | 3.16.2-3 | testing | arm64 linux-image-3.16-1-powerpc64le | 3.16.2-3 | testing | ppc64el Mraw, KiBi. signature.asc Description: Digital signature
Processing of hw-detect_1.103_i386.changes
hw-detect_1.103_i386.changes uploaded successfully to ftp-master.debian.org along with the files: hw-detect_1.103_i386.udeb ethdetect_1.103_all.udeb disk-detect_1.103_all.udeb driver-injection-disk-detect_1.103_all.udeb archdetect_1.103_i386.udeb hw-detect_1.103.dsc hw-detect_1.103.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtsgv-0005da...@coccia.debian.org
Processing of lvmcfg_1.35_i386.changes
lvmcfg_1.35_i386.changes uploaded successfully to ftp-master.debian.org along with the files: lvmcfg_1.35_all.udeb lvmcfg-utils_1.35_all.udeb lvmcfg_1.35.dsc lvmcfg_1.35.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtsh0-0005dg...@coccia.debian.org
Processing of hw-detect_1.103_i386.changes
hw-detect_1.103_i386.changes uploaded successfully to localhost along with the files: hw-detect_1.103_i386.udeb ethdetect_1.103_all.udeb disk-detect_1.103_all.udeb driver-injection-disk-detect_1.103_all.udeb archdetect_1.103_i386.udeb hw-detect_1.103.dsc hw-detect_1.103.tar.xz 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: https://lists.debian.org/e1xtskw-0002oa...@franck.debian.org
Processing of lvmcfg_1.35_i386.changes
lvmcfg_1.35_i386.changes uploaded successfully to localhost along with the files: lvmcfg_1.35_all.udeb lvmcfg-utils_1.35_all.udeb lvmcfg_1.35.dsc lvmcfg_1.35.tar.xz 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: https://lists.debian.org/e1xtskw-0002o1...@franck.debian.org
Processing of mdcfg_1.47_i386.changes
mdcfg_1.47_i386.changes uploaded successfully to ftp-master.debian.org along with the files: mdcfg_1.47_all.udeb mdcfg-utils_1.47_all.udeb mdcfg_1.47.dsc mdcfg_1.47.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtsqp-000621...@coccia.debian.org
Processing of grub-installer_1.97_i386.changes
grub-installer_1.97_i386.changes uploaded successfully to ftp-master.debian.org along with the files: grub-installer_1.97_i386.udeb grub-installer_1.97.dsc grub-installer_1.97.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtsql-00061v...@coccia.debian.org
Processing of grub-installer_1.97_i386.changes
grub-installer_1.97_i386.changes uploaded successfully to localhost along with the files: grub-installer_1.97_i386.udeb grub-installer_1.97.dsc grub-installer_1.97.tar.xz 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: https://lists.debian.org/e1xtsun-00063o...@franck.debian.org
Processing of mdcfg_1.47_i386.changes
mdcfg_1.47_i386.changes uploaded successfully to localhost along with the files: mdcfg_1.47_all.udeb mdcfg-utils_1.47_all.udeb mdcfg_1.47.dsc mdcfg_1.47.tar.xz 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: https://lists.debian.org/e1xtsun-00063f...@franck.debian.org
hw-detect_1.103_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:25:54 +0200 Source: hw-detect Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect Architecture: source i386 all Version: 1.103 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: archdetect - Hardware architecture detector (udeb) disk-detect - Detect disk drives (udeb) driver-injection-disk-detect - Detect OEM driver injection disks (udeb) ethdetect - Detect network hardware and load kernel drivers for it (udeb) hw-detect - Detect hardware and load kernel drivers for it (udeb) Changes: hw-detect (1.103) unstable; urgency=low . [ Petter Reinholdtsen ] * Enable hardening when building archdetect. Checksums-Sha1: 5e264f50901a09457c371d95d01ab616fbd82234 2026 hw-detect_1.103.dsc 016693cbe7e440a59b2db6917b9dd7e09cd6a747 179236 hw-detect_1.103.tar.xz 55e4c6de2608e1ada9effd48b9531923847ba9ec 128332 hw-detect_1.103_i386.udeb fded15687f2fdb96850680d52d3ac2e646e44239 36026 ethdetect_1.103_all.udeb 99cc8e4a286f0db1498127fcb57844a455c78fd5 27600 disk-detect_1.103_all.udeb 9a095a3e91d2b2be23cd769f3299c0b8211e262a 15126 driver-injection-disk-detect_1.103_all.udeb 0ababd90be2d232af87598e9ad85c40542191ccd 2518 archdetect_1.103_i386.udeb Checksums-Sha256: d724abaf2755d1ee72c574448d314537736c5c1744cbfc0f98ad9d681420a2f1 2026 hw-detect_1.103.dsc 98f801a7b04bd042964f66535a9f6856acd3bedb82a9f8d8b691aeae6f29d6eb 179236 hw-detect_1.103.tar.xz ef1757276e097614311fec2fe2d67deffe506ee1246b1ab6f70bb93d36957182 128332 hw-detect_1.103_i386.udeb 0743b5d580457bf6993bb7bd3b1cb16d8c2f0753d5f4b98acebad78be01642c9 36026 ethdetect_1.103_all.udeb 3d19abe2b09a82987cfd99482e5b2e3845141dcf5482f5704431d1506d782104 27600 disk-detect_1.103_all.udeb 8d153d19a289e6ca2cc562dcd13d115ad26321c4c184a1272fe946abe3dc4a2e 15126 driver-injection-disk-detect_1.103_all.udeb d08275104498825cb9f8273ee69524c7dc59232149a84d7c5a4836114ca918d6 2518 archdetect_1.103_i386.udeb Files: 7474aa026baaab57b25683831b5ff428 128332 debian-installer standard hw-detect_1.103_i386.udeb 6e5d746a551553b0eb83bd47681a4520 36026 debian-installer optional ethdetect_1.103_all.udeb 76df15334a333f82f4898654a04750cf 27600 debian-installer optional disk-detect_1.103_all.udeb 0d8028a5c2e3c23608a319ea2bab199f 15126 debian-installer optional driver-injection-disk-detect_1.103_all.udeb 498a956d0906c03c2de30d4a0ae71e86 2518 debian-installer standard archdetect_1.103_i386.udeb b5f71a769ae3a93cfe0ffbb744cb951f 2026 debian-installer standard hw-detect_1.103.dsc 1e150cb6a5d2a28a74807fa7eb90a9fa 179236 debian-installer standard hw-detect_1.103.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBax2IcvcCxNbiWoAQLBhQ/+NDP9ZQ7p/+mNily5IBo7aJrjzGrjvr0L GZub/tEu/mHHx9lLQgmsLKBWDaTwSNKJSpGvs15PtjhuJaP4GDGctfyTlJoF2wUe C694l8uRQqiJWKfzQ8txjDb061bY5fph4ACLL0RbZiesaLhJBEy/Xx9d9IAScQHl GAjga6LCzj7q/gvqPw18t2l/W5FTBECOMN6YXIsbSqjL4ZB8xIIUGz94s+YdgY5g S3/+MsZWszS/Ds7HDpUnOWCk3qvPUfpm0UImSV0GllXz9sjesZnLpkJXBWPLcJNY OwgT/u5URZ8skTZ1HV0aSXaN4IOdEaz2xhumRUGAgzGMDGjksmD3XHCV/Farc1sJ OBAW9LqZ6CYUprEe2v2qzl4ND9LDsgresg8m6NXeW6SlA/yRTHCswU96QkpheDCt GIK+V/0SwjPmq46zyIWSzro+85EeonD5wXHywsdvV7bxchkboF5eLhlSxeEnpqZ6 mTKD/SlNK/K7qqV3ZZnot0T1+igVOYoTNSTUXvOwwsY2qYkOQPnFxyHa7d2jktji gI7OygTKU/MAfb6IhKqTTb8sJrhy0EZuV92RLj6ndM+Moec/hVPCOnw2fNjfSeu9 d9Ny/iZUINpTlf5CYfax1z8M5v/aBNlbVsIQmLzCPbM5Ac6U7tey5VZvKjCju57E jq+AJpV/Kj8= =FMVM -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: https://lists.debian.org/e1xtsvq-0006kf...@franck.debian.org
lvmcfg_1.35_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:27:41 +0200 Source: lvmcfg Binary: lvmcfg lvmcfg-utils Architecture: source all Version: 1.35 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: lvmcfg - Configure the Logical Volume Manager (udeb) lvmcfg-utils - lvmcfg without the main menu item (udeb) Changes: lvmcfg (1.35) unstable; urgency=low . [ Updated translations ] * Danish (da.po) by Joe Hansen Checksums-Sha1: 333ed97fb6e2b268cb5d0fb07ebe19ebbd7b72c8 1683 lvmcfg_1.35.dsc 29f79bfe932e66d335734135568b3f2d43730568 155656 lvmcfg_1.35.tar.xz 2f95bc370c18f69637c1ac388879d930c10e7608 4078 lvmcfg_1.35_all.udeb 095563b40371d8b404847d4ec362fcfbfed38346 220180 lvmcfg-utils_1.35_all.udeb Checksums-Sha256: c0b3c06f91f04606db610f8e544b2a08d8c68bab6430c79af3a00c644bc4eb82 1683 lvmcfg_1.35.dsc d36c09fcc9ec94cd75fa29b7e39672c0c84f395b474cebb28af0858c40b35495 155656 lvmcfg_1.35.tar.xz 2997bfc120873d44a74bc96589bb7524de6327945b045e134c111ecea12cbefc 4078 lvmcfg_1.35_all.udeb 9e36eaf3cf5859a8acfe9245c35a4b58e526cfb182053e0ee1d7988d713b5407 220180 lvmcfg-utils_1.35_all.udeb Files: f40726161c466d80a204935faf9b7380 4078 debian-installer optional lvmcfg_1.35_all.udeb 0b3ca57590010b4eb6a788ba8c404599 220180 debian-installer optional lvmcfg-utils_1.35_all.udeb f716fd8813f08ea1242025740773ab77 1683 debian-installer optional lvmcfg_1.35.dsc 28309687f36e717712c1b93f90fe9d3c 155656 debian-installer optional lvmcfg_1.35.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBaxwocvcCxNbiWoAQJtUQ/8DBxWrNcbuZFVyRt15xbsuF78ZRj6tEDb VOOcM3ZwWLVmpjceyfl/dngfMO5P9YTPB/M1VnfglDGH6m31IpqGgHTqlAdJvXs0 Kmsag00hURKe7mB2fTTQYcdMfNckuTZJIovLZkAhvw1knunNcXjJZtrGnh4wcRjT T1d6Zw5V8r0LZIuFHnG5zq0DYZPc8NQEZkM8N36LzxCEUbHY4UfvCCQvO9E9DOGU gTo9sjFtVHAFpWL4s6svxGLl/UChgXTBaYFEsN5Y5QAQCU5llar8L8TOnkzGaLUG 4aW9M7TUi+Vcn0gvSiTO9eyde5o7vNy2ci4nHKT0XKlNnUbRCtNJh+eMNfOR+/MH +oFFMvIZNtEY1iLxbLPzzrZY74JvIHX5DzjeGpIJc4RBZ+T86TP7IlcygvNLAy52 +cWZPMJFY8ik0t1zYGkekiJusUEIt6xPDjqiHtNwwt9qOlSkpUU0+Jd+e2olwu6u AmHMqHuJr2O00lpFiKtC4dSHqh9w29Fhb9354gS+48498+YBBkVdHHp9989gS77/ T+DrPY4nl+EGvAnbQ67/pO9S8QNhT5hBQnCoJR7jXOTWoK+LXXwpakxzJ00jwFVy u0XXGV3jrWv1HxLshesGeM9wXtYrHI//MDFeuRh5r12Xau2jhM3R2j3sL1kTnkBd 207uK01iOqE= =Q5Jg -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: https://lists.debian.org/e1xtsvw-0006oc...@franck.debian.org
grub-installer_1.97_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:32:43 +0200 Source: grub-installer Binary: grub-installer Architecture: source i386 Version: 1.97 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: grub-installer - Install GRUB on a hard disk (udeb) Changes: grub-installer (1.97) unstable; urgency=medium . [ Debian Install System Team ] [ Steven Chamberlain] * In device_to_disk, recognise /dev/ada[0-9] disk naming on kfreebsd Checksums-Sha1: e2d0ef2b982d2692b6fb113cc6813505776ffa6a 1941 grub-installer_1.97.dsc d3f08a2d018b419b0181ebb773ca842af0727281 192112 grub-installer_1.97.tar.xz c256156a26a1ab634a191fe661c69345d3d995ef 261752 grub-installer_1.97_i386.udeb Checksums-Sha256: 1f26a9ddf8f499f219948f55e0adc23db491fbf2a068ac38b69b0b08a7333020 1941 grub-installer_1.97.dsc 7c7ec39ac09fdd84c68e77228d0fc69303f91ca5f1bbd86c78dcf40171bb556f 192112 grub-installer_1.97.tar.xz f27b0abdec12d1b6abfa2fd1989619066bd0b12cc1b22a31b4b117c818848394 261752 grub-installer_1.97_i386.udeb Files: 199f02517a232e4166d4885f0ed77335 261752 debian-installer standard grub-installer_1.97_i386.udeb 073813738d71dee421f6d64a8f661f82 1941 debian-installer standard grub-installer_1.97.dsc a5180f4a513e1b330e9110a10110eace 192112 debian-installer standard grub-installer_1.97.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBa0EocvcCxNbiWoAQJ07hAAnWk9tYItJJbA7oDILMaG8VMcfLEwTQHj ho5Ovr0MW40yXMCVBZsJrPlKGzi6TMaWTPVqq3WXKPXYVQQbrJEmlhpCepr5I/bK Jj01GXyleUJB8esCKI/XWzxDztxHpOk7Tq1otmNk/AS1lKMIcVHEdOXQwDqLt0XG WaDKVOCwhml0jakfFel+uRHQr2EnQsrJIksFcIHGkeD1JedKXFF35ny9H62vO3+V EqK1Nu84zOSiIZQ0ccySSEv9KZ/wnRsBE1EEoy0YNc7T+UCygmYfh5dxRa7TwgZi aGFi/JMeiaWKmFmv22mugs74CFpsmbv22A4HyKXuOVx0bE9jq+2/DBX823TBjNEB opo1r05AIQE35/HRhAIgAAG8WpVwHVu34eM9HnpIPH0EzCwUM9HRZLaGuvTQE+XG IKMn0ghS4BgutDYhwzyyrQ6x4rZPKw7XltK8ftlIv9j+cTQA8ow6SidzUjnD4UjN as5FsNDgB1HnPEJ1sPqVhigj4WjPfnG903j8xGJ/9nDUykgOk8VYLwXIz0KKHBpe VlkaOi0DBh1YylwGEFzngSOIkMnzM0Y8ADv3XLPXltQjOXUBDrhrwkt4ou8NXl6Y 6KQpQeEjdKBYjtxacjkUH6rS9Bs8/Jj1ZJRaUUKvCWbowqBgWBeqKQ2vxnJHTwm0 Luatw8+XP6M= =6Qqt -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: https://lists.debian.org/e1xtt8r-0004hk...@franck.debian.org
mdcfg_1.47_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:33:48 +0200 Source: mdcfg Binary: mdcfg mdcfg-utils Architecture: source all Version: 1.47 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: mdcfg - Configure MD devices (udeb) mdcfg-utils - Configure MD devices (udeb) Changes: mdcfg (1.47) unstable; urgency=low . [ Updated translations ] * Danish (da.po) by Joe Hansen * Estonian (et.po) by Mattias Põldaru Checksums-Sha1: adaa3113cf84a47d0fe8f8b19eb38e0e4a843144 1648 mdcfg_1.47.dsc 707e7027eff2a616986645b6b585dfd1c6849d90 144432 mdcfg_1.47.tar.xz aa6047886baf53a36ef18d8ac0f7033ea2082301 4734 mdcfg_1.47_all.udeb 83840e091c9e4261a2ff135d5836c301b991629b 182124 mdcfg-utils_1.47_all.udeb Checksums-Sha256: ebd247c0886b688cc011cd1b5124cd4a84ddf7a35662c300bd3b25f5b8f0 1648 mdcfg_1.47.dsc f8a75b0168b444e80146b2c6b0d32aef663e739c1942a9b725e5737de1faa9a3 144432 mdcfg_1.47.tar.xz f3cc836265fad0718eb197969d0c9633f08e072b0c701b775d1023b5164b9dbc 4734 mdcfg_1.47_all.udeb 8c3ea5bffa45b7cd07e439aea133eb09d013e2d798d71bb0aab0174471fc607f 182124 mdcfg-utils_1.47_all.udeb Files: 849144e76b543655b535521308f77b5d 4734 debian-installer optional mdcfg_1.47_all.udeb 855c2b580775793757af9711a49aa121 182124 debian-installer optional mdcfg-utils_1.47_all.udeb 3977c8c8518f29ab9741a6e791061dd7 1648 debian-installer optional mdcfg_1.47.dsc 286d2dd1b65ae6c0eab7434f3e605d14 144432 debian-installer optional mdcfg_1.47.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBa0OYcvcCxNbiWoAQJiFQ//Qy3EgaBI1uq9hPrtkeyfq1xPdtMh0XgQ Md77jht5bznjpeiXxWoOEqWevG8a6cJw0ZJt/bB2Oi4qHnuI+Tfe9yifZHrPT7wi GXJAulvUDA9DdIf9GdDhua7l5l+Th5Ittt//BBL3mXh5Bc4e2V0QVKN/7JO5K8pR klUjCbTIiXk81Rfvu7oWYmiLTIVlbm2LjXPRtNodpsRRelZIYBxRN2VbyqR5O+yd Pwm4GpXYp960j4PSGfTh0vqvGur8HM8AzpdzUiasTAvGQ2bedP9mT4brGnJgXjDZ nX3wTjzlixnn5YBcGgr8zDNf8Lp7IDm7yXSH2cyEga0QlYWOSzMMZzcZD7lgY50L 3fQF6dxQN2yoYqyln6dFU7sG055MRHDE3vWyRpB4KjxAkcxuiIHaU+nCyl4d26Sm ygsMlZlKBUFBoqOXTzER2JZyW5vDcarm6XtBE8olyFQWRZN+sb6MzKBb6FuZxbnU 5LJG92aLsCPycHTn+jajOlWfpnWx24d2nMcNfhdOf1brHqUUjhegFp+zAQXDJgMa Zypj2Yx4diMevGV4k2UxOaTQndDJKFPeSF1M3LQgwm7LE1SiZg1Kd4rjGIEAkoPF xnXFJ4G6qxLHus3FDegIL1U1lrCspXQZLz/LGdvvu8slg4wi8+vHwUzObpplr9F6 leteFKf2+QQ= =57sw -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: https://lists.debian.org/e1xtt8y-0004lc...@franck.debian.org
Processing of finish-install_2.50_amd64.changes
finish-install_2.50_amd64.changes uploaded successfully to localhost along with the files: finish-install_2.50_all.udeb finish-install_2.50.dsc finish-install_2.50.tar.xz 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: https://lists.debian.org/e1xtt9r-0005ft...@franck.debian.org
finish-install_2.50_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Sep 2014 11:59:33 +0200 Source: finish-install Binary: finish-install Architecture: source all Version: 2.50 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: finish-install - Finish the installation and reboot (udeb) Changes: finish-install (2.50) unstable; urgency=medium . * Team upload * finish-install.d/07speakup: Enable accessibility in LXDE, MATE and Cinnamon sessions too. Checksums-Sha1: 556b3503e8a8ad0e72a4c0281ddcca35bdd326e8 1624 finish-install_2.50.dsc f015f7dd2cb50a4ed2dd27daf92ec1358e062a8d 52872 finish-install_2.50.tar.xz e28b0d16a5d8a7082941a512bc9889e5f2685e7c 29662 finish-install_2.50_all.udeb Checksums-Sha256: 8ebbdbe2d0950bcf7cc9738446c2048573d62d8908755db948636903faf86ed0 1624 finish-install_2.50.dsc 437e427ccc50a19746184c009dce5b37d1cc5e2cf28b9cb37c11c635cb3e711c 52872 finish-install_2.50.tar.xz 72c45b097efb600181e82afc9a8423736d0eb72b3efe2b5e7484c0ca3c9a33c2 29662 finish-install_2.50_all.udeb Files: e7c488af61079ba316479b8e191d00a5 29662 debian-installer required finish-install_2.50_all.udeb 50323d7c7e8f41869dbd2af54cc9be23 1624 debian-installer required finish-install_2.50.dsc edf9b3787b3a90227670bfb9f721272c 52872 debian-installer required finish-install_2.50.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUFrkRAAoJEBH0lP5vGG7NTKcP/iHteDhl7+YsYrYM6SsJoWTa 7yJCUHKA5L1VELSk6aG0btEsuMi+K7IA3iEHop+HLXhe0YgC18zUksYByuT4wymu 8ShiU7X+flxuraTBL8vZKMYltg1iJMAMuigfl5RsFxCVubhLGNfohrxJckUIvbdM DrIQ2aJHQxQGLAE2hYZxqNLhbAzfhoufN5D8G/uNb4tQRROnRPMBB6x5pwL8f/b0 Oec8cAWMmWErihCSLfD974Hb22SUowBVClHZNQNFBvLKlXT/zKvI5j9viZHPam1s azBJ682SjZuWCzqy4hDVoZLIJeKn1piks+IRnJPSpPjSextX5NrxgijaEnfVTyh+ 3tftU5mRzO8TchqRqg0XP3eHw6X9HxKzHC4p5jQw5DHQYlYOH8oybZDIoAU+5L4a DW7kxvN23L2IuST7xMvoY2zwX8XiCJ7JVjZstVCU9/zPL1soHWKyY0oB0a2WDFZg NCpYlFEgaQ7BVPyUkeefcIzuOXIGvCk20mB7o4aHkyFRSdqTTPgiL0gursgYhFZu yky14lDFWP9fJ1JGCILy8vT0CU6Ia5UA59GsAXdVfF/TkVwa7Cm0EwHv1CcVvQXD 4yhiKkdpV0Ywx38ux0aLd8n+91e+WmKDUkTBZ0sB+eotYIg2tGcuyrTFEj8TVJKX 8OgI8yEGPDPWREcjTE14 =vpfB -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: https://lists.debian.org/e1xttnh-0002ci...@franck.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
On 15/09/14 08:36, Petter Reinholdtsen wrote: [Samuel Thibault] I have attached the syslog, interestingly: Aug 26 00:10:17 grub-installer: info: Installing grub on '' Yes, I suspect that is a typo in the script somewhere, failing to set the default. partman succeed in picking a good default, perhaps grub-installer can use the same logic? FWIW I've been looking into this issue already in the past few days. At this point I'd say Petter's patch shouldn't be necessary, because the intent was for the 'list' dialog to have an entry pre-selected (or not show that dialog at all). That only works sometimes (e.g. PXE), but in other cases (including CD-ROM) it appears grub-installer correctly guessed the boot device (based on filesystem containing /boot) and just didn't pre-select it in the dialog. That causes the regression in auto preseed installs. I suggest to actually remove this dialog now: Install the GRUB boot loader to the master boot record? Go Back Yes No because it doesn't make it clear which device we're actually installing to. If our guess was wrong, we want to give the user a chance to correct it. The new dialog can serve the same purpose and is more informative: Device for boot loader installation: [ ] Enter device manually [o] /dev/sda (ata-QEMU_HARDDISK_QM1) Go Back How do people feel about me making such a change? I think it will make the real bug (that we sometimes don't pre-select an option in that dialog despite having a good guess) easier for everyone to see. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5416c34a.1000...@pyro.eu.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Steven Chamberlain ste...@pyro.eu.org (2014-09-15): On 15/09/14 08:36, Petter Reinholdtsen wrote: [Samuel Thibault] I have attached the syslog, interestingly: Aug 26 00:10:17 grub-installer: info: Installing grub on '' Yes, I suspect that is a typo in the script somewhere, failing to set the default. partman succeed in picking a good default, perhaps grub-installer can use the same logic? FWIW I've been looking into this issue already in the past few days. At this point I'd say Petter's patch shouldn't be necessary, because the intent was for the 'list' dialog to have an entry pre-selected (or not show that dialog at all). That only works sometimes (e.g. PXE), but in other cases (including CD-ROM) it appears grub-installer correctly guessed the boot device (based on filesystem containing /boot) and just didn't pre-select it in the dialog. That causes the regression in auto preseed installs. I suggest to actually remove this dialog now: Install the GRUB boot loader to the master boot record? Go Back Yes No because it doesn't make it clear which device we're actually installing to. Errr, it doesn't have to. It's about *whether* touching the/a MBR is desired. If our guess was wrong, we want to give the user a chance to correct it. The new dialog can serve the same purpose and is more informative: Device for boot loader installation: [ ] Enter device manually [o] /dev/sda (ata-QEMU_HARDDISK_QM1) Go Back How do people feel about me making such a change? I think it will make the real bug (that we sometimes don't pre-select an option in that dialog despite having a good guess) easier for everyone to see. I still disagree with the good guess assessment! Repeating that over and over and over and over again is *not* going to make it true. Touching other prompts doesn't look like a safe, or welcome, or proper change to me. KiBi. signature.asc Description: Digital signature
Re: Installation manual upload?
Karsten Merker, le Sun 14 Sep 2014 20:37:12 +0200, a écrit : On Sun, Sep 14, 2014 at 07:13:33PM +0200, Cyril Brulebois wrote: last manual upload was 20131009 which is a while ago. Since we're closing in for a Jessie Beta 2 release, it'd be nice to have current svn uploaded soon. I'm not sure whether some translations are pending though. I currently have some small uncommitted changes to the english manual in my local working tree. Is it ok to do further commits for now or should I postpone them until after the package has been uploaded? If the changes are indeed small, it's probably better for non-english people to have the old, but translated, documentation, rather than having the new but untranslated documentation. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140915112824.ge3...@type.bordeaux.inria.fr
Re: Installation manual upload?
Cyril Brulebois, le Sun 14 Sep 2014 19:13:33 +0200, a écrit : last manual upload was 20131009 which is a while ago. Since we're closing in for a Jessie Beta 2 release, it'd be nice to have current svn uploaded soon. I'm not sure whether some translations are pending though. Christian, what do you think? Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140915114318.gg3...@type.bordeaux.inria.fr
Re: Installation manual upload?
Le 15/09/2014 13:43, Samuel Thibault a écrit : Cyril Brulebois, le Sun 14 Sep 2014 19:13:33 +0200, a écrit : last manual upload was 20131009 which is a while ago. Since we're closing in for a Jessie Beta 2 release, it'd be nice to have current svn uploaded soon. I'm not sure whether some translations are pending though. Christian, what do you think? Samuel ** CRM114 Whitelisted by: From: Samuel Thibault sthiba...@debian.org ** There will always be pending translations.Helge did, IIRC, some calls for translations but, anyway, an upload now doesn't prevent us to do another upload later on. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5416d2e7.8040...@debian.org
Bug#740589: Complains it cannot find device
Hello Kibi, I hit this bug too from time to time on VM creation (using PXE+preseed). It seems to be timer related. I don't know if this is with too fast disk or too slow disks. How can I increase the loglevel? Regards -- Mathieu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cafx5sbzrhzgiiq0gtukqapw8t1rxa53fqn7j+sud6-wsagf...@mail.gmail.com
Bug#760712: WEP vs WPA2
Cyril Brulebois k...@debian.org (2014-09-14): So, putting my laptop installation aside, and concentrating on a VM using KVM with USB pass-through to a USB adapter (USB ID is 0bda:8176, that's RTL8188CUS), I've been able to verify (assuming firmwares have been made available every time): - wheezy amd64 works with WPA (TKIP) and WPA2 (AES) [ sharing network over a Firefox OS phone with those denominations. ] - wheezy amd64 works with WPA2-PSK/AES [ as advertised by my home router ] - sid amd64 doesn't work with any of those, even if I build an image with wheezy's netcfg and/or wheezy's wpasupplicant-udeb. I've also verified that installing over a wired connection lets me configure wpa_supplicant and connect to wireless from within the same VM, so there's definitely something fishy within d-i, even if I don't know what yet. Anyway, that doesn't allow me to conclude on the “WEP might be OK” topic, but various WPA setups are clearly broken. Let's see whether I can get that debugged further tomorrow. With some flexible value of tomorrow, it seems I can conclude the problem is rather on the kernel side than on the userland side. It isn't too surprising since I had already tested downgrading netcfg and wpa to wheezy's versions, and that didn't help. My cross tests were done using: - wheezy or sid as a basis times: - 3.2 or 3.16 linux udebs building a netboot-gtk image in the appropriate chroot (wheezy or sid). I also included all the firmware files included in the firmware-realtek package from wheezy (for 3.2) or from sid (for 3.16) to take that out of the picture. End results: - wheezy and sid with 3.2 work - wheezy and sid with 3.16 don't work (card recognized, scanning OK but association KO). I've also checked that installing sid + 3.16 over Ethernet then manually connecting (wpa_passphrase then wpa_supplicant) worked just fine (that's been mentioned in my previous mail, but confirming). I'll now try and compare dmesg from within d-i and from the installed system to see whether I can spot some differences which could help me understand what the differences are, and possibly ask kernel maintainers for help/insight. Mraw, KiBi. signature.asc Description: Digital signature
Processing of debootstrap_1.0.62_i386.changes
debootstrap_1.0.62_i386.changes uploaded successfully to ftp-master.debian.org along with the files: debootstrap_1.0.62_all.deb debootstrap-udeb_1.0.62_all.udeb debootstrap_1.0.62.dsc debootstrap_1.0.62.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtzub-0007hv...@coccia.debian.org
Processing of media-retriever_1.35_i386.changes
media-retriever_1.35_i386.changes uploaded successfully to ftp-master.debian.org along with the files: media-retriever_1.35_all.udeb load-media_1.35_all.udeb media-retriever_1.35.dsc media-retriever_1.35.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xtzuf-0007hb...@coccia.debian.org
Processing of debootstrap_1.0.62_i386.changes
debootstrap_1.0.62_i386.changes uploaded successfully to localhost along with the files: debootstrap_1.0.62_all.deb debootstrap-udeb_1.0.62_all.udeb debootstrap_1.0.62.dsc debootstrap_1.0.62.tar.xz 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: https://lists.debian.org/e1xtzyp-00010o...@franck.debian.org
Processing of media-retriever_1.35_i386.changes
media-retriever_1.35_i386.changes uploaded successfully to localhost along with the files: media-retriever_1.35_all.udeb load-media_1.35_all.udeb media-retriever_1.35.dsc media-retriever_1.35.tar.xz 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: https://lists.debian.org/e1xtzyp-00010x...@franck.debian.org
Bug#757819: qemu-debootstrap can't handle Pre-Depends
Control: retitle -1 qemu-debootstrap can't handle Pre-Depends As the error message suggests, this is due to debootstrap trying to unpack something before configuring its Pre-Depends. #487908 was the same problem on the native architecture, which was fixed by the code at scripts/sid:174-185 and functions:1284-1288. A possible hint as to why this fix doesn't work here is this part of the log, suggesting they aren't being added to the dpkg database before calling dpkg --predep-package (which needs to know what we want to install to be of any use): Setting up init (1.21) ... Processing triggers for libc-bin (2.19-11) ... dpkg: warning: package not in database at line 98: apt [...same for everything else in the base-but-not-required list...] dpkg: warning: found unknown packages; this might mean the available database is outdated, and needs to be updated through a frontend method Selecting previously unselected package apt. (Reading database ... 6884 files and directories currently installed.) Preparing to unpack .../archives/apt_1.0.8_s390x.deb ... Unpacking apt (1.0.8) ... I don't know why this isn't happening, or whether it might cause any other problems. An (untested) way to fix this bug without needing it would be to put the unpack and configure steps in a single retry loop (instead of the two separate retry loops at scripts/sid:187-197), allowing Pre-Depends to be dealt with the same way as ordinary Depends, i.e. run through the list repeatedly until everything gets done. Priority:required packages and their dependencies can't trigger this because they are installed with --force-depends; this now (since init 1.21) includes systemd, so it no longer triggers this bug, but a plain (not buildd) debootstrap of s390x still does, as s390-tools Depends on gawk which Pre-Depends on libgmp10. (A workaround would be to simply --exclude s390-tools, as its description suggests it isn't needed in a qemu-user environment.) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541720e6.8000...@zoho.com
Bug#760712: WEP vs WPA2
[ Executive summary: WPA works fine in d-i with 3.2, but not with newer kernels, like 3.16; and userland doesn't seem to be the obvious culprit. ] Cyril Brulebois k...@debian.org (2014-09-15): So, putting my laptop installation aside, and concentrating on a VM using KVM with USB pass-through to a USB adapter (USB ID is 0bda:8176, that's RTL8188CUS), I've been able to verify (assuming firmwares have been made available every time): - wheezy amd64 works with WPA (TKIP) and WPA2 (AES) [ sharing network over a Firefox OS phone with those denominations. ] - wheezy amd64 works with WPA2-PSK/AES [ as advertised by my home router ] - sid amd64 doesn't work with any of those, even if I build an image with wheezy's netcfg and/or wheezy's wpasupplicant-udeb. I've also checked that installing sid + 3.16 over Ethernet then manually connecting (wpa_passphrase then wpa_supplicant) worked just fine (that's been mentioned in my previous mail, but confirming). I'll now try and compare dmesg from within d-i and from the installed system to see whether I can spot some differences which could help me understand what the differences are, and possibly ask kernel maintainers for help/insight. So I've created a bare wpa.conf using wpa_passphrase foo bar (matching my wireless setup) and tried to use it within d-i and outside, with: wpa_supplicant -c wpa.conf -i wlan0 Outside d-i I'm getting: ioctl[SIOCSIWFREQ]: Device or resource busy wlan0: Associating request to the driver failed wlan0: Associated with [mac address] wlan0: WPA: Key negotiation completed with [mac address] while within d-i I'm getting: ioctl[SIOCSIWFREQ]: Device or resource busy wlan0: Associating request to the driver failed wlan0: Associated with [mac address] ioctl[SIOCSIWENCODEEXT]: No such file or directory wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=[mac address]) Looking at wpa source code I see something that could explain why WEP still works while WPA doesn't: ,---[ src/drivers/driver_wext.c ]--- | /** | * wpa_driver_wext_set_key - Configure encryption key […] | * This function uses SIOCSIWENCODEEXT by default, but tries to use | * SIOCSIWENCODE if the extended ioctl fails when configuring a WEP key. | */ `--- Now, I guess the [n,w]ext step is figuring out why SIOCSIWENCODEEXT fails within d-i. debian-kernel@, any idea? Looking around, I've seen reports about crypto-related stuff like aes that could be missing? Maybe crypto-modules should get more stuff in? Trying to verify this particular option, I'm a bit astonished by CRYPTO_AES, which is advertised as =m in linux's sources, as well as in the generated debian/build/config.amd64_none_amd64 but advertised as =y in the resulting binary package I have installed (at least according to /boot/config-3.16-1-amd64). But looking at vmlinuz in the following packages, both look identical… linux-image-3.16-1-amd64_3.16.2-3_amd64.deb kernel-image-3.16-1-amd64-di_3.16.2-3_amd64.udeb so that might be something different anyway. Mraw, KiBi. signature.asc Description: Digital signature
Processed: qemu-debootstrap can't handle Pre-Depends
Processing control commands: retitle -1 qemu-debootstrap can't handle Pre-Depends Bug #757819 [debootstrap] qemu-debootstrap fails on systemd-sysv issue Changed Bug title to 'qemu-debootstrap can't handle Pre-Depends' from 'qemu-debootstrap fails on systemd-sysv issue' -- 757819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757819 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: https://lists.debian.org/handler.s.b757819.141080190812475.transcr...@bugs.debian.org
debootstrap_1.0.62_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:40:54 +0200 Source: debootstrap Binary: debootstrap debootstrap-udeb Architecture: source all Version: 1.0.62 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: debootstrap - Bootstrap a basic Debian system debootstrap-udeb - Bootstrap the Debian system (udeb) Changes: debootstrap (1.0.62) unstable; urgency=medium . [ Cyril Brulebois ] * Fix reporting of package version in retrieval and validation steps to cope with epochs. Checksums-Sha1: 90f79e115c693ee342751109050b891705ee3e0c 1812 debootstrap_1.0.62.dsc 825e8df4e48a4d55dd2a3a43ba9c92273ae7e2df 50040 debootstrap_1.0.62.tar.xz 6d22cf38172f0bdd20a8b93204cdb3bcdea3b944 56780 debootstrap_1.0.62_all.deb 4bce08c7d0c23d85ee5cc4c10faa57584aee480d 18244 debootstrap-udeb_1.0.62_all.udeb Checksums-Sha256: 0ec8f8ca71661c9da98186ee5181fbe2dfe69c84413d2df12fd2fd6f3b310ad8 1812 debootstrap_1.0.62.dsc 476d14f048b0c05e0ad02e8b9dd913a02883dad9a8b7080f5be8b9228f35622b 50040 debootstrap_1.0.62.tar.xz 98b35842ca2d0e8fddc821904aa07b95f70c40ff8c4c36751290f1abfd676fc0 56780 debootstrap_1.0.62_all.deb e10b2ef5d7524516409bcd7a40a1806cb0a5494e8ab5547c13826e5a6a50e8b6 18244 debootstrap-udeb_1.0.62_all.udeb Files: a6b7d34b38cb959e6bec34b08ca567f2 56780 admin extra debootstrap_1.0.62_all.deb 8115691c54e384534fcd617750f7bc4e 18244 debian-installer extra debootstrap-udeb_1.0.62_all.udeb acbc80d2bdc5ae25066cd759649fe1e3 1812 admin extra debootstrap_1.0.62.dsc a4b16d7f8d4a3e387b420e7ec47b56b6 50040 admin extra debootstrap_1.0.62.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBceRocvcCxNbiWoAQLI9Q//V2b7df18loUuJ92tsYO2/rcWMmtWAZqV 2zvRTR+iQXqzRrynFAjauiBGN5iskhCfKGVNtGEsdldjFMjq3AtxD2xy3lXeiJ2C Fbi3/rArcpj4AKIpCwpz08kD6DlhokB1O4QlyKW6h2CSFf2GfhzUHIm89IvFT8PL BDDhlY7vO4ioxaYWIoiL8S6rNC28hFITFfBk+gMcN4hHJ9XjgGAOjzU4LxlMhRQD nQqveEUu7GRwUwy6b/C3hFfl5QzETkcd5FIvFcHKz88OuKpYKV7q27wBrH2tMUBg X2URPJlgSLdqz8EZcnpgKkHzAlnNGqzFr9YGoV/ZchD14hEEjTiA83WtnrZVAAm9 +Ls6v5SVGf1V5kuhbW/uUZ3BgwFN6e9v2NP5aMRCD/0Yb/qoKBvAOel2LkKd1mL4 oNhu0J78CgUvqowT/0uYcp1A/3E4LJ3tPBuG6m/y9dtshbPWfmjTpobHIWk+Cuws X7NEds53gr+Oukv08rAT4Mvunpmf8Nk6c1EMTAVuAerppgsGaIlFnsgIOm6mYjQN o22Aj+LmqsDzspyHUHkdC7l42laNg0r7D9UqFXQ/VMJRY8oLfCKbhV3yOQ36rr9h 5gBBPbNG/z0n7Z6OWpY2KzYiYgHKFpGZhv4CnKdvkC/2DRWqcdsita9jnkDTKzen tCoVFIcfLtQ= =ZtJ7 -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: https://lists.debian.org/e1xta9d-00025a...@franck.debian.org
media-retriever_1.35_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2014 11:42:32 +0200 Source: media-retriever Binary: media-retriever load-media Architecture: source all Version: 1.35 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: load-media - Load installer components from removable media (udeb) media-retriever - Fetches modules from removable media (udeb) Changes: media-retriever (1.35) unstable; urgency=low . [ Updated translations ] * German (de.po) by Holger Wansing * Estonian (et.po) by Mattias Põldaru Checksums-Sha1: b5dbde99b6821b90704749d9b13a23a1157babeb 1741 media-retriever_1.35.dsc a1e6b5a6aa0c8cb4c2aa8ccc130219cac92513cb 69852 media-retriever_1.35.tar.xz 310713409994058414e0e4e66491722c8c732b9c 17582 media-retriever_1.35_all.udeb f4e0996e71eaba49e43cfdf00eaab5c80ccf3490 54326 load-media_1.35_all.udeb Checksums-Sha256: fe45ded158ff68a393b777c3fa1dded064242b0b5116599337d87079b750ea4a 1741 media-retriever_1.35.dsc 8722a3a3087b2863c575b58735c881680e5acee842adc4192184cdd9bfcda587 69852 media-retriever_1.35.tar.xz a248bef51968d9f7f89af668784b860368931d37f99ed1abcf9ee561b06d426d 17582 media-retriever_1.35_all.udeb 28bece2eccde2292751ea43912d1a611840c657153b18f9cee70fd6ca20b504c 54326 load-media_1.35_all.udeb Files: 1cc79ad753725b39c0c05659317ee6da 17582 debian-installer optional media-retriever_1.35_all.udeb 72f51a55836b2675911c57d67fb73dfe 54326 debian-installer extra load-media_1.35_all.udeb a9060b2e2dd0df4f65ff5a9c03b5f247 1741 debian-installer optional media-retriever_1.35.dsc 524cc403e9c9f714775dce739d31a93a 69852 debian-installer optional media-retriever_1.35.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVBceZ4cvcCxNbiWoAQLUyA//V+PzhNsJVUHB2xfu77tdiI2pCU5jEtNG yJZP24wjCPGmEawW4KaaRqLqwppVKVEpYwBWCjRPgGcHvykfFj4zo61+9cJ+kcq+ ikPYjoSZzIrVFkVjdYD3lcsQ3P35/HJKhLi196I9EHtRdFHXdqqw78Ac1TepAHBQ RVIHfos1+KugeY4AUjqIN5qedjS6z7y/AeAyIQUuEaw9HajMZViw8PA74t4APYsx W/lb+YsDlDKaBvDQrIe+ezQ1uIEjTXLU+FmIlarT4pOWNfy4YeCgY2yrCfcnOzfF 3jMnQb46sWE8OoDYyXgVn3Y6ls2zFhz8gFrMz5QNSq/+L3QexCaRyV+OCQU9rp0C 4vmci49j6FF35baMgqaGrVCVxrW1Pqz4a7STAxfUcgInb1atpVqsXThLanPNe6W+ hyCUz5C3xZyycx/1xJVIvU7qf1puswiL1yYHZT0nYGBU2KffHO+vWZYVMbbBvr/D RCJU6bHQFI5KvhC0ik+MPWdARGbHINFvgSObGLKIbqXfPrc7G+x/xKZ3TE9f3j6c 8NAMBkczOU1trHigwatMn65ZwSlp7CyFahuW8QDEU5IbDdd/6Vab/g1wVKqGj2q5 zrtC3SqBDBLQ3UM17QQYy7ujASTWdz9witeYVqJooC9rYDDETI7zYH4pJyXN62Ew VpwmBvdnnZg= =5WaL -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: https://lists.debian.org/e1xtaa0-0002bc...@franck.debian.org
Bug#760712: WEP vs WPA2
Hi
On Monday 15 September 2014, Cyril Brulebois wrote:
[ Executive summary: WPA works fine in d-i with 3.2, but not with newer
kernels, like 3.16; and userland doesn't seem to be the obvious
culprit. ]
Cyril Brulebois k...@debian.org (2014-09-15):
[...]
while within d-i I'm getting:
ioctl[SIOCSIWFREQ]: Device or resource busy
wlan0: Associating request to the driver failed
wlan0: Associated with [mac address]
ioctl[SIOCSIWENCODEEXT]: No such file or directory
The ioctl failure is because netcfg still (only) uses the deprecated
wireless-tools/ wext driver API with wpa_supplicant, even for mac80211
based drivers. While cfg80211 implements a wext compatibility layer,
it's strongly discouraged for modern drivers in favour of mac80211's
native nl80211 access method. wpa = 1.0~, unless forced by the user
(-D{nl80211,wext}), always prefers nl80211, if the driver supports it,
but netcfg can't configure it.
While the Documentation/feature-removal-schedule.txt files has been
removed from kernel = 3.8~ for procedural reasons (constant merge
conflicts for Linus), its stanza for CONFIG_CFG80211_WEXT is still
correct[1]:
What: CONFIG_CFG80211_WEXT
When: as soon as distributions ship new wireless tools, ie. wpa_supplicant 1.0
and NetworkManager/connman/etc. that are able to use nl80211
Why:Wireless extensions are deprecated, and userland tools are moving to
using nl80211. New drivers are no longer using wireless extensions,
and while there might still be old drivers, both new drivers and new
userland no longer needs them and they can't be used for an feature
developed in the past couple of years. As such, compatibility with
wireless extensions in new drivers will be removed.
Who:Johannes Berg johan...@sipsolutions.net
Of course basic wext operations are still supposed to work at the
moment, but it's not tested or debugged anymore (and likely to be
removed alltogether, once anyone sees a larger bug in it)- and almost
certain to fail beyond the most simple use cases. Unfortunately legacy
drivers like ipw2100/ ipw2200 (see [2] for a list, probably ipw2[12]00
is the only still relevant from that list) and most staging wlan
drivers (although some newer RealTek drivers implement a non-mac80211
based nl80211 API) can only be configured/ used via wext.
This is why Kel originally suggested to (ab-)use wpa_supplicant for
scanning from netcfg (which prefers nl80211, but can fall back to wext
where needed[3]), alternative ways that allow native scanning for
nl80211 and wext would be OpenWrt's iwinfo[4].
wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=[mac
address])
This bug is unrelated to the ioctl warning above, but is likely caused
by some missing kernel modules in the kernel udebs which are needed to
enable wpa for your wlan card. Which wlan cards (well, which kernel
module) are you using for testing? I see that the original submitter
uses Atheros AR9485 == ath9k, which
Looking at wpa source code I see something that could explain why WEP
still works while WPA doesn't:
,---[ src/drivers/driver_wext.c ]---
| /**
| * wpa_driver_wext_set_key - Configure encryption key
[…]
| * This function uses SIOCSIWENCODEEXT by default, but tries to use
| * SIOCSIWENCODE if the extended ioctl fails when configuring a WEP key.
| */
`---
Now, I guess the [n,w]ext step is figuring out why SIOCSIWENCODEEXT fails
within d-i.
As mentioned above, the ioctl warning only happens because netcfg
forces wpa_supplicant into wext mode, rather than allowing it to prefer
nl80211 (like it does on a full install). A simple test for this would
be configuring /etc/network/interface on an installed system by forcing
nl80211 or wext for comparison (see [5] for documentation of the
ifupdown hooks):
# Connect to access point of ssid 'homezone' with an encryption type of
# WPA-PSK/WPA2-PSK, using the 'wext' driver backend of wpa_supplicant.
# The psk is given as an encoded hexadecimal string. DHCP is used to obtain
# a network address.
#
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
Just change wpa-driver from wext to nl80211 (or don't set this option
at all), to switch between wext or nl80211 mode on an installed system.
debian-kernel@, any idea?
Looking around, I've seen reports about crypto-related stuff like aes
that could be missing? Maybe crypto-modules should get more stuff in?
Trying to verify this particular option, I'm a bit astonished by
CRYPTO_AES, which is advertised as =m in linux's sources, as well as in
the generated debian/build/config.amd64_none_amd64 but advertised as =y
in the resulting binary package I have installed (at least according to
/boot/config-3.16-1-amd64). But looking at vmlinuz in the following
Bug#760712: WEP vs WPA2
Hi,
Stefan Lippers-Hollmann s@gmx.de (2014-09-15):
The ioctl failure is because netcfg still (only) uses the deprecated
wireless-tools/ wext driver API with wpa_supplicant, even for mac80211
based drivers. While cfg80211 implements a wext compatibility layer,
it's strongly discouraged for modern drivers in favour of mac80211's
native nl80211 access method. wpa = 1.0~, unless forced by the user
(-D{nl80211,wext}), always prefers nl80211, if the driver supports it,
but netcfg can't configure it.
While the Documentation/feature-removal-schedule.txt files has been
removed from kernel = 3.8~ for procedural reasons (constant merge
conflicts for Linus), its stanza for CONFIG_CFG80211_WEXT is still
correct[1]:
What: CONFIG_CFG80211_WEXT
When: as soon as distributions ship new wireless tools, ie. wpa_supplicant 1.0
and NetworkManager/connman/etc. that are able to use nl80211
Why: Wireless extensions are deprecated, and userland tools are moving to
using nl80211. New drivers are no longer using wireless extensions,
and while there might still be old drivers, both new drivers and new
userland no longer needs them and they can't be used for an feature
developed in the past couple of years. As such, compatibility with
wireless extensions in new drivers will be removed.
Who: Johannes Berg johan...@sipsolutions.net
Of course basic wext operations are still supposed to work at the
moment, but it's not tested or debugged anymore (and likely to be
removed alltogether, once anyone sees a larger bug in it)- and almost
certain to fail beyond the most simple use cases. Unfortunately legacy
drivers like ipw2100/ ipw2200 (see [2] for a list, probably ipw2[12]00
is the only still relevant from that list) and most staging wlan
drivers (although some newer RealTek drivers implement a non-mac80211
based nl80211 API) can only be configured/ used via wext.
This is why Kel originally suggested to (ab-)use wpa_supplicant for
scanning from netcfg (which prefers nl80211, but can fall back to wext
where needed[3]), alternative ways that allow native scanning for
nl80211 and wext would be OpenWrt's iwinfo[4].
thanks for the background!
wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=[mac
address])
This bug is unrelated to the ioctl warning above, but is likely caused
by some missing kernel modules in the kernel udebs which are needed to
enable wpa for your wlan card. Which wlan cards (well, which kernel
module) are you using for testing? I see that the original submitter
uses Atheros AR9485 == ath9k, which
I'm using rtl8192cu.
As mentioned above, the ioctl warning only happens because netcfg
forces wpa_supplicant into wext mode, rather than allowing it to prefer
nl80211 (like it does on a full install). A simple test for this would
be configuring /etc/network/interface on an installed system by forcing
nl80211 or wext for comparison (see [5] for documentation of the
ifupdown hooks):
# Connect to access point of ssid 'homezone' with an encryption type of
# WPA-PSK/WPA2-PSK, using the 'wext' driver backend of wpa_supplicant.
# The psk is given as an encoded hexadecimal string. DHCP is used to obtain
# a network address.
#
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk
000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
Just change wpa-driver from wext to nl80211 (or don't set this option
at all), to switch between wext or nl80211 mode on an installed system.
Well I'm actually starting wpa_supplicant manually, using:
wpa_supplicant -i wlan0 -c wpa.conf
with wpa.conf generated with wpa_passphrase, contents being:
| network={
| ssid=my ssid
| #psk=ascii version
| psk=hexaversion
| }
so I'm not forcing anything.
For reference, I'm attaching wpa-ko.log (within d-i) and wpa-ok.log
(installed system). I've performed s/wlan0/wlan1/ in one of them because
udev persistent naming etc. For both I added the “-dd” flag to the
command given above.
Based on your answer, I'm wondering whether there might be some CONFIG_*
differences between wpasupplicant and its udeb, which might explain?
This is less of a configuration (as in kernel .config) problem, but
more likely to be caused by some (newly) required kernel modules
providing the functionality for wpa modes missing from the udebs for
d-i.
Taking a simple mac80211 based wlan card (ar5523, USB) as example,
forced into wext mode mode, I see these wireless modules as required
for wpa2-psk/ ccmp - this is not using the Debian kernel, which might
be slightly less modular:
plugging in ar5523, unconfigured:
+ arc4
+ ar5523 (well, this is the particular module only require for ar5523)
+ mac80211
+ cfg80211
+ rfkill
after starting wpa_supplicant in (forced) wext mode:
+ ctr
+ ccm
+ af_packet
Bug#760712: WEP vs WPA2
Cyril Brulebois k...@debian.org (2014-09-15): I'm using rtl8192cu. (In case anyone cares: USB ID is 0bda:8176.) […] Depending on your particular wlan card and how its driver is divided into sub-modules (or how well it is integrated into other kernel subsystems), you might need additional modules as well. ACK, I'll check lsmod output differences. Checking output before/after wpa_supplicant -Dwext on the installed system, I saw ctr and ccm reference count changed. I've copied them into d-i and after a few modprobes I managed to get networking with the same commands as before: wpa_supplicant -i wlan0 -c wpa.conf udhcpc -i wlan0 Ben, I guess it might make sense to add those to crypto-modules? Not sure how feasible it would be to figure out which other ones might be interesting for other wireless modules though… → I can open a bug against src:linux to keep track of it. Well currently, as far as I can see/test, WPA support in d-i isn't exactly working nicely, so I don't think a wpa upload is going to hurt much. Quite the contrary, hopefully. Ben mentioned on IRC: CONFIG_DEBUG_SYSLOG=y which might be helpful for the udeb. Adding this option on top of sid's wpasupplicant-udeb isn't sufficient, since one also needs adding the -s flag to netcfg's execlp call. Once both udebs have been modified, wpasupplicant lines end up in syslog, which is definitely helpful. → That should probably become 2 extra bug reports (src:wpa, src:netcfg). Beware of the order: passing -s without CONFIG_DEBUG_SYSLOG=y means getting an error and usage in syslog, so netcfg should only be patched when wpa is ready. Once we get there, it might make sense to pass (or make it possible to pass) at least -d to wpa_supplicant. → An extra bug report for netcfg. Mraw, KiBi. signature.asc Description: Digital signature
Build failure with French translation update
Hi, it looks like r69322 broke the build: | - creating bookinfo.xml | Info: generation of XML files complete | Language: fr | Updating PO files for language 'fr': | - updating post-install.po | ./po/fr/post-install.po:704: missing 'msgstr' section | ./po/fr/post-install.po:710:14: syntax error → trailing ';' got added apparently. | msgmerge: found 2 fatal errors | Error: error 1 while executing msgmerge […] | - updating preseed.po | ./po/fr/preseed.po:1774: end-of-line within string | msgmerge: found 1 fatal error | Error: error 1 while executing msgmerge → some kind of word wrapping in your editor might have triggered this? It'd be nice if you could double check and commit a fix; thanks! Mraw, KiBi. signature.asc Description: Digital signature
Bug#760712: WEP vs WPA2
Hi On Monday 15 September 2014, Cyril Brulebois wrote: Stefan Lippers-Hollmann s@gmx.de (2014-09-15): [...] Seeing that the actual problem are missing kernel modules for CCMP (AES), and probably TKIP as well, I'll concentrate on your new questions only Based on your answer, I'm wondering whether there might be some CONFIG_* differences between wpasupplicant and its udeb, which might explain? There are significant CONFIG_* differences between the regular wpasupplicant and wpasupplicant-udeb, both to get it smaller and to avoid dependencies on packages not providing udebs, but the udeb should support: - no encryption - WEP64 - WEP128 - WPAPSK v1 TKIP/ CCMP - WPAPSK2 TKIP/ CCMP More advanced setups, like IEEE8021X (using certificates and per-user encryption, e.g. eduroam and other commercial setups), smartcards and are not supported by the udeb (nor would netcfg know how to configure these). [ o.k., the following three paragraphs have been obsoleted by your other mail ] |As a quick test I have bind-mounted the wpa_supplicant binary from |wpasupplicant-udeb over /sbin/wpa_supplicant of a full installation |and successfully tested: | |# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf |Successfully initialized wpa_supplicant |wlan0: CTRL-EVENT-SCAN-STARTED |wlan0: SME: Trying to authenticate with 01:23:45:67:89:ab (SSID='test' freq=2472 MHz) |wlan0: Trying to associate with 01:23:45:67:89:ab (SSID='test' freq=2472 MHz) |wlan0: Associated with 01:23:45:67:89:ab |wlan0: WPA: Key negotiation completed with 01:23:45:67:89:ab [PTK=CCMP GTK=CCMP] |wlan0: CTRL-EVENT-CONNECTED - Connection to 01:23:45:67:89:ab completed [id=4 id_str=test_aes] |wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE |wlan0: WPA: Group rekeying completed with 01:23:45:67:89:ab [GTK=CCMP] | |# wpa_cli status |Selected interface 'wlan0' |bssid=01:23:45:67:89:ab |ssid=test |id=4 |id_str=test_aes |mode=station |pairwise_cipher=CCMP |group_cipher=CCMP |key_mgmt=WPA2-PSK |wpa_state=COMPLETED |ip_address=10.20.27.0 |address=ba:98:76:54:43:21 | |This is 802.11bgn, using WPA2PSK and CCMP (AES) encryption with an |Atheros AR9285 (ath9k) wlan card, so relatively comparable to the |original submitter (while I have rtl8192du, I currently don't have |access to any wlan card supported by rtl8192cu). Accordingly the udeb |config for wpasupplicant (at least on linux) should be fine. This reminds me, without regulatory domain support (iw(semi-optional), crda, wireless-regdb) only the channels allowed for world-roaming (slightly depending on what the individual wlan drivers and firmwares understand under world-roaming) would be available, which means channel 1-11 (no access to 12/13) and very little, if anything, in the 5 GHz band. [...] [with my wpa maintainer hat on] Semi-related, I have a pending upload for wpa (wpasupplicant-udeb), can you give me a rough guide when it's safe to upload in order not to interfere with d-i beta2[6]? There are no behavioural changes, besides many bugfixes[7]. If you want to test it for d-i, the packaging is ready (besides the changelog entries) in the normal VCS location[8]. Well currently, as far as I can see/test, WPA support in d-i isn't exactly working nicely, so I don't think a wpa upload is going to hurt much. Quite the contrary, hopefully. Thanks, I'll do some final testing (and add CONFIG_DEBUG_SYSLOG=y, as requested in your other mail) and will try to get the new version sponsored quickly. Regards Stefan Lippers-Hollmann signature.asc Description: This is a digitally signed message part.
Bug#760712: WEP vs WPA2
On Mon, 2014-09-15 at 23:08 +0200, Stefan Lippers-Hollmann wrote: Hi On Monday 15 September 2014, Cyril Brulebois wrote: Stefan Lippers-Hollmann s@gmx.de (2014-09-15): [...] Seeing that the actual problem are missing kernel modules for CCMP (AES), and probably TKIP as well, I'll concentrate on your new questions only Based on your answer, I'm wondering whether there might be some CONFIG_* differences between wpasupplicant and its udeb, which might explain? There are significant CONFIG_* differences between the regular wpasupplicant and wpasupplicant-udeb, both to get it smaller and to avoid dependencies on packages not providing udebs, but the udeb should support: - no encryption - WEP64 - WEP128 - WPAPSK v1 TKIP/ CCMP - WPAPSK2 TKIP/ CCMP More advanced setups, like IEEE8021X (using certificates and per-user encryption, e.g. eduroam and other commercial setups), smartcards and are not supported by the udeb (nor would netcfg know how to configure these). WPS would also be nice to have. [...] This reminds me, without regulatory domain support (iw(semi-optional), crda, wireless-regdb) only the channels allowed for world-roaming (slightly depending on what the individual wlan drivers and firmwares understand under world-roaming) would be available, which means channel 1-11 (no access to 12/13) and very little, if anything, in the 5 GHz band. I started to worry about this too. The built-in world regulatory domain allows *passive* use of channels 12-13 and other channels that are not permitted in all countries. That is, the kernel will allow passively scanning on those channels and connecting to an AP, on the assumption that the AP is following the local rules. But I'm prepared to believe that this doesn't work when using wext, or requires wext configuration to be done in a different order than netcfg and wpa_supplicant currently use. Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert. signature.asc Description: This is a digitally signed message part
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On 11/09/14 02:52 AM, Ian Campbell wrote: The new networking related bits seem to be marvell.ko and mvmdio.ko. marvell.ko was already packaged in the right place and I added mvmdio.ko yesterday. I remain hopeful that will have solved your issue. Looks like it. The 20140915 daily boots fine and I just completed a successful installation. Thanks! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5417676d.2000...@nardis.ca
Bug#760904: marked as done (installation-reports: no network on linkstation pro with jessie d-i)
/proc/meminfo: Active(file): 41832 kB /proc/meminfo: Inactive(file):33372 kB /proc/meminfo: Unevictable: 0 kB /proc/meminfo: Mlocked: 0 kB /proc/meminfo: SwapTotal:365564 kB /proc/meminfo: SwapFree: 364992 kB /proc/meminfo: Dirty:12 kB /proc/meminfo: Writeback: 0 kB /proc/meminfo: AnonPages: 24676 kB /proc/meminfo: Mapped:11348 kB /proc/meminfo: Shmem: 3768 kB /proc/meminfo: Slab: 7152 kB /proc/meminfo: SReclaimable: 4168 kB /proc/meminfo: SUnreclaim: 2984 kB /proc/meminfo: KernelStack: 536 kB /proc/meminfo: PageTables: 744 kB /proc/meminfo: NFS_Unstable: 0 kB /proc/meminfo: Bounce:0 kB /proc/meminfo: WritebackTmp: 0 kB /proc/meminfo: CommitLimit: 428296 kB /proc/meminfo: Committed_AS: 69284 kB /proc/meminfo: VmallocTotal: 892928 kB /proc/meminfo: VmallocUsed: 21828 kB /proc/meminfo: VmallocChunk: 854272 kB -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.14-2-orion5x Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Mon, 2014-09-15 at 15:25 -0700, Ryan Tandy wrote: On 11/09/14 02:52 AM, Ian Campbell wrote: The new networking related bits seem to be marvell.ko and mvmdio.ko. marvell.ko was already packaged in the right place and I added mvmdio.ko yesterday. I remain hopeful that will have solved your issue. Looks like it. The 20140915 daily boots fine and I just completed a successful installation. Thanks! Excellent! Closing the bug then, thanks! Ian.---End Message---
