Re: Reviewing nobootloader for wheezy
On 08/12/2012 02:59 PM, Cyril Brulebois wrote: > Hello Milan, > > and thanks for your patch for nobootloader. Got a quick question though. > > Changelog excerpt: > | nobootloader (1.35) unstable; urgency=low > | > | [ Milan Kupcevic ] > | * Do not assume Linux kernel verison is 2.* > | * Use symlink 'vmlinuz' instead of full kernel name. > > But I see this change in postinst which looks a bit unrelated: > | @@ -148,7 +148,7 @@ > | scsi,0) > | path="/pci/scsi/disk@$bus,$target,$lun" ;; > | *) > | - path="" ;; > | + path="hd" ;; > | esac > | > | # map theidevice to the OF aliases from /proc/device-tree/aliases. > > Can you please clarify whether it was intended? This changelog line is missing: * Fallback to factory default HD firmware alias, not to And what that does? At the end of nobootloader installation, d-i prints out a line the user installing the system is supposed to type into firmware prompt to make it find kernel on machine boots/reboots. The 'path' variable in question is the firmware device path used in the printed line on Pegasos machines. I've replaced the technically invalid firmware path '' with the device alias 'hd' which works out fine when the machine has only one HD, or if the user installs the system on the first HD when the machine has more than one drive. In my wheezy installer tests it always falls back to . This happens because the kernel internals changed since the original Pegasos code in nobootloader was written. To fix it properly, it requires significant rewrite. Which is not worth. I would rather spend more time into making Grub2 installer working on Pegasos and other PowerPC machines. But this change is too late for Wheezy. It has to wait for Jessie. In the meantime, the changes made in nobootloader version 1.35 are enough to make it work for wheezy. Milan signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#684573: busybox fails to parse less-than-3-component linux version string
Processing commands for cont...@bugs.debian.org: > reassign 684573 src:busybox 1:1.20.0-5 Bug #684573 [src] busybox fails to parse less-than-3-component linux version string Warning: Unknown package 'src' Bug reassigned from package 'src' to 'src:busybox'. No longer marked as found in versions 1:1.20.0-5. Ignoring request to alter fixed versions of bug #684573 to the same values previously set Bug #684573 [src:busybox] busybox fails to parse less-than-3-component linux version string Marked as found in versions busybox/1:1.20.0-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 684573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684573 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.13448475403834.transcr...@bugs.debian.org
Processed: bug 684573 is forwarded to https://bugs.busybox.net/show_bug.cgi?id=5444, merging 684611 684573
Processing commands for cont...@bugs.debian.org: > forwarded 684573 https://bugs.busybox.net/show_bug.cgi?id=5444 Bug #684573 [src:busybox] busybox fails to parse less-than-3-component linux version string Set Bug forwarded-to-address to 'https://bugs.busybox.net/show_bug.cgi?id=5444'. > merge 684611 684573 Bug #684611 [src:busybox] busybox fails to parse less-than-3-component linux version string Bug #684573 [src:busybox] busybox fails to parse less-than-3-component linux version string Merged 684573 684611 > thanks Stopping processing here. Please contact me if you need assistance. -- 684573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684573 684611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684611 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.13448484459919.transcr...@bugs.debian.org
Bug#684710: insta: wheezy installer hangs on detectin ethernet card (lenovo think pad x201i)
Package: installation-reports Severity: important File: insta Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: network Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso- cd/debian-testing-i386-kde-CD-1.iso 06-Aug-2012 Date: Machine: lenovo thinkpad x201i Partitions: $ df -Th Файловая система Тип Размер Использовано Дост Использовано% Cмонтировано в rootfs rootfs 5,5G 4,1G 1,2G 78% / udev devtmpfs10M0 10M0% /dev tmpfstmpfs 588M 772K 588M1% /run /dev/block/8:6 ext3 5,5G 4,1G 1,2G 78% / tmpfstmpfs 1,2G 348K 1,2G1% /run/shm /dev/sda2ext3 5,5G 4,9G 408M 93% /mnt/sda2 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] 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: I tried two installation cd-images (buisness card and cd-kde), and both are hanging up at the stage of detecting network card. -- 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="5.0 (lenny) - installer build 20090123lenny8" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux (none) 2.6.26-2-486 #1 Sat Nov 20 22:54:50 UTC 2010 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:0044] (rev 02) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0046] (rev 02) lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Ibex Peak HECI Controller [8086:3b64] (rev 06) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10ea] (rev 06) lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b3c] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Ibex Peak High Definition Audio [8086:3b56] (rev 06) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 1 [8086:3b42] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 4 [8086:3b48] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 5 [8086:3b4a] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b34] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a6) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Ibex Peak LPC Interface Controller [8086:3b07] (rev 06) lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation Ibex Peak 6 port SATA AHCI Controller [8086:3b2f] (rev 06) lspci -knn: Kernel driver in use: ahci lspci -knn: Kernel modules: ahci lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation Ibex Peak SMBus Controller [8086:3b30] (rev 06) lspci -knn: 00:1f.6 Signal processing controller [1180]: Intel Corporation Ibex Peak Thermal Subsystem [8086:3b32] (rev 06) lspci -knn: 02:00.0 Network controller [0280]: Intel Corporation Device [8086:0084] lspci -knn: ff:00.0 Host bridge [0600]: Intel Corporation Device [8086:2c62] (rev 02) lspci -knn: ff:00.1 Host bridge [0600]: Intel Corporation Device [8086:2d01] (rev 02) lspci -knn: ff:02.0 Host bridge [0600]: Intel Corporation Device [8086:2d10] (rev 02) lspci -knn: ff:02.1 Host bridge [0600]: Intel Corporation
Re: EFI approach and patches
On Mon, Aug 13, 2012 at 01:10:31AM +0100, Steve McIntyre wrote:
> 1. Add a new subarch of "efi" for i386 and amd64 in
>libdebian-installer, worked out (as usual for EFI) from whether
>/sys/firmware/efi is accessible. This filters through readily to
>archdetect, used all over the place elsewhere in d-i.
This needs efivars loaded AFAIK. I'm not yet familiar with the EFI part
of the Linux kernel.
> 2. Build efi-reader for amd64 as well as ia64. Not sure if this
>provides anything important, but it doesn't hurt. :-)
This is needed for what?
> 3. Build elilo-installer for amd64 too, and mark it as installable for
>i386/efi|amd64/efi.
Does elilo provide 32 and 64-bit efi binaries? All the current machines
need 64-bit binaries.
> 4. Mark grub-installer as not installable for i386/efi|amd64/efi
No.
> 5. Mark lilo-installer as not installable for i386/efi|amd64/efi
Okay.
> 6. Several tweaks to partman-auto:
> * Switch from fat16 to fat32 in ia64 recipes
Why?
> The first of these needs testing - is EFI on ia64 *definitely* ok
> with fat32, or must it have fat16? I've also upped the size of the
> EFI partition to 512MB, a more sensible minimum in case of multiple
> OS installs. I cloned tha ia64 recipes, then the diff shows the
> changes since. Not 100% sure of the best approach for partman-auto,
> I'll admit here. Thoughts?
It works fine with FAT16, however grub needs the partition properly
alligned.
> 8. partman-partitioning: for amd64/efi and i386/efi, use gpt instead
>of msdos
Nope. EFI works fine with msdos.
> +/* Are we on an EFI system? Check to see if /sys/firmware/efi
> + * exists */
> +static int is_efi(void)
> +{
> + int ret = access("/sys/firmware/efi", R_OK);
> +if (ret == 0)
> + return 1;
> +else
> + return 0;
> +}
Whitespace damage.
Bastian
--
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/20120813101547.ga18...@wavehammer.waldi.eu.org
Re: Byte queue limits in Linux for wheezy / linux kernel ABI bumps
On Sun, Aug 05, 2012 at 07:43:50PM +0200, Bastian Blank wrote: > On Sat, Aug 04, 2012 at 10:06:48PM +0100, Ben Hutchings wrote: > > A possible solution would be something like: > > 1. Keep multiple versions of udebs in the same suite (currently possible > > for arch:all, but maybe not supported for arch-dependent packages) > Breaks the expectations within d-i. This is listed on my TODO. > > 4. Make anna try older package versions if dependencies can't be reolved > > for the newest version > Versions in dependencies will be ignored. The packages stuff used in d-i is limited. It only allows one version of a package, which produced problems with cdebootstrap. In addition it disallows several other constructs: Breaks, Conflicts and ignores all versions in relations. I have the problem with multiple version on my list for a larger rewrite, which will make it need more memory. It can't be fixed in a backward compatible way. Bastian -- The sight of death frightens them [Earthers]. -- Kras the Klingon, "Friday's Child", stardate 3497.2 -- 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/20120813104949.ga19...@wavehammer.waldi.eu.org
installing on mdraid imsm arrays
At work, we're using mainly supermicro servers, and they have support in the BIOS for Intel Matrix raid (imsm), which is a form of sataraid/fakeraid. So I have been looking at installing debian on such a "raid" system. d-i supports dmraid somewhat, nowadays, but the package in wheezy is out of date, and I have the impression that support for monitoring/rebuilding of arrays by dmraid isn't all that good. It also looks like dmraid is not maintained by upstream anymore. Now I also noticed when booting the wheezy installer on a system with the disks configured as imsm, that the mdraid support of the installer actually reckognizes the array as imsm. And that in fact the imsm support in mdadm is quite good. The installer crashes though when trying to access that array, since the mdadm udeb misses 'mdmon'. But that is easily fixed. I now have a version of the wheezy installer that succesfully installs and boots debian on a mdadm imsm array. I had to fix/update mdadm (bug #684708), libparted (bug #684713) and lvm2 (bug #684712). wrt d-i, I had to fix up the following packages: - partman-auto: allow partioned md devices - partman-base: filter out devices that are part of a partioned md device - grub-installer: reckognize partitioned md devices and install grub on all the underlaying devices (only for RAID1 right now) Do you think that it would be worth it to integrate this for the wheezy release? If so, should I post patches for review on a webpage somewhere, or here on the list, or just submit them as bugs against their respective packages? Thanks, Mike. -- 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/5028e25e.8080...@debian.org
Re: installing on mdraid imsm arrays
Hi Miquel van Smoorenburg writes: > At work, we're using mainly supermicro servers, and they have support in > the BIOS for Intel Matrix raid (imsm), which is a form of > sataraid/fakeraid. So I have been looking at installing debian on such a > "raid" system. d-i supports dmraid somewhat, nowadays, but the package > in wheezy is out of date, and I have the impression that support for > monitoring/rebuilding of arrays by dmraid isn't all that good. It also > looks like dmraid is not maintained by upstream anymore. > > Now I also noticed when booting the wheezy installer on a system with > the disks configured as imsm, that the mdraid support of the installer > actually reckognizes the array as imsm. And that in fact the imsm > support in mdadm is quite good. The installer crashes though when trying > to access that array, since the mdadm udeb misses 'mdmon'. But that is > easily fixed. > > I now have a version of the wheezy installer that succesfully installs > and boots debian on a mdadm imsm array. > > I had to fix/update mdadm (bug #684708), libparted (bug #684713) and > lvm2 (bug #684712). > > wrt d-i, I had to fix up the following packages: > > - partman-auto: allow partioned md devices > - partman-base: filter out devices that are part of a >partioned md device > - grub-installer: reckognize partitioned md devices and install >grub on all the underlaying devices (only for RAID1 right now) > > Do you think that it would be worth it to integrate this for the wheezy > release? If so, should I post patches for review on a webpage somewhere, > or here on the list, or just submit them as bugs against their > respective packages? It's definitely worth to integrate this into Debian. If it's possible to include this in wheezy is up to the release team. IMHO the easiest way to track such changes is to send individual bug reports and to send a mail explaining how they depend on each other afterwards to all the reports (with links to all reports). Another possible way to track this is to add a meta-bug blocked by all the other bugs. If you have commit access (you can request it if you don't have it yet) to the d-i repository you can also commit your changes to a feature branch like people/miquels/imsm. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- 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/87fw7r6ma6@meteor.durcheinandertal.bofh
Re: EFI approach and patches
wa...@debian.org wrote:
>On Mon, Aug 13, 2012 at 01:10:31AM +0100, Steve McIntyre wrote:
>> 1. Add a new subarch of "efi" for i386 and amd64 in
>>libdebian-installer, worked out (as usual for EFI) from whether
>>/sys/firmware/efi is accessible. This filters through readily to
>>archdetect, used all over the place elsewhere in d-i.
>
>This needs efivars loaded AFAIK. I'm not yet familiar with the EFI part
>of the Linux kernel.
Yes, it does. It's automatically loaded by the point when it's needed
here.
>> 2. Build efi-reader for amd64 as well as ia64. Not sure if this
>>provides anything important, but it doesn't hurt. :-)
>
>This is needed for what?
On ia64, it provides access to EFI variables for things like language
preference. As far as I can see, they're also present on amd64. Not
critical, but there's no point to not use the package if it's already
available.
>> 3. Build elilo-installer for amd64 too, and mark it as installable for
>>i386/efi|amd64/efi.
>
>Does elilo provide 32 and 64-bit efi binaries? All the current machines
>need 64-bit binaries.
Yes, it already includes ia32, ia64 and x86_64 code and was already
building for all 3 architectures.
>> 4. Mark grub-installer as not installable for i386/efi|amd64/efi
>
>No.
Not in the long term, agreed. I've just turned it off for now as I was
having problems getting grub-efi to install. Should be fixed shortly,
I hope.
>> 5. Mark lilo-installer as not installable for i386/efi|amd64/efi
>
>Okay.
>
>> 6. Several tweaks to partman-auto:
>> * Switch from fat16 to fat32 in ia64 recipes
>
>Why?
For consistency with partman-efi. AFAICS it can only support one
filesystem without significant changes (or maybe a split into
partman-efi and partman-uefi). AFAIK UEFI explicitly wants fat32, so
I've switched over to that consistently.
>> The first of these needs testing - is EFI on ia64 *definitely* ok
>> with fat32, or must it have fat16? I've also upped the size of the
>> EFI partition to 512MB, a more sensible minimum in case of multiple
>> OS installs. I cloned tha ia64 recipes, then the diff shows the
>> changes since. Not 100% sure of the best approach for partman-auto,
>> I'll admit here. Thoughts?
>
>It works fine with FAT16, however grub needs the partition properly
>alligned.
Alignment seems fine for me:
tack:~/debian/efi$ gdisk -l efi-hard-disk.img
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk efi-hard-disk.img: 16777216 sectors, 8.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4F312FA0-5643-4775-9AB8-01BF3F207487
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 16777182
Partitions will be aligned on 2048-sector boundaries
Total free space is 4029 sectors (2.0 MiB)
Number Start (sector)End (sector) Size Code Name
12048 999423 487.0 MiB EF00
2 99942415994879 7.2 GiB 0700
31599488016775167 381.0 MiB 8200
>> 8. partman-partitioning: for amd64/efi and i386/efi, use gpt instead
>>of msdos
>
>Nope. EFI works fine with msdos.
But not reliably on all disks. We'd need to switch to GPT for large
disks (> 2TB), which people are going to want with new UEFI
installations anyway. Looking at the code, I think it's much easier to
just use GPT with UEFI than to bugger with the rest of the partman
code to switch partition style depending on disk size.
>> +/* Are we on an EFI system? Check to see if /sys/firmware/efi
>> + * exists */
>> +static int is_efi(void)
>> +{
>> + int ret = access("/sys/firmware/efi", R_OK);
>> +if (ret == 0)
>> + return 1;
>> +else
>> + return 0;
>> +}
>
>Whitespace damage.
ACK, easily fixed.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait: http://www.debian.org/CD/free-linux-cd
Debian does NOT ship free CDs. Please do NOT contact the mailing
lists asking us to send them to you.
--
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/e1t0ti4-0002b3...@mail.einval.com
Bug#684717: debian-installer-7.0-netboot-amd64: Relative paths in syslinux configuration interact badly with TFTP prefix
Package: debian-installer-7.0-netboot-amd64 Version: 20120712 Severity: wishlist I tried to make the d-i files available under the /debian-installer path of my TFTP server with a bind mount: $ findmnt /srv/tftp/debian-installer/ TARGET SOURCE FSTYPE OPTIONS /srv/tftp/debian-installer /dev/mapper/thoth-root[/usr/lib/debian-installer/images] ext4 rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered However the use of relative paths in the syslinux config files make this difficult. My PXE-booted client displays the following: BOOT SERVER IP: 10.0.0.1 !PXE entry point found (we hope) at 9E1C:0104 via plan A UNDI code segment at 9E1C len 199E UNDI data segment at 9C99 len 1830 Getting cached packet 01 02 03 My IP address seems to be 0A00010B 10.0.1.11 ip:10.0.1.11:109.0.0.1:10.0.0.1:255.255.0.0 BOOTIF=01-08-00-27-96-86-ec SYSUUID=blah TFTP prefix: debian-installer/amd64/text/ Trying to load: pxelinux.cfg/default Could not find kernel image: debian-installer/amd64/boot-screens/vesamenu.c32 boot: Looking at what's going over the network: # tshark -i eth0 -R tftp Capturing on eth0 6.25462810.0.1.11 -> 10.0.0.1 TFTP 97 Read Request, File: debian-installer/amd64/text/pxelinux.0, Transfer type: octet, tsize\000=0\000 6.259698 10.0.0.1 -> 10.0.1.11TFTP 1502 Data Packet, Block: 2 ... ... data packets and requests for mac-address-specific pxelinux.cfg elided ... ... 6.49234810.0.1.11 -> 10.0.0.1 TFTP 120 Read Request, File: debian-installer/amd64/text/pxelinux.cfg/default, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.492898 10.0.0.1 -> 10.0.1.11TFTP 67 Option Acknowledgement, tsize\000=154\000, blksize\000=1408\000 6.49627010.0.1.11 -> 10.0.0.1 TFTP 60 Acknowledgement, Block: 0 6.496343 10.0.0.1 -> 10.0.1.11TFTP 200 Data Packet, Block: 1 (last) 6.49701110.0.1.11 -> 10.0.0.1 TFTP 60 Acknowledgement, Block: 1 6.49765510.0.1.11 -> 10.0.0.1 TFTP 144 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/menu.cfg, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.498214 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.49941710.0.1.11 -> 10.0.0.1 TFTP 148 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.499975 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50129910.0.1.11 -> 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.cbt, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.501857 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50330510.0.1.11 -> 10.0.0.1 TFTP 150 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.0, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.503862 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50543110.0.1.11 -> 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.com, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.505995 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found 6.50723710.0.1.11 -> 10.0.0.1 TFTP 152 Read Request, File: debian-installer/amd64/text/debian-installer/amd64/boot-screens/vesamenu.c32.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 6.507794 10.0.0.1 -> 10.0.1.11TFTP 61 Error Code, Code: File not found, Message: File not found menu.cfg can't be loaded, because the TFTP prefix 'debian-installer/amd64/text' is prepended to the path in the config file of 'debian-installer/amd64/boot-screens/menu.cfg'. If the config file used paths relative to the pxelinux.0 file then I think booting would work correctly. Additionally the assumed prefix path written into the config files doesn't let the 'text' and 'gtk' versions of the installers co-exist in the same TFTP root, because the paths are missing the text/gtk element. Once the various debian-installer-$VERSION-netboot-$ARCH packages are co-installable, this will prevent different versions from being accessible from the same TFTP server as well. My workaround configuration involves bind-mounting /usr/lib/debian-installer/imag
Bug#684718: Debian-installer fails
Package: Debian-installer I have try to install wheezy twice, either by upgrading from squeeze or direct installation from internet In the case of upgrading the system works but after I restart the pc after the first screen showing the kernels, my screen goes gray and there is no responsee from the keyboard. The same holds when I try to install wheezy from the internet. I have attach the sysinfo. Please ask me any other information you need. Regards Antonis Manoussakis sysinfo Description: Binary data
Re: Bug#682857: console-setup-udeb: can't preseed keyboard layout=de variant=nodeadkeys
On Fri, Aug 10, 2012 at 11:36:28AM +0200, Samuel Thibault wrote: > > > > What about introducing new templates of string type that can be used in > > order to preseed arbitrary values in them? > > Then they'd appear in the user-presented choices, which we don't want to > clutter. > > Another way actually might be to skip the keymap question when layout > and variant are already provided. That'd however need careful tinkering > in the .config script. Well, my idea was not to ask questions when keyboard-configuration/modelcode, keyboard-configuration/layoutcode, keyboard-configuration/variantcode and keyboard-configuration/optionscode are preseeded. I suppose this is analogous to what already exists in the config script and is used by keyboard-configuration in order to avoid asking questions when /etc/default/keyboard contains unsupported by the config script configuration. I haven't looked carefully into specifics of the code used only by the udeb, but can't you simply use the variable $unsupported_layout even when $is_not_debian_installer is false? Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813121316.ga2...@logic.fmi.uni-sofia.bg
Processing of netcfg_1.88_amd64.changes
netcfg_1.88_amd64.changes uploaded successfully to localhost along with the files: netcfg_1.88.dsc netcfg_1.88.tar.gz netcfg_1.88_amd64.udeb netcfg-static_1.88_amd64.udeb 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/e1t0v8j-0006zb...@franck.debian.org
netcfg_1.88_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Aug 2012 15:50:50 +0200 Source: netcfg Binary: netcfg netcfg-static Architecture: source amd64 Version: 1.88 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Philipp Kern Description: netcfg - Configure the network (udeb) netcfg-static - Configure a static network (udeb) Changes: netcfg (1.88) unstable; urgency=low . * Team upload . [ Philipp Kern ] * Avoid gateway reachability testing on s390(x) with a layer 3 qeth network device. Checksums-Sha1: e8b9c97c22c026955421eef8984df617cefbbf45 1478 netcfg_1.88.dsc ff7160b64b14b53a70266e8e6ea3dafe7df19b52 677934 netcfg_1.88.tar.gz 8d39f224cec6089b3c962b5140d4719e85631112 395524 netcfg_1.88_amd64.udeb 1a2f83d9eba7ddf3857cdabd80a68a821d390f79 312276 netcfg-static_1.88_amd64.udeb Checksums-Sha256: ce5c0889027c4a636137f3e5c02dc4a956c99fd73306806d48197f39150d10b6 1478 netcfg_1.88.dsc 71794cca020cfaf2c6a7800e5112e83e1c0f570c088ba35144cdb1014c046502 677934 netcfg_1.88.tar.gz 858a8990b1f196fbd3358052b73d5e87158cfce0f2207d10beed770492425ff9 395524 netcfg_1.88_amd64.udeb 626958edd05d4277f4171a6725726e681008a90dccc1fbe4845d9ae0966212e7 312276 netcfg-static_1.88_amd64.udeb Files: 98b22beb027c419d6fe450cd8a661b2e 1478 debian-installer optional netcfg_1.88.dsc 31216ae70aa3f6d719d2de07007ecdec 677934 debian-installer optional netcfg_1.88.tar.gz ba69a1bfd7b9b7ce1c33ecff6d2a815c 395524 debian-installer optional netcfg_1.88_amd64.udeb 642977ad6dbb58baad63014733ba0b52 312276 debian-installer optional netcfg-static_1.88_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJQKQZZAAoJEERuJUU10FbswlsIAJl44naHPKJjCaaD+j1EHsuM D4VZ8lCH41MclhejFbA3fgc9n7C4GilTGCnqlOSr0hsO7RrB5JaGRQ30nnGHnDDL +vr0W/Nu6N86gsk75uK+daNM0ONe5iZxdQACWO9XdRecGF41hoAwJde+EQVDd42k G3ToHV234KGBwn2LVZ5RrA/+qNSwMupEChKEt4cgu7GAFwZ37Kr5cGpB5AOP0Znn NyjI1tUCy5WVM6WV6fCUS/SMsqdHM03vRAL7pa6FsRNeALUPTxq6q4fNELTnKXC7 iKQqLA2B9wLT2jpK15Yqpw8b/fnaxA26+DMiB4mr4GN9qYpNOlePDE26D2wbvc4= =ChQx -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/e1t0vvl-0005tr...@franck.debian.org
Bug#684718: Debian-installer fails
Quoting Anntonis Manoussakis (amano...@gmail.com): > > Package: Debian-installer > > > I have try to install wheezy twice, either by upgrading from squeeze > or direct installation from internet > > > In the case of upgrading the system works but after I restart the pc > > after the first screen showing the kernels, > my screen goes gray and there is no responsee > from the keyboard. > > The same holds when I try to install wheezy from the internet. > > > I have attach the sysinfo. Please ask me any other information you > need. Please be more specific: upgrading from squeeze is not D-I job so you may need to investigate in more details what's happening (quite likely you didn't follow the usual procedure which is described in release notes (admitedly release notes are not available for wheezy but the squeeze release notes will give you hints) When you mention "install directly from Internet", what happens? You just mention "The same holds". signature.asc Description: Digital signature
Processing of finish-install_2.37_amd64.changes
finish-install_2.37_amd64.changes uploaded successfully to localhost along with the files: finish-install_2.37.dsc finish-install_2.37.tar.gz finish-install_2.37_all.udeb 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/e1t0wvg-0004ba...@franck.debian.org
Bug#684710: marked as done (insta: wheezy installer hangs on detectin ethernet card (lenovo think pad x201i))
Your message dated Mon, 13 Aug 2012 18:05:41 +0200 with message-id <20120813160541.gj9...@mykerinos.kheops.frmug.org> and subject line Re: Bug#684710: insta: wheezy installer hangs on detectin ethernet card (lenovo think pad x201i) has caused the Debian Bug report #684710, regarding insta: wheezy installer hangs on detectin ethernet card (lenovo think pad x201i) 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.) -- 684710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: important File: insta Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: network Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso- cd/debian-testing-i386-kde-CD-1.iso 06-Aug-2012 Date: Machine: lenovo thinkpad x201i Partitions: $ df -Th Файловая система Тип Размер Использовано Дост Использовано% Cмонтировано в rootfs rootfs 5,5G 4,1G 1,2G 78% / udev devtmpfs10M0 10M0% /dev tmpfstmpfs 588M 772K 588M1% /run /dev/block/8:6 ext3 5,5G 4,1G 1,2G 78% / tmpfstmpfs 1,2G 348K 1,2G1% /run/shm /dev/sda2ext3 5,5G 4,9G 408M 93% /mnt/sda2 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] 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: I tried two installation cd-images (buisness card and cd-kde), and both are hanging up at the stage of detecting network card. -- 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="5.0 (lenny) - installer build 20090123lenny8" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux (none) 2.6.26-2-486 #1 Sat Nov 20 22:54:50 UTC 2010 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:0044] (rev 02) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0046] (rev 02) lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Ibex Peak HECI Controller [8086:3b64] (rev 06) lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Device [8086:10ea] (rev 06) lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b3c] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Ibex Peak High Definition Audio [8086:3b56] (rev 06) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 1 [8086:3b42] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 4 [8086:3b48] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Ibex Peak PCI Express Root Port 5 [8086:3b4a] (rev 06) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation Ibex Peak USB2 Enhanced Host Controller [8086:3b34] (rev 06) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:244
finish-install_2.37_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Aug 2012 17:49:33 +0200 Source: finish-install Binary: finish-install Architecture: source all Version: 2.37 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Philipp Kern Description: finish-install - Finish the installation and reboot (udeb) Changes: finish-install (2.37) unstable; urgency=low . * Team upload . [ Philipp Kern ] * Do not install finish-install.d/90console on s390(x). The default inittab as shipped by sysvinit is sufficient to configure the console correctly. Checksums-Sha1: 1917d6521ab7a72b4fa58e82cc050a14417b113a 1271 finish-install_2.37.dsc 7e1aa8a5711ba2f9beed4e1e8ed2496c67e295d1 60555 finish-install_2.37.tar.gz 5d65d8697d4d9733ef02604f7c9f585b952f32c6 24612 finish-install_2.37_all.udeb Checksums-Sha256: e9927f61bb8552fc521195cdeafeb70a0b29914b45fa60447d3cd7763fad89a1 1271 finish-install_2.37.dsc bb5f2d3430c9e9289e3eb6ca6750d9cc5713593608872b342153d2c64d9fe6e4 60555 finish-install_2.37.tar.gz aeabb6de916e253281ff88dd0c9d64b7c9537a35e32d28f18f99f527b3e8f0d7 24612 finish-install_2.37_all.udeb Files: 32a57c2bf1a7acd286c7259822ef71c7 1271 debian-installer required finish-install_2.37.dsc bf47c581f0957fb527f1b47d80f5868a 60555 debian-installer required finish-install_2.37.tar.gz 8c10f21d72289d95750c852cbfec1035 24612 debian-installer required finish-install_2.37_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJQKSIYAAoJEERuJUU10FbsInMIAIdJcb67kuBTDVJo6IT8d9j/ NUiJGYTeieJ1N4et4eV+yb0zehbiktiB850+f4hI3Dy0w16lipIVxYzC+Mf7MPv/ amEP6H52u1/PDi1Wn/7AmIQfAwdPZN2uhAJ8QSYCX9BZ380h7qs6KktKC6BQPg8l 3H+lPN08/xbBIxoryHWaRQ0xc1oc8YF7SYeOV24Krn8unbeJx5WBObcbV08QgD8D wj8JiC5TkfoHy6FI+lGBgbX9Qsniw2fBlqfVdplxLWAa86vhpkougrmqc/IUDiUb HyDj3pi/qQf49LR90Sz+iPIMNvpvFWpumQHqgC0Y1+QYGj8m98STdwCyCiKX8zk= =ihVm -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/e1t0x6p-0002co...@franck.debian.org
Bug#684718: Debian-installer fails
On Mon, 13 Aug 2012 18:02:34 +0200 Christian PERRIER wrote: Thanks for the reply When I install wheezy from internet, using the netinst (generally 135-175 MB) CD images, at some point the procedure ask to take-off the disk-installer and the system reboot. After the rebooting and after the first screen showing the kernels, the (upper) half of my screen goes gray and there is no response from the keyboard I tray this installation, today and also a month ago month ago using the netinstaller. After the failure(s), I turn again to squeeze installing using the netinst and everything is ok. Thanks Antonis Manoussakis > Quoting Anntonis Manoussakis (amano...@gmail.com): > > > > Package: Debian-installer > > > > > > I have try to install wheezy twice, either by upgrading from > > squeeze or direct installation from internet > > > > > > In the case of upgrading the system works but after I restart the > > pc > > > > after the first screen showing the kernels, > > my screen goes gray and there is no responsee > > from the keyboard. > > > > The same holds when I try to install wheezy from the internet. > > > > > > I have attach the sysinfo. Please ask me any other information you > > need. > > Please be more specific: > > upgrading from squeeze is not D-I job so you may need to investigate > in more details what's happening (quite likely you didn't follow the > usual procedure which is described in release notes (admitedly release > notes are not available for wheezy but the squeeze release notes will > give you hints) > > When you mention "install directly from Internet", what happens? You > just mention "The same holds". > > > -- 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/20120813193017.5727586f@debian
Bug#684771: installation-report: Typo in French translation.
Package: installation-report Severity: minor Tags: l10n patch Dear Maintainer, I found a typo in the French translation, I'm providing a patch for it. Regards, Valentin --- fr.po.old 2012-08-13 19:22:12.775732548 +0200 +++ fr.po 2012-08-13 19:22:27.611806116 +0200 @@ -1945,7 +1945,7 @@ #. :sl1: #: ../anna.templates:3001 msgid "Loading additional components" -msgstr "Charger des composants supplémentaires" +msgstr "Chargement des composants supplémentaires" #. Type: text #. Description signature.asc Description: PGP signature
Bug#684777: installation-report: Install of kfreebsd-i386 failed in VirtualBox
Package: installation-report Severity: minor Hi, Boot method: netinstall Image version: debian-wheezy-DI-b1-kfreebsd-i386-netinst.iso Date: 2012-08-13 19:31 +0002 Machine: VirtualBox (on Debian GNU/Linux Sid amd64) Processor: Memory: Partitions: automated install: /, /home, /var, ... separated Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: Cannot connect to my network, either automatically (does not connect to DHCP server) or manually (no connection, cannot ping it from another machine). I tried both "bridge" and "NAT" modes. Running ifconfig is the installer shell prints (after I select VirtualBox's bridge networking and manual configuration of the network): pcn0: flags=8843 metric 0 mtu 1500 option=8 ether 8:0:27:65:4d inet6 [my IP here] prefixlen 64 scopeid 0x1 inet 192.168.1.159 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet none status: active nd6 options=23 When detecting hard drives, I got this message: Could not get identity of device /dev/ada0 - Inapropriate ioctl for device I selected "ignore", and it passed. GRUB installed failed: "package grub-pc could not be installed in /target/". /var/log/syslog contains errors of dpkg and/or aptitude, telling no version of package grub-common is available, even if it has been found in the database. Regards, Valentin signature.asc Description: PGP signature
Bug#684771: marked as done (installation-report: Typo in French translation.)
Your message dated Mon, 13 Aug 2012 22:28:05 +0200 with message-id <20120813202805.gk9...@mykerinos.kheops.frmug.org> and subject line Re: Bug#684771: installation-report: Typo in French translation. has caused the Debian Bug report #684771, regarding installation-report: Typo in French translation. 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.) -- 684771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-report Severity: minor Tags: l10n patch Dear Maintainer, I found a typo in the French translation, I'm providing a patch for it. Regards, Valentin --- fr.po.old 2012-08-13 19:22:12.775732548 +0200 +++ fr.po 2012-08-13 19:22:27.611806116 +0200 @@ -1945,7 +1945,7 @@ #. :sl1: #: ../anna.templates:3001 msgid "Loading additional components" -msgstr "Charger des composants supplémentaires" +msgstr "Chargement des composants supplémentaires" #. Type: text #. Description signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Quoting Valentin Lorentz (prog...@progval.net): > Package: installation-report > Severity: minor > Tags: l10n patch > > Dear Maintainer, > > I found a typo in the French translation, I'm providing a patch for it. Not exactly a typo, more a mis-translation, but you're right it should be the substantive form, not a verbal form. I corrected this in the translation master file. In theory, the bug should be reassigned to the "anna" package, then closed with next uploadwhich is a bit complicated to achieve and prone to errors. Hence closing *now* as I know this issue will be fixed. Merci for reporting..:-) signature.asc Description: Digital signature --- End Message ---
Bug#684796: D-I wheezy B1 installation question/issue
Package: installation-reports Boot method: CD Image version: debian- wheezy-DI-b1-i386-netinst.iso Date: 2012 08 13 Machine: Great Quality GigaPro (Please don't laugh too hard! ;-) ) Processor: Via Samuel 2 Memory:512MB Partitions: Not Far Enough into procedure Output of lspci -knn (or lspci -nn): Not far enough into procedure Base System Installation Checklist: [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: [O ] Install base system:[O ] Clock/timezone setup: [O ] User/password setup:[O ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Doing a netinstall starting from cd... The distro "wheezy" did not appear to be supported on ftp.us.debian.org and mirror.cc.columbia.edu. The apparently relevant message on VT4 contains: mirror does not support the specified release (wheezy) I searched the D-I mail archive for some kind of hint as to which mirror I should be using and/or how to specify it -- to no avail. Which mirror should I be using what did I do wrong... and where should I have looked, please?
Bug#684796: D-I wheezy B1 installation question/issue
Hello, Matthew Variot wrote: > Doing a netinstall starting from cd... > > The distro "wheezy" did not appear to be supported on ftp.us.debian.org > and mirror.cc.columbia.edu. The apparently relevant message on VT4 > contains: > > mirror does not support the specified release (wheezy) I tested with exactly the same iso image and mirrors, and all worked fine, on both mirrors. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Powered by Sylpheed 3.0.2 under Debian GNU/ / _ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / // /_/ /_/\/ /___/ /_/\_\6.0 / Squeeze. Registered LinuxUser #311290 - http://counter.li.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/20120814013024.d2495369.li...@wansing-online.de
Bug#684796: D-I wheezy B1 installation question/issue
Okay, I will double check the network connectivity Thanks! Matt V. On Aug 13, 2012, at 4:30 PM, Holger Wansing wrote: Hello, Matthew Variot wrote: Doing a netinstall starting from cd... The distro "wheezy" did not appear to be supported on ftp.us.debian.org and mirror.cc.columbia.edu. The apparently relevant message on VT4 contains: mirror does not support the specified release (wheezy) I tested with exactly the same iso image and mirrors, and all worked fine, on both mirrors. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Powered by Sylpheed 3.0.2 under Debian GNU/ / _ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / // /_/ /_/\/ /___/ /_/\_\6.0 / Squeeze. Registered LinuxUser #311290 - http://counter.li.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/1bc5be03-14f5-4052-b736-e77d935ad...@dock.net
Bug#684796: marked as done (D-I wheezy B1 installation question/issue)
Your message dated Tue, 14 Aug 2012 06:18:17 +0200 with message-id <20120814041817.gm9...@mykerinos.kheops.frmug.org> and subject line Re: Bug#684796: D-I wheezy B1 installation question/issue has caused the Debian Bug report #684796, regarding D-I wheezy B1 installation question/issue 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.) -- 684796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: CD Image version: debian- wheezy-DI-b1-i386-netinst.iso Date: 2012 08 13 Machine: Great Quality GigaPro (Please don't laugh too hard! ;-) ) Processor: Via Samuel 2 Memory:512MB Partitions: Not Far Enough into procedure Output of lspci -knn (or lspci -nn): Not far enough into procedure Base System Installation Checklist: [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: [O ] Install base system:[O ] Clock/timezone setup: [O ] User/password setup:[O ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Doing a netinstall starting from cd... The distro "wheezy" did not appear to be supported on ftp.us.debian.org and mirror.cc.columbia.edu. The apparently relevant message on VT4 contains: mirror does not support the specified release (wheezy) I searched the D-I mail archive for some kind of hint as to which mirror I should be using and/or how to specify it -- to no avail. Which mirror should I be using what did I do wrong... and where should I have looked, please? --- End Message --- --- Begin Message --- Quoting Matthew Variot (jmvar...@dock.net): > Okay, I will double check the network connectivity As a consequence: Given that your installation was a complete success, I do as usual with reports for successful installations: I close the bug..:-) This does not of course mean you weren't right to report. Knowing the installations are correct is important for the d-i team. Many thanks for your time testing the Debian Installer and reporting your results. Have fun with your new Debian system! signature.asc Description: Digital signature --- End Message ---
Bug#684128: PATCH: choice of binary or decimal disk storage units is runtime-configurable
On Thu, 9 Aug 2012 13:53:30 +0200 Christian PERRIER wrote: > I'd like to get other D-I people advice about including these changes > *now* as thereis always a risk of regressions which, at this point of > the release, we would like to avoid. That's an important consideration. I offer the following test scripts as evidence of non-regression. The h-to-l.sh and l-to-h.sh scripts should be run in busybox, once with the old definitions of human2longint() and longint2human(), and once with the new definitions, and the output saved to file. The old and new versions of human2longint() produce output that is byte-for-byte identical. The new versions of longint2human() produces output that is different from the old in the following respects, as previously advertised: - if the chosen unit is bytes, then decimal fractions are not printed - otherwise, two decimal places are printed - values such as 99 are rounded up to "1.00 MB" The third script, round.sh, when applied to the new version output, accounts for the first two causes of difference, leaving the third: $ ./round.sh h-to-l.sh Description: application/shellscript l-to-h.sh Description: application/shellscript round.sh Description: application/shellscript
