Status of l10n uploads....
As requested by Cyril on IRC, sending this by mail: I might upload a few more packages for l10n in the upcoming daysunless that interferes too much with release plans. These are the ones that recently got a few string changes so it's hard to really anticipate when translators send updates. My rough plan is to leave them a few days and then upload . affected packages are: partman-basicfilesystems partman-iscsi partman-efi partman-lvm plus tzsetup but, there, chances are lower than updates come on -- signature.asc Description: Digital signature
Bug#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux >= 5
On Sun, Sep 21, 2014 at 03:51:52PM -0700, Chris Kuehl wrote: > On Sun, Sep 21, 2014 at 01:57:55PM +0200, Cyril Brulebois wrote: > > Looks like I could just blindly apply both patches, squashing them and > > crediting both of you then? > > Yup, I think that would do it. > > I can do additional sanity testing of the daily build after the patches > are applied, but already did pretty extensive testing on the netboot > image yesterday with the patches applied. Yeah, that works for me too. I wasn't in a hurry to push this until someone had actually tested the patch either (and I got buried again and didn't get to that myself), but I know that what it was _intended_ to do really works, so if it's been tested now, getting it into the dailies for wider testing seems like a good plan. Cheers, Ron -- 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/20140922015553.gd32...@hex.shelbyville.oz
finish-install_2.51_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Sep 2014 01:31:21 +0200 Source: finish-install Binary: finish-install Architecture: source all Version: 2.51 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Samuel Thibault Description: finish-install - Finish the installation and reboot (udeb) Changes: finish-install (2.51) unstable; urgency=medium . * Team upload * finish-install.d/07speakup: Enable accessibility GTK modules in MATE, fix permissions of files added to the user's home. Checksums-Sha1: 536d1fcbe56f975b1ca6972250c6fe67f1d9ba0a 1624 finish-install_2.51.dsc 9773b72a08e041cd371cb4cade9ef3bb33e0a399 52992 finish-install_2.51.tar.xz da63f0ba76de6d23d2dfee6c6ccdccb28f315905 29692 finish-install_2.51_all.udeb Checksums-Sha256: 7f3623be6d7e56bba9d59d8121ddfc9255977449886c000ee6c8599da5029e01 1624 finish-install_2.51.dsc 9e8dff4936db1901134b6adaad000cdf2d5e3ad63c923d48ee32d05c46ffa421 52992 finish-install_2.51.tar.xz 2637a0685d75001afaa0072ddd6c65324826a1686c0f715c7b523172cc64e599 29692 finish-install_2.51_all.udeb Files: 1f1a18faaa5f7b85b99d6a18da6a7549 29692 debian-installer required finish-install_2.51_all.udeb 955871f096250e46442dd2e50f3fe109 1624 debian-installer required finish-install_2.51.dsc b37c6c098a6f29f379a7e335f7640d1b 52992 debian-installer required finish-install_2.51.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUH2ALAAoJEBH0lP5vGG7Ndb0QAI+QgQoKo0J3I5HKSz/jFMBs xcjuEElHekwP76Y1Xau7LgclSZdb/tq35rT/IoznXm8U2iTXxGf6ZWL7jjMZYsMU toW5ciKaNL3XXWw40Pa5Lx8UiieKd2im5cWH1px6cQReyXDAo2UOGf8XwJAB3Yhp 8bhP5hNxUnR5llpjynk2z2GMZU5dppH1RJg+zlXDpzXoOkfI7f5VcW+Wh5IpfOY5 v4yAeHJNQS1wMKdpHPRPMQXnvLaLc/XuaeB2lVuNaavRVgJgSOHtagAt+FPEhkQ5 cK6pn51s90qYZDaCMyqRbdOEifYk1DgFvTEJ1NhPC/2VN+pmEBZR43G34WrEhfpq g0+hn/us+m/RCtY2lCK3qrBzJsHI/qC+b8E6QqOIBCPanMosYXfL2yvOAq3IXljn xjxSu7XUGCNePolR1YhCNT2YiNmhFvtE/ZkmVHSCnfdRTsshf4FAWRs9teaqiSTY yv8stog0zvzKUqfjEgNkvBVOQvktp8QJtv+PCZN6jAYgWpR+PJabdkbeRqE7kNiG rjBUeIu5PUOlkzKbqwGigLzHsgVsefDepo0Geg/fpTQqfktWaRkban+y6PgNnNnz L0YxfFuJe6BIwuADJWkWrVKP4CsjSg6l6MSdJqF4YEUT3VSZ1c9Te4ODqvZI5Jub cicsDeiD2kbNG3pizEor =XYnv -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/e1xvr6n-0002rg...@franck.debian.org
Processing of finish-install_2.51_amd64.changes
finish-install_2.51_amd64.changes uploaded successfully to localhost along with the files: finish-install_2.51_all.udeb finish-install_2.51.dsc finish-install_2.51.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/e1xvr4u-0002pz...@franck.debian.org
Bug#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux >= 5
On Sun, Sep 21, 2014 at 01:57:55PM +0200, Cyril Brulebois wrote: > Looks like I could just blindly apply both patches, squashing them and > crediting both of you then? Yup, I think that would do it. I can do additional sanity testing of the daily build after the patches are applied, but already did pretty extensive testing on the netboot image yesterday with the patches applied. Thanks! Chris -- 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/20140921225152.ga28...@ocf.berkeley.edu
Bug#762401: Installation kFreeBSD-amd64: OK with quirks
Package: installation-reports Boot method: CD Image version: Daily netinst kfreebsd-amd64 as of 2014-09-21 from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/kfreebsd-amd64/iso-cd/ Date: 2014-09-21 17:15 CEST Machine: noname Processor: Athlon64 X2 Memory: 3GByte Partitions: Disk /dev/ada0: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000919f8 Device Boot Start End Blocks Id System /dev/ada0p1 63 5863724 2931831 82 Linux swap / Solaris /dev/ada0p2 * 5863725 10352192848829102 a5 FreeBSD /dev/ada0p3 103522860 144541695205094187 HPFS/NTFS/exFAT /dev/ada0p4 201182056 488392064 143605004+ f W95 Ext'd (LBA) /dev/ada0p5 201182058 214853309 6835626 83 Linux /dev/ada0p6 214853373 29967650942411568+ 7 HPFS/NTFS/exFAT /dev/ada0p7 299676573 48063266990478048+ 83 Linux /dev/ada0p8 480632733 488392064 3879666 82 Linux swap / Solaris last_lba(): I don't know how to handle files with mode 20640 Output of lspci -knn (or lspci -nn): 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller [10de:0547] (rev a2) 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge [10de:0548] (rev a2) 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP67 SMBus [10de:0542] (rev a2) 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller [10de:0541] (rev a2) 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:04.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:06.0 IDE interface [0101]: NVIDIA Corporation MCP67 IDE Controller [10de:0560] (rev a1) 00:07.0 Audio device [0403]: NVIDIA Corporation MCP67 High Definition Audio [10de:055c] (rev a1) 00:08.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Bridge [10de:0561] (rev a2) 00:09.0 SATA controller [0106]: NVIDIA Corporation MCP67 AHCI Controller [10de:0554] (rev a2) 00:0b.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0562] (rev a2) 00:0c.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0d.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0e.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0f.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:11.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:12.0 VGA compatible controller [0300]: NVIDIA Corporation C68 [GeForce 7025 / nForce 630a] [10de:053e] (rev a2) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 01) 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: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: Installation itself was OK, with some errors in the installed system: - grub-install did not recognize Ubuntu 9.04 and Windows XP on the disk due to deficency of os-prober - X server did not recognize optimal screen resolution (1024x768 instead of 1280x1024), no way to change that - xterminal of XFCE4 desktop used US keymap, got to change it manually - german keymap is mostly OK, except Y and Z are exchanged (as in US map) - console (Alt-F1) used DE keymap, but no way to compose special characters like backslash or "@" with AltGr+key - unable to mount ext2/3 file systems: error message "/dev/ada0s7: no such device", but e.g. dd can read fr
Bug#762399: console-setup: WARNING: Unknown X keysym "permille"
Package: console-setup Version: 1.113 Severity: normal Setting up console-setup (1.113) ... WARNING: Unknown X keysym "permille" WARNING: Unknown X keysym "permille" WARNING: Unknown X keysym "permille" WARNING: Unknown X keysym "permille" WARNING: Unknown X keysym "ezh" WARNING: Unknown X keysym "EZH" WARNING: Unknown X keysym "ezh" WARNING: Unknown X keysym "EZH" WARNING: Unknown X keysym "ezh" WARNING: Unknown X keysym "EZH" WARNING: Unknown X keysym "ezh" WARNING: Unknown X keysym "EZH" Setting up libprotobuf9:i386 (2.6.0-3) ... Could this be caused by ckbcomp's built-in (X keysym -> kernel keysym) table missing these? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.113 ii debconf 1.5.53 ii keyboard-configuration 1.113 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.19-11 ii lsb-base 4.1+Debian13 Versions of packages keyboard-configuration depends on: ii debconf 1.5.53 ii initscripts 2.88dsf-53.4 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.113 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-1 -- debconf information: * console-setup/model: Generic 105-key (Intl) PC * console-setup/unsupported_config_options: true keyboard-configuration/unsupported_options: true keyboard-configuration/unsupported_options: true keyboard-configuration/unsupported_options: true * console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_config_layout: true keyboard-configuration/unsupported_config_layout: true keyboard-configuration/unsupported_config_layout: true * console-setup/store_defaults_in_debconf_db: true * console-setup/ask_detect: false * console-setup/ask_detect: false * console-setup/charmap: UTF-8 console-setup/use_system_font: console-setup/detect: console-setup/detect: debian-installer/console-setup/title: console-setup/guess_font: * console-setup/fontsize-text47: 8x16 * console-setup/compose: No compose key * keyboard-configuration/variantcode: * keyboard-configuration/variantcode: * keyboard-configuration/variantcode: keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_layout: true * console-setup/ttys: /dev/tty[1-9] * console-setup/codesetcode: guess * console-setup/layout: Finland * console-setup/unsupported_config_layout: true * console-setup/fontsize: 8x16 * console-setup/fontsize-fb: 16 console-setup/dont_ask_layout: * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/model: Generic 105-key (Intl) PC * console-setup/codeset: Uni1 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/toggle: No toggling * keyboard-configuration/toggle: No toggling * keyboard-configuration/toggle: No toggling * keyboard-configuration/layoutcode: fi * keyboard-configuration/layoutcode: fi * keyboard-configuration/layoutcode: fi * console-setup/modelcode: pc105 console-setup/framebuffer_only: * console-setup/unsupported_layout: true * console-setup/unsupported_options: true * keyboard-configuration/variant: Finnish * keyboard-configuration/variant: Finnish * keyboard-configuration/variant: Finnish * console-setup/detected: * console-setup/detected: * console-setup/variantcode: classic keyboard-configuration/other: keyboard-configuration/other: keyboard-configuration/unsupported_config_options: true keyboard-configuration/unsupported_config_options: true keyboard-configuration/unsupported_config_options: true * keyboard-configuration/compose: No compose key * keyboard-configuration/compose: No compose key * keyboard-configuration/compose: No compose key debian-installer/console-setup-udeb/title: debian-installer/console-setup-udeb/title: * console-setup/fontsize-text: 16 * keyboard-configuration/layout: * keyboard-configuration/layout: * keyboard-configuration/layout: * keyboard-configuration/altgr: Right Alt (AltGr) * keyboard-configuration/altgr: Right Alt (AltGr) * keyboard-configuration/altgr: Right Al
Re: Summary from the d-i / debian-cd BoF at DC14
On 09/09/14 17:51, Steve McIntyre wrote: > Discussion about trying to make desktops fit on 1 CD. XFCE and LXDE > both fit on 1 CD, Gnome and KDE basically don't fit any more. We > need to work out what to do there. > > Should we still build Gnome or KDE CDs at all? Not clear. Let's have > the discussion. Do you have numbers about this? Perhaps we could do something to make GNOME fit on a CD. Thanks, Emilio -- 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/541f0e14.5010...@debian.org
Processed: Re: Processed: Re: Bug#760442: installation-reports: Jessie installer hangs at 45% ‘starting partitioner’ on both desktop and Eee PC netbook
Processing commands for cont...@bugs.debian.org:
> # sorry - wrong bug:
> reassign 761148 debian-installer
Bug #761148 {Done: Steven Chamberlain } [src:partman-base]
Successful Installation
Bug reassigned from package 'src:partman-base' to 'debian-installer'.
No longer marked as found in versions partman-base/175.
No longer marked as fixed in versions partman-base/176.
> # meant to close this one instead:
> reassign 760442 src:partman-base
Bug #760442 [installation-reports] installation-reports: Jessie installer hangs
at 45% ‘starting partitioner’ on both desktop and Eee PC netbook
Bug reassigned from package 'installation-reports' to 'src:partman-base'.
Ignoring request to alter found versions of bug #760442 to the same values
previously set
Ignoring request to alter fixed versions of bug #760442 to the same values
previously set
> # jessie d-i 2014-08-12
> found 760442 175
Bug #760442 [src:partman-base] installation-reports: Jessie installer hangs at
45% ‘starting partitioner’ on both desktop and Eee PC netbook
Marked as found in versions partman-base/175.
> # jessie d-i 2014-09-06
> fixed 760442 176
Bug #760442 [src:partman-base] installation-reports: Jessie installer hangs at
45% ‘starting partitioner’ on both desktop and Eee PC netbook
Marked as fixed in versions partman-base/176.
> close 760442
Bug #760442 [src:partman-base] installation-reports: Jessie installer hangs at
45% ‘starting partitioner’ on both desktop and Eee PC netbook
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
760442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760442
761148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761148
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.c.141131266711424.transcr...@bugs.debian.org
Processed: Re: Bug#760442: installation-reports: Jessie installer hangs at 45% ‘starting partitioner’ on both desktop and Eee PC netbook
Processing commands for cont...@bugs.debian.org:
> reassign 761148 src:partman-base
Bug #761148 {Done: Miguel Figueiredo }
[installation-reports] Successful Installation
Bug reassigned from package 'installation-reports' to 'src:partman-base'.
Ignoring request to alter found versions of bug #761148 to the same values
previously set
Ignoring request to alter fixed versions of bug #761148 to the same values
previously set
> # jessie d-i 2014-08-12
> found 761148 175
Bug #761148 {Done: Miguel Figueiredo } [src:partman-base]
Successful Installation
Marked as found in versions partman-base/175 and reopened.
> # jessie d-i 2014-09-06
> fixed 761148 176
Bug #761148 [src:partman-base] Successful Installation
Marked as fixed in versions partman-base/176.
> close 761148
Bug #761148 [src:partman-base] Successful Installation
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
761148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761148
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.c.14113122868619.transcr...@bugs.debian.org
Bug#760442: installation-reports: Jessie installer hangs at 45% ‘starting partitioner’ on both desktop and Eee PC netbook
reassign 761148 src:partman-base # jessie d-i 2014-08-12 found 761148 175 # jessie d-i 2014-09-06 fixed 761148 176 close 761148 thanks > On Mon 2014-09-08 22.16.04, Steven Chamberlain wrote: > > There were significant changes to partman since d-i Beta 1, so it would > > be great if you could try more recent "Current daily snapshots" from: > > https://www.debian.org/devel/debian-installer/ On 13:12, Dr. Axel Stammler wrote: > I have (at least on the Eee PC netbook) and the installation went without any > problems (see also https://bugs.debian.org/761148#10 reporting success now on this same system) Thanks, 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/20140921151110.ga31...@squeeze.pyro.eu.org
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
On Sunday 21 September 2014 17:34:24 Michael Tokarev wrote: > This _is_ a glibc problem, and it can be trivially demonstrated by writing > a tiny program that calls, say, getaddrinfo() on its argument. When built > statically it always returns NOTFOUND, without any attempt to load any > nss modules or make dns queries or even do a /etc/hosts lookup. > > More, I don't think reassigning it to glibc will do any good either, because > static linking has been discoraged there for ages. Ok, thanks for the explanation. > I'm thinking about building busybox-static against uclibc. This means > compiling uclibc from uclibc-source during build time, but it is not much > more work than, say, compiling qemu (which also needs to link statically, > but has additional prob because it links with glib which can't be mixed > with uclibc). But anyway it will be a much bigger change than I'd like > to implement here. I understand your dilemma. Since this is outside my knowledge of expertise I can't asses the consequences of switching to a different glibc implementation nor offer a better idea. For my specific use case I can probably switch to the non-static version of busybox, although that doesn't resolve the issue reported here. I'd still be willing to test whatever solution you decide to implement. Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
> Petter Reinholdtsen (2014-09-21): > > > https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/artifact/results/snapshot_004900.png > > > > > > > This is very bad from a usability point of view, as normal people are > > not expected to know device paths. I got feedback from one of these normal people doing a wheezy install. The dialog instructed him to use /dev/sda if he wants to install GRUB to the first hard disk. But that was wrong! Since this was a USB- booted install, /dev/sda was the install media and /dev/sdb his first hard disk. grub-installer actually pre-filled the dialog with "/dev/sdb", meaning the code to not-install to USB media and guess something else, had worked correctly in this instance. There's a possibility that this has led to install reports implicating grub-installer, in which the code perhaps worked as intended but it was only the user's responses to wrong information that caused an issue. On 14:22, Cyril Brulebois wrote: > Well, I don't know anything about Debian Edu, but I'm pretty sure > there's another prompt before that in non-Edu, where devices are > listed, and where users can pick from. Yes, in jessie d-i there's now a preceding dialog that shows a list of devices and their identity. I think this is a great solution to the above problem. The problem here, affecting Debian Edu and AFAIK any preseed install, was that the new dialog defaults to 'Enter device manually' and the automated installer chooses that option. Therefore we see the original manual input dialog. During manual installs, *sometimes* something other than 'Enter device manually' is selected by default. We just need to figure out why that didn't happen in Petter's situation. Was /dev/sda the first hard disk in this case? Does grub-mkdevicemap in /target call it (hd0)? What is the full conents of /proc/partitions? grub-installer can log extra stuff to syslog if you uncomment some of the debug options at the top of the file. (We really should have jenkins.d.o redirect syslog to the virtual serial port, log it to a file and include it among the build artifacts. I think some of the Jenkins jobs do that, but not this one). 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/2014092111.gb31...@squeeze.pyro.eu.org
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
21.09.2014 17:19, Diederik de Haas wrote: > On Tuesday 12 August 2014 21:46:43 Michael Tokarev wrote: >> Nope. This is getaddrinfo() function. So it is glibc, not gcc or >> optimization. >> >> getaddrinfo() does not work in jessie glibc when linked statically. >> It immediately returns "Name or service not known" (rc=-2) without >> trying to read /etc/hosts or send dns queries. > > Any news on this bug? > > When I look at the diff from 1.22.0-6 to 1.22.0-7 it indeed doesn't seem > likely > that the issue is in busybox itself. > But when you look at the changelog of (e)glibc since 1.22.0-6 was released > there has been a new upstream release (2.19) and various patches relating to > dns resolving (as far as I can understand it). > > Maybe this should be reassigned to (e)glibc? This _is_ a glibc problem, and it can be trivially demonstrated by writing a tiny program that calls, say, getaddrinfo() on its argument. When built statically it always returns NOTFOUND, without any attempt to load any nss modules or make dns queries or even do a /etc/hosts lookup. More, I don't think reassigning it to glibc will do any good either, because static linking has been discoraged there for ages. I'm thinking about building busybox-static against uclibc. This means compiling uclibc from uclibc-source during build time, but it is not much more work than, say, compiling qemu (which also needs to link statically, but has additional prob because it links with glib which can't be mixed with uclibc). But anyway it will be a much bigger change than I'd like to implement here. If anyone has better idea please share. Thanks, /mjt -- 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/541ed3e0.9080...@msgid.tls.msk.ru
Bug#757941: busybox-static: DNS resolver stopped working in busybox-static version 1.22.0-7
On Tuesday 12 August 2014 21:46:43 Michael Tokarev wrote: > Nope. This is getaddrinfo() function. So it is glibc, not gcc or > optimization. > > getaddrinfo() does not work in jessie glibc when linked statically. > It immediately returns "Name or service not known" (rc=-2) without > trying to read /etc/hosts or send dns queries. Any news on this bug? When I look at the diff from 1.22.0-6 to 1.22.0-7 it indeed doesn't seem likely that the issue is in busybox itself. But when you look at the changelog of (e)glibc since 1.22.0-6 was released there has been a new upstream release (2.19) and various patches relating to dns resolving (as far as I can understand it). Maybe this should be reassigned to (e)glibc? -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#762345: task-mate-desktop: typo in tasks/mate-desktop "Relevance:" field
Processing control commands: > tag -1 pending Bug #762345 [tasksel] task-mate-desktop: typo in tasks/mate-desktop "Relevance:" field Added tag(s) pending. -- 762345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762345 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.b762345.141130233912047.transcr...@bugs.debian.org
Bug#762345: task-mate-desktop: typo in tasks/mate-desktop "Relevance:" field
Control: tag -1 pending Ben Armstrong (2014-09-21): > Package: tasksel > Version: 3.26 > Severity: normal > Tags: patch > > There is a typo in the tasks/mate-desktop file. I have attached a patch > to fix it. > diff -Nru tasksel-3.26/tasks/mate-desktop tasksel-3.26+nmu1/tasks/mate-desktop > --- tasksel-3.26/tasks/mate-desktop 2014-09-20 10:57:09.0 -0300 > +++ tasksel-3.26+nmu1/tasks/mate-desktop 2014-09-21 08:38:55.0 > -0300 > @@ -1,7 +1,7 @@ > Task: mate-desktop > Section: user > Parent: desktop > -Relvance: 7 > +Relevance: 7 > Test-default-desktop: 3 mate > Key: >task-mate-desktop If you had attached a patch against git you'd have noticed it was fixed in master already. :p Mraw, KiBi. signature.asc Description: Digital signature
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen (2014-09-21): > Just to be sure everyone reading this bug report understand what I see > as the problem, I present the installation as it is seen from Debian > Edu in Jessie. > > https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/ > > > show the grub dialog that show up at the end of the Debian Edu > installation. It ask people to type in the device path for grub. See > https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/artifact/results/snapshot_004900.png > > > for the dialog text. > > This is very bad from a usability point of view, as normal people are > not expected to know device paths. Well, I don't know anything about Debian Edu, but I'm pretty sure there's another prompt before that in non-Edu, where devices are listed, and where users can pick from. KiBi. signature.asc Description: Digital signature
Bug#762345: task-mate-desktop: typo in tasks/mate-desktop "Relevance:" field
Package: tasksel Version: 3.26 Severity: normal Tags: patch There is a typo in the tasks/mate-desktop file. I have attached a patch to fix it. diff -Nru tasksel-3.26/tasks/mate-desktop tasksel-3.26+nmu1/tasks/mate-desktop --- tasksel-3.26/tasks/mate-desktop 2014-09-20 10:57:09.0 -0300 +++ tasksel-3.26+nmu1/tasks/mate-desktop 2014-09-21 08:38:55.0 -0300 @@ -1,7 +1,7 @@ Task: mate-desktop Section: user Parent: desktop -Relvance: 7 +Relevance: 7 Test-default-desktop: 3 mate Key: task-mate-desktop
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Just to be sure everyone reading this bug report understand what I see as the problem, I present the installation as it is seen from Debian Edu in Jessie. https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/ > show the grub dialog that show up at the end of the Debian Edu installation. It ask people to type in the device path for grub. See https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/artifact/results/snapshot_004900.png > for the dialog text. This is very bad from a usability point of view, as normal people are not expected to know device paths. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140921120419.gd2...@ulrik.uio.no
Bug#762342: task-cinnamon-desktop: Please turn on display of Cinnamon desktop task
Package: tasksel Version: 3.26 Severity: normal Please turn on display of the Cinnamon desktop task. I have tested building Jessie live images with Cinnamon included and it seems to already provide a usable desktop. It would be useful for testers to be able to see Cinnamon so they can try it and help shake out any remaining bugs between now and the freeze. Thanks, Ben -- 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/20140921115852.5013.28624.reportbug@shade.edennet
Bug#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux >= 5
Ron (2014-09-21): > On Sat, Sep 20, 2014 at 02:28:24PM -0700, Chris Kuehl wrote: > > Thanks for your work on this -- we're also experiencing this bug in > > both jessie and sid daily netboot images in our PXE boot > > environment. > > > > On Thu, Aug 07, 2014 at 01:46:06PM +0200, Cyril Brulebois wrote: > > > I could apply it blindly but it'd be nice if someone else would > > > confirm it works fine. I've got other things cooking, but I might > > > end up testing it myself it nobody steps up. > > > > I might be building the image wrong, > > No, it looks like you did everything right afaics :) > > That was a blind and untested patch, working backward from what I'd > hand-hacked in place to get it working for me, at the end of a long > day, and the first time I'd ever even looked at this code ... > > It looks like I read $(TEMP_NETBOOT_DIR)/$(BOOT_SCREEN_DIR) wrong in > the surrounding code and assumed BOOT_SCREEN_DIR only had the > "/boot-screens" part in it. Or at least that's the only thing I can > think I must have done, since now that you've pointed, and I'm looking > at it again, your version of that link definitely looks like the right > one to me. > > Indeed amd64/netboot.cfg has: > BOOT_SCREEN_DIR = $(NETBOOT_PATH)/boot-screens/ > > Only the ia64 version appears to define or use it how I used it there. > > Thanks for actually testing this and sending a fixed patch! Looks like I could just blindly apply both patches, squashing them and crediting both of you then? It was low-priority (especially since untested) and I wasn't too keen on spending time on it, but if we have success reports, merging looks like a good idea. Mraw, KiBi. signature.asc Description: Digital signature
Bug#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux >= 5
On Sat, Sep 20, 2014 at 02:28:24PM -0700, Chris Kuehl wrote: > Hi all, > > Thanks for your work on this -- we're also experiencing this bug in both > jessie and sid daily netboot images in our PXE boot environment. > > On Thu, Aug 07, 2014 at 01:46:06PM +0200, Cyril Brulebois wrote: > > I could apply it blindly but it'd be nice if someone else would confirm > > it works fine. I've got other things cooking, but I might end up testing > > it myself it nobody steps up. > > I might be building the image wrong, No, it looks like you did everything right afaics :) That was a blind and untested patch, working backward from what I'd hand-hacked in place to get it working for me, at the end of a long day, and the first time I'd ever even looked at this code ... It looks like I read $(TEMP_NETBOOT_DIR)/$(BOOT_SCREEN_DIR) wrong in the surrounding code and assumed BOOT_SCREEN_DIR only had the "/boot-screens" part in it. Or at least that's the only thing I can think I must have done, since now that you've pointed, and I'm looking at it again, your version of that link definitely looks like the right one to me. Indeed amd64/netboot.cfg has: BOOT_SCREEN_DIR = $(NETBOOT_PATH)/boot-screens/ Only the ia64 version appears to define or use it how I used it there. Thanks for actually testing this and sending a fixed patch! Cheers, Ron > but after applying Ron's patch, I > get a symlink like the following in my netboot tarball: > > ldlinux.c32 -> > debian-installer/amd64/debian-installer/amd64/boot-screens//ldlinux.c32 > > Note that ``d-i/$arch'' is duplicated, and there is an extra slash > before ``ldlinux.c32''. > > During my build, the relevant vars were: > > NETBOOT_PATH=debian-installer/amd64 > BOOT_SCREEN_DIR=debian-installer/amd64/boot-screens/ > > I've attached a small patch (intended to be applied after Ron's) which > fixes the target path of the symlink on my sid build. > > With these two patches applied, the sid netboot image boots and installs > successfully in our environment. I'd be more than happy to help test any > additional work on this issue. > > Thanks! > Chris > From 89f74fdc2893a68d2baba8d13cff4846d92840e8 Mon Sep 17 00:00:00 2001 > From: Chris Kuehl > Date: Sat, 20 Sep 2014 21:00:11 + > Subject: [PATCH] Fix ldlinux.c32 symlink path > > The existing symlink creates a target path like: > debian-installer/amd64/debian-installer/amd64/boot-screens//ldlinux.c32 > > (note the duplicate of "d-i/amd64/" and the double slash after boot-screens) > --- > build/config/x86.cfg | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/build/config/x86.cfg b/build/config/x86.cfg > index 07f99b8..0bcd2a9 100644 > --- a/build/config/x86.cfg > +++ b/build/config/x86.cfg > @@ -393,7 +393,7 @@ arch_netboot_dir: x86_syslinux > ln -sf $(NETBOOT_PATH)/pxelinux.0 $(TEMP_NETBOOT_DIR)/pxelinux.0 > # This link is required because pxelinux only looks in the tftp root > # for this library (it does a PATH search for any others). > - ln -sf $(NETBOOT_PATH)/$(BOOT_SCREEN_DIR)/ldlinux.c32 > $(TEMP_NETBOOT_DIR)/ldlinux.c32 > + ln -sf $(BOOT_SCREEN_DIR)ldlinux.c32 $(TEMP_NETBOOT_DIR)/ldlinux.c32 > > set -e; \ > $(foreach file,$(wildcard $(TEMP_BOOT_SCREENS)/*.txt), \ > -- > 2.1.0 > -- 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/20140921081100.gc32...@hex.shelbyville.oz
