| Server IP : 185.11.201.71 / Your IP : 192.168.7.18 Web Server : Apache/2.4.29 (Ubuntu) System : Linux tech-virtual-machine 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 User : tech ( 1000) PHP Version : 7.4.28 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/lintian/checks/ |
Upload File : |
Check-Script: triggers Author: Niels Thykier <niels@thykier.net> Type: binary, udeb Info: Check of trigger files in the binary package. Needs-Info: bin-pkg-control Tag: unknown-trigger Severity: important Certainty: possible Info: The package has a trigger that Lintian does not recognise in its control file. . The package may be uninstallable, if dpkg does not support the trigger. . If this is a new type of trigger, then Lintian may simply be out of date. Please verify if the latest version of Lintian knows of the trigger, or file a bug against Lintian. Ref: deb-triggers(5) Tag: uses-implicit-await-trigger Severity: normal Certainty: possible Info: The listed trigger is present in the control file of the package. The trigger is an await trigger, which may not be obvious from its name. . Await triggers place rather strong requirements on dpkg that often lead to trigger cycles due to changes in other packages. . If the package does not need the guarantees that dpkg provides to await triggers, please use the "-noawait" variant of the trigger. This is often the case for packages that use the trigger to compile a form of cache. . If the package does need the guarantees provided by dpkg, then please document the rationale in a comment above the trigger and use the "-await" variant of the trigger to avoid this warning. Ref: deb-triggers(5), #774559 Tag: repeated-trigger-name Severity: important Certainty: certain Info: The package repeats the same trigger. There should be no reason to do this and it may lead to confusing results or errors. . For the same "base" type of trigger (e.g. two <tt>interest</tt>-type triggers) the last declaration will be the effective one. . This tag is also triggered if the package has an <tt>activate</tt> trigger for something on which it also declares an <tt>interest</tt>. The only (but rather unlikely) reason to do this is if another package <i>also</i> declares an <tt>interest</tt> and this package needs to activate that other package. If the package is using it for this exact purpose, then please use a Lintian override to state this. . Please remove any duplicate definitions. Ref: deb-triggers(5), #698723