/srv/irclogs.ubuntu.com/2014/11/05/#xubuntu-devel.txt

bluesabreevening folks00:14
slickymasterhey bluesabre 00:14
bluesabreUnit193, slickymaster: I tried experimenting with building the docs, but could not get the build process far enough... if died with some xml validation00:15
slickymasterbah just hope we're not facing a dead-end00:15
knomebluesabre, pastebin the output plz, it sounds like it's a problem somehwhere else00:17
slickymasterknome, regarding the last section of managing-applications.xml you pinged me about ->  http://pastebin.com/sAeTEcnq00:19
slickymasterreview and tell me if I can merge it00:19
knomeslickymaster, i think the wording is a bit clumsy00:21
slickymasterwhich one?00:21
knomeand while the argumentation is true, it's not mentioning the most important things00:21
knomeince each new Xubuntu release ships not only bug fixes but also updates for potential security problems and hardware support improvements, it's not recommended setting to <guilabel>Never</guilabel> the option to handle release updates notifications. 00:21
knomei'll put that in a pad and you can see how i'd change that00:21
slickymasterok00:22
knomehttp://pad.ubuntu.com/xubuntu-docs00:22
bluesabrehttp://paste.ubuntu.com/8827154/00:24
knomeslickymaster, there00:25
slickymasterhmmm00:25
knomeUnit193, sounds like a problem with relative paths?00:25
knomeor simply malformed translator xml files00:26
slickymasternot sure about starting the second sentence with "At the same time..." knome 00:27
slickymasterI mean it's already been stated that it would be a EOL version00:28
slickymasterwhich pretty much sums it all00:28
knomeyeah...00:28
knomei was thinking the same00:28
knomewhat about that?00:29
knomenah, i think it's as much duplication now00:29
knomethe point is not that their system is crap00:30
knome:P00:30
knomethe point is that we will not support it00:30
slickymasterJust to give some background00:30
slickymasteron why00:30
knomeand, at the same time, their system might be a bit duh00:30
slickymasterthat will happen for sure00:30
slickymasterbut then they'll be at their own risk00:30
knomeok, so what about hat00:31
knomethat too00:31
knomeno hats allowed00:31
slickymasterhappy with it00:31
knomeok, great00:31
slickymasterknome: what about the other options sub.section00:31
knomefine with the rest as is00:31
knomeone more thing i considered00:31
knomebecause the mailing list thread00:32
knomedo we want to mention synaptic?00:32
slickymasteri thought on dropping it, but the again i thought of expanded it a bit00:32
slickymasterno, just for one reason00:32
slickymasterwe'ew nor shipping it 00:32
knomeyep00:32
knomewe could say something like "Advanced users might want to use Synaptic (available from the repositories), ..." 00:32
knomebut yeah, there are a few problems with that00:33
slickymasteryeaps, if it works don't touch it00:33
knome1) everybody suddenly becomes an advanced user when we say that00:33
slickymasterexactly00:33
Unit193bluesabre: bzr pull && bzr status00:33
knome2) if we have decided that USC (and apt-get) is good enough, why mention other things00:33
Unit193translators.xml:1: element itemizedlist: validity error : Element itemizedlist content does not follow the DTD  is all I get, and that's because it doesn't setup translators.00:34
knomeslickymaster, oh, one more liiitle thing00:34
slickymastershot00:34
slickymastershoot00:34
slickymastera shot would be nice, also00:34
knomeslickymaster, in the itemizedlist "never" section, maybe say "not recommended, see below"00:34
knomeor alternatively,00:35
knomemove the note about why the LTS method is recommended below the list as well00:35
knomeconsistency, consistency...00:35
knomei'd probably lean towards the latter00:35
knomewith a simple <info> box or sth00:35
slickymasterso, <itemlist> x 300:36
slickymaster<info>00:36
slickymaster<warning>00:36
knomeyep00:36
slickymasterok, I'll cahnge the <warning> wording, update the changelog (including the bug elfy worked onDDD00:36
slickymasterand do those changes also00:36
slickymasterand merge00:36
slickymasterdamn so many typos00:37
knome"Opting in for LTS notifications is usually the recommmended option, especially if you are running Xubuntu on a production machine and/or need maximum stability."00:37
knomes/usually/in most cases/00:37
knomethere's something to start with :)00:37
slickymasterinstead of "...recommended if you need maximum stability" you say?00:38
Unit193Fixed it, maybe.00:38
slickymasterknome: ^00:38
knomeslickymaster, yeppers00:39
slickymasterok00:39
knomebecause i think that's what we want to say00:39
* slickymaster agrees00:39
knomesaying "update only every 2 years if you want max stability" is self-evident00:39
knomeso is the new form to say it, but meh... :)00:40
slickymasterit's a richer wording anyhow00:40
slickymasterit shows we care00:41
slickymaster;)00:41
knomeof course, it's many words longer as well ;)00:41
slickymasterok, doing it00:41
Unit193Actually, more confused than before.00:43
slickymasterlol Unit193 00:43
Unit193Ah I see.00:44
Unit193What idiot wrote this?!00:44
Unit193...Oh right.00:44
knomehah.00:48
slickymasterknome, should I run: bzr commit -m "bla bla" --fixes LP:1385479 ?00:50
slickymasterbecause I'm updating the changelog on that bug00:50
slickymasteror should i drop that parameter from the commit command?00:50
knomeif it's mentioned correctly on the changelog, no need to do that on the commit00:51
slickymasterok00:51
knomeapparently using the parameter makes the bug marked as "Fix Available", which is more suitable for "real" bugs in software anyway00:52
slickymasteroth it would close that bug report00:54
knomeit wouldn't00:54
* slickymaster thought it would :P00:54
knomefix available is as good as fix committed, which is what the changelog change does00:54
knomefix released is the status we get once the new docs package is uploaded00:55
slickymasterok00:55
slickymasterPushed up to revision 272.00:55
slickymastercare to check it knome, pretty please00:55
knomegreat00:55
knomeok, since you ask so nicely00:56
slickymasterdanka00:56
knomevalidates at least00:56
slickymasterlol00:57
slickymasterthe shame if it wouldn't00:57
Unit193echo $TEXTDOMAINDIR $LANGUAGE 00:57
Unit193/tmp/buildd/xubuntu-docs-15.04/desktop-guide/po//mo/ es00:57
Unit193http://pastebin.com/YdV3J01a00:57
Unit193I see nowhere does it search that dir.00:58
slickymasterknome, I forgot to add to the changelog what I've done :P00:58
knomeslickymaster, you know, i think we should use "Long-term Support (LTS)" instead of just LTS in that note00:58
knomechange that and change the changelog as you do that :)00:59
knomeotherwise - looks good00:59
slickymasterokie doke00:59
Unit193gettext just doesn't care about ENV vars?01:01
knomeUnit193, maybe?01:01
Unit193But it works outside the chroot!01:02
* knome shrugs01:03
Unit193`../scripts/translators.sh -l es`01:03
Unit193http://paste.openstack.org/show/5ewmsZgxTd8zxSytPTy9/01:03
knomei "understand" chroots, but they are in a way just as black magic to me as programming is to elfy01:04
slickymasterok knome, Pushed up to revision 273.01:04
slickymasterif you'd be so kind01:04
knomesec01:04
slickymastersure01:04
knomelooks all good to me01:07
slickymasterok, that done01:07
slickymasternow we just have to wait for jjfrv8 on the glossary 01:07
knome:)01:07
Unit193And, that's enough for one evening.01:10
slickymasterwhat01:12
slickymasterso soon Unit193 ?!01:12
slickymaster:)01:13
knomelazy Unit193 01:13
slickymasterage does not forgive 01:14
slickymasternor forgets01:14
Unit193Well, it just seems to ignore them, with no reason as to why, and no manual says it either.01:17
Unit193Brick wall with nowhere to go.01:17
slickymasterwe still have time Unit193 01:19
elfybluesabre: I updated utopic thunar, but I'm not sure my machine is one to test verification on as I fiddled with mimecache.info - the new thunar didn't make any difference to pdf opening in gimp there07:15
ochosimorning everyone08:57
ochosielfy: thanks for the testing-overview email!09:56
ochosii guess this time around there are a few good reasons to participate in a2, we'll get a new gtk3 version as well and that might break stuff again, and upower0.99 09:56
bluesabrehey elfy10:36
bluesabrethanks for letting me know... will set up a vm to verify10:36
ochosimorning bluesabre 10:36
ochosiand sorry for pinging you all over the place :>10:36
bluesabreit happens10:38
elfyochosi: 13:26
elfysigh13:26
knome:)13:26
ochosielfy: yes..?13:27
ochosi:)13:27
elfyochosi: the bug I reprted yesterday has been marked a dupe of another private one that no-one can read 13:27
ochosiawesome :/13:27
elfyyep13:28
ochosiby whom?13:28
elfylaunchpad I guess13:28
elfycommenting13:28
ochosiyeah, uncool13:28
ochosiwhy would that be a private issue13:28
ochosiit's not really security/privacy related13:28
brainwashcoredump13:29
elfycommented13:29
brainwashthis means that at least one other user encountered the same crash :)13:29
elfyyep and entirely likely that the other user won't go back to it either 13:30
elfyhttps://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1389400/comments/313:31
ubottuError: Could not gather data from Ubuntu for bug #1389400 (https://launchpad.net/bugs/1389400). The error has been logged13:31
elfybluesabre: re thunar - not too sure what's going on with that actually 13:34
bluesabreelfy: a patch was provided upstream, we packaged that and added it to vivid, and the same patch added to utopic-proposed13:35
bluesabreI'll comment/verify the bug tonight13:36
elfybluesabre: ok - what I meant was I didn'ty know why I couldn't verify it - I'm assuming because I mucked about with the .cache file13:36
elfyochosi: ok - panel - I've removed indicator-app and will watch it, then add that and remove another 13:37
bluesabremight be related, defaults should be respected now13:37
bluesabregotta run, bbl13:37
elfymeant to say that this morning13:37
elfybluesabre: mmm then if that's the case I'd have to verification-failed13:38
elfycya later - have fun :)13:38
ochosielfy: ok thanks13:38
bluesabreelfy: not sure of the risk, but you can try deleting that cache file and logging in/out13:39
elfybluesabre: ok - I'll try that when back properly - it's an unused install now anyway :)13:39
ali1234anyone want to do a session at UOS?15:32
knomeali1234, not really; if we want to have a session, there's no need to coordinate it to happen at the same time than UOS anyway15:36
knomeafter real-life UDS's ended, there hasn't been any benefits/synergies when doing that15:37
ali1234it would be more for promotional purposes15:38
knomewhat would the subject of the session be?15:38
ali1234"look at us, hey, look, we're still here"15:39
knomethat's a bad subject line..15:39
slickymasterWorklol15:39
* slickymasterWork likes ali1234 subject15:40
ali1234lubuntu is doing a session titled "Latest Developments In Lubuntu Development"15:40
ali1234and there's also "happy second birthday ubuntu gnome"15:40
knomeok, so who's willing to run that session?15:41
ali1234me15:41
knomewhat are we actually talking about?15:41
knomeok, great15:41
ali1234i don't know15:41
knomemind creating a pad and dump ideas there?15:41
knomeand send an email to the list saying you'd be interested and willing to run the session and ask for feedback/idas15:42
knome*ideas15:42
ali1234i don't actually have any ideas15:42
ali1234kubuntu: "We will be showing off our Plasma5 tech preview and have a Q&A session for users."15:43
ochosiit's not a bad idea, but i'm also not sure what it could be about15:43
ochosiso far, there haven't been colossal steps forward15:44
knomeyeah, and there are no big plans either15:44
ochosi(although i guess that's not necessary for every release)15:44
knomeali1234, but if you could still do that... at least we'd have a place where we can drop ideas, and somebody saying "i'll do it"15:44
knomei'm sure i can figure out a few things that we can talk about15:44
ochosias long as we have a title as self-referential as lubuntu's, i'm fine :>15:46
knomehuhu15:46
ochosi"Xubuntu Developments in Xubuntu Development" would be my #115:47
knomeplease no15:47
knomedon't even joke about that15:47
ochosi:D15:47
ali1234with Xubuntu developers?15:47
pleia2ftr, my vacation overlaps with UOS, so I'm skipping this time around15:47
knomepleia2, that's good to know and completely fine :)15:47
elfyso - did that discussion ^^ actually get a result? or is it still we don't do theseuds/uos things?16:16
ochosiif ali1234 is willing to host a session, i'm +116:18
elfyok - well for my sins I've apparently agreed to be a track lead so should be able to set it up16:18
elfythat does not equal run it I add ;)16:18
knomeelfy, i'm working on the qa-v-cycle pad, or tbe, the draft for the process page updates16:22
knomethough i'm not really working *at the pad*16:23
knomei have a three-way comparison in meld16:23
elfyk - well when you think you've got something that I can ack or not let me know - thanks :)16:26
knomelet me send you email with some files you can compare16:28
elfywell - I would rather just have a draft of what you get to tbh16:28
knomedone16:29
knomewell, one of the files is a draft16:29
knomebut i have added the appropriate partsf for your and the current version for comparison16:29
knometwo things i've left out:16:29
knomethe specific testing requirements for the team, because i'm not sure if the processes page is the right one for those16:30
elfywhich is the draft? the proc-test-new one?16:30
knomethe draft is -knome16:30
knome-new is your version16:30
knome-old is the one in the wiki16:30
elfyk16:30
elfywell 16:30
knomeand the other thing, the qa incenctive program, because we need to find the right place for that as well (probably website)16:31
knomewhat about16:35
elfyyea - wasn't too sure what to do with that tbh16:35
elfyand I would say without a doubt that x.org is the place for it - then we've got complete control 16:35
knome"The Xubuntu team members are expected to run milestone tests when they can."16:37
knomeor sth along the lines of that16:37
knometo me, that communicates the same thing, and even a bit more16:37
elfylily-livered16:37
knomehehe, yeah16:37
elfythat communicates nothing that we've not got already16:38
elfyI'm sorry - but if -team is the group who thinks 'release' is what we want to actually release - they should be prepared to test at least once in a cycle16:38
knomefrom my pov, what we need is a change in attitude16:39
knomechange in the strategy document can hardly do that16:39
elfyand asking nicely 2 or 3 times a cycle for people to actually test does not work16:39
knomeso putting down "you need to do X" in the SD is as good as.. nothing, in a way16:39
elfyand my position is that if team can't be bothered to test - why should I be bothered to set all this stuff up?16:39
knome^ don't get me wrong16:40
knomeagree with you16:40
elfyeveryone says that knome - and then nothing actually changes or happens ;)16:40
ali1234i don't16:40
elfyali1234: you're not in -team16:41
ochosithing is, people might wanna just contribute to the team in one field, and that's still a valid position16:41
knomeelfy, that proves there is no change in attitude16:41
elfyochosi: sorry - if people in team can't be bothered to test I see no reason why I should care either16:41
knomei guess "because you care about xubuntu"16:42
ochosielfy: well, i could also say that if others in the team can't be bothered to draw icons, why should i?16:42
elfyochosi: what happens if we have to drop some new package in and the only person who tests it is me 16:42
elfyand then we get hundreds of bugs 16:42
elfyochosi: becasue testing is about making sure the whole thing works 16:42
knomeelfy, then it's a fail16:43
elfyif it took 24 hours to run a test I can understand it - but a few minutes once in 6 months :)16:43
ali1234the problem is that it does take 24 hours to run a test16:43
ali1234because the installer has very few bugs. installing an iso and then checking each default program loads up just doesn't uncover bugs16:44
knomeali1234, that'a a different thing16:44
ali1234most of the actual bugs this cycle would not have been found by iso testing16:44
knomeof course16:45
ali1234for example the suspend thing, and the Qt problems16:45
elfyali1234: they might have been found if more people had been testing packages and running the system16:45
ali1234if you want testers to check for stuff like that, then you're asking them to spend a day on each test16:45
elfyI'll bbl16:46
knomeelfy, or not - we do not do/encourage a lot of exploratory testing16:46
ali1234well quite, i think more people should run the development system. i don't see much benefit in iso tests and the iso tracker16:46
elfyso I'm just completely wasting my time then - can't even get some people to check that the image boots16:49
knomeelfy, no, we should still keep on doing that16:50
knomeyou are just talking about two different things16:51
knomeexploratory testing, with which people find the most bugs16:51
knomeand manual ISO/package testing with testcases, which test that the basics of the system are working16:51
knomewhat ubuntu desktop have done lately is that they've shifted (or at least tried to shift) more towards the exploratory testing, because most of the basic tests are run automatically now16:52
knomecreating PPA's that have the development versions of the packages is in the same spirit as that16:53
knomeso we should encourage people to do that (as well)16:53
knomebut find a balance/way to get the basic manual tests ran enough times as well16:53
elfywe have none of that - we aren't ubuntu with a whole team for QA16:54
knomeno, but that's why we have to find other ways to do ti16:55
knome*it16:55
elfyif we aren't able to get people to run a basic install test at milestones - we have no chance of getting them to run the packages we're releasing16:55
knomeand if you look at the ubuntu desktop testing results, they aren't wonderful at all times either, even if they have the whole team for QA, and many more testers from the community16:55
knome(or at least more potential testers)16:55
ali1234i run the development PPA all the time16:56
elfythey don't have to be - they've got other tests running16:56
ali1234it's much easier than constantly reinstalling my computer16:56
knomeelfy, ^ what ali1234 said, running a development PPA *is* testing the packages we're about to land16:56
knomeand yes, it is easier16:56
elfyali1234: you might - and thanks, but all I CAN know about is the results I see on the trackers16:56
elfynot comments in an IRC channel that I might possibly see16:56
ali1234it is also much more useful, i'm much more likely to find bugs on a system i am using, rather than one i'm going to trash after 5 minutes16:56
elfyand THOSE tell me that no-one cares 16:57
knomeso the question is: how do we measure how successful the PPA testing is?16:57
knomei don't think there is an easy way16:57
elfyreport it on the tracker16:57
knomethere isn't a test on the tracker for PPA testing16:58
knomeand the point is that the PPA testing doesn't follow a tight testcase definition; people do what they usually do with the apps16:58
knomeand then they either find or don't find bugs16:58
elfythere doesn't need to be as long as there is a test for mousepad - report mousepad things there - if someone's using staging mousepad - put in the comment16:58
knomeok, then we should encourage people to do that16:59
knomemaybe a general testcase for "PPA tests"16:59
ali1234why must this be done in addition to reporting a bug on launchpad?16:59
ali1234if a find a bug i report it. if the bug report is not closed, you can assume the bug is not fixed. the tracker reports could be generated automatically16:59
knomewhat about adding a specific tag for bugs found with the staging PPA?17:00
knomethat sounds like the most accurate method to measure it17:01
knome(of course not the time that went to it)17:01
ali1234yes, one big problem with launchpad is it hates when you use PPAs and tries to prevent you from reporting a bug (at least apport does)17:01
knomeali1234, unless you file the bug manually17:02
ali1234yeah17:02
knomethat's a valid point17:02
ali1234although this is not an issue if you are running +117:03
ali1234as opposed to release plus staging ppa17:03
ali1234https://errors.ubuntu.com/?user=a-j-buxton&period=month look at all those bugs17:07
elfythen perhaps we don't bother with package tracker at all this cycle and tell the -dev list that we'll just be looking for reported bugs17:07
knomeelfy, if we manually add tags to those bugs that are found when using the staging PPA, yeah that sounds like a good experiment17:08
elfywell that's not anymore wishy washy than hoping people report on the tracker so not any worse17:12
knomeit's a different change, but if people are running the staging PPA already, it's less asked17:21
elfyyep - so anyway to know how many do? 17:21
elfyand we'd get bugs reported from people running vivid but not ppa as well - assuming they report them17:22
elfybut not specific to us unless of course it's a specific xubuntu package17:23
elfywe don't want to just look at staging ppa17:23
elfyI've not got an issue with us doing this - but team has to agree - and soon I guess or it'll be too late17:24
elfynone of this though makes any difference whatsoever to the not running basic install tests 17:25
knomeelfy, no way to know how many do except ask17:27
elfyok 17:28
elfynot that bothered by it - just if there was an easy way to see how many times a ppa package gets downloaded17:28
elfyknome: re the -gnome attachment works for me - but if we change package testing then the end needs to go17:30
knomeyep17:30
knomewell17:31
knomelet me read it again17:31
knomei would say change it to:17:31
knomeCalls for package testing sprints will be sent out as required.17:31
knomeand the first paragraph to:17:32
knomeThe QA team can schedule package testing sprints to happen during the cycle between milestone testing to ensure applications that are included in Xubuntu have sufficient amount of testing conducted.17:32
elfys/can/wiil17:33
elfywill even17:33
knomesure17:33
elfybluesabre: so thunar fix does work, just needed a reboot18:42
dkesselbtw this seems to be how to find out download counts of a PPA: http://askubuntu.com/questions/296197/how-to-find-out-the-package-download-count-from-a-ppa19:02
dkessel(have not tried it)19:03
slickymasterWorkbluesabre, following that ping in -offtopic, bug 138984019:26
ubottubug 1389840 in parole (Ubuntu) "parole crashed with SIGSEGV in packspu_VBoxPackSetInjectID()" [Undecided,New] https://launchpad.net/bugs/138984019:26
elfyochosi: sigh ... so somehow I would really like to get to the bottom of this screen blanking issue - which is now present in vivid for me :D20:06
elfyI'm not even sure where to look to see when it's being changed - if there is such a place20:15
ali1234it?20:15
elfysomething is randomly changing the never's I have for blanking in power manager20:16
elfythat20:16
ali1234oh. i thought the "black screen after wake up" thing was back20:17
elfyoh no - not that - this is something that apparently only I see :)20:17
knomeelfy, so if you have fundamentally nothing against my version of the proposal, i'll start to process it further :)20:45
elfywell 20:45
elfyuntil we've got a finite view of what we're going to do with packages then doing the processes page seems a bit premature20:46
knomehow i see it is that the manual testing we do now and the exploratory testing can live side-by-side20:46
knomesince the processes page isn't heavy to change in the bureaucratic level, i'd rather get it updated sooner than later20:47
elfyrun it by ochosi again please20:48
elfyand we've not made any decisions on what we do with packages - just a discussion with 3 people so far20:49
knomei will, that's partly what i meant with pushing it forward20:49
knome...and the other part was to ask for comments from the team :)20:49
elfyagain20:50
knomeyeah.20:50
Unit193Hmm?20:50
knomeone way to do that is to add it to the meeting agenda, then ask a few questions, and so. i'll see what we'll have to do :)20:51
elfyknome: well I'm not likely to be about for meetings till either pleia2 or I call one as we usually do them later in the day20:51
knomei can do one later in the day when it's my turn20:52
knomethat's the one after the next one.20:52
elfyknome: if you can mail me the one with the changes re packages too please20:53
knomesec20:53
knomedone20:54
elfyta :)20:54
Unit193So we're going with general rules/guidelines, and punting the support over to #ubuntu+1 when it's more of a core problem?  One downside will be known issues for release+1 in #ubuntu+1, but unknown thus takes longer to identify them in #xubuntu.21:02
knomewhat i was thinking because there was so little feedback...21:03
knomewhat about just supporting +1 everywhere starting from beta1?21:03
elfyUnit193: no idea what we're going to do - just no-one cares enough to say anything so ... 21:03
knomeit isn't like there are dozens of requests every day21:03
knomeand nobody wasn't really negative about any of the options21:03
Unit193knome: In here will make reading scrollback a pain, though.21:03
Unit193Yeah I was for in #xubuntu after b1 personally.21:04
knomewell people who are around handle it21:04
knomeor if they don't know the answer, tell people to ask again after n hours21:04
elfyknome: replied with a small addition21:06
knomecheers21:06
knomei'll look at that once i'm back21:07
knomethat said, have fun and bbl -21:07
knome->21:07
dkesselmeh... xfce4-appfinder can't be tested using autopilot. gtk2 apps are not supported21:41
elfydkessel: oh - sorry thought you were aware of that - I'm bad :(21:42
* dkessel saved that failure on the wiki page and on trello21:45
dkesseli am going to sort gtk2 out of the suggested tests list on http://pad.ubuntu.com/xubuntu-qa-v-autopilot21:47
elfywhy not try something like catfish21:47
dkesselnow catfish is on top of the list ;)21:50
dkesselbasically every row at https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Utopic/Autopilot for GTK2 apps claiming autopilot support is wrong21:51
elfydkessel: possibly - that was built from information from 2 or 3 cycles ago 21:52
Unit193de.po   69.2214%, es.po   96.9586%, fi.po   100%, fr.po   71.7762%, pt.po   100%, ru.po   66.18%22:36
slickymasterGridCub, can you please do one last effort so es.po gets to be 100%, pretty please?22:37
slickymasterdkessel, even though I know you've been caught up with autopilot, can't you manage to spare a few minutes/day to increment the value of de.po?22:38
slickymasterUnit193, thanks for those stats22:39
Unit193slickymaster: Heh, sure.  We've got a while yet, and strings will change though.22:39
Unit193Since the pot file hasn't been updated recently.22:39
slickymasteryeah, just yesterday I pushed a all new sub-section22:39
Unit193Next commit/merge, please update?22:39
dkesselslickymaster: i really want to get the "de" translation in, too ;)22:40
slickymasterok22:40
Unit193DE and RU are my hope. :P22:40
slickymasterI know dkessel, just poking you a bit so it won't get submerged under autopilot 22:40
slickymasterUnit193, I will update. I should had done it yesterday. My bad :P22:41
Unit193./scripts/get-pot.sh22:42
* slickymaster doesn't have the slightest idea of who might be working on the RU.po22:42
slickymasteryeah, I know Unit193. It was pure forgetfulness :(22:43
Unit193slickymaster: Nono, that's fine.  Does LP do the merges, or do we/I/you need to?22:43
slickymasterI think LP does them22:43
slickymasterbut not 100% sure of it22:44
slickymasterI'll ask the finnish guy Unit193 22:44
slickymaster:)22:44
Unit193I'd bet it does.22:45
slickymasterknome ^^22:45
slickymasterthat's also my idea Unit19322:46
knomeyeah, LP handles the merges22:50
slickymasterUnit193, updated. Pushed up to revision 274.22:52
dkesselbluesabre: I filed bug #1389896 . fixing it would help with reliable autopilot testing22:53
ubottubug 1389896 in Catfish "Test support: IDs of GUI elements should be unique" [Undecided,New] https://launchpad.net/bugs/138989622:53
dkesselgood night22:53
Unit193Alrighty.22:53
slickymasternighty dkessel 22:55
bluesabredkessel: cool, didn't know that anybody needed that... will fix and commit shortly, with a planned catfish release something in the near future23:09
slickymasterbah PT.po is now down to 97% :P23:16

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