Times are UTC Toggle Colours
00:17:06 *** Webster has joined #openttdcoop.devzone 08:22:40 <Ammler> I guess, we need to disable ogfx-trains until we find a working solution 08:27:13 <planetmaker> hm, ok 08:34:30 <Ammler> and about Brot6, maybe it might be better to use webster for RSS-Feeds 08:35:02 <Ammler> and if possible also to enable shell access... 08:36:04 <Ammler> @rss 08:36:05 <Webster> Ammler: (rss <url> [<number of headlines>]) -- Gets the title components of the given RSS feed. If <number of headlines> is given, return only that many headlines. 08:37:22 <planetmaker> shell access? 08:38:09 <Ammler> well, the abibility to push messages from console 08:38:32 <Ammler> you know something about DorpsGek or shall I ask Truebrain directly? 08:38:51 <planetmaker> I don't know any details or its setup. I never looked at it 08:39:21 <Ammler> afaik, it does have this ability in .notic 08:39:22 <Ammler> e 08:39:57 <planetmaker> well, dorpsgek / webster could something like that via some plug-ins probably 08:40:29 <Ammler> yep, I assume so quite much, or else TB/RB could hopefully provide a "howto" :-) 08:43:41 <planetmaker> probably TB 08:43:56 <planetmaker> Don't hope to get hold of Rb in the next weeks 08:50:23 <Ammler> yeah, I will try to reach TB this evening... 09:20:09 *** Xotic750 has joined #openttdcoop.devzone 09:26:38 <planetmaker> hi Xotic750 09:27:00 <Xotic750> hi there 09:32:33 <Xotic750> still no nightly builds then? 09:33:08 <planetmaker> the repo is too big 09:33:47 <planetmaker> we need to re-organize, re-structure or re-think the way stuff is handled 09:34:31 <planetmaker> it basically breaks many assumptions the CF and the layout of the service (ressources) was setup to serve 09:35:09 <Xotic750> I think moving the sources to a sub-repo is easiest 09:36:00 <planetmaker> probably... though the technical definition of 'subrepo' would not mean that the checkout size decreases. Technically we probably rather want a separate one 09:36:41 <Xotic750> does it not work the same as with GIT? 09:36:47 <planetmaker> nope 09:36:50 <Xotic750> only get pulled if recursed 09:36:58 <Xotic750> hmm, ok 09:38:09 <Xotic750> a seperate repo is no problem for me 09:38:10 <planetmaker> a sub repo is a separate repo. Whose state is recorded in the main repo. Thus upon checkout of the main repo, you get both repos with a certain revision to be checked out in the subrepo 09:39:36 <planetmaker> I guess we should go for that. And only the final sprites in the repo which creates the grf 09:40:09 <Xotic750> sure, no problem. When are you thinking of doing it? 09:40:47 <Xotic750> or not a move, just delete and upload to the new? 09:40:50 <planetmaker> hm, what about now? :-P A new repo is quickly created. The problem is re-creating the existing repo to a state that it is (easier) handled 09:41:20 <Xotic750> I am here now, so that's fine 09:41:26 <planetmaker> My suggestion is to a) start a new "working repo" for the graphics now. That ensures that you can continue as is 09:41:48 <planetmaker> b) you commit results to the existing ogfx-trains repo (if applicable) 09:41:58 <Xotic750> ok, well I have some graphics rendering but should be done soon 09:41:58 <planetmaker> results as in sprites as they're going to be used 09:42:24 <planetmaker> and c) I'll try to re-create the ogfx-trains repo such that it gets smaller (and possibly archive the existing as to not loose history) 09:42:57 <Xotic750> ok, well it will be an hour or 2 before things are finished here 09:43:23 <Xotic750> then I can commit everything and stop 09:43:39 <Xotic750> then I will be ready to write everything to a new repo 09:45:41 <Xotic750> I guess we can add an ignore for sprite_sources/blender so that I can clone the new repo to the same place, then no need to change scripts? 09:48:14 <planetmaker> repo name "OpenGFX+ Trains renders"? 09:48:30 <Xotic750> fine 09:48:37 <planetmaker> I'd create an empty repo and you choose whatever dir structure suits you. So probably the same as now 09:49:03 <planetmaker> btw, you can create new projects on the devzone yourself. You're a project manager, thus you're allowed to create any project as you wish :-) 09:49:13 <Xotic750> aha, ok 09:49:24 <planetmaker> But I'm about to hit 'create' on this one now 09:50:14 <planetmaker> the important thing you usually want to check is 'repository' - then it's created server-side automatically 09:51:19 <planetmaker> it may take now a few minutes before the repo is created (up to 7) 09:52:35 <Xotic750> no problem, I have a post process running on 6 new models, that takes a little while :) 10:11:04 <Xotic750> post-processing is nearly done 10:11:15 <Xotic750> then I will do a final commit of everything as is 10:11:33 <Xotic750> and then I will give the new repo a go and try to establish everything 10:17:02 <Xotic750> ok, finat commit and push is done, everything is backed up 10:18:13 <planetmaker> I'd just use it as 'storage' for render, not the full newgrf with everything. That'd be doubling things 10:19:27 <Xotic750> I was going to take the whole blender directory? 10:19:49 <planetmaker> yep 10:28:56 <Ammler> as first, the render images should not be part of history, however you split it, (sorry didn't read the whole back yet) 10:29:17 <planetmaker> Ammler: it's a matter of how workflow goes... 10:29:56 <planetmaker> Xotic750: needs something convenient to pass these intermediate results between stages. And keeping a timestamp so to say on them to make sure he's working on the latest version of it 10:31:36 <Ammler> well, you can do that in a seperate repo and create a tar after every build 10:31:55 <Ammler> this tar only will have the current version 10:32:51 <Ammler> this tar is hosted on bundls.o.o 10:33:11 <Ammler> and can be fetched via wget for building 10:33:39 <Ammler> ogfx-trains-images 10:33:54 <Ammler> or sprites or whatever :-P 10:34:12 <Ammler> such a workflow would be supported by the cf 10:35:30 <Ammler> hmm, the CF could also wget a directory if you don't want to tar, hmm, maybe we could wget the latest version from th hg repo 10:36:12 <planetmaker> Ammler: the sprites as used by the grf should be in the repo 10:36:18 <planetmaker> must be actually. Or it hardly could be built 10:36:28 <Ammler> no 10:36:37 <planetmaker> So you want a build time of 3 days? 10:36:40 <planetmaker> and build it daily? 10:36:41 <Ammler> you should be able to render it with blender, aren't you? 10:36:56 <Ammler> I think, this is what Xotic750 does on the special vps 10:37:02 <planetmaker> no 10:37:17 <planetmaker> he renders single vehicles or a few. Not everything at once 10:37:24 <Ammler> you didn't read :-( 10:37:33 <planetmaker> please correct me, when I'm wrong, Xotic750 10:37:49 <Ammler> of course, there is a snapshot or repo or whatever with the rendered images 10:37:53 <Ammler> just not in the same repo 10:38:00 <Xotic750> I render just the vehicles that need rendering, mostly small runs of 6 or so 10:38:06 <planetmaker> Ammler: the full build from render sourced to grf takes long. Even with all sprites in place it takes an hour to build 10:38:16 <Xotic750> occasionally if I have a library change then I need a complete re-render 10:40:48 <Ammler> planetmaker: the time is not the issue, he size is, or because of the size i needs that long 10:41:01 <planetmaker> Just nmlc needs that long to build the grf 10:41:18 <Ammler> I think around half of the time it is simple disk io 10:41:51 <planetmaker> sorry, would like to continue. But work calls 10:42:34 <Ammler> well, we shoul all think about it, maybe we got an idea, but for now I would like to disable nighly for ogfx-train and run it manually afterwards 10:44:00 <Ammler> and planetmaker, please use the screen on hg ssh 11:55:01 <planetmaker> Ammler, for what? :-) 11:57:55 <Xotic750> planetmaker: all is done now, so you can go ahead and archive the whole blender directory, or whatever you need to do to make things smaller 12:00:36 <planetmaker> aye, nice :-) 12:01:05 <planetmaker> Xotic750, just continue to use the existing repo for the resulting sprites. I probably won't find time today to look at how to modify the repo... 12:01:22 <planetmaker> I might just create a new one scripted with the existing commits in the old. Or something like that 12:02:07 <Xotic750> yep, I will put blends and renders in the new repo and resultant sprites in ogfx-trains 12:02:53 <Xotic750> and hopefully we can get some nightlies going again :) 12:08:42 <planetmaker> yes, believe me, I'm very much interested. Just my time currently is more restricted somewhat than I wished for 12:09:03 <planetmaker> (and the more happy I'm actually in you taking here some lead initiative :-) ) 12:12:48 <Xotic750> just doing what I can, and hopefully not too many mistakes :) 12:16:48 <planetmaker> well. what's a 'mistake'? A serious mistake would only be to physically delete the repo or break the VMs hard ;-) 12:17:22 <planetmaker> Anything else might from one POV or another be considered "not nice" but can always be recovered. 12:22:33 <Xotic750> I've created a bitbucket backup repo, https://bitbucket.org/Xotic750/ogfx-trains-render 12:22:36 <Webster> Title: Xotic750 / ogfx-trains-render / overview Bitbucket (at bitbucket.org) 12:23:13 <Xotic750> and hopefully the auto backup will work for that like it does for ogfx-trains 12:23:27 <Xotic750> again, you have admin rights 12:23:34 <planetmaker> k, thx :-) 16:06:37 *** Zuu has joined #openttdcoop.devzone 16:10:59 *** ODM has joined #openttdcoop.devzone 16:30:40 *** LordAro has joined #openttdcoop.devzone 16:35:38 *** frosch123 has joined #openttdcoop.devzone 17:21:03 *** Xotic750_ has joined #openttdcoop.devzone 18:56:56 <frosch123> http://dev.openttdcoop.org/issues/4014 <- michi_cc: didn't you have a patch for that? 18:57:48 <michi_cc> frosch123: http://dev.openttdcoop.org/projects/grfcodec/repository/revisions/d58724cc2169, i.e. update 18:59:09 <frosch123> se, we can just close that ask? 18:59:52 <michi_cc> Yes, it is E_STABLE_IS_STALE :) 21:26:46 *** frosch123 has quit IRC 21:37:43 *** Zuu has quit IRC 21:43:53 *** ODM has quit IRC 22:02:53 *** Xotic750_ has quit IRC 22:42:12 *** LordAro has quit IRC