Two packages 'kept back' after latest apt update on 22.04

[Walt Mankowski]

On Sat, Jul 30, 2022 at 09:14:54AM +0100, Chris Green wrote:
> On Fri, Jul 29, 2022 at 05:03:15PM +0200, Oliver Grawert wrote:
> > hi,
> > 
> > Am Freitag, dem 29.07.2022 um 15:40 +0100 schrieb Chris Green:
> > > 
> > > Is there just a minor dependency problem in 22.04 which will get
> > > fixed in
> > > due course or have I got something broken (it's the same on two
> > > different
> > > systems).
> > 
> > this is the new (since 21.10 IIRC) "phasing" feature [1] of the ubuntu
> > archive and apt ... you can check if a package is phased with "apt
> > policy" like below ... 
> > 
> > just wait, it will eventually come down the drain ...
> > 
> > $ LC_ALL=C apt policy language-pack-gnome-en-base 2>/dev/null|grep
> > phased
> >      1:22.04+20220721 500 (phased 30%)
> > $
> > 
> Ah, thank you, so there's nothing wrong at my end! :-)

I was thinking the same thing! But I'm still confused. I've been
running 22.04 since April, and before that I ran 21.10. Yet the first
I ever saw this happen was over the weekend.

I have two questions:

* Why did this suddenly start a few days ago?

* Having the packages held for phasing appear in `apt list
  --upgradable` together with all the other packages that are NOT held
  for phasing seems really confusing to me. Personally I'd much rather
  have them not appear in that list at all until they're ready to be
  installed. Is there an option to app to enable that?

Walt