I rewrote my spec as you can see here https://github.com/ValorNaram/goeasylinux/blob/master/package%20management/package%20install.md and noted "pkcon" as a already implemented solution in all major linux distributions.So packaging a symlink isn't needed anymore.Thank you all for your time, best wi
Hi,
at work we have a large fleet of Debian machines, but also more than
200k user accounts with no reuse and somewhat painful rename
experiences. Obviously an increasing number of accounts leads to a much
increased risk of collisions with system users as created by Debian
packages.
Of cour
On 2019-02-09 13:10, Philipp Kern wrote:
> How do others deal with this problem?
In my company, we use leading underscore for all non-human
accounts. Human accounts get lower-case ASCII letters only.
Also, we use the same uid/gid for the same human user on all
machines (1000 + something unique, e
❦ 9 février 2019 13:10 +01, Philipp Kern :
> Some core packages recently adding system users resorted to names like
> systemd-$daemon and _apt, which both address my concerns - as you can
> come up with simple rules like "no user might include [-_] in their
> username". On the other hand I know
On Sat, 09 Feb 2019 at 13:10:27 +0100, Philipp Kern wrote:
> Obviously an increasing number of accounts leads to a much increased risk of
> collisions with system users as created by Debian packages.
This topic comes up every so often and doesn't ever seem to come to a
conclusion.
One complicatin
Hi!
On Sat, 2019-02-09 at 13:10:27 +0100, Philipp Kern wrote:
> at work we have a large fleet of Debian machines, but also more than 200k
> user accounts with no reuse and somewhat painful rename experiences.
> Obviously an increasing number of accounts leads to a much increased risk of
> collisio
On Sat, Feb 09, 2019 at 01:34:41PM +0100, Vincent Bernat wrote:
> This is a recurring topic. See:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248809
in addition to this -policy bug there is also #399028
"developers-reference: best practices to create and delete system
accounts" which sugg
On Mon, Feb 04, 2019 at 02:51:45PM +0100, Andreas Beckmann wrote:
> emacs has had a bad history (from piuparts point of view) of providing
> clean upgrade paths to newer versions. All versioned emacs packages were
> co-installable and there were no transitional packages provided ever to
> ensure up
I'd like to support the _user convention as well.
It works well as packages move around between distributions and things
get upstreamed.
Hello,
On Sat 09 Feb 2019 at 01:51PM +01, Guillem Jover wrote:
> To that effect I sent a patch to adduser to allow these in #521883,
> but it seems that's stuck. :/
>
>> How do others deal with this problem? Could someone think of a viable
>> approach on how to approach this from a policy side?
>
Sam Hartman writes:
> I'd like to support the _user convention as well.
> It works well as packages move around between distributions and things
> get upstreamed.
Agreed. I think we should just write this up as the recommended approach
for all new system users in Policy.
(Changing the existing
On Feb 09, Sean Whitton wrote:
> ISTM to me we have a consensus, at least, that new packages with system
> users should use the underscore prefix convention. There isn't a
> consensus on what to do about old packages, but Policy can be written in
> such a way to refer only to new packages with s
On 2019-02-09.13:10, Philipp Kern wrote:
> How do others deal with this problem? Could someone think of a viable
> approach on how to approach this from a policy side?
systemd has an elegant solution for this problem, which I would like to
see more widely adopted:
http://0pointer.net/blog/dynamic
13 matches
Mail list logo
