reassign 302827 tetex-bin severity 302827 important thanks On Wed, Apr 06, 2005 at 01:33:19PM -0700, Steve Langasek wrote: > reassign 302827 jadetex > thanks
> On Wed, Apr 06, 2005 at 09:10:28AM +0200, Frank Küster wrote:
> > since I must go on "vacaction" for several weeks, and I'm unsure whether
> > there is enough "(wo)manpower" on debian-tetex-maint to resolve this
> > bug, I recommend that you keep a close look at it.
>
> > All my activities so far are recorded in the bug log. I have tried to
> > contact the buildd admins only by mailing to rian murray whose address
> > is at the bottom of the build logs - probably you know better than I how
> > to get in contact with the right people.
>
> > In my opinion, the first step to resolve this should be to check what
> > exactly is messed up in the build environments of the failing hosts,
> > clean it up, and verify whether this is the cause of the bug.
> Yeah, the architectures that failed to build pdns previously have all
> successfully built the subsequent version of it. I suspect this isn't a
> tetex-bin bug at all, so am downgrading it.
> One of the more suspicious lines in the log of the build failures is
> Error: `etex -ini -jobname=jadetex -progname=jadetex &latex jadetex.ini'
> failed
>
> This happens during the setup of tetex-bin, *before* jadetex has been
> configured; so I think this is actually a bug, probably historic, in
> jadetex, which seems to have left config files around incorrectly on purge.
> Reassigning to jadetex accordingly for further investigation; hopefully this
> is a known bug in previous versions of jadetex that have since been fixed.
... nope, guessed wrong here. Reassigning back to tetex-bin.
This bug has been fixed in tetex-bin 2.0.2-28:
tetex-bin (2.0.2-28) unstable; urgency=low
* The maintainer scripts now will again fail if the format or map file
generation fails. This has been turned into a debconf note in version
2.0.2-19 as an emergency action, and must be dropped now the packages
proved to be stable.
This might reveal some bugs that had been hidden so far, and might
help debug #302827. [frank]
* In postinst, fix language.dat if it points to an old french
hyphenation file that we no longer ship, and which only loaded the new
one even in woody, thanks to Sven Koch <[EMAIL PROTECTED]> (closes:
#302286) [frank]
-- Frank Küster <[EMAIL PROTECTED]> Mon, 4 Apr 2005 20:41:26 +0200
Frank, this install failure was *caused by the use of debconf*. The
debconf-devel(7) explanation for INPUT (db_input) says:
Debconf decides if the question is actually displayed, based on
its priority, and whether the user has seen it before, and which
frontend is being used. If the question will not be displayed,
debconf replies with code 30.
You were not checking the return code of db_input; therefore, the maintainer
script was exiting with code 30 on the buildds.
The actual format creation failures all seem to have been caused by stale
config files on the system from previous versions of jadetex; but the
tetex-bin install failure was caused by this misuse of debconf.
If you are going to readd the debconf note at a later date, please make sure
you fix this usage problem. (If what you really want is to force the
display of the debconf note, you should be using db_fset seen.) If you are
not going to readd the debconf note in the future, then this bug can be
closed.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
