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

Bug#169038: marked as done (cryptoapi-core-source: Please adapt package to work with 2.2 kernels)

Your message dated Thu, 22 Apr 2004 18:27:05 +0200
with message-id <20040422162705.GA3497@djpig.de>
and subject line Packages were removed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 14 Nov 2002 04:51:51 +0000
>From az@bond.edu.au Wed Nov 13 22:51:50 2002
Return-path: <az@bond.edu.au>
Received: from cluon.it.bond.edu.au [] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18CByj-0001iB-00; Wed, 13 Nov 2002 22:51:45 -0600
Received: from cluon.it.bond.edu.au (localhost [])
	by cluon.it.bond.edu.au (8.12.6/8.12.6/Debian-3) with ESMTP id gAE4pChZ015677;
	Thu, 14 Nov 2002 14:51:12 +1000
Received: (from az@localhost)
	by cluon.it.bond.edu.au (8.12.6/8.12.6/Debian-3) id gAE4pC2k015675;
	Thu, 14 Nov 2002 14:51:12 +1000
Message-Id: <200211140451.gAE4pC2k015675@cluon.it.bond.edu.au>
From: Alexander Zangerl <az@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: cryptoapi-core: module package cannot be built with 2.2.x kernels
X-Mailer: reportbug 1.50
Date: Thu, 14 Nov 2002 14:51:11 +1000
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=0.8 required=5.0

Package: cryptoapi-core-source
Version: 0.0+0.1.0-rc3-1
Severity: grave

there's a problem with the interaction of the makefiles of 
cryptoapi-core-source and the kernel:

i'm trying to build the cryptoapi-core package with a bog-standard kernel
version 2.2.22. 

what happens:
i run "make-kpkg --revision=custom.1.0 kernel_image modules_image"
and that's what i get: 

make[1]: Entering directory `/usr/src/modules/cryptoapi-core'
if [ -f debian/control.template ]; then \
        cp -a debian/control.template debian/control; \
touch configure-stamp
make -C /usr/src/linux modules SUBDIRS=`pwd`/crypto DEBIAN_COMPILE=1
make[2]: Entering directory `/usr/src/linux-2.2.22'
make -C  /usr/src/modules/cryptoapi-core/crypto CFLAGS="-Wall -Wstrict-prototype
s -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486
 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -DMODULE" MAKING_
MODULES=1 modules
make[3]: Entering directory `/usr/src/modules/cryptoapi-core/crypto'
make[3]: Nothing to be done for `modules'.
make[3]: Leaving directory `/usr/src/modules/cryptoapi-core/crypto'
make[2]: Leaving directory `/usr/src/linux-2.2.22'
dh_clean -k
sed 's/#KVERS#/2.2.22/g' debian/control.template > debian/control
sed 's/#KVERS#/2.2.22/g' debian/dirs.template > debian/dirs
install -d debian/tmp/lib/modules/2.2.22/kernel/crypto
install crypto/cryptoapi.o debian/tmp/lib/modules/2.2.22/kernel/crypto
install: cannot stat `crypto/cryptoapi.o': No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/src/modules/cryptoapi-core'
Module /usr/src/modules/cryptoapi-core failed.
Hit return to Continue

the problem is indicated by the line "Nothing to be done for `modules".

digging through all the makefiles in question results in:
Makefile.wrapped uses all kinds of variables which are not supported by
the Rules.make provided with 2.2.x kernels.

i have not yet found the proper mapping between Rules.make from 2.2.x 
and 2.4.x, therefore i can't supply a patch right now.

note: the same problem prevents cryptoloop from building.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux cluon 2.2.20 #1 Wed Jul 10 15:33:20 EST 2002 i686
Locale: LANG=C, LC_CTYPE=de_AT

Versions of packages cryptoapi-core-source depends on:
ii  build-essential               6          Informational list of build-essent

Received: (at 169038-done) by bugs.debian.org; 22 Apr 2004 16:27:12 +0000
>From frank@lichtenheld.de Thu Apr 22 09:27:12 2004
Return-path: <frank@lichtenheld.de>
Received: from mail.sorgfalt.net [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BGh2e-0002Mf-00; Thu, 22 Apr 2004 09:27:12 -0700
Received: from p50839807.dip.t-dialin.net ([] helo=djpig.djpig.de)
	by mail.sorgfalt.net with asmtp 
	(Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.35 (Sorgfalt))
	id 1BGh2d-0003sH-00; Thu, 22 Apr 2004 18:27:11 +0200
Received: from djpig by djpig.djpig.de with local (Exim 3.35 #1 (Debian))
	id 1BGh2X-0002cY-00; Thu, 22 Apr 2004 18:27:05 +0200
Date: Thu, 22 Apr 2004 18:27:05 +0200
From: Frank Lichtenheld <djpig@debian.org>
To: 212145-done@bugs.debian.org, 200562-done@bugs.debian.org,
	208873-done@bugs.debian.org, 208882-done@bugs.debian.org,
	209075-done@bugs.debian.org, 210268-done@bugs.debian.org,
	215435-done@bugs.debian.org, 169044-done@bugs.debian.org,
	203538-done@bugs.debian.org, 200561-done@bugs.debian.org,
	210267-done@bugs.debian.org, 211930-done@bugs.debian.org,
Subject: Packages were removed
Message-ID: <20040422162705.GA3497@djpig.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Sender: Frank Lichtenheld <frank@lichtenheld.de>
Delivered-To: 169038-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00 autolearn=no 
X-CrossAssassin-Score: 1

The cryptoapi-core-source and cryptoloop-source packages were
removed from Debian unstable yesterday so I close their remaining bugs.

[Date: Wed, 21 Apr 2004 18:37:55 -0400] [ftpmaster: James Troup]
Removed the following packages from unstable:

cryptoapi-core-source |    0.1.0-5 | source, all
cryptoloop-source | 0.0.0+0.0.1-pre1-10 | source, all
Closed bugs: 242245

------------------- Reason -------------------
ROM; unmaintained, don't apply to modern kernel.

Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/

Reply to: