libpam might miss ABI specific dependencies for pam-plugins-*, for RPM uses
generic names to check the packages depending on it and doesn't consider the
arch, which will lead to packaging issues in multilib build.
pam_plugin_hook is added because the plugin packages are dynamically
generated, so w
On 5/23/13 3:01 AM, Ming Liu wrote:
libpam might miss ABI specific dependencies for pam-plugins-*, for RPM uses
generic names to check the packages depending on it and doesn't consider the
arch, which will lead to packaging issues in multilib build.
pam_plugin_hook is added because the plugin pa
On Thursday 23 May 2013 09:40:51 Mark Hatle wrote:
> On 5/23/13 3:01 AM, Ming Liu wrote:
> > libpam might miss ABI specific dependencies for pam-plugins-*, for RPM
> > uses
> > generic names to check the packages depending on it and doesn't consider
> > the arch, which will lead to packaging issues
On 5/24/13 3:52 AM, Paul Eggleton wrote:
On Thursday 23 May 2013 09:40:51 Mark Hatle wrote:
On 5/23/13 3:01 AM, Ming Liu wrote:
libpam might miss ABI specific dependencies for pam-plugins-*, for RPM
uses
generic names to check the packages depending on it and doesn't consider
the arch, which wi
On 05/23/2013 05:01 PM, Ming Liu wrote:
libpam might miss ABI specific dependencies for pam-plugins-*, for RPM uses
generic names to check the packages depending on it and doesn't consider the
arch, which will lead to packaging issues in multilib build.
pam_plugin_hook is added because the plugi
