[[!meta copyright="Copyright © 2010, 2011, 2013, 2014 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
I'd be quite helpful to have nightly builds in form of Debian `.deb`
packages.
* (german)
* Need to have an automation to get from Hurd upstream Git branches to
a branch usable in Debian.
IRC, freenode, #hurd, 2013-12-18:
http://darnassus.sceen.net/~teythoon/hurd-ci/ has hurd and
mig and gnumach packages built directly from the upstream git
repository
---
There is infrastructure available to test whole OS installations.
*
---
[[service_solahart_jakarta_selatan__082122541663/Debian_cross_toolchain]] for cross-building?
---
See also [[nightly_builds]].
# Debian Jenkins Instance
## IRC, OFTC, #debian-hurd, 2014-02-24
hi. can hurd be installed using d-i? If so, what about scripting
the installation on ?
pere: d-i works for Hurd, yes, with full graphical interface I
dunno. Maybe you can ask about scripting in #hurd, more people are
present there?
gnu_srs: the scripts in questions are for jenkins. quite easy to
write (d-i preseed scripts and qemu boot rules).
## IRC, OFTC, #debian-hurd, 2014-02-25
getting a automated test in jenkins running could show the status.
what is needed to boot the hurd d-i image with a preseed file using qemu?
git://git.debian.org/git/users/holger/jenkins.debian.net.git is the
repo with the jenkins build rules.
youpi: is it possible to start the hurd d-i installer with a preseed
file from the qemu command line? --append need --kernel, which I suspect
do not make sense with hurd?
can the d-i hurd installer take a preseed file at all? my initial
try failed. :(
i don't know
there has been talk here the other day about using qemus
multiboot capabilities to directly boot the hurd
[[hurd/running/qemu#multiboot]].
For d-i purposes, you'll additionally need:
$ wget http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/current/initrd.gz
..., and to the `--initrd` option prepend `'initrd.gz $(ramdisk-create)',`
before the `ext2fs.static`, and refer the latter to `gunzip:device:rd0` instead
of `device:hd0s1`.
I tried adding an url= option to grub when booting the installer,
but it seem to be ignored.
perhaps the preseed udeb is missing, or the network support was
enabled after preseed looked for the file?
uh, i don't know about that stuff, youpi creates the d-i images
ok. seem to me that the d-i images do not support preseeding at the
moment.
youpi: ^ did you succeed? if so, can you share how?
teythoon: nope, I concluded it didn't work, and left it to other to
fix. :)
pere, teythoon: IIRC preseeding can be put on the gnumach kernel
command line
but I'm wondering why you can't simply modify the disk image into
doing what you want
or you mean reinstalling the image each time?
youpi: the point is testing the installer, and that can only be done
by using the installer. :)
ok
I would like to see something like for hurd.
## IRC, OFTC, #debian-hurd, 2014-02-26
* gg0 setting up jenkins, almost time to give up
gg0: why do you set up jenkins?
because i want to fail at doing all things, not just something ;)
oops seems my setup just sent emails to jenkins+debian-qa
holger@layer-acht.org :/
#debian-qa will understand. :)
## IRC, OFTC, #debian-hurd, 2014-02-28
gg0: are you able to feed the installer one of the preseed files at
?
though jenking translates double quotes, need to escape the world
debian_sid_daily_lxde_preseed.cfg seem like a good candiate. :)
pere: i'm working on that, stuck at working around that mandatory
double quote
*initrd double quote
ok got a g-i-installation_debian_sid_daily_hurd_lxde able to boot
let's provide a preseed
shouldn't there be some info/debug consoles from tty 2 to 4?
there should be
maybe i can't send alt+NUM from vlc
ah, yes
you need to use the menu for that
press f8
great
(found out C+A+{1,2,3} give interesting monitor,serial,parallel
consoles btw)
not much options on menu
just clipboard management, quit, full screen, send ctrl-alt-del, send
F8
* gg0 takes "great" back
i guess it depends on vnc implementation
don't ask me how i found out one can switch console with
... left/right arrow keys
without alt pressed?
without alt pressed
I've already seen that with qemu, when focusing into/out from the
qemu window by using alt
somehow the alt state gets stuck
so you mean if i close viewer then reattach it, it doesn't happen
anymore? let's see
you're right
though yes alt+left/right switches consoles
the last is expected :)
it says kbd-udeb doesn't exist so it falls back to
hurd-debian-ports-udeb
that's not a problem
no partman-auto?
it should be working
i meant if it was installed but yes it gets it along with others
## IRC, OFTC, #debian-hurd, 2014-03-01
partman-auto would need to be patched to be able to discover
available disks
worked around by forcing /dev/hd1, jenkins creates disk with index=1
stuck at installation-report installed. seems it can't manage to
umount(then remount) /cdrom gracefully
or better it gets stuck at apt-cdrom ident
something like https://bugs.debian.org/598457
## IRC, OFTC, #debian-hurd, 2014-03-02
youpi: any chance to have monthly/weekly (daily would be too much i
guess) isos/images? can i help somehow?
I am wondering why having that
since we have up-to-date mirrors
i'd say to install with latest installer/gnumach/hurd/eglibc
so that means also rebuilding the d-i image
and in general to not have to manually produce them
youpi: the point is to automatically test the current images using
jenkins.debian.net, I believe. for that to work, current images need to
exist. :)
not only. i think saving youpi's time is also important
gg0: it doesn't really take me much time to generate images
it's about a few command lines to start, and then work on something
else :)
well though it still requires manual intervention which is not
scheduled and also error prone btw
gg0: I guess the most important help you could provide would be to
actually track when the autobuild breaks :)
what pros keeping it manual? i don't think disk space saving
it's not really a question of manual, but the frequency
I prefer to test manually before uploading something on my
somehow-official directory on people, anyway
but that doesn't mean we can't have weekly builds somewhere else
indeed
it's just that for tests it's good to have several images backlog,
but then it takes disk
well we could keeping "official" ones + say 6 monthly and say 4
weekly
* gg0 randomizes retention
-ing
gg0: check out my hurdtest program
it updates qemu images automatically, and runs a test suite,
creates snapshots
youpi: you'd just take actually care of official ones
and it can zero-fill the disk images to compact them for
publication
gg0: and have a cron for the others
on mirror.ftp-master
nice, we already have a disk image generator then
i shall clean it up and merge stuff that i have changed locally
i covered it in my early blog posts
i use it extensively to test the packages from hurd-ci
great. so usually at this point /me can't do anything so good work!
lol
crontabs are in place, scheduled on monday mornings
I have already completed a run, can be seen in weekly-0
great!
assuming it will work forever without maintenance, how many minutes
you'll save per month? :)
I don't think that'll save me time per month
since it's just an additional thing
youpi: so weekly-0 will always be the latest weekly (same about
monthly) ?
yes
how about adding -YYYYMMDD after -1 CD/DVD/NETINST number?
that'd mean more scripting
just to distinguish them
we already have timestamps from the server
unfortunately i can't script myself, i can suggest though :)
or scripts are available somewhere?
so current/ should be a link to weekly-0?
on mirror.ftp-master.debian.org, but I guess you don't have access
to it
no
definitely no
the point of current/ is to have something tested
ok
while weekly/monthly are most probably to get broken
so let's not point people at that
same story about diskimage? how do you generate them?
how about teythoon's way?
I do it by hand at the moment, but scripts would be welcome indeed
http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.txt
ok now stuck at grub install
## IRC, OFTC, #debian-hurd, 2014-03-03
i probably should force /dev/hd0 as i did for /dev/hd0s1 as root
device
if it's possible
what do you mean by forcing /dev/hd0s1 as root device ?
you shouldn't have to do that
my fear is that these additional images will mostly just bring
additionnal reports
i had to specify it in preseed
which won't really decrease the amount of work
as partman-auto/disk
it can recognize available disks
that's also because it can't list root partitions on rescue mode
well, all I can say without having (again) to spend time on it, is
that you're not supposed to have to do that
why are you using rescue mode?
if it can't list root partitions, then of course partman can't work
well, rescue mode should work
if you delve into non-tested parts of d-i, you'll surely encounter
bugs
well, less "should" than plain "d-i"
in that I've never really tested it
so don't be surprised that some bugs remain
no problem
but again, we don't really need more bug reports
but rather bug fixing
we already have enough to fix, no need to delve into advanced
things
sure, i'm just trying to make it work with all its limitations
it autopartition the disk well, it can't just make one choose among
disks because it can't probe and list them
then fix the probe & list
i'd like doing it, i'm better at working around for now though :)
one blocker is mount/umount stuff
[[glibc#mount]].
well, you'll have to get into fixing bugs for real someday
otherwise this is just adding to TODO lists
what mount/umount stuff?
(took a quick look at partconf)
non-existent mount.h for instance
do we have replacements?
not that I know of
21:53 < teythoon> gnu_srs1: i put a small hacks entry in the list
about moving the mount/umount functionality from our utilities to the
libc
ok
another thing i'd really like to see would be a physical shutdown,
halt-hurd which actually poweroffs the system
how to switch to sysvinit by default? next sysvinit upload?
physical shutdown means implementing APM or ACPI
have to teach jenkins it can shut it down :/
I'm extremely far from having the will for this
switching to sysvinit by default is a matter of saying that we want
to do it
I already asked for this on the list without answer IIRC
i can't find anything
anyway, just propose on the list
d-i grub-installer/bootdev string /dev/hd0 - here it is
next run should not need any interaction, though it needs 20 mins to
understand it has to destroy it and run won't be successful :/
due to missing acpi/apm
first graphical automated install http://postimg.org/image/vgagj06q7/
it seems 720x400
though jenkins passes video=vesa:ywrap,mtrr vga=788
by reconnecting it switched to 800x600
http://postimg.org/image/h32qjykrx/
but seems stuck now and i can't even switch from graphical to
consoles
unusually stuck at scanning cdrom
i'll check text install to see if it gets stuck there too
text install switches from 720x400 to 640x400
i confirm it gets stuck on scanning cdrom, i guess because of this
one https://bugs.debian.org/728153 which already broke load-install-cd i
already had to workaround
gg0: are you in contact with h01ger to update jenkins.debian.net
with your cool installation code?
pere: still trying to have something working
plus with new weekly cd, apt-cdrom bug makes install getting stuck at
first Scanning cdrom:
03:44 < gg0> i confirm it gets stuck on scanning cdrom, i guess
because of this one https://bugs.debian.org/728153 which already broke
load-install-cd i already had to workaround
do we really need the CD-1 image in weekly builds?
just netinst?
yes
well, i don't know debian installer well. what's the difference
between CD and NETINST besides that CD has more packages user doesn't
need to download?
has CD anything not in NETINST which is worth to continously test?
(talking about jenkins)
that's only it, yes
btw new ACPI on hurd consists of serial console to file + looping
grep "In tight loop: hit ctl-alt-del to reboot" && kill qemu
anything better?
filed http://bugs.debian.org/740673
without a patch just to express my great laziness :p
well, I'm afraid nobody in the debian-boot team will attempt
anything at this
is it reproducible on linux?
nope
my guess is that's due to udev, need a deeper check btw
i mean non-udev cases like hurd maybe are not handled well
maybe try on kfreebsd then?
just guessing
* gg0 trying on kfreebsd
## IRC, OFTC, #debian-hurd, 2014-03-04
hurd install started getting stuck running os-prober, final grub
install phase
youpi: yes i confirm it affects kfreebsd too
then please say so in the bug
otherwise most probably but me in the debian-boot team will care
+nobody
that might get more attention from d-boot team?
ok
also Cc debian-bsd@
they will care
and tell about the hint as being the non-udev case
too much information or ideas is never a bad thing :)
done
(now i know notfound does remove found versions instead of adding
notfound versions)
crazy things. to unblock os-prober i had to settrans -fg
/target/media/./cdrom0
it was mounting /dev/hd0s1 ...
i suspect apt-cdrom is to blame again
ok now jenkins just managed to start the installed system
and it's configured to make vncdo testing it
i'd need a graphical-working cd with old-apt to continue
let's try to install old apt on weekly-0
"cdrom drive contains a cd which cannot be used for installation"
i think a sort of non-authenticated anymore
ehm.. http://paste.debian.net/plain/85224/
gg0: nice. :)
with apt 0.9.15.1 which should be good
pere: it did mount /dev/hd0s1 under /media/cdrom0
0.9.15.5, correctly i think, asks to insert it cdrom. but finally
both mount /dev/hd0s1 instead of /dev/hd2
-it
cause they both can't detect where cdrom is i guess
## IRC, freenode, #hurd, 2014-03-04
we could talk about apt-cdrom https://bugs.debian.org/740673
how should system recognize cdrom device?
there's no /dev/cdrom link to actual cdrom device
/dev/cd[01] are scsi devices if i'm not wrong
## IRC, OFTC, #debian-hurd, 2014-03-05
installer gets stuck running os-prober, seems because
/target/proc/mounts gets unreadable, sometimes Resource lost sometimes it
gets stuck reading it
[[hurd/translator/mtab/discussion#chroot]].
youpi: could you publish script to rebuild CDs you scheduled? with
last official CD (20140212) mtab on /target dies and that seems getting
os-prober stuck. last (and only) weekly has recent apt-cdrom so it gets
stuck wrongly asking to change cdrom
see the readme file
err, you say it's the 0212 build which fails?
I had tested that before uploading
so the issue comes form the installed packages, not from the CD
udebs
did you test with no network mirror?
no i didn't. should it find all packages it needs from cd?
sure, that's what netinst and dvd-1 are, as opposed to netboot
lxde desktop probably not
indeed
though with the dvd in principle it should
(if all deps were avaijlable at image build time)
gg0: btw if you haven't noticed, there's a daily too
youpi: till apt-cdrom is not fixed, they all will be broken, stuck at
"Scanning cdrom"
gg0: did you try to bisect which git change produces the apt-cdrom
bug?
youpi: all in bug in question
youpi: https://bugs.debian.org/740673
is there the precise git commit id in the bug log?