Previously I have been running with /testing/ for
windows, and /nightlies for master.
On Mon, 22 Apr 2019 at 23:05, Adam Wolf
wrote:
> I set them up. They'll upload to testing/5.1 for now.
>
> Do we want to move the regular nightlies to nightlies/master and put
> these in nightlies/5.1?
>
>
But it seems like you can also use the aws-cli as follows:
aws s3 cp your.dmg s3://kicad-downloads/osx/nightly/ --endpoint-url
https://s3.cern.ch
After you configured the access and secrect key with aws configure.
On Mon, 22 Apr 2019 at 15:30, Nick Østergaard wrote:
> I guess s3cmd d
I guess s3cmd does not work with python3.
Then I took at look at https://s3tools.org/s3cmd and it says that version 2
do work with python3 and it looks like are using verison 2...
Does it work if you put just one file?
On Mon, 22 Apr 2019 at 15:19, Adam Wolf
wrote:
> Hi folks!
>
> Apologies
Yes, just retag the 5.1.1 tags as 5.1.2 as well. We have done that before
and is probably what will have the least workload. :)
On Sun, 21 Apr 2019 at 23:44, Steven A. Falco wrote:
> On 4/21/19 5:18 PM, Wayne Stambaugh wrote:
> > It's looks like 5.1.1 has a serious issue which was fixed and
Hello Henner,
I think the Librarians more or less communicate exclusively via github
issues. So it may be worth to post this as an issue on the kicad-symbols
repo over on github.
Regards
Nick
On Sun, 21 Apr 2019 at 22:12, Henner Zeller wrote:
> Hi,
> While converting some older project to
Hi
I am just curious about this topic. Is this a case where we should have
bumped the SEXPR_BOARD_FILE_VERSION? Or is this not needed as an earlier
kicad version would read it just fine?
Nick
On Sun, 21 Apr 2019 at 18:46, Jeff Young wrote:
> Hi Kevin,
>
> KiCad will read them in either way
Both installers work when I download from s3.cern
The mirror you have must be broken.
On Thu, 18 Apr 2019 at 13:49, tedd.t...@gmail.com
wrote:
> Hi,
>
> I've downloaded the latest stable x64 build from
> kicad-downloads.s3.cern.ch, but it failed the NSIS installer
> verification.
>
> To be
; >
> > I have the release announcement ready to go but it's on my desktop
> > computer at home. If most of the packages are ready, I will push the
> > release announcement this evening after I get home from work.
> >
> > Cheers,
> >
> > Wayne
&
The windows installers are uploading to the stable folder
A quick sanity check says they work. Although that in the 32 bit version
the python console does not open from the toolbar, but I think that has
been an issue for a while. Works ok for 64 bit.
And of couse we see the cannot write
Ok, cool. I guess we all agree to merge it on master :)
man. 8. apr. 2019 16.45 skrev Tomasz Wlostowski :
> On 08/04/2019 13:58, Nick Østergaard wrote:
> > Hi Tomasz
> >
> > I was wondering about this yesterday. Has it even been merged on master?
> >
> > I
Fails on linux as well
man. 8. apr. 2019 17.12 skrev Wayne Stambaugh :
> According to `git bisect`, commit
> 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64
> bits) with the following error:
>
> C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import_project.cpp:144:46:
>
I am noy sure what this means. Does it depend on changes in kicad or the
installer only?
man. 8. apr. 2019 14.46 skrev Simon Richter :
> Hi,
>
> On Sat, Apr 06, 2019 at 11:31:27PM -0400, Seth Hillbrand wrote:
>
> > I'd like to suggest spinning out 5.1.1 soon and pushing the existing
> > 5.1.1
Hi Tomasz
I was wondering about this yesterday. Has it even been merged on master?
I think I would prefer not to merge it on stable if it has not even been
tested on master, but if you think it is low risk I guess it is ok.
As I have not tested it I don't know what it looks like, but if you
See https://twitter.com/launchpadstatus/status/1113042990228963328
On Wed, 3 Apr 2019 at 21:28, Jon Evans wrote:
> Same for me
>
> On Wed, Apr 3, 2019 at 3:27 PM Jeff Young wrote:
>
>> Is launchpad’s git instance down? It’s refusing my connection...
>>
A but report about this was also reported for tracking at
https://bugs.launchpad.net/bugs/1821476
søn. 24. mar. 2019 19.34 skrev Seth Hillbrand :
> Am 2019-03-24 13:23, schrieb Jon Evans:
> > Hi all,
> >
> > Another question from this forum thread:
> >
>
staller with
> python3 support and WXPYTHON disabled. But if you are tight on time, I can
> totally understand.
>
> Best regards, Mitja
>
>
> --
> *From:* Nick Østergaard
> *To:* thomas.pointhu...@gmx.at
> *Cc:* KiCad Developers
>
g all details (like the split out 3d
> >> packages) if necessary.
> >> We could/should also host the packaging under the KiCad github project
> >> if you decide to publish an official package.
> >>
> >> Best wishes
> >> Max
> >>
>
ke the split out 3d
> packages) if necessary.
> We could/should also host the packaging under the KiCad github project
> if you decide to publish an official package.
>
> Best wishes
> Max
>
> Am Fr., 15. März 2019 um 13:34 Uhr schrieb Nick Østergaard <
> oe.n...@
:
>
>> Thank you everyone for all of your hard work in getting 5.1 released.
>> It never ceases to amaze me the tireless efforts that everyone puts in
>> to make this happen. Here is to more great releases in the future.
>>
>> Cheers,
>>
>> Wayne
>&g
Hello
It seems that I have it under my canonical account.
I am not sure if access can somehhow be shared. If you add some
instructions on the readme in your repo I will take a look at it.
Nick
On Fri, 15 Mar 2019 at 13:30, Maximilian Federle
wrote:
> Hello,
>
> I've packaged KiCAD 5.1 as a
Release annoncement live now.
On Thu, 14 Mar 2019 at 18:15, Wayne Stambaugh wrote:
> Nick,
>
> I just pushed the last few changes to the release announcement so once
> the website download links are updated everything should be ready to go.
>
> Thanks,
>
> Wayne
>
&g
Thank you Steven!
tor. 14. mar. 2019 16.27 skrev Steven A. Falco :
> On 3/14/19 10:26 AM, Wayne Stambaugh wrote:
> > How are we doing on the 5.1.0 packaging? I've only heard from
> > Jean-Samuel thus far. Are the windows and macos packages ready to go
> > yet? I have a few minor tweaks to
Hi
Essentially ready, meaning windows, PPA and macos builds are done/sanity
checked, but not moved to stable folder yet. Please push your tweaks for
the draft of the announcement ASAP.
I intend to fixup the other things in a couple of hours.
Nick
On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh
//github.com/KiCad/kicad-winbuilder/blob/master/nsis/install.nsi#L647
>
>
> Regards
> Russell Oliver
>
> On Tue, 12 Mar 2019 at 21:30, Nick Østergaard wrote:
> >
> >
> https://github.com/KiCad/kicad-winbuilder/issues/53#issuecomment-337167911
> >
> > t
https://github.com/KiCad/kicad-winbuilder/issues/53#issuecomment-337167911
tir. 12. mar. 2019 11.07 skrev Russell Oliver :
> To cut down the download size, can there be a nightly package built
> that doesn't contain the library, module and 3d files? just enough to
> overwrite the program files.
If you do decide to merge but disable by default, please consider to use
the kicad_advanced config.
man. 11. mar. 2019 15.06 skrev Jon Evans :
> Hi Wayne,
>
> I will rebase and post an updated branch soon.
> I will also generally be available to fix any bugs although will be
> offline for a few
Thank you.
søn. 10. mar. 2019 20.34 skrev Wayne Stambaugh :
> Nick,
>
> I'll push the initial draft later this evening. I figure it will be
> Tuesday or Wednesday until most of the packages are built and uploaded
> to the website.
>
> Wayne
>
> On 3/10/19 3:2
Please push the announcement to the website repo in case we want to add
some more info.
søn. 10. mar. 2019 20.23 skrev Wayne Stambaugh :
> Thank your Rene and all of the library developers for your efforts.
> This should be the last of the repo tags so lets fire up those package
> builders. I
That particular commit didn't, but latest is good.
lør. 9. mar. 2019 07.27 skrev Simon Richter :
> Hi,
>
> the documentation failed to compile for me last night:
>
> https://jenkins.simonrichter.eu/job/any-kicad-doc-head/569/
>
> Is that just me, or is something broken?
>
>Simon
>
>
Forwarding to kicad-doc-devs in case anyone missed it, and adding tag
intent on kicad-i18n and kicad-doc as:
https://github.com/KiCad/kicad-i18n/issues/363
https://github.com/KiCad/kicad-doc/issues/691
On Fri, 8 Mar 2019 at 20:16, Wayne Stambaugh wrote:
> The 5.1.0 release has been tagged and
Hello Michal
I don't see any recent pull request from you. Please don't hold back, if
you got a good chunk done, just submit it.
On Thu, 7 Mar 2019 at 20:43, Michal Jahelka
wrote:
> Hi,
>
> I just finished Czech (cs) translation. Mostly translated, except some
> Gerber part (i am not too
You should be able to trigger a tagged build now for rc2
fre. 1. mar. 2019 03.29 skrev Adam Wolf :
> Any chance Nick or someone could make that docs tarball for this, so we
> can test 5.1.0 rc2 on Mac? (Probably built on 10.12!)
>
> On Thu, Feb 28, 2019, 1:30 PM Wayne Stambaugh
> wrote:
>
>>
Dunno, but I see kicad on this
https://static.rptorcs.com/TALOSII/images/talos_ii_eda_teaser_prerelease_small.png
>From https://www.raptorcs.com/TALOSII/prerelease.php
:)
On Tue, 26 Feb 2019 at 21:31, Vesa Solonen wrote:
> Clemens Koller kirjoitti 18.2.2019 klo 12.48:
> > Sorry, for getting
Hello, I know it may be slightly late, but I created a 5.1.0-rc2 milestone.
There was an issue with some rendering in sketch mode for arcs. I know that
rc2 is very imminent.
On Mon, 18 Feb 2019 at 08:14, Константин Барановский <
baranovskiykonstan...@gmail.com> wrote:
> Thank you, Carsten. Now
I think we also saw this a long time ago with hidpibdisplays. Maybe the
recent changes have undone something...
søn. 17. feb. 2019 23.17 skrev Tomasz Wlostowski :
> On 17/02/2019 23:04, Wayne Stambaugh wrote:
> > Looks fine on Linux.
> >
> > On 2/17/19 4:50 PM, Jeff Young wrote:
> >> The 3D
Should we create a 5.1.0-rc2 milestone or should we just use 5.1.0 if we
think something needs to be included?
On Tue, 5 Feb 2019 at 19:52, Wayne Stambaugh wrote:
> I'm going to tag 5.1.0-rc1 this evening after I get home from work.
> There are still two low priority bugs against the 5.1.0-rc1
I think all the scripts we have do work with python3 unless we missed
something. I think Thomas P. did test it.
On Mon, 11 Feb 2019 at 17:11, Jean-Samuel Reynaud
wrote:
> Dear All,
>
> PPA for KiCad 5.1 is now ready.
> When it's possible (for example on Ubuntu Bionic) GTK 3 is used, python3
>
The addition looks sane to me.
On Sun, 10 Feb 2019 at 22:56, John Beard wrote:
> Hi,
>
> Here's a patch for the advanced config dev-docs. Basically, it says
> "here be dragons, use at your peril". I realise after re-reading the
> docs I wrote before, that this is not clear.
>
> Sending to the
Hello
I would like to see the attached minor documentation change to be merged as
it makes it easier to link to the section from the www.
The patch should otherwise be self explanatory :)
Regards
Nick Østergaard
From d95b0ff71ea3335e6c769b46479ec10ed7617c1c Mon Sep 17 00:00:00 2001
From: =?UTF
see fit.
Regards
Nick Østergaard
[1] https://kicad-downloads.s3.cern.ch/index.html
[2] http://www2.futureware.at/~nickoe/kicad-downloads-mirror/
On Wed, 6 Feb 2019 at 21:53, Wayne Stambaugh wrote:
> This is primarily a question for the folks setting up and maintaining
> our download
@Wayne
It is enabled with phoenix and gtk3 as default for Archlinux AUR
@Steven
You may find inspiration here:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=kicad-git
Make sure to use the correct wxWidgets_CONFIG_EXECUTABLE, I don't remember
what they are called on fedora, but I think
Yes, I know.
tir. 5. feb. 2019 17.29 skrev Jean-Samuel Reynaud :
> On my side:
> http://kicad-pcb.org is NOT working
> but
> http://www.kicad-pcb.org IS working...
>
> They don't have the same address according to DNS:
> $ host kicad-pcb.org
> kicad-pcb.org has address 188.185.118.209
>
https://github.com/KiCad/kicad-website/issues/379#issuecomment-460694422
tir. 5. feb. 2019 17.18 skrev Rene Pöschl :
> It seems the kicad website is currently down.
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to :
Previously?
tor. 24. jan. 2019 17.26 skrev Adam Wolf :
> Something didn't work about the redirect previously, Mark, but I'll try
> with the new URL.
>
> Thanks folks!
>
> On Thu, Jan 24, 2019 at 10:07 AM Nick Østergaard
> wrote:
>
>> Hm, I didn't notice that you us
Adam Wolf :
> Sorry, resending since I sent from the wrong address.
>
> On Fri, Jan 18, 2019, 6:57 PM Adam Wolf
>> If I use git am, how do I release another 5.0.2, Nick?
>>
>> On Fri, Jan 18, 2019, 6:08 PM Nick Østergaard >
>>> IMHO, just use git am
> >
>> > Adam
>> >
>> > On Fri, Jan 18, 2019 at 1:41 PM Wayne Stambaugh > > <mailto:stambau...@gmail.com>> wrote:
>> >
>> > If you use `git am` to apply the patches, you wont get -dirty
>> appended
>> > to the ve
Mmm, what is wrong wit the git describe when the patches are applied with
git am?
fre. 18. jan. 2019 20.11 skrev Wayne Stambaugh :
> This is a result of modifications to the repo. The --dirty option of
> `git describe` checks to see anything is modified and appends -dirty to
> the version
Yes, I am fine with using it in the copr builds for now. Do we need to
submit a PR for the libngspice package to let the packager pick it up more
easy? I have not seen any activity from him.
On Tue, 15 Jan 2019 at 20:58, Steven A. Falco wrote:
> On 1/15/19 9:21 AM, Wayne Stambaugh wrote:
> > Hi
If needed be that it won't be merged in kicad, we could patch it in with
the build scripts for fedora until the libngspice package is updated and
this should allow us to enable ngspice on the fedora copr builds.
On Mon, 14 Jan 2019 at 16:30, Steven A. Falco wrote:
> I wanted to close the loop
All on needs to know if in the cmake message, I don't really think we need
to do any more hand holding here.
On Wed, 9 Jan 2019 at 16:00, Brian Piccioni
wrote:
> Thanks, Wayne
>
> Perhaps it might be useful to add a note to the make instructions to this
> effect as per my recent email.
>
>
Except it fails to build for me :/
http://ci.kicad-pcb.org/job/linux-kicad-full-gcc-head/4485/consoleText
CMake Error at qa/pcbnew/CMakeLists.txt:62 (target_link_libraries):
Target "pcbnew_kiface_objects" of type OBJECT_LIBRARY may not be linked
into another target. One may link only to
I just did git am 000* and it worked fine for me, on master.
On Sun, 6 Jan 2019 at 01:20, John Beard wrote:
> On Sat, Jan 5, 2019 at 4:23 PM Seth Hillbrand wrote:
>
> > Patch 0002 does not apply cleanly to qa/CMakeLists.txt even after
> > applying 0001
>
> Hmm, that's odd: I can apply this
Hi Lachlan,
Are you sure that your workspace is clean? I don't see any issues on
any platform.
Nick
On Sat, 22 Dec 2018 at 06:53, Lachlan Audas wrote:
>
> Hi, just pull the lest-est developer build from git-hub for KiCad
> and tried compiling it. But but get this Error, missing file
I guess Adam is still intending to test them a bit more before calling
it done. AFIK he bumped the minimum version of macos a bit hence the
uncertainty.
https://lists.launchpad.net/kicad-developers/msg38558.html
On Thu, 13 Dec 2018 at 15:29, Seth Hillbrand wrote:
>
> Hi Adam-
>
> I see that
It is fixed, I actually mentally has it in my head that it was
included in Stevens patch. You may need to refresh the page if your
browser caches aggressively.
On Wed, 12 Dec 2018 at 01:01, Seth Hillbrand wrote:
>
> Am 2018-12-09 13:13, schrieb Wayne Stambaugh:
> > I pushed the release
ar as I
>> >>> understand, it does not require a rebuild, only replacement of
>> >>> configuration files.
>> >>>
>> >>> Adam, do you think you can still add the patch to the macOS
>> >
>>> symbols and footprints, at least).
> > >>>
> > >>> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
> > >>> mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@g
See kicad-mac-builder on the github org
tir. 4. dec. 2018 22.48 skrev Andy Peters :
>
> > On Dec 4, 2018, at 2:45 PM, Adam Wolf
> wrote:
> >
> > I think this is also fixed for me!
>
> If you guys point me to a build recipe for macOS, I will set up nightly
> builds on one of my Mojave machines.
at 3:05 PM Wayne Stambaugh
> >>> mailto:stambau...@gmail.com>> wrote:
> >>>
> >>> I just tagged and pushed 5.0.2 so we need to decide what we
> >>> want
> >>> to do
> >>> about tagging th
Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
getting a minor library update as well?
On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh wrote:
>
> I just noticed a few last minute changes were made to the 5.0 branch.
> Is there anything else pending or am I good to go with
It does not look like it is enabled by now.
See the rules file here:
https://git.launchpad.net/~js-reynaud/+git/kicad-daily-pkg/tree/debian/rules?h=dailybuild
It uses:
https://git.launchpad.net/~js-reynaud/+git/kicad-daily-pkg/tree/debian/usewxpython.sh?h=dailybuild
To check if the wx-config
Has this been tested on all three major platforms?
On Mon, 19 Nov 2018 at 17:26, Brüns, Stefan
wrote:
>
> On Freitag, 9. November 2018 00:51:56 CET Brüns, Stefan wrote:
> > Currently, the plugindir in the plugin manager is constructed as
> >
Thank you, I can confirm that this was the last change that made the
fedora build happy. :)
On Mon, 5 Nov 2018 at 20:33, Wayne Stambaugh wrote:
>
> John,
>
> I merged your patch.
>
> Thanks,
>
> Wayne
>
> On 11/5/2018 9:49 AM, John Beard wrote:
> > Gah! Wrong patch! Try this.
> > On Mon, Nov 5,
Hello
It seems that we have a footprint wizard plugin which specifies a
shebang when we don't really want or need this. I have attached a
patch to bring the touch slider one in line with the others.
For reference, see https://github.com/KiCad/fedora-packaging/pull/20
Regards
Nick Østergaard
y problems.
> I wouldn't recommend that for stable builds but generally speaking, I
> don't run in to too many issue when upgrading msys2.
>
> Cheers,
>
> Wayne
>
> On 10/29/2018 1:13 PM, Nick Østergaard wrote:
> > Hi,
> >
> > A small update as follows: I have u
currently we are using:
mingw-w64-i686-gcc 7.3.0-2
mingw-w64-x86_64-gcc 8.2.0-3
Regards
Nick ØstergaardHi
On Sun, 28 Oct 2018 at 21:26, Nick Østergaard wrote:
>
> From https://bugs.launchpad.net/kicad/+bug/1800339/comments/9
>
> It do indeed seem like updating the msys2 build environme
forgotten. I will change it over as
soon as possible for the future builds.
Nick
On Sun, 28 Oct 2018 at 01:12, Nick Østergaard wrote:
>
> Hi Seth,
>
> Currently the gcc version is:
> mingw-w64-i686-binutils 2.28-2
> mingw-w64-i686-gcc 7.1.0-3
> mingw-w64-i686-gcc-ada 7.1.0-3
Hi Seth,
Currently the gcc version is:
mingw-w64-i686-binutils 2.28-2
mingw-w64-i686-gcc 7.1.0-3
mingw-w64-i686-gcc-ada 7.1.0-3
mingw-w64-i686-gcc-fortran 7.1.0-3
mingw-w64-i686-gcc-libgfortran 7.1.0-3
mingw-w64-i686-gcc-libs 7.1.0-3
mingw-w64-i686-gcc-objc 7.1.0-3
mingw-w64-x86_64-binutils
Yeah, it looks like it is missing in Version:
(6.0.0-rc1-dev-983-gabe1ffabd), release build
On Sat, 20 Oct 2018 at 12:43, jp charras wrote:
>
> Le 19/10/2018 à 22:28, Henner Zeller a écrit :
> > Hi,
> > A long time ago, I added a little connecting line while moving the
> > label or value in the
Hmm, this is still available in 5.0.0 at least.
On Fri, 19 Oct 2018 at 22:28, Henner Zeller wrote:
>
> Hi,
> A long time ago, I added a little connecting line while moving the
> label or value in the schematic editor (BZR4686 now as git commit:
> 3132c70e54a0c5a61110eab7662e288398145c15 ), which
I was not aware of that change, but I have made a test build if anyone
likes to testrun it.
This is master built with debug as the build type and the option enabled.
http://downloads.kicad-pcb.org/windows/testing/patched/kicad-patched-144-ddea4e11d-x86_64.exe
On Thu, 11 Oct 2018 at 22:54, Seth
FWIW everything should be tagged now. So packagers should be able to
bump the pkgver.
On Wed, 10 Oct 2018 at 12:18, Marco Ciampa wrote:
>
> On Mon, Oct 08, 2018 at 09:24:02AM -0400, Wayne Stambaugh wrote:
> > How much time will our translators and librarians need to tag 5.0.1?
> > Hopefully not
The branch seems to be fairly buildable. It is only some of the first
commits that does not build well, see
https://jenkins.simonrichter.eu:8443/job/windows-kicad-msys2-evaluate/86/artifact/build-report.txt/*view*/
On Sat, 29 Sep 2018 at 01:39, Simon Richter wrote:
>
> Hi,
>
> > Really guys,
r., 14. Sep. 2018 um 06:45 Uhr schrieb Nick Østergaard
> :
>>
>> This still needs testing on macos, but as no one have proved it to be broken
>> ok macos, I vote for merging as is.
>>
>> It has been tested on windows and linux.
>>
>> fre. 14. sep. 2018
This still needs testing on macos, but as no one have proved it to be
broken ok macos, I vote for merging as is.
It has been tested on windows and linux.
fre. 14. sep. 2018 11.39 skrev Thomas Pointhuber :
> Hi,
>
> I posted this proposal on launchpad, but no answers so far:
> * see:
In addition to that I can note; that it follows the 5.0 branch for the
kicad source and the kicad-i18n, but is using the 5.0.0 tag for
everything else.
On Mon, 10 Sep 2018 at 14:29, Nick Østergaard wrote:
>
> Hi Seth
>
> I have created them now, they are currently locat
It is not ideal, but should be good enough.
Nick
On Mon, 10 Sep 2018 at 11:11, Nick Østergaard wrote:
>
> I will add it for the windows builds soon.
>
> I don't think there is a nightly PPA for the 5.0 branch yet, there was
> for the 4.0 branch for a period at least.
> On Sun, 9 Sep 2
I will add it for the windows builds soon.
I don't think there is a nightly PPA for the 5.0 branch yet, there was
for the 4.0 branch for a period at least.
On Sun, 9 Sep 2018 at 16:22, Seth Hillbrand wrote:
>
> Hi All-
>
> Can we update the packaging scripts that produce nightly packages to also
Hi Seth
I have made the milestone, currently with this description.
"For stuff we don't really need to block 5.0.1 and we would like to
backport to 5.0..."
I am not sure we need this milestone, I thought we went for 5.1.0. But
as I am far behind with the emails, I created it anyways to not
I cant view the patch via my phone right now, but please add a simple
unittest in the qa folder as well.
fre. 31. aug. 2018 14.56 skrev Wayne Stambaugh :
> Andrew,
>
> I looked at this patch an it looks fine to me. I fine with exposing the
> 3D model properties in the Python scripting. Is
In the Symbol Library Browser
ons. 29. aug. 2018 01.47 skrev Jeff Young :
> Hi Tom,
>
> I pushed changes to
> https://git.launchpad.net/~jeyjey/kicad/log/?h=tom-eeschema-gal-aug27.
>
> This includes converting the Choose Symbol dialog to GAL, moving the
> GAL_DISPLAY_OPTIONS to common, and
Kevin, that is partly correct. But it is casued because the master
branch on Tom's repo is very old. This should not be needed anymore,
if it was not removed completely. There should not be any need for bzr
anymore.
On Tue, 28 Aug 2018 at 16:46, Kevin Cozens wrote:
>
> On 2018-08-27 03:43 PM,
There are still open issues that either need to be analyzed.
https://launchpad.net/kicad/+milestone/5.0.1
On Wed, 22 Aug 2018 at 07:51, Ingo Kletti wrote:
>
> Hello,
>
> don't want to sound like a "are we there yet?"-like kid, but: What is
> the status of the 5.0.x release?
>
> I'm asking
No we do not currently log downloads actively.
Den man. 23. jul. 2018 kl. 05.03 skrev Adam Wolf
:
>
> Do we capture download statistics on the file server at all? It would
> be really fun to see how many folks are downloading things. I know it
> is not an accurate representation of userbase, but
If you just push it to a local branch somwhere I can easily trigger a
windows build.
Den tir. 21. aug. 2018 kl. 20.05 skrev Wayne Stambaugh :
>
> Hey Tom,
>
> On 8/9/2018 10:12 AM, Tomasz Wlostowski wrote:
> > Hi all,
> >
> > The patch set in the attachment brings back the legacy autoplacement
> >
Alternatively, we could provide them in a dedicated repository on the
kicad org on github. Then they are decoupled from the normal source
and the wild west for IDE confs are self contained. This is just a
suggestion if you think this would be useful.
Den tir. 21. aug. 2018 kl. 19.49 skrev Wayne
Any update on this? It does not look like it is merged.
Den tor. 26. jul. 2018 kl. 17.17 skrev John Beard :
>
> Hi,
>
> Another -Wcatch-value warning, this time in kicad2step.cpp.
>
> Cheers,
>
> John
> ___
> Mailing list:
errors. It looks
like it needs to be updated to py3k syntax.
Regards
Nick Østergaard
Den lør. 4. aug. 2018 kl. 12.23 skrev Thomas Pointhuber
:
>
> Hi,
>
> I managed to get KiCad to run with Python 3 as well as did some quick
> verification that basic methods are working using CLI
It looks lile the patch does not compile, but maybe the patch was not
applied correctly. You should be able to look at the patched code in the
workspace.
tir. 7. aug. 2018 21.39 skrev Nick Østergaard :
> I triggered this windows build with the patch.
>
> https://jenkins.simonrichter.eu
Yes
https://bugs.launchpad.net/kicad/+bug/1785113
Den søn. 5. aug. 2018 kl. 21.56 skrev Wayne Stambaugh :
>
> I just updated my laptop build (Ubuntu 17.10 with stock gnome desktop)
> and notice a rather odd layout of the new exit dialog. Is anyone else
> seeing this?
>
> Wayne
>
The one with the fatter text and lighter blue.
søn. 5. aug. 2018 17.22 skrev Kevin Cozens :
> On 2018-08-05 08:22 AM, John Beard wrote:
> > Eagle-eyed (is that an offensive slur on a KiCad list?) Nick noticed
> > that the doxygen header logo is actually slightly incorrect.
> > Presumably I used
The new patch looks good to me.
Den søn. 5. aug. 2018 kl. 14.22 skrev John Beard :
>
> Hi,
>
> Eagle-eyed (is that an offensive slur on a KiCad list?) Nick noticed
> that the doxygen header logo is actually slightly incorrect.
> Presumably I used the wrong file for a source, not sure where it came
Ok, I completely forgot about this, but I have uploaded it for 5.0.0 now.
Den man. 4. sep. 2017 kl. 18.26 skrev Nick Østergaard :
>
> No, but good point. I will try to make that available.
>
> Den 4. sep. 2017 5.10 PM skrev "Greg Smith" :
>>
>> Is there an equ
Hello
Attached is a patch to update the dev-docs about the new option ot use
OCC instead of OCE
Regards
Nick Østergaard
From e8300b778c29f22f94023c4ae1683653f2e84977 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nick=20=C3=98stergaard?=
Date: Thu, 2 Aug 2018 19:11:04 +0200
Subject: [PATCH] Add
Hello
It may be off by default, but should we enable it by default? I think
yes. It has been discussed briefly here and there.
If we like it in the 5.0 builds I propose we set it as default on on
the 5.0 branch now.
Nick
Den man. 23. jul. 2018 kl. 05.48 skrev Seth Hillbrand :
>
> Hi Devs-
>
>
Yes.
https://github.com/KiCad/kicad-winbuilder/issues/53
It does basically work that way, but simply needs a bit of refactoring on
the build server to support both mechanisms, but as getting 5.0.0 has been
a priority have not not done it yet.
Nick
Den ons. 1. aug. 2018 kl. 15.32 skrev Ben Hest
FYI there is also a GTK setting to choose to show icons or not, so
some users on linux see the icons and other not depending on that
option, and also depending on the kicad option to show icons or not.
Den tir. 31. jul. 2018 kl. 13.45 skrev John Beard :
>
> Flag icons are also (ab)used in the
Hi Andrew
Seth already shared the build log.
tir. 31. jul. 2018 05.29 skrev Andrew Lutsenko :
> I just noticed that my patch was reverted with reference to a build
> failure with gcc 4.9.2
>
> Could you share the error messages too?
> Also curios which platform uses such ancient compiler. I
I guess we could remove the last section entirely. Please submit a PR
for how you would like to describe the assembler code thingie.
Den søn. 22. jul. 2018 kl. 22.20 skrev Nick Østergaard :
>
> woopsie, that meant to only to up to 4.0.7
> Den søn. 22. jul. 2018 kl. 22.19 skrev Simo
woopsie, that meant to only to up to 4.0.7
Den søn. 22. jul. 2018 kl. 22.19 skrev Simon Richter :
>
> Hi,
>
> On 22.07.2018 18:44, Wayne Stambaugh wrote:
>
> > I just pushed the updated version of the v5 release announcement[1].
> > Please let me know if you find any missing features.
>
> The
301 - 400 of 1794 matches
Mail list logo
