02:58:12asdfghwgwg joins
02:58:34Jack_Thompson joins
02:58:40asdfghwgwg quits [Remote host closed the connection]
04:26:46DogsRNice quits [Read error: Connection reset by peer]
07:20:19LeighR (LeighR) joins
15:38:18Jonboy345 quits [Read error: Connection reset by peer]
15:39:59Jonboy345 joins
15:49:39fofofofofofofofo quits [Quit: ZNC - https://znc.in]
15:50:28fofofofofofofofo joins
17:38:58LeGoupil joins
18:03:20Sylirana quits [Remote host closed the connection]
18:05:47Sylirana (Sylirana) joins
18:41:02etnguyen03 (etnguyen03) joins
18:43:27DogsRNice (Webuser299) joins
18:46:06hackerman joins
19:18:20LeGoupil quits [Client Quit]
19:34:21LeighR quits [Ping timeout: 244 seconds]
20:04:31LeighR (LeighR) joins
20:46:33luckcolors quits [Client Quit]
20:47:20LeGoupil joins
21:12:41<tech234a>Made a PR that should fix the issues reported about automatic Warrior updates via Watchtower https://github.com/ArchiveTeam/Ubuntu-Warrior/pull/18
21:16:19<tech234a>Once the PR is accepted the fixes will automatically be applied on next Warrior reboot (reboots are also automatically scheduled to take place every 7 days)
21:26:48LeGoupil quits [Client Quit]
21:34:08DoomsDay1990 (DoomsDay1990) joins
21:38:03EggplantN (EggplantN) joins
21:38:03@ChanServ sets mode: +o EggplantN
21:38:07<@EggplantN>what up tech234a
21:38:11<@EggplantN>what was the new changes
21:45:04<tech234a>Basically I don’t think the Warrior was correctly auto-updating because Watchtower wasn’t instructed to include stopped containers. I also added an immediate update check on startup.
21:45:10<tech234a>EggplantN: ^
21:47:49<tech234a>I think previously the Warrior was only pulling the correct images on initial startup
21:49:42<tech234a>*current images
22:01:35bit joins
22:04:19luckcolors (luckcolors) joins
22:21:18LeighR quits [Client Quit]