On Fri, 9 Jan 2015 12:47:28 -0800 Cameron Norman
<camerontnor...@gmail.com> wrote:
> On Fri, Jan 9, 2015 at 12:03 PM, László Böszörményi
(GCS)
> <g...@debian.org> wrote:
> > On Fri, Jan 2, 2015 at 8:33 PM, Cameron Norman
<camerontnor...@gmail.com> wrote:
> >> It hardcodes them as 175. The uid was not taken, but the gid was
so the
> >> package installation failed. Funnily enough, I was trying to fix
#767028 at
> >> the time.
> > Can you confirm that #767028 happens due to udevadm failure
because
> > /proc is not mounted?
> > What has gid 175 on your system?
>
> Not at my comp (will get back to you when I am), but I am pretty sure
> it was "radicale".
>
> I actually did not experience #767028 on a system that does have
/proc
> mounted, so it is likely. Again, I will double check later today.
I said I would check but I never followed up on that :). I already
deleted the group so I could not see who it was. I could not umount
/proc in a container, and I ended up getting too lazy to set up a
chroot (yes I know it is pretty easy, I am just kind of busy and
tired). That said your hypothesis that it is a udevadm failure seems
extremely likely.
Best regards,
--
Cameron Norman
