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

Re: dh_clean -k -i



> No, Architecture: any means that the package is architecture-dependent.
> You should use Architecture: all.

Well, I changed it to all and now get the following:

   dh_clean -k -s 
   dh_clean: I have no package to build

I am attaching my debian/control and debian/rules, in case they might
help in figuring out what I have done wrong. Almost everything is
untouched from the results of dh_make. Any feedback would be
appreciated.

Charles

-- 
Prickly pears
Are picked
For pickles
No peach picks
A face that prickles
Burma-Shave
http://burma-shave.org/jingles/1940/prickly_pears
Source: bouncycastle
Section: libs
Priority: optional
Maintainer: Charles Fry <debian@frogcircus.org>
Build-Depends-Indep: debhelper (>= 4.0.0), free-java-sdk, libgnumail-java, gjdoc, junit
Standards-Version: 3.6.2

Package: libbcprov-java
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, java2-runtime
Suggests: java-virtual-machine
Description: Bouncy Castle Java Cryptographic Service Provider
 The Bouncy Castle Crypto package is a Java implementation of
 cryptographic algorithms.
 .
 This package contains a JCE Provider.
 .
 Homepage: http://www.bouncycastle.org/

Package: libbcmail-java
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, java2-runtime, libgnumail-java
Suggests: java-virtual-machine
Description: Bouncy Castle Java SMIME/CMS implementation
 The Bouncy Castle Crypto package is a Java implementation of
 cryptographic algorithms.
 .
 This package contains high level classes for dealing with S/MIME
 objects (RFC 3851), and classes for processing RFC 3852 Cryptographic
 Message Syntax (CMS) objects - also referred to as PKCS#7 (formerly
 RFC 2630, 3369).
 .
 Homepage: http://www.bouncycastle.org/

Package: libbctsp-java
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, java2-runtime, libgnumail-java
Suggests: java-virtual-machine
Description: Bouncy Castle Java TSP implementation
 The Bouncy Castle Crypto package is a Java implementation of
 cryptographic algorithms.
 .
 This package contains classes for dealing with Time Stamp Protocol
 (TSP) - RFC 3161.
 .
 Homepage: http://www.bouncycastle.org/

Package: libbcpg-java
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, java2-runtime
Suggests: java-virtual-machine
Description: Bouncy Castle Java OpenPGP/BCPG implementation
 The Bouncy Castle Crypto package is a Java implementation of
 cryptographic algorithms.
 .
 This package contains high level classes for dealing with OpenPGP
 objects, and low level classes for dealing with OpenPGP objects,
 user attributes, and signature attributes.
 .
 Homepage: http://www.bouncycastle.org/
#!/usr/bin/make -f
# -*- makefile -*-

configure: configure-stamp
configure-stamp:
	dh_testdir
	# Add here commands to configure the package.

	touch configure-stamp


#Architecture 
build: build-arch build-indep

build-arch: build-arch-stamp
build-arch-stamp: configure-stamp 

	# Add here commands to compile the arch part of the package.
	#$(MAKE) 
	touch build-arch-stamp

build-indep: build-indep-stamp
build-indep-stamp: configure-stamp 

	# Add here commands to compile the indep part of the package.

	# build as version 0 for the sake of package creation
	. ./build1-4 0

	touch build-indep-stamp

clean:
	dh_testdir
	dh_testroot
	rm -f build-arch-stamp build-indep-stamp #CONFIGURE-STAMP#

	# Add here commands to clean up after the build process.
	#-$(MAKE) clean
	rm -rf *-0*

	dh_clean 

install: install-indep install-arch
install-indep:
	dh_testdir
	dh_testroot
	dh_clean -k -i 
	dh_installdirs -i

	# install javadocs
	mv -i bcmail-jdk14-0/docs debian/libbcmail-java/usr/share/doc/apidocs
	mv -i bcpg-jdk14-0/docs debian/libbcpg-java/usr/share/doc/apidocs
	mv -i bcprov-jdk14-0/docs debian/libbcprov-java/usr/share/doc/apidocs
	mv -i bctsp-jdk14-0/docs debian/libbctsp-java/usr/share/doc/apidocs

	dh_install -i

install-arch:
	dh_testdir
	dh_testroot
	dh_clean -k -s 
	dh_installdirs -s

	# Add here commands to install the arch part of the package into 
	# debian/tmp.
	#$(MAKE) install DESTDIR=$(CURDIR)/debian/bouncycastle

	dh_install -s
# Must not depend on anything. This is to be called by
# binary-arch/binary-indep
# in another 'make' thread.
binary-common:
	dh_testdir
	dh_testroot
	dh_installchangelogs 
	dh_installdocs
	dh_installexamples
#	dh_installmenu
#	dh_installdebconf	
#	dh_installlogrotate	
#	dh_installemacsen
#	dh_installpam
#	dh_installmime
#	dh_installinit
#	dh_installcron
#	dh_installinfo
	dh_installman
	dh_link
	dh_strip
	dh_compress 
	dh_fixperms
#	dh_perl
#	dh_python
	dh_makeshlibs
	dh_installdeb
	dh_shlibdeps
	dh_gencontrol
	dh_md5sums
	dh_builddeb
# Build architecture independant packages using the common target.
binary-indep: build-indep install-indep
	$(MAKE) -f debian/rules DH_OPTIONS=-i binary-common

# Build architecture dependant packages using the common target.
binary-arch: build-arch install-arch
	$(MAKE) -f debian/rules DH_OPTIONS=-a binary-common

binary: binary-arch binary-indep
.PHONY: build clean binary-indep binary-arch binary install install-indep install-arch configure

Attachment: signature.asc
Description: Digital signature


Reply to: