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

Bug#540481: unison has ocaml-base as dependency which has x11 as dependency...thats not necessarry



Package: unison
Version: 2.27.57-1+b1
Severity: normal



-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.30-1-kirkwood
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages unison depends on:
ii  libc6                     2.7-18         GNU C Library: Shared libraries
ii  libgcc1                   1:4.3.2-1.1    GCC support library
ii  libncurses5               5.7+20081213-1 shared libraries for terminal hand
ii  ocaml-base [ocaml-base-3. 3.10.2-3       Runtime system for OCaml bytecode 

Versions of packages unison recommends:
ii  openssh-client [ssh-client]   1:5.1p1-5  secure shell client, an rlogin/rsh

unison suggests no packages.

-- no debconf information
unison has ocaml-base as dependency which has x11 as dependency...thats 
not necessarry
 
 I am using Debian GNU/Linux ARM-Architecture
 
here is a mail from the package-maintainer:
 
 
Hello,
 
On Sat, Aug 08, 2009 at 10:46:48AM +0200, Stefan Lachinger wrote:
hello!
i hope i dont embarass u with this question!
 
No at all.
 
i just installed debian on my plug computer (arm-prozessor). when i
try to install unison aptitude always wants to install x11 as
dependency (its a dependency of ocaml-base). is it really needed to
have ocaml-base as dependency for unison?
 
 
Excellent question, and answer is: this is a bug
 
Please fill a bug report against unison package, with a copy of this
mail.
 
If you are using stable, I recommend you to rebuild unison replacing
 
DEB_DH_GENCONTROL_ARGS += -VF:OCamlInterpreter="ocaml-base-$(OCAML_ABI)"
by
DEB_DH_GENCONTROL_ARGS += 
-VF:OCamlInterpreter="ocaml-base-nox-$(OCAML_ABI)"
 
in debian/rules
 
Regards
Sylvain Le Gall
 
ps: if you are using unstable, you will get updated package in the near
future.



Reply to: