Re: github password policy
On 2021-08-16 17:59, Doug Henderson via Cygwin-apps wrote: On Mon, 16 Aug 2021 at 07:45, ASSI wrote: Thomas Wolff writes: As I cannot update mintty anymore right now from the git command line, Yes, I use SSH for all repos now. Do. Not. Use. GitHub. The raison raison d'être for GitHub is and always has been to subvert the fully distributed workflow that Git was designed to provide and replace it with their centralized lock-in "solution". As well as GitHub for several public repos, I have used BitBucket for several private repositories, as they allowed several, while GitHub only allowed one. They also have a large number of add on features around the Git repositories, aimed at lock-in. Does anyone have online Git servers they use and can recommend? BTW, I have done Google searches, etc. I'm looking for enthusiastic personal endorsements. Used the same as you, but I recently also joined Gitlab, run as a virtual cooperative corp, as some of my recent adopted upstreams are hosted there, and getting redundant release announcements is never a bad thing. I haven't yet added any projects there. GNOME projects are now hosted there, and Alibaba, IBM, and SpaceX use it, but as Gitlab servers are on Google Cloud, and subject to US embargos like BitBucket, GitHub, and SourceForge, a European mirror https://framagit.org/ (part of the Framasoft non-profit network) on Debian infrastructure, has been set up to bypass Google and the US, as well as allow access to/from embargoed countries. https://about.gitlab.com/blog/2018/05/31/welcome-gnome-to-gitlab/ https://about.gitlab.com/blog/2020/09/08/gnome-follow-up/ https://framagit.org/explore/projects?name=gnome-=latest_activity_desc -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]
Re: github password policy
On Mon, 16 Aug 2021 at 07:45, ASSI wrote: > > Thomas Wolff writes: > > As I cannot update mintty anymore right now from the git command line, Yes, I use SSH for all repos now. > Do. Not. Use. GitHub. > > The raison raison d'être for GitHub is and always has been to subvert > the fully distributed workflow that Git was designed to provide and > replace it with their centralized lock-in "solution". As well as GidHub for several public repos, I have used BitBucket for several private repositories, as they allowed several, while GitHub only allowed one. They also have a large number of add on features around the Git repositories, aimed at lock-in. Does anyone have online Git servers they use and can recommend? BTW, I have done Google searches, etc. I'm looking for enthusiastic personal endorsements. Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com
Re: github password policy
On 8/16/21 5:51 PM, Thomas Wolff wrote: Am 16.08.2021 um 16:46 schrieb Lee: On 8/16/21, Thomas Wolff wrote: github have changed their authentication policy not to allow passwords anymore. So they are asking maintainers to acquire another kind of password (a "token"), which I did a while ago. But they refuse to support users with the transition, there is no "plug-and-play" howto available, except for those who are willing to dive into details of authentication stuff and spend a few study hours on that useless policy change. As I cannot update mintty anymore right now from the git command line, is any maintainer here impacted by the same issue and can help out with some advice how to get rid of this nuisance? ssh keys work - start here: https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh Thanks for the link. So I've now added my ssh key to github and successfully tested it. Now what? git push apparently still wants to use the old password and reports an error. Kind regards, Thomas Regards Lee . Check your push URL, make sure it is ssh://g...@github.com/.../. OpenPGP_0x713B5FE29C145D45.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: github password policy
On Mon, 2021-08-16 at 19:51 +0200, Thomas Wolff wrote: > > Am 16.08.2021 um 16:46 schrieb Lee: > > On 8/16/21, Thomas Wolff wrote: > > > github have changed their authentication policy not to allow passwords > > > anymore. > > > So they are asking maintainers to acquire another kind of password (a > > > "token"), which I did a while ago. > > > But they refuse to support users with the transition, there is no > > > "plug-and-play" howto available, except for those who are willing to > > > dive into details of authentication stuff and spend a few study hours on > > > that useless policy change. > > > As I cannot update mintty anymore right now from the git command line, > > > is any maintainer here impacted by the same issue and can help out with > > > some advice how to get rid of this nuisance? > > ssh keys work - start here: > > https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh > Thanks for the link. So I've now added my ssh key to github and > successfully tested it. > Now what? git push apparently still wants to use the old password and > reports an error. Make sure the (push)url for the remote to which you wish to push is in the form g...@github.com:NAMESPACE/PROJECT.git rather than an https:// form. -- Yaakov Selkowitz Senior Software Engineer - Platform Enablement Red Hat, Inc.
Re: github password policy
Am 16.08.2021 um 16:46 schrieb Lee: On 8/16/21, Thomas Wolff wrote: github have changed their authentication policy not to allow passwords anymore. So they are asking maintainers to acquire another kind of password (a "token"), which I did a while ago. But they refuse to support users with the transition, there is no "plug-and-play" howto available, except for those who are willing to dive into details of authentication stuff and spend a few study hours on that useless policy change. As I cannot update mintty anymore right now from the git command line, is any maintainer here impacted by the same issue and can help out with some advice how to get rid of this nuisance? ssh keys work - start here: https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh Thanks for the link. So I've now added my ssh key to github and successfully tested it. Now what? git push apparently still wants to use the old password and reports an error. Kind regards, Thomas Regards Lee
Re: [ITA] scowl Spell Checker Oriented Word Lists
On 2021-08-12 08:34, Marco Atzeri via Cygwin-apps wrote: On 15.08.2021 20:30, Brian Inglis wrote: I'd like to adopt the orphaned scowl Spell Checker Oriented Word Lists package and get it updated as it is a few years out of date. This package also provides and updates hunspell-en. all yours Thanks Marco ATTN: Marco Atzeri - this update will make 2020.12.07 english dictionaries available to build an updated aspell-en, as I noticed that is a make option, and the dates align, but the package is not updated with or by scowl, although it could be if you preferred. I will look on the matter I haven't spent much time looking at scowl's build other than adding "cygmake aspell" in scowl, then deal with the generated aspell-en files, or that there is a cygport aspell cygclass to do the aspell dictionary builds and installs. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]
Re: github password policy
On 8/16/21, Thomas Wolff wrote: > github have changed their authentication policy not to allow passwords > anymore. > So they are asking maintainers to acquire another kind of password (a > "token"), which I did a while ago. > But they refuse to support users with the transition, there is no > "plug-and-play" howto available, except for those who are willing to > dive into details of authentication stuff and spend a few study hours on > that useless policy change. > As I cannot update mintty anymore right now from the git command line, > is any maintainer here impacted by the same issue and can help out with > some advice how to get rid of this nuisance? ssh keys work - start here: https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh Regards Lee
Re: github password policy
On Aug 16 14:13, Thomas Wolff wrote: > github have changed their authentication policy not to allow passwords > anymore. > So they are asking maintainers to acquire another kind of password (a > "token"), which I did a while ago. > But they refuse to support users with the transition, there is no > "plug-and-play" howto available, except for those who are willing to dive > into details of authentication stuff and spend a few study hours on that > useless policy change. > As I cannot update mintty anymore right now from the git command line, is > any maintainer here impacted by the same issue and can help out with some > advice how to get rid of this nuisance? ssh pubkey works nicely, afaik. Corinna
Re: github password policy
Thomas Wolff writes: > As I cannot update mintty anymore right now from the git command line, > is any maintainer here impacted by the same issue and can help out > with some advice how to get rid of this nuisance? Do. Not. Use. GitHub. The raison raison d'être for GitHub is and always has been to subvert the fully distributed workflow that Git was designed to provide and replace it with their centralized lock-in "solution". Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
github password policy
github have changed their authentication policy not to allow passwords anymore. So they are asking maintainers to acquire another kind of password (a "token"), which I did a while ago. But they refuse to support users with the transition, there is no "plug-and-play" howto available, except for those who are willing to dive into details of authentication stuff and spend a few study hours on that useless policy change. As I cannot update mintty anymore right now from the git command line, is any maintainer here impacted by the same issue and can help out with some advice how to get rid of this nuisance? Thanks Thomas
Re: [ITA] scowl Spell Checker Oriented Word Lists
On 15.08.2021 20:30, Brian Inglis wrote: I'd like to adopt the orphaned scowl Spell Checker Oriented Word Lists package and get it updated as it is a few years out of date. This package also provides and updates hunspell-en. all yours ATTN: Marco Atzeri - this update will make 2020.12.07 english dictionaries available to build an updated aspell-en, as I noticed that is a make option, and the dates align, but the package is not updated with or by scowl, although it could be if you preferred. I will look on the matter
Re: [ITA] mingw64-{i686,x86_64}-libmpc
On 15.08.2021 21:26, Achim Gratz wrote: These packages are orphaned by Yaakov and I apparently missed these earlier when taking over maintainance of the MinGW64 stuff that I maintain the Cygwin side of. Please assign to me, I plan to update them for gcc-11. Regards, Achim. all yours Thanks Marco
