Bug#946988: coinor-dylp_1.10.4-1_source.changes REJECTED

[Sudip Mukherjee <sudipm.mukherjee@gmail.com>]

Hi Adam,

On Thu, Dec 19, 2019 at 5:04 AM Adam Borowski <kilobyte@angband.pl> wrote:
>
> Control: reopen -1
>
> On Thu, Dec 19, 2019 at 04:49:10AM +0000, Debian FTP Masters wrote:
> > Source-only uploads to NEW are not allowed.
> >
> > binary:coinor-libdylp1 is NEW.
>
> Hrm, my script for automating bindebdiffs doesn't handle
> appearing/disappearing binaries well, making them easy to miss.  And I
> didn't notice that bit.
>
> Thus: it's fit for re-upload, but generally, it's best for a package for
> NEW, even binNEW, to be in a good shape (rather than small incremental
> changes which I prefer), thus I wonder if you'd like to polish at least the
> changelog first.
>
> In which, mentioning other removed/added binaries is another important bit.

Thanks for taking a look at it. I was actually confused with the
names. The previous package coinor-libdylp0 provides
"/usr/lib/libDylp.so.0" linking to "/usr/lib/libDylp.so.0.0.0" and I
think that is the reason the package was named with a '0'. But the
version was wrong. It should have been named
"/usr/lib/libDylp.so.1.6.0" and the package name should have had a '1'
instead of '0'.
But anyway, do you think I should keep the name as "coinor-libdylp0"
instead of moving to "coinor-libdylp1" based on my above mentioned
understanding?

While polishing it, I think I will also push it to salsa, that will
also fix two other lintian warnings.


-- 
Regards
Sudip