Re: [Kicad-developers] auto conversion of sch file not working

On 1/20/20 11:44 AM, Wayne Stambaugh wrote: > Is mylib an entry in the list of libraries below the > > LibDir=/i/pcbs/kicad_parts;/usr/local/share/kicad/library Does this not illustrate a yes to your question? >>> /i/pcbs/kicad_parts$ ll mylib* >>> -rw-rw 1 dick develop 286715 Apr 16 2018

Re: [Kicad-developers] Rebase the tree?

No problem. Hopefully it wont cause too many issues for other devs who have to rebase any local changes. Cheers, Wayne On 1/20/20 6:15 PM, Jeff Young wrote: > Thanks, Wayne! > > Sorry for causing such a mess. > > Cheers, > Jeff. > > >> On 20 Jan 2020, at 22:32, Wayne Stambaugh wrote: >>

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] Rebase the tree?

Thanks, Wayne! Sorry for causing such a mess. Cheers, Jeff. > On 20 Jan 2020, at 22:32, Wayne Stambaugh wrote: > > I found it. I had to create a new protection for the master branch. I > pushed the changes and enabled the GitLab protection for the master > branch so we should be good to

Re: [Kicad-developers] Rebase the tree?

I found it. I had to create a new protection for the master branch. I pushed the changes and enabled the GitLab protection for the master branch so we should be good to resume normal development. Thank you for the help and patience to work through this. Cheers, Wayne On 1/20/20 5:27 PM, Nick

Re: [Kicad-developers] GitHub Mirror not updating?

Hi Simon, Wayne, > 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

Re: [Kicad-developers] GitHub Mirror not updating?

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,

Re: [Kicad-developers] Rebase the tree?

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

Re: [Kicad-developers] Rebase the tree?

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

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] Rebase the tree?

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

Re: [Kicad-developers] Rebase the tree?

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

Re: [Kicad-developers] Rebase the tree?

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 >

Re: [Kicad-developers] Rebase the tree?

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

Re: [Kicad-developers] GitHub Mirror not updating?

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? On 1/20/20 2:11 PM, Mark Roszko wrote: > Rebasing is still required if enabling LFS after already having added a > file previously. LFS is simply a hack on top of Git

Re: [Kicad-developers] Linux distribution support policy

This seems reasonable to me. I guess the question is how long are we going to keep this information available i.e. the last X number of stable releases? Should we create a separate section for each stable release and always have a separate section for the current development branch? I'm sure

Re: [Kicad-developers] GitHub Mirror not updating?

Rebasing is still required if enabling LFS after already having added a file previously. LFS is simply a hack on top of Git rather than a protocol level improvement. On Mon, Jan 20, 2020 at 1:42 PM Jon Evans wrote: > I can say from experience that enabling LFS would be a lot more hassle > than

Re: [Kicad-developers] GitHub Mirror not updating?

No objections here. I've updated the GitLab settings to prevent these large files from being added in the future. -Seth On 2020-01-20 11:01, Wayne Stambaugh wrote: In this case, I am willing to accept the grief of removing the blob commits and rebasing unless someone else is dead set against

Re: [Kicad-developers] GitHub Mirror not updating?

In this case, I am willing to accept the grief of removing the blob commits and rebasing unless someone else is dead set against this. On 1/20/20 12:23 PM, Nick Østergaard wrote: > Yes, that is the error we get for the mirror script. > > On Mon, 20 Jan 2020 at 18:08, Wayne Stambaugh wrote: >>

Re: [Kicad-developers] file_formats.pdf doc is gone

file / document properties, that says from around 2013? On 1/18/20 21:18, Kevin Cozens wrote: > On 2020-01-18 8:16 a.m., Michael Kavanagh wrote: >> Here's the source files. I have no idea how old/out of date these are, > > I've said it before that whoever maintains the format documents needs to

Re: [Kicad-developers] auto conversion of sch file not working

Is mylib an entry in the list of libraries below the LibDir=/i/pcbs/kicad_parts;/usr/local/share/kicad/library entry in the project file? After remapping, is there a mylib library entry in the project symbol library table with the correct path? The remapping function uses the symbol library

Re: [Kicad-developers] How to show pad in pcbnew by clicking pin in eeschema

Le 20/01/2020 à 17:19, Jon Evans a écrit : > This does appear to have broken at some point.  Filed an issue for it: > https://gitlab.com/kicad/code/kicad/issues/3791 > > -Jon Fixed. > > On Mon, Jan 20, 2020 at 11:10 AM Dick Hollenbeck > wrote: > > Quick help, >

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] GitHub Mirror not updating?

I can say from experience that enabling LFS would be a lot more hassle than rebasing. On Mon, Jan 20, 2020 at 12:09 PM 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

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] GitHub Mirror not updating?

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:

Re: [Kicad-developers] GitHub Mirror not updating?

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

Re: [Kicad-developers] auto conversion of sch file not working

Same is true if I try and load from project manager. On 1/20/20 10:24 AM, Dick Hollenbeck wrote: > I want to use standalone EESCHEMA (standalone =: run from command line not > project > manager) to load an old schematic. > > In the project *.pro file corresponding to the old schematic I see

[Kicad-developers] auto conversion of sch file not working

I want to use standalone EESCHEMA (standalone =: run from command line not project manager) to load an old schematic. In the project *.pro file corresponding to the old schematic I see this line: LibDir=/i/pcbs/kicad_parts;/usr/local/share/kicad/library In /i/pcbs/kicad_parts is a library that

Re: [Kicad-developers] How to show pad in pcbnew by clicking pin in eeschema

This does appear to have broken at some point. Filed an issue for it: https://gitlab.com/kicad/code/kicad/issues/3791 -Jon On Mon, Jan 20, 2020 at 11:10 AM Dick Hollenbeck wrote: > Quick help, > > When I click on a pin in eeschema I get the disambiguating menu and then I > say "pin" choice. >

Re: [Kicad-developers] How to show pad in pcbnew by clicking pin in eeschema

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

Re: [Kicad-developers] Linux distribution support policy

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:

[Kicad-developers] How to show pad in pcbnew by clicking pin in eeschema

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

[Kicad-developers] GitHub Mirror not updating?

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