--- Log opened Fri Sep 22 00:00:05 2017
20170922 00:21:27-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 00:21:39-!- stikonas_ [~gentoo@wesnoth/translator/stikonas] has quit [Ping timeout: 252 seconds]
20170922 00:32:52-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 00:32:58-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 01:38:04-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 01:38:12-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 01:47:33-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Quit: Konversation terminated!]
20170922 02:41:17-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 02:41:21-!- vultraz [uid24821@wesnoth/developer/vultraz] has joined #wesnoth-dev
20170922 02:41:24-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 02:42:34-!- irker759 [~irker@uruz.ai0867.net] has quit [Quit: transmission timeout]
20170922 03:04:20-!- JyrkiVesterinen [~JyrkiVest@85-23-197-3.bb.dnainternet.fi] has joined #wesnoth-dev
20170922 03:25:58-!- MalcomX976 [~zmwrl@213.87.129.63] has joined #wesnoth-dev
20170922 03:25:58-!- MalcomX976 [~zmwrl@213.87.129.63] has quit [Excess Flood]
20170922 03:34:46< Necrosporus> If you can use paths such as data/add-on/Addon_Name does it mean that you can access entire userdata directory from addon content?
20170922 03:40:33-!- irker861 [~irker@uruz.ai0867.net] has joined #wesnoth-dev
20170922 03:40:33< irker861> wesnoth: Charles Dang wesnoth:master 95afd707c35d / changelog: Updated changelog https://github.com/wesnoth/wesnoth/commit/95afd707c35d657d6df38009f931eaf3d6e02949
20170922 03:40:36< irker861> wesnoth: Charles Dang wesnoth:master e47ea7fded72 / Doxyfile changelog players_changelog projectfiles/Xcode/Info.plist src/wesconfig.h: Pre-release version bump https://github.com/wesnoth/wesnoth/commit/e47ea7fded7221c40a59bc96073fb13b03182823
20170922 03:40:39< irker861> wesnoth: Vultraz wesnoth: e47ea7fded72 tagged as 1.13.9
20170922 03:48:08< irker861> wesnoth: Charles Dang wesnoth:master 8870f7d277b0 / Doxyfile changelog players_changelog src/wesconfig.h: Post-release version bump https://github.com/wesnoth/wesnoth/commit/8870f7d277b053404b7658c53d350b64cc459de3
20170922 03:48:20-!- vultraz changed the topic of #wesnoth-dev to: 1.13.9 tagged, announcing "soon" | Wesnoth Developers Channel | >>> Want to help? Go here: http://r.wesnoth.org/t42911 (and thanks!) <<< | Discord Server: https://discord.gg/tSmJS2E | Logs: http://irclogs.wesnoth.org | Bug tracker: http://bugs.wesnoth.org
20170922 03:58:09< Necrosporus> So it's already release
20170922 04:01:30-!- boucman [~rosen@wesnoth/developer/boucman] has joined #wesnoth-dev
20170922 04:04:11-!- celticminstrel [~celmin@unaffiliated/celticminstrel] has quit [Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
20170922 04:12:41-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 04:12:47-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 04:21:34-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 04:21:41-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 04:22:47< vultraz> loonycyborg: the release has been tagged
20170922 04:46:46< Necrosporus> When tarball will be available?
20170922 04:47:32< Necrosporus> I'm not talking about binaries, since they are build by distro maintainers for most platform, except windows and mac
20170922 05:12:27-!- travis-ci [~travis-ci@ec2-54-167-99-251.compute-1.amazonaws.com] has joined #wesnoth-dev
20170922 05:12:28< travis-ci> wesnoth/wesnoth#15092 (master - 8870f7d : Charles Dang): The build was fixed.
20170922 05:12:28< travis-ci> Build details : https://travis-ci.org/wesnoth/wesnoth/builds/278469284
20170922 05:12:28-!- travis-ci [~travis-ci@ec2-54-167-99-251.compute-1.amazonaws.com] has left #wesnoth-dev []
20170922 05:18:07-!- JyrkiVesterinen [~JyrkiVest@85-23-197-3.bb.dnainternet.fi] has quit [Quit: .]
20170922 05:26:58-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 05:45:20< vultraz> Necrosporus: tomorrow probably
20170922 05:49:06< Necrosporus> > You are in 'detached HEAD' state. // sounds scary
20170922 05:53:46< shadowm> Try not to lose your head over it.
20170922 06:00:27-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has joined #wesnoth-dev
20170922 06:02:48-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 06:05:58-!- boucman [~rosen@wesnoth/developer/boucman] has quit [Remote host closed the connection]
20170922 06:32:18< irker861> wesnoth: ln-zookeeper wesnoth:master 3786827b4f62 / data/campaigns/Eastern_Invasion/scenarios/11_Captured.cfg: EI S11: Corrected race=bat to race=bats, fixes #2031 https://github.com/wesnoth/wesnoth/commit/3786827b4f624022659df71a14437175fe369ed4
20170922 06:39:30< Necrosporus> One bug less
20170922 06:40:40< Necrosporus> zookeeper, what do you think about other races using singular while bats are plural?
20170922 06:51:51< vn971> \o/   wesnoth: Vultraz wesnoth: e47ea7fded72 tagged as 1.13.9
20170922 06:54:43< vn971> what happens with the "stable", "trunk" and such branches on the server now? If I build from "master" right now, wesnoth will connect to "1.13" server room? Or "trunk"?
20170922 06:55:19< JyrkiVesterinen> AFAIK, "master" builds always connect to the trunk server.
20170922 06:55:40< Necrosporus> You can connect to 1.13 server
20170922 06:55:51< vultraz> MP or addons?
20170922 06:55:52< Necrosporus> Though given both are empty theres no difference 
20170922 06:55:59< Necrosporus> I guess both
20170922 06:56:06< vn971> Also, shouldn't there be a "1.13" branch now? Or it's just master for now?
20170922 06:56:08< Necrosporus> though addons default to 1.13 even in trunk
20170922 06:56:18< vultraz> It connects to the trunk MP server but 1.13 addons server
20170922 06:56:35< Necrosporus> Why is there trunk addon server at all?
20170922 06:56:48< Necrosporus> Maybe if nobody uses it it's better to remove?
20170922 06:56:58< vn971> Necrosporus: there is no, see what vultraz wrote.
20170922 06:57:04< Necrosporus> It is there
20170922 06:57:08< Necrosporus> just nobody uses it
20170922 06:57:12< vn971> hmm.
20170922 06:57:17< vultraz> It’s for testing
20170922 06:57:27< Necrosporus> https://addons.wesnoth.org/trunk/
20170922 06:57:35< Necrosporus> How do I connect wesnoth master to this server?
20170922 06:57:49< vultraz> What?
20170922 06:58:07< Necrosporus> How do I tell Wesnoth client to connect to trunk server
20170922 06:58:21< Necrosporus> If it's built from git
20170922 06:58:24< vultraz> You need to specify the port and I can’t remember the port right now
20170922 06:58:36< vultraz> For the addons server, that is
20170922 06:58:50< Necrosporus> Or to use 1.13 mp server
20170922 07:00:20< vultraz> IIRC the released versions will connect to the 1.13 server automatically and connect to the trunk server otherwise (that is, if it’s a git build)
20170922 07:00:30< Necrosporus> Maybe we should change default to 1.13 server?
20170922 07:03:01< vn971> terminology is a bit itchy BTW. Instead of just default terminology of "master" branch, we use "git" (meaning I don't know what, and why, because everything is built from git now), "trunk" (hi SVN) and rarely "master".
20170922 07:03:14-!- JyrkiVesterinen_ [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 07:04:43< Necrosporus> Either way I don't see much reason in 1.13 - trunk MP server distinction
20170922 07:04:51< Necrosporus> And why 1.13 is not default
20170922 07:05:28-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Ping timeout: 240 seconds]
20170922 07:05:29-!- JyrkiVesterinen_ is now known as JyrkiVesterinen
20170922 07:08:48< shadowm> The "trunk" add-ons server is for testing purposes only and it's not used by any version by default.
20170922 07:09:02< shadowm> Do not confuse it with the MP server, which is a completely different story.
20170922 07:09:41< Necrosporus> Right. But what is purpose of trunk mp server?
20170922 07:09:47< shadowm> Some people also throw WIP/debug-proof-of-concept-style add-ons into the "trunk" server, like I did with the IftU April Fools release.
20170922 07:10:24< shadowm> Firstly, it's to keep players running the latest development version from running into devs testing something that may give them a barrage of OOS errors.
20170922 07:11:29< shadowm> Secondly, it also acts as the redirector hub for each server instance specific to a Wesnoth release series, and has assigned the default MP server port (!5000) so that it can handle the rest of the process as it sees fit.
20170922 07:12:13< shadowm> So e.g. it may redirect 1.12 client to port 13042 or whatever one day, or to port 14999 the next day. It's all so the Wesnoth.org admins chan change things without having to alter any client-side code.
20170922 07:13:29< Necrosporus> It seems that 1.13 server is still completely empty most of time
20170922 07:13:43< Necrosporus> same as trunk server
20170922 07:13:56< Necrosporus> Perhaps it will change if dev release news are announced
20170922 07:15:13< shadowm> trunk is empty by design since it's for people running UNRELEASED versions only (those would usually be devs unless you're crazy).
20170922 07:15:37< shadowm> 1.13? Empty because of all the poor PR surrounding development versions.
20170922 07:15:51< shadowm> That's been the case since 1.5.x approximately.
20170922 07:19:46< Necrosporus> then I'm crazy
20170922 07:20:15< Necrosporus> Anyway 1.13 master was less buggy than 1.13.8
20170922 07:20:45< Necrosporus> Already 1.13.9+dev contains a bugfix which is not coming in release probably
20170922 07:34:34< Necrosporus> Do we have a static analysis script for WML which can automatically catch missing images (and sounds) in WML?
20170922 07:34:53< Necrosporus> Would be useful for addons. I have seen many where a mistype causes missing images
20170922 07:35:39< Necrosporus> Or things such as upper case in code and lower case in actual filename or vice versa, which don't cause problems in some OSes and do in others
20170922 07:36:59< Necrosporus> Or mistypes in race, unit type and stuff
20170922 07:37:07< vn971> Necrosporus: adding to what Necrosporus said, I see a lot of warnings in terminal when I just view add-on list. Apparently you _can_ upload "wrong" stuff to the server, but client think it's serious enough to write in logs.
20170922 07:37:14< Necrosporus> It should be possible to find all such errors without need to test everything
20170922 07:37:48< Necrosporus> vn971, currently add-on server has almost no moderation, I guess
20170922 07:38:06< Necrosporus> At least there is no pre-moderation at all
20170922 07:38:20< Necrosporus> You can upload anything you want and it will stay there until moderators notice
20170922 07:39:28< vn971> Necrosporus: well I thought along the lines of doing some stuff automatically, or reduce the verbosity on the client. Dunno how hard would be the first thing to do.
20170922 07:39:58< Necrosporus> It should be trivial to collect all picture links and check if they exist in script
20170922 07:40:34< Necrosporus> Checking some other stuff such as https://github.com/wesnoth/wesnoth/issues/2031 is a little harder, but should be doable automatically in case of plain WML (without macros)
20170922 07:40:59< Necrosporus> Such as list of all defined races should be easy to compose automatically
20170922 07:41:08< Necrosporus> as well as list of all valid unit-ids
20170922 07:41:33< Necrosporus> And then it should be possible to grep all *.cfg files for stuff such as invalid ids
20170922 07:41:51< Necrosporus> (unit ids which are defined nowehere)
20170922 08:02:49-!- Ivanovic [~ivanovic@wesnoth/developer/ivanovic] has quit [Quit: Disconnecting from stoned server.]
20170922 08:03:05-!- Ivanovic [~ivanovic@p4FC53858.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 08:05:32-!- Appleman1234 [~quassel@124x38x163x22.ap124.ftth.ucom.ne.jp] has quit [Remote host closed the connection]
20170922 08:06:01-!- nore [~ncourant@sas.eleves.ens.fr] has quit [Ping timeout: 240 seconds]
20170922 08:07:19-!- Appleman1234 [~quassel@124x38x163x22.ap124.ftth.ucom.ne.jp] has joined #wesnoth-dev
20170922 08:10:14-!- nore [~ncourant@sas.eleves.ens.fr] has joined #wesnoth-dev
20170922 08:10:33-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
20170922 08:27:44-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 08:42:20< vn971> I've just compiled wesnoth from source. Yet I see: https://pointsgame.net/vn971/temp/2017.09.22_11:41:42_4f16df5.png  "Welcome to the official trunk multiplayer server!"
20170922 08:42:37< vn971> seemingly wesnoth connected to trunk instead of 1.13
20170922 08:43:04< vn971> More specifically, I compiled the 1.13.9 tag.
20170922 08:43:33< JyrkiVesterinen> IIRC, the MP server redirection needs to be updated manually. I guess it just hasn't been done yet.
20170922 08:47:21-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
20170922 08:47:30< vn971> JyrkiVesterinen: so it's server-side? (I can't understand how it can be server-side.)
20170922 08:47:53< JyrkiVesterinen> I don't recall exactly.
20170922 08:54:50-!- Bhoren [~Bhoren_wh@2a01:e0a:c:2150:e866:4fc7:b365:6048] has joined #wesnoth-dev
20170922 08:57:25< vn971> When it's all done and tested, would be time to ping distro maintainers.:)
20170922 08:59:23-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
20170922 09:00:23-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 09:02:37< Necrosporus> vn971, use 14997 port for now
20170922 09:15:35< vn971> Necrosporus: if only I'd understand what you wrote.:D I mean, is that a compile-time option? A run-time? `wesnoth --help` doesn't have a "port" thing (except proxy).
20170922 09:15:52-!- hrubymar10 [~hrubymar1@193.85.203.185] has joined #wesnoth-dev
20170922 09:15:56< Necrosporus> It is in connect mp server 
20170922 09:16:08< Necrosporus> Select second option and type port after colon
20170922 09:16:17< Necrosporus> server.wesnoth.org:14997
20170922 09:16:24< vn971> Basically what I want is to help testing wesnoth, and to flag it for release on ArchLinux when appropriate.
20170922 09:16:30< vn971> Necrosporus: got it, thanks!
20170922 09:17:58< vn971> It says "Welcome to the official development multiplayer server" though. I guess MOTD should be updated a bit.
20170922 09:22:08< hrubymar10> Hi, is Ivanovic there?
20170922 09:23:13< vn971> hrubymar10: you can write personal/private messages in IRC, 'y know.
20170922 09:24:53< Necrosporus> Whois says no
20170922 09:25:44< hrubymar10> @vn971 I don't tbh... I never used irc before...
20170922 09:27:00< vn971> hrubymar10: ah, OK. Ivanovic is here for that matter. Check your client, it most probably can actually show you room members. If you "click" on somebody from the room list you most usually can chat with him directly.
20170922 09:27:56< hrubymar10> Oh I see. thx
20170922 09:28:42< Necrosporus> vn971, though he's not here, his bnc is
20170922 09:28:51< JyrkiVesterinen> hrubymar10: IRC mentions work without the @.
20170922 09:28:53< Necrosporus> message is going to be delivered eventually probably though
20170922 09:31:45< hrubymar10> JyrkiVesterinen :D It is Discord habit
20170922 09:31:48< vn971> Necrosporus: you're right.
20170922 09:32:05< Soliton> unless it's a private question for Ivanovic it's probably best to just ask here.
20170922 09:32:23-!- irker861 [~irker@uruz.ai0867.net] has quit [Quit: transmission timeout]
20170922 09:32:46< hrubymar10> Soliton it is related to Wesnoth's translations
20170922 09:32:56< Soliton> vn971: what do you want updated in the MOTD?
20170922 09:36:19< vn971> Soliton: I guess we may just copy-paste and adapt the 1.12 message. 1. it should not have any "development" words 2. the line with "looking for more people" should be removed I think.
20170922 09:37:09< vn971> 3. change http to https  :)
20170922 09:40:13< Soliton> any reasons on how you came to the conclusion that those are good changes?
20170922 09:44:03-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
20170922 09:44:27< vn971> Soliton: well, if we're about to make 1.13 the stable release (and making 1.12 oldstable), it seems natural to copy current 1.12, isn't it? Since it would become "stable", no need to say "development". If we _want_ 1.13 to be more popular then we should remove the "popularity" notice. https may be a bit doubtful, OK, let's leave it out of scope if there are objections.
20170922 09:44:59-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 09:48:22< Soliton> so 1.13.9 is a release candidate?
20170922 09:48:55< vn971> Soliton: I thought so. Did I get, like, everything wrong?:D
20170922 09:49:06< Soliton> though i'm pretty sure we've also called release candidates the development version in the past.
20170922 09:49:53-!- hrubymar10 [~hrubymar1@193.85.203.185] has quit []
20170922 09:50:00< JyrkiVesterinen> Soliton: No, 1.13.9 is beta 2.
20170922 09:50:03< Soliton> vn971: no idea. haven't heard of that and nothing in the topic suggest it.
20170922 09:50:28< Necrosporus> Why is simulate-lobby-activity.lua in root directory and not in utils like utils/simulate_lobby_traffic.py
20170922 09:50:51< JyrkiVesterinen> Because it's a plugin. Same as host.lua and join.lua.
20170922 09:51:31< vn971> sorry then, I misunderstood intentions.
20170922 09:53:00-!- higgins` [~higgins@68.ip-149-56-14.net] has quit [Quit: Leaving]
20170922 09:55:09-!- Bhoren [~Bhoren_wh@2a01:e0a:c:2150:e866:4fc7:b365:6048] has quit [Remote host closed the connection]
20170922 09:55:55-!- higgins [~higgins@68.ip-149-56-14.net] has joined #wesnoth-dev
20170922 09:57:19-!- Bhoren [~Bhoren___@82-64-3-181.subs.proxad.net] has joined #wesnoth-dev
20170922 10:02:45-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Quit: .]
20170922 10:08:54-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has joined #wesnoth-dev
20170922 10:11:43< Necrosporus> data/cores.cfg says "17 Single Player Campaigns with 211 Scenarios"
20170922 10:11:49< Necrosporus> While there are 18 campaigns
20170922 10:12:00< Necrosporus> Not sure when it's displayed though
20170922 10:12:13< Necrosporus> but it's translatible text and it should be changed before string freeze
20170922 10:17:49< Necrosporus> Ah, actually it's 17 if you don't count tutorial
20170922 10:18:10< Necrosporus> I didn't notice it was in data/campaigns/
20170922 10:21:09< Necrosporus> There are files in data/core: encyclopedia/drakes.txt  encyclopedia/geography.cfg both seem to contain WML though
20170922 10:46:57< Necrosporus> In 1.13.9: error network: caught network error: End of file
20170922 10:48:19< Necrosporus> It happens if you click "join official server"
20170922 10:48:47< Necrosporus> vn971, can you confirm?
20170922 10:50:20< vn971> Necrosporus: it works for me (1.13.9 tag)
20170922 10:52:42< Necrosporus> No, still doesn't work for me
20170922 10:52:50< Necrosporus> 14997 works though
20170922 10:57:34< Necrosporus> vn971, could you run wesnoth with --log-debug=network then try to connect official server and paste console content for me?
20170922 10:59:28< Necrosporus> I get this https://pastebin.com/Ecs3JLyg
20170922 10:59:32-!- ToBeCloud [uid51591@wikimedia/ToBeFree] has joined #wesnoth-dev
20170922 10:59:35< Necrosporus> Built from 1.13.9 tag too
20170922 11:00:53< vn971> Necrosporus: https://gist.github.com/vn971/899a47c159ff71f00c25468404c463bf
20170922 11:01:52-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has joined #wesnoth-dev
20170922 11:02:41< Necrosporus> Data which is sent through network is not in log
20170922 11:02:48< Necrosporus> Only received
20170922 11:03:03< Necrosporus> Can wesnoth be made to also display what it sends to MP server?
20170922 11:03:41< Necrosporus> vn971, also it seem to contain some weird string, so you can expose your password accidentally. Though it seems not in your log
20170922 11:04:59< Necrosporus> vn971, what git status says for you?
20170922 11:05:10< Necrosporus> HEAD detached at 1.13.9 // nothing to commit, working directory clean
20170922 11:05:11< Necrosporus> For me
20170922 11:05:24< vn971> git status \n HEAD detached at 1.13.9 \n nothing to commit, working tree clean
20170922 11:05:34< Necrosporus> Then why difference?
20170922 11:05:42< Necrosporus> Try to connect using unregistered name
20170922 11:07:13< Necrosporus> It seems server tries to redirect me to 1.13 server and fails
20170922 11:07:27< Necrosporus> While putting you in trunk server
20170922 11:18:44-!- vultraz [uid24821@wesnoth/developer/vultraz] has quit [Quit: Connection closed for inactivity]
20170922 11:33:24< gfgtdf> hmm
20170922 11:34:07< gfgtdf> Necrosporus: coudl you try moving this block https://github.com/wesnoth/wesnoth/blob/master/src/wesnothd_connection.cpp#L357 in the if (recv_queue_.empty()) { conditional below (before the return false?)
20170922 11:38:42< Necrosporus> gfgtdf, I have removed build cash, so it will take two hours
20170922 11:40:37-!- irker945 [~irker@uruz.ai0867.net] has joined #wesnoth-dev
20170922 11:40:37< irker945> wesnoth: gfgtdf wesnoth:gfgtdf-patch_wesnothdredirection ff4f00a33a22 / src/wesnothd_connection.cpp: don't throw network_error if we still have incoming data queued https://github.com/wesnoth/wesnoth/commit/ff4f00a33a2229c002b93b6deae6d60c5f41c853
20170922 11:43:29< Necrosporus> scons is bad as it doesn't stop when ^C is pressed
20170922 11:43:48< Necrosporus> I have decided to try scons this time and removed cmake build dir
20170922 11:44:25< JyrkiVesterinen> I find SCons much easier for the developers, though.
20170922 11:45:01< JyrkiVesterinen> SCons developers have a point in that it's much easier to write custom logic in Python than to use a build system specific language.
20170922 11:45:26< vn971> Necrosporus: successfully logged in with all settings reset.
20170922 11:45:39< vn971> (and a guest password-less name "vasyatest")
20170922 11:48:31< Necrosporus> scons build=release desktop_entry=no nls=no notifications=no fribidi=n jobs=2 wesnoth 
20170922 11:48:36< Necrosporus> Is this command correct?
20170922 11:49:20< JyrkiVesterinen> Looks valid to me.
20170922 11:54:14< Necrosporus> scons doesn't show percents of completion like cmake
20170922 11:54:25< Necrosporus> Perhaps it could be made too
20170922 11:54:32< Necrosporus> Also I have old versions of most tools
20170922 11:54:57< Necrosporus> I hope scons won't rebuild from scratch after I change a file
20170922 11:55:25< JyrkiVesterinen> It can do incremental rebuilds like CMake.
20170922 11:57:02< Necrosporus> I don't know how to make incremental rebuild
20170922 11:57:13< Necrosporus> Imagine I finish building with command above
20170922 11:57:13< JyrkiVesterinen> SCons does it by default.
20170922 11:57:23< Necrosporus> so I simply repeat the command?
20170922 11:57:28< JyrkiVesterinen> Yes.
20170922 11:57:38< Necrosporus> Like regular make then
20170922 11:57:50< Necrosporus> If cmake is rerun then make will start building from scratch
20170922 11:58:05< Necrosporus> there is also ccache, perhaps I need to enable it
20170922 11:58:28< JyrkiVesterinen> IIRC, with CMake you're supposed to rerun make when you want to rebuild.
20170922 11:58:40< Necrosporus> it's what I did
20170922 11:59:15< Necrosporus> anyway, I'm rebuilding with scons without gfgtdf suggested changes to see if behavior will change
20170922 12:05:22< AI0867> I've noticed that the MP tests frequently fail for various reasons (they deadlock somehow, or the display server fails to start properly). Should we try to ignore those errors?
20170922 12:07:00< AI0867> example: https://travis-ci.org/wesnoth/wesnoth/jobs/278360183
20170922 12:09:47-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 12:10:40< vn971> // I'm on ArchLinux, most soft has maximum versions here. I wonder whether distro builders might have problems with that though. If the error is because of some outdated library, me need to explicitly write it in dependencies I guess.
20170922 12:12:10< JyrkiVesterinen> AI0867: IIRC, MP tests haven't deadlocked for a long time.
20170922 12:12:37< JyrkiVesterinen> Failing to connect to Mir is new. I think it started when Travis CI upgraded the Ubuntu image.
20170922 12:13:26< JyrkiVesterinen> vn971: Dependencies are listed in https://github.com/wesnoth/wesnoth/blob/master/INSTALL.md
20170922 12:13:43< JyrkiVesterinen> Nothing there should cause problems for any non-ancient distribution.
20170922 12:14:03< vn971> JyrkiVesterinen: (I was referring to Necrosporus-s error.)
20170922 12:15:04< JyrkiVesterinen> Outdated libraries very rarely show up as bugs.
20170922 12:15:12< Necrosporus> Mir was abandoned anyway
20170922 12:15:31< Necrosporus> Also did wesnoth support Mir?
20170922 12:16:03< JyrkiVesterinen> Wesnoth doesn't need to "support" it. Mir supports graphical programs, not the other way around.
20170922 12:16:59< JyrkiVesterinen> Ubuntu would never get anywhere by telling everyone "oh, by the way, we have written a new graphics server. Please port all graphical programs to support it, otherwise Ubuntu isn't going to have any working software. Kthxbye."
20170922 12:17:06< Necrosporus> I mean isn't wesnoth designed to work with X.org?
20170922 12:17:16< Necrosporus> Or does Mir implement X11 protocol?
20170922 12:17:48< Necrosporus> AFAIR Wayland needs special measures or X emulation plugin
20170922 12:17:55< Necrosporus> I have never looked into Mir though
20170922 12:18:57< JyrkiVesterinen> Both have compatibility layers for X programs.
20170922 12:19:03< JyrkiVesterinen> XWayland and XMir.
20170922 12:20:14< Necrosporus> So can Wesnoth work with Mir without XMir?
20170922 12:21:12< JyrkiVesterinen> I think so.
20170922 12:21:43< JyrkiVesterinen> We use SDL for rendering, and support for Mir and Wayland was enabled by default in SDL 2.0.4.
20170922 12:21:51< JyrkiVesterinen> Which is the minimum version we require.
20170922 12:22:52< loonycyborg> by default wesnoth is running via X
20170922 12:23:13< loonycyborg> which would use xwayland on wayland compositors
20170922 12:23:26< loonycyborg> SDL supports wayland
20170922 12:23:49< loonycyborg> but when I tried running wesnoth via wayland I got white noise
20170922 12:23:59< loonycyborg> that was on gnome on fedora
20170922 12:25:05< loonycyborg> Also even if that is fixed sdl apps don't do client side decorations
20170922 12:25:57< JyrkiVesterinen> Requiring client-side decorations is just stupid.
20170922 12:26:14< JyrkiVesterinen> At least KWin is going to have optional support for server-side decorations.
20170922 12:44:11< AI0867> JyrkiVesterinen: I got a host waiting for something to happen on travis just a few days ago
20170922 12:44:19< AI0867> but I seem to have restarted the job, so I can't find it
20170922 12:44:30< AI0867> and it happened more than once last week
20170922 12:45:51< JyrkiVesterinen> I have fixed such problems before. If you can find a log, I might try to fix it.
20170922 12:45:52< JyrkiVesterinen> https://github.com/wesnoth/wesnoth/commit/2c4d72f544b447d5a225f349b2078923e2f767cf#diff-a06a8e94379607b77569627ed0deb4ef
20170922 12:46:20< JyrkiVesterinen> Although fixing would be much, much easier if the problem was 100% reproducible.
20170922 12:46:54< JyrkiVesterinen> However, that still wouldn't help with the Mir problems...
20170922 12:47:47-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Remote host closed the connection]
20170922 12:48:21-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 12:54:40-!- matthiaskrgr [matthiaskr@gateway/shell/panicbnc/x-owvsmpfswwifljvt] has quit [Ping timeout: 255 seconds]
20170922 13:00:19-!- hrubymar10_irc [~textual@ip-86-49-124-139.net.upcbroadband.cz] has joined #wesnoth-dev
20170922 13:05:21-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Quit: Konversation terminated!]
20170922 13:08:40-!- ToBeCloud [uid51591@wikimedia/ToBeFree] has quit [Quit: Connection closed for inactivity]
20170922 13:09:39-!- hrubymar10_irc [~textual@ip-86-49-124-139.net.upcbroadband.cz] has quit [Quit: hrubymar10_irc]
20170922 13:11:10-!- travis-ci [~travis-ci@ec2-54-167-99-251.compute-1.amazonaws.com] has joined #wesnoth-dev
20170922 13:11:11< travis-ci> wesnoth/wesnoth#15094 (gfgtdf-patch_wesnothdredirection - ff4f00a : gfgtdf): The build passed.
20170922 13:11:11< travis-ci> Build details : https://travis-ci.org/wesnoth/wesnoth/builds/278581803
20170922 13:11:11-!- travis-ci [~travis-ci@ec2-54-167-99-251.compute-1.amazonaws.com] has left #wesnoth-dev []
20170922 13:11:36-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 13:11:53-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has joined #wesnoth-dev
20170922 13:17:45-!- mkdroid [~null@unaffiliated/matthiaskrgr] has joined #wesnoth-dev
20170922 13:19:41-!- mkdroid [~null@unaffiliated/matthiaskrgr] has quit [Client Quit]
20170922 13:27:29< Necrosporus> Interesting. Why does scons wesnoth take 22M bytes while one built with cmake takes 26M? Options are same
20170922 13:29:12< Necrosporus> also version is different
20170922 13:31:40< loonycyborg> well there were efforts to harmonize compiler options passed in both
20170922 13:31:44< JyrkiVesterinen> Is it reproducible?
20170922 13:31:52< JyrkiVesterinen> My first guess would be just random variation.
20170922 13:32:08< loonycyborg> but there still could be dependencies detected differently or something
20170922 13:32:54-!- matthiaskrgr [matthiaskr@gateway/shell/panicbnc/x-tgqbkqdmwtentnhj] has joined #wesnoth-dev
20170922 13:33:18-!- matthiaskrgr is now known as Guest31431
20170922 13:34:05-!- Guest31431 [matthiaskr@gateway/shell/panicbnc/x-tgqbkqdmwtentnhj] has quit [Changing host]
20170922 13:34:05-!- Guest31431 [matthiaskr@unaffiliated/matthiaskrgr] has joined #wesnoth-dev
20170922 13:34:05-!- Guest31431 [matthiaskr@unaffiliated/matthiaskrgr] has quit [Changing host]
20170922 13:34:05-!- Guest31431 [matthiaskr@gateway/shell/panicbnc/x-tgqbkqdmwtentnhj] has joined #wesnoth-dev
20170922 13:34:55-!- Guest31431 is now known as matthiaskrgr_
20170922 13:36:19-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 13:39:06-!- Oebele [~quassel@143.177.58.202] has joined #wesnoth-dev
20170922 13:40:13< Necrosporus> JyrkiVesterinen, what reproducible? different size? I think yes. My scons command line is posted above
20170922 13:40:28< Necrosporus> cmake line was identical as far as I remember
20170922 13:40:48< Necrosporus> I mean -DOPTION=value instead of option=value of course
20170922 13:40:56< Necrosporus> But otherwise same
20170922 13:41:02< JyrkiVesterinen> Hmm, I see.
20170922 13:41:22< JyrkiVesterinen> But I'd still guess random factors, such as the linking order of object files.
20170922 13:41:47< Necrosporus> Well, as far as I remember executable size was more or less constant
20170922 13:41:55< Necrosporus> in cmake repeated builds
20170922 13:42:13< Necrosporus> You can try yourself using my command line on 1.13.9 tag master
20170922 13:57:45< AI0867> Necrosporus: have you looked at the arguments passed to the actual compiler and such?
20170922 13:58:12< AI0867> not just the flags passed to the build system
20170922 13:58:37< Necrosporus> Nope
20170922 13:59:41< Necrosporus> I do not know how to see actual options in cmake build
20170922 14:00:01< Necrosporus> also I have removed cmake build directory so it's probably lost anyway
20170922 14:00:19< Necrosporus> scons outputs commmands as it executes them though
20170922 14:00:50< Necrosporus> There was some make key to make it output commands being executed
20170922 14:00:58< JyrkiVesterinen> I think you can see the commands with CMake if you build with make -v.
20170922 14:01:21< Necrosporus> right. But as I said I lost them
20170922 14:02:22< Necrosporus> also cmake version shows different commit number compared to scons version. Though I have built it several times without rerunning cmake so it got cached somewhere probably
20170922 14:03:49< Necrosporus> Will we need to postpone 1.13.9 if multiplayer connect bug remains?
20170922 14:05:10< JyrkiVesterinen> 1.13.9 is already tagged. The fix isn't going to it.
20170922 14:05:27< JyrkiVesterinen> And from what I can tell, it isn't a regression relative to 1.13.8 either.
20170922 14:09:55< Necrosporus> With gfgtdf patch connection didn't break
20170922 14:10:39-!- JyrkiVesterinen [~JyrkiVest@195-192-251-124.s1networks.fi] has quit [Quit: Going home, I'll be back online within three hours]
20170922 14:18:56< irker945> wesnoth: gfgtdf wesnoth:master 94e4ca1a38b9 / src/wesnothd_connection.cpp: don't throw network_error if we still have incoming data queued (#2032) https://github.com/wesnoth/wesnoth/commit/94e4ca1a38b9a65306db754d772f11a648399728
20170922 14:20:08< Necrosporus> Why did network error throw anyway?
20170922 14:20:37< Necrosporus> Also why doesn't wesnoth --log-debug=network say what is it writing to the server?
20170922 14:20:55< Necrosporus> It does recite what it gets back but not what it sends
20170922 14:21:16-!- gfgtdf_ [~chatzilla@x4e36956c.dyn.telefonica.de] has joined #wesnoth-dev
20170922 14:21:25< gfgtdf_> vultraz: we should consider retagging 1.13.9 to get that commit ^ into 1.13.9, it seems to fix a bug where clicking 'connect to official server' wouldn't work
20170922 14:21:49< Necrosporus> Though vn971 said that connect worked for him
20170922 14:21:59< Necrosporus> Why did it work for him and didn't work for me?
20170922 14:24:19< gfgtdf_> Necrosporus: hw probably tested at a differnt time when the server asn'T yet configurew to redirect version 1.13.9
20170922 14:24:22-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has quit [Ping timeout: 260 seconds]
20170922 14:24:26-!- gfgtdf_ is now known as gfgtdf
20170922 14:24:55< Necrosporus> he had tested after I told about my problem too
20170922 14:26:10< gfgtdf> Necrosporus: how do you know ?
20170922 14:26:45< Necrosporus> Because I reported this error here and asked him to reproduce
20170922 14:26:48< Necrosporus> Though I got it
20170922 14:27:02< Necrosporus> He has built from commit with post-release version bump
20170922 14:27:09< Necrosporus> His log says Battle for Wesnoth v1.13.9+dev
20170922 14:28:23< Necrosporus> I have Battle for Wesnoth v1.13.9 (e47ea7f-Clean)
20170922 14:28:23< Necrosporus>  which is exact commit of release
20170922 14:29:09< Necrosporus> Pre-release version bump to be exact
20170922 14:30:40< Necrosporus> I will try git pull and recompilation now
20170922 14:39:20< Necrosporus> gfgtdf, will vultraz have to remove changelog entry, make new tag and again read changelog entry?
20170922 14:41:59-!- matthiaskrgr_ is now known as matthiaskrgr
20170922 14:59:57< Necrosporus> It seems that simple version changing commit takes really lot of time to recompile
20170922 15:00:04< Necrosporus> almost like compiling from scratch
20170922 15:00:18< Necrosporus> even though all files stay the same but a single header
20170922 15:05:49< loonycyborg> a single header can be used in many .cpp files
20170922 15:05:58< loonycyborg> and all .cpp files using it need rebuild
20170922 15:06:45< Necrosporus> Is it possible to put wesnoth version header in less files?
20170922 15:06:58< Necrosporus> or perhaps use const instead of define?
20170922 15:07:21< Necrosporus> I guess the problem is that version is a preprocessor macross
20170922 15:07:39< Necrosporus> So preprocessing cpp files makes them different if it is changed
20170922 15:08:28< Necrosporus> If it was const then changing it would not change code in other files and they would not have to be recompiled
20170922 15:09:54< Necrosporus> #define VERSION "1.13.9+dev" in src/wesconfig.h
20170922 15:15:44-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has quit [Ping timeout: 248 seconds]
20170922 15:32:26< Necrosporus> Also Lua console default hotkey is tilda ~
20170922 15:38:47-!- sevu [~Shiki@p54854B15.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 15:41:47< Necrosporus> I get lots of libpng warning: iCCP: known incorrect sRGB profile
20170922 15:41:51< Necrosporus> What does it mean?
20170922 15:42:01< Necrosporus> does everybody else get it?
20170922 15:42:31< loonycyborg> it looks familiar but I'm not getting it here
20170922 15:43:18< Necrosporus> try starting aethermath
20170922 15:43:24< Necrosporus> libpng warning: iCCP: profile 'Photoshop ICC profile': 1000000h: invalid rendering intent
20170922 15:43:26< Necrosporus> This too
20170922 15:44:11< Necrosporus> loonycyborg, ah, campaign list causes it
20170922 15:44:15< Necrosporus> but there are addons
20170922 15:44:48< loonycyborg> there always are some silly warnings, as long as stuff works I assume it's not critical and they'll get to handling that stuff eventually
20170922 15:45:29< loonycyborg> I'm not getting it from addon list either
20170922 15:47:23< Necrosporus> Ah, it's picture from an addon
20170922 15:47:29< loonycyborg> hmm I got the tarball ready but I'm not sure if I should upload it given gfgtdf's fix
20170922 15:47:40< Necrosporus> loonycyborg, probably not
20170922 15:47:51< Necrosporus> Who wants a release which can't even connect to MP server
20170922 15:48:16< loonycyborg> ah yes
20170922 15:48:23< loonycyborg> I see it totally can't
20170922 15:49:09< Necrosporus> Interestingly this bug was only triggered after release was tagged because otherwise it will connect to trunk server wich sits on default port and no reconnect was needed
20170922 15:49:40< Necrosporus> It seems that problem was that server sends redirect and disconnects
20170922 15:50:01< Necrosporus> old version throws network error end of file
20170922 15:50:17< Necrosporus> gfgtdf fix makes it first process all received data
20170922 15:51:03< Necrosporus> I wonder, if I didn't report it in irc would it mean that release would came out with this bug or somebody else would have fixed it?
20170922 15:51:20< Necrosporus> * noticed it 
20170922 15:51:26< Necrosporus> before tarballs were deployed
20170922 15:52:06< loonycyborg> well generally I try to connect to mp server, but that's only when testing windows build
20170922 15:52:28< loonycyborg> I assume basic testing was done before tagging
20170922 15:52:46< Necrosporus> The problem is that tagging was the reason for bug
20170922 15:53:09< loonycyborg> https://wiki.wesnoth.org/ReleasingWesnoth#Test_the_build
20170922 15:53:44< Necrosporus> By the way I didn't try to connect addon server
20170922 15:53:49< loonycyborg> oh ah yes
20170922 15:53:52< loonycyborg> that's evil
20170922 15:54:07< loonycyborg> so testing it before tagging wouldn't catch it
20170922 15:56:24< Necrosporus> Actually vultraz could have caught it if he tried to build after writing changes to wesconfig.h
20170922 15:56:40< Necrosporus> but before commiting it to master with tag
20170922 15:57:07< Necrosporus> Unless he did but server didn't redirect him properly or
20170922 16:02:58< Necrosporus> loonycyborg, testing the build comes after committing version bump
20170922 16:03:25-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Quit: Konversation terminated!]
20170922 16:03:33< Necrosporus> Is it possible to tag existing commit after it has been made?
20170922 16:03:58< Necrosporus> or commit can be only tagged when pushed?
20170922 16:04:25< loonycyborg> a tag always references existing commit
20170922 16:04:37< loonycyborg> tag can be pointed to a different comming
20170922 16:04:40< loonycyborg> commit
20170922 16:04:48< loonycyborg> but it was problematic last time I did that
20170922 16:06:38< Necrosporus> if tag didn't exist was it possible to add it to a commit from a year ago?
20170922 16:17:47-!- Oebele [~quassel@143.177.58.202] has quit [Remote host closed the connection]
20170922 16:18:39< shadowm> Yes.
20170922 16:19:21< shadowm> (You ask weird questions, you know that right?)
20170922 16:19:46< irker945> wesnoth: loonycyborg wesnoth:master 414659200df8 / scons/system_include.py: scons: ensure that if /usr/include is added to CPPPATH it won't be used with -is https://github.com/wesnoth/wesnoth/commit/414659200df8a58f902ebf89031a12c23ca60e3e
20170922 16:19:56-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
20170922 16:25:44-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has joined #wesnoth-dev
20170922 16:29:32< gfgtdf> loonycyborg: trigering that bug afaik also requires the wesnoth config update, do een if vultraz tested after the pre relerase bump he probably wouldn'T ahev noticed
20170922 16:30:25< loonycyborg> the question is
20170922 16:30:38< loonycyborg> can we remove 1.13.9 tag and point it to another commit?
20170922 16:31:17< sevu> yes
20170922 16:31:55< sevu> https://nathanhoad.net/how-to-delete-a-remote-git-tag
20170922 16:31:55< shadowm> Please no.
20170922 16:32:16< shadowm> Anyone who ever thinks of doing this should REPLACE ME AS THE PERSON MAINTAINING THE MEDIAWIKI SETUP ON WESNOTH.ORG.
20170922 16:32:24< shadowm> Then you'll know true pain.
20170922 16:33:18< shadowm> (The MediaWiki devs have a habit of rewriting tags. Trust me, it's not great when you're on the receiving end of a broken patch chain.)
20170922 16:33:55< loonycyborg> I remember last time I did that it was received as if I did a force push to master :P
20170922 16:34:46< shadowm> In fact, you know what, if you do rewrite 1.13.9 I will disable the wiki, dump the database to eleven different unlabeled files scattered across all VMs, and clear the current database.
20170922 16:35:09< shadowm> Then leave YOU to deal with it.
20170922 16:36:25< gfgtdf> so we'll simply make a new label? like 1.13.10 or 1.13.9a ? and release that
20170922 16:41:35-!- boucman [~rosen@wesnoth/developer/boucman] has joined #wesnoth-dev
20170922 16:53:50< Necrosporus> Usually it's with a
20170922 17:05:25< Necrosporus> Where can 1.13.9 windows binaries be found?
20170922 17:05:39< Necrosporus> ± several commits
20170922 17:06:09< Necrosporus> Google found this https://ci.appveyor.com/project/wesnoth/wesnoth-7lnpw/ but I can't see download link
20170922 17:14:09< Necrosporus> loonycyborg, what is a force push to master?
20170922 17:14:51-!- sevu [~Shiki@p54854B15.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
20170922 17:15:38-!- JyrkiVesterinen [~JyrkiVest@85-23-197-3.bb.dnainternet.fi] has joined #wesnoth-dev
20170922 17:20:50< loonycyborg> history rewriting, would make things painful for everyone who has a checkout
20170922 17:23:54< JyrkiVesterinen> Necrosporus: Here are the latest AppVeyor Windows release binaries: https://ci.appveyor.com/project/wesnoth/wesnoth-605wt/build/Wesnoth-VS2017-master-165/job/5c76h3yvo7fu0crh/artifacts
20170922 17:24:25< JyrkiVesterinen> AppVeyor only builds daily, and doesn't care about tags. It doesn't give you binaries of 1.13.9 or any other release.
20170922 17:27:21< Necrosporus> Thanks.
20170922 17:29:51< vn971> don't commit more often than once a day, that's all.
20170922 17:39:35< gfgtdf> both apppveyor and jekins can be told to buidl the current master state immidiateley.
20170922 17:40:26< JyrkiVesterinen> It didn't work in AppVeyor's case.
20170922 17:40:48< gfgtdf> jenkins is usually faster since it caches the results and doesnt always do full rebuilds,  on the other hand iirc jenkins builds way more single builds, not sure wheterh tah fully compensated
20170922 17:41:22< gfgtdf> JyrkiVesterinen: i'm sure i did that many times succesfully in both jankins and appveyor
20170922 17:41:50< JyrkiVesterinen> Are you talking about the button to launch a manual build?
20170922 17:42:26< JyrkiVesterinen> I thought you were talking about setting up a repository hook that makes the CI build whenever code is pushed.
20170922 17:43:13-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has quit [Quit: hrubymar10_irc]
20170922 17:50:33< gfgtdf> i'm talkina about the button to make a manual build
20170922 17:54:57-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has joined #wesnoth-dev
20170922 17:56:59-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has quit [Client Quit]
20170922 17:57:04-!- vultraz [uid24821@wesnoth/developer/vultraz] has joined #wesnoth-dev
20170922 17:57:22-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has joined #wesnoth-dev
20170922 17:58:45< gfgtdf> vultraz: you saw the previosu discussion ?
20170922 17:58:51< vultraz> hm?
20170922 17:59:16< vultraz> what discussion?
20170922 17:59:34< Necrosporus> vultraz, tagged release won't work with MP
20170922 18:00:13< gfgtdf> vultraz: i said that we shodul put 94e4ca1a38 in our 1.13.9 release, shadowm said moving the tag is unacceptable.
20170922 18:00:29< Necrosporus> The problem is in server redirection. It does break connection after sending redirect but 1.13.9 tag won't parse it and throw network error immediately
20170922 18:00:45< Necrosporus> Add 1.13.9a tag then?
20170922 18:00:57< gfgtdf> ye that's what i suggested
20170922 18:01:19< vultraz> moving the tag is unacceptable, yes
20170922 18:01:52< Necrosporus> vultraz, did you try to build and test after changing wesconfig.h?
20170922 18:02:13< vultraz> i don't think i connected to MP
20170922 18:02:14< vultraz> sorry
20170922 18:02:35< Necrosporus> I'm not sure if this bug was reproduciable on window
20170922 18:02:46< Necrosporus> Did anybody build 1.13.9 tag for windows?
20170922 18:03:51< vultraz> gfgtdf: this was a blocker, yes?
20170922 18:04:13< Necrosporus> If connecting to Official Server doesn't work at all
20170922 18:04:25< Necrosporus> At least for me
20170922 18:04:42< gfgtdf> vultraz: Necrosporus notices it when i tested the 1.13.9 release, the point it it only effects releases, not +dev versions that why we didn'T see it before
20170922 18:04:49< gfgtdf> didn't
20170922 18:04:55< vultraz> i see
20170922 18:04:56< vultraz> ok
20170922 18:05:09< gfgtdf> noticed when he tested*
20170922 18:05:46< Necrosporus> So it's OK to report some bugs to irc after all
20170922 18:05:54< Necrosporus> Or not?
20170922 18:06:33< vultraz> yes it's ok
20170922 18:06:44< gfgtdf> Necrosporus: well you do risk that they get forgotten, so putting thme inth tracker is better.
20170922 18:07:28< gfgtdf> Necrosporus: this one was rather urgent, so ye beeing forgotten was rather unleikley there
20170922 18:07:28< Necrosporus> In this case I wanted somebody else to confirm first
20170922 18:08:30< gfgtdf> the disadvnatge of  1.13.9a release is that with the version_version object we have 1.13.9a > 1.13.9+dev
20170922 18:08:56< Necrosporus> Then use ascii symbol below +
20170922 18:09:01< gfgtdf> maybe we shodul just call it 1.13.10
20170922 18:09:59< Necrosporus> Will 1.13.9*  work?
20170922 18:10:06< Necrosporus> I'd recommend 1.13.9.1
20170922 18:10:49< Necrosporus> gfgtdf, also does release tag have to match version in wesconfig.h?
20170922 18:11:09< gfgtdf> hmm not sure aqctually, you shodul aks th release manager
20170922 18:11:27-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 18:11:39< Necrosporus> So if it does then 1.13.10 is better probably
20170922 18:11:43< vultraz> i don't think it does
20170922 18:11:56< Necrosporus> otherwise perhaps 1.13.9*
20170922 18:11:58< vultraz> shadowm has used the a suffix in the past when he was RM
20170922 18:12:17< shadowm> No,What suffix?
20170922 18:12:22< Necrosporus> If you want it to sort before 1.13.9+
20170922 18:12:29< vultraz> 1.x.xa
20170922 18:12:35< shadowm> The only botched release I was responsible for was 1.12.3.
20170922 18:12:38< Necrosporus> shadowm, is it ok if 1.13.9 release will have 1.13.9* tag in git?
20170922 18:12:39< shadowm> I released 1.12.4 instead.
20170922 18:12:45< vultraz> oh
20170922 18:12:52< shadowm> Necrosporus: Don't use asterisks.
20170922 18:12:53< vultraz> wait, should i release 1.13.10 then?
20170922 18:13:01-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has quit [Quit: hrubymar10_irc]
20170922 18:13:05< Necrosporus> shadowm, then 1.13.9+ 
20170922 18:13:07< gfgtdf> loonycyborg: made once a x.x.xa release fora  windows epcific bug iirc
20170922 18:13:17< shadowm> Don't use plus or minus signs either.
20170922 18:13:20< Necrosporus> or 1.13.10
20170922 18:13:26< shadowm> Especially don't use those.
20170922 18:13:28< Necrosporus> or 1.13.9.1
20170922 18:13:49< shadowm> (Why am I being asked these questions, I'm not the release manager.)
20170922 18:14:01< vultraz> you have approximate knowledge of many things
20170922 18:14:02< Necrosporus> I think if * + - are not acceptable then 1.13.10 is best
20170922 18:14:15< vultraz> gfgtdf: can you add a changelog entry for this bug 
20170922 18:14:32< gfgtdf> sure but where shodul i put it? 1.13.9 ro 1.13.10
20170922 18:14:42< shadowm> Like I said, when I released 1.12.3 and found out shortly afterwards that the primary fix in it was incomplete, I released 1.12.4 to rectify that instead.
20170922 18:15:02< vultraz> put it under the 1.13.9+dev header and I'll tag 1.13.10
20170922 18:15:16< shadowm> In the past, other release managers used letter suffixes, but the problem with those is that our tier 1 packagers have a habit of using those for patched rebuilds.
20170922 18:16:19< shadowm> The version_info object supports an arbitrary number of version components ≥ 3, but anything past 3 hasn't ever been tested with mainline and it's likely to cause all kinds of problems with external tools.
20170922 18:16:49< shadowm> Plus, since this project uses +dev and -dev as suffixes for unreleased versions, X.Y.Z.U+dev is going to look weird.
20170922 18:18:35< irker945> wesnoth: gfgtdf wesnoth:master 9ba7bfae3a70 / changelog: Update changelog https://github.com/wesnoth/wesnoth/commit/9ba7bfae3a70d05a9301ad249b9be1678091a0d3
20170922 18:19:00< gfgtdf> vultraz: ^
20170922 18:19:16< Necrosporus> vultraz, what if you don't tag immediately?
20170922 18:19:33< shadowm> Then he doesn't tag immediately.
20170922 18:19:33< vultraz> what?
20170922 18:19:48< Necrosporus> commit change to wesconf.h and stuff but don't commit again after that?
20170922 18:19:56< Necrosporus> and don't tag
20170922 18:20:03< vultraz> why
20170922 18:20:07< Necrosporus> Then when build is tested you can tag it
20170922 18:20:21< vultraz> alright, if you want to do some testing
20170922 18:20:21< Necrosporus> In order to not have to deal with 1.13.11
20170922 18:21:15< shadowm> I'm curious why you sound so sure that a quick 1.13.11 is going to be necessary.
20170922 18:21:26< shadowm> Do you know something the team doesn't?
20170922 18:21:33< Necrosporus> Nope
20170922 18:21:55< Necrosporus> I know there are several bugs I didn't find how to report properly yet
20170922 18:22:03< Necrosporus> but they are not as bad
20170922 18:22:27< Necrosporus> One of them stays since 1.12 by the way
20170922 18:22:35< irker945> wesnoth: Charles Dang wesnoth:master bc86ce762dc3 / Doxyfile changelog players_changelog projectfiles/Xcode/Info.plist src/wesconfig.h: Pre-release version bump https://github.com/wesnoth/wesnoth/commit/bc86ce762dc3ce9a3f5954cf31cdd9709190cf35
20170922 18:24:11< shadowm> "Nope" was good enough for an answer. :)
20170922 18:27:51-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 18:31:03< Necrosporus> OK, checked out and started building 1.13.10
20170922 18:32:21< Necrosporus> Does anybody has setup for windows build?
20170922 18:32:37< Necrosporus> vn971, do you want to test bugfix on arch?
20170922 18:37:42< gfgtdf> i renamed the 1.13.10 milestone to 1.13.11
20170922 18:39:35< Necrosporus> gfgtdf, can you add a job to build this release to appveyor?
20170922 18:39:50< gfgtdf> did that already
20170922 18:47:19< vn971> Necrosporus: bugfix for what? If anything, if something's on master, I can test that.
20170922 18:52:57< Necrosporus> vn971, yes, checkout master right now
20170922 18:53:06< Necrosporus> While it's in 1.13.10 state
20170922 18:53:38< Necrosporus> vn971, your build was 1.13.9+dev since commit which introduced 1.13.9 was immediately followed by another version bump
20170922 18:53:47< Necrosporus> The bug happens only in releases
20170922 18:54:06< Necrosporus> Bugfix for bug which we discussed today earlier
20170922 18:58:17-!- Bhoren [~Bhoren___@82-64-3-181.subs.proxad.net] has quit [Quit: Leaving]
20170922 18:59:05< JyrkiVesterinen> I can join the MP server with a local 1.13.10 Windows build just fine. :)
20170922 18:59:14-!- Bhoren [~Bhoren_wh@2a01:e0a:c:2150:b86f:6322:f808:2769] has joined #wesnoth-dev
20170922 19:01:12< stikonas> hi, can anybody help with with linking wesnoth? I get an error?
20170922 19:01:14< stikonas> https://pastebin.com/rZPrATWx
20170922 19:01:18< Necrosporus> JyrkiVesterinen, that's nice. Would you like to test rest of stuff?
20170922 19:01:50< Necrosporus> I mean starting every single campaign, trying to play at least one scenario to the end and so on
20170922 19:02:03< Necrosporus> also connecting addon server and installing addons
20170922 19:02:11< vn971> vn971 a.k.a. vasya a.k.a jenkins.:D  Anyway, it's compiling now.
20170922 19:02:19< JyrkiVesterinen> I can test some more stuff, but I'm not willing to spend much effort right now.
20170922 19:03:08< irker945> wesnoth: gfgtdf wesnoth:gfgtdf-patch_filter_this_unit daceb438cbee / src/units/filter.cpp: fix filters using this_unit in [hides] https://github.com/wesnoth/wesnoth/commit/daceb438cbee7eb837972c61b53ef5b975ca234d
20170922 19:03:22< gfgtdf> Necrosporus: ^
20170922 19:03:39< gfgtdf> it's a pr
20170922 19:04:21< EliDupree> Hmm, even in scenarios much simpler than EoHS, syntax errors in lua scripts aren't going to the commandline output
20170922 19:04:40< gfgtdf> i thought th would
20170922 19:04:53< gfgtdf> EliDupree: do they go into the la console ?
20170922 19:05:00< gfgtdf> they shodul probably go into both
20170922 19:05:02< EliDupree> I think they're going to the chat log, but I can't see them because they quickly get overridden by various additional errors
20170922 19:06:12< EliDupree> Or rather, just the main chat, but not the chat log
20170922 19:06:52< gfgtdf> so they are nopt going into the lua console?
20170922 19:07:01< EliDupree> the what?
20170922 19:07:19< gfgtdf> the lua console you can opne it via hotkey (1.13)
20170922 19:07:34< gfgtdf> in debug mode only unfortunatley
20170922 19:08:35< EliDupree> Neat feature, but no, they don't show up there either
20170922 19:08:53< vultraz> please everyone do any testing they desire
20170922 19:09:00< vultraz> i'll tag 1.13.10 tonight
20170922 19:09:32< EliDupree> This is specifically syntax errors in code=<<>> blocks, I don't know about wesnoth.require()
20170922 19:12:19-!- Ivanovic [~ivanovic@p4FC53858.dip0.t-ipconnect.de] has quit [Changing host]
20170922 19:12:19-!- Ivanovic [~ivanovic@wesnoth/developer/ivanovic] has joined #wesnoth-dev
20170922 19:14:28< gfgtdf> i just tested and i saw the syntaxerromessae in both stdout and the lua console
20170922 19:17:48< EliDupree> huh
20170922 19:18:13< EliDupree> I suppose it could have been fixed since 1.13.9. I wonder if there's anything else unique about my setup…
20170922 19:18:58< gfgtdf> there was onyl one engine commit since 1.13.9 that one one is unrelated
20170922 19:19:08< EliDupree> This is running wesnoth using `wesnoth -d --debug-lua -m`
20170922 19:19:35< gfgtdf> i wonder what debug-lua does
20170922 19:19:39< Necrosporus> What is --debug-lua ?
20170922 19:20:18< EliDupree> --debug-lua                     enables some Lua debugging mechanisms
20170922 19:20:22< EliDupree> according to wesnoth -h
20170922 19:20:57< EliDupree> I have no idea what it does
20170922 19:21:59< EliDupree> Anyway, I have the same problem without it
20170922 19:22:27< gfgtdf> and you start wesnoth without any parameters?
20170922 19:22:43< EliDupree> Oh no, there are a lot of parameters, I just didn;t list them
20170922 19:22:51< vn971> Necrosporus: I've connected to the MP server using a guest login just now. No problems, as before.
20170922 19:23:09< EliDupree> ./wesnoth -d --debug-lua -m --multiplayer-repeat 1000 --scenario Tiny_Close_Relation_LAI --controller 1:ai --controller 2:ai
20170922 19:24:24< Necrosporus> vn971, wesnoth -R output?
20170922 19:24:34< gfgtdf> it till happens to you if you start wesnoth without any parameters?
20170922 19:25:21< gfgtdf> still*
20170922 19:25:28< vn971> Necrosporus: https://gist.github.com/vn971/f8a962e4f2425f200e0ed5b381dc13b7
20170922 19:25:55-!- Kwandulin [~Kwandulin@pD9FD50F1.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
20170922 19:26:52-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Remote host closed the connection]
20170922 19:27:25-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 19:27:46< gfgtdf> EliDupree: oh wait maybe it'S becasue i tested with toplevel [lua] tags while you put yours into [event]s ?
20170922 19:27:56< EliDupree> maybe!
20170922 19:29:52< Necrosporus> vn971, so you have 1.13.10 proper release (at least unless there are more bugs)
20170922 19:30:32< vn971> when are we going to switch to 1.13 as "stable" branch btw?
20170922 19:30:41< JyrkiVesterinen> Never.
20170922 19:30:47< Necrosporus> In next ear probably
20170922 19:30:48< JyrkiVesterinen> The next stable branch will be 1.14.
20170922 19:31:18< loonycyborg> according to convention even numbers are stable releases, like 1.12 and 1.14
20170922 19:31:28< loonycyborg> odd numbers like 1.13 are dev releases
20170922 19:31:38< loonycyborg> based directly on master branch
20170922 19:31:41< vn971> lol.) It's just strange, I mean 1.12._6_ is already stable. But in 1.13 we already have .10, and still not stable. how?
20170922 19:32:04< Necrosporus> The Battle for Wesnoth version 1.13.10 (bc86ce7-Clean)
20170922 19:32:18< vn971> loonycyborg: ah! Now I got it (I think). Though I never understood that convention. It's definitely not semver.
20170922 19:32:22< loonycyborg> in this case numbers have little other meaning than to establish release order
20170922 19:32:42< JyrkiVesterinen> vn971: It's what you should expect.
20170922 19:32:46< loonycyborg> I think it doesn't contradict semver
20170922 19:32:51< JyrkiVesterinen> 1.11 went up to 1.11.11.
20170922 19:33:12< JyrkiVesterinen> Stable branches reach _lower_ version numbers than development branches.
20170922 19:33:15< loonycyborg> though if I was making a project of my own I for sure wouldn't have such a convention
20170922 19:33:25< vn971> loonycyborg: IDK, I think semver is a bit different, but I think it would be pointless to argue on that. Counter-productive for sure.
20170922 19:33:34< JyrkiVesterinen> Because 1.12 was already supposed to be stable in 1.12.0 and not *need* many bugfix releases.
20170922 19:33:40< Necrosporus> now the question
20170922 19:33:53< Necrosporus> why does my wesnoth report commit number while vn971 doesn't?
20170922 19:33:55< JyrkiVesterinen> Whereas development branches also introduce features in intermediate updates.
20170922 19:34:10< loonycyborg> that depends on how it's built
20170922 19:34:30< vn971> scons prefsdir=.local/share/$_gitname/$branch build=debug prefix=/opt/wesnoth-$branch-debug
20170922 19:34:38< loonycyborg> sometimes build either can't run the tool to extract git hash or it's not run from git repo
20170922 19:34:41< Necrosporus>  time scons build=release desktop_entry=no nls=no notifications=no fribidi=n jobs=2 wesnoth
20170922 19:34:45< gfgtdf> JyrkiVesterinen: more, we also had 1.11.19
20170922 19:34:46< EliDupree> Not that this matters, but it definitely does contradict semver, since it has breaking changes for add-ons without incrementing its most major version
20170922 19:35:06< JyrkiVesterinen> gfgtdf: Okay. It doesn't show up in master changelog though.
20170922 19:35:10< vn971> more specifically, in my case it's  scons prefsdir=.local/share/wesnoth/1.13 build=debug prefix=/my-personal-prefix
20170922 19:35:45< vn971> loonycyborg: it's not run from git repo, I'm erasing .git folder
20170922 19:36:08< JyrkiVesterinen> Well, have we ever stated that we comply to semver?
20170922 19:36:15< JyrkiVesterinen> It's not mandatory, you know.
20170922 19:36:24< gfgtdf> JyrkiVesterinen: yes probalby because master was plit form 1.11 at 1.11.12 , you'll see those vesiosn in the 1.12.c changelog though.
20170922 19:37:36< vn971> JyrkiVesterinen: yes. I just didn't get it (wesnoth versioning), and now I do. I guess complying to semver could have the advantage of being more familiar to people (if indeed wesnoth versioning != semver). But probably it's a small benefit.
20170922 19:47:03-!- hrubymar10_irc [~hrubymar1@ip-86-49-124-139.net.upcbroadband.cz] has joined #wesnoth-dev
20170922 19:54:57-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has quit [Quit: ChatZilla 0.9.93 [Firefox 55.0.3/20170824053622]]
20170922 20:01:05-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 20:01:12-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 20:08:53-!- JyrkiVesterinen [~JyrkiVest@85-23-197-3.bb.dnainternet.fi] has quit [Quit: Going to bed]
20170922 20:17:56< EliDupree> Sigh, my old lua AI no longer works. Is there an example of a working lua AI somewhere in mainline wesnoth?
20170922 20:19:26-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Remote host closed the connection]
20170922 20:19:59-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev
20170922 20:20:44< EliDupree> Never mind, found it myself
20170922 20:25:33-!- vn971 [~vasya@94.158.103.15] has quit [Ping timeout: 246 seconds]
20170922 20:35:25< EliDupree> weird... The AI side seems to be controlled first by the default AI, then EVENTUALLY calls my lua code after the regular AI is done with its moves :-(
20170922 20:36:27-!- sevu [~Shiki@p54854B15.dip0.t-ipconnect.de] has joined #wesnoth-dev
20170922 20:41:36< Necrosporus> >Check if in the game each campaign does start
20170922 20:41:53< Necrosporus> I have checked everything else from https://wiki.wesnoth.org/ReleasingWesnoth#Test_the_build page
20170922 20:42:05< Necrosporus> too lazy to check all 17 campaigns
20170922 20:42:24< shadowm> It takes what, 20 seconds each?
20170922 20:46:12< Necrosporus> A bit more if you try to make a few turns
20170922 20:46:24< Necrosporus> HttT works at least
20170922 20:47:11< Necrosporus> Liberty works
20170922 20:51:01-!- travis-ci [~travis-ci@ec2-54-91-250-86.compute-1.amazonaws.com] has joined #wesnoth-dev
20170922 20:51:02< travis-ci> wesnoth/wesnoth#15099 (gfgtdf-patch_filter_this_unit - daceb43 : gfgtdf): The build passed.
20170922 20:51:02< travis-ci> Build details : https://travis-ci.org/wesnoth/wesnoth/builds/278742046
20170922 20:51:02-!- travis-ci [~travis-ci@ec2-54-91-250-86.compute-1.amazonaws.com] has left #wesnoth-dev []
20170922 20:52:26< Necrosporus> LoW in local MP mode works
20170922 20:52:38< Necrosporus> though in Treasure even cage doesn't do anything
20170922 20:52:40< zookeeper> eh, there's a bug in UtBS, i guess i can fix it right away...
20170922 20:53:26< EliDupree> I pretty much copied data/ai/scenarios/scenario-lua_ai.cfg, and my evaluation function isn't even being CALLED until after the units get moved by some other AI (the default AI?)
20170922 20:53:31< Necrosporus> should in start of chapter II of LoW an elven cage spawn an elvish shyde?
20170922 20:53:45< Necrosporus> also side 3 has empty recruit list
20170922 20:54:06< Necrosporus> * s/even/elven
20170922 20:54:55< zookeeper> oh wait it's not a bug, just unit placed events not being fired when debug-creating a unit. i thought they were.
20170922 20:58:51< EliDupree> Here's my code: https://github.com/elidupree/wesnoth-ai/blob/master/_main.cfg
20170922 20:59:34< EliDupree> (Not using the era at the top, just using the [multiplayer])
20170922 21:03:37< Necrosporus> Seems that it's supposed to work like it does, but it's weird nevertheless. I mean in LoW treasury
20170922 21:06:04-!- Coffee_irc [~david@203.63.42.216] has joined #wesnoth-dev
20170922 21:20:37< zookeeper> umm. the right-click deselection bringing up the context menu problem is still there in master, so i don't see how it's supposed to be releasable.
20170922 21:20:50< zookeeper> unless the point is to drive players insane with that, for some reason.
20170922 21:21:58-!- mjs-de [~mjs-de@b9168e0e.cgn.dg-w.de] has joined #wesnoth-dev
20170922 21:25:32< zookeeper> vultraz, ^
20170922 21:27:21< zookeeper> you've been doing something with something related to right-clicking, so maybe it's your fault
20170922 21:28:19< zookeeper> namely d419caf24 and the commit it references
20170922 21:30:04< zookeeper> anyway, i'm off to bed ->
20170922 21:31:20< Ravana_> with 1.13.9 using "alt+s", closing that window, results in result of "s" open. I recall something about that being fixed
20170922 21:34:08-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has quit [Ping timeout: 240 seconds]
20170922 21:38:14< sevu> it's #1736
20170922 21:40:06< Ravana_> good, confirmed
20170922 21:43:17< Ravana_> but agreed, no working deselect ways is annoying - not even possible to put another hotkey for deselect unit
20170922 21:46:42-!- vultraz [uid24821@wesnoth/developer/vultraz] has quit [Quit: Connection closed for inactivity]
20170922 21:47:19< sevu> there seem to be problem with githubs infrastructure. #issues of the last days are gone, #2022 is the last, we were at least at #2030
20170922 21:51:01< sevu> hmm, at least #2030 is gone, was opened by arcanister ( Necrosporus ) , who's github page is gone too. hmm
20170922 21:54:52-!- mjs-de [~mjs-de@b9168e0e.cgn.dg-w.de] has quit [Remote host closed the connection]
20170922 21:55:11< sevu> Necrosporus, to answer your question, the unit-icons are used in the editor too. Already in older wesnoth versions.
20170922 22:05:00-!- irker945 [~irker@uruz.ai0867.net] has quit [Quit: transmission timeout]
20170922 22:34:24-!- sevu [~Shiki@p54854B15.dip0.t-ipconnect.de] has quit [Quit: Verlassend]
20170922 22:42:22-!- boucman [~rosen@wesnoth/developer/boucman] has quit [Remote host closed the connection]
20170922 22:45:37-!- Bhoren [~Bhoren_wh@2a01:e0a:c:2150:b86f:6322:f808:2769] has quit [Quit: Leaving]
20170922 23:17:17-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection]
20170922 23:17:25-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth-dev
20170922 23:20:52-!- gfgtdf [~chatzilla@x4e36956c.dyn.telefonica.de] has joined #wesnoth-dev
20170922 23:21:02< gfgtdf> i didn't even know it's possible to delete github issues completly
20170922 23:50:19-!- celticminstrel [~celmin@unaffiliated/celticminstrel] has joined #wesnoth-dev
--- Log closed Sat Sep 23 00:00:06 2017