public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: overseers@gcc.gnu.org
Subject: Re: Problems recovering password
Date: Sat, 13 Feb 2021 09:35:10 -0800	[thread overview]
Message-ID: <37367a4a-e499-43c8-f40b-dfb9b5becb59@charter.net> (raw)
In-Reply-To: <20210213054803.GA19609@cgf.cx>

Hi Christopher,

jvdelisle@charter.net is current


The one at frontier.com can be deleted. That was my email many years 
ago. I moved and switched to charter.  I think at some point in there 
frontier spun off from verizon.

The current outlook addeess was an attempt for me to switch one to two 
years ago.  I use it for other stuff, but not gcc work.

When I noticed I had no priviledges in bugzilla anymore as I did before 
I noticed the browser had saved jvdelisle@gcc.gnu.org which does forward 
to me.  I was told by some of the other gfortran folks that I need to 
log on to that account.  When I tried to login in it failed to work so I 
tried a password reset several times.  I also tried to create a new 
account with that it it came back and said it existed.

Thus my confusion.  For bugzilla I would prefer to have a login of 
jvdelisle@gcc.gnu.org and to have the update of PRs privileges.  The 
others can go away except jvdelisle@gcc.gnu.org needs to forward to 
jvdelisle@charter.net.

Should I try to create an account using jvdelisle@gcc.gnu.org?  It is 
not so clear for me.

Regards,

Jerry

On 2/12/21 9:48 PM, Christopher Faylor wrote:
> On Fri, Feb 12, 2021 at 11:03:49AM -0800, Jerry DeLisle wrote:
>> Have tried to recover/reset my password to jvdelisle@gcc.gnu.org
>> several times.  The bugzilla website states it has sent a token to
>> jvdelisle@gcc.gnu.org, but it does not seem to arrive at
>> jvdelisle@charter.net.  If I send an email to the gcc.gno.org email
>> it does forward through to me.
>>
>> Regardsless, something seems broken. Can you help.
> I may be misinterpreting bugzilla's table structure but, AFAICT, you
> seem to have four logins but none are jvdelisle@gcc.gnu.org:
>
> MariaDB [bugs]> select login_name from profiles where login_name like 'jvdel%';
> +------------------------+
> | login_name             |
> +------------------------+
> | jvdelisle2@outlook.com |
> | jvdelisle@charter.net  |
> | jvdelisle@frontier.com |
> | jvdelisle@verizon.net  |
> +------------------------+
>
> bugzilla claims to be sending a token when it isn't really which is a
> fairly standard way of dealing with nonexistent accounts.  I just tried
> resetting my own password and used the wrong email address a couple of
> times with the same result.  I did get an email when I figured out the
> right email address though.
>
> cgf
>


  reply	other threads:[~2021-02-13 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 19:03 Jerry DeLisle
2021-02-13  5:48 ` Christopher Faylor
2021-02-13 17:35   ` Jerry DeLisle [this message]
2021-02-13 18:36     ` Christopher Faylor
2021-02-13 21:39       ` Jerry DeLisle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37367a4a-e499-43c8-f40b-dfb9b5becb59@charter.net \
    --to=jvdelisle@charter.net \
    --cc=overseers@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).