2026-08-03 07:56:18 <ikke> hmm
2026-08-03 08:03:53 <ikke> https://status.alpinelinux.org/incidents/216fe837-8e68-4000-8fa6-9a6a8a597617
2026-08-03 08:28:00 <lotheac> is it intended that status.alpinelinux.org does not have an A record
2026-08-03 08:28:17 <lotheac> my isp does not do v6
2026-08-03 08:45:58 <ikke> lotheac: The server does not have an ipv4 address
2026-08-03 08:56:12 <lotheac> okay, so that's a yes :)
2026-08-03 09:16:50 <ikke> They VM is being cold migrated
2026-08-03 10:45:56 <Sertonix[m]> The ckermit test failures look like the tests expect /etc/hosts to start with a localhost entry. Is that something that should be changed? Or do we consider the test suite faulty?
2026-08-03 10:46:32 <ikke> Sertonix[m]: I was looking at it
2026-08-03 10:46:53 <ikke> There is a hosts service which sets a <hostname>.local as first entry for 127.0.0.1 / ::1
2026-08-03 10:47:01 <ikke> But no package seems to provide that service
2026-08-03 10:47:06 <ikke> but I have the same in my build container
2026-08-03 10:48:19 <ikke> Note I already fixed it on aarch64 / armv7 / armhf, but it is failing for other reasons
2026-08-03 11:01:17 <Sertonix[m]> It looks like the tests also need the net option for rootbld. I think it makes sense to disable them on all arches
2026-08-03 11:51:46 <jvvv> ikke: mirrors workitem 1199 asks we check that our dns resolves their new ip. Am I being a jerk in thinking that their dns record propigation is something THEY should ensure, not us?
2026-08-03 11:52:09 <ikke> More or less, yes.
2026-08-03 11:52:27 <ikke> I mean, it's not our responsibility
2026-08-03 11:52:36 <jvvv> Thanks
2026-08-03 11:52:37 <ikke> We can verify what it resolves to for us
2026-08-03 11:53:54 <jvvv> I resolves from where I am at. Is there a way I can check or should I just ask when it comes up?
2026-08-03 11:55:18 <jvvv> Well, 'dig alpine.hacker.net A' returned the new ip
2026-08-03 11:57:10 <ikke> It does not seem to resolve on the host running mirror status
2026-08-03 11:57:15 <ikke> tried different resolvers
2026-08-03 12:00:31 <jvvv> Oh, well, could be because I gave the wrong address, should have been alpine.elhacker.net
2026-08-03 12:19:41 <jvvv> Some of the mirrors seem like they are down when they are checked for the mirros page and for zabbix, but later when I check they are up. Seems like could be a possible timing issue
2026-08-03 12:20:58 <jvvv> Of course I don't know why some of these servers would need nightly maintainence, seems excessive
2026-08-03 12:22:26 <ikke> returns 83.40.227.128
2026-08-03 12:48:12 <jvvv> That's the new address, thanks for confirming
2026-08-03 13:26:43 <jvvv> Would it be possible to update the mirror status page twice a day instead of just once?
2026-08-03 13:30:12 <jvvv> I don't know how much overhead this would cost, so I admit that my naivete in this regard may have precipitated the question
2026-08-03 13:55:35 <achill> hm, the aarch64 builder seems to be offline
2026-08-03 14:38:22 <ikke> achill: will bring it back online soon
2026-08-03 14:38:27 <ikke> was debugging ckermit
2026-08-03 14:47:33 <achill> ah right
2026-08-03 14:47:38 <achill> thx
2026-08-03 15:48:09 <jvvv> ikke: I've opened mirrors work item 1213 to start a more transparent view of what I am looking at with mirror issues. No hurry for you to look at. I am just trying to get a more organized workflow going forward.
2026-08-03 15:48:45 <ikke> ack, np