[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: QT6 KDE Invent Repo has private/non-existent submodule
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-10-10 10:59:10
Message-ID: CA+XidOG_jV0x=BGkQCGcg_yAOzOw6XdFPiECSN3z59ZjGpZ6CQ () mail ! gmail ! com
[Download RAW message or body]

On Tue, Oct 10, 2023 at 8:31 PM <fekhesk@pm.me> wrote:

> At https://invent.kde.org/qt/qt/qt5 the `qtgrpc` submodule links to a
> 404 page, at least on the `dev` and `6.5.3` branches. Unsure if this is
> correct, but it is causing errors when doing a recursive `git pull` of
> the repository.


Thanks for raising this. For reasons not quite known to me, it appears that
when this project was provisioned it was done so as a private project.
This is certainly not normal practice for us, and has now been corrected.

This wasn't picked up earlier as the system that updates the mirror is
privileged and had the ability to see the private repository (and likewise,
whenever I need to do maintenance work within the Qt namespace on
invent.kde.org, I switch into Admin mode which bypasses all permission
checks including the public/private status of a project).

I've reviewed the list of private projects we currently have and can
confirm no other incorrectly flagged projects exist.

Cheers,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Tue, Oct 10, 2023 at 8:31 PM &lt;<a \
href="mailto:fekhesk@pm.me">fekhesk@pm.me</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">At <a \
href="https://invent.kde.org/qt/qt/qt5" rel="noreferrer" \
target="_blank">https://invent.kde.org/qt/qt/qt5</a> the `qtgrpc` submodule links to \
a<br> 404 page, at least on the `dev` and `6.5.3` branches. Unsure if this is<br>
correct, but it is causing errors when doing a recursive `git pull` of<br>
the repository.</blockquote><div><br></div><div>Thanks for raising this. For reasons \
not quite known to me, it appears that when this project was provisioned it was done \
so as a private project.</div><div>This is certainly not normal practice for us, and \
has now been corrected.</div><div><br></div><div>This wasn&#39;t picked up earlier as \
the system that updates the mirror is privileged and had the ability to see the \
private repository (and likewise, whenever I need to do maintenance work within the \
Qt namespace on <a href="http://invent.kde.org">invent.kde.org</a>, I switch into \
Admin mode which bypasses all permission checks including the public/private status \
of a project).</div><div><br></div><div>I&#39;ve reviewed the list of private \
projects we currently have and can confirm no other incorrectly flagged projects \
exist.</div><div><br></div><div>Cheers,</div><div>Ben</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]