On Fri, Sep 4, 2020 at 1:27 AM pgfed pagure@pagure.io wrote:

pgfed reported a new issue against the project: pagure that you are
following:
``
a new pagure project
```
https://pagure.io/pgnd/openldap-UPSTREAM-MIRROR

            pgnd / openldap-UPSTREAM-MIRROR
            Created 2 hours ago
            Maintained by pgfed
            This repo is brand new and meant to be mirrored from

https://git.openldap.org/openldap/openldap.git !
Mirrored projects are refreshed regularly, please seat
tight, code will come land soon!
```

setup to mirror a public repo

    https://git.openldap.org/openldap/openldap.git

is failing to populate

``

To reply, visit the link below or just reply to this email
https://pagure.io/pagure/issue/4983

Hi,

try

https://git.openldap.org/openldap/openldap

instead of

https://git.openldap.org/openldap/openldap.git

--
Lee

@leejnk

a few weeks ago, when this not-populating-a-repo had occurred with another upstread, I was told to ADD the .git suffix ... it was for a @gitlab repo, iirc. i was advised that one must use the provided clone URL ...

in this^^ case, that's explicitly:

https://git.openldap.org/openldap/openldap.git

, with the .git suffix.

in any case, I've switched it here ... we'll see what happens in a bit.

is there some guidance as to when to use the .git suffix, and when not? despite whatever the provided clone url might be?

is there some guidance as to when to use the .git suffix, and when not? despite whatever the provided clone url might be?

It depends on the Git server you are mirroring from. Some will require it, some won't. It's not a Pagure-side thing.

in any case, I've switched it here ... we'll see what happens in a bit.

unfortunately, neither source URL, with or without the suffix,

https://git.openldap.org/openldap/openldap
https://git.openldap.org/openldap/openldap.git

appears to work. the @pagure mirror remains UNpopulated.

This is what I'm seeing in the logs:

Sep 10 10:06:43 pagure01.fedoraproject.org python2[23818]: ERROR: [u'git', u'clone', u'--mirror', u'https://git.openldap.org/openldap/openldap', u'.'] =-- 128
Sep 10 10:06:43 pagure01.fedoraproject.org python2[23818]: Cloning into bare repository '.'...
Sep 10 10:06:43 pagure01.fedoraproject.org python2[23818]: error: RPC failed; result=22, HTTP code = 404
Sep 10 10:06:43 pagure01.fedoraproject.org python2[23818]: fatal: The remote end hung up unexpectedly

We really need to figure a way to provide this information to each project :/

there's no problem with any of

git clone https://git.openldap.org/openldap/openldap
git clone https://git.openldap.org/openldap/openldap.git
git clone --mirror https://git.openldap.org/openldap/openldap
git clone --mirror https://git.openldap.org/openldap/openldap.git

from any shell/location I test. doesn't appear to be a problem with the source; rather @ pagure.

this

https://github.com/pre-commit/pre-commit/issues/1206

suggests that git @ Pagure could be too old .

what OS/git-version runs @ Pagure?

We really need to figure a way to provide this information to each project :/

Turns out we already do, in the settings of mirrored project there is a "mirror logs" entry which contains the log of the last mirroring attempt.

I'm going to add a date to the log though as currently there is none and that's missing.

what OS/git-version runs @ Pagure?

To answer this question, we run git 2.27.0 and pygit2 0.26.4 on RHEL8

We really need to figure a way to provide this information to each project :/

Turns out we already do, in the settings of mirrored project there is a "mirror logs" entry which contains the log of the last mirroring attempt.

link: https://pagure.io/pgnd/openldap-UPSTREAM-MIRROR/settings#mirrorlog-tab

I'm thinking to close this ticket as invalid as both the original issue (lack of mirrorring in) as well as the follow up (we should provide the log info) are actually solved/already there.

Thoughts?

Makes sense to me.