[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: elaboration on "hard to nmu packages"; xlibs-dev transition



On Sun, Jan 15, 2006 at 11:24:56AM -0500, Justin Pryzby wrote:

> I also note the following packages are "hard" to NMU, because of some
> problem like another FTBFS or the package being native when it should
> not be.  I'm untagging these 'patch' now.
Let me elaborate on these

> arla-0.36.2
The following packages have unmet dependencies:
  kerberos4kth-dev

> ayttm-0.4.6+26
Files in second .deb but not in first
-------------------------------------
/usr/lib/ayttm/img2jpc.a
/usr/lib/ayttm/img2jpc.la
/usr/lib/ayttm/img2jpc.so

> bzflag-2.0.4.20051017.1
native

> gpsim-0.20.14
gui_regwin.c:1795: error: 'GTK_SHEET_CLIP_TEXT' undeclared (first use
in this fu

> grabc-1.1
X11/Xos.h not found; needs include path update

> jwm-0.23
group.c:252:41: error: macro "LoadNamedIcon" passed 2 arguments, but takes just 1
maintainer decision to rerun autoconf or build-dep: libxt-dev

> rsjog-1.1
Files in second .deb but not in first
-------------------------------------
/usr/lib/ruby/1.6/i386-linux/XTest.so

Files in first .deb but not in second
-------------------------------------
/usr/lib/ruby/1.6/i486-linux/XTest.so

> wininfo-0.7
Fails to find -lXRes even when I build-dep on libxres-dev

> wmblob-1.0.3
maintainer decision to rerun autoconf or build-dep: libxt-dev
Fails to find libXpm even when build-dep on libxpm-dev

> wmmaiload-1.0.2
Fails to find libXext even when build-dep on libxext-dev; needs -L
path update?

> wmressel-0.8
Fails to find libXxf86vm even when build-dep on libxext-dev; needs -L
path update?

> xpad-2.10
xpad-session-manager.o: In function `xpad_session_manager_stop_interact':/tmp/buildd/xpad-2.10/src/xpad-session-manager.c:168: undefined reference to
`SmcInteractDone'

> xscorch-0.2.0
maintainer decision to rerun autoconf or build-dep: libxt-dev, libxpm-dev

If someone knows that these ar expected or how to work around them, be
my guest to NMU or fill me in.  Otherwise some of these maybe should
be cloned bugs; I don't know.

-- 
Clear skies,
Justin



Reply to: