Vasudev Kamath <[email protected]> writes:
> I would reduce the level for dpkg-gensymbols so that build won't fail
> again and collect this diff together and patch the symbols file. I
> prefer symbols files over d-shlibs as it is supposed to do more help
> than just having shlibs system.
Fair enough; you just needn't feel obligated to do so for ctpp2.
> Can you do me a favor remove the --override='s/libc0.1-dev/libc6-dev/
> line in rules which is given as option for d-shlibmove and try
> building it to see what exact error you get.. I want to clear an FTBFS
> before it happens ;-)
I stand corrected:
d-shlibmove --commit \
--devunversioned \
--multiarch \
--exclude-la \
--override s/libctpp2-2-dev/libctpp2-dev/ \
--movedev "debian/tmp/usr/include/*" usr/include/ \
debian/tmp/usr/lib/libctpp2.so
Library package automatic movement utility
devlibs error: There is no package matching [libc0.1-dev] and noone
provides it, please report bug to d-shlibs maintainer
make: *** [debian/stamp-local-shlibs-libctpp2] Error 1
It looks like this error stems from d-devlibdeps, whose validate_package
function fails on libc0.1-dev because apt-cache segfaults(!):
$ apt-cache --no-generate show libc0.1-dev
Segmentation fault
The override sidesteps this because d-devlibdeps's overridedevlibdeps
function filters the resulting libc6-dev entry out altogether:
function overridedevlibdeps () {
# overrides necessary until the scheme is adopted.
sed \
"${OVERRIDE[@]/#/-e}" \
[...]
-e 's/libc6-dev//' \
[...]
As such, I'd recommend adjusting overridedevlibdeps to handle the other
possible names:
-e 's/libc0.[12]-dev//' \
-e 's/libc6-dev//' \
-e 's/libc6.1-dev//' \
and adjusting the override accordingly (meanwhile broadening it slightly):
--override='s/libc[0-9].[0-9]-dev//'
> Thanks for the continuous support :-)
No problem.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
