[02:43] <joosengee> hi
[02:43] <joosengee> anyone had the problem with ubuntu 11.10
[02:43] <joosengee> I can't delete or save files on the external harddisk
[02:43] <Unit193> joosengee: I think you are looking for #ubuntu
[02:44] <joosengee> how 's about this room?
[02:44] <joosengee> What's the topic that talk?
[02:45] <Unit193> !topic
[08:08] <dholbach> good morning
[08:10] <AlanBell> morning
[20:23] <Unit193> AlanBell: ubot5` still has autojoin set for #lubuntu.
[20:23] <AlanBell> jpds: ^^
[20:24] <pangolin> ban it
[20:24] <AlanBell> that works too
[20:24] <pangolin> also leave a note with jpds so he can remove the channel from the join list
[20:29] <Unit193> pangolin: Exactly as above? Or in PM? (Don't know how long he'll be away)
[20:30] <pangolin> in Pm as well just in case he doesn't check the scroll back here.
[20:30] <pangolin> PM
[20:30] <pangolin> but you can leave it banned without any issue
[20:33] <Unit193> I did, see other channel though.
[22:36] <tsimpson> Unit193, AlanBell, pangolin: ubot5 is not managed by jpds
[22:36] <AlanBell> ah ok
[22:41] <Unit193> Sorry to him.


[01:23] <josharenson> I'm getting a hang at the Google screen after enabling qt compositor... Trying a reflash now, but anyone else seeing this?
[01:47] <josharenson> also getting an error when I do dist-upgrade
[07:39] <tsdgeos> Saviq: i am in temp scope, and from dash overview "All" open a temp scope, that happens to be the same scope, i just go "back" instead of putting it on top, no?
[07:40] <Saviq> tsdgeos, on one hand, yes... on the other there's going to be the scope stack (multiple temp scopes open on top of one another)
[07:40] <Saviq> tsdgeos, so that'll need clarification,too
[07:42] <Saviq> tsdgeos, so do the simplest thing you can do (open one on top anyway?)
[07:42] <tsdgeos> i guess that's the simplest yes
[07:43] <Saviq> and we'll add to the list
[07:55] <Saviq> mzanetti, RFC https://bugs.launchpad.net/unity8/+bug/1343760/comments/1
[07:59] <mzanetti> Saviq: done
[07:59] <Saviq> tx
[08:09] <tsdgeos> Saviq: having two temp scopes is veeeery confusing
[08:09] <tsdgeos> hope they see it once it's running on their hands
[08:10] <Saviq> tsdgeos, yeah well... that's what the stacked scopes will lead to anyway
[08:10] <tsdgeos> but not with overview in the middle
[08:10] <tsdgeos> overview in the middle is confusing
[08:14] <Saviq> tsdgeos, well, you get an overview in the middle for different temp scopes as well (and for dash, for that matter)
[08:14] <tsdgeos> not sure i understand what you mean
[08:14] <tsdgeos> but let's finish this
[08:14] <tsdgeos> and then see what people think
[08:15] <Saviq> tsdgeos, I mean it's as confusing as when you have dash | overview | scope1
[08:15] <Saviq> and dash | scope2 | overview | scope1
[08:15] <Saviq> doesn't matter if scope2 is scope1 much
[08:15] <tsdgeos> ah sure
[08:18] <mzanetti> Saviq: can you tell me what's wrong here? https://ci-train.ubuntu.com/job/landing-006-1-build/122/console
[08:18] <mzanetti> dh: Unknown sequence get-packaged-orig-source
[08:19] <Saviq> mzanetti, that's not the problem
[08:19] <Saviq> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006/+sourcepub/4301552/+listing-archive-extra is
[08:19] <Saviq> mzanetti, prompt sessions
[08:19] <Saviq> mzanetti, https://launchpadlibrarian.net/180198115/buildlog_ubuntu-utopic-amd64.qtmir_0.4.0%2B14.10.20140718-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:20] <mzanetti> ah ok... that makes more sense now
[08:20] <mzanetti> I guess I need gerry for that
[08:20] <mzanetti> gonna do some taxes crap in the meantime
[08:22] <Saviq> mzanetti, FWIW https://code.launchpad.net/~nick-dedekind/unity-mir/unity-mir.trusted_sessions/+merge/208324 this is what got merged in unity-mir to get trusted prompts going
[08:40] <dednick> Saviq: looks like qtmir silo is having issues since mir 0.5 was released.
[08:41] <Saviq> dednick, yup, qtmir needs adaptation to prompt sessions
[08:42] <dednick> Saviq: hm. well if doesn't "need" adaptation. it should still be able to work without. but can't seem to upgrade to the packages in silo anymore.
[08:42] <Saviq> dednick, it did FTBFS https://launchpadlibrarian.net/180198115/buildlog_ubuntu-utopic-amd64.qtmir_0.4.0%2B14.10.20140718-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:43] <dednick> Saviq: ah, ned change to mir. er, i can fix that.
[08:43] <Saviq> dednick, SessionAuthorized does not implement prompt_session_is_allowed
[08:43] <dednick> s/ned/new
[08:43] <Saviq> dednick, sure, guys will be happy
[08:44] <Saviq> dednick, btw, something *weird* happened with your trusted MP to unity-mir https://bugs.launchpad.net/unity-mir/+bug/1343639/comments/3
[08:46] <dednick> huh. that's weird. must have been an dodgey merge during the CI.
[08:53] <dpm> hi pete-woods, I was discussing with pstolowski what to recommend to scope developers to use as a C++ library to do networking. The tutorial code that we've got uses Qt, and I'm told that's probably not the best option. It seems you're writing the youtube scope with netcpp? Is that what you think we should recommend?
[08:54] <pete-woods> dpm: I'd say so, yes
[08:54] <dednick> Saviq: https://code.launchpad.net/~nick-dedekind/qtmir/mir-0.5-compatibility/+merge/227290
[08:54] <pete-woods> dpm: otherwise you have to deal with integrating with the Qt event loop
[08:55] <pete-woods> dpm: I'd say the vimeo scope might be a more friendly example to point developers at than the youtube one, though
[08:55] <pete-woods> the youtube API is somewhat complex
[08:55] <Saviq> mzanetti, dednick fixed qtmir ↑↑, I'll add to the silo
[08:55] <dpm> pete-woods, we don't have any example c++ scope using the latest version of the api. Do you have the vimeo scope code somewhere in LP?
[08:55] <mzanetti> Saviq: dednick: awesomes, thanks guys
[08:55] <pete-woods> dpm: https://launchpad.net/unity-scope-vimeo/
[08:56] <pete-woods> it just uses a simple synchronous API
[08:56] <pete-woods> as opposed to the youtube scope, which is peppered with futures
[08:57] <dpm> pete-woods, awesome, thanks. Another thing that some scope developers might want to do is to parse JSON returned by the remote api they're connecting to. Do you have any suggestions for c++ libraries to do that?
[08:57] <pete-woods> dpm: again, see the vimeo scope - I'm using jsoncpp
[08:57] <dpm> excellent, thanks
[08:58] <pete-woods> dpm: see the youtube scope for a more difficult example, though (https://launchpad.net/unity-scope-youtube/)
[08:58] <pete-woods> as that's really what a more involved scope should look like
[08:58] <pete-woods> doing parallelised http requests (to some degree), gzip compression, etc
[08:59] <pete-woods> dpm: there are also (in my opinion) good examples of tests, using python's tornado as a fake HTTP server
[09:01] <dpm> pete-woods, great, thanks
[09:02] <dpm> pete-woods, for now, I think the vimeo scope should suffice. I'd like to get the scope template in the SDK to add some basic networking code to do a simple API call
[09:02] <pete-woods> sounds like a good idea to me
[09:03] <pete-woods> vimeo also has the tests, though, seriously think it's not a bad idea to include a simplified version of those in the template
[09:03] <pete-woods> reacting to just one API call, as you say
[09:16] <tsdgeos> Saviq: just pushed the show dash overview from temp scope + all interactions
[09:19] <Saviq> tsdgeos, ktx
[09:19] <Saviq> tsdgeos, looks like qmluitests are back in business, btw
[09:19] <tsdgeos> \o/
[09:19] <tsdgeos> So now i have a very small todo with a popup that doesn't want to die
[09:19] <tsdgeos> and will try to cover all the interations in a qmluitest
[09:19] <tsdgeos> not sure how well this can be tested
[09:19] <tsdgeos> but will try anyway
[09:20] <tsdgeos> Saviq: there's a magic item that opens a temp scope in tryDash
[09:20] <tsdgeos> Title 2.2 in the red scope
[09:38] <Saviq> tsdgeos, oh ok
[09:53] <mhr3> tsdgeos, didn't design want that disabled?
[09:53] <tsdgeos> mhr3: no
[09:53] <tsdgeos> they want dash overview disabled from dash overview temp scopes
[09:53] <tsdgeos> but not from general temp scopes
[09:53] <tsdgeos> don't ask me why
[09:54] <pstolowski> pete-woods, i'm trying to gelp dpm with getting scope tutorial compiled with the latest api, and getting errors that come from the guts of libproperties-cpp-dev - http://pastebin.ubuntu.com/7813060/
[09:54] <pstolowski> s/gelp/help/
[09:54] <pstolowski> pete-woods, ideas?
[09:55] <pstolowski> dpm, also, here is a little bit that at least removes errors related to scopes api calls: http://pastebin.ubuntu.com/7813572/
[09:55] <mhr3> tsdgeos, i have to think too hard just to parse that sentence :P
[09:56] <mhr3> pstolowski, slot is a qt keyword
[09:56] <dpm> pstolowski, thanks! pete-woods, for more context, that tutorial code uses Qt for networking. I realise we should now probably used netcpp based on the conversation earlier, but I think at this point the easiest thing is to fix the tutorial code to work with the latest API and update the networking part earlier -> http://bazaar.launchpad.net/~dpm/ubuntu-sdk-tutorials/api-updates/revision/119
[09:56] <mhr3> pstolowski, there was a fix for properties-cpp ages ago
[09:56] <dpm> err *later, not earlier
[09:57] <mhr3> pstolowski, and it's still there :( https://code.launchpad.net/~marcustomlinson/properties-cpp/fix_qt_keyword_clash/+merge/223056
[09:57] <pstolowski> mhr3, uh oh
[09:57] <pstolowski> dpm, ^
[09:57] <mhr3> dpm, easy fix though, -DQT_NO_KEYWORDS
[09:58] <pstolowski> awesome
[09:58] <dpm> ok, let me give this a go, thanks guys
[10:02] <pete-woods> yeah, beat me to it
[10:15] <Saviq> MacSlow, one for you https://code.launchpad.net/~saviq/unity8/fix-test-notifications/+merge/227239
[10:15] <Saviq> oh well, mterry ack'ed it already, but no top-ack, so might as well
[10:21] <mhr3> tsdgeos, hmm, something's broken with dash overview
[10:21] <tsdgeos> E_MORE_DETAILS_NEEDED
[10:21] <mhr3> somehow i can't activate any of the all scopes
[10:21] <mhr3> tsdgeos, do you expect it to emit openScope()?
[10:22] <tsdgeos> no
[10:22] <tsdgeos> i expect it to have a scopeId
[10:22] <tsdgeos> mhr3: how uptodate are you?
[10:22] <mhr3> tsdgeos, pulled like 15minutes ago
[10:22] <tsdgeos> ok
[10:23] <mhr3> let me push the plugin
[10:24] <mhr3> tsdgeos, lp:~unity-team/unity-scopes-shell/overview
[10:25] <tsdgeos> mhr3: make tryDash works for you, right?
[10:26] <mhr3> yep
[10:28] <tsdgeos> ok, let me compile the plugin
[10:28] <tsdgeos> see what i can help with
[10:33] <mhr3> tsdgeos, also, searching and then reseting the search seems to break quite a lot
[10:34] <tsdgeos> works for me in tryDash :D
[10:35] <tsdgeos> still building
[10:35] <mhr3> but i do unspeakable things to the models :P
[10:45] <tsdgeos> mhr3: why is your all so weird?
[10:45] <tsdgeos> i get holes :S
[10:45] <tsdgeos> and scroll doesn't work :S
[10:45] <mhr3> tsdgeos, guess a scope without art
[10:45] <mhr3> yea, what's up with that
[10:46] <tsdgeos> i don't know
[10:46] <tsdgeos> it works fine in tryDAsh :d
[10:46] <mhr3> should i be settings collapsed-rows: 0?
[10:46] <mhr3> setting*
[10:48] <tsdgeos> no unless something weird changed
[10:49] <tsdgeos> mhr3: scopes.getScope(com.canonical.scopes.ebay) returns null
[10:49] <mhr3> oh you call that?
[10:49] <tsdgeos> yes
[10:49] <mhr3> k, fixing
[10:50] <mhr3> tsdgeos, you'd call that even when doing searches?
[10:50] <tsdgeos> mhr3: what do you mean "evn when doing searches"
[10:50] <mhr3> tsdgeos, searches can return specific canned queries
[10:50] <tsdgeos> i don't know what's that
[10:50] <tsdgeos> i open scopes
[10:51] <tsdgeos> you give me a scopeId
[10:51] <tsdgeos> i use it
[10:51] <mhr3> tsdgeos, for example search for "u2", will return amazon result telling it to search for "u2" in the "music & dvd" department
[10:52] <mhr3> if you just do getScope() all that is lost
[10:52] <tsdgeos> well it's not what i was told to do
[10:52] <tsdgeos> i was told, you search, have a scope, open it
[10:53] <mhr3> that was cause you didn't want to wait for openScope
[10:53] <mhr3> which it might and might not emit
[10:53] <mhr3> iirc
[10:54] <tsdgeos> what¿
[10:55] <tsdgeos> oh is openScope going to be any different anyway?
[10:55] <mhr3> i can understand why you don't want to wait for a signal
[10:56] <mhr3> oh, oh, we have the performQuery on the scope object now
[10:56] <mhr3> could you just call that after getScope() with the result uri?
[10:58] <tsdgeos> i can do whatever you want
[10:58] <tsdgeos> i have just done what i've been told to do
[10:59] <tsdgeos> and in the 99.05% i have been told anything i just improvised
[11:01] <mhr3> tsdgeos, are you ok with having ownership of the temp scope you get via getScope() ?
[11:02] <tsdgeos> i don't know what it means
[11:02] <tsdgeos> so no
[11:03] <mhr3> you'll own the instance
[11:03] <mhr3> you're responsible for destroying it
[11:03] <tsdgeos> that's not specified in getScope docu
[11:03] <tsdgeos> is it?
[11:04] <mhr3> no
[11:04] <tsdgeos> because i'm pretty sure we do getScope in other places
[11:04] <tsdgeos> and never destroy it
[11:04] <tsdgeos> why should we do it in this case?
[11:04] <mhr3> cause it used to give you only scopes that are in the model
[11:04] <mhr3> but now you want temp ones
[11:04] <facundobatista> Holas
[11:05] <mhr3> tsdgeos, or we introduce a new call for that
[11:10] <tsdgeos> mhr3: if you're going to make me use a new function, may as well use openScope
[11:11] <tsdgeos> mhr3: can you please detail exactly how i'm supose to interact with you
[11:11] <mhr3> i'm giving you options
[11:11] <mhr3> if openScope is fine with you, let's do that
[11:12] <tsdgeos> anything is fine with me, you just need to tell me what you're going to do
[11:12] <tsdgeos> obviously it's not going to work now
[11:12] <tsdgeos> so don't complain it doesn't work
[11:12] <tsdgeos> i did it so that it works for me
[11:12] <tsdgeos> but it doesn't work for you, ok, tell me what you want
[11:12] <mhr3> relax
[11:13] <tsdgeos> i'm relaxed
[11:13] <mhr3> i'm just trying to figure out what's the difference
[11:13] <mhr3> and we identified that
[11:13] <mhr3> so yey
[11:13] <tsdgeos> and i'm going to give you a hint, don't tell relax to people that aren't relaxed
[11:13] <tsdgeos> doesn't help
[11:15] <tsdgeos> i'm investigating the height thing
[11:18] <mhr3> tsdgeos, so from my pov if you just call scope.activate(result) i'd be happy, that will emit either gotoScope (for favourites) or openScope(for the rest), or neither if it's a wikipedia result or whatever
[11:18] <tsdgeos> that would have been useful before i started doing anything
[11:18] <tsdgeos> mhr3: in search? in all?
[11:19] <mhr3> everywhere
[11:19] <tsdgeos> i'm not going to call that in favorites
[11:19] <mhr3> fine
[11:19] <mhr3> that means we could even get rid of gotoScope perhaps.. yey
[11:20] <mhr3> although i don't know what's supposed to happen if you tap music from all
[11:20] <mhr3> open is as a temp scope?
[11:23] <tsdgeos> no
[11:23] <tsdgeos> i go back to dash
[11:23] <tsdgeos> i handle that
[11:24] <tsdgeos> i check if it's on the favorites model or not
[11:24] <tsdgeos> and then go to dash or not
[11:24] <tsdgeos> booooo for using functions in bindings
[11:24] <tsdgeos> they don't update when the variables used in the function but not in the function call change
[11:28] <mhr3> tsdgeos, so you'll check scopeId, and if !favourite, call .activate() which you'll expect to emit openScope?
[11:29] <tsdgeos> yes
[11:29] <tsdgeos> mhr3: from the scope that was returned by getScope("scopesOverview")
[11:29] <tsdgeos> yes?
[11:29] <mhr3> yep
[11:29] <tsdgeos> mhr3: and i have to call closeScope when i'm done
[11:29] <mhr3> correct
[11:30] <mhr3> and of course the opened scope can again emit openScope
[11:35] <tsdgeos> not going to work
[11:35] <tsdgeos> sorry
[11:36] <tsdgeos> that doesn't work right now either in the dash
[11:36] <tsdgeos> so i'm not going to fix it for this case
[11:36] <tsdgeos> height of the "All" should be fixed now
[11:36] <tsdgeos> it looks like it's wrongly calculated here at the moment since there's scopes without images that make it look empty
[11:38] <mhr3> i wonder why is that
[11:39] <tsdgeos> Error downloading https://dash.ubuntu.com/imgs/art/openlibrary-scope.jpg - server replied: Forbidden
[11:39] <tsdgeos> You don't have permission to access /imgs/art/openlibrary-scope.jpg on this server.
[11:39] <tsdgeos> is that firefox says
[11:39] <tsdgeos> someone should fix it
[11:40] <mhr3> facundobatista, ^
[11:40] <tsdgeos> mhr3: so getScope is going to return null for any non favorite scope, right?
[11:40] <tsdgeos> mhr3: can we document that?
[11:42] <tsdgeos> so that i make my fake plugin do the same
[11:42] <Saviq> biab, interview
[11:42] <facundobatista> mhr3, tsdgeos, checking...
[11:43] <tsdgeos> mhr3: tbh it is kind of weird, since we have the visible flag, so i would expect your "Scopes" to have all the Scope objects and set the visible flag accordingly
[11:44] <tsdgeos> and then getScope would work
[11:44] <tsdgeos> but ok, getScope() only works for visible scopes
[11:45] <mhr3> tsdgeos, tbh i'd rather get rid of the visible flag, it's not like it was useful for anything, you just filter the invisible ones anyway
[11:46] <mhr3> tsdgeos, while at it, can we make the overviewScope something really special?
[11:46] <tsdgeos> mhr3: it's useful in my backend where i have all the scope objects created and then getScope works just fine for all scopes
[11:46] <mhr3> as in Scopes.getOverviewScope()
[11:46] <tsdgeos> mhr3: if you prefer, sure
[11:47] <tsdgeos> mhr3: you're adding it to unity::shell::scopes::ScopesInterface then, no?
[11:47] <mhr3> tsdgeos, doesn't work that great when you have dozens of objects and they're not that cheap
[11:47] <tsdgeos> mhr3: actually it should be kind of a property
[11:47] <tsdgeos> not a getOverviewScope?
[11:47] <tsdgeos> or you prefer the getter?
[11:47] <tsdgeos> are you creating it when i call that?
[11:48] <tsdgeos> i mean it will always be non null when i call getOverviewScope?
[11:48] <mhr3> tsdgeos, property is fine
[11:48] <mhr3> yea, it could be null if things aren't initialized
[11:48] <tsdgeos> i don't know, what do you prefer?
[11:48] <tsdgeos> well if it can be null
[11:48] <tsdgeos> i am going to need a property
[11:49] <tsdgeos> can you please define the interface so i can copy it to my fake plugin?
[11:49] <mhr3> k
[11:50] <tsdgeos> going for lunch
[11:53] <greyback> Saviq: hey out of laziness I bumped the version number of unity8 with QtComp support to 8.0 - mzanetti not so sure about that. WDYT?
[12:15] <mhr3> tsdgeos, lp:~unity-team/unity-api/scopes-v3
[12:51] <tsdgeos> mhr3: waht's overlaycolor?
[12:57] <mhr3> tsdgeos, unrelated
[12:57] <tsdgeos> ok
[12:58] <mhr3> tsdgeos, btw the going back from search to surfacing was my bug
[13:06] <dandrader> greyback, should we pass a QT_NODEBUG or something when building qtmir packages to silence its log output?
[13:25] <tsdgeos> mhr3: pushed the activate+openScope thing
[13:25] <tsdgeos> mhr3: should your part be ready or not yet?
[13:26] <mhr3> tsdgeos, nope, need to override activate
[13:26] <tsdgeos> ok, tell me when its done
[13:26] <tsdgeos> +'
[13:31] <Saviq> \o/ Dell technician's here
[13:40] <mhr3> tsdgeos, btw anything you can do about the large result? it's white text on light background atm
[13:40] <mhr3> tsdgeos, when you for example search for wiki in the overview
[13:41] <tsdgeos> mhr3: not sure what you mean
[13:42] <tsdgeos> mhr3: screenshot?
[13:43] <tedg> Saviq, Which MR is the one that splits out the dash?
[13:43] <mhr3> wth.. my zeitgeist doesn't work
[13:43] <mhr3> tsdgeos, http://imgur.com/EdrRvZ3
[13:44] <tsdgeos> i guess i need to set some background so it's not white
[13:44] <tsdgeos> i'll see
[13:44] <tsdgeos> mhr3: is that happening if i update all branches and compile?
[13:44] <mhr3> yes
[13:45] <tsdgeos> ok
[13:46] <mhr3> tsdgeos, although maybe we need to update the scope, it's specifying the background color itself
[13:47] <greyback> dandrader: I think it's a good idea to keep the verbose logs printing, it'll help us tracking down bugs
[13:47] <mhr3> still white on white... eek
[13:48] <tsdgeos> confused
[13:49] <mhr3> the designs no longer show the card being white... otoh there's no real visual design, just wireframes
[13:49] <tsdgeos> well
[13:50] <tsdgeos> the  card is using scopeStyle.foreground as color for something i idenfity as background
[13:50] <tsdgeos> Saviq: you there?
[13:51] <Saviq> tsdgeos, wassup
[13:51] <tsdgeos> Saviq: look at summaryColorWithBackground in CardCreator
[13:51] <tsdgeos> Saviq: why is it using foreground?
[13:51] <tsdgeos> should it be background?
[13:51] <dandrader> paulliu, is it the design that the shutdown dialog stays behind the indicators panel and launcher?
[13:52] <Saviq> tsdgeos, hmm? that's the colour of text?
[13:52] <tsdgeos> Saviq: the color of the text is background?
[13:52] <tsdgeos> or you mean summaryColorWithBackground is the color of the text?
[13:53] <tsdgeos> ah right summaryColorWithBackground is the color of the text
[13:53] <Saviq> yes it is
[13:53] <tsdgeos> then why is that thing white
[13:53] <Saviq> tsdgeos, maybe because it takes card background into account
[13:53] <Saviq> or well, should at least
[13:54] <Saviq> greyback, re: version... we didn want 8.0 to be when it becomes unity
[13:54] <Saviq> greyback, i.e. we don't want to keep it being unity8
[13:54] <Saviq> greyback, but OTOH does one preclude the other...
[13:54] <tsdgeos> Saviq: ah right
[13:54] <tsdgeos> hmmmm
[13:54] <tsdgeos> so how do we fix that?
[13:55] <tsdgeos> Saviq: that = http://imgur.com/EdrRvZ3
[13:55] <greyback> Saviq: I'll just do as you prefer on this matter. I don't have a strong opinion really
[13:55] <Saviq> tsdgeos, ah that
[13:56] <Saviq> tsdgeos, StyleTool has light/dark colours
[13:56] <Saviq> tsdgeos, we need to take luminance of the background color
[13:57] <Saviq> tsdgeos, and based on styleTool.threshold you go for dark or white
[13:57] <Saviq> s/white/light/
[13:58] <tsdgeos> Saviq: in the cardcreator code
[13:58] <Saviq> tsdgeos, it has cardStyle
[13:59] <tsdgeos> scopeStyle
[13:59] <tsdgeos> yes
[13:59] <Saviq> tsdgeos, so summaryColorWithBackground needs to check the background color luminance (that should be ~happening already)
[13:59] <tsdgeos> ok, let's see if i can make that happen
[13:59] <Saviq> tsdgeos, and depending on scopeStyle.threshold use background or foreground
[13:59] <Saviq> or well
[13:59] <Saviq> light or dark
[14:00] <Saviq> but yeah, that's something I didn't do yet
[14:00] <Saviq> mzanetti, do you have a branch with split dash for tedg to use?
[14:03] <mzanetti> Saviq: no
[14:03] <mzanetti> Saviq: doesn't work for that yet as ApplicationManager doesn't pick it up yet
[14:11] <tedg> mzanetti, I'm not sure how to interpret that. Simple or complex?
[14:11] <mzanetti> tedg: well, what exactly do you want to do with it?
[14:11] <tedg> mzanetti, I want to overlay a trusted session prompt on it.
[14:11] <tedg> mzanetti, So I need the pid of it to pass to Mir.
[14:12] <mzanetti> tedg: hmm, I see. no, slightly to early for that...
[14:12] <mzanetti> tedg: when QtComp has landed (Monday or tuestday hopefully) we'll work full steam on that
[14:13] <mzanetti> tedg: will ping you as soon as I have a branch for you to play with
[14:13] <tedg> mzanetti, So, again, I have no understanding of what the difficulty is. So is that a couple days after thing or a week or two after thing?
[14:14] <mzanetti> tedg: ah, no, shouldn't be too hard I hope, greyback estimated 1 day to get it working
[14:14] <tedg> Okay, cool.
[14:14] <mzanetti> tedg: so definitely next week unless QtComp plays bad on us (not expected any more)
[14:15]  * greyback touches wood
[14:15] <mzanetti> heh :D
[14:31] <kgunn> seb128: hey, just getting our qtcomp ducks in a row....would you mind approving https://code.launchpad.net/~unity-team/ubuntu-system-settings/use-qtComp/+merge/225540
[14:41] <dednick> tube every day in 30 degree heat. yay!
[14:42] <tsdgeos> Saviq: so something like http://paste.ubuntu.com/7814714/ ?
[14:45] <tsdgeos> mhr3: so it's fixed with ↑
[14:45] <tsdgeos> mhr3: you need to run make again to pick up these changes
[15:01] <Saviq> \o/ /me got my umph back
[15:07] <tsdgeos> dandrader|afk: any idea why my EdgeDragArea oesn't work in tests?
[15:07] <tsdgeos> or anyone
[15:09] <MacSlow> could someone test-ping me here please?
[15:10] <tsdgeos> MacSlow: ping
[15:10] <MacSlow> tsdgeos, thx
[15:12] <MacSlow> tsdgeos, once more please...
[15:12] <tsdgeos> MacSlow: looooolo
[15:13] <MacSlow> tsdgeos, great...thx
[15:15] <Saviq> tsdgeos, are you using touchDrag?
[15:16] <tsdgeos> Saviq: touchFlick
[15:16] <tsdgeos> can't find anything like touchDrag
[15:17] <Saviq> tsdgeos, yeah, that's probably the same
[15:17] <Saviq> s/same/one/
[15:18] <tsdgeos> it''s moving the scope below the drag area :S
[15:18] <paulliu> dandrader: https://launchpadlibrarian.net/158819734/poweroff-buttons.png
[15:18] <paulliu> dandrader: should be in-front-of those.
[15:18] <tsdgeos> ok now
[15:18] <tsdgeos> don't know what i did but works now :D
[15:18] <Saviq> \o/
[15:20] <dandrader> tsdgeos, using mouse events instead of touch events?
[15:20] <tsdgeos> dandrader: that was at the begnning, they i moved to touch and still didn't work, but i may have had the coords wrong
[15:23] <dandrader> paulliu, so it's a bug, right?
[15:23] <paulliu> dandrader: yes.
[15:24] <dandrader> paulliu, does it happens with stock image? I was trying with qtcomp modifications on top
[15:25] <paulliu> dandrader: I'm not sure. How did you make it behind them?
[15:25] <paulliu> dandrader: If just pressing the power button, it should pop-up in the front of everything.
[15:25] <dandrader> paulliu, well, just long pressed the power button and then slid down the indicators panel from the top edge
[15:26] <paulliu> dandrader: Let me try. I didn't do that. Should be on stock image too.
[15:26] <dandrader> paulliu, ie, while the dialog is being shown I have full access to the top bar
[15:26] <dandrader> paulliu, and can also do a left-edge drag to slide in the launcher
[15:27] <paulliu> dandrader: yeah. It is a bug.
[15:27] <dandrader> paulliu, ok, will report it then
[15:31] <dandrader> paulliu, https://bugs.launchpad.net/unity8/+bug/1344082 (don't know your launchpad nick)
[15:35] <mhr3> tsdgeos, awesome
[15:36] <paulliu> dandrader: ok. I'll assign myself.
[16:25] <dandrader> dednick, fyi: just started reviewing https://code.launchpad.net/~nick-dedekind/unity8/mirCompositor-appMocks/+merge/227317
[16:26] <dednick> dandrader: cool. thanks
[16:47] <dpm_> pete-woods, I was looking at the vimeo scope and noticed the PageHeader.Logo setting in the .ini file. However, when I try to run my scope using that setting via unity-scope-tool, I'm getting:
[16:47] <dpm_> warning: ignoring unknown key PageHeader.Logo in group Appearance in file /home/dpm/dev/build-8tracks-scope-Desktop-Default/src/com.ubuntu.developer.dplanella.8tracks-scope_8tracks.ini
[16:47] <pete-woods> dpm: yes, the error is nonsense
[16:47] <pete-woods> dpm: ^
[16:47] <dpm_> but the thing is that the logo does not load
[16:48] <pete-woods> dpm_: I think you need to provide an absolute path to the logo
[16:48] <pete-woods> but your stuff is click-packaged, right?
[16:50]  * pete-woods is asking what is supposed to happen here
[16:51] <dpm_> pete-woods, it will be click-packaged, it's just that it's not in a working state to be packaged yet. Right now I'm just getting the scope to run at all, using Qt Creator and unity-scope-tool
[16:52] <dpm_> so I set up the .ini file and I was puzzled by the error. Let me try to hardcode the path for testing purposes...
[16:52] <pete-woods> dpm_: I'm just checking whether you're allowed to pass a relative path (as that's what you need if you're a click auther)
[16:52] <pete-woods> *author
[16:52] <pete-woods> dpm_: yes, the error message is annoying and misleading
[16:52] <dpm_> I'm just using PageHeader.Logo =<EMAIL_ADDRESS>atm
[16:53] <pete-woods> dpm_: what does that resolve to in your binary directory?
[16:53] <pete-woods> it might be looking in the real /usr/lib/ARCH/unity-scopes/SCOPE_NAME/…
[16:53] <pete-woods> (and maybe there's nothing there)
[16:53] <dpm_> pete-woods, it's a relative path, right now using a non-click target, it's /8tracks-blue.png
[16:54] <pete-woods> dpm_: sounds like you don't have SCOPE_INSTALL_DIR set as a cmake variable when configuring the *.ini.in file
[16:55] <dpm_> pete-woods, yeah, I'll have to look into that. In any case, hardcoding the path shows me the logo
[16:56] <pete-woods> dpm_: okay, cool, will get back to you when I know about relative path support
[16:56] <pete-woods> (which is what you actually need as a click author)
[16:57] <dpm_> ok, thanks
[17:02] <pete-woods> dpm_: okay, so relative paths aren't supported yet, and we're having a big argument about it :p
[17:03] <dpm_> oh :)
[17:04] <pete-woods> it'll get fixed, though, as we're apparently already aware of it
[17:04]  * dednick EOD. later suckers.
[17:05] <dpm_> ok, thanks pete-woods
[17:20] <josharenson> enabling qt compositor leaves me hanging at the "Google" screen after a reboot??
[17:26] <dandrader> josharenson, should not :)
[17:27] <dandrader> josharenson, flashed my N4 and enabled qtcomp on it this morning and it just worked
[17:28] <josharenson> dandrader, its been happening since yesterday.... i install all dependencies to run tests, and then install qt comp via right-edge ppa, and my nex7 hangs on the "Google" screen
[17:28] <josharenson> I can still access adb shell, but I cannot even boot into the boot loader
[17:28] <dandrader> josharenson, aaahhh... right-edge ppa is "old news"
[17:28] <josharenson> of course
[17:29] <josharenson> what should I be using
[17:29] <josharenson> ?
[17:29] <dandrader> josharenson, follow these instructions now: https://wiki.ubuntu.com/Unity8/QtComp
[17:29] <dandrader> josharenson, we are using another ppa now
[17:29] <josharenson> dandrader, thanks a bunch... this has been a bit frustrating
[17:29] <josharenson> even when I purge the ppa, only a reflash brings the device back it seems
[17:29] <dandrader> josharenson, I've faced this very problem when returning from vacations last Monday :D
[17:29] <josharenson> haha ok
[17:30] <josharenson> oh this webpage is great
[17:30] <dandrader> josharenson, I don't thrust ppa purges
[17:30] <josharenson> lol ok
[17:30] <dandrader> kudos to kgunn on that
[17:30] <dandrader> (the webpage)
[17:31] <josharenson> thanks kgunn
[17:31] <kgunn> josharenson: ppa-purge won't quite work on this particular pkg set i think
[17:31] <kgunn> since we've not seeded qtmir
[17:31] <josharenson> kgunn, know of a way to undo without a lengthy reflash?
[17:32] <kgunn> josharenson: i honestly hadn't even tested ppa-purge....but i suppose you might be able to apt-get remove qtmir-android, then try ppa-purge ?
[17:33] <kgunn> again...its an i _think_ that ppa-purge won't work...
[17:33] <josharenson> kgunn, yeah I would concur
[17:33] <kgunn> i think i did try it, but i noticed i could still close apps with swipe up in spread
[17:33] <kgunn> meaning, it failed
[17:33] <kgunn> altho...i think it was really late at night....
[17:33] <kgunn> tired head
[17:34] <josharenson> kgunn, alright I'll try that... reflash isn't bad once its downloaded as a last resort... but something is wrong with Comcast right now and I'm getting ~200k down at best
[17:34] <kgunn> oooff
[17:37] <mhr3> Saviq, hm, looking at the header-link branch, the diff grew significantly, anything wrong there?
[17:37] <Saviq> mhr3, yeah, LP
[17:37] <mhr3> sigh
[17:37] <mhr3> think i'll have to deal with that on monday
[17:37] <mhr3> have a nice weekend!
[18:13] <cyrildz_> Hi all , I have some questions concerning the soundmenu
[18:13] <cyrildz_>  I have implemented for my App the mpris2 specs , I can see the interfaces present on the session Bus through qdbusviewer. But I can't see my App listed in the soundmenu. what should I add in my code to have it shown in the soundmenu?   As a test, I also did a notification  class to send notifactions through Dbus and it works
[18:23] <Saviq> cyrildz_, it might be better for you to send an email to ubuntu-devel mailing list
[18:23] <Saviq> cyrildz_, it's late on a Friday, so most devs are already having their weekend
[19:11] <josharenson> Window geometry broken w/ qt comp?
[19:12] <josharenson> AP tests don't run fullscreen even when forced
[19:35] <greyback> josharenson: apps say if they want fullscreen or not. It's working in QtComp, as panel (bar at top) goes away for video app or gallery
[19:35] <greyback> josharenson: what AP test are you running?
[20:15] <cwayne> hm, why is there no scope department for the store?
[20:24] <josharenson> greyback, any of them... it looks like some parts use the whole screen, but the wallpaper and panel are only ~25%
[20:25] <greyback> josharenson: I've no idea what you're seeing. Can you share a photo?
[20:31] <josharenson> greyback sure 1 min
[20:34] <josharenson> greyback
[20:34] <josharenson> https://drive.google.com/file/d/0B_oQNe1U0rhqcEpkYzRyay1pSXc/edit?usp=sharing
[20:35] <josharenson> you can see the search icon in the black area on the far right
[20:35] <josharenson> greyback, this was taken mid swipe
[20:36] <greyback> josharenson: how did you run unity8?
[20:37] <josharenson> greyback, AP launched it via "launch_unity()"... I think it just executes the binary with window geometry params specified
[20:37] <greyback> josharenson: that's an N7 right?
[20:37] <greyback> josharenson: unity8 overrides the window geometry requested by the app
[20:38] <greyback> unity8 should be fullscreen
[20:38] <greyback> I've not tested AP on N7, I'd better give it a go then
[20:38] <josharenson> greyback, it is nex7
[20:40] <greyback> sorry but I gotta run
[20:41] <josharenson> np


[12:28] <mup> PR snapd#13365 closed: tests: fix snap-run test for fedora <Simple 😃> <Created by ZeyadYasser> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/13365>
[18:25] <mup> PR snapcraft#4453 closed: fix(metadata): add f-string to debug message <Created by mr-cal> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/4453>


[00:00] <chrisccoulson> ah, ok, that might be more difficult to do then. i think flashplugin just uses wget
[00:08] <geser> it should be different than using wget as long as it prints just to stdout and doesn't do any fancy stuff (like a ncurses interface or such)
[00:10] <geser> the questioning should be better done with debconf and only the result of it passed directly to the updater to not break non-interactive updates
[00:16] <c_korn> I also want to use this script as normal application
[00:16] <c_korn> so the user can update the game data with it
[00:45] <c_korn> hm, can't I just execute the updater in xterm or something
[00:45] <c_korn> I can expect that X is installed, can't I?
[01:08] <jjardon> Hello, I'm not sure this is the correct channel to ask but: I'm editing https://wiki.ubuntu.com/Halsectomy Can I add gnome-pilot to the table ?
[01:52] <drdr> Hello?
[01:53] <drdr> is anyone here?
[01:53] <hyperair> !give drdr ask
[01:54] <hyperair> oops
[01:54] <hyperair> !ask | drdr
[01:54] <drdr> Anyone know when firefox 3.5 will be pushed as a update to the netbook spin?
[01:57] <hyperair> fta: ^^
[04:46] <stochastic> Is the Library General Public License forward compatible with the Lesser General Public License?
[04:53] <lifeless> stochastic: same thing
[05:12] <binarymutant> I keep getting debian-changelog-file-is-a-symlink from lintian, I've deleted the changelog and created a new one but it still didn't get rid of the warning :/
[05:13] <ScottK> binarymutant: This is almost certainly OK.
[05:13] <binarymutant> cool ty ScottK :D
[05:14] <ScottK> If it's a multi-binary package and the package depends on the one that ships the symlink it's OK.
[05:14] <jtimberman> any MOTU able to look at stompserver, merb and chef on REVU?
[05:15] <binarymutant> ScottK, awesome, it is multi-binary
[06:39] <dholbach> good morning
[06:43] <fabrice_sp> Good morning Daniel :-)
[06:44] <binarymutant> can reportbug work with debian's bts too?
[06:44] <fabrice_sp> binarymutant, yes: reportbug --bts=debian
[06:44] <dholbach> hey fabrice_sp!
[06:44] <binarymutant> fabrice_sp, ty :D
[06:49] <fabrice_sp> dholbach, what do you mean with "if you fix this for Karmic, I'm happy to ACK it" in bug #416262. Should I upload a new version in Debian with the translations and re-ask for the sync? Or do you mean having the po files in a temporary way in debian directory?
[06:49] <dholbach> just a sec
[06:50] <dholbach> it'd be nice to have translations back and investigate where they went
[06:50]  * RoAkSoAx off to bed, bye all
[06:53] <fabrice_sp> dholbach, upstream lost them. I can upload them again to the upstream repository (I have 'upstream' powers for aptoncd :-) ), and update debian then
[06:53] <dholbach> fabrice_sp: that'd be sweet!
[06:53] <fabrice_sp> here we go then :-) Thanks
[07:11] <iulian> Hello dholbach.
[07:12] <dholbach> hey iulian!
[07:24] <stochastic> Would a kind motu with a spare second or two be able to REVU http://revu.ubuntuwire.com/p/xjadeo
[07:35] <stochastic> This package has received two advocations http://revu.ubuntuwire.com/p/a2jmidid but they were on separate uploads, do I need them on the same upload for it to get pushed through?
[07:37] <stochastic> ^^ james_w I think you may need to re-advocate if that's what's stopping it.
[07:53] <jtimberman> stochastic: yes, you need to get a second advocate.
[07:58] <stochastic> don't you mean third ;)
[08:00] <jtimberman> stochastic: only if james_w is unavailable to advocate, i suppose.
[08:20] <lamalex> does anyone here know about python distutls?
[08:20] <lamalex> mine keeps installing to /usr/local/local
[08:20] <lamalex> cannot for the life of me figure out why
[09:03] <DktrKranz> lamalex: pass --install-layout=deb to setup.py install call
[09:14] <AnAnt> Hello, how usable is wine1.2 ?
[09:17] <james_w> stochastic: stefanlsd uploaded
[09:20] <stochastic> james_w, okay, I just haven't seen it appear here yet: https://launchpad.net/ubuntu/+source/a2jmidid and it was still listed in the new packages page on revu
[09:21] <james_w> it's in the NEW queue
[09:22] <stochastic> I don't follow. Maybe I'm still too NEW
[09:23] <directhex> stochastic, new source packages go into the NEW queue for approval by an archive admin
[09:23] <directhex> stochastic, then new binary packages go back into NEW
[09:24] <stochastic> okay, and where does feature freeze play on this? will that package be accepted?
[09:26] <james_w> yeah
[09:26] <james_w> unless it is rejected, in which case you may have to ask motu-release nicely to allow you to upload after Feature Freeze
[09:27] <stochastic> okay. thanks for the clarification.
[09:31] <stochastic> bdrung_, if you have a second, I've re-uploaded (with all earlier discussed changes) xjadeo to revu.  But I can't for the life of me figure out how to get rid of the executable-not-ELF-or-script lintian warning.
[09:45] <directhex> stochastic, i'm not seeing it
[09:45] <directhex> qjadeo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjadeo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjinfo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjremote: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:46] <stochastic> directhex my lintian reports ./usr/share/qjadeo/locale/qjadeo_fr.qm to be the culprit
[09:47] <stochastic> but as I browse through the source tree I can't find any place where the qjadeo_fr file becomes executable
[09:47] <directhex> hm, it IS executable isn't it
[09:48] <stochastic> directhex, it's probably from either the makefile or the debian/rules file (the debian folder is shipped from upstream so I didn't write debian/rules from scratch)
[10:17] <jussi01> dholbach: good morning. got time for a quick pm?
[10:18] <dholbach> jussi01: yep
[11:35] <\sh> siretart: pingeling you got the mail from mrfai?
[11:46] <siretart> \sh: yes, I did
[11:46] <\sh> siretart: would you like to review my comment...and eventually make a comment, too? :)
[11:56] <bdrung_> stochastic: why do you run "test -f configure || ./autogen.sh" in the clean target?
[12:00] <hyperair> i would guess that it's to autogen so that configure exists inside the source package, which is not a good idea
[12:03] <bdrung_> that's why i asked. clean is for cleaning, not for creating :)
[12:32] <sistpoty|work> any DD around, who could sponsor me an upgrade of min12xxw (preferred from svn - svn://svn.debian.org/svn/collab-maint/ext-maint/min12xxw/trunk/)?
[13:15] <slytherin> james_w: there? need to discuss something abuot cobertura package that you rejected last week.
[13:15] <james_w> hi
[13:17] <slytherin> james_w: Even after remocing the DTDs in xhtml folder there are still some DTDs etc/dtds/coverage*.dtd which do not have license header. Is that acceptable?
[13:17] <james_w> possibly
[13:18] <james_w> were they written for this project?
[13:18] <slytherin> juli_: Can you please answer james_w's question?
[13:21] <juli_> james_w, I think so but I didn't check it with authors
[13:30] <james_w> it that's the case then it moves them to a slightly (un)clearer license state
[13:35] <juli_> james_w, I'll contact them. But what about the package? I need it for the rest netbeans staff
[13:35] <ghostcube> packaging request.. would it be possible to package 64 bit packages for lighnting and enigmail working on TB3 :)
[13:35] <james_w> juli_: I can't say without looking really
[13:36] <james_w> I expect that it would be ok, but can't be sure
[13:36] <james_w> I suggest you upload again
[13:36] <juli_> james_w, ok, thank you.
[13:37] <slytherin> ghostcube: Is such a version available i.e. the one which works with TB3?
[13:37] <ghostcube> yes
[13:37] <juli_> slytherin, could you, please upload again. I will see what can I do about coverage*.dtd in the meantime
[13:37] <slytherin> juli_: Ok. Let me test build it.
[13:37] <juli_> slytherin, ok. Thank you
[13:38] <slytherin> ghostcube: but there is no TB3 in repository. Why would anyone want to package an extension for it?
[13:39] <ghostcube> there is an ppa daily i havent known there is no universe package oO
[13:40] <ghostcube> havent searched i thought with ff3.5 there was tb3 too
[13:40] <slytherin> ghostcube: TB3 has not been released yet.
[13:40] <ghostcube> oh ok ..
[13:41] <ghostcube> btw its a must have :D
[13:55] <james_w> jtimberman: hey, does merb need the embedded gems?
[14:03] <slytherin> juli_: uploaded cobertura. it is now at the mercy of archive admins. :-)
[14:04] <juli_> slytherin, thanks! I'm writing a letter to cobertura developers about the license)
[14:08] <jtimberman> james_w: what gem is embedded??
[14:09] <james_w> gem?
[14:09] <james_w> there's about 20 of them :-)
[14:09] <jtimberman> james_w: oh, stuff in the specs?
[14:09] <james_w> one second
[14:10] <james_w> ./merb-core/spec/public/core_ext/fixtures/gems/gems/
[14:10] <james_w> ./merb-core/spec10/public/webrat/test_app/gems/gems/
[14:13] <jtimberman> james_w: its not included in the resulting package.
[14:13] <james_w> still
[14:14] <jtimberman> it was fine for debian, merb was uploaded to NEW.
[14:15] <jtimberman> but i was told that it probably wouldn't get into an archive in time to make karmic feature freeze, hence packaging for universe as well.
[14:16] <jtimberman> and it wasn't a blocking issue in earlier reviews.
[14:21] <slytherin> jtimberman: 'NEW' is not equal to 'ACCEPTED'. :-)
[14:23] <james_w> sorry, plumber arrived
[14:26] <jtimberman> slytherin: sure, and Debian ruby packaging also does not include the source package.
[14:27] <james_w> jtimberman: at the least not all the gems are covered by the same license as the main code, and that is not documented in debian/copyright
[14:31] <jtimberman> james_w: so you want me to repackage the source tarball?
[14:32] <james_w> I think so, though I've no idea what they are there for
[14:35] <jtimberman> they're there for doing spec tests on the source.
[14:36] <directhex> even if things aren't in the final package, their distributability needs to be certain for them to be on the ubuntu archive
[14:37] <jtimberman> Perhaps this is why Debian doesn't include the original source tarball in the packaging.
[14:43] <james_w> juli_: those files look very much like they are written for the project, so would be covered by the dominant license. Therefore I have accepted the package. Clarifying the situation with upstream would still be appreciated.
[14:44] <jtimberman> where should removal of the source gems be mentioned?
[14:47] <jtimberman> james_w: should i note those were removed in README.source, or README.Debian ?
[14:47] <james_w> see debian policy
[14:47] <james_w> it's debian/copyright
[14:47] <james_w> and README.source I guess
[14:47] <james_w> plus the version number should change
[14:52] <Daviey> Does anyone know of an example package that generates debian/*.install etc files at source build time?
[14:53] <Laney> Surely you'd just call install manually instead?
[14:56] <jtimberman> james_w: http://paste.ubuntu.com/258692/ adding that to README.source, with the gems dirs removed, that good?
[14:57] <james_w> probably
[14:57] <james_w> I didn't review the whole package
[14:57] <james_w> you need to document it in debian/copyright as well, and change the version number as I said
[14:58] <jtimberman> as in a new dch entry, or modify the ubuntu version, 1ubuntu1
[14:58] <james_w> the upstream version number
[14:58] <james_w> so that it is clear the tarball has changed
[14:59] <jtimberman> i dont know what you mean
[15:00] <jtimberman> as in bump from merb-1.0.12 to merb-1.0.13 or something?
[15:01] <jtimberman> i don't think upstream isn't going to remove those gems from the source tarball, they're included on purpose for the spec tests.
[15:08] <james_w> jtimberman: no, merb-1.0.12+dfsg
[15:08] <james_w> so that it is clear that it is a modified tarball, and not the one that upstream calls 1.0.12
[15:09] <jtimberman> james_w: do i just change the name of the orig.tar.gz, or update the changelog?
[15:09] <james_w> both
[15:10] <jtimberman> ok
[15:11] <jtimberman> in changelog,  merb (1.0.12+dfsg-0ubuntu1) ?
[15:14] <james_w> yep
[15:18] <jtimberman> uploaded to revu.
[15:18] <juli_> james_w, thank you! I wrote a message to cobertura-devel. I hope they clarify the situation.
[15:18] <james_w> thanks juli_
[15:22] <bddebian> Heya gang
[15:22] <sistpoty|work> hi bddebian
[15:23] <bddebian> Heya sistpoty|work
[16:02] <juli_> james_w, cobertura developer said coverage* files are under W3C license (the same: http://changelogs.ubuntu.com/changelogs/pool/main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.1-5ubuntu1/w3c-dtd-xhtml.copyright). They will add these info for next release. Should I update copyright file now and reupload?
[16:03] <james_w> yes please
[16:03] <james_w> if they can make that explicit in the headers of their next release that would be great as well
[16:04] <james_w> I'd be happy to sponsor that change
[16:04] <juli_> james_w, thank you:) I'll update copyright and upload an updated version to REVU
[16:05] <james_w> just a debdiff would do
[16:05] <james_w> or even a diff for that file and proposed changelog entry :-)
[16:06] <juli_> should I create a bug in LP?
[16:06] <juli_> I suppose yes:) I'll do this today
[16:08] <james_w> no need really
[16:08] <james_w> if you just pass the changes to me I can sponsor straight away
[16:08] <james_w> a bug is fine though
[16:09] <jtimberman> james_w: can you take another look at merb please? i uploaded w/ new orig.tar.gz
[16:12] <james_w> sorry, I've got to do something else today
[16:12] <james_w> I've already spent most of my day on archive-admin stuff
[16:14] <james_w> jtimberman: you uploaded to REVU?
[16:14] <jtimberman> james_w: i did
[16:14] <james_w> I can upload that to NEW for you
[16:15] <jtimberman> james_w: :-D
[16:15] <james_w> link please?
[16:15] <jtimberman> http://revu.ubuntuwire.com/details.py?upid=6771
[16:15] <jtimberman> or, http://revu.ubuntuwire.com/p/merb
[16:47] <lamalex> DktrKranz: my distutils doesn't appear to have that option
[16:57] <juli_> james_w, I created a bug and attache diff files for copyright and changelog there: https://bugs.launchpad.net/ubuntu/+source/cobertura/+bug/418181
[17:16] <DktrKranz> lamalex: sounds strange, which release are you running?
[17:16] <lamalex> DktrKranz: jaunty
[17:16] <jtimberman> james_w: I also fixed blocking issue with license in stompserver, which had 2 advocates: http://revu.ubuntuwire.com/p/stompserver
[17:16] <lamalex> er
[17:16] <lamalex> karmic
[17:18] <lamalex> DktrKranz: i think part of the problem is that I dont understand distutils at all
[17:19] <DktrKranz> lamalex: so it should definitely support it. how do you call setup.py?
[17:20] <lamalex> DktrKranz: sudo python setup.py --instal-layout=deb install
[17:21] <DktrKranz> it should be "sudo python setup.py install --install-layout=deb"
[17:22] <lamalex> DktrKranz: do I pass the same flag for bdist?
[17:23] <DktrKranz> --install-layout is common for install only
[17:24] <lamalex> hmm how do I generate the correctly layed out tar.gz
[17:24] <lamalex> ah, it's dsist
[17:24] <lamalex> s/dsist/sdist
[17:32] <POX_> DktrKranz: ?! NEVER SUGGEST TO "sudo pytohn setup.py install" or ez_instal something!!! I will break other parts of the system
[17:33] <POX_> if someone wants to test something, he should use some kind of sandbox (like virtualenv)
[18:19] <slytherin> fabrice_sp: ping
[18:22] <fabrice_sp> slytherin, pong
[18:22] <jtimberman> Chef just needs one more advocate, who wants to be the lucky MOTU? :-D http://revu.ubuntuwire.com/p/chef
[18:22] <slytherin> fabrice_sp: do you plan to file sync request for doxia and doxia-site-tools?
[18:23] <fabrice_sp> slytherin, not yet. I was planning to get them built, for the moment
[18:25] <slytherin> fabrice_sp: Ok. I am updating my pbuilder. It will take me an hour to get doxia built. If you are done before that then please let me know.
[18:27] <fabrice_sp> slytherin, I can go with doxia-site-tools first
[18:28] <slytherin> it has build-dep on libdoxia-java
[18:29] <fabrice_sp> oh
[18:47] <fabrice_sp> slytherin, doxia build depends on plexus-containers and plexus-containers needs the latest version of libgoogle...
[18:48] <slytherin> so where are you stuck at?
[18:48] <fabrice_sp> compiling plexus-containers, without libgoogle
[18:50] <fabrice_sp> have to go. bbl
[18:50] <highvoltage> plexus-containers sound like something from star trek
[19:05] <fabrice_sp> back
[19:05] <fabrice_sp> highvoltage, it's almost as complex as the Enterprise :-)
[19:07] <highvoltage> fabrice_sp: :)
[19:07] <slytherin> fabrice_sp: so libgoogle is one of those few libraries which will need to be modified to have complete maven stack right?
[19:08] <fabrice_sp> slytherin, yes: it's also blocking the 'plugin' path
[19:08] <fabrice_sp> maven-plugin-tools-java
[19:08] <slytherin> fabrice_sp: have you discussed this already with ttx by any chance?
[19:09] <fabrice_sp> yes, and it's a no go :-/
[19:09] <fabrice_sp> ttx is more of the opinion to let maven and plexus as-is
[19:09] <slytherin> Then he is probably using google-* libraries as build dep for some other work.
[19:13] <fabrice_sp> I didn't specifically spoke about libgoogle, but his last email is more this way (do not touch non plexus lib)
[19:18] <slytherin> fabrice_sp: reply to that mail and add details about the libraries that 'must' be modified. Let's see what he says.
[19:18] <jtimberman> kirkland: thanks for your comments on Chef :)
[19:19] <mathiaz> jtimberman: debian-changelog-file-is-a-symlink - I've seen that one often - but I have no clue how to fix these
[19:19] <kirkland> jtimberman: sure, i just advocated
[19:19] <mathiaz> kirkland: ^^
[19:19] <kirkland> mathiaz: hmm, i've never seen that one before
[19:19] <kirkland> mathiaz: let me have a look
[19:19] <mathiaz> kirkland: it seems to be something from cdbs
[19:19] <fabrice_sp> slytherin, ok. As I will be on holidays beginning tomorrow, I won't be able to follow up on that until post-FFE.
[19:20] <slytherin> ok
[19:20] <kirkland> mathiaz: fwiw, i did advocate, packaging looks good
[19:20] <geser> it's one of Ubuntu's cdbs features to symlink identical files
[19:20] <kirkland> ah, space savings
[19:20] <slytherin> It does not need fixing
[19:20] <mathiaz> geser: that makes lintian unhappy
[19:20] <jtimberman> kirkland: thanks!
[19:20] <kirkland> mathiaz: i don't use cdbs very much, which is why i haven't seen it
[19:20] <slytherin> It is warning, not error.
[19:20] <jtimberman> there's an element of danger in using magic.
[19:21] <jtimberman> :)
[19:22] <mathiaz> slytherin: https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews#Tips says Package should be lintian clean
[19:22] <mathiaz> slytherin: lintian clean means error free or warning free?
[19:22] <mathiaz> kirkland: do you look for lintian warnings as an AA?
[19:23] <kirkland> mathiaz: yes, but warnings are not necessarily blockers
[19:23] <jtimberman> kirkland: you're an AA?
[19:23] <slytherin> Ideally it means free from errors as well as warnings. But in this case lintian is not updated to ignore a warning caused by a feature.
[19:23] <mathiaz> kirkland: lintian errors are though?
[19:23] <kirkland> mathiaz: bonus points for lintian overrides (with inline comments as to why they may be safely ignored)
[19:24] <kirkland> mathiaz: yeah, i generally require lintian overrides (with comments) for lintian errors
[19:24] <kirkland> mathiaz: where comments provide an acceptable explanation
[19:24] <kirkland> jtimberman: y
[19:24] <jtimberman> kirkland: mathiaz got me to put that in for chef-server ;)
[19:24] <jtimberman> as you probably saw.
[19:24] <kirkland> jtimberman: right
[19:25] <kirkland> mathiaz: honestly, most of my AA work is ensuring that debian/copyrights is comprehensive and correct
[19:26] <mathiaz> kirkland: right - are you also looking at the debian/ directory in general (as an AA)?
[19:26] <kirkland> mathiaz: and mostly trusting that the uploading/advocating MOTUs did a good job with the packaging checks
[19:26] <kirkland> mathiaz: only lightly; see my last statement ^
[19:26] <kirkland> mathiaz: so i did the REVU with MOTU hat on, not AA hat
[19:26] <mathiaz> kirkland: ok :)
[19:27] <kirkland> mathiaz: as for debian/copyrights, I read/digest that
[19:27] <mathiaz> kirkland: and you MOTU hat covers more things than your AA hat?
[19:27] <kirkland> mathiaz: i consider my MOTU hat to cover packaging technical details
[19:28] <jtimberman> kirkland, mathiaz and it was a good reminder to discuss the lintian override, now we have an upstream ticket to use system-provided jquery if it exists.
[19:28] <kirkland> mathiaz: which any MOTU, I think, should be able to cover
[19:28] <kirkland> mathiaz: and as an AA, we put a lot of trust in MOTUs
[19:29] <kirkland> mathiaz: for stuff like package syncs, we have to "trust" that the MOTU ack'ing the package sync has done a good job reviewing "why" the diffs can be dropped from the package
[19:29] <kirkland> mathiaz: because we might have to process a hundred of those per day, and can't look at every one of those
[19:30]  * mathiaz nods
[19:30] <kirkland> mathiaz: if a MOTU ack'd that, it's on him/her ;-)
[19:30] <kirkland> mathiaz: as for the licensing ...
[19:30] <kirkland> mathiaz: run "licensecheck -r ." from the package source tree
[19:30] <kirkland> mathiaz: i see chef is Apache license
[19:31] <kirkland> mathiaz: so I'll start with "licensecheck -r . | grep -v Apache"
[19:31] <kirkland> mathiaz: looking for anything licensed differently
[19:31] <mathiaz> kirkland: right - what do you do about Unknown - no copyright files?
[19:31] <kirkland> mathiaz: for instance, maybe some GPL code slipped into here
[19:32] <kirkland> mathiaz: i try to make sure those are clearly covered otherwise
[19:32] <jtimberman> kirkland: such as with the debian/copyright mentioning those filepaths
[19:32] <kirkland> mathiaz: and when possible, I ask upstream to ensure that they have proper copyrights in their files, and provide them the list of files missing copyright/license headers
[19:33] <kirkland> mathiaz: usually projects are willing/able to get that into a future release
[19:33] <kirkland> jtimberman: right; sometimes it's a matter of a whole section (subdir) being licensed/copyrighted and mentioning that in debian/copyrights
[19:35] <jtimberman> kirkland: gotcha. ran into a bit of that with merb earlier today. merb's spec tests include some gems, and some of those are available as packages but the upstream isn't going to worry about which platform they're on for testing.
[19:35] <jtimberman> so they can't rely on say libfoo-ruby is installed to do a test.
[20:19] <sistpoty> superm1: would you like to act as motu-release delegate for mythbuntu again, or do you have someone else you'd like to recommend for the position?
[20:20] <superm1> sistpoty, yeah should be able to.  i sponsor everything within our small team anyway :)
[20:20] <sistpoty> excellent, thanks superm1
[20:24] <lamalex> does anyone know what happens when there's a name conflict between packages from different sources?
[20:24] <sistpoty> fta: would you like to act as motu-release delegate for the mozilla team this feature freeze again (together with asac, if he agrees)?
[20:25] <ScottK> lamalex: If the two don't do the same thing, one has to be renamed.
[20:25] <sistpoty> lamalex: it's not coinstallable? (and you'd need to declare conflicts: otherpackage in both)
[20:25] <lamalex> sistpoty: they dont conflict
[20:26] <lamalex> ScottK: but what /happens/. does apt just pick on arbitrarily to be used?
[20:26] <ScottK> sistpoty: conflicts are only appropriate if they are alternative implementations of the same functionality.
[20:26] <fta> sistpoty, sure
[20:26] <ScottK> lamalex: First one installed wins.
[20:26] <ScottK> Second one will get an install failure.
[20:26] <lamalex> ScottK: and before installation?
[20:26] <ScottK> That's why one needs to be renamed.
[20:26] <sebner> ScottK: the one with higher versionsnumber wins xD
[20:27] <ScottK> sebner: Nope.
[20:27] <lamalex> aptitutde search package
[20:27] <lamalex> who gets shown
[20:27] <lamalex> both?
[20:27] <sebner> ScottK: why not?
[20:27] <sistpoty> thanks fta
[20:27] <ScottK> Ah.
[20:27] <ScottK> I was talking about file name conflicts, not package names.
[20:27] <ScottK> Sorry.
[20:27] <ScottK> sebner is likely correct.
[20:27] <sebner> np
[20:27] <sistpoty> he, /me is well
[20:27]  * sebner ^5 sistpoty
[20:28] <ScottK> lamalex: Only the binary with the higher version number will exist in the archive.
[20:30] <sistpoty> luisbg: up for ubuntustudio delegation for motu-release for karmic again together with _MMA_?
[20:31] <luisbg> sistpoty, yes
[20:31] <lamalex> ScottK: thanks
[20:31] <sistpoty> luisbg: excellent, thanks. can you also ask _MMA_ if he agrees?
[20:31] <luisbg> sistpoty, will do and will let you know
[20:31] <sistpoty> thanks a lot luisbg
[20:31] <luisbg> he is a little bit hard to contact now but still possible :)
[20:31] <sistpoty> heh
[21:17] <xnox> burnout. is when you answer to a user-request wine on a devel list and get tangled into a support thread.
[21:18] <xnox> Modern Support: http://xkcd.com/627/
[21:18] <jpds> No, I don't do that.
[21:21] <sistpoty> luisbg: btw.: read the mail about the request for audacity standing FFe? (https://lists.ubuntu.com/archives/ubuntu-motu/2009-August/006079.html) / I also cross-replied to ubuntu-studio-devel
[21:59] <ghostcube> fta, ping
[22:01] <fta> ghostcube, no contentless ping please
[22:01] <ghostcube> fta, ping http://bugzilla.songbirdnest.com/show_bug.cgi?id=17683 :)
[22:01] <ghostcube> sorry
[22:03] <binarymutant> does anyone use reportbug with gmail? It didn't send the mail for me :/
[22:03] <fta> ghostcube, no idea
[22:04] <ghostcube> i think it is an songbird bug or a missing lib maybe
[22:11] <ghostcube> fta, got it the problem is somehow a mising german loalisation
[22:11] <ghostcube> *c
[22:38] <stochastic> bdrung_ I've lost that last command you suggested I run, can you repost?
[22:39] <bdrung_> stochastic: run debuild twice
[22:40] <bdrung_> stochastic: and you will see, that the second run failes, because the clean target do not remove all generated files. you have to remove them in the clean target with "rm -f file1 file2" or "rm -rf dir1 dir2"
[22:41] <xnox> james_w: You are ubuntu top contributor ;-)
[22:41] <james_w> it's a lie!
[22:41] <xnox> https://edge.launchpad.net/debian/+topcontributors
[22:41]  * xnox lol
[22:42] <xnox> When people start using Distributed Development will Karma even out?
[22:42] <ScottK> That's Debian, not Ubuntu.
[22:42] <james_w> don't take karma as a proxy for worth :-)
[22:42] <bdrung_> stochastic: and why do you run "test -f configure || ./autogen.sh"?
[22:42] <bdrung_> in the clean target?
[22:43] <james_w> xnox: somewhat, though it may take some time
[22:43] <stochastic> bdrung_, I don't know why that's there, I inherited the debian packaging from upstream and am cleaning it up
[22:43] <xnox> james_w: I'm just jealous =) I was evaluating my chances for UniverseContributor and tried to weight my Ubuntu Karma to find this bob =)
[22:43] <xnox> s/bob/bomb
[22:43] <james_w> xnox: LP might subtract a large lump off me or something, as it's not at all fair
[22:43] <james_w> heh
[22:43] <bdrung_> stochastic: then remove this line
[22:44] <xnox> at least you now probably feel like poker tournament winner with a huge stake =)
[22:46] <xnox> james_w: anyhow by submitting Karmic recipes for daily-debs I was hoping to get nightly bzr for Karmic.... Will you update cron-jobs or however jw+dailydebs works
[22:47] <james_w> ah, Dmitrijs!
[22:47] <james_w> thanks
[22:47] <james_w> I'll do that now, thanks for the reminder
[22:47] <bdrung_> if you remove the 190000 from the bazaar branches of james_w, there will be only 451 karma points left
[22:48] <stochastic> bdrung_ I think the removal of xjadeo.desktop isn't happening, but that sill doesn't fix the elf binary warning...
[22:48] <xnox> james_w: your welcome =) scratching my itch really I've just moved to karmic and I can't live without my daily treats
[22:49] <james_w> feel free to send me any more packages you want added
[22:49] <james_w> well within reason ;-)
[22:49] <bdrung_> there must be something wrong with the karma points. i am listed as "top contributer", too. really strange.
[22:49] <xnox> james_w: I kind of trying to run my own as well ~crosswire-daily for my Debian/Ubuntu Packaging team of Crosswire stuff.
[22:50] <james_w> nice
[22:50] <james_w> what's crosswire?
[22:50] <bdrung_> stochastic: it complains about xjadeo-0.4.7/src/qt-gui/qjadeo_fr.qm
[22:51] <bdrung_> stochastic: you should remove this file on clean
[22:51] <xnox> james_w: I didn't know before I've signed up =) It's bible study library & front-ends + actual texts of hundreds of bibles/commentries etc.
[22:52] <xnox> a long the lines of making Ubuntu interesting without the internetz
[22:52] <james_w> ah, ok
[22:53] <SiDi> Hello. Is this a good place to look for someone who would accept to maintain the ubuntu package of an upstream project ?
[22:53] <bdrung_> xnox: if you need a helping hand for packaging Xiphos, feel free to contact me.
[22:53] <xnox> james_w: really didn't know how to get involved with Ubuntu/Debian and there was a team being formed in January so I joined =) Resurected from horrible QA state 2 packages in Debian and Ubuntu =)
[22:54] <xnox> bdrung_: I'm proud maintainer of Xiphos =) Hope it's in good shape in Karmic now
[22:54] <xnox> bdrung_: can you sponsor a fix though? I've forgot a "Provides:" in the latest version in Ubuntu
[22:55] <SiDi> (the package in question is exaile, which losts its maintainer for ubuntu)
[22:55] <xnox> bdrung_: lp:~dmitrij.ledkov/ubuntu/karmic/xiphos/fix-upgrades
[22:55] <bdrung_> xnox: not yet, in 3 day is my motu application :)
[22:56] <xnox> Aha =) well I wish you good luck
[22:56] <xnox> I'm noone yet. And I'm thinking whether I can make it into Contributors
[22:57] <bdrung_> xnox: being a contributor is the first step (you become ubuntu member and gain a nice email address)
[22:58] <bdrung_> xnox: i found a bug in your debian package :)
[22:58] <xnox> bdrung_: I'm listening =)
[22:58] <bdrung_> xnox: it's a native package
[22:58] <bdrung_> but it shouldn't be native
[23:00]  * xnox checking
[23:01] <xnox> bdrung_: how is 3.1.1-1 in Debian or the proposed fix 3.1.1-1ubuntu1 native?
[23:01]  * xnox is confused
[23:01] <bdrung_> the package in debian sid
[23:01] <bdrung_> 3.1.1-1
[23:03] <xnox> You are right! How did that happen
[23:04]  * xnox need to bash Debian Sponsor for mingling with my package!!!
[23:05] <bdrung_> it was the sponsors fault?
[23:05] <stochastic> bdrung_, I've added qjadeo_fr.qm to the files removed in clean, but lintian still gives me the elf-binary error
[23:06] <bdrung_> stochastic: that are different issues :)
[23:06] <xnox> bdrung_: thanks a lot =)
[23:06] <bdrung_> xnox: np
[23:06] <bdrung_> xnox: i will have a look at the package. let me see if i find more issues ;)
[23:08] <xnox> bdrung_: the previous DD who maintained it had tarball inside tarball so it was all native to him
[23:08] <xnox> And now I'm out-of sync with and the checksums will be different
[23:08] <xnox> crap
[23:08] <bdrung_> stochastic: the convert and install command should be moved to the install target (you see the correlation?)
[23:09] <bdrung_> xnox: tarballs inside tarballs are ugly
[23:10] <bdrung_> stochastic: after all the install command you could put a chmod 644 command for the qjadeo_fr.qm file
[23:10] <bdrung_> stochastic: the "$(MAKE) distclean" command should come before the "rm" commands
[23:11] <stochastic> bdrung_, so the binary-indep: build install target should be empty?
[23:11] <bdrung_> stochastic: yes
[23:11] <bdrung_> stochastic: i don't know why you have a "rm -f" command in the binary-indep target
[23:13] <stochastic> bdrung_, I believe it's because the convert command creates a temporary copy of those files, then it's copied to the right place, then the temporary files are removed
[23:13] <bdrung_> ok
[23:14] <bdrung_> stochastic: the convert command _could_ put the resulting files directly into the right place.
[23:14] <stochastic> bdrung_, yes that would seem cleaner
[23:14] <bdrung_> stochastic: after running debuild twice, run "zcat ../xjadeo_0.4.7-0ubuntu1.diff.gz |diffstat" and you will see that there are some files not cleaned
[23:15] <stochastic> bdrung_ I don't understand what you mean by "run debuild twice"  I've run it many times
[23:17] <bdrung_> stochastic: run debuild twice means, that you run it at least two times.
[23:17] <bdrung_> the diffstat command list all files in the diff file. in the diff file should only be the files of the debian/ directory
[23:20] <bdrung_> stochastic: http://paste.ubuntu.com/258969/ this fixes the copyright lintian warning
[23:21] <stochastic> I thought you mentioned we could safely ignore that warning
[23:22]  * stochastic changes it anyway
[23:22] <stochastic> the zcat |diffstat command only returns files in the debian directory for me
[23:22] <mzz> (if you don't mind me asking: is there an easy way to get lintian to *always* warn on changes outside of debian/, not only if it detects a patch system, which iirc is its default behavior?)
[23:23] <bdrung_> stochastic: ok, maybe i need your updates
[23:23] <stochastic> bdrung_, uploading to revu right now
[23:24] <stochastic> oops, forgot to debuild after that copyright file change
[23:24] <bdrung_> mzz: don't know. i normally use the zcat diff.gz | diffstat command
[23:24] <stochastic> next upload will include the copyright file changes
[23:24] <bdrung_> mzz: if you want everthing from lintian, run "lintian -iIE --pedantic ..."
[23:24] <mzz> bdrung_: sure, and that's a good habit anyway, I guess (since it'll also warn you about oddities inside debian/)
[23:25] <mzz> the diffstat, that is :) I haven't tried lintian in full pedantic mode yet...
[23:25] <bdrung_> mzz: some pedantic warnings are usefull
[23:26]  * mzz is beginning to get the hang of things, has managed to create a ppa with a few basic packages, might figure out how to get those in either debian or ubuntu proper in the future
[23:27] <bdrung_> mzz: new ones?
[23:27] <mzz> mostly backports
[23:27] <mzz> well, backports or fairly trivial version bumps
[23:29] <bdrung_> ok
[23:29] <mzz> so far my experience has been that it's not exactly hard, but that there are a great many layers of tools calling each other, with multiple choices on some of the layers, and I don't understand all the layers yet.
[23:30] <bdrung_> mzz: i know the feeling.
[23:30] <bdrung_> it will go away some day :)
[23:30] <mzz> (things like python-support versus python-central, pbuilder versus sbuild versus probably other things I haven't encountered yet, but also on a user level apt-get vs aptitude vs synaptic, which don't seem to be using exactly the same "marks" database)
[23:30] <stochastic> bdrung_, I get no lintian warnings on that latest upload.  Do you see any issues left?
[23:31] <bdrung_> stochastic: is the upload already on http://revu.ubuntuwire.com/p/xjadeo
[23:31]  * mzz shall stop distracting you now :)
[23:31] <bdrung_> the last upload date is 23:48
[23:32] <bdrung_> mzz: no problem. i am doing more thing parallel.
[23:32] <stochastic> bdrung_, oh, looks like that upload was rejected
[23:32] <mzz> this is generally the case on irc :)
[23:33] <bdrung_> mzz: yes.
[23:35] <bdrung_> stochastic: the revu page seams to be not up to date
[23:37] <bdrung_> mzz: it's good to have a choice, but on the beginning it could be confusing. sometimes you use more than one of them (e.g. i use apt-get and synaptic)
[23:38] <stochastic> bdrung_, okay revu is up to date now
[23:42] <bdrung_> stochastic: the second run of debuild failed. the patch could not applied. "1 out of 1 hunk FAILED -- saving rejects to file src/qt-gui/qjadeo.cpp.rej"
[23:43] <stochastic> bdrung_ how are you getting these errors?
[23:44] <stochastic> what options are you running debuild with?
[23:44] <stochastic> is it in a pbuilder environment?
[23:45] <bdrung_> stochastic: run this: http://paste.ubuntu.com/258979/
[23:46] <bdrung_> stochastic: no, you cannot reproduce it with pbuilder, because pbuilder do not rely on the clean target
[23:48] <stochastic> bdrung_, but for that I need to manually install the build deps?
[23:49] <bdrung_> stochastic: yes
[23:49] <stochastic> ugh, is there any way to do that without clogging my system up?
[23:51] <bdrung_> stochastic: setting up a virtual machine :)
[23:51] <xnox> stochastic: after playing around with a lot of pacakges a removed all -dev packages and then did an autoremove =)
[23:52] <xnox> "Developers spring cleaning"
[23:52] <bdrung_> xnox: i clean them once in a half year with reinstalling the current release. ;)
[23:52] <xnox> bdrung_: Ahh that's what you call install party =)
[23:52] <bdrung_> xnox: yes
[23:53] <bdrung_> xnox: but sometimes i install in between
[23:53] <bdrung_> last time was when i bought an ssd.
[23:53] <xnox> =) me too I've just upgraded to karmic alpha
[23:53] <bdrung_> the complete installation needs less than 10 minutes
[23:54] <bdrung_> karmic is on my previous hdd and in a vm
[23:54] <xnox> what about / etc?
[23:54] <xnox> and /var/cache/
[23:54] <stochastic> bdrung_, my apt-get doesn't want to install any of the last four dependencies because of broken sub dependencies, but pbuilder finds these just fine
[23:55] <stochastic> bdrung_ could you just pastebin the diffstat so I can see the result of the debuilds?
[23:55] <bdrung_> stochastic: strange
[23:56] <bdrung_> stochastic: http://paste.ubuntu.com/258982/
[23:57] <bdrung_> xnox: for /etc i have some scripts / patches that are making the required changes
[23:57] <bdrung_> xnox: but /var/cache?
[23:57] <xnox> ok /var/cache/pbuilder
[23:58] <xnox> and /var/cache/apt-cacher-ng
[23:58] <xnox> ~30 GB
[23:58] <bdrung_> xnox: i rebuilt them. that is not the problem. (i have mirrored jaunty and karmic with apt-mirror)
[23:58] <xnox> how much does that take space?
[23:58] <bdrung_> i have one pc without internet access
[23:59] <bdrung_> 44,8 GiB
[23:59] <xnox> ok not that bad
[23:59] <bdrung_> one distribution would use 22 - 25 GiB


[01:04] <Madpilot> mdke: ping
[01:05] <Madpilot> mdke: new GPG key is at Launchpad & on the keyservers, so if you could talk to elmo or whoever about commit-rights, that'd be cool. thanks.
[01:18] <theCore> LaserJock, I'm up again!
[01:20] <LaserJock> great!
[03:13] <lambert> If someone references a trademark name on the wiki, (is windows trademarked?) does the trademark need to be noted?
[03:16] <Kyral> lambert: Like?
[03:17] <Kyral> lambert: you can say "Windows" without the TM
[03:18] <lambert> kyral: If someone said "users of the windows operating system might find this next hint ...."
[03:18] <Kyral> oh yah thats fine
[03:19] <lambert> any situation where a trademark would be needed?
[03:19] <Kyral> uhh
[03:19] <lambert> just curious
[03:19] <Kyral> IANAL
[03:20] <Kyral> I Am Not A Laywer
[03:21] <theCore_> I wouldn't bother too much about the Windows trademark
[05:04] <LaserJock> theCore: so are you able to work on the packaging guide now that you've got a new hard drive?
[05:05] <theCore> i'm working on it
[05:06] <theCore> I'm doing an intro about the various skills you need to do packaging
[05:07] <LaserJock> oh cool, what section would it go in?
[05:07] <theCore> Getting Started ?
[05:09] <LaserJock> sounds good, what kind of skills are you thinking of?
[05:10] <theCore> make, autoconf ( the very basic ), diff, patch, etc...
[05:10] <theCore> apt
[05:13] <jsgotangco> :D
[05:13] <crimsun> I'd advocate autoconf being in the more advanced section
[05:13] <crimsun> make, diff, and patch-- yes
[05:14] <LaserJock> theCore: hmm, we need to be careful not to attempt too much so that we can't get it done for Dapper or overwhelm the reader before the even get started with the packaging
[05:15] <crimsun> right, that's why I think autoconf belongs in a more advanced setion
[05:15] <crimsun> section^
[05:15] <theCore> LaserJock, I just made some really quick intros with some references
[05:16] <theCore> crimsun, I just talked about how to make and use configure script
[05:16] <LaserJock> sounds good, I think a reference with a quick example would be good
[05:16] <LaserJock> it is easy to want to explain "everything" about packaging but that would really include way too much material.
[05:17] <LaserJock> also keep in mind that there will be an Ubuntu Developer's Reference for dapper too
[05:17] <LaserJock> so we want to keep the guide style
[05:18] <LaserJock> theCore: but I think it is a good idea, send me the patches when you have a chance
[05:18] <theCore> np
[05:22] <LaserJock> crimsun: have you had a chance to take a look at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html ?
[05:23] <crimsun> LaserJock: yeah, I have; I'll send some patches later
[05:31] <LaserJock> crimsun: very cool, thank you so much
[05:44] <theCore> I must go, cya later
[05:45] <theCore> LaserJock, I will send you the patch tomorrow
[10:22] <kagou> hi
[10:26] <kagou> i'm searching how translation process is working ...
[10:31] <dsas> kagou: I don't think the docs are ready to be translated yet
[10:32] <dsas> kagou: Presuming you did mean translating the ubuntu documentation?
[10:32] <kagou> ok dsas, yes , ubuntu-documentation
[10:32] <kagou> the job is done with rosetta ?
[10:33] <dsas> kagou: Yeah, that's the usual way of doing it for ubuntu
[10:34] <dsas> kagou: I think some of the docs will be ready soon.
[10:35] <jsgotangco> not yet but mdke already created POT files for it
[10:36] <kagou> is there specific mailing/list or chan for french translator?! i'v just found  #ubuntu-translators
[10:36] <Madpilot> kagou: there's also #ubuntu-fr, you might ask there
[10:37] <kagou> nothing in this chan Madpilot just users needing help
[10:38] <kagou> i'm waiting for seb128
[10:38] <dsas> kagou: There's two mailing lists, I guess https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr-l10n is the translation team one.
[10:39] <kagou> great !
[10:40] <dsas> kagou: I'd guess https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr is user help but in French
[10:40] <kagou> yes dsas
[12:03] <mdke> morning
[12:06] <jsgotangco> hi mdke
[12:06] <jsgotangco> :)
[12:08] <mdke> hiya
[12:10] <jsgotangco> these language bugs....are we still responsible for these?
[12:10] <mdke> yes we are
[12:10] <mdke> but I will close them as wontfix soon
[12:10] <jsgotangco> yeah ok
[12:10] <mdke> because I certainly don't think they are important enough to justify an upload to breezy-changes
[12:10] <jsgotangco> beacuse i have no idea what to do with these
[12:10] <jsgotangco> no they're trivial
[12:10] <mdke> yep. the docs in those languages still work
[12:11] <jsgotangco> i'll just have dinner first and let's talk about stuff more
[12:11] <mdke> okay, i should be around for a bit later
[12:11] <jsgotangco> no problem its only 7pm here anyways
[03:52] <mdke> do you guys think that we should have an entry in the desktopguide about using nautilus as root
[03:52] <mdke> ?
[03:52] <mdke> I can't really think of many good reasons
[03:52] <jsgotangco> yuck
[03:52] <jsgotangco> yeah
[03:54] <mdke> ok, taken out
[03:54] <mdke> jsgotangco, did you have any time to look at that tips and tricks patch I sent to the mailing list?
[03:55] <jsgotangco> yeah
[03:56] <siretart> mdke: around?
[03:56] <siretart> could anyone please look at bug #30563
[03:56] <siretart> https://launchpad.net/distros/ubuntu/+source/ubuntu-docs/+bug/30563
[03:57] <mdke> ok
[03:57] <mdke> oh bloody hell
[03:57] <jsgotangco> we've seen this in a lot of translated docs
[03:57] <mdke> that's the third dup in a week
[03:57] <siretart> I'm deploying ubuntu/breezy in an internet cafe (upgrade from sarge) and I get these very annoying errors
[03:57] <jsgotangco> yeah
[03:58] <mdke> siretart, how annoying?
[03:58] <siretart> oh. sorry if this is a dup, but I didn't find others
[03:58] <mdke> if you think it's worth another upload to breezy-updates, we can fix it
[03:58] <siretart> mdke: well, our admin mailing list is spammed with these messages
[03:58] <siretart> mdke: it looks to me like the xml files are faulty, and they don't look like they are very hard to fix
[03:59] <mdke> no they are easy to fix
[03:59] <mdke> but we'd need to upload to breezy-updates
[03:59] <siretart> mdke: now I have 2 options: roll my own ubuntu-docs package for local use, or fix it in ubuntu
[03:59] <siretart> mdke: thats no problem
[03:59] <jsgotangco> it seems only translated docs are affectede
[03:59] <mdke> alright, I'll fix it, and talk to Kamion about an upload
[03:59] <siretart> as long as the patch is sufficiently short
[04:00] <siretart> mdke: do you prepare uploads and need just a sponsor?
[04:00] <mdke> yep
[04:00] <siretart> mdke: or does kamion does the 'packaging'?
[04:00] <mdke> i'll do it
[04:00] <siretart> mdke: I can sponsor you as well
[04:01] <siretart> if kamion is not around. kamion has to review it, touhg ;)
[04:01] <mdke> no problem, but I'll talk to Kamion/mdz about the upload because they need to confirm it
[04:01] <siretart> tough
[04:01] <siretart> yes
[04:01] <mdke> siretart, ok, I'll ping you when I'm done
[04:01] <siretart> mdke: could you please give me your corrected package so that I can install it locally (for testing and until the official package hits the mirrors)
[04:01] <mdke> sure, and you can upload it too :D
[04:02] <siretart> ok. thank you very much
[04:03] <mdke> np
[04:15] <mdke> jsgotangco, did you have any time to look at that tips and tricks patch I sent to the mailing list?
[04:16] <jsgotangco> mdke, yeah
[04:16] <mdke> any thoughts?
[04:16] <jsgotangco> but i dont understand a thing about qanda sets
[04:16] <jsgotangco> you want me to apply it to my WC?
[04:16] <mdke> jsgotangco, open it in yelp, and see which of the sections in the tips and tricks chapter looks better
[04:16] <jsgotangco> ok hold on
[04:17] <jsgotangco> goodbye.quanda.diff?
[04:18] <lambert> Is there a way to number headers on the wiki so they don't duplicate in the TOC?
[04:19] <mdke> lambert, can you give us an example?
[04:20] <lambert> https://wiki.ubuntu.com/WirelessTroubleshootingGuide
[04:20] <lambert> from personal experience, I like and think it's easier in headers
[04:21] <lambert> to also be numbered as font difference isn't that drastic to separate
[04:21] <lambert> areas
[04:21] <lambert> just makes it an easier read
[04:22] <mdke> oh i see what you mean
[04:22] <jsgotangco> mdke, this looks better
[04:22] <mdke> no, there is no way to do that, afaik. Best to leave the numbers of the headings I think
[04:22] <mdke> jsgotangco, the first of the three sections looks better?
[04:23] <jsgotangco> instead of QA you made it to a numbered list
[04:24] <jsgotangco> this is cleaner
[04:24] <mdke> yay
[04:24] <jsgotangco> +1
[04:26] <jsgotangco> are you committing this?
[04:27] <mdke> i will, after a few more people give feedback
[04:27] <mdke> tbh, I've already done the rest of the chapter like that and done quick a few modifications of tips
[04:40] <mdke> siretart, have a look at http://doc.ubuntu.com/debs/breezy-updates/ for me?
[04:41] <mdke> and anyone else who fancies testing it
[04:42] <jsgotangco> you created a new package?
[04:42] <mdke> i fixed that bug, i hope
[04:45] <mdke> siretart, works here. I think you can upload it and we'll bug Kamion/mdz tomorrow
[04:46] <siretart> mdke: will look at it shortly. I'm having here unexpected dpkg errors, which I want to investigate first
[04:46] <mdke> argh, with that package?
[04:46] <mdke> surely not
[04:46] <siretart> with dpkg itself. it spits me an assertion error
[04:47] <mdke> ok
[04:47] <jsgotangco> works for me too
[04:48] <siretart> but diffs looks good. will install that package here
[04:48] <mdke> yep, then run your cronjob
[04:54] <siretart> it's not really a cronjob. we are using cfengine(cfexecd) here ;)
[04:54] <mdke> well run "sudo scrollkeeper-rebuilddb -q" or whatever it is
[05:03] <jsgotangco> mdke, i've added you as lp doc admin
[05:03] <mdke> ok, thanks.
[05:03] <jsgotangco> we're not worthy!
[05:04] <siretart> wah, because of status NEEDINFO, bugs do not show in the bugs overview of a package
[05:04] <siretart> *sigh*
[05:04] <mdke> siretart, or in searches *wink*
[05:15] <siretart> mdke: ok, your package works for me. thanks a lot
[05:15] <mdke> siretart, good, will you upload it?
[05:16] <siretart> will do shortly
[05:38] <siretart> mdke: I assume these issues are already fixed in dapper, no?
[05:43] <siretart> mdke: your changelog does not mention the removal of generic/faqguide/ro/faqguide-ro.omf
[05:43] <siretart> mdke: I'm not sure if mdz or Kamion will approve this, unless you talk to then in advance
[06:08] <mdke> siretart, I'll talk to them
[06:08] <mdke> siretart, as for dapper, we don't have any translations there yet
[06:16] <siretart> ok
[06:29] <mdke> siretart, did you upload already? I've sent them an email
[06:34] <siretart> mdke: ah, so its okay to upload. ok, will do so now
[06:34] <mdke> siretart, thanks
[06:42] <siretart> mdke: besides, why did you remove that file?
[06:43] <mdke> siretart, because it was empty, and scrollkeeper didn't like that
[06:44] <siretart> ah, okay
[06:44] <siretart> allright then
[06:45] <mdke> there is a bug in rosetta which prevents us from using romanian translations, unfortunately
[06:45] <mdke> that's why the file was empty
[07:12] <siretart> mdke: thats an pretty awful bit upload. this is my third try :/
[07:13] <siretart> s/bit/big/
[07:14] <mdke> siretart, yeah, the source package is offensively large. Sorry about that
[07:23] <siretart> mdke: my upload has been rejected
[07:24] <mdke> siretart, damn. no doubt because I didn't sign it
[07:25] <mdke> are you able to sign it?
[07:25] <mdke> i did the package on a computer without a gpg key
[07:31] <mdke> afk for a while
[08:01] <mdke> siretart, any luck?
[08:02] <siretart> mdke: no, my upload gets rejected
[08:02] <siretart> mdke: obviously I may not upload to breezy-updates any longer
[08:02] <mdke> siretart, oh, you think it isn't because I didn't sign the package?
[08:02] <siretart> mdke: but since it is sunday today, I wait until tomorrow and but #launchpad about that
[08:02] <siretart> mdke: certainly I signed my package
[08:03] <siretart> but it got rejected
[08:03] <mdke> ah, you signed it. Ok, np
[08:03] <mdke> i'll just highlight Colin again and let him know
[08:04] <siretart> yes, that would be best I think
[08:05] <mdke> siretart, ok thanks for your help. Good luck with uploading tomorrow
[08:05] <siretart> thanks :)
[08:05] <siretart> mdke: I installed your package in my local repo here, works nice
[08:05] <siretart> mdke: thanks for the package
[08:05] <mdke> np
[09:33] <mdke> heya Madpilot
[09:45] <Madpilot> hi mdke - can't stay, but thanks for the commit email - sorry for the trouble...
[09:46] <Madpilot> later, all


[00:46] <Guest83662> I'm trying to run ubuntu on android (arm based) device using chroot.. while it sounds simple and "should work out of the box" it looks like we have issues with apt-get update not bein able to resolve hosts.  I'm stuck with the following errors: [00:46] <Guest83662>  this may not be an ARM architecture issue per se but people complaining with this issue seem to face this only on Android (ARM based devices)
[00:47] <Guest83662>  Please help.. If this is not the right platform for the question, please point to the right one. I must highlight, the device has access to internet verified via wget and curl. I have asked these details here: https://askubuntu.com/questions/910865/apt-get-update-fails-on-chroot-ubuntu-16-04-on-android the device seems to have full internet acces (with dns resolution and all)
[00:47] <Guest83662> somehow only apt-* programs seem to suffer from this problem.
[00:47] <Guest83662>  Apparently, I am not alone: https://askubuntu.com/questions/820814/chroot-networking-doesnt-work-for-apt-get?rq=1 I have also tried with replacing the server names in sources.list with their IP addrs and I get a different error .... sudo apt-get update gives me another error: Could not create a socket for <IP_ADDRESS> (f=2 t=1 p=6) - socket (13: Permission denied)