From bloodhound-dev-return-1571-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Sun Jan 13 13:59:44 2013 Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9A25E9D9 for ; Sun, 13 Jan 2013 13:59:44 +0000 (UTC) Received: (qmail 90866 invoked by uid 500); 13 Jan 2013 13:59:44 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 90782 invoked by uid 500); 13 Jan 2013 13:59:43 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 90744 invoked by uid 99); 13 Jan 2013 13:59:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jan 2013 13:59:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates 209.85.210.170 as permitted sender) Received: from [209.85.210.170] (HELO mail-ia0-f170.google.com) (209.85.210.170) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jan 2013 13:59:36 +0000 Received: by mail-ia0-f170.google.com with SMTP id k20so2773788iak.1 for ; Sun, 13 Jan 2013 05:59:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=FHG3evJBUNemEaHXxCgH575jqa2iMhB7ULDxHoUA73U=; b=B8Z5nqkWS6ajqfWm7I/xhVk6SGkEneY9LqCsg8E596t8LZF8pnIaY5z13aIodhtMQN 9fry7oXB2F0IxqCr2l0u0NZaQz88urDzHBqdMIS6HMotMWIDV0YxiS0E+AVqGdwWPN2b OhGlSFnJvtdp7eqvrn8RySTI9kX17UyuPKODo0z70KCct6hTnwMhleZvkATAo7foryRt hnljIVsfbCuM2WQGHYCBGgGnuenPUFv+R79Jxlp/DWPtvVYIywiEkXG6axBwFjJYADCw pwwrtQFGNsMoAIk2pKkSSZEWEK2uh/Zo4UAuQ8l4w+y/utnDR1nrg6QgVfuResJ3dMxj z6Kg== MIME-Version: 1.0 X-Received: by 10.50.46.161 with SMTP id w1mr4236219igm.40.1358085555469; Sun, 13 Jan 2013 05:59:15 -0800 (PST) Received: by 10.50.1.44 with HTTP; Sun, 13 Jan 2013 05:59:15 -0800 (PST) In-Reply-To: <50F28DAB.5090905@digiverse.si> References: <055.55b84508f6fcc1a8cc545a03456faa21@incubator.apache.org> <070.15b8ebe71bafa7ae651d57d105b756d7@incubator.apache.org> <50D42A23.20005@digiverse.si> <50ED4B83.7050208@digiverse.si> <50F033E2.4050509@digiverse.si> <50F28DAB.5090905@digiverse.si> Date: Sun, 13 Jan 2013 08:59:15 -0500 Message-ID: Subject: Re: [Apache Bloodhound] #115: Product-specific settings From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 1/13/13, Jure Zitnik wrote: > On 1/13/13 7:07 AM, Olemis Lang wrote: >> On 1/11/13, Jure Zitnik wrote: >>> On 1/10/13 4:15 AM, Olemis Lang wrote: >>> >> [...] >>>>> I started integrating ProductEnvironment with the database proxy >>>>> (#288), >>>> good . >>>> >>>>> environment factory (#322) >>>> I'll take a look to see what's been done about this ... is there >>>> anything already in svn repos ? >>>> >>>>> and global hooks (#323). >>>>> >>>> :) >>> All the work done in integrating #115 with #288 and work done on #322 >>> and #323 is in the svn repo on bep_0003_multiproduct branch. >>> >> Is this usable your side ? I ask because >> [...] >> >> "/path/to/bloodhoundbloodhound_multiproduct/multiproduct/model.py", >> line 88, in insert >> from trac.bloodhound import TRANSLATE_TABLES >> ImportError: No module named bloodhound >> >> ---------------------------------------------------------------------- >> Ran 2 tests in 8.896s >> >> FAILED (errors=2) >> [...] > Missed that one when refactoring the code, r1432576 should fix that. ok thnx > Even after this tests are still failing in env.get_known_users with > IntegrityError: column name is not unique ... ok . Even if that's the case , now if I write new test cases then I should be able to run the test suite ... and build patches against bep_0003_multiproduct branch . ;) [...] -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: