[10:03] <sil2100> seb128: hi!
[10:04] <sil2100> seb128: as I wrote in the e-mail, strange thing with the bamf thing
[10:04] <sil2100> seb128: since the tarball is upladed and visible here https://launchpad.net/bamf/0.3
[10:04] <seb128> sil2100, hey
[10:04] <seb128> weird
[10:04] <sil2100> But *strangely* the newly created series is not available from the home page :/
[10:04] <seb128> https://launchpad.net/bamf/ doesn't list it on the right
[10:05] <sil2100> Indeed
[10:05] <sil2100> I think I need to tinker with the LP series properties
[10:05] <sil2100> mhr3: hi! You registered a series before, right?
[10:06] <mhr3> sil2100, hey, sure
[10:07] <sil2100> mhr3: what did I do wrong that the series I created is not visible on the main page?
[10:07] <sil2100> Do you have to set something explicitly?
[10:07] <sil2100> mhr3: ^
[10:08]  * mhr3 checks
[10:13] <mhr3> set it as development focus, changed 0.2 status to "current stable release", you should also branch the 0.2 code into a separate branch now (when it didn't have the 0.3 features, so that bug fixes could be done in that branch)
[10:14] <mhr3> otoh bamf was never branched according to ubuntu releases, so... :/
[10:19] <mhr3> sil2100, ^
[10:21] <mhr3> sil2100, seb128, btw the plan was to make 6.x libunity release with ubuntu's beta, is it ok if we bump stuff now?
[10:21] <mhr3> cause it's 5.96 or something atm
[10:21] <seb128> mhr3, wfm
[10:21] <mhr3> k
[10:50] <sil2100> mhr3: so that branch is necessary, yes?
[10:53] <sil2100> mhr3: works for me regarding libunity as well
[10:54] <sil2100> mhr3: could you branch the bamf code to 0.2? Since I don't really know how to make this fancy lp:bamf/0.2 branch
[11:32] <mhr3> sil2100, why is bamf tagged as 0.3.0, yet configure says it's 0.2.122?
[11:35] <sil2100> Oh, maybe I didn't push?
[11:35] <sil2100> Ah yes
[11:36] <sil2100> Crap, last week was horrible
[11:36] <sil2100> Let me fix that
[11:38] <mhr3> sil2100, also, none of the upstream bugs that were fix committed were changed to fix released
[11:38] <mhr3> at least not automagically
[11:38] <mhr3> which it used to do
[11:38] <sil2100> Yes, since there was no one to run unify this time ;)
[11:39] <sil2100> And I left the milestone opened
[11:39] <sil2100> Since all of this was so chaotic that I didn't want to close it right now
[11:39] <sil2100> mhr3: pushed
[11:40] <mhr3> sil2100, the tag needs to be moved
[11:43] <sil2100> Yep
[11:43] <sil2100> One moment...
[11:45] <sil2100> mhr3: it should be fine now
[11:45] <sil2100> mhr3: I'll change them manually now
[11:46] <sil2100> mhr3: the bugs - or maybe you want to wait a bit? Since I might try familiarizing with that unity thing
[11:46] <mhr3> $ bzr pull
[11:46] <mhr3> Using saved parent location: bzr+ssh://bazaar.launchpad.net/%2Bbranch/bamf/
[11:46] <mhr3> No revisions to pull.
[11:46] <mhr3> Conflicting tags:
[11:46] <mhr3>     0.3.0
[11:46] <sil2100> Strange, I overwrote the tags
[11:47] <mhr3> do i need to pull --overwrite?
[11:48] <mhr3> hmm, that worked
[11:48] <sil2100> I think so - although hm, now that I think of it, does bzr enable moving of tags without overwriting them?
[11:48] <sil2100> Since my bzr-foo is still weak
[11:48] <mhr3> like bzr tag --force?
[11:49] <sil2100> Yes, if I would do a bzr tag --force 0.3.0 and then push it to the remote repo, would it move the tag without me forcing --overwrite-tags ?
[11:49] <mhr3> if you used push --overwrite, it's not surprising that i had to pull overwrite
[11:50] <mhr3> afaik tag --delete and then tag again shouldn't require overwriting
[11:50] <sil2100> That's what I did actually...
[11:51] <sil2100> Strange that you had to overwrite during pull
[11:51] <mhr3> indeed
[11:51] <mhr3> but whatever, i didn't have half-finished branch
[11:52] <sil2100> Sorry about tha
[11:52] <sil2100> t
[11:53] <mhr3> nothing to be sorry about, i guess bzr is just being picky
[11:53] <sil2100> Shit, I did the same thing with nux, grrr
[11:53] <sil2100> Or wait, I think Timo put the tags on
[11:53] <sil2100> ANyway, need to fix that up
[11:54] <seb128> sil2100, mhr3: please guys no --overwrite that breaks all the mergers, distro tools, etc which default to pull and not pull --overwrite
[11:54] <sil2100> mhr3: what would be the best way to move a tag? bzr tag --delete, bzr tag and bzr push ?
[11:54] <sil2100> seb128: I just was doing --override-tags if anything
[11:56] <mhr3> hmm, seb128 has a point, next automerge to bamf will fail
[11:58] <sil2100> Overwriting tags?
[11:58] <sil2100> Ah, right
[11:59] <sil2100> Ok, hm, how to fix this now - maybe I'll bring back the tag to the previous version?
[11:59] <sil2100> But then the commit with the version bump won't be around
[12:00] <mhr3> i guess the branch signature changed already, the only way to revert it is to push --overwrite the original branch
[12:00] <mhr3> although i'm just guessing
[12:01] <sil2100> mhr3: do you have the original branch somewhere?
[12:01] <mhr3> no, i --overwritten it a moment ago
[12:02] <sil2100> Ok, so officially I broke the mergers today
[12:02] <sil2100> Great
[12:02] <sil2100> hm hm
[12:03] <mhr3> at least you didn't do it last week :)
[12:03] <sil2100> Yeah, great ;p
[12:03] <sil2100> Maybe if I tag the same commit, it'll get fixed, right?
[12:03] <mhr3> no idea.. #bzr?
[12:04] <sil2100> Since only the tag is a conflict, and it should be related to the commit it points to
[12:09] <sil2100> Ok, so it seems we can re-add the tag at the old place and it will be te same then
[12:09] <sil2100> mhr3: but do we want that actually? Since the tag was wrongly placed anyway...
[12:10] <sil2100> mhr3, seb128: maybe we can do bzr pull --overwrite-tags once in the mergers to fix those?
[12:10] <mhr3> from upstream pov - no, from unbreaking distro tools pov - yes
[12:10] <seb128> not sure, but the merge is only one place you might have broken
[12:11] <seb128> --overwrite should be banned from such public projects...
[12:12] <mhr3> sil2100, perhaps ask #bzr people if there's a way to move tag without it causing this problem?
[12:12] <mhr3> maybe with a dummy commit or something
[12:24] <sil2100> mhr3: waiting for an answer
[12:24] <sil2100> seb128: ok, I'll put the tag back
[12:25] <seb128> sil2100, thanks
[12:30] <sil2100> seb128: should be as it was before
[12:32] <seb128> sil2100, great, thanks
[13:12] <sil2100> seb128: we would need 2 branches for precise merged, for renaming geis
[13:12] <sil2100> seb128: who should I poke about this?
[13:12] <seb128> sil2100, Didier when he's back wednesday
[13:13] <seb128> I don't have time to deal with precise geis stuff this week with beta1
[13:13] <sil2100> seb128: is there anyone else I could ping about this before that time?
[13:13] <seb128> well, me I guess
[13:13] <seb128> what's the issue?
[13:14] <seb128> is that only vcs merges to do?
[13:14] <seb128> or is that sponsoring and uploads?
[13:16] <sil2100> For now only a vcs merge
[13:16] <sil2100> Since we'd need to have the packaging change uploaded so that we can merge in the code changes
[13:17] <sil2100> hmm, but I need to re-do the branch though
[13:17] <sil2100> Since Francis added some quilt patches
[13:20] <seb128> sil2100, just tell me what to merge where and I will run the command
[14:14] <OwaisL> Hi everyone, has the messaging menu API changed in Quantal? I can see we have libmessagingmenu and after latest updates everything but empathy is missing from the messaging menu
[17:32] <gotwig> hello
[18:37] <gotwig> unity scope devs here?
[18:38] <gotwig> would be pleased to know if          if self.scope.get_filter('appetizers'):
[18:38] <gotwig>                         baseurl = "http://www.chefkoch.de/rs/s0g2/%s/Vorspeisen-Rezepte.html" does work in a scope file. Seems it does not. What do I need to do, so I can check if a filter is active, in a scope?
[18:38]  * gotwig is afk
[19:16] <gotwig> unity scope devs here?
[19:16] <gotwig> I have questions regarding using filters..
[20:04] <gotwig> unity scope/lens devs available?
[20:11] <seb128> gotwig, wrong day,time I guess, it's late for anything but the U.S and it's an holiday in the U.S today
[20:11] <gotwig> and here in Germany, too :/
[20:11] <seb128> gotwig, davidcalle or mhr3 when they are around (european hours), or maybe mhall119 can help you
[20:11] <gotwig> I wrote David Calle a message on GTalk
[20:11] <seb128> he's maybe not around...?
[20:12] <gotwig> yeah, he gets it as an Email I guess
[20:12] <gotwig> I am working on my cooking lens
[20:12] <gotwig> First filters, than previews ;P
[20:12] <gotwig> I have time, till 12.10 ^^
[20:12] <gotwig> around 230,000 recipes are searchable, I guess
[20:13] <gotwig> even some specialized things for Netherlands, Germany
[20:13] <seb128> nice
[20:14] <gotwig> yip..
[20:14] <gotwig> Germany got 200,000 recipes
[20:14] <gotwig> lol
[20:15] <gotwig> Germans like to cook really often
[20:20] <gotwig> night 2 all