[00:31] <ScottK> cyphermox: I'm looking at bluez and trying to figure out why it depends on python-gobject?  AFAICT from grepping the code python-gobject is only used in the tests.  I'm asking because it's pulling python-gobject and another stack of things into the kubuntu seeds.
[01:55] <cyphermox> ScottK: ok. well, I'll be happy to drop it if it's possible. I'm about to do an upload; I can check now
[01:55] <ScottK> cyphermox: Thanks.
[01:56] <cyphermox> ah, I see
[01:56] <cyphermox> ScottK: I kind of like having these "tests" around; though maybe they'd be better suited in a separate package
[01:57] <ScottK> That or ship the tests, but drop python-gobject to Suggests.
[01:57] <ScottK> I think for tests that aren't automatically run, that's reasonable.
[01:58] <cyphermox> ScottK: those things really attempt to give you information about bluetooth devices more than actually being tests, but I think that's reasonable still
[02:08] <cyphermox> ScottK: did you file a bug about this?
[02:10] <ScottK> cyphermox: No.
[02:10] <cyphermox> ok
[02:29] <psusi> isn't dh_translations supposed to remove the .mo files from the package and put them in the langpack isntead?
[02:47] <micahg> cyphermox: it would have been nice to document reason for the drop to suggests in bluez in a bug or in the changelog itself
[03:05] <TheMuso> @pilot out
[03:05] <slangasek> psusi: no, that's the job of pkgbinarymangler
[03:10] <psusi> slangasek, ohh... so when I build the binary package, the .mo files are still there, but when it hits the archive, they get stripped?
[03:10] <slangasek> psusi: pkgbinarymangler is installed in the build chroots on the Ubuntu buildds, and strips them out as part of the package build
[03:11] <psusi> I see
[03:11] <slangasek> (by diverting/wrapping the commands used for building, making it transparent to the actual package)
[03:12] <micahg> you can do the same locally with a properly configured sbuild (and probably pbuilder as well)
[04:07] <benonsoftware> Hello
[05:45] <pitti> Good morning
[05:45] <pitti> cjwatson: waiting for micahg; I asked yesterday, not sure about the current status
[05:45] <pitti> ev: StacktraceAddressSignature is many to one
[05:46] <pitti> ev: in practice, I found that > 90% of our bugs in the db just have one address signature, but some have 5, and one had 10
[05:46] <pitti> SpamapS: ah, yes
[05:46] <pitti> @pilot out
[06:41] <poolie> raof, hi, current drm-intel-next has basically the same problems
[06:41] <RAOF> poolie: :(
[06:42] <poolie> i guess i could try digging in to that part of the kernel
[06:42] <RAOF> Now, I've dropped context.  What was the problem, again?  Was it “VT-d makes my system crazyslow?”
[06:42] <poolie> ah, that actually is adequately worked around by turning it off
[06:43] <poolie> i guess ideally the kernel would cope if it was turned on
[06:43] <poolie> no, this is bug 745112 (sorry for not quoting that) - external monitors can't reliably be set above about 1280x1024
[06:52] <RAOF> poolie: Urgh.  Time to upstream that bug.
[07:10] <pitti> Riddell, ScottK: do you know why calligra-libs Conflicts: koffice-libs? that seems to be the main reason for the uninstallability (http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html)
[07:41] <tjaalton> poolie: would you mind opening a bugreport either on the kernel or fdo bugzilla? I can walk you through it
[07:42] <poolie> tjaalton, sure, just tell me where
[07:42] <poolie> can lp send it upstream or should i create it manually?
[07:42] <tjaalton> don't think it can
[07:42] <tjaalton> but, you can comment on the upstream bug via lp
[07:43] <tjaalton> so if you don't have an account on fdo I could open the bug and you could interact with it via lp
[07:45] <poolie> i think i have one - should it be there or on the kernel?
[07:45] <tjaalton> either works, but I think the fdo one is used more
[07:45] <tjaalton> hang on
[07:47] <tjaalton> of course bugs.fd.o seems to be down atm
[07:52] <dholbach> good morning
[07:57] <tjaalton> poolie: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg then select Driver/intel
[08:00] <tjaalton> poolie: actually, scratch that
[08:00] <poolie> (otp)
[08:00] <poolie> but let me know
[08:02] <tjaalton> poolie: as it's likely a bug in the drm driver, use https://bugs.freedesktop.org/enter_bug.cgi?product=DRI and DRM/Intel
[08:12] <tjaalton> poolie: here's a list of what information upstream would like on the bugreport http://intellinuxgraphics.org/how_to_report_bug.html
[08:16] <brendand> what is the meaning of putting {python:Depends} in a control file rather than just 'python'?
[08:17] <geser> it's a variable that gets replaced with the correct dependency on python itself
[08:45] <tjaalton> shouldn't /usr/include/$triplet/ be in the default search path for headers?
[08:47] <tjaalton> because I get this http://pastebin.com/JN3JpCUU
[08:47] <tjaalton> the headers are in /usr/include/$triplet/bits/*
[08:55] <tjaalton> well, nothing under /usr/include/$triplet/ is found
[09:02] <poolie> tjaalton, that rings a bell with me, but i think it's meant to be set outside of gcc...
[09:03] <poolie> can't remember where
[09:03] <tjaalton> yeah googling revealed similar issues
[09:03] <tjaalton> fixed by patching the source..
[09:05] <geser> tjaalton: if I read the MultiArch pages correctly then /usr/include isn't multi-arched yet
[09:06] <tjaalton> geser: ref?
[09:08] <geser> tjaalton: http://wiki.debian.org/Multiarch/Implementation, section "What does the end result look like?"
[09:08] <geser> and two points above that header: "If your -dev package contains headers which vary across architectures then it cannot be marked as Multi-Arch: same until a policy decision is made about architecture-dependant headers and the toolchain is updated."
[09:08] <tjaalton> hmm ok
[09:10] <poolie> tjaalton, ok https://bugs.freedesktop.org/show_bug.cgi?id=45211
[09:11] <tjaalton> poolie: excellent, thanks
[09:11] <poolie> do you know what project i use in lp to attach to that bug?
[09:11] <tjaalton> just did that
[09:12] <tjaalton> there was already xf86-video-intel "opened" for it
[09:12] <poolie> huh
[09:12] <poolie> just mentioning it is enough?
[09:14] <tjaalton> with the upstream url
[09:14] <tjaalton> but it's there now
[09:17] <tjaalton> doko_: is it a mistake or intentional that bits/ etc are under /usr/include/$triplet/bits etc?
[09:25] <poolie> tjaalton, surely they are platform-specific, by definition?
[09:25] <tjaalton> libc6-dev-i386 installs into /usr/include/sys/?
[09:25] <tjaalton> on amd64
[09:25] <tjaalton> i'm just confused by all this .)
[09:26] <tjaalton> :)
[09:26] <tjaalton> point is that /usr/include/features.h can't find it's headers
[09:26] <geser> looking at packages.ubuntu.com, libc6-dev installs some files to /usr/include/$triplet since oneiric
[09:26] <tjaalton> and the fix can't be to install the i386 dev package
[09:26] <tjaalton> geser: right
[09:27] <poolie> tjaalton, i know it looks like it installs there, but it's actually redirected
[09:27] <poolie> (may not actually be a 'redirect')
[09:27] <poolie> lrwxrwxrwx 1 root 29 Jan 24 04:03 /usr/include/sys/sem.h -> ../x86_64-linux-gnu/sys/sem.h
[09:28] <tjaalton> hm? which package created the symlink then?
[09:30] <poolie> sorry i can't remember where this is configured
[09:30] <poolie> but, there is a thing, that allows two packages to both try to install to the same place, and they get moved
[09:30] <poolie> and that's what's happening here
[09:30] <poolie> anyhow, that's it for me, good night
[09:30] <tjaalton> ok, it's gcc-multilib
[09:31] <tjaalton> installed it and now I have a symlink from /usr/include/bits -> $triplet/bits
[09:31] <cjwatson> poolie: sounds like a diversion
[09:31] <tjaalton> doko_: nevermind :)
[09:32] <poolie> that's the word i was trying to remember, thanks
[09:32] <tjaalton> another mesa build then..
[09:33] <ev> pitti: cheers
[10:00] <Riddell> pitti: koffice is due to be deleted but I'm busy on the KDE SC release this week so I stopped working on koffice/calligra for immediately
[10:01] <pitti> Riddell: ah, ok; so will calligra grow some extra transitional packages for this then?
[10:04] <pitti> Riddell: thanks for the heads-up
[10:14] <Riddell> pitti: I need to look at having a smooth upgrade, maybe some transitional packages will be appropriate (it's a bit political since koffice still exists as a project)
[10:43] <seb128> kirkland, hey
[10:43] <seb128> Jan 25 10:57:26 localhost kernel: [ 3201.475561] Valid eCryptfs headers not foun
[10:43] <seb128> d in file header region or xattr region
[10:43] <seb128> Jan 25 10:57:26 localhost kernel: [ 3201.475564] Either the lower file is not in
[10:43] <seb128>  a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrou
[10:43] <seb128> gh mode is not enabled; returning -EIO
[10:43] <seb128> kirkland, is that a known issue? those are filing my kern.log
[10:43] <pitti> kirkland: ^ FWIW, I get these all the time
[10:43] <pitti> I don't notice anything which actually goes wrong
[10:44] <doko_> tjaalton, wondering why you would need gcc-multilib at all ...
[10:48] <tjaalton> doko_: I don't have /usr/include/{sys,bits} etc without it, dunno if it's a bug then
[10:50] <doko_> tjaalton, it should not be a bug, because it should fine the bits in /usr/include/<multiarch>
[10:50] <doko_> what is the error?
[10:50] <tjaalton> doko_: http://pastebin.com/JN3JpCUU
[10:51] <doko_> tjaalton, and makedepend is aware of multiarch?
[10:51] <doko_> $ dpkg -S predefs.h
[10:51] <doko_> libc6-dev: /usr/include/x86_64-linux-gnu/bits/predefs.h
[10:52] <tjaalton> well, rest of mesa is
[10:52] <tjaalton> dunno if it needs a hammer
[10:56] <doko_> tjaalton, does mesa build 32bit binaries on amd64?
[10:57] <tjaalton> doko_: not that I know of
[10:57] <doko_> hmm
[10:58] <tjaalton> but that doesn't mean much ;)
[10:59] <tjaalton> it builds a bunch of libs, that's pretty much it
[10:59] <pitti> mesa doesn't build a lib32something binary package anyway
[11:14] <Daviey> Mez: it goes back a long time it eems
[11:14] <Daviey> err
[11:45] <ScottK> pitti: No.  Riddell did all the Calligra stuff, although I'm not surprised they aren't co-installable - this is similar to the OOo -> LO migration.
[11:47] <Riddell> s/did/is still in the process of/ since it's paused while I do KDE SC 4.8 :)
[11:52] <tsdgeos> they are not coinstallable
[11:52] <tsdgeos> at least not in the .mo level
[11:52] <tsdgeos> they clash like crazy
[12:31] <lamont> Daviey: bind9 uploaded to debian, will sync it once sid has it
[12:33] <Daviey> lamont: that is great!  Thanks for the fast response.  When you sync, can you close the ubuntu bug aswell? :)
[12:34] <lamont> will do so
[12:50] <cjwatson> infinity: [adconrad] Co-ordinate the porting of ocaml-opt to armhf: TODO
[12:51] <cjwatson> infinity: I think this is more or less done now; doko enabled it in ocaml itself a while back, and I got irritated by the stack of failures and went through and reuploaded nearly everything relevant earlier this week
[12:51] <ogra_> heh
[12:51] <cjwatson> infinity: I only just noticed the work item
[12:52] <cjwatson> infinity: the only thing left is (a) coq and its reverse-build-deps (coq fails to build for some reason); (b) doing another sanity-comparison of cmx entries between armel and armhf Contents files, after LP next sees fit to regenerate them
[12:52] <cjwatson> it was mostly just a matter of rebuilding everything in dependency order
[12:55] <doko> hmm, did I leave something half-finished?
[13:01] <cjwatson> doko: findlib had to be rebuilt to be aware that ocamlopt was available, and then everything that might have been able to build with ocamlopt had to be rebuilt
[13:01] <cjwatson> doko: I only worked that out by inspection of build failures and some pondering though
[13:27] <dhana013> HI guys How to build deb package from source please guide me. guys
[13:28] <cjwatson> debuild
[13:29] <mvo> silly(?) question - it seems now we have sudo and admin groups. but users are not auto-transitioned, is that correct?
[13:31] <cjwatson> correct
[13:32] <pitti> mvo: we went through some effort to teach packages to get along with either
[13:32] <cjwatson> it's not entirely clear what we should ultimately do there but at the moment apps need to check both
[13:32] <cjwatson> auto-transitioning in u-m might be worthwhile; is there not a bug about that, actually?
[13:32] <mvo> aptdaemon uses root.admin currently for sources.list entries with private tokens
[13:33] <mvo> so either that needs to become root.sudo
[13:33] <pitti> jockey has the same problem, but I could get around that as it's only a first-time install matter there, so I switched to sudo
[13:34]  * mvo scratches head
[13:35] <dhana013> HI guys How to build deb package from source please guide me. guys
[13:35] <ogra_> debuild
[13:35] <ogra_> as colin said above already
[13:35] <ogra_> read zthe manpage
[13:35] <ogra_> *the
[13:36] <geser> !packaging guide
[13:47] <dhana013> How to automate package creation from source.
[13:53] <micahg> pitti: hoping to finish the testing today, lucid is almost done, but I figure that we don't want to break upgrades
[13:54] <pitti> micahg: good morning; ah, thanks!
[13:59] <TREllis> I'm trying to multi-arch libidl0, it depends on cpp, which means the i386 package still won't install on amd64, needs cpp:i386... does that mean cpp needs multi-arching?
[14:02] <Riddell> dhana013: you can't
[14:03] <Riddell> dhana013: or maybe I should answer "pay canonical" :)
[14:04] <ogra_> you can, if you know how to set up a buildd :)
[14:04] <ogra_> or how to write PPA build reciepes
[14:05] <Riddell> yeah once you do the initial packaging there's ways to automate updates
[14:05] <tumbleweed> generally speaking, automating packaging doesn't work so well. But automated updates (like the daily build recipes) do work rather well
[14:05] <Riddell> and ways to help the initial packaging too but that's never anything like 100% automatic
[14:05] <ogra_> alien ftw !
[14:05]  * ogra_ hides :)
[14:05] <Riddell> :)
[14:10] <cjwatson> TREllis: Multi-Arch: foreign on cpp *might* be the right thing if the version from another architecture will work; but I would have thought that cpp has architecture-specific defaults in it ...
[14:10] <cjwatson> TREllis: we don't have provision for real multi-arch of binaries yet
[14:12] <tumbleweed> lamont/buildd admins: I just gave back a timed out pypy build and it went back to the same builder, yellow. If you can kill it, I can try giving it back when yellow is otherwise occupied
[14:12] <lamont> tumbleweed: that's not actually solving the problem
[14:12] <tumbleweed> no, I'm interested in ideas for that :)
[14:12] <tumbleweed> I thought my memory check was sufficient, but it appears not to be
[14:12] <TREllis> cjwatson: right I thought that might be the case. That's one of my blockers at the moment whilst trying to fix a chain of multi-arch dependancies
[14:13] <lamont> if that was the build that was driving yellow into the ground with it's memory footprint, I suspect that it needs to be less agressive in its total vm footprint, probably a test suite of the "hey, this'll fit, I think" variety
[14:14] <lamont> yellow has 4GB of RAM and 4.5GB of swap
[14:14] <tumbleweed> it's checking MemTotal in meminfo
[14:14] <lamont> and it had 42% swap free a while ago
[14:14] <tumbleweed> ok, I didn't do any emprical checking on amd64, but I did check that it would build on i386 with 1.7G RAM (everything else mlocked)
[14:14] <tumbleweed> and the check doubles that for 64bit
[14:16] <tumbleweed> lamont: I'll try an allocation test in the next upload
[14:17] <ev> WebKitGtk+ is still lacking access to DOM events in 1.7.  Does anyone know what the consensus approach for communicating with a WebKit WebView is? Please say something other than "multiplexing the title element." :)
[14:17] <ev> in GI, that is
[14:24] <dhana013> Riddell, then How to create custom distro based on ubuntu but not dependent with ubuntu repo.
[14:25] <dhana013> How to create custom distro based on ubuntu, but not dependent with ubuntu repo.
[14:25] <Riddell> dhana013: umm that's a different question, see https://help.ubuntu.com/community/LiveCDCustomization or "pay canonical"
[14:25] <ogra_> could you please stop repeating yourself all the time ?
[14:26] <ogra_> asking once is sufficient
[14:29] <dhana013> I can't pay canonical I want to make source build to my custom distro is possible, all packages i can convert to my distro it's possible
[14:33] <dobey> ev: are those bits in the .gir but just have introspectable="0" on them?
[14:34] <ev> dobey: correct
[14:35] <ev> I just found this from sil, which leads me to believe that document.title is still the only game in town http://askubuntu.com/a/97682/46
[14:36] <dobey> ev: i think the answer is you need to fix webkit so the APIs are introspectable. i am not sure what that entails exactly, beyond tweaks to the documentation in the C code.
[14:37] <ev> I'd love to have the time for that
[14:37] <dobey> yeah
[14:37]  * dobey also wants the vapi to get updated for vala
[15:04] <dholbach> can somebody please massage my mail through u-d-a?
[15:16] <Riddell> how do I make sed apply to only the first line of a file?
[15:20] <pitti> Riddell: sed '1 s/foo/bar/'
[15:20] <pitti> Riddell: you can specify a line number or a range
[15:21] <pitti> e. g. 1,3 <cmd> for the first three lines
[15:24] <Riddell> cool thanks pitti
[15:25] <slangasek> cnd: your latest update of x11proto-input-dev has reverted multiarch support; is there a vcs repo somewhere that you're maintaining this package?  (Not listed in debian/control)
[15:32] <dholbach> thanks for moderating it through
[15:36]  * smb silently curses about non-obvious server disconnects
[15:36] <smb> slangasek, While looking at bug 607039 again, I realized that this actually has been fixed by an update to 662711. I assume the best action for the former is to mark it a duplicate of the latter bug then. Probably bug 117957  can either be closed marked duplicate, too. Not sure which as that has a debian bug reference.
[15:36] <barry> ScottK: the pyqt4 stuff looks good.  i'm just doing a chroot install check and if that pans out, i'll do the upload.  thanks for fixing this.  i'm also going to look at sync'ing pydbus today
[15:36] <smb> slangasek, Do you think that change is worth a backport to Oneiric, still?
[15:36] <ScottK> barry: Cool.
[15:41] <slangasek> smb: hmm, don't we still need to fix the module aliasing somewhere here?
[15:42] <slangasek> I wouldn't expect idmapd to magically autoload the nfs kernel module, but maybe I'm mistaken
[15:42] <smb> slangasek, Well I'd have something for that, but practically when you did always modprobe nfs with idmap and always start idmapo now as the bug fix
[15:43] <smb> +    should always be started automatically, because we can no longer assume
[15:43] <smb> +    that a mount of type 'nfs' in /etc/fstab is not nfs4.  This also lets
[15:43] <smb> +    things work by default with nfs4 autofs.  LP: #662711
[15:43] <slangasek> smb: oh, because the idmap job explicitly modprobes nfs, right
[15:43] <smb> yup
[15:44] <slangasek> I'm not sure if we should backport that to oneiric.  what's your opinion?
[15:45] <smb> slangasek, So fwiw nfs module always is already loaded when you try to mount, which makes the modprobe for nfs4 just silently fail but not necessary.
[15:46] <smb> slangasek, Hm, the problem is there too. And the fact that lead to modprobe it in idmapd upstart would be as valid there.
[15:46] <smb> (not that ANY reporter gets back to you as soon as they now a manual workaround)
[15:46] <zyga> has anyone seen voidspace around here lately?
[15:47] <smb> slangasek, Guess given that, we could just cover our eyes and wait until someone shouts at us
[15:48] <slangasek> smb: :)  well, I think if you want to do the work to backport the change, it would be an acceptable SRU - so it's up to you whether you think it's worth the effort
[15:51] <barry> ScottK: a few lintian warnings on the resulting .debs, but i think i can fix them: http://pastebin.ubuntu.com/816583/
[15:52] <ScottK> barry: Sounds good.
[15:52] <ScottK> Thanks.
[15:52] <smb> slangasek, Given it is some work to touch the package, and that one can easily work around it by having the modprobe.d alias (as documented in the first bug), I think it is maybe not worth doing as long someone really persists. At least it is ok in Precise.
[15:53] <slangasek> ok
[15:58] <smb> slangasek, So what would you think I should do with that very old bug report #117957. Also mark it a duplicate of the other. Or just close it fixed with a note to the other bug?
[15:59] <slangasek> smb: I wouldn't mark it as a duplicate, but I think it can be closed
[15:59] <slangasek> (with a note)
[15:59] <smb> slangasek, ok, will do
[16:09] <hrw> make[2]: Entering directory `/tmp/gcc/test/eglibc-2.13'
[16:09] <hrw> /usr/bin/install -c -m 644 include/limits.h /usr/include/limits.h
[16:09] <hrw> does someone had similar attempt during (cross) build of eglibc?
[16:47] <mpt> kirkland`, hi, is now a good time to talk settings?
[17:49] <infinity> cjwatson: Ahh, didn't realise it was just findlib having a hissy fit.  Thanks for the catch.
[17:56] <barry> ScottK: i'm giving up on the executable-not-elf-or-script lintian warnings in python-qt4-doc.  dh_fixperms does seem to be getting called, but it doesn't remove the x bit from the files (even when called manually with other cli options).  i did fix the strip problem though, so...
[17:56] <ScottK> bdmurray: You just added a rls-mgr-p-tracking tag to Bug 651294.  That bug is fixed, so I don't think that's what we want.
[17:56] <ScottK> barry: I think the strip problem was the most important.
[17:56] <barry> ScottK: agred
[17:56] <bdmurray> ScottK: the latest comments indicate otherwise
[17:57] <bdmurray> ScottK: feel free to remove it though
[17:57] <ScottK> bdmurray: No.  That bug was fixed.  Someone is having similar symptoms.  They should file a new bug and not try to go back and comment on ones that are already closed.
[17:57] <bdmurray> ScottK: well you could say as much in the bug report
[17:57] <ScottK> I did.
[17:58] <ScottK> bdmurray: ~ one minute before you added the tag,
[17:58] <ScottK> So it's just a timing issue.
[17:58] <ScottK> I'll remove it.
[17:59] <ScottK> Done.  Thaks.
[17:59] <ScottK> Thanks even.
[18:02] <ScottK> barry: Nice job on the dbus stuff, dbus-python and python-qt4.  Thanks.
[18:02] <barry> ScottK: thanks.  i'm looking at pulling dbus-python 1.0.0 from debian now.  it'll be nice to resync
[18:03] <barry> debian experimental
[18:03] <ScottK> Right.  Once it's built on experimental for i386, I can push the python-qt4 changes back to experimental and we can sync from there.
[18:04] <barry> +1
[18:25] <ScottK> barry: I mashed retry on armhf.  It was a very odd error like the builder vanished out from under it.
[18:25] <barry> maybe it ran out of memory?
[18:44] <shadeslayer> cjwatson: got a sec?
[18:50] <wolter> has anybody tried to build totem-3.3.4 ?
[18:51] <seb128> wolter, it's in https://launchpad.net/~gnome3-team/+archive/gnome3
[18:52] <seb128> wolter, that's an unstable ppa though so not really recommended for use if you want a stable system (but totem 3.3 is unstable as well so you probably don't aim at something working solid)
[18:53] <wolter> seb128, yeah I just want to try it to test if  a bug I reported is fixed already
[18:54] <wolter> Thanks for the guidance!
[18:54] <seb128> wolter, yw
[18:55] <seb128> could somebody score the builds of indicator-appmenu and unity in https://launchpad.net/~unity-team/+archive/hud/+packages ?
[18:55] <seb128> they need a rebuild for the precise indicator transition
[18:55] <seb128> doko, pitti, cjwatson: ^
[18:55] <seb128> jono, kenvandine: ^ should fix things
[18:56] <infinity> seb128: I can do that.
[18:56] <seb128> infinity, thanks
[18:56] <jono> seb128, what should fix things?
[18:56] <infinity> seb128: Err, but those are clearly PPA versions.
[18:56] <jono> I disconnected
[18:57] <seb128> jono, <seb128>  could somebody score the builds of indicator-appmenu and unity in https://launchpad.net/~unity-team/+archive/hud/+packages ?
[18:57] <jono> thanks seb128
[18:57] <seb128> infinity, yeah, and we need those rebuild to happen earlier rather than later ;-)
[18:57] <seb128> libindicator got an soname update in precise
[18:57]  * micahg is waiting for the unity amd64 archive build :)
[18:57] <seb128> but ppa builder lag half a day behind
[18:58] <stgraber> seb128: done
[18:58] <infinity> stgraber: Ahh, you'd be the reason I OOPSed. :P
[18:59]  * micahg would suggest blaming launchpad instead :)
[18:59] <stgraber> infinity: well, no, the reason would be a bug in LP, but I certainly contributed to having that bug affect you
[19:00] <stgraber> infinity: so LP doesn't like you trying to rescore something that's already building? :)
[19:00] <infinity> stgraber: Well, yes.  It's a bug that when you try to rescore a build that's in the BUILDING state, it OOPSes instead of giving you a friendly message.  But you helped me trigger it.  Better? :P
[19:02] <tumbleweed> I've got some local users breathing down my neck because appmenu is exporting UBUNTU_MENUPROXY in non-unity desktop environments. Is there any particular reason that this isn't done in the unity session only? (The related bugs all seem to be marked as duplicates of bug 787465 which is specific to gnome-terminal and fixed, according to jbicha)
[19:02] <stgraber> infinity: yep, that sounds good, now go file a bug since you were the one who got the ooops ;)
[19:02] <stgraber> tumbleweed: isn't the appmenu stuff working with KDE too?
[19:03] <tumbleweed> stgraber: neither KDE or unity
[19:03] <tumbleweed> awesome, fluxbox, etc
[19:23] <shadeslayer> cjwatson: nvm :)
[20:01] <micahg> cyphermox: I wouldn't bother much with libchamplain-0.8 or clutter-gtk-0.10, both need to be removed as soon as their rdeps are migrated
[20:05] <cyphermox> micahg: i know but in the meantime it works. this was a simple patch to grab from upstream and massage to apply
[20:07] <micahg> cyphermox: you could have just as easily merged claws-mail-extras-plugin or whatever and got it removed :), it's all good though
[20:10]  * micahg treats versioned source package names suspiciously
[20:11] <bdmurray> @pilot in
[20:14]  * micahg kicks ubottu
[20:16] <cyphermox> micahg: if you're not touching claws-mail-extras-plugin though I'll do the merge now :)
[20:17] <micahg> cyphermox: well, was going to leave it for barry on his +1 mission next month, so I'm not touching it, but if he doesn't mind, have at it :)
[20:17] <cyphermox> ah, I don't especially mind waiting either. Just picking at anything I can fix, really
[20:18] <micahg> pino has an RC bug (needs sync) and needs a g_thread_init patch to build
[20:19] <micahg> or update libav-extra to 4:0.8ubuntu1 (bug 921765) as I mentioned in --motu
[20:20] <micahg> cyphermox: ^^
[20:22] <cyphermox> micahg: thx
[20:31] <slangasek> cjwatson, TREllis: cpp is already marked Multi-Arch: allowed; packages that need to be able to depend on a foreign-arch version of cpp need to be updated to depend on cpp:any
[20:32] <slangasek> TREllis: because it's not correct to say that a cpp package of any architecture will satisfy the dependency on cpp for a package of any other architecture, because of the per-arch defaults cjwatson mentions.
[20:56] <SpamapS> Ugh 20 hours for PPA builds
[20:57] <micahg> SpamapS: powerpc is worse :)
[20:58] <SpamapS> micahg: yeah, because in the end, you get a powerpc package. ;)
[20:58] <Daviey> is listadmin broken for everyone else on precise?
[20:59] <Daviey> The spam headers changed?
[21:02] <micahg> cyphermox: oh, it looks like siretart is about to upload a new libav-extra to Debian
[21:03] <cyphermox> micahg: ok
[21:03] <cyphermox> I'm fighting pino
[21:03] <micahg> oh, it's more than g_thread_init? (was the first failure I got)
[21:07] <SpamapS> is there a simple way to run sbuild and say "build this .dsc, with these extra .debs installed" ?
[21:07] <SpamapS> do I just have to build a new source chroot and stick them in there?
[21:07] <micahg> SpamapS: try --add-depends
[21:08] <SpamapS> micahg: how is that going to get my .debs into the chroot?
[21:08] <SpamapS> micahg: these are .debs that are not available yet
[21:08] <micahg> SpamapS: oh, I thought you meant dependencies :)
[21:09] <siretart> micahg: uploading right now
[21:09] <micahg> SpamapS: dpkg in --pre-build-commands from a bindmount dir in the chroot might work
[21:09] <micahg> siretart: thanks
[21:09] <SpamapS> micahg: yeah that seems doable but eeeeevil ;)
[21:10] <micahg> SpamapS: actually, you might need --chroot-setup-commands, not sure
[21:11] <micahg> SpamapS: I can tell you how to add a PPA to a single run :)
[21:12] <cjwatson> --add-depends (assuming I didn't miss somebody already saying that while I was disconnected)
[21:12] <cyphermox> micahg: I'm not getting a failure for g_thread_init at all, but getting all these vala errors (and now that I've fixed them I'm doing to one error in the generated C code
[21:13] <micahg> cyphermox: are you building 0.2.11+dfsg-1?
[21:14] <cyphermox> yes, just found out I didn't properly make sure I was building with valac-0.10, not valac-0.14
[21:15] <SpamapS> micahg: dpkg -i seems to be working
[21:15] <SpamapS> micahg: or rather --chroot-setup-commands w/ the dpkg -i
[21:15] <micahg> cool, good to know :)
[21:18] <SpamapS> of course.. its complicated because I *also* need apt-get -yf install
[21:18] <SpamapS> but, seems to progress from there
[21:19] <micahg> SpamapS: just chain another --chroot-setup-commands afterwards
[21:21] <SpamapS> mciyeah it worked ok
[21:22] <SpamapS> tab complete fail
[21:23] <micahg> siretart: are you uploading to Ubuntu also or do you want me to?
[21:24] <siretart> micahg: I'm about to crash, if you want, feel free, otherwise I'll do it tomorrow
[21:24] <micahg> ok, I'll take care of it, thanks
[21:25] <siretart> micahg: in case you're doing it, I've pushed my branches to git.debian.org. IME, merging the git branches makes it pretty easy
[21:25] <micahg> siretart: it's just a sync, so I was going to grab from incoming
[21:25] <siretart> micahg: oh, right. that makes it indeed even easier.
[21:26] <siretart> good night!
[21:26] <micahg> good night siretart
[21:35] <jbicha> tumbleweed: are you still having problems w/ the ubuntu menuproxy on precise?
[21:44] <mhall119> who gets to send emails to ubuntu-devel without having to be moderated?
[21:44] <cjwatson> anyone in the whitelist
[21:44] <cjwatson> maybe that's tautologous :)
[21:45] <mhall119> is that something that I should be on, or is it normal for most people to go through moderation?
[21:45] <Daviey> I ust flushe dthe list from 145 moderated mails down to about 40.
[21:45] <cjwatson> the charter is "posting moderated for non-developers"
[21:45] <mhall119> ok
[21:45] <cjwatson> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-December/000227.html
[21:45] <mhall119> so it's not that I've screwed up my subscription to it
[21:45] <cjwatson> in practice we generally add sensible people to the whitelist when we're bored of accepting their posts
[21:46] <cjwatson> (this is written up in https://wiki.ubuntu.com/UbuntuDevelModeration)
[21:46] <mhall119> cool, thanks
[21:46] <mhall119> me and mailing lists have a love/hate relationship, so I wasn't sure if I was doing something wrong
[21:46] <Daviey> mhall119: your mail should now have gone through.
[21:46] <mhall119> thanks Daviey
[21:48] <micahg> cjwatson: is there a sane way to sync from incoming?
[21:48] <kirkland> slangasek: would you have any ideas or comment to add to https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/920609 ?
[21:49]  * micahg just realized there's no source.changes file to sign
[21:52] <tumbleweed> jbicha: no, it looks like tha tissue is sorted now. The question is why we are loading menu-proxy at all when not in unity. And TBH, without big smoking bugs to point at, it doesn't concern me that much
[21:53] <cjwatson> micahg: syncpackage --no-lp, or wait
[21:54]  * micahg supposes he can wait 4 hours
[21:54] <micahg> cjwatson: when's the next CD run?
[21:54] <cjwatson> takes a bit longer than that before gina gets round to the import IME
[21:54] <cjwatson> depends on the CD
[21:55] <micahg> ubuntu studio (libav-extra is out of sync)
[21:55] <cjwatson> 17 18 * * *
[21:55] <cjwatson> (UTC)
[21:55] <micahg> ah, so it was already
[21:55] <cjwatson> so 20 and a bit hours
[21:55] <micahg> ok, I"ll just wait then
[22:15] <slangasek> kirkland: do you know what the pam stack looks like in this case?
[22:19] <ScottK> infinity: Any ideas on https://launchpad.net/ubuntu/+source/python-qt4/4.9-2ubuntu2/+build/3121207 - seems it's arm* specific.
[22:28] <janimo> ScottK, I remember a similar error from last year, I wonder if some patches got dropped
[22:28] <janimo> "unsupported function argument type - provide %MethodCode and a valid C++ signature"
[22:28] <janimo> ScottK, one of the sip tools needed a patch
[22:30] <janimo> ScottK, it was related to qreal/double IIRC but in a much more subtle way than in plain C++ code
[22:34] <kirkland> slangasek: no idea
[22:35] <kirkland> slangasek: sorry, but I've been asked this from time to time
[22:35] <slangasek> kirkland: ok; have asked on the bug for a copy of the pam stack in question
[22:38] <slangasek> kirkland: since it would be non-trivial to reproduce without a likewise-backed domain login, I'm not going to try to reproduce it blindly :)
[22:40] <kirkland> slangasek: nope, me neither
[22:41] <kirkland> slangasek: and yes, good question