I saw this in the unapproved queue and have the following questions: What's the reason for singling out the libc6 reboot-required reason rather than asking for *any* reboot-required?
If you do strongly want to keep it limited to libc6 only, wouldn't opening the file in the python code instead of opening a grep subprocess be faster? I'm semi-convinced by your reasoning on untranslated strings, but if we could make some effort towards getting as many as possible I'd be happier, such as mailing the translator list so it gets in the next langpack refresh in bionic. (And it seems to me like if the string could avoid mentioning "libc6" that would be more friendly to any future tweaks in this area.) Is it right to say that this could equally be a 0-day SRU and so this upload isn't important for the release itself - there's no need to rush it in for final freeze? I'll reject from the queue for now, but someone else could find it in the rejected queue and accept if that is the decision. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797209 Title: do-release-upgrade should block release upgrades in some circumstances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1797209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
