[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#684954: marked as done (installation-reports: fine apart from timezone & apt translations)

Your message dated Wed, 15 Aug 2012 08:03:29 +0200
with message-id <20120815060329.GD5423@mykerinos.kheops.frmug.org>
and subject line Re: Bug#684954: installation-reports: fine apart from timezone & apt translations
has caused the Debian Bug report #684954,
regarding installation-reports: fine apart from timezone & apt translations
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
684954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684954
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: CD
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta1/i386/iso-cd/debian-wheezy-DI-b1-i386-netinst.iso
Date: Aug 11 13:37 PDT 2012

Machine: VIA CN400-8237/EPIA-SP
Processor: VIA C3-2 (Nehemiah)
Memory: 1G
Partitions: manual crypto layout, but irrelevant as everything worked fine

Output of lspci -knn (or lspci -nn):
 lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 Host Bridge [1106:0259]
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: agpgart-via
 lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 Host Bridge [1106:1259]
 lspci -knn: 00:00.2 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 CPU Host Bridge [1106:2259]
 lspci -knn: 00:00.3 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 Host Bridge [1106:3259]
 lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 Host Bridge [1106:4259]
 lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, Inc. CN333/CN400/PM880 Host Bridge [1106:7259]
 lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198]
 lspci -knn: 00:0d.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80)
 lspci -knn:     Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044]
 lspci -knn:     Kernel driver in use: firewire_ohci
 lspci -knn: 00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller [1106:3149] (rev 80)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: sata_via
 lspci -knn: 00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: pata_via
 lspci -knn: 00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: uhci_hcd
 lspci -knn: 00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: uhci_hcd
 lspci -knn: 00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: uhci_hcd
 lspci -knn: 00:10.3 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn:     Kernel driver in use: uhci_hcd
 lspci -knn: 00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 86)
 lspci -knn:     Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
 lspci -knn:     Kernel driver in use: ehci_hcd
 lspci -knn: 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] [1106:3227]
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn: 00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:aa01]
 lspci -knn: 00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 78)
 lspci -knn:     Subsystem: VIA Technologies, Inc. Device [1106:0102]
 lspci -knn:     Kernel driver in use: via-rhine
 lspci -knn: 00:14.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02)
 lspci -knn:     Subsystem: Intel Corporation Device [8086:002e]
 lspci -knn:     Kernel driver in use: e1000
 lspci -knn: 01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN400/PM800/PM880/PN800/PN880 [S3 UniChrome Pro] [1106:3118] (rev 02)
 lspci -knn:     Subsystem: VIA Technologies, Inc. CN400/PM800/PM880/PN800/PN880 [S3 UniChrome Pro] [1106:3118]

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:   [E]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:

   The only serious problem I faced with the wheezy beta installer was
the inability to set my timezone correctly on install.  I gather the
timezone choices are dictated by the "location" choice early on in the
install process, but even while I think its a big mistake to limit the
available timezone choices based on the physical location of a system,
more egregious, was the total inability to choose UTC.  It really
makes me wonder what worthwhile utility the first location question
has at all; I strongly suspect there is none.  It isn't used to
determine an appropriate package mirror, and rightly so, becuase
network latency and physical proximity are all too often at odds
anyhow.  It isn't used to impose strict language choices because that
would be myopic.  It shouldn't be used to restrict timezones, because
there are plenty of situations where you want to set a system's
localtime to something that doesn't actually match is physical
location---servers always kept in UTC regardless of location probably
being the most common example.

    The other issue I ran into has already been reported in bugs
#641967 and #678227, wherein apt wastes time and bandwidth downloading
translation files I have no use for by default.

-- 
Jamie Heilman                     http://audible.transient.net/~jamie/

--- End Message ---
--- Begin Message --- 
Quoting Jamie Heilman (jamie@audible.transient.net):

> Comments/Problems:
> 
>    The only serious problem I faced with the wheezy beta installer was
> the inability to set my timezone correctly on install.  I gather the
> timezone choices are dictated by the "location" choice early on in the
> install process, but even while I think its a big mistake to limit the
> available timezone choices based on the physical location of a system,
> more egregious, was the total inability to choose UTC.  It really
> makes me wonder what worthwhile utility the first location question
> has at all; I strongly suspect there is none.  It isn't used to

That's not correct. The initial choice of location has a *lot* of
consequences.

> determine an appropriate package mirror, and rightly so, becuase
> network latency and physical proximity are all too often at odds
> anyhow.  It isn't used to impose strict language choices because that
> would be myopic.  It shouldn't be used to restrict timezones, because
> there are plenty of situations where you want to set a system's
> localtime to something that doesn't actually match is physical
> location---servers always kept in UTC regardless of location probably
> being the most common example.


This is a design choice.

Localechooser makes it very clear that the country location impacts
the timezone choices (at least as clear as one can be in a two
sentences screen). 


If you want to use a given timezone, then choose
the appropriate country in localechooser. This is meant for that
purpose.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: