/srv/irclogs.ubuntu.com/2007/11/27/#ubuntu-installer.txt

mshadlesure enough, uninstall debconf and reinstall and im fine03:01
mshadleso something with di-tools, systemimager, or something else corrupted my debconf when i removed it03:06
=== mpt_ is now known as mpt
cjwatsonevand: 320 is probably actually closer, but we wanted to be conservative in a few places and said 38409:34
tjaaltoncjwatson: did you discuss console-setup with gravity at FOSSCamp?10:38
tjaaltonand if, what was the outcome10:38
tjaalton+so10:38
cjwatsonerm, what about it?10:40
cjwatsonwe did talk a bit, though I forget the exact details; if you remind me which bit you care about, I may remember ...10:40
tjaaltonwell, our xkb layout configuration depends on it10:41
tjaaltonbut debian uses something different10:41
cjwatsonDebian will be moving to console-setup in time10:41
tjaaltonoh10:41
cjwatsonand our XKB layout configuration does not depend on console-setup10:41
cjwatsonit's the other way round10:41
cjwatsonwell, though it does fish its initial value out of what console-setup did in the installer, true10:42
tjaaltonyes10:42
tjaaltonI just did some thinking about how to get the values for hal10:42
tjaaltonand how to keep them in sync10:42
cjwatsonhttp://wiki.debian.org/DebianInstaller/ConsoleSetupSwitch10:43
tjaaltonoh10:43
tjaaltongoal for lenny, sweet10:43
cjwatsonI think in practice sorting out console-setup layout/variant names i18n is the hardest problem10:45
cjwatsonbryce said he'd help out with that for hardy10:45
cjwatsonanyway, do go on regarding hal?10:45
tjaaltonright.. so AIUI it was decided that hal should ship a script that maintains the fdi-file10:46
tjaaltonor do it in config/postinst10:47
tjaaltonbut that would mean running dpkg-reconfigure when doing a change10:47
tjaaltonso I was thinking, if console-setup is the "master" place to store the data (I can't think of a situation where you'd have different layout on the console), there could be a "update-kbdlayout" or similar that would update the fdi10:50
tjaaltonconsole-setup seems to store the information in debconf10:51
cjwatsondebconf should never be the canonical place to store anything10:52
cjwatsonconsole-setup stores it in /etc/default/console-setup10:52
cjwatsonagreed that there needs to be a simple command to change it10:52
cjwatsonediting XML by hand is not good10:52
tjaaltonyes, I know that "debconf should not be a database" :)10:52
cjwatsonI don't think either console-setup or X needs to be the "master", if it's being kept in hal ...?10:52
cjwatsonbut it doesn't hugely matter, I guess10:53
tjaaltonwell, console-setup doesn't need hal, although they are both installed on every system..10:53
cjwatsonyes, that could be a sticking point in Debian10:54
cjwatsonit would mean committing to having hal in the base system10:54
cjwatsonfor that matter, I don't think hal is part of Ubuntu's base system10:54
cjwatsonit's priority optional10:54
tjaaltonso it seems..10:55
tjaaltonhmm10:55
cjwatsonright now, it's part of desktop10:55
cjwatsonserver installs don't have it10:55
cjwatsoncould hal fish it out of a non-fdi file?10:55
tjaaltonyep, didn't bother to check :)10:55
cjwatsonlike /etc/default/console-setup?10:55
tjaaltonit could10:56
cjwatsonI think that might be better10:56
cjwatsonif it fetched it dynamically at run-time10:56
cjwatsonthe console setup is the sort of thing you need to edit with very few tools, and having it as a simple text file seems like a win10:56
cjwatsonhaving it in hal (the protocol) seems more important than having it in hal's native file format10:57
tjaaltonhow to do that in runtime?10:57
cjwatsonnot my problem10:58
cjwatson;-)10:58
tjaaltonhaha10:58
cjwatsonhal has plenty of scripts that it calls to figure stuff out10:58
cjwatsone.g. for power management10:58
cjwatsonI'm not saying it's trivial but it ought to be possible10:58
tjaaltonso you mean it's better to have the information only in one place (on disk) and read that on fly?10:58
cjwatsonit feels better10:59
tjaaltonsounds more consistent10:59
tjaaltonfor us it's simple to rely on console-setup, and then Debian can add code to get the information from current xorg.conf or whatever11:00
tjaaltonuntil they use console-setup11:00
cjwatsonor migrate it from xorg.conf once-only into an fdi file if they prefer11:01
tjaaltonyeah, that could be done in some postinst11:01
cjwatsonso what will the gnome keyboard layout thing do?11:02
cjwatsonpresumably it can't set the value in hal, since it's per-user not system-wide11:02
tjaaltonright11:02
cjwatsonI guess it just carries on doing what it's doing now11:02
tjaaltonit should let the user change the layout if he needs to11:02
tjaaltonbut, there are bugs11:02
tjaaltonat least now that the default is us. If I add fi to the list, I can't make it default (on my session) until I remove us11:03
cjwatsonugh11:03
tjaaltonthen if I plug in another keyboard, it uses us, and the moment I type with it the whole session uses "us"11:03
tjaalton:P11:04
tjaaltoncorner cases, but still11:04
tjaaltonhmm, /usr/lib/hal/scripts has stuff that should help11:06
tjaalton..figuring out how to do it11:06
tjaaltonoh, just echo the values.. cool11:07
tjaaltondead simple :)11:07
tjaaltonhow the hell no-one thought of this before11:07
tjaaltonnow something completely different: has it been discussed if we could use 'relatime' mount option by default?11:09
tjaaltonFedora8 does that11:09
tjaaltoncurrently even every read from the cache forces a write to the disk11:10
cjwatsonyes, it has11:11
cjwatsonpartman now (hardy) supports relatime, but doesn't yet support the concept of default mount options11:11
cjwatsonso that needs to be added first11:12
tjaaltoncool11:12
cjwatsonbut I think it would be a good plan11:12
tjaaltonthere is a spec about noatime, but relatime is better11:12
tjaaltonsince some apps have problems with noatime11:12
tjaaltonhttps://blueprints.edge.launchpad.net/ubuntu/+spec/noatime11:12
tjaaltonhmm, it would be nice to see directly when a spec has been created11:13
cjwatsonsigh @ spec proliferation11:14
tjaaltonyeah..11:14
tjaaltonshould I draft a spec about it, and then later mark the noauto-spec as superceded?11:19
tjaaltonhog11:20
tjaaltonuh11:20
tjaalton"oh"11:20
tjaaltoncjwatson: didn't notice your comment that a spec is not necessary :)11:20
cjwatsonit's yet another case where a simple bug would be perfectly fine11:21
twbcjwatson: is partman-auto/purge_lvm_from_device supposed to work under gutsy's d-i?12:36
twbI get "Volume group name already in use".12:36
cjwatsonsorry, I don't know offhand12:37
twbAFAICT I can't make an automated lvm-using install idempotent.12:37
twbI got that entry from the Sid install guide, so it may not be applicable to gutsy.12:37
cjwatsonI don't know why it wouldn't work12:37
cjwatsonit's there12:37
twbHmm.12:38
cjwatsonperhaps some stupid device name difference12:38
twbI'm also using oem-config, if that makes a different.12:38
twb*difference12:38
cjwatsonno12:38
twbI don't know how to analyse the problem.12:39
twbOh, this VM isn't using DEBCONF_DEBUG, lemme reboot12:40
cjwatsonevand: did you get my mail about clock-setup?14:44
cjwatsonin reply to your merge requests14:44
evandindeed, I'm working on it as we speak14:44
cjwatsonok, thanks14:45
cjwatsonlocalechooser done, console-setup imported into bzr and nearly done, hw-detect imported into bzr and done, elilo-installer synced14:46
evandawesome14:47
evandwas ntp previously handled by a different component?14:47
cjwatsonit wasn't done at all14:54
evandah, that clears things up, thanks14:55
sorenJust FYI: mathiaz has done the ntp merge, I just need to review it.15:05
=== cjwatson_ is now known as cjwatson
cjwatsonconsole-setup uploaded, os-prober synced15:21
CIA-4oem-config: cjwatson * r383 oem-config/ (7 files in 2 dirs): * Convert to python-central.15:22
CIA-4oem-config: cjwatson * r384 oem-config/ (debian/changelog scripts/localechooser-apply):15:24
CIA-4oem-config: * Adjust for localechooser 1.39:15:24
CIA-4oem-config:  - Don'\''t edit /etc/environment unless it already contains LANG or15:24
CIA-4oem-config:  LANGUAGE settings.15:24
CIA-4oem-config: cjwatson * r385 oem-config/ (debian/changelog lib/components/language.py):15:25
CIA-4oem-config: * Adjust for localechooser 1.40:15:25
CIA-4oem-config:  - Cope with localechooser asking countrychooser/country-name rather than15:25
CIA-4oem-config:  countrychooser/shortlist.15:25
CIA-4ubiquity: cjwatson * r2360 ubiquity/ (debian/changelog ubiquity/components/language.py):15:25
CIA-4ubiquity: * Adjust for localechooser 1.40:15:25
CIA-4ubiquity:  - Cope with localechooser asking countrychooser/country-name rather than15:25
CIA-4ubiquity:  countrychooser/shortlist.15:25
CIA-4ubiquity: cjwatson * r2361 ubiquity/ (debian/changelog scripts/install.py):15:28
CIA-4ubiquity: * Remove the pregenerated snakeoil certificate and reconfigure ssl-cert so15:28
CIA-4ubiquity:  that each system gets a unique snakeoil certificate.15:28
cjwatsonevand: I think we should skip apt-setup for alpha 1; it requires new apt, new pkgsel, and new di-utils15:32
cjwatsonwhich is all kind of a pain to get in place by Thursday15:32
evandindeed15:33
twbWhat happens on Thursday?15:34
evandcjwatson: http://people.ubuntu.com/~evand/upload/clock-setup_0.92ubuntu1.dsc15:34
evandhttp://people.ubuntu.com/~evand/bzr/clock-setup/15:34
evandthat should address the issues you raised15:34
evandI looked over it a few times just to be sure, but you might want to review it one more time, just in case15:34
cjwatsontwb: alpha 1 planned to be released then15:35
cjwatsonevand: thanks, looking15:36
cjwatsonevand: could you please merge my changes? bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/clock-setup/ubuntu/15:36
cjwatsonerr15:36
cjwatsonI didn't make any changes there; did you throw away and start over?15:37
evandindeed, it seemed cleaner to do it that way.  Should I not have?15:37
cjwatsonplease don't in future, it's confusing15:37
evandI figured you hadn't merged from me15:37
evandok15:37
evandsorry about that15:37
cjwatsonhmm, I wonder what LP will do if I uncommit15:38
* cjwatson goes to look that up15:38
evandprobably explode15:38
cjwatsonI don't think so, it does branch.pull(self._source_branch, overwrite=True)15:39
cjwatsonso I'll just uncommit back to 0.16ubuntu1 and pull again15:39
cjwatsongenerally not good to uncommit on a published branch though, but in this case I guess it's the easiest recovery path15:40
evandok15:40
cjwatsonevand: this time you seem to have dropped the UTC question *and* its changelog entry15:41
cjwatsonI sort of meant to keep the question instead15:41
cjwatson(due to bug 28961)15:41
* evand checks15:42
evandah, I misread and thought that they had merged that bit15:49
evandthough on further inspection, no, they have not15:49
evandfixing now15:49
cjwatsonthanks15:51
evandok, pushed15:53
* evand crosses fingers15:56
cjwatsonlooks good16:34
evandgreat.  Shall I move on to base-installer, or are you already working on that?16:35
cjwatsonI am not16:35
evandok16:36
cjwatsonclock-setup uploaded, thanks, sorry for the long back-and-forth :)16:36
cjwatsonI'm working on the rather epic task of importing debian-installer's history into bzr16:36
evandsorry for messing it up three times :)16:36
evandyikes16:37
cjwatsontook a while to find all the tarballs I had from warty ...16:37
cjwatsonI want to have the aid of bzr for the merge though16:37
evandhaha16:37
cjwatsonurgh, bzr-svn doesn't seem to have done the right thing with $Id$ expansions16:39
cjwatsonhttps://blueprints.launchpad.net/bzr/+spec/bzr-keyword-expansion, sigh, guess I'll just ignore those conflicts16:41
cjwatsonmaybe I should use tailor instead ...16:42
twbI wouldn't trust tailor for more than a one-off migration of data from one SCM to another16:57
cjwatsonI've used it before with moderate success, and in this case I have already tried everything else that I know to be available17:00
cjwatsonplus I have some checks and balances available to me on an ongoing basis, so I'm not worried17:00
cjwatsonthat said, tailor isn't working for me either at the moment17:01
twbYou've used it successfully for two-way bzr svn interaction?17:01
cjwatsonI don't need two-way17:01
twbOh, OK17:01
cjwatsonI'm just working around the fact that a cscvs bug means that Launchpad can't import this particular Subversion repository into bzr as yet17:02
cjwatsonlooks like I'm stuck with bzr-svn's bugs though17:04
evandcjwatson: http://people.ubuntu.com/~evand/bzr/base-installer/ and http://people.ubuntu.com/~evand/upload/base-installer_1.85ubuntu1.dsc21:01
evandNot entirely sure if I did kernel/tests/sparc/niagara-t1-* correctly.  I was going to bump the kernel version, but linux-image-2.6.22-14-sparc64 doesn't exist according to p.u.c.21:01
knowmadHi, is this an appropriate channel for discussing usplash customization issues?21:03
evandknowmad: #ubuntu-devel might be more appropriate.  My usplash knowledge is somewhat limited.21:04
knowmadevand: thanks! i'm being challenged by it at the moment myself.21:05
cjwatsonevand: ok, I'll look tomorrow morning21:22
cjwatsonthanks21:22
cjwatsonthe kernel versions in tests aren't too important21:22
=== ebel_ is now known as ebel
evandah, thanks21:35
=== mpt_ is now known as mpt
=== ebel_ is now known as ebel

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!