--- Log for 12.12.116 Server: verne.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 5 days and 15 hours ago 00.00.56 # <[Saint]> PLATFORM_HOSTED only gets viewers, right? 00.01.01 # <[Saint]> wrt: plugins 00.01.54 # <[Saint]> or is that only the case if you don't build against a resolution that happens to be shared by a supported target? 00.03.40 # <[Saint]> trying to follow the chain here and it isn't too obvious to me immediately. 00.03.53 # <[Saint]> __builtin: plugins are your jam, ^? 00.04.11 # <__builtin> give me a sec 00.05.18 # <[Saint]> I seem to recall that the case is basically that we just supply viewers and assume that the host will do a much better job with native functions. 00.08.21 # <__builtin> it seems that there's a separate SOURCES for app builds 00.09.53 # <__builtin> and if there's a keypad it just degenerates to including SOURCES, but if not, only a select subset are built 00.11.21 # <__builtin> ... which seem to be mostly viewers but also a few games 00.13.15 # <__builtin> so there are a couple games built for hosted targets 00.14.08 Quit paulk-collins (Remote host closed the connection) 00.16.45 # <[Saint]> ones that have no hard requirement on fixed size bitmaps I presume. 00.17.07 # <[Saint]> I presume boomshine is one of them. 00.18.46 # <__builtin> yeah 00.19.05 # <__builtin> chopper, clix, and boomshine 00.19.16 # <__builtin> and reversi 00.20.00 # <[Saint]> does clix have a different common/display name? 00.20.02 # <[Saint]> can't recall it offhand. 00.20.25 # <[Saint]> Not that I spend a hell of a lot of time in plugin-land. my own builds just disable plugins globally. 00.21.17 # <__builtin> just clix 00.21.29 # <__builtin> the one with a bunch of colored squares 00.22.32 # <__builtin> it's pretty similar to "Same Game" in sgt-puzzles 00.22.55 # <__builtin> http://www.chiark.greenend.org.uk/~sgtatham/puzzles/js/samegame.html 00.30.00 *** Saving seen data "./dancer.seen" 00.30.41 Quit alexweissman (Remote host closed the connection) 00.32.08 # <[Saint]> Is it reasonably new? 00.32.25 Join alexweissman [0] (~alexweiss@149-160-180-247.dhcp-bl.indiana.edu) 00.32.31 # <[Saint]> where "reasonably new" == +/- ~36 months or so 00.32.57 # <__builtin> probably not 00.33.43 # <__builtin> 2009 or so 00.35.48 # <[Saint]> Hmmm. I see. Selective memory I guess. I don't recall that name at all. 00.38.47 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217) 00.44.19 Quit pamaury_ (Ping timeout: 256 seconds) 00.54.46 Join aaron [0] (a2ed858f@gateway/web/freenode/ip.162.237.133.143) 00.55.10 Nick aaron is now known as Guest54433 (a2ed858f@gateway/web/freenode/ip.162.237.133.143) 00.58.51 Quit Guest54433 (Client Quit) 01.06.53 # <__builtin> would I be correct in stating that rockbox does not control the entire boot process on most devices? 01.13.03 # <[Saint]> Absolutely. 01.20.00 # <[Saint]> You could probably go so far as to say on a good chunk of devices it doesn't control any of it. But I suppose that gets artificially inflated somewhat by the sansas and hosted platforms. 01.20.51 Quit girafe (Read error: Connection reset by peer) 01.22.18 Join girafe [0] (~girafe@LFbn-1-8015-136.w90-112.abo.wanadoo.fr) 01.29.56 Quit alexweissman (Remote host closed the connection) 01.51.35 Quit Senji (Ping timeout: 240 seconds) 02.08.46 Join alexweissman [0] (~alexweiss@149-160-180-247.dhcp-bl.indiana.edu) 02.23.58 Quit ZincAlloy (Quit: Leaving.) 02.25.07 Quit krnlyng (Ping timeout: 246 seconds) 02.30.01 *** Saving seen data "./dancer.seen" 02.35.36 Quit alexweissman (Remote host closed the connection) 02.38.31 Join krnlyng [0] (~liar@178.112.226.73.wireless.dyn.drei.com) 02.42.44 Join Senji [0] (~Senji@85.187.103.250) 02.48.46 Join nlogex [0] (~filip@CPEa84e3f5c8563-CMa84e3f5c8560.cpe.net.fido.ca) 02.50.03 Quit girafe (Quit: Leaving) 02.51.10 Quit Senji (Ping timeout: 270 seconds) 03.02.38 Quit Moarc (Ping timeout: 265 seconds) 03.02.41 Quit Slasheri (Ping timeout: 254 seconds) 03.02.59 Join Moarc [0] (~chujko@a105.net128.okay.pl) 03.03.31 Join Slasheri [0] (~miipekk@xen.ihme.org) 03.03.31 Quit Slasheri (Changing host) 03.03.31 Join Slasheri [0] (~miipekk@rockbox/developer/Slasheri) 03.06.57 Join Senji [0] (~Senji@85.187.103.250) 03.13.57 Quit Senji (Ping timeout: 250 seconds) 03.14.05 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 03.16.30 Join Senji [0] (~Senji@85.187.103.250) 03.16.45 Quit Senji (Read error: Connection reset by peer) 03.17.13 Join Senji [0] (~Senji@85.187.103.250) 03.23.54 Quit Senji (Ping timeout: 265 seconds) 03.30.02 Join Senji [0] (~Senji@85.187.103.250) 03.30.17 Quit Senji (Read error: Connection reset by peer) 03.30.47 Join Senji [0] (~Senji@85.187.103.250) 03.50.37 Quit robertd1 (Ping timeout: 258 seconds) 04.06.02 Join webguest54 [0] (~4bb14c3e@www.haxx.se) 04.10.57 Quit webguest54 (Quit: CGI:IRC (Ping timeout)) 04.30.04 *** Saving seen data "./dancer.seen" 05.39.27 Quit einhirn (Ping timeout: 252 seconds) 05.47.29 Quit nlogex (Ping timeout: 256 seconds) 05.48.25 Join JanC_ [0] (~janc@lugwv/member/JanC) 05.49.37 Quit JanC (Ping timeout: 245 seconds) 05.49.40 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 06.11.04 Join einhirn [0] (~Miranda@p4FC10E75.dip0.t-ipconnect.de) 06.12.47 Join einhirn_ [0] (~Miranda@bsod.rz.tu-clausthal.de) 06.16.07 Quit einhirn (Ping timeout: 250 seconds) 06.17.07 Quit TheSeven (Ping timeout: 245 seconds) 06.17.57 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.28.15 Join chrisb [0] (~chrisb@pool-71-175-243-141.phlapa.east.verizon.net) 06.30.08 *** Saving seen data "./dancer.seen" 06.42.37 Nick [Saint] is now known as [Sinner] (~sinner@rockbox/staff/saint) 08.23.52 Quit einhirn_ (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 08.30.11 *** Saving seen data "./dancer.seen" 08.35.12 Nick [Sinner] is now known as [Saint] (~sinner@rockbox/staff/saint) 08.36.48 Join ender` [0] (krneki@foo.eternallybored.org) 08.50.16 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 08.51.02 Join edhelas [0] (~edhelas@145.133.43.230) 08.57.25 Join petur [0] (~petur@rockbox/developer/petur) 08.57.37 Join The_Prospector|2 [0] (~The_Prosp@c-73-239-179-79.hsd1.wa.comcast.net) 09.00.25 Quit petur (Client Quit) 09.00.43 Quit The_Prospector (Ping timeout: 258 seconds) 09.00.47 Join petur [0] (~petur@91.183.48.77) 09.00.47 Quit petur (Changing host) 09.00.47 Join petur [0] (~petur@rockbox/developer/petur) 09.01.08 Quit edhelas (Ping timeout: 248 seconds) 09.20.24 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 09.20.30 Quit wodz (Client Quit) 09.20.51 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 09.40.12 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 09.52.08 Join advcomp2019 [0] (~advcomp20@65-131-157-74.sxct.qwest.net) 09.52.08 Quit advcomp2019 (Changing host) 09.52.08 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 09.54.55 Quit advcomp2019_ (Ping timeout: 265 seconds) 10.04.32 Quit The_Prospector|2 (Ping timeout: 252 seconds) 10.12.42 Quit pamaury (Ping timeout: 268 seconds) 10.16.16 Join MrZeus [0] (~MrZeus@81.144.218.162) 10.30.12 *** Saving seen data "./dancer.seen" 10.31.19 Join bzed [0] (~bzed@shell.bzed.at) 11.21.01 Join elensil [0] (~edhelas@2001:1c02:1903:d800:a5ef:9915:d112:99e8) 11.25.30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.30.52 Quit prg318 (Ping timeout: 245 seconds) 11.32.52 Join prg318 [0] (~prg318@deadcodersociety/prg318) 11.35.18 # Build Server message: 3New build round started. Revision 8e82839, 255 builds, 13 clients. 11.36.29 Quit MrZeus (Read error: Connection reset by peer) 11.37.15 Join MrZeus [0] (~MrZeus@81.144.218.162) 11.44.14 # Build Server message: 3Build round completed after 535 seconds. 11.44.15 # Build Server message: 3Revision 8e82839 result: All green 11.53.43 # Build Server message: 3New build round started. Revision 5c50efc, 255 builds, 13 clients. 12.03.09 # Build Server message: 3Build round completed after 567 seconds. 12.03.11 # Build Server message: 3Revision 5c50efc result: All green 12.03.12 # Build Server message: 3New build round started. Revision a983859, 255 builds, 13 clients. 12.05.34 Join The_Prospector [0] (~The_Prosp@unaffiliated/cornman) 12.13.29 # Build Server message: 3Build round completed after 618 seconds. 12.13.30 # Build Server message: 3Revision a983859 result: All green 12.13.31 # Build Server message: 3New build round started. Revision 1c97083, 255 builds, 12 clients. 12.22.27 # Build Server message: 3Build round completed after 536 seconds. 12.22.28 # Build Server message: 3Revision 1c97083 result: All green 12.22.29 # Build Server message: 3New build round started. Revision af81cc4, 255 builds, 12 clients. 12.30.15 *** Saving seen data "./dancer.seen" 12.35.39 # Build Server message: 3Build round completed after 792 seconds. 12.35.40 # Build Server message: 3Revision af81cc4 result: All green 12.45.34 Join rela_ [0] (~x@p200300764D16D100B99FD2B857A1F0EC.dip0.t-ipconnect.de) 12.45.46 Quit rela (Read error: Connection reset by peer) 12.58.12 Join pamaury_ [0] (~quassel@wks-50-63.mpi-sws.org) 13.05.29 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:24f5:a979:5299:889e) 13.10.42 # Build Server message: 3New build round started. Revision 9ca8bd6, 255 builds, 13 clients. 13.11.24 Join rlnd [0] (~smuxi@31-211-200-227.customers.ownit.se) 13.20.42 # Build Server message: 3Build round completed after 601 seconds. 13.20.43 # Build Server message: 3Revision 9ca8bd6 result: All green 13.20.44 # Build Server message: 3New build round started. Revision 17277fa, 255 builds, 13 clients. 13.31.37 # Build Server message: 3Build round completed after 653 seconds. 13.31.37 # Build Server message: 3Revision 17277fa result: All green 13.31.39 # Build Server message: 3New build round started. Revision ac0fc74, 255 builds, 13 clients. 13.37.07 Quit Senji (Ping timeout: 245 seconds) 13.42.28 # Build Server message: 3Build round completed after 650 seconds. 13.42.29 # Build Server message: 3Revision ac0fc74 result: All green 13.50.05 Join skapazzo [0] (~skapazzo@151.9.205.1) 14.05.36 Quit alucryd (Remote host closed the connection) 14.06.55 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 14.12.37 Join robertd1 [0] (~root@201.211.53.103) 14.30.17 *** Saving seen data "./dancer.seen" 14.38.48 Join girafe [0] (~girafe@LFbn-1-8015-136.w90-112.abo.wanadoo.fr) 15.02.31 Join paulk-blaze [0] (~paulk@no3.u-bordeaux.fr) 15.10.02 Quit marex-cloud () 15.10.24 Join marex-cloud [0] (sid137234@gateway/web/irccloud.com/x-ecjopzxxensugmdm) 15.18.08 Quit Moarc (Ping timeout: 260 seconds) 15.18.08 Quit froggyman (Ping timeout: 260 seconds) 15.18.27 Join Moarc [0] (~chujko@a105.net128.okay.pl) 15.18.36 Quit krnlyng (Ping timeout: 260 seconds) 15.19.40 Quit Tristitia (Ping timeout: 246 seconds) 15.20.07 Quit wodz (Quit: Ex-Chat) 15.23.19 Join krnlyng [0] (~liar@178.112.226.73.wireless.dyn.drei.com) 15.25.37 Join froggyman [0] (~frogs@unaffiliated/froggyman) 15.38.37 Join Tristitia [0] (~tristitia@static-ip-69-64-50-196.inaddr.ip-pool.com) 15.39.46 Quit paulk-blaze (Quit: Leaving) 15.59.53 Join amayer [0] (~amayer@mail.weberadvertising.com) 16.06.25 Join fujisan_ [0] (~fujisan@unaffiliated/fujisan) 16.13.34 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 16.26.13 Part robertd1 16.30.18 *** Saving seen data "./dancer.seen" 16.46.24 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 16.46.52 Quit dfkt (Client Quit) 16.47.52 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 17.06.01 Quit utrack (Ping timeout: 258 seconds) 17.06.08 Join nlogex [0] (~filip@CPEa84e3f5c8563-CMa84e3f5c8560.cpe.net.fido.ca) 17.06.36 Join utrack [0] (~utrack@21422.s.t4vps.eu) 17.17.36 Join PurlingNayuki [0] (~Thunderbi@114.242.249.250) 17.26.12 Quit petur (Quit: Connection reset by beer) 17.30.39 Quit PurlingNayuki (Ping timeout: 250 seconds) 17.39.28 Quit Rower (Quit: Hmmm...) 17.43.28 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 17.46.06 Quit pamaury_ (Remote host closed the connection) 17.49.23 Join scorche|sh [0] (~scorche@squisch.net) 17.49.23 Quit scorche|sh (Changing host) 17.49.23 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 17.50.43 Quit pamaury (Ping timeout: 248 seconds) 18.05.51 Quit elensil (Quit: Leaving.) 18.07.05 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.25.00 Quit nlogex (Ping timeout: 258 seconds) 18.25.25 Join nlogex [0] (~filip@CPEa84e3f5c8563-CMa84e3f5c8560.cpe.net.fido.ca) 18.30.21 *** Saving seen data "./dancer.seen" 18.35.24 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 18.55.41 Quit rela_ (Quit: Leaving) 19.25.50 Join Link8 [0] (~me@145.133.168.70) 19.32.56 Join rela [0] (~x@pdpc/supporter/active/rela) 19.44.12 # <[Saint]> Hmmmm. 19.44.32 # <[Saint]> Why are we getting build round notifications, but no commit notifications? 19.44.47 Quit Galois (Ping timeout: 260 seconds) 19.45.18 # [Saint]: no idea, I never quite understood the bluebot magic 19.46.44 # <[Saint]> I am writing another bot presently. Well, rather, I am pulling apart a much, much, much more complex bot and stripping it down to the bare essentials we would need. 19.47.16 # <[Saint]> I would really love to get a look at bluebot though. 19.47.59 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 19.48.46 # <[Saint]> One cute thing I noticed is that fs-bluebot doesn't seem to have any magic to determine /where/ it should look for Gerrit tags 19.49.26 Nick [Saint] is now known as g123 (~sinner@rockbox/staff/saint) 19.49.34 # like so 19.49.55 # Hmmm. Interesting. 19.50.21 # g123: testes 19.50.21 Nick g123 is now known as [Saint] (~sinner@rockbox/staff/saint) 19.50.23 # 3Gerrit review #123 at http://gerrit.rockbox.org/r/123 : 3Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini 19.50.34 # <[Saint]> There we go. 19.51.08 # interesting... yeah a new bot with the code would be nice 19.51.15 # <[Saint]> I noticed that a couple of days ago when someone's nick set it off. 19.51.20 # [Saint]: that "magic" is simply a regexp :) 19.51.38 # but it's not the nick, it's the nick being mentioned 19.51.49 # r'([rR]eview\s+|[Gg](errit)?) *#?([0-9]+)([^0-9a-zA-Z]|$)' 19.52.29 # <[Saint]> right, I should've been more clear. anyway, you've inspired me to ignore "g***:" 19.52.39 # I thought the syntax was g#number 19.52.51 # <[Saint]> AFAIK, it should be. 19.53.02 # well, in the beginning we had g#, but then we also had g, and gerrit 19.53.11 # <[Saint]> Aha. 19.53.15 # oh, I was never aware of that 19.53.17 # but we could simply always require the # 19.53.33 # I think most people use the # 19.53.36 # I've seen g123 being used quite some times. 19.53.37 # 3Gerrit review #123 at http://gerrit.rockbox.org/r/123 : 3Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini 19.53.54 # but I don't see a problem in restricting that. Those false alerts are a bit annoying ... 19.53.56 # <[Saint]> IIRC, somethingsomethingfoog123 triggers it too. 19.53.57 # 3Gerrit review #123 at http://gerrit.rockbox.org/r/123 : 3Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini 19.54.06 # <[Saint]> yeah. 19.54.12 # sure, because it's g ;-) 19.54.27 # and requiring a space before it breaks (g#) 19.54.30 # <[Saint]> no, it's "*g" ;) 19.54.39 # <[Saint]> they're distinct. 19.54.40 # or that :D 19.55.17 # \ and then we had g# as well as g # so ... 19.55.34 # <[Saint]> any idea why the commit notifications died? 19.55.56 # no, they should work. 19.56.12 # ah, commit notification. We only had build notifications from the bot 19.56.13 # <[Saint]> they ded. RIP. 19.56.30 # (or whatever the regex engine expects for a (left) word boundary) 19.56.45 # <[Saint]> Ah, what handles the commit nook notifications? I thought it was bluebot that did that? 19.56.53 # hmm, last build was ac0fc74 and that was announced in the channel 19.56.55 # <[Saint]> *hook 19.57.08 # <[Saint]> Oh, I misunderstood. 19.57.26 # no. I have a build client running on the same box as bluebot, and that build client pushes the notifications to bluebot 19.57.40 # <[Saint]> ahhh. 19.57.48 # <[Saint]> I wondered how you were doing that. 19.57.50 # some weird socket interface thingy. I don't like it too much but it works ;-) 19.58.10 # so when the build client dies the channel notifications stop 19.58.18 # <[Saint]> right. makes sense. 19.59.37 # I should review that code ... 19.59.51 # <[Saint]> If a client ends up being so shit that it can't compete in the build system, and never gets passed builds...does it still get notified of the builds? 20.00.08 # <[Saint]> As far as I'm concerned the only really interesting metric is that builds have started. 20.00.15 # and then there's still that ssl thing about Rockbox Utility open :( 20.00.28 # yes, I'm forwarding the messages the build client gets from the build server. 20.00.30 # <[Saint]> I figure I could abuse the rating system for build clients to artificially kill my clients reputation. 20.00.45 # and if the build server finds a client to be too slow it simply stops its build and uses another client 20.00.58 # <[Saint]> so I never actually get builds, but still get notitfied. 20.01.05 # but that's a build server thingy 20.01.05 # <[Saint]> cheating, but...should work for what I need. 20.01.39 # <[Saint]> well, it is and it isn't. iirc, the reputation is stored client side? 20.01.41 Join lebellium [0] (~chatzilla@89-93-179-5.hfc.dyn.abo.bbox.fr) 20.01.59 # that's kinda what I'm doing here. Though my client does get builds. 20.02.01 # <[Saint]> I'd need to look again but I recall this just being stored in a plain text file client side. 20.02.11 # it's one of the clients that provide the latex toolchain :) 20.02.14 # <[Saint]> I figure I'll just artifically shit the bed. 20.03.26 # <[Saint]> it makes some sense for reputations to be stored client side so if a person running a build client fixes their shit up they aren't still ignored by the build system I guess. I may be talking out my ass though. 20.03.40 # providing no useable toolchain might work as well :) 20.04.07 # <[Saint]> I think if it reports no usable build chain it /does/ get ignored. 20.04.12 # <[Saint]> but I might be wrong on that. 20.04.27 # <[Saint]> If it does it for too long. 20.05.07 # What's this "reputation" you mention? 20.05.49 # hmm, dev.cgi still shows only 0's when hovering over the state of a build 20.06.10 # * gevaerts doesn't really understand what [Saint] is proposing 20.06.57 # <[Saint]> gevaerts: aren't there client side metrics stored on builds completed and times taken to do so which is used to favor who gets handed what in the next rounds? 20.07.10 # Well, to decide 20.07.12 # I think he wants to mess with the score of his client to avoid geting builds 20.07.17 # I wouldn't call it "favor" 20.07.18 # <[Saint]> right 20.07.38 # But if you want a notify-only client, why would you give it the same id as a build client? 20.08.39 # <[Saint]> I wouldn't. I'd set an entirely new instance up and then just artificially puke on the score/reputation. 20.08.52 # Why? 20.09.26 # <[Saint]> Is there some other way of doing this you're withholding that I'm obviously not aware of with the existing build system? 20.09.47 # Doing what? I still don't get what you're trying to achieve 20.09.57 # <[Saint]> I want to know when a build round has been handed out. 20.10.27 # what happens if you try to start a build client that hasn't any useable toolchains? 20.10.29 # <[Saint]> for...reasons. 20.11.02 # <[Saint]> guess I'll find out after coffee starts to kick in. 20.11.26 # Easy 20.11.37 # <[Saint]> Well, do share. 20.11.48 # just tried it. Set --archlist=, 20.11.53 # Install an obsolete toolchain, and then perl -s rbclient.pl -username=something -password=something -clientname=something -archlist='arm' -buildmaster=buildmaster.rockbox.org -port=19999 20.12.03 # Oh, , works? Great! 20.12.23 # Better than reusing those old compilers I forgot to uninstall :) 20.12.24 # well, the client did connect. No idea if it will get any info from the server though 20.12.35 # <[Saint]> But won't I need to tell someone what I'm doing so no one culls it from the build system? 20.12.38 # I don't see wht it shouldn't 20.12.51 # me neither. 20.12.56 # [Saint]: you do get general information about the build round 20.13.14 # <[Saint]> semi-regularly non-contributing clients get disabled, I thought? 20.13.16 # leaving archlist empty didn't work (it tells me I need to provide all arguments). But since it uses toolchain1,toolchain2 ... 20.13.23 # <[Saint]> I guess I'd need to say "hey, leave me alone" or so. 20.13.52 # why not just do some cheap builds? 20.14.11 # No 20.14.22 # I have my client running mostly to have a client that provides latex, but I also announce sdl. Doesn't hurt, even if the machine is slow 20.14.26 # Broken clients get disabled 20.14.32 # Usually by me, when I notice 20.15.25 # <[Saint]> does 'never actually contributes a build, or even tries, ever' not count as broken? If not, sweet. 20.15.28 # <[Saint]> But I guess bluebrother is right, I just like to segregate things. 20.16.01 # just announce sdl, it will build some checkwps things or so. No biggie 20.16.03 # Broken clients get disabled manually 20.16.09 # There's no automated system 20.18.06 # <[Saint]> it's mildly annoying that I should even need to want to monkey the system like this, but I understand wholeheartedly why it never occurred to anyone to add a hook solely for notification to the build system. 20.19.24 # All you do is connect and tell the server you have no toolchains 20.19.29 # That's not *that* terrible 20.20.58 # I think there was discussion about this (*quite* some time back), and it kinda ended that it would be as simple as running a client that has no usable toolchains 20.21.12 Quit fujisan_ (Quit: Textual IRC Client: www.textualapp.com) 20.21.43 # pamaury: do you have some things to try out on E580 or A850? 20.21.57 # <[Saint]> If you're wondering, bluebrother, I'm not muscling in on your territory - so to speak. Or creating redundancy. 20.22.06 # <[Saint]> This bot will only speak when spoken to. 20.22.13 # <[Saint]> And even then only in privmsg. 20.22.58 # [Saint]: I have no problem with you running another bot 20.23.19 # <[Saint]> I'm sure people would if we were both yelling about build metrics in channel. :) 20.23.36 # bluebot came to life simply because some people thought it would be useful and I was kinda interested in a programming excercise back then :) 20.23.49 # [Saint]: I'm not people :D 20.24.08 # <[Saint]> yeah, it is useful. just making it clear that there's two distinct goals. 20.24.30 # oh, it's already 5 years ... though I've rewritten it 2 years ago 20.24.44 # <[Saint]> primary goal of this is spooky analytics. 20.25.52 # weee! 20.25.53 # <[Saint]> logbot's pervy stalker cousin. 20.26.01 # * bluebrother hides 20.30.25 *** Saving seen data "./dancer.seen" 20.33.52 # lebellium: yeah, but first you need to build the toolchain 20.34.05 # get g#1424 20.34.08 # 3Gerrit review #1424 at http://gerrit.rockbox.org/r/1424 : 3Initial commit for the Sony NWZ linux port and NWZ-E460 (WIP) by Amaury Pouly 20.41.14 Join TheLemonMan [0] (~root@unaffiliated/thelemonman) 20.41.59 # pamaury: got 20.42.13 # gotten* 20.44.11 # lebellium: ok, now make sure you have installed on your system at least libmpfr-dev and libmpc-dev 20.44.35 # and libgmp-dev 20.44.54 # once done, to go to tools, run rockboxdev.sh and select the arm-app 20.47.06 # sudo apt-get libmpfr-dev? 20.48.25 # something like that 20.48.41 # E: Invalid operation libmpfr-dev 20.48.47 # but not exactly as it should :D 20.49.19 # apt-get install 20.56.16 # RBDEV_PREFIX=~/arm-sony-linux-gnueabi ./rockboxdev.sh is OK? 20.58.33 # lebellium: actually the toolchain is now call arm-rockbox-linux-gnueabi 20.58.43 # arf 20.58.47 # otherwise yes it is ok 20.58.56 # I already run it 20.58.57 # I mean it's a small detail 20.59.01 # that's fine 21.07.45 # hum I don't know if it finally complete or if I mistakenly cancelled it 21.07.55 # ROCKBOXDEV: gcc-4.9.4/make 21.07.56 # ^C 21.07.58 # ubuntu@ubuntu-VirtualBox:~/rockbox/tools$ 21.14.58 Quit chrisb (Ping timeout: 265 seconds) 21.17.37 # lebellium: you cancelled (^C) is Control-C 21.17.53 # grrr 21.18.03 # you can restart from the last step with a special command 21.18.20 # can you pastebin the output of the tool ? 21.19.04 # http://pastie.org/private/tvrbqesqxacjyutluvk5xq 21.20.15 # RESTART=gcc-stage1 RBDEV_PREFIX=~/arm-sony-linux-gnueabi ./rockboxdev.sh 21.20.34 # select arm-app against and it should restart at the same step 21.21.30 # mkdir: cannot create directory `build-gcc-4.9.4': File exists 21.22.34 # ah you need to rm -rf the build dir 21.22.48 # something like: 21.22.48 # rm -rf /tmp/rbdev-build/build-gcc-4.9.4 21.23.25 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 21.23.33 Quit cc___ (Client Quit) 21.24.20 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 21.33.48 Join edhelas [0] (~edhelas@145.133.43.230) 21.36.43 # pamaury: gcc-4.9.4/make lasts forever! 21.37.54 # lebellium: you are compiling a compiler! (twice) 21.38.14 # the whole things takes about 45min on my i5 machine 21.38.22 # whaouh 21.38.37 # I also have a tired i5-540m but in Virtualbox... 21.58.07 # bluebrother: what is the "policy" to pull libraries in rbutil ? I'm starting to write a mknwzboot for Sony players and I need some crypto that we don't already have (DES). Currently I'm use libcrypto++, will that be a problem when we add it to rbutil? 22.03.00 Quit michaelni (Ping timeout: 264 seconds) 22.07.02 Join petur [0] (~petur@rockbox/developer/petur) 22.11.45 Quit pookie_ (Quit: All for nothing) 22.15.23 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 22.15.38 # hi pamaury :) 22.17.02 # hi 22.18.21 Quit ZincAlloy (Quit: Leaving.) 22.20.03 Quit nlogex (Ping timeout: 248 seconds) 22.30.27 *** Saving seen data "./dancer.seen" 22.39.36 # pamaury: I guess I need your i5. Mine is boring^^ 22.43.44 # haha 22.48.47 # pamaury: pff I aborted it again, just at the ened 22.49.09 # ROCKBOXDEV: Done! 22.49.10 # ROCKBOXDEV: Make sure your PATH includes /home/ubuntu/arm-sony-linux-gnueabi/bin 22.49.12 # ubuntu@ubuntu-VirtualBox:~/rockbox/tools$ ^C 22.49.25 Quit paulk-collins (Remote host closed the connection) 22.49.42 # I just wanted to copy and paste 22.50.15 Quit bluebrother (Ping timeout: 240 seconds) 22.51.00 Quit fs-bluebot (Ping timeout: 258 seconds) 22.52.05 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 22.54.57 Join nlogex [0] (~filip@CPEa84e3f5c8563-CMa84e3f5c8560.cpe.net.fido.ca) 22.56.56 # lebellium: I think it was done, since it said Done! 22.57.12 # I don't know if I can trust it :D 22.57.31 # can I check easilyN 22.57.33 # ? 22.58.34 # run: 22.58.34 # /home/ubuntu/arm-sony-linux-gnueabi/bin/arm-rockbox-linux-gnueabi-gcc 22.59.32 # sorry 22.59.37 # /home/ubuntu/arm-sony-linux-gnueabi/bin/arm-rockbox-linux-gnueabi-gcc -v 22.59.41 # and pastebin the result 23.00.00 # ubuntu@ubuntu-VirtualBox:~/rockbox$ /home/ubuntu/arm-sony-linux-gnueabi/bin/arm-rockbox-linux-gnueabi-gcc 23.00.02 # arm-rockbox-linux-gnueabi-gcc: fatal error: no input files 23.00.03 # compilation terminated. 23.00.07 # ah 23.00.52 # here you are http://pastie.org/private/imj9wvrikgampotnnezv3w 23.01.38 Quit nlogex (Read error: Connection reset by peer) 23.02.18 Join nlogex [0] (~filip@CPEa84e3f5c8563-CMa84e3f5c8560.cpe.net.fido.ca) 23.02.45 # it looks all right 23.03.06 # great 23.03.43 # Ok, I am still creating the configure entries for the E580 and A850, wait for 5min 23.03.44 # I didn't expect it to last the whole night but at least we can now on serious things from tomorrow :D 23.03.55 # work* 23.04.01 # But yeah maybe better wait until tomorrow ;) 23.04.20 # yeah, it's already quite late. You're available tomorrow night? 23.04.34 # yes, around the same time 23.05.05 # ok, thanks for your help and see you 23.05.29 Join fs-bluebot [0] (~fs-bluebo@xd9baf89f.dyn.telefonica.de) 23.05.32 # I'll read the logs if needed 23.07.12 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 50.0.2/20161129173726]) 23.13.44 # <[Saint]> sudo mount -o remount,rw /dev/mmcblk0p1 ; touch /boot/ssh 23.13.50 # <[Saint]> sudo mount -o remount,ro /dev/mmcblk0p1 23.14.02 # <[Saint]> ah, shit. 23.14.08 # <[Saint]> *whistles* 23.17.20 # sudo mount -o loop [Saint] [Saint] 23.17.48 # ;) 23.19.08 # <[Saint]> ps ax | grep pamaury 23.19.08 # <[Saint]> sudo kill ~pamaury@rockbox/developer/pamaury 23.19.18 # <[Saint]> :p 23.20.56 Quit Link8 (Ping timeout: 250 seconds) 23.21.23 # * pamaury is shocked but not killed 23.22.17 # <[Saint]> sudo pkill -f pamaury 23.22.25 # ah damn 23.23.03 # * pamaury has a patched kernel to intercept the KILL signal 23.26.38 # <__builtin> kill -SIGHUP `pidof pamaury` 23.26.58 # ah that's clever 23.31.22 Quit ender` (Quit: How many SEO experts does it take to change a light bulb, lightbulb, light, bulb, lamp, lighting, switch, sex, xxx, hardcore) 23.32.45 Join JanC_ [0] (~janc@lugwv/member/JanC) 23.34.00 Quit JanC (Killed (verne.freenode.net (Nickname regained by services))) 23.34.00 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 23.45.32 Quit [Saint] (Quit: Going down for routine maintenance - estimates downtime 5 minutes (+/- 2 minutes)) 23.48.14 Quit skapazzo (Quit: Lost terminal) 23.54.24 Join [Saint] [0] (~sinner@rockbox/staff/saint)