Hi Nilesh, On 22/10/25 at 20:57 +0530, Nilesh Patra wrote: > On 22/10/25 12:16 am, Lucas Nussbaum wrote: > > This still happens with the following packages: > > Are we sure that the runs happened with latest lintian (and appstream) > version? Please see below: > > > lucas@ullmann:~$ psql service=udd -c "select distinct source, version from > > lintian_logs where message != '' and message ~ 'mapping'"; > > source | version > > ---------+----------------- > > angband | 1:4.2.5+dfsg1-3 > > Salsa CI indicated the failure you point to in the past: > https://salsa.debian.org/games-team/angband/-/jobs/7169907 > But I just re-ran the pipeline and it is successful now, see > https://salsa.debian.org/games-team/angband/-/jobs/8485654 > > > qps | 2.11.1-1 > > The same is true for this package as well. > > Past failure is at https://salsa.debian.org/lxqt-team/qps/-/jobs/8002752 > > But The latest salsa CI run on qps that run 3 weeks ago emitted no warning: > > https://salsa.debian.org/lxqt-team/qps/-/jobs/8368919 > > My approximate guess is that these were failing with appstream version > 1.0.6-1 and now work fine with 1.0.6-2. > > I tried on my local machine as well, and I get no mapping warnings. Could you > please consider > to double-check this? > > Maybe re-run these jobs with latest packages and make UDD consume that?
Ah, I see what you mean. the machine that runs those checks uses Debian stable, with appstream/1.0.5-1. I manually built appstream/1.0.6-2 and it works fine now, so yes, I think that the bug can be closed. It's probably not needed to depend on appstream >= 1.0.6-2 since there are very few packages affected and it's useful to be able to install lintian on stable. Lucas
