Disclamier: I disabled the auto update for now as the change is not merged
pending review. I will fix it after the weekend.
fre. 10. maj 2019 16.54 skrev Jon Evans :
> Thanks, Nick!
>
> On Thu, May 9, 2019 at 4:38 PM Nick Østergaard wrote:
>
>> It should work now, and it may
It should work now, and it may also be a bit more responsive.
On Thu, 9 May 2019 at 16:16, Nick Østergaard wrote:
>
> I know. I will report back when it works.
>
> tor. 9. maj 2019 16.15 skrev Jon Evans :
>>
>> Still down
>>
>> On Wed, May 8, 2019 at 3:27 PM W
I know. I will report back when it works.
tor. 9. maj 2019 16.15 skrev Jon Evans :
> Still down
>
> On Wed, May 8, 2019 at 3:27 PM Wayne Stambaugh
> wrote:
>
>> Still no luck :(
>>
>> On 5/8/19 10:12 AM, Nick Østergaard wrote:
>> > Ok, thank you for
Nothing attached
tor. 9. maj 2019 09.45 skrev :
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help :
Ok, thank you for the notification.
It looks like the publish job jot stuck in a retry loop, I have
restarted it and it should be back within half an hour I hope.
On Wed, 8 May 2019 at 15:15, Ben Hest wrote:
>
> It's down for me.
>
> On Wed, May 8, 2019 at 6:20 AM Wayne Stambaugh wrote:
>>
>>
https://bugs.launchpad.net/kicad/+bug/1816286
ons. 8. maj 2019 15.40 skrev Nick Østergaard :
> Is the swig version 4.0.0?
>
> ons. 8. maj 2019 15.39 skrev Steven A. Falco :
>
>> I've started getting a build error on 5.1.2 in Fedora rawhide. Here is
>> part of the log:
Is the swig version 4.0.0?
ons. 8. maj 2019 15.39 skrev Steven A. Falco :
> I've started getting a build error on 5.1.2 in Fedora rawhide. Here is
> part of the log:
>
> [ 68%] Generating pcbnew_wrap.cxx, pcbnew.py
> cd /builddir/build/BUILD/kicad-5.1.2/pcbnew && /usr/bin/cmake -E
>
I guess this is sort of related to the observation and response I got here:
https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg27587.html
Or maybe I misunderstand what exactly you mean.
On Mon, 6 May 2019 at 12:38, Jeff Young wrote:
>
> Eelik reported that our cross-probing
Hello Jeff,
I ran my "evaluate" script on your branch and there are a couple of
commits that are not buildable, see
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-evaluate/107/artifact/build-report.txt
As usual the builds logs are available on the jenkins job if you need
them. (You may
Congratulations Wayne. That sounds like good news for everyone. But
remember not to burn yourself out, just the opportunity to take a
break from kicad in your "spare" time then :)
On Sat, 27 Apr 2019 at 20:05, Wayne Stambaugh wrote:
>
> For those you who haven't heard yet, I made the
It looks like there is an issue with the patch builds, the kicad
binaries are not included in the installer, only some dependencies...
So don't use that build.
On Fri, 3 May 2019 at 16:00, Nick Østergaard wrote:
>
> I have uploaded a build of the eemodern branch on
&
I have uploaded a build of the eemodern branch on
https://jenkins.simonrichter.eu/job/windows-kicad-msys2-patch/lastSuccessfulBuild/artifact/out/pack-x86_64/kicad-patched-330-5.1.0-437-gc807783d7-x86_64.exe
On Fri, 3 May 2019 at 14:06, Brian Piccioni wrote:
>
> Hello Devs
>
>
>
> This is well
Maybe it will be fixed in the next release of cmake
https://gitlab.kitware.com/cmake/cmake/merge_requests/2747
Found via https://gitlab.kitware.com/cmake/cmake/issues/18865
On Wed, 1 May 2019 at 22:34, Nick Østergaard wrote:
>
> @Wayne, please note that I think there is a workaround.
@Wayne, please note that I think there is a workaround. I have not
tested it myself, but I guess you can configure kicad with
Boost_NO_BOOST_CMAKE=ON as mention in the github issue.
On Wed, 1 May 2019 at 20:33, Wayne Stambaugh wrote:
>
> Jeff,
>
> I think that was a different issue. My issue
I don't think so, at least when I look at the PKGBUILD it is still
using bootstrap.sh and b2 to build. See:
https://github.com/msys2/MINGW-packages/blob/fd550b8d48e6bc831b1e36202eaf495cba5062f8/mingw-w64-boost/PKGBUILD
I don't see anything immediately alarming. Maybe the builds scripts in
boost
It worked fine in the past, but at some point the emails never reached the
mailing list. I am not sure if it was some email config on jenkins that
needed to be updated or what it was, but I never really tried to enable it
after the move because of the issues with the logs not really being public
Hi John
The one on ci.kicad-pcb.org does not exist after the move to some CERN
infra. I don't really like the setup as is. The intention is to have the
builds public, but they can not be like that at the moment because of the
infrastructure design. This is one of the reasons that we have not
Look in the dev console, it is the mimetype that is sometimes wrong.
It seems like it is not a good idea to host it directly is s3 like this. I
will make it more reliable at a later time.
tir. 23. apr. 2019 20.21 skrev Brian Piccioni :
> Foobared on Chrome Windows for me the past few days I've
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?
>
>
Enjoy.
On Mon, 22 Apr 2019 at 23:04, Marco Ciampa wrote:
> Just a heads-up
> I'll be abroad for a vacation for a week.
> No computer, no email.
>
> Best regards,
>
> --
>
>
> Marco Ciampa
>
>
> --
> Mailing list: https://launchpad.net/~kicad-doc-devs
> Post to :
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
I never got the time to try to review it, I was sort of hoping you ro
report that there were no issues with.
I assume you are still using it for your debian package and that it does
fix the issue.
Thank you for the bump.
lør. 20. apr. 2019 09.00 skrev Carsten Schoenert :
> Ping!
>
> Anyone
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
>
Flags were removed in later versions of kicad because they are ambigious.
On Fri, 22 Mar 2019 at 15:02, Alfrede wrote:
> Hi together,
>
> in the Moment i rewrite the gui_translation_howto Documentation for German.
>
> Where i struggle was when i came to the Point:
>
>
> As you see in this
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
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
Hello Mathias,
Welcome to the club. ;)
This particular issue should be addressed in
https://github.com/KiCad/kicad-doc-website/issues/13
Nick
søn. 10. feb. 2019 11.59 skrev Alfrede :
> Hi all,
>
> first of all i wanna say thank you for adding me in the mailinglist.
>
> I want to help you in
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 :
This is not wrong, this is as expected.
søn. 3. feb. 2019 18.33 skrev Aleks-Daniel Jakimenko-Aleksejev <
alex.jakime...@gmail.com>:
> Package: kicad
> Version: 5.1~20190127.4fc692f+dfsg1-1
>
> I installed kicad from experimental and noticed that the actual version
> is
No worries. Yes, that is the intention.
I am not sure about you, but I have heard that Rome was not built in
one day. It was built during the night. -- And that is where I sleep
:P
fre. 25. jan. 2019 00.56 skrev Marco Ciampa :
>
> On Thu, Jan 24, 2019 at 11:17:34PM +0100, Nick Østergaard
What do you mean by there being no links? There is a menu to select
language.
FWIW the master branch is not yet automatically added, so far it is only
the old tagged docs.
On Thu, 24 Jan 2019 at 17:58, Marco Ciampa wrote:
> There are no links to the tranlated docs...
>
>
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
No, this is wrong! I just pushed an update. Also I did reply to you
instantly. There is nothing wrong with discussing things first.
Also, there is not reason in changing thing without reasoning and testing
when what is available works.
On Sat, 12 Jan 2019 at 14:33, wrote:
> GPereira [1] filed
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
I don't think it is fair to orphan this as GPereira didn't respond to
my comment:
slic3r.desktop
Add Comment
Latest Comments
1 2 3 4 5 6 ... Next › Last »
swiftgeek commented on 2018-09-28 23:49
Few icons and a bit of perl scripts that implement gui that are not
executed is not overhead
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
301 - 400 of 1927 matches
Mail list logo
