Simon,
While Python 2 may be deprecated, I don't think we can change the defaults
for master yet. The main issue is the packaging of Windows and Mac still
requires Python 2 (based on the discussion in [1]) because the Python 3
packages are not validated/existing yet. Until we have Windows and OSX
JP,
Are you running this on your 3.0 or 3.1 build of wxwidgets? That looks like
there is an issue with their autosize calculation not factoring in the
width of the sorting bitmap.
-Ian
On Thu, 7 Nov 2019, 14:37 jp charras, wrote:
> Le 06/11/2019 à 23:18, Mikołaj Wielgus a écrit :
> > Hello,
>
Please wait until the migration. I will make an announcement and update
Lauchpad to disable the bug tracker and add a link to the main page that
we have moved to gitlab. We are currently just testing the bug tracker
migration script. There are still a few things that need to be ironed
out
Simon,
Continue to use Launchpad for the time being. I don't believe we have
officially created the KiCad repository yet, so all that is being done
currently is testing leading up to the migration.
-Ian
On Sun, Nov 10, 2019 at 7:10 PM Simon Richter
wrote:
> Hi,
>
> On Sun, Nov 10, 2019 at
Hi,
On Sun, Nov 10, 2019 at 06:43:33PM +0100, Maciej Suminski wrote:
> Good catch, thanks! I think I have already found the bug, I will let you
> know after the next run is finished.
Quick question: if I have a new bug report, should I file it in LP or in
gitlab or wait until migration is done?
Hi,
This is version 4 of this patch.
Navigator now updates in real time when sheets are edited/removed/added.
Franck.
From 550f88483d598df41f38114fb4b24191f1442330 Mon Sep 17 00:00:00 2001
From: Franck Jullien
Date: Thu, 24 Oct 2019 19:07:01 +0200
Subject: [PATCH v4] [NEW] eeschema: Allow
Le dim. 10 nov. 2019 à 18:29, jp charras a écrit :
>
> Le 10/11/2019 à 17:33, Franck Jullien a écrit :
> > Le jeu. 7 nov. 2019 à 21:51, a écrit :
> >>
> >> From: Franck Jullien
> >>
> >> User can now decide to keep the hierarchy navigator open while working
> >> on a schematic. This behavior
On 11/10/19 5:54 PM, Seth Hillbrand wrote:
> On 2019-11-10 08:43, Seth Hillbrand wrote:
>
>> On 2019-11-10 08:33, Eeli Kaikkonen wrote:
>>
>>> OK. Would it be worth re-importing everything even for this test database
>>> to avoid false impressions?
>>>
>>> Eeli Kaikkonen
>>
>> What false
Le 10/11/2019 à 17:33, Franck Jullien a écrit :
> Le jeu. 7 nov. 2019 à 21:51, a écrit :
>>
>> From: Franck Jullien
>>
>> User can now decide to keep the hierarchy navigator open while working
>> on a schematic. This behavior can be configured in
>> eeschema->preferences->eeschema->Editing
To make sure that we are talking about the same thing, here is indeed a bug
report originally written by me in launchpad but attributed to some Fabien
in this new database:
https://gitlab.com/orsonmmz/kicad-bug-tracker/issues/7600 (screenshot
attached in case you see it differently).
su 10.
On 2019-11-10 08:43, Seth Hillbrand wrote:
> On 2019-11-10 08:33, Eeli Kaikkonen wrote:
>
>> OK. Would it be worth re-importing everything even for this test database to
>> avoid false impressions?
>>
>> Eeli Kaikkonen
>
> What false impression? Is there a report that is listed as being
I got a false impression that importing the bug database currently has some
problem because those reports which I opened seemed to be written
originally by some mysterious username, while the subsequent comments were
correctly attributed. This led to me asking about it here. These kinds of
false
On 2019-11-10 08:33, Eeli Kaikkonen wrote:
> OK. Would it be worth re-importing everything even for this test database to
> avoid false impressions?
>
> Eeli Kaikkonen
What false impression? Is there a report that is listed as being
created by different people in launchpad vs. GitLab?
Le jeu. 7 nov. 2019 à 21:51, a écrit :
>
> From: Franck Jullien
>
> User can now decide to keep the hierarchy navigator open while working
> on a schematic. This behavior can be configured in
> eeschema->preferences->eeschema->Editing options.
>
> Signed-off-by: Franck Jullien
> ---
>
> v2: fix
OK. Would it be worth re-importing everything even for this test database
to avoid false impressions?
Eeli Kaikkonen
su 10. marrask. 2019 klo 18.27 Seth Hillbrand (s...@kipro-pcb.com)
kirjoitti:
> On 2019-11-10 08:17, Eeli Kaikkonen wrote:
>
> Who is this original reporter "Fabien Corona
On 2019-11-10 08:17, Eeli Kaikkonen wrote:
> Who is this original reporter "Fabien Corona (drinasaur)" who created all the
> reports?
>
> Eeli Kaikkonen
Not all of the reports. Just a bunch of the recent ones prior to this
import. Here is one you created [1].
Click on the "Original
Who is this original reporter "Fabien Corona (drinasaur)" who created all
the reports?
Eeli Kaikkonen
su 10. marrask. 2019 klo 0.08 Maciej Suminski (maciej.sumin...@cern.ch)
kirjoitti:
> I have fixed all issues, taking into account the ones reported on the
> mailing list and Ian's 'Gitlab Issue
Hi Jeff,
On Sun, Nov 10, 2019 at 11:45:20AM +, Jeff Young wrote:
> I’ve pushed changed which I hope will fix the spacing problem (but I never
> got the test environment working on my Mac so I’m not 100% sure).
Looks good.
Simon
___
Mailing
Hi Simon,
I’ve pushed changed which I hope will fix the spacing problem (but I never got
the test environment working on my Mac so I’m not 100% sure).
Cheers,
Jeff.
> On 10 Nov 2019, at 09:28, Simon Richter wrote:
>
> Hi,
>
> we seem to have picked up two test failure reports[1]:
>
>
Hi,
we seem to have picked up two test failure reports[1]:
[Info] - check KI_TEST::SexprIsListOfLength( (SEXPR::SEXPR&) s_list, 5 ) has
passed
== [File] -
/var/lib/jenkins-agent/workspace/linux-kicad-head/src/qa/libs/sexpr/test_sexpr.cpp
== [Line] - 101
== [Context] Sexpr string conversion
20 matches
Mail list logo
