From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Login to patchwork to mark patches as superseded
Date: Wed, 02 Jun 2021 23:20:06 +0200 [thread overview]
Message-ID: <3417f6c9-bf7a-b309-3720-4ed181e9612d@ipfire.org> (raw)
In-Reply-To: <8beb6d5d-ba8f-34fa-7361-80f510a26748@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3345 bytes --]
Hi Peter,
On 02/06/2021 22:32, Peter Müller wrote:
> Hello Adolf,
> hello Michael,
> hello *,
>
> oh, I perhaps should have read Adolf's mail more closely. :-/
>
> Personally, I cannot login using my projects' mail address (peter.mueller(a)ipfire.org), either.
> My username (pmueller), however, works fine. Looks like a changed LDAP search or something...
>
> @{Adolf,Michael}: Can you confirm this?
Unfortunately I can't confirm that.
My login fails for both my email address adolf.belka(a)ipfire.org and my user name bonnietwin
Regards,
Adolf.
>
> Thanks, and best regards,
> Peter Müller
>
>
>> Hello,
>>
>> I cannot log in either. I do not know why.
>>
>> I restarted apache but I still cannot find anything in any logs.
>>
>> There is also a large update available which I should install some time soon.
>>
>> I love Patchwork; it has great functionality but it always feels a little bit buggy :(
>>
>> -Michael
>>
>>> On 30 May 2021, at 15:54, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>> Hi Peter,
>>>
>>> On 30/05/2021 12:22, Peter Müller wrote:
>>>> Hello Adolf,
>>>>
>>>> thanks for your message.
>>>>
>>>> Yes, marking patches as being superseded if their author submits a new version of them is
>>>> a manual task. (Sometimes, Patchwork also looses track and marks staged or applied patches
>>>> as still being "new". We unfortunately never really figured out why that is. :-/ )
>>>>
>>>> Personally, I am going through my patches listed at Patchwork every now and then, and add
>>>> labels (superseded, applied, etc.) to patches needing them. Not sure if someone else besides
>>>> me does this, but since Michael will have that entire enormous blob in his inbox sooner or
>>>> later, I guess cleaning that list up a bit helps. :-)
>>>>
>>>> I am surprised to learn your IPFire people credentials don't work there. Mine do...
>>>
>>> Okay, so I tried it again just now and had the same problem. It clears the password field, leaving the username field filled in and says in red:-
>>>
>>> Please enter a correct username and password. Note that both fields may be case-sensitive.
>>>
>>> My IPFire People password is 20 characters long and also contains several special characters. It works fine for me in IPFire People, IPFire Community, IPFire Bugzilla and IPFire Webmail.
>>>
>>> Just in case the special characters are causing a problem with Patchwork login I reset my password to only use digits and upper/lower case letters. The changed password worked with IPFire People, IPFire Community, IPFire Bugzilla and IPFire Webmail but again would not work with Patchwork.
>>>
>>> Regards,
>>>
>>> Adolf.
>>>>
>>>> Thanks, and best regards,
>>>> Peter Müller
>>>>
>>>>> Hi All,
>>>>>
>>>>> I have seen communications recently where a person was asked to login to Patchwork and mark old patches as superseded.
>>>>>
>>>>> If this is something I should not be doing myself then no problems, I will stay with what I am doing.
>>>>>
>>>>> If I am supposed to be doing that, how do I login to Patchwork. I tried logging in using my credentials from IPFire People and from IPFire Bugzilla. In both cases it said my username or password were incorrect.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Adolf.
>>>>>
>>> --
>>> Sent from my laptop
>>
next prev parent reply other threads:[~2021-06-02 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01044895-14CA-4FDF-94B2-C501D0679F81@ipfire.org>
2021-06-02 20:32 ` Peter Müller
2021-06-02 21:20 ` Adolf Belka [this message]
2021-08-05 21:28 ` Adolf Belka
2021-05-25 20:23 Adolf Belka
2021-05-30 10:22 ` Peter Müller
2021-05-30 14:54 ` Adolf Belka
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=3417f6c9-bf7a-b309-3720-4ed181e9612d@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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