Re: [Kicad-developers] How to redefine default system footprint/symbols/packages3d/templates search paths at build time?

[Nick Østergaard]

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 templates)
> KICAD_SYMBOL_DIR (the eeschema symbols)
> KISYSMOD (the modules)
> KISYS3DMOD (the 3d models)
>
> -Ian
>
>
>
> On Sat, May 23, 2020 at 8:50 PM Johannes Maibaum 
> wrote:
>
>> Hello KiCad developers,
>>
>> TL;DR:
>> How can I redefine the default system
>> footprint/symbols/packages3d/templates base search paths at build time
>> using CMake options, so that KISYSMOD, KISYS3DMOD, KICAD_SYMBOL_DIR, and
>> KICAD_TEMPLATE_DIR all point to the directories:
>>
>> $PREFIX/data/share/kicad/{modules,modules/packages3d,symbols,templates}
>>
>> instead of:
>>
>> $PREFIX/share/kicad/{modules,modules/packages3d,symbols,templates}?
>>
>>
>> Longer version:
>>
>> First a quick update from flatpak land:
>>
>> This week I merged the update to KiCad 5.1.6, fixed the ngspice
>> simulator in Eeschema, activated Python scripting, and added user
>> documentation to the KiCad flatpak. This means that flatpak users by now
>> get a KiCad experience that should support close to all features that
>> the software package offers.
>>
>> But what I would like to do in order to make the installed size
>> (currently 6.2GB, mostly due to the 3D packages) a little bit more
>> controllable from the user perspective [1] is to move the footprint,
>> symbols, 3D models, and templates into separate "flatpak app extensions"
>> which can then be installed or removed independently of the main
>> application.
>>
>> The way flatpak extensions work is that you basically define an
>> "extension mount point" inside your main flatpak (I chose /app/data) for
>> whatever files and directories an installed extension wants to add into
>> the bundle.
>>
>> I have set up those library extensions already, and they are being
>> mounted correctly inside the flatpak at runtime, but so far I wasn't
>> able to configure KiCad correctly to use this mount point as base dir
>> for the data files.
>>
>> So far, I have tried either -DDEFAULT_INSTALL_PATH=/app/data or
>> -DCMAKE_INSTALL_DATADIR=/app/data during CMake configuration in two
>> different test builds (as those two options were appearing in
>> CMakeLists.txt and the surrounding lines seemed to indicate that they
>> were doing what I was trying to achieve).
>>
>> Yet, none of the two did change anything (though I didn't try using both
>> together yet) regarding to the KiCad system paths. This is what I see in
>> "Preferences->Configure Paths" with or without redefining the CMake
>> options:
>>
>> KICAD_SYMBOL_DIR=/app/share/kicad/library
>> KICAD_TEMPLATE_DIR=/app/share/kicad/template
>> KISY3DSMOD=/app/share/kicad/modules/packages3d
>> KISYSMOD=/app/share/kicad/modules
>>
>> I saw further CMake options which are all marked as advanced, thus I did
>> not try them yet.
>>
>> Is there a way to achieve what I want to do with the current set of
>> CMake switches or would this need deeper plumbing?
>>
>>
>> Here's my current CMake setup:
>>
>> "config-opts": [
>> "-DBOOST_ROOT=/app",
>> "-DDEFAULT_INSTALL_PATH=/app/data",
>> "-DGLEW_INCLUDE_DIR=/app/include/GL",
>> "-DOPENGL_glu_LIBRARY=/app/lib/libGLU.so",
>> "-DKICAD_BUILD_QA_TESTS=OFF",
>> "-DKICAD_SCRIPTING_PYTHON3=ON",
>> "-DKICAD_SCRIPTING_WXPYTHON_PHOENIX=ON"
>> ]
>>
>> (--prefix=/app is the default in flatpak land).
>>
>>
>> And version info:
>>
>> Application: KiCad
>> Version: 5.1.6, release build
>> Libraries:
>> wxWidgets 3.0.5
>> libcurl/7.65.3-DEV GnuTLS/3.6.13 (NSS/3.46.1) (OpenSSL/1.1.1d)
>> zlib/1.2.11 libidn2/2.2.0
>> Platform: Linux 5.6.14-arch1-1 x86_64, 64 bit, Little endian, wxGTK
>> Build Info:
>> wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8) GTK+
>> 3.24
>> Boost: 1.66.0
>> OpenCASCADE Community Edition: 6.9.1
>> Curl: 7.65.3-DEV
>> Compiler: GCC 9.2.0 with C++ ABI 1013
>>
>> Build settings:
>> USE_WX_GRAPHICS_CONTEXT=OFF
>> USE_WX_OVERLAY=ON
>> KICAD_SCRIPTING=ON
>> KICAD_SCRIPTING_MODULES=ON
>> KICAD_SCRIPTING_PYTHON3=ON
>> KICAD_SCRIPTING_WXPYTHON=ON
>> KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
>> KICAD_SCRIPTING_ACTION_MENU=ON
>> BUILD_GITHUB_PLUGIN=ON
>> KICAD_USE_OCE=ON
>> KICAD_USE_OCC=OFF
>> KICAD_SPICE=ON
>>
>>
>>
>> Cheers,
>> Johannes
>>
>>
>> [1] To quote a user: "KiCad is AFAIK the biggest flatpak on Flathub" (
>>
>> https://github.com/flathub/org.kicad_pcb.KiCad/issues/19#issuecomment-632761066
>> )
>>
>>
>> ___
>> 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] KiCad website

[Nick Østergaard]

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 completely different today on Firefox and Chrome (see
> attached screen shot).  Clicking on the topic links doesn't even take me
> to the correct page.
>
> Thanks,
>
> 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] [PATCH] Add remote lib retrieval to SCH_LEGACY_PLUGIN_CACHE

[Nick Østergaard]

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 :)
>
> Regards,
>
> Badr
>
> Le 2018-10-30 11:07, Badr Hack a écrit :
>
> Hi Wayne,
>
> Did you have a chance to give a look at this patch?
> From our side we are using it almost a year now, it works fine.
>
> Else, I don't know if an equivalent function is now under going in the
> version 6?
> If so, I will be glad to help in testing.
>
> Regards,
>
> Badr
>
> Le 2017-12-24 15:31, Wayne Stambaugh a écrit :
>
> Badr,
>
> Thank you for your patch but we are currently in feature freeze for the
> stable 5 release.  This patch will have to wait until the stable 5
> version is release and the version 6 development is opened.  I'm not
> sure exactly when that will happen but I will review your patch then.
>
> Cheers,
>
> Wayne
>
> On 12/24/2017 05:56 AM, Badr Hack wrote:
>
> Hi,
> Here is a patch to add the remote library management as a plugin.
> I added the possibility to specify multiple urls  in a single file, it
> was useful for our case.
> We tested this approach several weeks, it seems fine in term of
> performance.
> It doesn't support remote zip files as for pcbnew. I can manage to
> implement it in a second time.
> If this patch is ok I will write a detailed documentation on how to use it.
> Regards,
> Badr
>
>
> Le 2017-08-14 15:21, Wayne Stambaugh a écrit :
>
> You could modify the SCH_LEGACY_PLUGIN_CACHE code to handle urls instead
> of file names.  That way you could hand remote and local files in the
> same plugin.  wxWidgets has classes to handle urls (wxUrl) and input
> streams (wxInputStream) which can be use as the LINE_READER
> (INPUTSTREAM_LINE_READER takes a pointer to a wxInputStream object).
> The primary drawback to this is performance.  Past testing has shown
> that wxInputStream has a lot more overhead and is significantly slower
> than either our FILE_LINE_READER and std::istream so that is why we
> haven't used it anywhere.  It is also why I recommended writing a new
> plugin.  I'm guessing with remote I/O, the wxInputStream performance hit
> will be far less noticeable than the remote I/O time.
>
> Wayne
>
> On 8/14/2017 3:29 AM, Badr Hack wrote:
>
> I see,
> I thought it would be better to upgrade SCH_LEGACY_PLUGIN_CACHE to
> handle remote libraries seemlessly rather than creating a new plugin.
> I will check how to add a new plugin for remote libs without adding
> additional actions for the user.
>
> Badr
>
> Le 2017-08-14 02:44, Wayne Stambaugh a écrit :
>
> I think you misunderstood what I was implying.  You should not be
> looking for a different symbol library header.  This is a change that I
> would reject since you are effectively changing the library file
> format.
>  What I suggested was that you create new plugin that reads from a
> remote url similar to the github plugin used for footprint libraries.
>
> I also do not like the idea of a separate LoadRemote() method being
> added to the SCH_PLUGIN object.  There is no reason to add it.  All of
> the symbol library methods take a wxString which could be a url instead
> of a file name.  It is not limited to files and up to the plugin
> type to
> handle it correctly.  My preference is that you create a new plugin for
> remote files similar in concept to the github plugin.  That is the
> whole
> point of the current plugin interface.  Take a look at the board
> plugins
> to see the preferred method of creating plugins.
>
> I never really intended for the legacy symbol file format to have
> multiple plugins like the kicad board and footprint library file
> formats
> so I didn't create separate parser and formatter objects like I did
> with
> the board file formats.  Nothing is preventing that from happening with
> the current schematic and symbol library file formats.  I would not
> have
> any objection to splitting the parser out of the
> SCH_LEGACY_PLUGIN_CACHE
> object.  I am planning on make the parsers and formatters for the new
> schematic and symbol library file format code separate so it can be
> used
> by any plugin.
>
> Cheers,
>
> Wayne
>
> On 8/13/2017 3:26 PM, Badr Hack wrote:
>
> Hi,
>
> Here in the attachment the patch that add the remote lib retrieval.
>
> Badr
> Le 2017-08-13 17:29, Badr Hack a écrit :
>
> Hi,
>
> Those couple of days I was checking how to update EESCHEMA to add
> remote libraries retrieval function.
>
> Since am familiar with legacy format, I updated the plugin:
> SCH_LEGACY_PLUGIN_CACHE in charge of parsing the *.lib files.
>
> The idea was to create a new type of library
> EESchema-REMOTELIBRARY (I
> put an example in the attachment)
> The content of this library is the following:
> EESchema-REMOTELIBRARY Version 1.0
> URL https://www.example.com/mylib1.lib
> URL https://www.example.com/mylib2.lib
> ...
>

Re: [Kicad-developers] Build on msys2 fails : libngspice-x.dll not found in any executable path

[Nick Østergaard]

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 one of the packages is updated during script run
you MUST restart MSYS2"

After this, please try a clean (read new) build dir and run cmake afresh.

Nick

[1] https://www.msys2.org/wiki/MSYS2-installation/

On Wed, 20 May 2020 at 03:53, Brian Piccioni
 wrote:
>
> Hello
>
> I updated Msys2 (pacman -Syuu) and it borked the terminal (basically when 
> building the nice percentages, etc., became more or less random  strings).
>
> I decided to reinstall Msys2. I wiped the directory and reinstalled.
>
> After doing so and following the directions at 
> https://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html#build_windows
>
> cmake -DCMAKE_BUILD_TYPE=Release \
>   -G "MSYS Makefiles" \
>   -DCMAKE_PREFIX_PATH=/mingw64 \
>   -DCMAKE_INSTALL_PREFIX=/mingw64 \
>   -DDEFAULT_INSTALL_PATH=/mingw64 \
>   ../../
>
> Fails with
>
> -- Found Boost: C:/msys64/mingw64/include (found suitable version "1.72.0", 
> minimum required is "1.59.0")
> ERROR:
> * libngspice-x.dll not found in any executable path *
>
>
> CMake Error at 
> C:/msys64/mingw64/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164
>  (message):
>   Could NOT find ngspice (missing: NGSPICE_DLL)
> Call Stack (most recent call first):
>   
> C:/msys64/mingw64/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445
>  (_FPHSA_FAILURE_MESSAGE)
>   CMakeModules/Findngspice.cmake:63 (find_package_handle_standard_args)
>   CMakeLists.txt:628 (find_package)
>
> 
>
> However, I do have C:\msys64\mingw64\bin\libngspice-0.dll and my path is 
> PATH=C:\msys64;C:\msys64\mingw64\bin; ... (in the cmake file there is a remark
>
> # Note: libngspice-0.dll or libngspice-1.dll must be in a executable path
>
>
> Any suggestions how to fix this would be appreciated.
>
>
>
> ___
> 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] Requesting maintainership for KiCad manifest on flathub.org

[Nick Østergaard]

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 the flatpak is, nor do I think he may 
> follow this list closely.
>
>
> From what I can say, so far the flatpak has been maintained by whoever sent 
> in a PR, and it was updated whenever one of the main flathub maintainers 
> found time to review the PR.
>
> Johannes
>
>
> 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 months, I have been updating the KiCad flatpak on
> flathub.org from time to time, via PRs to
> https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> update to KiCad 5.1.6 right now as well).
>
> There are a few pending issues with the current flatpak build manifest
> for KiCad which I'd like to address: Activating Python scripting
> support, adding the docs, and generally updating various dependencies
> would be my next steps.
>
> I was recently being asked by another user if I would like to request
> the maintainership of the KiCad manifest on flathub, and I am now
> contemplating to do so. But, since I did only contribute a few tiny-tiny
> things to KiCad in the past, I wanted to ask the core
> packagers/developers first, if anyone else would take over the
> maintainership instead?
>
>
> Cheers,
> Johannes
> ___
> 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] Build Server for MacOS

[Nick Østergaard]

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 yet.

Nick

On Mon, 18 May 2020 at 19:17, S.Weber  wrote:
>
> Hello KiCad team,
>
> I am new to kicad and was thinking about helping with the MacOS CI.
>
> Ian McInerney was mentioning on 
> https://gitlab.com/kicad/code/kicad/-/merge_requests/218 that "currently 
> there are no reliable macOS CI solutions for KiCad".
>
> >We don't currently have a reliable macOS CI solution. GitLab doesn't provide 
> >one out of the box, and the nightly build server sometimes has issues that 
> >aren't related to the code, but instead to packaging.
>
> I am wondering if someone is working on a "new" macOS CI or do have some 
> experience there?
>
> I found two CIs provider which are free for MacOS open-source Projects:
>
> https://travis-ci.com/plans
>
> https://www.appveyor.com/pricing/
>
> => appveyor seems to directly support gitlab
> => travis only supports github => build needs to go over github mirror of 
> kicad repo..
>
> So I think appveyor might be worth a try.
>
> What do you think?
>
>
> Stefan
>
> ___
> 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] no broken default fp-lib-table, removed footprint library

[Nick Østergaard]

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 has some dedicated information for upstream projects and coders
> of course.
>
> https://wiki.debian.org/UpstreamGuide
>
> But these are all plain technically points written down. You will not
> find any issues for the main KiCad application based on the list from
> the Debian wiki and that's good.
>
> > Packaging is import to the project so if we can package devs lives a bit
> > easier, I'm willing to consider ways to do so.
>
> We are going in loops so I currently don't want to put more energy into
> a for me pointless discussion. And it's also disappointing and not
> encouraging if people saying they haven't read my complete message(s) ...
>
> The main point is that projects simply should provide as much
> information and communication as possible about the new versions they
> provide. Distributions need always to think about how intrusive
> modifications are, that's mainly a simple risk analysis.
>
> What do you think if a contributor is providing a 1000 line patch for
> KiCad and you have no further information than that pure diff?
> That's mainly the situation for me regarding to symbols and footprints.
>
> The release of a new KiCad version can be improved in my eyes by doing a
> better job of release managing. For example some parts do create release
> candidates some don't. Makes it difficult for me to do packaging
> preparations as the final version of the kicad package says then nothing
> about the real combined l10n and documentation parts as I need to pick
> up some random versions. Also not helpful if users bring up issues as
> you need to figure out against what commits these are for real.
>

There were probably no -rc tag for i18n and the doc, but I didn't see
you pointing it out in time either.

> --
> Regards
> Carsten
>
> ___
> 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] Requesting maintainership for KiCad manifest on flathub.org

[Nick Østergaard]

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 months, I have been updating the KiCad flatpak on
> flathub.org from time to time, via PRs to
> https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> update to KiCad 5.1.6 right now as well).
>
> There are a few pending issues with the current flatpak build manifest
> for KiCad which I'd like to address: Activating Python scripting
> support, adding the docs, and generally updating various dependencies
> would be my next steps.
>
> I was recently being asked by another user if I would like to request
> the maintainership of the KiCad manifest on flathub, and I am now
> contemplating to do so. But, since I did only contribute a few tiny-tiny
> things to KiCad in the past, I wanted to ask the core
> packagers/developers first, if anyone else would take over the
> maintainership instead?
>
>
> Cheers,
> Johannes
> ___
> 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.6 Release Update

[Nick Østergaard]

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 
>> (non-testing/nightly) releases. I would think that in this case users would 
>> want the updated libraries.
>>
>> -Ian
>>
>
> The lite installers are are very important for nightly and testing packages 
> which users may download daily. Not as much for stable releases which are 
> downloaded usually once in a couple of months or so.
>
> Eeli Kaikkonen
> ___
> 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 CMake Version Bump to 3.2

[Nick Østergaard]

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 discussed the
> version bump at length inside
> https://gitlab.com/kicad/code/kicad/-/merge_requests/167, and decided to
> only bump the minimum needed to fix the issue (which is to 3.2), and all
> our supported platforms have CMake versions larger than this (and we
> maintain compatibility with Ubuntu 16.04 for those users still using it).
>
> A similar bump happened on Master a week or so ago, and no problems have
> been reported because of it.
>
> -Ian
> ___
> 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.6 Release Update

[Nick Østergaard]

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 
> download.
> But probably many like me never install libraries anyway (I have official 
> libs in separate git checkout).
>
> On Fri, May 15, 2020 at 4:35 AM 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 
>> (non-testing/nightly) releases. I would think that in this case users would 
>> want the updated libraries.
>>
>> -Ian
>>
>> On Fri, May 15, 2020 at 12:33 PM Andrew Lutsenko  
>> wrote:
>>>
>>> Windows 5.1.6 builds seem to be uploaded as well but no lite release?
>>> https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/stable/
>>>
>>> On Fri, May 15, 2020 at 2:59 AM Jean-Samuel Reynaud  
>>> wrote:

 KiCad 5.1.6 is now available on Ubuntu PPA since 2 days.

 And some statistics on May 2020:

 By Ubuntu version (only for 5.1 download):
 Focal (20.04)  499.00 ( 8%)
 Eoan (19.10)   389.00 ( 6%)
 Bionic (18.04)4753.00 (76%)
 Xenial (16.04) 582.00 ( 9%)
 Totals6223.00





 Le 15/05/2020 à 04:56, Adam Wolf a écrit :
 > Mac builds have been uploaded, just the same as all the other 5.1
 > releases.  Have a good weekend, everyone!
 >
 > On Wed, May 13, 2020 at 3:48 PM Kevin Cozens  wrote:
 >>
 >> On 2020-05-13 4:11 p.m., Rene Pöschl wrote:
 >>> You must pull the tagged commit otherwise you get whatever got merged 
 >>> last.
 >>
 >> Ok, thank you. With the v6 libraries no longer compatible with v5 I was
 >> expecting to see a branch, not just a tag. Does this mean the v5 
 >> libraries
 >> are no longer being maintained or will they be branched later if a 
 >> change is
 >> required to a v5 library?
 >>
 >> --
 >> Cheers!
 >>
 >> Kevin.
 >>
 >> http://www.ve3syb.ca/   | "Nerds make the shiny things that
 >> https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
 >>  | that's why we're powerful"
 >> Owner of Elecraft K2 #2172  |
 >> #include  | --Chris Hardwick
 >>
 >> ___
 >> 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
>
> ___
> 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] ngspice-32

[Nick Østergaard]

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 KiCAD/Eeschema examples (official and private
> ones). Everything is o.k. so far.
>
> Fedora, Debian and Ubuntu already have a build in their recent testing
> distributions.
>
>
> Holger
>
>
>
> ___
> 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.6 docs tarball?

[Nick Østergaard]

@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
>
> You can specify a different file extension if you prefer something other than 
> bzip2.
>
> Since gitlab is where kicad-doc is source-controlled, that seems like a good 
> way to grab the tar.
>
> Steve
>
>
> On 5/14/20 10:27 AM, Adam Wolf wrote:
> > Odd.  It definitely is there. Thanks!  Everyone else, please disregard.
> >
> > Adam
> >
> > On Thu, May 14, 2020 at 9:25 AM Christoph Moench-Tegeder
> >  wrote:
> >>
> >> ## Adam Wolf (adamw...@feelslikeburning.com):
> >>
> >>> The Mac release packaging uses a tarball that has been located at
> >>> https://kicad-downloads.s3.cern.ch/docs/kicad-doc-5.1.x.tar.gz.  It
> >>> does not seem like the 5.1.6 tarball is up yet.
> >>
> >> It's there:
> >> ===>  License GPLv3+ CC-BY-3.0 accepted by the user
> >> ===>   kicad-doc-5.1.6 depends on file: /usr/local/sbin/pkg - found
> >> => kicad-doc-5.1.6.tar.gz doesn't seem to exist in 
> >> /fs/poudriere/ports/commit/distfiles/.
> >> => Attempting to fetch 
> >> https://kicad-downloads.s3.cern.ch/docs/kicad-doc-5.1.6.tar.gz
> >> kicad-doc-5.1.6.tar.gz 302 MB 9660 kBps
> >> 32s
> >> ===> Fetching all distfiles required by kicad-doc-5.1.6 for building
> >>
> >> Regards,
> >> Christoph
> >>
> >> --
> >> Spare Space
> >>
> >> ___
> >> 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] v6 breaking changes to eeschema - starting new refactor wise?

[Nick Østergaard]

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 assuming you mean changes yet to come and not
> broken changes which is something all together different.  I don't
> foresee any changes that would significantly impact the annotation code
> if any at all so you are probably safe to work on it.  I highly
> recommend that write up a simple proposal either on your GitLab instance
> or something like Google docs so that the lead dev team can comment.
> This helps to prevent you from wasting your time by implementing
> something that get rejected by the dev team.
>
> I am surprised you think the annotation code looks deceptively simple.
> I'm still trying to wrap my head around all of the potential sheet path
> issues and I've written and/or refactored most of that code.  I don't
> think anyone has gotten this right the first time including myself.
>
> All that being said, I think most users would find more advanced
> annotation options useful so I would be in favor of it.
>
> Cheers,
>
> Wayne
>
> On 5/12/20 12:36 PM, James Jackson wrote:
> > Hi all,
> >
> > I'm starting to dig through the code to understand how to implement a
> > new annotation scheme (all looks deceptively simple in terms of object
> > manipulation... there will be a crocodile hiding there somewhere I'm
> > sure!). However, I've noted in a few bug reports and new feature
> > requests that there are likely to be significant changes to eeschema
> > moving towards v6 (last reference I saw was in relation to vector and
> > group busses). So, is it wise to start looking at a significant feature
> > now (if the big changes have happened already), or wait until those
> > changes are made, or is this not actually an issue? Just trying to avoid
> > wasting effort and then have to re-duplicate it later!
> >
> > Thanks,
> > James.
> >
> > ___
> > 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.6 Release Update

[Nick Østergaard]

Awesome, thanks for the update.  I better trigger the windows build as well.

On Tue, 12 May 2020 at 23:30, Steven A. Falco  wrote:
>
> Thanks Nick.  I've started the builds on Fedora Koji.  The rawhide build is 
> done, and will become available on the next successful rawhide compose.
>
> 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.
>
>     Steve
>
> On 5/12/20 10:36 AM, Nick Østergaard wrote:
> > 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
> > https://gitlab.com/kicad/code/kicad-i18n
> > https://gitlab.com/kicad/services/kicad-doc
> >
> > That should be everything
> >
> > On Tue, 12 May 2020 at 16:23, Steven A. Falco  wrote:
> >>
> >> I'd like to clarify which pieces come from where.  The old list was:
> >>
> >> https://launchpad.net/kicad/5.0
> >> https://github.com/KiCad/kicad-doc
> >> https://github.com/KiCad/kicad-i18n
> >> https://github.com/KiCad/kicad-templates
> >> https://github.com/KiCad/kicad-symbols
> >> https://github.com/KiCad/kicad-footprints
> >> https://github.com/KiCad/kicad-packages3D
> >>
> >> I grabbed the 5.1.6 archives for kicad and kicad-i18n from gitlab - no 
> >> problem:
> >>
> >> https://gitlab.com/kicad/code/kicad/-/archive/5.1.6/kicad-5.1.6.tar.bz2
> >> https://gitlab.com/kicad/code/kicad-i18n/-/archive/5.1.6/kicad-i18n-5.1.6.tar.bz2
> >>
> >> But what about the other five pieces? (kicad-doc, kicad-templates, 
> >> kicad-symbols, kicad-footprints, kicad-packages3D).  Are they all still on 
> >> github at this point, or have any of them moved to gitlab?
> >>
> >>  Steve
> >>
> >>
> >> On 5/11/20 3:19 PM, Wayne Stambaugh wrote:
> >>> Thanks Rene.  I just tagged 5.1.6 in the repo so once the doc and
> >>> translations are tagged we should be ready to fire up the package 
> >>> builders.
> >>>
> >>> On 5/11/20 3:15 PM, Rene Pöschl wrote:
> >>>> Hi,
> >>>>
> >>>> library is tagged. Some bugfixes on the symbol lib again result in
> >>>> changes that would break an existing schematic.
> >>>>
> >>>> See details in issue comment:
> >>>> https://github.com/KiCad/kicad-symbols/issues/2656#issuecomment-626880880
> >>>>
> >>>> On 10/05/2020 18:07, Wayne Stambaugh wrote:
> >>>>> Since we are only a week away (Friday) from the proposed 5.1.6 release
> >>>>> date and none of the critical bugs seem to be reproducible,  I would
> >>>>> like to tag the 5.1 branch tomorrow along with the other repos so we
> >>>>> have time to allow the package builders to complete and website download
> >>>>> page to be updated by Friday so I can make the official announcement.
> >>>>> Is there anything else holding us back from this before I tag 5.1.6 in
> >>>>> the repo?
> >>>>>
> >>>>> 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
>

___
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.6 Release Update

[Nick Østergaard]

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
https://gitlab.com/kicad/code/kicad-i18n
https://gitlab.com/kicad/services/kicad-doc

That should be everything

On Tue, 12 May 2020 at 16:23, Steven A. Falco  wrote:
>
> I'd like to clarify which pieces come from where.  The old list was:
>
> https://launchpad.net/kicad/5.0
> https://github.com/KiCad/kicad-doc
> https://github.com/KiCad/kicad-i18n
> https://github.com/KiCad/kicad-templates
> https://github.com/KiCad/kicad-symbols
> https://github.com/KiCad/kicad-footprints
> https://github.com/KiCad/kicad-packages3D
>
> I grabbed the 5.1.6 archives for kicad and kicad-i18n from gitlab - no 
> problem:
>
> https://gitlab.com/kicad/code/kicad/-/archive/5.1.6/kicad-5.1.6.tar.bz2
> https://gitlab.com/kicad/code/kicad-i18n/-/archive/5.1.6/kicad-i18n-5.1.6.tar.bz2
>
> But what about the other five pieces? (kicad-doc, kicad-templates, 
> kicad-symbols, kicad-footprints, kicad-packages3D).  Are they all still on 
> github at this point, or have any of them moved to gitlab?
>
> Steve
>
>
> On 5/11/20 3:19 PM, Wayne Stambaugh wrote:
> > Thanks Rene.  I just tagged 5.1.6 in the repo so once the doc and
> > translations are tagged we should be ready to fire up the package builders.
> >
> > On 5/11/20 3:15 PM, Rene Pöschl wrote:
> >> Hi,
> >>
> >> library is tagged. Some bugfixes on the symbol lib again result in
> >> changes that would break an existing schematic.
> >>
> >> See details in issue comment:
> >> https://github.com/KiCad/kicad-symbols/issues/2656#issuecomment-626880880
> >>
> >> On 10/05/2020 18:07, Wayne Stambaugh wrote:
> >>> Since we are only a week away (Friday) from the proposed 5.1.6 release
> >>> date and none of the critical bugs seem to be reproducible,  I would
> >>> like to tag the 5.1 branch tomorrow along with the other repos so we
> >>> have time to allow the package builders to complete and website download
> >>> page to be updated by Friday so I can make the official announcement.
> >>> Is there anything else holding us back from this before I tag 5.1.6 in
> >>> the repo?
> >>>
> >>> 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

___
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] New schematic and symbol library file formats

[Nick Østergaard]

github for now

tor. 7. maj 2020 15.55 skrev Wayne Stambaugh :

> I just made some changes to the blog post to reflect a code change.  Are
> we still using the GitHub repo or have we migrated the website to the
> GitLab repo?
>
> On 5/6/20 10:59 PM, Mark Roszko wrote:
> > I 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 at 23:11, Wayne Stambaugh  > <mailto:stambau...@gmail.com>> 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 just copy paste from the forum post
> > more
> > > > or less and then you can edit it if you want.
> > > >
> > > > On Wed, 6 May 2020 at 22:56, Wayne Stambaugh
> > mailto:stambau...@gmail.com>> wrote:
> > > >>
> > > >> It's on my short list.  I planned on having it done already but
> > I've
> > > >> been busy fixing bugs so it got pushed back 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
> > mailto:stambau...@gmail.com>> wrote:
> > > >>>>
> > > >>>> For those nightly build users, the merge request to make the
> new
> > > >>>> schematic and symbol library file formats the default file
> > format was
> > > >>>> merged so builds should soon be available.  I wrote a detailed
> > > >>>> description on the KiCad user forum[1] if you are interested
> > in the
> > > >>>> changes.  Please test it and report any bugs so I can get
> > this stable as
> > > >>>> quickly as possible so we can start to add new features.
> > > >>>>
> > > >>>> Cheers,
> > > >>>>
> > > >>>> Wayne
> > > >>>>
> > > >>>> [1]:
> > > >>>>
> >
> https://forum.kicad.info/t/kicad-nightly-v5-99-new-schematic-and-symbol-library-file-formats-are-now-the-default/22655
> > > >>>>
> > > >>>> ___
> > > >>>> Mailing list: https://launchpad.net/~kicad-developers
> > > >>>> Post to : kicad-developers@lists.launchpad.net
> > <mailto: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
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> > --
> > Mark
>
___
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] New schematic and symbol library file formats

[Nick Østergaard]

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: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 just copy paste from the forum post more
>> > > or less and then you can edit it if you want.
>> > >
>> > > On Wed, 6 May 2020 at 22:56, Wayne Stambaugh 
>> wrote:
>> > >>
>> > >> It's on my short list.  I planned on having it done already but I've
>> > >> been busy fixing bugs so it got pushed back 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:
>> > >>>>
>> > >>>> For those nightly build users, the merge request to make the new
>> > >>>> schematic and symbol library file formats the default file format
>> was
>> > >>>> merged so builds should soon be available.  I wrote a detailed
>> > >>>> description on the KiCad user forum[1] if you are interested in the
>> > >>>> changes.  Please test it and report any bugs so I can get this
>> stable as
>> > >>>> quickly as possible so we can start to add new features.
>> > >>>>
>> > >>>> Cheers,
>> > >>>>
>> > >>>> Wayne
>> > >>>>
>> > >>>> [1]:
>> > >>>>
>> https://forum.kicad.info/t/kicad-nightly-v5-99-new-schematic-and-symbol-library-file-formats-are-now-the-default/22655
>> > >>>>
>> > >>>> ___
>> > >>>> 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
>>
>
>
> --
> Mark
>
___
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] New schematic and symbol library file formats

[Nick Østergaard]

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 just copy paste from the forum post more
> > or less and then you can edit it if you want.
> >
> > On Wed, 6 May 2020 at 22:56, Wayne Stambaugh  wrote:
> >>
> >> It's on my short list.  I planned on having it done already but I've
> >> been busy fixing bugs so it got pushed back 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:
> >>>>
> >>>> For those nightly build users, the merge request to make the new
> >>>> schematic and symbol library file formats the default file format was
> >>>> merged so builds should soon be available.  I wrote a detailed
> >>>> description on the KiCad user forum[1] if you are interested in the
> >>>> changes.  Please test it and report any bugs so I can get this stable as
> >>>> quickly as possible so we can start to add new features.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Wayne
> >>>>
> >>>> [1]:
> >>>> https://forum.kicad.info/t/kicad-nightly-v5-99-new-schematic-and-symbol-library-file-formats-are-now-the-default/22655
> >>>>
> >>>> ___
> >>>> 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] New schematic and symbol library file formats

[Nick Østergaard]

I can do it, I will probably just copy paste from the forum post more
or less and then you can edit it if you want.

On Wed, 6 May 2020 at 22:56, Wayne Stambaugh  wrote:
>
> It's on my short list.  I planned on having it done already but I've
> been busy fixing bugs so it got pushed back 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:
> >>
> >> For those nightly build users, the merge request to make the new
> >> schematic and symbol library file formats the default file format was
> >> merged so builds should soon be available.  I wrote a detailed
> >> description on the KiCad user forum[1] if you are interested in the
> >> changes.  Please test it and report any bugs so I can get this stable as
> >> quickly as possible so we can start to add new features.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> [1]:
> >> https://forum.kicad.info/t/kicad-nightly-v5-99-new-schematic-and-symbol-library-file-formats-are-now-the-default/22655
> >>
> >> ___
> >> 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] New schematic and symbol library file formats

[Nick Østergaard]

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 was
> merged so builds should soon be available.  I wrote a detailed
> description on the KiCad user forum[1] if you are interested in the
> changes.  Please test it and report any bugs so I can get this stable as
> quickly as possible so we can start to add new features.
>
> Cheers,
>
> Wayne
>
> [1]:
> https://forum.kicad.info/t/kicad-nightly-v5-99-new-schematic-and-symbol-library-file-formats-are-now-the-default/22655
>
> ___
> 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] Gitlab CI sucks

[Nick Østergaard]

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 new is hard. I fell quite a bit frustrated by the pipeline scripts.
>
> https://gitlab.com/kicad/services/kicad-doc/pipelines/139696624
>
> Someone with some more experience please propose a better merge
> request that will not unconditionally push to the registry, and
> trigger downstream 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 to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch freeze

[Nick Østergaard]

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
> > have a string freeze for the branch.
> >
> > I am sorta wondering why we can't enable the CI, for example. [1]
> >
> > Also as a heads up, there a couple of critical issues for the 5.1.6
> > milestone being added after 5.1.6-rc1 [2], most importantly [3] and
> > [4].
> >
> > [1]
> https://gitlab.com/kicad/code/kicad/-/merge_requests/198#note_337036264
> > [2] https://gitlab.com/groups/kicad/code/-/milestones/1
> > [3] https://gitlab.com/kicad/code/kicad/-/issues/4328
> > [4] https://gitlab.com/kicad/code/kicad/-/issues/4284
> >
>
> I cannot reproduce the crashes, both on W7 and Kubuntu 18.04LTS.
> issue 4328 can be depending on libraries or Window manager (or can be
> fixed since 5.1.5.0 version).
> issue 4284 can be related to some multi-threading seg-fault, very hard to
> reproduce.
>
>
> --
> Jean-Pierre CHARRAS
>
> ___
> 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 branch freeze

[Nick Østergaard]

Mmm, when you mean branch freeze, I assume you really mean that we
have a string freeze for the branch.

I am sorta wondering why we can't enable the CI, for example. [1]

Also as a heads up, there a couple of critical issues for the 5.1.6
milestone being added after 5.1.6-rc1 [2], most importantly [3] and
[4].

[1] https://gitlab.com/kicad/code/kicad/-/merge_requests/198#note_337036264
[2] https://gitlab.com/groups/kicad/code/-/milestones/1
[3] https://gitlab.com/kicad/code/kicad/-/issues/4328
[4] https://gitlab.com/kicad/code/kicad/-/issues/4284

On Sun, 3 May 2020 at 14:26, Wayne 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 wrote:
> >> Just the tag in git
> >>
> >> tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh  >> <mailto:stambau...@gmail.com>>:
> >>
> >> 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?
> >> >
> >> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh
> >> mailto:stambau...@gmail.com>
> >> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>:
> >> >
> >> > 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
> >> changes.  I
> >> > would like to release on Friday, May 15th if possible so
> >> please let me
> >> > know if there is any reason we cannot make that date.  Thank
> >> you to all
> >> > the development teams for your continued efforts.
> >> >
> >> > Cheers,
> >> >
> >> > Wayne
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> >> > Post to : kicad-developers@lists.launchpad.net
> >> <mailto:kicad-developers@lists.launchpad.net>
> >> > <mailto:kicad-developers@lists.launchpad.net
> >> <mailto: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] Submitting new wizards and plugins

[Nick Østergaard]

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 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 has been asked before or it’s in a FAQ somewhere 
> > that I haven’t located.
> >
> >
> >
> > I’ve written a number of scripts for KiCad over the past few months for 
> > things like component alignment and spacing, and am now working on 
> > converting those to plugins and additional footprint wizards. I feel like 
> > the community could benefit from some of these tools, but I don’t know the 
> > best way to submit them or if these sorts of things are welcomed by the 
> > community. For the new footprint wizards, for instance, should I just 
> > submit a pull-request to github of the kicad-footprint-wizards project?
> >
> >
> >
> > -Alan
> >
> > ___
> > 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] Submitting new wizards and plugins

[Nick Østergaard]

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 has been asked before or it’s in a FAQ somewhere 
> that I haven’t located.
>
>
>
> I’ve written a number of scripts for KiCad over the past few months for 
> things like component alignment and spacing, and am now working on converting 
> those to plugins and additional footprint wizards. I feel like the community 
> could benefit from some of these tools, but I don’t know the best way to 
> submit them or if these sorts of things are welcomed by the community. For 
> the new footprint wizards, for instance, should I just submit a pull-request 
> to github of the kicad-footprint-wizards project?
>
>
>
> -Alan
>
> ___
> 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] Separate download server directory for each Windows nightly build installer version?

[Nick Østergaard]

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/) open
> > in a browser tab to download the latest nightly build, often daily. It's
> > slightly annoying to have four files for each nightly build: 64 and 32 bit,
> > and lite and full.
>
> Possible, we'd just have to change the script that calls s3cmd to copy the
> files. If there is consensus that this is a good thing I can do that.
>
>Simon
>
> ___
> 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] Is it really the case that installing KiCad on a Mac requires manually copying files around?

[Nick Østergaard]

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 installer.

lør. 25. apr. 2020 15.17 skrev Michael Kavanagh :

> I really do not think that is necessary. Anyone who has owned a Mac
> for more than a few hours (the initial install/setup phase) will be
> well acquainted with the process.
>
> The KiCad macOS download page is already a bit "complicated" and
> "confusing" for us "special Mac people". Usually it's just an empty
> page with a big download button ;)
>
> https://www.mozilla.org/en-GB/firefox/mac/
>
>
> On Sat, 25 Apr 2020 at 07:50, Rene Pöschl  wrote:
> >
> > Hi again,
> >
> > might it be a good idea to add the content of the Readme to the download
> > page? That way it would bring the Mac download page to the standard of
> > the ubuntu one. (That page also explains the "normal" way to install
> > from a third party source.) Even better would be if screenshots are
> > included as the process is done in a graphical interface.
> >
> > My reasoning here would be that having this info clearly visible without
> > needing to download anything would help anyone that needs to help others
> > install software on any platform. So the forum users, teachers and
> > possibly even the IT guys in companies might benefit from such detailed
> > explanations.
> >
> > I would assume there might be differences depending on Mac version which
> > is why i first ask here instead of just copying the content of adams
> > mail into a pull request on the website repo.
> >
> > On 24/04/2020 17:31, Adam Wolf wrote:
> > > Hi folks,
> > >
> > > Thanks for bringing this to my attention, Rene.
> > >
> > > I have attached two images, one showing what "normal" macOS
> > > installation looks like, and what ours looks like.
> > >
> > > Our situation is not very far from normal and I would hesitate to call
> > > it "manual" copying.  I do not know what they're talking about, but it
> > > is not correct that you need to use a terminal or something to run
> > > commands to install KiCad on macOS.
> > >
> > > When we surveyed users ~5 years ago when I revamped the macOS
> > > packaging, users were overwhelmingly in favor of this method vs a pkg.
> > > Pkgs have a bad reputation for doing bad stuff to your system--like
> > > Zoom just did.
> > >
> > > There is also a README right when you open the DMG that explains step
> > > by step what to do:
> > >
> > > """
> > > To install KiCad, click and drag the two directory icons to the
> > > targets pointed at by the arrows.
> > >
> > > After dropping kicad onto Application Support, you may be asked to
> > > authenticate with an administrator username and password.  This
> > > installs the support files for KiCad for all users on the system.
> > >
> > > KiCad is now installed!  Inside of /Applications will be a directory
> > > called KiCad, and inside of that are all the programs in KiCad.  The
> > > project manager is the one labeled kicad, and is probably where you
> > > want to start.
> > >
> > > When you open the KiCad apps the first time, you must right-click on
> > > them and select Open.  You only need to do this once.  You must open
> > > KiCad first before opening the standalone apps, or else the standalone
> > > apps won't be able to open up due to macOS quarantining.
> > > """
> > >
> > > If someone wants to write a homebrew cask for using the mac DMG, I
> > > suspect it would only be an hour or so total, and then users could
> > > install with a single command in just a few minutes (however long it
> > > takes to download the DMG).  Previously, another developer made a
> > > homebrew recipe but it did not have a bottle, so it took hours to
> > > install on a user's computers.  This was before homebrew casks which
> > > should solve this problem.
> > >
> > > On Fri, Apr 24, 2020 at 9:35 AM Jon Evans  wrote:
> > >> I believe these users are talking about the normal MacOS method of
> installing software,
> > >> which does typically involve copying files.
> > >>
> > >> Normally MacOS software is packaged as a disk image that is mounted
> when you double click it.
> > >>
> > >> The mounted image then normally contains the software to be
> installed, and shortcuts
> > >> that are used as drop targets for a "drag and drop" copy.
> > >>
> > >> Most software only has one "file" (the .app file, which is actually a
> directory)
> > >> That file is copied to the Applications folder on the user's system.
> > >>
> > >> KiCad's installation also involves copying a second folder to a
> privileged location (Application Support),
> > >> so the user will be prompted for authentication when they do this
> step.
> > >>
> > >> This part of the approach is not very common for commercial MacOS
> software.
> > >> Software that must install to privileged locations 

Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

[Nick Østergaard]

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 documentation, possible as a big
section in the Getting Started in KiCad doc. Having it in the
documentation will also make it easier to translate.

Also, don't forget that as it is now works for all other people, than
a small handful of people. We can't help everyone always.

On Sat, 25 Apr 2020 at 09:31, Rene Pöschl  wrote:
>
> And again,
>
> Sorry forgot to add this. There seem to be some problems for some users
> on Catalina. I am not sure if what got suggested on the forum [1] is the
> correct way to install KiCad on Catalina. Would be great if somebody
> knowledgeable would double check the proposed solutions and possibly
> clarify the exact workflow. I think it would then be beneficial if that
> cleaned up info would also be found on the Mac download page.
>
> [1]: https://forum.kicad.info/t/solved-kicad-on-catalina/22189
>
> On 25/04/2020 08:50, Rene Pöschl wrote:
> > Hi again,
> >
> > might it be a good idea to add the content of the Readme to the download
> > page? That way it would bring the Mac download page to the standard of
> > the ubuntu one. (That page also explains the "normal" way to install
> > from a third party source.) Even better would be if screenshots are
> > included as the process is done in a graphical interface.
> >
> > My reasoning here would be that having this info clearly visible without
> > needing to download anything would help anyone that needs to help others
> > install software on any platform. So the forum users, teachers and
> > possibly even the IT guys in companies might benefit from such detailed
> > explanations.
> >
> > I would assume there might be differences depending on Mac version which
> > is why i first ask here instead of just copying the content of adams
> > mail into a pull request on the website repo.
> >
> > On 24/04/2020 17:31, Adam Wolf wrote:
> >> Hi folks,
> >>
> >> Thanks for bringing this to my attention, Rene.
> >>
> >> I have attached two images, one showing what "normal" macOS
> >> installation looks like, and what ours looks like.
> >>
> >> Our situation is not very far from normal and I would hesitate to call
> >> it "manual" copying.  I do not know what they're talking about, but it
> >> is not correct that you need to use a terminal or something to run
> >> commands to install KiCad on macOS.
> >>
> >> When we surveyed users ~5 years ago when I revamped the macOS
> >> packaging, users were overwhelmingly in favor of this method vs a pkg.
> >> Pkgs have a bad reputation for doing bad stuff to your system--like
> >> Zoom just did.
> >>
> >> There is also a README right when you open the DMG that explains step
> >> by step what to do:
> >>
> >> """
> >> To install KiCad, click and drag the two directory icons to the
> >> targets pointed at by the arrows.
> >>
> >> After dropping kicad onto Application Support, you may be asked to
> >> authenticate with an administrator username and password.  This
> >> installs the support files for KiCad for all users on the system.
> >>
> >> KiCad is now installed!  Inside of /Applications will be a directory
> >> called KiCad, and inside of that are all the programs in KiCad.  The
> >> project manager is the one labeled kicad, and is probably where you
> >> want to start.
> >>
> >> When you open the KiCad apps the first time, you must right-click on
> >> them and select Open.  You only need to do this once.  You must open
> >> KiCad first before opening the standalone apps, or else the standalone
> >> apps won't be able to open up due to macOS quarantining.
> >> """
> >>
> >> If someone wants to write a homebrew cask for using the mac DMG, I
> >> suspect it would only be an hour or so total, and then users could
> >> install with a single command in just a few minutes (however long it
> >> takes to download the DMG).  Previously, another developer made a
> >> homebrew recipe but it did not have a bottle, so it took hours to
> >> install on a user's computers.  This was before homebrew casks which
> >> should solve this problem.
> >>
> >> On Fri, Apr 24, 2020 at 9:35 AM Jon Evans  wrote:
> >>> I believe these users are talking about the normal MacOS method of 
> >>> installing software,
> >>> which does typically involve copying files.
> >>>
> >>> Normally MacOS software is packaged as a disk image that is mounted when 
> >>> you double click it.
> >>>
> >>> The mounted image then normally contains the software to be installed, 
> >>> and shortcuts
> >>> that are used as drop targets for a "drag and drop" copy.
> >>>
> >>> Most software only has one "file" (the .app file, which is actually a 
> >>> directory)
> >>> That file is copied to the Applications folder on the user's system.
> >>>
> >>> KiCad's installation 

[Kicad-developers] Gitlab CI sucks

[Nick Østergaard]

Hello

Everything new is hard. I fell quite a bit frustrated by the pipeline scripts.

https://gitlab.com/kicad/services/kicad-doc/pipelines/139696624

Someone with some more experience please propose a better merge
request that will not unconditionally push to the registry, and
trigger downstream 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 to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Separate download server directory for each Windows nightly build installer version?

[Nick Østergaard]

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 something daily then why not automate it?
> A simple shell or python script will do the job and use much less ram than a 
> browser tab :)
>
> On Fri, Apr 24, 2020 at 1:10 PM Eeli Kaikkonen  
> wrote:
>>
>> I keep the Windows nightly build download server page 
>> (https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/) open 
>> in a browser tab to download the latest nightly build, often daily. It's 
>> slightly annoying to have four files for each nightly build: 64 and 32 bit, 
>> and lite and full.
>>
>> Could it be possible to have four directories under the main directory:
>> * full_installer_with_libraries_64bit
>> * full_installer_with_libraries_32bit
>> * lite_installer_downloadable_libraries_64bit
>> * lite_installer_downloadable_libraries_32bit
>>
>> Then I could just refresh the tab and click on the last file. Now I have to 
>> check every time which one is what I want so that I don't download a wrong 
>> one by accident (which has happened).
>>
>> (The same is of course true for the 5.1 testing builds.)
>>
>> Eeli Kaikkonen
>> ___
>> 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] Is it really the case that installing KiCad on a Mac requires manually copying files around?

[Nick Østergaard]

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 "like" to drag things instead of clicking
next.

On Fri, 24 Apr 2020 at 17:35, Michael Kavanagh
 wrote:
>
> This is completely standard. Infact, the .pkg installers that Jon
> mentioned are in my experience very rare (only Microsoft Office and
> MatLab initially spring to mind).
>
> On Fri, 24 Apr 2020 at 15:22, Rene Pöschl  wrote:
> >
> > Hi all but especially adam,
> >
> >
> > lately there where a few threads on the forum where installation on Mac
> > came up. The users reported that they installed KiCad by manually
> > copying files around which sounded wrong to me. But as a lot of users
> > seem to be under the impression that this is indeed the right way i am
> > now starting to believe them.
> >
> > If these users are really correct then maybe this should be documented
> > very clearly on our download page. Or if there is any option to automate
> > this process (reducing human error) then maybe this would be the better
> > way to go long term but until then it should still be documented what
> > needs to be copied.
> >
> > One problem i see is if users can copy KiCad files then the libs might
> > not be write protected which would be a problem as KiCad relies on the
> > operating system write protection to avoid users modifying the shipped
> > libraries.
> >
> >
> > ___
> > 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] Help debug pcbnew

[Nick Østergaard]

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 Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372
>
> On 2020-04-23 09:50, Mário Luzeiro wrote:
> > Hello all,
> > I'm trying to run KiCad on debug mode (from latest development
> > branch).. it used to work.. but now it crashes when I try to run
> > pcbnew.
> > Has anyone seen this before? any idea how to solve it?
> >
> > ../src/common/object.cpp(251): assert "classTable->Get(m_className) ==
> > NULL" failed in Register(): Class "wxCommandEvent" already in RTTI
> > table - have you used IMPLEMENT_DYNAMIC_CLASS() multiple times or
> > linked some object file twice)?
> >
> > ...
> > 81 pcbnewInitPythonScripting
> >python_scripting.cpp 217
> > 0x7fffe96fcc2e
> > 82 scriptingSetup
> >pcbnew.cpp   279
> > 0x7fffe8f7b438
> > 83 PCB::IFACE::OnKifaceStart
> >pcbnew.cpp   364
> > 0x7fffe8f7baa5
> > 84 KIWAY::KiFACE
> >kiway.cpp250
> > 0x555fb594
> > 85 KIWAY::Player
> >kiway.cpp365
> > 0x555fbd3a
> > 86 PGM_SINGLE_TOP::OnPgmInit
> >single_top.cpp   366
> > 0x555ee909
> > 87 APP_SINGLE_TOP::OnInit
> >single_top.cpp   166
> > 0x555f2783
> > 88 wxAppConsoleBase::CallOnInit
> >app.h93
> > 0x555f0be7
> > 89 wxEntry(int&, wchar_t * *)
> >
> > 0x76683b3a
> > 90 main
> >single_top.cpp   283
> > 0x555ee3b5
> >
> > Regards,
> > Mario Luzeiro
> > ___
> > 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] Coverity for the 5.1 branch

[Nick Østergaard]

Yes, indeed. I am told that it is part of the bugs that they don't
care to fix, I guess this is since they were acquired by Synopsis and
priorities has shifted for them.

On Thu, 23 Apr 2020 at 16:25, Wayne Stambaugh  wrote:
>
> The swig files are turned off in the config and none of the swig code
> warnings show up in the defects list but for some reason they still show
> up in the status emails.  Maybe there is another config setting the we
> are missing.
>
> On 4/23/20 10:19 AM, Jon Evans wrote:
> > Thanks!
> >
> > Speaking of Coverity, should we 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!  Thank you Mark and Nick.
> >
> > On 4/23/20 4:03 AM, Nick Østergaard wrote:
> > > Hello
> > >
> > > Just a FYI, we (Mark and I) have created a new coverity project for
> > > the 5.1 branch, we call it kicad-stable [1], we still have the project
> > > just named kicad [2] for master.
> > >
> > > I added a few devs, but it is intended to be open for anyone
> > > interested in contributing. I think you can request 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
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > <mailto: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
> > <mailto: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

[Kicad-developers] Coverity for the 5.1 branch

[Nick Østergaard]

Hello

Just a FYI, we (Mark and I) have created a new coverity project for
the 5.1 branch, we call it kicad-stable [1], we still have the project
just named kicad [2] for master.

I added a few devs, but it is intended to be open for anyone
interested in contributing. I think you can request 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

___
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 branch freeze

[Nick Østergaard]

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?
> >
> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh  > <mailto:stambau...@gmail.com>>:
> >
> > 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 changes.
> I
> > would like to release on Friday, May 15th if possible so please let
> me
> > know if there is any reason we cannot make that date.  Thank you to
> all
> > the development teams for your continued efforts.
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto: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 branch freeze

[Nick Østergaard]

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 changes.  I
> would like to release on Friday, May 15th if possible so please let me
> know if there is any reason we cannot make that date.  Thank you to all
> the development teams for your continued efforts.
>
> 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] Dev docs not updating

[Nick Østergaard]

@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 container? GitLab 
>> has a built-in container registry for each repository that is very easy to 
>> push to from their CI (it basically 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.
>>>
>>> lør. 25. jan. 2020 21.13 skrev Ian McInerney :
>>>>
>>>> Forgive my ignorance here, since I don't know how the scripts to generate 
>>>> the docs are run currently, but is this a task we could move to a GitLab 
>>>> CI job? Based on what you said, it sounds like we build a docker image for 
>>>> the site to deploy it. I know that GitLab can build docker images and 
>>>> allow you to push them to repositories (I have made some containers for 
>>>> building a CI system for our code repo that way on 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 :
>>>>>>
>>>>>> It looks like the dev docs aren't updating again. The current page says 
>>>>>> it was generated on Dec 19, and definitely doesn't include the 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:
>>>>>>> >
>>>>>>> > 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
>>>>>>> > ___
>>>>>>> > 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] kicad2step runs for more than 12 hours and don't produce step file

[Nick Østergaard]

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 and
> I don't know if this process runs slowly or if it will never end.
>
> hilbert:[~/cvs/electronique/mateo_logique_5] > ps auwx | grep kicad2step
> bertrand  110880 99.9  4.1 1219712 642000 pts/5  Rl+  avril11 1371:54
> /usr/local/bin/kicad2step --user-origin=620.00 x 450.00
> --min-distance=0.0001 mm -f -o
> /home/bertrand/cvs/electronique/mateo_logique_5/mateo_logique.step
> /home/bertrand/cvs/electronique/mateo_logique_5/mateo_logique.kicad_pcb
>
> I run last 5.99 from git tree (1269-g174856bac) and my pcb file is a
> little big (56MB).
>
> If I run kicad2pcb from terminal, it returns a lot of warning :
> 09:40:04:   * no model defined for component 'Q11'
> 09:40:04:   * no model defined for component 'Q10'
> 09:40:04:   * no model defined for component 'Q9'
> 09:40:04:   * no model defined for component 'Q8'
> 09:40:04:   * no model defined for component 'Q7'
> 09:40:04:   * no model defined for component 'Q6'
> 09:40:04:   * no model defined for component 'Q5'
> 09:40:04:   * no model defined for component 'Q4'
> 09:40:04:   * no model defined for component 'Q3'
> 09:40:04:   * no model defined for component 'Q2'
> but 3dviewer does'nt.
>
> Best regards,
>
> JKB
>
> ___
> 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] availability

[Nick Østergaard]

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 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 again.  (I swear this whole fiasco ends with me
> joining the CMake macOS team...)  After the OCC switchover, I need to
> debug something weird with the 5.1.5 package, so we're ready for
> 5.1.6.  At that point, I have one thing to clear up from a project
> management (not technical) perspective re the notarization and that
> should be able to be setup on our nightlies and releases.
>
> Thanks for your patience as I continue to improve the macOS package :)
>  I appreciate bug reports and ideas and PRs but I'm currently only
> able to make time to process my KiCad backlog maybe once or twice a
> week.
>
> Adam Wolf
>
> ___
> 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] availability

[Nick Østergaard]

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 again.  (I swear this whole fiasco ends with me
> joining the CMake macOS team...)  After the OCC switchover, I need to
> debug something weird with the 5.1.5 package, so we're ready for
> 5.1.6.  At that point, I have one thing to clear up from a project
> management (not technical) perspective re the notarization and that
> should be able to be setup on our nightlies and releases.
>
> Thanks for your patience as I continue to improve the macOS package :)
>  I appreciate bug reports and ideas and PRs but I'm currently only
> able to make time to process my KiCad backlog maybe once or twice a
> week.
>
> Adam Wolf
>
> ___
> 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] Dev docs not updating

[Nick Østergaard]

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 container?
> GitLab has a built-in container registry for each repository that is very
> easy to push to from their CI (it basically 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.
>>
>> lør. 25. jan. 2020 21.13 skrev Ian McInerney :
>>
>>> Forgive my ignorance here, since I don't know how the scripts to
>>> generate the docs are run currently, but is this a task we could move to a
>>> GitLab CI job? Based on what you said, it sounds like we build a docker
>>> image for the site to deploy it. I know that GitLab can build docker images
>>> and allow you to push them to repositories (I have made some containers for
>>> building a CI system for our code repo that way on 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 >>> >:
>>>>
>>>>> It looks like the dev docs aren't updating again. The current page
>>>>> says it was generated on Dec 19, and definitely doesn't include the 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:
>>>>>> >
>>>>>> > 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
>>>>>> > ___
>>>>>> > 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] Dev docs not updating

[Nick Østergaard]

Yes, I already pushed a test script on some branche but we need to push it
to the docler registey.

lør. 25. jan. 2020 21.13 skrev Ian McInerney :

> Forgive my ignorance here, since I don't know how the scripts to generate
> the docs are run currently, but is this a task we could move to a GitLab CI
> job? Based on what you said, it sounds like we build a docker image for the
> site to deploy it. I know that GitLab can build docker images and allow you
> to push them to repositories (I have made some containers for building a CI
> system for our code repo that way on 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 :
>>
>>> It looks like the dev docs aren't updating again. The current page says
>>> it was generated on Dec 19, and definitely doesn't include the 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:
>>>> >
>>>> > 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
>>>> > ___
>>>> > 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] Dev docs not updating

[Nick Østergaard]

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 :

> It looks like the dev docs aren't updating again. The current page says it
> was generated on Dec 19, and definitely doesn't include the 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:
>> >
>> > 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
>> > ___
>> > 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] GitHub Mirror not updating?

[Nick Østergaard]

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 pushed for its first
> > update, since it looks like it got the first of the large files already
> > mirrored to it and it was choking on the second of the files.
> >
> > -Ian
> >
> > On Mon, Jan 20, 2020 at 10:25 PM Simon Richter  > > wrote:
> >
> > Hi Wayne,
> >
> > On 20.01.20 21:25, Wayne Stambaugh wrote:
> >
> > > If I run the commands Simon suggested to remove the blobs, what does
> > > this mean for devs who pull from the dev repo on gitlab?
> > After fetching normally, using
> >
> > $ git fetch
> >
> > anyone who doesn't have local work on top can just reset their
> > branch, using
> >
> > $ git reset --keep origin/master
> >
> > to pivot over. The --keep option makes sure that no local changes are
> > overwritten, and complains if it would do so.
> >
> > If they have local work, the sanest approach is to rebase on top of
> > origin/master and delete the offending commits at the same time by doing
> > an interactive rebase
> >
> > $ git rebase -i origin/master
> >
> > This gives a list of all commits that don't have identical content in
> > the old and new history. Since the filtered branch is the same except
> > for those four, the first four lines will be
> >
> > pick ea31730b4 Handle error returns from lstat.
> > pick e83420f19 Remove file accidentally commited in ea31730b4
> > pick e27e6ee16 Also catch null dereference in case wxASSERT was
> > skipped.
> > pick e1925b89c Remove file accidentally added in e27e6ee1
> >
> > and all local changes will follow those. You can either delete these
> > lines from the todo list, or replace the work "pick" by "drop".
> >
> > The approach using "git filter-branch" is not recommended for normal
> > developers, because it generates another alternate history that needs to
> > be resolved by calling "git rebase origin/master", and when you're
> > rebasing anyway, you can also remove the commits at that point.
> >
> > Wayne, if you want to avoid filter-branch, you can also use an
> > interactive rebase:
> >
> > $ git rebase -i 9df2cfb32
> >
> > In the list, move the correction commits under the commits they fix, and
> > replace "pick" by "fixup". The first six lines should read
> >
> > pick ea31730b4 Handle error returns from lstat.
> > fixup e83420f19 Remove file accidentally commited in ea31730b4
> > pick b3af41e1b RTree: Fix iterator in single branch trees
> > pick e27e6ee16 Also catch null dereference in case wxASSERT was
> > skipped.
> > fixup e1925b89c Remove file accidentally added in e27e6ee1
> > pick 7399465fd Handle nullptr.
> >
> > i.e. line 2 becomes "fixup", lines 5 and 6 are swapped, and line (now) 5
> > also becomes "fixup".
> >
> > Both this method and the filter-branch method alter the committer name
> > and date in the new history, so the commit IDs are not reproducible.
> >
> > Anyone but Wayne can of course run the same commands and get commits
> > with identical contents but different ID, which a normal rebase will
> > clean up nicely.
> >
> > The merge request workflow probably doesn't have to change (much), since
> > we rebase changes before merging them, for these the same interactive
> > rebase as above works.
> >
> >Simon
> >
> > ___
> > 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] Rebase the tree?

[Nick Østergaard]

It should be there, I am sure you are just confused by the gitlab webui.

It should be something along the lines of:
Settings -> Repository -> Protected branches, click expand. Set the
proper settings in the "Protect a branch" section.

On Mon, 20 Jan 2020 at 23:26, Wayne 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 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:
> >>>
> >>> 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 branch.
> >>>
> >>> Thanks,
> >>>
> >>> Wayne
> >>>
> >>> On 1/20/20 5:13 PM, Wayne Stambaugh wrote:
> >>>> Please do not push anything to the master branch or perform any merge
> >>>> requests until I push the rebase the master branch to prevent any commit
> >>>> losses because forcing a push will wipe out any changes.  I ran the git
> >>>> command suggested by Simon and it seems to have the desired results but
> >>>> I have no idea how this is going to play out so I'm making a backup
> >>>> clone of master just in case things go sideways.  I'll ping everyone
> >>>> once I have pushed the rebase.  Thank you for your cooperation and I
> >>>> apologize for whatever pain and agony this causes.  Hopefully we will
> >>>> never make this mistake again.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Wayne
> >>>>
> >>>> On 1/18/20 7:29 AM, Simon Richter wrote:
> >>>>> Hi,
> >>>>>
> >>>>> On 17.01.20 19:14, Simon Richter wrote:
> >>>>>
> >>>>>> 1. "git rebase -i origin/master"
> >>>>>> 2. in the editor, if they are present, remove the lines
> >>>>>>
> >>>>>> pick ea31730b4 Handle error returns from lstat.
> >>>>>> pick e83420f19 Remove file accidentally commited in ea31730b4
> >>>>>> pick e27e6ee16 Also catch null dereference in case wxASSERT was 
> >>>>>> skipped.
> >>>>>> pick e1925b89c Remove file accidentally added in e27e6ee1
> >>>>>>
> >>>>>> 3. save and exit
> >>>>>
> >>>>> Even less interactive:
> >>>>>
> >>>>> git filter-branch \
> >>>>> --prune-empty \
> >>>>> --index-filter \
> >>>>> 'git rm --cached --ignore-unmatch common/libcommon.a.*' \
> >>>>> 9df2cfb32..HEAD
> >>>>>
> >>>>> This rewrites the current branch to a state where the files were never
> >>>>> added, and removes the now-empty correction commits. The SHA1 sums in
> >>>>> the new branch are different, but as the commit contents are identical,
> >>>>> rebasing feature branches then goes smoothly even from the gitlab GUI.
> >>>>>
> >>>>> If you rebased a branch containing the offending commits on top of a
> >>>>> cleaned one, this generates four commits adding and removing the files
> >>>>> with no further changes, and the filter-branch commit above then reduces
> >>>>> these to no-ops and removes the commits.
> >>>>>
> >>>>> A simple test in gitlab *merge request is descended from e1925b89c"
> >>>>> could identify merge requests that would need to be rewritten.
> >>>>>
> >>>>>Simon
> >>>>>
> >>>>>
> >>>>> ___
> >>>>> 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] Rebase the tree?

[Nick Østergaard]

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:
> >
> > 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 branch.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 1/20/20 5:13 PM, Wayne Stambaugh wrote:
> > > Please do not push anything to the master branch or perform any merge
> > > requests until I push the rebase the master branch to prevent any commit
> > > losses because forcing a push will wipe out any changes.  I ran the git
> > > command suggested by Simon and it seems to have the desired results but
> > > I have no idea how this is going to play out so I'm making a backup
> > > clone of master just in case things go sideways.  I'll ping everyone
> > > once I have pushed the rebase.  Thank you for your cooperation and I
> > > apologize for whatever pain and agony this causes.  Hopefully we will
> > > never make this mistake again.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 1/18/20 7:29 AM, Simon Richter wrote:
> > >> Hi,
> > >>
> > >> On 17.01.20 19:14, Simon Richter wrote:
> > >>
> > >>> 1. "git rebase -i origin/master"
> > >>> 2. in the editor, if they are present, remove the lines
> > >>>
> > >>> pick ea31730b4 Handle error returns from lstat.
> > >>> pick e83420f19 Remove file accidentally commited in ea31730b4
> > >>> pick e27e6ee16 Also catch null dereference in case wxASSERT was 
> > >>> skipped.
> > >>> pick e1925b89c Remove file accidentally added in e27e6ee1
> > >>>
> > >>> 3. save and exit
> > >>
> > >> Even less interactive:
> > >>
> > >> git filter-branch \
> > >> --prune-empty \
> > >> --index-filter \
> > >> 'git rm --cached --ignore-unmatch common/libcommon.a.*' \
> > >> 9df2cfb32..HEAD
> > >>
> > >> This rewrites the current branch to a state where the files were never
> > >> added, and removes the now-empty correction commits. The SHA1 sums in
> > >> the new branch are different, but as the commit contents are identical,
> > >> rebasing feature branches then goes smoothly even from the gitlab GUI.
> > >>
> > >> If you rebased a branch containing the offending commits on top of a
> > >> cleaned one, this generates four commits adding and removing the files
> > >> with no further changes, and the filter-branch commit above then reduces
> > >> these to no-ops and removes the commits.
> > >>
> > >> A simple test in gitlab *merge request is descended from e1925b89c"
> > >> could identify merge requests that would need to be rewritten.
> > >>
> > >>Simon
> > >>
> > >>
> > >> ___
> > >> 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] Rebase the tree?

[Nick Østergaard]

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 branch.
>
> Thanks,
>
> Wayne
>
> On 1/20/20 5:13 PM, Wayne Stambaugh wrote:
> > Please do not push anything to the master branch or perform any merge
> > requests until I push the rebase the master branch to prevent any commit
> > losses because forcing a push will wipe out any changes.  I ran the git
> > command suggested by Simon and it seems to have the desired results but
> > I have no idea how this is going to play out so I'm making a backup
> > clone of master just in case things go sideways.  I'll ping everyone
> > once I have pushed the rebase.  Thank you for your cooperation and I
> > apologize for whatever pain and agony this causes.  Hopefully we will
> > never make this mistake again.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 1/18/20 7:29 AM, Simon Richter wrote:
> >> Hi,
> >>
> >> On 17.01.20 19:14, Simon Richter wrote:
> >>
> >>> 1. "git rebase -i origin/master"
> >>> 2. in the editor, if they are present, remove the lines
> >>>
> >>> pick ea31730b4 Handle error returns from lstat.
> >>> pick e83420f19 Remove file accidentally commited in ea31730b4
> >>> pick e27e6ee16 Also catch null dereference in case wxASSERT was 
> >>> skipped.
> >>> pick e1925b89c Remove file accidentally added in e27e6ee1
> >>>
> >>> 3. save and exit
> >>
> >> Even less interactive:
> >>
> >> git filter-branch \
> >> --prune-empty \
> >> --index-filter \
> >> 'git rm --cached --ignore-unmatch common/libcommon.a.*' \
> >> 9df2cfb32..HEAD
> >>
> >> This rewrites the current branch to a state where the files were never
> >> added, and removes the now-empty correction commits. The SHA1 sums in
> >> the new branch are different, but as the commit contents are identical,
> >> rebasing feature branches then goes smoothly even from the gitlab GUI.
> >>
> >> If you rebased a branch containing the offending commits on top of a
> >> cleaned one, this generates four commits adding and removing the files
> >> with no further changes, and the filter-branch commit above then reduces
> >> these to no-ops and removes the commits.
> >>
> >> A simple test in gitlab *merge request is descended from e1925b89c"
> >> could identify merge requests that would need to be rewritten.
> >>
> >>Simon
> >>
> >>
> >> ___
> >> 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] GitHub Mirror not updating?

[Nick Østergaard]

Yes, that is the error we get for the mirror script.

On Mon, 20 Jan 2020 at 18:08, Wayne Stambaugh  wrote:
>
> Is that what is causing the mirror issue?  If so, we should probably
> rebase to get rid of the blobs.  I was really hoping we wouldn't have to
> do that.
>
> On 1/20/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. 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 is 179.95 MB; this
> >> exceeds GitHub's file size limit of 100.00 MB
> >>
> >> On Mon, 20 Jan 2020 at 15:36, Felix Vollmer  wrote:
> >>>
> >>> Hi,
> >>>
> >>> are you aware that https://github.com/KiCad/kicad-source-mirror isn't
> >>> updating? Last commit is from 6 days ago.
> >>>
> >>> Cheers,
> >>> Felix Vollmer
> >>>
> >>> ___
> >>> 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] GitHub Mirror not updating?

[Nick Østergaard]

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.
> remote: error: Trace: 4ca7122c5342fce7e9459b19325e1a4d
> remote: error: See http://git.io/iEPt8g for more information.
> remote: error: File common/libcommon.a.ocP1Z7 is 179.95 MB; this
> exceeds GitHub's file size limit of 100.00 MB
>
> On Mon, 20 Jan 2020 at 15:36, Felix Vollmer  wrote:
> >
> > Hi,
> >
> > are you aware that https://github.com/KiCad/kicad-source-mirror isn't
> > updating? Last commit is from 6 days ago.
> >
> > Cheers,
> > Felix Vollmer
> >
> > ___
> > 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] GitHub Mirror not updating?

[Nick Østergaard]

 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 is 179.95 MB; this
exceeds GitHub's file size limit of 100.00 MB

On Mon, 20 Jan 2020 at 15:36, Felix Vollmer  wrote:
>
> Hi,
>
> are you aware that https://github.com/KiCad/kicad-source-mirror isn't
> updating? Last commit is from 6 days ago.
>
> Cheers,
> Felix Vollmer
>
> ___
> 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] How to show pad in pcbnew by clicking pin in eeschema

[Nick Østergaard]

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 over in pcbnew I get all pads highlighted rather than the single pad 
> corresponding to
> the pin.
>
> This behaviour ain't like it used to be.  So is this broken or is there some 
> other user
> action required to get the pad highlighted via cross-probing.
>
> Thanks,
>
> Dick
>
> ___
> 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] Linux distribution support policy

[Nick Østergaard]

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: https://github.com/KiCad/kicad-website/pull/470. I would like 
> feedback on this policy (either here or on GitHub).
>
> Basically, Fedora and Debian versions will be supported as long as they are 
> supported by upstream.
>
> LTS Ubuntu versions will be supported for 1 year after the next LTS version 
> is released (giving a 1-year overlap). Non-LTS versions will be supported for 
> as long as they are supported by upstream.
>
> I think 3 years of support for an LTS release is a good amount (if we went 
> with how long upstream supported it, then we would have a 6-year support 
> window). This is important not only for Boost, but also for wxWidgets. Once 
> 3.2 is released, I would imagine that only the new releases will contain it. 
> That means that if we support the LTS versions for the 6-year time frame, we 
> would have to also support the outdated wxWidgets versions (and deal with 
> their quirks/bugs) for that amount of time (and 3.2 won't be released by 
> 20.04, that I can say for sure, so that would mean supporting 3.0 until 2026 
> - when even wxWidgets upstream won't support it probably).
>
> -Ian
> ___
> 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

[Kicad-developers] file_formats.pdf doc is gone

[Nick Østergaard]

Hello

I see this is the link checker log of the website:

- ./public/help/file-formats/index.html
320  *  External link
http://bazaar.launchpad.net/~stambaughw/kicad/doc-read-only/download/head:/1115%4016bec504-3128-0410-b3e8-8e38c2123bca:trunk%252Fkicad-doc%252Fdoc%252Fhelp%252Ffile_formats%252Ffile_formats.pdf/file_formats.pdf
failed: 404 No error

Where is this supposed to be found now?

Nick

___
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] Rebase the tree?

[Nick Østergaard]

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 at least 4 that this would happen to).

That is currently only two commits on 5.1

> 2) The GitLab merge requests would be completely confused and each 
> contributor would have to manually fixup their branches and force push to 
> them to clean it up.
>
> For CI systems and the like, they can just do a shallow clone of the repo and 
> avoid those commits (at this point we are already 14 commits ahead of the 
> most recent (a clone of the last 5 commits is only 24.48MiB instead of the 
> 204.37MiB for a full clone).

This is not an issue, merge requests still need to be rebased when
changes pop in to master.

>
> -Ian
>
> On Fri, Jan 17, 2020 at 3:49 PM Jon Evans  wrote:
>>
>> Personally, I think "history is inviolate" doesn't need to apply to things 
>> that were checked in accidentally, and thus will never need to be merged 
>> against, diffed, etc.
>>
>> On Fri, Jan 17, 2020 at 10:48 AM Simon Richter  
>> wrote:
>>>
>>> Hi Seth,
>>>
>>> On Fri, Jan 17, 2020 at 06:53:46AM -0800, Seth Hillbrand wrote:
>>>
>>> > >there are two massive blobs that were accidentally checked in, and
>>> > >checking
>>> > >out the repo requires these to be transferred. Should we make an
>>> > >exception
>>> > >and rebase the tree to remove them from the history?
>>>
>>> > I would say no.  History is inviolate.
>>>
>>> True, but it's a significant chunk of useless history:
>>>
>>> -r--r--r-- 1 geier geier   5685856 Jan 17 16:40 
>>> pack-1478d96c882a625a8a6a25cac9ec2b8e514a2e61.idx
>>> -r--r--r-- 1 geier geier 157961655 Jan 17 16:40 
>>> pack-1478d96c882a625a8a6a25cac9ec2b8e514a2e61.pack
>>> -r--r--r-- 1 geier geier  1100 Jan 17 16:38 
>>> pack-81e52eb60810956fd5294dc2fb1ee61ce1aa7438.idx
>>> -r--r--r-- 1 geier geier  20734471 Jan 17 16:38 
>>> pack-81e52eb60810956fd5294dc2fb1ee61ce1aa7438.pack
>>> -r--r--r-- 1 geier geier  1100 Jan 17 16:37 
>>> pack-e18ed50ebfea3897568189f3806d0a2e7051dd37.idx
>>> -r--r--r-- 1 geier geier  44601959 Jan 17 16:37 
>>> pack-e18ed50ebfea3897568189f3806d0a2e7051dd37.pack
>>>
>>> The largest pack at 160 MB is our development history excluding these two
>>> files, the other two are the two files packed individually. They compress
>>> fairly well, but this is still 37.5% of our repository size.
>>>
>>>Simon
>>>
>>> ___
>>> 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] Rebase the tree?

[Nick Østergaard]

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, and
> >> checking
> >> out the repo requires these to be transferred. Should we make an
> >> exception
> >> and rebase the tree to remove them from the history?
> >>
> >>Simon
> >>
> >
> > I would say no.  History is inviolate.
>
> I would second that.  I don't see the need to rebase in this case.
>
> >
> > -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] What is the right build target to produce an installation zip.

[Nick Østergaard]

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 2020 at 20:31, Simon Richter  wrote:
>
> Hi,
>
> On Thu, Jan 09, 2020 at 12:12:43PM -0500, Brian Piccioni wrote:
>
> > How do I make a file I can unzip to/install to my Windows programs
> > directory?
>
> Packaging is external to the build tools, there is a separate
> KiCad-Winbuilder[1] project that does that.
>
>Simon
>
> [1] https://gitlab.com/kicad/packaging/kicad-win-builder
>
> ___
> 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] GitLab migration

[Nick Østergaard]

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 2019-11-26 12:41, Jeff Young wrote:
>
> OK, I’ve enabled 2FA.  Do I need to do something to get added back to
> the project?  (When I go to members, all I see are the bot, Seth and
> Wayne.)
>
> Cheers,
> Jeff.
>
> Hi Jeff-
>
> Wayne and the bot have permissions for the entire project.  I'm there
> while sorting out the transition work.  Coding permissions are specific
> to https://gitlab.com/kicad/code/ .  Library permissions are specific to
> https://gitlab.com/kicad/libraries/ , etc.
>
> If you'd like push permissions in libraries, you'll want to check with
> Rene.  I think Nick or Marek will be managing the website section
> (someone fill me in).  I'll also need to know who to assign to managing
> the documentation section (Nick also?).  Once I get the packaging
> section set up, we'll have folks in charge of their relative builds that
> we can run through the GitLab CI runner interface.
>
> -Seth
>
>
> Hi,
>
> well it seems i do not have access to the group either.
>
>
> Hi Rene-
>
> I've added you to the top-level group.  There is a sub-group called
> librarians where everyone goes but group permissions can only be assigned
> to repositories and not other groups (missed that part).
>
> Let me know if anything else looks amiss.
>
> I'm going to re-sync the repositories this weekend to see if we pick up
> any additional folks who are creating GitLab accounts.
>
> -Seth
>
>
> --
> KiCad Services Corporation [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> https://twitter.com/KiProEDA 
> https://www.linkedin.com/company/kicad
> 
> ___
> 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] Why is -Wno-deprecated-declarations defined

[Nick Østergaard]

Ok, sounds good to me.

lør. 28. dec. 2019 17.09 skrev Ian McInerney :

> I have run a build on both OSX and Linux (with wxWidgets 3.0) and don't
> see any more problems with the deprecation warnings (I fixed up the OSX
> ones by turning off the OpenGL deprecation warnings, since Apple has
> deprecated OpenGL, sigh...). I am going to go ahead and re-enable these
> warnings in master.
>
> The main reason I am digging into this is to mark the DLIST class as
> deprecated using the wxDEPRECATED_MSG macro (in response to
> https://gitlab.com/kicad/code/kicad/issues/2623#note_258333603).
>
> -Ian
>
> On Sat, Dec 28, 2019 at 2:30 PM Ian McInerney 
> wrote:
>
>> The commit that did it is this one from 2014:
>> https://gitlab.com/kicad/code/kicad/commit/a3211b2b9e57a36c79f4ba2b00d0ac1aa30dceb3,
>> but the log is literally just: "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:
>>
>>> 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 added because of that? Now, I don't think we
>>> should use that globally.
>>>
>>> On Sat, 28 Dec 2019 at 15:09, Ian McInerney 
>>> wrote:
>>> >
>>> > Is there a reason we disable warnings on deprecated declarations in
>>> debug mode? Other than a lot of warnings about OpenGL being deprecated on
>>> MacOS (gee, thanks Apple) that we can turn off pretty easily, I see no
>>> reason we should be forcing this in our CMakeLists. I tried tracing this
>>> back through the git history, but it is difficult to see why it was added.
>>> >
>>> > -Ian
>>> > ___
>>> > 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] Why is -Wno-deprecated-declarations defined

[Nick Østergaard]

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 added because of that? Now, I don't think we
should use that globally.

On Sat, 28 Dec 2019 at 15:09, Ian McInerney  wrote:
>
> Is there a reason we disable warnings on deprecated declarations in debug 
> mode? Other than a lot of warnings about OpenGL being deprecated on MacOS 
> (gee, thanks Apple) that we can turn off pretty easily, I see no reason we 
> should be forcing this in our CMakeLists. I tried tracing this back through 
> the git history, but it is difficult to see why it was added.
>
> -Ian
> ___
> 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] KiCad Website DNS Down

[Nick Østergaard]

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 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 planned outage at CERN for the webhosting DNS? I am trying to 
> > get to the kicad-pcb.org site and it is throwing a DNS error (unable to 
> > locate the IP for the site), and nslookup also can't find it.
> >
> > -Ian
> >
> >
> > ___
> > 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] KiCad Website DNS Down

[Nick Østergaard]

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 planned outage at CERN for the webhosting DNS? I am trying to get 
> to the kicad-pcb.org site and it is throwing a DNS error (unable to locate 
> the IP for the site), and nslookup also can't find it.
>
> -Ian
>
>
> ___
> 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] Dev docs not updating

[Nick Østergaard]

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
> ___
> 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] Version String using KICAD_VERSION

[Nick Østergaard]

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 supposed to be able to be overridden on the CMake 
> > command line (e.g. specifying -DKICAD_VERSION="blah")? It appears that the 
> > version string defined by CMake is always taking priority (then the git 
> > string is used afterwards if it exists), so this flag is being overwritten.
> >
> > I assume that this is something we are fine with, (if so I can cleanup the 
> > documentation and some of the CMake code around it). If not, then I guess 
> > we need to fix it.
> >
> > Is there anyone actively trying to use the -DKICAD_VERSION flag? Should we 
> > still support that (or only support the KICAD_VERSION_EXTRA flag?
>
> Fedora Linux only uses the  KICAD_VERSION_EXTRA flag.
>
> Steve
>
> ___
> 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] Replace "affects me" of launchpad in gitlab?

[Nick Østergaard]

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 
> currently thinking of using the thumbs-up to say that people support the 
> issue/that it affects them.
>
> -Ian
>
> On Thu, Dec 5, 2019 at 10:22 AM Eeli Kaikkonen  
> wrote:
>>
>> Which feature of gitlab issues replaces voting "affects me" in launchpad? 
>> Thumb up?
>>
>> I dislike the "thumb up" cliche because it's overused everywhere and has 
>> become almost meaningless or can be interpreted in many ways. Also it 
>> wouldn't match with thumb down here - would that mean "doesn't affect me"?
>>
>> BTW, how are "weight" and "popularity" calculated, what do they mean?
>>
>> Eeli Kaikkonen
>> ___
>> 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] New border/title blocks?

[Nick Østergaard]

I don't really use the page templates myself much. But I think it may
be time to rethink the page template concept to help it be easier for
the user to also select the correct paper size matching the template.
But I think that is better kept in an issue, but I guess keeping the
thoughts here are fine as we are in lp vs gitlab limbo right now.

But maybe a start could be to make the "Select Page Layout Description
File" open the templates folder in the installation directory if it
exists? Although this can conflict with the behaviour of the dialog
opening where last browsed. This is just an idea, not a "this is how I
think it should be in the end".

On Mon, 2 Dec 2019 at 05:18, Evan Shultz  wrote:
>
> My original request was misinterpreted or otherwise derailed and I'd like to 
> refocus things back to my original question.
>
> It was: "Is there a path to get these worksheets added into KiCad so they 
> appear along with the other options in the 'Size' pulldown menu in the Page 
> Settings dialog in Eeschema?"
>
> Having the new worksheets somewhere in the install directory is nice but it's 
> not very discoverable. Giving nice templates that match industry standard 
> convention the same visibility as the existing worksheets would be the most 
> salient way for KiCad users to take advantage of these new worksheets. In my 
> opinion, anyway.
>
> So, is it possible to make that happen? If so, what is 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 Nick Østergaard  wrote:
>>
>> Summa sumarum, from a packaging point of view it is included as it is
>> on other platforms.
>>
>> On Sun, 1 Dec 2019 at 23:42, Wayne Stambaugh  wrote:
>> >
>> > I downloaded and installed 5.1.5 on my windows box and it looked like
>> > these worksheets were in the template folder.  I didn't check the 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 > > > <mailto:ian.s.mciner...@ieee.org>> 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 see there:
>> > >
>> > > /usr/share/kicad/demos/interf_u/pagelayout_logo.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
>> > > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
>> > > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>> > > 
>> > > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
>> > > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>> > > /usr/share/kicad/template/gost_landscape.kicad_wks
>> > > /usr/share/kicad/template/gost_portrait.kicad_wks
>>

Re: [Kicad-developers] kicad-i18n on gitlab

[Nick Østergaard]

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 projects for kicad-i18n on gitlab:
> >>
> >> g...@gitlab.com:kicad/code/kicad-i18n.git
> >>
> >> g...@gitlab.com:kicad/kicad-translations/kicad-i18n.git
> >>
> >> They have two different project IDs, so they appear to be different
> >> repositories.  Which one should we pull from when building KiCad?
> >>
> >> Steve
>
> Sorry, I was still sorting the translations.  I previously imported it
> under code but deleted (I thought) and re-imported using KiCad Bot under
> "Translations".  The thinking here was that it was not code and there is
> a different group of committers generally responsible for it.
>
> I'm happy to take other suggestions.
>
> I'm removing the one under code (again) as it has me tagged for missing
> individuals rather than KiCad Bot.
>
> Best-
> 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

___
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] Space used on server

[Nick Østergaard]

Hi Tedd^2

Yeah, I probably didn't specify a proper ttl for some objects in some
directories, but you should definitely architect your mirroring
solution to handle that upstream has more data than you would like to
mirror, if it is an issue for you to keep up with the amount of data
upstream.

On Fri, 29 Nov 2019 at 11:26, tedd.t...@gmail.com  wrote:
>
> Hi Nick,
>
> I'm not asking for anything. Just, I'm using a hacky way to mirror the
> downloads to Sourceforge, involving storing a complete copy locally.
> I'm definitely going to architect a solution that 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 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 used in
> > > check.
> > >
> > > Since the move, there hasn't been any deletions of testing builds, and
> > > as of now, is coming up to 900GB, increasing about 100GB a month.
> > >
> > > Thanks,
> > > Tedd
> > >
> > > ___
> > > 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] [PATCH] Fixes for Visual Studio / vcpkg build

[Nick Østergaard]

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:
>>
>> 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 :)
>> >
>> > > https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
>> >
>> > They were broken at the same time as the Linux builds :)
>> >
>> >Simon
>> >
>> > ___
>> > 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] New border/title blocks?

[Nick Østergaard]

Summa sumarum, from a packaging point of view it is included as it is
on other platforms.

On Sun, 1 Dec 2019 at 23:42, Wayne Stambaugh  wrote:
>
> I downloaded and installed 5.1.5 on my windows box and it looked like
> these worksheets were in the template folder.  I didn't check the 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  > <mailto:ian.s.mciner...@ieee.org>> 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 see there:
> >
> > /usr/share/kicad/demos/interf_u/pagelayout_logo.kicad_wks
> > 
> > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> > /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> > /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
> > 
> > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> > /usr/share/kicad/template/gost_landscape.kicad_wks
> > /usr/share/kicad/template/gost_portrait.kicad_wks
> > /usr/share/kicad/template/pagelayout_default.kicad_wks
> > /usr/share/kicad/template/pagelayout_logo.kicad_wks
> >
> > -Ian
> >
> > On Thu, Nov 28, 2019 at 12:08 AM Evan Shultz  > <mailto:evan.shu...@gmail.com>> wrote:
> >
> > In 5.1.5_2, on Windows, I don't see these new page layouts. So
> > at least in Windows this wasn't packaged. I don't know about
> > other OSes.
> >
> > Perhaps there's a way to make this more obvious so that when new
> > page layouts are available all packagers are aware? The
> > discussion above reads to me like the KiCad project has no
> > control over this and my expectation would be that page layouts,
> > templates, and other "extras" that are in the official repos
> > would be included and consistent in all KiCad installs across
> > all OSes.
> >
> > Nick, is packaging Windows your domain? Is there any way I could
> > help to get them included in an updated 5.1.5 release or 5.1.6?
> > I know the GitLab stuff is taking a lot of time from everybody
> > but I don't want to let this wither away.
> >
> > On Thu, Nov 14, 2019 at 8:52 AM Evan Shultz
> > mailto:evan.shu...@gmail.com>> wrote:
> >
> > Thanks Seth! It would be great to have more templates
> > available for KiCad users. You can ping me for the review
> > when you post the PR.
> >
> > On Wed, Nov 13, 2019 at 9:44 PM Seth Hillbrand
> > mailto:s...@kipro-pcb.com>> wrote:
> >
> > On 2019-11-13 15:54, Evan Shultz wrote:
> >
> >> The contributor submitted ISO templates and the
> >> librarians have access to those standards, thus the
> >> review and merge could proceed.
> >
> > Fair enough
> >
> >> None of the librarians have access to the ASME
> >> s

Re: [Kicad-developers] New border/title blocks?

[Nick Østergaard]

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 see there:
>
> /usr/share/kicad/demos/interf_u/pagelayout_logo.kicad_wks
>
> /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>
> /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>
> /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>
> /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A3_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>
> /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
>
> /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>
> /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
>
> /usr/share/kicad/template/A4-portrait_ISO5457-1999_ISO7200-2004_EN.kicad_wks
>
> /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004-compact_EN.kicad_wks
>
> /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> /usr/share/kicad/template/gost_landscape.kicad_wks
> /usr/share/kicad/template/gost_portrait.kicad_wks
> /usr/share/kicad/template/pagelayout_default.kicad_wks
> /usr/share/kicad/template/pagelayout_logo.kicad_wks
>
> -Ian
>
> On Thu, Nov 28, 2019 at 12:08 AM Evan Shultz 
> wrote:
>
>> In 5.1.5_2, on Windows, I don't see these new page layouts. So at least
>> in Windows this wasn't packaged. I don't know about other OSes.
>>
>> Perhaps there's a way to make this more obvious so that when new page
>> layouts are available all packagers are aware? The discussion above reads
>> to me like the KiCad project has no control over this and my expectation
>> would be that page layouts, templates, and other "extras" that are in the
>> official repos would be included and consistent in all KiCad installs
>> across all OSes.
>>
>> Nick, is packaging Windows your domain? Is there any way I could help to
>> get them included in an updated 5.1.5 release or 5.1.6? I know the GitLab
>> stuff is taking a lot of time from everybody but I don't want to let this
>> wither away.
>>
>> On Thu, Nov 14, 2019 at 8:52 AM Evan Shultz 
>> wrote:
>>
>>> Thanks Seth! It would be great to have more templates available for
>>> KiCad users. You can ping me for the review when you post the PR.
>>>
>>> On Wed, Nov 13, 2019 at 9:44 PM Seth Hillbrand 
>>> wrote:
>>>
 On 2019-11-13 15:54, Evan Shultz wrote:

 The contributor submitted ISO templates and the librarians have access
 to those standards, thus the review and merge could proceed.


 Fair enough


 None of the librarians have access to the ASME standards and thus we
 could not properly review and vet them even if they were contributed.
 Should ASME templates be contributed that can be reviewed, they would be
 welcomed.


 OK, I can handle the ASME template submission.  If you run into
 standards in the future that the librarians don't have access to, feel free
 to ping the dev list.  We have a fair cross section of engineers who can
 help with reviews although we don't always follow the PRs at GitHub.


 -Seth


 KiCad Services Corporation [image: KiCad Services Corporation Logo]
 Seth Hillbrand
 *Lead Developer*
 +1-530-302-5483‬ <+12126039372>
 Davis, CA
 www.kipro-pcb.comi...@kipro-pcb.com
 https://twitter.com/KiProEDA 
 https://www.linkedin.com/company/kicad
 

>>> ___
>> 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 : 

Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

[Nick Østergaard]

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 
> > :)
>
> > https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
>
> They were broken at the same time as the Linux builds :)
>
>Simon
>
> ___
> 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] [PATCH] Fixes for Visual Studio / vcpkg build

[Nick Østergaard]

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 build going rather than a minimal one.
>
> In the meantime, I'm attaching my CMakeSettings.json from VS2019 in case it's 
> helpful.
> It has a hard-coded toolchain path that you'll have to check/update.
>
> I installed all the dependencies that were available in vcpkg, and then 
> disabled whatever was left (ngspice, OCE, and python stuff)
> Then I set up that CMakeSettings and basically things work :)
>
> By the way, I pushed my patches from my earlier email, let me know if anyone 
> has an issue with the change to the CMake script.
>
> Best,
> Jon
>
> On Sun, Nov 24, 2019 at 6:56 PM Brian Piccioni  
> wrote:
>>
>> Jon
>>
>>
>>
>> Despite MSVC Community being from MS, I see some advantages in using it, 
>> namely that it is basically a one-package solution: no msys2, no loads of 
>> other tools that have to be updated, etc..
>>
>>
>>
>> My lack of cmake-foo meant I hit a roadblock when trying to build an MSVC 
>> recipe. One time I got so far as to have it crap out on SSL or something 
>> like that but now I’m stuck much earlier.
>>
>>
>>
>> In any event I’m more than happy to experiment with whatever you’ve got, 
>> especially if you can provide some guidance.
>>
>>
>>
>> Brian
>>
>>
>>
>> From: Jon Evans
>> Sent: November 24, 2019 12:41 PM
>> To: KiCad Developers
>> Subject: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build
>>
>>
>>
>> Hi all,
>>
>>
>>
>> I got a build working using Visual Studio 2019 and vcpkg.
>>
>> Attached are three patches I needed to make so far.
>>
>> I'd appreciate some double-checking on these since cmake and wxwidgets can 
>> be a bit perilous.
>>
>>
>>
>> Thanks,
>>
>> -Jon
>>
>>
>
> ___
> 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] Linux Packagers: Resource File Updates

[Nick Østergaard]

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 version information is
> generated, only adding a tag to the appdata file to contain the full
> version (this will be the same as the version that gets displayed in the
> help window, so it contains the distro-specific extra version as well).
>
> The main effect that this will have is that the kicad.appdata.xml file
> will no longer be directly available in the source package, and will only
> be available after CMake has been run. I wanted to make sure that this
> wouldn't break any packaging scripts (which I think it wouldn't).
>
> Carsten, thanks for pointing those changes out. I will update the file
> with them as well. Redoing the screenshots is also on my todo list (since
> they still show a v4 release currently). Do you know what the guidelines
> are for sizing of them? I see that the current ones are 1024x576, and I
> can't seem to find any information on the suggested size (other than that
> Fedora recommends they are 16:9).
>
> Thanks,
> -Ian
>
> On Fri, Nov 29, 2019 at 5:39 AM Carsten Schoenert 
> wrote:
>
>> Hello Ian,
>>
>> On 28.11.19 17:53, Ian McInerney wrote:
>> > I would like to change the way we generate the kicad.appdata.xml file to
>> > have it be generated by CMake and include the version string inside of
>> > it (that way the version will appear in the app stores and other places
>> > that reference this). I don't think this will cause any issues, but I
>> > just want to see if anyone sees any problems with this.
>>
>> this can't be a problem as the AppStream specification is holding a key
>> for versioning information. Please see section 4.1.2,  ...
>> 
>>
>> >
>> https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps
>>
>> If you touch this all I'd suggest to update all URLs within the appdata
>> file as now the kicad-pcb.org domain is served by https.
>>
>> > $ git diff
>> > diff --git a/resources/linux/appdata/kicad.appdata.xml
>> b/resources/linux/appdata/kicad.appdata.xml
>> > index 2fc29f0c1..550cb10c5 100644
>> > --- a/resources/linux/appdata/kicad.appdata.xml
>> > +++ b/resources/linux/appdata/kicad.appdata.xml
>> > @@ -46,27 +46,27 @@
>> >
>> >
>> >  
>> > -  
>> http://kicad-pcb.org/img/screenshots/appstream/kicad.png
>> > +  
>> https://kicad-pcb.org/img/screenshots/appstream/kicad.png
>> >  
>> >
>> >  
>> >Eeschema Schematic Editor
>> > -  
>> http://kicad-pcb.org/img/screenshots/appstream/eeschema.png
>> > +  
>> https://kicad-pcb.org/img/screenshots/appstream/eeschema.png
>> >  
>> >
>> >  
>> >PcbNew PCB Layout
>> > -  
>> http://kicad-pcb.org/img/screenshots/appstream/pcbnew.png
>> > +  
>> https://kicad-pcb.org/img/screenshots/appstream/pcbnew.png
>> >  
>> >
>> >  
>> >PcbNew 3D Viewer
>> > -  
>> http://kicad-pcb.org/img/screenshots/appstream/3dviewer.png
>> > +  
>> https://kicad-pcb.org/img/screenshots/appstream/3dviewer.png
>> >  
>> >
>> >
>> > -  http://kicad-pcb.org/
>> > -  http://kicad-pcb.org/help/report-a-bug/
>> > +  https://kicad-pcb.org/
>> > +  https://kicad-pcb.org/help/report-a-bug/
>> 
>> >kicad-developers@lists.launchpad.net
>> 
>> >The KiCad Developers
>> >  
>>
>> This reminds me that all the screenshots should be updated too. ;)
>>
>> The validator for the AppData content within the Debian QA is mentioning
>> that the component ID is not a reverse domain-name. Should get fixed too
>> in case the file is getting changed.
>>
>> > https://appstream.debian.org/sid/main/issues/kicad.html
>>
>> --
>> 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
>>
> ___
> 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] Space used on server

[Nick Østergaard]

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 used in
> check.
>
> Since the move, there hasn't been any deletions of testing builds, and
> as of now, is coming up to 900GB, increasing about 100GB a month.
>
> Thanks,
> Tedd
>
> ___
> 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] Packaging for GitLab migration

[Nick Østergaard]

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-
>
> We're looking at timelines now for GitLab migration.  One thing we'd like
> to ensure is that the nightlight builds are still available.  Toward that
> end, I've submitted a couple PRs for updating the git repository to the new
> GitLab location in the Fedora and Mac builds.  It looks like Nick has a
> similar PR for the Windows build that should work with a minor modification.
>
> The GitLab repository is a read-only mirror at the moment but it is the
> same content as the launchpad repository.  Once the lead devs switch to
> committing code to GitLab, the launchpad repository will not be updated.
>
> The new git URL is https://gitlab.com/kicad/code/kicad.git
>
> I don't see a method for submitting a patch to the Ubuntu nightly build.
> @Jean-Samuel, will you be able to update the source location?
>
> Best-
> Seth
>
> --
> KiCad Services Corporation [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> https://twitter.com/KiProEDA 
> https://www.linkedin.com/company/kicad
> 
> ___
> 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] KiCad joins the Linux Foundation

[Nick Østergaard]

I am on a mobile screen

ons. 27. nov. 2019 17.01 skrev Wayne Stambaugh :

> I don't know how the donate window renders on your combination of
> browser and platform but given the width of the window that I'm seeing
> using Chrome on Linux, abbreviating Linux Foundation wont reduce the
> 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. 2019 15.06 skrev Wayne Stambaugh  > <mailto:stambau...@gmail.com>>:
> >
> > 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
> > donate buttons to "Donate via Linux Foundation" and "Donate via
> CERN" to
> > distinguish them.  I know that they are separated people tend to not
> > read things despite our best intentions.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 11/23/19 8:49 PM, Mark Roszko wrote:
> > > The attempt I took on adding TLF is live.
> > >
> > > On Sat, Nov 23, 2019 at 8:45 AM Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> wrote:
> > >
> > > Hi Sujith,
> > >
> > > I got it.  Thank you.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 11/22/19 10:09 PM, Sujith Anandan wrote:
> > > > Hello Wayne,
> > > >
> > > > I have already added you as page admin, please accept the
> > request you
> > > > will get in facebook.
> > > >
> > > > Thanks.
> > > > Sujith
> > > >
> > > > On Sat, Nov 23, 2019 at 5:15 AM Wayne Stambaugh
> > > mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>
> > > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>> wrote:
> > > >
> > > > I was wondering about that myself.  We can try a donate
> page
> > > and see how
> > > > it works.  We can always change it if we don't like it.
> > > >
> > > > On 11/22/19 3:53 PM, Mark Roszko wrote:
> > > > > I'm not sure about adding a second button in the
> header.
> > > > >
> > > > > I am envisioning creating a "Donate" page with both
> > CERN and
> > > Linux
> > > > > foundation options presented clearly with one big
> > button for
> > > each
> > > > and a
> > > > > small blurb for what each does. The header will go to
> this
> > > > intermediate
> > > > > page.
> > > > >
> > > > > On Fri, Nov 22, 2019 at 2:50 PM Wayne Stambaugh
> > > > mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> > > > > <mailto:stambau...@gmail.com
> > <mailto:stambau...@gmail.com> <mailto:stambau...@gmail.com
> > <mailto:stambau...@gmail.com>>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>>>
> wrote:
> > > > >
> > > > >
> > > > >
> > > > > On 11/22/19 2:39 PM, Mark Roszko wrote:
> > > > > >> I need to add a "Donate via Linux Foundation"
> > button
> > > to the
> > > > KiCad
> > > > > > website main page.
> > > >

Re: [Kicad-developers] KiCad joins the Linux Foundation

[Nick Østergaard]

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
> donate buttons to "Donate via Linux Foundation" and "Donate via CERN" to
> distinguish them.  I know that they are separated people tend to not
> read things despite our best intentions.
>
> Cheers,
>
> Wayne
>
> On 11/23/19 8:49 PM, Mark Roszko wrote:
> > 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:
> > > Hello Wayne,
> > >
> > > I have already added you as page admin, please accept the request
> you
> > > will get in facebook.
> > >
> > > Thanks.
> > > Sujith
> > >
> > > On Sat, Nov 23, 2019 at 5:15 AM Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > > >>
> wrote:
> > >
> > > I was wondering about that myself.  We can try a donate page
> > and see how
> > > it works.  We can always change it if we don't like it.
> > >
> > > On 11/22/19 3:53 PM, Mark Roszko wrote:
> > > > I'm not sure about adding a second button in the header.
> > > >
> > > > I am envisioning creating a "Donate" page with both CERN and
> > Linux
> > > > foundation options presented clearly with one big button for
> > each
> > > and a
> > > > small blurb for what each does. The header will go to this
> > > intermediate
> > > > page.
> > > >
> > > > On Fri, Nov 22, 2019 at 2:50 PM Wayne Stambaugh
> > > mailto:stambau...@gmail.com>
> > >
> > > > 
> >  > > >
> > > >
> > > >
> > > > On 11/22/19 2:39 PM, Mark Roszko wrote:
> > > > >> I need to add a "Donate via Linux Foundation" button
> > to the
> > > KiCad
> > > > > website main page.
> > > > >
> > > > > But is it in addition to or to replace CERN?
> > > >
> > > > In addition to.
> > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Nov 22, 2019 at 12:03 PM Wayne Stambaugh
> > > > mailto:stambau...@gmail.com>
> > >
> > > 
> > >>
> > > > >  >   > >
> > > 
> > 
> 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 some more flexibility on how
> > we can
> > > > spend donation
> > > > > money.  This does not in any way change our
> > relationship
> > > with
> > > > CERN and
> > > > > you can continue to donate via CERN if that is your
> > > > preference.  You
> > > > > should be seeing announcements from the Linux
> > Foundation
> > > shortly.
> > > > >
> > > > > I need to add a "Donate via Linux Foundation"
> > button to
> > > the KiCad
> > > > > website main page.  If someone would please point
> > me to the
> > > > correct
> > > > > place in the website source where I need to do
> > this, I would
> > > > appreciate
> > > > > it.  If you would rather do it yourself, the KiCad
> LF
> > > donation
> > > > link is
> > > > > https://funding.communitybridge.org/projects/kicad
> .
> > > > >
> > > > > Who has the account login information for the
> > KiCad Facebook
> > > > page?  I
> > > > > didn't 

Re: [Kicad-developers] 5.1.5 release tag

[Nick Østergaard]

Yes, late tonight in my timezone, tonight not that late in your timezone :)

ons. 27. nov. 2019 15.17 skrev Wayne Stambaugh :

> Hi Nick,
>
> Thanks, I'm not planning on making any changes to the release
> announcement so feel free to undraft it as is.  Are you going to be able
> 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 Østergaard wrote:
> > I just need to make sure they are mirrored to the github tags, so please
> > make it a pr and not mere it before the ci is green if you intend to
> > make the website change. But I will undraft it when everything is good,
> > so if you feed the need to add more info to the announcement please do
> > so as a draft.
> >
> > tir. 26. nov. 2019 20.37 skrev Wayne Stambaugh  > <mailto:stambau...@gmail.com>>:
> >
> > Perfect.  Thanks Adam!
> >
> > On 11/26/19 2:30 PM, Adam Wolf wrote:
> > > Not that I see. The macOS builds are uploading to S3 right now,
> should
> > > be finished within a few minutes.
> > >
> > > Adam
> > >
> > > On Tue, Nov 26, 2019 at 1:15 PM Wayne Stambaugh
> > mailto:stambau...@gmail.com>> wrote:
> > >>
> > >> Is there any reason for me to postpone the release announcement I
> was
> > >> planning for tomorrow?  It doesn't sound like it.
> > >>
> > >> On 11/25/19 9:02 PM, Adam Wolf wrote:
> > >>> Andy, thank you so much for this.  I normally run through the
> > releases
> > >>> but I am quite behind on some work and you definitely prevented
> the
> > >>> macOS release from holding everything up :)
> >     >>>
> > >>> I'll trigger builds tonight--there already 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 Nick Østergaard
> > mailto:oe.n...@gmail.com>
> > >>> <mailto:oe.n...@gmail.com <mailto:oe.n...@gmail.com>>> wrote:
> > >>>
> > >>> That is not a but, it is the autoplace fields feature.
> > >>>
> > >>> On Tue, 26 Nov 2019 at 01:58, Andy Peters  > <mailto:de...@latke.net>
> > >>> <mailto:de...@latke.net <mailto:de...@latke.net>>> wrote:
> > >>>
> > >>>
> > >>>> On Nov 25, 2019, at 5:31 PM, Ian McInerney
> > >>>>  > <mailto:ian.s.mciner...@ieee.org> <mailto:ian.s.mciner...@ieee.org
> > <mailto:ian.s.mciner...@ieee.org>>>
> > >>>> wrote:
> > >>>>
> > >>>> Andy, thank you for the feedback. None of these sound
> like
> > >>>> release stoppers though. Please file a bug report for
> the
> > >>>> first one, and the second one has been reported
> > >>>> already (https://bugs.launchpad.net/kicad/+bug/1850632
> ).
> > >>>
> > >>> Will do.
> > >>>
> > >>> One more.
> > >>>
> > >>> I’ve created a symbol in the Symbol Editor. In the
> > editor, the
> > >>> Reference Designator is placed just above the top of the
> > symbol
> > >>> and the Value (component name) is placed just below the
> > bottom
> > >>> of the symbol. See screenshot:
> > >>>
> > >>>
> > >>>
> > >>> But when the part is placed on the schematic, the
> reference
> > >>> designator is moved up to make room for the value field:
> > >>> I can’t figure out why it’s doing this.
> > >>>
> > >>> ___
> > >>> Mailing list: https://launchpad.net/~kicad-developers
> > >>> Post to : kic

Re: [Kicad-developers] New Official Bug Tracker Tags

[Nick Østergaard]

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 to avoid creating long tags, and since our current tags seem
> to be distributed more on the short side (and since in the new GitLab
> interface the tags are visible next to the issue name, the longer the tag
> the more UI space it takes up) I was trying to keep them short. (and these
> new ones would be on the upper end of the distribution of tag length, see
> below chart :) ).
>
> I guess the difference between sym-editor and symbol-editor is only 3
> characters though...
>
> [image: KiCadTagLength.png]
>
> -Ian
>
> On Tue, Nov 26, 2019 at 8:57 PM Jeff Young  wrote:
>
>> FWIW, in the code footprint is often abbreviated as fp, but symbol is
>> rarely abbreviated.
>>
>> On 26 Nov 2019, at 20:45, Ian McInerney  wrote:
>>
>> I do like fp-editor and sym-editor better. Note that for consistency with
>> the other multiword tags for GitLab, I will use a hyphen.
>>
>> -Ian
>>
>> On Tue, 26 Nov 2019, 8:07 p.m. Jeff Young,  wrote:
>>
>>> I would go with either historic (modedit and libedit) or current
>>> (fp_editor and symbol_editor).
>>>
>>> Mixing the two would be particularly obscure.
>>>
>>> Cheers,
>>> Jeff.
>>>
>>> > On 26 Nov 2019, at 19:40, Wayne Stambaugh 
>>> wrote:
>>> >
>>> >
>>> >
>>> > On 11/26/19 2:20 PM, Ian McInerney wrote:
>>> >> I would like to introduce two new official tags on the bug tracker to
>>> >> track issues relating to the symbol and footprint editors. Currently
>>> we
>>> >> are tracking these under the eeschema and pcbnew tags respectively,
>>> but
>>> >> those are growing quite large (pcbnew has over 500). I think tracking
>>> >> these two tools under separate tags would help, since then we can more
>>> >> easily locate bugs/wishlist items for them.
>>> >>
>>> >> I am thinking the footprint editor should be *modedit*, and my initial
>>> >> proposal for the symbol editor is *libedit*. I don't really like
>>> libedit
>>> >> though, since technically footprints also live in a library (but the
>>> >> code calls it libedit). Anyone have a better suggestion for its tag?
>>> >
>>> > How about "symedit", short for symbol editor.  Honestly I would prefer
>>> > "fpedit" over "modedit" since we really don't refer to footprints as
>>> > modules any more.
>>> >
>>> >>
>>> >> Once we sort out the tag, and if no one objects, I will go through and
>>> >> update the tags after the GitLab transition is done.
>>> >>
>>> >> -Ian
>>> >>
>>> >> ___
>>> >> 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
>>>
>>
>>
>
> --
> Ian McInerney
> mcians...@gmail.com
>
> No electrons were harmed in the making of this message
> ___
> 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 tag

[Nick Østergaard]

I just need to make sure they are mirrored to the github tags, so please
make it a pr and not mere it before the ci is green if you intend to make
the website change. But I will undraft it when everything is good, so if
you feed the need to add more info to the announcement please do so as a
draft.

tir. 26. nov. 2019 20.37 skrev Wayne Stambaugh :

> Perfect.  Thanks Adam!
>
> On 11/26/19 2:30 PM, Adam Wolf wrote:
> > Not that I see. The macOS builds are uploading to S3 right now, should
> > be finished within a few minutes.
> >
> > Adam
> >
> > On Tue, Nov 26, 2019 at 1:15 PM Wayne Stambaugh 
> wrote:
> >>
> >> Is there any reason for me to postpone the release announcement I was
> >> planning for tomorrow?  It doesn't sound like it.
> >>
> >> On 11/25/19 9:02 PM, Adam Wolf wrote:
> >>> Andy, thank you so much for this.  I normally run through the releases
> >>> but I am quite behind on some work and you definitely prevented the
> >>> macOS release from holding everything up :)
> >>>
> >>> I'll trigger builds tonight--there already 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 Nick Østergaard  >>> <mailto:oe.n...@gmail.com>> wrote:
> >>>
> >>> That is not a but, it is the autoplace fields feature.
> >>>
> >>> On Tue, 26 Nov 2019 at 01:58, Andy Peters  >>> <mailto:de...@latke.net>> wrote:
> >>>
> >>>
> >>>> On Nov 25, 2019, at 5:31 PM, Ian McInerney
> >>>> mailto:ian.s.mciner...@ieee.org>>
> >>>> wrote:
> >>>>
> >>>> Andy, thank you for the feedback. None of these sound like
> >>>> release stoppers though. Please file a bug report for the
> >>>> first one, and the second one has been reported
> >>>> already (https://bugs.launchpad.net/kicad/+bug/1850632).
> >>>
> >>> Will do.
> >>>
> >>> One more.
> >>>
> >>> I’ve created a symbol in the Symbol Editor. In the editor, the
> >>> Reference Designator is placed just above the top of the symbol
> >>> and the Value (component name) is placed just below the bottom
> >>> of the symbol. See screenshot:
> >>>
> >>>
> >>>
> >>> But when the part is placed on the schematic, the reference
> >>> designator is moved up to make room for the value field:
> >>> I can’t figure out why it’s doing this.
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> <mailto: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
> >>> <mailto: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
>
___
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] GitLab migration

[Nick Østergaard]

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 be doing anyway.  Anyone else object to this?
>
> Cheers,
>
> Wayne
>
> On 11/24/19 4:13 PM, Mark Roszko wrote:
> > Can the use of 2FA be mandated across the entire group since we have a
> > fresh start?
> >
> > It's been killing me that it's not required for GitHub and it really is
> > a vulnerability to not enforce. KiCad is a decent value target for
> > malicious code placement since it is a desktop app.
> >
> >
> https://docs.gitlab.com/ee/security/two_factor_authentication.html#enforcing-2fa-for-all-users-in-a-group
>
> >
> > On Tue, Nov 12, 2019 at 7:58 AM Wayne Stambaugh  > > wrote:
> >
> > Hey Orson,
> >
> > I'm on the fence on this one.  I remember similar issues when we
> > migrated from SourceForge.  It would be nice if we could migrate just
> > the bug reports that were fixed for 5.1 and later but I'm sure that
> is
> > not going to be possible because we did not do a great job in the
> past
> > of setting the bug report milestone.  This would at least make it
> > possible to search for bugs that have already been fixed in the
> current
> > stable branch without having to fall back to launchpad.  I'm not
> > concerned about closed bug reports for 5.0 and earlier since we no
> > longer support those branches.  We could migrate all the closed
> reports
> > with a milestone of 5.1.0 or later.  I know this wont be a complete
> > solution but it may be good enough.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 11/12/19 2:37 AM, Maciej Suminski wrote:
> > > Hi Andrew,
> > >
> > > I deliberately skipped the closed bugs, as I thought they do not
> carry
> > > much value, and they would still be available in the Launchpad
> > tracker.
> > > If majority prefers to migrate the closed bugs, then there is
> > nothing in
> > > the way.
> > >
> > > Cheers,
> > > Orson
> > >
> > > On 11/11/19 11:54 PM, Andrew Lutsenko wrote:
> > >> Is it possible to migrate closed bugs as well? I think gitlab
> search
> > >> indexing is much more useful, having history conserved there will
> > likely
> > >> be handy.
> > >>
> > >> On Mon, Nov 11, 2019 at 2:31 AM Maciej Suminski
> > mailto:maciej.sumin...@cern.ch>
> > >>  > >> wrote:
> > >>
> > >> Excellent, thanks for the verification! I have also checked a
> > few other
> > >> reports that had original authors incorrectly assigned, so I
> > believe the
> > >> bug has been fixed.
> > >>
> > >> Cheers,
> > >> Orson
> > >>
> > >> On 11/11/19 10:29 AM, Eeli Kaikkonen wrote:
> > >> > Now the example bug report ("Implicit 4-way junction" etc.)
> is
> > >> correctly
> > >> > attributed to "eelik".
> > >> >
> > >> > Eeli Kaikkonen
> > >> >
> > >> > su 10. marrask. 2019 klo 19.44 Maciej Suminski
> > >> (maciej.sumin...@cern.ch 
> > >
> > >> >  >   > >>)
> > >> kirjoitti:
> > >> >
> > >> > On 11/10/19 5:54 PM, Seth Hillbrand wrote:
> > >> > > On 2019-11-10 08:43, Seth Hillbrand wrote:
> > >> > >
> > >> > >> On 2019-11-10 08:33, Eeli Kaikkonen wrote:
> > >> > >>
> > >> > >>> OK. Would it be worth re-importing everything even
> for
> > >> this test
> > >> > database to avoid false impressions?
> > >> > >>>
> > >> > >>> Eeli Kaikkonen
> > >> > >>
> > >> > >> What false impression?  Is there a report that is
> > listed as
> > >> being
> > >> > created by different people in launchpad vs. GitLab?
> > >> > >
> > >> > > Oops.  Disregard.  I see a broken report here:
> > >> > >
> https://gitlab.com/orsonmmz/kicad-bug-tracker/issues/7367
> > >> > >
> > >> > > Looks like the Launchpad API doesn't handle users who
> > have since
> > >> > deleted
> > >> > > their accounts nicely and the script is falling back
> > on Fabien's
> > >> > > account, probably because his is index 0.
> > >> >
> > >> > Good catch, thanks! I think I have already found the
> bug, I
> > >> will let you
> > >> >

Re: [Kicad-developers] KiCad joins the Linux Foundation

[Nick Østergaard]

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:
>> > Hello Wayne,
>> >
>> > I have already added you as page admin, please accept the request you
>> > will get in facebook.
>> >
>> > Thanks.
>> > Sujith
>> >
>> > On Sat, Nov 23, 2019 at 5:15 AM Wayne Stambaugh > > > wrote:
>> >
>> > I was wondering about that myself.  We can try a donate page and
>> see how
>> > it works.  We can always change it if we don't like it.
>> >
>> > On 11/22/19 3:53 PM, Mark Roszko wrote:
>> > > I'm not sure about adding a second button in the header.
>> > >
>> > > I am envisioning creating a "Donate" page with both CERN and Linux
>> > > foundation options presented clearly with one big button for each
>> > and a
>> > > small blurb for what each does. The header will go to this
>> > intermediate
>> > > page.
>> > >
>> > > On Fri, Nov 22, 2019 at 2:50 PM Wayne Stambaugh
>> > mailto:stambau...@gmail.com>
>> > > >>
>> wrote:
>> > >
>> > >
>> > >
>> > > On 11/22/19 2:39 PM, Mark Roszko wrote:
>> > > >> I need to add a "Donate via Linux Foundation" button to the
>> > KiCad
>> > > > website main page.
>> > > >
>> > > > But is it in addition to or to replace CERN?
>> > >
>> > > In addition to.
>> > >
>> > > >
>> > > >
>> > > >
>> > > > On Fri, Nov 22, 2019 at 12:03 PM Wayne Stambaugh
>> > > mailto:stambau...@gmail.com>
>> > >
>> > > > 
>> > > 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 some more flexibility on how we
>> can
>> > > spend donation
>> > > > money.  This does not in any way change our relationship
>> > with
>> > > CERN and
>> > > > you can continue to donate via CERN if that is your
>> > > preference.  You
>> > > > should be seeing announcements from the Linux Foundation
>> > shortly.
>> > > >
>> > > > I need to add a "Donate via Linux Foundation" button to
>> > the KiCad
>> > > > website main page.  If someone would please point me to
>> the
>> > > correct
>> > > > place in the website source where I need to do this, I
>> would
>> > > appreciate
>> > > > it.  If you would rather do it yourself, the KiCad LF
>> > donation
>> > > link is
>> > > > https://funding.communitybridge.org/projects/kicad.
>> > > >
>> > > > Who has the account login information for the KiCad
>> Facebook
>> > > page?  I
>> > > > didn't create this so it would be nice if I had edit
>> > access so
>> > > I could
>> > > > post announcements there instead of asking someone else
>> > to do it.
>> > > >
>> > > > I hope joining the Linux Foundation will improve our
>> > potential
>> > > donor
>> > > > visibility so we can continue to grow the KiCad
>> project.
>> > > Thank you all
>> > > > for your continued support.
>> > > >
>> > > > 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
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Mark
>> > >
>> > >
>> > >
>> > > --
>> > > Mark
>> 

Re: [Kicad-developers] Who controls gitlab.com/kicad?

[Nick Østergaard]

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 name
> for the project.  The name appears to already be taken.  However, this is
> not a public group or user, so we don't know who controls the name.
>
> Does anyone on the list control the "kicad" name at GitLab?  In the
> interim, we've registered https://www.gitlab.com/kicad_pcb but it would
> be much better if we could use the shorter name.
>
>
> Thanks-
> Seth
>
>
> KiCad Services Corporation [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> https://twitter.com/KiProEDA 
> https://www.linkedin.com/company/kicad
> 
> ___
> 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] KiCad joins the Linux Foundation

[Nick Østergaard]

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 some more flexibility on how we can spend donation
> money.  This does not in any way change our relationship with CERN and
> you can continue to donate via CERN if that is your preference.  You
> should be seeing announcements from the Linux Foundation shortly.
>
> I need to add a "Donate via Linux Foundation" button to the KiCad
> website main page.  If someone would please point me to the correct
> place in the website source where I need to do this, I would appreciate
> it.  If you would rather do it yourself, the KiCad LF donation link is
> https://funding.communitybridge.org/projects/kicad.
>
> Who has the account login information for the KiCad Facebook page?  I
> didn't create this so it would be nice if I had edit access so I could
> post announcements there instead of asking someone else to do it.
>

I have admin access on it, but I think you got it as well from the
original creator (Sujith Anandan) of it. I don't really maintain it,
facebook is not really my thing.

> I hope joining the Linux Foundation will improve our potential donor
> visibility so we can continue to grow the KiCad project.  Thank you all
> for your continued support.
>
> 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 tag

[Nick Østergaard]

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.  Fedora 30 and 31 will have 5.1.5 in a week or 
> so, depending on whether we get any karma.
>
> Also of note - as of 5.1.5 we are now using OCC on all builds.  OCE is no 
> longer needed for current Fedora releases.
>
> Steve
>
> On 11/17/19 11:56 AM, Rene Pöschl wrote:
> > Libraries have been tagged.
> >
> > On 14/11/2019 18:36, Wayne Stambaugh wrote:
> >> The 5.1 branch has been tagged for 5.1.5 and the source archive has be
> >> uploaded to launchpad.  Please tag the library, doc, and translation
> >> repos so we can fire up those packages builders.
> >>
> >> Thanks,
> >>
> >> Wayne
> >>
> >> On 11/13/19 3:55 PM, Wayne Stambaugh wrote:
> >>> It's been a couple of weeks since 5.1.5-rc1 was tagged and everything
> >>> seems to have stabilized nicely.  I'm going to tag 5.1.5 tomorrow around
> >>> noon EST unless something comes up.  I'm assuming the libraries,
> >>> documentation, and translations are ready to go and that it shouldn't
> >>> take too long to get most of the installer packages build and uploaded
> >>> to the KiCad website.  I would like to make the release announcement on
> >>> Wednesday, November 27th.  It would be something to be thankful for
> >>> leading into the US Thanksgiving Holiday.  If there are any issues with
> >>> this date, please let me know.  Thank you everyone for your continued
> >>> support of the KiCad project.
> >>>
> >>> 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] Building current master fails

[Nick Østergaard]

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 this:
>
> cmake
> -DNGSPICE_INCLUDE_DIR=/Users/lijon/Coding/kicad-mac-builder/build/ngspice-dest/include/
>
> -DNGSPICE_LIBRARY=/Users/lijon/Coding/kicad-mac-builder/build/ngspice-dest/lib/libngspice.dylib
> -DKICAD_USE_OCE=OFF -DKICAD_SCRIPTING=OFF
>
> -DwxWidgets_CONFIG_EXECUTABLE=/Users/lijon/Coding/kicad-mac-builder/build/wxwidgets-dest/bin/wx-config
> -DKICAD_BUILD_QA_TESTS=OFF -DCMAKE_OSX_DEPLOYMENT_TARGET=10.14 ../..
>
> but it fails here:
>
> [ 42%] Building CXX object
> common/CMakeFiles/pcbcommon.dir/__/pcbnew/pcb_parser.cpp.o
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:996:18: error: use of
> undeclared identifier 'T_copper_finish'
> case T_copper_finish:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1002:18: error: use of
> undeclared identifier 'T_edge_plating'
> case T_edge_plating:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1008:18: error: use of
> undeclared identifier 'T_dielectric_constraints'
> case T_dielectric_constraints:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1014:18: error: use of
> undeclared identifier 'T_edge_connector'; did you mean
> 'T_zone_connect'?
> case T_edge_connector:
>  ^~~~
>  T_zone_connect
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:232:9: note:
> 'T_zone_connect' declared here
> T_zone_connect,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1020:35: error: use of
> undeclared identifier 'T_bevelled'
> else if( token == T_bevelled )
>   ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1026:18: error: use of
> undeclared identifier 'T_castellated_pads'
> case T_castellated_pads:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1088:30: error: use of
> undeclared identifier 'T_addsublayer'
> if( token == T_addsublayer )
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1100:26: error: use of
> undeclared identifier 'T_type'; did you mean 'T_top'?
> case T_type:
>  ^~
>  T_top
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:196:9: note: 'T_top'
> declared here
> T_top,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1123:26: error: use of
> undeclared identifier 'T_material'; did you mean 'T_general'?
> case T_material:
>  ^~
>  T_general
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:100:9: note: 'T_general'
> declared here
> T_general,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1129:26: error: use of
> undeclared identifier 'T_epsilon_r'
> case T_epsilon_r:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1135:26: error: use of
> undeclared identifier 'T_loss_tangent'
> case T_loss_tangent:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1141:26: error: use of
> undeclared identifier 'T_color'; did you mean 'T_bold'?
> case T_color:
>  ^~~
>  T_bold
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:60:9: note: 'T_bold'
> declared here
> T_bold,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1431:14: error: use of
> undeclared identifier 'T_stackup'; did you mean 'T_status'?
> case T_stackup:
>  ^
>  T_status
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:183:9: note: 'T_status'
> declared here
> T_status,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1524:14: error: use of
> undeclared identifier 'T_user_diff_pair'
> case T_user_diff_pair:
>  ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1571:14: error: use of
> undeclared identifier 'T_defaults'; did you mean 'default'?
> case T_defaults:
>  ^~
>  default
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1571:14: error:
> expected expression
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1638:14: error: use of
> undeclared identifier 'T_max_error'; did you mean 'T_mirror'?
> case T_max_error:
>  ^~~
>  T_mirror
> /Users/lijon/Coding/kicad/include/pcb_lexer.h:122:9: note: 'T_mirror'
> declared here
> T_mirror,
> ^
> /Users/lijon/Coding/kicad/pcbnew/pcb_parser.cpp:1639:58: error: use of
> undeclared identifier 

Re: [Kicad-developers] ngspice-31

[Nick Østergaard]

Hi Holger

I already built 5.1.5_1 for windows with ngspice 30, but I will
retrigger with ngspice 31 and that will give us 5.1.5_2 for windows. I
choose to do this in cause someone wanted to test stuff if some issue
were found.

The nightlies for windows will also use ngspice 31 from now on.

On Sun, 17 Nov 2019 at 12:11, Holger Vogt  wrote:
>
> Dear developers,
>
> would you mind distributing ngspice-31 with release 5.1.5?
> For macOS it is inevitable, to get rid of a seg-fault bug, it is part of
> the recent packages. For Windows and others this and other bug fixes may
> help.
>
> I have assembled some circuits for testing (including the four
> demo/simulation projects), available at
> http://ngspice.sourceforge.net/tests/kicad-test-circuits.7z. All my
> tests have been o.k. with Linux (openSUSE tumbleweed), macOS Catalina
> 15.1, Windows 7 and 10.
>
> ngspice.31 is available at Debian sid, bullseye, buster backports and
> even stretch backports sloppy, Fedora 30 and 31, Ubuntu Eoan and others.
>
>
> Viele Grüße
>
> Holger
>
>
> ___
> 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] Recipe for building Kicad on QT-Creator on Msys2 (Windows)

[Nick Østergaard]

FWIW there are some tips on using eclipse at
https://gist.github.com/johnbeard/895bad60e4716f7f9c77

On Mon, 18 Nov 2019 at 14:21, Dmitry Rezvanov  wrote:
>
> BTW, I'm programming and debugging Kicad in Eclipse.
> If necessary, I can create instruction for tuning.
>
>
> ___
> 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 tag

[Nick Østergaard]

Everything is tagged.

@adam, you should be able to bump the macos releases as well.

søn. 17. nov. 2019 17.57 skrev Rene Pöschl :

> Libraries have been tagged.
>
> On 14/11/2019 18:36, Wayne Stambaugh wrote:
> > The 5.1 branch has been tagged for 5.1.5 and the source archive has be
> > uploaded to launchpad.  Please tag the library, doc, and translation
> > repos so we can fire up those packages builders.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 11/13/19 3:55 PM, Wayne Stambaugh wrote:
> >> It's been a couple of weeks since 5.1.5-rc1 was tagged and everything
> >> seems to have stabilized nicely.  I'm going to tag 5.1.5 tomorrow around
> >> noon EST unless something comes up.  I'm assuming the libraries,
> >> documentation, and translations are ready to go and that it shouldn't
> >> take too long to get most of the installer packages build and uploaded
> >> to the KiCad website.  I would like to make the release announcement on
> >> Wednesday, November 27th.  It would be something to be thankful for
> >> leading into the US Thanksgiving Holiday.  If there are any issues with
> >> this date, please let me know.  Thank you everyone for your continued
> >> support of the KiCad project.
> >>
> >> 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] OCE vs OCC

[Nick Østergaard]

I can confirm your observation. I have been using occ for some time and
don't see any issues with switching other than the build script needs to
disable oce explicitly.

lør. 16. nov. 2019 17.42 skrev Steven A. Falco :

> It looks like Fedora may be switching from OCE to OCC, so I'm doing a
> trial build with OCC.
>
> How would folks recommend testing the build?  I'm not sure what would be
> necessary.
>
>
> Also, I have a question about CMakeLists.txt.  Around line 91, it says:
>
> option( KICAD_USE_OCC
> "Build tools and plugins related to OpenCascade Technology (overrides
> KICAD_USE_OCE, default OFF)"
> OFF )
>
> Note the comment that says KICAD_USE_OCC will override KICAD_USE_OCE.
> Thus, one would think that just setting KICAD_USE_OCC=ON would be
> sufficient to automatically set KICAD_USE_OCE=OFF
>
> Also, the code at line 472 makes it look like setting KICAD_USE_OCC=ON
> would set KICAD_USE_OCE=OFF.  However, in my build, that didn't work, and I
> had to explicitly set KICAD_USE_OCE=OFF.
>
> Steve
>
> ___
> 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] New lead developer announcement

[Nick Østergaard]

It is good to see Ian being recognized :) yaya

On Thu, 7 Nov 2019 at 21:55, Seth Hillbrand  wrote:

> On 11/7/19 12:14 PM, Wayne Stambaugh wrote:
>
> I am happy to announce that the KiCad project now has a new member of
> the lead development team.  Ian McInerney has accepted an invitation to
> become a member of the lead development team.  Ian's contributions have
> earned him this privilege and we are grateful for his efforts.  Please
> join me in congratulating Ian and welcoming in his new role.
>
> 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
>
> Congratulations, Ian!  And welcome!
>
> I'm really looking forward to working with you.
>
> Best-
> Seth
>
> --
> KiCad Services Corporation [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> https://twitter.com/KiProEDA 
> https://www.linkedin.com/company/kicad
> 
> ___
> 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] Website question

[Nick Østergaard]

Hi Wayne,

This is because of some minor technicalities not to mention time.

The intention is to get it working, but it is low priority on my todo list.

Nick

On Tue, 5 Nov 2019 at 18:41, Wayne Stambaugh  wrote:
>
> Is there any technical reason why our website is not using secure
> hosting via https://?  I noticed that our download site uses https://.
> I'm guessing at some point we are going to have to change this.  Thanks
> in advance for the help.
>
> 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] Benchmarking kicad compilation on CPUsreleased6 years apart

[Nick Østergaard]

I think we are derailing this thread by discussion this here. Lets not
keep doing that. Please start a new thread if you want support with
that.

On Wed, 30 Oct 2019 at 00:27, Brian Piccioni
 wrote:
>
> Nick
>
>
>
> Thanks for the lead. I am not very advanced on this stuff so if you can 
> direct me to an “Idiots Guide to Compiling Kicad with Microsoft Studio” if 
> such a thing exists I’d appreciate it.
>
>
>
> I got geographic re-annotation working in a standalone app and now I’m trying 
> to integrate it with Kicad so I can contribute.
>
>
>
> Brian
>
>
>
> From: Nick Østergaard
> Sent: October 29, 2019 7:19 PM
> To: Brian Piccioni
> Cc: Tomasz Wlostowski; Simon Richter; kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Benchmarking kicad compilation on 
> CPUsreleased6 years apart
>
>
>
> Hello Brian
>
>
>
> You would still need to obtain the dependencies in some way. vcpkg
>
> seems popular, but I still think there are issues with wxwidgets and
>
> vcpkg and some other dependencies kicad require to enable all features
>
> are not easily available.
>
>
>
> On Tue, 29 Oct 2019 at 22:28, Brian Piccioni
>
>  wrote:
>
> >
>
> > Tomasz
>
> >
>
> >
>
> >
>
> > Do you use Visual Studio to compile Kicad? If so, how? I’m not very good 
> > with things like cmake and I’ve tried and tried to get KiCad (or even just 
> > PCBNew) to compile with Visual Studio and end up with various problems I 
> > can’t solve like missing packages, etc..
>
> >
>
> >
>
> >
>
> > Besides the debugger, one thing with Visual Studio is that you only need 
> > Visual Studio, not MSYS2, Mingw, etc., etc..
>
> >
>
> >
>
> >
>
> > From: Tomasz Wlostowski
>
> > Sent: October 29, 2019 2:01 PM
>
> > To: Simon Richter; kicad-developers@lists.launchpad.net
>
> > Subject: Re: [Kicad-developers] Benchmarking kicad compilation on 
> > CPUsreleased 6 years apart
>
> >
>
> >
>
> >
>
> > On 29/10/2019 15:40, Simon Richter wrote:
>
> >
>
> > > We could probably shave off another two or three minutes of build time if
>
> >
>
> > > we could make sure that we always make progress on the critical path. The
>
> >
>
> > > dependency generation as a side effect pulls all the sources and headers
>
> >
>
> > > into cache, which reduces the effects of I/O latency a bit during
>
> >
>
> > > compilation, so parallelizing with more than the number of threads you
>
> >
>
> > > actually have is probably counterproductive.
>
> >
>
> >
>
> >
>
> > Hi,
>
> >
>
> >
>
> >
>
> > Another idea: use precompiled headers. I experimented some years ago
>
> >
>
> > with cotire for CMake on KiCad sources and it gave quite promising
>
> >
>
> > results. Since I didn't maintain this code it's probably useless by now
>
> >
>
> > given how new stuff has been added to KiCad tree but the savings in
>
> >
>
> > build time by header precompilation will be still IMHO quite significant.
>
> >
>
> >
>
> >
>
> > As for MSYS's GCC speed - personally I use Visual Studio under Windows,
>
> >
>
> > not only because of faster build time but also because of a debugger
>
> >
>
> > that actually works...
>
> >
>
> >
>
> >
>
> > As a side comment:
>
> >
>
> >
>
> >
>
> > $ make -j12 (latest KiCad master, i7-9750H, 32 GB DDR4 @ 2666 MHz,
>
> >
>
> > Ubuntu 19.04)
>
> >
>
> >
>
> >
>
> > real7m59.758s
>
> >
>
> > user   86m44.231s
>
> >
>
> > sys 5m9.724s
>
> >
>
> >
>
> >
>
> > Citing the classic: "not great, not terrible" ;-)
>
> >
>
> >
>
> >
>
> > Cheers,
>
> >
>
> > Tom
>
> >
>
> >
>
> >
>
> > ___
>
> >
>
> > 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] Benchmarking kicad compilation on CPUsreleased 6 years apart

[Nick Østergaard]

Hello Brian

You would still need to obtain the dependencies in some way. vcpkg
seems popular, but I still think there are issues with wxwidgets and
vcpkg and some other dependencies kicad require to enable all features
are not easily available.

On Tue, 29 Oct 2019 at 22:28, Brian Piccioni
 wrote:
>
> Tomasz
>
>
>
> Do you use Visual Studio to compile Kicad? If so, how? I’m not very good with 
> things like cmake and I’ve tried and tried to get KiCad (or even just PCBNew) 
> to compile with Visual Studio and end up with various problems I can’t solve 
> like missing packages, etc..
>
>
>
> Besides the debugger, one thing with Visual Studio is that you only need 
> Visual Studio, not MSYS2, Mingw, etc., etc..
>
>
>
> From: Tomasz Wlostowski
> Sent: October 29, 2019 2:01 PM
> To: Simon Richter; kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Benchmarking kicad compilation on 
> CPUsreleased 6 years apart
>
>
>
> On 29/10/2019 15:40, Simon Richter wrote:
>
> > We could probably shave off another two or three minutes of build time if
>
> > we could make sure that we always make progress on the critical path. The
>
> > dependency generation as a side effect pulls all the sources and headers
>
> > into cache, which reduces the effects of I/O latency a bit during
>
> > compilation, so parallelizing with more than the number of threads you
>
> > actually have is probably counterproductive.
>
>
>
> Hi,
>
>
>
> Another idea: use precompiled headers. I experimented some years ago
>
> with cotire for CMake on KiCad sources and it gave quite promising
>
> results. Since I didn't maintain this code it's probably useless by now
>
> given how new stuff has been added to KiCad tree but the savings in
>
> build time by header precompilation will be still IMHO quite significant.
>
>
>
> As for MSYS's GCC speed - personally I use Visual Studio under Windows,
>
> not only because of faster build time but also because of a debugger
>
> that actually works...
>
>
>
> As a side comment:
>
>
>
> $ make -j12 (latest KiCad master, i7-9750H, 32 GB DDR4 @ 2666 MHz,
>
> Ubuntu 19.04)
>
>
>
> real7m59.758s
>
> user   86m44.231s
>
> sys 5m9.724s
>
>
>
> Citing the classic: "not great, not terrible" ;-)
>
>
>
> Cheers,
>
> Tom
>
>
>
> ___
>
> 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] Python files still depending on Python2 only due used shebang

[Nick Østergaard]

For windows, someone newds to show phoenix working in either msys2 or msvc.
And if we will eventuallty transition to msvc we also need other
dependencies easily available. I am still hoping for those dependencies to
become available in vcpkg.

lør. 26. okt. 2019 17.13 skrev Ian McInerney :

> We should also be thinking of when we want to officially drop the Python 2
> support for KiCad. Since Python 2.7 will be end of life in just a few
> months, it might be worth starting the transition over to Python 3 (it
> looks like Windows and Mac builds ship with 2.7 currently).
>
> -Ian
>
> On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert 
> wrote:
>
>> Hello Wayne,
>>
>> Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:
>> > I'm guessing that fixing the shebangs will not be enough because there
>> > is python2 specific code in the script files.
>>
>> I think so, I've haven't looked at the Python3 compatibility of the
>> underlying code, just grep'd for potential shebang lines. Looking at the
>> date within the copyright statement let me be quite sure the files wont
>> be Python3 ready.
>>
>> And this is for sure true for mostly all the existing files.
>>
>> --
>> 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
>>
> ___
> 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]

+1

ons. 23. okt. 2019 15.28 skrev Wayne Stambaugh :

> One thing we don't specify on the system requirements page on the KiCad
> website is whether or not this applies to the current stable release or
> the nightly builds.  Since we don't specify this, I can see how users
> would assume that it's all versions of KiCad.  Perhaps we should note
> that this is only applicable to the current stable version and that
> nightly builds may not support older Linux distributions due to the
> availability of dependency library versions.  I don't think it's
> reasonable to expect the latest development version of KiCad to continue
> to support legacy Linux distros.  The current LTS release of Ubuntu is
> 18.04 which supports boost version 1.65.  I think attempting to support
> nightly builds on Ubuntu 16.04 is going to continue cause headaches as
> time goes on.  If no one objects, I will update the system requirements
> page accordingly.
>
> Cheers,
>
> Wayne
>
> On 10/23/2019 1:39 AM, Eeli Kaikkonen wrote:
> > It should also be noted that 20.04 will be the next LTS release of
> > Ubuntu. This means that there will be two post-16.04 LTS releases out
> > there before KiCad 6 will be released (I'm not *that* optimistic :) ).
> > Is it really worth it to actively support 3 different LTS releases? It
> > doesn't sound very realistic. How many users would actually be affected
> > if KiCad 6 wouldn't be available for 16.04? 1000s? 100s? 10? And if they
> > continue with 16.04 until 2021, why would they need to switch to KiCad 6
> > before that?
> >
> > Eeli Kaikkonen
> >
> > ke 23. lokak. 2019 klo 3.05 Seth Hillbrand (s...@kipro-pcb.com
> > ) kirjoitti:
> >
> > On 2019-10-22 16:06, Ian McInerney wrote:
> >
> >> I dug into the website history and apparently the original intent
> >> should have been to support 16.04 LTS until its standard support
> >> ends in 2021
> >> (
> https://github.com/KiCad/kicad-website/commit/007fb582a316fa513778a393e2696d17c0031cea#r33487782
> ).
> >> Since we haven't actually used any code from the newer Boost
> >> version (that we weren't already using), we should probably back
> >> out the change and also update the website with the correct Ubuntu
> >> LTS support date. It looks like that will make it so we can't
> >> update to 1.59 until 2021 then.
> >>
> >
> > Hi Ian-
> >
> > I did write that.  In retrospect, I'm not sure that the sentiment is
> > correct.  One of the things we are attempting to do is focus our
> > primary efforts where they will have the largest impact for our
> > users.  Toward that end, we were attempting (in the post KiCon
> > meeting) to define where that cut off should be.  We kind of
> > arbitrary picked "vendor supported" as it seemed reasonable.
> >
> > I now think we should tighten that a bit more for the Linux
> > distributions.  Under MSW/Mac, we compile or have rolling updates
> > for most of our own dependencies.  This allows us to ensure system
> > compatibility but not worry about library compatibility.  The Linux
> > library system is different and holds back updates.
> >
> > So, why would we want to update the boost libraries and what does it
> > gain us?  The original bump was to allow unit tests.  During v6, I
> > would also like to utilize the UUID library from 1.60 as many of the
> > feature we plan will require GUID at least.
> >
> > This doesn't preclude using KiCad on 16.04.  It just requires
> > someone to package a boost ppa.  There are a few out there that
> > could be used as baselines for this.
> >
> > -Seth
> >
> >
> > KiCad Services Corporation KiCad Services Corporation Logo
> > Seth Hillbrand
> > *Lead Developer*
> > +1-530-302-5483‬ 
> > Davis, CA
> > www.kipro-pcb.com i...@kipro-pcb.com
> > 
> > https://twitter.com/KiProEDA 
> > https://www.linkedin.com/company/kicad
> > 
> >
> > ___
> > 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   

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] Should gerber files in protel format use same name? (PATCH?)

[Nick Østergaard]

A related issue was brought up on
https://forum.kicad.info/t/gerber-filenames-with-protel-extensions/14177

I think the manufacturer should only make it a warning not an error. I
assume their reasoning is that they want to make sure only one project
is embedded in the gerber package they have, but I don't think that is
a fair way to determine if it is the same project.

I think having the layer names in the file name helps to verify that
the layer is correct when viewed in a gerber viewer.

I don't think the patch is good as is, as it changes the behaviour of
the protel file name extensions unconditionally. I think it should be
added as a option, but we already do have a lot of options. I think
you are better of using a python script for plotting and packing it up
as you like it. See for example
https://github.com/KiCad/kicad-source-mirror/blob/master/demos/python_scripts_examples/gen_gerber_and_drill_files_board.py

Don't your fab support X2 and gerber job files?

On Wed, 16 Oct 2019 at 09:16, Alexander Shuklin  wrote:
>
> Hi,
> sorry, I'm not quite sure with that topic, as I never worked with
> protel gerber format before. My PCB manufacturer started to use some
> online tool to check gerbers
> (https://www.frontline-pcb.com/products/sales/insight-pcb-overview.html)
> and now they demand to send them files with protel extensions. But
> that tool expect all files with same name. But now if you switch "use
> protel extensions" in KiCad, it generate something like :
> project_name-F_Cu.gtl
> project_name-B_Cu.gbl
> If "project_name.gtl" is the proper way, can you please apply my patch?
> btw, Altium creates similar to "project_name.gtl"
>
> And another question:
> For some reason they demand drill files to be same precision as
> gerbers (for example 4:5). Can you confirm that proper Excellon format
> should be 3:3 precision? In that case, I would send bug report to
> them.
> ___
> 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] GitLab migration

[Nick Østergaard]

The document is still open for comments on
https://docs.google.com/document/d/1pRcqXIXSn1_Ep2mYtSnoJWFahi9fMx4UJ8UEwFFwLkQ/edit?usp=sharing

On Thu, 10 Oct 2019 at 11:30, Ian McInerney  wrote:
>
> On a similar note, the issue workflow will need to be modified if the GitLab 
> tracker is used. Unfortunately, GitLab doesn't seem to have the same 
> functionality as the Launchpad tracker with respect to issue status and 
> severity. This might be a good time to finalize the earlier work that Nick 
> had started to formalize the issue process and the bug tracker workflow 
> before we transition to the GitLab tracker. That way we can define how we 
> want to do this from the outset. This will probably require some trial and 
> error and discussions to fully work it out.
>
> -Ian
>
> On Thu, Oct 10, 2019 at 8:51 AM Maciej Suminski  
> wrote:
>>
>> On 10/10/19 2:30 AM, Andrew Lutsenko wrote:
>> 
>> > In terms of issues migration I think moving open issues via script and
>> > locking down launchpad tracker is the best option. Even if migrated
>> > issues and comments on them will be owned by some service account/bot.
>> > It should be doable to include enough information there so that it's
>> > clear who originally posted it and the context is not lost.
>>
>> I agree, I am not sure if there is any added value in having correct
>> authors assigned to issues/comments, compared to displaying the
>> information in the contents field. Since I have spent some time
>> scripting both Launchpad and Gitlab, let me see how it can be done.
>>
>> Cheers,
>> Orson
>>
>> ___
>> 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