> I think no-change building dconf on questing just creates extra work later for
the Desktop Team when they need to sync dconf in from Debian.
No, a no-change rebuild would have a version of 0.40.0-5build1, which
will get autosync'd over next time there is a Debian upload (and when
it's not past Debian import freeze). Hence, no extra work is created,
and therefore I don't think there is sufficient justification for not
fixing plucky.
** Changed in: dconf (Ubuntu Plucky)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2072586
Title:
Running "dconf update" with different umask affects the permissions of
dconf databases in /etc/dconf/db/
To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/2072586/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
