[00:00] <asac> so for packging changes you add new bullet points to topmost changelog entry.
[00:01] <hjmf> OK it is safe then for (i.e. 3.1)  to not modify the version number firefox-3.5 (3.5~b4~hg20090330r24021+nobinonly-0ubuntu1) jaunty; urgency=low
[00:01] <hjmf> in 3.2 it's pretty clear because of the tag UNRELEASED
[00:02] <hjmf> firefox-3.6 (3.6~a1~hg20090330r26723+nobinonly-0ubuntu1) UNRELEASED; urgency=low
[00:02] <asac> hjmf: so 3.1.head has jaunty on top?
[00:02] <hjmf> yes
[00:02] <asac> hjmf: this means no new bullet points can be added there
[00:02] <asac> hjmf: so just run a dch -i -DUNRELEASED
[00:03] <asac> and add your text there
[00:03] <hjmf> OK
[00:03] <asac> leave it at UNRELEASED
[00:03] <asac> whoever uploads the change will do a release commit that flips that to jaunty (or karmic or whatever)
[00:04] <hjmf> I remember changing by hand those numbers in the past
[00:04] <asac> ;)
[00:04] <asac> yeah. dch is nice too ;)
[00:04] <asac> its more failsafe
[00:05] <asac> hjmf: only thing is you have to set your name and email properly to env i think
[00:05] <asac> env | grep DEB
[00:05] <asac> DEBEMAIL=asac@ubuntu.com
[00:05] <hjmf> I've just tested it right now, yeah! pretty cool
[00:07] <asac> hjmf: oh another cosmetic nit for changelog bullet points: we usually use the "- update|add|remove path/to/file" below the changelog entry in mozilla branches
[00:07] <asac> hjmf: there should be a bunch of examples
[00:08] <hjmf> OK taking note
[00:08] <asac> but i think thats only how we do it. so for other projects its usually * path/to/file: changed this and that
[00:08] <hjmf> The last one
[00:08] <asac> :)
[00:09] <hjmf> asac: should I fill a bug for each branch before proposing the merge
[00:09] <hjmf> ?
[00:09] <hjmf> asac: just to see which are the best practices
[00:09] <asac> hjmf: no need to. merged should be enough. you refer to the same bug everywhere
[00:09] <hjmf> OK
[00:09] <asac> hjmf: you can add the firefox-3.5 target to the bug (for the firefox-3.1 branch)
[00:10] <asac> hjmf: click on "Also affects distribution" ;)
[00:10] <asac> and select firefox-3.5
[00:10] <hjmf> I'm doing it :)
[00:10] <asac> sorry for the naming confusion. we didnt come to rename firefox-3.1 branches to 3.5 yet
[00:11] <hjmf> Package firefox-3.6 not published in Ubuntu
[00:11] <hjmf> OK then
[00:12] <asac> hjmf: yeah. thats only trunk. we dont have that in archive
[00:12] <asac> merge request is just enough
[00:12] <hjmf> lets do it, let me some minutes :-)
[00:12] <asac> hehe
[00:16] <asac> hjmf: look at this too: http://bazaar.launchpad.net/~mozillateam/firefox/firefox-3.0.head/revision/395
[00:17] <asac> its even better to refer to authors with email imo
[00:17] <asac> we try to remember to do that ;)
[00:17] <hjmf> OK
[17:53] <asac> Bug 228806
[17:53] <asac> that one is fun ;)
[17:56] <asac> mozilla bug 488311
[18:21] <armin76> asac: mozilla bug 448658
[18:22] <armin76> [reed]: add whoever should be for review, plz :)
[22:10] <mconnor> asac: so, where can I find a libnotify API doc?
[22:12] <fta> mconnor, libnotify-doc?
[22:13] <mconnor> fta: which is where?
[22:13] <BUGabundo> yayyyyyyyyyyy pidgin is working again on freenode!
[22:13] <mconnor> er, you get the docs by installing the package?
[22:14] <mconnor> that's... special
[22:14] <fta> mconnor, yes
[22:14] <fta> most people don't need docs for system libs
[22:14] <mconnor> and if you're not running linux, and you want to understand soemthing someone jammed into your source tree without the right reviews?
[22:14] <mconnor> why aren't they on the web?
[22:14] <mconnor> why are they something you would have on your system?
[22:15] <mconnor> seems like that makes things harder, not easier
[22:16] <BUGabundo> fta so what's up with LP and karma?
[22:16] <BUGabundo> haven't had the time to read the Answer on it
[22:16] <fta> http://www.galago-project.org/docs/api/libnotify/
[22:19] <fta> BUGabundo, no idea, i just see mine going off the charts
[22:19] <BUGabundo> fta I saw! crazy
[22:25] <mconnor> fta: that's current?
[22:26] <fta> not sure, i'll install libnotify-doc
[22:26] <fta> 0.3.2 vs 0.4.5
[22:27] <mconnor> thanks
[22:27] <mconnor> I'm at home, I don't have access to VMs etc
[22:28] <fta> mconnor, want a zip/tar.gz of 0.4.5 ?
[22:28] <fta> it's tiny
[22:28] <mconnor> fta: that'd be great
[22:28] <mconnor> you can just drop it in email if you want
[22:30] <fta> mconnor, http://www.sofaraway.org/ubuntu/tmp/libnotify.tar.gz
[22:30] <fta> that's all of libnotify-doc 0.4.5
[22:31] <mconnor> fta: awesome, thanks
[22:32] <mconnor> It seems like that'd be easy to automate and put somewhere searchable
[22:32] <mconnor> but clearly making everyone add packages is better
[22:32] <mconnor> or... something :)
[22:32] <fta> some devs prefer to have access to docs offline
[22:33] <fta> and once installed, you're sure your docs match your libs, both are updated at the same time
[22:34] <asac> mconnor: libnotify is basically a wrapper lib around http://www.galago-project.org/specs/notification/0.9/index.html
[22:34] <asac> mconnor: online docs are usually published by the upstream project - which makes sense somehow
[22:34] <asac> e.g. we don't republish MDC on ubuntu.com or something
[22:34] <mconnor> asac: sure
[22:34] <mconnor> I just don't know why you'd have a package for docs
[22:35] <asac> if they fail to update their online docs, its not much we can do :)
[22:35] <mconnor> it seems strange as hell to me
[22:35] <mconnor> anyway, I have the answers I need now!
[22:35] <asac> mconnor: its handy. first: you dont rely on the project still being online (could be abandoned or bankrupt or so on)
[22:35] <asac> secondly you dont need to search the web for the libs you have available in ubuntu
[22:36] <mconnor> I tend to avoid relying on abandoned projects where I can ;)
[22:36] <asac> so its a redundant service to also produce the docs during build (which is easy)
[22:37] <mconnor> so should I assume that ubuntu's libnotify doesn't deal with callbacks at all?
[22:37] <mconnor> or is that just a guideline?
[22:37] <asac> mconnor: obviously its bad to rely on something abandoned. but in this sense distros also help to preserve existing knowledge/code, so someone can adopt software or parts of it
[22:38] <asac> mconnor: ubuntu libnotify should be compatible with the spec. even actions are supported. they are just not supported in a shiny fashion
[22:38] <mconnor> ok
[22:38]  * mconnor hits some Mozilla people with a hammer
[22:39] <asac> mconnor: the idea is to use org.freedesktop.Notifications.GetCapabilities to check for the "action" capability
[22:39] <asac> and if thats not available, dont send it
[22:39] <asac> mconnor: yeah. the right implementation for toolkit should get action support
[22:40] <mconnor> I also think mpt's on crack, if I had time to write about why those guidelines are worse for users, I'd ahve done it by now
[22:40] <asac> mconnor: do it. open discussion can only help if done in a professional fashion
[22:40] <mconnor> giving up booze has lessened my propensity for angry rants
[22:41] <mconnor> asac: yeah, I know
[22:41] <mconnor> one can hope, at least
[22:43] <asac> mconnor: so what reviews were missing on the libnotify commit?
[22:43] <asac> didn't that have review/superreview?
[22:43] <mconnor> asac: ui-review, review from an actual toolkit peer
[22:45] <mconnor> actually, I guess roc's kinda/sorta the right peer, even though this was in a different part of the code tree
[22:45] <mconnor> but it changed interaction model, and broke a capability that toolkit components (and strings) assume is there
[22:45] <asac> mconnor: ui-review for something that isn't enabled?
[22:45] <mconnor> it's not enabled?
[22:45] <asac> mconnor: right. for now i would assume its work in progress
[22:46] <asac> mconnor: afaik its not enabled by default
[22:46] <asac> could be that that changed recently though
[22:46] <mconnor> it's possible that some builds don't have it
[22:46] <mconnor> but reading the patch, it looks like if libnotify is available, we use it
[22:47] <asac> i think you need --enable-libnotify
[22:47] <mconnor> possible
[22:47] <asac> for builds with that flag it will be used once libnotify is available on system, yes.
[22:48] <mconnor> ok, less annoyed now
[22:48] <asac> ;)
[22:48] <mconnor> but
[22:48] <asac> but
[22:48] <asac> there is always a but ;)
[22:48] <mconnor> we should ui-review stuff when it's being implemented, not at the end
[22:48] <BUGabundo> is it possible to have spyware on ubuntu? I just got a pop up page when clicking on a gmail link
[22:49] <mconnor> anything's possible
[22:49] <mconnor> it's software
[22:49] <asac> mconnor: yeah. i can talk to ventnor how to best finish this work. i agree that the implementation should be complete
[22:49] <mconnor> whether people are bothering... I dunno
[22:49] <mconnor> asac: since ventnor was talking about needing to change strings, I think he thinks it's complete
[22:50] <asac> mconnor: have you seen him recently online?
[22:50] <mconnor> no
[22:50] <mconnor> sec
[22:50] <asac> i think i send him a mail a few weeks ago, but he never replied. wonder if he declared mail-bankrupt for that email address ;)
[22:50] <mconnor> could be
[22:51] <mconnor> hasn't been online in seven weeks, according to firebot
[22:51] <asac> mconnor: heh. hmm.