On Tue, 2022-03-01 at 12:48 +0100, a a wrote:

Hi.

Today a tried to access contents of debian instaler git repository on salsa.debian.org and the
server responded with 403 error. Next i tried other content located on said server with the same
resposne. Was there a change in access policy or something is wrong with the server itself.

Thank You

Have A nice Day

See: https://micronews.debian.org/

Small headline and other than that we are being told nothing.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmIeDO0ACgkQckqptS8C TItHCA/8Di9QItW8vKIj0i7O888dRgVEjETsDyzNxTS/jmfMHkTMTCvsvn+GAyv8 14kwiRCxB8lq4V6l3v47duqrugOwYn+mMYVZSawNuLI4kXK+ykr7gjOm4hm13kQu hCN8ea6DnobxYcfZMWjKwL2SyXiopmyCFy3zomX1ditoL9qQPlIUwlvHRQuyVDSA 4014/NVTRDmfgzF+sRPhHaenkfZxpyrN7KpkbrXM1Mk1C4hRxAtKA6obp1IJFQOc Q8cgg//Y502PHFsZrWJrBzg0+gBJb/jzL/qZSX8vxjWPgs47BmND9TGj4ryJK/CF 18q0L4a44yNai4GIyeWB6crExGd9rwmZSe3G/Em1lXhPpIxkAr4WshfrgjLO9UyQ q6t7j2cfRj8Hj+dUNmlU2k8EYTkY5I06AuWu4bWSyOb3xyK+nv4Pt4oYwrHjbqId yOq4gYYgMn00QpPclqGzxPDoKczuF6rmNIkHs05YX0npr0+PBNL1500iWg04NHDx k/Nwh2Kc3A2C8/x9GHWzbq8gq64VjfCEK1BtqNEeNAi/+h3TelZ72kJ6G6gI1vho FFP9IR/1Oeia0x6TVEl0uZOvzW+cOrchiQJIuV6cIXejSNYKEFgpCN9Zfybxn0vA V6nk1tCaDZqDY2gSPO6ywgRUTaoQTw9h8NgVQrWD3RnQHAinzSs=
=t2BW
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

On 3/1/22 12:48, a a wrote:

Today a tried to access contents of debian instaler git repository on salsa.debian.org and the server responded with 403 error. Next i tried
other content located on said server with the same resposne. Was there a change in access policy or something is wrong with the server itself.

See: https://lists.debian.org/debian-infrastructure-announce/2022/02/msg00000.html

Kind Regards,

Bas

--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi.

Today a tried to access contents of debian instaler git repository on salsa.debian.org and the server responded with 403 error. Next i tried
other content located on said server with the same resposne. Was there a
change in access policy or something is wrong with the server itself.

Thank You

Have A nice Day

<div dir="ltr">Hi.<div><br></div><div>Today a tried to access contents of debian instaler git repository on <a href="http://salsa.debian.org">salsa.debian.org</a> and the server responded with 403 error. Next i tried other content located on said server
with the same resposne. Was there a change in access policy or something is wrong with the server itself.</div><div><br></div><div>Thank You</div><div><br></div><div>Have A nice Day</div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, Mar 01, 2022 at 12:09:17PM +0000, Philip Wyett wrote:

On Tue, 2022-03-01 at 12:48 +0100, a a wrote:

Hi.

Today a tried to access contents of debian instaler git repository on salsa.debian.org and the
server responded with 403 error. Next i tried other content located on said server with the same
resposne. Was there a change in access policy or something is wrong with the server itself.

Thank You

Have A nice Day

See: https://micronews.debian.org/

Small headline and other than that we are being told nothing.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

t's scheduled work: that is still ongoing - is that good enough?

All the very best, as ever,

Andy Cater

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 2022-03-01 at 12:56 +0000, Andrew M.A. Cater wrote:

On Tue, Mar 01, 2022 at 12:09:17PM +0000, Philip Wyett wrote:

On Tue, 2022-03-01 at 12:48 +0100, a a wrote:

Hi.

Today a tried to access contents of debian instaler git repository on salsa.debian.org and
the
server responded with 403 error. Next i tried other content located on said server with the
same
resposne. Was there a change in access policy or something is wrong with the server itself.

Thank You

Have A nice Day

See: https://micronews.debian.org/

Small headline and other than that we are being told nothing.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

t's scheduled work: that is still ongoing - is that good enough?

All the very best, as ever,

Andy Cater

Hi,

Thank you for the terse response. The two examples i.e. micronews and the infra list do not sound
that this is scheduled work at all. Better communication from teams would possibly give better
understanding and the patience of users/developers that is being asked for.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmIeG1wACgkQckqptS8C TIurNg//exFe6vwqvQvzPnWPEOusCQaePtjQ/um7Y3++GdIfMEje27iA8s8SSW7c pCdFOl90f9wMFpa5qFxrNE8tmRZukKdXRD6+gGyZB63ks+RX8HnHbs6LATd/F2Ey qP0NCFblKd4RiCbedCVYH2QNmg/rCm4Go91g6An1tGdhGxQH/rEp8jUWlU6ZKBPf aAZZ9qLUSGjZNF4nfdVb3F/O3Ub93gh8MFewhk5hc5DCg/ocMX222VfXd/v1dVMu X73UcU08Kr3HUdNRaucawXJsxjjYTaEAV63ykbCBC2tLQV3sYPam8CbltlD45azz 471MA7/RTELUrILELZNqytF8F1SF+U2E9QyxqZiBiwaBJ+ty5g7n7ifh3ipYeCne Tt8bjJV7Z2szMkSvgNux2L+jRNCa13GuoTpYYV7lSDOa/Sd8G+ncKuOjSbjKhomb jlGg//i23EeKsTDGZXR46Ptw3lECV6I0HOKGIfZRWBYDkldbtCuPg8Woi79u25Eb NJzc7/foj+r1hiE4U5PGyKEg1DyEAHCYvmUoGtjqHnpaamwwlF2dCO2+SMP6hRjl EScA3PhVQLHyG3836KjcFMhPtnaNg8gnGpRf0a0B5rXA6HpBLxeEDBpWVOyyIOXy gMWdZmMNjQBupuoOb52tQQEkDa7pTSfLhQC7Uw6Wmi1YVK9CWYk=
=v5cR
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

Hi Phil (and everyone)

On 2022/03/01 15:10, Philip Wyett wrote:

Thank you for the terse response. The two examples i.e. micronews and the infra list do not sound
that this is scheduled work at all. Better communication from teams would possibly give better
understanding and the patience of users/developers that is being asked for.

Our GitLab instance (Salsa), have fallen behind multiple versions. This
is due to a bunch of different hurdles that all came with their own
decisions (I'm going to urge the Salsa admins again to do a write-up
about it).

So what's happening now is point-to-point upgrades between all the
GitLab versions needed on this upgrade path, along with the migrations
between them (which are quite large, Salsa is one of the biggest GitLab instances out there).

So while a huge amount of pent up maintenance is all happening at once
now, at least regular updates (and security updates) will be able to run
again on short cycles.

(I hope salsa admins don't mind me posting this, but I hope it helps all
our contributors better understand what's going on).

On a practical note, please take note of any uploads you do during this downtime, and be sure to do a git push along with the tags when Salsa is
back up again.

-Jonathan

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 2022-03-01 at 15:24 +0200, Jonathan Carter wrote:

Hi Phil (and everyone)

On 2022/03/01 15:10, Philip Wyett wrote:

Thank you for the terse response. The two examples i.e. micronews and the infra list do not
sound
that this is scheduled work at all. Better communication from teams would possibly give better
understanding and the patience of users/developers that is being asked for.

Our GitLab instance (Salsa), have fallen behind multiple versions. This
is due to a bunch of different hurdles that all came with their own decisions (I'm going to urge the Salsa admins again to do a write-up
about it).

So what's happening now is point-to-point upgrades between all the
GitLab versions needed on this upgrade path, along with the migrations between them (which are quite large, Salsa is one of the biggest GitLab instances out there).

So while a huge amount of pent up maintenance is all happening at once
now, at least regular updates (and security updates) will be able to run again on short cycles.

(I hope salsa admins don't mind me posting this, but I hope it helps all
our contributors better understand what's going on).

On a practical note, please take note of any uploads you do during this downtime, and be sure to do a git push along with the tags when Salsa is back up again.

-Jonathan

Hi Jonathan,

Many thanks for the update. I hope work progresses well and salsa is available again soon post the
work that needs to be performed.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmIeJekACgkQckqptS8C TIvhWg//UBywhWP035d0DwB3MObEcy9cbu9F2ZnhUeT4tL1fF6kGsgc6JkBxc3jj zNGUs1Ohxs9Sc1U+79L+FXLG75FjuQEoiZ2sBFHFujjnqz7c5DZTyExyJpj5igdu f7TQentx5rpNNGOZW8kgBXHn6KQ8JA7nOsf2+7Wo/WjdOgjO4lJ+fonLujE8JoJV ds/MPYzVvu2IsyYCf3IXX+a/fILsv1bsNNSIeffyWoICDIifizt3fUX3b8dLkw7H es1qVE4Pk7CCAfMKX8c/FK/rWDs2s5oyd9kXBZ+8s+cOq5w1PaCkZ+D++5RA0H5g KP6R71wBuFr4BEu8Ikk6KZVJymN7iX41fZxykf2qMQe1XjZMi5appmP3vYsHq5Tx 9h9IdZYdVX7b/Fae2/0nJrUdG9prni+5n2IxYP9rYOtSRBLUcdLTgz7zo7nRDSC2 BwVW4MI9FzuCL97xkmS+27RXLT2937IE7RAY7SOUyloALy6+Iffo4cEqZ8GoXCJn VQrodGf6LRn6jvMYkAiSM9hqatAPWYGw3ZsunFPtmBJBXDJxA6w9bWsG51Y9hrHY 0b4ANzxmDDadEYR6lHCJuz5wV+HxWShcwNpmDHIQyFpNZuWBaboalA5BVLTCSxHV Njvoormxx9S2Xeohwn4+AxGEOIODRLEvLsVizwebnhWwJdk5WlI=
=WdRX
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

On 3/1/22 14:24, Jonathan Carter wrote:

Hi Phil (and everyone)

On 2022/03/01 15:10, Philip Wyett wrote:

Thank you for the terse response. The two examples i.e. micronews and
the infra list do not sound
that this is scheduled work at all. Better communication from teams
would possibly give better
understanding and the patience of users/developers that is being asked
for.

Our GitLab instance (Salsa), have fallen behind multiple versions. This
is due to a bunch of different hurdles that all came with their own
decisions (I'm going to urge the Salsa admins again to do a write-up
about it).

So what's happening now is point-to-point upgrades between all the
GitLab versions needed on this upgrade path, along with the migrations between them (which are quite large, Salsa is one of the biggest GitLab instances out there).

So while a huge amount of pent up maintenance is all happening at once
now, at least regular updates (and security updates) will be able to run again on short cycles.

(I hope salsa admins don't mind me posting this, but I hope it helps all
our contributors better understand what's going on).

On a practical note, please take note of any uploads you do during this downtime, and be sure to do a git push along with the tags when Salsa is
back up again.

-Jonathan

Like everyone, I am thankful for the volunteer time given by the Salsa
admins, and it feels great to know Salsa is fully updated.

While I very much appreciate the work, and understand the pain behind
migrating a huge db, I'd say the communication could be perfected.

The initial announcement explained none of the above, and the list
archive storing the announcement was down (because the list archive
needed Salsa to run). People even outside of Debian (like some managing
the Kolla OpenStack CI that uses Debian and extrepo) were affected. They
asked me multiple times what was going on, and it was painful to be
annoying asking on IRC (sorry guys, and thank you formorer and pabs for replying), and then relaying the small amount of info I could gather. A
status page (anywhere) would have help a lot (not everyone knows how to
read the topic on the #salsa channel). BTW, is there a public status
page for the Debian infra monitoring?

Cheers,

Thomas Goirand (zigo)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, Mar 01, 2022 at 01:55:52PM +0000, Philip Wyett wrote:

On Tue, 2022-03-01 at 15:24 +0200, Jonathan Carter wrote:

Hi Phil (and everyone)

On 2022/03/01 15:10, Philip Wyett wrote:

Thank you for the terse response. The two examples i.e. micronews and the infra list do not
sound
that this is scheduled work at all. Better communication from teams would possibly give better
understanding and the patience of users/developers that is being asked for.

Our GitLab instance (Salsa), have fallen behind multiple versions. This
is due to a bunch of different hurdles that all came with their own decisions (I'm going to urge the Salsa admins again to do a write-up
about it).

So what's happening now is point-to-point upgrades between all the
GitLab versions needed on this upgrade path, along with the migrations between them (which are quite large, Salsa is one of the biggest GitLab instances out there).

So while a huge amount of pent up maintenance is all happening at once
now, at least regular updates (and security updates) will be able to run again on short cycles.

(I hope salsa admins don't mind me posting this, but I hope it helps all our contributors better understand what's going on).

On a practical note, please take note of any uploads you do during this downtime, and be sure to do a git push along with the tags when Salsa is back up again.

-Jonathan

Hi Jonathan,

Many thanks for the update. I hope work progresses well and salsa is available again soon post the
work that needs to be performed.

Regards

Phil

Yes, salsa is back.

https://micronews.debian.org/2022/1646175793.html

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)