Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2022-12-09

00:21:34 Join advcomp2019 [0] (~advcomp20@user/advcomp2019)
01:19:36 Quit amiconn (Quit: - Chat comfortably. Anywhere.)
01:19:36 Quit pixelma (Quit: .)
01:20:32 Join amiconn [0] (
01:20:34 Join pixelma [0] (
01:21:40_bilgusugh Geaverts you still around?? Ive sent a thread to the archives and don't have the access to restore it
01:22:22_bilgusgevaerts and can't spell your name appropriately either
01:33:24 Quit tomato (Ping timeout: 248 seconds)
01:53:44***Saving seen data "./dancer.seen"
02:00:19 Quit CH23_M (Read error: Connection reset by peer)
02:00:42 Join CH23_M [0] (~CH23@revspace/participant/ch23)
02:01:29 Quit fourHZ (Quit: Client closed)
02:02:41 Join fourHZ [0] (
03:27:01 Join mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
03:27:09 Quit mink (Read error: Connection reset by peer)
03:28:28 Join mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
03:53:46***Saving seen data "./dancer.seen"
04:26:44gevaerts_bilgus: I am. Let me have a look
04:27:19gevaertsWhere does it need to go?
04:33:19gevaerts_bilgus: I moved it back to Hardware and edited the redirect post accordingly, although maybe that should be removed entirely?
05:43:05 Quit mink (Remote host closed the connection)
05:44:35 Join mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
05:53:48***Saving seen data "./dancer.seen"
06:53:28 Quit mink (Remote host closed the connection)
06:54:26 Join mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
07:38:23 Join massiveH [0] (~massiveH@2600:4040:a992:a300:d1fa:418d:babe:9147)
07:52:39 Join _bilgus_ [0] (~bilgus@
07:53:49***Saving seen data "./dancer.seen"
07:54:10 Quit _bilgus (Ping timeout: 260 seconds)
08:23:28_bilgus_gevaerts, thanks I did this the last time too thinking we still had sub headings in hardware back to hardware is fine thank you
08:24:49gevaertsWell, if you want it somewhere else you can move it again :)
08:26:17gevaertsspeachy1: I'm getting an error when viewing the staff list on the forums ( it lists the admins, and then it says "count(): Argument #1 ($value) must be of type Countable|array, null given"
08:27:13gevaertsI was looking there because I've been thinking maybe having one or two more admins would be good. I mean, if people have root access on the server, they can be trusted as forum admins by definition I'd say :)
08:27:46gevaerts(also, never ask if someone wants to be a forum admin. They might say no!)
08:30:05_bilgus_I would be ok with that but I might FSU too
08:43:19 Quit massiveH (Quit: Leaving)
09:16:20gevaertsWell, everyone can do *that* :)
09:23:56 Quit mink (Remote host closed the connection)
09:35:34speachy1ah, heh, smf is always broken somwhere
09:35:59 Quit speachy1 (Quit: WeeChat 3.6)
09:36:49 Join speachy [0] (
09:36:49 Quit speachy (Changing host)
09:36:49 Join speachy [0] (~speachy@rockbox/developer/speachy)
09:36:49Mode"#rockbox +v speachy" by ChanServ (
09:38:23speachyI don't think I've ever actually used that page fwiw. Instead I've just directly manipulated the administrators group list.
09:39:16gevaertsOh indeed, for actual work that's better, but I use that to get a quick reminder about who does what
09:40:05gevaertsIt definitely isn't the most critical thing that could break
09:41:51speachyI wonder what other groups smf is erroring out on.
09:41:53 Quit CH23_M (Ping timeout: 246 seconds)
09:42:04 Join CH23_M [0] (~CH23@revspace/participant/ch23)
09:42:40speachyok, advice taken, and root access folks are now in the admin group.
09:43:55gevaertsWelcome new victims^H^H^H^H^H^H^Hadmins!
09:45:21speachyI think it's because there are no "global moderators"
09:46:14speachyaah, there we go
09:46:36gevaertsAh, you assigned a volunteer :)
09:46:41speachybtw, _bilgus_, you should probably chek your email once in a while.
09:46:53speachyI assigned it to myself, which is kinda redundant but ..whatevs
09:47:23gevaertsIf it fixes things...
09:47:27speachyyou and I are the only ones lited as an admin as their primary group though
09:47:38speachydo you want me to change that to something less portentious?
09:48:04speachy(only really affects which badge that's shown for you)
09:48:42gevaertsMaybe. I'm not really active (sometimes I briefly pretend to be), so it's probably better if people don't go for me first if they need an admin
09:49:10speachyok, you've been publicly demoted to a mere developer.
09:49:17speachyyou'll still show up as an admin on teh staff list.
09:49:45gevaertsPerfect :)
09:51:04 Nick JanC_ is now known as JanC (~janc@user/janc)
09:51:08speachyhmm, what groups _should_ we show on the staff list? admin and global moderators, sure, but developers and "rockbox experts"?
09:53:11speachybtw, same two volunteers are now admins on the bug tracker too.
09:53:53***Saving seen data "./dancer.seen"
09:55:25gevaertsI'm trying to think why I'd want to find a random developer on the staff list, and I think you're right, it doesn't seem *that* useful
09:57:12speachythe badges are nice to have but... a nice index of them? not so much, given that hardly anyone is still active.
09:58:14gevaertsThe badges *do* matter, as they indicate that the post you're reading comes from someone who is assumed to know what they're talking about
09:58:45gevaertsBut purely functionally that's about it. They're also a "thank you
09:58:50gevaerts" of course
10:00:07speachyok, staff page gelded.
10:02:41speachyand added a few developer badges too.
10:03:22speachythe moderator list needs purging; a lot of the emails bounce now.
10:03:32speachybut that's a per-board thing. :(
10:06:57speachy....In theory I could do the server migration this weekend.
10:07:31speachyI have the bulk of the data dumped over now.
10:07:50speachy(what's left is the databases and system config stuff)
10:19:12speachyhuh, forum spam is down considerably from its heydey. guess the kool kids are now spamming mytwitfacetok these day.
11:02:52rb-bluebotBuild Server message: New build round started. Revision b63f4c5884, 303 builds, 7 clients.
11:18:24 Quit jacobk (Ping timeout: 256 seconds)
11:35:30speachyokay, the upload perf is what's killing things on my builders. We need to serialize these uploads.
11:38:39 Join jacobk [0] (
11:43:23 Quit CH23_M (Ping timeout: 264 seconds)
11:43:49 Join CH23_M [0] (~CH23@revspace/participant/ch23)
11:47:29 Join Acou_Bass [0] (
11:51:07 Quit CH23_M (Read error: Connection reset by peer)
11:51:27 Join CH23_M [0] (~CH23@revspace/participant/ch23)
11:51:56rb-bluebotBuild Server message: Build round completed after 2943 seconds.
11:51:59rb-bluebotBuild Server message: Revision b63f4c5884 result: All green
11:52:22 Quit Acou_Bass (Client Quit)
11:52:53 Join Piece_Maker [0] (
11:53:56***Saving seen data "./dancer.seen"
11:56:37 Join chris_s [0] (
11:57:08chris_soh wow, almost an hour...
12:01:18speachyb0hoon's beefy builder is offline and my beefy builders are too fast for their network pipe. (avg upload in sigle digits, wtf..)
12:03:36 Join b0hoon [0] (
12:04:06b0hoonHi. Sorry for confusing you, but i had to shutdown whole cluster of servers, due to electricity job for the weekend. vm2 should get up on monday i hope.
12:05:13sporkhow big an upload is a complete build round ?
12:06:16b0hoonBut good news is i want to resurrect vm1 after new year. Additionally i plan to add vm3 machine with similar capabilities.
12:06:44speachycomplete set is ~640MB, not counting logs.
12:07:22speachyb0hoon: no worries, the more the merrier!
12:07:51speachyI have three beefy systems completely unpowred right now because there's no point with my horrible upload speeds..
12:08:31b0hoonYep:)  I don't want to promise anything, but it's very possible. ;)
12:11:09speachyok, we're now back up to two builders capable of doing the android builds.
12:12:58speachyanother reason for the long build times is that we had some cold ccaches this time. the buildserver tries to hand stuff out to the same builder that did things the last time.
12:16:09speachyhmm, ought to try and make the client a little smarter and not request a new build if there's more than one upload going. right now it's fork-n-forget.
12:25:20 Join lebellium [0] (
12:37:55 Quit Piece_Maker (Ping timeout: 268 seconds)
12:38:43 Quit fourHZ (Ping timeout: 260 seconds)
12:41:46 Quit CH23 (Quit: Leaving)
12:49:00 Join fourHZ [0] (
12:49:31 Join Acou_Bass [0] (
13:00:04 Join CH23 [0] (~CH23@revspace/participant/ch23)
13:03:24 Quit b0hoon (Quit: Connection closed)
13:07:31 Quit chris_s (Ping timeout: 268 seconds)
13:40:05 Quit jacobk (Ping timeout: 260 seconds)
13:40:21 Join jacobk [0] (
13:53:59***Saving seen data "./dancer.seen"
14:33:00 Quit fourHZ (Quit: sleep off the dark)
15:25:14 Quit CH23_M (Read error: Connection reset by peer)
15:25:58 Join CH23_M [0] (~CH23@revspace/participant/ch23)
15:54:01***Saving seen data "./dancer.seen"
17:06:12_bilgus_speachy I have a email? or you mean the one registered?
17:06:40speachyhmm, __builtin has one, I don't remember if I made one for you or not
17:09:06_bilgus_if so I have literally no idea any of the creds for it lol
17:12:46_bilgus_woo thnks for the new access!
17:13:01_bilgus_Ill do my best not to FSU :p
17:24:08speachyit's a webforum, the odds are you'd accidently improve it, if anything.
17:31:36speachyas for flyspray, well, that's not seen much upstream movement either.
17:35:41_bilgus_i put the links in code blocks they aren't clickable but it removes the errors getting posted
17:40:23speachythe errors are in the dokuwiki formatting code.
17:54:02***No seen item changed, no save performed.
17:54:03rb-bluebotBuild Server message: New build round started. Revision fc18235323, 303 builds, 7 clients.
18:27:00 Join Romster [0] (~romster@
18:32:48 Quit lebellium (Quit: Leaving)
18:43:02rb-bluebotBuild Server message: Build round completed after 2939 seconds.
18:43:06rb-bluebotBuild Server message: Revision fc18235323 result: All green
18:43:51 Join massiveH [0] (~massiveH@2600:4040:a992:a300:d457:608e:5b46:c463)
19:33:01 Quit othello7 (Read error: Connection reset by peer)
19:33:21 Join othello7 [0] (
19:54:05***Saving seen data "./dancer.seen"
21:43:26 Quit jacobk (Ping timeout: 256 seconds)
21:54:08***Saving seen data "./dancer.seen"
22:29:42 Join jacobk [0] (~quassel@
22:38:28 Quit jacobk (Ping timeout: 248 seconds)
22:50:35 Join jacobk [0] (~quassel@
23:37:16 Quit m01 (Quit: Konversation terminated.)
23:39:27 Join m01 [0] (
23:54:11***Saving seen data "./dancer.seen"

Previous day | Next day