Colin Watson <[email protected]> writes: > For some reason I didn't pick this up in my archive search; sorry! > (Maybe I was searching testing rather than unstable or something, since > inn2 isn't in testing.) I know this wasn't the most graceful transition > ever, but, since the number of packages affected here is on the order of > a dozen, and most of the others have been fixed by now, I think it's > better to just fix everything rather than add warnings. See also > #734946.
> Marco, here's a patch; could you apply it? The bulk of it is > documentation updates. Judging by Russ's comments in #274229 and > https://lists.debian.org/debian-devel/2013/11/msg00014.html, this was > already something various sites were doing locally anyway, so it would > be good for inn2 to deal with it. I've put the new patch in the "Debian > integration" section, but I expect it would be upstreamable too. The specific change with the news user on a system with inn2 installed is somewhat debatable, as it's quite common for INN administrators to need to get an interactive shell as news to perform various actions with correct privileges. That said, I think the same issues apply here as applied to the other base accounts on any system where INN or some other news server is not installed, and given that that's 99% of the Debian systems out there, I think it's best to leave the shell as invalid and teach administrators to use the -s option to su. We could change the shell when inn2 is installed... but that would be a huge pain to do properly and I don't think it's worth it. This probably warrants a NEWS.Debian addition as well, though, since in the case of inn2, this will be rather surprising. In hindsight, it probably would have been better for INN and similar packages to manage their own users directly instead of having the news account in base-passwd, but that would have raised various other issues, and in any case it's too late now. As an upstream INN maintainer, I agree with this change from an upstream perspective and, unless Julien beats me to it, will incorporate it into the next upstream releases. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
