Hey! I prefer broken upgrades to get pulled anyway. Besides, packages are updated by unattended-upgrades in up-to 24 hours, so some users might have not gotten it yet. And there's also those not using undattended-upgrades. Let me demote it back to -proposed from -updates as well.
On Fri, 4 Dec 2020 at 10:00, Christian Ehrhardt <christian.ehrha...@canonical.com> wrote: > > On Fri, Dec 4, 2020 at 9:49 AM Lukasz Zemczak > <lukasz.zemc...@canonical.com> wrote: > > > > Hey Christian! > > > > This sounds bad indeed, let's see what Matthew has to say. In the > > meantime I have backed it out from both bionic-security and > > focal-security. > > Thank you > > > Should we also consider dropping it from -updates? > > Well, compared to other cases in this case we don't even yet have a > "ok this is a mess, but this is how you can resolve it afterwards to > work again". > Therefore I think pulling it from -updates as well makes sense until > Matthew had time to look at it in detail and give all-clear (or not). > > P.S.: you slightly raced vorlon who had a different assessment > [09:30] <vorlon> cpaelzer: well, by this point almost everyone will > have picked it up from security via unattended-upgrades so there's not > much point > But having it pulled for now is on the safe-side and we can re-instate > it at any time once we know more. > > > Cheers, > > > > On Fri, 4 Dec 2020 at 09:01, Christian Ehrhardt > > <christian.ehrha...@canonical.com> wrote: > > > > > > I was looking at 16 recently touched bugs. Of these a few needed a > > > comment or > > > task update but not a lot of work. Worth to mention are two of them. > > > > > > First we've had "one more" kind of conflicting mysql packages from > > > third party breaking install/upgrade of the one provided by Ubuntu. I > > > dupped it onto bug 1771630 which is our single place to unite all > > > those. > > > > > > > > > A recent sssd update (driven by SEG) seems to have regressed users > > > that now end in a hang. > > > I've pinged on [1], subscribed Matthew (and our Team) on [2]. I've > > > marked it regression-update and also pinged Matthew him via Chat. > > > Furthermore I've set him on CC on this mail. > > > @Matthew - once you've done your initial assessment would you mind > > > replying here with the next steps on this case please? > > > I've marked it prio high, if other triagers see more such reports > > > please mark it even critical then (in that case it is less likely to > > > be just one odd special setup) > > > The release is 21h ago, I'll ping ubuntu-archive (also on CC) if we > > > should - for now until clarified by Matthew - remove it from > > > -security. > > > > > > > > > [1]: > > > https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/comments/86 > > > [2]: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673 > > > > > > > > > -- > > > Christian Ehrhardt > > > Staff Engineer, Ubuntu Server > > > Canonical Ltd > > > > > > -- > > > ubuntu-archive mailing list > > > ubuntu-arch...@lists.ubuntu.com > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-archive > > > > > > > > -- > > Łukasz 'sil2100' Zemczak > > Foundations Team > > lukasz.zemc...@canonical.com > > www.canonical.com > > > > -- > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd -- Łukasz 'sil2100' Zemczak Foundations Team lukasz.zemc...@canonical.com www.canonical.com -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam