Hi!
On 11/19/2011 06:39 PM, Raphael Hertzog wrote:
> Hi,
>
> On Sat, 19 Nov 2011, Bernd Zeimetz wrote:
>> bzed@think ~debian/gpsd/build-area/gpsd-3.3 QUILT-% dpkg-gensymbols
>> -plibgps20 -Pdebian/libgps20 -d -e'libgps20.*'
>> Using references symbols from debian/libgps20.symbols
>> Scanning debian/libgps20/usr/lib/x86_64-linux-gnu/libgpsd.so.20.0 for symbol
>> information
>> ------------------------------------------------------^^^^^^^^^
>>
>> I do not want to scan libgpsd, only libgps. That worked well before but
>> broke since the last upgrade.
>
> Nothing changed... the behaviour that you see is that glob("libgps20.*")
> returns nothing because there's no matching file in the current directory.
>
> And due to this dpkg-gensymbols fallsback on finding files by itself.
>
> On Sat, 19 Nov 2011, Bernd Zeimetz wrote:
>> hi again,
>>
>>> bzed@think ~debian/gpsd/build-area/gpsd-3.3 QUILT-% dpkg-gensymbols
>>> -plibgps20 -Pdebian/libgps20 -d -e'libgps20.*'
>>
>> the regexp I copy and pasted here is buggy obviously - it should have been
>> -e'libgps.so.[0-9]*'. But the result is the same, it matches all libraries.
>
> I can't reproduce this here with the current unstable version:
> $ dpkg-gensymbols -plibgps20 -Pdebian/libgps20 -d -e'libgps.so.[0-9]*'
> Using references symbols from debian/libgps20.symbols
> Scanning libgps.so.20 for symbol information
> Merging symbols from libgps.so.20 as libgps.so.20
> Scanning libgps.so.20.0 for symbol information
> Merging symbols from libgps.so.20.0 as libgps.so.20
> Scanning libgps.so.20.0.0 for symbol information
> Merging symbols from libgps.so.20.0.0 as libgps.so.20
> Storing symbols in debian/libgps20/DEBIAN/symbols.
>
> But again this is sort of broken since you're scanning the files in the
> build tree and not the files that have been installed in the package. You
> should really use -e'debian/libgps20/usr/lib/libgps.so.[0-9][0-9]'.
>
> Maybe the new upstream version no longer has the libraries in the current
> directory but in a sub-directory and due to this the glob() no longer
> matches and dpkg-gensymbols fallsback to finding files by itself.
Indeed, they are in the multi-archified directory now.
> The manual page is a bit misleading though, it's not a regular expression
> but a "shell pattern used for pathname expansion". I'll fix that and I'll
> also add a warning when the maintainer uses a pattern that doesn't match
> anything.
Thanks for the explanation - what I'm seeing here is indeed a mix of the
additional directory together with assuming that -e takes a regexp as
documented. So please fix the documentation and add the warning, then it would
have been obvious.
Thanks,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
