[Piuparts-devel] problems with the new detect well known problems

[Holger Levsen]

Hi Dave,

On Sonntag, 1. Juni 2014, Dave Steele wrote:
> These both look like a misconfigured install - no module on the python
> path, and no known-problems confs in the known_problem directory. I'm
> seeing neither on my package-based install of current develop.

hmm, I'm guessing its the missing known-problems conf then.

OTOH: it doesnt fail like this when running from cron.
 
> My test tree is way out of date, but I have a kpr for
> stone_2.3.e-2+b1, with a non-unclassified entry. Is make processing
> @sharedir@ properly?

how to tell?

> > Third: looking at the code, I've seen that all those ISSUE=(0|1)
> > definitions in known_problems/*.conf have become obsolete and should be
> > removed. I just haven't done this as I dont want to interfere with
> > already existing branches/commits.
> 
> ISSUE predates me. It looks like it has never been used. It's purpose
> may be obsoleted by the WHEREs, which started to be added in 2011.
> ISSUE looks like a a straightforward proxy for replacing the current
> tpl name dependency in create_and_link_to_analyses(sp)(). I wouldn't
> delete them until the integration of dwke into piuparts-report is
> complete, and either WHERE or ISSUE is used to select tpl's (or
> equivalent) for inclusion into the report.

what's missing? do you have commits to pick?


cheers,
	Holger

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20140601/a35fb552/attachment.sig>