Re: d-i ftbfs on ppc64el-unicamp-01
On 2015-01-07 09:48, Aurelien Jarno wrote: On 2015-01-07 05:19, Cyril Brulebois wrote: Hi, d-i/ppc64el FTBFS on ppc64el-unicamp-01, probably due to a failure to get network access during the build: https://buildd.debian.org/status/fetch.php?pkg=debian-installerarch=ppc64elver=20150107stamp=1420603066 Please advise. It looks like the problem is that the sources.list is not generated correctly by the d-i script. This buildd uses weekly generated chroots by a DSA script, and I guess something is missing there. If it is urgent, we can build it on the non-DSAed non-autosigned buildd, otherwise I think i'll have time to have a deeper look tonight. The buildd chroots use a different configuration file for the sources.list, namely /etc/apt/sources.buildd.list. This file is therefore specified in /etc/apt.conf with the following line: Dir::Etc::SourceList sources.buildd.list; It seems that d-i sources.list generator doesn't take the configuration files into account. It works by chance on other buildds (but might use the wrong mirror if it has been modified since the chroot has been created), and doesn't work on automatically generated chroots as this file simply doesn't exist. I therefore guess this issue has to be fixed on the d-i side. However we can build this version on the non autosigned buildd, so that you don't have to do another upload just for that. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Re: d-i ftbfs on ppc64el-unicamp-01
On 2015-01-07 05:19, Cyril Brulebois wrote: Hi, d-i/ppc64el FTBFS on ppc64el-unicamp-01, probably due to a failure to get network access during the build: https://buildd.debian.org/status/fetch.php?pkg=debian-installerarch=ppc64elver=20150107stamp=1420603066 Please advise. It looks like the problem is that the sources.list is not generated correctly by the d-i script. This buildd uses weekly generated chroots by a DSA script, and I guess something is missing there. If it is urgent, we can build it on the non-DSAed non-autosigned buildd, otherwise I think i'll have time to have a deeper look tonight. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Re: d-i ftbfs on ppc64el-unicamp-01
Hi, Aurelien Jarno aurel...@aurel32.net (2015-01-07): The buildd chroots use a different configuration file for the sources.list, namely /etc/apt/sources.buildd.list. This file is therefore specified in /etc/apt.conf with the following line: Dir::Etc::SourceList sources.buildd.list; It seems that d-i sources.list generator doesn't take the configuration files into account. It works by chance on other buildds (but might use the wrong mirror if it has been modified since the chroot has been created), and doesn't work on automatically generated chroots as this file simply doesn't exist. Please file a bug report with the relevant files/contents so that the issue can be replicated outside a DSA-admin'd machine. I therefore guess this issue has to be fixed on the d-i side. However we can build this version on the non autosigned buildd, so that you don't have to do another upload just for that. That'd be appreciated, thanks already. Mraw, KiBi. signature.asc Description: Digital signature
d-i ftbfs on ppc64el-unicamp-01
Hi, d-i/ppc64el FTBFS on ppc64el-unicamp-01, probably due to a failure to get network access during the build: https://buildd.debian.org/status/fetch.php?pkg=debian-installerarch=ppc64elver=20150107stamp=1420603066 Please advise. Mraw, KiBi. signature.asc Description: Digital signature
