While testing out a ticket, I accidentally asked Sage to build some of its fake packages, like pandoc or perl_cpan_polymake_prereq. (Well, I asked it to build packages for which these were dependencies.) These fail with messages like
Error: pandoc is a dummy script package that the Sage distribution uses to provide information about equivalent system packages. It cannot be installed using the Sage distribution. Please install it manually, for example using the system packages recommended at the end of a run of './configure' See below for package-specific information. ... Unfortunately, this message is buried in `logs/install.log` and appears in no file in `logs/pkgs`, so when the build fails, Sage can't identify the problematic package, and you have to comb through `install.log` to find it. Could dummy packages write proper logs with error messages so that the build process can identify what's going wrong? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/79c6b004-aaa8-44e8-a153-f7eb292788e4n%40googlegroups.com.
