Your message dated Tue, 23 Jun 2020 18:49:26 +0200 with message-id <[email protected]> and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not found has caused the Debian Bug report #963372, regarding bsdmainutils must depend on bsdextrautils to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: pbuilder Version: 0.230.4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # syntax check. > bash -n bash_completion.d/pbuilder > bash -n pbuilderrc > bash -n pbuilderrc > bash -n debuild-pbuilder > bash -n pdebuild > bash -n pbuilder-apt-config > bash -n pbuilder-buildpackage > bash -n pbuilder-buildpackage-funcs > bash -n pbuilder-checkparams > bash -n pbuilder-createbuildenv > bash -n pbuilder-loadconfig > bash -n pbuilder-modules > bash -n pbuilder-runhooks > bash -n pbuilder-satisfydepends-apt > bash -n pbuilder-satisfydepends-aptitude > bash -n pbuilder-satisfydepends-checkparams > bash -n pbuilder-satisfydepends-classic > bash -n pbuilder-satisfydepends-experimental > bash -n pbuilder-satisfydepends-funcs > bash -n pbuilder-satisfydepends-gdebi > bash -n pbuilder-unshare-wrapper > bash -n pbuilder-updatebuildenv > bash -n pdebuild-checkparams > bash -n pdebuild-internal > bash -n pbuilder > bash -n examples/B90lintian > bash -n examples/B91dpkg-i > bash -n examples/B92test-pkg > bash -n examples/C10shell > bash -n examples/C11screen > bash -n examples/D10tmp > bash -n examples/D20addnonfree > bash -n examples/D65various-compiler-support > bash -n examples/D80no-man-db-rebuild > bash -n examples/D90chrootmemo > bash -n examples/F90chrootmemo > bash -n examples/B90list-missing > bash -n examples/B91debc > bash -n examples/B20autopkgtest > bash -n examples/execute_installtest.sh > bash -n examples/execute_paramtest.sh > bash -n examples/pbuilder-distribution.sh > bash -n examples/lvmpbuilder/lvmbuilder > bash -n examples/lvmpbuilder/lib/lvmbuilder-checkparams > bash -n examples/lvmpbuilder/lib/lvmbuilder-modules > bash -n examples/lvmpbuilder/lib/lvmbuilder-unimplemented > bash -n examples/pbuilder-test/000_prepinstall > bash -n examples/pbuilder-test/001_apprun > bash -n examples/pbuilder-test/002_libfile > bash -n examples/pbuilder-test/003_makecheck > bash -n examples/pbuilder-test/004_ldd > bash -n examples/rebuild/buildall > bash -n examples/rebuild/getlist > LANG=C MANWIDTH=80 man --warnings -l debuild-pbuilder.1 >/dev/null > man: can't execute col: No such file or directory > man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ > N; /^[[:space:]]*\n[[:space:]]*$/D; }' > make[1]: *** [Makefile:163: check] Error 3 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: error: make -j4 check returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/06/20/pbuilder_0.230.4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Hi, Lucas Nussbaum <[email protected]> wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<<PKGBUILDDIR>>' > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16a.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16a-double.bdf > > groff -mandoc -Tascii /<<PKGBUILDDIR>>/man/bdf2psf.1 | col -bx > > >/<<PKGBUILDDIR>>/man/bdf2psf.1.txt > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16b.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16b-double.bdf > > groff -mandoc -Tascii /<<PKGBUILDDIR>>/man/console-setup.5 | col -bx > > >/<<PKGBUILDDIR>>/man/console-setup.5.txt > > /bin/sh: 1: col: not found > > /bin/sh: 1: col: not found > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16c.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16c-double.bdf > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16d.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16d-double.bdf > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16e.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16e-double.bdf > > bdfresize -f 2 -b 1 /<<PKGBUILDDIR>>/Fonts/bdf/legacy16f.bdf > > >/<<PKGBUILDDIR>>/Fonts/bdf/legacy16f-double.bdf > > make[1]: *** [Makefile:137: /<<PKGBUILDDIR>>/man/console-setup.5.txt] Error > > 127 This was apparently caused by the take-over of several bsd tools (including col) by util-linux two days ago. Builds fine again now. So closing this bug. Holger -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
