Your message dated Mon, 13 Feb 2006 11:41:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348649: ftbfs: "I can't find file `policy.aux'."
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: java-common
Version: 0.23
Tags: FTBFS
Severity: minor
This is e-TeX, Version 3.14159-2.1 (Web2C 7.4.5)
entering extended mode
(/opt/debian/build/java-common-0.23/policy.tex
JadeTeX 2003/04/27: 3.13
(/usr/share/texmf/tex/latex/psnfss/t1ptm.fd)
Elements will be labelled
! LaTeX Error: Missing \begin{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.8 {0:2}}D
ebian policy for Java\endNode{}\Node%
[1.0.53]
! I can't find file `policy.aux'.
\enddocument ...makeatletter \input \jobname .aux
\fi [EMAIL PROTECTED]
\ifdim \f...
l.611 ...de{}\endNode{}\endNode{}\endNode{}\endFOT
{}
Please type another input file name
! Emergency stop.
\enddocument ...makeatletter \input \jobname .aux
\fi [EMAIL PROTECTED]
\ifdim \f...
l.611 ...de{}\endNode{}\endNode{}\endNode{}\endFOT
{}
Output written on policy.dvi (1 page, 12500 bytes).
Transcript written on policy.log.
make[1]: *** [policy.dvi] Error 9
make[1]: Leaving directory `/opt/debian/build/java-common-0.23'
make: *** [build-stamp] Error 2
Build command 'cd java-common-0.23 && dpkg-buildpackage -b -uc'
failed.
--- End Message ---
--- Begin Message ---
Max Kellermann wrote:
> On 2006/02/10 16:46, Wolfgang Baer <[EMAIL PROTECTED]> wrote:
>
>>I just tried it on an uptodate sid and with an uptodate pbuilder and
>>both built java-common without a problem.
>
>
> It does not fail anymore; I suspect the build dependencies were
> somehow not sufficient, and I upgraded a lot of other packages
> meanwhile.
Thanks for the feedback. As I have tested the build also in a pbuilder,
insufficient build dependencies are unlikely.
Closing the bug.
Wolfgang
--- End Message ---
