/srv/irclogs.ubuntu.com/2013/11/20/#ubuntu-devel.txt

=== freeflying_away is now known as freeflying
=== Mapley is now known as Mapley|group
pittiGood morning04:28
pittistgraber: what I didn't understand yet: why do we conceptually need a daemon for the cgroup management anyway? why can't this just be a library which does proper locking to avoid cgroup fs write conflicts?04:29
stgraberpitti: because it's unsafe to allow a container to mount cgroupfs, so we want to let a container alter only a sub-section of the hierarchy04:30
pittistgraber: ah, so the daemon's API would always be "relative" to the calling cgroup?04:30
stgrabera container wouldn't be able to access cgroupfs directly but would have access to the daemon's socket which will let it write only in its sub-section of the hierarchy04:31
stgraberpitti: correct04:31
pittistgraber: thanks04:31
stgraberso we can do any level of nesting and user switch (with userns) without ever having to grant access to cgroupfs and therefore preventing any of the containers from escaping their limits04:32
NoskcajCan someone look into removing rhythmbox-radio-browser? It is pretty much non-functions due to rhythmbox api changes05:39
=== brainwash_ is now known as brainwash
asac10:40 < jibel> asac, confirmed: apt-get install libc6-amd64 && apt-get remove libc6-amd6409:43
asac10:40 < jibel> and get a broken system for free09:43
asac10:42 < asac> jibel: thats on i386?09:43
asac10:43 < jibel> asac, amd64 with i386 enabled09:43
asachmm... doko not around :)09:43
Laneyprobably infinity09:44
jibelasac, doko has issues with his provider this morning09:44
asacinfinity: ^ (in case you are in a eur zone)09:46
didrocksasac: infinity is sick today09:47
LaneyI guess file a bug and assign him09:48
infinityasac: There's already a bug for that.  I was just trying to think up a clever fix right now, while I can't sleep.09:51
infinity(Not a new bug, it's been like this since precise, but it's very rare for people to install libc6:amd64 and libc6-amd64 on the same machine)09:52
didrocksLaney: yeah, I guess you will volonteer in hosting vUDS session btw as I can't start anything on my machine now :p09:52
* ogra_ would blame the package that installs it ... 09:52
seb128infinity, it was, until the emulator started pulling it in09:52
asacinfinity: right. i think for now didrocks just needs a good idea how to recover (e.g. what exactly is now wrong)09:52
seb128ogra_, that's the android emulator :p09:52
ogra_the emulator deps should just be fixed09:52
didrocksasac: agreed ;)09:53
asacinfinity: maybe just unpack libc6:amd64 ?09:53
Laneydidrocks: have you /seen/ me try to use hangouts?09:53
ogra_it cant even use any amd64 stuff ...09:53
seb128didrocks: oh, so you did that to sneak off vUDS hosting!09:53
Laney:P09:53
infinityasac: What's wrong is that /lib64/ld-linux-x86-64.so.2 is gone.09:53
seb128lol09:53
didrocksseb128: clearly ;)09:53
seb128Laney, man, you and hangouts don't get along for some reason ;-)09:53
infinityasac: So no amd64 binaries will run.09:53
asacyeah09:53
infinityasac: Recreating the symlink from a rescue CD would do the trick.09:54
infinitydidrocks: ^09:54
didrocksyeah, no /lib64/ld-2.17.so binary09:54
ogra_infinity, whats wrong is that a package that can only make use of libc6-i386 pulls in libc6-amd6409:54
didrocksinfinity: the symlink is there, just not /lib64/ld-2.17.so09:54
infinitydidrocks: /lib/x86_64-linux-gnu/ld-2.17.so09:54
infinitydidrocks: The symlink should point to that.09:54
asaci assume thats in libc6:amd64? so ifyou have that and can unpack it should be ther?09:54
didrocksah ok, so lrwxrwxrwx    1 root     root            10 Nov 20 09:41 /lib64/ld-linux-x86-64.so.2 -> ld-2.17.so09:54
didrockswhich points to /lib/x86_64-linux-gnu/ld-2.17.so09:55
didrocksright?09:55
infinitydidrocks: No, just directly aim the symlink at /lib/x86_64-linux-gnu/ld-2.17.so09:55
didrocksok, trying that in my busybox09:55
infinitydidrocks: /lib64/ld-2.17.so is only in libc6-amd6409:55
didrocksmaking sense09:55
infinityogra_: That makes no sense.  Why is an i386 package pulling in libc6-amd64?09:55
asacinfinity: android :)09:56
ogra_infinity, thats what i'm saying09:56
didrocksof course, I need to be root09:56
infinity(Not saying there isn't a massive glibc bug here, but installing libc6-amd64:i386 on amd64 is never a desired result)09:56
didrocksand can't in this / busybox09:56
didrocksso needing to reboot in initrd busybox09:56
ogra_infinity, its the android-emulator package apparently09:56
asachttp://paste.ubuntu.com/6447333/09:56
asacthats the stuff in android-emulator09:56
infinityasac: That doesn't explain why it's forcing this weird set of packages to be installed.  What are its deps?09:57
asacinfinity: it has emulator64 binaries in there09:57
infinityOh, it explicitly depends on libc6-amd64 ... FUN.09:57
asaccan the package say: libc6:amd64 | libc6-amd64 ?09:57
* ogra_ has never used the package, i build it from the tree ... which 09:58
asacguess not :)09:58
ogra_... requires the i386 libs installed already09:58
infinityxnox: Want to make android-emulator depend on libc6:amd64 and libstdc++6:amd64 instead, and just make it not work without multiarch?09:58
infinityOh, wait.  Can't do that.09:58
infinityGrr.09:58
infinityOf course, it could just be an amd64 package, period, which would solve the issue.09:59
infinityJust make it not available on i386.09:59
seb128heh, why so much hate for i386 users09:59
infinityOr if it has i386 and amd64 bits, build one on one, one on the other, and have a metapackage that pulls in -i386 and -amd64 bits.09:59
infinitypull-lp-source: Downloading android_20131120-0225.orig.tar.xz from archive.ubuntu.com (191.659 MiB)10:01
infinityGah.10:01
ogra_dont cry ... that used to be 500M in the past10:02
infinityI'm all for people reminding me that I have a glibc bug that really needs fixing, but I'm not sure this was the way to do it. :P10:02
infinityQuite entertaining if we've been telling people to install this.10:02
ogra_well ... https://wiki.ubuntu.com/Touch/Emulator10:03
infinityOkay, so it's already arch-restricted to i386... Splitting it to an i386 and amd64 bit wouldn't be rocket science.  And we already seem to be assuming users of this will have multiarch enabled.10:04
ogra_we only offer it in trusty10:04
asacI am pretty sure its not rocket science, but I assume that the android build system will have to be taught to build things separated by archs :)10:05
ogra_nah. that wouldnt work10:05
asacI assume ricard tried to avoid carryuing a big delta there for the time being10:05
infinityasac: No need to tell it to break things up.  Just find the i386 binaries and put them in emulator-i386, do the same for the amd64 binaries, and package it up.10:06
infinityAaand, it's an hour-long build.  This'll be fun.10:07
infinityOh well, can't sleep anyway with this cough.10:07
infinityOh, derp.  This means I'd have to build it twice, though.10:09
infinityOnce per arch.10:09
infinityOh, wait.  You *can* depend on foo:arch.  crossbuild-essential does it.10:10
=== freeflying is now known as freeflying_away
asacdidrocks1: managed to get past the point of no command?10:16
* asac assumes that no news is good news for now10:16
didrocks1asac: well, I need to create an usb stick10:16
infinityDoing a test build of this blind change: http://paste.ubuntu.com/6447414/10:16
asacnice one :)10:17
Laneybahaha, I like that hack10:17
didrocks1asac: that will teach me to not always have a root terminal opened…10:19
didrocks1(to start busybox as root)10:19
mlankhorstsabdfl: hey since we now lack a TB, can you make a decision on the MRE's I requested on technical-boards@lists.ubuntu.com ? https://lists.ubuntu.com/archives/technical-board/2013-October/001737.html10:19
infinityI'll see if I can fix the actual linker switcheroo mess in 2.18 (I was looking at that earlier anyway), but either way, we shouldn't be encouraging people to install the multilib stuff.10:19
didrocks1asac: seb128: maybe one of you can annotate the wiki with those infos (to not install the emulator on amd64 for now)? ^10:20
infinitymlankhorst: A one-time version bump like that isn't really a standing MRE that the TB should have to worry about anyway, the SRU team can probably take that in hand.10:20
didrocks1especially if people wants to clean up their machine then :p10:21
mlankhorstinfinity: I just want to move things forward soon if possible. Pixman is the one I'm most worried about. But libdrm seems to require a bump every release, so it sort of would need a standing MRE. :P10:22
infinitymlankhorst: Sure, libdrm could use a standing MRE (or, though the versions make it look like "micro" releases, they're clearly not, and it probably needs something more like the firefox exception), but it's never had one before, so we can live without for a bit.10:23
infinitymlankhorst: Is this all well tested in a PPA somewhere?  Do you have a placeholder HWE SRU bug that you can attach tasks for all these packages to and detail the testing done and subscribe the SRU team?10:24
mlankhorstinfinity: libdrm is weird, most of the driver stuff is just a c wrapper for the kernel interface10:25
mlankhorsthttps://launchpad.net/~ubuntu-x-swat/+archive/s-lts-backport10:25
Saviqseb128, "don't uninstall libc6-amd64"? or "don't install libc6-amd64"?10:25
infinitySaviq: Yes.10:25
infinitySaviq: Don't install it, but if you have, uninstalling it is also dangerous.10:25
seb128Saviq, don't uninstall it if you have it installed10:25
mlankhorstI think I created a bug for the pointer barriers specifically, but I didn't make one for pixman and libdrm yet.10:25
Saviqseb128, so I can still try the emulator on amd64, just never uninstall it? ;D10:25
mlankhorstppa with all components at https://launchpad.net/~ubuntu-x-swat/+archive/s-lts-backport10:26
seb128Saviq, basically, or better wait for infinity to fix those stuff ;-)10:26
infinityI wonder if I could work around this hackishly by providing a libc6-amd64 on amd64 that just Depends: libc6.10:26
* infinity shudders a bit at the ickiness of that.10:26
mlankhorstinfinity: or finally implement cross-arch depends. :P10:27
infinitymlankhorst: If you could just do up a meta bug for "lts-s backports" and detail what needs review, and what's been tested and how, then we can point any discussion there.10:27
infinitymlankhorst: cross-arch deps work.10:27
mlankhorstok10:27
mlankhorstI think I will make the metabug the bug for pixman/libdrm backporting too10:28
infinitymlankhorst: That doesn't solve this particular issue of people installing libc6-amd64:i386 on amd64.10:28
infinityWhich explodes hilariously.10:28
mlankhorstwhy have that? o.O10:28
infinityMaybe we just need a Multi-Arch: dont-even header.10:28
infinityPackage: libc6-amd6410:29
mlankhorstI thought that was what the Architecture: field was for, just build it on amd64 only. :P10:29
infinityMulti-Arch: hahahahano10:29
infinitymlankhorst: Erm it's only built on i386.10:29
mlankhorstoh10:29
infinitymlankhorst: But then people install an i386 package that depends on it.10:29
infinityOn their amd64 system.10:29
* didrocks1 wonders why usb-creator doesn't want to finish the current usb stick creation… will go with dd if this continues…10:29
infinitydidrocks1: Just use dd.  usb-creator is a steaming heap of needs a lot of love.10:29
infinity(I think there may even be a UDS session about that?)10:30
smbinfinity, was10:30
didrocks1infinity: yeah, I can testify this right now :)10:30
infinityOr was. :P10:30
infinitysmb: How did that go?10:30
smbinfinity, I think we use something different10:30
mlankhorstoh found the pointer barriers bug https://bugs.launchpad.net/ubuntu/+source/x11proto-input/+bug/124263310:30
ubottuUbuntu bug 1242633 in x11proto-input (Ubuntu) "unity pointer barriers sru bug" [High,In progress]10:30
pittidd wrapped in a GTK dialog?10:30
mlankhorstI'll open a metabug10:30
infinitypitti: Well, the reason for usb-creator (the only valid reason, other than the pretty GUI) is that it knew how to set up the weird partition scheme required for persistence.  dd alone can't pull that off.10:31
smbinfinity, Actually there seems to be a more interesting issue on the side about having something that works with uefi and secure boot but not wasting most of your usb key10:31
pittiinfinity: right, was mostly kidding10:31
smbinfinity, Plus I thought there was an issue at least with older bioses of not booting an iso fs on a usb key10:32
infinityBut for 99% of people who just want an installer USB key and don't give a crap about persistence, yeah, usb-creator really could just fork dd.10:32
pittiI actually successfully used usb-creator in saucy still, it's sad that it broke down so quickly10:32
infinitypitti: It's been broken for several releases, success rates seem to vary from person to person and moon phase.10:32
smbamd64 being better that trying to do i386 images in my experience10:33
* infinity shields his eyes from all the code duplication he sees zipping past in this Android build log.10:33
infinityLA LA LA, CAN'T SEE YOU, HANDWAVE, GOING FOR A DRINK.10:33
smbSadly coffee has not the desired effect... and at least its not ktb#1 time for me10:34
infinitysmb: Choice of beverage really doesn't matter to me right now.  I should be either asleep or at a doctor's office, and I'm neither, so I'm failing at life.10:35
smbinfinity, Yeah well, highly depends on your current location which often is hard to guess10:35
infinitysmb: Calgary.  I think.  It's a bit hazy.10:36
smbinfinity, That might be true now but was not last(?) week. Which could probably be part of the issue, too10:38
didrocksphew10:39
didrocksthanks infinity, asac (et jibel for testing in a vm)10:39
infinitydidrocks: All gooder?10:39
didrocksyeah ;)10:39
infinityI really need to come up with a clever fix for that.10:39
didrocksthe longest was to download/create this usb stick…10:39
infinityI was going to use dpkg diversions when I first found this issue in precise, but dpkg-divert had a bug that prevented it...10:40
didrocksI'll build an initramfs dropping me in a busybox for next time :p10:40
infinityThat's now fixed, but it would break on upgrades FROM precise...10:40
infinitySo.  Whee.10:40
didrocksinfinity: oh? interesting10:40
infinityOnly mildly interesting.  Mostly just annoying.10:41
didrocks(but, can be epic between the version without the fixed dpkg and then)10:41
infinityI can either bury my head in the sand and pretend the bug doesn't exist until 14.10 and fix it with diversions when I can do it safely.  Or come up with a more clever hack to work around it now.10:41
infinityAnd I think I almost mapped out a clever fix in my head about an hour before you broke your computer.10:42
infinityBut that could just be the drugs talking.10:42
infinityI'll need to commit it to code when I'm more aware of my surroundings and see if I'm drunk.10:42
didrocksinfinity: heh, sounds like a good plan, meanwhile, le'ts put an info in the wiki for the emulator, as I guess it's the main case for people getting into that bug10:43
mlankhorstinfinity: https://bugs.launchpad.net/ubuntu/precise/+source/libdrm/+bug/125304110:44
ubottuUbuntu bug 1253041 in libdrm (Ubuntu Precise) "lts-saucy enablement in precise" [High,In progress]10:44
infinitydidrocks: I might pull the emulator binaries from the archive for now.10:45
* infinity does that.10:45
infinityRemoving packages from trusty:10:45
infinityandroid-emulator 20131120-0225-0ubuntu1 in trusty i38610:45
infinityComment: High chance of breaking amd64 systems10:45
infinityRemove [y|N]? y10:45
* infinity waves bubye.10:46
infinityIf my test build goes okay, I'll upload that.10:46
asacthx. let us know10:46
infinityWith a nasty side-effect that people who *did* install the broken version of the emulator might get libc6-amd64 autoremoved and land in your situation...10:47
infinityWhat fun that will be.10:47
didrocksinfinity: TBH, I won't test you hack today :p10:50
seb128infinity, asac, didrocks: since that was announced on the list (https://lists.launchpad.net/ubuntu-phone/msg05195.html) I guess we can count on quite some people installing/trying it... would be better to not autobrick their systems with the update (e.g maybe fix the libc side if we can before updating the emulator)10:50
didrocksyour*10:50
didrocksright, I'm going to summarize what to do in case someone is broken?10:51
infinityseb128: The libc fix will take some more thinking.10:51
seb128didrocks, is that a question? yes please follow up on the list ;-)10:51
infinityseb128: And people installing the emulator might be removing it too.  Which already puts them in this situation.10:51
infinity(Granted, very few people also do autoremove religiously)10:52
asacisnt update-manager doing autoremove?10:54
infinityOh, is it?  Fun.10:55
seb128asac, not in normal update mode at least, maybe in dist-upgrader mode10:55
asacnot sure... asking :)10:55
infinityI didn't *think* it did.10:55
asac(i have to admit that i got stuck in old apt-get habits)10:56
didrocksI did autoremove religiously, not sure if one of our tool is doing that :)10:56
asacseb128: right. i think dist upgrading does autoremove10:56
asacnot normal upgrades10:56
asacdont think thats better though ... just makes the support bomb more intense :)10:56
infinityNah, buys me time until April to fix it!10:57
asacotoh, we can add arbitrary hackery to mitigate such issues in update-manager...10:57
infinity(I'll make it a priority right after 2.18 is otherwise ready, unless the answer comes to me while I'm at the doctor's in the morning)10:57
tseliotpitti: sorry to bother you again but the binaries for nvidia-graphics-drivers-304 and its -updates flavour are stuck in NEW (trusty)11:04
tseliotpitti: they include the same changes that you approved in the 331 series11:04
pittitseliot: ah, the new libraries, yes; looking11:06
tseliotthanks11:06
tseliotpitti: thanks a lot!11:21
=== _salem is now known as salem_
ahasenackhi guys, I have a recipe (https://code.launchpad.net/~ahasenack/+recipe/juju-deployer-daily) that started failing to build on trusty,11:31
ahasenack dpkg-source -i -I -b recipe-{debupstream}+bzr{revno}-0~{revno:packaging}11:31
ahasenackdpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision11:31
ahasenackbut my packaging branch has source format "3.0 (quilt)"11:31
ahasenackis this an artifact of how recipes are built in launchpad?11:32
ahasenackthe same package builds on saucy, for example11:32
ahasenackmaybe a flag was switched in trusty to make that a fatal error?11:32
infinity  * Catch mismatches between version strings and format versions in11:36
infinity    dpkg-source. Ensure that a 3.0 (quilt) package has a non-native version11:36
infinity    and that a 3.0 (native) package has a native version. Closes: #70017711:36
infinityahasenack: New dpkg enforces this, yes.11:36
ahasenackok, so it looks like launchpad recipe builds will break if your package is 3.0 (quilt)?11:36
ahasenackhttp://bazaar.launchpad.net/~ahasenack/juju-deployer/juju-deployer-packaging/view/head:/debian/source/format is what my recipe uses11:37
StevenKYou need pristine-tar information in the branch for the recipe to construct a tarball, otherwise it will override your recipe to 3.0 (native)11:37
ahasenackhttps://launchpadlibrarian.net/156978348/buildlog.txt.gz buildlog11:38
ahasenackStevenK: what's "pristine-tar information"?11:38
StevenKahasenack: pristine-tar allows you to regenerate any tarball you've made from the repository information, 'man pristine-tar'11:39
ahasenackStevenK: but there is no tarball on my side, it's a launchpad recipe, it builds the package from branches11:39
infinityStevenK: Oh, does pristine-tar actually allow recipes to DTRT here?  Nice.11:39
StevenKinfinity: Yes11:40
infinityahasenack: Yes, but pristin-tar is the glue that allows you to recreate the orig.tar.gz out of your branch.11:40
StevenKinfinity: Do you want to help ahasenack since it's like 224011:40
ahasenackinfinity: and what do I do with it? I have to upload it to the ppa manually first, then recipes will work, or what's the idea?11:40
infinityStevenK: Not really, it's 0440 here, and I'm sick. :P11:40
ahasenackoh boy :)11:40
StevenKHaha11:40
ahasenacklooks like you both need to be asleep11:40
ahasenackinfinity: that bug number from the changelog snippet you pasted seems wrong, btw, it's about "os-prober failed to detect both Windows bootable partition" ;)11:42
xnoxahasenack: the answer to your troubles, is to modify the recipe version used for the package, such that it is a native one.11:42
infinityahasenack: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=70017711:43
xnoxahasenack: otherwise, you need original tarball, which you say you don't have.11:43
ubottuDebian bug 700177 in dpkg-dev "dpkg-dev: please reject native/non-native version when building native/non-native source packages" [Wishlist,Fixed]11:43
ahasenackinfinity: ah, debian11:43
StevenKxnox: He can recreate an orig tarball with pristine-tar11:43
ahasenackxnox: it's a recipe build, I would think that LP would take care of it (generate the tarball)11:43
ahasenackdo you guys use launchpad recipes? Maybe I'm barking at the wrong tree11:43
xnoxStevenK: he wants to daily-build master crap no matter what it is, not generate orig tarball for each commit ;-)11:44
xnoxahasenack: so in {debupstream}+bzr{revno}-0~{revno:packaging}, remove the "-" =)11:44
ahasenackxnox: yeah, was going to paste11:45
ahasenack{debupstream}+bzr{revno}~{revno:packaging} maybe11:45
ahasenackor s/~/+/11:45
xnoxahasenack: then your recipe will be native, no original tarball needed, and it will just build.11:45
ahasenackwill have to think about it11:45
xnoxahasenack: that one will work too.11:45
infinityDepends: libstdc++6:amd64 (>= 4.1.1), libc6 (>= 2.15), libc6:amd64 (>= 2.15), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx, libstdc++6 (>= 4.6), libx11-611:45
* ahasenack ponders upgrades and all that stuff11:45
infinityI win.11:45
xnoxahasenack: i think "+" will be better.11:46
ahasenackyep11:46
ahasenackxnox: thanks11:46
xnoxinfinity: enlighten me about your winnings =)11:46
ahasenackand lp will still add ~ubuntu<release-number> at the end11:47
xnoxyes11:47
ahasenackok, let's kick it11:47
ahasenackthanks again11:47
infinityxnox: Making your emulator stop pulling in libc6-amd64:i38611:48
xnoxinfinity: patches welcome.11:49
xnoxinfinity: what should I do? =)11:49
infinityxnox: You can pull the patch from the archive shortly. :P11:49
xnoxinfinity: ah, even better. thanks for that.11:49
infinityMan, this source takes a while to re-pack on a rotary disk.11:50
xnox=)11:50
infinityxnox: http://paste.ubuntu.com/6447754/ FWIW.11:51
infinityxnox: With bonus guilt-induced tech-debt swap.11:52
infinityAlso, I can't spell dirty.11:52
* infinity doesn't upload.11:52
arunhello guys I had a question !!! should we ask any sort of permission on developing a distro based on UBuntu named as Obuntu under the support of Obuntu group ?11:52
infinityarun: Yes.11:53
xnoxarun: yes, "*buntu" is protected.11:53
ogra_infinity, your patch drops xz compression, doesnt it ?11:54
infinityarun: https://forms.canonical.com/trademark/11:54
arunGuys, where can we ask for it ?11:54
xnoxogra_: xz is default. see changelog entry above.11:54
infinityogra_: Reading changelogs is hard?11:54
ogra_bah, i only looked at the bottom :P11:54
xnoxarun: see link infinity pasted.11:55
infinityxnox: Uploaded.11:55
* infinity is going to see if he can nap for a few minutes before coughing himself awake again.11:55
xnoxinfinity: .... thanks. it doesn't help any other packages that build-depend on gcc-multilib though. Or would this be solved by builders having multiarch enabled?11:56
arunand by the way , what is  loCo ?/11:56
infinityxnox: There aren't many packages that actually end up depending on libc6-amd64/libc6-i386, but you're right, this won't help those that do.11:57
=== freeflying_away is now known as freeflying
infinityxnox: I still need to fix the libc bug that causes that situation to explode, but depending on biarch libs is generally wrong regardless, IMO.11:57
xnoxarun: LoCo = Local Community, i.e. local community groups representing ubuntu in their region.11:57
arunxnox: oh11:58
xnoxarun: typically they are known and participate in the Ubuntu community and thus are registered with Ubuntu Project and receiving sponsorship (e.g. free CDs & marketing materials) to promote Ubuntu.11:58
ogra_https://wiki.ubuntu.com/LoCoTeams11:58
arunGuys , does Canonical feeds Ubuntu devs ???11:58
brendandarun, we have to feed ourselves11:59
xnoxarun: there are girls here as well. and these sort of questions you are asking are not related to development of ubuntu core itself. Maybe you can take this conversation to #ubuntu instead?11:59
xnoxarun: i'm sure there are plenty of people who can answer these generic questions about Ubuntu Project.12:00
arunbrendand: oh ok12:00
arunxnox: ok thanks a lot ; I think I went off topic12:00
arunGuys, is Unity based on Gnome 3 ?12:02
mlankhorsthmz12:18
mlankhorstMismatchError: True != False12:18
mlankhorstbut that statement is true :o12:18
=== chuck__ is now known as zul
=== MacSlow is now known as MacSlow|lunch
=== dholbach_ is now known as dholbach
* jpds wonders why we have a super-old util-linux on Ubuntu.13:02
jpdsinfinity, lamont: Oh, hi. :)13:04
mitya57Hi, I see bug 1253003 in the sponsoring queue. Any hint why that has not been auto-synced yet?13:06
ubottubug 1253003 in Ubuntu "Sync wxwidgets3.0 3.0.0-1 (universe) from Debian sid (main)" [Undecided,New] https://launchpad.net/bugs/125300313:06
mitya57gilir: Hi, may I ask you to look at https://code.launchpad.net/~m-alaa8/ubuntu/saucy/pcmanfm/fix-for-993996/+merge/195625 please?13:12
=== steveire_ is now known as steveire
=== MacSlow|lunch is now known as MacSlow
pitti$ LANG= bzr branch ubuntu:systemd-shim13:49
pittibzr: ERROR: Revision {package-import@ubuntu.com-20130502111419-gg4b0m966tgp1p72} ist nicht in »Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))« vorhanden.13:49
pittierr, what does that want to tell me?13:49
pittiany known workaround?13:49
pittierr, neither LANG, LC_ALL, LANGUAGE help -- says something like "... revision ... isn't present in Graph.."13:50
seb128pitti, it's telling you "stop using udd"?13:52
mdeslaurlol13:52
seb128dunno about the specific error though :/13:52
pittiseb128: probably :/ I wanted to give it another try for developing some autopkgtests, but I guess I'll just go the classical way13:52
Laneyomg, a lesser spotted wednesday troll13:52
seb128ups, did I troll again?13:52
* seb128 needs to stop that13:52
ogra_yeah, not friday yet13:53
Laneyhaha13:53
pittione of the few packages which don't have patches, and thus would be manageable with UDD>.13:53
ogra_fix my firefox tooltip instead :P13:53
cjwatson[New] wxwidgets3.0_3.0.0-113:58
cjwatsonNo previous publications in Ubuntu13:58
cjwatsonOK (Y/n)?  y13:58
cjwatson * Trying to add wxwidgets3.0 ...13:58
cjwatsonwxwidgets3.0_3.0.0-1 is trying to override modified binary wx-common_2.8.12.1-14ubuntu2.  OK (y/N)?  n13:58
cjwatsonmitya57: ^- that's why13:58
cjwatsonmitya57: somebody needs to work out if those two changes need to be forward-ported to 3.013:59
mitya57cjohnston: oh thanks, will reject the bug for now then13:59
mitya57Bad xchat.14:00
cjwatsonI should tee the output of auto-sync to a file on people or something14:02
seb128roaksoax, hallyn_: hey, did you guys upstream that avahi patch you uploaded to trusty?14:36
smoserslangasek, around ?14:46
slangaseksmoser: vUDS14:46
smoserwould you think that bug 1235231 is fixable ?14:46
ubottubug 1235231 in plymouth (Ubuntu) "plymouth loses output to /dev/console (such as ci-info: messages)" [High,Confirmed] https://launchpad.net/bugs/123523114:46
hallyn_seb128: we could try submitting it to debian...  i'm not sure it's appropriate.  it's a workaround for lack of user namespaces, and i'm not very happy with it14:51
hallyn_seb128: oh, actually no we can't submit it to debian really, bc it relies on upstart14:51
slangaseksmoser: what do you mean, "fixable"?  I already said in the bug log that the cloud images should just override plymouth to stop it from running14:52
seb128hallyn_, hum, k, next time it would be nice to put those details in the patch header to make work easier for whoever is looking e.g at merging that package next14:52
hallyn_agreed14:53
seb128thanks14:53
smoserslangasek, i just added a comment there.14:55
smoserby "fixable" i meant "stop being broken".14:55
smoserplymouth is explicitly "supposed" to replay content it captures. its a clear bug that it does not do that.14:55
hallyn_seb128: sorry, it didn't occur to me yesterday that it depended on upstart.14:55
smoser(as are most dataloss issues :)14:55
seb128hallyn_, no problem, thanks for the reply to my questions!14:56
slangaseksmoser: don't count on a fix for that any time soon.  Workaround is known, and we don't have resources to fix all the plymouth issues any time soon14:57
smoserok. well, then i would appreciate your thoughts as to my comment 19 there, and i'll look to get this in sooner rather than later.14:57
slangaseksmoser: replied15:03
smoserslangasek, yeah, but you didn't reply the way i wanted.15:06
smoseri'd much rather have the disabler package close to plymouth, so that when/if a new upstart job is added its obvious it needs ot be fixed.15:06
slangasekthere aren't going to be more upstart jobs15:06
slangasekand half those overrides are niceties15:06
pittiooooh! http://alioth.debian.org/ just came back15:17
tseliot\o/15:18
mlankhorstyay15:19
cjwatsonYeah, it's on its way, I think they're still putting some pieces back together15:19
Laneyssh vasks works, at least, although the filesystem doesn't seem (fully) restored15:20
cjwatsonEr15:20
cjwatsonvasks is going away15:20
cjwatsonIt's being replaced by a new host15:20
roaksoaxseb128: i didn't yet.15:20
pittiyeah, host key changed (understandably)15:21
pittiLaney: moszumanska now15:21
cjwatsonI suggest waiting for an announcement from the alioth admins before pushing stuff15:21
Laneyah15:21
LaneyI've been checking d-i-a15:21
Laneyno news of that there15:21
pittimight still take a bit until it gets official, but I'm happy to see it alive again after two weeks15:22
shadeslayercjwatson: uhm, stupid question, there was this package which had a script to build your own ubuntu live cd ( not live-rootfs ), do you know which one it was?15:34
shadeslayeroh15:35
shadeslayerit *is* live-rootfs15:35
cjwatsonlivecd-rootfs15:35
cjwatsonbut ignore livecd.sh, use the live-build hooks there15:36
cjwatsonhttps://lists.ubuntu.com/archives/ubuntu-devel/2011-June/033458.html15:36
shadeslayer*nod*15:36
=== Sweetsha1k is now known as Sweetshark
smosermhall119, what circumstances make the 'Join hangout' link appear ?16:04
jcastroI beleive the person who runs the session needs to provide summit with the link16:04
smoserhttp://summit.ubuntu.com/uds-1311/meeting/22045/servercloud-1311-maas/ has hangout details, and i'm logged in, but id ont see it.16:04
smoserah. its there now.16:05
smoserit must only appear after start of session (it should have a grace "join" period)16:05
mhall119smoser: 1) it's within the slot's start & end times, 2) the user is logged in, 3) the user is marked as attending the UDS16:05
mhall119also 4) you're not getting a stale page from the caching server sitting in front of summit.u.c16:06
smosermhall119, well can i suggest that '1' be tweaked to include 10 or 15 minutes prior ?16:06
=== brainwash_ is now known as brainwash
slangasekrbasak, smoser: do you want anyone from the server team to come to the Secure Boot session?16:07
smoseris that now ?16:07
smoser:-(16:07
mhall119smoser: you can if you file a bug for it16:07
mhall119lp:summit16:07
seb128tjaalton, tseliot, mlankhorst, coming to the xorg for t vUDS session? https://plus.google.com/hangouts/_/7ecpjg4e7ibk4vghv8fkul3tt8?authuser=016:07
smoserk16:07
slangaseksmoser: yep16:07
smoserk.16:08
seb128RAOF, ^ up? or is it still night time for you?16:08
smoserslangasek, joining16:09
smoserslangasek, can you give me a link ?16:11
slangasekhttps://plus.google.com/hangouts/_/72cpj2k5dn4bjr053d5ehn1lpo16:11
smoseranyone interested, http://pad.ubuntu.com/lower-third16:20
smoserthats my "howto" for vuds and lower third16:20
josephtsmoser++16:21
tedgstgraber, I couldn't come to the Upstart session, but do you expect the cgroup to be created for pre-start or only when executing the job.16:26
stgrabertedg: I think we decided to go with consistency with other limit stanzas, so pre-start would also be put in the cgroup16:28
tedgstgraber, So then would pre-start be able to configure the cgroup?  i.e. this group can only use 100MB of RAM16:29
stgrabertedg: yes but it shouldn't cgroup limits should be applied through the cgroup stanza16:29
tedgstgraber, Ah, okay.  I thought the stanza only created, didn't realize the limits could be there.16:30
stgraberanyway, I'm planning to send a mail to upstart-devel later today with the suggested implementation16:31
tedgstgraber, K, I'll wait for that before I get confused :-)16:31
=== tkamppeter_ is now known as tkamppeter
seb128it seems that powerpc-porter is still down, do we have any alternative solution to debug ppc issues?16:35
cjwatsonI used the "machine in infinity's house" solution last time I needed it16:36
dholbachjibel, congratulations! finally! :)16:37
pittijibel: oh, got your membership?16:37
highvoltagetedg: it's ok, you can spawn your own upstart session :p16:37
ogra_jibel, whee !16:37
seb128jibel, congrats!16:38
seb128cjwatson, thanks, we did that last time as well for indicators issues, might need to do it again...16:38
seb128infinity, ^16:39
cjwatsonseb128: or you could get the package cross-building16:39
seb128I guess that's an option, less easy to set up though16:40
tedghighvoltage, I'm partially responsible for *everyone's* upstart session ;-)16:41
seb128would be nice if we had a porter box available :/16:41
tedgseb128, You can probably get a PlayStation 3 cheap :-)16:41
cjwatsonwe desupported those rather a long time ago :)16:42
seb128tedg, funny that you speak, the issues are indicators one, I could just get you to fix your stuff... ;-)16:42
seb128tedg, if you buy a ps3 for that, fine by me :p16:42
tedgseb128, Heh, it's a lot more than just indicators.  Webbrowser, upstart-app-launch, etc.16:43
ogra_heh16:43
seb128tedg, do we have an idea if that's a toolchain issue or what?16:44
seb128cyphermox, ^16:44
tedgIt seems a lot of them are actually dependency waits.16:44
seb128oh, indicators are failing tests16:44
tedgSo some false positive just looking at the icons.16:44
tedgI'm curious if it's not starting the X wrapper or something like that.16:45
seb128google test hiding the output sucks :/16:45
seb128tedg, e.g https://launchpadlibrarian.net/156991211/buildlog_ubuntu-trusty-powerpc.dbus-test-runner_14.04.0%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz16:45
seb128the log is pretty much useless16:45
Laneyblame automake not google16:45
seb128https://launchpadlibrarian.net/156995004/buildlog_ubuntu-trusty-powerpc.hud_13.10.1%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz16:46
seb128is interesting16:46
seb128*** stack smashing detected ***16:46
tedgYeah, it is odd.16:47
tedgSeems like a common thread is Python?16:47
seb128I've seen similar stack smash errors in one of the indicators16:47
tedgSome of the tests that use python was failing, and the dbusmock tests obviously use python.16:47
seb128doko, ^ is there a known issue with python3 on ppc on trusty?16:48
tedg*** stack smashing detected ***: python3 terminated16:49
dokoseb128, updated python3 yesterday, so it could be possible16:50
seb128didrocks, cyphermox, tedg: when did those tests issues start?16:50
cyphermoxtwo or three days ago. I'm not sure16:51
cyphermoxI don't think this is python issues16:51
dokopython3 changed yesterday16:51
seb128ok :/16:51
tedgNot sure either.  I just updated dbus-test-runner to use dbus-mock, so we've started using more of it as a result.16:51
cyphermoxI'll get the logs shortly, there's a build running for powerpc now16:51
cyphermoxtedg: seb128: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/524905816:52
seb128cyphermox, well, e.g https://launchpadlibrarian.net/156995004/buildlog_ubuntu-trusty-powerpc.hud_13.10.1%2B14.04.20131120-0ubuntu1_FAILEDTOBUILD.txt.gz has smashed stack python errors16:52
cyphermoxwell, yeah, but that might well be something different16:52
cyphermoxI'd like to know for sure, and that we can get with full logs.16:52
marrabldI have a few questions about packaging.  I used to package an App in my ppa.  But since Ubuntu moved where it keeps the QT libraries my recipes have failed for modern versions of Ubuntu.  So I have to take another look at my packaging scripts.  I am going to separate my packaging scripts from the code repo (currently in the same repo as the code).16:58
marrabldSo my first question is, should I put my debian directory in a separate branch and then get my recipe to merge the branches or should I put them in a separate repo.?16:58
seb128cyphermox, tedg, doko: https://launchpadlibrarian.net/157024833/buildlog_ubuntu-trusty-powerpc.indicator-messages_13.10.1%2B14.04.20131120.0-0ubuntu2_FAILEDTOBUILD.txt.gz17:00
seb128*** stack smashing detected ***17:00
seb128seems like a ppc toolchain issue17:01
seb128test-gactionmuxer is having the same problem than python17:01
* tedg blames the stack for allowing itself to get smashed17:01
tedgYeah, thinking so.17:02
tedgNot sure what, I guess we'd need a valgrind run to get some clues on what is happening.17:02
seb128doko, ^ did the ppc toolchain change recently? any idea about that?17:02
smoseranyone interested, http://paste.ubuntu.com/6449132/17:05
smoserthats a hacky script that reads a vuds link and makes nicely formated list of links to Hangout, Etherpad, IRC ...17:05
hikenboothello I have saucy and am wondering if there is packages for gmp mpfr and mpc (prepackaged version for this version of ubuntu)17:10
hikenboottrying to consistently compile gcc correctly a package would be helpful17:11
jtaylorhikenboot: sure all build depends of gcc are packaged17:12
jtaylorapt-get build-dep gcc17:12
jtayloralso gets you ppl cloog etc17:12
hikenbootah awsome ok didnt see that one coming but should have!17:12
cjwatsonwell, "apt-get build-dep gcc-4.8" is more likely to be useful17:13
cjwatsongcc -> just the defaults links17:13
jtaylorright different source :/17:14
hikenbootthanks a bunch..its really appreciated!17:14
pittijibel: how difficult is it to fix britney/the test scripts to run newly uploaded autopkgtests?17:45
pittijibel: e. g. I just added tests to systemd-shim, and it got promoted without running the new tests17:45
pittis/promoted/propagated/17:45
=== cmagina is now known as cmagina-lunch
jamespagedoko, hey are you OK to attend at least the first part of the juju activities for trusty session - specifically to discuss golang support in main17:58
dokojamespage, sorry no17:58
jamespagemwhudson, ^^ any chance you could attend as doko v2?17:59
dokoseb128, ?18:04
SaviqMirv, still around?18:17
=== salem_ is now known as _salem
=== vibhav is now known as Guest7386
MirvSaviq: following the sessions for a bit still18:23
Mirvwhat's up?18:23
SaviqMirv, when you have a minute (doesn't have to be today) - any reason why http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/qtdeclarative-opensource-src/trusty/view/head:/debian/patches/qtquick_delegate_creation_range_itemviews.patch is dropped from 5.2?18:24
seb128does anyone know how to debug "invoke-rc.d: initscript dbus, action "start" failed." issues (happening in a chroot)18:24
seb128unping, dbus is not needed to debug that build issue (though still happening when those happen)18:25
Mirvseb128: /var/lib/dpkg/info/dbus.postscript?18:25
seb128Mirv, postscript? postinst you mean?18:25
seb128Mirv, well, ideally the start job wouldn't fail which is real issue18:26
seb128Mirv, but yeah, it can be hacked around by hacking the postinst or the init job18:26
Mirvseb128: exactly :) I've removed the failing lines when installing packages in chroot18:26
MirvSaviq: probably it didn't apply or I thoight it's merged upstream18:27
seb128Mirv, ideally we would make the install work in a chroot rather than ask everyone to workaround it though ;-)18:27
SaviqMirv, yeah, we'd need to port it, that one is something we're carrying ourselves, unfortunately18:28
MirvSaviq: ah, ok18:28
=== SWAT_ is now known as SWAT
Mirvseb128: sure.. I've thought it'd probably work with enough bind mounts (/dev, /sys etc) but I haven't bothered to automate those although there are tools for that too18:30
infinityseb128: My chroots all have a policy-rc.d in them that prevents daemon startup.18:31
infinityseb128: mk-sbuild does this for you.18:31
seb128thanks, I was mostly trying to help one of the Debian guys who wants to look at the smashed stack trusty issues18:40
xnoxseb128: mk-sbuild is in debian.18:43
xnoxseb128: "sudo apt-get install ubuntu-dev-tools; mk-sbuild trusty; schroot -u root -c trusty-amd64/i386" works on debian.18:43
seb128xnox, yeah, I don't know what he's using, he was just hitting dbus not installing because of that error18:43
seb128but that's fine, he forced over it and that's good enough for debugging the issue18:44
seb128Laney, mardy: just for info, e-d-s upstream reply about uoa/calendar18:46
seb128"I think I know what's wrong: I forgot to update the UOA .service files for18:46
seb128Google's OAuth-based CalDAV interface.  Just need to find time to test it."18:46
pittizul: python-misaka tests fail with "ImportError: No module named 'misaka': https://jenkins.qa.ubuntu.com/job/trusty-adt-python-misaka/1;19:04
pittizul: sorry, email notifications are broken since the CI lab change, thus playing relay..19:05
zulpitti:  crap ill fix it up19:06
pittizul: thanks (probably just a missing test dep)19:06
zulpitti:  yeah :(19:07
slangasekmlankhorst: are you able to join the session for hwe planning for 14.04?19:08
slangasekmlankhorst: https://plus.google.com/hangouts/_/72cpi5mshd3mujd9pk5te8c50s19:08
loolcjwatson, slangasek: If either of you feels like joining the Go session, that might be useful for packaging related questions19:14
slangaseklool: can't, running another session; cjwatson?19:14
cjwatsonyeah19:15
smoserbdrung, thoughts? https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/125320819:20
ubottuUbuntu bug 1253208 in distro-info (Ubuntu) "python-distro-info hard to use for some cases" [Undecided,New]19:20
=== cmagina-lunch is now known as cmagina
mwhudsonjamespage: send me email but probably not, i am on leave in an inconvenient timezone :)19:53
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
ogra_cjwatson, is there some config file that needs editing to get ubuntu-touch onto http://people.canonical.com/~ubuntu-archive/germinate-output/ ?20:33
=== _salem is now known as salem_
cjwatsonogra_: script, but yes - edited snakefruit:~ubuntu-archive/bin/update-germinate, so that should appear for you on the next run20:54
ogra_thanks !20:55
ogra_pmcgowan always asks me weird questions why a package is in the image ... that might help a bit :)20:55
pmcgowanthanks20:55
cjwatsonYep, indeed20:55
cjwatsonMy oversight that it wasn't there already20:56
=== Mapley|group is now known as Mapley
=== Mapley is now known as Guest20302
=== Guest20302 is now known as Mapley
=== salem_ is now known as _salem
bdrungsmoser: hi, i am happy to accept patches.22:21
bdrungsmoser: returning a dict has the drawback that it could be hard to support if we want to change the internal22:22
bdrungsmoser: we could add functions instead that take a series and return the fullname/version/etc22:22
xnoxcjwatson: I get "dpkg-checkbuilddeps: Unmet build dependencies: libdbus-1-dev:native (>= 1.4) libexpat1-dev:native (>= 2.0.0)" when i did $ sbuild --host armhf, on just pushed lp:ubuntu/libnih22:24
xnoxcjwatson: that's using trusty chroot, am I missing something? should i use some specific build-deps resolver in sbuild?22:25
mlankhorstslangasek: sorry I was eating at that time :(22:39
mlankhorstand had to be somewhere at 9, evenings are terrible22:39
slangasekmlankhorst: eating, in the middle of UDS?  surely not22:39
barrykirkland: LP: #125345822:44
ubottuLaunchpad bug 1253458 in byobu "Switch to Python 3" [Undecided,New] https://launchpad.net/bugs/125345822:44
perocan anyone help me get back the unity webapps extension in chromium? it somehow disappeared and i'm at a loss on how to get it back22:48
mlankhorstoh well night23:11
=== freeflying is now known as freeflying_away

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