-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 23 Feb 2009 22:37:00 +0100 Daniel Leidert <[email protected]> wrote:
> > No problems up to here and no need to touch/repack the orig-tarball :) > Thanks, again:-) I also manage to solve this issue with the help of the list. Using -f /path/to/tar-ball to dh_make and dh_make couldn't care less what name and packaging scheme used upstream. Amazing set of tools, dh_*** :-) - -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir <at> datanom <dot> net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir <at> miras <dot> org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 - -------------------------------------------------------------- Executive ability is prominent in your make-up. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmjIcsACgkQQQOPluUB9RweugCfeDunw3tglAkCRHlOYuuhhnOW sx8AniXROZKDixWx5JPddRHRYqGZa0h8 =4Jk4 -----END PGP SIGNATURE-----
