stokachustgraber: ping00:21
=== _salem is now known as salem_
=== salem_ is now known as _salem
pittiGood morning05:03
dholbachgood morning06:02
stgraberstokachu: pong06:19
=== security is now known as megha
=== tvoss is now known as tvoss|exercise
=== jono is now known as Guest50668
stgraberroaksoax, Daviey: So MAAS was uploaded after final freeze. How critical is it that you have it on media for 13.04?07:35
=== smb` is now known as smb
infinitypitti: Methinks it's probably final langpack time?08:04
infinitypitti: (Unless that happened when I wasn't looking, it's been a weird week for me)08:04
pittistgraber, infinity: I'm about to upload a new network-manager with more tests, and resurrecting the dnsmasq autopkgtest; no changes to the actual code, is that okay?08:05
pittiinfinity: ah, good point; requesting full export now08:05
infinitypitti: More tests are fine, if they pass. :P08:05
pittiinfinity: yes, I'm pre-testing in a jenkins-like VM08:05
pittiand they now cover WPA and WPA2 as well08:05
pittiinfinity: actually, we got a full export yesterday, so unless we are heading for an even fresher one I'll take that one08:06
infinitypitti: Also, I've lost track through all the apport/whoopsie iterations what the new and improved "we're about to release" workflow is for stuff.  Do we still do some bit twiddle on apport, or is that a thing of the past?08:06
pittiinfinity: we still have to twiddle, but that already happened for raring08:06
infinitypitti: Yesterday should probably be fine.08:06
infinitypitti: Okay, cool beans.08:07
infinitypitti: Did your langpack chroot ever get upgraded, or are you still fudging it on a porter?08:08
pittiinfinity: it was, all working fine on macquarie now08:08
pittithe cron'ed ones also come from there08:09
infinityHrm, I wonder if I should try to fast-track Marc's apt-ftparchive change in precise to get it on pepo before we generate raring's final Sources.gz08:10
pittiinfinity: the only thing left to do there is to figure out how I can copy/rsync the precise ones from the porter box to macquarie08:10
pittiI haven't yet found a suitable route through ssh/firewalls/etc (except through my box, which would take ages)08:10
infinitypitti: netcat ftw?08:10
infinitypitti: Or just ask a GSA to do it for you.08:11
pittiinfinity: yeah, probably an RT08:11
pittiinfinity: I tried that back then, can't directly ping/cat from macquarie to osageorange08:11
pitti(or the other way round)08:12
* pitti turns the crank for building packs08:12
pittias we currently have four amd64 and four i386 buildds, I guess one should be permanently reassigned back to i386?08:13
=== Amaranthus is now known as Amaranth
infinitypitti: Oh, we should toss more than one back when we accept this mess anyway.08:15
infinitypitti: Like, all but one. :P08:15
pittiright, but only temporarily08:15
pittibut I thought we permanently have 5 i386 and 3 amd6408:15
infinityUsually, yeah.  I rebalanced cause we had a bunch of heavy arch:any jobs on the go.08:15
infinityMaking that a shared pool is on my TODO for the next cycle.08:16
infinitypitti: Anyhow, crank away.  You have 7 i386 builders now.08:18
infinitypitti: Once you verify those source packages are building right and looking sane or whatever, feel free to self-accept the lot.08:18
pittiinfinity: it'll take some two or three hours to build the (source) packages on macquarie and then I want to test them first08:18
pittiinfinity: ack, will do08:19
cjwatsoninfinity: pepo's on lucid, not precise, FWIW08:19
infinitycjwatson: Oh, right.  Derp.08:19
infinitycjwatson: I can backport his patch for IS.08:19
cjwatsonI thought that's what barry had done08:19
infinityOh, did someone already get there? :P08:19
cjwatsonDid that not happen?  He was certainly talking about it in foundations meetings ...08:19
infinityI've been missing those meetings of late.08:20
cjwatsonYeah, it's on pepo08:20
infinityYeahp, so it is.08:20
cjwatsonhttp://paste.ubuntu.com/5720945/ - head of /usr/share/doc/apt-utils/changelog.gz08:20
infinityHe says to the man staring at that in a terminal.08:20
infinityWas there a plan to also push that to lucid-updates, so it doesn't get lost after a security update?08:21
cjwatsonNot sure.  barry?08:22
infinityI mean, ideally, pepo will be precise some day.  But, I don't know when that day it.08:22
* cjwatson fixes up the bug metadata08:23
* infinity gives the i386 chroot a quick refresh before pitti goes all langpacky.08:23
pittiinfinity: ah, thanks08:24
infinityActually, I guess I'll do them all.  It's not like I can sleep anyway.08:24
stgraberinfinity: are you trying to shift to the Australian timezone right before flying to Europe? you really like jetlag that much? :)08:26
* infinity wonders why his Panda thinks it's 2012...08:26
infinitystgraber: I've only slept about 8 hours since Sunday.  It's not by choice, I assure you.08:26
stgraberinfinity: ouch08:27
seb128xnox, hey08:36
xnoxseb128: heya.08:36
seb128xnox, https://bugs.launchpad.net/ubuntu-geonames/+bug/1150109 ... is "fix commited", what is needed for it to be "fix released"? #is to deploy the update?08:36
ubottuLaunchpad bug 1150109 in Ubuntu Geonames "Ubuntu's geonames only knows about Hong Kong in Guyana, not in China" [Undecided,Fix committed]08:36
xnoxseb128: pending RT ticket I believe.08:37
seb128xnox, ok, thanks08:37
seb128xnox, do you have the rt number by any chance? ;-)08:37
seb128xnox, 60594 I guess08:38
xnoxseb128: correct. =) you are quick with RT08:38
seb128xnox, :p08:39
xnoxseb128: /me was waiting on thunderbird to launch and find the emails.08:39
seb128I went on the site and typed "geoname" in the query field08:39
seb128that listed only 2 tickets08:39
seb128so easy enough ;-)08:39
xnox2...? interesting.....08:39
seb128xnox, the other one is "Make geonames a fully webops managed service"08:40
xnoxseb128: interesting =) maybe I should look into that.08:40
cjwatsoninfinity: Think I should flip base-files now, for the sake of minimal obstacles to release candidate being true candidate?08:43
infinitycjwatson: Go nuts.08:44
infinitycjwatson: We really need to rewrite these checklists as we go.  They're a bit stale.08:45
cjwatsonFighting the last battle08:45
infinitycjwatson: Twiddling CONF.sh early isn't an awful plan either, IMO.08:45
cjwatsonHm, I've not done os-release before.  Any objections to me setting PRETTY_NAME to "Ubuntu 13.04", rather than something in the style of "Ubuntu quantal (12.10)" as was used for 12.10?08:49
infinitycjwatson: How's it look in Debian?  I'm not too picky, since we've not really done much with os-release...08:50
infinityPRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)"08:50
infinitySo, seems to match vaguely the format of issue.net08:51
stgrabercjwatson: I think it makes sense not to use the codename for the released version.08:51
cjwatsonOK, I'll go for "Ubuntu 13.04"; people can reupload if they object08:51
seb128the upstream definition is "A pretty operating system name in a format suitable for presentation to the user. May or may not contain a release code name or OS version of some kind, as suitable."08:51
seb128"Ubuntu 13.04" seems fine to me08:51
infinitycjwatson: That sounds good to me.08:51
infinityOh, wait, that means you're stealing base-files TILM from me.  Grr. :)08:54
infinityI geuss I'll resync in a week. :P08:54
cjwatsonFeel free08:55
evmpt: current theory: code is sound, we just need to run build_errors_by_release twice.08:55
mptev, you've unit-tested?08:55
evmpt: I have for the case of one system that reports an error a week ago, then a day later, then a day later08:55
evmpt: feel free to suggest more test cases08:55
evbut I realised that the work of build_errors_by_release would be inaccurate after the first run. FirstError will not be correct until we've seen all the data, and so ErrorsByRelease will not be correct until a second run.08:56
evWe're not processing the error reports in time order. We can't.08:57
=== zyga_ is now known as zyga
evSo for one system, if we see a report from a day ago and write it into FirstError and ErrorsByRelease, then we see a report from a week ago and write it into FirstError and ErrorsByRelease, the data in FirstError will be correct, but that first error report value in ErrorsByRelease will be inaccurate, because it was based on a report from a week ago being the first error report seen for the given release.08:58
cjwatsonbase-files uploaded, CONF.sh twiddled08:59
evI have no idea why this didn't occur to me straight away08:59
evmpt: I'll be posting a merge proposal for you and bdmurray to review today. I'll try to make the unit test as readable as possible.09:01
infinitycjwatson: Cheers.09:01
=== ckpringle_ is now known as ckpringle
infinitypitti: chroots are all updates, BTW.  Should be good to go when you're ready.09:20
pittiinfinity: thanks09:20
pittisources finished building, I'll give them a smoke test and binary debdiff now09:21
infinitypitti: If you have buildd admin, feel free to give amd64 a few machines back when you're done.09:21
pittiinfinity: I have, will do09:21
* infinity goes to see if he can get a couple hours of sleep...09:22
infinityMaybe I'll get lucky tonight.09:23
cjwatsonGood luck09:25
pittiinfinity: sleep well!09:26
pittinew langpacks look good, and have a lot of previously missing domains09:48
* pitti uploads; buildds, brace for impact09:48
seb128pitti, do you want/need testers?09:49
pittiseb128: if you wish; hang on, I'll build French ones09:50
pittiI checked English and German09:50
pittithere's no particular reason to believe anything is broken, but it can't hurt of course09:50
pittiseb128: les paquets de language sont ici: http://people.canonical.com/~pitti/tmp/langpack/09:54
pitti"de lange"09:54
pitti"de langue"09:54
pittididrocks, cjwatson, stgraber: perhaps for the final freeze we should disable the daily autolanding?09:55
didrockspitti: it's in manual mode09:56
seb128pitti, what daily autolanding?09:56
seb128what didrocks said09:56
pittididrocks: ah, because I just see builds09:56
didrockspitti: yeah, it's building everyday09:56
didrockstrying tests09:56
didrocksbut doesn't publish09:56
pittioh, that's just for the PPA, ignore me09:56
didrocksyep :)09:56
infinitydidrocks: Disabling even those PPA builds next week might be nice, in case they happen to clog the buildds at Just The Wrong Time and we need to get someone to kill them.09:58
didrocksinfinity: we can do that temporarly, however, we are preparing SRU009:58
didrocksinfinity: so yeah, if you see anything critical, we can kill them. however, right now, what's building is more the touch stacks for S that we bootstrap than stuff in daily release09:59
didrocksinfinity: meaning, like, this morning, only 2 source packages built for raring (in indicators stack)09:59
didrocksnothing else on the daily release "r"09:59
infinitydidrocks: Well, for release minus 48h, it might be nice to not have a panic conflict, but I also know which shoulders to tap if I need a buildd Right Now too.10:00
didrocksinfinity: agreed, can be disabled by then, we need to have mterry, cyphermox, robru and kenvandine do the "disable bits" for it (it's not a global switch)10:00
infinitydidrocks: Ahh, well.  I'll talk to you next week about it when we're in the same timezone.10:01
didrocksinfinity: sounds good :)10:01
seb128pitti, language-pack works fine for me, gnome-calculator is in french, all good ;-)10:01
pittiso much for sleeping :(10:01
infinitypitti: I'm asleep right now, can't you tell?10:02
pittiseb128: ah, most important app ever!10:02
pittiseb128: merci10:02
seb128pitti, lol10:02
seb128pitti, that's the one that I know about which was missing its template ;-)10:02
seb128pitti, de rien10:02
pittiinfinity: your IRC proxy clearly passes the Turing test!10:02
infinitypitti: Can you elaborate on that?10:05
=== tvoss|exercise is now known as tvoss
pittiEliza, how are you today?10:06
infinityAnd here I was, afraid you wouldn't get the reference.10:07
pittithe most important emacs feature missing in vim!10:07
highvolt1gein a very poor school district in south africa, I migrated a few schools form Fedora to Ubuntu a few years ago10:08
highvolt1geand received a bunch of faxes begging to bring back emacs because the kids wanted it back badly10:08
highvolt1geI was a bit confused as to why the kids wanted emacs so badly. turned out it was for the psychologist :)10:09
infinityDamn you, Launchpad, for not instantly knowing about new Debian uploads.10:11
infinity^-- Inclusion thereof is clearly RC for raring.10:12
StevenKinfinity: You have to wait for gina10:12
infinityStevenK: DON'T WANNA.10:12
xnoxinfinity: veto, unless is also ships a loldog symlink.10:13
* StevenK overrules xnox, since he is an archive admin10:13
* xnox :`(10:13
* infinity removes emacs from the archive to spite xnox.10:14
xnox /msg doko please blacklist lolcat10:14
xnoxinfinity: please do, everyone should be using emacs24 by now ;-)10:14
infinityxnox: I meant all emacsen. :P10:14
xnox /o\10:14
StevenKinfinity: Some way to track Debian uploads without having to have a mirror on iron (and probably somewhere else in the DC) and gina would be awesome10:15
StevenKOh, no, it's the debbugs mirror that is bounced twice, iron is not10:15
infinityStevenK: You'd think we could get near instant turnaround by tracking a changes list and pulling from incoming.10:16
infinityThough, incoming suffers the problem that there's no signed index, so we're blindly trusting the signatures on the .dsc files.10:16
infinityWhich is likely bad. :P10:17
cjwatsonWhich is pretty much why we wait for a mirror, yeah10:17
StevenKAnd at this point, we stuck until katie runs and ftp.uk is pulsed10:17
infinityOf course, incoming DOES have a signed index at /buildd/10:17
infinityShame it's no accessible to the public.10:17
StevenKinfinity: Not even a DD?10:18
xnoxnot _all_ DD10:18
infinityAll buildd admins have access to the buildd bits.10:18
xnoxlegal issues prevents access to incomming?!10:19
infinityMaybe we could get someone to agree that allowing us to pull from there would be cool.10:19
StevenKBack in my day, you couldn't build from incoming10:19
StevenKxnox: Yup10:19
StevenKxnox: It's a fun legal issue10:19
infinityHrm?  There are no legal issues with incoming.10:19
infinityincoming.debian.org is poorly named, it should be accepted.debian.org. :P10:20
xnoxinfinity: if it's new and ftp-master hasn't reviewed it yet..... oh incoming is not NEW?!10:20
infinityThe only technical issue with us pulling from incoming is that it has no trust path.10:20
StevenKincoming is not NEW, no10:20
infinityxnox: incoming.debian.org is queue/accepted.  Not to be confused with queue/incoming, which is the precursor to new/by-hand/etc.10:21
StevenKNEW is locked down, due to some US acroymn and having to announce packages to the US government because they may contain crypto, but my knowledge might be years out of date10:21
infinitySerious terminology overload.10:21
StevenKI thought BYHAND was mostly dead?10:22
xnoxStevenK: right, which debian was requested to stop mailing, but simply keep a record & produce it upon request.10:22
xnoxaren't docs and d-i bits still BYHAND?10:22
StevenKxnox: I was around when BenC produced the first list, which was 8,000 pages10:22
xnoxwow =)10:22
infinityAnd one wonders why DPLs burn out and disappear.10:23
* xnox is very young ;-)10:23
StevenKI've been a DD for 12 years10:23
infinityAnd you've still not fully repented for linda.10:23
StevenKLinda had her uses. And a fan club.10:24
infinityCharles Manson has a fan club.10:24
infinityJust sayin'.10:24
StevenKinfinity: Here, I have something for you. It's called 'ether'10:25
infinityYes, please.10:25
* xnox ponders how to check when one became a DD10:25
* infinity takes the hint and goes to stare at the ceiling some more.10:25
StevenKxnox: nm.debian.org10:25
StevenKBut only those who went through the new NM process10:26
xnoxmeh just a year.10:26
* xnox just under 2 years from start to finish.10:26
LaneyI think that might be a relative definition of "new"10:26
StevenKhttps://nm.debian.org/public/process/13201 is me10:27
infinitySweet.  Sledge has been a DD since the UNIX epoch.10:27
infinityhttps://nm.debian.org/public/people/dd_u <-- Might have accuracy issues for people who predate the NM database...10:27
StevenKMaybe just a bit10:27
xnoxStevenK: hmm... 5 days that's swift.10:27
StevenKxnox: Yup10:27
StevenKxnox: I didn't hear about the "NM problems" until after I became a DD and I was "What problems?"10:28
xnoxStevenK: I also had something like 7m+ hunting down for someone to sign my key.10:29
infinityStevenK: My AM was a slacker compared to yours.10:29
=== doko_ is now known as doko
StevenKI've been accused by others of having my dates changed by the klecker fire, and by one person that "I must have gotten access to the NM system and changed my own dates"10:29
StevenKinfinity: Who was your AM?10:29
highvolt1gen/win 1210:30
StevenKinfinity: tbm talked to joeyh about me, joeyh said "Yeah, Steve knows what he's doing", and tbm went "Right, there's T&S done."10:30
=== highvolt1ge is now known as highvoltage
mptev, the simplest test case would be one machine that reported one error today producing a weighted error rate of 1/9010:31
StevenKxnox: Ah, I had no issues with that, Sydney has a large number of DDs10:31
infinityI didn't have any DDs nearby, but I had some kernel devs that were considered strongly connected enough.10:32
StevenKI think I had four or five DD signatures by the time I applied10:32
evmpt: if a machine reported one error today and it was their only error for the release, wouldn't that be 0, not 1/90?10:32
evit's been 0 days since their first error.10:32
StevenKbod, wildfire, gus spring to mind10:32
infinitypasc, csmall?10:33
infinityMan, I haven't seen pasc in ages.10:33
StevenKI pre-date pasc being a DD10:33
infinityRight.  Sleep.  No reminiscing.10:33
mptev, yep, you're right :-)10:33
mpt(off-by-one error!)10:33
evI feel like balloons should be falling from the ceiling right now and someone should be approaching my desk with an award10:34
evmaybe a cake10:34
=== ckpringle_ is now known as ckpringle
* katie runs for StevenK 11:18
evbdmurray: happy to report that the only OOPS reports in https://errors.ubuntu.com/oops-local/2013-04-18/ yesterday were caused by me11:20
StevenKkatie: The *other* katie11:21
ev(I have a branch to fix the bug, I'm just a bit stuck on the YUI DataSource.Get code for catching a 404 raised by the API when the user cannot be found)11:21
cjwatsontjaalton: bug 1169071 - are they superseded by some other packages?  just trying to work out what to write in the removal comment11:24
ubottubug 1169071 in nvidia-settings-experimental-304 (Ubuntu) "please remove from the archive" [Wishlist,Confirmed] https://launchpad.net/bugs/116907111:24
tjaaltoncjwatson: yes, we have nvidia-304/310 already11:27
tjaaltontseliot knows the right answer I think :)11:28
tjaaltonwhy we had both11:28
=== security is now known as megha
DktrKranzcjwatson: wrt bug #1083091, I can't do it right now in Debian because of its rdep gtg. It's on my radar, and it'll be gone as soon as Wheezy is released :)11:44
ubottubug 1083091 in liblarch-gtk (Ubuntu) "Remove liblarch-gtk from the archive" [Wishlist,Fix released] https://launchpad.net/bugs/108309111:44
obounaimWhat is the lowest level packaging command that is called by all the other packaging tools like pbuilder, sbuild..?11:53
tumbleweeddpkg-buildpackage -b11:55
tumbleweedwhich essentially calls debian/rules build; fakeroot debian/rules binary11:55
obounaimok thanks12:01
obounaimI am looking for to integrate scan-build int the packaging system, any ideas how to do that?12:02
obounaimfor a way12:02
pittiinfinity: FTR, roseapple and allspice sent back to amd64 duty12:04
obounaimyes a static analyzer for C/C++ programs12:04
xnoxjibel: how would you like installer bugs tagged that affect ubuntu-gnome images? "ubuntu-gnome" tag? Are you ubuntu-gnome team monitor those?12:23
xnox(e.g. in ubiquity package we use kubuntu, xubuntu, lubuntu tags when it only affects those images)12:24
loolcjwatson: Hmm ISTR that ffmpeg was in a germinate blacklist, but I can't find it anymore; did the situation change or is this something that we were checking manually?12:27
loolI see it in supported-desktop-extra now12:27
loolcjwatson: ah!  found libavcodec in ubuntu.raring/usb-ship-live, nm12:28
loolseb128: ^12:28
jibelxnox, your question is for jbicha?12:28
xnoxjibel: correct.12:30
xnoxjibel: he is not here =) hmm... will catch him some other time.12:30
ScottKSweetsha1k: There's a bug asking for lo-menubar to be removed from raring.  Is that correct?12:35
seb128ScottK, yes, that got replaced by an upstream implementation in libreoffice itself, but that was for quantal, I'm surprised we still have the old source in the archive12:40
seb128so indicator-weather is just broken12:40
seb128is anyone working on it/upstream for it?12:40
seb128or should we just drop it from raring?12:41
tseliotcjwatson: nvidia-310-updates has transitional packages for experimental-310 and 304->updates for experimental-30412:49
=== _salem is now known as salem_
mptCould someone please answer my questions in bug 1166230 about why there are ever updates to "transitional dummy packages"? Thanks kindly.13:00
ubottubug 1166230 in update-manager (Ubuntu) "Updater lists many transitional dummy packages" [Medium,Confirmed] https://launchpad.net/bugs/116623013:00
seb128mpt, they are updated because they are typically built from the same source as the real package13:03
seb128mpt, like gcalctool -> gnome-calculator13:03
seb128mpt, so they have the source version13:03
mitya57hey seb128, do you think we can backport https://bug691040.bugzilla-attachments.gnome.org/attachment.cgi?id=238204 for raring gtk2?13:08
mitya57(bug 1125260)13:08
ubottubug 1125260 in gtk+2.0 (Ubuntu) "gtk_file_chooser_get_current_folder() function is broken in 2.24.10 < GTK+ < 2.24.15" [Undecided,Confirmed] https://launchpad.net/bugs/112526013:08
seb128mitya57, (sorry, otp, seems reasonable but maybe check with Laney/the release team)13:08
mitya57it'll be nice to have it at least as a sru13:10
=== mitya57 is now known as mitya57_
=== mitya57__ is now known as mitya57
gesermpt: at your 2nd questions: it's not always possible to remove those transitional packages yet as the transition isn't complete (e.g. ubuntu-minimal -> module-init-tools which is a transitional package to kmod)13:12
dokojibel, pitti: everything green now with the python autopkg tests?13:14
pittino, still not :(13:15
pittipython2.7: can't open file '/usr/lib//test/regrtest.py': [Errno 2] No such file or directory13:16
jibeldoko, it wasn't last time I checked, dbm test failed13:16
xnoxmpt: furthermore, we support LTS->LTS upgrades thus when we renamed gcalctool -> gnome-calculator, we kept a dummy empty package gcalctool which simply depends and installs gnome-calculator, such that a Precise user upgrades to 14.04 his "gcalctool" upgraded package installs "gnome-calculator". Then in 14.10 we can remove gcalctool transitional package.13:16
xnoxthus most of transitional packages stick around for 2 years or less.13:16
jibeldoko, for 3.313:16
pittijibel, doko: right, for 3.3 there are three failures in dbm13:16
Sweetsha1kScottK: we can do that yeah. its a transitional by now.13:17
Sweetsha1kScottK: /me in call13:17
=== wedgwood_away is now known as wedgwood
rbasakrsalveti: I'm just looking at the avogadro FTBFS. It's another example of the GLdouble declaration conflict. https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=gldouble+previous+declaration has nine others. Would it be an idea to collapse these into a single bug with multiple tasks? Is there a simple fix that will fix them all, or does each package need individual treatment?13:20
dokojibel, pitti: crap about 2.7/testsuite. can't see the test_io failure here with 2.7/testsuite-dbg13:21
dokojibel, doko: hmm, the test_dbm failure isn't reproducible here either13:25
cjwatsonrbasak: Each package needs individual treatment, so it should remain separate bugs rather than being collapsed into a single bug with multiple tasks.  See https://wiki.ubuntu.com/ARM/FTBFS#OpenGL_and_Qt_combination13:43
cjwatsonDktrKranz: Oh, I hadn't noticed that the liblarch that builds python-liblarch-gtk is still only in experimental.13:43
tseliotpitti: is it possible that jockey is trying to set the alternative in enable() before XorgDriverHandler.enable() finishes. This would explain our problem13:47
barrycjwatson, infinity yes, it's probably a good idea to backport the patch to lucid.  i can do that13:47
tseliotpitti: also maybe in a separate thread?13:48
pittitseliot: jockey doesn't use threads13:49
pittitseliot: so unless the nvidia.py handler calls them in the wrong order, no13:50
tseliotpitti: could it be that apt/dpkg does though?13:50
tseliotpitti: if so, as  a workaround, I can make sure that the alternatives are set in enabled() instead of enable()13:51
pittitseliot: no, enabled() must not change anything13:53
tseliotpitti: hmm... I guess I'm out of ideas on bug 804662 (on the nvidia-common side)13:54
ubottubug 804662 in nvidia-common (Ubuntu Precise) "jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 must contain only strings" [High,Triaged] https://launchpad.net/bugs/80466213:54
pittineed to run out for a bit, back in 45 ins13:54
tjaaltonslangasek: looks like I've come up with a fix for the plymouth race bug http://pastebin.com/2bZu24yG (+ 'and plymouth-ready' to *dm.conf)13:55
tjaaltonon another note, can someone explain why 'pkg-config --libs nss' doesn't show -lpthread, while it's linked against it?13:56
diwictjaalton, are you sure that it should, as long as the host software doesn't need -lpthread ?13:57
tjaalton-ldl is also missing, these both caused build issues with sssd13:57
cjwatsontjaalton: it's only linked against it indirectly13:57
tjaaltondiwic: I don't know13:57
tjaaltoncjwatson: ahh, ok13:57
cjwatsonuse 'objdump foo.so | grep NEEDED' rather than ldd13:57
cjwatsonsorry, objdump -p13:57
tjaaltongotcha, thanks13:58
cjwatsonso sssd must either be linked against something else that fails to specify that you need -lpthread; or it's using pthread directly and erroneously not specifying it13:58
tjaaltonnah the build-issues have been fixed, but upstream (or fedora) is complaining why these fixes are proposed there :)13:59
cjwatsonlibnssutil3 and libnspr4 are both directly linked against -lpthread13:59
tjaaltonor something, pinging me about it anyway13:59
cjwatsonhm, and  pkg-config --libs nss  says -lnssutil313:59
cjwatsonwell; -lpthread should not be necessary in sssd unless it uses pthread functions directly, should it?14:00
tjaaltonthere are some components that do use it14:00
cjwatsonwhich it does14:00
cjwatsonso it's sssd's fault then.  use directly, link directly.14:00
cjwatsonand don't use directly, don't link directly.  should be very simple :)14:00
seb128lool, we are discussing the gettext issue on #ubuntu-hardened14:00
cjwatsonlool: ubuntu.raring/ship-live is generally the governing one, but yes14:01
tjaaltoncjwatson: ok, but shouldn't nss.pc have -lpthread then if libnssutil3 links to it?14:03
cjwatsontjaalton: only if the mere fact of using the nssutil API causes the program using it to have *direct* references to symbols in libpthread14:04
cjwatsontjaalton: for example if an nssutil header file had macros that expanded to pthread_*14:04
tjaaltoncjwatson: alright.. think I got it this time14:04
cjwatsonprograms shouldn't overlink by re-specifying all the indirect linkage of the libraries they use14:05
cjwatsonat least not on Linux14:05
tjaaltonwhat changed it for raring?14:05
cjwatsonit actually causes some subtle problems if they do14:05
cjwatsonnot aware of any toolchain-level changes here for raring14:05
cjwatsonmaybe something changed in nss, dunno14:06
Laneymitya57: is the patch reviewed/committed upstream?14:06
tjaaltonmaybe it's nss/nspr then14:06
tjaaltonok, case closed anyway14:06
mitya57Laney: looks like a different set of patches was committed, I didn't yet figure out which of them actually fixes the bug14:07
Laneymitya57: sounds like SRU would be better then14:07
mitya57there are *lots* of gtkfilechooserbutton fixes @ https://git.gnome.org/browse/gtk+/log/?h=gtk-2-2414:07
Laneyeven since .17?14:08
* mitya57 wonders whether it'll be better to backport the whole set of fixes14:08
Laneyso there are14:08
Laneymaybe there will be another release14:09
mitya57Laney: is "another release" OK for SRU?14:10
LaneyGNOME micro releases are14:10
mitya57Laney: OK, so let's wait for the new release, I'll prepare a SRU then14:11
Laneymight be good to find out if/when that is planned for14:12
mitya57I don't think there is any schedule14:14
mitya57xnox: do you know why your reply is shown at http://www.riverbankcomputing.com/pipermail/pyqt/2013-April/thread.html, but my original mail isn't?14:14
xnoxmitya57: are you subscribed to the mailing list? as far as I remember it's moderated list.14:15
mitya57xnox: is it auto-moderated for those who are subscribed? I am not (yet)14:16
xnoxmitya57: yeah. rather not moderated at all if posted by subscribers, kind of like launchpad mailing lists.14:17
mitya57ok, let's hope they will read my mail via yours :)14:18
mitya57xnox: by the way, did you already test if phablet toolkit works with PyQt?14:20
xnoxmitya57: it could be me building it wrong though =/ I am surprised it build at all =))))14:20
xnoxmitya57: nope. I have only tried simple standard show a QApplication with a label =)14:21
mitya57but the target is the toolkit, right? or why do you need it?14:21
xnoxmitya57: my initial target is getting a non-trivial gui app working (e.g. ubiquity) or something QML based.14:22
mitya57xnox: fwiw, apart from QFont constructor and Xserver crashes, I am able to run ReText under Qt 514:22
xnoxmitya57: the target is to get oem-config (ubiquity) frontend in python with ubuntu-touch Qml components.14:22
xnoxmitya57: but we'd want pyqt4 (with qt5.... and eventually pyqt5) regardless of anything.14:23
mitya57yes, let's hope PyQt5 will be available soon14:24
mitya57and thanks for the work you have done!14:25
xnoxmitya57: i would not hold my breath waiting for PyQt5 release14:25
ogra_well, probably if you are a professional diver ...14:26
xnoxogra_: i'm no Linus ;-)14:28
mitya57seb128: I think https://plus.google.com/u/0/106010143685041042333/posts/XeygQ6A9dEk indicates that the author is not going to continue i-w development14:29
rbasakcjwatson: thanks, and for the wiki link - I had googled but not found it.14:29
cjwatsonMight be a plan to grab the UbuntuKylin people and point them at that post - hard14:31
mitya57(Vadim is here, and his nick is roignac)14:32
seb128mitya57, oh ok, thanks for pointing it, shame that he got offended just because those guys forked some code, they are pretty new to opensource communities and are learning...14:33
seb128mitya57, well, from what I see that yahoo service has been discontinued for a while .... in any case if nobody is wanting to fix it, just drop the source from raring, that's a shame though :/14:34
mitya57yes, let's drop it14:36
* mitya57 has to leave14:39
slangasektjaalton: 'start on filesystem' is very late, I don't think that's what you want - that's going to unnecessarily slow the boot down in some cases14:50
tjaaltonslangasek: 'startup' didn't work14:51
slangasektjaalton: I think you instead want 'start on startup or started plymouth-splash'14:51
tjaaltonhmm let me try again14:51
slangasektjaalton: 'startup' didn't work for the plymouth-in-initramfs case?14:51
tjaaltonI think so, hang on14:51
tjaaltongot some ideas from #upstart too, added sleep 0.1 and dropped console-output14:52
tjaaltonoh now it worked, heh14:52
=== nemo is now known as hedgewars|nemo
Riddellogra_: I've come to the conclusion that the kubuntu nexus images you made don't work14:54
ogra_haha, thats a prompt reply14:54
Riddellogra_: flashing them to the nexus just stops indefinately14:54
Riddellogra_: http://paste.kde.org/728402/14:55
Riddellogra_: that's quite reproducable on two nexus 7s14:55
ogra_when do you flash boot ?14:55
ogra_oh i see ...14:55
Riddellogra_: when it's in firmware mode14:56
ogra_your images are to big14:56
ogra_you can try using the -S option for fastboot14:56
ogra_but thats sadly unreliable and doesnt work on all models14:56
ogra_try with -S 512M14:57
ogra_that will cut the img in little chunks while transferring14:57
cjwatsonDaviey: Could you or somebody on your team confirm bug 1017609?15:02
ubottubug 1017609 in python-melangeclient (Ubuntu) "Please remove melange from ubuntu archive" [Undecided,New] https://launchpad.net/bugs/101760915:02
slangasektjaalton: also, I think you want to drop the 'stop' rule, add an 'instance $UPSTART_EVENTS', and lose the while loop15:06
tjaaltonslangasek: ok..15:07
Riddellogra_: well that seems to successfully copy over but then on reboot it drops me to an initramfs command line15:07
Riddellsaying "mounting /dev/mmcblk0p9 on /root failed: invalid argument"15:08
slangasektjaalton: e.g., (untested): http://paste.ubuntu.com/5721802/15:09
ogra_Riddell, thats with the matching bootimg file in place ?15:10
Riddellogra_: yep15:11
slangasektjaalton: caveat: for the plymouth-in-initramfs case, this will emit the event twice15:11
slangasektjaalton: which means, actually, that the initctl emit should be --no-wai15:11
ogra_Riddell, what kind of n7 is that (what size)15:11
ogra_just the 8G one or something bigger ?15:11
slangasekLaney: indicator-weather upstart respawn> haha, +115:12
ogra_uuuh !15:12
Riddellogra_: Google Nexus 7 Tablet PC (Android 4.1 Jellybean) - 16 GB15:12
ogra_as someone who had his disk eaten by indicator-weather i strongly disagree !15:12
slangasekogra_: oh, but you had your disk eaten by it because it was writing to .xsession-errors... as an upstart job you're safe from that ;)15:13
ogra_Riddell, hmm, might be that mmcblk0p9 isnt the userdata partition on that device15:13
slangasekogra_: you can even just remove .cache/upstart/indicator-weather.log, and upstart will automatically re-open the logfile automatically ;)15:13
ogra_slangasek, haha, so upstart doesnt log ?15:13
slangasekit *does* log - /properly/15:14
ogra_i could write an upstart job to remove it once it hits a certain size !15:14
Riddellogra_: ubuntu images work fine on it15:15
slangasektjaalton: so does my counterproposal make sense?15:15
Laneyslangasek: :-)15:15
slangasek(happy to explain it if not - also happy to take the discussion to #upstart, now that I've noticed I had fallen off the channel)15:16
tjaaltonslangasek: yeah, I'll test it in a bit15:19
slangasektjaalton: ok, cool15:19
tjaaltonI had --no-wait there first since I copied the idea from somewhere15:19
ogra_Riddell, hmm, try with a more recent bootimg then15:20
cjwatsonHow often is the rdepends data on qa.ubuntuwire.com updated?15:23
tjaaltonduh, forgot that modemmanager doesn't work with my old laptop (3g builtin). it hangs in shutdown and timeouts after some minutes, not a nice machine for quick testing15:23
tjaaltonthen again, power button15:23
slangasektjaalton: modemmanager> hmmm please escalate that to cyphermox15:23
cyphermoxerr what?15:23
slangasekmodemmanager is supposed to be shutdown cleanly by NM15:23
slangasekif it's still hanging on shutdown, that's a pretty serious bug15:24
tjaaltoncyphermox: I'll update the machine and get back to you later :)15:24
cyphermoxit wasn't, but I'll take a look15:24
tjaaltonslangasek: seems to work on the non-initrd (=normal) case15:26
tjaaltonnext the odd one15:26
=== hedgewars|nemo is now known as nemo
tjaaltonslangasek: hmm, works without --no-wait15:36
tjaaltonslangasek: the non-initrd case15:36
tjaaltonslangasek: same thing with initrd case15:38
tjaaltonthat's probably why it suddenly started working for me, when I dropped it :)15:39
tjaaltonslangasek: actually the initrd-case isn't working with your version15:42
tim`hrmm - there appears to be a libqwt6 package but no libqwt6-qw4-dev package15:47
tim`how are you supposed to get qwt6 dev headers?15:47
cjwatsontim`: libqwt-dev15:48
roaksoaxstgraber: howdy!! there are critical fixes that I think *need* to be fixed because it truly affects how it behaves in distributed environments and could potenttially break deployments. As far as the media side, i think I would be fine to accept it as a 0-day sru, as long as it hits the archives as part of raring15:48
roaksoaxstgraber: Daviey would be a better person to discuss this with :).15:49
tim`cjwatson: thx is 6 default now then ?15:49
roaksoaxstgraber: but idk whether he is back in the UK or whether he is flying now.15:49
cjwatsontim`: no idea, I just looked at the package structure ...15:50
tjaaltonslangasek: 'status plymouth-splash' should never return 'started' for the initrd case15:50
stgraberroaksoax: ok. We haven't technically started spinning RC media at this point, so if you're 100% sure this won't cause regressions, I think I'm fine to accept it (as 0 day SRUs for main pieces of software is always a bit annoying)15:52
tjaaltonslangasek: adding " || plymouth --ping" fixed it :)15:53
cjwatsontseliot: I don't see a transitional package for nvidia-settings-experimental-304 - is it OK to remove anyway?15:53
Riddellogra_: curiouser, on my other nexus it mounts fine (same boot image) and shows plymouth then goes to a blank screen15:53
cjwatsontseliot: ah, it's provided by nvidia-settings-304/nvidia-settings-304-updates I see; so would "superseded by nvidia-settings-304/nvidia-settings-304-updates" be a suitable removal message?15:54
Riddellogra_: Serial Debug Shell doesn't work15:54
tseliotcjwatson: oh, good point. I guess it will be ok, since the new drivers will pull in the relevant nvidia-settings flavour anyway15:54
=== Zic is now known as Guest51927
cjwatsontseliot: The Conflicts/Replaces/Provides are probably sufficient, if those are the correct replacement packages15:56
tseliotcjwatson: I guess a number of packages provide that though15:57
cjwatsontseliot: Yep - well, decide quickly whether you want me to remove it now or whether you want some further packaging change15:58
tseliotcjwatson: ok then please leave the nvidia-settings-* there for now, I'll make sure I come up with some proper transitional packages15:59
smbstgraber, So with that unpleasant UEFI experience there is something that probably should go into the release notes. Problem is that the kernel driver for efivars now refuses to add the ubuntu boot key when the space is already filled up to a certain degree. However the installer does not realize this a just shows the "reboot now" dialogue. Which then does not find anything to boot.15:59
stgrabersmb: yep, not sure about what to put in the release notes though... "If you install on UEFI and don't see an Ubuntu entry post-reboot, your system is broken, turn BIOS mode back on and use that."? :)16:01
slangaseksmb: oh, is *that* what's happening!16:01
slangasek(bug #1170183)16:01
smbUnfortunately (maybe again AMI) a GPT partition with something in does not count as bootable. Most seem to only look for EFI/BOOT/BOOTxxx.EFI.16:01
ubottubug 1170183 in grub2 (Ubuntu) "can not boot up in uefi secure boot mode unbuntu 13.04, can run in a live from cd uefi secure mode. will boot non secure boot mode" [Undecided,New] https://launchpad.net/bugs/117018316:01
stgraberor actually "reboot your system twice and try again" (as it's the AMI way of triggering the garbage collector and hopefully save some space)16:01
smbstgraber, Did not seem to help on that board... hence caused me to issue the command of doom16:02
stgraberbut yeah, I've had that specific issue on one of my UEFI machines and ended up going with a factory reset of the firmware which wiped enough stuff to let me write a new boot entry16:02
stgrabersmb: how long had you been using that board with UEFI on raring?16:02
stgrabersmb: I'm wondering whether you may have had some kernel panic dumps in pstore/nvram back when we still had that enabled in our kernel which would have caused your nvram to be pretty full and prevent any extra write (that was the cause for the broken efibootmgr on my other UEFI machine)16:03
smbstgraber, Not really long. That board is maybe 1 or two months old. And from that time I only did a UEFI install of 12.04.2 and kept that running. And then had some non-efi installs for other tings. Raring I probably only had tried the one or two weeks16:04
smbThe dumpstore output of all variables did not seem to contains anything like dumps16:05
stgrabersmb: hmm, ok, so that's not it. 12.04.2 doesn't have pstore efi nvram IIRC and if you only had raring for a couple of weeks you never had that in your kernel (sforshee turned that off after I bricked my laptop for the second time, so 1-2 months ago)16:05
smbBut maybe hidden through compression or so. Who knows. Yesterday I still was able to get the ubuntu entry written after I booted through efi shell and re-issued dpkg-reconfigure grub-efi-amd6416:06
smbNot anymore today16:06
stgraberthough I have no idea what kind of crap the firmware may end up storing in there causing it to grow slowly and eventually reach the 50% threshold16:06
smbYeah, I could not really tell16:07
smbJust hope that not too many people install aside a win8 and secure boot requiring the efi bios...16:08
cjwatsonogra_: I think bug 1153313 may need your attention before the archive team can do anything with it16:08
ubottubug 1153313 in usb-imagewriter (Ubuntu) "Please port usb-imagewriter to modern APIs, or remove it" [Undecided,New] https://launchpad.net/bugs/115331316:08
stgraberwell, that's just every single machine you currently find in stores... (and apparently they all have some flavour of the broken AMI firmware, haven't heard of anything shipping with a non-AMI UEFI firmware yet)16:09
roaksoaxstgraber: yeah I have been testing this the past week and have not found any regressions.16:09
stgraberroaksoax: ok, good enough for me. I'll let it in now. I can't remember seeing anything horribly wrong when reviewing the diff the other day16:09
stgrabers/other day/this morning/16:10
ogra_cjwatson,  do you need any attention from me to remove it from the archive ?16:10
ogra_cjwatson, updated the title :)16:11
cjwatsonogra_: comment in the bug ...16:11
smbstgraber, Yeah, if one would not have missed the good old bios already... anyway, the brick is packed to be sent msi's way.16:11
roaksoaxstgraber: i'd like to do a quick run now though? or at what time do you have to release this?16:11
roaksoaxstgraber: i think I spotted a tiny issue that I would like to get tested16:11
cjwatsonogra_: https://bugs.launchpad.net/ubuntu/+source/usb-imagewriter/+bug/1153313/comments/116:11
ubottuLaunchpad bug 1153313 in usb-imagewriter (Ubuntu) "Please remove usb-imagewriter from the archive" [Undecided,New]16:11
ogra_yeah, just saw it16:12
ogra_if SSO wouldnt constantly time out on me i could fix that wiki ...16:13
stgraberroaksoax: well, too late, it's already been accepted into the archive... if that issue is problematic enough, just upload again and I'll review the new one16:13
ogra_cjwatson, added a note that this is only supported until 12.1016:18
ogra_feel free to remove it16:18
tjaaltoncyphermox: turns out it was caused by (ahem) buggy sssd upstart job which leaves upstart thinking it's running when in fact it failed to start.. so my fault :P16:26
tjaalton"sssd stop/killed, process 1239" -> shutdown waits for 5min until it proceeds16:26
tjaaltonbut modemmanager at least used to segfault all the time on this machine, I need to revisit that issue..16:27
slangasekzyga: hi, did you end up filing any bug reports for your efivars/pstore issues?16:32
slangasekzyga: cf. bug #1170183, another user who I've asked to run 'grub-install --uefi-secure-boot' whose boot config failed to be updated16:33
ubottubug 1170183 in grub2 (Ubuntu) "can not boot up in uefi secure boot mode unbuntu 13.04, can run in a live from cd uefi secure mode. will boot non secure boot mode" [Undecided,New] https://launchpad.net/bugs/117018316:33
zygaslangasek: hi16:39
zygaslangasek: actually no, I only sent an email to the ubuntu-devel ML16:40
zygaslangasek: let's see16:40
zygaslangasek: interesting16:44
zygaslangasek: the symptopms are similar, I wonder if the cause is as well16:45
roaksoaxstgraber: alright. Uploaded a new package, is a really tiny change to one of the patches. SOrry about that16:45
slangasekzyga: since this seems to be a new install, it seems unlikely to be caused by the kernel filling the nvram16:45
zygaslangasek: indeed16:45
zygaslangasek: but if you recall, there were two oddities in my casae16:46
zygaslangasek: nvram going dry _and_ the incorrect image being loaded16:46
hallynslangasek: ok, so after going through some more links and edk2/ovmf code:  indeed you can NOT currently save efi nvram to a file from qemu.  david woodhouse was working on a patch in january toward this (http://permalink.gmane.org/gmane.comp.bios.tianocore.devel/1706), and others talk about using qemu's flash fs support.  i'll keep looking, and perhaps jump in on the patch to support that.16:53
slangasekhallyn: ah, alrighty16:53
hallyn(see for instance http://blog.hansenpartnership.com/uefi-secure-boot and http://sourceforge.net/mailarchive/forum.php?thread_name=CAFe8ug_dnTdU0OWR_LiGAzmcLgUDvumQJ%3DYgT9jZQmd14BNwHQ%40mail.gmail.com&forum_name=edk2-devel for more confirmation that you can't right now)16:53
=== Guest51927 is now known as Zic
xnoxbdmurray: are you uploading ndiswrapper to raring? as far as i can see we want it into precise as well due to linux-lts-raring17:07
xnoxor do you want me to upload?17:07
bdmurrayxnox: I uploaded it to raring, you could do precise17:07
xnoxbdmurray: ack. adding to my todo list for some time later e.g. by 12.04.3 i'm guessing.17:08
slangaseksmb, cking: so regarding pstore... why should we not just patch out pstore writing to uefi nvram?17:54
slangaseksmb, cking: it seems to be causing us no end of problems, and pre-3.9 there isn't even a "good" way to get at the data to maintain it, AIUI17:55
=== yofel_ is now known as yofel
ckingsforshee, ^^ didn't pstore uefi get disabled in raring?17:56
stgraberslangasek: we did actually17:57
stgrabercking, slangasek: Ubuntu carries an extra patch that disables UEFI nvram storage as a pstore backend17:57
slangasekso we're not pstoring in efi at all anymore?17:57
slangasekok, then I guess zyga's problem was just because he managed to fill nvram before that17:57
slangasekand this patch will go (or has gone) into 12.04 enablement kernel, right?17:58
stgrabersforshee wrote that one after we discovered the whole "thinkpad turn into brick on panic" bug17:58
stgraberslangasek: I guess so17:58
ckingbut also there was a patch to limit uefi vars from filling > 50% or so of space to avoid bricking issues too17:59
stgraberslangasek: I think that in theory we could remove mjg59 change to restrict nvram writes when > 50% of space used as without the pstore use case, it should be relatively safe to do so17:59
ckingone issue is that now we may not have enough free space to set the boot vars and hence installs fail if we run low18:00
stgrabercking: right, both try to address the same problem in different ways. mjg59's patch simply rejects any write done when we're past 50% of used space and that's what actually prevents efibootmgr from doing its job on some systems. sforshee's patch is specific to the use of nvram for pstore and essentially disables the biggest source of nvram writes18:00
ckingstgraber, yep, i concur with that18:00
stgraberso it "should" be safe to turn off the 50% one on Ubuntu, though this may still lead to some bricks if for example you have too many secureboot keys being added or any similar thing18:01
ckingstgraber, we just need to make sure users now don't tidy up their uefi vars by deleting them all and bricking their machines :-/18:01
stgraber(it's a case where all solution sucks... the real solution is to get a fixed firmware on those machine that does proper garbage collection and doesn't blow up when the nvram is empty or full)18:02
ckingstgraber, indeed.  firmware sucks18:02
slangasekother issues: - efibootmgr doesn't output any error messages on failure; - grub-install doesn't capture the error code from efibootmgr18:02
ckingslangasek, yes, the silent fail is a big fail18:02
stgraberslangasek: right, I saw that on a machine and didn't even realize it was caused by the 50% thing... I (wrongly) assumed it was a bad firmware, I updated to the new one which fixed it (likely because it forced the garbage collector or freeed some nvram variables)18:03
stgrabercking: does the kernel at least log something when it refuses a write because of the 50% stuff? A dmesg entry would be kind of nice (on top of having the userspace tools return an error message)18:03
ckingstgraber, ideally the failed update should return an error code so apps can react to that, not sure about the kernel messages18:04
ckingsforshee, any ideas ^^18:04
* sforshee tries to catch up after returning from lunch18:06
sforsheestgraber, if writes are done via the raw_var sysfs attribute then there should be an error code and something in dmesg18:09
ckingsomething like efivars: set_variable() failed: status=.... ?18:10
ckingI think if it ends in 9 then you've run out of free spafe18:11
cking..and you get -EIO on a failed write I believe18:11
sforsheesome other paths don't print to dmesg, but they all ought to return errors18:13
stgrabersforshee: is there an easy way to special case the boot order variable?18:14
stgraberAll of ^Boot* actually18:15
sforsheestgraber, with the way the driver is today there are multiple paths by which the variable could be written18:16
sforsheestgraber, there are probably only a couple that matter though18:17
ckingultimately one is at the mercy of the firmware run time service to update the vars though18:17
stgraberyeah, my guess is that we always want BootOrder and BootXXXX so that we can setup the boot entry18:17
slangasekhmm, I think I've spotted a simpler explanation for bug #1170183; we'll see what the submitter comes back wiht.18:18
ubottubug 1170183 in grub2 (Ubuntu) "can not boot up in uefi secure boot mode unbuntu 13.04, can run in a live from cd uefi secure mode. will boot non secure boot mode" [Undecided,New] https://launchpad.net/bugs/117018318:18
slangasekstgraber: "special case" them how?  excluding them from the 50% restriction?18:18
stgraberslangasek: yep18:19
ckingand then risking bricking some machines?18:19
slangasekright - the machines that are affected won't care how much over 50% you are18:22
slangasekthe failsafe is there because we don't have a saner option18:22
slangasekso I think it's more important instead to fix efibootmgr+grub-install wrt error reporting18:22
=== Ursinha is now known as Ursinha-afk
* cking got kids to sort out - sorry, need to go18:23
stgraberand say what? sorry you can't use UEFI on that box because your firmware is crap, switch back to BIOS and try again? (I rechecked the post by Matthew and yeah, I agree we shouldn't write past the 50%. I had the hope it'd only apply to new variables but apparently not)18:24
ckingstgraber, essentially, yes, firmware is the limiting factor18:24
stgraberwould be nice if we could somehow detect that before wiping the user's harddisk...18:25
ckingeither it bricks (v bad) or won't install (annoying)18:25
slangasekstgraber: not "sorry your firmware is crap", but "sorry your nvram is full, here's some helpful advice on how to clean it up safely"18:26
sforsheeslangasek, do we have advice on how to clean it up safely other than "try rebooting a couple of times and see if that helps"?18:26
stgraberhmm, yeah, I guess we could recommend doing a firmware factory reset and reboot twice, that "may" help freeing up nvram space18:27
slangaseksforshee: well, what I had zyga do was "rm /sys/firmware/efi/efivars/dump*"18:27
sforsheethat's only going to help people who were running raring during development though18:27
slangasekthat's the only confirmed cause of too-full nvram so far18:28
slangasekand no, it's not raring-only... this problem was seen in quantal too18:28
slangasekmaybe raring's kernel is the only one with the 50% guard, but you could have already filled your nvram up by running quantal18:28
sforsheeah, that's right18:28
stgraberah, we had nvram backend pstore in quantal?18:29
stgraberif we did, I was extremely lucky not to brick my machine before the 3.8 kernel18:29
slangasekstgraber: yes, that's basically what was bricking the samsung machines18:29
zygaslangasek: did my email start any internal discussion about how to use nvram?18:30
slangasekzyga: no18:30
slangasekzyga: I asked you to file bugs :)18:30
slangasekzyga: but it sounds like the kernel team was already on the ball and patched out nvram pstore in raring... you just already had a too-full nvram by that point18:31
zygaslangasek: you are right, I should have filed them right away18:31
* zyga sometimes feels that with the swarm of bugs, a message to a mailing list works better to start a conversation about a diffucult topic 18:33
=== Ursinha-afk is now known as Ursinha
tjaaltonslangasek: i've pushed plymouth to ubuntu-x-swat/x-staging ppa19:01
tjaaltonwith the job19:02
slangasektjaalton: ok.  care to raise a branch mp to go with it?19:02
tjaaltonslangasek: I'd need to use bzr, that takes time :)19:02
tjaaltonchecking out19:03
slangasekactually, looks like the branch is out of date because infinity and the package importer both failed to update it19:03
slangaseklet me fix that19:03
tjaaltonyeah looks like it19:04
tjaaltonadded plymouth.plymouth-ready.upstart and dh_installinit line to rules19:04
slangasekbranch updated19:05
mlankhorstogasawara: what happens with armel for the enablement stack, is it explicitly unsupported?19:06
bdmurraywhere is the python-apt upstream? lp:python-apt is behind ubuntu raring19:06
ogasawaramlankhorst: it's not supported19:06
slangasek(well, modulo race condition with my shell not having returned yet from 'bzr push')19:06
slangasekbdmurray: 'debcheckout -a python-apt' should DTRT here I think19:06
tjaaltonhmm, bzr pull didn't do what I wanted?19:07
mlankhorstok good, I'll fix up mesa-lts-raring to not fail to build on armel, but I'm 90% sure it won't actually run19:07
slangasektjaalton: did you hit the race with me telling you it was done before it was (sorry)? :)19:07
tjaaltonslangasek: no, pulled afterwards19:08
slangasektjaalton: ok.  if it didn't do what you wanted, what /did/ it do?19:08
tjaaltonI'll just clone it again19:08
tjaaltonnot sure what happened, bzr diff looks messy19:08
tjaaltonooh, managed to push it too19:14
tjaaltonslangasek: so how to do the mp?19:15
tjaaltonoh there it is19:16
slangasektjaalton: ta19:42
bdmurraystgraber: there is a crash on errors that is only about isc-dhcp version 4.2.4-1ubuntu10.2 from quantal-proposed19:53
stgraberbdmurray: odd, the only actual source change in that SRU is the UDP checksum offload, but it's been taken as-is from RedHat and is used in all RedHat derivatives and in raring, so I'm quite surprised it only shows up in quantal-proposed19:58
bdmurrayWell it could be that the bucketing is too specific.19:59
bdmurrayah maybe its bug 104840320:00
ubottuError: Launchpad bug 1048403 could not be found20:00
stgraberthe stacktrace also doesn't show anything that's been touched by the extra patch20:00
stgraberif it was a bug introduced by the SRU, I'd have expected to see decode_udp_ip_header in the trace20:00
stgraberbdmurray: ah yeah, that looks pretty similar.20:01
stgraberbdmurray: it's actually the same guy that triggered both entries (look at the IPs in the trace, they're the same)20:02
bdmurraythanks for looking20:05
stgraberso yeah, I don't think we should worry too much about this. Typically isc-dhcp issues are a pain to figure out from coredump, as they're almost impossible to replicate.20:05
stgraberIf they guy ever gets around to reporting it on Launchpad and is technical enough, I'll ask him for a pcap of the DHCP traffic, with that it's then trivial to reproduce20:06
slangasekMirv: hey, so bug #1131636 (which should probably be duped to #1155327) has a claim now that QtWebkit 2.3.1 fixes the skype/nvidia/webkit regression... is there something here that you could maybe cherry-pick for us?20:11
ubottubug 1131636 in skype (Ubuntu) "After QtWebkit update Skype is not launching" [Undecided,Confirmed] https://launchpad.net/bugs/113163620:11
hallynis there a 'proper' command-line way to detect http proxies specified in apt.conf?20:23
slangasekhallyn: interesting question.  Why do you want them?20:24
slangasekhallyn: last time I tried to use "http proxy specified in apt.conf" for something that wasn't apt, google yelled at me ;)20:24
hallynslangasek: I'm looking for an intelligent deafult for containers20:25
slangasekhallyn: so you want to extract the setting from the host for provisioning the guest?20:25
hallynright now we support a MIRROR variable in lxc.conf, but it has been suggested that the /etc/apt/apt.conf/70-procy or wahtever is the way to go20:25
slangasekhallyn: 'apt-config shell'; cf. /etc/cron.daily/apt20:26
hallyn(thanks, looking)20:28
infinity(base)adconrad@cthulhu:~$ apt-config shell APT_PROXY Acquire::http::Proxy20:29
infinity^-- For example.20:29
infinity(And then just eval that)20:30
hallynof course, if people commonly do localhost (like you did), then that won't work.  but i guess i can autodetect that20:31
infinityIt's a pretty common setup for people with apt caches.20:31
dtchenyeah, it helps heaps with these test-rebuilds20:33
hallynright.  i do it - but i wasn't sure that meant others would :)20:33
hallynall right well i can just ignore it if its 127.anything20:33
hallyn(and still let MIRROR override it)20:33
hallynthanks again20:33
infinitydtchen: Oh, I didn't want to go rejecting things because an FTBFS patch that works is better than none at all.20:35
infinitydtchen: But you should try to avoid the layering violation of injecting DEB_HOST_MULTIARCH into upstream configure checks, etc.20:35
infinitydtchen: And instead push patches upstream to actually use the compiler to find things instead of fighting against it by guessing at paths.20:36
=== salem_ is now known as _salem
dtcheninfinity: noted20:36
=== wedgwood is now known as wedgwood_away
=== wedgwood_away is now known as wedgwood
=== _salem is now known as salem_
=== rickspencer3_ is now known as rickspencer3
=== Ursinha is now known as Ursinha-afk
=== salem_ is now known as _salem
mhoughcan anyone help me with the removal of libgoogle-glog-dev?22:55
mhoughthe launchpad info just doesn't make sense22:56
mhoughsaid removed for qa reason but the bug listed is for a different package/language22:56
ScottKmhough: Link22:58
mhoughif you follow the bug link does that make sense?23:00
cjwatsonmhough: Launchpad renders the link wrongly23:03
cjwatsonmhough: Try http://bugs.debian.org/66213723:03
ubottuDebian bug 662137 in ftp.debian.org "RM: google-glog -- RoQA; FTBFS, unackowledged" [Normal,Open]23:03
cjwatsonmhough: FWIW that was a largely automatic removal - we tend to track packages that have been removed from Debian unless there's some special reason not to (substantial Ubuntu modifications, remaining reverse-dependencies, present on one of the images we build, etc.)23:04
mhoughI see. Thanks for all the help23:05
sarnoldwhy was it only removed from precise and not oneiric, quantal, or raring?23:05
cjwatsonWell it clearly couldn't have been removed from quantal or raring since they didn't exist yet23:05
mhoughwhat is an RC bug?23:05
cjwatsonAnd we don't remove packages from existing stable releases23:06
cjwatsonrelease-critical (Debian term)23:06
sarnoldcjwatson: ah :) thanks23:06
cjwatsonLooks like it was later reintroduced23:07
cjwatsonSomebody picked it up and fixed the RC bugs23:07
cjwatsonBut nevertheless I think it's right to err on the side of not shipping packages that we may not be able to stand behind23:08
cjwatsonhttps://launchpad.net/ubuntu/+source/google-glog/+publishinghistory shows the sequence of events23:08
jbichabug 1151844 is interesting then23:08
ubottubug 1151844 in google-glog (Ubuntu) "[MIR] google-glog" [Undecided,Fix committed] https://launchpad.net/bugs/115184423:08
mhoughdoes that mean the package be readded?23:09
cjwatsonmhough: Yes, in >=12.1023:09
cjwatsonjbicha: Well, as I say, the package was fixed up and reintroduced in quantal23:09
jbichaoh never mind then :)23:09
mhoughthe maintainer of another package is asking me the best way for people to read the package to build his package on precise23:10
mhoughsorry re-add23:10
cjwatsonProbably easiest to put it in a PPA23:10
mhoughthe 12.10 version?23:10
cjwatsonIf that works23:10
cjwatsonIt would be extremely rare and exceptional for us to introduce (effectively) new packages in stable updates23:10
mhoughno I see that23:11
cjwatsonIt does happen but there'd have to be a driving reason23:11
mhoughprobably not for obscure DICOM package23:11
cjwatsonThat might be a tough sell23:11
ScottKIt could be added in backports.23:15
mhoughwell I don't mind adding it to a launchpad PPA to learn how to do that23:17
ScottK!backports | mhough23:17
ubottumhough: If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging23:17
mhoughbut if you think its worth adding it to23:17
ScottKupdated can also mean doesn't exist.23:17
ScottKYou're call.23:17
mhoughhopefully his package will be in neurodebian or med debian23:18
mhoughis orthanc there yet?23:18
cjwatsonhttp://packages.qa.debian.org/o/orthanc.html ?23:19
mhoughyeah I see in unstable sid23:19
cjwatsonIt's in raring too.  https://launchpad.net/ubuntu/+source/orthanc/+publishinghistory23:19
cjwatsonWe try to keep track of new packages as well as removals ;-)23:20
cjwatson(Actually rather better - that side is more fully automated)23:20
mhoughso would that justify libgoogle-glog-dev for a backport?23:20
cjwatsonIf you were backporting orthanc too, yes23:21
mhoughI see23:22
mhoughlet me see how it goes with them on my ppa first I guess right?23:23
* cjwatson gets the archive admin to-do list down to three long-term items (one in progress) and one removal pending verification by the server team23:24
=== wedgwood is now known as wedgwood_away

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