| 00:49:44 | <fireonlive> | oh interesting |
| 00:57:29 | <flashfire42> | we have a version 4? |
| 00:58:14 | <flashfire42> | Um maybe change the channel heading it points to version 3 still |
| 00:58:53 | <flashfire42> | cc chfoo arkiver |
| 02:39:52 | <Ryz> | What's the differences between version 4 and version 3? oo; |
| 02:40:19 | <Ryz> | tech234a, loading up the stuff, I see some new sstuff, I haven't seen before from the VM, it's updating |
| 02:41:27 | <Ryz> | tech234a, it woooooorks, woooooo >#<; |
| 02:56:33 | <tech234a> | cool, glad it works! |
| 02:57:57 | <tech234a> | re the differences between version 4 and version 3, I wrote something for the wiki. I wasn't involved in making version 4 (chfoo made it), so it's possible I missed something but this should give a general idea of the updates: https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#What's_new_in_version_4.0_of_the_Warrior_virtual_machine? |
| 03:15:21 | <@arkiver> | tech234a: chfoo: the wiki now notes the user can use 3.2 or 4 at the top of the page https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior |
| 03:15:43 | <@arkiver> | is there a good reason to keep mentioning 3.2 as option there? or should we leave this out and only mention version 4 as option to run with? |
| 03:17:20 | | nulldata quits [Ping timeout: 240 seconds] |
| 03:18:45 | <tech234a> | I'm not sure why warrior4 hasn't been promoted more. I know it was initially a beta but it looks like the July release on was marked as Stable on GitHub (instead of pre-release) https://github.com/ArchiveTeam/warrior4-vm/releases |
| 03:19:02 | <tech234a> | I assume chfoo would know more |
| 03:20:53 | <tech234a> | warrior4 wasn't listed on the wiki at all before I added it today, but maybe the links to 3.2 should be removed or at least placed lower on the page |
| 03:21:50 | <tech234a> | if we do that it would make sense to also update all the VirtualBox commands on the page that reference 3.2 |
| 03:24:25 | | nulldata (nulldata) joins |
| 03:34:17 | <tech234a> | also the listed Internet Archive and Syping Development (DE) links for 3.2 don't appear to be Archive Team-controlled |
| 03:35:28 | <@arkiver> | if chfoo can confirm that warrior4 is stable and has at least all features warrior3 has, then I think we can from now mention everywhere to use warrior4 instead of warrior3.2 |
| 03:37:47 | <tech234a> | I know it has a new patching technique compared to warrior3 |
| 03:38:29 | <tech234a> | Also it doesn't separate out the watchtower logs from the warrior container logs but I think that's kind of minor |
| 03:53:45 | <@arkiver> | tech234a: would it be easy to still add that? |
| 03:56:09 | <tech234a> | yeah looks like it could just be added based on https://github.com/ArchiveTeam/warrior4-vm/blob/main/appliance/skeleton/usr/bin/warrior4-display-logs and assigned to tty3 using https://github.com/ArchiveTeam/warrior4-vm/blob/main/appliance/skeleton/etc/inittab |
| 03:58:57 | <tech234a> | I don't think warrior4 downloads and runs a startup.sh on boot but I'm guessing the new patching mechanism is supposed to solve the problem in a different way |
| 04:00:18 | <tech234a> | The ability to update startup.sh was helpful in 2021 (new Docker image, add Watchtower) and again recently (system/Docker update) to make configuration changes to existing VMs. |
| 04:22:25 | <fireonlive> | looks like the new patching mech is here? https://github.com/ArchiveTeam/warrior4-vm/blob/main/appliance/script/patch.sh |
| 04:23:27 | <fireonlive> | ah that's the template |
| 04:26:58 | <fireonlive> | https://github.com/ArchiveTeam/warrior4-vm/blob/1677f2e2ef927281dc212bc99d204fc454f714cd/dev.md?plain=1#L82 https://github.com/ArchiveTeam/warrior4-vm/blob/1677f2e2ef927281dc212bc99d204fc454f714cd/crates/warrior4-appliance/src/manager.rs#L345 |
| 04:26:58 | <fireonlive> | https://github.com/ArchiveTeam/warrior4-vm/blob/1677f2e2ef927281dc212bc99d204fc454f714cd/crates/warrior4-appliance/src/manager.rs#L91 |
| 04:27:03 | <fireonlive> | if you were a curious kitty like me |
| 04:53:57 | | DogsRNice quits [Read error: Connection reset by peer] |
| 05:29:56 | | qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds] |
| 06:08:18 | <tech234a> | https://tracker.archiveteam.org/ also still points to warrior3 (and has an inaccurate file size) |
| 06:09:01 | <tech234a> | that whole section at the top should probably point more directly to the wiki or something |
| 06:15:31 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 07:45:14 | | atphoenix quits [Read error: Connection reset by peer] |
| 07:45:48 | | atphoenix (atphoenix) joins |
| 09:46:21 | | bladem quits [Client Quit] |
| 10:00:06 | | Bleo1826 quits [Client Quit] |
| 10:01:23 | | Bleo1826 joins |
| 11:31:31 | | systwi quits [Ping timeout: 272 seconds] |
| 11:38:38 | | systwi (systwi) joins |
| 12:16:57 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 16:31:37 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 17:05:20 | | andrew quits [Ping timeout: 240 seconds] |
| 17:05:34 | | andrew (andrew) joins |
| 17:26:49 | | andrew quits [Ping timeout: 272 seconds] |
| 17:38:45 | | andrew7 (andrew) joins |
| 17:52:27 | <that_lurker> | The link "ArchiveTeam Warrior " point to the warrior wiki |
| 17:52:44 | <that_lurker> | s/point/points |
| 20:30:17 | | trc (trc) joins |
| 21:31:41 | | jacksonchen666 (jacksonchen666) joins |
| 22:25:29 | | jacksonchen666 quits [Ping timeout: 250 seconds] |
| 22:37:54 | | bladem (bladem) joins |
| 22:43:33 | | yts98 leaves |
| 23:57:47 | | DogsRNice joins |