/srv/irclogs.ubuntu.com/2009/05/14/#ubuntu-devel.txt

=== rickspencer3 is now known as rickspencer3-afk
=== savvas_ is now known as savvas
dholbachgood morning06:41
pittiGood morning07:03
pittiLordKow: try enabling UXA and KMS :)07:04
StevenKHey pitti!07:11
tjaaltonpitti: well, FUSA isn't working properly here :)07:15
pittitjaalton: at least something! :-) what's wrong with it?07:15
tjaaltonit doesn't present the options to shutdown/suspend etc07:15
tjaaltonthose work from the gdm login screen07:16
pittiinteresting07:16
=== herb__ is now known as herb
tjaaltonalso, seems like FUSA is making Xorg eat the cpu07:16
tjaaltonsince removing it from the session and logging back in makes that go away07:16
AmaranthKMS = 100% brightness :/07:24
=== tkamppeter_ is now known as tkamppeter
MmikeNekudWhat is the difference between Xserver and Xorg? I believed that Ubuntu 9.04 uses Xorg 7.4, now I'm reading it's using Xserver 1.6. What is Xserver 1.6?08:55
highvoltageXorg is an x server08:57
highvoltagexfree86 is another one, now mostly obsolete08:57
MmikeNekudhighvoltage, i know about xfree86, but, that's in version 4.something.... I have no idea what is Xserver 1.609:00
MmikeNekudi tought that xserver is 'type' of sofware... xorg is xserver ,xfree is xserver.... (much like mysql is rdbms, postgres is rdbms)09:00
cjwatsonMmikeNekud: "Xserver" is a name for a particular (important) component released by the X.org Foundation (actually, they normally call it xorg-server but both names are in use colloquially); see e.g. http://www.x.org/wiki/Releases/7.409:09
cjwatsonMmikeNekud: the name "X.org" or "Xorg" is sometimes used to refer to the whole suite of software released as various modules by the X.org Foundation09:10
MmikeNekudcjwatson, so, xserrver 1.6 is one of the xorg 7.4 components?09:10
macocjwatson, is it that xserver means a spec to which xorg and xfree86 conform?09:11
macosince xorg replaces xfree86 as the default xserver in a lot of distros09:11
cjwatsonMmikeNekud: actually, no, X11R7.4 included xorg-server 1.5.1 (as you would see if you'd gone to the wiki page I quoted above); Ubuntu 7.04 went a bit ahead of X11R7.4 for the server09:17
cjwatsonmaco: err, "spec" is putting it a bit strongly. Obviously both XFree86 and X.org need to include an X server or they'd be a bit pointless.09:17
macocjwatson, is there some sort of API or something?09:18
cjwatsonthere's a wire protocol, yes09:18
cjwatsonXFree86 was monolithic - the server wasn't released separately, X was just one giant lump09:18
seb128StevenK: hey, will you do syncs today?09:19
MmikeNekudcjwatson, yes, i see that now.... Ok, thnx, you clarified quite a bit for me here.... :) I'm trying to set up my friends laptop, he has FireGL 5200, and that one doesn't seem to be working with ubuntu :(09:19
cjwatsonso it's only with X.org that the server has started having independent versioning09:19
StevenKseb128: I was thinking about it :-P09:19
seb128StevenK: that would be nice, would clean the sponsoring and merge lists ;-)09:20
directhexsplitting xorg from one big fatty fat fat into actually distinct parts was one of the headline items that differentiated xorg 7.0 from xorg 6.9's xfree86-like build system09:20
StevenKAnd it moved to autofoo09:21
directhexeveryone loves autofoo09:22
directhexit's like cotton candy for the soul09:23
Chipzzcjwatson: I was reading yesterdays backlog, and I wonder what mksquashfs -sort actually does/how it works09:29
Chipzzdo you keep a list of filenames or block numbers?09:30
cjwatsonpitti: how do I stop the retracer from marking installer bugs as duplicates of bug 260001 when they aren't? they just happen to have the same backtrace because the backtrace isn't detailed enough. Can I change the bug description to stop it doing that?09:34
ubottuLaunchpad bug 260001 in ubiquity "ubiquity crashed with InstallStepError in configure_bootloader()" [Undecided,New] https://launchpad.net/bugs/26000109:34
cjwatsonChipzz: actually currently we give an empty file to mksquashfs -sort while building our live CDs :-)09:34
cjwatson(which is largely by accident, but)09:34
Chipzzcjwatson: but that doesn't actually explain what that option does :)09:35
cjwatsonChipzz: read the source, you know as much as I09:35
cjwatsonor the manual page09:35
ChipzzI was just going to say, I'm too lazy to install a package just for reading the man-page ;)09:36
Chipzzbut anyway09:36
Chipzzwhat I was thinking09:36
Chipzzwould something along these lines help for ext3:09:36
Chipzzfind /temporary/path | sort | cpio -pumdv /path/to/loop/ext309:37
Chipzzwhich would copy the files to the ext3 images in some sort of sorted fashion09:37
pitticjwatson: I could delete that one from the dup db, but the next time such a report comes in, it would be auto-dup'ed again09:38
Chipzzalso, something you may want to consider may be fragmentation of the image - in which case ext4 extents could help?09:38
pitticjwatson: I can do a quick cowboy-hack to not dup to 260001, if that helps09:39
pitticjwatson: fixing that properly will require some deeper thinking09:39
Chipzzcjwatson: anyway, just some idle braindumps I got when reading that backlog; you probably thought of those already, but just trying to contribute some ideas ;)09:40
cjwatsonpitti: would changing the bug description make any difference, or does it look at the original description or some cache?09:44
pitticjwatson: no, just bug numbers and stack traces09:44
cjwatsonChipzz: we used to do that sort of thing but it was hopelessly awkward to maintain and we don't want to go back to it09:44
pittiand package names09:44
cjwatsonpitti: ah. In that case, yes, I'd appreciate it if you could blacklist 260001 from auto-duplication09:45
cjwatsonthe traceback just says "installing the bootloader failed for some reason"09:45
pitticjwatson: done09:46
cjwatsonthanks!09:46
cjwatson(oh god, now I'm going to have to go through the 66 dups - oh well)09:47
pitticjwatson: well, untested, but worst that can happen is that it crashes now, and then I'll fix it09:47
pitticjwatson: sorry09:47
pitticjwatson: but I guess without auto-duplication you also had to go through them09:47
cjwatsonyeah09:48
cjwatsonnot your fault :)09:48
directhexhm. it seems i still suck at Closes:09:49
lifelesscjwatson: the installer again?09:53
cjwatsonlifeless: ?09:55
lifelesscjwatson: bug duplication detection [human and bot]09:57
lifelesscjwatson: we have similar issues in bzr where users think things are the same, that aren't, fairly regularly09:57
cjwatsonlifeless: in this case it's essentially because the traceback is too general09:58
cjwatsonI can't really blame them, you have to look into the syslog to stell09:58
cjwatsontell09:58
lifelessI wonder if we could hack the backtrace to be more useful09:58
cjwatsonclearly, but not retrospectively for old versions of the installer burned onto physical media09:59
lifelessof course :)09:59
cjwatsonthough it does irritate me when users deliberately report duplicates of their own bugs - but not much to be done about that10:00
seb128slangasek: hi, you know about samba and pam, could you have a look to bug #375569 and reassign where it would make sense?10:03
ubottuLaunchpad bug 375569 in gnome-screensaver "gnome-screensaver failure - can't access samba password database - not running as root " [Undecided,New] https://launchpad.net/bugs/37556910:03
=== Tonio__ is now known as Tonio_
pittiTheMuso: is anyone testing the ubuntustudio alpha-1 images?10:06
pittiseb128: FYI, slangasek is on holiday this week10:06
seb128pitti: oh right ;-)10:07
slangasekpitti, seb128: doesn't mean I'm not queuing it, though :)10:07
seb128slangasek: thanks10:08
slangasekprobably a not-a-bug, in any case10:08
pittislangasek: hush, back to gardening! :-)10:09
pittioh well, would ba fairly dark outside, I figure10:09
slangasekyeah, it rained all day today too :P10:09
ogragood gardeners can mow their lawn in the dark !10:09
slangasekI don't claim to be a good gardener10:09
slangasek:)10:09
pittiogra: to the great amusement of their neighbours10:09
ograyeah10:09
ogramine use to start around six on a good day :/10:10
ogra(AM)10:10
=== korn_ is now known as c_korn
smbcjwatson, Ok, so the thing for the kernel package post-installation would be to only claim /vmlinux if the version is more recent that the current. So this relates to the kernel with the higest version number and not to the one which happened to be installed last10:54
cjwatsonsmb: it's not especially clear to me what should happen if you previously had 2.6.28-6-386 installed and then install 2.6.28-11-generic10:55
smbRight, that was the reason that lead me to that timestamp idea. From purely looking at the installation viewpoint I deducted -u should always update all initrds that have been touched during that round of installation.10:57
cjwatsonno, that isn't true10:58
apwwhat is the criteria for a rebuild10:58
cjwatsonupdate-initramfs -u means "update the most current initramfs", which may be because one of the userspace packages that form part of the initramfs has been updated, not just because the kernel has been updated10:58
cjwatsonapw: what sort of rebuild?10:59
apwsorry for an initramfs rebuilt, it seems that update-initramfs -u is run whenever any possible contents are change10:59
apwi presume we don't rebuild all kernels as that could break your old ones11:00
smbAnd the whole problem arises because when the kernel installation itself builds an initrd, udev was somehow in an inconsistent state, so all builds done between that are broken and when udev finally gets into the correctly configured state, it will only update the mos recently build initrd11:01
smbapw, that would be my thinking11:01
apwcjwatson, how do the delayed triggers work for other things11:02
persiaThere's several factors involved though.11:02
apwit almost sounds like we should rebuild kernels at the end of things11:02
apwrebuild _initrds_ at the end11:02
persiaIf I install something *other* than a kernel that affects initramfs, I'd expect I'd want all my initramfs's updated.11:02
cjwatsonapw: please see the docs for dpkg triggers11:02
cjwatsonit's a lot quicker than me reciting them11:02
apwpersia, should that update be broken though then we would break _all_ your kernels, bad11:02
apwcjwatson, thanks for the pointer11:03
cjwatsonpersia: we've always said that we should only update the most current one, in order to increase the likelihood of having something older you can boot into if things go wrong11:03
cjwatsonI have no interest in changing that11:03
smbpersia, But in theory you could have a shared /boot and have older kernels there. Which you do not want to touch11:03
cjwatsonbut I do think we should update the most current one *for each kernel flavour*11:03
apwcjwatson, i think that is very reasonable to do11:03
persiacjwatson, Hrm.  I was unaware of that, but it does explain some behaviour I encountered in the past.11:04
* apw thinks he has a box with that situation11:04
smbapw, So we have to make sure update-initramfs can get the most recent kernel version11:05
cjwatsonapw: largely we do build initramfses at the end, but not for the kernel - there's no way to pass data to triggers, so the trigger can only say "update most current initramfses"11:05
cjwatsonlook, I can fix the update-initramfs thing11:05
cjwatsonI know exactly what the problem is there11:05
cjwatsonwhat I don't know is how to deal with the *other* problem Steve identified11:05
smbcjwatson, Ok, and I fix up the other thing11:05
cjwatsonthe kernel postinst unconditionally claims the /vmlinuz symlink11:06
=== Tonio__ is now known as Tonio_
cjwatsonsmb: how? it's not at all clear what the correct semantics are11:06
apwwhat does the vmlinuz link officially even mean11:06
cjwatsonit's the default thing you boot into11:06
smbcjwatson, Ok, to me it sounded as that link always is set to the most recently *installed* kernel11:07
cjwatsonsmb: it is, right now; it is not clear that this is correct11:07
apwdoes anything use it at all?11:07
cjwatsonapw: update-grub11:07
smbcjwatson, You actually boot into the kernel defined in grub. I don't think /vmlinz has any meaning to that11:07
cjwatsonsmb: update-grub is smarter than you think it is11:07
cjwatsonor at any rate is supposed to be :-)11:08
smbcjwatson, Maybe smarter than I fear it is .:)11:08
cjwatsonalso there are still people using lilo for various reasons and I'm pretty certain that lilo.conf refers to /vmlinuz11:08
smbcjwatson, So that is the "saved" magic?11:08
cjwatson(legitimate reasons; the installer still defaults to lilo in some circumstances)11:08
apwso our behaviour currently is to say that the latest kernel is your default kerenl11:08
smbapw, If I parse unconditionally claiming correctly it set the link whenever you install a kernel... But maybe not...11:09
cjwatsonwell, how about looking at it this way for something that's *obviously* wrong11:10
cjwatsonlet's say you have both 2.6.28-10-generic and 2.6.28-11-generic installed, and for whatever reason (let's say filesystem corruption) you decide to reinstall the 2.6.28-10-generic package11:11
cjwatsonright now, it's my belief that doing that will change /vmlinuz to point to 2.6.28-10-generic when it was previously 2.6.28-11-generic11:11
cjwatsoncan we agree that this is wrong?11:11
smbcjwatson, I would agree11:12
apwif the user has no other way to change the default, that might be a reasonable way to say i want this one to be the default11:12
cjwatsonthey have other ways11:12
apwif they have a way to select it is wrong11:12
apwso we should only update the link if the kernel is 'newer' in some sense11:12
cjwatsonnow, what should happen if they have 2.6.28-6-386 installed and then install 2.6.28-11-generic?11:12
cjwatsonthose ABI versions aren't comparable11:12
cjwatsonand, while we generally prefer -generic, the user might have a reason to use -38611:13
cjwatson(substitute -server if you prefer)11:13
apwi would tend to say stay at the latest of the current flavour11:13
apwand if the users wants to change they can use the changer11:13
cjwatsonlet's say that they have both the linux-386 and the linux-generic metapackages installed, so if they keep upgrading, right now the link flip-flops over time11:13
cjwatsonI think I agree, mostly, that it should stay pinned to a flavour, with one exception11:14
smbRight, so the post install would have to look at the current current flavour adn only update if newer.11:14
apwfor that reason i think we should only move the link to a later version of the current flavor11:14
cjwatsonif you *remove* a kernel, it needs to switch that link to a different flavour if there are none left of the current flavour11:14
cjwatsonbut really the exact rules need to be written down in policy style11:15
apwcjwatson, good point ... and yes we should document them somewhere11:15
apwsmb, you gonna do that.  cjwatson do we have a place for that kind of thing?11:15
apwif not we should make a KernelTeam/Policy thing and put it there11:16
cjwatsona big comment in the postinst would be fine, or a wiki page11:16
cjwatsonprobably ought to be commented in the postinst anyway11:16
smbProbably remove would dec the abi version as long as there is one with the same flavour and go to generic or anything left if not11:16
pittican anyone please test the current Kubuntu alternates? it becomes urgent now11:16
apwstay in flavour if at all possible11:16
smbapw, Maybe we get togehter later to think of that11:16
cjwatsonI don't think I'd mind it being essentially random if you remove a kernel, as long as it says on stdout what it's doing11:17
apwsmb, sure.  i think the rules are pretty sensible and implementing them sounds relativly straight forward11:17
apwi think some awk magic can work it out11:17
smbapw, Yes, I think the hardest part is to think of all the cases11:17
smband what should be the sensible approch there11:18
smbpitti, I could do a bit but only start in around an hour?11:18
smbpitti, something special to have tested?11:18
pittismb: just whether they install in general11:19
pittismb: the previous 5 didn't11:19
pittismb: if you can get through a standard "entire disk" VM install and can login and get a desktop, that's enough11:19
smbpitti, ok, so kubuntu alternate in general or 64 or 32 specifically11:19
pittismb: we need to test both11:19
smbpitti, Ok, let me start getting the immages11:20
smbpitti, rsyncing, I'l do the installs when I am back11:22
pittismb: thanks11:23
cjwatsonsmb,apw: If you haven't already, I'd recommend familiarising yourself with the chapter of the Ubuntu policy manual that describes the valid state transitions for packages11:25
apwcjwatson, ok thanks11:25
cjwatsonsmb,apw: it's something like "how maintainer scripts are called"11:25
smbcjwatson, Good idea. Thanks11:25
persiahttp://women.debian.org/wiki/English/MaintainerScripts has some nice graphs for the simpler cases.11:27
TheMusopitti: I tried testing them today but the RT kernel we are using + new karmic bits + desktop are all a little wacked out, so since nobody else has done anything at this point, I am enclined to say that we'll skip alpha 1.11:39
pittiTheMuso: okay, understood11:39
pittiogra: did anyone test the edubuntu addon alpha-1 CDs?11:40
ograpitti, no idea12:00
ograpitti, i havent touched edubuntu since hardy12:00
pittiogra: want me to release edubuntu alpha-1 CDs?12:00
pittioh, who is the primary contact nowadays?12:00
ograLaserJock is the last guy taking care from a technical side12:01
ograprobably highvoltage too12:01
pittihighvoltage: did you happen to test the edubuntu alpha-1 addons?12:01
ograi guess if nobody tested it wont do harm to skip A112:02
pitti*nod*12:03
=== fta_ is now known as fta
ftadoko, hi, any plan to add binutils-gold to karmic?12:46
dokofta: yes, should be reenabled12:47
* ogra thought thats still experimental12:48
dokothat's why we remove it before the releases12:49
ograah12:49
ftaok, thanks12:49
ftai want to start experimenting with it on some big packages12:50
ogracjwatson, did you notice that upstream is two versions ahead wrt unionfs-fuse ?12:51
highvoltagepitti: I agree with ogra that it's probably safe to skip A1, but if it won't be too late I'll be happy to test it tonight12:56
cjwatsonogra: no, but not exactly top of my agenda right now12:56
dholbachPackaging Training session in #ubuntu-classroom now!13:00
cjwatsonogra: (don't get me wrong, thanks, just doing a lot of stuff right now)13:00
ogracjwatson, yeah, i just noticed there were two upstream releases, one of tehm with a cryptic message wrt com filesystems13:01
ogra0.2213:01
ogra- Fix a bug reported by Jens Hoelldampf <jens@hoelldampf.net>, in 0.21 cow13:01
ogra  didn't work for pathes.13:01
ogras/com/cow/13:02
cjwatsonogra: at the moment I think it might be easiest to identify the problem I can see right now, and make decisions based on that13:05
cjwatsonbut right now I'm looking through grub-installer bugs and worrying about my allhands talk, so ...13:06
ograyep, i just noted that there are a bunch of upstream commits in their mercurial that arent released and that we are two releases behind, i simply thought i'd give you a heads up about that fact no need for any action here :)13:07
smbpitti, Kubuntu alternate i386 installed. My favourite testcase (playing mp3 with amarok) fails. No codecs installation offered.13:08
Riddellsmb: thanks.  audio may well not work at all that's not unexpected13:16
smbRiddell, actually it makes sound. :)13:17
smbamd64 next13:17
Riddellsmb: when does it make sound?13:17
smbRiddell, Login and logout (just before jockey crashes on logout. heh)13:18
Riddellok, that's good13:20
PecisDarbshi people, is there any plans to replace or extend gnome-bluetooth functionality with blueman? It has integration with NM .7 so it is possible to use Bluebooth modems as mobile broandband connections13:20
=== keffie_jayx is now known as effie_jayx
pittismb: thanks; if you got this far, it's about as much as we can expect for a113:38
smbpitti, Yeah, its not too bad. amd64 is about to reboot after installation13:40
smbpitti, Riddell, Ok amd64: basic installation ok, too13:43
pittismb: cheers!13:43
Riddellsmb: mouse working?13:43
smbRiddell, yep13:43
Riddellbetter than I get :)13:43
smbRiddell, All "old" hw. Ps/2 mouse and keyboard13:43
directhexis there a formal way to request that someone not act like an arse by treating launchpad bugs like youtube comments?13:48
=== rickspencer3-afk is now known as rickspencer3
=== asac_ is now known as asac
=== Lure_ is now known as Lure
loolkirkland: Didn't try it out, but I see that /usr/bin/ecryptfs-setup-swap uses vol_id and it was dropped; you might have to move to blkid instead14:38
* lool goes filing a bug14:38
lool37648614:38
kirklandlool: ah, good catch, thanks.15:09
kirklandlool: any chance you can file a bug to keep that from getting lost?15:09
seb128kirkland: I think he did * lool goes filing a bug <lool> 37648615:09
diverse_izzue__i'm doing my first steps with packaging and am trying to cook up my own tracker 0.6.94 package, starting from the jaunty 0.6.93 package. turns out the patch 99_autotools.patch needs to be updated - how do I do that?15:09
seb128diverse_izzue__: you can move the patch out of the way, cdbs-edit-patch 99_autotools.patch; autoreconf; remove cache dir; exit15:09
loolkirkland: like seb128 said :)15:09
kirklandlool: seb128: gotcha, thanks!15:09
=== pitti changed the topic of #ubuntu-devel to: Archive: Open for development | Karmic alpha 1 released! | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-jaunty | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
pittivoila15:11
diverse_izzue__seb128: by "moving the patch out of the way" you mean delete the patch file and remove the according line from the file "series"?15:11
seb128oh, that's a quilt package?15:11
seb128diverse_izzue__: try #ubuntu-motu for packaging questions15:11
diverse_izzue__seb128: sorry, thanks.15:11
\shoh nice...I hope my new bl7000c equipment arrives in time to test karmic on it :)15:19
=== Tonio__ is now known as Tonio_
bddebiandoko: You around by any chance?  Do you know what is up with the Debian Java team?15:34
ScottKbddebian: persia or ttx would be good people to ask about that.  They just finished a team meeting in #uubntu-meeting.15:36
ScottKbddebian: Nevermind.  I misread which distro's team you asked about.15:36
bddebianScottK: Is Persia on an ubuntu-java team?15:37
persia(and the highlighted person is in #debian-java anyway)15:37
persiabddebian, Yes.  I run the meetings.15:37
bddebianNo one ever responds in #debian-java :)15:38
* hyperair would love to see eclipse updated.15:38
* bddebian would love to see Java removed.. ;-P15:39
* bddebian hides15:39
* hyperair brandishes a knife15:40
* ScottK reminds hyperair he has to clean up the mess after, so consider carefully.15:40
* persia points hyperair at https://blueprints.launchpad.net/ubuntu/+spec/foundations-karmic-eclipse-update15:40
dokobddebian: I'm not the nanny of debian-java ... so I just see what you seem to see.15:42
ScottKdoko: Is Python 2.6 coming to unstable anytime soon?15:42
dokopersia: hot air (or call it it hyperair)15:42
dokoScottK: wrong channel15:42
ScottKWell it would help us with pushing stuff back and getting syncs if the Python 2.6 bugs went from wishlist to RC15:42
bddebiandoko: I didn't mean to imply that you were I'm just trying to find a warm body that will respond. :)  Response from Arnaud was that he is too busy and Michael Koch seems MIA :(15:42
hyperairpah. hot air indeed15:42
hyperairlol15:42
dokosoon, but not real soon15:42
ScottKOK15:42
bddebiandoko: BTW, any chance of updating python2.4/2.5 libdb to 4.6 or 4.7?15:43
dokobddebian: yes, I couldn't contact Michael for some months15:43
hyperairpersia: i've seen that before. unfortunately, 5 minutes after staring at eclipse's packaging, i decided against trying my luck15:44
ScottKbddebian: I'm going to guess that comes with 2.615:44
dokobddebian: not really. will get rid of 2.4 hopefully soonish (ScottK: not real soonish)15:44
* ScottK did some fixing of Eclipse back in the Feisty timeframe (IIRC). Learned better.15:44
hyperairpersia: also the debian-java guys have 3.3 in svn last i checked. for some reason, it's sitting there rotting away without anyone to tend for it.15:44
mterryasac: How usable are the packages in the mozilla daily build team ppa?15:47
bddebianScottK: Sure but I'm trying to RM: any libdb < 4.615:47
bddebianhyperair: Most of the debian-java packages seem to be bitrotting :(15:47
hyperairbddebian: indeed. what happened to them? have they all died or something?15:49
hyperairthem meaning the members of that team15:49
asacmterry: in general they are very much usable15:50
bddebianI'm trying to find that out.  As I said Arnaud is busy and Michael Koch is missing, the rest, I have no idea.15:50
persiaThe set of people who are 1) active, 2) DD, and 3) have access to pkg-java SVN has become small.15:50
asacmterry: firefox-3.5 is mostly frozen upstream, so you only get baked patches there15:50
bddebianI'm tempted to NMU jamvm without jikes but I hate to do that15:50
asacmterry: i run firefox-3.6 trunk and even there i usually dont get issues - probably because all extensions are incompatible/disabled ;)15:50
mterryasac: Heh, OK.  Thanks15:50
hyperairasac: haven't you heard of nightly tester tools? =P15:50
asachyperair: heh. i am quite happy without extensions ;)15:50
bddebianpersia: So hurry up and get your DD and join the team.. ;-P15:50
* persia waffles harder15:50
bddebianheh15:50
rtgcjwatson: I added a section to https://wiki.ubuntu.com/KernelTeam/Specs/KarmicKernelFlavours regarding unsupported architectures. Feel free to add your thoughts.16:00
=== thunderstruck is now known as gnomefreak
davmor2bryce: I couldn't get an R500 chipset in the end :(  So I had to go with an R600 chipset instead.  I'm having massive issues with it in Karmic.  I'm assuming it is trying to use the highest setting of the card rather than the highest setting of the monitor if I set it to safe graphics it works round this but  the system seems to be working at double speed including the internal clock in 4 minutes it had done 7.  Other16:15
cjwatsonrtg: thanks16:18
rtgnp16:18
al-maisanhow do I figure out which component a package belongs to?16:23
ScottKal-maisan: rmadison packagename will tell you (if it doesn't specify it's in Main)16:23
al-maisanScottK: great, thanks!16:23
cjwatsonal-maisan: I believe it's also in the Soyuz UI ;-)16:26
al-maisancjwatson :)16:26
cjwatsonhttps://launchpad.net/ubuntu/karmic/+source/man-db "Component: main" for example16:27
cjwatsonor https://launchpad.net/ubuntu/karmic/+source/man-db/2.5.5-1build1 which is what you can get to from the main source-package page also shows that16:28
ScottKI don't think you can get binary specific component that way though.16:28
cjwatsonScottK: you can. e.g. https://launchpad.net/ubuntu/karmic/i386/linux-rt has a Component column16:28
al-maisancjwatson: thanks for the pointer but command line tools are typically much handier.16:28
cjwatsonit's just very cumbersome to find because the links aren't very good16:28
cjwatsonal-maisan: well, personally I couldn't agree more, just thought somebody used to Launchpad might prefer the web UI ;-)16:30
cjwatsonbut certainly I always use rmadison myself - unfortunately it doesn't handle ports yet16:30
cjwatsonI think we have all the pieces in the LP API necessary to write lpmadison now mind you ...16:30
al-maisanI am an "old dog", love the command line :)16:30
ScottKcjwatson: Thanks.  I didn't know about that one.16:30
NCommandercjwatson, when using ubuntu-cdimage, is there an easy way to replace the ubuntu-keyring package in main to include a new ubuntu-keyring package on the fly? (I tried putting one in the LOCALDEBS folder, and it ends up on the CD, but not in the dists)17:06
Unggnuhi all17:16
UnggnuIs LVM and cryptsetup support planned for the Karmic desktop installer?17:16
UnggnuFedora 11 has this already while I guess the changes couldn't be adapted so easily or are the installer projects compatible?17:17
Chipzzyou can use the alternate installer if you want LVM17:21
=== kenvandine1 is now known as kenvandine
UnggnuChipzz: it is even possible with the desktop if you install the lvm2 package but it is no real option imho17:38
UnggnuAt least LVM should be possible because it is becoming more and more important. Afaik the Alternate uses LVM per default.17:39
* pitti does an autosync run and gives the buildds something to do17:54
calcdoko: thanks for fixing ooo-l10n, I'm not sure what happened to break my merge :\18:00
asaccjwatson: doing a full archive rebuild on PPAs?18:15
asaci386      12969 builds waiting in queue18:15
asachttps://edge.launchpad.net/builders/18:15
asacor is that huge number a bug?18:15
ion_So many PPA builders, as opposed to official archive builders? I’d have expected the PPA load to be lower than the main archive load.18:18
Wrongdevicehello18:19
asacion_: archive builders is real hardware, while ppa builders are VM instances afaik18:19
ion_Ah18:19
WrongdeviceUbuntu 9.10 Alpha 1 was compiled with -fgraphite Cflag ???18:19
ilyast91hi18:24
ion_That was quick.18:25
Wrongdeviceso the silence means NO18:26
ion_If you say so.18:27
Wrongdevicebah18:42
cjwatsonNCommander: there's a local directory that should work, see bin/update-local-indices; haven't used it in production since pre-warty though so it might have bitrotted, but that would be the place to start19:05
cjwatsonasac: yes, testing out a new LP feature19:05
NCommandercjwatson, yeah, that's what I tried. The debs ended up on the CD, but not in the main Packages file, so debootstrap self-destructs since the normal keyring package goes MIA :-/19:06
=== rickspencer3 is now known as rickspencer3-afk
cjwatsonNCommander: right, certainly not claiming it works, just that you can probably debug it into existence from there ... it's where I'd start19:15
cjwatsonit may put things into dists/karmic/local/ or some such which might not work for debootstrap19:15
cjwatsonI honestly forget, it's been nearly five years :)19:15
NCommandercjwatson, well, its ... weird :-/19:15
NCommandercjwatson, I'll provide a branch for merging once I get it fixed; its handy for building unofficial images for ports :-)19:16
pittianyone with a ThinkPad or Sony Vaio or Asus laptop here?19:16
* ion_ 19:16
ion_Thinkpad T2319:16
NCommandercjwatson, Sony VAIO VGN-660N19:17
NCommanderer19:17
NCommanderpitti,19:17
pittiion_: does this show one device for you:19:17
pittiudevadm trigger --verbose --dry-run --subsystem-match=input --attr-match=name='ThinkPad Extra Buttons'19:17
pittiNCommander: does this show one device for you:19:17
pittiudevadm trigger --verbose --dry-run --subsystem-match=input --attr-match=name='Sony Vaio Keys'19:17
ion_pitti: It prints /sys/devices/virtual/input/input719:18
pittirunning as user should work19:18
pittiion_: cool; does this directory have a 'dev'?19:18
ion_pitti: capabilities  event7  id  modalias  name  phys  power  subsystem  uevent  uniq19:18
pittiion_: aha, I want the event7/ sub dir then, I guess19:19
mcasadevallpitti, /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3b/SNY6001:00/input/input519:19
mcasadevallpitti, the media keys on this laptop work on and off depending on the phase of the moon19:19
ion_pitti: Ah, it has the dev. dev  device  power  subsystem  uevent19:19
pittimcasadevall: I suppose that dir has an "event5" subdir, and that has a "dev"?19:20
mcasadevallpitti, huh?19:21
pittimcasadevall: ls /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3b/SNY6001:00/input/input5/event5/dev19:22
pittimcasadevall: does that exist?19:22
mcasadevallpitti, yes19:22
pittimcasadevall: cool, thanks19:22
pittiion_: thanks as well19:22
ion_np19:22
pittimcasadevall, ion_: do you get the same output with this unified command:19:22
pittiudevadm trigger --verbose --dry-run --subsystem-match=input --attr-match=name='*Extra Buttons|Sony Vaio Keys'19:22
* pitti tries to write a debugging tool to make debugging and fixing wrong keymaps much much easier19:23
ion_pitti: '*Extra Buttons|Sony Vaio Keys' doesn’t print anything, '*Extra Buttons' prints the path.19:24
mcasadevallpitti, no output19:24
mcasadevallpitti, that being said, I only have working brightness, no sound, but that might be because my sound setup is funny, or because I'm running Xfce :-)19:24
pittiok, need to check them separately then19:24
ion_pitti: If it’s a plain fnmatch(), | won’t work.19:24
pittiion_: | works in udev rules, but apparently not here19:24
ion_Ok19:25
pittimcasadevall, ion_: could you now please try to run http://people.ubuntu.com/~pitti/tmp/keymap-debug ?19:30
pittiion_: for you it should say "input/event7"19:30
pittimcasadevall: for you it should say "input/event5"19:30
NCommanderpitti, I got input/event3 back19:30
pittiand probably another one which is your real keyboard19:30
pittiNCommander: can you pastebin sh -ex output?19:31
mcasadevallpitti, http://paste.ubuntu.com/172528/19:32
ion_pitti: evdev=$m/input* fails, i.e. it seems to behave as if evdev="$m/input*". I’ll edit the script to make it work and post a revised version for you.19:32
pittiion_: already done and uploaded19:34
ion_Ok19:34
pittimcasadevall: please get the current one19:34
pittiah, crap19:34
pittiupdated again19:34
mcasadevallinput/event319:34
mcasadevalldevice path not found19:34
=== jjohansen is now known as jj_lunch
pittimcasadevall: right, please download again19:34
mcasadevallpitti, I did, same output19:36
pitti*sigh*19:36
pittiI need a sh -ex then, I'm afraid19:36
mcasadevallpitti, I just rmed the script by accident and now get a 40419:37
mcasadevallpitti, er, no wait, I fail19:37
ion_pitti: I’ll just do the necessary changes and post the script, as i have a system to test with. :-P19:37
pittiion_: thanks19:37
pittiion_: seems the `ls $m/input*` trick doesn't work, hmm19:38
mcasadevallpitti, http://paste.ubuntu.com/172531/19:38
pittiion_: it does work, was just error on my faking19:38
pittimcasadevall: ah, that's because I suck19:39
pittimcasadevall: updated and uploaded19:39
pittiI want event*, not input*19:39
pittiit works for me now19:40
ion_AT keyboard: input/event4 module: input/event7 module: input/event419:41
pittiion_: that sounds right19:41
Prettopeople, i need some help, i must install ubuntu from network t0 400 computers, but my client need that a custom theme must be applied and custom packages, is there a semple on how to do that just using preseed?19:42
Prettosample*19:42
pittiion_: for the second module I'm sure that I uploaded my "fake" match19:42
pittiion_: uploaded again, should be perfect now19:42
mcasadevallPici,19:43
mcasadevaller pitti19:43
mcasadevallAT keyboard: input/event319:43
mcasadevallmodule: input/event519:43
pittimcasadevall: splendid19:43
pittimcasadevall: thanks muchly19:43
pitti<rough voice>I know where your keyboard is! MUHAHAHAHA!19:44
mcasadevallpitti, now if you can solve my trackpad from randomly disconnecting19:45
ion_pitti: Yeah, AT keyboard: input/event4, module: input/event719:48
pittiion_: splendid, thanks19:48
pittimcasadevall: not from here :/19:49
superm1pitti, does my memory serve me right that you made a v4l-dvb dkmsified package at some point?19:49
pittisuperm1: yes, http://martinpitt.wordpress.com/2008/06/10/packaged-dvb-t-drivers-for-ubuntu-804/19:49
superm1pitti, awesome.  someone on ~mythbuntu might use it as a basis to do some weekly v4l-dvb builds19:50
pittiyay19:50
ion_pretto: I’d use an image of a plain Ubuntu installation with something like puppet or chef installed, and let that tool handle the rest of the customization/configuration.19:50
pittiI'd love to see that picked up by someone who maintains it19:50
superm1pitti, yeah it would still live on a PPA and what not when it was done, and hopefully low maintenance :)19:51
pittiok, TTFN; see you tomorrow!19:52
Prettoion_, but later i can install it using network install?19:52
ion_pretto: Using such a tool, you can later do any changes on any or all of the computers arbitrarily. The clients periodically pull configuration rules from a server.19:53
Prettoion_, the main problem is doing manual installation to 400 computers19:54
ion_Create a single filesystem image of a freshly installed system with such a client installed, and replicate the image to the computers.19:55
ion_But this is offtopic for this channel. :-)19:55
Prettoion_, where can i find further information about on how to do that ?19:57
mcasadevallpitti, I'll give you my laptop at UDS to fix ;-)19:57
rtgKarmic on an xps1330 appears to work until you try to start a shell. it appears and disappears very quickly. any ideas?20:06
ScottKType quickly?20:09
rtgScreally, really fast20:10
rtgScottK ^^20:10
rtggui apps seem to work OK20:10
ScottKrtg: Sorry.  Sarcasm is the only help I have to offer.20:12
rtgSCottK: s'alright. you get what you pay for :)20:13
persiartg, Can you start a shell with a different terminal emulator, or on console?20:14
rtgpersia: console works20:14
persiartg, Then try a different terminal emulator, or a different default shell.  One of those is likely buggy.20:14
rtgpersia: this is an upgrade from Jaunty. do you suppose I've some cruft in my .bashrc ?20:15
persiaPossibly.  You'd know better than I.20:15
rtgpersia: I'll futz around and see what I can figure out20:15
persiartg, Good luck :)20:16
rtgpersia: its not my primary laptop, so I've time.20:16
persiaMy experience with things that fail is that there's usually another app that works.20:16
persia(which helps to diagnose the bug)20:16
=== ttx is now known as ttx_
=== ttx_ is now known as ttx
jdstranddoko: hi! so I am doing the libpng merge and found this in the changelog: debian/rules: Work around missing definition of ECHO. I don't have a bug reference and google didn't help me. what is it for? the package builds fine without it on amd6421:26
jdstranddoko: nm, I found it in the upstream changes21:34
cjwatsonrtg: there might be a hint in .xsession-errors21:37
rtgcjwatson: its booting. I'll have a look21:37
cjwatsonrtg: failing that, I think I'd (carefully) strace -f the gnome-panel process and see what it's doing21:38
rtgcjwatson: no joy, also changed from 2d to 3d nvidia. how do I (carefully) strace -f the gnome-panel process?21:52
cjwatsonrtg: ps x | grep gnome-panel, find pid, strace -f -o gnome.panel.trace -s 1024 -p <pid>21:58
cjwatsonctrl-c the strace when you're done with it or else your desktop will probably run like a drain21:59
rtgcjwatson: nothing too interesting there. lots of process attach/detached22:00
=== azeem_ is now known as azeem
=== yofel_ is now known as yofel
Ampelbeinhi guys. is it safe to assume the following: if file /etc/inittab exists -> sysv-rc, directory /etc/event.d exists -> upstart ?23:10
ion_Nope. sysvrc scripts can and will be used even without sysvinit, and in a newer version of Upstart, /etc/event.d has been renamed as something else.23:11
geofftmy upstart has code to parse /etc/inittab23:12
Ampelbeinion_: thanks.23:12
ion_geofft: Probably not Upstart itself, but Upstart job(s).23:12
Ampelbeinthe point is that i want to make a package (daemontools-run in this case) working on sysv as well as on upstart.23:13
pace_t_zuluasac: you here?23:13
asacpace_t_zulu: kinda late ... whats up?23:25
pace_t_zuluasac: trying to build chromium following your instructions23:26
pace_t_zulunot working... will pastebin23:27
ion_pace: There’s a PPA with daily chromium builds.23:27
pace_t_zuluasac: http://pastebin.ubuntu.com/172643/23:28
pace_t_zuluion_: i am trying to build myself... i have the PPA set up already... thanks23:28
maxbpace_t_zulu: Taking a known working build as a starting point would still make sense, though, no?23:30
pace_t_zulumaxb: you mean apt-get source ?23:30
maxbWell, I mean getting the source from the chromium daily PPA.23:31
maxbI wouldn't add a source to sources.list just to run apt-get source23:31
Riddellwhere's the UDS timetable again?23:31
james_whttp://summit.ubuntu.com23:33
pace_t_zulumaxb: could you please provide a command to get a PPA source?23:33
Riddellthanks james_w23:34
dtchenmaxb: triaged your audio issue (sorry about the duplicated responses, perhaps due to gmail queueing)23:35
asacpace_t_zulu: ../upstream/chromium-browser.svn23:36
asacdoes that dir exist?23:36
pace_t_zuluasac: no23:36
asacpace_t_zulu: then you need to get a full svn tree first23:37
pace_t_zuluasac: should the full tree be ../upstream relative to chromium-browser?23:37
asacpace_t_zulu: so basically do the upstream way ... and then refer to that directory as LOCAL_BRANCH23:37
maxbdtchen: Thanks. I would be at home testing it were I not currently fixing a bike puncture in order to get home :-)23:37
pace_t_zuluasac: thank you for clearing that up23:38
asacpace_t_zulu: hmm. could also be that you dont need the gclient sync thing, but just a full svn checkout23:38
pace_t_zuluthe instructions are not very clear... i would be happy to help with that once i am successful building it myself23:39
asacfta_: ^^ ... is that LOCAL_BRANCH the full trunk?23:39
asacpace_t_zulu: you can definitly follow the upstream way to build it for now23:39
asacthe packaging needs some clarification i agree23:39
fta_?23:40
=== fta_ is now known as fta
pace_t_zuluasac: i really would like to help23:40
asacfta: getorig-source LOCAL_BRANCH=../.....svn23:40
ftayep23:40
asacfta: is that a full trunk? or src/ ?23:40
ftawhat is not clear about the packaging?23:40
asacfta: how to get ../upstream/chromium-browser.svn23:41
ftait's all what needed to build the full thing, depot_tools, chromium and the 3rd party libs23:41
ftajust ./debian/rules get-orig-source LOCAL_BRANCH=../whatever23:41
asacfta: so in particular: is whatever = http://src.chromium.org/svn/trunk or http://src.chromium.org/svn/trunk/src23:42
ftayou will have both a tarball and the full svn tree in ../whatever23:42
asaconly question i have what full svn tree means ;)23:42
pace_t_zulushould the ./debian directory be in the folder that contains the source? or the folder that contains the folder that contains the source23:43
pace_t_zulu?23:43
asacpace_t_zulu: wait a second ;)23:43
pace_t_zuluasac: i am bootstrapping from a source tarball23:43
ftaasac, it's trunk + what is needed by gclient23:44
asacpace_t_zulu: then you dont need to run get-orig-source23:44
ftaso you end up with http://paste.ubuntu.com/172653/23:44
pace_t_zuluasac: i bootstrap from the a source tarball then gclient sync23:44
asacfta: so just trunk. ok23:45
ftanot really, but close23:45
asacfta: yeah its trunk minus something23:45
asacfta: so if LOCAL_BRANCH does not yet exist will get-orig-source create it?23:45
pace_t_zulufta: where is debian in the tree?23:45
ftaasac, it's trunk + all src/DEPS for linux + tools23:46
ftayes, if the value of LOCAL_BRANCH does not exist, it's created, otherwise, it's updated23:46
pace_t_zulufta: basically what you would get from a source tarball + tools23:46
asacfta: ok so LOCAL_BRANCH is created23:47
asacpace_t_zulu: that command shoujld then work23:47
asacfor me it starts to pull stuff from svn23:47
asacjust ensure that you have the ../upstream directory23:47
asacand its empty23:47
asacpace_t_zulu: dont do anything with the tarball you want to bootstrap from23:47
ftathe initial idea of LOCAL_BRANCH is to prevent the daily 3GB checkout for the daily ppa23:47
asacfta: yeah i understand that. wasnt sure if one needed to bootstrap that manually23:48
ftanope23:48
ftaas long as you have the permission to write there, the script will work23:48
asacpace_t_zulu: so its just because you have no ../upstream directory23:49
pace_t_zuluso you need a ../upstream directory relative to the debian directory?23:50
ftayou can point LOCAL_BRANCH to anything, relative or absolute, it doesn't matter23:50
asacpace_t_zulu: i updated the instructions to include this nit23:50
pace_t_zuluasac: thank you23:51
pace_t_zulufta and asac: is there anything i can do to contribute?23:51
pace_t_zuluasac: should the 'upstream' directory be in the 'chromium-browser' directory?23:53
asacpace_t_zulu: no everywhere, but not there23:53
asacpace_t_zulu: ok also added how to actually build the package23:56
pace_t_zuluasac: thank you... i would still like to help in any way possible23:58

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