gettext: Installation failed

[Debian Bug Importer]

Automatically imported from Debian bug report #260048 http://bugs.debian.org/260048

[Santiago Vila Doncel (sanvila-unex)]

On Sun, 18 Jul 2004, Pierre Machard wrote:

> Package: gettext
> Version: 0.14.1-2
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> it seems that the lastest gettext package is not installing properly.
> According to different autobuilder we have :
>
> Setting up gettext (0.14.1-3) ...
>
> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine
> description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1
>
> Could you please fix this issue ?
> (You can find build log on build.d.o for example on lirc package)

Thanks for the report. Working on it.

[Andreas Metzler (ametzler-downhill)]

Pierre Machard <email address hidden> wrote:
> Setting up gettext (0.14.1-3) ...

> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine
> description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1

> Could you please fix this issue ?
> (You can find build log on build.d.o for example on lirc package)

Looks like the ARM package was not correctly built:

ametzler@merkel:~$ ls -l gettext_0.14.1-3_*/usr/share/info/g*
     0 Jul 17 13:13 gettext_0.14.1-3_arm/usr/share/info/gettext.info
564888 Jul 17 12:55 gettext_0.14.1-3_hppa/usr/share/info/gettext.info

Comparing build-logs of gettext on hppa and arm shows these
differences:
-checking for dvips... /build/buildd/gettext-0.14.1/config/missing dvips
-checking for texi2pdf... /build/buildd/gettext-0.14.1/config/missing texi2pdf
+checking for dvips... /usr/bin/dvips
+checking for texi2pdf... /usr/bin/texi2pdf

-/build/buildd/gettext-0.14.1/config/missing: line 46: makeinfo: command not fou
nd
-WARNING: `makeinfo' is missing on your system. You should only need it if
- you modified a `.texi' or `.texinfo' file, or any other file
- indirectly affecting the aspect of the manual. The spurious
[...]

And the diff indeed changes the texinfo input file:
ametzler@merkel:~$ ./patchut/usr/bin/lsdiff -z /org/ftp.root/debian/pool/main/g/gettext/gettext_0.14.1-3.diff.gz | grep 'doc/gettext\.'
gettext-0.14.1/gettext-tools/doc/gettext.texi
gettext-0.14.1/gettext-tools/doc/gettext.info

This is reproducible on ix86, gettext.info is truncated at
"make install".
              cu andreas

                  cu andreas

--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[Santiago Vila Doncel (sanvila-unex)]

On Sun, 18 Jul 2004, Andreas Metzler wrote:

> Pierre Machard <email address hidden> wrote:
> > Setting up gettext (0.14.1-3) ...
>
> > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > install-info(/usr/share/info/gettext.info): unable to determine
> > description for `dir' entry - giving up
> > dpkg: error processing gettext (--configure):
> > subprocess post-installation script returned error exit status 1
>
> > Could you please fix this issue ?
> > (You can find build log on build.d.o for example on lirc package)
>
> Looks like the ARM package was not correctly built:
>
> ametzler@merkel:~$ ls -l gettext_0.14.1-3_*/usr/share/info/g*
> 0 Jul 17 13:13 gettext_0.14.1-3_arm/usr/share/info/gettext.info
> 564888 Jul 17 12:55 gettext_0.14.1-3_hppa/usr/share/info/gettext.info
>
> Comparing build-logs of gettext on hppa and arm shows these
> differences:
> -checking for dvips... /build/buildd/gettext-0.14.1/config/missing dvips
> -checking for texi2pdf... /build/buildd/gettext-0.14.1/config/missing texi2pdf
> +checking for dvips... /usr/bin/dvips
> +checking for texi2pdf... /usr/bin/texi2pdf
>
> -/build/buildd/gettext-0.14.1/config/missing: line 46: makeinfo: command not fou
> nd
> -WARNING: `makeinfo' is missing on your system. You should only need it if
> - you modified a `.texi' or `.texinfo' file, or any other file
> - indirectly affecting the aspect of the manual. The spurious
> [...]
>
> And the diff indeed changes the texinfo input file:
> ametzler@merkel:~$ ./patchut/usr/bin/lsdiff -z /org/ftp.root/debian/pool/main/g/gettext/gettext_0.14.1-3.diff.gz | grep 'doc/gettext\.'
> gettext-0.14.1/gettext-tools/doc/gettext.texi
> gettext-0.14.1/gettext-tools/doc/gettext.info
>
> This is reproducible on ix86, gettext.info is truncated at
> "make install".
> cu andreas

Your analysis is correct. I tried to avoid a "Build-Depends: texinfo" by
touching some files in debian/touch-more-files, but this was not enough.

I have just modified debian/touch-more-files to this:

touch gettext-tools/doc/stamp-vti
touch gettext-tools/doc/version.texi
touch gettext-tools/doc/gettext.info
touch gettext-tools/doc/*.html
touch gettext-runtime/ABOUT-NLS
touch gettext-tools/ABOUT-NLS

and now it works. Will make a new upload today.

[Santiago Vila (sanvila)]

Source: gettext
Source-Version: 0.14.1-4

We believe that the bug you reported is fixed in the latest version of
gettext, which is due to be installed in the Debian FTP archive:

gettext-base_0.14.1-4_i386.deb
  to pool/main/g/gettext/gettext-base_0.14.1-4_i386.deb
gettext-doc_0.14.1-4_all.deb
  to pool/main/g/gettext/gettext-doc_0.14.1-4_all.deb
gettext-el_0.14.1-4_all.deb
  to pool/main/g/gettext/gettext-el_0.14.1-4_all.deb
gettext_0.14.1-4.diff.gz
  to pool/main/g/gettext/gettext_0.14.1-4.diff.gz
gettext_0.14.1-4.dsc
  to pool/main/g/gettext/gettext_0.14.1-4.dsc
gettext_0.14.1-4_i386.deb
  to pool/main/g/gettext/gettext_0.14.1-4_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila <email address hidden> (supplier of updated gettext package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 18 Jul 2004 13:39:06 +0200
Source: gettext
Binary: gettext-doc gettext gettext-base gettext-el
Architecture: source all i386
Version: 0.14.1-4
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila <email address hidden>
Changed-By: Santiago Vila <email address hidden>
Description:
 gettext - GNU Internationalization utilities
 gettext-base - GNU Internationalization utilities for the base system
 gettext-doc - Documentation for GNU gettext
 gettext-el - Emacs po-mode for editing .po files
Closes: 260048
Changes:
 gettext (0.14.1-4) unstable; urgency=low
 .
   * Fixed info file (Closes: #260048).
Files:
 77e1e957fff0e3c888398b7abc9b2a35 662 devel optional gettext_0.14.1-4.dsc
 67a824ea42ff88021de2857f4778b45e 126001 devel optional gettext_0.14.1-4.diff.gz
 9e7ada2b056e56ea1f51b73c7c4f64b6 45226 devel optional gettext-el_0.14.1-4_all.deb
 d14ca3aa3144ae66763293057d4dd2a8 638806 doc optional gettext-doc_0.14.1-4_all.deb
 52daeae018dfb265763e01c22c259c32 91272 base standard gettext-base_0.14.1-4_i386.deb
 fdc02297cd582d7a9e5af074ecafb811 1556662 devel optional gettext_0.14.1-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+mKxd9Uuvj7yPNYRApn5AKC+wr4zecsyrq4HJBBmd+A8hNF0CQCgpHpy
hLYL0dt0ilkLrqNeJ+Aco1w=
=3CCS
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #260048 http://bugs.debian.org/260048

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 03:58:46 +0200
From: Pierre Machard <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: gettext: Installation failed

--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: gettext
Version: 0.14.1-2
Severity: grave
Justification: renders package unusable

Hi,

it seems that the lastest gettext package is not installing properly.
According to different autobuilder we have :

Setting up gettext (0.14.1-3) ...

No `START-INFO-DIR-ENTRY' and no `This file documents'.
install-info(/usr/share/info/gettext.info): unable to determine
description for `dir' entry - giving up
dpkg: error processing gettext (--configure):
 subprocess post-installation script returned error exit status 1

Could you please fix this issue ?
(You can find build log on build.d.o for example on lirc package)

Cheers,
--=20
                                Pierre Machard
<email address hidden> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87

--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+dlWs6AtZiNwb4cRAkXwAKCUkYklUAptxO8bjhiQ5iNZS8OUAQCeO3Jr
yX9i8imUxwEWpM/pdv1LGWc=
=7pwU
-----END PGP SIGNATURE-----

--SLDf9lqlvOQaIe6s--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 12:23:10 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: Pierre Machard <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: gettext: Installation failed

On Sun, 18 Jul 2004, Pierre Machard wrote:

> Package: gettext
> Version: 0.14.1-2
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> it seems that the lastest gettext package is not installing properly.
> According to different autobuilder we have :
>
> Setting up gettext (0.14.1-3) ...
>
> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine
> description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1
>
> Could you please fix this issue ?
> (You can find build log on build.d.o for example on lirc package)

Thanks for the report. Working on it.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 12:55:23 +0200
From: Andreas Metzler <email address hidden>
To: <email address hidden>
Cc: Pierre Machard <email address hidden>
Subject: Re: gettext: Installation failed

Pierre Machard <email address hidden> wrote:
> Setting up gettext (0.14.1-3) ...

> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine
> description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1

> Could you please fix this issue ?
> (You can find build log on build.d.o for example on lirc package)

Looks like the ARM package was not correctly built:

ametzler@merkel:~$ ls -l gettext_0.14.1-3_*/usr/share/info/g*
     0 Jul 17 13:13 gettext_0.14.1-3_arm/usr/share/info/gettext.info
564888 Jul 17 12:55 gettext_0.14.1-3_hppa/usr/share/info/gettext.info

Comparing build-logs of gettext on hppa and arm shows these
differences:
-checking for dvips... /build/buildd/gettext-0.14.1/config/missing dvips
-checking for texi2pdf... /build/buildd/gettext-0.14.1/config/missing texi2pdf
+checking for dvips... /usr/bin/dvips
+checking for texi2pdf... /usr/bin/texi2pdf

-/build/buildd/gettext-0.14.1/config/missing: line 46: makeinfo: command not fou
nd
-WARNING: `makeinfo' is missing on your system. You should only need it if
- you modified a `.texi' or `.texinfo' file, or any other file
- indirectly affecting the aspect of the manual. The spurious
[...]

And the diff indeed changes the texinfo input file:
ametzler@merkel:~$ ./patchut/usr/bin/lsdiff -z /org/ftp.root/debian/pool/main/g/gettext/gettext_0.14.1-3.diff.gz | grep 'doc/gettext\.'
gettext-0.14.1/gettext-tools/doc/gettext.texi
gettext-0.14.1/gettext-tools/doc/gettext.info

This is reproducible on ix86, gettext.info is truncated at
"make install".
              cu andreas

                  cu andreas

--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 13:31:11 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: Andreas Metzler <email address hidden>,
 <email address hidden>
Cc: Pierre Machard <email address hidden>
Subject: Re: Bug#260048: gettext: Installation failed

On Sun, 18 Jul 2004, Andreas Metzler wrote:

> Pierre Machard <email address hidden> wrote:
> > Setting up gettext (0.14.1-3) ...
>
> > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > install-info(/usr/share/info/gettext.info): unable to determine
> > description for `dir' entry - giving up
> > dpkg: error processing gettext (--configure):
> > subprocess post-installation script returned error exit status 1
>
> > Could you please fix this issue ?
> > (You can find build log on build.d.o for example on lirc package)
>
> Looks like the ARM package was not correctly built:
>
> ametzler@merkel:~$ ls -l gettext_0.14.1-3_*/usr/share/info/g*
> 0 Jul 17 13:13 gettext_0.14.1-3_arm/usr/share/info/gettext.info
> 564888 Jul 17 12:55 gettext_0.14.1-3_hppa/usr/share/info/gettext.info
>
> Comparing build-logs of gettext on hppa and arm shows these
> differences:
> -checking for dvips... /build/buildd/gettext-0.14.1/config/missing dvips
> -checking for texi2pdf... /build/buildd/gettext-0.14.1/config/missing texi2pdf
> +checking for dvips... /usr/bin/dvips
> +checking for texi2pdf... /usr/bin/texi2pdf
>
> -/build/buildd/gettext-0.14.1/config/missing: line 46: makeinfo: command not fou
> nd
> -WARNING: `makeinfo' is missing on your system. You should only need it if
> - you modified a `.texi' or `.texinfo' file, or any other file
> - indirectly affecting the aspect of the manual. The spurious
> [...]
>
> And the diff indeed changes the texinfo input file:
> ametzler@merkel:~$ ./patchut/usr/bin/lsdiff -z /org/ftp.root/debian/pool/main/g/gettext/gettext_0.14.1-3.diff.gz | grep 'doc/gettext\.'
> gettext-0.14.1/gettext-tools/doc/gettext.texi
> gettext-0.14.1/gettext-tools/doc/gettext.info
>
> This is reproducible on ix86, gettext.info is truncated at
> "make install".
> cu andreas

Your analysis is correct. I tried to avoid a "Build-Depends: texinfo" by
touching some files in debian/touch-more-files, but this was not enough.

I have just modified debian/touch-more-files to this:

touch gettext-tools/doc/stamp-vti
touch gettext-tools/doc/version.texi
touch gettext-tools/doc/gettext.info
touch gettext-tools/doc/*.html
touch gettext-runtime/ABOUT-NLS
touch gettext-tools/ABOUT-NLS

and now it works. Will make a new upload today.

[LaMont Jones (lamont)]

reopen 260048
--

Maybe it would be a good idea to have the gettext build fail if
/usr/share/info/gettext.info is empty (--> gettext.info.gz is 33 bytes)

lamont

> Setting up gettext (0.14.1-4) ...

> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sun, 18 Jul 2004 08:02:05 -0400
From: Santiago Vila <email address hidden>
To: <email address hidden>
Subject: Bug#260048: fixed in gettext 0.14.1-4

Source: gettext
Source-Version: 0.14.1-4

We believe that the bug you reported is fixed in the latest version of
gettext, which is due to be installed in the Debian FTP archive:

gettext-base_0.14.1-4_i386.deb
  to pool/main/g/gettext/gettext-base_0.14.1-4_i386.deb
gettext-doc_0.14.1-4_all.deb
  to pool/main/g/gettext/gettext-doc_0.14.1-4_all.deb
gettext-el_0.14.1-4_all.deb
  to pool/main/g/gettext/gettext-el_0.14.1-4_all.deb
gettext_0.14.1-4.diff.gz
  to pool/main/g/gettext/gettext_0.14.1-4.diff.gz
gettext_0.14.1-4.dsc
  to pool/main/g/gettext/gettext_0.14.1-4.dsc
gettext_0.14.1-4_i386.deb
  to pool/main/g/gettext/gettext_0.14.1-4_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila <email address hidden> (supplier of updated gettext package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 18 Jul 2004 13:39:06 +0200
Source: gettext
Binary: gettext-doc gettext gettext-base gettext-el
Architecture: source all i386
Version: 0.14.1-4
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila <email address hidden>
Changed-By: Santiago Vila <email address hidden>
Description:
 gettext - GNU Internationalization utilities
 gettext-base - GNU Internationalization utilities for the base system
 gettext-doc - Documentation for GNU gettext
 gettext-el - Emacs po-mode for editing .po files
Closes: 260048
Changes:
 gettext (0.14.1-4) unstable; urgency=low
 .
   * Fixed info file (Closes: #260048).
Files:
 77e1e957fff0e3c888398b7abc9b2a35 662 devel optional gettext_0.14.1-4.dsc
 67a824ea42ff88021de2857f4778b45e 126001 devel optional gettext_0.14.1-4.diff.gz
 9e7ada2b056e56ea1f51b73c7c4f64b6 45226 devel optional gettext-el_0.14.1-4_all.deb
 d14ca3aa3144ae66763293057d4dd2a8 638806 doc optional gettext-doc_0.14.1-4_all.deb
 52daeae018dfb265763e01c22c259c32 91272 base standard gettext-base_0.14.1-4_i386.deb
 fdc02297cd582d7a9e5af074ecafb811 1556662 devel optional gettext_0.14.1-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+mKxd9Uuvj7yPNYRApn5AKC+wr4zecsyrq4HJBBmd+A8hNF0CQCgpHpy
hLYL0dt0ilkLrqNeJ+Aco1w=
=3CCS
-----END PGP SIGNATURE-----

[Santiago Vila Doncel (sanvila-unex)]

On Sun, 18 Jul 2004, LaMont Jones wrote:

> reopen 260048
> --
>
> Maybe it would be a good idea to have the gettext build fail if
> /usr/share/info/gettext.info is empty (--> gettext.info.gz is 33 bytes)
>
> lamont
>
> > Setting up gettext (0.14.1-4) ...
>
> > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > dpkg: error processing gettext (--configure):
> > subprocess post-installation script returned error exit status 1

I can't reproduce this. Which architecture, please? The packages I see
for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.

[LaMont Jones (lamont)]

On Sun, Jul 18, 2004 at 04:32:53PM +0200, Santiago Vila wrote:
> > > Setting up gettext (0.14.1-4) ...
> >
> > > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > > dpkg: error processing gettext (--configure):
> > > subprocess post-installation script returned error exit status 1
> I can't reproduce this. Which architecture, please? The packages I see
> for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.

This is installing 0.14.1-4 on ia64. See, for example:
http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

lamont

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 07:37:55 -0600
From: LaMont Jones <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: still happening

reopen 260048
--

Maybe it would be a good idea to have the gettext build fail if
/usr/share/info/gettext.info is empty (--> gettext.info.gz is 33 bytes)

lamont

> Setting up gettext (0.14.1-4) ...

> No `START-INFO-DIR-ENTRY' and no `This file documents'.
> install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> dpkg: error processing gettext (--configure):
> subprocess post-installation script returned error exit status 1

[Santiago Vila Doncel (sanvila-unex)]

On Sun, 18 Jul 2004, LaMont Jones wrote:

> On Sun, Jul 18, 2004 at 04:32:53PM +0200, Santiago Vila wrote:
> > > > Setting up gettext (0.14.1-4) ...
> > >
> > > > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > > > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > > > dpkg: error processing gettext (--configure):
> > > > subprocess post-installation script returned error exit status 1
> > I can't reproduce this. Which architecture, please? The packages I see
> > for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.
>
> This is installing 0.14.1-4 on ia64. See, for example:
> http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

I see. The info file is wrong because the Tag Table at the very end is wrong.
This confuses install-info.

Will be fixed in 0.14.1-5. Sorry.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 16:32:53 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On Sun, 18 Jul 2004, LaMont Jones wrote:

> reopen 260048
> --
>
> Maybe it would be a good idea to have the gettext build fail if
> /usr/share/info/gettext.info is empty (--> gettext.info.gz is 33 bytes)
>
> lamont
>
> > Setting up gettext (0.14.1-4) ...
>
> > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > dpkg: error processing gettext (--configure):
> > subprocess post-installation script returned error exit status 1

I can't reproduce this. Which architecture, please? The packages I see
for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 08:48:41 -0600
From: LaMont Jones <email address hidden>
To: Santiago Vila <email address hidden>
Cc: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On Sun, Jul 18, 2004 at 04:32:53PM +0200, Santiago Vila wrote:
> > > Setting up gettext (0.14.1-4) ...
> >
> > > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > > dpkg: error processing gettext (--configure):
> > > subprocess post-installation script returned error exit status 1
> I can't reproduce this. Which architecture, please? The packages I see
> for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.

This is installing 0.14.1-4 on ia64. See, for example:
http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

lamont

[Santiago Vila Doncel (sanvila-unex)]

I said:
> The info file is wrong because the Tag Table at the very end is wrong.
> This confuses install-info.

But I don't see that install-info takes the Tag Table in account at all,
so there should be another reason for install-info to fail.

I'm puzzled.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 17:47:03 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On Sun, 18 Jul 2004, LaMont Jones wrote:

> On Sun, Jul 18, 2004 at 04:32:53PM +0200, Santiago Vila wrote:
> > > > Setting up gettext (0.14.1-4) ...
> > >
> > > > No `START-INFO-DIR-ENTRY' and no `This file documents'.
> > > > install-info(/usr/share/info/gettext.info): unable to determine description for `dir' entry - giving up
> > > > dpkg: error processing gettext (--configure):
> > > > subprocess post-installation script returned error exit status 1
> > I can't reproduce this. Which architecture, please? The packages I see
> > for 0.14.1-4 at incoming.debian.org right now (i386, hppa and ia64) are ok.
>
> This is installing 0.14.1-4 on ia64. See, for example:
> http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

I see. The info file is wrong because the Tag Table at the very end is wrong.
This confuses install-info.

Will be fixed in 0.14.1-5. Sorry.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 18 Jul 2004 18:21:28 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

I said:
> The info file is wrong because the Tag Table at the very end is wrong.
> This confuses install-info.

But I don't see that install-info takes the Tag Table in account at all,
so there should be another reason for install-info to fail.

I'm puzzled.

[Matt Zimmerman (mdz)]

Doesn't affect Warty; confirmed that the .texi is unmodified in our version

[Santiago Vila Doncel (sanvila-unex)]

On Sun, 18 Jul 2004, LaMont Jones wrote:

> This is installing 0.14.1-4 on ia64. See, for example:
> http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

This is very strange indeed, because I can install gettext_0.14.1-4_ia64.deb
even on a i386 system running sarge, using --force options:

# dpkg -i --force-depends --force-architecture gettext_0.14.1-4_ia64.deb
dpkg - warning, overriding problem because --force enabled:
 package architecture (ia64) does not match system (i386)
(Reading database ... 49274 files and directories currently installed.)
Preparing to replace gettext 0.14.1-4 (using gettext_0.14.1-4_ia64.deb) ...
Unpacking replacement gettext ...
dpkg: gettext: dependency problems, but configuring anyway as you request:
 gettext depends on libc6.1 (>= 2.3.2.ds1-4); however:
  Package libc6.1 is not installed.
Setting up gettext (0.14.1-4) ...

Anyway, I uploaded 0.14.1-5 shortly after this bug was reopened.
Is there a reason why the ia64 autobuilder is still using 0.14.1-4?

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 00:59:23 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On Sun, 18 Jul 2004, LaMont Jones wrote:

> This is installing 0.14.1-4 on ia64. See, for example:
> http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

This is very strange indeed, because I can install gettext_0.14.1-4_ia64.deb
even on a i386 system running sarge, using --force options:

# dpkg -i --force-depends --force-architecture gettext_0.14.1-4_ia64.deb
dpkg - warning, overriding problem because --force enabled:
 package architecture (ia64) does not match system (i386)
(Reading database ... 49274 files and directories currently installed.)
Preparing to replace gettext 0.14.1-4 (using gettext_0.14.1-4_ia64.deb) ...
Unpacking replacement gettext ...
dpkg: gettext: dependency problems, but configuring anyway as you request:
 gettext depends on libc6.1 (>= 2.3.2.ds1-4); however:
  Package libc6.1 is not installed.
Setting up gettext (0.14.1-4) ...

Anyway, I uploaded 0.14.1-5 shortly after this bug was reopened.
Is there a reason why the ia64 autobuilder is still using 0.14.1-4?

[Andreas Metzler (ametzler-downhill)]

On 2004-07-19 Santiago Vila <email address hidden> wrote:
> On Sun, 18 Jul 2004, LaMont Jones wrote:

> > This is installing 0.14.1-4 on ia64. See, for example:
> > http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

> This is very strange indeed, because I can install gettext_0.14.1-4_ia64.deb
> even on a i386 system running sarge, using --force options:
[...]
> Anyway, I uploaded 0.14.1-5 shortly after this bug was reopened.
> Is there a reason why the ia64 autobuilder is still using 0.14.1-4?

Hmm. ia64 still fails with -5, see e.g.
http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
LaMont, is it possible that the buildd chroot is busted?
              cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 08:56:35 +0200
From: Andreas Metzler <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On 2004-07-19 Santiago Vila <email address hidden> wrote:
> On Sun, 18 Jul 2004, LaMont Jones wrote:

> > This is installing 0.14.1-4 on ia64. See, for example:
> > http://buildd.debian.org/fetch.php?&pkg=patch&ver=2.5.9-2&arch=ia64&stamp=1090157473&file=log&as=raw

> This is very strange indeed, because I can install gettext_0.14.1-4_ia64.deb
> even on a i386 system running sarge, using --force options:
[...]
> Anyway, I uploaded 0.14.1-5 shortly after this bug was reopened.
> Is there a reason why the ia64 autobuilder is still using 0.14.1-4?

Hmm. ia64 still fails with -5, see e.g.
http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
LaMont, is it possible that the buildd chroot is busted?
              cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[LaMont Jones (lamont)]

On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> Hmm. ia64 still fails with -5, see e.g.
> http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> LaMont, is it possible that the buildd chroot is busted?

I rebuilt the chroot from scratch, still get the error.

lamont

[Santiago Vila Doncel (sanvila-unex)]

[ Please Cc: <email address hidden> as I'm not subscribed to this list ]

Lately, the ia64 autobuilder has a great difficulty trying to build
anything which build-depends on gettext. Every time gettext has to be
installed, install-info fails (see any of the recent build logs).

Is anybody here able to reproduce the problem on a ia64 system running
unstable, or is this only a problem in the autobuilder?

[ LaMont has reopened Bug #260048 because of this problem, but AFAIK
  the bug in gettext is already fixed ].

Thanks.

[Santiago Vila Doncel (sanvila-unex)]

tags 260048 + moreinfo
tags 260048 + help
thanks

On Mon, 19 Jul 2004, LaMont Jones wrote:

> On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> > Hmm. ia64 still fails with -5, see e.g.
> > http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> > LaMont, is it possible that the buildd chroot is busted?
>
> I rebuilt the chroot from scratch, still get the error.

Well, can you reproduce it on a ia64 system running unstable, or it
fails only in the chroot?

I have made a zdiff between the gettext.info.gz in the i386 package
and the same file in the ia64 package, and they are exactly the same.

Are you sure that the ia64 package which the autobuilder tries to
install is the same that may be found in the archive? If they are the
same, then this does not seem to be the 0-length info file problem anymore.

Can you still install version 0.14.1-2 from March or does it also fail?

I can install the ia64 package on a i386 system using --force-architecture
and --force-depends without errors in the postinst. Can you do the
opposite? Can you install the i386 package on a ia64 system using
both --force-architecture and --force-depends, or it also fails?

Please note that I don't have an ia64 system, so without a little bit
of debugging on your side it is going to be very difficult for me to
fix this bug, assuming it is a gettext bug at all.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 11:49:41 -0600
From: LaMont Jones <email address hidden>
To: Andreas Metzler <email address hidden>
Cc: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> Hmm. ia64 still fails with -5, see e.g.
> http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> LaMont, is it possible that the buildd chroot is busted?

I rebuilt the chroot from scratch, still get the error.

lamont

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 19:57:05 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Is the ia64 autobuilder working properly?

[ Please Cc: <email address hidden> as I'm not subscribed to this list ]

Lately, the ia64 autobuilder has a great difficulty trying to build
anything which build-depends on gettext. Every time gettext has to be
installed, install-info fails (see any of the recent build logs).

Is anybody here able to reproduce the problem on a ia64 system running
unstable, or is this only a problem in the autobuilder?

[ LaMont has reopened Bug #260048 because of this problem, but AFAIK
  the bug in gettext is already fixed ].

Thanks.

[Andreas Metzler (ametzler-downhill)]

On 2004-07-19 LaMont Jones <email address hidden> wrote:
> On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> > Hmm. ia64 still fails with -5, see e.g.
> > http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> > LaMont, is it possible that the buildd chroot is busted?

> I rebuilt the chroot from scratch, still get the error.

Strange, it seems to work now:

| http://buildd.debian.org/fetch.php?&pkg=exim4&ver=4.34-3&arch=ia64&stamp=1090258573&file=log&as=raw
| Selecting previously deselected package gettext.
| Unpacking gettext (from .../gettext_0.14.1-5_ia64.deb) ...
[...]
| Setting up gettext-base (0.14.1-5) ...

| Setting up gettext (0.14.1-5) ...

| Setting up intltool-debian (0.30+20040213) ...

gimp built successfully with gettext_0.14.1-5, too.
             cu andreas

--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 21:13:17 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Cc: Andreas Metzler <email address hidden>,
 <email address hidden>
Subject: Re: Bug#260048: still happening

tags 260048 + moreinfo
tags 260048 + help
thanks

On Mon, 19 Jul 2004, LaMont Jones wrote:

> On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> > Hmm. ia64 still fails with -5, see e.g.
> > http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> > LaMont, is it possible that the buildd chroot is busted?
>
> I rebuilt the chroot from scratch, still get the error.

Well, can you reproduce it on a ia64 system running unstable, or it
fails only in the chroot?

I have made a zdiff between the gettext.info.gz in the i386 package
and the same file in the ia64 package, and they are exactly the same.

Are you sure that the ia64 package which the autobuilder tries to
install is the same that may be found in the archive? If they are the
same, then this does not seem to be the 0-length info file problem anymore.

Can you still install version 0.14.1-2 from March or does it also fail?

I can install the ia64 package on a i386 system using --force-architecture
and --force-depends without errors in the postinst. Can you do the
opposite? Can you install the i386 package on a ia64 system using
both --force-architecture and --force-depends, or it also fails?

Please note that I don't have an ia64 system, so without a little bit
of debugging on your side it is going to be very difficult for me to
fix this bug, assuming it is a gettext bug at all.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 21:59:49 +0200
From: Andreas Metzler <email address hidden>
To: LaMont Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#260048: still happening

On 2004-07-19 LaMont Jones <email address hidden> wrote:
> On Mon, Jul 19, 2004 at 08:56:35AM +0200, Andreas Metzler wrote:
> > Hmm. ia64 still fails with -5, see e.g.
> > http://buildd.debian.org/fetch.php?&pkg=pciutils&ver=1%3A2.1.11-15&arch=ia64&stamp=1090219158&file=log&as=raw
> > LaMont, is it possible that the buildd chroot is busted?

> I rebuilt the chroot from scratch, still get the error.

Strange, it seems to work now:

| http://buildd.debian.org/fetch.php?&pkg=exim4&ver=4.34-3&arch=ia64&stamp=1090258573&file=log&as=raw
| Selecting previously deselected package gettext.
| Unpacking gettext (from .../gettext_0.14.1-5_ia64.deb) ...
[...]
| Setting up gettext-base (0.14.1-5) ...

| Setting up gettext (0.14.1-5) ...

| Setting up intltool-debian (0.30+20040213) ...

gimp built successfully with gettext_0.14.1-5, too.
             cu andreas

--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

[Santiago Vila Doncel (sanvila-unex)]

On Mon, 19 Jul 2004, Andreas Metzler wrote:

> Strange, it seems to work now:
>
> | http://buildd.debian.org/fetch.php?&pkg=exim4&ver=4.34-3&arch=ia64&stamp=1090258573&file=log&as=raw
> | Selecting previously deselected package gettext.
> | Unpacking gettext (from .../gettext_0.14.1-5_ia64.deb) ...
> [...]
> | Setting up gettext-base (0.14.1-5) ...
>
> | Setting up gettext (0.14.1-5) ...
>
> | Setting up intltool-debian (0.30+20040213) ...
>
> gimp built successfully with gettext_0.14.1-5, too.

Yes, I noticed builds started to work again. I suspect this is a
kernel/libc bug, or filesystem corruption in the build machine.

LaMont, may this bug be closed now?

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 23:34:00 +0200 (CEST)
From: Santiago Vila <email address hidden>
To: Andreas Metzler <email address hidden>,
 <email address hidden>
Cc: LaMont Jones <email address hidden>
Subject: Re: Bug#260048: still happening

On Mon, 19 Jul 2004, Andreas Metzler wrote:

> Strange, it seems to work now:
>
> | http://buildd.debian.org/fetch.php?&pkg=exim4&ver=4.34-3&arch=ia64&stamp=1090258573&file=log&as=raw
> | Selecting previously deselected package gettext.
> | Unpacking gettext (from .../gettext_0.14.1-5_ia64.deb) ...
> [...]
> | Setting up gettext-base (0.14.1-5) ...
>
> | Setting up gettext (0.14.1-5) ...
>
> | Setting up intltool-debian (0.30+20040213) ...
>
> gimp built successfully with gettext_0.14.1-5, too.

Yes, I noticed builds started to work again. I suspect this is a
kernel/libc bug, or filesystem corruption in the build machine.

LaMont, may this bug be closed now?

[LaMont Jones (lamont)]

On Mon, Jul 19, 2004 at 11:34:00PM +0200, Santiago Vila wrote:
> > gimp built successfully with gettext_0.14.1-5, too.
> Yes, I noticed builds started to work again. I suspect this is a
> kernel/libc bug, or filesystem corruption in the build machine.
> LaMont, may this bug be closed now?

It would appear to have been bitrot in the chroot. closed.

lamont

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 19 Jul 2004 21:01:55 -0600
From: LaMont Jones <email address hidden>
To: Santiago Vila <email address hidden>
Cc: Andreas Metzler <email address hidden>,
 <email address hidden>, LaMont Jones <email address hidden>
Subject: Re: Bug#260048: still happening

On Mon, Jul 19, 2004 at 11:34:00PM +0200, Santiago Vila wrote:
> > gimp built successfully with gettext_0.14.1-5, too.
> Yes, I noticed builds started to work again. I suspect this is a
> kernel/libc bug, or filesystem corruption in the build machine.
> LaMont, may this bug be closed now?

It would appear to have been bitrot in the chroot. closed.

lamont