> It drops symbols so effectively this includes a transition. I am aware of this. This reason I did not think an ABI bump would be necessary in this case, is that these symbols anyway cannot be used since the code behind violates the license.
> This upload will need an ABI bump - preferably the same as upstream, but given they haven't released this version yet, it is not certain we can reuse that bump (in case they want to remove/change more symbols). I am also upstream, so in general this would not be a problem. The only complication I see is that I, as a Debian Maintainer, will need a sponsor to get the NEW binary package libycadgraywolf1 uploaded. I can bump the ABI upstream, and prepare a new package. Cheers, Ruben 2017-03-07 9:00 GMT+01:00 Niels Thykier <ni...@thykier.net>: > Niels Thykier: >> [...] >> >> It drops symbols so effectively this includes a transition. Only one >> rdep (qflow) with same maintainer. I cannot tell if it uses the symbols >> (codesearch.d.n does not respond to the search and I don't have time to >> check manually). >> >> I believe we need an ABI bump for this. Will check up and get back to you. >> >> ~Niels >> >> > > Hi Ruben, > > This upload will need an ABI bump - preferably the same as upstream, but > given they haven't released this version yet, it is not certain we can > reuse that bump (in case they want to remove/change more symbols). > > If you have questions about how to perform the ABI bump, please feel > free to ask on debian-mentors@l.d.o (or #debian-mentors, if you are on IRC). > > Thanks, > ~Niels > >
