[chuck c <bubbasnmp@xxxxxxxxx>]

"This project is mirrored from https://gitlab.com/wireshark/wireshark.git. Pull mirroring updated 6 minutes ago."

Seems to be auto updating and also the "Update Now" button is now working again.

On Wed, Jul 27, 2022 at 11:28 AM Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:

And yet again, my mirror is stuck at “Updating” for five days now.

I’m just not sure what’s going on there.

On 23 Jul 2022, at 02:05, chuck c <bubbasnmp@xxxxxxxxx> wrote:

https://gitlab.com/gitlab-org/gitlab/-/issues/368209#note_1035286538

"Because of the incident - gitlab-com/gl-infra/production#7420 (closed) the pull mirroring for public projects was temporary off to help us with processing delayed mirrors. The problem was identified and fixed on GitLab.com."

My repository mirrored this morning:

This project is mirrored from https://gitlab.com/wireshark/wireshark.git. Pull mirroring updated 12 hours ago.
 Successfully updated 12 hours ago. (Jul 22, 2022 6:26am CDT)

It's now back in "Update Scheduled...".

There was an update to the Gitlab issue above - "Update Delays might be expected, we are looking into it."

On Mon, Jul 18, 2022 at 11:07 AM Roland Knall <rknall@xxxxxxxxx> wrote:

Hi everyone

For those of you using a forked repository, I just want to inform you of an issue some of you might be having but not being aware of. For the past few days it seems, Gitlab has issues updating a forked repository, thus affecting those of you who forked directly from Gitlab. As a result, you may not have a master branch in your forked repository, which uses the latest changes.

There already seems to be work done at gitlab in that area: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/7420 and others are tracking the issue.

For now, those affected have to revert to a manual update of their forked repository. You can do that by using the following two lines back to back in a CLI (that is assuming, you followed the naming scheme used in the documentation, with upstream being the main wireshark repository):

git pull upstream master:master

git push origin master

After that, your local and remote-forked branch should have the latest changes.

Btw, deleting your repo and forking again, will not resolve the issue.

cheers

Roland

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe