Re: GMiller 2019-01-16 <[🔎] 224e2555e56a21b88749bfa77e88a5dd.startmail@startmail.com>
> I am working the subject ITP (first attempt at a Debian package). I am
> following procedure per the 'Debian New Maintainers Guide' and have reached
> 'dpkg-buildpackage -us -uc'.
>
> The build goes OK down through where '3.0 (quilt)' starts, at which point I
> receive two types of errors and warnings.
Hi Garie,
if the build leaves modified files behind, the next build from the
same directory will fail because dpkg-source complains that those
changes are not properly represented as quilt patches.
For an immediate workaround, you can use dpkg-buildpackage -b to skip
building the source package, and just build the binary packages.
To reset the working directory to what's in the upstream tarball,
either use git operations ("git checkout .", assuming you haven't
commited any of these changes to git), or use "origtargz -u" (from
devscripts) to re-extract the tarball to the current directory
(Warning: this will wipe any changes to upstream files that have not
yet been recorded in debian/patches/).
> But first I will note that the 'Dream' application has not heretofore
> included files supporting Autotools (no Makefiles). So, within my limited
> experience I have written these files presuming they will be required for
> Debian. I have also added a subdirectory which includes some header files
> that are necessary to support the FunCube and a Docs subdirectory for added
> documentation (well, debian too). These sum most of the changes I have made
> so far. I presume these will somehow appear in difference files, but then I
> have never done a package before.
(Not sure how to answer that without seeing the concrete package.)
> The warnings are generally like this; warning: new empty file
> '../autoscan.log' not represented in diff
>
> executable mode 0755 file of '../configure' not represented in diff
>
> The autoscan.log is likely not needed, but I don't if the mode must be set
> in the configure files or how to do so. Can I ignore these warnings?
Yes, but the above instructions will also remove these.
Christoph DF7CB