March 2023 - pacsat-dev - mailman.amsat.org

Pacsat dev meeting 3/30/2023
by Bill 30 Mar '23

30 Mar '23

Pacsat dev meeting 3/30/2023 Thu, Mar 30, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/513907517 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,513907517# Access Code: 513-907-517 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Pacsat dev meeting 3/23/2023
by Bill 23 Mar '23

23 Mar '23

Pacsat dev meeting 3/23/2023 Thu, Mar 23, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/222702053 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,222702053# Access Code: 222-702-053 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Software Architecture Doc updated
by Chris Thompson 19 Mar '23

19 Mar '23

As discussed on the call, I have updated the software architecture document. Please review and let me know any comments. https://github.com/AMSAT-NA/PacSatDocs/blob/main/requirements/Pacsat-Softwa… 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Pacsat dev meeting 3/16/2023
by Corey Minyard 16 Mar '23

16 Mar '23

On Thu, Mar 16, 2023 at 04:30:46PM +0000, Bill via pacsat-dev wrote: > Pacsat dev meeting 3/16/2023 > Thu, Mar 16, 2023 7:00 PM - 9:00 PM (CDT) I probably won't be able to make this. Either I will be NCS for the storms coming through Dallas (and Bill will probably be out, too) or I have another obligation. -corey > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/537925421 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (571) 317-3122 > - One-touch: tel:+15713173122,,537925421# > > Access Code: 537-925-421 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Pacsat dev meeting 3/16/2023
by Bill 16 Mar '23

16 Mar '23

Pacsat dev meeting 3/16/2023 Thu, Mar 16, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/537925421 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3122 - One-touch: tel:+15713173122,,537925421# Access Code: 537-925-421 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Pacsat-dev meeting 3/9/2023
by Burns Fisher (AMSAT) 09 Mar '23

09 Mar '23

I think I previously said that I could not come on the 1st Thursday of the month. Nope...I counted wrong. It is the second Thursday. In any case, I won't be there tonight. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Mar 9, 2023 at 2:41 PM Bill via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > Pacsat-dev meeting 3/9/2023 > Thu, Mar 9, 2023 7:00 PM - 9:00 PM (CST) > > Please join my meeting from your computer, tablet or smartphone. > > https://meet.goto.com/243430525 > > You can also dial in using your phone. > (For supported devices, tap a one-touch number below to join instantly.) > > United States: +1 (872) 240-3412 > - One-touch: tel:+18722403412,,243430525# > > Access Code: 243-430-525 > > > Get the app now and be ready when your first meeting starts: > https://meet.goto.com/install > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Pacsat-dev meeting 3/9/2023
by Bill 09 Mar '23

09 Mar '23

Pacsat-dev meeting 3/9/2023 Thu, Mar 9, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/243430525 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (872) 240-3412 - One-touch: tel:+18722403412,,243430525# Access Code: 243-430-525 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Missing Mar 9 meeting
by Burns Fisher (AMSAT) 07 Mar '23

07 Mar '23

As always, I am unable to make the first meeting of the month. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

PacSat git repo changes
by Burns Fisher (AMSAT) 03 Mar '23

03 Mar '23

Hi All, Bill and I talked this morning and decided (actually confirmed that we both agreed with what we already thought) that the PacSat git repository names are confusing. Bill and I agreed to change them, and I have done so. This means that if you have cloned them, you will have to change the upstream names in your local repository to match in order to push upstream. Here are the changes: 1. pacsatx is now PacSatSw and is to be use only for software (and documentation in the form of comments). 2. pacsat is now PacSatDocs and is to be used for documentation, including hardware schematics, hardware layouts etc. 3. PacSatSw is now WB1FJPacSatToDelete. This was the original repo that I created PacSatSw can be cloned directly into Code Composer Studio--it contains some of the CCS metadata to describe to the compiler where header files are etc. Currently there are two subdirectories in PacSatDocs: "requirements" and "reference". Requirements contains documents about PacSat itself. Reference contains files taken from other repositories, generally Fox or Golf SVN. These will usually be PDF files, and are NOT the masters. If changes are required, they must be made in the source files, which are in their original repositories. Bill is thinking about what to do regarding hardware, but will probably add a "hardware" folder for schematics etc etc. WB1FJPacSatToDelete can be deleted if no one is using it. It has had no checkins since November...it was moved to what is now PacSatSw at that time. We hope and expect that we will not have to do this again, and we apologize to those who have to change their local git repos. But hopefully, this renaming makes it a lot more clear what is going on. 73, Burns and Bill

1 1

Re: PacSat git repo changes
by Corey Minyard 03 Mar '23

03 Mar '23

On Fri, Mar 03, 2023 at 06:27:54PM +0000, Burns Fisher (AMSAT) via pacsat-dev wrote: > Hi All, > > Bill and I talked this morning and decided (actually confirmed that we both > agreed with what we already thought) that the PacSat git repository names > are confusing. Bill and I agreed to change them, and I have done so. Thanks, I was thinking about making a suggestion like this, but the new names are good names. -corey > > This means that if you have cloned them, you will have to change the > upstream names in your local repository to match in order to push upstream. > > Here are the changes: > > > > 1. pacsatx is now PacSatSw and is to be use only for software (and > documentation in the form of comments). > 2. pacsat is now PacSatDocs and is to be used for documentation, > including hardware schematics, hardware layouts etc. > 3. PacSatSw is now WB1FJPacSatToDelete. This was the original repo that > I created > > > PacSatSw can be cloned directly into Code Composer Studio--it contains some > of the CCS metadata to describe to the compiler where header files are etc. > > Currently there are two subdirectories in PacSatDocs: "requirements" and > "reference". Requirements contains documents about PacSat itself. > Reference contains files taken from other repositories, generally Fox or > Golf SVN. These will usually be PDF files, and are NOT the masters. If > changes are required, they must be made in the source files, which are in > their original repositories. > > Bill is thinking about what to do regarding hardware, but will probably add > a "hardware" folder for schematics etc etc. > > WB1FJPacSatToDelete can be deleted if no one is using it. It has had no > checkins since November...it was moved to what is now PacSatSw at that time. > > We hope and expect that we will not have to do this again, and we apologize > to those who have to change their local git repos. But hopefully, this > renaming makes it a lot more clear what is going on. > > > 73, > > Burns and Bill > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: No net?
by Burns Fisher (AMSAT) 02 Mar '23

02 Mar '23

That sux. Sorry about the storms. I'll try just in case. Should have stayed at the South Pole??? 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Thu, Mar 2, 2023 at 7:47 PM BILL via pacsat-dev <pacsat-dev(a)amsat.org> wrote: > > Bad storms here. Power out. Probably no net tonight. > Get BlueMail for Android <https://bluemail.me> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 1

Re: No net?
by Chris Thompson 02 Mar '23

02 Mar '23

Some of us are on if others want to join. On Thu, Mar 2, 2023 at 7:49 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > That sux. Sorry about the storms. I'll try just in case. Should have > stayed at the South Pole??? > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Thu, Mar 2, 2023 at 7:47 PM BILL via pacsat-dev <pacsat-dev(a)amsat.org> > wrote: > >> >> Bad storms here. Power out. Probably no net tonight. >> Get BlueMail for Android <https://bluemail.me> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

No net?
by BILL 02 Mar '23

02 Mar '23

Bad storms here. Power out. Probably no net tonight. ⁣Get BlueMail for Android

1 0

Pacsat dev meeting 3-2-2023
by Bill 02 Mar '23

02 Mar '23

Pacsat dev meeting 3-2-2023 Thu, Mar 2, 2023 7:00 PM - 9:00 PM (CST) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/131084093 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (571) 317-3112 - One-touch: tel:+15713173112,,131084093# Access Code: 131-084-093 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: Writing to the PacSatx git repository
by Chris Thompson 01 Mar '23

01 Mar '23

I am using ssh keys from the Linux command line (and windows). That works for me. You are authenticating to your own GitHub account of course, so the public key is stored in security preferences for your account. If you can push to one of your own repos with ssh then you should be able to push to the Pacsat repos. At least that was my experience. 73 Chris On Wed, Mar 1, 2023, 10:44 Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I'm happiest with Linux command line, too. I'll use one of my other GitHub > accounts that doesn't have special privileges in an attempt to reproduce > the behavior. > > In the meantime, as you say, SSH keys can be a good option. I'll also use > that in this environment. I'm been using 2FA with my account so this hasn't > popped up. > > Jonathan > On 3/1/23 09:37, Bob Stricklin via pacsat-dev wrote: > > Thanks to all for feedback… > > I can use any of the systems and methods you described Jonathan. My > preferred method is fro the command line on Linux but if I get that working > I can use MAC too. Windows would be my last choice. > > I have used SSH keys. Let me look into that idea. That would be a good > solution if it works. > > Never had any trouble with cloning a repository. The issue is writing and > deleting and creating on a repository. I have done all this on my own > repository. Burns, since you created PacSatx you are the owner and I would > not expect you to have a problem. > > Bob > > On Mar 1, 2023, at 8:28 AM, Burns Fisher (AMSAT) via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > > I've never had to use a token to clone a repo. I just did this yesterday > with the loader repo that Heimir created. I just looked in "Code" for the > URL to clone. So for pacsatx, it should be > > git clone https://github.com/AMSAT-NA/PacSatx.git > <https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> > > Checking something in is a different ball of wax. However, by "normal" > personal access token, created in my own account about the time that github > stopped allowing the normal password for checkins, seems to work fine. > There is also the public key method, but I think you have to mess around > with your local git to make that work. Or something. It works for the > repos in my own area, but not for the AMSAT-NA repos. > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I am happy to have a look at it. Can you remind me of your environment, >> please? >> >> Are you Windows, Mac or Linux? >> >> Are you using command line, web interface, or a Git client (like >> TortoiseGit)? >> >> Is your personal access token one of the fine-grained tokens? (There are >> a little tricky to use interactively but it can be configured. They must be >> given access to each individual API call as they are designed for automatic >> scripts.) Or is this a "classic" personal access token? (I know those are >> discouraged because of the ability for "lateral movement" between >> repositories in an organization.) Or, are you using 2FA? (I believe 2FA is >> the preferred mechanism for interactive human access). >> >> Thank you! >> >> Jonathan >> On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote: >> >> All, >> >> I continue to have an issue writing to the PacSatx repository. Jonathan >> has adjusted permissions to give me write access. Apparently there is more >> to it in this case. My use of git has mostly been with a repository I setup >> or one a company had. In this case it seems several here have owner rights >> in this repository. >> >> I have tried with one of my personal access Tokens, but I have seen this >> from GIT: >> >> Each token can only access resources owned by a single user or >> organization. Each token can only access specific repositories. Each >> token is granted specific permissions, which offer more control than the >> scopes granted to personal access tokens (classic). Each token must have an >> expiration date. >> Creating a personal access token - GitHub Docs >> <https://url.emailprotection.link/?b_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> >> >> I have also read it may be possible to access a GIT if you have a project >> Token and create access with that using: >> >> git clone "https://my-project: <https://url.emailprotection.link/?bUGyKvxiy3XARL1hpyUkkd27ECbOJxe-qS3Nqu-kp…>$PROJECT_TOKEN(a)my.gitlab.host/my-group/my-project.git" >> >> Would anyone that knows the process on how to do this please help with >> the steps or send me the needed Token so i can gain access? >> >> >> Thanks, >> >> Bob >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> -- >> Jonathan Brandenburg >> Radio Amateur Satellite Corporation >> 1-214-213-1066 >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org > > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Writing to the PacSatx git repository
by Jonathan Brandenburg 01 Mar '23

01 Mar '23

I'm happiest with Linux command line, too. I'll use one of my other GitHub accounts that doesn't have special privileges in an attempt to reproduce the behavior. In the meantime, as you say, SSH keys can be a good option. I'll also use that in this environment. I'm been using 2FA with my account so this hasn't popped up. Jonathan On 3/1/23 09:37, Bob Stricklin via pacsat-dev wrote: > Thanks to all for feedback… > > I can use any of the systems and methods you described Jonathan. My > preferred method is fro the command line on Linux but if I get that > working I can use MAC too. Windows would be my last choice. > > I have used SSH keys. Let me look into that idea. That would be a good > solution if it works. > > Never had any trouble with cloning a repository. The issue is writing > and deleting and creating on a repository. I have done all this on my > own repository. Burns, since you created PacSatx you are the owner and > I would not expect you to have a problem. > > Bob > >> On Mar 1, 2023, at 8:28 AM, Burns Fisher (AMSAT) via pacsat-dev >> <pacsat-dev(a)amsat.org> wrote: >> >> I've never had to use a token to clone a repo. I just did this >> yesterday with the loader repo that Heimir created. I just looked in >> "Code" for the URL to clone. So for pacsatx, it should be >> >> git clone https://github.com/AMSAT-NA/PacSatx.git >> <https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> >> >> Checking something in is a different ball of wax. However, by >> "normal" personal access token, created in my own account about the >> time that github stopped allowing the normal password for checkins, >> seems to work fine. There is also the public key method, but I think >> you have to mess around with your local git to make that work. Or >> something. It works for the repos in my own area, but not for the >> AMSAT-NA repos. >> >> 73, >> >> Burns Fisher, WB1FJ >> /AMSAT(R) Engineering -- Flight Software/ >> >> >> On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev >> <pacsat-dev(a)amsat.org> wrote: >> >> I am happy to have a look at it. Can you remind me of your >> environment, please? >> >> Are you Windows, Mac or Linux? >> >> Are you using command line, web interface, or a Git client (like >> TortoiseGit)? >> >> Is your personal access token one of the fine-grained tokens? >> (There are a little tricky to use interactively but it can be >> configured. They must be given access to each individual API call >> as they are designed for automatic scripts.) Or is this a >> "classic" personal access token? (I know those are discouraged >> because of the ability for "lateral movement" between >> repositories in an organization.) Or, are you using 2FA? (I >> believe 2FA is the preferred mechanism for interactive human access). >> >> Thank you! >> >> Jonathan >> >> On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote: >>> All, >>> >>> I continue to have an issue writing to the PacSatx repository. >>> Jonathan has adjusted permissions to give me write access. >>> Apparently there is more to it in this case. My use of git has >>> mostly been with a repository I setup or one a company had. In >>> this case it seems several here have owner rights in this >>> repository. >>> >>> I have tried with one of my personal access Tokens, but I have >>> seen this from GIT: >>> >>> Each token can only access resources owned by a single user or >>> organization. Each token can only access specific repositories. >>> Each token is granted specific permissions, which offer more >>> control than the scopes granted to personal access tokens >>> (classic). Each token must have an expiration date. >>> >>> >>> Creating a personal access token - GitHub Docs >>> <https://url.emailprotection.link/?b_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> >>> >>> >>> I have also read it may be possible to access a GIT if you have >>> a project Token and create access with that using: >>> >>> |git clone "https://my-project: >>> <https://url.emailprotection.link/?bUGyKvxiy3XARL1hpyUkkd27ECbOJxe-qS3Nqu-kp…>$PROJECT_TOKEN(a)my.gitlab.host/my-group/my-project.git"| >>> Would anyone that knows the process on how to do this please >>> help with the steps or send me the needed Token so i can gain >>> access? >>> >>> >>> Thanks, >>> >>> Bob >>> >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list --pacsat-dev(a)amsat.org >>> View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/[email protected] <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >>> To unsubscribe send an email topacsat-dev-leave(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> -- >> Jonathan Brandenburg >> Radio Amateur Satellite Corporation >> 1-214-213-1066 >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> <https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> <https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/[email protected] >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Re: Writing to the PacSatx git repository
by Bob Stricklin 01 Mar '23

01 Mar '23

Thanks to all for feedback… I can use any of the systems and methods you described Jonathan. My preferred method is fro the command line on Linux but if I get that working I can use MAC too. Windows would be my last choice. I have used SSH keys. Let me look into that idea. That would be a good solution if it works. Never had any trouble with cloning a repository. The issue is writing and deleting and creating on a repository. I have done all this on my own repository. Burns, since you created PacSatx you are the owner and I would not expect you to have a problem. Bob On Mar 1, 2023, at 8:28 AM, Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: I've never had to use a token to clone a repo. I just did this yesterday with the loader repo that Heimir created. I just looked in "Code" for the URL to clone. So for pacsatx, it should be git clone https://github.com/AMSAT-NA/PacSatx.git<https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQ…> Checking something in is a different ball of wax. However, by "normal" personal access token, created in my own account about the time that github stopped allowing the normal password for checkins, seems to work fine. There is also the public key method, but I think you have to mess around with your local git to make that work. Or something. It works for the repos in my own area, but not for the AMSAT-NA repos. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev <pacsat-dev(a)amsat.org<mailto:[email protected]>> wrote: I am happy to have a look at it. Can you remind me of your environment, please? Are you Windows, Mac or Linux? Are you using command line, web interface, or a Git client (like TortoiseGit)? Is your personal access token one of the fine-grained tokens? (There are a little tricky to use interactively but it can be configured. They must be given access to each individual API call as they are designed for automatic scripts.) Or is this a "classic" personal access token? (I know those are discouraged because of the ability for "lateral movement" between repositories in an organization.) Or, are you using 2FA? (I believe 2FA is the preferred mechanism for interactive human access). Thank you! Jonathan On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote: All, I continue to have an issue writing to the PacSatx repository. Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository. I have tried with one of my personal access Tokens, but I have seen this from GIT: Each token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date. Creating a personal access token - GitHub Docs<https://url.emailprotection.link/?b_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5…> I have also read it may be possible to access a GIT if you have a project Token and create access with that using: git clone "https://my-project:<https://url.emailprotection.link/?bUGyKvxiy3XARL1hpyUkkd27ECbOJxe-qS3Nqu-kp…>$PROJECT_TOKEN(a)my.gitlab.host/my-group/my-project.git" Would anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access? Thanks, Bob ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066 ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aq…> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gi…> ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:[email protected]> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:[email protected]> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Writing to the PacSatx git repository
by Burns Fisher (AMSAT) 01 Mar '23

01 Mar '23

I've never had to use a token to clone a repo. I just did this yesterday with the loader repo that Heimir created. I just looked in "Code" for the URL to clone. So for pacsatx, it should be git clone https://github.com/AMSAT-NA/PacSatx.git Checking something in is a different ball of wax. However, by "normal" personal access token, created in my own account about the time that github stopped allowing the normal password for checkins, seems to work fine. There is also the public key method, but I think you have to mess around with your local git to make that work. Or something. It works for the repos in my own area, but not for the AMSAT-NA repos. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I am happy to have a look at it. Can you remind me of your environment, > please? > > Are you Windows, Mac or Linux? > > Are you using command line, web interface, or a Git client (like > TortoiseGit)? > > Is your personal access token one of the fine-grained tokens? (There are a > little tricky to use interactively but it can be configured. They must be > given access to each individual API call as they are designed for automatic > scripts.) Or is this a "classic" personal access token? (I know those are > discouraged because of the ability for "lateral movement" between > repositories in an organization.) Or, are you using 2FA? (I believe 2FA is > the preferred mechanism for interactive human access). > > Thank you! > > Jonathan > On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote: > > All, > > I continue to have an issue writing to the PacSatx repository. Jonathan > has adjusted permissions to give me write access. Apparently there is more > to it in this case. My use of git has mostly been with a repository I setup > or one a company had. In this case it seems several here have owner rights > in this repository. > > I have tried with one of my personal access Tokens, but I have seen this > from GIT: > > Each token can only access resources owned by a single user or organization. > Each token can only access specific repositories. Each token is granted > specific permissions, which offer more control than the scopes granted to > personal access tokens (classic). Each token must have an expiration date. > Creating a personal access token - GitHub Docs > <https://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > I have also read it may be possible to access a GIT if you have a project > Token and create access with that using: > > git clone "https://my-project:[email protected]/my-group/my-project.git" > > Would anyone that knows the process on how to do this please help with the > steps or send me the needed Token so i can gain access? > > > Thanks, > > Bob > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org > > -- > Jonathan Brandenburg > Radio Amateur Satellite Corporation > 1-214-213-1066 > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Writing to the PacSatx git repository
by Corey Minyard 01 Mar '23

01 Mar '23

On Wed, Mar 01, 2023 at 02:51:54AM +0000, Bob Stricklin via pacsat-dev wrote: > All, > > I continue to have an issue writing to the PacSatx repository. Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository. > > I have tried with one of my personal access Tokens, but I have seen this from GIT: > > Each token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date. > Creating a personal access token - GitHub Docs<https://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > I have also read it may be possible to access a GIT if you have a project Token and create access with that using: > > > git clone "https://my-project:[email protected]/my-group/my-project.git" There's probably an easier way to do this, especially if you are running on Linux. You need to create an ssh key and upload it. On Linux you should already have one in ~/.ssh/id_xxx.pub, where xxx is the key type. If that's not there, then run ssh-keygen. I'd recommend using an ed25519 key, but rsa is fine. (Run ssh-keygen -t ed25519). Don't use dsa. I don't know how to do that on Windows. Then you need to upload it to github. That's in "settings" -> SSH and GPG keys. Then click on "New SSH key". Then paste in the contents of the public key file (ends in .pub, as above). Once you have that, clone it with ssh. In the repository view on github, you click on "Code" then shoose Local then SSH. Clone what is says there, like "git clone [email protected]:AMSAT-NA/pacsat.git". I've never tries the otken access because it's fairly inconvenient. -corey > > Would anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access? > > > Thanks, > > Bob > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Writing to the PacSatx git repository
by Jonathan Brandenburg 01 Mar '23

01 Mar '23

I am happy to have a look at it. Can you remind me of your environment, please? Are you Windows, Mac or Linux? Are you using command line, web interface, or a Git client (like TortoiseGit)? Is your personal access token one of the fine-grained tokens? (There are a little tricky to use interactively but it can be configured. They must be given access to each individual API call as they are designed for automatic scripts.) Or is this a "classic" personal access token? (I know those are discouraged because of the ability for "lateral movement" between repositories in an organization.) Or, are you using 2FA? (I believe 2FA is the preferred mechanism for interactive human access). Thank you! Jonathan On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote: > All, > > I continue to have an issue writing to the PacSatx repository. > Jonathan has adjusted permissions to give me write access. Apparently > there is more to it in this case. My use of git has mostly been with a > repository I setup or one a company had. In this case it seems several > here have owner rights in this repository. > > I have tried with one of my personal access Tokens, but I have seen > this from GIT: > > Each token can only access resources owned by a single user or > organization. Each token can only access specific repositories. Each > token is granted specific permissions, which offer more control than > the scopes granted to personal access tokens (classic). Each token > must have an expiration date. > > > Creating a personal access token - GitHub Docs > <https://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> > > > I have also read it may be possible to access a GIT if you have a > project Token and create access with that using: > > |git clone "https://my-project: > <https://my-project:>$PROJECT_TOKEN(a)my.gitlab.host/my-group/my-project.git"| > Would anyone that knows the process on how to do this please help with > the steps or send me the needed Token so i can gain access? > > > Thanks, > > Bob > > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/[email protected] > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org -- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

1 0

Writing to the PacSatx git repository
by Bob Stricklin 28 Feb '23

28 Feb '23

All, I continue to have an issue writing to the PacSatx repository. Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository. I have tried with one of my personal access Tokens, but I have seen this from GIT: Each token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date. Creating a personal access token - GitHub Docs<https://docs.github.com/en/authentication/keeping-your-account-and-data-sec….> I have also read it may be possible to access a GIT if you have a project Token and create access with that using: git clone "https://my-project:[email protected]/my-group/my-project.git" Would anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access? Thanks, Bob

1 0