Oh yeah this is a weird situation. :) I guess it would normally make
sense to re-review if the potentially older code was different than what
was previously approved.
In this case, the code is the same as the newer releases? So I normally
would expect a MIR rubber stamp.
BUT... the MIR team is not happy with snapd these days. See bug
1658181, which is a big security and MIR policy violation, implemented
just a few months after getting MIR approval last time around.
(Presumably done specifically to support trusty? I don't know, because
no one that knows why it was done has commented.)
So bug 1658181 is a blocker. Though oddly, for trusty specifically an
exception might be able to be made because the golang packages you need
may not be in the archive. But for all *other* releases, it's
definitely a blocker, after the fact. But that's not what this bug is
about... I'll assign to security team to see what they want to do about
supporting this.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660550
Title:
[MIR] snapd in trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1660550/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
