00:05 | andygraybeal_ has joined IRC (andygraybeal_!~andy@h44.218.213.151.dynamic.ip.windstream.net) | |
00:07 | MastaaK has left IRC (MastaaK!c3dd3a29@gateway/web/freenode/ip.195.221.58.41, Ping timeout: 245 seconds) | |
00:09 | sep has left IRC (sep!~sep@40.211.jostedal.no, Ping timeout: 252 seconds) | |
00:24 | Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 252 seconds) | |
00:43 | knipwim_ has joined IRC (knipwim_!~wim@ip4da83870.direct-adsl.nl) | |
00:46 | knipwim has left IRC (knipwim!~wim@ip4da83870.direct-adsl.nl, Ping timeout: 265 seconds) | |
01:23 | PhoenixSTF has left IRC (PhoenixSTF!~rudi@78.29.134.164, Quit: Leaving) | |
02:10 | andygraybeal_ has left IRC (andygraybeal_!~andy@h44.218.213.151.dynamic.ip.windstream.net, Ping timeout: 255 seconds) | |
02:14 | vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving) | |
02:16 | ball has joined IRC (ball!~ball@c-24-14-239-108.hsd1.il.comcast.net) | |
04:58 | sha_ has left IRC (sha_!~sha@e177171024.adsl.alicedsl.de, Ping timeout: 252 seconds) | |
05:00 | sha has joined IRC (sha!~sha@e177172226.adsl.alicedsl.de) | |
05:49 | mah454 has joined IRC (mah454!~quassel@2.191.10.102) | |
06:09 | mah454 has left IRC (mah454!~quassel@2.191.10.102, Remote host closed the connection) | |
06:34 | ltspuser_26 has joined IRC (ltspuser_26!4bca231b@gateway/web/freenode/ip.75.202.35.27) | |
06:35 | <ltspuser_26> hi eveeyone
| |
06:49 | ltspuser_26 has left IRC (ltspuser_26!4bca231b@gateway/web/freenode/ip.75.202.35.27, Ping timeout: 245 seconds) | |
07:00 | * ball waves | |
07:55 | komunista has joined IRC (komunista!~slavko@adsl-195-168-235-217.dynamic.nextra.sk) | |
08:32 | knipwim_ is now known as knipwim | |
08:58 | bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) | |
08:59 | mah454 has joined IRC (mah454!~quassel@2.191.10.102) | |
09:02 | mah454 has left IRC (mah454!~quassel@2.191.10.102, Read error: Connection reset by peer) | |
09:04 | mah454 has joined IRC (mah454!~quassel@2.191.10.102) | |
09:13 | Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas) | |
09:17 | ball has left IRC (ball!~ball@c-24-14-239-108.hsd1.il.comcast.net, Quit: Sleep) | |
09:53 | mah454 has left IRC (mah454!~quassel@2.191.10.102, Ping timeout: 272 seconds) | |
09:53 | mah454 has joined IRC (mah454!~quassel@2.191.10.102) | |
09:57 | yalu has left IRC (yalu!~yalu@91.180.85.133, Ping timeout: 244 seconds) | |
09:59 | yalu has joined IRC (yalu!~yalu@91.180.93.68) | |
10:23 | mikkel has joined IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk) | |
10:28 | markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it) | |
10:32 | <knipwim> Phantomas: when installing epoptes from source, using the setup.py, can i install the server separate from the client and vice versa?
| |
10:33 | mah454_ has joined IRC (mah454_!~quassel@2.191.10.102) | |
10:33 | mah454 has left IRC (mah454!~quassel@2.191.10.102, Ping timeout: 272 seconds) | |
10:44 | mah454_ has left IRC (mah454_!~quassel@2.191.10.102, Remote host closed the connection) | |
10:45 | Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 255 seconds) | |
11:05 | <markit> hi knipwim :)
| |
11:05 | Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas) | |
11:07 | <knipwim> hey markit
| |
11:07 | having a good weekend?
| |
11:07 | <markit> more or less... I planned to do a LOT of stuff, but was able to acomplish only.. 1% ;P
| |
11:07 | what about you?
| |
11:08 | knipwim: what distro do you use that does not have epoptes packaged?
| |
11:08 | <knipwim> easy going, have cleaned up a lot of old files mostly
| |
11:08 | but ltsp stuff
| |
11:08 | erm, s/but/bit/
| |
11:09 | Gentoo
| |
11:14 | Phantomas: when installing epoptes from source, using the setup.py, can i install the server separate from the client and vice versa?
| |
11:34 | <Phantomas> hey knipwim
| |
11:35 | Uhm, we don't have a proper setup.py yet :(
| |
11:37 | (sorry for my late answer)
| |
11:43 | knipwim: Aren't you the epoptes packager for Gentoo? Do you have any issues? I'll be glad to make a proper setup.py (at last) if it is a problem.
| |
11:46 | patches are welcome too :)
| |
12:00 | <markit> hi Phantomas :)
| |
12:27 | <Phantomas> hey markit!
| |
12:36 | vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 252 seconds) | |
12:36 | vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi) | |
12:41 | sha has left IRC (sha!~sha@e177172226.adsl.alicedsl.de, Remote host closed the connection) | |
12:43 | <markit> Phantomas: any udated/reliable roadmap for Epoptes? I've asked alkisg about block clients web navigation... easy to do once you can add custom actions to epoptes (name, description, code to execute, i.e. run a script or run a iptables rule)
| |
12:46 | <knipwim> Phantomas: i want to be able to build a separate client package and server package
| |
12:46 | i'm not really familiar with distutils, but can you specify make-like build targets
| |
12:47 | for example, python setup.py install client
| |
12:47 | installing only the epoptes-client stuff
| |
12:55 | komunista has left IRC (komunista!~slavko@adsl-195-168-235-217.dynamic.nextra.sk, Ping timeout: 272 seconds) | |
13:02 | <Phantomas> markit: yes, internet blocking is in the plans, I can't tell you ETA though.
| |
13:04 | <knipwim> Phantomas: i think i found a way, not use the distutils for the client part at all
| |
13:04 | and patch the client part from the setup.py before installing the server part
| |
13:05 | <Phantomas> knipwim: I'm not very familiar with distutils either, maybe a second setup.py for the client would be a good idea
| |
13:05 | knipwim: good!
| |
13:09 | markit: The features included in the next version will be student broadcasting, zoom bar for the thumbnails, better broadcasting performance on multithreaded CPUs, and a "lab health checking" tool (network speed benchmarks, clients' capabilities and others) :)
| |
13:10 | maybe we will have a mini addon system too where you could make clients execute custom scripts from the epoptes interface
| |
13:11 | <markit> Phantomas: wow, good news, especially (for me) the "lab health checking"!!!
| |
13:12 | the custom scripts is, I think, all what is needed to expand Epoptes functionality at low level stuff
| |
13:12 | neverless I think that the "block navigation" is something really widly usefull, so should be integrated someway
| |
13:13 | wondering if can work only for fat clients...
| |
13:13 | <Phantomas> yes it should, I don't know if it will be in the next version though :-\ We'll see!
| |
13:15 | btw brace yourself, new strings waiting for translation are coming :P (soon...)
| |
13:15 | <markit> oh, please tell me with email, I don't go to epoptes site very often
| |
13:15 | <Phantomas> I will
| |
13:15 | <markit> to be sincere, should be automatically managed by the translation backend, OMHO
| |
13:16 | if something is the translator, and new translation is needed, should be notified with email
| |
13:16 | btw, what are your (you and alkisg) goals at the moment? what are you working on?
| |
13:16 | (IF you are developing, remember that your university study must have higher priority)
| |
13:23 | <Phantomas> Alkis is focused on LTSP currently!
| |
13:23 | I am working on some of the above mentioned features and sch-scripts mainly
| |
13:25 | <markit> ok, thanks and keep the good work. Would love that the Epoptes site will have an updated roadmap
| |
13:27 | andygraybeal_ has joined IRC (andygraybeal_!~andy@h44.218.213.151.dynamic.ip.windstream.net) | |
13:32 | <Phantomas> knipwim: You were installing both server and client with your packages before?
| |
14:18 | PhoenixSTF has joined IRC (PhoenixSTF!~rudi@78.29.134.164) | |
14:30 | PhoenixSTF has left IRC (PhoenixSTF!~rudi@78.29.134.164, Read error: Connection timed out) | |
14:31 | PhoenixSTF has joined IRC (PhoenixSTF!~rudi@78.29.134.164) | |
14:31 | <knipwim> no
| |
14:32 | these would be the first packages
| |
14:48 | bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 264 seconds) | |
15:36 | <knipwim> Phantomas: you have any idea what this means? ValueError: illegal provides specification: 'build-2.7.lib.epoptes'
| |
15:45 | hmm
| |
15:45 | never mind, that's a Gentoo build problem
| |
16:01 | i get the error because gentoo first does a:
| |
16:02 | python2.7 setup.py build -b build-2.7
| |
16:02 | followed by a:
| |
16:02 | python2.7 setup.py build -b build-2.7 install --no-compile
| |
16:21 | komunista has joined IRC (komunista!~slavko@adsl-195-168-235-217.dynamic.nextra.sk) | |
16:52 | vagrantc has joined IRC (vagrantc!~vagrant@c-98-232-129-196.hsd1.or.comcast.net) | |
16:52 | vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc) | |
17:11 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
17:46 | mikkel has left IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk, Quit: Leaving) | |
17:47 | Parker955_Away has left IRC (Parker955_Away!~parker@74.112.203.151, Ping timeout: 245 seconds) | |
17:47 | <vagrantc> alkisg: never did get a chance to chat about the translation stuff
| |
17:48 | alkisg: but i looked over some docs on launchpad to try and figure it out for myself...
| |
17:48 | alkisg: and updated the existing translations
| |
17:48 | <alkisg> vagrantc: Phantomas is the expert on configuring launchpad for translations
| |
17:48 | * vagrantc waves to Phantomas | |
17:49 | <alkisg> vagrantc: you agree to moving the translations to launchpad, right?
| |
17:49 | Should launchpad commit automatically on our branch, or only on request?
| |
17:49 | <vagrantc> alkisg: yes, i think it would be a good thing to do- i haven't been able to keep up with it manually very well.
| |
17:50 | alkisg: if it doesn't happen automatically, we'll forget... so i think it should happen automatically :)
| |
17:50 | it doesn't interfere with manually updated translations, right?
| |
17:50 | <alkisg> Sure - we just might have a few more commits than usual, e.g. check the epoptes trunk for an example
| |
17:51 | Not unless there's a conflict
| |
17:51 | <vagrantc> well, if it commits directly, i'm hoping there wouldn't be any conflicts... i.e. it would use -trunk
| |
17:52 | <alkisg> Suppose you have version A of a translation
| |
17:52 | A person gets that and updates it to B. It's not committed yet.
| |
17:52 | <vagrantc> right
| |
17:52 | <alkisg> Another person translates version A in launchpad, and immediately "commits" version C.
| |
17:53 | When the first person mails you version B and you commit it, there's a conflict there
| |
17:53 | <vagrantc> that's only standard vcs stuff
| |
17:54 | <alkisg> Sure, if you're going to do the merge manually, I don't see any problems
| |
17:54 | But in general I'd tell the people to upload the .po to launchpad themselves :D
| |
17:54 | <vagrantc> sure
| |
17:54 | <alkisg> ...and if at some point we have regular translators, we can create an ltsp-translators group
| |
17:55 | And only give access to them
| |
17:55 | vagrantc: how is the .pot file updated now?
| |
17:55 | * vagrantc wondered if launchpad still obliterates the comments and headers for translations | |
17:55 | <alkisg> With mkdist?
| |
17:56 | <vagrantc> alkisg: i run it manually... there's a script in the ldm-trunk that i use.
| |
17:56 | (and just symlink into ltsp-trunk)
| |
17:56 | <alkisg> Ah. Cool, let's keep doing that.
| |
17:56 | It causes less translations commits
| |
17:56 | <vagrantc> although basically the translations end up always being one release behind.
| |
17:57 | <alkisg> If we run that e.g. 2 months before releases, it would be pretty much ok...
| |
17:57 | <vagrantc> it grabs it out of release.conf, so it's always whatever was previously released.
| |
17:57 | it could probably use ${version}+
| |
17:58 | <alkisg> vagrantc: do you have time to try to do the translations configuration now?
| |
17:58 | Phantomas ^ ?
| |
17:58 | <vagrantc> alkisg: not till tomorrow
| |
17:59 | <alkisg> ok
| |
17:59 | <vagrantc> or maybe ${version}+${date}
| |
17:59 | most translators also don't update those values in the .po files, in my experience...
| |
18:01 | <alkisg> vagrantc: ah, and we should maintain the https://launchpad.net/ltsp page a bit...
| |
18:01 | licenses: I don't know yet
| |
18:02 | Series: main /ubuntu
| |
18:02 | ...ubuntu?! What for?!
| |
18:02 | LTSP main series is the current focus of development
| |
18:02 | ...in CVS?! :D
| |
18:02 | Etc etc
| |
18:14 | <vagrantc> heh
| |
18:27 | <alkisg> Meh somehow I still don't have access there
| |
18:28 | The "driver" probably isn't enough, only the "maintainer" has access
| |
18:29 | sbalneav: around? do you have access e.g. in this page? https://launchpad.net/ltsp/+edit
| |
18:52 | mcfloppy has left IRC (mcfloppy!~kvirc@95-88-40-95-dynip.superkabel.de, Ping timeout: 248 seconds) | |
19:00 | Parker955_Away has joined IRC (Parker955_Away!~parker@74.112.203.151) | |
19:04 | vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving) | |
19:05 | muppis_ has joined IRC (muppis_!muppis@viuhka.fi) | |
19:06 | <knipwim> alkisg: i tried the configuration of the translations
| |
19:07 | mainly we have to connect a branch to a series
| |
19:07 | because translations are connected to series
| |
19:09 | muppis has left IRC (muppis!muppis@viuhka.fi, *.net *.split) | |
19:09 | monteslu has left IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net, *.net *.split) | |
19:11 | <knipwim> and i also cannot do that, if we want to
| |
19:16 | monteslu has joined IRC (monteslu!~monteslu@68.109.174.213) | |
19:43 | bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) | |
20:09 | vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) | |
20:09 | vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc) | |
20:17 | <alkisg> knipwim: I'll mail jammcq and tell him to give me maintainance access to the launchpad ltsp page, so that we can clean up all of it
| |
20:17 | Series, branches, translations etc
| |
20:22 | <knipwim> i made a topic of it for next meeting
| |
20:22 | apparently we can also make releases on a series
| |
20:22 | which you can download
| |
20:23 | xet7 has left IRC (xet7!~xet7@a91-156-233-189.elisa-laajakaista.fi, Remote host closed the connection) | |
20:30 | jammcq has joined IRC (jammcq!~jam@c-98-209-67-190.hsd1.mi.comcast.net) | |
20:30 | <jammcq> hey friends
| |
20:30 | alkisg: ping
| |
20:30 | <alkisg> Hey jammcq
| |
20:30 | <jammcq> got your email
| |
20:31 | * vagrantc waves to jammcq | |
20:31 | <vagrantc> jammcq: warren was looking for you the other day
| |
20:31 | * alkisg was about to leave, but since everyone is here... let's do some work! | |
20:31 | * vagrantc isn't really here. | |
20:31 | <jammcq> vagrantc: yeah, I saw his message too late
| |
20:31 | alkisg: i'm lookin g athte +edit-people screen
| |
20:32 | do I just change the Mainter to be 'ltsp-drivers' ?
| |
20:32 | <alkisg> Yup
| |
20:32 | I think that'll be enough
| |
20:32 | <knipwim> alkisg: you intend to connect ltsp-trunk to the main series?
| |
20:32 | <jammcq> alkisg: done
| |
20:32 | <alkisg> jammcq: yup, got full access now, ty
| |
20:33 | <jammcq> excellent
| |
20:33 | <alkisg> knipwim: I think we should delete the main series
| |
20:33 | But let's take it slowly...
| |
20:33 | I'll start with the logo :P
| |
20:33 | <jammcq> vagrantc: if I wanted to give Debian LTSP a try, which debian should I install?
| |
20:33 | <knipwim> :)
| |
20:34 | alkisg: i was looking at the series for https://launchpad.net/schooltool
| |
20:34 | <alkisg> knipwim: check also launchpad.net/epoptes
| |
20:34 | We have translations, series etc configured there
| |
20:34 | * Phantomas back, hey vagrantc :) | |
20:34 | <Phantomas> alkisg: series would be used for translating LDM
| |
20:35 | <knipwim> alkisg: the difference, is epoptes has actually one development branch
| |
20:35 | we have ltsp-docs. ltspfs, ldm-trunk and ltsp-trunk
| |
20:35 | following launchpad logic, these should be different project altogether
| |
20:35 | <alkisg> Phantomas: as a hack around launchpad inefficiencies?
| |
20:36 | <vagrantc> jammcq: debian wheezy, although there are some important bugfixes that won't get there for another 6 days or so
| |
20:36 | <Phantomas> as a quick way to achieve what you would achieve by using different projects
| |
20:36 | <vagrantc> jammcq: wheezy's going to release any day now- i wouldn't bother with the old stable release.
| |
20:36 | <Phantomas> and a project group named LTSP
| |
20:36 | <knipwim> Phantomas: what's a project group?
| |
20:36 | <jammcq> ah cool
| |
20:36 | <alkisg> vagrantc: ltsp license: gpl v2, right?
| |
20:37 | <jammcq> does that mean that wheezy will become the new 'stable' ?
| |
20:37 | <Phantomas> knipwim: eg: https://launchpad.net/mozilla
| |
20:37 | <alkisg> We don't have anything gpl 3 etc, correct?
| |
20:37 | <vagrantc> alkisg: either v2 or v2+ generally
| |
20:37 | <alkisg> OK
| |
20:37 | <vagrantc> alkisg: i'd prefer v2+
| |
20:37 | <alkisg> Not listed there
| |
20:37 | <vagrantc> if we're setting new standards...
| |
20:37 | <alkisg> (in launchpad)
| |
20:37 | <Hyperbyte> Hey everyone. :)
| |
20:37 | <alkisg> Apache Licence view licence GNU Affero GPL v3 view licence GNU LGPL v2.1 view licence Simplified BSD Licence view licence GNU GPL v2 view licence GNU LGPL v3 view licence Creative Commons - No Rights Reserved view licence GNU GPL v3 view licence
| |
20:37 | Hi Hyperbyte
| |
20:40 | jammcq: do you have any links to the logo handy?
| |
20:40 | <knipwim> alkisg: epoptes is mostly developed in the trunk now
| |
20:41 | alkisg: i can get the one from the wiki
| |
20:41 | <jammcq> alkisg: hmm, I don't
| |
20:41 | <alkisg> knipwim: the one without the ltsp text
| |
20:41 | <jammcq> that's a logo the Diskless guys came up with
| |
20:41 | <alkisg> We want 14x14 and 64x64, I can resize existing ones
| |
20:41 | And a 192x192 one... this one can probably have the ltsp text too
| |
20:42 | <knipwim> ok, i'll make those
| |
20:46 | <alkisg> knipwim: I put some quick ones, if you get better ones I'll replace them
| |
20:48 | Phantomas, knipwim: do we need a project group for ltsp, with seperate projects for ldm, ltspfs etc?
| |
20:48 | <Phantomas> About translations, you can have multiple pot files in a branch and rosetta will recognize this and make them all available for translation. I am not sure if this is true for having multiple pot files in different branches, we should test it.
| |
20:48 | <alkisg> Or that's stretching it too far?
| |
20:50 | <Phantomas> for example we could translate both epoptes and epoptes-client with different POTs (they are both in the same branch)
| |
20:50 | <knipwim> our project group is now ltsp-upstream ?
| |
20:50 | <Phantomas> no, you don't have a project group
| |
20:50 | <knipwim> Phantomas: i don't think multiple branches will work
| |
20:50 | so a project group doesn't control access?
| |
20:51 | <Phantomas> your team is ltsp-upstream
| |
20:51 | vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 246 seconds) | |
20:51 | <Phantomas> which owns the ltsp project
| |
20:51 | instead it could own the LTSP project group
| |
20:52 | which would contain ltsp ldm etc
| |
20:52 | but maybe as alkisg said that's stretching it too far
| |
20:52 | <alkisg> stgraber, ogra_, vagrantc, knipwim, Phantomas: anyone knows why do we need an "ubuntu" series for ltsp? https://launchpad.net/ltsp/ubuntu
| |
20:53 | bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds) | |
20:53 | <Phantomas> different code in ubuntu branch than in trunk?
| |
20:53 | <alkisg> Phantomas: I think someone was experimenting with launchpad... I don't think the ubuntu series is actually used
| |
20:54 | <stgraber> alkisg: doesn't seem useful
| |
20:54 | <alkisg> ty
| |
20:54 | Deleting...
| |
20:54 | adrianorg_ has joined IRC (adrianorg_!~adrianorg@177.132.218.134) | |
20:54 | <Phantomas> asked in #launchpad
| |
20:55 | about translating different branches of a project
| |
20:55 | <alkisg> Ouch, can't delete the ubuntu series, it's linked to packages: https://launchpad.net/ltsp/+packages
| |
20:56 | Maybe because xxx-0ubuntu1 packages exist for ltsp
| |
20:58 | ...the ubuntu series is used for ltsp, and the main series for ldm/ltspfs... nope, that doesn't make sense... :-/
| |
21:01 | <Phantomas> https://translations.launchpad.net/openshot
| |
21:01 | It uses series to achieve the same thing (openshot and openshot-docs)
| |
21:01 | (the same thing as we want)
| |
21:02 | <alkisg> Phantomas: so we'd want 3 series, one for ltsp, one for ldm, and one for ltspfs?
| |
21:02 | And maybe even one for ltsp-docs?
| |
21:03 | All those are on different branches, btw...
| |
21:03 | <Phantomas> alkisg: yes, that's the problem :)
| |
21:03 | yep 3 series would do...
| |
21:03 | (or separate projects)
| |
21:04 | <knipwim> i guess so too, separate series, and all are used as trunk
| |
21:05 | <alkisg> Phantomas, knipwim: and what about the "focus of translation"?
| |
21:05 | <Phantomas> In openshot they even use a separate branch for translations to keep their logs clean, but that wouldn't allow translating different version series, I think
| |
21:05 | <alkisg> We don't want to only "focus on ltsp"....
| |
21:05 | <Phantomas> alkisg: you leave it unset
| |
21:06 | <alkisg> Phantomas: I mean, isn't this idea a hack? Wouldn't it be much cleaner to have 3 separate projects?
| |
21:06 | <Phantomas> It is a shortcut, yes
| |
21:07 | <alkisg> If using launchpad that way is "supported", sure, I'm in favor of maintaining less projects :D
| |
21:07 | <knipwim> alkisg: for translations we really only need ltsp-trunk
| |
21:07 | <alkisg> knipwim: not ldm?
| |
21:07 | <knipwim> if we retire ldm for lightdm
| |
21:07 | then ldm is deprecated anyway
| |
21:08 | <alkisg> You have a point there...
| |
21:08 | Agreed then, different series for now, not registering new projects
| |
21:09 | <Phantomas> or you could merge all branches in 1 :P :P
| |
21:09 | <alkisg> So, how about renaming "main" to "ldm", and "ubuntu" to "ltsp"?
| |
21:09 | https://launchpad.net/ltsp/+packages
| |
21:09 | (because that's how they were used up to now)
| |
21:09 | Or, ldm-trunk, and ltsp-trunk
| |
21:10 | <knipwim> the ubuntu series isn't connected to a branch right now
| |
21:10 | <alkisg> And neither is main, right?
| |
21:10 | <knipwim> correct
| |
21:11 | <alkisg> So, I'm thinking of renaming them like I said above, and then connecting them to the trunks
| |
21:11 | <knipwim> i was just wondering how the packages are connected to code
| |
21:11 | if the series isn't connected to a branch
| |
21:11 | <alkisg> No idea there
| |
21:11 | https://launchpad.net/ltsp/ubuntu/+ubuntupkg
| |
21:11 | <knipwim> sure, ltsp-trunk and ldm-trunk then
| |
21:12 | <alkisg> Maybe it's just manually declared in launchpad, from the page above
| |
21:12 | Phantomas, vagrantc: do you agree with renaming "main" to "ldm", "ubuntu" to "ltsp", and linking them to their branches?
| |
21:13 | <Phantomas> I think it would be fine.
| |
21:14 | or ltsp-trunk and ldm-trunk as knipwim mentioned
| |
21:15 | (or you were talking about the branch names?)
| |
21:15 | <knipwim> no, the series
| |
21:16 | to be clear the series are connected to trunks
| |
21:16 | <Phantomas> yep
| |
21:16 | <knipwim> perhaps we'll get an ltsp-dev or something
| |
21:16 | ltsp-6
| |
21:17 | <alkisg> Done, ltsp-trunk and ldm-trunk
| |
21:18 | Phantomas, knipwim: moving on to translations?
| |
21:18 | <Phantomas> alkisg: set the development focus to ltsp-trunk
| |
21:18 | <alkisg> Phantomas: ok, why?
| |
21:18 | Didn't you suggest we should leave it unset?
| |
21:19 | <Phantomas> translation focus
| |
21:19 | <alkisg> Ah
| |
21:19 | <Phantomas> seems you can't set development focus to none :-\
| |
21:19 | <knipwim> and our focus is on ltsp
| |
21:19 | <Phantomas> yep
| |
21:20 | or you would get ldm-trunk when doing bzr branch lp:ltsp
| |
21:20 | <alkisg> Done
| |
21:21 | vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving) | |
21:21 | <Phantomas> ok let's go to translations
| |
21:22 | <alkisg> Phantomas, knipwim: so, I've enabled translations, what else?
| |
21:23 | no focus, no group
| |
21:23 | open policy
| |
21:23 | vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) | |
21:23 | vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc) | |
21:23 | <Phantomas> You need to set the import branch and the export branch
| |
21:23 | <knipwim> i'm guessing Import template and translation files
| |
21:24 | <alkisg> https://translations.launchpad.net/ltsp/ltsp-trunk/+translations
| |
21:24 | <Phantomas> https://translations.launchpad.net/ltsp/ltsp-trunk/+translations-settings
| |
21:24 | https://translations.launchpad.net/ltsp/ldm-trunk/+translations-settings
| |
21:25 | (You want automatic import/export right?)
| |
21:25 | <alkisg> Right
| |
21:25 | So, like knipwim said...
| |
21:25 | <Phantomas> ah, yes!
| |
21:27 | <alkisg> Currently not exporting translations to a branch. Choose a target branch.
| |
21:28 | <Phantomas> why?
| |
21:28 | <alkisg> We don't need that, right?
| |
21:28 | If unset, it'll use our main branch... correct?
| |
21:28 | <Phantomas> You don't want rosetta to push translations to your branch?
| |
21:28 | <alkisg> We do, ok, all fine
| |
21:29 | <Phantomas> I don't think it does :-\
| |
21:29 | <knipwim> do we want it automatic the first time?
| |
21:29 | <alkisg> Phantomas: how did we do that in epoptes?
| |
21:29 | knipwim: yes...?
| |
21:29 | Ah, in case it does stupid things?
| |
21:30 | <Phantomas> alkisg: which one? We set the trunk branch as both the export and import branch
| |
21:30 | <knipwim> yes
| |
21:30 | <alkisg> Phantomas: vagrantc said we want the same thing in ltsp too
| |
21:30 | <Phantomas> ok so set the export branch to ltsp-trunk and ldm-trunk respectively
| |
21:31 | and the import branch
| |
21:34 | alkisg: You can ask a one-time import for the first time :)
| |
21:35 | "I speak england very best!" :P s/ask/request/ whatever... :)
| |
21:36 | <alkisg> Phantomas, knipwim, vagrantc: supposedly, all is done... check for anything else and ping me!
| |
21:37 | <Phantomas> alkisg: seems perfect :)
| |
21:37 | https://translations.launchpad.net/ltsp/ltsp-trunk/+lang/el
| |
21:37 | https://translations.launchpad.net/ltsp/ldm-trunk/+lang/el
| |
21:37 | it already imported them!
| |
21:38 | * alkisg is already translating the missing greek strings... :D | |
21:38 | <knipwim> cool guys :)
| |
21:39 | and doing some Dutch strings :)
| |
21:39 | <Phantomas> alkisg: uhm, you should only add a translator credits msgid
| |
21:39 | <alkisg> Phantomas: ah, in the sources?
| |
21:39 | Phantomas: can you give me an example diff?
| |
21:39 | <Phantomas> sure
| |
21:40 | <alkisg> Phantomas: well, I wouldn't mind for a diff for all the .po's... :P :D
| |
21:40 | I hope pushing to the .po's won't conflict with launchpad...
| |
21:42 | <Phantomas> alkisg: you need to include it in your POT generation scripts btw
| |
21:42 | * alkisg saved a .pdf version of https://translations.launchpad.net/ltsp/ltsp-trunk/+pots/ltsp, to compare it in the future with the number/percentages of translations then... | |
21:43 | <alkisg> Phantomas: I'm going to head to bed, if you could file a bug report with a debdiff or something based on ltsp-trunk and ldm-trunk, I'd be much obliged...
| |
21:43 | Or send me a mail
| |
21:43 | ...if you don't want the launchpad karma points :P
| |
21:43 | <Phantomas> haha
| |
21:44 | I'll be a worm in my next life :P
| |
21:44 | <alkisg> ta ta guys
| |
21:44 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
22:15 | <Phantomas> knipwim: About the epoptes bug you reported, do you start epoptes as root?
| |
22:16 | <warren> OK, I emailed folks about training my replacement for Fedora LTSP.
| |
22:17 | komunista has left IRC (komunista!~slavko@adsl-195-168-235-217.dynamic.nextra.sk, Quit: Leaving.) | |
22:17 | <jammcq> warren: hey
| |
22:17 | how's it goin?
| |
22:17 | I just saw the email
| |
22:53 | markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, ) | |