Hi!
On Mon, 2015-10-05 at 16:14:38 +, Niels Thykier wrote:
> As of debhelper/9.20151004, dh_makeshlibs is now using triggers rather
> than maintainer scripts to invoke ldconfig.
>
> * Lintian in untable + testing is already aware of this
> * Lintian has /not yet/ been backported. Lintian f
Hi,
As of debhelper/9.20151004, dh_makeshlibs is now using triggers rather
than maintainer scripts to invoke ldconfig.
* Lintian in untable + testing is already aware of this
* Lintian has /not yet/ been backported. Lintian from backports still
(incorrectly) reports this an issue.
Please d
On 2015-08-29 23:52, Aurelien Jarno wrote:
>[...]
>
>> * The major concern I have, is that "activate"-triggers are done for
>>- unpack (is this ok?)
>>- configure (ok)
>>- remove (ok, assuming it is post-removal)
>>- purge (should not be an issue)
>>- deconfigure (would be a no
On 2015-08-23 17:01, Niels Thykier wrote:
> Hi,
Hi,
> Currently, all Debian libraries (is required to) have a call ldconfig in
> postrm and postinst. I would like to replace that with a declarative
> method somehow. There are a couple of reasons for this:
>
> * Packages without postinst scrip
On 2015-08-25 15:12, Ian Jackson wrote:
> Niels Thykier writes ("Replacing ldconfig maintscripts with declarative
> methods"):
>> A possible solution is to replace these scripts with an
>> "activate-no-await" trigger (again, no-await to avoid trigger cycles).
>> I would need libc-bin to promote it
Niels Thykier writes ("Replacing ldconfig maintscripts with declarative
methods"):
> A possible solution is to replace these scripts with an
> "activate-no-await" trigger (again, no-await to avoid trigger cycles).
> I would need libc-bin to promote its trigger to part of its API for this
> to work
6 matches
Mail list logo
