--- Log for 26.09.121 Server: sodium.libera.chat Channel: #rockbox --- Nick: rb-logbot_ Version: Dancer V4.16 Started: 4 hours and 48 minutes ago 00.04.30 Quit Moriar (Ping timeout: 260 seconds) 00.21.04 Quit massiveH (Quit: Leaving) 00.47.22 # <_bilgus_> speach y I don't even see a way to enable seeing join and leave on this client and don't have the ssh key on thsi machine but I should be able to get my dev machine set up by winter :p 01.16.30 *** Saving seen data "./dancer.seen" 01.45.51 # what is preventing a new 'stable' release? often the answer to any question is to use a dev build first. and there seems very little wrong with the current dev build for daily use. 01.54.20 # i am not underestimating the effort to do a new official release but current rockbox seems very solid. 03.16.31 Quit scorche (Ping timeout: 252 seconds) 03.16.34 *** Saving seen data "./dancer.seen" 03.31.06 Join scorche [0] (~scorche@174-17-179-250.phnx.qwest.net) 03.31.06 Quit scorche (Changing host) 03.31.06 Join scorche [0] (~scorche@user/scorche) 03.33.51 Join whatfor [0] (~whatfor@84-84-97-124.fixed.kpn.net) 03.35.38 # I'm getting nothing but 403 Forbidden on all things rockbox.org. This a general project feature or more a specific visitor targeted feature? 03.58.27 # can't reproduce 04.08.25 # So, specific visitors only. Well, that answers my question. 04.08.39 Join ZincAlloy [0] (~Adium@ip5f5abcae.dynamic.kabel-deutschland.de) 04.11.49 # some ranges are blocked because of spammers/bots 04.18.35 Join lebellium [0] (~lebellium@2a01cb04012c090020a7fd58f221b154.ipv6.abo.wanadoo.fr) 04.18.57 # Apparently at least one false positive that you know of, now. And that's just the top of the iceberg of what's wrong with this approach. But, I'm not here to argue. I wondered if the project is dead. Apparently not, whoever runs the website went off the rails. 04.20.30 # It does mean that my rockbox-capable devices won't get updates or upgrades any time soon. Oh well. 04.21.01 Quit whatfor (Quit: oh well) 05.13.48 # vpn? 05.16.36 *** Saving seen data "./dancer.seen" 06.12.25 # speachy: is their ip even in the blacklist range 06.13.05 # says netherlands 06.45.57 Quit braewoods (Quit: WeeChat 2.8) 06.49.35 Join braewoods [0] (~braewoods@user/braewoods) 07.16.39 *** Saving seen data "./dancer.seen" 07.34.21 # whatfor: the IP you used to connect to IRC isn't in the www block list. 07.35.16 # and, respectfully, grow the fuck up. 07.37.58 # it is easier to complain than give better solutions 07.38.52 # or "here's the IP I'm using, can you unblock me" is another approach 07.39.17 # it might be an IP rang 07.39.27 # IP range, it might be user agent string, who knows. 07.39.43 # didn't provide enough information to actually act upon 07.40.49 # quick, move the site before he returns! 07.42.27 # the old and new sites have the same static block list/rules at the moment. 07.42.45 # though the dynamic stuff IDS stuff is different 07.43.17 # (same setup, but the blocklist is dependent on who tries to break in) 07.44.24 # i assumed so, i was not entirely serious 07.44.30 # I intend to move at least parts of the www blocklist to the dynamic IDS but that'll come after all of this migration stuff is done (moving rockbox infra is only part of it) 07.44.58 # (the dynamic stuff has the advantage of automatically purging entries after some period of time) 07.46.01 # keeping a dynamic site on the public internet these days can be a _lot_ of work. 07.46.02 Quit benjaoming (Ping timeout: 260 seconds) 07.50.29 # especially when foswiki is involved. clunky POS... 07.50.49 # (well, foswiki 1.x; 2.x might be much improved) 08.05.24 Join dconrad [0] (~dconrad@208.38.228.17) 08.16.12 Join benjaoming [0] (~benjaomin@37.139.19.237) 08.27.27 # <_bilgus_> spork a official release is a bunch of work builtin did the last two 08.28.21 # <_bilgus_> we need to get our collective crap together before we can, testing all the devices we claim to support for one.. 08.28.43 # <_bilgus_> or removing targets w no coverage 08.32.43 # there's one known regression at the moment, on 1st-gen sansa ams targets -- USB doesn't work right. 08.32.53 # brought on by using -Os 08.33.46 # though it probably needs retesting since amachronic fixed a couple of USB core issues 08.45.11 # _bilgus_: i get that. not underestimating it. but the standard answer to just about everything recently is 'try the latest dev build'. of course i have no idea how questions are spread over devices. 08.47.10 # spork: We have pretty good basic smoke test coverage at this point; all but hte most esoteric targets are confirmed to at least boot up and play music. 08.47.50 # but there are still some pretty large functional coverage gaps -- for example, that USB issue wasn't reported until just shy of a year after it was introduced. 08.51.00 # people might be generally consirvative and stick to a release build. so it makes sense to be very sure they work. 08.51.12 # exactly 08.51.28 # but we don't know about issues if folks don't test things. :/ 08.53.58 # i only have 3 ams v2 sansa's 08.54.03 # so no help there 08.54.15 # yeah, my only working sansas are v2s 08.55.01 # I have a fuzev1 but only the power/hold switch works thanks to a damaged ribbon cable. 08.57.43 # speachy I have fuze1 08.57.56 # so I get one shot and then I'll never be able to write to the device ever again. :/ 08.59.05 # got another issue: 10% battery after 1h charging. after charger reconnect: 20%. after another reconnect: 16%. 08.59.50 # <_bilgus_> its based on the voltage level 08.59.52 # that's an issue inherent to rechargable batteries, alas. 09.00.11 # so the battery dying? 09.00.11 # <_bilgus_> so perhaps the battery is flaky or even the adc 09.00.36 # there's a voltage bounce around charging/discharging transitions. 09.01.27 # anyway, you can ping me when usb fix will arrive to ams1 09.01.37 # paulcarroty: there were some fixes committed last weekend; I don't think they'd affect UMS but it's worth confirming things are still broken 09.02.17 # <_bilgus_> doesn't mean its got no time left but maybe don't discharge it so far down DoD is a very important thing to liion 09.02.31 # (I really want to get a USB sniff of the failure, but again, whatever I write to my fuzev1 will be the last thing I ever write to it...) 09.02.31 # <_bilgus_> depth of discharge 09.02.57 # <_bilgus_> why not solder some switches in? 09.03.17 # OK, will test the last build later 09.05.59 # power switch of my fuze v2 is just about the worst thing about it 09.06.17 # does anybody know where I can find fuze battery width, length & height? 09.06.25 # then again, it has been through the laundry twice and still works so i cannot really complain 09.08.53 # _bilgus_: I don't think I could have ever soldered someting that fine, even in my more misguided youth. 09.10.30 # and while I think I can bribe someone at work to do this for me, it'll probably cost me more in bribe^H^H^H^H^Hbeer than it would cost to just replace the damn thing. 09.10.40 # paulcarroty: i would google a fuze battery replacement video 09.11.29 # spork: only fuze+ available 09.12.06 # gimme a seco, I'll measure one of the batteries from my pile of broken dreams. 09.14.08 # many fuze+ indeed 09.15.33 # paulcarroty: 37x42mm, 3.8mm thick. which seems to match what's printed on it. 09.15.40 Quit tomato (Ping timeout: 252 seconds) 09.15.48 # though the wiki says it's a 35x42mm (perhaps the v1 is slightly smaller?) 09.16.00 # speachy: huge thanks 09.16.26 # oh, have 4 ams v2's. forgot my clip zip. 09.16.41 *** Saving seen data "./dancer.seen" 09.18.29 Join MarcAndersen [0] (~no_znepna@85.218.172.116) 09.19.44 # Hi. I am trying to build a win32 simulator but get the error /home/marc/rockbox/uisimulator/common/filesystem-sim.c:579: undefined reference to `os_modtime' I remember getting it before and I think there was a patch for it, can someone confirm this? 09.21.31 # And if so please point me in the right direction? 09.24.15 # cross compiling/mingw, cygwin? 09.24.34 # linux, mingw 09.25.37 # wow, found my orignal clip+ with the fried flash. thought I'd tossed it. 09.26.16 # MarcAndersen: I recall beating my head against the win32 sim build a while ago but decided I'd rather go scrub the bathrooms. 09.26.42 # But it worked a few months ago 09.26.51 # Without a patch I think 09.28.20 # the simplest thing to do is create a stub no-op function for os_modtime in the win32 sim code. 09.29.34 # wsl? 09.30.28 # or #ifdef away the call to os_modtime for windows builds 09.32.23 # MarcAndersen: try g#3833 09.32.27 # 3Gerrit review #3833 at https://gerrit.rockbox.org/r/c/rockbox/+/3833 : 3win32: Add a stub for os_modtime() to make sim builds happy by Solomon Peachy 09.33.27 # speachy found https://www.amazon.com/Cameron-Sino-Battery-SanDisk-Toolskits/dp/B01M65KVGN , says 39.40 x 39.80 x 3.90mm, probably this is v2 09.33.41 # what probably broke this was adding support to the simulator for modtime().. which happened this past July 09.34.10 # yep, in commit d6dcb996847 09.34.27 # that's going to be a bit too large, in every dimension 09.34.42 # Can we revert it at some point? 09.35.13 # And I'm not running wsl, it's ubuntu server 09.35.27 # with that patch the build gets much further then blows up with strtol issues in the calculator plugin 09.36.01 # paulcarroty: I wonder if that might not be a fuze+ battery instead. 09.36.16 # Yes, at that time I couldn't build calculator, that's right. 09.36.37 # well, some of the reviews claim it's a litlte larger but still fits. so... up to you to take that chance.. 09.37.04 # Build Server message: 3New build round started. Revision 38b2648f48, 303 builds, 11 clients. 09.37.34 # MarcAndersen: I committed the patch, jut grab latest git code and try again. 09.37.59 # probably should have held off on this until after the infra move but eh, I guess we'll find out what difference the reworked build scores made. 09.38.40 # I should probably add a token windows sim build to the regression farm. 09.39.13 Join petur [0] (~petur@78-21-55-218.access.telenet.be) 09.39.31 # It's running now 09.40.53 # And it built! 09.41.00 # Thanks 09.41.08 # what target? 09.41.32 # I thought it was because i ran rockboxdev yesterday to enable mips in order to compile for my x3 09.41.35 # windows sim builds well on wsl on windows 10 09.41.57 # I just tried a nano 1g 09.42.00 # at least for fiio m3k and shanling q1 09.42.21 # the x3 is what failed in my just-now sim build test 09.48.25 # Build Server message: 3Build round completed after 681 seconds. 09.48.28 # Build Server message: 3Revision 38b2648f48 result: All green 09.53.52 # much better efficiency, yay. 10.05.08 Quit rb-logbot (Remote host closed the connection) 10.05.56 # I can build a win32 sim of the x3 here 10.10.05 # everyone: please hold off on any new commits for the time being; I'm starting data syncing early. 10.13.54 # starting with the buildmaster 10.14.06 # since it's a pretty large database 10.15.34 # What is data syncing in this case? 10.16.14 # migrating databases from one machine to another 10.16.46 # So you are moving the git server or what? 10.16.58 # git was moved a couple of weeks ago 10.17.16 # What are you moving now? 10.17.28 # this is for our automated build system; it gets notified by gerrit when commits occur and generates all of the dev builds (among other per-commit tasks) 10.17.49 # I'm moving everything accessible via www.rockbox.org, builds.rockbox.org, and buildmaster.rockbox.org 10.18.05 # Oh. When do you think it's done and functioning? 10.18.37 # a couple of hours; mostly a matter of waiting for DNS to update. 10.19.07 # buildmaster is self-contained and is safe to move as long as nobody does a commit to git. 10.19.11 # Wow. You are moving the domain? That's a lot of work. Why are you moving it? 10.19.15 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net) 10.19.29 # MarcAndersen: hosting changes is the usual reason 10.19.30 # (actually it's safe to make commits, it's just that the builds won't get triggered) 10.19.51 # MarcAndersen: the server everything is/was on is getting evicted, and its new home won't have the bandwidth to support rockbox's needs. 10.20.12 # so all rockbox stuff is getting moved to a cloud-hosted VPS. 10.20.18 # Wow. Good luck then. 10.34.19 # Do you guys need a packages mirror ? 10.35.37 # nope, we're fine in that regard. 10.35.53 # speachy: where are the mirrors listed? 10.36.43 Quit dconrad (Remote host closed the connection) 10.38.02 # if you use Fosshost for builds, do they also offer mirorrs ? 10.44.45 # yep, all of the above 10.45.10 # buildmaster is now switched btw. 10.46.10 # so is irc logging. 10.48.20 Join dconrad [0] (~dconrad@208.38.228.17) 10.52.35 Quit dconrad (Ping timeout: 252 seconds) 11.02.12 # also sourceforge, osdn 11.07.36 # sourceforge and osdn also provide mirrors ? 11.07.45 # hm ok 11.16.44 *** Saving seen data "./dancer.seen" 11.18.05 # yang: mirrors aren't really necessary at this point in time, at least not enough to be worth the admin overhead. 11.19.05 # after capping off the worst of the bots (which we needed to do for DoS purposes) we're about 250-300GB/mo typically. 11.19.37 Join dconrad [0] (~dconrad@208.38.228.17) 11.20.08 # I am thinking about starting a mirroring project on a hobbyist scale (I would eventually like to expand it with more servers and harddrives) 11.20.36 # it's probably something that doesn't bring any value 11.20.44 # so, it cannot be commercialised 11.21.25 # doing anything on a small scale these days is nearly impossible to commercialize. 11.22.29 # I already sponsor a few mirror, but I would like to cluster all of them later under one big directory, so the user could just click directories and be able to browse files 11.23.25 # there are however fosshost, SF etc. which managed to get sponsorships, so they could expand their service, they provide some monetary value 11.24.05 # I could prbably only get sponsorships in the terms of sponsored hardware or bandwidth or such.... 11.24.31 # I haven't really tried launching the project, but it's on my mind 11.34.09 # best of luck 11.36.34 # hrm, ideas from the peanut gallery, but, how hard would it be to build a purpose built mp3 player with the intention of running rockbox on it? kinda like the pine64 projects.... 11.38.03 Quit dconrad (Remote host closed the connection) 11.38.05 # tl;dr: quite hard. :) 11.38.07 # thanks speachy 11.38.32 # the really expensive part is the physical enclousure. 11.38.55 # since you have to pay for the tooling costs upfront. 11.39.04 # yang "it cannot be commercialised" you can sell your traffic to advertisers. doubt you can earn a lot, probably cover your internet bill plus couple $ over 11.39.24 # 3d printing is okay for prototypes but doesn't scale (economically) for serial production 11.39.58 # serial production wasnt in the plans 11.40.17 # the idea was more a parts list. i dont care about selling them really 11.40.41 # i just have an emotional attachment to this project and dont want to ever not have a rockbox pmp 11.40.47 # in that case you're probably best off starting with the likes of an RPi Zero and bolting on some accessories (dac, display, buttons, battery) 11.41.15 # yeah thats huge tho 11.42.08 # but rhere are devices stillb eing produced that work fine. 11.43.01 # ....okay, all data is synchronized. just waiting for the clock to strike 12 to flip DNS and mark the old sites as retired. 11.43.48 # hrm, the unipi zulu is tiny 11.50.56 # temporary redirect rules and DNS changes staged. 10 minutes until go. 11.53.09 # pine64 cheating with production. they do hardware releases with alpha-stage software. well, anyway better than nothing. 12.04.03 # paulcarroty: how do you sell traffic to advertisers? like placing banner on the main site ? 12.13.57 # ok, everything is done. now it's just a matter of DNS. 12.19.40 # paulcarroty: nevermind the question 12.34.13 # yang: stuff like https://iproyal.com/pawns/ 12.40.12 Join dconrad [0] (~dconrad@208.38.228.17) 12.51.16 # thanks 13.16.47 *** Saving seen data "./dancer.seen" 13.40.58 Quit dconrad (Remote host closed the connection) 13.43.28 Join dconrad [0] (~dconrad@208.38.228.17) 13.58.30 # I wonder if the best option for longetivity is really the ipod 5g... parts are plentiful, relatively easy to open, and afaik, no parts that tend to wear out beyond the battery, which is easy to source 13.58.51 # probably serviceable for many years to come 14.10.44 # <_bilgus_> nephi we need coders, documentation, helpers on the forums, new blood in any area is welcome :) 14.11.54 # i can help with docu, helping on forums. i am not a programmer though. 14.14.25 # <_bilgus_> the documentation is so out of sorts between manuals, forums, wiki plenty of things that no longer apply or have changed since 3.1 14.17.34 # i cannot start on anything today, as ive got a toddler but i can start looking at it this week 14.19.47 # <_bilgus_> what you work on is your choice :) 14.21.49 # kinda a funny thing, some of the sansa e250r branded boxes actually contained regular e250 14.26.50 Quit dconrad (Remote host closed the connection) 14.40.11 Quit Piece_Maker (Quit: ZNC 1.8.2 - https://znc.in) 14.41.47 Join Piece_Maker [0] (~Piece_Mak@cpc95746-bolt17-2-0-cust360.10-3.cable.virginm.net) 14.45.15 Join amachronic [0] (~amachroni@user/amachronic) 15.03.29 # i've got USB DMA working on the M3K and Q1. hopefully I didn't break anything else in the process :) 15.14.15 Quit ZincAlloy (Quit: Leaving.) 15.16.49 *** Saving seen data "./dancer.seen" 15.26.16 # speachy: tested master build on fuze - still no USB mass storage 15.37.09 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:8dc9:d002:e057:e960) 15.39.03 Quit lebellium (Remote host closed the connection) 15.39.25 Join lebellium [0] (~lebellium@2a01cb04012c090020a7fd58f221b154.ipv6.abo.wanadoo.fr) 15.51.05 # amachronic: when sticking in the Sony headphones into m3k, I need to push quite hard that it connects, do I have the right jack for the plug ? 15.51.39 # I get the sound though 15.53.36 # it's a normal 3.5mm jack, as far as I know. 16.18.51 # speachy, _bilgus: USB stuff is up on gerrit now, review / testing would be appreciated! everything appears to work good on my end. 16.49.59 Join dconrad [0] (~dconrad@208.38.228.17) 16.51.24 Quit amachronic (Quit: amachronic) 16.59.23 Quit lebellium (Quit: Leaving) 17.01.21 # <_bilgus_> amachronic I have the Clip+ zip and fuze v2 I should be able to get testing by mid week 17.04.55 Quit dconrad (Remote host closed the connection) 17.05.35 Join dconrad [0] (~dconrad@208.38.228.17) 17.09.16 Quit dconrad (Remote host closed the connection) 17.09.20 # _bilgus_: you seem to know the Rockbox ui better than most. how well would it translate to a widget based system like GTK+ 17.09.22 # ? 17.09.30 # or does it need a low level drawing canvas to even work? 17.14.47 Quit Piece_Maker (Quit: ZNC 1.8.2 - https://znc.in) 17.16.51 *** Saving seen data "./dancer.seen" 17.19.57 Join Piece_Maker [0] (~Piece_Mak@cpc95746-bolt17-2-0-cust360.10-3.cable.virginm.net) 17.22.36 # just as a quick sanity check, the www site working for everyone? 17.23.05 # amachronic: awesome, thanks for a nice split-up series 17.23.45 # It works here. 17.25.47 # works here 17.31.47 # <_bilgus_> braewoods, No idea how you would use a windowed GUI on most of these devices I'm sure you could leverage your own widgets but by the time you did all that i'm not so sure itd be worth it .. Not that I haven't considered options, buttons and checkboxes 17.32.17 # _bilgus_: ah, i was asking for a new port. an alternative to SDL I guess. 17.33.01 # i wasn't sure how flexible the existing setup is for mapping to a widget based toolkit. 17.33.31 # some people are asking for a pinephone / pinetab port of rockbox. GTK+ is one way to achieve that. 17.35.40 # <_bilgus_> It probably wouldnt be too terrible once you got the differences between device displays smoothed out ( a lot still spills out needs better abstraction) 17.36.24 # they don't want a "port" of rockbox, they want rockbox with a native UI appropriate to that sort of device. 17.38.08 # but it's probably worth redoing our SDL port to use SDL2 now. 17.38.27 # * speachy pages Mr. Somebody. 17.39.43 # speachy: which for a pinephone would best be done with a toolkit that can be modified by the regular themes at work. 17.39.52 # I am having a bit of crackling sound from the voice on my clip zip which is not on my other players, like very small pause clicks in the speech. Can you reproduce this? 17.41.34 # It mostly happens when reading long things, like the playing time screen or the rockbox info screen. 17.42.15 # although to be honest i don't see a lot of value in what amounts to a desktop port 17.42.34 # there's plenty of other good audio players for desktop Linux 17.42.42 # precisely. 17.43.20 # it's the same argument against a port to that bluetooth SoC -- it's a lot of work, for something that shares little commonality with the rest of the codebase. 17.44.53 # and you might as well use native widgets for the WPS too, with proper native touchscreen interfacing instead of what we do. 17.45.46 # well if doing GTK+, the toolkit handles all that crap for us. 17.46.29 # why put our own absractions on top of gtk's? 17.46.49 # even so i'd prefer to just use deadbeef 17.47.19 # it basically does everything rockbox does in a desktop app 17.47.43 # it'll be less work to build a new media player from scratch using GTK/QT/whatever. 17.47.57 # they also have their own accessibility approaches 17.48.17 # the entire user interaction paradigm is different from what we target. 17.48.36 # i still appreciate pine's efforts though. we do have a legitimate problem with finding new hardware to target. 17.49.50 # the SoC they showed us had more RAM than I expected. 17.49.56 # 1MB rougjhly. 17.50.27 # probably enough for a stripped down core but not much else. 17.51.08 # i'm just puzzled. 1MB is the best they can do? i know router SOCs with more RAM than that. 17.51.28 # my microuter n300 has 128MB ... 17.51.38 # it's a mediatek chip even. 17.51.41 # is it on-package? 17.51.45 # external. 17.51.47 # DDR 17.51.48 # there ya go 17.51.49 # 2 17.51.51 # i believe 17.51.57 # this is 1MB on-chip SRAM 17.52.04 # with no option for external ram 17.52.19 # most of the time DRAM is external anyway 17.52.27 # there are SoCs that have on-package DRAM (eg the ingenic ones, allwinner FC1xx and V3/V3s) 17.52.38 # but they all cost more 17.53.09 # well we basically need a modest amount of RAM to give the full experience 17.53.49 # there are SoCs that use stacked RAM-on-top-of-package (eg the SoC used by the RPi) 17.54.22 # it's funny how the RPi has 2GB of RAM but the board only costs $35 17.54.27 # go figur 17.54.29 # -e 17.54.48 # they've cost-optimized the heck out of it, managed to get preferential pricing, and of course, have pretty large volumes 17.55.14 # yea, a lot more of those floating around than pine stuff 17.55.38 # almost makes me wonder if a pi zero would be a good board for rockbox 17.55.44 # X) 17.56.15 # it's a good start, but needs a lot more to be usable. 17.56.46 # porting rockbox to work on a rpi to replace a regular linux setup would be a good start to developing a custom hardware solution 17.57.11 # lots of accessories and options for them 17.57.32 # pi zero being the end goal, ideally. 17.57.47 # the existing video stuff could be used to drive a screen 17.57.54 # gpio for buttons 17.58.05 # over hdmi sure, but that's expensive. 18.01.30 # I do think that in the end it's going to take arranging for an exising OEM to crank out a large batch that we pay for in advance, and eventually sell to whomever wants it. 18.02.04 # a sufficiently large order and we'll probably get complete schematics and our logo on the case. 18.02.33 # and then we'll find out just how much of a market there truly is for a rockbox player. 18.03.46 # probably not enough if existing data is anything to go by 18.08.51 Quit ZincAlloy (Quit: Leaving.) 18.15.09 # my wild-ass guess is a few hundred units. 18.15.49 # maybe more if it's in the $60-80 range. 18.23.56 # the only things still hitting the old site are bots 18.24.00 # excellent. 18.27.09 # id buy 2 18.27.55 # Build Server message: 3New build round started. Revision 6d98c9e6b2, 303 builds, 11 clients. 18.28.06 # ok, let's see how everything fares. :D 18.29.22 # Build Server message: 3Build round completed after 86 seconds. 18.29.27 # Build Server message: 3Revision 6d98c9e6b2 result: 303 errors 0 warnings 18.29.28 # ....quite badly! 18.33.24 # Build Server message: 3New build round started. Revision 6d98c9e6b2, 303 builds, 11 clients. 18.34.32 # Build Server message: 3Build round completed after 69 seconds. 18.34.33 # Build Server message: 3Revision 6d98c9e6b2 result: All green 18.35.14 # How could it build so fast? Doesn't it normaly take 10 minutes? 18.36.15 # Build Server message: 3New build round started. Revision 6d98c9e6b2, 303 builds, 8 clients. 18.36.31 # a permission problem in the upload directory 18.36.47 # Oh 18.40.38 Quit TorC (Quit: Vanishing into the mist) 18.40.53 Join TorC [0] (~Tor@fsf/member/TorC) 18.45.34 # it's still screwed up, working on fixing. there will be another attempt on this in a bit. 18.47.45 # Build Server message: 3Build round completed after 691 seconds. 18.47.46 # Build Server message: 3Revision 6d98c9e6b2 result: All green 19.03.23 # Build Server message: 3New build round started. Revision 6d98c9e6b2, 303 builds, 11 clients. 19.03.29 # third try's the charm, I hope. 19.12.59 Quit petur (Remote host closed the connection) 19.13.39 # Build Server message: 3Build round completed after 616 seconds. 19.13.40 # Build Server message: 3Revision 6d98c9e6b2 result: All green 19.16.54 *** Saving seen data "./dancer.seen" 19.30.43 # Build Server message: 3New build round started. Revision 6d98c9e6b2, 303 builds, 11 clients. 19.31.32 # braewoods: you're getting a fatal error to build some stuff. sansaclipboot was what blocked you 19.31.53 # speachy: log? 19.32.04 # that's what the server reported based on what your client reported. 19.32.34 # " Fatal build error: Command not found. Blocking meh-braewoods. " when handed 'sansaclipboot' 19.32.54 # so try to build that by hand and see what pops out 19.38.24 # i'll wait for an idle period 19.41.27 # Build Server message: 3Build round completed after 645 seconds. 19.41.28 # Build Server message: 3Revision 6d98c9e6b2 result: All green 19.49.38 # there, fixed the last straggler. 19.50.00 # all future builds will be fine 21.07.24 Quit MarcAndersen (Read error: Connection reset by peer) 21.16.55 *** Saving seen data "./dancer.seen" 22.16.57 Quit nephi (Remote host closed the connection) 22.34.50 Join nephi [0] (~butts@2600:1700:be60:2b60::3e) 22.45.10 Quit Moriar (Ping timeout: 250 seconds) 23.16.57 *** Saving seen data "./dancer.seen" 23.23.13 Quit scorche (Ping timeout: 252 seconds) 23.31.14 Join scorche [0] (~scorche@97-124-42-45.phnx.qwest.net) 23.31.14 Quit scorche (Changing host) 23.31.14 Join scorche [0] (~scorche@user/scorche)