Bug#693510: installation report

[Anton Andreev]

Package: installation-reports

Boot method: default text mode installer
Image version: 
http://hammurabi.acc.umu.se/cdimage/wheezy_di_beta3/kfreebsd-amd64/iso-cd/debian-wheezy-DI-b3-kfreebsd-amd64-xfce-CD-1.iso
Date: 17/11/2012 dd/mm/yyy

Machine: Virtual box amd 64
Processor:
Memory:
Partitions: Virtual box ide disk

Output of lspci -knn (or lspci -nn):

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: [E ]

Could not get identity of device /dev/ada0 - Inappropriate ioctl for device

Partition hard drives:  [E ]

All default settings selected, such as guided, ufs ...

update-dev: warning: unable to find udevadm; skipping
partman: mkfs.ufs: /dev/ada0s1: failed to open disk for writing

Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:


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

building and testing d-i with jenkins

[Holger Levsen]

Hi,

as you might have seen, I'm running certain d-i jobs on 
http://jenkins.debian.net/

There are three views showing d-i related jobs, which are 
http://jenkins.debian.net/view/d-i_packages/ 
http://jenkins.debian.net/view/d-i_manual/ 
http://jenkins.debian.net/view/d-i_misc/ 

In these views 4 kinds of jobs are shown and run:

d_i_build_* - there is one job for each git repo referred to in 
http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co
Each job pdebuilds the master branch of its git repo on every git push in a 
sid environment.

d_i_manual - builds the full installation-guide package with pdebuild in sid 
on every commit to svn://svn.debian.org/svn/d-i/ matching these patterns: 
/trunk/manual/debian/.*, /trunk/manual/po/.*, /trunk/manual/doc/.* 
/trunk/manual/scripts/.*

d_i_manual_* - builds a language (on wheezy) on every commit of 
svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64 
formats=html"

d_i_parse_build_logs - parses logs from http://d-i.debian.org/daily-
images/build-logs.html daily, to give them a bit more exposure.


IMHO this is just more or less a demo what could be done, as I'm quite aware 
that these are not really optimal jobs to support d-i development - which is 
my motivation to do this :-) So you need to tell me more what you need, or 
what is sensible. 

http://jenkins.debian.net/userContent/about.html has a general description of 
the setup.


Stuff I already know is missing:

* svn/trunk/packages - I have no idea what to build here, but I see frequent 
commits. Can you help?

* notifications - while jenkins does nice email notifications by default (it 
sends mail on every failure and when a build succeeds, it informs once and 
then it shuts up til the next failure), I think it's better to start with IRC 
notifications in #debian-boot - what do you think?

* testing actuall installations with d-i, for that I plan to give 
http://www.os-autoinst.org/ a try

* bubulle already wrote: 'Another interesting target would be d-i builds 
including non uploaded packages (something like "d-i from git repositories" 
images). That would in some way require to create a quite specific image, with 
all udebs (while netboot only has udebs needed before one gets a working 
network setup).' - as you can see I'm going in that direction, but I'm not 
there yet. 


Feedback very much welcome. I'll reply to this mail myself too, to keep this 
mail somehwat short, but I still want to explain the current build failures... 
(and ask & give ideas how to deal with them.)


cheers,
Holger


-- 
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/201211171147.51179.hol...@layer-acht.org

d-i manual (Re: building and testing d-i with jenkins)

[Holger Levsen]

Hi,

On Samstag, 17. November 2012, Holger Levsen wrote:
> d_i_manual - builds the full installation-guide package with pdebuild in
> sid on every commit to svn://svn.debian.org/svn/d-i/ matching these
> patterns: /trunk/manual/debian/.*, /trunk/manual/po/.*,
> /trunk/manual/doc/.* /trunk/manual/scripts/.*

Instead of building the full installation-guide package on commits in 
/trunk/manual/po/$LANG I'd like to only build that language - how can I do 
this?
 
> d_i_manual_* - builds a language (on wheezy) on every commit of
> svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64
> formats=html"

first, I don't really get the difference between svn/trunk/manual/$LANG and 
svn/trunk/manual/po/$LANG - can someone please explain?

second, http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_eu/ fails to 
build, as as far as I can see, rightfully. Seems to be a ".po file with broken 
XML inside" issue.


cheers,
Holger


-- 
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/201211171341.40597.hol...@layer-acht.org

Re: building and testing d-i with jenkins

[Holger Wansing]

Hi,

Holger Levsen  wrote:
> d_i_manual_* - builds a language (on wheezy) on every commit of 
> svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64 
> formats=html"

In the past I had errors in my d-i manual translation, which only affected
the pdf variant of the manual.
So it would probably good, to build pdf as well.

> * notifications - while jenkins does nice email notifications by default (it 
> sends mail on every failure and when a build succeeds, it informs once and 
> then it shuts up til the next failure), I think it's better to start with IRC 
> notifications in #debian-boot - what do you think?

For the d-i manual part, the only way to inform translators about errors
in their translations will probably be via e-mail (don't know if this is
already intended, but that would be the optimal: if manual in de fails
to build (when building the de manual because of a commit to manual/de/ ),
only inform the german translator, don't bother others).
This may apply to other parts as well.

Holger W.


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20121117152314.5b640c97.li...@wansing-online.de

Re: d-i manual (Re: building and testing d-i with jenkins)

[Holger Wansing]

Hi,

Holger Levsen  wrote:
> On Samstag, 17. November 2012, Holger Levsen wrote:
> > d_i_manual - builds the full installation-guide package with pdebuild in
> > sid on every commit to svn://svn.debian.org/svn/d-i/ matching these
> > patterns: /trunk/manual/debian/.*, /trunk/manual/po/.*,
> > /trunk/manual/doc/.* /trunk/manual/scripts/.*
> 
> Instead of building the full installation-guide package on commits in 
> /trunk/manual/po/$LANG I'd like to only build that language - how can I do 
> this?

As documented in manual/doc/translations_po.txt:
Use the following commands:
  1. ./scripts/merge_xml en
  2. ./scripts/update_pot
  3. ./scripts/update_po 
  4. ./scripts/revert_pot
  5. ./scripts/create_xml 

> > d_i_manual_* - builds a language (on wheezy) on every commit of
> > svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64
> > formats=html"
> 
> first, I don't really get the difference between svn/trunk/manual/$LANG and 
> svn/trunk/manual/po/$LANG - can someone please explain?

There are two ways of translating the manual: via xml files (as the english
original is) and via po files.
In manual/$LANG there are the xml based translations, in manual/po/$LANG
are the po based ones.


Holger W.


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20121117152830.6251426a.li...@wansing-online.de

Re: building and testing d-i with jenkins

[Joey Hess]

Holger Levsen wrote:
> as you might have seen, I'm running certain d-i jobs on 
> http://jenkins.debian.net/
> 
> There are three views showing d-i related jobs, which are 
> http://jenkins.debian.net/view/d-i_packages/ 
> http://jenkins.debian.net/view/d-i_manual/ 
> http://jenkins.debian.net/view/d-i_misc/ 

You forgot to mention http://jenkins.debian.net/view/chroot-tests/ which
all test debootstrap and task installs. 

> * svn/trunk/packages - I have no idea what to build here, but I see frequent 
> commits. Can you help?

Of traslations to packages/po, presumably. Since these are in turn
exploded out to the translations of individual packages that you already
test, I don't think additional tests are needed here.

> * notifications - while jenkins does nice email notifications by default (it 
> sends mail on every failure and when a build succeeds, it informs once and 
> then it shuts up til the next failure), I think it's better to start with IRC 
> notifications in #debian-boot - what do you think?

If IRC notifications tend to come shortly after commit notifications, I
think using IRC makes sense.

I'd like to see debootstrap failure notifications sent to debian-devel,
or someplace like that. It can be caused by breakage in a great many
packages, and getting Debian as a whole to own keeping debootstap and
task installs working would take some load off of d-i.


Thanks for your work.  Very much appreciated.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password

[Holger Wansing]

Hi,

Richard Owlett  wrote:
> Package: installation-reports
> Severity: important
> 
> *** Please type your report below this line ***
> 
> _PROBLEM HISTORY_
> I've been doing a series of Debian installs over the last 
> several months.
> Purpose:Evolve a install meeting a personal minimal and 
> Functional.
> Constraint: NO network physically available. Install from 
> purchased set of DVDs.
> 
> I have a history of problems with the root password not 
> being recognized.

It would be useful, if you could try to reproduce that bug with
the current daily build for Wheezy:
http://www.debian.org/devel/debian-installer/


thanks
Holger


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20121117171539.ce250b73.li...@wansing-online.de

Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password

[Richard Owlett]

Holger Wansing wrote:

Hi,

Richard Owlett  wrote:

Package: installation-reports
Severity: important

*** Please type your report below this line ***

_PROBLEM HISTORY_
I've been doing a series of Debian installs over the last
several months.
Purpose:Evolve a install meeting a personal minimal and
Functional.
Constraint: NO network physically available. Install from
purchased set of DVDs.

I have a history of problems with the root password not
being recognized.


It would be useful, if you could try to reproduce that bug with
the current daily build for Wheezy:
http://www.debian.org/devel/debian-installer/


thanks
Holger



I only have occasional acces to a high speed internet 
connection. Normal connection is dial-up :(



--
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/50a7ca55.8030...@cloud85.net

Bug#692458: debian installer hangs when entering user name in non-latin languages

[Samuel Thibault]

Hello,

I still can't reproduce the issue. Here are the steps I'm following:

- Start virtualbox 4.1.18-dfsg-1.1
- Create virtual machine with Linux Debian parameters, 1GiB memory,
  8GiB HDD
- Booting debian-wheezy-DI-b3-amd64-CD-1.iso with the graphical
  installer boot entry.
- At the language question, I choose Malayalam.
- At the warning about translation, I choose to continue
- From there, I'm choosing all the default answers, until:
- As root passwd, I type just b
- As user name, I switch to Malayalam using alt-shift, then type on keys
hdjbrCd] (naming keys through the qwerty layout), it seems to be
printing the same as above.
- As user login, I do the same

then I'm getting the error message about login having to be just
letters, without any hang.

Could you review the details above and check what could be different in
your (failing) case?

Samuel


-- 
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/20121117205038.GA14234@type

Bug#693574: Debian Installer 7.3 Beta - Xfce4 CD1 - Successful

[Guy Fontaine]

Package: installation-reports

Boot method: 
Image version: /debian-wheezy-DI-b3-i386-xfce-CD-1.iso>

Date: <2012-11-17/19h00 EST (GMT - 5)>

Machine: 
Processor: Pentium 4
Memory: 2 GB
Partitions:

Disk /dev/sda: 488397168 sectors, 232.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 1CB12959-6BEE-48FD-9E3F-F334CF2F40F1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 2048-sector boundaries
Total free space is 191267117 sectors (91.2 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   12048  194559   94.0 MiB0700
   2  194560  258047   31.0 MiBEF02
   3  258048 4163583   1.9 GiB 8200
   4 4163584   101820415   46.6 GiB0700
   5   101820416   297132031   93.1 GiB0700

/ and /home formated with BTRFS

Résultat de lspci -knn (ou lspci -nn) :


guy@gamma:~$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface [8086:2570] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80f2]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 82865G/PE/P AGP Bridge
[8086:2571] (rev 02)
00:06.0 System peripheral [0880]: Intel Corporation 82865G/PE/P
Processor to I/O Memory Interface [8086:2576] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) USB UHCI Controller #1 [8086:24d2] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) USB UHCI Controller #2 [8086:24d4] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) USB UHCI Controller #3 [8086:24d7] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) USB UHCI Controller #4 [8086:24de] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev c2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801EB/ER (ICH5/ICH5R)
LPC Interface Bridge [8086:24d0] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801EB/ER
(ICH5/ICH5R) IDE Controller [8086:24db] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller [8086:24d3] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard 
[1043:80a6]
Kernel driver in use: i801_smbus
00:1f.5 Multimedia audio controller [0401]: Intel Corporation
82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller [8086:24d5] (rev 02)
Subsystem: ASUSTeK Computer Inc. P4P800 series motherboard [1043:80f3]
Kernel driver in use: snd_intel8x0
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD]
nee ATI Radeon R100 QD [Radeon 7200] [1002:5144]
Subsystem: Advanced Micro Devices [AMD] nee ATI Radeon AIW [1002:02aa]
Kernel driver in use: radeon
02:05.0 Ethernet controller [0200]: 3Com Corporation 3c940
10/100/1000Base-T [Marvell] [10b7:1700] (rev 12)
Subsystem: ASUSTeK Computer Inc. A7V600/P4P800/K8V motherboard 
[1043:80eb]
Kernel driver in use: skge
02:0a.0 Multimedia audio controller [0401]: Creative Labs SB Audigy
[1102:0004] (rev 04)
Subsystem: Creative Labs SB Audigy2 Platinum [1102:1002]
Kernel driver in use: snd_emu10k1
02:0a.1 Input device controller [0980]: Creative Labs SB Audigy Game
Port [1102:7003] (rev 04)
Subsystem: Creative Labs SB Audigy2 MIDI/Game Port [1102:0060]
Kernel driver in use: Emu10k1_gameport
02:0a.2 FireWire (IEEE 1394) [0c00]: Creative Labs SB Audigy FireWire
Port [1102:4001] (rev 04)
Subsystem: Creative Labs SB Audigy FireWire Port [1102:0010]
Kernel driver in use: firewire_ohci


Installation du système de base :
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD