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
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.
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
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
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.
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 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
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:17:49 |
Calls: | 7,466 |
Calls today: | 2 |
Files: | 12,691 |
Messages: | 5,627,864 |