From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patchwork now connected to people.ipfire.org
Date: Sat, 04 Dec 2021 12:45:55 +0000 [thread overview]
Message-ID: <FB69D44F-6C5E-4CC8-9F5E-B44019DF21A9@ipfire.org> (raw)
In-Reply-To: <7b55bb77-796b-30e0-8b82-f60d6f98b5d8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
Hello Adolf,
It looks like I broke it yesterday when I was trying to fix how Patchwork reads our LDAP groups.
I have reverted my changes from yesterday now and you should be able to log in again.
Let me know if it doesn’t work, yet.
-Michael
> On 3 Dec 2021, at 21:44, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> On 21/10/2021 11:57, Adolf Belka wrote:
>> Hi Michael,
>>
>> On 20/10/2021 23:46, Michael Tremer wrote:
>>> Could you try again now?
>> Thanks very much, it is working now. I successfully changed the status of two of my old patches to superseded.
>>
> I have been going through my patches in IPFire over the last few weeks, updating any that had the wrong status. The last time I successfully logged in was a few days ago.
>
> Just now I tried to login and I got the message that my username or password were incorrect but the same credentials are still letting me login to IPFire People. So something has changed again with Patchwork.
>
> Regards,
>
> Adolf.
>
>> Adolf.
>>>
>>>> On 20 Oct 2021, at 21:40, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>>> On 19/10/2021 17:58, Michael Tremer wrote:
>>>>> Very good. Thanks for testing. Happy patching :)
>>>>>>> On 19 Oct 2021, at 16:45, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> On 19/10/2021 16:57, Michael Tremer wrote:
>>>>>>> Hello everyone,
>>>>>>>
>>>>>>> As requested at the last conference call, I have enabled LDAP authentication on Patchwork.
>>>>>>>
>>>>>>> I would like to ask people to log in and confirm that it works.
>>>>>>
>>>>>> Yeah, login successful. 😁
>>>> Today I tried to change some patches to status superseded. However I got the message that I don't have the permissions to change the status of my patches.
>>>>
>>>> Adolf.
>>>>>>
>>>>>> Adolf.
>>>>>>
>>>>>>> If there are any problems with it, feel free to raise them here or create a bug report.
>>>>>>>
>>>>>>> Best,
>>>>>>> -Michael
>>
next prev parent reply other threads:[~2021-12-04 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 14:57 Michael Tremer
2021-10-19 15:45 ` Adolf Belka
2021-10-19 15:58 ` Michael Tremer
2021-10-20 20:40 ` Adolf Belka
2021-10-20 21:46 ` Michael Tremer
2021-10-21 9:57 ` Adolf Belka
2021-12-03 21:44 ` Adolf Belka
2021-12-04 12:45 ` Michael Tremer [this message]
2021-12-04 14:04 ` 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=FB69D44F-6C5E-4CC8-9F5E-B44019DF21A9@ipfire.org \
--to=michael.tremer@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