Your message dated Sun, 21 Jul 2013 14:32:43 +0200
with message-id <[email protected]>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #593258,
regarding base-installer: error: exiting on error base-installer/no_codename
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 [email protected]
immediately.)
--
593258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593258
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: debian-installer-launcher - cdebconf troubles / d-i installation fails
Package: debian-installer-launcher
Version: 2
Severity: important
*** Please type your report below this line ***
Hi,
I have got some errors when trying to install a live image using
debian-installer-launcher (s. below).
There are first few errors (missinf part of .so file names of cdebconf) however
it is possible to follow the installation to the virtual HDD (VirtualBox von
Oracle) only when chosing the english language (the live image has german as
defaults and comes up with german language settings). After installing all
files there is an error messages like "install failed" (s. below). I had the
same problems when booting on real hardware (without VirtualBox) and when
trying to install from the "install boot menu". I have repeated these tests few
times and will it execute some furthers tests with English as an default live
language.
regards,
Mark
PS. on the host I used live-build a23 to create live images
# ---- LOG from the install try
-------------------------------------------------------------------------
ironmux@ironmux:~$ dpkg -l cdebconf debian-installer-launcher
||/ Name Version Beschreibung
+++-=====================-=====================-==========================================================
ii cdebconf 0.150 Debian Configuration Management
System (C-implementation)
ii debian-installer-laun 2 Debian Installer desktop
launcher
ironmux@ironmux:~$ uname -a
Linux ironmux 2.6.32-5-486 #1 Sat Jul 24 01:48:25 UTC 2010 i686 GNU/Linux
# ---
ironmux@ironmux:~$ sudo debian-installer-launcher
Loading debian-installer...
non-network local connections being added to access control list
Starting system log daemon: syslogd, klogd.
/tmp/buildd/cdebconf-0.150/src/frontend.c:276 (frontend_new): Cannot load
frontend module /usr/lib/cdebconf/frontend/.so: /usr/lib/cdebconf/frontend/.so:
cannot open shared object file: No such file or directory
/tmp/buildd/cdebconf-0.150/src/frontend.c:276 (frontend_new): Cannot load
frontend module /usr/lib/cdebconf/frontend/.so: /usr/lib/cdebconf/frontend/.so:
cannot open shared object file: No such file or directory
# ---
+-------------------------------------+ [!!] Install the system
+--------------------------------------+
|
|
| Installation step failed
|
| An installation step failed. You can try to run the failing item again
from the menu, or skip it and |
| choose something else. The failing step is: Install the system
|
|
|
| <Continue>
|
|
|
+------------------------------------------------------------------------------------------------------+
<Tab> moves; <Space> selects; <Enter> activates buttons
# ---
+---------+ [?] Debian installer main menu
+---------+
|
|
| Choose the next step in the install process:
|
|
|
| Choose language
|
| Select a keyboard layout
|
| Detect and mount CD-ROM
|
| Load installer components from CD
|
| Detect network hardware
|
| Configure the network
|
| Set up users and passwords
|
| Configure the clock
|
| Detect disks
|
| Partition disks
|
| Install the system
|
| Configure the package manager
|
| Install the GRUB boot loader on a hard disk
|
| Install the LILO boot loader on a hard disk
|
| Continue without boot loader
|
| Finish the installation
|
| Change debconf priority
|
| Check the CD-ROM(s) integrity
|
| Save debug logs
|
| Execute a shell
|
| Abort the installation
|
|
|
+----------------------------------------------------+
<Tab> moves; <Space> selects; <Enter> activates buttons
# --- END of LOG
-----------------------------------------------------------------------
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages debian-installer-launcher depends on:
ii cdebconf [debconf-2.0] 0.150 Debian Configuration Management Sy
ii debconf [debconf-2.0] 1.5.33 Debian configuration management sy
ii gnome-terminal [x-terminal-em 2.30.2-1 The GNOME terminal emulator applic
ii psmisc 22.11-1 utilities that use the proc file s
debian-installer-launcher recommends no packages.
debian-installer-launcher suggests no packages.
-- debconf information:
debian-installer-launcher/kernel-mismatch/error:
debian-installer-launcher/kernel-mismatch/title:
--- End Message ---
--- Begin Message ---
reassign 716710 preseed,release-notes
forcemerge 704881 552563
tags 633128 + confirmed
reassign 633128 src:linux,kernel-wedge
affects 633128 debian-installer
reassign 653391 archdetect
forcemerge 653390 653391
reassign 655579 rootskel-gtk
reassign 690246 partman-lvm
affects 690246 debian-installer
severity 699430 wishlist
reassign 655124 kernel-wedge
affects 655124 debian-installer
thanks
Hi,
thank you for submitting bug reports concering debian-installer, much
appreciated.
I read through all the bugs mentioned here (and I'm sure they were read by
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old and/or
- they are wishlist but rather special + exotic and not have been acted on for
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to
close wishlist bugs.)
If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll
do if requested) or just file a new one - and that's often better, as the bug
log will be clearer and shorter and not contain cruft.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
