=== mhall119_ is now known as mhall119 [06:38] pdf is broken in docs [09:59] flocculant, elaborate? [10:02] it didn't build http://pastebin.com/fvhpze2h [10:03] weird, i just pulled the latest state and it built for me [10:03] mmm [10:03] I pulled when I said it was broken [10:04] No revisions or tags to pull. [10:04] are you on xenial or something other weird stuff? :P [10:04] :) [10:04] bzr status [10:04] of course [10:05] Unit193: status just tells me the things it did build [10:05] https://bugzilla.redhat.com/show_bug.cgi?id=1194369 [10:05] bugzilla.redhat.com bug 1194369 in fop "Exception in thread "main" java.lang.NoSuchMethodError: org.apache.xmlgraphics.xmp.Metadata.mergeInto(Lorg/apache/xmlgraphics/xmp/Metadata;)V" [Unspecified,Closed: rawhide] [10:06] knome: just fyi - it built fine yesterday [10:06] suppose I should have a look see what I've updated [10:06] maybe some syncs from debian landed? [10:06] but later, biab - dodging showers here :) [10:08] yep, looks like libxmlgraphics-commons-java is 2.0 [10:09] but fop is 1.1 [10:10] tbe, it has been 1.1 since trusty [10:10] :P [10:10] Debian has newer. [10:11] yep [10:11] http://metadata.ftp-master.debian.org/changelogs/main/f/fop/unstable_changelog [10:11] there's some ubuntu patches, so it isn't synced autoamtically [10:12] somebody want to poke people on #ubuntu-devel? [10:12] Unit193? [10:12] knome: https://launchpad.net/ubuntu/+source/fop/1:2.0+dfsg-4 [10:12] aha [10:12] good then [10:14] (Except, -proposed and ftbfs, but yeah otherwise good.) Also, I don't see any patches in Ubuntu... [10:14] i assumed there was something because the package version was XubuntuX [10:14] but i guess it's something else silly then [10:14] but good that somebody is actually working on it, even if ftbfs and propsoed [10:15] That's delta, not patches. [10:15] Build-dep transitioned. [10:15] * knome shrugs === rg__ is now known as amerigena [13:10] thanks for looking :) [13:10] I've no need for pdf's - but thought I would mention it was broken here, just in case === sidi is now known as sidi-unbounced [14:24] d [14:24] hi people [14:24] Does Xubuntu have an easy-to-use API for displaying permanent notifications? [14:24] that libindicator thingy? [14:25] i want my sandbox daemon to have a way to display running sandboxes and notify of sandboxed apps performing specific actions [14:27] yeah, if you're thinking xubuntu then yes, you could write an indicator [14:28] O_O [14:28] beware that that'll only work in ubuntu, few distros really support it and the indicator maintainers said they aren't interested in making indicators work in other distros [14:28] an ochosi ... [14:28] the better way may be to write a small panel plugin [14:28] ochosi, the study im doing is on Xub so that's fine by me for now :-) [14:28] right, that too [14:28] not sure whether a panel plugin is actually more work... [14:28] in both you have to live with the restrictions of gtk ;) [14:28] i have a C daemon written in very low-level C code, without even a glib linked to it right now [14:28] it's setuid, too :D [14:29] dont wanna put up too much code into that. Panel plugins are loaded by the panel dynamically, right? [14:29] and they have an init function that's called and run as a panel thread afterwards? [14:30] actually i was thinking of using that persistent thing only for a history of notifications [14:30] and using Xfwm to display primary controls for sandboxed apps [14:33] sidi, ping ping [14:33] it seems my bouncer is back. [14:52] knome: I think a manual sync of the recent translations to the docs branch before renaming the user docs source dir would be wise? Also, notice the .pot file will be renamed too, of course. [14:53] Also, should I try and exempt the SD from the translation too? [14:55] (In the subdir way, that is.) [15:16] Or, similar to the CC one, we could move it to the doc-specific "libs" directory. [15:20] I'd prefer that. [16:26] knome: Just noticed, you might need to fix the placement of the branch icon here :P - https://unit193.net/xubuntu/docs/contributor-docs/C/howto.html#bzr-push Also, might be nice to spell out "Bazaar" for once in the title at least. And I'd expand the title of the page a bit again, to more than just "How to..." And for the XSD one, I'd drop the "The" at the start. [16:32] And I think we should add 'bzr mv' there - it's really important for the resulting diff, as I've just noticed recently! :P [16:33] words and words and words :p [16:33] Yeah, sorry about that. :| [16:33] :D [16:33] pffft [16:33] why worry :) [16:33] Right! [16:34] or rather - nothing TOO worry about :) [16:42] knome: but if you do do anything - can you fix the with with in QA team release responsibilities :) [16:48] Hah - plus missing period. [16:49] Also, I'd make the whole "Release Note" the link. [16:50] Similarly for other links in that page. [16:50] * on [16:51] Like "Manual Testcases". [16:54] "bug report to the testcase project" - "bug report" should link to "../+filebug", rather than "project". [16:54] not that concerned about that tbh [16:55] imo these pages shouldn't need handholding [16:56] Basically, I want the anchor text indicate what to expect of the target. [16:56] well you know what I want got :p [16:57] Yep, "just click the link!" :D [16:57] things like that really don't bother me much :D [16:58] that said if you're that concerned - do an MP as long as you don't change words without me knowing :) [16:58] remember to do the with with though :p [16:58] lol [16:59] which does bring up a point seriously [16:59] Yeah, I have a huge MP upcoming anyway. :P [16:59] taking QA as an example [16:59] if changes to QA pages are subject to an MP - then the QA lead should ack them [16:59] and docs- doc team [16:59] etc [16:59] Yeah, agree. [17:00] Just add as additional reviewer then. [17:00] not really an issue when it's all new and the people concerned are filling the hole [17:01] perhaps should be in there somewhere as a point [17:01] krytarik: yea [17:02] In Processes probably then. [17:02] considering there wasn't anything at all a week or two ago it's all pretty much \o/ if you ask me [17:02] yea - that would probably work [17:02] Indeed! [17:12] So many "Xubuntu" there that seem unneeded! :P [17:12] probably [17:13] in fact unless it's pointing to somewhere linky - not sure it's needed ever [17:14] except the strategy doc [17:14] Also, noticed while in the index it says "Subteam documentation", QA has three chapters in there. :P [17:14] yep [17:14] greedy as you like [17:15] Not sure the title of the SD needs to have it either though. [17:16] needs to have what? [17:17] "Xubuntu". [17:17] it doesn't [17:17] at least not here [17:18] says Part I. Subteam documentation here [17:19] There's only one pot file? [17:21] Unit193: One per doc variant. [17:21] Ah good, OK. [17:23] I thought pot files were translation things? [17:26] Yep - it'd seem Unit193 is referring to something reg. the user docs one I said earlier. [17:26] Unit193: And yes, I only touched that one. [17:28] so - forgive me if I'm looking at this wrong - should there be any pot file for the cont docs? [17:28] There is. [17:30] right - but why? [17:31] knome put it there first! :P [17:31] not saying he didn't :) [17:31] flocculant: I wondered too. [17:32] I vaguely saw Unit193 and knome talking about cont docs and languages - with the result being it should be english [17:32] not sure when now - days merging :) [17:33] No one concluded it shouldn't be offered for translation at all though - only exempt the SD. [17:33] I'd certainly not promote it as much as the user docs though. [17:34] yea - but if cont docs are in say swahili - tends to imply if someone comes here talking swahili someone will answer them :) [17:34] should be in en imo - if for no other reason than it implies that all the cont stuff is en [17:35] anyway - not overly bothered till someone tries to talk to me ;) [17:35] Heh. [18:41] Well infinity popped up, but that's not the one we're looking for, IIRC. [18:41] for? [18:42] Core MPs. [18:42] Unit193: Also, they're going to force you to update them anyway! :P [18:42] he'd do I'm sure [18:44] I'm not sure. [18:45] Honestly, I'd say have them review first, then fix if NACK and update if ACK. [18:45] Yeah. [18:45] Unit193: iirc he was involved with the discussion before slangasek [18:46] and yea agree with that [18:46] cos it's easy for me to say :) [18:46] flocculant: You remember well. The second is the one that wanted changes/did more of a review. [18:46] Also, I don't plan to update it for review. :P [18:46] yea - well I did ping slangasek a while back but [18:47] Yep, thanks for that. [18:47] Unit193: I assume you mean - let them ack the way we want to do it - and then update it if they ack [18:47] Rebase/make it nice, yeah. [18:51] k - just like to know where we are :) [18:53] Seemingly in a rowboat in the middle of a great lake without a paddle. [18:58] lol [18:58] hope it's a big boat if we're all in it with you :D [18:59] got an LO update earlier - seems I had some other icon set too [20:56] huhu [21:12] hey ho knomio [21:13] o/ [21:33] Are bugcontrol members ever useful? [21:48] flocculant: In order to try and get you back on my good side, new xfdashboard is already in the extras PPA! [21:48] :) [21:49] I'm always on my good side ... [21:49] I did see the mail an hour or so ago about that [21:50] why's it in ppa twice though? [21:50] Still building. [21:50] aah - ok :) [21:52] Unit193: oh yea - I did use the xfce sound plugin for a while - but I had two sound notifications [21:52] even though I had removed other one and rebooted [21:52] indicator-sound was purged? [21:52] will check that properly tomorrow again [21:52] pretty sure I did [21:53] And, ochosi or someone wants results on that, I'm just the packager. [21:53] at the time - the 2 notifications was annoying enough to just stop even looking [21:53] I'll check it out again tomorrow [21:54] Understandable, I'm not testing it either. :3 [21:54] :) [21:54] I should though. [21:55] ppa says newer version available - that always confuses me [21:57] Fixed. :P [21:57] :) [21:57] I'll check it out tomorrow :) [21:58] anyone need to know anything about xfdashboard? [21:58] I only wish it wasn't enormously full screen :p [21:59] I do! Is it going into Ubuntu? That's the "development" branch we've got in the PPA, I'd presume we'd want stable? [21:59] not as far as I know [22:00] I guess full screen would be ok if you had a whole bunch of things open :) [22:04] OK, well enough users in extras to keep it going (heck, a team member likes it, that's good enough), so that's fine anyway. [22:06] mmm [22:07] actually it's bigger than full screen [22:07] if I whack the mouse over to the right it sees all the right pane [22:07] and just upgraded it [22:08] unless it's always been like that and I'd not noticed ...