Re: [Kicad-developers] 5.1.5 release status

[Carsten Schoenert]

Hi,

Am 21.10.19 um 23:16 schrieb Ian McInerney:
> We also seem to have assertions enabled in the Debian build (there have
> been two reports from users [1], [2]). Is this something we control as
> well, or is the the distribution packaging forcing them on?

the Debian build configuration is visible in the GitLab repo for KiCad
on Salsa.

https://salsa.debian.org/electronics-team/KiCad/kicad
https://salsa.debian.org/electronics-team/KiCad/kicad/blob/debian/sid/debian/rules

I'm happily taken any patches if provided.

I personally haven't seen these asserts.

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Issues building PCBNew on Windows10/Msys:fatal exception

[Brian Piccioni]

Wayne

Thanks for the additional information. I mentioned the compile warnings because 
they appear to be different from the ones I got when I compiled 32 bit.

As for MSVC, I am a big fan and can see the benefits of moving to it. One 
advantage was that you wouldn’t have to install MSYS2 and all the other issues 
associated with that such as keeping it updated and in sync with the 
distributions. 

Thanks again

Brian 

From: Wayne Stambaugh
Sent: October 21, 2019 10:31 AM
Subject: Re: [Kicad-developers] Issues building PCBNew on Windows10/Msys:fatal 
exception

Brian,

On 10/21/19 9:24 AM, Brian Piccioni wrote:
> I'm updating this email in case somebody else has a similar problem.
> 
>  
> 
> I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad.
> It appear to run fine, except when I run PCBNew from a mingw64 terminal
> I get
> 
>  
> 
> $ pcbnew
> 
> C:/msys64/mingw64/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> UserWarning: wxPython/wxWidgets release number mismatch
> 
>   warnings.warn("wxPython/wxWidgets release number mismatch")

You should always see this warning.  The msys2 wxPython release is 3.0.2
and the wxWidgets release is 3.0.4 which causes the version mismatch.
Again, AFAIK, there this does not create any issues other than the fact
that wxPython is dead and has been replaced with wxPhoenix.  wxPhoenix
is wxPython for Python 3.  Unfortunately, the wxPython folks broke the
build scripts for wxPhoenix which means that you cannot build it on
msys2.  This *is* going to be a problem in the not too distant future
for windows users unless we either fix the wxPhoenix build scripts for
msys2 or switch to the free version of msvc to create windows builds.  I
prefer the former but we may not have any choice depending on manpower.

> 
>  
> 
>  
> 
> Interestingly, compiling does not generate "release number mismatch"
> warnings as happened when I did a 32 bit build.
> 
>  
> 
> I do, however, get these warnings:
> 
>  
> 
> C:\kicad-source\pcbnew\..\include\common.h(357) : Warning 317:
> Specialization of non-template 'hash'.
> 
> C:\kicad-source\pcbnew\..\include\common.h(365) : Warning 317:
> Specialization of non-template 'less'.
> 
> class_board.h(45) : Warning 315: Nothing known about 'std::unique_ptr'.

These are known issues with the code generated by SWIG to build the
Python scripting module.  AFAIK, they do not present any issues.

Cheers,

Wayne

> 
>  
> 
>  
> 
> (these are the only warnings I get compiling all of Kicad).
> 
>  
> 
> I will recompile wxPython and see if the PCBNew warnings go away though
> it is not pressing as everything works.
> 
>  
> 
> Thanks again
> 
>  
> 
> Brian
> 
>  
> 
> *From: *Wayne Stambaugh 
> *Sent: *October 20, 2019 10:09 AM
> *To: *kicad-developers@lists.launchpad.net
> 
> *Subject: *Re: [Kicad-developers] Issues building PCBNew on Windows
> 10/Msys:fatal exception
> 
>  
> 
> Hi Brian,
> 
>  
> 
> There is a long litany of things that can go wrong with msys2 builds but
> 
> I do not believe that the wxPython/wxWidgets mismatch is the problem.
> 
> Typically when I see issues like this, there has been a new gcc version
> 
> released and only one of the two dependency libraries have been compiled
> 
> with the new compiler which causes issues.  It's been a while but the
> 
> last time this happened, I had to recompile the wxPython package.  I
> 
> also noticed you are attempting to use 32 builds for debugging.  I
> 
> highly recommend that you debug using 64 bit builds.  Debug builds on
> 
> msys2 are massive and you will likely run into memory limit issues.  I
> 
> hope this helps.
> 
>  
> 
> Cheers,
> 
>  
> 
> Wayne
> 
>  
> 
> On 10/19/19 5:36 PM, Brian Piccioni wrote:
> 
>> Sorry if this is a bit long and thanks in advance for the help. I
> 
>> decided to move to a new laptop and create a debug version of Kicad so I
> 
>> can work on integrating my software. I believe I carefully followed the
> 
>> build instructions I suspect this may be related to a version mismatch
> 
>> but I don’t know how to fix it.
> 
>>
> 
>>  
> 
>>
> 
>> I installed Msys2, downloaded Kicad source and compiled a debug build.
> 
>> It compiled without errors but I get a warning
> 
>>
> 
>>  
> 
>>
> 
>>
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> 
>> UserWarning: wxPython/wxWidgets release number mismatch
> 
>>
> 
>>      warnings.warn("wxPython/wxWidgets release number mismatch")
> 
>>
> 
>>  
> 
>>
> 
>> I get the same error building the release and debug versions and the
> 
>> release version appears to work fine, except for complaints about
> 
>>
> 
>> version mismatch.
> 
>>
> 
>>  
> 
>>
> 
>> However, with the debug build I can run Kicad and invoke eeSchema and
> 
>> all the other applications from the Kicad menu except
> 
>>
> 
>> PCBNew and  the symbol editor. When I run these, I get errors:
> 
>>
> 
>>  
> 
>>
> 
>> 

Re: [Kicad-developers] Minimum Boost version

[Jon Evans]

On Mon, Oct 21, 2019 at 5:53 PM Diego Herranz 
wrote:

>
> It looks like by the time 6.0 is out, Ubuntu 16.04 may still be officially
> supported. Just something to have in mind.
>

I love your optimism :)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Diego Herranz]

I understand and that'll mean I'll have to move on, which in my case, it's
not a big issue. I was waiting until 20.04 LTS, though :)

>> The stable version of KiCad will always build with 16.04.

It looks like by the time 6.0 is out, Ubuntu 16.04 may still be officially
supported. Just something to have in mind.

Cheers,
Diego

On Mon, 21 Oct 2019, 21:11 Nick Østergaard,  wrote:

> You can still run 5.1 on 16.04. If you want bleeding edge, don't lock
> yourself down with a "stable" system.
>
> On Mon, 21 Oct 2019 at 21:37, Diego Herranz
>  wrote:
> >
> > I see. Are those dates when the respective OS support finishes or when
> we stop supporting them?
> > I was under the impression it is the former (although it is not fully
> clear) in which case that date is wrong.
> >
> > Thanks,
> > Diego
> >
> > On Mon, 21 Oct 2019 at 20:16, Ian McInerney 
> wrote:
> >>
> >> The listing I used when looking at whether our supported OS's had Boost
> 1.59 were the dates given here:
> http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page,
> it says that our support for 16.04 ended in April.
> >>
> >> -Ian
> >>
> >> On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz <
> diegoherr...@diegoherranz.com> wrote:
> >>>
> >>> I wasn't getting any nightly package update lately and checking [1]
> I've just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
> >>> Ubuntu 16.04 will be supported until April 2021 [2].
> >>>
> >>> Was this overlooked when checking distros? Or was it a deliberate
> decision? Is there anything that can be done?
> >>> I've been planning to move to a newer Ubuntu LTS release for some time
> but didn't really have the need while it is supported (everything stable
> and working very well).
> >>> I guess there may be more people in a situation similar to mine.
> >>>
> >>> Cheers,
> >>> Diego
> >>>
> >>> [1]
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
> >>> [2]
> https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions
> >>>
> >>> On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh 
> wrote:
> 
>  10/2/2019 8:34 PM, Wayne Stambaugh wrote:
>  > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
>  >> Hi,
>  >>
>  >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
>  >>> Ping. Is there any opposition to bumping the minimum Boost
> version to
>  >>> 1.59?
>  >> I still see no technical need to increase the minimal version for
> Boost.
>  >>
>  >
>  > The boost version used in Debian old stable is 1.62.  I think 1.59
> is a
>  > pretty safe bet at this point for the development version.  For the
> 5.1
>  > branch, we should keep the current version unless we are planning to
>  > back port any of the testing features which were the primary reason
> for
>  > the version bump request.  I will make the change as soon as I get a
>  > chance, we can always revert it if it causes too much grief.
>  >
>  > Cheers,
>  >
>  > Wayne
>  >
> 
>  I bumped the Boost version to 1.59.  If this causes any major
> headaches,
>  I can always revert it.  Before we go using any new Boost stuff,
> please
>  let the dust settle on the version bump change so we don't have to
> back
>  out a bunch of changes.
> 
>  Cheers,
> 
>  Wayne
> 
>  ___
>  Mailing list: https://launchpad.net/~kicad-developers
>  Post to : kicad-developers@lists.launchpad.net
>  Unsubscribe : https://launchpad.net/~kicad-developers
>  More help   : https://help.launchpad.net/ListHelp
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Ian McInerney]

We also seem to have assertions enabled in the Debian build (there have
been two reports from users [1], [2]). Is this something we control as
well, or is the the distribution packaging forcing them on?

-Ian

[1] https://bugs.launchpad.net/kicad/+bug/1847554
[2] https://bugs.launchpad.net/kicad/+bug/1848107

On Mon, Oct 21, 2019 at 6:51 PM Wayne Stambaugh 
wrote:

> I thought this might be the case.  If you click cancel, the assertion
> dialog will not be displayed again until you restart KiCad.
>
> Would one of our macos devs please take a look at the config settings
> use to build wxWidgets and see if we can turn the assertions off on
> release builds?  This might require some compiler flag settings to
> completely disable.
>
> On 10/21/19 1:39 PM, Kymatica wrote:
> > Ok. It’s not crashing after I tap No, but it’s ”a bit” annoying,
> especially when there’s a chain of 5 or so assertion pop-ups, as seems to
> happen sometimes when rerunning simulation while some error in the
> schematics make the sim fail and not finding the plotted nets.
> >
> > /Jonatan
> >
> >> 21 okt. 2019 kl. 19:44 skrev Wayne Stambaugh :
> >>
> >> Hi Jonaton,
> >>
> >> This is an assertion in wxWidgets being raised.  This really shouldn't
> >> happen on release builds.  While assertions like this are annoying they
> >> are not show stoppers unless clicking either the "No" or "Cancel"
> >> buttons cause KiCad to crash.  I'm guessing this is not the case but one
> >> of our macos devs can confirm this.  It looks like our macos wxWidgets
> >> library builds need to have the assertions disabled.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >>> On 10/20/19 10:37 AM, Kymatica wrote:
> >>> I still see this a lot on macOS, not only when editing symbol fields
> but
> >>> here and there:
> >>>
> >>> https://bugs.launchpad.net/bugs/1844545
> >>>
> >>> I don’t think 5.1.5 is ”production ready” until this is fixed.
> >>>
> >>> /Jonatan
> >>>
> > 20 okt. 2019 kl. 17:13 skrev Seth Hillbrand :
> 
>  On 2019-10-20 06:41, Wayne Stambaugh wrote:
> > Where are we on the 5.1.5 release?  I took a look at the bug tacker
> and
> > the only serious bug I saw was the glib assertion bug[1].  How close
> are
> > we to getting this fixed?  There is still some unexpected behavior
> with
> > the constrained zone drawing and editing changes that should be fixed
> > before we release.  I would like to tag -rc1 and start the string
> freeze
> > by the end of October.
> 
>  Odd, I didn't see that one come through.  I'll fix that this weekend.
> 
>  -S
> 
>  Seth Hillbrand
>  KiCad Services Corporation
>  https://www.kipro-pcb.com
>  +1 530 302 5483 | +1 212 603 9372
> 
>  ___
>  Mailing list: https://launchpad.net/~kicad-developers
>  Post to : kicad-developers@lists.launchpad.net
>  Unsubscribe : https://launchpad.net/~kicad-developers
>  More help   : https://help.launchpad.net/ListHelp
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Wayne Stambaugh]

According to Ubuntu[1], 16.04 looks like it will continue to receive
maintenance updates until April 2021.  It looks like we got that wrong.
 The boost version in 16.04 is 1.58.  There is no newer version of boost
in the back ports repo so we have a decision to make.  Drop support for
Ubuntu 16.04 nightly builds or drop the minimum boost version to 1.58.
I'm fine with dropping nightly build support for Ubuntu 16.04.  I don't
have a vested interest one way or another.  The stable version of KiCad
will always build with 16.04.

Cheers,

Wayne

On 10/21/19 3:36 PM, Diego Herranz wrote:
> I see. Are those dates when the respective OS support finishes or when
> we stop supporting them?
> I was under the impression it is the former (although it is not fully
> clear) in which case that date is wrong.
> 
> Thanks,
> Diego
> 
> On Mon, 21 Oct 2019 at 20:16, Ian McInerney  > wrote:
> 
> The listing I used when looking at whether our supported OS's had
> Boost 1.59 were the dates given
> here: http://kicad-pcb.org/help/system-requirements/#_gnulinux. On
> that page, it says that our support for 16.04 ended in April.
> 
> -Ian
> 
> On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz
>  > wrote:
> 
> I wasn't getting any nightly package update lately and checking
> [1] I've just noticed this boost bump has left Ubuntu 16.04
> (Xenial) out.
> Ubuntu 16.04 will be supported until April 2021 [2].
> 
> Was this overlooked when checking distros? Or was it a
> deliberate decision? Is there anything that can be done?
> I've been planning to move to a newer Ubuntu LTS release for
> some time but didn't really have the need while it is supported
> (everything stable and working very well).
> I guess there may be more people in a situation similar to mine.
> 
> Cheers,
> Diego
> 
> [1] 
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
> [2]
> https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions
> 
> On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
> 
> 10/2/2019 8:34 PM, Wayne Stambaugh wrote:
> > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
> >> Hi,
> >>
> >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
> >>> Ping. Is there any opposition to bumping the minimum
> Boost version to
> >>> 1.59?
> >> I still see no technical need to increase the minimal
> version for Boost.
> >>
> >
> > The boost version used in Debian old stable is 1.62.  I
> think 1.59 is a
> > pretty safe bet at this point for the development
> version.  For the 5.1
> > branch, we should keep the current version unless we are
> planning to
> > back port any of the testing features which were the
> primary reason for
> > the version bump request.  I will make the change as soon
> as I get a
> > chance, we can always revert it if it causes too much grief.
> >
> > Cheers,
> >
> > Wayne
> >
> 
> I bumped the Boost version to 1.59.  If this causes any
> major headaches,
> I can always revert it.  Before we go using any new Boost
> stuff, please
> let the dust settle on the version bump change so we don't
> have to back
> out a bunch of changes.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Nick Østergaard]

You can still run 5.1 on 16.04. If you want bleeding edge, don't lock
yourself down with a "stable" system.

On Mon, 21 Oct 2019 at 21:37, Diego Herranz
 wrote:
>
> I see. Are those dates when the respective OS support finishes or when we 
> stop supporting them?
> I was under the impression it is the former (although it is not fully clear) 
> in which case that date is wrong.
>
> Thanks,
> Diego
>
> On Mon, 21 Oct 2019 at 20:16, Ian McInerney  wrote:
>>
>> The listing I used when looking at whether our supported OS's had Boost 1.59 
>> were the dates given here: 
>> http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page, it 
>> says that our support for 16.04 ended in April.
>>
>> -Ian
>>
>> On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz 
>>  wrote:
>>>
>>> I wasn't getting any nightly package update lately and checking [1] I've 
>>> just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
>>> Ubuntu 16.04 will be supported until April 2021 [2].
>>>
>>> Was this overlooked when checking distros? Or was it a deliberate decision? 
>>> Is there anything that can be done?
>>> I've been planning to move to a newer Ubuntu LTS release for some time but 
>>> didn't really have the need while it is supported (everything stable and 
>>> working very well).
>>> I guess there may be more people in a situation similar to mine.
>>>
>>> Cheers,
>>> Diego
>>>
>>> [1] https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
>>> [2] https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions
>>>
>>> On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh  wrote:

 10/2/2019 8:34 PM, Wayne Stambaugh wrote:
 > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
 >> Hi,
 >>
 >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
 >>> Ping. Is there any opposition to bumping the minimum Boost version to
 >>> 1.59?
 >> I still see no technical need to increase the minimal version for Boost.
 >>
 >
 > The boost version used in Debian old stable is 1.62.  I think 1.59 is a
 > pretty safe bet at this point for the development version.  For the 5.1
 > branch, we should keep the current version unless we are planning to
 > back port any of the testing features which were the primary reason for
 > the version bump request.  I will make the change as soon as I get a
 > chance, we can always revert it if it causes too much grief.
 >
 > Cheers,
 >
 > Wayne
 >

 I bumped the Boost version to 1.59.  If this causes any major headaches,
 I can always revert it.  Before we go using any new Boost stuff, please
 let the dust settle on the version bump change so we don't have to back
 out a bunch of changes.

 Cheers,

 Wayne

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Diego Herranz]

I see. Are those dates when the respective OS support finishes or when we
stop supporting them?
I was under the impression it is the former (although it is not fully
clear) in which case that date is wrong.

Thanks,
Diego

On Mon, 21 Oct 2019 at 20:16, Ian McInerney 
wrote:

> The listing I used when looking at whether our supported OS's had Boost
> 1.59 were the dates given here:
> http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page,
> it says that our support for 16.04 ended in April.
>
> -Ian
>
> On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz <
> diegoherr...@diegoherranz.com> wrote:
>
>> I wasn't getting any nightly package update lately and checking [1] I've
>> just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
>> Ubuntu 16.04 will be supported until April 2021 [2].
>>
>> Was this overlooked when checking distros? Or was it a deliberate
>> decision? Is there anything that can be done?
>> I've been planning to move to a newer Ubuntu LTS release for some time
>> but didn't really have the need while it is supported (everything stable
>> and working very well).
>> I guess there may be more people in a situation similar to mine.
>>
>> Cheers,
>> Diego
>>
>> [1] https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
>> [2]
>> https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions
>>
>> On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh 
>> wrote:
>>
>>> 10/2/2019 8:34 PM, Wayne Stambaugh wrote:
>>> > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
>>> >> Hi,
>>> >>
>>> >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
>>> >>> Ping. Is there any opposition to bumping the minimum Boost version to
>>> >>> 1.59?
>>> >> I still see no technical need to increase the minimal version for
>>> Boost.
>>> >>
>>> >
>>> > The boost version used in Debian old stable is 1.62.  I think 1.59 is a
>>> > pretty safe bet at this point for the development version.  For the 5.1
>>> > branch, we should keep the current version unless we are planning to
>>> > back port any of the testing features which were the primary reason for
>>> > the version bump request.  I will make the change as soon as I get a
>>> > chance, we can always revert it if it causes too much grief.
>>> >
>>> > Cheers,
>>> >
>>> > Wayne
>>> >
>>>
>>> I bumped the Boost version to 1.59.  If this causes any major headaches,
>>> I can always revert it.  Before we go using any new Boost stuff, please
>>> let the dust settle on the version bump change so we don't have to back
>>> out a bunch of changes.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Ian McInerney]

The listing I used when looking at whether our supported OS's had Boost
1.59 were the dates given here:
http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page, it
says that our support for 16.04 ended in April.

-Ian

On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz 
wrote:

> I wasn't getting any nightly package update lately and checking [1] I've
> just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
> Ubuntu 16.04 will be supported until April 2021 [2].
>
> Was this overlooked when checking distros? Or was it a deliberate
> decision? Is there anything that can be done?
> I've been planning to move to a newer Ubuntu LTS release for some time but
> didn't really have the need while it is supported (everything stable and
> working very well).
> I guess there may be more people in a situation similar to mine.
>
> Cheers,
> Diego
>
> [1] https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
> [2] https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions
>
> On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh  wrote:
>
>> 10/2/2019 8:34 PM, Wayne Stambaugh wrote:
>> > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
>> >> Hi,
>> >>
>> >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
>> >>> Ping. Is there any opposition to bumping the minimum Boost version to
>> >>> 1.59?
>> >> I still see no technical need to increase the minimal version for
>> Boost.
>> >>
>> >
>> > The boost version used in Debian old stable is 1.62.  I think 1.59 is a
>> > pretty safe bet at this point for the development version.  For the 5.1
>> > branch, we should keep the current version unless we are planning to
>> > back port any of the testing features which were the primary reason for
>> > the version bump request.  I will make the change as soon as I get a
>> > chance, we can always revert it if it causes too much grief.
>> >
>> > Cheers,
>> >
>> > Wayne
>> >
>>
>> I bumped the Boost version to 1.59.  If this causes any major headaches,
>> I can always revert it.  Before we go using any new Boost stuff, please
>> let the dust settle on the version bump change so we don't have to back
>> out a bunch of changes.
>>
>> Cheers,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Ian McInerney]

There were two bugs still on the 5.1.5 milestone [1], [2] that related to
the editing of H/V/45 constrained polygons. I have bumped those to 6.0 now.
Should we reopen and move [3] and [4] to 6.0 so that we actually fix the
issues there?

-Ian

[1] https://bugs.launchpad.net/kicad/+bug/1842055
[2] https://bugs.launchpad.net/kicad/+bug/1842195
[3] https://bugs.launchpad.net/kicad/+bug/1847722
[4] https://bugs.launchpad.net/kicad/+bug/1846029

On Mon, Oct 21, 2019 at 7:02 PM Seth Hillbrand  wrote:

> On 2019-10-21 10:52, Ian McInerney wrote:
>
> > Seth,
> >
> > Just to clarify, for 5.1.5 (and future 5.1 releases), the H/V/45 is
> > only available during initial zone creation and is not going to be
> > active for editing the lines after creation? If this is the case, I
> > will push the bugs for this into the 6.0 milestone, so they can be
> > addressed there.
> >
> > -Ian
>
> That is correct.  I've already reset that bug[1].  But if you see others
> that relate to it, feel free to mark the dupes.
>
> -Seth
>
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372
>
> [1] https://bugs.launchpad.net/kicad/+bug/1833673
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

[Diego Herranz]

I wasn't getting any nightly package update lately and checking [1] I've
just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
Ubuntu 16.04 will be supported until April 2021 [2].

Was this overlooked when checking distros? Or was it a deliberate decision?
Is there anything that can be done?
I've been planning to move to a newer Ubuntu LTS release for some time but
didn't really have the need while it is supported (everything stable and
working very well).
I guess there may be more people in a situation similar to mine.

Cheers,
Diego

[1] https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly
[2] https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions

On Thu, 3 Oct 2019 at 19:59, Wayne Stambaugh  wrote:

> 10/2/2019 8:34 PM, Wayne Stambaugh wrote:
> > On 9/27/19 12:20 AM, Carsten Schoenert wrote:
> >> Hi,
> >>
> >> Am 26.09.19 um 22:26 schrieb Ian McInerney:
> >>> Ping. Is there any opposition to bumping the minimum Boost version to
> >>> 1.59?
> >> I still see no technical need to increase the minimal version for Boost.
> >>
> >
> > The boost version used in Debian old stable is 1.62.  I think 1.59 is a
> > pretty safe bet at this point for the development version.  For the 5.1
> > branch, we should keep the current version unless we are planning to
> > back port any of the testing features which were the primary reason for
> > the version bump request.  I will make the change as soon as I get a
> > chance, we can always revert it if it causes too much grief.
> >
> > Cheers,
> >
> > Wayne
> >
>
> I bumped the Boost version to 1.59.  If this causes any major headaches,
> I can always revert it.  Before we go using any new Boost stuff, please
> let the dust settle on the version bump change so we don't have to back
> out a bunch of changes.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Seth Hillbrand]

On 2019-10-21 10:52, Ian McInerney wrote:


Seth,

Just to clarify, for 5.1.5 (and future 5.1 releases), the H/V/45 is 
only available during initial zone creation and is not going to be 
active for editing the lines after creation? If this is the case, I 
will push the bugs for this into the 6.0 milestone, so they can be 
addressed there.


-Ian


That is correct.  I've already reset that bug[1].  But if you see others 
that relate to it, feel free to mark the dupes.


-Seth

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

[1] https://bugs.launchpad.net/kicad/+bug/1833673

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Wayne Stambaugh]

I thought this might be the case.  If you click cancel, the assertion
dialog will not be displayed again until you restart KiCad.

Would one of our macos devs please take a look at the config settings
use to build wxWidgets and see if we can turn the assertions off on
release builds?  This might require some compiler flag settings to
completely disable.

On 10/21/19 1:39 PM, Kymatica wrote:
> Ok. It’s not crashing after I tap No, but it’s ”a bit” annoying, especially 
> when there’s a chain of 5 or so assertion pop-ups, as seems to happen 
> sometimes when rerunning simulation while some error in the schematics make 
> the sim fail and not finding the plotted nets.
> 
> /Jonatan 
> 
>> 21 okt. 2019 kl. 19:44 skrev Wayne Stambaugh :
>>
>> Hi Jonaton,
>>
>> This is an assertion in wxWidgets being raised.  This really shouldn't
>> happen on release builds.  While assertions like this are annoying they
>> are not show stoppers unless clicking either the "No" or "Cancel"
>> buttons cause KiCad to crash.  I'm guessing this is not the case but one
>> of our macos devs can confirm this.  It looks like our macos wxWidgets
>> library builds need to have the assertions disabled.
>>
>> Cheers,
>>
>> Wayne
>>
>>> On 10/20/19 10:37 AM, Kymatica wrote:
>>> I still see this a lot on macOS, not only when editing symbol fields but
>>> here and there: 
>>>
>>> https://bugs.launchpad.net/bugs/1844545
>>>
>>> I don’t think 5.1.5 is ”production ready” until this is fixed.
>>>
>>> /Jonatan 
>>>
> 20 okt. 2019 kl. 17:13 skrev Seth Hillbrand :

 On 2019-10-20 06:41, Wayne Stambaugh wrote:
> Where are we on the 5.1.5 release?  I took a look at the bug tacker and
> the only serious bug I saw was the glib assertion bug[1].  How close are
> we to getting this fixed?  There is still some unexpected behavior with
> the constrained zone drawing and editing changes that should be fixed
> before we release.  I would like to tag -rc1 and start the string freeze
> by the end of October.

 Odd, I didn't see that one come through.  I'll fix that this weekend.

 -S

 Seth Hillbrand
 KiCad Services Corporation
 https://www.kipro-pcb.com
 +1 530 302 5483 | +1 212 603 9372

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Ian McInerney]

Seth,

Just to clarify, for 5.1.5 (and future 5.1 releases), the H/V/45 is only
available during initial zone creation and is not going to be active for
editing the lines after creation? If this is the case, I will push the bugs
for this into the 6.0 milestone, so they can be addressed there.

-Ian

On Sun, Oct 20, 2019 at 5:02 PM Seth Hillbrand  wrote:

> On 2019-10-20 08:40, Ian McInerney wrote:
>
> > There is also this H/V/45 issue [1]. It is more of a gray area though,
> > since it will probably involve touching the file format due to what is
> > happening (the H/V/45 is being saved as a global board setting rather
> > than a per-zone setting as the GUI would seem to make it).
> >
> > -Ian
> >
> > [1] https://bugs.launchpad.net/kicad/+bug/1847722
>
> Ugh.  You are right Ian.  We definitely need to fix that one.  Since I'm
> in the area, I'll deal with it.  I'm going to disable the H/V/45 during
> edits.  The setting will then only affect the newly created zone.  Since
> we don't have a place to store the information, keeping it with the zone
> info doesn't make sense because it will change based on opening/closing
> the file.
>
> For v6, I think we add the parameter to the zone unless people object.
>
> -Seth
>
>
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Adam Wolf]

It may be a false alarm--I am reviewing everything and it looks like
it is working for everyone so far.  There may be some documentation we
have to add to the macOS specific things about allowing permissions
when a popup pops up on first run, but if I am understanding correctly
none of the issues seem like blockers.

I have asked on the bug to see if anyone is having this problem still.

On Mon, Oct 21, 2019 at 9:54 AM Wayne Stambaugh  wrote:
>
> Do we know if this is a KiCad source bug issue or a macos packaging
> issue?  I was getting the distinct impression that it was the latter.  I
> agree that we do not want to release 5.1.5 without a functioning macos
> package.  I'm willing to hold off on the rc1 tag until we resolve this
> issue.  It may give us an opportunity to fix some additional bug for 5.1.5.
>
> On 10/20/19 9:02 PM, Adam Wolf wrote:
> > Hi folks.
> >
> > I was under the impression that although the macOS 10.15 betas had
> > weird issues with KiCad, that the release Catalina was fine.  This may
> > not be the case.  I am mobile today and only using my phone, so it's
> > difficult for me to dig into it right now. If folks are still
> > reporting that they create new projects, I would request that we
> > postpone a release until this is resolved.
> >
> > (I had posted a small and unhelpful error message, and was going to
> > get a debugger on a 10.15 machine to get a real stack trace, but
> > postponed going to 10.15 on that machine based on reports that it was
> > working--but I may have to get that set up this week, unless someone
> > else can.)
> >
> > Adam
> >
> > On Sun, Oct 20, 2019 at 6:50 PM Seth Hillbrand  wrote:
> >>
> >> Hi Wayne-
> >>
> >> These should be fixed.  I've pushed the reload issue off to v6 as the
> >> setting isn't available in the current file format as Ian mentioned, so
> >> I've reset the associated bug with a new milestone.
> >>
> >> We should be clear for these reports now.  It's safe to tag 5.1.5RC1
> >> from my perspective and we'll get some testing of the fixes.  It might
> >> be good to get a 5.1.6 milestone in launchpad at the same time and I
> >> will move all unaddressed items to that milestone so that we are only
> >> fixing issues with 5.1.5 commits during the RC phase.
> >>
> >> Thoughts?
> >>
> >> -Seth
> >>
> >> On 2019-10-20 07:38, Wayne Stambaugh wrote:
> >>> Thanks Seth,
> >>>
> >>> There is also this[1] bug and this[2] bug and this[3] bug related to
> >>> the
> >>> zone constraint changes.  I probably wont hold up the 5.1.5 release for
> >>> them but they are behavioral changes which users will not expect.  The
> >>> most annoying one is lp:1846028.
> >>>
> >>> Cheers,
> >>>
> >>> Wayne
> >>>
> >>> [1]: https://bugs.launchpad.net/kicad/+bug/1842195
> >>> [2]: https://bugs.launchpad.net/kicad/+bug/1846028
> >>> [3]: https://bugs.launchpad.net/kicad/+bug/1846029
> >>>
> >>> On 10/20/19 10:13 AM, Seth Hillbrand wrote:
>  On 2019-10-20 06:41, Wayne Stambaugh wrote:
> > Where are we on the 5.1.5 release?  I took a look at the bug tacker
> > and
> > the only serious bug I saw was the glib assertion bug[1].  How close
> > are
> > we to getting this fixed?  There is still some unexpected behavior
> > with
> > the constrained zone drawing and editing changes that should be fixed
> > before we release.  I would like to tag -rc1 and start the string
> > freeze
> > by the end of October.
> 
>  Odd, I didn't see that one come through.  I'll fix that this weekend.
> 
>  -S
> 
>  Seth Hillbrand
>  KiCad Services Corporation
>  https://www.kipro-pcb.com
>  +1 530 302 5483 | +1 212 603 9372
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>
> >> Seth Hillbrand
> >> KiCad Services Corporation
> >> https://www.kipro-pcb.com
> >> +1 530 302 5483 | +1 212 603 9372
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Wayne Stambaugh]

Hi Jonaton,

This is an assertion in wxWidgets being raised.  This really shouldn't
happen on release builds.  While assertions like this are annoying they
are not show stoppers unless clicking either the "No" or "Cancel"
buttons cause KiCad to crash.  I'm guessing this is not the case but one
of our macos devs can confirm this.  It looks like our macos wxWidgets
library builds need to have the assertions disabled.

Cheers,

Wayne

On 10/20/19 10:37 AM, Kymatica wrote:
> I still see this a lot on macOS, not only when editing symbol fields but
> here and there: 
> 
> https://bugs.launchpad.net/bugs/1844545
> 
> I don’t think 5.1.5 is ”production ready” until this is fixed.
> 
> /Jonatan 
> 
>> 20 okt. 2019 kl. 17:13 skrev Seth Hillbrand :
>>
>> On 2019-10-20 06:41, Wayne Stambaugh wrote:
>>> Where are we on the 5.1.5 release?  I took a look at the bug tacker and
>>> the only serious bug I saw was the glib assertion bug[1].  How close are
>>> we to getting this fixed?  There is still some unexpected behavior with
>>> the constrained zone drawing and editing changes that should be fixed
>>> before we release.  I would like to tag -rc1 and start the string freeze
>>> by the end of October.
>>
>> Odd, I didn't see that one come through.  I'll fix that this weekend.
>>
>> -S
>>
>> Seth Hillbrand
>> KiCad Services Corporation
>> https://www.kipro-pcb.com
>> +1 530 302 5483 | +1 212 603 9372
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Wayne Stambaugh]

On 10/20/19 12:02 PM, Seth Hillbrand wrote:
> On 2019-10-20 08:40, Ian McInerney wrote:
> 
>> There is also this H/V/45 issue [1]. It is more of a gray area though,
>> since it will probably involve touching the file format due to what is
>> happening (the H/V/45 is being saved as a global board setting rather
>> than a per-zone setting as the GUI would seem to make it).
>>
>> -Ian
>>
>> [1] https://bugs.launchpad.net/kicad/+bug/1847722
> 
> Ugh.  You are right Ian.  We definitely need to fix that one.  Since I'm
> in the area, I'll deal with it.  I'm going to disable the H/V/45 during
> edits.  The setting will then only affect the newly created zone.  Since
> we don't have a place to store the information, keeping it with the zone
> info doesn't make sense because it will change based on opening/closing
> the file.
> 
> For v6, I think we add the parameter to the zone unless people object.

This is definitely a v6 bug fix.  We have a strict stable release file
format change policy.  I don't think this bug is severe enough to break
with that policy.

Wayne

> 
> -Seth
> 
> 
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Wayne Stambaugh]

Do we know if this is a KiCad source bug issue or a macos packaging
issue?  I was getting the distinct impression that it was the latter.  I
agree that we do not want to release 5.1.5 without a functioning macos
package.  I'm willing to hold off on the rc1 tag until we resolve this
issue.  It may give us an opportunity to fix some additional bug for 5.1.5.

On 10/20/19 9:02 PM, Adam Wolf wrote:
> Hi folks.
> 
> I was under the impression that although the macOS 10.15 betas had
> weird issues with KiCad, that the release Catalina was fine.  This may
> not be the case.  I am mobile today and only using my phone, so it's
> difficult for me to dig into it right now. If folks are still
> reporting that they create new projects, I would request that we
> postpone a release until this is resolved.
> 
> (I had posted a small and unhelpful error message, and was going to
> get a debugger on a 10.15 machine to get a real stack trace, but
> postponed going to 10.15 on that machine based on reports that it was
> working--but I may have to get that set up this week, unless someone
> else can.)
> 
> Adam
> 
> On Sun, Oct 20, 2019 at 6:50 PM Seth Hillbrand  wrote:
>>
>> Hi Wayne-
>>
>> These should be fixed.  I've pushed the reload issue off to v6 as the
>> setting isn't available in the current file format as Ian mentioned, so
>> I've reset the associated bug with a new milestone.
>>
>> We should be clear for these reports now.  It's safe to tag 5.1.5RC1
>> from my perspective and we'll get some testing of the fixes.  It might
>> be good to get a 5.1.6 milestone in launchpad at the same time and I
>> will move all unaddressed items to that milestone so that we are only
>> fixing issues with 5.1.5 commits during the RC phase.
>>
>> Thoughts?
>>
>> -Seth
>>
>> On 2019-10-20 07:38, Wayne Stambaugh wrote:
>>> Thanks Seth,
>>>
>>> There is also this[1] bug and this[2] bug and this[3] bug related to
>>> the
>>> zone constraint changes.  I probably wont hold up the 5.1.5 release for
>>> them but they are behavioral changes which users will not expect.  The
>>> most annoying one is lp:1846028.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> [1]: https://bugs.launchpad.net/kicad/+bug/1842195
>>> [2]: https://bugs.launchpad.net/kicad/+bug/1846028
>>> [3]: https://bugs.launchpad.net/kicad/+bug/1846029
>>>
>>> On 10/20/19 10:13 AM, Seth Hillbrand wrote:
 On 2019-10-20 06:41, Wayne Stambaugh wrote:
> Where are we on the 5.1.5 release?  I took a look at the bug tacker
> and
> the only serious bug I saw was the glib assertion bug[1].  How close
> are
> we to getting this fixed?  There is still some unexpected behavior
> with
> the constrained zone drawing and editing changes that should be fixed
> before we release.  I would like to tag -rc1 and start the string
> freeze
> by the end of October.

 Odd, I didn't see that one come through.  I'll fix that this weekend.

 -S

 Seth Hillbrand
 KiCad Services Corporation
 https://www.kipro-pcb.com
 +1 530 302 5483 | +1 212 603 9372
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>> Seth Hillbrand
>> KiCad Services Corporation
>> https://www.kipro-pcb.com
>> +1 530 302 5483 | +1 212 603 9372
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.5 release status

[Wayne Stambaugh]

Hi Seth,

On 10/20/19 1:48 PM, Seth Hillbrand wrote:
> Hi Wayne-
> 
> These should be fixed.  I've pushed the reload issue off to v6 as the
> setting isn't available in the current file format as Ian mentioned, so
> I've reset the associated bug with a new milestone.

Thanks.  I appreciate the speedy fixes.

> 
> We should be clear for these reports now.  It's safe to tag 5.1.5RC1
> from my perspective and we'll get some testing of the fixes.  It might
> be good to get a 5.1.6 milestone in launchpad at the same time and I
> will move all unaddressed items to that milestone so that we are only
> fixing issues with 5.1.5 commits during the RC phase.

I just created the 5.1.6 milestone.  I will move the unaddressed 5.1.5
items today.  I only want the issues fixed with the 5.1.5 commits during
the RC phase so please no other bug fix commits without at least
discussing them on the mailing list first.  I want to avoid some of the
issues we've had during the a couple of the 5.1 releases.  If the fix is
trivial and unlikely to cause any other issues, than we can decide to
commit them as part of the 5.1.5 release.  However, if there is a
possibility that the fix could create additional bugs, they will have to
be pushed back to 5.1.6.

Cheers,

Wayne

> 
> Thoughts?
> 
> -Seth
> 
> On 2019-10-20 07:38, Wayne Stambaugh wrote:
>> Thanks Seth,
>>
>> There is also this[1] bug and this[2] bug and this[3] bug related to the
>> zone constraint changes.  I probably wont hold up the 5.1.5 release for
>> them but they are behavioral changes which users will not expect.  The
>> most annoying one is lp:1846028.
>>
>> Cheers,
>>
>> Wayne
>>
>> [1]: https://bugs.launchpad.net/kicad/+bug/1842195
>> [2]: https://bugs.launchpad.net/kicad/+bug/1846028
>> [3]: https://bugs.launchpad.net/kicad/+bug/1846029
>>
>> On 10/20/19 10:13 AM, Seth Hillbrand wrote:
>>> On 2019-10-20 06:41, Wayne Stambaugh wrote:
 Where are we on the 5.1.5 release?  I took a look at the bug tacker and
 the only serious bug I saw was the glib assertion bug[1].  How close
 are
 we to getting this fixed?  There is still some unexpected behavior with
 the constrained zone drawing and editing changes that should be fixed
 before we release.  I would like to tag -rc1 and start the string
 freeze
 by the end of October.
>>>
>>> Odd, I didn't see that one come through.  I'll fix that this weekend.
>>>
>>> -S
>>>
>>> Seth Hillbrand
>>> KiCad Services Corporation
>>> https://www.kipro-pcb.com
>>> +1 530 302 5483 | +1 212 603 9372
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Issues building PCBNew on Windows 10/Msys:fatal exception

[Wayne Stambaugh]

Brian,

On 10/21/19 9:24 AM, Brian Piccioni wrote:
> I'm updating this email in case somebody else has a similar problem.
> 
>  
> 
> I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad.
> It appear to run fine, except when I run PCBNew from a mingw64 terminal
> I get
> 
>  
> 
> $ pcbnew
> 
> C:/msys64/mingw64/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> UserWarning: wxPython/wxWidgets release number mismatch
> 
>   warnings.warn("wxPython/wxWidgets release number mismatch")

You should always see this warning.  The msys2 wxPython release is 3.0.2
and the wxWidgets release is 3.0.4 which causes the version mismatch.
Again, AFAIK, there this does not create any issues other than the fact
that wxPython is dead and has been replaced with wxPhoenix.  wxPhoenix
is wxPython for Python 3.  Unfortunately, the wxPython folks broke the
build scripts for wxPhoenix which means that you cannot build it on
msys2.  This *is* going to be a problem in the not too distant future
for windows users unless we either fix the wxPhoenix build scripts for
msys2 or switch to the free version of msvc to create windows builds.  I
prefer the former but we may not have any choice depending on manpower.

> 
>  
> 
>  
> 
> Interestingly, compiling does not generate "release number mismatch"
> warnings as happened when I did a 32 bit build.
> 
>  
> 
> I do, however, get these warnings:
> 
>  
> 
> C:\kicad-source\pcbnew\..\include\common.h(357) : Warning 317:
> Specialization of non-template 'hash'.
> 
> C:\kicad-source\pcbnew\..\include\common.h(365) : Warning 317:
> Specialization of non-template 'less'.
> 
> class_board.h(45) : Warning 315: Nothing known about 'std::unique_ptr'.

These are known issues with the code generated by SWIG to build the
Python scripting module.  AFAIK, they do not present any issues.

Cheers,

Wayne

> 
>  
> 
>  
> 
> (these are the only warnings I get compiling all of Kicad).
> 
>  
> 
> I will recompile wxPython and see if the PCBNew warnings go away though
> it is not pressing as everything works.
> 
>  
> 
> Thanks again
> 
>  
> 
> Brian
> 
>  
> 
> *From: *Wayne Stambaugh 
> *Sent: *October 20, 2019 10:09 AM
> *To: *kicad-developers@lists.launchpad.net
> 
> *Subject: *Re: [Kicad-developers] Issues building PCBNew on Windows
> 10/Msys:fatal exception
> 
>  
> 
> Hi Brian,
> 
>  
> 
> There is a long litany of things that can go wrong with msys2 builds but
> 
> I do not believe that the wxPython/wxWidgets mismatch is the problem.
> 
> Typically when I see issues like this, there has been a new gcc version
> 
> released and only one of the two dependency libraries have been compiled
> 
> with the new compiler which causes issues.  It's been a while but the
> 
> last time this happened, I had to recompile the wxPython package.  I
> 
> also noticed you are attempting to use 32 builds for debugging.  I
> 
> highly recommend that you debug using 64 bit builds.  Debug builds on
> 
> msys2 are massive and you will likely run into memory limit issues.  I
> 
> hope this helps.
> 
>  
> 
> Cheers,
> 
>  
> 
> Wayne
> 
>  
> 
> On 10/19/19 5:36 PM, Brian Piccioni wrote:
> 
>> Sorry if this is a bit long and thanks in advance for the help. I
> 
>> decided to move to a new laptop and create a debug version of Kicad so I
> 
>> can work on integrating my software. I believe I carefully followed the
> 
>> build instructions I suspect this may be related to a version mismatch
> 
>> but I don’t know how to fix it.
> 
>>
> 
>>  
> 
>>
> 
>> I installed Msys2, downloaded Kicad source and compiled a debug build.
> 
>> It compiled without errors but I get a warning
> 
>>
> 
>>  
> 
>>
> 
>>
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> 
>> UserWarning: wxPython/wxWidgets release number mismatch
> 
>>
> 
>>      warnings.warn("wxPython/wxWidgets release number mismatch")
> 
>>
> 
>>  
> 
>>
> 
>> I get the same error building the release and debug versions and the
> 
>> release version appears to work fine, except for complaints about
> 
>>
> 
>> version mismatch.
> 
>>
> 
>>  
> 
>>
> 
>> However, with the debug build I can run Kicad and invoke eeSchema and
> 
>> all the other applications from the Kicad menu except
> 
>>
> 
>> PCBNew and  the symbol editor. When I run these, I get errors:
> 
>>
> 
>>  
> 
>>
> 
>> Application failed to load:
> 
>>
> 
>>  IO_ERROR: Failed to load kiface library
> 
>> "C:\msys32\mingw32\bin\_pcbnew.kiface".
> 
>>
> 
>> from kiway.cpp : KiFACE() line:213
> 
>>
> 
>>  
> 
>>
> 
>> If I run PCBNew from the debug directory I get the same result but with
> 
>> details I can copy.
> 
>>
> 
>>  
> 
>>
> 
>> Details:
> 
>>
> 
>> 17:18:15: Failed to load shared library
> 
>> 'C:\kicad-source\build\debug\pcbnew\_pcbnew.kiface' (error 127: the
> 
>> specified procedure could not be found.)
> 
>>
> 
>> 17:18:15: IO_ERROR: Failed to load kiface 

Re: [Kicad-developers] Issues building PCBNew on Windows 10/Msys:fatal exception

[Brian Piccioni]

I'm updating this email in case somebody else has a similar problem.

I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad. It 
appear to run fine, except when I run PCBNew from a mingw64 terminal I get 

$ pcbnew
C:/msys64/mingw64/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633: 
UserWarning: wxPython/wxWidgets release number mismatch
  warnings.warn("wxPython/wxWidgets release number mismatch")


Interestingly, compiling does not generate "release number mismatch" warnings 
as happened when I did a 32 bit build.

I do, however, get these warnings:

C:\kicad-source\pcbnew\..\include\common.h(357) : Warning 317: Specialization 
of non-template 'hash'.
C:\kicad-source\pcbnew\..\include\common.h(365) : Warning 317: Specialization 
of non-template 'less'.
class_board.h(45) : Warning 315: Nothing known about 'std::unique_ptr'.


(these are the only warnings I get compiling all of Kicad).

I will recompile wxPython and see if the PCBNew warnings go away though it is 
not pressing as everything works.

Thanks again

Brian

From: Wayne Stambaugh
Sent: October 20, 2019 10:09 AM
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] Issues building PCBNew on Windows 10/Msys:fatal 
exception

Hi Brian,

There is a long litany of things that can go wrong with msys2 builds but
I do not believe that the wxPython/wxWidgets mismatch is the problem.
Typically when I see issues like this, there has been a new gcc version
released and only one of the two dependency libraries have been compiled
with the new compiler which causes issues.  It's been a while but the
last time this happened, I had to recompile the wxPython package.  I
also noticed you are attempting to use 32 builds for debugging.  I
highly recommend that you debug using 64 bit builds.  Debug builds on
msys2 are massive and you will likely run into memory limit issues.  I
hope this helps.

Cheers,

Wayne

On 10/19/19 5:36 PM, Brian Piccioni wrote:
> Sorry if this is a bit long and thanks in advance for the help. I
> decided to move to a new laptop and create a debug version of Kicad so I
> can work on integrating my software. I believe I carefully followed the
> build instructions I suspect this may be related to a version mismatch
> but I don’t know how to fix it.
> 
>  
> 
> I installed Msys2, downloaded Kicad source and compiled a debug build.
> It compiled without errors but I get a warning
> 
>  
> 
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> UserWarning: wxPython/wxWidgets release number mismatch
> 
>      warnings.warn("wxPython/wxWidgets release number mismatch")
> 
>  
> 
> I get the same error building the release and debug versions and the
> release version appears to work fine, except for complaints about
> 
> version mismatch.
> 
>  
> 
> However, with the debug build I can run Kicad and invoke eeSchema and
> all the other applications from the Kicad menu except
> 
> PCBNew and  the symbol editor. When I run these, I get errors:
> 
>  
> 
> Application failed to load:
> 
>  IO_ERROR: Failed to load kiface library
> "C:\msys32\mingw32\bin\_pcbnew.kiface".
> 
> from kiway.cpp : KiFACE() line:213
> 
>  
> 
> If I run PCBNew from the debug directory I get the same result but with
> details I can copy.
> 
>  
> 
> Details:
> 
> 17:18:15: Failed to load shared library
> 'C:\kicad-source\build\debug\pcbnew\_pcbnew.kiface' (error 127: the
> specified procedure could not be found.)
> 
> 17:18:15: IO_ERROR: Failed to load kiface library
> “C:\kicad-source\build\debug\pcbnew\_pcbnew.kiface”.
> 
>  
> 
> This PC has 32 GB of DRAM installed and
> 'C:\msys32\mingw32\bin\_pcbnew.kiface' is present.
> 
>  
> 
> When I run PCBNew standalone in msys2, I get this message
> 
>  
> 
> $ pcbnew
> 
> C:/msys32/mingw32/lib/python2.7/site-packages/wx-3.0-msw/wx/_core.py:16633:
> UserWarning: wxPython/wxWidgets release number mismatch
> 
>      warnings.warn("wxPython/wxWidgets release number mismatch")
> 
> Exception code=0xc005 flags=0x0 at 0x05A28FDE. Access violation -
> attempting to read data at address 0x
> 
> Segmentation fault
> 
>  
> 
> When I run this command
> 
> $ pacman -Qs wx   I get
> 
> local/mingw-w64-i686-wxPython 3.0.2.0-9
> 
>      A wxWidgets GUI toolkit for Python (mingw-w64)
> 
> local/mingw-w64-i686-wxWidgets 3.0.4-3
> 
>      A C++ library that lets developers create applications for
> Windows, Linux and UNIX (mingw-w64)
> 
>  
> 
> Here is the version info:
> 
>  
> 
> Application: KiCad
> 
> Version: 5.99.0-unknown, debug build
> 
> Libraries:
> 
>     wxWidgets 3.0.4
> 
>     libcurl/7.66.0 OpenSSL/1.1.1d (Schannel) zlib/1.2.11 brotli/1.0.7
> libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.39.2
> 
> Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
> wxMSW
> 
> Build Info:
> 
>     Build date: Oct 19 2019 09:19:25
> 
>     wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
> 
>     Boost: