Package: ftp.debian.org
Severity: serious
Justification: no longer builds from source
Hi,
The mcvs package used to build on ia64, mipsel, s390, and sparc in the past
because clisp at that time still contained the FFI module. This is no longer
the case, however, and as a result mcvs fails to
I am going to close this bug because it is already reported
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=230947) and not pertaining
to the mcvs package. If anything, file it against clisp if you think a
second bug for this is warranted.
Thanks,
- robin
On Fri, Apr 28, 2006 at 06:17:28PM
reopen 346164
reassign 346164 clisp
stop
The clisp package still tries to use gcc-3.3 for certain platforms but does
not depend on that compiler for the platforms in question. Either it should
just try and use the system gcc or a proper dependency on gcc-3.3 should be
added.
Thanks,
- robin
--
This issue keeps coming up, and every time it gets resolved by re-adding the
build dependencies to mcvs that should have been declared by clisp-dev. The
weird thing is that looking at clisp-dev's dependencies, the libraries you
mention are indeed already specified by clisp-dev.
So why do the
tags 356163 pending
stop
This bug is waiting for #362276 to be fixed so that KDE-based packages can
compile again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The following patch might fix this:
--- clisp-2.35/debian/rules.orig2005-12-04 14:03:32.0 -0500
+++ clisp-2.35/debian/rules 2005-12-04 14:04:14.0 -0500
@@ -13,14 +13,10 @@
tmp:=`pwd`/debian/tmp
XLIBS_PRE_DEPENDS=
-ifneq (,$(filter alpha hppa ia64
MCVS usually happens to be the canary in the coal mine for any packaging
errors in clisp since it is one of the few packages in Debian that uses
it; in this case it fails to build from source due to an error in the
latest clisp packages. It appears thet clisp-dev does not depend on clisp
for (at
Ehm... why doesn't clisp declare a dependency on common-lisp-controller anymore?
On Wed, Nov 23, 2005 at 05:33:22AM +0100, Peter Van Eynde wrote:
On Wednesday 23 November 2005 02:07, Robin wrote:
What package is /usr/sbin/register-common-lisp-implementation supposed to
be in? It's not in
The reason for this dependency is the versioned part of it.
KVIrc is present in Debian both as kvirc2 (version 2) and kvirc (version 3).
The dependency for kvirc-data is versioned so that on upgrades, users don't get
stuck using kvirc 3 with kvirc-data from kvirc 2.
If this is in any way
This is a duplicate of bug #340250 for clisp:
clisp: Package contains invalid link for base/lispinit.mem
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340250]
Until that is fixed, I cannot do anything about it from this side.
Thanks,
- robin
--
To UNSUBSCRIBE, email to [EMAIL
Package: clisp
Version: 2.35-8
Severity: important
The clisp package contains an invalid symbolic link:
/usr/lib/clisp/base/lispinit.mem -- ../full/lispinit.mem
The file /usr/lib/clisp/full/lispinit-orig.mem DOES exist, but consequently
clisp fails to start up, giving the user the following
Package: kvim
Version: 1:6.3-061+1
Severity: normal
The kvim package lists the wrong executable in /usr/lib/mime/packages/kvim.
I suspect it's a simple matter of eyes seeing A, fingers typing B. Here's
a quick patch to fix it:
1,2c1,2
text/plain; kview %s; edit=kvim -f %s; compose=kvim -f %s;
12 matches
Mail list logo
