Package is updated. I made those changes and tried to upload last night,but the update was silently dropped. Deleting the first upload and uploading again worked. But, doing that caused other problems last time.
I don't understand why debian/control tries to have a tidy Build-Depends but dpkg-buildpackage creates debian/tinymux/DEBIAN/control with the full dependencies including libpcre3. And, that doesn't show up on a lintian report. It's hard to know what it cares about and what it doesn't care about. My guess is that everything on the Depends: line is debian/tinymux/DEBIAN/control is part of the base system _except_ for libpcre3 so that must be called out explicitly in Build-Depends? Thanks for your help. Stephen On Sun, Aug 9, 2020 at 6:38 PM Adam Borowski <kilob...@angband.pl> wrote: > On Sun, Aug 09, 2020 at 04:32:31PM -0600, Stephen Dennis wrote: > > * Package name : tinymux > > Version : 2.12.0.10-1 > > > > https://mentors.debian.net/debian/pool/main/t/tinymux/tinymux_2.12.0.10-1.dsc > > > tinymux (2.12.0.10-1) UNRELEASED; urgency=medium > ^^^^^^^^^^ > This tag designates the package's state as WIP, and would have caused an > autoreject if uploaded. By the time you send a RFS, the package is > supposed > to be ready to go. Thus, could you please target unstable? > > > * New upstream release. > > * Update Standards-Version in debian/control from 4.0.1 to 4.5.0 (no > > change needed). > > * Avoid embedding PCRE. > > * Removed PCRE license from debian/copyright. > > Alas, it fails to build in a clean environment: > > command.cpp:23:10: fatal error: pcre.h: No such file or directory > 23 | #include <pcre.h> > | ^~~~~~~~ > > which is caused by an obvious missing Build-Dependency. > > > Meow! > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ > ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i. > ⠈⠳⣄⠀⠀⠀⠀ >
