On 01/02/26 at 12:17 +0000, Sebastien Bacher wrote: > > > > The script in question already uses launchpad's API (through launchpadlib) > > so I think things are fine (and future-proof). > > > > https://salsa.debian.org/qa/udd/-/blob/master/scripts/launchpad-ubuntu-changes?ref_type=heads > > > > Hum, indeed that seems fine, I need to check again with the launchpad team > because what they told me as > > > They aren't hitting our API; they are hitting our web frontend > > They are resolving 2620:2d:4000:1009::f3 and 2620:2d:4000:1009::3ba which > corresponds to our web frontends > > To be clear, the API frontends should resolve to 2620:2d:4000:1009::10e > and 2620:2d:4000:1009::330
This might be because the script uses archive.getPublishedSources(), and then changesFileUrl(), that points to the web frontend, e.g. https://launchpad.net/ubuntu/+archive/primary/+files/fenics-basix_0.10.0.post0-2build1_source.changes That URL then redirects to https://launchpadlibrarian.net/845605766/fenics-basix_0.10.0.post0-2build1_source.changes > > For various reasons, there are still 246 sources in resolute with no > > matching upload in UDD. It could probably be fixed by re-importing all > > uploads from launchpad, but I'm not sure it's worth it. SQL query to > > list those: > > udd> select source, version, release > > from ubuntu_sources s > > left join ubuntu_upload_history uh using (source, version) > > where uh.source is null and s.release = 'resolute'; > > I will try to check that. It is not important but also it would be nice > have complete data. I wouldn't run a complete re-import of resolute uploads > for that though because we are rebuilding the complete archive this cycle > so that's a lot of data to process again... To be clear, the uploads are only missing in UDD (not launchpad) so it's a UDD-only problem. Lucas
