[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Thermometer not updating

Hi Bas,

On Thu, Oct 17, 2013 at 11:21:17PM +0200, Sebastiaan Couwenberg wrote:
> On 10/17/2013 09:49 PM, Andreas Tille wrote:
> > Yes, taht's what I mean.  There is a table new_packages which is queried
> > for the tasks pages but not for the thermometer.  I have just not seen
> > any need to respect this - but it is no big problem to implement it.
> > 
> >> I'll get back to you when I have a patch.
> > 
> > :-)
> I've chosen to include a NEW column in the thermometer after all. And
> gave it its own color (medium purple), that doesn't conflict with the
> other color usages.
> There is a change to for the blends website, which I've already pushed
> to git.debian.org:
>  blends/website: Also include packages in NEW in the thermometer.
> http://anonscm.debian.org/gitweb/?p=blends/website.git;a=commitdiff;h=15ae65ffa76400ca620d9bad302909224ecdaedf

Cool!  Many thanks for the patch.  Unfortunately it is really seldom
that people provide patches to the Blends tools and thus I'm really
happy about it!  I have upgraded the code on Alioth accordingly.

However, we were wrong with the assumption about freexl that it was just
a cron job we need to wait for:  The problem was actually in the tasks
file.  The syntax is the same as in debian/control files where you are
not allowed to have more than one "Depends:" per paragraph.  I commited
a patch with two additional newlines which should finally fix the issue
(after next cron job).

May be some additional check / warning inside the tasks file parser
might make sense to avoid such mistakes.

Another thing about your thermometer patch:  It is only for the Debian
GIS thermometer - the Ubuntu GIS thermometer does not contain the
package in new.

> And another changes for UDD to not consider packages in NEW as
> prospective. As I'm not a member of collab-qa and cannot push the
> change, it currently lives in my person git repo:
>  http://git.linuxminded.nl/?p=collab-qa/udd;a=commitdiff;h=68936658170e695d04f651bc84c9c12d9234bd3c

That's also cool.  I noticed when applying this we need to make sure
that the following impoerters:

   ftpnew, blends-prospective and blends-metadata

need to be run in exactly this sequence and so I organised this

> > Having a local UDD copy comes quite handy if you work with the Blends
> > framework. 
> Indeed it does. And it's fortunately not as large as some of the GIS and
> OSM databases.


> I haven't looked into FreeXL yet, for now I only have the NEW packages
> change.

See above - this should be fixed now.  You might like to inspect your
recent edits for other missing newlines.

Kind regards



Reply to: