Unconditionally print hint about noatime. This problem seems to occur
quite rarely (noatime is out of fashion nowadays, and I haven't seen
any other causes) so it doesn't seem worth fiddling about writing code
to determine the mount options. Instead, print a hint and let the
user investigate.
Closes:#851873.
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
dgit (5.11~) unstable; urgency=medium
* test suite: unset VISUAL, which interferes. Closes:#904308.
+ * apt-get method: when apt does not update release files,
+ unconditionally print hint about noatime. Closes:#851873.
--
}
my @inreleasefiles = grep { m#/InRelease$# } @releasefiles;
@releasefiles = @inreleasefiles if @inreleasefiles;
- die "apt updated wrong number of Release files (@releasefiles), erk"
+ if (!@releasefiles) {
+ fail <<END;
+apt seemed to not to update dgit's cached Release files for $isuite.
+(Perhaps $cache
+ is on a filesystem mounted `noatime'; if so, please use `relatime'.)
+END
+ }
+ die "apt updated too many Release files (@releasefiles), erk"
unless @releasefiles == 1;
($aptget_releasefile) = @releasefiles;