[15:16] <jiangfuqiao> Cannot find Glib2! If you are using binary packages based system, check that you
[15:16] <jiangfuqiao> have the corresponding -dev/devel packages installed.
[18:18] <K_> TheKK:test
[18:20] <TheKK> K_: good
[18:20] <TheKK> good


[00:12] <jelmer> mwhudson, I can reproduce the determining revisions to fetch slowness
[00:23] <thumper> jelmer: awesome
[00:23] <thumper> jelmer: what was it
[00:24] <jelmer> thumper: building against svn 1.4 slows down bzr-svn significantly
[00:24] <jelmer> because we attempt to fetch all revision properties manually for each revision in the repository and don't cache the results
[00:25] <jelmer> something that can apparently take 7 hours for some repositories where it takes less than a minute when built against svn 1.5...
[00:26] <thumper> Ursinha: ping
[00:26] <thumper> jelmer: hmm.. interesting
[00:26] <thumper> jelmer: on a side note, has bzr-hg been fixed for the infinite recursion bug?
[00:32] <jelmer> thumper: I haven't had a chance to look into it yet.
[00:32] <poolie> hi jelmer
[00:33] <jelmer> 'morning poolie
[00:42] <wgrant> sinzui: Is there a good reason that admins cannot promote others to admins?
[00:46] <thumper> wgrant: admins of what?
[00:46] <wgrant> thumper: Teams.
[00:46] <thumper> wgrant: they can can't they?
[00:46] <thumper> wgrant: I thought they could
[00:46] <wgrant> No. Only owners can.
[00:46] <thumper> really?
[00:46] <wgrant> Admins can demote, but not promote.
[00:47] <thumper> hmm...
[00:47] <thumper> seems a bit screwy to me
[00:47] <thumper> if you trust them to be admins, let them be admins, not half-admins
[00:47] <wgrant> Right.
[00:50] <sinzui> wgrant: I am certain there is not *good* reason admins cannot promote
[00:51] <wgrant> It has been like that for as long as I remember, and I have always wondered about it.
[00:53] <thumper> wgrant: patches accepted :)
[01:06] <maxb> Submitting a patch loosening security policy can feel weird
[01:08] <wgrant> Yes.
[01:08] <wgrant> Particularly a security policy that has been around for perhaps 5 years and nobody knows the purpose of.
[01:09] <maxb> I don't suppose there's any light at the end of the tunnel w.r.t. removing xx-resetpassword-of-sso-account.txt ?
[01:09] <maxb> I miss being able to do a clean test run
[01:10] <wgrant> The OpenID RP stuff should cause that to vanish.
[01:10] <wgrant> But I'm not sure how far off that is...
[01:23] <Ursinha> thumper: pong
[01:24] <thumper> Ursinha: I was wondering if you had used (QAed for me) the API to get branches by date
[01:24] <Ursinha> thumper: not yet
[01:24] <thumper> ok
[01:24] <Ursinha> thumper: but will soon
[01:24] <thumper> :)
[01:34] <maxb> wgrant: I don't suppose you've already debugged ""GpgmeError: (32, 176, 'Unknown error code')"" on lucid, have you?
[01:36] <wgrant> maxb: Try http://paste.ubuntu.com/379455/
[01:36] <wgrant> (in sourcecode/pygpgme)
[01:36] <wgrant> Other than that, most stuff seems to work with stock Lucid + ppa:launchpad.
[01:37] <wgrant> I haven't run the whole test suite lately, though.
[01:37] <wgrant> The need to downgrade python-setuptools has mysteriously vanished in the past week or so.
[01:37] <maxb> nifty
[01:38] <maxb> I'm actually not working on 2.6 or lucid right now, having got distracted by "No really, don't load my system bzrlib.plugins.*"
[01:38] <wgrant> Is there a codeimport queue visible somewhere?
[01:38] <wgrant> I'm wondering if I would be better to branch from Git locally rather than waiting for my new import to complete.
[02:05] <mwhudson> lolz
[02:05] <mwhudson> mwh@grond:unicod-branch-names-bug-449528$ ls lib/canonical/launchpad/images/*gray*
[02:05] <mwhudson> lib/canonical/launchpad/images/persongray.png  lib/canonical/launchpad/images/teamgray.png
[02:05] <mwhudson> mwh@grond:unicod-branch-names-bug-449528$ ls lib/canonical/launchpad/images/*grey*
[02:05] <mwhudson> lib/canonical/launchpad/images/edit-grey.png  lib/canonical/launchpad/images/link-grey-arrow.png
[02:06] <mwhudson> wgrant: no, it's not visible
[02:06] <mwhudson> (there's already a bug report about that)
[02:06] <thumper> mwhudson: looking for a grey tick?
[02:06] <mwhudson> should be getting more machines soon though...
[02:06] <mwhudson> thumper: well
[02:06] <mwhudson> thumper: playing around with the icon for "partial success", yeah
[02:07] <mwhudson> tried a few things, i think a grey tick works best of the things i've tried
[02:08]  * thumper nods
[02:08]  * thumper is working through today
[02:08] <mwhudson> i've made one in gimp
[02:08] <mwhudson> i was actually trying to decide what to save it as :-)
[02:09] <thumper> I thought we use american spelling in the code, so gray
[02:09] <mwhudson> wfm
[02:10] <wgrant> Partial success? Does that mean incremental imports are sufficiently close that UI is a concern?
[02:10] <mwhudson> wgrant: yes
[02:14] <mwhudson> the gimp still has a pretty weird ui
[02:15] <wgrant> mwhudson: The single window mode is coming in the next release.
[02:16] <thumper> just in time to be removed by default?
[02:16] <mwhudson> wgrant: hooray
[02:17] <mwhudson> thumper, wgrant: http://people.canonical.com/~mwh/partial-success.png
[02:17] <thumper> mwhudson: looks good
[02:17] <wgrant> thumper: It's still probably a year away.
[02:18] <thumper> mwhudson: did you just desaturate the image?
[02:18] <mwhudson> thumper: yeah
[02:18] <wgrant> mwhudson: Nice.
[02:18] <wgrant> It has a tooltip, I hope?
[02:18] <mwhudson> wgrant: yeah
[02:18] <mwhudson> "Partial Success"
[02:21] <thumper> mwhudson: where is our list of contributor agreement signers?
[02:21] <wgrant> We're mostly not in the team :(
[02:22] <mwhudson> thumper: private url given to you in private channel
[02:22] <thumper> :)
[02:23] <lifeless> also the public team - you should get added wgrant :)
[02:28] <wgrant> Does anybody actually use Empathy?
[02:31] <jelmer> wgrant: Yep
[02:31] <jelmer> mwhudson, thumper: Does the "determining revisions to fetch" step always take very long or just on the initial import?
[02:31] <mwhudson> jelmer: just on the initial import
[02:31] <jelmer> mwhudson: I don't think there's a lot we can do to work around that other than upgrade the svn on lp to 1.5
[02:32] <mwhudson> jelmer: ok, want to fire off an rt asking how much work that would be?
[02:32] <mwhudson> or i can
[02:32] <wgrant> jelmer: With MSNP?
[02:32] <jelmer> wgrant: yep
[02:33] <jelmer> mwhudson: how urgent is it? Lucid will have a recent enough version of svn
[02:33] <wgrant> jelmer: Odd. I keep trying to use it, but give up every time because it silently drops incoming messages once the conversation times out after a minute or so.
[02:33] <wgrant> It doesn't drop messages for you?
[02:34] <jelmer> wgrant: not that I have seen
[02:36] <mwhudson> jelmer: maybe not all that urgent, it's only a performance thing after all
[02:50] <wgrant> Subject: None
[02:50] <wgrant> Thankyou Launchpda.
[03:23] <maxb> FYI, I already have svn 1.6 *and* pysvn for hardy in a PPA
[03:26] <_thumper_> mwhudson: https://code.edge.launchpad.net/~ian-clatworthy/bzr/whats-new/
[03:26] <thumper> mwhudson: a bad error... know what caused it?
[03:26] <thumper> mwhudson: my guess is the scanner, I just don't know why
[03:26] <thumper> mwhudson: also, we should get bzr 2.1 final into LP
[03:26] <mwhudson> thumper: no, that's the puller
[03:27] <mwhudson> thumper: 2.1 is probably trivial, drop the tarball in, update versions.cfg and ec2 land
[03:27] <thumper> mwhudson: does the puller set the stacked branch in the DB?
[03:27] <mwhudson> thumper: yes
[03:27] <thumper> ah
[03:27] <mwhudson> that's a pretty nasty error indeed
[03:27] <mwhudson> maybe duelling pullers?
[03:28] <mwhudson> a remirror will probably clear it up
[03:32] <thumper> hmm..
[04:13] <thumper> mwhudson: it is past beer o'clock
[04:13] <thumper> mwhudson: are you tweaking the code import dispatcher?
[04:13] <mwhudson> thumper: yeah
[04:13] <mwhudson> thumper: i'm thinking about it
[04:14] <thumper> mwhudson: thinking about doing it Monday?
[04:14] <mwhudson> or maybe i'll stop instead and go and sit outside until emma calls and tells me she's finished work
[04:14] <mwhudson> thumper: yeah
[04:14] <thumper> you know if you try again, you'll miss something
[04:14] <thumper> do it Monday
[04:14] <thumper> have a beer
[04:14] <mwhudson> ok :-)
[04:14] <thumper> I hope it is sunnier in Wellington than here
[04:14] <thumper> we used to have sun
[04:14] <thumper> but it has gone again
[04:15] <mwhudson> it's a very very nice day today actually
[04:15] <thumper> do you think the description should go above or below?
[04:15] <mwhudson> sunny, not too windy
[04:15] <thumper> I'm thinking above
[04:15] <mwhudson> bit cool perhaps
[04:15] <mwhudson> thumper: did you make that screeny?
[04:15] <thumper> yeah
[04:15] <thumper> 6
[04:16] <thumper> http://people.canonical.com/~tim/description6.png
[04:16] <mwhudson> oh right
[04:17] <mwhudson> i'm not really sure
[04:17] <mwhudson> i guess it makes sense for it to go high up the page
[04:25]  * mwhudson EOWs
[04:25] <poolie> cheerio
[04:26] <poolie> thumper: really a description and a commit msg and a comment?
[04:26] <thumper> poolie: the editable description is instead of the initial comment
[04:27] <poolie> oh ok
[04:27] <poolie> more like a bug then?
[04:27] <thumper> poolie: trying to be
[04:33]  * thumper EOWs too
[04:52] <Ursinha> thumper: are you still there?
[04:53] <Ursinha> thumper: if so, do you have an example of usage of the branches search by date?
[05:46] <kfogel> thumper: looking rocketfuel-setup, I see that it does 'bzr branch lp:~launchpad-pqm/launchpad/devel $LP_TRUNK_NAME' after attempting 'bzr launchpad-login $lpusername'.  This means that if the user has a Launchpad login (and successfully logs in) that the 'bzr branch' will happen over bzr+ssh://, right?
[05:46] <kfogel> thumper: oh, I see your answer in https://answers.edge.launchpad.net/launchpad/+question/101139
[05:46] <kfogel> thumper: which I think says that
[05:52] <poolie> hello kfogel
[05:53] <kfogel> poolie: hello
[06:22] <wgrant> BjornT: Can you please review https://code.edge.launchpad.net/~wgrant/launchpad/sprbu-columns-to-sprb/+merge/18995 reasonably soon?
[08:18] <henninge> Morning!
[08:18] <henninge> How do I find out the current database user in a unit test?
[08:27] <adeuring> good morning
[08:57] <BjornT> wgrant: sure. sorry, i had missed that one, thanks for reminding me.
[08:59] <wgrant> BjornT: Thanks.
[09:12] <mrevell> Hi
[11:01] <deryck> Good morning, all.
[12:02] <wgrant> bigjools: The circular import may not be a good reason to not do it, but is there a good reason *to* do it?
[12:10] <bigjools> because Attribute sucks and it takes 60 seconds to do the right thing
[12:11] <bigjools> and on that note, I am heading out for a liquid lunch while my power is off
[14:09] <wgrant> Why is db-devel so ancient?
[14:44] <deryck> BjornT, ping
[14:47] <BjornT> deryck: pong
[15:15] <kfogel> deryck, adeuring: just fyi (re my mail about failing test): the EC2 run that I submitted right after that has now passed, so I'm going to pqm-submit my changes for bug #255868.  sinzui already reviewed.
[15:15] <mup> Bug #255868: Project summary page should show links to patches <story-patch-report> <ubuntu-upstream-relations> <Launchpad Bugs:In Progress by kfogel> <https://launchpad.net/bugs/255868>
[15:16] <deryck> kfogel, sounds good.  Was going to look later, but glad it's passing now.
[15:16] <deryck> kfogel, it looked to me like your ec2 run was against devel instead of db-devel, based on the log messages you sent.
[15:19] <adeuring> kfogel: I haven't received your mail (yet)...
[15:19] <kfogel> adeuring: was to bugs team members (all)
[15:20] <kfogel> deryck: based on the two outputs (failure and then success), you're right, and yet the command line was the same and specified db-devel.  hmmm.
[15:20] <adeuring> kfogel: our mail server seems to be a bit slow sometimes...
[15:21] <kfogel> deryck: I'll keep the records; would like to figure out what happened here -- a lost EC2 run costs a lot.
[15:22] <deryck> kfogel, you use `utilities/ec2 land` to make sure the syntax is good, too.
[15:22] <deryck> kfogel, I think most of us use that now, rather than ec2 test.
[15:22] <kfogel> deryck: yeah, should just do that
[15:23] <kfogel> ok, submitted.  out for a while
[15:24] <BjornT> bigjools: ping?
[15:25] <bigjools> BjornT: yo
[15:26] <BjornT> bigjools: we currently have both DistributionSourcePackage and DistributionSourcePackageCache in the db. it feels like we should combine those two, but i'm not sure what the latter is used for. can you enlighten me?
[15:28] <bigjools> BjornT: it's for searching; the distro search page uses it
[15:29] <bigjools> gets updated every day
[15:29] <bigjools> there's an fti on the various columns
[15:30] <BjornT> bigjools: would  make sense add settable columns to it? i.e., have it represent a distribution source package in the db, which can have bug reporting guide lines for example.
[15:31] <bigjools> BjornT: I don't follow what you mean
[15:35] <BjornT> bigjools: basically, i think that the DistributionSourcePackage python class should be connected to a table in the db. this table should both have some properties for the package, for example bug reporting guidelines, which is settable by users, as well as acting as a cache for certain properties, like the latest publication record.
[15:36] <BjornT> bigjools: would it make sense to use DistributionSourcePackageCache for this? is would it be better to keep it for searching only?
[15:37] <bigjools> BjornT: there is already a DistributionSourcePackageInDatabase !
[15:37] <bigjools> I would keep it for searching only
[15:37] <bigjools> DistributionSourcePackage and DistributionSourcePackageInDatabase should be merged; that was always the intention
[15:38] <bigjools> and you'll notice the latter has the bug_reporting_guidelines on it
[15:38] <BjornT> bigjools: yes, i know. my question was whether it would make sense to merge DistributionSourcePackageInDatabase and DistributionSourcePackageCache
[15:39] <bigjools> BjornT: I don't think it does
[15:39] <bigjools> partly because the latter is also archive-specific
[15:39] <bigjools> i.e. it gets generated with knowledge about publications
[15:44] <BjornT> bigjools: ok, makes sense. DistributionSourcePackageCache should probably get renamed as to not cause that much confusion.
[15:44] <bigjools> yeah, that's cool
[15:44] <bigjools> naming is the hardest part of programming, after all :)
[15:57] <BjornT> bigjools: do you have time to have a quick call to talk me through https://code.edge.launchpad.net/~wgrant/launchpad/sprbu-columns-to-sprb/+merge/18995? i'm interested in the model's PoV
[15:57] <bigjools> BjornT: yeah can do
[15:58] <bigjools> call me on skype when you're ready
[15:59] <BjornT> cool
[16:02] <jtv> BjornT, can I bounce something off you?
[16:02] <jtv> BjornT: we have a bunch of fake transaction managers in tests.
[16:03] <jtv> Would it be a good idea to make that a test helper?
[16:10] <BjornT> jtv: could be, if they are similar enough.
[16:10] <jtv> BjornT: looks like.  In fact this is one reason why I still like to pass transaction managers around: it's a reasonably clear injection point for tests.
[17:08] <adiroiban> gmb: hi. Any news regarding the landing of this MP https://code.edge.launchpad.net/~adiroiban/launchpad/bug-522188/+merge/19395 ?
[17:08] <gmb> adiroiban: !??! It appears to have disappeared again. This is vexing. I'll go and see if I can find it.
[17:09] <adiroiban> :))
[17:11] <gmb> adiroiban: It looks like the ec2 run just sort of died and didn't email anyone to say that it had. Starting a new run now; I'll keep an eye on it.
[17:12] <adiroiban> gmb: np. I will remind you on monday if it will fail again
[17:13] <gmb> adiroiban: If that happens I'm going to take a very large axe to our ec2 utility.
[17:20] <adiroiban> :)
[17:24] <jtv> abentley: preparing to land your branch-url branch
[17:25] <abentley> jtv, rock.
[17:26] <jtv> abentley: that's a whopping 4-branch landing.  :)  Can I just land the last branch (after pumping) and the whole pipeline will be included?
[17:29] <abentley> jtv, yes.  As long as all your stuff is fully merged into mine.  You can check that with bzr missing.
[17:31] <jtv> abentley: it says "you have 15 extra revision(s):"
[17:31] <jtv> followed by... yes, 15 revisions.
[17:34] <jtv> abentley: does that mean I'm good to go?
[17:35] <abentley> jtv, well, it depends whether the extra revisions are in my branch or yours.
[17:35] <jtv> abentley: I merged yours into mine.
[17:37] <abentley> jtv, okay, never mind then.
[17:37] <jtv> abentley: and all those 15 revisions are mine.
[17:37] <abentley> jtv, the general answer to your question is yes.
[17:37] <jtv> \o/
[17:38] <abentley> If you want to land multiple branches, and all the branches have been merged directly or indirectly into one of them, you can just land that one.
[17:39] <abentley> pumping is just a convenient way of ensuring all the branches are merged into the last pipe.
[17:42] <jtv> convenient indeed... it's been fun!
[18:37] <sinzui> EdwinGrubbs: I like your proposal. I'll reply with some questions about how communities complete for the involvement portlet.  Let's assume we are going to extend the Involvement portlet instead of creating a new portlet
[20:05] <deryck> Have a good weekend, everyone.
[20:42] <maxb> I have a MP that is "review approve"d but not "merge approve"d. Would someone possibly be around who could flip that setting and ec2 land it?   https://code.edge.launchpad.net/~maxb/launchpad/bug-497731/+merge/19732
[21:20] <rockstar> gary_poster, hi
[21:20] <gary_poster> hi rockstar
[21:21] <gary_poster> (I'm about to turn into a pumpkin btw, but can reply using cell phone in a bit)
[21:22] <rockstar> gary_poster, so, if I need to create a new script in bin/ then I need to create a .in file in buildout-templates/bin, but where do I tell buildout about it?
[21:25] <gary_poster> rockstar, if it is one of those kinds of templates--free form--then just putting it in the directory is sufficient.  rerunning bin/buildout will notice and build.  Note that there are other kinds of scripts that let you keep your code in the tree (see lp-windmill, for instance, and how it is hooked up in buildout.cfg [scripts] entry-points, but I imagine you've seen those and rejected them with reason.
[21:41] <wgrant> Can somebody please ec2 land https://code.edge.launchpad.net/~wgrant/launchpad/sprbu-columns-to-sprb/+merge/18995 for me?
[21:43] <lifeless> lp-project-upload looks nearly-useful
[21:43] <lifeless> but I really don't want to depend on ubuntu-dev-tools for an upstrea project
[21:43] <lifeless> any suggestions on where I should ask pitti to move the code to ?
[21:49] <wgrant> lifeless: Maybe launchpad-tools, the collection of useful Launchpad-related scripts?
[21:49] <lifeless> wgrant: I'm thinking lptools
[21:49] <lifeless> https://bugs.edge.launchpad.net/lptools
[21:49] <lifeless> is that what you were meaning?
[21:50] <lifeless> dobey: btw
[21:50] <wgrant> lifeless: I meant a hypothetical thing, the lack of existence of which was a bug.
[21:50] <lifeless> dobey: _puhlease_ beat statik into giving you some work time to do QA [we do allow for this when we open source something, so that we're not doing abandon-ware]
[21:50] <lifeless> wgrant: hah. Well it exists but is named differently.
[22:06] <wgrant> Why has db-devel not been merged into for a couple of days?
[22:28] <dobey> lifeless: was off today, so was out doing other things in the nice warm sun :)
[22:28] <lifeless> fair 'nuff
[22:29] <lifeless> dobey: I'd love to see you do an upstream release :)
[22:30] <dobey> lifeless: During this cycle, I don't even really have enough work time to finish the stuff for Lucid. But I think after Lucid, I want to switch to our ops+ team for 6-12 months, and do a lot of work on infrastructure/tools, and lptools would certainly fall into that realm
[22:30] <dobey> lifeless: yeah, I know. I would if I had any time to fix the bugs and do it :)
[22:31] <lifeless> dobey: just doing a release would be helpful
[22:31] <lifeless> it would mean that the packaging would be a little more sane.
[22:31] <dobey> lifeless: I'll see if I can't do that. I need to do a release for changeup also
[22:33] <lifeless> changeup ?
[22:34] <dobey> A fairly simple thing to make it possible to automatically restart ubuntuone-syncdaemon, gwibber-daemon, and similar 'behind the scenes' user-level services, on upgrades
[22:34] <lifeless> dobey: also if you can merge the non-packaging parts of bzr+ssh://bazaar.launchpad.net/~lifeless/debian/sid/lptools/sid/ that would be really nice.
[22:34] <dobey> what's non-packaging in there?
[22:35] <lifeless> dobey: e.g.: bzr merge lp:~lifeless/debian/sid/lptools/sid/; bzr revert debian; bzr revert --forget-merges; bzr commit -m "whatever"
[22:35] <lifeless> dobey: have a look :>
[22:36] <dobey> hrmm
[22:36] <lifeless> a bunch of work from ted
[22:36] <lifeless> desktop files
[22:36] <lifeless> a preferences dialog
[22:37] <dobey> sounds frightening
[22:40] <lifeless> https://code.edge.launchpad.net/lptools/+activereviews
[22:40] <lifeless> would be good to merge
[22:40] <dobey> I wish I could get the same list of reviews from the API, as is shown on http://code.launchpad.net/~dobey/+activereviews
[22:40] <lifeless> it has most of the changes I'm talking about
[22:40] <lifeless> dobey: you can now I believe
[22:41] <lifeless> or not quite; you can get reviews-requested-for-an-object
[22:41] <dobey> yeah, I just haven't had time to look at his branch because it's so big
[22:41] <lifeless> which is not the same
[22:41] <lifeless> dobey: JFDI, honestly, everyone is running his branch.
[22:49] <james_w> dobey: you can now get those two reviews on your +activereviews page with lp.me.getRequestedReviews() or similar
[22:50] <lifeless> james_w: I thought that didn't handle group membership yet?
[22:50]  * lifeless really wants a direct match to +activereviews too
[22:51] <james_w> but those reviews are requested of dobey n'est pas?
[22:51] <lifeless> in this case
[22:52] <james_w> hence "those two reviews"
[22:52] <lifeless> it may be that +me/activereviews isn't showing what it should either ;>
[22:52] <james_w> it's a start
[22:53] <james_w> so, one API request to get them all would be good
[22:53] <james_w> and just returning a list of merge proposals is fine, as you can sort client side
[22:54] <james_w> so we need a parameter to getRequestedReviews() to do a recursive lookup, then a modification to the internal method it calls
[22:54] <dobey> There's a 3rd review on a private branch that isn't directly requested of me, but is via group membership
[22:54] <james_w> do you know if there is a way to get the transitive closure of team memberships for a person?
[22:55] <james_w> dobey: ah, I can't see that one, indeed you can't get that easily with this API yet
[22:55] <james_w> I'd like to fix that, but it's more than just exposing something over the API like the current version
[22:55] <dobey> I don't really care about sorting. That's a trivial problem. :)
[22:55] <dobey> I just want all the reviews pertaining to me


[06:51]  * Obsidian1723 Anyone here know which is the better method to us (and why) to send video over CAT5e? S-Video or HDMI? I don't want video or audio attenuation/degredation.
[21:58] <Takyoji> Woo http://games.slashdot.org/story/10/05/23/154218/First-Pandora-Console-Reaches-Customer


[13:32] <alci> I think this bug deserves a look and should be worked on. It seems complete to me, and affect libreoffice on unity, which is a central piece of software for the desktop : https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1049612
[13:32] <ubot2> Ubuntu bug 1049612 in libreoffice "Libre Offices global menu does not appear randomly when opening the application" [Undecided,Confirmed]
[15:23] <TheLordOfTime> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/515386  <-- if "Thunderbird" upstream project says its Invalid, are we leaving it as a valid bug in ubuntu?
[15:23] <ubot2> Ubuntu bug 515386 in xdg-utils "No attachment when Thunderbird is set as default client." [Medium,Fix released]
[15:45] <micahg> TheLordOfTime: that was fixed in Thunderbird almost a year and a half ago
[15:45] <TheLordOfTime> micahg, scrollbacks in #ubuntu.  someone says it still exists
[15:45] <TheLordOfTime> micahg, its also set as "Triaged", not "Fix Released" if i'm reading it right
[15:46] <TheLordOfTime> it was fixed in xdg-utils
[15:46] <TheLordOfTime> not thunderbird specifically
[15:46] <TheLordOfTime> unless someone mis-entered bug info
[15:47] <micahg> probably no one closed the task
[15:49] <micahg> I see the bug, but idk where it is
[15:49]  * micahg would suggest filing a new bug since it was fixed
[15:50] <TheLordOfTime> mhm.  i'm curious why thunderbird upstream shows "Invalid"
[15:50]  * micahg wonders if simple scan or xdg-email regressed
[15:50]  * TheLordOfTime opens the upstream bug
[15:50] <micahg> TheLordOfTime: resolved duplicate
[15:50] <TheLordOfTime> micahg, ah.  well to point this one out, openscan shows as invalid too
[15:51] <TheLordOfTime> i wonder if xdg-email (where it was "fixed") regressed, as you surmised
[15:51] <TheLordOfTime> but as i dont use thunderbird, i can't  test :P
[16:20] <MCR1> JohnLea: Do you have a minute ?
[16:20] <MCR1> JohnLea: Hi :), btw.
[16:21]  * TheLordOfTime yawns
[16:21] <TheLordOfTime> hiya MCR1
[16:21] <MCR1> heya
[16:28] <JohnLea> MCR1; hyia
[17:37] <TheLordOfTime> MCR1, you missed JohnLea
[17:37] <TheLordOfTime> just to let you know.
[19:06] <TheLordOfTime> https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1065196  <-- that should be grub2, no?
[19:06] <ubot2> Ubuntu bug 1065196 in grub "update-grub sets wrong kernel root for linux dual boot systems" [Undecided,New]
[19:06] <TheLordOfTime> since grub2's what we use in precise and later?
[19:07] <TheLordOfTime> against grub2 *
[19:11] <micahg> TheLordOfTime: depends, I think both are still in the archive
[19:11] <TheLordOfTime> micahg, when i see a Package: grub (not installed), that usually means grub2
[19:12] <TheLordOfTime> hence the question
[19:12] <TheLordOfTime> Package: grub (not installed) <-- that
[19:12] <micahg> probably then
[19:12] <TheLordOfTime> micahg, or would it be better to ask them which they have installed?  (grub vs. grub2)
[19:14] <TheLordOfTime> rather than just set it to be against grub2 instead of grub?
[19:14] <TheLordOfTime> just to confirm which we should have it affect
[19:14] <micahg> you could ask I guess, probably doesn't hurt to be sure
[19:15] <TheLordOfTime> yeah, better safe than sorry in my opinion
[19:15] <TheLordOfTime> esp. with stuff where legacy and current versions both exist in the repos
[19:15] <TheLordOfTime> (like grub and grub2)
[21:09] <augcampos> I there can some help me, with a ATI Radeon HD4850 in ubuntu 12.10?
[21:10] <TheLordOfTime> augcampos, did you try asking in #ubuntu+1 ?
[21:10] <augcampos> every time I reboot the resoluton of 2nd monitor is set to 1024x768
[21:11] <augcampos> yes
[21:11] <TheLordOfTime> and?
[21:11] <TheLordOfTime> because that's where you're a tad more likely to get support
[21:11] <TheLordOfTime> since user support for issues is typically in #ubuntu or #ubuntu+1
[21:12] <augcampos> i have to set it to 1680x1050 in command line


[01:51] <tsimonq2> Wassaaaaaaaaaaaaaap
[01:53] <tsimonq2> wxl, lynorian: Looking
[01:54] <tsimonq2> Oh
[01:54] <tsimonq2> wxl: Got a bug yet bud?
[01:55] <wxl> tsimonq2: almost out so bug lynorian
[01:56] <tsimonq2> lynorian: What's the deal?
[01:57] <lynorian> bug 1667128
[01:57] <tsimonq2> Thanks.
[01:57] <lynorian> touchpad other than moving cursor and buttons does not work at all
[01:59] <wxl> off for most of the eve
[02:03] <lynorian> tsimonq2, need me for anything else
[02:04] <lynorian> I might get more testing done but am pretty hungry and will be going for dinner
[02:04] <lynorian> but will give enough time for a respin probably
[02:04] <tsimonq2> lynorian: Not really
[05:17] <q4a> hi all.
[05:18] <tsimonq2> o/ q4a
[05:18] <q4a> I'm trying to disable lock screen after wake from suspend
[05:18] <q4a> on lxqt on ubuntu 17.04
[05:19] <q4a> tested set org.gnome.desktop.lockdown disable-lock-screen 'true'
[05:20] <q4a> but did't help. Also checked xscreen-saver - it's disabled
[05:20] <q4a> may be some config in powermanager
[05:20] <q4a> ?
[05:22] <q4a> package "gnome-power-manager" installed by default, but it has only /usr/bin/gnome-power-statistics
[09:49] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate amd64 [Zesty Beta 1] has been updated (20170223)
[09:49] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate i386 [Zesty Beta 1] has been updated (20170223)
[10:07] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Zesty Beta 1] has been updated (20170223)
[10:07] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop i386 [Zesty Beta 1] has been updated (20170223)
[10:29] <b_b> hi
[17:48] <tsimonq2> Please someone go help Lubuntu and Ubuntu Studio with ISO QA tests.
[17:48] <tsimonq2> Beta 1 needs some love.
[17:48] <tsimonq2> lynorian, b_b ^^
[17:50] <b_b> hi tsimonq2
[17:50] <tsimonq2> b_b: Could you please help us test? :)
[17:50] <b_b> not for now sorry, i'm totally on other things :\
[17:51] <tsimonq2> Ok, thanks anyways
[17:58] <acheronuk> tsimonq2: I synced the lubuntu iso spun today earlier, so will try a couple
[17:58] <tsimonq2> acheronuk: Please please please :)
[18:11] <acheronuk> welcome to lubuntu 16.10! noted
[18:35] <acheronuk> tsimonq2: Lubuntu Desktop amd64 test cases done
[18:37] <b_b> "il y a une sorte de brouillard sur toute cette gestion de l'arrière boutique"
[18:37]  * b_b aime bien le brouillard
[18:37] <b_b> "et ça n'aide pas à rassurer ceux qui ont des doutes"
[18:37] <b_b> mince...
[18:44]  * acheronuk tries lxqt in this VM before throwing it away
[21:10] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate amd64 [Zesty Beta 1] has been marked as ready
[21:10] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Zesty Beta 1] has been marked as ready
[21:10] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate i386 [Zesty Beta 1] has been marked as ready
[21:10] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop i386 [Zesty Beta 1] has been marked as ready


[00:59] <ahoneybun__> hello all
[01:33] <ahoneybun> hello
[02:51] <ahoneybun> hello all
[03:17] <ahoneybun> hey palasso
[05:11] <palasso> hey ahoneybun ;)
[06:06] <soee> god morning
[09:35] <shadeslayer> Riddell: ScottK is LGPL compatible with GPL v2?
[09:43] <Riddell> shadeslayer: which LGPL, there's three of them.  compatible to do what?
[09:43] <Tm_T> ScottK is LGPL?
[09:43] <shadeslayer> saidinesh5: ^^
[09:44] <shadeslayer> hah
[09:44]  * saidinesh5 checks
[09:44] <shadeslayer> Riddell: would it be possible for you to evaluate https://github.com/vovoid/vsxu for inclusion in the ubuntu archive?
[09:44] <shadeslayer> from a source/license PoV
[09:45]  * Riddell clones
[10:00] <Riddell> Visualizations, project files and art provided with this release:
[10:00] <Riddell>     You may use them as you see fit, but we reserve the right to decide wether
[10:01] <Riddell>     or not you can remix them.
[10:01] <Riddell> shadeslayer: so the visualisation files can't be included
[10:01] <Riddell>   All design and graphic content/skins etc (c) Vovoid Media Technologies AB
[10:01] <Riddell>   are provided to you as-is, not for remixing.
[10:01] <Riddell> nor can they
[10:01] <shadeslayer> saidinesh5: ^^
[10:01] <Riddell>   Example assets:    Raya (c) Katie De Sousa.
[10:01] <Riddell> no licence on that
[10:02] <saidinesh5> Ah
[10:10] <Riddell> shadeslayer, saidinesh5: the cpp code is a mix of GPL 2, GPL 2+, LGPL 2+ and LGPL 3+.  GPL 2 isn't compatible with LGPL 3+
[10:10] <saidinesh5> Oh
[10:10] <saidinesh5> and LGPL2.1 ?
[10:10] <Riddell> yes, that's the same as LGPL 2+
[10:11] <saidinesh5> no i mean is GPLv2 compatible with LGPL2.1 ?
[10:11] <Riddell> yes that's fine
[10:11] <Riddell> for both linking and distributing together
[10:11] <saidinesh5> Ah
[10:11] <saidinesh5> Riddell: which bits are using LGPL3+ ?
[10:12] <Riddell> ./tools/socket_library/trunk/src/
[10:12] <Riddell> says   find . -name *cpp | xargs licensecheck | grep LGPL
[10:13] <saidinesh5> Ahh
[10:14] <Riddell> so maybe those bits don't get linked in, I'm not sure
[10:15] <saidinesh5> yep those arent linked afaik
[10:48] <apol> maybe kdevelop should depend on kate-data? https://bugs.kde.org/show_bug.cgi?id=318188
[10:50] <Riddell> apol: yeah I'll add that
[10:51] <Riddell> apol: probably also worth that being noted in the sources, in a README (it points at http://www.kdevelop.org/index.html?filename=HEAD/requirements.html but that doesn't exist) or better yet in cmake config output
[10:52] <apol> ok
[10:53] <Riddell> shadeslayer: a person has e-mailed me asking for plasma active 4 packages pointing at http://mail.kde.org/pipermail/active/2013-May/006136.html
[10:53] <Riddell> shadeslayer: I'm not sure what martin's e-mail there is saying though, I don't think there's such a thing as PA 4 yet
[10:55] <Riddell> ah it's on k-d as well
[10:56] <Quintasan> Riddell: I am to schedule a packaging sprint for PA so we can get the packages in shape
[10:57] <Quintasan> I'll do that after the damn exams
[10:57] <Riddell> very cool
[10:58] <Quintasan> Riddell: as for KTp, I'm putting uploading onhold till I get it into Debian since I believe I just just became the maintainer of it
[10:58] <Quintasan> Might as well as attempt to get DM
[11:03] <Riddell> Quintasan: mm that sounds like something that could take time
[11:15] <Quintasan> Riddell: Getting it to Debian - no. Getting DM - more likely
[11:16] <Quintasan> Riddell: When I get it to Debian I'll just ask you to sync it, or ScottK, whoever has rights to perform this magic
[11:19] <Riddell> Quintasan: mm well be careful it doesn't end up taking weeks when people could be using it and testing it
[11:20] <Quintasan> Riddell: Should uploading that take more than 3 days from now on I'll just throw in the whole stack into our repos
[11:22] <Riddell> sounds a good plan
[11:29] <Riddell> hi tariq_
[11:30] <Quintasan> lol
[11:30] <Quintasan> It's almost like apachelogger's reaction to python
[11:30] <tariq_> Hi RIddell!
[11:31] <tariq_> still getting to grips with this IRC!
[12:48] <BluesKaj> Hey all
[15:12] <murthy> hello everyone
[15:14] <ahoneybun> murthy: hello
[15:14] <Riddell> hi murthy
[15:16]  * Riddell blogs http://blogs.kde.org/2013/06/12/nice-e-mail
[15:17] <murthy> we here some in the #kubuntu channel
[15:17] <murthy> *hear
[15:18] <ahoneybun> Riddell: always getting great emails :)
[15:21] <murthy> I have some doubts about updating a changelog for a merge
[15:22] <Riddell> murthy: what do you doubt?
[15:30] <murthy> a package has only 1 conflicting file which is debian/control, grab-merge script generates the source from A(debian), B(ubuntu) and produces C  which contains the conflicting file with the two difference with markings. Now the debian/control segments that are in conflict in A(debian) is not right and is totally ignored by choosing all the details from B(ubuntu). What will be my changelog entry and is C ubuntu or debian. I will paste the debian/control
[15:30] <murthy>  given by grab-merge and the merged one now
[15:31] <murthy> Riddell: ^
[15:32]  * Riddell waits for paste
[15:32] <murthy> http://paste.kde.org/771608/
[15:32] <murthy> ^the file in conflict
[15:33] <murthy> http://paste.kde.org/771614/
[15:33] <murthy> ^ the new one
[15:33] <Riddell> murthy: please use   diff -u  and paste that again
[15:34] <murthy> Riddell: between the two?
[15:34] <Riddell> yes
[15:34] <murthy> ok
[15:34] <Riddell> http://paste.kde.org/771608/ does not use diff -u
[15:37] <murthy> Riddell: I couldn't get you
[15:38] <murthy> Riddell: http://paste.kde.org/771608/ is generated by grab-merge script
[15:38] <murthy> Riddell: http://paste.kde.org/771626/
[15:38] <murthy> thats the one with diff -u of both the control files
[15:40] <Riddell> hmm, I'm not sure it is :)
[15:40] <Riddell> anyway, build-deps looks like no changes needed so keep debian
[15:40] <Riddell> X-Python-Version need to work out if that's needed (by dh_python or something like that)
[15:41] <Riddell> Breaks: python-albatross-common   probably still needed, check changelog
[15:41] <Riddell> Breaks: python-albatross likewise
[15:41] <Riddell> changes to Maintainer: are needed if there's any ubuntu changes
[15:41] <Riddell> voila
[15:41] <Riddell> murthy: how did you get on with kdiff3 ?
[15:42] <murthy> Riddell: why what?
[15:43] <Riddell> murthy: what why what?
[15:44] <murthy> Riddell: What about kdiff3?
[15:44] <murthy> Riddell: have you noticed python in build-depends ?
[15:45] <Riddell> murthy: did you merge it?
[15:46] <murthy> Riddell: you mean the file or the status of the merge request?
[15:46] <Riddell> murthy: the package of kdiff3 needs merged https://merges.ubuntu.com/universe.html
[15:46] <murthy> oh :D
[15:47] <murthy> I thought you were talking about the kdiff app
[15:47] <murthy> I am doing albatross now
[15:47] <murthy> #1189942
[15:48] <murthy> LP : #1189942
[15:48] <murthy> whats the syntax?
[15:48] <Riddell> bug 1189942
[15:50] <murthy> Riddell:  this "python (>= 2.6.6-3~)" is added to the ubuntu's build-depends have you noticed?
[15:50] <murthy> Riddell: so the resulting merge is a debian one?
[15:50] <Riddell> murthy: it's not needed as far as I can see, python-all would being it in
[15:50] <Riddell> murthy: it's not needed as far as I can see, python-all would bring it in
[15:51] <murthy> Riddell: ok, in case if it is need what should i put in the changelog?
[15:52] <Riddell> murthy: merge from debian, remaining changes: add python build-dep (needed for reason foo)
[15:52] <murthy> Riddell: so the target is debian
[15:53] <murthy> oops
[15:53] <Riddell> murthy: yes, we want to have as few changes from debian as possible
[15:53] <Riddell> don't be afraid of adding them but also don't add them for no reason, it just adds more work
[15:53] <Riddell> ok I'm out for the evening, good luck
[15:55] <murthy> see you later
[15:57] <murthy> yofel: are you there?
[15:57] <yofel> yes?
[15:57] <murthy> yofel: can you help me with a changlog for a merge
[15:58] <murthy> yofel: its a very simple one
[15:58] <yofel> sure
[15:58] <murthy> thank you, i will paste the files
[15:58] <murthy> yofel: http://paste.kde.org/771608/
[15:59] <murthy> ^ thats the debian/control file in conflict given by grab-merge
[16:00] <yofel> ok
[16:00] <murthy> yofel: assume all the ubuntu stuff is correct, now update the  changelog which i will paste now
[16:01] <murthy> yofel: http://paste.kde.org/771662/
[16:01] <murthy> the last entry is mine
[16:01] <murthy> correct that please
[16:03] <yofel> murthy: well, Continuing the line, you add "Remaining changes:" and then list every change that you had to add to the debian package
[16:04] <murthy> yofel: can you do that and show me?
[16:04] <yofel> you don't need to document the maintainer update though
[16:05] <murthy> yofel: just this one changelog
[16:08] <yofel> murthy: try it yourself and I'll tell you what's wrong ;) take http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/digikam/view/head:/debian/changelog as example
[16:09] <murthy> yofel: ok i will try
[16:16] <shadeslayer> yofel: can you send me a test mail at rohangarg AT kubuntu dot org ?
[16:23] <yofel> shadeslayer: done
[16:23] <shadeslayer> that subject ...
[16:23] <yofel> I couldn't resist :P
[16:24] <shadeslayer> :D
[16:24] <shadeslayer> the error mail usually has the same subject ;)
[16:27] <murthy> yofel: http://paste.kde.org/771692/
[16:27] <murthy> the updated changelog
[16:47] <yofel> murthy: looking
[16:48] <yofel> murthy: do we really still need that build-dep on python?
[16:48] <yofel> rest looks fine, except that I don't know enough about python packaging to decide what X-Python-Version should be set to
[16:48] <murthy> yofel: no it has to be checked, but for now, i am concerned about the changelog
[16:49] <murthy> yofel: so expect the python stuff everything ok(in case of the changelog wordings)?
[16:49] <yofel> murthy: change "Update" to "Add" or "Set" as that's not really an update of anything but a new thing
[16:50] <murthy> ok
[16:50] <yofel> other than that, the changelog is fine for the changes in the control file
[16:51] <murthy> ok thank you, i will check for the phthon build-dep and update the changelog accordingly
[18:49] <vHanda> Riddell: Could you please verify this package? https://sourceforge.net/projects/oscaf/files/shared-desktop-ontologies/0.11.0/
[18:49] <vHanda> shadeslayer: ^
[18:51] <yofel> vHanda: what do you need verified?
[18:51] <vHanda> just that the package is fine
[18:51] <vHanda> and that I haven't done anything stupid
[18:51] <vHanda> s/package/tarball
[18:53] <yofel> hm, looks fine on first glance
[18:54] <vHanda> cool, thanks
[18:54] <vHanda> It looked fine to me as well, but I wanted to be sure before I made the release announcement
[19:07] <ahoneybun> hello valorie
[21:07] <valorie> greets
[21:09] <ahoneybun> valorie: hello
[21:11] <valorie> hello, ahoneybun
[21:11] <ahoneybun> valorie: littlegirl has been really working hard
[21:11] <valorie> I saw what you said the first time; I always read all the scrollback
[21:11] <valorie> I saw that
[21:11] <ahoneybun> oh
[21:14] <valorie> I sort of stepped back because it seemed she was doing her work off the wiki for some reason
[21:14] <valorie> so many pastebins!
[21:14] <valorie> once she's slowed down, I'll look
[21:14] <ahoneybun> to see the work before saving
[21:14] <valorie> it would be nice to get all our pages with a common format
[21:14] <valorie> I was working on that as I could
[21:14] <ahoneybun> yea
[21:18] <valorie> Riddell: lovely blog!
[21:19] <ahoneybun> valorie: did you see the rewrite of the managing repos
[21:20] <ahoneybun> https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic/ManagingRepositories
[21:22] <valorie> wth, why do we have the old way to add repositories, instead of the apt-add-repo way?
[21:22] <valorie> which is much superior
[21:22] <ahoneybun> oh
[21:22] <valorie> not a good idea at all, IMO
[21:22] <valorie> perhaps a link to the old way, for people running ancient versions
[21:23] <valorie> but seriously, those have long been EOL
[21:23] <ahoneybun> littlegirl is running 10.04
[21:23] <ahoneybun> how would you remove them then?
[21:24] <valorie> oh, I dunno
[21:24] <valorie> sec
[21:25] <valorie> grrr, I had a good explanation of that, now it's gone
[21:25] <valorie> :(
[21:25] <valorie> oh, well
[21:27] <valorie> short answer: sudo ppa-purge ppa:<repository-name>/<subdirectory>
[21:27] <ahoneybun> does that work without additional software?
[21:27] <valorie> what?
[21:27] <valorie> I'm not sure what you mean
[21:28] <valorie> ppa-purge is something we should document anyway, for those who have added problematic PPAs
[21:29] <valorie> anyway, I see no reason to make that page enormous by documenting an outdated method of adding and removing repos
[21:29] <valorie> but that's just my opinion
[21:30] <ahoneybun> true
[21:30] <ahoneybun> I'm ok with making it more uptodate
[21:30] <ahoneybun> up to date
[21:31] <valorie> I'm just wondering why good work was removed, and replaced with old stuff
[21:32] <ahoneybun> well I thought we needed work done on how to deal with ppa;s
[21:35] <valorie> sure
[21:35] <valorie> I was wrong though, there is a ppa-purge package
[21:35] <valorie> http://www.webupd8.org/2009/12/remove-ppa-repositories-via-command.html
[21:35]  * valorie goes to find official documentation of this
[21:37] <valorie> so otherwise it can be done thus: sudo add-apt-repository --remove ppa:someppa/ppa
[21:37] <yofel> there's 2 definitions of "remove" mixed here
[21:37] <valorie> probably a better idea to not introduce a package
[21:37] <valorie> true
[21:37] <yofel> add-apt-repository --remove -> disables the source entry but keeps the packages
[21:38] <yofel> ppa-purge -> removes the PPA and downgrades what it can
[21:38] <valorie> and there are cases for doing both
[21:38] <valorie> or either
[21:39] <ahoneybun> valorie: do what you think is best and I will work on it later
[21:39] <ahoneybun> gtg
[21:39] <valorie> https://launchpad.net/ubuntu/precise/+package/ppa-purge
[21:39] <valorie> see you later
[21:39] <ahoneybun> yea \


[03:43] <pitti> Good morning
[08:43] <DanChapman> Good Morning all :-)
[08:49] <JackYu> morning:)
[09:11] <smartboyhw> Noskcaj, are you sure you can cope with timezone issues as a release manager?
[09:11] <Noskcaj> probably not, note the "if no ones else does"
[09:12] <smartboyhw> Noskcaj, heh heh
[09:13]  * smartboyhw won't be, he is already release team member of 2 flavorus-.-
[09:18]  * Noskcaj has virtually no power, anywhere
[09:18] <Noskcaj> (possibly a good thing)
[09:18] <smartboyhw> Noskcaj, one day, I'm expecting you to have more power
[09:18] <smartboyhw> This is a meritocracy after all:P
[09:19] <knome> before that, i'm expecting the "i'll do that" -attitude, "i'll can do that if no one else does"
[09:19] <knome> *not
[09:20] <knome> it's important to really want to do something, otherwise it's highly likely you'll lose your interest...
[09:20] <Noskcaj> ok
[09:21] <smartboyhw> Noskcaj, it's time you start to take responsibilities:P
[09:22] <Noskcaj> i want to, but I'm never online for meetings and hardware limits what i can do in terms of devel and testing
[09:23] <smartboyhw> Noskcaj, 1. We don't have meetings specifically for release managers-.-
[09:23] <smartboyhw> Only if you take up as a full QA lead if you should
[09:23] <smartboyhw> *then you should
[09:23] <smartboyhw> Noskcaj, phillw himself isn't a dev:P
[09:23] <smartboyhw> And as for testing, no worries;)
[09:24] <knome> Noskcaj, not being able to be in the meetings can be fixed, either by moving the meetings here and there or if you have things you are responsible for, communicate about them outside the meetings
[09:24] <knome> we do have all kinds of mailing list and stuff to cooperate with others
[09:24] <smartboyhw> Noskcaj, you ARE lucky though, in the 12.10 cycle we have meetings with the release team almost every week:P
[09:24] <Noskcaj> ok
[09:24] <knome> i'm just saying, it's not about the others, it's about you; whether you are committed to something or not
[09:25] <knome> (and i'm speaking in a general level, don't feel like i'm pushing you to pick up any release manager's task if you don't wish to)
[09:26] <smartboyhw> It's like that in Ubuntu Studio too. I am the Release Manager, so I commit to my release and testing-related responsibilities:)
[09:32]  * Noskcaj thinks trying for MOTU might be his next target
[09:32] <smartboyhw> Noskcaj, good.
[09:32] <smartboyhw> Well, I would rather prefer being a DD or DM:P
[09:33] <smartboyhw> Noskcaj, if you became a MOTU expect me to ask you to sponsor packages:P
[09:36] <Noskcaj> smartboyhw, I've done a fair bit of stuff in debian too, but hardware (no VMs) and the fact the pbuilder keeps breaking make it hard for me t do stuff proprly
[09:37] <smartboyhw> Noskcaj, oh
[09:37] <pitti> Noskcaj: OOI, what breaks for you in pbuilder? (I abandoned it quite some time ago)
[09:38]  * smartboyhw quite like the pbuilder-dist sid
[09:38] <Noskcaj> pitti, cowbuilder, pbuilder-dist, it thinks sid uses saucy-proposed and aqueorea doesn't have a good gpg key
[09:39] <smartboyhw> It's the saucy pbuilder-dist which keeps unable to download packages-.-
[09:39] <Noskcaj> ok
[09:39] <smartboyhw> Noskcaj, uh hum, I don't think pitti knows about aequorea
[09:39] <smartboyhw> And, don't forget, it's still a project in the womb:P
[09:39] <pitti> no, I don't
[09:40] <Noskcaj> ignore that bit then
[09:40] <pitti> well, LP builders do use -proposed
[09:40] <pitti> my own schroots usually don't, though
[09:43] <smartboyhw> pitti, I won't let my pbuilders touch -proposed unless absolutely necessary
[12:59] <smartboyhw> balloons, good morning (U. S. Time) to you
[14:49] <smartboyhw> balloons, ping for some testcase consulation
[14:49] <balloons> smartboyhw, aloha
[14:50] <smartboyhw> balloons, aloha. The upgrade (image) testcases are not mentioning that it only works when there is only 1 version of Ubuntu (without any other OS)
[14:50] <smartboyhw> See https://docs.google.com/document/d/1bZ4yQIVgGaUGSYu3qiUHnQt3ieBZoqunP_DcleHCr3I/preview?pli=1#bookmark=id.35db66d9d3b3
[14:50] <smartboyhw> How can we clarify that
[14:51] <balloons> smartboyhw, you can upgrade ubuntu even if you have another os like windows installed according to what I read in the document
[14:51] <smartboyhw> balloons, not with two versions of Ubuntu
[14:51] <smartboyhw> So, we need to clarify a bit-.-
[14:51] <smartboyhw> Or, with multiple partitions
[14:52] <balloons> ahh you mean when you have essentially 2 versions of ubuntu and potentially another os
[14:52] <smartboyhw> Both Studio and Kylin are getting it misunderstood without xnox telling us about this
[14:52] <smartboyhw> balloons, yes
[14:53] <balloons> my guess is the installer doesn't automagically upgrade either version of ubuntu
[14:53] <smartboyhw> balloons, yes, but I think most of us don't know that
[15:00] <xnox> smartboyhw: you are miss-quoting me.
[15:01] <smartboyhw> xnox, well, at least you gave us the doc-.-
[15:01] <smartboyhw> If not, we wouldn't have known it
[15:02] <xnox> smartboyhw: balloons: an upgrade or reinstall option is available, if there is only one ubuntu installation. One can have other operating systems installed, as long as none of them are also ubuntu.
[15:02] <xnox> (and here it's any ubuntu system that identifies itself as such, thus all official flavours are simply ubuntu)
[15:02] <balloons> xnox, smartboyhw yes I got that.. xnox you said it the simplest ;-) More than one version of ubuntu and you don't try and guess which one to upgrade :-)
[15:03]  * smartboyhw makes simple things complicated (always)
[15:03] <balloons> smartboyhw, does xnox make sense? 1 ubuntu install means upgrade and re-install are available. More than one and it's not. Other OS's installed have no bearing
[15:04] <smartboyhw> balloons, OK
[15:04] <balloons> and yes note ubuntu + ubuntu studio means there are 2 versions of ubuntu, and thus no re-install and upgrade
[15:05] <DanChapman> afternoon balloons & smartboyhw o/
[15:05] <smartboyhw> Good evening DanChapman
[15:05] <smartboyhw> (And I will go to sleep after the Release Team gives orders on Beta 1)
[15:05] <balloons> ty xnox
[16:38] <skaet> Beta 1 is now released.
[16:38] <skaet> Thanks to everyone who has been helping to test this and make it available.
[16:39] <SergioMeneses> skaet, \o/
[16:39] <SergioMeneses> balloons, sent email about it
[16:40] <skaet> :-)   Goodness.    Thanks balloons.
[16:40] <balloons> ty everyone :-)
[16:41] <SergioMeneses> btw balloons do you know what happen with phillw?
[16:42] <balloons> SergioMeneses, he got a little burned out and frustrated.. a little down time would do him some good
[16:43] <elfy> good for eveeryone from time to time
[16:43] <elfy> it also helps if you're not the only one doing something
[16:44] <SergioMeneses> balloons, I see I hope that he come back soon
[16:44] <SergioMeneses> elfy, agree
[16:44] <elfy> I like our team - we all pitch in and help others where we can and if we can
[16:45] <SergioMeneses> :)
[16:46] <elfy> and people respond to calls for help - if I'd had to do our bunch of testcases on my own - I'd still be doing them
[16:47] <SergioMeneses> chilicuil, I saw your post about the jam
[16:49] <chilicuil> SergioMeneses: =), I'm gonna have fun in one of the remote UGJ organized by the michigan team
[16:50] <SergioMeneses> chilicuil, sounds good maybe I can join as well
[16:52] <chilicuil> SergioMeneses: feel free =), http://loco.ubuntu.com/events/ubuntu-michigan/2319-ubuntu-global-jam-s-series/
[16:53] <SergioMeneses> 2) Say "I'm Jamming!" in the channel. (This is a requirement.) (Note: not really)
[16:53] <SergioMeneses> jajaja
[16:53] <balloons> we should update the testing page again.. just needs a light touchup
[16:56] <SergioMeneses> balloons, remembers me about lubuntu-wikis project
[18:19] <knome> pitti, send me your preferred email address and i'll add that to auto-approve for xubuntu-devel
[19:07] <balloons> letozaf, hello
[19:08] <letozaf> balloons, hello
[19:08] <balloons> thomi, when your about I'd like to chat about some unicode errors that continue to pop up in rssreader tests
[19:08] <balloons> letozaf, so how are you?
[19:08] <letozaf> balloons, fine and you ?
[19:09] <balloons> getting back into the groove of things
[19:09] <letozaf> balloons, I worked on rssreader autopilto tests, I was waiting for the adding feed changes to be made as Joey told me by mail
[19:09] <letozaf> balloons, but now I found some conflicts
[19:10] <letozaf> balloons, is there a way to fix them quickly that you know
[19:10] <letozaf> balloons, or is it better to branch again and put my tests back in some way ?
[19:11] <letozaf> balloons, yeah think you had a lot to work after vUDS :D
[19:12] <balloons> letozaf, I made some changes to RSSReader to try and help the tests out.. In general, it seems like the app is much better now. I think I can add and remove things easily enough
[19:13] <letozaf> balloons, I had rixed the remove topic test, but when I merged found a bug on adding a feed...
[19:14] <letozaf> balloons, well lets say that the changes become too quickly, maybe I should just branch again and see what the new things are
[19:14] <letozaf> balloons, and fix my tests again :'(
[19:14] <balloons> letozaf, I don't think you need to.. what changes do you have that aren't landed?
[19:15] <balloons> my changes were just to clear the database each time so you don't have issues adding a topic, etc
[19:15] <letozaf> balloons, yes but when my tests were working fine i merged and they broke
[19:15] <letozaf> balloons, anyway if you want I can push them so you can have a look
[19:16] <balloons> letozaf, you should be able to merge easily enough..
[19:16] <balloons> there might be conflicts, but you should be able to resolve them
[19:17] <balloons> anyways, I want to figure out why the tests seem to fail with a unicode error all the time
[19:17] <balloons> I assume your still working on adding back tests for the other features :-)
[19:17] <letozaf> balloons, yes that is a weired "bug"
[19:18] <letozaf> balloons, I had fixed the remove topic test but now nothing works again :(
[19:18] <letozaf> balloons, I think I will try to solve the conflicts
[19:19] <balloons> letozaf, they shouldn't be bad.. I don't think I messed with the tests that much
[19:20] <letozaf> balloons, there is a thing I do not understand, I now find  files with "extension" .THIS .OTHER .BASE  after the merge
[19:21] <letozaf> balloons, how do you fix that ? is there something about these in bzr documentation ?
[19:21] <balloons> letozaf, right, that is showing you the different versions
[19:22] <letozaf> balloons, yes I kind of understood that but do not know how to fix it
[19:22] <letozaf> balloons, without making a mess I mean
[19:22] <balloons> I think git makes it easier to solve conflicts, but that's probably because I was more used to git.. regardless, it can seem daunting but it's not in reality
[19:23] <balloons> http://doc.bazaar.canonical.com/beta/en/user-reference/conflict-types-help.html
[19:23] <letozaf> balloons, thanks I will read this now hope I can fix them :)
[19:23] <balloons> letozaf, so you can say bzr resolve --action=
[19:23] <balloons> I gave you the link, but I find it confusing even :-p
[19:24] <letozaf> balloons, :P
[19:25] <balloons> letozaf, this is closer to explaining how I do it
[19:25] <balloons> http://muffinresearch.co.uk/archives/2007/06/05/dealing-with-conflicts-in-bazaar-version-control/
[19:25] <balloons> basically I use meld as the graphical diff application
[19:25] <balloons> so "bzr diff --using meld"
[19:26] <balloons> then I edit the file incorporating the new changes along with my stuff.. meld makes it easy
[19:26] <balloons> then you do "bzr resolve" and your done
[19:27] <letozaf> balloons, thanks, well... I got got some reading to do :P
[19:27] <balloons> letozaf, you have conflicts right now right?
[19:27] <letozaf> balloons, yes
[19:27] <balloons> so let's walk through quickly
[19:27] <balloons> no need to read the docs.. you'll be more confused than me
[19:27] <balloons> bzr conflicts
[19:28] <balloons> that shows your conflicts..  do you have meld installed?
[19:28] <letozaf> balloons, http://paste.ubuntu.com/6067704/
[19:29] <letozaf> balloons, no I will install it now
[19:30] <balloons> letozaf, ok perfect. So make sure you have meld installed, then do this "bzr diff --using meld"
[19:30] <letozaf> balloons, ok got meld now
[19:30] <balloons> that will load each of those conflicted files one at a time. it'll show your version along with the new version. Edit your version inside meld until it contains everything you want
[19:31] <letozaf> balloons, looks good :) let me see
[19:31] <balloons> make sure to save when your done
[19:31] <balloons> when your all done editing the files and everything is good, just tell bzr it's resolved
[19:31] <balloons> bzr resolve --all
[19:31] <balloons> your = you are
[19:32] <balloons> I must be feeling good, I caught myself
[19:32] <letozaf> balloons, but the differences in RssFeedPage.qml are changes made by devs I think
[19:32] <letozaf> balloons, for instance: text: DateUtils.formatRelativeTime(i18n, model.pubdate)
[19:33] <balloons> letozaf, yes, make sure you get all the differences put in by other folks.. don't just remove them :-)
[19:33] <letozaf> balloons, oh yes  I understand, good
[19:33] <balloons> if you don't want any of your changes in a file, you can have bzr do the merge for you by just taking the new version
[19:34] <balloons> bzr resolve --take-other FILENAME
[19:34] <balloons> make sense?
[19:35] <letozaf> balloons, yes I will try now, let's see
[19:37] <letozaf> balloons, I tried to quit meld to yse bzr resolve for some files ... but it say's it modified files did I make a mess or what ?
[19:37] <letozaf> to use, sorry not to yse
[19:38] <balloons> letozaf, you can never make a mess when you have files version controlled :-)
[19:38] <letozaf> balloons, good :P
[19:39] <letozaf> balloons, so now I can use bzr resolve --take-other for fieles with changes made only by others and meld for the ones I worked on, right ?
[19:40] <balloons> letozaf, yep
[19:40] <letozaf> balloons, ok let try, thanks
[19:40] <balloons> your a pro now
[19:40] <balloons> bah!
[19:40] <letozaf> balloons, :P
[19:40] <balloons> you are a pro now
[19:41] <balloons> I'm 0/2, but I noticed.. maybe knome would still be proud
[19:42] <letozaf> balloons, well wait until  I fix the conflicts ... :P
[19:47] <letozaf> balloons, cool I like this meld :)
[19:48] <balloons> pretty handy eh?
[19:49] <Noskcaj> balloons, Once Dan Chapman has finished re-writing testdrive for GTK3, would you support the idea that we "officially" support KVM, and leave all the other VMs as "unsupported". e.g. If Vbox breaks in any release, we'll just have a warning saying it's unsupported and un-tested
[19:49] <Noskcaj> It was phill's idea
[19:53] <letozaf> balloons, yeah ! magic!
[19:58] <knome> balloons, hehe :)
[19:58] <knome> i can't agree with not supporting other VM's
[19:59] <balloons> Noskcaj, I'm not on the dev team for testdrive, but as a user, I like choice :-)
[19:59] <knome> if we can't get some virtual machines working with ubuntu, how can we make sure it works on various hardware?
[19:59] <balloons> that said, nothing wrong with not wanting to support something that frequently breaks
[19:59] <balloons> the question is, why does it break?
[20:00] <TheDrums> "Unsupported" and "if it breaks not our fault" just seem to be cop outs, like "Patches accepted" :P
[20:00] <knome> that's debatable, but i don't know the history well enough to argument for or against either side
[20:00] <Noskcaj> Part of our reasoning was the latest ubuntu kernal breaks Vbox (semi-proprietary), parallels is mac only(and proprietary), and VMware (a feature request) is also proprietary.
[20:01] <knome> i suppose the question is: how many of the testers regularly use there other methods?
[20:01] <balloons> I'd guess many folks use vbox.. indeed, all the tutorials I show use it
[20:01] <knome> so wouldn't that speak pro-vbox even if it broke here and there?
[20:01] <Noskcaj> I recently swapped from Vbox to KVM, and i've not seen any losses
[20:01] <TheDrums> If your CPU doesn't have "The KVM feature" kvm/qemu is *very* slow.
[20:02] <knome> what TheDrums said.
[20:02] <Noskcaj> yeah, that's one of my worries
[20:02] <TheDrums> So mainly I use it for testing flash booting, and OVMF/EFI.
[20:05] <balloons> I would say choice is good, so my question remains -- why does vbox break? kernel modules issue or ? there is an open source version
[20:06] <Noskcaj> balloons, AFAIK, ubuntu uses the open-surce version, and phill has talked to the kernal team and they have said they won't fix it
[20:08] <knome> so are you saying vbox is only broken if you use the non-open-source version?
[20:09] <Noskcaj> knome, i don't know
[20:09] <knome> that's what i gathered from your comment
[20:09] <knome> if that's not what you are saying, what are you saying?
[20:10] <balloons> well the module might not be in core, which wouldn't be surprising, but it should have a maintainer
[20:10] <knome> it's not a huge problem for testers if it only works with the open source version
[20:11] <knome> but i'd imagine we might lose quite some users with not supporting the partly proprietary vbox?
[20:12] <Noskcaj> Where is phillw when i need him?
[20:12] <Noskcaj> All i know is Vbox doesn't work too well and parallels is mac only
[20:13] <knome> vbox doesn't work too well?
[20:14] <knome> it has worked for me pretty much always?
[20:14] <Noskcaj> on saucy
[20:14] <knome> on saucy.
[20:14] <balloons> same.. but to be fair I don't always use testdrive to launch it.
[20:15] <knome> i never use testdrive
[20:15] <knome> if it's broken when used with testdrive, doesn't that imply testdrive is broken?
[20:24] <letozaf> balloons, ok I solved the conflicts but now when I launch autopilot  I get this: http://paste.ubuntu.com/6067890/
[20:24] <letozaf> balloons, something wrong with TopicTab... or what ever
[20:24] <TheDrums> knome: Guessing no extension pack?
[20:25] <balloons> letozaf, looks like qml file error
[20:25] <balloons> did you make changes in the qml?
[20:25] <letozaf> balloons, hope not, I tried to be carefull
[20:25] <balloons> best to just grab the upstream version of it, and add in the objectnames you need
[20:26] <balloons> they are just oneliners :-)
[20:26] <letozaf> balloons, yes I will do it thanks
[20:28] <knome> TheDrums, extension pack..?
[20:28] <TheDrums> That's a "no" :)
[20:29] <knome> i personally hope virtualbox works with all kinds of setups, but even if *buntu* only works as a guest with the basic open source version, i'm more than fine with *that*
[20:29] <knome> just saying it might lose ubuntu some users, and when any virtualization solutions do not work, it's a possible loss
[20:32] <TheDrums> knome: https://www.virtualbox.org/wiki/Downloads support for PXE, USB, and RDP.
[20:32] <knome> yeah, i figured we're talking about that
[20:32] <knome> but i got no confirmation if that was the cause to any breakage.
[20:34] <wxl> there's a problem with the kernel that affects virtualbox?! this is news to me. why? what?
[20:35] <knome> there might be or might not be, nobody is able to confirm.
[20:35] <wxl> :/ where does the suggestion come from?
[20:35] <Noskcaj> wxl, phill found it, and has since taken a break from ubuntu
[20:36] <wxl> Noskcaj: i've been mostly afk. did he post to the list about this?
[20:36] <knome> if he's the only one who hit it, it can't be a awfully critical bug.
[20:36] <Noskcaj> wxl, no, just a conversation with the kernal team, then with smartboyhw and i on his channel
[20:36] <wxl> huh.
[20:37] <wxl> well i guess i won't worry about it too much then XD
[20:37] <knome> an unfiled bug is as useless as no bug at all...
[20:38]  * TheDrums files a bug on knome.
[20:38] <knome> what bug?
[20:38] <knome> bad description, marking as invalid
[20:38] <wxl> you sure it's not a dupe?
[20:39] <letozaf> balloons, it's weired I got the ubuntu-rssreader-app.qml file from upstream added just 4 or 5 objectNames and get this output again: http://paste.ubuntu.com/6067940/
[20:39] <letozaf> balloons, ubuntu-rssreader-app.qml:178 Type TopicTab unavailable
[20:40] <letozaf> balloons,            TopicTab {
[20:40] <letozaf>                 id: shortsTab
[20:40] <letozaf>                 objectName: "Tab0"
[20:40] <letozaf>                 title: i18n.tr("Shorts")
[20:40] <letozaf>                 topicId: 0
[20:40] <letozaf>                 isAll: true
[20:40] <letozaf> balloons, doesn't look like something I changed, what could it be ?
[20:44] <letozaf> balloons, I branched the rssreader in another directory and it works fine, so I better try to bring my tests in there otherwise I might just make a mess and don't want to
[20:45] <letozaf> balloons, I will copy them over to the new directory that works :P :(
[20:45] <balloons> letozaf, go for it
[20:46] <letozaf> balloons, :P
[20:47] <letozaf> balloons, better go now, it's getting late I will continue tomorrow
[20:47] <letozaf> night everyone!


[01:49] <lool> dantalizing: Not sure I understand your question
[01:59] <lool> persia: Wow, does mobile-basic-flash work for you?
[02:00] <lool> persia: It's broken for most of us with xul 1.9
[02:22] <david88_lin>  /msg NickServ IDENTIFY 123456
[02:22] <david88_lin>  /msg NickServ IDENTIFY
[03:06] <lool> david88_lin: Hmm I'm afraid this went out to the public
[03:06] <lool> david88_lin: You'd better change password now
[03:31] <david88_lin> I am changed. Thanks.
[06:20] <dholbach> good morning
[12:54] <persia> lool: It would be more accurate to say that I did not find any degradation with the updated mobile-basic-flash, and that the changes seemed reasonable (and helpful) from a textual review.
[13:04] <theseinfeld> Anybody knows why the ume-xephyr-start was removed from the ume-config-common package?
[13:07] <theseinfeld> lool any idea why the ume-config-common doesn't include the ume-xephyr-start?
[13:09] <phreekbird|work> so i just started reading about ume ... looks great, i am very impressed
[13:10] <phreekbird|work> just wanted to show my appreciation and let everyone know that its a great looking product ... keep up the good work!
[13:14] <theseinfeld> anybody here from the ubuntu-mobile team? davidm?
[13:15] <theseinfeld> so after doing the apt-get full-upgrade the ume-xephyr-start is gone
[13:15] <theseinfeld> i check the old backup to see that it was in the ume-config-common package and now that package doesn't have it
[13:15] <theseinfeld> if i start manually the xephyr and the hildon-desktop, boing
[13:15] <theseinfeld> core dump
[13:15] <theseinfeld> great success
[13:16] <theseinfeld> anybody knows what is going on?
[13:18] <theseinfeld> agoliveira, any idea?
[13:20]  * theseinfeld is sleeping...*snorrr* *snorrrrrr*
[13:21] <agoliveira> theseinfeld: Sorry, no idea.
[13:21] <theseinfeld> agoliveira, but you acknowledge that it is gone :)
[13:22] <theseinfeld> I am not crazy :)
[13:22] <theseinfeld> right :)
[13:22] <agoliveira> theseinfeld: I don't know. I'm working on an unrelated urgent work since yesterday evening and didn't run UME since.
[13:22] <agoliveira> Let me turn on my Q1
[13:22] <theseinfeld> hardy in 1 day
[13:23] <agoliveira> Gah, sorry
[13:24] <agoliveira> theseinfeld: I'm updating an image. Let's see what happens.
[13:24] <theseinfeld> full-upgrade
[13:29] <theseinfeld> agoliveira let me know
[13:31] <agoliveira> theseinfeld: You're right, ume-xephyr-start was removed.
[13:31]  * theseinfeld is not crazy then...
[13:31] <theseinfeld> agoliveira, do you know why?
[13:31] <theseinfeld> :D
[13:31] <theseinfeld> or what is subsituting it?
[13:32] <agoliveira> theseinfeld: No idea, sorry. Looks more like an error.
[13:32] <theseinfeld> ok
[13:32] <theseinfeld> I will check with the uploader
[13:32] <theseinfeld> maintainer
[13:32] <theseinfeld> thanks
[13:32] <theseinfeld> then i fill a bug report :)
[13:32] <agoliveira> Great
[14:18] <lool> theseinfeld: Hey, I'm afraid we were sleeping in our timezone when you popped the issue
[14:18] <lool> I think inuka might have broken it with the latest ume-config-common upload
[14:18] <lool> I'll check with him
[14:19] <theseinfeld> lool thanks
[14:19] <theseinfeld> lool just to let you know :)
[14:19] <theseinfeld> lool actually I am quite active in ume
[14:20] <theseinfeld> lool i also applied for membership
[14:20] <theseinfeld> lool but you denied it :)
[14:20]  * theseinfeld sulks in the corner...
[14:21] <persia> Which is broken again?  I'm also seeing strange startup behaviour, but it may be different.
[14:22] <theseinfeld> ume-config-commong
[14:22] <theseinfeld> at least
[14:22] <theseinfeld> persia ...
[14:23] <theseinfeld> moreover there is that xf86-video-psb
[14:23] <theseinfeld> in the fsets
[14:23] <theseinfeld> that is named differently in ubuntu
[14:23] <theseinfeld> thank you moblin :)
[14:23] <theseinfeld> so this is more like a MIC issue
[14:23] <theseinfeld> :D
[14:30] <persia> Ah yes.  The latest ume-config-common doesn't actually install the scripts.  Looks like a typo.  Testing a fix now...
[14:34] <theseinfeld> good
[14:34]  * theseinfeld likes persia...
[14:35] <persia> theseinfeld: I should be thanking you.  I've been hunting for the last hour as to why my device has no window manager on boot.  The pointer is very much appreciated.
[14:35] <theseinfeld> persia, thanks
[14:36] <theseinfeld> i've been swearing here as well :)
[14:39] <theseinfeld> persia have to go now
[14:39] <theseinfeld> persia but I will be back tomorrow...
[14:39] <theseinfeld> cheers
[14:50] <lool> persia: Oh you're looking into ume-config-common?  thanks!
[14:51] <lool> persia: Can you let inuka know if you fix it?
[14:51] <persia> lool: Just fixed.  About to push to PPA.  Should I notify by email?
[14:53] <lool> persia: inuka?  Yeah email is good enough
[14:53] <lool> Or file a bug and assign to him
[14:53] <lool> But I told him to debdiff his .debs before upload, grah
[14:54] <persia> The upstream tarball is actually infected by the issue as well: everything is currently duplicated.  I'll catch inuka by mail to cover details.
[14:55] <lool> duplicated?
[14:56] <persia> $(DESTDIR) was missing /debian/, so the build put the target in $(CURDIR).  It looks like there was a test-run of the Makefile before tar creation, so the "build" results are in the tarball.
[14:57] <persia> Anyway, fixed version in the PPA: updated images should boot to hildon, rather than to default X (or at least it does so on my device).
[15:05] <lool> persia: THanks
[15:08] <agoliveira> persia: I would catch inuka by the throat instead of by email! :)
[15:08]  * persia is on the wrong side of the world for that :)
[15:09] <agoliveira> persia: Yeah but one can dream, right? :)
[17:22] <Xiliath> so anybody been able to boot ume yet?
[17:23] <agoliveira> Xiliath: UME boots and runs, what's your problem?
[17:25] <Xiliath> well i downloaded it, made install on usb flash disc using moblin image creator, but i couldn't do any thing
[17:25] <Xiliath> so i downloaded the newest release version, of 8.04 UME and i kept getting an error for my broadcom chip saying the firmware wasn't installed
[17:26] <Xiliath> so i fixed that problem, but with the new version it finishes loading, and says Ubutnu UME tty1
[17:26] <Xiliath> Login:
[17:26] <Xiliath> and the screen just flashes
[17:29] <Xiliath> i tried using xypher but all i get is a gray screen when i launch it, and i can't load UME from there
[17:30] <Xiliath> i tried live and live rw boots on flash discs
[17:30] <persia> Xiliath: Gray screen?  Are you using the PPA repository?  You might need to wait for a new ume-config-common to build.
[17:31] <Xiliath> you done a boot from flash?
[17:36] <Xiliat1> maybe i'll have better luck after they release 8.04 and officially realease UME
[17:38] <lool> Xiliat1: What hardware are you running on?
[17:38] <lool> Xiliat1: The builds we publish are aimed at specific hardware; it needs a lot of tweaking to run on other hardware
[17:42] <agoliveira> Xiliat1, Xiliath: and in case you didn't, I suggest you read the FAQ here: https://wiki.ubuntu.com/MobileAndEmbedded/FAQ
[17:44] <Xiliat1> yeah i know
[17:46] <Xiliat1> i tweaked the target rootfs so that my hardware would be better supported, i installed the 8.04 beta just so i could easily combine parts of my install with the target rootfs to make it all easier
[17:47] <Xiliat1> i've read all the faqs and the wiki many times
[17:48] <Xiliat1> i was amazed to find out a month or so ago about UME and have dove into working on it
[17:58] <Xiliat1> agoliveira, you a developer for ubuntu mobile?
[17:59] <agoliveira> Xiliat1: Yes, I am.
[17:59] <Xiliat1> is there a plan to port UME to ARM?
[18:00] <Xiliat1> i know that 6.04 has been and 7.04 is being ported by a 3rd party
[18:00] <agoliveira> Xiliat1: There's the idea, but nothing planned. Nokia already ported a form of Ubuntu to ARM so you may want to take a look.
[18:01] <agoliveira> Xiliat1: It's not hard to port UME to ARM, we just don't have the manpower to do it right now.
[18:04] <Xiliat1> yeah, i read about them doing it, for the N770 and 800
[18:04] <prpplague> if someone is interested in port ume to arm, tincantools would be happy to donate either a hammer kit or nail board
[18:05] <Xiliat1> what was the software nokia said they used to port most of ubuntu over to arm?
[18:06] <prpplague> davidm already has a nail board, but i'm not sure what he's planning to do with it
[18:06] <agoliveira> prpplague: This is something I want to do as a personal pet project, just don't have the time to do it now.
[18:09] <prpplague> agoliveira: we've alotted a few boards for porting projects so if someone is serious about doing the work we can donate a board
[18:09] <lool> prpplague: It looks a bit slow from my reading
[18:10] <agoliveira> prpplague: I would love to get one but unfortunately, right now, I can't promisse anything.
[18:10] <lool> 200 MHz is just plain slower than stuff you can find on the market; like Thecus
[18:10] <lool> 32 MB of SDRAM, we're not getting anywhere with that either  :-/
[18:10]  * agoliveira didn't look at the hardware
[18:10] <prpplague> lool: probably compared to what most x86 folks think of clock cycles, yea, but performance wise it fits for most projects
[18:11] <prpplague> lool: i'm not familiar with Thecus, got a url?
[18:11] <lool> prpplague: We're just super far away from that envelope
[18:11] <agoliveira> lool: a 200Mh ARM will do I suppose. The RAM is indeed low.
[18:11] <lool> And to build something like Ubuntu, you got to plan some >= 512 MB RAM
[18:11] <lool> agoliveira: It "will do", you would need 50 of them though
[18:12] <lool> Ah I'm exagerrating, at least 20 I'd say
[18:12] <prpplague> lool / agoliveira  yea its a different realm, "ram is indeed low", most of our customers are amazed at the size of the ram, hehe
[18:12] <agoliveira> lool: Don't be pushy :)
[18:12] <lool> prpplague: Sure http://www.cyrius.com/debian/iop/n2100/index.html
[18:12]  * prpplague looks
[18:13] <lool> You can replace the RAM up to 512 MB RAM
[18:13] <lool> But that's probably too low for some corner packages
[18:13]  * agoliveira will now will retreat from the fun and return to those damn licenses
[18:13] <prpplague> interesting
[18:13] <prpplague> different ballpark indeed
[18:14] <lool> It's closer to a real distribution than to an embedded one
[18:14] <prpplague> s/real/desktop
[18:14] <lool> If you like
[18:16] <prpplague> lool: so for you, something around 600MHz with 256MB sdram and 128MB flash would be more attractive?
[18:16] <prpplague> lool: and i assume you'd be doing more software dev than hardware dev
[18:16] <lool> prpplague: flash would still be a bit low to run UME; it's clearly not enough to build Ubuntu for ARM though
[18:17] <prpplague> lool:  we thats just base flash, you can always add with things like sd cards
[18:18] <lool> prpplague: The current vague goals are 192 MB RAM, 500 MB storage
[18:18] <prpplague> pretty hefty
[18:18] <lool> prpplague: Depends on the usage; to actually build the distro, we need quite a lot of space, to run UME we would need some hundreds MB
[18:18] <lool> prpplague: That's just the base goal, but then some spins have higher constraints
[18:18] <lool> For storage
[18:19] <lool> Well stronger constraints I mean
[18:19] <lool> Like 200 MB
[18:19] <lool> But you can't really reduce the RAM consumption right now when you want user apps to be able to eat some RAM
[18:19] <Xiliat1> 200mb is big for an embedded device
[18:19] <prpplague> indeed
[18:19] <lool> Well it's an embedded device where you run Firefox
[18:19] <lool> Or rather midbrowser in our case
[18:20] <lool> And you still have to allow people to run $custom_app which eats some RAM
[18:20] <Xiliat1> i had the mid browser working on ubuntu 7.10, i actually liked the look and feel better than firefox 3
[18:20] <lool> The main targets for UME are MIDs, not phones etc.
[18:20] <Xiliat1> yeah i know though some of the mids do have phone capabilities
[18:21] <lool> Sure, what I mean is that the hardware expectations are not the one of typical phones
[18:21] <Xiliat1> i can't seem to get mid browser to run on 8.04
[18:21] <lool> (Where you typically find some MB of RAM, some MB of flash)
[18:21] <Xiliat1> yeah
[18:22] <lool> That said I find the tincantools hardware cute
[18:23] <lool> It's probably not suited for running UME in its current form or building Ubuntu for ARM, but it's nice hardware nevertheless
[18:23] <prpplague> lool: thanks we have a whole line in waiting to be released, including 400 and 600 mhz devices
[18:25] <Xiliat1> is that those in the list of devices in development, or a whole new set of devices for us to drool over?
[18:25] <prpplague> Xiliat1: whole new set
[18:26] <prpplague> Xiliat1: most of them are actually complete, just waiting to go into production
[18:27] <Xiliat1> god, that makes me want to badger you with 50 questions, lol
[18:27] <prpplague> Xiliat1: you are welcome to join #edev and ask, there are a number of tincantools product users there
[18:31] <Xiliat1> yeah, but most my questions would be like, what, when, how much, ect...
[18:33] <prpplague> hehe, well most of them are on hold untill we see how much demand there is for these types of products
[18:33] <Xiliat1> well, you need to generate demand
[18:34] <prpplague> Xiliat1: yea, seeing how much there is starting with the hammer
[18:35] <prpplague> Xiliat1: http://movial.elinux.org/JackHammer_Board , http://movial.elinux.org/SledgeHammer_Board
[18:35] <prpplague> Xiliat1: 600Mhz and 400Mhz respectively
[18:36] <Xiliat1> though these are samsung processors though no?
[18:36] <prpplague> yea
[18:37] <Xiliat1> ok, i'm confused then, UME is not compiled for ARM though...
[18:37] <prpplague> Xiliat1:as i understand it right now, that is correct
[18:39] <Xiliat1> so are you talking about running UME on these boards?
[18:39] <prpplague> we hope so in the future
[18:41] <prpplague> Xiliat1: right now for GUI based stuff we are using familiar and angstrom distros
[18:41] <prpplague> Xiliat1: but the gentoo guys are also working on it too
[19:32] <pk> hello i'm newbie
[19:33] <landley> pk: hello.
[19:35] <pk> hello
[19:37] <pk> /ms
[19:37] <landley> pk: so what kind of stuff would you like to know?
[19:37] <landley> pk: I'm not typing that. :)
[19:38] <pavolklacansky> i want testing on desktop ubuntu mobile