:: Re: [devuan-dev] deb.devuan.org rou…
Top Page
Delete this message
Reply to this message
Author: Olaf Meeuwissen
To: devuan developers internal list
Subject: Re: [devuan-dev] deb.devuan.org round-robin causing pain
Hi Boian,

Boian Bonev <bbonev@???> writes:

> Hi Olaf,
> Just removed it. It was added there by mistake. The intention of the mirror,
> AFAIU is to serve nz.deb.devuan.org and not deb.devuan.org besides its
> canonical name.

Thanks. The build of an updated devuan/devuan:ceres image has now
completed successfully on the second try.

> BTW. Did you try the more regional country code round-robins? E.g.
> jp.deb.devuan.org (guessing by your time zone) or some of the ones in EU?

No, because a regional round-robin should not end up in the Devuan
Docker Hub images ;-)

> With best regards,
> b.
> On Sat, 2023-03-18 at 00:33 +0900, Olaf Meeuwissen wrote:
>> Hi,
>> For the last two, three hours I've been experiencing rather persistent
>> package download failures trying to debootstrap and migrate releases for
>> my Docker images in CI/CD jobs.  All use
>>   http://deb.devuan.org/merged
>> in their sources.list.
>> Normally, the jobs taking care of this succeed without a hitch (unless I
>> screw things up), but debootstrap has been unable to download "random"
>> packages and migrations show similar symptoms.  The random bit is in the
>> packages that fail to download.  These differ between jobs.
>> Unfortunately, debootstrap hides the server it tries to download from
>> but other package downloads in the jobs that use it, as well as the
>> migration jobs, point at being the culprit.
>> A reverse DNS lookup[1] says that's mx1.4mail.nz (which is not on the
>> list of mirrors[2], btw).
>>  [1]: https://www.nslookup.io/ip/
>>  [2]: https://www.devuan.org/get-devuan
>> If someone could address this that would be appreciated.  Here address
>> could be one of getting that server to get its act together or take it
>> of the round-robin DNS until it giet its act together.
>> Right now, trying to download packages is a crap-shoot from where I'm
>> at.  BTW, you can see the results of that in the failed build jobs at
>>   https://gitlab.com/paddy-hack/container-images/-/pipelines/809891130
>>   https://gitlab.com/paddy-hack/container-images/-/pipelines/810031670
>> Hope this helps,

Olaf Meeuwissen