Bug#1032587: marked as done (UDD's upstream_metadata table may contain stale data?)
Your message dated Mon, 20 Mar 2023 11:25:08 +0100
with message-id <ZBg0hDPtWRq1EQXZ@an3as.eu>
and subject line Re: Bug#1032587: UDD's upstream_metadata table may contain stale data?
has caused the Debian Bug report #1032587,
regarding UDD's upstream_metadata table may contain stale data?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1032587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032587
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
User: qa.debian.org@packages.debian.org
Usertags: udd
Severity: normal
X-Debbugs-Cc: tille@debian.org
m trying to query UDD for upstream metadata, but upon running some
SELECTs on public.upstream_metadata I've noticed that it doesn't have
data for e.g. src:python-structlog, which I added to the package with
the 22.3.0-1 upload on 18 Feb 2023.
I asked about the refresh frequency in #debian-qa, to which Lucas
responded that's not 100% sure of the status and encouraged me to file a
bug here. He also noted there is no mention of upstream metadata in
https://udd.debian.org/udd-status.cgi and that maybe [the updater] is no
longer running.
This is my first attempt to query this data, so I hope this isn't an
operator error!
Thanks in advance,
Faidon
--- End Message ---
--- Begin Message ---
Hi Faidon,
the problem was caused by two reasons:
1. The cron job fetching machine readable data from Salsa that did
not finished (since mid-November last year :-((() Its now
finishing again since I've added a couple of try-excepts and also
increased delay times inside the job.
(Commits f66f428c, 755ee077, a51cf1cf, 7368031c in [1])
2. A broken description in one auto-generated packaging made the
actual UDD importer fail which is fixed as well[2]
The import works now on my local UDD clone and I've manually triggered
the importer job on udd.debian.org. I guess the mirror will feature
the update today evening latest tomorrow.
I'm closing the bug hereby not without thanking you again for the
report which helped tracking down the issue.
Kind regards
Andreas.
[1] https://salsa.debian.org/blends-team/website/-/commits/master
[2] https://salsa.debian.org/qa/udd/-/commit/bf567b388508aa72d25a137b4916cd386ee26159
--
http://fam-tille.de
--- End Message ---
Reply to: