Hi, and happy new year
Could the patch from Dmitry Shachnev applied to dpkg soonish if that is ok?
I have patched it for Kubuntu's CI repositories, so temporarily our
symbols handling is not messed up, but it would obviously be better if
the correct output could be fixed at debian's end and then
Also tracked in:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1728847
On 30/10/17 09:13, Dmitry Shachnev wrote:
> The attached small patch fixes the issue for me. Tested with libjpeg-turbo,
> where one symbol was deliberately removed.
>
> The previous if (defined $state) check was always true, because a //=
> operator is used to define $state two lines above.
>
>
On Mon, Oct 30, 2017 at 09:03:06AM +, Rik Mills wrote:
> The output of dpkg-gensymbols has regressed when reporting new or
> changed symbols
>
> Previously the output stated:
>
> dpkg-gensymbols: debian/libnameDEBIAN/symbols doesn't match completely
> debian/libname.symbols
>
> this now
Package: dpkg
Version: 1.19.0.4
The output of dpkg-gensymbols has regressed when reporting new or
changed symbols
Previously the output stated:
dpkg-gensymbols: debian/libnameDEBIAN/symbols doesn't match completely
debian/libname.symbols
this now incorrectly states:
dpkg-gensymbols: warning:
5 matches
Mail list logo
