TeX broken in Hardy?

[Fred]

Binary package hint: texlive

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

ii tex-common 1.10 common infrastructure for building and insta
ii texlive-base 2007-13 TeX Live: Essential programs and files
ii texlive-base-bin 2007.dfsg.1-2 TeX Live: Essential binaries
ii texlive-common 2007-13 TeX Live: Base component
ii texlive-doc-base 2007-3 TeX Live: Base documentation
ii texlive-fonts-recommended 2007-13 TeX Live: Recommended fonts
ii texlive-latex-base 2007-13 TeX Live: Basic LaTeX packages
ii texlive-latex-recommended 2007-13 TeX Live: LaTeX recommended packages

I think TeX is broken in Hardy Heron.

$ pdftex noob.tex
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
(./noob.tex
! Undefined control sequence.
l.1 \documentclass
                  {article}
?
! Undefined control sequence.
l.2 \begin
          {document}
?
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] )</usr/share/texmf-texli
ve/fonts/type1/bluesky/cm/cmr10.pfb>
Output written on noob.pdf (1 page, 7050 bytes).
Transcript written on noob.log.

--------------

$ cat noob.log
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=pdftex 2008.1.20) 29 FEB 2008 18:29
entering extended mode
 %&-line parsing enabled.
**noob.tex
(./noob.tex
! Undefined control sequence.
l.1 \documentclass
                  {article}
?
! Undefined control sequence.
l.2 \begin
          {document}
?
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] )</usr/share/texmf-texli
ve/fonts/type1/bluesky/cm/cmr10.pfb>
Output written on noob.pdf (1 page, 7050 bytes).
PDF statistics:
 10 PDF objects out of 1000 (max. 8388607)
 0 named destinations out of 1000 (max. 131072)
 1 words of extra memory for PDF output out of 10000 (max. 10000000)

---

$ cat noob.tex
\documentclass{article}
\begin{document}
  Hello, world!
\end{document}

[Ralph Janke (txwikinger)]

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs