Austin Roach <ahro...@gmail.com> wrote: > Currently, this fails on sid because of an unsigned local repository (logfile > attached).
One note on that logfile: I added a 'printenv' to tmp/debian-cd/Makefile before the first 'apt-get update' call to help myself in debugging, and forgot to re-run without it before submitting the log. So this log has a dump of environment variables that you wouldn't expect to see in the standard log. > apt [...] now issues an error instead of a warning for insecure repositories. To add a little more detail, here is a snippet of the logfile from 'build-simple-cdd' executed on a machine running stretch, during the first apt-get update executed by tmp/debian-cd/Makefile: [...] 2017-10-21 07:33:20,578 DEBUG build/debian-cd stdout: # Updating the apt database 2017-10-21 07:33:20,610 DEBUG build/debian-cd stdout: Get:1 file:/home/testuser/scdd/tmp/mirror stretch InRelease 2017-10-21 07:33:20,610 DEBUG build/debian-cd stdout: Ign:1 file:/home/testuser/scdd/tmp/mirror stretch InRelease 2017-10-21 07:33:20,611 DEBUG build/debian-cd stdout: Get:2 file:/home/testuser/scdd/tmp/mirror stretch Release [1,482 B] 2017-10-21 07:33:20,621 DEBUG build/debian-cd stdout: Get:2 file:/home/testuser/scdd/tmp/mirror stretch Release [1,482 B] 2017-10-21 07:33:20,626 DEBUG build/debian-cd stdout: Get:3 file:/home/testuser/scdd/tmp/mirror stretch Release.gpg 2017-10-21 07:33:20,626 DEBUG build/debian-cd stdout: Ign:3 file:/home/testuser/scdd/tmp/mirror stretch Release.gpg 2017-10-21 07:33:20,629 DEBUG build/debian-cd stdout: Get:4 file:/home/testuser/scdd/tmp/mirror stretch/main amd64 Packages [129 kB] 2017-10-21 07:33:20,644 DEBUG build/debian-cd stdout: Get:5 file:/home/testuser/scdd/tmp/mirror stretch/main/debian-installer amd64 Packages [79.8 kB] 2017-10-21 07:33:20,697 DEBUG build/debian-cd stdout: Reading package lists... 2017-10-21 07:33:20,704 DEBUG build/debian-cd stderr: W: The repository 'file:/home/testuser/scdd/tmp/mirror stretch Release' is not signed. [...] Contrast this with the equivalent logfile from a machine running sid: [...] 2017-10-23 14:28:59,005 DEBUG build/debian-cd stdout: # Updating the apt database 2017-10-23 14:28:59,077 DEBUG build/debian-cd stdout: Get:1 file:/home/testuser/scdd/tmp/mirror sid InRelease 2017-10-23 14:28:59,078 DEBUG build/debian-cd stdout: Ign:1 file:/home/testuser/scdd/tmp/mirror sid InRelease 2017-10-23 14:28:59,078 DEBUG build/debian-cd stdout: Get:2 file:/home/testuser/scdd/tmp/mirror sid Release [1,474 B] 2017-10-23 14:28:59,097 DEBUG build/debian-cd stdout: Get:2 file:/home/testuser/scdd/tmp/mirror sid Release [1,474 B] 2017-10-23 14:28:59,099 DEBUG build/debian-cd stdout: Get:3 file:/home/testuser/scdd/tmp/mirror sid Release.gpg 2017-10-23 14:28:59,099 DEBUG build/debian-cd stdout: Ign:3 file:/home/testuser/scdd/tmp/mirror sid Release.gpg 2017-10-23 14:28:59,143 DEBUG build/debian-cd stdout: Reading package lists... 2017-10-23 14:28:59,143 DEBUG build/debian-cd stderr: E: The repository 'file:/home/testuser/scdd/tmp/mirror sid Release' is not signed. [...] On stretch, debian-cd successfully fetches the package lists from the local repo and stores them in tmp/cd-build/apt/$THIS_PKGSET/apt-state/lists/. On sid, the error prevents the package lists from being retrieved. You can observe the difference in behavior of apt-get directly by running the update command with the arguments as specified in tmp/debian-cd/tools/apt-selection: apt-get -q -o Dir::State::status=$APTTMP/$THIS_PKGSET/status \ -o Dir::State=$APTTMP/$THIS_PKGSET/apt-state/ \ -o Dir::Cache=$APTTMP/$THIS_PKGSET/apt-cache/ \ -o Dir::Etc=$APTTMP/$THIS_PKGSET/apt/ \ -o APT::Cache::AllVersions=0 \ -o APT::Cache::ShowVersion=1 \ -o APT::Architecture=$ARCH \ -o APT::Architectures::=$ARCH \ -o Acquire::Languages=none \ update Cheers, Austin