[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: calling ldconfig



Hi Bas,

I updated chroot but that didnt work. Still have the same report from linitan.  See the lintian output


On Wed, Dec 23, 2015 at 5:55 PM, Rashad Kanavath <mohammedrashadkm@gmail.com> wrote:


On Wed, Dec 23, 2015 at 5:52 PM, Sebastiaan Couwenberg <sebastic@xs4all.nl> wrote:
On 23-12-15 17:39, Rashad Kanavath wrote:
> I have an error from lintian after update to 5.2. This may be because I
> renamed .install and .symbols files when updating package and is the wrong
> way.
>
> E: libotbmetadata-5.2-1: postinst-must-call-ldconfig
> usr/lib/x86_64-linux-gnu/libOTBMetadata-5.2.so.1
>
> In documentation[1], it list some circumstances where ldconfig needs to be
> called. But I cannot understand why it appears after 5.2 update.
>
> [1]https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-ldconfig

The maintainer scripts are no longer required for their #DEBHELPER#
substitution of the ldconfig calls. This is now handled by triggers:

 https://lists.debian.org/debian-devel/2015/10/msg00050.html

This leads me to think that your sid chroot is outdated and doesn't have
the new debhelper yet.

Do you update your pbuilder chroots at least daily before working on a
package? You need to update sid chroots frequently because changes are
made every day.
No. That might be it. trying update and rebuild now..

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1




--
Regards,
   Rashad



--
Regards,
   Rashad

Attachment: lintian_out_amd64.log
Description: Binary data


Reply to: