Bug#385486: ftp.debian.org: Need to remove obsolete mcvs packages from the pool
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 build from source on those four architectures. After talking to the clisp maintainer it became obvious that while there is a certain interest in trying to get those 4 architectures up to sync with the others again, feature-wise, there is no definite date for that nor is there much of a priority to do so. In the mean time, this prevents newer mcvs versions from progressing to testing because the old architectures still have package files. In light of the fact that those are lesser-used architectures (based on popcon) and that I am unable to get any changes to mcvs in to debian/testing, I would like to request the removal from the package pool of: mcvs_1.0.13-8_ia64.deb mcvs_1.0.13-8_mipsel.deb mcvs_1.0.13-8_s390.deb mcvs_1.0.13-8_sparc.deb For one thing, this will allow the amd64 package from getting into testing. Thank you very much, - robin -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.7-robin Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365230: mcvs - FTBFS: There is no package with name FFI
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 +0200, Bastian Blank wrote: Package: mcvs Version: 1.0.13-14 Severity: serious There was an error while trying to autobuild your package: Automatic build of mcvs_1.0.13-14 on debian-31 by sbuild/s390 85 [...] ;; Compiling file /build/buildd/mcvs-1.0.13/code/unix-bindings/unix.lisp ... *** - SYSTEM::%FIND-PACKAGE: There is no package with name FFI 0 errors, 0 warnings Bye. make[1]: *** [unix.c] Error 1 make[1]: Leaving directory `/build/buildd/mcvs-1.0.13/code/unix-bindings' linking set failed to build. make: *** [common-install-arch] Error 1 ** Build finished at 20060428-1208 FAILED [dpkg-buildpackage died] Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346164: Reopen, reassign to clisp
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346164: This keeps coming up
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 autobuilders not install them when asked to build mcvs? I could keep adding the required build dependencies to my package but I would very much like to know why they are necessary in the first place. The gcc-3.3 dependency is not declared by mcvs explicitly, so I suspect that perhaps clisp pulls it in without declaring a proper Depends: gcc-3.3 [sparc] line. Any ideas? - Robin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341850: More info
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 ,$(DEB_BUILD_ARCH))) +ifneq (,$(filter alpha hppa ia64 m68k sparc ,$(DEB_BUILD_ARCH))) export CC = gcc -D SAFETY=3 -D NO_MULTIMAP_SHM -D NO_MULTIMAP_FILE -D NO_SINGLEMAP -D NO_TRIVIALMAP endif -ifneq (,$(filter m68k sparc ,$(DEB_BUILD_ARCH))) - export CC = gcc-3.3 -D SAFETY=3 -D NO_MULTIMAP_SHM -D NO_MULTIMAP_FILE -D NO_SINGLEMAP -D NO_TRIVIALMAP -endif - ifneq (,$(filter arm hppa,$(DEB_BUILD_ARCH))) # Disable FFI on ARM, HPPA, MIPSel FFI=--without-dynamic-ffi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340646: More info
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 least) IA64 and SPARC. Buildd logs are available at: http://buildd.debian.org/fetch.php?pkg=mcvsver=1.0.13-11arch=ia64stamp=1133382079file=logas=raw http://buildd.debian.org/fetch.php?pkg=mcvsver=1.0.13-11arch=sparcstamp=118365file=logas=raw From the installation logs, it becomes clear that clisp-dev does not depend on clisp, whereas I do believe that it should though. Thanks, - robin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340304: bugs
reassign 340304 clisp tag 340304 fixed close 340304 merge 340304 340250 stop This bug was never in mcvs; the corresponding bug (in clisp) has now been fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340304: (no subject)
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 PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
