stlsaintHello all,00:23
stlsaintI am looking for the file that sets the default applications within unity bar00:23
stlsaintFile that i can set the default apps for a livecd and all users00:24
stlsaintwell alright00:36
stlsaintam i able to ask on mailing list? Launchpad states one must be a team member to subscribe00:37
stlsaintguess im in wrong channel00:37
=== trijntje_ is now known as trijntje
sil2100didrocks: hi!08:05
didrockshey sil210008:06
sil2100didrocks: would you mind if we did an unity video lens and scope SRU in the nearest time?08:06
didrockssil2100: no, I would love that08:07
didrockssil2100: does it fix the top errors on errors.ubuntu.com?08:07
sil2100Excellent, since David fixed the two top errors from that indeed08:07
didrocksah great ;)08:08
sil2100didrocks: is the merger using quantal also for the 5.0 branch of unity?08:59
didrockssil2100: no, see my email ;) I told precise09:00
didrocksit should at least09:00
sil2100https://jenkins.qa.ubuntu.com/job/automerge-unity/862/console <- we got this last night09:00
sil2100didrocks: this looks identical to the things that we were getting on quantal before one of my fixes for 4.709:01
sil2100didrocks: yep, it's using quantal09:02
sil2100didrocks: Get:1 http://archive.ubuntu.com quantal Release.gpg [198 B]09:02
didrocksI: extracting base tarball [/var/cache/pbuilder/quantal-amd64-base.tgz]09:02
didrocksyou're right09:02
didrockshum, looking in a minute09:02
sil2100didrocks: thanks09:02
didrockssil2100: do you have the MR handy?09:10
didrocksgot it meanwhile, but thanks :)09:11
didrockssil2100: ok fixed09:21
didrockssil2100: that was stupid me09:21
sil2100didrocks: yaaay, thanks \o/09:21
didrocksyw :)09:22
sil2100didrocks: btw. since I think I forgot this one, but on the sprint you mentioned you have a tool for generating changelog entries automagically09:24
didrockssil2100: lp:unify09:25
sil2100didrocks: is there some documentation on how to use unify?09:34
didrockssil2100: no, that's why I took time to explain the options the other day :)09:34
sil2100didrocks: I think I was busy with the releases and other things... ;) Ok, I'll browse through what others wrote down09:35
didrocksok :)09:35
popeydidrocks, i think you mostly went through the source code you didnt show it running or how you invoke it09:38
didrockspopey: yep, I couldn't run it otherwise it would have change status on bugs ;) I showed options on --help and which options to use for which case :)09:39
didrocksso yeah, how to invoke it was covered I guess09:39
didrocksbut if you have any question, do not hesitate09:41
popeyperhaps some detail of how you actually run it?09:42
popeyas in, how didrocks runs it09:42
didrockspopey: well, need more info, unify has 3 modes as I explained, sync bugs status09:43
didrocksrelease for getting changelog09:43
didrocksand creating the designify view we explored09:43
didrocksso need to be more specific :)09:44
sil2100didrocks: I was actually interested in the release part - with creating the changelog ;)09:44
didrockspopey: also, remember that there is still the question of how you would like to handle the super task09:44
didrocksas it's still heavily relying on "one unity super task"09:44
didrockssil2100: quite easy, see --help: unify -R unity09:44
didrocksif you want to release the current version09:44
didrocksand that the target dates for current version and next version suits the timing09:45
didrocksif you want to release a particular milestone target:09:45
didrocksunify -R unity -m <milestone_to_release> -n <next_milestone_to_report_all_unclosed_bugs>09:45
didrocksbeware that the changelog collects all components09:46
didrocksso it assumes that you are releasing compiz/unity/nux/bamf/deeā€¦09:46
didrocks(all bugs attached with a unity master task in this milestone)09:46
didrocksand it's doing stuff when you the command, so don't try if you are not sure of releasing :)09:46
sil2100ACK ;)09:48
popeynice one, thanks09:49
popeynext time, I'm video recording everything09:49
didrocksheh ;)09:50
sil2100That was what I proposed even ;)09:50
* sil2100 sighs10:11
seb128sil2100, there is no exit there ;-)10:20
seb128sil2100, popey: how is the unity SRU going? do you have an eta for upload?10:35
sil2100didrocks: I noticed that for unity-lens-video you released the previous version 0.3.5-0ubuntu2 for quantal, and for precise-updates you created the 0.3.5-0ubuntu1.1 version instead10:36
seb128sil2100, popey: if you have your candidate version in a ppa or something let me know, I'm interested in testing it ;-)10:36
didrockssil2100: yep, indeed10:36
sil2100didrocks: so for the new SRU release of the lens, should I do the same? i.e. 0.3.5-0ubuntu1.2 for precise and 3 for quantal ;)?10:36
sil2100seb128: from what I know, we prioritized unity 6.0.0 for quantal first, so we're in the middle of testing that10:37
sil2100seb128: besides that, there will be an SRU for dee and unity-video lens/scope10:37
didrockssil2100: exactly!10:38
sil2100didrocks: thanks :)10:38
seb128sil2100, dee and the video lens,scope seem easy, would be good to start with those and get them uploaded today?10:38
sil2100seb128: yep - not sure about dee, since the thing confuses be a bit (still waiting for didrocks to check the precise issue) - but unity lens/scope for today is a safe bet10:39
sil2100seb128: I'm working on the lens now10:39
seb128sil2100, excellent, thank you10:39
mhr3it doesn't make much sense to sru dee if pygi with py3 doesn't work in P10:41
sil2100mhr3: that needs to be checked10:42
mhr3unless you SRU pygi as well :)10:43
sil2100mhr3: don't push me... ;)10:45
mhr3sil2100, you know it's the right thing to do ;)10:46
popeymhr3, have you seen the size of sil2100's sword!? :S10:50
mhr3uh oh, i forgot about that10:50
mhr3sil2100, well, i guess it'd be fine if pygi waited :)10:51
sil2100seb128: but we're also testing a pre-6.0.0 version of unity for quantal if you're interested10:57
seb128sil2100, I'm still running precise (I'm on the LTS .1 team) but thanks10:57
popeyseb128, hey, there's this thing called dual-boot :p11:00
seb128popey, dual boot is for wimps ;-)11:00
sil2100popey: I'd like to run precise now as well btw. ;)11:01
seb128it's a pain to change between versions and installed software11:01
seb128popey, I've a netbook I use for testing though, I might just run quantal on that one, that's a more practical solution than dual booting ;-)11:02
popeyyeah, I agree11:02
popeyI have two machines. there's no perfect solution really11:02
seb128I do the multi machine thing11:02
seb128I recommend having a cheap netbook for testing out of your main work station, makes testing easier without having to close everything and reboot11:04
seb128you can even dual boot the test machine then :p11:04
=== MacSlow is now known as MacSlow|lunch
sil2100seb128: I've uploaded the lens and scope to my PPA for testing: ppa:sil2100/ppa11:42
sil2100seb128: they didn't get built yet, but I suspect it to happen soon11:43
sil2100seb128: the fixed bugs are noted in the respective changelogs11:43
sil2100didrocks: can you ACK some nominations for me?11:55
ubot5Ubuntu bug 972304 in unity-scope-video-remote (Ubuntu) "unity-scope-video-remote crashed with GError in on_activate_uri(): Failed to execute child process "/usr/bin/gvfs-open" (No such file or directory)" [Medium,Fix committed]11:55
ubot5Ubuntu bug 977158 in Unity Videos Lens "unity video lens always re-thumbnails" [Undecided,New]11:56
=== davmor2_ is now known as davmor2
didrockssil2100: done, why are there some upstream bugs where it's invalidated?12:04
sil2100didrocks: what do you mean?12:06
=== MacSlow|lunch is now known as MacSlow
didrockssil2100: on one bug, the upstream task is invalid12:18
sil2100I'll fix that12:20
=== yofel_ is now known as yofel
=== _salem is now known as salem_
sil2100seb128: me and popey are testing the lenses/scopes SRUs right now, but the bugs are prepared for SRUs already13:01
seb128sil2100, great, I will test your ppa in a bit13:01
sil2100seb128: same for packaging branches for precise-propose13:01
sil2100seb128: remember to only pull those two packages from that PPA, since it's full of other packages too13:01
seb128sil2100, yeah, don't worry about that ;-)13:01
sil2100seb128: you want the precise packaging branches too?13:02
sil2100(if anything)13:02
sil2100seb128: we can't reproduce the bugs, seem fixed - and no regressions visible, so it's green from our tests13:13
seb128sil2100, same here13:13
seb128sil2100, the depends change is obvious, the other changes look right and I see to regression13:13
seb128go go go, upload ;-)13:13
sil2100hmm... can I upload to precise-proposed at all? ;p13:14
seb128sil2100, I don't think you can, I can sponsor you if you want ... let me check with didrocks first though in case he wanted to do it13:15
seb128didrocks, do you want to do the video lens,scope sponsoring or should I do it? I'm still on precise and testing them so I can upload if you want13:15
seb128didrocks, I will check the bugs, etc before uploading13:15
sil2100Ah, sponsoring!13:15
sil2100The only thing needed is switching from UNRELEASED to precise-proposed in the changelogs13:16
didrocksseb128: upload them if you want13:16
didrockssil2100: do you have put on a google doc the tests results?13:16
seb128didrocks, your call, I'm happy to do it if that helps but I don't want to steal stuff you planned to do either13:16
didrocksseb128: well, if you checked the packaging and that they followed the merge process and so on, I'm fine :)13:17
didrocksalso ensure that we have a gdocs with the tests results13:17
didrocksas it's mandatory to have something more formal than IRC13:17
seb128didrocks, ok13:17
sil2100didrocks: I'm creating one now13:17
didrocksthanks sil2100, seb12813:18
didrocksbut before uploading to -proposed13:18
didrocksit needs to be available and tested on quantal as well13:18
didrocksas we want the fixes first in the unstable version13:18
didrocksI can sponsor those (as I'll try on quantal)13:18
sil2100didrocks: the branches are prepared for quantal as well, I'll test it too13:18
didrockssil2100: yeah, we need to get that building and confirmed first :)13:19
didrocksdon't want to end up again in the case of FTBFS on quantal and blocked13:19
seb128sil2100, didrocks: I will look at the precise side and make sure everything is in order13:19
didrocksgreat ;)13:19
seb128then wait for the quantal feedback for upload13:19
didrockswill do the same on quantal13:19
sil2100didrocks: when you upload the quantal version, best use this branch: lp:~sil2100/unity-lens-videos/readd_missing_version <- since davidcalle didn't merge in the missing changelog entry yet13:20
popeysil2100, I can test those on quantal too if needed..13:20
sil2100popey: ok, check if you can13:20
didrockssil2100: this is your branch with the two fixes?13:20
davidcallesil2100, didrocks, merging it in a minute13:20
sil2100didrocks: it's the trunk branch (which has the fix already) - I just added a missing changelog entry13:21
sil2100But David will merge it in in a moment13:21
didrocksoh right, this branch doesn't follow the regular packaging practice13:22
didrocksit should be converted at some point13:22
didrockssil2100: interested in doing those for this release?13:22
didrockslike, separate the packaging branch and upstream13:22
didrocksusing merge-upstream13:22
didrocksand rolling tarballs13:22
didrocksit can be a first easy release ;)13:23
sil2100didrocks: but that would be for quantal, yes? Since precise needs to follow the old one still?13:23
didrockssil2100: oh yes, quantal only ;)13:24
didrocksminimizing the diff for already released version13:24
sil2100didrocks: I'll just finish this doc and I'll try doing that ;)13:25
didrocksexcellent :)13:25
sil2100https://docs.google.com/a/canonical.com/document/d/1GcmU2lrprBlZvSnPj27RU8lx7pWmlVeMyrRuwfatgXY/edit# <- can something as simple as this be good?13:26
sil2100davidcalle: thanks!13:28
sil2100didrocks: but to do that, I'll have to create a new bzr repository with just the source, right?13:31
didrockssil2100: exactly, and make the first import and I did last week :)13:31
didrockssil2100: precise "precise", but it seems perfect to me :)13:31
didrockssil2100: also, ensure that embeeded tests or things impacted are still running13:32
didrocksunfortunatly the lens has no test :/13:32
davidcalleWell, it has manual tests.13:33
* davidcalle has his tongue a bit in his cheek13:33
sil2100didrocks: in the source tree, should I leave the bzr history from the previous branch?13:42
didrockssil2100: for your new one, you mean?13:42
didrockssil2100: then, trunk should really becomes trunk and not having any packaging in it13:42
didrocksso bzr rm debian/13:42
sil2100didrocks: yes, for the one I'll create13:42
sil2100Ok, so leave the history, but remove packaging13:43
popeysil2100, your ppa doesn't seem to have quantal sources..13:52
sil2100popey: no, you can try using the precise ones though ;)13:52
popeybah! I knew you'd say that :D13:52
didrockssil2100: doesn't work13:53
didrockssil2100: need to be built with the quantal toolchain13:53
sil2100didrocks: ACK13:53
sil2100popey: so wait a bit13:53
popeyping me, box is setup ready13:53
sil2100popey: thanks13:55
seb128sil2100, you can pocket copy from the launchpad ui13:56
seb128sil2100, https://launchpad.net/~sil2100/+archive/ppa/+copy-packages13:56
didrocksseb128: you can't do that in the same ppa for different releases13:56
seb128didrocks, oh right, versions conflict13:57
didrocksand yes it could have been handy for multiple reasons in the past :)13:58
sil2100didrocks: ok, so I did the merge-upstream thing, but it removed everything from the debian/changelog that was before14:20
sil2100In the 'ubuntu' repository14:20
didrockssil2100: ok, so with the tag, everything was fine?14:20
didrocksthe upstream one which was missing?14:20
sil2100Yes, I changed the 0.3.4-0ubuntu1 tag to upstream-0.3.414:21
didrockssil2100: you can bzr revert debian/changelog14:21
didrocksto get it14:21
didrocksand add the new entry manually14:21
sil2100Ah, wait, I see he has a conflict with debian/14:21
sil2100Anyway, just to be sure I'm doing the right thing:14:23
didrockssil2100: well, it's normal you got one14:23
didrockssil2100: as you removed the debian/ directory upstream14:23
didrockshence the bzr revert14:23
sil2100We want to release 0.3.5-0ubuntu3 for quantal14:24
sil2100So, first what I need to do is to fetch a revision that is _before_ we released 0.3.514:24
didrocksyou will do a new release14:24
sil2100Ah, a new release? Completely?14:24
didrocksyeah :)14:24
sil2100New tarball?14:24
sil2100Ok, this makes things much easier ;p14:24
didrocksso 0.3.614:24
sil2100So the first thing I need to do is prepare the 0.3.6 tarball14:26
=== dandrader is now known as dandrader|afk
sil2100didrocks: how to nicely create the new tarball? Since I see the previous one didn't have the po/ directory14:31
sil2100didrocks: why was it only in distro?14:32
didrockssil2100: it's create on package build14:32
didrocksas for the .mo files14:32
didrocksthat we expurge from the package14:32
sil2100didrocks: so wait, I don't have to prepare the 0.3.6 tarball first..?14:33
didrockssil2100: hum? sure you do14:33
sil2100didrocks: since for compiz you had to do make dist before doing any merge-upstream magic14:33
didrocksit's better to get a tarball14:33
didrocksthat's nothing to do with having some po or not14:33
sil2100didrocks: yes, but should I include that in the new tarball? Since I'm just creating 0.3.6, I need to create the tarball by hand, right?14:34
sil2100By taring and such14:34
didrockssil2100: if you have them generated, yeah, it's better :)14:35
sil2100didrocks: ok so I just do it and then you'll just tell me if it's good or bad14:36
=== dandrader|afk is now known as dandrader
sil2100didrocks: can you check?15:01
sil2100http://ubuntuone.com/6uJF8oLJzKmLIXHWNjBzsU <- tarball15:01
sil2100brb in a moment15:01
didrockssil2100: you didn't bump the version in setup.py15:01
didrocksyou need to do that15:02
didrockscommitting that to upstream trunk15:02
didrockswriting "releasing version <>"15:02
didrocksand tagging15:02
didrocksthen, report that in your packaging branch15:02
sil2100didrocks: ACK, will redo15:14
=== dandrader is now known as dandrader|afk
sil2100didrocks: should I also add that PKG-INFO file to the tarball and trunk or not?15:18
didrockssil2100: not needed15:23
sil2100didrocks: ok, created new branches with the same names15:29
sil2100And tarball here: http://ubuntuone.com/6uJF8oLJzKmLIXHWNjBzsU15:29
sil2100didrocks: could you re-check?15:29
didrockslet me run a test first ;)15:30
didrockssil2100: looks good to me15:34
didrockslooking at the branches now15:34
sil2100 /me hopes he didn't screw up this time15:34
sil2100Ouch, whitespace! Damn youu15:35
didrockssil2100: looks good for me ;)15:36
didrockssil2100: however, you could have looked at the lintian warnings :p15:36
didrockslike no good revision, no up to date standards-version15:36
didrocksi'll update that15:36
didrockssil2100: can you post the release to the bamf page?15:43
sil2100didrocks: what do you mean..?15:44
didrockssil2100: posting the tarball to launchpda?15:45
sil2100Ah, you mean, unity-lens?15:47
didrocksunity-lens-video, right15:47
didrockssorry, got trapped into this bamf thing :)15:47
didrockshum, the rights on this project is screwed up15:48
didrocksI can't even push to trunk15:48
sil2100didrocks: will try - what are we doing with the scopes though..?15:48
didrockssil2100: ensure that tomorrow, davidcalle is taking your tarball and trunk please :)15:48
didrockssil2100: same fate :)15:48
didrocksI'm sponsoring unity-lens-video to quantal now15:48
didrocksseb128: FYI ^15:48
didrocks(did some quick testing here)15:48
seb128didrocks, thanks ;-)15:49
sil2100didrocks: ok, hm, but I don't see a place where the unity-scope-video-remote tarball is published ;p15:49
didrockssil2100: same, we need to do some publishing15:49
sil2100Ah, it's in the same place15:49
sil2100Ok, I see it now15:50
didrockslet's sort the tarball for tomorrow, just keep them15:50
sil2100Ok, I'll create the tarball for that now too for tomorrow15:50
sil2100And the branches15:50
sil2100heh, this one is more tricky15:59
sil2100didrocks: I also prepared branches for the scope...16:11
sil2100http://ubuntuone.com/37ldvMpNknG1bTaUINn3km <- tarball here16:11
didrockssil2100: need to pops out, so will be a real checking tomorrow or later today16:12
sil2100This one was more tricky, so it might be wrong16:12
sil2100didrocks: thanks! Have fun ;)16:12
didrocksthanks, you too16:12
popeydidrocks, do you know if unity looks in /usr/local/share/dbus-1/services/ as well as /usr/share/dbus-1/services/ for lenses on startup?16:49
popeyI have a lens in the /usr/local place but it doesnt seem to start :S16:49
didrockspopey: this is dbus16:52
didrockspopey: dbus is local at both places16:52
popeyoh, duh16:52
didrockshowever unity look for the .lens file only in /usr/share/ IIRC not in local16:53
didrocks(same for .scope)16:53
=== dandrader|afk is now known as dandrader
=== dpb__ is now known as Guest1484
APIhi, today I tried to compile unity18:02
APIit was a long time since the last time I tried18:02
APII used this recipe:18:02
APIand I was able to compile it, but it crashes if I try to use it18:03
APIthe only difference with respect that recipe is that in my system I have precise18:03
APIany idea?18:03
=== zyga is now known as zyga-afk
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== salem_ is now known as _salem

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