| - plomlompom (QUIT: Remote host closed the connection) (~plom@139.59.138.73) | 00:01 | |
| + plomlompom (~plom@139.59.138.73) | 00:02 | |
| minute | i have a very unorthodox workaround for the waybar icon issue... but it could be much more unorthodox | 00:05 |
|---|---|---|
| minute | josch: i just pushed a new tool | 00:29 |
| minute | josch: so thanks for updating reform-tools/changelog, but there's now reform-waybar-icon-wedge as well | 00:30 |
| minute | josch: which i'm testing on target now | 00:30 |
| josch | then we put that into the next release | 00:31 |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 00:50 | |
| minute | josch: how do you like my latest horror https://source.mnt.re/reform/reform-tools/-/blob/main/bin/reform-waybar-icon-wedge?ref_type=heads | 00:51 |
| - TechnoWizard (QUIT: Remote host closed the connection) (~TechnoWiz@user/TechnoWizard) | 00:55 | |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 00:56 | |
| - TechnoWizard (QUIT: Remote host closed the connection) (~TechnoWiz@user/TechnoWizard) | 00:56 | |
| elb | I just updated my pocket reform, and it acts like I'm sitting on the spacebar when it reboots | 00:59 |
| elb | (and I can't decrypt the disk, possibly for this reason) | 00:59 |
| elb | does that sound familiar to anyone | 00:59 |
| minute | elb: hmmm, try oled menu -> reset keyboard | 01:00 |
| elb | did nothing, neither did power cycling | 01:00 |
| elb | I'm opening it up to unplug the keyboard USB right now | 01:00 |
| elb | but like ... they keyboard worked fine before rebooting | 01:00 |
| minute | elb: huh. by power cycling do you mean standby switch toggle? | 01:01 |
| elb | and the oled menu works normally and fine | 01:01 |
| elb | oh no I mean hyper+enter 0 then 1 | 01:01 |
| minute | elb: try standby switch toggle, then you don't need to unplug | 01:01 |
| minute | elb: keyboard will be powered off by doing that | 01:01 |
| elb | oh I meant to make sure the keyboard is even sending anything at all | 01:01 |
| elb | but yeah let me try that, good call | 01:01 |
| minute | ah gotcha | 01:02 |
| minute | like, switch or gpio failure | 01:02 |
| elb | standby switch did nothing | 01:02 |
| minute | hmm, mechanical problem with one of the space keys? | 01:03 |
| elb | ok, the keyboard is unplugged | 01:04 |
| elb | and it's still doing it | 01:04 |
| elb | so it's teh kernel or something | 01:04 |
| minute | anything else connected? HDMI? | 01:04 |
| elb | nope | 01:04 |
| elb | not even usb pd | 01:05 |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 01:07 | |
| elb | going to put a system image on microsd | 01:08 |
| minute | elb: i recently added gpio-keys for the wakeup gpio, with linux,code = <57> | 01:08 |
| minute | elb: i wonder if it's that | 01:08 |
| elb | I think last I updated was about a week ago | 01:09 |
| elb | this addition was in the linux kernel? | 01:09 |
| minute | elb: it's in the devicetree, so in the kernel package | 01:09 |
| minute | elb: merged oct 24 | 01:10 |
| elb | hmmm not surew hat my previous kernel was | 01:11 |
| elb | I'll find out as soon as I get this image written | 01:11 |
| minute | i'm gonna comment this out of the device tree in any case, because if the gpio is not initialized by system controller, i'm not sure about the initial state | 01:12 |
| minute | pushed (but will take a while until that's rolled out) | 01:14 |
| elb | it will apparently take a while until this image writes, too ;-) | 01:17 |
| minute | btw the gnome session is kind of broken (i think due to gnome-settings-daemon or similar) after logging out of a sway session | 01:18 |
| elb | I normally log in at boot and then shut down when I'm done, so that feels survivable for me, personally | 01:19 |
| minute | yeah... i don't have the energy to look into fixing this now... but i think the way that the sway session is started needs to be improved at some point | 01:19 |
| elb | I find that a lot of things about sway need to be improved; -) | 01:19 |
| elb | but I'm not sure that's a reform problem | 01:19 |
| minute | yeah... | 01:20 |
| elb | hmmm this system image is 11 GB uncompressed but compresses to 2 | 01:21 |
| elb | as someone who lives always on the edge of running out of storage for reasons of personal shortcomings, that's a lot of zeroes (or whatever) to store ;-) | 01:21 |
| elb | I'm writing by piping gzip -dc to dd | 01:22 |
| minute | elb: the best way to write the image is: | 01:22 |
| minute | elb: bmaptool copy https://image/url /dev/sdX | 01:22 |
| schalken1 | i'm having the same problem as elb, oof | 01:22 |
| elb | bmaptool is new to me | 01:22 |
| minute | elb: it will then do sparse copy and decompression with http range requests | 01:22 |
| minute | schalken1: same solution applies! | 01:23 |
| elb | interesting | 01:23 |
| elb | well for now I'm using a pipe | 01:23 |
| elb | I'll look at this for next time | 01:23 |
| minute | i.e. you don't need any temp storage, it will be streamed from the web to your disk :D | 01:24 |
| elb | all of this because I was going to install typst and try to build slides with pdf accessibility built in | 01:24 |
| elb | but typst is %!@#!@ rust | 01:24 |
| minute | oh and what's the problem with rust? | 01:24 |
| elb | it's a toolchain nightmare | 01:25 |
| elb | and they're deeply unserious about security and reliability | 01:25 |
| minute | elb: hmm. i would recommend "apt install rustup" | 01:25 |
| elb | yes, that's what I do | 01:25 |
| minute | ah | 01:25 |
| elb | then I rustup update rustup and all its crap | 01:25 |
| minute | oh | 01:25 |
| elb | but the _recommended_ method is friggin' curl | sh | 01:26 |
| minute | true | 01:26 |
| elb | which makes me want to either cry or scream | 01:26 |
| elb | depending on mood | 01:26 |
| minute | rustup update rustup not working on debian sounds like a debian bug tho | 01:26 |
| elb | oh it works | 01:26 |
| minute | because rustup do recommend using apt on debian... | 01:27 |
| elb | but then you transition from a system rust to an unmanaged rust in ~ | 01:27 |
| minute | yeah that's what you want tbh... | 01:27 |
| elb | I mean this is just how software is, now | 01:27 |
| minute | i guess the debian devs can't chase that much of a moving target | 01:27 |
| elb | and rust has to be that way because every package I ever look at demands that i install a newer verison of the compiler | 01:28 |
| minute | for python3 i recently started using "uv" to | 01:28 |
| minute | too | 01:28 |
| minute | yeah, the debian rustc is usually old | 01:28 |
| elb | uv is also new to me | 01:28 |
| elb | I try to just keep my python3 needs moderate | 01:29 |
| sigrid | with uv I can actually run python scripts for once | 01:29 |
| minute | i'm not very good at python but uv was surprisingly painless | 01:29 |
| elb | 3.8 or so added the type checking stuff that's important to me, personally, so past that I have little opinion | 01:29 |
| - TechnoWizard (QUIT: Remote host closed the connection) (~TechnoWiz@user/TechnoWizard) | 01:35 | |
| elb | ok, confirmed that the system image works fine | 01:46 |
| minute | uh oh | 01:47 |
| minute | elb: btw... which one did you image? | 01:47 |
| elb | I used the "known working" one from 2025-07-24 | 01:47 |
| elb | I'm guessing the non-booting kernel is 6.17.5-mnt-reform-arm64 | 01:51 |
| elb | the previous working terminal was 6.16.9 | 01:51 |
| elb | no, maybe .12 | 01:51 |
| elb | yup, running 6.16.12 fine business again | 01:54 |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 01:59 | |
| - TechnoWizard (QUIT: Remote host closed the connection) (~TechnoWiz@user/TechnoWizard) | 02:02 | |
| - enwu (QUIT: Ping timeout: 256 seconds) (~enwu@user/enwu) | 02:03 | |
| + enwu (~enwu@user/enwu) | 02:07 | |
| - chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1) | 02:07 | |
| - enwu (QUIT: Ping timeout: 244 seconds) (~enwu@user/enwu) | 02:12 | |
| + enwu (~enwu@user/enwu) | 02:14 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 02:16 | |
| minute | elb: hmm i merged 6.17 patchset earlier because i interpreted josch's comments as "tested" on his devices. so it's actually broken? | 02:16 |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 02:16 | |
| minute | i also tested several new system image builds a few hours ago and they worked (on reform rk3588 though, not pocket) | 02:17 |
| elb | it's certainly broken for me, at least along with whatever else happens in early boot | 02:18 |
| elb | it really acts like it's geetting continuous keyboard input, the cursor just keeps moving to the right | 02:18 |
| elb | (but it did it even with no keyboard attached) | 02:20 |
| minute | ok, i'm installing 6.17 update on my reform now | 02:25 |
| minute | > Error! Bad return status for module build on kernel: 6.17.6-mnt-reform-arm64 (aarch64) | 02:27 |
| minute | Failed command: | 02:27 |
| minute | make -j8 KERNELRELEASE=6.17.6-mnt-reform-arm64 -C /lib/modules/6.17.6-mnt-reform-arm64/build M=/var/lib/dkms/reform2_lpc/1.76/build | 02:27 |
| minute | trying > sudo apt install linux-image-mnt-reform-arm64 reform2-lpc-dkms | 02:29 |
| minute | ok, that fixed it... reboot! | 02:31 |
| minute | ok, works for me on classic reform rk3588 | 02:33 |
| - TechnoWizard (QUIT: Ping timeout: 264 seconds) (~TechnoWiz@user/TechnoWizard) | 02:36 | |
| - dok (QUIT: Ping timeout: 256 seconds) (~dok@2a01:e0a:12:d860:3696:e5bc:8411:9bc5) | 02:36 | |
| minute | elb: works for me on pocket rk3588 | 02:41 |
| minute | > Linux pocki3000 6.17.6-mnt-reform-arm64 #1 SMP PREEMPT Debian 6.17.6-1+reform20251104T001425Z (2025-11-0 aarch64 GNU/Linux | 02:42 |
| + dok (~dok@2a01:e0a:12:d860:3696:e5bc:8411:9bc5) | 02:44 | |
| elb | ok mine is 20251101, so this is your updated kernel with the new dtb? | 02:46 |
| elb | updating now | 02:46 |
| minute | elb: yes, very likely, the time checks out | 02:49 |
| minute | elb: i really need to sleep, it's almost 3am. fingers crossed it works for you | 02:49 |
| - mjw (QUIT: Ping timeout: 250 seconds) (~mjw@gnu.wildebeest.org) | 02:50 | |
| elb | good night :-) | 02:53 |
| elb | I'll let you know when I get it back up | 02:54 |
| elb | it's updating, my wi-fi from this location is very slow | 02:54 |
| - paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@107.159.15.124) | 02:54 | |
| elb | minute: confirmed 6.17.6-1+reform20251104T001425Z works properly here | 03:01 |
| grimmware | I’ve not looked at uv yet. Work is predominantly python-based so I know my way around a virtualenv and have been using pipx for installing command line utilities | 03:03 |
| grimmware | I’m not terribly keen on python to be honest. The idioms are syntax maximalist, especially list comprehensions. | 03:04 |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:06 | |
| elb | I put python in the "ok" department | 03:07 |
| elb | I strongly preferred ruby, but the language kind of lost to python and RoR | 03:07 |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:08 | |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:08 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:08 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.15.124) | 03:28 | |
| + paperManu (~paperManu@107.159.15.124) | 03:33 | |
| + plomlompom0 (~plom@139.59.138.73) | 04:01 | |
| + iank_ (~iank@fsf/staff/iank) | 04:02 | |
| + wakest_ (m-a7d6fe@67.219.99.225) | 04:04 | |
| - plomlompom (QUIT: *.net *.split) (~plom@139.59.138.73) | 04:07 | |
| - colinsane (QUIT: *.net *.split) (~colinunin@97-113-142-187.tukw.qwest.net) | 04:07 | |
| - rwa_ (QUIT: *.net *.split) (0a82deb4eb@2a03:6000:1812:100::41b) | 04:07 | |
| - iank (QUIT: *.net *.split) (~iank@fsf/staff/iank) | 04:07 | |
| - jn (QUIT: *.net *.split) (~quassel@user/jn/x-3390946) | 04:07 | |
| - wakest (QUIT: *.net *.split) (m-a7d6fe@67.219.99.225) | 04:07 | |
| - qbit (QUIT: *.net *.split) (~qbit@user/qbit) | 04:07 | |
| + rwa_ (0a82deb4eb@2a03:6000:1812:100::41b) | 04:07 | |
| + jn (~quassel@user/jn/x-3390946) | 04:07 | |
| + qbit (~qbit@user/qbit) | 04:07 | |
| * wakest_ -> wakest | 04:09 | |
| + colinsane (~colinunin@97-113-142-187.tukw.qwest.net) | 04:18 | |
| - paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@107.159.15.124) | 04:27 | |
| + chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1) | 07:10 | |
| josch | minute: my comment was indeed only the "booted" part, not that I tested much more than that. That's why I had the Linux 6.17 MR still marked as "Draft". | 07:26 |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.212) | 07:34 | |
| + TechnoWizard (~TechnoWiz@user/TechnoWizard) | 07:40 | |
| - TechnoWizard (QUIT: Remote host closed the connection) (~TechnoWiz@user/TechnoWizard) | 08:04 | |
| + gidzit (~gidzit@gidzit.org) | 08:05 | |
| - gidzit (QUIT: Ping timeout: 256 seconds) (~gidzit@gidzit.org) | 08:30 | |
| josch | minute: about reform-waybar-icon-wedge -- do you know if there is already an open waybar issue about this problem? Usually when I write ugly "hacks" I make it under the condition that the software with the problem has a bug about it and then I can reference that bug in my "hack" to proof to others: "see, this hack is necessary because upstream doesn't want it any other way" or "see, this hack is | 08:38 |
| josch | necessary because fixing the problem properly is much harder or too difficult" | 08:38 |
| josch | it at least gives the chance of the hack not staying forever or for those who hate the hack sufficiently to put in the work and fix it upstream | 08:38 |
| + gidzit (~gidzit@gidzit.org) | 09:14 | |
| minute | josch: there's at least a gtk bug about this (wontfix) iirc. someone requested and env var for icon theme | 10:29 |
| minute | josch: and yeah there's something among the 1000 issues of waybar too, would need to dig it up | 10:30 |
| josch | minute: no worries, i can search for it too. I was just asking in case you had looked it yesterday or something. | 10:32 |
| josch | the file /usr/share/xdg-terminal-exec/sway-xdg-terminals.list also sounds like something that should be going into a different package than reform-tools -- there might be a file conflict waiting to happen | 10:38 |
| minute | josch: probably in sway, where i see a very low probability of that happening | 10:40 |
| josch | yes. if somebody complains we can move it | 10:51 |
| grimmware | elb: yeah I prefer ruby, I find you can write much more terse but still readable code | 10:53 |
| grimmware | but I do think it's mostly that all the method chaining and shit like that fits the way I think | 10:54 |
| grimmware | I'd prefer it if they dropped some of the syntactic sugar stuff and just stuck with parentheses | 10:55 |
| + aloo_shu (~aloo_shu@85.51.18.212) | 11:21 | |
| - RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk) | 11:27 | |
| + RandyK (~RandyK@user/randyk) | 11:27 | |
| MartiniMoe | minute: I really don't mean to push and its totally fine if you answer "can't say", but I wanted to ask if you can somehow guess if my pocket reform might arrive before 39c3. Because otherwise I'll look for a different laptop to bring to the event, which would also be totally fine ^^ again, I really don't wanna push and its totally fine if it won't be shipped until then :D | 11:36 |
| - chomwitt (QUIT: Ping timeout: 250 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1) | 12:08 | |
| + paperManu (~paperManu@107.159.15.124) | 12:18 | |
| + mjw (~mjw@gnu.wildebeest.org) | 12:20 | |
| + tisiphone (~quassel@user/tisiphone) | 12:35 | |
| + gustav25 (~gustav@c-78-82-52-240.bbcust.telenor.se) | 13:02 | |
| minute | MartiniMoe: order date? | 13:09 |
| MartiniMoe | minute: 20th of september | 13:17 |
| - svp (QUIT: Quit: Gateway shutdown) (~svp@2002:4f07:f0bd:0:69b1:b463:d245:e861) | 13:28 | |
| + chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1) | 13:46 | |
| - cwebber (QUIT: Quit: crossing the threshold of Lugonu's domain) (~Christine@user/cwebber) | 14:16 | |
| + Serve0925 (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 14:16 | |
| - Serve0925 (QUIT: Remote host closed the connection) (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 14:35 | |
| + Serve0925 (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 14:36 | |
| minute | josch: ok i'm back to trying to release the system image | 14:39 |
| minute | (for flashing here) | 14:39 |
| minute | last night some gitlab glitch happened, so rerunning | 14:40 |
| + josch-pocket (~josch-poc@194.213.108.8) | 14:48 | |
| josch-pocket | minute: would you like another reform-tools release with your recent changes for that? | 14:49 |
| josch-pocket | minute: are you flashing rk3588 units? Maybe this is a good opportunity to merge my outstanding u-boot MR and tag a new release of reform-rk3588-uboot? Then that release tag can be part of the reform-tools release as well | 14:50 |
| minute | josch-pocket: ok both yes | 14:54 |
| + paperManu_ (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:55 | |
| + cwebber (~Christine@user/cwebber) | 14:57 | |
| minute | josch-pocket: meh, uboot pipeline failed after merge | 15:00 |
| minute | bizarro > WARNING: Failed to pull image with policy "always": open /ramdisk/docker/tmp/GetImageBlob3135916763: no such file or directory (manager.go:203:1s) | 15:00 |
| minute | josch-pocket: i'll assign the arm runner | 15:00 |
| josch-pocket | in the past, the x86 runner was necessary because there was a x86 binary blob run during u-boot compilation --it turned out that that proprietary blob did nothing so it's removed now | 15:05 |
| josch-pocket | and that's why it should work fine on the arm runner now even if it did not before | 15:05 |
| minute | ah nice. hope it'll work | 15:06 |
| minute | otherwise: box64 :D | 15:06 |
| josch-pocket | i didn't get the blob to work with box64 only qemu workey | 15:07 |
| josch-pocket | but it doesn't matter the blob is gone | 15:07 |
| minute | yes, uboot build worked | 15:09 |
| josch-pocket | with the new build.sh it should be very simple to do a release | 15:09 |
| josch-pocket | you no longer have to edit a file with the name of the git tag | 15:09 |
| josch-pocket | it should be sufficient to just tag it | 15:09 |
| minute | ok, just make a tag? | 15:09 |
| josch-pocket | yes, that should work, lets see :) | 15:10 |
| josch-pocket | and then i copy the checksum of the binaries produced by the gitlab job into reform-tools machine.conf | 15:10 |
| minute | tagged | 15:10 |
| josch-pocket | good the new pipeline is running | 15:10 |
| josch-pocket | i'll flash that to my pocket and see if it looks right | 15:11 |
| - josch-pocket (QUIT: Quit: josch-pocket) (~josch-poc@194.213.108.8) | 15:23 | |
| minute | :0 | 15:23 |
| + wielaard (~mjw@2001:1c06:2486:a800:158:adb1:a1e7:3c3f) | 15:25 | |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 15:27 | |
| + svp (~svp@host-79-7-240-189.business.telecomitalia.it) | 15:33 | |
| josch | it doesn't boot :( | 15:39 |
| * wielaard -> mjw | 15:46 | |
| josch | oh no it *does* work | 15:55 |
| josch | just wonky emmc init i guess | 15:56 |
| josch | (i'm at work right now so i cannot have a look via uart) | 15:56 |
| josch | minute: coudl you change the gitlab runner for reform-tools to the arm64 machine as well? https://source.mnt.re/reform/reform-tools/-/jobs/15218 | 16:13 |
| josch | i'd like to see a green pipeline result before i tag this | 16:13 |
| josch | but unless you have anything else to add, the release should be ready | 16:13 |
| josch | oh, there is one problem with reform-waybar-icon-wedge which was not spotted because the CI didn't run | 16:18 |
| minute | josch: ah sorry, one moment | 16:18 |
| minute | josch: what's the wedge problem? | 16:19 |
| minute | josch: arm64 ci pointed to reform-tools | 16:20 |
| minute | (now i mean) | 16:20 |
| josch | minute: man pages are automatically generated by calling the tool. Calling it with --help just starts another waybar instead of showing --help output. I have it fixed locally. | 16:21 |
| josch | Another problem is that the makefile is not creating usr/share/xdg-terminal-exec/ in $(DESTDIR) -- also fixed | 16:22 |
| josch | it helps to have CI :) | 16:22 |
| minute | josch: ah thank you! i didn't really check those last night, just did a best effort :D | 16:25 |
| minute | josch: where did you put the fix though? | 16:25 |
| josch | no worries, easy to fix up | 16:25 |
| josch | i'm pushing in a bit | 16:25 |
| josch | i'm cleaning up the git history | 16:25 |
| minute | ah alright | 16:25 |
| josch | pipeline is green, tag 1.81 is created | 16:30 |
| josch | now uploading to Debian | 16:30 |
| - aelius (QUIT: Remote host closed the connection) (~aelius@user/aelius) | 16:38 | |
| - gidzit (QUIT: Ping timeout: 246 seconds) (~gidzit@gidzit.org) | 16:38 | |
| + aelius (~aelius@user/aelius) | 16:40 | |
| josch | and uploaded | 16:42 |
| josch | lets hope that nothing else was missed | 16:42 |
| josch | but if it was, we'll do another release :) | 16:42 |
| minute | ah, uploading to debian... how can i build a system image with this version, or one that can be upgraded to debian later? | 16:53 |
| minute | i mean, how can i build an image now? | 16:53 |
| minute | josch: is an image with reform-tools branch set, and using make install, installing a .deb that can be updated to a release version? | 16:53 |
| minute | josch: ah, this looks like it's using reform-tools 1.8 from our git or.... ? https://source.mnt.re/reform/reform-system-image/-/merge_requests/145 | 16:55 |
| minute | yeah ok https://source.mnt.re/josch/reform-system-image/-/jobs/15210#L3871 | 16:55 |
| - RandyK (QUIT: Ping timeout: 272 seconds) (~RandyK@user/randyk) | 16:55 | |
| + RandyK_ (~RandyK@user/randyk) | 16:55 | |
| minute | so i'll update our factory installer to job 15210 and test that now | 16:56 |
| * RandyK_ -> RandyK | 16:57 | |
| - Serve0925 (QUIT: Remote host closed the connection) (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 16:57 | |
| + Serve0925 (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 16:57 | |
| minute | josch: ah woops i ended up in your repo | 16:59 |
| minute | 15216 | 16:59 |
| josch | minute: that is reform-tools 1.80 but the test version is 1.81 | 17:00 |
| minute | uff | 17:00 |
| minute | ok what do i have to do... my brain is cooked already | 17:00 |
| minute | i need an image right now... | 17:01 |
| josch | minute: if you want to build a system image with reform-tools 1.81 package *now* then you need to adjust reform-debian-packages to build a *.deb from sources instead of pulling it from Debian | 17:01 |
| minute | ok i'm not capable of doing that atm | 17:01 |
| josch | sorry, i have had classes the whole afternoon (until 17:30) so my availability is also spotty | 17:01 |
| minute | ok i'll start with the old version and see | 17:02 |
| josch | i could've prepared this this morning if you had told me a bit earlier | 17:02 |
| minute | yeah, somehow i didn't remember that this has to go through debian | 17:02 |
| josch | the reform-debian-package machinery could be extended to build a .deb from scratch | 17:02 |
| josch | it doesn't have to | 17:02 |
| minute | josch: so the "make install" thing does not cleanly install a package, but just installs the reform-tools content on the target fs? | 17:02 |
| minute | josch: i mean if i specify a reform-tools branch in the CI variables | 17:02 |
| josch | but if it's not going through debian first, then somebody else has to do the work of maintaining the version which is temporary on the MNT repo | 17:03 |
| josch | and the upgrade path between the two in case there are descrepancies | 17:03 |
| josch | yes, the "make install" only copies files | 17:03 |
| minute | ok, thanks for clarifications | 17:03 |
| josch | using the "make install" method might be an acceptable hack if it's okay that dpkg-verify will show you problems until the user updated to 1.81 properly | 17:03 |
| minute | ok we'll abort here then and i'll just do some tests with the version with 1.80 | 17:03 |
| minute | and we'll try again tomorrow | 17:04 |
| josch | i have a system image here with 1.81 properly installed but i cannot upload it because uni wifi, sorry :( | 17:04 |
| minute | ok no problem... it would be great to make it possible in the future that i could act independently to make in-between versions | 17:04 |
| josch | (and you probably should not distribute what i build here to customers :D) | 17:04 |
| josch | minute: we'd have to talk about how you'd like the tooling to work for that | 17:05 |
| josch | because it would be an extra layer of complexity | 17:05 |
| josch | we should've talked about that last Thursday :) | 17:05 |
| minute | josch: yeah... i guess i wanted to fix too many bugs last minute | 17:05 |
| minute | but it feels like some things can't be fixed later because there's no mechanism to import fixes from /etc/skel | 17:06 |
| josch | well, there is always a way -- it depends on how hacky is still acceptable | 17:06 |
| minute | josch: hmm but reform-debian-packages already builds a reform-tools .deb... can't i just rerun reform-debian-packages pipeline and yield 1.81? | 17:14 |
| minute | hmmm no it builds 1.80... ah, so that's what you meant by changing reform-debian-packages | 17:21 |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@2001:1c06:2486:a800:158:adb1:a1e7:3c3f) | 17:31 | |
| josch | so, the core of reform-debian-packages is build_patched.sh, the rest is just "bolted on" | 17:36 |
| josch | what build_patched.sh does is to download source packages from the debian archive, patches them and then builds them | 17:36 |
| josch | reform-tools is built like that right now | 17:36 |
| josch | now we could special-case reform-tools to be built differently, that instead of pulling it from Debian, it pulls the packaging source from elsewhere and builds that | 17:37 |
| josch | but then somebody needs to maintain that packaging source | 17:37 |
| josch | i mean you could pull the packaging source from salsa.debian.org but then you would again be dependant on me which you want to avoid | 17:37 |
| josch | so instead you have to start maintaining your fork of my packaging work and change it in lock-step with the changes I perform | 17:38 |
| josch | this is extra complexity and extra work for you and it's up to you whether you would want to do this or not | 17:38 |
| + mjw (~mjw@gnu.wildebeest.org) | 17:48 | |
| - chrcav (QUIT: Ping timeout: 264 seconds) (~chrcav@user/chrcav) | 17:57 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 18:07 | |
| + mjw (~mjw@2001:1c06:2486:a800:158:adb1:a1e7:3c3f) | 18:18 | |
| - paperManu_ (QUIT: Ping timeout: 260 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 18:18 | |
| josch | minute: this upload is actually a good example. Because things needed to be done quickly, I uploaded without testing. This means that I have a bug in what will now be in Debian. Somebody has to put in the work and fix the packaging changes which accumlate over time. (in this case, this was the fix: https://paste.debian.net/hidden/9e80487e/ ) | 18:29 |
| josch | minute: sorry for the wall of text. I mean no disrespect. I know you have an extremely busy schedule and while I'd like to help, I 100% agree that it would be great if I was not a single-point-of-failure. I remember the last time you wanted a new reform-tools Debian package *now* I think it was a few months ago. I have performed over 80 reform-tools releases so far and I think the vast majority of them | 18:31 |
| josch | was without much urgency. I wonder if the extra complexity and the extra things you have to learn to then only really need them every 3 months or so is worth it? | 18:31 |
| josch | this is your project and you get to decide how it's run. I would like to supply you with a better way forward than the status quo but cannot come up with one which would be an overall win but of course my perspective might be different from yours. Maybe somebody else has an idea. :) | 18:32 |
| minute | josch: ideally what i want is that either reform-tools builds a .deb, and reform-system-package pulls in that deb | 18:33 |
| minute | josch: or reform-debian-packages builds the reform-tools .deb | 18:33 |
| minute | josch: but not from debian sources but from mnt reform-tools git | 18:33 |
| josch | right, but that either has to be coordinate with what is in Debian or you do a complete fork independent from Debian because otherwise the package versions will be incompatible (think of the upgrade scenario) | 18:34 |
| minute | josch: why would they be incompatible? i would build 1.81 now, the same that you upload to debian... | 18:38 |
| josch | no, what i'm uploading to debian right now is 1.81-2 | 18:38 |
| josch | it's slightly different from 1.81-1 | 18:38 |
| minute | josch: it sounds like we just have to make sure that the version in mnt repo is not numerically ahead of a newer version you upload to debian | 18:39 |
| minute | josch: so that one can always upgrade to the debian version without losing functionality | 18:39 |
| josch | no, it's not about which version is larger because the apt pinning rules already prefer the MNT repos indpendent on which version is larger | 18:40 |
| minute | josch: ok but 1.80 was built by reform-debian-packages and will go to the mnt repo, right? so that means users won't be able to install 1.81 by default until reform-debian-packages reruns with debian as reform-tools deb source? | 18:40 |
| josch | that is correct | 18:41 |
| josch | but that's because how reform-debian-packages is set up. This can be changed. | 18:41 |
| josch | another example to illustrate what i mean when weighing complexities against each other: | 18:43 |
| josch | you asked for an easier way to quickly put changes into reform-tools without editing a patch file, so I added the ./reform-tools directory to reform-debian-packages to make this easier | 18:44 |
| josch | until now, I have made 24 commits in the ./reform-tools directory (just to keep the reform-tools version in sync with Debian) and there are 2 commits from you | 18:44 |
| josch | so there is extra complexity and extra work for me for just two commits from you | 18:45 |
| josch | again, please do not see this as any disrespect. I have no problem with helping | 18:45 |
| josch | but to me, this sounds like a similar situation where more complexity is added, more work for me, which will only be used very rarely by you | 18:45 |
| josch | as in: it will be used in situations like today but these are "rare" no? | 18:46 |
| josch | i hope you underrstand what i'm trying to say and that i do not come across at wanting to remain the single point of failure, i don't -- i just don't have a good idea myself | 18:47 |
| josch | this would be easier to talk about than to write about :) | 18:48 |
| - chomwitt (QUIT: Ping timeout: 250 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1) | 18:48 | |
| josch | sorry, i realize this is frustrating for you right now because you had to scrap plans you had. Sorry :/ | 18:53 |
| minute | josch: ah, so i could just add the 1.81 patch to reform-debian-packages? | 18:55 |
| minute | josch: i.e. the diff from 1.80 to 1.81? | 18:55 |
| josch | often but not always | 18:56 |
| josch | unfortunately the Debian patch system has some limitations | 18:56 |
| minute | josch: yeah but i mean today | 18:56 |
| josch | yes, try it and if it breaks i can explain you why it didn't work today :) | 18:56 |
| minute | josch: i don't have the mental bandwidth to work on future proof solution today because i'm a bit sleep deprived, it would just be great to have a fix for this release which doesn't break the update to the next version(s) | 18:57 |
| minute | i just had to make a 6 page document pointing out cutting and sewing issues in the reform next sleeve | 18:58 |
| josch | Please try it out. I hope it works but no promises. I'm on my way home right now and will be back later (but by then, reform-tools 1.81 will already be in Debian unstable) | 18:59 |
| josch | (currently sitting at the station for wifi) | 18:59 |
| josch | fingers crossed and ttyl | 19:00 |
| minute | ah ok. then i'll just wait | 19:01 |
| minute | i stared at reform-debian-packages/reform-tools and don't know how and what patches to put in there anyways | 19:01 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:10 | |
| - pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0) | 19:16 | |
| josch | minute: maybe like this: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/147 | 19:24 |
| + Murphy (~Murphy@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 19:26 | |
| Murphy | One of my keys are stuck down after upgrading packages. I think it's spacebar. I tried resetting the keyboard and using the power switch. Any suggestions? | 19:28 |
| - Serve0925 (QUIT: Remote host closed the connection) (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 19:30 | |
| + Serve0925 (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 19:30 | |
| + pomel0 (~pomel0@user/pomel0) | 19:31 | |
| minute | Murphy: uhm, that sounds like the issue elb had last night | 19:37 |
| minute | Murphy: do you have any possibility to check which kernel version was installed, i.e. can you do uname -a ? | 19:37 |
| minute | Murphy: (i guess hard with space key flood) | 19:37 |
| minute | Murphy: when did you do the upgrade? | 19:37 |
| Murphy | I updated last night from a pretty old version on an SD card | 19:39 |
| Murphy | if I switch to my local version its fine, so it seems software related | 19:39 |
| minute | Murphy: at which time exactly? | 19:39 |
| Murphy | must have been around 7ish pacific | 19:40 |
| Murphy | it took an hour or two to run an I think I started around 6pm pacific time | 19:40 |
| Murphy | let me check /boot on the SD card and see the kernel version | 19:41 |
| minute | Murphy: ok, then you got the faulty dtb i think. can you do another update/upgrade of linux-image-mnt-reform-arm64? | 19:41 |
| Murphy | I can try, otherwise no big deal since it's an SD card install. if its a known issue and it was fixed, no worries | 19:42 |
| minute | Murphy: i see, but in any case thanks for confirming it | 19:44 |
| Murphy | ya I'll see if I can get the kernel info just incase it helps | 19:45 |
| - mjw (QUIT: Ping timeout: 246 seconds) (~mjw@2001:1c06:2486:a800:158:adb1:a1e7:3c3f) | 19:45 | |
| Murphy | Ive been busy so I haven't had a chance to use my pocket. I picked up a MT7921AUN wifi/bt m.2 and im curious if it will work | 19:48 |
| Murphy | minute: its 6.17.6 | 19:56 |
| Murphy | btw is gnome-firmware supported yet? I don't see any new firmware since last time I was around | 19:57 |
| minute | Murphy: thx. and yes, gnome-firmware is supported | 20:00 |
| Murphy | I ordered the new expansion board yesterday and upgrade board. wanted to make sure im on the latest version | 20:00 |
| + mjw (~mjw@gnu.wildebeest.org) | 20:14 | |
| - Serve0925 (QUIT: Remote host closed the connection) (~Serve0925@2a0a:ef40:da7:b301:11d9:40ba:e142:b53) | 20:16 | |
| - Murphy (QUIT: Ping timeout: 250 seconds) (~Murphy@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 20:16 | |
| + Murphy (~Murphy@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 20:36 | |
| Murphy | ugh firmware-gnome crashes on first open then won't open again | 20:43 |
| josch | Murphy: could you open it from a terminal? Maybe there is useful output on stdout/stderr | 20:45 |
| * plomlompom0 -> plomlompom | 20:46 | |
| Murphy | fwupd_client_build_report_devices: assertion devices != NULL failed | 20:47 |
| Murphy | if I do verbose last message before that line is no report metadata | 20:48 |
| Murphy | wonder if running from sdcard is the problem | 20:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!