packages.debian.org shows outdated package versions for Unstable and
Testing. It shows version from between 1 and 2 weeks ago for those
recently uploaded packages I checked.

Is there something no more syncing package databases or no more
regenerating content?

Some examples:

1) hugo

https://packages.debian.org/search?keywords=hugo shows me the
following version of hugo in Unstable to me:

  sid (unstable) (web): Fast and flexible Static Site Generator written in Go
  0.96.0-1+b1: amd64 arm64 armel armhf i386 mips64el mipsel ppc64 ppc64el riscv64 s390x

And https://packages.debian.org/sid/hugo shows me:

  Package: hugo (0.96.0-1 and others)
  […]
  Architecture	Version	Package Size	Installed Size	Files
  amd64	0.96.0-1+b1	11,200.4 kB	49,651.0 kB	[list of files]

But according to https://tracker.debian.org/pkg/hugo, this is outdated
since at least 2022-06-04, i.e. for more than 5 days (and less than 5
weeks) as of now, because all these uploads of the past few days are
not shown on packages.debian.org:

[2022-06-08] Accepted hugo 0.100.1-1 (source) into unstable (Anthony Fok)
[2022-06-07] Accepted hugo 0.99.1-1 (source) into unstable (Anthony Fok)
[2022-06-05] Accepted hugo 0.98.0-1 (source) into unstable (Anthony Fok)
[2022-06-04] Accepted hugo 0.97.3-1 (source) into unstable (Anthony Fok)

2) libwww-dict-leo-org-perl

https://packages.debian.org/sid/libwww-dict-leo-org-perl and
https://packages.debian.org/bookworm/libwww-dict-leo-org-perl both
show:

  Package: libwww-dict-leo-org-perl (2.02-2)

But I did one upload on 2022-06-04 which already migrated to Testing
more than a day ago, see
https://tracker.debian.org/pkg/libwww-dict-leo-org-perl:

  [2022-06-08] libwww-dict-leo-org-perl 2.02-3 MIGRATED to testing (Debian testing watch)
  [2022-06-04] Accepted libwww-dict-leo-org-perl 2.02-3 (source) into unstable (Axel Beckert)

3) linux-image-*-amd64-unsigned, linux-doc and src:linux

https://packages.debian.org/sid/linux-image-5.17.0-2-amd64-unsigned is
there (uploaded 2022-05-11), but no more in Sid since 2022-05-27.

https://packages.debian.org/sid/linux-image-5.18.0-1-amd64-unsigned
gives "No such package". And there even was a
linux-image-5.17.0-3-amd64 in Unstable in between, uploaded on
2022-05-27, which was more or less 2 weeks ago.

https://packages.debian.org/sid/linux-doc as well as
https://packages.debian.org/source/sid/linux also show 5.17.6-1 and
miss these uploads to Unstable:

  [2022-06-06] Accepted linux 5.18.2-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
  [2022-05-27] Accepted linux 5.17.11-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)

4) libdevel-cover-perl

https://packages.debian.org/search?keywords=libdevel-cover-perl shows
1.36-2+b2 for Unstable and Testing, but actually these should be shown
(citing from https://tracker.debian.org/pkg/libdevel-cover-perl):

  [2022-06-09] Accepted libdevel-cover-perl 1.38-1 (source) into unstable (Axel Beckert)
  [2022-06-08] libdevel-cover-perl 1.37-1 MIGRATED to testing (Debian testing watch)
  [2022-06-05] Accepted libdevel-cover-perl 1.37-1 (source) into unstable (gregor herrmann)

Hi Adam,

Adam D. Barratt wrote:

Oops.

Thanks!

		Regards, Axel

# bcc control@bugs
user www.debian.org@packages.debian.org
usertags 1012598 + packages
thanks

Hi,

It looks like a generation process had got stuck. Unfortunately, that
was sufficiently long ago that all of the logs that might have
suggested the cause of the issue have already rotated out.

I've rebooted the server so I guess someone[tm] will need to keep an
eye on things during / after the next cron run.

Regards,

Adam
(with DSA hat on, no particular connection to packages.d.o otherwise)

Hi,

Adam D. Barratt wrote:

Seems to have fixed the recent data lag:
https://packages.debian.org/sid/hugo is now showing the expected
0.100.1-1 version. Thanks!

I'm though leaving the bug report open in case someone wants to dig
into the cause of this issue.

		Regards, Axel

Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie
Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran,
Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun.

Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie
für weitere Details.