touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Simon McVittie [2015-10-29 11:55 -0000]:
> > systemd doesn't inself create /etc/machine-id when missing, which it
> should.
> 
> I think the solution to "my system-imaging setup isn't working" is to
> get that bug (presumably a systemd bug?) fixed - this one is rather
> minor by comparison. Do you have a correct bug# for it?

Indeed, that would interest me as well.

> I'd be happy to review a patch upstream that made
> _dbus_read_local_machine_uuid() with create_if_not_found=TRUE (i.e. the
> implementation of dbus-uuidgen --ensure) symlink the machine ID rather
> than copying it.
> 
> Alternatively, the postinst could create the symlink if /etc/machine-id
> exists and has syntactically valid contents, or run dbus-uuidgen
> --ensure if not.

Either approach sounds fine to me. Changing dbus-uuidgen seems a bit
more universal as then distros don't need to all do the same postinst
change and /etc/machine-id validity check (which dbus-uuidgen already
does), but either way it should be simple enough.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1508697

Title:
  dbus-uuidgen --ensure: Symlink instead of copy existing /etc/machine-
  id

Status in dbus package in Ubuntu:
  Triaged

Bug description:
  If you do a Wily desktop install, /var/lib/dbus/machine-id is a
  symlink to /etc/machine-id.

  If you do a Wily server install, /var/lib/dbus/machine-id is a file
  containing the same value as /etc/machine-id.

  Minor issue, but still a weird inconsistency between Ubuntu desktop
  and server.

  Thanks!

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