[09:56] <mamarley> ricotz: Because of https://bugs.launchpad.net/bugs/1589006, I reverted the snappy patch in the nvidia-364 and nvidia-367 packages.  (It was breaking X for a number of people.)  I will answer all the emails from people complaining about the bug when attempting to upgrade.
[10:27] <mamarley> OK, I have responded to everyone who emailed the team so far.
[10:37] <ricotz> mamarley, hi, I see :\
[10:38] <ricotz> mamarley, any reports for 361?
[10:39] <mamarley> ricotz: Yes, but those are going to the bug report for the official archive package.  That was what I linked above.
[10:40] <mamarley> Those are from people who are using the -proposed repository, which they aren't really supposed to be doing.
[10:40] <ricotz> mamarley, ah alright, I don't have snap installed here
[10:40] <ricotz> I was wondering why I am not seeing problems
[10:41] <mamarley> ricotz: Yeah, it doesn't always happen, which is weird.  I don't have snapd installed on any of my systems and it didn't affect my desktop, but it did affect my laptop.
[10:41] <mamarley> (At least the uninstall problem.  It didn't prevent X from starting on any of my systems.)
[10:42] <ricotz> ok
[10:43] <ricotz> mamarley, reverting the change doesnt solve the upgrade problem though which was reported
[10:44] <mamarley> Correct, which is why I am responding to user emails and telling them how to work around the problem.
[10:44] <ricotz> good
[10:46] <mamarley> There is actually a secondary problem that seems to be occurring in a number of cases as well.  The command to start or stop the service is getting executed from the pre/post inst/rm scripts from a different package from the one that actually has the file, so they are getting errors about the unit not being loaded.