Hi, since I didn't receive Bdale's mail, I'm answering to Martin-Éric's answer:
> pe, 2006-01-06 kello 17:30 -0700, Bdale Garbee kirjoitti: >> >> /var/lib/dpkg/info/tetex-base.postinst: line 678: update-language: >> >> command not found >> >> Reading tetex-base.postinst, update-language is being called without an >> explicit path specification: >> >> # Update language.dat (update-language is in tex-common on which we depend) >> update-language >> >> Since this script gets put in /usr/sbin, if it's "not found" I presume it's >> because the file truly isn't present yet, The file is in the tex-common deb, and since tetex-base depends on tex-common, tex-common should not only be unpacked, but even configured. >> /usr/sbin isn't in PATH, How should that happen? Surprised I find that Policy does not specifiy what should be in the PATH, but /usr/sbin for sure will, and Policy specifically says that maintainer scripts should call executables without prepending a path. >> or the >> execute bit in the permissions for that script isn't set. Since tex-common is an arch: all package, this would happen on *every* host - and tetex-base can be installed fine even on hppa machines other than sarti's debbuild chroot. If you show me the error in the (te)TeX packages that cause this, I'll be glad to fix it; but currently it doesn't seem as if there was any - just a buildd with messy hardware (or whatever) and no communication from the admins. As it stands, I'm going to downgrade all FTBFS-on-sarti bugs reported against my packages to important unless they *really* look like arch-specific. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer