Hello, I don't know why you are seeing that problem but it might be due to using dpkg-buildpackage. I usually build packages in a clean pbuilder ( http://packages.debian.org/sid/pbuilder ) because a) it does not force me to install development packages I don't need, and b) it does not shadow missing build-depends in the debian/control file.
I have created source packages for today's git ( available at http://www.elpauer.org/tmp/wt3/ ) using a slightly modified Wt 2.2.4 packaging. It's a native source package (i. e. no .orig.tar.gz + .diff.gz but a single .tar.gz), which is wrong but I don't care: it's a git snapshot :-) When a new version of Wt is released, few changes are required. In the current packaging, just make sure proper soversions are used in witty.install and witty.lintian-overrides. I am not providing binaries for that packaging because I want to split witty in several packages (one per library), as Wt has not changed soversions at the same time for quite some time now, which was not true when I started packaging Wt in a single binary package. Dependencies between 'witty' and the future 'libwt3-whatever' packages will be handled but atm I can't promise I won't break anything. I will start working in this new packaging (and in a much improved, more granular FindWt.cmake) when I'm back from Gran Canaria Desktop Summit ( http://www.grancanariadesktopsummit.org/ ), i. e. in the second half of July. On Thu, Jun 18, 2009 at 6:02 PM, Richard Ulrich<[email protected]> wrote: > Hi Pau, > > I'm still fighting with the debian package generation. > I wanted to create witty 2.99 packages for debian lenny. > Do do so, I copied the debian folder from > http://ftp.debian.org/debian/pool/main/w/witty/ to my git working copy. > Changed the versoin number in debian/changelog and debian/rules and > witty.install. > Then I ran "dpkg-buildpackage -rfakeroot". > That gives me an errormessage like : > dh_installexamples > dh_install --sourcedir=debian/tmp/ > cp: cannot stat 'debian/tmp///etc/wt/wt_config.xml' : No such file or > directory > dh_install: command returned error code 256 > > What do you usually have to change, when packing a new version of witty? > > Rgds > Richard > > > On Mon, 2009-06-08 at 17:58 +0200, Pau Garcia i Quiles wrote: >> On Fri, Jun 5, 2009 at 7:37 PM, Richard Ulrich<[email protected]> wrote: >> > Has anybody here packaged a witty webapp as a debian package? >> > >> > I want to do that for my witty app, and have read some documentation on >> > the creation of deb packages. After all I'm getting the impression, that >> > a witty web app might not be an ideal example to start with. >> > >> > What is of interest to me is: >> > - can I use the packaged witty deb's also as dependencies on a >> > voyage-linux (based on debian etch) installation, or do I have to link >> > statically? (Pau?) >> >> AFAIK, Wt is not in Voyage's repositories, so you would need to build >> them or statically link your application. There are instructions on >> how to build .deb packages from the source debs in >> http://www.webtoolkit.eu/wt/wiki/index.php/Installing_Wt_on_Debian >> >> Please note the current packaging of witty is only dynamic. If you >> want to build your application statically, you need to build Wt >> yourself. I am considering building a static version of the packages >> from Wt 3.0.0 on. >> >> > - what directories do you install the files to? >> >> If you want to be a good citizen, you should abide by the FHS, i. e: >> >> /usr/bin for your application >> /usr/share/doc/applicationname for the docs >> /usr/lib/applicationname for the plugins (if any) >> /usr/share/applicationname for platform-independent resources (images, >> JavaScript, etc) >> /etc/applicationname for the config files >> /tmp for temporary files (if any) >> >> If you want to make if simpler, you can also use /opt/aplicationname >> (or alike) and put everything in there. It's not the preferred place >> but it's still FHS-compliant ( see >> http://www.pathname.com/fhs/2.2/fhs-3.12.html ) >> >> >> > - how do I configure the apache integration (a2ensite and so on) >> >> So far I have not use Apache for Wt apps but this should not be >> difficult: use the postinst and prerm scripts >> >> > >> > Does anybody have some examples to share? >> > >> > Below is what I have so far. >> > >> > Thanks in advance >> > Richard >> > >> > ***************** debian/control: ******************* >> > Source: flugbuch2 >> > Package: flugbuch2 >> > Version: 2.0.5 >> ^^ Not needed. Use debian/changelog to specify version (and >> packaging version, for instance 2.0.5-1 ) >> >> > Section: web >> > Priority: optional >> > Architecture: i386 >> > Essential: no >> > standards-Version: 3.8.0 >> ^^ Latest standards is 3.8.1.0 >> >> > Homepage: http://sourceforge.net/projects/flugbuch2 >> > Depends: apache2, libapache2-mod-fastcgi, libfcgi0ldbl >> > Provides: flugbuch2 >> ^^ Not needed >> >> > Recommends: mozilla | netscape | firefox >> ^^ "Recommended" packages are installed. Maybe you mean "Suggests" ? >> >> > Installed-Size: 1024 >> ^^ Not needed >> >> > Maintainer: Richard Ulrich <[email protected]> >> > Description: Flight log book for paraglider pilots >> ^^ The short description must begin with lower case and you should >> also add a long description, i. e. >> >> Description: flight log book for paraglider pilots >> This is the long description. I have never flied with >> a paraglider but it sounds interesting. >> . >> In case you want to other paragraphs, make >> sure there is a dot joining them. >> >> You are missing the Build-Depends field. >> >> > >> > ***************** debian/rules: ************************* >> > #!/usr/bin/make -f >> > # -*- makefile -*- >> > # Sample debian/rules that uses debhelper. >> > # This file was originally written by Joey Hess and Craig Small. >> > # As a special exception, when this file is copied by dh-make into a >> > # dh-make output file, you may use that output file without restriction. >> > # This special exception was added by Craig Small in version 0.37 of >> > dh-make. >> > >> > # Uncomment this to turn on verbose mode. >> > #export DH_VERBOSE=1 >> > >> > >> > >> > >> > >> > configure: configure-stamp >> > configure-stamp: >> > dh_testdir >> > # Add here commands to configure the package. >> > >> > touch configure-stamp >> > >> > >> > build: build-stamp >> > >> > build-stamp: configure-stamp >> > dh_testdir >> > >> > # Add here commands to compile the package. >> > # $(MAKE) >> > codeblocks --build >> > $(CURDIR)/../proj/CodeBlocks/Flugbuch2_wt/Flugbuch2_wt.cbp >> > --target="Release_fcgi_static" >> >> Are you sure CodeBlocks is the only way to build the package? It looks >> excessive to me >> >> > #docbook-to-man debian/flugbuch2.sgml > flugbuch2.1 >> > >> > touch $@ >> > >> > clean: >> > dh_testdir >> > dh_testroot >> > rm -f build-stamp configure-stamp >> > >> > # Add here commands to clean up after the build process. >> > # $(MAKE) clean >> > codeblocks --clean >> > $(CURDIR)/../proj/CodeBlocks/Flugbuch2_wt/Flugbuch2_wt.cbp >> > --target="Release_fcgi_static" >> > >> > dh_clean >> > >> > install: build >> > dh_testdir >> > dh_testroot >> > dh_prep >> > dh_installdirs >> > >> > # Add here commands to install the package into debian/flugbuch2. >> > # $(MAKE) DESTDIR=$(CURDIR)/debian/flugbuch2 install >> > cp $(CURDIR)/../res >> > $(CURDIR)/debian/flugbuch2/usr/share/flugbuch2/www >> > -r >> >> 'install' is the preferred way to copy files >> >> > >> > >> > >> > # Build architecture-independent files here. >> > binary-indep: install >> > # We have nothing to do by default. >> > >> > # Build architecture-dependent files here. >> > binary-arch: install >> > dh_testdir >> > dh_testroot >> > dh_installchangelogs >> > dh_installdocs >> > dh_installexamples >> > # dh_install >> > # dh_installmenu >> > # dh_installdebconf >> > # dh_installlogrotate >> > # dh_installemacsen >> > # dh_installpam >> > # dh_installmime >> > # dh_python >> > # dh_installinit >> > # dh_installcron >> > # dh_installinfo >> > dh_installman >> > dh_link >> > dh_strip >> > dh_compress >> > dh_fixperms >> > # dh_perl >> > # dh_makeshlibs >> > dh_installdeb >> > dh_shlibdeps >> > # dh_gencontrol >> > dh_md5sums >> > dh_builddeb >> > >> > binary: binary-indep binary-arch >> > .PHONY: build clean binary-indep binary-arch binary install configure >> >> > > -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
