PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` #!/bin/sh set -e # Packages including pam configurations need to include a block like # the following to arrange for removal of the PAM profile prior to # package removale. Libpam-runtime is special because it includes the # machinery for managing the profiles and because there is a check to # make sure at least one profile is enabled. Libpam-runtime can only # be removed in a situation where dpkg checks are being overriden; in # that case the resulting PAM config is likely to be broken anyway. # But we prefer to permit the removal if enough dpkg force options are # given than to create an infinite loop. So, this block is commented # out, left here as an example for other packages. # if [ "$1" = remove ] ; then # pam-auth-update --package --remove unix # fi