On 04/03/2015 03:34 PM, Jochen Topf wrote: > On Thu, Apr 02, 2015 at 10:00:16PM +0200, Sebastiaan Couwenberg wrote: >> On 03/31/2015 10:34 PM, Sebastiaan Couwenberg wrote: >>> On 03/31/2015 10:13 PM, Jochen Topf wrote: >>>> Currently the package seems to build, but the created .deb files are >>>> essentially empty!? >> >> I've updated the pyosmium package to use the pybuild build system, it >> now builds and installs the Python module for both versions. > > Looks good. > > What is the policy regarding package descriptions in control files? The > current > description is somewhat misleading, because it mostly describes abilities of > the underlying libosmium that are not all available in pyosmium. Shall I > change > the description?
Policy sections 3.4 & 5.6.13 document the description requirements: https://www.debian.org/doc/debian-policy/ch-binary.html#s-descriptions https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description The Developers Reference further documents some best practices: https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-control Please go ahead with your description changes. >> For now it ignores the documentation which looks like a work in progress. > > Yes. We'll probably finish that in a week or two. We can wait with the release > till then. I'll ping you when that's done. > >> Will the documentation remain separate from the python builds? > > Probably. I'll ask Sarah about it. I think the packaging is mostly ready, so we'll only need to add building & installing the documentation when that's ready upstream. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
