On 10 September 2017 at 08:55, ruffsl <roxfox...@gmail.com> wrote: > Hello Dan, just following up. Any new ideas? I suppose I can modify our > official docker hub manifest to omit trusty for armhf to at least get > xenial images out of our farm.
Do not omit trusty for armhf, there are production systems that depend on it. Apart from not having correct security stanzas are there any other side-effects? Note it is mostly harmless as -updates is enabled by default, and all security updates are published in both -security and -updates. Thus "wrong" security stanza, is mostly harmless. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711735 Title: source.list for armhf includes trusty-security which does not exist for arm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1711735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
