Re: conflict with ioctl.h and ioccom.h?
Hi.
While going through some of the packages in NOTES [1] I noticed that the
darkice package is FTBFS again after being claimed fixed. It used to be FTBFS
because of bad build-deps but now it is something different:
from the build log [2]:
It looks like we are currently doing the same thing :-(
Look at r1727 on
http://svn.debian.org/wsvn/glibc-bsd/?op=log&rev=0&sc=0&isdir=1
My working copy of "claimed fixed" is currently:
allegro4.1_4.1.15-6+kbsd BTS
darkice_0.16-1+kbsd kfreebsd-kernel-headers
dictd_1.10.2-3+cfg fixed, should not be in unreleased
gamin_0.1.7-3+kbsd BTS
glew_1.3.4-3+kbsd BTS
gnome-applets_2.10.1-5+kbsd
gst-plugins-base0.10_0.10.10-1+kbsd fixed with new cdparanoia
gtk-engines_0.12-8.1+libtool
kaquarium_1.0-beta-5+libtool+b1 BTS
kde-style-lipstik_2.2.1-1+libtool
kdeedu_3.5.1-1+kbsd
libapache-mod-encoding_0.0.20021209-6.1+libtool BTS
libgtkhtml2_2.6.3-1+libtool+b1 fixed
libibtk_0.0.14-10+libtool BTS
ocamlgsl_0.3.5-3+kbsd
pyopengl_2.0.1.09-1.1+kbsd
realtimebattle_1.0.6-2+cfg ?
showimg_0.9.4.1-3+libtool+b1 ? build-dep koffice-dev
sidplay_2.0.9-2+kbsd+b1 BTS, pending
solfege_3.0.2-1+kbsd fixed
tktable_2.9-1+kbsd fixed in tktable2.9, tktable scheduled for removal
totem_1.4.5-1+kbsd BTS, pending
xdb_1.2.0-7.libtool.1 BTS
BTS = an updated fix is again in BTS
fixed = it is really fixed, needs "just" rebuild
Petr
Reply to: