--- Log for 13.03.116 Server: verne.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 9 days and 19 hours ago 00.25.48 Join PurlingNayuki [0] (~Thunderbi@219.142.158.89) 00.33.34 *** Saving seen data "./dancer.seen" 00.38.25 Quit saratoga (Ping timeout: 252 seconds) 00.46.06 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 45.0/20160303134406]) 01.12.57 Quit ender` (Quit: What language do deaf people think in?) 02.02.15 Nick opal is now known as sosueme (h@wowana.me) 02.07.12 Join PurlingNayuki1 [0] (~Thunderbi@219.142.158.89) 02.08.10 Quit PurlingNayuki (Ping timeout: 244 seconds) 02.08.39 Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@219.142.158.89) 02.09.47 Quit sosueme (Quit: <3) 02.10.45 Join opal [0] (h@eat.at.the.krustykrab.restaurant) 02.12.43 Nick opal is now known as kashire- (h@eat.at.the.krustykrab.restaurant) 02.14.12 Nick kashire- is now known as opal (h@eat.at.the.krustykrab.restaurant) 02.33.35 *** Saving seen data "./dancer.seen" 02.43.12 Quit opal (Quit: <3) 02.43.49 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 02.57.51 Quit TheSeven (Ping timeout: 250 seconds) 02.59.23 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 03.01.18 Join Milardo [0] (1805b463@gateway/web/freenode/ip.24.5.180.99) 03.02.35 # Hi, i've checked the release list of builds for sony nwz players but can't find one for mine which is nwz-e353 03.03.26 # anybody know happen to know if it will get supported? 03.05.58 # <[Saint]> It might. Perhaps some time between now and possibly never. 03.06.10 # <[Saint]> That's about the closest to realistic statement anyone can offer. 03.10.29 # well anybody here who works on the sony ports? 03.11.55 # or do any of the sony ports compatible with mine? 03.13.16 # <[Saint]> You would probably want to talk to pamaury about this. I'm not confident he has this hardware, which would be a limiting factor. 03.13.17 # <[Saint]> The guts of it is, basically, that if you want it to happen in any reasonable amount of time you should be looking towards pretending that no one else exists and doing it all yourself entirely. 03.14.26 # i guess its really hard to do that? 03.15.23 # <[Saint]> http://www.rockbox.org/wiki/NewPort will give you some idea. 03.15.34 # <[Saint]> The wording of it seems harsh, but it is realistic. 03.16.28 # too hard for me 03.16.52 # <[Saint]> It was too hard for everyone until they learned the skills to allow them to do so. ;) 03.16.59 # <[Saint]> No one was born knowing these things. 03.17.18 # right but i have only one player like this 03.17.27 # and id rather not take it apart 03.17.51 # if it is just software stuff maybe 03.18.19 # <[Saint]> Well, one needs to know what they are dealing with in the hardware department first. 03.19.06 # <[Saint]> Another option would be supplying the hardware to a willing developer, but that also comes with no guarantees. Its a hobby project, such is its nature. 03.19.39 # ok thanks for the info 03.30.04 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 03.33.03 Join CrashBash-Kun [0] (~CrashBash@unaffiliated/crashbash-kun) 03.35.42 Quit Milardo (Quit: Page closed) 03.36.30 Quit Rower (Ping timeout: 244 seconds) 03.42.36 Join ZincAlloy1 [0] (~Adium@pD9FB74B5.dip0.t-ipconnect.de) 03.45.10 Quit ZincAlloy (Ping timeout: 246 seconds) 04.03.27 Nick NEffi is now known as Neffi (~Neffi@visenya.neffi.net) 04.11.33 Quit CrashBash-Kun (Ping timeout: 240 seconds) 04.33.37 *** Saving seen data "./dancer.seen" 04.37.58 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 04.38.46 Quit krabador (Quit: Take The Time) 04.41.00 Quit JdGordon_ (Ping timeout: 250 seconds) 04.57.22 Join krabador [0] (~krabador@unaffiliated/krabador) 05.34.39 Join FSanches [0] (~felipe@2804:14c:37:268b:f8cc:c4a6:ec80:ab48) 05.36.24 Quit krabador (Ping timeout: 244 seconds) 05.37.31 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 05.40.29 Quit JdGordon (Ping timeout: 248 seconds) 06.17.12 Quit Slasheri_ (Ping timeout: 260 seconds) 06.21.27 Join Slasheri [0] (miipekk@rockbox/developer/Slasheri) 06.22.33 Quit ZincAlloy1 (Quit: Leaving.) 06.32.33 Quit FSanches (Quit: Leaving.) 06.33.41 *** Saving seen data "./dancer.seen" 07.20.08 Join rela [0] (~x@pdpc/supporter/active/rela) 08.31.21 Quit nlogex (Ping timeout: 252 seconds) 08.33.44 *** Saving seen data "./dancer.seen" 09.00.54 Quit krnlyng (Ping timeout: 276 seconds) 09.01.18 Join krnlyng [0] (~liar@83.175.90.24) 09.26.56 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 09.38.53 Quit Topy44 (Ping timeout: 246 seconds) 09.38.56 Join Topy44 [0] (topy@2a03:b0c0:0:1010::2d:2001) 10.13.17 Quit bertrik (Remote host closed the connection) 10.33.48 *** Saving seen data "./dancer.seen" 10.50.36 Join ender` [0] (krneki@foo.eternallybored.org) 11.06.21 Join petur [0] (~petur@rockbox/developer/petur) 11.09.25 Join lebellium [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr) 11.28.27 Join xorly [0] (~xorly@ip-86-49-15-121.net.upcbroadband.cz) 12.33.49 *** No seen item changed, no save performed. 12.45.44 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.00.00 Quit pamaury (Ping timeout: 240 seconds) 13.13.52 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.21.03 Quit pamaury (Ping timeout: 240 seconds) 13.21.57 Quit krnlyng (Quit: krnlyng) 13.26.28 Quit dfkt (Quit: SIC GORGIAMVS ALLOS SVBJECTATOS NVNC.) 13.26.33 Join krnlyng [0] (~liar@77.116.67.69.wireless.dyn.drei.com) 13.33.53 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 13.45.24 Quit krnlyng (Ping timeout: 252 seconds) 13.51.48 Quit sLite (Quit: No Ping reply in 180 seconds.) 13.53.09 Join sLite [0] (~quassel@mail.slite.org) 13.53.09 Quit dfkt (Read error: Connection reset by peer) 13.53.51 Join krnlyng [0] (~liar@77.116.67.69.wireless.dyn.drei.com) 13.54.03 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 13.58.13 Quit petur (Quit: Leaving) 14.09.51 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 14.12.34 Quit JdGordon_ (Ping timeout: 250 seconds) 14.14.50 Quit JdGordon (Ping timeout: 276 seconds) 14.14.53 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 14.18.47 Join FSanches [0] (~felipe@2804:14c:37:268b:fc38:196:d605:a2d7) 14.21.47 Join krabador [0] (~krabador@unaffiliated/krabador) 14.29.10 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 14.32.04 Quit JdGordon_ (Ping timeout: 250 seconds) 14.33.53 *** Saving seen data "./dancer.seen" 14.35.06 Quit dfkt (Read error: Connection reset by peer) 14.36.26 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 14.41.10 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 14.43.09 Quit JdGordon (Ping timeout: 252 seconds) 14.51.44 Join fs-bluebot [0] (~fs-bluebo@xd9bef2ca.dyn.telefonica.de) 14.52.19 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 14.53.38 Quit bluebrother (Ping timeout: 248 seconds) 14.53.50 Quit fs-bluebot_ (Ping timeout: 244 seconds) 14.55.42 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 15.36.09 Join nlogex [0] (~filip@dhcp-108-168-15-53.cable.user.start.ca) 16.06.32 Quit Strife89 (Ping timeout: 250 seconds) 16.07.43 Join Strife89 [0] (~quassel@adsl-98-80-231-103.mcn.bellsouth.net) 16.33.54 *** Saving seen data "./dancer.seen" 16.37.44 Quit PurlingNayuki (Ping timeout: 250 seconds) 17.23.44 Nick suYin`OFF is now known as suYin (mysuyin@server2.shellfire.net) 17.35.01 Quit krnlyng (Ping timeout: 260 seconds) 17.38.39 Join PurlingNayuki [0] (~Thunderbi@219.142.158.89) 17.42.12 Join ZincAlloy [0] (~Adium@pD9FB74B5.dip0.t-ipconnect.de) 17.55.24 Join krnlyng [0] (~liar@83.175.90.24) 17.55.39 Quit PurlingNayuki (Ping timeout: 252 seconds) 17.56.54 Join petur [0] (~petur@rockbox/developer/petur) 18.00.16 Quit xorly (Quit: I quit, that is all) 18.11.02 Quit sLite (Quit: No Ping reply in 180 seconds.) 18.12.26 Join sLite [0] (~quassel@mail.slite.org) 18.19.43 Join CrashBash-Kun [0] (~CrashBash@unaffiliated/crashbash-kun) 18.24.40 Join CrashBash-Kun_ [0] (~CrashBash@unaffiliated/crashbash-kun) 18.25.11 Quit CrashBash-Kun (Ping timeout: 244 seconds) 18.30.52 Quit CrashBash-Kun_ (Ping timeout: 244 seconds) 18.33.55 *** Saving seen data "./dancer.seen" 18.39.57 Join JdGordon [0] (~jonno@ppp118-209-173-146.lns20.mel8.internode.on.net) 18.39.57 Quit JdGordon (Changing host) 18.39.57 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 18.42.57 Quit JdGordon_ (Ping timeout: 250 seconds) 18.51.38 Join JanC_ [0] (~janc@lugwv/member/JanC) 18.51.44 Quit JanC (Ping timeout: 276 seconds) 18.54.18 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 18.57.20 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 19.00.38 Quit JdGordon (Ping timeout: 268 seconds) 19.49.53 Quit nlogex (Quit: WeeChat 1.4) 19.57.45 Quit sLite (Quit: No Ping reply in 180 seconds.) 19.59.05 Join sLite [0] (~quassel@mail.slite.org) 20.16.07 Quit [Saint] (Ping timeout: 250 seconds) 20.27.58 Quit sLite (Quit: No Ping reply in 180 seconds.) 20.29.27 Join sLite [0] (~quassel@mail.slite.org) 20.33.58 *** Saving seen data "./dancer.seen" 20.38.28 Join [Saint] [0] (~hayden@rockbox/staff/saint) 20.53.09 Join b0hoon [0] (~quassel@83-238-235-158.adsl.inetia.pl) 20.55.19 # Build Server message: 3New build round started. Revision e0a4dc5, 255 builds, 24 clients. 21.04.35 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 21.07.38 Quit JdGordon_ (Ping timeout: 264 seconds) 21.07.46 # Build Server message: 3Build round completed after 746 seconds. 21.07.46 # Build Server message: 3Revision e0a4dc5 result: 0 errors 111 warnings 21.09.48 # <[Saint]> Ouch. 21.10.41 # <[Saint]> I...what? 21.10.44 # <[Saint]> How the? 21.11.15 # <[Saint]> How the hell does a comment trigger 111 warnings? 21.15.16 # what? 21.15.34 # <[Saint]> 'Revision e0a4dc5 result: 0 errors 111 warnings' 21.16.26 # <[Saint]> That commit alters no code paths at all, so, I'm more than a little confused as to how that can happen. 21.16.32 # it's from new gcc i suppose not mine 21.18.03 # you scared me :) 21.21.47 Quit sLite (Quit: No Ping reply in 180 seconds.) 21.23.06 Join sLite [0] (~quassel@mail.slite.org) 21.34.42 # it's probably just that the compiler from one of the build clients prints a lot of warnings, it's not related to the commit 21.37.16 # with gcc 5.3.1 (503) 21.46.36 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 21.48.35 # Build Server message: 3New build round started. Revision 2c7bb67, 255 builds, 24 clients. 21.49.00 Quit JdGordon (Ping timeout: 248 seconds) 21.54.37 Join Horscht [0] (~Horscht@kodi/user/horscht) 21.56.41 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 21.59.23 # Build Server message: 3Build round completed after 647 seconds. 21.59.24 # Build Server message: 3Revision 2c7bb67 result: 0 errors 204 warnings 22.00.29 # <[Saint]> I am somewhat surprised that the build system doesn't enforce a very strict set of versioning criteria for the dependent tool set. 22.00.52 # <[Saint]> Having this whole "any verion'll do as long as it compiles in the end" system is a bit odd. 22.02.13 # <[Saint]> pamaury: I noticed a comment from you in one of the commits - did you want/require the Rockbox MIPS toolchain by any chance? 22.02.33 # <[Saint]> I have 64 bit toolchains for all targets pre-packaged. 22.03.14 # no that's fine, I just gave up using the toolchain from rockboxdev.sh and I'm using the one prepackaged in debian repositories 22.03.30 # the one we are using is just completely outdated, we should update it 22.05.19 Quit rela (Ping timeout: 250 seconds) 22.06.09 # <[Saint]> What are your feelings about the other point raised regarding dependent tools? Is it worth me looking in to strict versioning checks? It's something I've been thinking about for a while but it involves a lot of coordination and decisions on what constitutes an acceptable version. 22.06.28 # <[Saint]> I kinda tend to think it is worth it in the end but there's a lot of fuckery involved to get it working initially. 22.11.27 # <[Saint]> The idea of a distributed build system where anyone can bring any tools or toolchains to the party as long as the end result doesn't error out seems ...I dunno. Weird to me. 22.12.46 # <[Saint]> It hasn't really created any problems in the past that weren't trivially fixable by simply temporarily disabling a specific client or clients, but if it would be useful and not too overly restrictive for everyone to be on the same page then the required work to implement it isn't too daunting for me. 22.13.10 # our build systems allows from some range of versions, it also crucially depends on the default flags of the compiler, I'm not sure if it's really worth it but if you can get everyone who has a build client to agree on this that can't hurt I guess 22.13.36 # except it's annoying to have multiple redundant toolchains because of rockbox 22.15.24 Quit krabador (Read error: Connection reset by peer) 22.15.30 # <[Saint]> I guess the really difficult part lies in getting everyone to agree on the base requirements. 22.15.52 # maybe the first part would be to gather information ? 22.16.01 Join krabador [0] (~krabador@unaffiliated/krabador) 22.16.04 # <[Saint]> I think, in general, if we can rely on toolchains packed from $distribution, that would be very desirable. 22.16.05 # ask everyone who has a build client to report the toolchains details 22.16.41 # [Saint]: The code pointed by new gcc indeed looks strange and iilogical and should be fixed IMO 22.16.53 # <[Saint]> armeabi and MIPS should be doable on a large scale from $distribution packaged toolchains 22.17.02 # <[Saint]> Not sure about any of the more esoteric ones. 22.17.26 # I'll try to do it but not now 22.17.30 # but not everyone has the same distribution, also the packged version may change from time to time 22.18.18 # <[Saint]> Yes. This is true. I'm somewhat willing to bet that most of us are on some form of debian-esque distribution, though. And package pinning exists. 22.21.19 # <[Saint]> But, pamaury is quite right. This all starts with asking build client operators to do full version reporting of their build systems and seeing exactly how wide a range we're dealing with. 22.22.27 # you're right that version pinning with would work well, assuming debian of course. I guess we could arrange so that the prepackaged version fits in the range and everyone agrees to use it 22.29.41 # how do we have the list of clients ? 22.30.07 # <[Saint]> AFAIK, we don't. Which is another problem. 22.30.35 # There's a mailing list build client admins are supposed to be on 22.30.59 # s/are supposed to/might/ :) 22.31.18 # <[Saint]> If this did eventuate, we'd have to just disable all the clients that didn't meet the requirements and rely on them eventually figuring it out or checking their mail. 22.32.43 Part b0hoon ("GTG... Bye.") 22.32.49 # If you want to check, rbclient.pl is probably the right place 22.33.32 # <[Saint]> right - yeah, I was just actually writing something to that effect. 22.33.58 # <[Saint]> I wouldn't want to step on the build system as a whole and force developers into using a specific tool set and having to hack their way out of it. 22.34.00 *** Saving seen data "./dancer.seen" 22.34.17 # <[Saint]> I only want the hard versioning requirements to affect the build clients. 22.34.28 # Well... 22.34.45 # As far as I remember, back in the day the variation there was seen as a bonus 22.35.00 # <[Saint]> Oh? 22.35.09 # <[Saint]> Hmmm...well, yeah, I guess I can see that. 22.36.11 # <[Saint]> I guess it helps that we're not running on any critical systems, or when we do, we have no networking ability. 22.37.21 # <[Saint]> so there's no real need to care about avoiding known exploitable tool versions. And I guess I can see why it would be desirable to know it builds across a wide range of variables. 22.40.24 # Hmm, who wrote that code? 22.40.41 # <[Saint]> which? 22.40.59 # Have you looked at those new warnings? :) 22.41.09 # <[Saint]> ah, yes. 22.41.13 # I'd *thank* that new gcc 22.41.32 # are we talking about some plugin by chance ? 22.41.35 # Yes 22.41.44 # some of them are just horrible 22.42.42 # <[Saint]> I would honestly give zero fucks if we just ousted them all except for test_* plugins 22.42.48 # The code works *because* the precedence is wrong 22.43.29 # If it did what the author thought it does, that function would always error out 22.43.53 # <[Saint]> All the plugins are basically gimmicks or weird ridiculously difficult to use kludges based around a situation most people are going to avoid like the plague. 22.44.19 # <[Saint]> No one in their right mind is going to deliberately use any of the editor plugins or anything that revolves around the use of the virtual keyboard. 22.44.25 Quit petur (Quit: Leaving) 22.44.41 # So how do we fix it? Take out that entire if block so the behaviour is what it always was, but without misleading code and fun warnings, or try to fix it properly without testing and risk breaking the plugin? 22.46.22 # <[Saint]> I take it we're talking about Goban? 22.46.34 # yes 22.47.42 # <[Saint]> 'rm -rf /plugins/*' ought to do it. 22.48.18 # That's against the license terms :) 22.48.33 # <[Saint]> :) 22.48.49 # You have to keep credits.c! 22.49.49 # I think just removing the obviously broken lines is the best way forward 22.52.57 # Build Server message: 3New build round started. Revision b58b9c2, 255 builds, 23 clients. 22.52.59 # There! 22.53.03 # * gevaerts hopes it compiles :) 22.53.42 # <[Saint]> Build Server message: Revision b58b9c2 result: 0 errors 164897 warnings 22.54.27 # :) 22.56.09 # By the way, if you're ever not sure about operator precedence, *add parentheses* 22.56.52 # At least that way you'll find out that the slightly higher level logic is totally broken :) 22.57.18 Join PurlingNayuki [0] (~Thunderbi@219.142.158.89) 22.59.20 # Hmmm, I'm not sure now about the fix now... 23.04.40 # * gevaerts pushes a probably better but possibly worse fix 23.05.01 # <[Saint]> why hasn't that build even returned yet? 23.05.06 # <[Saint]> or did bluebot die? 23.05.12 # Because it's not done yet 23.05.17 # Build Server message: 3Build round completed after 740 seconds. 23.05.18 # Build Server message: 3Revision b58b9c2 result: 0 errors 6 warnings 23.05.19 # Build Server message: 3New build round started. Revision 2292782, 255 builds, 23 clients. 23.05.26 # <[Saint]> ah, there we go. 23.05.39 # <[Saint]> Did some of the beefier clients fall off the roster? 23.06.23 # Probably, petur left, so it seems likely that his client also left 23.06.38 # Which is annoying, as that was the one that gave the warnings :) 23.07.11 # I'm not really awake enough to wade through the subtle side effects of that read_char_no_whitespace() function combined with lazy evaluation and misunderstood precedence, so I hope that whoever likes playing goban will complain if I did it wrong 23.07.59 # <[Saint]> Where's Lee Sedol when you need 'em? 23.08.47 # Celebrating, probably :) 23.13.08 Quit FSanches (Quit: Leaving.) 23.14.39 Quit Horscht (Quit: quit) 23.17.29 # Build Server message: 3Build round completed after 731 seconds. 23.17.30 # Build Server message: 3Revision 2292782 result: 0 errors 7 warnings 23.20.09 Quit Strife89 (Ping timeout: 252 seconds) 23.20.51 # I don't see where that other warning is 23.21.26 Join Strife89 [0] (~quassel@adsl-98-80-231-103.mcn.bellsouth.net) 23.26.52 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 45.0/20160303134406])