Thank you.
søn. 14. jun. 2020 14.25 skrev Holger Vogt :
> Uups,
>
> Nick, thanks for the hint.
>
> ngspice-doc-32.tar.gz is uploaded now.
>
> Holger
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to :
Hello Holger
Ok, I sorta tried to update the package a couple of times and was
wondering why the download did not work on a simple pkg bump.
This is because the doc tar is missing. Could you please add that, or
is it not intended to be included anymore?
Erhm, ooh yeah, I sorta nuked the jenkins instance that performed the
mirroring... so I will need to fix that one of these days..
On Thu, 4 Jun 2020 at 14:59, wrote:
>
> Hello Jeff,
>
> I was using github instead of gitlab, this lags gitlab by a day it seems.
> The problem fixed with
It is fixed now.
On Tue, 2 Jun 2020 at 12:16, Nick Østergaard wrote:
>
> Well, the jenkins job that prepares the copr package fails to clone the 3d
> models for some reason, maybe the repo grew massively in size recently.
>
> tir. 2. jun. 2020 04.01 skrev Oleg Endo
Well, the jenkins job that prepares the copr package fails to clone the 3d
models for some reason, maybe the repo grew massively in size recently.
tir. 2. jun. 2020 04.01 skrev Oleg Endo :
> Hi all,
>
> The Fedora nightly builds are already 4 days behind.
> Did something get stuck there?
>
>
Plain speculation, but maybe you did run the cmake command initially
without libglm-dev being installed, then installed it and re-reun the
config? If that is the erase, you should probably delta your build
(containing the CMakeCache.txt) and try again.
On Mon, 1 Jun 2020 at 18:41, Brian Henning
I think you need to make a PR for msys2 with a pkgver bump, if they
merge it I assume it will appear in https://packages.msys2.org/queue
and it may be easier to poke them to let it rebuild. :/
On Mon, 25 May 2020 at 12:57, jp charras wrote:
>
> Le 23/05/2020 à 17:55, jp charras a écrit :
> > Le
Maybe some of thar stuff depends on CMAKE_INSTALL_PREFIX in some unexpected
way?
lør. 23. maj 2020 22.38 skrev Ian McInerney :
> Have you tried redefining the environment variables to point to the
> correct system libraries? Specifically I believe the 4 you need are:
> KICAD_TEMPLATE_DIR (the
Looks fine for me in chrome. It looks like you are missing some assets, I
assume you already tried to force refrash it to make sure it is not a
caching issue.
lør. 23. maj 2020 15.26 skrev Wayne Stambaugh :
> I don't know if it was intentional (I'm guessing not) but the KiCad
> website looks
Maybe submit it as a MergeRequest on gitlab.
ons. 20. maj 2020 12.16 skrev Badr Hack :
> Hi Wayne,
>
> Is there any update regarding this patch?
>
> If there is any thing else to adjust please let me know.
>
> For information, the plugin is working without any bug since 2018 in my
> for :)
>
>
Hi Brian
Mmm, it sound more like you are not updating msys2 properly...
But please attach pkglist_with_s.txt.
pacman -Qs > pkglist_with_s.txt
It looks like msys2 also recommends an update script (update-core) to
workaround the issues with the runtime. [1] Especially note:
"Run update-core. If
Yeah, hence there are probably no one here that can give you
maintainer ship, unfortunately. :/
On Sat, 16 May 2020 at 16:10, Johannes Maibaum wrote:
>
> Hi Nick,
>
> Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
>
> I am not aware of who the maintainer of t
Hi Stefan
Do you have a macos yourself? If yes, you are probably better off
starting with resolving issues at
https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues
Adam Wolf got some new hardware for building for macos, the plan is to
add it as a gitlab runner. This has not been done
v6 behavior and this one should
> never be cherry-pick
If that works for now, please do that. If you have changes that
applies to 5.1, don't hold them back. It is better to get it in ASAP,
if it is easy (cherry-pick'able).
>
> Francisco
>
> - Mail original -
>
On Sun, 17 May 2020 at 11:24, Carsten Schoenert wrote:
>
> Hello Wayne,
>
> Am 14.05.20 um 18:43 schrieb Wayne Stambaugh:
> > Carsten,
> >
> > What information do you need from KiCad. Does Debian (or any other
> > disto) have recommendations for upstream projects to help packagers?
>
> Debian
I am not aware of who the maintainer of the flatpak is, nor do I think he
may follow this list closely.
But it would certanly be good to get the package updated to be on part with
other packages.
Nick
lør. 16. maj 2020 12.27 skrev Johannes Maibaum :
> Hello KiCad team,
>
> during the past
I have updated it now.
On Fri, 15 May 2020 at 16:41, Eeli Kaikkonen wrote:
>
>
>
> On Fri, May 15, 2020 at 5:35 PM Ian McInerney
> wrote:
>>
>> Considering that there are also changes to the library in the releases, does
>> it make sense to package the light releases for the versioned
>>
Great! :)
fre. 15. maj 2020 13.50 skrev Ian McInerney :
> FYI: I have just merged
> https://gitlab.com/kicad/code/kicad/-/merge_requests/198 into 5.1 which
> bumps the minimum CMake version required from 3.0 to 3.2 so that we can fix
> https://gitlab.com/kicad/code/kicad/-/issues/4209. We
They are under testing for a reason. That is they have not been tested
yet. I expect them to download the tagged version, but I have not
verified it yet.
On Fri, 15 May 2020 at 13:47, Andrew Lutsenko wrote:
>
> They can get libraries using lite release as well, it's just install time
>
Hi Holger
That sounds good. I will update it for the windows build 5.1.6_2, _1 has 31
IIRC.
This page should probably be updated as well.
http://ngspice.sourceforge.net/download.html
Nick
fre. 15. maj 2020 08.11 skrev Holger Vogt :
> ngspice-32 is available.
>
> I have tested various
@Steven A. Falco it is because we just prebuilt docs in the macos builds.
On Thu, 14 May 2020 at 21:34, Steven A. Falco wrote:
>
> You can directly download tars from gitlab. Here is the url for the docs:
>
> https://gitlab.com/kicad/services/kicad-doc/-/archive/5.1.6/kicad-doc-5.1.6.tar.bz2
>
Hi Francisco
Thank you for your interest and effort. I have added you now, you
should be able to manage the issuetracker, please test it.
Some thoughts about yours:
Tracking things to be updated or changed is better done in the issue tracker.
I think all effort should be focused on the master
I am not sure exactly what kind of annotation stuff you are working
on, but there is another guy working on some geographical annotation.
See https://gitlab.com/kicad/code/kicad/-/merge_requests/108
On Tue, 12 May 2020 at 19:07, Wayne Stambaugh wrote:
>
> Hi James,
>
> By "breaking" changes, I'm
t;
> The F32 build finished but I want to test it before I submit it. The F31
> build is still finishing up, but should be ready for me to test soon.
>
> Once I test and submit them, then we'll just have to wait for karma for them
> to go into production.
>
> St
The library is till on github:
https://github.com/KiCad/kicad-templates
https://github.com/KiCad/kicad-symbols
https://github.com/KiCad/kicad-footprints
https://github.com/KiCad/kicad-packages3D
The code, translation and docs are on gitlab:
https://gitlab.com/kicad/code/kicad
to branch from 5.1.2 or
814321ecf474f2c1a6061a01122c9b3148b17a2e. I have pushed the 5.1 branch
I have with merge-base on the latest commit for now.
Regards
Nick Østergaard
On Thu, 7 May 2020 at 19:19, Jon Evans wrote:
>
> Why not just not translate the master docs branch (if you start
made it better, maybe
> >
> > On Wed, May 6, 2020 at 6:00 PM Nick Østergaard > <mailto:oe.n...@gmail.com>> wrote:
> >
> > I have done it, could't be bothered with the bullet points though. :)
> >
> > On Wed, 6 May 2020
Awesome, thanks!
tor. 7. maj 2020 04.59 skrev Mark Roszko :
> I made it better, maybe
>
> On Wed, May 6, 2020 at 6:00 PM Nick Østergaard wrote:
>
>> I have done it, could't be bothered with the bullet points though. :)
>>
>> On Wed, 6 May 2020 at 23
I have done it, could't be bothered with the bullet points though. :)
On Wed, 6 May 2020 at 23:11, Wayne Stambaugh wrote:
>
> If you have time, I'm fine with that. Thanks for the help.
>
> On 5/6/2020 4:57 PM, Nick Østergaard wrote:
> > I can do it, I will probably ju
ack a bit.
>
> On 5/6/2020 4:16 PM, Nick Østergaard wrote:
> > Shouldn't we post that on the blog on the website as well? Looks copy
> > pastable.
> >
> > What you do think Wayne?
> >
> > On Mon, 4 May 2020 at 22:53, Wayne Stambaugh wrote:
> >>
&
u are used to.
On Wed, 6 May 2020 at 10:22, Marco Ciampa wrote:
>
> On Wed, May 06, 2020 at 07:48:06AM +0200, Nick Østergaard wrote:
> > Maybe a repo config error, I will check the permissions for you. But you
> > should be able to push to your own fork an make a MR.
>
&g
Shouldn't we post that on the blog on the website as well? Looks copy pastable.
What you do think Wayne?
On Mon, 4 May 2020 at 22:53, Wayne Stambaugh wrote:
>
> For those nightly build users, the merge request to make the new
> schematic and symbol library file formats the default file format
Just as a follow up on this. There was a kind contributor [1], who
helped me getting the functionality that I wanted.
Thank you Luca (@wifasoi)
Regards
Nick Østergaard
[1] https://gitlab.com/wifasoi
On Fri, 24 Apr 2020 at 23:24, Nick Østergaard wrote:
>
> Hello
>
> Everything ne
Please see the comments about #4328 onnthe issue itself. I don't think you
are testimg with the same conditions.
ons. 6. maj 2020 12.55 skrev jp charras :
> Le 06/05/2020 à 00:09, Nick Østergaard a écrit :
> > Mmm, when you mean branch freeze, I assume you really mean that we
> >
Maybe a repo config error, I will check the permissions for you. But you
should be able to push to your own fork an make a MR.
ons. 6. maj 2020 01.22 skrev Marco Ciampa :
> I tried a push ... this error...
>
> remote: GitLab: You are not allowed to push code to protected branches on
> this
Stambaugh wrote:
>
> We are just under two weeks out of the 5.1.6 release. If anyone needs
> any extra time. Please let me know.
>
> Thanks,
>
> Wayne
>
> On 4/16/20 8:19 AM, Wayne Stambaugh wrote:
> > Done.
> >
> > On 4/16/20 7:58 AM, Nick Østergaard wrot
As far as I am aware there are no officially distributed "plugins", if
you are thinking about the action plugins.
On Sat, 2 May 2020 at 01:25, Nick Østergaard wrote:
>
> Hi Alan
>
> I don't see anyone else responding to you, but beware that google does
> not like you
Hi Alan
I don't see anyone else responding to you, but beware that google does
not like your email, so it is flagged as spam, but yes, you need to
submit a pull request for the kicad-footprint-wizards on github.
Nick
On Fri, 24 Apr 2020 at 19:08, Alan Samet wrote:
>
> Please excuse me if this
I don't think it is a good idea.
On Mon, 27 Apr 2020 at 12:57, Simon Richter wrote:
>
> Hi,
>
> On Fri, Apr 24, 2020 at 11:10:27PM +0300, Eeli Kaikkonen wrote:
>
> > I keep the Windows nightly build download server page (
> > https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/)
Yes, exactly my point. We already used the 30 seconds of attention span on
the download page trying to help describe the different options for stable
and what versions og macos is supported.
The user simply need one click to go to the instructions after that one
click needed to open the
I don't think we gain anything by adding more complexity to the
download page. It is after all just a download page.
If we really need to do very step-by-step and verbose explanations for
those can't can't read the README in the installer, I think that is
better suited in a chapter of the
projects.
It is getting late here.
Nick Østergaard
p.s. Not in a good mude, but I guess it is better to send this now
than later. Sorry if I hurt anyone, it is not intentional.
___
Mailing list: https://launchpad.net/~kicad-developers
Post
I don't think we gain anything for adding more directories.
As Andrew suggested, it is probably better to make a script or helper
tool for yourself to do that. You may be able to use aws s3 or s3cmd
to query the server.
On Fri, 24 Apr 2020 at 22:58, Andrew Lutsenko wrote:
>
> If you do
Just a small comment. The windows that Adam attached are actually
Finder, the file explorer thing on macos, that is stylized as part of
the Disk Image file (.dmg). Hence, when the user do the "drag the
KiCad folder to Applications" it is just a normal file copy. It just
happens that apple peeps
Yah, maybe you nedd to create a new buid dir, if it is really really old.
Otherwise, show us your cmake config. ;)
tor. 23. apr. 2020 18.53 skrev Seth Hillbrand :
> That usually pops up when you are loading GTK2 from wx and pcbnew is
> compiled for GTK3
>
> -Seth
>
> Seth Hillbrand
> KiCad
change the config to skip the
> > auto-generated swig files? They seem to generate lots of noise.
> >
> > -Jon
> >
> > On Thu, Apr 23, 2020 at 8:01 AM Wayne Stambaugh > <mailto:stambau...@gmail.com>> wrote:
> >
> > Nice work! Th
access in there
when you have a coverity account, but I am not sure. If you can't find
it just reply to me and I can add you.
As it stands now, a new coverity build is submitted every day.
Nick Østergaard
[1] https://scan.coverity.com/projects/kicad-stable
[2] https://scan.coverity.com/projects/kicad
Just the tag in git
tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh :
> Nick,
>
> Do you need a source archive or just the tag?
>
> Cheers,
>
> Wayne
>
> On 4/16/20 3:58 AM, Nick Østergaard wrote:
> > Can we have a 5.1.6-rc1 tag then?
> >
> > t
Can we have a 5.1.6-rc1 tag then?
tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh :
> The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable
> release. Please do not make any commits to the 5.1 branch without first
> confirming with the lead dev team and no translated string
@Ian McInerney It should work now automatically.
On Sun, 26 Jan 2020 at 18:48, Nick Østergaard wrote:
>
> No, bjt wr just need to make sure it works.
>
> søn. 26. jan. 2020 01.39 skrev Ian McInerney :
>>
>> Are we required to use the Docker Hub registry to host the c
Hi JKB,
Please report it at https://gitlab.com/kicad/code/kicad/-/issues
On Sun, 12 Apr 2020 at 09:48, BERTRAND Joël wrote:
>
> Hello,
>
> I'm trying to export a PCB (50cm*75cm if I remember) to step and I
> don't obtain step file. kicad2step takes 100% of CPU for a long time
Hi Adam
If the current 5.1 nightly build jobs are to be used again, maybe we
can enable it now to see what we are missing? Assuming there is enough
build capacity available.
Nick
On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote:
>
> Hi folks!
>
> My KiCad time has been dramatically reduced for the
Thank you very much for the effort!
On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote:
>
> Hi folks!
>
> My KiCad time has been dramatically reduced for the past month due to
> schools closing for COVID-19.
>
> I hope to have the OCC switchover complete this week--there were some
> fixup_bundle snags
lly takes no setup, since the login
> credentials are already provided to CI if I recall).
>
> -Ian
>
> On Sat, Jan 25, 2020 at 8:50 PM Nick Østergaard wrote:
>
>> Yes, I already pushed a test script on some branche but we need to push
>> it to the docler registey.
&
GitLab).
>
> -Ian
>
> On Sat, 25 Jan 2020, 01:03 Nick Østergaard, wrote:
>
>> It isn't automatically upsated for the time being because docker hub does
>> not support gitlab easily.
>>
>> fre. 24. jan. 2020 19.36 skrev Ian McInerney :
>>
>>>
update to the
> commit message policy that was made last month.
>
> -Ian
>
> On Thu, Dec 19, 2019 at 9:08 AM Nick Østergaard wrote:
>
>> Thank you for reporting, I will check it.
>>
>> On Thu, 19 Dec 2019 at 01:42, Ian McInerney
>> wrote:
>>
Its a mirror, no manual action required ;)
On Tue, 21 Jan 2020 at 00:38, Wayne Stambaugh wrote:
>
> Did someone already do this? I just checked the github repo and the
> latest commit hash is correct.
>
> On 1/20/20 5:46 PM, Ian McInerney wrote:
> > The GitHub mirror will also need to be force
Stambaugh wrote:
>
> Well this is a kick in the teeth. I just unprotected it and I don't see
> an option to re-enable the protection after I force the changes.
>
> On 1/20/20 5:18 PM, Nick Østergaard wrote:
> > There is a "protected branches" section in the settings of the r
There is a "protected branches" section in the settings of the repo.
On Mon, 20 Jan 2020 at 23:18, Nick Østergaard wrote:
>
> You probably need to disable the option to disable force pushing on the repo.
>
> On Mon, 20 Jan 2020 at 23:20, Wayne Stambaugh wrote:
> >
&g
You probably need to disable the option to disable force pushing on the repo.
On Mon, 20 Jan 2020 at 23:20, Wayne Stambaugh wrote:
>
> GitLab rejected the forced push using this method. Anyone else have any
> ideas. Until we get this resolved, please do not push any commits to
> the master
/20 11:35 AM, Nick Østergaard wrote:
> > It would be nice to rebase the repo to exclude those useless blobs.
> >
> > On Mon, 20 Jan 2020 at 17:33, Nick Østergaard wrote:
> >>
> >> git push --mirror
> >> remote: error: GH001: Large files detected
It would be nice to rebase the repo to exclude those useless blobs.
On Mon, 20 Jan 2020 at 17:33, Nick Østergaard wrote:
>
> git push --mirror
> remote: error: GH001: Large files detected. You may want to try Git
> Large File Storage - https://git-lfs.github.com.
> remot
git push --mirror
remote: error: GH001: Large files detected. You may want to try Git
Large File Storage - https://git-lfs.github.com.
remote: error: Trace: 4ca7122c5342fce7e9459b19325e1a4d
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File common/libcommon.a.ocP1Z7
Works fine for me in Version: (5.1.5-54-g8a2705f81), release build
One pin from eeschema to pcbnew and vice versa.
On Mon, 20 Jan 2020 at 17:10, Dick Hollenbeck wrote:
>
> Quick help,
>
> When I click on a pin in eeschema I get the disambiguating menu and then I
> say "pin" choice.
>
> But
No other comments? If not, I guess we should just merge the proposed changes.
On Thu, 16 Jan 2020 at 18:54, Ian McInerney wrote:
>
> After the discussion on the list after the update to Boost 1.59, I have
> drafted an updated support statement for the 3 supported Linux distributions
> we have:
Hello
I see this is the link checker log of the website:
- ./public/help/file-formats/index.html
320 * External link
On Fri, 17 Jan 2020 at 17:18, Ian McInerney wrote:
>
> There are 2 main issues I can see with rebasing:
> 1) Rebuilding the history will change the commit hashes on master, which will
> throw off our 5.1 cherry-picked commit messages that refer to the master
> commit they came from (there are
I think it would be better to just rebase to get rid of that object.
On Fri, 17 Jan 2020 at 16:08, Wayne Stambaugh wrote:
>
> On 1/17/20 9:53 AM, Seth Hillbrand wrote:
> > On 2020-01-17 03:23, Simon Richter wrote:
> >> Hi,
> >>
> >> there are two massive blobs that were accidentally checked in,
I guess you could just specify he CMAKE_INSTALL_PREFIX and do make
install if you like, but keep in mind that all the dependencies should
also be available. This is what the packaging scripts do.
If you are developing, I think you can just start kicad from the msys2
mingw64 shell.
On Thu, 9 Jan
The one named "kicad-services" is NOT an official kicad repo, that is
someone else. Everything official about kicad on gitlab is on the
"kicad" namespace.
On Mon, 6 Jan 2020 at 16:37, Marco Ciampa wrote:
>
> On Mon, Jan 06, 2020 at 02:42:36PM +0100, f.dos.san...@free.fr wrote:
> > Hi KiCad doc
What is the blocker for the libs to move to gitlab.
I was under the impression that the librarians where the people most keen
on moving to gitlab.
On Wed, 27 Nov 2019 at 21:39, Seth Hillbrand wrote:
> On 11/27/19 11:42 AM, Rene Pöschl wrote:
>
> On 26/11/2019 21:54, Seth Hillbrand wrote:
>
> On
"disable deprecation warnings in Debug
>> build, change message in fp_lib_table.cpp," so I don't know what the actual
>> reasoning behind the change was.
>>
>> -Ian
>>
>> On Sat, Dec 28, 2019 at 2:18 PM Nick Østergaard
>> wrote:
>>
>>&g
What does the git log tell you?
I once did it in my build scripts because of:
# Add flag to silence deprecation warnings
# Due to bug in gcc 5.1,5.2
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65974
So it would spew out a tremendous amount of unrelated warnings and was
useless. Maybe it was
Ok, everything should be resolved now.
On Tue, 24 Dec 2019 at 15:48, Nick Østergaard wrote:
>
> It does not look like there is an issue at CERN. I asked Ajo to check.
>
> On Tue, 24 Dec 2019 at 15:16, wrote:
> >
> > I can confirm that dig reports a server fail but th
It does not look like there is an issue at CERN. I asked Ajo to check.
On Tue, 24 Dec 2019 at 15:16, wrote:
>
> I can confirm that dig reports a server fail but that is at the GoDaddy DNS
> server not the web hosting.
>
> -Seth
>
> On Dec 24, 2019 5:01 AM, Ian McInerney wrote:
>
> Is there a
Thank you for reporting, I will check it.
On Thu, 19 Dec 2019 at 01:42, Ian McInerney wrote:
>
> It appears that the Doxygen for the developer documentation
> (https://docs.kicad-pcb.org/doxygen/index.html) is not updating the site, and
> the last update looks to be November 17.
>
> -Ian
>
As far as I understand it the non-extra version is not supposed to be
modified by the user/packager. So only adding custom stuff to the
_EXTRA is supposed to work "right".
On Tue, 17 Dec 2019 at 21:29, Steven A. Falco wrote:
>
> On 12/17/19 3:13 PM, Ian McInerney wrote:
> > Is the version string
I think the thumbs up is a good enough indicator of interest in an issue.
On Thu, 5 Dec 2019 at 11:58, Ian McInerney wrote:
>
> The weight field is the value that Launchpad displayed for the "flame" icon.
> I am not sure if normal users are able to modify that field though, so we are
>
s the process? As I
> said, I'm not very familiar with the code base and I couldn't find files for
> the existing worksheets in that dialog when I looked around; but if I can get
> a few pointers about what to do I would be happy to submit a PR.
>
> On Sun, Dec 1, 2019, 2:51 PM
Are you re-adding it under code?
On Mon, 2 Dec 2019 at 05:38, Seth Hillbrand wrote:
>
> On 2019-12-01 13:43, Nick Østergaard wrote:
>
> > The one under code
> >
> > søn. 1. dec. 2019 22.40 skrev Steven A. Falco :
> >
> >> I see two separate proj
at doesn't require that
> if it becomes a problem for me, but I thought I'd let the list know
> just in case no-one's aware.
>
> Thanks,
> Tedd
>
> On Fri, 29 Nov 2019 at 20:17, Nick Østergaard wrote:
> >
> > What are you asking?
> >
> > On Fri, 29 Nov 201
It uses -G "Visual Studio 15 2017" as the generator.
On Sun, 1 Dec 2019 at 23:45, Jon Evans wrote:
>
> What environment does that build use? My patches were necessary for VS2019
> using default compiler settings
>
> On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote:
&g
he entire
> list so maybe I got it wrong.
>
> On 12/1/19 5:34 PM, Nick Østergaard wrote:
> > The templates are packaged like everything else with cmake, so if it is
> > not included it is a bug in the templates repo.
> >
> > On Thu, 28 Nov 2019 at 03:16, Ian McInerney
The templates are packaged like everything else with cmake, so if it is not
included it is a bug in the templates repo.
On Thu, 28 Nov 2019 at 03:16, Ian McInerney
wrote:
> They appear to be packaged in the update to Fedora, but I don't have a
> Windows install handy to test on to verify what I
Oh, ok. Then I wonder why Jon needed to patch it.
On Sun, 1 Dec 2019 at 20:14, Simon Richter wrote:
>
> Hi Nick,
>
> On 01.12.19 20:07, Nick Østergaard wrote:
>
> > OK, cool, it looks like the msvc builds on jenkins are back in green again
> > :)
>
> >
OK, cool, it looks like the msvc builds on jenkins are back in green again :)
https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
On Sat, 30 Nov 2019 at 03:19, Jon Evans wrote:
>
> Hi Brian,
>
> I will try to write a better guide, especially if I can get a full (all
> options) KiCad
I have not seen any packaging scripts depend on it, if it does I think it
is fair for the package to be updated, but isn't it alreade handled by the
make install step?
fre. 29. nov. 2019 12.59 skrev Ian McInerney :
> Thanks for the feedback.
>
> Steve, I won't be changing anything about how the
What are you asking?
On Fri, 29 Nov 2019 at 10:44, tedd.t...@gmail.com wrote:
>
> Hi all,
>
> Just a quick note in case no-one's aware. I remember before the move
> to CERN's infrastructure, the server hosting all the builds had a
> script to delete old testing builds, presumably to keep space
I think all of the PPA build definitions are on Jean-Samuels account on
launchpad. I think this repo is used for the nightlies:
https://code.launchpad.net/~js-reynaud/+git/kicad-daily-pkg
I think you can make a merge request on lp.
On Wed, 27 Nov 2019 at 21:46, Seth Hillbrand wrote:
> Hi All-
he
> size of the window. If we need to abbreviate to prevent layout issues,
> that's fine.
>
> On 11/27/19 9:16 AM, Nick Østergaard wrote:
> > Maybe to keep the button name short use the strings:
> > Donate via TLF
> > Donate via CERN
> >
> > ons. 27. nov.
Maybe to keep the button name short use the strings:
Donate via TLF
Donate via CERN
ons. 27. nov. 2019 15.06 skrev Wayne Stambaugh :
> Hi Mark,
>
> I noticed you made some changes to the latest donations window which are
> definitely an improvement. I'm wondering if we should also change the
>
gt; to complete this today? I was also planning on making announcements on
> some other platforms (Launcpad, User Forum, Twitter, etc.) as well so
> please ping me when you undraft the release announcement.
>
> Cheers,
>
> Wayne
>
> On 11/27/19 5:24 AM, Nick Østerga
Would it be to controversial to just call it fpedit and symedit? I am not
sure I understand why you wanted the hyphen, but I didn't really follow the
discussion to much in this thread. What are the other multiword tags in
gitlab?
On Wed, 27 Nov 2019 at 12:13, Ian McInerney wrote:
> I was trying
ready is a deep queue for
> >>> nightlies, and in the morning I'll upload them to downloads and let
> >>> Wayne know so we can announce. Thanks everyone!
> >>>
> >>> Adam
> >>>
> >>> On Mon, Nov 25, 2019 at 7:05 PM
Mm, no, just two factor auth, this is not about signed commits.
man. 25. nov. 2019 15.09 skrev Wayne Stambaugh :
> Hi Mark,
>
> Do you mean using a GPG key? I see the gitlab supports signed commits
> so would that be an adequate solution? I'm fine with this, it's
> probably something we should
It looks good to me :)
søn. 24. nov. 2019 02.50 skrev Mark Roszko :
> The attempt I took on adding TLF is live.
>
> On Sat, Nov 23, 2019 at 8:45 AM Wayne Stambaugh
> wrote:
>
>> Hi Sujith,
>>
>> I got it. Thank you.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 11/22/19 10:09 PM, Sujith Anandan wrote:
>>
I don't know, but I have https://gitlab.com/kicad_eda that I have been
using as a playground.
søn. 24. nov. 2019 15.42 skrev Seth Hillbrand :
> Hi All-
>
> As you have heard, we are moving from Launchpad to GitLab. However, we
> have been unable to secure the https://www.gitlab.com/kicad group
On Fri, 22 Nov 2019 at 18:03, Wayne Stambaugh wrote:
>
> I just pushed a blog post to the KiCad website that KiCad has joined the
> Linux Foundation so consider this the official announcement. The
> project did this to give donors a choice of how they want to donate to
> KiCad and it gives us
5.1.5 is fairly well rolled out now, thanks to various good people :)
To make the release official, I think we are only needing the macos
build. @Adam Wolf if you need any help, please speak up.
Nick
On Wed, 20 Nov 2019 at 19:33, Steven A. Falco wrote:
>
> Fedora Rawhide has 5.1.5 now.
It seems to build ok for linux on jenkins.
Maybe double chevk you are not in a merge state or something. Also, please
state the has of the version you are trying to build.
ons. 20. nov. 2019 11.34 skrev Jonatan Liljedahl :
> Hi, I'm trying to build the current master, cmake configured like
101 - 200 of 1927 matches
Mail list logo
