Re: [UDD] Role of different upstream status tables (upstream versus dehs)
Hi,
On 26/05/15 at 20:28 +0200, Andreas Tille wrote:
> Hi,
>
> could anybody please explain the role of the different tables upstream
> and dehs which look quite similar but show different results:
>
> udd=> SELECT unstable_parsed_version, unstable_status from dehs where source = 'trimmomatic' ;
> unstable_parsed_version | unstable_status
> -------------------------+-----------------
> 0.32 | outdated
> (1 row)
>
> udd=> SELECT upstream_version, status from upstream where source = 'trimmomatic' ;
> upstream_version | status
> ------------------+------------
> 0.33 | up to date
> (1 row)
>
>
> The Blends tools are (currently!) using dehs (since it existed a long
> time). I realised that it was not updated since some time - the
> (random) example trimmomatic version 0.33 migrated to testing so the
> problem exists since >= 10 days. The code is obviously broken:
>
> udd@ullmann:/srv/udd.debian.org/udd$ ./update-and-run.sh dehs
> Traceback (most recent call last):
> File "/srv/udd.debian.org/udd//udd.py", line 86, in <module>
> exec "gatherer.%s()" % command
> File "<string>", line 1, in <module>
> File "/srv/udd.debian.org/udd/udd/dehs_gatherer.py", line 50, in run
> for e in pkgs:
> TypeError: 'NoneType' object is not iterable
>
> and the reason for this is that the CGI that should deliver the needed
> data returns zero bytes:
>
> udd@ullmann:/srv/udd.debian.org/udd$ wget http://qa.debian.org/cgi-bin/udd-dehs -O /srv/udd.debian.org/mirrors/dehs.txt
> --2015-05-26 18:24:01-- http://qa.debian.org/cgi-bin/udd-dehs
> Resolving qa.debian.org (qa.debian.org)... 2001:41c8:1000:21::21:28, 5.153.231.28
> Connecting to qa.debian.org (qa.debian.org)|2001:41c8:1000:21::21:28|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: https://qa.debian.org/cgi-bin/udd-dehs [following]
> --2015-05-26 18:24:01-- https://qa.debian.org/cgi-bin/udd-dehs
> Connecting to qa.debian.org (qa.debian.org)|2001:41c8:1000:21::21:28|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 0 [text/plain]
> Saving to: `/srv/udd.debian.org/mirrors/dehs.txt'
>
> [ <=> ] 0 --.-K/s in 0s
>
> 2015-05-26 18:24:09 (0.00 B/s) - `/srv/udd.debian.org/mirrors/dehs.txt' saved [0/0]
>
>
> I'm wild guessing that this might be somehow connected to a Wheezy ->
> Jessie upgrade at qa.debian.org. But more generally speaking: Do we
> need to fix this or should we rather drop this table in favour of
> upstream which is properly updated. I admit I would really love if
> changes in UDD would be propagated more prominently to enable users to
> adapt their code accordingly.
>
> If somebody could explain the role of these competing tables I could
> decide whether adapting the Blends code or filing a bug report would
> be the appropriate course of actions.
The dehs table was trying to mirror the data provided by DEHS.
Unfortunately, DEHS died a long time ago, so the 'upstream' gatherer
(and table) were created.
I recommend that you switch to using 'upstream' instead of 'dehs'.
I've just emptied the dehs table to make it clearer that it should not
be used.
Lucas
Reply to: