/srv/irclogs.ubuntu.com/2023/03/16/#ubuntu-quality.txt

-queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.6] has been marked as ready12:38
-queuebot:#ubuntu-quality- Builds: Ubuntu Desktop (Legacy) amd64 [Focal 20.04.6] has been updated (20230316)16:00
-queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.6] has been updated (20230316)18:33
-queuebot:#ubuntu-quality- Builds: Xubuntu Desktop amd64 [Focal 20.04.6] has been updated (20230316)18:36
-queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Focal 20.04.6] has been updated (20230316)18:37
-queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.6] has been updated (20230316)18:38
-queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.6] has been updated (20230316)18:38
ubuntubridgebot[telegram] <teward001> i believe that's because the system decided to explode during an i/o timeout (re @bittin1: seems the bridge to IRC from Telegram is down btw)21:43
teward*this is a test of the emergency broadcast system*21:43
ubuntubridgebot[telegram] <teward001> good it works again21:43
ubuntubridgebot[telegram] <teward001> *returns to the abyss*21:43
guivercthanks teward 21:54
ubuntubridgebot[telegram] <teward001> yep21:55
ubuntubridgebot[telegram] <teward001> @bittin1 when in doubt it's probably me running the relay21:55
ubuntubridgebot[telegram] <teward001> in this case there was a network blip and an I/O timeout that repeated on the 14th for the entire day and it resulted in a timeout on retry21:55
ubuntubridgebot[telegram] <teward001> eventually it just dies on retries ;)21:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!