darkxstwe (Ubuntu GNOME) would like to opt-in for alpha1, what needs to be done for this to happen?07:57
tjaaltonany archive admin; pleae accept the uploads of mesa*, xserver-xorg-video-intel* to fix bug #117553308:39
ubot2Launchpad bug 1175533 in linux (Ubuntu Quantal) "[HSW] intel VGA driver i915 doesn't support new haswell graphics [8086:0a2e] " [Critical,In progress] https://launchpad.net/bugs/117553308:39
tjaaltonthe kernle & libdrm bits are there already08:39
=== doko__ is now known as doko
cjwatsonI've temporarily sync-blacklisted the packagekit transition by request of jbicha (23:42 UTC above)09:26
cjwatsonNow, time to debug why force-autopkgtest isn't working09:38
infinitycjwatson: Oh, if you're going to make the linux stuff get all forcey, let me upload d-i.09:40
infinitycjwatson: Uploaded.  When you get the whole mess to migrate, don't forget to change the seeds.09:42
cjwatsoninfinity: I tried forcing the autopkgtest bit of it at the weekend, but it didn't take for some reason09:42
* cjwatson nods09:42
infinitycjwatson: And now that d-i/linux migration is way less predictable due to autopkgtest delays, I think it's time for my next upload to implement that hack I was going to do to make the seeds not need ABI knowledge.09:43
infinityI'll do that after I've slept.09:43
cjwatsonAh, there, I think it was just a hint permission bug09:44
cjwatsonjibel: Can you make out from your end why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html still shows "autopkgtest for linux RUNNING" in a few places?09:57
infinitycjwatson: It got stuck due to linux's autopkgtest having a broken Depends:09:59
infinitycjwatson: I think Andy's fixing that in the next upload, but it won't get unstuck on the current version unless jibel works some magic.09:59
cjwatsoninfinity: Right, but shouldn't that have ended up as FAIL or something?10:01
infinitycjwatson: Possibly, yeah.10:01
* cjwatson commits a bit more logging10:01
cjwatsonAnd forcing linux-signed/3.9.0-7.1510:01
cjwatsonScottK: Curious about the kde4libs block; wouldn't proposed-migration's standard "wait until everything has built" have been enough there?10:02
cjwatsonNot that it's a huge problem if you're keeping an eye on it, I was just curious10:03
didrocksinfinity: hem, I don't even dare to ask more, but do you think you will have time for the unity SRU in raring? :)10:11
infinitydidrocks: Yeahp, can you bug me in ~6h? :)10:13
didrocksinfinity: will do :)10:13
jibelcjwatson, correct, it should be marked as FAIL even if it timed out or in that case what adt-run considers an invalid 'Depends' field. I'll check what happened10:25
LaneyLots of other tests seem to be stuck at RUNNING too10:26
Laneye.g. the ones triggered by glib2.010:27
cjwatsonYeah, it'd be helpful to know which end of the channel this bug is at10:27
* Laney nods10:28
ScottKcjwatson:  No.  I put it there so that it wouldn't migrate until the rest of the release was built (kde4libs could, in theory migrate as soon as it's built on all archs since it doesn't cause the older KDE packages to become uninstallable.10:46
ScottKNot that it matters much since armhf is broken.10:46
=== mmrazik is now known as mmrazik|lunch
ScottKcjwatson: I did a lot of New processing for KDE package splits over the weekend (not quite done, but close).  Would you please re-run the packageset script.11:31
cjwatsonYikes, it's been a while since I ran that.  It seems to want to put unity* into the Kubuntu packageset, which seems slightly odd11:34
ogra_it's all about unification :)11:37
cjwatsonI think it's all about a seed bug.  Let me see ...11:40
dokocjwatson, is the libreoffice autopkgtest failure still blocking migrations?12:12
cjwatsondoko: I was waiting for jibel to tell me if there was a problem at the Jenkins end before looking into that kind of thing12:16
cjwatson(Because as far as proposed-migration is concerned the libreoffice test is still "RUNNING")12:17
LaneyI did poke Sweetshark about that failing this morning12:18
jibelcjwatson, I found that the job that consumes test requests had been disabled, probably for a maintenance of the server last Saturday, and not re-enabled. I ran the script manually and that triggered tests for http://paste.ubuntu.com/5795363/12:22
jibelI'm waiting for the admin to show up before re-enabling that cron job12:22
cjwatsonjibel: Ah, that looks relevant, thanks12:22
cjwatsonHm, I should make force-autopkgtest operate on the tested package rather than on the triggering package12:22
jibelas I don't know why it has been disabled in the first place12:22
=== mmrazik|lunch is now known as mmrazik
cjwatson(force-autopkgtest> done)12:25
cjwatsonScottK: OK, fixed up seeds at least somewhat, and refreshed the packageset12:37
mlankhorstcan someone delete xorg-server in raring NEW? it will cause a regression in its current state14:25
RiddellI think I'll force kde4libs into -release, it's currently blocked on arm but I don't see that getting fixed in time for alpha 115:28
Riddellalso calligra and qtwebkit are the same15:28
cjwatsonRiddell: Will that render things above it uninstallable?15:29
smartboyhwRiddell, and rekonq?:P15:30
Riddellcjwatson: on arm but we can live without that for alpha 115:30
cjwatsonsmartboyhw: rekonq is collateral damage rather than failing in its own right15:30
cjwatsonRiddell: Hm, that will unfortunately make proposed-migration much more tolerant of mistakes15:31
cjwatsonThere's a BIG stack behind kde4libs15:31
cjwatsonYou're free to if you want but it's very unfortunate.15:33
cjwatsonRe auto-sync and possibly re-enabling it tomorrow morning; I assume we're just using a migration block for alpha 1, rather than disabling auto-sync and freezing harder?15:34
cjwatson(unfortunate> as in, if it were me, I would prefer to hold kde4libs out of the saucy release pocket until it's been fixed on ARM)15:35
=== mmrazik is now known as mmrazik|afk
LaneyIs proposed-migration right to say that pango1.0's autopkgtest is still running? Looks like it completed a few hours ago.16:24
LaneyAlso, shouldn't it be blocking on the failed LO test?16:24
Laneyit/glib2.0 & co16:24
seb128infinity, did you get pinged again about the raring unity SRU? ;-)18:40
seb128slangasek, ^ if you feel like doing some SRU work? (would be really good to unblock those fixes after > 1 month)18:41
infinityseb128: Just now, by you. :)18:41
infinityseb128: I'll get to it all today (I'll start on it now).18:42
seb128infinity, you are saying that for 1.5 weeks :p18:42
infinityThat's not true. :P18:42
seb128don't make me grab my IRC logs ;-)18:42
seb128infinity, thanks for looking at it today ;-)18:43
infinityLast week was a mess, though.  I'll admit to that.18:43
slangasekhey, the package has only been in the queue for 5 days, not 1.5 weeks ;)18:43
slangasekinfinity: a lot of treading water last week? ;p18:43
seb128slangasek, right, because infinity looked at it a week ago and rejected the previous ones, because the original sources from the ppa expired18:43
infinityslangasek: Hospital scares at the beginning of the week and then, yes, lots of floating away.18:43
infinityslangasek: I'm fine, but friends and family aren't so lucky, and I've been running around helping.18:44
seb128infinity, hope things get better for your friends/family!18:44
infinityseb128: Well, no one lost more than stuff.  Stuff's replaceable, though pricey.  Just lots of cleanup and cost evaluations and rebuilding and such.18:45
balloonsis kate the release manager for alpha1?19:05
infinityThere is no release manager, so no?19:06
balloonsinfinity, ahh.. well I'm asking who is setting up the milestone on the tracker and managing builds19:10
infinityballoons: stgraber, most likely.19:10
balloonsis stephane doing it all? ATM there is no milestone19:10
balloonstrying not to ping him on his holiday :-)19:10
infinityballoons: It's a public holiday in Quebec, I assume he intends to get to it tomorrow.19:10
infinityballoons: It all needs some love from him specifically anyway, since he's trialling the "flavours get to request rebuilds via the UI" bits.19:11
stgraberballoons: I'll be managing builds, will also take care of the tracker, though I only plan to do that once the first flavour says they're ready and want to get a1 builds19:11
balloonsstgraber, I think lubuntu is chomping at the bits to get some builds (at least the testing side is, heh). Just wanted to confirm who was going to manage it so I could direct them properly19:12
balloonsty stgraber and infinity19:12
Riddellcjwatson: I'm trying to force kde4libs into -release but it seems to need something more than the single force line, do you know what?20:05
Riddellwill it need every kde app forced?20:07
cjwatsonMaking the uninstallable count worse needs force-hint rather than force ...20:08
cjwatson(possibly as well as)20:08
cjwatsonI'm still very concerned that this will destabilise proposed-migration in general, but hey20:08
cjwatson630 uninst, grief20:08
cjwatsonI hope you know what you're doing20:09
phillwbdmurray: do you have 5 mins for a quick PM before the bugs section of ubuntu-clasroom start?20:28
=== ajmitch_ is now known as ajmitch
ScottK cjwatson: thanks for the packageset refresh.21:53
ScottKcjwatson: re forcing kde4libs - it's the victim of a gcc issue. there's not much between forcing it and skip Alpha 1.21:57
infinityScottK: Or do A1 with what's in the release pocket.  Or build kubuntu A1 against proposed.22:01
cjwatsonRiddell,ScottK: Just to confirm, are you OK with re-enabling auto-sync tomorrow morning as discussed on ubuntu-release, and relying on a migration block for your alpha needs?22:04
ScottKwhat's in the release pocket isn't much different than raring22:06
Riddellcjwatson: yep22:07
ScottKcjwatson: I'm in favor of it.22:07
cjwatsonOK, thanks22:11
cjwatsonWill you folks either put the block in place before tomorrow morning (my time), then, or else drop me a mail with the correct block line(s)?22:12
LaneyScottK: Maybe you could build it with gcc-4.7?22:12
Laney(on armhf)22:12
infinityLaney: That certainly would be a valid option.22:15
ScottKgood idea22:18
infinityI do share Colin's concern about raising the uninstallables count so high that britney becomes much less effective for a while.22:18
LaneyCan you educate me as to the problem there? I don't think I understand how britney works in that regard.22:20
infinityWell, britney's job is to make sure nothing gets worse after a migration.22:22
infinityIf things are already hideously broken, then you can introduce new breakage as long as you fix the same number of other breakages at the same time.22:22
infinityWhich isn't an ideal situation.22:22
infinityIdeally, you want the release pocket to be in a "not broken" state, rather than an "as broken as before" state.22:22
infinityBut if you force something that causes hundreds of uninstallables, you have to be pretty careful to unwind the whole mess again, rather than spending the next month trading one break for another.22:23
LaneySo it gives you room to trade off breakage. I thought it just didn't allow you to break new things.22:23
RiddellLaney: calligra is built with gcc 4.7 (cos you made it so) and it seems to have the same ICE22:24
infinityTechnically, it doesn't allow you to break new things, but when the case is that "everything that depends on Qt" is broken, that's a lot of wiggle room. :P22:24
LaneyRiddell: Actually I fat fingered that calligra change when I did it but we got away with it at the time22:25
Riddellinfinity: it seems to be either this or not do alpha 1 and I'd like to do an alpha22:25
RiddellLaney: how do you mean?22:25
LaneyI set one of the wrong environment variables22:25
Riddellexport CXX=g++-4.722:26
Riddellthat one?22:26
infinityThat only matters if the build calls CC at any point.22:26
infinityRiddell: No, the one above, which should have been CC, not CPP.22:26
LaneyI think I set CPP instead of CC22:26
infinityAnyhow, I don't see an ICE on calligra...22:27
infinity/build/buildd/calligra-2.6.92/krita/image/kis_filter_weights_applicator.h:305:26: error: conversion from 'double' to 'const KisFixedPoint' is ambiguous22:27
infinityJust a straight up error.22:27
infinityGuessing a qreal-ish porting issue?22:28
Riddellhum, I'm sure I remember seeing an ICE before22:29
infinityHrm, doesn't take kde4libs too long to fail on a Panda.  I'll test it with gcc-4.7 here.22:29
infinityErm, wait.  Did people retry kde4libs?22:30
infinity"The bug is not reproducible, so it is likely a hardware or OS problem."22:30
infinityThat means gcc tried again and succeeded the second time, and maybe the Panda was just sad.22:30
ScottKabout 142 bazillion times22:31
infinityHeh.  Alright.22:32
infinityI'll try it with 4.7 here.22:32
ScottKI even put the armhf buildds on manual briefly to make sure I retried it on each type of builder.  Failed on them all.22:35
infinityEvery time I test build on my Panda, I kick myself for not having spent the previous weekend reinstalling my mx6...22:35
infinityScottK: Each type?  There's only two, and they're basically the same.22:35
infinityScottK: Anyhow, if this test build passes here, I'll upload ASAP.22:37
ScottKcouldn't tell if it was two or three based on how they're listed.  in any case,  I hit a variety to be sure.22:37
infinityBut as for calligra, it's a straight up porting issue, not a GCC thing.22:37
infinity(And this is another unfortunate problem with hinting away arch problems, people tend to start seeing the same problem everywhere and getting hint happy)22:37
infinityThe old "if all you have is a hammer" adage.22:38

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