Bug#1023494: apt: package cache file is corrupted after upgrade from 2.5.2 to 2.5.4

[Shengjing Zhu <zhsj@debian.org>]

On Sat, Nov 5, 2022 at 8:58 PM Julian Andres Klode <jak@debian.org> wrote:
>
> On Sat, Nov 05, 2022 at 08:53:29PM +0800, Shengjing Zhu wrote:
> > Hi,
> >
> > On Sat, Nov 5, 2022 at 8:49 PM Julian Andres Klode <jak@debian.org> wrote:
> > >
> > > On Sat, Nov 05, 2022 at 08:08:41PM +0800, Shengjing Zhu wrote:
> > > > Package: apt
> > > > Version: 2.5.4
> > > > Severity: important
> > > > X-Debbugs-Cc: zhsj@debian.org
> > > >
> > > > Dear Maintainer,
> > > >
> > > > After upgrade to 2.5.4, `apt-cache --no-generate pkgnames ''` gives me:
> > > >
> > > > E: The package cache file is corrupted, it has the wrong hash
> > >
> > > Yes, this is of course expected. The version is hashed into the
> > > cache hash, and you told it to not generate a new cache, so it
> > > can't make any progress here.
> >
> > Could you elaborate "you told it to not generate a new cache"?
> > I don't see any special configuration there.
>
> You literally used --no-generate
>

Ok. However this is what is in the bash completion scripts.

I find the problem because apt's bash completion stops working today.
So users are expected to do an `apt clean && apt update` to regenerate
the cache after upgrading apt?

-- 
Shengjing Zhu