public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: October 2023 Archives
Date: Mon, 30 Oct 2023 10:08:50 +0000	[thread overview]
Message-ID: <03F511C1-4331-405B-B9D9-C22B19141048@ipfire.org> (raw)
In-Reply-To: <860BE64E-B3EF-4AF7-AE7C-A0EBA38E36D3@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

Hello,

> On 20 Oct 2023, at 16:54, jon <jon.murphy(a)ipfire.org> wrote:
> 
> My IPFire Development list username and password did not work.  Is that normal?

No, not normal. But currently Peter is half way through a migration to Mailman 3 and nobody can log in any more :(

I hope he finds the time to finish the migration soon.

Best,
-Michael

> 
> 
> 
>> On Oct 20, 2023, at 3:08 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hello everyone,
>> 
>> Yes, this is correct.
>> 
>> Peter updated Mailman to Mailman 3 which changes a lot of things.
>> 
>> However, there should have been redirects from the old URLs to the new ones and the old archives should have been taken down.
>> 
>> I have opened a ticket for him to take care of this:
>> 
>>  https://bugzilla.ipfire.org/show_bug.cgi?id=13398
>> 
>> Thank you for raising this.
>> 
>> Best,
>> -Michael
>> 
>>> On 20 Oct 2023, at 07:49, ummeegge <ummeegge(a)ipfire.org> wrote:
>>> 
>>> It seems that a new version (update to mailman3) has been introduced --
>>>> 
>>> https://lists.ipfire.org/mailman3/hyperkitty/list/development(a)lists.ipfire.org/
>>> or via
>>> https://lists.ipfire.org
>>> and the URL has been changed.
>>> 
>>> Best,
>>> 
>>> Erik
>>> 
>>> 
>>> Am Donnerstag, dem 19.10.2023 um 21:10 -0500 schrieb jon:
>>>> I see the same thing.  Last update was Oct 1.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Jon Murphy
>>>> jon.murphy(a)ipfire.org
>>>> 
>>>> 
>>>> 
>>>>> On Oct 19, 2023, at 5:57 PM, Charles Brown <cab_77573(a)yahoo.com>
>>>>> wrote:
>>>>> 
>>>>> Is it just me?  I see no updates to "October 2023 Archives" past
>>>>> Oct 1st.
>>>>> 
>>>>> 
>>>>> https://lists.ipfire.org/pipermail/development/2023-October/date.ht
>>>>> ml
>>>>> 
>>>>> .
>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 


       reply	other threads:[~2023-10-30 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <860BE64E-B3EF-4AF7-AE7C-A0EBA38E36D3@ipfire.org>
2023-10-30 10:08 ` Michael Tremer [this message]
     [not found] <43888844-2084-4277-B8F6-978A91E71448@ipfire.org>
2023-10-20  6:49 ` ummeegge
2023-10-20  8:08   ` Michael Tremer
     [not found] <1e120b3e-b10b-4b73-903d-187bca7253f5.ref@yahoo.com>
2023-10-19 22:57 ` Charles Brown

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=03F511C1-4331-405B-B9D9-C22B19141048@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