Fwd: sourceware.org migration notice

Fwd: sourceware.org migration notice

[Jon Turney]

Assuming this migration goes ahead as planned this weekend:

* I'll stop package upload processing sometime on Friday

* An announcement will be made when package upload processing is restored.

* Cygwin setup should continue to function (if it can't contact 
cygwin.com to fetch the mirror list, it should use a cached mirror list, 
and all package downloads are from a mirror)

-------- Forwarded Message --------
Subject: sourceware.org migration notice
Date: 26 Feb 2020 23:13:41 -0000
From: root@sourceware.org

Hi -

As a developer/accountholder on sourceware.org / gcc.gnu.org / 
cygwin.com, this email is to notify you about an upcoming service 
disruption involved
in migrating its services to a new server & new datacenter.  This is
currently scheduled to take place the weekend of March 7/8, 2020.

For more details, please keep an eye on the following web page,
https://sourceware.org/sourceware-wiki/MigrationStatus ,
and the #overseers IRC channel on freenode.

(If you are no longer involved in any of the projects hosted here, please
let us know so we can mark your account as an "emeritus" member and we
don't bother you again.)

- FChE

Re: Fwd: sourceware.org migration notice

[Jon Turney]

On 04/03/2020 13:33, Jon Turney wrote:
> 
> Assuming this migration goes ahead as planned this weekend:
> 
> * I'll stop package upload processing sometime on Friday
> 
> * An announcement will be made when package upload processing is restored.
> 
> * Cygwin setup should continue to function (if it can't contact 
> cygwin.com to fetch the mirror list, it should use a cached mirror list, 
> and all package downloads are from a mirror)

Unfortunately, due to some mis-coordination, the DNS for cygwin.com was 
updated a day earlier (today).

Please note that it may appear that you can currently git push to 
cygwin.com URLs, but that will be lost when the repositories on the old 
server are replicated onto the new server this weekend.

Re: Fwd: sourceware.org migration notice

[Jon Turney]

On 06/03/2020 18:27, Jon Turney wrote:
> On 04/03/2020 13:33, Jon Turney wrote:
>>
>> Assuming this migration goes ahead as planned this weekend:
>>
>> * I'll stop package upload processing sometime on Friday
>>
>> * An announcement will be made when package upload processing is 
>> restored.

package maintainer sftp and git is working.

calm is running again.

Re: Fwd: sourceware.org migration notice

[Marco Atzeri]

Am 09.03.2020 um 22:22 schrieb Jon Turney:
> On 06/03/2020 18:27, Jon Turney wrote:
>> On 04/03/2020 13:33, Jon Turney wrote:
>>>
>>> Assuming this migration goes ahead as planned this weekend:
>>>
>>> * I'll stop package upload processing sometime on Friday
>>>
>>> * An announcement will be made when package upload processing is 
>>> restored.
> 
> package maintainer sftp and git is working.
> 
> calm is running again.


it seems that the forwarding from cygwin-announce to cygwin
mailing list is not active anymore

cygwin-announce notices not forwarding to cygwin list

[Brian Inglis]

> On Sat, 14 Mar 2020 15:54:31 +0100, Marco Atzeri wrote:
>> Am 09.03.2020 um 22:22 schrieb Jon Turney:
>>> On 06/03/2020 18:27, Jon Turney wrote:
>>>> On 04/03/2020 13:33, Jon Turney wrote:
>>>>>
>>>>> Assuming this migration goes ahead as planned this weekend:
>>>>>
>>>>> * I'll stop package upload processing sometime on Friday
>>>>>
>>>>> * An announcement will be made when package upload processing is 
>>>>> restored.
>>> 
>>> package maintainer sftp and git is working.
>>> 
>>> calm is running again.
> 
> it seems that the forwarding from cygwin-announce to cygwin
> mailing list is not active anymore

Hi folks,

Could you please look at why cygwin-announce notices are no longer forwarding to
cygwin list post-migration, when you have some time from higher priority work,
or inform the folks responsible if not already CCed.

-- 
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.

Re: cygwin-announce notices not forwarding to cygwin list

[Jon Turney]

On 15/03/2020 17:34, Brian Inglis wrote:
>> On Sat, 14 Mar 2020 15:54:31 +0100, Marco Atzeri wrote:
>>> Am 09.03.2020 um 22:22 schrieb Jon Turney:
>>>> On 06/03/2020 18:27, Jon Turney wrote:
>>>>> On 04/03/2020 13:33, Jon Turney wrote:
>>>>>>
>>>>>> Assuming this migration goes ahead as planned this weekend:
>>>>>>
>>>>>> * I'll stop package upload processing sometime on Friday
>>>>>>
>>>>>> * An announcement will be made when package upload processing is
>>>>>> restored.
>>>>
>>>> package maintainer sftp and git is working.
>>>>
>>>> calm is running again.
>>
>> it seems that the forwarding from cygwin-announce to cygwin
>> mailing list is not active anymore
> 
> Hi folks,
> 
> Could you please look at why cygwin-announce notices are no longer forwarding to
> cygwin list post-migration, when you have some time from higher priority work,
> or inform the folks responsible if not already CCed.

This has been worked on, and appears to be working as of yesterday pm.

Re: cygwin-announce notices not forwarding to cygwin list

[Brian Inglis]

On 2020-03-15 11:37, Jon Turney wrote:
> On 15/03/2020 17:34, Brian Inglis wrote:
>>> On Sat, 14 Mar 2020 15:54:31 +0100, Marco Atzeri wrote:
>>>> Am 09.03.2020 um 22:22 schrieb Jon Turney:
>>>>> On 06/03/2020 18:27, Jon Turney wrote:
>>>>>> On 04/03/2020 13:33, Jon Turney wrote:
>>>>>>>
>>>>>>> Assuming this migration goes ahead as planned this weekend:
>>>>>>>
>>>>>>> * I'll stop package upload processing sometime on Friday
>>>>>>>
>>>>>>> * An announcement will be made when package upload processing is
>>>>>>> restored.
>>>>>
>>>>> package maintainer sftp and git is working.
>>>>>
>>>>> calm is running again.
>>>
>>> it seems that the forwarding from cygwin-announce to cygwin
>>> mailing list is not active anymore
>>
>> Hi folks,
>>
>> Could you please look at why cygwin-announce notices are no longer forwarding to
>> cygwin list post-migration, when you have some time from higher priority work,
>> or inform the folks responsible if not already CCed.
> 
> This has been worked on, and appears to be working as of yesterday pm.

The backlog between your notices on the 5th and Achim's on the 14th have not
been forwarded. How should this be handled? Should maintainers repost their
original announcements, make their own announcements on cygwin, or can the
process be rerun to forward only the missing posts?

-- 
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.