Lars Heill wrote, On 02/07/08 15:18: > Lars Heill wrote, On 02/06/08 18:20: >> Daniel Holbach wrote, On 02/06/08 11:14: >>> debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a >>> warning, so nothing to worry about. Pbuilder shouldn't fail building it >>> because of that. >>> >>> If all fails, try to upload to PPA: >>> http://help.launchpad.net/PPAQuickStart - your page is fine too. >>> >>> Review: - try to make it non-native (have a >>> sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/ >>> bits) and .dsc) >>> - "The deprecated frameworks software is not included" (in >>> debian/README.Debian) could be a bit more verbose. Also adding that >>> information to debian/copyright would not hurt. >>> - Make it Standards-Version 3.7.3 to comply with the newest policy >>> version. >>> - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty >>> directory >>> - please adhere to http://wiki.ubuntu.com/DebianMaintainerField >> >> Stepping into a mess getting confused when trying to make it non-native: >> >> 1. CDBS tarball would like a tarball in sun-javadb-10.3.2.1, without it >> I am not suprised to get stuff like >> >> dh_install -psun-javadb-client >> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib >> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such >> file or directory >> >> 2. With a copy of sun-javadb_10.3.2.1.orig.tar.gz in sun-javadb-10.3.2.1, >> I get >> >> dpkg-source: warning: unknown information field 'Homepage' in >> input data in general section of control info file >> dpkg-source: warning: Version number suggests Ubuntu changes, but >> there is no XSBC-Original-Maintainer field >> dpkg-source: building sun-javadb using existing >> sun-javadb_10.3.2.1.orig.tar.gz >> dpkg-source: building sun-javadb in >> sun-javadb_10.3.2.1-0ubuntu1.diff.gz >> dpkg-source: warning: newly created empty file >> 'sun-javadb_10.3.2.1.orig.tar.gz.cdbs-config_list' will not be >> represented in diff >> >> and then: >> >> dpkg-source: cannot represent change to >> sun-javadb_10.3.2.1.orig.tar.gz: binary file contents changed >> dpkg-source: warning: ignoring deletion of file CHANGES.html >> dpkg-source: warning: ignoring deletion of file RELEASE-NOTES.html >> ... >> dpkg-source: warning: ignoring deletion of file >> docs/pdf/ref/refderby.pdf >> dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.dsc >> dpkg-source: unrepresentable changes to source >> >> booom! >> >> With pbuilder I run into this one, regardless: >> >> dh_install -psun-javadb-client >> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib >> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such >> file or directory >> >> with orig.tar.gz, dsc and diff.gz in place. >> >> There must be some fundamental I have missed, - tried googling, and >> all FAQs and guides I know of... > > Silly me forgot a 'cd'... > > Have updated Source link with new packages. Changes: > > * non-native > * no longer unzip build dependency > * put "frameworks" back in for consistency across platforms for Java DB > ==> get "W: sun-javadb-core: executable-not-elf-or-script" for .ksh > files under frameworks. Yes, this is due to these files not > including > "#!/bin/sh". > - Can these warnings be overlooked? > - Should I add dependency on ksh | mksh | pdksh for this? > (they are deprecated, and they do execute under under sh and bash) > * Standards-Version is now 3.7.3 (disregarding lintian warning on this) > * Maintainer set to "MOTU Developers