Re: Multi-arch netinst getting too big
On Mon, 2010-06-28 at 22:43 +0100, Steve McIntyre wrote:
Is this list part of the output somewhere when I do a local build
either
with easy-build.sh or by replicating the invocation from
debian-cd-setup
SVN?
It's an excerpt from make_disc_tree.log, produced when
make_disc_trees.pl is laying out packages into the temporary trees. It
logs into the temporary directory where debian-cd is working.
Thanks.
Subject: boot-x86: detect duplicates in the extra images used for
installation
Several files included under install.{386,amd} are actually identical
to
others. Rather than duplicating them attempt to detect this and
symlink
them.
I don't think sym-links are going to work - the filesystem code in
isolinux is very simple (e.g. it only supports basic 8.3 filenames!)
and I doubt it'll work. Hard links *might*, however.
OK, that's a one character change...
The files under install.{486,amd}/xen/ don't need to be readable by
isolinux, only by the xen tools. I've just had a quick look and they
appear to support hardlinks but not symlinks so that's another argument
for hardlinks. If we think isolinux would be a problem then we could
restrict this to files under install.*/xen/.
Ian.
---
Subject: boot-x86: detect duplicates in the extra images used for installation
Several files included under install.{386,amd} are actually identical to
others. Rather than duplicating them attempt to detect this and hardlink
them.
Since images can be downloaded from the web at build time it is not
always possible to detect identical files by looking for the symlinks
created by the debian-installer build. Instead we pass a list of
potential doppelgangers to extra_image each of which is checked for
similarity to the new image.
I added gtk/vmlinuz (which is always the same as plain vmlinuz) which
although not necessary makes it more explicit which kernel goes with the
initrd at very little cost.
Hardlinks are used in preference to symlinks since these are expected to
work better with isolinux and the Xen tools.
Signed-off-by: Ian Campbell i...@hellion.org.uk
diff --git a/tools/boot/squeeze/boot-x86 b/tools/boot/squeeze/boot-x86
index c0a5bdc..2189cbf 100644
--- a/tools/boot/squeeze/boot-x86
+++ b/tools/boot/squeeze/boot-x86
@@ -133,6 +133,8 @@ fi
extra_image () {
image=$1
+ doppelgangers=$2
+
dir=$(dirname $image)
mkdir -p $CDDIR/$INSTALLDIR/$dir
@@ -146,6 +148,15 @@ extra_image () {
wget $DI_WWW_HOME/cdrom/$image -O
$CDDIR/$INSTALLDIR/$image
fi
fi
+
+ for doppelganger in $doppelgangers ; do
+ if [ -f $CDDIR/$INSTALLDIR/$dir/$doppelganger ]
+ cmp -s $CDDIR/$INSTALLDIR/$image
$CDDIR/$INSTALLDIR/$dir/$doppelganger ; then
+ echo $image identical to $doppelganger. Linking
+ ln -nf $doppelganger $CDDIR/$INSTALLDIR/$image
+ break
+ fi
+ done
}
# If multiple desktops are to be supported, set the default one
@@ -231,7 +242,8 @@ if [ $THISTYPE = isolinux ]; then
fi
if [ -e boot$N/isolinux/f3.txt.withgtk ]; then
- extra_image gtk/initrd.gz
+ extra_image gtk/vmlinuz ../vmlinuz
+ extra_image gtk/initrd.gz ../initrd.gz
mv boot$N/isolinux/f3.txt.withgtk boot$N/isolinux/f3.txt
mv boot$N/isolinux/f4.txt.withgtk boot$N/isolinux/f4.txt
if [ -e boot$N/isolinux/isolinux.cfg.withgtk ]; then
@@ -243,8 +255,8 @@ if [ $THISTYPE = isolinux ]; then
rm -f boot$N/isolinux/isolinux.cfg.with*
if variant_enabled xen ; then
- extra_image xen/vmlinuz
- extra_image xen/initrd.gz
+ extra_image xen/vmlinuz ../vmlinuz ../gtk/vmlinuz
+ extra_image xen/initrd.gz ../initrd.gz ../gtk/initrd.gz
extra_image xen/xm-debian.cfg
fi
--
--
Ian Campbell
Generic Fortune.
signature.asc
Description: This is a digitally signed message part
Localization status for Debian Installer (June 29th update)
The nearly safe languages should now MOVE AND COMPLETE. It's about time, folks! In very short: 55 languages are in good shape (+1) 10 languages are in danger of being deactivated (-1) Progress: - Progress for Amharic (13 strings left in sl2). Technically still in danger but, as the translator proved to be active, I'm confident he'll make it The safe side - 42 languages are complete (+0): ar ast bg bn bs ca cs da de dz eo es eu fi fr ga gl gu he hi id it ja kk km ko lt lv mr nb pa pl pt ro ru sk sl sv th tr zh_CN zh_TW 5 languages were complete before hw-detect changes in sublevel 3 (+0): el et nl ta vi (reminder mailed on June 6th) 2 languages were complete before changes to sublevels 5 and 3 (+0): ml sq (reminder mailed on June 6th) (ml: l1 and l2 update on June 27th) 1 language complete for all sublevels but sublevel 3 (+0): ka 1 language complete for all first 3 sublevels (+0): nn The nearly safe side -- 5 languages have a few strings to update in sublevels 1 to 3 but have recently active translators who will probably easy cope with them (+1): am be hu pt_BR uk (be: reminder mailed on June 6th for sublevels 3 and 5) (pt_BR: reminder mailed June Tth for sublevels 2-5, ACK on June 10th) (hu: progress on June 15th) (uk: progress on June 27th. 2 remaining strings in sl2) (am: completed sublevel 1 on June 15th. Progress in sl2 June 28th) The unsafe side --- 1 languages had a few updates since lenny but not on a regular basis (-1). These languages are at risk of being deactivated for Squeeze if they are not complete for sublevels 1 and 2: tl (tl: mailed June 15th) 4 languages were complete in lenny but had no update since then (+0). These languages are at risk of being deactivated for Squeeze if they are not complete for sublevels 1 and 2: hr mk ne wo (mail to as many ppl as possible: June 15th) 4 active languages are in bad shape (+0) They were not complete for lenny and had no update since *before* the release of lenny. They're at risk of being deactivated except se which is an historical exception. Stats for sublevels 1 and 2: 093% ku 093% sr 092% cy 024% se The prospective side -- Prospective languages are languages that are not yet activated. They'll be activated if they reach 100% for sublevels 1 and 2. 2 Prospective language are doing progress(+0). Stats for sublevels 1 and 2: 071% fa 071% kn 10 Prospective languages are stalled(+0). Stats for sublevels 1 and 2: 097% si (P) 075% is (P) 069% ms (P) 043% br (P) 024% te (P) 023% mg (P) 015% xh (P) 013% ur (P) 003% hy (P) 000% lo (P) -- signature.asc Description: Digital signature
Bug#587451: installation-report: Gigabyte GA-586TX3
Quoting Márton Németh (nm...@freemail.hu): Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso , the build finished at Sun Jun 13 04:24:35 UTC 2010 Date: Date and time of the install Machine: Gigabyte GA-586TX3 desktop computer Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] 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
Bug#587451: marked as done (installation-report: Gigabyte GA-586TX3)
Your message dated Tue, 29 Jun 2010 06:37:33 +0200 with message-id 20100629043733.gf22...@mykerinos.kheops.frmug.org and subject line Re: Bug#587451: installation-report: Gigabyte GA-586TX3 has caused the Debian Bug report #587451, regarding installation-report: Gigabyte GA-586TX3 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.) -- 587451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso , the build finished at Sun Jun 13 04:24:35 UTC 2010 Date: Date and time of the install Machine: Gigabyte GA-586TX3 desktop computer Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [ ] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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=6.0 (squeeze) - installer build 20100613-03:54 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux madar 2.6.32-5-486 #1 Wed May 19 19:19:16 UTC 2010 i586 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 430TX - 82439TX MTXC [8086:7100] (rev 01) lspci -knn: 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01) lspci -knn: 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 01) lspci -knn: 00:08.0 SCSI storage controller [0100]: Adaptec AHA-2940/2940W / AIC-7871 [9004:7178] lspci -knn: Kernel driver in use: aic7xxx lspci -knn: 00:09.0 VGA compatible controller [0300]: S3 Inc. 86c764/765 [Trio32/64/64V+] [5333:8811] (rev 54) lspci -knn: 00:0a.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) lspci -knn: Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] lspci -knn: Kernel driver in use: 8139too lspci -knn: 00:0b.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 50) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:0b.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 50) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:0b.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 51) lspci -knn: Subsystem: First International Computer, Inc. Device [0925:1234] lspci -knn: Kernel driver in use: ehci_hcd usb-list: usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.32-5-486 ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 02 Device 01: UHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.32-5-486 uhci_hcd
Re: Multi-arch netinst getting too big
On Mon, 2010-06-28 at 22:46 +0100, Steve McIntyre wrote: On Wed, Jun 23, 2010 at 03:45:31PM +0200, Goswin von Brederlow wrote: Steve McIntyre st...@einval.com writes: The netinsts are meant to have the base system, yes. I can't see anything obvious myself that we can drop. Maybe time to give up on powerpc on that image, like we've done on the m-a DVD. Shame, but there's only so much stuff we can accommodate here. Anybody else have an opinion here? Frans/Joey? Just a crcy idea: Could the plain i386 kernel be droped instead? That would loose support for i486 and i586 cpus on the m-a CD. But is that needed there? That's an option, yes. We could strip out the kernels for 686 systems here, but I'd like to keep them on if at all possible to make this image as universally useful as possible. I'd be more convinced to simply drop powerpc instead, like we already did for the multi-arch DVD. Sounds reasonable to me, but then I'm not a powerpc user... Does the CD image need powerpc, powerpc-smp and powerpc64 kernels? Perhaps one of powerpc and powerpc-smp could be dropped (presuming that the smp variant still works on a UP system dropping the UP could well be reasonable). Do you have any idea where perl (not perl-base) comes from? python (not python-minimal) doesn't seem to be in the base system but is on the CD as well. Similarly nothing seems to pull in binutils or doc-linux-text deliberately. (I'm picking on these packages because they are the largest components under pool/main/*) I have a feeling I'm misunderstanding the technical definition of base system. I thought it was Priority: important or higher but perl, python and binutils are all Priority: standard. Ian. -- Ian Campbell Your happiness is intertwined with your outlook on life. signature.asc Description: This is a digitally signed message part
Re: Multi-arch netinst getting too big
On Mon, 2010-06-28 at 22:46 +0100, Steve McIntyre wrote: the multi-arch DVD. Another random thought, would we be better off enabling the xen variant on the m-a DVD rather than CD? Ian. -- -- Ian Campbell Pull the trigger and you're garbage. -- Lady Blue signature.asc Description: This is a digitally signed message part
Bug#587493: choose-mirror: Strange wget error message in the installation log
Package: choose-mirror
Version: 2.32
User: debian-...@lists.debian.org
UserTags: debian-edu
In Debian Edu, we automatically search for error: in the installation
log to detect errors during installation. When PXE installing, I get
this one:
Jun 28 23:18:29 main-menu[555]: (process:2840): wget: server returned
error: HTTP/1.0 404 Not Found
It is a bogus error message that is creating noise and confusion in
the Debian Edu test installation.
I've tried to track down where it come from, and as far as I
understand from the log it must originate from choose-mirror.
This is the relevant log fragment:
Jun 28 23:18:28 main-menu[555]: DEBUG: resolver (localization-config-udeb):
package doesn't exist (ignored)
Jun 28 23:18:28 anna-install: Queueing udeb partman-lvm for later installation
Jun 28 23:18:28 anna-install: Queueing udeb partman-auto-lvm for later
installation
Jun 28 23:18:28 main-menu[555]: INFO: Falling back to the package description
for auto-install
Jun 28 23:18:28 main-menu[555]: INFO: Falling back to the package description
for ai-choosers
Jun 28 23:18:28 main-menu[555]: INFO: Menu item 'choose-mirror' selected
Jun 28 23:18:28 anna-install: Queueing udeb apt-mirror-setup for later
installation
Jun 28 23:18:28 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/oldstable/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:28 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/stable/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/lenny/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/testing/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/squeeze/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/unstable/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/sid/Release -O - | grep -E
'^(Suite|Codename):'
Jun 28 23:18:29 choose-mirror[2847]: INFO: suite/codename set to:
testing/squeeze
Jun 28 23:18:29 choose-mirror[2847]: DEBUG: command: wget -q
http://ftp.skolelinux.org/debian/dists/squeeze/main/binary-i386/Release -O - |
grep ^Architecture:
Jun 28 23:18:29 anna-install: Queueing udeb squeeze-support for later
installation
Jun 28 23:18:29 main-menu[555]: (process:2840): wget: server returned error:
HTTP/1.0 404 Not Found
Jun 28 23:18:29 main-menu[555]: DEBUG: resolver (libc6-udeb): package doesn't
exist (ignored)
The URLs in the log seem to work, so I do not understand why wget is
complaining. Is there some other wget calls that are not reported to
the log?
The only wget calls I find in choose-mirror do not throw away error
messages. Perhaps they should? If so, this untested patch should
implement it:
debian/changelog
* Throw away stderr when calling wget, to avoid getting bogus error
messages in the installation log.
--- choose-mirror.c (revision 63581)
+++ choose-mirror.c (working copy)
@@ -243,7 +243,7 @@
free(directory);
directory = strdup(debconf-value);
- asprintf(command, wget -q %s://%s%s/dists/%s/Release -O - | grep -E
'^(Suite|Codename):',
+ asprintf(command, wget -q %s://%s%s/dists/%s/Release -O - 2/dev/null
| grep -E '^(Suite|Codename):',
protocol, hostname, directory, name);
di_log(DI_LOG_LEVEL_DEBUG, command: %s, command);
f = popen(command, r);
@@ -757,7 +757,7 @@
if (strlen(debconf-value) 0) {
codename = strdup(debconf-value);
- asprintf(command, wget -q
%s://%s%s/dists/%s/main/binary-%s/Release -O - | grep ^Architecture:,
+ asprintf(command, wget -q
%s://%s%s/dists/%s/main/binary-%s/Release -O - 2/dev/null | grep
^Architecture:,
protocol, hostname, directory, codename, ARCH_TEXT);
di_log(DI_LOG_LEVEL_DEBUG, command: %s, command);
f = popen(command, r);
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2fl8w5y41h0@login1.uio.no
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Petter Reinholdtsen wrote: In Debian Edu, we automatically search for error: in the installation log to detect errors during installation. Then it seems you need to make an exception for this error. When PXE installing, I get this one: Jun 28 23:18:29 main-menu[555]: (process:2840): wget: server returned error: HTTP/1.0 404 Not Found So, one wget results in a 404. As choose-mirror tries various possible suites and codenames and wgets are used for other purposes as well, a 404 is always a possibility. It is a bogus error message that is creating noise and confusion in the Debian Edu test installation. It's not bogus. It's a useful message for troubleshooting and debugging. The only thing that is a pity is that logging of the error messages to stderr gets delayed until the component completes. The URLs in the log seem to work, so I do not understand why wget is complaining. Is there some other wget calls that are not reported to the log? Did you check the code? The only wget calls I find in choose-mirror do not throw away error messages. Perhaps they should? If so, this untested patch should implement it: NACK. The errors are too useful to suppress. -- 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/201006291326.51214.elen...@planet.nl
Bug#413696: marked as done (root-access required to write FAT32 harddisk partitions)
Your message dated Tue, 29 Jun 2010 15:52:25 +0200 with message-id 1277819545.2966.8.ca...@rbg-a64.fritz.box and subject line No more relevant for me has caused the Debian Bug report #413696, regarding root-access required to write FAT32 harddisk partitions 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.) -- 413696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-k7 Version: 2.6.18+6 To write to a FAT32 harddisk partition, root-access is required. This is only for partitions on the harddisk. Hot-plug FAT32 drives (for example: an USB Drive), no root-access is required. Here: the /etc/fstab: # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hda7 / ext3defaults,errors=remount-ro 0 1 /dev/hda8 /home ext3defaults0 2 /dev/hda6 /share vfatdefaults0 0 /dev/hda9 noneswapsw 0 0 /dev/hdc/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 The /share partition is the FAT32 partition. The /etc/fstab was created by the installer and was not hand-modified. The /share directory has the following attributes: - owner: root - group: root - access-rights: 755 (octal) - owner: 7 (read, write and execute) - group: 5 (read and execute) - others: 5 (read and execute; without write) Changing the attributes of this directory with root-rights has no effect. I am using Debian GNU/Linux 4.0, kernel 2.6.18-4-k7 and libc6 2.3.6.dsl-13 ---End Message--- ---BeginMessage--- Hello, This is no more relevant for me. Regards Bernhard signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ---End Message---
Bug#534106: marked as done (Installation of Etch broken - signature check of release file failed on AMD64)
Your message dated Tue, 29 Jun 2010 15:55:05 +0200 with message-id 1277819705.2966.11.ca...@rbg-a64.fritz.box and subject line Etch archived in meantime has caused the Debian Bug report #534106, regarding Installation of Etch broken - signature check of release file failed on AMD64 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.) -- 534106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports severity: important Boot method: CD Image version: Etch businesscard 4.0r8 Date: 2009-06-21 Machine: Desktop PC 64Bit Processor: Athlon64 X2 3800+ Memory: 1024MB Partitions: - Output of lspci -nn: not performed 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:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Installation failed. Before installation of base system, the signature of release file is checked. This check fails, because the new key 55BE302B is missing. Output window: Install the base system Debootstrap Error Release file signed by unknown key (key id 9AA38DCD55BE302B) In /usr/share/keyrings/archive.gpg, there are only the keys for Etch: - Debian Archive Automatic Signing Key (2006) - Debian Archive Automatic Signing Key (4.0/etch) - Etch Stable Release Key - Debian-Volatile Archive Automatic Signing Key (4.0/etch) The new Lenny-Keys are missing. Hint: With the i386 Businesscard CD, there are all keys available. The signature check of release file was successfully. If you need further informations, please let me know. Regards Bernhard -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAko+beoACgkQkmK4ErR8cgT0lwCfWIjLpa3LLCXl7HMCJDa3KXi0 p6oAmgOTMXhisKM7L3wTPxH1cxepdo2J =X2pT -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Hello, because Etch is archived now, this is no more relevant for me. Regards Bernhard signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ---End Message---
Bug#587493: choose-mirror: Strange wget error message in the installation log
[Frans Pop] So, one wget results in a 404. As choose-mirror tries various possible suites and codenames and wgets are used for other purposes as well, a 404 is always a possibility. Sure, but all the URLs listed in the log are working, so it seem strange that one of them give 404. It's not bogus. It's a useful message for troubleshooting and debugging. The only thing that is a pity is that logging of the error messages to stderr gets delayed until the component completes. It is bogus, as all the URLs in the log are working when I test them manually, and it is close to impossible to figure out what URL was failing. The URLs in the log seem to work, so I do not understand why wget is complaining. Is there some other wget calls that are not reported to the log? Did you check the code? Yes. Only found the two mentioned in the patch, and neither seem to use a non-existing URL. :/ The only wget calls I find in choose-mirror do not throw away error messages. Perhaps they should? If so, this untested patch should implement it: NACK. The errors are too useful to suppress. I disagree. The error in question is almost useless. There is no way to see which URL was missing, and the message show up in the wrong location in the log. A useful error message would make it possible to figure out what is wrong. This one do not. :( If the error message continue to come from d-i, we need to filter it out in debian-edu, but I thought it best to try to get rid of it first. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629134401.gj24...@login1.uio.no
uboot-envtools-udeb or uboot-installer
Hi! Thibaut Girka is hacking on d-i for the FreeRunner as a GSoC project this year, Gaudenz mentor and I co-mentor. As you probably know the FR uses U-Boot as bootloader. When installation is finished, the environment for U-Boot needs modification so we can boot. Last year at DebConf I worked on an udeb for uboot-envtools which I dusted off recently. This udeb will: * Install uboot-envtools. * Sanity checks for /boot partition (U-boot needs this to be ext2). * Add menu entry in d-i main menu after boot loaders. Invoking it would modify the U-Boot environment with data gathered during installation. (I.e. partition which /boot resides on.) The work so far is in uboot-envtools packaging git repo on alioth. [0] Feedback is very welcome, also debian-boot has the final saying in udeb matters IIRC. Gaudenz commented on the udeb and said that it might be better to create an uboot-installer package, similar to other boot-loader installer packages in d-i. How should this proceed? Continue with uboot-envtools-udeb or create uboot-installer and put it in d-i repo? [0] http://git.debian.org/?p=pkg-fso/uboot-envtools.git;a=summary Best, Per -- 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/aanlktintrojav_6nrdlojuqf380jasw2kfezt2fiw...@mail.gmail.com
uboot-envtools-udeb or uboot-installer
Hi! Thibaut Girka is hacking on d-i for the FreeRunner as a GSoC project this year, Gaudenz mentor and I co-mentor. As you probably know the FR uses U-Boot as bootloader. When installation is finished, the environment for U-Boot needs modification so we can boot. Last year at DebConf I worked on an udeb for uboot-envtools which I dusted off recently. This udeb will: * Install uboot-envtools. * Sanity checks for /boot partition (U-boot needs this to be ext2). * Add menu entry in d-i main menu after boot loaders. Invoking it would modify the U-Boot environment with data gathered during installation. (I.e. partition which /boot resides on.) The work so far is in uboot-envtools packaging git repo on alioth. [0] Feedback is very welcome, also debian-boot has the final saying in udeb matters IIRC. Gaudenz commented on the udeb and said that it might be better to create an uboot-installer package, similar to other boot-loader installer packages in d-i. How should this proceed? Continue with uboot-envtools-udeb or create uboot-installer and put it in d-i repo? [0] http://git.debian.org/?p=pkg-fso/uboot-envtools.git;a=summary Best, Per -- 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/aanlktiliptjpclsiszqxx0rh0w_7je5k5nfkshhqf...@mail.gmail.com
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Petter Reinholdtsen wrote: [Frans Pop] So, one wget results in a 404. As choose-mirror tries various possible suites and codenames and wgets are used for other purposes as well, a 404 is always a possibility. Sure, but all the URLs listed in the log are working, so it seem strange that one of them give 404. So either it's due to a temporary mirror issue (which you'd want to know about), or it's from an unlogged wget. Or it's from a wget from a subprogram called by choose-mirror, in which case you patch won't even help. It's not bogus. It's a useful message for troubleshooting and debugging. The only thing that is a pity is that logging of the error messages to stderr gets delayed until the component completes. It is bogus, as all the URLs in the log are working when I test them manually, and it is close to impossible to figure out what URL was failing. No, it's not bogus. There *is* a wget that's failing. Whether it affects the end result of the install or not is another matter. wgets in choose-mirror can fail for various valid reasons. Most of them you want to know about for troubleshooting purposes. Examples are: (temporarily) broken mirrors, incomplete mirrors, broken proxies. I've seen 403s and 404s that have helped a lot tracing the cause of failed installs. Removing valid information from logs for cosmetic reasons is wrong. The URLs in the log seem to work, so I do not understand why wget is complaining. Is there some other wget calls that are not reported to the log? Did you check the code? Yes. Only found the two mentioned in the patch, and neither seem to use a non-existing URL. :/ So, you'll need to look a bit deeper. Usually we fix the *cause* of errors. We don't suppress errors for cosmetic reasons. The only wget calls I find in choose-mirror do not throw away error messages. Perhaps they should? If so, this untested patch should implement it: NACK. The errors are too useful to suppress. I disagree. The error in question is almost useless. There is no way to see which URL was missing, and the message show up in the wrong location in the log. A useful error message would make it possible to figure out what is wrong. This one do not. :( But it's currently all we have! And, as mentioned before, it *has* helped me a number of times in the past, both while tracing issues from installation reports and while debugging. Improving the error handling is valid. Simply removing the messages without replacing them with something else (better) is plain wrong. If the error message continue to come from d-i, we need to filter it out in debian-edu, but I thought it best to try to get rid of it first. If you can't come up with a proper solution for choose-mirror then that is the correct way to go. The primary purpose of the syslog is to help users and developers to find the cause of issues. Removing real error messages for cosmetic reasons does not improve the installer. -- 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/201006291822.17669.elen...@planet.nl
Bug#587493: choose-mirror: Strange wget error message in the installation log
On Tuesday 29 June 2010, Frans Pop wrote: NACK. The errors are too useful to suppress. I disagree. The error in question is almost useless. There is no way to see which URL was missing, and the message show up in the wrong location in the log. A useful error message would make it possible to figure out what is wrong. This one do not. :( Note that the order of the errors does match the order of calls. Together with other info I've always been able to match things up properly. I agree (and said so in my initial reply) that the current situation is not ideal, but that does not make the errors useless. -- 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/201006291824.33939.elen...@planet.nl
Bug#587493: choose-mirror: Strange wget error message in the installation log
so which of Petters wget calls failed? signature.asc Description: This is a digitally signed message part.
(lspci joined) emachines, which kernel module for lan card, expecially wired?
emachines, which kernel module for lan card? Si quelqu'un a un module compilé pour un noyau/kernel 2.6.26-1-686 pour la carte Ethernet : 01:00.0 Network controller: Atheros Communications Inc. Device 002b (rev 01) ou : 03:00.0 Ethernet controller: Attansic Technology Corp. Device 1062 (rev c0) debian je suis preneur : Would be great. http://www.array.org/ubuntu/ Found ubuntu would do the job, but the http repository for is unbrowseable lspci result on emachines 250-01G16i : 00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 01:00.0 Network controller: Atheros Communications Inc. Device 002b (rev 01) 03:00.0 Ethernet controller: Attansic Technology Corp. Device 1062 (rev c0) Q also on http://www.lapspecs.com/wiki/acer+aspire+one+d250#comment_35c53600db26b1f0f70208b3e46bd03f -- 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/4c2a46bc.4050...@thomas-harding.name
Bug#587570: New, non-broken squeeze images are needed
Package: debian-installer Version: 20100211 Severity: grave The installers are currently broken due to bug 583551, which prevents mkfs.ext3 et al. from working. New images are needed, per tytso in this message: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583551#117 Please ensure that the following executables, all of which use libblkid, run correctly: /bin/parted_devices /bin/parted_server /bin/partmap /sbin/blkid /sbin/e2fsck /sbin/fsck.ext2 /sbin/fsck.ext3 /sbin/fsck.ext4 /sbin/mke2fs /sbin/mkfs.ext2 /sbin/mkfs.ext3 /sbin/mkfs.ext4 /sbin/tune2fs /usr/sbin/fdisk (The non-functional parted_devices causes the installer to fail to detect any disks on the system. I can't say if that is a distinct bug, however.) -- 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/1277843952.30910.1382514...@webmail.messagingengine.com
Bug#587236: You can close this bug
Daily built from June 30 seems to boot OK Thierry -- 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/201006300355.01581.tchate...@free.fr
Bug#583735: sucess with SCSI HDD instead of IDE HDD
Hi, I tried the installation with an SCSI HDD instead of with IDE HDD on the same computer. The installation was sucessful, see the report at bug #587451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587451 Regards, Márton Németh -- 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/4c2acbb3.9010...@freemail.hu
Bug#587451: reboot problem
Hi, there was one small problem when I installed this computer: the reboot does not work correctly, only if I turn off the computer completely and turn it on again. The reboot does not work also with the installed system. When I type reboot on the console the system shuts down and it is restarted. However, the SCSI controller no longer recognises the installed HDD on boot. Somehow during the shutdown process the HDD is put to a state where it is not coming back again. When I turn off the computer and turn it on again the SCSI controller recognises the HDD and the system boots correctly. Regards, Márton Németh -- 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/4c2accae.2050...@freemail.hu
