infinitydoko: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5244500:01
ubottugcc.gnu.org bug 52445 in tree-optimization "[4.6 Regression] conditional store replacement causes segfault in generated code" [Normal,Assigned]00:01
infinitydoko: There are a few long threads around arm-linux and other lists about how that bug causes some kernel driver miscompilations.00:01
=== cpg|away is now known as cpg
infinityNow, if only I could remember who it was who brought it to my attention a few weeks ago...00:02
=== fisted_ is now known as fisted
=== Guest5764 is now known as vibhav
=== vibhav is now known as Guest74795
=== Guest74795 is now known as vibhav
=== vibhav is now known as Guest65373
=== Guest65373 is now known as vibhav
=== vibhav is now known as Guest79079
=== Guest79079 is now known as vibhav
=== vibhav is now known as Guest84459
=== Guest84459 is now known as vibhav
cjwatsonjdstrand: Disabling normal.mod doesn't make sense.  That's the module that provides the menu.01:14
cjwatsonjdstrand: You should be able to copy /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed into your environment as grubx64.efi and execute it from firmware configured to trust the Canonical key (or via shim from firmware configured to trust the Microsoft key).01:16
cjwatsonjdstrand: Or, if you already have an installed system that you're booting in OVMF rather than trying to bootstrap one from scratch, install the grub-efi-amd64-signed package and run 'grub-install --uefi-secure-boot'.01:18
cjwatsonjdstrand: (I believe I have a work item to make that the default even on non-SB systems, with a few associated tweaks)01:18
cjwatsonjdstrand: And rereading, it sounds as though you probably want the latter approach.01:19
cjwatsonjdstrand: A message refusing to load normal.mod indicates that you've tried to sign a minimal GRUB image (perhaps the one generated by plain grub-efi-amd64) that's expecting to load much of its brain from /boot/grub/x86_64-efi/*.mod - but GRUB insmod is forbidden in secure boot because all the boot loader code must be signed.01:20
ShinobiThe only rdp client I can get to connect is rdesktop, none of the rdp clients I've tried in 10.10 will connect. Is there some library that I need to add or something?01:41
ShinobiSorry. None of the rdp clients with GUI front ends will connect. CLI is fine.01:42
ScottK10.10 is long out of support in any case.  This isn't a help channel, but certainly not for old releases.01:44
infinityShinobi: This isn't a support channel, try #ubuntu.  Also, 10.10 is an EOL product, you might want to try 12.04 (or later) before asking for help.01:44
infinityScottK: Jinx.01:44
Shinobiinfinity: Sorry. Nobody seemed to know in Ubuntu, so I thought I'd see if someone may have known. I plan to upgrade to 12.04 tonight.01:46
SpamapSShinobi: I seem to recall some serious bugs that were fixed somewhat recently in one of the other rdp clients01:56
=== Tonio_ is now known as Tonio_aw
jdstrandcjwatson: thanks-- let me try grub-install --uefi-secure-boot. I that sounds like the missing piece-- but you gave a lot of info I can play with. much appreciated02:54
jdstrandcjwatson: that was exactly it. perfect-o!03:08
jdstrandcjwatson: huge thanks. I'll fiddle with the other options later as well (ie, Canonical key, shim, etc)03:09
=== attente is now known as attente_zzz
pittiGood morning05:37
pittiinfinity: do you plan to do an initramfs-tools merge soon, or want me to ignore the warning in u-d-common for now?06:22
infinitypitti: I plan to merge tonight or (more realistically) first thing in the morning.  That eglibc upload I just did a couple of hours ago was occupying me.06:25
pittiinfinity: ah cool, thanks!06:26
infinitydoko_: Ugh.  Shouldn't there be a /usr/include/i686-linux-gnu to match the cross target, rather than i386-linux-gnu to match the Debian arch (or maybe one a symlink to the other)?06:43
infinitydoko_: Or maybe I get to special-case i?86 in glibc's configure and it won't be upstreamable.06:44
* infinity ponders.06:45
infinitydoko_: Yeah, all the stuff that used to be in /usr/include/c++/4.7/`g++ -dumpmachine` is now in /usr/include/$DEB_HOST_MULTIARCH/c++/4.7 which is subtly different on i386.06:48
infinitydoko_: Oh, I guess I can conditionally use g++ -print-multiarch and still have this upstreamable.06:52
* infinity kicks himself for only testing on amd64 and powerpc.06:52
infinitypitti: You wake up too early.  It always makes me thing (very incorrectly) that I can start talking to other Germans and expect a response. :P07:21
pittihah, hardly07:21
pittiinfinity: I usually start between 5:30 and 6:30 these days07:21
infinitypitti: I often stop around then...07:22
infinitySo, now that armel's out of the archive, can we get rid of i386 too?07:23
infinityI'm sick of its quirks.07:23
dholbachgood morning07:47
pittihey dholbach07:57
dholbachhi pitti07:57
=== smb` is now known as smb
dholbach@pilot in08:13
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
infinitydoko_: Alright, fix uploaded for glibc/i386, you can ignore my whining about dumpmachine versus multiarch.08:21
didrocksdholbach: hey, FYI, I'll have to swap my pilot timing for Thu/Fri I guess08:21
dholbachdidrocks, sure - I'll leave that to you - I split up my patch pilot session yesterday/today because there was no other way08:22
didrocksdholbach: ok ;)08:22
pittiDaviey: are you aware of the maas autopkgtest failure? It's reproducible locally as well (https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-maas/lastFailedBuild/ARCH=amd64,label=albali/)08:23
pittiDaviey: looks like a dependency or component mismatch issue08:23
=== agateau_ is now known as agateau
dholbachdidrocks, do you know if there's plans to get the new libnice from Debian experimental? it seems to be needed for bug 107899108:25
ubottuLaunchpad bug 1078991 in farstream (Ubuntu) "Sync farstream-0.2 0.2.2-1 (universe) from Debian experimental (main)" [Wishlist,Triaged] https://launchpad.net/bugs/107899108:25
infinitySetting up tgt (1:1.0.17-1ubuntu3) ...08:26
infinitystart: Job failed to start08:26
infinityinvoke-rc.d: initscript tgt, action "start" failed.08:26
infinitydpkg: error processing tgt (--configure):08:26
infinity subprocess installed post-installation script returned error exit status 108:26
infinitypitti / Daviey : That's your bug ^^08:26
didrocksdholbach: I didn't hear about any blocker on that, it seems it didn't change its soname, and have gstreamer 0.10 and 1.0 bindings08:27
didrocksdholbach: so if you want to test/sync… ;)08:27
dholbachwhy did Robert file a sync request for this and not just sync it?08:28
infinityMaybe he still lives in the past and no one's told him he can sync things?08:28
Davieypitti: i am now :).. thanks.  We'll get that fixed up today.08:29
didrocksdholbach: maybe he's not aware we can sync directly08:29
infinityCurious, tgt starts here just fine.08:30
pittiDaviey: great, thanks; I start prodding people now as soon this will become critical path, and you couldn't land uploads any more when their tests fail08:33
pittiI got a lot of them fixed, but I can't keep up with them all08:33
infinitypitti: Curiously, I can't make it fail locally.08:33
infinity(Not that I care terribly, cause I should be napping, but I figured I'd give it a try)08:33
pitti"run-adt-test -s maas" fails with the same reason08:34
infinitypitti: Sure, I was just installing the package that failed to start, rather than running the full test environment.08:34
infinitypitti: Perhaps it fails to start because the daemon relies on a recent kernel?08:35
Davieypitti: well, fixing it directly in the archive wouldn't last.. as this package is strictly managed via bzr.08:35
pittiinfinity: the kernel in the VM is just as recent as raring is08:36
infinityWas just a thought, since I can't make it die in a quick test here.08:38
pittimvo: do you happen to understand the metaclass magic in aptdaemon in https://code.launchpad.net/~pitti/aptdaemon/pygobject-fixes/+merge/134942 ?08:41
pittimvo: I wondered if it can/should be fixed, or just dropped completely for simplicity08:41
pittiinfinity, Daviey: "sudo apt-get install tgt" in a VM reproduces it well08:43
pittiI'll file a bug with the details08:43
infinitypitti: Right, it's the "in a VM" bit I'm missing here. :P08:43
infinitypitti: Worked fine in a chroot on bare metal, which is curious.08:43
pittiDaviey: I filed bug 1081495 with the output of tgtd08:46
ubottuLaunchpad bug 1081495 in tgt (Ubuntu) "E: Sub-process /usr/bin/dpkg returned an error code (1)" [Undecided,New] https://launchpad.net/bugs/108149508:46
infinitypitti: Oh, out of curiosity, do you have autopkgtests for eglibc, binutils, and gcc?08:46
pittiinfinity: no, we don't08:46
pittiinfinity: well, the new eglibc triggered all autopkgtests that we have of course08:46
pittiso we do rdepends check08:47
pittibut not for eglibc itself08:47
infinitypitti: I'd suggest (since things like "try to rebuild the whole archive lololol" would be pointless) they their tests should consist of each one triggering a rebuild test of the other two.08:47
infinitypitti: If upgrading any of those three manages to keep the testsuite of the others passing, that's a win.08:47
pittiinfinity: i. e. the test script woudl more or less be "apt-get build-dep binutils; apt-get source -b binutils", right?08:48
infinitypitti: (This came up today after I just spent hours fixing a regression in glibc due to the new gcc, and the inverse happens all the time too)08:48
infinitypitti: Yeahp.08:48
infinitypitti: Oh, and linux-libc-dev (so, the linux source package) should also trigger those three to a rebuild test, same reason.08:49
infinitypitti: If linux-libc-dev's headers survive the GCC and glibc testsuites, they're good enough for regular users. :P08:49
infinity(And if they break regular users but not the toolchain, I'd humbly suggest the users are wrong)08:49
infinityDefinitely would have been nice to know when gcc and the kernel were uploaded (so, a couple of weeks ago) that they broke glibc, instead of finding out today while I was uploading for other reasons.08:52
infinityBut, yeah, toolchain rdep testing needs to have some sane limits, cause I assume our resources aren't infinite (and our time certainly isn't, when we start plugging this in as a britney blocker)08:53
pittiso binutils seems to have a proper Vcs-Bzr:; gcc-4.7 is just apt-get source/UDD?08:53
infinitypitti: apt-get source is the only "proper" way to get any of them for a rebuild test...08:53
pittiinfinity: yeah, bintuils and glibc tests are bearable, but gcc does take some time08:53
infinitypitti: We don't want to know if something staged in a VCS is broken, we want to know if the archive is.08:53
pittiinfinity: no, I mean for adding the autopkgtests08:54
pittithese need to go into their source08:54
infinitypitti: Oh.  These end up in the source package themselves?08:54
infinitypitti: Right, forward the binutils and gcc ones to doko, the eglibc one to me, and the linux one to apw, then.08:54
infinitypitti: I'd rather have a modicum of control over how often toolchains get uploaded for non-critical things. :)08:54
pittiyeah, I wasn't going to upload them just for that, hence I was looking for the VCSes08:55
infinityRighto.  eglibc's VCS header is a filthy lie, I need to fix that.08:55
infinityAnd no idea about doko's.08:56
infinityAnd the kernel's isn't a lie, but you can't commit to it. :P08:56
infinitypitti: To cut down on the pain, we could potentially refine the tests to do something like only build a single pass of libc6 and run the tests, only build a single kernel, etc.  Most of these things take so effin' long cause they build 4 times.08:57
pittilet's put that into a bug to keep track of the status and have a place to attach patches to08:58
infinityBe my guest.  I'm thinking a nap at 2am might not be a bad plan.08:58
* infinity snickers at jcm getting flooded off freenode.08:59
infinitypitti: If you file a big meta bug, can you toss me the number?  I suck at bugmail filtering about as much as someone who doesn't put much effort into filtering bugmail.09:00
infinity(I should probably fix that some day)09:00
pittiinfinity: bug 108150009:01
ubottuLaunchpad bug 1081500 in linux (Ubuntu) "Add autopkgtest for mutual rebuild-testing amongst glibc, linux-libc-dev, gcc, and binutils" [Undecided,New] https://launchpad.net/bugs/108150009:01
infinitypitti: Great.  I look forward to patches that teach me all about autopkgtest by example. ;)09:02
pittiinfinity: http://developer.ubuntu.com/packaging/html/auto-pkg-test.html :09:03
infinityI don't accept HTML patches.09:03
pittinah, I'll send a first one, and maybe a second09:04
pittiI expect they will look pretty much alike, except for the "only build one flavour" bit09:04
infinityThe only one flavour bit may take some refinement.09:04
infinityThe kernel's pretty good at it (you can call individual targets out of debian/rules), glibc might actually take some wrangling to convince it to try.09:05
infinityI'm happy to do that bit myself. :P09:05
infinityAnyhow, nap time before morning meetings.09:06
pittiyeah, once we enable those on armhf, any speedup will be greatly appreciated09:06
infinityGah, and that override bug.09:07
* infinity promotes kernels to main before going to bed.09:07
lifelessgood times09:07
lifelessinfinity: what TZ is infintytime aligned with atm ?09:08
pittilifeless: all of them :)09:08
infinitylifeless: I reside in MST7MDT, I'm currently awake in... Actually, close to that.  It's only 2am.  Not a horrible bedtime.09:08
lifelesspitti: I think that would get a dividebyzero error :)09:09
=== Tonio_aw is now known as Tonio_
=== Tonio_ is now known as Tonio_aw
cjwatsonjdstrand: cool09:43
=== Tonio_aw is now known as Tonio_
infinitycjwatson: Having to override all the kernels in raring again after britney promoted them reminded me to be annoyed by that bug.  Did you have something filed for it?09:46
infinitycjwatson: (Still wildly confused by why this happens for proposed->release but not proposed->updates, unless britney's somehow copying differently than sru-release does...)09:46
=== Sweetsha1k is now known as Sweetshark
cjwatsonI don't think I filed one09:47
cjwatsonI was just doing morning "oh, images failed, oh look, component-mismatches"09:47
cjwatsonBut the output suggests you beat me to it09:48
infinityYeah, c-m is a lie, I already fixed.09:48
infinityThankfully, you didn't notice until the publisher started. :P09:48
infinityThat double-override-eats-binaries bug is also a lovely one.09:48
infinityAnd likely to get stumbled on a lot while this current "oops, I forget everything during migration" business is going on and people scrable to fix the release pocket.09:49
cjwatsonOverriding twice to main doesn't count, though, since that doesn't actually produce new pubs.09:49
infinityEven if it was previously in universe?09:50
* infinity is unfamiliar with that bit, and is suddenly happy he is.09:50
cjwatsoninfinity: By the time of the second override attempt, it's now in main so doesn't get re-overridden.09:54
cjwatson(Sorry, I was busy trolling a phone scammer.)09:55
didrockshey cjwatson, it's been 10+ minutes I tried to copy 3 components from the ubuntu-unity ppa to the archive, and it seems the first attempt failed :/ any way to see what happened?09:57
dholbachtkamppeter_, hello - do you think you can have a look at https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1069324 and see if you can upload the patch?09:58
ubottuLaunchpad bug 1069324 in hplip (Ubuntu) "diagnose_queues.py crashed with NameError in su_sudo(): global name 'utils' is not defined" [Medium,Triaged]09:58
infinitydidrocks: If it failed, you should have gotten an email with an OOPS in it.  Maybe.09:58
didrocksinfinity: the thing is that the bot is https://launchpad.net/~ps-jenkins and it's a ML. But mmrazik isn't around to check them09:58
infinityThere's a bot auto-copying from PPAs to the archive?09:59
cjwatsoninfinity: Yeah, didrocks and I agreed on this09:59
infinityFair enough.09:59
cjwatsondidrocks: Package name?09:59
didrockscjwatson: indicator-sound, indicator-power and indicator-messages10:00
cjwatson"Cannot copy DDEBs to a primary archive"10:00
didrocksah, so we need to ask for removing the ddebs from the ppa10:01
didrocks(would have been useful for the autopilot crash though)10:01
pittiinfinity: actually, didn't we want to enable that for the main archive?10:01
infinitypitti: We do, yes.  Hit me up tomorrow, and we'll talk. :)10:01
didrockslike if autopilot crashed with a stack, we would use those ddebs to debug10:01
cjwatsonNothing would take care of rebuilding the ddebs for the main archive, if you remove them10:01
infinitydidrocks: It's a devirt PPA, right?10:01
pittito replace those apache servers10:01
cjwatsonWhich would mean that errors.u.c will be unable to display useful tracebacks for those packages10:02
infinitycjwatson: No need to rebuild them.  The trick is to do the same thing the kernel PPA does.10:02
didrocksinfinity: yeah, it's building on all archs10:02
pittiinfinity: I thought you wanted to go to sleep an hour ago :)10:02
infinitycjwatson: Which is to act like the primary archive.10:02
didrockscjwatson: right, but the tests are runned before copying to the main archive, so being able to debug there was useful10:02
infinitycjwatson: IOW, not have the flag on that publishes ddebs in .changes10:02
mitya57dholbach, I've already asked him to do that :)10:02
dholbachmitya57, ok, perfect :)10:02
cjwatsoninfinity: And they then get picked up for ddebs.u.c?10:03
cjwatsonPresumably as long as versions never clash.10:03
infinitycjwatson: Sure, they're all slammed in public_html.10:03
infinityThe real solution is some JFDIing by pitti and I to switch this all over.10:03
didrockshow does the kernel do to have ddebs?10:03
didrocksas it's not rebuilt10:03
infinityAnd then scour the world for PPAs that do weird things and make them do what didrocks's does.10:03
infinitydidrocks: The kernel's PPA acts just like the primary archive.  It builds ddebs, but doesn't upload them.10:04
infinitydidrocks: And they get scraped off the buildds by pitti's evil script, the same as they are for the primary archive.10:04
pitticjwatson: we'd eventually like to stop having to stage them on the buildds for 7 days and those rather unreliable apache servers to publish them; I'd much rather pull them from the librarian10:04
didrocksinfinity: ah, ok, so evil hack :)10:04
infinityBut yes, we should fix all of this hackish crap.10:04
cjwatsondidrocks: In infinity's proposal, you'd debug by getting the ddebs from ddebs.ubuntu.com instead.10:04
infinityMy proposal is the "right way" to do things today.10:05
infinityIt may not be in a few days, if pitti and I get some ducks in a row.10:05
pittiwell, ddebs.u.c. would continue to only publish Ubuntu ddebs; but copying packages from PPA into the ubuntu archive shoudl copy the ddebs along?10:05
infinity(The right way to do things if your PPA is essentially an extension of the primary archive, like kernel and security are)10:05
cjwatsonpitti: In some new world order that might be possible, sure.  I'm aware of the plans.10:06
infinitypitti: Yeah, in the new world order, ddebs would be attached to build records, and copying with binaries will get the ddebs too.10:06
dholbach@pilot out10:06
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
infinitypitti: That part looks like it might need an LP patch, but likely just removing a check.10:06
infinity(We probably also need to test and make sure that the publisher doesn't try to vomit ddebs on disk when they show up in the primary archive)10:07
infinityI guess I might need to dust off a local LP instance tomorrow, since I don't have dogfood to play with. :/10:07
infinityAaaanyhow.  pitti's right, I'm supposed to be asleep.10:08
didrockshow can I help to make things happen? :)10:08
infinitydidrocks: Depends on which things.10:08
pittising "soft kitty" to infinity, so that he gets to sleep, and is awake tomorrow? :-)10:08
didrockspitti: can do that :)10:09
* infinity might not appreciate this so much.10:09
didrocksinfinity: I'm not really familiar with the whole copy to ddeb.u.c process, but if you think I can be of any help10:09
cjwatsoninfinity: Better to construct a unit test that exercises it, since you'll want one of those to go with any change anyway.10:09
=== tkamppeter_ is now known as tkamppeter
infinitycjwatson: Sure, this doesn't preclude the value of doing actual end-to-end testing to make sure it does what you think you claim the unit test is testing.10:10
cjwatsondidrocks: For the meantime, you could copy without binaries.  I know that strictly that partially invalidates your testing, but confirming that the source builds sensible binaries in autopilot is still a lot better than nothing.10:10
didrockscjwatson: well, if it's just a question of days, I think I'll better to wait10:11
infinityOr, he could ask webops to twiddle his PPA to make it look "like the kernel team's".10:11
tkamppeterdholbach, I can do so. Simply for Raring or as Quantal SRU?10:11
dholbachmitya57, ^?10:11
infinityBut if you do that, you need to trat it like the primary archive, never reuse version numbers (even if you delete something), etc.10:11
infinitydidrocks: It could be more than days to get this all tested and sane.  I'm not about to commit.10:11
infinitydidrocks: But it's seconds to make your PPA behave differently.10:12
didrocksinfinity: I already do that, depends on the timing for the "proper fix" in your mind10:12
didrocksinfinity: ok, so right now, asking webops to twiddle the PPA seems to more robust idea?10:12
mitya57tkamppeter, it would be good to have this SRUed if you plan a SRU, otherwise I don't think it's worth that10:12
didrockswaiting for the real fix?10:12
infinitydidrocks: Either that or, as Colin suggests, copying source-only.10:12
infinitydidrocks: But the kernel PPA method DTRT for now.10:13
didrocksI'm not confortable with that, as we won't have in proposed the real stack/build order we tested10:13
infinitydidrocks: Where "the right thing" is "exactly the same awful hack as the primary archive".10:13
didrocksinfinity: yeah, I understood that ;) do you have anyone in mind knowledgeable about it in IS?10:13
cjwatsonDon't do that, ask webops.  It's an alias.10:13
cjwatsonDuty admins highlight on it.10:14
didrocksok, doing so :)10:14
cjwatson(#launchpad-ops, internal)10:14
didrocksthanks cjwatson, doing that right now :)10:14
infinitycjwatson: Actually, they prefer #webops.10:15
cjwatsonAh, that works too10:15
didrocksah, too late :)10:16
mitya57hi barry10:18
mitya57barry: do you know python's cElementTree code? If yes, maybe you can take a look at http://bugs.python.org/msg175235?10:19
mitya57(this is cause of debian bug 692285)10:20
ubottuDebian bug 692285 in src:python-docutils "python-docutils: FTBFS with Python 3.3: TypeError: must be Element, not _ElementInterfaceWrapper" [Important,Open] http://bugs.debian.org/69228510:20
infinitydoko_: Oh, for the love of... How am I meant to divine the mystery path for the multilib c++ includes?  *sigh*10:42
mlankhorstgcc -v?10:43
infinityYeah, I was avoiding using the whole output of gcc -v, since it includes paths I might not want.10:43
infinityNot much point in using nostdinc if you then end up appending all of stdinc's paths to your call.10:46
mlankhorst  gcc -print-file-name=include10:47
infinityWrong one.10:47
infinityAre there others? :P10:47
infinityWhat I'm after is /usr/include/c++/4.7 /usr/include/c++/4.7/backward /usr/include/x86_64-linux-gnu/c++/4.710:47
infinityThat last one is a bitch to construct for multilib builds.10:48
infinitySince it ends up as /usr/include/x86_64-linux-gnu/c++/4.7/32 or /usr/include/x86_64-linux-gnu/c++/4.7/x3210:48
infinityRather than using the target triplet.10:48
infinity(I suppose to avoid clashing with the multiarch version of same)10:48
mlankhorstg++ -E -x c++ - -v < /dev/null10:49
infinityYes, I know.  That's where I copied and pasted the above from.10:50
infinityBut the list also includes things I don't want.10:50
mlankhorstyeah :/10:50
infinityIf I could guarantee the top three were always the ones I want, I'd go with that.10:50
infinityBut I'm not sure that's a sane assumption.10:50
infinity(Though currently true)10:51
mlankhorst|grep c++ ? :P10:54
infinitymlankhorst: Well, that's definitely correct today.  Almost certainly not upstreamable.10:54
infinitymlankhorst: But meh.  For now, it might do.10:54
mlankhorstwhat are you trying though10:55
mlankhorstand if it's meant for upstream, you could just add a -dump-includes to gcc or something10:55
infinityHrm?  This is the glibc test suite.10:55
infinityWhich worked fine in hackish ways until doko's new gcc.10:55
mlankhorststill, could be better in long term to just get it over with and add it, even though that menas dealing with gcc coding style..10:56
* mlankhorst shivers10:56
=== pcarrier_ is now known as pcarrier
infinityAhh, -print-multi-directory gets me that...11:00
cjwatsonHmm, has libnss-files started to autocreate /etc/{protocols,services} or something?11:00
infinityExcept I can't get the multiarch dir in the same invocation, cause that ends up wrong.11:00
* cjwatson is trying to debug chroot weirdness11:00
infinitycjwatson: No, schroot copies those in unless you tell it not to.11:00
cjwatsonOh is *that* it11:00
cjwatsonOK, thanks11:00
infinity /etc/schroot/default/copyfiles11:00
infinityOr, no. /etc/schroot/default/nssdatabases11:01
infinityThat one.11:01
infinityAnd in mine, #services and #protocols are commented out. :P11:01
pittididrocks: ^ please try the "soft kitty" approach :)11:01
infinityLikely due to debugging a weird unreproducible "should have build-depended on netbase" build failure.11:01
cjwatsonRight, that explains rather a lot of failures any time netbase gets upgraded.11:01
cjwatsonOr rather, installed, since it isn't in the base.11:02
didrockspitti: yeah, it seems that's really needed, he will never stop! :)11:02
=== Quintasan_ is now known as Quintasan
infinitypitti: WRT your reverse-dep analysis, note that any of those packages having build-deps on each other is purely due to versioned build-deps (which can, and often do, go away).11:08
infinitypitti: Since all of those packages are build-essential, they don't need to be in build-deps at all. :P11:08
pittiinfinity: right, I was mostly checking how the current deps would work wiht our current parser11:09
infinitypitti: I suspect that relying on rdep triggering to always work for that set is either asking us to always carry build-dep cruft (which seems wrong), or just being naive. :)11:09
cjwatsoninfinity: are services and protocols the only ones you have commented out there?11:10
pittiinfinity: I'm just discussing that with apw11:10
pittiinfinity: we can probably introduce an XS-Test-Depends: field or something like that11:10
infinitycjwatson: Yeah, none others have caused me personal grief.11:10
cjwatsonOK, great11:10
* cjwatson tweaks his charm11:10
pittiinfinity: problem is that debian/tests/control isn't exposed in the apt indexes, so we cannot trigger on changes of pure test dependencies right now11:10
pittiinfinity: (mind you, this is stretching what autopkgtest was designed for quite a lot, so we need to make up things here)11:11
pittiinfinity, apw: of course we could also just special-case those four pacakges and hardcode their mutual trigger dependencies in our scripts11:11
infinitypitti: That was sort of what I was suggesting when I brought it up.11:12
infinitypitti: I thought it would be something server-side, not in the packages.11:12
apwXS-Testsuite-Depends: i suspect if we do it there11:12
pittiwe still need to add the actual tests to the packages11:12
infinityYeah, we need the tests in packages, I'm fine with that.11:12
infinityDoes anyone in Debian use this stuff (ie: is it upstreamable without annoying people with "useless cruft")?11:13
pittiinfinity: no, the tests themselves should be in the packages, but I'm ok with hardcoding the depends set for this particualr "mini rebuild test" case11:13
pittiinfinity: yes, we upstream a lot of tests11:13
infinityAlright, cool.11:13
pittithey are supposed to run in http://jenkins.debian.net/ at some point11:13
pittiinfinity: dep-8 is a Debian standard, after all :)11:13
infinityThe only slight problem with hardcoding the set is that one of these four packages keeps changing its name.11:13
* infinity glares at gcc-X.X11:13
pittiinfinity: ah, if only there was some way of expressing that with a pattern or so..11:14
pitti"regular patterns" or "globby expressions" or so11:14
infinitypitti: Well, but if you express it as a regex, you just triggered a rebuild of ALL gcc versions in the archive, when that may or may not be what we want.  Actually, maybe it would be.11:14
infinityBut we wouldn't want the inverse.11:15
infinityThat's the problem.11:15
infinityWhen gcc-4.5 revs (if it's still in the archive, too lazy to look), we don't care that it can't build the kenrel and glibc properly.11:15
pittiinfinity: anyway, hardcoding this in the scripts requires manual maintenance anyway; having to change it with each new compiler version isn't that big of a deal11:15
infinityNor do we care if gcc-4.8 can't do either of those things.11:15
pittiinfinity: but it can parse the defualt version from the "gcc" metapackage11:15
infinityBut we do care if glibc makes gcc-4.8 worse.11:16
infinitypitti: If only it were that simple. ;)11:16
infinitypitti: (Last cycle, the default gcc was 4.7, but glibc was built with 4.6, not sure what the kernel used)11:16
apwso the source packages expressing that works no?11:16
infinityapw: Yeah, expressing things in the source package might make more sense.11:16
apwas i am saying linux -> gcc-4.711:16
pittiinfinity: but that's fine -- glibc would then have a gcc-4.6 build dep, and the normal reverse dep parsing would kick in11:16
infinitypitti: Oh, fair.11:17
infinityI think I'll skip on the brown-paper-bag glibc upload tonight and finally go nap.11:17
infinityAnd fix this in the morning with an ugly non-upstreamable hammer.11:18
infinityAnd die a little inside.11:18
apwpitti, so i think you are saying the following is enough: http://paste.ubuntu.com/1374603/11:18
pittiapw: looks good, except that we don't implement XS-Testsuite-Depends ATM11:19
=== _salem is now known as salem_
pittiapw: and in fact we might not use that yet, as it's not covered by DEP-811:19
pittiapw: I think we should start with hardcoding those11:19
infinityapw: And if that header actually worked, you'd want binutils in there too.11:19
apwinfinity, i think i already dep on that in reality, so its ok11:19
pittinot needed, linux-source pulls in binutisl11:19
apwthough it might be clearer indeed11:20
infinityEh.  While it's okay that there's an implicit one, I'd prefer being explicit.11:20
infinity(Thinking of my specific glibc use-case where build-deps come and go more often than people I date)11:20
pittiwell, if no part of linux depends on eglibc, do we actually need to test that then?11:21
infinitypitti: I'm trying to sort out what that header will mean.11:21
apwi am expecting to need to test eglibc will still build after linux publishes11:21
infinitypitti: Is it "when this is upgraded, test these" or "when these are upgraded, test this"?11:21
apwas it consumes my binary packages11:21
pittiinfinity: the latter11:22
infinityapw: Yes, I want to test eglibc when linux-libc-dev lands.  The inverse isn't necessary.11:22
pittibut as I said, I wouldn't add this new header just yet11:22
pittiand instead put that into lp:auto-package-testing for now11:22
pittiwe can clean it up when it works and we can convince Debian to adopt the header into DEP-811:22
pitti(and Debian's autopkgtest)11:22
infinitypitti: Oh, and as to the DEB_BUILD_OPTIONS=whatever thing, that would probably be a DEB_BUILD_PROFILE in the new world.11:23
infinityDEB_BUILD_PROFILE=autopkgtest or something.11:23
pittiWFM :) I just wanted to take a variable taht already exists11:23
apwpitti, ok so i'll add it commented out so we remember11:23
infinityYeah, this is precisely why DEB_STAGE was changed to DEB_BUILD_PROFILE, so it could be genericized into a "mangle your build order/output" thing.11:24
apwpitti, when you are expressing those, linux-libc-dev only ever comes from linux11:24
pittiinfinity: it should be "rebuild-test", not "autopktest", IMHO (we'd want that for the full rebuild tests too, I think)11:25
apwpitti, so DEB_BUILD_PROFILE=autopkgtest or DEB_BUILD_PROFILE=rebuild-test11:25
pittiapw: right, but we'd set that in lp:auto-package-testing globally then11:25
apwindeed, just adjusting my support within the package11:26
pittia package can't set the environment in autopkgtest11:26
infinitypitti: I dunno.  A full rebuild test should just be a normal build.11:26
infinitypitti: (My current glibc build failure wouldn't be a failure if I wasn't building the second pass, actually) :P11:26
apwinfinity, i am proposing to use it to build just the first flavour on each arch11:27
apwinfinity, for the autopkgtest case11:27
infinityapw: Right, which is why I think it's wrong for it to be for "all rebuild tests".11:27
pittiso if it's wrong for the "all rebuild tests", how is it not wrong for the "mini rebuild test"?11:27
infinitypitti: It's a speed-versus-accuracy tradeoff.  The "right" thing to do when uploading a new toolchain is to rebuild test the whole archive before we let the toolchain in.  We're not going to do that, cause we'll get lynched.11:28
infinitypitti: So, autopkgtest as a blocker to migration needs to hit good test coverage without being too heavy.11:28
infinitypitti: A full rebuild test is async, and can be as heavy as you want.11:29
pittiwell, except that it still takes like a month on arm :)11:29
infinityNot true.11:29
infinityThe last time was because buildds kept ABORTing every few minutes.11:29
infinityThe time before that, armhf finished before amd64.11:29
doko_infinity, g++ -E -x c++ - -v < /dev/null | fgrep /c++/11:29
infinityPeople have short memories.11:29
infinitydoko_: Yeah, I was going to settle on the grep c++ solution.11:30
infinitydoko_: Is that guaranteed to always only be the internal includes?11:30
pittiapw: oh, and you might want to add a bug ref to #1081500 to the commit ?11:30
infinitydoko_: Like, in an unstreamably reliable way?11:30
doko_ig glibc is that backward, it even includes the backward headers11:30
apwpitti, will do11:30
doko_bug 108150011:30
ubottuLaunchpad bug 1081500 in linux (Ubuntu) "Add autopkgtest for mutual rebuild-testing amongst glibc, linux-libc-dev, gcc, and binutils" [Low,Triaged] https://launchpad.net/bugs/108150011:30
apwonce you lot hash out what the DEB_PROFILE is going to be11:30
infinitydoko_: It might not actually need the backward ones, but it does need the tricky-to-construct arch-path ones. :P11:31
infinityapw: Doesn't matter, we can change it once guillem tells us we're wrong.11:32
pittiapw: so DEB_PROFILE=autopkgtest WFM at the moment11:32
infinity /11:32
apwifeq ($(DEB_BUILD_PROFILE),autopkgtest)11:32
infinityapw: I bet you're having a good laugh now about having implemented all that do_* stuff reusably. :/11:33
* infinity suspects he's going to have to take some dull scissors to glibc to make this work.11:33
xnoxifneq (,$(ADTTMP)) ?11:33
apwinfinity, i am feeling somewhat smug at having rejected those original crosscompile patches about 4 times before implementing them right indeed :)11:34
apwpitti, so i guess are you happy enough for me to push these to our package for the next upload ?11:34
pittiapw: sounds good, thanks! I'll commit http://paste.ubuntu.com/1374628/ then11:35
apwexpect carnage in the next upload :)11:37
pittiapw: so the next linux upload would trigger a binutils autopkgtest, provided that we get the binutils test in by then11:38
pittiapw: if that works, I can add the remaining "virtual" dependencies, so that the next upload will trigger all three11:38
apwpitti, and presumably its own build test too11:38
pittibut let's start small first11:38
pittiapw: right11:38
apwindeed small please11:38
infinitypitti: Hrm, I guess this would be something I could add to glibc tomorrow as well, so my brown-paper-bag comes with the frills of at least some other change. :P11:38
pittiinfinity: yeah, hides much better in a changelog that way :)11:39
infinity(Though mine won't do the "only one flavour" thing straight away)11:39
didrockscjwatson: infinity: it worked \o/ Thanks a lot :)11:39
pittiinfinity: so that should be http://paste.ubuntu.com/1374603/ with the obvious debian.master/control.stub.in → debian/control11:40
infinitydidrocks: NP.11:40
pittiinfinity: and dropping the XS-Testsuite-Depends thing11:40
* infinity is curious about needing a fake test to trigger a rebuild, but whatever.11:40
infinity(I know why, it just feels a bit inelegant)11:41
doko_infinity, if you have other suggestions for the path, I'm fine, but the current location wasn't good enough for multiarch11:41
pittiinfinity: this actually is intended for building the tests that you are about to run11:41
pittiinfinity: this is just abusing this to provide a rebuild test :)11:41
infinitypitti: Well, because our rebuild also happens to run tests, so this makes some sense.11:42
pittiinfinity: but if we can run the built test suite against the installed glibc, this would be the intended (and ideal) case11:42
apwpitti, it would be nice perhaps if you could just have Tests: <empty>11:42
infinitydoko_: Yeah, I'm not sure I have better ideas.  The mixing of both multiarch and multilib on the same path just hurts a bit.11:42
=== Tonio_ is now known as Tonio_aw
pittiapw: that might or might not work, I haven't tried11:42
infinitypitti: You mean after installing the one we just built?  Cause running it against the archive one is almost pointless.11:43
pittiinfinity: no, running it against the archive one is the whole idea of autopkgtest11:43
infinitypitti: Yes, but pointless in THIS case.11:43
infinitypitti: Cause we're trying to see if a new toolchain misbuilds everything.11:43
pittiin the context of a rebuilt test11:43
infinitypitti: I agree that detached testsuites are handy for other things.11:44
infinityAlso a pain in the ass to do to some larger suites. :/11:44
pittibut it's a good thing in its own right11:44
infinity(We did it a ton at Nokia/Maemo, cause they also had an out-of-package-run-against-installed-packages test harness)11:44
infinityThe telepathy suite was very violently mangled to make this work.11:45
apwpitti, i guess the sort of thing our real package test should do is check that the abi does not change11:45
infinityNot my finest work.11:45
apwpitti, as in check that the rebuild abi matches the binary packages we have in the archive11:45
pittiapw: right, or integrate your existing tests to run in autopkgtests (file system tests and what not)11:46
* apw shudders11:46
pittiapw: do we ship the abi files?11:46
apwpitti, yep11:46
infinitypitti: Yes, but not in the source that produced them.11:46
infinitySo, the test needs to grab the debs from the archive to compare.11:46
infinityWhich isn't hard, just a bit weird.11:47
apwinfinity, well i should be able to make the test build-dep: on the kernel binaries11:47
pittiwell, the kernel is already installed11:47
pittithe files should be "just there"11:47
infinitypitti: Oh, I suppose there's that.  If it's the same flavour that Andy builds. :)11:47
apware all my binar spawn installed then ?11:47
pittiapw: all build, binary, and test depends are installed11:48
pittiand of course whatever is in a base system (currently the cloud images)11:48
apwok so we can depend on the real binary generated packages if we need them11:48
infinityRight, so just test-depending on all his kernel images would get him all his ABI files.11:48
pittiyou still need to check the installed kernel version of course, as the -proposed one might bump api11:48
infinityYeah, hence the test-depends, cause that could be exact versions.11:49
infinityNo guesswork.11:49
apwsounds 'awsome' :)11:49
pittiapw: debian/tests/control: Depends: @11:49
pittiwill install all binaries produced by that source package11:49
pitti(which is in fact the default if you don't specify anything)11:49
apwoh great, so it'll just be there11:50
infinityWhat if the source produces conflicting binaries?11:50
pittiyou lose and can't use @11:50
infinityI guess autopkgtst just explodes until you specify it?  Check.11:50
pittiyou can split your test and set different depends: for each of them11:50
pittiinfinity: yes, it'll fail with a package installation failure11:50
* infinity nods.11:51
pittimuch like maas' test11:51
pitti(in which case it's a legitimate failure)11:51
infinitydidrocks: Alright, I'm ready.  Soft Kitty me.  Do it.11:51
infinityFriggin' 5am.11:51
pitti♩ soooft kitty, waaarm kitty, little ball of fur ♪11:51
cjwatsondidrocks: Oh good11:52
didrocksinfinity: :)11:57
didrockscjwatson: rerunning for checking that it's skipping part of the stack now, added the cron to lillypilly and we should be fine! :)11:57
cjwatsonIs this in cu2d/ ?11:58
cjwatson(BTW you know the singular of "series" is also "series", right? :-) )12:00
doko_infinity, but g++ in eglibc is only needed for the tests, not the build, afaik12:02
infinitydoko_: Yep.  I'll fix this when I wake up, using your grep suggestion.12:03
infinity(Well, paring down the whole thing to be saner and upstreamable too)12:04
infinityNap time.12:04
didrockscjwatson: right cu2d :)12:04
didrockscjwatson: hum, I powndered, I'll fix it :)12:04
doko_I think I won't upstream the gcc patch upstream12:04
infinitycjwatson: I might not be at the meeting in the morning for the team I'm only sort of a part of.  Just pretend I'm American and took the week off.12:05
didrocks(english is confusing)12:05
cjwatsonMm, I suspect we'll have a low turnout12:05
cjwatsondidrocks: In this case I blame Latin.12:05
infinitydoko_: Well, I'm upstreaming the glibs bits cause I don't want to carry it.12:05
didrockscjwatson: :)12:07
=== tiagohillebrandt is now known as tiagoscd
=== fisted_ is now known as fisted
didrocksindicator-sound as well autolanded and other project ignored :)12:19
pittididrocks, jibel: congrats! this is awesome12:20
didrocksthanks a lot to jibel :)12:20
pittiwill there be sane version numbers at some point, at the end of the release?12:20
didrockspitti: the goal is to have a simple version number before "daily"12:21
didrocksthen, it's <number>daily12.11.2112:21
pittiso you want to do away completely with upstream releases?12:21
didrocksthere, the added .1 is because I had to rerun it ^ (I hopefully took care of this case)12:21
didrockspitti: once a cycle I would say12:21
didrockslike, at the end12:22
didrocksbut it's up to upstream to do it12:22
didrocksso, if I rerun right now, for the same components12:22
didrocksand there is new code to land12:22
didrocksit will be .2, .3…12:22
didrocksuntil tomorrow :)12:22
didrockspitti: also, the credit is given to who fixed the bug: https://lists.ubuntu.com/archives/raring-changes/2012-November/001547.html12:22
didrocks(don't worry about the 2 "Automatic snapshot from revision", one is for boostrap and was excepted. Didn't worth workarounding this)12:23
=== mcclurmc_away is now known as mcclurmc
=== cpg is now known as cpg|away
=== Tonio_aw is now known as Tonio_
tumbleweeddidrocks: where is the script that's doing this published?13:09
didrockstumbleweed: https://launchpad.net/cupstream2distro13:09
didrocksyw :)13:10
tumbleweeddidrocks: should there not be a whitelist of packages that are allowed to be copied? not everyone in the team owning that PPA has upload rights13:25
didrockstumbleweed: there should be no direct upload to the ppa13:26
didrockstumbleweed: the scripts are doing the upload13:26
tumbleweedthat's not enforced by anything, though13:26
DavieyAnyone have any thoughts on a merge of rsyslog from experimental ?13:26
didrockstumbleweed: indeed, but only the package in a stack can be copied13:26
tumbleweeddidrocks: what defines the stack?13:28
didrockstumbleweed: the jenkins jobs: https://jenkins.qa.ubuntu.com/view/cu2d/13:28
=== fisted_ is now known as fisted
=== attente_zzz is now known as attente
tumbleweedgiven that administation of that jenkins instance has no corellation to uplaod rights, I'd still prefer a whitelist13:31
cjwatsonI tend to agree13:31
tumbleweedcjwatson: does the tech board intend to review this workflow?13:32
cjwatsontumbleweed: I reviewed it at UDS; I don't know that it needs full board consideration unless you want to raise a specific problem with us13:33
didrockstumbleweed: what the whitelist will give? people will in ~ubuntu-desktop will be able to edit it, and the desktop package set doesn't covered all components here AFAIK13:33
cjwatsondidrocks: Not if you put the whitelist in somewhere only ubuntu-archive@lillypilly gets to edit.13:34
cjwatsonGiven that that account is the one whose privileges are being used, it's entitled to limit them.13:34
=== morphis|away is now known as morphis
didrockscjwatson: I don't know what we try to fix here. We can have restricted access to jenkins to people who can have those upload rights13:35
cjwatsondidrocks: This job is not supposed to be an end-run around the system of upload rights.13:35
didrockscjwatson: it seems way easier that having a whitelist which will always be outdated compared to the stack13:35
cjwatsondidrocks: tumbleweed is rightly objecting to what seems to be such a system.13:35
didrockscjwatson: and it is not13:35
cjwatsonBut it is, as long as people without upload rights can cause any package they like to be uploaded.13:35
tumbleweedhow often do you add new packages?13:35
didrocksso duplicated list of stack? one in jenkins, one in lillypilly13:35
didrockstumbleweed: well, in the first weeks, it will be daily, as soon as they are bootstrapped to this process13:36
cjwatsonI don't care where the list of packages lives as long as nobody without upload rights can edit it.13:36
didrockscjwatson: so you are fine with that list being defined in jenkins?13:37
tumbleweedI have no idea who has access to the jenkins instance. If I'm assure that only core-devs can admin it then I guess that'd be OK. Somehow, I doubt that's true, though.13:37
didrocksknowing that only people with upload right can access to it (maybe not everyone, but some)13:38
=== lu_zero_ is now known as lu_zero
cjwatsondidrocks: I'm fine with anything that meets the condition I laid out; I don't know how your jenkins instance is administered.13:38
cjwatsonSo I can't answer that question.13:38
didrocksbecause then, you can say the same with the jenkins machine13:38
didrocksIS can administrate those macihnes13:38
didrocksas IS can change something in lillypilly13:38
cjwatsonYeah, I don't mind assuming IS aren't malevolent13:38
cjwatsonThere's no point going down a rathole here13:38
didrocksare you assuming that QA is?13:38
cjwatsonI think I should leave this conversation.13:39
tumbleweedas an outsider, I accept that canonical have sysadmins who have root on all the machines13:39
cjwatsonI am assuming that people will use privileges they believe themselves to have to get their jobs done efficiently.13:39
didrockstumbleweed: QA are the sysadmins for jenkins13:39
tumbleweedI'm not convinced that the QA team should have a backdoor to the archive13:39
didrocksso we need to remove jenkins access to people administrating it?13:40
cjwatsonYou're the one who wants the list to live in jenkins.13:40
didrockscjwatson: well, the list is one thing13:40
didrockswhat we upload is way more important13:40
didrocksand the source packages are created by jenkins jobs13:41
didrocksso this is the part that QA can play with, change the content and so on13:41
didrocksthe list won't prevent that13:41
cjwatsonThat depends on your point of view.  There are plenty of things that the content of these packages doesn't affect at all.13:41
cjwatsonubuntu-archive@lillypilly can do *anything*.13:41
cjwatsonBut not all the world is Unity ...13:41
tumbleweedbut they're only reviewed g:q!13:42
didrockscjwatson: I know that, but I mean, if we have a whitelist, they can get something in Unity and break the rule of the upload rights13:42
didrocksso I don't see what the whitelist is fixing here13:42
didrocksI can do it, but that will fix nothing13:43
cjwatsonThey can't decide that somebody isn't fixing a bug in some other package quickly enough and stick it temporarily (and well-meaningly) in jenkins13:43
=== l3on_ is now known as l3on
=== Pricey_ is now known as Pricey
=== jbernard_ is now known as jbernard
tumbleweedpersonally, I'd like the automatic uploads to be approved for a particular set of packages13:44
didrockstumbleweed: it's all packages that are from canonical upstream, the UDS session was clear for that13:44
cjwatsonAnd all I want to do is enforce that it can only be used for such packages.13:44
tumbleweeddidrocks: right, then it should be staright-forward to come up with a list of those13:44
didrockscjwatson: I'll implement the whitelist on lillypilly, still unsure what it adresses those13:44
cjwatsonI consider this due diligence.13:45
didrockstumbleweed: there are those that are bootstraped and the others that are not13:45
tumbleweeddidrocks: that doesn't concern me too much13:45
didrockstumbleweed: it does for me13:45
tumbleweedit stops the robot doing things that it isn't allowed to13:45
didrocksbut again, i'll implement that whitelist13:45
tumbleweeddidrocks: thanks13:45
didrocksit's still fixing nothing IMHO compared to what others can do with this13:45
didrocksbut I'll do it13:45
cjwatsonThe limitation of upload rights is an important part of our organisational security.13:46
didrockscjwatson: I still reiterate that anyone having jenkins access to jenkins machines can change the tarball content13:46
cjwatsonAnd it's still valuable to limit the set of packages even if changes to those packages' content are unrestricted.13:46
tumbleweedI'd also prefer it if the detection of packaging changes happened at the bot level, rather than jenkns. But that's a minor issue, compared to having unrestricted upload rights13:46
=== broder is now known as broder_
cjwatsonBecause it is easy to review changes to a single package, or a small set of packages; it is very hard to review changes to the entire archive.13:47
didrockslet me implement it, I'll ping you back then13:47
cjwatsonSo I accept your point that anyone with jenkins access can change the tarball content, but it doesn't change my mind.13:47
cjwatsontumbleweed: I agree, seems like the security boundary should be where the check happens13:47
GunnarHjcjwatson: Hi Colin, wondering if you could take a look at the proposed solution to bug 952185. Saw Steve's comment at bug 584249, but I felt that a pam config change might still be ok. And it works. :)13:48
ubottuLaunchpad bug 952185 in pam (Ubuntu) "~/.pam_environment not parsed when HOME is encrypted" [Undecided,In progress] https://launchpad.net/bugs/95218513:48
ubottuLaunchpad bug 952185 in pam (Ubuntu) "duplicate for #584249 ~/.pam_environment not parsed when HOME is encrypted" [Undecided,In progress] https://launchpad.net/bugs/95218513:48
cjwatsonGunnarHj: Sorry, I don't consider myself immediately competent to review that13:48
GunnarHjcjwatson: Is Steve the one and only? (Think he's on vacation.)13:49
cjwatsonI don't know.13:49
tumbleweeddidrocks: so, what happens if some core-dev uploads an emergency PS stack packaging fix to the archive? it doesn't like like it would stop the bot from overwriting it the next day13:50
didrockstumbleweed: it would stop it13:50
didrockssee prepare-package13:50
didrocksand so the doc at the end of it13:51
=== NimeshNeema is now known as NimeshNeema_
tumbleweedah, there it is, ta13:51
GunnarHjcjwatson: Think I'll wait til Steve is back, then, since he seems to do the bulk of the pam maintenance. Thanks anyway.13:52
cjwatsonSorry I can't help.13:52
GunnarHjcjwatson: No problem.13:53
tumbleweeddidrocks: shouldn't that check should happen as close to the copy as possible? rather than before the source build?13:54
didrockstumbleweed: we will never get to the "copy" state if the source build fails13:55
cjwatsonBut consider a race condition13:55
didrocksyeah, I can do a second check if needed13:55
cjwatsonWe can't actually close it, but we can make it as narrow as possible13:55
didrocksgood point, adding that13:55
mspencerpitti: png re. bug 65727514:06
ubottuLaunchpad bug 657275 in apport (Ubuntu) "ubuntu-bug should save reports offline automatically rather than giving a cryptic error message" [Wishlist,In progress] https://launchpad.net/bugs/65727514:06
apwpitti, as the kernel depends on kernel-wedge, under autopkgtest i assume an upload there would trigger testing in linux -- correctly too14:21
=== Tonio_ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio_
didrockstumbleweed: cjwatson: whitelist built: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/revision/8614:46
didrocksI'll add the tests with the whole framework for testing14:46
didrocksI need more investigation to build properly the last-minute check for upload (particularly as I'm out of jenkins, how to get emails about those failures, even if I read -changes without being spammed with the rest) and passing the "previous last automated upload" version to the rsync file14:47
nemoHey guys, I'm stuck on W:Failed to fetch gzip:/var/lib/apt/lists/partial/mirror.anl.gov_pub_ubuntu_dists_quantal_universe_i18n_Translation-en   after attempted upgrade.15:01
nemoare not all the mirrors updated yet?15:01
nemoalso "bzip2: (stdin) is not a bzip2 file." on console.15:02
nemothe other possibility is the idiots here screwed up their explicit whitelisting of mirror.anl.gov on the stupid Websense server. which I'm totally open to15:02
nemooh. right. part of that error was "Encountered a section with no Package: header"15:05
nemohm. maybe if I run ltrace -S on update-manager I can figure out what URL it is trying to hit15:05
=== Tonio_ is now known as Tonio_aw
didrockscjwatson: tumbleweed: and the extra check for an upload to distro just before doing the copy: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/revision/8715:09
pittimspencer: hello15:09
pittiapw: right, that makes sense I guess?15:09
tumbleweeddidrocks: thanks15:09
apwpitti, i think it does indeed15:10
didrockstumbleweed: yw15:10
nemohrm. that didn't work :-/15:10
dholbachLaney, where can I file a bug on the transitions tracker?15:10
mspencerHi pitti, for LP #657275, what do you want done with bug reports if there is no Internet connection?15:11
ubottuLaunchpad bug 657275 in apport (Ubuntu) "ubuntu-bug should save reports offline automatically rather than giving a cryptic error message" [Wishlist,In progress] https://launchpad.net/bugs/65727515:11
Laneydholbach: is it a bug in the software?15:12
dholbachLaney, it's a wishlist item and https://launchpad.net/ubuntu-transition-tracker does not let me file bugs15:12
Laneyubuntu-bug ben15:12
nemoah. there's a tmp dir. let's see what's in there15:13
Laneyyeah, that's a different version to the one we have deployed but ho hum15:13
xnoxdholbach: what's the bug?15:13
dholbach[dholbach] file bug on transition tracker (lp:ubuntu-transition-tracker) to produce Harvest JSON output: TODO15:14
pittimspencer: I'm not keen on implementing a wholly new UI for browsing .crash files; you can just double-click on them in nautilus after all; but the [Save] button sounds fine15:14
=== Tonio_aw is now known as Tonio_
mspencerpitti: So just save them to the user's home folder and tell them to report them later?15:15
pittimspencer: but honestly it's not quite at the top of my list; there is a --save option if you really need to15:16
dholbachLaney, xnox: is there another place to report the bug then?15:16
Laneyjust report it against the ben package15:16
nemoah. !@#$ websense15:16
Laneyben (newer versions) can output yaml already though15:17
mspencerpitti: I know it's not very important, it was just something I came across that I thought I could handle since I'm new.15:17
xnoxdholbach: well. upstream is a package in debian called ben. Currently it can produce "text" and "html" outputs.15:17
dholbachok, I had no idea15:17
pittimspencer: oh, if you want to do that, great :)15:17
xnoxdholbach: in ubuntu we only replaced the logo & use our own transition good/bad/affects stanzas. Nothing fancy.15:17
pittimspencer: yes, it's not hard to do, just takes some time and love15:17
dholbachok, I see15:17
nemoand the place to look is apparently /var/lib/apt/lists/partial15:17
xnoxdholbach: it's written in OCaml , so don't expect major json developments =/15:18
mspencerpitti: where should I save the reports to? Home folder or a "Bug Reports" subfolder?15:18
Laneyxnox: I don't see what the language has to do with that?15:19
xnoxLaney: doesn't like PTS query ben somehow to show which packages are in a transition?15:19
Laneyvia the yaml file I already mentioned15:19
Laneybut you started talking about OCaml being a hindrance to this feature's development somehow15:19
pittimspencer: it should show a file dialog IMHO15:20
mspencerpitti: Okay, that's what I'll do, thanks!15:20
LaneyI would say that harvest should just work with the yaml file somehow, even if it's via some tool translating it to json. But it's moot ATM until we get the new ben deployed.15:20
xnoxLaney: in ubuntu we don't have many people who know ocaml, that is all. Didn't mean it, to come across the way it did.15:21
=== beuno_ is now known as beuno
=== Zic is now known as Guest98738
=== doko_ is now known as doko
=== Tonio_ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio_
=== Zic_ is now known as Guest7270
=== Tonio_ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio_
mspencerHi, I'm new to developing for Ubuntu and am interested in working on the Contributor Console (https://wiki.ubuntu.com/ContributorConsole). Is this something a beginner could do? So far I've worked on bug fixes.16:40
ScottKmpt: ^^^ since it's your page.  Not sure who's working on development.16:46
xnoxmspencer: as far as I know, there are only mockups and no coding has started yet.16:46
mptmspencer, hi, I wondered if you'd be interested ;-)16:47
mptmspencer, no-one's started it as far as I know. You're welcome to.16:47
mspencermpt: I'm not very familiar with packaging - do I need someone else to start the project and then I contribute to it or can I start it myself?16:50
bdrungJFYI: I started the gnustep transition16:51
mspencermpt: Would I be responsible for all the work on it or can I just work on as much as I can?16:51
=== stan_ is now known as stan
mptmspencer, you can start it yourself, and merge in branches contributed by other people. If you get bored of it later you can hand over ownership to someone else.16:53
mptmspencer, for example, you might decide you're only interested in doing the "Bugs" tab, but others might contribute parts of other tabs.16:54
mspencermpt, Okay, I'll work on it.16:54
mspencermpt: So I'll just create a new project in launchpad and use quickly to do this?16:55
mptmspencer, great! Yep, Launchpad and Quickly would be a good start.16:55
mspencermpt: Will I need to do anything to get it included in the Ubuntu?16:56
mptmspencer, yes, but you don't need to think about that until later. Others can work on the packaging, in the same way that they can work on parts of the code.16:56
mspencermpt: Great, thanks for your help!16:57
mptThank you, mspencer16:57
=== yofel_ is now known as yofel
mspencerHere's the new project: https://launchpad.net/contributor-console17:08
=== Ursinha is now known as Ursinha-afk
=== Tonio_ is now known as Tonio_aw
=== Guest7270 is now known as Zic
=== deryck is now known as deryck[lunch]
slangasekogra-cb_: I didn't say plymouth would be an easy merge, I said *don't merge it from Debian*, you should pull the new upstream version first and ignore the Debian package for now :)17:40
slangasekogra-cb_: s/would/wouldn't/17:40
slangasekonly after we're at the same upstream version, should we look at doing the packaging merge17:41
ogra-cb_oh, k17:41
slangasekogra-cb_: I see you and xnox both active on the package bug... is one of you going to take on the merge?17:41
slangasek(the upstream merge)17:41
slangasekor do you prefer to leave it for me to play with?17:42
ogra-cb_slangasek, i can try my best after the image stuff is done17:42
ogra-cb_i fear though that this will keep me busy for this week still17:42
xnoxslangasek: ogra-cb_: I can poke it a little =)17:42
* xnox really doesn't like 293kB long britney output.txt17:43
ogra-cb_slangasek, also, setting console=tty0 instead of tty1 seems to help with the hard crashing17:43
ogra-cb_it still doesnt get us a splash but i havent seen any reboots anymore at least17:43
slangasekah, nice17:43
ogra-cb_(still it shouldnt crash this hard indeed)17:44
GunnarHjslangasek: Hi Steve, wondering if you could take a look at the proposed solution to bug 952185. Saw your comment at bug 584249, but I felt that a pam config change might still be ok. And it works. :)17:47
ubottuLaunchpad bug 952185 in pam (Ubuntu) "~/.pam_environment not parsed when HOME is encrypted" [Undecided,In progress] https://launchpad.net/bugs/95218517:47
ubottuLaunchpad bug 952185 in pam (Ubuntu) "duplicate for #584249 ~/.pam_environment not parsed when HOME is encrypted" [Undecided,In progress] https://launchpad.net/bugs/95218517:47
=== andreas__ is now known as ahasenack
sarnoldarges: btw, "Fromat" in "RSYSLOG_SyslogProtocol23Fromat" in https://bugs.launchpad.net/bugs/105959217:54
ubottuLaunchpad bug 1059592 in rsyslog (Ubuntu Raring) "Message and memory corruption in rsyslog" [High,In progress]17:54
argessarnold, whoops17:55
argessarnold, fixed : )17:56
sarnoldarges: woo :)17:56
slangasekGunnarHj: hey there - so I'm still on vacation, don't know that I'll get a chance to look at that this week :)  Off the top of my head I'm not convinced this is a completely correct solution, so I need to look at it in some detail18:01
GunnarHjslangasek: Oh, sorry, saw your comment here, so I thought you were back. Let's wait then.18:02
slangasekGunnarHj: yeah, "vacation" is a sliding scale ;)18:02
mspencermpt: I've created the Contributor Console project in Launchpad. Should the wiki spec get updated to point to it?18:22
=== Ursinha-afk is now known as Ursinha
=== deryck[lunch] is now known as deryck
seb128unity fails to build in raring without code change18:53
seb128-- Found Gettext: /usr/bin/msgmerge (found version "0.18.1")18:53
seb128CMake Error at CMakeLists.txt:106 (if):18:53
seb128  if given arguments:18:53
seb128    "STREQUAL" "TRUE"18:53
seb128  Unknown arguments specified18:53
seb128 18:53
seb128is there any toolchain/gettext/cmake known issue?18:53
=== mcclurmc is now known as mcclurmc_away
bryceCould an SRU admin approve the jockey 0.9.7-0ubuntu7.6 upload for precise?  This includes two important fixes, one for the LTS point release backport drivers, and one for Valve experimental drivers.  It should make things display correctly in jockey, and we'd like to get people able to start testing both fixes soon.19:02
bryces/approve/approve into -proposed/19:03
bryce(if it matters, I did a quick code review of the change diff.)19:04
mterryIs anyone familiar with passing file descriptors over dbus?  Apparently it has support for it, but I'm not sure how it is supposed to work19:18
=== cpg|away is now known as cpg
=== mterry is now known as do_not_highlight
=== cpg is now known as cpg|away
=== mrpouit is now known as mr_pouit
mlankhorsttell mterry that unix fd's are probably sent as any other parameter..21:32
=== Tonio_aw is now known as Tonio_
tkamppeterSomeone knows the date of the next UDS?21:46
=== salem_ is now known as _salem
=== mcclurmc_away is now known as mcclurmc
bdrungrobert_ancell: do you plan to SRU evolution 3.6.2 to quantal? evolution 3.6.2 crashes several time a day and i like to check the new version.22:21
robert_ancellbdrung, do you mean 3.6.0 is crashing?22:24
seb128bdrung, check with cyphermox, he's maintaining evo22:24
bdrungrobert_ancell: yes22:24
robert_ancellthere's heaps of changes in 3.6.2 so I don't know about how that goes in an SRU, but yeah, cyphermox is the right guy to talk to22:25
bdrungrobert_ancell: opening an mail with attachment has a high chance to let it crash22:25
bdrungcyphermox: ^22:25
cyphermoxI agree, it's crashy. Perhaps we can SRU the specific fixes though22:26
ScottKmails with attachments are a security risk.  Security feature, not a bug.22:26
cyphermoxScottK: +122:26
bdrungScottK: so i can tell people that i can't review their debdiff sent by mail -> less work for me :D22:27
ScottKDouble win.22:27
bdrungcyphermox: is the wrong handling of signatures in evo 3.6 already reported?22:28
bdrungevo places my signature twice22:28
=== mcclurmc is now known as mcclurmc_away
cyphermoxbdrung: yeah, and I spent quite a few hours trying to make sense of it without luck :(22:30
cyphermoxbdrung: did you look at 3.6.2 and whether things were better there?22:30
bdrungcyphermox: not yet. i just tried to compile it under quantal without luck: http://paste.debian.net/211376/22:31
bdrungthe build dependencies seems to be not strict enough22:31
bdrungScottK: can you let gnustep-base pass through new?22:32
ScottKbdrung: No time to review it now, sorry.22:33
bdrungScottK: it's just binary new22:33
bdrungScottK: are binary new package reviewed the same way new packages are reviewed?22:35
ScottKbdrung: The review is not identical (don't review licensing), but there are still some checks to do.22:38
bdrungScottK: can you recommend someone i can nag? i have prepared the transition and like to get it done.22:40
ScottKNot really.  This is a holiday period here in the US.22:40
bdrungah, okay22:40
ScottKI don't recall if it is for Canada or not, so maybe infinity would do it.22:40
bdrunginfinity: do you have a little spare time to review the binary new packages of gnustep-base?22:41
infinitybdrung: Yeah, I'll poke it in a sec.22:48
cyphermoxbdrung: I'll package evo 3.6.2 and push it to a PPA to begin with22:55
cyphermoxor I guess upload to raring, instead22:56
bdrungcyphermox: robert_ancell uploaded evo 3.6.2 to raring.22:56
bdrungcyphermox: if you upload evo 3.6.2 to a quantal ppa, i will be happy to test it22:57
=== cpg|away is now known as cpg
=== Tonio_ is now known as Tonio_aw
=== Tonio_aw is now known as Tonio_
dokoall gcc-multiarch target patches accepted upstream, doko is opening a bottle of beer23:37
sarnolddoko: prost!23:38
cjwatsonnice!  sláinte23:40

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