Re: [Kicad-developers] 5.1.6 Release Update
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
Re: [Kicad-developers] 5.1.6 docs tarball?
Thanks Nick - I didn't know that. I thought Adam was looking for the source tar rather than pre-built docs. Steve On 5/14/20 3:44 PM, Nick Østergaard wrote: @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 kBps32s ===> 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] 5.1.6 docs tarball?
@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] 5.1.6 docs tarball?
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 kBps32s ===> 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
Re: [Kicad-developers] no broken default fp-lib-table, removed footprint library
On 14/05/2020 18:43, Wayne Stambaugh wrote: Rene, I wonder if we should implement a library commit message policy similar to the one we use for the source repo[1] and tailor the changelog tags for how library commits (or any other kicad repo) are made? It's pretty painless from a committers point of view since you already have to provide a commit message with git. Maybe a "PACKAGING" tag that could easily be extracted would be helpful. It probably wouldn't hurt to have this tag in the source repo as well so we don't blindside package devs with new dependencies and folder layout changes. Cheers, Wayne [1]: https://docs.kicad-pcb.org/doxygen/commit_messages.html . I am against rejecting any library contributions because of git to be honest. Most of our contributors are complete novices with git. I kind of supect they are mostly electrical engineers not software engineers so quite unlikely to need git knowledge in their career. We might already filter out a lot of potentially good contributors with the very small git knowledge that we need to require and i don't want to increase the negative impact of git. Right now we librarians write new messages for our contributors during the merge process (we use githubs squash feature). Because of that we can not use CI and not even a manual review to ensure following of some commit message rules. A fully manual workflow is extremely error prone so i doubt we will ever get a full changelog from git. To be honest something similar to our changelog script that analyzes symbols might in the end be a better fit for the whole lib. Even better would be a graphical diff tool to be honest. And all of that build into kicad itself for example as part of the "update footprint/update symbol" tools. After all the library assets are graphical things. Describing changes to them using text is really not helpful at all. ___ Mailing list: https://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
Carsten, What information do you need from KiCad. Does Debian (or any other disto) have recommendations for upstream projects to help packagers? 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. Rene, I wonder if we should implement a library commit message policy similar to the one we use for the source repo[1] and tailor the changelog tags for how library commits (or any other kicad repo) are made? It's pretty painless from a committers point of view since you already have to provide a commit message with git. Maybe a "PACKAGING" tag that could easily be extracted would be helpful. It probably wouldn't hurt to have this tag in the source repo as well so we don't blindside package devs with new dependencies and folder layout changes. Cheers, Wayne [1]: https://docs.kicad-pcb.org/doxygen/commit_messages.html On 5/14/20 11:56 AM, Rene Pöschl wrote: > The kicad library team does not have the resources to properly handle > even our main tasks (see the number of open pull requests awaiting > review, hint it is >300 with >600 open over all) let alone handling > additional docu. Plus we are not working with sourcecode. The skills of > the librarieans are in checking electrical constrains not git, not > packaging, ... > > Also consider that 90% of changes are additions of new assets which can > only be documented in a graphical way (screenshots of the asset, > dimensioned drawings, ...) so really the documentation is in the pull > requests not in git (git links to the pull requests) again completely > different to software! > > See the kicad library more akin to optional binary assets instead of > sourcecode (similar example would be the clipart library of a word > processor) > > --- > > I did not fully read your previous message so i do not quote it either > ;) (Another thing that is strange to at least me is a mailing list. I > would be much more conferrable on a forum or even the issue tracker.) > > lg Rene > > ___ > Mailing list: https://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
The kicad library team does not have the resources to properly handle even our main tasks (see the number of open pull requests awaiting review, hint it is >300 with >600 open over all) let alone handling additional docu. Plus we are not working with sourcecode. The skills of the librarieans are in checking electrical constrains not git, not packaging, ... Also consider that 90% of changes are additions of new assets which can only be documented in a graphical way (screenshots of the asset, dimensioned drawings, ...) so really the documentation is in the pull requests not in git (git links to the pull requests) again completely different to software! See the kicad library more akin to optional binary assets instead of sourcecode (similar example would be the clipart library of a word processor) --- I did not fully read your previous message so i do not quote it either ;) (Another thing that is strange to at least me is a mailing list. I would be much more conferrable on a forum or even the issue tracker.) lg Rene ___ Mailing list: https://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?
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 kBps32s > ===> 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
Re: [Kicad-developers] 5.1.6 docs tarball?
## 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 kBps32s ===> 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
[Kicad-developers] 5.1.6 docs tarball?
Hi folks! 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. Is that something that will happen today? I built test builds using the 5.1.6 tags for everything using the 5.1.5 docs tarball, and they went fine, so once this is ready, I can get the mac builds uploaded. I think this might be two times in a row that macOS isn't holding up the release! :D Adam ___ Mailing list: https://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] Compile problem with Fedora 32
On 5/14/20 1:28 AM, victor tejada wrote: Hello, guys, I tried to compile kicad source code on fedora 32 but the error is "ImportError: No module named wx CMake Error at CMakeModules/FindwxPython.cmake:52 (message): wxPython/Phoenix does not appear to be installed on the system Call Stack (most recent call first): CMakeLists.txt:740 (find_package)" so wxPython 4.0.1 is installed on my pc. I don't understand what happened. I'm not sure which version of KiCad that you are trying to build. I've built 5.1.6 for F32, and you can install it from the testing repository. In 6 days it will be pushed to the stable repository. Here is a link to bohdi, which lists a command that you can use to install: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6371942327 You can also download the source and binary packages directly here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1506421 If you grab the source rpm file, you might try rebuilding it using mock. Mock will pull in all the dependencies while building. 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
Re: [Kicad-developers] no broken default fp-lib-table, removed footprint library
Hello Evan, thanks for taking some time and writing up some sentences and opinions. I don't wanted to blame anybody by my email, I just wanted to raise some concerns I did have. KiCad is not the only upstream project I package for Debian. From about 5 years experience of Debian packaging I can say that getting information from upstream about changes is far more important than a source tree that is building without problems. The latter is something I simply expect. I've made mixed experience with various upstream projects, there are projects it's really a pleasure to work with and there are also projects with it's own difficulties. Packagers don't expect they get all needed information directly in person by upstream developers, but it shouldn't take a long time to find all relevant stuff. Other FOSS projects have websites that holding all the information. What does KiCad have here? Am 13.05.20 um 15:52 schrieb Evan Shultz: > Carsten, > > It was was my PR that was merged ( > https://github.com/KiCad/kicad-footprints/pull/1586) which removed these > footprints. In the initial PR comment I noted removing the Multicomp > footprints and it was also discussed in later comments. Those footprints > were deleted with commit > https://github.com/KiCad/kicad-footprints/pull/1586/commits/acce9a43b8e105b28db62589c71c37036af8446e, > where I specifically noted this in the commit message, but I expect the PR > was squash merged. Yeah, possible. Commit messages are for developers that are by nature deeply within their project(s) and know how to read them. But well written and organized commit messages can be an easy and excellent source for collecting some information for a release. For the KiCad main application this was discussed multiple times also on the -dev list. There were some suggestions about using trigger word and terms like FEATURE, BUGFIX so far I remember. > When something similar happened in the past, I created > https://bugs.launchpad.net/kicad/+bug/1820305 (now at > https://gitlab.com/kicad/code/kicad/-/issues/2360). And I was careful to > check that this PR didn't cause similar problems. > > I can understand requesting some readme file, and in this case I did leave > a readme file in Connector_Multicomp library but I edited the file to > specifically tell the user where to find the compatible footprints. See > https://github.com/KiCad/kicad-footprints/tree/master/Connector_Multicomp.pretty That's the only thing I've found so far. But also consider that such files will mostly not get installed by the packaging tools because they are detected as non library related. It's fully o.k. and normal to place such an file here. But please document all these cases in a central README file e.g. too. This is done by FOSS projects since ever. Why not here? There is a reason why GNU is suggesting the usage of the files COPYING, README, INSTALL, LICENSE. > In a general sense, we (I am also a librarian) have learned from issues in > the past. We know that removing footprints (not symbols!) won't cause > issues for existing designs so we allowed this change during a 'minor' > release. Is that somehow documented publicity? I can't find anything about this specific but also important topic on the typical places I'd start to search. https://kicad.github.io/ https://kicad-pcb.org/libraries/contribute/ https://kicad-pcb.org/libraries/klc/#_footprint_guidelines > (Note that we try to only merge changes that would affect existing > designs if there is a bug being fixed that outweighs any user trouble.) > There are many changes happening with each release and we have let GitHub > capture the discussion and resolution (as it was done here). There may be > some notable changes to the library worth announcing during minor releases, > but usually keeping some running readme file for the library as a whole > would only duplicate work for no benefit I can see. And here is exact the contrary point I have, packagers and also users don't look into git history. They don't even have one as they get a tarball as a release! Please try to always also have a view from a user side and ask yourself if you would expect this as user! Talk about and announce your modifications, collect ideally some statistics for each release. People love numbers! Make some marketing. :) Shouldn't be that hard to enhance the existing Python tools you have to provide some numbers about libraries and their amount of symbols. > Also note that Rene was careful to review symbol cjanges and he did > provide a summary of things that could impact users at> > https://github.com/KiCad/kicad-symbols/issues/2656#issuecomment-626880880 > before tagging the library as 5.1.6. Fine, I'm reading this for the first time. But why wasn't this presented to a broader audience? As written, you can't expect that every person is stepping through the GitHub and now also also the GitLab sites to get an full overview. > All this is to say we will try not to repeat past
