FS#34434 - [util-linux] No support for remote users in chsh/chfn in 2.22
Attached to Project:
Arch Linux
Opened by Cody Maloney (maloney) - Saturday, 23 March 2013, 21:21 GMT
Last edited by Toolybird (Toolybird) - Sunday, 25 June 2023, 21:28 GMT
Opened by Cody Maloney (maloney) - Saturday, 23 March 2013, 21:21 GMT
Last edited by Toolybird (Toolybird) - Sunday, 25 June 2023, 21:28 GMT
|
Details
Description:
util-linux doesn't have support in 2.22 for remote users (LDAP, etc.) which is a feature loss when the move from shadow-utils to util-linux for these utilities occured. I wrote patches which were accepted and included in 2.23 support this. Please enable this support (Add libuser as a dependency and it should "just work", --with-libuser in configure if you want to force it). This means libuser needs to move to core though, which probably means it needs to either have the python API disabled or move to a split package (libuser, python2-libuser?). Additional info: * util-linux 2.23-rc1 |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 25 June 2023, 21:28 GMT
Reason for closing: Won't implement
Additional comments about closing: See comments
Sunday, 25 June 2023, 21:28 GMT
Reason for closing: Won't implement
Additional comments about closing: See comments
Dave, you had opinions about this I believe?
I admit the relatively limited usefulness if you don't have non-local accounts, but I have no good stats, just the notes that openldap is in core, ldap auth modules are in extra, and pam krb5 modules have 4 votes in AUR. I also know for the network I'm on no one uses chsh/chfn most of the time so it took quite a while to notice that the functionality was lost (3 months between the arch switch in June and the bug report in September).
That said, adding python2 to core is not an option. However, I think it would be acceptable to have it as an optdepend (which means it can stay in extra and libuser stay in core).
Do you see any problem with that Dave? If not, I'll take it to the ML.
I'm not clear on how you see this working out... we can't split between repos. As I see it, the options are:
1) duplicate the build -- shared lib goes to core, python stuff goes to extra under the name python2-libuser or such.
2) put libuser in extra regardless, make it an optdepend (breaking chsh/chfn)
3) don't package the python crap.
> I also know for the network I'm on no one uses chsh/chfn most of the time so it took quite a while to notice that the functionality was lost (3 months between the arch switch in June and the bug report in September).
Yeah... this is a rousing endorsement for inclusion...
move libuser to [core], but make python2 an optdepend.
> > I also know for the network I'm on no one uses chsh/chfn most of the time so it took quite a while to notice that the functionality was lost (3 months between the arch switch in June and the bug report in September).
> Yeah... this is a rousing endorsement for inclusion...
Well, you usually only do this once (when you first use a network), so it is not so strange.
but you (Arch) already did it, freetype2 was maked an optdep (and makedep) for grup and recide in other repo (freetype2 in extra and grub in core) so is what Arch do and is supported and used on critical package.
So I think is ok do it.