Bug#706659: [hw-detect] Claims some hardware (Realtek) needs merely ideal firmware to operate

[Filipus Klutiero]

Package: hw-detect
Version: 1.92
Severity: normal

check-missing-firmware.sh asks administrators whether they want to install 
non-free firmware which would expand the capabilities of their computer:


ask_load_firmware () {
if [ "$first_try" ]; then
first_try=""
return 0
fi

if [ "$NONINTERACTIVE" ]; then
if [ ! "$first_ask" ]; then
return 1
else
first_ask=""
return 0
fi
fi

db_subst hw-detect/load_firmware FILES "$files"
if ! db_input high hw-detect/load_firmware; then
if [ ! "$first_ask" ]; then
exit 1;
else
first_ask=""
fi
fi
if ! db_go; then
exit 10 # back up
fi
db_get hw-detect/load_firmware
if [ "$RET" = true ]; then
return 0
else
echo "$files" | tr ' ' '\n' >> $DENIED
return 1
fi
}


Typically, a device won't operate without the non-free firmware designed for 
it. The prompt therefore reads:

Template: hw-detect/load_firmware
Type: boolean
Default: true
# :sl2:
_Description: Load missing firmware from removable media?
  Some of your hardware needs non-free firmware files to operate. The
  firmware can be loaded from removable media, such as a USB stick or
  floppy.
  .
  The missing firmware files are: ${FILES}
  .
  If you have such media available now, insert it, and continue.


But it is not always the case that a device *needs* a firmware designed for it 
to operate. Some devices are simply enhanced by firmware. This is particularly 
true for my Ethernet card, a Realtek 8111F. While firmware-realtek does provide 
firmware for it, that firmware merely patches a bug in the default firmware. 
This bug apparently only happens in specific contexts. I have been using a PC 
with that card without the firmware for more than 2 weeks without any apparent 
network issue. Therefore, the prompt is misleading and may cause the user to 
install unneeded software or change hardware without a strong reason.

Ideally, d-i would explain the advantages of each firmware. The simplest 
solution would be to say the firmware enables /or/ helps a device. A middle 
solution could be to tag firmware as necessary or optional.

The opposite case (d-i not recommending firmware when it should) also exists 
(#649851). But fixing these cases will expose this bug even more. Radeon cards 
are good examples of devices which are improved by firmware without being 
unusable without.

--- System information. ---
Architecture: i386
Kernel: Linux 3.8-trunk-amd64

Debian Release: 7.0
990 testing security.debian.org
990 testing debian.mirror.iweb.ca
500 unstable debian.mirror.iweb.ca
1 experimental debian.mirror.iweb.ca

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#706659: Severity

[Filipus Klutiero]

Hi Ben,
could you explain why you changed this report's severity to wishlist? wishlist 
severity is designed for mere RFEs.


--
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/51870003.9090...@gmail.com

Bug#706659: Severity

[Filipus Klutiero]

severity 706659 normal
thanks

On 2013-05-05 21:29, Ben Hutchings wrote:

On Sun, 2013-05-05 at 20:57 -0400, Filipus Klutiero wrote:

Hi Ben,
could you explain why you changed this report's severity to wishlist?
wishlist severity is designed for mere RFEs.

This *is* a request for enhancement.


It is, but it is *not* a *mere* request for enhancement. wishlist severity is 
not designed for bug reports.


Previously, you wrote:

Therefore, the prompt is misleading and may cause the user to install
unneeded software or change hardware without a strong reason.

There are very few cases where the current statement is incorrect.  In
your example, the Realtek PHY firmware patch is needed because (if I
understand correctly) the ROM firmware is incompatible with a lot of
other Ethernet devices and won't establish a link.  Even though it may
not affect the specific cable and switch you were using during
installation, you will not want to find out about this bug when you plug
the machine in somewhere else!  (And I don't want to see this bug being
reported against the driver.)


The proper way to avoid such reports would be to warn admins if a buggy 
firmware is detected (and ideally offering an update).

Even if there are few cases where the current statement is incorrect, this is a 
bug. If you're confident that there are few cases, feel free to set severity to 
*minor*, but I have 2 personal PCs, and both have a device where the current 
formulation is inappropriate.

I don't know much about this specific example, but I'm skeptical about Realtek shipping a 
firmware which fails in "a lot" of scenarios, and continuing to pre-install 
that buggy firmware today.


I don't understand what you mean about changing hardware.  Is this about
people who think firmware is evil if it's on disk but not if it's in
flash?


I don't know, but there must be reasons why the missing firmware is not in 
Debian. Some admins may prefer changing their hardware to taking that risk.



Radeon cards are good examples of devices which are improved by
firmware without being unusable without.

The current AMD GPUs cannot be used without firmware, except through the
userland VESA driver which has appalling performance and doesn't support
the native resolution of most displays (or any widescreen displays,
AFAIK).  We definitely should be alerting users that this hardware does
need firmware to work properly.



OK, I was thinking about older GPUs such as Radeon HD 5650M, which can use the radeon driver without installing non-free 
firmware. Anyway, both of these cases are good examples; even in your case, the current prompt says firmware is needed for the 
devices to *operate*. "Operate" and "work properly" are not the same. And even "work properly" 
would not be quite true - if vesa works bug-free, I'd say the device can "work properly". Maybe not "work 
well".

Bug#706659: Severity

[Filipus Klutiero]

On 2013-05-06 00:33, Ben Hutchings wrote:

On Mon, 2013-05-06 at 00:01 -0400, Filipus Klutiero wrote:

severity 706659 normal
thanks

On 2013-05-05 21:29, Ben Hutchings wrote:

On Sun, 2013-05-05 at 20:57 -0400, Filipus Klutiero wrote:
[...]
Previously, you wrote:

Therefore, the prompt is misleading and may cause the user to install
unneeded software or change hardware without a strong reason.

There are very few cases where the current statement is incorrect.  In
your example, the Realtek PHY firmware patch is needed because (if I
understand correctly) the ROM firmware is incompatible with a lot of
other Ethernet devices and won't establish a link.  Even though it may
not affect the specific cable and switch you were using during
installation, you will not want to find out about this bug when you plug
the machine in somewhere else!  (And I don't want to see this bug being
reported against the driver.)

The proper way to avoid such reports would be to warn admins if a
buggy firmware is detected (and ideally offering an update).

It is detected.


What I meant is that the purpose of check-missing-firmware is to offer firmware 
which may enhance the target. Its purpose is not to detect buggy firmware and 
warn the admin, accessorily offering firmware updates to solve. If we want to 
avoid bogus bug reports against drivers, fixed firmware surely helps, but if 
the only firmware fixing the issue has downsides, that only solves part of the 
cases. We should also inform admins who prefer the original firmware of what 
problems that firmware will cause.




Even if there are few cases where the current statement is incorrect,
this is a bug. If you're confident that there are few cases, feel free
to set severity to minor, but I have 2 personal PCs, and both have a
device where the current formulation is inappropriate.

I don't know much about this specific example, but I'm skeptical about
Realtek shipping a firmware which fails in "a lot" of scenarios, and
continuing to pre-install that buggy firmware today.

If the firmware is loaded from ROM, as I suspect it is, then they can't
change it except by re-spinning the chip which is extremely expensive -
or, as they do, by patching it from the driver code.


Hum, thanks


I assume there are several different bugs fixed by the various different
firmware patches for each chip.


That's quite possible. Surely having a changelog or any explanation at all of 
the firmware's interest would be nice. But Debian comes with thousands of bugs. 
I think there should be a very good reason to prompt or warn about a bug (or 
bugs) when installing at default priority.

[...]

Radeon cards are good examples of devices which are improved by
firmware without being unusable without.

The current AMD GPUs cannot be used without firmware, except through the
userland VESA driver which has appalling performance and doesn't support
the native resolution of most displays (or any widescreen displays,
AFAIK).  We definitely should be alerting users that this hardware does
need firmware to work properly.


OK, I was thinking about older GPUs such as Radeon HD 5650M, which can
use the radeon driver without installing non-free firmware. Anyway,
both of these cases are good examples; even in your case, the current
prompt says firmware is needed for the devices to operate. "Operate"
and "work properly" are not the same. And even "work properly" would
not be quite true - if vesa works bug-free, I'd say the device can
"work properly". Maybe not "work well".

The VESA driver does its job OK, but the system as a whole is buggy if
it can't drive the connected displays at native resolution or use the
actual GPU.



We need to look at this in functional terms. If an algorithmic breakthrough is 
achieved tomorrow allowing CPUs to do anything GPUs do better, then we don't 
need to use GPUs anymore. The fact that systems would keep unused GPUs might be 
suboptimal, but that doesn't make these imaginary systems buggy. Similarly, if 
a resolution other than a native resolution doesn't cause problems other than 
making the user's experience suboptimal, we have a problem but not a bug.

Even if we had a bug, we wouldn't necessarily have one which prevents the 
device from operating. My problem is really with excessive alarming of admins. 
I don't have problems with warning or prompting, as long as this doesn't 
mislead admins. In fact, such information can be useful.


--
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/5188f402.4080...@gmail.com

Bug#708019: installation-reports: 2013-04-14 daily on ASUS F2A85-M/CSM: Limited success

[Filipus Klutiero]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: USB
Image version: Official Snapshot i386 NETINST Binary-1 20130414-09:20  
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 2013-04-15

Machine: IBM PC compatible clone, ASUS F2A85-M/CSM based
Partitions:
Filesystem Type 1K-blocks 
Used Available Use% Mounted on
rootfs rootfs37534240 
10306444  25314504  29% /
udev   devtmpfs 10240   
 0 10240   0% /dev
tmpfs  tmpfs   772836  
908771928   1% /run
/dev/disk/by-uuid/3890f9d1-e8db-4528-a7d3-cd4a1926d226 ext4  37534240 
10306444  25314504  29% /
tmpfs  tmpfs 5120   
 0  5120   0% /run/lock
tmpfs  tmpfs  1879280   
 4   1879276   1% /run/shm


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]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
Hardware detection claimed my Ethernet card needed non-free firmware to 
operate. This was reported as #706659.
As usual, os-prober misdetected Windows, as reported in #666764.

The real fun started after d-i finished its job. The installed system was 
mostly unusable. Thanks to tty-s, it was possible to identify a kernel bug and 
work around it by upgrading to Linux 3.8 (see #701054). From there, the system 
was mostly
usable. The main problem left was the poor screen resolution due to the poor 
X.org driver used (vesa). The graphics chip is somewhat new (ATI Southern 
Islands, integrated in the CPU). Installing the non-free package 
firmware-radeon managed to work around this.

Most stuff worked at that point. As I had forgotten to select KDE during the 
install, I originally had both GNOME and KDE installed, which exposed #692982. 
After working around that one, the only problem left was another - more minor - 
sound problem with non-KDE applications. speaker-test would fail and the Adobe 
Flash Player plugin in Iceweasel wouldn't output any sound. Unloading the 
snd_hda_intel LKM and [re]loading it with a parameter (modprobe snd_hda_intel 
index=1,0) worked around that. After I knew that sufficed, I made the 
workaround permanent by creating an asound.conf file.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130412"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux vinci 3.2.0-4-486 #1 Debian 3.2.41-2 i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 15h 
(Models 10h-1fh) Processor Root Complex [1022:1410]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
lspci -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices 
[AMD] nee ATI Trinity [Radeon HD 7660D] [1002:9901]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
lspci -knn: 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI 
Trinity HDMI Audio Controller [1002:9902]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
lspci -knn: 00:10.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB 
XHCI Controller [1022:7812] (rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:10.1 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB 
XHCI Controller [1022:7812] (rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] FCH 
SATA Controller [AHCI mode] [1022:7801] (rev 40)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB 
OHCI Controller [1022:7807] (rev 11)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB 
EHCI Controller [1022:7808] (rev 11)
lspci -knn: Su

Bug#720133: [installation-guide] uses old release numbering scheme (7.1 is not 7.0)

[Filipus Klutiero]

Package: installation-guide
Version: 20130503
Severity: minor

In wheezy, the release numbering scheme was changed to match the post-sarge 
practice of putting the major version number in the first version number. The 
first point release of wheezy is therefore Debian 7.1, not Debian 7.0.1. 
Consequently, while Debian 6.0 refers to all squeeze versions, Debian 7.0 does 
not refer to all wheezy versions. The installation guide needs an update to 
reflect that. http://www.debian.org/releases/stable/amd64/index.html.en 
currently contains:

This document contains installation instructions for the Debian GNU/Linux 7.0 
system (codename “wheezy”), for the 64-bit PC (“amd64”) architecture. It also 
contains pointers to more information and information on how to make the most 
of your new Debian system.


Besides the Abstract, the first section and section 1.6 are affected. I spotted 
these with a very quick scan, but I'm afraid there will be more.

By the way, http://www.debian.org/releases/wheezy/releasenotes has the same 
issue.

--
Filipus Klutiero
http://www.philippecloutier.com


--
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/521197aa.7050...@gmail.com

Bug#496019: installation-reports: Debian testing i386 20080820 on ECS K7S5A (SiS 735): Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: CD
Image version: Debian GNU/Linux testing "Lenny" - Official Snapshot i386 
NETINST  Binary-1 20080820-09:34
Date: 2008-08-21 06:21 GMT-5

Machine: ECS K7S5A (SiS 735 chipset), 256 MB SDRAM, 80 GB PATA
Partitions: 
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hda7 ext3 1921156   1146956676608  63% /
tmpfstmpfs  128268 0128268   0% /lib/init/rw
udev tmpfs   1024096 10144   1% /dev
tmpfstmpfs  128268 0128268   0% /dev/shm
/dev/hdc   iso9660  167428167428 0 100% /media/cdrom0


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:[O]
Overall install:[O]

Comments/Problems:

Everything went as expected...ignoring the problems I hit installing from sid 
d-i on this machine a few weeks ago :)

-- 

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="5.0 (lenny) - installer build 20080819-19:05"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux k7s5a 2.6.25-2-486 #1 Fri Jul 18 17:03:35 UTC 2008 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 735 
Host [1039:0735] (rev 01)
lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual 
PCI-to-PCI bridge (AGP) [1039:0001]
lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] 
SiS85C503/5513 (LPC Bridge) [1039:0018]
lspci -knn: 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 
SMBus Controller [1039:0016]
lspci -knn: 00:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 
1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 
1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 
[IDE] [1039:5513] (rev d0)
lspci -knn: Kernel driver in use: SIS_IDE
lspci -knn: Kernel modules: sis5513, pata_sis
lspci -knn: 00:02.6 Modem [0703]: Silicon Integrated Systems [SiS] AC'97 Modem 
Controller [1039:7013] (rev a0)
lspci -knn: 00:03.0 Ethernet controller [0200]: Silicon Integrated Systems 
[SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90)
lspci -knn: Kernel driver in use: sis900
lspci -knn: Kernel modules: sis900
lspci -knn: 00:0d.0 Multimedia audio controller [0401]: Ensoniq ES1371 
[AudioPCI-97] [1274:1371] (rev 08)
lspci -knn: 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV25 
[GeForce4 Ti 4200] [10de:0253] (rev a3)
lsmod: Module  Size  Used by
lsmod: ufs69764  0 
lsmod: qnx4   10628  0 
lsmod: ntfs  189760  0 
lsmod: dm_mod 54500  0 
lsmod: md_mod 72724  0 
lsmod: xfs   462836  0 
lsmod: reiserfs  199936  0 
lsmod: jfs   159452  0 
lsmod: ext3  117640  1 
lsmod: jbd38932  1 ext3
lsmod: vfat   11648  0 
lsmod: fat45852  1 vfat
lsmod: ext2   62216  0 
lsmod: mbcache 7680  2 ext3,ext2
lsmod: sis900 20736  0 
lsmod: mii 5248  1 sis900
lsmod: nls_utf82048  2 
lsmod: isofs  31908  0 
lsmod: nls_base6784  6 ntfs,jfs,vfat,fat,nls_utf8,isofs
lsmod: zlib_inflate   14208  1 isofs
lsmod: rsrc_nonstatic 11520  0 
lsmod: pcmcia_core36112  1 rsrc_nonstatic
lsmod: ide_generic 1280  0 [permanent]
lsmod: usb_storage76096  0 
lsmod: scsi_mod  138508  1 usb_storage
lsmod: vga16fb12940  2 
lsmod: vgastate8192  1 vga16fb
lsmod: fan 5508  0 
lsmod: ide_cd_mod 32672  0 
lsmod: cdrom  31776  1 ide_cd_mod
lsmod: ide_disk   13696  3 
lsmod: usbhid 39424  0 
lsmod: hid34816  1 usbhid
lsmod: ff_memless  5128  1 usbhid
lsmod: parport_pc 25636  0 
lsmod: parport32584

Bug#404554: tasksel-data: Please remove xsane from desktop

[Filipus Klutiero]

Package: tasksel-data
Version: 2.59
Severity: wishlist

KDE provides kooka for scanning. Having xsane in the base desktop is
bloat for KDE people. Please move xsane to the desktops which don't
provide their own scanning program.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#405421: netcfg: Unknown IEEE 1394/FireWire interface reported as "Ethernet or Fast Ethernet"

[Filipus Klutiero]

Package: netcfg
Version: 1.32
Severity: normal

d-i detects my FireWire card, but doesn't recognize the model as lspci:

01:01.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller
(rev 04)

Instead, it reports it as "Ethernet or Fast Ethernet", which is
misleading.

Unless you want to implement a way to distinguish Ethernet and FireWire,
a simple fix would be to change 

Template: netcfg/internal-eth
Type: text
_Description: Ethernet or Fast Ethernet

for something like
[...]
_Description: Ethernet or IEEE 1394

I've experienced this on a single machine, but if I read netcfg-common.c
right, the bug should happen for all 1394 devices.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410355: inconsistent behaviors between --task-packages desktop and install desktop

[Filipus Klutiero]

Package: tasksel
Version: 2.66
Severity: normal

When I tried to install the desktop task, tasksel went to install >400
packages, which I found surprising. When checking with --task-packages
that "install desktop" really installed the desktop task and not
"Desktop environment", tasksel outputted the list of packages of the
desktop task that I expected "install desktop" to install. However
remaining download time made it clear that tasksel was installing
gnome-desktop. I confirmed that with --test.

There are two issues: it doesn't seem possible to install just the
desktop task, plus install and --task-packages have inconsistent
behaviors. This is made quite worst by the fact that
debconf-apt-progress is not verbose about what it's doing and killing it
is bastard.


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)

Versions of packages tasksel depends on:
ii  aptitude  0.4.4-1terminal-based apt frontend
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  liblocale-gettext-perl1.05-1 Using libc functions for internati
ii  tasksel-data  2.66   Official tasks used for installati

tasksel recommends no packages.

-- debconf information:
  tasksel/title:
* tasksel/first: standard
  tasksel/tasks:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#411405: please move foomatic-gui out of common desktop task

[Filipus Klutiero]

Package: tasksel-data
Version: 2.66
Severity: wishlist

Please remove foomatic-gui from the common desktop task, presumably
moving it to gnome-desktop and maybe xfce-desktop.
I believe this will allow to avoid that gksu be pulled by the common
desktop task.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400966: Patch, security

[Filipus Klutiero]

I'm submitting the following patch, result of many corrections thanks to tests 
on all release architectures and kfreebsd-i386.

Seriously, this is an untested patch which I think is quite important to apply 
for Etch. We released Sarge without the PHP version recommended by upstream, 
and thankfully upstream provided security support for PHP 4 up to now, but 
shipping PHP 4 "by default" in Etch doesn't look good, given the state of 
upstream security in general and the time since PHP 4 was replaced. It is too 
late to remove PHP 4 from Etch but I expect it to have inappropriate support 
similar to what happened in woody, so we should avoid making it the default 
version.
Please let me know if you have a reason not to apply this patch.
--- web-server	2005-08-24 21:40:18.0 -0400
+++ web-server.5	2007-03-02 18:04:18.0 -0500
@@ -9,7 +9,7 @@
 Packages: task-fields
 Packages-list:
  apache2-doc
- libapache2-mod-php4
+ libapache2-mod-php5
  libapache2-mod-perl2
  libapache2-mod-python
  analog

Bug#413794: please remove language-env from french

[Filipus Klutiero]

Package: tasksel-data
Version: 2.66
Severity: wishlist

language-env currently has important bugs when used for french which
make it more problematic than helpful for French and probably many other
languages. It would be best to remove it at least from the french task. 
Japanese seems to be an exception but I still recommend to remove it from the 
key so that language-env can be removed from Debian if it's not fixed.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Some quotes about the issue at hand which should be consensual ... (Was: gtk 2.0.x or 2.9+ for etch g-i ?)

[Filipus Klutiero]

Sven Luther a écrit :


Some thoughts by someone else than me about this issue :
 

Those are not thoughts about this issue. Those are general impressions 
with a null argumentational value.



So, Frans and other of the d-i team, please read them, and think a bit before
you get offended because i propose some pro-active thinking for d-i.
 

Please read them too: "There are often good reaons for this [...]". And 
most of all, don't request others to read them before you did.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Can libdebian-installer be unblocked from entering testing?

[Filipus Klutiero]

Hi,
I'm trying to see if the newt transition could be done. I didn't see 
blockers yet. cdebconf needs to go in with this transition, which means 
libdebian-installer has to go in too.
I'd like somebody to (approve/explain issues with) unblocking 
libdebian-installer and cdebconf, so that I can later suggest a newt 
transition to d-release if this is approved.


Thanks for your critical contribution, and sorry if that mail is found 
superfluous.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[RECAP] Can libdebian-installer be unblocked from entering testing?

[Filipus Klutiero]

I'm trying to recapitulate on what was said. Please correct me if I got 
something wrong.


cdebconf

Joey Hess approved unblocking cdebconf 0.101. Then, Colin Watson noticed 
this thread after uploading 0.102 and said he was sorry. I discussed 
this with him on IRC:


 [...] first, what are the implications of the cdebconf 0.102 
upload? will it still be possible to unfreeze it soon?

 I guess it will take another couple of days, unfortunately
 unless it was already unfrozen in the britney run last night

So, Colin only said he was sorry because 0.102 needed usual testing and 
it will be possible to unblock it.



libd-i

Joey Hess:


Unblocking libdebian-installer 0.97 might cause problems due to this change:

 * archdetect: Rename sb1-swarm-bn to sb1-bcm91250a for consistency.
 

Then Martin Michlmayr clarified (at least for me) that the problem was 
risking to break a MIPS subarch getting 1 to 3 insts. on popcon for 
beta2 installs.


Bastian Blank replied to Martin's mail:


We will glue the libdi transition to the newt transition.

I failed to get a clarification from him, but from an IRC discussion I 
had with him the day before that post, I'm pretty sure he meant that an 
upcoming libdi transition and the newt transition would be tied *if* 
libdi doesn't transition to testing now.



In summary, the only problem which is expected from unblocking libd-i is 
to break beta2 installs on a rare subarch. I can't see how this would be 
worse than risking to delay the newt transition, but if some people 
aren't convinced, what's the alternative? If it is waiting for beta3, 
does that mean the upcoming libd-i transition Bastian warned about will 
be tied? If so, what should this libd-i transition look like?



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#279855: Blocked by missing PPP support

[Filipus Klutiero]

Note that this is blocked for Etch by the fact that [decent] PPP support 
is no more present.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382577: installation-report: deprecated tail call "tail +2"

[Filipus Klutiero]

Package: installation-report
Version: 2.17
Severity: minor

/usr/share/bug/installation-report/script calls tail with "tail +2" at line 53, 
which is deprecated, generating a
tail: Warning: "+number" syntax is deprecated, please use "-n +number"

A trivial correction should fix this.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382735: Oops

[Filipus Klutiero]

A reportbug bug explains the duplicated information. Please ignore the 
second part of the report.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Updating linux-2.6 in testing (to 2.6.17)

[Filipus Klutiero]

Hi,
3 days ago Frederik Schueler mentioned the following item for then's 
today in his Kernel schedule proposal for Etch:



start migration of 2.6.17 kernel and udebs to testing
 

I asked him on #d-kernel precisely what was being done about this but 
got no answer. I didn't see anything happen and currently linux-2.6 is 
still frozen. Today I saw a linux-2.6.16 upload, which I found 
suspicious since I can't see its use if 2.6.17 is about to transition to 
testing. I mentioned this on #d-release, and resulting discussion with 
vorlon made me realize that it's possible that the Linux team wouldn't 
necessarily feel responsible for requesting a linux-2.6 update, as 
according to him, "the reason it was frozen in the first place was to 
keep 2.6.17 from clobbering 2.6.16 in etch before beta3".


Since I'm afraid that the Linux team isn't doing anything to update 
linux-2.6 in testing and that nothing else feels responsible for doing 
so, I'm initiating the discussion. I request the release team to force a 
linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are 
raised until then. If you have an objection, please raise it on 
debian-release only (dropping d-boot and d-kernel).



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

)Request should be ignored, linux-2.6 update responsibility and new 2.6.17 plans

[Filipus Klutiero]

Filipus Klutiero a écrit :


Hi,
3 days ago Frederik Schueler mentioned the following item for then's 
today in his Kernel schedule proposal for Etch:



start migration of 2.6.17 kernel and udebs to testing
 

I asked him on #d-kernel precisely what was being done about this but 
got no answer. I didn't see anything happen and currently linux-2.6 is 
still frozen. Today I saw a linux-2.6.16 upload, which I found 
suspicious since I can't see its use if 2.6.17 is about to transition 
to testing.


About 24 hours ago I talked with fjp on #d-boot about this, and I 
learned that he considers the kernel team to be responsible for 
requesting a linux-2.6 update in testing. He also mentioned that he 
already gave an OK regarding d-i to update linux-2.6 to 2.6.17.


Just after I talked with fs, and got:
 I guess we will try to push 2.6.17 to testing next week
and after trying to understand why not now:
 we have some things pending for the next 2.6.17 upload, including 
2.6.17.9
which is not very useful, as 2.6.17.9 doesn't seem to fix any 2.6.17 
regression from 2.6.16, but at least the Linux team still plans to push 
2.6.17 in [at this point] a reasonable timeframe.


Since fjp can clearly define who is responsible to request a linux-2.6 
update, and this matches the Linux team's new plans mentioned by fs, I 
drop any responsibility regarding this update and defer to the Linux 
team. Release team, please ignore my request.


Thanks to fjp and fs. I'm sorry if I jumped to conclusions too fast.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#500206: [installation-guide] "4.4.1. Copying the files the easy way" needs greater care to avoid data loss

[Filipus Klutiero]

Package: installation-guide
Severity: normal
Tags: security

Section 4.4.1. Copying the files — the easy way contains:

You only have to extract it directly to your USB stick: 
# zcat boot.img.gz > /dev/sda

Sounds simple and easy, doesn't it? Granted, there's a bold Warning just 
below:
Using this method will destroy anything already on the device. Make sure that 
you use the correct device name for your USB stick.

The fact that the device can be something else than /dev/sda is mentioned in 
the introduction of 4.4:
try to find out which SCSI device the USB stick has been mapped to (in this 
example /dev/sda is used)

This needs to be more clear. Users *need* to find out which device their USB 
stick is mapped to, and the fact that /dev/sda is only an example shouldn't 
be mentioned *in parentheses*. Also, the sentence introducing the command 
should be more like

"If and only if your USB stick is mapped to /dev/sda, you can extract 
boot.img.gz directly with the following command:"

I also suggest obscuring the command by replacing /dev/sda with a variable, 
say $DEVICE, so that the reader has to take the time to stop and read a bit. 
The device suggested could be /dev/sdb, so that a laptop user with 1 SATA 
hard drive won't lose his primary disk with that command.

Furthermore, since the warning starts with "Using this method will destroy 
anything already on the device.", one may think "Oh OK, that warning is just 
going to tell me to save the data on my USB key elsewhere, but I have nothing 
of value on the key, so let's skip the second sentence and run the command."
It should be clear from the first sentence, that running this may corrupt your 
primary hard drive.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#500283: [installation-guide] Please clarify which Optional kernel modules should be used to create a flexible USB Memory Stick (4.4.2.1)

[Filipus Klutiero]

Package: installation-guide
Severity: wishlist

4.4.2.1. USB stick partitioning on Intel x86
contains:

copy the following files from the Debian archives to the stick:
[...]
Optional kernel modules

Although the "from the Debian archives" is quite vague, the file name helps to 
find the first files. Finding "Optional kernel modules" seems to be harder. 
Unless I'm missing something obvious, this pretty much makes the section 
useless.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#501175: [installation-guide] 6.2: please improve iso-scan component description

[Filipus Klutiero]

Package: installation-guide
Severity: wishlist
Tags: patch

In section 6.2, iso-scan is described as

Looks for ISO file systems, which may be on a CD-ROM or on the hard drive.

This sounded to me as if iso-scan would only look on the [primary] hard drive, 
but it looks on any hard drive (including external hard drives connected via 
USB). Also, there should be no distinction between CD-ROM-s and other optical 
disks. So I suggest

Looks for ISO images, which may be on an optical disk or on a hard drive.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#501176: installation-reports: d-i lenny 20081004 netboot i386 on SL-NV400-L64: Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: network
Image version: 
http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz 20081004
Date: 2008-10-05 01:18:09.0 -0400

Machine: Soltek NV400-L64-based clone (desktop)
Partitions:

/dev/hda6 ext3 9614116   3047328   6078416  34% /
tmpfstmpfs  388000 0388000   0% /lib/init/rw
udev tmpfs   1024088 10152   1% /dev
tmpfstmpfs  388000 0388000   0% /dev/shm

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:[O]
Overall install:[O]

Comments/Problems:

Almost everything went as expected.

-- 

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 [EMAIL PROTECTED]

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="5.0 (lenny) - installer build 20081004-19:05"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
umame -a: Linux andrea 2.6.26-1-486 #1 Wed Sep 24 14:06:01 UTC 2008 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: nVidia Corporation nForce2 IGP2 
[10de:01e0] (rev c1)
lspci -knn: 00:00.1 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 0 [10de:01ea] (rev c1)
lspci -knn: 00:00.2 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 4 [10de:01ee] (rev c1)
lspci -knn: 00:00.3 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 3 [10de:01ed] (rev c1)
lspci -knn: 00:00.4 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 2 [10de:01ec] (rev c1)
lspci -knn: 00:00.5 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 5 [10de:01ef] (rev c1)
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation nForce2 ISA Bridge 
[10de:0060] (rev a4)
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation nForce2 SMBus (MCP) 
[10de:0064] (rev a2)
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0067] (rev a4)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0067] (rev a4)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.2 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0068] (rev a4)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:04.0 Ethernet controller [0200]: nVidia Corporation nForce2 
Ethernet Controller [10de:0066] (rev a1)
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: Kernel modules: forcedeth
lspci -knn: 00:06.0 Multimedia audio controller [0401]: nVidia Corporation 
nForce2 AC97 Audio Controler (MCP) [10de:006a] (rev a1)
lspci -knn: 00:08.0 PCI bridge [0604]: nVidia Corporation nForce2 External PCI 
Bridge [10de:006c] (rev a3)
lspci -knn: 00:09.0 IDE interface [0101]: nVidia Corporation nForce2 IDE 
[10de:0065] (rev a2)
lspci -knn: Kernel driver in use: AMD_IDE
lspci -knn: Kernel modules: amd74xx
lspci -knn: 00:1e.0 PCI bridge [0604]: nVidia Corporation nForce2 AGP 
[10de:01e8] (rev c1)
lspci -knn: 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV25 
[GeForce4 Ti 4600] [10de:0250] (rev a3)
lsmod: Module  Size  Used by
lsmod: ufs63620  0 
lsmod: qnx47684  0 
lsmod: ntfs  180416  0 
lsmod: dm_mod 45384  0 
lsmod: md_mod 65940  0 
lsmod: jfs   148060  0 
lsmod: nls_utf81664  4 
lsmod: sd_mod 21904  2 
lsmod: loop   12428  1 
lsmod: isofs  27812  0 
lsmod: zlib_inflate   14080  1 isofs
lsmod: xfs   446836  0 
lsmod: vfat8832  0 
lsmod: fat39964  1 vfat
lsmod: nls_base6528  6 ntfs,jfs,nls_utf8,isofs,vfat,fat
lsmod: reiserfs  187008  0 
lsmod: ext3  103432  2 
lsmod: jbd35092  1 ext3
lsmod: ext2   52616  0 
lsmod: mbcache 6656  2 ext3,ext2
lsmod: ide_generic

Bug#501278: installation-reports: d-i lenny 20081004 netboot i386 on ECS K7S5A (SiS 735): Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: network
Image version: 
http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz 20081004
Date: 2008-10-06 02:38:59.0 -0400

Machine: ECS K7S5A (SiS 735 chipset), 256 MB SDRAM, 80 GB PATA
Partitions:
/dev/hda7 ext3 4214036   3025112974860  76% /
tmpfstmpfs  128200 0128200   0% /lib/init/rw
udev tmpfs   10240   112 10128   2% /dev
tmpfstmpfs  128200 0128200   0% /dev/shm
/dev/sda1 ext357669728  27792728  26947552  51% /media/disk


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:[O]
Overall install:[O]

Comments/Problems:

Almost everything went as expected.

-- 

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 [EMAIL PROTECTED]

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="5.0 (lenny) - installer build 20081004-19:05"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
umame -a: Linux k7s5a 2.6.26-1-486 #1 Wed Sep 24 14:06:01 UTC 2008 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 735 
Host [1039:0735] (rev 01)
lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual 
PCI-to-PCI bridge (AGP) [1039:0001]
lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] 
SiS85C503/5513 (LPC Bridge) [1039:0018]
lspci -knn: 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 
SMBus Controller [1039:0016]
lspci -knn: 00:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 
1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 
1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 
[IDE] [1039:5513] (rev d0)
lspci -knn: Kernel driver in use: SIS_IDE
lspci -knn: Kernel modules: sis5513
lspci -knn: 00:02.6 Modem [0703]: Silicon Integrated Systems [SiS] AC'97 Modem 
Controller [1039:7013] (rev a0)
lspci -knn: 00:03.0 Ethernet controller [0200]: Silicon Integrated Systems 
[SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90)
lspci -knn: Kernel driver in use: sis900
lspci -knn: Kernel modules: sis900
lspci -knn: 00:0d.0 Multimedia audio controller [0401]: Ensoniq ES1371 
[AudioPCI-97] [1274:1371] (rev 08)
lspci -knn: 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV25 
[GeForce4 Ti 4200] [10de:0253] (rev a3)
lsmod: Module  Size  Used by
lsmod: ufs63620  0 
lsmod: qnx47684  0 
lsmod: ntfs  180416  0 
lsmod: dm_mod 45384  0 
lsmod: md_mod 65940  0 
lsmod: jfs   148060  0 
lsmod: nls_utf81792  4 
lsmod: loop   12428  1 
lsmod: isofs  27812  0 
lsmod: zlib_inflate   14080  1 isofs
lsmod: xfs   446836  0 
lsmod: vfat8960  0 
lsmod: fat40220  1 vfat
lsmod: nls_base6528  6 ntfs,jfs,nls_utf8,isofs,vfat,fat
lsmod: reiserfs  187008  0 
lsmod: ext3  103432  1 
lsmod: jbd35092  1 ext3
lsmod: ext2   52616  1 
lsmod: mbcache 6656  2 ext3,ext2
lsmod: ide_generic 2432  0 [permanent]
lsmod: ide_cd_mod 27652  0 
lsmod: cdrom  30240  1 ide_cd_mod
lsmod: ide_disk   10496  3 
lsmod: parport_pc 22436  0 
lsmod: parport30408  1 parport_pc
lsmod: sis5513 6788  0 [permanent]
lsmod: ide_core   95144  4 ide_generic,ide_cd_mod,ide_disk,sis5513
lsmod: rsrc_nonstatic  9344  0 
lsmod: pcmcia_core31760  1 rsrc_nonstatic
lsmod: sd_mod 21904  2 
lsmod: usbhid 35456  0 
lsmod: hid32000  1 usbhid
lsmod: ff_memless  

Bug#501175: [installation-guide] 6.2: please improve iso-scan component description

[Filipus Klutiero]

Le October 15, 2008 05:34:44 am Frans Pop, vous avez écrit :
> tags 501175 pending
> thanks
>
> On Sunday 05 October 2008, Filipus Klutiero wrote:
> > So I suggest
> > Looks for ISO images, which may be on an optical disk or on a hard
> > drive.
>
> Actually it does not look on real CDs at all, so I've changed it to:
> Searches for ISO images (.iso files) on hard drives.
Heh, that's a good point too :-P

Thank you



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Success on Compal FL90 (Re: Call for testing of RC2 images)

[Filipus Klutiero]

Everything went as expected installing 
debian-Lenny-DI-rc2-amd64-businesscard.iso on a Compal FL90.


Thank you very much
 



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#514190: installation-reports: d-i lenny RC2 amd64 on Compal FL90 (PM965): Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/.lenny_bibble/amd64/iso-cd/debian-Lenny-DI-rc2-amd64-businesscard.iso
 
2009-01-28
Date: Jan 30 05:21:49

Machine: Compal FL90 with Intel Core 2 Duo T7500
Partitions:
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/sda8 ext3 4134900   1418452   2506400  37% /
tmpfstmpfs 1031212 0   1031212   0% /lib/init/rw
udev tmpfs   10240   116 10124   2% /dev
tmpfstmpfs 1031212 0   1031212   0% /dev/shm
/dev/hda   iso9660   37630 37630 0 100% /media/cdrom0


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:[O]
Overall install:[P]

Comments/Problems:

This is an install on the same target as #497318. Everything went as expected, 
which means that the 3 issues mentioned there were fixed. Additionally, I 
used amd64 instead of i386. The test 
image I downloaded is supposed to be the same as the final RC2.

kudos.

-- 

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 20090123"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux vinci 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 
x86_64 unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 
PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 0c)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 
Family) HD Audio Controller [8086:284b] (rev 03)
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 2 [8086:2841] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 3 [8086:2843] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 4 [8086:2845] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 5 [8086:2847] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #3 [8086:2832] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.7 USB Controller [0c0

Bug#468668: Unable to start d-i after running win32-loader (empty GRUB)

[Filipus Klutiero]

Package: win32-loader
Version: 0.6.3
Severity: normal

On a new laptop on which I never used win32-loader successfully before, I 
succeeded to run win32-loader now that it works on Vista 64-bit (thank you), 
but it failed once rebooting and trying to launch d-i. After selecting in 
Windows' bootloader to run d-i, I get a GRUB 2 menu with no choices. A "first 
choice" was selected, but there was no label and I only saw that it was 
highlighted. I couldn't boot it.
I can't remember what's supposed to happen after choosing to run d-i, so I 
don't know whether I should see choices or whether it's abnormal that I see 
GRUB.
I don't know the actual win32-loader version I used, I'm putting 0.6.3 because 
that's the current version and I downloaded debian.exe yesterday.
This only happened on 1 machine once. Sorry to have no more clues, I'd be 
happy to provide you more information if you need.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400715: apt-setup: typo "n'a pas acceder" in French translation

[Filipus Klutiero]

Package: apt-setup
Version: 1:0.16
Severity: minor
Tags: l10n

trunk/packages/po/fr.po revision 42479 contains at line 6111 "Le
programme d'installation n'a pas accéder au  miroir."
There's a "pu" missing, so this should read "Le programme d'installation n'a 
pas pu accéder au miroir."

Bug#400966: tasksel-data: Please make web-server install PHP 5, not 4

[Filipus Klutiero]

Package: tasksel-data
Version: 2.58
Severity: wishlist

The web-server task should install PHP5, not 4. Please substitute
libapache2-mod-php4 by libapache2-mod-php5.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400967: installation-manual: E.2 Contributing to This Document - package for bug reports should be updated

[Filipus Klutiero]

Package: installation-manual
Severity: minor

Section E.2 reads that "If you have problems or suggestions regarding
this document, you should probably submit them as a bug report against
the package debian-installer-manual."
debian-installer-manual should be changed for installation-guide.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400969: installation-manual: 6.3.1.5. Configuring Network - etherconf will not be in Etch

[Filipus Klutiero]

Package: installation-manual
Severity: minor

The note in section 6.3.1.5 ends with "Alternatively, you can install
etherconf, which will step you through your network setup."
This should be removed, as etherconf is no longer in Etch.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415634: "Blocked" by #401861

[Filipus Klutiero]

FWIW, I've already filed a report for a package dealing with KDE extragear; 
see #401861.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#515715: installation-reports: d-i 5.0.0 DVD 1 i386 on ASUS Z71A: Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: DVD
Image version: 
http://cdimage.debian.org/cdimage/release/5.0.0/i386/iso-dvd/debian-500-i386-DVD-1.iso
 
2009-02-14
Date: Feb 16 18:00

Machine: ASUS Z71A
Partitions:
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hda5 ext3 7692876   2323828   4978272  32% /
tmpfstmpfs  769912 0769912   0% /lib/init/rw
udev tmpfs   10240   112 10128   2% /dev
tmpfstmpfs  769912 0769912   0% /dev/shm


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:[O]
Overall install:[O]

Comments/Problems:

Two things didn't go quite right.

First, the laptop task wasn't selected by default. I don't know why; on 
the installed system laptop-detect returns 0.

Second, as happened in all my previous installations on PCs with 
wireless cards, d-i didn't connect to the network. I tried this on a PC 
with an IPW 3945 with the required firmware, and on this PC, which has 
an RT2500, supported by Linux (in the main kernel tree). The network has 
a DHCP server on a non-encrypted broadcasted 802.11g network. Specifying 
the ESSID didn't help.

I don't know if this is normal. The install guide reads "The use of 
wireless networking during installation is still under development and 
whether it will work depends on the type of adaptor and the 
configuration of your wireless access point."
This sounds like "Don't expect it to work, but it may work." On the 
other hand, the installer's design suggest it should work.

-- 

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 20090123"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux vinci 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 
unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04)
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 d4)
lspci -knn: 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 
04)
lspci -knn: 00:1e.3 Modem [0703]: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) AC'97 Modem Controller [8086:266d] (rev 04)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC 
Interface Bridge [8086:2641] (rev 04)
lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 04)
lspci -knn: Kernel driver in use: PIIX_IDE
lspci -knn: Kernel modules: piix
lspci -knn: 01:0

Bug#515902: installation-reports: d-i 5.0.0 DVD 1 i386 on SL-NV400-L64: Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: DVD
Image version: 
http://cdimage.debian.org/cdimage/release/5.0.0/i386/iso-dvd/debian-500-i386-DVD-1.iso
2009-02-14
Date: 2009-02-17

Machine: Soltek NV400-L64-based clone (desktop)
Partitions: 
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hda6 ext3 9614116   2624296   6501448  29% /
tmpfstmpfs  387996 0387996   0% /lib/init/rw
udev tmpfs   1024088 10152   1% /dev
tmpfstmpfs  387996 0387996   0% /dev/shm


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:[O]
Overall install:[O]

Comments/Problems:

Everything went as expected.

-- 

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 20090123"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux andrea 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: nVidia Corporation nForce2 IGP2 
[10de:01e0] (rev c1)
lspci -knn: 00:00.1 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 0 [10de:01ea] (rev c1)
lspci -knn: 00:00.2 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 4 [10de:01ee] (rev c1)
lspci -knn: 00:00.3 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 3 [10de:01ed] (rev c1)
lspci -knn: 00:00.4 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 2 [10de:01ec] (rev c1)
lspci -knn: 00:00.5 RAM memory [0500]: nVidia Corporation nForce2 Memory 
Controller 5 [10de:01ef] (rev c1)
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation nForce2 ISA Bridge 
[10de:0060] (rev a4)
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation nForce2 SMBus (MCP) 
[10de:0064] (rev a2)
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0067] (rev a4)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0067] (rev a4)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.2 USB Controller [0c03]: nVidia Corporation nForce2 USB 
Controller [10de:0068] (rev a4)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:04.0 Ethernet controller [0200]: nVidia Corporation nForce2 
Ethernet Controller [10de:0066] (rev a1)
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: Kernel modules: forcedeth
lspci -knn: 00:06.0 Multimedia audio controller [0401]: nVidia Corporation 
nForce2 AC97 Audio Controler (MCP) [10de:006a] (rev a1)
lspci -knn: 00:08.0 PCI bridge [0604]: nVidia Corporation nForce2 External PCI 
Bridge [10de:006c] (rev a3)
lspci -knn: 00:09.0 IDE interface [0101]: nVidia Corporation nForce2 IDE 
[10de:0065] (rev a2)
lspci -knn: Kernel driver in use: AMD_IDE
lspci -knn: Kernel modules: amd74xx
lspci -knn: 00:1e.0 PCI bridge [0604]: nVidia Corporation nForce2 AGP 
[10de:01e8] (rev c1)
lspci -knn: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc R300 
AD [Radeon 9500 Pro] [1002:4144]
lspci -knn: 01:00.1 Display controller [0380]: ATI Technologies Inc R300 AD 
[Radeon 9500 Pro] (Secondary) [1002:4164]
lsmod: Module  Size  Used by
lsmod: ufs63748  0 
lsmod: qnx47684  0 
lsmod: ntfs  180416  0 
lsmod: dm_mod 45384  0 
lsmod: md_mod 65940  0 
lsmod: xfs   446836  0 
lsmod: reiserfs  187008  0 
lsmod: jfs   148060  0 
lsmod: ext3  103688  1 
lsmod: jbd35092  1 ext3
lsmod: vfat8832  0 
lsmod: fat39964  1 vfat
lsmod: ext2   52744  0 
lsmod: mbcache 6656  2 ext3,ext2
lsmod: forcedeth  44816  0 
lsmod: nls_utf81664  2 
lsmod: isofs  27684  0 
lsmod: nls_base 

Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0

[Filipus Klutiero]

Package: installation-guide
Severity: minor

In section 5.1.3, if using GRUB, the procedure says to add lines
kernel (hd0,0)/boot/newinstall/vmlinuz
initrd (hd0,0)/boot/newinstall/initrd.gz

This will of course only work if the files were copied to 
(hd0,0)/boot/newinstall/.

BTW, I have no idea what "the value of ramdisk_size" refers to in "Note 
that the value of the ramdisk_size may need to be adjusted for the size 
of the initrd image." (just below).

And another BTW, it would be more generic to talk about ISO images in 
the third paragraph, since the iso can also be a DVD image.




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#519581: installation-reports: d-i 5.0.0 i386 on ECS K7S5A (SiS 735): Success

[Filipus Klutiero]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: Target hard drive
Image version: i386 initrd.gz, vmlinuz and debian-500-i386-DVD-1.iso
Date: 2009-03-13 02:24

Machine: ECS K7S5A (SiS 735 chipset), 256 MB SDRAM, 250 GB PATA
Partitions:
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hda3 ext363495136   1697568  58572120   3% /
tmpfstmpfs  128196 0128196   0% /lib/init/rw
udev tmpfs   1024092 10148   1% /dev
tmpfstmpfs  128196 0128196   0% /dev/shm
/dev/hda2 ext348062468  14403328  31217664  32% /mnt/hda2
/mnt/hda2/debian-500-i386-DVD-1.iso
   iso9660 4588206   4588206 0 100% /mnt/iso


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:[O]
Overall install:[O]

Comments/Problems:

Everything went as expected, even on this old K7S5A...as soon as I resorted to 
using an install method the board likes.

-- 

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 20090123"
X_INSTALLATION_MEDIUM=hd-media

==
Installer hardware-summary:
==
umame -a: Linux k7s5a 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 
unknown
lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 735 
Host [1039:0735] (rev 01)
lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] 
Virtual PCI-to-PCI bridge (AGP) [1039:0001]
lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] 
SiS85C503/5513 (LPC Bridge) [1039:0018]
lspci -knn: 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 
SMBus Controller [1039:0016]
lspci -knn: 00:02.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] 
USB 1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] 
USB 1.1 Controller [1039:7001] (rev 07)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: Kernel modules: ohci-hcd
lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 
5513 [IDE] [1039:5513] (rev d0)
lspci -knn: Kernel driver in use: SIS_IDE
lspci -knn: Kernel modules: sis5513
lspci -knn: 00:02.6 Modem [0703]: Silicon Integrated Systems [SiS] AC'97 Modem 
Controller [1039:7013] (rev a0)
lspci -knn: 00:03.0 Ethernet controller [0200]: Silicon Integrated Systems 
[SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 90)
lspci -knn: Kernel driver in use: sis900
lspci -knn: Kernel modules: sis900
lspci -knn: 00:0d.0 Multimedia audio controller [0401]: Ensoniq ES1371 
[AudioPCI-97] [1274:1371] (rev 08)
lspci -knn: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 
Radeon R300 ND [Radeon 9700 Pro] [1002:4e44]
lspci -knn: 01:00.1 Display controller [0380]: ATI Technologies Inc Radeon 
R300 [Radeon 9700 Pro] (Secondary) [1002:4e64]
lsmod: Module  Size  Used by
lsmod: ufs63748  0 
lsmod: qnx47684  0 
lsmod: ntfs  180416  0 
lsmod: dm_mod 45384  0 
lsmod: md_mod 65940  0 
lsmod: xfs   446836  0 
lsmod: jfs   148060  0 
lsmod: rsrc_nonstatic  9344  0 
lsmod: pcmcia_core31760  1 rsrc_nonstatic
lsmod: floppy 47620  0 
lsmod: sis900 17024  0 
lsmod: mii 4864  1 sis900
lsmod: nls_utf81664  1 
lsmod: loop   12300  2 
lsmod: isofs  27684  1 
lsmod: zlib_inflate   13952  1 isofs
lsmod: vfat8832  0 
lsmod: fat39964  1 vfat
lsmod: nls_base6528  6 ntfs,jfs,nls_utf8,isofs,vfat,fat
lsmod: reiserfs  186240  0 
lsmod: ext3  103176  1 
lsmod: jbd34836  1 ext3
lsmod: ext2   52232  1 
lsmod: mbcache 6656  2 ext3,ext2
lsmod: ide_generic 2432  0 [permanent]
lsmod: usb_storage753

Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0

[Filipus Klutiero]

Le April 5, 2009 06:59:43 pm Frans Pop, vous avez écrit :
> tags 519508 pending
> thanks
> 
> On Friday 13 March 2009, Filipus Klutiero wrote:
> > In section 5.1.3, if using GRUB, the procedure says to add lines
> > kernel (hd0,0)/boot/newinstall/vmlinuz
> > initrd (hd0,0)/boot/newinstall/initrd.gz
> >
> > This will of course only work if the files were copied to
> > (hd0,0)/boot/newinstall/.
> 
> Which is exactly what's suggested in section 4.4 to which 5.1.3 refers.
I see the path suggested in 4.4, but nothing about the partition. I'd suggest

The procedure for GRUB is quite similar. Locate your menu.lst in the 
/boot/grub/ directory (sometimes in the /boot/boot/grub/), add an entry for the 
installer and reboot. The entry can be defined by the following lines if the 
installer is in /boot/newinstall/ on the first partition of the first hard 
drive: 


> > BTW, I have no idea what "the value of ramdisk_size" refers to in "Note
> > that the value of the ramdisk_size may need to be adjusted for the size
> > of the initrd image." (just below).
> 
> Removed. That's a remnant from the 2.4 and early 2.6 kernel era.
> 
> > And another BTW, it would be more generic to talk about ISO images in
> > the third paragraph, since the iso can also be a DVD image.
> 
> I've added a mention of DVD.
> 
> Cheers,
> FJP

Thanks much.

Cheers



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#665775: [netcfg] Confusing prompt for Domain name

[Filipus Klutiero]

Package: netcfg
Version: 1.70
Severity: normal

From as far as I can remember, debian-installer prompts for a domain 
name during the installation. I never knew what to enter there.


The prompt:


Template: netcfg/get_domain
Type: string
# :sl1:
_Description: Domain name:
  The domain name is the part of your Internet address to the right of your
  host name.  It is often something that ends in .com, .net, .edu, or .org.
  If you are setting up a home network, you can make something up, but make
  sure you use the same domain name on all your computers.


The manual says:



  3.3.4. Network Settings

If your computer is connected to a network 24 hours a day (i.e., an 
Ethernet or equivalent connection --- not a PPP connection), you 
should ask your network's system administrator for this information.


 *

Your host name (you may be able to decide this on your own).

 *

Your domain name.

 *

Your computer's IP address.

 *

The netmask to use with your network.

 *

The IP address of the default gateway system you should route to,
if your network /has/ a gateway.

 *

The system on your network that you should use as a DNS (Domain
Name Service) server.

On the other hand, if your administrator tells you that a DHCP server 
is available and is recommended, then you don't need this information 
because the DHCP server will provide it directly to your computer 
during the installation process.





http://d-i.alioth.debian.org/manual/en.i386/ch03s03.html#id316925

First, please avoid using "your" here. Prefer "the computer's Internet 
address" and "the computer's hostname".


The main problem is that a host may have any number of Internet 
addresses. Having 1 is just one case. While the case where hosts have 
several addresses may be less problematic, one is left quite confused 
when the host has no address. One doesn't necessarily have a network, 
and if there is a network, it doesn't necessarily have a system 
administrator. Also, although DHCP does provide an IP address and some 
parameters, the domain name is not necessarily provided by DHCP.


Finally, the first sentence ("The domain name is the part of your 
Internet address to the right of your host name.") is misleading. As 
mentioned in http://en.wikipedia.org/wiki/Domain_name#Domain_name_syntax :

A hostname *is* a domain name that has at least one associated IP address.



Meanwhile, for those wondering what to enter, the domain name will be 
written to /etc/hosts (see netcfg_write_common() in netcfg-common.c).

Bug#665786: [task-xfce-desktop] "XFCE" completely uppercase in descriptions

[Filipus Klutiero]

Package: task-xfce-desktop
Version: 3.08
Severity: minor

The short description reads:

XFCE desktop environment

As explained in http://en.wikipedia.org/wiki/Xfce#History "Xfce" is no 
longer completely uppercase, but only takes a capital "X" nowadays.




--
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/4f700203.6050...@gmail.com

Bug#666090: [installation-guide] netinst does not fit with boot.img.gz

[Filipus Klutiero]

Package: installation-guide
Severity: normal

According to 4.3.1. Copying the files — the easy way:

A second disadvantage is that you cannot copy a full CD image onto the 
USB stick, but only the smaller businesscard or netinst CD images. 


http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html

Unfortunately, the i386 netinst, which now weighs 231 MB, does not fit 
anymore on the 256 MB partition created by the 31 MB boot.img.gz, 
unsurprisingly.


Either the boot.img should only support businesscard images, the netinst 
should be sized down, or boot.img.gz should create a larger partition. I 
notice that 256 MB USB sticks are actually still being sold. An 
alternative would be to provide several boot.img, for varying sizes. 1 
GB would be fine for me.




--
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/4f733e79.5010...@gmail.com

Bug#666105: [installation-guide] 5.1.4. Booting from USB Memory Stick: No prompt when installing the flexible way

[Filipus Klutiero]

Package: installation-guide
Severity: normal

According to section 5.1.4:

Let's assume you have prepared everything from Section 3.6.2, "Boot 
Device Selection" 
 
and Section 4.3, "Preparing Files for USB Memory Stick Booting" 
. Now just 
plug your USB stick into some free USB connector and reboot the 
computer. The system should boot up, and you should be presented with 
the |boot:| prompt. Here you can enter optional boot arguments, or 
just hit *Enter*. 


http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html#usb-boot

This would be nice, but is not actually the case, at least when creating 
the installation media "the flexible way". The stick just launches d-i 
automatically with defaults (non-expert install).

Bug#650414: Patch

[Filipus Klutiero]

I agree the current GRUB 2 path is too complicated.

I don't know if the proposed patch has functional regressions, but the 
code gets inconsistent in the sense that grub2 functions like 
grub2_write_chain() are kept but not used.


Another version of this, with the same issue, is on 
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/grub-installer/oneiric/revision/96#grub-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/4f739033.2090...@gmail.com

Bug#650414: os-prober is only extra

[Filipus Klutiero]

Joey Hess wrote:

AFAICS, the grub configuration generated by otheros.sh is entirely
grub-legacy syntax. If it ever worked with grub-pc it was due to luck or
compatability hacks in grub-pc. So I suspect my patch fixes this bug,
and that modifying otheros to use --set=root is unnecessary, and
would break it when used with grub-legacy.


otheros.sh seems to work with grub-pc. So much, in fact, that it saves 
the day in certain cases, like a problem I'm debugging which causes the 
normal update-grub to write a grub.cfg with an empty otheros section. 
When os-prober is not installed and update_grub is rerun with 
grub-installer's 30_otheros, the second update_grub is good and causes 
the other OS-es to go in the final grub.cfg by overwriting the broken 
initial grub.cfg.


Also, note that os-prober is extra and the os-prober deb is *not* 
present on all installation media. For example, a netinst without 
network access will fail to install os-prober to target.




--
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/4f7478f1.2030...@gmail.com

Bug#608025: Merge

[Filipus Klutiero]

merge 618498 608025
severity 618498 serious
thanks

Colin Watson wrote:

clone 618498 -1
reassign 618498 grub-installer: grub-mkconfig does not pick up correct 
os-prober output when run from installer
reassign -1 os-prober: Puppy Linux not detected
thanks

On Tue, Mar 15, 2011 at 06:29:12PM +0100, Erik Grootjans wrote:
>  I did a clean install of debian 6 Squeeze on my netbook.
>
>  After the isnstallation i had only 2 grub items
>  - debian
>  - and debian single mode
>
>  The other os-s had not been recognized.
>
>  I did a upgrade-grub
>  And grub did found 2 more OS-en
>
>  - XP-loader (on /dev/sda1)
>  -Microsoft XP Home Edition (on /dev/sda2)

This part is a grub-installer bug (which I think has already been
reported, but I haven't looked up the bug number).


Most likely #608025 (or #587397).



--
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/4f74fcea.7040...@gmail.com

Bug#666255: [grub-installer] Does not verify list of other operating systems when multiple targets (HDDs) detected

[Filipus Klutiero]

Package: grub-installer
Version: 1.70
Severity: normal

grub-installer generally prompts once, to confirm the list of other 
operating systems detected:



Template: grub-installer/with_other_os
Type: boolean
Default: true
# :sl1:
_Description: Install the GRUB boot loader to the master boot record?
  The following other operating systems have been detected on this
  computer: ${OS_LIST}
  .
  If all of your operating systems are listed above, then it should be safe to
  install the boot loader to the master boot record of your first hard
  drive. When your computer boots, you will be able to choose to load one of
  these operating systems or your new system.


This is not always the case however. When several possible target 
devices for installing GRUB are detected, grub-installer prompts:



Template: grub-installer/bootdev
Type: string
# :sl2:
_Description: Device for boot loader installation:
  You need to make the newly installed system bootable, by installing
  the GRUB boot loader on a bootable device. The usual way to do this is to
  install GRUB on the master boot record of your first hard drive. If you
  prefer, you can install GRUB elsewhere on the drive, or to another drive,
  or even to a floppy.
  .
  The device should be specified as a device in /dev. Below are some
  examples:
   - "/dev/sda" will install GRUB to the master boot record of your first
 hard drive;
   - "/dev/sda2" will use the second partition of your first hard drive;
   - "/dev/sdc5" will use the first extended partition of your third hard
 drive;
   - "/dev/fd0" will install GRUB to a floppy.


This prompt is good in this case, but it does not *replace* 
with_other_os. The list of other operating systems still needs to be 
confirmed.


When no other operating systems are detected, the prompt is phrased 
differently, but the idea is the same:



Template: grub-installer/only_debian
Type: boolean
Default: true
# :sl1:
_Description: Install the GRUB boot loader to the master boot record?
  It seems that this new installation is the only operating system
  on this computer. If so, it should be safe to install the GRUB boot loader
  to the master boot record of your first hard drive.
  .
  Warning: If the installer failed to detect another operating system that
  is present on your computer, modifying the master boot record will make
  that operating system temporarily unbootable, though GRUB can be manually
  configured later to boot it.


However, the phrasing here mixes a question about the target with a 
question whether to install GRUB in general. This should simply say 
"Install the GRUB boot loader?" Same for with_other_os, in fact.



Hum, there's a lot of cleanup to do here...
The code relevant to this specific problem is:


 574 while : ; do
 575 if [ "$state" = 1 ]; then
 576 db_input high $q || true
 577 if ! db_go; then
 578 # back up to menu
 579 db_progress STOP
 580 exit 10
 581 fi
 582 db_get $q
 583 if [ "$RET" = true ]; then
 584 bootdev="$default_bootdev"
 585 break
 586 else
 587 # Exit to menu if /boot is on SATA 
RAID/multipath; we

 588 # don't support device selection in that case
 589 if [ "$frdev" ]; then
 590 db_progress STOP
 591 exit 10
 592 fi
 593 state=2
 594 fi
 595 elif [ "$state" = 2 ]; then
 596 db_input critical grub-installer/bootdev || true
 597 if ! db_go; then
 598 if [ "$q" ]; then
 599 state=1
 600 else
 601 # back up to menu
 602 db_progress STOP
 603 exit 10
 604 fi
 605 else
 606 db_get grub-installer/bootdev
 607 bootdev=$RET
 608 if echo "$bootdev" | grep -qv '('; then
 609 mappedbootdev=$(mapdevfs 
"$bootdev") || true

 610 if [ -n "$mappedbootdev" ]; then
 611 bootdev="$mappedbootdev"
 612 fi
 613 fi
 614 break
 615 fi
 616 else
 617 break
 618 fi
 619 done


This could be solved by setting state to 1 at the end of the else (line 
613). But then, grub-installer would prompt for bootdev and only then 
for only_debian/with_other_os, which would mean asking where to install 
before asking whether to instal

Bug#666261: [os-prober] "unknown udeb fuse-modules" when installing

[Filipus Klutiero]

Package: os-prober
Version: 1.51
Severity: minor
Tags: patch

When installing, the following is logged to syslog:


Mar 29 16:03:30 anna-install: Installing fuse-modules
Mar 29 16:03:30 os-prober: unknown udeb fuse-modules


This is due to /usr/lib/os-probes/init/10filesystems which uses the same 
list of filesystems both for installing and loading LKMs. But this 
module, fuse, is not in the installer.


NOTE: fuse *can* be loaded in the installer if fuse is in the installed 
kernel. This will happen in practice when the installer's flavour 
matches the installed flavour (say when installing 486 with a i386 
installer) and something running in the target probes fuse.


The attached patch fixes that. It also slightly optimizes and minimizes 
the code run with set +e.


--- 10filesystems	2011-04-09 06:19:55.0 -0400
+++ 10filesystems.patched	2012-03-29 14:04:45.706707994 -0400
@@ -1,15 +1,13 @@
 #!/bin/sh
 # Make sure filesystems are available.
-set +e	# ignore errors from modprobe
-
-FILESYSTEMS='ext2 ext3 ext4 reiserfs xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs btrfs'
-# fuse is needed to make grub-mount work.
-FILESYSTEMS="$FILESYSTEMS fuse"
-# The Ubuntu kernel udebs put a number of filesystem modules in
-# fs-{core,secondary}-modules. It's fairly cheap to check for these too.
-FILESYSTEMS="$FILESYSTEMS fs-core fs-secondary"
 
 if [ ! -e /var/lib/os-prober/modules ]; then
+	FILESYSTEMS='ext2 ext3 ext4 reiserfs xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs btrfs'
+
+	# The Ubuntu kernel udebs put a number of filesystem modules in
+	# fs-{core,secondary}-modules. It's fairly cheap to check for these too.
+	FILESYSTEMS="$FILESYSTEMS fs-core fs-secondary"
+
 	# Check for anna-install to make it easier to use os-prober outside
 	# d-i.
 	if type anna-install >/dev/null 2>&1 && [ -d /lib/debian-installer ]; then
@@ -21,6 +19,10 @@
 		depmod -a >/dev/null 2>&1 || true
 	fi
 
+	# fuse is needed to make grub-mount work.
+	FILESYSTEMS="$FILESYSTEMS fuse"
+
+	set +e	# ignore errors from modprobe
 	for fs in $FILESYSTEMS; do
 		case "$fs" in
 			fs-*)

Bug#666552: [grub-common] Bad GRUB / os-prober integration: Other operating systems removed from GRUB's list when os-prober is removed, duplicate menu entries

[Filipus Klutiero]

Package: grub-common, os-prober, grub-installer
Version: 1.99-17
Severity: important
X-Debbugs-Cc: 650...@bugs.debian.org
X-Debbugs-Cc: 563...@bugs.debian.org

GRUB doesn't depend on os-prober, it only recommends it.

One obvious effect is that when installing GRUB, other operating systems 
are not necessarily detected. This was reported in #563204. However, 
debian-installer includes a fallback procedure to write a static 
/etc/grub.d/30_otheros in that case (for example, when installing from a 
netinst without a mirror). This itself has a downside - if os-prober is 
later installed, both 30_otheros and 30_os-prober will cause the 
addition of entries for other OS-es, so other operating systems will be 
duplicated.


One less obvious and worst effect, which was alluded to in comments of 
#563204, is that the removal of os-prober eventually causes the loss of 
other operating systems. And this is both likely and non-trivial to "debug".

os-prober is only extra. Its extended description reads:

This package detects other OSes available on a system and outputs the 
results in a generic machine-readable format. 


Unless the administrator reading this is very alert, it's unlikely he 
will think the removal of os-prober can affect GRUB. And when removing 
os-prober, there is no warning at all about an effect on GRUB.


Also, the effect will only be seen after grub.cfg is updated and then 
the system rebooted, which will normally take days, usually weeks, so it 
will be hard for the administrator to realize that his removal of 
os-prober caused the problem when he notices the problem.



The duplication of menu entries could be solved by removing 30_otheros 
when os-prober is installed. The loss of menu entries could be solved by 
writing a "final" 30_otheros when os-prober is removed, in prerm.
However, it would be even better, and much less complicated to 
implement, to simply make GRUB depend on os-prober, which only weighs 
128 kB, as suggested in #563204. This would in fact allow a substantial 
simplification of grub-installer eventually, and fix #650414 for free. 
It could also make os-prober-udeb unneeded.





--
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/4f773905.2090...@gmail.com

Bug#650414: Fwd: Bug#666552: Acknowledgement ([grub-common] Bad GRUB / os-prober integration: Other operating systems removed from GRUB's list when os-prober is removed, duplicate menu entries)

[Filipus Klutiero]

 Original Message 
Subject: 	Bug#666552: Acknowledgement ([grub-common] Bad GRUB / 
os-prober integration: Other operating systems removed from GRUB's list 
when os-prober is removed, duplicate menu entries)

Date:   Sat, 31 Mar 2012 17:06:04 +
From:   ow...@bugs.debian.org (Debian Bug Tracking System)
Reply-To:   666...@bugs.debian.org
To: Filipus Klutiero 



Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
  563...@bugs.debian.org
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
 GRUB Maintainers
 Debian Install System Team

If you wish to submit further information on this problem, please
send it to 666...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

--
666552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#655437: Confirmed

[Filipus Klutiero]

tags 655437 + confirmed
thanks

I have to confirm this. This (the problem reported by Martin) is 
particularly confusing when several flavours are possible. On a x86-64 
system, I get this:


Mar 29 15:53:14 base-installer: info: kernel linux-image-686-pae 
usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel linux-image-486 usable on 
686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel 
linux-image-3.2.0-2-686-pae usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: kernel linux-image-3.2.0-2-486 
usable on 686-pae 686-bigmem amd64 686 486
Mar 29 15:53:14 base-installer: info: Found kernels 
'linux-image-3.2.0-2-486,linux-image-3.2.0-2-686-pae,linux-image-486,linux-image-686-pae'
Mar 29 15:53:14 base-installer: info: arch_kernel candidates: 
linux-image-3.2-686-pae linux-image-3.2-686-bigmem 
linux-image-3.2-amd64 linux-image-3.2-686 linux-image-3.2-486
Mar 29 15:53:14 base-installer: info: arch_kernel: 
linux-image-3.2-686-pae (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: 
linux-image-3.2-686-bigmem (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: 
linux-image-3.2-amd64 (absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: linux-image-3.2-686 
(absent)
Mar 29 15:53:14 base-installer: info: arch_kernel: linux-image-3.2-486 
(absent)


This needs to be fixed for wheezy. However, since the choices presented 
to the user are sorted alphabetically, the current situation must cause 
a greater usage of the 486 image on i386, which works around #650819. It 
may be wise to wait for #650819 to be fixed before uploading a fix for 
this one.




--
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/4f77899d.2040...@gmail.com

Bug#650819: Confirmed, serious

[Filipus Klutiero]

severity 650819 serious
tags 650819 + confirmed patch
retitle 650819 GRUB entries (grub.cfg) sometimes lacking other operating 
systems, particularly installing 686 or amd64 images (i386)

reassign 650819 os-prober, grub-common
thanks

I have to confirm this. I was hit by this when installing from the March 
22 i386 wheezy netinst on my laptop, a typical Intel Core i3 (x86-64) 
laptop with Windows 7. Although d-i detected Windows, after the install 
Windows was not listed by GRUB.
I reproduced with a later businesscard, and then with a March 27 
"flexible way" USB key with an updated netinst. I reproduced this about 
in 10-20 installs before precisely understanding when/why it happened.


Thanks Brian for reporting. All the information you reported was 
precious in nailing this one. This is indeed an os-prober bug, or at 
least a bug of interaction between os-prober and GRUB.


First of all, debian-installer typically calls os-prober 3 times. The 
last time is during finish-install (clock-setup) and although it nicely 
fills syslog, it is not relevant at all to this problem. The 2 other 
times are indeed from grub-installer.
There are 2 os-prober packages, a deb and a udeb. Typically, both are 
installed. The deb may however not be installed, when automatic 
installation of recommendations is disabled (os-prober is only installed 
because it's recommended by grub-common) or when it is not available 
(for example, when installing from a netinst without using a mirror).
Typically, grub-installer calls os-prober twice. The first is used 
mainly to verify the list of other operating systems detected, before 
asking whether GRUB should be installed. The (possible) second time is 
when grub-installer calls update-grub (line 845). update-grub's 
30_os-prober hook calls os-prober if it is installed.
There is an important difference between these calls. The first, direct, 
call to os-prober happens in d-i's context (it uses os-prober-udeb). The 
second one happens in-target (it uses the os-prober deb). This problem 
comes from this second time. Starting from version 1.45, os-prober's 
50mounted-tests attempts to mount partitions using grub-mount, rather 
than using mount, if the former is available: 
http://packages.qa.debian.org/o/os-prober/news/20110424T183244Z.html

http://anonscm.debian.org/gitweb/?p=d-i/os-prober.git;a=commit;h=7ed9dec4d2c65056f211324f8e25a4d913b0f2a1


mounted=
if which grub-mount >/dev/null 2>&1 && \
   grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
mounted=1
type="$(grub-probe -d "$partition" -t fs)"
[ "$type" ] || type=fuseblk
else
ro_partition "$partition"
for type in $types; do
if mount -o ro -t "$type" "$partition" "$tmpmnt" 2>/dev/null; then
mounted=1
break
fi
done
fi


What happens here is that grub-mount fails, but the if's condition still 
evaluates to true because grub-mount's exit status is 0, and the code 
above assumes 0 means success. From that point, 50mounted-tests 
considers the partition mounted, and subtests quietly fail to find anything.


This issue does not affect the first call to os-prober (which is outside 
the target) because which(1) is not available in the installer, so the 
condition is false and the tests fallback to the standard mount, which 
works. This bug (using which in os-prober-udeb) was fixed in os-prober 
1.51: 
http://anonscm.debian.org/gitweb/?p=d-i/os-prober.git;a=commit;h=94048e4ec7a8896fb2c9c917433fa5e3ba71fbbe
However, that commit also introduced a check for grub-probe, which is 
not in grub-mount-udeb for now, as indicated in the commit message, so 
for now there is no functional difference; the first use of os-prober 
will keep falling back to the standard mount.



Brian's finding about the subtle "fuse init" line was a hint to the 
reason why grub-mount fails. grub-mount needs fuse, and fuse is not in 
the installer's 486 Linux. Here is what happens:

# grub-mount /dev/sdb1 /var/lib/os-prober/mount
fuse: device not found, try 'modprobe fuse' first

However, fuse is in stock (non-install) Linux images, so when installing 
the 486 image, grub-mount succeeds to load fuse because it's running 
in-target and it attemps loading the installed Linux's LKM, rather than 
failing to find a fuse LKM for the installer Linux. Of course, the 
installed Linux's fuse is compatible with the installer Linux's module 
ABI when installing the 486 image, but not when installing the 686 
image. This is presumably also true on i386 for any non-486 image, such 
as amd64, however the 686 image is on netinsts and offered as a choice. 
It should be noted that at this time, the 486 image is more likely to be 
installed on 686 machines due to #655437, but this is merely a blessed 
misfortune.


I do not know other architectures, but I imagine that this doesn't 
affect amd64, as the only image proposed for installation will be amd64, 
which matches the installer. So I imagine this problem is largely 
spec

Bug#666750: [debian-installer] grub-installer prompt mentions other operating systems like Windows, but only Debian actually offered after install

[Filipus Klutiero]

Package: debian-installer, grub-installer
Severity: serious

This is a fake bug to document a particularly bad scenario caused by 
#650819 for users and ease finding it.


When the installer installs a Linux image of a different flavour than 
the flavour it uses, the GRUB installed does not offer booting other 
operating systems. For example, if installing Debian wheezy i386 on a PC 
that came with Windows 7, Windows 7 will not be bootable using a GRUB 
entry if the Linux flavour installed is 686-pae. However, when 
debian-installer asks whether GRUB should be installed, the list of 
operating systems detected is fine, so the user has no idea he's going 
to "lose" other operating systems.
A rare exception to that is if os-prober is not installed to the target 
system.


This bug obviously does not affect squeeze.

If you hit this bug, your other operating systems are still there.
All you need to do to recover them is to boot Debian and run the 
update-grub command, as the root user (assuming your Debian install 
succeeeds to boot...) You should then see other operating systems in 
GRUB when you reboot.



Although fixing #650819 will get rid of this issue, grub-installer could 
do better to avoid this deceptive scenario. As explained in #650819, 
grub-installer typically calls os-prober twice, once to ask if all other 
OS-es were detected, and once to actually generate grub.cfg. Instead, if 
os-prober was called once to generate grub.cfg (by moving update-grub 
before grub-install), the list of other operating systems that were 
detected could be presented to the user after analyzing update-grub's 
result.


Unfortunately, I'm afraid update-grub doesn't return a list of other 
OS-es it detected, and parsing its generated grub.cfg may need some 
effort. But it would be much more reliable.
Alternatively, we could at least have the 2 calls to os-prober run both 
in the target or outside the target (presumably inside). Or, if 
os-prober (deb) is installed, run both inside (and if not, keep having a 
single call running outside, as is currently happening).





--
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/4f78692b.1020...@gmail.com

Bug#666764: [os-prober] 20microsoft is stuck on Vista (newer Windows versions sometimes detected as Vista, encoding problem)

[Filipus Klutiero]

Package: os-prober
Version: 1.51
Severity: normal

20microsoft's detection of Windows Vista and ulterior is problematic. 
First, it's stuck in Vista times. The comment and the fallback case 
should be updated. Perhaps "Windows Vista or superior", "Unrecognized 
Windows version" or "Recent Windows version". In my previous install, 
both my Windows 7 partition and its recovery partition were showing as 
"Windows Vista (loader)" (identical labels).


This test is grepping a binary file for strings. While the presence of 
these strings in the file may be reliable, grepping a binary file is 
unfortunately not nice and this apparently causes issues when os-prober 
runs in the installer's context, where the test always falls back to 
"Windows Vista (loader)". I'm not sure what's going on, but this shows 
the problem:


/target/mnt/Boot # ../../bin/grep "W.i.n.d.o.w.s" BCD
Binary file BCD matches
# grep "W.i.n.d.o.w.s" BCD
# ../../bin/busybox grep "W.i.n.d.o.w.s" BCD
[Much randomness (works)]

So it seems there's a problem with the *installer's* busybox grep. The 
installed busybox grep works fine. It's not the pattern syntax that's 
different.


This test works when run after installation, or in-target (as is the 
case when grub-installer runs update-grub).

# Vista (previously Longhorn)
if item_in_dir -q bootmgr "$2"; then
# there might be different boot directories in different case as:
# boot Boot BOOT
for boot in $(item_in_dir boot "$2"); do
bcd=$(item_in_dir bcd "$2/$boot")
if [ -n "$bcd" ]; then
if grep -qs "W.i.n.d.o.w.s. .7" "$2/$boot/$bcd"; then
long="Windows 7 (loader)"
elif grep -qs "W.i.n.d.o.w.s. .V.i.s.t.a" "$2/$boot/$bcd"; 
then

long="Windows Vista (loader)"
elif grep -qs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. 
.R.2." "$2/$boot/$bcd"; then

long="Windows Server 2008 R2 (loader)"
elif grep -qs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8." 
"$2/$boot/$bcd"; then

long="Windows Server 2008 (loader)"
elif grep -qs "W.i.n.d.o.w.s. .R.e.c.o.v.e.r.y. 
.E.n.v.i.r.o.n.m.e.n.t" "$2/$boot/$bcd"; then

long="Windows Recovery Environment (loader)"
elif grep -qs "W.i.n.d.o.w.s. .S.e.t.u.p" "$2/$boot/$bcd"; 
then

long="Windows Recovery Environment (loader)"
else
long="Windows Vista (loader)"
fi
short=Windows

found=true

break
fi
done
fi





--
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/4f7876f2.5040...@gmail.com

Bug#415634: Update

[Filipus Klutiero]

With KDE 4.7, things are quite different. We have new metapackages, 
including a convenient "kde-standard", which is pretty much the same as 
the proposed kde-typical. Considering that kaffeine is less interesting 
now (kaboodle was replaced by dragonplayer), the only important thing 
from kde-extras-typical that's still not installed by kde-standard is 
amarok. Amarok has changed too. Installing it on my not-so-barebone KDE 
(kde-standard is installed) now adds 99 MB (installed size):
amarok amarok-common amarok-utils kdemultimedia-kio-plugins 
libgpod-common libgpod4-nogtk liblastfm0 libloudmouth1-0 libqjson0 
libqtscript4-core libqtscript4-gui libqtscript4-network 
libqtscript4-sql libqtscript4-uitools libqtscript4-xml

  libtag-extras


Amarok itself is 78 MB. JuK is still just 1 MB. Now that KDE has changed 
(see http://dot.kde.org/2009/11/24/repositioning-kde-brand?page=1 ) I 
think we could make kde-standard depend on either JuK or Amarok, and not 
need to change task-kde-desktop.




--
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/4f7a4a8e.8040...@gmail.com

Bug#666977: [src:tasksel] Please remove dependencies of tasks on tasksel

[Filipus Klutiero]

Source: tasksel
Version: 3.08
Severity: wishlist

This is similar to #413250, making tasks usable without having to 
install tasksel. Now having packages for tasks is great (although it 
does make a fair amount of task packages!), as tasks can now be used 
without using tasksel. But tasks cannot yet be used without *installing* 
tasksel, as installing these tasks requires the administrator to also 
install tasksel. For example, task-kde-desktop depends on tasksel.


The only reason task-kde-desktop depends on tasksel is that 
/usr/share/doc/task-kde-desktop is a symlink to /usr/share/doc/tasksel. 
This contains tasksel's changelog, README, TODO and copyright. TODO and 
README are more confusing than helpful for tasks. That leaves the 
changelog and copyright. Only the changelog has a significant size. 
These could either be duplicated in all task packages, or a new 
dependency package could be created (for example, tasks-common or 
tasksel-common). I wouldn't mind a dependency on tasksel-data if 
tasksel-data wouldn't depend on tasksel.
My problem with this dependency is not tasksel itself, but tasksel's 
dependency on aptitude.




--
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/4f7a64da.9090...@gmail.com

Bug#413250: Fwd: Bug#666977: Acknowledgement ([src:tasksel] Please remove dependencies of tasks on tasksel)

[Filipus Klutiero]

 Original Message 
Subject: 	Bug#666977: Acknowledgement ([src:tasksel] Please remove 
dependencies of tasks on tasksel)

Date:   Tue, 03 Apr 2012 02:51:04 +
From:   ow...@bugs.debian.org (Debian Bug Tracking System)
Reply-To:   666...@bugs.debian.org
To: Filipus Klutiero 



Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Install System Team

If you wish to submit further information on this problem, please
send it to 666...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

--
666977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#665775: [netcfg] Confusing prompt for Domain name

[Filipus Klutiero]

Hi Christian,

On 2012-03-26 01:17, Christian PERRIER wrote:

reassign 665775 netcfg
tags 665775 wontfix
thanks

Quoting Filipus Klutiero (chea...@gmail.com):

On the other hand, if your administrator tells you that a DHCP
server is available and is recommended, then you don't need this
information because the DHCP server will provide it directly to
your computer during the installation process.



http://d-i.alioth.debian.org/manual/en.i386/ch03s03.html#id316925

First, please avoid using "your" here. Prefer "the computer's
Internet address" and "the computer's hostname".

Well, this prompt has been worked and reworked over the years and one
of the involved people is the person well known in Debian for pushing
to avoid "computer personnalization". Guess who that might be? :-)


You must be confusing with something else. As I said, I was always 
confused by this prompt, and I installed Debian for the first time in 
2004. This is not a regression. The last time the prompt was changed is 
in 2000: 
http://anonscm.debian.org/gitweb/?p=d-i/netcfg.git;a=commitdiff;h=7ec48a21da9e6f89f8c62d5ff26973336f9b1f45
I find the previous version interesting, it's not much worst than the 
current one. I wonder if there was something wrong with "Please enter 
your domain name or leave this field empty if you don't have a domain."




And still, we have "your". That's perfectly on purpose to fit the need
for being as user-accessible as possible, which is one of the goals of
D-I.


It's not. Just ask your mother her Internet address. She'll surely tell 
you her Internet *mail* address. We don't want people entering gmail.com 
as domain name.
However, this does show that "Internet address" is not a perfect wording 
neither.
Searching for "Internet address" on Wikipedia brings to 
http://en.wikipedia.org/wiki/Internet_address
In French, it's a disambiguation page: 
http://fr.wikipedia.org/wiki/Adresse_Internet





The main problem is that a host may have any number of Internet
addresses. Having 1 is just one case. While the case where hosts
have several addresses may be less problematic, one is left quite
confused when the host has no address. One doesn't necessarily have
a network, and if there is a network, it doesn't necessarily have a
system administrator. Also, although DHCP does provide an IP address
and some parameters, the domain name is not necessarily provided by
DHCP.

Finally, the first sentence ("The domain name is the part of your
Internet address to the right of your host name.") is misleading. As
mentioned in
http://en.wikipedia.org/wiki/Domain_name#Domain_name_syntax :

A hostname *is* a domain name that has at least one associated IP address.


Trying to enter such considerations would be too pedantic. We need to
keep prompts simple. We guess that users who understand all underlying
subtleties will anyway never read down to that part of the prompt and
probably stop at "Domain name:".


Pedantic? One prompt usually displayed by d-i is making an assumption 
which is usually wrong. I don't consider fixing that pedantic. 
Simplifying this prompt is precisely what I'm suggesting here. If d-i 
asks for a domain name, its prompt should at least not be confusing. 
What prompted me to report this is users who do *not* know what a domain 
name is.


D-I is designed to be as usable from the home computer to the server
in a datacenter. Such prompts that are common to all have been
thoroughly worked over years to fit all such needs.


Well, this one must be the exception then.
PCs in particular should be kept in mind so that d-i supports more than 
a minority of machines.



It is anyway too late for such changes. I'm sorry to say so but fro
mabout now, I'll be fighting very hard against *any* change in D-I
prompts. You have no idea how hard it can be to get translations
updated.

The only changes to D-I prompts that may get my approval will be those
that do not impact localization at all, such as typo, spelling,
grammar, punctuation fixes (and even punctuation might be debated).

Other changes have to happen in the first year after a Debian release,
not a few months before. And, yes, it takes *months* to get everything
updated when it comes at l10n (hunting down translators is an
incredibly painful task).




If I endured this prompt in its current state for 8 years, I'll probably 
manage to endure it until wheezy, particularly if I know my ordeal will 
end soon. However, the sooner the change will be done, the lesser effort 
wasted from translators.




--
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/4f7b19f3.7000...@gmail.com

Bug#650819: Increased potentiality

[Filipus Klutiero]

#655437 is now fixed, which will increase this bug's exposure.



--
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/4f7c920f.5090...@gmail.com

Re: NetworkManager and wireless interfaces created by d-i (Re: Bug#606268:...)

[Filipus Klutiero]

On 2012-04-04 17:02, Michael Biebl wrote:

On 04.04.2012 22:48, Michael Biebl wrote:

On 04.04.2012 19:50, Filipus Klutiero wrote:

I just reinstalled Debian and for the first time did it via my wireless
network (with WPA encryption), without even requiring non-free firmware.
It was disappointing after that to discover that using wireless during
the install was what caused network-manager not to manage my wireless
card, after the installation :-/

I read the README and also tried managed=true to workaround, but that
didn't do it for me. NetworkManager would show my wireless card as
"Unavailable"... whatever that means. It reluctantly gave as only reason
for that state that the device was now managed...
d-i added this stanza to /etc/network/interfaces for my wireless card:


# The primary network interface
allow-hotplug wlan0
iface wlan0 inet dhcp
 wpa-ssid 1391
 wpa-psk  openssh5.1p1

Commenting the allow-hotplug line managed to work around. It seems that
wlan0 was up when network-manager started, and this caused it not to
consider wlan0. After bringing wlan0 down and restarting
network-manager, NetworkManager could control wlan0.

I thought d-i does *not* create any /e/n/i entries for wireless
connections anymore, so NM can properly manage the interface later on.

 d-i surely did here. To be exact, I "just" reinstalled on March 23rd, 
using a March 22nd i386 testing netinst. I didn't touch 
/etc/network/interfaces or play with the network after the install 
except through NetworkManager.



--
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/4f7d3292.4090...@gmail.com

Bug#650819: Confirmed, serious

[Filipus Klutiero]

On 2012-04-05 08:16, Touko Korpela wrote:

On Sat, Mar 31, 2012 at 07:58:17PM -0400, Filipus Klutiero wrote:

severity 650819 serious
tags 650819 + confirmed patch
retitle 650819 GRUB entries (grub.cfg) sometimes lacking other
operating systems, particularly installing 686 or amd64 images
(i386)
reassign 650819 os-prober, grub-common
thanks

Looks like your BTS commands were ignored (maybe because of MIME multipart
message).



Yeah, the BTS ignores all my commands :-( The BTS team is aware of the 
issue.

Thanks



--
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/4f7daaa8.4090...@gmail.com

Bug#667703: [task-desktop] Please install Synaptic Package Manager

[Filipus Klutiero]

Package: task-desktop
Version: 3.09
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: 586...@bugs.debian.org

Synaptic is no longer in the desktop task since tasksel 2.43: 
http://packages.debian.org/changelogs/pool/main/t/tasksel/current/changelog#version2.43



* Add kpackage to kde-desktop.
* Move synaptic to gnome-desktop.


The idea of having each desktop provide its package manager was good, 
but kpackage was very far from matching Synaptic. It was even removed 
from KDE later, with the result that installing task-kde-desktop no 
longer causes the installation of a graphical package manager, as 
reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586982

There is still nothing that matches Synaptic today.

Furthermore, we now have LXDE and Xfce, which are also not preinstalling 
any graphical package manager. So I think Synaptic should be 
preinstalled on all DE-s... except that in Squeeze, GNOME itself does 
not preinstall Synaptic. Instead, it preinstalls GNOME PackageKit.


I asked about this, specifically about the situation for GNOME, in 
https://lists.debian.org/debian-devel/2012/03/msg00829.html

That message has some more relevant information.
There was one reply from Jon Dowland, who thinks "Synaptic is probably 
quite rightly not part of either [GNOME or KDE], but [agrees] that a 
"default desktop" via install should provide a GUI package manager." 
There were however no suggestions of alternatives.

It seems nobody thinks it's best to just install GNOME PackageKit.

Adding synaptic to task-desktop will effectively cause the 
preinstallation of both Synaptic and GNOME PackageKit on GNOME. I do not 
consider that a big problem, but gnome-core could stop depending on 
gnome-packagekit if we think it's best.

Bug#667703: [task-desktop] Please install Synaptic Package Manager

[Filipus Klutiero]

Hi Christian,

On 2012-04-06 01:15, Christian PERRIER wrote:

Quoting Filipus Klutiero (chea...@gmail.com):


The idea of having each desktop provide its package manager was
good, but kpackage was very far from matching Synaptic. It was even
removed from KDE later, with the result that installing
task-kde-desktop no longer causes the installation of a graphical
package manager, as reported in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586982
There is still nothing that matches Synaptic today.

Furthermore, we now have LXDE and Xfce, which are also not
preinstalling any graphical package manager. So I think Synaptic
should be preinstalled on all DE-s... except that in Squeeze, GNOME
itself does not preinstall Synaptic. Instead, it preinstalls GNOME
PackageKit.


I agree with the idea of graphical environments to need a graphical
package manager (though, for LXDE and Xfce, one might argue that users
of these environments are probably looking for a "not-too-bloated"
environment and therefore could maybe deal with a text-based package
manager).


Hum, good point. I admit I don't remember it even crossed my mind that 
LXDE and Xfce would be intentionally leaving a package manager out.


I'm testing from a more or less minimal KDE environment (1489 packages 
installed). I usually install synaptic with --no-install-recommends, and 
then it's quite lightweight. synaptic itself is 6.5 MB.


Before adding this, I'd like to get comments from other tasksel
maintainers (that would be Otavio and/or Joey).

The concern might be dependencies being pulled in by synaptic. I'm
not in position to test that but wouldn't it pull "half of GNOME" into
other graphical environments? :-). At least probably some GTK
libraries that wouldn't be pulled otherwise?


Indeed. Synaptic is more GTK+ than GNOME, although it does

Recommends: gksu | kdebase-bin | policykit-1


and gksu recommends gnome-keyring. Otherwise, it depends on GTK+ 2, but 
all tasks already installs that (for one thing, via Iceweasel).
On my system, the only real new dependency is libvte9, just 2.5 MB. Most 
of the additional weight comes from recommendations:


Recommends: gksu | kdebase-bin | policykit-1, libgtk2-perl (>= 
1:1.130), rarian-compat, software-properties-gtk


kde-standard depends on polkit-kde-1, which depends on policykit-1, so 
the first *should* not be a problem for KDE. It might be for LXDE and 
Xfce, however.


libgtk2-perl and its additional dependencies amount to an extra 5.5 MB. 
This is considerable, but I think worth it for new users. The 
alternative of prompting in CLI is not great and exposes 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339556


rarian-compat only brings 0.7 MB here. I don't see much what Rarian 
does, and I have no idea what it's adding to Synaptic.


Finally, the most problematic is software-properties-gtk, which replaces 
the native dialog Synaptic offers to configure source (Settings -> 
Repositories). This is rarely used, but is probably quite nice when you 
need it (I don't know it much). That one brings in a large 8 MB, 
primarily due to its dependency on python-aptdaemon.gtk3widget. That 
causes the installation of another, GTK 3, libvte. This may be a bit 
less problematic if Synaptic transitions to GTK+ 3 and that newer libvte.


In total, installing synaptic with its recommends adds an extra 23 MB here.

Trying to install task-xfce-desktop and task-lxde-desktop, I see that 
these apparently already bring in gksu and libvte9. So adding synaptic 
to task-desktop should cause task-desktop to install about 20 MB more 
for LXDE and Xfce. task-xfce-desktop installs an extra 235 MB here. 
task-lxde-desktop, 198 MB. These numbers should give a rough picture, 
but are not very representative. I wish it was a little less, but I 
would say that 20 MB versus about 200 MB is reasonable, considering the 
alternative, providing only CLI package managers.


For reference:


# LANG=C apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  aptdaemon aptdaemon-data gir1.2-atk-1.0 gir1.2-freedesktop 
gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 gir1.2-pango-1.0 gir1.2-vte-2.90 
libcairo-perl libglib-perl libgtk2-perl libpango-perl librarian0 
libvte-2.90-9 libvte-2.90-common libvte-common libvte9 python-aptdaemon
  python-aptdaemon.gtk3widgets python-defer python-gnupginterface 
python-software-properties rarian-compat software-properties-common 
software-properties-gtk unattended-upgrades

Suggested packages:
  libfont-freetype-perl libgtk2-perl-doc dwww deborphan 
apt-xapian-index bsd-mailx

The following NEW packages will be installed:
  aptdaemon aptdaemon-data gir1.2-atk-1.0 gir1.2-freedesktop 
gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 gir1.2-pango-1.0 gir1.2-vte-2.90 
libcairo-perl libglib-perl libgtk2-perl libpango-perl librarian0 
libv

Bug#667703: gnome, size for Xfce

[Filipus Klutiero]

Sorry, I hadn't read Holger's reply when I sent my previous message.
Thanks Holger. The difference between my 20 MB and your 24 mostly comes 
from docbook-xml, which is a dependency of rarian-compat. kdoctools 
already depends on docbook-xml, which is why I didn't notice it. So the 
situation must be the same for LXDE, Synaptic must bring closer to 24 MB.


Josselin, why would the gnome metapackage already pull synaptic? I don't 
see any direct relation. This is what happens on my testing/unstable mix:



# LANG=C apt-get -tsid install gnome
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  abiword abiword-common abiword-plugin-grammar 
abiword-plugin-mathview accountsservice aisleriot alacarte apg 
app-install-data apt-xapian-index at-spi baobab bluez bogofilter 
bogofilter-bdb bogofilter-common brasero brasero-common 
browser-plugin-gnash cheese
  cheese-common cli-common cups-pk-helper dconf-tools 
desktop-file-utils ekiga empathy empathy-common eog epiphany-browser 
epiphany-browser-data epiphany-extensions evince evince-common 
evolution evolution-common evolution-data-server 
evolution-data-server-common
  evolution-plugins evolution-webcal file-roller finger folks-common 
fonts-cantarell fonts-lyx freedesktop-sound-theme freepats gcalctool 
gcc-4.7-base gdebi gdebi-core gdm3 gedit gedit-common gedit-plugins 
geoclue geoclue-hostip geoclue-localnet geoclue-manual
  geoclue-yahoo gimp gir1.2-accountsservice-1.0 gir1.2-atk-1.0 
gir1.2-caribou-1.0 gir1.2-clutter-1.0 gir1.2-clutter-gst-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-evince-3.0 
gir1.2-folks-0.6 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdata-0.0 
gir1.2-gdkpixbuf-2.0
  gir1.2-gee-1.0 gir1.2-gkbd-3.0 gir1.2-glib-2.0 gir1.2-gmenu-3.0 
gir1.2-gnomebluetooth-1.0 gir1.2-gnomekeyring-1.0 gir1.2-goa-1.0 
gir1.2-gst-plugins-base-0.10 gir1.2-gstreamer-0.10 gir1.2-gtk-3.0 
gir1.2-gtkclutter-1.0 gir1.2-gtksource-3.0 gir1.2-gucharmap-2.90
  gir1.2-javascriptcoregtk-3.0 gir1.2-json-1.0 gir1.2-mutter-3.0 
gir1.2-networkmanager-1.0 gir1.2-panelapplet-4.0 gir1.2-pango-1.0 
gir1.2-peas-1.0 gir1.2-polkit-1.0 gir1.2-rb-3.0 gir1.2-soup-2.4 
gir1.2-telepathyglib-0.12 gir1.2-telepathylogger-0.2 gir1.2-totem-1.0
  gir1.2-totem-plparser-1.0 gir1.2-tracker-0.14 gir1.2-upowerglib-1.0 
gir1.2-vte-2.90 gir1.2-webkit-3.0 gir1.2-xkl-1.0 gjs gksu glchess 
glines gnash gnash-common gnect gnibbles gnobots2 gnome-applets 
gnome-applets-data gnome-backgrounds gnome-bluetooth gnome-contacts
  gnome-control-center gnome-control-center-data gnome-core 
gnome-desktop3-data gnome-dictionary gnome-disk-utility 
gnome-documents gnome-font-viewer gnome-games gnome-games-data 
gnome-games-extra-data gnome-icon-theme gnome-icon-theme-extras 
gnome-icon-theme-symbolic
  gnome-js-common gnome-keyring gnome-media gnome-menus gnome-nettool 
gnome-online-accounts gnome-packagekit gnome-packagekit-data 
gnome-panel gnome-panel-data gnome-power-manager gnome-screensaver 
gnome-screenshot gnome-search-tool gnome-session gnome-session-bin
  gnome-session-common gnome-session-fallback gnome-settings-daemon 
gnome-shell gnome-shell-common gnome-sudoku gnome-sushi 
gnome-system-log gnome-system-monitor gnome-terminal 
gnome-terminal-data gnome-themes-standard gnome-user-guide 
gnome-user-share
  gnome-utils-common gnome-video-effects gnomine gnotravex gnotski 
gnuchess gnuchess-book gnumeric gnumeric-common grilo-plugins-0.1 
gstreamer0.10-ffmpeg gstreamer0.10-fluendo-mp3 gstreamer0.10-gconf 
gstreamer0.10-nice gstreamer0.10-plugins-bad
  gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly 
gstreamer0.10-pulseaudio gstreamer0.10-x gtali gtk2-engines gucharmap 
gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-libs 
hamster-applet hwdata iagno inkscape libabiword-2.9 libaccountsservice0
  libapache2-mod-dnssd libatspi1.0-0 libavahi-gobject0 
libavahi-ui-gtk3-0 libbabl-0.1-0 libblas3gf libboost-iostreams1.49.0 
libboost-thread1.49.0 libbrasero-media3-1 libburn4 libcairo-perl 
libcamel-1.2-29 libcanberra-gtk-module libcanberra-gtk0 
libcanberra-gtk3-0
  libcanberra-gtk3-module libcanberra-pulse libcanberra0 libcap-ng0 
libcap2-bin libcapi20-3 libcaribou-common libcaribou0 libcdaudio1 
libcdio-cdda0 libcdio-paranoia0 libchamplain-0.12-0 
libchamplain-gtk-0.12-0 libcheese-gtk21 libcheese3 libclutter-1.0-0
  libclutter-1.0-common libclutter-gst-1.0-0 libclutter-gtk-1.0-0 
libclutter-imcontext-0.1-0 libcluttergesture-0.0.2-0 libcmis-0.2-0 
libcogl-common libcogl-pango0 libcogl5 libcolamd2.7.1 libcurl3-nss 
libdbus-glib1.0-cil libdbus1.0-cil libdmapsharing-3.0-2 libdv4
  libebackend-1.2-1 libebook-1.2-12 libecal-1.2-10 
libedata-book-1.2-11 libedata-cal-1.2-13 libedataserver-1.2-15 
libedataserverui-3.0-1 libepc-1.0-3 libepc-common libepc-ui-1.0-3 
libevince3-3 libevolution libexempi3 libexttextcat-data libexttextcat0 
libfolks-eds25
  libfolks-telepathy25 libfolks25 libgail-3-0 libgail-common libgcc1

Bug#667703: gnome

[Filipus Klutiero]

On 2012-04-07 15:56, Joey Hess wrote:

Filipus Klutiero wrote:

Josselin, why would the gnome metapackage already pull synaptic? I
don't see any direct relation. This is what happens on my
testing/unstable mix:

nautilus recommends synaptic.



In Squeeze, but not in Wheezy (see 
http://anonscm.debian.org/viewvc/pkg-gnome?view=revision&revision=31733 ).
As explained on debian-devel, the GNOME situation changed since Squeeze 
(and GNOME 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/4f809e34.9040...@gmail.com

Bug#288476: nForce 2 success

[Filipus Klutiero]

Package: installation-reports
INSTALL REPORT
Debian-installer-version: 20041217
uname -a: Linux leo.ido.ath.cx 2.6.8-1-k7 #1 Thu Nov 25 04:13:37 UTC 
2004 i686 GNU/Linux
Date: 20041230
Method: linux26 install from CD 1 of 2.

Machine: nForce 2
Processor: Barton 2500+
Memory: 256 MB
Root Device: SEAGATE BARRACUDA 7200.7 80GB HD ATA/100 8.5MS 7200
Root Size/partition table:
1primary4.7ntfs
5logic26.2fat32
6logic789.6swapswap
7logic31.3ext3/home
8primary17.0ext3/
Output of lspci and lspci -n:
:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different 
version?) (rev c1)
:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 0 
(rev c1)
:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 
(rev c1)
:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 
(rev c1)
:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 
(rev c1)
:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 
(rev c1)
:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a4)
:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a4)
:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a4)
:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet 
Controller (rev a1)
:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge 
(rev a3)
:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
:01:00.0 VGA compatible controller: nVidia Corporation NV25 
[GeForce4 Ti 4600] (rev a3)
:02:07.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)

:00:00.0 0600: 10de:01e0 (rev c1)
:00:00.1 0500: 10de:01ea (rev c1)
:00:00.2 0500: 10de:01ee (rev c1)
:00:00.3 0500: 10de:01ed (rev c1)
:00:00.4 0500: 10de:01ec (rev c1)
:00:00.5 0500: 10de:01ef (rev c1)
:00:01.0 0601: 10de:0060 (rev a4)
:00:01.1 0c05: 10de:0064 (rev a2)
:00:02.0 0c03: 10de:0067 (rev a4)
:00:02.1 0c03: 10de:0067 (rev a4)
:00:02.2 0c03: 10de:0068 (rev a4)
:00:04.0 0200: 10de:0066 (rev a1)
:00:08.0 0604: 10de:006c (rev a3)
:00:09.0 0101: 10de:0065 (rev a2)
:00:1e.0 0604: 10de:01e8 (rev c1)
:01:00.0 0300: 10de:0250 (rev a3)
:02:07.0 0401: 1274:5880 (rev 02)
Base System Installation Checklist:
Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
Comments/Problems:
Hi, this is my second time with d-i, after a first experience with 
Debian in June. I used a 20041217 snapshot and installed with "linux26" 
several times because I wanted to test a driver without taking risks and 
I'm not experienced in kernel stuff.

Usability
Partitionning was not totally easy. I used the automatic partitioning 
first and it generated the current partition table previously detailed 
except that 10 GB were in partition 7 (then 41.3) GB instead of 
partition 8 (then 7.0 GB). Starting from there I wanted to decrease 
partition 7's size by 10 GB to 8's profit. If I remember right, resizing 
implied deleting partitions and recreating them. Even there, if I 
recreated 7 with 31.3 GB, I couldn't create a 17.0 GB 8th partition, 
which seemed to be a bug. You might want to test the usability of a 
simple resizing.

One problem that didn't change much since June is setting up an Internet 
connection with DSL. d-i allows to setup a connection either via a 
gateway, either with dial-up, not with DSL. The worst is that this is 
not really clear, because a new person will wonder whether PPP allows 
DSL connections (PPPoE...a subset of PPP?). Since I installed several 
times, I focused on verifying if this was clear and IMHO, first-timers 
are more likely to attempt to connect DSL with PPP than understand they 
can't. Approximately translated, the installation says "If you have an 
account at an ISP and you want to use it during the install, you can 
configure the PPP service now so that a PPP connection to your access 
provider can be established." I do have an account at an ISP and want to 
use it during install. What tells me I can't? If you try to setup the 
connexion before realizing you can't, the installer will say later, 
after "Impossible to access security updates.", "You should find the 
reason of this *error* later." and prints several error messages...not 
really reassuring.

In general I consider the usability medium, with the lack of mouse 
support, back buttons, and use of tasksel/apti

Bug#288476: acknowledged by developer (Re: Bug#288476: nForce 2 success)

[Filipus Klutiero]

Debian Bug Tracking System a écrit :
This is an automatic notification regarding your Bug report
#288476: nForce 2 success,
which was filed against the installation-reports package.
It has been closed by one of the developers, namely
Christian Perrier <[EMAIL PROTECTED]>.
Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Received: (at 288476-done) by bugs.debian.org; 4 Jan 2005 06:54:59 +
From [EMAIL PROTECTED] Mon Jan 03 22:54:59 2005
Return-path: <[EMAIL PROTECTED]>
Received: from onera.onera.fr [144.204.65.4] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Cliap-0002Z8-00; Mon, 03 Jan 2005 22:54:59 -0800
Received: from cc-mykerinos.onera (localhost [127.0.0.1])
   by onera.onera.fr  with ESMTP id j046svpR018088;
   Tue, 4 Jan 2005 07:54:57 +0100 (MET)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
	id 755D0232B0; Tue,  4 Jan 2005 07:40:59 +0100 (CET)
Date: Tue, 4 Jan 2005 07:40:59 +0100
From: Christian Perrier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#288476: nForce 2 success
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-message-flag: Outlook is a good virus spreading tool. It can send mail, too.
X-pot_a_miel: [EMAIL PROTECTED]
User-Agent: Mutt/1.5.6+20040907i
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by onera.onera.fr id j046svpR018088
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Quoting Filipus Klutiero ([EMAIL PROTECTED]):
 

The last point is about locales. I use French in Canada (fr_CA) and a=20
PS/2 104 keys keyboard and that doesn't work well. At the last step=20
before the first reboot, d-i proposes to "go back" instead of rebooting=
   

.=20
 

If you choose that and end the first part immediately after, the second=
   

=20
 

part will be in "expert" mode. Then you'll see a step "Postconfigure=20
   

This is expected behaviour.
 

language-related parameters". At this step, d-i only writes "Unsupporte=
   

d=20
 

locale fr_CA" quickly. Probably as a consequence, my X is configured by=
   

=20
 

default with "us" keyboard. Then, this probably causes KDE to also use=20
   

This message is harmless. It will soon be removed from localization-confi=
g.
It happens for all locales, supported or not, indeed..:-)
 

the wrong keyboard layout by default (this is pretty irritating...).=20
Also, KDE is set by default to use the Imperial measure system, even if=
   

=20
 

I'm in Canada. Finally, in expert mode, I can choose the papersize, and=
   

=20
 

it says that A4 is certainly the good size, even if I'm in Canada (I=20
wish that would be true...). Obviously in normal installs d-i will=20
automatically pick up the wrong size. What needs to be done to make d-i=
   

=20
 

support fr_CA?
   


Nothing. It supports fr_CA. I'm not really sure about the KDE paper
size thing but this definitely is not a d-i problem.
Given that this install report is a complete success report, I do as
usual with successful install report=A0: 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 yourtime testing the Debian Installer and reporting
your results. Have fun with your new Debian system!

 

Hi Christian,
/etc/papersize is not related to KDE, but to dpkg-reconfigure libpaper1 
so affects all programs, like OOo under Gnome. Also, even if my 
installation was mainly successful, I was wondering if the problem of X 
defaulting to us instead of fr_CA was known. I didn't know about 
dpkg-reconfigure xserver-xfree86 until months after I installed debian 
for the first time, so it's not cool if you have to run that immediately.

Philippe

pcmciautils utility for CardBus (Re: Bug#698105: Please remove pcmciautils from laptop task)

[Filipus Klutiero]

Hi Colin,

Colin Watson wrote:

On Mon, Jan 14, 2013 at 06:33:53AM +0100, Michael Biebl wrote:
>  PCMCIA is so uncommon nowadays that installing pcmciautils on every laptop
>  by default is imho no longer warranted. I would thus like to see it removed
>  from task-laptop, similar to apmd.
>  PCMCIA has been a technology which was relevant in the 1990s and has
>  been superseded by e.g. ExpressCard for over 10 years.
>
>  I've CCed Colin, the pcmciautils maintainer, for his input.

pcmciautils is a slightly misleading name, as it does some CardBus
handling as well.  However, it's true that udev improvements mean that
it's no longer actually needed to get anything other than 16-bit PCMCIA
cards up and running; so I think this proposed tasksel change is OK.


If pcmciautils can actually be useful in any way for CardBus in wheezy, 
the misleading name is a secondary problem considering that while the 
short description, the extended description and the manual pages mention 
PCMCIA, none say anything about CardBus. I do not see any clue from the 
package that it could help CardBus.



--
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/511805ba.3060...@gmail.com

Bug#705259: Only some EFI systems affected

[Filipus Klutiero]

It seems on the Lenovo (and all UEFI systems?) Windows is not anymore
booted through the nt loader but through an efi boot loader
residing in the efi partition.


I can assert that some EFI systems are not affected by this. My Windows 
8 install on an ASUS F2A85-M can be booted from the GRUB entry, which is 
similar to the one GRUB generated for Dieter.



--
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/51774186.4060...@gmail.com

Bug#705259: Related

[Filipus Klutiero]

Both these tickets report bugs identical or similar. I didn't 
investigate enough to tell what to do though.



--
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/517c2e63.9020...@gmail.com

Re: [DRAFT] Debian Installer Wheezy Alpha1 release

[Filipus Klutiero]

Thank you Cyril and everyone.
In terms of presentation, this looks fine to me. In terms of content, I 
added all issues from DebianInstaller/Today which I'm confident affect 
alpha1 (that is, 1 issue).



On 2012-05-12 15:50, Cyril Brulebois wrote:

Hi folks,

I prepared the following draft, based on copy-pastes from:
   http://wiki.debian.org/DebianInstaller/ReleaseAnnounce

I took the liberty to replace “Wheezy” with “7.0” to match the previous
announce, which mentioned “6.0”. I have no strong (or bad) feeling about
this, just wanted to be consistent with prior art by default.

Please let me know of any issues with it, stuff that would be missing
etc. I guess you could just mention anything by mail, also fixing the
wiki. I guess/hope there won't be too many changes to merge, so that
shouldn't be too painful.

Steve/debian-cd: As mentioned on IRC basic tests made some bugs pop up,
but nothing that should block alpha1 as far as I can tell. So please
publish the images.

The draft follows.

Mraw,
KiBi.



From: Cyril Brulebois
To: debian-devel-annou...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Debian Installer 7.0 Alpha1 release
Organization: Debian

The Debian Installer team[1] is pleased to announce the first alpha
release of the installer for Debian Wheezy.


Improvements in this release of the installer
=

Network configuration
-
  * Add WPA support to installer (#327309).
  * Improvements in link detection and DHCP configuration, which
should improve reliability for systems with flaky network
cards (#496647, #414117, #606515).
  * Release DHCP lease at the end of the install, to work around
problems with non-RFC compliant DHCP servers (#610553).
  * The requirements for hostnames have been clarified, and the
parser tightened up to avoid letting through some really
dodgy names (#399071).
  * Added Spanning Tree Protocol (STP) support.

Linux Specific
--
  * Kernel version has been updated to 3.2.16.
  * Default filesystem changed to Ext4.
  * Allow btrfs /boot partition (grub2 and lilo).
  * Add support for Network Block Devices (NBD).

GNU/kFreeBSD Specific
-
  * Kernel updated to version 8.3.
  * Detect LVM devices.

Operating system probing

  * Add detection for Windows 8, support for BSD systems, MeeGo,
Linux From Scratch and Haiku on BeFS partitions.
  * Improve Windows and MS-DOS detection.
  * Fix Gentoo detection on OS probing.

Win32-loader

  * Add PXE functionality (#607417).

USB stick installs
--
  * Add choice of ISO image to use when multiple images are found
on the installation medium (#564441). This includes a full
rewrite of the state machine in the iso-scan component. This
work was contributed by Frans Pop and Frédéric Boiteux.

Translations

  * New language supported: Uyghur.


Behavioral changes in this release
==

  * Make sure to put "hda" into the CoLo config file instead
of "sda" since CoLo only knows about the former (#614839).
  * Remove 5 second sleeps when debootstrap finds additional
required dependencies. d-i just got that much faster.
  * Use SHA checksums.
  * Re-enable ZFS on kfreebsd-i386.
  * Allow stripped ZFS for root filesystem.
  * Mirror and RAID-Z support on ZFS filesystems.
  * Redesign ZFS pool management, new features include:
 - Support for pools with multiple physical devices.
 - Support for multiple filesystems within a ZFS pool.
 - Support for legacy filesystems using ZFS volumes (ZVOL).
 - Arbitrary names for ZFS pools, filesystems and ZVOLs.
  * Switch espeakup language around language selection (#630477).


Hardware support changes


  * Support AMD CPU family 20 (LP: #676838).
  * Add support for:
 - Buffalo Linkstation LiveV3 (LS-CHL) (#612167).
 - Buffalo Linkstation Mini (LS-WSGL).
 - Toshiba AC100.
 - MX53 LOCO board.
 - OMAP4 Pandora.
 - armhf architecture.
 - Genesi Efika MX nettops and smarttops (#612376).
  * Blacklist snd-aoa to allow snd-powermac to work.
  * Install mmc-modules if no disk is found, since some devices
may not have hard drives, but SD slots instead (#593108).
  * Increase the number of attempts to detect new disk devices on
some SCSI subsystems with long driver/disk initialization
time (#611314).
  * Include ahci module for the QNAP TS-419P+ (#613497).
  * Add niu network driver for sparc, needed by T2+ Sparc
systems (#608516).
  * Recognize /dev/duart* as a serial console.


Known issues in this release


  * kFreeBSD installer images don't work (kernel panic) (#671884).
  * GRUB installation fails with RAID+LVM (#662086).
  * Linux kernel installation fails on old x86 processors (earlier

Bug#673715: [installation-guide] boot.img now creates a 1 GB filesystem, no longer 256 MB

[Filipus Klutiero]

Package: installation-guide
Severity: normal
X-Debbugs-Cc: 666...@bugs.debian.org

According to 4.3.1. Copying the files — the easy way:

Note that, although convenient, this method does have one major 
disadvantage: the logical size of the device will be limited to 256 
MB, even if the capacity of the USB stick is larger.


http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html

This is no longer correct with the work done on #666090. boot.img is now 
a 1 GB filesystem. This also makes the following sentence wrong:


A second disadvantage is that you cannot copy a full CD image onto the 
USB stick, but only the smaller businesscard or netinst CD images. 


The enlargement of boot.img now allows putting CD 1 on the stick :-)
One unfortunate consequence which I didn't foresee, though, is that 
writing boot.img to the key is now significantly longer (at least with 
my key/laptop) :-(

Unused space is written with blank.




--
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/4fb983f7.9030...@gmail.com

Bug#673997: apt-cdrom issue now fixed

[Filipus Klutiero]

On 2012-06-05 17:09, Miguel Figueiredo wrote:

This is now fixed.
My guess this was fixed with apt 0.9.5.1.



It's still broken here (testing).



--
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/4fce7bd7.4000...@gmail.com

Confirmed

[Filipus Klutiero]

Thank you for the fix Milan. I verified that 0.9.6 fixes the problem on 
my testing install. However, this report shouldn't have been downgraded.


Thank you also for applying the fix David, although it would be nice to 
watch credits in the future.
It would also have been nice to upload a new version focusing on this 
bug (and perhaps other important bugs) at high urgency. This needs to 
migrate to testing before dailies and weeklies get usable again. I asked 
the release team to consider urging migration anyway.



--
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/4fdaadca.4010...@gmail.com

Dailies fixed

[Filipus Klutiero]

apt 0.9.6 migrated to testing on June 17th thanks to hinting from Adam 
D. Barratt. I verified that dailies are finally fixed. I was able to 
install using 
http://cdimage.debian.org/cdimage/daily-builds/daily/20120619-5/i386/iso-cd/debian-testing-i386-netinst.iso

Weeklies may be fixed too (last build was on June 18th).


--
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/4fe0ef84.1040...@gmail.com

Bug#666750: Solved

[Filipus Klutiero]

retitle 666750 Please avoid differences between OS-en detected in the 
installer and those offered in GRUB

severity 666750 wishlist
tags 666750 - wheezy sid
thanks

This no longer happens with grub2 1.99-19 ("Add grub-probe to 
grub-mount-udeb").
I'm keeping this report as a wish to prevent new occurences of the same 
symptom from new causes. Feel free to treat as you think is best.




--
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/4fe0ff45.1050...@gmail.com

Bug#650819: Also affects GRUB prompt now

[Filipus Klutiero]

Now that grub2 1.99-19 was uploaded, this doesn't just affect grub.cfg:

  * Add grub-probe to grub-mount-udeb (LP: #963471).
grub-installer's prompt before installing GRUB is now, from what I can 
see, always broken, so it's at least as bad as the grub.cfg actually 
generated. Therefore, this doesn't cause #666750 anymore. The worst that 
should happen now if users are careful is that they'd refuse to install 
Debian.


There are now 2 scenarios:

1. If installing a Linux image different from the installer's image,
   both the prompt and the actual grub.cfg will lack other OS-en, so
   this is a consistent failure.
2. If installing the same Linux image as the installer's, the prompt
   will lack other OS-en, but the actual grub.cfg will have other
   OS-en, so this is just a false alarm.

I witnessed scenario 1 installing i386 on a recent desktop (686-pae). I 
witnessed scenario 2 installing i386 on a non-PAE laptop. Installs of 
the amd64 architecture should be in scenario 2. In the end, this is a 
regression for amd64, but a big (unintended) "improvement" for i386.

Bug#667703: Mostly solved (was Re: Filed (Re: Preinstalled package manager(s) for PCs (wheezy)))

[Filipus Klutiero]

On 2012-04-05 20:20, Filipus Klutiero wrote:
This didn't generate as much feedback as I hoped, but I filed a ticket 
asking task-desktop to install synaptic: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667703


Joey Hess changed tasks to bring Synaptic in KDE, LXDE and Xfce. Only 
the GNOME situation is unchanged (Josselin Mouette alleged that gnome 
already pulls in Synaptic).

tasksel 3.10 should migrate to testing shortly.



--
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/4feb27ee.7060...@gmail.com

Bug#667703: Apper instead of Synaptic for KDE (was Re: Mostly solved (was Re: Filed (Re: Preinstalled package manager(s) for PCs (wheezy))))

[Filipus Klutiero]

Hi Matthias,

On 2012-06-27 14:54, Matthias Klumpp wrote:

Hi!
How odd that I didn't notice that bug... (I'm the GPK/PK maintainer)
Well, I think pulling in Synaptic on KDE might be a bad idea, probably
KDE desktop packages should pull in Apper instead, a KDE package
manager based on PackageKit and fully integrated into the KDE desktop.
It does not provide all functions of Synaptic, but for most users it
will be good enough and KDE can avoid pulling in many GNOME packages.



Synaptic is at best just a little GNOME-ish, beyond its GTK-ness. In 
reality, installing Synaptic would install just a little more than Apper 
- perhaps. Apper probably does integrate with KDE, but this is a small 
advantage compared to the difference in maturity. I wouldn't be strongly 
against installing Apper by default, but replacing Synaptic is a bigger 
challenge.


[...]



--
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/4feb7e59.7030...@gmail.com

Bug#415634: The kde-desktop task already has a multimedia player

[Filipus Klutiero]

On 2012-07-13 17:56, Christian PERRIER wrote:

It installs kde-standard that actually install juk.

So there's indeed no need for Yet Another Multimedia Player. If you
thing that amarok should replace juk, then please file a bug report
against kde-standard.



Amarok is not "Yet Another Multimedia Player", unless you have something 
other than JuK in mind as reference. Amarok is not strictly superior to 
JuK since it is a lot larger, and surely generally more heavyweight. On 
a business install, having JuK must be enough. But for most "personal" 
computers, Amarok is a better choice. As evidence, even though JuK is 
installed by default while Amarok isn't, Amarok has more than twice as 
many votes as Amarok (2322 vs 927).


I cannot figure out how I computed Amarok's size as 78 MB. In any case, 
documentation was now split into amarok-doc, and Amarok's current size 
(2.6~beta1+75.g47e75df-1) is now just 45 MB if excluding amarok-doc 
(which is merely suggested by amarok), which is a lot better. It would 
probably be best to install JuK or Amarok depending on the target 
system's power, but failing infrastructure to facilitate that, and 
considering that using a single player would be more consistent, I 
believe Amarok should indeed replace JuK as the default music player for 
KDE, given this new number. I believe the proportion of PCs which will 
lack power to prefer Amarok over JuK by the time we release 8 should be 
negligible.


I agree it would be best if the KDE team could manage which packages are 
recommended, however, it's not clear that installing Amarok fits in 
kde-standard's scope. I asked for a clarification of kde-standard in 
#666968.



--
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/5002fbf2.9050...@gmail.com

Bug#667703: Mostly solved (was Re: Filed (Re: Preinstalled package manager(s) for PCs (wheezy)))

[Filipus Klutiero]

On 2012-06-27 11:34, Filipus Klutiero wrote:

On 2012-04-05 20:20, Filipus Klutiero wrote:
This didn't generate as much feedback as I hoped, but I filed a 
ticket asking task-desktop to install synaptic: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667703


Joey Hess changed tasks to bring Synaptic in KDE, LXDE and Xfce. Only 
the GNOME situation is unchanged (Josselin Mouette alleged that gnome 
already pulls in Synaptic).


I tested d-i last week and accidentally installled GNOME. This allowed 
me to confirm that GNOME does not pull Synaptic in testing.



tasksel 3.10 should migrate to testing shortly.


tasksel 3.11 has now migrated to testing.


--
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/5008a4d8.8090...@gmail.com

Bug#650819: Worked around

[Filipus Klutiero]

severity 650819 normal
close 684265 3.2.29-1
forcemerge 650819 686314
thanks

This is no longer RC. A workaround has finally been applied, namely the 
first one, adding fuse. It will take some time before the fix makes it 
to install media. Note that I did not verify that the current symptom is 
gone and am closing its report assuming that fuse was properly added to 
installer images.


We should still apply one of solutions 3 or 4, but this is no longer urgent.


--
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/50590880.5070...@gmail.com