libcaca: FTBFS: "cannot find X11 development files"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libcaca (Debian) |
Fix Released
|
Unknown
|
|||
libcaca (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #266070 http://
Debian Bug Importer (debzilla) wrote : | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Message-Id: <email address hidden>
Date: Mon, 16 Aug 2004 17:33:48 +0200
From: Roland Stigge <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: libcaca: FTBFS: "cannot find X11 development files"
Package: libcaca
Severity: serious
Hi,
trying to build the package in a clean environment (pbuilder chroot), I got:
=======
[...]
checking for endian.h... yes
checking for unistd.h... (cached) yes
checking for signal... yes
checking for ioctl... yes
checking for vsnprintf... yes
checking for getenv... yes
checking for putenv... yes
checking for strcasecmp... yes
checking for usleep... yes
checking for gettimeofday... yes
checking for Sleep... no
checking for sin in -lm... yes
checking conio.h usability... no
checking conio.h presence... no
checking for conio.h... no
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking slang.h usability... yes
checking slang.h presence... yes
checking for slang.h... yes
checking for SLkp_init in -lslang... yes
checking slang/slang.h usability... no
checking slang/slang.h presence... no
checking for slang/slang.h... no
checking for X... no
checking for XOpenDisplay in -lX11... no
checking X11/XKBlib.h usability... yes
checking X11/XKBlib.h presence... yes
checking for X11/XKBlib.h... yes
configure: error: cannot find X11 development files
make: *** [configure-stamp] Error 1
=======
Thanks for considering.
bye,
Roland
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=
In Debian Bug tracker #266070, Sam Hocevar (sam-h) wrote : Bug#266070: fixed in libcaca 0.9-4 | #3 |
Source: libcaca
Source-Version: 0.9-4
We believe that the bug you reported is fixed in the latest version of
libcaca, which is due to be installed in the Debian FTP archive:
caca-utils_
to pool/main/
libcaca-
to pool/main/
libcaca_
to pool/main/
libcaca_0.9-4.dsc
to pool/main/
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.
Sam Hocevar (Debian packages) <email address hidden> (supplier of updated libcaca 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: Tue, 17 Aug 2004 13:29:58 +0200
Source: libcaca
Binary: caca-utils libcaca-dev
Architecture: source i386
Version: 0.9-4
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) <email address hidden>
Changed-By: Sam Hocevar (Debian packages) <email address hidden>
Description:
caca-utils - text mode graphics utilities
libcaca-dev - development files for libcaca
Closes: 266070
Changes:
libcaca (0.9-4) unstable; urgency=low
.
* debian/control:
+ Build-depend on libxt-dev because autoconf's AC_PATH_X needs it to find
the X headers (Closes: #266070).
+ Set policy to 3.6.1.1.
Files:
abc02bed9d90bb
7db2ca9724beaa
03ca59ae0f0541
462a70ddffc265
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBIe1WfPP
QdyMfxgchUIhUPh
=8gAB
-----END PGP SIGNATURE-----
Fabio Massimo Di Nitto (fabbione) wrote : | #4 |
works fine in warty
Debian Bug Importer (debzilla) wrote : | #5 |
Message-Id: <email address hidden>
Date: Tue, 17 Aug 2004 07:49:47 -0400
From: Sam Hocevar (Debian packages) <email address hidden>
To: <email address hidden>
Subject: Bug#266070: fixed in libcaca 0.9-4
Source: libcaca
Source-Version: 0.9-4
We believe that the bug you reported is fixed in the latest version of
libcaca, which is due to be installed in the Debian FTP archive:
caca-utils_
to pool/main/
libcaca-
to pool/main/
libcaca_
to pool/main/
libcaca_0.9-4.dsc
to pool/main/
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.
Sam Hocevar (Debian packages) <email address hidden> (supplier of updated libcaca 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: Tue, 17 Aug 2004 13:29:58 +0200
Source: libcaca
Binary: caca-utils libcaca-dev
Architecture: source i386
Version: 0.9-4
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) <email address hidden>
Changed-By: Sam Hocevar (Debian packages) <email address hidden>
Description:
caca-utils - text mode graphics utilities
libcaca-dev - development files for libcaca
Closes: 266070
Changes:
libcaca (0.9-4) unstable; urgency=low
.
* debian/control:
+ Build-depend on libxt-dev because autoconf's AC_PATH_X needs it to find
the X headers (Closes: #266070).
+ Set policy to 3.6.1.1.
Files:
abc02bed9d90bb
7db2ca9724beaa
03ca59ae0f0541
462a70ddffc265
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBIe1WfPP
QdyMfxgchUIhUPh
=8gAB
-----END PGP SIGNATURE-----
In Debian Bug tracker #266070, Roland Stigge (stigge) wrote : libcaca: FTBFS | #6 |
reopen 266070
severity 266070 important
thanks
Hi,
now, it exits at:
=======
[...]
rm -f latex/libcaca.tex latex/libcaca.ps
mv latex/refman.tex latex/libcaca.tex
sed 's/setlength{
cd latex && /usr/bin/make ps
make[4]: Entering directory `/tmp/buildd/
echo "Running latex..."
Running latex...
latex refman.tex
This is e-TeX, Version 3.14159-2.1 (Web2C 7.4.5)
entering extended mode
(./refman.tex
LaTeX2e <2001/06/01>
Babel <v3.7h> and hyphenation patterns for american, polish, loaded.
(/usr/share/
Document Class: book 2001/04/21 v1.4e Standard LaTeX document class
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
mkdir: cannot create directory `/var/cache/
d
kpsestat: /var/cache/
chmod: too few arguments
Try `chmod --help' for more information.
mkdir: cannot create directory `/var/cache/
or directory
kpsestat: /var/cache/
chmod: too few arguments
Try `chmod --help' for more information.
mktextfm: mktexdir /var/cache/
kpathsea: Appending font creation commands to missfont.log.
! Font T1/cmr/
nd.
<to be read again>
l.95 \fontencoding\
?
! Emergency stop.
<to be read again>
l.95 \fontencoding\
No pages of output.
Transcript written on refman.log.
make[4]: *** [refman.dvi] Error 1
make[4]: Leaving directory `/tmp/buildd/
make[3]: *** [stamp-latex] Error 2
make[3]: Leaving directory `/tmp/buildd/
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/
make: *** [build-stamp] Error 2
=======
I d...
In Debian Bug tracker #266070, Sam Hocevar (sam-h) wrote : Re: Bug#266070: libcaca: FTBFS | #7 |
On Wed, Aug 25, 2004, Roland Stigge wrote:
> reopen 266070
> severity 266070 important
It's a very different bug. I think you should have opened a new one
instead.
> [...]
> (/usr/share/
> (/usr/share/
> mkdir: cannot create directory `/var/cache/
> kpsestat: /var/cache/
This looks like a problem with tetex, doesn't it? Are your tetex
packages up to date?
--
Sam.
Debian Bug Importer (debzilla) wrote : | #8 |
Message-Id: <email address hidden>
Date: Wed, 25 Aug 2004 13:48:49 +0200
From: Roland Stigge <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: libcaca: FTBFS
reopen 266070
severity 266070 important
thanks
Hi,
now, it exits at:
=======
[...]
rm -f latex/libcaca.tex latex/libcaca.ps
mv latex/refman.tex latex/libcaca.tex
sed 's/setlength{
cd latex && /usr/bin/make ps
make[4]: Entering directory `/tmp/buildd/
echo "Running latex..."
Running latex...
latex refman.tex
This is e-TeX, Version 3.14159-2.1 (Web2C 7.4.5)
entering extended mode
(./refman.tex
LaTeX2e <2001/06/01>
Babel <v3.7h> and hyphenation patterns for american, polish, loaded.
(/usr/share/
Document Class: book 2001/04/21 v1.4e Standard LaTeX document class
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
(/usr/share/
mkdir: cannot create directory `/var/cache/
d
kpsestat: /var/cache/
chmod: too few arguments
Try `chmod --help' for more information.
mkdir: cannot create directory `/var/cache/
or directory
kpsestat: /var/cache/
chmod: too few arguments
Try `chmod --help' for more information.
mktextfm: mktexdir /var/cache/
kpathsea: Appending font creation commands to missfont.log.
! Font T1/cmr/
nd.
<to be read again>
l.95 \fontencoding\
?
! Emergency stop.
<to be read again>
l.95 \fontencoding\
No pages of output.
Transcript written on refman.log.
make[4]: *** [refman.dvi] Error 1
make[4]: Leaving directory `/tmp/buildd/
make[3]: *** [stamp-latex] Error 2
make[3]: Leaving directory `/tmp/buildd/
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/t...
In Debian Bug tracker #266070, Roland Stigge (stigge) wrote : | #9 |
On Wed, 2004-08-25 at 15:20, Sam Hocevar wrote:
> It's a very different bug. I think you should have opened a new one
> instead.
>
> > [...]
> > (/usr/share/
> > (/usr/share/
> > mkdir: cannot create directory `/var/cache/
> > kpsestat: /var/cache/
>
> This looks like a problem with tetex, doesn't it? Are your tetex
> packages up to date?
I'm using a daily-current pbuilder chroot with a daily-current debian
mirror. Can't you reproduce it (w/ pbuilder)?
Debian Bug Importer (debzilla) wrote : | #10 |
Message-ID: <email address hidden>
Date: Wed, 25 Aug 2004 15:20:52 +0200
From: Sam Hocevar <email address hidden>
To: Roland Stigge <email address hidden>, <email address hidden>
Subject: Re: Bug#266070: libcaca: FTBFS
On Wed, Aug 25, 2004, Roland Stigge wrote:
> reopen 266070
> severity 266070 important
It's a very different bug. I think you should have opened a new one
instead.
> [...]
> (/usr/share/
> (/usr/share/
> mkdir: cannot create directory `/var/cache/
> kpsestat: /var/cache/
This looks like a problem with tetex, doesn't it? Are your tetex
packages up to date?
--
Sam.
Debian Bug Importer (debzilla) wrote : | #11 |
Message-Id: <email address hidden>
Date: Wed, 25 Aug 2004 16:21:38 +0200
From: Roland Stigge <email address hidden>
To: Sam Hocevar <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#266070: libcaca: FTBFS
On Wed, 2004-08-25 at 15:20, Sam Hocevar wrote:
> It's a very different bug. I think you should have opened a new one
> instead.
>
> > [...]
> > (/usr/share/
> > (/usr/share/
> > mkdir: cannot create directory `/var/cache/
> > kpsestat: /var/cache/
>
> This looks like a problem with tetex, doesn't it? Are your tetex
> packages up to date?
I'm using a daily-current pbuilder chroot with a daily-current debian
mirror. Can't you reproduce it (w/ pbuilder)?
In Debian Bug tracker #266070, Bastian Blank (waldi) wrote : cloning 266070, tagging 266070, severity of 266070 is serious | #12 |
# Automatically generated email from bts, devscripts version 2.8.1
clone 266070 -1
tags 266070 sarge
severity 266070 serious
Debian Bug Importer (debzilla) wrote : | #13 |
Message-Id: <email address hidden>
Date: Sat, 28 Aug 2004 16:20:13 +0200
From: Bastian Blank <email address hidden>
To: <email address hidden>
Subject: cloning 266070, tagging 266070, severity of 266070 is serious
# Automatically generated email from bts, devscripts version 2.8.1
clone 266070 -1
tags 266070 sarge
severity 266070 serious
In Debian Bug tracker #266070, Frank Küster (frank-kuesterei) wrote : | #14 |
Hi Folks,
<email address hidden> wrote:
> On Wed, Aug 25, 2004, Roland Stigge wrote:
> > reopen 266070
> > severity 266070 important
>
> It's a very different bug. I think you should have opened a new one
> instead.
>
> > [...]
> > (/usr/share/
> > (/usr/share/
> > mkdir: cannot create directory `/var/cache/
> > kpsestat: /var/cache/
>
> This looks like a problem with tetex, doesn't it? Are your tetex
> packages up to date?
I'm kind of confused by the way you handled this bug. Why the cloning?
Did you mean to assign the clone to tetex, Bastian? Why does it need a
VAC message on debian-private to hear from this bug? I would really
appreciate if everybody could notify the maintainers of suspect packages
if important bugs arise.
As for the bug itself: Actually this looks like
,----
| * Fix permissions of the font cache directories, causing FTBFS of zope
| (and possibly others) (Closes: #267413, #267752), thanks to Pierre
| Machard <email address hidden> [frank]
`----
a bug in tetex-base, introduced in tetex-base 2.0.2b-1 and fixed in
2.0.2b-3. Bastian, why did you add the sarge tag? Do you have any
indication that this is also in 2.0.2-9?
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Debian Bug Importer (debzilla) wrote : | #15 |
Message-ID: <email address hidden>
Date: Mon, 30 Aug 2004 12:32:12 +0200
From: <email address hidden> (=?iso-
To: <email address hidden>
Cc: <email address hidden>, Bastian Blank <email address hidden>, Roland Stigge <email address hidden>,
debian-tetex-maint <email address hidden>
Subject: libcaca: FTBFS: "cannot find X11 development files"
Hi Folks,
<email address hidden> wrote:
> On Wed, Aug 25, 2004, Roland Stigge wrote:
> > reopen 266070
> > severity 266070 important
>=20
> It's a very different bug. I think you should have opened a new one
> instead.
>=20
> > [...]
> > (/usr/share/
> > (/usr/share/
crm1000
> > mkdir: cannot create directory `/var/cache/
ion denied
> > kpsestat: /var/cache/
>=20
> This looks like a problem with tetex, doesn't it? Are your tetex
> packages up to date?
I'm kind of confused by the way you handled this bug. Why the cloning?
Did you mean to assign the clone to tetex, Bastian? Why does it need a
VAC message on debian-private to hear from this bug? I would really
appreciate if everybody could notify the maintainers of suspect packages
if important bugs arise.
As for the bug itself: Actually this looks like=20
,----
| * Fix permissions of the font cache directories, causing FTBFS of zope
| (and possibly others) (Closes: #267413, #267752), thanks to Pierre
| Machard <email address hidden> [frank]
`----
a bug in tetex-base, introduced in tetex-base 2.0.2b-1 and fixed in
2.0.2b-3. Bastian, why did you add the sarge tag? Do you have any
indication that this is also in 2.0.2-9?
Regards, Frank
--=20
Frank K=FCster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
In Debian Bug tracker #266070, Steve Langasek (vorlon) wrote : | #16 |
My understanding of this log is that this bug is closed, now both in sid
and in sarge.
I'm assuming that Bastian's cloning was intended to document the other
build problem that was later reported, but his clone message contained
no details and that bug doesn't seem to be a bug in libcaca at all.
Thanks,
--
Steve Langasek
postmodern programmer
Debian Bug Importer (debzilla) wrote : | #17 |
Message-ID: <email address hidden>
Date: Wed, 15 Sep 2004 01:43:49 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: libcaca: FTBFS: "cannot find X11 development files"
--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-
Content-
My understanding of this log is that this bug is closed, now both in sid
and in sarge.
I'm assuming that Bastian's cloning was intended to document the other
build problem that was later reported, but his clone message contained
no details and that bug doesn't seem to be a bug in libcaca at all.
Thanks,
--=20
Steve Langasek
postmodern programmer
--n8g4imXOkfNTN/H1
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBSAC+
FJPt9cqu4SQ/
=figl
-----END PGP SIGNATURE-----
--n8g4imXOkfNTN
Changed in libcaca: | |
status: | Unknown → Fix Released |
Automatically imported from Debian bug report #266070 http:// bugs.debian. org/266070