[01:52] <IDWMaster> Is this the appropriate channel for discussing software development on Ubuntu?
[01:52] <IDWMaster> Not app development, but library development
[01:56] <xnox> IDWMaster: any most development goes on at #ubuntu-app-devel. Unless it's something major / widespread framework you'd expect the core desktop/os to use a lot.
[01:56] <xnox> then it's appropriate for this channel.
[01:56] <xnox> IDWMaster: better just ask ahead =) and we redirect you if this is not the right channel ;-)
[01:57] <xnox> infinity: at least with wubi, it's signed with microsoft ssl cert and it should be valid.
[01:58] <IDWMaster> I'm receiving realtime signal 34 for some odd reason:
[01:58] <IDWMaster> And it's crashing my program
[01:58] <IDWMaster> It's crashing on pthread_cond_wait
[01:59] <IDWMaster> I'm not sure how to debug such an error
[01:59] <IDWMaster> Sometimes it crashes on read() as well within getch
[02:01] <IDWMaster> Any idea what could be causing this?
[02:01] <IDWMaster> Crashes with the message: Program received signal SIG34, Real-time event 34.
[02:01] <IDWMaster> Backtrace from GDB indicates it's crashing in read() from getch
[02:03] <Chipzz> IDWMaster: NO, this is NOT the approrpiate channel for that
[02:03] <infinity> IDWMaster: You probably want #ubuntu-app-devel (see /topic)
[02:03] <IDWMaster> OK
[02:03] <IDWMaster> Thanks
[02:03] <infinity> Chipzz: You could be a bit more polite about your redirects.
[02:03] <Chipzz> (was that too harsh?)
[02:03] <Chipzz> sorry, my bad
[02:04] <xnox> Chipzz: NO, it was NOT the approrpiate voice for that redirect.
[02:04] <xnox> ;-)
[02:04] <infinity> Oh, hi /topic, I've been patch piloting for how many days now?  Oops.
[02:04] <infinity> @pilot out
[02:04] <Chipzz> xnox: LOL :)
[02:04] <xnox> How did that read to you?! =))))))
[02:04] <Chipzz> xnox: but why did you not redirect him right away instead of saying this could be the right channel?
[02:05] <Chipzz> xnox: IME, if people are asking that question, the answer is almost always "no"
[02:05]  * xnox thought to teach not to ask a question to ask a question.
[02:05] <infinity> Every once in a while, an "app devel" question actually ends up being a "why is the compiler buggy?" question, or similar.
[02:05] <xnox> and hopefully let somebody else redirect. =)))))
[02:05] <Chipzz> the very fact that they ask (in most cases) means they're uninformed and hence by definition shouldn't be here
[02:06] <infinity> In his case, definitely not.  He was just writing a poorly-threaded application.
[02:06] <lifeless> thus having two problems
[02:06] <xnox> lifeless: =)
[02:06] <Chipzz> infinity: I would argue that if it involves such a problem, the people encountering those problems tend to more informed, and thus come here for a reason
[02:07]  * xnox always jumps a little when lifeless just appears and makes a comment once in a blue moon
[02:07] <infinity> Chipzz: Eh.  Not always.  Tripping over new and exciting bugs isn't limited to the experienced.
[02:07] <Chipzz> infinity: no it isn't, but in 99% of the cases the fact that people are asking "is this the right channel?" is a very good indicator that it's not ;)
[02:08] <Chipzz> because like I said, informed people *know* wether or not this is the right channel. and informed people read the topic :)
[02:09] <scientes> if only
[02:10] <Chipzz> and I'ld argue that tripping over a compiler error isn't very common. and even if it is, one could argue that the correct avenue is to ask in #gcc or something of the kind first
[02:11] <Chipzz> infinity: but like I said, the moment I hit enter I realized my sentence could have done with less caps. meh
[02:26] <xnox> cannot find Python.h would be #ubuntu-app-devel, right until we uploaded multiarched python and /broke the world/ and suddently it's a very #ubuntu-devel on topic.
[02:39] <Malsasa> Hello, lintian says copyright-file-contains-full-gpl-license, i have read lintian page about it and debian policy manual, but i don't understand. What should I fill in copyright file? I have filled it with copy of GPL text...
[02:40] <scientes> Malsasa, the gpl header text
[02:41] <Malsasa> scientes: i don;t know what is that... any example what should I write in the copyright file?
[02:42] <scientes> this is the short versino: http://paste.debian.net/235443/
[02:42] <scientes> but you really should include the no warranty clause as well
[02:42] <scientes> (per the GPL)
[02:43] <Malsasa> scientes: TKP
[02:43] <scientes> Malsasa, like this http://paste.debian.net/235444/
[02:43] <Malsasa> scientes: TKP again
[02:44] <Malsasa> scientes: thank you... i will try to copypaste them i copyright
[02:44]  * Malsasa am learning debian packaging
[02:44] <scientes> make sure to differentiate between GPL and LGPL
[02:45] <scientes> and the v3 text is differn't to v2 text, even the header
[02:45] <Malsasa> scientes: oooh, okay
[02:45] <Malsasa> scientes: okay
[02:45] <Malsasa> scientes: if i confused, i wanna ask you again here... :)
[02:45] <scientes> and there is a LGPL-2.1
[02:53] <Malsasa> scientes: okay
[02:53] <Malsasa> scientes: so, in the point, i should fill only 1 copyright in that file?
[02:54] <infinity> Malsasa: You might find http://dep.debian.net/deps/dep5/ informative
[02:54] <Malsasa> infinity: waaah, thanks!
[02:55] <scientes> Malsasa, http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
[02:55] <scientes> that superceeds dep5
[02:55] <Malsasa> scientes: wow, thank you again. TKP
[02:56] <infinity> Oh, indeed.  I just always remember it as DEP5, and Google it as such.  Someone should edit DEP5 to put a link to the proper spec at the top.
[02:57] <Malsasa> infinity: thank you
[03:12] <Malsasa> infinity: my problem about copytight file solved
[03:13] <Malsasa> scientes: i copied another deb's copyright , i've checked it befire by lintian
[03:49] <ScottK> infinity: Any more luck with qscintilla2?
[03:49] <infinity> ScottK: Oh, I stopped looking right around when I whined at you.
[03:50] <ScottK> Oh.  Rats.
[03:50]  * ScottK adds it back to TODO.
[03:50] <infinity> ScottK: I could rewrite the symbols files by hand and probably do a better job than the helper script, which keeps failing.
[03:50] <infinity> ScottK: Just had no motivation today.  Day off, and I was still working. :/
[03:50] <ScottK> Understood.
[05:08] <vibhav> Should libnotify depend on glib?
[05:08] <vibhav> Shouldnt*
[05:08] <vibhav> /usr/include/libnotify/notify.h:25:18: fatal error: glib.h: No such file or directory
[06:55] <pitti> Good morning
[08:01] <dholbach> good morning
[08:35] <brendand> does anyone remember the name of the python module which converts ubuntu release numbers to series names and vice versa?
[08:40] <pitti> brendand: python-distro-info
[08:40] <pitti> (or python3-distro-info)
[08:46] <brendand> pitti, how robust is it?
[08:46] <brendand> pitti, if i install it on a lucid box will it still be able to tell me 13.04 is raring?
[08:47] <pitti> brendand: AFAIK it's supposed to be the definitive place for this now, and being used by several developer tools
[08:47] <brendand> pitti, and so on continuing into the future
[08:47] <brendand> pitti, cool
[08:47] <pitti> brendand: I don't know; it did get a few SRUs for newer releases
[08:54] <pitti> brendand: I don't think lucid's got SRUs to add raring etc.; if you need this always, it's probably better to query launchpad
[08:54] <brendand> pitti, how would you query launchpad?
[08:55] <brendand> pitti, i mean not in general (obviously using launchpadlib), but to get the series name from release number
[08:57] <pitti> brendand: http://paste.ubuntu.com/1680511/
[09:01] <geser> brendand: you can also use "ubuntu.getSeries(name_or_version='13.04')" to get the right series object instead of needing to iterate the list to find it
[09:04] <brendand> geser, i was wondering that
[09:11] <tumbleweed> pitti: we SRU to add new releases
[09:11] <tumbleweed> otherwise ubuntu-dev-tools breaks (it needs to know development release names, in tools that don't use LP)
[09:11] <pitti> tumbleweed: oh right, I was looking for a lucid SRU, but distro-info isn't in lucid yet; my bad
[09:43] <doko> barry, xnox: could you have a look at shiboken again? ftbfs
[09:44] <xnox> doko: ok. cjohnston was looking at it yesterday.
[09:44] <doko> ahh, cool
[09:44] <xnox> (and I do mean cjohnston this time around ;-) )
[09:57] <doko> stgraber, upstart ping
[09:59] <brendand> pitti, tumbleweed - it happens that the script i'm writing has to use launchpadlib anyway so i will just use that method
[10:10] <cjwatson> vibhav: Er, it does.  apt-cache show libnotify-dev | grep glib
[10:11] <cjwatson> vibhav: I suspect that whatever you're building isn't using the proper compiler flags, as emitted by 'pkg-config --cflags libnotify', so is missing the correct include directory for glib
[10:26] <cjwatson> infinity: By the way, I fixed the cdimage checksumming bug from last night.  https://bazaar.launchpad.net/~cjwatson/ubuntu-cdimage/mainline/revision/974
[10:26] <cjwatson> hallyn: FYI, bug 1129571, if you haven't seen it already
[10:31] <ogra_> cjwatson, hmm, do the launchpad buildds actually use qemu ? i thought only PPAs do
[10:33] <ogra_> would have helped if it mentioned the builder in the bug ... the log seems gone too
[10:33] <cjwatson> ogra_: Uh, the bug was about a failure on virtualised PPAs
[10:33] <ogra_> well, nothing in the bug indicates that
[10:33] <cjwatson> ogra_: My comment does
[10:33] <cjwatson> ogra_: I have context from a lengthy IRC conversation yesterday
[10:33] <ogra_> oh
[10:34] <ogra_> yeah, i thought so
[10:34] <ogra_> (that there was side conversation)
[10:34] <cjwatson> Getting Alex to escalate this qemu bug was one of the conditions for working around the problem temporarily by making the PPA devirtualised
[10:34] <cjwatson> And that state shouldn't go on too long
[10:35] <ogra_> yeah
[10:35] <Daviey> cjwatson: Happen to know what version of qemu is in use (& maybe what kernel)?
[10:35] <cjwatson> Daviey: Whatever's on archive.admin.c.c
[10:35] <cjwatson> 1.3.0+dfsg-1~exp3ubuntu8~3.IS.12.04 I think
[10:35] <Daviey> cjwatson: Ok, thanks.
[10:36] <cjwatson> And for the kernel, check any virtualised PPA armhf build log
[10:36] <caribou> pitti: looks like I'll have to do my apport MP against a raring branch as I have a change to debian/apport.upstart which is not in trunk
[10:37] <pitti> caribou: you can do two MPs
[10:37] <caribou> pitti: ah, didn't think of that
[10:37] <pitti> caribou: if you do just one, I'll pick it apart myself, i. e. apply the matching bits to trunk
[10:37] <pitti> caribou: trunk has a sysv init script
[10:38] <cjwatson> Daviey: (commented to that effect)
[10:38] <caribou> pitti: fine, then I'll adapt the upstart change to the sysv script in trunk and do a separate one for upstart
[10:38] <Daviey> cjwatson: thanks
[10:38] <pitti> caribou: great, thanks!
[10:39] <caribou> pitti: should I do the upstart one on lp:ubuntu/raring-proposed/apport ?
[10:39] <pitti> caribou: not -proposed, just raring; please, yes
[10:39] <caribou> pitti: ok, will do
[10:51] <zequence> diwic: Any chance you will be updating pulseaudio to a newer upstream version before feature freeze?
[10:52] <diwic> zequence, 3.1 might happen if it's released, but that would not be any huge change compared to 3.0.
[10:52] <zequence> diwic: I prepared a patch that adds the channel config thing to the jack module http://paste.ubuntu.com/1681367/
[10:53] <zequence> Was a little unsure of what would be the best way to forward it
[10:53] <zequence> I haven't actually tested the patch. I should probably do that :P
[10:54] <diwic> zequence, it seems to be missing an entry in debian/changelog
[10:57] <diwic> zequence, hmm, or maybe you just posted the patch file, not the debdiff
[11:03] <zyga> bryce: hey
[11:04] <zyga> bryce: it still crashes with xorg-edgers
[11:33] <mjt> how does ubuntu use qemu for building stuff?
[11:33] <mjt> it looks like some arches are built in qemu (qemu user mode emulation), right?
[11:34] <mjt> according to LP:1129571
[11:35] <zyga> mjt: I don't think we use qemu for building packages
[11:35] <cjwatson> Virtualised PPAs use qemu for some architectures
[11:35] <cjwatson> Specifically ARM
[11:35] <mjt> that's arm :)
[11:35] <cjwatson> I've answered this twice in this channel in the last hour or so :)
[11:35] <cjwatson> mjt: Yes, and this bug is about ARM
[11:35] <zyga> ah ;)
[11:36] <mjt> oh. i see it in the scrollback
[11:36] <cjwatson> And yes, it's qemu-user-static + binfmt_misc in roughly the obvious way
[11:37] <mjt> i was going to say, more or less, that it's better to replace this with qemu-system, if possible... :)
[11:37] <cjwatson> Unlikely to happen
[11:38] <cjwatson> I asked Alex to escalate this bug because that clearly ought to be done; I doubt there's any time to entirely rewrite the way virtualised PPAs are handled
[11:38] <mjt> i see
[11:38] <mjt> well. if the root cause of this is hat i think it is, it won't be fixed in a few seconds in qemu either.
[11:38] <cjwatson> Not to mention that that would doubtless have its own set of problems, e.g. with finding a machine to emulate that can use all the memory of the build system
[11:39] <cjwatson> mjt: Sure, didn't claim it would
[11:39] <cjwatson> Any real bug tracking system has hard bugs in it
[11:41] <mjt> this should ebe a good testing ground for qemu and building stuff this way, anyway
[11:42] <Malsasa> Hello, is Size field necessary in debian/control file? Or just Installed-Size field?
[11:42] <mjt> both fields are generated automatically
[12:18] <leighman> how can I get a launchpad recipe to build with debug symbols/a -dbg package?
[12:28] <xnox> leighman: one should add a -dbg package in the control file and dh_strip should put the symbols there. and one should make sure package is compiled with debug symbols on.
[12:29] <lantizia> Lo... I just bought a Nexus 4 (mainly because I'm sick of using a dead OS called Maemo on my N900 and I'm finally admitting it's time to use android - but ALSO because of this Ubuntu Mobile beta coming out in 2 days time) but it'll take 2 weeks to get here
[12:29] <xnox> (they are by default but some crazy packages overwrite it)
[12:29] <lantizia> I'm wondering... how likely is it I can dual boot Android and Ubuntu Mobile on it?
[12:29] <lantizia> or maybe load one from the other?
[12:29] <xnox> lantizia: see #ubuntu-phone channel.
[12:29] <lantizia> xnox, ah I tried #ubuntu-mobile but it says to go to #ubuntu-devel!
[12:30] <xnox> lantizia: sorry about the loop.
[12:30] <xnox> lantizia: #ubuntu-mobile is obsolete channel, latest Phone OS is on #ubuntu-phone.
[12:33] <ogra_> yeah, #ubuntu-mobile kind of turned towards #ubuntu-arm a few years ago .... and the phone is separate and new
[12:46] <zequence> diwic: Hi. Got cut off the internet before
[12:49] <mterry> didrocks, what's the new sdk package name?
[12:49] <diwic> zequence, yeah, I wrote something about missing debian/changelog but I'll take it back because I realized you just pastebinned the patch, not the full debdiff
[12:49] <didrocks> mterry: it's not in raring yet
[12:49] <mterry> didrocks, oh, I misread something
[12:53] <zequence> diwic: Yes, I was having a bit of trouble with it. I suspect I need to test this first, cause I only realized later I actually didn't know if it'll work. Bit busy now, but will give it another shot this evening. Ping you tomorrow, maybe
[12:54] <diwic> zequence, won't be around tomorrow, back on Thursday
[12:56] <zequence> diwic: ok
[12:58] <diwic> zequence, my workflow for adding a pulseaudio patch would, roughly, be: bzr branch lp:~ubuntu-audio-dev/pulseaudio/ubuntu ; cd ubuntu ; bzr bd-do ; quilt push -a ; quilt import <patch> ; quilt push ; exit ; dch -i ; bzr add debian/patches/* ; bzr commit ; bzr push
[12:59] <diwic> zequence, and bzr-buildpackage for testing
[13:26] <leighman> xnox: so it should have debug symbols as is or dh_strip only adds them if there is a -dbg package?
[13:28] <hrw> leighman: if build is done on buildd then dh_strip will create dbgsym ddeb package
[13:30] <leighman> hrw: should http://bazaar.launchpad.net/~leighman/evolution-force/evolution-force-packaging/files/head:/debian/ in a recipe produce something that gives a reasonable backtrace or do I explicitely need a -dbg package?
[13:30] <leighman> hrw: sorry, total package noob
[13:31] <hrw> leighman: sorry, I lack knowledge of cdbs
[13:36] <diwic> seb128, hi
[13:50] <seb128> diwic, hey
[13:52] <xnox> leighman: if you are building in a ppa, unlike ubuntu archive, there are no automatic dbgsym packages. By default dh_strip either saves detached debug symbols in $pkg-dbg or discards them.
[13:52] <xnox> leighman: if that's too hard just `export DEB_BUILD_OPTIONS='nostrip'` and that should keep debug symbols attached to the objects.
[13:53] <leighman> xnox: I'm don't understand half of those words :P
[13:53] <diwic> seb128, with PA 3.0 finally in Raring I'm experimenting with a patch to g-c-c that will give us better icons, i e a speaker icon instead of the card icon.
[13:53] <seb128> nice
[13:53] <diwic> seb128, the problem seems to be that some of the icons, e g the speaker icon, is not present on the system.
[13:53] <xnox> leighman: in that case seek further help in #ubuntu-packaging channel.
[13:53] <leighman> xnox: ahha, ok, cool
[13:54] <diwic> seb128, but e g the HDMI icon and the mic icon works fine
[13:54] <diwic> seb128, the question is what to do about that?
[13:54] <seb128> diwic, do we need those icons added to our icon theme or...?
[13:55] <diwic> seb128, yeah I think they need to be added somewhere, and I'm not an icon expert :-)
[13:55] <seb128> diwic, the issue is not to have them added, it's to have them "made"
[13:56] <diwic> seb128, let me look up the icon names
[13:57] <diwic> seb128, the names are "audio-headphones" and "audio-speakers" I believe
[13:58] <diwic> seb128, so, in short, do you know how to "get icons made"?
[13:58] <diwic> seb128, if you think it's worth the effort?
[13:58] <seb128> diwic, talk to the design team, but I guess it's too low priority that will be work on it any time soon
[13:58] <seb128> be worked on*
[13:58] <seb128> diwic, I would stay with what we have
[13:59] <diwic> seb128, is it possible to use Gnome's icons if they have them?
[13:59] <diwic> seb128, just copy them in to our theme or so
[14:04] <diwic> seb128, it looks like audio-speakers is shipped in gnome-icon-theme-full eg
[14:04] <xnox> diwic: we should auto-fallback correctly to some theme that has them already.
[14:04] <cjohnston> doko, xnox: fwiw, I continued to get error after error with shiboken... I am at a loss as to why it builds in debian but there are so many issues in ubuntu
[14:04] <xnox> cause we do have a number of fallbacks.
[14:05] <xnox> cjohnston: it doesn't build in clean debian sbuild any more.
[14:05] <cjohnston> oh
[14:05]  * xnox did say that me and ScottK did poke it extensively (and both having DD and ubuntu hats....)
[14:06] <stgraber> doko: upstart pong
[14:06] <cjohnston> xnox: yup.. :-)
[14:06] <doko> stgraber, see email
[14:06] <stgraber> doko: ok, will do in a minute
[14:06] <diwic> xnox, so I do have a working speaker icon if gnome-icon-theme-full is installed - maybe we can move that icon from gnome-icon-theme-full to gnome-icon-theme?
[14:08] <xnox> how big is the package?
[14:09] <xnox> (despite raising the limits on normal desktop, fully installed default experience still has every MB to account for on devices that do not have the luxury of TBs of space ;-) )
[14:09] <cjwatson> Well, diwic was just talking about moving one icon
[14:11] <diwic> there's still the missing headphones icon though, which is not shipped in our theme, nor in gnome's.
[14:15] <hallyn> cjwatson: yup, i did notice it yesterday.  glad Peter took a look for a start.
[14:18] <stgraber> doko: thanks for the analysis. I'd rather have jodh look at the changes and get upstart and libnih fixed though. I think he's out today so hopefully this can be done tomorrow.
[14:21] <hallyn> cjwatson: all right i'll see what i can do with that today.  maybe i can at least bisect it.
[14:40] <cjwatson> hallyn: *nod* thanks
[15:17] <doko> seb128, not sure if you are the right one to track this ... qtcreator will stay in -proposed unless powerpc binaries are removed, or qtjsbackend-opensource-src is built on powerpc
[15:18] <seb128> didrocks, ^
[15:18] <seb128> doko, didrocks is rather
[15:20] <didrocks> doko: either way, I think we can remove the binary for now and let it go to raring
[15:20] <doko> didrocks, in this case, please identify all the depending binaries
[15:21] <didrocks> doko: I will, just not right now though, trying to get most of what we are focusing the sprint on, and then, will list that
[15:22] <didrocks> or maybe Riddell, as he sponsored part of the stack as well
[15:27] <geryon6> When I'm looking at a Launchpad bug marked “Fix Released” (e. g. LP #964897), how do I know which version actually fixes the bug?
[15:28] <geser> geryon6: look at the changelog from the janitor (comment #7)
[15:29] <stgraber> @pilot in
[15:30] <geryon6> geser: Unfortunately that's the wrong one, because the bug was reopened and fixed again later.
[15:32] <geser> geryon6: in such cases it's probably best to ask the person who set the bug to "Fix released" again (perhaps it's tracked in a different bug now)
[15:34] <geryon6> It would be nice if that information would be shown next to the “fix released” at the top. Am I the only one who is missing this feature?
[15:37] <geser> geryon6: I guess not, I'm pretty sure other people would like to see LP have versioning support for bugs
[15:41] <cjwatson> doko,didrocks: qtcreator has only one reverse-dep on powerpc, namely qt-sdk, which is Architecture: all
[15:41] <cjwatson> If the new qtcreator is urgent then it might be best to leave that intentionally broken for now rather than trying to work around it; qt-sdk itself has no reverse-dependencies
[15:42] <cjwatson> (As in, remove the powerpc binaries knowing that it will create one extra uninstallable)
[15:53] <geryon6> geser: I've found LP #163694 which more or less covers this. Seems this issue is known for years already.
[15:57] <cjwatson> geryon6: Explicit version tracking was in the initial design for Launchpad Bugs, but was later removed/long-term-deferred
[15:58] <cjwatson> At this point it's very unlikely to be added in (at least) the medium term
[16:00] <geryon6> cjwatson: That's sad to hear because it confuses me quite often. Sometimes I can see the fixed version number in the comments, but not always. And if it is there, it is not easy to find.
[16:01] <cjwatson> geryon6: You're preaching to the choir :)
[16:01] <cjwatson> It was in the initial design for Launchpad Bugs because when we designed it I had recently added the corresponding feature to debbugs
[16:01] <cjwatson> But, as things worked out, I ended up working on Ubuntu rather than on the bug tracker
[16:02] <mlankhorst> at least you get to make a lts pointrelease ;)
[16:04] <geryon6> cjwatson: I see. :)
[16:04] <xnox> ev: ubiquity-dm crashed but "it's no longer installed" since well it's removed at the end of the oem-config, can we still whitelist that?
[16:05] <didrocks> cjwatson: I agree, there is no rush for qtcreator to go outside proposed, and we  need to wait for mirv to be back from vacations for pushing the ubuntu sdk as well
[16:15] <infinity> didrocks: Well, as long as it depends unconditionally on a v8 JS engine, it ain't gonna build on PPC, so we need to either sort out how to turn some bits off for !x86/ARM, or we need to just drop the binaries that fall out of that chain.
[16:16] <didrocks> infinity: I would go for dropping, but prefer to check with mirv first
[16:16] <infinity> didrocks: This'll be a bigger deal as this all gets pushed to Debian, where the majority of their arches have no v8 port (while for us, it's only one arch), so someone, somewhere, is going to have to come up with a pleasant solution.
[16:17] <ev> xnox: I'd much rather see if we can drop that check. Digging through the code, it looks like we only need the package installed to determine its origin.
[16:18] <ev> (we could compromise and set it to [origin: uninstalled])
[16:19] <infinity> didrocks: But we can certainly remove the binaries in Ubuntu and push back on the Debian maintainers to find a more elegant solution for arches without V8 ports, and we'll pick up whatever they decide to do.
[16:19] <didrocks> infinity: urgh, interesting, not sure why they didn't discuss that yet as he ensured me they sync together. Let's see how it goes
[16:19] <didrocks> infinity: agreed
[16:20] <infinity> (I really wish V8 had a generic C implementation for non-native ports, but unless you know a V8 engineer at Google who wants to make that happen, it's certainly not a weekend project I intend to get sucked into)
[16:59] <hallyn> pitti: slangasek: bug 1092715 is causing headaches with automated testing.  so until both it and inotify kernel bugs are definately resolved, i'd like to remove the udev rule hack i had in place (which isn't reliable anyway) in favor of expliclty doing chown/chmod/setfacl in postinst.  just until the other bugs are fixed.
[17:49] <Malsasa> Hello, anybody can help me? http://ubuntuforums.org/showthread.php?p=12518579#post12518579 <<< How to Write Correct copyright File?
[17:53] <slangasek> hallyn: go for it.  Where are we wrt kernel inotify bugs, though?
[17:55] <hallyn> slangasek: i'm not sure.  i *thought* it was supposed to be fixed,
[17:55] <hallyn> but comments by jamespage suggest they may not be
[17:56] <hallyn> infinity: ^ do you know if all inotify bugs are supposed to be fixed in raring's current kernel?
[18:22] <infinity> hallyn: I'm not familiar with the bug you were working around, so I can't say.
[18:23] <hallyn> infinity: oh i'm sorry, i thought you were the one who had pointed it out to me.  nm.
[18:24] <infinity> hallyn: Well, we've had different inotify bugs.  The one where it was causing leaks and you'd eventually run out of inotify handles has been fixed.
[18:24] <infinity> hallyn: But if it's just a case of "inotify doesn't work right, and I don't know why", that could be a bug in the application, not the kernel.
[18:27] <hallyn> app being udev - possible to be sure
[18:27] <hallyn> lunch (and not me) - biab
[20:01] <kieppie> well done with the new table, mobile & tv stuff guys. just watched the vid. very nice!
[20:01] <kieppie> can hardly wait for stable code repo's
[20:02] <kieppie> 13.04?
[20:02]  * kieppie can't wait to see the fan/parody vids....
[20:19] <stgraber> @pilot out
[22:20] <zyal> Helo
[22:20] <zyal> Can anyone help me out here?
[22:21] <sarnold> zyal: irc tends to work best if you ask a specific question upfront :)
[22:21] <zyal> Okay =D
[22:21] <zyal> I'm trying to install the Ubuntu SDK
[22:21] <zyal> but am stuck at the qtchooser package
[22:22] <zyal> Running sudo-apt-get -f install yields:
[22:22] <zyal> Unpacking qtchooser (from .../qtchooser_0.0.1~git20121229.g8f08405-0ubuntu1~precise1~test5_i386.deb) ...
[22:22] <cjwatson> Where's the web page with the instructions you're starting from?
[22:22] <zyal> dpkg: error processing /var/cache/apt/archives/qtchooser_0.0.1~git20121229.g8f08405-0ubuntu1~precise1~test5_i386.deb (--unpack):
[22:22] <zyal>  trying to overwrite '/usr/bin/xmlpatterns', which is also in package qt4-dev-tools 4:4.8.1-0ubuntu4.4
[22:22] <zyal> No apport report written because MaxReports is reached already
[22:22] <zyal>                                                               Processing triggers for man-db ...
[22:22] <zyal> Errors were encountered while processing:
[22:22] <zyal>  /var/cache/apt/archives/qtchooser_0.0.1~git20121229.g8f08405-0ubuntu1~precise1~test5_i386.deb
[22:22] <zyal> E: Sub-process /usr/bin/dpkg returned an error code (1)
[22:22] <cjwatson> Yeah, whatever way you slice it that's a bug *somewhere*
[22:22] <zyal> http://developer.ubuntu.com/get-started/gomobile/
[22:22]  * cjwatson looks
[22:22] <zyal> I followded it to the tee
[22:23] <cjwatson> zyal: What Ubuntu version are you running?
[22:23] <cjwatson> I assume 12.04, from that log
[22:23] <zyal> Yes
[22:23] <zyal> Do I have to 12.10 >.<
[22:24] <cjwatson> No, just one minute while I set up a reproduction environment
[22:24] <zyal> Okay
[22:29] <cjwatson> zyal: Did you already have qt4-dev-tools installed before starting this?
[22:29] <cjwatson> Or was it one of the new packages installed?
[22:29] <zyal> I think I've installed qt4-dev-tools before
[22:29] <zyal> For what reason I dont know why
[22:30] <GuidoPallemans> ph
[22:30] <GuidoPallemans> oh
[22:30] <cjwatson> I ask because it's only a recommendation here, so if you didn't have it installed already then that'd be a workaround
[22:30] <zyal> okay
[22:31] <cjwatson> But I want to check this out anyway - just waiting for it all to download
[22:32] <zyal> alright
[22:38] <cjwatson> Hmm, doesn't look like qt4-x11 has had qtchooser support added to it in precise.  https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-proper/+packages shows it for raring (though it's in the primary archive there anyway) and quantal, but not precise
[22:38] <zyal> aw shicks
[22:38] <zyal> Does this mean no SDK for me in precise?
[22:38] <cjwatson> So my reading of this is that Timo needs to fix that
[22:39] <cjwatson> I suspect you can make it work for now by 'sudo apt-get remove qt4-dev-tools; sudo apt-get install ubuntu-sdk notepad-qml qt4-dev-tools-'
[22:39] <cjwatson> But I haven't got far enough through this download to be able to test that
[22:39] <zyal> that's the thing
[22:39] <cjwatson> If you wait 10-15 minutes or so I should be able to verify
[22:39] <zyal> my installer is locked up
[22:40] <cjwatson> Oh, that's just apt, that's recoverable
[22:40] <zyal> How should I?
[22:40] <cjwatson> sudo dpkg --configure -a
[22:40] <cjwatson> sudo apt-get -f install
[22:40] <cjwatson> Then if it's still busted, paste the error into paste.ubuntu.com and post the URL you get
[22:42] <zyal> http://pastebin.com/cQYUi9BU
[22:43] <cjwatson> zyal: sudo dpkg --remove qt4-dev-tools; then repeat the two commands above
[22:46] <zyal> cjwatson: Same Errors
[22:46] <cjwatson> zyal: Can't possibly be exactly the same; paste again
[22:47] <zyal> Oops your right
[22:47] <zyal> sec
[22:47] <cjwatson> (If nothing else, I would expect an error from the first command if it didn't resolve the second/third)
[22:48] <zyal> http://pastebin.com/h1hYQYUL
[22:52] <cjwatson> zyal: Meh, you're going to have to remove a fairly large chunk of Qt4 to make this possible as it stands - is that something that will cause a problem?  (e.g. if you were running Kubuntu or Unity-2D it would not be a good plan)
[22:52] <zyal> cjwatson: No sir, I use DWM anyway
[22:52] <zyal> No unity
[22:53] <cjwatson> You can, I believe, do this with "sudo dpkg --remove libqt4-dev libqt4-opengl-dev libqtwebkit-dev qdbus qt4-qmlviewer" and then those same two commands again
[22:53] <zyal> Somewhat related: I dont need unity to develop though, right?
[22:53] <cjwatson> Don't ask me, I'm a foundations developer :)
[22:53] <cjwatson> But I'll mail Timo and remind him that qt4-x11 is busted
[22:53] <zyal> Ah okay
[22:54] <zyal> So how do i atleast get the term working again?
[22:55] <cjwatson> Have you tried that command above yet?
[22:55] <zyal> Oops slipped my eyes
[22:57] <zyal> Success?
[22:57] <zyal> Yes
[22:57] <zyal> no error this time
[22:57] <cjwatson> GOod
[22:57] <zyal> Does this mean ubuntu-sdk is installed?
[22:57] <cjwatson> If the last command's output ended with "Setting up ubuntu-sdk (0.1~bzr20130204-0ubuntu1~precise1~test1) ...", you should be good
[22:58] <cjwatson> You can always repeat "sudo apt-get install ubuntu-sdk notepad-qml" to make sure
[22:58] <cjwatson> I've sent that mail, so hopefully this can get sorted out properly rather than by this kind of hack
[22:58] <cjwatson> Thanks for reporting
[22:58] <zyal> Thanks alot cj..
[22:59] <zyal> should I report this officially.. I have no experience
[22:59] <cjwatson> It's in a PPA so that's a bit awkward
[22:59] <cjwatson> I've already mailed the person I believe to be the responsible developer, which should be enough here
[23:00] <zyal> Alright sweet
[23:00] <zyal> What do you do as a foundations dev?
[23:00] <cjwatson> bottom layer of userspace; personally, boot loaders, installers, package archive infrastructure
[23:01] <zyal> ooh sounds like hard work
[23:01] <infinity> zyal: As a general rule, if it's pretty, we don't touch it ("we" being "foundations developers")
[23:01] <zyal> LOL
[23:02] <infinity> The installer being the only possible exception to that rule.
[23:02] <zyal> Ive always wondered do you guys ever get to talk to Shuttleworth?
[23:02] <cjwatson> It wasn't desperately pretty for a fair while ...
[23:02] <zyal> other than the summits
[23:02] <zyal> or do you just work under a branch
[23:03] <cjwatson> Now and again; he's a busy man
[23:03] <infinity> Most of us probably talk to Mark a lot less than we did 8 years ago.
[23:03] <infinity> See above, re: busy man.  Plus, the company is much larger.
[23:03] <zyal> I can imagine
[23:03] <infinity> I haven't had strange 5am phone calls in a long time.
[23:04] <zyal> But you guys have met him in the early years tho
[23:04] <cjwatson> It's not that we're not allowed to talk to him, it's just that if he tried to talk to several hundred employees and goodness knows how many community members directly he'd never sleep at all
[23:04] <infinity> Yeah.  When we were all much younger and slightly more silly.
[23:05] <zyal> Ah
[23:05] <zyal> As a FOSS dev.. do you guys have any alternative $$ making gigs on the side? Did your FOSS credit help you guys in your fields?
[23:05]  * cjwatson digs
[23:05] <cjwatson> 2026     Feb 18 Mark Shuttlewor (  19) New Debian-related project
[23:05] <cjwatson> :)
[23:06] <zyal> Just curious on the whole scene actually
[23:06] <zyal> ;D
[23:06] <sarnold> cjwatson: cool :)
[23:06] <cjwatson> Eh, Canonical employs me, I don't have time for two jobs
[23:06] <infinity> cjwatson: I like Scott's version better than the real thing.
[23:06] <jcastro> we're coming up on 10 years of Ubuntu!
[23:07] <cjwatson> But certainly the fact that I'd been doing free software for several years beforehand got me this job
[23:07] <infinity> jcastro: Getting there, yeah.
[23:07] <cjwatson> Hey, yeah, that mail was 9 years yesterday
[23:10] <infinity> cjwatson: Hrm.  Tempted to wiggle the 12.04.4 release date to 2014-02-18, and make a 10th anniversary thing out of it.
[23:10] <cjwatson> It's only a tenth anniversary in a weird internal sense
[23:11] <infinity> Thankfully, I hate editing wikis, and I'll forget in a year.
[23:11] <cjwatson> Besides, pretty sure Scott was already on the payroll (such as it was) by then
[23:11] <infinity> cjwatson: True, the 10th anniversary of warty is probably more interesting.
[23:11] <cjwatson> I seem to remember he said he had to go to considerable effort to keep his mouth shut in Málaga
[23:12] <cjwatson> (er, Open Source World Conference, held there around that time; at least he and I and Tollef were there)
[23:15] <jcastro> infinity: we need to find something clever for no-name-yet.com too
[23:16] <infinity> jcastro: You'd have to ask Matt nicely, it's his, not the company's.
[23:16] <infinity> jcastro: Or, so says the all knowing registrar.
[23:16] <jcastro> I'm sure we can find some kind of scheme
[23:21] <lifeless> cjwatson: I don't think scott was on the payroll on the 18th
[23:21] <lifeless> cjwatson: would have to dig up evolution to check though :)
[23:22] <lifeless> warty release as 10th anniversary makes lots of sense to me
[23:26] <cjwatson> lifeless: Maybe not as such but he certainly knew about the project then
[23:27] <lifeless> cjwatson: certainly
[23:28] <lifeless> cjwatson: you can pick jan 16th or thereabouts if you want 'when folk knew' :)