Re: Bug#1068017: util-linux: please ship liblastlog2 packages

Chris Hofstaedtler <[email protected]>
Newsgroups gmane.linux.debian.alioth.pkg-shadow,gmane.linux.debian.devel.ssh
Message-ID <iwkaj65bfjzvcpuh535siyqf4kxwasppe5dzsujl45are5synj@s5j7x5ljyxys>
Hi,

* Iker Pedrosa <[email protected]> [240403 09:43]:
> Hi Chris,
> 
> I have some questions regarding your proposal:
> 
>    - What is the difference between liblastlog2 and libpam-lastlog2
>    binaries? Upstream util-linux only provides one binary (lastlog2) so this
>    confuses me.

util-linux upstream provides three binary objects to be built:
- liblastlog2.so
- pam_lastlog2.so
- lastlog2 (program)

Debian's PAM policy says to put PAM modules into their own package,
thus libpam-lastlog2. liblastlog2.so would go into the
liblastlog2(-0) package. The lastlog2 program either into its own
lastlog2 package, or elsewhere.

>    - Did you consider using a systemd service to upgrade from lastlog to
>    lastlog2 data?

No, I did not consider this, as I wasn't aware of any
implementations for this. Does u-l upstream ship such a service?

> This way when the distribution is updated to the next
>    version you can also remove the lastlog binary and all its dependencies. In
>    addition, you can use "--disable-lastlog" in shadow to stop building this
>    binary.

Chris
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.