Dear Wiki user, You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.
The "DebianMed/MoM" page has been changed by AndreasTille: https://wiki.debian.org/DebianMed/MoM?action=diff&rev1=95&rev2=96 Comment: More information how to quickstart PATH_TO_package_template_CLONE/package_template/personalise_template https://github.com/USER/PACKAGE/ or PATH_TO_package_template_CLONE/package_template/personalise_template PACKAGE - 1. The good thing for Github maintained projects is that we can pretty much predict the {{{debian/watch}}} file which is parsed by {{{uscan}}}. If the target software is not at Github the {{{package_template}}} contains lots of other examples for valid {{{debian/watch}}} files. So edit {{{debian/watch}}} if the project is somewhere else than Github and do + 1. The good thing for Github maintained projects is that we can pretty much predict the {{{debian/watch}}} file which is parsed by {{{uscan}}}. If the target software is not at Github the {{{package_template}}} contains lots of other examples for valid {{{debian/watch}}} files. So go to the freshly created dir {{{PACKAGE_}}} (mind the trailing '_' at the end of the package name!) edit {{{PACKAGE_/debian/watch}}} if the project is somewhere else than Github and do - cd PACKAGE/debian && uscan --verbose + cd PACKAGE_/debian && uscan --verbose 1. In all cases when you manage to create a valid {{{debian/watch}}} file you can safely remove the files {{{debian/get-orig-source*}}}. These are just fallbacks if there is no easy way to use {{{uscan}}} which is luckily extremely rare. + 1. I usually also remove {{{debian/doc-base}}} and {{{debian/lintian-overrides}}}. You can easily copy them over later from the original {{{package_template}}} Git if needed. + 1. Now add a proper version number in {{{debian/changelog}}} which was initially set to 0.0.0 to make sure {{{uscan}}} will be forced to fetch something newer. Set it to the version {{{uscan}}} has fetched for you (possibly double check upstream web page whether this is really the version you want to package) + 1. Edit the Description field in {{{debian/control}}}. It needs a short and a long description. Upstream homepage will hopefully provide the needed information. + 1. Possibly find a publication covering the software and edit {{{debian/upstream/metadata}}} to add publication details + 1. So far for the preparation of the {{{debian/}}} dir. Now we create the actual packaging git. Now it becomes obvious why in the beginning the '_' was attached to the package name. We need a fresh directory with the package name now. This is the way how you can create the repository and import the source tarball + mkdir PACKAGE && cd PACKAGE && git init && gbp import-orig --pristine-tar --no-interactive ../PACKAGE_VERSION.orig.tar.gz + 1. Finally move over you prepared {{{debian/}}} dir and commit it + mv PACKAGE_/debian PACKAGE && cd PACKAGE && git add debian && commit -a -m"Initial packaging" + + == Current mentors, students and packages == _______________________________________________ debian-med-commit mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-commit
