Re: How to determine when being packaged under Debian?

ndividual build. Also, I would question the assumption a bit: if this is important for distributions, wouldn't it be important for all builds? -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>

Re: How to determine when being packaged under Debian?

check into the Debian packaging to be sure that the software was built this way and abort the build during the check phase if it wasn't, with a big comment explaining the situation. Then hopefully anyone else who picks up the package, if that happens, would be aware. -- Russ Allbery (r...@debi

Re: How to determine when being packaged under Debian?

Jeffrey Walton writes: > On Wed, Sep 30, 2015 at 3:55 AM, Russ Allbery wrote: >> Yeah, this is why I'd put a check into the Debian packaging to be sure >> that the software was built this way and abort the build during the >> check phase if it wasn't, with a big c

Re: To override or not to override?

remove them. That should make it safer to add an override for a Lintian bug, since when the bug is fixed, Lintian will tell you that you can remove it. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>

Re: public-domain in the debian/copyright

mewhere in debian/copyright (a Comment field or whatever). -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>

Re: git-buildpackage pattern question

ut your packaging. I think gbp import-orig, under the hood, does something more complicated using Git plumbing to create the merge commit directly. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>

Re: Packaging mmh (fork of nmh)

gt; subdir of /usr/bin is /usr/bin/mh. > So nmh is not following FHS either. mh implementations have a special historical exception in the FHS. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>

<    3   4   5   6   7   8