coderangerAnyone around that knows the first magic to put in the Sources file to make it functionally empty? Trying to make a repo that has deb-src be a noop.00:00
infinitycoderanger: Just make it empty?00:06
infinitycoderanger: Of course, if you're distributing binaries built from copyleft (like, GPL) source, you really don't want your Sources to be empty. :P00:07
coderangerinfinity: "Encountered a section with no Package: header"00:07
coderangerinfinity: These aren't packages built from normal debian-style sources, so deb-src is meaningless00:08
coderangerbut easier to make it a noop than to explain to users why apt-add-repo is wrong :-000:08
infinitycoderanger: So just don't have a Sources.gz at all if you don't intend to serve deb-src...00:09
infinitycoderanger: apt-add-repository only turns on matching deb-src if people call it with -s/--enable-source00:09
coderangerIts the default00:09
coderanger(unless apt-add-repo was changed since 12.04)00:10
infinityAnyhow, I don't get the error you do with a zero-length Sources file.00:12
infinity(Just tested)00:12
coderangerHmm, what about with a single newline in it00:12
coderangerS3 was grumping about 0-byte files00:12
infinityThat would confuse apt, yes.  The first line of Packages/Sources shouldn't be a newline.00:12
coderangerOkay, hmm00:12
infinityIf you're doing this in a storage scenario that hates zero-byte files:00:13
infinity(base)adconrad@cthulhu:~/source-test$ : > Sources && gzip -c Sources > Sources.gz00:13
infinity(base)adconrad@cthulhu:~/source-test$ ls -l00:13
infinitytotal 400:13
infinity-rw-rw-r-- 1 adconrad adconrad  0 Jan  5 17:13 Sources00:13
infinityAnd then upload Sources.gz, but not Sources.  Problem solved.00:13
infinity-rw-rw-r-- 1 adconrad adconrad 28 Jan  5 17:13 Sources.gz00:14
coderangerHah, fair enough00:14
infinityMost real Debian/Ubuntu mirrors never publish the non-compressed versions anyway.00:14
coderangerYeah, I just have the tool generate them for the hell of it00:14
* mwhudson has to laugh at this00:17
coderangerHmm, the zero-byte error might be libcloud instead of S3, sigh00:17
coderangermwhudson: Hmm?00:21
mwhudsoncoderanger: the battle between different unhelpful technologies and the solution of compressing a 0-byte file into a larger thing00:22
coderangermwhudson: lolcomputers00:24
infinityWell, given the HTTP overhead in requesting and returning a 0-length file, making it 28 bytes isn't really making the problem much worse. :P00:26
RAOFHm. Why isn't upstart-dbus-bridge started on the system init?00:29
mwhudsonRAOF: hey, can i bug you about my x problem quickly?00:39
RAOFmwhudson: Sure00:39
mwhudsonRAOF: every so often i get a short freeze, something restarts00:39
mwhudsonand then some font render buffer is corrupted and i get this sort of thing:00:39
mwhudsonRAOF: http://people.canonical.com/~mwh/mangled.png00:40
mwhudson(x220 so sandybridge graphics)00:40
mwhudsonRAOF: is this a known problem?00:40
infinityI get that sometimes with my i915 lockups.00:41
infinityAnd sometimes not.00:41
RAOFWhee! I love font cache corruption.00:41
infinity(The corruption, that is)00:41
mwhudsonyeah, it's not every time00:41
mwhudsonthe lockups themselves seem to happen a lot more when spotify is running, but that might just be anecdata00:41
RAOFI'm not aware of that problem, but I'm less involved in the X bug triage than I once was :)00:41
infinitymwhudson: Say, since you're another poor Sandy user, maybe you've seen the weird bug that no one else has ever seen...00:42
mwhudsonRAOF: heh, fair enough00:42
mwhudsonis there some way to dump the cache at least?00:42
infinitymwhudson: When you open new windows (a new Firefox, a new gnome-terminal, whatever), do they sometimes seem to lose the ability to repaint themselves except when being moved?00:42
mwhudsoninfinity: not seen that one00:42
infinityWeirdst bug ever, cause I seem to be the only one who sees it. :/00:43
mwhudsoninfinity: you got lucky with hardware?00:44
infinityI guess, but it's hardly obscure hardware.00:44
=== freeflying_away is now known as freeflying
infinityBasically identical to your X220 under the hood.00:45
mwhudsoni mean, you have slightly broken hardware00:45
mwhudsonit's not like i'm the only person in the company with an x220 either :)00:45
infinityAlso possible, but I'd expect broken hardware to behave in more obviously broken ways, not in ways that look like software bugs. :P00:45
infinityWhereas the Sandy lockups and font cache corruption are things everyone experiences, AFAIK, to varying degrees.00:46
infinityBut my weird "new windows don't know how to window correctly" thing seems unique.00:46
infinityOr other people just have never sorted out how to describe it and close their non-responsive (not actually, but not painting sure LOOKS unresponsive) windows out of frustration...00:46
=== panda is now known as Guest88517
=== shuduo|afk is now known as shuduo
alkisgdpkg: error processing /var/cache/apt/archives/gstreamer1.0-plugins-ugly_1.2.2-1ubuntu2_i386.deb (--unpack):04:17
alkisg trying to overwrite '/usr/share/locale/id/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-ugly:i386 0.10.19-2ubuntu204:17
RAOFalkisg: Yeah, join the club :)04:17
* alkisg removed gstreamer 0.10 ugly to work around that...04:18
RAOFYou're looking at bug #126614104:18
ubottubug 1266141 in gst-plugins-ugly1.0 (Ubuntu Trusty) "package gstreamer1.0-plugins-ugly 1.2.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/locale/sl/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-ugly:amd64 0.10.19-2ubuntu2" [High,Triaged] https://launchpad.net/bugs/126614104:18
alkisgThanks, as long as it's reported... :)04:18
* RAOF just --force-overwrite'd it04:18
Logan_slangasek: Hey, are you around?04:53
NoskcajLogan_, Any chance you could look at some stuff on the sponsoring queue? I've got 20+ packages, some of which we really need for xubuntu.04:56
NoskcajAlso some lubuntu and ubuntu-gnome stuff04:56
Logan_Noskcaj: Shit, that's a huge backlog. I'm dealing with Bug 1266141 right now (look at how many people affected, ugh), but I'll take a look ASAP.04:57
ubottubug 1266141 in gst-plugins-ugly1.0 (Ubuntu Trusty) "package gstreamer1.0-plugins-ugly 1.2.2-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/locale/sl/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-ugly:amd64 0.10.19-2ubuntu2" [High,Triaged] https://launchpad.net/bugs/126614104:57
Noskcajthanks. I'm one of the people affected by that bug, so a fix would be great04:57
Logan_Oh wonderful. More pressure. :P04:58
Logan_I managed to delete my entire home directory, so working on that first.04:58
NoskcajLogan_, nice work ;)05:02
Logan_Oh, believe me, I'm killing it today.05:02
Logan_rm -rf gst* != rm -rf gst *05:02
Logan_I don't know why I did that.05:02
Logan_I think I might have to back out all of the changes to the gstreamer packages if the fix I'm thinking of doesn't work.05:04
Logan_debdiff. The moment of truth.05:05
Logan_Oh thank god. It worked.05:05
* Logan_ hugs Noskcaj.05:06
* Noskcaj hugs Logan_ 05:06
Logan_Happiness everywhere. Alright. Lemme upload.05:06
NoskcajHopefully my PC will update again now05:06
Fudgeit effects me too but just force installed it as suggested05:09
FudgeLogan_:  the pressure you must feel :D05:12
Logan_Tell me about it.05:12
Fudgeshe'll be good mate, look at all those 'effected people' cheering you on...05:13
Logan_Uploaded. Phew.05:15
Logan_Noskcaj: Now, onto the sponsorship queue.05:15
NoskcajLogan_, Could https://code.launchpad.net/~noskcaj/ubuntu/trusty/xfce4-session/light-locker/+merge/196436 be one of the ones you look at? It's a two month old merge and we still need it in xubuntu05:17
* Logan_ looks.05:17
Logan_Noskcaj: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1254366/comments/505:18
ubottuUbuntu bug 1254366 in xfce4-session (Ubuntu) "Add support for light-locker in xflock4" [Undecided,Confirmed]05:18
NoskcajWe're wanting to fix this a a basic, no regression way now. Then get it all working fully in upstream for the next release05:19
Logan_Noskcaj: The patch looks alright. So Jarno is just concerned that it's running a lock command for every possible one, without considering whether or not they are running?05:21
Logan_Does this cause any error?05:22
Logan_I guess not, since it's going to /dev/null...05:22
NoskcajLogan_, no errors, we've been calling two commands for ages05:22
Logan_Have you tested it with and without light-locker?05:22
NoskcajI haven't personally, but some of the other xubuntu guys have05:22
Logan_And it's all good?05:22
Logan_Noskcaj: ^, and you didn't credit Sean.05:24
Logan_And can I have an upstream bug where this patch was forwarded?05:25
Logan_Sorry I'm being such a stickler. It's just the process. :)05:25
NoskcajI'll try and find one. I think sean might have fixed it upstream already05:27
Logan_Okay. Try to find a commit.05:31
Logan_I'll look into the gnome-tweak-tool merge now.05:31
Logan_Noskcaj: Shouldn't we wait for Debian?05:38
Logan_At least report it, and maybe forward the patch. We can merge if we approach feature freeze with no response.05:39
Logan_Another sponsor may disagree, but that's my opinion on new upstream versions.05:39
NoskcajLogan_, Request of darkxst, the gnome dev lead. It's been in their testing PPA for ages. Plus pkg-gnome is understaffed, i've got stuff there needing sponsorship for 6 months05:40
Logan_Fine. Then at least report a bug in Debian requesting a new upstream release.05:40
Logan_I'll test the merge.05:40
Logan_I got two conflicts. Please fix.05:43
NoskcajWill do. This is why PPA merging is a pain05:43
NoskcajI'll redo the merge, since i probably broke something05:51
NoskcajLogan_, For some reason that merge error comes up even with just bzr merge-upstream and a dropped patch06:14
Logan_Noskcaj: That's odd.06:14
NoskcajI might leave this one till debian update it06:23
xnoxRAOF: hm, dbus-bridge has been changed to run on session-init only these days I think?! Do you have /etc/init/upstart-dbus-bridge.conf that is RC ?07:04
RAOFxnox: I did not have an /etc/init/upstart-dbus-bridge.conf until I modified the one from it out of /usr/share/upstart/sessions07:05
RAOFI was just playing with watching NetworkManager events and autogenerating apt-cacher-ng's mirror substitution file from mirrors.ubuntu.com when I change networks, and realised the reason that my job wasn't triggering is that the system init isn't watching dbus :)07:07
xnoxRAOF: i see, so you are the rare case where you _do_ want it on the system-init =)07:10
RAOFI just wondered if there was some reason why the system-init no longer watched dbus :)07:10
=== geser_ is now known as geser
=== alkisg1 is now known as alkisg
xnoxRAOF: well, in session-init (were most dbus events are used at the moment) it was that "session dbus" events were naked, yet "system dbus" events would arrive with "sys:" prefix. So we moved system-init system-dbus-bridge to session-init only.07:18
xnoxif we ever get dbus-bridge using jobs in default / system-init, then we can look into having sys:dbus events filtered out on the session-init size.07:19
=== sabdfl_ is now known as sabdfl
=== NCommander is now known as 14WABSAYH
=== mthaddon` is now known as mthaddon
NoskcajLogan_, On the xfce-session stuff, there's no upstream bug, but the upstream devs also work on light locker, so it will be done soon. please approve the branch09:00
Logan_Noskcaj: Please file a bug. :)09:01
NoskcajI'll do that tomorrow, need sleep now.09:01
tester56what does apport-noui do exactly? (it is stated that it automatically submit bugreports, but does it do so when "sumbit bug reports to canonical" is disabled?)09:50
dokojamespage, why is this golang patch not applied in debian?10:19
jamespagedoko, differences in the way dpkg detects shared library deps (I think)10:19
jamespagedoko, I can probable persuade the debian maintainer to take that patch10:20
jamespageI think it should not effect the debian builds negatively10:20
=== schmidtm_ is now known as schmidtm
dokowgrant, your pykde4 upload now lets python3-pyqt4 depend on both libpython3.3 and libpython3.4. it should not directly link the extension against the shared library10:28
=== Lutin_ is now known as Lutin
dokoI do love embedded waflib copies everywhere ...11:06
ogra_can't have enough of them :)11:06
jtaylorcan someone reproduce the skimage adt failure?11:12
jtaylorI can't in a chroot or adt-run11:12
jtaylor(ignore the 3.4 failure, adt chokes on py3.3 which I can'T reproduce)11:15
=== Sweetsha1k is now known as Sweetshark
=== _salem is now known as salem_
dokojtaylor, https://launchpadlibrarian.net/161710633/buildlog_ubuntu-trusty-arm64.fftw3_3.3.3-7ubuntu1_FAILEDTOBUILD.txt.gz12:32
dokodid you introduce this?12:32
doko  * enable runtime detected neon support for arm6412:32
jtaylorI was told (here) arm64 has neon12:32
jtaylorso why doesnt it work? no hardware or gcc does not support it?12:35
xnoxjtaylor: neon is uncoditional on arm64 and it's supperset of armhf, so one doesn't need to specify neon build flags12:36
jtaylorinteresting, gcc could ignore the flag then ...12:37
jtaylorfix requires a change the the build system12:37
xnoxjtaylor: it's wrong to set it. cause you might be forcing an armv7 build instead of armv8.12:37
jtaylordropping --enable-neon will disable neon altogether even if its auto-on12:37
xnoxjtaylor: remember that arm64 can execute armv7/32bit binaries with neon.12:38
jtaylorpatches accepted, I don't have the hardware to test it12:38
xnoxjtaylor: mk-sbuild --arch arm64?12:38
xnoxjtaylor: mk-sbuild --arch arm64 trusty?12:38
jtaylorthat works now?12:39
xnoxjtaylor: it worked since trusty opening, saucy release had small bug in qemu-debootstrap however.12:39
jtaylorbut I don't use sbuild12:40
xnoxjtaylor: use whatever you use, there is qemu-user-static binary for arm64.12:41
xnoxso you can execute native arm64 chroots.12:41
jtaylormeh I don't have time for that now, patch it out, I'll fix it when it gets a problem in debian12:41
jtaylorfftw needs merging anyway12:41
xnoxjtaylor: yeah back it out in ubuntu or debian or both.12:42
xnoxcause otherwise fftw will be stuck in -proposed.12:42
jtaylorits main so nothing I can do12:42
jtayloror better its more time efficient for someone else to drop the two lines12:43
xnoxjtaylor: i think you should do it =)))) you could have pastebined patch "enabling neon arm64" asking anybody here to test it.12:43
jtaylorI did12:43
jtaylorwas told it works, so I did it to save an extra upload12:44
xnoxjtaylor: and there was a non-ftbfs build log?12:44
jtaylorat the time it was said qemu arm64 does not work yet12:44
xnoxjtaylor: yes, neon works on arm64. that build FTBFS however.12:44
jtaylorasier to just do it on real hardware and see then12:44
jtaylorwhich is what I did12:45
jtaylornow we have the result :)12:45
jtaylorand can fix it12:45
jtaylorI'm happy to take any patches and forward them upstream12:48
jtaylorif you don't want to bother creating one drop the two lines in debian/rules and disable it altogether12:48
jtaylorI may have time to look into it myself but not today12:48
jtaylorsorry for abusing ubuntu as my testing platform, should have asked for a buildlog when I did this12:49
jtaylorinformation needed for a proper patch is how to detect arm64 in configure.ac12:53
jtaylorhm a debian specific one is simpler as we can assume gcc supports fpu=neon12:55
cjwatsonjtaylor: aarch64*12:55
jtaylorjust dropt he gcc check12:55
cjwatson(in case "${host_cpu}" etc.)12:55
jtaylordo you know an example of the top of your head?12:55
cjwatsonI was basing that on the "dnl configure options" block near the top of configure.ac12:56
cjwatsonthe arm64 triplet starts with "aarch64" so you can use that12:56
cjwatsoncf. "dpkg-architecture -aarm64 -qDEB_HOST_GNU_TYPE" (ignore stderr)12:57
mitya57jtaylor: If you prefer pbuilder over sbuild, then 'pbuilder-dist trusty arm64 create' should do the thing12:57
jtaylormitya57: not in saucy :/12:57
jtaylornot running trusty yet12:57
jtayloroh no12:57
jtaylorI'm just dumb and mixed upt he ordering12:57
jtaylork then I can give it a try today12:58
mitya57You can always backport ubuntu-dev-tools & qemu-debootstrap12:58
jtaylorqemu backport requires more backports :/13:01
xnoxjtaylor: yeah, for host_cpu aarch64 it should define have_neon & not mangle gcc flags. But do get that test-built before uploaded.13:01
xnoxjtaylor: qemu-user-static are statically linked binaries... so just download the deb & unpack arm64 static binary out of it.13:01
xnox(or install trusty qemu-user-static)13:01
jtaylornice thx13:02
xnoxjtaylor: or run nested chroots.... =) chroot into trusty, then create arm64 pbuilder/sbuild/whatever chroot there for arm64.13:02
jtaylorwhy must arm64 look like amd64 :( I always click the wrong linkg when downloading debs13:03
jtaylor /usr/sbin/qemu-debootstrap --arch arm64; E: Sorry, I don't know how to support arch13:05
jtaylorversion 1.7.013:06
* xnox votes to rename all arches using UUIDs13:06
xnoxjtaylor: yeah that's the other bit i've fixed in trusty. it's a shell script with hard-coded names of arches it knows about....13:06
xnox(or maybe it wasn't shell, it's just a script...)13:06
jtaylorI installed the trusty versiion13:08
jtaylorxnox: ^13:09
* xnox wonders if it got broke again.13:10
xnoxhallyn: looks like 1.7.0+dfsg-2ubuntu1 merge reverted/dropped changes I've applied in 1.6.0+dfsg-2ubuntu413:13
xnoxhallyn: where/how should they be done, to not get lost? as qemu-debootstrap for arm64 is now broken again...13:14
xnoxdebian/binfmts/qemu-arm64 possibly also reverted, not sure.13:15
didrocksstgraber (or other lxc gurus): do you know if you can mount /proc in a lxc container? My debootstrap is failing me on that one: W: Failure trying to run: chroot /var/cache/pbuilder/trusty-amd64/base.cow/. mount -t proc proc /proc13:24
asacdidrocks: not sure if its relevant, but i see something about lxc config to mount proc/sys here: http://l3net.wordpress.com/2013/11/03/debian-virtualization-lxc-debootstrap-filesystem/13:25
asaclxc.mount.entry=proc /proc proc nodev,noexec,nosuid 0 013:25
asaclxc.mount.entry=tmpfs /dev/shm tmpfs  defaults 0 013:25
didrocksasac: I guess this is to mount /proc into the container, let me look/have a try13:25
didrocksasac: yep, that didn't do it from what I tried13:29
jtaylorxnox: ping me when its fixed and I'll have a look (bin/qemu-arm64-static also does not exist)13:29
jtaylorthat its in proposed doesn't matter, the only really relevant change is arm64 support13:29
asacogra_: xnox: do you know about lxc (see didrocks question above)? if not, anyone besides stgraber who might know?13:31
jtayloractually is arm64 build now required for proposed migration?13:32
ogra_there shouldnt be anything blocking you from mounting /proc13:32
didrocksogra_: weird, I used the ubuntu template to create my container though13:33
xnoxdidrocks: i think by default you cannot mount / remount proc from inside the lxc container. You should either specify it in the template on the host side, or grant the container to do so (note it's a security risk and apparmor will block from doing so as well)13:33
xnoxdidrocks: what's your use-case / what are you trying to achieve?13:33
ogra_xnox, better ask what is pbuilders use-case :)13:34
didrocksxnox: I'm just trying to test locally my new ci system (pbuilder/cowbuilder are used to create source package) and I didn't want to install jenkins on my desktop, so lxc container ;)13:34
xnoxjtaylor: the requirement is imposed by britney and it's same as it always been, the built architectures should not regress - since there if fftw3/3.3.3-5ubuntu1 built on arm64, it should continue to be built on arm64.13:34
xnoxjtaylor: and enforced by release & archive teams =)13:35
didrocks(and the jenkins CI job is using then the pbuilder/cowbuilder, that's why I'm trying to create one inside the container)13:35
xnoxdidrocks: right, i think we do apparmor confinment on the lxc containers by default, but there was a  key / config to disable apparmor confinment for a given lxc container.13:35
* asac lunch13:36
xnoxdidrocks: (reboot of the host may be required)13:36
xnoxdidrocks: alternatively $ juju bootstrap lcy01 / lcy02 and have disposable things to install jenkins on ;-)13:36
didrocksxnox: interesting, ok, let me have a look :)13:36
cjwatsonxnox: not so much enforced as we generally decline to overrule the automation :)13:36
cjwatsonjtaylor: full docs: https://wiki.ubuntu.com/ProposedMigration13:37
didrocksxnox: right, the thing will be jujuifed, but right now, local development :)13:37
xnoxdidrocks: i at times launch throwaway instances in couple of click through dashboard.cs.c.c  to install things like jenkins to not trash my host, nor sufficate from my small VM sizes / lxc container restrictions.13:38
caribouxnox: I gave a shot to merging backuppc following Logan's confirmation that he would not work on it13:39
tester56will qt 4.8.5 land in trusty?13:45
mitya57tester56: yes, it's almost ready13:47
mitya57Waiting for Rohan to do some final testing & upload13:47
ogra_pfft ... 4.8 ... use 5.x !13:48
tester56would resolve a few crashes: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/120052313:48
ubottuUbuntu bug 1200523 in qt4-x11 (Ubuntu Saucy) "Some of the kubuntu patches break plasma" [Undecided,Fix released]13:48
tester56see also https://bugs.kde.org/show_bug.cgi?id=30293113:49
ubottuKDE bug 302931 in general "changed a value in system settings and clicked APPLY [@ Plasma::FrameSvgItem::~FrameSvgItem]" [Crash,Resolved: downstream]13:49
tester56just experienced one crash yesterday with trusty13:49
=== Fudgey is now known as Fudge
mitya57the first bug is marked as already fixed13:50
caribouxnox: I Have a bzr branch ready if you want to have a look13:51
mitya57the second one looks like the same issue13:51
xnoxcaribou: make a merge proposal against lp:ubuntu/$package13:55
xnoxcaribou: leave the default reviewers.13:55
xnoxcaribou: and request a second review from me (~xnox)13:55
xnox(that way i get notified, and it will also land in the sponsorship queue report)13:55
caribouxnox: I used lp:ubuntu/backuppc/trusty-proposed as a reference branch, is that correct ?13:55
tester56mitya57: yeah is the same issue, but according to the bug report it is only resolved using 4.8.5 ...13:55
xnoxcaribou: lp:ubuntu/backuppc13:57
caribouxnox: the source branch ?13:57
xnoxcaribou: if trusty-proposed was ahead of ubuntu/backupppc, you'd add your changes on top of lp:ubuntu/trusty-proposed/backuppc but still make merge proposal into lp:ubuntu/backuppc13:58
caribouxnox: ok, I'll check both & rebuild if needed13:58
xnoxcaribou: it doesn't matter in this case as both lp:ubuntu/backupppc and lp:ubuntu/trusty-proposed/backuppc are the same, 3.2.1-4ubuntu2 is last version in either of the branches.13:58
caribouxnox: k13:59
knocteis medibuntu down? I can't access http://packages.medibuntu.org/14:06
ogra_knocte, support is in #ubuntu14:06
ogra_(and i think medibuntu stopped a while ago)14:07
stgraberdidrocks: you can but not with the default apparmor profile as doing so is a security risk.14:10
didrocksstgraber: ok, that confirms then, I'll fetch your documentation as well on what needs to be disabled then14:12
xnoxstgraber: as alternative, i've directed didrocks to use beefy canonistack instances, instead of local lxc containers.14:13
stgraberdidrocks: let me grab you my sbuild LXC apparmor profile, that should do the trick for you.14:15
didrocksstgraber: ah, excellent, that should unblock me for the short term (like today) and I'll then look at canonistack within the week14:16
stgraberdidrocks: set lxc.aa_profile to lxc-container-default-builder for your container14:17
stgraberdidrocks: then create /etc/apparmor.d/lxc/lxc-default-builder containing: http://paste.ubuntu.com/6703385/14:17
stgraberdidrocks: after that, do "sudo /etc/init.d/apparmor reload" and restart your container14:17
stgraberdidrocks: those rules are enough for me to run sbuild here (used for LXC's own CI environment), I'm only guessing they should work with pbuilder too. If something still fails, let me know (with a copy of the dmesg output) and I'll tell you what to add.14:19
mitya57Funny MP: https://code.launchpad.net/~chris.gagnon/kubuntu-packaging/enable-unit-tests-qtbase-opensource-src/+merge/200535 - states that DFSG is not mandatory in Ubuntu14:20
mitya57I believe it is, at least in main/universe14:20
cjwatsonmitya57: He's sort of correct; for non-code elements the Ubuntu licensing policy states that we'll consider them case-by-case14:21
cjwatsonThough it's still good practice to do things in a Debian-mergeable way where possible14:22
cjwatsonmitya57: http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-archive.html#s-ulp14:22
mitya57Yes, will ask if we can skip tests that need such data14:22
cjwatson(last para of that section)14:23
didrocksstgraber: worked perfectly! Thanks a lot :)14:23
stgraberdidrocks: good to hear! np14:25
hallynxnox: hm.  well i keep the source at github.com/hallyn/qemu, but I looked at all the debdiffs in the archive so shouldn't have lost any changes.  i'll look at 1.6.0+dfsg-2ubuntu4 again - though my internet is dead so i'm on ip-over-pigeon right now.14:43
mlankhorstis it just me or is the toolchain messed up ?14:44
mlankhorstchecking if gcc -std=gnu99 static flag -static works... *** Error in `/usr/bin/ld': corrupted double-linked list: 0x091a6558 ***14:44
mlankhorston i38614:44
mlankhorstgcc -std=gnu99 -o conftest -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -DPRE_RELEASE=0 -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-Bsymbolic -static conftest.c15:00
mlankhorst$ cat conftest.c15:01
mlankhorstint main(){return 0;}15:01
mlankhorst/usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.24 assertion fail ../../bfd/elflink.c:1305315:08
dholbachxnox, seb128: do you know what might cause this: http://paste.ubuntu.com/6703638/ ?15:08
dholbachit happens when running http://paste.ubuntu.com/6703644/15:08
mlankhorstanyone wants to look at that toolchain failure?15:08
seb128dholbach, I don't15:09
dholbachseb128, should I file a bug for it?15:10
xnoxdholbach: arch mis-match? what's your "host" / main arch, and which foreign arches are enabled?15:10
xnoxdholbach: you shouldn't need to install "ubuntu-sdk-libs-dev:armhf" that's already installed (abeit partially)15:10
mlankhorstdoes gcc -fPIE -pie make sense on a static binary?15:11
xnoxmlankhorst: on some arches =)))))))15:11
mlankhorstxnox: -static -fPIE -pie ?15:11
dholbachxnox, I just wanted to make sure that everything's installed, to make sure it works as part of instructions for folks to compile their QML extensions15:11
mlankhorstwell I guess it might15:11
xnoxmlankhorst: oh pie, not pic. hm.... not sure.15:11
seb128dholbach, I guess you can, though I'm not the best person to ping about multiarch issues, let's see if xnox manages to help you ;-)15:12
mlankhorststill staticaly linked and movable15:12
cjwatsondholbach: no, you shouldn't put that in instructions.  anything that click chroot create doesn't already install that's needed would be a bug in click15:12
xnoxdholbach: the instructions should be - click create, cmake compile.15:12
cjwatsonplease don't work around software bugs in instructions ...15:12
cjwatson(if it is a bug)15:12
xnoxcjwatson: should i seed cmake:native somewhere, or can you install one, btw?15:13
dholbachcjwatson, no, I didn't want to work around software bugs - I just assumed that ubuntu-sdk-libs-dev would give people everything they potentially need to compile their QML extensions15:13
xnoxdholbach: where are these instructions you are talking about?15:13
cjwatsondholbach: click chroot is already meant to install everything they need15:13
dholbachxnox, there are none right now15:13
dholbachcjwatson, ok, thanks15:13
cjwatsonxnox: send me an MP with a suitable change to click/chroot.py?15:13
xnoxcjwatson: ack.15:14
dholbach(and this was just for playing around locally)15:15
dholbachtedg, who could nudge https://code.launchpad.net/~ted/upstart-app-launch/tracking-arch/+merge/196194 along? :)15:16
tedgdholbach, charles_ has been doing most of those reviews, considering the weather, sending hot chocolate is probably your best bet :-)15:17
dholbachtedg, thanks15:18
dholbachcharles_, if you have a bit of time, it'd be fantastic if you could review the MP mentioned above :)15:19
charles_dholbach: I'll review it asap, it's third on my list right now15:31
* dholbach hugs charles_15:31
dholbachthanks a bunch!15:31
charles_hm, when did I pick up an _ on my nick15:31
=== charles_ is now known as charles
xnoxtedg: that would be Ice Frapuchinno on arrival ;-)15:32
tedgxnox, You clearly don't believe in the magic that is dholbach ;-)15:33
tedgIt is freaky cold though.  Staying inside today.15:33
xnoxtedg: very cold here as well, i've put on socks today with my flip-flops. =))))))15:34
ogra_tedg, just come over to europe ... we are stuck in eternal fall/spring here15:34
mlankhorsthttps://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1266492 causes a FTBFS when attempting to rebuild existing xorg-server too15:34
ubottuUbuntu bug 1266492 in binutils (Ubuntu) "ld:i386 crashes with -static -fPIE -pie" [High,New]15:34
xnoxtedg: is it just me or click app launcher can block until the app is started? e.g. like with normal upstart job one has $ start foo; and $ start --no-wait foo. First one will block, until foo is started. The second one, will return immediately.15:36
xnoxtedg: i'm asking because starting click apps in the  emulator, on underclock CPUs of cloud instances take forever wall-clock time, and autopilot currently timesout within "10 seconds" (actually 10x1s sleeps, which are subject to poor clock resolution)15:37
tedgxnox, I think that should work, but the cascading may break it.  I haven't tested.  But that changes a lot in the proposed MRs, so I wouldn't test on trunk today.15:37
dholbachtedg, I could ask the XKCD guy to find out how hot a hot chocolate would need to be to survive 8200km and still be nice and warm ;-)15:37
xnoxtedg: i'm testing as it is on the current system-images (stock, no ppas enabled etc.)15:38
tedgdholbach, Wonder if you could get one of those containers they store liquid nitrogen in... they're very insulated.15:38
xnoxdholbach: isn't that same as http://what-if.xkcd.com/1/ ?15:38
tedgxnox, That's old :-)  You might see if the behavior is different if you call "application-click" directly.15:39
xnoxtedg: right, let me compare with what autopilot code actually calls....15:39
dholbachxnox, if the hot hot chocolate experiment resulted in http://what-if.xkcd.com/imgs/a/1/05.png I'd probably try tedg's approach first :-)15:39
xnoxtedg: autopilot does "$ start application APP_ID=$(app_id)" that doesn't block does it?15:42
xnox(can it be optionally made to block?)15:42
tedgxnox, It calls "start" for the sub-jobs, which should block, no?15:45
tedgxnox, But, again, that's going to change a lot, so I'd not want to fix it for trunk today.15:45
xnoxtedg: right, i'll work around that in my juju charm then.15:46
xnox(for now)15:46
* xnox needs proof of concept anyway.15:46
bdmurrayxnox: bug 1022815, which you commented on at one point in time has had a patch added16:23
ubottubug 1022815 in cryptsetup (Ubuntu) "initramfs should try password against other devices" [Undecided,Confirmed] https://launchpad.net/bugs/102281516:23
=== sarnold_ is now known as sarnold
=== marcoceppi_ is now known as marcoceppi
=== tkamppeter_ is now known as tkamppeter
charlesdholbach, ted: https://code.launchpad.net/~ted/upstart-app-launch/tracking-arch/+merge/196194 approved17:37
hallynjdstrand: regarding test-libvirt.py in qrt;  it does a device-detach then checks whether the device was removed from apparmor profile.  However, libvirt now waits for qemu to say the device is removed before actually removing the device, and since the guest image doesn't do acpi that never happens18:37
hallynjdstrand: so do you prefer to (a) add acpi to the guest image, (b) check that the device is in the vm's xml and skip the apparmor check if so, or (c) skip the test on new libvirt?18:37
smagouncyphermox: Hi, do you know if anyone is looking at the nm-applet bug that results in multiple "Authetication Required" dialogs onscreen? It's lp:#1224040; the bug is still present in 14.04.19:31
cyphermoxsmagoun: it was supposed to have been fixed long ago, I'm going to ask upstream. I certainly haven't seen it happen in a long while here and I used to get that to show up pretty easily19:41
smagouncyphermox: It's easy enough for me to reproduce. I came back to a machine that was idle for 2 weeks, if my math is right there were 3196 dialogs onscreen. :/ nm-applet was using 2.4GB of ram19:42
cyphermoxoh, I believe you :)19:42
smagouncyphermox: anyway, thanks  for checking with upstream. Let me know if there is anything I can do to help debug/test!19:43
cyphermoxI discussed this with dcbw a few times already, I'll just remind him and let him know it's still broken19:44
sarnoldoooof, 3196 dialogs? did you grab a screenshot?19:46
roadmrsarnold: I think all the dialogs are superimposed, so they look like a single dialog (but with an evil thick black border)19:47
sarnoldroadmr: heh, those must be some very menacing pixels indeed :)19:48
roadmrsarnold: haha :) yes, it's just the merged drop shadows from all the dialog but it looks weird somehow19:49
smagounsarnold: no screenshot no, but I have a witness (pmcgowan, who is not in this room right now) . You can see all the dialogs using super-w in unity, which is sloooooooooooow with that many dialogs19:50
sarnoldsmagoun: oh well, it sounds less impressive than I hoped for. :)19:52
=== timrc-afk is now known as timrc
=== wendar_ is now known as wendar
nashantHi guys. Can anyone tell me where to find the python indicator api docs? Every link I go to says it's gone. I'm fed up with the rubbish power indicator with no brightness control21:20
Noskcajcjwatson, bug 126651621:26
ubottubug 1266516 in console-setup (Ubuntu) "New version available upstream: 1.104" [Undecided,New] https://launchpad.net/bugs/126651621:26
jdstrandhallyn: ok, I'm here (and still trying to climb out of holiday backlog)21:35
jdstrandhallyn: I think ideally we would adjust the vm to have acpi, since the code is all still there to do this in libvirt and we should be testing for it21:36
jdstrandhallyn: iirc, the libvrt vm is dapper. if there were other reasons to update the vm that would be helpful for adding tests, then I would go that route. otherwise, skip the test until such time as you want to regenerate the vm?21:38
hallynjdstrand: how did you generate the vm?  wonder if i coudl just update sources.list and have it work :)21:40
jdstrandhallyn: see QRT/scripts/libvirt/README.qatest21:41
jdstrandhallyn: basically, that should work. it is just ubuntu-minimal + ssh21:42
cjwatsonNoskcaj: ack, will try to look this week; it generally takes some time21:42
hallynbuilt using vmbuilder, which is being dropped :)21:42
nashantHi guys. Can anyone tell me where to find the python indicator api docs? Every link I go to says it's gone. I'm fed up with the rubbish power indicator with no brightness control21:44
cyphermoxsmagoun: I think I may have just made sense of it now... going to test a patch21:46
=== blueyed_ is now known as blueyed
smagouncyphermox: NIce! I'd be happy to test too22:16
stgrabercjwatson: I've got an e-mail in the u-d-a queue when you have a minute22:19
=== sraue_ is now known as sraue
=== salem_ is now known as _salem
infinitystgraber: Accepted.23:12

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