Thanks, I think you should read over the Ubuntu packaging guide and some of the MOTU classroom sessions" on packaging. I didn't look that closely, but I caught at least two critical things:
1) Don't delete the debian/changelog In fact, you keep it and append your changes. There is a helper program called "dch" that will help you format and change it properly. If you type "dch -i" it will add an entry for you, make sure the name and email matches yours and that the version number is correct (see the ubuntu wiki on how to do that). Add that it is an upgrade from upstream, place " (LP: #374343) " somewhere in the description. The version number should be something like: <packagename>_<versionnumber>-0ubuntu1 0ubuntu1 means: 0 --> not in Debian ubuntu --> ubuntu local changes that are not in Debian 1 --> first revision in Ubuntu 2) debian/control needs to be formatted as described on the wiki. You put Ubuntu developers or MOTU down as the maintainer (whatever the wiki says to do) and make the debian maintainer the XSBC maintainer like below: Maintainer: Ubuntu MOTU Developers <[email protected]> XSBC-Original-Maintainer: Captain Packager <[email protected]> also in debian/control : Don't change the section and the priority. They have important meanings (see the Debian Policy Manual: http://www.debian.org/doc/debian-policy/) 3) In general we want these packages to be as close to the Debian packages as possible, so we want to do the minimal changes possible. If a simple upgrade of the upstream source code builds, all you should need to do is increment the changelog "dch -i" and then change the maintainer in debian/control as above (this is all described on the wiki). If you have questions, check on #ubuntu-motu, people are very helpful there! -- Please sync to 2.2.0 release https://bugs.launchpad.net/bugs/374343 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
