Thanks Andreas and Christian for the updates/comments. I agree that I should have been more verbose in the changelog. I'm tracing all the commits to learn more about packaging. I was playing with gbp for updating upstream. I really like how it works with git! No worries, my time was not wasted anyway.
I talked to Christian briefly about the symbol file. He added one for liblinear4. I have a question about this file. The symbol file I generated looks a bit different from liblinear4.symbols, in which several lines start with (c++) and contain the exact parameters. I couldn't figure out how to make dpkg-gensymbols produce this. Thanks, Chen-Tse On Wed, Dec 25, 2019 at 10:02 AM Andreas Tille <ti...@debian.org> wrote: > On Wed, Dec 25, 2019 at 03:04:47PM +0100, Christian Kastner wrote: > > On 2019-12-25 10:59, Andreas Tille wrote: > > > Kind regards > > > > > > Andreas. > > > > I've re-read my original message and feel that I was overly harsh. I was > > irritated about the rushed upgrade as in private communication with > > Chen-Tse, I highlighted precisely the possible complexity of this > > upgrade and how it should be performed properly -- but, that was private > > communication. > > I admit I did not considered it overly harsh. My upload was in fact not > the best idea and your response just reflected it. > > > Apologies. > > Thanks but from my point of view not needed. Everything is fine at my > side and as I said I'll now leave the issue to you who are more > comfortable with that package. Something that came to my mind later: > When upstream does not mark SOVERSIONs: In this case I usually add a > symbols file. Thats more maintenance burden but usually helps to spot > issues with ABI changes. > > Kind regards > > Andreas. > > > -- > http://fam-tille.de >
