| + mooglebrundle (~mooglebru@2600:387:15:916::9) | 00:03 | |
| mooglebrundle | Hi all, I can't connect to https://source.mnt.re/ in Firefox, I am getting an error "Secure Connection Failed An error occurred during a connection to source.mnt.re. PR_END_OF_FILE_ERROR" | 00:04 |
|---|---|---|
| - eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf73d8b008705f8ef9d2fb7fc.dip0.t-ipconnect.de) | 00:07 | |
| + eibachd (~eibachd@p200300dcf73d8b003317ba279b1237b2.dip0.t-ipconnect.de) | 00:07 | |
| mooglebrundle | This is also the case on my phone in Safari --- I'm on an ATT wireless connection in the United States. My friend can get to it fine from a standard ISP. I'll try and figure out what my wireless provider is doing to mess up the connection. This is strange because I was reading the sources just yesterday on my phone. | 00:25 |
| minute | mooglebrundle: is it still happening? works fine for me on iphone safari | 00:58 |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@2600:387:15:916::9) | 00:58 | |
| - mtm (QUIT: Ping timeout: 276 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:05 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 01:32 | |
| + murphnj (~murph@ool-457bb02e.dyn.optonline.net) | 01:44 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:49 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 02:09 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 02:09 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 02:12 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 02:13 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 02:15 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 02:18 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 02:19 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 02:30 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 02:35 | |
| + mooglebrundle (~mooglebru@156.146.98.3) | 02:38 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:10 | |
| - dodo (QUIT: Remote host closed the connection) (~dodo@user/dodo) | 03:31 | |
| + dodo (~dodo@user/dodo) | 03:32 | |
| - mooglebrundle (QUIT: Remote host closed the connection) (~mooglebru@156.146.98.3) | 03:38 | |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 03:47 | |
| + arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 03:51 | |
| - arminweigl (QUIT: Ping timeout: 268 seconds) (~arminweig@sourcehut/user/arminweigl) | 03:53 | |
| * arminweigl_ -> arminweigl | 03:53 | |
| - nsc (QUIT: Ping timeout: 268 seconds) (~nicolas@45-121-142-46.pool.kielnet.net) | 04:00 | |
| + nsc (~nicolas@182-121-142-46.pool.kielnet.net) | 04:02 | |
| josch | minute: i don't know if there is something that you can (or should) do, but if one enters "reform handbook pdf" into google, none of the results link to https://mntre.com/media/reform_md/mnt-reform2-operator-handbook.pdf or to https://mntre.com/reform2/handbook/index.html | 06:53 |
| josch | instead, one gets several results for the reform 1 handbook which might be very confusing for some? | 06:54 |
| josch | minute: could i propose another tag for the reform keyboard firmware? It would allow messages like "If you have an old version of the keyboard firmware" or "If you were on an old firmware" to be turned in one that contains the actual firmware version that starts having a feature | 06:59 |
| josch | minute: maybe we should do something about these sparks that fly when i change my keyboard bezel. This time they flew when i removed it on the very left most latch. | 07:16 |
| josch | I wanted to flash my keyboard firmware and hence the reform was turned on. I was not sure what keyboard firmware version i was on and whether it already supported circle+x so i tried pressing circle-y, circle-x and circle-c to see what happens. I tried multiple keys because i have the NEO2 layout printed on my keys so i don't know what is considered a X for normal people. | 07:19 |
| josch | in any case, my keyboard just stopped. It shows the main menu but doesn't react otherwise. I'm on another usb keyboard now. | 07:20 |
| josch | In an attempt to fix this, i removed the bezel to press the reset switch. During that removal (so all latches were in their correct position this time) sparks flew again. This cannot be healthy, no? I don't know what the keyboard could be bridging because i have kapton tape around my battery board edges. | 07:21 |
| josch | Funnily, pressing the reset button does nothing. OLED still shows the main menu. What am i missing? | 07:22 |
| Boostisbetter | I would just disconnect the batteries and reset the old fashion way | 07:25 |
| josch | I'd just consider that a workaround but not a fix. Ultimately, removing the bezel should not short out anything. This needs to be fixed somehow. | 07:47 |
| - eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf73d8b003317ba279b1237b2.dip0.t-ipconnect.de) | 07:52 | |
| + eibachd (~eibachd@2a01:599:315:6e43:d03d:4d51:ad4f:d599) | 07:52 | |
| minute | josch: sorry to hear about the sparks! before the keyboard was auto flashable, i also did not remove the bezel but held down f4 and pressed the button with anything shaped like a toothpick | 08:18 |
| minute | josch: it is not considered "the right way" to remove the bezel while the system is powered, so to speak, so the fix is to prevent people from doing that (i.e. the keyboard entering flashing mode without needing to disassemble anything) | 08:19 |
| josch | ah okay, then it was my fault | 08:20 |
| minute | josch: it's not about blame, more like, it's hard to safely handle a metal part in a system that's powered. i also wonder what it touched, but i don't have a good guess | 08:30 |
| josch | minute: ah no worries, i didn't feel that you put any blame or otherwise negativity on me. | 08:32 |
| minute | alright | 08:33 |
| josch | my misunderstanding occurred because when it said to press the reset switch, i didn't even think about *not* removing the bezel | 08:33 |
| josch | i mean i have to because otherwise how do i know where the reset switch is | 08:33 |
| josch | and from "the keyboard can be flashed while the reform is powered" to "press the reset switch now" i arrived at "it's okay to remove the bezel while it's powered" | 08:34 |
| josch | minute: if it's not considered "the right way" to remove the bezel while the system is powered, would you mind a tiny merge request that points this out and gives the tip with the toothpick and the F4 key at the point of the reform keyboard flasher script that instructs to press the reset button? | 08:35 |
| minute | josch: good idea | 08:39 |
| Boostisbetter | so to update the keyboard and the LPC, I can just remove the keyboard bezel, and then I'd be able to access the USB ports? | 08:55 |
| Boostisbetter | I REALLY need to update the firmwares on those things. | 08:55 |
| josch | Boostisbetter: you can update the keyboard using the reform that the keyboard is plugged into (even without removing the bezel by using the toothpick method) but you cannot flash the lpc firmware without having access to a second machine | 09:03 |
| josch | minute: do you think adding another keyboard firmware tag makes sense at this point? i see a lot of nice new features in the git log. Then i can make that tag part of the MR. | 09:04 |
| Boostisbetter | josch: I didn't realize the keyboard didn't need another computer to update. | 09:05 |
| josch | Boostisbetter: there is a flashing script that guides you through the process | 09:05 |
| Boostisbetter | to update the LPC, is that possible by removing the keyboard bezel? | 09:05 |
| josch | Boostisbetter: to connect to the lpc via usb you have to open up the bottom of the reform | 09:06 |
| Boostisbetter | ahh ok, it is close to the battery connectors. | 09:06 |
| Boostisbetter | Ok, then I think I'm going to tackle that in a bit. | 09:06 |
| Boostisbetter | I am off today, as yesterday we celebrated Thanksgiving. | 09:06 |
| Boostisbetter | so I am some time. | 09:07 |
| Boostisbetter | josch: could you point me to the updating documentation? I should have bookmarked that along time ago | 09:07 |
| josch | Boostisbetter: i think the handbook is not 100% correct anymore for this. It is basically downloading the firmware from gitlab CI (or you build it yourself) and then running the flash.sh script from the reform git repo which then tells you what to do step by step. | 09:08 |
| Boostisbetter | excellent, I'll go to the gitlab and download that. | 09:09 |
| josch | Boostisbetter: maybe you want to wait until the next tag is out, then it will show the version in the OLED. | 09:09 |
| Boostisbetter | well I really should update the LPC though | 09:10 |
| Boostisbetter | it is way out of date | 09:10 |
| josch | minute: currently, the flash.sh script says to press circle+x but on my keyboard firmware version, that completely freezes the firmware and not even pressing the reset switch helps | 09:11 |
| josch | minute: so maybe there should be a warning attached directly to that instruction as well? | 09:11 |
| josch | is that known behaviour? | 09:12 |
| minute | josch: yep @ tag | 09:15 |
| minute | josch: are you sure it only freezed? | 09:16 |
| minute | josch: didn't enter dfu mode? | 09:17 |
| minute | on older-than-my kbd versions, it would look like freezing | 09:17 |
| minute | that's why i added helpful text on the oled now | 09:17 |
| minute | which states it is in flashing mode | 09:17 |
| - Boostisbetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com) | 09:23 | |
| josch | minute: maybe it entered dfu mode but how do i get it out of it? | 09:25 |
| josch | pressing the reset switch didn't change things | 09:25 |
| josch | i plugged in another keyboard and did "systemctl poweroff" | 09:26 |
| josch | but i think since the keyboard is involved in the poweroff, the system still remained "on" | 09:26 |
| josch | so i had to open and unplug the batteries | 09:26 |
| josch | minute: but the helpful text only appears on newer keyboard firmware versions, no? So somebody on an old version who wants to upgrade would still run into this problem. | 09:27 |
| josch | minute: can the programming DIP switch SW84 on the keyboard also be reached via toothpick? | 09:35 |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 09:36 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 09:36 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 09:53 | |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-140-33.tukw.qwest.net) | 10:49 | |
| + colinsane (~colinunin@97-113-140-33.tukw.qwest.net) | 10:50 | |
| minute | josch: unfortunately there's no way to exit dfu mode except for flashing the keyboard | 11:27 |
| minute | josch: weren't you able to flash the keyboard when it was in dfu mode using the external keyboard? | 11:28 |
| + mjw (~mjw@gnu.wildebeest.org) | 12:22 | |
| - eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:315:6e43:d03d:4d51:ad4f:d599) | 12:43 | |
| + eibachd (~eibachd@p200300dcf73d8b004451df41d1d18d79.dip0.t-ipconnect.de) | 12:43 | |
| - erle (QUIT: Ping timeout: 255 seconds) (~erle@2a02:8109:da40:c4:579e:7e85:3049:ad61) | 12:57 | |
| - mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 13:04 | |
| + erle (~erle@ip5f5bf354.dynamic.kabel-deutschland.de) | 13:16 | |
| - mjw (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org) | 13:33 | |
| * mark_ -> mjw | 13:42 | |
| + chomwitt (~chomwitt@2a02:587:7a24:bc00:1ac0:4dff:fedb:a3f1) | 14:34 | |
| tretinha | hi minute, I was wondering if it's in any way possible to alter my pocket reform order to add linear switches instead of the clicky ones I previously chose? if so, how do I go about that? | 14:35 |
| minute | tretinha: sorry, we don't handle the CS orders at all, you would have to ask CS support | 14:55 |
| tretinha | ah, ok! no problem, thanks! | 15:01 |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 15:09 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 15:40 | |
| - eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf73d8b004451df41d1d18d79.dip0.t-ipconnect.de) | 15:48 | |
| + eibachd (~eibachd@p200300dcf73d8b01c77aa34a0eb8cec4.dip0.t-ipconnect.de) | 15:49 | |
| eibachd | josh: I am booting directly from eMMC UBoot to SATA /boot now. Works fine so far, until systemd is looking for dev-mmcblk0p1.device. It goes to emergency mode then. | 15:59 |
| eibachd | Is there any magic script I can return from emergency mode to fix this? | 16:01 |
| eibachd | *run* | 16:01 |
| - mark_ (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 16:10 | |
| eibachd | josh: Nevermind. Just had to remove eMMC from fstab. | 16:18 |
| - eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf73d8b01c77aa34a0eb8cec4.dip0.t-ipconnect.de) | 16:30 | |
| + eibachd (~eibachd@p200300dcf73d8b00c946ce6f1d48a285.dip0.t-ipconnect.de) | 16:30 | |
| + arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 16:42 | |
| - arminweigl (QUIT: Ping timeout: 260 seconds) (~arminweig@sourcehut/user/arminweigl) | 16:42 | |
| * arminweigl_ -> arminweigl | 16:42 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:28 | |
| + jacobk (~quassel@47-186-95-57.dlls.tx.frontiernet.net) | 17:38 | |
| minute | so cool https://mastodon.social/@bnys@lasersword.club/111457555272993366 | 17:52 |
| - jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@47-186-95-57.dlls.tx.frontiernet.net) | 17:53 | |
| sevan | eibachd: this is great, root on ZFS could be a reality on the reform | 18:07 |
| vkoskiv | Oh, resin printed. I was wondering how it's optically so clear | 18:07 |
| vkoskiv | I can't find a panel on panelook that would match the required dimensions, but a 16x10 mod to extend the display down another 18mm @ 1920x1200 would be really neat if possible | 18:13 |
| vkoskiv | I think some of the hinge mounting hardware would get in the way, though | 18:14 |
| josch | minute: i didn't try flashing as the oled menu was shown but the keyboard was otherwise unresponsive so i though it was somehow "stuck" and didn't attempt flashing | 18:15 |
| josch | minute: can the programming DIP switch SW84 on the keyboard also be reached via toothpick? | 18:15 |
| vkoskiv | josch: can, but you don't need to access it with the newest firmware | 18:16 |
| vkoskiv | Though if you're upgrading to that, you do need it :D | 18:16 |
| josch | vkoskiv: but people with the old firmware still do, so i'm writing some text that explains this | 18:16 |
| vkoskiv | Ah let me double-check. I do think I've done it | 18:17 |
| vkoskiv | Well, pushing down the F4 key does show the button, the switch is further back, a bit hard to see but reachable | 18:17 |
| josch | eibachd: just uboot on emmc and /boot and the rest on sata is really cool, thank you for working on that! But it needs some hardware modifications to the board, right? | 18:18 |
| josch | vkoskiv: okay, thank you | 18:18 |
| vkoskiv | Probably still best to take off the frame though | 18:19 |
| vagrantc | huh. never noticed before that the voltage reading on the individual cells reads quite high when charging regardless of how discharged they started at ... had it down to 14% and 3.1~3.2v ... and as soon as I plugged in the charger it read 3.4~3.6v each cell | 18:19 |
| josch | minute: then let me confirm another thing: for the bezel removal to be safe, the reform should not only just be switched off but the battery boards need to be unplugged? Or can the battery boards remain plugged? | 18:19 |
| josch | vagrantc: same here | 18:19 |
| vagrantc | i had always assumed those high readings were just because i rarely got below 90% and that is where lifepo4 tend to be when nearly fully charged | 18:19 |
| vagrantc | i *still* have yet to swap in the fancy upgraded battery boards (and ball-bearing-augmented trackball) | 18:20 |
| eibachd | josch: yes, there is a hardware modification required. I think I will do a full write-up on my blog this weekend. | 18:21 |
| josch | eibachd: looking forward :) | 18:22 |
| minute | josch: for any disassembly the batteries should be disconnected to be safe | 18:24 |
| minute | that's the official statement | 18:24 |
| minute | vagrantc: well, it's tricky because you're measuring the charging voltage at that point | 18:26 |
| sevan | Something colourful https://files.mastodon.social/media_attachments/files/111/466/688/966/224/290/original/f6971e6ffd4a6a8d.png | 18:28 |
| sevan | (for wallpaper) | 18:28 |
| vagrantc | minute: somehow my solar charge controller manages it ... and i think it uses the same charging chip | 18:29 |
| minute | vagrantc: i meant regarding your observation that the cell voltages go high when charging | 18:29 |
| vagrantc | though, that is a 40-amp-hour battery charging much lower than the batteries are rated to handle ... these small 18650 cells are probably much closer to their rated charging capacity | 18:30 |
| vagrantc | this claims to be pulling ~1amp at 28.75v ... and the cells are maybe 1.8amp-hour if i remember correctly ... so that is above 0.5c .... vs. my solar which rarely gets even close to 0.2c | 18:32 |
| josch | minute: awesome, thank you for confirming! :) | 18:35 |
| vagrantc | minute: well, comparing to my solar, the cells do not seem to go so high, except when it nears 100% | 18:35 |
| josch | minute: after creating my MR I noticed that there are a couple more keyboard related MRs open by me, sevan and vkoskiv -- maybe those should be looked at first before creating a new tag? | 19:10 |
| mhoye | How much vertical play is there in the mnt screen case? | 19:14 |
| hramrach | vertical being which direction? | 19:14 |
| mhoye | The bottom maybe two pixel of my screen are obscured by the laptop's frame, which doesn't seem like a big deal but that's enough to hide the cursor | 19:15 |
| mhoye | I can tweak it to a half-character-high cursor but I'd rather solve the real problem. | 19:15 |
| hramrach | Also see https://mastodon.social/@bnys@lasersword.club/111457555272993366 | 19:15 |
| mhoye | Yeah, I guess that's possible... | 19:18 |
| hramrach | it's not detailed enough but should give you some idea what the insides are like | 19:19 |
| mhoye | I have to admit that I like the idea of having a new perspext frame milled out | 19:20 |
| mhoye | More computers should be transparent IMO | 19:20 |
| mhoye | I wonder if there's an on-demand CAD milling place near me. | 19:21 |
| hramrach | it's not milled out, it's made of UV cured resin or somesuch | 19:21 |
| minute | the standard bottom part is milled acrylic tho | 19:22 |
| mhoye | Yeah, I think there are enough cnc places in near me that I can probably just modify the mnt cad files and get a quote | 19:24 |
| mhoye | josch: it looks like the "just comment out the meta+direction" approach to Sway won't do the trick if something running inside sway catches those keystrokes. | 19:25 |
| + mark_ (~mjw@gnu.wildebeest.org) | 20:31 | |
| - eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf73d8b00c946ce6f1d48a285.dip0.t-ipconnect.de) | 21:14 | |
| + eibachd (~eibachd@p200300dcf73d8b00531d08e4b519b9cf.dip0.t-ipconnect.de) | 21:15 | |
| + vagrantc_ (~vagrant@2600:3c01:e000:21:7:77:0:50) | 21:17 | |
| josch | sevan: where do the version numbers in your reform MRs come from? | 22:03 |
| josch | vkoskiv: are you still working on https://source.mnt.re/reform/reform/-/merge_requests/31 ? | 22:06 |
| vkoskiv | Kind of, a different approach is needed, that MR can be closed | 22:08 |
| vkoskiv | My oled project depends on that change, so I | 22:08 |
| vkoskiv | have to figure out something before I release it :D | 22:09 |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 22:09 | |
| * mark_ -> mjw | 22:09 | |
| + mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 22:09 | |
| minute | http://lists.infradead.org/pipermail/linux-arm-kernel/2023-November/878914.html | 22:21 |
| josch | was this issue already observed on the (pocket) reform? | 22:25 |
| minute | i am not sure. i don't think the controller was completely frozen yet | 22:30 |
| hramrach | you need to meet quite specific criteria to trigger the bug so it's possible nobody has noticed | 22:35 |
| josch | minute: https://source.mnt.re/reform/reform/-/merge_requests/59 is ready. The pipeline is red because it also includes a commit that checks that the current git tag corresponds to the preprocessor defines in the code (which it doesn't yet because no tag has been put) | 22:53 |
| josch | minute: is there anything else you'd like to see included in the next release? | 22:54 |
| minute | josch: checking! so !58 can be dropped then, but !57 and !56 included, or? | 22:58 |
| sevan | josch: I set the date on the most recent commit | 22:59 |
| minute | josch: wait, the "release" is only about the keyboard version, yes? | 22:59 |
| josch | minute: yes, but you have all in the same repository, so the git tag applies to the lpc firmware as well | 23:00 |
| josch | i'm not aware of a method that allows tagging only a subdirectory | 23:00 |
| sevan | otherwise, I flashed new firmware on LPC & Keyboard & still ended up with a date of July (which was the date of the previous build I was running) | 23:00 |
| minute | josch: yep. so should i merge !57 and !56 before? | 23:00 |
| - Boostisbetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com) | 23:00 | |
| minute | josch: or would you rather bump the lpc version to the same string also? | 23:01 |
| josch | minute: sevan's changes that set the preprocessor defines to the latest git commit date are incorrect | 23:02 |
| josch | the preprocessor defines need to be set to the latest tag or otherwise the pipeline will fail | 23:02 |
| josch | minute: yes, both strings (for lpc and keyboard) are bumped in my commit here: https://source.mnt.re/reform/reform/-/merge_requests/59/diffs?commit_id=e864b86cd6f058e7c2bd17ae516df8034744b546 | 23:02 |
| josch | sorry, replying is slow because gitlab is slow on the reform ;) | 23:03 |
| josch | constantly waiting for this javascript to finish rendering... | 23:03 |
| josch | i'll leave a comment in !56 on how it should be adjusted | 23:04 |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 23:04 | |
| josch | sevan, minute: i think !57 and !58 are just incorrect | 23:04 |
| sevan | no worries, feel free to close or I can do it now. | 23:05 |
| minute | josch: ok thanks! | 23:05 |
| josch | i guess i should leave a code comment in reform2-keyboard-fw/constants.h and reform2-lpc-fw/src/boards/reform2/board_reform2.c explaining that this is the latest git tag | 23:07 |
| sevan | I closed MR 57 & 58. Hopefully 56 is still valid :) | 23:07 |
| josch | sevan: i left a comment for !56 :) | 23:09 |
| sevan | josch: so really the tag needs to be updated per commit? if there wasn't set of noticable changes in the latest revision, I would've wondered if I'd flashed things correctly since the menu still stated the date of the previous version I was running :) | 23:10 |
| josch | sevan: if you are developing the firmware, you build straight from git and are responsible to set the firmware version string to whatever you desire and makes you happy. The build will not fail. It is the gitlab CI that checks this and fails if the version string is incorrect. | 23:11 |
| josch | sevan: this is because as a normal user, you don't want to build it yourself but grab the artifacts from the gitlab CI release page | 23:11 |
| sevan | aha | 23:11 |
| josch | which in turn get it from the pipeline results | 23:11 |
| sevan | I was not aware that such helpful facilities were available | 23:12 |
| sevan | I just cloned the repo & tried to build | 23:12 |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-140-33.tukw.qwest.net) | 23:12 | |
| + colinsane (~colinunin@97-113-140-33.tukw.qwest.net) | 23:15 | |
| josch | CI builds everything: https://source.mnt.re/reform/reform/-/jobs/2549/artifacts/browse | 23:15 |
| sevan | josch: re 56, makes sense. I can update the change later. | 23:15 |
| josch | cool thank you! :) | 23:15 |
| minute | josch: so i can merge, yes? | 23:16 |
| sevan | josch: thanks for the artifacts link. | 23:16 |
| josch | minute: yes, and then run "git tag 2023-11-24" | 23:17 |
| minute | !59 that is | 23:17 |
| minute | ok | 23:17 |
| minute | well, i can only use the web interface right now | 23:17 |
| josch | doesn't matter if the tagging is done later i think :) | 23:19 |
| minute | josch: created a tag in the web ui after merge, i hope this did the right thing? | 23:19 |
| josch | oh lets see | 23:19 |
| josch | minute: looks good, thank you! | 23:19 |
| minute | ok cool. thank you too! | 23:19 |
| josch | minute: what's the next thing coming up as far as reform-debian-packages and reform-system-image goes? creating pocket reform system images? | 23:22 |
| - vagrantc_ (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 23:22 | |
| minute | josch: yep, pocket will be a biggie | 23:22 |
| josch | it will? | 23:23 |
| josch | not just different kernel patches and done? | 23:23 |
| minute | josch: more tweaks to desktop things probably | 23:23 |
| josch | oh okay | 23:23 |
| minute | incl some onboarding similar to what you suggested, but perhaps graphical or TUI | 23:24 |
| josch | the first-boot stuff? | 23:24 |
| josch | the things i made run inside the initramfs or otherwise they cannot resize partitions etc -- so no graphical ui possible, sadly | 23:25 |
| josch | well... possible but hard | 23:25 |
| minute | :3 | 23:35 |
| josch | next week my minipcie->pcix16 adapter is arriving -- now i just need a second motherboard :) | 23:46 |
| minute | ha. yep, it's pretty high on my todo list! | 23:52 |
| josch | \o/ | 23:53 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
