/srv/irclogs.ubuntu.com/2009/11/04/#ubuntu-devel.txt

=== dendro-afk is now known as dendrobates
wgrantlamont: Around to talk a bit about fairly important buildd changes?01:16
spmwgrant: fyi. he may answer anyway; but he eod' about 90 mins ago.01:26
wgrantspm: Oops, I thought it was closer than that, but I forget that DST switched off a few days ago.01:30
lamontwgrant: heading out to dinner with my sister - catch me tomorrow PST work hours?03:11
wgrantlamont: OK, I'll try to catch you late in that interval.03:12
lamontsounds good - when do you come online?  (UTC fine)03:13
wgrantlamont: I'm +11 at the moment, and am normally around from about 2100 UTC.03:14
lamontso yeah - I'm generally wrapping things up and getting ready to run by 2200-2300UTC03:15
wgrantRight.03:15
lamontand this week, I'm -8, and trying to be done by 3PM local --> 2300... so not too bad03:17
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
exewmtJust watched karmic boot cd fry a monitor03:54
exewmtOn first boot, i38603:54
hyperairfry a monitor?03:56
hyperairthat's pretty interesting. i wanna see too03:56
exewmtYep, booted until modesetting for 2nd splash03:57
exewmtFlashing light now03:57
exewmtCan't even display post03:57
exewmtDead03:57
hyperairdo you smell anything? =p03:58
exewmtNot my pc either, after installing ubuntu for people for 4 years, I get to buy a monitor03:58
exewmtNo03:58
exewmtNo burning, nothing of the sort03:58
hyperairheh03:59
hyperairwell, if it can burn from improper settings, it sure as hell has to be very old =p03:59
hyperairabout time, i'd say03:59
wgrantI think that monitor is disobeying some fairly important common sense.03:59
hyperairi agree03:59
exewmtYeah, Dell 15" , veery common03:59
exewmtScary how common actually03:59
exewmtFor legacy desktop stuff04:00
exewmtAbout time? It's now on me to replace it, way to go04:00
exewmtJust figured I'd tell you, but I guess it's just on everyone to upgrade04:01
jcastroScottK, around?04:03
exewmtI really hope that isn't the stance shuttlesworth wants .com take04:03
ScottKjcastro: Yep04:03
jcastroScottK, pretend I want to run -proposed to be a good citizen so I can find bugs before they hit -updates04:03
MsMacoexewmt: this isnt where bugs get reported04:03
ScottKexewmt: I think it's worth a bug report, although I think it's unlikely it's anything other than coincidental.04:03
exewmtThere should be a big red banner until that gets fixed though, because Dell has sold millions of these models in the us04:04
jcastroScottK, is there a bug list or tag I can follow?04:04
ScottKjcastro: There is.  Let me find it.04:04
MsMaco"warning: using the wrong mode is bad for screens"?04:04
LaserJockjcastro: ;-)04:04
exewmtScott: I watched it, it booted to splash04:04
ScottKjcastro: Did the OpenWeek PDF get fixed.04:04
jcastroI don't think it did04:04
exewmtMsMaco: It's Automaticc04:04
wgrantMsMaco: The thing is, it hasn't been bad for them for like 15 years.04:04
MsMacowgrant: wow04:05
ScottKexewmt: I'm not saying it didn't fry when you booted it, I'm just saying I think it's unlikely it was caused by a bug.04:05
jcastroScottK, I can check it now04:05
ScottKI still think it's worth filing, just in case.04:05
exewmtScottK: Thing is.... It won't even go to amber led04:05
ScottKexewmt: I don't doubt it died.04:06
exewmtNow just the same flashing green that first occurred when mode changes to grey screen w bar in boot seuence04:06
exewmtlike, right when the mode changes to 2nd booting splash04:06
ScottKjcastro: http://people.canonical.com/~ubuntu-archive/pending-sru.html - I don't recommed 'running proposed' however.  I recommend enabling it, installing just the package you want to test, and then disabling it.04:06
exewmtThat is why I don't think it was purely coincidence04:07
exewmtI have a few more, should I fry another!04:07
exewmt? (sorry touchtyping$04:07
wgrantOh, right, I forget about the DIEMONITORDIE command that xsplash sends on startup.04:07
serialorderis debootstrap ready so i can set up a chroot for Lucid? I was looking at it and noticed its the same one as used in Karmic04:08
exewmtwgrant: Just saying that between every other ver of xsplash used04:08
exewmtMaybe t's a bug affecting the ver bundled in the cd04:09
ScottKexewmt: What's in the CD and in the archive is the same.04:09
ScottKserialorder: I think they added lucid to the karmic one before release.04:09
jcastroScottK, I've always just thought we're supposed to run -proposed and report bugs.04:10
exewmtk, But should I test w an identical monitor and see if it bricks it?04:10
ScottKexewmt: Your call.  If it did, it would be pretty conclusive.  I think it's unlikely to.04:10
ScottKjcastro: I know people do that, but I don't recommend it nor do it myself.  The point is that we put stuff in proposed to test it and it doesn't always work out well.04:11
wgrantjcastro: That can cause problems when something is copied from -proposed to -updates, and all the testers use -proposed in its entirety. It could be broken with versions in -updates.04:11
exewmtScottK: We have a running bet then04:11
exewmtI'll be back tomorrow to report04:11
wgrantSo it's important to get people to test each -proposed package with everything else in -updates.04:11
ScottKjcastro: I've personally seen more problems with running -proposed than with -backports.04:12
ajmitchScottK: that doesn't sound positive04:12
MsMacoi usually run with proposed enabled04:12
ScottKajmitch: Thus my recommendation.04:12
jcastrowow04:12
ScottKI've also almost never seen a problem with backports.04:12
hyperairhas anyone noticed any issue with the recent udev SRU?04:13
MsMacoScottK: i can think of one problem with backports :P04:13
ajmitchI hadn't noticed there was a udev SRU04:13
ScottKI remember that one.04:13
jcastroScottK, I only noticed this problem now when LaserJock told me his empathy was crashing and I asked him to enable -proposed and he was wary of enabling the whole thing04:13
serialorderScottK, thanks04:13
jcastroScottK, has someone talked about this with like pitti or something?04:14
ScottKjcastro: It gets discussed every now and then.04:15
MsMacowell the point of proposed is to catch bugs...04:15
LaserJockit seems like we had some threads about this like a year ago04:15
ScottKSo far the "If we have people enable everything, we get more testers" has won the day.04:15
ScottKLaserJock: We did.04:15
LaserJocksomething about when the desktop team was thinking of having a staging PPA or something04:15
LaserJockfor me a lot of the -proposed vs -backports issue stems from a lot of -proposed packages being pretty core things04:17
LaserJockI don't often get a whole new kernel, Xorg, evolution, etc. from -backports04:17
LaserJock:-)04:18
jcastrowell, backports are new upstream releases04:18
LaserJockyep, but in my experience new upstream releases of low-risk packages04:19
ScottKOr when we do backport risky stuff, we do actually test it a lot before putting it in.04:19
ScottKBackports is often more tested than Proposed, but generally less tested than Updates.04:19
jcastroproposed is supposed to be the staging area for updates afaik04:20
wgrantRight.04:20
wgrantAnd sometimes stuff gets in there with very, very little testing.04:20
wgrantWhich is why very few people should run -proposed.04:20
LaserJockright, there's no real check on what goes in to -proposed other than pitti's quick check04:20
jcastrodo you have examples of little tested things that hit proposed?04:21
wgrantI sense that this is turning into that ML thread.04:21
MsMacoi thought the point of proposed was to do testing04:22
ScottKjcastro: We had a bad svn regression in -proposed that I recall.04:23
MsMacoi mean, the uploader should test yeah, but...if it was perfectly tested before upload, we wouldnt need proposed04:23
jcastroMsMaco, yeah but in some cases (like hardware stuff) there's only some testing an uploader can do04:23
* ScottK recalls a MOTU who was unaware udpates should be tested before uploading to proposed.04:23
ScottKI asked him how to test the fix and the response I got was, "I don't know".04:24
jdongb/i/r in pre... oh wait wrong process04:24
MsMacojcastro: right so...proposed is for testing...04:24
MsMacoim confused by whats surprising about that04:24
ScottKWhich is why you should just install stuff from it you plan to test, IMO.04:24
MsMacook i should just shush since im obviously the weird one in this bunch04:25
jcastroI don't think it's weird04:26
MsMacoif i run stable, its with proposed enabled. though i rarely run stable.04:26
MsMaco"production" system or not04:26
MsMaco(read "production" as "the only computer i have")04:27
jdongwell IMO if you install a package from -proposed, it should be to contribute to the verification process04:27
ScottKThe theory last time we went around on this was more peole just running proposed would increase the odds of catching an odd regression.04:29
MsMacothere were a few odd evolution regressions on hardy-proposed, i remember04:30
johanbrit worked the way it was supposed to? :)04:31
=== vorian is now known as v
=== v is now known as vorian
=== jdong_ is now known as jdong
=== ArneGoet1e is now known as ArneGoetje
wgrantpitti: You might want to copy jaunty-updates' tzdata to karmic-updates and lucid. We're seeing a few people confused by bug #467165.06:53
ubottuLaunchpad bug 467165 in tzdata "karmic version is lower then jaunty-updates" [Undecided,New] https://launchpad.net/bugs/46716506:53
dholbachgood morning07:27
ebroderHmm...am I supposed to be poking somebody to get lilo-installer accepted into hardy-proposed?07:36
stoojMorning Daniel07:44
dholbachhi stooj07:44
stoojI feel sorry for you - 9.10 is awesome, and you have to move straight on to Lucid already!07:45
wgrantBut Slashdot and The Register say that 9.10 sucks. They must be right.07:45
stoojGrr @ elReg: "60% of people hate Karmic in a poll on ubuntuforums" == News07:46
wgrantYup.07:47
dholbachstooj: karmic development slowed down a lot in the last weeks, so some of us got a bit of a break :)07:50
stoojGlad to hear it07:51
stoojGoing home - later all07:51
highvoltagewell they say there's no such thing as bad publicity08:07
user_hi guys.. i'm manipulating init scripts on my machine - I want service 1 to be stopped only AFTER service 2 is stopped. Do I use "Should-Stop 2" for this ?08:08
=== dholbach_ is now known as dholbach
primes2hapw: Hello, any news about this bug #446146?08:17
ubottuLaunchpad bug 446146 in linux "Several Huawei USB dongle don't work with kernel 2.6.31-12.40" [Medium,Fix committed] https://launchpad.net/bugs/44614608:17
jsgotangcohello sabdfl08:17
apwprimes2h, the fix for that is committed and will be rolled out in the first kernel SRU which is expected pretty soon.  likely thursday currently08:50
pittiGood morning09:01
pittiwgrant: ah, because of the +repack thing09:03
pittiwgrant: yeah, will do; thanks09:03
wgrantpitti: Thanks.09:03
pittiwgrant: ah, no, can't do; the packaging changed slightly, and it would be a regression to move the jaunty one to karmic09:04
pittiwgrant: what I'll do instead is to update the entire squad to 2009q, which was just released09:05
wgrantpitti: Even better.09:05
=== Tonio__ is now known as Tonio_
primes2hapw: Oh, that's nice. At least users would stop changing status to "fix released" on their own. ;)09:16
slangasekpitti: you marked bug #441638 as assigned to you; still working on it?  it seems there are a fair number of users for whom having bulletproof-X available would be a particular help right after upgrade09:59
ubottuLaunchpad bug 441638 in gdm "upstart job keeps restarting a dying gdm" [High,In progress] https://launchpad.net/bugs/44163809:59
pittiit's still on my list; although I didn't really intend to implement bulletproof X, just to stop the eternal auto-respawning10:00
pittibut if someone else wants to beat me to it, be my guest, of course :)10:00
slangasekpitti: ah - then per https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/441638/comments/20, I'll take it if you won't10:01
ubottuUbuntu bug 441638 in gdm "upstart job keeps restarting a dying gdm" [High,In progress]10:01
pittioh, thank you10:02
slangaseksiretart: hum, your cryptsetup apport hook change makes the package ftbfs in bzr10:08
slangaseksiretart: though I have yet to figure out why10:09
siretart`slangasek: I thought keybuk uncommitted it? - anyway, I think there is just a 'mkdir' missing in debian/rules10:10
slangasekwell, or an entry missing from debian/dirs10:10
slangasek(though why does this package not use dh_install, sigh)10:10
siretart`ah, right. that'd be easier10:10
slangasekanyway, no, not uncommittd10:10
=== akgraner_ is now known as akgraner
NCommandersuperm1, ping? (I'd like to talk to you about recovery partitions if you have a moment soonish)11:22
=== agateau is now known as agateau|lunch
=== thegodfather is now known as fabbione
=== ogra_ is now known as ogra
LaneyCould someone rescore https://launchpad.net/~laney/+archive/ppa/+build/1319012 for me, pretty please?13:03
Laney(testing an ftbfs fix for lucid)13:05
Laneynever mind, someone else did it :)13:12
pitticjwatson: could we have http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.lucid ?13:13
=== agateau|lunch is now known as agateau
seb128do we know when autosyncs should start? they are blocked on source format changes too?13:32
ogradoko, is the gcc in the archive already using ARMv7 and thumb2 ? or is that only the one in your ppa ?13:32
wgrantseb128: The autosyncer will crash at the moment due to the new source formats.13:32
james_wseb128: the autosyncer is currently pointing at unstable13:32
james_wthat will be fixed in the LP rollout scheduled for tomorrow morning I believe13:33
seb128is there anything stopping me to sync the desktop things I want if they are in good old source format still?13:33
wgrantseb128: I have a LP branch waiting for RC approval which will stop it from crashing, however it will not be able to sync v3 packages until somebody from the distro world convinces LP that it is important.13:33
pittiseb128: no, that works fine13:33
james_wspecific syncs in the old format are fine as far as I know13:33
seb128ok thanks13:33
wgrantThat will work fine, right.13:33
pittiI did several syncs and they work well13:33
seb128I just wanting to make sure before stepping where I should not ;-)13:34
pittiseb128: if Soyuz breaks, we'll blame you :)13:34
seb128I knew it!13:34
seb128;-)13:34
sebnerslangasek: is the ext4 corruption bug already fixed? LP says no so I'm wondering if it's the same issue linus closed with new -rc kernel. http://lkml.org/lkml/2009/11/3/37713:36
=== ingenius1 is now known as ingenius
=== marjomercado is now known as marjo
siretart`james_w: if some package branch is not available, does it make sense to report it as a bug, nag you on irc, or should I rather ignore it and just merge the package it in the "traditional" way?14:16
smoserdoes anyone know why ppa builds are taking so long ? https://launchpad.net/~smoser/+archive/ppa/+build/1318926 has been uploaded for 17 hours, it is to "start in 9 hours"14:20
ScottKsmoser: Look at the number of actively PPA buildds currently.14:21
Laneyapparently they were taken out to be release mirrors14:22
smoserScottK, where is that info?14:24
smoserah.14:25
smoserbut, just wondering, where can you see that?14:25
ScottKsmoser: https://launchpad.net/builders/14:25
james_wsiretart`: yes, yes and yes :-)14:26
sorenI'm still somewhat surprised that computing power is the bottleneck rather than bandwidth :)14:26
smoserthanks ScottK .14:26
james_wif you want me to take a look then I will, but it is often more than a 5 minute thing, so if it is urgent doing it another way would probably be wise14:27
siretart`no, it is not urgent. I'm just experimenting with merging package with bzr and I am making great experiences14:28
smosermore wondering, if "Architecture: all" then it gets built on i386 ?14:28
ScottKsmoser: Yes14:29
sgallaghmathiaz: A few months ago, you reported a set of unused dependencies in the SSSD. I didn't have time to look into them until now. I saw that you guys pulled in 0.7.1 recently. Would it be possible for you to point me to the build log, so I can see the set of unused dependencies?14:37
sgallagh/set/updated set/14:37
mathiazsgallagh: sssd is still at 0.5.0 in the developement  version (lucid)14:38
mathiazsgallagh: there is a bug to update it to 0.7.1 though14:38
sgallaghmathiaz: Oh ok, so it hasn't been run yet. I was just trying to get the updated set of dependencies so I can fix them all in one go.14:39
mathiazsgallagh: ok - I'll try to get a test build run14:42
mathiazsgallagh: and file a bug report about it14:42
sgallaghmathiaz: That would be fantastic. Thank you.14:44
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
davmor2pitti: I've done a bunch of upgrade tests and I can't reproduce the issues people are having with the kernel being the jaunty one.  Also only issue I did come across was one on audio where the gfx card has hdmi out.  But once I'd told pulse which card to use and unmuted it was fine.14:55
pittidavmor2: thanks; perhaps it's related to using apt-get dist-upgrade?14:56
davmor2pitti: I can run one and see for you if you want?14:56
pittiif you want, would be interesting to see if we have a bug there; but it should all be covered by the metapackages, I'd think?14:57
pittidavmor2: it wouldn't work if they removed the linux meta packages, of course14:57
mvothe upgrader will take care of a linux meta-package automatically, only apt-get users can be hit by that14:58
davmor2I'll try an apt-get upgrade and see how it does14:59
davmor2dist-upgrade even14:59
pittidavmor2: thank you!15:02
dokokees: online?15:03
=== Sp4rKy is now known as Guest37492
=== Guest37492 is now known as Sp4rKy
=== Sp4rKy is now known as Guest30894
keesdoko: I am now, hi!15:10
cjwatsonpitti: oops, forgot about that. It'll generate next time the cron job fires15:20
seb128doko, could you unbreak python in lucid too for the -lssl issue?15:20
pitticjwatson: thanks15:20
dokoseb128: no, please fix the apps15:21
seb128doko, there is a ton to do, could you be help having smooth transitions?15:21
seb128doko, that breaks a good part of GNOME15:22
seb128and I will not be able to look at those before uds15:22
dokoit's not breaking a running a system, so we should fix these during merges15:22
seb128between vac, travelling and sprint next week15:22
seb128I don't know how to fix those15:23
seb128could you send patches please?15:23
seb128doko, I guess I will just add libssl depends everywhere for now15:24
dokonot this week, and maybe not next week. if such a package is on my merge list, I'll fix it of course15:24
dokoseb128: don't do that, the bug report is concise about the exact fix15:24
seb128doko, could be clear to you but it's not to me and I said I don't want to get things blocked until after uds15:25
dokoseb128: what exactly is unclear?15:25
seb128the same packages is working in debian and those build fine in any other distro15:25
seb128I've no time to deal with autotools changes and convincing upstream of why ubuntu need that now15:26
dokoseb128: no, it's not in experimental15:26
seb128it's a compatibility breakage on your side imho15:26
seb128but whatever I don't want to argue now15:26
seb128I will add the depends so I get things to build15:27
seb128thanks15:27
jcastroRiddell, pitti, you have scheduling powers in the summit system now15:27
pittijcastro: thanks15:27
pittijcastro: rickspencer3 as well?15:27
jcastroyep15:27
=== akgraner_ is now known as akgraner
dokoseb128: I'm a bit pissed about your attitude to work around a known bug; it'll just be extra work later in the cycle15:32
* Riddell feels the power15:35
seb128doko, looks like a compatibility breakage on your side and not a known bug to me but I don't think arguing will bring you somewhere15:36
seb128doko, so let's agree to disagree15:36
dokoseb128: no, it has nothing to do about "compatibility"15:36
seb128doko, the python package should not those public if they are not meant to be used and if they are public you should install enough to get it working15:36
pittiwhat is the actual issue?15:36
seb128it's like shipping a .pc and saying to not use it15:36
seb128pitti, some python flag bringing -lssl without depends on libssl-dev15:37
seb128pitti, let me look again to the exact build failure15:37
seb128pitti, /usr/lib/python2.6/config/Makefile: LOCALMODLIBS=                       -lssl -lcrypto  -lssl -lcrypto      -L$(exec_prefix)/lib -lz15:39
seb128pitti, that is shipping with python2.615:40
seb128and GNOME softwares use it15:40
seb128but python doesn't have the depends corresponding to the -l<nnn>15:40
pittiseb128, doko: are LOCALMODLIBS meant to get linked to external softare?15:41
dokoit is wrong that an extension links with LOCALMODLIBS15:41
seb128what should be used instead?15:41
seb128I just feel that I understand the issue enough to argue upstream or open a bug there15:41
seb128+don't15:41
pittican't we just stop the affected packages from including LOCALMODLIBS into their linkage list?15:42
pittithat would also avoid extra dependencies and make transitions easier15:42
dokodon't use LOCALMODLIBS at all15:42
seb128why did they start using it in the first place?15:42
dokothe jaunty and karmic behaviour always links these libs with -lz, which is wrong as well. just by chance, or because zlib-dev is installed, lets you get away with it15:43
seb128ok, let me try to just drop that from the configure15:44
dokowhat was the bug number?15:44
seb128do you have any pointer saying why those should be used to use for upstream bug reference?15:45
seb128doko, bug #45035515:45
ubottuLaunchpad bug 450355 in totem "python extensions must not link with LOCALMODLIBS" [High,Triaged] https://launchpad.net/bugs/45035515:45
dokoseb128: at least for rhythmbox this is code which pre-dates distutils (i.e. python1.5). upstream is removing more and more of this old build stuff in every release, so an application/extension shouldn't rely on it. This code in gnome is really, really old. either distutils should be used, or at least python-config16:03
doko        PYTHON_CFLAGS="-I$PY_PREFIX/include/python$PYTHON_VERSION"16:05
doko        PYTHON_LOCALMODLIBS=`sed -n -e 's/^LOCALMODLIBS=\(.*\)/\1/p' $PYTHON_MAKEFILE`16:05
doko        PYTHON_BASEMODLIBS=`sed -n -e 's/^BASEMODLIBS=\(.*\)/\1/p' $PYTHON_MAKEFILE`16:05
doko        PYTHON_OTHER_LIBS=`sed -n -e 's/^LIBS=\(.*\)/\1/p' $PYTHON_MAKEFILE`16:05
doko        PYTHON_EXTRA_LIBS="$PYTHON_LOCALMODLIBS $PYTHON_BASEMODLIBS $PYTHON_OTHER_LIBS"16:05
dokopitti, seb128: for a quick fix, just remove the lines about PYTHON_LOCALMODLIBS and PYTHON_BASEMODLIBS. PYTHON-CFLAGS should use the output of python-config --includes to pick up the correct headers for debug builds, but apparently is not necessary in that package16:07
dokoanyway, afk now16:08
seb128doko, ok thanks16:23
Riddelldoko: word reaches me that gdb 7.0 is broken for c++, do you know anything about it?16:41
Riddellhttp://lists.trolltech.com/pipermail/qt-creator/2009-November/004963.html16:41
davmor2pitti: apt-get dist-upgrade seems to be correct just confirming now16:41
RiddellScottK: what does your backports hat say to having a gdb-6.8 in backports and having qt-sdk depend on that?16:41
davmor2pitti: it is in fact correct16:41
ScottKRiddell: I don't understand.  We already have 7.0 in Karmic?16:43
RiddellScottK: and I'm told it's broken16:44
Riddellfor c++16:44
ScottKRiddell: So you're thinking introduce a new gdb-6.8 package?16:45
RiddellScottK: yes16:45
ScottKIf so, I'd say get it into Lucid and a backport of a new package is no problem at all.16:45
Riddelldoko: got an opinion on that?16:46
ScottKIt might not be a bad idea to have a non-broken with C++ gdb in the development series either.16:46
davmor2pitti: anything else you'd like me to try?16:56
=== asac_ is now known as asac
pittidavmor2: thanks; so I guess it's a customized /boot/grub/menu.list or something such17:03
davmor2pitti: it certainly sounds it, that or a modded kernel17:03
jdstrandsoren: is there a vmbuilder somewhere that let's me build a lucid vm?17:14
jdstrandsoren: hi btw!17:14
tagI've been having trouble with a segfault in libc since one of the Karmic beta releases and it has continued even on a fresh install of the official karmic release.17:21
tagIt appears to be related to catgets, now I'm not sure if it has anything to do with localization files somehow.17:21
=== deryck is now known as deryck[lunch]
tagI know that's what catgets/catopen is used for.  When javac segfaults:17:24
tagor java, rather17:24
tag# C  [libc.so.6+0x31b08]  catgets+0x1817:24
tagI'm having trouble with both swing apps and some SDL apps, but specifically *all* java swing apps and the fancy-terminal tilda.17:24
=== Tarbo is now known as Guest58289
tagI can't seem to recreate the segfault by simply exercising catgets()17:37
mathiazrobbiew: hi - are there any guidelines for naming blueprints for lucid uds?17:47
mathiazrobbiew: for karmic we used to have karmic-$track-foo as a template17:47
mathiazrobbiew: has this changed for Lucid UDS?17:48
robbiewnot that I know of17:48
robbiewas long as you are consistent17:48
robbiewit really doesn't matter17:49
robbiewjust helps with finding the blueprints quickly for scheduling17:49
mptrobbiew, is mvo's reply enough info for you to schedule UDS sessions on Ubuntu Software Center stuff?18:02
robbiewyeah...I'll be doing the scheduling18:03
robbiewthis week18:03
mptok, thanks18:03
slangaseksebner: no, it's completely unrelated to the problem Linus is seeing in 2.6.32.18:18
sebnerslangasek: oh, I'm sorry than18:19
kirklandhttps://bugs.launchpad.net/bugs/458549  <--- most entertaining bug report in a while18:34
ubottuUbuntu bug 458549 in ecryptfs "One Tin Platter (The Legend of Davey Jack)" [Critical,Incomplete]18:35
=== ryu2 is now known as ryu
buxyUnfortunately merge-o-matic is down due to Debian's change of source package format.18:52
buxyanyone knows for how long? unfortunately the PTS mails me every 6 hours when http://patches.ubuntu.com/PATCHES can't be downloaded18:52
buxyslangasek: ^ (ping someone random that I know :))18:53
slangasekbuxy: until someone can update the merge-o-matic code to cope with the new packages; I think next week at the earliest18:53
ScottKbuxy: It's actually down due to Ubuntu not planning for the new source format.  Debian didn't do this by suprise.18:54
=== deryck[lunch] is now known as deryck
=== dpm is now known as dpm-afk
=== dendrobates is now known as dendro-afk
james_wScottK: bear in mind you are speaking to someone that is intimately familiar with how Debian did it ;-)19:09
buxyheh :)19:11
kirklandpitti: hi there19:21
kirklandpitti: around? procedure question for you19:21
kirklandpitti: order of operations, really19:21
=== dendro-afk is now known as dendrobates
mathiazsgallagh: hi - the current code in sssd trunk is supposed to be named 0.7.2 or 0.8.0?19:35
mathiazsgallagh: making sure to have the right upstream version number in the snapshot I'm preparing19:35
kirklandmathiaz: okay, i have *fixed* https://bugs.edge.launchpad.net/ubuntu/+source/kvm/+bug/404394  :-)19:40
ubottuUbuntu bug 404394 in kvm "qcow2 corruption regression" [High,In progress]19:40
kirklandmathiaz: i just uploaded to -proposed for SRU ification19:40
kirklandmathiaz: i also uploaded the fix to hardy-backports and intrepid-backports, as it needs to be fixed there too19:40
mathiazkirkland: as in: a SRU for -backports?19:40
kirklandmathiaz: right, sort of19:41
mathiazkirkland: out of curiosity - do you plan to do a backport of karmic kvm to hardy?19:41
jdongbugfix on top of backports (tm) :)19:41
kirklandmathiaz: no19:41
mathiazkirkland: virtio doesn't work on hardy host + karmic guests19:41
kirklandmathiaz: the kvm-84 backport took a *lot* of effort19:41
mathiazkirkland: agreed.19:41
kirklandmathiaz: how so?19:41
kirklandmathiaz: i think this new upload might fix that for you...19:41
kirklandmathiaz: you want a ppa package to test?19:42
mathiazkirkland: hm - I don't find the bug right now :/19:44
mathiazkirkland: it had to do with disk errors19:44
kirklandmathiaz: that's this19:44
mathiazkirkland: you'd see them in the guest - like I/O errors19:44
kirklandmathiaz: right19:44
mathiazkirkland: ok - then it's good news :)19:44
kirklandmathiaz: i believe this upload fixes your problem19:44
kirklandmathiaz: you want to grab the patch and test, or you want a ppa build?19:44
kirklandmathiaz: ppa build will take a while19:45
mathiazkirkland: it will cut down iso testing from 4 hours to 2 h and 42 minutes19:45
mathiazkirkland: I can wait for the PPA build19:45
kirklandmathiaz: https://bugs.edge.launchpad.net/ubuntu/+source/kvm/+bug/404394/comments/1619:45
ubottuUbuntu bug 404394 in kvm "qcow2 corruption regression" [High,In progress]19:45
kirklandmathiaz: that's the hardy patch19:45
mathiazkirkland: ok - I may have a look at it later19:45
kirklandmathiaz: is your hardy kvm server amd64 or i386 ?19:54
mathiazkirkland: amd6419:54
superm1hi NCommander, what's up?20:00
KEBA1considering the new gnome features (gnome shell and gnome zeitgeist) will come september 2010, is it possible that 10.10 will be a lts version instead of 10.04?20:01
KEBA1because mabye the old gnome wont be supported a long time20:01
MsMaco10.04 wasnt going to get gnome 3 anyway20:01
kirklandpopey: outstanding blog post on upgrading20:03
popeythanks kirkland20:03
MsMacopopey++20:06
KEBA1MsMaco: ah ok, because it might be to unstable?20:07
KEBA1like kde 4.020:07
MsMacoi guess so20:08
MsMacolessons learned?20:08
nxvljames_w: did you know why lp:ubuntu/hardy-security/firefox-3.0 is firefox 3.0.14 and not 3.0.15?20:08
nxvli mean the branch20:08
nxvljames_w: isn't it updated automagically after upload?20:08
james_wyes20:08
james_wI've been working out some kinks that meant it sometimes fell over though20:09
=== dendrobates is now known as dendro-afk
nxvljames_w: mm, so i just need to wait?20:12
nxvljames_w: it has been 2 days20:12
james_wnxvl: forced a check of that package20:14
nxvljames_w: thank you20:15
james_wnxvl: damn20:16
james_whit a bzr bug20:16
james_wlet me see if I can do anything about that20:16
nxvljames_w: my problem isn't exactly now20:16
nxvljames_w: i'm already late and doing some workarounds to make it work, so don't worry20:17
nxvljames_w: what i'm worried is about it becaming my primary process20:17
nxvljames_w: maybe we can discuss this better at UDS20:17
james_wyes20:17
kirklandmathiaz: build done -> https://edge.launchpad.net/~kirkland/+archive/ppa/+build/132060920:18
kirklandmathiaz: could you grab that .deb, try it out and let me know?20:18
mathiazkirkland: sure - when do you need an answer?20:20
wgrantlamont: Around?20:41
kirklandmathiaz: today'ish?20:42
kirklandmathiaz: i figure pitti will accept the upload for -proposed tonight20:42
kirklandmathiaz: i'd like to have your feedback before then, if possible20:42
mathiazkirkland: okoidoikoi20:43
sebastien_Hello tous le monde20:44
james_wnxvl: I appreciate the testing, I'm working to iron out the kinks as you find them. Thanks.20:44
sebastien_what is the chan for the ubuntu dev web ?20:44
nxvljames_w: thank you for making my life easier :D20:47
=== dendro-afk is now known as dendrobates
mathiazjames_w: seems that the karmic checkbox branch is not up-to-date21:00
mathiazcr3: ^^ this is why it generates these huge diff21:02
mathiazcr3: when you ask the review21:02
james_wmathiaz: queued an import, thanks21:02
mathiazjames_w: great - thanks21:03
james_wI took the opportunity of the release to do some infrastructure work, so downtime was longer than desirable21:03
=== lionel_ is now known as lionel
lifelessjames_w: hi21:12
james_whi lifeless21:12
lifelessyou have mail21:12
lifelessI think I mailed you about this some months ago21:13
lifelessbut I was reminded recently21:13
james_wdon't see it yet, give me a clue?21:14
lifelesspristine tar21:16
lifelessbzr21:16
wgrantslangasek: I slipped that autosync crasher fix into 3.1.10, as it has been delayed.21:18
slangasekhas it?21:19
wgrantYeah, by 24 hours -- 2009-11-05 090021:19
james_wlifeless: the answer is still the same as before21:19
lifelessjames_w: I don't recall what it was, sorry21:20
slangasekwgrant: ah, ok21:26
slangasekwgrant: that must be why the announcement mail didn't look right to me :)21:26
ScottKFortunately someome pointed out they'd neglected to announce their planned outage, so they rescheduled and announced.21:28
ftado we already know if lucid will use gcc 4.5 or stick with 4.4?21:29
slangasekfta: 4.421:31
ftaok, thanks21:31
mathiazcr3: http://bazaar.launchpad.net/~cr3/ubuntu/karmic/checkbox/0.8.5-0ubuntu1/revision/1321:31
mathiazcr3: is this^^ the diff to apply to checkbox?21:31
mathiazcr3: (except for the revision number - that I can fix)21:32
mathiazkees: hm - trying to do a SRU for a native package (checkbox)21:35
mathiazkees: the new revision number is 0.8.5-0ubuntu0.1 as suggested by https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging21:36
mathiazkees: however debuild -S complains about a missing .orig.tar.gz file21:36
james_wI don't think that recommendation applies to native21:36
mathiazkees: http://paste.ubuntu.com/309940/21:37
keesmathiaz: hrm, yeah, that suggestion in the wiki may be wrong.21:37
slangasekhonestly, I think it's better to ignore the debuild complaint21:37
keesmathiaz: I would have said 0.8.5ubuntu0.1 or 0.8.5~0.1 .... native packages are weird.21:37
mathiazslangasek: doing that create a checkbox_0.8.5-0ubuntu0.1.tar.gz21:38
keesslangasek: that works too :)21:38
slangasekmathiaz: I don't see a problem with this :)21:38
slangasek0.8.5~0.1 doesn't work, that would sort earlier than 0.8.521:38
mathiazkees: ok - so what do you suggest?21:38
keesslangasek: it won't?  I thought that's what ~ did.21:39
keesmathiaz: 0.8.5-0ubuntu0.1 without an orig should be fine21:39
slangasekkees: ~ sorts before null21:39
slangasekso if you're already at 0.8.5, 0.8.5~0.1 means going backwards21:39
mathiazkees: ok - thanks.21:39
keesslangasek: right, i assumed 0.8.5 did not yet exist (i.e. SRU)21:40
keesI see, however, that this is not true.  :)21:40
mathiazkees: oh - 0.8.5 is already in the archive21:40
keesmathiaz: how about 0.8.5.1 then?  :)21:40
=== thunderstruck is now known as gnomefreak
mathiazkees: that's possible as well21:41
mathiazkees: I was just following https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging21:41
slangasekwell, given that it's a native package anyway, 'ubuntu' in the version number seems redundant21:41
slangasek0.8.5+nmu1?21:41
keesnooo21:41
slangasekor 0.8.5+nmu0.121:41
slangasekor 0.8.5-0.121:41
slangasekor flog cr3 and make him stop using native version numbers21:41
* kees likes the latter21:42
mathiazkees: "flog cr3 and make him stop using native version numbers" ?21:44
keesmathiaz: yup.  there's rarely a reason to use native numbers.  he should release proper tar balls, and use -0ubuntuN package versions21:45
mathiazkees: well - we've discussed this.21:45
mathiazkees: he used to do that (release tarballs)21:46
mathiazcr3: we should probably revisit that at the next UDS then21:46
james_wmathiaz, cr3: checkbox branches up to date21:50
mathiazjames_w: awesome - thanks21:50
lifelessjames_w: is there a command to export a tarball from a bzr branch [with pristine-tar magic]21:52
james_wno21:52
lifelessok. I think thats what I'm basically looking for21:53
lifelessI have use cases beyond debs21:53
lifelesswhich is perhaps why you've been answering diferent questions than I've thought I had been asking21:53
siretartjames_w: if you have a free minute, you might want to review the imports for the devscripts package. I've just finished merging it with debian using bzr branches, but noticed that there are tons on conflicts, and most of them are spurious...21:56
james_wsiretart: from sid?21:57
siretartit doesn't really matter if I merge the sid branch into the karmic one or the other way round21:58
siretartgenerally, merges seem easier if you merge the ubuntu branch into the debian one21:59
=== dendrobates is now known as dendro-afk
Laneysemantically that's what you are doing, right?22:01
james_wyeah22:01
james_wsiretart: it's because unfortunately the latest shared ancestor we have is ages old22:03
james_wwe don't have a full debian history, and so in some cases there have been huge changes since we can last infer a merge22:04
james_whang on, that's not quite right22:04
mathiazkirkland: seems that your kvm backport is working well here22:17
james_wit's a bug that has been fixed in the meantime22:17
mathiazkirkland: I'm able to perform a successfull install of a karmic guest using a qcow2 file via virtio on a hardy host22:18
mathiazkirkland: which is failing with the version from hardy-backport22:18
kirklandmathiaz: \o/22:25
kirklandmathiaz: okay, please provide feedback in that bug22:25
mathiazkirkland: commented in the bug22:25
kirklandmathiaz: that'll help get the uploads approved22:25
kirklandmathiaz: great22:25
kirklandmathiaz: sorry about that in the meantime22:25
mathiazkirkland: now the question I have is: are there any side effects on other configuration?22:26
mathiazkirkland: like raw+virtio22:26
mathiazkirkland: or qcow2+ide22:26
mathiazkirkland: or block device+virtio?22:26
kirklandmathiaz: good question; i'm not sure.  but this code is upstream22:26
kirklandmathiaz: and was released in RHEL522:26
mathiazkirkland: right - so IIUC the patch is against block-qcow2.c22:27
=== Zic is now known as Guest56730
mathiazkirkland: so it would only affect qcow2 files right?22:29
mathiazkirkland: why would qcow2+virtio fail and not qcow2+ide?22:29
kirklandmathiaz: it should only affect qcow2+virtio22:29
=== sconklin is now known as sconklin-afk
kirklandmathiaz: the affected code is in the qcow2 block driver22:30
mathiazkirkland: so qcow2+scsi uses a different block driver?22:30
kirklandmathiaz: http://paste.ubuntu.com/309969/22:30
mathiazkirkland: so qcow2+*ide* uses a different block driver?22:30
kirklandmathiaz: qcow2 is one block driver22:31
kirklandmathiaz: raw is another22:31
mathiazkirkland: ok - so why does virtio trigger the bug and not ide?22:32
kirklandmathiaz: ide, scsi, virtio are different interfaces22:32
kirklandmathiaz: i'm not exactly sure22:32
=== Guest56730 is now known as Zic
mathiazkirkland: there's another comment added in the diff - probably related to the issue22:33
mathiazkirkland: does that mean that IDE doesn't do multiple writes while virtio does?22:33
kirklandmathiaz: that sounds plausible; i don't know this code well enough to say for sure22:34
kirklandmathiaz: thanks for the reminder to fix this issue in this morning's meeting22:35
kirklandmathiaz: i had mostly forgotten about it22:35
mathiazkirkland: np - that's what bug lists (and LP fwiw) are for :)22:35
sgallaghmathiaz: Sorry for the delay. We haven't officially decided what we're numbering the next release of SSSD. It's supposed to be a 1.0 release candidate. We might call it 0.8.0, 0.9.0 or 1.0.0rc (I'm leaning towards the latter)22:37
mathiazsgallagh: ok thanks for the update. It's not that important for now. Just making sure the release number are working correclty for package upgrades.22:37
mathiazsgallagh: so I'll use 0.8.0 and the version number could always be bumped for the final version22:38
sgallaghmathiaz: Thank you for reporting the build failure. I'll look into that first thing tomorrow22:38
sgallaghmathiaz: Yeah, I'm using 0.8.0 for our internal builds right now, with the same reasoning22:38
mathiazsgallagh: great. Probably a linking issue22:38
sgallaghmathiaz: Yes, I suspect that the way we determine SELINUX_LIBS is probably coming up with the wrong set of flags on Ubuntu.22:39
=== dendro-afk is now known as dendrobates

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