> the problem does not exist on 18.04.

OK, so I'll mark this bug as Triaged as I think it's clear what
behaviour needs to change. I'm setting this as Importance: Low though,
since I think this affects only unusual end-user configurations of
Ubuntu. I don't expect the Ubuntu server team to work on this any time
soon, but if you can provide a patch and help drive the QA required to
get a fix into 16.04, we'd be happy to take it.

> ...which does nothing to get ubunut's LTS samba package to not give
this message.

In Ubuntu we can cherry-pick an upstream fix (or come up with our own
fix) and apply it to 16.04. How practical this is depends on the exact
fix.

If this bug previously existed upstream and has since been fixed in a
newer upstream release, it would be helpful to find the upstream bug
reference (if it exists) and the upstream VCS commit(s) that fix the
problem.

If you can volunteer your help, please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for details. The
first step though is to figure out a patch that works for the samba
package in Ubuntu 16.04, which can be done independent of Ubuntu
processes.

** Changed in: samba (Ubuntu)
   Importance: Undecided => Low

** Changed in: samba (Ubuntu)
       Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719889

Title:
  internal-use-only SIDs being mapped to GIDs on users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1719889/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to